Re: [dnsext] draft-yao-dnsext-identical-resolution-02 comment

Suzanne Woolf <woolf@isc.org> Mon, 14 February 2011 07:10 UTC

Return-Path: <woolf@isc.org>
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 0A9F03A6C7C for <dnsext@core3.amsl.com>; Sun, 13 Feb 2011 23:10:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.6
X-Spam-Level:
X-Spam-Status: No, score=-3.6 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, NO_RELAYS=-0.001]
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 6aH76z0QH6HS for <dnsext@core3.amsl.com>; Sun, 13 Feb 2011 23:10:37 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by core3.amsl.com (Postfix) with ESMTP id 2DEAC3A6C77 for <dnsext@ietf.org>; Sun, 13 Feb 2011 23:10:37 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id C61EC5F98E9; Mon, 14 Feb 2011 07:10:48 +0000 (UTC) (envelope-from woolf@isc.org)
Received: by bikeshed.isc.org (Postfix, from userid 10265) id 6D107216C36; Mon, 14 Feb 2011 07:10:47 +0000 (UTC)
Date: Mon, 14 Feb 2011 07:10:47 +0000
From: Suzanne Woolf <woolf@isc.org>
To: Vaggelis Segredakis <segred@ics.forth.gr>
Message-ID: <20110214071047.GA64679@bikeshed.isc.org>
References: <4D48617E.1020408@ogud.com> <3A5CD55E5CCE43F0BA44AAC89BADB866@ics.forth.gr> <20110211020125.GA147@bikeshed.isc.org> <F5CC3C0B5F464E63A4154F62B9BFFDD1@ics.forth.gr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F5CC3C0B5F464E63A4154F62B9BFFDD1@ics.forth.gr>
User-Agent: Mutt/1.4.2.3i
Cc: dnsext@ietf.org, 'Olafur Gudmundsson' <ogud@ogud.com>
Subject: Re: [dnsext] 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: Mon, 14 Feb 2011 07:10:39 -0000

On Fri, Feb 11, 2011 at 06:17:16PM +0200, Vaggelis Segredakis wrote:
> As the Greek registry, offering registrations in Greek characters presented
> the problem with the accent mark "tonos" which is used in the majority of
> Greek words. In capital letters however, the same words are spelled without
> the tonos. Their representation in the Punycode is unfortunately different
> and we had to match these up (make similar) for the user, otherwise the user
> experience of case-insensitivity would be lost. We used the DNAME mechanism
> with not very satisfactory results.

The previous version of the document used your previous messages on
Greek as an example of the "bundling" requirement, however I can't
find any previous reference to specific problems you might have had
with DNAME. Could you elaborate?

> The revision of the IDNA protocol to IDNA2008 brought forward two other
> issues:
> 1. The mapping of the upper case letters to the lower case is no longer a
> feature of the protocol but rather a task of the application. This way we
> cannot have consistent mappings since we do not know what the programmer has
> chosen to do with the upper case characters, especially in regards to tonos
> and final sigma.

This uncertainty about what the application will do with "bundled"
names as far as treating them "the same" seems to be the underlying
concern that motivates all the discussion we've had about adding
functionality to the DNS to support the "sameness" property.

However, it's also been strongly argued here that there's no way to
support "aliases" in the DNS without application support, particularly
without introducing inconsistencies in handling of certificates and
other objects that rely on domain names. So the tension that needs to
be explained in the next version of the document is between the need
for providing this kind of "help" to applications, and the challenge
of getting them to use it.

> We are in favor of a solution of the BNAME type proposal. We do not intend
> to SHADOW the .gr zone to another one but we would really like to "make
> similar" a great number of IDN domain names that will have variants. This
> way, while a SHADOW would be helpful only to our registrants wishing to
> "make similar" the variants themselves we as a registry would like to
> provide to our registrants the easiest solution of not having to deal
> extensively with DNS. The registrant could just ask the registry to provide
> the "sameness" for the variants in the BNAME form.

The thing that worries me about this is that the registry can provide
BNAMEs, but if applications don't make use of the "sameness"
semantics, we haven't really gained anything....

> I hope that Olafur in his email on the 1st of February was mistaken
> when he declared the item "Aliasing Requirements" dead and a
> discussion will take place in the next DNSSEC meeting to initiate
> the solution procedure.

The requirements document is a WG item under the recent charter, and
it remains my intent (as I believe Olafur knows) to make sure the
document is completed as an Informational RFC in the near future. The
work item isn't done until the WG has decided one way or another
whether to pursue additional work on the subject, so I'll respectfully
disagree with Olafur's assertion.

Whether there's a meeting of DNSEXT in Prague or not, the WG version
of this draft will ship soon so we can continue the discussion.


best,
Suzanne