Re: [hybi] Websockets sub-protocol registry

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 21 March 2016 18:33 UTC

Return-Path: <alexey.melnikov@isode.com>
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 6209212D7DF for <hybi@ietfa.amsl.com>; Mon, 21 Mar 2016 11:33:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
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 GWznfMRoDFgf for <hybi@ietfa.amsl.com>; Mon, 21 Mar 2016 11:33:39 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 13E8312D8B5 for <hybi@ietf.org>; Mon, 21 Mar 2016 11:33:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1458585217; d=isode.com; s=selector; i=@isode.com; bh=NWeDBV6HxR7M0n2qvUGsPamRh8KdoOw5X4KVU/Xe3Us=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=L2q7KoQriHArYsECyhq3sQw42MvHYKdzq0KLvpOBdJQt8rT+Ddv00CAGTcadIcuJaskaJp 8CJCb82iaoGCLnES9053nuOWZc3tBwGs8F7enBtdPi6QNMl6osQyIuh2D1AxIyBUs3PMG2 hQUWxSarUR9Pqn9RWDsgyDrs+PPOab8=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <VvA-gAB25l5H@statler.isode.com>; Mon, 21 Mar 2016 18:33:36 +0000
To: 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> <56EC0A26.1070107@isode.com> <CA+9kkMAeJ7g_vizZwWnAXCeEA19DksEOhAOfzo14XM8uPMpgwg@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <56F03E3D.1010405@isode.com>
Date: Mon, 21 Mar 2016 18:32:29 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
In-Reply-To: <CA+9kkMAeJ7g_vizZwWnAXCeEA19DksEOhAOfzo14XM8uPMpgwg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------010706040701070705020008"
Archived-At: <http://mailarchive.ietf.org/arch/msg/hybi/o71g9oUuJyAmgLhjnEHayfPfhLw>
Cc: Julian Reschke <julian.reschke@gmx.de>, 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: Mon, 21 Mar 2016 18:33:42 -0000

On 21/03/2016 15:54, Ted Hardie wrote:
> On Fri, Mar 18, 2016 at 7:01 AM, Alexey Melnikov 
> <alexey.melnikov@isode.com <mailto:alexey.melnikov@isode.com>> wrote:
>
>     Hi Ted,
>
>
>
>     We can either put that in the RTCWEB draft, a short draft updating
>     just the registration portion of RFC 6445,
>     I slightly prefer the latter, but the former would be Ok.
>
>
> There's a 00 shot at this in 
> https://datatracker.ietf.org/doc/draft-hardie-rfc6455-iana-clarification/ 
> .
>
> I'm not sure what status to aim it at; BCP is probably wrong, but also 
> easy to fix.  Suggestions for that or other changes welcome.

2.  Clarified instructions

    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 encouraged to consult
    the non-normative section 1.9 of RFC 6445.

6445 --> 6455. But otherwise this looks good.
>
> Ted
>
>>     or possibly even in an accepted erratum.
>     We can do that as well. Although I would rather the erratum not
>     being the only source of information on this.
>>     If it were an accepted erratum for RFC 6445, we would likely
>>     still want to include something in the RTCWEB docs noting that
>>     those were the rules (but not having that doc update the RFC.)
>>
>>     Any thoughts on that approach?
>
>