Re: [hybi] -09: IANA considerations

Dave Cridland <dave@cridland.net> Tue, 21 June 2011 12:30 UTC

Return-Path: <dave@cridland.net>
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 BF0A211E807A for <hybi@ietfa.amsl.com>; Tue, 21 Jun 2011 05:30:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level:
X-Spam-Status: No, score=-2.197 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 z+tCvQ1us1I0 for <hybi@ietfa.amsl.com>; Tue, 21 Jun 2011 05:30:33 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [IPv6:2001:470:1f09:882:2e0:81ff:fe29:d16a]) by ietfa.amsl.com (Postfix) with ESMTP id E20A311E8079 for <hybi@ietf.org>; Tue, 21 Jun 2011 05:30:32 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 6221D1168087; Tue, 21 Jun 2011 13:30:29 +0100 (BST)
X-Virus-Scanned: Debian amavisd-new at peirce.dave.cridland.net
Received: from peirce.dave.cridland.net ([127.0.0.1]) by localhost (peirce.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NFiouRMHu5v6; Tue, 21 Jun 2011 13:30:26 +0100 (BST)
Received: from puncture (puncture.dave.cridland.net [IPv6:2001:470:1f09:882:221:85ff:fe3f:1696]) by peirce.dave.cridland.net (Postfix) with ESMTPA id 5018F1168067; Tue, 21 Jun 2011 13:30:26 +0100 (BST)
References: <4DFB8E07.60908@stpeter.im> <BANLkTi=6_1H_cTTXRh00v1LM=E_1LUCq9g@mail.gmail.com>
In-Reply-To: <BANLkTi=6_1H_cTTXRh00v1LM=E_1LUCq9g@mail.gmail.com>
MIME-Version: 1.0
Message-Id: <4898.1308659426.327742@puncture>
Date: Tue, 21 Jun 2011 13:30:26 +0100
From: Dave Cridland <dave@cridland.net>
To: =?UTF-8?B?SWFuIEZldHRlICjjgqTjgqLjg7Pjg5Xjgqfjg4Pjg4bjgqMp?= <ifette@google.com>, Server-Initiated HTTP <hybi@ietf.org>, Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: text/plain; delsp="yes"; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8Bit
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: Tue, 21 Jun 2011 12:30:33 -0000

On Fri Jun 17 21:07:22 2011, Ian Fette (イアンフェッティ)  
wrote:
> On Fri, Jun 17, 2011 at 10:25 AM, Peter Saint-Andre  
> <stpeter@stpeter.im>wrote;wrote:
> > 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.
> >
> 
> RFC Required is different from Standards Action. RFC Publication  
> (either as
> an IETF submission or as an RFC editor independent submission)  
> suffices.
> Standards Action requires Standards Track RFCs approved by the  
> IESG. My
> understanding from this as that an I-D counts as an IETF submission?

Yes, but it only counts as an RFC once it's published...

The solution is to assign these to this document, but note in this  
section that versions 1-8 are older versions.

One might even ask IANA to maintain a note saying that, when creating  
the registry.

That all said, it's not clear to me this really needs a registry, or  
why one might want to allow independant stream RFCs to define a new  
version number - that effectively means that the next version of  
WebSockets might not be an IETF protocol at all. In contrast with the  
other registries - which seem reasonable - allowing random people to  
invent new and conflicting versions seems like a recipe for chaos.

I'd have thought that we want standards-track here, and in any case,  
the version numbers would be handled by Obsoletes/Updates perfectly  
well.

Am I missing something?

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade