IETF Logo Mail Archive

Re: Last Call on draft-ietf-pim-registry-03.txt

Lars Eggert <lars.eggert@nokia.com> Fri, 14 January 2011 08:24 UTC

Return-Path: <lars.eggert@nokia.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 D9A073A6ABD for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 00:24:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.729
X-Spam-Level:
X-Spam-Status: No, score=-104.729 tagged_above=-999 required=5 tests=[AWL=-1.130, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 MSgXLlPyWzuA for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 00:24:02 -0800 (PST)
Received: from mgw-da01.nokia.com (mgw-da01.ext.nokia.com [147.243.128.24]) by core3.amsl.com (Postfix) with ESMTP id EC69B3A6AB9 for <ietf@ietf.org>; Fri, 14 Jan 2011 00:24:01 -0800 (PST)
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-da01.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p0E8NY2I010232 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Jan 2011 10:23:36 +0200
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.96.5 at fit.nokia.com
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/signed; boundary="Apple-Mail-19-1006110016"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <C954A3DF.2B01C%michelle.cotton@icann.org>
Date: Fri, 14 Jan 2011 10:23:26 +0200
Message-Id: <D21961EC-F70B-48EA-B0DE-C94110EA80E1@nokia.com>
References: <C954A3DF.2B01C%michelle.cotton@icann.org>
To: Michelle Cotton <michelle.cotton@icann.org>
X-Mailer: Apple Mail (2.1082)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mail.fit.nokia.com); Fri, 14 Jan 2011 10:23:31 +0200 (EET)
X-Nokia-AV: Clean
Cc: Julian Reschke <julian.reschke@gmx.de>, "stig@cisco.com" <stig@cisco.com>, Adrian Farrel <adrian.farrel@huawei.com>, 'The IETF' <ietf@ietf.org>
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 08:24:02 -0000

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

v2.23.0 | Report a Bug | By Email