Re: Comments on draft-ietf-idnabis-defs-10

Patrik Fältström <patrik@frobbit.se> Mon, 31 August 2009 06:24 UTC

Return-Path: <patrik@frobbit.se>
X-Original-To: idna-update@alvestrand.no
Delivered-To: idna-update@alvestrand.no
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id E834139E3BD for <idna-update@alvestrand.no>; Mon, 31 Aug 2009 08:24:44 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qwrvmc1OrDL6 for <idna-update@alvestrand.no>; Mon, 31 Aug 2009 08:24:40 +0200 (CEST)
X-Greylist: domain auto-whitelisted by SQLgrey-1.6.8
Received: from srv01.frobbit.se (srv01.frobbit.se [85.30.129.39]) by eikenes.alvestrand.no (Postfix) with ESMTP id CD1A139E3B7 for <idna-update@alvestrand.no>; Mon, 31 Aug 2009 08:24:40 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id 9C1966D7F3BD; Mon, 31 Aug 2009 08:24:40 +0200 (CEST)
X-Virus-Scanned: amavisd-new at frobbit.se
Received: from srv01.frobbit.se ([127.0.0.1]) by localhost (srv01.frobbit.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oS3GlHvQRPZM; Mon, 31 Aug 2009 08:24:40 +0200 (CEST)
Received: from [192.165.72.14] (64-103-25-233.cisco.com [64.103.25.233]) by srv01.frobbit.se (Postfix) with ESMTP id D8C556D7F3B5; Mon, 31 Aug 2009 08:24:39 +0200 (CEST)
Message-Id: <73AC7457-56E7-49FE-BBF1-4CDAD86C9C23@frobbit.se>
From: Patrik Fältström <patrik@frobbit.se>
To: Wil Tan <wil@cloudregistry.net>
In-Reply-To: <2c74643b0908302309u3f3b56efvccd3ce6b83849914@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Apple-Mail-94-662255417"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: Comments on draft-ietf-idnabis-defs-10
Date: Mon, 31 Aug 2009 08:24:38 +0200
References: <20090825032439.GF3180@shinkuro.com> <FA0AF06A3A27B9D75E54EA87@PST.JCK.COM> <2c74643b0908301122l4574d4acoc68f36a8576adf04@mail.gmail.com> <61FA36B9-90A5-4C2E-A68C-9983ACE8658A@frobbit.se> <CD9192CC-0069-4267-8BC2-620131346152@frobbit.se> <71226B6F-5286-47F8-9487-317A1D7B4536@frobbit.se> <3ABA414A34AF578C387B17CC@PST.JCK.COM> <2c74643b0908302309u3f3b56efvccd3ce6b83849914@mail.gmail.com>
X-Pgp-Agent: GPGMail d55 (v55, Leopard)
X-Mailer: Apple Mail (2.936)
Cc: IDNA update work <idna-update@alvestrand.no>, John C Klensin <klensin@jck.com>
X-BeenThere: idna-update@alvestrand.no
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IDNA update work <idna-update.alvestrand.no>
List-Unsubscribe: <http://www.alvestrand.no/mailman/listinfo/idna-update>, <mailto:idna-update-request@alvestrand.no?subject=unsubscribe>
List-Archive: <http://www.alvestrand.no/pipermail/idna-update>
List-Post: <mailto:idna-update@alvestrand.no>
List-Help: <mailto:idna-update-request@alvestrand.no?subject=help>
List-Subscribe: <http://www.alvestrand.no/mailman/listinfo/idna-update>, <mailto:idna-update-request@alvestrand.no?subject=subscribe>
X-List-Received-Date: Mon, 31 Aug 2009 06:24:45 -0000

To reiterate, yes, I agree.

We also should remember, when fixing this, that ascii labels might  
swap casing in the DNS server for security reasons.

See draft-vixie-dnsext-dns0x20-00.txt

http://stupid.domain.name/ietf/draft-vixie-dnsext-dns0x20-00.txt

A-labels must because of this be lower cased before doing de-punycode.

Mumble...

    Patrik

On 31 aug 2009, at 08.09, Wil Tan wrote:

> Agreed. I just came to the same conclusion too.
>
> 2009/8/31 John C Klensin <klensin@jck.com>
>
>>
>>
>> --On Monday, August 31, 2009 07:10 +0200 Patrik Fältström
>> <patrik@frobbit.se> wrote:
>>
>>>
>>> On 31 aug 2009, at 07.05, Patrik Fältström wrote:
>>>
>>>> So, casefold of the ascii in the A-label only result in
>>>> casefold of the ascii in the U-label.
>>>
>>> Ok, after a gulp of coffee, I see your point.
>>>
>>> In the tables document we have the following:
>>>
>>>> 2.5. LDH (E) E:
>>>>
>>>>    cp is in {002D, 0030..0039, 0061..007A}
>>>
>>> That make for example 'F' illegal in an U-label.
>>>
>>> By changing this rule to the following, uppercase ASCII would
>>> be ok to have in an U-label.
>>>
>>> 2.5. LDH (E) E:
>>>
>>>     cp is in {002D, 0030..0039, 0041..005A, 0061..007A}
>>
>> But that would be a mistake, IMO, because it would result in
>> U-labels containing uppercase ASCII that produce different
>> A-labels from the same U-label with lowercase ASCII.  Those
>> A-labels would match in the DNS, which uses case-insensitive
>> comparison, but not in ordinary string comparisons (because they
>> are different).
>>
>> Put differently, that would give us a pair of U-labels that do
>> not compare equal on bitstring comparison (the only kind of
>> comparison defined for U-labels) but which produce equivalent
>> (although not identical) A-labels.  And, because of the
>> compression "feature", we would lose unambiguous symmetry of
>> A-labels and U-labels because, depending on where it came from,
>> a given A-label (and its DNS-equivalents) could produce
>> different U-labels.
>>
>> This would also imply that
>>  "Fältström" and "fältström"
>> would be valid U-labels but that "FÄLTSTRÖM" would not be
>> because Ä and Ö are both DISALLOWED.  I don't think we want to
>> go there.
>>
>>   john
>>
>>
>>
>> _______________________________________________
>> Idna-update mailing list
>> Idna-update@alvestrand.no
>> http://www.alvestrand.no/mailman/listinfo/idna-update
>>
>
>
>
> -- 
> Wil Tan
> CTO
> Cloud Registry <http://www.cloudregistry.net>