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

Hello all,

Let me cite RFC 5226, that says:

<...>
Documents that create a new namespace (or modify the definition of an
existing space) and that expect IANA to play a role in maintaining
that space (e.g., serving as a repository for registered values) MUST
provide clear instructions on details of the namespace.  In
particular, instructions *MUST* include:
<...>
5) Initial assignments and reservations.  Clear instructions should be
provided to identify any initial assignments or registrations.  In
addition, any ranges that are to be reserved  for "Private Use",
"Reserved", *"Unassigned"*, etc. should be *clearly indicated*.
<...>

So the document specifying the regsitry MUST mention what are
Unassigned.  Moreover, IMO, it would be useful to assign one value for
Experimentation.

Mykyta

2011/1/13, Julian Reschke <julian.reschke@gmx.de>:
> 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
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>