< draft-ietf-dnsop-as112-dname-03.txt		draft-ietf-dnsop-as112-dname-04.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: September 20, 2014 Verisign Labs		Expires: December 29, 2014 Verisign Labs
	W. Kumari		W. Kumari
	Google		Google
	G. Michaelson		G. Michaelson
	APNIC		APNIC
	March 19, 2014		June 27, 2014
	AS112 Redirection using DNAME		AS112 Redirection using DNAME
	draft-ietf-dnsop-as112-dname-03		draft-ietf-dnsop-as112-dname-04
	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 September 20, 2014.		This Internet-Draft will expire on December 29, 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 6, line 43 ¶		skipping to change at page 6, line 43 ¶
	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
	installing a DNAME resource record in the 192.IN-ADDR.ARPA zone, as		installing a DNAME resource record in the 192.IN-ADDR.ARPA zone, as
	illustrated in Figure 1.		illustrated in Figure 1.
	$ORIGIN 192.IN-ADDR.ARPA.		$ORIGIN 192.IN-ADDR.ARPA.
	...		...
	2.0.IN-ADDR.ARPA. IN DNAME EMPTY.AS112.ARPA.		2.0 IN DNAME EMPTY.AS112.ARPA.
	...		...
	Figure 1		Figure 1
	There is no practical limit to the number of redirections that can be		There is no practical limit to the number of redirections that can be
	configured in this fashion. Redirection of a particular part of the		configured in this fashion. Redirection of a particular part of the
	namespace to EMPTY.AS112.ARPA can be removed at any time, under the		namespace to EMPTY.AS112.ARPA can be removed at any time, under the
	control of the administrators of the corresponding part of the DNS		control of the administrators of the corresponding part of the DNS
	namespace. No changes to deployed AS112 nodes incorporating the		namespace. No changes to deployed AS112 nodes incorporating the
	extensions described in this document are required to support		extensions described in this document are required to support
	skipping to change at page 16, line 7 ¶		skipping to change at page 16, line 7 ¶
	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
	[RFC6304bis].		[RFC6304bis].
	10. Acknowledgements		10. Acknowledgements
	Your name here, etc.		The authors acknowledge the valuable contributions of Bob Harold and
			other participants in the DNSOP working group in the preparation of
			this document.
	11. References		11. References
	11.1. Normative References		11.1. Normative References
	[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.
	skipping to change at page 22, line 5 ¶		skipping to change at page 21, line 33 ¶
	01 Minor updates following submission of		01 Minor updates following submission of
	draft-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		03 Updated references to 6304 following guidance from working group
	chairs.		chairs.
			04 Corrected an error picked up by Bob Harold.
	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. 7 change blocks.
	6 lines changed or deleted		10 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/