IETF Logo Mail Archive

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

Julian Reschke <julian.reschke@gmx.de> Thu, 13 January 2011 08:00 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 4F3E23A6AB3 for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 00:00:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.075
X-Spam-Level:
X-Spam-Status: No, score=-104.075 tagged_above=-999 required=5 tests=[AWL=-1.476, 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 0HNebEDYt3EH for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 00:00:15 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id D7E873A6A99 for <ietf@ietf.org>; Thu, 13 Jan 2011 00:00:14 -0800 (PST)
Received: (qmail invoked by alias); 13 Jan 2011 08:02:35 -0000
Received: from p508FA62D.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.166.45] by mail.gmx.net (mp055) with SMTP; 13 Jan 2011 09:02:35 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18kwBN+do4kvFSHXfYqFdrPxN1kgyaYHU3f11313b MT9+2CMNvmVaEY
Message-ID: <4D2EB195.60604@gmx.de>
Date: Thu, 13 Jan 2011 09:02:29 +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: Doug Ewell <doug@ewellic.org>
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> <4D2DBC48.2080302@gmx.de> <AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com> <0FCCAC8F1FBB48FDA5A5C347233271AA@DougEwell>
In-Reply-To: <0FCCAC8F1FBB48FDA5A5C347233271AA@DougEwell>
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>
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: Thu, 13 Jan 2011 08:00:16 -0000

On 13.01.2011 03:56, Doug Ewell wrote:
> Donald Eastlake wrote:
>
>> Almost all registries I'm familiar with explicitly list unassigned
>> ranges.
>
> The IANA Language Subtag Registry doesn't:
>
> http://www.iana.org/assignments/language-subtag-registry

Obviously it depends on the datatype whether saying what's unassigned is 
useful or feasible.

Back to ma point: for registries where it *can* be done, the unassigned 
values can be *computed*. Thus, they shouldn't be part of the registry 
data, but simply be displayed as such. That would ensure that the 
information always is up-to-date.

Best regards, Julian

v2.23.0 | Report a Bug | By Email