openscreenprotocol
openscreenprotocol copied to clipboard
w3c
Open Screen Protocol
These comments relate to the authentication discussion of the open screen protocol. In particular I wanted to comment on the devices and their certificate discussion from the [last F2F meeting](https://www.w3.org/2018/05/17-webscreens-minutes.html#x09)....
Follow-up from Berlin F2F - See slide 43 of the [slide deck]( https://drive.google.com/file/d/1dWQuJIe5tn62VdrIfR9g6LiSUEx5UMuJ/view) This is a placeholder to investigate alternative discovery mechanisms. Currently we have specified SSDP as the non-mandatory...
From https://www.w3.org/2017/11/07-webscreens-minutes.html#x21: - ACTION: @schien to check the timeline of TLS 1.3 deployments from Mozilla's editors (Seems a little silly for this, but I'm filing issues for all TPAC action...
This is for data collection to compare discovery protocols.
From https://github.com/webscreens/openscreenprotocol/pull/20/files#r108024631 --- mfoltzgoogle 3 days ago Collaborator How is FRIENDLY-NAME encoded? @louaybassbouss louaybassbouss 2 days ago Collaborator it is just a clear-text string field like the other SSDP headers....
This meta-issue tracks the work to gather performance data on proposed discovery protocols. Even though both SSDP and mDNS have been implemented in Chrome (and Mozilla?), for a variety of...
Background: https://github.com/w3c/presentation-api/issues/32 This use case is not yet explicitly supported by Presentation API, but we should make the control protocol forward compatible with a reasonable implementation of it.
From https://www.w3.org/2017/11/07-webscreens-minutes.html#x05: - ACTION: @mfoltzgoogle to clarify that device requirements are driven by rendering Web content and not the network stack - ACTION: @mfoltzgoogle to consult internally to find out...