draft-ietf-urn-net-procedures-08.txt   draft-ietf-urn-net-procedures-09.txt 
Network Working Group M. Mealling Network Working Group M. Mealling
Internet-Draft Verisign Internet-Draft Verisign
Expires: November 23, 2001 May 25, 2001 Expires: April 28, 2002 October 28, 2001
Assignment Procedures for URI Resolution Using DNS Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA
draft-ietf-urn-net-procedures-08 Assignment Procedures
draft-ietf-urn-net-procedures-09.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 31 skipping to change at page 1, line 32
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 23, 2001. This Internet-Draft will expire on April 28, 2002.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
Abstract Abstract
RFCYYYY defines a how DNS is used as a DDDS database that contains RFCYYYY defines a how DNS is used as a DDDS database that contains
URI delegation rules (sometimes called resolution hints). That URI delegation rules (sometimes called resolution hints). That
document specifies that the first step in that algorithm is to append document specifies that the first step in that algorithm is to append
'URI.ARPA' to the URI scheme and retrieve the NAPTR record for that 'URI.ARPA' to the URI scheme and retrieve the NAPTR record for that
domain-name. I.e., the first step in resolving "http://foo.com/" domain-name. I.e., the first step in resolving "http://foo.com/"
would be to look up a NAPTR record for the domain "http.URI.ARPA". would be to look up a NAPTR record for the domain "http.URI.ARPA".
URN resolution also follows a similar procedure but uses the URN resolution also follows a similar procedure but uses the
'URN.ARPA' zone as its root. This document describes the procedures 'URN.ARPA' zone as its root. This document describes the procedures
for inserting a new rule into the 'URI.ARPA' and 'URN.ARPA' zones. for inserting a new rule into the 'URI.ARPA' and 'URN.ARPA' zones.
This document is fifth in a series that is completely specified in
"Dynamic Delegation Discovery System (DDDS) Part One: The
Comprehensive DDDS Standard" (RFC WWWW). It is very important to
note that it is impossible to read and understand any document in
this series without reading the others.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. URI Resolution vs URN Resolution . . . . . . . . . . . . . . 3 2. URI Resolution vs URN Resolution . . . . . . . . . . . . . . 3
3. Registration Policies . . . . . . . . . . . . . . . . . . . 3 3. Registration Policies . . . . . . . . . . . . . . . . . . . 3
3.1 URI.ARPA Registration . . . . . . . . . . . . . . . . . . . 3 3.1 URI.ARPA Registration . . . . . . . . . . . . . . . . . . . 3
3.1.1 Only Schemes in the IETF Tree Allowed . . . . . . . . . . . 3 3.1.1 Only Schemes in the IETF Tree Allowed . . . . . . . . . . . 3
3.1.2 Scheme Registration Takes Precedence . . . . . . . . . . . . 3 3.1.2 Scheme Registration Takes Precedence . . . . . . . . . . . . 3
3.1.3 NAPTR Registration May Accompany Scheme Registration . . . . 4 3.1.3 NAPTR Registration May Accompany Scheme Registration . . . . 4
3.1.4 Registration or Changes after Scheme Registration . . . . . 4 3.1.4 Registration or Changes after Scheme Registration . . . . . 4
3.2 URN.ARPA Registration . . . . . . . . . . . . . . . . . . . 4 3.2 URN.ARPA Registration . . . . . . . . . . . . . . . . . . . 4
3.2.1 NID Registration Takes Precedence . . . . . . . . . . . . . 4 3.2.1 NID Registration Takes Precedence . . . . . . . . . . . . . 4
3.2.2 NAPTR Registration May Accompany NID Registration . . . . . 4 3.2.2 NAPTR Registration May Accompany NID Registration . . . . . 4
3.2.3 Registration or Changes after Scheme Registration . . . . . 4 3.2.3 Registration or Changes after Scheme Registration . . . . . 4
4. Requirements on hints . . . . . . . . . . . . . . . . . . . 5 4. Requirements on hints . . . . . . . . . . . . . . . . . . . 5
5. Submission Procedure . . . . . . . . . . . . . . . . . . . . 6 5. Submission Procedure . . . . . . . . . . . . . . . . . . . . 6
6. Registration Template . . . . . . . . . . . . . . . . . . . 6 6. Registration Template . . . . . . . . . . . . . . . . . . . 6
6.1 Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 6.1 Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6.2 Authority . . . . . . . . . . . . . . . . . . . . . . . . . 6 6.2 Authority . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.3 Records . . . . . . . . . . . . . . . . . . . . . . . . . . 7 6.3 Records . . . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Example Template . . . . . . . . . . . . . . . . . . . . . . 7 7. Example Template . . . . . . . . . . . . . . . . . . . . . . 7
8. The URN Registration in the URI.ARPA zone . . . . . . . . . 7 8. The URN Registration in the URI.ARPA zone . . . . . . . . . 7
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . 7 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . 7
10. Security Considerations . . . . . . . . . . . . . . . . . . 8 10. Security Considerations . . . . . . . . . . . . . . . . . . 8
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
References . . . . . . . . . . . . . . . . . . . . . . . . . 8 References . . . . . . . . . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . 9 Author's Address . . . . . . . . . . . . . . . . . . . . . . 9
Full Copyright Statement . . . . . . . . . . . . . . . . . . 10 Full Copyright Statement . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
This document defines the policies and procedures for inserting NAPTR This document defines the policies and procedures for inserting NAPTR
records into the 'URI.ARPA' and 'URN.ARPA' zones for the purpose of records into the 'URI.ARPA' and 'URN.ARPA' zones for the purpose of
resolving URIs according to "URI Resolution using the Dynamic resolving URIs according to "Dynamic Delegation Discovery System
Delegation Discovery System" (RFCXXXX) [7], which is an Application (DDDS) Part Four: The URI Resolution Application" (RFCXXXX) [2],
that uses the DNS based DDDS Database defined in RFCYYYY [6]. The which is an Application that uses the DNS based DDDS Database. All
algorithm expressed by these Rules is specified in "Dynamic of these concepts are defined in RFC WWWW [1]. It is very important
Delegation Discovery System (DDDS) (RFCZZZZ) [8]. to note that it is impossible to correctly understand this document
without reading RFC WWWW and the documents it specifies.
2. URI Resolution vs URN Resolution 2. URI Resolution vs URN Resolution
RFCXXXX [7] defines how both URI [2] resolution and URN [1] RFCXXXX [2] defines how both URI [7] resolution and URN [6]
resolution work when DNS is used as the delegation rule (or hint) resolution work when DNS is used as the delegation rule (or hint)
database. Specifically it says that the initial instructions database. Specifically it says that the initial instructions
('hints') for DNS-based resolution of URIs are stored as resource ('hints') for DNS-based resolution of URIs are stored as resource
records in the 'URI.ARPA' DNS zone. records in the 'URI.ARPA' DNS zone.
Since a URN is a URI scheme, a hint for resolution of the URI prefix Since a URN is a URI scheme, a hint for resolution of the URI prefix
'urn:' will also be stored in the 'URI.ARPA' zone. This rule states 'urn:' will also be stored in the 'URI.ARPA' zone. This rule states
that the namespace id [1] is extracted, 'URN.ARPA' is appended to the that the namespace id [6] is extracted, 'URN.ARPA' is appended to the
end of the namespace id, and the result is used as the key for end of the namespace id, and the result is used as the key for
retrieval of a subsequent NAPTR record [6]. retrieval of a subsequent NAPTR record [4].
3. Registration Policies 3. Registration Policies
The creation of a given URI scheme or URN namespace id (NID) follows The creation of a given URI scheme or URN namespace id (NID) follows
the appropriate registration documents for those spaces. URI schemes the appropriate registration documents for those spaces. URI schemes
follow "Registration Procedures for URL Scheme Names" (RFC 2717) follow "Registration Procedures for URL Scheme Names" (RFC 2717)
[5]. URN namespace ids follow "URN Namespace Definition Mechanisms" [10]. URN namespace ids follow "URN Namespace Definition Mechanisms"
(RFC 2611) (or updates thereto) [4]. (RFC 2611) (or updates thereto) [9].
3.1 URI.ARPA Registration 3.1 URI.ARPA Registration
3.1.1 Only Schemes in the IETF Tree Allowed 3.1.1 Only Schemes in the IETF Tree Allowed
In order to be inserted into the URI.ARPA zone, the subsequent URI In order to be inserted into the URI.ARPA zone, the subsequent URI
scheme MUST be registered under the IETF URI tree. The requirements scheme MUST be registered under the IETF URI tree. The requirements
for this tree are specified in [5]. for this tree are specified in [10].
3.1.2 Scheme Registration Takes Precedence 3.1.2 Scheme Registration Takes Precedence
The registration of a NAPTR record for a URI scheme MUST NOT precede The registration of a NAPTR record for a URI scheme MUST NOT precede
proper registration of that scheme and publication of a stable proper registration of that scheme and publication of a stable
specification in accordance with [5]. The IESG or its designated specification in accordance with [10]. The IESG or its designated
expert will review the request for expert will review the request for
1. correctness and technical soundness 1. correctness and technical soundness
2. consistency with the published URI specification, and 2. consistency with the published URI specification, and
3. to ensure that the NAPTR record for a DNS-based URI does not 3. to ensure that the NAPTR record for a DNS-based URI does not
delegate resolution of the URI to a party other than the holder delegate resolution of the URI to a party other than the holder
of the DNS name. This last rule is to insure that a given URI's of the DNS name. This last rule is to insure that a given URI's
resolution hint doesn't hijack (inadvertently or otherwise) resolution hint doesn't hijack (inadvertently or otherwise)
network traffic for a given domain. network traffic for a given domain.
3.1.3 NAPTR Registration May Accompany Scheme Registration 3.1.3 NAPTR Registration May Accompany Scheme Registration
skipping to change at page 4, line 15 skipping to change at page 4, line 17
3. to ensure that the NAPTR record for a DNS-based URI does not 3. to ensure that the NAPTR record for a DNS-based URI does not
delegate resolution of the URI to a party other than the holder delegate resolution of the URI to a party other than the holder
of the DNS name. This last rule is to insure that a given URI's of the DNS name. This last rule is to insure that a given URI's
resolution hint doesn't hijack (inadvertently or otherwise) resolution hint doesn't hijack (inadvertently or otherwise)
network traffic for a given domain. network traffic for a given domain.
3.1.3 NAPTR Registration May Accompany Scheme Registration 3.1.3 NAPTR Registration May Accompany Scheme Registration
A request for a URI.ARPA registration MAY accompany a request for a A request for a URI.ARPA registration MAY accompany a request for a
URI scheme (in accordance with [5]), in which case both requests will URI scheme (in accordance with [10]), in which case both requests
be reviewed simultaneously by IESG or its designated experts. will be reviewed simultaneously by IESG or its designated experts.
3.1.4 Registration or Changes after Scheme Registration 3.1.4 Registration or Changes after Scheme Registration
A request for a NAPTR record (or an request to change an existing A request for a NAPTR record (or an request to change an existing
NAPTR record) MAY be submitted after the URI prefix has been NAPTR record) MAY be submitted after the URI prefix has been
registered. If the specification for the URI prefix is controlled registered. If the specification for the URI prefix is controlled
by some other party than IETF, IESG will require approval from the by some other party than IETF, IESG will require approval from the
owner/maintainer of that specification before the registration will owner/maintainer of that specification before the registration will
be accepted. This is in addition to any technical review of the be accepted. This is in addition to any technical review of the
NAPTR registration done by IESG or its designated experts. NAPTR registration done by IESG or its designated experts.
3.2 URN.ARPA Registration 3.2 URN.ARPA Registration
3.2.1 NID Registration Takes Precedence 3.2.1 NID Registration Takes Precedence
The registration of a NAPTR record for a URN NID MUST NOT precede The registration of a NAPTR record for a URN NID MUST NOT precede
proper registration of that NID and publication of a stable proper registration of that NID and publication of a stable
specification in accordance with [4]. This is to prevent the specification in accordance with [9]. This is to prevent the
registration of a NAPTR record in URN.ARPA from circumventing the NID registration of a NAPTR record in URN.ARPA from circumventing the NID
registration process. registration process.
3.2.2 NAPTR Registration May Accompany NID Registration 3.2.2 NAPTR Registration May Accompany NID Registration
A request for a URN.ARPA registration MAY accompany a request for a A request for a URN.ARPA registration MAY accompany a request for a
NID (in accordance with [4]), in which case both requests will be NID (in accordance with [9]), in which case both requests will be
reviewed at the same time. reviewed at the same time.
3.2.3 Registration or Changes after Scheme Registration 3.2.3 Registration or Changes after Scheme Registration
A request for a NAPTR record (or an request to change an existing A request for a NAPTR record (or an request to change an existing
NAPTR record) MAY be submitted after the NID has been registered. NAPTR record) MAY be submitted after the NID has been registered.
If the specification for the NID is controlled by some other party If the specification for the NID is controlled by some other party
than IETF, IESG will require approval from the owner/maintainer of than IETF, IESG will require approval from the owner/maintainer of
that specification before the registration will be accepted. This is that specification before the registration will be accepted. This is
in addition to any technical review of the NAPTR registration done by in addition to any technical review of the NAPTR registration done by
skipping to change at page 6, line 13 skipping to change at page 6, line 15
http IN NAPTR 100 100 "" "" "/http:\\/\\/([^\\/:]+)/\\2/i" . http IN NAPTR 100 100 "" "" "/http:\\/\\/([^\\/:]+)/\\2/i" .
Thus, the second step of resolution is to use the domain-name found Thus, the second step of resolution is to use the domain-name found
in the URL as the next key in the cycle. If, for example, that NAPTR in the URL as the next key in the cycle. If, for example, that NAPTR
was terminal and contains some hostname in the replacement field, was terminal and contains some hostname in the replacement field,
then the client could contact that host in order to ask questions then the client could contact that host in order to ask questions
about this particular URI. about this particular URI.
5. Submission Procedure 5. Submission Procedure
Using the MIME Content-Type registration mechanism [3] as a model Using the MIME Content-Type registration mechanism [8] as a model
for a successful registration mechanism, the 'URI.ARPA' and for a successful registration mechanism, the 'URI.ARPA' and
'URN.ARPA' procedures consist of a request template submitted to an 'URN.ARPA' procedures consist of a request template submitted to an
open mailing list made up of interested parties. If no objections open mailing list made up of interested parties. If no objections
are made within a two week period, a representative of the are made within a two week period, a representative of the
registration authority considers the submission to be accepted and registration authority considers the submission to be accepted and
enters that submission into the nameserver. enters that submission into the nameserver.
o Registrations for the 'URI.ARPA' zone are sent to o Registrations for the 'URI.ARPA' zone are sent to
'register@URI.ARPA'. 'register@URI.ARPA'.
skipping to change at page 7, line 5 skipping to change at page 7, line 9
This is the URN NID or URL scheme, which is used as the domain This is the URN NID or URL scheme, which is used as the domain
portion of the DNS entry. It must be valid according to the portion of the DNS entry. It must be valid according to the
procedures specified in the URN namespace-id assignment document and procedures specified in the URN namespace-id assignment document and
any future standards for registering new URL schemes. any future standards for registering new URL schemes.
6.2 Authority 6.2 Authority
This is the individual or organization (entity) which has authority This is the individual or organization (entity) which has authority
for registering the record. It must be an authority recognized as for registering the record. It must be an authority recognized as
either the IESG or any authority defined in the URN NID [4] or URL either the IESG or any authority defined in the URN NID [9] or URL
scheme registration [5] documents. scheme registration [10] documents.
6.3 Records 6.3 Records
The actual DNS records representing the rule set for the key. The The actual DNS records representing the rule set for the key. The
required values are Preference, Order, Flags, Services, Regex, and required values are Preference, Order, Flags, Services, Regex, and
Replacement as defined by RFCYYYY [6]. Replacement as defined by RFCYYYY [4].
7. Example Template 7. Example Template
To: register@URN.ARPA To: register@URN.ARPA
From: joe@foo.com From: joe@foo.com
Key: foo Key: foo
Authority: Foo Technology, Inc as specified in RFCFOO Authority: Foo Technology, Inc as specified in RFCFOO
Record: foo IN NAPTR 100 100 "" "" "" urn.foo.com. Record: foo IN NAPTR 100 100 "" "" "" urn.foo.com.
skipping to change at page 8, line 26 skipping to change at page 8, line 29
11. Acknowledgements 11. Acknowledgements
The author would like to thank Ron Daniel who was originally co- The author would like to thank Ron Daniel who was originally co-
author of these documents. Ron's original insite into the intricate author of these documents. Ron's original insite into the intricate
nature of delegation rules made these procedures and the DDDS itself nature of delegation rules made these procedures and the DDDS itself
possible. possible.
References References
[1] Moats, R., "URN Syntax", RFC 2141, November 1998. [1] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
One: The Comprehensive DDDS Standard", RFC WWWW, draft-ietf-
urn-ddds-toc-00.txt (work in progress), October 2001.
[2] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource [2] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
Identifiers (URI): Generic Syntax", RFC 2396, August 1998. Two: The Algorithm", RFC XXXX, draft-ietf-urn-ddds-05.txt (work
in progress), May 2000.
[3] Freed, N., Klensin, J. and J. Postel, "Multipurpose Internet [3] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
Three: The DNS Database", RFC ZZZZ, draft-ietf-urn-dns-ddds-
database-07.txt (work in progress), May 2000.
[4] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
Four: The URI Resolution Application", RFC YYYY, draft-ietf-
urn-uri-res-ddds-05.txt (work in progress), October 2000.
[5] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
Five: URI.ARPA Assignment Procedures", RFC VVVV, draft-ietf-
urn-net-procedures-09.txt (work in progress), October 2001.
[6] Moats, R., "URN Syntax", RFC 2141, November 1998.
[7] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
Resource Identifiers (URI): Generic Syntax", RFC 2396, August
1998.
[8] Freed, N., Klensin, J. and J. Postel, "Multipurpose Internet
Mail Extensions (MIME) Part Four: Registration Procedures", RFC Mail Extensions (MIME) Part Four: Registration Procedures", RFC
2048, November 1996. 2048, November 1996.
[4] Faltstrom, P., Iannella, R., Daigle, L. and D. van Gulik, "URN [9] Faltstrom, P., Iannella, R., Daigle, L. and D. van Gulik, "URN
Namespace Definition Mechanisms", RFC 2611, October 1998. Namespace Definition Mechanisms", RFC 2611, October 1998.
[5] Petke, R. and I. King, "Registration Procedures for URL Scheme [10] Petke, R. and I. King, "Registration Procedures for URL Scheme
Names", RFC 2717, January 1999. Names", RFC 2717, January 1999.
[6] Mealling, M., "A DDDS Database Using The Domain Name System",
draft-ietf-urn-dns-ddds-database-00.txt (work in progress), May
2000.
[7] Mealling, M., "URI Resolution using the Dynamic Delegation
Discovery System", draft-ietf-urn-uri-res-ddds-00.txt (work in
progress), July 2000.
[8] Mealling, M., "Dynamic Delegation Discovery System (DDDS)",
draft-ietf-urn-ddds-00.txt (work in progress), May 2000.
Author's Address Author's Address
Michael Mealling Michael Mealling
Verisign Verisign
505 Huntmar Park Drive 505 Huntmar Park Drive
Herndon, VA 22070 Herndon, VA 22070
US US
Phone: (770) 721-2251 Phone: (770) 721-2251
EMail: michael@research.netsol.com EMail: michael@research.netsol.com
 End of changes. 26 change blocks. 
43 lines changed or deleted 61 lines changed or added

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