draft-ietf-urn-net-procedures-06.txt   draft-ietf-urn-net-procedures-07.txt 
Network Working Group M. Mealling Network Working Group M. Mealling
Internet-Draft Network Solutions, Inc. Internet-Draft Verisign
Expires: May 2, 2001 November 1, 2000 Expires: August 9, 2001 February 8, 2001
Assignment Procedures for URI Resolution Using DNS Assignment Procedures for URI Resolution Using DNS
draft-ietf-urn-net-procedures-06 draft-ietf-urn-net-procedures-07
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 other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as reference at any 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 To view the entire list of Internet-Draft Shadow Directories, see
http://www.ietf.org/ietf/1id-abstracts.txt
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 May 2, 2001. This Internet-Draft will expire on August 9, 2001.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2000). 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 document specifies that the first step in that algorithm is to
append 'URI.ARPA' to the URI scheme and retrieve the NAPTR record append 'URI.ARPA' to the URI scheme and retrieve the NAPTR record
for that domain-name. I.e., the first step in resolving for that domain-name. I.e., the first step in resolving
"http://foo.com/" would be to look up a NAPTR record for the domain "http://foo.com/" would be to look up a NAPTR record for the domain
"http.URI.ARPA". URN resolution also follows a similar procedure but "http.URI.ARPA". URN resolution also follows a similar procedure but
skipping to change at page 2, line 28 skipping to change at page 2, line 28
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 . . . . . . . . . . . . . . . . . . . . . . . . . 6
6.3 Records . . . . . . . . . . . . . . . . . . . . . . . . . . 6 6.3 Records . . . . . . . . . . . . . . . . . . . . . . . . . . 6
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. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 10. Security Considerations . . . . . . . . . . . . . . . . . . 7
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
References . . . . . . . . . . . . . . . . . . . . . . . . . 8 References . . . . . . . . . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . 9
Full Copyright Statement . . . . . . . . . . . . . . . . . . 9 Full Copyright Statement . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
This document defines the policies and procedures for inserting This document defines the policies and procedures for inserting
NAPTR records into the 'URI.ARPA' and 'URN.ARPA' zones for the NAPTR records into the 'URI.ARPA' and 'URN.ARPA' zones for the
purpose of resolving URIs according to "URI Resolution using the purpose of resolving URIs according to "URI Resolution using the
Dynamic Delegation Discovery System" (RFCXXXX)[7], which is an Dynamic Delegation Discovery System" (RFCXXXX)[7], which is an
Application that uses the DNS based DDDS Database defined in Application that uses the DNS based DDDS Database defined in
RFCYYYY[6]. The algorithm expressed by these Rules is specified in RFCYYYY[6]. The algorithm expressed by these Rules is specified in
"Dynamic Delegation Discovery System (DDDS) (RFCZZZZ)[8]. "Dynamic Delegation Discovery System (DDDS) (RFCZZZZ)[8].
skipping to change at page 6, line 20 skipping to change at page 6, line 20
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'.
o Registrations for the 'URN.ARPA' zone are sent to o Registrations for the 'URN.ARPA' zone are sent to
'register@URN.ARPA'. 'register@URN.ARPA'.
At this time the registration authority is expected to be the IANA. The registration authority is the Internet Assigned Numbers
Authority (IANA).
Objections are restricted to those that point out impacts on the Objections are restricted to those that point out impacts on the
zone itself or to DNS in general. Objections to the URL scheme or to zone itself or to DNS in general. Objections to the URL scheme or to
the URN namespace-id are not allowed, as these should be raised in the URN namespace-id are not allowed, as these should be raised in
their respective forums. The logical conclusion of this is that ANY their respective forums. The logical conclusion of this is that ANY
sanctioned URL scheme or URN namespace MUST be allowed to be sanctioned URL scheme or URN namespace MUST be allowed to be
registered if it meets the requirements specified in this document registered if it meets the requirements specified in this document
as regards times to live and general impact to the DNS. as regards times to live and general impact to the DNS.
6. Registration Template 6. Registration Template
skipping to change at page 7, line 46 skipping to change at page 7, line 47
o to create and maintain (or designate some other entity to o to create and maintain (or designate some other entity to
maintain) a primary nameserver for the URI.ARPA and URN.ARPA maintain) a primary nameserver for the URI.ARPA and URN.ARPA
zones. From time to time the IANA may delegate or change zones. From time to time the IANA may delegate or change
delegation of operations at its discretion. delegation of operations at its discretion.
o to maintain the mailing lists "register@URI.ARPA" and o to maintain the mailing lists "register@URI.ARPA" and
"register@URN.ARPA" as the forum for discussions of submissions; "register@URN.ARPA" as the forum for discussions of submissions;
and and
o to act as the party that determines if all objections have been o to act as the party that determines if all objections have been
noted and accommodated. noted and accommodated.
10. Acknowledgements 10. Security Considerations
The 'uri.arpa' and 'urn.arpa' zones will be a common point of attack
both for Denial of Service and for spoofing entries in order to
redirect delegation paths. Any entity running nameservers that
contain these zones should take appropriate action for securing an
infrastructure level component of the Internet. When it becomes
possible for a nameserver to reliably sign the records in its zone
it should do so.
11. Acknowledgements
The author would like to thank Ron Daniel who was originally The author would like to thank Ron Daniel who was originally
co-author of these documents. Ron's original insite into the co-author of these documents. Ron's original insite into the
intricate nature of delegation rules made these procedures and the intricate nature of delegation rules made these procedures and the
DDDS itself possible. DDDS itself possible.
References References
[1] Moats, R., "URN Syntax", RFC 2141, November 1998. [1] Moats, R., "URN Syntax", RFC 2141, November 1998.
skipping to change at page 8, line 37 skipping to change at page 9, line 8
[7] Mealling, M., "URI Resolution using the Dynamic Delegation [7] Mealling, M., "URI Resolution using the Dynamic Delegation
Discovery System", Internet-Draft Discovery System", Internet-Draft
draft-ietf-urn-uri-res-ddds-00.txt, July 2000. draft-ietf-urn-uri-res-ddds-00.txt, July 2000.
[8] Mealling, M., "Dynamic Delegation Discovery System (DDDS)", [8] Mealling, M., "Dynamic Delegation Discovery System (DDDS)",
Internet-Draft draft-ietf-urn-ddds-00.txt, May 2000. Internet-Draft draft-ietf-urn-ddds-00.txt, May 2000.
Author's Address Author's Address
Michael Mealling Michael Mealling
Network Solutions, Inc. Verisign
505 Huntmar Park Drive 505 Huntmar Park Drive
Herndon, VA 22070 Herndon, VA 22070
US US
Phone: (703) 742-0400 Phone: (770) 721-2251
EMail: michaelm@netsol.com EMail: michaelm@netsol.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implmentation may be prepared, copied, published or assist in its implmentation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 12 change blocks. 
17 lines changed or deleted 26 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/