Re: Last Call: <draft-ishikawa-yrpunl-ucode-urn-01.txt> (A URN Namespace For The ucode) to Informational RFC

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

 



On 2012-01-17 19:27, Mykyta Yevstifeyev wrote:
Hello,

Having reviewed this document, I think there is no problem with its
publication.  Several tiny comments:

1) "RFID" in the Introduction needs expanding at first use.

2)   ucode-value = 32hex-decimal
    hex-decimal = "0" / "1" / "2" / "3" / "4" / "5" / "6" / "7" /
                  "8" / "9" / "A" / "B" / "C" / "D" / "E" / "F"

may be changed to:

    ucode-value = 32HEXDIG

and that's RFC 5234 which defines<HEXDIG>  so you may refer to it later.

3)

Rules for lexical equivalence:

    The entire UCODE-URN is case-sensitive.

This is at least wrong for the first three chars in URN (the URI
scheme name "urn"), that is case-insensitive as per RFC 3986.  What's
the reason for setting such regulation?
...

What's case-sensitive depends on context; for instance, when comparing XML namespace URIs or Atom IDs, everything is case-sensitive. See also <http://greenbytes.de/tech/webdav/rfc3986.html#rfc.section.6.2>.

Best regards, Julian
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf


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