- From: Alexey Melnikov <alexey.melnikov@isode.com>
- Date: Thu, 30 Aug 2018 11:09:58 +0100
- To: Mark Nottingham <mnot@mnot.net>, Patrick McManus <mcmanus@ducksong.com>
- Cc: Mike Bishop <mbishop@evequefou.be>, "Julian F. Reschke" <julian.reschke@gmx.de>, HTTP Working Group <ietf-http-wg@w3.org>
On Thu, Aug 30, 2018, at 1:22 AM, Mark Nottingham wrote: > > > On 30 Aug 2018, at 3:46 am, Patrick McManus <mcmanus@ducksong.com> wrote: > > > >> Personally, I really wonder if existing implementations have seen enough deployment to preclude just changing the value. > > > > the 6455 implementations all (to some close approximation of all) use lower case websocket.. the new protocol is just matching reality. let's not double down on the registry problem in the new protocol. > > Ah, I forgot about that. > > It sounds like we need to: > - register 'websocket' pointing to 6455 > - file an errata on 6455 recommending using that for interop, but noting > that some might send other casings of the token > - perhaps modify the registry entry for "WebSocket" noting that it's not > the preferred protocol artefact / historic / whatever > > Alexey? Sounds like a good plan!
Received on Thursday, 30 August 2018 10:10:21 UTC