draft-ietf-urn-syntax-03.txt   draft-ietf-urn-syntax-04.txt 
Internet-Draft Ryan Moats Internet-Draft Ryan Moats
draft-ietf-urn-syntax-03.txt AT&T draft-ietf-urn-syntax-04.txt AT&T
URN Syntax URN Syntax
Filename: draft-ietf-urn-syntax-03.txt Filename: draft-ietf-urn-syntax-04.txt
Status of This Memo Status of This Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts. distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
skipping to change at page 3, line 36 skipping to change at page 3, line 36
<other> ::= "(" | ")" | "+" | "," | "-" | "." | <other> ::= "(" | ")" | "+" | "," | "-" | "." |
":" | "=" | "@" | ";" | "$" | ":" | "=" | "@" | ";" | "$" |
"_" | "!" | "*" | "'" "_" | "!" | "*" | "'"
Depending on the rules governing a namespace, valid identifiers in a Depending on the rules governing a namespace, valid identifiers in a
namespace might contain characters that are not members of the URN namespace might contain characters that are not members of the URN
character set above (<URN chars>). Such strings MUST be translated character set above (<URN chars>). Such strings MUST be translated
into canonical NSS format before using them as protocol elements or into canonical NSS format before using them as protocol elements or
otherwise passing them on to other applications. Translation is done otherwise passing them on to other applications. Translation is done
by encoding each character outside the URN character set as a by encoding each character outside the URN character set as a
sequence of one to six octets using UTF-8 encoding, and the encoding sequence of one to six octets using UTF-8 encoding [5], and the
of each of those octets as "%" followed by two characters from the encoding of each of those octets as "%" followed by two characters
<hex> character set above. The two characters give the hexadecimal from the <hex> character set above. The two characters give the
representation of that octet. hexadecimal representation of that octet.
2.3 Reserved characters 2.3 Reserved characters
The remaining character set left to be discussed above is the The remaining character set left to be discussed above is the
reserved character set, which contains various characters reserved reserved character set, which contains various characters reserved
from normal use. The reserved character set follows, with a from normal use. The reserved character set follows, with a
discussion on the specifics of why each character is reserved. discussion on the specifics of why each character is reserved.
The reserved character set is: The reserved character set is:
skipping to change at page 6, line 30 skipping to change at page 6, line 30
This document specifies the syntax for URNs. While some namespaces This document specifies the syntax for URNs. While some namespaces
resolvers may assign special meaning to certain of the characters of resolvers may assign special meaning to certain of the characters of
the Namespace Specific String, any security consideration resulting the Namespace Specific String, any security consideration resulting
from such assignment are outside the scope of this document. It is from such assignment are outside the scope of this document. It is
strongly recommended that the process of registering a namespace strongly recommended that the process of registering a namespace
identifier include any such considerations. identifier include any such considerations.
9. Acknowledgments 9. Acknowledgments
Thanks to various members of the URN working group and <<your name Thanks to various members of the URN working group for comments on
here!!>> for comments on earlier drafts of this document. This earlier drafts of this document. This document is partially
document is partially supported by the National Science Foundation, supported by the National Science Foundation, Cooperative Agreement
Cooperative Agreement NCR-9218179. NCR-9218179.
10. References 10. References
Request For Comments (RFC) and Internet Draft documents are available Request For Comments (RFC) and Internet Draft documents are available
from <URL:ftp://ftp.internic.net> and numerous mirror sites. from <URL:ftp://ftp.internic.net> and numerous mirror sites.
[1] K. R. Sollins, "Requirements and a Framework for [1] K. R. Sollins, "Requirements and a Framework for
URN Resolution Systems," Internet Draft (work in URN Resolution Systems," Internet Draft (work in
progress), November 1996. progress), November 1996.
[2] [2] T. Berners-Lee, "Universal Resource Identifiers in
T. Berners-Lee, "Universal Resource Identifiers in WWW," RFC WWW," RFC 1630, June 1994.
1630, June 1994.
[3] K. Sollins and L. Masinter, "Functional Require- [3] K. Sollins and L. Masinter, "Functional Require-
ments for Uniform Resource Names," RFC 1737. ments for Uniform Resource Names," RFC 1737.
December 1994. December 1994.
[4] T. Berners-Lee, R. Fielding, L. Masinter, "Uniform [4] T. Berners-Lee, R. Fielding, L. Masinter, "Uniform
Resource Locators (URL)," Internet Draft (work in Resource Locators (URL)," Internet Draft (work in
progress), December 1996. progress), December 1996.
[5] Appendix A.2 of The Unicode Consortium, "The
Unicode Standard, Version 2.0", Addison-Wesley
Developers Press, 1996. ISBN 0-201-48345-9.
11. Editor's address 11. Editor's address
Ryan Moats Ryan Moats
AT&T AT&T
15621 Drexel Circle 15621 Drexel Circle
Omaha, NE 68135-2358 Omaha, NE 68135-2358
USA USA
Phone: +1 402 894-9456 Phone: +1 402 894-9456
EMail: jayhawk@ds.internic.net EMail: jayhawk@ds.internic.net
 End of changes. 7 change blocks. 
14 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/