Re: [hybi] -09: IANA considerations

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 07 July 2011 18:42 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 D2D4821F867A for <hybi@ietfa.amsl.com>; Thu, 7 Jul 2011 11:42:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3T+lYzNUFiSO for <hybi@ietfa.amsl.com>; Thu, 7 Jul 2011 11:42:00 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id D0CBB21F8678 for <hybi@ietf.org>; Thu, 7 Jul 2011 11:41:58 -0700 (PDT)
Received: from [188.28.132.132] (188.28.132.132.threembb.co.uk [188.28.132.132]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <ThX98wB=gAY-@rufus.isode.com>; Thu, 7 Jul 2011 19:41:56 +0100
Message-ID: <4E15FDCF.7020803@isode.com>
Date: Thu, 07 Jul 2011 19:41:19 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Peter Saint-Andre <stpeter@stpeter.im>
References: <4DFB8E07.60908@stpeter.im>
In-Reply-To: <4DFB8E07.60908@stpeter.im>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] -09: IANA considerations
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 07 Jul 2011 18:42:00 -0000

Peter Saint-Andre wrote:
 [...]

>Sections 11. and 11.2 both say:
>
>   Interoperability considerations.
>      None.
>
>However, the template in RFC 4395 says:
>
>   Interoperability considerations.
>      If you are aware of any details regarding your scheme that might
>      impact interoperability, please identify them here.  For example:
>      proprietary or uncommon encoding method; inability to support
>      multibyte character sets; incompatibility with types or versions
>      of any underlying protocol.
>
>Now, Section 5.1 of the WebSocket spec says:
>
>   2.   The Method of the request MUST be GET and the HTTP version MUST
>        be at least 1.1.
>
>So it seems that the interoperability considerations of our URI
>registration requests might need to say something about incompability
>with HTTP 1.0.
>  
>
I've replaced "None" with "Use of WebSocket requires use of HTTP version 
1.1 or higher.". I hope this is sufficient.

>Section 11.6 mentions private use tokens beginning with "x-". Ick. :)
>  
>
I think this is still a debate to have in the Apps Area meeting in 
Quebec ;-).

>Typo in Section 11.10: "Paragraph 10 of Paragraph 4 of Section 5.1 "
>  
>
I've removed "of Paragraph 4", as I think the Paragraph 10 of Section 
5.1 is the correct reference.

>Section 11.12 says that assignment of WebSocket Version Numbers shall be
>"RFC Required", but then requests assignment of version numbers 0-8 to
>prior submissions of this Internet-Draft. The requested assignments are
>at odds with the stated policy.
>
I am not entirely sure that RFC Required prevents what the document 
does, but in order to clarify I've added:

      In order to improve interoperability with intermediate versions
      published in Internet Drafts, version numbers associated with such 
drafts
      might be registered in this registry.