draft-ietf-dnsext-rfc2672bis-dname-20.txt   draft-ietf-dnsext-rfc2672bis-dname-21.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) October 14, 2010 (if approved) December 2, 2010
Intended status: Standards Track Intended status: Standards Track
Expires: April 17, 2011 Expires: June 5, 2011
Update to DNAME Redirection in the DNS Update to DNAME Redirection in the DNS
draft-ietf-dnsext-rfc2672bis-dname-20 draft-ietf-dnsext-rfc2672bis-dname-21
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 April 17, 2011. This Internet-Draft will expire on June 5, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 13, line 33 skipping to change at page 13, line 33
punycode in their RDATA. What must be done then is to have the punycode in their RDATA. What must be done then is to have the
domain names with DNAME substitution already applied to it as the MX, domain names with DNAME substitution already applied to it as the MX,
NS, PTR, SRV data. These are valid canonical hostnames. NS, PTR, SRV data. These are valid canonical hostnames.
5.2. Dynamic Update and DNAME 5.2. Dynamic Update and DNAME
DNAME records can be added, changed and removed in a zone using DNAME records can be added, changed and removed in a zone using
dynamic update transactions. Adding a DNAME RR to a zone occludes dynamic update transactions. Adding a DNAME RR to a zone occludes
any domain names that may exist under the added DNAME. any domain names that may exist under the added DNAME.
A server MUST ignore a dynamic update message that attempts to add a If a dynamic update message attempts to add a DNAME with a given
non-DNAME/CNAME RR at a name that already has a DNAME RR associated owner name but a CNAME is associated with that name, then the server
with that name. Otherwise, replace the DNAME RR with the DNAME (or MUST ignore the DNAME. If a DNAME is already associated with that
CNAME) update RR. This is similar behavior to dynamic updates to an name, then it is replaced with the new DNAME. Otherwise, add the
owner name of a CNAME RR [RFC2136]. DNAME. If a CNAME is added with a given owner name but a DNAME is
associated with that name, then the CNAME MUST be ignored. This is
similar behavior for dynamic updates to an owner name of a CNAME RR
[RFC2136].
5.3. DNSSEC and DNAME 5.3. DNSSEC and DNAME
The following subsections specify the behavior of implementations The following subsections specify the behavior of implementations
that understand both DNSSEC and DNAME (synthesis). that understand both DNSSEC and DNAME (synthesis).
5.3.1. Signed DNAME, Unsigned Synthesized CNAME 5.3.1. Signed DNAME, Unsigned Synthesized CNAME
In any response, a signed DNAME RR indicates a non-terminal In any response, a signed DNAME RR indicates a non-terminal
redirection of the query. There might or might not be a server redirection of the query. There might or might not be a server
 End of changes. 5 change blocks. 
9 lines changed or deleted 12 lines changed or added

This html diff was produced by rfcdiff 1.40. The latest version is available from http://tools.ietf.org/tools/rfcdiff/