[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [dnsext] Re: DNAME-bis issues (was: [DNSOP] new draft about idn tld variant implementation)



On Oct 21 2009, Andrew Sullivan wrote:

Dear colleagues,

On Wed, Oct 21, 2009 at 05:54:18PM +1100, Mark Andrews wrote:

DNAME's placement is the same as any ordinary resource record (e.g.
MX, TXT).  There is nothing special about where DNAME can or can't
be used.

While that is true, quite plainly the current dname-bis draft doesn't
leave everyone with that impression.  We need proposed text to make
the intent clearer.  Can someone please propose it?  Given the
emergence of this issue, the document is clearly not ready for
advancement, and it needs to be fixed before we send it on.

We really need Alfred Hönes to comment on this, as he was the one who
acquired the wrong impression. My feeling is that the confusion is
confined to section 2.3, and I would now suggest the following:

--- draft-ietf-dnsext-rfc2672bis-dname-17.xml	Wed Oct 21 16:17:14 2009
+++ draft-ietf-dnsext-rfc2672bis-dname-17a.xml	Wed Oct 21 16:19:51 2009
@@ -214,7 +214,7 @@
	for the YXDOMAIN (value 6) RCODE.
	</t>
</section>
-<section title="DNAME Apex not Redirected itself">
+<section title="DNAME Owner Name not Redirected itself">
<t>
	Unlike a CNAME RR, a DNAME RR redirects DNS names subordinate to its
	owner name; the owner name of a DNAME is not redirected itself.
@@ -224,9 +224,10 @@
DNAME RRs are not allowed at the parent side of a delegation point but are allowed at a zone apex.
</t><t>
-	There still is a need to have the customary SOA and NS
-	resource records at the zone apex.  This means that DNAME does not
-	mirror a zone completely, as it does not mirror the zone apex.
+	If a DNAME record is present at the zone apex, there is still a need
+	to have the customary SOA and NS resource records there as well. Such
+	a DNAME cannot be used to mirror a zone completely, as it does not
+	mirror the zone apex.
</t><t>
	These rules also allow DNAME records to be queried through RFC 1034
	<xref target="RFC1034" /> compliant, DNAME-unaware caches.

--
Chris Thompson               University of Cambridge Computing Service,
Email: cet1@ucs.cam.ac.uk    New Museums Site, Cambridge CB2 3QH,
Phone: +44 1223 334715       United Kingdom.