[dnsext] Name equivalence: Another no protocol change solution

Alex Bligh <alex@alex.org.uk> Thu, 09 September 2010 16:33 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-dnsext-archive@core3.amsl.com
Delivered-To: ietfarch-dnsext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 505C73A68E7; Thu, 9 Sep 2010 09:33:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.067
X-Spam-Level:
X-Spam-Status: No, score=-0.067 tagged_above=-999 required=5 tests=[AWL=-0.482, BAYES_40=-0.185, J_CHICKENPOX_55=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VojOQc2Keocr; Thu, 9 Sep 2010 09:33:43 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 8D40F3A67FF; Thu, 9 Sep 2010 09:33:43 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1Otk1W-0002S9-Hk for namedroppers-data0@psg.com; Thu, 09 Sep 2010 16:30:54 +0000
Received: from mail.avalus.com ([89.16.176.221]) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <alex@alex.org.uk>) id 1Otk1T-0002Rk-Jd for namedroppers@ops.ietf.org; Thu, 09 Sep 2010 16:30:52 +0000
Received: from [192.168.100.15] (87-194-71-186.bethere.co.uk [87.194.71.186]) by mail.avalus.com (Postfix) with ESMTPSA id 5C41EC56960; Thu, 9 Sep 2010 17:30:49 +0100 (BST)
Date: Thu, 09 Sep 2010 17:30:49 +0100
From: Alex Bligh <alex@alex.org.uk>
Reply-To: Alex Bligh <alex@alex.org.uk>
To: namedroppers@ops.ietf.org
cc: Alex Bligh <alex@alex.org.uk>
Subject: [dnsext] Name equivalence: Another no protocol change solution
Message-ID: <C0F55485EA77FDF78E9B0398@Ximines.local>
X-Mailer: Mulberry/4.0.8 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>
List-Unsubscribe: To unsubscribe send a message to namedroppers-request@ops.ietf.org with
List-Unsubscribe: the word 'unsubscribe' in a single line as the message text body.
List-Archive: <http://ops.ietf.org/lists/namedroppers/>

The problem to me seems to be divided into (at least) two:

1. Apparent pseudo-regulatory requirement to ensure TLDs operate with
   recursive sameness. This is making TLD1 == TLD2.

2. Requirement within a TLD for some sort of equivalence (possibly not
   recursive) but notably not driven by a third party's perceived
   requirements. This is making foo.TLD == bar.TLD.

Problem 1 can, it seems to me, be solved by DNAME. DNAME only doesn't
do the job when there is a record at the apex, because DNAME+CNAME
can't coexist. Few if any TLDs have records at their apexes.

Problem 2 cannot in general be solved by DNAME (DNAME+CNAME problem),
as foo.tld may well exist. This can, however, in general be solved
by provisioning algorithms.

It is not particularly neat solving what looks like one problem with
two solutions, but closer inspection suggests the problems are
in fact different.

-- 
Alex Bligh