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

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).
--Michelle

On 1/12/11 6: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