< draft-ietf-dnsop-as112-dname-02.txt   draft-ietf-dnsop-as112-dname-03.txt >
Network Working Group J. Abley Network Working Group J. Abley
Internet-Draft Dyn, Inc. Internet-Draft Dyn, Inc.
Updates: 6304 (if approved) B. Dickson Intended status: Informational B. Dickson
Intended status: Informational Verisign Labs Expires: September 20, 2014 Verisign Labs
Expires: August 18, 2014 W. Kumari W. Kumari
Google Google
G. Michaelson G. Michaelson
APNIC APNIC
February 14, 2014 March 19, 2014
AS112 Redirection using DNAME AS112 Redirection using DNAME
draft-ietf-dnsop-as112-dname-02 draft-ietf-dnsop-as112-dname-03
Abstract Abstract
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
RFC 1918 for private use within individual sites. RFC 1918 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
those private-use addresses. Since the addresses concerned have only those private-use addresses. Since the addresses concerned have only
skipping to change at page 2, line 15 skipping to change at page 2, line 15
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, 2014. This Internet-Draft will expire on September 20, 2014.
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 3, line 25 skipping to change at page 3, line 25
7. IAB Considerations . . . . . . . . . . . . . . . . . . . . . . 11 7. IAB Considerations . . . . . . . . . . . . . . . . . . . . . . 11
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
8.1. Address Assignment . . . . . . . . . . . . . . . . . . . . 12 8.1. Address Assignment . . . . . . . . . . . . . . . . . . . . 12
8.2. Hosting of AS112.ARPA . . . . . . . . . . . . . . . . . . 13 8.2. Hosting of AS112.ARPA . . . . . . . . . . . . . . . . . . 13
8.3. Delegation of AS112.ARPA . . . . . . . . . . . . . . . . . 14 8.3. Delegation of AS112.ARPA . . . . . . . . . . . . . . . . . 14
9. Security Considerations . . . . . . . . . . . . . . . . . . . 15 9. Security Considerations . . . . . . . . . . . . . . . . . . . 15
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
11.1. Normative References . . . . . . . . . . . . . . . . . . . 17 11.1. Normative References . . . . . . . . . . . . . . . . . . . 17
11.2. Informative References . . . . . . . . . . . . . . . . . . 17 11.2. Informative References . . . . . . . . . . . . . . . . . . 17
Appendix A. Assessing Support for DNAME in the Real World . . . . 19 Appendix A. Assessing Support for DNAME in the Real World . . . . 18
A.1. Methodology . . . . . . . . . . . . . . . . . . . . . . . 19 A.1. Methodology . . . . . . . . . . . . . . . . . . . . . . . 18
A.2. Results . . . . . . . . . . . . . . . . . . . . . . . . . 21 A.2. Results . . . . . . . . . . . . . . . . . . . . . . . . . 20
Appendix B. Editorial Notes . . . . . . . . . . . . . . . . . . . 22 Appendix B. Editorial Notes . . . . . . . . . . . . . . . . . . . 21
B.1. Change History . . . . . . . . . . . . . . . . . . . . . . 22 B.1. Change History . . . . . . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
The AS112 project is described in detail in [RFC6304]. The AS112 project is described in detail in [RFC6304bis].
The AS112 nameservers (PRISONER.IANA.ORG, BLACKHOLE-1.IANA.ORG and The AS112 nameservers (PRISONER.IANA.ORG, BLACKHOLE-1.IANA.ORG and
BLACKHOLE-2.IANA.ORG) are required to answer authoritatively for each BLACKHOLE-2.IANA.ORG) are required to answer authoritatively for each
and every zone that is delegated to them. and every zone that is delegated to them.
If a zone is delegated to AS112 nameservers without those nameservers If a zone is delegated to AS112 nameservers without those nameservers
being configured ahead of time to answer authoritatively for that being configured ahead of time to answer authoritatively for that
zone, there is a detrimental impact on clients following referrals zone, there is a detrimental impact on clients following referrals
for queries within that zone. This misconfiguration is colloquially for queries within that zone. This misconfiguration is colloquially
known as a "lame delegation". known as a "lame delegation".
skipping to change at page 5, line 22 skipping to change at page 5, line 22
address covered by that prefix is in use. The IPv6 address TBAv6-1 address covered by that prefix is in use. The IPv6 address TBAv6-1
has been similarly assigned such that no other address within a has been similarly assigned such that no other address within a
covering /48 is in use. This addressing plan accommodates the covering /48 is in use. This addressing plan accommodates the
anycast distribution of the BLACKHOLE.AS112.ARPA service using a anycast distribution of the BLACKHOLE.AS112.ARPA service using a
single IPv4 service prefix and a single IPv6 service prefix. See single IPv4 service prefix and a single IPv6 service prefix. See
[RFC4786] for more discussion of anycast service distribution; see [RFC4786] for more discussion of anycast service distribution; see
Section 8 for the specific requests this document makes of the IANA. Section 8 for the specific requests this document makes of the IANA.
Some or all of the existing AS112 nodes should be extended to support Some or all of the existing AS112 nodes should be extended to support
these new nameserver addresses, and to host the EMPTY.AS112.ARPA these new nameserver addresses, and to host the EMPTY.AS112.ARPA
zone. See [I-D.jabley-dnsop-rfc6304bis] for revised guidance to zone. See [RFC6304bis] for revised guidance to AS112 server
AS112 server operators. operators.
Each part of the DNS namespace for which it is desirable to sink Each part of the DNS namespace for which it is desirable to sink
queries at AS112 nameservers should be redirected to the queries at AS112 nameservers should be redirected to the
EMPTY.AS112.ARPA zone using DNAME [RFC6672]. See Section 3.2 for EMPTY.AS112.ARPA zone using DNAME [RFC6672]. See Section 3.2 for
guidance to zone administrators. guidance to zone administrators.
3. AS112 Operations 3. AS112 Operations
3.1. Extensions to Support DNAME Redirection 3.1. Extensions to Support DNAME Redirection
The guidance provided in [RFC6304] is extended to include Guidance to operators of AS112 nodes is extended to include
configuration of the TBAv4-1, and TBAv6-1 addresses, and the configuration of the TBAv4-1, and TBAv6-1 addresses, and the
corresponding announcement of covering routes for those addresses, corresponding announcement of covering routes for those addresses,
and to host the EMPTY.AS112.ARPA zone. and to host the EMPTY.AS112.ARPA zone.
IPv4-only AS112 nodes should only configure the TBAv4-1 nameserver IPv4-only AS112 nodes should only configure the TBAv4-1 nameserver
address; IPv6-only AS112 nodes should only configure the TBAv6-1 address; IPv6-only AS112 nodes should only configure the TBAv6-1
nameserver address. nameserver address.
It is only necessary for a single AS112 server operator to implement It is only necessary for a single AS112 server operator to implement
these extensions for this mechanism to function as intended. It is these extensions for this mechanism to function as intended. It is
beneficial if many more than one AS112 server operators make these beneficial if many more than one AS112 server operators make these
changes, however, since that provides for greater distribution and changes, however, since that provides for greater distribution and
capacity for the nameservers serving the EMPTY.AS112.ARPA zone. It capacity for the nameservers serving the EMPTY.AS112.ARPA zone. It
is not necessary for all AS112 server operators to make these changes is not necessary for all AS112 server operators to make these changes
for the mechanism to be viable. for the mechanism to be viable.
Detailed instructions for the implementation of these extensions is Detailed instructions for the implementation of these extensions is
included in [I-D.jabley-dnsop-rfc6304bis]. included in [RFC6304bis].
3.2. Redirection of Query Traffic to AS112 Servers 3.2. Redirection of Query Traffic to AS112 Servers
Once the EMPTY.AS112.ARPA zone has been deployed using the Once the EMPTY.AS112.ARPA zone has been deployed using the
nameservers described in Section 3.1, redirections may be installed nameservers described in Section 3.1, redirections may be installed
in the DNS namespace for queries that are intended to be answered by in the DNS namespace for queries that are intended to be answered by
the AS112 infrastructure. the AS112 infrastructure.
For example, reverse queries corresponding to TEST-NET-1 For example, reverse queries corresponding to TEST-NET-1
(192.0.2.0/24) [RFC5737] could be redirected to AS112 nameservers by (192.0.2.0/24) [RFC5737] could be redirected to AS112 nameservers by
skipping to change at page 15, line 11 skipping to change at page 15, line 11
| | | | | |
| DS-RDATA: | 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
[RFC6304]. [RFC6304bis].
10. Acknowledgements 10. Acknowledgements
Your name here, etc. Your name here, etc.
11. References 11. References
11.1. Normative References 11.1. Normative References
[I-D.jabley-dnsop-rfc6304bis]
Abley, J. and W. Maton, "AS112 Nameserver Operations",
draft-jabley-dnsop-rfc6304bis-00 (work in progress),
February 2014.
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987. specification", STD 13, RFC 1035, November 1987.
[RFC2308] Andrews, M., "Negative Caching of DNS Queries (DNS [RFC2308] Andrews, M., "Negative Caching of DNS Queries (DNS
NCACHE)", RFC 2308, March 1998. NCACHE)", RFC 2308, March 1998.
[RFC6304] Abley, J. and W. Maton, "AS112 Nameserver Operations", [RFC6304bis]
RFC 6304, July 2011. Abley, J. and W. Maton, "AS112 Nameserver Operations",
draft-ietf-dnsop-rfc6304bis-00 (work in progress),
February 2014.
[RFC6672] Rose, S. and W. Wijngaards, "DNAME Redirection in the [RFC6672] Rose, S. and W. Wijngaards, "DNAME Redirection in the
DNS", RFC 6672, June 2012. DNS", RFC 6672, June 2012.
11.2. Informative References 11.2. Informative References
[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
E. Lear, "Address Allocation for Private Internets", E. Lear, "Address Allocation for Private Internets",
BCP 5, RFC 1918, February 1996. BCP 5, RFC 1918, February 1996.
skipping to change at page 22, line 24 skipping to change at page 21, line 24
01 Some particularly egregious spelling mistakes fixed. Warren 01 Some particularly egregious spelling mistakes fixed. Warren
Kumari and George Michaelson added as co-authors. Intended status Kumari and George Michaelson added as co-authors. Intended status
changed to informational. Appendix on DNAME testing added, changed to informational. Appendix on DNAME testing added,
describing an experiment conducted by Geoff Huston and George describing an experiment conducted by Geoff Huston and George
Michaelson. Michaelson.
00 Adopted by dnsop in IETF88, Vancouver; resubmitted as 00 Adopted by dnsop in IETF88, Vancouver; resubmitted as
draft-ietf-dnsop-as112-dname. Changed contact info for Brian. draft-ietf-dnsop-as112-dname. Changed contact info for Brian.
01 Minor updates following submission of 01 Minor updates following submission of
[I-D.jabley-dnsop-rfc6304bis]. draft-jabley-dnsop-rfc6304bis.
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
chairs.
Authors' Addresses Authors' Addresses
Joe Abley Joe Abley
Dyn, Inc. Dyn, Inc.
470 Moore Street 470 Moore Street
London, ON N6C 2C2 London, ON N6C 2C2
Canada Canada
Phone: +1 519 670 9327 Phone: +1 519 670 9327
Email: jabley@dyn.com Email: jabley@dyn.com
 End of changes. 14 change blocks. 
26 lines changed or deleted 26 lines changed or added

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