Re: [hybi] Websockets sub-protocol registry

Julian Reschke <julian.reschke@gmx.de> Tue, 15 March 2016 09:04 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 712D612D92A for <hybi@ietfa.amsl.com>; Tue, 15 Mar 2016 02:04:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.601
X-Spam-Level:
X-Spam-Status: No, score=-1.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K3fkqTOZ4B_U for <hybi@ietfa.amsl.com>; Tue, 15 Mar 2016 02:04:00 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB4BD12D55C for <hybi@ietf.org>; Tue, 15 Mar 2016 02:03:52 -0700 (PDT)
Received: from [192.168.178.20] ([84.187.34.69]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0M8NWM-1ZscHH1esc-00vx7V; Tue, 15 Mar 2016 10:03:49 +0100
To: Takeshi Yoshino <tyoshino@google.com>, Ted Hardie <ted.ietf@gmail.com>
References: <CA+9kkMDZQ_dPM76HaAKwvsRaOhdyvbQd+YLOCTR9piBYO2Kt+w@mail.gmail.com> <CADnb78gBkzjhVRQgzF29hNq4LsCZ=vSu4CJSM9nDWuLVcsOzDw@mail.gmail.com> <CA+9kkMCriEjDrs0Fpb-6QGcuZLWX37xVTBo6wk1Zq9cBSRMTxw@mail.gmail.com> <CADnb78iuJ=F=uhOTfyKx7mnH6wtpN6Pjqa2w2sQ7ZCbdULU_rw@mail.gmail.com> <CA+9kkMA5gHqd9QgfOseowEuFsE=sp8yjcUDa+6A06rQg650Jvw@mail.gmail.com> <56E6E454.7090207@gmx.de> <CA+9kkMCPkZcaM6xF0ctkhnz+Uju0WNj24pJ+-+VUqgkRy0BEjw@mail.gmail.com> <CAH9hSJZqP1xgYM9HEixif+OiLnrOnRD0dDbTaWHO2rkz8b-w2w@mail.gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <56E7CFF3.5010709@gmx.de>
Date: Tue, 15 Mar 2016 10:03:47 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CAH9hSJZqP1xgYM9HEixif+OiLnrOnRD0dDbTaWHO2rkz8b-w2w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:Xr5TkkfQgW1fdHMq9BRq03t1uCnmzLSFlrIHbMvXz31a1mfvPlX NcB3AWe/7kLKbMBetoUAonEeRpgw9zhdN2N4MVXfy4eJUpu+aHjtSNZE4FgJDLGfpoWOIAU x6NKBTpjQhoQVxHowxbzddLZI9+3fezJ4qRIdVVHlcYFiI5DVr1+rTcY8ov3U0E3dcONfwM 8h4g5Fvzc3H0DGyTLGQVg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:Tbv7hjg3+dQ=:pgUN61sH4AmNdIdTQg+5Wo /OIV3c29A5JDUeeIyT8Y3UOzuxRyvKfatkHczCtxx6IBE2Sqf+Ft+j/Nvo1zRn3C3GJd8YH7p ZQ5HUgvSkJ/Ze6hl2F878MqiHADlmLRYtLNcd513MLBaHvmJRlqRe+qsESuYkeTij37b3Tusf g8EEvNxBjsvaObYs+ZGKvwQTELxrkEf6DMTAx30n2qhE/Hk+3PEi9W9ewfQ6KRolTh9GXmfK4 bPJPk5woJf/qe+YmG/CbOxzv7g3RtfR6pmfC2d/H0oBAaEJrfvsD7GaCsuY5o1NyskdERzJLy Pb3kAJh3p6tvdxiSAEB+e7s8eIL0P7sF0QiowmbQPYWdPhuH24W5KBCLRAPKv+RrXTQx7qXZi F1Is9xy9qdcMX9nKYTr2jnKmIABl2mGlg4CIAtkOixxsgf+N41p8u42f3B/avxwJHIASGJiAQ No5abKXjZjC1bTInjh5yhx3nSATvk9d2dO6L2kGbbd8Mu/deqmlrRcBwEFQrynOC7ZlFOU72q sUqRdguuUCg9gxASdBQV50URiCarOdEf5D6viEr3AkJBrvK9Pi/HkF9NdV5kqrkNRB4bWLQja 8zIx7WpvHlo6UzknwJh+P8cyD6VxGCxoEblDwBbl80MQaEIQXJxzvDzGfujslJOs5g8XxnLu0 bg9d93JkZTZPM0VgHlUyER9qBhB/GGV/KLFCHPLjkNgElYvCeWWRgbXh2KHRECisZc9gIa0ae 5TIilALJejMY6Y5bu8b6XKBTEVcjiuF1Xjg305yjJqGj5/Tz95td+srK1FRePLD3sJ689ZUyx yeGdrwxw3qumVyU7YKSNMD1GbSX10+FkKb07TauEhOn6no83YxhIW0mI6Q/B9/wAMESouaQCB vD5x7dkAucgVbsIu595g==
Archived-At: <http://mailarchive.ietf.org/arch/msg/hybi/pbEImRSjhYLsuoVsasYQKv4Z2KQ>
Cc: Server-Initiated HTTP <hybi@ietf.org>
Subject: Re: [hybi] Websockets sub-protocol registry
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hybi/>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2016 09:04:03 -0000

On 2016-03-15 09:52, Takeshi Yoshino wrote:
> On Tue, Mar 15, 2016 at 1:43 AM, Ted Hardie <ted.ietf@gmail.com
> <mailto:ted.ietf@gmail.com>> wrote:
>
>     On Mon, Mar 14, 2016 at 9:18 AM, Julian Reschke
>     <julian.reschke@gmx.de <mailto:julian.reschke@gmx.de>> wrote:
>
>         On 2016-03-14 17:04, Ted Hardie wrote:
>
>             On Mon, Mar 14, 2016 at 8:56 AM, Anne van Kesteren
>             <annevk@annevk.nl <mailto:annevk@annevk.nl>
>             <mailto:annevk@annevk.nl <mailto:annevk@annevk.nl>>> wrote:
>
>                  On Mon, Mar 14, 2016 at 4:01 PM, Ted Hardie
>             <ted.ietf@gmail.com <mailto:ted.ietf@gmail.com>
>                  <mailto:ted.ietf@gmail.com
>             <mailto:ted.ietf@gmail.com>>> wrote:
>                  > We simply don't want to assume it; we'd like it to be
>             specified, at least in
>                  > the RTCWEB case.
>
>                  In the typical use of the word, "a" does not match "A".
>
>
>                  > Back to the IANA side of the question: Any objection
>             to specifying that IANA
>                  > should not register two values that differed only in
>             case?  The current
>                  > instructions aren't clear on that.
>
>                  Why? That would restrict the value space. We don't do
>             that for HTTP
>                  verbs either (although it might make sense there, and
>             require them to
>                  be uppercase).
>
>
>             The IANA registry currently has 23 items in it; restricting
>             the value
>             space does not seem like a current issue.  Basically, you
>             would do it so
>             that confusion in which was meant did not occur in the event
>             that
>             someone did attempt the registration of XMPP (rather than
>             xmpp, which is
>             already registered).   This is a first-come-first-served
>             registry, so
>             there is no one to give helpful advice to registrants on
>             this to avoid;
>             the best we can do is give instructions to IANA.
>
>             regards,
>
>             Ted
>
>
>         The main risk I see is that people could mis-read this as
>         meaning that the values are indeed case-insensitive. Of course
>         that could be mitigated by being crystal clear in the wording.
>
>
>     How would this work:
>
>     "The tokens registered in the Websockets sub-protocol registry
>     created by RFC 6445 Section 11.5 are matched using case-sensitive
>     string match.  IANA is, however, instructed to decline registrations
>     in the registry which differ only as to case, in order to minimize
>     potential confusion among different registered versions.  For other
>     useful advice on avoiding collision, registrants are encourage to
>     consult the non-normative section 1.9 of RFC 6445."
>
>
> Sounds good to me.

+1.

> I agree that there's no normative text specifying what comparison method
> to use.
>
>
> FYI, current status of browsers:
>
> The implementation of the WHATWG WebSocket API on Chromium 49.0.2623.87:
> - validates that the Sec-WebSocket-Protocol header value in the
> handshake response is one of the subprotocols listed in the handshake
> request.
> - Case-sensitive comparison is used for this.
> - When the validation fails, the handshake fails.
>
> The API implemented on Firefox 44.0.2:
> - also validates the value against the list sent in the handshake request.
> - But case-insensitive comparison is used.

...raise a bug report?


 > ...

Best regards, Julian