IETF Logo Mail Archive

Re: Use of "unassigned" in IANA registries

Lars Eggert <lars.eggert@nokia.com> Tue, 18 January 2011 13:59 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 DDB133A6F0F for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 05:59:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.383
X-Spam-Level:
X-Spam-Status: No, score=-104.383 tagged_above=-999 required=5 tests=[AWL=-0.784, 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 TaYCtQ600n5c for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 05:59:46 -0800 (PST)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by core3.amsl.com (Postfix) with ESMTP id 07C453A6F2C for <ietf@ietf.org>; Tue, 18 Jan 2011 05:59:45 -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 p0IE2I6o020635 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jan 2011 16:02:19 +0200
Subject: Re: Use of "unassigned" in IANA registries
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-14--775449584"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <AANLkTinHxBS7h-Y+=9fAoJgR=Az3jqd6c_bD05+K5_Lt@mail.gmail.com>
Date: Tue, 18 Jan 2011 16:02:10 +0200
Message-Id: <9A63E4EE-0847-43A6-BBAC-5D47E63038B4@nokia.com>
References: <201101142206.p0EM6XNB027935@fs4113.wdf.sap.corp> <06456B13-F9E5-4530-B7E8-7CF7F41000E0@muada.com> <AANLkTiksCOABzGAVqrHQzpbyROhMPVR65zsuGVe=Q6Wg@mail.gmail.com> <27DB0613-457D-4B99-89B4-D13DC2D7232E@nokia.com> <AANLkTinHxBS7h-Y+=9fAoJgR=Az3jqd6c_bD05+K5_Lt@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1082)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mail.fit.nokia.com); Tue, 18 Jan 2011 16:02:15 +0200 (EET)
X-Nokia-AV: Clean
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, paul.hoffman@vpnc.org, 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: Tue, 18 Jan 2011 13:59:47 -0000

Hi,

On 2011-1-18, at 15:51, Phillip Hallam-Baker wrote:
> >Using a term other than "unassigned" might prevent some instances of the latter.
> 
> I don't see how changing the name is going to affect behavior for the positive here. If you do succeed in confusing people as to which numbers are unassigned and which are not it is going to increase the risk of a collision.

huh? The purpose here is to make it *clearer* that assignment is needed.

> If five people are experimenting with TCP options and this is not causing collisions, what is the problem?

Have you read my original email? It *is* going to cause collisions.

Lars

v2.23.0 | Report a Bug | By Email