WG ACTION: Uniform Resource Names (urn)

Cynthia Clark <cclark@ietf.org> Tue, 24 September 1996 14:45 UTC

Received: from ietf.org by ietf.org id aa02800; 24 Sep 96 10:45 EDT
Received: from localhost by ietf.org id aa02404; 24 Sep 96 10:39 EDT
To: IETF-Announce:;
Subject: WG ACTION: Uniform Resource Names (urn)
Date: Tue, 24 Sep 1996 10:39:52 -0400
Sender: ietf-announce-request@ietf.org
From: Cynthia Clark <cclark@ietf.org>
Message-ID: <9609241039.aa02404@ietf.org>

A new working group has been formed in the Applications Area 
of the IETF. For additional information, contact the Area Directors or 
the WG Chair.


Uniform Resource Names (urn)
----------------------------
 
 Chair(s):
     Leslie Daigle <leslie@bunyip.com>
     John Curran <jcurran@bbn.com>
 
 Applications Area Director(s): 
     Keith Moore  <moore+iesg@cs.utk.edu>
     Harald Alvestrand  <Harald.T.Alvestrand@uninett.no>
 
 Area Advisor
     Harald Alvestrand  <Harald.T.Alvestrand@uninett.no>
 
 Mailing lists: 
     General Discussion:urn-ietf@bunyip.com
     To Subscribe:      majordomo@bunyip.com
         In Body:       In body of message: subscribe urn-ietf
     Archive:           ftp://ftp.bunyip.com/pub/mailing-lists/urn-ietf.archive
 
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 <draft-daigle-urnframework-00.txt>

 o Resolution of Uniform Resource Identifiers using the Domain Name
   System <draft-daniel-naptr-01.txt>

 o Requirements for URN Resolution Systems
   <draft-girod-urn-res-require-00.txt>

 
 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 paper outlining grandfathering one namespace into the 
                framework 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.         

   Feb 97       Submit revised new Namespace document as 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.    

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