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

Jay Ashworth <jra@baylink.com> Wed, 16 February 2011 04:17 UTC

Return-Path: <jra@baylink.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 AE4F43A6D23 for <dnsext@core3.amsl.com>; Tue, 15 Feb 2011 20:17:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 cUnfWZw1knoj for <dnsext@core3.amsl.com>; Tue, 15 Feb 2011 20:17:05 -0800 (PST)
Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.125]) by core3.amsl.com (Postfix) with ESMTP id CC1623A6CD1 for <dnsext@ietf.org>; Tue, 15 Feb 2011 20:17:04 -0800 (PST)
X-Authority-Analysis: v=1.1 cv=dquaJDitHqzHCdqWSoZ6IgapSuTzW/4TaRYx9N9k4W8= c=1 sm=0 a=SnqA-C_CkNwA:10 a=FKkrIqjQGGEA:10 a=Xve_KQuntz4A:10 a=wPDyFdB5xvgA:10 a=IkcTkHD0fZMA:10 a=QDKGtjV+XQz2PzAlwL4sQw==:17 a=3DW5ysfuAAAA:8 a=fAb-cvdhe0lY3sdcGIIA:9 a=o1FYIOhP8hwyg9pv7Wc_EBzMREsA:4 a=QEXdDO2ut3YA:10 a=2SAumGWBsQEA:10 a=QDKGtjV+XQz2PzAlwL4sQw==:117
X-Cloudmark-Score: 0
X-Originating-IP: 24.129.180.187
Received: from [24.129.180.187] ([24.129.180.187:54887] helo=benjamin.baylink.com) by hrndva-oedge01.mail.rr.com (envelope-from <jra@baylink.com>) (ecelerity 2.2.3.46 r()) with ESMTP id 1C/29-14011-BDF4B5D4; Wed, 16 Feb 2011 04:17:31 +0000
Received: from localhost (localhost.localdomain [127.0.0.1]) by benjamin.baylink.com (Postfix) with ESMTP id 491701F0012C for <dnsext@ietf.org>; Tue, 15 Feb 2011 23:17:49 -0500 (EST)
X-Virus-Scanned: amavisd-new at benjamin.baylink.com
Received: from benjamin.baylink.com ([127.0.0.1]) by localhost (benjamin.baylink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EuhQ+lF+wYgj for <dnsext@ietf.org>; Tue, 15 Feb 2011 23:17:48 -0500 (EST)
Received: from benjamin.baylink.com (benjamin.baylink.com [192.168.253.10]) by benjamin.baylink.com (Postfix) with ESMTP id 81AD81F000F0 for <dnsext@ietf.org>; Tue, 15 Feb 2011 23:17:48 -0500 (EST)
Date: Tue, 15 Feb 2011 23:17:48 -0500 (EST)
From: Jay Ashworth <jra@baylink.com>
To: dnsext@ietf.org
Message-ID: <32007060.266.1297829868445.JavaMail.root@benjamin.baylink.com>
In-Reply-To: <20110216032120.43474.qmail@joyce.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Mailer: Zimbra 6.0.9_GA_2686 (ZimbraWebClient - FF3.0 (Linux)/6.0.9_GA_2686)
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 04:17:05 -0000

----- Original Message -----
> From: "John Levine" <johnl@iecc.com>

> But as has often been noted, many protocols such as HTTP and SMTP
> depend on the actual domain name, so nothing the DNS does to make
> stuff "the same" will make variants of a domain name work.
> Considering the number of variants that a name can have, e.g., M^N for
> any name with N characters that have M variants, any approach that
> provisions the HTTP and SMTP servers manually is likely to fail in
> practice, since the various lists of equivalent domains will always
> get out of sync.

And, as has been pointed out in some other venues, and which seems 
applicable here also, some approachs to certain things *depend on trying
a DNS lookup and having it break*.  I'm damned if I can remember what
the canonical example was, but it fell in the general category of 
"please don't make this change to try to 'help' 'the web', cause you'll
break *my* protocol which isn't http".

Cheers,
-- jra