Re: [dnsext] we need help to make names the same, was draft-yao-dnsext-identical-resolution-02 comment

"John R. Levine" <johnl@iecc.com> Wed, 16 February 2011 17:56 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F01FC3A6EDF for <dnsext@core3.amsl.com>; Wed, 16 Feb 2011 09:56:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.899
X-Spam-Level:
X-Spam-Status: No, score=-110.899 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, J_CHICKENPOX_43=0.6, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 OWp8pngV-e8T for <dnsext@core3.amsl.com>; Wed, 16 Feb 2011 09:56:38 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 94BBC3A6EDE for <dnsext@ietf.org>; Wed, 16 Feb 2011 09:56:38 -0800 (PST)
Received: (qmail 4856 invoked from network); 16 Feb 2011 17:57:05 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=12f7.4d5c0ff1.k1102; i=johnl@submit.iecc.com; bh=V2hRHf6F2d5XS1K9X5GcN3NfD4tAwoqRx78Ut7Jz8eo=; b=WD/KV9vQw39MqeJt5+xFtiknL2wC/eY7R2dHsIfkcctt1JuSZIcoFa3QhwvhpRtgq1cdc2FKMewF2uWRohmYGyzNp34ioaeFTHLAtKdrTrm5ZYxfGgjFGR94o9qN18RJ9r3ZdI3OS8ljWuRTN3jklORz1Zrlsj+TH+FhueQ3CIM=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd johnl@64.57.183.62) with (DHE-RSA-AES256-SHA encrypted) SMTP; 16 Feb 2011 17:56:43 -0000
Date: Wed, 16 Feb 2011 09:57:03 -0800
Message-ID: <alpine.BSF.2.00.1102160944390.62118@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: Vaggelis Segredakis <segred@ics.forth.gr>
In-Reply-To: <F21692535B1A478F95D9E3AA048E8037@ics.forth.gr>
References: <4D5B5E81.1050602@necom830.hpcl.titech.ac.jp> <20110216073338.7251.qmail@joyce.lan> <F21692535B1A478F95D9E3AA048E8037@ics.forth.gr>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Cc: dnsext@ietf.org
Subject: Re: [dnsext] we need help to make names the same, was draft-yao-dnsext-identical-resolution-02 comment
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 17:56:40 -0000

> The number of these domain names varies from two (or four if a final sigma
> is present) to some tens of domains, not millions and certainly not
> billions.

Well, yes, but that's in one component.  If someone has a name A.B.C.gr, 
where each of A B C has ten variants, now there's a thousand equivalent 
names.  I would think that a design that handled the variants in C but not 
in A and B is not worth implementing.

If you only care about C, you can do that with bundling, have the registry 
assign all variants of a requested name to the registrant, and let the 
registrant deal with making them the same, by copies of the zone.  It's 
not particularly elegant, but it requires no changes to existing protocol 
and the software is not very complicated.

> We asked for a DNS rr that will allow two, three, four, or tens of 
> chosen domain names to act as if they were interchangeable in all the 
> branches of the domain name tree, starting from the top. They could be 
> perfectly normal Latin domain names that point to the same services and 
> the administrator decides to administer them as one.

Except that, as often noted, if the servers they point to don't have some 
way to discover that the names are intended to be equivalent, the services 
won't work.  The assumptions so far seem to be either that the services 
are something like telnet that doesn't care what its name is, or that 
they'll be manually provisioned, which seems unlikely to work except in 
the tiniest cases.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly