 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
Last Modifield: 2001-07-31
Concluded: 2002-10-22
URNs are persistent identifiers for information resources. The output of this Working Group will comply with RFC 1737, which defines URNs and gives requirements for them. The framework will define the mechanics for enabling global scope, persistence, and legacy support requirements of URNs; requirements for namespaces to support this structure will also be defined. Although the framework will allow URNs to be defined that vary in terms of degree of scalability and persistance, ensuring "user friendliness" of all resultant identifiers is beyond the scope of this group.
This WG will define the framework for URNs, at least one resolution registry system, and at least one namespace. RFCs describing additional material will also be developed (per the milestones, below).
Input documents:
o A Framework for the Assignment and Resolution of Uniform Resource
Names
o Resolution of Uniform Resource Identifiers using the Domain Name
System
o Requirements for URN Resolution Systems
Goals and Milestones:
Done Submit revision of URN Framework document as
Internet-Draft. Done Submit revised version of the NAPTR proposal as an
Internet-Draft. Done Submit document detailing the N2L/N2R/etc resolution
results as an Internet-Draft. Done Submit Syntax document as an Internet-Draft. Done Submit document describing one (new) namespace as an
Internet-Draft. Done Submit NAPTR proposal to IESG as Experimental RFC. Submit
Framework document to IESG for publication as an RFC.
Submit syntax paper to IESG for publication as an RFC. Done Submit paper outlining grandfathering one namespace into
the framework as an Internet-Draft. Done Submit revised N2L/N2R/etc document as an Internet-Draft. Done Submit revised grandfather namespace document as
Internet-Draft. Done Submit N2L/N2R/etc document to IESG for publication as RFC. Done Submit revised new Namespace document as Internet-Draft. Done Submit grandfathered namespace paper to IESG for
publication as RFC. Submit new namespace proposal to IESG
for publication as RFC. Done Submit Assignment Procedures for the URI Resolution using
DNS to IESG as Proposed Standard. Done Submit Dynamic Delegation Discovery System (DDDS) to IESG
as Proposed Standard Done Submit A DDDS Database Using The Domain Name System to IESG
as Proposed Standard Done Submit URI Resolution using the Dynamic Delegation
Discovery System to IESG as Proposed Standard. No Current Internet-Drafts
Request For Comments:
URN Syntax (RFC 2141) (14077 bytes)
A Trivial Convention for using HTTP in URN
Resolution (RFC 2169) (17763 bytes)
Resolution of Uniform Resource Identifiers using the
Domain Name System (RFC 2168) (46528 bytes)
Architectural Principles of Uniform Resource Name
Resolution (RFC 2276) (64811 bytes)
Using Existing Bibliographic Identifiers as Uniform
Resource Names (RFC 2288) (21628 bytes)
URI Resolution Services Necessary for URN Resolution (RFC 2483) (30518 bytes)
URN Namespace Definition Mechanisms (RFC 2611) (26916 bytes)
A URN Namespace for IETF Documents (RFC 2648) (46826 bytes)
The Naming Authority Pointer (NAPTR) DNS Resource
Record (RFC 2915) (41555 bytes)
Dynamic Delegation Discovery System (DDDS) Part One:
The Comprehensive DDDS (RFC 3401) (10172 bytes)
Dynamic Delegation Discovery System (DDDS)Part Two:
The Algorithm (RFC 3402) (38925 bytes)
Dynamic Delegation Discovery System (DDDS) Part
Three: The The Domain Name System (DNS) Database (RFC 3403) (31058 bytes)
Dynamic Delegation Discovery System (DDDS) Part
Four: The The Uniform Resource
Identifiers(URI)Resolution Application (RFC 3404) (40124 bytes)
Dynamic Delegation Discovery System (DDDS) Part
Five: URI.ARPA Assignment Procedures (RFC 3405) (19469 bytes)
Uniform Resource Names (URN) Namespace Definition
Mechanisms (RFC 3406) (43707 bytes)
IETF Secretariat - Please send questions, comments, and/or
suggestions to
ietf-web@ietf.org.
Return to working group directory.