Re: [dnsext] Name equivalence: Another no protocol change solution

Niall O'Reilly <Niall.oReilly@ucd.ie> Mon, 13 September 2010 13:32 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 DC8C63A69C5; Mon, 13 Sep 2010 06:32:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.557
X-Spam-Level:
X-Spam-Status: No, score=-5.557 tagged_above=-999 required=5 tests=[AWL=0.442, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_MED=-4]
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 y+QLUkbl5tvi; Mon, 13 Sep 2010 06:32:18 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 5D49F3A69A3; Mon, 13 Sep 2010 06:32:18 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1Ov92u-000PZP-7n for namedroppers-data0@psg.com; Mon, 13 Sep 2010 13:26:08 +0000
Received: from mailhub2.ucd.ie ([193.1.169.37] helo=cali.ucd.ie) by psg.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.72 (FreeBSD)) (envelope-from <Niall.oReilly@ucd.ie>) id 1Ov92r-000PYH-MU for namedroppers@ops.ietf.org; Mon, 13 Sep 2010 13:26:05 +0000
Received: from conversion-daemon.cali.ucd.ie by cali.ucd.ie (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) id <0L8O00I01TA0YS00@cali.ucd.ie> (original mail from Niall.oReilly@ucd.ie) for namedroppers@ops.ietf.org; Mon, 13 Sep 2010 14:26:01 +0100 (IST)
Received: from [10.0.1.177] (bark.no8.be [83.141.81.52]) by cali.ucd.ie (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTPSA id <0L8O001BSTBDSY00@cali.ucd.ie>; Mon, 13 Sep 2010 14:26:01 +0100 (IST)
Date: Mon, 13 Sep 2010 14:26:05 +0100
From: Niall O'Reilly <Niall.oReilly@ucd.ie>
Subject: Re: [dnsext] Name equivalence: Another no protocol change solution
In-reply-to: <C0F55485EA77FDF78E9B0398@Ximines.local>
To: Alex Bligh <alex@alex.org.uk>
Cc: namedroppers@ops.ietf.org
Message-id: <4C8E266D.3070702@ucd.ie>
MIME-version: 1.0
Content-type: text/plain; format="flowed"; charset="UTF-8"
Content-transfer-encoding: 7bit
References: <C0F55485EA77FDF78E9B0398@Ximines.local>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-IE.utf8; rv:1.9.1.12) Gecko/20100826 Thunderbird/3.0.7
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/>

On 09/09/10 17:30, Alex Bligh wrote:
> 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.

	Alex,

	Are you assuming either
	(a) that cascaded sameness requirements won't arise. or
	(b) that the multiplicity (cardinality?) of a "sameness
	    bundle" will always be small?

	ATB
	Niall O'Reilly