draft-ietf-urn-ietf-00.txt   draft-ietf-urn-ietf-01.txt 
Internet-Draft Ryan Moats Internet-Draft Ryan Moats
draft-ietf-urn-ietf-00.txt AT&T draft-ietf-urn-ietf-01.txt AT&T
URN Namespace for RFC series documents A URN Namespace for IETF Documents
Filename: draft-ietf-urn-ietf-00.txt Filename: draft-ietf-urn-ietf-01.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 1, line 34 skipping to change at page 1, line 34
(Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East
Coast), or ftp.isi.edu (US West Coast). Coast), or ftp.isi.edu (US West Coast).
Abstract Abstract
A system for Uniform Resource Names (URNs) must be capable of A system for Uniform Resource Names (URNs) must be capable of
supporting new naming systems. As an example of the sort of supporting new naming systems. As an example of the sort of
information that needs to be supplied when proposing new namepsaces, information that needs to be supplied when proposing new namepsaces,
this document presents a naming system based on the RFC family of this document presents a naming system based on the RFC family of
documents (RFCs, STDs, and FYIs) developed by the IETF and published documents (RFCs, STDs, and FYIs) developed by the IETF and published
by the RFC editor. This namespace can be supported within the URN by the RFC editor and the minutes of working groups (WG) and birds of
framework and the currently proposed syntax for URNs. a feather (BOF) meetings that occur during IETF conferences. This
namespace can be supported within the URN framework and the currently
0. Document History and Status proposed syntax for URNs.
With the first draft of this document, the only issue that has
occured on the list is the discussion on functional equivalence for
this namespace (see section 1.5). There are currently two positions
on this: the first is what is specified here, and the second is that
there is no equivalency for this namespace, e.g. a resolver receiving
a request must return ONLY the resource named by that request.
1. Namespace Syntax 1. Namespace Syntax
Consistent with the URN syntax specification [1], each namespace must Consistent with the URN syntax specification [1], each namespace must
specify syntax related information that is specific to that specify syntax related information that is specific to that
namespace. This section covers these specifications. namespace. This section covers these specifications.
1.1. Namespace Identifier (NID) 1.1. Namespace Identifier (NID)
The namespace identifier for this namespace is "ietf". The namespace identifier for this namespace is "ietf".
1.2. Namespace Specific String (NSS) 1.2. Namespace Specific String (NSS)
The Namespace Specific String has the following ABNF [2] The Namespace Specific String has the following ABNF [2]
specification: specification:
NSS = family ":" number NSS = (family ":" number) / ("mtg-" number "-" wgbofname)
family = "rfc" | "std" | "fyi" family = "rfc" / "std" / "fyi"
number = 1*DIGIT number = 1*DIGIT
wgbofname = 1*LETDIGIT
LETDIGIT = DIGIT / %x41..%x5a / %x61..%x7a
DIGIT = %x30..%x39 DIGIT = %x30..%x39
The ABNF specification for "family" above is based on the current The ABNF specification for "family" is based on the current documents
documents in the RFC family. As new document series are added to the in the RFC family. As new document series are added to the IETF
IETF family by the IESG (or its successor), this ABNF specification family by the IESG (or its successor), this ABNF specification will
will need to be updated. Any system intended to resolve names for need to be updated. Any system intended to resolve names for this
this namespace should be written with the awareness that a new namespace should be written with the awareness that a new document
document series may be introduced at any time. series may be introduced at any time.
The ABNF specification for "wgbofname" is based on the current and
past abbreviations for working groups and BOFs in the IETF. If a
working group or BOF is created that used characters outside the
range of this ABNF specification, this specification will need to be
update. Any system intended to resolve names for this namespace
should be written with the awareness that this could occur at any
time.
1.3. Additional Reserved Characters 1.3. Additional Reserved Characters
No characters in addition to those specified in [1] are reserved by No characters in addition to those specified in [1] are reserved by
this namespace. this namespace.
1.4. Additional Lexical Equivalence Relations 1.4. Additional Lexical Equivalence Relations
Note that the entire URN is case-insensitive, because of the Note that the entire URN is case-insensitive, because of the
defintion of the NSS. definition of the NSS.
1.5. Functional Equivalence Relations 1.5. Functional Equivalence Relations
Rules for equivalence in this namespace are embedded in the document Rules for equivalence in this namespace are embedded in the document
mappings maintained by the RFC Editor (the index files "rfc- mappings maintained by the RFC Editor (the index files "rfc-
index.txt", "fyi-index.txt", "std-index.txt"). A resource is index.txt", "fyi-index.txt", "std-index.txt"). A resource is
equivalent to the set of resources implied by the "(Also...)" equivalent to the set of resources implied by the "(Also...)"
construct in these mappings. As an example, the URN construct in these mappings. As an example, the URN
"urn:ietf:rfc:1661" is equivalent to th URN "urn:ietf:std:51" because "urn:ietf:rfc:1661" is equivalent to th URN "urn:ietf:std:51" because
the "rfc-index.txt" map shows that RFC 1661 is also STD 51. However, the "rfc-index.txt" map shows that RFC 1661 is also STD 51. However,
skipping to change at page 3, line 24 skipping to change at page 3, line 29
the existence of the reserved characters from [1]. Further, the the existence of the reserved characters from [1]. Further, the
definition of the NSS above does not use any of the reserved definition of the NSS above does not use any of the reserved
characters from [1], which means that resolvers for this namespace characters from [1], which means that resolvers for this namespace
may be considered "secure" in the sense that any escaping of may be considered "secure" in the sense that any escaping of
characters in the NSS MUST result in the resolver indicating that the characters in the NSS MUST result in the resolver indicating that the
URN has incorrect syntax. URN has incorrect syntax.
3. Acknowledgments 3. Acknowledgments
Thanks to various members of the URN working group for comments on Thanks to various members of the URN working group for comments on
earlier drafts of this document. This document is partially earlier drafts of this document. The work described in this document
supported by the National Science Foundation, Cooperative Agreement is partially supported by the National Science Foundation,
NCR-9218179. Cooperative Agreement NCR-9218179.
4. References 4. 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] R. Moats, "URN Syntax," RFC 2141, May 5, 1997. [1] R. Moats, "URN Syntax," RFC 2141, May 5, 1997.
[2] D. Crocker, P. Overell, "Augmented BNF for Syntax [2] D. Crocker, P. Overell, "Augmented BNF for Syntax
Specifications: ABNF," Internet Draft (work in pro- Specifications: ABNF," Internet Draft (work in pro-
skipping to change at page 3, line 46 skipping to change at page 4, line 4
Specifications: ABNF," Internet Draft (work in pro- Specifications: ABNF," Internet Draft (work in pro-
gress), January 1997. gress), January 1997.
5. Author's Address 5. Author'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@att.com EMail: jayhawk@att.com
This Internet Draft expires November 30, 1997. This Internet Draft expires December 31, 1997.
 End of changes. 11 change blocks. 
27 lines changed or deleted 30 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/