Re: [idn] draft-ietf-idn-requirements-07.txt

Dan <Dan.Oscarsson@trab.se> Wed, 27 June 2001 10:18 UTC

Received: from psg.com (exim@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA27157 for <idn-archive@lists.ietf.org>; Wed, 27 Jun 2001 06:18:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1) id 15FC2B-000OCl-00 for idn-data@psg.com; Wed, 27 Jun 2001 02:54:55 -0700
Received: from malmo.trab.se ([131.115.48.10]) by psg.com with esmtp (Exim 3.16 #1) id 15FC2A-000OCe-00 for idn@ops.ietf.org; Wed, 27 Jun 2001 02:54:54 -0700
Received: from terra (terra.malmo.trab.se [131.115.48.22]) by malmo.trab.se (8.10.1/TRAB-primary-2) with SMTP id f5R9r8t09094; Wed, 27 Jun 2001 11:53:08 +0200 (MEST)
Message-Id: <200106270953.f5R9r8t09094@malmo.trab.se>
Date: Wed, 27 Jun 2001 11:53:07 +0200
From: Dan <Dan.Oscarsson@trab.se>
Reply-To: Dan <Dan.Oscarsson@trab.se>
Subject: Re: [idn] draft-ietf-idn-requirements-07.txt
To: idn@ops.ietf.org, phoffman@imc.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset="us-ascii"
Content-MD5: QcW2Jvw/rwSZfpfoiokRBw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc
Sender: owner-idn@ops.ietf.org
Precedence: bulk

>>How are we going to handle a draft like IDNA that does not change the
>>DNS protocol and does not fulfill all protocol requirements?
>>In [3] it is said that the protocol must not limit the code points
>>that can be used. As IDNA does not change the protocol, it does not
>>limit the protocol directely, but it does indirectely as some IDNA
>>removes all upper case letters.
>
>Nothing in IDNA "removes all upper case letters". Please point to the 
>specific text of IDNA that you think does so.

IDNA requires nameprep which removes all upper case letters by converting
them to lower case. IDNA requires that all names are canonicalised
which results if data being destoyed.

>
>>  And in [13] it says that the
>>protocol must specify how characters are encoded in DNS records.
>>This is not solved by IDNA - it only says how characters in names can
>>be encoded.
>
>Not true. It says exactly how they are encoded: using the ACE that 
>will be picked by this WG.

It only says how "names" are to be encoded. In a DNS record there are
other parts than names that contain characters. IDNA does not cover
them.

>
>>In [19] it is said that cononicalisation must be done at a single
>>well-defined place in the DNS resolution process. As canonicalisation
>>may result in data being destroyed, it should be required that
>>if canonicalisation is done at client end the canonicalisation
>>process must not destroy data in a name.
>
>That is impossible. Canonicalizing Unicode strings will possibly 
>destroy data no matter where you do it.

No, not if the canonicalisation is only done for comparing of strings.
If a client compares domain names by canonicalisation names, and a DNS
server does it when it compares name, and only the normalised string
is sent in the protocol then canonicalisation will not destroy the data
in the DNS names.

In IDNA it is required that the names are canonicalised when transmitted
in the DNS protocol while in UDNS name need only be normalised. So in
IDNA data in names are destroyed but not in UDNS.

   Dan