draft-ietf-urnbis-semantics-clarif-01.txt   draft-ietf-urnbis-semantics-clarif-02.txt 
Uniform Resource Names (urnbis) J. Klensin Uniform Resource Names (urnbis) J. Klensin
Internet-Draft Internet-Draft August 10, 2015
Updates: 3986 (if approved) February 14, 2015 Updates: 3986 (if approved)
Intended status: Standards Track Intended status: Standards Track
Expires: August 18, 2015 Expires: February 11, 2016
URN Semantics Clarification URN Semantics Clarification
draft-ietf-urnbis-semantics-clarif-01.txt draft-ietf-urnbis-semantics-clarif-02.txt
Abstract Abstract
Experience has shown that identifiers associated with persistent Experience has shown that identifiers associated with persistent
names have properties and requirements that may be somewhat different names have properties and requirements that may be somewhat different
from identifiers associated with the locations of objects. This is from identifiers associated with the locations of objects. This is
especially true when such names are expected to be stable for a very especially true when such names are expected to be stable for a very
long time or when they identify large and complex entities. In order long time or when they identify large and complex entities. In order
to allow Uniform Resource Names (URNs) to evolve to meet the needs of to allow Uniform Resource Names (URNs) to evolve to meet the needs of
the Library, Museum, Publisher, and Information Science communities the Library, Museum, Publisher, and Information Science communities
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 August 18, 2015. This Internet-Draft will expire on February 11, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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
skipping to change at page 2, line 25 skipping to change at page 2, line 25
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Pragmatic Goals . . . . . . . . . . . . . . . . . . . . . . . 4 2. Pragmatic Goals . . . . . . . . . . . . . . . . . . . . . . . 4
3. The role of queries and fragments in URNs . . . . . . . . . . 4 3. The role of queries and fragments in URNs . . . . . . . . . . 4
4. Changes to RFC 3986 . . . . . . . . . . . . . . . . . . . . . 5 4. Changes to RFC 3986 . . . . . . . . . . . . . . . . . . . . . 5
5. Actions Occurring in Parallel with this Specification . . . . 5 5. Actions Occurring in Parallel with this Specification . . . . 5
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
9. Security Considerations . . . . . . . . . . . . . . . . . . . 6 9. Security Considerations . . . . . . . . . . . . . . . . . . . 7
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
10.1. Normative References . . . . . . . . . . . . . . . . . . 7 10.1. Normative References . . . . . . . . . . . . . . . . . . 7
10.2. Informative References . . . . . . . . . . . . . . . . . 7 10.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Background on the URN - URI relationship . . . . . . 8 Appendix A. Background on the URN - URI relationship . . . . . . 8
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 8 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 9
B.1. Changes from draft-ietf-urnbis-urns-are-not-uris-00 B.1. Changes from draft-ietf-urnbis-urns-are-not-uris-00
(2014-04-07) to -01 (2014-07-03) . . . . . . . . . . . . 9 (2014-04-07) to -01 (2014-07-03) . . . . . . . . . . . . 9
B.2. Changes from draft-ietf-urnbis-urns-are-not-uris-01 B.2. Changes from draft-ietf-urnbis-urns-are-not-uris-01
to draft-ietf-urnbis-semantics-clarif-00 (2014-08-25) . . 9 to draft-ietf-urnbis-semantics-clarif-00 (2014-08-25) . . 9
B.3. Changes from draft-ietf-urnbis-semantics-clarif-00 B.3. Changes from draft-ietf-urnbis-semantics-clarif-00
(2014-08-25) to -01 . . . . . . . . . . . . . . . . . . . 10 (2014-08-25) to -01 . . . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10 B.4. Changes from draft-ietf-urnbis-semantics-clarif-01
(2015-02-14) to -02 . . . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
The Generic URI Syntax specification [RFC3986] covers both locators The Generic URI Syntax specification [RFC3986] covers both locators
and names and mixtures of the two (See its Section 1.1.3) and and names and mixtures of the two (See its Section 1.1.3) and
describes Uniform Resource Locators (URLs) -- first documented in the describes Uniform Resource Locators (URLs) -- first documented in the
IETF in RFC 1738 [RFC1738] -- as an embodiment of the locator concept IETF in RFC 1738 [RFC1738] -- as an embodiment of the locator concept
and Uniform Resource Names (URNs), specifically those using the "urn" and Uniform Resource Names (URNs), specifically those using the "urn"
scheme [RFC2141], as an embodiment of the names that do not directly scheme [RFC2141], as an embodiment of the names that do not directly
provide for resource location. This specification is concerned only provide for resource location. This specification is concerned only
skipping to change at page 7, line 12 skipping to change at page 7, line 18
contained (as specified in other documents), relying on the generic contained (as specified in other documents), relying on the generic
URI syntax specification for syntax only. It should have no effect URI syntax specification for syntax only. It should have no effect
on Internet security unless the use of a definition, syntax, and on Internet security unless the use of a definition, syntax, and
semantics that are more clear reduces the potential for confusion and semantics that are more clear reduces the potential for confusion and
consequent vulnerabilities. consequent vulnerabilities.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. [RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141,
May 1997, <http://www.rfc-editor.org/info/rfc2141>.
[RFC2141bis]
Saint-Andre, P. and J. Klensin, "Uniform Resource Name
(URN) Syntax", June 2015,
<https://datatracker.ietf.org/doc/draft-ietf-urnbis-
rfc2141bis-urn/>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, RFC Resource Identifier (URI): Generic Syntax", STD 66,
3986, January 2005. RFC 3986, DOI 10.17487/RFC3986, January 2005,
<http://www.rfc-editor.org/info/rfc3986>.
10.2. Informative References 10.2. Informative References
[DeterministicURI] [DeterministicURI]
Mazahir, O., Thaler, D., and G. Montenegro, "Deterministic Mazahir, O., Thaler, D., and G. Montenegro, "Deterministic
URI Encoding", February 2014, <http://www.ietf.org/id/ URI Encoding", February 2014, <http://www.ietf.org/id/
draft-montenegro-httpbis-uri-encoding-00.txt>. draft-montenegro-httpbis-uri-encoding-00.txt>.
[IETF90-URNBISWG] [IETF90-URNBISWG]
IETF, "URN BIS Working Group Minutes", July 2014, IETF, "URN BIS Working Group Minutes", July 2014,
<http://www.ietf.org/proceedings/90/minutes/ <http://www.ietf.org/proceedings/90/minutes/
minutes-90-urnbis>. minutes-90-urnbis>.
[RFC1738] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform [RFC1738] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform
Resource Locators (URL)", RFC 1738, December 1994. Resource Locators (URL)", RFC 1738, DOI 10.17487/RFC1738,
December 1994, <http://www.rfc-editor.org/info/rfc1738>.
[RFC2141bis]
Saint-Andre, P., "Uniform Resource Name (URN) Syntax",
January 2014, <https://datatracker.ietf.org/doc/draft-
ietf-urnbis-rfc2141bis-urn/>.
[RFC2483] Mealling, M. and R. Daniel, "URI Resolution Services [RFC2483] Mealling, M. and R. Daniel, "URI Resolution Services
Necessary for URN Resolution", RFC 2483, January 1999. Necessary for URN Resolution", RFC 2483,
DOI 10.17487/RFC2483, January 1999,
<http://www.rfc-editor.org/info/rfc2483>.
[RFC3401] Mealling, M., "Dynamic Delegation Discovery System (DDDS) [RFC3401] Mealling, M., "Dynamic Delegation Discovery System (DDDS)
Part One: The Comprehensive DDDS", RFC 3401, October 2002. Part One: The Comprehensive DDDS", RFC 3401,
DOI 10.17487/RFC3401, October 2002,
<http://www.rfc-editor.org/info/rfc3401>.
[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, DOI 10.17487/RFC3406,
October 2002, <http://www.rfc-editor.org/info/rfc3406>.
[ServiceRequests] [ServiceRequests]
Klensin, J., "Names are Not Locators and URNs are Not Klensin, J., "Names are Not Locators and URNs are Not
URIs, Appendix B", July 2014, <http://www.ietf.org/id/ URIs, Appendix B", July 2014, <http://www.ietf.org/id/
draft-ietf-urnbis-urns-are-not-uris-01.txt>. draft-ietf-urnbis-urns-are-not-uris-01.txt>.
[URN-transition] [URN-transition]
Klensin, J. and J. Hakala, "Uniform Resource Name (URN) Klensin, J. and J. Hakala, "Uniform Resource Name (URN)
Namespace Registration Transition", February 2015, Namespace Registration Transition", August 2015,
<https://datatracker.ietf.org/doc/draft-ietf-urnbis-ns- <https://datatracker.ietf.org/doc/draft-ietf-urnbis-ns-
reg-transition/>. reg-transition/>.
[URNBIS-MailingList] [URNBIS-MailingList]
IETF, "IETF URN Mailing list", 2014, IETF, "IETF URN Mailing list", 2014,
<https://www.ietf.org/mailman/listinfo/urn>. <https://www.ietf.org/mailman/listinfo/urn>.
Appendix A. Background on the URN - URI relationship Appendix A. Background on the URN - URI relationship
The Internet community now has many years of experience with both The Internet community now has many years of experience with both
skipping to change at page 10, line 32 skipping to change at page 10, line 42
remove referenced to deleted material. It is not possible to remove referenced to deleted material. It is not possible to
reconstruct what earlier versions of this document contained by reconstruct what earlier versions of this document contained by
examining these change summaries. examining these change summaries.
o Moved specific comments about the IETF 90 discussions to o Moved specific comments about the IETF 90 discussions to
Acknowledgments and removed or edited some material that was only Acknowledgments and removed or edited some material that was only
appropriate for a discussion piece. appropriate for a discussion piece.
o Made several small editorial changes as usual. o Made several small editorial changes as usual.
B.4. Changes from draft-ietf-urnbis-semantics-clarif-01 (2015-02-14) to
-02
o Reissued to keep draft alive; no substantive changes.
o Updated references, including some that were already outdated in
-01.
Author's Address Author's Address
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. 15 change blocks. 
21 lines changed or deleted 40 lines changed or added

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