Uniform Resource Names (urn)

This Working Group did not meet

NOTE: This charter is a snapshot of the 52nd IETF Meeting in Salt Lake City, Utah USA. It may now be out-of-date. Last Modified: 31-Jul-01

Chair(s):
John Curran <jcurran@netgeeks.net>
Leslie Daigle <leslie@thinkingcat.com>
Applications Area Director(s):
Ned Freed <ned.freed@mrochek.com>
Patrik Faltstrom <paf@cisco.com>
Applications Area Advisor:
Patrik Faltstrom <paf@cisco.com>
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 Syntax document as an Internet-Draft.
Done   Submit document detailing the N2L/N2R/etc resolution results as an Internet-Draft.
Done   Submit document describing one (new) namespace as an Internet-Draft.
Done   Submit revised N2L/N2R/etc document 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 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.
Oct 00   Submit Assignment Procedures for the URI Resolution using DNS to IESG as Proposed Standard.
Oct 00   Submit Dynamic Delegation Discovery System (DDDS) to IESG as Proposed Standard
Oct 00   Submit A DDDS Database Using The Domain Name System to IESG as Proposed Standard
Oct 00   Submit URI Resolution using the Dynamic Delegation Discovery System to IESG as Proposed Standard.
Internet-Drafts:
Request For Comments:
RFCStatusTitle
RFC2141PSURN Syntax
RFC2168E Resolution of Uniform Resource Identifiers using the Domain Name System
RFC2169E A Trivial Convention for using HTTP in URN Resolution
RFC2276 Architectural Principles of Uniform Resource Name Resolution
RFC2288 Using Existing Bibliographic Identifiers as Uniform Resource Names
RFC2483E URI Resolution Services Necessary for URN Resolution
RFC2611 URN Namespace Definition Mechanisms
RFC2648 A URN Namespace for IETF Documents
RFC2915PSThe Naming Authority Pointer (NAPTR) DNS Resource Record

Current Meeting Report

None received.

Slides

None received.