Re: Last Call: <draft-ietf-urnbis-rfc2141bis-urn-20.txt> (Uniform Resource Names (URNs)) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2/21/17 10:40 AM, John C Klensin wrote:

> How would you
> feel about making the phrase something closer to "the basic
> Latin repertoire, i.e., the letters and digits of ASCII as
> described above" and moving the RFC 20 citation to the first use
> of "ASCII" in that previous paragraph?

OLD

   In order to make URNs as stable and persistent as possible when
   protocols evolve and the environment around them changes, URN
   namespaces SHOULD NOT allow characters outside the basic Latin
   repertoire [RFC20] unless the nature of the particular URN namespace
   makes such characters necessary.

NEW

   In order to make URNs as stable and persistent as possible when
   protocols evolve and the environment around them changes, URN
   namespaces SHOULD NOT allow non-ASCII characters [RFC6365] unless
   the nature of the particular URN namespace makes such characters
   necessary.

The term "non-ASCII" is defined in RFC 6365 and seems perfectly
appropriate here.

Peter




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]