Re: [dnsext] Name equivalence - thoughts on the Greek issue

Andrew Sullivan <ajs@shinkuro.com> Mon, 13 September 2010 16:58 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 426213A6A20; Mon, 13 Sep 2010 09:58:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.992
X-Spam-Level:
X-Spam-Status: No, score=-101.992 tagged_above=-999 required=5 tests=[AWL=0.607, BAYES_00=-2.599, 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 ioEz3zYDhilV; Mon, 13 Sep 2010 09:58:02 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 2EBC43A6A1E; Mon, 13 Sep 2010 09:58:02 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1OvCJ8-000NGu-EP for namedroppers-data0@psg.com; Mon, 13 Sep 2010 16:55:06 +0000
Received: from mail.yitter.info ([208.86.224.201]) by psg.com with esmtps (TLSv1:CAMELLIA256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <ajs@shinkuro.com>) id 1OvCJ5-000NG3-Mv for namedroppers@ops.ietf.org; Mon, 13 Sep 2010 16:55:03 +0000
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id C02A51ECB408 for <namedroppers@ops.ietf.org>; Mon, 13 Sep 2010 16:55:01 +0000 (UTC)
Date: Mon, 13 Sep 2010 12:54:55 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: namedroppers@ops.ietf.org
Subject: Re: [dnsext] Name equivalence - thoughts on the Greek issue
Message-ID: <20100913165454.GJ19594@shinkuro.com>
Mail-Followup-To: namedroppers@ops.ietf.org
References: <AANLkTiktL=5b_izJGpuOPHHoOH0XJoVbTJK+0H5FoXUP@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <AANLkTiktL=5b_izJGpuOPHHoOH0XJoVbTJK+0H5FoXUP@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
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 Mon, Sep 13, 2010 at 01:35:01PM -0300, Brian Dickson wrote:

> For instance, if the encodings of a specific character, with and without
> some special property unique to the language/script of its origin (such as
> Greek "tonos"), were to differ only in the ASCII case of the encoding
> itself, the problem goes away by virtue of DNS case insensitivity.
> 
> This would require (some) encodings that on a per-character basis are
> byte-aligned, meaning each original character becomes an integer number of
> characters.

Uh, I think (1) that this is now well into the weeds for this
discussion and (2) you seem not to be attending to the unhappy fact
that IDNA2008 is all based on UTF-8, and that that bears with it a
large number of issues having to do with Unicode and the way it
happened to develop, historically speaking.

Moreover,

> The rest of RFC 3490 and RFC 3492 would need to be -bis'd to handle the
> additional logic and ACE prefix(es).

your targets are wrong.  The present discussion has been inspired
primarily by the effects of obsoleting 3490 and updating 3491.  One of
those effects was to remove all the mapping from the protocol.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.