Tomoyuki Shimizu

Now IETF HTTP WG is discussing WebSockets with HTTP/2 again: https://lists.w3.org/Archives/Public/ietf-http-wg/2017OctDec/0076.html https://tools.ietf.org/html/draft-mcmanus-httpbis-h2-websockets-01

@mfoltzgoogle One question: Does QUARTC require a bootstrapping signaling channel as current RTCDataChannel does?

Thanks, @schien!

> This is will become the major road blocker for HbbTV and ASTC since they both depend on non-secured local web server. The problem with secure connection between devices in...

@mfoltzgoogle Do you mean that we should consider an additional securing mechanism on the top of existing WebSocket protocol, without adopting TLS? I can agree that QUIC/QUARTC would be incompatible...

@pthatcherg Initially, we discussed how to incorporate QUIC (not QUARTC) into WebSocket on HbbTV or ATSC terminals, but we found that need for a certificate is a major blocker. We...

> 4. Implement the "stash" functionality? +1. The reasons are: - Both the controller and the receiver use pre-defined constant UUIDs, which might cause conflict between simultaneous access to stash....

@mfoltzgoogle Though UPnP Device Architecture mentions Transfer-Encoding (as an optional feature for HTTP/1.1), a Transfer-Encoding does not appear in Section 1. Discovery (i.e. SSDP).

@tidoust I tried to check Presentation API on the latest version of Nightly for Android (Fennec), and confirmed that it seems to have both controller and receiver implementation of Presentation...

Do we need messages for J-PAKE authentication before exchanging offer/answer and ICE candidates? I suppose that a device identification step would be essential unless the underlying transport channel could provide...