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

Andrew Sullivan <ajs@anvilwalrusden.com> Sun, 05 July 2015 14:44 UTC

Return-Path: <ajs@anvilwalrusden.com>
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 0A5D01A8A4C for <dnsop@ietfa.amsl.com>; Sun, 5 Jul 2015 07:44:45 -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] 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 YZfAoOGOC4Ft for <dnsop@ietfa.amsl.com>; Sun, 5 Jul 2015 07:44:43 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info [IPv6:2600:3c03::f03c:91ff:fedf:cfab]) by ietfa.amsl.com (Postfix) with ESMTP id AD8511A8A3F for <dnsop@ietf.org>; Sun, 5 Jul 2015 07:44:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id 034611036F for <dnsop@ietf.org>; Sun, 5 Jul 2015 14:44:43 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j1osGZIGGeeP for <dnsop@ietf.org>; Sun, 5 Jul 2015 14:44:42 +0000 (UTC)
Received: from mx2.yitter.info (c-50-169-68-91.hsd1.nh.comcast.net [50.169.68.91]) by mx2.yitter.info (Postfix) with ESMTPSA id 02B6410370 for <dnsop@ietf.org>; Sun, 5 Jul 2015 14:44:41 +0000 (UTC)
Date: Sun, 05 Jul 2015 10:44:40 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20150705144440.GB49476@mx2.yitter.info>
References: <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> <5598D9EF.7000006@bellis.me.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5598D9EF.7000006@bellis.me.uk>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/mOjk_-OrXRZ4ium3f-lRlEoRnsI>
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 14:44:45 -0000

On Sun, Jul 05, 2015 at 08:17:03AM +0100, Ray Bellis wrote:
> 
> Sure, CNAME is *defined* for all classes, but AFAIK there's no way to "jump"
> out of one class into another using a CNAME.

No, that's correct.  But if the point of using a class is to create a
separate namespace, then the fact of class-independent RRTYPEs means
you can't do that.  As Paul Vixie notes, there appears to be some
ambiguity with CNAMEs on this front, but as nearly as I can tell RFC
6672 makes this plain for DNAME.

Imagine the alternative-resolution class FAKE.  In the IN class,
example.com has a DNAME entry pointing to example.net.  What should
happen when someone performs a query for QNAME localentry.example.com,
TYPE AAAA, and CLASS FAKE?

RFC 6672's description of the algorithm does not use CLASS as a
distinguishing criterion.  So, I think the answer is the DNAME
processing should return the results for localentry.example.net,
regardless of the class.  As a consequence, CLASS does not work to
provide different completely independent namespaces, and therefore
co-ordination across the class registrations will be necessary.  In
effect, CLASS doesn't work.

At least, that's my reading of the RFC.  I'd be pleased to be wrong.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com