- From: Takeshi Yoshino <tyoshino@google.com>
- Date: Wed, 15 Nov 2017 19:14:28 +0900
- To: Patrick McManus <mcmanus@ducksong.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
Received on Wednesday, 15 November 2017 10:15:12 UTC
"due to its multiplexing nature" in the introduction section looks redundant. Given that we drop the Sec-WebSocket-Key/Sec-WebSocket-Accept header considering that SETTINGS+:protocol is sufficient to ensure everyone on the path understands WebSockets (tunneling), I suggest that we also drop the client-server frame masking while also allowing masking as optional for LBs that don't want to parse/rebuild frames but forward everything after upgrading.
Received on Wednesday, 15 November 2017 10:15:12 UTC