Uniform Resource Names (urn) ---------------------------- Charter Last Modified: 2001-07-31 Current Status: Active Working Group Chair(s): John Curran Leslie Daigle Applications Area Director(s): Ned Freed Patrik Faltstrom Applications Area Advisor: Patrik Faltstrom Mailing Lists: General Discussion:urn-ietf@lists.netsol.com To Subscribe: listserv@lists.netsol.com In Body: subscribe urn-ietf Archive: http://lists.netsol.com/archives/urn-ietf.html Description of Working Group: The goal of this working group is to define both a Uniform Resource Name (URN) framework and an initial set of components that fit this framework. 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. Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Jun 98 May 02 Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedures Jul 00 May 02 Dynamic Delegation Discovery System (DDDS)Part Two: The Algorithm Jul 00 May 02 Dynamic Delegation Discovery System (DDDS) Part Three: The DNS Database Jul 00 May 02 Dynamic Delegation Discovery System (DDDS) Part Four: The URI Resolution Application Nov 00 Jan 02 URN Namespace Definition Mechanisms Oct 01 May 02 Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS Standard Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC2141 PS May 97 URN Syntax RFC2169 E Jun 97 A Trivial Convention for using HTTP in URN Resolution RFC2168 E Jun 97 Resolution of Uniform Resource Identifiers using the Domain Name System RFC2276 I Jan 98 Architectural Principles of Uniform Resource Name Resolution RFC2288 I Feb 98 Using Existing Bibliographic Identifiers as Uniform Resource Names RFC2483 E Jan 99 URI Resolution Services Necessary for URN Resolution RFC2611BCP Jun 99 URN Namespace Definition Mechanisms RFC2648 I Aug 99 A URN Namespace for IETF Documents RFC2915 PS Sep 00 The Naming Authority Pointer (NAPTR) DNS Resource Record