draft-ietf-urnbis-ns-reg-transition-00.txt   draft-ietf-urnbis-ns-reg-transition-01.txt 
URNbis J. Klensin URNbis J. Klensin
Internet-Draft Internet-Draft
Obsoletes: 3044, 3187 (if approved) J. Hakala Obsoletes: 3044, 3187 (if approved) J. Hakala
Intended status: Standards Track The National Library of Finland Intended status: Standards Track The National Library of Finland
Expires: February 27, 2014 August 26, 2013 Expires: July 26, 2014 January 22, 2014
Uniform Resource Name (URN) Namespace Registration Transition Uniform Resource Name (URN) Namespace Registration Transition
draft-ietf-urnbis-ns-reg-transition-00 draft-ietf-urnbis-ns-reg-transition-01
Abstract Abstract
The original registration procedure for formal Uniform Resource Name The original registration procedure for formal Uniform Resource Name
(URN) namespaces required IETF Consensus. That requirement (URN) namespaces required IETF Consensus. That requirement
discouraged some registrations and increased the risk for problems discouraged some registrations and increased the risk for problems
that could occur as a result. The requirements have now been changed that could occur as a result. The requirements have now been changed
in [[RFC 3406bis]] to adopt a different model. This document in [[RFC 3406bis]] to adopt a different model. This document
specifies IANA instructions to adapt selected existing registrations specifies IANA instructions to adapt selected existing registrations
to the new model. It also obsoletes some previous RFCs to eliminate to the new model. It also obsoletes some previous RFCs to eliminate
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 27, 2014. This Internet-Draft will expire on July 26, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Obsoleting Older Registration RFCs . . . . . . . . . . . . . 3 2. Obsoleting Older Registration RFCs . . . . . . . . . . . . . 3
2.1. ISBN URN Changes . . . . . . . . . . . . . . . . . . . . 4 2.1. ISBN URN Changes . . . . . . . . . . . . . . . . . . . . 4
2.2. ISSN URN Changes . . . . . . . . . . . . . . . . . . . . 4 2.2. ISSN URN Changes . . . . . . . . . . . . . . . . . . . . 4
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . 5 7.1. Normative References . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . 5 7.2. Informative References . . . . . . . . . . . . . . . . . 5
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 6
A.1. Changes from version -00 to -01 . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
[[RFC Editor: Please note that mentions of "RFC 3406bis" in this I-D
are defined as an Entity in the XML. They should be corrected to
show the actual RFC number before publication.]]
[[Note in draft: This document has been written in RFC form, i.e., [[Note in draft: This document has been written in RFC form, i.e.,
assuming that it and 3406bis have been approved. That style of assuming that it and 3406bis have been approved. That style of
writing assumes that RFC 3406 and the rules it specified are already writing assumes that RFC 3406 and the rules it specified are already
obsolete. It may be a bit awkward while the I-D is being evaluated obsolete. It may be a bit awkward while the I-D is being evaluated
by the WG and the IETF, but lowers the risk for errors or other by the WG and the IETF, but lowers the risk for errors or other
surprises during the RFC editing process.]] surprises during the RFC editing process.]]
As a part of the initial development of the URN system back in the As a part of the initial development of the URN system in the late
late 1990s, the IETF URN working group agreed that it was important 1990s, the IETF URN working group agreed that it was important to
to demonstrate that the URN syntax can accommodate existing demonstrate that the URN syntax can accommodate existing identifier
identifier systems. RFC 2288 [RFC2288] investigated the feasibility systems. RFC 2288 [RFC2288] investigated the feasibility of using
of using three identifiers (ISBN, ISSN and SICI) as URNs, with three identifiers (ISBN, ISSN and SICI) as URNs, with positive
positive results; however, it did not formally register corresponding results; however, it did not formally register corresponding URN
URN namespaces. This was in part due to the still evolving process namespaces. This was in part due to the still evolving process to
to formalize criteria for namespace definition documents and formalize criteria for namespace definition documents and
registration, consolidated later in the IETF, first into RFC 2611 registration, consolidated later in the IETF into successive
[RFC2611] and then into RFC 3406 [RFC3406]. Namespace Definition Mechanism documents [RFC2611] [RFC3406].
URN Namespaces have subsequently been registered for NBN (National URN Namespaces have subsequently been registered for NBN (National
Bibliography Number), ISBN (International Standard Book Number), and Bibliography Number) [RFC3188], ISBN (International Standard Book
ISSN (International Serial Standard Number) in RFCs 3188 [RFC3188], Number) [RFC3187], and ISSN (International Standard Serial Number)
3187 [RFC3187], 3044 [RFC3044] respectively. [RFC3044].
The original registration procedure for Uniform Resource Name (URN) The predecessor registration procedure for Uniform Resource Name
namespaces [RFC3406] required IETF Consensus for formal ones. That (URN) namespaces [RFC3406] required IETF Consensus for formal
requirement discouraged some registrations and increased the risk for namespaces. That requirement discouraged some registrations and
problems that could occur as a result. Those potential problems increased the risk for problems, including use of names without
included the possibility of the same name being used to identify registration ("squatting"), that could occur as a result. Those
different namespaces with different rules. The requirements have now potential problems included the possibility of the same name being
been changed [RFC3406bis] to adopt a different model that focuses used to identify different namespaces with different rules. The
more on attempting to get all namespaces that follow the syntax of requirements have now been changed [RFC3406bis] to adopt a different
formal ones registered, with as much information collected as a model that focuses more on attempting to get all namespaces that
possible consistent with that goal. This document specifies IANA follow the syntax of formal ones registered, with as much information
instructions to adapt selected existing registrations to the new collected as a possible consistent with that goal. This document
model and obsoletes the RFCs that specify the namespaces for specifies IANA instructions to adapt selected existing registrations
International Standard Serial Numbers (ISSNs) [RFC3044], to the new model and obsoletes the separate RFCs that specify the
International Standard Book Numbers (ISBNs) [RFC3187] to eliminate namespaces for International Standard Serial Numbers (ISSNs)
any ambiguity about the status of new templates and updated [RFC3044], International Standard Book Numbers (ISBNs) [RFC3187] to
eliminate any ambiguity about the status of new templates and updated
registrations. registrations.
An updated version of the specification for the namespace for An updated version of the specification for the namespace for
National Bibliography Numbers (NBNs) [RFC3188] will be issued National Bibliography Numbers (NBNs) [RFC3188] will be issued
separately. NBN is not a formal standard and RFC 3188 is the only separately. NBN is not a formal international standard and RFC 3188
formal document which specifies its scope. The intention is to is the only formal document which specifies its scope. The intention
modernize the existing namespace registration so that it specifies is to modernize the existing namespace registration so that it
the identifier and provides examples of its use, while the actual specifies the identifier and provides examples of its use, while the
namespace registration will be done according to the new practice. actual namespace registration will be done according to the new
practice.
2. Obsoleting Older Registration RFCs 2. Obsoleting Older Registration RFCs
The existing RFCs that describe URN namespaces for ISSNs (RFC 3044) The existing RFCs that describe URN namespaces for ISSNs (RFC 3044)
and ISBNs (RFC 3187) should be identified as "Historic" immediately and ISBNs (RFC 3187) should be identified as "Historic" immediately
after this document is approved and the new registration templates after this document is approved and the new registration templates
for those namespaces are submitted and incorporated into the URN for those namespaces are submitted and incorporated into the URN
Namespace registry by IANA. Namespace registry by IANA.
[[Note in draft: The more information that can be supplied in the [[Note in draft: The more information that can be supplied in the
template or references from it, the better. But, if there is template or references from it, the better. But, if there is
information in the now-expired Internet-Drafts (draft-ietf-urnbis- information in the now-expired Internet-Drafts (draft-ietf-urnbis-
rfc3187bis-isbn-urn, draft-ietf-urnbis-rfc3044bis-issn-urn) that rfc3187bis-isbn-urn, draft-ietf-urnbis-rfc3044bis-issn-urn) that
should be captured somewhere and that doesn't fit naturally in the should be captured somewhere and that doesn't fit naturally in the
template, the discussion below is probably a reasonable place to put template, the discussion below is probably a reasonable place to put
it.]] it.]]
The updated templates reflect not only new template formats but
substantive changes to the definitions of the namespaces. The
changes are summarized in the subsections that follow.
Those updated templates reflect not only new formats but substantive For both ISSN and ISBN URNs, it is intended that the registrations
changes to the definitions of the namespaces, as described in the track the evolution of ISO standardization without requiring
following subsections. resubmission of the templates or other formal IETF or IANA
registration update approval procedures.
2.1. ISBN URN Changes 2.1. ISBN URN Changes
The revised ISBN namespace reflects the updated version of the ISO The revised ISBN namespace reflects the updated version of the ISO
Standard for ISBNs, ISO 2108:2005 [ISO-ISBN-b] and allows for the use Standard for ISBNs, ISO 2108:2005 [ISO-ISBN-b] and allows for the use
of both the ten character numbers described in RFC 3187 and the of both the ten character numbers described in RFC 3187 and the
earlier ISO 2108:1992 [ISO-ISBN-a] (known as ISBN-10) and the earlier ISO 2108:1992 [ISO-ISBN-a] (known as ISBN-10) and the
expanded ones of the revised standard (known as ISBN-13). expanded ones of the revised standard (known as ISBN-13).
2.2. ISSN URN Changes 2.2. ISSN URN Changes
skipping to change at page 4, line 31 skipping to change at page 4, line 39
IANA is requested to update the registry entries for URN ISSNs, IANA is requested to update the registry entries for URN ISSNs,
ISBNs, and NRNs to reflect the new, RFC 3406bis-complaint templates ISBNs, and NRNs to reflect the new, RFC 3406bis-complaint templates
as soon as they are available and to no longer reference the now- as soon as they are available and to no longer reference the now-
historic RFCs. Other registrations and templates conforming to the historic RFCs. Other registrations and templates conforming to the
newer rules may be substituted for the older ones when they are newer rules may be substituted for the older ones when they are
available. However, neither this document nor RFC 3406bis available. However, neither this document nor RFC 3406bis
invalidates existing registrations other than those listed above, so invalidates existing registrations other than those listed above, so
IANA needs to be prepared to maintain a registry whose contents IANA needs to be prepared to maintain a registry whose contents
reflect both old and new templates. reflect both old and new templates.
IANA should also note that the portions of the registrations that
point to ISO Standards are intended to identify current versions
(which may change) rather than only the versions that are active at
the time this document is approved (see Section 2).
4. Security Considerations 4. Security Considerations
While particular URN namespaces and their registrations might While particular URN namespaces and their registrations might
conceivably have security implications, this specification merely conceivably have security implications, this specification merely
specifies a transition in a registration procedure and does not have specifies a transition of a pair of registration procedures and does
such implications. The security implications associated with not have such implications. The security implications associated
particular namespaces are expected to be listed in registration with particular namespaces are expected to be listed in registration
templates as specified in RFC 3406bis. templates as specified in RFC 3406bis.
5. Acknowledgements 5. Acknowledgements
This document draws heavily on discussions in the IETF URNbis Working This document draws heavily on discussions in the IETF URNbis Working
Group in the second and third quarters of 2013, particularly during Group in the second and third quarters of 2013, particularly during
IETF 87 in August 2013, and on informal discussions during the IETF 87 in August 2013, and on informal discussions during the
plenary meeting of ISO TC 46 in June 2013. The efforts of those who plenary meeting of ISO TC 46 in June 2013. The efforts of those who
participated in those discussions are greatly appreciated. It also participated in those discussions are greatly appreciated. It also
draws on internet-drafts that were developed to update the older draws on internet-drafts that were developed to update the older
skipping to change at page 5, line 16 skipping to change at page 5, line 28
Alfred Hoenes was the editor and co-author of two of the documents Alfred Hoenes was the editor and co-author of two of the documents
from which this one is, in part, derived. This document would not from which this one is, in part, derived. This document would not
have been possible without his contributions. have been possible without his contributions.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC3406bis] [RFC3406bis]
Saint-Andre, P., Ed., Daigle, L., van Gulik, D., Iannella, Saint-Andre, P., Ed., "Uniform Resource Name (URN)
R., and P. Faltstrom, "Uniform Resource Name (URN) Namespace Definition Mechanisms", November 2013, <https://
Namespace Definition Mechanisms", August 2013, <https://
datatracker.ietf.org/doc/draft-ietf-urnbis-rfc3406bis-urn- datatracker.ietf.org/doc/draft-ietf-urnbis-rfc3406bis-urn-
ns-reg/>. ns-reg/>.
7.2. Informative References 7.2. Informative References
[ISO-ISBN-a] [ISO-ISBN-a]
ISO, "Information and documentation - The International ISO, "Information and documentation - The International
Standard Book Number (ISBN)", ISO 2180:1992, 1992. Standard Book Number (ISBN)", ISO 2180:1992, 1992.
[ISO-ISBN-b] [ISO-ISBN-b]
skipping to change at page 6, line 12 skipping to change at page 6, line 24
Book Numbers as Uniform Resource Names", RFC 3187, October Book Numbers as Uniform Resource Names", RFC 3187, October
2001. 2001.
[RFC3188] Hakala, J., "Using National Bibliography Numbers as [RFC3188] Hakala, J., "Using National Bibliography Numbers as
Uniform Resource Names", RFC 3188, October 2001. Uniform Resource Names", RFC 3188, October 2001.
[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
"Uniform Resource Names (URN) Namespace Definition "Uniform Resource Names (URN) Namespace Definition
Mechanisms", BCP 66, RFC 3406, October 2002. Mechanisms", BCP 66, RFC 3406, October 2002.
Appendix A. Change Log
A.1. Changes from version -00 to -01
o Modified the introduction to Section 2 and Section 3 to make it
clear that registry update procedures should not be required to
keep the registrations current with ISO Standard reaffirmations or
replacments.
o Many editorial changes to improve readability and clarity.
Authors' Addresses Authors' Addresses
John C Klensin John C Klensin
1770 Massachusetts Ave, Ste 322 1770 Massachusetts Ave, Ste 322
Cambridge, MA 02140 Cambridge, MA 02140
USA USA
Phone: +1 617 245 1457 Phone: +1 617 245 1457
Email: john-ietf@jck.com Email: john-ietf@jck.com
 End of changes. 17 change blocks. 
47 lines changed or deleted 74 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/