draft-ietf-dnsext-rfc2672bis-dname-23.txt   draft-ietf-dnsext-rfc2672bis-dname-24.txt 
DNS Extensions Working Group S. Rose DNS Extensions Working Group S. Rose
Internet-Draft NIST Internet-Draft NIST
Obsoletes: 2672 (if approved) W. Wijngaards Obsoletes: 2672 (if approved) W. Wijngaards
Updates: 3363,4294 (if approved) NLnet Labs Updates: 3363,4294 (if approved) NLnet Labs
Intended status: Standards Track June 24, 2011 Intended status: Standards Track July 26, 2011
Expires: December 26, 2011 Expires: January 27, 2012
Update to DNAME Redirection in the DNS DNAME Redirection in the DNS
draft-ietf-dnsext-rfc2672bis-dname-23 draft-ietf-dnsext-rfc2672bis-dname-24
Abstract Abstract
The DNAME record provides redirection for a sub-tree of the domain The DNAME record provides redirection for a sub-tree of the domain
name tree in the DNS system. That is, all names that end with a name tree in the DNS system. That is, all names that end with a
particular suffix are redirected to another part of the DNS. This is particular suffix are redirected to another part of the DNS. This is
a revision to the original specification in RFC 2672 as well as a revision to the original specification in RFC 2672 as well as
updating RFC 3363 and RFC 4294 to align with this revision. updating RFC 3363 and RFC 4294 to align with this revision.
Requirements Language Requirements Language
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 December 26, 2011. This Internet-Draft will expire on January 27, 2012.
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 4, line 40 skipping to change at page 4, line 40
renumbering. With a careful set-up, a renumbering event in the renumbering. With a careful set-up, a renumbering event in the
network causes no change to the authoritative server that has the network causes no change to the authoritative server that has the
address-to-name mappings. Examples in practice are classless reverse address-to-name mappings. Examples in practice are classless reverse
address space delegations. address space delegations.
Another usage of DNAME lies in aliasing of name spaces. For example, Another usage of DNAME lies in aliasing of name spaces. For example,
a zone administrator may want sub-trees of the DNS to contain the a zone administrator may want sub-trees of the DNS to contain the
same information. Examples include punycode alternates for domain same information. Examples include punycode alternates for domain
spaces. spaces.
This update to DNAME does not change the wire format or the handling This revision of the DNAME specification does not change the wire
of DNAME Resource Records. Discussion is added on problems that may format or the handling of DNAME Resource Records. Discussion is
be encountered when using DNAME. added on problems that may be encountered when using DNAME.
2. The DNAME Resource Record 2. The DNAME Resource Record
2.1. Format 2.1. Format
The DNAME RR has mnemonic DNAME and type code 39 (decimal). It is The DNAME RR has mnemonic DNAME and type code 39 (decimal). It is
not class-sensitive. not class-sensitive.
Its RDATA is comprised of a single field, <target>, which contains a Its RDATA is comprised of a single field, <target>, which contains a
fully qualified domain name that must be sent in uncompressed form fully qualified domain name that must be sent in uncompressed form
 End of changes. 4 change blocks. 
8 lines changed or deleted 8 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/