Uniform Resource Name (URN) Namespace Registration Transition
draft-ietf-urnbis-ns-reg-transition-08

Document Type Active Internet-Draft (urnbis WG)
Last updated 2017-08-14 (latest revision 2017-07-01)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: May 2017 - WGLC on URN Namespac... )
Document shepherd Barry Leiba
Shepherd write-up Show (last changed 2017-07-01)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Alexey Melnikov
Send notices to Barry Leiba <barryleiba@computer.org>
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IC
RFC Editor RFC Editor state EDIT
URNbis                                                        J. Klensin
Internet-Draft
Obsoletes: 3044, 3187 (if approved)                            J. Hakala
Intended status: Standards Track         The National Library of Finland
Expires: January 2, 2018                                    July 1, 2017

     Uniform Resource Name (URN) Namespace Registration Transition
                 draft-ietf-urnbis-ns-reg-transition-08

Abstract

   The original registration procedure for formal Uniform Resource Name
   (URN) namespaces required IETF Consensus.  That requirement
   discouraged some registrations and increased the risk for problems
   that could occur as a result.  The requirements have now been changed
   by RFC 8141, which adopts a different model, focusing on encouraging
   registration and publication of information for all appropriate
   namespaces.  This document clarifies the status of relevant older
   RFCs and confirms and documents advice to IANA about selected
   existing registrations.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 2, 2018.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Klensin & Hakala         Expires January 2, 2018                [Page 1]
Internet-Draft         URN Registration Transition             July 2017

   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Obsoleting Older Registration RFCs for ISSNs and ISBNs  . . .   3
     2.1.  ISBN URN Changes  . . . . . . . . . . . . . . . . . . . .   4
     2.2.  ISSN URN Changes  . . . . . . . . . . . . . . . . . . . .   4
   3.  The Older Registration RFC for NBNs . . . . . . . . . . . . .   4
   4.  Other Existing URN Registrations and RFCs . . . . . . . . . .   5
   5.  Registration Examples . . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   9.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   6
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   6
     10.2.  Informative References . . . . . . . . . . . . . . . . .   6
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .   8
     A.1.  Changes from version -00 to -01 . . . . . . . . . . . . .   8
     A.2.  Changes from version -01 to -02 . . . . . . . . . . . . .   8
     A.3.  Changes from version -02 to -03 . . . . . . . . . . . . .   9
     A.4.  Changes from version -03 to -04 . . . . . . . . . . . . .   9
     A.5.  Changes from version -04 to -05 . . . . . . . . . . . . .   9
     A.6.  Changes from version -05 to -06 . . . . . . . . . . . . .   9
     A.7.  Changes from version -06 (2016-02-07) to -07  . . . . . .   9
     A.8.  Changes from version -07 (2017-05-09) to -08  . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   As a part of the initial development of the Uniform Resource Name
   (URN) system in the late 1990s, the IETF URN working group agreed
   that it was important to demonstrate that the URN syntax could
   accommodate existing identifier systems.  RFC 2288 [RFC2288] showed
   the feasibility of using International Standard Book Number (ISBN),
   International Standard Serial Number (ISSN), and Serial Item and
   Contribution Identifier (SICI) [ANSI-SICI]) as URNs; however, it did
Show full document text