draft-ietf-dnsop-as112-ops-08.txt   draft-ietf-dnsop-as112-ops-09.txt 
Network Working Group J. Abley Network Working Group J. Abley
Internet-Draft ICANN Internet-Draft ICANN
Intended status: Informational W. Maton Intended status: Informational W. Maton
Expires: October 31, 2011 NRC-CNRC Expires: November 12, 2011 NRC-CNRC
April 29, 2011 May 11, 2011
AS112 Nameserver Operations AS112 Nameserver Operations
draft-ietf-dnsop-as112-ops-08 draft-ietf-dnsop-as112-ops-09
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 6 skipping to change at page 2, line 6
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 October 31, 2011. This Internet-Draft will expire on November 12, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 30 skipping to change at page 3, line 30
4.2. Downtime . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.2. Downtime . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3. Statistics and Measurement . . . . . . . . . . . . . . . . 13 4.3. Statistics and Measurement . . . . . . . . . . . . . . . . 13
5. Communications . . . . . . . . . . . . . . . . . . . . . . . . 14 5. Communications . . . . . . . . . . . . . . . . . . . . . . . . 14
6. On the Future of AS112 Nodes . . . . . . . . . . . . . . . . . 15 6. On the Future of AS112 Nodes . . . . . . . . . . . . . . . . . 15
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
8. Security Considerations . . . . . . . . . . . . . . . . . . . 17 8. Security Considerations . . . . . . . . . . . . . . . . . . . 17
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
10.1. Normative References . . . . . . . . . . . . . . . . . . . 19 10.1. Normative References . . . . . . . . . . . . . . . . . . . 19
10.2. Informative References . . . . . . . . . . . . . . . . . . 19 10.2. Informative References . . . . . . . . . . . . . . . . . . 19
Appendix A. History . . . . . . . . . . . . . . . . . . . . . . . 22 Appendix A. History . . . . . . . . . . . . . . . . . . . . . . . 21
Appendix B. Change History . . . . . . . . . . . . . . . . . . . 23 Appendix B. Change History . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23
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) [RFC1034] queries (so-called "reverse lookups") System (DNS) [RFC1034] queries (so-called "reverse lookups")
corresponding to those private-use addresses. Since the addresses corresponding to those private-use addresses. Since the addresses
skipping to change at page 4, line 35 skipping to change at page 5, line 5
the IN-ADDR.ARPA authoritative servers [RFC5855]. the IN-ADDR.ARPA authoritative servers [RFC5855].
The AS112 project encompasses a loosely coordinated collection of The AS112 project encompasses a loosely coordinated collection of
independently operated nameservers. Each nameserver functions as a independently operated nameservers. Each nameserver functions as a
single node in an AS112 anycast cloud [RFC4786], and is configured to single node in an AS112 anycast cloud [RFC4786], and is configured to
answer authoritatively for a particular set of nominated zones. answer authoritatively for a particular set of nominated zones.
The AS112 project is named after the Autonomous System Number (ASN) The AS112 project is named after the Autonomous System Number (ASN)
that was assigned to it. that was assigned to it.
It is noted that recent guidance exists on the choice of origin ASN
for anycast services that is inconsistent with the choices made in
the AS112 project [I-D.ietf-grow-unique-origin-as].
2. AS112 DNS Service 2. AS112 DNS Service
2.1. Zones 2.1. Zones
AS112 nameservers answer authoritatively for the following zones, AS112 nameservers answer authoritatively for the following zones,
corresponding to [RFC1918] private-use netblocks: corresponding to [RFC1918] private-use netblocks:
o 10.IN-ADDR.ARPA o 10.IN-ADDR.ARPA
o 16.172.IN-ADDR.ARPA, 17.172.IN-ADDR.ARPA, ..., 31.172.IN-ADDR.ARPA o 16.172.IN-ADDR.ARPA, 17.172.IN-ADDR.ARPA, ..., 31.172.IN-ADDR.ARPA
skipping to change at page 19, line 35 skipping to change at page 19, line 35
Protocol 4 (BGP-4)", RFC 4271, January 2006. Protocol 4 (BGP-4)", RFC 4271, January 2006.
[RFC4786] Abley, J. and K. Lindqvist, "Operation of Anycast [RFC4786] Abley, J. and K. Lindqvist, "Operation of Anycast
Services", BCP 126, RFC 4786, December 2006. Services", BCP 126, RFC 4786, December 2006.
10.2. Informative References 10.2. Informative References
[I-D.ietf-dnsop-as112-under-attack-help-help] [I-D.ietf-dnsop-as112-under-attack-help-help]
Abley, J. and W. Maton, "I'm Being Attacked by Abley, J. and W. Maton, "I'm Being Attacked by
PRISONER.IANA.ORG!", PRISONER.IANA.ORG!",
draft-ietf-dnsop-as112-under-attack-help-help-05 (work in draft-ietf-dnsop-as112-under-attack-help-help-06 (work in
progress), March 2011. progress), April 2011.
[I-D.ietf-dnsop-default-local-zones] [I-D.ietf-dnsop-default-local-zones]
Andrews, M., "Locally-served DNS Zones", Andrews, M., "Locally-served DNS Zones",
draft-ietf-dnsop-default-local-zones-15 (work in draft-ietf-dnsop-default-local-zones-15 (work in
progress), March 2011. progress), March 2011.
[I-D.ietf-grow-unique-origin-as]
McPherson, D., Donnelly, R., and F. Scalzo, "Unique Per-
Node Origin ASNs for Globally Anycasted Services",
draft-ietf-grow-unique-origin-as-00 (work in progress),
November 2010.
[RFC1876] Davis, C., Vixie, P., Goodwin, T., and I. Dickinson, "A [RFC1876] Davis, C., Vixie, P., Goodwin, T., and I. Dickinson, "A
Means for Expressing Location Information in the Domain Means for Expressing Location Information in the Domain
Name System", RFC 1876, January 1996. Name System", RFC 1876, January 1996.
[RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses", [RFC5735] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses",
BCP 153, RFC 5735, January 2010. BCP 153, RFC 5735, January 2010.
[RFC5855] Abley, J. and T. Manderson, "Nameservers for IPv4 and IPv6 [RFC5855] Abley, J. and T. Manderson, "Nameservers for IPv4 and IPv6
Reverse Zones", BCP 155, RFC 5855, May 2010. Reverse Zones", BCP 155, RFC 5855, May 2010.
skipping to change at page 22, line 8 skipping to change at page 21, line 8
[3] <http://www.linux.it/~md/software/> [3] <http://www.linux.it/~md/software/>
[4] <http://dns.measurement-factory.com/tools/dnstop/> [4] <http://dns.measurement-factory.com/tools/dnstop/>
[5] <http://dns.measurement-factory.com/tools/dsc/> [5] <http://dns.measurement-factory.com/tools/dsc/>
Appendix A. History Appendix A. History
Widespread use of the private address blocks listed in [RFC1918] Widespread use of the private address blocks listed in [RFC1918]
followed that document's publication in 1996. followed that document's publication in 1996. At that time the IN-
ADDR.ARPA zone was served by root servers.
The idea of off-loading IN-ADDR.ARPA queries relating to [RFC1918] The idea of off-loading IN-ADDR.ARPA queries relating to [RFC1918]
addresses from the root nameservers was first proposed by Bill addresses from the root nameservers was first proposed by Bill
Manning and John Brown. Manning and John Brown.
The use of anycast for distributing authoritative DNS service for The use of anycast for distributing authoritative DNS service for
[RFC1918] IN-ADDR.ARPA zones was subsequently proposed at a private [RFC1918] IN-ADDR.ARPA zones was subsequently proposed at a private
meeting of root server operators. meeting of root server operators.
ARIN provided an IPv4 prefix for the anycast service, and also the ARIN provided an IPv4 prefix for the anycast service, and also the
autonomous system number 112 for use in originating that prefix. autonomous system number 112 for use in originating that prefix.
This assignment gave the project its name. This assignment gave the project its name.
In 2002, the first AS112 anycast nodes were deployed. In 2002 the first AS112 anycast nodes were deployed.
In 2011 the IN-ADDR.ARPA zone was redelegated from the root servers
to a new set of servers operated independently by AfriNIC, APNIC,
ARIN, ICANN, LACNIC and the RIPE NCC and named according to
[RFC5855].
The use of anycast nameservers in the AS112 project contributed to The use of anycast nameservers in the AS112 project contributed to
the operational experience of anycast DNS services, and can be seen the operational experience of anycast DNS services, and can be seen
as a precursor to the anycast distribution of other authoritative DNS as a precursor to the anycast distribution of other authoritative DNS
servers in subsequent years (e.g. various root servers). servers in subsequent years (e.g. various root servers).
Appendix B. Change History Appendix B. Change History
This section to be removed prior to publication. This section to be removed prior to publication.
skipping to change at page 24, line 5 skipping to change at page 22, line 34
Minor wordsmithing. Minor wordsmithing.
05 Updated following review from Peter Koch. 05 Updated following review from Peter Koch.
06 Updated following review from Alfred Hoenes. 06 Updated following review from Alfred Hoenes.
07 Updated following IESG review. 07 Updated following IESG review.
08 Updated following review by S. Moonesamy. 08 Updated following review by S. Moonesamy.
09 Updated following review by Peter Koch.
Authors' Addresses Authors' Addresses
Joe Abley Joe Abley
ICANN ICANN
4676 Admiralty Way, Suite 330 4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292 Marina del Rey, CA 90292
US US
Phone: +1 519 670 9327 Phone: +1 519 670 9327
Email: joe.abley@icann.org Email: joe.abley@icann.org
 End of changes. 10 change blocks. 
21 lines changed or deleted 19 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/