On 14.01.2011 15:04, Mykyta Yevstifeyev wrote:
13.01.2011 18:19, Julian Reschke wrote:
On 13.01.2011 17:14, Mykyta Yevstifeyev wrote:
<...>
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*.
<...>
Yes.
There's still no "MUST" applying to unassigned code points. Note the
"In addition" and "should".
There is MUST before the list of the criteria for the documents defining
the registry. This MUST applies to everything mentioned in this list.
...
Well, we can go on repeating this exchange over and over, or just stop.
I'll stop.
Best regards, Julian
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf