AS112 Redirection Using DNAME
RFC 7535
|
| Document |
Type |
|
RFC - Informational
(May 2015; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Replaces |
|
draft-jabley-dnsop-as112-dname
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Tim Wicinski
|
|
Shepherd write-up |
|
Show
(last changed 2014-06-27)
|
| IESG |
IESG state |
|
RFC 7535 (Informational)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Joel Jaeggli
|
|
Send notices to |
|
(None)
|
| IANA |
IANA review state |
|
Version Changed - Review Needed
|
|
IANA action state |
|
RFC-Ed-Ack
|
Internet Engineering Task Force (IETF) J. Abley
Request for Comments: 7535 Dyn, Inc.
Category: Informational B. Dickson
ISSN: 2070-1721 Twitter, Inc.
W. Kumari
Google
G. Michaelson
APNIC
May 2015
AS112 Redirection Using DNAME
Abstract
AS112 provides a mechanism for handling reverse lookups on IP
addresses that are not unique (e.g., RFC 1918 addresses). This
document describes modifications to the deployment and use of AS112
infrastructure that will allow zones to be added and dropped much
more easily, using DNAME resource records.
This approach makes it possible for any DNS zone administrator to
sink traffic relating to parts of the global DNS namespace under
their control to the AS112 infrastructure without coordination with
the operators of AS112 infrastructure.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7535.
Abley, et al. Informational [Page 1]
RFC 7535 AS112 Redirection Using DNAME May 2015
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction ....................................................3
2. Design Overview .................................................4
3. AS112 Operations ................................................5
3.1. Extensions to Support DNAME Redirection ....................5
3.2. Redirection of Query Traffic to AS112 Servers ..............5
4. Continuity of AS112 Operations ..................................6
5. Candidate Zones for AS112 Redirection ...........................6
6. DNAME Deployment Considerations .................................7
7. IAB Statement Regarding This .ARPA Request ......................8
8. IANA Considerations .............................................8
8.1. Address Assignment .........................................8
8.2. Hosting of AS112.ARPA .....................................10
8.3. Delegation of AS112.ARPA ..................................10
9. Security Considerations ........................................10
10. References ....................................................11
10.1. Normative References .....................................11
10.2. Informative References ...................................11
Appendix A. Assessing Support for DNAME in the Real World .........13
A.1. Methodology ................................................13
A.2. Results ....................................................15
Acknowledgements ..................................................16
Authors' Addresses ................................................16
Abley, et al. Informational [Page 2]
RFC 7535 AS112 Redirection Using DNAME May 2015
1. Introduction
Many sites connected to the Internet make use of IPv4 addresses that
are not globally unique. Examples are the addresses designated in
[RFC1918] for private use within individual sites.
Show full document text