Re: [DNSOP] Some distinctions and a request - Have some class?

Ray Bellis <ray@bellis.me.uk> Sun, 05 July 2015 07:17 UTC

Return-Path: <ray@bellis.me.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF3FB1B2BF9 for <dnsop@ietfa.amsl.com>; Sun, 5 Jul 2015 00:17:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3gtBOKTycr8j for <dnsop@ietfa.amsl.com>; Sun, 5 Jul 2015 00:17:07 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B2E51B2BF8 for <dnsop@ietf.org>; Sun, 5 Jul 2015 00:17:05 -0700 (PDT)
Received: from [46.227.151.81] (port=58761 helo=Barbaras-MacBook-Pro-3.local) by hydrogen.portfast.net ([188.246.200.2]:587) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1ZBeAh-0001Nr-5S (Exim 4.72) (return-path <ray@bellis.me.uk>); Sun, 05 Jul 2015 08:17:03 +0100
Message-ID: <5598D9EF.7000006@bellis.me.uk>
Date: Sun, 05 Jul 2015 08:17:03 +0100
From: Ray Bellis <ray@bellis.me.uk>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
References: <6CB05D82CE245B4083BBF3B97E2ED470C2759F@ait-pex01mbx01.win.dtu.dk> <6CB05D82CE245B4083BBF3B97E2ED470C275B2@ait-pex01mbx01.win.dtu.dk> <E225C721-7279-4053-97A2-2D63A155DA14@karoshi.com> <6CB05D82CE245B4083BBF3B97E2ED470C27602@ait-pex01mbx01.win.dtu.dk> <88E49F4B-64BD-4832-BD02-D1A882874E92@karoshi.com> <20150702234423.GB23022@mycre.ws> <EBDBDD70-046F-4E31-BDAC-A619EECD4F13@karoshi.com> <20150703012146.GA29948@mycre.ws> <DC13E07F-2203-4FE9-A67F-B5851A54298F@karoshi.com> <986E07DA-B174-4F81-BFB5-F5EAD46C506F@karoshi.com> <20150705003514.GD48722@mx2.yitter.info>
In-Reply-To: <20150705003514.GD48722@mx2.yitter.info>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/DtPlX73C5hdtK7RjwU-9RM1C5Vo>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Some distinctions and a request - Have some class?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Jul 2015 07:17:08 -0000


On 05/07/2015 01:35, Andrew Sullivan wrote:

 > Classes don't work in the general case, because CNAME (and following
 > it, DNAME) is class-independent.  This is arguably a bug in the
 > protocol, but it's a fact nevertheless.  As a result, different
 > classes aren't really different namespaces.

Andrew,

Can you please elaborate on what you mean there?

Sure, CNAME is *defined* for all classes, but AFAIK there's no way to 
"jump" out of one class into another using a CNAME.  If you've queried 
in class FOO and see a CNAME then the resolution of the target of the 
CNAME should continue in class FOO.

RFC 1034 §3.6.2:

"CNAME RRs cause special action in DNS software. When a name server 
fails to find a desired RR in the resource set associated with the 
domain name, it checks to see if the resource set consists of a CNAME 
record with a matching class. If so, the name server includes the CNAME 
record in the response and restarts the query at the domain name 
specified in the data field of the CNAME record."

kind regards,

Ray