URNBIS BOF, IETF 78

BOF CHAIRS

   John C. Klensin <john-ietf at jck.com>
   Alfred Hönes <ah at TR-Sys.de>


DATE/TIME/VENUE:

   27 July, Tuesday, 0900 - 1130, Room 0.8 Rome


GOAL:  to charter a new WG

RECOMMENDED READING FOR ATTENDEES/PARTICIPANTS:
      The "Introduction" sections (at least!) of the following
      I-Ds (also listed in the draft charter):

  draft-ah-rfc2141bis-urn          (-00: submitted March 2010)
  draft-hakala-rfc3187bis-isbn-urn (-00: submitted March 2010)
  draft-hakala-rfc3188bis-nbn-urn  (-00: submitted May 2010) 

      Preliminary draft charter:
  http://www.ietf.org/mail-archive/web/urn/current/msg01431.html
    


AGENDA:

1. Administrivia (Chairs, 5 min)

   - Note takers, Jabber scribes

   - "Note Well"

   - Agenda bashing


2. Presentations (40-45 min)

2.1. The need for up-to-date URN Standard documents (10-15 min)
       -  where do URNs come from, why do we need them
       -  URN work in the IETF, from mid 1970's until today
       -  what happened on a wider scale, regarding URIs
       -  mismatches and inconsistencies, lack of maturity

2.2. One URN "customer":                                (5 min)
       -  National library use of URNs
       -  a short presentation of project PersID
     

2.3. Work items -- problem statement and scope of work (25 min)
     

     a) general goals and non-goals              (2 min)

     b) Core URN documents                       (6 min)
        -  formal specification / revision of RFC 2141
        -  namespace registration / revision of RFC 3406
       
     c) URN namespaces for bibliograpic identifier 
        systems                                  (6 min)
        - ISBN URNs / revision of RFC 3187
        - NBN URNs  / revision of RFC 3188
        - ISSN URNs  / revision of RFC 3044
        
     d) Review of other URN namespaces           (3 min)
        - review existing namespace registration RFCs
           {with respect to RFC 3986 etc. and work in b) above}
        - point original registrants to issues / needs for
            update 
        - take on work on revisions in WG (only upon
            rechartering) 
        - serve as a voluntary forum of competence in support of
            new URN namespace registrants and IANA urn-nid expert

     e) staging of work, possible milestones, 
        advancing of STD maturity                (10 min)


  2.4 URN Resolution                                    (6 min)

     In order to keep the scope of the proposed WG plausible,
     a review and revision or addition of URN Resolution 
     protocols will not be part of an initial proposed 
     charter.  Nonetheless, if time permits, a brief overview
     of principles, systems, issues and experience from other
     work will be included in the BOF for context:

        - review existing RFCs for relevance and need for
            update 
        - discuss whether new URN resolution framework document
            is needed 
        - Possible future BCP on use of HTTP for URN resolution
        - based on experience in Project PersID



3. Open Q&A for presentations  (Chairs)                (45 min)


4. Discussion of Draft Charter and Work 
  Plan (Chairs/ADs)                                    (30 min)


5. Conclusions and Next Steps  (Chairs/ADs)            (10 min)