RE: Last Call on draft-ietf-pim-registry-03.txt
"Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com> Fri, 14 January 2011 09:56 UTC
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 917993A6AC9 for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 01:56:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.166
X-Spam-Level:
X-Spam-Status: No, score=-6.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2F3jnWyIX1L9 for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 01:56:53 -0800 (PST)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by core3.amsl.com (Postfix) with ESMTP id 660D63A6A0D for <ietf@ietf.org>; Fri, 14 Jan 2011 01:56:53 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.60,322,1291593600"; d="scan'208";a="109865598"
Received: from unknown (HELO baemasodc004.greenlnk.net) ([10.108.36.11]) by Baemasodc001ir.sharelnk.net with ESMTP; 14 Jan 2011 09:59:16 +0000
Received: from glkms1103.GREENLNK.NET (glkms1103.greenlnk.net [10.108.36.194]) by baemasodc004.greenlnk.net (Switch-3.4.3/Switch-3.4.3) with ESMTP id p0E9xCt4002049; Fri, 14 Jan 2011 09:59:15 GMT
Received: from GLKMS2100.GREENLNK.NET ([10.15.184.93]) by glkms1103.GREENLNK.NET with Microsoft SMTPSVC(6.0.3790.4675); Fri, 14 Jan 2011 09:59:14 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: Last Call on draft-ietf-pim-registry-03.txt
Date: Fri, 14 Jan 2011 09:59:09 -0000
Message-ID: <ABE739C5ADAC9A41ACCC72DF366B719D03D0AC20@GLKMS2100.GREENLNK.NET>
In-Reply-To: <D21961EC-F70B-48EA-B0DE-C94110EA80E1@nokia.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Last Call on draft-ietf-pim-registry-03.txt
Thread-Index: AcuzxMIqW2bzSWLIRVa9l9c6psZvtgAC7TRA
References: <C954A3DF.2B01C%michelle.cotton@icann.org> <D21961EC-F70B-48EA-B0DE-C94110EA80E1@nokia.com>
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: Lars Eggert <lars.eggert@nokia.com>, Michelle Cotton <michelle.cotton@icann.org>
X-OriginalArrivalTime: 14 Jan 2011 09:59:14.0594 (UTC) FILETIME=[B32F2820:01CBB3D1]
Cc: Julian Reschke <julian.reschke@gmx.de>, The IETF <ietf@ietf.org>, Adrian Farrel <adrian.farrel@huawei.com>, stig@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jan 2011 09:56:54 -0000
RFC 5226 (BCP 26) says IANA must be given a set of guidelines that allow it to make allocation decisions with minimal subjectivity and without requiring any technical expertise with respect to the protocols that make use of a registry. and goes on to discuss categories of unassigned code points (though it does also define the unqualified word Unassigned). We were thus advised, when publishing RFC 5444, to specify this clearly and so we had tables such as +---------+-----------------------+------------------------+ | Type | Description | Allocation Policy | +---------+-----------------------+------------------------+ | 0-127 | Unassigned | Expert Review | | 128-223 | Message-Type-specific | Reserved, see Table 11 | | 224-255 | Unassigned | Experimental Use | +---------+-----------------------+------------------------+ (For the purposes of this discussion I suggest ignoring the 128 to 223 line above.) This seemed to keep everyone (IESG, IANA, RFC Editor) happy. -- Christopher Dearlove Technology Leader, Communications Group Communications and Networks Capability BAE Systems Advanced Technology Centre West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK Tel: +44 1245 242194 Fax: +44 1245 242124 BAE Systems (Operations) Limited Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK Registered in England & Wales No: 1996687 -----Original Message----- From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Lars Eggert Sent: 14 January 2011 08:23 To: Michelle Cotton Cc: Julian Reschke; stig@cisco.com; Adrian Farrel; 'The IETF' Subject: Re: Last Call on draft-ietf-pim-registry-03.txt Hi, On 2011-1-13, at 22:43, Michelle Cotton wrote: > Many believe it makes it very clear to the users of the registry what is > available for assignment. Something we will be rolling out soon (for those > registries with a finite space) will be small charts showing how much of the > registry space is unassigned, assigned and reserved (utilizing the > unassigned entries). I mentioned in the past that the term "unassigned" to me at least doesn't make it sufficiently clear that IANA assignment is often needed before codepoints may be taken into use. We have several cases (the many different squats on TCP option numbers, for example) were people pick unassigned codepoints during development and only later realize that they should have registered them. If you want to explicitly list unassigned codepoints in the registries, I'm wondering if we can find a short phrase that makes it more clear that an IANA action is normally required - maybe "available for IANA assignment"? Lars ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ********************************************************************
- Re: Last Call on draft-ietf-pim-registry-03.txt Stig Venaas
- Re: Last Call on draft-ietf-pim-registry-03.txt Julian Reschke
- Last Call on draft-ietf-pim-registry-03.txt Mykyta Yevstifeyev
- RE: Last Call on draft-ietf-pim-registry-03.txt Adrian Farrel
- Re: Last Call on draft-ietf-pim-registry-03.txt Julian Reschke
- RE: Last Call on draft-ietf-pim-registry-03.txt Adrian Farrel
- Re: Last Call on draft-ietf-pim-registry-03.txt Donald Eastlake
- Re: Last Call on draft-ietf-pim-registry-03.txt Mykyta Yevstifeyev
- Re: Last Call on draft-ietf-pim-registry-03.txt Doug Ewell
- Re: Last Call on draft-ietf-pim-registry-03.txt Julian Reschke
- Re: Last Call on draft-ietf-pim-registry-03.txt Mykyta Yevstifeyev
- Re: Last Call on draft-ietf-pim-registry-03.txt Julian Reschke
- Re: Last Call on draft-ietf-pim-registry-03.txt Mykyta Yevstifeyev
- Re: Last Call on draft-ietf-pim-registry-03.txt Julian Reschke
- Re: Last Call on draft-ietf-pim-registry-03.txt Mykyta Yevstifeyev
- Re: Last Call on draft-ietf-pim-registry-03.txt Julian Reschke
- Re: Last Call on draft-ietf-pim-registry-03.txt Mykyta Yevstifeyev
- Re: Last Call on draft-ietf-pim-registry-03.txt Julian Reschke
- Re: Last Call on draft-ietf-pim-registry-03.txt Michelle Cotton
- Re: Last Call on draft-ietf-pim-registry-03.txt Julian Reschke
- Re: Last Call on draft-ietf-pim-registry-03.txt Lars Eggert
- RE: Last Call on draft-ietf-pim-registry-03.txt Dearlove, Christopher (UK)
- Re: Last Call on draft-ietf-pim-registry-03.txt Mykyta Yevstifeyev
- Re: Last Call on draft-ietf-pim-registry-03.txt Julian Reschke
- Use of "unassigned" in IANA registries Paul Hoffman
- Re: Use of "unassigned" in IANA registries Iljitsch van Beijnum
- Re: Use of "unassigned" in IANA registries Phillip Hallam-Baker
- Re: Use of "unassigned" in IANA registries Paul Wouters
- Re: Use of "unassigned" in IANA registries Martin Rex
- Re: Last Call on draft-ietf-pim-registry-03.txt Mykyta Yevstifeyev
- Re: Use of "unassigned" in IANA registries Phillip Hallam-Baker
- Re: Use of "unassigned" in IANA registries Phillip Hallam-Baker
- Re: Use of "unassigned" in IANA registries Mykyta Yevstifeyev
- Re: Use of "unassigned" in IANA registries Julian Reschke
- Re: Use of "unassigned" in IANA registries Lars Eggert
- Re: Use of "unassigned" in IANA registries Phillip Hallam-Baker
- Re: Use of "unassigned" in IANA registries Spencer Dawkins
- Re: Use of "unassigned" in IANA registries Lars Eggert
- Re: Use of "unassigned" in IANA registries Lars Eggert
- Re: Use of "unassigned" in IANA registries Phillip Hallam-Baker
- Re: Use of "unassigned" in IANA registries Lars Eggert
- Re: Use of "unassigned" in IANA registries Eric Rosen
- Re: Use of "unassigned" in IANA registries Lars Eggert
- Re: Use of "unassigned" in IANA registries Martin Rex
- Re: Use of "unassigned" in IANA registries t.petch
- Re: Use of "unassigned" in IANA registries Phillip Hallam-Baker
- Re: Use of "unassigned" in IANA registries t.petch
- Re: Last Call on draft-ietf-pim-registry-03.txt Stig Venaas
- Re: Last Call on draft-ietf-pim-registry-03.txt Mykyta Yevstifeyev