Mark Foltz

icon indicating an email [email protected]

icon company Google icon location Seattle, WA icon location Senior Staff Software Engineer at Google, works on Chrome/Chromium. Primary developer of the Open Screen Library. Editor of various W3C specs for media.

Results 205 comments of Mark Foltz

Investigate message latency requirements for media sync

Thanks @chrisn. I will file a followup issue for the sub-10ms use case.

Investigate message latency requirements for media sync

> Thanks @chrisn. I will file a followup issue for the sub-10ms use case. Filed https://github.com/w3c/openscreenprotocol/issues/325 for this.

[SSDP] Investigate mechanisms to pre-filter devices by Presentation URL

Closing as: - We are not using SSDP any more so discussion of SSDP is moot. - There is a standard way to advertise device-specific capabilites through protocol extensions: https://w3c.github.io/openscreenprotocol/#protocol-extensions

[Meta] Write document describing protocol requirements

Closing out this old issue, discussion of Guest Mode can continue in #41.

[QUIC] Investigate WebSocket layering onto QUIC

Current spec requires QUIC; verification of the TLS certificates is done through a authentication step via SPAKE2 in the current spec: https://w3c.github.io/openscreenprotocol/#authentication-with-spake2 I don't think WebSockets are going to be...

[SSDP] Ensure that advertised friendly names are i18n capable

Closing as we are not using SSDP.

[Meta] Performance data for discovery protocols

We've already committed to mDNS in the current spec.

Presentation reconnection with an implementation specific mechanism?

Closed by https://github.com/w3c/openscreenprotocol/pull/323.

[SSDP] Get network and power efficiency data

Closing as we are not using SSDP.

[QUIC] Define suspend and resume behavior for connection protocol

Filed #324 to follow up on state synchronization.