draft-ietf-dnsop-as112-dname-05.txt   draft-ietf-dnsop-as112-dname-06.txt 
Network Working Group J. Abley Network Working Group J. Abley
Internet-Draft Dyn, Inc. Internet-Draft Dyn, Inc.
Intended status: Informational B. Dickson Intended status: Informational B. Dickson
Expires: May 23, 2015 Twitter, Inc. Expires: May 28, 2015 Twitter, Inc.
W. Kumari W. Kumari
Google Google
G. Michaelson G. Michaelson
APNIC APNIC
November 19, 2014 November 24, 2014
AS112 Redirection using DNAME AS112 Redirection using DNAME
draft-ietf-dnsop-as112-dname-05 draft-ietf-dnsop-as112-dname-06
Abstract Abstract
AS112 provides a mechanism for handling reverse lookups on IP AS112 provides a mechanism for handling reverse lookups on IP
addresses that are not unique (e.g., RFC 1918 addresses). This addresses that are not unique (e.g., RFC 1918 addresses). This
document describes modifications to the deployment and use of AS112 document describes modifications to the deployment and use of AS112
infrastructure that will allow zones to be added and dropped much infrastructure that will allow zones to be added and dropped much
more easily, using DNAME resource records. more easily, using DNAME resource records.
This approach makes it possible for any DNS zone administrator to This approach makes it possible for any DNS zone administrator to
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 May 23, 2015. This Internet-Draft will expire on May 28, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 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
skipping to change at page 2, line 30 skipping to change at page 2, line 30
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Design Overview . . . . . . . . . . . . . . . . . . . . . . . 4 2. Design Overview . . . . . . . . . . . . . . . . . . . . . . . 4
3. AS112 Operations . . . . . . . . . . . . . . . . . . . . . . 4 3. AS112 Operations . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Extensions to Support DNAME Redirection . . . . . . . . . 4 3.1. Extensions to Support DNAME Redirection . . . . . . . . . 4
3.2. Redirection of Query Traffic to AS112 Servers . . . . . . 5 3.2. Redirection of Query Traffic to AS112 Servers . . . . . . 5
4. Continuity of AS112 Operations . . . . . . . . . . . . . . . 5 4. Continuity of AS112 Operations . . . . . . . . . . . . . . . 5
5. Candidate Zones for AS112 Redirection . . . . . . . . . . . . 6 5. Candidate Zones for AS112 Redirection . . . . . . . . . . . . 6
6. DNAME Deployment Considerations . . . . . . . . . . . . . . . 6 6. DNAME Deployment Considerations . . . . . . . . . . . . . . . 6
7. IAB Considerations . . . . . . . . . . . . . . . . . . . . . 7 7. IAB Statement Regarding this .ARPA Request . . . . . . . . . 7
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8.1. Address Assignment . . . . . . . . . . . . . . . . . . . 7 8.1. Address Assignment . . . . . . . . . . . . . . . . . . . 7
8.2. Hosting of AS112.ARPA . . . . . . . . . . . . . . . . . . 9 8.2. Hosting of AS112.ARPA . . . . . . . . . . . . . . . . . . 9
8.3. Delegation of AS112.ARPA . . . . . . . . . . . . . . . . 10 8.3. Delegation of AS112.ARPA . . . . . . . . . . . . . . . . 10
9. Security Considerations . . . . . . . . . . . . . . . . . . . 11 9. Security Considerations . . . . . . . . . . . . . . . . . . . 10
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
11.1. Normative References . . . . . . . . . . . . . . . . . . 11 11.1. Normative References . . . . . . . . . . . . . . . . . . 11
11.2. Informative References . . . . . . . . . . . . . . . . . 11 11.2. Informative References . . . . . . . . . . . . . . . . . 11
Appendix A. Assessing Support for DNAME in the Real World . . . 12 Appendix A. Assessing Support for DNAME in the Real World . . . 12
A.1. Methodology . . . . . . . . . . . . . . . . . . . . . . . 12 A.1. Methodology . . . . . . . . . . . . . . . . . . . . . . . 12
A.2. Results . . . . . . . . . . . . . . . . . . . . . . . . . 14 A.2. Results . . . . . . . . . . . . . . . . . . . . . . . . . 14
Appendix B. Editorial Notes . . . . . . . . . . . . . . . . . . 15 Appendix B. Editorial Notes . . . . . . . . . . . . . . . . . . 14
B.1. Change History . . . . . . . . . . . . . . . . . . . . . 15 B.1. Change History . . . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
Many sites connected to the Internet make use of IPv4 addresses that Many sites connected to the Internet make use of IPv4 addresses that
are not globally unique. Examples are the addresses designated in are not globally unique. Examples are the addresses designated in
[RFC1918] for private use within individual sites. [RFC1918] for private use within individual sites.
Devices in such environments may occasionally originate Domain Name Devices in such environments may occasionally originate Domain Name
System (DNS) queries (so-called "reverse lookups") corresponding to System (DNS) queries (so-called "reverse lookups") corresponding to
skipping to change at page 7, line 29 skipping to change at page 7, line 29
received CNAME RR should hence not limit the ability to sign the received CNAME RR should hence not limit the ability to sign the
redirection point, and for those signatures to be validated. redirection point, and for those signatures to be validated.
In the case where a recursive server implements DNAME, but DNAME is In the case where a recursive server implements DNAME, but DNAME is
not implemented in a stub resolver, CNAME synthesis will again not implemented in a stub resolver, CNAME synthesis will again
provide a viable path. provide a viable path.
DNAME support on AS112 nodes themselves is never required under this DNAME support on AS112 nodes themselves is never required under this
proposal. proposal.
7. IAB Considerations 7. IAB Statement Regarding this .ARPA Request
This document proposes a delegation within the ARPA domain, and, in
accordance with [RFC3172], IAB review and approval of the delegation
of AS112.ARPA as described in Section 8 is required.
Once IAB approval has been obtained, this section may be removed With the publication of this document, the IAB approves of the
prior to publication or updated to include text that confirms the delegation of 'AS112' in the ARPA domain. Under [RFC3172], the IAB
IAB's decision, at the IAB's discretion. has requested that IANA delegate and provision "AS112.ARPA" as
specified in this specification. However, the IAB does not take any
architectural or technical position about this specification.
8. IANA Considerations 8. IANA Considerations
8.1. Address Assignment 8.1. Address Assignment
This document requests that IANA assign IPv4 and IPv6 number This document requests that IANA assign IPv4 and IPv6 number
resources in conformance with section 4 of [RFC2860]. resources in conformance with section 4 of [RFC2860].
The IANA is requested to assign one IPv4 /24 netblock and register The IANA is requested to assign one IPv4 /24 netblock and register
its use in the IPv4 Special-Purpose Address Registry [RFC6890] as its use in the IPv4 Special-Purpose Address Registry [RFC6890] as
skipping to change at page 10, line 33 skipping to change at page 10, line 33
EMPTY NS BLACKHOLE EMPTY NS BLACKHOLE
Figure 2 Figure 2
8.3. Delegation of AS112.ARPA 8.3. Delegation of AS112.ARPA
Once the AS112.ARPA zone is being hosted in production, the IANA is Once the AS112.ARPA zone is being hosted in production, the IANA is
requested to arrange delegation from the ARPA zone according to requested to arrange delegation from the ARPA zone according to
normal IANA procedure for ARPA zone management, to the nameservers normal IANA procedure for ARPA zone management, to the nameservers
used in carrying out the direction in Section 8.2. The following used in carrying out the direction in Section 8.2. The whois contact
metadata is suggested for the delegation, but may be changed by the information for the new record should be specified by the IAB under
IANA if required: [RFC3172].
+----------------+--------------------------------------------------+
| Name | Value |
+----------------+--------------------------------------------------+
| Domain: | AS112.ARPA |
| | |
| Administrative | Internet Architecture Board (IAB) c/o IETF |
| Contact: | Administrative Support Activity, ISOC |
| | |
| Technical | Internet Assigned Numbers Authority (IANA) |
| Contact: | |
| | |
| Nameservers: | As chosen by the IANA, see Section 8.2 |
| | |
| DS-RDATA: | As chosen by the IANA, see Section 8.2 |
+----------------+--------------------------------------------------+
9. Security Considerations 9. Security Considerations
This document presents no known additional security concerns to the This document presents no known additional security concerns to the
Internet. Internet.
For security considerations relating to AS112 service in general, see For security considerations relating to AS112 service in general, see
[I-D.ietf-dnsop-rfc6304bis]. [I-D.ietf-dnsop-rfc6304bis].
10. Acknowledgements 10. Acknowledgements
skipping to change at page 15, line 35 skipping to change at page 15, line 20
02 Text in IANA Considerations section dealing with address 02 Text in IANA Considerations section dealing with address
assignments modified following informal advice received from Leo assignments modified following informal advice received from Leo
Vegoda. Vegoda.
03 Updated references to 6304 following guidance from working group 03 Updated references to 6304 following guidance from working group
chairs. chairs.
04 Corrected an error picked up by Bob Harold. 04 Corrected an error picked up by Bob Harold.
05 Addressed various comments from the IESG and IAB. Updated 05 Addressed various comments from the IESG and IAB. Updated Brian's
Brian's contact info. Minor spelling and grammatical corrections. contact info. Minor spelling and grammatical corrections. Added
Added text to the abstract and introduction to reinforce the point text to the abstract and introduction to reinforce the point that
that this approach allows liberal use of AS112 infrastructure this approach allows liberal use of AS112 infrastructure without
without coordination with AS112 operators. coordination with AS112 operators.
06 Made changes requested by the IAB relating to [RFC3172].
Authors' Addresses Authors' Addresses
Joe Abley Joe Abley
Dyn, Inc. Dyn, Inc.
186 Albert Street, Suite 103 186 Albert Street, Suite 103
London, ON N6A 1M1 London, ON N6A 1M1
Canada Canada
Phone: +1 519 670 9327 Phone: +1 519 670 9327
 End of changes. 11 change blocks. 
41 lines changed or deleted 25 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/