draft-ietf-dnsext-rfc2672bis-dname-21.txt   draft-ietf-dnsext-rfc2672bis-dname-22.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 NLnet Labs Updates: 3363,4294 NLnet Labs
(if approved) December 2, 2010 (if approved) May 2, 2011
Intended status: Standards Track Intended status: Standards Track
Expires: June 5, 2011 Expires: November 3, 2011
Update to DNAME Redirection in the DNS Update to DNAME Redirection in the DNS
draft-ietf-dnsext-rfc2672bis-dname-21 draft-ietf-dnsext-rfc2672bis-dname-22
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 of the original specification in RFC 2672, also aligning a revision of the original specification in RFC 2672, also aligning
RFC 3363 and RFC 4294 with this revision. RFC 3363 and RFC 4294 with this revision.
Requirements Language Requirements Language
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 June 5, 2011. This Internet-Draft will expire on November 3, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 8, line 19 skipping to change at page 8, line 19
specified and this document also does not specify this signaling specified and this document also does not specify this signaling
behavior. behavior.
RFC 2672 (obsoleted by this document) stated that the EDNS version RFC 2672 (obsoleted by this document) stated that the EDNS version
had a meaning for understanding of DNAME and DNAME target name had a meaning for understanding of DNAME and DNAME target name
compression. This document revises RFC 2672, in that there is no compression. This document revises RFC 2672, in that there is no
EDNS version signaling for DNAME. EDNS version signaling for DNAME.
3. Processing 3. Processing
The DNAME RR causes type NS additional section processing. This
refers to action at step 6 of the server algorithm outlined in
section 3.2.
3.1. CNAME synthesis 3.1. CNAME synthesis
When preparing a response, a server performing a DNAME substitution When preparing a response, a server performing a DNAME substitution
will in all cases include the relevant DNAME RR in the answer will in all cases include the relevant DNAME RR in the answer
section. Relevant includes the following cases: section. Relevant includes the following cases:
1. The DNAME is being employed as a substitution instruction. 1. The DNAME is being employed as a substitution instruction.
2. The DNAME itself matches the QTYPE and the owner name matches 2. The DNAME itself matches the QTYPE and the owner name matches
QNAME. QNAME.
 End of changes. 6 change blocks. 
9 lines changed or deleted 5 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/