Uniform Resource Names (urn)

This Working Group Did Not Meet.
NOTE: This charter is a snapshot of the 47th IETF Meeting in Adelaide, Australia. It may now be out-of-date. Last Modified: 03-Jun-99

Chair(s):

John Curran <jcurran@netgeeks.net>
Leslie Daigle <leslie@thinkingcat.com>

Applications Area Director(s):

Keith Moore <moore@cs.utk.edu>
Patrik Faltstrom <paf@swip.net>

Applications Area Advisor:

Keith Moore <moore@cs.utk.edu>

Mailing Lists:

General Discussion:urn-ietf@lists.internic.net
To Subscribe: listserv@lists.internic.net
In Body: subscribe urn-ietf
Archive: http://lists.internic.net/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:

Oct 96

  

Submit revision of URN Framework document as Internet-Draft.

Oct 96

  

Submit revised version of the NAPTR proposal as an Internet-Draft.

Oct 96

  

Submit Syntax document as an Internet-Draft.

Oct 96

  

Submit document detailing the N2L/N2R/etc resolution results as an Internet-Draft.

Nov 96

  

Submit document describing one (new) namespace as an Internet-Draft.

Dec 96

  

Submit revised N2L/N2R/etc document as an Internet-Draft.

Dec 96

  

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.

Dec 96

  

Submit paper outlining grandfathering one namespace into the framework as an Internet-Draft.

Feb 97

  

Submit revised grandfather namespace document as Internet-Draft.

Feb 97

  

Submit N2L/N2R/etc document to IESG for publication as RFC.

Feb 97

  

Submit revised new Namespace document as Internet-Draft.

Mar 97

  

Submit grandfathered namespace paper to IESG for publication as RFC. Submit new namespace proposal to IESG for publication as RFC.

Internet-Drafts:

Request For Comments:

RFC

Status

Title

 

RFC2141

PS

URN Syntax

RFC2168

E

Resolution of Uniform Resource Identifiers using the Domain Name System

RFC2169

E

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

RFC2483

E

URI Resolution Services Necessary for URN Resolution

RFC2611

 

URN Namespace Definition Mechanisms

RFC2648

 

A URN Namespace for IETF Documents