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

Mykyta Yevstifeyev <evnikita2@gmail.com> Thu, 13 January 2011 00:28 UTC

Return-Path: <evnikita2@gmail.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 382133A67B4 for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 16:28:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.321
X-Spam-Level:
X-Spam-Status: No, score=-2.321 tagged_above=-999 required=5 tests=[AWL=-0.682, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_DNSWL_LOW=-1]
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 wCIsJyUjqA8s for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 16:28:19 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id AB9723A67AE for <ietf@ietf.org>; Wed, 12 Jan 2011 16:28:18 -0800 (PST)
Received: by bwz12 with SMTP id 12so1171257bwz.31 for <ietf@ietf.org>; Wed, 12 Jan 2011 16:30:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=vWETLGTvH8uz1HUzKBP05bQHrLh/321SGSBr3s7iqNA=; b=gB7achWM98tFgvxhgRUTaNo1CMA/UAytmf0ehZkqFKYgwI4N0Kzg1fO72Ol3aN315M ygk6mdrhTGAmHd3+CJy2x5nu1jSqcVilvlH5ZUeknIKXFU97Dg75SukGs6bdChvNoq7w Xm2+NsHcUqN7VjgPQ96g+gGdCbUosBLHEOXGw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=gsw/ijEsayAj2q2WS5V8OVg52VTSvScI2nVSuSTwCE7rltS5ORggMIkWLU0u/R1g3+ TgFN7fM434hoaaz1cR/kKBoPs2pyfh6GBazjpcenghhgwZ6ft1CKXGHwW4dVyh7sPI65 6eSRTH9IJUGg2EQVEyX7LVPEkTPdAovaE3nxQ=
Received: by 10.204.81.72 with SMTP id w8mr1272461bkk.205.1294878636167; Wed, 12 Jan 2011 16:30:36 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id j11sm349125bka.12.2011.01.12.16.30.34 (version=SSLv3 cipher=RC4-MD5); Wed, 12 Jan 2011 16:30:34 -0800 (PST)
Message-ID: <4D2E47BD.5040305@gmail.com>
Date: Thu, 13 Jan 2011 02:30:53 +0200
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Donald Eastlake <d3e3e3@gmail.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> <4D2DBC48.2080302@gmx.de> <AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com>
In-Reply-To: <AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Julian Reschke <julian.reschke@gmx.de>, The IETF <ietf@ietf.org>, 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: Thu, 13 Jan 2011 00:28:20 -0000

12.01.2011 22:07, Donald Eastlake wrote:
> Almost all registries I'm familiar with explicitly list unassigned
> ranges. In some cases, different unassigned subranges have different
> allocation policies. For example, there may be a small unassigned
> range of lower values requiring Standards Action with the bulk of the
> unassigned values allocatable on a less stringent basis.
RFC 5226 has an exact rule: Unassigned values shall be mentioned while 
creating registries.

And another (not from 5226): it is RECOMMENDED to explain all 
abbreviation, even well-known once they occur.

I do not know what is the problem here.

Mykyta
> Thanks,
> Donald
> =============================
>   Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>   155 Beaver Street
>   Milford, MA 01757 USA
>   d3e3e3@gmail.com
>
>
>
> On Wed, Jan 12, 2011 at 9:35 AM, Julian Reschke<julian.reschke@gmx.de>  wrote:
>> 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
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>