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

"Vaggelis Segredakis" <segred@ics.forth.gr> Thu, 17 February 2011 07:37 UTC

Return-Path: <segred@ics.forth.gr>
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 16AA03A6D56 for <dnsext@core3.amsl.com>; Wed, 16 Feb 2011 23:37:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.401
X-Spam-Level:
X-Spam-Status: No, score=-6.401 tagged_above=-999 required=5 tests=[AWL=-0.402, BAYES_00=-2.599, J_CHICKENPOX_43=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 TzgkMiTVh8Ry for <dnsext@core3.amsl.com>; Wed, 16 Feb 2011 23:37:12 -0800 (PST)
Received: from mailgate.ics.forth.gr (mailgate.ics.forth.gr [139.91.1.2]) by core3.amsl.com (Postfix) with ESMTP id 321EF3A6CE6 for <dnsext@ietf.org>; Wed, 16 Feb 2011 23:37:11 -0800 (PST)
Received: from av1.ics.forth.gr (av1-in.ics.forth.gr [139.91.1.71]) by mailgate.ics.forth.gr (8.14.3/ICS-FORTH/V10-1.8-GATE) with ESMTP id p1H7bXrH010843; Thu, 17 Feb 2011 09:37:35 +0200 (EET)
X-AuditID: 8b5b9d47-b7c88ae0000076fe-cf-4d5cd03c9ab4
Received: from enigma.ics.forth.gr (webmail.ics.forth.gr [139.91.1.30]) by av1.ics.forth.gr (SMTP Outbound / FORTH / ICS) with SMTP id 7F.E3.30462.C30DC5D4; Thu, 17 Feb 2011 09:37:32 +0200 (EET)
Received: from Thanatos (thanatos.ics.forth.gr [139.91.88.160]) (authenticated bits=0) by enigma.ics.forth.gr (8.14.3//ICS-FORTH/V10.3.0C-EXTNULL-SSL-SASL) with ESMTP id p1H7bVac021719 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 17 Feb 2011 09:37:32 +0200
X-ICS-AUTH-INFO: Authenticated user: segred at ics.forth.gr
From: Vaggelis Segredakis <segred@ics.forth.gr>
To: "'John R. Levine'" <johnl@iecc.com>
References: <4D5B5E81.1050602@necom830.hpcl.titech.ac.jp> <20110216073338.7251.qmail@joyce.lan> <F21692535B1A478F95D9E3AA048E8037@ics.forth.gr> <alpine.BSF.2.00.1102160944390.62118@joyce.lan>
Date: Thu, 17 Feb 2011 09:36:13 +0200
Message-ID: <25C1FE09988043CCAA0DDC5CD6CE3DC9@ics.forth.gr>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcvOAvN1eo1iwWgYQOqeos8BTzrR2QAb9HKw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
In-Reply-To: <alpine.BSF.2.00.1102160944390.62118@joyce.lan>
X-Brightmail-Tracker: AAAAAA==
X-j-chkmail-Score: MSGID : 4D5CD03D.000 on mailgate : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-ICS-JCHK-SCL: Ham
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: Thu, 17 Feb 2011 07:37:14 -0000

Dear John,

>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.

I guess you know we are the Registry of [.gr] domain names. If we are asking
for a different solution than simple bundling and letting the registrant
deal with the issue this should mean something about bundling, right? When
an issue is so common that all your IDN registrants have to register bundles
and "deal with making them the same", it appears to be a good thing if the
registry can assist on such an issue.

The registrants have not asked for IDNA2003 or IDNA2008 to be implemented as
they were, protocols with shortcomings. However, since the IDNA protocols
are well in use by now, a BNAME type solution could make life easier for the
average user.

>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.

My guess is that when the solution is available, many services will benefit
from it and use it.

Kind Regards,

Vaggelis Segredakis