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

Julian Reschke <julian.reschke@gmx.de> Wed, 12 January 2011 14:33 UTC

Return-Path: <julian.reschke@gmx.de>
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 9CF743A6B30 for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 06:33:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.22
X-Spam-Level:
X-Spam-Status: No, score=-104.22 tagged_above=-999 required=5 tests=[AWL=-1.621, BAYES_00=-2.599, 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 AUgg8F8cnsRE for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 06:33:39 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id D003228C0E8 for <ietf@ietf.org>; Wed, 12 Jan 2011 06:33:37 -0800 (PST)
Received: (qmail invoked by alias); 12 Jan 2011 14:35:56 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.133]) [217.91.35.233] by mail.gmx.net (mp059) with SMTP; 12 Jan 2011 15:35:56 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1++8wsqmxm+v8HXNbz0qzLaSesyKY2sutJ11BhkpV ZYs9KpOPol0jLw
Message-ID: <4D2DBC48.2080302@gmx.de>
Date: Wed, 12 Jan 2011 15:35:52 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Adrian.Farrel@huawei.com
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com> <01bc01cbb25c$41590700$c40b1500$@huawei.com> <4D2DB36C.7070107@gmx.de> <01da01cbb264$2f1462d0$8d3d2870$@huawei.com>
In-Reply-To: <01da01cbb264$2f1462d0$8d3d2870$@huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: 'The IETF' <ietf@ietf.org>, 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: Wed, 12 Jan 2011 14:33:40 -0000

On 12.01.2011 15:22, Adrian Farrel wrote:
> Entirely at random I clicked on:
>
> http://www.iana.org/assignments/aaa-parameters/aaa-parameters.xhtml
> http://www.iana.org/assignments/calipso/calipso.xhtml
> http://www.iana.org/assignments/lmp-parameters
>
> Looks like IANA tries to fill up all the blanks with markers of "unassigned".
>
> Is that harmful?

Minimally, it's redundant. Also, it only makes sense on certain types of 
registries.

I just checked the XML version of the first registry, and, indeed, it 
contains entries for unassigned values. /me shakes head in disbelief.

What *should* be done is computing the unassigned ranges for 
*presentation*; that is, they should not be part of the actual registry. 
The way it's done currently defeats one of the reasons of having a 
machine-readable registry (consumers will have to hard-wire knowledge of 
the specific "unassigned" entry to make sense of the registry).

Best regards, Julian