From owner-idn@ops.ietf.org  Sun Jul  1 12:44:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA12686
	for <idn-archive@lists.ietf.org>; Sun, 1 Jul 2001 12:44:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.30 #1)
	id 15Gk35-000Add-00
	for idn-data@psg.com; Sun, 01 Jul 2001 09:26:15 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.30 #1)
	id 15Gk33-000AdW-00
	for idn@ops.ietf.org; Sun, 01 Jul 2001 09:26:13 -0700
Received: from [216.153.32.39] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 153083; Sun, 01 Jul 2001 09:25:32 -0700
Message-ID: <3B3F4ED4.C2CABE13@ehsco.com>
Date: Sun, 01 Jul 2001 11:24:53 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: James Seng/Personal <James@Seng.cc>
CC: Edmon <edmon@neteka.com>, idn@ops.ietf.org
Subject: Re: [idn] Who supports UDNS (ACE+UTF-8)
References: <200106291552.f5TFqeX29046@nic-naa.net> <007a01c100e9$ac734520$1001a8c0@neteka.com> <3B3D57C4.76E504A3@ehsco.com> <001001c101ca$6c605a40$0201000a@jamessonyvaio>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> Thus, *if* we have the opportunity to 'fix' this, why do we need to
> change to 63 Unicode character limit too? Why not more just in case?

*when* we go to UTF8-over-EDNS (hehe) it will be important to make it
enticing to users and developers. Keeping as many rules as similar as
possible across the methods will be important to the latter camp. If they
have a web form which allows input, they won't want to have server-side
and client-side input controls based on whether the input is ASCII or
UTF8. That would be really hard.

Sticking with 63 "characters" means that input rules work the same whether
they are ASCII or UTF8.

Usability will be the defining factor for success, IMO. Making it hard to
deploy is self-defeating.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Sun Jul  1 22:51:09 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA17598
	for <idn-archive@lists.ietf.org>; Sun, 1 Jul 2001 22:51:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.30 #1)
	id 15GtTO-0004uK-00
	for idn-data@psg.com; Sun, 01 Jul 2001 19:30:02 -0700
Received: from drugs.dv.isc.org ([130.155.191.236])
	by psg.com with esmtp (Exim 3.30 #1)
	id 15GtTL-0004u7-00
	for idn@ops.ietf.org; Sun, 01 Jul 2001 19:29:59 -0700
Received: from nominum.com (localhost.dv.isc.org [127.0.0.1])
	by drugs.dv.isc.org (8.11.3/8.11.2) with ESMTP id f622Tju73163
	for <idn@ops.ietf.org>; Mon, 2 Jul 2001 12:29:55 +1000 (EST)
	(envelope-from marka@nominum.com)
Message-Id: <200107020229.f622Tju73163@drugs.dv.isc.org>
To: idn@ops.ietf.org
From: Mark.Andrews@nominum.com
Subject: Re: [idn] Who supports UDNS (ACE+UTF-8) 
In-reply-to: Your message of "Fri, 29 Jun 2001 18:20:13 -0400."
             <007a01c100e9$ac734520$1001a8c0@neteka.com> 
Date: Mon, 02 Jul 2001 12:29:45 +1000
Sender: owner-idn@ops.ietf.org
Precedence: bulk


> - uses EDNS to allow longer labels than 63 bytes.

	EDNS is useless for this.  See the experience with bitstring
	labels deployment.  Extending the label size has the same
	problems.  In both cases you are using the new label types
	in the question and not in only in the answer.

--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@nominum.com



From owner-idn@ops.ietf.org  Mon Jul  2 11:19:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA28418
	for <idn-archive@lists.ietf.org>; Mon, 2 Jul 2001 11:19:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.30 #1)
	id 15H58Y-00010c-00
	for idn-data@psg.com; Mon, 02 Jul 2001 07:57:18 -0700
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.30 #1)
	id 15H58W-00010T-00
	for idn@ops.ietf.org; Mon, 02 Jul 2001 07:57:16 -0700
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10653;
	Mon, 2 Jul 2001 10:56:29 -0400 (EDT)
Message-Id: <200107021456.KAA10653@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: idn@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [idn] I-D ACTION:draft-ietf-idn-lsb-ace-00.txt
Date: Mon, 02 Jul 2001 10:56:29 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internationalized Domain Name Working Group of the IETF.

	Title		: Improving ACE using code point reordering v0.9
	Author(s)	: S. Lee
	Filename	: draft-ietf-idn-lsb-ace-00.txt
	Pages		: 
	Date		: 29-Jun-01
	
This document describes code point reordering to improve ACE 
compression algorithms. Based on frequency statistics of characater
sets, this reordering is easily implemented with simple character 
mapping tables.
DUDE implementation of this idea shows great improvements for
Hangul, Chineses, Vietnamese and European domains.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idn-lsb-ace-00.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-idn-lsb-ace-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-idn-lsb-ace-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010629141539.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idn-lsb-ace-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idn-lsb-ace-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010629141539.I-D@ietf.org>

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Tue Jul  3 10:02:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA19619
	for <idn-archive@lists.ietf.org>; Tue, 3 Jul 2001 10:02:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.30 #1)
	id 15HQUT-000DBj-00
	for idn-data@psg.com; Tue, 03 Jul 2001 06:45:21 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.30 #1)
	id 15HQUR-000DBa-00
	for idn@ops.ietf.org; Tue, 03 Jul 2001 06:45:19 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f63DjBT04088;
	Tue, 3 Jul 2001 22:45:11 +0900 (KST)
Message-ID: <04dd01c103c7$0eeef0c0$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Cc: <lsb@postel.co.kr>
Subject: [idn] [FYI]  improving ACE using code point reordering v1.0
Date: Tue, 3 Jul 2001 22:50:01 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

I have a new revision of my I-D:  improving ACE using code point reordering
v1.0
 http://www.postel.co.kr/lsb-ace-01.txt   ( sources included for dude and
amc-w)

It reports 30%~ 58% improvements in compressing ACE labels of
typical han/hangeul business names in CJK.

Reordering  v1.0  is based on character frequency plus
WORD ADJACENCY statitistics on modern han/hangeul business names
and the fact that most frequent 256 han letters have cumulative
usage frequency of near 60%  ( for top freq 256 hangul syllables,
about 80%).

I applied this reordering to both DUDE and AMC-ACE-W, and found
DUDE outperforms AMC-ACE-W even for han/hangul.

I think  tricks, tuning or heuristics (not based on language-specific
knowledge) are not enough to get the 'ceiling' ACE compression ratio.

I propose "Let  languages compress themselves  in new reordering layer
between NAMEPREP and ACE, and leave ACE encoding as simple as possible".


Your careful evaluation and feedback, please.

Thanks.

Soobok, lsb@postel.co.kr

----------------------------------------------------------------------------
---
Example Strings

    About 30%~58% improvement in DUDE compression ratio is achieved in
    these Hangul examples.

    LDUDE and LAMCW denote reordering-applied DUDE-02 and
    AMC-ACE-W, respectively. (AMCW for AMC-ACE-W).
    Most examples show LDUDE outperforms LAMCW.

    (K1) Korean String 1: ( 24 hangul syllables )
      u+C138 u+ACC4 u+C758 u+BAA8 u+B4E0 u+C0AC u+B78C u+B4E4
      u+C774 u+D55C u+AD6D u+C5B4 u+B97C u+C774 u+D574 u+D55C
      u+B2E4 u+BA74 u+C5BC u+B9C8 u+B098 u+C88B

      DUDE-02 : 6txiy79ny53nz79a8wizwwnzzuavyizv3atuuiz2vby27jz66iz8sit\
                usauiyz5i23az96iz6ze3xaz2td ( 82 chars )
      LDUDE   : 5suhxb9jt2pydtwetwkxhtsrxhbyhvsmvvk7r2ityd6atqt8etvittk
                ( 55 chars, 33.9% shorter )
      AMCW    : 6tvifgem42ixihhakfnh6nhhem5wrk6fmpmpwim6m5wrmwxn5u8eivw\
                mp6iqige2nem ( 67 chars )
      LAMCW   : 5swhtg8r5tycsb5swfgirxi5sxhsabyg5vypgcz2isa5tyd4d5p5sxj\
                gmbgd5 ( 61 chars )


    (K2) Korean String 2:  ( 9 hangul syllables )
      <KRNIC in korean>
      U+D55C U+AD6D U+C778 U+D130 U+B137 U+C815 U+BCF4 U+C13C

      DUDE-02 : 7xvNz2vBy4tFtywIyssHz3uCzw8Bz76I
                ( 32 chars )
      LDUDE   : 5syAB3BIJ7BB7N
                ( 14 chars,  56.2% shorter )
      AMCW    : 7xxNFmpM52QjsGjzNaxJhwKj6
                ( 25 chars )
      LAMCW   : 5ssAsB3AIBwAB3P
                ( 15 chars )


    (K3) Korean String 3:  ( 18 hangul syllables )
      U+C804 U+AD6D U+C2E4 U+C9C1 U+B178 U+C219 U+C790 U+B300
      U+CC45 U+C885 U+AD50 U+C2DC U+BBFC U+B2E8 U+CCB4 U+D611
      U+C758 U+D68C

      DUDE-02 : 62yEyxyJy92J5uFz25JzvyBx2Jzw3Az9wFw6Ayx7Fy92Nz3uA3tEz8\
                xNt44FttwJtt7E ( 68 chars )
      LDUDE   : 5szAtBtvBt7Mt2Qv4Qu7KtFt5It3MuEvAtvDyJCtuC4G4J
                ( 46 chars,  32% shorter )
      AMCW    : 62sEFmpKzeNqbGm2Ks3M6sG2aPcfNefFksKy6I96GziPfwRstM42Rwn
                ( 55 chars )
      LAMCW   : 5stAsB5tvAGhmGmgG2mGatsE5t7JGbhsDvD5tsAyIK5swJ8RwG
                ( 50 chars )


    (K4) Korean String 4:  ( 7 hangul syllables )
      <Hynics Semiconductor in korean>
      U+D558 U+C774 U+B2C9 U+C2A4 U+BC18 U+B3C4 U+CCB4

      DUDE-02 : 7xvItuuNzx5PzsyPz85N97Nz9zA
                ( 27 chars )
      LDUDE   : 5s3C4F5Q7PtwRtMK
                ( 16 chars,  40% shorter )
      AMCW    : 7xxIM5wGyjKxeJa2G8ePfw
                ( 22 chars )
      LAMCW   : 5s9CxH8JvE5tzMyAK
                ( 17 chars )


    (K5) Korean String 5:  ( 13 hangul syllables )
      U+D658 U+ACBD U+C6B4 U+B3D9 U+C5F0 U+D569 U+BC18 U+D575
      U+D2B9 U+BCC4 U+C704 U+C6D0 U+D68C

      DUDE-02 : 7yvIz48Fy4sJzxyPzyuJts3Jy3zBy3yPz6Ny8zPz56At7EtsxN
                ( 50 chars )
      LDUDE   : 5s7NB4EDvHFtxDv5Kv6NtIt4R5GwK
                ( 29 chars, 42% shorter )
      AMCW    : 7yxIFf7MxwG83MrsRmjJa2RmxQx3JgeM2eMysRwn
                ( 40 chars )
      LAMCW   : 5s5N5PtJKuPI5tzMGybGiptF5s5KsNwG
                ( 32 chars )



    About 35%~50% improvement in DUDE compression ratio is achieved in
    these UniHan examples.

    (TC1) Traditional Chinese String 1: ( 16 letters )
      u+5354 u+91c7 u+5065 u+5eb7 u+4e8b u+696d u+670d u+52d9
      u+7db2 u+002d u+5354 u+91c7 u+6709 u+9650 u+516c u+53f8

      DUDE-02 : xvve6u3d6t4c87ctsvnuz8g8yavx7eu9ym-u88g6u3d9y6q9txj6z\
                vnu3e  ( 58 chars)
      LDUDE   : xs8qy7ny9jhyi6f6bb8h-4iy7nyxkbed
                ( 32 chars, 44.8% shorter)
      AMCW    : xvxen8huyfafzs2mc5pcipw7jh7u--xxen8hcijqcsvynx9i
                ( 48 chars )
      LAMCW   : xs2q2xcu4m4n6esb6abug--2q2xcusijpq
                ( 34 chars )


    (TC2) Traditional Chinese String 2: ( 21 letters )
      u+5317 u+4eac u+5e02 u+91ab u+85e5 u+7d93 u+6fdf u+6280
      u+8853 u+7d93 u+71df u+516c u+53f8 u+5fa1 u+91ab u+7db2
      u+7d61 u+83ef u+91ab u+7db2 u+8def

      DUDE-02 : xvzht75mts4q694jtwwq92zgtuwn7xr847d9x6a6wnus5du3e6xj6\
                8sk86tj7d982qtuwe86tj9sxp ( 78 chars)
      LDUDE   : xtwicfz6b99a38g27c2vdd8cz7mzuqdt6izuiy6iz5nz5fy6by6ib
                ( 53 chars, 32.0% shorter)
      AMCW    : xvths4naacn7mj9fh6veq9beakuvh6ve89vynx9iapbn7mh7uyb2v\
                8rn7mh7um9r ( 64 chars )
      LAMCW   : xtuiukr28q5tqu9i4ukutjk9i3uduspqv6g28quug33kuur28quugh
                ( 54 chars )


    (TC3) Traditional Chinese String 3: ( 18 letters )
      u+795e u+8fb2 u+7db2 u+990a u+8eab u+4fdd u+5065 u+7db2
      u+5065 u+5eb7 u+4e16 u+754c u+5065 u+5eb7 u+8a2d u+8a08
      u+5bb6 u+60e0

      DUDE-02 : z3vq9y8n9usa8w5itz4b6tzgt95iu77hu77h87cts4bv5xkuxuj87\
                c7w3kuf7t5qv5xg ( 68 chars )
      LDUDE   : xwsiw5e9kzyqz8fhb2p2phtvgxtbwuah8qbtwmyg
                ( 40 chars, 41.1% shorter )
      AMCW    : z3xqnpuh7uq2knfmt7puyfh7uuyfafzstgf4nuyfafzmbpsi75gys\
                8a ( 55 chars )
      LAMCW   : xwyiu7nug3wiu4pkmug4mnv3ky2mu4mnwcdvsiyq
                ( 40 chars )


    (SC1) Simplified Chinese String  1 : ( 16 letters )
      <ministry of foreign trade and economic cooperation, PRC>
      u+4e2d u+534e u+4eba u+6c11 u+5171 u+548c u+56fd u+5bf9
      u+5916 u+8d38 u+6613 u+7ecf u+6d4e u+5408 u+4f5c u+90e8

      DUDE-02 : w8wpt7ydt79euu4mv7yax9puzb7seu8r7wuq85umt27ntv2bv3wgt\
                5xe795e ( 60 chars )
      LDUDE   : xswjuzru6nu7fv7kv4gutrwgb7mbwiu6cuzqqxm
                ( 39 chars, 35.0% shorter )
      AMCW    : w8up29ps5kdst5uh7ygsup29pm3cb39n8tknpb39hkygswhdysupa\
                qd ( 55 chars )
      LAMCW   : xsujwxgu3kwwrv3fwvduunykm5ab9jwvmuwfmta
                ( 39 chars )


    (SC2) Simplified Chinese String  2 : ( 18 letters )
      u+4e2d u+56fd u+4eba u+6c11 u+5927 u+5b66 u+4e2d u+56fd
      u+8d22 u+653f u+91d1 u+878d u+653f u+7b56 u+7814 u+7a76
      u+4e2d u+5fc3

      DUDE-02 : w8wpt27at2whuu4mvxvguwbtxwmt27a757r82tp9w8qtyxn8u5ct\
                8yjvwcuycvwxmtt8q ( 69 chars )
      LDUDE   : xswjf5gu7fu6rb4ifz8dx6ju8gnu8kwugy8fd8rd
                ( 40 chars, 42.2% shorter )
      LAMCW   : xsujun3kwwru2abujn36rwsgu8anwsg2uau6fgujk
                ( 41 chars )


    About 20%~35% improvement in DUDE compression ratio is achieved in
    these Japanese Kanji/Katakana examples.

    (JP1) Japanese String 1: ( 25 letters )
      U+793E U+56E3 U+6CD5 U+4EBA U+65E5 U+672C U+30CD U+30C3 U+30C8
      U+30EF U+30FC U+30AF U+30A4 U+30F3 U+30D5 U+30A9 U+30E1 U+30FC
      U+30B7 U+30E7 U+30F3 U+30BB U+30F3 U+30BF U+30FC

      DUDE-02 : z3xQu97Pv4vGuuyRu5xRu6Jxz8BQMuHtDxDMxHuGzNwItPwMxAtE\
                wIwIwNwD  (60 chars)
      LDUDE   : xs8Nu2Cu4RvMGBysxGyCKtHtQCPFtAyPyKtPBGPyAyAyFyR
                ( 47 chars, 21.6% shorter)
      AMCW    : z3vQ28DDyxs5KB9fCjnvs6P6DI8R9N4RE9D7F4J8B9N5H8H9D5M9\
                D5R9N ( 57 chars )
      LAMCW   : xs2NwsQu4B3KNPvs6M4JD5E4KIFA5A7P5H4KMPA6A4A6F4K
                ( 47 chars )


    (JP2) Japanese String 2: ( 16 letters )
      U+8CA1 U+56E3 U+6CD5 U+4EBA U+5317 U+6D77 U+9053 U+81EA
      U+7136 U+4FDD U+8B77 U+63A8 U+9032 U+5354 U+4F1A

      DUDE-02 : 266B74wCv4vGuuyRt74Pv8yA97uEtt5J9s7Nv88M6w4K827R9v3K\
                6vyGt6wQ (60 chars)
      LDUDE   : xs3Hu9Ju4RvMt5CFvuGvsRxtGw5Iz2Ev6BzIwtJE
                ( 40 chars, 33.3% shorter)
      AMCW    : 264B28DDyxs5KxtHD5zNuvI9kE3yt7PMmzBpiNtuxxEttK
                ( 46 chars )
      LAMCW   : xs9HwsQu4B3KvuIPwsMvsEytCu4K3uQy8R3Hu2QK
                ( 40 chars )


    (JP3) Japanese String 3: ( 16 letters )
      U+6771 U+4EAC U+90FD U+60C5 U+5831 U+30B5 U+30FC U+30D3 U+30B9
      U+7523 U+696D U+5065 U+5EB7 U+4FDD U+967A U+7D44 U+5408

      DUDE-02 : yztBu37P78xB9svIv29Ey22EwJuRyKwx3Kt6wQv3sI87CttyK734\
                H85vQu3wN (61 chars)
      LDUDE   : xttHxPvtFu9CDyssAyEyHyRys9PxQ4KHGEu4CuwJ
                ( 40 chars, 34.4% shorter)
      AMCW    : z3vQ28DDyxs5KB9fCjnvs6P6DI8R9N4RE9D7F4J8B9N5H8H9D5M9\
                D5R9N ( 57 chars )
      LAMCW   : xs2NwsQu4B3KNPvs6M4JD5E4KIFA5A7P5H4KMPA6A4A6F4K
                ( 47 chars )



    LDUDE-2  shows the same good compression ratio for Latin family of
    scripts.

    (L1) Vietnamese: ( 38 syllables using diacritical marks )
      Ta<dotbelow>isaoho<dotbelow>kh<ocirc>ngth<ecirc><hookabove>chi\
      <hookabove>no<acute>iti<ecirc><acute>ngVi<ecirc><dotbelow>t
      U+0054 u+0061 u+0323 u+0069 u+0073 u+0061 u+006F u+0068 u+006F
      u+0323 u+006B u+0068 u+00F4 u+006E u+0067 u+0074 u+0068 u+00EA
      u+0309 u+0063 u+0068 u+0069 u+0309 u+006E u+006F u+0301 u+0069
      u+0074 u+0069 u+00EA u+0301 u+006E u+0067 U+0056 u+0069 u+00EA
      u+0323 u+0074

      DUDE-02 : vEvfvwcvwktktcqhhvwnvwid3n3kjtdtn2cv8dvykmbvyavyhbvyqv\
                yitptp2dv8mvyrjvBvr2dv6jvxh ( 82 chars )
      LDUDE   : uGuh5c5kckqhh5n4atm3n3ktmtdq2cxd7kmb7a7hb7q7irr2dxm7rt\
                muDvr2dvj5f (66 chars , 16 chars(19%) shorter)


    (L2) Spanish: ( using basic Latin & Latin Supplement )
      Porqu<eacute>nopuedensimplementehablarenEspa<ntilde>ol
      U+0050 u+006F u+0072 u+0071 u+0075 u+00E9 u+006E u+006F u+0070
      u+0075 u+0065 u+0064 u+0065 u+006E u+0073 u+0069 u+006D u+0070
      u+006C u+0065 u+006D u+0065 u+006E u+0074 u+0065 u+0068 u+0061
      u+0062 u+006C u+0061 u+0072 u+0065 u+006E U+0045 u+0073 u+0070
      u+0061 u+00F1 u+006F u+006C

      DUDE-02 : vAvrtpde3n2hbtrftabbmtptketptnjiimtktbpjdqptdthmuMvgdt\
                b3a3qd  (61 chars)
      LDUDE   : uAurftmtg2q2hbrhcbbmfcepnjiimidpjdqpmrmuMuqmb3a3qd
                (51 chars, 10 chars (16%) shorter)


    (L3) Czech:  (using Latin Extended A)
      Pro<ccaron>prost<ecaron>nemluv<iacute><ccaron>esky
      U+0050 u+0072 u+006F u+010D u+0070 u+0072 u+006F u+0073 u+0074
      u+011B u+006E u+0065 u+006D u+006C u+0075 u+0076 u+00ED u+010D
      u+0065 u+0073 u+006B u+0079

      DUDE-02 : vAuctptyctzpctptnhtyrtzfmibtjd3mt8atyitgtitc
                (45 chars)
      LDUDE   : uAukfycypkfepzpzfmibmtb3m8ayiqtik
                (34 chars, 24% shorter)







From owner-idn@ops.ietf.org  Tue Jul  3 10:09:02 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA23717
	for <idn-archive@lists.ietf.org>; Tue, 3 Jul 2001 10:09:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.30 #1)
	id 15HQhr-000Ddo-00
	for idn-data@psg.com; Tue, 03 Jul 2001 06:59:11 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.30 #1)
	id 15HQhq-000Ddh-00
	for idn@ops.ietf.org; Tue, 03 Jul 2001 06:59:10 -0700
Message-ID: <002d01c103c8$db812120$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: "John C Klensin" <klensin@jck.com>
Cc: <idn@ops.ietf.org>
References: <007a01c100e9$ac734520$1001a8c0@neteka.com> <71961143.993843588@P2>
Subject: Re: [idn] Who supports UDNS (ACE+UTF-8)
Date: Tue, 3 Jul 2001 10:02:51 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sorry for the slow reply... it was "flag day" here in Canada.. ;-)
I mean that if we use EDNS to signal IDN and then specify that the
"count"="character count" instead of "octet count" then we can have 63
characters all through.
Edmon

----- Original Message -----
From: "John C Klensin" <klensin@jck.com>
To: "Edmon" <edmon@neteka.com>
Cc: <idn@ops.ietf.org>
Sent: Friday, June 29, 2001 7:39 PM
Subject: Re: [idn] Who supports UDNS (ACE+UTF-8)


> --On Friday, 29 June, 2001 18:20 -0400 Edmon <edmon@neteka.com>
> wrote:
>
> >...
> > Perhaps if we use UCS directly then the "count" can actually
> > be the number of Unicode code points and every language will
> > have 63 "character" spaces to use.
>
> Edmon,
>
> I have having trouble understanding what you are proposing here.
> The limit of 63 octets is a fundamental DNS limitation, at least
> within Class=IN (I can imagine having rules that would extend it
> in other Classes, just as I can imagine EDNS rules that would
> extend it).  Consequently, "use of UCS[-4?] directly" presumably
> means that every language gets 15 character names (and you still
> need code tagging, but maybe we can make the three spare octets
> sufficient for that).
>
> Or are you planning a "flag day" replacement for the DNS?
>
> What am I missing?
>
>    john
>




From owner-idn@ops.ietf.org  Thu Jul  5 07:14:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA07291
	for <idn-archive@lists.ietf.org>; Thu, 5 Jul 2001 07:14:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15I6m3-0008vK-00
	for idn-data@psg.com; Thu, 05 Jul 2001 03:54:19 -0700
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15I6m2-0008vD-00
	for idn@ops.ietf.org; Thu, 05 Jul 2001 03:54:18 -0700
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06530;
	Thu, 5 Jul 2001 06:53:32 -0400 (EDT)
Message-Id: <200107051053.GAA06530@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: idn@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [idn] I-D ACTION:draft-ietf-idn-hangeulchar-00.txt
Date: Thu, 05 Jul 2001 06:53:32 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internationalized Domain Name Working Group of the IETF.

	Title		: Hangeul NAMEPREP recommendation version 1.0
	Author(s)	: S. Lee, G. Gim
	Filename	: draft-ietf-idn-hangeulchar-00.txt
	Pages		: 
	Date		: 03-Jul-01
	
This document suggests Hangeul-specific NAMEPREP recommendations.
It defines :
- mapping tables for half-width jamo and enclosed jamo
- excluding compatibility Hangeul jamo block 
from compatibility decomposition in normalization step
- criteria for determining invalid syl-ipf jamo sequence
- prohibited hangul filler character  in KC norm output.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idn-hangeulchar-00.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-idn-hangeulchar-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-idn-hangeulchar-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010703124644.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idn-hangeulchar-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idn-hangeulchar-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010703124644.I-D@ietf.org>

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Thu Jul  5 12:07:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA17821
	for <idn-archive@lists.ietf.org>; Thu, 5 Jul 2001 12:07:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IBJq-000GAJ-00
	for idn-data@psg.com; Thu, 05 Jul 2001 08:45:30 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15IBJp-000GAD-00
	for idn@ops.ietf.org; Thu, 05 Jul 2001 08:45:29 -0700
Message-ID: <006601c10569$ffa20e00$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: "Natalia Syracuse" <nsyracus@ietf.org>, "David Leung" <david@neteka.com>,
        "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>, <idn@ops.ietf.org>
Cc: <jseng@pobox.org.sg>
References: <5.1.0.14.1.20010705084656.02b0e138@mail.viagenie.qc.ca>
Subject: [idn] Re: permission <draft-ietf-idn-ace37-00.txt (attach)
Date: Thu, 5 Jul 2001 11:48:53 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi all,

I was unaware that the workgroup no longer accepts new drafts.  Anyway, I
have drafted a new ACE based on the simplicity of DUDE which has hugely
improved compression.  Worst case scenario CJK could have 21 han characters!
Attached below is a copy of the draft (for my original submission), you can
also find it at http://www.dnsii.org/idn-ace37-00.txt (easier to read) and
hopefully in the i-d-n.net website soon.

ACE37 is based on the one-pass one-mode scheme of DUDE (diiferential XOR),
then utilizes a simple code block shifting (similar to the reference points
in the AMC series) to hugely increase the capacity for CJK (worst case
scenario 21 han characters!) and then utilizes base-32 for compression (as
in LACE) (DUDE and AMC-w/v uses base-32 only for flagging).  In addition to
base-32, a base-4 scheme is introduced by using the remaining characters
{wxyz}.  These contain 2 bits of character information and doubles as an
indicator for codepoint brackets.  All the while, the algorithm is kept to
be as simple as DUDE.

Hopefully you might find that it is interesting and appropriate to be
considered as an ACE within the IETF.  Afterall, it was intended to be an
integrated version of the three primary ACEs: DUDE, LACE and the AMC series,
identified by the ACE design team report.

Looking forward to all your inputs.

Edmon

PS. I have created an Excel worksheet to illustrate the Encoding and
Decoding procedures as well you can find them at
http://www.dnsii.org/ace37/ace37-encode.xls and
http://www.dnsii.org/ace37/ace37-decode.xls respectively.



----- Original Message -----
From: "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>
To: "Natalia Syracuse" <nsyracus@ietf.org>; <edmon@neteka.com>;
<david@neteka.com>
Cc: <jseng@pobox.org.sg>
Sent: Thursday, July 05, 2001 8:50 AM
Subject: Re: permission <draft-ietf-idn-ace37-00.txt (attach)


> I'm sorry but the new wg policy is to not accept draft unless there is a
> demonstrated support. But drafts are _highly_ encouraged to be published
as
> individual submissions. I would recommend to put idn in the filename and
> use this filenaming convention: draft-<yourname>-idn-ace37-00.txt. After
> publication in the internet-draft, the author should announce it in the wg
> mailing list and I'll put a reference to it in the wg web page.
>
> So please publish it as individual submission.
>
> Marc.
>
> At/À 08:34 2001-07-05 -0400, Natalia Syracuse you wrote/vous écriviez:
> >
> >
> >
> >Internet Draft                                 Edmon Chung, Neteka Inc.
> ><draft-ietf-idn-ace37-00.txt>                  David Leung, Neteka Inc.
> >                                                               June 2001
> >
> >
> >
> >           ACE Utilizing All 37 Alphanumeric Characters (ACE37)
> >
> >
> >STATUS OF THIS MEMO
> >
> >    This document is an Internet-Draft and is in full conformance with
> >    all provisions of Section 10 of RFC2026.
> >
> >    Internet-Drafts are working documents of the Internet Engineering
> >    Task Force (IETF), its areas, and its working groups.  Note that
> >    other groups may also distribute working documents as Internet-
> >    Drafts.  Internet-Drafts are draft documents valid for a maximum of
> >    six months and may be updated, replaced, or obsoleted by other
> >    documents at any time.  It is inappropriate to use Internet-Drafts
> >    as reference material or to cite them other than as "work in
> >    progress."
> >
> >    The reader is cautioned not to depend on the values that appear in
> >    examples to be current or complete, since their purpose is primarily
> >    educational.  Distribution of this memo is unlimited.
> >
> >    The list of current Internet-Drafts can be accessed at
> >    http://www.ietf.org/ietf/1id-abstracts.txt
> >    The list of Internet-Draft Shadow Directories can be accessed at
> >    http://www.ietf.org/shadow.html.
> >
> >Abstract
> >
> >    ACE37 is a combination of DUDE-02, AMC-W/V and LACE.  ACE37 utilizes
> >    the simple one pass algorithm of DUDE, the character block
> >    considerations of AMC-W/V and the Base-32 compression of LACE.  It
> >    also fully utilizes entire LDH set currently allowed in the DNS (A-
> >    z, 0-9 and "-") within its character repertoire to optimize
> >    performance and compression.  Even for the worst-case scenario in
> >    ACE37, any name can have 21 characters including Chinese, Japanese
> >    and Korean names. Two Excel spreadsheets for ACE37 encoding and
> >    decoding can be found at http://www.dnsii.org/ace37/ace37-encode.xls
> >    and http://www.dnsii.org/ace37/ace37-decode.xls respectively.
> >
> >    While DUDE-02 provides a very efficient differential mechanism, its
> >    compression is inefficient as it fails to take advantage of the
> >    base-32 scheme in using all 5-bits for character information.  The
> >    AMC series is highly efficient in compression but requires
> >    complicated mode changes and therefore inefficient in process.  LACE
> >    is rather moderate and requires a two-pass mechanism but utilizes
> >    base-32 for good compression.
> >
> >
> >Chung & Leung                                                  [Page 1]
> >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> >
> >    ACE37 uses simple character block shifting to achieve the
> >    compression efficiency of the AMC series, retains the one-pass and
> >    one mode XOR differential mechanism used by DUDE while embracing the
> >    base-32 compression used by LACE for efficient character bit
> >    information.
> >
> >Terminology
> >
> >    The key words "MUST", "SHALL", "REQUIRED", "SHOULD", "RECOMMENDED",
> >    and "MAY" in this document are to be interpreted as described in RFC
> >    2119 [RFC2119].
> >
> >    LDH: Letters, Digits and Hyphens: a string of characters that
> >    consists only hyphens ("-"), English letters (A-z) and digits (0-9),
> >    which might not be a result of an algorithm for transcoding
> >    multilingual characters. For example: whatever-you-want.example
> >
> >    ACE - ASCII Compatible Encoding: a string of characters resulting
> >    from a particular algorithm for transforming multilingual character
> >    information into an alphanumeric form acceptable by the existing
> >    DNS.  For example: bq--3bhc2zmh.tld.  In essence, ACE is a subset of
> >    LDH.
> >
> >    Hexadecimal values are shown preceeded by "0x".  For example, 0x60
> >    is decimal 96.  Binary values are shown preceeded by "0b" for
> >    example "0b1000" is decimal 8.  As in the Unicode Standard
> >    [UNICODE], Unicode code points are denoted by "U+" followed by four
> >    to six hexadecimal digits, while a range of code points (or
> >    hexadecimal numbers) is denoted by two hexadecimal numbers separated
> >    by "..", with no prefixes.
> >
> >    Octets: sequences of 8 bits; Quintets: sequences of 5 bits;
> >    Quartets: sequences of 4 bits; Duplets: sequences of 2 bits.
> >
> >    XOR: bitwise exclusive or.  Given 2 nonnegative integers A and B, A
> >    XOR B is the nonnegative integer value whose binary representation
> >    is 1 wherever A and B disagrees, and 0 wherever they agree.
> >
> >Table Of Contents
> >
> >    1. Introduction....................................................3
> >    2. Code Block Shifting.............................................4
> >    3. Base-32 Characters..............................................5
> >    4. Base-4 Characters...............................................6
> >
> >    5. LDH Considerations..............................................9
> >    6. Encoding Procedure..............................................9
> >    7. Decoding Procedure.............................................11
> >    8. Examples.......................................................13
> >    9. Summary & Comparisons..........................................15
> >    10. Security Considerations.......................................16
> >    11. References....................................................16
> >
> >Chung & Leung                                                  [Page 2]
> >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> >
> >1. Introduction
> >
> >    ACE37 takes into account the recommendations and findings of the ACE
> >    design team to create a "super-ACE" that incorporates the key
> >    advantages of the various considered ACEs without complicated mode
> >    changes.  The encoding (Section 6) and decoding (Section 7) process
> >    is largely similar to and as simple as DUDE-02.  The encoding
> >    processes for ACE37 in comparison with DUDE-02 could be summarized:
> >
> >         ACE37 Encoding Procedure     |     DUDE Encoding Procedure
> >     ---------------------------------+---------------------------------
> >     (1) let initial prev = 0x00      | (1) let initial prev = 0x60
> >     (2) if n = LDH output "-n"       | (2) if n = hyphen output "-"
> >     (3) code block shift to obtain   | (3) diff = prev XOR n
> >           ACE37 shifted n (Section 2)| (4) prepend "0" to the last
> >     (4) diff = prev XOR n            |      quartet and "1" to others
> >     (5) output in appropriate base-4 | (5) output a base-32 character
> >           and base-32 form           |      for each corresponding
> >           (Sections 3&4)             |      quintet
> >     (6) let prev = n                 | (6) let prev = n
> >
> >    Similarly, the decoding process can be described and compared:
> >
> >         ACE37 Decoding Procedure     |     DUDE Decoding Procedure
> >     ---------------------------------+---------------------------------
> >     (1) let initial prev = 0x00      | (1) let initial prev = 0x60
> >     (2) if char = hyphen discard "-" | (2) if char = hyphen consume
> >           and output next char       |       and output 0x002D
> >     (3) consume and convert char into| (3) consume and convert to
> >           duplets and quintets       |       quintets until encoun-
> >           (according to Sections 3&4)|       erring a quintet with "0"
> >     (4) concatenate to form diff     |       as first bit
> >           (based on Sections 4.1&4.2)| (4) strip all first bits off
> >     (5) let prev = prev XOR diff     | (5) concatente to form diff
> >     (6) reverse code block shifting  | (6) let prev = prev XOR diff
> >     (7) output Unicode code point    | (7) output Unicode code point
> >
> >    The features of ACE37 include:
> >
> >    Unique & Reversible - the ACE37 encoding scheme yields a unique and
> >    consistent result string for a given set of Unicode code points.
> >    The encoded string could be decoded back to the original Unicode
> >    code points without loss of character data.
> >
> >    Simple - ACE37 utilizes a one-pass system and the XOR differential
> >    function to encode and decode.  Code block shifting is done by a
> >    simple calculation instead of mapping or creation of arbitrary
> >    reference points. Complex mode changes are not required.
> >
> >    Spacious - With the code block shifting coupled with a base-32
> >    scheme, ACE37 can accommodate up to 21 unique Han characters
> >    (including CJK) within the 63 octets allowed by the DNS.  Other
> >    Latin based scripts can reach up to 31 characters.
> >Chung & Leung                                                  [Page 3]
> >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> >
> >
> >    Completeness - any sequence of Unicode code points
> >    (U+0000..U+10FFFF) could be encoded.  Restrictions of allowed code
> >    points is not discussed, but is expected that Nameprep [Nameprep]
> >    will be used prior to ACE37 encoding.
> >
> >    In essence, it captures the focus criterions discussed by the
> >    workgroup ACE design team - reversibility, simplicity and
> >    compression capability.  Moreover, ACE37 utilizes a very simple code
> >    block shifting (Section 2) mechanism to allow up to any 21 CJK
> >    ideographs to be encoded within the 63-octet constraint.
> >
> >2. Code Block Shifting
> >
> >    While the DNS was not originally designed for multilingual
> >    characters, Unicode was not designed with the DNS in mind and
> >    therefore code points were apparently not allocated in an ACE-
> >    friendly way.
> >
> >    The AMC series [AMC-W & AMC-V] utilizes a number of reference points
> >    to achieve better compression efficiency by anticipating and
> >    minimizing delta between characters.  For ACE37, a much simpler
> >    rendering is used.  More specifically, the entire character block
> >    U+3000..U+9FFF for CJK ideographs is shifted down by 0x3000.  That
> >    is U+3000 will become 0x0000, U+4000 becomes 0x1000, and so on.  To
> >    compensate for the downwards shift, the general script and symbol
> >    characters in U+0000..U+2FFF will be shifted upwards by 0x7000.
> >    Therefore, U+0100 will become 0x7100, U+2000 becomes 0x9000, and so
> >    on.  All other code points (U+A000..U+10FFFF) are unchanged.
> >
> >       Original Unicode Allocation   |     ACE37 Code Block Shifted
> >     --------------------------------|-------------------------------
> >       General Scripts  U+0000 -+    |     +- 0x0000 CJK Misc
> >                        U+1000  |    |     |  0x1000 CJK Ideographs
> >                                +-   |  -> |  0x2000
> >       Symbols          U+2000 -+ \  | /   |  0x3000
> >                                   \ |/    |  0x4000
> >       CJK Misc         U+3000 -+   \/     |  0x5000
> >       CJK Ideographs   U+4000  |   /\     +- 0x6000
> >                        U+5000  |  / |\
> >                        U+6000  +--  | \   +- 0x7000 General Scripts
> >                        U+7000  |    |  -> |  0x8000
> >                        U+8000  |    |     |
> >                        U+9000 -+    |     +- 0x9000 Symbols
> >                                     |
> >       Hangul           U+A000 -+    |     +- 0xA000 Hangul
> >                        U+B000  |    |     |  0xB000
> >                        U+C000  +----|---> |  0xC000
> >                        U+D000  |    |     |  0xD000
> >         :                 :   -+    |     +-    :      :
> >                                     |
> >
> >
> >Chung & Leung                                                  [Page 4]
> >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> >
> >    This shifting effectively moves the entire Han library to within
> >    0x6FFF and therefore could be represented in 15-bits or exactly 3
> >    base-32 characters.  (details on base-32 characters in Section 3)
> >
> >    For example, the Chinese character for <change> with the original
> >    Unicode code point at U+8F49, will be shifted to 0x5F49 and can be
> >    represented in 3 quintets, and in turn with 3 base-32 characters:
> >
> >                     Character: <change>
> >            Unicode Code Point: U+8F49
> >                 ACE37 Shifted: 0x5F49
> >        Corresponding Quartets: 0101 1111 0100 1001
> >            Resulting Quintets: 10111 11010 01001
> >                       Base-32: nq9   (further discussed in Section 3)
> >
> >    This in turn means that any Chinese character could be represented
> >    with 3 base-32 characters making the total possible characters
> >    within a label, even without further compression introduced by the
> >    XOR differential process (Section 6), to be at least 21.  The ACE37
> >    code block shifting process could be described as follows:
> >
> >       for each input code point = n
> >       if n <= 9FFF
> >          n = n - 0x3000      /*downwards shifting*/
> >          if n <= 0
> >             n = 0x9FFF + n   /*compensation for U+0000..U+2FFF*/
> >
> >    The character block shifting introduced here is extremely simple and
> >    utilizes simple calculation that requires no mapping function.  At
> >    the same time, it achieves the goal in adjusting the Unicode
> >    allocation so that it becomes more ACE friendly.
> >
> >3. Base-32 Characters
> >
> >    Base-32 characters are used in LACE for compression, while DUDE-02
> >    and the AMC series only utilizes it for quartet flagging to indicate
> >    the last quartet of each encoded code point.  ACE37 utilizes base-32
> >    characters for compression while base-4 characters, which will be
> >    introduced in Section 4, determine the compressed code point
> >    brackets.
> >
> >    The following table shows the 32 base-32 characters and their
> >    corresponding quintets:
> >
> >    Base-32 Character =to= Corresponding Quintet
> >        0 = 00000       8 = 01000       g = 10000       o = 11000
> >        1 = 00001       9 = 01001       h = 10001       p = 11001
> >        2 = 00010       a = 01010       i = 10010       q = 11010
> >        3 = 00011       b = 01011       j = 10011       r = 11011
> >        4 = 00100       c = 01100       k = 10100       s = 11100
> >        5 = 00101       d = 01101       l = 10101       t = 11101
> >        6 = 00110       e = 01110       m = 10110       u = 11110
> >        7 = 00111       f = 01111       n = 10111       v = 11111
> >Chung & Leung                                                  [Page 5]
> >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> >
> >
> >    With this layout of base-32 characters, it is also possible to
> >    implement a computation based base-32 conversion instead of having
> >    to resort to mapping and lookup tables:
> >
> >       For each quintet = q
> >           if q <= 0x0F
> >              then hex dump q to form base-32 character
> >           if 0x10 <= q <= 0x1F
> >              then q = q - 0x10
> >                 and char(q + 0x67) to form base-32 character
> >
> >    Note that 0x67 is the code value for the letter "g".  Therefore, for
> >    example if the quintet is 0b10001 its base-32 character can be
> >    obtained by:
> >
> >       0x10 <= q=0b10001=0x11 <= 0x1F
> >       therefore q = q - 0x10 = 0x11 - 0x10 = 0x01
> >             and base-32 character = char(0x01 + 0x67)
> >                 char(0x68) = "h"
> >
> >4. Base-4 Characters
> >
> >    ACE37 goes beyond the 32 characters (base-32) to include the
> >    remaining 4 characters {w,x,y,z} in the alphabet.  These base-4
> >    characters enable ACE37 to better utilize the existing "resources"
> >    (the allowed characters) to represent IDN character information,
> >    therefore making it's encoding more efficient.
> >
> >    The set of base-4 characters are {w,x,y,z} and will be used to
> >    represent the following duplets (duplets are groups containing 2
> >    bits):
> >
> >    Base-4 Character =to= Corresponding Duplet
> >                   w   =  00
> >                   x   =  01
> >                   y   =  10
> >                   z   =  11
> >
> >4.1 Base-4 Indicators
> >
> >    Base-4 characters while carrying character information, also doubles
> >    as an indicator for code point brackets.  In DUDE-02, an extra bit
> >    was pre-pended to each quartet.  The last quartet of each encoded
> >    code point will be pre-pended with "0", marking the end of the code
> >    point.  In ACE37, base-4 characters will determine the length
> >    (number of ACE37 characters) of the encoded code point.  Actually,
> >    to be more precise, the encoded bits are in fact the "diff" and not
> >    the code point itself (diff carries the same meaning as in DUDE-02
> >    and is further discussed in Sections 6 & 7)
> >
> >
> >
> >Chung & Leung                                                  [Page 6]
> >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> >
> >    The following table explains how base-4 characters are combined with
> >    base-32 characters to form a representation of a diff (key: b4=base-
> >    4, b32=base-32):
> >
> >              diff value         |bits|       ACE37 Form
> >        -------------------------|----|----------------------------
> >                  diff<=0x7F     |  7 | <b4><b32>
> >            0x80<=diff<=0x7FFF   | 15 | <b32><b32><b32>
> >          0x8000<=diff<=0x1FFFF  | 17 | w<b4><b32><b32><b32>
> >         0x20000<=diff<=0xFFFFF  | 20 | ww<b32><b32><b32><b32>
> >        0x100000<=diff<=0x10FFFF | 22 | <b4>w<b32><b32><b32><b32>
> >
> >    Note that the "bits" column represents the maximum number of
> >    significant bits for the given diff value.  For example when
> >    diff<=0x7F, the maximum value is 0b1111111, therefore the number of
> >    significant bits is 7.
> >
> >    Note also that to encode a 17-bit diff, the letter "w" is used as an
> >    indicator to distinguish the sequence from the 7 bit diff where a
> >    base-32 character is expected to follow a base-4 character.  Since
> >    "w" represents "00" that has no value, it will not be used in the
> >    base-4 representation for a 17-bit diff (if a "00" is used, it means
> >    that there are only 15 significant bits and therefore should use the
> >    15 bit diff form).  This is the case for the 20-bit form as well.
> >    The "w" is used as an arbitrary indicator in the 22-bit form and
> >    MUST be discarded during decoding.
> >
> >    By analyzing the ACE37 form, an encoded string could be successfully
> >    returned to its original form.  There is no overlap and the form can
> >    be determined precisely.  The following 5 rules dictate the 5
> >    different ACE37 forms:
> >
> >    (1) Encode: if diff<=0x7F
> >        Decode: if first character is <b4> AND next character NOT <b4>
> >                Then it MUST be in 7-bit form: <b4><b32>
> >
> >    (2) Encode: if 0x80<=diff<=0x7FFF
> >        Decode: if first character is <b32>
> >                Then it MUST be a 15-bit form: <b32><b32><b32>
> >
> >    (3) Encode: if 0x8000<=diff<=0x1FFFF
> >        Decode: if first character is "w" AND next character is <b4>
> >                   AND NOT "w"
> >                Then it MUST be in 17-bit form: w<b4><b32><b32><b32>
> >
> >    (4) Encode: if 0x20000<=diff<=0xFFFFF
> >        Decode: if first character is "w" AND next character is "w"
> >                Then it MUST be in 20-bit form: ww<b32><b32><b32><b32>
> >
> >    (5) Encode: if 0x80<=diff<=0x7FFF
> >        Decode: if first character is <b4> AND NOT "w"
> >                   AND next character is "w"
> >                Then it MUST be 22-bit form: <b4>w<b32><b32><b32><b32>
> >Chung & Leung                                                  [Page 7]
> >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> >
> >
> >    Note that the ACE37 scheme can effectively encode a diff of up to 22
> >    significant bits or 0x3FFFFF.  The Unicode code points are expected
> >    to range only between 0x0000..0x10FFFF, therefore ACE37 will be able
> >    to handle any Unicode code point.
> >
> >    Additionally, base-4 characters (and sometimes base-32 characters)
> >    could be used for mixed-case annotation.  This optional mixed-case
> >    annotation mechanism is discussed in Appendix B.
> >
> >4.2 First Code Point Considerations
> >
> >    There are additional considerations for the first code point that is
> >    encoded or decoded to ensure that if the first code point is within
> >    the first Unicode plane (U+0000..U+FFFF), it will not occupy more
> >    than 4 ACE37 characters.
> >
> >    This special consideration affects only Rules (1), (3) and (4)
> >    explained in Section 4.1.  Rule (1) is discarded for the first code
> >    point, therefore any diff under 0x7FFF will be in the form
> >    <b32><b32><b32>.  The form for Rule (3) becomes simply
> >    <b4><b32><b32><b32> without the "w" indicator.  Similarly, the form
> >    for Rule (4) becomes w<b32><b32><b32><b32> with one less "w".
> >
> >    The first code point considerations can be summarized in the
> >    following 4 rules:
> >
> >    (a) Encode: if diff<=0x7FFF
> >        Decode: if first character is <b32>
> >                Then it MUST be in 15-bit form: <b32><b32><b32>
> >
> >    (b) Encode: if 0x8000<=diff<=0x1FFFF
> >        Decode: if first character is <b4> AND NOT "w"
> >                Then it MUST be in 17-bit form: <b4><b32><b32><b32>
> >
> >    (c) Encode: if 0x20000<=diff<=0xFFFFF
> >        Decode: if first character is "w"
> >                Then it MUST be in 20-bit form: w<b32><b32><b32><b32>
> >
> >    (d) Encode & Decode: same as Rule (5) in Section 4.1
> >
> >    Besides special considerations for base-4 character usage, prev
> >    setting is also specially considered for the first code point.  As
> >    laid out in Section 6, in order to detect for the first code point,
> >    the prev is evaluated.  If prev = 0x00, it is assumed that it is the
> >    first code point as 0x00 SHOULD not be a permitted character for
> >    input.  When an LDH is the first code point, there is a need to make
> >    a special consideration.  Regularly, if n = LDH is encountered
> >    (Section 5), it will be output as "-n" and prev is not changed.
> >    However, if the first code point is an LDH, after outputting "-n",
> >    prev is updated to = lowercase(n).  This is to ensure and maintain
> >    that only the first code point coming in will have a prev = 0x00.
> >
> >Chung & Leung                                                  [Page 8]
> >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> >
> >5. LDH Considerations
> >
> >    Finally, the 37th character of the entire LDH repertoire, the hyphen
> >    will be used to indicate LDH exceptions.  Extending the hyphen
> >    consideration of DUDE-02, ACE37 gives special consideration for the
> >    entire LDH repertoire.  All LDH characters will be encoded "as is"
> >    with the addition of a leading hyphen.  For example, the character
> >    "a" will be encoded within ACE37 as "-a".  The hyphen character "-"
> >    will be encoded as "--".
> >
> >    This ensures that each LDH character will only take up 2 character
> >    spaces within an ACE37 encoded string and also will allow
> >    administrators to see the actual characters, similar to the AMC
> >    series.  Unlike the AMC series however, the hyphen is not used to
> >    indicate an ongoing mode change, but only the following character.
> >    Therefore retaining the simplicity of the DUDE-02 single-mode,
> >    single-pass philosophy.
> >
> >6. Encoding Procedure
> >
> >    Similar to DUDE, all ordering of bits and quartets is big-endian.
> >    The following describes the encoding procedure:
> >
> >    Set initial value for prev = 0x00
> >    for each input code point = n
> >       if n is an LDH {A-z, 0-9, -}
> >          output "-n"                   (Section 5: LDH Considerations)
> >          if prev = 0x00                (Section 4.2: First Code Point)
> >             let prev = lowercase(n)
> >       else perform code block shifting (Section 2: Code Block Shifting)
> >       let diff = prev XOR n            (n after code block shifting)
> >       if diff<=0x7F --------------------------------------+
> >          and if this is the first code point (Section 4.2)|
> >          then output 15-bit form: <b32><b32><b32>         |
> >          else, output 7-bit form: <b4><b32>               |
> >       if 0x80<=diff<=0x7FFF                               +-(Section 4:
> >          output 15-bit form: <b32><b32><b32>              |   Base-4
> >       if 0x8000<=diff<=0x1FFFF                            | Characters)
> >          and if this is the first code point (Section 4.2)|
> >          output 17-bit form: w<b4><b32><b32><b32>         |
> >       if 0x20000<=diff<=0xFFFFF                           |
> >          output 20-bit form: ww<b32><b32><b32><b32>       |
> >       if 0x100000<=diff<=0x10FFFF                         |
> >          output 22-bit form: <b4>w<b32><b32><b32><b32> ---+
> >       let prev = n
> >    end and obtain next n and return to: "for each input code point = n"
> >
> >    The following is a more comprehensive pseudo code:
> >
> >    let prev = 0x00
> >    for each input integer n (in order) do begin
> >       if n = "-" or "0..9" or "A..Z" or "a..z"
> >       then output "hyphen"+"char(n)"
> >Chung & Leung                                                  [Page 9]
> >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> >
> >          if prev = 0x00
> >             let prev = lowercase(n)
> >
> >       else begin
> >          if n = 0x00
> >             then error and abort
> >          if n <= 9FFF
> >          n = n - 0x30
> >             if n < 0
> >             then n = 9FFF + n
> >
> >          let diff = prev XOR n
> >
> >          if diff <= 0x7F
> >             if prev = 0x00
> >             then output with 3 base-32 characters
> >          else, output first 2 bits with a base-4 character {wxyz}
> >             and remaining 5 bits with 1 base-32 character
> >
> >          if 0x80 <= diff <= 0x7FFF
> >          then output all 15 bits with base-32 characters
> >
> >          if 0x8000 <= diff <= 0xFFFF
> >             if prev = 0x00
> >             then output first 2 bits with a base-4 {xyz} (except w)
> >             and output remaining 15 bits with base-32
> >          else, output "w"
> >             and output first 2 bits with a base-4 {xyz} (except w]
> >             and output remaining 15 bits with base-32
> >
> >          if 0x10000 <= diff <= 0x1FFFF
> >          then output "w"
> >             and output first 2 bits with a base-4 {xyz} (except w)
> >             and output remaining 15 bits with base-32
> >
> >          if 0x20000 <= diff <= 0xFFFFFF
> >          then output "w"
> >             and output all 20 bits with base-32 characters
> >
> >          if 0x100000 <= diff <= 0x10FFFF
> >          then output first 2 bits with a base-4 {xyz} (except w)
> >             and output "w"
> >             and output remaining 15 bits with base-32
> >
> >          let prev = n
> >       end
> >    end
> >
> >    Nameprep [NAMEPREP] is not discussed in this document, but is
> >    expected that it be implemented for IDN.  Hence, regardless of the
> >    code point presented, an encoder MUST not produce an incorrect
> >    output.  The encoder must fail if it encounters a negative input
> >    value.
> >Chung & Leung                                                 [Page 10]
> >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> >
> >
> >    The initial value used is 0x00 so that all domains beginning with a
> >    CJK ideograph or within row 0 (U+0000..U+0FFF) will be shorter.
> >    Note that after the code block shifting (Section 2), the entire Han
> >    library is within 0x0000..0x6FFF, while row 0 is fitted to
> >    0x7000..0x7FFF.  Therefore by using an initial value of 0x00 the
> >    diff for all Han and row 0 characters will be less than 0x7FFF.  The
> >    initial value is also used as a check point for the first code point
> >    considerations (Section 4.2).
> >
> >    Additionally, an optional mixed-case annotation mechanism is
> >    discussed in Appendix B.
> >
> >7. Decoding Procedure
> >
> >    A thorough description of the decoding rules, except for the final
> >    reversal of the code block shifting has been presented in Sections
> >    4.1 and 4.2.  The following description is a brief representation of
> >    the decoding procedure:
> >
> >    let prev = 0x00
> >    while the input string is not exhausted
> >       if present character = hyphen               (Section 5: LDH
> >          discard and output next character         Considerations)
> >       else, depending on the presented form       (Section 4)
> >          convert into duplets and quintets        (Section 4 & 3)
> >          and concatenate to form diff
> >       let prev = prev XOR diff
> >       reverse code block shifting:                (Section 2)
> >          if prev<=0x9FFF
> >             and if prev<=0x6FFF
> >                    output character = prev + 0x3000
> >             else, output character = prev - 0x7000
> >          else output character = prev
> >       output character
> >    End
> >
> >    The following is a more comprehensive pseudo code for the decoding
> >    precedure:
> >
> >    let prev = 0x00
> >    while the input string is not exhausted do begin
> >       if present character = hyphen    /*Section 5:LDH Considerations*/
> >       then consume and discard hyphen
> >          and obtain the next character
> >          and output character
> >          if prev = 0x00                /*Section 4.2:First Code Point*/
> >             let prev = code block shifted lowercase output character
> >
> >       else,
> >          if present character = Base-32 characters (0..v)
> >             consume present character and next 2 characters
> >             and convert them to quintets according to Base-32
> >Chung & Leung                                                 [Page 11]
> >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> >
> >             concatenate the resulting quintets to form diff
> >             /*15 bit form, 0x80<=diff<=0x7FFF*/
> >
> >          if present character = Base-4 characters {xyz} and NOT w
> >             consume present character
> >                and convert it to a duplet according to Base-4
> >
> >             if prev = 0x00
> >                obtain and consume next 3 characters
> >                and convert them to quintets according to Base-32
> >                concatenate duplet with the 3 quintets to form diff
> >                /*first code point: 17 bit form, 0x8000<=diff<=0x1FFFF*/
> >
> >             else, if next character = Base-32 character (0..v)
> >                then consume and convert to quintet according to Base-32
> >                concatenate duplet with the quintet to form diff
> >                /*7 bit form, diff<=0x7F*/
> >
> >             else, obtain next character
> >             if next character = Base-4 characters {xyz} and NOT w
> >                then fail and indicate error
> >
> >             else, if next character = w
> >                then consume and discard w and obtain next 4 characters
> >                consume and convert characters to
> >                   quintets according to Base-32
> >                concatenate duplet with the 4 quintets to form diff
> >                /*22 bit form, 0x100000<=diff<=0x10FFFF*/
> >
> >          if present character = w
> >             discard "w" and obtain next character
> >
> >             if next character = Base-4 characters {xyz} and NOT w
> >
> >                and if prev = 0x00
> >                    obtain and consume next 4 characters
> >                    and convert characters to quintets based on Base-32
> >                    concatenate the 4 quintets to form diff
> >                    /*first code point: 20 bit form,*/
> >                    /*0x20000<=diff<=0xFFFFFF       */
> >
> >                else, consume and convert to duplet according to Base-4
> >                   and obtain and consume next 3 characters
> >                   and convert to quintets according to Base-32
> >                   concatenate duplet with the 3 quintets to form diff
> >                   /*17 bit form, 0x8000<=diff<=0x1FFFF*/
> >
> >             else, if next character = w
> >                then consume and discard w
> >                and obtain and consume next 4 characters
> >                   and convert to quintets according to Base-32
> >                concatenate duplet the 4 quintets to form diff
> >                /*20 bit form, 0x20000<=diff<=0xFFFFFF*/
> >Chung & Leung                                                 [Page 12]
> >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> >
> >
> >             else, if next character = Base-32 character (0..v)
> >                then convert to quintet according to Base-32
> >                set quintet to diff
> >                /*7 bit form, diff<=0x7F*/
> >
> >          fail upon encountering a non-ACE37 character
> >             or end-of-input
> >
> >          let prev = prev XOR diff
> >
> >          if prev <= 0x9FFF                /*reversal of the code    */
> >             and if prev <= 6FFF           /*block shifting described*/
> >             output = prev + 0x3000        /*in Section 2            */
> >             else, output = prev - 0x7000
> >          else, output prev
> >       end
> >    end
> >    encode the output sequence and compare it to the input string
> >    fail if they do not match (case insensitively)
> >
> >8. Examples
> >
> >    ACE37 is likely to be implemented with an ACE prefix in the form
> >    "xx--".  The actual prefix to be used is not discussed in this
> >    document.  The following examples are taken from the mailing list as
> >    well as from DUDE-02 and the AMC series.  The resulting ACE37 string
> >    is compared with that using DUDE:
> >
> >    (A) JPNIC (the registry of .jp domain)
> >
> >    Unicode: U+793E U+56E3 U+6CD5 U+4EBA U+65E5 U+672C U+30CD U+30C3
> >             U+30C8 U+30EF U+30FC U+30AF U+30A4 U+30F3 U+30D5 U+30A9
> >             U+30E1 U+30FC U+30B7 U+30E7 U+30F3 U+30BB U+30F3 U+30BF
> >             U+30FC
> >      ACE37: i9urut6hm8jfaqv0m9dv1wewbx7wjyjwbynx6zsy8wtybygwky8y8ycy3
> >             (57 char)
> >    DUDE-02: (error: result string exceeds 59 characters*)
> >             Note: 59 characters is the maximum allowable when the ACE
> >             prefix "xx--" is included
> >
> >
> >    (B) A health-insurance organization in Tokyo
> >
> >    Unicode: U+6771 U+4EAC U+90FD U+60C5 U+5831 U+30B5 U+30FC U+30D3
> >             U+30B9 U+7523 U+696D U+5065 U+5EB7 U+4FDD U+967A U+7D44
> >             U+5408
> >      ACE37: drhaetvihk1o67ka44y9xfzahcqv2e6883micbaud7apuqac (48 char)
> >    DUDE-02: (error: result string exceeds 59 characters)
> >
> >
> >
> >
> >Chung & Leung                                                 [Page 13]
> >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> >
> >    (C) 6 hangul syllables
> >
> >    Unicode: U+C138 U+ACC4 U+C758 U+BAA8 U+B4E0 U+C0AC
> >      ACE37: xg9orfsqssvfg3i8t2c (19 char)
> >    DUDE-02: 6txiy79ny53nz79a8wizwwn (23 char)
> >
> >
> >    (D) maji<de>koi<suru>5<byou><mae>  (Latin, hiragana, kanji)
> >
> >    Unicode: U+006D U+0061 U+006A U+0069 U+3067 U+006B U+006F U+0069
> >             U+3059 U+308B U+0035 U+79D2 U+524D
> >      ACE37: -m-a-j-is0a-k-o-xu06i-5iapqsv (30 char)
> >    DUDE-02: pnmdvssqvssnegvsva7cvs5qz38hu53r (32 char)
> >
> >
> >    (E) <pafii>de<runba>  (Latin, katakana)
> >
> >    Unicode: U+30D1 U+30D5 U+30A3 U+30FC U+0064 U+0065 U+30EB U+30F3
> >             U+30D0
> >      ACE37: 06hw4zmyv-d-ewnwox3 (19 char)
> >    DUDE-02: vs5bezgxrvs3ibvs2qtiud (22 char)
> >
> >
> >    (F) <sono><supiido><de>  (hiragana, katakana)
> >
> >    Unicode: U+305D U+306E U+30B9 U+30D4 U+30FC U+30C9 U+3067
> >      ACE37: 02txj06nzdx8xl05e (17 char)
> >    DUDE-02: vsvpvd7hypuivf4q (16 char)
> >
> >
> >    (G) 2 Arbitrary Plane Two Code Points
> >
> >    Unicode: U+261AF U+261BF
> >      ACE37: w4odfwg (7 char)
> >    DUDE-02: uyt6rta (7 char)
> >
> >
> >    (H) Czech: Pro<ccaron>prost<ecaron>nemluv<iacute><ccaron>esky
> >
> >    Unicode: U+0050 U+0072 U+006F U+010D U+0070 U+0072 U+006F U+0073
> >             U+0074 U+011B U+006E U+0065 U+006D U+006C U+0075 U+0076
> >             U+00ED U+010D U+0065 U+0073 U+006B U+0079
> >      ACE37: -p-r-o0bt-p r-o-s-twm-n-e-m-l-u-v0fm0f0-e-s-k-y (47 char)
> >    DUDE-02: vauctptyctzpctptnhtyrtzfmibtjd3mt8atyitgtitc (44 char)
> >
> >
> >    (I) Chinese
> >
> >    Unicode: U+4ED5 U+5011 U+7232 U+4EC0 U+9EBD U+4E0D U+8AAA U+4E2D
> >             U+6587
> >      ACE37: 7mmfm7oh3n7is3ts5gh57h47ata (27 char)
> >    DUDE-02: w85gt86huuudv69c7szp7s5a6w4h6w2hu54k (36 char)
> >
> >Chung & Leung                                                 [Page 14]
> >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> >
> >9. Summary & Comparisons
> >
> >    In summary, ACE37 is based on the DUDE-02 process with an improved
> >    compression scheme for code point sequences that are less likely to
> >    cluster too closely together, such as CJK ideographs.
> >
> >    Since it is the design team's indication that generally 30
> >    characters should be good enough and that there are a lot of concern
> >    from the Asian community that 14-15 characters is definitely
> >    limiting and that few indication from the Latin community that
> >    length is really a concern, ACE37 have set its objective to increase
> >    the possible number of characters in a worse case scenario closer to
> >    20 characters.
> >
> >    ACE37 have succeeded in creating a very simple variation based on
> >    the primary ACEs identified by the design team to create an ACE that
> >    achieves dramatically better performance for CJK characters while
> >    maintaining the simplicity of DUDE.
> >
> >    Key Improvements of ACE37 over DUDE-02
> >    - much more spacious for Han characters.  Improved worst-case
> >      scenario to 21 Han ideographs by introducing code block shifting
> >      and utilizing fully base-32 characters
> >    - no need to arbitrarily pre-pend flagging bits to identify code
> >      point brackets.  Instead base-4 characters and diff forms are used
> >    - base-32 and base-4 characters can be easily computed instead of
> >      mapped using lookup tables
> >
> >    Key Improvements of ACE37 over the AMC series
> >    - a more simple process, utilizing the one-pass differential
> >      mechanism from DUDE-02
> >    - a much more simple code block shifting process is used in ACE37 to
> >      achieve a similar goal for the complex multiple reference point
> >      system used by the AMC series
> >    - base-32 and base-4 characters can be easily computed instead of
> >      mapped using lookup tables
> >
> >    Key Improvements of ACE37 over LACE
> >    - a more simple process, utilizing the one-pass differential
> >      mechanism from DUDE-02
> >    - much more spacious for Han characters.  Improved worst-case
> >      scenario to 21 Han ideographs by introducing code block shifting
> >      and utilizing fully base-32 characters
> >    - base-32 and base-4 characters can be easily computed instead of
> >      mapped using lookup tables
> >
> >    Two Excel spreadsheet for ACE37 encoding and decoding can be found
> >    at http://www.dnsii.org/ace37/ace37-encode.xls and
> >    http://www.dnsii.org/ace37/ace37-decode.xls respectively.  This
> >    illustrates the simplicity of ACE37 and provides a handy tool for
> >    checking ACE37 encoding and decoding algorithms.  The ACE37-encode
> >    spreadsheet also includes a DUDE-encode worksheet.
> >
> >Chung & Leung                                                 [Page 15]
> >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> >
> >10. Security Considerations
> >
> >    This document does not talk about DNS security issues, and it is
> >    believed that the proposal does not introduce additional security
> >    problems not already existent and/or anticipated by adding
> >    multilingual characters to DNS and/or using ACE.
> >
> >11. References
> >
> >    [AMC-W]   Adam M. Costello, "AMC-ACE-W version 0.1.0", May 31, 2001.
> >
> >    [AMC-V]   Adam M. Costello, "AMC-ACE-V version 0.1.0", May 31, 2001.
> >
> >    [DUDE-02] Mark Welter, Brian W. Spolarich & Adam M.
> >              Costello, "Differential Unicode Domain Encoding (DUDE)",
> >              June 7, 2001.
> >
> >    [LACE]    Mark Davis, IBM & Paul Hoffman, IMC & VPNC, "LACE: Length-
> >              based ASCII Compatible Encoding for IDN", January 5, 2001.
> >
> >    [Nameprep]Paul Hoffman, IMC & VPNC & Marc Blanchet, ViaGenie,
> >              "Preparation of Internationalized Host Names", February
> >              24, 2001
> >
> >Appendix A. Acknowledgements
> >
> >    The ACE37 draft is a combination of DUDE-02, the AMC series and
> >    LACE, and takes into consideration the report of the ACE design
> >    team.  The authors would therefore like to thank the authors of
> >    DUDE-02 - Mark Welter, Brian W. Spolarich & Adam M. Costello; the
> >    authors of the AMC series - Adam M.Costello; the authors of LACE -
> >    Mark Davis & Paul Hoffman; and, the ACE design team and its advisors
> >    - Adam M. Costello, Paul Hoffman, Makoto Ishisone, David Laurence,
> >    Brian Spolarich, Rick Wesson, Marc Blanchet, Patrik Faltstrom and
> >    Erik Nordmark for their inspirations.
> >
> >Appendix B. Mixed-case annotation
> >
> >    This section is taken from DUDE and modified for ACE37
> >
> >    In order to use ACE37 to represent case-insensitive Unicode strings,
> >    higher layers need to case-fold the Unicode strings prior to ACE37
> >    encoding.  The encoded string can, however, use mixed-case base-4
> >    characters as an annotation telling how to convert the folded
> >    Unicode string into a mixed-case Unicode string for display
> >    purposes.
> >
> >    Each Unicode code point (unless it is an LDH) is represented by a
> >    sequence of base-4 and base-32 characters, the first of which is
> >    mostly a base-4 character, which is always a letter {wxyz} (as
> >    opposed to a digit).  If that letter is uppercase, it is a
> >    suggestion that the Unicode character be mapped to uppercase (if
> >
> >Chung & Leung                                                 [Page 16]
> >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> >
> >    possible); if the letter is lowercase, it is a suggestion that the
> >    Unicode character be mapped to lowercase (if possible).
> >
> >    If the code point is an LDH, for example "a", it will be represented
> >    as "-a".  To mark the case for an LDH, simply set the LDH to the
> >    desired case following the "-".  Fir example if an uppercase "A" is
> >    desired, the encoded form SHOULD be "-A".
> >
> >    Note that there is a possibility that no base-4 character is present
> >    for a code point representation.  That is the case for a 15-bit diff
> >    form.  In this case, the base-32 characters will be used for case
> >    suggestion (if possible), similar to that discussed for using a
> >    base-4 character.  However, also note that there is a very remote
> >    possibility that all 3 base-32 characters are digits.  If this
> >    happens, case unfolding will be aborted.  Since case annotation is
> >    an optional feature and used for display purposes only, this is not
> >    considered to be a major concern.  Moreover, the possibility of this
> >    happening is truly remote at only (32639/27)/1114109 or just 0.1%
> >    chance of happening.
> >
> >    ACE37 encoders and decoders are not required to support these
> >    annotations, and higher layers need not use them.
> >
> >    For example:  In order to suggest that example (H) in Section 8:
> >    "Examples" be displayed as:
> >    Czech: Pro<ccaron(uppercase)>prost<ecaron(uppercase)>
> >           nemLUV<iacute(lowercase)><ccaron(lowercase)>esky
> >
> >    one could capitalize the ACE37 encoding as:
> >      ACE37: -P-r-o0BT-p-r-o-s-tWM-n-e-m-L-U-V0fm0f0-e-s-k-y (47 char)
> >
> >Authors:
> >
> >Edmon Chung
> >Neteka Inc.
> >2462 Yonge St. Toronto,
> >Ontario, Canada M4P 2H5
> >edmon@neteka.com
> >
> >David Leung
> >Neteka Inc.
> >2462 Yonge St. Toronto,
> >Ontario, Canada M4P 2H5
> >david@neteka.com
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >Chung & Leung                                                 [Page 17]
>





From owner-idn@ops.ietf.org  Thu Jul  5 14:00:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA21750
	for <idn-archive@lists.ietf.org>; Thu, 5 Jul 2001 14:00:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IDBt-000IyZ-00
	for idn-data@psg.com; Thu, 05 Jul 2001 10:45:25 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IDBs-000IyT-00
	for idn@ops.ietf.org; Thu, 05 Jul 2001 10:45:24 -0700
Received: from CLASSIC.viagenie.qc.ca (classic.viagenie.qc.ca [206.123.31.136])
	by jazz.viagenie.qc.ca (Viagenie/8.11.0) with ESMTP id f65I4k152757;
	Thu, 5 Jul 2001 14:04:46 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010705120420.01efc498@mail.viagenie.qc.ca>
X-Sender: blanchet@mail.viagenie.qc.ca
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 05 Jul 2001 12:08:02 -0400
To: "Edmon" <edmon@neteka.com>, <idn@ops.ietf.org>
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: [idn] Re: permission <draft-ietf-idn-ace37-00.txt (attach)
In-Reply-To: <006601c10569$ffa20e00$1001a8c0@neteka.com>
References: <5.1.0.14.1.20010705084656.02b0e138@mail.viagenie.qc.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

At/À 11:48 2001-07-05 -0400, Edmon you wrote/vous écriviez:
>Hi all,
>
>I was unaware that the workgroup no longer accepts new drafts.

see:

Message-Id: <5.1.0.14.1.20010626000156.03d85e50@mail.viagenie.qc.ca>
Date: Tue, 26 Jun 2001 00:05:28 -0400
To: idn@ops.ietf.org
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: [idn] wg next steps

and:

Message-Id: <5.1.0.14.1.20010629080012.02042a10@mail.viagenie.qc.ca>
Date: Fri, 29 Jun 2001 08:06:14 -0400
To: idn@ops.ietf.org
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: [idn] document pools active

And, as I wrote in the email, you are _encouraged_ to submit as individual 
submission. The only difference is filename and no listing in the ietf idn 
wg charter web page.

Marc.


>   Anyway, I
>have drafted a new ACE based on the simplicity of DUDE which has hugely
>improved compression.  Worst case scenario CJK could have 21 han characters!
>Attached below is a copy of the draft (for my original submission), you can
>also find it at http://www.dnsii.org/idn-ace37-00.txt (easier to read) and
>hopefully in the i-d-n.net website soon.
>
>ACE37 is based on the one-pass one-mode scheme of DUDE (diiferential XOR),
>then utilizes a simple code block shifting (similar to the reference points
>in the AMC series) to hugely increase the capacity for CJK (worst case
>scenario 21 han characters!) and then utilizes base-32 for compression (as
>in LACE) (DUDE and AMC-w/v uses base-32 only for flagging).  In addition to
>base-32, a base-4 scheme is introduced by using the remaining characters
>{wxyz}.  These contain 2 bits of character information and doubles as an
>indicator for codepoint brackets.  All the while, the algorithm is kept to
>be as simple as DUDE.
>
>Hopefully you might find that it is interesting and appropriate to be
>considered as an ACE within the IETF.  Afterall, it was intended to be an
>integrated version of the three primary ACEs: DUDE, LACE and the AMC series,
>identified by the ACE design team report.
>
>Looking forward to all your inputs.
>
>Edmon
>
>PS. I have created an Excel worksheet to illustrate the Encoding and
>Decoding procedures as well you can find them at
>http://www.dnsii.org/ace37/ace37-encode.xls and
>http://www.dnsii.org/ace37/ace37-decode.xls respectively.
>
>
>
>----- Original Message -----
>From: "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>
>To: "Natalia Syracuse" <nsyracus@ietf.org>; <edmon@neteka.com>;
><david@neteka.com>
>Cc: <jseng@pobox.org.sg>
>Sent: Thursday, July 05, 2001 8:50 AM
>Subject: Re: permission <draft-ietf-idn-ace37-00.txt (attach)
>
>
> > I'm sorry but the new wg policy is to not accept draft unless there is a
> > demonstrated support. But drafts are _highly_ encouraged to be published
>as
> > individual submissions. I would recommend to put idn in the filename and
> > use this filenaming convention: draft-<yourname>-idn-ace37-00.txt. After
> > publication in the internet-draft, the author should announce it in the wg
> > mailing list and I'll put a reference to it in the wg web page.
> >
> > So please publish it as individual submission.
> >
> > Marc.
> >
> > At/À 08:34 2001-07-05 -0400, Natalia Syracuse you wrote/vous écriviez:
> > >
> > >
> > >
> > >Internet Draft                                 Edmon Chung, Neteka Inc.
> > ><draft-ietf-idn-ace37-00.txt>                  David Leung, Neteka Inc.
> > >                                                               June 2001
> > >
> > >
> > >
> > >           ACE Utilizing All 37 Alphanumeric Characters (ACE37)
> > >
> > >
> > >STATUS OF THIS MEMO
> > >
> > >    This document is an Internet-Draft and is in full conformance with
> > >    all provisions of Section 10 of RFC2026.
> > >
> > >    Internet-Drafts are working documents of the Internet Engineering
> > >    Task Force (IETF), its areas, and its working groups.  Note that
> > >    other groups may also distribute working documents as Internet-
> > >    Drafts.  Internet-Drafts are draft documents valid for a maximum of
> > >    six months and may be updated, replaced, or obsoleted by other
> > >    documents at any time.  It is inappropriate to use Internet-Drafts
> > >    as reference material or to cite them other than as "work in
> > >    progress."
> > >
> > >    The reader is cautioned not to depend on the values that appear in
> > >    examples to be current or complete, since their purpose is primarily
> > >    educational.  Distribution of this memo is unlimited.
> > >
> > >    The list of current Internet-Drafts can be accessed at
> > >    http://www.ietf.org/ietf/1id-abstracts.txt
> > >    The list of Internet-Draft Shadow Directories can be accessed at
> > >    http://www.ietf.org/shadow.html.
> > >
> > >Abstract
> > >
> > >    ACE37 is a combination of DUDE-02, AMC-W/V and LACE.  ACE37 utilizes
> > >    the simple one pass algorithm of DUDE, the character block
> > >    considerations of AMC-W/V and the Base-32 compression of LACE.  It
> > >    also fully utilizes entire LDH set currently allowed in the DNS (A-
> > >    z, 0-9 and "-") within its character repertoire to optimize
> > >    performance and compression.  Even for the worst-case scenario in
> > >    ACE37, any name can have 21 characters including Chinese, Japanese
> > >    and Korean names. Two Excel spreadsheets for ACE37 encoding and
> > >    decoding can be found at http://www.dnsii.org/ace37/ace37-encode.xls
> > >    and http://www.dnsii.org/ace37/ace37-decode.xls respectively.
> > >
> > >    While DUDE-02 provides a very efficient differential mechanism, its
> > >    compression is inefficient as it fails to take advantage of the
> > >    base-32 scheme in using all 5-bits for character information.  The
> > >    AMC series is highly efficient in compression but requires
> > >    complicated mode changes and therefore inefficient in process.  LACE
> > >    is rather moderate and requires a two-pass mechanism but utilizes
> > >    base-32 for good compression.
> > >
> > >
> > >Chung & Leung                                                  [Page 1]
> > >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> > >
> > >    ACE37 uses simple character block shifting to achieve the
> > >    compression efficiency of the AMC series, retains the one-pass and
> > >    one mode XOR differential mechanism used by DUDE while embracing the
> > >    base-32 compression used by LACE for efficient character bit
> > >    information.
> > >
> > >Terminology
> > >
> > >    The key words "MUST", "SHALL", "REQUIRED", "SHOULD", "RECOMMENDED",
> > >    and "MAY" in this document are to be interpreted as described in RFC
> > >    2119 [RFC2119].
> > >
> > >    LDH: Letters, Digits and Hyphens: a string of characters that
> > >    consists only hyphens ("-"), English letters (A-z) and digits (0-9),
> > >    which might not be a result of an algorithm for transcoding
> > >    multilingual characters. For example: whatever-you-want.example
> > >
> > >    ACE - ASCII Compatible Encoding: a string of characters resulting
> > >    from a particular algorithm for transforming multilingual character
> > >    information into an alphanumeric form acceptable by the existing
> > >    DNS.  For example: bq--3bhc2zmh.tld.  In essence, ACE is a subset of
> > >    LDH.
> > >
> > >    Hexadecimal values are shown preceeded by "0x".  For example, 0x60
> > >    is decimal 96.  Binary values are shown preceeded by "0b" for
> > >    example "0b1000" is decimal 8.  As in the Unicode Standard
> > >    [UNICODE], Unicode code points are denoted by "U+" followed by four
> > >    to six hexadecimal digits, while a range of code points (or
> > >    hexadecimal numbers) is denoted by two hexadecimal numbers separated
> > >    by "..", with no prefixes.
> > >
> > >    Octets: sequences of 8 bits; Quintets: sequences of 5 bits;
> > >    Quartets: sequences of 4 bits; Duplets: sequences of 2 bits.
> > >
> > >    XOR: bitwise exclusive or.  Given 2 nonnegative integers A and B, A
> > >    XOR B is the nonnegative integer value whose binary representation
> > >    is 1 wherever A and B disagrees, and 0 wherever they agree.
> > >
> > >Table Of Contents
> > >
> > >    1. Introduction....................................................3
> > >    2. Code Block Shifting.............................................4
> > >    3. Base-32 Characters..............................................5
> > >    4. Base-4 Characters...............................................6
> > >
> > >    5. LDH Considerations..............................................9
> > >    6. Encoding Procedure..............................................9
> > >    7. Decoding Procedure.............................................11
> > >    8. Examples.......................................................13
> > >    9. Summary & Comparisons..........................................15
> > >    10. Security Considerations.......................................16
> > >    11. References....................................................16
> > >
> > >Chung & Leung                                                  [Page 2]
> > >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> > >
> > >1. Introduction
> > >
> > >    ACE37 takes into account the recommendations and findings of the ACE
> > >    design team to create a "super-ACE" that incorporates the key
> > >    advantages of the various considered ACEs without complicated mode
> > >    changes.  The encoding (Section 6) and decoding (Section 7) process
> > >    is largely similar to and as simple as DUDE-02.  The encoding
> > >    processes for ACE37 in comparison with DUDE-02 could be summarized:
> > >
> > >         ACE37 Encoding Procedure     |     DUDE Encoding Procedure
> > >     ---------------------------------+---------------------------------
> > >     (1) let initial prev = 0x00      | (1) let initial prev = 0x60
> > >     (2) if n = LDH output "-n"       | (2) if n = hyphen output "-"
> > >     (3) code block shift to obtain   | (3) diff = prev XOR n
> > >           ACE37 shifted n (Section 2)| (4) prepend "0" to the last
> > >     (4) diff = prev XOR n            |      quartet and "1" to others
> > >     (5) output in appropriate base-4 | (5) output a base-32 character
> > >           and base-32 form           |      for each corresponding
> > >           (Sections 3&4)             |      quintet
> > >     (6) let prev = n                 | (6) let prev = n
> > >
> > >    Similarly, the decoding process can be described and compared:
> > >
> > >         ACE37 Decoding Procedure     |     DUDE Decoding Procedure
> > >     ---------------------------------+---------------------------------
> > >     (1) let initial prev = 0x00      | (1) let initial prev = 0x60
> > >     (2) if char = hyphen discard "-" | (2) if char = hyphen consume
> > >           and output next char       |       and output 0x002D
> > >     (3) consume and convert char into| (3) consume and convert to
> > >           duplets and quintets       |       quintets until encoun-
> > >           (according to Sections 3&4)|       erring a quintet with "0"
> > >     (4) concatenate to form diff     |       as first bit
> > >           (based on Sections 4.1&4.2)| (4) strip all first bits off
> > >     (5) let prev = prev XOR diff     | (5) concatente to form diff
> > >     (6) reverse code block shifting  | (6) let prev = prev XOR diff
> > >     (7) output Unicode code point    | (7) output Unicode code point
> > >
> > >    The features of ACE37 include:
> > >
> > >    Unique & Reversible - the ACE37 encoding scheme yields a unique and
> > >    consistent result string for a given set of Unicode code points.
> > >    The encoded string could be decoded back to the original Unicode
> > >    code points without loss of character data.
> > >
> > >    Simple - ACE37 utilizes a one-pass system and the XOR differential
> > >    function to encode and decode.  Code block shifting is done by a
> > >    simple calculation instead of mapping or creation of arbitrary
> > >    reference points. Complex mode changes are not required.
> > >
> > >    Spacious - With the code block shifting coupled with a base-32
> > >    scheme, ACE37 can accommodate up to 21 unique Han characters
> > >    (including CJK) within the 63 octets allowed by the DNS.  Other
> > >    Latin based scripts can reach up to 31 characters.
> > >Chung & Leung                                                  [Page 3]
> > >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> > >
> > >
> > >    Completeness - any sequence of Unicode code points
> > >    (U+0000..U+10FFFF) could be encoded.  Restrictions of allowed code
> > >    points is not discussed, but is expected that Nameprep [Nameprep]
> > >    will be used prior to ACE37 encoding.
> > >
> > >    In essence, it captures the focus criterions discussed by the
> > >    workgroup ACE design team - reversibility, simplicity and
> > >    compression capability.  Moreover, ACE37 utilizes a very simple code
> > >    block shifting (Section 2) mechanism to allow up to any 21 CJK
> > >    ideographs to be encoded within the 63-octet constraint.
> > >
> > >2. Code Block Shifting
> > >
> > >    While the DNS was not originally designed for multilingual
> > >    characters, Unicode was not designed with the DNS in mind and
> > >    therefore code points were apparently not allocated in an ACE-
> > >    friendly way.
> > >
> > >    The AMC series [AMC-W & AMC-V] utilizes a number of reference points
> > >    to achieve better compression efficiency by anticipating and
> > >    minimizing delta between characters.  For ACE37, a much simpler
> > >    rendering is used.  More specifically, the entire character block
> > >    U+3000..U+9FFF for CJK ideographs is shifted down by 0x3000.  That
> > >    is U+3000 will become 0x0000, U+4000 becomes 0x1000, and so on.  To
> > >    compensate for the downwards shift, the general script and symbol
> > >    characters in U+0000..U+2FFF will be shifted upwards by 0x7000.
> > >    Therefore, U+0100 will become 0x7100, U+2000 becomes 0x9000, and so
> > >    on.  All other code points (U+A000..U+10FFFF) are unchanged.
> > >
> > >       Original Unicode Allocation   |     ACE37 Code Block Shifted
> > >     --------------------------------|-------------------------------
> > >       General Scripts  U+0000 -+    |     +- 0x0000 CJK Misc
> > >                        U+1000  |    |     |  0x1000 CJK Ideographs
> > >                                +-   |  -> |  0x2000
> > >       Symbols          U+2000 -+ \  | /   |  0x3000
> > >                                   \ |/    |  0x4000
> > >       CJK Misc         U+3000 -+   \/     |  0x5000
> > >       CJK Ideographs   U+4000  |   /\     +- 0x6000
> > >                        U+5000  |  / |\
> > >                        U+6000  +--  | \   +- 0x7000 General Scripts
> > >                        U+7000  |    |  -> |  0x8000
> > >                        U+8000  |    |     |
> > >                        U+9000 -+    |     +- 0x9000 Symbols
> > >                                     |
> > >       Hangul           U+A000 -+    |     +- 0xA000 Hangul
> > >                        U+B000  |    |     |  0xB000
> > >                        U+C000  +----|---> |  0xC000
> > >                        U+D000  |    |     |  0xD000
> > >         :                 :   -+    |     +-    :      :
> > >                                     |
> > >
> > >
> > >Chung & Leung                                                  [Page 4]
> > >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> > >
> > >    This shifting effectively moves the entire Han library to within
> > >    0x6FFF and therefore could be represented in 15-bits or exactly 3
> > >    base-32 characters.  (details on base-32 characters in Section 3)
> > >
> > >    For example, the Chinese character for <change> with the original
> > >    Unicode code point at U+8F49, will be shifted to 0x5F49 and can be
> > >    represented in 3 quintets, and in turn with 3 base-32 characters:
> > >
> > >                     Character: <change>
> > >            Unicode Code Point: U+8F49
> > >                 ACE37 Shifted: 0x5F49
> > >        Corresponding Quartets: 0101 1111 0100 1001
> > >            Resulting Quintets: 10111 11010 01001
> > >                       Base-32: nq9   (further discussed in Section 3)
> > >
> > >    This in turn means that any Chinese character could be represented
> > >    with 3 base-32 characters making the total possible characters
> > >    within a label, even without further compression introduced by the
> > >    XOR differential process (Section 6), to be at least 21.  The ACE37
> > >    code block shifting process could be described as follows:
> > >
> > >       for each input code point = n
> > >       if n <= 9FFF
> > >          n = n - 0x3000      /*downwards shifting*/
> > >          if n <= 0
> > >             n = 0x9FFF + n   /*compensation for U+0000..U+2FFF*/
> > >
> > >    The character block shifting introduced here is extremely simple and
> > >    utilizes simple calculation that requires no mapping function.  At
> > >    the same time, it achieves the goal in adjusting the Unicode
> > >    allocation so that it becomes more ACE friendly.
> > >
> > >3. Base-32 Characters
> > >
> > >    Base-32 characters are used in LACE for compression, while DUDE-02
> > >    and the AMC series only utilizes it for quartet flagging to indicate
> > >    the last quartet of each encoded code point.  ACE37 utilizes base-32
> > >    characters for compression while base-4 characters, which will be
> > >    introduced in Section 4, determine the compressed code point
> > >    brackets.
> > >
> > >    The following table shows the 32 base-32 characters and their
> > >    corresponding quintets:
> > >
> > >    Base-32 Character =to= Corresponding Quintet
> > >        0 = 00000       8 = 01000       g = 10000       o = 11000
> > >        1 = 00001       9 = 01001       h = 10001       p = 11001
> > >        2 = 00010       a = 01010       i = 10010       q = 11010
> > >        3 = 00011       b = 01011       j = 10011       r = 11011
> > >        4 = 00100       c = 01100       k = 10100       s = 11100
> > >        5 = 00101       d = 01101       l = 10101       t = 11101
> > >        6 = 00110       e = 01110       m = 10110       u = 11110
> > >        7 = 00111       f = 01111       n = 10111       v = 11111
> > >Chung & Leung                                                  [Page 5]
> > >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> > >
> > >
> > >    With this layout of base-32 characters, it is also possible to
> > >    implement a computation based base-32 conversion instead of having
> > >    to resort to mapping and lookup tables:
> > >
> > >       For each quintet = q
> > >           if q <= 0x0F
> > >              then hex dump q to form base-32 character
> > >           if 0x10 <= q <= 0x1F
> > >              then q = q - 0x10
> > >                 and char(q + 0x67) to form base-32 character
> > >
> > >    Note that 0x67 is the code value for the letter "g".  Therefore, for
> > >    example if the quintet is 0b10001 its base-32 character can be
> > >    obtained by:
> > >
> > >       0x10 <= q=0b10001=0x11 <= 0x1F
> > >       therefore q = q - 0x10 = 0x11 - 0x10 = 0x01
> > >             and base-32 character = char(0x01 + 0x67)
> > >                 char(0x68) = "h"
> > >
> > >4. Base-4 Characters
> > >
> > >    ACE37 goes beyond the 32 characters (base-32) to include the
> > >    remaining 4 characters {w,x,y,z} in the alphabet.  These base-4
> > >    characters enable ACE37 to better utilize the existing "resources"
> > >    (the allowed characters) to represent IDN character information,
> > >    therefore making it's encoding more efficient.
> > >
> > >    The set of base-4 characters are {w,x,y,z} and will be used to
> > >    represent the following duplets (duplets are groups containing 2
> > >    bits):
> > >
> > >    Base-4 Character =to= Corresponding Duplet
> > >                   w   =  00
> > >                   x   =  01
> > >                   y   =  10
> > >                   z   =  11
> > >
> > >4.1 Base-4 Indicators
> > >
> > >    Base-4 characters while carrying character information, also doubles
> > >    as an indicator for code point brackets.  In DUDE-02, an extra bit
> > >    was pre-pended to each quartet.  The last quartet of each encoded
> > >    code point will be pre-pended with "0", marking the end of the code
> > >    point.  In ACE37, base-4 characters will determine the length
> > >    (number of ACE37 characters) of the encoded code point.  Actually,
> > >    to be more precise, the encoded bits are in fact the "diff" and not
> > >    the code point itself (diff carries the same meaning as in DUDE-02
> > >    and is further discussed in Sections 6 & 7)
> > >
> > >
> > >
> > >Chung & Leung                                                  [Page 6]
> > >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> > >
> > >    The following table explains how base-4 characters are combined with
> > >    base-32 characters to form a representation of a diff (key: b4=base-
> > >    4, b32=base-32):
> > >
> > >              diff value         |bits|       ACE37 Form
> > >        -------------------------|----|----------------------------
> > >                  diff<=0x7F     |  7 | <b4><b32>
> > >            0x80<=diff<=0x7FFF   | 15 | <b32><b32><b32>
> > >          0x8000<=diff<=0x1FFFF  | 17 | w<b4><b32><b32><b32>
> > >         0x20000<=diff<=0xFFFFF  | 20 | ww<b32><b32><b32><b32>
> > >        0x100000<=diff<=0x10FFFF | 22 | <b4>w<b32><b32><b32><b32>
> > >
> > >    Note that the "bits" column represents the maximum number of
> > >    significant bits for the given diff value.  For example when
> > >    diff<=0x7F, the maximum value is 0b1111111, therefore the number of
> > >    significant bits is 7.
> > >
> > >    Note also that to encode a 17-bit diff, the letter "w" is used as an
> > >    indicator to distinguish the sequence from the 7 bit diff where a
> > >    base-32 character is expected to follow a base-4 character.  Since
> > >    "w" represents "00" that has no value, it will not be used in the
> > >    base-4 representation for a 17-bit diff (if a "00" is used, it means
> > >    that there are only 15 significant bits and therefore should use the
> > >    15 bit diff form).  This is the case for the 20-bit form as well.
> > >    The "w" is used as an arbitrary indicator in the 22-bit form and
> > >    MUST be discarded during decoding.
> > >
> > >    By analyzing the ACE37 form, an encoded string could be successfully
> > >    returned to its original form.  There is no overlap and the form can
> > >    be determined precisely.  The following 5 rules dictate the 5
> > >    different ACE37 forms:
> > >
> > >    (1) Encode: if diff<=0x7F
> > >        Decode: if first character is <b4> AND next character NOT <b4>
> > >                Then it MUST be in 7-bit form: <b4><b32>
> > >
> > >    (2) Encode: if 0x80<=diff<=0x7FFF
> > >        Decode: if first character is <b32>
> > >                Then it MUST be a 15-bit form: <b32><b32><b32>
> > >
> > >    (3) Encode: if 0x8000<=diff<=0x1FFFF
> > >        Decode: if first character is "w" AND next character is <b4>
> > >                   AND NOT "w"
> > >                Then it MUST be in 17-bit form: w<b4><b32><b32><b32>
> > >
> > >    (4) Encode: if 0x20000<=diff<=0xFFFFF
> > >        Decode: if first character is "w" AND next character is "w"
> > >                Then it MUST be in 20-bit form: ww<b32><b32><b32><b32>
> > >
> > >    (5) Encode: if 0x80<=diff<=0x7FFF
> > >        Decode: if first character is <b4> AND NOT "w"
> > >                   AND next character is "w"
> > >                Then it MUST be 22-bit form: <b4>w<b32><b32><b32><b32>
> > >Chung & Leung                                                  [Page 7]
> > >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> > >
> > >
> > >    Note that the ACE37 scheme can effectively encode a diff of up to 22
> > >    significant bits or 0x3FFFFF.  The Unicode code points are expected
> > >    to range only between 0x0000..0x10FFFF, therefore ACE37 will be able
> > >    to handle any Unicode code point.
> > >
> > >    Additionally, base-4 characters (and sometimes base-32 characters)
> > >    could be used for mixed-case annotation.  This optional mixed-case
> > >    annotation mechanism is discussed in Appendix B.
> > >
> > >4.2 First Code Point Considerations
> > >
> > >    There are additional considerations for the first code point that is
> > >    encoded or decoded to ensure that if the first code point is within
> > >    the first Unicode plane (U+0000..U+FFFF), it will not occupy more
> > >    than 4 ACE37 characters.
> > >
> > >    This special consideration affects only Rules (1), (3) and (4)
> > >    explained in Section 4.1.  Rule (1) is discarded for the first code
> > >    point, therefore any diff under 0x7FFF will be in the form
> > >    <b32><b32><b32>.  The form for Rule (3) becomes simply
> > >    <b4><b32><b32><b32> without the "w" indicator.  Similarly, the form
> > >    for Rule (4) becomes w<b32><b32><b32><b32> with one less "w".
> > >
> > >    The first code point considerations can be summarized in the
> > >    following 4 rules:
> > >
> > >    (a) Encode: if diff<=0x7FFF
> > >        Decode: if first character is <b32>
> > >                Then it MUST be in 15-bit form: <b32><b32><b32>
> > >
> > >    (b) Encode: if 0x8000<=diff<=0x1FFFF
> > >        Decode: if first character is <b4> AND NOT "w"
> > >                Then it MUST be in 17-bit form: <b4><b32><b32><b32>
> > >
> > >    (c) Encode: if 0x20000<=diff<=0xFFFFF
> > >        Decode: if first character is "w"
> > >                Then it MUST be in 20-bit form: w<b32><b32><b32><b32>
> > >
> > >    (d) Encode & Decode: same as Rule (5) in Section 4.1
> > >
> > >    Besides special considerations for base-4 character usage, prev
> > >    setting is also specially considered for the first code point.  As
> > >    laid out in Section 6, in order to detect for the first code point,
> > >    the prev is evaluated.  If prev = 0x00, it is assumed that it is the
> > >    first code point as 0x00 SHOULD not be a permitted character for
> > >    input.  When an LDH is the first code point, there is a need to make
> > >    a special consideration.  Regularly, if n = LDH is encountered
> > >    (Section 5), it will be output as "-n" and prev is not changed.
> > >    However, if the first code point is an LDH, after outputting "-n",
> > >    prev is updated to = lowercase(n).  This is to ensure and maintain
> > >    that only the first code point coming in will have a prev = 0x00.
> > >
> > >Chung & Leung                                                  [Page 8]
> > >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> > >
> > >5. LDH Considerations
> > >
> > >    Finally, the 37th character of the entire LDH repertoire, the hyphen
> > >    will be used to indicate LDH exceptions.  Extending the hyphen
> > >    consideration of DUDE-02, ACE37 gives special consideration for the
> > >    entire LDH repertoire.  All LDH characters will be encoded "as is"
> > >    with the addition of a leading hyphen.  For example, the character
> > >    "a" will be encoded within ACE37 as "-a".  The hyphen character "-"
> > >    will be encoded as "--".
> > >
> > >    This ensures that each LDH character will only take up 2 character
> > >    spaces within an ACE37 encoded string and also will allow
> > >    administrators to see the actual characters, similar to the AMC
> > >    series.  Unlike the AMC series however, the hyphen is not used to
> > >    indicate an ongoing mode change, but only the following character.
> > >    Therefore retaining the simplicity of the DUDE-02 single-mode,
> > >    single-pass philosophy.
> > >
> > >6. Encoding Procedure
> > >
> > >    Similar to DUDE, all ordering of bits and quartets is big-endian.
> > >    The following describes the encoding procedure:
> > >
> > >    Set initial value for prev = 0x00
> > >    for each input code point = n
> > >       if n is an LDH {A-z, 0-9, -}
> > >          output "-n"                   (Section 5: LDH Considerations)
> > >          if prev = 0x00                (Section 4.2: First Code Point)
> > >             let prev = lowercase(n)
> > >       else perform code block shifting (Section 2: Code Block Shifting)
> > >       let diff = prev XOR n            (n after code block shifting)
> > >       if diff<=0x7F --------------------------------------+
> > >          and if this is the first code point (Section 4.2)|
> > >          then output 15-bit form: <b32><b32><b32>         |
> > >          else, output 7-bit form: <b4><b32>               |
> > >       if 0x80<=diff<=0x7FFF                               +-(Section 4:
> > >          output 15-bit form: <b32><b32><b32>              |   Base-4
> > >       if 0x8000<=diff<=0x1FFFF                            | Characters)
> > >          and if this is the first code point (Section 4.2)|
> > >          output 17-bit form: w<b4><b32><b32><b32>         |
> > >       if 0x20000<=diff<=0xFFFFF                           |
> > >          output 20-bit form: ww<b32><b32><b32><b32>       |
> > >       if 0x100000<=diff<=0x10FFFF                         |
> > >          output 22-bit form: <b4>w<b32><b32><b32><b32> ---+
> > >       let prev = n
> > >    end and obtain next n and return to: "for each input code point = n"
> > >
> > >    The following is a more comprehensive pseudo code:
> > >
> > >    let prev = 0x00
> > >    for each input integer n (in order) do begin
> > >       if n = "-" or "0..9" or "A..Z" or "a..z"
> > >       then output "hyphen"+"char(n)"
> > >Chung & Leung                                                  [Page 9]
> > >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> > >
> > >          if prev = 0x00
> > >             let prev = lowercase(n)
> > >
> > >       else begin
> > >          if n = 0x00
> > >             then error and abort
> > >          if n <= 9FFF
> > >          n = n - 0x30
> > >             if n < 0
> > >             then n = 9FFF + n
> > >
> > >          let diff = prev XOR n
> > >
> > >          if diff <= 0x7F
> > >             if prev = 0x00
> > >             then output with 3 base-32 characters
> > >          else, output first 2 bits with a base-4 character {wxyz}
> > >             and remaining 5 bits with 1 base-32 character
> > >
> > >          if 0x80 <= diff <= 0x7FFF
> > >          then output all 15 bits with base-32 characters
> > >
> > >          if 0x8000 <= diff <= 0xFFFF
> > >             if prev = 0x00
> > >             then output first 2 bits with a base-4 {xyz} (except w)
> > >             and output remaining 15 bits with base-32
> > >          else, output "w"
> > >             and output first 2 bits with a base-4 {xyz} (except w]
> > >             and output remaining 15 bits with base-32
> > >
> > >          if 0x10000 <= diff <= 0x1FFFF
> > >          then output "w"
> > >             and output first 2 bits with a base-4 {xyz} (except w)
> > >             and output remaining 15 bits with base-32
> > >
> > >          if 0x20000 <= diff <= 0xFFFFFF
> > >          then output "w"
> > >             and output all 20 bits with base-32 characters
> > >
> > >          if 0x100000 <= diff <= 0x10FFFF
> > >          then output first 2 bits with a base-4 {xyz} (except w)
> > >             and output "w"
> > >             and output remaining 15 bits with base-32
> > >
> > >          let prev = n
> > >       end
> > >    end
> > >
> > >    Nameprep [NAMEPREP] is not discussed in this document, but is
> > >    expected that it be implemented for IDN.  Hence, regardless of the
> > >    code point presented, an encoder MUST not produce an incorrect
> > >    output.  The encoder must fail if it encounters a negative input
> > >    value.
> > >Chung & Leung                                                 [Page 10]
> > >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> > >
> > >
> > >    The initial value used is 0x00 so that all domains beginning with a
> > >    CJK ideograph or within row 0 (U+0000..U+0FFF) will be shorter.
> > >    Note that after the code block shifting (Section 2), the entire Han
> > >    library is within 0x0000..0x6FFF, while row 0 is fitted to
> > >    0x7000..0x7FFF.  Therefore by using an initial value of 0x00 the
> > >    diff for all Han and row 0 characters will be less than 0x7FFF.  The
> > >    initial value is also used as a check point for the first code point
> > >    considerations (Section 4.2).
> > >
> > >    Additionally, an optional mixed-case annotation mechanism is
> > >    discussed in Appendix B.
> > >
> > >7. Decoding Procedure
> > >
> > >    A thorough description of the decoding rules, except for the final
> > >    reversal of the code block shifting has been presented in Sections
> > >    4.1 and 4.2.  The following description is a brief representation of
> > >    the decoding procedure:
> > >
> > >    let prev = 0x00
> > >    while the input string is not exhausted
> > >       if present character = hyphen               (Section 5: LDH
> > >          discard and output next character         Considerations)
> > >       else, depending on the presented form       (Section 4)
> > >          convert into duplets and quintets        (Section 4 & 3)
> > >          and concatenate to form diff
> > >       let prev = prev XOR diff
> > >       reverse code block shifting:                (Section 2)
> > >          if prev<=0x9FFF
> > >             and if prev<=0x6FFF
> > >                    output character = prev + 0x3000
> > >             else, output character = prev - 0x7000
> > >          else output character = prev
> > >       output character
> > >    End
> > >
> > >    The following is a more comprehensive pseudo code for the decoding
> > >    precedure:
> > >
> > >    let prev = 0x00
> > >    while the input string is not exhausted do begin
> > >       if present character = hyphen    /*Section 5:LDH Considerations*/
> > >       then consume and discard hyphen
> > >          and obtain the next character
> > >          and output character
> > >          if prev = 0x00                /*Section 4.2:First Code Point*/
> > >             let prev = code block shifted lowercase output character
> > >
> > >       else,
> > >          if present character = Base-32 characters (0..v)
> > >             consume present character and next 2 characters
> > >             and convert them to quintets according to Base-32
> > >Chung & Leung                                                 [Page 11]
> > >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> > >
> > >             concatenate the resulting quintets to form diff
> > >             /*15 bit form, 0x80<=diff<=0x7FFF*/
> > >
> > >          if present character = Base-4 characters {xyz} and NOT w
> > >             consume present character
> > >                and convert it to a duplet according to Base-4
> > >
> > >             if prev = 0x00
> > >                obtain and consume next 3 characters
> > >                and convert them to quintets according to Base-32
> > >                concatenate duplet with the 3 quintets to form diff
> > >                /*first code point: 17 bit form, 0x8000<=diff<=0x1FFFF*/
> > >
> > >             else, if next character = Base-32 character (0..v)
> > >                then consume and convert to quintet according to Base-32
> > >                concatenate duplet with the quintet to form diff
> > >                /*7 bit form, diff<=0x7F*/
> > >
> > >             else, obtain next character
> > >             if next character = Base-4 characters {xyz} and NOT w
> > >                then fail and indicate error
> > >
> > >             else, if next character = w
> > >                then consume and discard w and obtain next 4 characters
> > >                consume and convert characters to
> > >                   quintets according to Base-32
> > >                concatenate duplet with the 4 quintets to form diff
> > >                /*22 bit form, 0x100000<=diff<=0x10FFFF*/
> > >
> > >          if present character = w
> > >             discard "w" and obtain next character
> > >
> > >             if next character = Base-4 characters {xyz} and NOT w
> > >
> > >                and if prev = 0x00
> > >                    obtain and consume next 4 characters
> > >                    and convert characters to quintets based on Base-32
> > >                    concatenate the 4 quintets to form diff
> > >                    /*first code point: 20 bit form,*/
> > >                    /*0x20000<=diff<=0xFFFFFF       */
> > >
> > >                else, consume and convert to duplet according to Base-4
> > >                   and obtain and consume next 3 characters
> > >                   and convert to quintets according to Base-32
> > >                   concatenate duplet with the 3 quintets to form diff
> > >                   /*17 bit form, 0x8000<=diff<=0x1FFFF*/
> > >
> > >             else, if next character = w
> > >                then consume and discard w
> > >                and obtain and consume next 4 characters
> > >                   and convert to quintets according to Base-32
> > >                concatenate duplet the 4 quintets to form diff
> > >                /*20 bit form, 0x20000<=diff<=0xFFFFFF*/
> > >Chung & Leung                                                 [Page 12]
> > >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> > >
> > >
> > >             else, if next character = Base-32 character (0..v)
> > >                then convert to quintet according to Base-32
> > >                set quintet to diff
> > >                /*7 bit form, diff<=0x7F*/
> > >
> > >          fail upon encountering a non-ACE37 character
> > >             or end-of-input
> > >
> > >          let prev = prev XOR diff
> > >
> > >          if prev <= 0x9FFF                /*reversal of the code    */
> > >             and if prev <= 6FFF           /*block shifting described*/
> > >             output = prev + 0x3000        /*in Section 2            */
> > >             else, output = prev - 0x7000
> > >          else, output prev
> > >       end
> > >    end
> > >    encode the output sequence and compare it to the input string
> > >    fail if they do not match (case insensitively)
> > >
> > >8. Examples
> > >
> > >    ACE37 is likely to be implemented with an ACE prefix in the form
> > >    "xx--".  The actual prefix to be used is not discussed in this
> > >    document.  The following examples are taken from the mailing list as
> > >    well as from DUDE-02 and the AMC series.  The resulting ACE37 string
> > >    is compared with that using DUDE:
> > >
> > >    (A) JPNIC (the registry of .jp domain)
> > >
> > >    Unicode: U+793E U+56E3 U+6CD5 U+4EBA U+65E5 U+672C U+30CD U+30C3
> > >             U+30C8 U+30EF U+30FC U+30AF U+30A4 U+30F3 U+30D5 U+30A9
> > >             U+30E1 U+30FC U+30B7 U+30E7 U+30F3 U+30BB U+30F3 U+30BF
> > >             U+30FC
> > >      ACE37: i9urut6hm8jfaqv0m9dv1wewbx7wjyjwbynx6zsy8wtybygwky8y8ycy3
> > >             (57 char)
> > >    DUDE-02: (error: result string exceeds 59 characters*)
> > >             Note: 59 characters is the maximum allowable when the ACE
> > >             prefix "xx--" is included
> > >
> > >
> > >    (B) A health-insurance organization in Tokyo
> > >
> > >    Unicode: U+6771 U+4EAC U+90FD U+60C5 U+5831 U+30B5 U+30FC U+30D3
> > >             U+30B9 U+7523 U+696D U+5065 U+5EB7 U+4FDD U+967A U+7D44
> > >             U+5408
> > >      ACE37: drhaetvihk1o67ka44y9xfzahcqv2e6883micbaud7apuqac (48 char)
> > >    DUDE-02: (error: result string exceeds 59 characters)
> > >
> > >
> > >
> > >
> > >Chung & Leung                                                 [Page 13]
> > >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> > >
> > >    (C) 6 hangul syllables
> > >
> > >    Unicode: U+C138 U+ACC4 U+C758 U+BAA8 U+B4E0 U+C0AC
> > >      ACE37: xg9orfsqssvfg3i8t2c (19 char)
> > >    DUDE-02: 6txiy79ny53nz79a8wizwwn (23 char)
> > >
> > >
> > >    (D) maji<de>koi<suru>5<byou><mae>  (Latin, hiragana, kanji)
> > >
> > >    Unicode: U+006D U+0061 U+006A U+0069 U+3067 U+006B U+006F U+0069
> > >             U+3059 U+308B U+0035 U+79D2 U+524D
> > >      ACE37: -m-a-j-is0a-k-o-xu06i-5iapqsv (30 char)
> > >    DUDE-02: pnmdvssqvssnegvsva7cvs5qz38hu53r (32 char)
> > >
> > >
> > >    (E) <pafii>de<runba>  (Latin, katakana)
> > >
> > >    Unicode: U+30D1 U+30D5 U+30A3 U+30FC U+0064 U+0065 U+30EB U+30F3
> > >             U+30D0
> > >      ACE37: 06hw4zmyv-d-ewnwox3 (19 char)
> > >    DUDE-02: vs5bezgxrvs3ibvs2qtiud (22 char)
> > >
> > >
> > >    (F) <sono><supiido><de>  (hiragana, katakana)
> > >
> > >    Unicode: U+305D U+306E U+30B9 U+30D4 U+30FC U+30C9 U+3067
> > >      ACE37: 02txj06nzdx8xl05e (17 char)
> > >    DUDE-02: vsvpvd7hypuivf4q (16 char)
> > >
> > >
> > >    (G) 2 Arbitrary Plane Two Code Points
> > >
> > >    Unicode: U+261AF U+261BF
> > >      ACE37: w4odfwg (7 char)
> > >    DUDE-02: uyt6rta (7 char)
> > >
> > >
> > >    (H) Czech: Pro<ccaron>prost<ecaron>nemluv<iacute><ccaron>esky
> > >
> > >    Unicode: U+0050 U+0072 U+006F U+010D U+0070 U+0072 U+006F U+0073
> > >             U+0074 U+011B U+006E U+0065 U+006D U+006C U+0075 U+0076
> > >             U+00ED U+010D U+0065 U+0073 U+006B U+0079
> > >      ACE37: -p-r-o0bt-p r-o-s-twm-n-e-m-l-u-v0fm0f0-e-s-k-y (47 char)
> > >    DUDE-02: vauctptyctzpctptnhtyrtzfmibtjd3mt8atyitgtitc (44 char)
> > >
> > >
> > >    (I) Chinese
> > >
> > >    Unicode: U+4ED5 U+5011 U+7232 U+4EC0 U+9EBD U+4E0D U+8AAA U+4E2D
> > >             U+6587
> > >      ACE37: 7mmfm7oh3n7is3ts5gh57h47ata (27 char)
> > >    DUDE-02: w85gt86huuudv69c7szp7s5a6w4h6w2hu54k (36 char)
> > >
> > >Chung & Leung                                                 [Page 14]
> > >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> > >
> > >9. Summary & Comparisons
> > >
> > >    In summary, ACE37 is based on the DUDE-02 process with an improved
> > >    compression scheme for code point sequences that are less likely to
> > >    cluster too closely together, such as CJK ideographs.
> > >
> > >    Since it is the design team's indication that generally 30
> > >    characters should be good enough and that there are a lot of concern
> > >    from the Asian community that 14-15 characters is definitely
> > >    limiting and that few indication from the Latin community that
> > >    length is really a concern, ACE37 have set its objective to increase
> > >    the possible number of characters in a worse case scenario closer to
> > >    20 characters.
> > >
> > >    ACE37 have succeeded in creating a very simple variation based on
> > >    the primary ACEs identified by the design team to create an ACE that
> > >    achieves dramatically better performance for CJK characters while
> > >    maintaining the simplicity of DUDE.
> > >
> > >    Key Improvements of ACE37 over DUDE-02
> > >    - much more spacious for Han characters.  Improved worst-case
> > >      scenario to 21 Han ideographs by introducing code block shifting
> > >      and utilizing fully base-32 characters
> > >    - no need to arbitrarily pre-pend flagging bits to identify code
> > >      point brackets.  Instead base-4 characters and diff forms are used
> > >    - base-32 and base-4 characters can be easily computed instead of
> > >      mapped using lookup tables
> > >
> > >    Key Improvements of ACE37 over the AMC series
> > >    - a more simple process, utilizing the one-pass differential
> > >      mechanism from DUDE-02
> > >    - a much more simple code block shifting process is used in ACE37 to
> > >      achieve a similar goal for the complex multiple reference point
> > >      system used by the AMC series
> > >    - base-32 and base-4 characters can be easily computed instead of
> > >      mapped using lookup tables
> > >
> > >    Key Improvements of ACE37 over LACE
> > >    - a more simple process, utilizing the one-pass differential
> > >      mechanism from DUDE-02
> > >    - much more spacious for Han characters.  Improved worst-case
> > >      scenario to 21 Han ideographs by introducing code block shifting
> > >      and utilizing fully base-32 characters
> > >    - base-32 and base-4 characters can be easily computed instead of
> > >      mapped using lookup tables
> > >
> > >    Two Excel spreadsheet for ACE37 encoding and decoding can be found
> > >    at http://www.dnsii.org/ace37/ace37-encode.xls and
> > >    http://www.dnsii.org/ace37/ace37-decode.xls respectively.  This
> > >    illustrates the simplicity of ACE37 and provides a handy tool for
> > >    checking ACE37 encoding and decoding algorithms.  The ACE37-encode
> > >    spreadsheet also includes a DUDE-encode worksheet.
> > >
> > >Chung & Leung                                                 [Page 15]
> > >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> > >
> > >10. Security Considerations
> > >
> > >    This document does not talk about DNS security issues, and it is
> > >    believed that the proposal does not introduce additional security
> > >    problems not already existent and/or anticipated by adding
> > >    multilingual characters to DNS and/or using ACE.
> > >
> > >11. References
> > >
> > >    [AMC-W]   Adam M. Costello, "AMC-ACE-W version 0.1.0", May 31, 2001.
> > >
> > >    [AMC-V]   Adam M. Costello, "AMC-ACE-V version 0.1.0", May 31, 2001.
> > >
> > >    [DUDE-02] Mark Welter, Brian W. Spolarich & Adam M.
> > >              Costello, "Differential Unicode Domain Encoding (DUDE)",
> > >              June 7, 2001.
> > >
> > >    [LACE]    Mark Davis, IBM & Paul Hoffman, IMC & VPNC, "LACE: Length-
> > >              based ASCII Compatible Encoding for IDN", January 5, 2001.
> > >
> > >    [Nameprep]Paul Hoffman, IMC & VPNC & Marc Blanchet, ViaGenie,
> > >              "Preparation of Internationalized Host Names", February
> > >              24, 2001
> > >
> > >Appendix A. Acknowledgements
> > >
> > >    The ACE37 draft is a combination of DUDE-02, the AMC series and
> > >    LACE, and takes into consideration the report of the ACE design
> > >    team.  The authors would therefore like to thank the authors of
> > >    DUDE-02 - Mark Welter, Brian W. Spolarich & Adam M. Costello; the
> > >    authors of the AMC series - Adam M.Costello; the authors of LACE -
> > >    Mark Davis & Paul Hoffman; and, the ACE design team and its advisors
> > >    - Adam M. Costello, Paul Hoffman, Makoto Ishisone, David Laurence,
> > >    Brian Spolarich, Rick Wesson, Marc Blanchet, Patrik Faltstrom and
> > >    Erik Nordmark for their inspirations.
> > >
> > >Appendix B. Mixed-case annotation
> > >
> > >    This section is taken from DUDE and modified for ACE37
> > >
> > >    In order to use ACE37 to represent case-insensitive Unicode strings,
> > >    higher layers need to case-fold the Unicode strings prior to ACE37
> > >    encoding.  The encoded string can, however, use mixed-case base-4
> > >    characters as an annotation telling how to convert the folded
> > >    Unicode string into a mixed-case Unicode string for display
> > >    purposes.
> > >
> > >    Each Unicode code point (unless it is an LDH) is represented by a
> > >    sequence of base-4 and base-32 characters, the first of which is
> > >    mostly a base-4 character, which is always a letter {wxyz} (as
> > >    opposed to a digit).  If that letter is uppercase, it is a
> > >    suggestion that the Unicode character be mapped to uppercase (if
> > >
> > >Chung & Leung                                                 [Page 16]
> > >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> > >
> > >    possible); if the letter is lowercase, it is a suggestion that the
> > >    Unicode character be mapped to lowercase (if possible).
> > >
> > >    If the code point is an LDH, for example "a", it will be represented
> > >    as "-a".  To mark the case for an LDH, simply set the LDH to the
> > >    desired case following the "-".  Fir example if an uppercase "A" is
> > >    desired, the encoded form SHOULD be "-A".
> > >
> > >    Note that there is a possibility that no base-4 character is present
> > >    for a code point representation.  That is the case for a 15-bit diff
> > >    form.  In this case, the base-32 characters will be used for case
> > >    suggestion (if possible), similar to that discussed for using a
> > >    base-4 character.  However, also note that there is a very remote
> > >    possibility that all 3 base-32 characters are digits.  If this
> > >    happens, case unfolding will be aborted.  Since case annotation is
> > >    an optional feature and used for display purposes only, this is not
> > >    considered to be a major concern.  Moreover, the possibility of this
> > >    happening is truly remote at only (32639/27)/1114109 or just 0.1%
> > >    chance of happening.
> > >
> > >    ACE37 encoders and decoders are not required to support these
> > >    annotations, and higher layers need not use them.
> > >
> > >    For example:  In order to suggest that example (H) in Section 8:
> > >    "Examples" be displayed as:
> > >    Czech: Pro<ccaron(uppercase)>prost<ecaron(uppercase)>
> > >           nemLUV<iacute(lowercase)><ccaron(lowercase)>esky
> > >
> > >    one could capitalize the ACE37 encoding as:
> > >      ACE37: -P-r-o0BT-p-r-o-s-tWM-n-e-m-L-U-V0fm0f0-e-s-k-y (47 char)
> > >
> > >Authors:
> > >
> > >Edmon Chung
> > >Neteka Inc.
> > >2462 Yonge St. Toronto,
> > >Ontario, Canada M4P 2H5
> > >edmon@neteka.com
> > >
> > >David Leung
> > >Neteka Inc.
> > >2462 Yonge St. Toronto,
> > >Ontario, Canada M4P 2H5
> > >david@neteka.com
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >Chung & Leung                                                 [Page 17]
> >





From owner-idn@ops.ietf.org  Thu Jul  5 14:03:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA21813
	for <idn-archive@lists.ietf.org>; Thu, 5 Jul 2001 14:03:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IDGP-000J5W-00
	for idn-data@psg.com; Thu, 05 Jul 2001 10:50:05 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.31 #1)
	id 15IDGO-000J5Q-00
	for idn@ops.ietf.org; Thu, 05 Jul 2001 10:50:04 -0700
Received: (qmail 32436 invoked from network); 6 Jul 2001 01:06:16 -0000
Received: from chubby.internal.realnames.com (HELO heaven.internal.realnames.com) (10.1.5.39)
  by friendly.realnames.com with SMTP; 6 Jul 2001 01:06:16 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:4379]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <164897@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Thu, 5 Jul 2001 10:47:54 AM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2650.21)
	id <N4MTB7VV>; Thu, 5 Jul 2001 10:48:44 -0700
Message-ID: <B7233BD6980AD411875700508B5BD5D2011E958E@elporto.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: idn@ops.ietf.org
Subject: [idn] FW: I-D ACTION:draft-arrouye-idn-ie5-resolution-00.txt
Date: Thu, 5 Jul 2001 10:48:43 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C1057A.BB72DAA0"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C1057A.BB72DAA0
Content-Type: text/plain

We wrote this in response to James Seng's e-mail asking if we could document
how IDNs resolve when typed in IE's command line.

YA

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
Sent: Thursday, July 05, 2001 3:54 AM
Subject: I-D ACTION:draft-arrouye-idn-ie5-resolution-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: IDN Resolution in Windows Internet Explorer 5.0
and 
                          Above
	Author(s)	: Y. Arrouye
	Filename	: draft-arrouye-idn-ie5-resolution-00.txt
	Pages		: 6
	Date		: 03-Jul-01
	
This document describes how internationalized domain names (IDNs) are being
resolved in the Windows Internet Explorer (IE) Web browser version 5.0 and
above. The resolution that is described in this document is currently
available on a limited basis for an existing test bed. This document focuses
on the different steps that are taken after a user enters an IDN in the
address bar of IE, up to when the relevant Web page is displayed in the
user's browser.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-arrouye-idn-ie5-resolution-00.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in, type
"cd internet-drafts" and then
	"get draft-arrouye-idn-ie5-resolution-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-arrouye-idn-ie5-resolution-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


------_=_NextPart_000_01C1057A.BB72DAA0
Content-Type: message/rfc822

To: 
Subject: 
Date: Thu, 5 Jul 2001 10:48:44 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_002_01C1057A.BB72DAA0"


------_=_NextPart_002_01C1057A.BB72DAA0
Content-Type: text/plain



------_=_NextPart_002_01C1057A.BB72DAA0
Content-Type: application/octet-stream;
	name="ATT34844"
Content-Disposition: attachment;
	filename="ATT34844"

Content-type: message/external-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010703150624.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-arrouye-idn-ie5-resolution-00.txt

------_=_NextPart_002_01C1057A.BB72DAA0
Content-Type: message/external-body;
	site="internet-drafts";
	dir="draft-arrouye-idn-ie5-resolution-00.txt";
	mode="ftp.ietf.org";
	access-type="anon-ftp"


------_=_NextPart_002_01C1057A.BB72DAA0--

------_=_NextPart_000_01C1057A.BB72DAA0--



From owner-idn@ops.ietf.org  Thu Jul  5 14:39:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA23117
	for <idn-archive@lists.ietf.org>; Thu, 5 Jul 2001 14:39:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IDs9-000KHD-00
	for idn-data@psg.com; Thu, 05 Jul 2001 11:29:05 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15IDs8-000KH7-00
	for idn@ops.ietf.org; Thu, 05 Jul 2001 11:29:04 -0700
Message-ID: <003a01c10580$e1b3e320$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: <idn@ops.ietf.org>, "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>
References: <5.1.0.14.1.20010705084656.02b0e138@mail.viagenie.qc.ca> <5.1.0.14.1.20010705120420.01efc498@mail.viagenie.qc.ca>
Subject: [idn] draft-idn-ace37-00.txt
Date: Thu, 5 Jul 2001 14:32:41 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi Marc,
Sorry about all the fuss about trying to submit this draft. Truly.


In any case, please refer to http://www.dnsii.org/idn-ace37-00.txt for my
draft on ACE37.  In essence, the following is what ACE37 tries to achieve.

   ACE37 is a combination of DUDE-02, AMC-W/V and LACE.  ACE37 utilizes
   the simple one pass algorithm of DUDE, the character block
   considerations of AMC-W/V and the Base-32 compression of LACE.  It
   also fully utilizes entire LDH set currently allowed in the DNS (A-
   z, 0-9 and "-") within its character repertoire to optimize
   performance and compression.  Even for the worst-case scenario in
   ACE37, any name can have 21 characters including Chinese, Japanese
   and Korean names.

   ACE37 uses simple character block shifting to achieve the
   compression efficiency of the AMC series, retains the one-pass and
   one mode XOR differential mechanism used by DUDE while embracing the
   base-32 compression used by LACE for efficient character bit
   information.

I am truly excited about the idea and think that it provides a better
solution based on the findings of the ACE design team report.  Perhaps there
are still a number of holes in it, but I think the general direction: to
combine the primary ACEs in a DUDE mode, is a good way to go.

Edmon



> At/À 11:48 2001-07-05 -0400, Edmon you wrote/vous écriviez:
> >Hi all,
> >
> >I was unaware that the workgroup no longer accepts new drafts.
>
> see:
>
> Message-Id: <5.1.0.14.1.20010626000156.03d85e50@mail.viagenie.qc.ca>
> Date: Tue, 26 Jun 2001 00:05:28 -0400
> To: idn@ops.ietf.org
> From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
> Subject: [idn] wg next steps
>
> and:
>
> Message-Id: <5.1.0.14.1.20010629080012.02042a10@mail.viagenie.qc.ca>
> Date: Fri, 29 Jun 2001 08:06:14 -0400
> To: idn@ops.ietf.org
> From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
> Subject: [idn] document pools active
>
> And, as I wrote in the email, you are _encouraged_ to submit as individual
> submission. The only difference is filename and no listing in the ietf idn
> wg charter web page.
>
> Marc.
>
>





From owner-idn@ops.ietf.org  Thu Jul  5 16:20:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA26324
	for <idn-archive@lists.ietf.org>; Thu, 5 Jul 2001 16:20:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IEr3-000Lp4-00
	for idn-data@psg.com; Thu, 05 Jul 2001 12:32:01 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IEr2-000Lox-00
	for idn@ops.ietf.org; Thu, 05 Jul 2001 12:32:00 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA27678;
        Thu, 5 Jul 2001 15:31:29 -0400 (EDT)
Message-Id: <200107051931.PAA27678@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Yves Arrouye <yves@realnames.com>
cc: idn@ops.ietf.org
Subject: Re: [idn] FW: I-D ACTION:draft-arrouye-idn-ie5-resolution-00.txt 
In-reply-to: Your message of "Thu, 05 Jul 2001 10:48:43 PDT."
             <B7233BD6980AD411875700508B5BD5D2011E958E@elporto.internal.realnames.com> 
Date: Thu, 05 Jul 2001 15:31:29 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

do you think you could update this 'documentation' to simply reflect
what is done by IE and to leave out the marketing languange touting
the supposed advantages of this approach?

(and unless you have knowledge that Microsoft will fail to implement
IDN correctly once it is standardized, could you also remove 
"and Above" from the title?)

I for one do not condone premature deployment of IDNs outside of 
controlled conditions, or abuse of the market by monopolies.  Value-neutral
documentation is one thing, but I think it's inappropriate to attempt 
to use IETF publication processes to promote abuses of the both monopoly
power and the protocol standards. 

Even those who have less objections than I do not necessarily regard this 
mechanism as a Good Thing.  

Keith



From owner-idn@ops.ietf.org  Thu Jul  5 16:50:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA27199
	for <idn-archive@lists.ietf.org>; Thu, 5 Jul 2001 16:50:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IFvd-000NYN-00
	for idn-data@psg.com; Thu, 05 Jul 2001 13:40:49 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.31 #1)
	id 15IFvd-000NYG-00
	for idn@ops.ietf.org; Thu, 05 Jul 2001 13:40:49 -0700
Received: (qmail 6132 invoked from network); 6 Jul 2001 03:57:04 -0000
Received: from chubby.internal.realnames.com (HELO heaven.internal.realnames.com) (10.1.5.39)
  by friendly.realnames.com with SMTP; 6 Jul 2001 03:57:04 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:4715]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <167061@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Thu, 5 Jul 2001 1:39:08 PM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2650.21)
	id <N4MTB02M>; Thu, 5 Jul 2001 13:39:42 -0700
Message-ID: <B7233BD6980AD411875700508B5BD5D2011E9596@elporto.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: idn@ops.ietf.org
Subject: RE: [idn] FW: I-D ACTION:draft-arrouye-idn-ie5-resolution-00.txt 
Date: Thu, 5 Jul 2001 13:39:41 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> (and unless you have knowledge that Microsoft will fail to implement
> IDN correctly once it is standardized, could you also remove 
> "and Above" from the title?)

Well, this is how it works in IE 5.5 too. And in IE 6 beta. And in later
versions of IE, I'd assume, until this working group produces a
recommendation. Then, I hope, everybody will want to do something else. I
for one would *really* like to have a standard to implement.

Nor do I believe that we are abusing either the IETF publication process or
protocol standards, as you suggested, by the way. We replied to a request
for information, and believe that both the disadvantages (e.g. doesn't work
as part of an URI) and the advantages of this approach have been presented.

YA



From owner-idn@ops.ietf.org  Thu Jul  5 18:04:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA28639
	for <idn-archive@lists.ietf.org>; Thu, 5 Jul 2001 18:04:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IGz5-000PMU-00
	for idn-data@psg.com; Thu, 05 Jul 2001 14:48:27 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IGz4-000PMN-00
	for idn@ops.ietf.org; Thu, 05 Jul 2001 14:48:26 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id RAA28601;
        Thu, 5 Jul 2001 17:48:18 -0400 (EDT)
Message-Id: <200107052148.RAA28601@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Yves Arrouye <yves@realnames.com>
cc: idn@ops.ietf.org
Subject: Re: [idn] FW: I-D ACTION:draft-arrouye-idn-ie5-resolution-00.txt 
In-reply-to: Your message of "Thu, 05 Jul 2001 13:39:41 PDT."
             <B7233BD6980AD411875700508B5BD5D2011E9596@elporto.internal.realnames.com> 
Date: Thu, 05 Jul 2001 17:48:18 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > (and unless you have knowledge that Microsoft will fail to implement
> > IDN correctly once it is standardized, could you also remove
> > "and Above" from the title?)
> 
> Well, this is how it works in IE 5.5 too. And in IE 6 beta. And in later
> versions of IE, I'd assume, until this working group produces a
> recommendation. 

right.  but if the document is published as an RFC then the title is
frozen, even if the behavior of IE changes.    so the title could
be misleading at some point.

> Nor do I believe that we are abusing either the IETF publication process or
> protocol standards, as you suggested, by the way. We replied to a request
> for information, and believe that both the disadvantages (e.g. doesn't work
> as part of an URI) and the advantages of this approach have been presented.

I do appreciate your documeting the interface, I just don't think that
some of the language is appropriate.

as for documenting the disadvantages, you haven't even scratched the surface.  
for instance, you're giving support to at least one illegal monopoly that 
continues to use its power to victimize consumers.



From owner-idn@ops.ietf.org  Thu Jul  5 18:16:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA28893
	for <idn-archive@lists.ietf.org>; Thu, 5 Jul 2001 18:16:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IHGp-000PtY-00
	for idn-data@psg.com; Thu, 05 Jul 2001 15:06:47 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.31 #1)
	id 15IHGp-000PtS-00
	for idn@ops.ietf.org; Thu, 05 Jul 2001 15:06:47 -0700
Received: (qmail 9195 invoked from network); 6 Jul 2001 05:23:02 -0000
Received: from chubby.internal.realnames.com (HELO heaven.internal.realnames.com) (10.1.5.39)
  by friendly.realnames.com with SMTP; 6 Jul 2001 05:23:02 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:4839]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <168124@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Thu, 5 Jul 2001 3:05:10 PM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2650.21)
	id <N4MTCAQX>; Thu, 5 Jul 2001 15:05:40 -0700
Message-ID: <B7233BD6980AD411875700508B5BD5D2011E9599@elporto.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: idn@ops.ietf.org
Subject: RE: [idn] FW: I-D ACTION:draft-arrouye-idn-ie5-resolution-00.txt 
Date: Thu, 5 Jul 2001 15:05:39 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> right.  but if the document is published as an RFC then the title is
> frozen, even if the behavior of IE changes.    so the title could
> be misleading at some point.

Understood. Hopefully, in the process of publishing as an RFC, I'd get a
chance at changing the title, right? But I'll make it more clear when the
document will get revised, and will take your comments into account.

> as for documenting the disadvantages, you haven't even 
> scratched the surface.  
> for instance, you're giving support to at least one illegal 
> monopoly that 
> continues to use its power to victimize consumers..

Boy, I hope that my being yves@debian.org, a contributor to the ICU project
a number of you are using, and having done a number of other long-standing
contributions to free software, will save my soul :)

IMHO, the beneficiaries of such a setup are the people who bought names that
they could not use up to now. And I believe we both agree that a standard
will make this discussion moot, as everybody will then implement the
standard.

Regards,
YA



From owner-idn@ops.ietf.org  Thu Jul  5 18:24:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA28986
	for <idn-archive@lists.ietf.org>; Thu, 5 Jul 2001 18:24:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IHQI-0000DS-00
	for idn-data@psg.com; Thu, 05 Jul 2001 15:16:34 -0700
Received: from pimout2-ext.prodigy.net ([207.115.63.101] helo=pimout2-int.prodigy.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IHQH-0000DM-00
	for idn@ops.ietf.org; Thu, 05 Jul 2001 15:16:33 -0700
Received: from pc (ip-20-152-158.chicago-n.navipath.net [64.20.152.158])
	by pimout2-int.prodigy.net (8.11.0/8.11.0) with SMTP id f65MG98217200;
	Thu, 5 Jul 2001 18:16:10 -0400
Message-ID: <042601c105a0$428986e0$6b961440@pc>
From: "Jim Fleming" <JimFleming@prodigy.net>
To: "Keith Moore" <moore@cs.utk.edu>, "Yves Arrouye" <yves@realnames.com>
Cc: <idn@ops.ietf.org>
References: <200107052148.RAA28601@astro.cs.utk.edu>
Subject: Re: [idn] FW: I-D ACTION:draft-arrouye-idn-ie5-resolution-00.txt 
Date: Thu, 5 Jul 2001 17:17:14 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-Mimeole: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

When you say...."illegal monopoly"....Are you referring to ICANN ?

Jim Fleming
http://www.DOT-Arizona.com
http://www.DOT.Arizona


----- Original Message -----
From: "Keith Moore" <moore@cs.utk.edu>
To: "Yves Arrouye" <yves@realnames.com>
Cc: <idn@ops.ietf.org>
Sent: Thursday, July 05, 2001 4:48 PM
Subject: Re: [idn] FW: I-D ACTION:draft-arrouye-idn-ie5-resolution-00.txt


> > > (and unless you have knowledge that Microsoft will fail to implement
> > > IDN correctly once it is standardized, could you also remove
> > > "and Above" from the title?)
> >
> > Well, this is how it works in IE 5.5 too. And in IE 6 beta. And in later
> > versions of IE, I'd assume, until this working group produces a
> > recommendation.
>
> right.  but if the document is published as an RFC then the title is
> frozen, even if the behavior of IE changes.    so the title could
> be misleading at some point.
>
> > Nor do I believe that we are abusing either the IETF publication process
or
> > protocol standards, as you suggested, by the way. We replied to a
request
> > for information, and believe that both the disadvantages (e.g. doesn't
work
> > as part of an URI) and the advantages of this approach have been
presented.
>
> I do appreciate your documeting the interface, I just don't think that
> some of the language is appropriate.
>
> as for documenting the disadvantages, you haven't even scratched the
surface.
> for instance, you're giving support to at least one illegal monopoly that
> continues to use its power to victimize consumers.
>




From owner-idn@ops.ietf.org  Thu Jul  5 18:39:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA29162
	for <idn-archive@lists.ietf.org>; Thu, 5 Jul 2001 18:39:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IHen-0000dw-00
	for idn-data@psg.com; Thu, 05 Jul 2001 15:31:33 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IHej-0000dY-00
	for idn@ops.ietf.org; Thu, 05 Jul 2001 15:31:30 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f65MUvT12608;
	Fri, 6 Jul 2001 07:30:57 +0900 (KST)
Message-ID: <002701c105a2$f0731800$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Keith Moore" <moore@cs.utk.edu>, "Yves Arrouye" <yves@realnames.com>
Cc: <idn@ops.ietf.org>
References: <200107052148.RAA28601@astro.cs.utk.edu>
Subject: Re: [idn] FW: I-D ACTION:draft-arrouye-idn-ie5-resolution-00.txt 
Date: Fri, 6 Jul 2001 07:36:30 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

AFAIK,
Many versions of Netscape Navigators [456].x   'just send'
 8-bit (not neccesarilly UTF8 in many cases) domain names to DNS servers,
even if they contain  non-LDH special characters, for example '&' .

Is this a feature or a harmful bug ?

To Netscape Navigators, this IE5-IDN-like  approach is not applicable ?
right?
Can any Netscape person answer for this question ?


----- Original Message -----
From: "Keith Moore" <moore@cs.utk.edu>
To: "Yves Arrouye" <yves@realnames.com>
Cc: <idn@ops.ietf.org>
Sent: Friday, July 06, 2001 6:48 AM
Subject: Re: [idn] FW: I-D ACTION:draft-arrouye-idn-ie5-resolution-00.txt


> > > (and unless you have knowledge that Microsoft will fail to implement
> > > IDN correctly once it is standardized, could you also remove
> > > "and Above" from the title?)
> >
> > Well, this is how it works in IE 5.5 too. And in IE 6 beta. And in later
> > versions of IE, I'd assume, until this working group produces a
> > recommendation.
>
> right.  but if the document is published as an RFC then the title is
> frozen, even if the behavior of IE changes.    so the title could
> be misleading at some point.
>
> > Nor do I believe that we are abusing either the IETF publication process
or
> > protocol standards, as you suggested, by the way. We replied to a
request
> > for information, and believe that both the disadvantages (e.g. doesn't
work
> > as part of an URI) and the advantages of this approach have been
presented.
>
> I do appreciate your documeting the interface, I just don't think that
> some of the language is appropriate.
>
> as for documenting the disadvantages, you haven't even scratched the
surface.
> for instance, you're giving support to at least one illegal monopoly that
> continues to use its power to victimize consumers.
>




From owner-idn@ops.ietf.org  Thu Jul  5 18:48:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA29313
	for <idn-archive@lists.ietf.org>; Thu, 5 Jul 2001 18:48:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IHnp-0000wg-00
	for idn-data@psg.com; Thu, 05 Jul 2001 15:40:53 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IHnm-0000wX-00
	for idn@ops.ietf.org; Thu, 05 Jul 2001 15:40:51 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f65MeLT13270;
	Fri, 6 Jul 2001 07:40:21 +0900 (KST)
Message-ID: <003901c105a4$401cf6e0$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Edmon" <edmon@neteka.com>, "Natalia Syracuse" <nsyracus@ietf.org>,
        "David Leung" <david@neteka.com>, <idn@ops.ietf.org>
References: <5.1.0.14.1.20010705084656.02b0e138@mail.viagenie.qc.ca> <006601c10569$ffa20e00$1001a8c0@neteka.com>
Subject: Re: [idn] Re: permission <draft-ietf-idn-ace37-00.txt (attach)
Date: Fri, 6 Jul 2001 07:45:54 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

When the diff value is less than 0xF, what is the ACE37 form for it ?

And any example C doe for ACE37  available on the web ?

Thanks.

Soobok

> > >Chung & Leung                                                  [Page 6]
> > >ACE37       ACE Utilizing All 37 Alphanumeric Characters      July 2001
> > >
> > >    The following table explains how base-4 characters are combined
with
> > >    base-32 characters to form a representation of a diff (key:
b4=base-
> > >    4, b32=base-32):
> > >
> > >              diff value         |bits|       ACE37 Form
> > >        -------------------------|----|----------------------------
> > >                  diff<=0x7F     |  7 | <b4><b32>
> > >            0x80<=diff<=0x7FFF   | 15 | <b32><b32><b32>
> > >          0x8000<=diff<=0x1FFFF  | 17 | w<b4><b32><b32><b32>
> > >         0x20000<=diff<=0xFFFFF  | 20 | ww<b32><b32><b32><b32>
> > >        0x100000<=diff<=0x10FFFF | 22 | <b4>w<b32><b32><b32><b32>
> > >
> > >    Note that the "bits" column represents the maximum number of
> > >    significant bits for the given diff value.  For example when
> > >    diff<=0x7F, the maximum value is 0b1111111, therefore the number of


----- Original Message -----
From: "Edmon" <edmon@neteka.com>
To: "Natalia Syracuse" <nsyracus@ietf.org>; "David Leung"
<david@neteka.com>; "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>;
<idn@ops.ietf.org>
Cc: <jseng@pobox.org.sg>
Sent: Friday, July 06, 2001 12:48 AM
Subject: [idn] Re: permission <draft-ietf-idn-ace37-00.txt (attach)


> Hi all,
>
> I was unaware that the workgroup no longer accepts new drafts.  Anyway, I
> have drafted a new ACE based on the simplicity of DUDE which has hugely
> improved compression.  Worst case scenario CJK could have 21 han
characters!
> Attached below is a copy of the draft (for my original submission), you
can
> also find it at http://www.dnsii.org/idn-ace37-00.txt (easier to read) and
> hopefully in the i-d-n.net website soon.
>
> ACE37 is based on the one-pass one-mode scheme of DUDE (diiferential XOR),
> then utilizes a simple code block shifting (similar to the reference
points
> in the AMC series) to hugely increase the capacity for CJK (worst case
> scenario 21 han characters!) and then utilizes base-32 for compression (as
> in LACE) (DUDE and AMC-w/v uses base-32 only for flagging).  In addition
to
> base-32, a base-4 scheme is introduced by using the remaining characters
> {wxyz}.  These contain 2 bits of character information and doubles as an
> indicator for codepoint brackets.  All the while, the algorithm is kept to
> be as simple as DUDE.
>
> Hopefully you might find that it is interesting and appropriate to be
> considered as an ACE within the IETF.  Afterall, it was intended to be an
> integrated version of the three primary ACEs: DUDE, LACE and the AMC
series,
> identified by the ACE design team report.
>
> Looking forward to all your inputs.
>
> Edmon





From owner-idn@ops.ietf.org  Thu Jul  5 19:31:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA00077
	for <idn-archive@lists.ietf.org>; Thu, 5 Jul 2001 19:31:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IISj-00028V-00
	for idn-data@psg.com; Thu, 05 Jul 2001 16:23:09 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15IISi-00028P-00
	for idn@ops.ietf.org; Thu, 05 Jul 2001 16:23:09 -0700
Message-ID: <00a201c105a8$1a31cb00$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
References: <5.1.0.14.1.20010705084656.02b0e138@mail.viagenie.qc.ca> <006601c10569$ffa20e00$1001a8c0@neteka.com> <003901c105a4$401cf6e0$ed1bd9d2@postel.co.kr>
Subject: Re: [idn] Re: permission <draft-ietf-idn-ace37-00.txt (attach)
Date: Thu, 5 Jul 2001 19:13:24 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Hi,
>
Great hearing from you.  Actually, I sh
ould give you some credit cause you sta
rted the codepoint reordering thing fir
st, though the ACE37 idea really came a
bout earlier than I saw your draft.  An
yway, I think my code block shifting me
chanism is much more simple and can suc
cessfully get 21+ han ideographs which
is much more acceptable than DUDE's cur
rent state.

> When the diff value is less than 0xF,
what is the ACE37 form for it ?
>
When diff<=0x7F it will be in the 7bit
form, that is
<b4><b32>

the reason <b4> has to be used is that
it signifies how many more characters a
re used for the particular codepoint (or
what I termed as codepoint bracket).  If
only a <b32> is used, then you wont know
whether it is a 15 bit form or a 22 bit
form.
Therefore, if diff=0xF, ACE37=wf

> And any example C doe for ACE37  avai
lable on the web ?
>
Not yet, David & I will work on it and
post it on the web if more people are i
nterested in the idea and think that it
could be better than DUDE.  For now you
can check out my excel worksheet to see
how it works. http://www.dnsii.org/ace3
7/ace37-encode.xls (for encoding), http
://www.dnsii.org/ace37/ace37-decode.xls
(for decoding).

Edmon




> Thanks.
>
> Soobok
>
> > > >Chung & Leung
[Page 6]
> > > >ACE37       ACE Utilizing All 37
Alphanumeric Characters      July 2001
> > > >
> > > >    The following table explains
how base-4 characters are combined
> with
> > > >    base-32 characters to form a
representation of a diff (key:
> b4=base-
> > > >    4, b32=base-32):
> > > >
> > > >              diff value
|bits|       ACE37 Form
> > >
 >        -------------------------
|----|----------------------------
> > > >                  diff<=0x7F
|  7 | <b4><b32>
> > > >            0x80<=diff<=0x7FFF
| 15 | <b32><b32><b32>
> > > >          0x8000<=diff<=0x1FFFF
| 17 | w<b4><b32><b32><b32>
> > > >         0x20000<=diff<=0xFFFFF
| 20 | ww<b32><b32><b32><b32>
> > > >        0x100000<=diff<=0x10FFFF
| 22 | <b4>w<b32><b32><b32><b32>
> > > >
> > > >    Note that the "bits" column
represents the maximum number of
> > > >    significant bits for the giv
en diff value.  For example when
> > > >    diff<=0x7F, the maximum value
is 0b1111111, therefore the number of
>
>
> ----- Original Message -----
> From: "Edmon" <edmon@neteka.com>
> To: "Natalia Syracuse" <nsyracus@ietf
.org>; "David Leung"
> <david@neteka.com>; "Marc Blanchet" <
Marc.Blanchet@viagenie.qc.ca>;
> <idn@ops.ietf.org>
> Cc: <jseng@pobox.org.sg>
> Sent: Friday, July 06, 2001 12:48 AM
> Subject: [idn] Re: permission <draft-
ietf-idn-ace37-00.txt (attach)
>
>
> > Hi all,
> >
> > I was unaware that the workgroup no
longer accepts new drafts.  Anyway, I
> > have drafted a new ACE based on the
simplicity of DUDE which has hugely
> > improved compression.  Worst case s
cenario CJK could have 21 han
> characters!
> > Attached below is a copy of the dra
ft (for my original submission), you
> can
> > also find it at http://www.dnsii.or
g/idn-ace37-00.txt (easier to read) and
> > hopefully in the i-d-n.net website
soon.
> >
> > ACE37 is based on the one-pass one-
mode scheme of DUDE (diiferential XOR),
> > then utilizes a simple code block s
hifting (similar to the reference
> points
> > in the AMC series) to hugely increa
se the capacity for CJK (worst case
> > scenario 21 han characters!) and th
en utilizes base-32 for compression (as
> > in LACE) (DUDE and AMC-w/v uses bas
e-32 only for flagging).  In addition
> to
> > base-32, a base-4 scheme is introdu
ced by using the remaining characters
> > {wxyz}.  These contain 2 bits of ch
aracter information and doubles as an
> > indicator for codepoint brackets.
All the while, the algorithm is kept to
> > be as simple as DUDE.
> >
> > Hopefully you might find that it is
interesting and appropriate to be
> > considered as an ACE within the IET
F.  Afterall, it was intended to be an
> > integrated version of the three pri
mary ACEs: DUDE, LACE and the AMC
> series,
> > identified by the ACE design team r
eport.
> >
> > Looking forward to all your inputs.
> >
> > Edmon
>




From owner-idn@ops.ietf.org  Thu Jul  5 19:32:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA00102
	for <idn-archive@lists.ietf.org>; Thu, 5 Jul 2001 19:32:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IION-000216-00
	for idn-data@psg.com; Thu, 05 Jul 2001 16:18:39 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IION-000210-00
	for idn@ops.ietf.org; Thu, 05 Jul 2001 16:18:39 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15IIOL-0005wV-00; Thu, 05 Jul 2001 16:18:37 -0700
Date: Thu, 5 Jul 2001 23:18:37 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Re: permission <draft-ietf-idn-ace37-00.txt (attach)
Message-ID: <20010705231837.A22709@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <006601c10569$ffa20e00$1001a8c0@neteka.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Edmon <edmon@neteka.com> wrote:

> Worst case scenario CJK could have 21 han characters!

That's assuming the encoded string can be up to 63 octets.  For IDNA
the limit is 59 octets, in which case ACE37 can support up to 19 Han
characters, same as several other ACEs (but better than DUDE's 15).

But I'm pretty sure that ACE37 is less efficient than DUDE for all
non-CJK scripts.

> All the while, the algorithm is kept to be as simple as DUDE.

It doesn't look as simple as DUDE to me.  To me it looks no simpler than
AMC-ACE-W, which is as efficient as ACE37 for CJK, as efficient as DUDE
for single-row scripts, and more efficient than DUDE for Latin-based
scripts.  Whereas AMC-ACE-W's complexity is in a state machine, ACE37's
complexity is in encoding/recognizing lots of different patterns.  I
know nothing about Excel (and do not have it), but maybe patterns are
easier than state machines in Excel, and maybe ACE37 appears simpler
than AMC-ACE-W when both are implemented in Excel.

By the way, I'm now in the process of tweaking AMC-ACE-Z, which is as
simple as AMC-ACE-W (if not simpler) and also more efficient.  A draft
will be coming soon, along with an evaluation of many ACE proposals.
Edmon, if you'd like to provide me with a C implementation of ACE37, I
can include it in the evaluation.  You are welcome (and even encouraged)
to use my example implementation of DUDE as a template.

AMC



From owner-idn@ops.ietf.org  Fri Jul  6 02:46:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA21335
	for <idn-archive@lists.ietf.org>; Fri, 6 Jul 2001 02:46:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IP4q-000E2J-00
	for idn-data@psg.com; Thu, 05 Jul 2001 23:26:56 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IP4o-000E2C-00
	for idn@ops.ietf.org; Thu, 05 Jul 2001 23:26:54 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP id 31EC8FFC07
	for <idn@ops.ietf.org>; Fri,  6 Jul 2001 14:28:49 +0800 (SGT)
Message-ID: <05b201c105e4$96f18ea0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: <idn@ops.ietf.org>
Subject: [idn] Fw: Hello, This is KyungJae Park (KRNIC)
Date: Fri, 6 Jul 2001 14:26:28 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_05AF_01C10627.A4FC3D90"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_05AF_01C10627.A4FC3D90
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 8bit

forward as requested.

-James Seng

----- Original Message -----
From: "KJ,Park" <vpark@nic.or.kr>
To: "Jame.S" <James@Seng.cc>
Cc: "µµ±â¼ú" <domt@nic.or.kr>
Sent: Friday, July 06, 2001 12:52 PM
Subject: Hello, This is KyungJae Park (KRNIC)


> Dear James.
>
> I am sending you this mail hoping you do me a favor.
>
> I handed in an internet draft as an an individual submission.
> Because I am not a member of IDN WG, I hope you to post this draft to
IDN WG Mail-group.
>
> http://www.ietf.org/internet-drafts/draft-park-idn-ace-eval-kr-00.txt
>
> Thank you.
> Best regards,
>
>

------=_NextPart_000_05AF_01C10627.A4FC3D90
Content-Type: text/plain;
	name="draft-ieft-idn-ace-eval-kr-00.txt"
Content-Disposition: attachment;
	filename="draft-ieft-idn-ace-eval-kr-00.txt"
Content-Transfer-Encoding: quoted-printable

Internet Draft                          Chanki Park, KyungJae Park
draft-ietf-idn-ace-eval-kr-00.txt                           KRNIC
Jun 28, 2001
Expires Dec 28, 2001

     Evaluation of various ACEs with Hangeul Domain Names

Status of this memo

    This document is an Internet-Draft and is in full conformance with
    all provisions of Section 10 of RFC2026.

    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups. =20
    Note that other groups may also distribute working documents as=20
    Internet-Drafts.

    Internet-Drafts are draft documents valid for a maximum of six
    months and may be updated, replaced, or obsoleted by other=20
    documents at any time.  It is inappropriate to use =20
    Internet-Drafts as reference material or to cite them other than=20
    as "work in progress."

Abstract

    This document explains about result of applying various ACEs to ex
    isting Hangeul Domain Names and considers which ACE is appropriate
    to Hangeul Domain Names.


1. The test data composition

    The data for this ACE test consist of two lists.=20
      - 1000 Hageul domain names
      - 1000 real Korean company names.
      - 1000 web site names
      (Company Names and Web site names are very strong Hangeul=20
      Domain Name Candidates)
    =20
    Hangeul Domain Names consist of at least 2 characters
    Hangeul Domain Names Names may include letters, digits and=20
    hyphens, but at least 1 Hangeul character.
   =20
    The following result shows the distribution of Hangeul Domain=20
    Name length.
   =20
=0C
    Number of chars             Number of Hangeul Domain Names
    2 chars                                   271
    3 chars                                   336
    4 chars                                   550
    5 chars                                   373
    6 chars                                   333
    7 chars                                   210
    8 chars                                   215
    9 chars                                   157
    10 chars                                  137
    11 chars                                  98=20
    12 chars                                  91=20
    13 chars                                  59=20
    14 chars                                  54=20
    15 chars                                  28=20
    16 chars                                  29=20
    17 chars                                   15=20
    18 chars                                   6 =20
    19 chars                                   12=20
    20 chars                                   5 =20
    21 chars                                   5 =20
    22 chars                                   5 =20
    23 chars                                  2 =20
    24 chars                                   4 =20
    27 chars                                   2 =20
    29 chars                                   2 =20
    30 chars                                   1 =20
   =20
    We applied the following ACEs=20
   =20
    RACE-03, BRACE-00, LACE-01, UTF-6-00, DUDE-02, AMC-ACE-M-00,=20
    AltDUDE-01, AMC-ACE-O-00, AMC-ACE-R-01 with nameprep-03.
                                                  =20
    The input encoding method was Hangeul local encoding (EUC-KR).
                                                  =20
                                                  =20
2. ACEed Hangeul Domain Name Length
                                                  =20
    The following result shows the distribution of ACEed Hangeul=20
    Domain Name length.
                                                  =20
2.1 UTF6                                          =20

    Domain  ACEed  ACEed  ACEed
    Name    MAX     MIN      Average
    Length   Length  Length  Length
    2             8          6        7.95=20
=0C
    3             12         6        11.92
    4             16         12       15.99
    5             20         14       19.81
    6             24         16       23.78
    7             28         16       27.62
    8             32         20       31.67
    9             37         22       34.99
    10            41         24       39.5=20
    11            44         28       42.41
    12            48         30       46.36
    13            52         30       46.4=20
    14            56         32       52.91
    15            60         34       51.86
    16            64         38       58.18
    17            68         40       59.29
    18            72         38       56  =20
    19            76         50       66.5=20
    20            80         58       74.5=20
    21            84         50       65.6=20
    22            88         54       54.8=20
    23            84         60       63  =20
    24            96         60       69  =20
    27            62         60       61  =20
    29            84         66       75  =20
    30            74         74       74  =20


2.2 RACE
   =20
    Domain  ACEed  ACEed  ACEed
    Name    MAX     MIN      Average
    Length   Length  Length  Length
    2             8          5        7.88
    3             12         7        11.9
    4             15         15       15
    5             18         18       18
    6             21         21       21
    7             24         22       23.99
    8             29         28       28
    9             35         31       31.03
    10            38         34       34.09
    11            38         37       37.01
    12            40         40       40
    13            44         44       44
    14            48         47       47.02
    15            50         50       50
    16            57         53       53.14
=0C
    17            56         56       56
    18            60         58       59.67
    19            63         63       63
    20            66         66       66
    21            69         69       69
    22            88         54       63
    23            76         80       78
    24            79         82       79
    27            88         88       88
    29            95         95       95
    30            98         98       98
   =20
2.3 LACE
   =20
    Domain  ACEed  ACEed  ACEed
    Name    MAX     MIN      Average
    Length   Length  Length  Length
    2             8          7        7.96
    3             12         8        11.92
    4             15         13       15
    5             18         18       18
    6             21         20       20.99
    7             24         18       23.96
    8             29         23       27.96
    9             35         24       30.92
    10            38         26       34.03
    11            38         31       36.82
    12            40         32       39.76
    13            44         31       42.66
    14            48         32       46.34
    15            50         34       47.71
    16            57         39       52.18
    17            56         40       53.14
    18            60         39       51.5
    19            63         50       60.83
    20            66         64       65.5
    21            69         50       60.8
    22            72         55       53
    23            76         58       60.75
    24            79         60       66.25
    27            60         56       58
    29            95         66       80.5
    30            77         77       77
   =20
2.4 BRACE
   =20
    Domain  ACEed  ACEed  ACEed
=0C
    Name    MAX     MIN      Average
    Length   Length  Length  Length
    2             7          5        6.94
    3             10         7        9.9
    4             14         10       13.8
    5             17         11       16.81
    6             20         12       19.66
    7             25         12       22.62
    8             31         14       25.61
    9             32         15       28.93
    10            37         16       32.55
    11            40         20       34.54
    12            39         20       37.46
    13            42         19       37.12
    14            50         21       43.11
    15            49         22       40.57
    16            52         24       46.29
    17            55         25       46.36
    18            58         24       42
    19            62         34       52.5
    20            65         41       59
    21            68         33       48.8
    22            71         35       40.6
    23            68         39       45.25
    24            78         38       49.5
    27            38         35       36.5
    29            61         42       51.5
    30            49         49       49

2.5 DUDE

    Domain  ACEed  ACEed  ACEed
    Name    MAX     MIN      Average
    Length   Length  Length  Length
    2             8          5        7.6
    3             12         6        11.22
    4             16         11       14.93
    5             20         14       18.36
    6             24         14       21.81
    7             28         15       25.54
    8             32         16       29.15
    9             36         17       32.28
    10            40         19       36.23
    11            44         21       38.89
    12            48         25       42.57
    13            51         24       42.83
    14            55         28       48.72
=0C
    15            60         27       47.36
    16            63         33       53.68
    17            65         34       54.36
    18            68         35       50.67
    19            72         43       60.5
    20            80         54       68
    21            78         41       57
    22            85         46       49.4
    23            76         50       56.25
    24            89         51       61
    27            53         45       49
    29            75         53       64
    30            58         58       58

2.6 AltDUDE

    Domain  ACEed  ACEed  ACEed
    Name    MAX     MIN      Average
    Length   Length  Length  Length
    2             8           5        7.6
    3             12          6        11.22
    4             16          11       14.93
    5             20          14       18.36
    6             24          14       21.8
    7             28          14       25.52
    8             32          15       29.14
    9             36          16       32.25
    10            40          19       36.22
    11            44          20       38.81
    12            48          25       42.55
    13            51          24       42.72
    14            55          28       48.68
    15            60          26       47.11
    16            63          32       53.64
    17            65          34       54.21
    18            68          34       50.5
    19            72          43       60.42
    20            80          54       68
    21            78          41       57
    22            85          46       49.4
    23            76          50       56.25
    24            89          51       60.5
    27            53          45       49
    29            75          52       63.5
    30            58          58       58

=0C
2.7 AMC-ACE-M

    Domain  ACEed  ACEed  ACEed
    Name    MAX     MIN      Average
    Length   Length  Length  Length
    2             8            5         7.6
    3             11           6         10.73
    4             14           10        13.72
    5             17           11        16.38
    6             20           12        19.12
    7             25           12        22.01
    8             34           14        26.08
    9             33           15        27.26
    10            39           16        30.59
    11            42           20        32.54
    12            37           21        35.29
    13            41           20        35.47
    14            49           22        40.36
    15            46           22        38.29
    16            49           25        43.75
    17            52           26        43.64
    18            55           24        40.33
    19            57           33        49.42
    20            60           39        54.5
    21            63           33        46.6
    22            66           35        39.6
    23            62           38        44
    24            72           38        47.75
    27            38           36        37
    29            58           42        50
    30            48           48        48

2.8 AMC-ACE-O

    Domain  ACEed  ACEed  ACEed
    Name    MAX     MIN      Average
    Length   Length  Length  Length
    2             8            5         7.6
    3             12           6         11.01
    4             16           10        14.4
    5             19           11        17.29
    6             23           12        20.3
    7             27           12        23.64
    8             34           14        26.13
    9             34           15        28.97
    10            42           16        32.53
    11            45           20        34.75
=0C
    12            43           21        37.66
    13            48           20        38.16
    14            52           22        43.83
    15            53           22        41.29
    16            57           25        46.54
    17            59           26        46.5
    18            59           24        42.67
    19            64           34        53.58
    20            69           39        56.75
    21            73           33        49.8
    22            78           37        43.2
    23            67           39        48.5
    24            81           39        50.75
    27            39           36        37.5
    29            62           42        52
    30            48           48        48

2.9 AMC-ACE-R

    Domain  ACEed  ACEed  ACEed
    Name    MAX     MIN      Average
    Length   Length  Length  Length
    2             8            5          7.6
    3             12           6          11.22
    4             16           10         14.94
    5             20           11         18.18
    6             24           12         21.53
    7             28           12         25.22
    8             32           14         28.35
    9             36           15         31.48
    10            40           16         35.15
    11            44           21         37.82
    12            48           21         40.96
    13            50           20         40.98
    14            55           22         46.87
    15            59           23         44.82
    16            62           25         49.82
    17            63           27         49.57
    18            65           24         45
    19            68           35         56.42
    20            72           40         61.5
    21            77           34         53
    22            82           38         44.6
    23            74           40         50.25
    24            90           39         54.25
    27            39           36         37.5
    29            66           43         54.5
=0C
    30            51           51         51



3. Conversion Speed

    The following result shows the ACE Conversion speed
   =20
     UTF6 RACE LACE BRACE DUDE ALTDUDE AMC-ACE-M AMC-ACE-O AMC-ACE-R
  MAX 0.46 0.49 0.49 0.60 0.62 0.49    0.43      0.45      0.56
  MIN 0.12 0.12 0.14 0.13 0.12 0.12    0.14      0.15      0.14
  AVR 0.147 0.151 0.153 0.1510.148 0.143 0.161   0.19      0.152
   =20


4. The summary of result=20
   =20
    4-1 ACEed Hangeul Domain Name Length
   =20
     - The Maximum length of Hangeul Domain Name before the conversion
      UTF-6 RACE LACE BRACE DUDE AltDUDE AMC-ACE-M AMC-ACE-O AMC-ACE-R
       14   17   17    17    14    14      19         18       15
   =20
      - Good : AME-ACE-M, AMC-ACE-O
      - Bad   : UTF6, DUDE(AltDUDE)
     =20
    4-2 Conversion Speed
      - Good : AltDUDE, DUDE
      - Bad   : AMC-ACE-O, AMC-ACE-M
     =20
      =20
 =20
5. Conclusion

   For Hangeul Domain Name, AME-ACE-M seems to be the best choice,=20
   if we think the length is more important than the conversion speed.
  DUDE may be a good choice if the ACEed length of Hangeul Domain Name
   can be shortened.



6. References

    [MDNKIT]   "Multilingual Domain Name tool Kit",
                http://www.nic.ad.jp/jp/research/idn/mdnkit/download/
    [RFC1035]  "DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION",=20
                RFC1034, Nov 1987, P. Mockapetris=20
=0C
    [NAMEPREP] "Preparation of Internationalized Host Names",
                draft-ietf-idn-nameprep-03.txt, Feb 2001, P Hoffman
                , M Blanchet
    [RACE]     "RACE: Row-based ASCII Compatible Encoding for IDN",
               draft-ietf-idn-race-03.txt, Nov 2000, P Hoffman
    [BRACE]    "BRACE: Bi-mode Row-based ASCII-Compatible Encoding=20
               for IDN version 0.1.2"                               =20
               draft-ietf-idn-brace-00.txti, Sep 2000, A Costello
    [LACE]     "LACE: Length-based ASCII Compatible Encoding for IDN"
              draft-ietf-idn-lace-01.txt, Jan 2001, M Davis, P Hoffman
    [UTF6]     "UTF-6 - Yet Another ASCII-Compatible Encoding for IDN"
               draft-ietf-idn-utf6-00, Nov 2000, M Welter, B Spolarich
    [DUDE]     "Differential Unicode Domain Encoding (DUDE)"
               draft-ietf-idn-dude-02.txt, Jun 2001, M Welter,=20
               B Spolarich, A Costello
    [AMCACEM]  "AMC-ACE-M version 0.1.0"=20
               draft-ietf-idn-amc-ace-m-00.txt, Feb 2001, A Costello
    [AltDUDE]  "AltDUDE version 0.0.2"
               draft-ietf-idn-altdude-00.txt, Mar 2001, A Costello
    [AMCACEO]  "AMC-ACE-O version 0.0.3"
               draft-ietf-idn-amc-ace-o-00.txt, Mar 2001, A Costello
    [AMCACER]  "AMC-ACE-R version 0.2.1"
               draft-ietf-idn-amc-ace-r-01.txt, May 2001, A Costello



7. Acknowledgements                                                    =20

    This ACE evaluation testing tool was provided by JPNIC.=20
                                                                       =20


8. Author's Address                                                    =20

    Chanki Park  ckp@nic.or.kr
    KyungJae Park vpark@nic.or.kr
    Korea Network Information Center                                   =20
    Nara Bldg 14F, 1328-3Bunji Seocho 2 Dong Seochogu Seoul, S.Korea.

------=_NextPart_000_05AF_01C10627.A4FC3D90--




From owner-idn@ops.ietf.org  Fri Jul  6 07:10:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA26796
	for <idn-archive@lists.ietf.org>; Fri, 6 Jul 2001 07:10:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15ITCf-000LPi-00
	for idn-data@psg.com; Fri, 06 Jul 2001 03:51:17 -0700
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15ITCe-000LPb-00
	for idn@ops.ietf.org; Fri, 06 Jul 2001 03:51:16 -0700
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25875;
	Fri, 6 Jul 2001 06:50:29 -0400 (EDT)
Message-Id: <200107061050.GAA25875@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: idn@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [idn] I-D ACTION:draft-chung-idn-ace37-00.txt
Date: Fri, 06 Jul 2001 06:50:28 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: ACE Utilizing All 37 Alphanumeric Characters (ACE37)
	Author(s)	: E. Chung, D. Leung
	Filename	: draft-chung-idn-ace37-00.txt
	Pages		: 17
	Date		: 05-Jul-01
	
ACE37 is a combination of DUDE-02, AMC-W/V and LACE.  ACE37 utilizes 
the simple one pass algorithm of DUDE, the character block 
considerations of AMC-W/V and the Base-32 compression of LACE.  It 
also fully utilizes entire LDH set currently allowed in the DNS (A-
z, 0-9 and '-') within its character repertoire to optimize 
performance and compression.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-chung-idn-ace37-00.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-chung-idn-ace37-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-chung-idn-ace37-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010705113846.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-chung-idn-ace37-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-chung-idn-ace37-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010705113846.I-D@ietf.org>

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Fri Jul  6 07:50:06 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA27777
	for <idn-archive@lists.ietf.org>; Fri, 6 Jul 2001 07:50:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15ITpY-000Mmj-00
	for idn-data@psg.com; Fri, 06 Jul 2001 04:31:28 -0700
Received: from 217-13-28-204.dd.nextgentel.com ([217.13.28.204] helo=eikenes.alvestrand.no)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15ITpX-000MmS-00
	for idn@ops.ietf.org; Fri, 06 Jul 2001 04:31:27 -0700
Received: from [192.168.1.31] (eikenes.alvestrand.no [217.13.28.203])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 87FB962202; Fri,  6 Jul 2001 13:30:16 +0200 (CEST)
Date: Fri, 06 Jul 2001 13:30:23 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: "James Seng/Personal" <James@Seng.cc>, idn@ops.ietf.org
Subject: Re: [idn] Fw: Hello, This is KyungJae Park (KRNIC)
Message-ID: <759999481.994426223@[192.168.1.31]>
In-Reply-To: <05b201c105e4$96f18ea0$dd00a8c0@jamessonyvaio>
References:  <05b201c105e4$96f18ea0$dd00a8c0@jamessonyvaio>
X-Mailer: Mulberry/2.1.0b1 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

this points to a very interesting property of the ACEs:
the upper limit on length is not a fixed value, it depends on the character 
values used, even within a single script.

For ams-ace-m:
  len          maxlen enc    minlen enc  average
    22            66           35        39.6

so most of the 5 Hangul names of length 22 are acceptable, but some are not.

This will be fun to explain to customers.....




From owner-idn@ops.ietf.org  Fri Jul  6 11:00:44 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA06416
	for <idn-archive@lists.ietf.org>; Fri, 6 Jul 2001 11:00:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IWwU-0002vT-00
	for idn-data@psg.com; Fri, 06 Jul 2001 07:50:50 -0700
Received: from pc-62-30-167-16-ca.blueyonder.co.uk ([62.30.167.16] helo=NEXUS.replicants.org.uk)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IWwT-0002td-00
	for idn@ops.ietf.org; Fri, 06 Jul 2001 07:50:49 -0700
Received: from mail pickup service by NEXUS.replicants.org.uk with Microsoft SMTPSVC;
	 Fri, 6 Jul 2001 15:54:50 +0100
X-From_: ietf-123-owner@loki.ietf.org Fri Jul 06 13:58:29 2001
Received: from [132.151.1.177] (helo=loki.ietf.org)	by mail8.svr.pol.co.uk with esmtp (Exim 3.13 #0)	id 15IVBl-0000ca-00; Fri, 06 Jul 2001 13:58:29 +0100
Received: (from adm@localhost)	by loki.ietf.org (8.9.1b+Sun/8.9.1) id IAA24317	for ietf-123-outbound.10@ietf.org; Fri, 6 Jul 2001 08:05:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id GAA23670	for <all-ietf@loki.ietf.org>; Fri, 6 Jul 2001 06:50:31 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25875;	Fri, 6 Jul 2001 06:50:29 -0400 (EDT)
Message-Id: <200107061050.GAA25875@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: idn@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [idn] I-D ACTION:draft-chung-idn-ace37-00.txt
Date: Fri, 06 Jul 2001 06:50:28 -0400
X-OriginalArrivalTime: 06 Jul 2001 14:54:50.0487 (UTC) FILETIME=[9B796870:01C1062B]
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: ACE Utilizing All 37 Alphanumeric Characters (ACE37)
	Author(s)	: E. Chung, D. Leung
	Filename	: draft-chung-idn-ace37-00.txt
	Pages		: 17
	Date		: 05-Jul-01
	
ACE37 is a combination of DUDE-02, AMC-W/V and LACE.  ACE37 utilizes 
the simple one pass algorithm of DUDE, the character block 
considerations of AMC-W/V and the Base-32 compression of LACE.  It 
also fully utilizes entire LDH set currently allowed in the DNS (A-
z, 0-9 and '-') within its character repertoire to optimize 
performance and compression.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-chung-idn-ace37-00.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-chung-idn-ace37-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-chung-idn-ace37-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010705113846.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-chung-idn-ace37-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-chung-idn-ace37-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"


--OtherAccess--
--NextPart--


From owner-idn@ops.ietf.org  Fri Jul  6 11:06:27 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA06769
	for <idn-archive@lists.ietf.org>; Fri, 6 Jul 2001 11:06:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IX1N-00037c-00
	for idn-data@psg.com; Fri, 06 Jul 2001 07:55:53 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IX1M-00037N-00
	for idn@ops.ietf.org; Fri, 06 Jul 2001 07:55:52 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id XAA26097;
	Fri, 6 Jul 2001 23:55:19 +0900
Message-ID: <005101c1062b$04b07c80$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Harald Tveit Alvestrand" <harald@alvestrand.no>, <idn@ops.ietf.org>
References:  <05b201c105e4$96f18ea0$dd00a8c0@jamessonyvaio> <759999481.994426223@[192.168.1.31]>
Subject: [idn] Analysis : maximum length of hangul/han domains
Date: Fri, 6 Jul 2001 23:50:37 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Even in DUDE,  the  max length of hangul domain label can be  56
(first  <4*base32> + 55 <1*base32>s = 59 octets = 63 - 4 (prefix) ),
 if we form a hangul domain label with hangul syllables
only from U+B000~U+B00F, because their XOR diff values are always less than
0x10.

If we form a hangul domain label with hangul syllables
only from U+B000~U+B0FF (256).  Their XOR diff values are always less than
0x100,
and in the worst case, the maximum length is 28  (first  <4*base32> + 27
<2*base32>s = 58).

If we form a hangul domain label with hangul syllables
only from U+B000~U+BFFF (4096).  Their XOR diff values are always less than
0x1000,
and in the worst case, the maximum length is 19  (first  <4*base32> + 18
<3*base32>s = 58).

If we form a hangul domain label with hangul syllables
from entire hangul code range U+AC00~U+D7AF.
Their XOR diff values are sometimes greater than 0x1000,
and in the worst case, the maximum length is 14  (first  <4*base32> + 13
<4*base32>s = 56).

My frequency&adjacency-based codepoint reordering is based on this analysis.

If you gather(really map) most frequent 256 and 4096 hangul  code points to
aligned blocks of
256 and 4096 code points starting from 0xB000,
 we can express most modern typical hangul domains with hangul syllables
mainly from the inner 256 codes block (~ 0xB0FF)
and occasionally from the outer 4096 codes block ( ~ 0xBFFF).

In this case, the max length of a hangul domain varies between 19 ~ 28
depending upon
how many deviations from top freq 256 hangul syllables  occur in the domain
label.
In my study on samples of typical hangul business names,
the averaged percentage of deviations does not exceed 20~30%.
I guess that the averaged maximum length of hangul domains is around  25
for both 'reordered' DUDE and 'reordered' AMC-ACE-W.
This reordering can be implemented only with code mapping tables which
are much smaller than those for KC norm and NAMEPREP.

This analysis works for Unified Han code range for which the averaged
maximum length seems to be around 22 slightly less than that for hangul.

If you want to read more about this topic,  go
 http://www.postel.co.kr/lsb-ace-01.txt
This is the new version of my draft.

Soobok Lee

----- Original Message -----
From: "Harald Tveit Alvestrand" <harald@alvestrand.no>
To: "James Seng/Personal" <James@Seng.cc>; <idn@ops.ietf.org>
Sent: Friday, July 06, 2001 8:30 PM
Subject: Re: [idn] Fw: Hello, This is KyungJae Park (KRNIC)


> this points to a very interesting property of the ACEs:
> the upper limit on length is not a fixed value, it depends on the character
> values used, even within a single script.
>
> For ams-ace-m:
>   len          maxlen enc    minlen enc  average
>     22            66           35        39.6
>
> so most of the 5 Hangul names of length 22 are acceptable, but some are not.
>
> This will be fun to explain to customers.....
>
>




From owner-idn@ops.ietf.org  Fri Jul  6 12:02:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA09935
	for <idn-archive@lists.ietf.org>; Fri, 6 Jul 2001 12:02:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IXs2-0004xW-00
	for idn-data@psg.com; Fri, 06 Jul 2001 08:50:18 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15IXs1-0004xQ-00
	for idn@ops.ietf.org; Fri, 06 Jul 2001 08:50:17 -0700
Message-ID: <002201c10634$0051a020$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: <idn@ops.ietf.org>, "Adam M. Costello" <amc@cs.berkeley.edu>
References: <20010705231837.A22709@arwen.cs.berkeley.edu>
Subject: Re: [idn] Re: permission <draft-ietf-idn-ace37-00.txt (attach)
Date: Fri, 6 Jul 2001 11:54:53 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Edmon <edmon@neteka.com> wrote:
>
> > Worst case scenario CJK could have 21 han characters!
>
> That's assuming the encoded string can be up to 63 octets.  For IDNA
> the limit is 59 octets, in which case ACE37 can support up to 19 Han
> characters, same as several other ACEs (but better than DUDE's 15).

DUDE's support for 15 characters is also based on 63 octets. It would be 14
if it is 59 octets.

>
> But I'm pretty sure that ACE37 is less efficient than DUDE for all
> non-CJK scripts.
>

Yup, there is a trade off definitely.  However, it seems that the CJK
community is more concerned about the issue so we should take this into
consideration when striking a balance.

> > All the while, the algorithm is kept to be as simple as DUDE.
>
> It doesn't look as simple as DUDE to me.  To me it looks no simpler than
> AMC-ACE-W, which is as efficient as ACE37 for CJK

AMC-ACE-W will not always achieve 19 characters with the 4 extra charcters
in front, whereas ACE37 will.

> Whereas AMC-ACE-W's complexity is in a state machine, ACE37's
> complexity is in encoding/recognizing lots of different patterns.  I

True to an extent, but ACE37 operates under the same mode throughout,
similar to the DUDE concept.

>
> By the way, I'm now in the process of tweaking AMC-ACE-Z, which is as
> simple as AMC-ACE-W (if not simpler) and also more efficient.  A draft
> will be coming soon, along with an evaluation of many ACE proposals.
> Edmon, if you'd like to provide me with a C implementation of ACE37, I
> can include it in the evaluation.  You are welcome (and even encouraged)
> to use my example implementation of DUDE as a template.
>

Will do so asap.

> AMC

Edmon




From owner-idn@ops.ietf.org  Fri Jul  6 12:17:38 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA10789
	for <idn-archive@lists.ietf.org>; Fri, 6 Jul 2001 12:17:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IYBU-0005ZV-00
	for idn-data@psg.com; Fri, 06 Jul 2001 09:10:24 -0700
Received: from beatles.cselt.it ([163.162.29.125])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IYBS-0005Z7-00
	for idn@ops.ietf.org; Fri, 06 Jul 2001 09:10:23 -0700
Received: from beatles (beatles [163.162.29.125])
	by beatles.cselt.it (8.9.3/8.9.3) with SMTP id SAA07166
	for <idn@ops.ietf.org>; Fri, 6 Jul 2001 18:07:52 +0200 (MEST)
Date: Fri, 6 Jul 2001 18:07:52 +0200
From: Maurizio Codogno <mau@beatles.cselt.it>
To: idn@ops.ietf.org
Subject: [idn] efficiency of codings
Message-Id: <20010706180752.17493d19.mau@beatles.cselt.it>
In-Reply-To: <002201c10634$0051a020$1001a8c0@neteka.com>
References: <20010705231837.A22709@arwen.cs.berkeley.edu>
	<002201c10634$0051a020$1001a8c0@neteka.com>
Organization: Telecom Italia Lab
X-Mailer: Sylpheed version 0.5.0 (GTK+ 1.2.8; sparc-sun-solaris2.8)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In die Fri, 6 Jul 2001 11:54:53 -0400
"Edmon" <edmon@neteka.com> scripsit:


> DUDE's support for 15 characters is also based on 63 octets. It would be 14
> if it is 59 octets.
> 
> >
> > But I'm pretty sure that ACE37 is less efficient than DUDE for all
> > non-CJK scripts.
> >
> 
> Yup, there is a trade off definitely.  However, it seems that the CJK
> community is more concerned about the issue so we should take this into
> consideration when striking a balance.

Given that we may spare two strings to indicate ACE, would it be feasible
to use one for CJK scripts and another for the other scripts, making it 
impossible to use the wrong coding (this is necessary to assure unique 
labels), or do you think it is too complicated?

ciao, .mau.



From owner-idn@ops.ietf.org  Fri Jul  6 13:37:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA13903
	for <idn-archive@lists.ietf.org>; Fri, 6 Jul 2001 13:37:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IZNX-0008BS-00
	for idn-data@psg.com; Fri, 06 Jul 2001 10:26:55 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IZNV-0008BL-00
	for idn@ops.ietf.org; Fri, 06 Jul 2001 10:26:54 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id CAA07895
	for <idn@ops.ietf.org>; Sat, 7 Jul 2001 02:26:40 +0900
Message-ID: <00d401c10640$254d96c0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
References: <200107061050.GAA25875@ietf.org>
Subject: [idn] ACE37,AMCW and LDUDE
Date: Sat, 7 Jul 2001 02:21:51 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I compared ACE37 with my LDUDE (reordered DUDE).

LDUDE's reordering mapping tables  are tuned to produce
as many single-quintet-XOR- diff values as possible
based on character & adjacency statistics.

If we apply reordering to ACE37, we can improve ACE37.

However, if reordering applied to ACE37 become MOST successful,
ACE37 should support  single quintet XOR difference when encoding,
that ACE37 does not support now.

Reordering  already statistically  guarantees XOR diff values less than
0x1000 for Han, by mapping most frequent 4096 han letters into 4096
codes block starting from 0x5000. Most freq 4096 han letters
( in about 23000 han letters  )  have cumulative frequency sum
of 99.9% in typical chinese texts and business names.
(for top 256, 58% )

LDUDE compresses the next 25 letters of Japanese strings down to 47
chars of ACE labels, 10 chars shorter than that of AMCW and ACE37.


JP1) Japanese String 1: ( 25 letters )
      U+793E U+56E3 U+6CD5 U+4EBA U+65E5 U+672C U+30CD U+30C3 U+30C8
      U+30EF U+30FC U+30AF U+30A4 U+30F3 U+30D5 U+30A9 U+30E1 U+30FC
      U+30B7 U+30E7 U+30F3 U+30BB U+30F3 U+30BF U+30FC

      DUDE-02 : z3xQu97Pv4vGuuyRu5xRu6Jxz8BQMuHtDxDMxHuGzNwItPwMxAtE\
                wIwIwNwD  (60 chars)
      LDUDE   : xs8Nu2Cu4RvMGBysxGyCKtHtQCPFtAyPyKtPBGPyAyAyFyR
                ( 47 chars, 21.6% shorter)
      AMCW    : z3vQ28DDyxs5KB9fCjnvs6P6DI8R9N4RE9D7F4J8B9N5H8H9D5M9\
                D5R9N ( 57 chars )
      LAMCW   : xs2NwsQu4B3KNPvs6M4JD5E4KIFA5A7P5H4KMPA6A4A6F4K
                ( 47 chars )

      ACE37: i9urut6hm8jfaqv0m9dv1wewbx7wjyjwbynx6zsy8wtybygwky8y8ycy3
                (57 char)

     JP3) Japanese String 3: ( 17 letters )
      U+6771 U+4EAC U+90FD U+60C5 U+5831 U+30B5 U+30FC U+30D3 U+30B9
      U+7523 U+696D U+5065 U+5EB7 U+4FDD U+967A U+7D44 U+5408

      DUDE-02 : yztBu37P78xB9svIv29Ey22EwJuRyKwx3Kt6wQv3sI87CttyK734\
                H85vQu3wN (61 chars)
      LDUDE   : xttHxPvtFu9CDyssAyEyHyRys9PxQ4KHGEu4CuwJ
                ( 40 chars, 34.4% shorter)
      AMCW    : z3vQ28DDyxs5KB9fCjnvs6P6DI8R9N4RE9D7F4J8B9N5H8H9D5M9\
                D5R9N ( 57 chars )
      LAMCW   : xs2NwsQu4B3KNPvs6M4JD5E4KIFA5A7P5H4KMPA6A4A6F4K
                ( 47 chars )

      ACE37: drhaetvihk1o67ka44y9xfzahcqv2e6883micbaud7apuqac (48 char)


Soobok Lee, lsb@postel.co.kr


> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
>
>
> Title : ACE Utilizing All 37 Alphanumeric Characters (ACE37)
> Author(s) : E. Chung, D. Leung
> Filename : draft-chung-idn-ace37-00.txt
> Pages : 17
> Date : 05-Jul-01
>
> ACE37 is a combination of DUDE-02, AMC-W/V and LACE.  ACE37 utilizes
> the simple one pass algorithm of DUDE, the character block
> considerations of AMC-W/V and the Base-32 compression of LACE.  It
> also fully utilizes entire LDH set currently allowed in the DNS (A-
> z, 0-9 and '-') within its character repertoire to optimize
> performance and compression.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-chung-idn-ace37-00.txt
>





From owner-idn@ops.ietf.org  Fri Jul  6 14:01:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA14617
	for <idn-archive@lists.ietf.org>; Fri, 6 Jul 2001 14:01:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IZn5-00095L-00
	for idn-data@psg.com; Fri, 06 Jul 2001 10:53:19 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IZn4-00095F-00
	for idn@ops.ietf.org; Fri, 06 Jul 2001 10:53:18 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA02764;
        Fri, 6 Jul 2001 13:53:05 -0400 (EDT)
Message-Id: <200107061753.NAA02764@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Soobok Lee" <lsb@postel.co.kr>
cc: idn@ops.ietf.org
Subject: Re: [idn] ACE37,AMCW and LDUDE 
In-reply-to: Your message of "Sat, 07 Jul 2001 02:21:51 +0900."
             <00d401c10640$254d96c0$ec1bd9d2@temp> 
Date: Fri, 06 Jul 2001 13:53:05 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I would *really* like to avoid complex reordering of codepoints, because
it would require fairly large tables (that would have to be implemented
on some machines of modest capability) and would be error-prone.  

I also fear that this kind of mapping would encourage greater use
of proxies over end-to-end implementations, with all of the implications
for reliability, control, delay, etc. that would result from this design 
choice.  I don't think we want to encourage a walled garden.

I could see having a very simple reordering of codepoints in order
to increase the efficiency of DUDE for ideographic languages.  But my
(admittedly biased) sense is that we're fast approaching the point
of diminishing returns.  Just how important is it to provide for names 
that are one or two ideographs longer?

Keith



From owner-idn@ops.ietf.org  Fri Jul  6 17:13:17 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA20176
	for <idn-archive@lists.ietf.org>; Fri, 6 Jul 2001 17:13:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IcdM-000EXn-00
	for idn-data@psg.com; Fri, 06 Jul 2001 13:55:28 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15IcdL-000EXU-00
	for idn@ops.ietf.org; Fri, 06 Jul 2001 13:55:27 -0700
Message-ID: <00cf01c1065e$9975a100$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: "Keith Moore" <moore@cs.utk.edu>, "Soobok Lee" <lsb@postel.co.kr>
Cc: <idn@ops.ietf.org>
References: <200107061753.NAA02764@astro.cs.utk.edu>
Subject: Re: [idn] ACE37,AMCW and LDUDE 
Date: Fri, 6 Jul 2001 16:59:49 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I would *really* like to avoid complex reordering of codepoints, because
> it would require fairly large tables (that would have to be implemented
> on some machines of modest capability) and would be error-prone.
>
I agree.  The code block shifting mechanism in ACE37 however is very simple
and yeilds great benefit for CJK ideographs.

> I could see having a very simple reordering of codepoints in order
> to increase the efficiency of DUDE for ideographic languages.  But my
> (admittedly biased) sense is that we're fast approaching the point
> of diminishing returns.  Just how important is it to provide for names
> that are one or two ideographs longer?

It is more than one or two... in the worst case scenario for CJK, ACE37 out
performs DUDE by 5 characters!
And there is an undeniable demand from the CJK community to up the 14
character limit to at least, I guess close to the original 23 character
limit.

>
> Keith

Edmon





From owner-idn@ops.ietf.org  Fri Jul  6 18:23:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA21930
	for <idn-archive@lists.ietf.org>; Fri, 6 Jul 2001 18:23:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IdqV-000GlL-00
	for idn-data@psg.com; Fri, 06 Jul 2001 15:13:07 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IdqV-000GlF-00
	for idn@ops.ietf.org; Fri, 06 Jul 2001 15:13:07 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15IdqU-0002tk-00; Fri, 06 Jul 2001 15:13:06 -0700
Date: Fri, 6 Jul 2001 22:13:06 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Re: permission <draft-ietf-idn-ace37-00.txt (attach)
Message-ID: <20010706221305.A11087@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <002201c10634$0051a020$1001a8c0@neteka.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Edmon <edmon@neteka.com> wrote:

> DUDE's support for 15 characters is also based on 63 octets. It would
> be 14 if it is 59 octets.

I was basing it on 59 octets.  In the worst case, DUDE would require
60 octets for 15 Han characters, but the worst case virtually never
happens.  In the thousands of names that JPNIC tried, it never happened.
59 octets happened a few times, but I think the typical length was 58 or
57.  So DUDE can almost always support 15 characters, but usually cannot
support 16.  I think the boundary between "usually fits" and "usually
fails" is more useful than the "always fits" number.

AMC



From owner-idn@ops.ietf.org  Fri Jul  6 19:18:56 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA23198
	for <idn-archive@lists.ietf.org>; Fri, 6 Jul 2001 19:18:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IejT-000IbL-00
	for idn-data@psg.com; Fri, 06 Jul 2001 16:09:55 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IejS-000IbE-00
	for idn@ops.ietf.org; Fri, 06 Jul 2001 16:09:54 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f66N9eT05091;
	Sat, 7 Jul 2001 08:09:41 +0900 (KST)
Message-ID: <000e01c10671$6df30a00$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: <idn@ops.ietf.org>
References: <200107061753.NAA02764@astro.cs.utk.edu>
Subject: Re: [idn] ACE37,AMCW and LDUDE 
Date: Sat, 7 Jul 2001 08:14:37 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message ----- 
From: "Keith Moore" <moore@cs.utk.edu>
 

> I would *really* like to avoid complex reordering of codepoints, because
> it would require fairly large tables (that would have to be implemented
> on some machines of modest capability) and would be error-prone.  
> 

It's not complex.
Its table is not so large compared to that of KC norm and
NAMEPREP. ACE & NAMEPREP will be packaged into one library
as MDNkit of JPNIC. Look into KC norm and NAMEPREP tables and
think about the reordering table, more simpler. 

Reordering reduce the length typical ACE label about 40% ~ 50%.
Please throughly test my example sources with average length of
han/hangul domains. 

> I also fear that this kind of mapping would encourage greater use
> of proxies over end-to-end implementations, with all of the implications
> for reliability, control, delay, etc. that would result from this design 
> choice.  I don't think we want to encourage a walled garden.

No proxies needed. No walls. 
All reordering is hidden and done in ACE & de-ACE libraries transparently.

No delay at all. Because what is needed is "n=maptable[n]" operation.
Single machine instruction away!!!
What i implemented in my example source is using mapping functions
with tables. IN the final version, we can use only tables.

> 
> I could see having a very simple reordering of codepoints in order
> to increase the efficiency of DUDE for ideographic languages.  But my
> (admittedly biased) sense is that we're fast approaching the point
> of diminishing returns.  Just how important is it to provide for names 
> that are one or two ideographs longer?
> 
> Keith
> 

With DUDE+REORDERING , we get 7~8 more Han ideographs. 
If you have enough time, test with many han examples.

code-block shifting does not help to reduce average XOR distance
in general cases ( good only for the first 4096 code block ).

What is important is  to reduce ACE label length of AVERAGED 
han/hangul domains. THis working group should concentrage
attentions  not to the max length issue but to  issues of
reducing ACE label length of average hangul/han domains.

Soobok Lee








From owner-idn@ops.ietf.org  Fri Jul  6 19:53:12 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA23946
	for <idn-archive@lists.ietf.org>; Fri, 6 Jul 2001 19:53:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IfII-000Jj7-00
	for idn-data@psg.com; Fri, 06 Jul 2001 16:45:54 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IfIG-000Jip-00
	for idn@ops.ietf.org; Fri, 06 Jul 2001 16:45:52 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f66NjhT12681;
	Sat, 7 Jul 2001 08:45:44 +0900 (KST)
Message-ID: <002801c10676$755fba40$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>, "Keith Moore" <moore@cs.utk.edu>
Cc: <idn@ops.ietf.org>
References: <200107061753.NAA02764@astro.cs.utk.edu> <000e01c10671$6df30a00$ed1bd9d2@postel.co.kr>
Subject: Re: [idn] ACE37,AMCW and LDUDE 
Date: Sat, 7 Jul 2001 08:50:38 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

If you tested with my old reordering I-D version 0.9:
 You'd better try with my newly submitted I-D version 1.0 at
  http://www.postel.co.kr/lsb-ace-01.txt

 it contains many examples for CJK.
 40~50% shorter ACE labels are produced!

 It does better compression for European
 domains, too.

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: <idn@ops.ietf.org>
Sent: Saturday, July 07, 2001 8:14 AM
Subject: Re: [idn] ACE37,AMCW and LDUDE


>
> ----- Original Message -----
> From: "Keith Moore" <moore@cs.utk.edu>
>
>
> > I would *really* like to avoid complex reordering of codepoints, because
> > it would require fairly large tables (that would have to be implemented
> > on some machines of modest capability) and would be error-prone.
> >
>
> It's not complex.
> Its table is not so large compared to that of KC norm and
> NAMEPREP. ACE & NAMEPREP will be packaged into one library
> as MDNkit of JPNIC. Look into KC norm and NAMEPREP tables and
> think about the reordering table, more simpler.
>
> Reordering reduce the length typical ACE label about 40% ~ 50%.
> Please throughly test my example sources with average length of
> han/hangul domains.
>
> > I also fear that this kind of mapping would encourage greater use
> > of proxies over end-to-end implementations, with all of the implications
> > for reliability, control, delay, etc. that would result from this design
> > choice.  I don't think we want to encourage a walled garden.
>
> No proxies needed. No walls.
> All reordering is hidden and done in ACE & de-ACE libraries transparently.
>
> No delay at all. Because what is needed is "n=maptable[n]" operation.
> Single machine instruction away!!!
> What i implemented in my example source is using mapping functions
> with tables. IN the final version, we can use only tables.
>
> >
> > I could see having a very simple reordering of codepoints in order
> > to increase the efficiency of DUDE for ideographic languages.  But my
> > (admittedly biased) sense is that we're fast approaching the point
> > of diminishing returns.  Just how important is it to provide for names
> > that are one or two ideographs longer?
> >
> > Keith
> >
>
> With DUDE+REORDERING , we get 7~8 more Han ideographs.
> If you have enough time, test with many han examples.
>
> code-block shifting does not help to reduce average XOR distance
> in general cases ( good only for the first 4096 code block ).
>
> What is important is  to reduce ACE label length of AVERAGED
> han/hangul domains. THis working group should concentrage
> attentions  not to the max length issue but to  issues of
> reducing ACE label length of average hangul/han domains.
>
> Soobok Lee
>
>
>
>
>
>




From owner-idn@ops.ietf.org  Fri Jul  6 20:08:56 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA24201
	for <idn-archive@lists.ietf.org>; Fri, 6 Jul 2001 20:08:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IfZG-000KHm-00
	for idn-data@psg.com; Fri, 06 Jul 2001 17:03:26 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IfZF-000KHe-00
	for idn@ops.ietf.org; Fri, 06 Jul 2001 17:03:25 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6702XT17081;
	Sat, 7 Jul 2001 09:02:33 +0900 (KST)
Message-ID: <003401c10678$cef09500$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Edmon" <edmon@neteka.com>, "Keith Moore" <moore@cs.utk.edu>
Cc: <idn@ops.ietf.org>
References: <200107061753.NAA02764@astro.cs.utk.edu> <00cf01c1065e$9975a100$1001a8c0@neteka.com>
Subject: Re: [idn] ACE37,AMCW and LDUDE 
Date: Sat, 7 Jul 2001 09:07:27 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

----- Original Message -----
From: "Edmon" <edmon@neteka.com>
To: "Keith Moore" <moore@cs.utk.edu>; "Soobok Lee" <lsb@postel.co.kr>


> > I would *really* like to avoid complex reordering of codepoints, because
> > it would require fairly large tables (that would have to be implemented
> > on some machines of modest capability) and would be error-prone.
> >
> I agree.  The code block shifting mechanism in ACE37 however is very
simple
> and yeilds great benefit for CJK ideographs.
>

Code block shiffting  (  0x4E00:8FFFF ----> 0x0000: 0x52FF)
does reduce XOR diff value  for small subset of the code points
from   first 0x4E00 ~ 0x5E00 block.

For example, 0x4e00 and 0x5000 (xor diff is 0x1e00)
is mapped to 0x0000, 0x0200 (xir diff value 0x200 ).


But, For 0x4e00 and 0x6e00, xor diff values are  0x2000  for either
cases !


> > I could see having a very simple reordering of codepoints in order
> > to increase the efficiency of DUDE for ideographic languages.  But my
> > (admittedly biased) sense is that we're fast approaching the point
> > of diminishing returns.  Just how important is it to provide for names
> > that are one or two ideographs longer?
>
> It is more than one or two... in the worst case scenario for CJK, ACE37
out
> performs DUDE by 5 characters!

For 99% CJK domains, LDUDE allows 30~58% longer CJK domains than DUDE .

In other words, LDUDE compress 30~50% better than DUDE for average length
domains. This is more important point.
I will report when I complete testing with ACE37 + REORDERING later.


> And there is an undeniable demand from the CJK community to up the 14
> character limit to at least, I guess close to the original 23 character
> limit.
>
> >
> > Keith
>
> Edmon
>
>
>




From owner-idn@ops.ietf.org  Fri Jul  6 20:31:32 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA24570
	for <idn-archive@lists.ietf.org>; Fri, 6 Jul 2001 20:31:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ift2-000Ky8-00
	for idn-data@psg.com; Fri, 06 Jul 2001 17:23:52 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ift0-000Ky1-00
	for idn@ops.ietf.org; Fri, 06 Jul 2001 17:23:50 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f670NXT24297;
	Sat, 7 Jul 2001 09:23:33 +0900 (KST)
Message-ID: <003e01c1067b$bd85ef60$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>, "Edmon" <edmon@neteka.com>,
        "Keith Moore" <moore@cs.utk.edu>
Cc: <idn@ops.ietf.org>
Subject: Re: [idn] ACE37,AMCW and LDUDE 
Date: Sat, 7 Jul 2001 09:28:26 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Moreover,

codeblock shifting produces longer XOR diff in some cases:

0x5000 and 0x5f00: xor diff value = 0xf00

after codeblock shifting applied ( 0x4e00 -> 0x0000 ),

They are reduced to

0x0200 and 0x1100: xor diff value = 0x1300

diff value 0x1300 is longer than 0xf00.


codeblock shifting withOUT frequecy reordering
does not  help.

It  merely SHIFT xor diff distribution and
does NOT REDUCE the xor diff values.

I had tried it before and gave up.

Soobok Lee

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Edmon" <edmon@neteka.com>; "Keith Moore" <moore@cs.utk.edu>
 > > > I would *really* like to avoid complex reordering of codepoints,
because
> > > it would require fairly large tables (that would have to be
implemented
> > > on some machines of modest capability) and would be error-prone.
> > >
> > I agree.  The code block shifting mechanism in ACE37 however is very
> simple
> > and yeilds great benefit for CJK ideographs.
> >
>
> Code block shiffting  (  0x4E00:8FFFF ----> 0x0000: 0x52FF)
> does reduce XOR diff value  for small subset of the code points
> from   first 0x4E00 ~ 0x5E00 block.
>
> For example, 0x4e00 and 0x5000 (xor diff is 0x1e00)
> is mapped to 0x0000, 0x0200 (xir diff value 0x200 ).
>
>
> But, For 0x4e00 and 0x6e00, xor diff values are  0x2000  for either
> cases !





From owner-idn@ops.ietf.org  Fri Jul  6 22:01:18 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA26320
	for <idn-archive@lists.ietf.org>; Fri, 6 Jul 2001 22:01:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IhEE-000NR5-00
	for idn-data@psg.com; Fri, 06 Jul 2001 18:49:50 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IhED-000NQz-00
	for idn@ops.ietf.org; Fri, 06 Jul 2001 18:49:50 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f671ncT07882;
	Sat, 7 Jul 2001 10:49:38 +0900 (KST)
Message-ID: <007601c10687$c2e00f20$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Edmon" <edmon@neteka.com>, "Keith Moore" <moore@cs.utk.edu>
Cc: <idn@ops.ietf.org>
References: <200107061753.NAA02764@astro.cs.utk.edu> <00cf01c1065e$9975a100$1001a8c0@neteka.com>
Subject: Re: [idn] ACE37,AMCW and LDUDE 
Date: Sat, 7 Jul 2001 10:54:29 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Edmon" <edmon@neteka.com>
To: "Keith Moore" <moore@cs.utk.edu>; "Soobok Lee" <lsb@postel.co.kr>
Cc: <idn@ops.ietf.org>
Sent: Saturday, July 07, 2001 5:59 AM
Subject: Re: [idn] ACE37,AMCW and LDUDE


 >
> > I could see having a very simple reordering of codepoints in order
> > to increase the efficiency of DUDE for ideographic languages.  But my
> > (admittedly biased) sense is that we're fast approaching the point
> > of diminishing returns.  Just how important is it to provide for names
> > that are one or two ideographs longer?
>
> It is more than one or two... in the worst case scenario for CJK, ACE37
out
> performs DUDE by 5 characters!

No. It may be so for the worst case.
For nominal case for hangul/han domains, max length reaches 28~29 syllables.

moreover, ACE37 with REORDERING will do much more compression, i guess.
REORDERING is another compression layer applicabe to all ACEs, not for
DUDE.




From owner-idn@ops.ietf.org  Fri Jul  6 22:25:21 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA26782
	for <idn-archive@lists.ietf.org>; Fri, 6 Jul 2001 22:25:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15IhgT-000OJ3-00
	for idn-data@psg.com; Fri, 06 Jul 2001 19:19:01 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15IhgR-000OIx-00
	for idn@ops.ietf.org; Fri, 06 Jul 2001 19:19:00 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f672IiT24176;
	Sat, 7 Jul 2001 11:18:44 +0900 (KST)
Message-ID: <001001c1068b$d35d1c40$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>, "Edmon" <edmon@neteka.com>,
        "Keith Moore" <moore@cs.utk.edu>
Cc: <idn@ops.ietf.org>
References: <003e01c1067b$bd85ef60$ed1bd9d2@postel.co.kr>
Subject: Re: [idn] ACE37,AMCW and LDUDE 
Date: Sat, 7 Jul 2001 11:23:34 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

codeblock shifting does good for ACE37, but not for DUDE.

The previous argument does not hurt ACE37's usefulness.
It cleverly uses
"base37" to utilize  shifted xor diff distrubutions. Good idea.

But the shifting will not benefit other "base16" ACEs (DUDE?).
That's the point.

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>; "Edmon" <edmon@neteka.com>; "Keith
Moore" <moore@cs.utk.edu>
Cc: <idn@ops.ietf.org>
Sent: Saturday, July 07, 2001 9:28 AM
Subject: Re: [idn] ACE37,AMCW and LDUDE


> Moreover,
>
> codeblock shifting produces longer XOR diff in some cases:
>
> 0x5000 and 0x5f00: xor diff value = 0xf00
>
> after codeblock shifting applied ( 0x4e00 -> 0x0000 ),
>
> They are reduced to
>
> 0x0200 and 0x1100: xor diff value = 0x1300
>
> diff value 0x1300 is longer than 0xf00.
>
>
> codeblock shifting withOUT frequecy reordering
> does not  help.
>
> It  merely SHIFT xor diff distribution and
> does NOT REDUCE the xor diff values.
>
> I had tried it before and gave up.
>
> Soobok Lee
>
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: "Edmon" <edmon@neteka.com>; "Keith Moore" <moore@cs.utk.edu>
>  > > > I would *really* like to avoid complex reordering of codepoints,
> because
> > > > it would require fairly large tables (that would have to be
> implemented
> > > > on some machines of modest capability) and would be error-prone.
> > > >
> > > I agree.  The code block shifting mechanism in ACE37 however is very
> > simple
> > > and yeilds great benefit for CJK ideographs.
> > >
> >
> > Code block shiffting  (  0x4E00:8FFFF ----> 0x0000: 0x52FF)
> > does reduce XOR diff value  for small subset of the code points
> > from   first 0x4E00 ~ 0x5E00 block.
> >
> > For example, 0x4e00 and 0x5000 (xor diff is 0x1e00)
> > is mapped to 0x0000, 0x0200 (xir diff value 0x200 ).
> >
> >
> > But, For 0x4e00 and 0x6e00, xor diff values are  0x2000  for either
> > cases !
>
>
>




From owner-idn@ops.ietf.org  Fri Jul  6 22:40:44 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA28004
	for <idn-archive@lists.ietf.org>; Fri, 6 Jul 2001 22:40:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ihqp-000Oet-00
	for idn-data@psg.com; Fri, 06 Jul 2001 19:29:43 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ihqn-000Oen-00
	for idn@ops.ietf.org; Fri, 06 Jul 2001 19:29:42 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f672TZT29941
	for <idn@ops.ietf.org>; Sat, 7 Jul 2001 11:29:35 +0900 (KST)
Message-ID: <001f01c1068d$56c83000$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Subject: [idn] time to consider  average han/hangul domains
Date: Sat, 7 Jul 2001 11:34:25 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Now that we have many useful ACE alternatives to overcome
"15 han letters barrier",
it is time for us to consider the reducing length of ACE labels for
AVERAGE han/hangul domains.

As the next example shows,
LDUDE produces 15 chars ace labels for a 9-letter hangul domain.

9 letters Han/Hangeul domains are very common.



K2) Korean String 2:  ( 9 hangul syllables )
      <KRNIC in korean>
      U+D55C U+AD6D U+C778 U+D130 U+B137 U+C815 U+BCF4 U+C13C
      U+D130

      DUDE-02 : 7xvNz2vBy4tFtywIyssHz3uCzw8Bz76ItssN
                ( 36 chars )
      LDUDE   : 5syAB3BIJ7BB7NF
                ( 15 chars,  58.3% shorter )
      AMCW    : 7xxNFmpM52QjsGjzNaxJhwKj6Qjs
                ( 28 chars )
      LAMCW   : 5ssAsB3AIBwAB3PI
                ( 16 chars )
      MACE     : lasbbdhrok9gc9ni0lf7kg9sk9g
                ( 26 chars )

      ACE37    : still waiting for the source.




From owner-idn@ops.ietf.org  Mon Jul  9 09:26:01 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA13547
	for <idn-archive@lists.ietf.org>; Mon, 9 Jul 2001 09:26:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15JahM-0005sv-00
	for idn-data@psg.com; Mon, 09 Jul 2001 06:03:36 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15JahJ-0005sk-00
	for idn@ops.ietf.org; Mon, 09 Jul 2001 06:03:33 -0700
Message-ID: <003201c10878$34f5b460$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: "Edmon" <edmon@neteka.com>, <idn@ops.ietf.org>,
        "Adam M. Costello" <amc@cs.berkeley.edu>
References: <20010705231837.A22709@arwen.cs.berkeley.edu> <002201c10634$0051a020$1001a8c0@neteka.com>
Subject: [idn] ACE37
Date: Mon, 9 Jul 2001 09:08:10 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

One thing I forgot to point out:

From: "Adam M. Costello" <amc@cs.berkeley.edu>
> It doesn't look as simple as DUDE to me.  To me it looks no simpler than
> AMC-ACE-W, which is as efficient as ACE37 for CJK, as efficient as DUDE
> for single-row scripts, and more efficient than DUDE for Latin-based
> scripts.  Whereas AMC-ACE-W's complexity is in a state machine, ACE37's
> complexity is in encoding/recognizing lots of different patterns.

DUDE uses a similar algorithm to determine the significance of diff, which
in turn determines how many b32 characters to use:

diff value                                    DUDE Form
----------------------------------------------------------------------------
diff<=0xF                                 <"0"+quartet>
0x10<=diff<=0xFF                  <"1"+quartet><"0"+quartet>
0x100<=diff<=0xFFF              <"1"+quartet><"1"+quartet><"0"+quartet>
0x1000<=diff<=0xFFFF
<"1"+quartet><"1"+quartet><"1"+quartet><"0"+quartet>
0x10000<=diff<=0xFFFFF
<"1"+quartet><"1"+quartet><"1"+quartet><"1"+quartet><"0"+quartet>
0x100000<=diff<=0x10FFFF
<"1"+quartet><"1"+quartet><"1"+quartet><"1"+quartet><"1"+quartet><"0"+quarte
t>

Here you see that there are 6 different scenarios as opposed to ACE37's 5
scenarios.  Both DUDE and ACE37 needs to determine the significant bits of
the resulting diff to come up with the correct form.  So perhaps it doesnt
look as simple (because I created these charts in the draft), but in effect
it is the same.  You could refer to the procedure comparison I did in my
draft in Section 1
<http://www.ietf.org/internet-drafts/draft-chung-idn-ace37-00.txt>


Edmon





From owner-idn@ops.ietf.org  Mon Jul  9 09:52:01 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA14584
	for <idn-archive@lists.ietf.org>; Mon, 9 Jul 2001 09:52:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15JbHC-00071X-00
	for idn-data@psg.com; Mon, 09 Jul 2001 06:40:38 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15JbHB-00071I-00
	for idn@ops.ietf.org; Mon, 09 Jul 2001 06:40:37 -0700
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id GAA13527;
	Mon, 9 Jul 2001 06:40:30 -0700
Message-Id: <5.1.0.14.2.20010709063204.040f9008@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 09 Jul 2001 06:33:36 -0700
To: Harald Tveit Alvestrand <harald@alvestrand.no>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] Fw: Hello, This is KyungJae Park (KRNIC)
Cc: idn@ops.ietf.org
In-Reply-To: <759999481.994426223@[192.168.1.31]>
References: <05b201c105e4$96f18ea0$dd00a8c0@jamessonyvaio>
 <05b201c105e4$96f18ea0$dd00a8c0@jamessonyvaio>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 04:30 AM 7/6/2001, Harald Tveit Alvestrand wrote:
>the upper limit on length is not a fixed value, it depends on the 
>character values used, even within a single script.
>...
>This will be fun to explain to customers...

That bit of complication sounds like a market opportunity for a new 
technical skill:  finding appealing names that fit, especially when needing 
or wanting to squeeze in extra characters.

d/

----------
Dave Crocker  <mailto:dcrocker@brandenburg.com>
Brandenburg InternetWorking  <http://www.brandenburg.com>
tel +1.408.246.8253;  fax +1.408.273.6464




From owner-idn@ops.ietf.org  Mon Jul  9 11:03:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA17227
	for <idn-archive@lists.ietf.org>; Mon, 9 Jul 2001 11:03:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15JcPR-00098d-00
	for idn-data@psg.com; Mon, 09 Jul 2001 07:53:13 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15JcPP-00098X-00
	for idn@ops.ietf.org; Mon, 09 Jul 2001 07:53:11 -0700
Message-ID: <003a01c10887$8fe5e520$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: "Soobok Lee" <lsb@postel.co.kr>, "Keith Moore" <moore@cs.utk.edu>
Cc: <idn@ops.ietf.org>
References: <003e01c1067b$bd85ef60$ed1bd9d2@postel.co.kr>
Subject: Re: [idn] ACE37,AMCW and LDUDE 
Date: Mon, 9 Jul 2001 10:58:04 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Soobok,

> codeblock shifting produces longer
XOR diff in some cases:
> 0x5000 and 0x5f00: xor diff value =
0xf00
> after codeblock shifting applied (
0x4e00 -> 0x0000 ),

This is incorrect. With codeblock
shifting in ACE37 0x4e00 becomes 0x1e00
(0x4e00 - 0x3000 = 0x1e00)
0x2000 and 0x2f00: diff = 0xf00
The diff is the same in this case.

> codeblock shifting withOUT frequecy
reordering
> does not  help.
> It  merely SHIFT xor diff
distribution and
> does NOT REDUCE the xor diff values.

ACE37 does not intend to reduce xor
diff values but to optimize it (or
shift it as the name suggests, so that
within the CJK ideograph library, diff
will not exceed 15bit or 3 <b32>
characters) to improve the han
ideographs capacity and keep the
algorithm as simple as DUDE.

Edmon




From owner-idn@ops.ietf.org  Mon Jul  9 16:07:23 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA27544
	for <idn-archive@lists.ietf.org>; Mon, 9 Jul 2001 16:07:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Jgry-000Gld-00
	for idn-data@psg.com; Mon, 09 Jul 2001 12:38:58 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Jgrw-000GlR-00
	for idn@ops.ietf.org; Mon, 09 Jul 2001 12:38:56 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH682MQ438w43h47r6jwQo2e8xnXUjFHzfw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id F9W9X4AM; Mon, 09 Jul 2001 15:36:37 EDT
To: dhc@dcrocker.net
Cc: harald@alvestrand.no, idn@ops.ietf.org
Date: Mon, 9 Jul 2001 12:51:39 -0700
Subject: Re: [idn] Fw: Hello, This is KyungJae Park (KRNIC)
Message-ID: <20010709.125142.-779829.0.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.11
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-9,11-30
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

We should allow more space for the names.  Even most of database
applications give default  80 letters to a name field.  I have tried 60 
letters in 1988, at time of space is a lot more expensive.  It has more 
trouble for me then, and I have not use it for less than 80 ever since.  
Internet is a much larger database, if we have a voice in this field 
length, we should expand it now rather than hear this again within 
a few years.

Liana

On Mon, 09 Jul 2001 06:33:36 -0700 Dave Crocker <dhc@dcrocker.net>
writes:
> At 04:30 AM 7/6/2001, Harald Tveit Alvestrand wrote:
> >the upper limit on length is not a fixed value, it depends on the 
> >character values used, even within a single script.
> >...
> >This will be fun to explain to customers...
> 
> That bit of complication sounds like a market opportunity for a new 
> technical skill:  finding appealing names that fit, especially when 
> needing 
> or wanting to squeeze in extra characters.
> 
> d/
> 
> ----------
> Dave Crocker  <mailto:dcrocker@brandenburg.com>
> Brandenburg InternetWorking  <http://www.brandenburg.com>
> tel +1.408.246.8253;  fax +1.408.273.6464
> 
> 



From owner-idn@ops.ietf.org  Mon Jul  9 17:01:31 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA28438
	for <idn-archive@lists.ietf.org>; Mon, 9 Jul 2001 17:01:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ji24-000InL-00
	for idn-data@psg.com; Mon, 09 Jul 2001 13:53:28 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ji22-000InD-00
	for idn@ops.ietf.org; Mon, 09 Jul 2001 13:53:26 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id QAA20682;
        Mon, 9 Jul 2001 16:53:20 -0400 (EDT)
Message-Id: <200107092053.QAA20682@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: liana.ydisg@juno.com
cc: dhc@dcrocker.net, harald@alvestrand.no, idn@ops.ietf.org
Subject: Re: [idn] Fw: Hello, This is KyungJae Park (KRNIC) 
In-reply-to: Your message of "Mon, 09 Jul 2001 12:51:39 PDT."
             <20010709.125142.-779829.0.liana.ydisg@juno.com> 
Date: Mon, 09 Jul 2001 16:53:20 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> We should allow more space for the names.  Even most of database
> applications give default  80 letters to a name field.

63 characters per label has been far more than enough for English.
If you are really trying to convince us that ideographic languages 
(which pack more information per characters) need *more* than 63 
characters per label, I think you're going to need to provide more 
justification.  Especially when the emperical evidence seems to 
indicate otherwise.

Keith



From owner-idn@ops.ietf.org  Mon Jul  9 18:34:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA00144
	for <idn-archive@lists.ietf.org>; Mon, 9 Jul 2001 18:34:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15JjEY-000Ks2-00
	for idn-data@psg.com; Mon, 09 Jul 2001 15:10:26 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15JjEW-000Krf-00
	for idn@ops.ietf.org; Mon, 09 Jul 2001 15:10:25 -0700
Message-ID: <000201c108c4$a29e9a80$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: <idn@ops.ietf.org>, "Adam M. Costello" <amc@cs.berkeley.edu>
References: <20010706221305.A11087@arwen.cs.berkeley.edu>
Subject: [idn] ACE37
Date: Mon, 9 Jul 2001 18:14:53 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

From: "Adam M. Costello" <amc@cs.berkeley.edu>
> I was basing it on 59 octets.  In the worst case, DUDE would require
> 60 octets for 15 Han characters, but the worst case virtually never
> happens.  In the thousands of names that JPNIC tried, it never happened.
> 59 octets happened a few times, but I think the typical length was 58 or
> 57.  So DUDE can almost always support 15 characters, but usually cannot
> support 16.  I think the boundary between "usually fits" and "usually
> fails" is more useful than the "always fits" number.

I dont think this is very true for Chinese.  Most of the time, characters
would come from different rows causing DUDE to have to use 4 characters for
each Chinese ideograph.  In anycase, if you compare "usually fits" then
ACE37 should still out perform DUDE by a magnitude of at least 5 codepoints,
cause 19 codepoints is the "worst case" scenario (with the 59-octet limit),
but it is likely that it would "usually fit" 20-21 codepoints.  As in my
example with JPNIC in Japanese, it has 25 (>21) codepoints and ACE37 can
still handle it, whereas DUDE fails.

I think the point I am trying to make is that ACE37 greatly increases the
capacity for CJK ideographs, which has been identified as an undeniable
concern through the discussion on this mailing list, without requiring a
complex algorithm and utilizes the simplicity of DUDE.

Edmon










From owner-idn@ops.ietf.org  Mon Jul  9 18:45:06 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA00330
	for <idn-archive@lists.ietf.org>; Mon, 9 Jul 2001 18:45:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Jjd1-000LYV-00
	for idn-data@psg.com; Mon, 09 Jul 2001 15:35:43 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Jjcy-000LYK-00
	for idn@ops.ietf.org; Mon, 09 Jul 2001 15:35:40 -0700
Received: from [165.227.249.20] (ip20.proper.com [165.227.249.20])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f69MZam01624
	for <idn@ops.ietf.org>; Mon, 9 Jul 2001 15:35:36 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100312b76fe08ee6b4@[165.227.249.20]>
In-Reply-To: <000201c108c4$a29e9a80$1001a8c0@neteka.com>
References: <20010706221305.A11087@arwen.cs.berkeley.edu>
 <000201c108c4$a29e9a80$1001a8c0@neteka.com>
Date: Mon, 9 Jul 2001 15:34:50 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] ACE37
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 6:14 PM -0400 7/9/01, Edmon wrote:
>the
>capacity for CJK ideographs, which has been identified as an undeniable
>concern through the discussion on this mailing list

The fact that a few people have expressed the concern without ever 
giving any evidence for it is not "undeniable". So far, there has 
been *no* evidence that a 15-character limit would restrict names 
that would be used for a significant number of real-live, 
actually-used host names. If you have any evidence to the contrary 
(that is, names that would actually be used in DNS names), please say 
so ASAP.

The concerns have all been for companies that want to register their 
legal names. Well, the DNS will *never* allow all the companies that 
want their legal names to do so. In the United States and throughout 
Europe, legal company names include spaces, commas, periods, 
apostrophes, ampersands, and so on. Those are not going to be allowed 
in IDN names, so those companies will not be able to register their 
legal names.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Mon Jul  9 19:15:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA00687
	for <idn-archive@lists.ietf.org>; Mon, 9 Jul 2001 19:15:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Jk4a-000MKA-00
	for idn-data@psg.com; Mon, 09 Jul 2001 16:04:12 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Jk4Y-000MK4-00
	for idn@ops.ietf.org; Mon, 09 Jul 2001 16:04:11 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15Jk4X-0007MQ-00; Mon, 09 Jul 2001 16:04:09 -0700
Date: Mon, 9 Jul 2001 23:04:09 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] ACE37
Message-ID: <20010709230408.B9469@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <000201c108c4$a29e9a80$1001a8c0@neteka.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Edmon <edmon@neteka.com> wrote:

> I think the point I am trying to make is that ACE37 greatly increases
> the capacity for CJK ideographs

Yes, it certainly does (and also reduces the capacity for non-CJK
characters).

> without requiring a complex algorithm

I agree that the amount of complexity it adds to DUDE is not great, but
I think it's comparable to the amount of complexity that AMC-ACE-W adds
to DUDE.  DUDE does not have six different patterns, it has only one
pattern, because they're all handled by the same logic:

  To encode diff:

    for (tmp = diff >> 4, k = 1;  tmp != 0;  ++k, tmp >>= 4);
    out += k;
    output[out - 1] = base32[diff & 0xF];

    for (j = 2;  j <= k;  ++j) {
      diff >>= 4;
      output[out - j] = base32[0x10 | (diff & 0xF)];
    }

  To decode diff:

    /* invariant: c == input[in] */

    for (diff = 0;  ;  c = input[++in]) {
      q = base32_decode(c);
      if (q == base32_invalid) return dude_bad_input;
      diff = (diff << 4) | (q & 0xF);
      if (q >> 4 == 0) break;
    }

ACE37, on the other hand, must have separate logic for each pattern,
right?

By the way, I don't advocate AMC-ACE-W, because it's inferior to
AMC-ACE-Z, for which there will be a draft soon.

AMC



From owner-idn@ops.ietf.org  Mon Jul  9 21:27:27 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA03038
	for <idn-archive@lists.ietf.org>; Mon, 9 Jul 2001 21:27:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Jm51-000Pgv-00
	for idn-data@psg.com; Mon, 09 Jul 2001 18:12:47 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Jm4r-000PgZ-00
	for idn@ops.ietf.org; Mon, 09 Jul 2001 18:12:41 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6A0WhT21530;
	Tue, 10 Jul 2001 09:32:46 +0900 (KST)
Message-ID: <015401c108d8$48663320$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "Paul Hoffman / IMC" <phoffman@imc.org>
References: <20010706221305.A11087@arwen.cs.berkeley.edu> <000201c108c4$a29e9a80$1001a8c0@neteka.com> <p05100312b76fe08ee6b4@[165.227.249.20]>
Subject: [idn] THis WG derailed ?
Date: Tue, 10 Jul 2001 09:35:46 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

This WG  should focus on issues of AVERAGE length of ACE lables.

We have not enough time for the debate around max ACE label length.
We have already many useful ACE alternatives 
to overcome this 14-han barrier easily.

bare DUDE produces  long and complex ACE lables for average length of
han/hangul domains, while DUDE's algorithm seems to be simple.
We have no justification for why we should sacrifice 
label simplicity for code simplicity, 
while we already have very HUGE mapping tables 
and algorithms in NAMEPREP and KC Norm.
ACE codes are written once and copied and executed many times.
Output label simplicity matters.

No one has provided the right reason 
to exclude needs for the following names. 
What does it GIVE us  to ban people from registering them?
What does ACE code simplicity give us ?

Soobok
--------------------------------------------------------------------


ONE EVIDENCE from Chinese Gov for domains of 16 han letters.

(SC1) Simplified Chinese String  1 : ( 16 letters )
      <ministry of foreign trade and economic cooperation, PRC>
      u+4e2d u+534e u+4eba u+6c11 u+5171 u+548c u+56fd u+5bf9
      u+5916 u+8d38 u+6613 u+7ecf u+6d4e u+5408 u+4f5c u+90e8

      DUDE-02 : w8wpt7ydt79euu4mv7yax9puzb7seu8r7wuq85umt27ntv2bv3wgt\
                5xe795e ( 60 chars )
      LDUDE   : xswjuzru6nu7fv7kv4gutrwgb7mbwiu6cuzqqxm
                ( 39 chars, 35.0% shorter )
      AMCW    : w8up29ps5kdst5uh7ygsup29pm3cb39n8tknpb39hkygswhdysupa\
                qd ( 55 chars )
      LAMCW   : xsujwxgu3kwwrv3fwvduunykm5ab9jwvmuwfmta
                ( 39 chars )


ANOTHER EVIDENCE from korean site names of 18 hangeul letters.


(K3) Korean String 3:  ( 18 hangul syllables )
      U+C804 U+AD6D U+C2E4 U+C9C1 U+B178 U+C219 U+C790 U+B300
      U+CC45 U+C885 U+AD50 U+C2DC U+BBFC U+B2E8 U+CCB4 U+D611
      U+C758 U+D68C

      DUDE-02 : 62yEyxyJy92J5uFz25JzvyBx2Jzw3Az9wFw6Ayx7Fy92Nz3uA3tEz8\
                xNt44FttwJtt7E ( 68 chars )
      LDUDE   : 5szAtBtvBt7Mt2Qv4Qu7KtFt5It3MuEvAtvDyJCtuC4G4J
                ( 46 chars,  32% shorter )
      AMCW    : 62sEFmpKzeNqbGm2Ks3M6sG2aPcfNefFksKy6I96GziPfwRstM42Rwn
                ( 55 chars )
      LAMCW   : 5stAsB5tvAGhmGmgG2mGatsE5t7JGbhsDvD5tsAyIK5swJ8RwG
                ( 50 chars )


Average lenght hangeul domain:

    (K4) Korean String 4:  ( 7 hangul syllables )
      <Hynics Semiconductor in korean>
      U+D558 U+C774 U+B2C9 U+C2A4 U+BC18 U+B3C4 U+CCB4        

      DUDE-02 : 7xvItuuNzx5PzsyPz85N97Nz9zA
                ( 27 chars )
      LDUDE   : 5s3C4F5Q7PtwRtMK
                ( 16 chars,  40% shorter )
      AMCW    : 7xxIM5wGyjKxeJa2G8ePfw
                ( 22 chars )
      LAMCW   : 5s9CxH8JvE5tzMyAK
                ( 17 chars )


----- Original Message ----- 
From: "Paul Hoffman / IMC" <phoffman@imc.org>
To: <idn@ops.ietf.org>
Sent: Tuesday, July 10, 2001 7:34 AM
Subject: Re: [idn] ACE37


> At 6:14 PM -0400 7/9/01, Edmon wrote:
> >the
> >capacity for CJK ideographs, which has been identified as an undeniable
> >concern through the discussion on this mailing list
> 
> The fact that a few people have expressed the concern without ever 
> giving any evidence for it is not "undeniable". So far, there has 
> been *no* evidence that a 15-character limit would restrict names 
> that would be used for a significant number of real-live, 
> actually-used host names. If you have any evidence to the contrary 
> (that is, names that would actually be used in DNS names), please say 
> so ASAP.
> 
> The concerns have all been for companies that want to register their 
> legal names. Well, the DNS will *never* allow all the companies that 
> want their legal names to do so. In the United States and throughout 
> Europe, legal company names include spaces, commas, periods, 
> apostrophes, ampersands, and so on. Those are not going to be allowed 
> in IDN names, so those companies will not be able to register their 
> legal names.
> 
> --Paul Hoffman, Director
> --Internet Mail Consortium
> 




From owner-idn@ops.ietf.org  Tue Jul 10 00:08:22 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA07340
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 00:08:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15JoZP-0003w1-00
	for idn-data@psg.com; Mon, 09 Jul 2001 20:52:19 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15JoZM-0003vt-00
	for idn@ops.ietf.org; Mon, 09 Jul 2001 20:52:16 -0700
Received: from [165.227.249.20] (ip20.proper.com [165.227.249.20])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f6A3qBm07953
	for <idn@ops.ietf.org>; Mon, 9 Jul 2001 20:52:11 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05101000b7702903d0ec@[165.227.249.20]>
In-Reply-To: <015401c108d8$48663320$ed1bd9d2@postel.co.kr>
References: <20010706221305.A11087@arwen.cs.berkeley.edu>
 <000201c108c4$a29e9a80$1001a8c0@neteka.com>
 <p05100312b76fe08ee6b4@[165.227.249.20]>
 <015401c108d8$48663320$ed1bd9d2@postel.co.kr>
Date: Mon, 9 Jul 2001 20:51:16 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] THis WG derailed ?
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 9:35 AM +0900 7/10/01, Soobok Lee wrote:
>?This WG  should focus on issues of AVERAGE length of ACE lables.

That is an opinion. There has been a different opinion of many other 
people that the WG should focus on getting an algorithm good enough 
for the vast majority of likely names. If you think the discussion 
needs to be opened again, you should speak with the WG chairs. 
However, you need to be much more specific than saying "AVERAGE".

There are three kinds of averages (mean, median, and mode); of those, 
clearly we do not want to consider mode. How do you intend to measure 
either mean or median? All of the ACEs proposed so far have different 
means and medians for different scripts. They also have different 
means and medians for names that contain characters from only one 
script versus names that contain characters from two (such as names 
that are based on a non-Latin script but use Latin hyphens or digits).

>We have not enough time for the debate around max ACE label length.

It seems like nine months is plenty of time. Could you say how much 
longer you think is appropriate?

>ONE EVIDENCE from Chinese Gov for domains of 16 han letters.
>
>(SC1) Simplified Chinese String  1 : ( 16 letters )
>       <ministry of foreign trade and economic cooperation, PRC>
>       u+4e2d u+534e u+4eba u+6c11 u+5171 u+548c u+56fd u+5bf9
>       u+5916 u+8d38 u+6613 u+7ecf u+6d4e u+5408 u+4f5c u+90e8

Two questions:
- Do you expect them to actually use that name? Or would they instead 
use one that is easier to remember?

- Why would they use "PRC" at the end if this name will be in the .cn 
TLD or, hopefully, in the TLD that will express the name "China" in 
the Chinese language?

As for the new subject line, it is difficult to see how a wide 
consensus moving forwards is "derailed". If we were at a technical 
impasse, that could be considered derailment, but certainly doesn't 
described the WG as it stands now.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Tue Jul 10 00:48:04 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA07865
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 00:48:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15JpHE-0005Ku-00
	for idn-data@psg.com; Mon, 09 Jul 2001 21:37:36 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15JpHC-0005Kn-00
	for idn@ops.ietf.org; Mon, 09 Jul 2001 21:37:34 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id AAA23564;
        Tue, 10 Jul 2001 00:37:27 -0400 (EDT)
Message-Id: <200107100437.AAA23564@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Soobok Lee" <lsb@postel.co.kr>
cc: idn@ops.ietf.org, "Paul Hoffman / IMC" <phoffman@imc.org>
Subject: Re: [idn] THis WG derailed ? 
In-reply-to: Your message of "Tue, 10 Jul 2001 09:35:46 +0900."
             <015401c108d8$48663320$ed1bd9d2@postel.co.kr> 
Date: Tue, 10 Jul 2001 00:37:27 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> This WG  should focus on issues of AVERAGE length of ACE lables.

why?  do you have some evidence that this has a significant
effect on performance of ANY protocol?



From owner-idn@ops.ietf.org  Tue Jul 10 01:11:49 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA08756
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 01:11:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15JpaQ-0005zs-00
	for idn-data@psg.com; Mon, 09 Jul 2001 21:57:26 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15JpaL-0005za-00
	for idn@ops.ietf.org; Mon, 09 Jul 2001 21:57:23 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6A4v2T22083;
	Tue, 10 Jul 2001 13:57:02 +0900 (KST)
Message-ID: <01bf01c108fd$22731500$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: <idn@ops.ietf.org>, "Paul Hoffman / IMC" <phoffman@imc.org>
References: <200107100437.AAA23564@astro.cs.utk.edu>
Subject: Re: [idn] THis WG derailed ? 
Date: Tue, 10 Jul 2001 13:59:43 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I am not sure  what you mean by "significant" effect.

I think shorter ACE labels benefits  :

 1. save momory resources
     shorter IDN zone file
     save memory space of  intermediate DNS/Web cache servers
     shorter log file for dns/web/mail transactions
     shorter Http cookie cache entries 

 2. reduce traffic
    shorter DNS queries
    shorter HTTP host: header value
    shorter SMTP session from to:  and rcpt to: tags
    
 3. for human
    more easy to transcript
    good for administrators to manage leaked ACE labels
    registrants cannot avoid ACE labels now and near future


For, <Samsung Electronics  in Korean> ( 4 hangul syllables)

U+C0BC U+C131 U+C804 U+C790

DUDE-02  : 6s7Nt2P3vF93E      13       
LDUDE     : 5s7AB4BB             8 ( 5 chars, 38% shorter )


<Hyundai  Develpoment Company in Korean> ( 6 syllables)
U+D604 U+B300 U+C0B0 U+C5C5 U+AC1C U+BC1C

DUDE-02  : 7yyEyxsEzv5AxzFy37JtssA    ( 23 )
LDUDE     : 5syMRtAB3FB                      11 ( 12 chars, 52% shorter )




----- Original Message ----- 
From: "Keith Moore" <moore@cs.utk.edu>
To: "Soobok Lee" <lsb@postel.co.kr>
Cc: <idn@ops.ietf.org>; "Paul Hoffman / IMC" <phoffman@imc.org>
Sent: Tuesday, July 10, 2001 1:37 PM
Subject: Re: [idn] THis WG derailed ? 


> > This WG  should focus on issues of AVERAGE length of ACE lables.
> 
> why?  do you have some evidence that this has a significant
> effect on performance of ANY protocol?
> 




From owner-idn@ops.ietf.org  Tue Jul 10 01:19:22 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA09838
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 01:19:21 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Jpea-00067q-00
	for idn-data@psg.com; Mon, 09 Jul 2001 22:01:44 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15JpeY-00067i-00
	for idn@ops.ietf.org; Mon, 09 Jul 2001 22:01:42 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id BAA23835;
        Tue, 10 Jul 2001 01:01:38 -0400 (EDT)
Message-Id: <200107100501.BAA23835@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Soobok Lee" <lsb@postel.co.kr>
cc: "Keith Moore" <moore@cs.utk.edu>, idn@ops.ietf.org,
        "Paul Hoffman / IMC" <phoffman@imc.org>
Subject: Re: [idn] THis WG derailed ? 
In-reply-to: Your message of "Tue, 10 Jul 2001 13:59:43 +0900."
             <01bf01c108fd$22731500$ed1bd9d2@postel.co.kr> 
Date: Tue, 10 Jul 2001 01:01:38 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> I am not sure  what you mean by "significant" effect.

I mean the burden is on you to demonstrate that it's worth
the trouble that would be required to further reduce the 
average length of label representation, and you haven't yet
provided any support for this argument.

the question is not whether there are benefits, the question
is whether they are worth the extra complexity and overhead,
and the additional delay in getting IDNs out the door.

Keith



From owner-idn@ops.ietf.org  Tue Jul 10 02:04:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA22210
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 02:04:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15JqNu-0007bf-00
	for idn-data@psg.com; Mon, 09 Jul 2001 22:48:34 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15JqNs-0007bX-00
	for idn@ops.ietf.org; Mon, 09 Jul 2001 22:48:32 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6A5mKT00134;
	Tue, 10 Jul 2001 14:48:23 +0900 (KST)
Message-ID: <01dc01c10904$4e1c9620$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "\"Keith Moore\"" <moore@cs.utk.edu>
References: <200107100501.BAA23835@astro.cs.utk.edu>
Subject: Re: [idn] THis WG derailed ? 
Date: Tue, 10 Jul 2001 14:50:59 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


We already have ACE alternatives ** NOW **.

How much time  do you expect  to be taken
in order to improve or replace DUDE ?
1 week or 1 month of delay?  That's too long to wait for?

Can you demonstrate  whom  and how much
code simplicity  benefits ?  ACE codes are compiled into
binary codes in *HUGE* NAMEPREP & KC Norm libraries.

soobok

----- Original Message ----- 
From: "Keith Moore" <moore@cs.utk.edu>
To: "Soobok Lee" <lsb@postel.co.kr>
Cc:<idn@ops.ietf.org>; "Paul Hoffman / IMC" <phoffman@imc.org>
Sent: Tuesday, July 10, 2001 2:01 PM
Subject: Re: [idn] THis WG derailed ? 


> > I am not sure  what you mean by "significant" effect.
> 
> I mean the burden is on you to demonstrate that it's worth
> the trouble that would be required to further reduce the 
> average length of label representation, and you haven't yet
> provided any support for this argument.
> 
> the question is not whether there are benefits, the question
> is whether they are worth the extra complexity and overhead,
> and the additional delay in getting IDNs out the door.
> 
> Keith
> 




From owner-idn@ops.ietf.org  Tue Jul 10 02:43:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA24173
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 02:43:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Jqys-0008qf-00
	for idn-data@psg.com; Mon, 09 Jul 2001 23:26:46 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Jqyp-0008qX-00
	for idn@ops.ietf.org; Mon, 09 Jul 2001 23:26:43 -0700
Received: from enoshima (tea13.w3.mag.keio.ac.jp [133.27.228.243])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id PAA09949;
	Tue, 10 Jul 2001 15:26:28 +0900 (JST)
Message-Id: <4.2.0.58.J.20010710145423.032a47c0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 10 Jul 2001 15:07:15 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, "Keith Moore" <moore@cs.utk.edu>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] THis WG derailed ? 
Cc: <idn@ops.ietf.org>, "Paul Hoffman / IMC" <phoffman@imc.org>
In-Reply-To: <01bf01c108fd$22731500$ed1bd9d2@postel.co.kr>
References: <200107100437.AAA23564@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 13:59 01/07/10 +0900, Soobok Lee wrote:
>I am not sure  what you mean by "significant" effect.
>
>I think shorter ACE labels benefits  :
>
>  1. save momory resources
>      shorter IDN zone file
>      save memory space of  intermediate DNS/Web cache servers
>      shorter log file for dns/web/mail transactions
>      shorter Http cookie cache entries
>
>  2. reduce traffic
>     shorter DNS queries
>     shorter HTTP host: header value
>     shorter SMTP session from to:  and rcpt to: tags

Can you give an estimate of what percentage of overall transfer/
storage will be for Hangul/Han domain names? I'm very sure this
is extremely low, also because the average Han/Hangul names will
be quite short.


>  3. for human
>     more easy to transcript
>     good for administrators to manage leaked ACE labels
>     registrants cannot avoid ACE labels now and near future

I consider that a good reason against any kind of ACE.
It doesn't, in my opinion, give any reason for any kind
of length arguments. If administrators ever have to deal
with ACE (I very much hope they don't), they will do that
by cut/copy/paste, where length is rather irrelevant.


Regards,    Martin.


>For, <Samsung Electronics  in Korean> ( 4 hangul syllables)
>
>U+C0BC U+C131 U+C804 U+C790
>
>DUDE-02  : 6s7Nt2P3vF93E      13
>LDUDE     : 5s7AB4BB             8 ( 5 chars, 38% shorter )
>
>
><Hyundai  Develpoment Company in Korean> ( 6 syllables)
>U+D604 U+B300 U+C0B0 U+C5C5 U+AC1C U+BC1C
>
>DUDE-02  : 7yyEyxsEzv5AxzFy37JtssA    ( 23 )
>LDUDE     : 5syMRtAB3FB                      11 ( 12 chars, 52% shorter )
>
>
>
>
>----- Original Message -----
>From: "Keith Moore" <moore@cs.utk.edu>
>To: "Soobok Lee" <lsb@postel.co.kr>
>Cc: <idn@ops.ietf.org>; "Paul Hoffman / IMC" <phoffman@imc.org>
>Sent: Tuesday, July 10, 2001 1:37 PM
>Subject: Re: [idn] THis WG derailed ?
>
>
> > > This WG  should focus on issues of AVERAGE length of ACE lables.
> >
> > why?  do you have some evidence that this has a significant
> > effect on performance of ANY protocol?
> >
>




From owner-idn@ops.ietf.org  Tue Jul 10 02:50:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA24261
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 02:50:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Jr9C-0009Ff-00
	for idn-data@psg.com; Mon, 09 Jul 2001 23:37:26 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Jr99-0009FT-00
	for idn@ops.ietf.org; Mon, 09 Jul 2001 23:37:23 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6A6bIT06049;
	Tue, 10 Jul 2001 15:37:18 +0900 (KST)
Message-ID: <01ee01c1090b$2253ebe0$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "\"Paul Hoffman / IMC\"" <phoffman@imc.org>
References: <20010706221305.A11087@arwen.cs.berkeley.edu> <000201c108c4$a29e9a80$1001a8c0@neteka.com> <p05100312b76fe08ee6b4@[165.227.249.20]> <015401c108d8$48663320$ed1bd9d2@postel.co.kr> <p05101000b7702903d0ec@[165.227.249.20]>
Subject: [idn] overall compression efficiciency matters
Date: Tue, 10 Jul 2001 15:39:56 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Please don't worry about my strong-worded subject  "...derailed".

DUDE , in a  case, supports up to 56 han/hangeul letters
in a label (a letter repeated 56 times). if anyone ever registers it,
the median average becomes 28. Let's ignore it.

Both mean (weighted) average and mode (most frequent value) 
average are not relevant to our works, i think.  

What I mean by "average domains", is  that we should
consider overall compression efficiency for samples of 
various lengths of domains that are likely to be registered, 
not only for *rare* marginal cases of very long domains which
can mislead us to lose our right focus. That's the point.
 
And many useful DUDE-alternatives are not expensive.
Lengthy tables do not add complexity, but only require 
time for careful evaluation and preparations as that for 
nameprep and kc norm.

Soobok


----- Original Message ----- 
From: "Paul Hoffman / IMC" <phoffman@imc.org>
To: <idn@ops.ietf.org>
Sent: Tuesday, July 10, 2001 12:51 PM
Subject: Re: [idn] THis WG derailed ?


> At 9:35 AM +0900 7/10/01, Soobok Lee wrote:
> >?This WG  should focus on issues of AVERAGE length of ACE lables.
> 
> That is an opinion. There has been a different opinion of many other 
> people that the WG should focus on getting an algorithm good enough 
> for the vast majority of likely names. If you think the discussion 
> needs to be opened again, you should speak with the WG chairs. 
> However, you need to be much more specific than saying "AVERAGE".
> 
> There are three kinds of averages (mean, median, and mode); of those, 
> clearly we do not want to consider mode. How do you intend to measure 
> either mean or median? All of the ACEs proposed so far have different 
> means and medians for different scripts. They also have different 
> means and medians for names that contain characters from only one 
> script versus names that contain characters from two (such as names 
> that are based on a non-Latin script but use Latin hyphens or digits).
> 

 




From owner-idn@ops.ietf.org  Tue Jul 10 07:35:01 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA26851
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 07:35:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15JvIM-000GY0-00
	for idn-data@psg.com; Tue, 10 Jul 2001 04:03:10 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15JvII-000GXo-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 04:03:06 -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 f6AB1EP18634 for <idn@ops.ietf.org>; Tue, 10 Jul 2001 13:01:14 +0200 (MEST)
Message-Id: <200107101101.f6AB1EP18634@malmo.trab.se>
Date: Tue, 10 Jul 2001 13:04:08 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: [idn] Reality Check
To: idn@ops.ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: OvnfotbQpLrzfiB/veqZMA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Has this working group lost the contact with the real world?

All discussion is about ACE/nameprep/IDNA/backward compatibility!

What about the current real needs and the future?
What about DNS?

It looks like many think the only important thing is
backward compatibility without changing the DNS protocol/server.
Why is people talking about DNSSEC, SRV records, DNAME,..., if
nobody is going to update their DNS servers?
Why not go for a solution that updates DNS and requires upgrade
of the DNS protocol and servers?
Why should it be quicker to implement DNS in the appications and
get them to be updated faster? MIME was introduced very long time
ago and still there are a lot of mail programs that do not handle it.

What does the normal human beings of the real world expect from DNS?
The semantics of current DNS says:
- a name can have mixed upper and lower case letters
- names will be matched case insensitively
IDNA says:
- a name can only be in lower case
- names will be matched exactely
So IDNA breaks current semantics of DNS. Why not go for a solution
that works as people expect? And matches the current semantics of DNS?

I have tried to think of how I as a programmer, developer, editor and
user would handle DNS names.
An ACE-solution will result in e-mails containing lines like:
To: =?quoted-printable-encoded?= <ACE-like-user-name@ACE-domain.ACE-domain.com>
A line with a lot of different mixed encoded forms. To handle this
as a programmer you have to idetify the different parts of the line and then
for each part identify what encoding is used, and the decode each before the
line can be displayed to a user or handled in a program.
As of today I have fewer programs than I want that handles e-mail - this
is because the difficulty in programmatically handling MIME.
With ACE in domain names and something like it in user names it will be
even worse. Why could we not use something simple like having the
entire line encoded in UTF-8? Instead of having a difficult time to
parse data and a lot of different decoders I could use decode UTF-8 into my
local character set.
Many edits their html files with a text editor, or writes documents
with embedded DNS names and URLs. The only way you can expect people
to enter DNS names and URLs in those files is by using the same character
set as the rest of the text and they will not convert them into
ACE, %-encoding or other unnatural form. If we use different encodings
for all things, all software handling text files have to handle the
convertion to/from the character set of the file into the special
encoding needed for protocols. I can see lots of failures giving the
user failures they cannot understand and a lot of encoded forms getting
into the users text files, and a lot of non-encoded forms getting into
the DNS protocol. At my site clearly the simplest and best working
solution is to let my DNS server do most of the work.
While many programmes working for interoperability have code to handle
UCS to local character set conversions and have case insensitive matching,
they do not have code for things like ACE or quoted-printable.
A solution based on using UCS as transport format and matching based
on the normal "case insensitive" matching rules would make many programs
much easier to adopt to non-ASCII DNS names.
And if we used UCS only and did not use ACE as a backward compatibility
encoding, would it really be that bad? In my system the function that
might have most problems is e-mail, but that is also one of the systems
that probably can be handled easiest - I can fix my MTA and I can also
avoid using non-ascii in my mail domain to begin with. or ACE could be used
in the few places where it cannot be avoided for a transition period.

Does the IDNA (ACE in application) solution that appears be the only
focus of this working group match the real needs of people in the
current and future world?

As it feels for me, this working group is going for a solution that
is far from the simple clean handling of non-ASCII in DNS that I have
always wanted and worked for.

    Dan




From owner-idn@ops.ietf.org  Tue Jul 10 09:42:15 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA29167
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 09:42:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15JxVH-000KU8-00
	for idn-data@psg.com; Tue, 10 Jul 2001 06:24:39 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15JxVG-000KU2-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 06:24:38 -0700
Received: from CLASSIC.viagenie.qc.ca (modemcable245.48-201-24.que.mc.videotron.ca [24.201.48.245])
	by jazz.viagenie.qc.ca (Viagenie/8.11.0) with ESMTP id f6ADiV102524;
	Tue, 10 Jul 2001 09:44:31 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010710092434.035b0018@mail.viagenie.qc.ca>
X-Sender: blanchet@mail.viagenie.qc.ca
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 10 Jul 2001 09:27:07 -0400
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: Re: [idn] average length
In-Reply-To: <015401c108d8$48663320$ed1bd9d2@postel.co.kr>
References: <20010706221305.A11087@arwen.cs.berkeley.edu>
 <000201c108c4$a29e9a80$1001a8c0@neteka.com>
 <p05100312b76fe08ee6b4@[165.227.249.20]>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

changed to subject to a more appropriate one!

At/À 09:35 2001-07-10 +0900, Soobok Lee you wrote/vous écriviez:
>This WG  should focus on issues of AVERAGE length of ACE lables.

Don't understand why. Average number of octets doesn't help me.
However, the max length do change the maximum length of chars that I may use.

I probably don't understand your point.

Marc.


>We have not enough time for the debate around max ACE label length.
>We have already many useful ACE alternatives
>to overcome this 14-han barrier easily.
>
>bare DUDE produces  long and complex ACE lables for average length of
>han/hangul domains, while DUDE's algorithm seems to be simple.
>We have no justification for why we should sacrifice
>label simplicity for code simplicity,
>while we already have very HUGE mapping tables
>and algorithms in NAMEPREP and KC Norm.
>ACE codes are written once and copied and executed many times.
>Output label simplicity matters.
>
>No one has provided the right reason
>to exclude needs for the following names.
>What does it GIVE us  to ban people from registering them?
>What does ACE code simplicity give us ?
>
>Soobok
>--------------------------------------------------------------------
>
>
>ONE EVIDENCE from Chinese Gov for domains of 16 han letters.
>
>(SC1) Simplified Chinese String  1 : ( 16 letters )
>       <ministry of foreign trade and economic cooperation, PRC>
>       u+4e2d u+534e u+4eba u+6c11 u+5171 u+548c u+56fd u+5bf9
>       u+5916 u+8d38 u+6613 u+7ecf u+6d4e u+5408 u+4f5c u+90e8
>
>       DUDE-02 : w8wpt7ydt79euu4mv7yax9puzb7seu8r7wuq85umt27ntv2bv3wgt\
>                 5xe795e ( 60 chars )
>       LDUDE   : xswjuzru6nu7fv7kv4gutrwgb7mbwiu6cuzqqxm
>                 ( 39 chars, 35.0% shorter )
>       AMCW    : w8up29ps5kdst5uh7ygsup29pm3cb39n8tknpb39hkygswhdysupa\
>                 qd ( 55 chars )
>       LAMCW   : xsujwxgu3kwwrv3fwvduunykm5ab9jwvmuwfmta
>                 ( 39 chars )
>
>
>ANOTHER EVIDENCE from korean site names of 18 hangeul letters.
>
>
>(K3) Korean String 3:  ( 18 hangul syllables )
>       U+C804 U+AD6D U+C2E4 U+C9C1 U+B178 U+C219 U+C790 U+B300
>       U+CC45 U+C885 U+AD50 U+C2DC U+BBFC U+B2E8 U+CCB4 U+D611
>       U+C758 U+D68C
>
>       DUDE-02 : 62yEyxyJy92J5uFz25JzvyBx2Jzw3Az9wFw6Ayx7Fy92Nz3uA3tEz8\
>                 xNt44FttwJtt7E ( 68 chars )
>       LDUDE   : 5szAtBtvBt7Mt2Qv4Qu7KtFt5It3MuEvAtvDyJCtuC4G4J
>                 ( 46 chars,  32% shorter )
>       AMCW    : 62sEFmpKzeNqbGm2Ks3M6sG2aPcfNefFksKy6I96GziPfwRstM42Rwn
>                 ( 55 chars )
>       LAMCW   : 5stAsB5tvAGhmGmgG2mGatsE5t7JGbhsDvD5tsAyIK5swJ8RwG
>                 ( 50 chars )
>
>
>Average lenght hangeul domain:
>
>     (K4) Korean String 4:  ( 7 hangul syllables )
>       <Hynics Semiconductor in korean>
>       U+D558 U+C774 U+B2C9 U+C2A4 U+BC18 U+B3C4 U+CCB4
>
>       DUDE-02 : 7xvItuuNzx5PzsyPz85N97Nz9zA
>                 ( 27 chars )
>       LDUDE   : 5s3C4F5Q7PtwRtMK
>                 ( 16 chars,  40% shorter )
>       AMCW    : 7xxIM5wGyjKxeJa2G8ePfw
>                 ( 22 chars )
>       LAMCW   : 5s9CxH8JvE5tzMyAK
>                 ( 17 chars )
>
>
>----- Original Message -----
>From: "Paul Hoffman / IMC" <phoffman@imc.org>
>To: <idn@ops.ietf.org>
>Sent: Tuesday, July 10, 2001 7:34 AM
>Subject: Re: [idn] ACE37
>
>
> > At 6:14 PM -0400 7/9/01, Edmon wrote:
> > >the
> > >capacity for CJK ideographs, which has been identified as an undeniable
> > >concern through the discussion on this mailing list
> >
> > The fact that a few people have expressed the concern without ever
> > giving any evidence for it is not "undeniable". So far, there has
> > been *no* evidence that a 15-character limit would restrict names
> > that would be used for a significant number of real-live,
> > actually-used host names. If you have any evidence to the contrary
> > (that is, names that would actually be used in DNS names), please say
> > so ASAP.
> >
> > The concerns have all been for companies that want to register their
> > legal names. Well, the DNS will *never* allow all the companies that
> > want their legal names to do so. In the United States and throughout
> > Europe, legal company names include spaces, commas, periods,
> > apostrophes, ampersands, and so on. Those are not going to be allowed
> > in IDN names, so those companies will not be able to register their
> > legal names.
> >
> > --Paul Hoffman, Director
> > --Internet Mail Consortium
> >





From owner-idn@ops.ietf.org  Tue Jul 10 09:47:49 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA29259
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 09:47:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15JxV9-000KU0-00
	for idn-data@psg.com; Tue, 10 Jul 2001 06:24:31 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15JxV7-000KTt-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 06:24:29 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA25949;
        Tue, 10 Jul 2001 09:24:22 -0400 (EDT)
Message-Id: <200107101324.JAA25949@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Soobok Lee" <lsb@postel.co.kr>
cc: idn@ops.ietf.org, "\"Keith Moore\"" <moore@cs.utk.edu>
Subject: Re: [idn] THis WG derailed ? 
In-reply-to: Your message of "Tue, 10 Jul 2001 14:50:59 +0900."
             <01dc01c10904$4e1c9620$ed1bd9d2@postel.co.kr> 
Date: Tue, 10 Jul 2001 09:24:22 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> How much time  do you expect  to be taken
> in order to improve or replace DUDE ?
> 1 week or 1 month of delay?  That's too long to wait for?

Based on long experience with IETF working groups, if people
don't like the idea almost immediately, the additional time
spent debating the details can require six to eighteen months.
I'm not exaggerating.  Groups get very slow after they've been
around a while.

and yes, that's too long to wait.



From owner-idn@ops.ietf.org  Tue Jul 10 09:53:04 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA29434
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 09:53:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15JxfH-000KoA-00
	for idn-data@psg.com; Tue, 10 Jul 2001 06:34:59 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15JxfF-000Ko4-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 06:34:57 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6ADYmT15755
	for <idn@ops.ietf.org>; Tue, 10 Jul 2001 22:34:48 +0900 (KST)
Message-ID: <027401c10945$6c2d8340$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Subject: [idn] chinese/hangul ML.com statistics with DUDE/LDUDE
Date: Tue, 10 Jul 2001 22:37:10 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

  
The next table is from
285108 chinese ML.com samples (old raw data from VGRS). 
 
"COMP" column includes improvement ratios of LDUDE over DUDE.
"Y" column points that  for long chinese domains, LDUDE's label
length is close to (2.0~2.5)*(input domain length).


N:            length of a domain label ( # of code points)
FREQ:         number domains of length N
SUM OF DUDE:  sum of lengths of DUDE labels
X:            SUM OF DUDE / N * FREQ
SUM OF LDUDE: sum of lengths of LDUDE labels
Y:            SUM OF LDUDE / N * FREQ
COMP:         (SUM OF LDUDE - SUM OF DUDE) / SUM OF DUDE * 100

|  N|    FREQ|    N*FREQ|  SUM OF DUDE(X)| SUM OF LDUDE(Y)| COMP|

|  1|    4642|      4642|     18568(4.00)|     18568(4.00)| 0.00|
|  2|   59708|    119416|    462031(3.87)|    415599(3.48)|10.05|
|  3|   49471|    148413|    566440(3.82)|    477649(3.22)|15.68|
|  4|   99402|    397608|   1509929(3.80)|   1168378(2.94)|22.62|
|  5|   29974|    149870|    554237(3.70)|    426226(2.84)|23.10|
|  6|   20809|    124854|    457412(3.66)|    333416(2.67)|27.11|
|  7|    8860|     62020|    220880(3.56)|    160563(2.59)|27.31|
|  8|    5251|     42008|    146822(3.50)|    103903(2.47)|29.23|
|  9|    2666|     23994|     81433(3.39)|     58657(2.44)|27.97|
| 10|    2008|     20080|     68385(3.41)|     46708(2.33)|31.70|
| 11|     859|      9449|     31596(3.34)|     22111(2.34)|30.02|
| 12|     671|      8052|     27039(3.36)|     18135(2.25)|32.93|
| 13|     346|      4498|     14306(3.18)|     10088(2.24)|29.48|
| 14|     235|      3290|     10676(3.24)|      7230(2.20)|32.28|
| 15|     117|      1755|      5568(3.17)|      3854(2.20)|30.78|
| 16|      68|      1088|      3383(3.11)|      2376(2.18)|29.77|
| 17|      21|       357|      1075(3.01)|       750(2.10)|30.23|

|   |  285108|   1121394|   4179780(3.73)|   3274211(2.92)|21.67|



The next table is  
From 207207 hangul ML.com samples (old raw data from VGRS). 

|  N|    FREQ|    N*FREQ|  SUM OF DUDE(X)| SUM OF LDUDE(Y)| COMP|

|  1|    1941|      1941|      7764(4.00)|      7764(4.00)|0.00|
|  2|   16978|     33956|    129239(3.81)|    111308(3.28)|13.87|
|  3|   38852|    116556|    436845(3.75)|    341333(2.93)|21.86|
|  4|   61642|    246568|    915355(3.71)|    653736(2.65)|28.58|
|  5|   40375|    201875|    743090(3.68)|    502097(2.49)|32.43|
|  6|   24561|    147366|    540245(3.67)|    349710(2.37)|35.27|
|  7|   13034|     91238|    332964(3.65)|    211206(2.31)|36.57|
|  8|    5596|     44768|    162833(3.64)|    100618(2.25)|38.21|
|  9|    2421|     21789|     78945(3.62)|     48633(2.23)|38.40|
| 10|    1033|     10330|     36144(3.50)|     22323(2.16)|38.24|
| 11|     427|      4697|     16744(3.56)|     10259(2.18)|38.73|
| 12|     173|      2076|      7178(3.46)|      4578(2.21)|36.22|
| 13|      96|      1248|      4386(3.51)|      2725(2.18)|37.87|
| 14|      32|       448|      1656(3.70)|      1006(2.25)|39.25|
| 15|      22|       330|      1168(3.54)|       750(2.27)|35.79|
| 16|      15|       240|       757(3.15)|       529(2.20)|30.12|
| 17|       8|       136|       470(3.46)|       299(2.20)|36.38|
| 19|       1|        19|        30(1.58)|        30(1.58)|0.00|

|   |  207207|    925581|   3415813(3.69)|   2368904(2.56)|30.65|









From owner-idn@ops.ietf.org  Tue Jul 10 10:10:31 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA29885
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 10:10:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Jy2A-000LaE-00
	for idn-data@psg.com; Tue, 10 Jul 2001 06:58:38 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Jy28-000La8-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 06:58:36 -0700
Received: from bbthead.dcrocker.net (inetgw.il.neustar.com [209.173.57.225])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id GAA23059;
	Tue, 10 Jul 2001 06:58:24 -0700
Message-Id: <5.1.0.14.2.20010710075847.02190910@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 10 Jul 2001 08:02:39 -0400
To: "Soobok Lee" <lsb@postel.co.kr>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] THis WG derailed ? 
Cc: <idn@ops.ietf.org>
In-Reply-To: <01bf01c108fd$22731500$ed1bd9d2@postel.co.kr>
References: <200107100437.AAA23564@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 12:59 AM 7/10/2001, Soobok Lee wrote:
>I think shorter ACE labels benefits  :
>  1. save momory resources
>
>  2. reduce traffic

#1 and #2 are correct, theoretically but not practically.  That is, it is 
valid to claim that one string being a single character shorter than 
another character can save resources.  However practical system behavior 
will show no measurable difference between the two.

In fact there is a very strong argument which says that packet- or 
datagram-oriented systems are entirely dominated by the overhead of 
processing a data segment, rather than the length of the segment.


>   3. for human

All of the proposed encoding schemes are horrible for humans.

d/


----------
Dave Crocker  <mailto:dcrocker@brandenburg.com>
Brandenburg InternetWorking  <http://www.brandenburg.com>
tel +1.408.246.8253;  fax +1.408.273.6464




From owner-idn@ops.ietf.org  Tue Jul 10 10:43:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA01700
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 10:43:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15JyUF-000MWr-00
	for idn-data@psg.com; Tue, 10 Jul 2001 07:27:39 -0700
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15JyUD-000MWl-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 07:27:37 -0700
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00728;
	Tue, 10 Jul 2001 10:26:44 -0400 (EDT)
Message-Id: <200107101426.KAA00728@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: idn@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [idn] I-D ACTION:draft-ietf-idn-lsb-ace-01.txt
Date: Tue, 10 Jul 2001 10:26:44 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internationalized Domain Name Working Group of the IETF.

	Title		: Improving ACE using code point reordering v0.9
	Author(s)	: S. Lee
	Filename	: draft-ietf-idn-lsb-ace-01.txt
	Pages		: 
	Date		: 09-Jul-01
	
This document describes code point reordering to improve ACE 
compression algorithms. Based on frequency statistics of characater
sets, this reordering is easily implemented with simple character 
mapping tables.
DUDE implementation of this idea shows great improvements for
Hangul, Chineses, Vietnamese and European domains.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idn-lsb-ace-01.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-idn-lsb-ace-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-idn-lsb-ace-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010709103720.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idn-lsb-ace-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idn-lsb-ace-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010709103720.I-D@ietf.org>

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Tue Jul 10 11:19:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03307
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 11:19:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Jyju-000N3s-00
	for idn-data@psg.com; Tue, 10 Jul 2001 07:43:50 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Jyjs-000N3f-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 07:43:48 -0700
Received: from enoshima (i205162.ppp.asahi-net.or.jp [61.125.205.162])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id XAA12127;
	Tue, 10 Jul 2001 23:43:49 +0900 (JST)
Message-Id: <4.2.0.58.J.20010710234039.00d19e70@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 10 Jul 2001 23:43:14 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] chinese/hangul ML.com statistics with DUDE/LDUDE
In-Reply-To: <027401c10945$6c2d8340$ed1bd9d2@postel.co.kr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 22:37 01/07/10 +0900, Soobok Lee wrote:
>
>The next table is from
>285108 chinese ML.com samples (old raw data from VGRS).

Can you explain what you sampled (i.e. how you extracted
the words,..?).

On the other hand, maybe I shouldn't ask, because this looks
more and more like a PhD on the subject rather than like
practical engineering.

Regards,   Martin.






From owner-idn@ops.ietf.org  Tue Jul 10 11:38:35 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA04122
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 11:38:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15JzNL-000P0a-00
	for idn-data@psg.com; Tue, 10 Jul 2001 08:24:35 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15JzNJ-000P0P-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 08:24:33 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6AFORT23029;
	Wed, 11 Jul 2001 00:24:27 +0900 (KST)
Message-ID: <02d001c10954$b975ea20$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <4.2.0.58.J.20010710234039.00d19e70@sh.w3.mag.keio.ac.jp>
Subject: Re: [idn] chinese/hangul ML.com statistics with DUDE/LDUDE
Date: Wed, 11 Jul 2001 00:26:42 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Simple RACE decoding on ML.com samples
produces the original code points, which are then fed into
DUDE.   
If you are interested in how I get the samples,
send me a personal email. (VGRS people knows that :-)).

Regards,

Soobok


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
Sent: Tuesday, July 10, 2001 11:43 PM
Subject: Re: [idn] chinese/hangul ML.com statistics with DUDE/LDUDE


> At 22:37 01/07/10 +0900, Soobok Lee wrote:
> >
> >The next table is from
> >285108 chinese ML.com samples (old raw data from VGRS).
> 
> Can you explain what you sampled (i.e. how you extracted
> the words,..?).
> 
> On the other hand, maybe I shouldn't ask, because this looks
> more and more like a PhD on the subject rather than like
> practical engineering.
> 
> Regards,   Martin.
> 
> 
> 




From owner-idn@ops.ietf.org  Tue Jul 10 11:38:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA04133
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 11:38:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15JzRK-000PBS-00
	for idn-data@psg.com; Tue, 10 Jul 2001 08:28:42 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15JzRJ-000PBJ-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 08:28:41 -0700
Received: from enoshima (i205162.ppp.asahi-net.or.jp [61.125.205.162])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id AAA12432;
	Wed, 11 Jul 2001 00:25:17 +0900 (JST)
Message-Id: <4.2.0.58.J.20010710234410.05ed44e0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 11 Jul 2001 00:23:48 +0900
To: Dan Oscarsson <Dan.Oscarsson@trab.se>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Reality Check
Cc: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>,
        James Seng/Personal <jseng@POBOX.ORG.SG>
In-Reply-To: <200107101101.f6AB1EP18634@malmo.trab.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hello Dan, others,

At 13:04 01/07/10 +0200, Dan Oscarsson wrote:
>Has this working group lost the contact with the real world?
>
>All discussion is about ACE/nameprep/IDNA/backward compatibility!

>I have tried to think of how I as a programmer, developer, editor and
>user would handle DNS names.
>An ACE-solution will result in e-mails containing lines like:
>To: =?quoted-printable-encoded?= 
><ACE-like-user-name@ACE-domain.ACE-domain.com>
>A line with a lot of different mixed encoded forms. To handle this
>as a programmer you have to idetify the different parts of the line and then
>for each part identify what encoding is used, and the decode each before the
>line can be displayed to a user or handled in a program.
>As of today I have fewer programs than I want that handles e-mail - this
>is because the difficulty in programmatically handling MIME.
>With ACE in domain names and something like it in user names it will be
>even worse. Why could we not use something simple like having the
>entire line encoded in UTF-8? Instead of having a difficult time to
>parse data and a lot of different decoders I could use decode UTF-8 into my
>local character set.

This is a subject I have partially discussed with Keith earlier.
I think it's indeed very serious. There are thousands of different
file formats and occasions where domain names turn up. If ACE leaks
into only a small percentage of them, a lot of people have a lot
of problems. They may complain about ACE more than Keith is
complaining about NAT.

Practical books about a programming language often contain examples
of how to process your mail, and so on. All these examples are based
on the fact that the characters can be parsed directly. Grepping
for a word in the subject headers in a mail spool file is easy as long
as the subject is in ASCII. For anything beyond ASCII, it just fails.

I remember Ulrich Drepper, responsible for gclib, saying at a dinner
here in Japan that UTF-8 was the right way to go, because it would
allow people like him to provide the base for internationalization
(rather than just doing nothing at all), and would allow others,
more familiar with their own language, to build on it. In some sense,
RFC 2277 is based on a similar assumption. ACE severely breaks this
assumption.

Internationalization doesn't come for free. Most people who think
ACE is a good idea just don't see that work. In the short term,
having to update a DNS server (even if it's just with an 8-bit
clean version) seems a lot of work. But it's actually extremely
easy, compared to updating applications. Also, passing ACE in
application protocols seems extremely easy. But it just means
that these application protocols aren't really internationalized
yet, and that a lot of work is waiting out there.


>Many edits their html files with a text editor, or writes documents
>with embedded DNS names and URLs. The only way you can expect people
>to enter DNS names and URLs in those files is by using the same character
>set as the rest of the text and they will not convert them into
>ACE, %-encoding or other unnatural form.

Yes indeed. Please see
http://www.ietf.org/internet-drafts/draft-masinter-url-i18n-07.txt
for URIs (working on updating it) and
http://www.ietf.org/internet-drafts/draft-ietf-idn-uri-00.txt
for the DNS part in URIs (will resubmit it to keep it alive;
I don't expect this to be discussed in London, but I haven't
seen any other proposals for how to solve this part of the
problem, and I guess the WG should deal with it once the
important issues are dealt with, and it would look silly
to resubmit as a personal contribution and later again
as a WG draft [sorry for this lengthy sentence]).


>Does the IDNA (ACE in application) solution that appears be the only
>focus of this working group match the real needs of people in the
>current and future world?

No. People will suffer from ACE for years to come. When MIME
was created, Unicode barely existed, so there was some excuse.
But there is no excuse for ACE. I wish I had patented it in
December 1996; all bad ideas should be patented ;-(.


Regards,   Martin.






From owner-idn@ops.ietf.org  Tue Jul 10 14:48:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA14334
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 14:48:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15K2Jw-0005Jr-00
	for idn-data@psg.com; Tue, 10 Jul 2001 11:33:16 -0700
Received: from [152.160.20.25] (helo=admin1.corp.walid.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15K2Ju-0005I9-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 11:33:14 -0700
Received: from CHOAM (admin1.corp.walid.com [152.160.20.25])
	by admin1.corp.walid.com (8.11.2/8.11.2) with SMTP id f6AIK6G02581;
	Tue, 10 Jul 2001 18:20:06 GMT
From: "Brian W. Spolarich" <briansp@walid.com>
To: "Dan Oscarsson" <Dan.Oscarsson@trab.se>, <idn@ops.ietf.org>
Subject: RE: [idn] Reality Check
Date: Tue, 10 Jul 2001 14:28:47 -0400
Message-ID: <FJEPLIJJEDBNPIOAEIHDKEDGCGAA.briansp@walid.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
In-Reply-To: <200107101101.f6AB1EP18634@malmo.trab.se>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


| What does the normal human beings of the real world expect from DNS?
| The semantics of current DNS says:
| - a name can have mixed upper and lower case letters
| - names will be matched case insensitively
| IDNA says:
| - a name can only be in lower case
| - names will be matched exactely
| So IDNA breaks current semantics of DNS.

  This isn't an entirely correct statement.  Names after nameprep are folded
to lower case for purposes of comparison to ensure that the
case-insensitivity requirement is preserved.  Users can enter names in mixed
case, and nameprep+a case preserving ACE could preserve this in the ACEd
name.  These semantics are essentially preserved in the current
IDNA+nameprep+DUDE recommendation, and could be enhanced to preserve case in
the ACE->IDN conversion step.

  Dan, you've mentioned elsewhere in this message that the IDNA approach is
flawed because it assumes that no one wants to update their DNS servers.

  IDN is not a DNS problem.  It is an applications-that-use-the-DNS problem.

  Given that you're going to have to update many applications to properly
handle IDNs, why not only update the applications?

  I think one area where the IDNA document currently falls down is in not
providing enough discussion on where IDNs will be in native form and where
they will be in ACE form.  I think much of the confusion in this discussion
arises from that point.

  -bws




From owner-idn@ops.ietf.org  Tue Jul 10 15:31:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA16669
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 15:31:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15K32B-0006re-00
	for idn-data@psg.com; Tue, 10 Jul 2001 12:18:59 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15K329-0006rJ-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 12:18:57 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15K329-0000KV-00; Tue, 10 Jul 2001 12:18:57 -0700
Date: Tue, 10 Jul 2001 19:18:56 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Reality Check
Message-ID: <20010710191856.A943@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4.2.0.58.J.20010710234410.05ed44e0@sh.w3.mag.keio.ac.jp> <200107101101.f6AB1EP18634@malmo.trab.se>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dan Oscarsson <Dan.Oscarsson@trab.se> wrote:

> What about DNS?

What about DNS?  How DNS works just doesn't matter very much, because
it's invisible to everything except the resolver, which can offer any
combination of interfaces to applications (including ASCII, ACE, UTF-8,
and the local charset) regardless of what actually appears on the wire
between the resolver and the DNS server.  We can define a way for DNS to
use UTF-8 now, or later, or never, and I really don't think it will make
much difference to anything.

What matters much more than DNS are all the other protocols that
embed domain names in messages (RFC 2822, SMTP, URIs, HTTP cookies,
SSL certificates, SSH keys, PGP keys, etc).  Maybe these should all
be upgraded to support UTF-8 domain names, and maybe they all will be
eventually, but that could take a long time.  We need ACE to be an
option (in addition to UTF-8), at least for a while.

> Why should it be quicker to implement DNS in the applications and get
> them to be updated faster?

Huh?  I don't think anyone is suggesting this.  DNS should be
implemented in the resolver, as it always has been.  Applications are
going to need to be updated to support nameprep if they want to compare
names, and they are going to need to be updated to support UTF-8 if they
want to display IDNs returned from a UTF-8 resolver or pass user-entered
names to a UTF-8 resolver.  This is true regardless of whether the
protocols (email etc.) use ACE or UTF-8.

> MIME was introduced very long time ago and still there are a lot of
> mail programs that do not handle it.

Good point.  Do you think an extension to RFC 2822 to allow UTF-8 domain
names is going to be supported much more quickly?  I wouldn't count on
it.

> What does the normal human beings of the real world expect from DNS?
> The semantics of current DNS says:
> - a name can have mixed upper and lower case letters
> - names will be matched case insensitively
> IDNA says:
> - a name can only be in lower case
> - names will be matched exactly
> So IDNA breaks current semantics of DNS.

No, IDNA does not say that.  Application protocols can transmit
names in non-nameprep'd mixed-case form.  Applications can store
and display names in non-nameprep'd mixed-case form.  The only
time it is necessary to apply nameprep is just before comparing
two names.  Nameprep is mainly just a way to do case-insensitive
alternate-represenation-insensitive comparisons.

In DNS, in order to perform case-insensitive name comparisons, the
server must perform case-folding, or it must rely on the client to do
it.  It makes no semantic difference whether it's done on the server or
the client, but doing it on the client is better for load balancing,
since case-folding expensive and there are more clients than servers.

As for the names returned from the DNS server, there are two ways to get
the full mixed-case name, either of which will work:  First, DNS could
return both the nameprep'd ACE name and the non-nameprep'd UTF-8 name,
and the application could use whichever one it prefers (IDN-unaware
applications would automatically get the nameprep'd ACE name) (maybe
there could be an optional flag in the request to tell the server not
to bother with the ACE name, as an optimization).  Second, all the ACEs
currently under consideration can represent mixed-case Unicode strings
as mixed-case ACE strings.

> Why could we not use something simple like having the entire line
> encoded in UTF-8?

We could, eventually.  But if you want to send mail to your friend with
an IDN address and also to your other friend whose ISP/employer/school
does not yet use a UTF-8-aware MTA, then you need ACE.

Martin Duerst <duerst@w3.org> wrote:

> Practical books about a programming language often contain examples
> of how to process your mail, and so on.  All these examples are based
> on the fact that the characters can be parsed directly.  Grepping for
> a word in the subject headers in a mail spool file is easy as long as
> the subject is in ASCII.  For anything beyond ASCII, it just fails.

Yes, and this argues for some other working group to define an extension
to RFC 2822 that uses UTF-8 instead of ACE and MIME encoded-strings.
And one of the first places this extension would get used would be, not
on the wire, but in mailbox files, because the interoperability issues
are less severe there.  Eventually this format might get deployed for
on-the-wire use.  This extension is already motivated by Subject fields,
but the demand hasn't been enough for the extension to appear.  Maybe
after IDNs become common the demand for this RFC 2822 extension will
become great enough, but I don't see how IDNs can get off the ground
without ACE.

In summary, I think applications should use UTF-8 when possible, but
ACE must be an option to allow interoperability with existing protocols
that require LDH characters.  It hardly matters what DNS uses.  Nameprep
should be thought of as the mechanism for comparing IDNs, analagous to
the case-insensitive ASCII comparison currently used for LDH names.

AMC



From owner-idn@ops.ietf.org  Tue Jul 10 16:13:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA20881
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 16:13:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15K3ia-0008O9-00
	for idn-data@psg.com; Tue, 10 Jul 2001 13:02:48 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15K3iZ-0008O3-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 13:02:47 -0700
Received: from CLASSIC.viagenie.qc.ca (classic.viagenie.qc.ca [206.123.31.136])
	by jazz.viagenie.qc.ca (Viagenie/8.11.0) with ESMTP id f6AKN0109354
	for <idn@ops.ietf.org>; Tue, 10 Jul 2001 16:23:00 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010710153939.02008e88@mail.viagenie.qc.ca>
X-Sender: blanchet@mail.viagenie.qc.ca
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 10 Jul 2001 15:42:42 -0400
To: idn@ops.ietf.org
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: [idn] wg administrativia
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

- current slot time (_may_ change: it already changes one time) for London:

THURSDAY, August 9, 2001
>1300-1500 Afternoon Sessions I
>APP     opes            Open Pluggable Edge Services WG
>INT     idn             Internationalized Domain Name WG
>OPS     aaa             Authentication, Authorization and Accounting WG
>OPS     hubmib          Ethernet Interfaces and Hub MIB WG
>SEC     kink            Kerberized Internet Negotiation of Keys WG
>TSV     mmusic          Multiparty Multimedia Session Control WG


- if you would like to make a presentation at London IETF, please send 
email to co-chairs (jseng@pobox.org.sg,marc.blanchet@viagenie.qc.ca) with 
the following information:

Title:
Name:
Requested duration:
Draft name:


- July 13 - Internet Draft Cut-off for initial document (-00) submission at 
17:00 ET

- July 20 - Internet Draft final submission cutoff date at 1700 ET

- WG pool deadline: July 13th.

Marc.




From owner-idn@ops.ietf.org  Tue Jul 10 16:28:23 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA22023
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 16:28:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15K3og-0008b6-00
	for idn-data@psg.com; Tue, 10 Jul 2001 13:09:06 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15K3od-0008ac-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 13:09:03 -0700
Message-ID: <009c01c1097c$e0a096e0$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: <idn@ops.ietf.org>, "Adam M. Costello" <amc@cs.berkeley.edu>
References: <20010710191856.A943@arwen.cs.berkeley.edu>
Subject: Re: [idn] Reality Check
Date: Tue, 10 Jul 2001 16:14:07 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

From: "Adam M. Costello" <amc@cs.berkeley.edu>
> In summary, I think applications should use UTF-8 when possible, but
> ACE must be an option to allow interoperability with existing protocols
> that require LDH characters.

Currently, IDNA does not provide the "option" for UTF-8 that you are
suggesting.  Do you think it is appropriate therefore that there be a
mechanism whereby an application can choose to use either the UTF8 or ACE
form of an IDN depending on the compliancy of the destination server?  This
ensures that once the other components or protocols become UTF8 compliant,
the DNS will not be stuck with ACE.

Edmon




From owner-idn@ops.ietf.org  Tue Jul 10 17:00:23 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA24118
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 17:00:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15K4OC-0009m6-00
	for idn-data@psg.com; Tue, 10 Jul 2001 13:45:48 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15K4OB-0009m0-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 13:45:47 -0700
Message-ID: <00b301c10982$02eefde0$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: <idn@ops.ietf.org>, "Adam M. Costello" <amc@cs.berkeley.edu>
References: <20010709230408.B9469@arwen.cs.berkeley.edu>
Subject: Re: [idn] ACE37
Date: Tue, 10 Jul 2001 16:50:52 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

From: "Adam M. Costello" <amc@cs.berkeley.edu>
> Edmon <edmon@neteka.com> wrote:
>
> > I think the point I am trying to make is that ACE37 greatly increases
> > the capacity for CJK ideographs
>
> Yes, it certainly does (and also reduces the capacity for non-CJK
> characters).
>

Agreed.  From the discussions here however, it seems that CJK capacity is of
more concern than non-CJK.  I have heard quite a few raise the issue that 15
characters for CJK is not enough, but I think generally, non-CJK having ~30
codepoint capacity is ok.  Also this was suggested by the ACE design team.

> > without requiring a complex algorithm
>
> I agree that the amount of complexity it adds to DUDE is not great, but
> I think it's comparable to the amount of complexity that AMC-ACE-W adds
> to DUDE.  DUDE does not have six different patterns, it has only one
> pattern, because they're all handled by the same logic:
>
Yes, I agree that there is an amount of complexity added to DUDE, and you
also agree that the amount is small.
Additionally, ACE37 maintains the one-mode system that I think is comparably
less complex than a separate state machine that is required by AMC-ACE-W.

Edmon





From owner-idn@ops.ietf.org  Tue Jul 10 17:01:35 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA24170
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 17:01:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15K4OU-0009nc-00
	for idn-data@psg.com; Tue, 10 Jul 2001 13:46:06 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15K4OT-0009nQ-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 13:46:05 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15K4OS-0000UZ-00; Tue, 10 Jul 2001 13:46:04 -0700
Date: Tue, 10 Jul 2001 20:46:04 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Reality Check
Message-ID: <20010710204604.B943@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <009c01c1097c$e0a096e0$1001a8c0@neteka.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Edmon <edmon@neteka.com> wrote:

> Do you think it is appropriate therefore that there be a mechanism
> whereby an application can choose to use either the UTF8 or ACE form
> of an IDN depending on the compliancy of the destination server?

The application does not talk to the DNS server.  The application talks
to the resolver, and the resolver talks to the DNS server.  The DNS
protocol matters to servers and resolvers, but not applications.  (Am I
wrong about this?  Are there applications that speak DNS directly?  More
than a negligible number of them?)

> This ensures that once the other components or protocols become UTF8
> compliant, the DNS will not be stuck with ACE.

I have no objection to defining a UTF-8 extension for DNS, but I don't
see how it will have much impact on applications, and I certainly
don't see any urgency.  IDN deployment can commence as soon as IDNA is
finalized and approved, while the DNS extension can be rolled out soon
after, or much later, with the same chance of success either way.

Perhaps the people focused on the DNS protocol should redirect their
attention to the resolver API, because that's where you can help
applications.  This API is already being changed to support IPv6 (see
RFC 2553), so I'd suggest coordinating with that effort.

AMC



From owner-idn@ops.ietf.org  Tue Jul 10 17:18:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA24968
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 17:18:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15K4XO-000A6p-00
	for idn-data@psg.com; Tue, 10 Jul 2001 13:55:18 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15K4XN-000A6j-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 13:55:17 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15K4XM-0000W9-00; Tue, 10 Jul 2001 13:55:16 -0700
Date: Tue, 10 Jul 2001 20:55:16 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] ACE37
Message-ID: <20010710205516.C943@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00b301c10982$02eefde0$1001a8c0@neteka.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Edmon <edmon@neteka.com> wrote:

> Additionally, ACE37 maintains the one-mode system that I think is
> comparably less complex than a separate state machine that is required
> by AMC-ACE-W.

Then you will like AMC-ACE-Z better than AMC-ACE-W, because it is
a one-mode system with fewer state variables.  Compared to ACE37,
AMC-ACE-Z is more subtle but requires less code to implement (I think),
is equally efficient for Han, and much more efficient for all other
scripts.

http://www.cs.berkeley.edu/~amc/charset/amc-ace-z.gz

I'm in the process of cleaning up the presentation.  I'll submit an
internet draft soon.

AMC



From owner-idn@ops.ietf.org  Tue Jul 10 17:37:41 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA25808
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 17:37:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15K54u-000BA7-00
	for idn-data@psg.com; Tue, 10 Jul 2001 14:29:56 -0700
Received: from [152.160.20.25] (helo=admin1.corp.walid.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15K54s-000B9p-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 14:29:54 -0700
Received: from CHOAM (admin1.corp.walid.com [152.160.20.25])
	by admin1.corp.walid.com (8.11.2/8.11.2) with SMTP id f6ALMsG07049;
	Tue, 10 Jul 2001 21:22:54 GMT
From: "Brian W. Spolarich" <briansp@walid.com>
To: "Adam M. Costello" <amc@cs.berkeley.edu>, <idn@ops.ietf.org>
Subject: RE: [idn] Reality Check
Date: Tue, 10 Jul 2001 17:31:37 -0400
Message-ID: <FJEPLIJJEDBNPIOAEIHDEEDOCGAA.briansp@walid.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
In-Reply-To: <20010710204604.B943@arwen.cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


| The application does not talk to the DNS server.  The application talks
| to the resolver, and the resolver talks to the DNS server.  The DNS
| protocol matters to servers and resolvers, but not applications.  (Am I
| wrong about this?  Are there applications that speak DNS directly?  More
| than a negligible number of them?)

  MTAs (sendmail, etc.) generate MX lookups directly instead of through the
resolver.

  DNS tools such as dnsquery and dig (and the venerable but deprecated
nslookup) generate their DNS packets directly, but aren't really much of an
issue (and can be easily wrapped).

  Anything that uses DNS data but doesn't do get{host|node}by{name|addr}
doesn't use the system resolver.

  -bws




From owner-idn@ops.ietf.org  Tue Jul 10 17:43:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA25934
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 17:43:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15K59D-000BOc-00
	for idn-data@psg.com; Tue, 10 Jul 2001 14:34:23 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15K59B-000BOV-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 14:34:21 -0700
Message-ID: <00cf01c10988$cb97a5c0$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: <idn@ops.ietf.org>, "Adam M. Costello" <amc@cs.berkeley.edu>
References: <20010710204604.B943@arwen.cs.berkeley.edu>
Subject: Re: [idn] Reality Check
Date: Tue, 10 Jul 2001 17:39:23 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

From: "Adam M. Costello" <amc@cs.berkeley.edu>
> The application does not talk to the DNS server.  The application talks
> to the resolver, and the resolver talks to the DNS server.  The DNS
> protocol matters to servers and resolvers, but not applications.  (Am I
> wrong about this?

What I meant was the application using the DNS information then
communicating to a destination server such as an http server.  That is,
after they obtain an RR from the DNS, how they use the information to then
connect with the destination.  Should we not allow this to be in UTF8 in the
future?

> > This ensures that once the other components or protocols become UTF8
> > compliant, the DNS will not be stuck with ACE.
>
> I have no objection to defining a UTF-8 extension for DNS, but I don't
> see how it will have much impact on applications, and I certainly
> don't see any urgency.  IDN deployment can commence as soon as IDNA is
> finalized and approved, while the DNS extension can be rolled out soon
> after, or much later, with the same chance of success either way.

I think it is important that a UTF-8 extension is available either in
parallel or soon after, or there is a greater risk that we wont see an
upgrade anytime soon.

> Perhaps the people focused on the DNS protocol should redirect their
> attention to the resolver API, because that's where you can help
> applications.  This API is already being changed to support IPv6 (see
> RFC 2553), so I'd suggest coordinating with that effort.

Are you suggesting then that the discussion on using a UTF8 extension for
IDN in the DNS would be outside the scope of the IDN wg?

Edmon




From owner-idn@ops.ietf.org  Tue Jul 10 18:15:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA27066
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 18:15:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15K5b6-000CNJ-00
	for idn-data@psg.com; Tue, 10 Jul 2001 15:03:12 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15K5b5-000CND-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 15:03:11 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15K5b4-0000cK-00; Tue, 10 Jul 2001 15:03:10 -0700
Date: Tue, 10 Jul 2001 22:03:10 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Reality Check
Message-ID: <20010710220310.E943@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00cf01c10988$cb97a5c0$1001a8c0@neteka.com> <FJEPLIJJEDBNPIOAEIHDEEDOCGAA.briansp@walid.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

"Brian W. Spolarich" <briansp@walid.com> wrote:

> MTAs (sendmail, etc.) generate MX lookups directly instead of through
> the resolver.
>
> Anything that uses DNS data but doesn't do get{host|node}by{name|addr}
> doesn't use the system resolver.

Okay, thanks.  It sounds like there are indeed some significant
applications that speak DNS directly, but going through the resolver
is by far the common case.  (Hmmm, now that I think about it, I bet
the inability of the resolver to provide access to arbitrary resource
records is the main reason why so few resource records have been
deployed.)

Edmon <edmon@neteka.com> wrote:

> What I meant was the application using the DNS information then
> communicating to a destination server such as an http server.  That
> is, after they obtain an RR from the DNS, how they use the information
> to then connect with the destination.  Should we not allow this to be
> in UTF8 in the future?

I don't follow.  The application gets the domain name from the user or
an href attribute or wherever (not from DNS).  The application hands
the domain name to the resolver, and gets back an IP address.  The
application then opens a TCP connection to that IP address and sends the
HTTP request, which includes the original domain name but not anything
that came back from DNS.

In some other scenarios, applications might indeed receive domain
names from DNS and copy them into application messages.  But the
application is almost always getting the name from the resolver, not
from DNS directly.  Therefore, if you want to make things easier for
the application by giving it UTF-8 domain names, you need a resolver
interface that can return UTF-8 when invited to do so by the application
(but the resolver should return UTF-8 only if explicitly invited by the
application, otherwise it will break existing applications).  Once you
have a UTF-8 resolver interface, it doesn't matter what protocol is
running between the resolver and the DNS server, because the application
can get UTF-8 from the resolver regardless.

> Are you suggesting then that the discussion on using a UTF8 extension
> for IDN in the DNS would be outside the scope of the IDN wg?

Not at all.  I am suggesting that if your goal is to make life easier
for application programmers by allowing them to use UTF-8 internally
and never use ACE, then the way to accomplish that goal is to extend
the resolver interface.  You can also change DNS, but that is less
helpful to applications (it mostly affects resolvers and DNS servers)
and therefore less urgent.

AMC



From owner-idn@ops.ietf.org  Tue Jul 10 18:30:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA27648
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 18:30:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15K5kX-000ChD-00
	for idn-data@psg.com; Tue, 10 Jul 2001 15:12:57 -0700
Received: from spider.nic-se.se ([212.247.3.67])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15K5kV-000Ch6-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 15:12:55 -0700
Received: from localhost (dufberg@localhost)
	by spider.nic-se.se (8.11.1/8.11.1) with ESMTP id f6AMCCb09871;
	Wed, 11 Jul 2001 00:12:12 +0200 (CEST)
X-Authentication-Warning: spider.nic-se.se: dufberg owned process doing -bs
Date: Wed, 11 Jul 2001 00:12:11 +0200 (CEST)
From: Mats Dufberg <dufberg@nic-se.se>
To: "Adam M. Costello" <amc@cs.berkeley.edu>
cc: <idn@ops.ietf.org>
Subject: Re: [idn] Reality Check
In-Reply-To: <20010710220310.E943@arwen.cs.berkeley.edu>
Message-ID: <Pine.BSF.4.30.0107110005580.8353-100000@spider.nic-se.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Tue, 10 Jul 2001, Adam M. Costello wrote:

> Okay, thanks.  It sounds like there are indeed some significant
> applications that speak DNS directly, but going through the resolver
> is by far the common case.  (Hmmm, now that I think about it, I bet
> the inability of the resolver to provide access to arbitrary resource
> records is the main reason why so few resource records have been
> deployed.)

The destinction between resolver and (authoritative) nameserver is not as
sharp as might seems. In fact, the responses from both are the same,
except for the aa flag. Often, an nameserver is used for both types of
services, typically authoritative for the local domain and resolver for
the local net. If ACE is used for IDN, then both resolvers and
authoritative servers must give respones with the same encoding.


Mats

-----------------------------------------------------------------
Mats Dufberg                                     +46-8-545 857 06
dufberg@nic-se.se                           fax: +46-8-545 857 29





From owner-idn@ops.ietf.org  Tue Jul 10 18:55:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA28527
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 18:55:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15K6Bl-000Del-00
	for idn-data@psg.com; Tue, 10 Jul 2001 15:41:05 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15K6Bj-000DeL-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 15:41:03 -0700
Message-ID: <00e101c10992$1cb3b8a0$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: <idn@ops.ietf.org>, "Adam M. Costello" <amc@cs.berkeley.edu>
References: <20010710220310.E943@arwen.cs.berkeley.edu>
Subject: Re: [idn] Reality Check
Date: Tue, 10 Jul 2001 18:46:05 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

From: "Adam M. Costello" <amc@cs.berkeley.edu>
> Edmon <edmon@neteka.com> wrote:
>
> > What I meant was the application using the DNS information then
> > communicating to a destination server such as an http server.  That
> > is, after they obtain an RR from the DNS, how they use the information
> > to then connect with the destination.  Should we not allow this to be
> > in UTF8 in the future?
>
> I don't follow.  The application gets the domain name from the user or
> an href attribute or wherever (not from DNS).  The application hands
> the domain name to the resolver, and gets back an IP address.  The
> application then opens a TCP connection to that IP address and sends the
> HTTP request, which includes the original domain name but not anything
> that came back from DNS.
>

Yes, I meant that when a dns application connects to the destination server,
it includes the "original domain name".  Do you at this point use ACE or
UTF8 or some other encoding?  IDNA mandates the use of ACE.  I think we
should have an "option" where if the destination HTTP server is IDN/UTF8
aware, then the UTF8 could be used.  This would give the incentive for
related servers and protocols such as HTTP servers to update to IDN/UTF8
extension.

Edmon




From owner-idn@ops.ietf.org  Tue Jul 10 19:56:25 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA00352
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 19:56:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15K77r-000FdJ-00
	for idn-data@psg.com; Tue, 10 Jul 2001 16:41:07 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15K77p-000Fd4-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 16:41:05 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15K77p-0000gr-00; Tue, 10 Jul 2001 16:41:05 -0700
Date: Tue, 10 Jul 2001 23:41:05 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Reality Check
Message-ID: <20010710234104.F943@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00e101c10992$1cb3b8a0$1001a8c0@neteka.com> <Pine.BSF.4.30.0107110005580.8353-100000@spider.nic-se.se>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

[A response to Mats Dufberg appears at the bottom.]

Edmon <edmon@neteka.com> wrote:

> Yes, I meant that when a dns application connects to the destination
> server, it includes the "original domain name".  Do you at this point
> use ACE or UTF8 or some other encoding?  IDNA mandates the use of
> ACE.  I think we should have an "option" where if the destination HTTP
> server is IDN/UTF8 aware, then the UTF8 could be used.

But "DNS applications" are the exception.  In the common case,
applications use the resolver, in which case the language spoken between
the resolver and DNS server is independent of the language spoken
between the application and the resolver.  (If a resolver provides a
UTF-8 interface but the DNS server does not support UTF-8, then the
resolver should ACE-encode the queries and ACE-decode the responses for
applications using the UTF-8 interface.)

Does IDNA really forbid DNS extensions for UTF-8?  Or does it merely
specify how IDNs can be used without extending DNS, while remaining
silent on the issue of DNS extensions?  I see no reason to forbid a DNS
extension for UTF-8, but nor do I see a pressing need for one.

> This would give the incentive for related servers and protocols such
> as HTTP servers to update to IDN/UTF8 extension.

I don't see how the incentive for other protocols to use UTF-8 is any
greater if DNS uses UTF-8.  DNS responses are seldom directly seen by
applications, and domain names obtained from DNS are seldom copied
into application messages.  The only time UTF-8 support in DNS would
encourage UTF-8 support in application protocols is when domain names
are copied directly from DNS responses into application messages, and
the frequency of that is seldom * seldom = approximately never.

A UTF-8 resolver interface, on the other hand, would indeed encourage
other protocols to support UTF-8, because then the applications could
copy domain names directly from application messages to the resolver and
vice-versa, without ever needing to do ACE encoding or decoding.

Mats Dufberg <dufberg@nic-se.se> wrote:

> The destinction between resolver and (authoritative) nameserver is not
> as sharp as might seems.

I wonder if you misunderstand what I mean by resolver.  The resolver is
a library on the client machine, linked into the application process.
It is not a DNS server of any kind--it is a DNS client.

AMC



From owner-idn@ops.ietf.org  Tue Jul 10 21:09:09 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA02229
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 21:09:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15K8IF-000I2o-00
	for idn-data@psg.com; Tue, 10 Jul 2001 17:55:55 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15K8IE-000I2i-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 17:55:54 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id UAA29310;
        Tue, 10 Jul 2001 20:55:47 -0400 (EDT)
Message-Id: <200107110055.UAA29310@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Edmon" <edmon@neteka.com>
cc: idn@ops.ietf.org, "Adam M. Costello" <amc@cs.berkeley.edu>
Subject: Re: [idn] Reality Check 
In-reply-to: Your message of "Tue, 10 Jul 2001 16:14:07 EDT."
             <009c01c1097c$e0a096e0$1001a8c0@neteka.com> 
Date: Tue, 10 Jul 2001 20:55:47 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Currently, IDNA does not provide the "option" for UTF-8 that you are
> suggesting.

sure it does.  the application can use whatever encoding it wants to.
the protocol used by DNS on-the-wire is irrelevant.



From owner-idn@ops.ietf.org  Tue Jul 10 23:21:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA06932
	for <idn-archive@lists.ietf.org>; Tue, 10 Jul 2001 23:21:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KAHp-000LoS-00
	for idn-data@psg.com; Tue, 10 Jul 2001 20:03:37 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KAHn-000LoG-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 20:03:35 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15KAHn-0000ya-00; Tue, 10 Jul 2001 20:03:35 -0700
Date: Wed, 11 Jul 2001 03:03:35 +0000
To: idn working group <idn@ops.ietf.org>
Subject: [idn] AMC-ACE-Z
Message-ID: <20010711030335.I943@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I have just submitted AMC-ACE-Z as draft-costello-idn-amc-ace-z-00.txt.
You can also find it at:

http://www.cs.berkeley.edu/~amc/charset/amc-ace-z.gz

Recently the ACE design team recommended DUDE, but AMC-ACE-Z did not
exist then.  At this time I personally recommend AMC-ACE-Z.  While it is
not as simple as DUDE, it is still fairly simple, and only a little bit
larger than DUDE when implemented in C.  But it is more efficient than
DUDE for all scripts: DUDE is typically about 30% longer than AMC-ACE-Z.
A comparative evaluation between these and several other ACEs can be
found at:

http://www.cs.berkeley.edu/~amc/charset/ace-eval.gz

(Would anyone like me to submit the evaluation as an internet draft?)

Some have argued that we should select the simplest ACE that is
"efficient enough".  But one could just as well argue that we should
select the most efficient ACE that is "simple enough".  In my opinion,
AMC-ACE-Z is more than simple enough.  And I think most of us here are
much better qualified to speculate on what constitutes "simple enough"
than on what constitutes "efficient enough".

But actually, I don't believe there is any such think as "simple enough"
or "efficient enough".  More efficient is always better, and simpler is
always better, and the two goals must be balanced.

Rather than presume to dictate what is a reasonable length for a name,
I think it would be more prudent to ask dozens of implementors to
spend a few extra hours coding and debugging in order to give millions
registrants more breathing room, in case they need it.

AMC

P.S.  I think Soobok Lee's reordering layer, which is known to improve
DUDE's efficiency, would similarly improve AMC-ACE-Z's efficiency,
but I don't know by how much.  I'm also curious how reordered-DUDE
would compare to non-reordered-AMC-ACE-Z.  (Note:  While DUDE wants
common code points to be in the same aligned block of 16, 256, or
4096, AMC-ACE-Z cares nothing about alignment, but simply wants common
code points to be as close together as possible, so sorting them in
decreasing order of frequency would probably be best.)

One concern I have regarding this reordering layer is who is going to
design the reordering tables for the 32 scripts that Soobok Lee has not
been working on?



From owner-idn@ops.ietf.org  Wed Jul 11 01:51:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA16770
	for <idn-archive@lists.ietf.org>; Wed, 11 Jul 2001 01:51:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KCYp-000Pwm-00
	for idn-data@psg.com; Tue, 10 Jul 2001 22:29:19 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KCYm-000Pwg-00
	for idn@ops.ietf.org; Tue, 10 Jul 2001 22:29:17 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6B5SsD14524;
	Wed, 11 Jul 2001 14:28:54 +0900 (KST)
Message-ID: <040c01c109ca$973289c0$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Adam M. Costello" <amc@cs.berkeley.edu>
Cc: <idn@ops.ietf.org>
Subject: [idn] (new) chinese/hangul ML.com statistics with AMCZ/LAMCZ
Date: Wed, 11 Jul 2001 14:30:16 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi, Adams and all

AMC-ACE-Z + REORDERING  is more efficient than DUDE + REORDERING
  at least for Chinese/Hangul. Testing other scripts, too.

For long chinese/hangul domains, the LAMCZ label length  approximates to
(1.95~2.15) * (number of code points).

As for label length efficiency,

LAMCZ is  11.30% efficient than LDUDE for chinese 285108 ML.com samples.
LAMCZ is  4.29% efficient than LDUDE for hangeul  207207 ML.com samples.

LAMCZ is the most efficient one that I have ever tested with.
(I have not tested with MACE,ACE37 yet. wait for a while, please.)
(I excluded Latin Ranges from REORDERING due to AMCZ's literal mode).

Cheers,

Soobok Lee
-------------------------------------------------------------------------


For Chinese ML.com samples.

N:            length of a domain label ( # of code points)
FREQ:         number domains of length N
N*FREQ:       sum of # of code points of domains of length N
SUM OF AMCZ:  sum of lengths of AMCZ labels
X:            SUM OF AMCZ / N * FREQ
SUM OF LAMCZ: sum of lengths of LAMCZ labels
Y:            SUM OF LAMCZ / N * FREQ
COMP:         (SUM OF LAMCZ - SUM OF AMCZ) / SUM OF AMCZ * 100

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|

|  1|    4642|      4642|     15804(3.40)|     14807(3.19)|6.31|
|  2|   59708|    119416|    401549(3.36)|    352022(2.95)|12.33|
|  3|   49471|    148413|    484456(3.26)|    415104(2.80)|14.32|
|  4|   99402|    397608|   1269398(3.19)|   1034646(2.60)|18.49|
|  5|   29974|    149870|    467070(3.12)|    381651(2.55)|18.29|
|  6|   20809|    124854|    384013(3.08)|    304635(2.44)|20.67|
|  7|    8860|     62020|    186347(3.00)|    147111(2.37)|21.06|
|  8|    5251|     42008|    124325(2.96)|     97303(2.32)|21.73|
|  9|    2666|     23994|     69234(2.89)|     54697(2.28)|21.00|
| 10|    2008|     20080|     57887(2.88)|     44270(2.20)|23.52|
| 11|     859|      9449|     26914(2.85)|     20836(2.21)|22.58|
| 12|     671|      8052|     22819(2.83)|     17294(2.15)|24.21|
| 13|     346|      4498|     12217(2.72)|      9581(2.13)|21.58|
| 14|     235|      3290|      9084(2.76)|      6933(2.11)|23.68|
| 15|     117|      1755|      4723(2.69)|      3721(2.12)|21.22|
| 16|      68|      1088|      2884(2.65)|      2258(2.08)|21.71|
| 17|      21|       357|       911(2.55)|       704(1.97)|22.72|

|   |  285108|   1121394|   3539635(3.16)|   2907573(2.59)|17.86|





For Korean ML.com samples.

N:            length of a domain label ( # of code points)
FREQ:         number domains of length N
N*FREQ:       sum of # of code points of domains of length N
SUM OF AMCZ:  sum of lengths of AMCZ labels
X:            SUM OF AMCZ / N * FREQ
SUM OF LAMCZ: sum of lengths of LAMCZ labels
Y:            SUM OF LAMCZ / N * FREQ
COMP:         (SUM OF LAMCZ - SUM OF AMCZ) / SUM OF AMCZ * 100

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|

|  1|    1941|      1941|      7764(4.00)|      7764(4.00)|0.00|
|  2|   16978|     33956|    123248(3.63)|    105628(3.11)|14.30|
|  3|   38852|    116556|    394410(3.38)|    322373(2.77)|18.26|
|  4|   61642|    246568|    803121(3.26)|    625970(2.54)|22.06|
|  5|   40375|    201875|    639079(3.17)|    483118(2.39)|24.40|
|  6|   24561|    147366|    458978(3.11)|    337398(2.29)|26.49|
|  7|   13034|     91238|    280346(3.07)|    203406(2.23)|27.44|
|  8|    5596|     44768|    136452(3.05)|     97248(2.17)|28.73|
|  9|    2421|     21789|     65504(3.01)|     46536(2.14)|28.96|
| 10|    1033|     10330|     29964(2.90)|     21330(2.06)|28.81|
| 11|     427|      4697|     13845(2.95)|      9739(2.07)|29.66|
| 12|     173|      2076|      5905(2.84)|      4261(2.05)|27.84|
| 13|      96|      1248|      3588(2.88)|      2539(2.03)|29.24|
| 14|      32|       448|      1331(2.97)|       921(2.06)|30.80|
| 15|      22|       330|       927(2.81)|       675(2.05)|27.18|
| 16|      15|       240|       606(2.52)|       471(1.96)|22.28|
| 17|       8|       136|       378(2.78)|       267(1.96)|29.37|
| 19|       1|        19|        26(1.37)|        26(1.37)|0.00|

|   |  207207|    925581|   2965472(3.20)|   2269670(2.45)|23.46|

----- Original Message ----- 
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Sent: Tuesday, July 10, 2001 10:37 PM
Subject: chinese/hangul ML.com statistics with DUDE/LDUDE


>   
> The next table is from
> 285108 chinese ML.com samples (old raw data from VGRS). 
>  
> "COMP" column includes improvement ratios of LDUDE over DUDE.
> "Y" column points that  for long chinese domains, LDUDE's label
> length is close to (2.0~2.5)*(input domain length).
> 
> 
> N:            length of a domain label ( # of code points)
> FREQ:         number domains of length N
> SUM OF DUDE:  sum of lengths of DUDE labels
> X:            SUM OF DUDE / N * FREQ
> SUM OF LDUDE: sum of lengths of LDUDE labels
> Y:            SUM OF LDUDE / N * FREQ
> COMP:         (SUM OF LDUDE - SUM OF DUDE) / SUM OF DUDE * 100
> 
> |  N|    FREQ|    N*FREQ|  SUM OF DUDE(X)| SUM OF LDUDE(Y)| COMP|
> 
> |  1|    4642|      4642|     18568(4.00)|     18568(4.00)| 0.00|
> |  2|   59708|    119416|    462031(3.87)|    415599(3.48)|10.05|
> |  3|   49471|    148413|    566440(3.82)|    477649(3.22)|15.68|
> |  4|   99402|    397608|   1509929(3.80)|   1168378(2.94)|22.62|
> |  5|   29974|    149870|    554237(3.70)|    426226(2.84)|23.10|
> |  6|   20809|    124854|    457412(3.66)|    333416(2.67)|27.11|
> |  7|    8860|     62020|    220880(3.56)|    160563(2.59)|27.31|
> |  8|    5251|     42008|    146822(3.50)|    103903(2.47)|29.23|
> |  9|    2666|     23994|     81433(3.39)|     58657(2.44)|27.97|
> | 10|    2008|     20080|     68385(3.41)|     46708(2.33)|31.70|
> | 11|     859|      9449|     31596(3.34)|     22111(2.34)|30.02|
> | 12|     671|      8052|     27039(3.36)|     18135(2.25)|32.93|
> | 13|     346|      4498|     14306(3.18)|     10088(2.24)|29.48|
> | 14|     235|      3290|     10676(3.24)|      7230(2.20)|32.28|
> | 15|     117|      1755|      5568(3.17)|      3854(2.20)|30.78|
> | 16|      68|      1088|      3383(3.11)|      2376(2.18)|29.77|
> | 17|      21|       357|      1075(3.01)|       750(2.10)|30.23|
> 
> |   |  285108|   1121394|   4179780(3.73)|   3274211(2.92)|21.67|
> 
> 
> 
> The next table is  
> From 207207 hangul ML.com samples (old raw data from VGRS). 
> 
> |  N|    FREQ|    N*FREQ|  SUM OF DUDE(X)| SUM OF LDUDE(Y)| COMP|
> 
> |  1|    1941|      1941|      7764(4.00)|      7764(4.00)|0.00|
> |  2|   16978|     33956|    129239(3.81)|    111308(3.28)|13.87|
> |  3|   38852|    116556|    436845(3.75)|    341333(2.93)|21.86|
> |  4|   61642|    246568|    915355(3.71)|    653736(2.65)|28.58|
> |  5|   40375|    201875|    743090(3.68)|    502097(2.49)|32.43|
> |  6|   24561|    147366|    540245(3.67)|    349710(2.37)|35.27|
> |  7|   13034|     91238|    332964(3.65)|    211206(2.31)|36.57|
> |  8|    5596|     44768|    162833(3.64)|    100618(2.25)|38.21|
> |  9|    2421|     21789|     78945(3.62)|     48633(2.23)|38.40|
> | 10|    1033|     10330|     36144(3.50)|     22323(2.16)|38.24|
> | 11|     427|      4697|     16744(3.56)|     10259(2.18)|38.73|
> | 12|     173|      2076|      7178(3.46)|      4578(2.21)|36.22|
> | 13|      96|      1248|      4386(3.51)|      2725(2.18)|37.87|
> | 14|      32|       448|      1656(3.70)|      1006(2.25)|39.25|
> | 15|      22|       330|      1168(3.54)|       750(2.27)|35.79|
> | 16|      15|       240|       757(3.15)|       529(2.20)|30.12|
> | 17|       8|       136|       470(3.46)|       299(2.20)|36.38|
> | 19|       1|        19|        30(1.58)|        30(1.58)|0.00|
> 
> |   |  207207|    925581|   3415813(3.69)|   2368904(2.56)|30.65|
> 
> 
> 
> 
> 
> 




From owner-idn@ops.ietf.org  Wed Jul 11 04:40:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA28340
	for <idn-archive@lists.ietf.org>; Wed, 11 Jul 2001 04:40:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KF8L-0003zQ-00
	for idn-data@psg.com; Wed, 11 Jul 2001 01:14:09 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KF8J-0003zH-00
	for idn@ops.ietf.org; Wed, 11 Jul 2001 01:14:07 -0700
Received: from enoshima (dhcp-100-137.mag.keio.ac.jp [133.27.195.137])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id RAA15638;
	Wed, 11 Jul 2001 17:13:24 +0900 (JST)
Message-Id: <4.2.0.58.J.20010711105253.033c16f0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 11 Jul 2001 17:12:54 +0900
To: Patrik Faltstrom <paf@cisco.com>, Paul Hoffman / IMC <phoffman@imc.org>,
        Keith Moore <moore@cs.utk.edu>, "Edmon" <edmon@neteka.com>
From: Martin Duerst <duerst@w3.org>
Subject: Comments on IDNA (was: Re: [idn] Reality Check)
Cc: idn@ops.ietf.org, "Adam M. Costello" <amc@cs.berkeley.edu>
In-Reply-To: <200107110055.UAA29310@astro.cs.utk.edu>
References: <Your message of "Tue, 10 Jul 2001 16:14:07 EDT." <009c01c1097c$e0a096e0$1001a8c0@neteka.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 20:55 01/07/10 -0400, Keith Moore wrote:
> > Currently, IDNA does not provide the "option" for UTF-8 that you are
> > suggesting.
>
>sure it does.  the application can use whatever encoding it wants to.
>the protocol used by DNS on-the-wire is irrelevant.

It would be extremely helpful if IDNA would make it clear that
applications can and should do something else than ACE.

The current IDNA draft (02), in the the unnumbered diagram,
says 'Application-specific protocol: predefined by the
protocol or defaults to nameprepped ACE'. This should be
changed.

Some other comments on the IDNA draft:

The abstract and intro give the impression that only updating
applications results in a significant advantage. Readers of
the doc may get the impression that servers/resolvers are
50% and applications 50%. As far as I know, it's more like
10%/90%. The draft should be changed to not give such wrong
impressions.

2.1.1: "Applications MAY allow ACE input and output, but are
not encouraged to do so except as an interface for advanced
users, possibly for debugging.": Please remove the 'advanced
user'. Giving people who want to look at the names the way they
are written the impression that they are retarded is not a
good idea.

2.1.1: "Since ACE can be rendered either as the encoded ASCII
glyphs or the proper decoded characters, the rendering engine
for an application SHOULD have an option for the user to select
the preferred display.

- The word 'ACE' is used here completely differently from above
   (including input, output, and process, rather than only one
    form).
- 'Rendering engine' is usually in the OS or window system/
   toolkit, not in the application. It would be strange to require
   such an engine to be able to decode ACE.
- The 'SHOULD' has to be conditioned on the MAY above.

My rewording would look like this:

In case Applications allow ACE input and output, they SHOULD
provide an option for the user to select ACE, which SHOULD
be off by default.


2.1.1:
In protocols and document formats that define how to handle
specification or negotiation of charsets, IDN host name parts can be
given in any charset allowed by the protocol or document format. If a
protocol or document format only allows one charset, IDN host name parts
must be given in that charset.

Preferably change 'charset' to 'character encoding' throughout
the draft. 'charset' is the name of a parameter, not a concept.
Also, in addition to character encodings, escapes are also possible
(I'm thinking of HTML &eacute;,...).

Also 'given in any' is much too general. And negotiation is irrelevant.
A single encoding is also just a special case, and so it should be
either left out, or called out ("In particular,..."). Also
On the other hand, protocols often use different character encodings
in different places. So I would write:

In any place where a protocol or document format allows to transmit
the characters in IDN host name parts, IDN host name parts MUST/SHOULD
be transmitted using whatever character encoding and escape mechanism
that the protocol or document format uses at that place.


2.1.2:
"that is resolving a non-internationalized host name parts MUST NOT do"
singular-plural mismatch.


2.1.4:
----
If an application decodes an ACE name but cannot show all of the
characters in the decoded name, such as if the name contains characters
that the output system cannot display, the application SHOULD show the
name in ACE format instead of displaying the name with the replacement
character (U+FFFD). This is to make it easier for the user to transfer
the name correctly to other programs using copy-and-paste techniques.
Programs that by default show the ACE form when they cannot show all the
characters in a name part SHOULD also have a mechanism to show the name
with as many characters as possible and replacement characters in the
positions where characters cannot be displayed.
----

Copy-and-paste often works even if display doesn't, and on the other
hand display may work but copy-and-paste may fail. So I would suggest
to just write:

This is to make it easier for the user to transfer
the name correctly to other programs.

Also, I would note that there are other ways to deal with this,
namely to show some hex code or use some popup tooltip,...
And also in many cases, the application doesn't know exactly what
the underlying rendering engine can display or not.


2.1.5

----
An application which receives a host name SHOULD verify whether or not
the host name is in ACE. This is possible by verifying the prefix in
each of the labels, and seeing whether or not the label is in ACE. This
MUST be done regardless of whether or not the communication channel used
(such as keyboard input, cut and paste, application protocol,
application payload, and so on) has negotiated ACE.
----

'negotiating ACE' sounds quite strange, in particular for keyboards.
It is not completely impossible to e.g. go to the X Consortium and
register something like "ACE_STRING" in addition to "COMPOUND_TEXT"
and "UTF8_STRING",... and then have application A fill in all of
these and application B pick ACE_STRING if it doesn't understand
the others,... It is also in theory concievable to create an input
method that directly produces ACE from some keyboard layout.
But there are considerable problems with this, I'm sure it's not
done for similar things such as Mail mime headers, and I think
it's a bad idea that the draft mention such things because it
may lead implementers into the woods.

Another problem is that the MUST seems to overrule the SHOULD.
Which one do we take?


----
The reason for this requirement is that many applications are not
ACE-aware. Applications that are not ACE-aware will send host names in
ACE but mark the charset as being US-ASCII or some other charset which
has the characters that are valid in [STD13] as a subset.
----

I thought that the general idea was to register a 'charset' parameter
value for the finally chosen ACE so that it could be used by transcoding
libraries, but to strongly discourage the use of this label in any
other context. Also, in a large number of cases, the 'charset' parameter
cannot be changed for every single bit of text (think email bodies).


2.1.6 Bidirectional text
----
In IDNA, bidirectional text is entered and displayed exactly as it is
specified in ISO/IEC 10646. Both ISO/IEC 10646 and the Unicode standard
have extensive discussion of how to deal with bidirectional text. Any
input mechanism and display mechanism that handles characters from
bidirectional scripts should already conform to those specifications.
Note that the formatting characters that manually change the direction
of display are prohibited by nameprep, thus making the task for input
and display mechanisms easier.
----

Sorry, but this is completely bogus. Some examples, even though
logically clear, would look totally mutilated.
Paul told me that there is an alternative proposal that requires
bidirectional text to be entered and stored in visual order.
This would have several very severe problems, namely:
- People would have to type things in backwards (i.e. typing
   FTEI to get IETF)
- Cut/paste from general text would not work at all.
- Sorting of domain names in Arabic or Hebrew would work the
   wrong way (first all words ending in 'a', then all ending in
   'b' and so,...)
- Text-to-speech applications will read the text the wrong way
   round (ftei for IETF again).

An alternate proposal has been around for a very long time, please
see http://www.ietf.org/internet-drafts/draft-masinter-url-i18n-07.txt
section 3.2. This proposal, originally by Francois Yergeau
(main contributor to RFC 2070 and to Tango, first web browser
that worked with Arabic as far as I know) works by taking advantage
of the Unicode bidirectional algorithm (thus not requiring special
code in particular for display) and can easily be integrated into
the nameprep algorithm (mainly removing specific bidi control
characters under specific conditions).

It may look more complicated than other (non-)proposals, but
bidirectionality IS a very thorny issue without easy ways out.


3. Name Server Considerations

----
The host name data in zone files (as specified by section 5 of RFC 1035)
MUST be both nameprepped and ACE encoded.
----

I thought that the zone files described here refer to some format
as exchanged over the network. But reading sec. 5 of 1035, it
speaks about 'loading a zone'. Obviously, there may be different
formats and ways to load a zone, so I have no idea why we would
have to require that ACE is used. I can very well imagine enhanced
dns software that is able to read in data in UTF-8 (or some local
encoding) and do nameprep and ACE internally. Actually, it would
seem that this would be a lot more convenient for a lot of users.

So either you have to explain the requirement, and restrict it
to the cases where it's really needed, or you remove it.
(or even better, say that dns software should provide facilities
for input from something readable).


Regards,    Martin.















From owner-idn@ops.ietf.org  Wed Jul 11 09:25:20 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA02692
	for <idn-archive@lists.ietf.org>; Wed, 11 Jul 2001 09:25:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KJeM-00079k-00
	for idn-data@psg.com; Wed, 11 Jul 2001 06:03:30 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KJeK-00079b-00
	for idn@ops.ietf.org; Wed, 11 Jul 2001 06:03:28 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA03454;
        Wed, 11 Jul 2001 09:03:14 -0400 (EDT)
Message-Id: <200107111303.JAA03454@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Martin Duerst <duerst@w3.org>
cc: Patrik Faltstrom <paf@cisco.com>, Paul Hoffman / IMC <phoffman@imc.org>,
        Keith Moore <moore@cs.utk.edu>, "Edmon" <edmon@neteka.com>,
        idn@ops.ietf.org, "Adam M. Costello" <amc@cs.berkeley.edu>
Subject: Re: Comments on IDNA (was: Re: [idn] Reality Check) 
In-reply-to: Your message of "Wed, 11 Jul 2001 17:12:54 +0900."
             <4.2.0.58.J.20010711105253.033c16f0@sh.w3.mag.keio.ac.jp> 
Date: Wed, 11 Jul 2001 09:03:14 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> It would be extremely helpful if IDNA would make it clear that
> applications can and should do something else than ACE.

Transition issues for existing applications are sufficiently
thorny, and differ enough from one application to another, that
it would be difficult to word an appropriate blanket 
recommendation to use "something else".  Even for new applications,
a blanket recommendation may not be appropriate.

The trend of using UTF-8 in new applications is already 
well-established even without encouragement from IDN; the
fact that IDN names are based on the 10646 character 
repertoire will only serve to further encourage the practice.
It will be natural for many of these applications 
to use the UTF-8 form of IDNs also.  Still, this choice needs
to be made on a per-application basis.  For example, should
IMAP server accept search queries for domains in UTF-8 even
though the stored messages that they're searching have those
domains expressed in DUDE (or whatever)?  We might have a guess
about the answer (and your guess might even agree with mine), 
but this is a question that should be answered by MTA and UA 
implementors (who have a better understanding of the issues,
and who will have to deal with their choices) rather than by 
the IDN WG.
 
Keith



From owner-idn@ops.ietf.org  Wed Jul 11 10:18:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA04294
	for <idn-archive@lists.ietf.org>; Wed, 11 Jul 2001 10:18:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KKd3-0007sh-00
	for idn-data@psg.com; Wed, 11 Jul 2001 07:06:13 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15KKd1-0007sS-00
	for idn@ops.ietf.org; Wed, 11 Jul 2001 07:06:11 -0700
Message-ID: <002501c10a13$59478400$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: <idn@ops.ietf.org>, "Adam M. Costello" <amc@cs.berkeley.edu>
References: <20010710234104.F943@arwen.cs.berkeley.edu>
Subject: Re: [idn] Reality Check
Date: Wed, 11 Jul 2001 10:11:12 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


From: "Adam M. Costello" <amc@cs.berkeley.edu>
> A UTF-8 resolver interface, on the other hand, would indeed encourage
> other protocols to support UTF-8, because then the applications could
> copy domain names directly from application messages to the resolver and
> vice-versa, without ever needing to do ACE encoding or decoding.
>

If you think that a UTF8 resolver interface is helpful, why then do we not
go one step further to layout a plan for UTF8 to be used on the dns as well?
How would the wait benefit us?  We are in a DNS WG, we are talking about IDN
and we are supposed to explore protocol extensions too.  I do not disagree
that IDNA is not a good start, but should we not go a few steps more to
layout a plan that would take us through IDNA(ACE) and into UTF8 eventually?

Edmon




From owner-idn@ops.ietf.org  Wed Jul 11 10:32:25 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA05360
	for <idn-archive@lists.ietf.org>; Wed, 11 Jul 2001 10:32:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KKj6-0007xK-00
	for idn-data@psg.com; Wed, 11 Jul 2001 07:12:28 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KKj4-0007xE-00
	for idn@ops.ietf.org; Wed, 11 Jul 2001 07:12:27 -0700
Received: from jamessonyvaio (ad202.166.28.121.magix.com.sg [202.166.28.121])
	by mail.i-dns.net (Postfix) with SMTP
	id 11E16FFC01; Wed, 11 Jul 2001 22:14:19 +0800 (SGT)
Message-ID: <000201c10a13$774d8530$4101a8c4@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: <idn@ops.ietf.org>, "Soobok Lee" <lsb@postel.co.kr>
References: <200107101324.JAA25949@astro.cs.utk.edu>
Subject: ave length, best compression etc - Was Re: [idn] THis WG derailed ? 
Date: Wed, 11 Jul 2001 14:16:33 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-Mimeole: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

As with all compression algorithm, there is an 'entropy' which is the
mininum length (or max compression) you can achieve by eliminating extra
information. Beyond that, you can achieve better compression for some
particular string by causing other strings to expand, ie, you have two
set: compressed strings and expanded strings. It is a give-and-take.

Thus, the idea is that if we do have a compression algorithm, then we
want to have the more oftenly occured string to be in the compressed
set. Thus, an rearrangment algorithm like LSB which basically rearrange
the certain characters so that it can be compressed better is generally
a good idea.

OTOH, we do not know whether this rearragement will produce better
compression in the long run. It may turn out that those strings which
falls in the expanded strings set is more oftenly used in future.

There is always a holy grail of compression. And we could spend donkey
years arguing over it and never get to our goal, ie, IDN. Lets not
forget that and hopefully we can get IDN in a timely fashion.

-James Seng




From owner-idn@ops.ietf.org  Wed Jul 11 15:22:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA16905
	for <idn-archive@lists.ietf.org>; Wed, 11 Jul 2001 15:22:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KPGQ-000D1a-00
	for idn-data@psg.com; Wed, 11 Jul 2001 12:03:10 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KPGP-000D1U-00
	for idn@ops.ietf.org; Wed, 11 Jul 2001 12:03:09 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA05382;
        Wed, 11 Jul 2001 15:02:56 -0400 (EDT)
Message-Id: <200107111902.PAA05382@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Edmon" <edmon@neteka.com>
cc: idn@ops.ietf.org, "Adam M. Costello" <amc@cs.berkeley.edu>
Subject: Re: [idn] Reality Check 
In-reply-to: Your message of "Wed, 11 Jul 2001 10:11:12 EDT."
             <002501c10a13$59478400$1001a8c0@neteka.com> 
Date: Wed, 11 Jul 2001 15:02:56 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> I do not disagree
> that IDNA is not a good start, but should we not go a few steps more to
> layout a plan that would take us through IDNA(ACE) and into UTF8 eventually?

first we need to get an ASCII-based solution out the door.

perhaps by then someone will have come up with a convincing argument as to
why having the ability to use UTF-8 on the wire in the DNS protocol 
(and producing consistent results with ASCII queries) actually produces 
a tangible benefit that is worth the incremental cost. 

so far, nobody has managed to do that.

Keith



From owner-idn@ops.ietf.org  Wed Jul 11 15:40:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17431
	for <idn-archive@lists.ietf.org>; Wed, 11 Jul 2001 15:40:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KPhh-000DRW-00
	for idn-data@psg.com; Wed, 11 Jul 2001 12:31:21 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KPhg-000DRP-00
	for idn@ops.ietf.org; Wed, 11 Jul 2001 12:31:20 -0700
Received: from [216.153.32.56] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 160640; Wed, 11 Jul 2001 12:30:45 -0700
Message-ID: <3B4CA96E.3D4F72CA@ehsco.com>
Date: Wed, 11 Jul 2001 14:30:54 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Edmon <edmon@neteka.com>, idn@ops.ietf.org,
        "Adam M. Costello" <amc@cs.berkeley.edu>
Subject: Re: [idn] Reality Check
References: <200107111902.PAA05382@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> first we need to get an ASCII-based solution out the door.

Not "out the door" so much, but one definitely needs to exists as a legacy
mode. IOW, ACE must exist in any event, but it does not need to exist as
"the solution to the problem".

> perhaps by then someone will have come up with a convincing argument
> as to why having the ability to use UTF-8 on the wire in the DNS
> protocol (and producing consistent results with ASCII queries)
> actually produces a tangible benefit that is worth the incremental
> cost.
> 
> so far, nobody has managed to do that.

Nobody has proposed a protocol for it. I will do this soon.

The costs for embedding and managing encrypted domain names in protocols
is obviously greater than the costs for embedding and managing UTF8 domain
names. This should be so obvious that no "arguments" are needed.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Wed Jul 11 15:52:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17745
	for <idn-archive@lists.ietf.org>; Wed, 11 Jul 2001 15:52:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KPm6-000DVp-00
	for idn-data@psg.com; Wed, 11 Jul 2001 12:35:54 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KPm6-000DVj-00
	for idn@ops.ietf.org; Wed, 11 Jul 2001 12:35:54 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA05827;
        Wed, 11 Jul 2001 15:35:44 -0400 (EDT)
Message-Id: <200107111935.PAA05827@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: Keith Moore <moore@cs.utk.edu>, Edmon <edmon@neteka.com>, idn@ops.ietf.org,
        "Adam M. Costello" <amc@cs.berkeley.edu>
Subject: Re: [idn] Reality Check 
In-reply-to: Your message of "Wed, 11 Jul 2001 14:30:54 CDT."
             <3B4CA96E.3D4F72CA@ehsco.com> 
Date: Wed, 11 Jul 2001 15:35:43 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > first we need to get an ASCII-based solution out the door.
> 
> Not "out the door" so much, but one definitely needs to exists as a legacy
> mode. IOW, ACE must exist in any event, but it does not need to exist as
> "the solution to the problem".
> 
> > perhaps by then someone will have come up with a convincing argument
> > as to why having the ability to use UTF-8 on the wire in the DNS
> > protocol (and producing consistent results with ASCII queries)
> > actually produces a tangible benefit that is worth the incremental
> > cost.
> > 
> > so far, nobody has managed to do that.
> 
> Nobody has proposed a protocol for it. I will do this soon.
> 
> The costs for embedding and managing encrypted domain names in protocols
> is obviously greater than the costs for embedding and managing UTF8 domain
> names. This should be so obvious that no "arguments" are needed.

if you think the cost savings are obvious, you haven't done the analysis.

hint: the cost of dealing with two different name representations is greater
than the cost of dealing with a single one.

Keith



From owner-idn@ops.ietf.org  Wed Jul 11 15:53:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17795
	for <idn-archive@lists.ietf.org>; Wed, 11 Jul 2001 15:53:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KPxZ-000Djz-00
	for idn-data@psg.com; Wed, 11 Jul 2001 12:47:45 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KPxY-000Djt-00
	for idn@ops.ietf.org; Wed, 11 Jul 2001 12:47:44 -0700
Received: from [216.153.32.56] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 160645; Wed, 11 Jul 2001 12:47:07 -0700
Message-ID: <3B4CAD45.DCDA35B5@ehsco.com>
Date: Wed, 11 Jul 2001 14:47:17 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Edmon <edmon@neteka.com>, idn@ops.ietf.org,
        "Adam M. Costello" <amc@cs.berkeley.edu>
Subject: Re: [idn] Reality Check
References: <200107111940.PAA05880@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> but due to backward compatibility and deployment issues, the ACE
> representation is the essential one.  The UTF8 one is not needed.

It is only essential to the past twenty years of activity, while UTF8 is
essential to the next twenty years.

Managing a single representation of data is going to be the most important
aspect going forward. You know this deep inside.

> as I've said before, the time to move to a UTF8 representation in the
> DNS protocol is when we upgrade to something better than DNS.

Not necessary.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Wed Jul 11 15:56:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17971
	for <idn-archive@lists.ietf.org>; Wed, 11 Jul 2001 15:56:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KPr6-000Dc3-00
	for idn-data@psg.com; Wed, 11 Jul 2001 12:41:04 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KPr5-000Dbo-00
	for idn@ops.ietf.org; Wed, 11 Jul 2001 12:41:03 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA05880;
        Wed, 11 Jul 2001 15:40:56 -0400 (EDT)
Message-Id: <200107111940.PAA05880@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: Keith Moore <moore@cs.utk.edu>, Edmon <edmon@neteka.com>, idn@ops.ietf.org,
        "Adam M. Costello" <amc@cs.berkeley.edu>
Subject: Re: [idn] Reality Check 
In-reply-to: Your message of "Wed, 11 Jul 2001 14:38:01 CDT."
             <3B4CAB19.BC9794C8@ehsco.com> 
Date: Wed, 11 Jul 2001 15:40:55 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > hint: the cost of dealing with two different name representations is
> > greater than the cost of dealing with a single one.
> 
> No kidding. With UTF8 they only do it once. With ACE they do it twice.

but due to backward compatibility and deployment issues, the ACE 
representation is the essential one.  The UTF8 one is not needed.

as I've said before, the time to move to a UTF8 representation in the
DNS protocol is when we upgrade to something better than DNS.



From owner-idn@ops.ietf.org  Wed Jul 11 15:58:02 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA18023
	for <idn-archive@lists.ietf.org>; Wed, 11 Jul 2001 15:58:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KPoa-000DZ7-00
	for idn-data@psg.com; Wed, 11 Jul 2001 12:38:28 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KPoZ-000DZ1-00
	for idn@ops.ietf.org; Wed, 11 Jul 2001 12:38:27 -0700
Received: from [216.153.32.56] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 160642; Wed, 11 Jul 2001 12:37:51 -0700
Message-ID: <3B4CAB19.BC9794C8@ehsco.com>
Date: Wed, 11 Jul 2001 14:38:01 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Edmon <edmon@neteka.com>, idn@ops.ietf.org,
        "Adam M. Costello" <amc@cs.berkeley.edu>
Subject: Re: [idn] Reality Check
References: <200107111935.PAA05827@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> hint: the cost of dealing with two different name representations is
> greater than the cost of dealing with a single one.

No kidding. With UTF8 they only do it once. With ACE they do it twice.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Wed Jul 11 16:20:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA18904
	for <idn-archive@lists.ietf.org>; Wed, 11 Jul 2001 16:20:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KQDV-000E4v-00
	for idn-data@psg.com; Wed, 11 Jul 2001 13:04:13 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KQDU-000E4h-00
	for idn@ops.ietf.org; Wed, 11 Jul 2001 13:04:12 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id QAA05958;
        Wed, 11 Jul 2001 16:04:08 -0400 (EDT)
Message-Id: <200107112004.QAA05958@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: Keith Moore <moore@cs.utk.edu>, Edmon <edmon@neteka.com>, idn@ops.ietf.org,
        "Adam M. Costello" <amc@cs.berkeley.edu>
Subject: Re: [idn] Reality Check 
In-reply-to: Your message of "Wed, 11 Jul 2001 14:47:17 CDT."
             <3B4CAD45.DCDA35B5@ehsco.com> 
Date: Wed, 11 Jul 2001 16:04:08 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > but due to backward compatibility and deployment issues, the ACE
> > representation is the essential one.  The UTF8 one is not needed.
> 
> It is only essential to the past twenty years of activity, while UTF8 is
> essential to the next twenty years.

for some applications, ACE will be needed for the next twenty years.
we can't expect people to upgrade their applications en masse.
nor would this make good operational sense.
 
> Managing a single representation of data is going to be the most important
> aspect going forward. You know this deep inside.

Gut feelings are often wrong, especially when they favor widespread and
disruptive change.  I place far more confidence in cost-vs-benefit analysis.

Keith



From owner-idn@ops.ietf.org  Wed Jul 11 16:28:17 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA19175
	for <idn-archive@lists.ietf.org>; Wed, 11 Jul 2001 16:28:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KQMz-000EBw-00
	for idn-data@psg.com; Wed, 11 Jul 2001 13:14:01 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KQMy-000EBq-00
	for idn@ops.ietf.org; Wed, 11 Jul 2001 13:14:00 -0700
Received: from [216.153.32.56] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 160656; Wed, 11 Jul 2001 13:13:24 -0700
Message-ID: <3B4CB36D.20E8775E@ehsco.com>
Date: Wed, 11 Jul 2001 15:13:33 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Edmon <edmon@neteka.com>, idn@ops.ietf.org,
        "Adam M. Costello" <amc@cs.berkeley.edu>
Subject: Re: [idn] Reality Check
References: <200107112004.QAA05958@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> for some applications, ACE will be needed for the next twenty years.

Yes, this is why it is necessary for legacy support. It is not necessary
for moving forward, and will actively interfere with progress.

> we can't expect people to upgrade their applications en masse.
> nor would this make good operational sense.

We are expecting them to do it for ACE (so that it is usable anyway). We
might as well let them move to recent state-of-the-art when they do it.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Wed Jul 11 17:32:54 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA21193
	for <idn-archive@lists.ietf.org>; Wed, 11 Jul 2001 17:32:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KRRW-000GkL-00
	for idn-data@psg.com; Wed, 11 Jul 2001 14:22:46 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KRRV-000GkF-00
	for idn@ops.ietf.org; Wed, 11 Jul 2001 14:22:45 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15KRRV-0001gY-00; Wed, 11 Jul 2001 14:22:45 -0700
Date: Wed, 11 Jul 2001 21:22:44 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Reality Check
Message-ID: <20010711212244.C5565@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B4CB36D.20E8775E@ehsco.com> <3B4CA96E.3D4F72CA@ehsco.com> <002501c10a13$59478400$1001a8c0@neteka.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Edmon <edmon@neteka.com> wrote:

> If you think that a UTF8 resolver interface is helpful, why then do we
> not go one step further to layout a plan for UTF8 to be used on the
> dns as well?  How would the wait benefit us?

We cannot develop standards at infinite speed.  If we worry about the
less urgent problems now, we distract ourselves away from the more
urgent problems, and thus delay the more urgent solutions.

The priorities are (in my estimation):

ACE & nameprep: essential
UTF-8 resolver: helpful
UTF-8 in DNS:   slightly helpful, maybe

Applications can start using IDNs as soon as ACE and nameprep are
finalized, and not a moment sooner.  A UTF-8 resolver interface might
encourage more applications to start supporting IDNs, because it will
make it easier.  A UTF-8 DNS extension will do very little, if anything,
for applications; it will make DNS servers and resolvers more complex
in the short term (when they support both UTF-8 and ACE) and simpler in
the long term (if ACE can someday be deprecated).  This is why I see no
urgency in developing a DNS extension.

"Eric A. Hall" <ehall@ehsco.com> wrote:

> The costs for embedding and managing encrypted domain names in
> protocols is obviously greater than the costs for embedding and
> managing UTF8 domain names.

If a protocol has the option of using only UTF-8 and not ACE (a new
application protocol would have this option, for example), then yes
that is obviously simpler.  But DNS does not have this option--it must
support ACE, at least in the short term.  It therefore has a choice
between ACE-only or ACE-plus-UTF-8.  Obviously, ACE-only is simpler
(but ACE-plus-UTF-8 is still an option that could be chosen for other
reasons).

> [ACE] is necessary for legacy support.  It is not necessary for moving
> forward, and will actively interfere with progress.

Huh?  Backward compatibility is most needed at the beginning, and the
need for it only decreases over time.  It is indeed necessary for moving
forward.  People are rarely willing to embrace a new thing if it causes
their existing stuff to stop working.

AMC



From owner-idn@ops.ietf.org  Thu Jul 12 09:21:31 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA18805
	for <idn-archive@lists.ietf.org>; Thu, 12 Jul 2001 09:21:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KfgA-0008bi-00
	for idn-data@psg.com; Thu, 12 Jul 2001 05:34:50 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Kfg9-0008bc-00
	for idn@ops.ietf.org; Thu, 12 Jul 2001 05:34:49 -0700
Received: from jamessonyvaio (tokyo-ppp-210-253-96-243.interq.or.jp [210.253.96.243])
	by mail.i-dns.net (Postfix) with SMTP
	id 1DA86FFC01; Thu, 12 Jul 2001 20:36:41 +0800 (SGT)
Message-ID: <02b001c10ace$ff5f4920$4101a8c4@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <200107101324.JAA25949@astro.cs.utk.edu> <000201c10a13$774d8530$4101a8c4@jamessonyvaio> <4.2.0.58.J.20010712190651.03462570@sh.w3.mag.keio.ac.jp>
Subject: Re: [idn] Re: ave length, best compression etc  
Date: Thu, 12 Jul 2001 20:34:28 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-Mimeole: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

There are approximately 2000 very commonly used chinese characters which
we will learn by primary school. a typical chinese can survive day to
day knowing about 4000 to 5000 han ideograph. I believe it is the
similar with Korean and Japanese. Not all ideograph are equal.

But my experience ends here. I am not sure if it is applicable to other
scripts or how it should be. OTOH, there aint many scripts which used
more than 255 block like CJK.

-James Seng

----- Original Message -----
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; "James Seng/Personal"
<James@seng.cc>; <idn@ops.ietf.org>
Sent: Thursday, July 12, 2001 6:07 PM
Subject: Re: [idn] Re: ave length, best compression etc


> At 10:31 01/07/12 +0900, Soobok Lee wrote:
>
> >The most frequent 256 Han letters has cumulative frequency sum
> >     of 58.2% and for the cases of top 512,1024,2048 and 4096 ones,
> >     it reaches 72.8,85.9,95.4 and 99.4%, respectively.
> >    4096 is roughly close to the size of Simplified Chinese Character
sets.
>
> By the way, how do you weight simplified, traditional, Japanese,
> and Korean when they use different codepoints?
>
> Regards,   Martin.
>




From owner-idn@ops.ietf.org  Thu Jul 12 09:22:32 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA18931
	for <idn-archive@lists.ietf.org>; Thu, 12 Jul 2001 09:22:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KdOR-0006Pz-00
	for idn-data@psg.com; Thu, 12 Jul 2001 03:08:23 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KdOQ-0006PS-00
	for idn@ops.ietf.org; Thu, 12 Jul 2001 03:08:22 -0700
Received: from enoshima (dhcp-100-137.mag.keio.ac.jp [133.27.195.137])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id TAA20644;
	Thu, 12 Jul 2001 19:08:18 +0900 (JST)
Message-Id: <4.2.0.58.J.20010712190651.03462570@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 12 Jul 2001 19:07:50 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, "James Seng/Personal" <James@Seng.cc>,
        <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Re: ave length, best compression etc  
In-Reply-To: <047101c10a72$619b4600$ed1bd9d2@postel.co.kr>
References: <200107101324.JAA25949@astro.cs.utk.edu>
 <000201c10a13$774d8530$4101a8c4@jamessonyvaio>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 10:31 01/07/12 +0900, Soobok Lee wrote:

>The most frequent 256 Han letters has cumulative frequency sum
>     of 58.2% and for the cases of top 512,1024,2048 and 4096 ones,
>     it reaches 72.8,85.9,95.4 and 99.4%, respectively.
>    4096 is roughly close to the size of Simplified Chinese Character sets.

By the way, how do you weight simplified, traditional, Japanese,
and Korean when they use different codepoints?

Regards,   Martin.



From owner-idn@ops.ietf.org  Thu Jul 12 09:22:38 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA18947
	for <idn-archive@lists.ietf.org>; Thu, 12 Jul 2001 09:22:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KfF9-00089x-00
	for idn-data@psg.com; Thu, 12 Jul 2001 05:06:55 -0700
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KfF7-00089q-00
	for idn@ops.ietf.org; Thu, 12 Jul 2001 05:06:54 -0700
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09225;
	Thu, 12 Jul 2001 08:05:58 -0400 (EDT)
Message-Id: <200107121205.IAA09225@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: idn@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [idn] I-D ACTION:draft-ietf-idn-lsb-ace-01.txt
Date: Thu, 12 Jul 2001 08:05:57 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internationalized Domain Name Working Group of the IETF.

	Title		: Improving ACE using code point reordering v1.0
	Author(s)	: S. Lee
	Filename	: draft-ietf-idn-lsb-ace-01.txt
	Pages		: 
	Date		: 12-Jul-01
	
This document describes code point reordering to improve ACE 
compression algorithms. Being based on character frequency and 
character adjacency statistics for major characater sets, this 
reordering can be easily implemented only with simple character 
mapping tables without adding complexity to existing ACE algorithms.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idn-lsb-ace-01.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-idn-lsb-ace-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-idn-lsb-ace-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010712080644.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idn-lsb-ace-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idn-lsb-ace-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010712080644.I-D@ietf.org>

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Thu Jul 12 09:46:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA21983
	for <idn-archive@lists.ietf.org>; Thu, 12 Jul 2001 09:46:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KgIM-0009FN-00
	for idn-data@psg.com; Thu, 12 Jul 2001 06:14:18 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KgIK-0009FH-00
	for idn@ops.ietf.org; Thu, 12 Jul 2001 06:14:17 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6CDDqD14569;
	Thu, 12 Jul 2001 22:13:53 +0900 (KST)
Message-ID: <005001c10ad5$505bf480$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <James@Seng.cc>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <200107101324.JAA25949@astro.cs.utk.edu> <000201c10a13$774d8530$4101a8c4@jamessonyvaio> <4.2.0.58.J.20010712190651.03462570@sh.w3.mag.keio.ac.jp>
Subject: Re: [idn] Re: ave length, best compression etc  
Date: Thu, 12 Jul 2001 22:19:41 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

First 512 (or more) letters in my reordering table were
manually chosen from frequent business category names
and region names in taiwan/china/japan.
They are placed to reflect word adjacencies.
SC/TC pairs are placed together in this 512 letters.

For ordering of other letters following the first 512 ones,
I merged two relative letter frequency distribution data sets with 
SC:TC=1:1 weight allocation ( excluding the first 512 letters).


a SC letter and its TC counterpart (and even Kanji counterpart)
should have been treated as one letter and placed together, 
but not in my current reordering table  which therefore
might favor the common letters of SC and TC character sets
over SC-only and TC-only letters. 
 
I am reading CNNIC-submitted draft on SC/TC
tranformation , which is a good source of  TC/SC pairs
for my next version of reordering tables.

Regards,

Soobok

----- Original Message -----
From: "Martin Duerst" <duerst@w3.org>
> >The most frequent 256 Han letters has cumulative frequency sum
> >     of 58.2% and for the cases of top 512,1024,2048 and 4096 ones,
> >     it reaches 72.8,85.9,95.4 and 99.4%, respectively.
> >    4096 is roughly close to the size of Simplified Chinese Character
sets.
>
> By the way, how do you weight simplified, traditional, Japanese,
> and Korean when they use different codepoints?
>
> Regards,   Martin.
>





From owner-idn@ops.ietf.org  Thu Jul 12 14:47:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA04218
	for <idn-archive@lists.ietf.org>; Thu, 12 Jul 2001 14:47:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KkXT-000CbT-00
	for idn-data@psg.com; Thu, 12 Jul 2001 10:46:11 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KkXT-000CbN-00
	for idn@ops.ietf.org; Thu, 12 Jul 2001 10:46:11 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15KkXS-0004ZJ-00; Thu, 12 Jul 2001 10:46:10 -0700
Date: Thu, 12 Jul 2001 17:46:10 +0000
To: idn working group <idn@ops.ietf.org>
Subject: [idn] pool deadline imminent, DUDE is only ACE in pool
Message-ID: <20010712174609.A17455@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I didn't really understand until this morning that any proposal that
doesn't have seven supporters by tomorrow will be out of the running.

Right now, DUDE is the only ACE in the pool.  If there is to be an
alternative to consider, at least seven people must coalesce around some
other proposal.  I suggest AMC-ACE-Z:

draft-costello-idn-amc-ace-z-00.txt  (submitted, should appear soon)
http://www.cs.berkeley.edu/~amc/charset/amc-ace-z.gz

Here is an analysis showing why AMC-ACE-Z is the best alternative to
DUDE, and is arguably preferable to DUDE:

http://www.cs.berkeley.edu/~amc/charset/ace-eval.gz

If you wish to express support for AMC-ACE-Z, please send mail (very
soon) to me <amc@cs.berkeley.edu>, not to the list.

Finally, please forgive me for soliciting support on the list.  It would
have been more proper for me to send mail privately to people I thought
might be interested, but I'm not sure who those people are, and time is
almost up.

AMC



From owner-idn@ops.ietf.org  Thu Jul 12 15:54:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA14786
	for <idn-archive@lists.ietf.org>; Thu, 12 Jul 2001 15:54:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KmC5-000EQx-00
	for idn-data@psg.com; Thu, 12 Jul 2001 12:32:13 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15KmC5-000EQr-00
	for idn@ops.ietf.org; Thu, 12 Jul 2001 12:32:13 -0700
Message-ID: <006401c10b0a$0d38f6a0$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: "idn working group" <idn@ops.ietf.org>,
        "Adam M. Costello" <amc@cs.berkeley.edu>
References: <20010712174609.A17455@arwen.cs.berkeley.edu>
Subject: Re: [idn] pool deadline imminent, DUDE is only ACE in pool
Date: Thu, 12 Jul 2001 15:37:12 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

From: "Adam M. Costello" <amc@cs.berkeley.edu>
> I didn't really understand until this morning that any proposal that
> doesn't have seven supporters by tomorrow will be out of the running.
>
I didn't either.
Forgive me also to advertise on this list for some support on my ACE37
proposal:
You can find it at
http://www.ietf.org/internet-drafts/draft-chung-idn-ace37-00.txt

here is a summary:

- ACE37 is a combination of DUDE, AMC-W/V & LACE (the three primary ACE
identified by the design team)
- ACE37 utilizes simple code block reordering (without requiring mapping) to
optimize diff so that there could be at least 21 Han ideographs within a 63
octet constraint (19 characters if 59 octets is used)
- ACE37 uses a single pass, single mode system that is almost as simple as
DUDE (a C implementation will be pubished soon to illustrate further that it
is as simple as DUDE)
- ACE37 uses all 37 characters allowed in the current DNS to optimize
compression

Edmon




From owner-idn@ops.ietf.org  Thu Jul 12 16:06:35 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA16478
	for <idn-archive@lists.ietf.org>; Thu, 12 Jul 2001 16:06:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KmH1-000EVy-00
	for idn-data@psg.com; Thu, 12 Jul 2001 12:37:19 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KmH0-000EVs-00
	for idn@ops.ietf.org; Thu, 12 Jul 2001 12:37:19 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH682MQ438w43ffWi4Y+kL6WpDt9kyg47Ew==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id F96Y5ZR8; Thu, 12 Jul 2001 15:36:29 EDT
To: moore@cs.utk.edu
Cc: ehall@ehsco.com, moore@cs.utk.edu, edmon@neteka.com, idn@ops.ietf.org,
        amc@cs.berkeley.edu
Date: Thu, 12 Jul 2001 12:12:48 -0700
Subject: Re: [idn] Reality Check
Message-ID: <20010712.125138.-803011.0.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.11
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,
 I am working on muenonic symbol mapping to ASCII [a-z0-9].
I have done French, English and Chinese.  I may summit it to
WG soon.  I am looking into Indian, Korean, Japanese, Hebrew 
 and other languages. If anyone would like to contribute to this 
effort, please respond to this message.

Liana

On Wed, 11 Jul 2001 15:40:55 -0400 Keith Moore <moore@cs.utk.edu> writes:
> > > hint: the cost of dealing with two different name representations 
> is
> > > greater than the cost of dealing with a single one.
> > 
> > No kidding. With UTF8 they only do it once. With ACE they do it 
> twice.
> 
> but due to backward compatibility and deployment issues, the ACE 
> representation is the essential one.  The UTF8 one is not needed.
> 
> as I've said before, the time to move to a UTF8 representation in 
> the
> DNS protocol is when we upgrade to something better than DNS.
> 



From owner-idn@ops.ietf.org  Thu Jul 12 16:07:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA16601
	for <idn-archive@lists.ietf.org>; Thu, 12 Jul 2001 16:07:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KmH8-000EWF-00
	for idn-data@psg.com; Thu, 12 Jul 2001 12:37:26 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KmH7-000EVs-00
	for idn@ops.ietf.org; Thu, 12 Jul 2001 12:37:25 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH682MQ438w43XpPZnYYM5ufT8ddgvRwSmQ==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id F96Y5ZU3; Thu, 12 Jul 2001 15:36:30 EDT
To: amc@cs.berkeley.edu
Cc: idn@ops.ietf.org
Date: Thu, 12 Jul 2001 12:51:03 -0700
Subject: Re: [idn] pool deadline imminent, DUDE is only ACE in pool
Message-ID: <20010712.125138.-803011.1.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.11
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-7,9-39
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I did not know this is procedure is either.  
I am working on resummiting StepCode proposal
and don't want to waste anyone's time when the 
proposal is not ready.

Liana


On Thu, 12 Jul 2001 17:46:10 +0000 "Adam M. Costello"
<amc@cs.berkeley.edu> writes:
> I didn't really understand until this morning that any proposal that
> doesn't have seven supporters by tomorrow will be out of the 
> running.
> 
> Right now, DUDE is the only ACE in the pool.  If there is to be an
> alternative to consider, at least seven people must coalesce around 
> some
> other proposal.  I suggest AMC-ACE-Z:
> 
> draft-costello-idn-amc-ace-z-00.txt  (submitted, should appear soon)
> http://www.cs.berkeley.edu/~amc/charset/amc-ace-z.gz
> 
> Here is an analysis showing why AMC-ACE-Z is the best alternative to
> DUDE, and is arguably preferable to DUDE:
> 
> http://www.cs.berkeley.edu/~amc/charset/ace-eval.gz
> 
> If you wish to express support for AMC-ACE-Z, please send mail (very
> soon) to me <amc@cs.berkeley.edu>, not to the list.
> 
> Finally, please forgive me for soliciting support on the list.  It 
> would
> have been more proper for me to send mail privately to people I 
> thought
> might be interested, but I'm not sure who those people are, and time 
> is
> almost up.
> 
> AMC
> 



From owner-idn@ops.ietf.org  Thu Jul 12 18:26:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA04806
	for <idn-archive@lists.ietf.org>; Thu, 12 Jul 2001 18:26:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KoYX-000Gj2-00
	for idn-data@psg.com; Thu, 12 Jul 2001 15:03:33 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KoYU-000GiW-00
	for idn@ops.ietf.org; Thu, 12 Jul 2001 15:03:31 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6CM3MD14583
	for <idn@ops.ietf.org>; Fri, 13 Jul 2001 07:03:22 +0900 (KST)
Message-ID: <00b701c10b1f$45b70ac0$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "idn working group" <idn@ops.ietf.org>
References: <20010712174609.A17455@arwen.cs.berkeley.edu>
Subject: [idn] call for support for REORDERING
Date: Fri, 13 Jul 2001 07:09:07 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


My I-D on "Improving ACE using code point reordering"
is looking forward to your supports. It has no contenders, 
only need your interests.

It  helps AMC-AMC-Z/DUDE's mean ACE label lengths 
to be close to that of UCS-2 ( 2*n) for 7 or more letters of 
typical han/hangul IDNs and does better compression for
other scripts, too.

To express your interests ( does not necessarily mean 
you support all the aspects of my I-D version1.0 )
in REORDERING, do not hesitate to send mail to me  
<lsb@postel.co.kr>. 

You can find my recent I-D (soon to be revised in IDN wg home).
http://www.postel.co.kr/lsb-ace-01.txt   (version 1.0)

Soobok Lee

=========================================================
The following attachment shows the amounts of
improvements achieved for big ML.com samples.


For Chinese ML.com samples.

N:            length of a domain label ( # of code points)
FREQ:         number domains of length N
N*FREQ:       sum of # of code points of domains of length N
SUM OF AMCZ:  sum of lengths of AMCZ labels
X:            SUM OF AMCZ / N * FREQ
SUM OF LAMCZ: sum of lengths of LAMCZ labels
Y:            SUM OF LAMCZ / N * FREQ
COMP:         (SUM OF LAMCZ - SUM OF AMCZ) / SUM OF AMCZ * 100

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|

|  1|    4642|      4642|     15804(3.40)|     14807(3.19)|6.31|
|  2|   59708|    119416|    401549(3.36)|    352022(2.95)|12.33|
|  3|   49471|    148413|    484456(3.26)|    415104(2.80)|14.32|
|  4|   99402|    397608|   1269398(3.19)|   1034646(2.60)|18.49|
|  5|   29974|    149870|    467070(3.12)|    381651(2.55)|18.29|
|  6|   20809|    124854|    384013(3.08)|    304635(2.44)|20.67|
|  7|    8860|     62020|    186347(3.00)|    147111(2.37)|21.06|
|  8|    5251|     42008|    124325(2.96)|     97303(2.32)|21.73|
|  9|    2666|     23994|     69234(2.89)|     54697(2.28)|21.00|
| 10|    2008|     20080|     57887(2.88)|     44270(2.20)|23.52|
| 11|     859|      9449|     26914(2.85)|     20836(2.21)|22.58|
| 12|     671|      8052|     22819(2.83)|     17294(2.15)|24.21|
| 13|     346|      4498|     12217(2.72)|      9581(2.13)|21.58|
| 14|     235|      3290|      9084(2.76)|      6933(2.11)|23.68|
| 15|     117|      1755|      4723(2.69)|      3721(2.12)|21.22|
| 16|      68|      1088|      2884(2.65)|      2258(2.08)|21.71|
| 17|      21|       357|       911(2.55)|       704(1.97)|22.72|

|   |  285108|   1121394|   3539635(3.16)|   2907573(2.59)|17.86|





For Korean ML.com samples.

N:            length of a domain label ( # of code points)
FREQ:         number domains of length N
N*FREQ:       sum of # of code points of domains of length N
SUM OF AMCZ:  sum of lengths of AMCZ labels
X:            SUM OF AMCZ / N * FREQ
SUM OF LAMCZ: sum of lengths of LAMCZ labels
Y:            SUM OF LAMCZ / N * FREQ
COMP:         (SUM OF LAMCZ - SUM OF AMCZ) / SUM OF AMCZ * 100

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|

|  1|    1941|      1941|      7764(4.00)|      7764(4.00)|0.00|
|  2|   16978|     33956|    123248(3.63)|    105628(3.11)|14.30|
|  3|   38852|    116556|    394410(3.38)|    322373(2.77)|18.26|
|  4|   61642|    246568|    803121(3.26)|    625970(2.54)|22.06|
|  5|   40375|    201875|    639079(3.17)|    483118(2.39)|24.40|
|  6|   24561|    147366|    458978(3.11)|    337398(2.29)|26.49|
|  7|   13034|     91238|    280346(3.07)|    203406(2.23)|27.44|
|  8|    5596|     44768|    136452(3.05)|     97248(2.17)|28.73|
|  9|    2421|     21789|     65504(3.01)|     46536(2.14)|28.96|
| 10|    1033|     10330|     29964(2.90)|     21330(2.06)|28.81|
| 11|     427|      4697|     13845(2.95)|      9739(2.07)|29.66|
| 12|     173|      2076|      5905(2.84)|      4261(2.05)|27.84|
| 13|      96|      1248|      3588(2.88)|      2539(2.03)|29.24|
| 14|      32|       448|      1331(2.97)|       921(2.06)|30.80|
| 15|      22|       330|       927(2.81)|       675(2.05)|27.18|
| 16|      15|       240|       606(2.52)|       471(1.96)|22.28|
| 17|       8|       136|       378(2.78)|       267(1.96)|29.37|
| 19|       1|        19|        26(1.37)|        26(1.37)|0.00|

|   |  207207|    925581|   2965472(3.20)|   2269670(2.45)|23.46|

----- Original Message ----- 
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Sent: Tuesday, July 10, 2001 10:37 PM
Subject: chinese/hangul ML.com statistics with DUDE/LDUDE


>   
> The next table is from
> 285108 chinese ML.com samples (old raw data from VGRS). 
>  
> "COMP" column includes improvement ratios of LDUDE over DUDE.
> "Y" column points that  for long chinese domains, LDUDE's label
> length is close to (2.0~2.5)*(input domain length).
> 
> 
> N:            length of a domain label ( # of code points)
> FREQ:         number domains of length N
> SUM OF DUDE:  sum of lengths of DUDE labels
> X:            SUM OF DUDE / N * FREQ
> SUM OF LDUDE: sum of lengths of LDUDE labels
> Y:            SUM OF LDUDE / N * FREQ
> COMP:         (SUM OF LDUDE - SUM OF DUDE) / SUM OF DUDE * 100
> 
> |  N|    FREQ|    N*FREQ|  SUM OF DUDE(X)| SUM OF LDUDE(Y)| COMP|
> 
> |  1|    4642|      4642|     18568(4.00)|     18568(4.00)| 0.00|
> |  2|   59708|    119416|    462031(3.87)|    415599(3.48)|10.05|
> |  3|   49471|    148413|    566440(3.82)|    477649(3.22)|15.68|
> |  4|   99402|    397608|   1509929(3.80)|   1168378(2.94)|22.62|
> |  5|   29974|    149870|    554237(3.70)|    426226(2.84)|23.10|
> |  6|   20809|    124854|    457412(3.66)|    333416(2.67)|27.11|
> |  7|    8860|     62020|    220880(3.56)|    160563(2.59)|27.31|
> |  8|    5251|     42008|    146822(3.50)|    103903(2.47)|29.23|
> |  9|    2666|     23994|     81433(3.39)|     58657(2.44)|27.97|
> | 10|    2008|     20080|     68385(3.41)|     46708(2.33)|31.70|
> | 11|     859|      9449|     31596(3.34)|     22111(2.34)|30.02|
> | 12|     671|      8052|     27039(3.36)|     18135(2.25)|32.93|
> | 13|     346|      4498|     14306(3.18)|     10088(2.24)|29.48|
> | 14|     235|      3290|     10676(3.24)|      7230(2.20)|32.28|
> | 15|     117|      1755|      5568(3.17)|      3854(2.20)|30.78|
> | 16|      68|      1088|      3383(3.11)|      2376(2.18)|29.77|
> | 17|      21|       357|      1075(3.01)|       750(2.10)|30.23|
> 
> |   |  285108|   1121394|   4179780(3.73)|   3274211(2.92)|21.67|
> 
> 
> 
> The next table is  
> From 207207 hangul ML.com samples (old raw data from VGRS). 
> 
> |  N|    FREQ|    N*FREQ|  SUM OF DUDE(X)| SUM OF LDUDE(Y)| COMP|
> 
> |  1|    1941|      1941|      7764(4.00)|      7764(4.00)|0.00|
> |  2|   16978|     33956|    129239(3.81)|    111308(3.28)|13.87|
> |  3|   38852|    116556|    436845(3.75)|    341333(2.93)|21.86|
> |  4|   61642|    246568|    915355(3.71)|    653736(2.65)|28.58|
> |  5|   40375|    201875|    743090(3.68)|    502097(2.49)|32.43|
> |  6|   24561|    147366|    540245(3.67)|    349710(2.37)|35.27|
> |  7|   13034|     91238|    332964(3.65)|    211206(2.31)|36.57|
> |  8|    5596|     44768|    162833(3.64)|    100618(2.25)|38.21|
> |  9|    2421|     21789|     78945(3.62)|     48633(2.23)|38.40|
> | 10|    1033|     10330|     36144(3.50)|     22323(2.16)|38.24|
> | 11|     427|      4697|     16744(3.56)|     10259(2.18)|38.73|
> | 12|     173|      2076|      7178(3.46)|      4578(2.21)|36.22|
> | 13|      96|      1248|      4386(3.51)|      2725(2.18)|37.87|
> | 14|      32|       448|      1656(3.70)|      1006(2.25)|39.25|
> | 15|      22|       330|      1168(3.54)|       750(2.27)|35.79|
> | 16|      15|       240|       757(3.15)|       529(2.20)|30.12|
> | 17|       8|       136|       470(3.46)|       299(2.20)|36.38|
> | 19|       1|        19|        30(1.58)|        30(1.58)|0.00|
> 
> |   |  207207|    925581|   3415813(3.69)|   2368904(2.56)|30.65|
> 
> 
> 
> 
> 
> 





From owner-idn@ops.ietf.org  Thu Jul 12 19:13:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA10371
	for <idn-archive@lists.ietf.org>; Thu, 12 Jul 2001 19:13:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15KpBm-000Hgz-00
	for idn-data@psg.com; Thu, 12 Jul 2001 15:44:06 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15KpBl-000Hgt-00
	for idn@ops.ietf.org; Thu, 12 Jul 2001 15:44:05 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6CMi1D00662
	for <idn@ops.ietf.org>; Fri, 13 Jul 2001 07:44:01 +0900 (KST)
Message-ID: <00d701c10b24$f480e260$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Subject: [idn] Hangeul NAMEPREP recommendation version 1.0
Date: Fri, 13 Jul 2001 07:49:48 +0900
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00D3_01C10B70.642566E0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_00D3_01C10B70.642566E0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit

Hi, nameprep team and all

This I-D  suggests Hangeul-specific NAMEPREP additions.
It prevents non-displayable and non-identifiable hangeul 
code sequences to appear in IDN, 
while current NAMEPREP 3.0 allows them that
may hurt IDN security.

You can read it:
http://www.ietf.org/internet-drafts/draft-ietf-idn-hangeulchar-00.txt

 
Abstract

    This document suggests Hangeul-specific NAMEPREP recommendations.
    It defines :
       - mapping tables for half-width jamo and enclosed jamo
       - excluding compatibility Hangeul jamo block 
         from compatibility decomposition in normalization step
       - criteria for determining invalid syl-ipf jamo sequence
       - prohibited hangul filler character  in KC norm output.

 

------=_NextPart_000_00D3_01C10B70.642566E0
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dks_c_5601-1987">
<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Hi, nameprep team and all</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>This I-D&nbsp; suggests Hangeul-specific NAMEPREP=20
additions.</FONT></DIV>
<DIV><FONT size=3D2>It prevents non-displayable and non-identifiable =
hangeul=20
</FONT></DIV>
<DIV><FONT size=3D2>code sequences to </FONT><FONT size=3D2>appear in =
IDN,=20
</FONT></DIV>
<DIV><FONT size=3D2>while current NAMEPREP 3.0 allows them =
that</FONT></DIV>
<DIV><FONT size=3D2>may hurt IDN security.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>You can read it:</FONT></DIV>
<DIV><FONT size=3D2><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-idn-hangeulchar-00=
.txt">http://www.ietf.org/internet-drafts/draft-ietf-idn-hangeulchar-00.t=
xt</A></FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;<BR>Abstract<BR><BR>&nbsp;&nbsp;&nbsp; This document suggests =

Hangeul-specific NAMEPREP recommendations.<BR>&nbsp;&nbsp;&nbsp; It =
defines=20
:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - mapping tables for =
half-width jamo=20
and enclosed jamo<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - excluding=20
compatibility Hangeul jamo block=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from compatibility=20
decomposition in normalization =
step<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -=20
criteria for determining invalid syl-ipf jamo=20
sequence<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - prohibited hangul =
filler=20
character&nbsp; in KC norm output.<BR><BR>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_00D3_01C10B70.642566E0--




From owner-idn@ops.ietf.org  Thu Jul 12 21:15:38 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA25171
	for <idn-archive@lists.ietf.org>; Thu, 12 Jul 2001 21:15:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Kqzv-000KYh-00
	for idn-data@psg.com; Thu, 12 Jul 2001 17:39:59 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Kqzt-000KYa-00
	for idn@ops.ietf.org; Thu, 12 Jul 2001 17:39:57 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6D0dmD12313;
	Fri, 13 Jul 2001 09:39:53 +0900 (KST)
Message-ID: <00fe01c10b35$2400f7e0$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Cc: "Adam M. Costello" <amc@cs.berkeley.edu>
Subject: [idn] (new)  experiments with  *PURE* UniHan/Hangul ML.com with LAMCZ/LDUDE
Date: Fri, 13 Jul 2001 09:45:35 +0900
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00FA_01C10B80.90D54560"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_00FA_01C10B80.90D54560
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit

I  have taken another experiments with *PURE* Unihan/Hangeul ML.com 
domains without any scripts from Digits,Hiragana,Katakana and etc.
 
-------------------------------------------------------------------
LAMCZ with pure UniHan ML.com


N:            length of a domain label ( # of code points)
FREQ:         number domains of length N
N*FREQ:       sum of # of code points of domains of length N
SUM OF AMCZ:  sum of lengths of AMCZ labels
X:            SUM OF AMCZ / N * FREQ
SUM OF LAMCZ: sum of lengths of LAMCZ labels
Y:            SUM OF LAMCZ / N * FREQ
COMP:         (SUM OF LAMCZ - SUM OF AMCZ) / SUM OF AMCZ * 100

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|

|  1|    3735|      3735|     12177(3.26)|     11589(3.10)|4.83|
|  2|   42793|     85586|    281303(3.29)|    249930(2.92)|11.15|
|  3|   28033|     84099|    267446(3.18)|    230951(2.75)|13.65|
|  4|   54607|    218428|    685584(3.14)|    562349(2.57)|17.98|
|  5|   12591|     62955|    195596(3.11)|    157259(2.50)|19.60|
|  6|    7680|     46080|    141927(3.08)|    110465(2.40)|22.17|
|  7|    2761|     19327|     59231(3.06)|     44754(2.32)|24.44|
|  8|    1336|     10688|     32554(3.05)|     24120(2.26)|25.91|
|  9|     641|      5769|     17490(3.03)|     12833(2.22)|26.63|
| 10|     298|      2980|      8962(3.01)|      6570(2.20)|26.69|
| 11|     137|      1507|      4575(3.04)|      3226(2.14)|29.49|
| 12|      57|       684|      2057(3.01)|      1529(2.24)|25.67|
| 13|      25|       325|       983(3.02)|       727(2.24)|26.04|
| 14|       6|        84|       253(3.01)|       181(2.15)|28.46|
| 15|       6|        90|       266(2.96)|       195(2.17)|26.69|
| 17|       1|        17|        48(2.82)|        32(1.88)|33.33|

|   |  154707|    542354|   1710452(3.15)|   1416710(2.61)|17.17|



-------------------------------------------------------------------
LAMCZ with pure Hangul ML.com

N:            length of a domain label ( # of code points)
FREQ:         number domains of length N
N*FREQ:       sum of # of code points of domains of length N
SUM OF AMCZ:  sum of lengths of AMCZ labels
X:            SUM OF AMCZ / N * FREQ
SUM OF LAMCZ: sum of lengths of LAMCZ labels
Y:            SUM OF LAMCZ / N * FREQ
COMP:         (SUM OF LAMCZ - SUM OF AMCZ) / SUM OF AMCZ * 100

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|

|  1|    1940|      1940|      7760(4.00)|      7760(4.00)|0.00|
|  2|   16492|     32984|    119927(3.64)|    102659(3.11)|14.40|
|  3|   37406|    112218|    380305(3.39)|    310666(2.77)|18.31|
|  4|   57732|    230928|    756089(3.27)|    587684(2.54)|22.27|
|  5|   36661|    183305|    587547(3.21)|    440929(2.41)|24.95|
|  6|   22090|    132540|    418286(3.16)|    304984(2.30)|27.09|
|  7|   11503|     80521|    251226(3.12)|    180533(2.24)|28.14|
|  8|    4963|     39704|    122742(3.09)|     86642(2.18)|29.41|
|  9|    2104|     18936|     57964(3.06)|     40725(2.15)|29.74|
| 10|     833|      8330|     25332(3.04)|     17599(2.11)|30.53|
| 11|     358|      3938|     11919(3.03)|      8225(2.09)|30.99|
| 12|     123|      1476|      4422(3.00)|      3092(2.09)|30.08|
| 13|      71|       923|      2752(2.98)|      1901(2.06)|30.92|
| 14|      28|       392|      1160(2.96)|       805(2.05)|30.60|
| 15|      18|       270|       798(2.96)|       565(2.09)|29.20|
| 16|      10|       160|       460(2.88)|       342(2.14)|25.65|
| 17|       7|       119|       354(2.97)|       243(2.04)|31.36|

|   |  192339|    848684|   2749043(3.24)|   2095354(2.47)|23.78|


-------------------------------------------------------------------
LDUDE  with pure UniHan ML.com


N:            length of a domain label ( # of code points)
FREQ:         number domains of length N
N*FREQ:       sum of # of code points of domains of length N
SUM OF DUDE:  sum of lengths of DUDE labels
X:            SUM OF DUDE / N * FREQ
SUM OF LDUDE: sum of lengths of LDUDE labels
Y:            SUM OF LDUDE / N * FREQ
COMP:         (SUM OF LDUDE - SUM OF DUDE) / SUM OF DUDE * 100

|  N|    FREQ|    N*FREQ|  SUM OF DUDE(X)| SUM OF LDUDE(Y)| COMP|

|  1|    3735|      3735|     14940(4.00)|     14940(4.00)|0.00|
|  2|   42793|     85586|    328641(3.84)|    296679(3.47)|9.73|
|  3|   28033|     84099|    318916(3.79)|    268987(3.20)|15.66|
|  4|   54607|    218428|    826020(3.78)|    639417(2.93)|22.59|
|  5|   12591|     62955|    237862(3.78)|    178866(2.84)|24.80|
|  6|    7680|     46080|    173063(3.76)|    122010(2.65)|29.50|
|  7|    2761|     19327|     72750(3.76)|     49710(2.57)|31.67|
|  8|    1336|     10688|     40078(3.75)|     26187(2.45)|34.66|
|  9|     641|      5769|     21554(3.74)|     14009(2.43)|35.01|
| 10|     298|      2980|     11164(3.75)|      7095(2.38)|36.45|
| 11|     137|      1507|      5671(3.76)|      3482(2.31)|38.60|
| 12|      57|       684|      2528(3.70)|      1678(2.45)|33.62|
| 13|      25|       325|      1188(3.66)|       807(2.48)|32.07|
| 14|       6|        84|       309(3.68)|       202(2.40)|34.63|
| 15|       6|        90|       323(3.59)|       204(2.27)|36.84|
| 17|       1|        17|        55(3.24)|        39(2.29)|29.09|

|   |  154707|    542354|   2055062(3.79)|   1624312(2.99)|20.96|


-------------------------------------------------------------------
LDUDE  with pure Hangul ML.com
 
N:            length of a domain label ( # of code points)
FREQ:         number domains of length N
N*FREQ:       sum of # of code points of domains of length N
SUM OF DUDE:  sum of lengths of DUDE labels
X:            SUM OF DUDE / N * FREQ
SUM OF LDUDE: sum of lengths of LDUDE labels
Y:            SUM OF LDUDE / N * FREQ
COMP:         (SUM OF LDUDE - SUM OF DUDE) / SUM OF DUDE * 100

|  N|    FREQ|    N*FREQ|  SUM OF DUDE(X)| SUM OF LDUDE(Y)| COMP|

|  1|    1940|      1940|      7760(4.00)|      7760(4.00)|0.00|
|  2|   16492|     32984|    125398(3.80)|    107795(3.27)|14.04|
|  3|   37406|    112218|    420812(3.75)|    328202(2.92)|22.01|
|  4|   57732|    230928|    860712(3.73)|    610053(2.64)|29.12|
|  5|   36661|    183305|    682356(3.72)|    454656(2.48)|33.37|
|  6|   22090|    132540|    492239(3.71)|    313997(2.37)|36.21|
|  7|   11503|     80521|    298365(3.71)|    186251(2.31)|37.58|
|  8|    4963|     39704|    146595(3.69)|     89221(2.25)|39.14|
|  9|    2104|     18936|     69955(3.69)|     42413(2.24)|39.37|
| 10|     833|      8330|     30705(3.69)|     18333(2.20)|40.29|
| 11|     358|      3938|     14452(3.67)|      8628(2.19)|40.30|
| 12|     123|      1476|      5397(3.66)|      3314(2.25)|38.60|
| 13|      71|       923|      3387(3.67)|      2055(2.23)|39.33|
| 14|      28|       392|      1452(3.70)|       893(2.28)|38.50|
| 15|      18|       270|       998(3.70)|       632(2.34)|36.67|
| 16|      10|       160|       582(3.64)|       386(2.41)|33.68|
| 17|       7|       119|       438(3.68)|       272(2.29)|37.90|

|   |  192339|    848684|   3161603(3.73)|   2174861(2.56)|31.21|





------=_NextPart_000_00FA_01C10B80.90D54560
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dks_c_5601-1987">
<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>I&nbsp; have taken another experiments with *PURE*=20
Unihan/Hangeul ML.com </FONT></DIV>
<DIV><FONT size=3D2>domains without any scripts from =
Digits,Hiragana,Katakana and=20
etc.</FONT></DIV>
<DIV><FONT size=3D2>&nbsp;</FONT></DIV>
<DIV><FONT size=3D2>
<DIV><FONT=20
size=3D2>----------------------------------------------------------------=
---</FONT></DIV>
<DIV><FONT size=3D2>LAMCZ with pure UniHan =
ML.com</FONT></DIV></FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV><FONT size=3D2>
<DIV><BR>N:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
length of a domain label ( # of code=20
points)<BR>FREQ:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; number =
domains=20
of length N<BR>N*FREQ:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sum of # of =
code=20
points of domains of length N<BR>SUM OF AMCZ:&nbsp; sum of lengths of =
AMCZ=20
labels<BR>X:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
SUM OF AMCZ / N * FREQ<BR>SUM OF LAMCZ: sum of lengths of LAMCZ=20
labels<BR>Y:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
SUM OF LAMCZ / N * =
FREQ<BR>COMP:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
(SUM OF LAMCZ - SUM OF AMCZ) / SUM OF AMCZ * 100</DIV>
<DIV>&nbsp;</DIV>
<DIV>|&nbsp; N|&nbsp;&nbsp;&nbsp; FREQ|&nbsp;&nbsp;&nbsp; N*FREQ|&nbsp; =
SUM OF=20
AMCZ(X)| SUM OF LAMCZ(Y)| COMP|</DIV>
<DIV>&nbsp;</DIV>
<DIV>|&nbsp; 1|&nbsp;&nbsp;&nbsp; 3735|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
3735|&nbsp;&nbsp;&nbsp;&nbsp; 12177(3.26)|&nbsp;&nbsp;&nbsp;&nbsp;=20
11589(3.10)|4.83|<BR>|&nbsp; 2|&nbsp;&nbsp; =
42793|&nbsp;&nbsp;&nbsp;&nbsp;=20
85586|&nbsp;&nbsp;&nbsp; 281303(3.29)|&nbsp;&nbsp;&nbsp;=20
249930(2.92)|11.15|<BR>|&nbsp; 3|&nbsp;&nbsp; =
28033|&nbsp;&nbsp;&nbsp;&nbsp;=20
84099|&nbsp;&nbsp;&nbsp; 267446(3.18)|&nbsp;&nbsp;&nbsp;=20
230951(2.75)|13.65|<BR>|&nbsp; 4|&nbsp;&nbsp; 54607|&nbsp;&nbsp;&nbsp;=20
218428|&nbsp;&nbsp;&nbsp; 685584(3.14)|&nbsp;&nbsp;&nbsp;=20
562349(2.57)|17.98|<BR>|&nbsp; 5|&nbsp;&nbsp; =
12591|&nbsp;&nbsp;&nbsp;&nbsp;=20
62955|&nbsp;&nbsp;&nbsp; 195596(3.11)|&nbsp;&nbsp;&nbsp;=20
157259(2.50)|19.60|<BR>|&nbsp; 6|&nbsp;&nbsp;&nbsp;=20
7680|&nbsp;&nbsp;&nbsp;&nbsp; 46080|&nbsp;&nbsp;&nbsp;=20
141927(3.08)|&nbsp;&nbsp;&nbsp; 110465(2.40)|22.17|<BR>|&nbsp;=20
7|&nbsp;&nbsp;&nbsp; 2761|&nbsp;&nbsp;&nbsp;&nbsp;=20
19327|&nbsp;&nbsp;&nbsp;&nbsp; 59231(3.06)|&nbsp;&nbsp;&nbsp;&nbsp;=20
44754(2.32)|24.44|<BR>|&nbsp; 8|&nbsp;&nbsp;&nbsp; =
1336|&nbsp;&nbsp;&nbsp;&nbsp;=20
10688|&nbsp;&nbsp;&nbsp;&nbsp; 32554(3.05)|&nbsp;&nbsp;&nbsp;&nbsp;=20
24120(2.26)|25.91|<BR>|&nbsp; 9|&nbsp;&nbsp;&nbsp;&nbsp;=20
641|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5769|&nbsp;&nbsp;&nbsp;&nbsp;=20
17490(3.03)|&nbsp;&nbsp;&nbsp;&nbsp; 12833(2.22)|26.63|<BR>|=20
10|&nbsp;&nbsp;&nbsp;&nbsp; 298|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
2980|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
8962(3.01)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
6570(2.20)|26.69|<BR>| 11|&nbsp;&nbsp;&nbsp;&nbsp;=20
137|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1507|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
4575(3.04)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3226(2.14)|29.49|<BR>|=20
12|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
57|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
684|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2057(3.01)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
1529(2.24)|25.67|<BR>| 13|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
25|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
325|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
983(3.02)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 727(2.24)|26.04|<BR>|=20
14|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
6|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
84|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
253(3.01)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 181(2.15)|28.46|<BR>|=20
15|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
6|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
90|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
266(2.96)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 195(2.17)|26.69|<BR>|=20
17|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
1|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
17|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
48(2.82)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
32(1.88)|33.33|</DIV>
<DIV>&nbsp;</DIV>
<DIV>|&nbsp;&nbsp; |&nbsp; 154707|&nbsp;&nbsp;&nbsp; 542354|&nbsp;&nbsp; =

1710452(3.15)|&nbsp;&nbsp; 1416710(2.61)|17.17|<BR></FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT=20
size=3D2>----------------------------------------------------------------=
---</FONT></DIV>
<DIV><FONT size=3D2>LAMCZ with pure Hangul ML.com</FONT></DIV>
<DIV><BR><FONT=20
size=3D2>N:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
length of a domain label ( # of code=20
points)<BR>FREQ:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; number =
domains=20
of length N<BR>N*FREQ:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sum of # of =
code=20
points of domains of length N<BR>SUM OF AMCZ:&nbsp; sum of lengths of =
AMCZ=20
labels<BR>X:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
SUM OF AMCZ / N * FREQ<BR>SUM OF LAMCZ: sum of lengths of LAMCZ=20
labels<BR>Y:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
SUM OF LAMCZ / N * =
FREQ<BR>COMP:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
(SUM OF LAMCZ - SUM OF AMCZ) / SUM OF AMCZ * 100</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>|&nbsp; N|&nbsp;&nbsp;&nbsp; FREQ|&nbsp;&nbsp;&nbsp; =

N*FREQ|&nbsp; SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>|&nbsp; 1|&nbsp;&nbsp;&nbsp;=20
1940|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1940|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
7760(4.00)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7760(4.00)|0.00|<BR>|&nbsp;=20
2|&nbsp;&nbsp; 16492|&nbsp;&nbsp;&nbsp;&nbsp; 32984|&nbsp;&nbsp;&nbsp;=20
119927(3.64)|&nbsp;&nbsp;&nbsp; 102659(3.11)|14.40|<BR>|&nbsp; =
3|&nbsp;&nbsp;=20
37406|&nbsp;&nbsp;&nbsp; 112218|&nbsp;&nbsp;&nbsp;=20
380305(3.39)|&nbsp;&nbsp;&nbsp; 310666(2.77)|18.31|<BR>|&nbsp; =
4|&nbsp;&nbsp;=20
57732|&nbsp;&nbsp;&nbsp; 230928|&nbsp;&nbsp;&nbsp;=20
756089(3.27)|&nbsp;&nbsp;&nbsp; 587684(2.54)|22.27|<BR>|&nbsp; =
5|&nbsp;&nbsp;=20
36661|&nbsp;&nbsp;&nbsp; 183305|&nbsp;&nbsp;&nbsp;=20
587547(3.21)|&nbsp;&nbsp;&nbsp; 440929(2.41)|24.95|<BR>|&nbsp; =
6|&nbsp;&nbsp;=20
22090|&nbsp;&nbsp;&nbsp; 132540|&nbsp;&nbsp;&nbsp;=20
418286(3.16)|&nbsp;&nbsp;&nbsp; 304984(2.30)|27.09|<BR>|&nbsp; =
7|&nbsp;&nbsp;=20
11503|&nbsp;&nbsp;&nbsp;&nbsp; 80521|&nbsp;&nbsp;&nbsp;=20
251226(3.12)|&nbsp;&nbsp;&nbsp; 180533(2.24)|28.14|<BR>|&nbsp;=20
8|&nbsp;&nbsp;&nbsp; 4963|&nbsp;&nbsp;&nbsp;&nbsp; =
39704|&nbsp;&nbsp;&nbsp;=20
122742(3.09)|&nbsp;&nbsp;&nbsp;&nbsp; 86642(2.18)|29.41|<BR>|&nbsp;=20
9|&nbsp;&nbsp;&nbsp; 2104|&nbsp;&nbsp;&nbsp;&nbsp;=20
18936|&nbsp;&nbsp;&nbsp;&nbsp; 57964(3.06)|&nbsp;&nbsp;&nbsp;&nbsp;=20
40725(2.15)|29.74|<BR>| 10|&nbsp;&nbsp;&nbsp;&nbsp;=20
833|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8330|&nbsp;&nbsp;&nbsp;&nbsp;=20
25332(3.04)|&nbsp;&nbsp;&nbsp;&nbsp; 17599(2.11)|30.53|<BR>|=20
11|&nbsp;&nbsp;&nbsp;&nbsp; 358|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
3938|&nbsp;&nbsp;&nbsp;&nbsp; 11919(3.03)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

8225(2.09)|30.99|<BR>| 12|&nbsp;&nbsp;&nbsp;&nbsp;=20
123|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1476|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
4422(3.00)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3092(2.09)|30.08|<BR>|=20
13|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
71|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
923|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2752(2.98)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
1901(2.06)|30.92|<BR>| 14|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
28|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
392|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
1160(2.96)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 805(2.05)|30.60|<BR>|=20
15|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
18|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
270|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
798(2.96)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 565(2.09)|29.20|<BR>|=20
16|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
10|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
160|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
460(2.88)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 342(2.14)|25.65|<BR>|=20
17|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
7|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
119|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
354(2.97)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
243(2.04)|31.36|</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>|&nbsp;&nbsp; |&nbsp; 192339|&nbsp;&nbsp;&nbsp;=20
848684|&nbsp;&nbsp; 2749043(3.24)|&nbsp;&nbsp;=20
2095354(2.47)|23.78|<BR></FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV>
<DIV><FONT=20
size=3D2>----------------------------------------------------------------=
---</FONT></DIV>
<DIV><FONT size=3D2>LDUDE&nbsp; with pure UniHan ML.com</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV><FONT size=3D2>
<DIV><BR>N:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
length of a domain label ( # of code=20
points)<BR>FREQ:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; number =
domains=20
of length N<BR>N*FREQ:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sum of # of =
code=20
points of domains of length N<BR>SUM OF DUDE:&nbsp; sum of lengths of =
DUDE=20
labels<BR>X:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
SUM OF DUDE / N * FREQ<BR>SUM OF LDUDE: sum of lengths of LDUDE=20
labels<BR>Y:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
SUM OF LDUDE / N * =
FREQ<BR>COMP:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
(SUM OF LDUDE - SUM OF DUDE) / SUM OF DUDE * 100</DIV>
<DIV>&nbsp;</DIV>
<DIV>|&nbsp; N|&nbsp;&nbsp;&nbsp; FREQ|&nbsp;&nbsp;&nbsp; N*FREQ|&nbsp; =
SUM OF=20
DUDE(X)| SUM OF LDUDE(Y)| COMP|</DIV>
<DIV>&nbsp;</DIV>
<DIV>|&nbsp; 1|&nbsp;&nbsp;&nbsp; 3735|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
3735|&nbsp;&nbsp;&nbsp;&nbsp; 14940(4.00)|&nbsp;&nbsp;&nbsp;&nbsp;=20
14940(4.00)|0.00|<BR>|&nbsp; 2|&nbsp;&nbsp; =
42793|&nbsp;&nbsp;&nbsp;&nbsp;=20
85586|&nbsp;&nbsp;&nbsp; 328641(3.84)|&nbsp;&nbsp;&nbsp;=20
296679(3.47)|9.73|<BR>|&nbsp; 3|&nbsp;&nbsp; =
28033|&nbsp;&nbsp;&nbsp;&nbsp;=20
84099|&nbsp;&nbsp;&nbsp; 318916(3.79)|&nbsp;&nbsp;&nbsp;=20
268987(3.20)|15.66|<BR>|&nbsp; 4|&nbsp;&nbsp; 54607|&nbsp;&nbsp;&nbsp;=20
218428|&nbsp;&nbsp;&nbsp; 826020(3.78)|&nbsp;&nbsp;&nbsp;=20
639417(2.93)|22.59|<BR>|&nbsp; 5|&nbsp;&nbsp; =
12591|&nbsp;&nbsp;&nbsp;&nbsp;=20
62955|&nbsp;&nbsp;&nbsp; 237862(3.78)|&nbsp;&nbsp;&nbsp;=20
178866(2.84)|24.80|<BR>|&nbsp; 6|&nbsp;&nbsp;&nbsp;=20
7680|&nbsp;&nbsp;&nbsp;&nbsp; 46080|&nbsp;&nbsp;&nbsp;=20
173063(3.76)|&nbsp;&nbsp;&nbsp; 122010(2.65)|29.50|<BR>|&nbsp;=20
7|&nbsp;&nbsp;&nbsp; 2761|&nbsp;&nbsp;&nbsp;&nbsp;=20
19327|&nbsp;&nbsp;&nbsp;&nbsp; 72750(3.76)|&nbsp;&nbsp;&nbsp;&nbsp;=20
49710(2.57)|31.67|<BR>|&nbsp; 8|&nbsp;&nbsp;&nbsp; =
1336|&nbsp;&nbsp;&nbsp;&nbsp;=20
10688|&nbsp;&nbsp;&nbsp;&nbsp; 40078(3.75)|&nbsp;&nbsp;&nbsp;&nbsp;=20
26187(2.45)|34.66|<BR>|&nbsp; 9|&nbsp;&nbsp;&nbsp;&nbsp;=20
641|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5769|&nbsp;&nbsp;&nbsp;&nbsp;=20
21554(3.74)|&nbsp;&nbsp;&nbsp;&nbsp; 14009(2.43)|35.01|<BR>|=20
10|&nbsp;&nbsp;&nbsp;&nbsp; 298|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
2980|&nbsp;&nbsp;&nbsp;&nbsp; 11164(3.75)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

7095(2.38)|36.45|<BR>| 11|&nbsp;&nbsp;&nbsp;&nbsp;=20
137|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1507|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
5671(3.76)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3482(2.31)|38.60|<BR>|=20
12|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
57|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
684|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2528(3.70)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
1678(2.45)|33.62|<BR>| 13|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
25|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
325|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
1188(3.66)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 807(2.48)|32.07|<BR>|=20
14|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
6|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
84|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
309(3.68)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 202(2.40)|34.63|<BR>|=20
15|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
6|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
90|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
323(3.59)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 204(2.27)|36.84|<BR>|=20
17|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
1|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
17|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
55(3.24)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
39(2.29)|29.09|</DIV>
<DIV>&nbsp;</DIV>
<DIV>|&nbsp;&nbsp; |&nbsp; 154707|&nbsp;&nbsp;&nbsp; 542354|&nbsp;&nbsp; =

2055062(3.79)|&nbsp;&nbsp; 1624312(2.99)|20.96|<BR></FONT></DIV></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV>
<DIV><FONT=20
size=3D2>----------------------------------------------------------------=
---</FONT></DIV>
<DIV><FONT size=3D2>LDUDE&nbsp; with pure Hangul =
ML.com</FONT></DIV></DIV>
<DIV><FONT=20
size=3D2>&nbsp;<BR>N:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;=20
length of a domain label ( # of code=20
points)<BR>FREQ:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; number =
domains=20
of length N<BR>N*FREQ:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sum of # of =
code=20
points of domains of length N<BR>SUM OF DUDE:&nbsp; sum of lengths of =
DUDE=20
labels<BR>X:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
SUM OF DUDE / N * FREQ<BR>SUM OF LDUDE: sum of lengths of LDUDE=20
labels<BR>Y:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
SUM OF LDUDE / N * =
FREQ<BR>COMP:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
(SUM OF LDUDE - SUM OF DUDE) / SUM OF DUDE * 100</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>|&nbsp; N|&nbsp;&nbsp;&nbsp; FREQ|&nbsp;&nbsp;&nbsp; =

N*FREQ|&nbsp; SUM OF DUDE(X)| SUM OF LDUDE(Y)| COMP|</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>|&nbsp; 1|&nbsp;&nbsp;&nbsp;=20
1940|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1940|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
7760(4.00)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7760(4.00)|0.00|<BR>|&nbsp;=20
2|&nbsp;&nbsp; 16492|&nbsp;&nbsp;&nbsp;&nbsp; 32984|&nbsp;&nbsp;&nbsp;=20
125398(3.80)|&nbsp;&nbsp;&nbsp; 107795(3.27)|14.04|<BR>|&nbsp; =
3|&nbsp;&nbsp;=20
37406|&nbsp;&nbsp;&nbsp; 112218|&nbsp;&nbsp;&nbsp;=20
420812(3.75)|&nbsp;&nbsp;&nbsp; 328202(2.92)|22.01|<BR>|&nbsp; =
4|&nbsp;&nbsp;=20
57732|&nbsp;&nbsp;&nbsp; 230928|&nbsp;&nbsp;&nbsp;=20
860712(3.73)|&nbsp;&nbsp;&nbsp; 610053(2.64)|29.12|<BR>|&nbsp; =
5|&nbsp;&nbsp;=20
36661|&nbsp;&nbsp;&nbsp; 183305|&nbsp;&nbsp;&nbsp;=20
682356(3.72)|&nbsp;&nbsp;&nbsp; 454656(2.48)|33.37|<BR>|&nbsp; =
6|&nbsp;&nbsp;=20
22090|&nbsp;&nbsp;&nbsp; 132540|&nbsp;&nbsp;&nbsp;=20
492239(3.71)|&nbsp;&nbsp;&nbsp; 313997(2.37)|36.21|<BR>|&nbsp; =
7|&nbsp;&nbsp;=20
11503|&nbsp;&nbsp;&nbsp;&nbsp; 80521|&nbsp;&nbsp;&nbsp;=20
298365(3.71)|&nbsp;&nbsp;&nbsp; 186251(2.31)|37.58|<BR>|&nbsp;=20
8|&nbsp;&nbsp;&nbsp; 4963|&nbsp;&nbsp;&nbsp;&nbsp; =
39704|&nbsp;&nbsp;&nbsp;=20
146595(3.69)|&nbsp;&nbsp;&nbsp;&nbsp; 89221(2.25)|39.14|<BR>|&nbsp;=20
9|&nbsp;&nbsp;&nbsp; 2104|&nbsp;&nbsp;&nbsp;&nbsp;=20
18936|&nbsp;&nbsp;&nbsp;&nbsp; 69955(3.69)|&nbsp;&nbsp;&nbsp;&nbsp;=20
42413(2.24)|39.37|<BR>| 10|&nbsp;&nbsp;&nbsp;&nbsp;=20
833|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8330|&nbsp;&nbsp;&nbsp;&nbsp;=20
30705(3.69)|&nbsp;&nbsp;&nbsp;&nbsp; 18333(2.20)|40.29|<BR>|=20
11|&nbsp;&nbsp;&nbsp;&nbsp; 358|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
3938|&nbsp;&nbsp;&nbsp;&nbsp; 14452(3.67)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

8628(2.19)|40.30|<BR>| 12|&nbsp;&nbsp;&nbsp;&nbsp;=20
123|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1476|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
5397(3.66)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3314(2.25)|38.60|<BR>|=20
13|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
71|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
923|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
3387(3.67)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
2055(2.23)|39.33|<BR>| 14|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
28|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
392|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
1452(3.70)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 893(2.28)|38.50|<BR>|=20
15|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
18|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
270|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
998(3.70)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 632(2.34)|36.67|<BR>|=20
16|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
10|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
160|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
582(3.64)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 386(2.41)|33.68|<BR>|=20
17|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
7|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
119|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
438(3.68)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
272(2.29)|37.90|</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>|&nbsp;&nbsp; |&nbsp; 192339|&nbsp;&nbsp;&nbsp;=20
848684|&nbsp;&nbsp; 3161603(3.73)|&nbsp;&nbsp;=20
2174861(2.56)|31.21|<BR></FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>&nbsp;</DIV></FONT>
<DIV><FONT size=3D2></FONT><FONT =
size=3D2>&nbsp;</DIV></FONT></BODY></HTML>

------=_NextPart_000_00FA_01C10B80.90D54560--




From owner-idn@ops.ietf.org  Fri Jul 13 01:47:41 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA03192
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 01:47:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Kv3z-0002F3-00
	for idn-data@psg.com; Thu, 12 Jul 2001 22:00:27 -0700
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Kv3y-0002Cs-00
	for idn@ops.ietf.org; Thu, 12 Jul 2001 22:00:26 -0700
Received: from [216.153.32.74] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 160901 for idn@ops.ietf.org; Thu, 12 Jul 2001 21:58:46 -0700
Message-ID: <3B4E800D.49220A3@ehsco.com>
Date: Thu, 12 Jul 2001 23:58:53 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: IDN <idn@ops.ietf.org>
Subject: [idn] proposals and deadlines
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


I'd like to clarify that he ACE-UTF8 coexistence protocol I am working on
will *not* be in tomorrow's pool. First of all, it requires the presence
of an ACE for backwards compatibility, and I want to wait for a decision
to be made on that first, without distracting from that process.
Secondarily, this is looking to be an extremely large and complex document
involving multiple delicate factors, and the science simply is not cooked
all of the way through as of yet. Thirdly, I just moved to the other side
of the country and have been without stable connectivity or systems for a
month, and its nowhere near completion. For all of those reasons, my
ACE-UTF8 coexistence protocol will not be in tomorrow's pool.

For those who care, here's an overview of the protocol as planned:

 1) Master files become UTF8.

 2) Servers convert and store ACE and UTF8 versions of IDNs together.

 3) Resolvers present two separate APIs: one for legacy names, one
    for IDNs.

 4) When an application calls the resolver, it uses the appropriate
    API as determined by the application protocol. EG, if an href=
    was encountered that had been encoded in ACE -- and if there
    were no external protocol demands from HTTP or the W3C or
    whoever -- then the legacy APIs would be used. Conversely,
    if the user entered an IDN into the URL input field and this
    were deemed legal through some other protocol that the browser
    was aware of (possibly an HTTP extension), then the extended
    API would be used.

 5) The UTF8 IDN resolver calls would generate messages with an
    EDNS extended label type. Legacy apps or resolvers would
    continue to use the legacy APIs and therefore legacy labels.

 6) Servers would answer EDNS-labelled queries with the raw UTF8
    data, and would answer the legacy queries with the ACE data.
    Any CNAME or PTR handling or any other labels would use this
    same rule (this means that it is important for clients to
    always use the extended API whenever they are allowed to do
    so according to protocol mandate).

 7) In those cases where the extended lookup failed (possibly due
    to a non-compliant server returning FORMERR or NOTIMP, or due
    to the resolver not supporting the extended API), the client
    would have to convert the UTF8 IDN to ACE, according to the
    mandate of the higher-layer protocol (EG, whatever the HTTP
    spec said to do whenever an IDN URL failed).

Those are the seven major elements to the protocol.

While this is not a proposal, a few rebuttals to "obvious" problems:

 A) Caches should not be a problem, as clients will have to be
    upgraded to adjust for application-specific UTF8 protocols,
    while nobody will be able to deploy UTF8 IDNs without using
    compatible servers and caches. IOW, as UTF8 IDNs are deployed
    the relevant infrastructure is upgraded along with it. This
    is a marginal cost increase over the upgrade burden for ACE
    usability (client transposition).

 B) The root server only needs to understand the extended label
    type, and will not need to store/use UTF8 until ICANN starts
    to assign IDN TLDs. The TLD servers will need to be upgraded
    to support IDN 3LDs, but this should happen enthusiastically
    in the relevant markets.

 C) The UTF8-to-ACE client fallback conversion should happen
    very infrequently. Protocols will have to support UTF8 IDNs
    themselves before *any* UTF8 IDNs are passed to resolvers,
    and applications will have to be upgraded for those protocols
    to work, and there will most likely have to be a way for a
    server to signify that it supports UTF8 explicitly (ESMTP
    extension, HTTP extension, etc.). For the immediate future,
    all of the queries will be ACE. Eventually, almost all of
    the queries will be UTF8. Fallback should be very rare.

 D) Label lengths are not increased. The hard limit of 255
    octets in the question section is unavoidable. Although it
    would be possible to lengthen the individual labels, it
    is not possible to change the maximum domain name length
    without changing the structure of the DNS message itself.
    This is possible (question section is null, or some other
    hack) but it would be disruptive.

    In fact, the use of EDNS extended label types reduces the
    IDN label length to a maximum of 62 characters.

 E) The coexistence "load" on the servers is unfortunate but it
    should not be preventative. For one thing, it will only 
    require 2x entries for every IDN, not for every domain name
    in every zone. Furthermore, the sooner this happens the
    better, since there will obviously be a smaller total number
    of entries this year than 10 years from now. By then, it
    should be possible to have made most systems speak UTF
    directly, such that support for ACE can be deprecated.

I've started scratching together the document, and am grateful for the
assistance of any interested parties.

Thanks



From owner-idn@ops.ietf.org  Fri Jul 13 01:51:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA04226
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 01:51:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Kt0q-000O5C-00
	for idn-data@psg.com; Thu, 12 Jul 2001 19:49:04 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Kt0p-000O54-00
	for idn@ops.ietf.org; Thu, 12 Jul 2001 19:49:03 -0700
Received: from enoshima (e145218.ppp.asahi-net.or.jp [211.13.145.218])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id LAA23317
	for <idn@ops.ietf.org>; Fri, 13 Jul 2001 11:49:24 +0900 (JST)
Message-Id: <4.2.0.58.J.20010713114727.02c22580@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 13 Jul 2001 11:48:52 +0900
To: idn working group <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] pool deadline imminent
In-Reply-To: <20010712174609.A17455@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 17:46 01/07/12 +0000, Adam M. Costello wrote:
>I didn't really understand until this morning that any proposal that
>doesn't have seven supporters by tomorrow will be out of the running.

Just for the record: If anybody is working on a UTF-8 based
(or even ACE/UTF-8 mixed) solution, they herewith all have
my support (I won't tell them one-by-one).

Regards,   Martin.



From owner-idn@ops.ietf.org  Fri Jul 13 06:27:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA13590
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 06:27:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Kyb7-0008QO-00
	for idn-data@psg.com; Fri, 13 Jul 2001 01:46:53 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Kyb6-0008QF-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 01:46:52 -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 f6D8itP12233; Fri, 13 Jul 2001 10:44:55 +0200 (MEST)
Message-Id: <200107130844.f6D8itP12233@malmo.trab.se>
Date: Fri, 13 Jul 2001 10:47:52 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: [idn] Reality Check
To: idn@ops.ietf.org, amc@cs.berkeley.edu
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: h6J+BZ9Da40TW5D7u65xGA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk


Adam M. Costello wrote:


>> What does the normal human beings of the real world expect from DNS?
>> The semantics of current DNS says:
>> - a name can have mixed upper and lower case letters
>> - names will be matched case insensitively
>> IDNA says:
>> - a name can only be in lower case
>> - names will be matched exactly
>> So IDNA breaks current semantics of DNS.
>
>No, IDNA does not say that.  Application protocols can transmit
>names in non-nameprep'd mixed-case form.  Applications can store
>and display names in non-nameprep'd mixed-case form.  The only
>time it is necessary to apply nameprep is just before comparing
>two names.  Nameprep is mainly just a way to do case-insensitive
>alternate-represenation-insensitive comparisons.
>

IDNA indirectely says the above!
IDNA says that over the DNS protocol namepreped ACE must be used.
Because of this, DNS can only return names in lower case.
So, while you can enter mixed case, the moment a name is sent or
received over the DNS protocol it is converted into lower case and
the mixed case information is lost.

   Dan




From owner-idn@ops.ietf.org  Fri Jul 13 11:05:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA19818
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 11:05:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15L1iN-000D58-00
	for idn-data@psg.com; Fri, 13 Jul 2001 05:06:35 -0700
Received: from twnic.net.tw ([211.72.210.250])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15L1iM-000D51-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 05:06:34 -0700
Received: from twnic.net.tw (pc029.twnic.net.tw [211.72.211.29])
	by twnic.net.tw (8.9.3/8.9.3) with ESMTP id UAA07871;
	Fri, 13 Jul 2001 20:06:12 +0800
Message-ID: <3B4EE803.81EBD285@twnic.net.tw>
Date: Fri, 13 Jul 2001 20:22:27 +0800
From: Erin Chen <erin@twnic.net.tw>
Organization: TWNIC
X-Mailer: Mozilla 4.51 [zh-tw]C-CCK-MCD   (WinNT; U)
X-Accept-Language: zh-TW,en,pdf
MIME-Version: 1.0
To: internet-drafts@ietf.org
CC: jseng@pobox.org.sg, Marc.Blanchet@viagenie.qc.ca, idn@ops.ietf.org,
        Li-Ming Tseng <tsenglm@csie.ncu.edu.tw>,
        Jan-Ming Ho <hoho@iis.sinica.edu.tw>, hlqian <hlqian@cnnic.net.cn>,
        Kenny Huang <huangk@alum.sinica.edu.tw>
Subject: [idn] draft about <draft-ietf-idn-uname-01.txt>
References: <00de01c0ffd0$cd17bfa0$4607e29f@xiaodonglee>
Content-Type: multipart/mixed;
 boundary="------------B51834E02CAAADC7E1B121DA"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

3o,O MIME .f&!*:&h,q&!6l%s!C
--------------B51834E02CAAADC7E1B121DA
Content-Type: text/plain; charset=big5
Content-Transfer-Encoding: 8bit

Dear IETF & IDN WG:

Attached is <draft-ietf-idn-uname-01.txt>.

This document add a practical case to indicate that using CNAME to
implement
UNAME is workable for Internet application to fetch a unique name. And
show
it could be treated as a further process of NAMEPREP and it is
compatible with
the IDNA aproach.

Thanks for any suggestion and comment!

Erin Chen
TWNIC
 

--------------B51834E02CAAADC7E1B121DA
Content-Type: text/plain; charset=big5;
 name="draft-ietf-idn-uname-01.txt"
Content-Disposition: inline;
 filename="draft-ietf-idn-uname-01.txt"
Content-Transfer-Encoding: 7bit

Internet Draft                                         Authors: Li Ming TSENG
<draft-ietf-idn-uname-01.txt>                    		  Jan Ming HO
13 Jul 2001                                                      Hua Lin QIAN
Expires 13 Jan 2002					          Kenny HUANG                                                               Editor: James SENG

       Internationalized Domain Names and Unique Identifiers/Names

Status of this Memo

    This document is an Internet-Draft and is in full conformance 
    with all provisions of Section 10 of RFC2026.

    Internet-Drafts are working documents of the Internet 
    Engineering Task Force (IETF), its areas, and its working 
    groups. Note that other groups may also distribute working 
    documents as Internet-Drafts.

    Internet-Drafts are draft documents valid for a maximum of
    six months and may be updated, replaced, or obsoleted by other
    documents at any time. It is inappropriate to use Internet-
    Drafts as reference material or to cite them other than as
    "work in progress."

    The list of current Internet-Drafts can be accessed at
    http://www.ietf.org/ietf/1id-abstracts.txt

    The list of Internet-Draft Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html


Terminology

The key words "MUST", "SHALL", "REQUIRED", "SHOULD", "RECOMMENDED", and
"MAY" in this document are to be interpreted as described in RFC 2119
[RFC2119].

Abstract

One of the biggest technical challenge of Internationalized Domain 
Names (IDN) is how to determine if the two given domain names matches. 
The current approach to this problem is via a process known as 
[NAMEPREP]. 

This document attempts to describe an alternative view and solution to 
the IDN matching problem. It could be treated as a further process of 
NAMEPREP and it is compatible with the IDNA aproach.

There is a practical case to indicate that using CNAME to implement 
UNAME is workable for Internet application to fetch a unique name.

1. Introduction

The Chinese Domain Name Consortium (CDNC) has taken a very keen 
interest in the IDN, in particular, the uses of chinese script in the 
domain names. CDNC are formed by the regional registries (CNNIC, TWNIC, 
HKNIC and MONIC) and have experimented doing Chinese Domain Names 
System for many months.

The primarily motivation for this proposal is due to the lack of 
support of Traditional and Simplified Chinese in NAMEPREP. See [HAN] 
for a discussion of Traditional/Simplified Han Ideograph problems. 

In addition, given the operational experience of the registries, this 
proposal will reduce the operational and deployment cost from a TLD 
managers' perspective based on the examinations and developments in 
CDNC.

Backward compatibility, interoperability, scalability, security, 
operational and deployment are all elements that must be considered as 
part of criteria when designing internationalized domain name system.

2. Background on Legacy Encoding

The most popular Chinese character set used in Taiwan is the 
industrial standard "BIG5" and the corresponding one in China is 
"GBK". BIG5 have primarily Traditional Chinese characters and GBK have 
Simplified Chinese.
In addition, the China government has also mandated that all Chinese 
software in China must support a new standard that supercede GBK known 
as GB18030.

Both BIG5 and GBK are widely used in China, Taiwan, Hong Kong and 
Macao and supported within many operating systems including Windows. 
Thus, supporting these encodings in IDN is essential from a 
geographical perspective.

3. An overview of current proposals and its problems

3.1. ASCII Compatible Encoding (ACE)

The need of supporting ACE in IDN has been extensively discussed in 
the IDN Working Group. Backward compatibility is the strongest 
advantage of ACE. The deployment of ACE neither affects the existing 
naming infrastructure, nor creates potential damage of current 
Internet applications. To move the current Internet to multilingual 
infrastructure, ACE obviously is the most appropriate bridging 
solution.

Although ACE has the advantages mentioned above, but most of the 
user's systems support local encoding. User doesn't want to download 
any special software or upgrade their software in order to handle 
multilingual domain name system. The support of native encoding 
without altering user's software has became an important issue for 
TLD managers'.

3.2. NAMEPREP

The design goal of [NAMEPREP] is to allow users to enter host names 
in applications and have the highest chance of getting the name 
correct. The NAMEPREP process comprises of three basic steps, namely 
"MAP", "NORMALIZATION" and "PROHIB".

The MAP and NORMALIZATION step aims to reduce the number of possible 
representations domain name that should be equivalent. These are 
based upon Unicode Technical Reports [UTR15] and [UTR21]. However, 
when there are multiple representations of the same domain name but 
matching changes depending on languages and context, NAMEPREP will 
fail in these cases. Of our interest, Traditional and Simplified 
Chinese ideograph cannot be handled by NAMEPREP.

4. Alternative view to the problem space

While the IDN WG has been working very hard to solve the ACE and 
NAMEPREP in IDN, it is apparently that there is another view to these 
problems that may give us a different approach and solution.

First, there is an assumption that NAMEPREP IDN is ISO10646/Unicode 
string. In reality, most IDN is often encoded in legacy encoding and 
a additional step have to be taken to covert it to ISO10646/Unicode.

Other than the backward compatibility feature of ACE, ACE is also an 
identifier string for an IDN. And the NAMEPREP process is to unify the 
various possible representations of IDNs to a single "unique name" for 
matching purposes.

In other words, we have a conceptual model.

  +-------+     +---------+   (ISO10646)
  |XYZ.COM|-->--|Transcode|-->------------+
  +-------+     +---------+      +----------------+     +---------------+
       :  (Legacy)         ...---|NAMEPREP/Unified|-->--|ACE/unique name|
  +-------+     +---------+      +----------------+     +---------------+
  |xyz.com|-->--|Transcode|-->------------+
  --------+     +---------+   (ISO10646)

5. Proposal

Given the context of the alternative view to IDN, we can derive another 
set of solution using a directory concept.

  +-------+       +---------+
  |XYZ.COM|-->----|         |     
  +-------+       |         |     +---------------+
       :  (Legacy)|Directory|-->--|ACE/unique name|
  +-------+       |         |     +---------------+
  |xyz.com|-->----|         |
  +-------+       +---------+

In section 3.2., it mentioned there are some ideograph cannot only be 
handled by NAMEPREP's "MAP", "NORMALIZATION" and "PROHIB" essential 
process. To build up a directory system is to doing as a further  
NAMEPREP process. The further process will solve the matching problem.
For example the one to many and many to one mapping.

The purpose of this directory system is to list all the possible 
representations of IDNs and unify them to a unique name. This unique 
name could be an ACE of the most common representation or NAMEPREPPED 
ACE.

The content of the directory is build up upon registration whereby 
registrant will have to provide a list of equivalence representation 
of the domain names they registered.

However, there is still a question of what directory should we use. 
In this document, we shall examine a couple of different solutions.

5.1. LDAP as Directory

Lightweight Directory Access Protocol [LDAP] is one of the most 
widely used directory protocols. In LDAP, there is a concept of 
hierarchy similar to the DNS hierarchy. Hence, it is possible to 
distribute the content of the directory across various LDAP servers 
for scalability and authority control. For example, each registries 
who wish to deploy IDN may setup an LDAP server and to register this 
LDAP with a "root" LDAP server.

The IDN query process would then look something like this:
   a. User Input IDN name into an application
   b. Application does a LDAP query to look for unique name
   c. Application use unique name to do DNS lookup

Advantages:
   - encapsulate the problem in the representation layer and 
     registration time
   - able to handle with unification problems 

Disadvantage 
   - requires all applications to upgrade 
   - additional LDAP lookup overhead
   - policy issues with "root" LDAP server
   - requires access to LDAP servers to function, i.e. can't work 
offline

5.2. CNRP as Directory

Common Name Resolution Protocol [CNRP] is a newly developed protocol 
in IETF that does common names resolutions. In CNRP, there is no 
concept of hierarchy but there is a referrer scheme. Hence, it is 
possible to build a distributed directory system whereby they refer 
to each another.

The IDN query process would then look something like this:
  a. User Input IDN name into an application
  b. Application does a CNRP query to look for unique name
  c. Application use unique name to do DNS lookup

Advantages:
   - encapsulate the problem in the representation layer and 
     registration time
   - able to handle with unification problems
   - no policy issues with "root" CNRP server

Disadvantage 
   - requires all applications to upgrade
   - additional CNRP lookup overhead and no assurance that unique name 
     can be located
   - requires access to CNRP servers to function, i.e. can't work 
offline

5.3. DNS as Directory

Domain Name System [DNS] is a widely established lookup distributed 
directory. There is an existing hierarchy structure and resource 
records are distributed. In theory, the DNS is able to handle 8-bit 
binary string.

The IDN query process would then look something like this:
   a. User Input IDN name into an application
   b. Application does a DNS query to look for unique name which will 
return the       Resource Record of the unique name together

Advantages:
   - encapsulate the problem in the representation layer and 
     registration time
   - able to handle with unification problems
   - existing "root" DNS server with existing hierarchy
   - does not requires all applications to upgrade

Disadvantage 
   - unknown behavior on applications which cannot handle 8-bit 
   - unknown behavior of servers/caching software which cannot handle 
8-bit

6. Solution

Given CDNC operational experience that it is difficult to get 
applications developers to upgrade, difficult to get users to 
download new applications and difficult etc, using DNS as a Directory 
would be the fastest approach to deploy IDN for our users.

6.1. Zone file

Because there are multiple encoding and multiple representation of the 
same name even within the same encoding, for a single name, there are 
multiple binary strings for a single domain name (e.g. ML1, ML2, ML3, 
ML4).

Hence, we would create the following Resource Records within the name 
server. In the Resource Records, it would look like this:

ML1		UNAME		ACE1
ML2		UNAME		ACE1
ML3		UNAME		ACE1
ML4		UNAME		ACE1

ACE1		IN 	A	1.2.3.4.
		IN	A	1.2.3.4.

A "UNAME" Resource Record is shown here. In practice, it could be 
CNAME (except CNAME is unable to handle MX).

6.2. The practical case of implementing UNAME with CNAME

Before the UNAME protocol is defined, in TWNIC IDN testbed, it has 
implimented IDN unique name with CNAME in current stage. When register 
a Traditional Chinese domain name(TCDN) can get another one 
corresponding Simplified Chinese domain name(SCDN). The Traditional 
and Simplified Chinese Conversion is defined in [TSCONV].

The Resource Records is look like this:

TCDN1		CNAME		EDN1
SCDN1		CNAME		EDN1
EDN1		IN	A	IP-of-EDN1

If the EDN1 is not in the same domain with TCDN1 and SCDN1, that the
Resource Record of EDN1 would in the different zone file. The left 
side of CNAME Resource Record would be all of the equivalent ML1, 
ML2 .... Like TCDN1 and SCDN1 are equivalent. The right side of CNAME 
Resource Record would be an unique name of ACE compatible. EDN1
(English Domain Name 1) is a kind of ACE compatible nique name. EDN1 
could be substiude with any kind of ACE compatible unique name. Such 
like xACE encode or random number. Once the xACE is decided by IETF 
IDN WG, the implimentation would adopt the standard. The unique name 
also retains compatible with [IDNA] approach. 

In order to get the unique name EDN1 not the destination IP-of-EDN1,
there would be construct some intermediate server. In TWNIC testbed,
there are Web DNS or DNS proxy as the intermediate server. Any 
application can pass a TCDN1 or SCDN1 to the intermediate server. The 
intermediate server would ask the DNS for the coresponding right side 
which is the unique name. And then pass the unique name EDN1 to the 
application. And then go with the current DNS infrastructure. Once the 
UNAME protocol is defined, there is no more need a intermediate server.

The process could be represented as following:

                                +------+
                                | User |
                                +------+
                                 |    ^
                   Request to AP |    | Response from AP
                   with MDN      |    |                   End system
    +----------------------------|----|----------------------------+
    |                            v                                 |
    |  +--------------------------------------------------------+  |
    |  |                  Application Client                    |  |
    |  +--------------------------------------------------------+  |
    |      |  ^ Nameprepped               |  ^         |  ^        |
    |  MDN |  | ACE compatible            |  |         |  |        |
    |      |  | unique name               |  | IP of   |  |        |
    |      v  |            Nameprepped    |  | unique  |  |        | 
    |  +--------------+    ACE compatible |  | name    |  |        |
    |  | intermediate |    unique name    v  |         |  |        |
    |  |  server      |             +----------+       |  |        |
    |  +--------------+             | Resolver |       |  |        |
    |      |  ^ Nameprepped         +----------+       |  |        |
    |  MDN |  | ACE compatible        |  ^             |  |        |          
    |      |  | unique name           |  |             |  |        |
    |  +--------------+               |  |     Request |  |Response|
    |  | Directory of |               |  |     for     |  |from    |
    |  | DNS          |               |  |     service |  |server  |
    |  +--------------+               |  |             |  |        |
    |                                 |  |             |  |        |
    +---------------------------------|--|-------------|--|--------+
                       Nameprepped ACE|  | IP of       |  |
                       compatible     |  | unique      |  |
                       unique name    v  | name        v  |
                            +-------------+  +---------------------+
                            | DNS servers |  | Application servers |
                            +-------------+  +---------------------+

6.3. Advantages

The strongest advantage to this solution is that:
a. This does not requires our users to download any special software 
or upgrade their software since it is able to handle the native 
encoding of the user directly

b. It will work immediately for ccTLD who wish to offers ML.ccTLD 
services without any changes at the user client

c. It also retains the compatible with IDNA approach so long we keep 
the unique name equivalent to NAMEPREPPED ACE.

d. Existing DNS hierarchy 

6.4. Potential Loopholes

There are many loopholes within this solution that we need to take 
note:

a. Some "smart" localized browser will send out "wrong" binary 
string due to different. For example, English Internet Explorer will 
not be able to handle Chinese double-byte legacy encoding properly.
But if there is the requirement of use double-byte encoding, the 
appropriate application environment is necessary.

b. While Chinese have a handful (usually 2 to 3) representation 
forms for a single IDN, other languages may have much more 
complicated representations which may not be suitable to use this 
approach. For example, if case-folding for Latin character is done 
using this solution, for a string length of 32 characters, it will 
requires 2^32 entries in the DNS. But this could be solved in some 
other means.

c. It might be possible to construct a binary string in some legacy 
encoding which gives the same binary representation for another 
domain name (a.k.a. binary collision). The binary collesion of in the 
same zone could be avoided by registration system and policy. If the 
left side of UNAME (like ML1,ML2, ML3, ML4 or TCDN1, SCDN1) are not in 
the same zone, they would not occur binary collesion. The intermediate 
server would have the ability to decide which zone of DNS directory it 
sould access.

Acknowledgement

Author(s)

Li Ming Tseng, Prof
National Central University, TWNIC
Email: tsenglm@cc.ncu.edu.tw
Tel: +886-3-490-4421

Jan Ming Ho, Prof
Academia Sinica, TWNIC
Email: hoho@iis.sinica.edu.tw
Tel: +886-2-2788-3799 x 1803

Hua lin Qian, Prof
Chinese Academy of Science, CNNIC
Email: hlqian@ns.cnc.ac.cn
Tel: +86-10-6256-9960

Kenny Huang
Asia Infra International Ltd, TWNIC
Email: huangk@alum.sinica.edu
Tel: +886-2-2658-6510

Editor: James SENG
i-DNS.net International
8 Temasek Boulevard
Suntec Tower Three #24-02
Singapore 038988
Email: jseng@i-dns.net
Tel: +65-2486-188

Editor: Erin Chen
Taiwan Network Information Center (TWNIC)
4F-2, No. 9, Sec. 2, Roosevelt Rd., Taipei, 100 Taiwan.
Email: erin@twnic.net.tw
Tel: +886-2-23411313#502

Reference

[IDNREQ]	Requirements of Internationalized Domain Names, Zita Wenzel, 
                James Seng, draft-ietf-idn-requirements

[NAMEPREP]	Preparation of Internationalized Host Names, P. Hoffman, 
                M. Blanchet, draft-ietf-idn-nameprep

[HAN]		Han Ideograph (CJK) for Internationalized Domain Names, 
                J. Seng, Y. Yoneya, K. Huang, K. Kim, draft-ietf-idn-cjk

[LDAP]	        Lightweight Directory Access Protocol (v3), M. Wahl, 
                T. Howes, S. Kille, rfc2251.txt

[CNRP]	        Common Name Resolution Protocol, N. Popp, M. Mealing, 
                M. Moseley, draft-ietf-cnrp

[DNS]		Domain Names - Implementation and Specification, 
                P. Mockapetris, RFC1035

[CJKV]          CJKV Information Processing ISBN 1-56592-224-7

[UTR15] 	Unicode Normalization Forms, Mark Davis and Martin Duerst,
                Unicode Technical Report 15.

[UTR21]         Case Mappings, Mark Davis, Unicode Technical Report 21.

[TSCONV]	Traditonal and Simplified Chinese Conversion, XiaoDong LEE,
		HSU NAI-WEN, Erin Chen, GuoNian SUN, CNNIC, TWNIC, CDNC,
		draft-ietf-idn-tsconv

[IDNA]		Internationalizing Host Names In Applications (IDNA),
		Patrik Faltstrom, Paul Hoffman, draft-ietf-idn-idna                                    Cisco


             



--------------B51834E02CAAADC7E1B121DA--




From owner-idn@ops.ietf.org  Fri Jul 13 12:03:02 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA19830
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 11:05:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15L1nl-000DAa-00
	for idn-data@psg.com; Fri, 13 Jul 2001 05:12:09 -0700
Received: from twnic.net.tw ([211.72.210.250])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15L1nk-000DAU-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 05:12:08 -0700
Received: from twnic.net.tw (pc029.twnic.net.tw [211.72.211.29])
	by twnic.net.tw (8.9.3/8.9.3) with ESMTP id UAA08204;
	Fri, 13 Jul 2001 20:12:01 +0800
Message-ID: <3B4EE960.DD253971@twnic.net.tw>
Date: Fri, 13 Jul 2001 20:28:16 +0800
From: Erin Chen <erin@twnic.net.tw>
Organization: TWNIC
X-Mailer: Mozilla 4.51 [zh-tw]C-CCK-MCD   (WinNT; U)
X-Accept-Language: zh-TW,en,pdf
MIME-Version: 1.0
To: internet-drafts@ietf.org
CC: jseng@pobox.org.sg, Marc.Blanchet@viagenie.qc.ca, idn@ops.ietf.org,
        abelyang@twnic.net.tw
Subject: [idn] draft about Evaluation of various ACEs with existing Chinese 
 (BIG5) Domain Names
References: <00de01c0ffd0$cd17bfa0$4607e29f@xiaodonglee>
Content-Type: multipart/mixed;
 boundary="------------1438EFA646E9FC984C61F8BD"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

3o,O MIME .f&!*:&h,q&!6l%s!C
--------------1438EFA646E9FC984C61F8BD
Content-Type: text/plain; charset=big5
Content-Transfer-Encoding: 8bit

Dear IETF & IDN WG:

Attached is the draft of :
Evaluation of various ACEs with existing Chinese (BIG5) Domain Names

This document offer an overview of the results of various ACEs that
being
applied to Chinese (BIG5) Domain Names. And give a brief summary of
the evaluation result.

Thanks for any suggestion and comment!

Erin Chen
TWNIC
 

--------------1438EFA646E9FC984C61F8BD
Content-Type: text/plain; charset=big5;
 name="draft-ietf-idn-ace-eval-tw-00.txt"
Content-Disposition: inline;
 filename="draft-ietf-idn-ace-eval-tw-00.txt"
Content-Transfer-Encoding: 7bit

Internet Draft                                                 Abel Yang
draft-ietf-idn-ace-eval-tw-00.txt                              Erin Chen 
Jul 13, 2001                                                       TWNIC
Expires Jan 13, 2002                                           

   Evaluation of various ACEs with existing Chinese (BIG5) Domain Names

Status of this memo

    This document is an Internet-Draft and is in full conformance with
    all provisions of Section 10 of RFC2026.

    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as 
    Internet-Drafts.

    Internet-Drafts are draft documents valid for a maximum of six
    months and may be updated, replaced, or obsoleted by other documents
    at any time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."

    The list of current Internet-Drafts can be accessed at
    http://www.ietf.org/ietf/1id-abstracts.txt

    The list of Internet-Draft Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html.



Abstract

    In order to help the ACE (ASCII Compatible Encoding) Design Team in 
    IDN Working Group to selecting an appropriate ACE proposal. This 
    document offer an overview of the results of various ACEs that being
    applied to Chinese (BIG5) Domain Names. And give a brief summary of 
    the evaluation result.

1. Test data and tools

    The sample data were come from TWNIC registration database. All of 
    them are in BIG5 encoding. The amount of the data is 28454. And the 
    data distribution by the length is:

      Length of data     quantity of BIG5 Domain Names
    	2 chars			3762 
	3 chars			3914 
	4 chars			4613 
	5 chars			1723 
	6 chars			1851 
	7 chars			4282 
	8 chars			1621 
	9 chars			1254 
       10 chars			2075 
       11 chars			1215 
       12 chars		 	 753 
       13 chars			 646 
       14 chars			 745 
	
	                amount=28454 
	
    TWNIC just accept 2 to 14 BIG5 chars in a Chinese Domain Name. Those 
    data are all in local encoding of BIG5 ( or CP950 ). Base on those 
    data, apply them to various ACEs. There are RACE-03 [RACE], BRACE-00 
    [BRACE], LACE-01 [LACE], UTF-6-00 [UTF6], DUDE-02 [DUDE], 
    AMC-ACE-M-00 [AMCACEM], AltDUDE-01 [AltDUDE], AMC-ACE-O-00 [AMCACEO], 
    and AMC-ACE-R-01 [AMCACER].
    
2. Result of each ACE length
    
    The CHN_len is the length of Chinese (BIG5) domain name in byte 
    before apply ACE encoding. All of the data in the same CHN_len, the 
    max_len is the maximum length, the min_len is the minimum length, 
    the aver_len is the averager length of them after apply ACE encoding.

  2.1 AMC-ACE-M

    CHN_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    	2		 8	 5	 8 
	3		11	 6	11 
	4		17	 8	14 
	5		17	11	17 
	6		21	11	20 
	7		24	13	22 
	8		27	15	25 
	9		30	16	28 
	10		33	18	31 
	11		36	22	34 
	12		39	19	37 
	13		42	21	40 
	14		45	23	43 


  2.2 AMC-ACE-O

    CHN_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
	2		 8	 5	 8 
	3		12	 6	11 
	4		20	 9	15 
	5		20	11	18 
	6		24	11	22 
	7		27	13	25 
	8		31	15	29 
	9		35	16	32 
	10		39	18	36 
	11		42	24	38 
	12		46	19	41 
	13		50	21	44 
	14		54	23	48 


  2.3 AMC-ACE-R

    CHN_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
	2		 8 	 5	 8 
	3		12 	 6	12 
	4		20 	 9	16 
	5		20 	11	19 
	6		24 	11	23 
	7		28 	13	26 
	8		32 	15	30 
	9		36 	16	34 
	10		40 	18	38 
	11		44 	24	41 
	12		48 	19	44 
	13		52 	21	48 
	14		56 	24	51 

  
  2.4 AltDUDE

    CHN_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
	2		 8	 5	 8 
	3		12	 6	11 
	4		20	 8	16 
	5		20	13	19 
	6		24	11	23 
	7		28	14	26 
	8		32	15	30 
	9		36	18	34 
	10		40	21	38 
	11		44	26	41 
	12		48	26	46 
	13		52	25	48 
	14		56	30	53 


  2.5 BRACE

    CHN_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    	2		 7	 5	 7 
	3		10	 7	10 
	4		17	 8	14 
	5		17	11	17 
	6		20	11	20 
	7		23	13	23 
	8		28	14	26 
	9		30	15	30 
	10		33	17	33 
	11		36	22	36 
	12		39	18	39 
	13		42	20	42 
	14		46	23	46 


  2.6 DUDE

    CHN_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    	2		 8	 5	 8 
	3		12	 6	11 
	4		20	 8	16 
	5		20	13	19 
	6		24	11	23 
	7		28	15	26 
	8		32	15	30 
	9		36	18	34 
	10		40	21	38 
	11		44	27	41 
	12		48	26	46 
	13		52	25	48 
	14		56	30	53 


  2.7 LACE

    CHN_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    	2		 8	 7	 8 
	3		12	 8	12 
	4		18	10	15 
	5		18	18	18 
	6		21	16	21 
	7		24	21	24 
	8		31	23	28 
	9		31	24	31 
	10		34	26	34 
	11		37	34	37 
	12		40	29	40 
	13		44	31	44 
	14		47	36	47 
  
  2.8 RACE

    CHN_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    	2		 8	 5	 8 
	3		12	 7	12 
	4		18	 8	15 
	5		18	18	18 
	6		21	20	21 
	7		24	24	24 
	8		31	28	28 
	9		31	31	31 
	10		34	34	34 
	11		37	37	37 
	12		40	40	40 
	13		44	44	44 
	14		47	47	47 



  2.9 UTF-6

    CHN_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    	2		 8	 5	 8 
	3		12	 6	12 
	4		20	 9	16 
	5		20	14	20 
	6		24	14	24 
	7		28	18	28 
	8		32	20	32 
	9		36	21	36 
	10		40	23	40 
	11		44	30	44 
	12		48	28	48 
	13		52	29	52 
	14		56	33	56 

3. Result of each ACE conversion speed

		UTF-6	RACE	LACE	BRACE	DUDE	ALTDUDE	
	MAX	0.80 	0.75 	0.82 	0.86 	0.74 	0.70 	
	MIN	0.56 	0.55 	0.52 	0.62 	0.53 	0.53 	
	AVERAGE	0.68 	0.64 	0.62 	0.73 	0.64 	0.62 	

		AMC-ACE-M	AMC-AMC-O	AMC-ACE-R
	MAX	1.12 		1.92 		0.99 
	MIN	0.86 		1.69 		0.67 
	AVERAGE	0.98 		1.81 		0.82 




4. Summary of the result

    All the ACE max_length is less than 64, because the Chinese 
    Domain Name is limited from 2 to 14 BIG5 chars. For those sample
    data, the result of LENGTH and SPEED, it seems the LACE and RACE 
    are better than others.
        
5. Acknowledgements

    This ACE evaluation testing tool was provided by JPNIC. 
    TWNIC provide the real registered Chinese ( BIG5 ) domain names.
    Hsu Nai-Wen <snw@twnic.net.tw> and TWNIC MDNS technical team give 
    a lot of suggestion.            

6. Author's Address

    Abel Yang
    Taiwan Network Information Center (TWNIC)
    4F-2, No. 9, Sec. 2, Roosevelt Rd., Taipei, 100 Taiwan.
    Email: abelyang@twnic.net.tw
    Tel: +886-23411313#505

    Erin Chen
    Taiwan Network Information Center (TWNIC)
    4F-2, No. 9, Sec. 2, Roosevelt Rd., Taipei, 100 Taiwan.
    Email: erin@twnic.net.tw
    Tel: +886-23411313#502

7. References

    [RFC1035]  "DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION",
               RFC1034, Nov 1987, P. Mockapetris
    [RACE]     "RACE: Row-based ASCII Compatible Encoding for IDN",
               draft-ietf-idn-race-03.txt, Nov 2000, P Hoffman
    [BRACE]    "BRACE: Bi-mode Row-based ASCII-Compatible Encoding
   	       for IDN version 0.1.2"
               draft-ietf-idn-brace-00.txti, Sep 2000, A Costello
    [LACE]     "LACE: Length-based ASCII Compatible Encoding for IDN"
               draft-ietf-idn-lace-01.txt, Jan 2001, M Davis, P Hoffman
    [UTF6]     "UTF-6 - Yet Another ASCII-Compatible Encoding for IDN"
               draft-ietf-idn-utf6-00, Nov 2000, M Welter, B Spolarich
    [DUDE]     "Differential Unicode Domain Encoding (DUDE)"
               draft-ietf-idn-dude-02.txt, Jun 2001, M Welter, 
	       B Spolarich, A Costello
    [AMCACEM]  "AMC-ACE-M version 0.1.0"
               draft-ietf-idn-amc-ace-m-00.txt, Feb 2001, A Costello
    [AltDUDE]  "AltDUDE version 0.0.2"
               draft-ietf-idn-altdude-00.txt, Mar 2001, A Costello
    [AMCACEO]  "AMC-ACE-O version 0.0.3"
               draft-ietf-idn-amc-ace-o-00.txt, Mar 2001, A Costello
    [AMCACER]  "AMC-ACE-R version 0.2.1"
               draft-ietf-idn-amc-ace-r-01.txt, May 2001, A Costello
    [AMCACEV]  "AMC-ACE-V version 0.1.0"
               draft-ietf-idn-amc-ace-v-00.txt, May 2001, A Costello
    [AMCACEW]  "AMC-ACE-W version 0.1.0"
               draft-ietf-idn-amc-ace-w-00.txt, May 2001, A Costello
    [MACE]     "MACE: Modal ASCII Compatible Encoding for IDN"
               draft-ietf-idn-mace-00.txt, Jun 2001, M Ishisone, Y Yoneya
    [LDUDE]    "Improving ACE using code point reordering v0.9"
               draft-ietf-idn-lsb-ace-00.txt, Jun 2001, Soobok Lee
    [MDNKIT]   "Multilingual Domain Name tool Kit",
               http://www.nic.ad.jp/jp/research/idn/mdnkit/download/
    [NAMEPREP] "Preparation of Internationalized Host Names",                 
               draft-ietf-idn-nameprep-03.txt, Feb 2001, P Hoffman, 
	       M Blanchet
    



--------------1438EFA646E9FC984C61F8BD--




From owner-idn@ops.ietf.org  Fri Jul 13 12:22:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA01259
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 12:22:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15L4q0-000GhX-00
	for idn-data@psg.com; Fri, 13 Jul 2001 08:26:40 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15L4py-000GhQ-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 08:26:38 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6DFQKD24134
	for <idn@ops.ietf.org>; Sat, 14 Jul 2001 00:26:21 +0900 (KST)
Message-ID: <01cb01c10bb0$f9a0d020$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "idn working group" <idn@ops.ietf.org>
Subject: [idn] New revision 1.0 of my I-D  on REORDERING
Date: Sat, 14 Jul 2001 00:32:06 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Today, New revision 1.0 of my I-D on REOREDERING appeared
on IDN WG directory.
http://www.ietf.org/internet-drafts/draft-ietf-idn-lsb-ace-01.txt
This link has the same url  as that of 0.9 but has 
different title and content. (due to some mistakes between me and ietf).
Please click this link and press "refresh"button on your browser
to fetch this new draft.

Next week, I will submit another new draft version 2.0
with new experiments with
AMC-ACE-Z and other ACEs. It will  support 
Hindi,Hiragana,Russian,Arabic 
 in addition to Han,Hangul,Katakana and Latins.

Regards,

Soobok Lee


----- Original Message ----- 
From: "Soobok Lee" <lsb@postel.co.kr>
To: "idn working group" <idn@ops.ietf.org>
Sent: Friday, July 13, 2001 7:09 AM
Subject: call for support for REORDERING


> 
> My I-D on "Improving ACE using code point reordering"
> is looking forward to your supports. It has no contenders, 
> only need your interests.
> 
> It  helps AMC-AMC-Z/DUDE's mean ACE label lengths 
> to be close to that of UCS-2 ( 2*n) for 7 or more letters of 
> typical han/hangul IDNs and does better compression for
> other scripts, too.
> 
> To express your interests ( does not necessarily mean 
> you support all the aspects of my I-D version1.0 )
> in REORDERING, do not hesitate to send mail to me  
> <lsb@postel.co.kr>. 
> 
> You can find my recent I-D (soon to be revised in IDN wg home).
> http://www.postel.co.kr/lsb-ace-01.txt   (version 1.0)
> 
> Soobok Lee
> 
> =========================================================
> The following attachment shows the amounts of
> improvements achieved for big ML.com samples.
> 
> 
> For Chinese ML.com samples.
> 
> N:            length of a domain label ( # of code points)
> FREQ:         number domains of length N
> N*FREQ:       sum of # of code points of domains of length N
> SUM OF AMCZ:  sum of lengths of AMCZ labels
> X:            SUM OF AMCZ / N * FREQ
> SUM OF LAMCZ: sum of lengths of LAMCZ labels
> Y:            SUM OF LAMCZ / N * FREQ
> COMP:         (SUM OF LAMCZ - SUM OF AMCZ) / SUM OF AMCZ * 100
> 
> |  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
> 
> |  1|    4642|      4642|     15804(3.40)|     14807(3.19)|6.31|
> |  2|   59708|    119416|    401549(3.36)|    352022(2.95)|12.33|
> |  3|   49471|    148413|    484456(3.26)|    415104(2.80)|14.32|
> |  4|   99402|    397608|   1269398(3.19)|   1034646(2.60)|18.49|
> |  5|   29974|    149870|    467070(3.12)|    381651(2.55)|18.29|
> |  6|   20809|    124854|    384013(3.08)|    304635(2.44)|20.67|
> |  7|    8860|     62020|    186347(3.00)|    147111(2.37)|21.06|
> |  8|    5251|     42008|    124325(2.96)|     97303(2.32)|21.73|
> |  9|    2666|     23994|     69234(2.89)|     54697(2.28)|21.00|
> | 10|    2008|     20080|     57887(2.88)|     44270(2.20)|23.52|
> | 11|     859|      9449|     26914(2.85)|     20836(2.21)|22.58|
> | 12|     671|      8052|     22819(2.83)|     17294(2.15)|24.21|
> | 13|     346|      4498|     12217(2.72)|      9581(2.13)|21.58|
> | 14|     235|      3290|      9084(2.76)|      6933(2.11)|23.68|
> | 15|     117|      1755|      4723(2.69)|      3721(2.12)|21.22|
> | 16|      68|      1088|      2884(2.65)|      2258(2.08)|21.71|
> | 17|      21|       357|       911(2.55)|       704(1.97)|22.72|
> 
> |   |  285108|   1121394|   3539635(3.16)|   2907573(2.59)|17.86|
> 
> 
> 
> 
> 
> For Korean ML.com samples.
> 
> N:            length of a domain label ( # of code points)
> FREQ:         number domains of length N
> N*FREQ:       sum of # of code points of domains of length N
> SUM OF AMCZ:  sum of lengths of AMCZ labels
> X:            SUM OF AMCZ / N * FREQ
> SUM OF LAMCZ: sum of lengths of LAMCZ labels
> Y:            SUM OF LAMCZ / N * FREQ
> COMP:         (SUM OF LAMCZ - SUM OF AMCZ) / SUM OF AMCZ * 100
> 
> |  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
> 
> |  1|    1941|      1941|      7764(4.00)|      7764(4.00)|0.00|
> |  2|   16978|     33956|    123248(3.63)|    105628(3.11)|14.30|
> |  3|   38852|    116556|    394410(3.38)|    322373(2.77)|18.26|
> |  4|   61642|    246568|    803121(3.26)|    625970(2.54)|22.06|
> |  5|   40375|    201875|    639079(3.17)|    483118(2.39)|24.40|
> |  6|   24561|    147366|    458978(3.11)|    337398(2.29)|26.49|
> |  7|   13034|     91238|    280346(3.07)|    203406(2.23)|27.44|
> |  8|    5596|     44768|    136452(3.05)|     97248(2.17)|28.73|
> |  9|    2421|     21789|     65504(3.01)|     46536(2.14)|28.96|
> | 10|    1033|     10330|     29964(2.90)|     21330(2.06)|28.81|
> | 11|     427|      4697|     13845(2.95)|      9739(2.07)|29.66|
> | 12|     173|      2076|      5905(2.84)|      4261(2.05)|27.84|
> | 13|      96|      1248|      3588(2.88)|      2539(2.03)|29.24|
> | 14|      32|       448|      1331(2.97)|       921(2.06)|30.80|
> | 15|      22|       330|       927(2.81)|       675(2.05)|27.18|
> | 16|      15|       240|       606(2.52)|       471(1.96)|22.28|
> | 17|       8|       136|       378(2.78)|       267(1.96)|29.37|
> | 19|       1|        19|        26(1.37)|        26(1.37)|0.00|
> 
> |   |  207207|    925581|   2965472(3.20)|   2269670(2.45)|23.46|
> 
> ----- Original Message ----- 
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: <idn@ops.ietf.org>
> Sent: Tuesday, July 10, 2001 10:37 PM
> Subject: chinese/hangul ML.com statistics with DUDE/LDUDE
> 
> 
> >   
> > The next table is from
> > 285108 chinese ML.com samples (old raw data from VGRS). 
> >  
> > "COMP" column includes improvement ratios of LDUDE over DUDE.
> > "Y" column points that  for long chinese domains, LDUDE's label
> > length is close to (2.0~2.5)*(input domain length).
> > 
> > 
> > N:            length of a domain label ( # of code points)
> > FREQ:         number domains of length N
> > SUM OF DUDE:  sum of lengths of DUDE labels
> > X:            SUM OF DUDE / N * FREQ
> > SUM OF LDUDE: sum of lengths of LDUDE labels
> > Y:            SUM OF LDUDE / N * FREQ
> > COMP:         (SUM OF LDUDE - SUM OF DUDE) / SUM OF DUDE * 100
> > 
> > |  N|    FREQ|    N*FREQ|  SUM OF DUDE(X)| SUM OF LDUDE(Y)| COMP|
> > 
> > |  1|    4642|      4642|     18568(4.00)|     18568(4.00)| 0.00|
> > |  2|   59708|    119416|    462031(3.87)|    415599(3.48)|10.05|
> > |  3|   49471|    148413|    566440(3.82)|    477649(3.22)|15.68|
> > |  4|   99402|    397608|   1509929(3.80)|   1168378(2.94)|22.62|
> > |  5|   29974|    149870|    554237(3.70)|    426226(2.84)|23.10|
> > |  6|   20809|    124854|    457412(3.66)|    333416(2.67)|27.11|
> > |  7|    8860|     62020|    220880(3.56)|    160563(2.59)|27.31|
> > |  8|    5251|     42008|    146822(3.50)|    103903(2.47)|29.23|
> > |  9|    2666|     23994|     81433(3.39)|     58657(2.44)|27.97|
> > | 10|    2008|     20080|     68385(3.41)|     46708(2.33)|31.70|
> > | 11|     859|      9449|     31596(3.34)|     22111(2.34)|30.02|
> > | 12|     671|      8052|     27039(3.36)|     18135(2.25)|32.93|
> > | 13|     346|      4498|     14306(3.18)|     10088(2.24)|29.48|
> > | 14|     235|      3290|     10676(3.24)|      7230(2.20)|32.28|
> > | 15|     117|      1755|      5568(3.17)|      3854(2.20)|30.78|
> > | 16|      68|      1088|      3383(3.11)|      2376(2.18)|29.77|
> > | 17|      21|       357|      1075(3.01)|       750(2.10)|30.23|
> > 
> > |   |  285108|   1121394|   4179780(3.73)|   3274211(2.92)|21.67|
> > 
> > 
> > 
> > The next table is  
> > From 207207 hangul ML.com samples (old raw data from VGRS). 
> > 
> > |  N|    FREQ|    N*FREQ|  SUM OF DUDE(X)| SUM OF LDUDE(Y)| COMP|
> > 
> > |  1|    1941|      1941|      7764(4.00)|      7764(4.00)|0.00|
> > |  2|   16978|     33956|    129239(3.81)|    111308(3.28)|13.87|
> > |  3|   38852|    116556|    436845(3.75)|    341333(2.93)|21.86|
> > |  4|   61642|    246568|    915355(3.71)|    653736(2.65)|28.58|
> > |  5|   40375|    201875|    743090(3.68)|    502097(2.49)|32.43|
> > |  6|   24561|    147366|    540245(3.67)|    349710(2.37)|35.27|
> > |  7|   13034|     91238|    332964(3.65)|    211206(2.31)|36.57|
> > |  8|    5596|     44768|    162833(3.64)|    100618(2.25)|38.21|
> > |  9|    2421|     21789|     78945(3.62)|     48633(2.23)|38.40|
> > | 10|    1033|     10330|     36144(3.50)|     22323(2.16)|38.24|
> > | 11|     427|      4697|     16744(3.56)|     10259(2.18)|38.73|
> > | 12|     173|      2076|      7178(3.46)|      4578(2.21)|36.22|
> > | 13|      96|      1248|      4386(3.51)|      2725(2.18)|37.87|
> > | 14|      32|       448|      1656(3.70)|      1006(2.25)|39.25|
> > | 15|      22|       330|      1168(3.54)|       750(2.27)|35.79|
> > | 16|      15|       240|       757(3.15)|       529(2.20)|30.12|
> > | 17|       8|       136|       470(3.46)|       299(2.20)|36.38|
> > | 19|       1|        19|        30(1.58)|        30(1.58)|0.00|
> > 
> > |   |  207207|    925581|   3415813(3.69)|   2368904(2.56)|30.65|
> > 
> > 
> > 
> > 
> > 
> > 
> 
> 




From owner-idn@ops.ietf.org  Fri Jul 13 13:34:38 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA11796
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 13:34:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15L6IH-000IY9-00
	for idn-data@psg.com; Fri, 13 Jul 2001 09:59:57 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15L6IG-000IY3-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 09:59:56 -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 f6DGuiP15809; Fri, 13 Jul 2001 18:56:45 +0200 (MEST)
Message-Id: <200107131656.f6DGuiP15809@malmo.trab.se>
Date: Fri, 13 Jul 2001 18:59:41 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: [idn] Summary of support for UDNS
To: Marc.Blanchet@viagenie.qc.ca, jseng@pobox.org.sg, idn@ops.ietf.org
Cc: bill@mail.nic.nu, edmon@neteka.com, magnus@gustavsson.se, duerst@w3.org,
        ehall@ehsco.com, djb@cr.yp.to
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: QRbgWDzmPRk5o7KuefVyfQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk

With it being summer vacation time and the short time to collect supporters,
it is not that easy to get responses.

Anyway the following support UDNS (or something based on that):
Dan Oscarsson (myself)
"J. William Semich" <bill@mail.nic.nu>
"Edmon" <edmon@neteka.com>
C C Magnus Gustavsson <magnus@gustavsson.se>
Martin Duerst <duerst@w3.org>
"Eric A. Hall" <ehall@ehsco.com>

That is 6 persons, one less than 7 that is needed to give it "core of interest".

I would expect "D. J. Bernstein" <djb@cr.yp.to> to support it, but he have not
been active lately on the list.
With all the discussions we have had on the list about UTF-8, I would expect
UDNS (which is UTF-8 with ACE for backward compatibility (including IDNA))
to get the 7 needed, if there had been more time to collect supporters.

It is up to our two co-chairs to decide if this is good enough
for "core of interest".

Regards,

   Dan






From owner-idn@ops.ietf.org  Fri Jul 13 13:47:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA13617
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 13:47:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15L6f7-000J2P-00
	for idn-data@psg.com; Fri, 13 Jul 2001 10:23:33 -0700
Received: from [195.149.39.78] (helo=courgette.jml.net ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15L6f6-000J2D-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 10:23:32 -0700
Received: from du-tele3-137.mailbox.co.uk ([195.82.121.137] helo=fluffy.centralnic.com)
	by courgette.jml.net with esmtp (Exim 3.22 #1)
	id 15L6eQ-0006HV-00; Fri, 13 Jul 2001 18:22:53 +0100
Message-Id: <5.1.0.14.2.20010713182304.035e3510@pop3.centralnic.net>
X-Sender: joel@pop3.centralnic.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 13 Jul 2001 18:23:36 +0100
To: Dan Oscarsson <Dan.Oscarsson@trab.se>, Marc.Blanchet@viagenie.qc.ca,
        jseng@pobox.org.sg, idn@ops.ietf.org
From: Joel Rowbottom <joel.rowbottom@centralnic.com>
Subject: Re: [idn] Summary of support for UDNS
Cc: bill@mail.nic.nu, edmon@neteka.com, magnus@gustavsson.se, duerst@w3.org,
        ehall@ehsco.com, djb@cr.yp.to
In-Reply-To: <200107131656.f6DGuiP15809@malmo.trab.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 18:59 13/07/01 +0200, Dan Oscarsson wrote:

>With all the discussions we have had on the list about UTF-8, I would expect
>UDNS (which is UTF-8 with ACE for backward compatibility (including IDNA))
>to get the 7 needed, if there had been more time to collect supporters.

I would certainly support looking into this effort.


--
Joel Rowbottom BSc.(Hons)  :  Chief Technical Officer, CentralNic Ltd.
website - http://www.centralnic.com/   :   email - joel@centralnic.com
London SW6 Office : Tel. +44 (0)20 7751 9000 : Fax +44 (0)20 7736 9253
[---  Don't let my unseriousness make you think it isn't serious  ---]




From owner-idn@ops.ietf.org  Fri Jul 13 18:21:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA20519
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 18:21:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LAxN-000Oka-00
	for idn-data@psg.com; Fri, 13 Jul 2001 14:58:41 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LAxM-000OkT-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 14:58:40 -0700
Received: from [216.153.32.109] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 160985; Fri, 13 Jul 2001 14:58:04 -0700
Message-ID: <3B4F6EF4.560DDE68@ehsco.com>
Date: Fri, 13 Jul 2001 16:58:12 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Adam M. Costello" <amc@cs.berkeley.edu>
CC: IDN <idn@ops.ietf.org>
Subject: Re: [idn] proposals and deadlines
References: <20010713210619.G26469@arwen.cs.berkeley.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



"Adam M. Costello" wrote:
> 
> "Eric A. Hall" <ehall@ehsco.com> wrote:
> 
> >  3) Resolvers present two separate APIs: one for legacy names, one for
> >     IDNs.
> >
> >  5) The UTF8 IDN resolver calls would generate messages with an EDNS
> >     extended label type.
> >
> >  7) In those cases where the extended lookup failed, the client would
> >     have to convert the UTF8 IDN to ACE
> 
> It would not only ACE-encode IDNs in DNS queries, but also ACE-decode
> IDNs in DNS responses (because the application is using the UTF-8 API
> and expects a UTF-8 answer), right?
> 
> This looks like it would work, but if I'm writing a resolver, and I'm
> supposed to implement ACE-encode, ACE-decode, and EDNS, I'm probably
> going to think to myself, "Hmmm, if I just pretend that the EDNS lookup
> always fails, then I won't have to bother implementing EDNS, and the
> application will never know the difference."

Couple of things:

a) the resolver doesn't encode anything, it just passes whatever the
client application passed to it via one of the APIs

b) the fall-back mechanisms for UTF8-to-ACE would need to be specified for
each application. How ESMTP chooses to deal with a failed UTF8 lookup will
be different from how HTTP chooses to deal with it, and so forth.

c) I am going to assume that there will be libraries for most OSes that
provide ACE-encode and ACE-decode functions, since those are already
required for ACE presentation services

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Fri Jul 13 18:22:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA20642
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 18:22:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LA8j-000NYn-00
	for idn-data@psg.com; Fri, 13 Jul 2001 14:06:21 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LA8i-000NYh-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 14:06:20 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15LA8i-000765-00; Fri, 13 Jul 2001 14:06:20 -0700
Date: Fri, 13 Jul 2001 21:06:19 +0000
To: IDN <idn@ops.ietf.org>
Subject: Re: [idn] proposals and deadlines
Message-ID: <20010713210619.G26469@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B4E800D.49220A3@ehsco.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

"Eric A. Hall" <ehall@ehsco.com> wrote:

>  3) Resolvers present two separate APIs: one for legacy names, one for
>     IDNs.
>
>  5) The UTF8 IDN resolver calls would generate messages with an EDNS
>     extended label type.
>
>  7) In those cases where the extended lookup failed, the client would
>     have to convert the UTF8 IDN to ACE

It would not only ACE-encode IDNs in DNS queries, but also ACE-decode
IDNs in DNS responses (because the application is using the UTF-8 API
and expects a UTF-8 answer), right?

This looks like it would work, but if I'm writing a resolver, and I'm
supposed to implement ACE-encode, ACE-decode, and EDNS, I'm probably
going to think to myself, "Hmmm, if I just pretend that the EDNS lookup
always fails, then I won't have to bother implementing EDNS, and the
application will never know the difference."

AMC



From owner-idn@ops.ietf.org  Fri Jul 13 18:22:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA20653
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 18:22:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LA0K-000NN0-00
	for idn-data@psg.com; Fri, 13 Jul 2001 13:57:40 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LA0J-000NMu-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 13:57:39 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15LA0I-00074y-00; Fri, 13 Jul 2001 13:57:38 -0700
Date: Fri, 13 Jul 2001 20:57:38 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] draft about <draft-ietf-idn-uname-01.txt>
Message-ID: <20010713205738.F26469@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B4EE803.81EBD285@twnic.net.tw>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

It is already permissible (I think) for DNS servers to perform more
complex matching than the usual case-insensitive ASCII matching.  For
example, a DNS server implementation could support master file entries
whose keys are regular expressions, and it could compare incoming
requests to those patterns.  For example, it could allow:

foo-?(two|2)   A   1.2.3.4

to be used as shorthand for:

foo2      A   1.2.3.4
footwo    A   1.2.3.4
foo-2     A   1.2.3.4
foo-two   A   1.2.3.4

Similarly, if a DNS server implementation wants to perform
simplified/traditional Chinese matching, or matching of names encoded
in alternate charsets, isn't it already allowed to do so?  Is there any
need to standardize this?

Note that using such a feature will cause problems at higher layers,
because clients won't know the matching rules.  For example, if I
follow a link to www.foo2.net, and later follow a different link to
www.foo-two.net, the link will not be colored as visited.  If I tell
my browser to accept cookies from foo2.net, it won't know to also
accept cookies from foo-two.net.  Same problem with SSL certificates.
Therefore it would probably be desirable to deal with extended matching
not only in the DNS server but also at higher layers.  In these
examples, one might want the HTTP server to redirect requests from the
alternate server names to a single preferred server name.

AMC



From owner-idn@ops.ietf.org  Fri Jul 13 18:25:15 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA20948
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 18:25:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LAx4-000OjO-00
	for idn-data@psg.com; Fri, 13 Jul 2001 14:58:22 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15LAx4-000OjI-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 14:58:22 -0700
Message-ID: <00ff01c10be7$a07297e0$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: "IDN" <idn@ops.ietf.org>, "Adam M. Costello" <amc@cs.berkeley.edu>
References: <20010713210619.G26469@arwen.cs.berkeley.edu>
Subject: Re: [idn] proposals and deadlines
Date: Fri, 13 Jul 2001 18:03:16 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

From: "Adam M. Costello" <amc@cs.berkeley.edu>
> This looks like it would work, but if I'm writing a resolver, and I'm
> supposed to implement ACE-encode, ACE-decode, and EDNS, I'm probably
> going to think to myself, "Hmmm, if I just pretend that the EDNS lookup
> always fails, then I won't have to bother implementing EDNS, and the
> application will never know the difference."
>

But if I am writing a DNS server, I'm probably going to think to myself,
"hmmm, if I pretend that ACE names will be answered by LDH records anyway
(which will be entered into by the zone administrator), then I won't have to
bother implementing ACE conversion and applications will never know the
difference.  I only need to make sure master files could be in UTF8 and I
can answer IDN/EDNS"

And if I am writing an http server (given that http will later support IDN
based on some of the works of this WG), I'm probably going to think to
myself... "hmmm, if I pretend that I dont know ACE and let the information
(ACE form) leak to the users and just implement UTF8, then I wont have to
bother implementing ACE conversion, and the application will never know the
difference."

These in turn (especially ACE leakage) would encourage the
application/resolver developer to eventually implement EDNS.

Edmon




From owner-idn@ops.ietf.org  Fri Jul 13 18:27:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA21220
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 18:27:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LAfj-000OKm-00
	for idn-data@psg.com; Fri, 13 Jul 2001 14:40:27 -0700
Received: from [152.160.20.25] (helo=admin1.corp.walid.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LAfi-000OK1-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 14:40:26 -0700
Received: from CHOAM (admin1.corp.walid.com [152.160.20.25])
	by admin1.corp.walid.com (8.11.2/8.11.2) with SMTP id f6DEk9G18599;
	Fri, 13 Jul 2001 14:46:09 GMT
From: "Brian W. Spolarich" <briansp@walid.com>
To: "Dan Oscarsson" <Dan.Oscarsson@trab.se>, <idn@ops.ietf.org>,
        <amc@cs.berkeley.edu>
Subject: RE: [idn] Reality Check
Date: Fri, 13 Jul 2001 10:55:12 -0400
Message-ID: <FJEPLIJJEDBNPIOAEIHDAEHBCGAA.briansp@walid.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
In-Reply-To: <200107130844.f6D8itP12233@malmo.trab.se>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


| IDNA indirectely says the above!
| IDNA says that over the DNS protocol namepreped ACE must be used.
| Because of this, DNS can only return names in lower case.
| So, while you can enter mixed case, the moment a name is sent or
| received over the DNS protocol it is converted into lower case and
| the mixed case information is lost.

  This does not have to be the case.  An ACE encoder which takes case
information passed by nameprep can store case information for the decoded
name by setting case in the ACE sequence.  The decoder can then use these
hints when converting for display.

  This would require nameprep to capture case before squashing and passing
to an ACE which supports it.  Any of the ACEs which do not break codepoints
during their encoding steps could support this.  DUDE-02 does, as do all of
AMC's alternatives (I think).

  If the WG feels that case preservation in decoding is important, then 1)
it is not inconsistent with IDNA's architecture and 2) the ACE and NamePrep
can be modified to support it without adding too much complexity (beyond the
inherent complexities of case in general).

  -bws




From owner-idn@ops.ietf.org  Fri Jul 13 18:47:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA23496
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 18:47:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15L95o-000M9b-00
	for idn-data@psg.com; Fri, 13 Jul 2001 12:59:16 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15L95n-000M9U-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 12:59:15 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15L95m-00071C-00; Fri, 13 Jul 2001 12:59:14 -0700
Date: Fri, 13 Jul 2001 19:59:14 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Reality Check
Message-ID: <20010713195914.D26469@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FJEPLIJJEDBNPIOAEIHDAEHBCGAA.briansp@walid.com> <200107130844.f6D8itP12233@malmo.trab.se>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dan Oscarsson <Dan.Oscarsson@trab.se> wrote:

> IDNA says that over the DNS protocol namepreped ACE must be used.
> Because of this, DNS can only return names in lower case.

IDNA says that it is possible to use today's DNS, with no changes, for
IDNs, and the way to do that is via nameprep'd ACE.  IDNA does not
forbid DNS extensions.

As Brian has already pointed out, nameprep'd ACE can easily retain
mixed-case information.  So it's still not necessary to change DNS.

If you don't like that solution, you could instead add some new resource
records, like ICNAME and IPTR, which would be just like CNAME and
PTR except that they would contain non-nameprep'd UTF-8 instead of
nameprep'd ACE.  DNS servers could return them along with the legacy
records.  One problem would be that for some names, the ACE will fit in
63 bytes but the UTF-8 will not.

Alternatively, you could alter the DNS protocol itself so that the
request can contain a flag inviting the server to put non-nameprep'd
UTF-8 directly into CNAME and PTR responses.  The length problem would
still exist unless the DNS protocol extension also increased the length
limit.

I recommend the first solution (mixed-case ACE), because it doesn't
have the length problem and appears to be the simplest (given that ACE
already needs to be supported).

> So, while you can enter mixed case, the moment a name is sent or
> received over the DNS protocol it is converted into lower case and the
> mixed case information is lost.

Even if that were true (which it's not in light of mixed-case ACE),
keep in mind that names received from DNS are very rarely displayed to
users (except sysadmins).  CNAME records are usually just looked up
again for their address, and PTR records are usually used internally for
permissions checks, or written to log files or similarly unseen places
(like Received: headers).

AMC



From owner-idn@ops.ietf.org  Fri Jul 13 19:02:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA25040
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 19:02:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LBYt-000Pbx-00
	for idn-data@psg.com; Fri, 13 Jul 2001 15:37:27 -0700
Received: from ns1.ar.com ([63.194.205.74] helo=mail.ar.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LBYs-000Pbr-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 15:37:26 -0700
Received: from loki (IDENT:wessorh@loki [10.10.10.88])
	by mail.ar.com (8.11.2/8.11.2) with ESMTP id f6DMUxr05101;
	Fri, 13 Jul 2001 15:30:59 -0700
Date: Fri, 13 Jul 2001 15:30:59 -0700 (PDT)
From: Rick H Wesson <wessorh@ar.com>
To: "Brian W. Spolarich" <briansp@walid.com>
cc: Dan Oscarsson <Dan.Oscarsson@trab.se>, <idn@ops.ietf.org>,
        <amc@cs.berkeley.edu>
Subject: RE: [idn] Reality Check
In-Reply-To: <FJEPLIJJEDBNPIOAEIHDAEHBCGAA.briansp@walid.com>
Message-ID: <Pine.LNX.4.30.0107131529360.2775-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


Brian,

I do feel that it is important not to preserve case, furthermore I believe
that it is a major drawback of the DUDE draft that it could support
case preservation.

-rick

On Fri, 13 Jul 2001, Brian W. Spolarich wrote:


>   If the WG feels that case preservation in decoding is important, then 1)
> it is not inconsistent with IDNA's architecture and 2) the ACE and NamePrep
> can be modified to support it without adding too much complexity (beyond the
> inherent complexities of case in general).
>
>   -bws
>
>




From owner-idn@ops.ietf.org  Fri Jul 13 20:15:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA04321
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 20:15:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LCXn-00011o-00
	for idn-data@psg.com; Fri, 13 Jul 2001 16:40:23 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LCXm-00011i-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 16:40:22 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15LCXl-0007H8-00; Fri, 13 Jul 2001 16:40:21 -0700
Date: Fri, 13 Jul 2001 23:40:21 +0000
To: IDN <idn@ops.ietf.org>
Subject: Re: [idn] proposals and deadlines
Message-ID: <20010713234021.A27796@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B4F6EF4.560DDE68@ehsco.com> <00ff01c10be7$a07297e0$1001a8c0@neteka.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Edmon <edmon@neteka.com> wrote:

> These in turn (especially ACE leakage) would encourage the
> application/resolver developer to eventually implement EDNS.

You'll have to walk me through the argument, because I just don't get
it.  DNS servers will be motivated to answer ACE queries correctly
because a lot of queries will be in ACE format, at least at the
beginning.  It doesn't matter whether they perform ACE conversion
on-the-fly, or at zone-loading time, or if they rely on administrators
to use preprocessing tools on the zone files, DNS servers will be
motivated to handle ACE queries somehow or other.

Therefore, resolvers and/or clients will have a choice between
attempting to use a DNS extension and falling back to ACE when it fails,
or just always using ACE.  By the previous argument, the latter option
will work anyway, and is easier, so it will probably be used in many
cases.  And that in turn will keep alive the motivation for DNS servers
to handle ACE queries correctly.

I'm not saying the DNS extension is bad, I'm just explaining why I
wouldn't expect it to become ubiquitous quickly.

"Eric A. Hall" <ehall@ehsco.com> wrote:

> a) the resolver doesn't encode anything, it just passes whatever the
> client application passed to it via one of the APIs

Okay, I thought you were saying that if the EDNS query fails, then the
resolver would perform ACE transformations on behalf of the application.
Now I guess you're saying that the resolver would simply return an
error, and the application would try again using the old resolver API
and the ACE transformations.

This just moves my argument up a layer.  Now the application has a
choice between trying the new API and falling back to ACE, or just
always using ACE with the old API.  The latter is simpler and works just
as well (and is more portable).

If you want to entice me to use the new resolver API, you're going to
have to offer more incentive.  Having the resolver perform the ACE
conversions for me would do it.

AMC



From owner-idn@ops.ietf.org  Fri Jul 13 20:20:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA04955
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 20:20:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LC5v-0000Nx-00
	for idn-data@psg.com; Fri, 13 Jul 2001 16:11:35 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15LC5t-0000Ms-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 16:11:34 -0700
Received: (qmail 14706 invoked by uid 1001); 13 Jul 2001 23:11:45 -0000
Date: 13 Jul 2001 23:11:45 -0000
Message-ID: <20010713231145.3583.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
Automatic-Copyright-Notice: Copyright 2001, D. J. Bernstein. My transmission of this message to you does not constitute a copyright waiver or any other limitation of my rights, even if you have told me otherwise.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] Reality Check
References: <200107130844.f6D8itP12233@malmo.trab.se> <FJEPLIJJEDBNPIOAEIHDAEHBCGAA.briansp@walid.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Brian W. Spolarich writes:
> store case information for the decoded name by setting case in the ACE

If lowercase x is ACE-encoded as 75, how is uppercase X encoded?

Are you suggesting that the WG stop considering any encodings for which
there isn't at least one letter in the output per letter in the input?

Please, folks, think through the details of your proposals.

---Dan



From owner-idn@ops.ietf.org  Fri Jul 13 21:49:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA15798
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 21:49:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LDKF-00025t-00
	for idn-data@psg.com; Fri, 13 Jul 2001 17:30:27 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LDKE-00025n-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 17:30:26 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15LDKE-0007MO-00; Fri, 13 Jul 2001 17:30:26 -0700
Date: Sat, 14 Jul 2001 00:30:26 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Reality Check
Message-ID: <20010714003026.B27796@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20010713231145.3583.qmail@cr.yp.to>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

"D. J. Bernstein" <djb@cr.yp.to> wrote:

> Are you suggesting that the WG stop considering any encodings for
> which there isn't at least one letter in the output per letter in the
> input?

A few hours ago the working group stopped considering any encodings
without seven supporters, which I think leaves only DUDE, AMC-ACE-Z,
and maybe MACE (I hope we'll hear an announcement soon).  In each of
these encodings, every input letter is represented by a sequence of
output characters, the last of which is always a letter.  The last
proposal being considered by the ACE design team that didn't have this
property was LACE, which lost support on Jun-05 in favor of DUDE (which
is simpler than LACE, a little less efficient for Han and Hangul, and a
little more efficient for everything else).

It has been discovered that ACEs that use an integral number of output
characters per input character are simpler and need not be less
efficient, and once you're in that regime, it's easy to arrange for the
last character to always be a letter.

AMC



From owner-idn@ops.ietf.org  Fri Jul 13 22:46:44 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA23063
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 22:46:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LFHN-0004xK-00
	for idn-data@psg.com; Fri, 13 Jul 2001 19:35:37 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LFHM-0004xD-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 19:35:36 -0700
Received: from enoshima (g052213.ppp.asahi-net.or.jp [211.132.52.213])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id LAA28102;
	Sat, 14 Jul 2001 11:35:46 +0900 (JST)
Message-Id: <4.2.0.58.J.20010714113411.03996d30@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Sat, 14 Jul 2001 11:35:06 +0900
To: "Eric A. Hall" <ehall@ehsco.com>, "Adam M. Costello" <amc@cs.berkeley.edu>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] proposals and deadlines
Cc: IDN <idn@ops.ietf.org>
In-Reply-To: <3B4FAA3A.F46D463E@ehsco.com>
References: <20010713234021.A27796@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 21:11 01/07/13 -0500, Eric A. Hall wrote:
>You are certainly free to try embedding ACE into your data, displaying it
>properly in all situations, managing clipboard representations of it (did
>they want the visual representation or the mailto link?), educating users
>on its syntax, and so forth. Not having to do any of that should be
>compelling enough.

Very good point. Glad to see that more people see that ACE will
bring us more problems than it will solve.

Regards,   Martin.



From owner-idn@ops.ietf.org  Fri Jul 13 22:53:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA23825
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 22:53:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LF5z-0004fc-00
	for idn-data@psg.com; Fri, 13 Jul 2001 19:23:51 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LF5y-0004fS-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 19:23:50 -0700
Received: from enoshima (g052213.ppp.asahi-net.or.jp [211.132.52.213])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id LAA28073;
	Sat, 14 Jul 2001 11:24:01 +0900 (JST)
Message-Id: <4.2.0.58.J.20010714112155.03aee780@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Sat, 14 Jul 2001 11:23:06 +0900
To: "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] draft about <draft-ietf-idn-uname-01.txt>
In-Reply-To: <20010713205738.F26469@arwen.cs.berkeley.edu>
References: <3B4EE803.81EBD285@twnic.net.tw>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 20:57 01/07/13 +0000, Adam M. Costello wrote:
>It is already permissible (I think) for DNS servers to perform more
>complex matching than the usual case-insensitive ASCII matching.  For
>example, a DNS server implementation could support master file entries
>whose keys are regular expressions, and it could compare incoming
>requests to those patterns.  For example, it could allow:
>
>foo-?(two|2)   A   1.2.3.4

Yes, they could. But how would that work with ACE?
It would be a terrible headache. That's one of ACE's
main problems.

Regards,   Martin.




>to be used as shorthand for:
>
>foo2      A   1.2.3.4
>footwo    A   1.2.3.4
>foo-2     A   1.2.3.4
>foo-two   A   1.2.3.4
>
>Similarly, if a DNS server implementation wants to perform
>simplified/traditional Chinese matching, or matching of names encoded
>in alternate charsets, isn't it already allowed to do so?  Is there any
>need to standardize this?
>
>Note that using such a feature will cause problems at higher layers,
>because clients won't know the matching rules.  For example, if I
>follow a link to www.foo2.net, and later follow a different link to
>www.foo-two.net, the link will not be colored as visited.  If I tell
>my browser to accept cookies from foo2.net, it won't know to also
>accept cookies from foo-two.net.  Same problem with SSL certificates.
>Therefore it would probably be desirable to deal with extended matching
>not only in the DNS server but also at higher layers.  In these
>examples, one might want the HTTP server to redirect requests from the
>alternate server names to a single preferred server name.
>
>AMC




From owner-idn@ops.ietf.org  Fri Jul 13 22:54:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA23952
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 22:54:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LFL7-00054M-00
	for idn-data@psg.com; Fri, 13 Jul 2001 19:39:29 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LFL6-00054D-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 19:39:28 -0700
Received: from enoshima (g052213.ppp.asahi-net.or.jp [211.132.52.213])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id LAA28096;
	Sat, 14 Jul 2001 11:32:04 +0900 (JST)
Message-Id: <4.2.0.58.J.20010714113113.037c3f00@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Sat, 14 Jul 2001 11:31:37 +0900
To: Rick H Wesson <wessorh@ar.com>, "Brian W. Spolarich" <briansp@walid.com>
From: Martin Duerst <duerst@w3.org>
Subject: RE: [idn] Reality Check
Cc: Dan Oscarsson <Dan.Oscarsson@trab.se>, <idn@ops.ietf.org>,
        <amc@cs.berkeley.edu>
In-Reply-To: <Pine.LNX.4.30.0107131529360.2775-100000@loki.ar.com>
References: <FJEPLIJJEDBNPIOAEIHDAEHBCGAA.briansp@walid.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 15:30 01/07/13 -0700, Rick H Wesson wrote:
>I do feel that it is important not to preserve case, furthermore I believe
>that it is a major drawback of the DUDE draft that it could support
>case preservation.

Rick - can you give us a clue why?     Martin.



From owner-idn@ops.ietf.org  Fri Jul 13 22:59:30 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA24442
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 22:59:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LF9A-0004lc-00
	for idn-data@psg.com; Fri, 13 Jul 2001 19:27:08 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LF8v-0004kG-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 19:26:54 -0700
Received: from enoshima (g052213.ppp.asahi-net.or.jp [211.132.52.213])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id LAA28083;
	Sat, 14 Jul 2001 11:27:10 +0900 (JST)
Message-Id: <4.2.0.58.J.20010714112605.03825d50@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Sat, 14 Jul 2001 11:26:44 +0900
To: "Adam M. Costello" <amc@cs.berkeley.edu>, IDN <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] proposals and deadlines
In-Reply-To: <20010713210619.G26469@arwen.cs.berkeley.edu>
References: <3B4E800D.49220A3@ehsco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 21:06 01/07/13 +0000, Adam M. Costello wrote:
>"Eric A. Hall" <ehall@ehsco.com> wrote:
>
> >  3) Resolvers present two separate APIs: one for legacy names, one for
> >     IDNs.

I think this should read: one for legacy names and one for
IDNs (including legacy names).

Regards,   Martin.



From owner-idn@ops.ietf.org  Fri Jul 13 23:04:20 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA24940
	for <idn-archive@lists.ietf.org>; Fri, 13 Jul 2001 23:04:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LEu7-0004OW-00
	for idn-data@psg.com; Fri, 13 Jul 2001 19:11:35 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LEu6-0004O2-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 19:11:34 -0700
Received: from [216.153.32.1] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 161000; Fri, 13 Jul 2001 19:10:59 -0700
Message-ID: <3B4FAA3A.F46D463E@ehsco.com>
Date: Fri, 13 Jul 2001 21:11:06 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Adam M. Costello" <amc@cs.berkeley.edu>
CC: IDN <idn@ops.ietf.org>
Subject: Re: [idn] proposals and deadlines
References: <20010713234021.A27796@arwen.cs.berkeley.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> This just moves my argument up a layer.  Now the application has a
> choice between trying the new API and falling back to ACE, or just
> always using ACE with the old API.  The latter is simpler and works
> just as well (and is more portable).

You avoid transliteration when using UTF8. What you see is what you get,
rather than a codified representation of it. For email messages, text
files, and just about every other form of user-manipulatable storage, this
is extremely important, and will become moreso over time.

Users don't want to write "ask jane@aq--gobbledygook for info". Users
don't want to see it in netstat output. Etc.

> If you want to entice me to use the new resolver API, you're going to
> have to offer more incentive. Having the resolver perform the ACE
> conversions for me would do it.

You are certainly free to try embedding ACE into your data, displaying it
properly in all situations, managing clipboard representations of it (did
they want the visual representation or the mailto link?), educating users
on its syntax, and so forth. Not having to do any of that should be
compelling enough.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Sat Jul 14 00:28:44 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA04381
	for <idn-archive@lists.ietf.org>; Sat, 14 Jul 2001 00:28:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LGjj-0007Cz-00
	for idn-data@psg.com; Fri, 13 Jul 2001 21:08:59 -0700
Received: from mail.fm-net.ne.jp ([211.15.66.133])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LGji-0007Cr-00
	for idn@ops.ietf.org; Fri, 13 Jul 2001 21:08:59 -0700
Received: from bruce (bruce.fm-net.ne.jp [211.15.66.163])
	by mail.fm-net.ne.jp (8.9.3/8.8.7) with SMTP id NAA31420
	for <idn@ops.ietf.org>; Sat, 14 Jul 2001 13:08:57 +0900
Message-ID: <001301c10c1a$9997ccf0$a3420fd3@bruce>
From: "Bruce Thomson" <bthomson@fm-net.ne.jp>
To: <idn@ops.ietf.org>
References: <200107131656.f6DGuiP15809@malmo.trab.se>
Subject: Re: [idn] Summary of support for UDNS
Date: Sat, 14 Jul 2001 13:08:12 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I support UDNS too. Sorry for the late response.

----- Original Message -----
From: "Dan Oscarsson" <Dan.Oscarsson@trab.se>
To: <Marc.Blanchet@viagenie.qc.ca>; <jseng@pobox.org.sg>; <idn@ops.ietf.org>
Cc: <bill@mail.nic.nu>; <edmon@neteka.com>; <magnus@gustavsson.se>;
<duerst@w3.org>; <ehall@ehsco.com>; <djb@cr.yp.to>
Sent: Saturday, July 14, 2001 1:59 AM
Subject: [idn] Summary of support for UDNS


> With it being summer vacation time and the short time to collect
supporters,
> it is not that easy to get responses.
>
> Anyway the following support UDNS (or something based on that):
> Dan Oscarsson (myself)
> "J. William Semich" <bill@mail.nic.nu>
> "Edmon" <edmon@neteka.com>
> C C Magnus Gustavsson <magnus@gustavsson.se>
> Martin Duerst <duerst@w3.org>
> "Eric A. Hall" <ehall@ehsco.com>
>
> That is 6 persons, one less than 7 that is needed to give it "core of
interest".
>
> I would expect "D. J. Bernstein" <djb@cr.yp.to> to support it, but he have
not
> been active lately on the list.
> With all the discussions we have had on the list about UTF-8, I would
expect
> UDNS (which is UTF-8 with ACE for backward compatibility (including IDNA))
> to get the 7 needed, if there had been more time to collect supporters.
>
> It is up to our two co-chairs to decide if this is good enough
> for "core of interest".
>
> Regards,
>
>    Dan
>
>
>
>
>




From owner-idn@ops.ietf.org  Sat Jul 14 07:35:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA03965
	for <idn-archive@lists.ietf.org>; Sat, 14 Jul 2001 07:35:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LLxX-000G18-00
	for idn-data@psg.com; Sat, 14 Jul 2001 02:43:35 -0700
Subject: RE: [idn] Reality Check
From: "Russ Rolfe" <rrolfe@windows.microsoft.com>
To: "Eric A. Hall" <ehall@ehsco.com>, "Keith Moore" <moore@cs.utk.edu>
Cc: <idn@ops.ietf.org>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15LLxX-000G18-00@psg.com>
Date: Sat, 14 Jul 2001 02:43:35 -0700

>> we can't expect people to upgrade their applications en masse. nor=20
>> would this make good operational sense.

> We are expecting them to do it for ACE (so that it is usable anyway).
> We might as well let them move to recent state-of-the-art when they
> do it.

All thou I have been most of the time a silent observer, I agree here
with Eric, and would to like to state the following:

1. Since IDN is a new feature being added to the internet, most people
   will accept the premise that to use a new feature, you will most
   likely need to upgrade to some application or system that=20
   supports the use of this feature.

2. Before the Internet became the default carrier for E-mail, many
   companies had some internal system that allowed electron mail.
   With these E-mail packages people could send e-mail to some=20
   people but not to all the people they wanted.  As the internet
   became more accesses able to companies, people began to=20
   request the ability to send to others out side of their systems.
   A lot of these companies had to install whole new systems in order
   to accommodate this request.  And while doing so, a lot of us had
   to live with two or more E-mail systems to do our work until every
   thing was right.

   I see no difference in this analogy then what we are trying to do
   with the introduction of an IDN standard.  With the introduction
   of a UTF-8 based IDN, those who wish to use it will upgrade
   to the applications and systems that can handle it.  While in
   the process of upgrading, people may not be able to communicate=20
   with everyone they want to via the new feature, but if it is
   important enough, these people will use both IDN and non-IDN
   address until every they need to communicate can, but because
   it is important all parties will upgrade there systems ASAP.

3. I have read a lot of comments on this list that state that ACE
   is just an intermediate step to help us get to a UTF-8 solution.
   IMHO most intermediate steps become long term solutions (for
   example how many of you have seen supposable TEMPORARY taxes =20
   that have actually been repealed -- not very many).

Thus I would suggest that a UTF-8 solution that in the beginning may
cause some a little irritation, will actually help us get to the UTF-8
solution quicker than using ACE as an intermediate step.  For it is
human nature to remove or change that which is uncomfortable first
before addressing things that don't seam to be causing problems.

Regards, Russ Rolfe (rrolfe@microsoft.com)
Microsoft






From owner-idn@ops.ietf.org  Sat Jul 14 07:38:09 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA04248
	for <idn-archive@lists.ietf.org>; Sat, 14 Jul 2001 07:38:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LLxW-000G11-00
	for idn-data@psg.com; Sat, 14 Jul 2001 02:43:34 -0700
From: "tsenglm" <tsenglm@cc.ncu.edu.tw>
To: <idn@ops.ietf.org>, "Adam M. Costello" <amc@cs.berkeley.edu>
Subject: Re: [idn] draft about <draft-ietf-idn-uname-01.txt>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15LLxW-000G11-00@psg.com>
Date: Sat, 14 Jul 2001 02:43:34 -0700

       Thanks for your comment ,  I  try to give some explanation  in
the
following.
----- Original Message -----
From: "Adam M. Costello" <amc@cs.berkeley.edu>
To: <idn@ops.ietf.org>
Sent: Saturday, July 14, 2001 4:57 AM
Subject: Re: [idn] draft about <draft-ietf-idn-uname-01.txt>


> It is already permissible (I think) for DNS servers to perform more
> complex matching than the usual case-insensitive ASCII matching.  For
> example, a DNS server implementation could support master file entries
> whose keys are regular expressions, and it could compare incoming
> requests to those patterns.  For example, it could allow:
>
> foo-?(two|2)   A   1.2.3.4
>
> to be used as shorthand for:
>
> foo2      A   1.2.3.4
> footwo    A   1.2.3.4
> foo-2     A   1.2.3.4
> foo-two   A   1.2.3.4
      This is a very good representation for  OR operation on some set
of
equivalence meanning words(characters).
But it can be solved in nameprep by character normalization ,  because
CJK
character is  UCS-2 in 2 byte
form , so it is a  case of  normalization  to a set of  equivalent
byte-length characters. The  1-1 mapping  of equivalence meanning  words
is
the simplest case.  Uname draft treat another case of  chinese
character(words),
especially in  one to many(include none) & many to one mapping  ,  The
meanning is equivalent or not  is highly dependent on the context
sequence ,
these are not the case of  1-1 mapping & equivalence .
      To simplify the SC/TC  translation ,  one to many(include none)
mapping are  freely selected  one by register in registratin stage ,  so
they need a record to guide the resoving of  partial-different
character-string-name map to only one unique identifier .
>
> Similarly, if a DNS server implementation wants to perform
> simplified/traditional Chinese matching, or matching of names encoded
> in alternate charsets, isn't it already allowed to do so?  Is there
any
> need to standardize this?
>
> Note that using such a feature will cause problems at higher layers,
> because clients won't know the matching rules.  For example, if I
> follow a link to www.foo2.net, and later follow a different link to
> www.foo-two.net, the link will not be colored as visited.  If I tell
> my browser to accept cookies from foo2.net, it won't know to also
> accept cookies from foo-two.net.  Same problem with SSL certificates.
          You just describe the problem why  the authorized unique-root
based ML-DNS server is needed . Based on the DNS tree server ,
www.foo2.net
www.foo-two.net  will be " replaced "  by the same  ACE
unique-name/identifier in resoving processing if they are mapped to the
same
ACE identifier.
> Therefore it would probably be desirable to deal with extended
matching
> not only in the DNS server but also at higher layers.  In these
> examples, one might want the HTTP server to redirect requests from the
> alternate server names to a single preferred server name.
>
> AMC
>
         The  TC/SC translation automatically occurs in  browser and
mail
agent,  but they translate it based on  ISO-10646 code font ,  A  TC
viewer
may get many ???  reading in SC content especially in receiver , subject
and
URL input field of  browser.  It is not just for not displayable ,  the
information in these field for identification is lost in cross TC/SC
visiting  or  mail reply ,  So a  mapping record is needed to help
mailing
system and browser to prevent the confusing in critical Domain Name
field is
very important.

Li-Ming Tseng






From owner-idn@ops.ietf.org  Sat Jul 14 17:34:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA08055
	for <idn-archive@lists.ietf.org>; Sat, 14 Jul 2001 17:34:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LWNO-00058m-00
	for idn-data@psg.com; Sat, 14 Jul 2001 13:50:58 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LWNN-00058g-00
	for idn@ops.ietf.org; Sat, 14 Jul 2001 13:50:57 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15LWNN-0008Fc-00; Sat, 14 Jul 2001 13:50:57 -0700
Date: Sat, 14 Jul 2001 20:50:57 +0000
To: IDN <idn@ops.ietf.org>
Subject: Re: [idn] proposals and deadlines
Message-ID: <20010714205056.C31484@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B4FAA3A.F46D463E@ehsco.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

"Eric A. Hall" <ehall@ehsco.com> wrote:

> Users don't want to write "ask jane@aq--gobbledygook for info". Users
> don't want to see it in netstat output. Etc.
>
> > If you want to entice me to use the new resolver API, you're going
> > to have to offer more incentive. Having the resolver perform the ACE
> > conversions for me would do it.
>
> You are certainly free to try embedding ACE into your data, displaying
> it properly in all situations, managing clipboard representations of
> it (did they want the visual representation or the mailto link?),
> educating users on its syntax, and so forth. Not having to do any of
> that should be compelling enough.

I must have completely failed to make my argument understood, because
your response is unrelated to the point I was trying to make.  Let me
try again.

You said that in your proposed architecture, if the EDNS/UTF-8
lookup fails, then there is a fallback to DNS/ACE (at least in some
situations).  At first, I assumed that the fallback would happen inside
the resolver, but then you said it wouldn't, so that means the fallback
must happen inside the application, right?  In other words, you expect
these applications to include code that looks like this:

    start with a UTF-8 query
    look up using newAPI
    if that failed then begin
      ACE-encode the query
      look up using oldAPI
      ACE-decode the response
    end
    finish with a UTF-8 response

But they could instead use code that looks like this:

    start with a UTF-8 query
    ACE-encode the query
    look up using oldAPI
    ACE-decode the response
    finish with a UTF-8 response

The latter starts and ends with UTF-8 just like the former, but
is smaller and simpler.  You were recommending a fallback to be
used sometimes by some applications, and my point is that for those
applications it's easier to just use the "fallback" all the time.

If you want to help these applications to forget about ACE, you can do
that by hiding the fallback mechanism inside the resolver.  Then the
application can simply do:

    start with a UTF-8 query
    look up using newAPI
    finish with a UTF-8 response

AMC



From owner-idn@ops.ietf.org  Sat Jul 14 17:56:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA10338
	for <idn-archive@lists.ietf.org>; Sat, 14 Jul 2001 17:56:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LWnp-0005nc-00
	for idn-data@psg.com; Sat, 14 Jul 2001 14:18:17 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LWnp-0005nW-00
	for idn@ops.ietf.org; Sat, 14 Jul 2001 14:18:17 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15LWno-0008H9-00; Sat, 14 Jul 2001 14:18:16 -0700
Date: Sat, 14 Jul 2001 21:18:16 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Reality Check
Message-ID: <20010714211816.D31484@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E15LLxX-000G18-00@psg.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Russ Rolfe <rrolfe@windows.microsoft.com> wrote:

> ...people will use both IDN and non-IDN address until every they need
> to communicate can...

Are you arguing that ACE is unnecessary?  If so, please explain how
email is going to work.  What is supposed to happen when IDN-capable
person A sends a message to IDN-capable person B, who then forwards the
message to IDN-incapable person C, who would like to reply to A?  What
is supposed to happen when IDN-capable people send email to mailing
lists?  Are they supposed to use their non-IDN address if there are any
IDN-incapable subscribers?  How will they know?

> I have read a lot of comments on this list that state that ACE is just
> an intermediate step to help us get to a UTF-8 solution.

I don't agree with those comments.  While I can see ACE becoming less
common over time, I wouldn't expect it to completely die out in the
forseeable future.

AMC



From owner-idn@ops.ietf.org  Sat Jul 14 18:37:23 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA14407
	for <idn-archive@lists.ietf.org>; Sat, 14 Jul 2001 18:37:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LXB9-0006PS-00
	for idn-data@psg.com; Sat, 14 Jul 2001 14:42:23 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LXB8-0006PM-00
	for idn@ops.ietf.org; Sat, 14 Jul 2001 14:42:23 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15LXB8-0008J7-00; Sat, 14 Jul 2001 14:42:22 -0700
Date: Sat, 14 Jul 2001 21:42:22 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] draft about <draft-ietf-idn-uname-01.txt>
Message-ID: <20010714214222.E31484@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E15LLxW-000G11-00@psg.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

tsenglm <tsenglm@cc.ncu.edu.tw> wrote:

> Based on the DNS tree server, www.foo2.net www.foo-two.net will
> be "replaced " by the same ACE unique-name/identifier in resoving
> processing if they are mapped to the same ACE identifier.

You mean replaced in the application layer, so that, for example, the
browser knows that foo2.net and foo-two.net are the same?  For that to
happen, the resolver interface must be changed.  Right now, even if
foo.com and bar.com are both CNAME records for webhost.com, the browser
will not treat foo.com and bar.com as the same, which is good, because
webhost.com is probably using virtual hosting, so that foo.com and
bar.com really are logically separate sites.  If you want foo2.com and
foo-two.com to be considered the same by the browser, you need some
other relationship connecting them, not the alias (CNAME) relationship.
Even if you introduce a new resource record type (UNAME), the existing
resolver interface has no way of expressing any connection between
names other than the alias relationship, so you'd need a new resolver
interface.  Or you could inform the browser of the name equivalence at a
higher layer, for example using HTTP redirects.

AMC



From owner-idn@ops.ietf.org  Sun Jul 15 00:40:28 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA23375
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 00:40:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LdAb-000GSs-00
	for idn-data@psg.com; Sat, 14 Jul 2001 21:06:13 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LdAS-000GSX-00
	for idn@ops.ietf.org; Sat, 14 Jul 2001 21:06:05 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6F45mD14478;
	Sun, 15 Jul 2001 13:05:49 +0900 (KST)
Message-ID: <031001c10ce4$2d906880$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <20010714211816.D31484@arwen.cs.berkeley.edu> <4.2.0.58.J.20010715125225.00a00dc0@sh.w3.mag.keio.ac.jp>
Subject: Re: [idn] IDN security and ACE leakage
Date: Sun, 15 Jul 2001 13:11:09 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

DUDE and AMC-ACE-Z (not RACE,ACE37) already  avoid 
using '0', 'o', '1', 'l'  in its base 32 encoding 
for security reasons. It is a nice feature. 
 
----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
Sent: Sunday, July 15, 2001 12:54 PM
Subject: Re: [idn] IDN security and ACE leakage


> 'l' and '1' and 'I' ('ell' and 'one' and 'upper-case i') are
> almost indistinguishable. For security reasons, DNS-capable email
> programs (i.e. every email program) may display an email
> address using hexadecimal (ACE won't work).
> 
> How many programs actually do this?
> 
> Regards,   Martin.
> 
> At 12:16 01/07/15 +0900, Soobok Lee wrote:
> >Latin 'o' and Greek 'o'  are almost indistinguishable ,
> >(and I can list up hundreds of such examples.)
> >but their ACE labels  often look very different.
> >
> >For security reasons, IDN-capable email programs
> >may display an IDN email address
> >  both in its original scripts and in its ACEed form
> >  to encourage  instant verification  like this:
> >"FullName <i18n-mbox@i18n-hostname.com>" [qq--xxx@bq--yyy.com]
> >
> >It's more secure but looks ugly. shorter ACE labels may help.
> >ACE labels are better than appended hexadecimal dump of utf8 lables
> >for this purpose.
> >
> >Soobok Lee
> 




From owner-idn@ops.ietf.org  Sun Jul 15 00:41:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA23483
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 00:41:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Lczx-000G7y-00
	for idn-data@psg.com; Sat, 14 Jul 2001 20:55:13 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Lczw-000G7s-00
	for idn@ops.ietf.org; Sat, 14 Jul 2001 20:55:12 -0700
Received: from enoshima (i205225.ppp.asahi-net.or.jp [61.125.205.225])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id MAA00276;
	Sun, 15 Jul 2001 12:55:10 +0900 (JST)
Message-Id: <4.2.0.58.J.20010715125225.00a00dc0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Sun, 15 Jul 2001 12:54:46 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] IDN security and ACE leakage
In-Reply-To: <02fd01c10cdc$938219c0$ed1bd9d2@postel.co.kr>
References: <20010714211816.D31484@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

'l' and '1' and 'I' ('ell' and 'one' and 'upper-case i') are
almost indistinguishable. For security reasons, DNS-capable email
programs (i.e. every email program) may display an email
address using hexadecimal (ACE won't work).

How many programs actually do this?

Regards,   Martin.

At 12:16 01/07/15 +0900, Soobok Lee wrote:
>Latin 'o' and Greek 'o'  are almost indistinguishable ,
>(and I can list up hundreds of such examples.)
>but their ACE labels  often look very different.
>
>For security reasons, IDN-capable email programs
>may display an IDN email address
>  both in its original scripts and in its ACEed form
>  to encourage  instant verification  like this:
>"FullName <i18n-mbox@i18n-hostname.com>" [qq--xxx@bq--yyy.com]
>
>It's more secure but looks ugly. shorter ACE labels may help.
>ACE labels are better than appended hexadecimal dump of utf8 lables
>for this purpose.
>
>Soobok Lee




From owner-idn@ops.ietf.org  Sun Jul 15 00:41:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA23547
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 00:41:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LanQ-000C9z-00
	for idn-data@psg.com; Sat, 14 Jul 2001 18:34:08 -0700
From: "tsenglm" <tsenglm@cc.ncu.edu.tw>
To: <idn@ops.ietf.org>, "Adam M. Costello" <amc@cs.berkeley.edu>
References: <20010714214222.E31484@arwen.cs.berkeley.edu>
Subject: Re: [idn] draft about <draft-ietf-idn-uname-01.txt>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15LanQ-000C9z-00@psg.com>
Date: Sat, 14 Jul 2001 18:34:08 -0700

----- Original Message -----
From: "Adam M. Costello" <amc@cs.berkeley.edu>
To: <idn@ops.ietf.org>
Sent: Sunday, July 15, 2001 5:42 AM
Subject: Re: [idn] draft about <draft-ietf-idn-uname-01.txt>


> tsenglm <tsenglm@cc.ncu.edu.tw> wrote:
>
> > Based on the DNS tree server, www.foo2.net www.foo-two.net will
> > be "replaced " by the same ACE unique-name/identifier in resoving
> > processing if they are mapped to the same ACE identifier.
>
> You mean replaced in the application layer, so that, for example, the
> browser knows that foo2.net and foo-two.net are the same?  For that to
> happen, the resolver interface must be changed.  Right now, even if
> foo.com and bar.com are both CNAME records for webhost.com, the
browser
> will not treat foo.com and bar.com as the same, which is good, because
> webhost.com is probably using virtual hosting, so that foo.com and
> bar.com really are logically separate sites.  If you want foo2.com and
> foo-two.com to be considered the same by the browser, you need some
> other relationship connecting them, not the alias (CNAME)
relationship.
> Even if you introduce a new resource record type (UNAME), the existing
> resolver interface has no way of expressing any connection between
> names other than the alias relationship, so you'd need a new resolver
> interface.  Or you could inform the browser of the name equivalence at
a
> higher layer, for example using HTTP redirects.
            IDN Name "replaced" by the idenetifier  is a necessary
effort
for backward compatibility.  For  cross visiting  of  different TC/SC
nodes,  the ACE identifier "replacement" can be used to help them
without
confusing in TC/SC translation.  DNS  UNAME records  are used to
indicate
that these IDN names are mapped to the same identifier .  How the
Application software (for ex. the browser) can kown it ?  There are many
different ways to implement it:
            1. The IDN-aware AP can recognize and do the right
interpretation.
            2. A pre-processing module between user input module and
Application . This preprocessing module query ML-DNS  with IDN and put
correct ACE identifier to IDN-unaware-AP. For forward compatibility, an
gateway to treat ACE identifier for  IDN-only  node may be required.
            3. A  browser user interface that uses HTTP protocol to
query
ML-DNS with  IDN and native-lang tag as parameter ,  the user interface
can
start up any  AP and put it with  correct  unique-name/identifier.

>
> AMC
>
            Thanks your comment, You get  all points.
            More precisely,  we treat the same meaning of characters as
one
way mapping to the same identifier.
The reverse mapping may be true or false in reverse way, so I do not
call
them  equivalence.

Li-Ming Tseng






From owner-idn@ops.ietf.org  Sun Jul 15 00:43:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA23745
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 00:43:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LdRk-000Gzc-00
	for idn-data@psg.com; Sat, 14 Jul 2001 21:23:56 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LdRj-000GzW-00
	for idn@ops.ietf.org; Sat, 14 Jul 2001 21:23:55 -0700
Received: from [216.153.32.88] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 161044; Sat, 14 Jul 2001 21:23:17 -0700
Message-ID: <3B511ABB.8EE1C2ED@ehsco.com>
Date: Sat, 14 Jul 2001 23:23:23 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Adam M. Costello" <amc@cs.berkeley.edu>
CC: IDN <idn@ops.ietf.org>
Subject: Re: [idn] proposals and deadlines
References: <20010714205056.C31484@arwen.cs.berkeley.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> You said that in your proposed architecture, if the EDNS/UTF-8
> lookup fails, then there is a fallback to DNS/ACE (at least in some
> situations).  At first, I assumed that the fallback would happen inside
> the resolver, but then you said it wouldn't, so that means the fallback
> must happen inside the application, right?

It has to, since each application (or more accurately, each usage) will
have its own behavioral considerations.

For example, a mail client may allow users to specify the SMTP and POP3
servers by using UTF8 IDNs. This doesn't affect the protocol operations,
but instead only affects the lookup of the server's IP address. A fallback
to ACE can be expected for this lookup operation, but this doesn't affect
the protocol, and the resulting ACE IDN would not need to be rendered by
the client anywhere.

Conversely, the same mailer may keep an address book containing UTF8 IDNs.
Without some sort of extension to SMTP, those addresses will have to be
converted to ACE whenever they are written into the envelope or whenever
they are written into the message headers. If a UTF8-envelope extension
mechanism is created, but it fails to negotiate, then presumably LDH rules
will still apply, so conversion will have to take place in the
applicaiton. In this example, the option negotiation has failed, but no
lookups have failed.

Assuming that the option negotiation succeeds, the SMTP server will
eventually need to log the connection for a Received header. Obviously it
speaks UTF8 if the option was successfully negotiated, so it could try to
use UTF8 for the PTR lookup, although the default behavior should be to
use LDH (ACE), using the legacy API calls. We can also assume that if the
EDNS PTR lookup fails, then it would have to fallback to ACE.

Once mail arrives, the recipient system may need to convert UTF8 envelopes
back to ACE, or if the local message routing maps are using UTF8 IDNs,
vice versa.

That is four conversion scenarios: 

   o A RR lookup failure
   o extended-envelope-option negotiation failure
   o PTR RR lookup failure
   o message routing lookup

As can be seen from the above, each usage will need its own rules, only
two of which use DNS, and two of them have to be defined by an external
protocol (UTF8 in Received headers). As such, the applications have to
manage the conversion process.

> In other words, you expect these applications to include code that
> looks like this:
> 
>     start with a UTF-8 query
>     look up using newAPI
>     if that failed then begin
>       ACE-encode the query
>       look up using oldAPI
>       ACE-decode the response
>     end
>     finish with a UTF-8 response

No, I am thinking:

      start with a UTF-8 query
      look up using newAPI
      if that failed then do whatever they are supposed to do next

> But they could instead use code that looks like this:
> 
>     start with a UTF-8 query
>     ACE-encode the query
>     look up using oldAPI
>     ACE-decode the response
>     finish with a UTF-8 response
> 
> The latter starts and ends with UTF-8 just like the former, but
> is smaller and simpler.  You were recommending a fallback to be
> used sometimes by some applications, and my point is that for those
> applications it's easier to just use the "fallback" all the time.

I think this is a really creative idea, but as illustrated, the onus of
conversion is on the applications and their protocols just as much as it
is on DNS. Even though we could do this for the DNS parts, the
applications will still have to perform conversions. This would be
somewhat easier on the server infrastructure, but it wouldn't save the
applications any labor, and would simply move the server's burden to the
resolver's side of the fence.

There is also a technical consideration here, in that this approach does
not provide a way to distinguish between spurious 8bit data and IDNs. An
older application that encounters an 8bit domain name may pass it into the
stream when it shouldn't (there is at least one application out there now
that passes UTF8 into the DNS). With the dual-message model, at least we
can tell that this is an old client and the malformed data can be compared
to LDH and rejected, while EDNS messages should only be coming from
modernized applications that (hopefully) follow the normalization rules.
This flag is required for Internet stability, IMO.

More importantly (to me anyway), this approach does not provide a
migration path to a UTF8-aware DNS infrastructure. We would still have to
store the raw zone data in ACE format, we would have to invent ACE
editors, we would have to educate the administrative masses on ACE
encoding syntax, and there would be less impetus to move to UTF8
end-to-end in higher-layer protocols. We should be helping to make the
network truly internationalized with this work, IMHO.

> If you want to help these applications to forget about ACE, you can do
> that by hiding the fallback mechanism inside the resolver.  Then the
> application can simply do:
> 
>     start with a UTF-8 query
>     look up using newAPI
>     finish with a UTF-8 response

The unique message is the flag; the API just provides a separate access
point for the message.

> AMC

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Sun Jul 15 00:44:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA23783
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 00:44:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LdV4-000H18-00
	for idn-data@psg.com; Sat, 14 Jul 2001 21:27:22 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LdUz-000H0q-00
	for idn@ops.ietf.org; Sat, 14 Jul 2001 21:27:18 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6F4PcD15950;
	Sun, 15 Jul 2001 13:25:38 +0900 (KST)
Message-ID: <031c01c10ce6$f1c95700$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Martin Duerst" <duerst@w3.org>, <idn@ops.ietf.org>
References: <20010714211816.D31484@arwen.cs.berkeley.edu> <4.2.0.58.J.20010715125225.00a00dc0@sh.w3.mag.keio.ac.jp>
Subject: Re: [idn] IDN security and ACE leakage
Date: Sun, 15 Jul 2001 13:30:57 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

For 1 and 'l', choosing a good latin display font set is enough.
and the ambiguity is well known.

But, In IDN context, we have hundreds or more of such ambiguities 
that are too many to educate.

How can we distinguish  katakana 'ro-to.com' and hangul 'ma.com' 
if we haven't learn japanese and korean ?

----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
Sent: Sunday, July 15, 2001 12:54 PM
Subject: Re: [idn] IDN security and ACE leakage


> 'l' and '1' and 'I' ('ell' and 'one' and 'upper-case i') are
> almost indistinguishable. For security reasons, DNS-capable email
> programs (i.e. every email program) may display an email
> address using hexadecimal (ACE won't work).
> 
> How many programs actually do this?
> 
> Regards,   Martin.
> 
> At 12:16 01/07/15 +0900, Soobok Lee wrote:
> >Latin 'o' and Greek 'o'  are almost indistinguishable ,
> >(and I can list up hundreds of such examples.)
> >but their ACE labels  often look very different.
> >
> >For security reasons, IDN-capable email programs
> >may display an IDN email address
> >  both in its original scripts and in its ACEed form
> >  to encourage  instant verification  like this:
> >"FullName <i18n-mbox@i18n-hostname.com>" [qq--xxx@bq--yyy.com]
> >
> >It's more secure but looks ugly. shorter ACE labels may help.
> >ACE labels are better than appended hexadecimal dump of utf8 lables
> >for this purpose.
> >
> >Soobok Lee
> 




From owner-idn@ops.ietf.org  Sun Jul 15 00:46:02 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA24006
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 00:46:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LafR-000BxH-00
	for idn-data@psg.com; Sat, 14 Jul 2001 18:25:53 -0700
From: John C Klensin <klensin@research.att.com>
To: Russ Rolfe <rrolfe@windows.microsoft.com>
Cc: idn@ops.ietf.org
Subject: RE: [idn] Reality Check
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15LafR-000BxH-00@psg.com>
Date: Sat, 14 Jul 2001 18:25:53 -0700

--On Saturday, 14 July, 2001 02:43 -0700 Russ Rolfe
<rrolfe@windows.microsoft.com> wrote:

> All thou I have been most of the time a silent observer, I
> agree here with Eric, and would to like to state the following:
> 
> 1. Since IDN is a new feature being added to the internet, most
> people    will accept the premise that to use a new feature,
> you will most    likely need to upgrade to some application or
> system that=20    supports the use of this feature.
> 
> 2. Before the Internet became the default carrier for E-mail,
> many    companies had some internal system that allowed
> electron mail.    With these E-mail packages people could send
> e-mail to some=20    people but not to all the people they
> wanted.  As the internet    became more accesses able to
> companies, people began to=20    request the ability to send to
>...

Russ,

It seems to me that your argument, with a very slight recasting
or none at all, would make at least as strong as case for one of
the major, "solve more of the problem" approaches -- search
systems and new DNS Class included-- than for embedding UTF-8 in
the existing, Class=IN DNS.  

To pick up on one part of your example, the companies that
managed to upgrade their mail systems to provide Internet gateway
capability did not put any of their existing uses at significant
risk, since the gateway should have been a clear add-on (this
was, of course, not the case with some software whose developers/
vendors took the upgrade process as an opportunity to introduce
other significant changes and a full complement of new bugs, but
that is a separate matter or should be).

Just an observation...

    john







From owner-idn@ops.ietf.org  Sun Jul 15 00:46:23 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA24049
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 00:46:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LcxE-000G3v-00
	for idn-data@psg.com; Sat, 14 Jul 2001 20:52:24 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LcxD-000G3o-00
	for idn@ops.ietf.org; Sat, 14 Jul 2001 20:52:23 -0700
Received: from enoshima (i205225.ppp.asahi-net.or.jp [61.125.205.225])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id MAA00263;
	Sun, 15 Jul 2001 12:52:33 +0900 (JST)
Message-Id: <4.2.0.58.J.20010715124450.03e38ac0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Sun, 15 Jul 2001 12:51:48 +0900
To: "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Reality Check
In-Reply-To: <20010714211816.D31484@arwen.cs.berkeley.edu>
References: <E15LLxX-000G18-00@psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 21:18 01/07/14 +0000, Adam M. Costello wrote:

>Are you arguing that ACE is unnecessary?  If so, please explain how
>email is going to work.  What is supposed to happen when IDN-capable
>person A sends a message to IDN-capable person B, who then forwards the
>message to IDN-incapable person C, who would like to reply to A?  What
>is supposed to happen when IDN-capable people send email to mailing
>lists?  Are they supposed to use their non-IDN address if there are any
>IDN-incapable subscribers?  How will they know?

Assuming that the sender has some clue about how the address will
show up at the other end, no sender will want ACE to show up.
If mail systems don't get some functionality that will automatically
only use the ACE address if the other systems can display the actual
characters, ACE will get very bad press. So there is no real argument
here to favor ACE over UTF-8.

Regards,   Martin.




From owner-idn@ops.ietf.org  Sun Jul 15 00:48:06 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA24231
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 00:48:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LcK6-000EuV-00
	for idn-data@psg.com; Sat, 14 Jul 2001 20:11:58 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LcJu-000Esr-00
	for idn@ops.ietf.org; Sat, 14 Jul 2001 20:11:46 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6F3BLD10028
	for <idn@ops.ietf.org>; Sun, 15 Jul 2001 12:11:21 +0900 (KST)
Message-ID: <02fd01c10cdc$938219c0$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
References: <20010714211816.D31484@arwen.cs.berkeley.edu>
Subject: [idn] IDN security and ACE leakage
Date: Sun, 15 Jul 2001 12:16:43 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Latin 'o' and Greek 'o'  are almost indistinguishable ,
(and I can list up hundreds of such examples.)
but their ACE labels  often look very different.
  
For security reasons, IDN-capable email programs
may display an IDN email address 
 both in its original scripts and in its ACEed form
 to encourage  instant verification  like this:
"FullName <i18n-mbox@i18n-hostname.com>" [qq--xxx@bq--yyy.com]

It's more secure but looks ugly. shorter ACE labels may help.
ACE labels are better than appended hexadecimal dump of utf8 lables
for this purpose.

Soobok Lee


----- Original Message ----- 
From: "Adam M. Costello" <amc@cs.berkeley.edu>
To: <idn@ops.ietf.org>
Sent: Sunday, July 15, 2001 6:18 AM
Subject: Re: [idn] Reality Check


> Russ Rolfe <rrolfe@windows.microsoft.com> wrote:
> 
> > ...people will use both IDN and non-IDN address until every they need
> > to communicate can...
> 
> Are you arguing that ACE is unnecessary?  If so, please explain how
> email is going to work.  What is supposed to happen when IDN-capable
> person A sends a message to IDN-capable person B, who then forwards the
> message to IDN-incapable person C, who would like to reply to A?  What
> is supposed to happen when IDN-capable people send email to mailing
> lists?  Are they supposed to use their non-IDN address if there are any
> IDN-incapable subscribers?  How will they know?
> 
> > I have read a lot of comments on this list that state that ACE is just
> > an intermediate step to help us get to a UTF-8 solution.
> 
> I don't agree with those comments.  While I can see ACE becoming less
> common over time, I wouldn't expect it to completely die out in the
> forseeable future.
> 
> AMC
> 




From owner-idn@ops.ietf.org  Sun Jul 15 00:48:20 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA24272
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 00:48:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LciU-000Faw-00
	for idn-data@psg.com; Sat, 14 Jul 2001 20:37:10 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LciT-000Fak-00
	for idn@ops.ietf.org; Sat, 14 Jul 2001 20:37:09 -0700
Received: from enoshima (i205225.ppp.asahi-net.or.jp [61.125.205.225])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id MAA00200;
	Sun, 15 Jul 2001 12:36:44 +0900 (JST)
Message-Id: <4.2.0.58.J.20010715121729.03dffed0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Sun, 15 Jul 2001 12:36:12 +0900
To: John C Klensin <klensin@research.att.com>,
        Russ Rolfe <rrolfe@windows.microsoft.com>
From: Martin Duerst <duerst@w3.org>
Subject: RE: [idn] Reality Check
Cc: idn@ops.ietf.org
In-Reply-To: <E15LafR-000BxH-00@psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 18:25 01/07/14 -0700, John C Klensin wrote:

>It seems to me that your argument, with a very slight recasting
>or none at all, would make at least as strong as case for one of
>the major, "solve more of the problem" approaches -- search
>systems

Yes indeed, except that we know quite well how to build and
run the DNS (including where we have to be careful,...),
whereas we don't really have any experience at all of how
to build an Internet-wide reference search system. It may
be that somebody comes up with some great idea tomorrow,
and such a system will fully exist in a year, but it also
may be that we never get there.

Another point is that search systems don't provide the same
as the DNS, namely lookup. There is no guarantee that you
get to the right place (or nowhere) directly. So 'solving more
of the problem' may cut off some of the problem space.


>and new DNS Class included-- than for embedding UTF-8 in
>the existing, Class=IN DNS.

A new class is one of the many (unfortunately too many) options
to upgrade DNS to UTF-8, on one end of the spectrum, whereas
'just send UTF-8' is on the other end.



>To pick up on one part of your example, the companies that
>managed to upgrade their mail systems to provide Internet gateway
>capability did not put any of their existing uses at significant
>risk,

Using UTF-8 is a clear add-on, isn't it? Where is the significant
risk? With 'just send UTF-8', there is the risk that a DNS server
blows up, or returns something else e.g. because it folds the most
significant bit in each byte to 0. But both of these behaviors
are clearly against the DNS specs. If a server blows up, it was
a risk 10 years ago already (if it existed then).
And 'any of their existing uses' is definitely NOT put at risk.
NONE of the UTF-8 proposals is putting at risk the resolution
of ASCII-only domain names.


Just a few observations,      Martin.



From owner-idn@ops.ietf.org  Sun Jul 15 02:29:00 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA20403
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 02:28:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Lews-000Ji9-00
	for idn-data@psg.com; Sat, 14 Jul 2001 23:00:10 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Lews-000Ji3-00
	for idn@ops.ietf.org; Sat, 14 Jul 2001 23:00:10 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15Lewr-0000bT-00; Sat, 14 Jul 2001 23:00:09 -0700
Date: Sun, 15 Jul 2001 06:00:09 +0000
To: IDN <idn@ops.ietf.org>
Subject: Re: [idn] proposals and deadlines
Message-ID: <20010715060009.A2136@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B511ABB.8EE1C2ED@ehsco.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

"Eric A. Hall" <ehall@ehsco.com> wrote:

> Even though we could do this [put ACE conversions in the resolver]
> for the DNS parts, the applications will still have to perform
> conversions.

Are you resigned to have applications contain ACE conversion code
forever?  If so, why should it bother you if DNS likewise uses ACE
forever?  On the other hand, if you'd like to see applications evolve
away from ACE (by upgrading old protocol formats, or replacing old
protocols by new protocols), then you need to give them a way to avoid
ACE in DNS lookups too, and that means giving them a UTF-8 resolver
interface that makes a best effort, not one that gives up too easily and
expects the application to do the fallback to ACE.

> This would be somewhat easier on the server infrastructure, but it
> wouldn't save the applications any labor...

Yes it would.  There will definitely be some applications that want a
UTF-8 response to a UTF-8 query.  If newAPI tries EDNS/UTF-8 and gives
up on failure, then these applications can do their lookup in either of
two ways:

    look up using newAPI
    if that failed then begin
      ACE-encode query
      look up using oldAPI
      ACE-decode response
    end

or:

    ACE-encode query
    look up using oldAPI
    ACE-decode response

The latter is less code to write and maintain.  I can't see a reason
why any programmer would opt for the more complex method given those
two choices.  I also can't think of any scenario where an EDNS/UTF-8
lookup failure should not be followed by an attempt with DNS/ACE.  Which
means I can't think of a single scenario where a programmer would want
to use newAPI at all.  That's my point.  I don't see an incentive for a
programmer to call newAPI if newAPI only makes a half-hearted attempt.
If it makes a best-effort attempt, then it becomes attractive.

> this approach does not provide a migration path to a UTF8-aware DNS
> infrastructure.  We would still have to store the raw zone data in ACE
> format, we would have to invent ACE editors, we would have to educate
> the administrative masses on ACE encoding syntax, and there would be
> less impetus to move to UTF8 end-to-end in higher-layer protocols.

Zone files can be stored in the local charset, or UTF-8, and the DNS
server can do ACE encoding when it starts up and reads the file.  No
need for ACE editors, or for administrators to even see ACE.

If the UTF-8 resolver interface is best-effort, then there is greater
impetus to move to UTF-8 in higher layers, not less, because then
applications can be completely free of ACE.  If the resolver interface
is half-hearted, then applications will always have to do their own
fallback, and will therefore never be free of ACE, so why should they
bother migrating the upper layers away from ACE?

> There is also a technical consideration here, in that this approach
> does not provide a way to distinguish between spurious 8bit data and
> IDNs.  An older application that encounters an 8bit domain name may
> pass it into the stream when it shouldn't (there is at least one
> application out there now that passes UTF8 into the DNS).  With the
> dual-message model, at least we can tell that this is an old client
> and the malformed data can be compared to LDH and rejected, while
> EDNS messages should only be coming from modernized applications that
> (hopefully) follow the normalization rules.

I don't see how this conflicts with anything I've proposed.  I have not
proposed putting 8-bit data into old-style DNS messages.

AMC



From owner-idn@ops.ietf.org  Sun Jul 15 02:30:04 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA20555
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 02:30:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LevZ-000Jeg-00
	for idn-data@psg.com; Sat, 14 Jul 2001 22:58:49 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LevN-000JeS-00
	for idn@ops.ietf.org; Sat, 14 Jul 2001 22:58:38 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6F5vQD23279;
	Sun, 15 Jul 2001 14:57:26 +0900 (KST)
Message-ID: <033d01c10cf3$c396a2e0$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
Subject: Re: [idn] IDN security and ACE leakage
Date: Sun, 15 Jul 2001 15:02:43 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

some corrections.
AMC-ACE-Z  uses "base36" encoding which includes '0' '1' 'l' 'o'.
It is the DUDE and AMC-ACE-W that avoid  using the four.

----- Original Message ----- 
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>; "Martin Duerst" <duerst@w3.org>
Sent: Sunday, July 15, 2001 1:11 PM
Subject: Re: [idn] IDN security and ACE leakage


> DUDE and AMC-ACE-Z (not RACE,ACE37) already  avoid 
> using '0', 'o', '1', 'l'  in its base 32 encoding 
> for security reasons. It is a nice feature. 
>  
> ----- Original Message ----- 
> From: "Martin Duerst" <duerst@w3.org>
> To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
> Sent: Sunday, July 15, 2001 12:54 PM
> Subject: Re: [idn] IDN security and ACE leakage
> 
> 
> > 'l' and '1' and 'I' ('ell' and 'one' and 'upper-case i') are
> > almost indistinguishable. For security reasons, DNS-capable email
> > programs (i.e. every email program) may display an email
> > address using hexadecimal (ACE won't work).
> > 
> > How many programs actually do this?
> > 
> > Regards,   Martin.
> > 
> > At 12:16 01/07/15 +0900, Soobok Lee wrote:
> > >Latin 'o' and Greek 'o'  are almost indistinguishable ,
> > >(and I can list up hundreds of such examples.)
> > >but their ACE labels  often look very different.
> > >
> > >For security reasons, IDN-capable email programs
> > >may display an IDN email address
> > >  both in its original scripts and in its ACEed form
> > >  to encourage  instant verification  like this:
> > >"FullName <i18n-mbox@i18n-hostname.com>" [qq--xxx@bq--yyy.com]
> > >
> > >It's more secure but looks ugly. shorter ACE labels may help.
> > >ACE labels are better than appended hexadecimal dump of utf8 lables
> > >for this purpose.
> > >
> > >Soobok Lee
> > 
> 




From owner-idn@ops.ietf.org  Sun Jul 15 02:46:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA22246
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 02:46:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LfQu-000Kae-00
	for idn-data@psg.com; Sat, 14 Jul 2001 23:31:12 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LfQt-000KaY-00
	for idn@ops.ietf.org; Sat, 14 Jul 2001 23:31:11 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15LfQt-0000dF-00; Sat, 14 Jul 2001 23:31:11 -0700
Date: Sun, 15 Jul 2001 06:31:11 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Reality Check
Message-ID: <20010715063111.B2136@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4.2.0.58.J.20010715124450.03e38ac0@sh.w3.mag.keio.ac.jp>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Martin Duerst <duerst@w3.org> wrote:

> > What is supposed to happen when IDN-capable people send email to
> > mailing lists?  Are they supposed to use their non-IDN address if
> > there are any IDN-incapable subscribers?  How will they know?
>
> Assuming that the sender has some clue about how the address will
> show up at the other end, no sender will want ACE to show up.  If
> mail systems don't get some functionality that will automatically
> only use the ACE address if the other systems can display the actual
> characters, ACE will get very bad press. So there is no real argument
> here to favor ACE over UTF-8.

Suppose I have a Chinese email address and an ASCII email address, and
I want to send mail to a mailing list.  Let's compare what happens in a
world without ACE, versus a world with ACE:

In a world without ACE, if I send mail using my Chinese email address,
then all IDN-incapable subscribers will be completely unable to reply to
me.  No thanks, I'll use my ASCII address.  Looks like IDN is going to
have a hard time catching on in this world.

In a world with ACE, if I send mail using my Chinese email address,
everyone will be able to reply to me.  Some subscribers will be
IDN-capable and will see my Chinese address in its proper form, while
others will be IDN-incapable and will see the ACE.  If I use my ASCII
address things will be prettier for the IDN-incapable subscribers who
are familiar with ASCII letters, but less pretty for the IDN-capable
subscribers who are familiar with Chinese characters.  But since
everyone can reply to me in any case, I might prefer to reward the
IDN-capable folks and let the IDN-incapable folks see the ACE.  This way
I can encourage the IDN-incapable folks to upgrade without completely
cutting them off.  IDNs have an easier time catching on in this world.

AMC



From owner-idn@ops.ietf.org  Sun Jul 15 03:14:00 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA02080
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 03:13:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LfUf-000Khm-00
	for idn-data@psg.com; Sat, 14 Jul 2001 23:35:05 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LfUe-000Khg-00
	for idn@ops.ietf.org; Sat, 14 Jul 2001 23:35:04 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15LfUe-0000dm-00; Sat, 14 Jul 2001 23:35:04 -0700
Date: Sun, 15 Jul 2001 06:35:04 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] IDN security and ACE leakage
Message-ID: <20010715063504.C2136@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <033d01c10cf3$c396a2e0$ed1bd9d2@postel.co.kr>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Soobok Lee <lsb@postel.co.kr> wrote:

> some corrections.
> AMC-ACE-Z uses "base36" encoding which includes '0' '1' 'l' 'o'.
> It is the DUDE and AMC-ACE-W that avoid using the four.

Right.  DUDE and AMC-ACE-W use bitwise operations, and can therefore use
only 32 characters.  Since 4 characters had to be left out anyway, it
made sense to leave out the visually confusing ones.

AMC-ACE-Z, on the other hand, does not use bitwise operations, and can
therefore utilize all the characters.

AMC



From owner-idn@ops.ietf.org  Sun Jul 15 13:29:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA27598
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 13:29:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LoXK-000BW8-00
	for idn-data@psg.com; Sun, 15 Jul 2001 09:14:26 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LoXJ-000BW2-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 09:14:26 -0700
Received: from [165.227.249.20] (ip20.proper.com [165.227.249.20])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f6FGELq04773;
	Sun, 15 Jul 2001 09:14:21 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0510031ab7776f708f90@[165.227.249.20]>
In-Reply-To: <3B51BDC6.E8011A76@ehsco.com>
References: <20010715060009.A2136@arwen.cs.berkeley.edu>	
 <3B51B216.33947C1B@ehsco.com> <p05100316b77769501f54@[165.227.249.20]>
 <3B51BDC6.E8011A76@ehsco.com>
Date: Sun, 15 Jul 2001 09:13:26 -0700
To: "Eric A. Hall" <ehall@ehsco.com>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
Cc: "Adam M. Costello" <amc@cs.berkeley.edu>, IDN <idn@ops.ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 10:59 AM -0500 7/15/01, Eric A. Hall wrote:
>Paul Hoffman / IMC wrote:
>>
>>  At 10:09 AM -0500 7/15/01, Eric A. Hall wrote:
>>  >No, only until ACE can be deprecated. This will happen on a per-app
>>  >basis where it happens,
>>
>>  In the IETF, we are not in the habit of saying "features of an
>>  earlier version of this protocol that worked fine will be broken in
>>  this new version". Can you list the advantages to the end users that
>>  deprecating ACE will have?
>
>For specific applications, there are natural benefits. Perhaps HTML v99
>will say "all URLs must be UTF8" just so state doesn't have to be
>maintained between browsers and servers.

Sorry, but that doesn't answer the question, and it instead raises a 
straw man that is untrue. What would be the advantage to end users of 
HTML v99 not interoperating with HTML v98? Also, IDNA does not 
require any state to be maintained between browsers and servers.

>  > >  or with entirely new applications that avoid using ACE
>>  >altogether.
>>
>>  That's like saying "entirely new applications that avoid using the
>  > DNS altogether". Again, please list the advantages to the end user of
>  > creating a protocol that doesn't use the same DNS as the rest of the
>  > IETF protocols.
>
>Not all applications come out of the IETF.

Applications don't come out of the IETF: protocols do. None of this 
discussion is about creating new applications.

>Whose to say that something
>won't use UTF8 solely? Maybe winsock v99 will only provide a wide API.

In the IETF's IDN Working Group, we are discussing IETF protocols. 
Anyone else is free to make whatever other protocols they want, and 
those protocols might or might not use some of the IETF's work.

So, to be clearer: please list the advantages to the end user of the 
IETF creating a protocol that doesn't use the same DNS as the rest of 
the IETF protocols.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Sun Jul 15 13:29:07 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA27609
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 13:29:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Lo5F-000AWt-00
	for idn-data@psg.com; Sun, 15 Jul 2001 08:45:25 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Lo5F-000AWn-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 08:45:25 -0700
Received: from [165.227.249.20] (ip20.proper.com [165.227.249.20])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f6FFjJq03354;
	Sun, 15 Jul 2001 08:45:19 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100316b77769501f54@[165.227.249.20]>
In-Reply-To: <3B51B216.33947C1B@ehsco.com>
References: <20010715060009.A2136@arwen.cs.berkeley.edu>
 <3B51B216.33947C1B@ehsco.com>
Date: Sun, 15 Jul 2001 08:44:24 -0700
To: "Eric A. Hall" <ehall@ehsco.com>, "Adam M. Costello" <amc@cs.berkeley.edu>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: [idn] Why follow IDNA with UTF-8?
Cc: IDN <idn@ops.ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 10:09 AM -0500 7/15/01, Eric A. Hall wrote:
>No, only until ACE can be deprecated. This will happen on a per-app basis
>where it happens,

In the IETF, we are not in the habit of saying "features of an 
earlier version of this protocol that worked fine will be broken in 
this new version". Can you list the advantages to the end users that 
deprecating ACE will have?

>  or with entirely new applications that avoid using ACE
>altogether.

That's like saying "entirely new applications that avoid using the 
DNS altogether". Again, please list the advantages to the end user of 
creating a protocol that doesn't use the same DNS as the rest of the 
IETF protocols.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Sun Jul 15 13:30:04 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA27810
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 13:30:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LnWj-0009LF-00
	for idn-data@psg.com; Sun, 15 Jul 2001 08:09:45 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LnWi-0009L8-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 08:09:44 -0700
Received: from [216.153.32.61] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 161060; Sun, 15 Jul 2001 08:09:05 -0700
Message-ID: <3B51B216.33947C1B@ehsco.com>
Date: Sun, 15 Jul 2001 10:09:10 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Adam M. Costello" <amc@cs.berkeley.edu>
CC: IDN <idn@ops.ietf.org>
Subject: Re: [idn] proposals and deadlines
References: <20010715060009.A2136@arwen.cs.berkeley.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


"Adam M. Costello" wrote:
> 
> "Eric A. Hall" <ehall@ehsco.com> wrote:
> 
> > Even though we could do this [put ACE conversions in the resolver]
> > for the DNS parts, the applications will still have to perform
> > conversions.
> 
> Are you resigned to have applications contain ACE conversion code
> forever?

No, only until ACE can be deprecated. This will happen on a per-app basis
where it happens, or with entirely new applications that avoid using ACE
altogether. But when it happens, the app should end up with a native UTF8
environment, rather than being stuck with ACE.

> On the other hand, if you'd like to see applications evolve away
> from ACE (by upgrading old protocol formats, or replacing old
> protocols by new protocols), then you need to give them a way to avoid
> ACE in DNS lookups too, and that means giving them a UTF-8 resolver
> interface that makes a best effort, not one that gives up too easily
> and expects the application to do the fallback to ACE.

The application *MUST* do the conversion, since protocol operations may
require it.

The example I gave with UTF8 envelopes shows this. If the envelope is
allowing UTF8 IDNs, then it also makes sense that the left-hand-side of
the address (user@) would be encoded in UTF8 rather than using MIME
charset tags. If the option-negotiation succeeded, the mailer would send
UTF8@UTF8, but if not then it would have to send MIME@ACE. Simply put,
some extensions will affect multiple elements and not just DNS, and the
application is the only thing that will know what to do.

This is also the case with DNS lookups. If the POP3/SMTP mailer is
configured with an IDN for the mail server -- and if that lookup fails
(resolver pukes on API, server returns FORMERR, or whatever) -- then the
client knows that it does not have access to an UTF8 environment, and it
can use this information to make subsequent decisions for the remainder of
that session. It will know that it should not attempt to negotiate
UTF8-envelope, for example.

Another example would be X.509 certificates; the resolver could break
things if it returned a UTF8 IDN that didn't match the domain name
provided with the certificate. This would also be important for HTTP where
negotiation would affect URL inputs and redirect outputs; the server must
not send UTF8 IDNs to a client that is not capable of dealing with them if
the client is stuck with an old resolver.

In any event, the application *MUST* perform the conversion, since it is
the only thing that knows all of the ramifications from failure.

You are also working on the assumption that fallback will happen
frequently. I posit that this is not true, for two basic reasons:

  1) If an initial IDN lookup (or test binding) fails, the app
     finds out immediately, and can use ACE for the duration
     of the session. There would be no need for the app to
     negotiate over extended features, no need for the app to
     try issuing any additional UTF8 IDN queries, etc.

  2) Server failure is not to be expected. Nobody should be
     providing IDNs that are not accessible via the IDN
     protocol. What would be the point? Maybe some domain name
     speculators who have not upgraded their servers will
     cause some failures, but legitimate orgs who are trying
     to embrace IDNs will upgrade their infrastructure
     accordingly. Cumulatively, there should be very few
     server-side failures. [Further, where this does happen,
     the client will find out about it and can stop issuing
     UTF8 IDN queries for that session.]

Taken together, very few DNS-level fallback queries should occur. There is
no great penalty. The only measurable penalty in this model is that zone
and cache sizes increase, and this probably isn't much of one (my research
for another effort indicates that memory consumption is not an issue for
the vast majority of servers and/or caches).

> > There is also a technical consideration here, in that this approach
> > does not provide a way to distinguish between spurious 8bit data and
> > IDNs.  An older application that encounters an 8bit domain name may
> > pass it into the stream when it shouldn't (there is at least one
> > application out there now that passes UTF8 into the DNS).  With the
> > dual-message model, at least we can tell that this is an old client
> > and the malformed data can be compared to LDH and rejected, while
> > EDNS messages should only be coming from modernized applications that
> > (hopefully) follow the normalization rules.
> 
> I don't see how this conflicts with anything I've proposed. I have not
> proposed putting 8-bit data into old-style DNS messages.

DNS allows any 8-bit data. There are already implementations that pass
8-bit data in domain names, and the only reason they don't do it
frequently is because IDNs aren't commonly found in the wild yet. Once
IDNs start showing up, these legacy apps will pass 8-bit names more
frequently. It can be expected that at least a few legacy apps will pass
IDNs as rendered (ISO-8859-nn, Windows-nnnn, MacRoman, whatever) instead
of converting them to UTF8 first. At the very least, they will *not* run
them thruogh nameprep first.

The use of an alternative API provides a way to segregate the queries at
the source (the calling application). If 8-bit data comes into the system
using the legacy APIs, it will also use the legacy message, and can be
compared at the zone authoritatively. Conversely, if it comes into the
system using the new APIs and EDNS message, then we are safe in assuming
that the data is UTF8, and that it has been generated according to
application-specific rules (rather than coming from spurious inputs), and
that it has been run through nameprep. In order for this to work, the
messages must somehow be flagged at the server.

Furthermore, this flag must also exist in order for the server to
intelligently handle IDNs in ASCII names. EG, an organization that has
obtained an IDN may want to setup a CNAME for the old ASCII name that
points to an IDN, and the server needs a way to know that it is safe to
return the IDN in the CNAME response. A flag of some kind is required for
this. Reconverting ACE at the client side will not work for all RRs.

The use of a new API allows IDNs to be flagged, but it is the use of a new
and different message that is what's really important. Your proposal does
not provide this differentiator, and allows corrupt data to enter the
query chain on the same footing as legitimate data.

Furthermore, as pointed out earlier, there is no great "I'm always
failing!" penalty, since applications discover failure quickly, and use
this information to make subsequent decisions. If they know they don't
have access to UTF8 IDNs, they will not negotiate the use of UTF8
protocol-specific extensions, and will not generate UTF8 queries.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Sun Jul 15 13:31:25 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA28095
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 13:31:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LotV-000CJ3-00
	for idn-data@psg.com; Sun, 15 Jul 2001 09:37:21 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LotU-000CIx-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 09:37:20 -0700
Received: from [216.153.32.106] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 161068; Sun, 15 Jul 2001 09:36:45 -0700
Message-ID: <3B51C6A2.4F5BDE90@ehsco.com>
Date: Sun, 15 Jul 2001 11:36:50 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Paul Hoffman / IMC <phoffman@imc.org>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, IDN <idn@ops.ietf.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
References: <20010715060009.A2136@arwen.cs.berkeley.edu>
		 <3B51B216.33947C1B@ehsco.com> <p05100316b77769501f54@[165.227.249.20]> <3B51BDC6.E8011A76@ehsco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> For specific applications, there are natural benefits. Perhaps HTML v99
> will say "all URLs must be UTF8" just so state doesn't have to be
> maintained between browsers and servers.

Let me expand on this by saying that any application which supports
version negotiation is a candidate for UTF8 migration. NFS v99 for example
may benefit from an UTF8-only approach, and since NFS supports version
negotiation, this is feasible to implement (relying on version numbers for
fallback negotiation). LDAP v99 would be another.

The IETF is unfortunately not in the habit of mandating versioning in
their application protocols. But wherever it exists, migration is feasible
and even simple, and will offer natural benefits. Where users need ACE,
they can stay with the earlier versions.

For protocols that do not support in-line versioning, once a critical mass
is achieved and sustained (say 10 or even 20 years from now), I expect
that many implementations will default to UTF8, even if the protocol
doesn't. Look at TELNET: there aren't very many implmentations that
support Go-Ahead anymore (even though it is mandated by the protocol),
simply because there isn't much of a need for it anymore. Why would UTF8
be any different? If every SMTP client and server on the planet supports
UTF8, new implementations may implement just that, and freak out when
negotiation fails (like most of the TELNET implementations do when SGA
fails).

> So, to be clearer: please list the advantages to the end user of the
> IETF creating a protocol that doesn't use the same DNS as the rest of
> the IETF protocols.

It's not a different DNS. I don't know why you're saying that. The same
authoritative servers and the same zone data is being used. What is
different about it?

The advantages may or may not be compelling at this point. It is most
likely to simply be a matter of pragmatism when it happens (not "if" but
"when"). New protocols are already required to use ISO-10646 for charsets,
so how long will it be before the IAB simply decrees that UTF8 is the
preferred encoding as well? The ISO-10646 decree certainly wasn't driven
by user benefit, why would this one?

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Sun Jul 15 13:48:25 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA01058
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 13:48:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LoIv-000B0O-00
	for idn-data@psg.com; Sun, 15 Jul 2001 08:59:33 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LoIu-000B0I-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 08:59:32 -0700
Received: from [216.153.32.61] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 161063; Sun, 15 Jul 2001 08:58:57 -0700
Message-ID: <3B51BDC6.E8011A76@ehsco.com>
Date: Sun, 15 Jul 2001 10:59:02 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Paul Hoffman / IMC <phoffman@imc.org>
CC: "Adam M. Costello" <amc@cs.berkeley.edu>, IDN <idn@ops.ietf.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
References: <20010715060009.A2136@arwen.cs.berkeley.edu>
	 <3B51B216.33947C1B@ehsco.com> <p05100316b77769501f54@[165.227.249.20]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Paul Hoffman / IMC wrote:
> 
> At 10:09 AM -0500 7/15/01, Eric A. Hall wrote:
> >No, only until ACE can be deprecated. This will happen on a per-app
> >basis where it happens,
> 
> In the IETF, we are not in the habit of saying "features of an
> earlier version of this protocol that worked fine will be broken in
> this new version". Can you list the advantages to the end users that
> deprecating ACE will have?

For specific applications, there are natural benefits. Perhaps HTML v99
will say "all URLs must be UTF8" just so state doesn't have to be
maintained between browsers and servers.

> >  or with entirely new applications that avoid using ACE
> >altogether.
> 
> That's like saying "entirely new applications that avoid using the
> DNS altogether". Again, please list the advantages to the end user of
> creating a protocol that doesn't use the same DNS as the rest of the
> IETF protocols.

Not all applications come out of the IETF. Whose to say that something
won't use UTF8 solely? Maybe winsock v99 will only provide a wide API.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Sun Jul 15 13:55:19 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA01825
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 13:55:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LplN-000EEq-00
	for idn-data@psg.com; Sun, 15 Jul 2001 10:33:01 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LplM-000EEX-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 10:33:00 -0700
Received: from [165.227.249.20] (ip20.proper.com [165.227.249.20])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f6FHWtq18312;
	Sun, 15 Jul 2001 10:32:55 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0510031db7777d16c4af@[165.227.249.20]>
In-Reply-To: <3B51C6A2.4F5BDE90@ehsco.com>
References: <20010715060009.A2136@arwen.cs.berkeley.edu>		
 <3B51B216.33947C1B@ehsco.com> <p05100316b77769501f54@[165.227.249.20]>
 <3B51BDC6.E8011A76@ehsco.com> <3B51C6A2.4F5BDE90@ehsco.com>
Date: Sun, 15 Jul 2001 10:31:48 -0700
To: "Eric A. Hall" <ehall@ehsco.com>, "Adam M. Costello" <amc@cs.berkeley.edu>,
        IDN <idn@ops.ietf.org>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 11:36 AM -0500 7/15/01, Eric A. Hall wrote:
>Let me expand on this by saying that any application which supports
>version negotiation is a candidate for UTF8 migration.

Not unless there is a possible need for that migration. And, again, 
you have not shown even a single example of that possible need.

>For protocols that do not support in-line versioning, once a critical mass
>is achieved and sustained (say 10 or even 20 years from now), I expect
>that many implementations will default to UTF8, even if the protocol
>doesn't.

Ignoring backwards compatibility for no advantage is not a common 
trait among application writers.

>  > So, to be clearer: please list the advantages to the end user of the
>>  IETF creating a protocol that doesn't use the same DNS as the rest of
>>  the IETF protocols.
>
>It's not a different DNS. I don't know why you're saying that. The same
>authoritative servers and the same zone data is being used. What is
>different about it?

It uses a different part of the DNS protocol, namely the marking of 
the UTF-8 requests and responses. We are talking about *protocols* 
here, not file formats.

>The advantages may or may not be compelling at this point.

Well, you haven't given a single instance of one that might be 
compelling, so it is more accurate to simply say "there are no known 
advantages now".

>  It is most
>likely to simply be a matter of pragmatism when it happens (not "if" but
>"when").

So, although there is no need now, you firmly predict that there will 
be and therefore we have to act now with a protocol. How do you know 
that your protocol will in fact meet the future need? There are lots 
of different proposals for how to do marked UTF-8 in DNS; why are you 
so sure that your marking plan will work for the as-yet-unknown needs?

>  New protocols are already required to use ISO-10646 for charsets,

That statement is incorrect. BCP 18 says that protocols that use 
character data are required to at mark the character data with 
charsets, and at least be able to use the UTF-8 charset, but are 
explicitly allowed to use other charsets. IDNA does not use character 
data: it encodes labels.

>so how long will it be before the IAB simply decrees that UTF8 is the
>preferred encoding as well?

There are IAB members who are following this list; maybe you should 
let them answer the question instead of answering it for them.

>  The ISO-10646 decree certainly wasn't driven
>by user benefit, why would this one?

BCP 18 most certainly was driven by user benefit; to say otherwise is 
fairly insulting to the many people who worked on it. Mandating that 
any protocol that can accept charsets MUST accept UTF-8 greatly 
increases interoperability (which benefits end users) *and* makes 
sure that all applications use at least one charset that uses all of 
the scripts in the world (which benefits end users outside 
English-speaking countries).

Please re-read BCP 18 before you use it in the context of this discussion.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Sun Jul 15 14:27:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA06701
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 14:27:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Lq8g-000F5Q-00
	for idn-data@psg.com; Sun, 15 Jul 2001 10:57:06 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Lq8f-000F5K-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 10:57:05 -0700
Received: from [216.153.32.121] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 161075; Sun, 15 Jul 2001 10:56:30 -0700
Message-ID: <3B51D952.BC11859B@ehsco.com>
Date: Sun, 15 Jul 2001 12:56:34 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Paul Hoffman / IMC <phoffman@imc.org>
CC: "Adam M. Costello" <amc@cs.berkeley.edu>, IDN <idn@ops.ietf.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
References: <20010715060009.A2136@arwen.cs.berkeley.edu>		
	 <3B51B216.33947C1B@ehsco.com> <p05100316b77769501f54@[165.227.249.20]>
	 <3B51BDC6.E8011A76@ehsco.com> <3B51C6A2.4F5BDE90@ehsco.com> <p0510031db7777d16c4af@[165.227.249.20]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Paul Hoffman / IMC wrote:
> 
> At 11:36 AM -0500 7/15/01, Eric A. Hall wrote:
> >Let me expand on this by saying that any application which supports
> >version negotiation is a candidate for UTF8 migration.
> 
> Not unless there is a possible need for that migration. And, again,
> you have not shown even a single example of that possible need.

I do not assume that I can predict all possible uses of inline UTF8 data.
What I do know is that people will not want ACE in their soup.

If you are only wanting one possible example, think of a protocol for
replicating mail-routing maps. Wouldn't it be beneficial for the admins of
the affected mail servers to have a common format for that data? Wouldn't
it make sense to use UTF8 for the IDNs in the router maps, given its
usability with multiple languages? Furthermore, wouldn't it be beneficial
if the data and the IDN protocol both used the same encodings? How would
it benefit anybody to manage ACE-encoded lists of mail domains? How would
it benefit anybody to replicate a UTF8 list that had to be converted into
ACE for pre-processing? If UTF8 were available for the list contents and
the pre-processing, wouldn't it that be beneficial to the users?

Clearly there are natural benefits to using UTF8 everywhere. Providing
access to UTF8 (whether with this mechanism or some other) allows for
greater levels of functionality, servicability and usability.

> >It's not a different DNS. I don't know why you're saying that. The
> >same authoritative servers and the same zone data is being used.
> >What is different about it?
> 
> It uses a different part of the DNS protocol, namely the marking of
> the UTF-8 requests and responses. We are talking about *protocols*
> here, not file formats.

By this argument, every RR represents a different DNS.

> >  New protocols are already required to use ISO-10646 for charsets,
> 
> That statement is incorrect. BCP 18 says ...

I was referring to RFC2130.

As to the other comments following this, all I will say is that I was
referring to the commentary provided in RFC2130. I was not intending to
insult anybody, and if anybody was offended by any misrepresentation or
misintepretation, I apologize for the brush.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Sun Jul 15 16:04:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA22748
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 16:04:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LrN5-000HwT-00
	for idn-data@psg.com; Sun, 15 Jul 2001 12:16:03 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LrN4-000Hw4-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 12:16:02 -0700
Received: from [165.227.249.20] (ip20.proper.com [165.227.249.20])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f6FJFuq27586;
	Sun, 15 Jul 2001 12:15:56 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100321b777942a30d1@[165.227.249.20]>
In-Reply-To: <3B51D952.BC11859B@ehsco.com>
References: <20010715060009.A2136@arwen.cs.berkeley.edu>			
 <3B51B216.33947C1B@ehsco.com> <p05100316b77769501f54@[165.227.249.20]>	
 <3B51BDC6.E8011A76@ehsco.com> <3B51C6A2.4F5BDE90@ehsco.com>
 <p0510031db7777d16c4af@[165.227.249.20]> <3B51D952.BC11859B@ehsco.com>
Date: Sun, 15 Jul 2001 12:14:52 -0700
To: "Eric A. Hall" <ehall@ehsco.com>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
Cc: "Adam M. Costello" <amc@cs.berkeley.edu>, IDN <idn@ops.ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 12:56 PM -0500 7/15/01, Eric A. Hall wrote:
>I do not assume that I can predict all possible uses of inline UTF8 data.

Nor were you ever asked to.

>If you are only wanting one possible example, think of a protocol for
>replicating mail-routing maps.

That's rather obscure, but let's go with it.

>  Wouldn't it be beneficial for the admins of
>the affected mail servers to have a common format for that data?

Yes.

>  Wouldn't
>it make sense to use UTF8 for the IDNs in the router maps, given its
>usability with multiple languages?

Not necessarily. The format of the router maps could be plain text 
with UTF-8, plain text with ACE, ASN.1, and so on. You are mixing up 
document formats with DNS protocol.

>  Furthermore, wouldn't it be beneficial
>if the data and the IDN protocol both used the same encodings?

Probably, and that would be ACE.

>  How would
>it benefit anybody to manage ACE-encoded lists of mail domains?

Because ACE is being used as the host names that are being routed. 
You can't say "UTF-8 is needed for this protocol" unless UTF-8 is 
being used in the DNS.

>  How would
>it benefit anybody to replicate a UTF8 list that had to be converted into
>ACE for pre-processing?

The list does not have to be UTF-8: it could be in a wide variety of formats.

>  If UTF8 were available for the list contents and
>the pre-processing, wouldn't it that be beneficial to the users?

No more so than ACE, or ASN.1, or whatever.

>Clearly there are natural benefits to using UTF8 everywhere.

Sure, if you ignore most existing protocols and the severe problems 
during the wholesale upgrade of DNS servers. Have you now shifted 
from "ACE then UTF-8" to "never ACE"?

>  Providing
>access to UTF8 (whether with this mechanism or some other) allows for
>greater levels of functionality, servicability and usability.

You still haven't shown that. You gave one example in which a 
document format might be in UTF-8, but could just as easily been in 
any other format.

Do you have other, hopefully better, examples?
>  > >  New protocols are already required to use ISO-10646 for charsets,
>>
>>  That statement is incorrect. BCP 18 says ...
>
>I was referring to RFC2130.

RFC 2130 is not a "decree": it is an Informational RFC that is simply 
a report from a workshop. It does not "require" anything, and it is 
incorrect to say that it does. BCP 18, which came out after RFC 2130, 
is a synthesis of the ideas from the workshop. BCP 18 has 
requirements, but they do not apply to IDNA because IDNA does not 
deal with text content.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Sun Jul 15 16:10:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA23449
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 16:10:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LrXR-000IKo-00
	for idn-data@psg.com; Sun, 15 Jul 2001 12:26:45 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15LrXQ-000IKh-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 12:26:44 -0700
Received: (qmail 12548 invoked by uid 1001); 15 Jul 2001 19:24:26 -0000
Date: 15 Jul 2001 19:24:26 -0000
Message-ID: <20010715192426.31277.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
Automatic-Copyright-Notice: Copyright 2001, D. J. Bernstein. My transmission of this message to you does not constitute a copyright waiver or any other limitation of my rights, even if you have told me otherwise.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] Reality Check
References: <4.2.0.58.J.20010715124450.03e38ac0@sh.w3.mag.keio.ac.jp> <20010715063111.B2136@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Adam M. Costello writes:
> IDN-incapable subscribers will be completely unable to reply

Are you saying that there are mail readers today that can't reply to a
UTF-8 address? Please identify the specific software bugs that you're
talking about.

As far as I know, there are only two relevant bugs anywhere in the
entire mail path: the UNIX gethostbyname() 8-bit bug, which in current
versions is trivially worked around with a one-line change to
/etc/resolv.conf, and the sendmail 8-bit bug.

There are certainly some programs that don't _display_ UTF-8 nicely, but
that's a separate issue. (They don't display ACE nicely either.)

---Dan



From owner-idn@ops.ietf.org  Sun Jul 15 16:22:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA24933
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 16:22:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Lru9-000JFO-00
	for idn-data@psg.com; Sun, 15 Jul 2001 12:50:13 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Lru8-000JFI-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 12:50:12 -0700
Received: from [216.153.32.87] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 161081; Sun, 15 Jul 2001 12:49:37 -0700
Message-ID: <3B51F3D5.23F8460F@ehsco.com>
Date: Sun, 15 Jul 2001 14:49:42 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Paul Hoffman / IMC <phoffman@imc.org>
CC: "Adam M. Costello" <amc@cs.berkeley.edu>, IDN <idn@ops.ietf.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
References: <20010715060009.A2136@arwen.cs.berkeley.edu>			
	 <3B51B216.33947C1B@ehsco.com> <p05100316b77769501f54@[165.227.249.20]>	
	 <3B51BDC6.E8011A76@ehsco.com> <3B51C6A2.4F5BDE90@ehsco.com>
	 <p0510031db7777d16c4af@[165.227.249.20]> <3B51D952.BC11859B@ehsco.com> <p05100321b777942a30d1@[165.227.249.20]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> >  Wouldn't
> >it make sense to use UTF8 for the IDNs in the router maps, given its
> >usability with multiple languages?
> 
> Not necessarily. The format of the router maps could be plain text
> with UTF-8, plain text with ACE, ASN.1, and so on. You are mixing up
> document formats with DNS protocol.

Yes I am, because in this case, the document will be edited and its
contents reused later in SMTP and DNS. If we are encouraged to use UTF8
for the document contents by various OS and protocol issues, then we
should also be using UTF8 for the DNS parts.

> >  Furthermore, wouldn't it be beneficial
> >if the data and the IDN protocol both used the same encodings?
> 
> Probably, and that would be ACE.

Once a UTF8 format exists, why not leverage it? It would not be unheard of
for a new protocol to make such a demand. HTML 4.0 has different technical
demands than HTML 3.2, for example.

> >Clearly there are natural benefits to using UTF8 everywhere.
> 
> Sure, if you ignore most existing protocols and the severe problems
> during the wholesale upgrade of DNS servers.

What severe problems?

Is the need to upgrade ACE clients (and servers, unless you consider
manually editing ACE gobbledygook in zone files to be a wonderful feature)
also a severe problem?

> Have you now shifted
> from "ACE then UTF-8" to "never ACE"?

For new applications, there is absolutely the possibility that they will
be able to only specify the use of UTF8. This is a good thing, as new
applications can be written for international markets from the beginning,
and UTF8 is becoming very common. UTF8-in-DNS is an enabler. Furthermore I
would argue that it is absolutely critical to the next twenty years of
protocol work.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Sun Jul 15 16:52:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA28262
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 16:52:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LsYE-000Klv-00
	for idn-data@psg.com; Sun, 15 Jul 2001 13:31:38 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15LsYD-000Kln-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 13:31:37 -0700
Received: (qmail 14913 invoked by uid 1001); 15 Jul 2001 20:30:04 -0000
Date: 15 Jul 2001 20:30:04 -0000
Message-ID: <20010715203004.30572.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org,
  iesg@ietf.org,
  poised@lists.tislabs.com
Automatic-Copyright-Notice: Copyright 2001, D. J. Bernstein. My transmission of this message to you does not constitute a copyright waiver or any other limitation of my rights, even if you have told me otherwise.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org, iesg@ietf.org, poised@lists.tislabs.com
Subject: [idn] UTF-8 as the long-term IDN solution
References: <E15LLxX-000G18-00@psg.com> <20010714211816.D31484@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > I have read a lot of comments on this list that state that ACE is just
> > an intermediate step to help us get to a UTF-8 solution.
> I don't agree with those comments.

I believe that the IDN WG has consensus on the following point: ``The
long-term IDN solution will encode Unicode characters as UTF-8 on the
wire.'' I find the other possibilities absurd, and I am dismayed at the
amount of time that has been wasted discussing them on the IDN list.

On 2001-05-29 I requested that the the IDN WG chairs run a poll to see
whether we do, in fact, have consensus on this point.

``I would like to hear some support on this before we run this poll,''
James Seng said, speaking as chair.

He promptly heard some support, but he did not run the poll. I asked why
the chairs were not running the poll. There was no response.

I accuse the chairs of bias in their selection of polls. They appear to
be running polls that they believe will promote their personal agendas,
and refusing to run any other polls. Does the IETF have any procedures
to fix this problem?

In a legitimate standards organization, when 2/3 of the members agree on
something, they can easily force a binding vote---not just a wishy-washy
``poll''---over the chair's opposition. They can even expel the chair;
I've never heard of that actually happening, but it's comforting to know
that the group has final control over the chair, instead of vice versa.

---Dan



From owner-idn@ops.ietf.org  Sun Jul 15 18:00:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA05759
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 18:00:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Lt6B-000M53-00
	for idn-data@psg.com; Sun, 15 Jul 2001 14:06:43 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Lt6A-000M4x-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 14:06:42 -0700
Received: from [165.227.249.20] (ip20.proper.com [165.227.249.20])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f6FL6Xq29844;
	Sun, 15 Jul 2001 14:06:33 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100325b777b39692ae@[165.227.249.20]>
In-Reply-To: <3B51F3D5.23F8460F@ehsco.com>
References: <20010715060009.A2136@arwen.cs.berkeley.edu>				
 <3B51B216.33947C1B@ehsco.com> <p05100316b77769501f54@[165.227.249.20]>		
 <3B51BDC6.E8011A76@ehsco.com> <3B51C6A2.4F5BDE90@ehsco.com>	
 <p0510031db7777d16c4af@[165.227.249.20]> <3B51D952.BC11859B@ehsco.com>
 <p05100321b777942a30d1@[165.227.249.20]> <3B51F3D5.23F8460F@ehsco.com>
Date: Sun, 15 Jul 2001 14:05:38 -0700
To: "Eric A. Hall" <ehall@ehsco.com>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
Cc: "Adam M. Costello" <amc@cs.berkeley.edu>, IDN <idn@ops.ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 2:49 PM -0500 7/15/01, Eric A. Hall wrote:
>What severe problems?

If any DNS server in the search path for a name has not been updated, 
or if the user's resolver has not been updated, the query will fail. 
That seems pretty bad, yes?

>Is the need to upgrade ACE clients (and servers, unless you consider
>manually editing ACE gobbledygook in zone files to be a wonderful feature)
>also a severe problem?

No. Applications will need to be upgraded no matter what. Further, 
DNS servers do *not* need to be upgraded: the editing interface to 
the host file does. That is pretty trivial: a single script that 
converts the native-charset file (which does not have to be UTF-8: it 
can be any native charset) to the host file. It took me about 5 
minutes to write mine in Perl (using an existing ACE<=>UTF-8 routine).

>  > Have you now shifted
>>  from "ACE then UTF-8" to "never ACE"?
>
>For new applications, there is absolutely the possibility that they will
>be able to only specify the use of UTF8.

One more time: we are talking about protocols, not applications. And, 
even then "able to" is completely different than "needs to". Where is 
the need here? How will balkanizing the DNS help end users?

>  This is a good thing, as new
>applications can be written for international markets from the beginning,
>and UTF8 is becoming very common. UTF8-in-DNS is an enabler. Furthermore I
>would argue that it is absolutely critical to the next twenty years of
>protocol work.

Because...?

You still haven't given any examples of why it is needed, only one 
where it would make writing an application only slightly easier, but 
only if we already had UTF-8 names. Please reconsider your arguments 
about an upgrade path.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Sun Jul 15 21:05:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA25931
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 21:05:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LvG2-0001D4-00
	for idn-data@psg.com; Sun, 15 Jul 2001 16:25:02 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LvG1-0001Cq-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 16:25:01 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15LvG0-0002De-00; Sun, 15 Jul 2001 16:25:00 -0700
Date: Sun, 15 Jul 2001 23:25:00 +0000
To: IDN <idn@ops.ietf.org>
Subject: Re: [idn] proposals and deadlines
Message-ID: <20010715232459.A8322@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B51B216.33947C1B@ehsco.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

"Eric A. Hall" <ehall@ehsco.com> wrote:

> No, only until ACE can be deprecated.  This will happen on a per-app
> basis where it happens, or with entirely new applications that avoid
> using ACE altogether.  But when it happens, the app should end up with
> a native UTF8 environment, rather than being stuck with ACE.

Okay, now let's think about this hypothetical new application that
uses UTF-8 natively.  It uses UTF-8 to talk to its peers, and UTF-8 to
interact with the user, data files, etc.  Absolutely everything it ever
does with domain names uses UTF-8.  Except one thing: DNS lookups, which
sometimes use UTF-8 and sometimes use ACE.  Why?  Because the UTF-8
resolver interface you have postulated gives up when EDNS fails.  Our
application has no control over whether the local DNS server supports
EDNS, or whether any particular caching DNS server between the local
server and the target supports EDNS.  Therefore, the application will
need to do its own fallback to the old resolver interface, which means
the application will need to be able to perform ACE encoding, so it is
not completely free of ACE.

But your stated goal is to avoid having the application stuck with ACE.
If there were a UTF-8 resolver interface that would make a best effort,
instead of giving up when EDNS is unavailable, then the application
could truly eliminate all traces of ACE within itself.  Isn't that what
you want?

> In any event, the application *MUST* perform the conversion, since it
> is the only thing that knows all of the ramifications from failure.

I'm not trying to assert that providing a best-effort UTF-8 resolver
interface will magically free applications from doing ACE conversions.
Of course it won't, because there are many reasons unrelated to DNS that
applications might need to use ACE.  But even after applications manage
to eliminate all those other reasons, they still cannot completely free
themselves of ACE unless this best-effort UTF-8 resolver interface
exists.

> You are also working on the assumption that fallback will happen
> frequently.

No I am not.  I am working under the assumption that, for an application
programmer, it doesn't matter whether the fallback happens frequently
or rarely, either way the programmer still needs to write code for
doing it.  The only way to avoid that code in the application is if the
fallback happens *never* (that is, never in the application, but instead
in the resolver).

> Your proposal does not provide this differentiator, and allows corrupt
> data to enter the query chain on the same footing as legitimate data.

What do you think my proposal is?  I have not suggested that calls to
the old resolver interface should ever perform EDNS queries or ACE
transformations; the old interface should continue to do exactly what it
does today.  I have not suggested that DNS servers should ever put 8-bit
data into old-style responses.  I have not suggested that resolvers
falling back from EDNS to DNS should ever put 8-bit data into old-style
queries.  I don't see how I'm allowing corrupt data to enter anything.
If you still think I am, you'll have to walk me through a concrete
scenario.

> If [applications] know they don't have access to UTF8 IDNs, they will
> not negotiate the use of UTF8 protocol-specific extensions, and will
> not generate UTF8 queries.

Just because my local DNS server doesn't support EDNS, that doesn't mean
I should speak ACE to my application-layer peer.  If that peer and I
both support UTF-8, then we should speak UTF-8 to each other, regardless
of the capabilities of my name server, in order to reduce the risk of
ACE leakage.

AMC



From owner-idn@ops.ietf.org  Sun Jul 15 21:06:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA26040
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 21:06:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LwJ5-0003x4-00
	for idn-data@psg.com; Sun, 15 Jul 2001 17:32:15 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LwJ5-0003wy-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 17:32:15 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15LwJ4-0002Jc-00; Sun, 15 Jul 2001 17:32:14 -0700
Date: Mon, 16 Jul 2001 00:32:14 +0000
To: IDN <idn@ops.ietf.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
Message-ID: <20010716003214.C8322@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4.2.0.58.J.20010716085702.03e95c90@sh.w3.mag.keio.ac.jp>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Martin Duerst <duerst@w3.org> wrote:

> In HTML 4.0, there is a provision that says that URIs that contain
> non-ASCII characters should be interpreted based on conversion to
> UTF-8
>
> The Web and the W3C took RFC 2277 seriously.  We are ready for UTF-8,
> we don't need ACE at all.

Not quite.  HTML 4.01 still says that URIs are defined by RFC 2396.  So
consider href="http://IDN.com/foo/".  The provision you mention will
convert it to http://%HH%HH%HH.com/foo/, but that's not a syntactically
valid URI according to RFC 2396, which says the host part can contain
only letters, digits, hyphens, and dots, not percent signs.  And nowhere
does the HTML spec say that the %HH encoding should not be used on the
host part (or should be undone before the name is looked up).

AMC



From owner-idn@ops.ietf.org  Sun Jul 15 21:07:09 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA26149
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 21:07:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Lvzo-00036Q-00
	for idn-data@psg.com; Sun, 15 Jul 2001 17:12:20 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Lvzn-00036J-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 17:12:19 -0700
Received: from enoshima (e147152.ppp.asahi-net.or.jp [211.13.147.152])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id JAA01764;
	Mon, 16 Jul 2001 09:12:22 +0900 (JST)
Message-Id: <4.2.0.58.J.20010716085702.03e95c90@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Mon, 16 Jul 2001 09:11:58 +0900
To: Paul Hoffman / IMC <phoffman@imc.org>, "Eric A. Hall" <ehall@ehsco.com>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
Cc: "Adam M. Costello" <amc@cs.berkeley.edu>, IDN <idn@ops.ietf.org>
In-Reply-To: <p0510031ab7776f708f90@[165.227.249.20]>
References: <3B51BDC6.E8011A76@ehsco.com>
 <20010715060009.A2136@arwen.cs.berkeley.edu>
 <3B51B216.33947C1B@ehsco.com>
 <p05100316b77769501f54@[165.227.249.20]>
 <3B51BDC6.E8011A76@ehsco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 09:13 01/07/15 -0700, Paul Hoffman / IMC wrote:
>At 10:59 AM -0500 7/15/01, Eric A. Hall wrote:
>>Paul Hoffman / IMC wrote:

>>For specific applications, there are natural benefits. Perhaps HTML v99
>>will say "all URLs must be UTF8" just so state doesn't have to be
>>maintained between browsers and servers.
>
>Sorry, but that doesn't answer the question, and it instead raises a straw 
>man that is untrue. What would be the advantage to end users of HTML v99 
>not interoperating with HTML v98? Also, IDNA does not require any state to 
>be maintained between browsers and servers.

Talking about HTML v99 or HTML v98 is a complete strawman indeed.
But let's talk about HTML 4.0. In HTML 4.0, there is a provision that
says that URIs that contain non-ASCII characters should be interpreted
based on conversion to UTF-8 (which is a slight, but very important
difference from 'all URIs must be UTF-8). And there is no old HTML
that contains IDNs.

And the newest versions of the main browsers support this convention.
And there is no need for state to be maintained between browsers and
servers; that's not what the HTTP protocol is about.

The Web and the W3C took RFC 2277 seriously. We are ready for UTF-8,
we don't need ACE at all. For HTML and the Web (also including XML,
XML Schema, XLink,...), ACE is useless baggage.


Regards,   Martin.

#-#-#  Martin J. Du"rst, I18N Activity Lead, World Wide Web Consortium
#-#-#  mailto:duerst@w3.org   http://www.w3.org/People/D%C3%BCrst



From owner-idn@ops.ietf.org  Sun Jul 15 21:09:30 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA26420
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 21:09:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LwGZ-0003or-00
	for idn-data@psg.com; Sun, 15 Jul 2001 17:29:39 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LwGY-0003ol-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 17:29:38 -0700
Received: from enoshima (e147152.ppp.asahi-net.or.jp [211.13.147.152])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id JAA01811;
	Mon, 16 Jul 2001 09:29:53 +0900 (JST)
Message-Id: <4.2.0.58.J.20010716091901.03e09320@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Mon, 16 Jul 2001 09:28:49 +0900
To: Paul Hoffman / IMC <phoffman@imc.org>, "Eric A. Hall" <ehall@ehsco.com>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
Cc: "Adam M. Costello" <amc@cs.berkeley.edu>, IDN <idn@ops.ietf.org>
In-Reply-To: <p05100325b777b39692ae@[165.227.249.20]>
References: <3B51F3D5.23F8460F@ehsco.com>
 <20010715060009.A2136@arwen.cs.berkeley.edu>
 <3B51B216.33947C1B@ehsco.com>
 <p05100316b77769501f54@[165.227.249.20]>
 <3B51BDC6.E8011A76@ehsco.com>
 <3B51C6A2.4F5BDE90@ehsco.com>
 <p0510031db7777d16c4af@[165.227.249.20]>
 <3B51D952.BC11859B@ehsco.com>
 <p05100321b777942a30d1@[165.227.249.20]>
 <3B51F3D5.23F8460F@ehsco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 14:05 01/07/15 -0700, Paul Hoffman / IMC wrote:

>[T]he editing interface to the host file does. That is pretty trivial: a 
>single script that converts the native-charset file (which does not have 
>to be UTF-8: it can be any native charset) to the host file. It took me 
>about 5 minutes to write mine in Perl (using an existing ACE<=>UTF-8 routine).

That's five minutes for each different format. And then that's a few seconds
every time a conversion is needed. Nobody in the US would want to do that
for US-ASCII. For US-ASCII, the widest variety of Internet protocols is
designed so that no such additional conversion step is necessary.
And for those protocols and formats where it's not the case, everybody
complains about, and for good reason. Why is it so difficult for somebody
like you to understand that the rest of the world would also benefit
greatly from this, and that it's a bad idea to deny them such benefits?


>>  > Have you now shifted
>>>  from "ACE then UTF-8" to "never ACE"?

I for one always claimed that ACE is a big step backwards.


Regards,   Martin.



From owner-idn@ops.ietf.org  Sun Jul 15 21:09:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA26458
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 21:09:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LwPd-0004Es-00
	for idn-data@psg.com; Sun, 15 Jul 2001 17:39:01 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LwPd-0004Eh-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 17:39:01 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15LwPc-0002L9-00; Sun, 15 Jul 2001 17:39:00 -0700
Date: Mon, 16 Jul 2001 00:39:00 +0000
To: idn working group <idn@ops.ietf.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
Message-ID: <20010716003900.D8322@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4.2.0.58.J.20010716091901.03e09320@sh.w3.mag.keio.ac.jp>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk


At 14:05 01/07/15 -0700, Paul Hoffman / IMC wrote:

> [T]he editing interface to the host file does.  That is pretty
> trivial: a single script that converts the native-charset file (which
> does not have to be UTF-8: it can be any native charset) to the host
> file.  It took me about 5 minutes to write mine in Perl (using an
> existing ACE<=>UTF-8 routine).

Martin Duerst <duerst@w3.org> replied:

> That's five minutes for each different format.  And then that's a few
> seconds every time a conversion is needed.

Okay, anyone who doesn't like that method can get a DNS server that
reads UTF-8 zone files directly (I have no doubt that such servers will
appear) and use their favorite UTF-8 capable editor to edit it.  The
encoding used by the server on the wire is orthogonal to the zone file
encoding.

AMC



From owner-idn@ops.ietf.org  Sun Jul 15 21:10:30 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA26542
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 21:10:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Lw0m-00039K-00
	for idn-data@psg.com; Sun, 15 Jul 2001 17:13:20 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Lw0m-00039E-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 17:13:20 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15Lw0l-0002H5-00; Sun, 15 Jul 2001 17:13:19 -0700
Date: Mon, 16 Jul 2001 00:13:19 +0000
To: idn@ops.ietf.org
Cc: iesg@ietf.org, poised@lists.tislabs.com
Subject: Re: [idn] Reality Check
Message-ID: <20010716001319.B8322@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20010715203004.30572.qmail@cr.yp.to> <20010715192426.31277.qmail@cr.yp.to>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

"D. J. Bernstein" <djb@cr.yp.to> wrote:

> Are you saying that there are mail readers today that can't reply to a
> UTF-8 address?  Please identify the specific software bugs that you're
> talking about.

I'm not talking about any bugs.  I'm talking about software that
conforms to the standards.

> As far as I know, there are only two relevant bugs anywhere in the
> entire mail path: the UNIX gethostbyname() 8-bit bug, which in
> current versions is trivially worked around with a one-line change to
> /etc/resolv.conf, and the sendmail 8-bit bug.

Out of dozens (if not hundreds) of mail user agents, and dozens of mail
transfer agents, and various resolver and DNS server implementations,
you think there are only two that rely on hostnames being what the
standard says they are?

I think that's very unlikely, but suppose these were indeed the only
two.  Then the only people who can't reply to my IDN address are UNIX
users who haven't customized their /etc/resolv.conf and anyone whose
mail would have to pass through sendmail on its way to me.  Hmmm, if I
care about getting replies, I think I'd stick with ASCII names rather
than stuff UTF-8 into message headers.  But with ACE, everyone can
reply, even people behind "buggy" (standard-conformant) software, so I'd
use that.

> I believe that the IDN WG has consensus on the following point: ``The
> long-term IDN solution will encode Unicode characters as UTF-8 on the
> wire.'' I find the other possibilities absurd, and I am dismayed at
> the amount of time that has been wasted discussing them on the IDN
> list.

I think we have consensus on "New protocols should use UTF-8 for
hostnames."  We might have strong support for "Existing application
protocols should try to migrate toward UTF-8."  I don't think there is
anything approaching consensus on "ACE will eventually be eradicated
from all protocols."

Here is one end-game that I don't find absurd:  UTF-8 everywhere
except in DNS messages, which use ACE.  DNS already uses a different
representation of domain names than everything else does:  Everything
else uses dots to separate the labels, while DNS does not, so the
resolver already has to translate back and forth.  There are very few
things that speak DNS directly (like DNS servers, resolvers, and MTAs)
and everything else could be oblivious to ACE.

Why don't I think it's important to eliminate ACE from DNS?  Because
I don't think it's even practical.  We wouldn't be able to remove ACE
support from DNS until all other message/file formats support UTF-8 IDNs
and all ACEs in all data files have been decoded.  Even if that ever
came to pass, how would we know?

Why don't I think it's important to add a UTF-8 option to DNS?  Because
ACE gets the job done, and adding a UTF-8 option would increase the
complexity of DNS servers (which would then have to handle both UTF-8
and ACE) while helping only a few entities (the ones that speak DNS
directly).  While many applications might appreciate a UTF-8 resolver
interface, most have no way to know how DNS messages are encoded, and no
reason to care.

AMC



From owner-idn@ops.ietf.org  Sun Jul 15 21:12:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA26801
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 21:12:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LviF-0002O3-00
	for idn-data@psg.com; Sun, 15 Jul 2001 16:54:11 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LviE-0002N2-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 16:54:11 -0700
Received: from enoshima (e147152.ppp.asahi-net.or.jp [211.13.147.152])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id IAA01736;
	Mon, 16 Jul 2001 08:54:08 +0900 (JST)
Message-Id: <4.2.0.58.J.20010716084917.03df7800@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Mon, 16 Jul 2001 08:53:44 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] IDN security and ACE leakage
In-Reply-To: <031c01c10ce6$f1c95700$ed1bd9d2@postel.co.kr>
References: <20010714211816.D31484@arwen.cs.berkeley.edu>
 <4.2.0.58.J.20010715125225.00a00dc0@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 13:30 01/07/15 +0900, Soobok Lee wrote:
>For 1 and 'l', choosing a good latin display font set is enough.
>and the ambiguity is well known.

Yes, that's the main point. The ambiguities are again well known
in the other scripts where they turn up.

>How can we distinguish  katakana 'ro-to.com' and hangul 'ma.com'
>if we haven't learn japanese and korean ?

Well, the main point will be spacing. There are also other font
differences. But these are made for people who write katakana or
hangul, not for those that don't.


Regards,   Martin.



From owner-idn@ops.ietf.org  Sun Jul 15 22:06:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA03352
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 22:06:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LxL1-0006l3-00
	for idn-data@psg.com; Sun, 15 Jul 2001 18:38:19 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LxL0-0006kx-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 18:38:18 -0700
Received: from enoshima (e147152.ppp.asahi-net.or.jp [211.13.147.152])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id KAA02027;
	Mon, 16 Jul 2001 10:38:18 +0900 (JST)
Message-Id: <4.2.0.58.J.20010716103555.0353add0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Mon, 16 Jul 2001 10:37:52 +0900
To: "Adam M. Costello" <amc@cs.berkeley.edu>,
        idn working group <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
In-Reply-To: <20010716003900.D8322@arwen.cs.berkeley.edu>
References: <4.2.0.58.J.20010716091901.03e09320@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 00:39 01/07/16 +0000, Adam M. Costello wrote:

>At 14:05 01/07/15 -0700, Paul Hoffman / IMC wrote:
>
> > [T]he editing interface to the host file does.  That is pretty
> > trivial: a single script that converts the native-charset file (which
> > does not have to be UTF-8: it can be any native charset) to the host
> > file.  It took me about 5 minutes to write mine in Perl (using an
> > existing ACE<=>UTF-8 routine).
>
>Martin Duerst <duerst@w3.org> replied:
>
> > That's five minutes for each different format.  And then that's a few
> > seconds every time a conversion is needed.
>
>Okay, anyone who doesn't like that method can get a DNS server that
>reads UTF-8 zone files directly (I have no doubt that such servers will
>appear)

I also have little doubt this should and will happen. But the current
IDNA draft explicitly specifies that zone files must be in ACE, and
therefore prohibits such implementations.


>and use their favorite UTF-8 capable editor to edit it.  The
>encoding used by the server on the wire is orthogonal to the zone file
>encoding.

Yes, it is. But zone files are one of the easiest places to address
in that respect. Domain names turn up in many more places. How do you
solve the problem for these?

Regards,  Martin.



From owner-idn@ops.ietf.org  Sun Jul 15 22:06:12 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA03363
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 22:06:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Lx4n-00060r-00
	for idn-data@psg.com; Sun, 15 Jul 2001 18:21:33 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Lx4m-00060i-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 18:21:32 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6G1LGQ02134
	for <idn@ops.ietf.org>; Mon, 16 Jul 2001 10:21:21 +0900 (KST)
Message-ID: <03ab01c10d96$4f8a3e40$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
References: <20010714211816.D31484@arwen.cs.berkeley.edu> <4.2.0.58.J.20010715125225.00a00dc0@sh.w3.mag.keio.ac.jp> <4.2.0.58.J.20010716084917.03df7800@sh.w3.mag.keio.ac.jp>
Subject: Re: [idn] IDN security and ACE leakage
Date: Mon, 16 Jul 2001 10:26:10 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
> >How can we distinguish  katakana 'ro-to.com' and hangul 'ma.com'
> >if we haven't learn japanese and korean ?
> 
> Well, the main point will be spacing. There are also other font
> differences. But these are made for people who write katakana or
> hangul, not for those that don't.
> 
In most cases, the problems come from the similarities, not from spacing.

katakana 'ka' and chinese letter 'power(U+529B)' look the same.
Begali numeral '4'  and latin '8' looks the same.

What if japanese or korean customers send us with their IDN-email
addresses  and we don't know japanese and korean letters and theri
spacing sematics ?

Still I cannot distinguish between Bengali numerial '4' and latin '8'.

How can we prevent malicious attempts to 
forge similiarly-looking but different domains ?



> 
> Regards,   Martin.
> 




From owner-idn@ops.ietf.org  Sun Jul 15 22:17:17 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA04551
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 22:17:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LxWL-0007IF-00
	for idn-data@psg.com; Sun, 15 Jul 2001 18:50:01 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LxWL-0007I7-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 18:50:01 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15LxWK-0002SE-00; Sun, 15 Jul 2001 18:50:00 -0700
Date: Mon, 16 Jul 2001 01:50:00 +0000
To: idn working group <idn@ops.ietf.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
Message-ID: <20010716015000.F8322@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4.2.0.58.J.20010716103555.0353add0@sh.w3.mag.keio.ac.jp>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Martin Duerst <duerst@w3.org> wrote:

> But the current IDNA draft explicitly specifies that zone files must
> be in ACE, and therefore prohibits such implementations.

Well that's just silly.  Paul and Patrick, the IDNA spec should not say
that master files must use ACE, it should say that DNS servers must
accept master files that use ACE and may also accept master files that
use other encodings, like UTF-8.

AMC



From owner-idn@ops.ietf.org  Sun Jul 15 22:23:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA05184
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 22:23:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LxN3-0006oF-00
	for idn-data@psg.com; Sun, 15 Jul 2001 18:40:25 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LxN2-0006o7-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 18:40:25 -0700
Received: from [216.153.32.19] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 161115; Sun, 15 Jul 2001 18:39:50 -0700
Message-ID: <3B5245EA.36EA04DC@ehsco.com>
Date: Sun, 15 Jul 2001 20:39:54 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Paul Hoffman / IMC <phoffman@imc.org>
CC: "Adam M. Costello" <amc@cs.berkeley.edu>, IDN <idn@ops.ietf.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
References: <20010715060009.A2136@arwen.cs.berkeley.edu>				
	 <3B51B216.33947C1B@ehsco.com> <p05100316b77769501f54@[165.227.249.20]>		
	 <3B51BDC6.E8011A76@ehsco.com> <3B51C6A2.4F5BDE90@ehsco.com>	
	 <p0510031db7777d16c4af@[165.227.249.20]> <3B51D952.BC11859B@ehsco.com>
	 <p05100321b777942a30d1@[165.227.249.20]> <3B51F3D5.23F8460F@ehsco.com> <p05100325b777b39692ae@[165.227.249.20]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Paul Hoffman / IMC wrote:
> 
> At 2:49 PM -0500 7/15/01, Eric A. Hall wrote:
> >What severe problems?
> 
> If any DNS server in the search path for a name has not been updated,
> or if the user's resolver has not been updated, the query will fail.
> That seems pretty bad, yes?

If that were actually the case, yes. The dual-mode proposal allows for the
use of ACE wherever it is required. It will work just as well as the
ACE-only approach.

The difference comes from what the user gets when they commit to the
technology and upgrade. In the ACE-only camp, they get transliteration. In
the dual-mode camp, they get transliteration and they also get direct
access to UTF8. The ACE approach restricts *ALL FUTURE ACTIVITY* to the
boat anchor that is ASCII, while the dual-mode approach lays a foundation
for a new breed of internationalized applications.

How you can oppose the obvious choice here is completely beyond me. What
exactly is the problem that this WG is trying to solve? Aren't we trying
to internationalize domain names so that apps can enjoy them? And yet you
want us to make it even *HARDER* for developers by mandating that they may
only use encrypted strings that show up nowhere else in the entire
computing universe. Outrageous.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Sun Jul 15 22:34:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA07308
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 22:34:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LxqD-0008DG-00
	for idn-data@psg.com; Sun, 15 Jul 2001 19:10:33 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LxqD-0008D8-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 19:10:33 -0700
Received: from [216.153.32.19] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 161124; Sun, 15 Jul 2001 19:09:58 -0700
Message-ID: <3B524CFB.A6F2E5DC@ehsco.com>
Date: Sun, 15 Jul 2001 21:10:03 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Adam M. Costello" <amc@cs.berkeley.edu>
CC: idn working group <idn@ops.ietf.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
References: <20010716015000.F8322@arwen.cs.berkeley.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


"Adam M. Costello" wrote:
> 
> Martin Duerst <duerst@w3.org> wrote:
> 
> > But the current IDNA draft explicitly specifies that zone files must
> > be in ACE, and therefore prohibits such implementations.
> 
> Well that's just silly.  Paul and Patrick, the IDNA spec should not say
> that master files must use ACE, it should say that DNS servers must
> accept master files that use ACE and may also accept master files that
> use other encodings, like UTF-8.

The format of a master file needs to be agreed on. This is required for
DNS to operate properly.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Sun Jul 15 22:52:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA09179
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 22:52:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ly1z-0008ms-00
	for idn-data@psg.com; Sun, 15 Jul 2001 19:22:43 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ly1y-0008md-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 19:22:42 -0700
Received: from [216.153.32.19] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 161126; Sun, 15 Jul 2001 19:22:06 -0700
Message-ID: <3B524FD3.AB782E8@ehsco.com>
Date: Sun, 15 Jul 2001 21:22:11 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Adam M. Costello" <amc@cs.berkeley.edu>
CC: IDN <idn@ops.ietf.org>
Subject: Re: [idn] proposals and deadlines
References: <20010715232459.A8322@arwen.cs.berkeley.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


"Adam M. Costello" wrote:
> 
> "Eric A. Hall" <ehall@ehsco.com> wrote:
> 
> > No, only until ACE can be deprecated.  This will happen on a per-app
> > basis where it happens, or with entirely new applications that avoid
> > using ACE altogether.  But when it happens, the app should end up
> > with a native UTF8 environment, rather than being stuck with ACE.
> 
> Okay, now let's think about this hypothetical new application that
> uses UTF-8 natively.  It uses UTF-8 to talk to its peers, and UTF-8 to
> interact with the user, data files, etc.  Absolutely everything it ever
> does with domain names uses UTF-8.  Except one thing: DNS lookups,
> which sometimes use UTF-8 and sometimes use ACE.

This hypothetical application would be written to only use UTF8. After a
certain point, it wouldn't make sense to continue writing apps for an
outdated encoding. This wouldn't happen immediately, but once there was a
sufficient installed base, why not? EG, how many new apps are being
written for 7-E-1 parity, or for punchcard storage? After some point, we
should assume that the mere presence of UTF8-encoding will result in some
new application using UTF8 alone, and not supporting a fallback to ACE.

> > Your proposal does not provide this differentiator, and allows
> > corrupt data to enter the query chain on the same footing as
> > legitimate data.
> 
> What do you think my proposal is?

  | Subject: Re: [idn] proposals and deadlines
  |    Date: Sun, 15 Jul 2001 06:00:09 +0000
  |    From: "Adam M. Costello" <amc@cs.berkeley.edu>
  |      To: IDN <idn@ops.ietf.org>

  |     ACE-encode query
  |     look up using oldAPI
  |     ACE-decode response
  | 
  | The latter is less code to write and maintain. I can't see a
  | reason why any programmer would opt for the more complex method
  | given those two choices.  I also can't think of any scenario
  | where an EDNS/UTF-8 lookup failure should not be followed by an
  | attempt with DNS/ACE.  Which means I can't think of a single
  | scenario where a programmer would want to use newAPI at all. 

When you put conversion in the resolver, the resolver will attempt to
convert data that should not be converted.

For example, there are currently applications on the market that will try
to process 8-bit data that is given to them. Because these applications
were written before nameprep, before the IDNS draft, and the other new
rules (which may or may not come about), these applications are guaranteed
to make wrong assumptions.

If this data is passed to oldAPI, and then the resolver says "oh goodie,
UTF8!", converts it to ACE and then pushes it into the query chain,
unexpected results will absolutely occur. Detrimental effects (such as
positive matches for wrong data) are likely to occur. This is particularly
true with applications that try to work with charset data from
locale-based encodings (like 8859-15) or OS-specific encodings (like
Windows-1252 or MacRoman).

Furthermore, the resolver must not perform the conversion because it
doesn't know what the application is going to do with the data. If a
resolver answered in the affirmative to a probe-test, then the application
may wrongly perform a subsequent task (such as an authentication request).

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Sun Jul 15 22:55:32 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA09546
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 22:55:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ly8l-000926-00
	for idn-data@psg.com; Sun, 15 Jul 2001 19:29:43 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ly8k-000920-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 19:29:42 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15Ly8k-0002Xu-00; Sun, 15 Jul 2001 19:29:42 -0700
Date: Mon, 16 Jul 2001 02:29:42 +0000
To: idn working group <idn@ops.ietf.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
Message-ID: <20010716022942.G8322@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B524CFB.A6F2E5DC@ehsco.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

"Eric A. Hall" <ehall@ehsco.com> wrote:

> The format of a master file needs to be agreed on.  This is required
> for DNS to operate properly.

Why?  Zone transfers use the regular binary DNS message format, not the
text master file format.  As far as I know, having a standard master
file format is not necessary for DNS to operate properly, but is a
convenience for DNS administrators because it allows them to switch to
a different server implementation without having to translate their
zone files.  Some server implementations (like BIND) support extensions
to the master file format (like $GENERATE), and DNS administrators who
use such extensions assume the risk that if they switch to a different
server implementation, those extensions might not work.  The same would
be true of an extension for supporting UTF-8.  The extension for UTF-8
might be sufficiently useful that it becomes a standard extension, like
$TTL added by RFC 2308.

AMC



From owner-idn@ops.ietf.org  Sun Jul 15 22:57:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA09778
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 22:57:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Lxqw-0008GH-00
	for idn-data@psg.com; Sun, 15 Jul 2001 19:11:18 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Lxqu-0008GA-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 19:11:17 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 2262CFFC03; Mon, 16 Jul 2001 10:13:03 +0800 (SGT)
Message-ID: <00e901c10d9c$8c55d860$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>, <iesg@ietf.org>,
        <poised@lists.tislabs.com>
References: <E15LLxX-000G18-00@psg.com> <20010714211816.D31484@arwen.cs.berkeley.edu> <20010715203004.30572.qmail@cr.yp.to>
Subject: Re: [idn] UTF-8 as the long-term IDN solution
Date: Mon, 16 Jul 2001 10:10:56 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I believe that the IDN WG has consensus on the following point: ``The
> long-term IDN solution will encode Unicode characters as UTF-8 on the
> wire.'' I find the other possibilities absurd, and I am dismayed at
the
> amount of time that has been wasted discussing them on the IDN list.

I speak for myself in this note. (Marc may have different opinion)

The working groups works based on ideas documented in internet drafts
and not a broad statement/claim.

> On 2001-05-29 I requested that the the IDN WG chairs run a poll to see
> whether we do, in fact, have consensus on this point.
>
> ``I would like to hear some support on this before we run this poll,''
> James Seng said, speaking as chair.
>
> He promptly heard some support, but he did not run the poll. I asked
why
> the chairs were not running the poll. There was no response.

First, there is a response: I requested you to point to an internet
draft which you are referring or write a draft yourself.

Secondly, strawpoll are not fun events which we conduct -- it is very
time-consuming. Surprisingly, I still have a day-time job.

Thirdly, strawpoll are useful, but not neccessary, when the chairs wants
to know if there is a consensus on a particular *draft*.

And last, but not the least, there is a existing announced process to
split the wg drafts into Pool W for drafts with 7 supporters and Pool T
for others. If you strongly feel about your idea, please write a draft,
gather 7 supporters, then come back to the working group with your
draft.

> I accuse the chairs of bias in their selection of polls. They appear
to
> be running polls that they believe will promote their personal
agendas,
> and refusing to run any other polls. Does the IETF have any procedures
> to fix this problem?

You are free to form any conspiracy theory you like in your personal
thoughts. But making these theory into public statement requires
substained evidences.

If anyone feels the wg chairs is act inappropriatly, a private note to
IESG would usually do the job. Given that a number of IESG and IAB
members are on this list, any wrongdoing would be note almost
immediately.

Once in a while, certain individual in the wg have louder voice than
others and repeat his opinion often enough. Fortunately, the IETF
process does not guage consensus based on decibel level or number of
emails sent. Instead, we work on Internet Drafts and consensus, ie. each
and every wg members' views are taken into consideration. A louder voice
does not make anyone more important than others.

And the wg chairs are here to assist the process, not to conduct
strawpoll for individual whims. Thank you.

-James Seng




From owner-idn@ops.ietf.org  Sun Jul 15 23:31:18 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA13734
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 23:31:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Lyh2-000AZw-00
	for idn-data@psg.com; Sun, 15 Jul 2001 20:05:08 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Lyh1-000AZX-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 20:05:07 -0700
Received: from [216.153.32.19] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 161133; Sun, 15 Jul 2001 20:04:33 -0700
Message-ID: <3B5259C4.483F3797@ehsco.com>
Date: Sun, 15 Jul 2001 22:04:37 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Adam M. Costello" <amc@cs.berkeley.edu>
CC: idn working group <idn@ops.ietf.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
References: <20010716022942.G8322@arwen.cs.berkeley.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


"Adam M. Costello" wrote:
> 
> "Eric A. Hall" <ehall@ehsco.com> wrote:
> 
> > The format of a master file needs to be agreed on.  This is required
> > for DNS to operate properly.
> 
> Why?  Zone transfers use the regular binary DNS message format, not the
> text master file format.  As far as I know, having a standard master
> file format is not necessary for DNS to operate properly, but is a
> convenience for DNS administrators because it allows them to switch to
> a different server implementation without having to translate their
> zone files.

The master file is separate from the database. While the use of a common
master file format does make switching convenient, the primary purpose is
to ensure that a zone *can* be moved. People who are moving servers or
recovering from a crash or whatever will email the master file to some
other admin or server, and will expect it to function.

RFC 1035 discusses the master file in several contexts -- not just as the
database -- meaning that it's an integrated part of the spec.

Finally, RFC 1034 says that zone transfers are the "preferred" method but
not the only method to move zones around:

  | 4.3.5. Zone maintenance and transfers
  | 
  | Part of the job of a zone administrator is to maintain the zones
  | at all of the name servers which are authoritative for the zone.
  | When the inevitable changes are made, they must be distributed
  | to all of the name servers.  While this distribution can be
  | accomplished using FTP or some other ad hoc procedure, the
  | preferred method is the zone transfer part of the DNS protocol.

It is legal to use FTP or rdist or anything else to move master files
around. Their format must be known for this to work.

My thinking is that master files for IDNs must be in UTF-8. This ensures
that an authoritative server cannot be upgraded without all of the servers
being upgraded simultaneously. Since all of the servers have to speak
UTF-8, they all need to be upgraded at roughly the same time.

Note that this MUST would be hollow; all of the servers could still run in
cripple-mode by using ACE with the legacy APIs.

But I am sure to get flamed for this anyway.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Sun Jul 15 23:35:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA14783
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 23:35:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Lyoi-000AmT-00
	for idn-data@psg.com; Sun, 15 Jul 2001 20:13:04 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15Lyog-000Am2-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 20:13:02 -0700
Received: (qmail 22448 invoked by uid 1001); 16 Jul 2001 03:13:18 -0000
Date: 16 Jul 2001 03:13:18 -0000
Message-ID: <20010716031318.8723.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org,
  iesg@ietf.org,
  poised@lists.tislabs.com
Automatic-Copyright-Notice: Copyright 2001, D. J. Bernstein. My transmission of this message to you does not constitute a copyright waiver or any other limitation of my rights, even if you have told me otherwise.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org, iesg@ietf.org, poised@lists.tislabs.com
Subject: Re: [idn] UTF-8 as the long-term IDN solution
References: <E15LLxX-000G18-00@psg.com> <20010714211816.D31484@arwen.cs.berkeley.edu> <20010715203004.30572.qmail@cr.yp.to> <00e901c10d9c$8c55d860$dd00a8c0@jamessonyvaio>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James Seng/Personal writes:
> I requested you to point to an internet draft

Your request is noted.

In the meantime, please run the poll. A two-week poll will leave enough
time for people to get back from vacation. The agree/disagree statement,
as I've told you repeatedly, is as follows: ``The long-term IDN solution
will encode Unicode characters as UTF-8 on the wire.''

I think we have consensus on this one aspect of what's going to happen.
If I'm right, then we can stop wasting time discussing silly ACE-forever
scenarios that aren't going to happen. Please stop stonewalling.

> strawpoll for individual whims

Excuse me? Many people have announced their support for UTF-8 as the
long-term solution. Only a few people have objected. When you stalled by
saying ``I would like to hear some support on this before we run this
poll,'' you immediately saw some public messages of support. For
example, here's what Bruce Thomson said:

   It is likely that we have consensus on this point, and it would be
   well worth the effort of a straw poll to establish this, so we can
   move on.

How you can call this an ``individual whim'' is beyond me.

---Dan



From owner-idn@ops.ietf.org  Sun Jul 15 23:37:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA15083
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 23:37:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Lz68-000BXU-00
	for idn-data@psg.com; Sun, 15 Jul 2001 20:31:04 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Lz62-000BXG-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 20:30:58 -0700
Received: from enoshima (e147152.ppp.asahi-net.or.jp [211.13.147.152])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id MAA02344;
	Mon, 16 Jul 2001 12:30:58 +0900 (JST)
Message-Id: <4.2.0.58.J.20010716093644.03df9790@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Mon, 16 Jul 2001 12:30:29 +0900
To: "Adam M. Costello" <amc@cs.berkeley.edu>, IDN <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
In-Reply-To: <20010716003214.C8322@arwen.cs.berkeley.edu>
References: <4.2.0.58.J.20010716085702.03e95c90@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 00:32 01/07/16 +0000, Adam M. Costello wrote:
>Martin Duerst <duerst@w3.org> wrote:
>
> > In HTML 4.0, there is a provision that says that URIs that contain
> > non-ASCII characters should be interpreted based on conversion to
> > UTF-8
> >
> > The Web and the W3C took RFC 2277 seriously.  We are ready for UTF-8,
> > we don't need ACE at all.
>
>Not quite.  HTML 4.01 still says that URIs are defined by RFC 2396.  So
>consider href="http://IDN.com/foo/".  The provision you mention will
>convert it to http://%HH%HH%HH.com/foo/, but that's not a syntactically
>valid URI according to RFC 2396, which says the host part can contain
>only letters, digits, hyphens, and dots, not percent signs.

Yes. I already have written a draft to do the necessary update.
Please see http://search.ietf.org/internet-drafts/draft-ietf-idn-uri-00.txt.
And the philosophy of URIs is that you don't check more than necessary,
and many applications do that.


>And nowhere
>does the HTML spec say that the %HH encoding should not be used on the
>host part

Yes, on purpose. The U in URI stands for Uniform (among else).


>(or should be undone before the name is looked up).

That's not the business of the HTML spec, obviously.


Regards,   Martin.




From owner-idn@ops.ietf.org  Sun Jul 15 23:41:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA16103
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 23:41:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Lz1G-000BNW-00
	for idn-data@psg.com; Sun, 15 Jul 2001 20:26:02 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Lz1G-000BNQ-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 20:26:02 -0700
Received: from [165.227.249.20] (ip20.proper.com [165.227.249.20])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f6G3Piq07547;
	Sun, 15 Jul 2001 20:25:44 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100331b7780e02d13e@[165.227.249.20]>
In-Reply-To: <3B524CFB.A6F2E5DC@ehsco.com>
References: <20010716015000.F8322@arwen.cs.berkeley.edu>
 <3B524CFB.A6F2E5DC@ehsco.com>
Date: Sun, 15 Jul 2001 20:24:49 -0700
To: "Eric A. Hall" <ehall@ehsco.com>, "Adam M. Costello" <amc@cs.berkeley.edu>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
Cc: idn working group <idn@ops.ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 9:10 PM -0500 7/15/01, Eric A. Hall wrote:
>The format of a master file needs to be agreed on. This is required for
>DNS to operate properly.

There is a *large* amount of disagreement here. The fact that the 
zone file was made standard by RFC 1034/1035 does not mean it is 
needed. Nothing exchanges zone files, so there is no interoperational 
impact.

Further, even if you wanted to have a standard zone file format, you 
can create precursors to the zone file in any format. It could be a 
text file in UTF-8, a text file in GB, a bunch of dialog boxes, an 
SQL database, and so on. (All of those are already in use today.) 
Quite frankly, I doubt that many non-BIND DNS systems create 
compliant zone files from their much-friendlier input formats unless 
you ask them to.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Sun Jul 15 23:49:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA17692
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 23:49:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LzAc-000Bs9-00
	for idn-data@psg.com; Sun, 15 Jul 2001 20:35:42 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LzAb-000Bs2-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 20:35:41 -0700
Received: from [216.153.32.19] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 161141; Sun, 15 Jul 2001 20:35:07 -0700
Message-ID: <3B5260EF.8D872029@ehsco.com>
Date: Sun, 15 Jul 2001 22:35:12 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Adam M. Costello" <amc@cs.berkeley.edu>
CC: idn@ops.ietf.org
Subject: Re: [idn] Reality Check
References: <20010716001319.B8322@arwen.cs.berkeley.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


"Adam M. Costello" wrote:

> I think we have consensus on "New protocols should use UTF-8 for
> hostnames."  We might have strong support for "Existing application
> protocols should try to migrate toward UTF-8."  I don't think there is
> anything approaching consensus on "ACE will eventually be eradicated
> from all protocols."

I concur on this assessment, even though the third point weakens my
arguments. Some protocols which are dead and buried are very unlikely to
be upgraded.

As an aside, it is possible to upgrade many of the legacy protocols to
UTF-8 without actually changing the protocol semantics, simply by using
out-of-band negotation features. Finger, Echo, Gopher, etc., all of them
could be upgraded. Not by this WG of course, but the work that this WG
performs will dictate how that work eventually happens.

For example, if there's an out-of-band negotiation for "use UTF-8" that is
glued onto finger, then the output can be internationalized, but the query
inputs will also need to be internationalized for maximum functionality.
This will include IDNs (with Finger in particular).

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Sun Jul 15 23:52:54 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA18380
	for <idn-archive@lists.ietf.org>; Sun, 15 Jul 2001 23:52:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Lz7A-000Bak-00
	for idn-data@psg.com; Sun, 15 Jul 2001 20:32:08 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15Lz7A-000BaL-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 20:32:08 -0700
Received: (qmail 25911 invoked by uid 1001); 16 Jul 2001 03:32:23 -0000
Date: 16 Jul 2001 03:32:23 -0000
Message-ID: <20010716033223.2513.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
Automatic-Copyright-Notice: Copyright 2001, D. J. Bernstein. My transmission of this message to you does not constitute a copyright waiver or any other limitation of my rights, even if you have told me otherwise.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] Why follow IDNA with UTF-8?
References: <20010715060009.A2136@arwen.cs.berkeley.edu> <3B51B216.33947C1B@ehsco.com> <p05100316b77769501f54@[165.227.249.20]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Paul Hoffman / IMC writes:
> Can you list the advantages to the end users that deprecating ACE will have?

I already answered this in May:

: Consider a programmer writing network software five years from now, or
: ten years from now.
:
: He'll be working with text in UTF-8. But wait, you say, he has to
: convert to some screwy ACE format on the wire. When he asks why all the
: Internet protocols have this strange complication, you mumble something
: about ancient versions of Sendmail that didn't support 8-bit text.
:
: So he'll have to deal with ACE, taking time away from implementing new
: features that users actually want.
:
: You should be ashamed of yourself.

---Dan



From owner-idn@ops.ietf.org  Mon Jul 16 00:24:25 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA24838
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 00:24:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Lzko-000DgZ-00
	for idn-data@psg.com; Sun, 15 Jul 2001 21:13:06 -0700
From: Steve Atkins <steve@blighty.com>
To: idn@ops.ietf.org
Subject: Re: [idn] Why follow IDNA with UTF-8?
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15Lzko-000DgZ-00@psg.com>
Date: Sun, 15 Jul 2001 21:13:06 -0700

On Sun, Jul 15, 2001 at 09:10:03PM -0500, Eric A. Hall wrote:
> "Adam M. Costello" wrote:
> >
> > Martin Duerst <duerst@w3.org> wrote:
> >
> > > But the current IDNA draft explicitly specifies that zone files
must
> > > be in ACE, and therefore prohibits such implementations.
> >
> > Well that's just silly.  Paul and Patrick, the IDNA spec should not
say
> > that master files must use ACE, it should say that DNS servers must
> > accept master files that use ACE and may also accept master files
that
> > use other encodings, like UTF-8.
>
> The format of a master file needs to be agreed on. This is required
for
> DNS to operate properly.

Uhm, no.

Please don't suggest repeating the bind-centric mistakes in the current
set of DNS RFCs.

Master file format is just an implementation detail. It can easily
differ
from one implementation to another.

Cheers,
  Steve
>From steve@blighty.COM Sun Jul 15 20:45:08 2001
Received: from vix.samspade.org ([204.152.186.148] helo=blighty.com)
by psg.com with esmtp (Exim 3.31 #1)
id 15LzJk-000CLd-00
for idn@ops.ietf.org; Sun, 15 Jul 2001 20:45:08 -0700
Received: by blighty.com (Postfix, from userid 1000)
id 5A5C2634; Sun, 15 Jul 2001 21:09:01 -0700 (PDT)
Date: Sun, 15 Jul 2001 21:09:01 -0700
From: Steve Atkins <steve@blighty.com>
To: idn@ops.ietf.org
Subject: Re: [idn] Why follow IDNA with UTF-8?
Message-ID: <20010715210901.A93700@blighty.com>
References: <20010716015000.F8322@arwen.cs.berkeley.edu>
<3B524CFB.A6F2E5DC@ehsco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3B524CFB.A6F2E5DC@ehsco.com>; from ehall@ehsco.com on Sun,
Jul 15, 2001 at 09:10:03PM -0500

On Sun, Jul 15, 2001 at 09:10:03PM -0500, Eric A. Hall wrote:
> "Adam M. Costello" wrote:
> >
> > Martin Duerst <duerst@w3.org> wrote:
> >
> > > But the current IDNA draft explicitly specifies that zone files
must
> > > be in ACE, and therefore prohibits such implementations.
> >
> > Well that's just silly.  Paul and Patrick, the IDNA spec should not
say
> > that master files must use ACE, it should say that DNS servers must
> > accept master files that use ACE and may also accept master files
that
> > use other encodings, like UTF-8.
>
> The format of a master file needs to be agreed on. This is required
for
> DNS to operate properly.

Uhm, no.

Please don't suggest repeating the bind-centric mistakes in the current
set of DNS RFCs.

Master file format is just an implementation detail. It can easily
differ
from one implementation to another.

Cheers,
  Steve




From owner-idn@ops.ietf.org  Mon Jul 16 01:00:12 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA24842
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 00:24:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Lzli-000DjC-00
	for idn-data@psg.com; Sun, 15 Jul 2001 21:14:03 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Lzli-000Diy-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 21:14:02 -0700
Received: from [216.153.32.111] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 161147; Sun, 15 Jul 2001 21:13:27 -0700
Message-ID: <3B5269EB.5E9999B7@ehsco.com>
Date: Sun, 15 Jul 2001 23:13:31 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Adam M. Costello" <amc@cs.berkeley.edu>, IDN <idn@ops.ietf.org>
Subject: Re: [idn] proposals and deadlines
References: <20010716024235.H8322@arwen.cs.berkeley.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


"Adam M. Costello" wrote:
> 
> "Eric A. Hall" <ehall@ehsco.com> wrote:
> 
> > If this [8-bit] data is passed to oldAPI, and then the resolver says
> > "oh goodie, UTF8!", converts it to ACE and then pushes it into the
> > query chain, unexpected results will absolutely occur.
> 
> Indeed.  But in my previous message I explicitly stated that I don't
> want the resolver to perform ACE transformations for calls to the old
> API.  I want the old API to continue to function just like it does
> today.  I would have the resolver perform ACE transformations only in
> conjuction with the new API.

Well then, you are halfway there. :)

> > Furthermore, the resolver must not perform the conversion because it
> > doesn't know what the application is going to do with the data.  If
> > a resolver answered in the affirmative to a probe-test, then the
> > application may wrongly perform a subsequent task (such as an
> > authentication request).
> 
> As long as the resolver and the application agree on the semantics of
> the new API, there is no problem.  The semantics I propose for the new
> resolver API are: "Please take this UTF-8 query and do your best to
> give me back a UTF-8 response, using any DNS versions/extensions you
> please."

This would break things that rely on the domain name being preserved. With
X.509 the client and the server have to agree on the domain name, for
example. If the resolver recombobulates a UTF-8 domain name from ACE
output, then the client and server are likely to have different ideas of
what the domain name should be.

One of the benefits to the dual-usage approach is that it is possible to
store raw ACE strings as UTF-8 strings. This means that the client and
server can use the new API to successfully resolve a legacy domain name
which has been manually encoded and stored as raw ACE data. This keeps
this kind of stuff from breaking.

and all for the low, low price of a wee bit of extra memory

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Mon Jul 16 01:12:20 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA05688
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 01:12:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15M0Uv-000Frs-00
	for idn-data@psg.com; Sun, 15 Jul 2001 22:00:45 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15M0Us-000For-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 22:00:43 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6G4xhp18281
	for <idn@ops.ietf.org>; Mon, 16 Jul 2001 13:59:47 +0900 (KST)
Message-ID: <003501c10db4$f8d70500$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Subject: Re: [idn] IDN security and ACE leakage
Date: Mon, 16 Jul 2001 14:05:41 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I think ACE is convenient utf8-replacement to improve  universal
verifiability of  internet identifiers, since it can be restored to
 its utf8 (sometimes undisplayable or unrecognizable or
 undistinguishable) string and also provides ascii compatible 
(ugly but always verifiable ) labels while assuring backward 
compatiblities to existing DNS infrastructures.

We cannot enforce all the peoples in the world to learn every 
scripts/glyphs in unicode code charts. 
They are not all geniuses for languages.

I believe ACE will  be not deprecated and will remain forever as an
auxiliary common-denominator display format of internet 
identifiers as well as one of viable zone file formats and 
wire formats.  shorter ACE labels always benefit.

ACE is another "utf-8" for identifiers, not an inferior interim 
encoding. It deserves its overhead for improving  identifier  security.

Soobok Lee

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Sent: Monday, July 16, 2001 10:26 AM
Subject: Re: [idn] IDN security and ACE leakage


>
> ----- Original Message -----
> From: "Martin Duerst" <duerst@w3.org>
> > >How can we distinguish  katakana 'ro-to.com' and hangul 'ma.com'
> > >if we haven't learn japanese and korean ?
> >
> > Well, the main point will be spacing. There are also other font
> > differences. But these are made for people who write katakana or
> > hangul, not for those that don't.
> >
> In most cases, the problems come from the similarities, not from spacing.
>
> katakana 'ka' and chinese letter 'power(U+529B)' look the same.
> Bengali numeral '4'  and latin '8' look the same.
>
> What if japanese or korean customers send us with their IDN-email
> addresses  and we don't know japanese and korean letters and their
> spacing semantics ?
>
> Still I cannot distinguish between Bengali numeral '4' and latin '8'.
>
> How can we prevent malicious attempts to
> forge similiarly-looking but different domains ?
>
>
>
> >
> > Regards,   Martin.
> >
>






From owner-idn@ops.ietf.org  Mon Jul 16 01:15:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA06810
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 01:15:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15LzuC-000EA1-00
	for idn-data@psg.com; Sun, 15 Jul 2001 21:22:48 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15LzuA-000E9t-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 21:22:47 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 58492FFC03; Mon, 16 Jul 2001 12:24:39 +0800 (SGT)
Message-ID: <021a01c10dae$eeb3dcc0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>, <iesg@ietf.org>,
        <poised@lists.tislabs.com>
References: <E15LLxX-000G18-00@psg.com> <20010714211816.D31484@arwen.cs.berkeley.edu> <20010715203004.30572.qmail@cr.yp.to> <00e901c10d9c$8c55d860$dd00a8c0@jamessonyvaio> <20010716031318.8723.qmail@cr.yp.to>
Subject: Re: [idn] UTF-8 as the long-term IDN solution
Date: Mon, 16 Jul 2001 12:22:31 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Pardon me, but I have to eat my own words. I do not think running a
strawpoll based on a broad statement as you proposed is useful to the
process.

It would be more appropriate when you have an draft (or point to a draft
which you support) and if there is sufficient support for that draft, a
strawpoll maybe conducted to evaluate consensus.

Strawpoll is useful tool for wg chairs to guage consensus of a draft
when the chairs is unable to determine consensus within the group. It is
not an "voting tool" for a statement. Neither is it actually neccessary
for any process so long the chairs can determine consensus.

Using it as an affirmation of a statement as you request would be
abusing the strawpoll. It is not only time-consuming, it is also a waste
of time for wg members if it is not neccessary.

ps: speaking for myself again, I can say it is not neccessary because I
have suspected there is some agreement (given the discussion of UTF-8 in
the wg) with your statement already. Nevertheless, the wg cannot proceed
based on ideas, we need drafts.

-James Seng

----- Original Message -----
From: "D. J. Bernstein" <djb@cr.yp.to>
To: <idn@ops.ietf.org>; <iesg@ietf.org>; <poised@lists.tislabs.com>
Sent: Monday, July 16, 2001 11:13 AM
Subject: Re: [idn] UTF-8 as the long-term IDN solution


> James Seng/Personal writes:
> > I requested you to point to an internet draft
>
> Your request is noted.
>
> In the meantime, please run the poll. A two-week poll will leave
enough
> time for people to get back from vacation. The agree/disagree
statement,
> as I've told you repeatedly, is as follows: ``The long-term IDN
solution
> will encode Unicode characters as UTF-8 on the wire.''
>
> I think we have consensus on this one aspect of what's going to
happen.
> If I'm right, then we can stop wasting time discussing silly
ACE-forever
> scenarios that aren't going to happen. Please stop stonewalling.
>
> > strawpoll for individual whims
>
> Excuse me? Many people have announced their support for UTF-8 as the
> long-term solution. Only a few people have objected. When you stalled
by
> saying ``I would like to hear some support on this before we run this
> poll,'' you immediately saw some public messages of support. For
> example, here's what Bruce Thomson said:
>
>    It is likely that we have consensus on this point, and it would be
>    well worth the effort of a straw poll to establish this, so we can
>    move on.
>
> How you can call this an ``individual whim'' is beyond me.
>
> ---Dan
>




From owner-idn@ops.ietf.org  Mon Jul 16 01:50:12 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA17794
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 01:50:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15M13i-000HFX-00
	for idn-data@psg.com; Sun, 15 Jul 2001 22:36:42 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15M13h-000HFO-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 22:36:41 -0700
Received: from enoshima (dhcp-100-151.mag.keio.ac.jp [133.27.195.151])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id OAA02663;
	Mon, 16 Jul 2001 14:36:37 +0900 (JST)
Message-Id: <4.2.0.58.J.20010716143102.038bd920@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Mon, 16 Jul 2001 14:36:15 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] IDN security and ACE leakage
In-Reply-To: <003501c10db4$f8d70500$ed1bd9d2@postel.co.kr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 14:05 01/07/16 +0900, Soobok Lee wrote:
>We cannot enforce all the peoples in the world to learn every
>scripts/glyphs in unicode code charts.
>They are not all geniuses for languages.

Agreed. It is impossible to require e.g. from average
Koreans or Japanese to be able to use Arabic domain names,
exactly the same way it is impossible to ask them to
read an Arabic newspaper or an Arabic email or web page.

ACE is a very bad fallback for all these purposes.
Ideally, every person should at least have one purely
ASCII-only email address, and every machine should have
at least one purely ASCII-only domain name, not consisting
of characters that look like they come from a random generator.


Regards,   Martin.



From owner-idn@ops.ietf.org  Mon Jul 16 01:57:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA20187
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 01:57:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15M0ht-000GNX-00
	for idn-data@psg.com; Sun, 15 Jul 2001 22:14:09 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.31 #1)
	id 15M0hs-000GNO-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 22:14:09 -0700
Received: (qmail 5242 invoked from network); 16 Jul 2001 12:30:00 -0000
Received: from chubby.internal.realnames.com (HELO heaven.internal.realnames.com) (10.1.5.39)
  by friendly.realnames.com with SMTP; 16 Jul 2001 12:30:00 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:1300]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <247401@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Sun, 15 Jul 2001 10:12:22 PM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2650.21)
	id <3M50TLCQ>; Sun, 15 Jul 2001 22:13:41 -0700
Message-ID: <B7233BD6980AD411875700508B5BD5D2011E9658@elporto.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: "'idn@ops.ietf.org'" <idn@ops.ietf.org>
Subject: [idn] Should we add U+FF0E FULLWIDTH FULL STOP to section 5.10 of Namep
	rep?
Date: Sun, 15 Jul 2001 22:13:41 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hi,

I am not a Chinese expert myself, but have been told that it is quite likely
that U+FF0E would be generated instead of U+002E FULL STOP using a Chinese
IME, in a context where both ideographs and Roman characters were in close
proximity. This sounds defintely likely to happen if you have <CHINESE>.COM
for example where <CHINESE> is made up of Han characters. If that is really
the case, it could be useful to put U+FF0E in the same bag as U+3002 is in
Nameprep.

YA

PS: here's what someone I work with sent me on this topic (along with an
explanation on how easy it is to generate U+FF0E rather than U+002E while
typing mixed Chinese and Roman on MS Windows):

A plain Chinese user would use double wide roman characters in a context
containing both ideographs and roman characters in close proximity,
that's what my Chinese speaking coworkers tell me.

I find evidence that double wide punctuation is used in ideograph
dominated context, strangely even when embedded between single-wide
roman:
http://surf.sina.com.cn/cgi-bin/newlogin/regentry.cgi, near "Altavista"
or 
http://www.taiwan.com/info_10.htm, near "Cookies".

You can see clearly on sina.com or any other Chinese site that double
wide punctuation is used exclusively in ideograph context.




From owner-idn@ops.ietf.org  Mon Jul 16 02:00:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA21824
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 02:00:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15M16L-000HR8-00
	for idn-data@psg.com; Sun, 15 Jul 2001 22:39:25 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15M16K-000HR2-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 22:39:24 -0700
Received: from enoshima (dhcp-100-151.mag.keio.ac.jp [133.27.195.151])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id OAA02671;
	Mon, 16 Jul 2001 14:39:38 +0900 (JST)
Message-Id: <4.2.0.58.J.20010716143627.0389f710@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Mon, 16 Jul 2001 14:39:16 +0900
To: Yves Arrouye <yves@realnames.com>, "'idn@ops.ietf.org'" <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Should we add U+FF0E FULLWIDTH FULL STOP to section
  5.10 of Nameprep?
In-Reply-To: <B7233BD6980AD411875700508B5BD5D2011E9658@elporto.internal.
 realnames.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I haven't checked the details on this, but 'full-width period'
is definitely also used in Japanese, in particular for horizontal
writing. But having it appear between half-width Latin characters
is most probably an accident.

Regards,   Martin.


At 22:13 01/07/15 -0700, Yves Arrouye wrote:
>Hi,
>
>I am not a Chinese expert myself, but have been told that it is quite likely
>that U+FF0E would be generated instead of U+002E FULL STOP using a Chinese
>IME, in a context where both ideographs and Roman characters were in close
>proximity. This sounds defintely likely to happen if you have <CHINESE>.COM
>for example where <CHINESE> is made up of Han characters. If that is really
>the case, it could be useful to put U+FF0E in the same bag as U+3002 is in
>Nameprep.
>
>YA
>
>PS: here's what someone I work with sent me on this topic (along with an
>explanation on how easy it is to generate U+FF0E rather than U+002E while
>typing mixed Chinese and Roman on MS Windows):
>
>A plain Chinese user would use double wide roman characters in a context
>containing both ideographs and roman characters in close proximity,
>that's what my Chinese speaking coworkers tell me.
>
>I find evidence that double wide punctuation is used in ideograph
>dominated context, strangely even when embedded between single-wide
>roman:
>http://surf.sina.com.cn/cgi-bin/newlogin/regentry.cgi, near "Altavista"
>or
>http://www.taiwan.com/info_10.htm, near "Cookies".
>
>You can see clearly on sina.com or any other Chinese site that double
>wide punctuation is used exclusively in ideograph context.
>




From owner-idn@ops.ietf.org  Mon Jul 16 02:09:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA00941
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 02:09:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15M1Sf-000IY2-00
	for idn-data@psg.com; Sun, 15 Jul 2001 23:02:29 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15M1Sd-000IXv-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 23:02:28 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6G61Op02547;
	Mon, 16 Jul 2001 15:02:10 +0900 (KST)
Message-ID: <004e01c10dbd$b0455b80$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <4.2.0.58.J.20010716143102.038bd920@sh.w3.mag.keio.ac.jp>
Subject: Re: [idn] IDN security and ACE leakage
Date: Mon, 16 Jul 2001 15:06:12 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I believe IDN is not only for local use, but also
for international exchange of identities and infor-
mations. I  believe most of them will surely use 
only IDN email addresses.

Enforcing dual email addresses 
(one using LDH domain and the other using IDN ) 
may be a (costly) remedy for such situations.

How can we enforce them?  Is it possible ?
How can they decide when and to whom they
should choose IDN email addresses over LDH ones?

They may   inadvertently or intentionally 
send emails using their Arabic email addresses 
while email contents are  in english or japanese.

Soobok Lee

----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
Sent: Monday, July 16, 2001 2:36 PM
Subject: Re: [idn] IDN security and ACE leakage


> At 14:05 01/07/16 +0900, Soobok Lee wrote:
> >We cannot enforce all the peoples in the world to learn every
> >scripts/glyphs in unicode code charts.
> >They are not all geniuses for languages.
> 
> Agreed. It is impossible to require e.g. from average
> Koreans or Japanese to be able to use Arabic domain names,
> exactly the same way it is impossible to ask them to
> read an Arabic newspaper or an Arabic email or web page.
> 
> ACE is a very bad fallback for all these purposes.
> Ideally, every person should at least have one purely
> ASCII-only email address, and every machine should have
> at least one purely ASCII-only domain name, not consisting
> of characters that look like they come from a random generator.
> 
> 
> Regards,   Martin.
> 




From owner-idn@ops.ietf.org  Mon Jul 16 03:07:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA12394
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 03:07:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15M1oB-000JIy-00
	for idn-data@psg.com; Sun, 15 Jul 2001 23:24:43 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15M1o8-000JIW-00
	for idn@ops.ietf.org; Sun, 15 Jul 2001 23:24:41 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6G6ODp19141;
	Mon, 16 Jul 2001 15:24:16 +0900 (KST)
Message-ID: <005c01c10dc0$c5f2f340$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Yves Arrouye" <yves@realnames.com>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <4.2.0.58.J.20010716143627.0389f710@sh.w3.mag.keio.ac.jp>
Subject: Re: [idn] Should we add U+FF0E FULLWIDTH FULL STOP to section  5.10 of Nameprep?
Date: Mon, 16 Jul 2001 15:30:11 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

FULLWIDTH FULLSTOP(U+FF0E) is already compatibility decomposed into
Latin FULLSTOP (U+002E)  in KC Normalization step in NAMEPREP.
You can confirm that in page 4 of
http://www.unicode.org/charts/PDF/UFF00.pdf .

If any label contains U+ff0e to be mapped into u+002e in kc norm in
nameprep,
it will be treated as error  in the following prohibition stage in nameprep
, since
u+002E. is prohibited.

MDNkit from JPNIC has huge tables for that  compatibility/canonical
mappings for all unicode points.

   1694   11778   73804 nameprepdata.c
   6806   38573  327222 unicodedata.c
   8500   50351  401026 total

Soobok Lee

----- Original Message -----
From: "Martin Duerst" <duerst@w3.org>
To: "Yves Arrouye" <yves@realnames.com>; <idn@ops.ietf.org>
Sent: Monday, July 16, 2001 2:39 PM
Subject: Re: [idn] Should we add U+FF0E FULLWIDTH FULL STOP to section 5.10
of Nameprep?


> I haven't checked the details on this, but 'full-width period'
> is definitely also used in Japanese, in particular for horizontal
> writing. But having it appear between half-width Latin characters
> is most probably an accident.
>
> Regards,   Martin.
>
>
> At 22:13 01/07/15 -0700, Yves Arrouye wrote:
> >Hi,
> >
> >I am not a Chinese expert myself, but have been told that it is quite
likely
> >that U+FF0E would be generated instead of U+002E FULL STOP using a
Chinese
> >IME, in a context where both ideographs and Roman characters were in
close
> >proximity. This sounds defintely likely to happen if you have
<CHINESE>.COM
> >for example where <CHINESE> is made up of Han characters. If that is
really
> >the case, it could be useful to put U+FF0E in the same bag as U+3002 is
in
> >Nameprep.
> >
> >YA
> >
> >PS: here's what someone I work with sent me on this topic (along with an
> >explanation on how easy it is to generate U+FF0E rather than U+002E while
> >typing mixed Chinese and Roman on MS Windows):
> >
> >A plain Chinese user would use double wide roman characters in a context
> >containing both ideographs and roman characters in close proximity,
> >that's what my Chinese speaking coworkers tell me.
> >
> >I find evidence that double wide punctuation is used in ideograph
> >dominated context, strangely even when embedded between single-wide
> >roman:
> >http://surf.sina.com.cn/cgi-bin/newlogin/regentry.cgi, near "Altavista"
> >or
> >http://www.taiwan.com/info_10.htm, near "Cookies".
> >
> >You can see clearly on sina.com or any other Chinese site that double
> >wide punctuation is used exclusively in ideograph context.
> >
>
>




From owner-idn@ops.ietf.org  Mon Jul 16 03:51:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA19666
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 03:51:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15M32I-000MXz-00
	for idn-data@psg.com; Mon, 16 Jul 2001 00:43:22 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15M32G-000MXt-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 00:43:20 -0700
Received: from .q.j.tw ([140.115.5.16])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f6G7l4701913;
	Mon, 16 Jul 2001 15:47:05 +0800 (CST)
Message-ID: <002701c10dc2$34b9e8a0$1005738c@q.j.tw>
From: "tsenglm" <tsenglm@cc.ncu.edu.tw>
To: <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>
References: <20010716.002716.-616801.0.liana.ydisg@juno.com>
Subject: Re: [idn] draft about <draft-ietf-idn-uname-01.txt>
Date: Mon, 16 Jul 2001 14:40:29 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

----- Original Message ----- 
From: <liana.ydisg@juno.com>
To: <tsenglm@cc.ncu.edu.tw>
Cc: <liana.ydisg@juno.com>
Sent: Monday, July 16, 2001 3:27 PM
Subject: Re: [idn] draft about <draft-ietf-idn-uname-01.txt>


> Hi, 
>   What is the relationship between the intermdiate server
> you are proposing and [nameprep]?  My guess is before
> [nameprep], is this correct? Otherwise, is it possible to leak 
        The nameprep can be done before any LDH-DNS/resolver query.
If the intermediate server or ML-DNS directory server are not using the
LDH-DNS  tree ,  then there are no relationship with leakage to LDH-DNS
server.
> out two bytes characters into DNS directory?  Or am I missing
> something here?
> 
> Liana
> 




From owner-idn@ops.ietf.org  Mon Jul 16 05:52:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA02616
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 05:52:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15M4ne-00017e-00
	for idn-data@psg.com; Mon, 16 Jul 2001 02:36:22 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15M4nd-00017Y-00; Mon, 16 Jul 2001 02:36:21 -0700
Received: from enoshima (dhcp-100-151.mag.keio.ac.jp [133.27.195.151])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id SAA03424;
	Mon, 16 Jul 2001 18:35:57 +0900 (JST)
Message-Id: <4.2.0.58.J.20010716182210.03489820@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Mon, 16 Jul 2001 18:32:55 +0900
To: (Recipient list suppressed)
From: Martin Duerst <duerst@w3.org>
Subject: [idn] New Internet-Draft on Bidirectionality in Identifiers
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hello everybody,

The following draft has been submitted last Friday to the Internet-Draft
editor and should appear soon at
http://www.ietf.org/internet-drafts/draft-duerst-iri-bidi-00.txt.

It has been separated out from
http://www.ietf.org/internet-drafts/draft-masinter-url-i18n-07.txt,
Section 3.2, to allow more in-depth and focused discussion of the
specific problems of bidirectionality.

The draft suggests uri@w3.org as a mailing list for discussion,
but any of the lists that I have sent this mail to is also
okay (please excuse the multiple postings; I made sure that
follow-ups won't be cross-posted).

This is not a final document, in particular Section 5., item 3)
needs more work. Any comments welcome.

Regards,    Martin.

=========================================================================
INTERNET-DRAFT                                              Martin Duerst
                                                       W3C/Keio University
draft-duerst-iri-bidi-00.txt
Expires January 2002                                        July 13, 2001


            Internet Identifiers and Bidirectionality


Status of this Memo

This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026.

Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups.  Note that other
groups may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time.  It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress."

The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.

This document is not a product of any working group, but should be
discussed on the mailing list <uri@w3.org>. Comments of editorial
nature should be sent directly to the author. For more information
on the topic of this Internet-Draft, please also see [W3C IRI].


Abstract

This memo describes how to deal with Internet identifiers containing
characters from scripts such as Arabic and Hebrew, which use right-to-
left or bidirectional writing. The solution proposed addresses three
different contexts: The purely graphical representation of such
identifiers, e.g. on paper, the embedding of such identifiers into
running text with established rules for bidirectionality, and the
processing and resolution of such identifiers.


0. Change history

Version 00:

This memo has been separated out from [IRI], Section 3.2 to allow
more in-depth and focused discussion of the specific problems of
bidirectionality.


1. Introduction

There is an increased tendency to allow identifiers to use a wide
range of characters from the scripts of the world. The Universal
Character Set (UCS, see [Unicode] and [ISO10646]) makes it easy to
use and exchange such identifiers digitally. With the appropriate
care (similar to the care needed to avoid confusion between '1', 'l',
and 'I' in US-ASCII-based identifiers), such identifiers can also
be exchanged non-digitally, e.g. written down visually on a medium
such as paper. Potential examples of such idenitifiers include
Internationalized Resource Identifiers [IRI], Internationalized
Domain Names [IDN], and internationalized email addresses.

Some characters, in particular those of the Arabic and the Hebrew
script, are written from right to left. Together with characters
written from left to right, or with digits that are written from
left to right even in these scripts, this gives raise to the
mixture of different writing directions, a phenomenon called
bidirectionality. Dealing with bidirectionality is indispesable
for the proper treatment of text written with the Arabic or Hebrew
script. But it is highly complex because user expectations may
depend on context and are often difficult to identify and express.

This memo deals with the specific problems of Internet identifiers
containing rigth-to-left characters, hereafter called bidirectional
identifiers.

The basic paradigm of all modern bidirectional text handling solutions
is the distinction between digital backing store, where text is stored
in logical order, and rendering (display or printing), for which the
necessary reordering is applied according to well-defined rules.
'Logical order' in this context is the order in which the characters
in the text are pronounced or spelled out.

Using logical order in the digital backing store simplifies a large
number of operations, including sorting, searching, text-to-speech
conversion, various other kinds of linguistic processing, input from
keyboards and other devices, and rendering-related operations such as
line breaking and text reflow. The alternative is to use display order
even in the backing store, but this makes some of the operations above
much more complex and others impossible.

For general text (e.g. average prose,...), the Unicode bidirectional
algorithm [UnicodeBidi] is the single widely accepted and used reference
for providing this reordering from logical order to rendering. The
Unicode bidirectional algorithm consists of an implicit part (producing
adequate results in most cases) and explicit formatting characters for
advanced cases.

The Unicode bidirectional algorithm also allows higher-order protocols
o overwrite certain aspects of the algorithm. A case where this has
been done is the 'dir' attribute in [HTML4].

Bidirectional Internet identifiers primarily are used in three different
contexts:

1) In visual form: This includes display on CTR and LCDs as well as
    more permanent visual forms such as printing. At least as far
    as the reading of individual components is concerned, the visual
    form has to use the inherent directionality of the characters used.
    Otherwise, identification, reading, transcription, and so on are
    severely affected.

2) In digital form inside running text (e.g. an IRI or an email
    address in an email or on a web page). It is not always easy
    or possible to distinguish identifiers from other text.

3) In digital form on its own (e.g. in a structured format or
    database of identifiers, or when transmitted for resolution).
    It should be possible to process bidirectional identifiers
    in the same way as other Internet identifiers.

This memo addresses all these three cases as well as the conversion
between them. The specifics of bidirectional text and of identifier
structure make it impossible to design a solution that works without
additional effort (when compared to non-bidirectional identifiers).
However, the solution proposed in this memo is designed to make the
best out of the severe constraints.


2. Notational Conventions

Keywords in all upper-case such as MUST and SHOULD are defined
in [RFC 2119]. For examples, lower-case letters are used for
letters that flow left to right. Upper-case letters stand for
letters that flow from right to left. A left-to-right example
would be 'hello', whereas a right-to-left example would be
'OLLEH'.

For bidirectional formatting characters from [Unicode], the [XML]-style
entitiy notation is used, as follows:

&lrm;    U+200E     LEFT-TO-RIGHT MARK
&rlm;    U+200F     RIGHT-TO-LEFT MARK
&lre;    U+202A     LEFT-TO-RIGHT EMBEDDING
&rle;    U+202B     RIGHT-TO-LEFT EMBEDDING
&pdf;    U+202C     POP DIRECTIONAL FORMATTING
&lro;    U+202D     LEFT-TO-RIGHT OVERRIDE
&rlo;    U+202E     RIGHT-TO-LEFT OVERRIDE

Only the first two are defined in [HTML4]; the others are
replaced by the 'dir' attribute and the <bdo> element.


3. Identifier Structure

Most Internet identifiers have an inherent structure that distinguishes
structural characters (usually punctuation such as '@', '.', ':', '/',
and so on) and payload components (usually formed with plain alphabetic
or alphanumeric characters).

In order to be able to process bidirectional identifiers in the same
way as other identifiers, it is crucial that in the digital
representations, the individual structural characters and identifier
components are stored in the same sequence as for other identifiers.

The main problem to solve for the visual representation of bidirectional
identifiers is whether the general sequence of components and syntax
characters should be from left to right or from right to left, i.e.
whether the right-to-left equivalent of "ftp.example.com" should be
"MOC.ELPMAXE.PTF" or "PTF.ELPMAXE.MOC". The former one may be
seen as more natural in a purely right-to-left context. But there is also
the possibility of mixed identifiers such as "PTF.ELPMAXE.com".
These provide a very strong motivation for maintaining the same
left-to-right overall component sequence for all Internet identifiers.

The Unicode bidirectional algorithm, extremely simplified, tries to
reorder continuous sequences of right-to-left characters between
continuous sequences of left-to-right characters. A third category,
called neutrals, is processed in the same way as surrounding characters.
The main problem for identifiers is that all the structural characters
are treated as neutrals by the Unicode algorithm, which means that they
are moved around together with their context. As an example, the
logical sequence FTP.EXAMPLE.com (corresponding to the example above),
without additional care is displayed as ELPMAXE.PTF.com, which is
obviously highly confusing.


4. Bidirectional Identifiers in Context

4.1 Independently Processed Bidirectional Identifiers

Bidirectional identifiers processed independently, i.e. stored or
transmitted for resolution, MUST be in full logical order both
for the overall structure as well as for the individual components.
They MUST conform directly to the relevant syntax rules.

4.2 Visual Rendering of Bidirectional Identifiers

Bidirectional Identifiers MUST be rendered visually by rendering
each component and each structural character from left to right.
They MUST render each component according to its natural direction
(i.e. left-to-right for components with left-to-right characters,
right-to-left for components with right-to-left characters).

4.3 Bidirectional Identifiers in Textual Context

In textual context, i.e. assuming rendering by the Unicode bidirectional
algorithm, the backing store representation prescribed in Section 4.1
and the visual rendering prescribed in section 4.2 have to be
combined. This is done as follows:

- Each component with right-to-left characters is preceded and
   followed by an &lrm;. This left-to-right mark provides a
   left-to-right context to intervening syntactic characters.

- If the overall context (base directionality) is right-to-left,
   the identifier is preceded by an &lre; and followed by a &pdf;.
   This makes sure that the components of the identifier are
   rendered in left-to-right order. This may also be done by
   using the equivalent features of a higher-order protocol
   (e.g. by using the dir='ltr' attribute in HTML).

4.4 Conversions

Conversion from textual context to visual representation is done
simply by applying the Unicode bidirectional algorithm, i.e. by
passing the whole text to an appropriate rendering engine.

Conversion from processing representation to textual context is
done by adding the necessary formatting characters as described
in Section 4.3.

Conversion from textual context to processing representation is
done by removing the formating characters at the positions
described in Section 4.3. For international domain names, this
can e.g. be integrated in [nameprep].

Conversion from visual representation to processing representation
is done by inputting the identifier, component-by-component from
left to right, using the natural reading order for each component.

 From these three conversions, the remaining conversions can be
easily constructed. Any other procedure that leads to the same results
is also allowed.


5. Restrictions

The definitions and conversions in Section 4 only work under the
following restrictions.

1) A component MUST NOT not use both right-to-left and left-to-right
    characters.

2) A component MUST NOT contain bidirectional formatting characters
    except for those and in those positions as defined in Section 4.3.

3) A component using right-to-left characters MUST NOT use any other
    class of characters (e.g. neutrals or numbers).

Restrictions 1) and 2) are not very severe, in that they do not overly
restrict useful identifiers. Also, trying to remove it would make it
impossible for humans to predict the logical sequence of characters
inside a single component. On the other hand, it would be very desirable
to remove or at least soften restriction 3). Otherwise, it is impossible
to combine Arabic or Hebrew letters with numbers, or to use a hyphen 
between two subcomponents of an Arabic component to avoid the cursive
connection of the two subcomponents. To a certain extent, softening this
restriction should be easily possible by adding additional formating
characters in well defined ways similar to the provisions in Section 4.3.
Feedback on this issue is particularly welcome.


6. Security Considerations

Knowledge of deficiencies of a particular implementation of the above
specification can allow somebody to pretend to resolve a particular
identifier when indeed another identifier is being resolved.


Acknowledgements

The basic idea for the approach proposed in this memo are due to
Francois Yergeau, and go back to around 1995. Discussions with
Stephen Atkin, Paul Hoffman, and many others provided additional
motivation and insight.


Copyright

Copyright (C) The Internet Society, 1997. All Rights Reserved.

This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works.  However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other
than English.

The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.

This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."


Author's address

           Martin J. Duerst
           W3C/Keio University
           5322 Endo, Fujisawa
           252-8520 Japan
           duerst@w3.org
           http://www.w3.org/People/D%C3%BCrst/
           Tel/Fax: +81 466 49 1170

           Note: Please write "Duerst" with u-umlaut wherever
                 possible, e.g. as "D&#252;rst" in XML and HTML.


References

[HTML4] "HTML 4.01", World Wide Web Consortium,
   <http://www.w3.org/TR/REC-html40>.

[IDN] Internationalized Domain Name (idn) IETF Working Group. For
   furter information, please see
   <http://www.ietf.org/html.charters/idn-charter.html>.

[IRI] L. Masinter, M. Duerst, "Internationalized Resource Identifiers
   (IRI)", Internet Draft, Jan. 2001,
   <http://www.ietf.org/internet-drafts/draft-masinter-url-i18n-07.txt>,
   work in progress.

[ISO10646] ISO/IEC, Information Technology - Universal Multiple-Octet
   Coded Character Set (UCS) - Part 1: Architecture and Basic
   Multilingual Plane, Oct. 2000, with amendments.

[Nameprep] P. Hoffman, M. Blanchet, "Preparation of Internationalized
   Host Names", Internet Draft, Feb. 2001,
   <http://www.ietf.org/internet-drafts/draft-ietf-idn-nameprep-03.txt>,
   work in progress.

[RFC 2119] S. Bradner, "Key words for use in RFCs to Indicate
   Requirement Levels", March 1997.

[Unicode] The Unicode Consortium, "The Unicode Standard, Version 3.1",
   consisting of: "The Unicode Standard, Version 3.0", Addison-Wesley,
   Reading, MA, 2000, and "Unicode Standard Annex #27: Unicode 3.1",
   <http://www.unicode.org/unicode/reports/tr27/>, May 2001.

[UnicodeBidi] The Unicode Consortium, "The Unicode Standard, Version
   3.0", Addison-Wesley, Reading, MA, 2000, Section 3.12, pp. 55-69, also
   available at <http://www.unicode.org/unicode/uni2book/ch03.pdf>
   and "Unicode Standard Annex #9: The Bidirectional Algorithm",
   <http://www.unicode.org/unicode/reports/tr9/tr9-9.html">, March 2001.

[W3C IRI] Internationalization - URIs and other identifiers
   <http://www.w3.org/International/O-URL-and-ident.html>.

[XML] "XML 1.0", World Wide Web Consortium Recommendation,
   <http://www.w3.org/TR/REC-xml#sec-external-ent>.





From owner-idn@ops.ietf.org  Mon Jul 16 06:32:17 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA06824
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 06:32:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15M5DA-0002WM-00
	for idn-data@psg.com; Mon, 16 Jul 2001 03:02:44 -0700
Received: from h-135-207-24-10.research.att.com ([135.207.24.10] helo=r2.jck.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15M5D9-0002WG-00; Mon, 16 Jul 2001 03:02:43 -0700
Date: Mon, 16 Jul 2001 05:28:43 -0400
From: John C Klensin <klensin@jck.com>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: idn@ops.ietf.org
Subject: Re: [idn] Reality Check
Message-ID: <3652661.995261323@localhost>
X-Mailer: Mulberry/2.1.0b1 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Sunday, 15 July, 2001 22:35 -0500 "Eric A. Hall"
<ehall@ehsco.com> wrote:

> As an aside, it is possible to upgrade many of the legacy
> protocols to UTF-8 without actually changing the protocol
> semantics, simply by using out-of-band negotation features.
> Finger, Echo, Gopher, etc., all of them could be upgraded. Not
> by this WG of course, but the work that this WG performs will
> dictate how that work eventually happens.
> 
> For example, if there's an out-of-band negotiation for "use
> UTF-8" that is glued onto finger, then the output can be
> internationalized, but the query inputs will also need to be
> internationalized for maximum functionality. This will include
> IDNs (with Finger in particular).

Eric,

Could you elaborate on what you propose to do with "out of band
negotiation" in these cases.  I can certainly understand a
protocol in which you call me, ask if my server is upgraded, and
then put it on a list, but such things traditionally have lousy
scaling and long-term properties.  It is difficult for me to
imagine how you would add anything out of band to finger, whois,
or other "one connection, one exchange" protoocols.  What did you
have in mind?

    john
 



From owner-idn@ops.ietf.org  Mon Jul 16 08:10:18 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA20814
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 08:10:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15M6pz-0007Ye-00
	for idn-data@psg.com; Mon, 16 Jul 2001 04:46:55 -0700
From: John C Klensin <klensin@psg.com>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: idn@ops.ietf.org
Subject: Re: [idn] Reality Check
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15M6pz-0007Ye-00@psg.com>
Date: Mon, 16 Jul 2001 04:46:55 -0700

--On Sunday, 15 July, 2001 22:35 -0500 "Eric A. Hall"
<ehall@ehsco.com> wrote:

> As an aside, it is possible to upgrade many of the legacy
> protocols to UTF-8 without actually changing the protocol
> semantics, simply by using out-of-band negotation features.
> Finger, Echo, Gopher, etc., all of them could be upgraded. Not
> by this WG of course, but the work that this WG performs will
> dictate how that work eventually happens.
> 
> For example, if there's an out-of-band negotiation for "use
> UTF-8" that is glued onto finger, then the output can be
> internationalized, but the query inputs will also need to be
> internationalized for maximum functionality. This will include
> IDNs (with Finger in particular).

Eric,

Could you elaborate on what you propose to do with "out of band
negotiation" in these cases.  I can certainly understand a
protocol in which you call me, ask if my server is upgraded, and
then put it on a list, but such things traditionally have lousy
scaling and long-term properties.  It is difficult for me to
imagine how you would add anything out of band to finger, whois,
or other "one connection, one exchange" protoocols.  What did you
have in mind?

    john
  





From owner-idn@ops.ietf.org  Mon Jul 16 09:48:28 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA10780
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 09:48:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15M84y-000BgB-00
	for idn-data@psg.com; Mon, 16 Jul 2001 06:06:28 -0700
To: <idn@ops.ietf.org>, iesg@ietf.org, <poised@lists.tislabs.com>
Subject: Re: [idn] UTF-8 as the long-term IDN solution
Date: Mon, 16 Jul 2001 08:41:42 -0400
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15M84y-000BgB-00@psg.com>

I am writing to support the WG chairs. IDN has been a particularly
contentious and multidimentsional problem. IETF working groups are not
run by voting or polls but by the chair's judgement of consensus and
how to achieve progress on the charter.  Although polls can, in some
cases, be useful, they occur only at the discretion of the chair. The
appeals path if you don't like the chair's judgement is quite clear,
it goes to the Area Director, and then the IESG. It specifically does
not include the poised mailing list.

Although I haven't seen that much evidence of consensus on the point,
it's possible that there is an IDN WG consensus that the "long-term"
solution is UTF-8, where long term is >10 years. But I believe the
charter of the WG is to do something a lot sooner than that and I do
not believe there is a consensus to just send UTF-8 in the near term.

I do not see any bias in the chairs. On the other hand, over several
years, I have observed what I believe is consistent trigger happy
posting of ad hominum attacks by Mr. Bernstein in violaiton of the
draft IETF document which the POISSON WG insists on calling a "Code of
Coduct.

Donald

From:  "James Seng/Personal" <James@Seng.cc>
Message-ID:  <00e901c10d9c$8c55d860$dd00a8c0@jamessonyvaio>
To:  "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>,
<iesg@ietf.org>,
            <poised@lists.tislabs.com>
References:  <E15LLxX-000G18-00@psg.com>
<20010714211816.D31484@arwen.cs.berkeley.edu
> <20010715203004.30572.qmail@cr.yp.to>
Date:  Mon, 16 Jul 2001 10:10:56 +0800

>> I believe that the IDN WG has consensus on the following point: ``The
>> long-term IDN solution will encode Unicode characters as UTF-8 on the
>> wire.'' I find the other possibilities absurd, and I am dismayed at
>the
>> amount of time that has been wasted discussing them on the IDN list.
>
>I speak for myself in this note. (Marc may have different opinion)
>
>The working groups works based on ideas documented in internet drafts
>and not a broad statement/claim.
>
>> On 2001-05-29 I requested that the the IDN WG chairs run a poll to
see
>> whether we do, in fact, have consensus on this point.
>>
>> ``I would like to hear some support on this before we run this
poll,''
>> James Seng said, speaking as chair.
>>
>> He promptly heard some support, but he did not run the poll. I asked
>why
>> the chairs were not running the poll. There was no response.
>
>First, there is a response: I requested you to point to an internet
>draft which you are referring or write a draft yourself.
>
>Secondly, strawpoll are not fun events which we conduct -- it is very
>time-consuming. Surprisingly, I still have a day-time job.
>
>Thirdly, strawpoll are useful, but not neccessary, when the chairs
wants
>to know if there is a consensus on a particular *draft*.
>
>And last, but not the least, there is a existing announced process to
>split the wg drafts into Pool W for drafts with 7 supporters and Pool T
>for others. If you strongly feel about your idea, please write a draft,
>gather 7 supporters, then come back to the working group with your
>draft.
>
>> I accuse the chairs of bias in their selection of polls. They appear
>to
>> be running polls that they believe will promote their personal
>agendas,
>> and refusing to run any other polls. Does the IETF have any
procedures
>> to fix this problem?
>
>You are free to form any conspiracy theory you like in your personal
>thoughts. But making these theory into public statement requires
>substained evidences.
>
>If anyone feels the wg chairs is act inappropriatly, a private note to
>IESG would usually do the job. Given that a number of IESG and IAB
>members are on this list, any wrongdoing would be note almost
>immediately.
>
>Once in a while, certain individual in the wg have louder voice than
>others and repeat his opinion often enough. Fortunately, the IETF
>process does not guage consensus based on decibel level or number of
>emails sent. Instead, we work on Internet Drafts and consensus, ie.
each
>and every wg members' views are taken into consideration. A louder
voice
>does not make anyone more important than others.
>
>And the wg chairs are here to assist the process, not to conduct
>strawpoll for individual whims. Thank you.
>
>-James Seng
>





From owner-idn@ops.ietf.org  Mon Jul 16 10:40:17 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA22765
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 10:40:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15M8z9-000EP9-00
	for idn-data@psg.com; Mon, 16 Jul 2001 07:04:31 -0700
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15M8z8-000EP3-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 07:04:30 -0700
Received: from [216.153.32.76] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 161196; Mon, 16 Jul 2001 07:03:55 -0700
Message-ID: <3B52F44E.9CBBE7E4@ehsco.com>
Date: Mon, 16 Jul 2001 09:03:59 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: John C Klensin <klensin@jck.com>
CC: idn@ops.ietf.org
Subject: Re: [idn] Reality Check
References: <3652661.995261323@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> It is difficult for me to imagine how you would add anything out of
> band to finger, whois, or other "one connection, one exchange"
> protoocols.  What did you have in mind?

Using transport-layer options to negotiate over compression, encryption,
charset and other per-session characteristics.

With finger, for example, the client and server could use TCP options to
negotiate over the charset, without having to change the finger protocol
semantics whatsoever.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Mon Jul 16 12:07:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA11042
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 12:07:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MANe-000J2w-00
	for idn-data@psg.com; Mon, 16 Jul 2001 08:33:54 -0700
Received: from mail4.microsoft.com ([131.107.3.122])
	by psg.com with smtp (Exim 3.31 #1)
	id 15MANc-000J2l-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 08:33:53 -0700
Received: from 157.54.9.108 by mail4.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 16 Jul 2001 08:33:19 -0700 (Pacific Daylight Time)
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-imc-05.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 16 Jul 2001 08:32:58 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.82]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 16 Jul 2001 08:32:58 -0700
Received: from win-msg-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.134]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 16 Jul 2001 08:31:57 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.5683.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C10E0C.72BF2F13"
Subject: [idn] Test -- please disregard
Date: Mon, 16 Jul 2001 08:31:57 -0700
Message-ID: <8CC03F47967BF14D9710887723FADDB6964D43@win-msg-02.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Test -- please disregard
Thread-Index: AcEODJPbY8bfa5hZSjiS1f8pkheDfg==
From: "Russ Rolfe" <rrolfe@windows.microsoft.com>
To: <idn@ops.ietf.org>
X-OriginalArrivalTime: 16 Jul 2001 15:31:57.0478 (UTC) FILETIME=[72FEC460:01C10E0C]
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01C10E0C.72BF2F13
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable



------_=_NextPart_001_01C10E0C.72BF2F13
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.5683.1">
<TITLE>Test -- please disregard</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C10E0C.72BF2F13--



From owner-idn@ops.ietf.org  Mon Jul 16 12:42:32 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA18029
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 12:42:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MB1C-000LPB-00
	for idn-data@psg.com; Mon, 16 Jul 2001 09:14:46 -0700
Date: Mon, 16 Jul 2001 10:32:42 -0400 (EDT)
From: James M Galvin <galvin@acm.org>
Subject: [idn] Re: UTF-8 as the long-term IDN solution
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15MB1C-000LPB-00@psg.com>
To: idn-data@psg.com

Speaking as co-Chair of POISSON, as important as this discussion is the
only part of it that is relevant to POISSON (and its poised mailing
list) is the one question Dan asked, repeated below for your
convenience.

Please trim the "cc" list on all discussion to exclude the poised
mailing list unless you are answering this question:


On Sun, 15 Jul 2001, D. J. Bernstein wrote:

    I accuse the chairs of bias in their selection of polls. They appear
to
    be running polls that they believe will promote their personal
agendas,
    and refusing to run any other polls. Does the IETF have any
procedures
    to fix this problem?


Thanks,

Jim
--
James M. Galvin <galvin@acm.org>






From owner-idn@ops.ietf.org  Mon Jul 16 13:15:02 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA26340
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 13:15:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MBmF-000Nwt-00
	for idn-data@psg.com; Mon, 16 Jul 2001 10:03:23 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MBmE-000Nwn-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 10:03:22 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id TAA03105;
	Mon, 16 Jul 2001 19:02:44 +0200 (MET DST)
Date: Mon, 16 Jul 2001 18:27:08 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: "Adam M. Costello" <amc@cs.berkeley.edu>,
        idn working group <idn@ops.ietf.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
Message-ID: <171080.995308028@localhost>
In-Reply-To: <20010716015000.F8322@arwen.cs.berkeley.edu>
References:  <20010716015000.F8322@arwen.cs.berkeley.edu>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-07-16 01.50 +0000 "Adam M. Costello" <amc@cs.berkeley.edu> wrote:

> Martin Duerst <duerst@w3.org> wrote:
> 
>> But the current IDNA draft explicitly specifies that zone files must
>> be in ACE, and therefore prohibits such implementations.
> 
> Well that's just silly.  Paul and Patrick, the IDNA spec should not say
> that master files must use ACE, it should say that DNS servers must
> accept master files that use ACE and may also accept master files that
> use other encodings, like UTF-8.

If that is in the text (I don't have it in front of me) yes, that is silly
and should of course be changed. What charset the user uses when entering
data into his favourite DNS server is up to the implementation.

What Paul and I want to say is that the zone data (in some meta-way) is ACE
encoded in the master server, and the master server operates on that data.
How the data is entered, converted or whatever is out of scope. The same
would be true for UTF-8 by the way given the ability for users to have
editors and operating systems which doesn't use _NAMEPREPPED_ UTF-8
natively in files which later are read by the DNS server.

And, regarding UTF-8 or ACE, the most important thing is the nameprep and
not what encoding the labels uses. I am sorry to say that I am extremely
worried that if we go with an encoding that is implemented (like UTF-8)
people will not do nameprep.

   paf




From owner-idn@ops.ietf.org  Mon Jul 16 13:28:21 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA29493
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 13:28:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MBmt-000Nxe-00
	for idn-data@psg.com; Mon, 16 Jul 2001 10:04:03 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MBms-000Nx5-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 10:04:02 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id TAA03115;
	Mon, 16 Jul 2001 19:02:51 +0200 (MET DST)
Date: Mon, 16 Jul 2001 18:41:23 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Martin Duerst <duerst@w3.org>, Soobok Lee <lsb@postel.co.kr>,
        idn@ops.ietf.org
Subject: Re: [idn] IDN security and ACE leakage
Message-ID: <222306.995308883@localhost>
In-Reply-To: <4.2.0.58.J.20010716143102.038bd920@sh.w3.mag.keio.ac.jp>
References:  <4.2.0.58.J.20010716143102.038bd920@sh.w3.mag.keio.ac.jp>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-07-16 14.36 +0900 Martin Duerst <duerst@w3.org> wrote:

> Ideally, every person should at least have one purely
> ASCII-only email address, and every machine should have
> at least one purely ASCII-only domain name, not consisting
> of characters that look like they come from a random generator.

I don't agree.

If people said this about some arabic script to me, I would not be able to
know the difference between a random generated string in arabic compared to
something which makes sense to people which know arabic (something I don't
do).

I much rather be able to use my name, which I have chosen, in my script, in
applications I have chosen, and then some magic which is implemented in the
network which makes it possible for others to reply to my email.

If I have upgraded my software to be able to handle whatever IDN is coming
up with, I should never have to see the encoded characters which are passed
in the protocols -- regardless of if it is UTF-8 or ACE or whatever.

As a user I don't care.

I want it to work. And to make it to work for users, we engineers have to
be extremely conservative, and as you have understood by now, I don't care
if some of you think I am stupid asking for something as stupid as ACE when
UTF-8 is better. I am conservative, belive nameprep is by far more
important than what encoding we use, and IF we should do something smart,
we should use neither UTF-8 nor ACE in DNS, but instead something much more
efficient given the binary labels we already have in the DNS protocol.

But, as applications take the uncompressed data in the DNS protocol and
"just" use it here and there, we need to see that that data is safe in
whatever (stupid) application there is. If I have upgraded my applications,
I am done. I will never see this encoding stuff anymore. Just like with
quoted-printable in MIME. Do you see QP somewhere? Maybe in headers of
email? Maybe even this email? Then you have broken software, but is that my
fault? Maybe because I did choose to use a charset you can not support, and
that is a valid issue, but if you DO handle the charset, or if you don't,
how do your client handle that situation? _Those_ situations are what we
should talk about and not this smalltalk about "my software is better than
yours".

   paf




From owner-idn@ops.ietf.org  Mon Jul 16 13:30:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA00039
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 13:30:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MBmN-000Nx3-00
	for idn-data@psg.com; Mon, 16 Jul 2001 10:03:31 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MBmL-000Nww-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 10:03:30 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id TAA03109;
	Mon, 16 Jul 2001 19:02:49 +0200 (MET DST)
Date: Mon, 16 Jul 2001 18:28:03 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: "Eric A. Hall" <ehall@ehsco.com>, "Adam M. Costello" <amc@cs.berkeley.edu>
cc: idn working group <idn@ops.ietf.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
Message-ID: <174378.995308083@localhost>
In-Reply-To: <3B524CFB.A6F2E5DC@ehsco.com>
References: <20010716015000.F8322@arwen.cs.berkeley.edu>
 <3B524CFB.A6F2E5DC@ehsco.com>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-07-15 21.10 -0500 "Eric A. Hall" <ehall@ehsco.com> wrote:

>> Well that's just silly.  Paul and Patrick, the IDNA spec should not say
>> that master files must use ACE, it should say that DNS servers must
>> accept master files that use ACE and may also accept master files that
>> use other encodings, like UTF-8.
> 
> The format of a master file needs to be agreed on. This is required for
> DNS to operate properly.

We should differ between "the holy master file format" and what users _can_
use for entering data into their DNS server.

I think we are in agreement but have problems stating what it is.

  paf




From owner-idn@ops.ietf.org  Mon Jul 16 14:04:23 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA07258
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 14:04:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MCPZ-0000GN-00
	for idn-data@psg.com; Mon, 16 Jul 2001 10:44:01 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MCPY-0000GF-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 10:44:00 -0700
Received: from [216.153.32.92] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 161240; Mon, 16 Jul 2001 10:43:24 -0700
Message-ID: <3B5327BF.CB3260DC@ehsco.com>
Date: Mon, 16 Jul 2001 12:43:27 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>
CC: "Adam M. Costello" <amc@cs.berkeley.edu>,
        idn working group <idn@ops.ietf.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
References: <20010716015000.F8322@arwen.cs.berkeley.edu> <171080.995308028@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> And, regarding UTF-8 or ACE, the most important thing is the nameprep
> and not what encoding the labels uses. I am sorry to say that I am
> extremely worried that if we go with an encoding that is implemented
> (like UTF-8) people will not do nameprep.

Any application which is modern enough to use the new API should also be
applying the nameprep rules. If it doesn't, it is broken.

Just-use-ACE is actually the most succeptible to this particular problem,
since old and new applications pass data into the system through the old
APIs equally, without any distinctive markings. Was it nameprepped? nobody
knows... At least with the new API approach we know that a particular IDN
was most likely nameprepped.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Mon Jul 16 14:09:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA08381
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 14:09:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MChU-0001IK-00
	for idn-data@psg.com; Mon, 16 Jul 2001 11:02:32 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MChT-0001IE-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 11:02:31 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA10676;
        Mon, 16 Jul 2001 14:02:19 -0400 (EDT)
Message-Id: <200107161802.OAA10676@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>,
        "Adam M. Costello" <amc@cs.berkeley.edu>,
        idn working group <idn@ops.ietf.org>
Subject: Re: [idn] Why follow IDNA with UTF-8? 
In-reply-to: Your message of "Mon, 16 Jul 2001 12:43:27 CDT."
             <3B5327BF.CB3260DC@ehsco.com> 
Date: Mon, 16 Jul 2001 14:02:19 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Just-use-ACE is actually the most succeptible to this particular problem,
> since old and new applications pass data into the system through the old
> APIs equally, without any distinctive markings. Was it nameprepped? nobody
> knows...

ACE is sufficiently ugly that it's difficult to imagine that it will be produced 
other than by calling the APIs that produce it - and those APIs will support 
nameprep.



From owner-idn@ops.ietf.org  Mon Jul 16 14:10:27 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA08483
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 14:10:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MCRn-0000Ib-00
	for idn-data@psg.com; Mon, 16 Jul 2001 10:46:19 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15MCRl-0000IB-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 10:46:18 -0700
Received: (qmail 25834 invoked by uid 1001); 16 Jul 2001 17:28:41 -0000
Date: 16 Jul 2001 17:28:41 -0000
Message-ID: <20010716172841.10339.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org,
  iesg@ietf.org,
  poised@lists.tislabs.com
Automatic-Legal-Notices: Copyright 2001, D. J. Bernstein. My transmission of this message to you does not constitute a copyright waiver or any other limitation of my rights, even if you have told me otherwise.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org, iesg@ietf.org, poised@lists.tislabs.com
Subject: [idn] Re: UTF-8 as the long-term IDN solution
References: <Pine.BSF.4.21.0107161026550.12160-100000@two.elistx.com> <200107161523.LAA09625@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Keith Moore writes:
> I believe this is adequately addressed in RFC 2026, section 6.5.

I don't see how.

RFC 2026, section 6.5, is for cases where someone disagrees with ``a
Working Group recommendation.''

What's happening in this case is completely different. There is no
recommendation. There are a huge number of WG members who

   (1) agree that UTF-8 will be the long-term solution;
   (2) suspect that there's consensus in the WG on #1; and
   (3) believe that establishing consensus would save time for the WG.

But the chair, who disagrees with #1, is stonewalling, in violation of
his responsibility under RFC 2418 to ensure forward progress.

As you can see from http://cr.yp.to/djbdns/namedroppers.html, I've
already tried using the RFC 2026 process to handle procedural problems,
specifically DNSEXT mailing list censorship, which has been roundly
criticized in POISSON recently. The process took more than two years.
The basic problem still isn't fixed.

I don't want IDN to wait two years. There needs to be a mechanism for
the WG to act over the opposition of the chair. IETF doesn't seem to
have any such mechanism.

---Dan



From owner-idn@ops.ietf.org  Mon Jul 16 14:11:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA08826
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 14:11:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MCI1-000PrJ-00
	for idn-data@psg.com; Mon, 16 Jul 2001 10:36:13 -0700
Received: from mail-blue.research.att.com ([135.207.30.102])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MCI0-000Pr1-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 10:36:12 -0700
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 575554D808; Mon, 16 Jul 2001 13:36:11 -0400 (EDT)
Received: from r2.jck.com (secure.research.att.com [135.207.24.10])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id NAA15121;
	Mon, 16 Jul 2001 13:35:51 -0400 (EDT)
Date: Mon, 16 Jul 2001 13:35:17 -0400
From: John C Klensin <klensin@research.att.com>
To: "Eric A. Hall" <ehall@ehsco.com>
Cc: idn@ops.ietf.org
Subject: Re: [idn] Reality Check
Message-ID: <2717881.995290517@r2.jck.com>
In-Reply-To: <3B52F44E.9CBBE7E4@ehsco.com>
References:  <3B52F44E.9CBBE7E4@ehsco.com>
X-Mailer: Mulberry/2.1.0b1 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Monday, 16 July, 2001 09:03 -0500 "Eric A. Hall"
<ehall@ehsco.com> wrote:

> 
>> It is difficult for me to imagine how you would add anything
>> out of band to finger, whois, or other "one connection, one
>> exchange" protoocols.  What did you have in mind?
> 
> Using transport-layer options to negotiate over compression,
> encryption, charset and other per-session characteristics.
>...

Ok, that is fair, although I personally believe that moving
applications options (such as most of the above) down to the
transport layer would introduce layering problems that we would
come to very seriously regret in the future.
  
> With finger, for example, the client and server could use TCP
> options to negotiate over the charset, without having to change
> the finger protocol semantics whatsoever.

Yep.  Although I think that institutionalizing that type of layer
violation would be much more likely to wreck the Internet than
anything we could do with the DNS.  Remember that the corollary
to the end to end principle that we don't change the transport
core to accomodate particular applications is considered by many
to be the key doctrine that has preserved our ability to quickly
innovate and test new ideas.

Just my impression, however.

     john




From owner-idn@ops.ietf.org  Mon Jul 16 14:28:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA12016
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 14:28:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MCWA-0000dx-00
	for idn-data@psg.com; Mon, 16 Jul 2001 10:50:50 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MCW9-0000do-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 10:50:49 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA10522;
        Mon, 16 Jul 2001 13:50:42 -0400 (EDT)
Message-Id: <200107161750.NAA10522@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
cc: "Eric A. Hall" <ehall@ehsco.com>, "Adam M. Costello" <amc@cs.berkeley.edu>,
        idn working group <idn@ops.ietf.org>
Subject: Re: [idn] Why follow IDNA with UTF-8? 
In-reply-to: Your message of "Mon, 16 Jul 2001 18:28:03 +0200."
             <174378.995308083@localhost> 
Date: Mon, 16 Jul 2001 13:50:42 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> We should differ between "the holy master file format" and what users _can_
> use for entering data into their DNS server.
> 
> I think we are in agreement but have problems stating what it is.

perhaps we should state things in terms of "exchange format" and "local format".

"exchange format" is the format used to exchange zones in a flat file;
DNS implementations should be able to dump and accept zones in that format.
for the time being, it should use ACE, for compatibility with old DNS 
implementations.

"local format" can be anything the DNS implementation wants (web form input,
XML, S-expressions, Morse code, whatever) and the standard shouldn't place any 
restrictions on it.

Keith



From owner-idn@ops.ietf.org  Mon Jul 16 14:29:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA12197
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 14:29:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MCqB-0001jK-00
	for idn-data@psg.com; Mon, 16 Jul 2001 11:11:31 -0700
Received: from work.netcorps.com ([207.1.125.97])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MCqA-0001jD-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 11:11:30 -0700
Received: from localhost (bright@localhost)
	by work.netcorps.com (8.9.0/8.9.0) with SMTP id LAA29303;
	Mon, 16 Jul 2001 11:10:44 -0700 (PDT)
Date: Mon, 16 Jul 2001 11:10:43 -0700 (PDT)
From: Bright Fulton <bright@alldomains.com>
X-Sender: bright@work.netcorps.com
Reply-To: Bright Fulton <bright@alldomains.com>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>,
        "Adam M. Costello" <amc@cs.berkeley.edu>,
        idn working group <idn@ops.ietf.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
In-Reply-To: <3B5327BF.CB3260DC@ehsco.com>
Message-ID: <Pine.GSO.3.96.1010716110318.24481F-100000@work.netcorps.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Mon, 16 Jul 2001, Eric A. Hall wrote:
> Just-use-ACE is actually the most succeptible to this particular problem,
> since old and new applications pass data into the system through the old
> APIs equally, without any distinctive markings. Was it nameprepped? nobody
> knows... At least with the new API approach we know that a particular IDN
> was most likely nameprepped.

Implementing ACE without Nameprep wouldn't be logical, and we need not
consider it any more than we consider any other mis-implementation of
IDNA.

Bright






From owner-idn@ops.ietf.org  Mon Jul 16 14:34:30 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA13047
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 14:34:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MCmw-0001Z7-00
	for idn-data@psg.com; Mon, 16 Jul 2001 11:08:10 -0700
Received: from mail3.microsoft.com ([131.107.3.123])
	by psg.com with smtp (Exim 3.31 #1)
	id 15MCmv-0001Yn-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 11:08:09 -0700
Received: from 157.54.9.104 by mail3.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 16 Jul 2001 11:04:56 -0700 (Pacific Daylight Time)
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 16 Jul 2001 11:07:30 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 16 Jul 2001 11:07:27 -0700
Received: from win-msg-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.134]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 16 Jul 2001 11:06:26 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.5683.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: [idn] pool deadline imminent
Date: Mon, 16 Jul 2001 11:06:26 -0700
Message-ID: <8CC03F47967BF14D9710887723FADDB6964D4E@win-msg-02.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: [idn] pool deadline imminent
Thread-Index: AcELSbT+7Zj44QVeQhGNfAQsq+fDtwC2B3JQ
From: "Russ Rolfe" <rrolfe@windows.microsoft.com>
To: "Martin Duerst" <duerst@w3.org>, "idn working group" <idn@ops.ietf.org>
X-OriginalArrivalTime: 16 Jul 2001 18:06:26.0978 (UTC) FILETIME=[080C3820:01C10E22]
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA13047

Martin Duerst wrote:

> At 17:46 01/07/12 +0000, Adam M. Costello wrote:
>> I didn't really understand until this morning that any proposal that 
>> doesn't have seven supporters by tomorrow will be out of the running.

> Just for the record: If anybody is working on a UTF-8 based
> (or even ACE/UTF-8 mixed) solution, they herewith all have
> my support (I won't tell them one-by-one).

I know this is late, but was unable to reply until now.  UTF-8 based
solutions also have my support.

Regards, Russ Rolfe
Microsoft -- rrolfe@microsoft.com

-----Original Message-----
From: Martin Duerst [mailto:duerst@w3.org] 
Sent: Thursday, July 12, 2001 7:49 PM
To: idn working group
Subject: Re: [idn] pool deadline imminent


At 17:46 01/07/12 +0000, Adam M. Costello wrote:
>I didn't really understand until this morning that any proposal that 
>doesn't have seven supporters by tomorrow will be out of the running.

Just for the record: If anybody is working on a UTF-8 based
(or even ACE/UTF-8 mixed) solution, they herewith all have
my support (I won't tell them one-by-one).

Regards,   Martin.




From owner-idn@ops.ietf.org  Mon Jul 16 14:38:18 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA13763
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 14:38:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MD67-0002TT-00
	for idn-data@psg.com; Mon, 16 Jul 2001 11:27:59 -0700
Received: from epa.secret.org ([206.220.140.150] ident=0)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MD65-0002TA-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 11:27:57 -0700
Received: from localhost (lucid@localhost)
	by epa.secret.org (8.9.3/8.9.1) with ESMTP id OAA36217;
	Mon, 16 Jul 2001 14:27:52 -0400 (EDT)
Date: Mon, 16 Jul 2001 14:27:52 -0400 (EDT)
From: *click* <lucid@epa.secret.org>
To: idn working group <idn@ops.ietf.org>
cc: Russ Rolfe <rrolfe@windows.microsoft.com>, Martin Duerst <duerst@w3.org>
Subject: RE: [idn] pool deadline imminent
In-Reply-To: <8CC03F47967BF14D9710887723FADDB6964D4E@win-msg-02.wingroup.windeploy.ntdev.microsoft.com>
Message-ID: <Pine.BSF.4.33.0107161421280.33288-100000@epa.secret.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


Better late then never...
I am in support of any UTF-8 based solution and am willing to help
contribute if anyone is working on such a draft.

-Bill

On Mon, 16 Jul 2001, Russ Rolfe wrote:

> Martin Duerst wrote:
>
> > At 17:46 01/07/12 +0000, Adam M. Costello wrote:
> >> I didn't really understand until this morning that any proposal that
> >> doesn't have seven supporters by tomorrow will be out of the running.
>
> > Just for the record: If anybody is working on a UTF-8 based
> > (or even ACE/UTF-8 mixed) solution, they herewith all have
> > my support (I won't tell them one-by-one).
>
> I know this is late, but was unable to reply until now.  UTF-8 based
> solutions also have my support.
>
> Regards, Russ Rolfe
> Microsoft -- rrolfe@microsoft.com
>
> -----Original Message-----
> From: Martin Duerst [mailto:duerst@w3.org]
> Sent: Thursday, July 12, 2001 7:49 PM
> To: idn working group
> Subject: Re: [idn] pool deadline imminent
>
>
> At 17:46 01/07/12 +0000, Adam M. Costello wrote:
> >I didn't really understand until this morning that any proposal that
> >doesn't have seven supporters by tomorrow will be out of the running.
>
> Just for the record: If anybody is working on a UTF-8 based
> (or even ACE/UTF-8 mixed) solution, they herewith all have
> my support (I won't tell them one-by-one).
>
> Regards,   Martin.
>
>
>




From owner-idn@ops.ietf.org  Mon Jul 16 14:49:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA15567
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 14:49:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MDGS-0002nY-00
	for idn-data@psg.com; Mon, 16 Jul 2001 11:38:40 -0700
Received: from mail5.microsoft.com ([131.107.3.121])
	by psg.com with smtp (Exim 3.31 #1)
	id 15MDGR-0002mB-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 11:38:39 -0700
Received: from 157.54.9.100 by mail5.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 16 Jul 2001 11:05:09 -0700 (Pacific Daylight Time)
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-imc-03.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 16 Jul 2001 11:04:52 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.82]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 16 Jul 2001 11:04:29 -0700
Received: from win-msg-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.134]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 16 Jul 2001 11:03:28 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.5683.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: [idn] Reality Check
Date: Mon, 16 Jul 2001 11:03:27 -0700
Message-ID: <8CC03F47967BF14D9710887723FADDB687E3B1@win-msg-02.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: [idn] Reality Check
Thread-Index: AcEMr+BVwL+hFYdISFilgq2h9zO/QQBa+1uw
From: "Russ Rolfe" <rrolfe@windows.microsoft.com>
To: "Adam M. Costello" <amc@cs.berkeley.edu>, <idn@ops.ietf.org>
X-OriginalArrivalTime: 16 Jul 2001 18:03:28.0357 (UTC) FILETIME=[9D94D150:01C10E21]
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA15567

Let me first apologize for not answering sooner.  First my message that
showed up on Saturday was actually sent on Wednesday.  Some kind soul
re-submitted my E-mail and E-mail address to allow me to contribute
again to the list.

Adam M. Costello wrote:

> Are you arguing that ACE is unnecessary?  

Yes

> If so, please explain how email 
> is going to work.  What is supposed to happen when IDN-capable person
A 
> sends a message to IDN-capable person B, who then forwards the message
to 
> IDN-incapable person C, who would like to reply to A?  

To follow my example given.  In the past when people did not have
matching E-mail systems, person C would send the reply back to person B
to forward it on to person A.  Not efficient, but the message got back
to person A.  Thus it would work the same IDN-incapable person C would
send to IDN-capable person B who would forward it to Person A. 

Another solution is if Person A also has a non-IDN address, he can added
it to his signature (just like most of us add a phone number, address,
fax or other way to communicate to our signature) and then person C can
E-mail his reply via the non-IDN address directly to person A.

If it is important enough for person C and A to continue with
communications, they either stay with the non-IDN address or person C
contacts his IT people and suggests that they need to upgrade their
system to allow him to communicate with person A via the IDN-address.

> What is supposed to 
> happen when IDN-capable people send email to mailing lists?  Are they 
> supposed to use their non-IDN address if there are any IDN-incapable 
> subscribers?  How will they know?

Same as mentioned above, during the transition, some people will have
both E-mail addresses, IDN and non-IDN, (by the way it is not unusual
for people to have and manage more than one E-mail address -- example
they have both a private and work related addresses) those who do, would
put their non-IDN and IDN address as part of their signature and those
who chose to reply to them would use the address they are capable of
using.

If it is a true mailing list, all the non-IDN subscribers who wish to
reply to the sender would actually send to the mailing-list and the
mailing list would forward it to the IDN address.  If the mailing list
didn't handle IDN addresses, the person with the IDN-address would know
from the very beginning because he would not get any replies (including
the one that said that he had joined) and would use his non-IDN address
to send to the mailing list.  He may then contact the mailing list owner
and ask why he doesn't handle IDN address and a long with other request,
the mailing list my be updated.

Again this is my whole point, if there is no pressure to upgrade, then
it will either take a long time (10 years or longer as people mention)
or it won't happen at all to move to UTF-8, and IMHO if we go with an
ACE only solution, it will never go away in the long run.  

I see no wrong asking users to take some of the responsibility of moving
to a new technology (i.e. having two addresses, adding a line as part of
the signature pointing to non-IDN address, requesting System-Operators
to upgrade)?  I know that this will be uncomfortable for users in the
beginning, but because of this, there will be more pressure to upgrade
to the new IDN standard and thus the final solution (UTF8) will be
reached sooner.

Regards, Russ
Microsoft -- rrolfe@microsoft.com


-----Original Message-----
From: Adam M. Costello [mailto:amc@cs.berkeley.edu] 
Sent: Saturday, July 14, 2001 2:18 PM
To: idn@ops.ietf.org
Subject: Re: [idn] Reality Check


Russ Rolfe <rrolfe@windows.microsoft.com> wrote:

> ...people will use both IDN and non-IDN address until every they need 
> to communicate can...

Are you arguing that ACE is unnecessary?  If so, please explain how
email is going to work.  What is supposed to happen when IDN-capable
person A sends a message to IDN-capable person B, who then forwards the
message to IDN-incapable person C, who would like to reply to A?  What
is supposed to happen when IDN-capable people send email to mailing
lists?  Are they supposed to use their non-IDN address if there are any
IDN-incapable subscribers?  How will they know?

> I have read a lot of comments on this list that state that ACE is just

> an intermediate step to help us get to a UTF-8 solution.

I don't agree with those comments.  While I can see ACE becoming less
common over time, I wouldn't expect it to completely die out in the
forseeable future.

AMC




From owner-idn@ops.ietf.org  Mon Jul 16 15:21:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA21910
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 15:21:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MDPw-0003Mk-00
	for idn-data@psg.com; Mon, 16 Jul 2001 11:48:28 -0700
Received: from sh.lh.vix.com ([204.152.188.26])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MDPw-0003Ma-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 11:48:28 -0700
Received: from KEYSER (sh.lh.vix.com [204.152.188.26]) 
	by sh.lh.vix.com (8.11.2/8.9.1) via ESMTP id f6GImFf28091
	for <idn@ops.ietf.org>; Mon, 16 Jul 2001 11:48:15 -0700 (PDT)
	env-from (pvm@a21.com)
Message-Id: <4.2.0.58.20010716114701.02405d90@127.0.0.1>
X-Sender: pvm@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Mon, 16 Jul 2001 11:49:00 -0700
To: idn working group <idn@ops.ietf.org>
From: "Paul V. Mockapetris" <pvm@a21.com>
Subject: RE: [idn] pool deadline imminent
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hi,

I believe UTF8 solutions deserve consideration as well.


paul



From owner-idn@ops.ietf.org  Mon Jul 16 16:16:23 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA01720
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 16:16:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MEWR-0006hE-00
	for idn-data@psg.com; Mon, 16 Jul 2001 12:59:15 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MEWQ-0006h2-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 12:59:14 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA11442;
        Mon, 16 Jul 2001 15:59:02 -0400 (EDT)
Message-Id: <200107161959.PAA11442@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: *click* <lucid@epa.secret.org>
cc: idn working group <idn@ops.ietf.org>,
        Russ Rolfe <rrolfe@windows.microsoft.com>,
        Martin Duerst <duerst@w3.org>
Subject: Re: [idn] pool deadline imminent 
In-reply-to: Your message of "Mon, 16 Jul 2001 14:27:52 EDT."
             <Pine.BSF.4.33.0107161421280.33288-100000@epa.secret.org> 
Date: Mon, 16 Jul 2001 15:59:02 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> I am in support of any UTF-8 based solution and am willing to help
> contribute if anyone is working on such a draft.

without details of such a solution, seems like such a statement is
fairly meaningless...or at least difficult to evaluate.



From owner-idn@ops.ietf.org  Mon Jul 16 17:31:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA14683
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 17:31:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MFog-000Ana-00
	for idn-data@psg.com; Mon, 16 Jul 2001 14:22:10 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MFof-000AnD-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 14:22:10 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id XAA05552;
	Mon, 16 Jul 2001 23:21:19 +0200 (MET DST)
Date: Mon, 16 Jul 2001 22:21:27 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Russ Rolfe <rrolfe@windows.microsoft.com>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: RE: [idn] Reality Check
Message-ID: <1014184.995322087@localhost>
In-Reply-To: <8CC03F47967BF14D9710887723FADDB687E3B1@win-msg-02.wingroup.windeploy.ntdev.microsoft.com>
References:  <8CC03F47967BF14D9710887723FADDB687E3B1@win-msg-02.wingroup.wind
 eploy.ntdev.microsoft.com>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-07-16 11.03 -0700 Russ Rolfe <rrolfe@windows.microsoft.com> wrote:

> I see no wrong asking users to take some of the responsibility of moving
> to a new technology (i.e. having two addresses, adding a line as part of
> the signature pointing to non-IDN address, requesting System-Operators
> to upgrade)?  I know that this will be uncomfortable for users in the
> beginning, but because of this, there will be more pressure to upgrade
> to the new IDN standard and thus the final solution (UTF8) will be
> reached sooner.

Being a bit pessimistic on the ability for end users to make software
developers and system managers (yes, I was one of them for some 10 years)
to upgrade, I say we should look at the bad handling of MIME which make
client and server software still not handling mime correctly.

But, due to the ascii encoding MIME has (for example in the headers) makes
it possible for people to communicate just because the encodings are 100%
backward compatible with the standard.

I did interoperability tests for MIME during the 90's, and even though we
had minimal requirements, it took software manufacturers _years_ to handle
the things correctly.

It's also the case that I only see "I support UTF-8" when a real solution
with UTF-8 would be something like IDNA, with UTF-8 as the output and not
ACE encoded strings, let's call it INDU. :-)

Because of the fact that some software already do UTF-8 (without nameprep),
and people on this list which should know better say "UTF-8 and not ACE"
when they should point at the actual algorithm used, I am extremely worried
that what I see on this list is IDNA (which include nameprep) or "just send
UTF-8 without nameprep". In reality that is.

Is that what people want?

Is that not what people will get?

If not, explain how the software which today send UTF-8 on the wire will
stop doing that the day we release the IDNU proposal? Who will suffer and
discover what software do nameprep and not?

  paf




From owner-idn@ops.ietf.org  Mon Jul 16 17:43:23 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA16763
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 17:43:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MFb7-000A7E-00
	for idn-data@psg.com; Mon, 16 Jul 2001 14:08:09 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MFb6-000A76-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 14:08:08 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15MFb1-0003MO-00; Mon, 16 Jul 2001 14:08:03 -0700
Date: Mon, 16 Jul 2001 21:08:03 +0000
To: IDN <idn@ops.ietf.org>
Subject: Re: [idn] proposals and deadlines
Message-ID: <20010716210803.F12031@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B5269EB.5E9999B7@ehsco.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

"Eric A. Hall" <ehall@ehsco.com> wrote:

> This would break things that rely on the domain name being preserved.
> With X.509 the client and the server have to agree on the domain name,
> for example.  If the resolver recombobulates a UTF-8 domain name from
> ACE output, then the client and server are likely to have different
> ideas of what the domain name should be.

Not so.  This is exactly what nameprep is for.  By definition, two names
X and Y are equal iff nameprep(X) and nameprep(Y) are byte-for-byte
equal.  The "recombobulated" name Y will always be equal to the original
name X according to this definition.  If an application works for X
but fails for Y then the application is broken, not the DNS.  Even
if DNS didn't use ACE, you never know when a domain name might get
transferred across some 7-bit protocol, so all applications must respect
this definition of equality.

AMC



From owner-idn@ops.ietf.org  Mon Jul 16 17:49:25 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA17556
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 17:49:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MFwQ-000BHo-00
	for idn-data@psg.com; Mon, 16 Jul 2001 14:30:10 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MFwQ-000BHi-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 14:30:10 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15MFwP-0003Or-00; Mon, 16 Jul 2001 14:30:09 -0700
Date: Mon, 16 Jul 2001 21:30:09 +0000
To: idn working group <idn@ops.ietf.org>
Subject: Re: [idn] Why follow IDNA with UTF-8?
Message-ID: <20010716213009.G12031@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <200107161750.NAA10522@astro.cs.utk.edu> <171080.995308028@localhost>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Patrik Fältström <paf@cisco.com> wrote:

> What Paul and I want to say is that the zone data (in some meta-way)
> is ACE encoded in the master server, and the master server operates on
> that data.

I don't recommend trying to talk about how the names are represented
internally.  Perhaps the idea you want to express is this:  An ASCII
query Q matches a name N iff Q matches ace(nameprep(N)) using a
case-insensitive ASCII comparison.  One obvious (but not required)
implementation strategy is for the server to precompute ace(nameprep(N))
for each name N when it starts up, and then act just like an old
ASCII-only DNS server.  Another strategy is to use a separate
preprocessor to perform ace(nameprep(N)) on the master file, and
actually use an old ASCII-only DNS server.

Keith Moore <moore@cs.utk.edu> wrote:

> perhaps we should state things in terms of "exchange format" and
> "local format".
>
> "exchange format" is the format used to exchange zones in a flat file;
> DNS implementations should be able to dump and accept zones in that
> format. for the time being, it should use ACE, for compatibility with
> old DNS implementations.
>
> "local format" can be anything the DNS implementation wants (web form
> input, XML, S-expressions, Morse code, whatever) and the standard
> shouldn't place any restrictions on it.

I like this.

AMC



From owner-idn@ops.ietf.org  Mon Jul 16 17:52:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA18252
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 17:52:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MFoV-000AnK-00
	for idn-data@psg.com; Mon, 16 Jul 2001 14:21:59 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MFoU-000Ams-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 14:21:58 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id XAA05564;
	Mon, 16 Jul 2001 23:21:23 +0200 (MET DST)
Date: Mon, 16 Jul 2001 22:21:57 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: "Paul V. Mockapetris" <pvm@a21.com>, idn working group <idn@ops.ietf.org>
Subject: RE: [idn] pool deadline imminent
Message-ID: <1015970.995322117@localhost>
In-Reply-To: <4.2.0.58.20010716114701.02405d90@127.0.0.1>
References:  <4.2.0.58.20010716114701.02405d90@127.0.0.1>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-07-16 11.49 -0700 "Paul V. Mockapetris" <pvm@a21.com> wrote:

> I believe UTF8 solutions deserve consideration as well.

Please explain what you mean by UTF8 solutions?

  paf




From owner-idn@ops.ietf.org  Mon Jul 16 18:18:32 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA22064
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 18:18:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MGJE-000CUo-00
	for idn-data@psg.com; Mon, 16 Jul 2001 14:53:44 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MGJE-000CUi-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 14:53:44 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15MGJD-0003QX-00; Mon, 16 Jul 2001 14:53:43 -0700
Date: Mon, 16 Jul 2001 21:53:43 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Reality Check
Message-ID: <20010716215343.H12031@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1014184.995322087@localhost> <8CC03F47967BF14D9710887723FADDB687E3B1@win-msg-02.wingroup.windeploy.ntdev.microsoft.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Russ Rolfe <rrolfe@windows.microsoft.com> wrote:

> I see no wrong asking users to take some of the responsibility of
> moving to a new technology (i.e. having two addresses, adding a line
> as part of the signature pointing to non-IDN address, requesting
> System-Operators to upgrade)?

In other words, you'd rather create technical difficulties for users in
order to ease the technical burden on engineers (by freeing them from
ACE).  I'll concede that it may be possible to do so, but in my opinion
it's the wrong tradeoff.  Users are far more numerous than engineers,
and less able to deal with technical challenges.  I think it makes more
sense to increase the technical burden on the engineers in order to make
things easier for the users.

> IMHO if we go with an ACE only solution, it will never go away in the
> long run.

If the engineers really hate ACE, they will move toward other mechanisms
at every opportunity, and ACE will become less common over time.  If
the engineers don't mind using ACE, then there's no problem with it
remaining common forever.

In either case, I think the desire of users to see the native characters
will be sufficient pressure to make ACEs very rarely visible to users.
After that, users won't care whether ACE is truly gone or merely hidden.

Patrik Fältström <paf@cisco.com> wrote:

> I am extremely worried that what I see on this list is IDNA (which
> include nameprep) or "just send UTF-8 without nameprep".

Nitpick:  The problem isn't sending non-nameprep'd UTF-8.  The problem
is receiving UTF-8 and neglecting to run nameprep on it before comparing
it with something.  Even with ACE, after a receiver decodes the ACE
to obtain a Unicode name X, it must verify that X == nameprep(X),
otherwise it's susceptible to spoofing.  But you still have a point:
The ACE-decoding function is likely to have the nameprep check built in,
whereas nameprep is more likely to be forgotten if UTF-8 is received.
Still, I don't think we could stop new protocols from using UTF-8,
and I don't think we'd even want to, so we just have to emphasize the
importance of using nameprep for comparing IDNs.

AMC



From owner-idn@ops.ietf.org  Mon Jul 16 19:18:41 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA01729
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 19:18:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MHLd-000G2s-00
	for idn-data@psg.com; Mon, 16 Jul 2001 16:00:17 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MHLb-000G2H-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 16:00:16 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6GMxKp02718;
	Tue, 17 Jul 2001 07:59:21 +0900 (KST)
Message-ID: <00e601c10e4b$c7fbf980$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Keith Moore" <moore@cs.utk.edu>, "Eric A. Hall" <ehall@ehsco.com>
Cc: "Patrik F?tstr?" <paf@cisco.com>, "Adam M. Costello" <amc@cs.berkeley.edu>,
        "idn working group" <idn@ops.ietf.org>
References: <200107161802.OAA10676@astro.cs.utk.edu>
Subject: Re: [idn] Why follow IDNA with UTF-8? 
Date: Tue, 17 Jul 2001 08:05:12 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

We can verify whether a ACE label is NAMEPREPed one or not
by re-applying NAMEPREP process to ACE-decoding-produced
code points and see if any changes.

Soobok lee
----- Original Message -----
From: "Keith Moore" <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
Cc: "Patrik F?tstr?" <paf@cisco.com>; "Adam M. Costello"
<amc@cs.berkeley.edu>; "idn working group" <idn@ops.ietf.org>
Sent: Tuesday, July 17, 2001 3:02 AM
Subject: Re: [idn] Why follow IDNA with UTF-8?


> > Just-use-ACE is actually the most succeptible to this particular
problem,
> > since old and new applications pass data into the system through the old
> > APIs equally, without any distinctive markings. Was it nameprepped?
nobody
> > knows...
>
> ACE is sufficiently ugly that it's difficult to imagine that it will be
produced
> other than by calling the APIs that produce it - and those APIs will
support
> nameprep.
>




From owner-idn@ops.ietf.org  Mon Jul 16 20:14:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA13444
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 20:14:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MHfH-000H82-00
	for idn-data@psg.com; Mon, 16 Jul 2001 16:20:35 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MHfC-000H6p-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 16:20:31 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6GNIxp04141;
	Tue, 17 Jul 2001 08:18:59 +0900 (KST)
Message-ID: <00fe01c10e4e$833c7560$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Patrik F?tstr?" <paf@cisco.com>, "Martin Duerst" <duerst@w3.org>,
        <idn@ops.ietf.org>
References:  <4.2.0.58.J.20010716143102.038bd920@sh.w3.mag.keio.ac.jp> <222306.995308883@localhost>
Subject: Re: [idn] IDN security and ACE leakage
Date: Tue, 17 Jul 2001 08:24:50 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Patrik F?tstr?" <paf@cisco.com>

> fault? Maybe because I did choose to use a charset you can not support,
and
> that is a valid issue, but if you DO handle the charset, or if you don't,
> how do your client handle that situation? _Those_ situations are what we
> should talk about and not this smalltalk about "my software is better than
> yours".

Could NAMEPREP elminate all the script/glyph ambiguities across
languages?

katakana 'ka' and chinese letter 'power(U+529B)' look the same.
When we normalize them in either directions, there may be conflict of
interests between  Japan and China.

Soobok Lee

>
>    paf
>




From owner-idn@ops.ietf.org  Mon Jul 16 22:22:25 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA06383
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 22:22:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MJPT-000Nka-00
	for idn-data@psg.com; Mon, 16 Jul 2001 18:12:23 -0700
Subject: [idn] RE: UTF-8 as the long-term IDN solution
Date: Mon, 16 Jul 2001 11:47:08 -0700
From: "Ian King" <iking@microsoft.com>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15MJPT-000Nka-00@psg.com>

Sounds to me like this is the ADs' job.  I know that in the past, I've
seen an AD replace a chair who was not forwarding the work of the group.
Obviously, it's a pretty extreme remedy. =20

Do NOT intepret this as an endorsement from me that a particular chair
needs to be replaced; I'm only commenting on process.  -- Ian=20

-----Original Message-----
From: D. J. Bernstein [mailto:djb@cr.yp.to]=20
Sent: Monday, July 16, 2001 10:29 AM
To: idn@ops.ietf.org; iesg@ietf.org; poised@lists.tislabs.com
Subject: Re: UTF-8 as the long-term IDN solution


Keith Moore writes:
 > I believe this is adequately addressed in RFC 2026, section 6.5.

I don't see how.

RFC 2026, section 6.5, is for cases where someone disagrees with ``a
Working Group recommendation.''

What's happening in this case is completely different. There is no
recommendation. There are a huge number of WG members who

    (1) agree that UTF-8 will be the long-term solution;
    (2) suspect that there's consensus in the WG on #1; and
    (3) believe that establishing consensus would save time for the WG.

But the chair, who disagrees with #1, is stonewalling, in violation of
his responsibility under RFC 2418 to ensure forward progress.

As you can see from http://cr.yp.to/djbdns/namedroppers.html, I've
already tried using the RFC 2026 process to handle procedural problems,
specifically DNSEXT mailing list censorship, which has been roundly
criticized in POISSON recently. The process took more than two years.
The basic problem still isn't fixed.

I don't want IDN to wait two years. There needs to be a mechanism for
the WG to act over the opposition of the chair. IETF doesn't seem to
have any such mechanism.

---Dan






From owner-idn@ops.ietf.org  Mon Jul 16 22:45:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA10083
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 22:45:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MJR4-000Npz-00
	for idn-data@psg.com; Mon, 16 Jul 2001 18:14:02 -0700
From: Jeff Williams <jwkckid1@ix.netcom.com>
To: "D. J. Bernstein" <djb@cr.yp.to>
CC: idn@ops.ietf.org, iesg@ietf.org, poised@lists.tislabs.com
Subject: Re: [idn] UTF-8 as the long-term IDN solution
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15MJR4-000Npz-00@psg.com>
Date: Mon, 16 Jul 2001 18:14:02 -0700

D.J. And all,

  I agree with D.J. here that a straw poll would be a good idea at this
juncture.

D. J. Bernstein wrote:

> James Seng/Personal writes:
> > I requested you to point to an internet draft
>
> Your request is noted.
>
> In the meantime, please run the poll. A two-week poll will leave
enough
> time for people to get back from vacation. The agree/disagree
statement,
> as I've told you repeatedly, is as follows: ``The long-term IDN
solution
> will encode Unicode characters as UTF-8 on the wire.''
>
> I think we have consensus on this one aspect of what's going to
happen.
> If I'm right, then we can stop wasting time discussing silly
ACE-forever
> scenarios that aren't going to happen. Please stop stonewalling.
>
> > strawpoll for individual whims
>
> Excuse me? Many people have announced their support for UTF-8 as the
> long-term solution. Only a few people have objected. When you stalled
by
> saying ``I would like to hear some support on this before we run this
> poll,'' you immediately saw some public messages of support. For
> example, here's what Bruce Thomson said:
>
>    It is likely that we have consensus on this point, and it would be
>    well worth the effort of a straw poll to establish this, so we can
>    move on.
>
> How you can call this an ``individual whim'' is beyond me.
>
> ---Dan

Regards,

--
Jeffrey A. Williams
Spokesman for INEGroup - (Over 118k members strong!)
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number:  972-447-1800 x1894 or 214-244-4827
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208







From owner-idn@ops.ietf.org  Mon Jul 16 22:52:25 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA10835
	for <idn-archive@lists.ietf.org>; Mon, 16 Jul 2001 22:52:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MJcM-000OSh-00
	for idn-data@psg.com; Mon, 16 Jul 2001 18:25:42 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MJcK-000ONt-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 18:25:41 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 27876FFC03; Tue, 17 Jul 2001 09:25:02 +0800 (SGT)
Message-ID: <054d01c10e5f$01b27880$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>, <iesg@ietf.org>,
        <poised@lists.tislabs.com>
References: <Pine.BSF.4.21.0107161026550.12160-100000@two.elistx.com> <200107161523.LAA09625@astro.cs.utk.edu> <20010716172841.10339.qmail@cr.yp.to>
Subject: [idn] Re: UTF-8 as the long-term IDN solution
Date: Tue, 17 Jul 2001 09:22:55 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dan,

Once again, let me clarify: the chairs do not have any opinion on #1.
(In fact, I think you can put me in group #2).

But what we need is a draft, not an idea. Please point us to the draft
which you are supporting or write one. No drafts, no face-time, no RFC,
something I expected a long-time IETFer like you should be aware of.

-James Seng

----- Original Message -----
From: "D. J. Bernstein" <djb@cr.yp.to>
To: <idn@ops.ietf.org>; <iesg@ietf.org>; <poised@lists.tislabs.com>
Sent: Tuesday, July 17, 2001 1:28 AM
Subject: Re: UTF-8 as the long-term IDN solution


> Keith Moore writes:
>  > I believe this is adequately addressed in RFC 2026, section 6.5.
>
> I don't see how.
>
> RFC 2026, section 6.5, is for cases where someone disagrees with ``a
> Working Group recommendation.''
>
> What's happening in this case is completely different. There is no
> recommendation. There are a huge number of WG members who
>
>     (1) agree that UTF-8 will be the long-term solution;
>     (2) suspect that there's consensus in the WG on #1; and
>     (3) believe that establishing consensus would save time for the
WG.
>
> But the chair, who disagrees with #1, is stonewalling, in violation of
> his responsibility under RFC 2418 to ensure forward progress.
>
> As you can see from http://cr.yp.to/djbdns/namedroppers.html, I've
> already tried using the RFC 2026 process to handle procedural
problems,
> specifically DNSEXT mailing list censorship, which has been roundly
> criticized in POISSON recently. The process took more than two years.
> The basic problem still isn't fixed.
>
> I don't want IDN to wait two years. There needs to be a mechanism for
> the WG to act over the opposition of the chair. IETF doesn't seem to
> have any such mechanism.
>
> ---Dan
>




From owner-idn@ops.ietf.org  Tue Jul 17 00:14:28 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA20437
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 00:14:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MLcP-0001k0-00
	for idn-data@psg.com; Mon, 16 Jul 2001 20:33:53 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MLcO-0001ju-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 20:33:52 -0700
Received: from bbthead.brandenburg.com (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id UAA11689;
	Mon, 16 Jul 2001 20:33:46 -0700
Message-Id: <5.1.0.14.2.20010716202954.033e4140@brandenburg.com>
X-Sender: dcrocker@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 16 Jul 2001 20:32:37 -0700
To: "Ian King" <iking@microsoft.com>
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: [idn] RE: UTF-8 as the long-term IDN solution
Cc: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>, <iesg@ietf.org>,
        <poised@lists.tislabs.com>
In-Reply-To: <8D25F244B8274141B5D313CA4823F39C018EF070@red-msg-06.redmon
 d.corp.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 11:47 AM 7/16/2001, Ian King wrote:
>Sounds to me like this is the ADs' job.  I know that in the past, I've
>seen an AD replace a chair who was not forwarding the work of the group.
>Obviously, it's a pretty extreme remedy.

Folks, unfortunately the IETF is mostly populated by well-meaning, earnest 
people who take all criticisms seriously.

It leaves us open to a deprivation of service attack by the occasional 
participant who is more interested in disruption than in progress.

Continued responses on the mailing list, to Dan's limited but peristent 
variety of harangues serve only to distract the group.

I strongly urge all non-"management" personnel (ie, anyone not a WG chair 
or an AD) to refrain from responding to Dan's periodic challenges... unless 
of course you really, really, REALLY believe he is raising a major 
criticism that has strong validity.

d/


----------
Dave Crocker  <mailto:dcrocker@brandenburg.com>
Brandenburg InternetWorking  <http://www.brandenburg.com>
tel +1.408.246.8253;  fax +1.408.273.6464




From owner-idn@ops.ietf.org  Tue Jul 17 00:14:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA20443
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 00:14:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MLcU-0001k8-00
	for idn-data@psg.com; Mon, 16 Jul 2001 20:33:58 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MLcT-0001k2-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 20:33:58 -0700
Received: from bbthead.brandenburg.com (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id UAA11686;
	Mon, 16 Jul 2001 20:33:45 -0700
Message-Id: <5.1.0.14.2.20010716202749.02227ad8@brandenburg.com>
X-Sender: dcrocker@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 16 Jul 2001 20:29:17 -0700
To: "D. J. Bernstein" <djb@cr.yp.to>
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: [idn] Re: UTF-8 as the long-term IDN solution
Cc: idn@ops.ietf.org, iesg@ietf.org, poised@lists.tislabs.com
In-Reply-To: <20010715203004.30572.qmail@cr.yp.to>
References: <E15LLxX-000G18-00@psg.com>
 <20010714211816.D31484@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 01:30 PM 7/15/2001, D. J. Bernstein wrote:
>I accuse the chairs of bias in their selection of polls. They appear to
>be running polls that they believe will promote their personal agendas,
>and refusing to run any other polls. Does the IETF have any procedures
>to fix this problem?

Dan, you have raised similar complaints many times in recent years.  You 
have had IETF procedures and procedural documents explained to you many times.

Please follow those procedures or please refrain from disrupting working 
group processes.

d/


----------
Dave Crocker  <mailto:dcrocker@brandenburg.com>
Brandenburg InternetWorking  <http://www.brandenburg.com>
tel +1.408.246.8253;  fax +1.408.273.6464




From owner-idn@ops.ietf.org  Tue Jul 17 00:26:28 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA22937
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 00:26:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MMAl-0002hA-00
	for idn-data@psg.com; Mon, 16 Jul 2001 21:09:23 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MMAk-0002h3-00
	for idn@ops.ietf.org; Mon, 16 Jul 2001 21:09:22 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id GAA16262;
	Tue, 17 Jul 2001 06:09:07 +0200 (MET DST)
Date: Tue, 17 Jul 2001 06:06:04 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Soobok Lee <lsb@postel.co.kr>, Martin Duerst <duerst@w3.org>,
        idn@ops.ietf.org
Subject: Re: [idn] IDN security and ACE leakage
Message-ID: <1645717.995349964@localhost>
In-Reply-To: <00fe01c10e4e$833c7560$ed1bd9d2@postel.co.kr>
References:  <4.2.0.58.J.20010716143102.038bd920@sh.w3.mag.keio.ac.jp>
 <222306.995308883@localhost> <00fe01c10e4e$833c7560$ed1bd9d2@postel.co.kr>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-07-17 08.24 +0900 Soobok Lee <lsb@postel.co.kr> wrote:

> ----- Original Message -----
> From: "Patrik F?tstr?" <paf@cisco.com>
> 
>> fault? Maybe because I did choose to use a charset you can not support,
> and
>> that is a valid issue, but if you DO handle the charset, or if you don't,
>> how do your client handle that situation? _Those_ situations are what we
>> should talk about and not this smalltalk about "my software is better
>> than yours".
> 
> Could NAMEPREP elminate all the script/glyph ambiguities across
> languages?
> 
> katakana 'ka' and chinese letter 'power(U+529B)' look the same.
> When we normalize them in either directions, there may be conflict of
> interests between  Japan and China.

I have not claimed nameprep do solve all problems, but, we have agreed on
this list that what is needed for interoperability is that everyone uses
the same algorithm when doing nameprep, and that that should be applied
before strings are compared.

Now, if you are unhappy with the current definition of nameprep, please
come with suggestions on how it can be approved.

  paf




From owner-idn@ops.ietf.org  Tue Jul 17 02:03:32 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA22645
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 02:03:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MNP0-0004WD-00
	for idn-data@psg.com; Mon, 16 Jul 2001 22:28:10 -0700
Date: Tue, 17 Jul 2001 00:12:19 -0700
From: Jeff Williams <jwkckid1@ix.netcom.com>
Organization: INEGroup Spokesman
To: Dave Crocker <dcrocker@brandenburg.com>
CC: poised@lists.tislabs.com
Subject: [idn] Re: UTF-8 as the long-term IDN solution
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15MNP0-0004WD-00@psg.com>

Dave and all,

  Well than why are you responding here Dave? This has made
the third response to Dan thus far on this thread.  Has your Troll virus
got the better of you again?  See: http://www.dnso.com/incompetence/
for reference...

Dave Crocker wrote:

> At 11:47 AM 7/16/2001, Ian King wrote:
> >Sounds to me like this is the ADs' job.  I know that in the past,
I've
> >seen an AD replace a chair who was not forwarding the work of the
group.
> >Obviously, it's a pretty extreme remedy.
>
> Folks, unfortunately the IETF is mostly populated by well-meaning,
earnest
> people who take all criticisms seriously.
>
> It leaves us open to a deprivation of service attack by the occasional
> participant who is more interested in disruption than in progress.
>
> Continued responses on the mailing list, to Dan's limited but
peristent
> variety of harangues serve only to distract the group.
>
> I strongly urge all non-"management" personnel (ie, anyone not a WG
chair
> or an AD) to refrain from responding to Dan's periodic challenges...
unless
> of course you really, really, REALLY believe he is raising a major
> criticism that has strong validity.
>
> d/
>
> ----------
> Dave Crocker  <mailto:dcrocker@brandenburg.com>
> Brandenburg InternetWorking  <http://www.brandenburg.com>
> tel +1.408.246.8253;  fax +1.408.273.6464

Regards,

--
Jeffrey A. Williams
Spokesman for INEGroup - (Over 118k members strong!)
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number:  972-447-1800 x1894 or 214-244-4827
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208








From owner-idn@ops.ietf.org  Tue Jul 17 04:33:30 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24253
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 04:33:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MPeX-0008E9-00
	for idn-data@psg.com; Tue, 17 Jul 2001 00:52:21 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MPeS-0008Dq-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 00:52:16 -0700
Received: from enoshima (dhcp-100-151.mag.keio.ac.jp [133.27.195.151])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id QAA08405;
	Tue, 17 Jul 2001 16:48:30 +0900 (JST)
Message-Id: <4.2.0.58.J.20010717154931.03f7b130@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 17 Jul 2001 16:48:04 +0900
To: Patrik F=?ISO-2022-JP?B?GyRCZ00bKEI=?=tstr
 =?ISO-2022-JP?B?GyRCi04bKEI=?= <paf@cisco.com>,
        Russ Rolfe <rrolfe@windows.microsoft.com>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check)
In-Reply-To: <1014184.995322087@localhost>
References: <8CC03F47967BF14D9710887723FADDB687E3B1@win-msg-02.wingroup.windeploy.ntdev.microsoft.com>
 <8CC03F47967BF14D9710887723FADDB687E3B1@win-msg-02.wingroup.wind eploy.ntdev.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

At 22:21 01/07/16 +0200, Patrik F$BgM(Btstr$B‹N(B wrote:

>It's also the case that I only see "I support UTF-8" when a real solution
>with UTF-8 would be something like IDNA, with UTF-8 as the output and not
>ACE encoded strings, let's call it INDU. :-)

Yes. Actually it would be quite easy to convert the IDNA draft to an IDNU
draft, more or less by replacing ACE with UTF-8. Of course a second pass
to smoothen some edges may be required.


>Because of the fact that some software already do UTF-8 (without nameprep),
>and people on this list which should know better say "UTF-8 and not ACE"
>when they should point at the actual algorithm used, I am extremely worried
>that what I see on this list is IDNA (which include nameprep) or "just send
>UTF-8 without nameprep". In reality that is.

Just send UTF-8 with nameprep is definitely what's needed, much better
than just send UTF-8 without nameprep.


>If not, explain how the software which today send UTF-8 on the wire will
>stop doing that the day we release the IDNU proposal? Who will suffer and
>discover what software do nameprep and not?

This software will most probably be upgraded. If it's browsers,
I'll definitely contribute by talking to the right people. I'm very
sure browser vendors prefer UTF-8 with nameprep over ACE with nameprep.

Anyway, I think that nameprep is in various ways very important, but
on the other hand, its importance has also been highly overestimated.
So the amount of suffering is much more limited than it may seem.

It is very important to understand that in most contexts, the chance
that a label is changed (except for lowercasing, which was part of
the UTF-8 proposal from the start) by nameprep when somebody takes a
proper domain name from paper and inputs it, is *very* small.
There are some well-known and important exceptions such as 
half-width/full-width
kana, and some implementations of Vietnamese (windows-1258), but for
many areas of the world, nameprep, in its relevant parts, just
conforms what's done anyway.

The reason for this is that this property is *designed* into NFC, and
that most of NFK (but not all of it) is garbage collection and includes
many things that are in some way similar but that the user would never
want to type in (because they really look different from the real thing),
and in addition are difficult to type; a lot of examples can e.g. be
found in blocks U+32xx and U+33xx).

So what we very much need is a very clear definition of which names are
acceptable and which names are not acceptable, and a high-enough
checking/compliance rate (somewhere between 50% and 90%) on the request
side to put enough pressure on the registry side to make that side of
compliance 100%.

What is also quite beneficial is to have some clear guidelines as to
what characters should be mapped to others before lookup and what not.
Half-width/full-width is a typical example. But currently, we are e.g.
forbidding somebody who makes Turkish software to use the case mapping
that a Turkish user would expect, just because we want to avoid
problems if ever a user without an idea about Turkish casing rules
uses that software. The current tendencies of 'better check once too much
than not enough times' (to which I agree in principle) and 'better uniform
and sometimes wrong than according to user expectations' (about which I
have serious doubts) seem to have lead us to overshoot our goals.


Regards,    Martin.











From owner-idn@ops.ietf.org  Tue Jul 17 04:45:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA25541
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 04:45:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MPti-0008bR-00
	for idn-data@psg.com; Tue, 17 Jul 2001 01:08:02 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MPtd-0008bK-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 01:08:01 -0700
Received: from enoshima (dhcp-100-151.mag.keio.ac.jp [133.27.195.151])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id RAA08492;
	Tue, 17 Jul 2001 17:07:50 +0900 (JST)
Message-Id: <4.2.0.58.J.20010717170019.009d9650@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 17 Jul 2001 17:07:23 +0900
To: "Adam M. Costello" <amc@cs.berkeley.edu>, IDN <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] proposals and deadlines
In-Reply-To: <20010716210803.F12031@arwen.cs.berkeley.edu>
References: <3B5269EB.5E9999B7@ehsco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 21:08 01/07/16 +0000, Adam M. Costello wrote:
>"Eric A. Hall" <ehall@ehsco.com> wrote:
>
> > This would break things that rely on the domain name being preserved.
> > With X.509 the client and the server have to agree on the domain name,
> > for example.  If the resolver recombobulates a UTF-8 domain name from
> > ACE output, then the client and server are likely to have different
> > ideas of what the domain name should be.
>
>Not so.  This is exactly what nameprep is for.  By definition, two names
>X and Y are equal iff nameprep(X) and nameprep(Y) are byte-for-byte
>equal.  The "recombobulated" name Y will always be equal to the original
>name X according to this definition.  If an application works for X
>but fails for Y then the application is broken, not the DNS.  Even
>if DNS didn't use ACE, you never know when a domain name might get
>transferred across some 7-bit protocol, so all applications must respect
>this definition of equality.

Obviously ACE isn't needed here; the only condition is that you compare
them using the same encoding (UTF-8, today's choice of ACE, or whatever),
or you can compare characters directly.

And the above also shows the danger of doing too much folding in nameprep,
or at the wrong place. As much as possible, names should only be stored
in the namepreped version. In operational terms, it would be better if
a dn server would reject a zone file with non-namepreped names
(whether in ACE or in UTF-8 or whatever, as specified), and a nameprep
utility were available separately, than if everything would just get
namepreped without reflecting the errors back.


Regards,   Martin.



From owner-idn@ops.ietf.org  Tue Jul 17 05:26:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA29972
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 05:26:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MQg1-0009mR-00
	for idn-data@psg.com; Tue, 17 Jul 2001 01:57:57 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MQfX-0009l0-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 01:57:27 -0700
Received: from enoshima (dhcp-100-151.mag.keio.ac.jp [133.27.195.151])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id RAA08723;
	Tue, 17 Jul 2001 17:53:43 +0900 (JST)
Message-Id: <4.2.0.58.J.20010717171624.036459a0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 17 Jul 2001 17:52:16 +0900
To: Patrik F=?ISO-2022-JP?B?GyRCZ00bKEI=?=tstr
 =?ISO-2022-JP?B?GyRCi04bKEI=?= <paf@cisco.com>,
        idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] IDN security and ACE leakage
In-Reply-To: <222306.995308883@localhost>
References: <4.2.0.58.J.20010716143102.038bd920@sh.w3.mag.keio.ac.jp>
 <4.2.0.58.J.20010716143102.038bd920@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

At 18:41 01/07/16 +0200, Patrik F$BgM(Btstr$B‹N(B wrote:
>--On 01-07-16 14.36 +0900 Martin Duerst <duerst@w3.org> wrote:
>
> > Ideally, every person should at least have one purely
> > ASCII-only email address, and every machine should have
> > at least one purely ASCII-only domain name, not consisting
> > of characters that look like they come from a random generator.
>
>I don't agree.
>
>If people said this about some arabic script to me, I would not be able to
>know the difference between a random generated string in arabic compared to
>something which makes sense to people which know arabic (something I don't
>do).

Your example of Arabic may apply to some cases of people not having any
idea about Latin, but in general, Greek is a much better example.
Your knowledge of Greek letters is most probably much closer to
the average knowledge of Latin by somebody who doesn't use it as
their everyday script. If you had to use Greek in your email,
would you prefer it to use some appropriate letters, or would you
not care and just think random is as good as anything?


>I much rather be able to use my name, which I have chosen, in my script, in
>applications I have chosen, and then some magic which is implemented in the
>network which makes it possible for others to reply to my email.

If it's just about email replies, then MIME may already be enough
(assuming it's really implemented; not like what my mailer is doing :-(.
[For the web, the eqivalent is following a link.]

The main problem is getting the email address from the business card
to the MUA, or getting the web address from the product pamphlet,...
to the browser. For that, you may want to have an Arabic email address
if you are doing business in the Arabic region, even if you don't
speak a word of Arabic. And you will be wise to at least have an
ASCII-only email address, so that your business partners don't have
to try to get the special characters right. That's just a matter
of courtesy and common sense, and I don't think that will change
much with idn.


>If I have upgraded my software to be able to handle whatever IDN is coming
>up with, I should never have to see the encoded characters which are passed
>in the protocols -- regardless of if it is UTF-8 or ACE or whatever.
>
>As a user I don't care.

Agreed, except for wording. You would never want to see anything except
the encoded characters, regardless of whether the encoding is UTF-8 or
ACE or whatever.


>I want it to work. And to make it to work for users, we engineers have to
>be extremely conservative, and as you have understood by now, I don't care
>if some of you think I am stupid asking for something as stupid as ACE when
>UTF-8 is better. I am conservative, belive nameprep is by far more
>important than what encoding we use,

I think you take nameprep a tiny bit too serious. See my other mail.


>and IF we should do something smart,
>we should use neither UTF-8 nor ACE in DNS, but instead something much more
>efficient given the binary labels we already have in the DNS protocol.

Something like gzip on top of SCSU on top of frequency reordering
or so? Squeezing the last drop of inefficiency out of these labels.
Having the WG spend a few more years on the 'who's ace is better'
game? Or did I misunderstand you?


>But, as applications take the uncompressed data in the DNS protocol and
>"just" use it here and there, we need to see that that data is safe in
>whatever (stupid) application there is. If I have upgraded my applications,
>I am done. I will never see this encoding stuff anymore. Just like with
>quoted-printable in MIME. Do you see QP somewhere? Maybe in headers of
>email? Maybe even this email? Then you have broken software, but is that my
>fault? Maybe because I did choose to use a charset you can not support, and
>that is a valid issue, but if you DO handle the charset, or if you don't,
>how do your client handle that situation? _Those_ situations are what we
>should talk about and not this smalltalk about "my software is better than
>yours".

MIME was a pain for a long time. Where it still is a pain (including
my mailer), that may be blamed on the implementation. But the years it took
to reasonably deploy MIME cannot be blamed on any implementation, they have
to be blamed on MIME itself.

What you are saying is that because we have suffered with MIME, we can
suffer another time. We are in a much better position now (Unicode and
UTF-8 wasn't really an option when MIME was created), and that we should
not repeat the mistakes we know from the past. Just sending something
off and not caring about whether the recipients can really see it
or not (which is the basic idea behind ACE) is not a good idea.
If a specific protocol wants to work on that base, we may just
close our eyes. But to make it the central assumption on the
central infrastructure is a bad idea.


Regards,   Martin.








From owner-idn@ops.ietf.org  Tue Jul 17 05:58:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA03514
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 05:58:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MRA2-000AWa-00
	for idn-data@psg.com; Tue, 17 Jul 2001 02:28:58 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MRA1-000AWO-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 02:28:57 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id LAA28200;
	Tue, 17 Jul 2001 11:28:05 +0200 (MET DST)
Date: Tue, 17 Jul 2001 11:06:39 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Martin Duerst <duerst@w3.org>, Russ Rolfe <rrolfe@windows.microsoft.com>,
        idn@ops.ietf.org
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check)
Message-ID: <152039.995367999@localhost>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-07-17 16.48 +0900 Martin Duerst <duerst@w3.org> wrote:

> It is very important to understand that in most contexts, the chance
> that a label is changed (except for lowercasing, which was part of
> the UTF-8 proposal from the start) by nameprep when somebody takes a
> proper domain name from paper and inputs it, is *very* small.

We will have problems when domainnames are registered.

Say that someone send in request for registering domain A which is
correctly nameprepped. If someone else is sending in domain B for
registration which would be nameprepped into A, it is extremely important
that B is not registered, but instead this second person get to know that
B, converted to A, is already registered.

It is enough with only _one_ mistake (regardless of how small the risk is
that this happens) and we will have some definition of chaos.

I also ask myself this the last couple of days:

- This wg is about what is used in the DNS protocol.
- Many people want UTF-8 to be used in DNS.
- Application protocols do not use UTF-8 but ASCII (most of them).
- Someone (in Applications Area) have to write documents, one per protocol
  on how to pass Unicode characters in the protocols, how to handle
  downgrading to something else if needed (like 8BITMIME in SMTP) and
  for each protocol what the downgrade is to.

Conclusion:
- As many application protocols (like SMTP) can not use UTF-8 for a while
  should not DNS use some more efficient encoding than UTF-8 in the
  packets?

I claim that the actual encoding which is to be used in the DNS protocol is
something this wg can not come up with, but instead the DNSEXT wg in the
DNS is the correct group which is to come up with an encoding which is as
efficient as possible, given DNSSEC and other new things which they are
working with.

I further guess that when people in this wg talk about "we want UTF-8" they
really talk about what they want to use in the Application Layer protocols,
but defining that is really out of scope for this wg.

So be careful what you ask for!

Either this wg come up with something which is backward compatible with
other existing standards, or it comes up with a "framework" and give work
items for other wg's and leave it to them for standarization.

  paf




From owner-idn@ops.ietf.org  Tue Jul 17 06:10:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA04816
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 06:10:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MRQy-000Ax6-00
	for idn-data@psg.com; Tue, 17 Jul 2001 02:46:28 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MRQx-000Awl-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 02:46:28 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id LAA01466;
	Tue, 17 Jul 2001 11:46:06 +0200 (MET DST)
Date: Tue, 17 Jul 2001 11:44:20 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Martin Duerst <duerst@w3.org>, idn@ops.ietf.org
Subject: Re: [idn] IDN security and ACE leakage
Message-ID: <287643.995370260@localhost>
In-Reply-To: <4.2.0.58.J.20010717171624.036459a0@sh.w3.mag.keio.ac.jp>
References: <4.2.0.58.J.20010716143102.038bd920@sh.w3.mag.keio.ac.jp>
 <4.2.0.58.J.20010716143102.038bd920@sh.w3.mag.keio.ac.jp>
 <4.2.0.58.J.20010717171624.036459a0@sh.w3.mag.keio.ac.jp>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-07-17 17.52 +0900 Martin Duerst <duerst@w3.org> wrote:

>> If I have upgraded my software to be able to handle whatever IDN is
>> coming up with, I should never have to see the encoded characters which
>> are passed in the protocols -- regardless of if it is UTF-8 or ACE or
>> whatever.
>> 
>> As a user I don't care.
> 
> Agreed, except for wording. You would never want to see anything except
> the encoded characters, regardless of whether the encoding is UTF-8 or
> ACE or whatever.

My point is that as a user, I think there are two things that should work:

(a) When I have upgraded my own applications, I should see the real glyphs
on my monitor, my cut and paste should work, and I should be able to input
domainnames with whatever mechanism I choose. I don't care what encoding is
used for the glyphs when they are moved over the wire.

(b) When I send an email to someone which have NOT upgraded their software,
or via someone which have not upgraded their software, that other person
should get the email, and should be able to reply.

>> and IF we should do something smart,
>> we should use neither UTF-8 nor ACE in DNS, but instead something much
>> more efficient given the binary labels we already have in the DNS
>> protocol.
> 
> Something like gzip on top of SCSU on top of frequency reordering
> or so? Squeezing the last drop of inefficiency out of these labels.
> Having the WG spend a few more years on the 'who's ace is better'
> game? Or did I misunderstand you?

You exaggerate. We _do_ have problems with the size of the DNS packets.
Especially when we are trying to do DNSSEC. Because of this, what is stored
in the DNS packet, if the larger packet should be flagged with EDNS0.5
stuff for new content or whatever else is something I feel is not a task of
this wg to decide on.

I.e. that you as a member of this group didn't acknowledge the lack of
space in DNS packets show that probably someone else should look at this
problem?

So, in some form you are correct, I am talking about doing a more efficient
encoding as what is used there most certainly not will be used in
application layer protocols (at least not to start with). Some protocols
can be changed to use UTF-8 pretty quickly, but maybe other rather use
something else.

> MIME was a pain for a long time. Where it still is a pain (including
> my mailer), that may be blamed on the implementation. But the years it
> took to reasonably deploy MIME cannot be blamed on any implementation,
> they have to be blamed on MIME itself.

Point of clearification: I didn't pick mime just because I know your mailer
is not upgraded Martin.

> What you are saying is that because we have suffered with MIME, we can
> suffer another time.

No, what I am saying is that email works even though software is still not
upgraded just because MIME is 100% backward compatible.

> We are in a much better position now (Unicode and
> UTF-8 wasn't really an option when MIME was created), and that we should
> not repeat the mistakes we know from the past. Just sending something
> off and not caring about whether the recipients can really see it
> or not (which is the basic idea behind ACE) is not a good idea.

Well, you seem to argue for "just send UTF-8" and do not care about whether
the recipient can even do a reply to the mail.

I.e. both you and I use the same argument here, but for different "layers".

You say that something is broken if the recipient do not see the correct
glyphs. I say that something is broken if the recipient can not do reply
(or even see the email), but think that things work if the recipient see
the ACE encoding.

The good thing with IDNA and ACE is that it is 100% compatible with what is
in use today, and nothing will break. It is then up to each and every
individual to upgrade her software so the correct glyphs are displayed, and
so she can enter the correct glyphs.

If you choose something which is not, then we (a) have to go to the dnsext
wg and ask then to please come up with a solution for encoding Unicode in
DNS labels and (b) to every protocol wg and ask them for a transision plan
for moving to UTF-8, a plan which most certainly might include ACE
encodings when one communicate with old software.


   paf





From owner-idn@ops.ietf.org  Tue Jul 17 07:18:32 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA13456
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 07:18:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MSUv-000Cbl-00
	for idn-data@psg.com; Tue, 17 Jul 2001 03:54:37 -0700
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MSUu-000Cbe-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 03:54:36 -0700
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10607;
	Tue, 17 Jul 2001 06:53:41 -0400 (EDT)
Message-Id: <200107171053.GAA10607@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: idn@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [idn] I-D ACTION:draft-ietf-idn-uname-01.txt
Date: Tue, 17 Jul 2001 06:53:41 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internationalized Domain Name Working Group of the IETF.

	Title		: Internationalized Domain Names and Unique 
                          Identifiers/Names
	Author(s)	: L. Tseng et al.
	Filename	: draft-ietf-idn-uname-01.txt
	Pages		: 
	Date		: 16-Jul-01
	
One of the biggest technical challenge of Internationalized Domain 
Names (IDN) is how to determine if the two given domain names matches. 
The current approach to this problem is via a process known as 
[NAMEPREP].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idn-uname-01.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-idn-uname-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-idn-uname-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010716153854.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idn-uname-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idn-uname-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010716153854.I-D@ietf.org>

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Tue Jul 17 09:11:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA01300
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 09:11:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MTyv-000F5W-00
	for idn-data@psg.com; Tue, 17 Jul 2001 05:29:41 -0700
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MTyu-000F5O-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 05:29:40 -0700
Received: from cnnic.net.cn ([159.226.7.66]) by
          whale.cnnic.net.cn (Netscape Messaging Server 4.15) with ESMTP
          id GGMASF00.104 for <idn@ops.ietf.org>; Tue, 17 Jul 2001 20:31:27 +0800 
Message-ID: <3B542F88.CA600BE3@cnnic.net.cn>
Date: Tue, 17 Jul 2001 20:28:56 +0800
From: "Sun Guonian" <sun@cnnic.net.cn>
Reply-To: sun@cnnic.net.cn
Organization: CNNIC
X-Mailer: Mozilla 4.77 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: idn@ops.ietf.org
Subject: [idn] draft-ietf-idn-ace-eval-cn-00
Content-Type: multipart/mixed;
 boundary="------------7948C4ED27739F7CF3B36BC4"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.
--------------7948C4ED27739F7CF3B36BC4
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

hello, all,

Last Thursday I had sent this document to internet-drafts@ietf.org
and co-chairs of IDN WG, but I can't see it in IDN group mail list
till now.
I think it is important for the people on the mail list to share it, so
I
send it to the list.

regards,
Sun Guonian

--
*****************************************************
* China Internet Network Information Center (CNNIC) *
*   Sun Guonian                    No.4, S.4 Street *
*                                  Zhong Guan Cun   *
* Phone: 86-10-62553604            Haidian District *
* Email: sun@cnnic.net.cn          Beijing          *
* http://drop.cnnic.net.cn/~sun/   P.O.Box: 100080  *
*****************************************************
* =D6=D0=B9=FA=BB=A5=C1=AA=CD=F8=C2=E7=D0=C5=CF=A2=D6=D0=D0=C4    =CB=EF=B9=
=FA=C4=EE                    *
*****************************************************


--------------7948C4ED27739F7CF3B36BC4
Content-Type: text/plain; charset=us-ascii;
 name="draft-ietf-idn-ace-eval-cn-00.txt"
Content-Disposition: inline;
 filename="draft-ietf-idn-ace-eval-cn-00.txt"
Content-Transfer-Encoding: 7bit

Internet Draft                                               Sun Guonian
draft-ietf-idn-ace-eval-cn-00.txt                                  CNNIC
Jul 10, 2001
Expires Jan 10, 2002

     Evaluation of various ACEs with existing Chinese Domain Names

Status of this memo

    This document is an Internet-Draft and is in full conformance with
    all provisions of Section 10 of RFC2026.

    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as
    Internet-Drafts.

    Internet-Drafts are draft documents valid for a maximum of six
    months and may be updated, replaced, or obsoleted by other documents
    at any time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."

    The list of current Internet-Drafts can be accessed at
    http://www.ietf.org/ietf/1id-abstracts.txt

    The list of Internet-Draft Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html.



Abstract

    The ACE (ASCII Compatible Encoding) Design Team in IDN Working Group
    is selecting an appropriate ACE proposal.  To push forward the work of
    ACE Design Team, this document illustrates the results of various ACEs
    that being applied to Chinese Domain Names.

1. Test data and tools

    These test data were sampled from CNNIC's current registry database, with
    the total number of 100,000.

    Applied ACEs are RACE-03 [RACE], BRACE-00 [BRACE], LACE-01 [LACE],
    UTF-6-00 [UTF6], DUDE-02 [DUDE], AMC-ACE-M-00 [AMCACEM], AltDUDE-01
    [AltDUDE], AMC-ACE-O-00 [AMCACEO], AMC-ACE-R-01 [AMCACER],
    AMC-ACE-V-00 [AMCACEV], AMC-ACE-W-00 [AMCACEW], MACE-01 [MACE] and
    LDUDE-00[LDUDE].

2. Result of each ACE

    HANZI_len is the characters in the Chinese string before UCS2-ACE coding,
    max_len is the maximum length that a ACE-coded string can reach, min_len
    is the minimum length that a ACE-coded string can reach, aver_len is the
    average length of all ACE-coded strings converted from the Chinese string
    with the same HANZI_len-size.
 
  2.1 AMC-ACE-M

    HANZI_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    1            9        9        9.0000  
    2            13       10       12.7385 
    3            17       11       15.8155 
    4            20       12       18.8141 
    5            23       13       21.7565 
    6            26       14       24.6305 
    7            29       16       27.5662 
    8            33       16       30.4084 
    9            35       30       33.3293 
    10           39       27       36.1929 
    11           41       36       39.1082 
    12           45       34       42.0063 
    13           48       42       44.8869 
    14           50       43       47.8597 
    15           53       48       50.7955 
    16           57       51       53.8091 
    17           59       53       56.5031 
    18           62       57       59.7467 
    19           65       61       62.5106 
    20           68       63       65.6471 

  2.2 AMC-ACE-O

    HANZI_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    1            9        9        9.0000  
    2            13       10       12.7401 
    3            17       11       16.2954 
    4            21       12       19.8272 
    5            25       13       23.3622 
    6            29       14       26.6862 
    7            32       16       30.3160 
    8            36       16       33.3543 
    9            40       30       36.9435 
    10           44       27       40.1309 
    11           48       36       43.5358 
    12           51       34       46.9934 
    13           55       41       50.1921 
    14           59       31       53.6718 
    15           62       48       56.4908 
    16           66       51       60.5728 
    17           68       53       63.0881 
    18           73       57       66.3467 
    19           76       61       70.4894 
    20           79       67       73.4706 

  2.3 AMC-ACE-R

    HANZI_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    1            9        9        9.0000  
    2            13       10       12.7401 
    3            17       11       16.4921 
    4            21       12       20.3006 
    5            25       13       24.0866 
    6            29       14       27.7128 
    7            33       16       31.5339 
    8            37       16       34.8798 
    9            41       31       38.7328 
    10           45       27       42.2981 
    11           49       40       45.9261 
    12           53       34       49.7214 
    13           57       45       53.1325 
    14           61       43       56.8372 
    15           65       52       60.1350 
    16           69       56       64.5534 
    17           73       53       67.0566 
    18           75       63       71.5600
    19           80       67       74.8936
    20           84       72       79.2647 

  2.4 AMC_ACE_V

    HANZI_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    1            8        8        8.0000  
    2            12       10       10.9848 
    3            16       11       13.9613 
    4            20       12       16.9441 
    5            23       13       19.9398 
    6            25       14       22.9069 
    7            28       16       25.9121 
    8            32       16       28.8512 
    9            35       29       31.8418 
    10           37       27       34.8368 
    11           41       35       37.7769 
    12           44       35       40.8079 
    13           47       40       43.7668 
    14           49       32       46.7032 
    15           52       45       49.6626 
    16           56       50       52.8026 
    17           58       53       55.6604 
    18           65       57       58.9733 
    19           64       60       61.8085 
    20           67       63       64.8235 

  2.5 AMC_ACE_W

    HANZI_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    1            8        8        8.0000  
    2            12       10       10.9848 
    3            16       11       13.9790 
    4            19       12       16.9746 
    5            24       13       19.9955 
    6            27       14       22.9755 
    7            29       16       26.0036 
    8            34       16       28.9908 
    9            37       29       32.0108 
    10           41       27       35.0201 
    11           46       36       38.0537 
    12           49       28       41.0596 
    13           52       42       44.1294 
    14           56       44       47.1385 
    15           56       47       50.1472 
    16           62       51       53.3204 
    17           66       54       56.3082 
    18           72       58       60.1333 
    19           69       61       62.7234 
    20           71       64       65.2059 

  2.6 AltDUDE

    HANZI_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    1            8        8        8.0000  
    2            12       9        11.7401 
    3            16       10       15.4679 
    4            20       11       19.2468 
    5            24       12       23.0600 
    6            28       13       26.7517 
    7            32       15       30.6092 
    8            36       15       34.1284 
    9            40       30       37.9871 
    10           44       29       41.5955 
    11           48       38       45.2093 
    12           52       26       49.0893 
    13           56       45       52.7266 
    14           60       49       56.3480 
    15           64       53       59.7935 
    16           68       57       63.8964 
    17           72       61       67.2956 
    18           76       65       71.6400 
    19           79       71       75.3404 
    20           83       72       78.3529 

  2.7 BRACE

    HANZI_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    1            8        8        8.0000  
    2            11       9        10.9402 
    3            14       11       13.9295 
    4            18       12       17.8337 
    5            21       14       20.9788 
    6            24       15       23.9537 
    7            27       16       26.9647 
    8            30       18       29.9676 
    9            34       31       33.8942 
    10           37       29       36.9766 
    11           40       36       39.9731 
    12           43       36       42.9665 
    13           46       43       45.9814 
    14           50       43       49.9406 
    15           53       51       52.9877 
    16           56       54       55.9806 
    17           59       52       58.8868 
    18           62       59       61.9200 
    19           66       65       65.9787 
    20           69       69       69.0000 

  2.8 DUDE

    HANZI_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    1            8        8        8.0000  
    2            12       9        11.7401 
    3            16       10       15.4679 
    4            20       11       19.2468 
    5            24       12       23.0600 
    6            28       13       26.7517 
    7            32       15       30.6092 
    8            36       15       34.1284 
    9            40       30       37.9871 
    10           44       29       41.5955 
    11           48       38       45.2093 
    12           52       26       49.0893 
    13           56       45       52.7266 
    14           60       49       56.3480 
    15           64       53       59.7935 
    16           68       57       63.8964 
    17           72       61       67.2956 
    18           76       65       71.6400 
    19           79       71       75.3404 
    20           83       72       78.3529 

  2.9 LACE

    HANZI_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    1            9        9        9.0000  
    2            12       11       11.9642 
    3            16       12       15.9868 
    4            19       14       18.9913 
    5            22       16       21.9985 
    6            25       17       24.9972 
    7            28       19       27.9995 
    8            32       20       31.9990 
    9            35       35       35.0000 
    10           38       36       37.9994 
    11           41       41       41.0000 
    12           44       33       43.9934 
    13           48       48       48.0000 
    14           51       51       51.0000 
    15           54       54       54.0000 
    16           57       57       57.0000 
    17           60       60       60.0000 
    18           64       64       64.0000 
    19           67       67       67.0000 
    20           70       70       70.0000 

  2.10 LDUDE

    HANZI_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    1            8        8        8.0000  
    2            12       9        11.3573 
    3            16       10       14.4717 
    4            20       11       17.5182 
    5            24       12       20.5703 
    6            28       13       23.5265 
    7            32       15       26.6787 
    8            36       15       29.6551 
    9            40       21       32.7320 
    10           44       23       35.9557 
    11           48       28       38.9694 
    12           51       26       42.1635 
    13           55       34       45.1844 
    14           60       37       48.4613 
    15           63       40       51.3865 
    16           66       43       54.9903 
    17           70       45       58.2767 
    18           75       50       61.8133 
    19           76       51       62.7234 
    20           78       57       67.9706 

  2.11 MACE

    HANZI_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    1            8        7        7.9850  
    2            12       9        10.9905 
    3            16       10       13.9855 
    4            19       11       16.9912 
    5            24       12       19.9935 
    6            26       14       22.9938 
    7            29       15       26.0009 
    8            34       15       29.0167 
    9            37       29       32.0114 
    10           41       30       35.0183 
    11           46       37       38.0455 
    12           49       29       41.0432 
    13           52       42       44.0883 
    14           56       45       47.1493 
    15           56       48       50.1718 
    16           62       53       53.3042 
    17           66       55       56.3837 
    18           70       59       60.1467 
    19           69       62       62.7234 
    20           71       64       65.2941 

  2.12 RACE

    HANZI_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    1            9        8        8.0014  
    2            12       9        11.8931 
    3            16       11       15.9835 
    4            19       12       18.9981 
    5            22       14       21.9994 
    6            25       16       24.9987 
    7            28       17       27.9993 
    8            32       19       31.9989 
    9            35       35       35.0000 
    10           38       38       38.0000 
    11           41       41       41.0000 
    12           44       44       44.0000 
    13           48       48       48.0000 
    14           51       51       51.0000 
    15           54       54       54.0000 
    16           57       57       57.0000 
    17           60       60       60.0000 
    18           64       64       64.0000 
    19           67       67       67.0000 
    20           70       70       70.0000 

  2.13 UTF-6

    HANZI_len    max_len  min_len  aver_len
    -----------  -------- -------- --------
    1            8        8        8.0000
    2            12       9        11.9582
    3            16       10       15.9889
    4            20       11       19.9985
    5            24       17       23.9995
    6            28       13       27.9984
    7            32       21       31.9993
    8            36       23       35.9989
    9            40       40       40.0000
    10           44       44       44.0000
    11           48       48       48.0000
    12           52       52       52.0000
    13           56       56       56.0000
    14           60       60       60.0000
    15           64       64       64.0000
    16           68       68       68.0000
    17           72       72       72.0000
    18           76       76       76.0000
    19           80       80       80.0000
    20           84       84       84.0000


3. Summary

    ACE_name   max_cstring
    AMC-ACE-M  18
    AMC-ACE-O  15
    AMC-ACE-R  14
    AMC_ACE_V  17
    AMC_ACE_W  16
    AltDUDE    14
    BRACE      18
    DUDE       14
    LACE       17
    LDUDE      15
    MACE       16
    RACE       17
    UTF-6      14

    The max_cstring is the maximum length of Chinese Domain Name when
    max_len is less than 64.

    For Chinese Domain Name, the max_len is most significant.

4. References

    [RFC1035]  "DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION",
               RFC1034, Nov 1987, P. Mockapetris
    [RACE]     "RACE: Row-based ASCII Compatible Encoding for IDN",
               draft-ietf-idn-race-03.txt, Nov 2000, P Hoffman
    [BRACE]    "BRACE: Bi-mode Row-based ASCII-Compatible Encoding for IDN
               version 0.1.2"
               draft-ietf-idn-brace-00.txti, Sep 2000, A Costello
    [LACE]     "LACE: Length-based ASCII Compatible Encoding for IDN"
               draft-ietf-idn-lace-01.txt, Jan 2001, M Davis, P Hoffman
    [UTF6]     "UTF-6 - Yet Another ASCII-Compatible Encoding for IDN"
               draft-ietf-idn-utf6-00, Nov 2000, M Welter, B Spolarich
    [DUDE]     "Differential Unicode Domain Encoding (DUDE)"
               draft-ietf-idn-dude-02.txt, Jun 2001, M Welter, B Spolarich,
	       A Costello
    [AMCACEM]  "AMC-ACE-M version 0.1.0"
               draft-ietf-idn-amc-ace-m-00.txt, Feb 2001, A Costello
    [AltDUDE]  "AltDUDE version 0.0.2"
               draft-ietf-idn-altdude-00.txt, Mar 2001, A Costello
    [AMCACEO]  "AMC-ACE-O version 0.0.3"
               draft-ietf-idn-amc-ace-o-00.txt, Mar 2001, A Costello
    [AMCACER]  "AMC-ACE-R version 0.2.1"
               draft-ietf-idn-amc-ace-r-01.txt, May 2001, A Costello
    [AMCACEV]  "AMC-ACE-V version 0.1.0"
               draft-ietf-idn-amc-ace-v-00.txt, May 2001, A Costello
    [AMCACEW]  "AMC-ACE-W version 0.1.0"
               draft-ietf-idn-amc-ace-w-00.txt, May 2001, A Costello
    [MACE]     "MACE: Modal ASCII Compatible Encoding for IDN"
               draft-ietf-idn-mace-00.txt, Jun 2001, M Ishisone, Y Yoneya
    [LDUDE]    "Improving ACE using code point reordering v0.9"
               draft-ietf-idn-lsb-ace-00.txt, Jun 2001, Soobok Lee
    [MDNKIT]   "Multilingual Domain Name tool Kit",
               http://www.nic.ad.jp/jp/research/idn/mdnkit/download/

5. Acknowledgements

    CNNIC Chinese Registry Service Department provided registered
    Chinese Domain Names.
    XiaoDong LEE, lee@cnnic.net.cn
    Wang Yanfeng, wyf@cnnic.net.cn
    Deng Xiang, deng@cnnic.net.cn
    
6. Author's Address

    Sun Guonian
    China Internet Network Information Center
    No.4, South 4th street, Zhongguancun,
    Haidian District, Beijing,
    China  100080
    sun@cnnic.net.cn

--------------7948C4ED27739F7CF3B36BC4--




From owner-idn@ops.ietf.org  Tue Jul 17 09:47:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA06915
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 09:47:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MUyI-000HLG-00
	for idn-data@psg.com; Tue, 17 Jul 2001 06:33:06 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MUyH-000HLA-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 06:33:05 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA16969;
        Tue, 17 Jul 2001 09:32:52 -0400 (EDT)
Message-Id: <200107171332.JAA16969@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Martin Duerst <duerst@w3.org>
cc: Patrik F=?ISO-2022-JP?B?GyRCZ00bKEI=?=tstr =?ISO-2022-JP?B?GyRCi04bKEI=?= <paf@cisco.com>,
        Russ Rolfe <rrolfe@windows.microsoft.com>, idn@ops.ietf.org
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check) 
In-reply-to: Your message of "Tue, 17 Jul 2001 16:48:04 +0900."
             <4.2.0.58.J.20010717154931.03f7b130@sh.w3.mag.keio.ac.jp> 
Date: Tue, 17 Jul 2001 09:32:52 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Just send UTF-8 with nameprep is definitely what's needed, 

I find that statement completely irresponsible.  It completely ignores 
the need for deployed applications to keep working through this transition.

Keith



From owner-idn@ops.ietf.org  Tue Jul 17 10:05:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA11049
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 10:05:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MV4G-000Ha7-00
	for idn-data@psg.com; Tue, 17 Jul 2001 06:39:16 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MV4F-000HZz-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 06:39:16 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA17020;
        Tue, 17 Jul 2001 09:39:11 -0400 (EDT)
Message-Id: <200107171339.JAA17020@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Martin Duerst <duerst@w3.org>
cc: Patrik F=?ISO-2022-JP?B?GyRCZ00bKEI=?=tstr =?ISO-2022-JP?B?GyRCi04bKEI=?= <paf@cisco.com>,
        idn@ops.ietf.org
Subject: Re: [idn] IDN security and ACE leakage 
In-reply-to: Your message of "Tue, 17 Jul 2001 17:52:16 +0900."
             <4.2.0.58.J.20010717171624.036459a0@sh.w3.mag.keio.ac.jp> 
Date: Tue, 17 Jul 2001 09:39:11 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> MIME was a pain for a long time. Where it still is a pain (including
> my mailer), that may be blamed on the implementation. But the years it took
> to reasonably deploy MIME cannot be blamed on any implementation, they have
> to be blamed on MIME itself.

perhaps, but it's irrelevant to your argument.

the time required for MIME deployment has nothing to do with charset issues, 
and everything to do with the large installed base of RFC 822 text-only mailers, 
and the design decision for MIME to provide for carriage of a tree-shaped 
structure of arbitrary, labelled body parts.

even if you think that supporting multiple charsets delayed MIME further,
there was no universal charset available at the time that MIME was defined.
would you have delayed the work on MIME until 10646 was finalized
(several years later)?

Keith



From owner-idn@ops.ietf.org  Tue Jul 17 10:35:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA18116
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 10:35:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MVKt-000IA9-00
	for idn-data@psg.com; Tue, 17 Jul 2001 06:56:27 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MVKs-000I9c-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 06:56:26 -0700
Received: from CLASSIC.viagenie.qc.ca (modemcable245.48-201-24.que.mc.videotron.ca [24.201.48.245])
	by jazz.viagenie.qc.ca (Viagenie/8.11.0) with ESMTP id f6HEEt185458;
	Tue, 17 Jul 2001 10:14:55 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010717090741.02cd1e38@mail.viagenie.qc.ca>
X-Sender: blanchet@mail.viagenie.qc.ca
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 17 Jul 2001 09:10:09 -0400
To: "Russ Rolfe" <rrolfe@windows.microsoft.com>,
        "Martin Duerst" <duerst@w3.org>,
        "idn working group" <idn@ops.ietf.org>
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: RE: [idn] pool deadline imminent
In-Reply-To: <8CC03F47967BF14D9710887723FADDB6964D4E@win-msg-02.wingroup
 .windeploy.ntdev.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Three extracts (I should use multipart mime...) and my comment below:

===============
>Martin Duerst wrote:
>
> > At 17:46 01/07/12 +0000, Adam M. Costello wrote:
> >> I didn't really understand until this morning that any proposal that
> >> doesn't have seven supporters by tomorrow will be out of the running.
>
> > Just for the record: If anybody is working on a UTF-8 based
> > (or even ACE/UTF-8 mixed) solution, they herewith all have
> > my support (I won't tell them one-by-one).

====================
At/À 11:06 2001-07-16 -0700, Russ Rolfe you wrote/vous écriviez:
>I know this is late, but was unable to reply until now.  UTF-8 based
>solutions also have my support.

==============================
Date: Mon, 16 Jul 2001 14:27:52 -0400 (EDT)
From: *click* <lucid@epa.secret.org>
To: idn working group <idn@ops.ietf.org>
cc: Russ Rolfe <rrolfe@windows.microsoft.com>, Martin Duerst <duerst@w3.org>
Subject: RE: [idn] pool deadline imminent

Better late then never...
I am in support of any UTF-8 based solution and am willing to help
contribute if anyone is working on such a draft.

-Bill
==============================
==============================

To me, this is ambiguous support.  I could write a personal internet-draft 
that will use electricity to distribute labels over an optical vpn using 
BGP extensions and a diffie-hellman exchange that uses UTF-8 for idn.  Are 
you going to support and implement it?

To Martin, Russ, Bill (and others), please indicate a specific draft (or 
drafts) you are supporting. And not to the mailing list but to the authors 
(this will save wg mailing list bandwidth).

Marc.


>Regards, Russ Rolfe
>Microsoft -- rrolfe@microsoft.com
>
>-----Original Message-----
>From: Martin Duerst [mailto:duerst@w3.org]
>Sent: Thursday, July 12, 2001 7:49 PM
>To: idn working group
>Subject: Re: [idn] pool deadline imminent
>
>
>At 17:46 01/07/12 +0000, Adam M. Costello wrote:
> >I didn't really understand until this morning that any proposal that
> >doesn't have seven supporters by tomorrow will be out of the running.
>
>Just for the record: If anybody is working on a UTF-8 based
>(or even ACE/UTF-8 mixed) solution, they herewith all have
>my support (I won't tell them one-by-one).
>
>Regards,   Martin.





From owner-idn@ops.ietf.org  Tue Jul 17 10:41:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA19540
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 10:41:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MVmO-000JB9-00
	for idn-data@psg.com; Tue, 17 Jul 2001 07:24:52 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MVmN-000JB3-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 07:24:51 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f6HEMZd01107;
	Tue, 17 Jul 2001 10:22:35 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107171422.f6HEMZd01107@nic-naa.net>
To: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
cc: "Russ Rolfe" <rrolfe@windows.microsoft.com>,
        "Martin Duerst" <duerst@w3.org>,
        "idn working group" <idn@ops.ietf.org>, brunner@nic-naa.net
Subject: Re: [idn] pool deadline imminent 
In-Reply-To: Your message of "Tue, 17 Jul 2001 09:10:09 EDT."
             <5.1.0.14.1.20010717090741.02cd1e38@mail.viagenie.qc.ca> 
Date: Tue, 17 Jul 2001 10:22:35 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Marc,

Deng (.cn nic) and I (.biz nic) are collaborating on a utf8 draft.

Anyone interested simply drop me a note.

Eric



From owner-idn@ops.ietf.org  Tue Jul 17 10:55:15 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA22783
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 10:55:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MW9T-000Juq-00
	for idn-data@psg.com; Tue, 17 Jul 2001 07:48:43 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MW9S-000Juk-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 07:48:42 -0700
Received: from enoshima (g055087.ppp.asahi-net.or.jp [211.132.55.87])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id XAA10225;
	Tue, 17 Jul 2001 23:48:19 +0900 (JST)
Message-Id: <4.2.0.58.J.20010717234452.0362f6c0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 17 Jul 2001 23:47:22 +0900
To: Keith Moore <moore@cs.utk.edu>
From: Martin Duerst <duerst@w3.org>
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality
  Check) 
Cc: Patrik F=?ISO-2022-JP?B?GyRCZ00bKEI=?=tstr 
 =?ISO-2022-JP?B?GyRCi04bKEI=?= <paf@cisco.com>,
        Russ Rolfe <rrolfe@windows.microsoft.com>, idn@ops.ietf.org
In-Reply-To: <200107171332.JAA16969@astro.cs.utk.edu>
References: <Your message of "Tue, 17 Jul 2001 16:48:04 +0900." <4.2.0.58.J.20010717154931.03f7b130@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 09:32 01/07/17 -0400, Keith Moore wrote:
> > Just send UTF-8 with nameprep is definitely what's needed,
>
>I find that statement completely irresponsible.  It completely ignores
>the need for deployed applications to keep working through this transition.

Hello Keith,

If you can explain to me why ACE should be better than NAT,
and why deployed applications should stop working with the
domain names they always have worked with until now,
I'll accept your comments.

Regards,   Martin.



From owner-idn@ops.ietf.org  Tue Jul 17 10:56:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA23034
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 10:56:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MW6J-000Jno-00
	for idn-data@psg.com; Tue, 17 Jul 2001 07:45:27 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MW6I-000JnO-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 07:45:26 -0700
Received: from enoshima (g055087.ppp.asahi-net.or.jp [211.132.55.87])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id XAA10138;
	Tue, 17 Jul 2001 23:40:34 +0900 (JST)
Message-Id: <4.2.0.58.J.20010717233736.035b9c50@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 17 Jul 2001 23:40:04 +0900
To: Keith Moore <moore@cs.utk.edu>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] IDN security and ACE leakage 
Cc: Patrik F=?ISO-2022-JP?B?GyRCZ00bKEI=?=tstr 
 =?ISO-2022-JP?B?GyRCi04bKEI=?= <paf@cisco.com>,
        idn@ops.ietf.org
In-Reply-To: <200107171339.JAA17020@astro.cs.utk.edu>
References: <Your message of "Tue, 17 Jul 2001 17:52:16 +0900." <4.2.0.58.J.20010717171624.036459a0@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 09:39 01/07/17 -0400, Keith Moore wrote:

>the time required for MIME deployment has nothing to do with charset issues,
>and everything to do with the large installed base of RFC 822 text-only 
>mailers,
>and the design decision for MIME to provide for carriage of a tree-shaped
>structure of arbitrary, labelled body parts.
>
>even if you think that supporting multiple charsets delayed MIME further,

Well, probably there was some synergy effect, so in part it may have
made things faster. But there are still some mailers that do quite
a good job on multiparts but a bad job on charset issues, so in part
indeed things have been slower.


>there was no universal charset available at the time that MIME was defined.
>would you have delayed the work on MIME until 10646 was finalized
>(several years later)?

I acknowledged that. But now the situation is different.

Regards,   Martin.



From owner-idn@ops.ietf.org  Tue Jul 17 11:04:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA25052
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 11:04:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MW6I-000Jnh-00
	for idn-data@psg.com; Tue, 17 Jul 2001 07:45:26 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MW6G-000Jn4-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 07:45:25 -0700
Received: from enoshima (g055087.ppp.asahi-net.or.jp [211.132.55.87])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id XAA10199;
	Tue, 17 Jul 2001 23:44:56 +0900 (JST)
Message-Id: <4.2.0.58.J.20010717234201.03647210@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 17 Jul 2001 23:44:30 +0900
To: sun@cnnic.net.cn, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] draft-ietf-idn-ace-eval-cn-00
In-Reply-To: <3B542F88.CA600BE3@cnnic.net.cn>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 20:28 01/07/17 +0800, Sun Guonian wrote:
>      Evaluation of various ACEs with existing Chinese Domain Names

>3. Summary
>
>     ACE_name   max_cstring
>     AMC-ACE-M  18
>     AMC-ACE-O  15
>     AMC-ACE-R  14
>     AMC_ACE_V  17
>     AMC_ACE_W  16
>     AltDUDE    14
>     BRACE      18
>     DUDE       14
>     LACE       17
>     LDUDE      15
>     MACE       16
>     RACE       17
>     UTF-6      14

Not an ACE, but probably worth mentioning anyway:

UTF-8       21

With the additional advantage that it's much easier to explain
to anybody why some names are too long and others are short enough.


Regards,   Martin.



From owner-idn@ops.ietf.org  Tue Jul 17 11:20:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA28665
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 11:20:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MWVN-000Kj9-00
	for idn-data@psg.com; Tue, 17 Jul 2001 08:11:21 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MWVM-000Kj1-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 08:11:20 -0700
Received: from enoshima (g055087.ppp.asahi-net.or.jp [211.132.55.87])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id AAA10384;
	Wed, 18 Jul 2001 00:11:24 +0900 (JST)
Message-Id: <4.2.0.58.J.20010717184708.035bae20@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 18 Jul 2001 00:10:52 +0900
To: Patrik F=?ISO-2022-JP?B?GyRCZ00bKEI=?=tstr
 =?ISO-2022-JP?B?GyRCi04bKEI=?= <paf@cisco.com>,
        Russ Rolfe <rrolfe@windows.microsoft.com>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality
  Check)
In-Reply-To: <152039.995367999@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello Patrick

At 11:06 01/07/17 +0200, Patrik F$BgM(Btstr$B‹N(B wrote:
>--On 01-07-17 16.48 +0900 Martin Duerst <duerst@w3.org> wrote:
>
> > It is very important to understand that in most contexts, the chance
> > that a label is changed (except for lowercasing, which was part of
> > the UTF-8 proposal from the start) by nameprep when somebody takes a
> > proper domain name from paper and inputs it, is *very* small.
>
>We will have problems when domainnames are registered.
>
>Say that someone send in request for registering domain A which is
>correctly nameprepped. If someone else is sending in domain B for
>registration which would be nameprepped into A, it is extremely important
>that B is not registered, but instead this second person get to know that
>B, converted to A, is already registered.

I agree that it's extremely important for registration. But
registration happens once, and then it's over. I was answering
to your claim that applications that now just use UTF-8 need to
be updated to use nameprep. In the limit, compiling a zone file
into a domain name server is the only place we really need
nameprep. If that is done 100% consistently, everything else
can be left to quality of implementation (I don't think we
should leave it at that, but I'm saying it could, without
any major consequences).


>It is enough with only _one_ mistake (regardless of how small the risk is
>that this happens) and we will have some definition of chaos.

Well, yes, and the registrar who registered it will get some
*very* serious blame.


>I also ask myself this the last couple of days:
>
>- This wg is about what is used in the DNS protocol.

Yes, but it should also look at the overall consequences,
for backwards compatibility but even more for how we want
the future of the Internet and Internet internationalization
to work.

>- Many people want UTF-8 to be used in DNS.

For obvious reasons. It's the most straightforward solution,
given that getting people who use ASCII to abandon it and
given that the Internet is an 8-bit network.


>- Application protocols do not use UTF-8 but ASCII (most of them).

Well, is some way. FTP already uses utf-8 for file names.
NNTP is working on it, just to give a few examples.
And many others are perfectly capable
of doing more than ASCII.

The Internet is 8-bit end-to-end. The application protocols should
be no exception.


>- Someone (in Applications Area) have to write documents, one per protocol
>   on how to pass Unicode characters in the protocols, how to handle
>   downgrading to something else if needed (like 8BITMIME in SMTP) and
>   for each protocol what the downgrade is to.

If internationalization hasn't been done, it indeed should be done.
Are you suggesting that ACE will make it unnecessary to internationalize
protocols? I very much hope not.

For most protocols, in particular point-to-point protocols,
the downgrade will be failure if implemented tightly (i.e. checking
for ASCII) and success if implemented 8-bit transparent.
FTP internationalization is a typical case. People didn't find
it necessary to negotiate or downgrade (except for some provisions
for legacy encodings).

SMTP indeed needs some serious work, because it's application is
so important, because way less than could have been done has been
done until now, and because of the pushing and semi-point-to-point
characteristics of email. For most other protocols, the situation
is much simpler.


>Conclusion:
>- As many application protocols (like SMTP) can not use UTF-8 for a while
>   should not DNS use some more efficient encoding than UTF-8 in the
>   packets?
>
>I claim that the actual encoding which is to be used in the DNS protocol is
>something this wg can not come up with, but instead the DNSEXT wg in the
>DNS is the correct group which is to come up with an encoding which is as
>efficient as possible, given DNSSEC and other new things which they are
>working with.

Are you saying we couldn't decide to use UTF-8, even if everybody
and her grandmother wanted that? Or are you saying that if DNS
needs some generic compression, this WG shouldn't do it?


>I further guess that when people in this wg talk about "we want UTF-8" they
>really talk about what they want to use in the Application Layer protocols,
>but defining that is really out of scope for this wg.

Yes indeed. But choosing a solution that fits with the rest
should very much be within the scope of the wg, I hope.


>So be careful what you ask for!
>
>Either this wg come up with something which is backward compatible with
>other existing standards, or it comes up with a "framework" and give work
>items for other wg's and leave it to them for standarization.

So are you saying that this WG is allowed to do crude hacks
to smuggle characters around, but not to do serious work in the open?


Regards,   Martin.



From owner-idn@ops.ietf.org  Tue Jul 17 11:34:35 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA01470
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 11:34:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MWbh-000L0P-00
	for idn-data@psg.com; Tue, 17 Jul 2001 08:17:53 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MWbg-000L0H-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 08:17:53 -0700
Received: from enoshima (g055087.ppp.asahi-net.or.jp [211.132.55.87])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id AAA10410
	for <idn@ops.ietf.org>; Wed, 18 Jul 2001 00:18:08 +0900 (JST)
Message-Id: <4.2.0.58.J.20010718001411.03563e00@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 18 Jul 2001 00:17:10 +0900
To: idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: [idn] Mail reliability
In-Reply-To: <200107171511.f6HFBRR28564@sj-msg-av-1.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

<sneak>Just a side remark. Given things like below, which I see daily,
I don't think that using UTF-8 in mail headers will cause much more
problems.</sneak>

Regards,   Martin.


At 08:11 01/07/17 -0700, Mail Delivery Subsystem wrote:
>The original message was received at Tue, 17 Jul 2001 08:11:23 -0700 (PDT)
>from localhost [127.0.0.1]
>
>    ----- The following addresses had permanent fatal errors -----
><paf@sj-av.cisco.com>
>     (reason: 550 5.1.1 <paf@cisco.com>... User unknown)
>
>    ----- Transcript of session follows -----
>... while talking to sj-msg-core-4.cisco.com.:
> >>> RCPT To:<paf@cisco.com>
><<< 550 5.1.1 <paf@cisco.com>... User unknown
>550 5.1.1 <paf@sj-av.cisco.com>... User unknown
>Reporting-MTA: dns; sj-msg-av-1.cisco.com
>Received-From-MTA: DNS; localhost
>Arrival-Date: Tue, 17 Jul 2001 08:11:23 -0700 (PDT)
>
>Final-Recipient: RFC822; paf@cisco.com
>Action: failed
>Status: 5.1.1
>Remote-MTA: DNS; sj-msg-core-4.cisco.com
>Diagnostic-Code: SMTP; 550 5.1.1 <paf@cisco.com>... User unknown
>Last-Attempt-Date: Tue, 17 Jul 2001 08:11:27 -0700 (PDT)
>Return-Path: <duerst@w3.org>
>Received: from proxy3.cisco.com (localhost [127.0.0.1])
>         by sj-msg-av-1.cisco.com (8.10.1/8.10.1) with ESMTP id f6HFBNR28562
>         for <paf@sj-av.cisco.com>; Tue, 17 Jul 2001 08:11:23 -0700 (PDT)
>Received: from sh.w3.mag.keio.ac.jp (sh.w3.mag.keio.ac.jp [133.27.194.41])
>         by proxy3.cisco.com (8.11.2/8.11.2) with ESMTP id f6HFBn402614
>         for <paf@cisco.com>; Tue, 17 Jul 2001 08:11:50 -0700 (PDT)
>Received: from enoshima (g055087.ppp.asahi-net.or.jp [211.132.55.87])
>         by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id AAA10384;
>         Wed, 18 Jul 2001 00:11:24 +0900 (JST)
>Message-Id: <4.2.0.58.J.20010717184708.035bae20@sh.w3.mag.keio.ac.jp>
>X-Sender: duerst@sh.w3.mag.keio.ac.jp
>X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J
>Date: Wed, 18 Jul 2001 00:10:52 +0900
>To: Patrik F$BgM(Btstr$B‹N(B <paf@cisco.com>,Russ Rolfe 
><rrolfe@windows.microsoft.com>, idn@ops.ietf.org
>From: Martin Duerst <duerst@w3.org>
>Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] RealityCheck)
>In-Reply-To: <152039.995367999@localhost>
>Mime-Version: 1.0
>Content-Type: text/plain; charset="ISO-2022-JP"; format=flowed
>Content-Transfer-Encoding: 7bit
>
>Hello Patrick
>
>At 11:06 01/07/17 +0200, Patrik F$BgM(Btstr$B‹N(B wrote:
>>--On 01-07-17 16.48 +0900 Martin Duerst <duerst@w3.org> wrote:
>>
>> > It is very important to understand that in most contexts, the chance
>> > that a label is changed (except for lowercasing, which was part of
>> > the UTF-8 proposal from the start) by nameprep when somebody takes a
>> > proper domain name from paper and inputs it, is *very* small.




From owner-idn@ops.ietf.org  Tue Jul 17 12:01:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA08344
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 12:01:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MWrI-000LfG-00
	for idn-data@psg.com; Tue, 17 Jul 2001 08:34:00 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MWrH-000Lf4-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 08:33:59 -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 f6HFWAP14278 for <idn@ops.ietf.org>; Tue, 17 Jul 2001 17:32:11 +0200 (MEST)
Message-Id: <200107171532.f6HFWAP14278@malmo.trab.se>
Date: Tue, 17 Jul 2001 17:35:11 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: [idn] If I used IDNA or UTF-8 at my site
To: idn@ops.ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: j2NY/f/FciC18Ya2+HkwYg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk


Some more thoughts about the ACE/nameprep versus UTF-8 debate.
I have lately tried to think less on backward compatibility and instead
on the effects on using one or the other in the real world.
One can think of three possibilities: ACE+nameprep, UTF-8 and both.
There are existing areas that are somewhat alike that can be
compared with:
- MIME: In MIME non-ASCII can be encoded using quoted-printable and BASE64.
        If ASCII is enough, why even allow 8-bit transfer of documents?
        In e-mail today you can send ISO 8859-1 without any ASCII downcoding
        by having 8-bit MIME body parts.
        
- URLs: In URLs you encode non-ASCII using a %-escape mechanism.
        But a people are sending URLs in binary format today and there
        are drafts defining how non-ASCII should be handled without %-encoding.
        Why is this? If ACE is enough for the DNS protocol, %-encoding
        should be enough for protocols sending URLs.
        
The above two examples shows that despite it being enough to always use the
ASCII character set, prople do not stop there. Instead they want to send
the data without having to encode it.

What is the effect on the IDN possibilities?
Here I have looked at how my system is handling DNS and how I expect many
do handle DNS.
In my system we have a few DNS servers who all clients talk to. These DNS
servers then do the talking to other DNS servers around the world.
Simplified it works like this:
client <-> local DNS server <-> the rest of the world

On my system we use ISO 8859-1 as the local character set.
Now what would happen if I used IDNA (ACE with nameprep in client).
- I do now want to change my system vendors resolver code so
  all old clients would still use if and the old API.
  They would all see ACE.
- As I do not want my clients to worry about ACE a new resolver
  library is needed. This resolver would do the translation between
  ISO 8859-1 (my local character set) and ACE.
  A client would get a host name in ISO 8859-1 from the resolver except
  in the case where it cannot be represented as ISO 8859-1, it would then
  return ACE.
  As a general resolver for this the library would probably work
  like: ACE -> UCS -> ISO 8859-1 and in reverse.
- The users would copy host names between applications and files.
  This will result in ISO 8859-1 encoded host names ending up in
  applications only supporting the old DNS API. This resulting in them
  sending ISO 8859-1 hostnames over the DNS protocol to my local
  DNS server.
  Also, on printed paper and in files, host names will be in ISO 8859-1.
  Users will enter host names from printed matter using ISO 8859-1, once
  again resulting in ISO 8859-1 ending up over the DNS protocol.
- Due to the above problem I need to fix my local DNS server to
  catch the ISO 8859-1 encoded host names and convert them to ACE.
  So my local DNS server need to be changed.
- And as people will enter e-mail adresses they get on printed matter
  there will be ISO 8859-1 host names going into e-mail.
  So I will have to fix my e-mail MTA (sendmail).
- I will fail to have non-ASCII e-mail addresses in SOA records
  as IDNA uses nameprep+ACE to encode the labels and that forbids
  characters I need in the user name and also mangles case.
  (or do IDNA want to handle the SOA lable for e-mail address
   differently from all others?).

If I instead used only UTF-8, what happes?
- The local DNS server need to be upgraded to handle UTF-8.
- I do now want to change my system vendors resolver code so
  all old clients would still use if and the old API.
  They would not get any host name for IP -> name lookups when
  the host names is non-ASCII. To avoid breaking e-mail, which
  is the most important, I will need to use a ASCII only name
  on mail servers.
  Some other old clients may have to be disabled or worked around.
  Probably will all important things work.
- As I do not want my clients to worry about UTF-8 a new resolver
  library is needed. This resolver would do the translation between
  ISO 8859-1 and UTF-8.
  A client would get a host name in ISO 8859-1 from the resolver except
  in the case where it cannot be represented as ISO 8859-1, it would
  the have to be represented in some way for the user. Leaving it
  as UTF-8 will often be ok.
- The users would copy host names between applications and files.
  This will result in ISO 8859-1 encoded host names ending up in
  applications only supporting the old DNS API. This resulting in them
  sending ISO 8859-1 hostnames over the DNS protocol to my local
  DNS server.
  Also, on printed paper and in files, host names will be in ISO 8859-1.
  Users will enter host names from printed matter using ISO 8859-1, once
  again resulting in ISO 8859-1 ending up over the DNS protocol.
- Due to the above problem I need to fix my local DNS server to
  catch the ISO 8859-1 encoded host names and convert them to ACE.
  So my local DNS server need to handle ISO 8859-1 also.
- And as people will enter e-mail adresses they get on printed matter
  there will be ISO 8859-1 host names going into e-mail.
  So I will have to fix my e-mail MTA (sendmail).

If I instead use UTF-8 with nameprep+ACE for backward compatibility I get:
- The local DNS server need to be upgraded to handle UTF-8 and ACE.
  The server will send UTF-8 to new clients and ACE to old.
- I do now want to change my system vendors resolver code so
  all old clients would still use if and the old API.
  The will all get ACE in answers.
- As I do not want my clients to worry about UTF-8 a new resolver
  library is needed. This resolver would do the translation between
  ISO 8859-1 and UTF-8.
  A client would get a host name in ISO 8859-1 from the resolver except
  in the case where it cannot be represented as ISO 8859-1, it would
  the have to be represented in some way for the user. Encoding it using
  ACE is fine, it will then work if pasted into an old client.
- The users would copy host names between applications and files.
  This will result in ISO 8859-1 encoded host names ending up in
  applications only supporting the old DNS API. This resulting in them
  sending ISO 8859-1 hostnames over the DNS protocol to my local
  DNS server.
  Also, on printed paper and in files, host names will be in ISO 8859-1.
  Users will enter host names from printed matter using ISO 8859-1, once
  again resulting in ISO 8859-1 ending up over the DNS protocol.
- Due to the above problem I need to fix my local DNS server to
  catch the ISO 8859-1 encoded host names and convert them to UTF-8.
  So my local DNS server need to handle ISO 8859-1 also.
- And as people will enter e-mail adresses they get on printed matter
  there will be ISO 8859-1 host names going into e-mail.
  So I will have to fix my e-mail MTA (sendmail).
  
In summary:
- All possibilities result in a new resolver library and in
  a modified DNS server.
- The IDNA resolver need to do ACE <-> UCS <-> ISO 8859-1 translations,
  the UTF-8 resolver need to do  UTF-8 <-> ISO 8859-1 translations,
  and the UTF-8+ACE resolver do UTF-8 <-> ISO 8859-1, and UTF-8 -> ACE
  translations.
  I.e. they will contain more or less the same code. The strict UTF-8 only
  is simplest.
  The IDNA resolver will need most CPU time as it always translats to/from
  ACE.
- All need a modified DNS server unless you want a lot of failed
  DNS lookups because of wrong character set being used in old
  clients.

So, it looks difficult to tell which is best.
UTF-8 (UCS) being on of major directions for internationalisation today
and the fact that by using UTF-8 all labels and character data in DNS
can be internationlised, speaks in favor of a UTF-8 solution.
I have still not seen a good enough analys if ACE for backward compatibility
gives less problems than a pure UTF-8 solution does.
As indicated above there are problems with a pure UTF-8 solution, but
I cannot say if they can be solved simply enough to avoid ACE. Not allowing
ACE will result in much quicker fixing of old protocols and
applications. It took a long time before enough e-mail software
could handle MIME so that I could use non-ASCII in e-mail.
I can live with not having a non-ASCII e-mail address until enough
e-mail software is fixed for non-ASCII.

May be it all boils down to: 
do we once again go for the "encode all into ASCII, and the later extend
to full 8-bit" or instead go directely to "8-bit"?


    Dan




From owner-idn@ops.ietf.org  Tue Jul 17 12:08:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA09858
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 12:08:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MX48-000MA2-00
	for idn-data@psg.com; Tue, 17 Jul 2001 08:47:16 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MX46-000M9v-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 08:47:14 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id LAA17497;
        Tue, 17 Jul 2001 11:47:06 -0400 (EDT)
Message-Id: <200107171547.LAA17497@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Martin Duerst <duerst@w3.org>
cc: Keith Moore <moore@cs.utk.edu>,
        Patrik F=?ISO-2022-JP?B?GyRCZ00bKEI=?=tstr =?ISO-2022-JP?B?GyRCi04bKEI=?= <paf@cisco.com>,
        idn@ops.ietf.org
Subject: Re: [idn] IDN security and ACE leakage 
In-reply-to: Your message of "Tue, 17 Jul 2001 23:40:04 +0900."
             <4.2.0.58.J.20010717233736.035b9c50@sh.w3.mag.keio.ac.jp> 
Date: Tue, 17 Jul 2001 11:47:06 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> >the time required for MIME deployment has nothing to do with charset issues,
> >and everything to do with the large installed base of RFC 822 text-only
> >mailers,
> >and the design decision for MIME to provide for carriage of a tree-shaped
> >structure of arbitrary, labelled body parts.
> >
> >even if you think that supporting multiple charsets delayed MIME further,
> 
> Well, probably there was some synergy effect, so in part it may have
> made things faster. But there are still some mailers that do quite
> a good job on multiparts but a bad job on charset issues, so in part
> indeed things have been slower.

There are so many things required of a good MIME implementation that 
it's not surprising that an implementation does a better job with
some parts than others.  But again, this isn't the fault of MIME unless
you believe that MIME should have solved *only* the charset problem and 
not bothered with attachments and the structure thereof.
 
> >there was no universal charset available at the time that MIME was defined.
> >would you have delayed the work on MIME until 10646 was finalized
> >(several years later)?
> 
> I acknowledged that. But now the situation is different.

so is the problem.  However, the current IDN question and MIME do have one
significant thing in common - the need to avoid unnecessary disruption of
the installed base.

Keith



From owner-idn@ops.ietf.org  Tue Jul 17 12:10:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA10150
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 12:10:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MXG3-000MdR-00
	for idn-data@psg.com; Tue, 17 Jul 2001 08:59:35 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MXG2-000MdJ-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 08:59:34 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id LAA17564;
        Tue, 17 Jul 2001 11:59:24 -0400 (EDT)
Message-Id: <200107171559.LAA17564@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Martin Duerst <duerst@w3.org>
cc: Keith Moore <moore@cs.utk.edu>,
        Patrik F=?ISO-2022-JP?B?GyRCZ00bKEI=?=tstr =?ISO-2022-JP?B?GyRCi04bKEI=?= <paf@cisco.com>,
        Russ Rolfe <rrolfe@windows.microsoft.com>, idn@ops.ietf.org
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check) 
In-reply-to: Your message of "Tue, 17 Jul 2001 23:47:22 +0900."
             <4.2.0.58.J.20010717234452.0362f6c0@sh.w3.mag.keio.ac.jp> 
Date: Tue, 17 Jul 2001 11:59:24 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > > Just send UTF-8 with nameprep is definitely what's needed,
> >
> >I find that statement completely irresponsible.  It completely ignores
> >the need for deployed applications to keep working through this transition.
> 
> Hello Keith,
> 
> If you can explain to me why ACE should be better than NAT,
> and why deployed applications should stop working with the
> domain names they always have worked with until now,
> I'll accept your comments.

ACE and NAT are completely orthogonal, so comparisons are almost meaningless.
Even as analogy it doesn't fit - e.g. ACE is end-to-end and applications that
need to know about it are aware of it, while NAT corrupts data in midstream
without the endpoints' awareness or consent.

As to the second question, the burden is on you to explain why widely used
applications should break because of a few folks' instistence on using UTF-8.  
To break these applications for the sake of preserving compatibility for a 
relatively few people who have been violating the protocols is simply insane.  
It's more far important to maintain operation of services that are standardized 
and widespread, than it is to maintain operation of services that are nonstandard 
and in limited use.

Keith



From owner-idn@ops.ietf.org  Tue Jul 17 12:10:15 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA10176
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 12:10:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MX8D-000MJc-00
	for idn-data@psg.com; Tue, 17 Jul 2001 08:51:29 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MX8C-000MJV-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 08:51:28 -0700
Received: from [165.227.249.20] (ip20.proper.com [165.227.249.20])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f6HFpKq03879;
	Tue, 17 Jul 2001 08:51:20 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100387b77a0ebb47d8@[165.227.249.20]>
In-Reply-To: <4.2.0.58.J.20010717234452.0362f6c0@sh.w3.mag.keio.ac.jp>
References: <Your message of "Tue, 17 Jul 2001 16:48:04 +0900."
 <4.2.0.58.J.20010717154931.03f7b130@sh.w3.mag.keio.ac.jp>
 <4.2.0.58.J.20010717234452.0362f6c0@sh.w3.mag.keio.ac.jp>
Date: Tue, 17 Jul 2001 08:50:26 -0700
To: Martin Duerst <duerst@w3.org>, Keith Moore <moore@cs.utk.edu>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality   Check)
Cc: Patrik F??tstr  ?? <paf@cisco.com>,
        Russ Rolfe <rrolfe@windows.microsoft.com>, idn@ops.ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 11:47 PM +0900 7/17/01, Martin Duerst wrote:
>If you can explain to me why ACE should be better than NAT,
>and why deployed applications should stop working with the
>domain names they always have worked with until now,
>I'll accept your comments.

I'll do it for Keith:

IDNA lets applications use the domain names that they have always 
worked with just as they are. Your proposal it to break all current 
applications by requiring the application to both do UTF-8 (which 
many don't do) and to do nameprep (which those that currently do 
UTF-8 don't do).

How did you get these two mixed up?

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Tue Jul 17 12:21:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA13219
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 12:21:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MXVE-000NDW-00
	for idn-data@psg.com; Tue, 17 Jul 2001 09:15:16 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MXVD-000NDN-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 09:15:15 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id MAA17887;
        Tue, 17 Jul 2001 12:13:56 -0400 (EDT)
Message-Id: <200107171613.MAA17887@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Dan Oscarsson <Dan.Oscarsson@trab.se>
cc: idn@ops.ietf.org
Subject: Re: [idn] If I used IDNA or UTF-8 at my site 
In-reply-to: Your message of "Tue, 17 Jul 2001 17:35:11 +0200."
             <200107171532.f6HFWAP14278@malmo.trab.se> 
Date: Tue, 17 Jul 2001 12:13:56 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dan,

going directly to 8-bit IDNs has always been a non-starter for many applications.
no matter what this group says, applications protocol standards (or implementations)
are not going to universally embrace UTF-8 as soon as IDNs are approved.

the only real question is, will there be a single ASCII format for IDNs, or will
each application develop its own?

trying to force applications to use UTF-8 serving no purpose other than to delay 
deployment of IDNs.

Keith



From owner-idn@ops.ietf.org  Tue Jul 17 12:23:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA13644
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 12:23:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MXPo-000MzQ-00
	for idn-data@psg.com; Tue, 17 Jul 2001 09:09:40 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MXPn-000MzJ-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 09:09:39 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id MAA17828;
        Tue, 17 Jul 2001 12:09:37 -0400 (EDT)
Message-Id: <200107171609.MAA17828@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Martin Duerst <duerst@w3.org>
cc: idn@ops.ietf.org
Subject: Re: [idn] Mail reliability 
In-reply-to: Your message of "Wed, 18 Jul 2001 00:17:10 +0900."
             <4.2.0.58.J.20010718001411.03563e00@sh.w3.mag.keio.ac.jp> 
Date: Tue, 17 Jul 2001 12:09:37 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> <sneak>Just a side remark. Given things like below, which I see daily,
> I don't think that using UTF-8 in mail headers will cause much more
> problems.</sneak>

but if you really thought about it you'd realize that the problems
with UTF-8 in mail headers would compound those that exist due to other
reasons.  for instance, instead of seeing an error message indicating
that paf's mail was broken, you wouldn't get the message at all because
your UTF-8 domain was munged in transit.



From owner-idn@ops.ietf.org  Tue Jul 17 12:24:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA13923
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 12:24:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MXNu-000Mvl-00
	for idn-data@psg.com; Tue, 17 Jul 2001 09:07:42 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MXNs-000MvO-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 09:07:40 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id MAA17805;
        Tue, 17 Jul 2001 12:07:30 -0400 (EDT)
Message-Id: <200107171607.MAA17805@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Martin Duerst <duerst@w3.org>
cc: sun@cnnic.net.cn, idn@ops.ietf.org
Subject: Re: [idn] draft-ietf-idn-ace-eval-cn-00 
In-reply-to: Your message of "Tue, 17 Jul 2001 23:44:30 +0900."
             <4.2.0.58.J.20010717234201.03647210@sh.w3.mag.keio.ac.jp> 
Date: Tue, 17 Jul 2001 12:07:30 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Not an ACE, but probably worth mentioning anyway:
> 
> UTF-8       21
> 
> With the additional advantage that it's much easier to explain
> to anybody why some names are too long and others are short enough.

is it really?  would an average Greek, Russian, Chinese, Japanese,
or Korean speaker really understand the mapping between characters 
and length of UTF-8 representation any better than the mapping 
between characters and length of (say) DUDE representation?

seems like if the limits are specified in any other form than 
"maximum number of symbols" then users will find this mysterious.
and for many languages UTF-8 requires different octet lengths for 
different characters.

Keith



From owner-idn@ops.ietf.org  Tue Jul 17 12:39:38 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA16833
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 12:39:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MXeg-000Nbo-00
	for idn-data@psg.com; Tue, 17 Jul 2001 09:25:02 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MXef-000Nbc-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 09:25:01 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id MAA18075;
        Tue, 17 Jul 2001 12:24:53 -0400 (EDT)
Message-Id: <200107171624.MAA18075@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Martin Duerst <duerst@w3.org>
cc: Paul Hoffman / IMC <phoffman@imc.org>, Keith Moore <moore@cs.utk.edu>,
        Patrik F??tstr ?? <paf@cisco.com>,
        Russ Rolfe <rrolfe@windows.microsoft.com>, idn@ops.ietf.org
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check) 
In-reply-to: Your message of "Wed, 18 Jul 2001 01:12:29 +0900."
             <4.2.0.58.J.20010718005935.03626120@sh.w3.mag.keio.ac.jp> 
Date: Tue, 17 Jul 2001 12:24:53 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> As I have remarked earlier, we don't need this WG to allow
> people to create random domain name labels. ACE is not
> 'domain names just as they are'. It's a clear layer violation.

That's simply BS.  ACE is an *encoding" just like UTF-8 is an *encoding*.

> You can't do any serious kind of processing (e.g. sorting,
> searching,...) on ACEd domain names.

You can do comparison of names with ACE.  Sorted ACE names are almost
as useful to humans as sorted names in UTF-8, which is to say - not very.
It's true that you cannot search for substrings of an ACE name as
easily as you can do so in UTF-8, but this hardly compels use of UTF-8
where it will break existing applications.

> >Your proposal it to break all current applications by requiring the
> >application to both do UTF-8 (which many don't do)
> 
> There are mainly three cases:
> - Those that just pass data along. Most implementations nowadays are
>    8-bit transparent, for most others, it's easy to clean them.
> - Those that do some actual character processing, but not display.
>    These will require work, but considerably less with UTF-8 than
>    with ACE.
> - Those that do display. Again, less work with UTF-8
>    than with ACE. And more work already done.

For the latter two, the burden in supporting ACE in addition to supporting
UTF-8 is small.  The application has to call API routines in either case -
the differences between ACE and UTF-8 are mostly hidden under those routines.

The other thing that you're leaving out is the additional complexity that
would be required to add UTF-8 negotiation to existing applications that
could not be expected to deal with UTF-8 names.

> >and to do nameprep (which those that currently do UTF-8 don't do).
> 
> Again, nameprep only is easier than nameprep+ACE.

It requires more code, but the application writer doesn't really notice
the difference.

Keith



From owner-idn@ops.ietf.org  Tue Jul 17 12:42:09 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA17237
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 12:42:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MXSJ-000N6D-00
	for idn-data@psg.com; Tue, 17 Jul 2001 09:12:15 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MXSI-000N63-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 09:12:15 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id SAA14375;
	Tue, 17 Jul 2001 18:11:27 +0200 (MET DST)
Date: Tue, 17 Jul 2001 18:01:00 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Martin Duerst <duerst@w3.org>, sun@cnnic.net.cn, idn@ops.ietf.org
Subject: Re: [idn] draft-ietf-idn-ace-eval-cn-00
Message-ID: <707758.995392860@localhost>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-07-17 23.44 +0900 Martin Duerst <duerst@w3.org> wrote:

> Not an ACE, but probably worth mentioning anyway:
> 
> UTF-8       21

If we start going down this path, why not mention UCS-2, USC-4 etc aswell?

Once again, this wg is definitly not the one from my perspective which
should tell how to do new definitions of what is stored in DNS labels -- if
it is not US-ASCII or "undefined".

If you talk about what should be used in application protocols, that is not
a task of this wg either. For example, how to handle non-ascii characters
in SMTP is a task of some SMTP wg. Remember, 2821 and 2822 only took some
5-6 years to finish so maybe we can do that in 4 years this time?

  paf -- I feel like a parrot




From owner-idn@ops.ietf.org  Tue Jul 17 12:47:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA18068
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 12:47:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MXUZ-000NCT-00
	for idn-data@psg.com; Tue, 17 Jul 2001 09:14:35 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MXUY-000NCL-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 09:14:34 -0700
Received: from enoshima (g055087.ppp.asahi-net.or.jp [211.132.55.87])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id BAA10683;
	Wed, 18 Jul 2001 01:14:10 +0900 (JST)
Message-Id: <4.2.0.58.J.20010718005935.03626120@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 18 Jul 2001 01:12:29 +0900
To: Paul Hoffman / IMC <phoffman@imc.org>, Keith Moore <moore@cs.utk.edu>
From: Martin Duerst <duerst@w3.org>
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality  
  Check)
Cc: Patrik F??tstr  ?? <paf@cisco.com>,
        Russ Rolfe <rrolfe@windows.microsoft.com>, idn@ops.ietf.org
In-Reply-To: <p05100387b77a0ebb47d8@[165.227.249.20]>
References: <4.2.0.58.J.20010717234452.0362f6c0@sh.w3.mag.keio.ac.jp>
 <Your message of "Tue, 17 Jul 2001 16:48:04 +0900." <4.2.0.58.J.20010717154931.03f7b130@sh.w3.mag.keio.ac.jp>
 <4.2.0.58.J.20010717234452.0362f6c0@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 08:50 01/07/17 -0700, Paul Hoffman / IMC wrote:
>At 11:47 PM +0900 7/17/01, Martin Duerst wrote:
>>If you can explain to me why ACE should be better than NAT,
>>and why deployed applications should stop working with the
>>domain names they always have worked with until now,
>>I'll accept your comments.
>
>I'll do it for Keith:
>
>IDNA lets applications use the domain names that they have always worked 
>with just as they are.

As I have remarked earlier, we don't need this WG to allow
people to create random domain name labels. ACE is not
'domain names just as they are'. It's a clear layer violation.
You can't do any serious kind of processing (e.g. sorting,
searching,...) on ACEd domain names.


>Your proposal it to break all current applications by requiring the 
>application to both do UTF-8 (which many don't do)

There are mainly three cases:
- Those that just pass data along. Most implementations nowadays are
   8-bit transparent, for most others, it's easy to clean them.
- Those that do some actual character processing, but not display.
   These will require work, but considerably less with UTF-8 than
   with ACE.
- Those that do display. Again, less work with UTF-8
   than with ACE. And more work already done.


>and to do nameprep (which those that currently do UTF-8 don't do).

Again, nameprep only is easier than nameprep+ACE.
And as I have explained to Patrick, while on the registration
side, 100% nameprep and nothing less is extremely important,
on the application side, it's not really that important.


Regards,    Martin.






From owner-idn@ops.ietf.org  Tue Jul 17 13:29:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA27094
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 13:29:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MYLl-000OzQ-00
	for idn-data@psg.com; Tue, 17 Jul 2001 10:09:33 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MYLk-000Oz9-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 10:09:32 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id TAA23585;
	Tue, 17 Jul 2001 19:08:44 +0200 (MET DST)
Date: Tue, 17 Jul 2001 19:04:33 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Martin Duerst <duerst@w3.org>, "Paul Hoffman / IMC" <phoffman@imc.org>,
        Keith Moore <moore@cs.utk.edu>
cc: Russ Rolfe <rrolfe@windows.microsoft.com>, idn@ops.ietf.org
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality   Check)
Message-ID: <936382.995396673@localhost>
In-Reply-To: <4.2.0.58.J.20010718005935.03626120@sh.w3.mag.keio.ac.jp>
References: <4.2.0.58.J.20010717234452.0362f6c0@sh.w3.mag.keio.ac.jp><Your
 message of "Tue, 17 Jul 2001 16:48:04 +0900."
 <4.2.0.58.J.20010717154931.03f7b130@sh.w3.mag.keio.ac.jp>
 <4.2.0.58.J.20010717234452.0362f6c0@sh.w3.mag.keio.ac.jp>
 <4.2.0.58.J.20010718005935.03626120@sh.w3.mag.keio.ac.jp>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-07-18 01.12 +0900 Martin Duerst <duerst@w3.org> wrote:

> Again, nameprep only is easier than nameprep+ACE.
> And as I have explained to Patrick, while on the registration
> side, 100% nameprep and nothing less is extremely important,
> on the application side, it's not really that important.

The day an online stock trader doesn't get his bid in to the broker because
he typed the wrong version of what according to nameprep is the wrong
character, you loose.

  paf




From owner-idn@ops.ietf.org  Tue Jul 17 13:51:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA02113
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 13:51:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MXzR-000OIs-00
	for idn-data@psg.com; Tue, 17 Jul 2001 09:46:29 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MXzQ-000OIK-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 09:46:29 -0700
Received: from enoshima (g055087.ppp.asahi-net.or.jp [211.132.55.87])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id BAA10817;
	Wed, 18 Jul 2001 01:46:33 +0900 (JST)
Message-Id: <4.2.0.58.J.20010718013611.03590100@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 18 Jul 2001 01:45:45 +0900
To: Keith Moore <moore@cs.utk.edu>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] draft-ietf-idn-ace-eval-cn-00 
Cc: sun@cnnic.net.cn, idn@ops.ietf.org
In-Reply-To: <200107171607.MAA17805@astro.cs.utk.edu>
References: <Your message of "Tue, 17 Jul 2001 23:44:30 +0900." <4.2.0.58.J.20010717234201.03647210@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 12:07 01/07/17 -0400, Keith Moore wrote:
> > Not an ACE, but probably worth mentioning anyway:
> >
> > UTF-8       21
> >
> > With the additional advantage that it's much easier to explain
> > to anybody why some names are too long and others are short enough.
>
>is it really?

Very significantly, yes.

>would an average Greek, Russian, Chinese, Japanese,
>or Korean speaker really understand the mapping between characters
>and length of UTF-8 representation any better than the mapping
>between characters and length of (say) DUDE representation?

Greek and Russian may be a bit easier for some of the ACEs,
but for Chinese, Japanese, and Korean, you either just use
some program and believe the output, whatever it may be, or
you go look up the numbers and do the calculations by hand,
which may take you something like 20-30min.

All these cases are very easy with UTF-8.

>seems like if the limits are specified in any other form than
>"maximum number of symbols" then users will find this mysterious.

Well, because different users may even see different numbers
of symbols, there will always stay some bit of mistery.


>and for many languages UTF-8 requires different octet lengths for
>different characters.

Yes. But it's something that isn't too difficult to know, if
you want to know. The toughest case is probably Vietnamese,
because you have ASCII (1 byte), Latin-1/Latin extended A
(2 bytes) and Latin Extended Additional (3 bytes).

Regards,   Martin.



From owner-idn@ops.ietf.org  Tue Jul 17 15:51:25 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA28351
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 15:51:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Majs-0003tl-00
	for idn-data@psg.com; Tue, 17 Jul 2001 12:42:36 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Majq-0003sm-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 12:42:35 -0700
Received: from zetnet.co.uk (man-s190.dialup.zetnet.co.uk [194.247.45.61])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6HJgPg29718
        for <idn@ops.ietf.org>; Tue, 17 Jul 2001 20:42:26 +0100
Message-ID: <3B543741.EE5B9E7@zetnet.co.uk>
Date: Tue, 17 Jul 2001 14:01:53 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: idn@ops.ietf.org
Subject: Re: [idn] pool deadline imminent
References: <8CC03F47967BF14D9710887723FADDB6964D4E@win-msg-02.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

Russ Rolfe wrote:
> Martin Duerst wrote:
> > At 17:46 01/07/12 +0000, Adam M. Costello wrote:
> >> I didn't really understand until this morning that any proposal that
> >> doesn't have seven supporters by tomorrow will be out of the running.

Did that only apply to ACE proposals? I've been reading the list archives
to get an idea of where the group is up to, and I have some ideas that
haven't been proposed in any of the current drafts.

> > Just for the record: If anybody is working on a UTF-8 based
> > (or even ACE/UTF-8 mixed) solution, they herewith all have
> > my support (I won't tell them one-by-one).

I'm working on such a solution; for lack of a better name I'll call it
IDN-8. It is ACE + UTF-8, but with ACE restricted to only the places
where it is needed: RFC 2822 headers and SMTP commands/responses.
UTF-8 is used almost everywhere else, including on the wire for DNS
queries. The most important changes that need to be made are to resolvers,
although applications can link with a compatibility library so that they
work even if the resolver hasn't been changed.

In practice ACE names will leak, and so there are various measures to
minimise any problems caused by that. nameprep is used for
canonicalization and to define which names are valid. The exact choice
of ACE is not critical: maximum lengths are mainly determined by
the efficiency of UTF-8. New or updated software is required to
understand UTF-8 everywhere (including RFC 2822 headers and SMTP
commands/responses).

Can I take it that there is sufficient support for a solution along
these lines that it is worth me writing it up as a formal I-D?

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO1O/MzkCAxeYt5gVAQGm/Af/fWwu5DVKw8yK8T/VBfOTYRzNCvqlQbNM
B/edOs9If9GP4aTMPPjFeXCyaqMqYZx7n2KAjTyoWIEUYiA3hHKZYbDM1OQjQLPa
8GDZqGi/nxzAn95X13DpBlgtqRT8m7IYf36M9DdBxJWMOmlBJ5Pq/TSHbDdCCjdW
/QHdH6+72mnR/aHcPilqLRr7YNW+ZwBeAcL6FcCV2z22TckYGhM+P3XAplUVdRsX
U/yW4ZQ/GyJwds36fAG6osAVvrGWHCcwfEvhHyFwyFJ9bN59eboWuEjLNVzX1SeG
okxjWoggh17mTBAUm2VdUugyp9NbqTWWEiQmFtEg3uVCAseHoboDlg==
=QfE/
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Tue Jul 17 16:59:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA12579
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 16:59:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MbLc-0005Al-00
	for idn-data@psg.com; Tue, 17 Jul 2001 13:21:36 -0700
Received: from sh.lh.vix.com ([204.152.188.26])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MbLb-00057c-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 13:21:35 -0700
Received: from KEYSER (sh.lh.vix.com [204.152.188.26]) 
	by sh.lh.vix.com (8.11.2/8.9.1) via ESMTP id f6HKLHf28993; Tue, 17 Jul 2001 13:21:17 -0700 (PDT)
	env-from (pvm@a21.com)
Message-Id: <4.2.0.58.20010717131643.022a06b0@127.0.0.1>
X-Sender: pvm@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Tue, 17 Jul 2001 13:21:59 -0700
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>,
        idn working group <idn@ops.ietf.org>
From: "Paul V. Mockapetris" <pvm@a21.com>
Subject: RE: [idn] pool deadline imminent
In-Reply-To: <1015970.995322117@localhost>
References: <4.2.0.58.20010716114701.02405d90@127.0.0.1>
 <4.2.0.58.20010716114701.02405d90@127.0.0.1>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_10830984==_.ALT"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--=====================_10830984==_.ALT
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable

At 10:21 PM 7/16/2001 +0200, Patrik F=E4ltstr=F6m wrote:
>--On 01-07-16 11.49 -0700 "Paul V. Mockapetris" <pvm@a21.com> wrote:
>
> > I believe UTF8 solutions deserve consideration as well.
>
>Please explain what you mean by UTF8 solutions?
>
>   paf

Patrik, Sorry a sentence got lost.

I think of this issue from a broader base than just IDN.  My opinion is=20
that we need three efforts:

1. A standard for the use of pure binary/8 bit clean labels (and of course=
=20
content) in the DNS.  This will require changes.  (for example, the ASCII=20
matching rules)  A requirement for pure binary APIs should be articulated,=
=20
even if the APIs themselves are not.  BCPs so that ISPs et al don't hurt=20
themselves with shell scripts may be desirable.

2. Standards preparing, matching, canonicalizing UTF8 at the edge of the=20
DNS before it is carried in 8 bit clean DNS.

3 Standards for whatever encodings (to build APIs) are wanted by those that=
=20
don't want 8 bit clean interfaces.

The intent is that these are layered, so that those that want to bypass=20
encodings and go 8 bit clean can do so.  The UTF8 standards should not be=20
intended for all DNS labels; for example if some application wants to use=20
DNA sequences as four base pairs per byte, that should be OK.

I'm really only an advocate of the first two, the third step is to make=20
this politically palatable
to those that think UTF8, 8 bit clean, and some rules at the edges aren't=20
enough.

UDNS seems the closest, although there are things I would change.



paul=20
--=====================_10830984==_.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
At 10:21 PM 7/16/2001 +0200, Patrik F=E4ltstr=F6m wrote:<br>
<blockquote type=3Dcite cite>--On 01-07-16 11.49 -0700 &quot;Paul V.
Mockapetris&quot; &lt;pvm@a21.com&gt; wrote:<br>
<br>
&gt; I believe UTF8 solutions deserve consideration as well.<br>
<br>
Please explain what you mean by UTF8 solutions?<br>
<br>
&nbsp; paf</blockquote><br>
Patrik, Sorry a sentence got lost.<br>
<br>
I think of this issue from a broader base than just IDN.&nbsp; My opinion
is that we need three efforts:<br>
<br>
1. A standard for the use of pure binary/8 bit clean labels (and of
course content) in the DNS.&nbsp; This will require changes.&nbsp; (for
example, the ASCII matching rules)&nbsp; A requirement for pure binary
APIs should be articulated, even if the APIs themselves are not.&nbsp;
BCPs so that ISPs et al don't hurt themselves with shell scripts may be
desirable.<br>
<br>
2. Standards preparing, matching, canonicalizing UTF8 at the edge of the
DNS before it is carried in 8 bit clean DNS.<br>
<br>
3 Standards for whatever encodings (to build APIs) are wanted by those
that don't want 8 bit clean interfaces.<br>
<br>
The intent is that these are layered, so that those that want to bypass
encodings and go 8 bit clean can do so.&nbsp; The UTF8 standards should
not be intended for all DNS labels; for example if some application wants
to use DNA sequences as four base pairs per byte, that should be=20
OK.<br>
<br>
I'm really only an advocate of the first two, the third step is to make
this politically palatable <br>
to those that think UTF8, 8 bit clean, and some rules at the edges aren't
enough.<br>
<br>
UDNS seems the closest, although there are things I would change.<br>
<br>
<br>
<br>
paul
</html>

--=====================_10830984==_.ALT--




From owner-idn@ops.ietf.org  Tue Jul 17 19:07:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA06852
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 19:07:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MdVA-0009lf-00
	for idn-data@psg.com; Tue, 17 Jul 2001 15:39:36 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MdV9-0009lW-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 15:39:35 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id SAA20665;
        Tue, 17 Jul 2001 18:39:30 -0400 (EDT)
Message-Id: <200107172239.SAA20665@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: David Hopwood <david.hopwood@zetnet.co.uk>
cc: idn@ops.ietf.org
Subject: Re: [idn] pool deadline imminent 
In-reply-to: Your message of "Tue, 17 Jul 2001 14:01:53 BST."
             <3B543741.EE5B9E7@zetnet.co.uk> 
Date: Tue, 17 Jul 2001 18:39:30 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> I'm working on such a solution; for lack of a better name I'll call it
> IDN-8. It is ACE + UTF-8, but with ACE restricted to only the places
> where it is needed: RFC 2822 headers and SMTP commands/responses.

which is out of scope for this working group.

> UTF-8 is used almost everywhere else, including on the wire for DNS
> queries. The most important changes that need to be made are to resolvers,
> although applications can link with a compatibility library so that they
> work even if the resolver hasn't been changed.

for your  proposal to be credible you need to explain how (for instance)
how a legacy email client talking to a legacy resolver can lookup an ACEd
IDN if the on-the-wire protocol uses raw UTF-8.

and for that matter, you should explain why using UTF-8 on the wire in
the DNS query provides any significant benefit over more compact encodings
such as DUDE.  nobody has explained this yet, beyond some vague appeals 
to idealism.

Keith



From owner-idn@ops.ietf.org  Tue Jul 17 19:19:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA08969
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 19:19:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MdZ6-0009uR-00
	for idn-data@psg.com; Tue, 17 Jul 2001 15:43:40 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MdZ6-0009uL-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 15:43:40 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15MdZ5-0004R3-00; Tue, 17 Jul 2001 15:43:39 -0700
Date: Tue, 17 Jul 2001 22:43:39 +0000
To: idn@ops.ietf.org
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check)
Message-ID: <20010717224339.B16252@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4.2.0.58.J.20010717234201.03647210@sh.w3.mag.keio.ac.jp> <4.2.0.58.J.20010717154931.03f7b130@sh.w3.mag.keio.ac.jp>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Martin Duerst <duerst@w3.org> wrote:

> I'm very sure browser vendors prefer UTF-8 with nameprep over ACE with
> nameprep.

If that's true, then they can opt to rely on updated HTML and HTTP
standards that support UTF-8 domain names (using nameprep to compare
them), deploy browsers and servers that conform to the new standards,
and not bother with ACE at all.  (Of course, browsers that include mail
user agents would also need to rely on updated standards for message
headers and SMTP.)  The only time they would need to use ACE would be
to use a legacy resolver, but if they can convince the operating system
providers to add a UTF-8 API to the resolver then they don't have to use
ACE anywhere.

This argument applies to any application or protocol.  ACE is there
if you want to interoperate with 7-bit protocols/formats, but if you
don't want to, then don't, just go ahead and stick to your new 8-bit
protocols.

There are obviously people here who think ACE is important, and
people who think nameprep is important, and people who think UTF-8 in
application protocols is important, and people who think UTF-8 in DNS
is important.  There are obviously people who think other people are
wasting their time on some of these.

Perhaps we should stop trying to convince people that what they're
working on is a waste, and just get out of each other's way.  We can
end up with a standard for each of the above four items, and they need
not all be ready at the same moment.  As an implementor or application
protocol designer, if you think one of the standards is worthless to
you, then don't use it.  (Except for nameprep--I think everyone needs to
use that one.)

AMC

P.S.

> Not an ACE, but probably worth mentioning anyway:
> 
> UTF-8       21

UTF-8 has a slight edge for Han (AMC-ACE-Z can almost always fit at
least 19 Han characters) and Latin, but it's terrible for Indian scripts
(AMC-ACE-Z can fit about twice as many characters) and pretty bad for
other non-Latin alphabetic scripts (AMC-ACE-Z can fit about 1.5 to 1.7
times as many characters).



From owner-idn@ops.ietf.org  Tue Jul 17 19:32:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA11666
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 19:32:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Mdxt-000Ami-00
	for idn-data@psg.com; Tue, 17 Jul 2001 16:09:17 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Mdxs-000Amc-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 16:09:16 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id TAA21194;
        Tue, 17 Jul 2001 19:09:11 -0400 (EDT)
Message-Id: <200107172309.TAA21194@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "David R. Conrad" <david.conrad@nominum.com>
cc: Keith Moore <moore@cs.utk.edu>, David Hopwood <david.hopwood@zetnet.co.uk>,
        idn@ops.ietf.org
Subject: Re: [idn] pool deadline imminent 
In-reply-to: Your message of "Tue, 17 Jul 2001 15:58:48 PDT."
             <5.0.2.1.2.20010717155149.020b5dc8@localhost> 
Date: Tue, 17 Jul 2001 19:09:11 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> 1) DUDE isn't particularly compact, at least in comparison to UTF-8 or some
> of the other ACE alternatives.

sorry, I misread some figures.
 
> 2) Does "idealism" include wanting to simplify the system so one form of
> presentation encoding is in use?

if the operational need for backward compatibility is ignored, yes.

> 3) What implements DUDE now?  What implements UTF-8 now?

since nameprep is a necessary part of any UTF-8 scheme, nobody implements
either one...or at least the number of deployed implementations are so 
small relative to the number of things that need to be upgraded that there
is no practical difference in deployment.
 
> Put me in the camp of those who see similarities between these discussion
> and the NAT/end-to-end holy wars.

me too, I suppose - since both arguments are being made for entirely 
practical reasons.  but the comparison isn't exactly illuminating.

Keith



From owner-idn@ops.ietf.org  Tue Jul 17 19:42:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA13341
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 19:42:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Me7a-000B8l-00
	for idn-data@psg.com; Tue, 17 Jul 2001 16:19:18 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Me7Z-000B8e-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 16:19:17 -0700
Received: from enoshima (g052046.ppp.asahi-net.or.jp [211.132.52.46])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id IAA12033;
	Wed, 18 Jul 2001 08:19:28 +0900 (JST)
Message-Id: <4.2.0.58.J.20010718080904.009fc210@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 18 Jul 2001 08:19:09 +0900
To: Patrik F=?ISO-2022-JP?B?GyRCZ00bKEI=?=tstr
 =?ISO-2022-JP?B?GyRCi04bKEI=?= <paf@cisco.com>,
        Keith Moore <moore@cs.utk.edu>
From: Martin Duerst <duerst@w3.org>
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality  
  Check)
Cc: idn@ops.ietf.org
In-Reply-To: <936382.995396673@localhost>
References: <4.2.0.58.J.20010718005935.03626120@sh.w3.mag.keio.ac.jp>
 <4.2.0.58.J.20010717234452.0362f6c0@sh.w3.mag.keio.ac.jp>
 <Your message of "Tue, 17 Jul 2001 16:48:04 +0900." <4.2.0.58.J.20010717154931.03f7b130@sh.w3.mag.keio.ac.jp>
 <4.2.0.58.J.20010717234452.0362f6c0@sh.w3.mag.keio.ac.jp>
 <4.2.0.58.J.20010718005935.03626120@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

At 19:04 01/07/17 +0200, Patrik F$BgM(Btstr$B‹N(B wrote:
>--On 01-07-18 01.12 +0900 Martin Duerst <duerst@w3.org> wrote:
>
> > Again, nameprep only is easier than nameprep+ACE.
> > And as I have explained to Patrick, while on the registration
> > side, 100% nameprep and nothing less is extremely important,
> > on the application side, it's not really that important.
>
>The day an online stock trader doesn't get his bid in to the broker because
>he typed the wrong version of what according to nameprep is the wrong
>character, you loose.

This is just spreading FUD. No halfway serious online trader types
in the broker address every time he trades. For that, there are
things such as bookmarks and autocompletion.

Also, if it were true, there would be a lot of law suits related to
this because currently in Japan, only half-width ASCII (and not the
full-width equivalents) work for domain names. And because the 'fi'
ligature doesn't work with domain names (but it will with nameprep
as currently defined).


Regards,   Martin.



From owner-idn@ops.ietf.org  Tue Jul 17 19:43:43 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA13465
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 19:43:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Mdnz-000APT-00
	for idn-data@psg.com; Tue, 17 Jul 2001 15:59:03 -0700
Received: from shell.nominum.com ([204.152.187.59])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Mdnz-000APN-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 15:59:03 -0700
Received: from drc-toshiba.nominum.com (shell.nominum.com [204.152.187.59])
	by shell.nominum.com (Postfix) with ESMTP
	id 4E9723190C; Tue, 17 Jul 2001 15:58:50 -0700 (PDT)
Message-Id: <5.0.2.1.2.20010717155149.020b5dc8@localhost>
X-Sender: drc@localhost
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 17 Jul 2001 15:58:48 -0700
To: Keith Moore <moore@cs.utk.edu>, David Hopwood <david.hopwood@zetnet.co.uk>
From: "David R. Conrad" <david.conrad@nominum.com>
Subject: Re: [idn] pool deadline imminent 
Cc: idn@ops.ietf.org
In-Reply-To: <200107172239.SAA20665@astro.cs.utk.edu>
References: <Your message of "Tue, 17 Jul 2001 14:01:53 BST." <3B543741.EE5B9E7@zetnet.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Keith,

At 06:39 PM 7/17/2001 -0400, Keith Moore wrote:
>and for that matter, you should explain why using UTF-8 on the wire in
>the DNS query provides any significant benefit over more compact encodings
>such as DUDE.  nobody has explained this yet, beyond some vague appeals
>to idealism.

Not choosing sides, but:

1) DUDE isn't particularly compact, at least in comparison to UTF-8 or some 
of the other ACE alternatives.

2) Does "idealism" include wanting to simplify the system so one form of 
presentation encoding is in use?

3) What implements DUDE now?  What implements UTF-8 now?

Put me in the camp of those who see similarities between these discussion 
and the NAT/end-to-end holy wars.

Rgds,
-drc




From owner-idn@ops.ietf.org  Tue Jul 17 19:49:38 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA14293
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 19:49:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MeDJ-000BM7-00
	for idn-data@psg.com; Tue, 17 Jul 2001 16:25:13 -0700
Received: from shell.nominum.com ([204.152.187.59])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MeDI-000BLr-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 16:25:13 -0700
Received: from drc-toshiba.nominum.com (shell.nominum.com [204.152.187.59])
	by shell.nominum.com (Postfix) with ESMTP
	id 7BB433190C; Tue, 17 Jul 2001 16:25:00 -0700 (PDT)
Message-Id: <5.0.2.1.2.20010717161543.020900b0@localhost>
X-Sender: drc@localhost
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 17 Jul 2001 16:24:57 -0700
To: Keith Moore <moore@cs.utk.edu>
From: "David R. Conrad" <david.conrad@nominum.com>
Subject: Re: [idn] pool deadline imminent 
Cc: Keith Moore <moore@cs.utk.edu>, David Hopwood <david.hopwood@zetnet.co.uk>,
        idn@ops.ietf.org
In-Reply-To: <200107172309.TAA21194@astro.cs.utk.edu>
References: <Your message of "Tue, 17 Jul 2001 15:58:48 PDT." <5.0.2.1.2.20010717155149.020b5dc8@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Keith,

At 07:09 PM 7/17/2001 -0400, Keith Moore wrote:
> > 2) Does "idealism" include wanting to simplify the system so one form of
> > presentation encoding is in use?
>if the operational need for backward compatibility is ignored, yes.

There are other operational needs beyond backwards compatibility.  One of 
these is providing useful functionality that meets market demands in a 
timeframe the market wants.

> > 3) What implements DUDE now?  What implements UTF-8 now?
>since nameprep is a necessary part of any UTF-8 scheme,

Nameprep has not, as far as I know, been necessary to implement UTF-8 in 
(say) an operating system, an MUA, a web browser, etc.

>nobody implements
>either one...or at least the number of deployed implementations are so
>small relative to the number of things that need to be upgraded that there
>is no practical difference in deployment.

I would think rewriting (say) the operating system, the MUA, the web 
browser, etc. to understand DUDE at the same level at current UTF-8 support 
would imply a difference in deployment.

Don't you worry about replicating the Coloured Book insanity?

Rgds,
-drc




From owner-idn@ops.ietf.org  Tue Jul 17 20:00:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA16439
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 20:00:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MeLW-000Bgd-00
	for idn-data@psg.com; Tue, 17 Jul 2001 16:33:42 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MeLW-000BgW-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 16:33:42 -0700
Received: from enoshima (g052046.ppp.asahi-net.or.jp [211.132.52.46])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id IAA12065;
	Wed, 18 Jul 2001 08:33:43 +0900 (JST)
Message-Id: <4.2.0.58.J.20010718081934.009efdc0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 18 Jul 2001 08:33:23 +0900
To: Keith Moore <moore@cs.utk.edu>
From: Martin Duerst <duerst@w3.org>
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality
  Check) 
Cc: Paul Hoffman / IMC <phoffman@imc.org>, Keith Moore <moore@cs.utk.edu>,
        Patrik F??tstr ?? <paf@cisco.com>,
        Russ Rolfe <rrolfe@windows.microsoft.com>, idn@ops.ietf.org
In-Reply-To: <200107171624.MAA18075@astro.cs.utk.edu>
References: <Your message of "Wed, 18 Jul 2001 01:12:29 +0900." <4.2.0.58.J.20010718005935.03626120@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 12:24 01/07/17 -0400, Keith Moore wrote:
> > As I have remarked earlier, we don't need this WG to allow
> > people to create random domain name labels. ACE is not
> > 'domain names just as they are'. It's a clear layer violation.
>
>ACE is an *encoding" just like UTF-8 is an *encoding*.

Sorry, no. ACE can be reapplied to ACE (the drafts of course prohibit this),
but please try to apply UTF-8 to UTF-8. Also, when the term 'UTF-5' became
known for my original proposal, there was strong pushback in the Unicode
community, and similar for UTF-7, which again maps 'more than ASCII' to
'ASCII'.

Also, ACE is used piecemeal. Maybe the lhs of an email address will
use a different ACE than the rhs, or a different prefix. Maybe it
will restart at dots, or not. There is no definition of how to apply
ACE to a text file. Content-Type: text/plain; charset=XXXACE cannot
be use. If you try to get down that path, you get the horrible
dependencies between mail header syntax and the =? ? ? ?= encoding.

Converting a file from Latin-1 to UTF-8 (or chose your encoding)
is independent of the content of the file. Converting ACE to
UTF-8 needs to parse the file (i.e. go to a different layer).



>The other thing that you're leaving out is the additional complexity that
>would be required to add UTF-8 negotiation to existing applications that
>could not be expected to deal with UTF-8 names.

The main application that really needs this is SMTP. Most others don't.
And those that do would need it for other purposes, anyway.


Regards,    Martin.



From owner-idn@ops.ietf.org  Tue Jul 17 20:50:00 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA28455
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 20:49:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Mf7k-000DZY-00
	for idn-data@psg.com; Tue, 17 Jul 2001 17:23:32 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Mf7e-000DZ3-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 17:23:26 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6I0N2p14658
	for <idn@ops.ietf.org>; Wed, 18 Jul 2001 09:23:06 +0900 (KST)
Message-ID: <021001c10f20$8f0dc920$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Subject: [idn] language scripts classified
Date: Wed, 18 Jul 2001 09:28:20 +0900
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_020C_01C10F6B.FBFA80A0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_020C_01C10F6B.FBFA80A0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit

While gathering  usage frequency data for many language scripts,
I classified them into 6 categories (see enclosed ):

  Will all of these scripts  be frequently  used in IDN ?
  At least #3 archaic scripts and #4 won't and 
  for #1 and #2 , i am neutral yet.
  I am working on #5.

I can find many similarities and ambiguities across these language scripts.
Many Indian language scripts came from the same mother language 
'Brahmi' and have  similarly-looking scripts and numerals .

 see http://www.omniglot.com/writing/yi.htm


Soobok Lee 
------------------------------------------------------------------------

#0  already in ML.com testbed  (I got huge usage frequency samples for these)
Hebrew:
Arabic:
Thai:
Hindi(Devanagari):
Cyrillic:
Greek:
Hiragana:
Katakana:
Hangul:
Han Ideograph:


#1 few native speakers

Georgian: < 3.5 millions
Cherokee:  100,000 (North America)
Thaana  :  100,000 (Maldives)
Armenian:   2 millions


#2 two languages in one country:

bengali: Indian language ( > 180 millions )
gujarati: Indian language  
gurmukhi: Indian language
kannada: Indian language
malayalam: Indian language
oriya: Indian language
telugu: Indian language

tibetan : chinese (mainland china)   , < 5 milliions
yi syllables: chinese (mainland china), < 5 millions


#3 Archaic
Ogham: 
Runic:
Gothic:
Syriac: only used for for liturgical purpose 
Unified Canadian ABoriginal Syllables:


#4 Written only vertically
mongolian:  (once had been abolished and restored)


#5  others

sinhala : Sri lanka
tamil : Sri lanka
khmer : Camobodian
lao  : Laos, Thai
ethiopic : Ethiopia
myanmar : Burmese


------=_NextPart_000_020C_01C10F6B.FBFA80A0
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dks_c_5601-1987">
<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>While&nbsp;gathering&nbsp; usage frequency data for =
many=20
language scripts,</FONT></DIV>
<DIV><FONT size=3D2>I&nbsp;classified them into 6 categories (see =
enclosed=20
):</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>&nbsp; Will all of these scripts&nbsp; be frequently =

&nbsp;used in IDN ?</FONT></DIV>
<DIV><FONT size=3D2>&nbsp; At least #3 archaic scripts =
and&nbsp;#4&nbsp;won't and=20
</FONT></DIV>
<DIV><FONT size=3D2>&nbsp; for #1 and #2&nbsp;, i am neutral =
yet.</FONT></DIV>
<DIV><FONT size=3D2>&nbsp; I am working on #5.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>I can find many similarities and ambiguities across =
these=20
language scripts.</FONT></DIV>
<DIV><FONT size=3D2>Many Indian language scripts came from the same =
mother=20
language </FONT></DIV>
<DIV><FONT size=3D2>'Brahmi' and </FONT><FONT size=3D2>have&nbsp; =
similarly-looking=20
scripts and numerals&nbsp;.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>&nbsp;</FONT><FONT size=3D2>see <A=20
href=3D"http://www.omniglot.com/writing/yi.htm">http://www.omniglot.com/w=
riting/yi.htm</A></FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Soobok Lee&nbsp;</FONT></DIV>
<DIV><FONT=20
size=3D2>----------------------------------------------------------------=
--------</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>#0&nbsp; already in ML.com testbed&nbsp; (I got huge =

usage&nbsp;frequency samples for these)</FONT></DIV>
<DIV><FONT size=3D2>Hebrew:</FONT></DIV>
<DIV><FONT size=3D2>Arabic:</FONT></DIV>
<DIV><FONT size=3D2>Thai:</FONT></DIV>
<DIV><FONT size=3D2>Hindi(Devanagari):</FONT></DIV>
<DIV><FONT size=3D2>Cyrillic:</FONT></DIV>
<DIV><FONT size=3D2>Greek:</FONT></DIV>
<DIV><FONT size=3D2>Hiragana:</FONT></DIV>
<DIV><FONT size=3D2>Katakana:</FONT></DIV>
<DIV><FONT size=3D2>Hangul:</FONT></DIV>
<DIV><FONT size=3D2>Han Ideograph:</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2></FONT><BR><FONT size=3D2>#1 few native =
speakers</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Georgian: &lt; 3.5 millions<BR>Cherokee:&nbsp; =
100,000 (North=20
America)<BR>Thaana&nbsp; :&nbsp; 100,000 =
(Maldives)<BR>Armenian:&nbsp;&nbsp; 2=20
millions</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>#2&nbsp;two languages in one country:</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>bengali: Indian language ( &gt; 180 millions =
)</FONT></DIV>
<DIV><FONT size=3D2>gujarati: Indian language&nbsp; </FONT></DIV>
<DIV><FONT size=3D2>gurmukhi: Indian language<BR>kannada: Indian=20
language<BR>malayalam: Indian language<BR>oriya: Indian =
language<BR>telugu:=20
Indian language</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>tibetan : chinese (mainland china)&nbsp;&nbsp; , =
&lt; 5=20
milliions<BR>yi syllables: chinese (mainland china), &lt; 5=20
millions</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>#3 Archaic<BR>Ogham: =
<BR>Runic:<BR>Gothic:<BR>Syriac: only=20
used for for liturgical purpose <BR>Unified Canadian ABoriginal=20
Syllables:</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>#4 Written only vertically<BR>mongolian:&nbsp; (once =
had been=20
abolished and restored)<BR></FONT></DIV>
<DIV><FONT size=3D2>&nbsp;</DIV></FONT>
<DIV>
<DIV><FONT size=3D2>#5&nbsp; others</FONT></DIV>
<DIV><FONT size=3D2><BR>sinhala : Sri lanka<BR>tamil : Sri =
lanka<BR>khmer :=20
Camobodian<BR>lao&nbsp; : Laos, Thai<BR>ethiopic : Ethiopia<BR>myanmar : =

Burmese</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV></DIV></BODY></HTML>

------=_NextPart_000_020C_01C10F6B.FBFA80A0--




From owner-idn@ops.ietf.org  Tue Jul 17 20:56:35 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA29839
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 20:56:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MfSd-000EVD-00
	for idn-data@psg.com; Tue, 17 Jul 2001 17:45:07 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MfSd-000EV7-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 17:45:07 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id UAA21744;
        Tue, 17 Jul 2001 20:45:04 -0400 (EDT)
Message-Id: <200107180045.UAA21744@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Adam M. Costello" <amc@cs.berkeley.edu>
cc: idn@ops.ietf.org
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check) 
In-reply-to: Your message of "Tue, 17 Jul 2001 22:43:39 -0000."
             <20010717224339.B16252@arwen.cs.berkeley.edu> 
Date: Tue, 17 Jul 2001 20:45:03 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Perhaps we should stop trying to convince people that what they're
> working on is a waste, and just get out of each other's way.  

that sounds like a fine strategy. 

It's painfully clear that we need an ACE format for IDNs to be used in 
legacy appliactions, and that queries for ACE-encoded IDNs have to work.

If people can make a good case that we also need to support queries that 
use UTF-8 (or some other general purpose encoding of 10646), more power 
to them.  I won't swear that the case cannot be made, it's just that when
I did my own analysis of the effort involved (with the requirement that
ACE queries produce consistent results with native queries), it looked 
to be a fair amount of effort for a marginal amount of gain.   

The one thing that I don't want is for the folks who want UTF-8 on the
wire to block progress on deployment of an ACE solution.  Because it's
clear that we need to move forward on this, and that we will need the 
ACE solution in any case.

We can probably afford to have two ways of looking up IDNs.  We 
cannot afford a tug-of-war in this group that delays adoption of
any solution.

--

What I'd really like to see us work on is the transcribability problem.
This is a problem that all of the proposals have in common - there
are still too many similar glyphs with different code points that are not
folded by nameprep.  I see this as the biggest remaining problem that
must be solved before we can standardize an ACE lookup scheme for IDNs.
(even if we standardize an alternate one later that uses UTF-8 or some
other encoding)

Keith



From owner-idn@ops.ietf.org  Tue Jul 17 20:57:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA00146
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 20:57:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MfAw-000Dld-00
	for idn-data@psg.com; Tue, 17 Jul 2001 17:26:50 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MfAv-000DlX-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 17:26:49 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id UAA21659;
        Tue, 17 Jul 2001 20:26:45 -0400 (EDT)
Message-Id: <200107180026.UAA21659@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "David R. Conrad" <david.conrad@nominum.com>
cc: Keith Moore <moore@cs.utk.edu>, David Hopwood <david.hopwood@zetnet.co.uk>,
        idn@ops.ietf.org
Subject: Re: [idn] pool deadline imminent 
In-reply-to: Your message of "Tue, 17 Jul 2001 16:24:57 PDT."
             <5.0.2.1.2.20010717161543.020900b0@localhost> 
Date: Tue, 17 Jul 2001 20:26:45 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > > 2) Does "idealism" include wanting to simplify the system so one form of
> > > presentation encoding is in use?
> >if the operational need for backward compatibility is ignored, yes.
> 
> There are other operational needs beyond backwards compatibility.  One of
> these is providing useful functionality that meets market demands in a
> timeframe the market wants.

Absolutely.  But this also favors an ACE solution.

True, you can provide a UTF-8 solution sooner to the market - but only if 
you pretend that the various things out there that already use UTF-8
do so in an acceptable manner.  For instance, you have to ignore the 
need for IDNs lookups to work even after the IDN has been transcribed 
by a human or transcoded into a different character set encoding.

> > > 3) What implements DUDE now?  What implements UTF-8 now?
> >since nameprep is a necessary part of any UTF-8 scheme,
> 
> Nameprep has not, as far as I know, been necessary to implement UTF-8 in
> (say) an operating system, an MUA, a web browser, etc.

No, you don't need nameprep to implement UTF-8 lookups.  You just need
it before UTF-8 lookups (or any kind of lookup using the 10646 repertoire) 
will work well.

> >nobody implements
> >either one...or at least the number of deployed implementations are so
> >small relative to the number of things that need to be upgraded that there
> >is no practical difference in deployment.
> 
> I would think rewriting (say) the operating system, the MUA, the web
> browser, etc. to understand DUDE at the same level at current UTF-8 support
> would imply a difference in deployment.

I would think that also if it were relevant.  But in fact there's no need to 
rewrite an operating system, web browser, etc.  Applications  that already
know how to input and display 10646 characters (regardless of encoding) 
need only small changes to use an ACE for IDN lookups, and they will need
those changes in any case due to (a) the need to do nameprep and (b)
the need to interoperate with other legacy applications.  

And there's absolutely nothing that prevents a vendor from shipping an app 
that uses DUDE on legacy operating systems.

> Don't you worry about replicating the Coloured Book insanity?

There have been so many different sets of coloured books (with different
kinds of insanity) that I don't know which one you mean.

Keith



From owner-idn@ops.ietf.org  Tue Jul 17 21:23:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA04762
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 21:23:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MfJx-000E74-00
	for idn-data@psg.com; Tue, 17 Jul 2001 17:36:09 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MfJw-000E6y-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 17:36:08 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id UAA21703;
        Tue, 17 Jul 2001 20:36:00 -0400 (EDT)
Message-Id: <200107180036.UAA21703@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Martin Duerst <duerst@w3.org>
cc: Keith Moore <moore@cs.utk.edu>, Paul Hoffman / IMC <phoffman@imc.org>,
        Patrik F??tstr ?? <paf@cisco.com>,
        Russ Rolfe <rrolfe@windows.microsoft.com>, idn@ops.ietf.org
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check) 
In-reply-to: Your message of "Wed, 18 Jul 2001 08:33:23 +0900."
             <4.2.0.58.J.20010718081934.009efdc0@sh.w3.mag.keio.ac.jp> 
Date: Tue, 17 Jul 2001 20:36:00 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> At 12:24 01/07/17 -0400, Keith Moore wrote:
> > > As I have remarked earlier, we don't need this WG to allow
> > > people to create random domain name labels. ACE is not
> > > 'domain names just as they are'. It's a clear layer violation.
> >
> >ACE is an *encoding" just like UTF-8 is an *encoding*.
> 
> Sorry, no. ACE can be reapplied to ACE (the drafts of course prohibit this),
> but please try to apply UTF-8 to UTF-8. 

I fail to see how this is relevant.

> Also, ACE is used piecemeal. 

That's true.  ACE is an encoding, but is not a general purpose encoding.
It's designed for a narrow but important purpose, and it's sufficiently ugly 
that you really would not want to use it except when necessary.  But there 
are cases where it is necessary. 

> >The other thing that you're leaving out is the additional complexity that
> >would be required to add UTF-8 negotiation to existing applications that
> >could not be expected to deal with UTF-8 names.
> 
> The main application that really needs this is SMTP. Most others don't.

that's simply false.  any deployed application that exchanges DNS names
as protocol elements needs ACE if those deployed codes are expected to
interoperate (and exchange DNS names) with new codes that use IDNs. 

true, there are sometimes other ways to solve the problem than ACE - 
explicit negotiation for instance.  But this isn't feasible with all
applications, and it's very unattractive for most of those in which it is
feasible.

Keith



From owner-idn@ops.ietf.org  Tue Jul 17 21:37:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA08700
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 21:37:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Mg94-000G0z-00
	for idn-data@psg.com; Tue, 17 Jul 2001 18:28:58 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Mg93-000G0L-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 18:28:57 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP id 33BE9FFC06
	for <idn@ops.ietf.org>; Wed, 18 Jul 2001 09:30:48 +0800 (SGT)
Message-ID: <070001c10f28$faeb5600$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: <idn@ops.ietf.org>
Subject: [idn] Fw: IDN WG discussions (3,4)
Date: Wed, 18 Jul 2001 09:28:42 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

not sure if it is relevant to the wg but i doing what the sender
requested.

james

----- Original Message -----
From: "sue me" <idnwg@email.com>
To: <idnwg@email.com>
Sent: Wednesday, July 18, 2001 2:03 AM
Subject: IDN WG discussions (3,4)


> (I was asked to forward this email, so please help me post it up at
your IDN WG discussion forum.)
>
> Here is what ICANN said "...the internationalization of the Internet's
domain name system must be accomplished through standards that are open,
non-proprietary, and fully compatible with the Internet's existing
end-to-end model and that preserve globally unique naming in a
universally resolvable public name space..."
>
> In other words, NO TECHNOLOGY WILL BE ACCEPTED if it endangers the
stability of the internet by giving others the opportunity to create an
alternate root.
>
> Anyone is free to have their personal agendas.  The question is- is
your personal agendas in parallel with those of the government of the
United States of America?  If it is, then you are in luck and if not,
then you are out of luck!
>
> Any decision made concerning the future of IDNs is what is best for
the world politically and NOT what is best for the internet technically.
>
> So if I were you guys, I will stop all the mean attacks on each other.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
> _______________________________________________
> Make PC-to-Phone calls with Net2Phone.
> Sign-up today at: http://www.net2phone.com/cgi-bin/link.cgi?121
>
>
>




From owner-idn@ops.ietf.org  Tue Jul 17 21:38:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA08770
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 21:38:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MgBy-000GCb-00
	for idn-data@psg.com; Tue, 17 Jul 2001 18:31:58 -0700
From: The IESG <iesg-secretary@ietf.org>
Subject: [idn] Note Well
Date: Tue, 17 Jul 2001 13:16:53 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15MgBy-000GCb-00@psg.com>
To: idn-data@psg.com


Greetings,

This is the revised text of the NOTE WELL statement.

------------------------------------------------------

NOTE WELL

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026, which
grants to the IETF and its participants certain licenses and rights in
such statements.

Such statements include verbal statements in IETF meetings, as well as
written and electronic communications made at any time or place, which
are addressed to:

    - the IETF plenary session,
    - any IETF working group or portion thereof,
    - the IESG, or any member thereof on behalf of the IESG,
    - the IAB or any member thereof on behalf of the IAB,
    - any IETF mailing list, including the IETF list itself,
      any working group or design team list, or any other list
      functioning under IETF auspices,
    - the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.





From owner-idn@ops.ietf.org  Tue Jul 17 22:28:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA17010
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 22:28:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MgyE-000IE3-00
	for idn-data@psg.com; Tue, 17 Jul 2001 19:21:50 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MgyE-000IDt-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 19:21:50 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id WAA22344;
        Tue, 17 Jul 2001 22:21:47 -0400 (EDT)
Message-Id: <200107180221.WAA22344@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/ 
From: Keith Moore <moore@cs.utk.edu>
To: "David R. Conrad" <david.conrad@nominum.com>
cc: Keith Moore <moore@cs.utk.edu>, idn@ops.ietf.org
Subject: Re: [idn] pool deadline imminent 
In-reply-to: Your message of "Tue, 17 Jul 2001 19:01:00 PDT."
             <5.0.2.1.2.20010717173427.02ff3330@localhost> 
Date: Tue, 17 Jul 2001 22:21:47 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > > Don't you worry about replicating the Coloured Book insanity?
> >There have been so many different sets of coloured books (with different
> >kinds of insanity) that I don't know which one you mean.
> 
> Sorry.  Showing my age.  UK Coloured Book naming system that reversed the
> labels (at least according to 1034/1035 specification).  Despite programs
> and gateways designed to reverse the UK names, they leaked and resulted in
> lots of annoyance and confusion.

ah yes.  (oddly enough, that particular kind of colored book hadn't occured
to me, even though I'd written code to deal with it in a mailing list manager)

no matter what solution is chosen, we'll have leakage (in both directions) 
between legacy environments (that in general can only deal with ASCII names)
and environments that are explicitly written to deal with IDNs.   the major 
difference between the proposal camps is in how often the names leak, and 
what breaks when the names leak.  

> I am worried that a similar thing will happen with folks using ACE --
> people will (say) cut and paste a (utf-8 representation of a) name from an
> application into something that is supposed to do lookups (based on ACE)
> and those lookups will fail because a conversion from UTF-8 to ACE didn't
> happen.  To the user, this won't make sense since could look identical.

we can't avoid that case no matter what solution.  most legacy apps won't
be able to deal correctly with IDNs that are input in native format, period.

Keith



From owner-idn@ops.ietf.org  Tue Jul 17 22:34:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA18617
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 22:34:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Mgpj-000Hr4-00
	for idn-data@psg.com; Tue, 17 Jul 2001 19:13:03 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Mgpi-000Hqy-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 19:13:02 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6I2Clp07115;
	Wed, 18 Jul 2001 11:12:47 +0900 (KST)
Message-ID: <026b01c10f2f$da789660$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
Subject: [idn] Re: language scripts classified
Date: Wed, 18 Jul 2001 11:17:53 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Some corrections.
someone suggests that these two should be moved to #1.
These are modern scripts used by some minorities. sorry.

Syriac: only used for for liturgical purpose 
Unified Canadian ABoriginal Syllables:  

----- Original Message ----- 
From: Soobok Lee 
To: idn@ops.ietf.org 
Sent: Wednesday, July 18, 2001 9:28 AM
Subject: language scripts classified


While gathering  usage frequency data for many language scripts,
I classified them into 6 categories (see enclosed ):

  Will all of these scripts  be frequently  used in IDN ?
  At least #3 archaic scripts and #4 won't and 
  for #1 and #2 , i am neutral yet.
  I am working on #5.

I can find many similarities and ambiguities across these language scripts.
Many Indian language scripts came from the same mother language 
'Brahmi' and have  similarly-looking scripts and numerals .

 see http://www.omniglot.com/writing/yi.htm


Soobok Lee 
------------------------------------------------------------------------

#0  already in ML.com testbed  (I got huge usage frequency samples for these)
Hebrew:
Arabic:
Thai:
Hindi(Devanagari):
Cyrillic:
Greek:
Hiragana:
Katakana:
Hangul:
Han Ideograph:


#1 few native speakers

Georgian: < 3.5 millions
Cherokee:  100,000 (North America)
Thaana  :  100,000 (Maldives)
Armenian:   2 millions


#2 two languages in one country:

bengali: Indian language ( > 180 millions )
gujarati: Indian language  
gurmukhi: Indian language
kannada: Indian language
malayalam: Indian language
oriya: Indian language
telugu: Indian language

tibetan : chinese (mainland china)   , < 5 milliions
yi syllables: chinese (mainland china), < 5 millions


#3 Archaic
Ogham: 
Runic:
Gothic:
Syriac: only used for for liturgical purpose 
Unified Canadian ABoriginal Syllables:


#4 Written only vertically
mongolian:  (once had been abolished and restored)


#5  others

sinhala : Sri lanka
tamil : Sri lanka
khmer : Camobodian
lao  : Laos, Thai
ethiopic : Ethiopia
myanmar : Burmese




From owner-idn@ops.ietf.org  Tue Jul 17 22:36:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA18770
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 22:36:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MgeJ-000HK8-00
	for idn-data@psg.com; Tue, 17 Jul 2001 19:01:15 -0700
Received: from shell.nominum.com ([204.152.187.59])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MgeI-000HJw-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 19:01:14 -0700
Received: from drc-toshiba.nominum.com (shell.nominum.com [204.152.187.59])
	by shell.nominum.com (Postfix) with ESMTP
	id EE88C3190D; Tue, 17 Jul 2001 19:01:00 -0700 (PDT)
Message-Id: <5.0.2.1.2.20010717173427.02ff3330@localhost>
X-Sender: drc@localhost
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 17 Jul 2001 19:01:00 -0700
To: Keith Moore <moore@cs.utk.edu>
From: "David R. Conrad" <david.conrad@nominum.com>
Subject: Re: [idn] pool deadline imminent 
Cc: idn@ops.ietf.org
In-Reply-To: <200107180026.UAA21659@astro.cs.utk.edu>
References: <Your message of "Tue, 17 Jul 2001 16:24:57 PDT." <5.0.2.1.2.20010717161543.020900b0@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 08:26 PM 7/17/2001 -0400, Keith Moore wrote:
> > Don't you worry about replicating the Coloured Book insanity?
>There have been so many different sets of coloured books (with different
>kinds of insanity) that I don't know which one you mean.

Sorry.  Showing my age.  UK Coloured Book naming system that reversed the 
labels (at least according to 1034/1035 specification).  Despite programs 
and gateways designed to reverse the UK names, they leaked and resulted in 
lots of annoyance and confusion.

I am worried that a similar thing will happen with folks using ACE -- 
people will (say) cut and paste a (utf-8 representation of a) name from an 
application into something that is supposed to do lookups (based on ACE) 
and those lookups will fail because a conversion from UTF-8 to ACE didn't 
happen.  To the user, this won't make sense since could look identical.

Rgds,
-drc

P.S. To be clear, I really am not taking sides.  I find all the options 
offensive (:-)).




From owner-idn@ops.ietf.org  Tue Jul 17 23:17:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA23732
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 23:17:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MhOU-000J5s-00
	for idn-data@psg.com; Tue, 17 Jul 2001 19:48:58 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MhOU-000J5m-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 19:48:58 -0700
Received: from [24.252.219.84] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 161523; Tue, 17 Jul 2001 19:48:25 -0700
Message-ID: <3B54F916.7200C58B@ehsco.com>
Date: Tue, 17 Jul 2001 21:48:54 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check)
References: <200107180045.UAA21744@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> It's painfully clear that we need an ACE format for IDNs to be used in
> legacy appliactions, and that queries for ACE-encoded IDNs have to
> work.

Yes.

> If people can make a good case that we also need to support queries
> that use UTF-8 (or some other general purpose encoding of 10646),
> more power to them.

Future applications will want to be totally internationalized from the
ground up, without any legacy crap in the soup. Ease-of-deployment in
programming and operating environments where UTF-8 is easily accessed.
Overall "servicability" of DNS, where problems with UTF-8 will be much
simpler to analyze than similar problems with ACE. More to the point,
however, it does not need to be "justified" if there is a sufficient
amount of interest from knowledgable people, which there is.

And while it would be nice to have the just-send-UTF8 camp recognize the
merits of ACE, it would also be nice to have the ACE-only camp recognize
that many of their peers find some measurable amount of merit in UTF-8.

> We can probably afford to have two ways of looking up IDNs.

There have been many proposals for a dual-mode approach, and this should
illustrate that many folks recognize the merits of both camps already. And
if it is done right, it doesn't suffer from compromise syndrome, since
folks can deploy the one they wish without suffering any real penalties
(you can only-send-ACE or just-send-UTF8, as you choose, although it would
be self-defeating to ignore half the benefits). And we can do it cheaply.

If we can at least agree to work on a dual-mode approach -- even if we
think the other half is nuts -- we will get the kinks worked out that much
faster and to everyone's benefit.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Tue Jul 17 23:29:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA25059
	for <idn-archive@lists.ietf.org>; Tue, 17 Jul 2001 23:29:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Mhn7-000K6x-00
	for idn-data@psg.com; Tue, 17 Jul 2001 20:14:25 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Mhn6-000K6r-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 20:14:24 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id XAA22669;
        Tue, 17 Jul 2001 23:14:19 -0400 (EDT)
Message-Id: <200107180314.XAA22669@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: Keith Moore <moore@cs.utk.edu>, "Adam M. Costello" <amc@cs.berkeley.edu>,
        idn@ops.ietf.org
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check) 
In-reply-to: Your message of "Tue, 17 Jul 2001 21:48:54 CDT."
             <3B54F916.7200C58B@ehsco.com> 
Date: Tue, 17 Jul 2001 23:14:18 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > It's painfully clear that we need an ACE format for IDNs to be used in
> > legacy appliactions, and that queries for ACE-encoded IDNs have to
> > work.
> 
> Yes.
> 
> > If people can make a good case that we also need to support queries
> > that use UTF-8 (or some other general purpose encoding of 10646),
> > more power to them.
> 
> Future applications will want to be totally internationalized from the
> ground up, without any legacy crap in the soup. 

No doubt about that at all.   I have some doubts about whether it will
really matter if they get it, but I don't doubt that people want it.

(I don't think it affects such applications in any significant way 
if they use ACE only under the hood in DNS queries. After all, the format 
of DNS names within queries is *already* very different than that used by 
applications, without the dots, with each label prefixed by a byte count,
with label compression, etc.  But very few apps need to care about this.)

> More to the point,
> however, it does not need to be "justified" if there is a sufficient
> amount of interest from knowledgable people, which there is.

Well, it still needs a cost-vs-benefit justification.  But perhaps those
knowledgable people can provide one.  

> And while it would be nice to have the just-send-UTF8 camp recognize the
> merits of ACE, it would also be nice to have the ACE-only camp recognize
> that many of their peers find some measurable amount of merit in UTF-8.

I doubt that anyone fails to see the merit in just-send-UTF-8 within 
applications, under some conditions.  It's the notion that it's always 
okay for applications to just-send-UTF-8 that seems to have little merit.

> > We can probably afford to have two ways of looking up IDNs.
> 
> There have been many proposals for a dual-mode approach, and this should
> illustrate that many folks recognize the merits of both camps already. And
> if it is done right, it doesn't suffer from compromise syndrome, since
> folks can deploy the one they wish without suffering any real penalties

That seems like a stretch.  But perhaps the proponents should go off and
work out the details for themselves.

I suggest some essential criteria for a dual-mode solution: 

- ACE lookups have to work from legacy apps for all ACE-encoded IDNs, 
  without additional support on the part of applications, hosts, caches, 
  resolvers, or servers.  

- Native lookups from IDN-aware apps have to work for all Native IDNs, 
  though it might be acceptable to impose some new requirements on 
  those applications, their hosts, caches, resolvers, etc.  

- ACE lookups and Native lookups have to produce results that are
  consistent with one another in both results and failure rates.

> If we can at least agree to work on a dual-mode approach -- even if we
> think the other half is nuts -- we will get the kinks worked out that much
> faster and to everyone's benefit.

Right.  But if we do this, working out the details of the native approach
should not hold back the ACE solution.

Keith

p.s. I still think the argument about what to send over the wire in DNS
is specious.  I get the strong impression that people who are arguing
in favor of using UTF-8 over the wire in DNS are really wanting to insist
that we use UTF-8 over the wire, immediately, in all applications - or
at least that this is the default behavior for all applications even if
a few applications make an exception to this rule.  I don't think this is
feasable, and even if it were, it's not within this WG's purview.

But if the proponents of UTF-8 over the wire in DNS can come up with a
sound proposal and make a good case for it, we ought to seriously consider
it. 



From owner-idn@ops.ietf.org  Wed Jul 18 01:43:41 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA23373
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 01:43:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MjtM-000Pbs-00
	for idn-data@psg.com; Tue, 17 Jul 2001 22:29:00 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MjtK-000Pbm-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 22:28:59 -0700
Received: from enoshima (dhcp-100-151.mag.keio.ac.jp [133.27.195.151])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id OAA12835;
	Wed, 18 Jul 2001 14:29:03 +0900 (JST)
Message-Id: <4.2.0.58.J.20010718120208.04004790@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 18 Jul 2001 14:10:04 +0900
To: Keith Moore <moore@cs.utk.edu>
From: Martin Duerst <duerst@w3.org>
Subject: [idn] Back to work (Nameprep) (was: Re: Just send UTF-8 with
  nameprep (was: RE: [idn] Reality Check)) 
Cc: idn@ops.ietf.org
In-Reply-To: <200107180045.UAA21744@astro.cs.utk.edu>
References: <Your message of "Tue, 17 Jul 2001 22:43:39 -0000." <20010717224339.B16252@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 20:45 01/07/17 -0400, Keith Moore wrote:

>We can probably afford to have two ways of looking up IDNs.  We
>cannot afford a tug-of-war in this group that delays adoption of
>any solution.

Thanks, Keith!
This is an excellent proposal for a forward-looking compromise.


>What I'd really like to see us work on is the transcribability problem.
>This is a problem that all of the proposals have in common - there
>are still too many similar glyphs with different code points that are not
>folded by nameprep.  I see this as the biggest remaining problem that
>must be solved before we can standardize an ACE lookup scheme for IDNs.
>(even if we standardize an alternate one later that uses UTF-8 or some
>other encoding)

Very good point. Do you have any particular kind of similarities
in mind, or can you give some examples? Or do you have some kind
of principles or tests in mind that should be applied? Or any
particular kind of procedure that we should follow?

Also, there are some things that get folded in nameprep that should not.
This is not so important if nameprep is mainly seen as the absolute
check for registrations. But if it is supposed to be strictly applied
on every occasion, in particular every time a name is resolved,
as e.g. Patrick is describing it, these foldings may lead to people
believing that these characters are acceptable in a domain name the
same way an upper-case character is.

What should be eliminated are:

1) Characters that are very clearly visually distinct from the ones
    they are mapped to. (for obvious reasons)
2) Characters that completely map to ASCII-only characters
    (to make sure that current applications and applications doing
    nameprep behave the same way for ASCII-only).

An example of a character for which both of the above apply is
U+2460 CIRCLED DIGIT ONE. This is a simple digit 'one' in a circle.
Obviously, everybody can immediately see that it's different from
just a '1'. Also, if it's mapped to '1' by nameprep applications,
these applications will behave differently from applications not using
nameprep (i.e. everything out there now).

There are quite a few of these, all identified with <circle> (or
similar) in Unicode. There are also quite a few to which only
1) applies (circles with things other than ASCII letters in them,...)
and a few to which only 2) applies (e.g. fi, ffi,... ligatures).

I propose that all of them should be rejected, for the reasons above,
rather than folded.


Regards,   Martin.




From owner-idn@ops.ietf.org  Wed Jul 18 02:01:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA01597
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 02:01:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MjtQ-000Pc1-00
	for idn-data@psg.com; Tue, 17 Jul 2001 22:29:04 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MjtP-000Pbv-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 22:29:04 -0700
Received: from enoshima (dhcp-100-151.mag.keio.ac.jp [133.27.195.151])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id OAA12823;
	Wed, 18 Jul 2001 14:29:01 +0900 (JST)
Message-Id: <4.2.0.58.J.20010718100321.040053e0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 18 Jul 2001 14:05:41 +0900
To: Keith Moore <moore@cs.utk.edu>
From: Martin Duerst <duerst@w3.org>
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality
  Check) 
Cc: Keith Moore <moore@cs.utk.edu>, Paul Hoffman / IMC <phoffman@imc.org>,
        Patrik F??tstr ?? <paf@cisco.com>,
        Russ Rolfe <rrolfe@windows.microsoft.com>, idn@ops.ietf.org
In-Reply-To: <200107180036.UAA21703@astro.cs.utk.edu>
References: <Your message of "Wed, 18 Jul 2001 08:33:23 +0900." <4.2.0.58.J.20010718081934.009efdc0@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 20:36 01/07/17 -0400, Keith Moore wrote:
> > At 12:24 01/07/17 -0400, Keith Moore wrote:
> > > > As I have remarked earlier, we don't need this WG to allow
> > > > people to create random domain name labels. ACE is not
> > > > 'domain names just as they are'. It's a clear layer violation.
> > >
> > >ACE is an *encoding" just like UTF-8 is an *encoding*.
> >
> > Sorry, no. ACE can be reapplied to ACE (the drafts of course prohibit 
> this),
> > but please try to apply UTF-8 to UTF-8.
>
>I fail to see how this is relevant.

Architecturally, because it's folding one layer back onto the same layer.
Operationally, because some implementations will get it wrong, and we will
see ACE over ACE the same way we have seen Mime over Mime.


> > Also, ACE is used piecemeal.
>
>That's true.  ACE is an encoding, but is not a general purpose encoding.
>It's designed for a narrow but important purpose, and it's sufficiently ugly
>that you really would not want to use it except when necessary.  But there
>are cases where it is necessary.

What I see comming more and more is that this 'narrow but important'
argument will be applied over and over: It's not worth to do anything
to upgrade protocol A because the DNS is ACE, then it's not worth to
upgrade protocol B because protocol A uses ACE, and so on.

If for example the IDNA draft could say that resolvers should provide
a way (a new API) to resolve UTF-8 directly, and could say that UTF-8
(nameprepped) is accepted as an alternate encoding for zone files and
is preferred where possible, that would help quite a bit to avoid forcing
protocols and operations into ACE unnecessarily.

What do you think of it?


Similarly for the DNS protocol: Send UTF-8, and if it's not found,
try again with ACE. An existing DNS server with no IDN names (in
whatever encoding) that behaves in any other way than returning
'unknown' for UTF-8 is definitely broken and has to be fixed anyway
(and I'm still really and seriously looking for somebody to give
an actual report on such a case).

I agree with you that when thinking about whether it's worth to
do a dual implementation in a DNS server, it looks like a pure
overhead, and just looking at DNS, it is. But overall and in the
long run, it's not an overhead, it's an investment. The past is
important, but the future is more important than the past.

Regards,   Martin.



From owner-idn@ops.ietf.org  Wed Jul 18 02:45:00 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA16806
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 02:44:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Mkoj-0002I3-00
	for idn-data@psg.com; Tue, 17 Jul 2001 23:28:17 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Mkoi-0002Hx-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 23:28:16 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id CAA23782;
        Wed, 18 Jul 2001 02:28:14 -0400 (EDT)
Message-Id: <200107180628.CAA23782@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Martin Duerst <duerst@w3.org>
cc: Keith Moore <moore@cs.utk.edu>, idn@ops.ietf.org
Subject: Re: Back to work (Nameprep) (was: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check)) 
In-reply-to: Your message of "Wed, 18 Jul 2001 14:10:04 +0900."
             <4.2.0.58.J.20010718120208.04004790@sh.w3.mag.keio.ac.jp> 
Date: Wed, 18 Jul 2001 02:28:13 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> >What I'd really like to see us work on is the transcribability problem.
> >This is a problem that all of the proposals have in common - there
> >are still too many similar glyphs with different code points that are not
> >folded by nameprep.  I see this as the biggest remaining problem that
> >must be solved before we can standardize an ACE lookup scheme for IDNs.
> >(even if we standardize an alternate one later that uses UTF-8 or some
> >other encoding)
> 
> Very good point. Do you have any particular kind of similarities
> in mind, or can you give some examples? 

this is well outside of my area of expertise, but several people have cited 
examples that haven't been refuted.  


> Or do you have some kind
> of principles or tests in mind that should be applied? Or any
> particular kind of procedure that we should follow?

one idea (which I don't particularly like) is to assume that all characters
within a single label are from a single langauge, and if the same glyph
maps to different code points (indicating characters from differnet languages)
then you resolve the ambiguity by using the code point that creates the
fewest number of language changes.  I won't even begin to list the problems
with this; I mention it only because I think that this approximates the
behavior that is most natural for human beings.

another idea (which I likely only slightly better) is to have two kinds
of ACE - one (using nameprep) for name-to-whaterver lookups and another 
(not using nameprep) for IDNs returned in PTR records.  That way, 
nameprep can be more agressive about folding together codepoints with
similar glyphs, because it doesn't affect names *returned* from DNS.
(unfortunately, you still have to nameprep names returned in CNAME 
records, NS records, MX records, etc.)

actually, the ability to do lookups without having to force the names
to suffer nameprep munging - in other words, the ability to do 
name comparisons without requiring that the representations be identical -
might be the most compelling reason to eventually deploy a native
IDN query interface to DNS.  

Keith 



From owner-idn@ops.ietf.org  Wed Jul 18 02:47:31 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA17289
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 02:47:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MkYu-0001X6-00
	for idn-data@psg.com; Tue, 17 Jul 2001 23:11:56 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MkYt-0001Wz-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 23:11:55 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id CAA23706;
        Wed, 18 Jul 2001 02:11:48 -0400 (EDT)
Message-Id: <200107180611.CAA23706@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Martin Duerst <duerst@w3.org>
cc: Keith Moore <moore@cs.utk.edu>, Paul Hoffman / IMC <phoffman@imc.org>,
        Patrik F??tstr ?? <paf@cisco.com>,
        Russ Rolfe <rrolfe@windows.microsoft.com>, idn@ops.ietf.org
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check) 
In-reply-to: Your message of "Wed, 18 Jul 2001 14:05:41 +0900."
             <4.2.0.58.J.20010718100321.040053e0@sh.w3.mag.keio.ac.jp> 
Date: Wed, 18 Jul 2001 02:11:48 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > > >ACE is an *encoding" just like UTF-8 is an *encoding*.
> > >
> > > Sorry, no. ACE can be reapplied to ACE (the drafts of course prohibit 
> > > this), but please try to apply UTF-8 to UTF-8.
> >
> >I fail to see how this is relevant.
> 
> Architecturally, because it's folding one layer back onto the same layer.
> Operationally, because some implementations will get it wrong, and we will
> see ACE over ACE the same way we have seen Mime over Mime.

I'm not convinced; the cases aren't even similar.  MIME was designed
to be applied recursively, so it's hardly surprising that it's
used in this way.  ACE is designed to be easily distinguished from non-ACE
forms, so it seems unlikely that implementors will accidentally re-encode
an ACE very often.  The closest thing to ACE is RFC 2047 encodings,
and I've never seen one of those recursively applied except as an example
of what not to do.  

Also, I assume that the WG will produce one or more high-quality reference 
implementations of the chosen ACE - actually I'd regard that as essential.  
So it won't often be necessary for folks to implement it from scratch.

> > > Also, ACE is used piecemeal.
> >
> >That's true.  ACE is an encoding, but is not a general purpose encoding.
> >It's designed for a narrow but important purpose, and it's sufficiently ugly
> >that you really would not want to use it except when necessary.  But there
> >are cases where it is necessary.
> 
> What I see comming more and more is that this 'narrow but important'
> argument will be applied over and over: It's not worth to do anything
> to upgrade protocol A because the DNS is ACE, then it's not worth to
> upgrade protocol B because protocol A uses ACE, and so on.

I don't know where you're seeing that argument - I haven't seen it at all.
But even if it's true to some extent, it says nothing about whether
applications will get upgraded and therefore it says nothing about 
whether users will be able to use IDNs in their applications.  They are
completely separate issues.  If anything, the appearance of ACE in
legacy appliations will drive deployment of IDN-aware versions of those
applications.

I do think that most widely-used legacy protocols will get upgraded - 
but on their own schedules, depending on the additional perceived 
utility in doing so, the perceived difficulty of doing so, and also
depending on what other demands there are that the protocol get updated.
And the last thing we want from an operational perspective is for
large numbers of protocols to get updated concurrently - producing
the maximum disruption.
 
> If for example the IDNA draft could say that resolvers should provide
> a way (a new API) to resolve UTF-8 directly, and could say that UTF-8
> (nameprepped) is accepted as an alternate encoding for zone files and
> is preferred where possible, that would help quite a bit to avoid forcing
> protocols and operations into ACE unnecessarily.
>
> What do you think of it?

Regarding the API, I've always assumed that an API to resolve UTF-8 
IDNs was essential.  As for zone files, I've already proffered a suggestion 
to have an exchange format (using ACE) distinct from the native 
format.  The native format could use UTF-8 if that were the platform's 
native charset.  But we shouldn't presume that all platforms will use 
UTF-8.  A separate UTF-8 exchange format, or a way of labelling
native format to say that it is using UTF-8, might also be a possibility.

> Similarly for the DNS protocol: Send UTF-8, and if it's not found,
> try again with ACE. 

no, that's simply not acceptable.  DNS queries are already too 
slow and too unreliable, and you've just introduced some very 
interesting failure modes.

> I agree with you that when thinking about whether it's worth to
> do a dual implementation in a DNS server, it looks like a pure
> overhead, and just looking at DNS, it is. But overall and in the
> long run, it's not an overhead, it's an investment. 

okay, but what's the return on the investment?  it appears to be 
purely psycological, since using UTF-8 on the wire in DNS doesn't 
make it any easier to upgrade either applications or protocols to 
use UTF-8 natively.    you could argue that it reduces complexity
in the long run, but the day that some benefit will be derived
for that reason is decades away.  and by then we should have
upgraded DNS (for other reasons) anyway.

Keith



From owner-idn@ops.ietf.org  Wed Jul 18 03:35:49 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA22626
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 03:35:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ml6T-0002zs-00
	for idn-data@psg.com; Tue, 17 Jul 2001 23:46:37 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15Ml6S-0002zE-00
	for idn@ops.ietf.org; Tue, 17 Jul 2001 23:46:36 -0700
Received: (qmail 26570 invoked by uid 1001); 18 Jul 2001 06:46:56 -0000
Date: 18 Jul 2001 06:46:56 -0000
Message-ID: <20010718064656.15762.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
Automatic-Legal-Notices: Copyright 2001, D. J. Bernstein. My transmission of this message to you does not constitute a copyright waiver or any other limitation of my rights, even if you have told me otherwise.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: [idn] Debunking the ACE myth
References: <5.0.2.1.2.20010717173427.02ff3330@localhost> <200107180221.WAA22344@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

The ACE myth is that we can safely start using ACE IDNs before all the
browsers, mail clients, etc. have been modified.

Here's a counterexample, elaborating on David Conrad's messages. This is
an ACE failure involving a hypothetical ACE IDN, a hypothetical ACE
browser, a real mail client under a real UTF-8 xterm, and a real MTA.

I see a mailto URL in my browser. I don't like the browser's built-in
mailer, and changing the mailto handler is inconvenient, so I simply
copy-and-paste the address into my mail client. The address looks fine.
I type the message and send it. (This is a very common situation.)

The message bounces. In contrast, it would have gone through if the
domain name owner hadn't tried to use IDNs. ``Don't use IDNs!''

What went wrong is that the browser displayed the address as Unicode
characters. The address then passed through the (CTEXT UTF-8, although
UTF8_STRING would be better) copy-and-paste mechanism, the UTF-8 xterm,
the mail client, and the 8-bit-clean MTA, none of which converted back
to ACE. The resulting UTF-8 DNS lookup produced NXDOMAIN.

You might try to help the mail go through by also providing UTF-8 IDNs.
But we've been told again and again that this doesn't work. ``What about
mail clients that reject 8-bit bytes? What about the default behavior of
UNIX gethostbyname()?'' If we do the software upgrades to make this work
then we can simply use UTF-8 without ACE.

These failures can't occur when there are no ACE applications. They also
can't occur when there are no non-ACE applications. But they can and
will occur if we deploy ACE when there are _some_ ACE applications.

As I've commented before, moving to ACE (even without the subsequent
switch to UTF-8) appears to be much more expensive than moving directly
to UTF-8. See http://cr.yp.to/proto/idn.html for details. The ACE myth
has been the only counterargument, and it simply isn't true.

---Dan



From owner-idn@ops.ietf.org  Wed Jul 18 04:23:44 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA27987
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 04:23:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Mm7p-0005yG-00
	for idn-data@psg.com; Wed, 18 Jul 2001 00:52:05 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Mm7o-0005yA-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 00:52:04 -0700
Received: from enoshima (dhcp-100-151.mag.keio.ac.jp [133.27.195.151])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id QAA13319;
	Wed, 18 Jul 2001 16:52:17 +0900 (JST)
Message-Id: <4.2.0.58.J.20010718162652.039f5620@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 18 Jul 2001 16:46:26 +0900
To: Keith Moore <moore@cs.utk.edu>
From: Martin Duerst <duerst@w3.org>
Subject: [idn] Re: Back to work (Nameprep) (was: Re: Just send UTF-8 with
  nameprep (was: RE: [idn] Reality Check)) 
Cc: Keith Moore <moore@cs.utk.edu>, idn@ops.ietf.org
In-Reply-To: <200107180628.CAA23782@astro.cs.utk.edu>
References: <Your message of "Wed, 18 Jul 2001 14:10:04 +0900." <4.2.0.58.J.20010718120208.04004790@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 02:28 01/07/18 -0400, Keith Moore wrote:
> > Or do you have some kind
> > of principles or tests in mind that should be applied? Or any
> > particular kind of procedure that we should follow?
>
>one idea (which I don't particularly like) is to assume that all characters
>within a single label are from a single langauge, and if the same glyph
>maps to different code points (indicating characters from differnet languages)
>then you resolve the ambiguity by using the code point that creates the
>fewest number of language changes.  I won't even begin to list the problems
>with this; I mention it only because I think that this approximates the
>behavior that is most natural for human beings.

I think this is worth trying, in order to get rid of the famous 'A' for
Latin, Greek, and Cyrillic. It's of course to be done on a per script
base, not per language. I wouldn't actually resolve by tweaking
codepoints (sometimes it will be very difficult to decide which
codepoint to tweak), but just by rejecting strange combinations.
You have to do a keyboard switch to get from one script to the other,
so the chance of getting a mixture accidentally isn't great.
Doing the check only on the registration side may also be a very
good idea; that may allow us to start with very tight rules and
expand them later (e.g. allow scripts separated by a hyphen,...).
It would also help a lot to address some bidirectionality problems.


>another idea (which I likely only slightly better) is to have two kinds
>of ACE - one (using nameprep) for name-to-whaterver lookups and another
>(not using nameprep) for IDNs returned in PTR records.  That way,
>nameprep can be more agressive about folding together codepoints with
>similar glyphs, because it doesn't affect names *returned* from DNS.
>(unfortunately, you still have to nameprep names returned in CNAME
>records, NS records, MX records, etc.)

Well, 'not using nameprep' for PTR records would actually mean
to use it to make sure the mapping is right, but not to put the
result into the PTR record. It may be that it's better to use
a new record type.


In terms of feasibility, the idea to check that each label only
contains letters from a single script sonds much more doable,
although there are a few special cases (languages written with
Cyrillic using some Latin letters).


Regards,    Martin.



From owner-idn@ops.ietf.org  Wed Jul 18 04:41:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA00013
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 04:41:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Mmdd-0007L1-00
	for idn-data@psg.com; Wed, 18 Jul 2001 01:24:57 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Mmdb-0007Ku-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 01:24:56 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6I8OKp12132;
	Wed, 18 Jul 2001 17:24:20 +0900 (KST)
Message-ID: <031601c10f63$a8ca6560$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Keith Moore" <moore@cs.utk.edu>, "Martin Duerst" <duerst@w3.org>
Cc: <idn@ops.ietf.org>
References: <Your message of "Wed, 18 Jul 2001 14:10:04 +0900." <4.2.0.58.J.20010718120208.04004790@sh.w3.mag.keio.ac.jp> <4.2.0.58.J.20010718162652.039f5620@sh.w3.mag.keio.ac.jp>
Subject: Re: [idn] Re: Back to work (Nameprep) (was: Re: Just send UTF-8 with  nameprep (was: RE: [idn] Reality Check)) 
Date: Wed, 18 Jul 2001 17:28:42 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,
----- Original Message -----
From: "Martin Duerst" <duerst@w3.org>
 > >one idea (which I don't particularly like) is to assume that all characters
> >within a single label are from a single langauge, and if the same glyph
> >maps to different code points (indicating characters from differnet
languages)
> >then you resolve the ambiguity by using the code point that creates the
> >fewest number of language changes.  I won't even begin to list the problems
> >with this; I mention it only because I think that this approximates the
> >behavior that is most natural for human beings.
>
> I think this is worth trying, in order to get rid of the famous 'A' for
> Latin, Greek, and Cyrillic. It's of course to be done on a per script
> base, not per language. I wouldn't actually resolve by tweaking
> codepoints (sometimes it will be very difficult to decide which
> codepoint to tweak), but just by rejecting strange combinations.
> You have to do a keyboard switch to get from one script to the other,
> so the chance of getting a mixture accidentally isn't great.
> Doing the check only on the registration side may also be a very
> good idea; that may allow us to start with very tight rules and
> expand them later (e.g. allow scripts separated by a hyphen,...).
> It would also help a lot to address some bidirectionality problems.

Good idea.

Now, let's think about another case of   all-Greek "oo.com" and all-Latin
"oo.com":
Either of the two consists of scripts from only single character sets.
But the two still look very similiar. Do you have any good idea about this ?

Regards, Soobok Lee





From owner-idn@ops.ietf.org  Wed Jul 18 05:00:43 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA02216
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 05:00:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Mmyl-0008IF-00
	for idn-data@psg.com; Wed, 18 Jul 2001 01:46:47 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Mmyk-0008I9-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 01:46:46 -0700
Received: from enoshima (dhcp-100-151.mag.keio.ac.jp [133.27.195.151])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id RAA13686;
	Wed, 18 Jul 2001 17:46:23 +0900 (JST)
Message-Id: <4.2.0.58.J.20010718173057.068a5580@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 18 Jul 2001 17:38:09 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, "Keith Moore" <moore@cs.utk.edu>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Re: Back to work (Nameprep) (was: Re: Just send
  UTF-8 with  nameprep (was: RE: [idn] Reality Check)) 
Cc: <idn@ops.ietf.org>
In-Reply-To: <031601c10f63$a8ca6560$ed1bd9d2@postel.co.kr>
References: <Your message of "Wed, 18 Jul 2001 14:10:04 +0900." <4.2.0.58.J.20010718120208.04004790@sh.w3.mag.keio.ac.jp>
 <4.2.0.58.J.20010718162652.039f5620@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 17:28 01/07/18 +0900, Soobok Lee wrote:
>Good idea.
>
>Now, let's think about another case of   all-Greek "oo.com" and all-Latin
>"oo.com":
>Either of the two consists of scripts from only single character sets.
>But the two still look very similiar. Do you have any good idea about this ?

1) Not try to do any business in Greece with this (either way),
    or in any region where Cyrillic is used (at least until IDNs
    are deployed widely enough).
2) Use an appropriate equivalent to .com for disambiguation.
3) Disallow all combinations of any of the three letters only.

Probably 1) or 2) are easier than 3).
2) will take quite some time.

Regards,   Martin.



From owner-idn@ops.ietf.org  Wed Jul 18 07:26:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA01881
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 07:26:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Mp64-000E2w-00
	for idn-data@psg.com; Wed, 18 Jul 2001 04:02:28 -0700
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Mp63-000E2q-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 04:02:27 -0700
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26785;
	Wed, 18 Jul 2001 07:01:32 -0400 (EDT)
Message-Id: <200107181101.HAA26785@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: idn@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [idn] I-D ACTION:draft-ietf-idn-nameprep-04.txt
Date: Wed, 18 Jul 2001 07:01:31 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internationalized Domain Name Working Group of the IETF.

	Title		: Preparation of Internationalized Host Names
	Author(s)	: P. Hoffman, M. Blanchet
	Filename	: draft-ietf-idn-nameprep-04.txt
	Pages		: 
	Date		: 17-Jul-01
	
This document describes how to prepare internationalized host names for
use in the DNS. The steps include:
- mapping characters to other characters, such as to change their case
- normalizing the characters
- excluding characters that are prohibited from appearing in
internationalized host names
This document does not specify a wire protocol. This preparation should
be done before the DNS request.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idn-nameprep-04.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-idn-nameprep-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-idn-nameprep-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010717133931.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idn-nameprep-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idn-nameprep-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010717133931.I-D@ietf.org>

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Wed Jul 18 12:35:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA07623
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 12:35:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MtdC-0002BA-00
	for idn-data@psg.com; Wed, 18 Jul 2001 08:52:58 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Mtd8-0002A7-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 08:52:55 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f6IFoed35851
	for <idn@ops.ietf.org>; Wed, 18 Jul 2001 11:50:44 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107181550.f6IFoed35851@nic-naa.net>
To: idn@ops.ietf.org
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check)
Date: Wed, 18 Jul 2001 11:50:40 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Recently Keith Moore wrote:

	ACE is an *encoding" just like UTF-8 is an *encoding*.

I thought about responding, but Ken wrote something last January in the
discussion of the skwan-utf8 draft that apparently needs reposting.

Eric

------- Forwarded Message

Date: Thu, 4 Jan 2001 11:14:25 -0800 (PST)
From: Kenneth Whistler <kenw@sybase.com>
Message-Id: <200101041914.LAA24879@birdie.sybase.com>
To: briansp@walid.com
Subject: Re: [idn] What's wrong with skwan-utf8?
Cc: idn@ops.ietf.org
X-Sun-Charset: US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

A terminological quibble here:

>   I guess I still don't get why some people are so focused on UTF-8.  
> UTF-8 is an 8-bit encoding of the UCS.  ACE (whatever flavor) is a 7-bit
> encoding of the UCS. 

UTF-8, UTF-16, and UTF-32 are encoding forms of Unicode (or the UCS,
if you prefer). These have a privileged status in the standard(s), and
are implemented as processing forms of the encoded characters, as
well as interchange forms. People treat UTF-8 streams as streams of
the *characters* themselves, not as cryptographic puzzles to be teased
apart by the appropriate API before the characters can be identified.

ACE, on the other hand, is one of a large class of things that are
referred to as transfer encoding syntaxes in the Unicode Character Model.
It is an explicit reshuffling of the bits to meet the bit-pattern
constraints of one or more protocols that can't handle the encoding
forms per se. Nobody is going to use ACE (or LACE or RACE or *ACE) as
a processing form of the encoded characters, nor will they use ACE
as a generic interchange form for the encoded characters, in any
but the protocols concerned with IDN.

That said, I am not advocating one or the other particularly as
an IDN solution. (I see that the ACE advocates have strong arguments
in their favor.) But you need to understand that UTF-8 and ACE are
not just morally equivalent "encodings" to understand why UTF-8
advocates would be so focussed on it.

- --Ken



------- End of Forwarded Message




From owner-idn@ops.ietf.org  Wed Jul 18 12:36:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA07834
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 12:36:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Mtvg-0003EF-00
	for idn-data@psg.com; Wed, 18 Jul 2001 09:12:04 -0700
Received: from [209.187.148.217] (helo=P2)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Mtvf-0003E6-00; Wed, 18 Jul 2001 09:12:03 -0700
Date: Wed, 18 Jul 2001 12:11:59 -0400
From: John C Klensin <klensin@jck.com>
To: Soobok Lee <lsb@postel.co.kr>
cc: idn@ops.ietf.org
Subject: Re: [idn] Re: language scripts classified
Message-ID: <6429400.995458319@localhost>
In-Reply-To: <026b01c10f2f$da789660$ed1bd9d2@postel.co.kr>
References:  <026b01c10f2f$da789660$ed1bd9d2@postel.co.kr>
X-Mailer: Mulberry/2.1.0b2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I suggest that most of your category #5 should also be moved to
#1.  Regardless of the population, these are contemporary,
spoken, languages.  Also, separating #2 from other categories
is, while factual, not useful.  Most or all of these are the
_primary_ languages of some groups: the fact that members of
those populations also speak "something else" is no more
relevant  than the fact that you speak English is to the
legitimacy of Korean.  

In addition, linguistic boundaries are, for better or worse,
different from political ones.  Both tend to shift.  If we make
decisions based on a mapping between political and linguistic
boundaries (which is what #2 implies), we will certainly find
ourselves, over time, getting it wrong.

Finally, if we really want to internationalize the system, we
had best not try to do so on the basis of population counts.
Doing so leads to forms of discrimination that are
uncomfortable, at best.  And it is not clear that the small
number of people who might want to do so is a good argument
against prohibiting naming hosts in, e.g., Runic.

    john


--On Wednesday, 18 July, 2001 11:17 +0900 Soobok Lee
<lsb@postel.co.kr> wrote:

> Some corrections.
> someone suggests that these two should be moved to #1.
> These are modern scripts used by some minorities. sorry.
> 
> Syriac: only used for for liturgical purpose 
> Unified Canadian ABoriginal Syllables:  
> 
> ----- Original Message ----- 
> From: Soobok Lee 
> To: idn@ops.ietf.org 
> Sent: Wednesday, July 18, 2001 9:28 AM
> Subject: language scripts classified
> 
> 
> While gathering  usage frequency data for many language
> scripts, I classified them into 6 categories (see enclosed ):
> 
>   Will all of these scripts  be frequently  used in IDN ?
>   At least #3 archaic scripts and #4 won't and 
>   for #1 and #2 , i am neutral yet.
>   I am working on #5.
> 
> I can find many similarities and ambiguities across these
> language scripts. Many Indian language scripts came from the
> same mother language  'Brahmi' and have  similarly-looking
> scripts and numerals .
> 
>  see http://www.omniglot.com/writing/yi.htm
> 
> 
> Soobok Lee 
> --------------------------------------------------------------
> ----------
> 
># 0  already in ML.com testbed  (I got huge usage frequency
># samples for these)
> Hebrew:
> Arabic:
> Thai:
> Hindi(Devanagari):
> Cyrillic:
> Greek:
> Hiragana:
> Katakana:
> Hangul:
> Han Ideograph:
> 
> 
># 1 few native speakers
> 
> Georgian: < 3.5 millions
> Cherokee:  100,000 (North America)
> Thaana  :  100,000 (Maldives)
> Armenian:   2 millions
> 
> 
># 2 two languages in one country:
> 
> bengali: Indian language ( > 180 millions )
> gujarati: Indian language  
> gurmukhi: Indian language
> kannada: Indian language
> malayalam: Indian language
> oriya: Indian language
> telugu: Indian language
> 
> tibetan : chinese (mainland china)   , < 5 milliions
> yi syllables: chinese (mainland china), < 5 millions
> 
> 
># 3 Archaic
> Ogham: 
> Runic:
> Gothic:
> Syriac: only used for for liturgical purpose 
> Unified Canadian ABoriginal Syllables:
> 
> 
># 4 Written only vertically
> mongolian:  (once had been abolished and restored)
> 
> 
># 5  others
> 
> sinhala : Sri lanka
> tamil : Sri lanka
> khmer : Camobodian
> lao  : Laos, Thai
> ethiopic : Ethiopia
> myanmar : Burmese
> 
> 
> 
>  





From owner-idn@ops.ietf.org  Wed Jul 18 12:36:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA07848
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 12:36:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MtrI-0002yf-00
	for idn-data@psg.com; Wed, 18 Jul 2001 09:07:32 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MtrD-0002yK-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 09:07:28 -0700
Received: from .q.j.tw ([140.115.5.16])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f6IGAi728704;
	Thu, 19 Jul 2001 00:10:45 +0800 (CST)
Message-ID: <001501c10f9b$04b060a0$1005738c@q.j.tw>
From: "tsenglm" <tsenglm@cc.ncu.edu.tw>
To: "Keith Moore" <moore@cs.utk.edu>, "Soobok Lee" <lsb@postel.co.kr>
Cc: "Keith Moore" <moore@cs.utk.edu>, "Martin Duerst" <duerst@w3.org>,
        <idn@ops.ietf.org>
References: <200107181510.LAA26526@astro.cs.utk.edu>
Subject: Re: [idn] Re: Back to work (Nameprep) (was: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check)) 
Date: Wed, 18 Jul 2001 23:04:55 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Keith Moore" <moore@cs.utk.edu>
To: "Soobok Lee" <lsb@postel.co.kr>
Cc: "Keith Moore" <moore@cs.utk.edu>; "Martin Duerst" <duerst@w3.org>;
<idn@ops.ietf.org>
Sent: Wednesday, July 18, 2001 11:10 PM
Subject: Re: [idn] Re: Back to work (Nameprep) (was: Re: Just send UTF-8
with nameprep (was: RE: [idn] Reality Check))


> > Now, let's think about another case of   all-Greek "oo.com" and
all-Latin
> > "oo.com":
> > Either of the two consists of scripts from only single character sets.
> > But the two still look very similiar. Do you have any good idea about
this ?
>
Assume there are no mixed type of language scripts  except the ASCII.
At client side , the input method environment knows what language the user
used.
To differentiate them ,   a lookup table can be  used , they can be
represented as:
      Greek(oo.com)  => unicode(oo).greek.com
      Latin(oo.com)   =>  unicode(oo).latin.com

Just like ACE is mapped to  ASCII LDH, so ACE(IDN)  need  bq--  tag for IDN
to differentiate them from traditional ascii domain-name.

Li-Ming Tseng,




From owner-idn@ops.ietf.org  Wed Jul 18 12:37:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA08200
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 12:37:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Mtf6-0002Ht-00
	for idn-data@psg.com; Wed, 18 Jul 2001 08:54:56 -0700
Received: from [209.187.148.217] (helo=P2)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Mtf5-0002Es-00; Wed, 18 Jul 2001 08:54:55 -0700
Date: Wed, 18 Jul 2001 11:54:38 -0400
From: John C Klensin <klensin@jck.com>
To: Mark Davis <mark@macchiato.com>
cc: idn@ops.ietf.org
Subject: Re: [idn] Re: Back to work (Nameprep) (was: Re: Just
 send UTF-8 with  nameprep (was: RE: [idn] Reality Check)) 
Message-ID: <5388265.995457278@localhost>
In-Reply-To: <004d01c10f9d$66dff540$0c680b41@c1340594a>
References:  <004d01c10f9d$66dff540$0c680b41@c1340594a>
X-Mailer: Mulberry/2.1.0b2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA08200

--On Wednesday, 18 July, 2001 08:22 -0700 Mark Davis
<mark@macchiato.com> wrote:

> I think the whole notion of trying to prevent cross-script
> confusions in domain names is a morass. It would invariably
> result in complicated rules that would invariably have false
> positives and negatives; it also depends greatly upon the font
> in use on the particular user's machine. We even have that
> now, with one and ell -- depending on the user's font, those
> can look identical.
> 
> Better would be to have useful GUIs that detect and signal
> possibly confusing names. For example, in the URL field of a
> browser, the spelling-check-style wavy underline could be used
> under terms like "intеl.com" vs "intel.com" (where in the
> first the "e" is the Cyrillic letter U+0435), to alert the
> user that the URL might be odd. Such tools would not get in
> the way of legitimate domain names that mix scripts or symbols.

Mark,

I think your conclusion is correct, but its implications are
quite broad.

This set of conversations has been very interesting to me, for
the unfortunate reason that it confirms the tentative, but
painful, conclusion I reached a few months ago.  Once we get
down to the really fine details of which characters match and
which do not, how to disambiguate glyphs from different scripts
that look (or are) identical, and so on, we need to rely on user
interfaces and human intelligence (or very close approximations
to the latter), rather than depending on absolute matching rules.

If we have to do that (and I agree that we will), then we almost
certainly need a non-DNS mechanism to support it.  If nothing
else, the performance costs of making multiple "maybe it is this
one" probes into the DNS to try to sort out ambiguities will
almost certainly be unacceptable (remember that DNS timeouts are
on the order of seconds and that cached negative responses
cannot have long durations).

If we _are_ going to fix the UIs to handle these cases, the
amount of work required to use a completely different mechanism
that supports human-assisted disambiguation tools (rather than
one encoding or another within the DNS) is almost certainly
quite small in comparison to other aspect of the effort required.

And, if we need a non-DNS mechanism, the current ACE versus
UTF-8 debate has the potential to turn into "look in three or
more different ways" story.   That, in turn, dramatically
increases the odds of false positives, and false positives cause
both security and sanity problems (as well as driving trademark
lawyers crazy).

    john





From owner-idn@ops.ietf.org  Wed Jul 18 12:44:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA09877
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 12:44:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Mt80-0000Of-00
	for idn-data@psg.com; Wed, 18 Jul 2001 08:20:44 -0700
Received: from femail1.sdc1.sfba.home.com ([24.0.95.81])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Mt7z-0000Na-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 08:20:43 -0700
Received: from c1340594a ([65.11.104.12]) by femail1.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20010718152036.NVSP8703.femail1.sdc1.sfba.home.com@c1340594a>;
          Wed, 18 Jul 2001 08:20:36 -0700
Message-ID: <004d01c10f9d$66dff540$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>, "Keith Moore" <moore@cs.utk.edu>,
        "Martin Duerst" <duerst@w3.org>
Cc: <idn@ops.ietf.org>
References: <Your message of "Wed, 18 Jul 2001 14:10:04 +0900." <4.2.0.58.J.20010718120208.04004790@sh.w3.mag.keio.ac.jp> <4.2.0.58.J.20010718162652.039f5620@sh.w3.mag.keio.ac.jp> <031601c10f63$a8ca6560$ed1bd9d2@postel.co.kr>
Subject: Re: [idn] Re: Back to work (Nameprep) (was: Re: Just send UTF-8 with  nameprep (was: RE: [idn] Reality Check)) 
Date: Wed, 18 Jul 2001 08:22:05 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

I think the whole notion of trying to prevent cross-script confusions in
domain names is a morass. It would invariably result in complicated rules
that would invariably have false positives and negatives; it also depends
greatly upon the font in use on the particular user's machine. We even have
that now, with one and ell -- depending on the user's font, those can look
identical.

Better would be to have useful GUIs that detect and signal possibly
confusing names. For example, in the URL field of a browser, the
spelling-check-style wavy underline could be used under terms like
"intеl.com" vs "intel.com" (where in the first the "e" is the Cyrillic
letter U+0435), to alert the user that the URL might be odd. Such tools
would not get in the way of legitimate domain names that mix scripts or
symbols.

Mark
—————

πάντων μέτρον ἄνθρωπος — Πρωταγόρας
[http://www.macchiato.com]

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Keith Moore" <moore@cs.utk.edu>; "Martin Duerst" <duerst@w3.org>
Cc: <idn@ops.ietf.org>
Sent: Wednesday, July 18, 2001 01:28
Subject: Re: [idn] Re: Back to work (Nameprep) (was: Re: Just send UTF-8
with nameprep (was: RE: [idn] Reality Check))


> Hi,
> ----- Original Message -----
> From: "Martin Duerst" <duerst@w3.org>
>  > >one idea (which I don't particularly like) is to assume that all
characters
> > >within a single label are from a single langauge, and if the same glyph
> > >maps to different code points (indicating characters from differnet
> languages)
> > >then you resolve the ambiguity by using the code point that creates the
> > >fewest number of language changes.  I won't even begin to list the
problems
> > >with this; I mention it only because I think that this approximates the
> > >behavior that is most natural for human beings.
> >
> > I think this is worth trying, in order to get rid of the famous 'A' for
> > Latin, Greek, and Cyrillic. It's of course to be done on a per script
> > base, not per language. I wouldn't actually resolve by tweaking
> > codepoints (sometimes it will be very difficult to decide which
> > codepoint to tweak), but just by rejecting strange combinations.
> > You have to do a keyboard switch to get from one script to the other,
> > so the chance of getting a mixture accidentally isn't great.
> > Doing the check only on the registration side may also be a very
> > good idea; that may allow us to start with very tight rules and
> > expand them later (e.g. allow scripts separated by a hyphen,...).
> > It would also help a lot to address some bidirectionality problems.
>
> Good idea.
>
> Now, let's think about another case of   all-Greek "oo.com" and all-Latin
> "oo.com":
> Either of the two consists of scripts from only single character sets.
> But the two still look very similiar. Do you have any good idea about this
?
>
> Regards, Soobok Lee
>
>
>
>




From owner-idn@ops.ietf.org  Wed Jul 18 12:44:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA09893
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 12:44:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MtLs-0001CL-00
	for idn-data@psg.com; Wed, 18 Jul 2001 08:35:04 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MtLr-0001CF-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 08:35:03 -0700
Received: from [24.252.219.84] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 161630; Wed, 18 Jul 2001 08:34:31 -0700
Message-ID: <3B55ACA5.C844356B@ehsco.com>
Date: Wed, 18 Jul 2001 10:35:01 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Martin Duerst <duerst@w3.org>, idn@ops.ietf.org
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check)
References: <200107180611.CAA23706@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Keith Moore wrote:

> As for zone files, I've already proffered a suggestion to have an
> exchange format (using ACE) distinct from the native format. The
> native format could use UTF-8 if that were the platform's native
> charset.  But we shouldn't presume that all platforms will use UTF-8.
> A separate UTF-8 exchange format, or a way of labelling native format
> to say that it is using UTF-8, might also be a possibility.

I think that the exchange format (master files and AXFR/IXFR) can and
should be one the last point we discuss. It doesn't need to be decided on
first, and if we debate it later we will have arguments that don't lend
themselves to an "X is preferred, so Y must suck" interpretation.

However, a couple of points.

 a) There will be some requirement for the UTF-8 namespace to
    provide manually-encoded ACE names directly. If we are
    converting UTF-8 to ACE, these fixed names are pretty easy to
    implement. Conversely, if we are doing ACE to UTF-8, then we
    have to come up with a way to prevent the ACE name from being
    converted to its UTF-8 equivalent in order for the ACE
    encoding to be preserved in the UTF-8 namespace.

 b) The exchange format applies to a specific zone. A zone which
    consists of IDNs only has to be consistent across the servers
    for that zone. If we are supporting a UTF-8 namespace for a
    particular zone, then it is okay to use UTF-8 as the default,
    since any additional servers which join the zone must be able
    to use it.

Like I said, this should probably be one of the last things we do. But
given the impact of (a) and the permission of (b), the default encoding
for zone management operations should probably be UTF-8.

> > Similarly for the DNS protocol: Send UTF-8, and if it's not found,
> > try again with ACE.
> 
> no, that's simply not acceptable.  DNS queries are already too
> slow and too unreliable, and you've just introduced some very
> interesting failure modes.

The default encoding for application functions needs to be ACE, except in
those cases where the application protocol explicitly provides in-stream
support for UTF-8 IDNs.

However, it's also important to remember that many lookups are not
dictated by application protocols (IETF or otherwise). Ping should
certainly be allowed to use the UTF-8 encoding on its command line, for
example. Hostnames in simple apps (like POP3 server) could also use UTF-8,
even though the POP3 protocol doesn't address this. It might be prudent to
simply say that "A lookups MAY default to UTF-8 if the operating
environment allows it, but the environment SHOULD explicitly indicate that
it supports this usage." We may need to encourage a usage whereby the
application can do a binding test to check the resolver.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Wed Jul 18 12:44:54 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA09911
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 12:44:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MtFU-0000o7-00
	for idn-data@psg.com; Wed, 18 Jul 2001 08:28:28 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MtFT-0000o1-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 08:28:27 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id LAA26737;
        Wed, 18 Jul 2001 11:28:24 -0400 (EDT)
Message-Id: <200107181528.LAA26737@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "D. J. Bernstein" <djb@cr.yp.to>
cc: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth 
In-reply-to: Your message of "18 Jul 2001 06:46:56 -0000."
             <20010718064656.15762.qmail@cr.yp.to> 
Date: Wed, 18 Jul 2001 11:28:24 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> The ACE myth is that we can safely start using ACE IDNs before all the
> browsers, mail clients, etc. have been modified.

I don't think anyone has claimed that it's perfectly safe to do so -
only that there's less risk of leakage of native IDNs into environments
than can only deal with ASCII if we don't *deliberately* introduce 
native IDNs into protocols that were specified to deal with ASCII names.

> Here's a counterexample, elaborating on David Conrad's messages. This is
> an ACE failure involving a hypothetical ACE IDN, a hypothetical ACE
> browser, a real mail client under a real UTF-8 xterm, and a real MTA.

Your example assumes that the browser will decode the ACE in the
mailto: URL when copying the URL to the paste buffer, when in fact it's 
much safer to leave it as ACE.  I won't claim that the browser vendor
will always do the right thing (there are plenty of counterexamples
to that idea)  but at least it is possible for them to do something 
sensible.

Keith



From owner-idn@ops.ietf.org  Wed Jul 18 12:46:21 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA10148
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 12:46:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Msxy-000PsQ-00
	for idn-data@psg.com; Wed, 18 Jul 2001 08:10:22 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Msxx-000PsH-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 08:10:21 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id LAA26526;
        Wed, 18 Jul 2001 11:10:09 -0400 (EDT)
Message-Id: <200107181510.LAA26526@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Soobok Lee" <lsb@postel.co.kr>
cc: "Keith Moore" <moore@cs.utk.edu>, "Martin Duerst" <duerst@w3.org>,
        idn@ops.ietf.org
Subject: Re: [idn] Re: Back to work (Nameprep) (was: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check)) 
In-reply-to: Your message of "Wed, 18 Jul 2001 17:28:42 +0900."
             <031601c10f63$a8ca6560$ed1bd9d2@postel.co.kr> 
Date: Wed, 18 Jul 2001 11:10:09 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Now, let's think about another case of   all-Greek "oo.com" and all-Latin
> "oo.com":
> Either of the two consists of scripts from only single character sets.
> But the two still look very similiar. Do you have any good idea about this ?

first, how likely is this in practice that a label of all Greek letters
will accidentally collide with a label of all Latin letters?   (as opposed
to a deliberate collision)

for second-level domains at least, and for some third-level domains,
it would make sense for the registry to disallow labels whose appearances
collide with all-ASCII labels.   there are already some such rules in place
even for ASCII, these would just be extended.




From owner-idn@ops.ietf.org  Wed Jul 18 13:00:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA12660
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 13:00:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MuQn-0004gs-00
	for idn-data@psg.com; Wed, 18 Jul 2001 09:44:13 -0700
Received: from femail1.sdc1.sfba.home.com ([24.0.95.81])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MuQm-0004fC-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 09:44:12 -0700
Received: from c1340594a ([65.11.104.12]) by femail1.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20010718164406.RKEW8703.femail1.sdc1.sfba.home.com@c1340594a>;
          Wed, 18 Jul 2001 09:44:06 -0700
Message-ID: <00ff01c10fa9$10c6fad0$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "John C Klensin" <klensin@jck.com>
Cc: <idn@ops.ietf.org>
References:  <004d01c10f9d$66dff540$0c680b41@c1340594a> <5388265.995457278@localhost>
Subject: Re: [idn] Re: Back to work (Nameprep) (was: Re: Justsend UTF-8 with  nameprep (was: RE: [idn] Reality Check)) 
Date: Wed, 18 Jul 2001 09:45:34 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John,

>This set of conversations has been very interesting to me, for
the unfortunate reason that it confirms the tentative, but
painful, conclusion I reached a few months ago.  Once we get
down to the really fine details of which characters match and
which do not, how to disambiguate glyphs from different scripts
that look (or are) identical, and so on, we need to rely on user
interfaces and human intelligence (or very close approximations
to the latter), rather than depending on absolute matching rules.

I agree for the most part; in that we can do the bulk of the "heavy-lifting"
in nameprep, handling case issues and obvious variants. However, for the
fine issues of mixtures of scripts and symbols, I think that at this point
we are better off not having absolute rules, but rather leaving it up to
some intelligence on the client side, assisted by the GUI.

> If we have to do that (and I agree that we will), then we almost
certainly need a non-DNS mechanism to support it.  If nothing
else, the performance costs of making multiple "maybe it is this
one" probes into the DNS to try to sort out ambiguities will
almost certainly be unacceptable (remember that DNS timeouts are
on the order of seconds and that cached negative responses
cannot have long durations).

I don't know that we need to specify the precise mechanism: after all, there
was none for "1" and "l", which may look different on your machine, but look
identical on mine right now. I agree that such intelligence should be on the
client side.

> If we _are_ going to fix the UIs to handle these cases, the
amount of work required to use a completely different mechanism
that supports human-assisted disambiguation tools (rather than
one encoding or another within the DNS) is almost certainly
quite small in comparison to other aspect of the effort required.

I agree. If we leave it up to humans to make the choice (assisted by GUI)
then probably something as simple as:

  Using http://www.unicode.org/Public/3.1-Update/Scripts-3.1.0.txt

  - find the first script that is neither COMMON nor INHERITED
  - flag any character that has a different script.

(flagging could be: different color, wavy underline, or some other
mechanism)

This should, however, be a recommendation not a requirement. More
sophisticated mechanisms could be developed in the future, either by this
body or by application vendors. For example, the consortium could develop
"confusible" mappings: sets of characters that in common fonts, at common
sizes, could be easily confused with one another. Given them, an application
could have a finer-grained GUI assist. However, the development of such
mappings would take time and effort, and continue to be refined over an
extended period.

After all,
(a) the majority of characters in different scripts are not confusible:
there is no Latin letter that looks like katakana KA.
(b) more importantly, not all confusible characters are separated by script:
especially in the area of symbols.

> And, if we need a non-DNS mechanism, the current ACE versus
UTF-8 debate has the potential to turn into "look in three or
more different ways" story.   That, in turn, dramatically
increases the odds of false positives, and false positives cause
both security and sanity problems (as well as driving trademark
lawyers crazy).

If it is impossible to register names *except those that have been
nameprepped*, then whether or not UTF-8 names go over the wire unprepped or
not should not cause much of a security problem.

    john








From owner-idn@ops.ietf.org  Wed Jul 18 14:47:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA03200
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 14:47:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MwDf-0009v3-00
	for idn-data@psg.com; Wed, 18 Jul 2001 11:38:47 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MwDe-0009tv-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 11:38:46 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA28504;
        Wed, 18 Jul 2001 14:36:05 -0400 (EDT)
Message-Id: <200107181836.OAA28504@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: John C Klensin <klensin@jck.com>
cc: Mark Davis <mark@macchiato.com>, idn@ops.ietf.org
Subject: Re: [idn] Re: Back to work (Nameprep) (was: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check)) 
In-reply-to: Your message of "Wed, 18 Jul 2001 11:54:38 EDT."
             <5388265.995457278@localhost> 
Date: Wed, 18 Jul 2001 14:36:05 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

John,

> This set of conversations has been very interesting to me, for
> the unfortunate reason that it confirms the tentative, but
> painful, conclusion I reached a few months ago.  Once we get
> down to the really fine details of which characters match and
> which do not, how to disambiguate glyphs from different scripts
> that look (or are) identical, and so on, we need to rely on user
> interfaces and human intelligence (or very close approximations
> to the latter), rather than depending on absolute matching rules.

I think this is true to a large degree.  But I think that to come
up with a practical solution to the problem will require a 
combination of not only user interfaces and human intelligence
on the client side, but also client APIs that reject ambiguous
symbol sequences, registration rules that discourage conflicts, 
nameprep-like canonicalization and folding, and perhaps even
fuzzy matching on the server side.
 
> If we have to do that (and I agree that we will),  then we almost
> certainly need a non-DNS mechanism to support it.

I agree that we can't support this with current DNS protocol 
mechanisms.  However there is so much investment and mind-share
in the DNS name space, that I don't think starting another 
name space that is similar to DNS will get very far.  And if
we're going to have DNS-like names, then we might well be better
off augmenting DNS servers (with appropriate protocol extensions
that allow them to do fuzzy matching) than to try to build a 
completely separate service.    Separate services seem far more
likely to get out of sync with each other and produce inconsistent
results.

Keith



From owner-idn@ops.ietf.org  Wed Jul 18 15:20:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA09249
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 15:20:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MwWl-000AqD-00
	for idn-data@psg.com; Wed, 18 Jul 2001 11:58:31 -0700
Received: from [209.187.148.217] (helo=P2)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MwWk-000Aq7-00; Wed, 18 Jul 2001 11:58:31 -0700
Date: Wed, 18 Jul 2001 14:58:29 -0400
From: John C Klensin <klensin@jck.com>
To: Keith Moore <moore@cs.utk.edu>
cc: idn@ops.ietf.org
Subject: Re: [idn] Re: Back to work (Nameprep) (was: Re: Just
 send UTF-8 with nameprep (was: RE: [idn] Reality Check)) 
Message-ID: <6004785.995468309@P2>
In-Reply-To: <200107181836.OAA28504@astro.cs.utk.edu>
References:  <200107181836.OAA28504@astro.cs.utk.edu>
X-Mailer: Mulberry/2.1.0b2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Wednesday, 18 July, 2001 14:36 -0400 Keith Moore
<moore@cs.utk.edu> wrote:

> John,
> 
>> This set of conversations has been very interesting to me, for
>> the unfortunate reason that it confirms the tentative, but
>> painful, conclusion I reached a few months ago.  Once we get
>> down to the really fine details of which characters match and
>>...
> I think this is true to a large degree.  But I think that to
> come up with a practical solution to the problem will require
> a  combination of not only user interfaces and human
> intelligence on the client side, but also client APIs that
> reject ambiguous symbol sequences, registration rules that
> discourage conflicts,  nameprep-like canonicalization and
> folding, and perhaps even fuzzy matching on the server side.

I believe in all of these but the last.  Perhaps it is just lack
of knowledge on my part, but I don't understand how to do fuzzy
matching in a deterministic way.  Fuzzy matching, to me, always
implies heuristics and, in a changing environment (as new names
are registered and others drop out of the DNS space), heuristics
imply that a given search string might resolve to one name and
target on one day and a different one on a different day.  That
is a property I hope to never see in the DNS.

>> If we have to do that (and I agree that we will),  then we
>> almost certainly need a non-DNS mechanism to support it.
> 
> I agree that we can't support this with current DNS protocol 
> mechanisms.  However there is so much investment and mind-share
> in the DNS name space, that I don't think starting another 
> name space that is similar to DNS will get very far.  And if
> we're going to have DNS-like names, then we might well be
> better off augmenting DNS servers (with appropriate protocol
> extensions that allow them to do fuzzy matching) than to try
> to build a  completely separate service.    Separate services
> seem far more likely to get out of sync with each other and
> produce inconsistent results.

Well, I don't know anyone who has seriously proposed a non-DNS
name space.  The most radical proposals on the table are, to my
knowledge, both my strawmen:

	* Staying within the DNS, but using a different Class to
	force application changes and create an unambiguous
	distinction between "upgraded" and "non-upgraded"
	clients.  The arguments against that include important
	"slow deployment" and "difficult transition" issues, a
	risk-free environment (even the proponents of ACE see
	some risks), but are otherwise painfully similar to the
	ACE-versus-UTF8 discussion we have seen in the last week
	or so.
	
	* Layering additional search-type facilities on top of
	the DNS, with most or all of the "internationalization"
	work being done in those additional sublayers, rather
	than relying exclusively on the DNS.

I hope it is obvious that neither of these is a "discard the
DNS, find another namespace and mechanism" approach.

And I note for the record that I haven't suggested, this week,
that the IDN WG declare success and shut down without proposing
any modifications to the DNS or the way it is used.

   john




From owner-idn@ops.ietf.org  Wed Jul 18 17:40:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA10353
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 17:40:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MydC-000Gln-00
	for idn-data@psg.com; Wed, 18 Jul 2001 14:13:18 -0700
Received: from mercury.sun.com ([192.9.25.1])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15MydC-000Glh-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 14:13:18 -0700
Received: from bebop.France.Sun.COM ([129.157.174.15])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA23323;
	Wed, 18 Jul 2001 14:13:15 -0700 (PDT)
Received: from lillen (vpn133-11.EBay.Sun.COM [129.150.133.11])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f6ILDB212748;
	Wed, 18 Jul 2001 23:13:11 +0200 (MET DST)
Date: Wed, 18 Jul 2001 23:11:29 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: RE: [idn] Reality Check
To: Russ Rolfe <rrolfe@windows.microsoft.com>
Cc: "Eric A. Hall" <ehall@ehsco.com>, Keith Moore <moore@cs.utk.edu>,
        idn@ops.ietf.org
In-Reply-To: "Your message with ID" <E15LLxX-000G18-00@psg.com>
Message-ID: <Roam.SIMC.2.0.6.995490689.16718.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


Russ,

> 2. Before the Internet became the default carrier for E-mail, many
>    companies had some internal system that allowed electron mail.
>    With these E-mail packages people could send e-mail to some=20
>    people but not to all the people they wanted.  As the internet
>    became more accesses able to companies, people began to=20
>    request the ability to send to others out side of their systems.
>    A lot of these companies had to install whole new systems in order
>    to accommodate this request.  And while doing so, a lot of us had
>    to live with two or more E-mail systems to do our work until every
>    thing was right.
> 
>    I see no difference in this analogy then what we are trying to do
>    with the introduction of an IDN standard.  With the introduction
>    of a UTF-8 based IDN, those who wish to use it will upgrade
>    to the applications and systems that can handle it.  While in
>    the process of upgrading, people may not be able to communicate=20
>    with everyone they want to via the new feature, but if it is
>    important enough, these people will use both IDN and non-IDN
>    address until every they need to communicate can, but because
>    it is important all parties will upgrade there systems ASAP.

You omit one important issue - the possibility that upgrading the software
makes it impossible (or harder) to communicate with those that haven't
upgraded.

For instance, if as part of upgrading the user ends up changing their email
address to be an IDN email address, then the user might no longer be
able to communcate with peers that don't support IDN.

One way to avoid this is to define an ACE encoding to be used in that case.
Another would be for the user to have two different email address - one
IDN and one following current email address syntax.
In the latter case the user and/or the applications need to be able to
pick which sender email address to use in a given case.

  Erik




From owner-idn@ops.ietf.org  Wed Jul 18 18:21:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA19634
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 18:21:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15MzJI-000Is8-00
	for idn-data@psg.com; Wed, 18 Jul 2001 14:56:48 -0700
Received: from mail2.microsoft.com ([131.107.3.124])
	by psg.com with smtp (Exim 3.31 #1)
	id 15MzJH-000Iqb-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 14:56:47 -0700
Received: from 157.54.9.108 by mail2.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 18 Jul 2001 14:36:38 -0700 (Pacific Daylight Time)
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-imc-05.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Wed, 18 Jul 2001 14:35:42 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Wed, 18 Jul 2001 14:35:41 -0700
Received: from win-msg-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.134]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Wed, 18 Jul 2001 14:34:38 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.5683.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [idn] Reality Check
Date: Wed, 18 Jul 2001 14:34:38 -0700
Message-ID: <8CC03F47967BF14D9710887723FADDB687E3BB@win-msg-02.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: [idn] Reality Check
Thread-Index: AcEORMlZcbZUvG1BTd2aqMoum/UCEQBjCU+w
From: "Russ Rolfe" <rrolfe@windows.microsoft.com>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, <idn@ops.ietf.org>
X-OriginalArrivalTime: 18 Jul 2001 21:34:38.0447 (UTC) FILETIME=[725E9FF0:01C10FD1]
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA19634

Patrik Fältström <paf@cisco.com> wrote:

> I am extremely worried that what I see on this list is IDNA (which 
> include nameprep) or "just send UTF-8 without nameprep".

In my example, it was an over site not to include NamePrep.  I do see the importance of this feature and believe it is import no matter what encoding we choose.

Regards, Russ
Microsoft

-----Original Message-----
From: Adam M. Costello [mailto:amc@cs.berkeley.edu] 
Sent: Monday, July 16, 2001 2:54 PM
To: idn@ops.ietf.org
Subject: Re: [idn] Reality Check


Russ Rolfe <rrolfe@windows.microsoft.com> wrote:

> I see no wrong asking users to take some of the responsibility of 
> moving to a new technology (i.e. having two addresses, adding a line 
> as part of the signature pointing to non-IDN address, requesting 
> System-Operators to upgrade)?

In other words, you'd rather create technical difficulties for users in order to ease the technical burden on engineers (by freeing them from ACE).  I'll concede that it may be possible to do so, but in my opinion it's the wrong tradeoff.  Users are far more numerous than engineers, and less able to deal with technical challenges.  I think it makes more sense to increase the technical burden on the engineers in order to make things easier for the users.

> IMHO if we go with an ACE only solution, it will never go away in the 
> long run.

If the engineers really hate ACE, they will move toward other mechanisms at every opportunity, and ACE will become less common over time.  If the engineers don't mind using ACE, then there's no problem with it remaining common forever.

In either case, I think the desire of users to see the native characters will be sufficient pressure to make ACEs very rarely visible to users. After that, users won't care whether ACE is truly gone or merely hidden.

Patrik Fältström <paf@cisco.com> wrote:

> I am extremely worried that what I see on this list is IDNA (which 
> include nameprep) or "just send UTF-8 without nameprep".

Nitpick:  The problem isn't sending non-nameprep'd UTF-8.  The problem is receiving UTF-8 and neglecting to run nameprep on it before comparing it with something.  Even with ACE, after a receiver decodes the ACE to obtain a Unicode name X, it must verify that X == nameprep(X), otherwise it's susceptible to spoofing.  But you still have a point: The ACE-decoding function is likely to have the nameprep check built in, whereas nameprep is more likely to be forgotten if UTF-8 is received. Still, I don't think we could stop new protocols from using UTF-8, and I don't think we'd even want to, so we just have to emphasize the importance of using nameprep for comparing IDNs.

AMC




From owner-idn@ops.ietf.org  Wed Jul 18 19:51:54 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA10606
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 19:51:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N0kQ-000NRd-00
	for idn-data@psg.com; Wed, 18 Jul 2001 16:28:54 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15N0kP-000NRV-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 16:28:53 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15N0kO-0005L8-00; Wed, 18 Jul 2001 16:28:52 -0700
Date: Wed, 18 Jul 2001 23:28:52 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Back to work (Nameprep)
Message-ID: <20010718232852.B19841@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200107181836.OAA28504@astro.cs.utk.edu> <00ff01c10fa9$10c6fad0$0c680b41@c1340594a> <001501c10f9b$04b060a0$1005738c@q.j.tw> <004d01c10f9d$66dff540$0c680b41@c1340594a> <4.2.0.58.J.20010718120208.04004790@sh.w3.mag.keio.ac.jp>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This message contains responses to Martin Duerst, Mark Davis, and Keith
Moore.

Martin Duerst <duerst@w3.org> wrote:

> But if [nameprep] is supposed to be strictly applied on every
> occasion, in particular every time a name is resolved, as e.g. Patrick
> is describing it, these foldings may lead to people believing that
> these characters are acceptable in a domain name the same way an
> upper-case character is.

What's wrong with actually considering them to be acceptable in the same
way as uppercase characters?

> 1) Characters that are very clearly visually distinct from the ones
>    they are mapped to. (for obvious reasons)

The reason is not obvious to me.  B and b are very clearly visually
distinct, yet we live happily in a world where both berkeley.edu and
Berkeley.EDU are commonly used, and are equivalent.

> 2) Characters that completely map to ASCII-only characters (to make
>    sure that current applications and applications doing nameprep
>    behave the same way for ASCII-only).

I don't see the problem, and you are apparently proposing to eliminate
the mapping from full-width Latin to half-width Latin, which I think
would be unfortunate.

> An example of a character for which both of the above apply is
> U+2460 CIRCLED DIGIT ONE. This is a simple digit 'one' in a circle.
> Obviously, everybody can immediately see that it's different from
> just a '1'. Also, if it's mapped to '1' by nameprep applications,
> these applications will behave differently from applications not using
> nameprep (i.e. everything out there now).

Well of course, if you try to compare names without doing nameprep, then
you will fail to see matches where you should.  Of course feeding a
non-ASCII hostname to an IDN-unaware application is asking for trouble.

If you decide to write the domain name foo1.com using a circled 1, then
obviously you are using IDN functionality and you assume the same risk
as anyone using any IDN: the risk that someone will try to paste it into
an IDN-unaware application.

Mark Davis <mark@macchiato.com> wrote:

> I think the whole notion of trying to prevent cross-script confusions
> in domain names is a morass.
>
> Better would be to have useful GUIs that detect and signal possibly
> confusing names.

I agree.  There's really no way to guarantee that the distinction
between non-equivalent names is apparent to users.  Even with a font
that distinguishes 1 from l and 0 from O, people still overlook
misspellings, even blatant ones like "whitehouse.com" instead of
"whitehouse.gov".

What nameprep can do, however, is help make sure that users are able
to type the names they have in mind.  So a user who wants to type
<omicron><omicron> can do so, and a user who wants to type oo (Latin)
can do so (regardless of whether their keyboard interface defaults to
full-width or half-width).  A user who configures their browser to
accept cookies from oo.com (Latin) will not accidentally get cookies
from the Greek look-alike.

> If it is impossible to register names *except those that have been
> nameprepped*, then whether or not UTF-8 names go over the wire
> unprepped or not should not cause much of a security problem.

Here's another way to think of it:  Whenever I use any domain name
for any purpose, I am trusting the name servers of that zone (and
all its ancestor zones) to give out true information when that name
is looked up.  With IDNs, I must now also trust those servers not to
give out bogus information in response to non-nameprep'd equivalent
representations of that name, but my exposure has not increased--I was
completely at the mercy of those servers before, and I still am.  So
as you say, allowing non-nameprep'd UTF-8 on the wire does not cause a
security problem.

Keith Moore <moore@cs.utk.edu> wrote:

> fuzzy matching on the server side.

Fuzzy matching at lookup time (as opposed to registration time) would
not help with the problem of domain name spoofing (like tricking someone
to follow a link to yah<omicron><omicron>.com).  It would help the
problem of someone seeing oo.com in print and not knowing whether
it's Latin or Greek, but that problem is much rarer, usually resolved
by context, and people can choose to register names that are not so
confusing.  I think fuzzy matching in servers would be more trouble than
it's worth.

AMC



From owner-idn@ops.ietf.org  Wed Jul 18 20:32:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA17009
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 20:32:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N1FO-000P7c-00
	for idn-data@psg.com; Wed, 18 Jul 2001 17:00:54 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15N1FO-000P7T-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 17:00:54 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15N1FN-0005Mr-00; Wed, 18 Jul 2001 17:00:53 -0700
Date: Thu, 19 Jul 2001 00:00:53 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
Message-ID: <20010719000053.C19841@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20010718064656.15762.qmail@cr.yp.to>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

"D. J. Bernstein" <djb@cr.yp.to> wrote:

> This is an ACE failure...

In your scenario you paste a UTF-8 string into an IDN-unaware
application and it doesn't work.  I don't see how this is an ACE
failure.  It has nothing to do with ACE.

> These failures can't occur when there are no ACE applications.

False.  If the application is IDN-unaware but accepts 8-bit domain
names, then it will be able to look up the UTF-8 name if and only if the
old resolver API accepts UTF-8 queries.  We can debate whether it should
or not, but that issue is orthogonal to the issue of whether ACE exists
or not.

I think we all understand that ACE can serve to bridge IDN-aware and
IDN-unaware applications only when the IDN-aware applications know
that they have to use ACE (either because they know they're talking
to an IDN-unaware peer, or because they're talking via an IDN-unaware
protocol).  When the domain names are transferred out-of-band (via
cut-and-paste, for example), then the ACE-encoding might not happen.

Users who transfer domain names out-of-band will have to learn that
feeding UTF-8 to old applications is asking for trouble, and that's
equally true whether ACE exists or not.

I think there has been enough discussion to establish who favors ACE and
who doesn't, and you have no chance of dissuading the ACE supporters.  I
suggest that your time would be better spent working on UTF-8 standards
than on trying to prevent ACE standards.

AMC



From owner-idn@ops.ietf.org  Wed Jul 18 21:15:44 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA22545
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 21:15:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N24p-0001mA-00
	for idn-data@psg.com; Wed, 18 Jul 2001 17:54:03 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15N24p-0001m4-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 17:54:03 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15N24o-0005ST-00; Wed, 18 Jul 2001 17:54:02 -0700
Date: Thu, 19 Jul 2001 00:54:02 +0000
To: idn@ops.ietf.org
Subject: [idn] Re: Just send UTF-8 with nameprep
Message-ID: <20010719005402.D19841@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B55E6CF.7A275F3@ehsco.com> <3B55ACA5.C844356B@ehsco.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

"Eric A. Hall" <ehall@ehsco.com> wrote:

>  a) There will be some requirement for the UTF-8 namespace to provide
>     manually-encoded ACE names directly.  If we are converting
>     UTF-8 to ACE, these fixed names are pretty easy to implement.
>     Conversely, if we are doing ACE to UTF-8, then we have to come up
>     with a way to prevent the ACE name from being converted to its
>     UTF-8 equivalent in order for the ACE encoding to be preserved in
>     the UTF-8 namespace.

There is only one namespace.  Every name in that single namespace has
both an ASCII representation and a UTF-8 representation (which are
identical in the case of ASCII names).  Every protocol, message format,
file format, etc. is free to require the ASCII representation or to
allow both representations.  If both representations are allowed, then
they must be treated the same by the receiver, because they are the
same name.  There is no need to tag some names as must-use-ACE.  Are
you trying to support names that really do begin with the ACE signature
prefix, so that the user sees the ACE prefix even inside IDN-aware
applications?  Such names are forbidden; they simply do not exist in the
namespace.  Trying to support them would be much more trouble than it's
worth.

> Ping should certainly be allowed to use the UTF-8 encoding on its
> command line, for example.

This is not a protocol issue, but a user-interface issue, and operating
systems have their ways of dealing with it.  For example, under UNIX,
commands should assume that their command-line arguments use the
encoding indicated LC_ALL or LANG.

> Hostnames in simple apps (like POP3 server) could also use UTF-8, even
> though the POP3 protocol doesn't address this.

I don't know what you mean by the POP3 protocol not addressing this.
The POP3 protocol exchanges a variety of commands, none of which contain
hostnames, and also exchanges RFC 822 messages, which are required to be
ASCII.  I see no way for a POP server to use UTF-8 hostnames until there
is an updated message header format and an updated Post Office Protocol
that uses it.

AMC



From owner-idn@ops.ietf.org  Wed Jul 18 21:45:30 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA29369
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 21:45:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N2Qt-0002vP-00
	for idn-data@psg.com; Wed, 18 Jul 2001 18:16:51 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15N2Qs-0002ul-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 18:16:50 -0700
Received: (qmail 19041 invoked by uid 1001); 19 Jul 2001 01:17:10 -0000
Date: 19 Jul 2001 01:17:09 -0000
Message-ID: <20010719011709.3228.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
Automatic-Legal-Notices: Copyright 2001, D. J. Bernstein. My transmission of this message to you does not constitute a copyright waiver or any other limitation of my rights, even if you have told me otherwise.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <20010718064656.15762.qmail@cr.yp.to> <20010719000053.C19841@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Adam has been telling us that UTF-8 IDNs are bad because using them may
cause failures in the short term, i.e., before the software upgrade is
complete. He's been claiming that ACE is better in the short term:

   Suppose I am considering getting an IDN for my domain. With ACE, this
   will make [some displays better, some displays worse] but nothing
   will actually break (mail will get through, web pages will load, etc)

This example shows that he's wrong. Some mail _won't_ get through if he
switches to an ACE IDN before all the software supports ACE.

Adam M. Costello writes:
> I don't see how this is an ACE failure.

You don't see that it's a failure? Or you don't see that the procedure
succeeds if the ACE IDN is replaced by a normal domain name?

Pasting an address from a browser into a mail client is a very common
operation. I do it all the time. I'll be extremely unhappy if it breaks.

> you have no chance of dissuading the ACE supporters

We'll see. I think that the ACE myth has been a big part of the ACE
advertising campaign on this mailing list. I find it interesting that
you're trying to abort the discussion of this example.

---Dan



From owner-idn@ops.ietf.org  Wed Jul 18 22:02:00 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA03316
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 22:02:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N2im-0003s4-00
	for idn-data@psg.com; Wed, 18 Jul 2001 18:35:20 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15N2il-0003ry-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 18:35:19 -0700
Received: (qmail 16582 invoked by uid 1001); 19 Jul 2001 01:35:39 -0000
Date: 19 Jul 2001 01:35:39 -0000
Message-ID: <20010719013539.9259.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
Automatic-Legal-Notices: Copyright 2001, D. J. Bernstein. My transmission of this message to you does not constitute a copyright waiver or any other limitation of my rights, even if you have told me otherwise.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: [idn] nameprep failures
References: <Your <4.2.0.58.J.20010718120208.04004790@sh.w3.mag.keio.ac.jp> <4.2.0.58.J.20010718162652.039f5620@sh.w3.mag.keio.ac.jp> <031601c10f63$a8ca6560$ed1bd9d2@postel.co.kr> <004d01c10f9d$66dff540$0c680b41@c1340594a>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Mark Davis writes:
> I think the whole notion of trying to prevent cross-script confusions in
> domain names is a morass. It would invariably result in complicated rules

I see a domain name on a business card. I type it in. I'll be unhappy if
I don't get the right name. Isn't that the whole point of nameprep?

If I see WWW.AOL.COM, where the first dot is actually U+3002, then I'm
sure I'll type it incorrectly. Isn't this why nameprep prohibits U+3002?

If I see WWW.AOL.COM, where the A is actually a capital Alpha, then I'm
sure I'll type it incorrectly. So why doesn't nameprep prohibit Alpha?

It seems safe to allow lowercase Greek alpha (and not the other alphas)
as long as users _don't_ think they can type it in uppercase. We really
should deprecate the use of uppercase characters in domain names.

---Dan



From owner-idn@ops.ietf.org  Wed Jul 18 22:13:19 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA05495
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 22:13:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N33c-0004yk-00
	for idn-data@psg.com; Wed, 18 Jul 2001 18:56:52 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15N33b-0004yX-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 18:56:51 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15N33b-0005WT-00; Wed, 18 Jul 2001 18:56:51 -0700
Date: Thu, 19 Jul 2001 01:56:51 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
Message-ID: <20010719015651.F19841@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20010719011709.3228.qmail@cr.yp.to>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

"D. J. Bernstein" <djb@cr.yp.to> wrote:

> > I don't see how this is an ACE failure.
>
> You don't see that it's a failure?  Or you don't see that the
> procedure succeeds if the ACE IDN is replaced by a normal domain name?

Of course it's a failure, but it's not an ACE failure, it's an IDN
failure.  The exact same failure would happen for any IDN in this
scenario regardless of whether ACE existed or not.

But there are other scenarios (like replying to a message, which is
even more common than cutting and pasting addresses) where ACE will not
fail, and any other encoding might (often would, given the popularity of
sendmail and BIND).

It's undeniable that ACE is more backward-compatible, and fails in fewer
instances, than any 8-bit encoding.  The only disagreement is how much
that additional backward compatibility is worth.  Some think it's worth
very little.  Others think it's worth a lot.  Fine.  Let some people
work on standards for ACE, and some people work on standards for UTF-8,
and if you're right about ACE being worthless, then the ACE standards
will get ignored.

AMC



From owner-idn@ops.ietf.org  Wed Jul 18 22:34:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA09407
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 22:34:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N3P9-0006DY-00
	for idn-data@psg.com; Wed, 18 Jul 2001 19:19:07 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15N3P8-0006DS-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 19:19:06 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15N3P8-0005Yi-00; Wed, 18 Jul 2001 19:19:06 -0700
Date: Thu, 19 Jul 2001 02:19:06 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] nameprep failures
Message-ID: <20010719021906.G19841@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20010719013539.9259.qmail@cr.yp.to>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

"D. J. Bernstein" <djb@cr.yp.to> wrote:

> I see a domain name on a business card.  I type it in.  I'll be
> unhappy if I don't get the right name.  Isn't that the whole point of
> nameprep?

In my opinion (and this is just my opinion, not an interpretation of
the nameprep spec or the IDNA spec) the point of nameprep is to make
sure that users are able to type what they intend to type, and to make
sure that names are not corrupted by transcoders.  I think the visual
ambiguity problem is too much for nameprep to solve.  What do you do
about l and 1?  What about katakana ka and the Han character for power?
What about the katakana long vowel mark and the Han character for one
(and the em dash, and the minus sign...)?  I think Mark Davis is right
that this is a morass.

> If I see WWW.AOL.COM, where the first dot is actually U+3002, then
> I'm sure I'll type it incorrectly.  Isn't this why nameprep prohibits
> U+3002?

No, the nameprep spec is explicit about the reason for prohibiting
U+3002:

    U+3002 is used as if it were U+002E in many input mechanisms,
    particularly in Asia.  This prohibition allows input mechanisms to
    safely map U+3002 to U+002E before doing nameprep without worrying
    about preventing users from accessing legitimate host name parts.

> If I see WWW.AOL.COM, where the A is actually a capital Alpha, then
> I'm sure I'll type it incorrectly.  So why doesn't nameprep prohibit
> Alpha?

[Nitpick:  I wouldn't say you typed it incorrectly, I'd say you read it
incorrectly, then typed exactly what you intended to type.]

No one is going to put <Alpha>OL.COM on a business card and seriously
expect people to read it correctly.

AMC



From owner-idn@ops.ietf.org  Wed Jul 18 22:36:07 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA09706
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 22:36:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N3IN-0005nk-00
	for idn-data@psg.com; Wed, 18 Jul 2001 19:12:07 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15N3IM-0005ne-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 19:12:07 -0700
Received: from [24.252.219.84] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 180013; Tue, 17 Jul 2001 21:11:19 -0500
Message-ID: <3B5641F4.85668B13@ehsco.com>
Date: Wed, 18 Jul 2001 21:12:04 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Adam M. Costello" <amc@cs.berkeley.edu>
CC: idn@ops.ietf.org
Subject: Re: [idn] Re: Just send UTF-8 with nameprep
References: <20010719005402.D19841@arwen.cs.berkeley.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


"Adam M. Costello" wrote:
> 
> "Eric A. Hall" <ehall@ehsco.com> wrote:
> 
> >  a) There will be some requirement for the UTF-8 namespace to provide
> >     manually-encoded ACE names directly.  If we are converting
> >     UTF-8 to ACE, these fixed names are pretty easy to implement.
> >     Conversely, if we are doing ACE to UTF-8, then we have to come up
> >     with a way to prevent the ACE name from being converted to its
> >     UTF-8 equivalent in order for the ACE encoding to be preserved in
> >     the UTF-8 namespace.
> 
> There is only one namespace.  Every name in that single namespace has
> both an ASCII representation and a UTF-8 representation (which are
> identical in the case of ASCII names).

You are correct in that there is only one DNS namespace. Using that term
was a bad idea, and as much as I complain about conflicting metaphors, I
should have known better.

> Every protocol, message format,
> file format, etc. is free to require the ASCII representation or to
> allow both representations.  If both representations are allowed, then
> they must be treated the same by the receiver, because they are the
> same name.  There is no need to tag some names as must-use-ACE.  Are
> you trying to support names that really do begin with the ACE signature
> prefix, so that the user sees the ACE prefix even inside IDN-aware
> applications?  Such names are forbidden; they simply do not exist in
> the namespace.  Trying to support them would be much more trouble than
> it's worth.

Well, since you brought it up, this is my current thinking:

Dual-mode servers would flag specific RRs as having legacy or IDN names,
or having both flags. Some legacy domain names will look like UTF-8 names
(any eight-bit binary label is legal), and so there must be a way to flag
specific entries as being either a legacy name or an IDN (or both).

Any domain name which is entered as an IDN would need to have the IDN flag
enabled, but must not have the legacy flag enabled. These IDNs must only
be used to answer IDN queries, and must not be processed through legacy
query paths, as they would likely be used to answer queries being issued
by older applications in that scenario. We must not allow UTF-8 IDNs to to
be processed by older applications, since they may be issuing queries
based on a local encoding (such as 8859-n or windows-nnnn or MacRoman or
whatever). Using these IDNs to answer legacy queries will absolutely
definitely cause some kind of unintended consequence, and we will get a
lot of heat for the failure.

ACE domain names which are automatically created from the UTF-8 names
should only have the legacy flag enabled, to prevent bleed-over in the
opposite direction. It is also feasible to allow these entries to exist
with both flags, but see below.

It should also be possible to have an ACE name with both flags by allowing
users to enter it manually, although this should be cautioned against (but
not prohibited). We don't want applications that always re-apply ACE to an
IDN to do that, but moreover we don't want to make it common or simple to
make that mistake (although in truth, it might be more effective to let
people shoot themselves in the feet to really drive this message home).

For things like Dynamic DNS, this mechanism is actually pretty simple:
what message format was used for the registered name? Legacy names get the
legacy flag, while IDNs get the IDN flag (while the ACE conversions get
the legacy flag). For human operators, it is less clear. Perhaps one
product will allow users to specify the datatype on entry, while another
will simply store all names as IDNs and automatically create a legacy
version of the zone whenever the IDN zone is [re]loaded (with the caveat
that such a mechanism will break any non-IDN eight-bit labels). UI stuff
is probably outside of the scope, but some discussion would be fruitful as
it would likely result in a better management method than the one
presented here.

It would be a lot simpler to simply declare non-ASCII labels as IDNs, but
I don't think this is feasible. Perhaps it is?

> > Ping should certainly be allowed to use the UTF-8 encoding on its
> > command line, for example.
> 
> This is not a protocol issue, but a user-interface issue, and operating
> systems have their ways of dealing with it.  For example, under UNIX,
> commands should assume that their command-line arguments use the
> encoding indicated LC_ALL or LANG.

Good approach.

> > Hostnames in simple apps (like POP3 server) could also use UTF-8,
> > even  though the POP3 protocol doesn't address this.
> 
> I don't know what you mean by the POP3 protocol not addressing this.

*hostnames* for POP3 servers are not specifed by the protocol. You have to
tell your POP3 mailer where it should go to pickup mail; that hostname is
what I'm referring to.

Also, from the quoted message:

 | It might be prudent to simply say that "A lookups MAY default to
 | UTF-8 if the operating environment allows it, but the environment
 | SHOULD explicitly indicate that it supports this usage."

This should be the general rule for all lookups (not just A RRs). In the
case of application-specific queries, the application must be sure to only
use domain names which are legal for that application. IOW, if an
application is presented with an IDN but the protocol specifications do
not allow for the use of IDNs, then the application should down-convert
the IDN and use that (or return an error, or whatever is appropriate).

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Wed Jul 18 22:44:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA12215
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 22:44:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N3Sr-0006Qq-00
	for idn-data@psg.com; Wed, 18 Jul 2001 19:22:57 -0700
Received: from heron.verisign.com ([216.168.233.95])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15N3Sq-0006Nz-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 19:22:57 -0700
Received: from VSVAPOSTALGW1.prod.netsol.com (vsvapostalgw1.prod.netsol.com [216.168.234.201])
	by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id WAA12233
	for <idn@ops.ietf.org>; Wed, 18 Jul 2001 22:22:25 -0400 (EDT)
Received: by VSVAPOSTALGW1.prod.netsol.com with Internet Mail Service (5.5.2653.19)
	id <NP41ZT4F>; Wed, 18 Jul 2001 22:22:53 -0400
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD66DF814@vsvapostal3.prod.netsol.com>
From: "Colosi, John" <jcolosi@verisign.com>
To: idn@ops.ietf.org
Subject: RE: [idn] Debunking the ACE myth
Date: Wed, 18 Jul 2001 22:17:27 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dan,

	I don't think you addressed Adam's specific assertion that ACE is
not involved in the problem.  I believe his point is that your operating
system will probably use utf-8 on the clipboard to transport the Unicode
data from the browser to the e-mail client.  ACE doesn't seem involved in
the client's failure to send the e-mail.  Can you address his point
specifically?

	In fact, I think ACE is at least responsible for giving the illusion
that the e-mail might succeed.  The behavior of the browser might also be at
fault.  By using only Unicode characters in the mailto address, the browser
has displayed these characters in an unusable form.  Maybe the browser
should elect to display the ACE characters along with the Unicode,
indicating to users that the strings are identical in some context.  This
would allow you to easily cut & paste the address.

	I think you could make an interesting argument here and I'd like to
see it.  The "ACE Myth" conspiracy theory stuff is not very constructive.

-- John

-----Original Message-----
From: D. J. Bernstein [mailto:djb@cr.yp.to]
Sent: Wednesday, July 18, 2001 9:17 PM
To: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth


Adam has been telling us that UTF-8 IDNs are bad because using them may
cause failures in the short term, i.e., before the software upgrade is
complete. He's been claiming that ACE is better in the short term:

   Suppose I am considering getting an IDN for my domain. With ACE, this
   will make [some displays better, some displays worse] but nothing
   will actually break (mail will get through, web pages will load, etc)

This example shows that he's wrong. Some mail _won't_ get through if he
switches to an ACE IDN before all the software supports ACE.

Adam M. Costello writes:
> I don't see how this is an ACE failure.

You don't see that it's a failure? Or you don't see that the procedure
succeeds if the ACE IDN is replaced by a normal domain name?

Pasting an address from a browser into a mail client is a very common
operation. I do it all the time. I'll be extremely unhappy if it breaks.

> you have no chance of dissuading the ACE supporters

We'll see. I think that the ACE myth has been a big part of the ACE
advertising campaign on this mailing list. I find it interesting that
you're trying to abort the discussion of this example.

---Dan



From owner-idn@ops.ietf.org  Wed Jul 18 23:00:02 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA15426
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 23:00:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N3ne-0007ed-00
	for idn-data@psg.com; Wed, 18 Jul 2001 19:44:26 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15N3nc-0007eX-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 19:44:25 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6J2i5p16335;
	Thu, 19 Jul 2001 11:44:06 +0900 (KST)
Message-ID: <00a401c10ffd$2d19e9a0$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "Adam M. Costello" <amc@cs.berkeley.edu>
References: <20010719021906.G19841@arwen.cs.berkeley.edu>
Subject: Re: [idn] nameprep failures
Date: Thu, 19 Jul 2001 11:47:38 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message ----- 
From: "Adam M. Costello" <amc@cs.berkeley.edu>
To: <idn@ops.ietf.org>
Sent: Thursday, July 19, 2001 11:19 AM
Subject: Re: [idn] nameprep failures


 > 
> > If I see WWW.AOL.COM, where the A is actually a capital Alpha, then
> > I'm sure I'll type it incorrectly.  So why doesn't nameprep prohibit
> > Alpha?
> 
> [Nitpick:  I wouldn't say you typed it incorrectly, I'd say you read it
> incorrectly, then typed exactly what you intended to type.]
> 
> No one is going to put <Alpha>OL.COM on a business card and seriously
> expect people to read it correctly.
> 

At least, a cheater or a fraud would deliberately try  it.


> AMC
> 




From owner-idn@ops.ietf.org  Wed Jul 18 23:55:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA26920
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 23:55:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N4Yz-000ACj-00
	for idn-data@psg.com; Wed, 18 Jul 2001 20:33:21 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15N4Yy-000ACd-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 20:33:20 -0700
Received: (qmail 14035 invoked by uid 1001); 19 Jul 2001 03:33:41 -0000
Date: 19 Jul 2001 03:33:41 -0000
Message-ID: <20010719033341.31782.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
Automatic-Legal-Notices: Copyright 2001, D. J. Bernstein. My transmission of this message to you does not constitute a copyright waiver or any other limitation of my rights, even if you have told me otherwise.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <20010719011709.3228.qmail@cr.yp.to> <20010719015651.F19841@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Adam M. Costello writes:
> The exact same failure would happen for any IDN in this scenario

Right! That's the whole point. IDNs, including ACE IDNs, aren't safe to
deploy until the software upgrade is complete.

The ACE myth is that ACE IDNs are safe. In fact, people who try using
ACE IDNs in the short term will encounter failures. You keep complaining
about this aspect of UTF-8 IDNs; but it's true for ACE IDNs too.

(By the way, all the programs I have in mind already handle UTF-8 IDNs.
But I agree that there are other programs that need upgrades.)

> It's undeniable that ACE is more backward-compatible, and fails in fewer
> instances, than any 8-bit encoding.

Actually, that claim requires a careful analysis.

What you're neglecting to take into account is that ACE is substantially
more expensive to deploy than UTF-8. See http://cr.yp.to/proto/idn.html.
ACE requires many more programs to be changed.

I agree that short-term deployment of ACE IDNs would break _fewer_
existing procedures than short-term deployment of UTF-8 IDNs. But those
procedures will be broken for _longer_ with ACE.

You were claiming before that ACE wouldn't cause any failures. ``Nothing
will actually break,'' you said. So you could ignore the question of how
long the ACE upgrade would take; zero times anything is zero. However,
without the ACE myth, the analysis is substantially more difficult.

---Dan



From owner-idn@ops.ietf.org  Wed Jul 18 23:57:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA27526
	for <idn-archive@lists.ietf.org>; Wed, 18 Jul 2001 23:57:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N4hq-000Aje-00
	for idn-data@psg.com; Wed, 18 Jul 2001 20:42:30 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15N4hq-000AjY-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 20:42:30 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15N4hp-0005gE-00; Wed, 18 Jul 2001 20:42:29 -0700
Date: Thu, 19 Jul 2001 03:42:29 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Re: Just send UTF-8 with nameprep
Message-ID: <20010719034229.K19841@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B5641F4.85668B13@ehsco.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

"Eric A. Hall" <ehall@ehsco.com> wrote:

> Dual-mode servers would flag specific RRs as having legacy or IDN
> names, or having both flags. Some legacy domain names will look like
> UTF-8 names (any eight-bit binary label is legal), and so there must
> be a way to flag specific entries as being either a legacy name or an
> IDN (or both).

Okay, now I see what you meant by multiple namespaces.  On the one hand,
there's the world of ASCII names and IDNs.  On the other hand, there are
things that are neither:  8-bit names that predate any IDN standard.
Let's call such things "freaks".  :)

First, I question whether there really are any such names, and if there
are, whether we should care if we break them.

But assuming for the moment that we want to support these freak names,
we only need one flag, the freak flag.  An old-style DNS query can match
ASCII names (including ACEs) and freaks, but not IDNs.  A UTF-8 EDNS
query can match IDNs and ASCII names (including ACEs), but not freaks.
(I suppose you could also define another EDNS query for freaks, if you
wanted everything to be accessible via EDNS.)

There is no need for a second flag.  If a label contains only LDH
characters and conforms to ACE syntax, then it *is* an ACE, regardless
of whether it was obtained via an ASCII transport or a UTF-8 transport
or whatever.  There are no labels whose native (Unicode) form conforms
to ACE syntax.  To allow that would just confuse people.

> *hostnames* for POP3 servers are not specifed by the protocol. You
> have to tell your POP3 mailer where it should go to pickup mail; that
> hostname is what I'm referring to.

Okay, then this is a user-interface issue just like the ping example.

> This should be the general rule for all lookups (not just A RRs).  In
> the case of application-specific queries, the application must be
> sure to only use domain names which are legal for that application.
> IOW, if an application is presented with an IDN but the protocol
> specifications do not allow for the use of IDNs, then the application
> should down-convert the IDN and use that (or return an error, or
> whatever is appropriate).

I'm not sure what you mean here.  Let's take POP3 for example.  The
protocol doesn't allow for the use of IDNs, but that's unrelated to
the question of whether a POP3 client can connect to a server named by
an IDN.  If the client is IDN-aware, and has a UTF-8 resolver at its
disposal, there's no reason it shouldn't accept a UTF-8 server name from
the user and look it up.

AMC



From owner-idn@ops.ietf.org  Thu Jul 19 00:31:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA04806
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 00:31:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N5Cd-000CVB-00
	for idn-data@psg.com; Wed, 18 Jul 2001 21:14:19 -0700
Received: from mail.fm-net.ne.jp ([211.15.66.133])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15N5Cc-000CV5-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 21:14:18 -0700
Received: from bruce (bruce.fm-net.ne.jp [211.15.66.163])
	by mail.fm-net.ne.jp (8.9.3/8.8.7) with SMTP id NAA25316
	for <idn@ops.ietf.org>; Thu, 19 Jul 2001 13:14:16 +0900
Message-ID: <02e401c11009$0e734530$a3420fd3@bruce>
From: "Bruce Thomson" <bthomson@fm-net.ne.jp>
To: <idn@ops.ietf.org>
References: <20010719021906.G19841@arwen.cs.berkeley.edu>
Subject: Re: [idn] nameprep failures
Date: Thu, 19 Jul 2001 13:12:42 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

These kind of visual ambiguities can only be resolved by
knowing the language. It's not likely that a business card
recipient will be able to type an IDN properly if the
script is exotic for him. He needs a second romanized
domain name to use.

On the other hand, one of the main good things about
nameprep is that it prohibits "bad" names at registration
time, preventing the unscrupulous from making scam sites
similar to legitimate ones. But with the abundance of
supported scripts, mixing and matching weird characters
will allow registration of things that we would prefer not
to have registered with the potential of confusion.

Unfortunately, the only way to stop this is to further
burden nameprep with rules that disallow scripts in
bizarre combinations. Is this worth it? I don't know
but I would be interested in hearing what people think.

Bruce


----- Original Message ----- 
From: "Adam M. Costello" <amc@cs.berkeley.edu>
To: <idn@ops.ietf.org>
Sent: Thursday, July 19, 2001 11:19 AM
Subject: Re: [idn] nameprep failures


> "D. J. Bernstein" <djb@cr.yp.to> wrote:
> 
> > I see a domain name on a business card.  I type it in.  I'll be
> > unhappy if I don't get the right name.  Isn't that the whole point of
> > nameprep?
> 
> In my opinion (and this is just my opinion, not an interpretation of
> the nameprep spec or the IDNA spec) the point of nameprep is to make
> sure that users are able to type what they intend to type, and to make
> sure that names are not corrupted by transcoders.  I think the visual
> ambiguity problem is too much for nameprep to solve.  What do you do
> about l and 1?  What about katakana ka and the Han character for power?
> What about the katakana long vowel mark and the Han character for one
> (and the em dash, and the minus sign...)?  I think Mark Davis is right
> that this is a morass.
> 
> > If I see WWW.AOL.COM, where the first dot is actually U+3002, then
> > I'm sure I'll type it incorrectly.  Isn't this why nameprep prohibits
> > U+3002?
> 
> No, the nameprep spec is explicit about the reason for prohibiting
> U+3002:
> 
>     U+3002 is used as if it were U+002E in many input mechanisms,
>     particularly in Asia.  This prohibition allows input mechanisms to
>     safely map U+3002 to U+002E before doing nameprep without worrying
>     about preventing users from accessing legitimate host name parts.
> 
> > If I see WWW.AOL.COM, where the A is actually a capital Alpha, then
> > I'm sure I'll type it incorrectly.  So why doesn't nameprep prohibit
> > Alpha?
> 
> [Nitpick:  I wouldn't say you typed it incorrectly, I'd say you read it
> incorrectly, then typed exactly what you intended to type.]
> 
> No one is going to put <Alpha>OL.COM on a business card and seriously
> expect people to read it correctly.
> 
> AMC
> 
> 




From owner-idn@ops.ietf.org  Thu Jul 19 00:42:02 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA06503
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 00:42:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N5L4-000CwD-00
	for idn-data@psg.com; Wed, 18 Jul 2001 21:23:02 -0700
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15N5Kr-000Ct2-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 21:22:49 -0700
Received: from deng ([159.226.7.68]) by whale.cnnic.net.cn
          (Netscape Messaging Server 4.15) with SMTP id GGPDKX00.627; Thu,
          19 Jul 2001 12:24:33 +0800 
Message-ID: <002701c11009$5788fcb0$4407e29f@deng>
From: "xiang deng" <deng@cnnic.net.cn>
To: <internet-drafts@ietf.org>, <idn@ops.ietf.org>
Cc: <Marc.Blanchet@viagenie.qc.ca>, <James@Seng.cc>
Subject: [idn] draft-ietf-idn-icdns-00.txt
Date: Thu, 19 Jul 2001 12:14:45 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0023_01C1104C.6590C570"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0023_01C1104C.6590C570
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0024_01C1104C.6590C570"


------=_NextPart_001_0024_01C1104C.6590C570
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

SW50ZXJuZXQgRHJhZnQgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgQXV0aG9y
czogWGlhbmcgRGVuZw0KPGRyYWZ0LWlldGYtaWRuLWljZG4tMDAudHh0PiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgWWFuIEZhbmcgV2FuZyAgICAgICANCkp1bHkgLCAyMDAxICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KRXhwaXJlcyBp
biBzaXggbW9udGhzICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICANCiAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgDQogICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAN
CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgDQogICAgICAgVGhlIEltcGxlbWVudGF0aW9uIG9mIENoaW5lc2UgY2hhcmFjdGVyIGlu
IElETg0KDQpTdGF0dXMgb2YgdGhpcyBNZW1vDQoNClRoaXMgZG9jdW1lbnQgaXMgYW4gSW50ZXJu
ZXQtRHJhZnQgYW5kIGlzIGluIGZ1bGwgY29uZm9ybWFuY2Ugd2l0aCBhbGwgDQpwcm92aXNpb25z
IG9mIFNlY3Rpb24gMTAgb2YgUkZDMjAyNi4NCg0KSW50ZXJuZXQtRHJhZnRzIGFyZSB3b3JraW5n
IGRvY3VtZW50cyBvZiB0aGUgSW50ZXJuZXQgRW5naW5lZXJpbmcgVGFzayANCkZvcmNlIChJRVRG
KSwgaXRzIGFyZWFzLCBhbmQgaXRzIHdvcmtpbmcgZ3JvdXBzLiBOb3RlIHRoYXQgb3RoZXIgZ3Jv
dXBzIA0KbWF5IGFsc28gZGlzdHJpYnV0ZSB3b3JraW5nIGRvY3VtZW50cyBhcyBJbnRlcm5ldC1E
cmFmdHMuDQoNCkludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRzIHZhbGlkIGZvciBh
IG1heGltdW0gb2Ygc2l4IG1vbnRocyANCmFuZCBtYXkgYmUgdXBkYXRlZCwgcmVwbGFjZWQsIG9y
IG9ic29sZXRlZCBieSBvdGhlciBkb2N1bWVudHMgYXQgYW55IA0KdGltZS4gSXQgaXMgaW5hcHBy
b3ByaWF0ZSB0byB1c2UgSW50ZXJuZXQtRHJhZnRzIGFzIHJlZmVyZW5jZSBtYXRlcmlhbCANCm9y
IHRvIGNpdGUgdGhlbSBvdGhlciB0aGFuIGFzICJ3b3JrIGluIHByb2dyZXNzLiINCg0KICAgIFRo
ZSBsaXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtRHJhZnRzIGNhbiBiZSBhY2Nlc3NlZCBhdA0KICAg
IGh0dHA6Ly93d3cuaWV0Zi5vcmcvaWV0Zi8xaWQtYWJzdHJhY3RzLnR4dA0KDQogICAgVGhlIGxp
c3Qgb2YgSW50ZXJuZXQtRHJhZnQgU2hhZG93IERpcmVjdG9yaWVzIGNhbiBiZSBhY2Nlc3NlZCBh
dA0KICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvc2hhZG93Lmh0bWwNCg0KVGVybWlub2xvZ3kNCg0K
VGhlIGtleSB3b3JkcyAiTVVTVCIsICJTSEFMTCIsICJSRVFVSVJFRCIsICJTSE9VTEQiLCAiUkVD
T01NRU5ERUQiLCBhbmQNCiJNQVkiIGluIHRoaXMgZG9jdW1lbnQgYXJlIHRvIGJlIGludGVycHJl
dGVkIGFzIGRlc2NyaWJlZCBpbiBSRkMgMjExOQ0KW1JGQzIxMTldLg0KDQpBYnN0cmFjdA0KDQpU
aGlzIGRvY3VtZW50IG1haW5seSB0YWxrcyBhYm91dCBDaGluZXNlIGNoYXJhY3RlcnMgYW5kIHR3
byBwcm9wb3NlZCANCnNjaGVtZXMgb2YgaW1wbGVtZW50aW9uIGJhc2VkIG9uIFtJRE5SRVFdIGFu
ZCBbTkFNRVBSRVBdLHRob3VnaCANCnRoZXJlIGFyZSBzb21lIGRpZmZlcmVuY2VzIGFtb25nIHRo
ZW0uVGhlIGRpc3RpbmN0aW9uIGJldHdlZW4gdGhlc2UgdHdvIHNjaGVtZXMgDQppcyB0aGUgcG9z
aXRpb24gb2YgdGhlIGltcGxlbWVudGF0aW9uIGZ1bmN0aW9uOg0KICAgIC0tIGNsaWVudCBzaWRl
IHByb2Nlc3NpbmcgDQpvciANCiAgICAtLSBzZXJ2ZXIgc2lkZSBwcm9jZXNzaW5nDQoNCkluIENo
aW5hLCB0aGUgbW9zdCBwb3B1bGFyIGNoYXJhY3RlciBzZXQgYXJlIFtHQktdLFtCSUc1XSxbR0Ix
ODAzMF0sd2hpbGUNCmluIHRoaXMgZG9jdW1lbnQsYWxsIGV4YW1wbGVzIGFyZSBiYXNlZCBvbiBb
VUNTXS4NCg0K

------=_NextPart_001_0024_01C1104C.6590C570
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi
MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w
MC4yOTIwLjAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9E
WSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPkludGVybmV0IA0KRHJhZnQmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgDQpBdXRob3JzOiBYaWFuZyANCkRlbmc8QlI+
Jmx0O2RyYWZ0LWlldGYtaWRuLWljZG4tMDAudHh0Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyANCllhbiBG
YW5nIFdhbmcmbmJzcDsmbmJzcDsgJm5ic3A7Jm5ic3A7Jm5ic3A7IDxCUj5KdWx5ICwgDQoyMDAx
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IA0KPEJSPkV4cGlyZXMgaW4gc2l4IA0KbW9udGhzJm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7PEJSPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxCUj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDs8QlI+Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7PEJSPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxCUj4mbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgDQpUaGUgSW1wbGVtZW50YXRpb24gb2YgQ2hpbmVzZSBj
aGFyYWN0ZXIgaW4gSUROPC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5TdGF0dXMgb2Yg
dGhpcyBNZW1vPC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5UaGlzIGRvY3VtZW50IGlz
IGFuIEludGVybmV0LURyYWZ0IGFuZCBpcyBpbiBmdWxsIGNvbmZvcm1hbmNlIHdpdGggYWxsIA0K
PEJSPnByb3Zpc2lvbnMgb2YgU2VjdGlvbiAxMCBvZiBSRkMyMDI2LjwvRElWPg0KPERJVj4mbmJz
cDs8L0RJVj4NCjxESVY+SW50ZXJuZXQtRHJhZnRzIGFyZSB3b3JraW5nIGRvY3VtZW50cyBvZiB0
aGUgSW50ZXJuZXQgRW5naW5lZXJpbmcgVGFzayANCjxCUj5Gb3JjZSAoSUVURiksIGl0cyBhcmVh
cywgYW5kIGl0cyB3b3JraW5nIGdyb3Vwcy4gTm90ZSB0aGF0IG90aGVyIGdyb3VwcyANCjxCUj5t
YXkgYWxzbyBkaXN0cmlidXRlIHdvcmtpbmcgZG9jdW1lbnRzIGFzIEludGVybmV0LURyYWZ0cy48
L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPkludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQg
ZG9jdW1lbnRzIHZhbGlkIGZvciBhIG1heGltdW0gb2Ygc2l4IG1vbnRocyANCjxCUj5hbmQgbWF5
IGJlIHVwZGF0ZWQsIHJlcGxhY2VkLCBvciBvYnNvbGV0ZWQgYnkgb3RoZXIgZG9jdW1lbnRzIGF0
IGFueSANCjxCUj50aW1lLiBJdCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFm
dHMgYXMgcmVmZXJlbmNlIG1hdGVyaWFsIA0KPEJSPm9yIHRvIGNpdGUgdGhlbSBvdGhlciB0aGFu
IGFzICJ3b3JrIGluIHByb2dyZXNzLiI8L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPiZu
YnNwOyZuYnNwOyZuYnNwOyBUaGUgbGlzdCBvZiBjdXJyZW50IEludGVybmV0LURyYWZ0cyBjYW4g
YmUgYWNjZXNzZWQgDQphdDxCUj4mbmJzcDsmbmJzcDsmbmJzcDsgPEEgDQpocmVmPSJodHRwOi8v
d3d3LmlldGYub3JnL2lldGYvMWlkLWFic3RyYWN0cy50eHQiPmh0dHA6Ly93d3cuaWV0Zi5vcmcv
aWV0Zi8xaWQtYWJzdHJhY3RzLnR4dDwvQT48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElW
PiZuYnNwOyZuYnNwOyZuYnNwOyBUaGUgbGlzdCBvZiBJbnRlcm5ldC1EcmFmdCBTaGFkb3cgRGly
ZWN0b3JpZXMgY2FuIGJlIA0KYWNjZXNzZWQgYXQ8QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxBIA0K
aHJlZj0iaHR0cDovL3d3dy5pZXRmLm9yZy9zaGFkb3cuaHRtbCI+aHR0cDovL3d3dy5pZXRmLm9y
Zy9zaGFkb3cuaHRtbDwvQT48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPlRlcm1pbm9s
b2d5PC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5UaGUga2V5IHdvcmRzICJNVVNUIiwg
IlNIQUxMIiwgIlJFUVVJUkVEIiwgIlNIT1VMRCIsICJSRUNPTU1FTkRFRCIsIA0KYW5kPEJSPiJN
QVkiIGluIHRoaXMgZG9jdW1lbnQgYXJlIHRvIGJlIGludGVycHJldGVkIGFzIGRlc2NyaWJlZCBp
biBSRkMgDQoyMTE5PEJSPltSRkMyMTE5XS48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElW
PkFic3RyYWN0PC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5UaGlzIGRvY3VtZW50IG1h
aW5seSB0YWxrcyBhYm91dCBDaGluZXNlIGNoYXJhY3RlcnMgYW5kIHR3byBwcm9wb3NlZCANCjxC
Uj5zY2hlbWVzIG9mIGltcGxlbWVudGlvbiBiYXNlZCBvbiBbSUROUkVRXSBhbmQgW05BTUVQUkVQ
XSx0aG91Z2ggPEJSPnRoZXJlIA0KYXJlIHNvbWUgZGlmZmVyZW5jZXMgYW1vbmcgdGhlbS5UaGUg
ZGlzdGluY3Rpb24gYmV0d2VlbiB0aGVzZSB0d28gc2NoZW1lcyA8QlI+aXMgDQp0aGUgcG9zaXRp
b24gb2YgdGhlIGltcGxlbWVudGF0aW9uIGZ1bmN0aW9uOjxCUj4mbmJzcDsmbmJzcDsmbmJzcDsg
LS0gY2xpZW50IA0Kc2lkZSBwcm9jZXNzaW5nIDxCUj5vciA8QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7
IC0tIHNlcnZlciBzaWRlIHByb2Nlc3Npbmc8L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElW
PkluIENoaW5hLCB0aGUgbW9zdCBwb3B1bGFyIGNoYXJhY3RlciBzZXQgYXJlIA0KW0dCS10sW0JJ
RzVdLFtHQjE4MDMwXSx3aGlsZTxCUj5pbiB0aGlzIGRvY3VtZW50LGFsbCBleGFtcGxlcyBhcmUg
YmFzZWQgb24gDQpbVUNTXS48QlI+PC9ESVY+PC9CT0RZPjwvSFRNTD4NCg==

------=_NextPart_001_0024_01C1104C.6590C570--

------=_NextPart_000_0023_01C1104C.6590C570
Content-Type: text/plain;
	name="draft-ietf-idn-icdns-00.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="draft-ietf-idn-icdns-00.txt"
Content-Transfer-Encoding: quoted-printable

Internet Draft                                     Authors: Xiang Deng
<draft-ietf-idn-icdn-00.txt>                                Yan Fang =
Wang   		 =20
July , 2001                                                   =20
Expires in six months		                                  =20
                                                          =20
                                                          =20
                                                          =20
                                                             =20
       The Implementation of Chinese character in IDN

Status of this Memo

This document is an Internet-Draft and is in full conformance with all=20
provisions of Section 10 of RFC2026.

Internet-Drafts are working documents of the Internet Engineering Task=20
Force (IETF), its areas, and its working groups. Note that other groups=20
may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months=20
and may be updated, replaced, or obsoleted by other documents at any=20
time. It is inappropriate to use Internet-Drafts as reference material=20
or to cite them other than as "work in progress."

    The list of current Internet-Drafts can be accessed at
    http://www.ietf.org/ietf/1id-abstracts.txt

    The list of Internet-Draft Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html

Terminology

The key words "MUST", "SHALL", "REQUIRED", "SHOULD", "RECOMMENDED", and
"MAY" in this document are to be interpreted as described in RFC 2119
[RFC2119].

Abstract

This document mainly talks about Chinese characters and two proposed=20
schemes of implemention based on [IDNREQ] and [NAMEPREP],though=20
there are some differences among them.The distinction between these two =
schemes=20
is the position of the implementation function:
    -- client side processing=20
or=20
    -- server side processing

In China, the most popular character set are =
[GBK],[BIG5],[GB18030],while
in this document,all examples are based on [UCS].


1.  Charateristics of Chinese characters and Chinese languange
1.1 The context dependent semantics of Chinese characters=20
    In [UCS],each Chinese character is a codepoint,which is composed of =
two
    bytes.
   =20
    Chinese character can be classified as two groups. In one group,each
    character does its own meaning(notional character) while that of the
    other group has not(empty characters). Both notional characters and
    empty characters can be made words by combining with other=20
    character(s),even sentences. the notional character=20
    is the basic unit of Chinese language which has meaning similar to =
phonems.
   =20
1.2 A Chinese characters may have several writing forms.
   =20
    Chinese characters were continuously evolved and widely spread =
during
    5,000-year-long Chinese history. They were also largely introduced=20
    into other countries and became a major component of their =
languages.
    Therefore, it is inevitably for a Chinese character has many other
    writing forms. In Unicode encoding standards, the criterion for
    distributing codepoint is the shape of character. So the different=20
    glyph of the same Chinese character have several different=20
    codepoint according to the international encoding standard.
   =20
    Currently,there are two forms of writing Chinese character:
      -- simplified character(SC): mainland of China
      -- traditional character(TC): Taiwan,Hongkong,Macao
   =20
    Except for some special writing forms of certain character, their=20
    meaning had also been changed in the long history. Generally =
different
    writing forms of a Chinese character can substituted by each other=20
    without changing the meaning of the word(phrase).   =20
=20
  =20
1.3 The Usage of Appellation in China
    In China, Generally speaking,every companies,organizations and =
people
    have two names: full name and abbreviation.
   =20
    The abbreviated name is easy to remember and to communicate.The full
    name is a formal name which is used in formal document,situation.
   =20
    To the name owners,the two names are equal necessary and important.=20
    So,in domain name registration,they usually register both full name=20
    and the corresponding abbreviations in order to permit people to =
access
    the same domain name by typing the full name or the abbreviatied =
name.
    Some of the full names are quite long,that's why the length of =
domain=20
    name is important for Chinese user.


2. Chinese characters in DNS
1.1 Traditional and Simplified Chinese Conversion has 3 forms:
    1-1 mapping: one traditional character(TC) maps to ONLY one =
simplified
                 characer(SC).
    1-n mapping: one TC has several SC writing forms=09
    n-1 mapping: one SC has several forms of TC

1.2 Delimiter folding
    The full stop in chinese is "=A1=A3". Therefore, the "=A1=A3" in =
CDNS is equal=20
    to the dot "." as the delimiter.

1.3 Label sequence
   Currently,the label sequence of LDH domain name is from left to =
right,
   (e.g.:abc.def.ghi.net),the subdomain is to the left and the superset=20
   of the subdomain is to the right.
  =20
   In China,user has reverse convention of language. Considering the=20
   culture different between the east and the west, it's necessary for
   people to access the Internet with the convention of using their =
native
   languages.for example:
  =20
        CDNLabel1.CDNLabel2.cn=20
   perfer to :
        cn.CDNLabel2.CDNLabel1
        =20
  =20


3. Solutions =20
3.1 Client side solution=20

	    +-----------------------------------------------+
	    |                  user input 		    |
	    +-----------------------------------------------+
		   |				      ^
		   V				      |
	 +-------------------+			      |
	 | Delimiter folding |			      |
	 |    "=A1=A3" -> "."    |			      |
	 +-------------------+			      |
	 	   |				      |=09
	 	   V				      |=09
    +------------------------------+	+------------------------------+
    | label sequence normalization |	| label sequence normalization |
    +------------------------------+	+------------------------------+
		   |				      ^
		   V				      |=09
        +----------------------+  	   +----------------------+
  	| local encoding ->UCS |	   | UCS ->local encoding |
        +----------------------+	   +----------------------+
	  	   |				      ^
	  	   V				      |=09
       +------------------------+	  +------------------------+
       | local mapping (TC - SC)|	  | local mapping (TC - SC)|
       +------------------------+	  +------------------------+
       		   |				      ^
       		   V				      |=09
       	      +----------+                            |
              | NAMEPREP |                            |
              +----------+                            |
              	   |				      |=09
              	   V				      |=09
             +------------+			+-----------------+
             | UCS -> MDN |			| UTF8/ACE -> UCS |
             +------------+			+-----------------+
             	   |				      ^=09
             	   V				      |
             +-----------------------------------------------+
             | 		     	local resolver 		     |
             +-----------------------------------------------+
             |  		  DNS server		     |
             +-----------------------------------------------+


3.1 Server side solution

	    +-----------------------------------------------+
	    |                  user input 		    |
	    +-----------------------------------------------+
		   |				      ^
		   V				      |
	 +-------------------+			      |
	 | Delimiter folding |			      |
	 |    "=A1=A3" -> "."    |			      |
	 +-------------------+			      |
	 	   |				      |=09
	 	   V				      |=09
    +------------------------------+	+------------------------------+
    | label sequence normalization |	| label sequence normalization |
    +------------------------------+	+------------------------------+
		   |				      ^
		   V				      |=09
        +----------------------+  	   +----------------------+
  	| local encoding ->UCS |	   | UCS ->local encoding |
        +----------------------+	   +----------------------+
	  	   |				      ^
	  	   V				      |=09
       	      +----------+                            |
              | NAMEPREP |                            |
              +----------+                            |
              	   |				      |=09
              	   V				      |=09
             +------------+			+-----------------+
             | UCS -> MDN |			| UTF8/ACE -> UCS |
             +------------+			+-----------------+
             	   |				      ^=09
             	   V				      |
             +-----------------------------------------------+
             | 		     	local resolver 		     |
             +-----------------------------------------------+
             			     |
             			     V
             +-----------------------------------------------+
             |  	    local mapping (TC - SC)	     |
             |-----------------------------------------------|
             |  		  DNS server		     |
             +-----------------------------------------------+


6 Authors' Address
Xiang Deng
China Internet Network Information Center=20
NO.4  South 4th ST. Beijing, P.R.China, 100080, PO BOX 349
Tel: +86-10-62619750=20

Yan Fang Wang
China Internet Network Information Center=20
NO.4  South 4th ST. Beijing, P.R.China, 100080, PO BOX 349
Tel: +86-10-62619750=20


7 References

[IDNREQ]  Requirements of Internationalized Domain Names, Zita Wenzel,=20
                James Seng, draft-ietf-idn-requirements

[NAMEPREP] Paul Hoffman & Marc Blanchet, Preparation of
           Internationalized Host Names, draft-ietf-idn-nameprep

[RFC2119] Scott Bradner, Key words for use in RFCs to Indicate
          Requirement Levels, March 1997, RFC 2119.

[STD13]   Paul Mockapetris, Domain names - implementation and
          specification, November 1987, STD 13 (RFC 1034 and 1035).
            =20
[UNAME]   Internationalized Domain Names and Unique Identifiers/Names
                Li Ming TSENG, Jan Ming HO, Hua Lin QIAN, Kenny HUANG
                draft-ietf-idn-uname
               =20
[TSCONV]  Traditional and Simplified Chinese Conversion
		Xiao Dong Lee, Nai Wen Hsu, Erin Chen, Guo Nian Sun
		draft-ietf-idn-tsconv
	=09
[ISO10646] ISO/IEC 10646-1:2000. International Standard -- Information
           technology -- Universal Multiple-Octet Coded Character Set=20
           (UCS) -- Part 1: Architecture and Basic Multilingual Plane.

[Unicode3] The Unicode Consortium, "The Unicode Standard -- Version3.0",
           ISBN 0-201-61633-5.=20
          =20
           
------=_NextPart_000_0023_01C1104C.6590C570--




From owner-idn@ops.ietf.org  Thu Jul 19 00:48:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA07223
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 00:48:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N5Ta-000DRv-00
	for idn-data@psg.com; Wed, 18 Jul 2001 21:31:50 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15N5TZ-000DRY-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 21:31:49 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15N5TY-0005jK-00; Wed, 18 Jul 2001 21:31:48 -0700
Date: Thu, 19 Jul 2001 04:31:48 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
Message-ID: <20010719043148.M19841@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20010719033341.31782.qmail@cr.yp.to>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

"D. J. Bernstein" <djb@cr.yp.to> wrote:

> What you're neglecting to take into account is that ACE is
> substantially more expensive to deploy than UTF-8.

If you're right, then it won't be deployed, so don't worry about it.

> You were claiming before that ACE wouldn't cause any
> failures. ``Nothing will actually break,'' you said.

I overstated it.  I was wrong.  Sorry.  But you agree that ACE will
break fewer things in the beginning than an 8-bit encoding.  I think
that's very important for the successful rollout of IDNs, so I'm going
to work on ACE.  You are free to believe that I'm wasting my time.

AMC



From owner-idn@ops.ietf.org  Thu Jul 19 00:57:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA08274
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 00:57:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N5bY-000DxR-00
	for idn-data@psg.com; Wed, 18 Jul 2001 21:40:04 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15N5bU-000Dv0-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 21:40:02 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f6J4bNd53509;
	Thu, 19 Jul 2001 00:37:23 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107190437.f6J4bNd53509@nic-naa.net>
To: "Soobok Lee" <lsb@postel.co.kr>
cc: idn@ops.ietf.org, brunner@nic-naa.net, quaynor@ghana.com
Subject: Re: [idn] Re: language scripts classified 
In-Reply-To: Your message of "Wed, 18 Jul 2001 11:17:53 +0900."
             <026b01c10f2f$da789660$ed1bd9d2@postel.co.kr> 
Date: Thu, 19 Jul 2001 00:37:23 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Soobok,

I still haven't any idea as to the utility or purpose of your scheme, but
I don't have to understand your purpose to attempt an answer to your set
of questions.

UCAS (Unified Canadian Aboriginal Syllabics) entered ISO10646 via the work
of the Canadian Aboriginal Syllabics Encoding Committee, chaired by Dirk
Vermeulen.

It incorporates the syllabic characters of Eastern, Western and Bible Cree,
Naskapi, Siksika (Algonquin), Athabascan, Carrier, Sayisi, Slavey (Dene),
and Inuktitut and Nunavut (Inuit), three language families, so character
frequency data "for UCAS" would be an average, comperable to one for Finnish
and Turkish, Icelandic, English and French, and Romaji-form Japanesse.

As with some other scripts now in ISO10646 via the Unicode Technical Committee,
UCAS was "unified" by people who's primary interest was glyph collection and
who view language, collation, distribution, etc., as properties of glyphs, who
managed to fail to impress upon the beneficiaries of their technical largess
that perhaps not all the world is a printer.

The current ISO10646 ordering approximates row-centric (E, I, O, A) vowel
ordering, marred by "Han (like) Unification", which manages to compress a
set of under 1K possible code-points into 600 or so (range U+1400 to U+1676),
a rather modest win. Here are the first "row", keep in mind that Y-CREE is as
like CARRIER as Japanese is like English.

		U+1401 E
		U+1401 AAI
		U+1402 I
		U+1404 II
		U+1405 O
		U+1406 OO
		U+1407 Y-CREE OO
		U+1408 CARRIER EE
		U+1409 CARRIER I
		U+1410 A

All the Algonquin languages I'm familiar with (W-Cree, Y-Cree, Siksika) teach
column ordering in schools ("Wa Pa Ta Ka ...") columnar consonant-ordering,
though both ordering exist in Nunavut (Inuktitut) usages. I can't shed any
light on Dene use though I suppose I'll have to ask around eventually.

That should motivate why writing collation for languages using UCAS for
code-points is difficult, even a barrier to the expansion of text-based
computer mediated language applications for about half of the Indians in
Canada.

The population question is hard to answer, as lots of people, Canadian and
Indian, arrive at different answers, for policy reasons. Canadians want to
diminsh the number of "Indians", Treaty Indians want to control the number
of C-31 "Indians", and Constitutional "Indians" may differ from everyone.
The "counting" situation is no better in the US, where differing "blood
quanta" and lineal descent rules exist, in a hodgepodge of Federal, State,
and formerly Terminated Tribes rules. It isn't a useful question to attempt
either, utilitarianism in this area is not polite, neh?

I hope this has been helpful, there are several dozen characters in the
1400 - 1676 range that are nameprep suspects for the usual reasons e.g.,
U+1429 FINAL PLUS looks like "+" U+002b, etc.

Do you really need character frequency data for UCAS for reordering? Just
how much of a win would halving the effective repetoire present to an ACE
designer? I'm pretty ignorant about ACE design issues. I'm afraid that my
text archives are a) in print, and b) W-Cree and Siksika centric, and not
representative of all the syllabics language communities.

I hope you don't mind my responding via the IDN list, and cc'ing Dr. Nii
Quaynor, who is working on a syllabary for several Central African languages,
and may appreciate some exposure to non-glyph issues he may not already be
aware of.

Eric



From owner-idn@ops.ietf.org  Thu Jul 19 02:12:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA10371
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 02:12:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N6cd-000HV0-00
	for idn-data@psg.com; Wed, 18 Jul 2001 22:45:15 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15N6cc-000HUt-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 22:45:14 -0700
Received: from zetnet.co.uk (man-s346.dialup.zetnet.co.uk [194.247.45.217])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6J5ids12503;
	Thu, 19 Jul 2001 06:44:39 +0100
Message-ID: <3B567416.32652779@zetnet.co.uk>
Date: Thu, 19 Jul 2001 06:45:58 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <20010719015651.F19841@arwen.cs.berkeley.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

"Adam M. Costello" wrote:
> "D. J. Bernstein" <djb@cr.yp.to> wrote:
> 
> > > I don't see how this is an ACE failure.
> >
> > You don't see that it's a failure?  Or you don't see that the
> > procedure succeeds if the ACE IDN is replaced by a normal domain name?
> 
> Of course it's a failure, but it's not an ACE failure, it's an IDN
> failure.  The exact same failure would happen for any IDN in this
> scenario regardless of whether ACE existed or not.

No - it works for just-send-UTF8 (which I assume is Dan's point [*]),
and it also works for ACE + UTF-8 proposals in which either an ACE or a
UTF-8 name can be passed to the resolver (including IDN-8). IDN-8 pays
great attention to fixing some other types of cut and paste failure as
well; I consider any proposal where cut and paste doesn't work properly
to be seriously deficient.

[*] I don't agree with Dan that just-send-UTF-8 is an acceptable solution,
    but I do certainly agree that ACE-only proposals are not.

> But there are other scenarios (like replying to a message, which is
> even more common than cutting and pasting addresses) where ACE will not
> fail, and any other encoding might (often would, given the popularity of
> sendmail and BIND).

IDN-8 will work with sendmail and BIND. (I'll describe the details in
another post; please bear with me on that.)

> It's undeniable that ACE is more backward-compatible, and fails in fewer
> instances, than any 8-bit encoding.

Encodings don't succeed or fail; proposals do. So, which ACE proposal?

It isn't true in general that proposals using ACE as the primary encoding
fail in fewer instances than proposals where UTF-8 is preferred. IDNA, for
example, fails in some cases where IDN-8 works, including the example
given by Dan, and including any other situation where a UTF-8 name leaks
to an application using ACE. (Note that UTF-8 will be a very commonly used
character encoding - probably *the* most common - regardless of which
proposal is adopted, so it is impossible to completely prevent such leakage.)

If you count displaying an ACE name to a human user as a failure (which
I do, although it is less serious than a lookup failure), then ACE-only
proposals fail in many more cases.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO1ZWYjkCAxeYt5gVAQF6Hgf+O/z/PThOO8UIDqtdf/kuTtTOhDk+nw6e
GyRKSy0YSSQ6yx7t5W0xFhw93ikeR2Yk5/GaQpr95h2wmfgzgWv7nmuGpkh3vRuJ
mqezObIQZraFXzfhJpsHt70JrMnZDYwoHO8lGkmN896cTMyl20KX5Dh5YOw+Cdjb
qPMyzfAwYOgiibWqVrRpaVhG80XNO1rZw41grJPcseZPtlhMQdh3Kxhc5cLmUpcY
+MMb401ZYwwn1L/yfW/JDGhOUwnyhxKIxQ4KI+lZR8qNwMb2Ecowfq/KKkiXeU/d
eduBwvZ+KDjGdEnwFCLJq77DeQMt+CpOS1JuzWTBsU+h/j8EWs/z3A==
=dPBw
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Thu Jul 19 02:29:17 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA13900
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 02:29:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N6xV-000Ibd-00
	for idn-data@psg.com; Wed, 18 Jul 2001 23:06:49 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15N6xU-000IbX-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 23:06:48 -0700
Received: (qmail 29688 invoked by uid 1001); 19 Jul 2001 06:07:08 -0000
Date: 19 Jul 2001 06:07:08 -0000
Message-ID: <20010719060708.18221.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
Automatic-Legal-Notices: Copyright 2001, D. J. Bernstein. My transmission of this message to you does not constitute a copyright waiver or any other limitation of my rights, even if you have told me otherwise.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <20010719033341.31782.qmail@cr.yp.to> <20010719043148.M19841@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

The following diagram may be helpful:

           2002       2003       2004       2005       2006
          +----------+----------+----------+----------+----------+
   ACE   A|**********|**********|********* |********  |******    |
         B|          |          |          |          |          |
         C|XXXXXXX   |XXXXXXXXXX|XXXXXXXX  |XXXXXX    |XXXX      |
          +----------+----------+----------+----------+----------+
   UTF-8 A|******    |***       |*         |          |          |
         B|XXX       |XX        |          |          |          |
         C|XXXX      |XXX       |X         |          |          |
          +----------+----------+----------+----------+----------+

The X's represent mail reply failures: row B for built-in replies, row C
for copy-and-paste. The *'s in row A represent annoying IDN displays.
All the numbers are guesses; we need further analysis.

The ACE myth is that there are no X's in the ACE boxes. What's true is
that there are no X's in row B in the ACE boxes.

Adam M. Costello writes:
> But you agree that ACE will
> break fewer things in the beginning than an 8-bit encoding

Fewer procedures, yes---fewer lines in the above picture---but this
doesn't necessarily mean that the _number_ of failures will be smaller,
even if you look only at the 2002 box. Count the X's!

What you're neglecting to take into account this time is that UTF-8
support is already far past ``the beginning.'' That's why the rows of
X's for UTF-8 are relatively short.

Many programs can send mail to UTF-8 addresses, for example. They'll
work fine in the copy-and-paste situation I described, if we use UTF-8
IDNs rather than ACE IDNs.

---Dan



From owner-idn@ops.ietf.org  Thu Jul 19 02:47:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA18244
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 02:47:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N7NP-000K6M-00
	for idn-data@psg.com; Wed, 18 Jul 2001 23:33:35 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15N7NO-000K6G-00
	for idn@ops.ietf.org; Wed, 18 Jul 2001 23:33:34 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15N7NO-0006aJ-00; Wed, 18 Jul 2001 23:33:34 -0700
Date: Thu, 19 Jul 2001 06:33:34 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
Message-ID: <20010719063334.O19841@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B567416.32652779@zetnet.co.uk>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

David Hopwood <david.hopwood@zetnet.co.uk> wrote:

> > Of course it's a failure, but it's not an ACE failure, it's an IDN
> > failure.  The exact same failure would happen for any IDN in this
> > scenario regardless of whether ACE existed or not.
>
> No - it works for just-send-UTF8 (which I assume is Dan's point [*]),
> and it also works for ACE + UTF-8 proposals in which either an ACE or
> a UTF-8 name can be passed to the resolver (including IDN-8).

It works iff the old resolver API can resolve names encoded using the
8-bit encoding used by the clipboard when the mailto: URL was copied
from the browser.  Whether the old resolver API can or should do this is
a debatable question whether ACE exists or not.  The operation in this
scenario is going to succeed or fail regardless of whether this name is
represented using ACE or not.  These are what I meant when I said it's
not an ACE failure, but an IDN failure.

> > It's undeniable that ACE is more backward-compatible, and fails in
> > fewer instances, than any 8-bit encoding.
>
> Encodings don't succeed or fail; proposals do.  So, which ACE
> proposal?

I wasn't talking about proposals, I was talking about domain names
encoded one way or another.  Take any situation where an ACE name fails
to work, replace the name with a corresponding 8-bit encoding, and it
still won't work.  But there are many situations where an ACE name
succeeds while an 8-bit name name would fail.  Therefore ACE is a useful
tool to have in your toolbox.  I think you agree, since you advocate a
system (IDN-8) that includes ACE.

> It isn't true in general that proposals using ACE as the primary
> encoding fail in fewer instances than proposals where UTF-8 is
> preferred.

I don't think I've ever advocated an ACE-only approach, or even argued
that ACE should be preferred.  I've merely argued that ACE is a good
thing to have as an option, for interoperating with old protocols and
old software.

> If you count displaying an ACE name to a human user as a failure
> (which I do, although it is less serious than a lookup failure), then
> ACE-only proposals fail in many more cases.

I'd count it as an annoyance or a glitch, but not a failure.  The
primary purpose of a domain name is to identify a network resource and
allow it to be accessed.  Being pretty/memorable/meaningful is very
desirable, but not essential.

AMC



From owner-idn@ops.ietf.org  Thu Jul 19 03:34:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA23711
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 03:34:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15N812-000MVu-00
	for idn-data@psg.com; Thu, 19 Jul 2001 00:14:32 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15N811-000MVo-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 00:14:31 -0700
Received: from bbthead.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id AAA11266;
	Thu, 19 Jul 2001 00:14:19 -0700
Message-Id: <5.1.0.14.2.20010719000035.0330e150@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 19 Jul 2001 00:06:43 -0700
To: "D. J. Bernstein" <djb@cr.yp.to>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] Debunking the ACE myth
Cc: idn@ops.ietf.org
In-Reply-To: <20010718064656.15762.qmail@cr.yp.to>
References: <5.0.2.1.2.20010717173427.02ff3330@localhost>
 <200107180221.WAA22344@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 11:46 PM 7/17/2001, D. J. Bernstein wrote:
>The ACE myth is that we can safely start using ACE IDNs before all the
>browsers, mail clients, etc. have been modified.
>...
>I see a mailto URL in my browser. I don't like the browser's built-in
>mailer, and changing the mailto handler is inconvenient, so I simply
>copy-and-paste the address into my mail client. The address looks fine.
>I type the message and send it. (This is a very common situation.)

The premise behind transition approaches that use special encoding, on top 
of an existing infrastructure that is unmodified, is that arbitrary pairs 
of participants can safely use the scheme, without waiting for 
infrastructure changes. The comparison, then, is against a scheme that 
requires deeper changes, to the infrastructure.

In this case, the question is about changes to the DNS server 
infrastructure.  UTF8 requires changes to them.  ACE does not.

Hence ACE can become usable far quicker than a raw binary approach.

This of course does not mean that ACE will work for everyone immediately. 
But, then, neither scheme will cause me to be able to type or read kanji.

On the other hand, if I DID understand kanji, then someone with a domain 
name that uses that character set would be accessible to me, subject only 
to my upgrading my own system.  Neither they nor I would have to wait for 
DNS server infrastructure upgrades.

With UTF-8, we would have to wait on the server operators to make the upgrade.

d/


----------
Dave Crocker  <mailto:dcrocker@brandenburg.com>
Brandenburg InternetWorking  <http://www.brandenburg.com>
tel +1.408.246.8253;  fax +1.408.273.6464




From owner-idn@ops.ietf.org  Thu Jul 19 05:56:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA13172
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 05:56:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NAJA-0002vY-00
	for idn-data@psg.com; Thu, 19 Jul 2001 02:41:24 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NAJ8-0002vB-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 02:41:22 -0700
Received: from enoshima (tea13.w3.mag.keio.ac.jp [133.27.228.243])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id SAA20203;
	Thu, 19 Jul 2001 18:41:19 +0900 (JST)
Message-Id: <4.2.0.58.J.20010719162407.030fff00@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 19 Jul 2001 16:25:26 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>,
        "Adam M. Costello" <amc@cs.berkeley.edu>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] nameprep failures
In-Reply-To: <00a401c10ffd$2d19e9a0$ed1bd9d2@postel.co.kr>
References: <20010719021906.G19841@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 11:47 01/07/19 +0900, Soobok Lee wrote:

>From: "Adam M. Costello" <amc@cs.berkeley.edu>


> > No one is going to put <Alpha>OL.COM on a business card and seriously
> > expect people to read it correctly.

>At least, a cheater or a fraud would deliberately try  it.

Cheaters won't try to put in on namecards.
They may try to put it into an email, and get you to
click on it.

Regards,   Martin.



From owner-idn@ops.ietf.org  Thu Jul 19 05:57:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA13255
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 05:57:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NAJA-0002vX-00
	for idn-data@psg.com; Thu, 19 Jul 2001 02:41:24 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NAJ8-0002vA-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 02:41:22 -0700
Received: from enoshima (tea13.w3.mag.keio.ac.jp [133.27.228.243])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id SAA20209;
	Thu, 19 Jul 2001 18:41:20 +0900 (JST)
Message-Id: <4.2.0.58.J.20010719163929.039b4100@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 19 Jul 2001 16:47:27 +0900
To: "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Debunking the ACE myth
In-Reply-To: <20010719015651.F19841@arwen.cs.berkeley.edu>
References: <20010719011709.3228.qmail@cr.yp.to>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 01:56 01/07/19 +0000, Adam M. Costello wrote:
>Let some people
>work on standards for ACE, and some people work on standards for UTF-8,
>and if you're right about ACE being worthless, then the ACE standards
>will get ignored.

Adam - Some people working on UTF-8 standards (or trying to suggest
such work) have been told that this would not be possible to happen
in this WG. Nobody on the ACE side has been told thus. This is quite
asymmetric.

Another aspect where the situation is not symmetric is that
on the ACE side, there is disagreement about which ACE to take,
but everybody agrees with IDNA, because there is really not that
much to it. On the UTF-8 side, it's clear what UTF-8 is, but
there are a wide range of options of how to flag it (from
'just send' to 'new class'). I.e. the decision tree looks
quite different on each side. This makes it much more difficult
for any specific UTF-8 proposal to gather consensus. On the ACE
side, the fact that there is about the same disagreement as to
what ACE to take as there is as to what UTF-8 flagging is best
is just hidden behind IDNA.

Regards,   Martin.



From owner-idn@ops.ietf.org  Thu Jul 19 05:57:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA13359
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 05:57:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NAJY-0002w5-00
	for idn-data@psg.com; Thu, 19 Jul 2001 02:41:48 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NAJJ-0002vk-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 02:41:38 -0700
Received: from enoshima (tea13.w3.mag.keio.ac.jp [133.27.228.243])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id SAA20197;
	Thu, 19 Jul 2001 18:41:17 +0900 (JST)
Message-Id: <4.2.0.58.J.20010719155703.034369f0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 19 Jul 2001 16:04:22 +0900
To: Keith Moore <moore@cs.utk.edu>, "Soobok Lee" <lsb@postel.co.kr>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Re: Back to work (Nameprep) (was: Re: Just send
  UTF-8 with nameprep (was: RE: [idn] Reality Check)) 
Cc: "Keith Moore" <moore@cs.utk.edu>, idn@ops.ietf.org
In-Reply-To: <200107181510.LAA26526@astro.cs.utk.edu>
References: <Your message of "Wed, 18 Jul 2001 17:28:42 +0900." <031601c10f63$a8ca6560$ed1bd9d2@postel.co.kr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 11:10 01/07/18 -0400, Keith Moore wrote:
> > Now, let's think about another case of   all-Greek "oo.com" and all-Latin
> > "oo.com":
> > Either of the two consists of scripts from only single character sets.
> > But the two still look very similiar. Do you have any good idea about 
> this ?
>
>first, how likely is this in practice that a label of all Greek letters
>will accidentally collide with a label of all Latin letters?   (as opposed
>to a deliberate collision)

Very low for lower case. Between Latin and Greek, or Cyrillic and Greek,
it's only the 'o'.
Between Latin and Cyrillic, it's the 'a', 'e', 'o', 'p', 'c', 'y', 'x',
plus 's', 'i', and 'j' in some languages.

For upper-case, it's more. Regards,   Martin.



>for second-level domains at least, and for some third-level domains,
>it would make sense for the registry to disallow labels whose appearances
>collide with all-ASCII labels.

Most probably yes.


>there are already some such rules in place
>even for ASCII, these would just be extended.

Can you tell me more about these, or give some pointer?

Regards,   Martin.



From owner-idn@ops.ietf.org  Thu Jul 19 05:57:41 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA13398
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 05:57:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NAJK-0002vr-00
	for idn-data@psg.com; Thu, 19 Jul 2001 02:41:34 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NAJJ-0002vl-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 02:41:33 -0700
Received: from enoshima (tea13.w3.mag.keio.ac.jp [133.27.228.243])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id SAA20194;
	Thu, 19 Jul 2001 18:41:17 +0900 (JST)
Message-Id: <4.2.0.58.J.20010719155449.03cb5950@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 19 Jul 2001 15:56:08 +0900
To: Keith Moore <moore@cs.utk.edu>, "D. J. Bernstein" <djb@cr.yp.to>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Debunking the ACE myth 
Cc: idn@ops.ietf.org
In-Reply-To: <200107181528.LAA26737@astro.cs.utk.edu>
References: <Your message of "18 Jul 2001 06:46:56 -0000." <20010718064656.15762.qmail@cr.yp.to>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 11:28 01/07/18 -0400, Keith Moore wrote:
>Your example assumes that the browser will decode the ACE in the
>mailto: URL when copying the URL to the paste buffer, when in fact it's
>much safer to leave it as ACE.

It could as well assume that the mailto: uri was in UTF-8 from
the start, or was converted to that by a browser from an IRI.

Regards,   Martin.



From owner-idn@ops.ietf.org  Thu Jul 19 05:57:54 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA13465
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 05:57:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NAJF-0002vi-00
	for idn-data@psg.com; Thu, 19 Jul 2001 02:41:29 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NAJE-0002vc-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 02:41:28 -0700
Received: from enoshima (tea13.w3.mag.keio.ac.jp [133.27.228.243])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id SAA20212;
	Thu, 19 Jul 2001 18:41:20 +0900 (JST)
Message-Id: <4.2.0.58.J.20010719165243.0346b640@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 19 Jul 2001 17:16:13 +0900
To: Dave Crocker <dhc@dcrocker.net>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Debunking the ACE myth
Cc: idn@ops.ietf.org
In-Reply-To: <5.1.0.14.2.20010719000035.0330e150@dcrocker.net>
References: <20010718064656.15762.qmail@cr.yp.to>
 <5.0.2.1.2.20010717173427.02ff3330@localhost>
 <200107180221.WAA22344@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dave - What is your guess as to how quickly servers will be
upgraded, as compared to how quickly applications will be
upgraded?

My idea is that servers would be upgraded quite quickly,
much more quickly than applications.
The number of DNS server software offerings is not that
large, and the people responsible for the software are
in one way or another following this WG.
Any serious isp would very quickly get requests to upgrade
the DNS servers they advertise in their DHCP, and would
upgrade. (maybe with the exception of some isp in the US
outback)
Local resolver software can also be upgraded easily,
because it's a single upgrade for a system, and because
most probably patches will be provided rather quickly by
the OS vendors or by third parties.
Of course DNS servers that authoritatively serve IDNs
can be assumed to be upgraded also.

For applications, it's much more difficult. In some cases,
you will be lucky, but in other cases, you won't. If you
depend on an application, you may have to wait forever.
Also, application upgrades may cost much more.

So upgrading the DNS side isn't that much on the critical
path as far as I can see.

Regards,   Martin.

At 00:06 01/07/19 -0700, Dave Crocker wrote:

>The premise behind transition approaches that use special encoding, on top 
>of an existing infrastructure that is unmodified, is that arbitrary pairs 
>of participants can safely use the scheme, without waiting for 
>infrastructure changes. The comparison, then, is against a scheme that 
>requires deeper changes, to the infrastructure.
>
>In this case, the question is about changes to the DNS server 
>infrastructure.  UTF8 requires changes to them.  ACE does not.
>
>Hence ACE can become usable far quicker than a raw binary approach.
>
>This of course does not mean that ACE will work for everyone immediately. 
>But, then, neither scheme will cause me to be able to type or read kanji.
>
>On the other hand, if I DID understand kanji, then someone with a domain 
>name that uses that character set would be accessible to me, subject only 
>to my upgrading my own system.  Neither they nor I would have to wait for 
>DNS server infrastructure upgrades.
>
>With UTF-8, we would have to wait on the server operators to make the upgrade.




From owner-idn@ops.ietf.org  Thu Jul 19 05:58:20 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA13560
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 05:58:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NAJA-0002vV-00
	for idn-data@psg.com; Thu, 19 Jul 2001 02:41:24 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NAJ8-0002uy-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 02:41:23 -0700
Received: from enoshima (tea13.w3.mag.keio.ac.jp [133.27.228.243])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id SAA20200;
	Thu, 19 Jul 2001 18:41:18 +0900 (JST)
Message-Id: <4.2.0.58.J.20010719161607.030afe70@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 19 Jul 2001 16:19:58 +0900
To: "Eric A. Hall" <ehall@ehsco.com>, "Adam M. Costello" <amc@cs.berkeley.edu>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Re: Just send UTF-8 with nameprep
Cc: idn@ops.ietf.org
In-Reply-To: <3B5641F4.85668B13@ehsco.com>
References: <20010719005402.D19841@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 21:12 01/07/18 -0500, Eric A. Hall wrote:

>Any domain name which is entered as an IDN would need to have the IDN flag
>enabled, but must not have the legacy flag enabled. These IDNs must only
>be used to answer IDN queries, and must not be processed through legacy
>query paths, as they would likely be used to answer queries being issued
>by older applications in that scenario. We must not allow UTF-8 IDNs to to
>be processed by older applications, since they may be issuing queries
>based on a local encoding (such as 8859-n or windows-nnnn or MacRoman or
>whatever). Using these IDNs to answer legacy queries will absolutely
>definitely cause some kind of unintended consequence, and we will get a
>lot of heat for the failure.

The chance that when a legacy resolver passes through a local encoding
and this matches with a UTF-8 entry is extremely low. The reason for this
is that UTF-8 has a very peculiar byte pattern. For details, please see my
paper at
http://www.ifi.unizh.ch/mml/mduerst/papers/PDF/IUC11-UTF-8.pdf.

Regards,   Martin.



From owner-idn@ops.ietf.org  Thu Jul 19 05:59:18 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA13781
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 05:59:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NAJ8-0002vC-00
	for idn-data@psg.com; Thu, 19 Jul 2001 02:41:22 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NAJ7-0002ux-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 02:41:21 -0700
Received: from enoshima (tea13.w3.mag.keio.ac.jp [133.27.228.243])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id SAA20206;
	Thu, 19 Jul 2001 18:41:19 +0900 (JST)
Message-Id: <4.2.0.58.J.20010719162631.037e8ef0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 19 Jul 2001 16:34:57 +0900
To: "D. J. Bernstein" <djb@cr.yp.to>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] nameprep failures
In-Reply-To: <20010719013539.9259.qmail@cr.yp.to>
References: <Your <4.2.0.58.J.20010718120208.04004790@sh.w3.mag.keio.ac.jp>
 <4.2.0.58.J.20010718162652.039f5620@sh.w3.mag.keio.ac.jp>
 <031601c10f63$a8ca6560$ed1bd9d2@postel.co.kr>
 <004d01c10f9d$66dff540$0c680b41@c1340594a>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 01:35 01/07/19 +0000, D. J. Bernstein wrote:

>It seems safe to allow lowercase Greek alpha (and not the other alphas)

There are many accented Greek alphas; am I right that you would allow
them (in lower case)? There is a Latin alpha (in IPA), what about that?
There is a turned alpha (also in IPA), I guess that's no harm.


>as long as users _don't_ think they can type it in uppercase. We really
>should deprecate the use of uppercase characters in domain names.

Deprecating them looks like a good point, something that should go
in some of the drafts (maybe we need something like an 'advice to
users' draft?).

The nameprep draft might contain some advice to implementers about
whether to show the pre-nameprep or the post-nameprep string.
But I'm not sure it's worth throwing out the display of upper-case
(assuming about the same frequency as we have it currently)
to prevent the accidental confusion.

Regards,   Martin.



From owner-idn@ops.ietf.org  Thu Jul 19 06:37:41 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA21870
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 06:37:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NAsq-0004ki-00
	for idn-data@psg.com; Thu, 19 Jul 2001 03:18:16 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NAsp-0004kb-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 03:18:15 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id MAA29281;
	Thu, 19 Jul 2001 12:17:44 +0200 (MET DST)
Date: Thu, 19 Jul 2001 11:52:04 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: "D. J. Bernstein" <djb@cr.yp.to>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
Message-ID: <1351242.995543524@localhost>
In-Reply-To: <20010718064656.15762.qmail@cr.yp.to>
References: <5.0.2.1.2.20010717173427.02ff3330@localhost>
 <200107180221.WAA22344@astro.cs.utk.edu>
 <20010718064656.15762.qmail@cr.yp.to>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-07-18 06.46 +0000 "D. J. Bernstein" <djb@cr.yp.to> wrote:

> What went wrong is that the browser displayed the address as Unicode
> characters. The address then passed through the (CTEXT UTF-8, although
> UTF8_STRING would be better) copy-and-paste mechanism, the UTF-8 xterm,
> the mail client, and the 8-bit-clean MTA, none of which converted back
> to ACE. The resulting UTF-8 DNS lookup produced NXDOMAIN.

In the IDNA proposal we have specified that an application which handle
IDNA (like you seem to say that the browser is) only support IDNA if also
the content of the clipboard is converted to ACE before the domainname is
passed to other applications (which doesn't handle IDNA/ACE solution).

  paf




From owner-idn@ops.ietf.org  Thu Jul 19 08:34:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA14155
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 08:34:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NCVt-0009SR-00
	for idn-data@psg.com; Thu, 19 Jul 2001 05:02:41 -0700
Received: from [152.160.20.25] (helo=admin1.corp.walid.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NCVs-0009S6-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 05:02:40 -0700
Received: from CHOAM (admin1.corp.walid.com [152.160.20.25])
	by admin1.corp.walid.com (8.11.2/8.11.2) with SMTP id f6JBt6s29957;
	Thu, 19 Jul 2001 11:55:06 GMT
From: "Brian W. Spolarich" <briansp@walid.com>
To: "Martin Duerst" <duerst@w3.org>
Cc: <idn@ops.ietf.org>
Subject: RE: [idn] Debunking the ACE myth
Date: Thu, 19 Jul 2001 08:04:24 -0400
Message-ID: <FJEPLIJJEDBNPIOAEIHDAEMHCGAA.briansp@walid.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
In-Reply-To: <4.2.0.58.J.20010719165243.0346b640@sh.w3.mag.keio.ac.jp>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


| My idea is that servers would be upgraded quite quickly,
| much more quickly than applications.

  Martin, I suspect you are being extremely over-optimistic on this point.
:-)

  I've had discussions with a number of WALID clients who are interested in
deploying IDN resolution capabilities and have tried other, so-called
"server-side" approaches.  Those that in particular focus on requiring ISPs
to make changes have met with limited success in getting them to do so.

  There is a tremendous amount of inertia in the deployed nameserver
infrastructure.

  -bws




From owner-idn@ops.ietf.org  Thu Jul 19 09:13:44 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA24025
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 09:13:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NDBW-000BWI-00
	for idn-data@psg.com; Thu, 19 Jul 2001 05:45:42 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NDBS-000BW5-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 05:45:40 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f6JCgdd64554;
	Thu, 19 Jul 2001 08:42:39 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107191242.f6JCgdd64554@nic-naa.net>
To: "Brian W. Spolarich" <briansp@walid.com>
cc: "Martin Duerst" <duerst@w3.org>, idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Debunking the ACE myth 
In-Reply-To: Your message of "Thu, 19 Jul 2001 08:04:24 EDT."
             <FJEPLIJJEDBNPIOAEIHDAEMHCGAA.briansp@walid.com> 
Date: Thu, 19 Jul 2001 08:42:39 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> There is a tremendous amount of inertia in the deployed nameserver
> infrastructure.

Yeah. Last I heard the ISPs and their users were going to be stuck with the
com/net/org troika under a single vendor _forever_  ;-)

Inertia isn't absolute, and our responsibility is to more than just the
present comfortable.

Any change in the IPR status?

Eric



From owner-idn@ops.ietf.org  Thu Jul 19 09:23:00 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA27187
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 09:23:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NDG3-000Bnk-00
	for idn-data@psg.com; Thu, 19 Jul 2001 05:50:23 -0700
Received: from [152.160.20.25] (helo=admin1.corp.walid.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NDG1-000Bkm-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 05:50:22 -0700
Received: from CHOAM (admin1.corp.walid.com [152.160.20.25])
	by admin1.corp.walid.com (8.11.2/8.11.2) with SMTP id f6JCh0s30244;
	Thu, 19 Jul 2001 12:43:00 GMT
From: "Brian W. Spolarich" <briansp@walid.com>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
Subject: RE: [idn] Debunking the ACE myth 
Date: Thu, 19 Jul 2001 08:52:18 -0400
Message-ID: <FJEPLIJJEDBNPIOAEIHDEEMICGAA.briansp@walid.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
In-Reply-To: <200107191242.f6JCgdd64554@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


| Inertia isn't absolute, and our responsibility is to more than just the
| present comfortable.

  Our responsibility is to engineer solutions to problems that may actually
be deployable.

| Any change in the IPR status?

  That's not my bailiwick.  You should contact our IPR person if you have
particular questions.

  -bws




From owner-idn@ops.ietf.org  Thu Jul 19 09:25:43 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA27859
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 09:25:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NDSL-000CPJ-00
	for idn-data@psg.com; Thu, 19 Jul 2001 06:03:05 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NDSK-000CPB-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 06:03:04 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA03125;
        Thu, 19 Jul 2001 09:02:59 -0400 (EDT)
Message-Id: <200107191302.JAA03125@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "D. J. Bernstein" <djb@cr.yp.to>
cc: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth 
In-reply-to: Your message of "19 Jul 2001 06:07:08 -0000."
             <20010719060708.18221.qmail@cr.yp.to> 
Date: Thu, 19 Jul 2001 09:02:59 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

>            2002       2003       2004       2005       2006
>           +----------+----------+----------+----------+----------+
>    ACE   A|**********|**********|********* |********  |******    |
>          B|          |          |          |          |          |
>          C|XXXXXXX   |XXXXXXXXXX|XXXXXXXX  |XXXXXX    |XXXX      |
>           +----------+----------+----------+----------+----------+
>    UTF-8 A|******    |***       |*         |          |          |
>          B|XXX       |XX        |          |          |          |
>          C|XXXX      |XXX       |X         |          |          |
>           +----------+----------+----------+----------+----------+
> 
> The X's represent mail reply failures: row B for built-in replies, row C
> for copy-and-paste. The *'s in row A represent annoying IDN displays.
> All the numbers are guesses; we need further analysis.
> 
> The ACE myth is that there are no X's in the ACE boxes. What's true is
> that there are no X's in row B in the ACE boxes.
> 

thanks, that's a useful illustration.

I find it interesting that it assumes that MUAs will be upgraded more
quickly with UTF-8 than with ACE.  I would assume just the opposite - 
that UTF-8 is more immediately disruptive because the failures that 
it does cause are more numerous, and thus a larger barrier to adoption. 

Also, the X's in row C look larger than the spaces in row B - but 
built-in replies are surely far more common than copy-and-paste replies.

The graph also does not consider other kinds of failures due to UTF-8 -
e.g. failures of mail (including nondelivery reports) to be delivered
because one of the intermediate systems either couldn't deal with
the UTF-8 or because it munged the UTF-8 to the point that subsequent
systems couldn't make sense of it.


Precisely because of the copy-and-paste problem, I expect that
vendors will quickly upgrade MUAs to accept native IDN input 
regardless of whether ACE is used as the on-the-wire encoding.
Whether a large percentage of their customers upgrade quickly is
a different question-  but even if a few percent require that 
functionality, that's sufficient motiviation to fix the product.

Again, I don't think this is a either/or choice for this group-
most of us are convinced that we are going to need ACE for some
applications (at least during a transition period), and that we 
are going to use UTF-8 on the wire within other applications.  
Those choices will be made by other working groups.  

Keith



From owner-idn@ops.ietf.org  Thu Jul 19 09:26:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA27975
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 09:26:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NDZ0-000CjC-00
	for idn-data@psg.com; Thu, 19 Jul 2001 06:09:58 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NDYz-000Cim-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 06:09:57 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA03205;
        Thu, 19 Jul 2001 09:09:53 -0400 (EDT)
Message-Id: <200107191309.JAA03205@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Martin Duerst <duerst@w3.org>
cc: Dave Crocker <dhc@dcrocker.net>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth 
In-reply-to: Your message of "Thu, 19 Jul 2001 17:16:13 +0900."
             <4.2.0.58.J.20010719165243.0346b640@sh.w3.mag.keio.ac.jp> 
Date: Thu, 19 Jul 2001 09:09:53 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Dave - What is your guess as to how quickly servers will be
> upgraded, as compared to how quickly applications will be
> upgraded?
> 
> My idea is that servers would be upgraded quite quickly,
> much more quickly than applications.

I think server products will be upgraded quickly, but in many
parts of the world they will be deployed slowly.  It's not just
the ISPs that need to deploy new servers for this to work;
it's anyone that runs a DNS cache.

Keith



From owner-idn@ops.ietf.org  Thu Jul 19 09:36:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA00536
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 09:36:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NDdh-000D1U-00
	for idn-data@psg.com; Thu, 19 Jul 2001 06:14:49 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NDdh-000D1M-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 06:14:49 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA03254;
        Thu, 19 Jul 2001 09:14:45 -0400 (EDT)
Message-Id: <200107191314.JAA03254@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Martin Duerst <duerst@w3.org>
cc: "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth 
In-reply-to: Your message of "Thu, 19 Jul 2001 16:47:27 +0900."
             <4.2.0.58.J.20010719163929.039b4100@sh.w3.mag.keio.ac.jp> 
Date: Thu, 19 Jul 2001 09:14:45 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Another aspect where the situation is not symmetric is that
> on the ACE side, there is disagreement about which ACE to take,
> but everybody agrees with IDNA, because there is really not that
> much to it. 

yes, but I don't think that the choice of which ACE will be hugely
contentious.  It's just that we're still looking at various tradeoffs,
and people have been making productive suggestions that illuminate
those tradeoffs.  Most people who support IDNA would be willing to
accept any of the better ACEs.

Keith



From owner-idn@ops.ietf.org  Thu Jul 19 09:42:06 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA01597
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 09:42:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NDfh-000D8m-00
	for idn-data@psg.com; Thu, 19 Jul 2001 06:16:53 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15NDfg-000D8f-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 06:16:52 -0700
Received: (qmail 6569 invoked by uid 1001); 19 Jul 2001 13:17:07 -0000
Date: 19 Jul 2001 13:17:07 -0000
Message-ID: <20010719131707.30213.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
Automatic-Legal-Notices: Copyright 2001, D. J. Bernstein. My transmission of this message to you does not constitute a copyright waiver or any other limitation of my rights, even if you have told me otherwise.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <5.0.2.1.2.20010717173427.02ff3330@localhost> <200107180221.WAA22344@astro.cs.utk.edu> <20010718064656.15762.qmail@cr.yp.to> <5.1.0.14.2.20010719000035.0330e150@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dave Crocker writes:
> In this case, the question is about changes to the DNS server 
> infrastructure.  UTF8 requires changes to them.

Wrong again. UTF-8 poses no problems for DNS servers. As Mark Andrews
says: ``UTF8 does not require a server upgrade.''

---Dan



From owner-idn@ops.ietf.org  Thu Jul 19 10:21:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA10420
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 10:21:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NELx-000FUf-00
	for idn-data@psg.com; Thu, 19 Jul 2001 07:00:33 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NELw-000FTT-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 07:00:32 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id PAA13859;
	Thu, 19 Jul 2001 15:58:56 +0200 (MET DST)
Date: Thu, 19 Jul 2001 15:54:47 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Martin Duerst <duerst@w3.org>, "Adam M. Costello" <amc@cs.berkeley.edu>,
        idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
Message-ID: <1685871.995558087@localhost>
In-Reply-To: <4.2.0.58.J.20010719163929.039b4100@sh.w3.mag.keio.ac.jp>
References: <20010719011709.3228.qmail@cr.yp.to>
 <4.2.0.58.J.20010719163929.039b4100@sh.w3.mag.keio.ac.jp>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-07-19 16.47 +0900 Martin Duerst <duerst@w3.org> wrote:

> Adam - Some people working on UTF-8 standards (or trying to suggest
> such work) have been told that this would not be possible to happen
> in this WG. Nobody on the ACE side has been told thus. This is quite
> asymmetric.

Reason for this is that ACE is backward compatible with the standards we
already have, such as RFC 2821 and RFC 2822. If we have a solution which
points at UTF-8 as the transport, then the RFC's specifying the application
layer protocols have to be updated -- and proper handshake (if needed) and
downgrade to ascii encoding (if needed) is defined.

I.e. the problem with using non-ascii in the labels in DNS, is that it is
really easy to get what I would call leakage into the application layer
protocols which can not handle other characters than ASCII.

How to handle Unicode and how to reach the goal of using UTF-8 encoding in
the future is something I rather see each wg which have knowledge about the
specific protocol. Regardless of how easy or hard it is.

  paf




From owner-idn@ops.ietf.org  Thu Jul 19 11:15:56 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA19682
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 11:15:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NFDH-000IBL-00
	for idn-data@psg.com; Thu, 19 Jul 2001 07:55:39 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15NFDG-000IBE-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 07:55:38 -0700
Message-ID: <004601c11063$a8283aa0$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        "Martin Duerst" <duerst@w3.org>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, <idn@ops.ietf.org>
References: <20010719011709.3228.qmail@cr.yp.to> <4.2.0.58.J.20010719163929.039b4100@sh.w3.mag.keio.ac.jp> <1685871.995558087@localhost>
Subject: Re: [idn] Debunking the ACE myth
Date: Thu, 19 Jul 2001 11:01:12 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> How to handle Unicode and how to reach the goal of using UTF-8 encoding in
> the future is something I rather see each wg which have knowledge about
the
> specific protocol. Regardless of how easy or hard it is.
>
But where do we start? Is not this a good opportunitiy and place to begin?
I am very much for a ACE+UTF solution and I think we should work on both
before we submerge ourselves into a possibly irreversible journey into ACE
forever.  Once a specifcation for eventually using UTF in DNS is set, it
will layout a framework for all the protocols that depend on DNS to start
upgrading.  The point I am trying to make is that DNS has to move first, it
has been from the begining, or else, why would the other protocols have
depended on DNS at all?

Edmon




From owner-idn@ops.ietf.org  Thu Jul 19 11:42:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA27358
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 11:42:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NFdc-000Jhv-00
	for idn-data@psg.com; Thu, 19 Jul 2001 08:22:52 -0700
Received: from epa.secret.org ([206.220.140.150] ident=0)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NFdb-000Jhp-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 08:22:51 -0700
Received: from localhost (lucid@localhost)
	by epa.secret.org (8.9.3/8.9.1) with ESMTP id LAA62293;
	Thu, 19 Jul 2001 11:22:37 -0400 (EDT)
Date: Thu, 19 Jul 2001 11:22:36 -0400 (EDT)
From: <lucid@epa.secret.org>
To: "Brian W. Spolarich" <briansp@walid.com>
cc: Martin Duerst <duerst@w3.org>, <idn@ops.ietf.org>
Subject: RE: [idn] Debunking the ACE myth
In-Reply-To: <FJEPLIJJEDBNPIOAEIHDAEMHCGAA.briansp@walid.com>
Message-ID: <Pine.BSF.4.33.0107191119470.61325-100000@epa.secret.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


Getting ISPs to upgrade to DNS that supports UTF-8 is simple.
Patch BIND now, wait for the next remote root exploit which is
followed by a worm.

-Bill

On Thu, 19 Jul 2001, Brian W. Spolarich wrote:

>
> | My idea is that servers would be upgraded quite quickly,
> | much more quickly than applications.
>
>   Martin, I suspect you are being extremely over-optimistic on this point.
> :-)
>
>   I've had discussions with a number of WALID clients who are interested in
> deploying IDN resolution capabilities and have tried other, so-called
> "server-side" approaches.  Those that in particular focus on requiring ISPs
> to make changes have met with limited success in getting them to do so.
>
>   There is a tremendous amount of inertia in the deployed nameserver
> infrastructure.
>
>   -bws
>
>
>




From owner-idn@ops.ietf.org  Thu Jul 19 11:42:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA27430
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 11:42:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NFaL-000JOS-00
	for idn-data@psg.com; Thu, 19 Jul 2001 08:19:29 -0700
Received: from femail1.sdc1.sfba.home.com ([24.0.95.81])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NFaJ-000JNz-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 08:19:27 -0700
Received: from c1340594a ([65.11.104.12]) by femail1.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20010719151920.QRBF8703.femail1.sdc1.sfba.home.com@c1340594a>;
          Thu, 19 Jul 2001 08:19:20 -0700
Message-ID: <00bc01c11066$640cbeb0$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "Keith Moore" <moore@cs.utk.edu>, "Soobok Lee" <lsb@postel.co.kr>,
        "Martin Duerst" <duerst@w3.org>
Cc: "Keith Moore" <moore@cs.utk.edu>, <idn@ops.ietf.org>
References: <Your message of "Wed, 18 Jul 2001 17:28:42 +0900." <031601c10f63$a8ca6560$ed1bd9d2@postel.co.kr> <4.2.0.58.J.20010719155703.034369f0@sh.w3.mag.keio.ac.jp>
Subject: Re: [idn] Re: Back to work (Nameprep) (was: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check)) 
Date: Thu, 19 Jul 2001 08:20:49 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00B9_01C1102B.B77B6500"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_00B9_01C1102B.B77B6500
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

> Very low for lower case. Between Latin and Greek, or Cyrillic and =
Greek,
> it's only the 'o'.

This is inaccurate. For example, phi (=CF=86,=CF=95) and o-slash =
(=C3=B8) are confusable depending on the font, i.e., where the slash in =
the phi is at an angle. Rho (=CF=81) and p (p) are confusible in certain =
fonts, etc. And you can't forget all the extended Latin characters. =
There is Latin small letter open e (=C9=9B) and epsilon (=CE=B5). For =
Cyrillic and Greek, you are omitting many characters that are confusable =
(=D0=BA, =D0=BF, =D1=80, =D1=84, =D1=94, =D1=A1, =D1=B1, =D1=B3, ...) . =
For capitals, don't forget the extended Latin and Cyrillic characters, =
like O with tilde (=C6=9F) vs. theta (=CE=98), or Latin letter Esh =
(=C6=A9) and Sigma (=CE=A3).

But there are also many confusable characters even within the same =
script, like b (b) and Latin letter tone 6 (=C6=85), p (p) and latin =
letter wynn (=C6=BF), many hooked letters which can fool someone who =
isn't looking for them: k (k) vs hooked k (=C6=99), capital I or one and =
dental clicks (=C7=80), variants like script g (=C9=A1), etc. Forbidding =
script mixing would not solve those.

It would take some real work to look at all the Unicode characters under =
a variety of common fonts at 9-12 point (normal body text) to determine =
which are confusable and which are not, and cross-check all the results. =
I'm not saying it can't be done -- and it would be a worthwhile effort =
in the long run -- but it is not trivial.

That is why I think the most practical solution is for GUI support that =
allows for human judgment.

Mark

P.S. Depending on what font your are using, of course, the above =
examples may or may not be distinguishable.

=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94

=CF=80=CE=AC=CE=BD=CF=84=CF=89=CE=BD =
=CE=BC=CE=AD=CF=84=CF=81=CE=BF=CE=BD =
=E1=BC=84=CE=BD=CE=B8=CF=81=CF=89=CF=80=CE=BF=CF=82 =E2=80=94 =
=CE=A0=CF=81=CF=89=CF=84=CE=B1=CE=B3=CF=8C=CF=81=CE=B1=CF=82
[http://www.macchiato.com]

----- Original Message -----=20
From: "Martin Duerst" <duerst@w3.org>
To: "Keith Moore" <moore@cs.utk.edu>; "Soobok Lee" <lsb@postel.co.kr>
Cc: "Keith Moore" <moore@cs.utk.edu>; <idn@ops.ietf.org>
Sent: Thursday, July 19, 2001 00:04
Subject: Re: [idn] Re: Back to work (Nameprep) (was: Re: Just send UTF-8 =
with nameprep (was: RE: [idn] Reality Check))=20


> At 11:10 01/07/18 -0400, Keith Moore wrote:
> > > Now, let's think about another case of   all-Greek "oo.com" and =
all-Latin
> > > "oo.com":
> > > Either of the two consists of scripts from only single character =
sets.
> > > But the two still look very similiar. Do you have any good idea =
about=20
> > this ?
> >
> >first, how likely is this in practice that a label of all Greek =
letters
> >will accidentally collide with a label of all Latin letters?   (as =
opposed
> >to a deliberate collision)
>=20
> Very low for lower case. Between Latin and Greek, or Cyrillic and =
Greek,
> it's only the 'o'.
> Between Latin and Cyrillic, it's the 'a', 'e', 'o', 'p', 'c', 'y', =
'x',
> plus 's', 'i', and 'j' in some languages.
>=20
> For upper-case, it's more. Regards,   Martin.
>=20
>=20
>=20
> >for second-level domains at least, and for some third-level domains,
> >it would make sense for the registry to disallow labels whose =
appearances
> >collide with all-ASCII labels.
>=20
> Most probably yes.
>=20
>=20
> >there are already some such rules in place
> >even for ASCII, these would just be extended.
>=20
> Can you tell me more about these, or give some pointer?
>=20
> Regards,   Martin.
>=20
>=20

------=_NextPart_000_00B9_01C1102B.B77B6500
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<META content=3D"MSHTML 5.50.4616.200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff background=3D"">
<DIV><FONT size=3D1>&gt; Very low for lower case. Between Latin and =
Greek, or=20
Cyrillic and Greek,<BR>&gt; it's only the 'o'.<BR><BR>This is =
inaccurate. For=20
example, phi (=CF=86,=CF=95) and o-slash (=C3=B8) are confusable =
<EM>depending on the=20
font</EM>, i.e., where the slash in the phi is at an angle. Rho (=CF=81) =
and p (p)=20
are confusible in certain fonts, etc. And you can't forget all the =
extended=20
Latin characters. There is Latin small letter open e (=C9=9B) and =
epsilon (=CE=B5). For=20
Cyrillic and Greek, you are omitting many characters that are confusable =
(=D0=BA, =D0=BF,=20
=D1=80, =D1=84, =D1=94, =D1=A1, =D1=B1, =D1=B3, ...) .&nbsp;For =
capitals, don't forget the extended Latin and=20
Cyrillic characters, like O with tilde (=C6=9F) vs. theta (=CE=98), or =
Latin letter Esh=20
(=C6=A9) and Sigma (=CE=A3).</FONT></DIV>
<DIV><FONT size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT size=3D1>But there are also many confusable characters even =
within the=20
<EM>same</EM> script, like b (b) and Latin letter tone 6 (=C6=85), p (p) =
and latin=20
letter wynn (=C6=BF), many hooked letters which can fool someone who =
isn't looking=20
for them: k (k) vs hooked k&nbsp;(=C6=99), capital I or one and dental =
clicks (=C7=80),=20
variants like script g (=C9=A1), etc. Forbidding script mixing would not =
solve=20
those.</FONT></DIV>
<DIV><FONT size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT size=3D1>It would take some real work to look at <EM>all</EM> =
the=20
Unicode characters under a variety of common fonts at 9-12 point (normal =
body=20
text) to determine which are confusable and which are not, and =
cross-check all=20
the results. I'm not saying it can't be done -- and it would be a =
worthwhile=20
effort in the long run&nbsp;-- but it is <STRONG><EM>not</EM></STRONG>=20
trivial.</FONT></DIV>
<DIV><FONT size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT size=3D1>That is why I think the most practical solution is =
for GUI=20
support that allows for human judgment.<BR><BR>Mark</FONT></DIV>
<DIV><FONT size=3D1></FONT>&nbsp;</DIV>
<DIV><FONT size=3D1>P.S. Depending on what font your are using, of =
course, the=20
above examples may or may not be distinguishable.</FONT></DIV>
<DIV><FONT =
size=3D1><BR>=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94<BR><BR>=CF=80=CE=
=AC=CE=BD=CF=84=CF=89=CE=BD =CE=BC=CE=AD=CF=84=CF=81=CE=BF=CE=BD =
=E1=BC=84=CE=BD=CE=B8=CF=81=CF=89=CF=80=CE=BF=CF=82 =E2=80=94=20
=CE=A0=CF=81=CF=89=CF=84=CE=B1=CE=B3=CF=8C=CF=81=CE=B1=CF=82<BR>[http://w=
ww.macchiato.com]<BR><BR>----- Original Message -----=20
<BR>From: "Martin Duerst" &lt;duerst@w3.org&gt;<BR>To: "Keith Moore"=20
&lt;moore@cs.utk.edu&gt;; "Soobok Lee" &lt;lsb@postel.co.kr&gt;<BR>Cc: =
"Keith=20
Moore" &lt;moore@cs.utk.edu&gt;; &lt;idn@ops.ietf.org&gt;<BR>Sent: =
Thursday,=20
July 19, 2001 00:04<BR>Subject: Re: [idn] Re: Back to work (Nameprep) =
(was: Re:=20
Just send UTF-8 with nameprep (was: RE: [idn] Reality Check)) =
<BR><BR><BR>&gt;=20
At 11:10 01/07/18 -0400, Keith Moore wrote:<BR>&gt; &gt; &gt; Now, let's =
think=20
about another case of&nbsp;&nbsp; all-Greek "oo.com" and =
all-Latin<BR>&gt; &gt;=20
&gt; "oo.com":<BR>&gt; &gt; &gt; Either of the two consists of scripts =
from only=20
single character sets.<BR>&gt; &gt; &gt; But the two still look very =
similiar.=20
Do you have any good idea about <BR>&gt; &gt; this ?<BR>&gt; =
&gt;<BR>&gt;=20
&gt;first, how likely is this in practice that a label of all Greek=20
letters<BR>&gt; &gt;will accidentally collide with a label of all Latin=20
letters?&nbsp;&nbsp; (as opposed<BR>&gt; &gt;to a deliberate =
collision)<BR>&gt;=20
<BR>&gt; Very low for lower case. Between Latin and Greek, or Cyrillic =
and=20
Greek,<BR>&gt; it's only the 'o'.<BR>&gt; Between Latin and Cyrillic, =
it's the=20
'a', 'e', 'o', 'p', 'c', 'y', 'x',<BR>&gt; plus 's', 'i', and 'j' in =
some=20
languages.<BR>&gt; <BR>&gt; For upper-case, it's more. =
Regards,&nbsp;&nbsp;=20
Martin.<BR>&gt; <BR>&gt; <BR>&gt; <BR>&gt; &gt;for second-level domains =
at=20
least, and for some third-level domains,<BR>&gt; &gt;it would make sense =
for the=20
registry to disallow labels whose appearances<BR>&gt; &gt;collide with =
all-ASCII=20
labels.<BR>&gt; <BR>&gt; Most probably yes.<BR>&gt; <BR>&gt; <BR>&gt; =
&gt;there=20
are already some such rules in place<BR>&gt; &gt;even for ASCII, these =
would=20
just be extended.<BR>&gt; <BR>&gt; Can you tell me more about these, or =
give=20
some pointer?<BR>&gt; <BR>&gt; Regards,&nbsp;&nbsp; Martin.<BR>&gt; =
<BR>&gt;=20
</FONT></DIV></BODY></HTML>

------=_NextPart_000_00B9_01C1102B.B77B6500--




From owner-idn@ops.ietf.org  Thu Jul 19 12:22:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA05763
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 12:22:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NGFc-000LhA-00
	for idn-data@psg.com; Thu, 19 Jul 2001 09:02:08 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NGFc-000Lh3-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 09:02:08 -0700
Received: from CLASSIC.viagenie.qc.ca ([128.107.245.168])
	by jazz.viagenie.qc.ca (Viagenie/8.11.0) with ESMTP id f6JGNO118120;
	Thu, 19 Jul 2001 12:23:24 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010719114902.02ea6358@mail.viagenie.qc.ca>
X-Sender: blanchet@mail.viagenie.qc.ca
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 19 Jul 2001 12:03:07 -0400
To: idn@ops.ietf.org
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: [idn] new list of wg documents and next steps
Cc: jseng@pobox.org.sg
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hi,
	As stated previously, July 14th was the deadline for showing core of 
interest for wg documents. The wg web page (http://www.i-d-n.net#docpool) 
now contains the list of documents that showed core of interest (7 people 
supporting). The IETF secretariat has been requested to change the status 
of the other documents to be non-wg documents, so they will not be shown on 
the IETF idn wg web page 
(http://www.ietf.org/html.charters/idn-charter.html).  But the wg web page 
(http://www.i-d-n.net) will keep track of all documents related to idn. Any 
new document that shows core of interest will be added to the list of the 
wg documents.

This process is to help reaching concensus, there is no implicit judgement 
on the value of the documents.

The list of wg documents is now:
  draft-ietf-idn-requirements-08.txt
  draft-ietf-idn-idna-02.txt
  draft-ietf-idn-nameprep-03.txt
  draft-ietf-idn-dude-02.txt
  draft-ietf-idn-aceid-02.txt
  draft-ietf-idn-jpchar-01.txt
  draft-ietf-idn-ace-eval-jp-00.txt
  draft-ietf-idn-mace-01.txt
  draft-ietf-idn-uname-01.txt
  draft-ietf-idn-tsconv-00.txt
  draft-ietf-idn-udns-02.txt
  draft-costello-idn-amc-ace-z-00.txt

Note that the focus of this process is for documents that would be 
eventually pushed as standard track documents (i.e. protocol 
documents).  Informational documents do not need to be in that list for now 
to be considered (for example, the requirements documents will be subject 
to a final wg last call).

We can try, with some approximation, to categorize the wg documents in the 
following categories:

a) Matching
  draft-ietf-idn-nameprep-03.txt
  draft-ietf-idn-jpchar-01.txt
  draft-ietf-idn-tsconv-00.txt

b) Encoding
  draft-ietf-idn-dude-02.txt
  draft-ietf-idn-mace-01.txt
  draft-costello-idn-amc-ace-z-00.txt

c) Protocol
  draft-ietf-idn-idna-02.txt
  draft-ietf-idn-uname-01.txt
  draft-ietf-idn-udns-02.txt

d) Informational (no action to be taken for now)
  draft-ietf-idn-aceid-02.txt
  draft-ietf-idn-ace-eval-jp-00.txt

e) Informational (going to RFC informational)
  draft-ietf-idn-requirements-08.txt

The authors of documents in each category (as well as authors of the other 
documents not listed here) should discuss about converging to one document 
or to agree on one proposal.  Deadline is August 3th with a document that 
would be discussed during the idn wg meeting in London.  Marc Blanchet is 
happy to provide a majordomo specific mailing list to help the groups reach 
concensus, just drop me an email.

We hope to have wg concensus on the main topics during the London meeting.

James & Marc.

PS. I haven't updated the i-d-n web page with all the  internet-drafts sent 
recently. Should be done by tomorrow.







From owner-idn@ops.ietf.org  Thu Jul 19 12:34:20 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA07479
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 12:34:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NGPN-000M2q-00
	for idn-data@psg.com; Thu, 19 Jul 2001 09:12:13 -0700
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NGPM-000Lya-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 09:12:12 -0700
Received: from [24.252.219.84] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 180142; Wed, 18 Jul 2001 11:10:22 -0500
Message-ID: <3B57069A.B0901390@ehsco.com>
Date: Thu, 19 Jul 2001 11:11:06 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>
CC: Martin Duerst <duerst@w3.org>, "Adam M. Costello" <amc@cs.berkeley.edu>,
        idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <20010719011709.3228.qmail@cr.yp.to>
	 <4.2.0.58.J.20010719163929.039b4100@sh.w3.mag.keio.ac.jp> <1685871.995558087@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> I.e. the problem with using non-ascii in the labels in DNS, is that
> it is really easy to get what I would call leakage into the
> application layer protocols which can not handle other characters
> than ASCII.

Will you *PLEASE* stop saying this! The use of separate APIs and message
types prevents this from happening.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Thu Jul 19 12:34:21 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA07493
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 12:34:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NGML-000LsA-00
	for idn-data@psg.com; Thu, 19 Jul 2001 09:09:05 -0700
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NGMK-000Lr8-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 09:09:04 -0700
Received: from [24.252.219.84] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 180140; Wed, 18 Jul 2001 11:07:14 -0500
Message-ID: <3B5705DE.E7913FC8@ehsco.com>
Date: Thu, 19 Jul 2001 11:07:58 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Martin Duerst <duerst@w3.org>, Dave Crocker <dhc@dcrocker.net>,
        idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <200107191309.JAA03205@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> I think server products will be upgraded quickly, but in many
> parts of the world they will be deployed slowly.  It's not just
> the ISPs that need to deploy new servers for this to work;
> it's anyone that runs a DNS cache.

Where are these caches?

Half are on the back-end, half are at the client. Which half won't
upgrade? Which half doesn't want the technology they are trying to use?

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Thu Jul 19 12:46:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA09124
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 12:46:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NG8s-000LNn-00
	for idn-data@psg.com; Thu, 19 Jul 2001 08:55:10 -0700
Received: from [209.187.148.217] (helo=P2)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NG8r-000LMv-00; Thu, 19 Jul 2001 08:55:09 -0700
Date: Thu, 19 Jul 2001 11:55:04 -0400
From: John C Klensin <klensin@jck.com>
To: lucid@epa.secret.org
cc: idn@ops.ietf.org
Subject: RE: [idn] Debunking the ACE myth
Message-ID: <11052207.995543704@localhost>
In-Reply-To: <Pine.BSF.4.33.0107191119470.61325-100000@epa.secret.org>
References:  <Pine.BSF.4.33.0107191119470.61325-100000@epa.secret.
 org>
X-Mailer: Mulberry/2.1.0b2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Thursday, 19 July, 2001 11:22 -0400 lucid@epa.secret.org
wrote:

> Getting ISPs to upgrade to DNS that supports UTF-8 is simple.
> Patch BIND now, wait for the next remote root exploit which is
> followed by a worm.

Sigh.

Folks, this is important.  Let's get real.

Unless recent consolidations have changed things dramatically --
and in directions other than the one my experience would
predict-- there are basically two kinds of ISPs: the ones who
are very careful and conservative about infrastructure software
updates and the ones who don't expect to be in business for much
longer (a few manage to fall into both categories, of course).

Bug-fixing patches to BIND (or anything else) that address a
security problem are installed quickly iff their content is
addressed specifically to that problem.  If they contain a lot
of irrelevant stuff, the software providers take a lot of flak.
Complete new versions that ISPs are expected to install on the
basis that it will be good for them, but without specifics, get
even more resistance.  (Those closer to BIND maintenance cycles
should confirm this or tell me I'm crazy.)

In general, anything that requires ISPs to make changes to
servers that impact all of their users or customers (and, if
they are in the hosting business, customers of their customers)
is going to be deployed when it is clearly in the ISP's business
interests, and/or after very careful and leisurely testing, or
never.

If you want fast deployment, select something that doesn't
require ISPs to make changes.  There may be fewer of them than
there are end users, but the latter can much more easily decide
to install software upgrades that meet their particular
perceived needs.  And don't depend on tricking the ISPs into
installing something -- the good ones are hard to trick and they
collectively represent a very large portion of the marketplace.

    john




From owner-idn@ops.ietf.org  Thu Jul 19 12:47:25 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA09394
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 12:47:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NGTQ-000MAX-00
	for idn-data@psg.com; Thu, 19 Jul 2001 09:16:24 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NGTP-000MAO-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 09:16:23 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id MAA04593;
        Thu, 19 Jul 2001 12:16:17 -0400 (EDT)
Message-Id: <200107191616.MAA04593@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: Keith Moore <moore@cs.utk.edu>, Martin Duerst <duerst@w3.org>,
        Dave Crocker <dhc@dcrocker.net>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth 
In-reply-to: Your message of "Thu, 19 Jul 2001 11:07:58 CDT."
             <3B5705DE.E7913FC8@ehsco.com> 
Date: Thu, 19 Jul 2001 12:16:17 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > I think server products will be upgraded quickly, but in many
> > parts of the world they will be deployed slowly.  It's not just
> > the ISPs that need to deploy new servers for this to work;
> > it's anyone that runs a DNS cache.
> 
> Where are these caches?
> 
> Half are on the back-end, half are at the client. Which half won't
> upgrade? Which half doesn't want the technology they are trying to use?

your network people must be more responsive than the ones I'm used to.

Keith



From owner-idn@ops.ietf.org  Thu Jul 19 12:52:17 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA10404
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 12:52:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NGdM-000MYK-00
	for idn-data@psg.com; Thu, 19 Jul 2001 09:26:40 -0700
Received: from epa.secret.org ([206.220.140.150] ident=0)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NGdL-000MY9-01
	for idn@ops.ietf.org; Thu, 19 Jul 2001 09:26:39 -0700
Received: from localhost (lucid@localhost)
	by epa.secret.org (8.9.3/8.9.1) with ESMTP id MAA63179;
	Thu, 19 Jul 2001 12:24:08 -0400 (EDT)
Date: Thu, 19 Jul 2001 12:24:08 -0400 (EDT)
From: <lucid@epa.secret.org>
To: John C Klensin <klensin@jck.com>
cc: <idn@ops.ietf.org>
Subject: RE: [idn] Debunking the ACE myth
In-Reply-To: <11052207.995543704@localhost>
Message-ID: <Pine.BSF.4.33.0107191201410.61325-100000@epa.secret.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


Actually, I should have been more clear.
There are currently three major versions of BIND
in common usage. 4.x, 8.x, and 9.1.x None of which
will be patched for new features. The 9.x series is still under
evaluation at several ISPs that I know of. If there are features that
need to go into the DNS server, I would think the best time to get them
in is now, before upgrades to 9.x have been completed. The security issue
will just push things forward, the real issue is 9.x is on the upgrade
schedule.

-Bill

On Thu, 19 Jul 2001, John C Klensin wrote:
> In general, anything that requires ISPs to make changes to
> servers that impact all of their users or customers (and, if
> they are in the hosting business, customers of their customers)
> is going to be deployed when it is clearly in the ISP's business
> interests, and/or after very careful and leisurely testing, or
> never.
>
> If you want fast deployment, select something that doesn't
> require ISPs to make changes.  There may be fewer of them than
> there are end users, but the latter can much more easily decide
> to install software upgrades that meet their particular
> perceived needs.  And don't depend on tricking the ISPs into
> installing something -- the good ones are hard to trick and they
> collectively represent a very large portion of the marketplace.
>
>     john
>
>




From owner-idn@ops.ietf.org  Thu Jul 19 13:10:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA12987
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 13:10:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NGsy-000NAJ-00
	for idn-data@psg.com; Thu, 19 Jul 2001 09:42:48 -0700
Received: from [209.187.148.217] (helo=P2)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NGsx-000NAD-00; Thu, 19 Jul 2001 09:42:47 -0700
Date: Thu, 19 Jul 2001 12:42:46 -0400
From: John C Klensin <klensin@jck.com>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: lucid@epa.secret.org, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
Message-ID: <13913852.995546566@P2>
In-Reply-To: <3B570AAB.5D7E0B92@ehsco.com>
References:  <3B570AAB.5D7E0B92@ehsco.com>
X-Mailer: Mulberry/2.1.0b2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Thursday, 19 July, 2001 11:28 -0500 "Eric A. Hall"
<ehall@ehsco.com> wrote:

>> Folks, this is important.  Let's get real.
> 
> Yes let's.
> 
> How many users of HTTP 1.1 didn't upgrade?
> 
> How many users of LDAP v3 didn't upgrade?
> 
> Give me a break. The people that want it will upgrade. Duh.

I think that was my point.  The people that want "it" will
upgrade, if they can.   The ISPs who run the servers may not see
"want" the same way.   So, once again, if you want rapid
deployment, pick a solution that leaves the upgrading in the
hands of those who need the functionality --the users in this
case-- rather than entertaining fantasies about what ISPs and
other server operators will do.

   john




From owner-idn@ops.ietf.org  Thu Jul 19 13:11:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA13153
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 13:11:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NGgB-000MhO-00
	for idn-data@psg.com; Thu, 19 Jul 2001 09:29:35 -0700
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NGgA-000Maz-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 09:29:34 -0700
Received: from [24.252.219.84] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 180146; Wed, 18 Jul 2001 11:27:44 -0500
Message-ID: <3B570AAB.5D7E0B92@ehsco.com>
Date: Thu, 19 Jul 2001 11:28:28 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: John C Klensin <klensin@jck.com>
CC: lucid@epa.secret.org, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <Pine.BSF.4.33.0107191119470.61325-100000@epa.secret.
	 org> <11052207.995543704@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> Folks, this is important.  Let's get real.

Yes let's.

How many users of HTTP 1.1 didn't upgrade?

How many users of LDAP v3 didn't upgrade?

Give me a break. The people that want it will upgrade. Duh.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Thu Jul 19 13:15:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA13645
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 13:15:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NH0q-000NOK-00
	for idn-data@psg.com; Thu, 19 Jul 2001 09:50:56 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NH0o-000NOC-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 09:50:55 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id MAA05023;
        Thu, 19 Jul 2001 12:50:49 -0400 (EDT)
Message-Id: <200107191650.MAA05023@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>,
        Martin Duerst <duerst@w3.org>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth 
In-reply-to: Your message of "Thu, 19 Jul 2001 11:11:06 CDT."
             <3B57069A.B0901390@ehsco.com> 
Date: Thu, 19 Jul 2001 12:50:49 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > I.e. the problem with using non-ascii in the labels in DNS, is that
> > it is really easy to get what I would call leakage into the
> > application layer protocols which can not handle other characters
> > than ASCII.
> 
> Will you *PLEASE* stop saying this! The use of separate APIs and message
> types prevents this from happening.

will you *PLEASE* stop making bogus assertions like this?

in most cases, it's simply not feasible to separate the use of IDNs from 
the use of ASCII DNS names and negotiate or convert at the boundaries.

for instance, in the particular case of email, we tried that with 
8-bit-SMTP and it failed miserably.

Keith



From owner-idn@ops.ietf.org  Thu Jul 19 13:23:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA15430
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 13:23:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NHC6-000Nr8-00
	for idn-data@psg.com; Thu, 19 Jul 2001 10:02:34 -0700
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NHC5-000NpI-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 10:02:33 -0700
Received: from [24.252.219.84] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 180155; Wed, 18 Jul 2001 12:00:43 -0500
Message-ID: <3B571267.6D364B08@ehsco.com>
Date: Thu, 19 Jul 2001 12:01:27 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>,
        Martin Duerst 
	<duerst@w3.org>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <200107191650.MAA05023@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> in most cases, it's simply not feasible to separate the use of IDNs
> from the use of ASCII DNS names and negotiate or convert at the
> boundaries.

Give me one example where it fails. Just one.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Thu Jul 19 13:25:04 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA15704
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 13:24:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NH8l-000NlI-00
	for idn-data@psg.com; Thu, 19 Jul 2001 09:59:07 -0700
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NH8k-000NjB-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 09:59:06 -0700
Received: from [24.252.219.84] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 180154; Wed, 18 Jul 2001 11:57:16 -0500
Message-ID: <3B571197.9831A97@ehsco.com>
Date: Thu, 19 Jul 2001 11:57:59 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: John C Klensin <klensin@jck.com>
CC: lucid@epa.secret.org, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <3B570AAB.5D7E0B92@ehsco.com> <13913852.995546566@P2>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> So, once again, if you want rapid
> deployment, pick a solution that leaves the upgrading in the
> hands of those who need the functionality --the users in this
> case-- rather than entertaining fantasies about what ISPs and
> other server operators will do.

I am getting very frustrated over these specious claims. Sorry if it comes
out harsh. Let's think this through though, please.

1) We have the owners and operators of IDNS. They will want to
   upgrade their servers to get the full benefits of an UTF-8
   IDN approach. The only operators who are not likely to
   upgrade immediately are speculators; they won't be getting
   much traffic anyway.

2) We have the corporate user community. They will want to
   upgrade sooner or later, as business dictates. For those
   orgs who maintain an international presence, this will be
   sooner rather than later. For those orgs who are purely
   local, and who never ever do anything in any international
   market, later will be fine (ACE will work for the 1% of
   domain names which are IDN). Not a problem.

3) We have the *international* end-user community and their
   ISPs. What ISPs in any foreign market is going to insist
   that their end-users must continue using ASCII??????????

4) We have domestic ISPs. See #2 above. Some of these will
   be upgrading sooner than others. For the lazy xenophobes
   who think the rest of the world should just learn English,
   they may never upgrade. Chances are they aren't upgrading
   much of anything else, either. They will continue using
   ACE, until they have no customers left.

If we use absurd numbers and give each of those camps 25% share, then we
are looking at 75% cache upgrades. More importantly, we are looking at
100% penetration in the markets which are affected by the technology.

Who gives a fsck if the lazy xenophobes in the other 25% don't upgrade?
They aren't involved with international markets anyway.

Also keep in mind that once the application protocols start to embrace
UTF-8 IDNs, that the bar will raise further.

It would also be a good thing for the Internet for such an upgrade to be
required. Note that it isn't really required -- lazy xenophobes can
continue to use ACE -- but that it is required for maximum efficiency and
also likely to be required for future protocols.

Upgrading the servers is not a preventative issue. Please, let's drop 
this FUD and move on.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Thu Jul 19 13:32:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17541
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 13:32:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NHHF-000O1f-00
	for idn-data@psg.com; Thu, 19 Jul 2001 10:07:53 -0700
Received: from [209.187.148.217] (helo=P2)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NHHE-000O1Y-00; Thu, 19 Jul 2001 10:07:53 -0700
Date: Thu, 19 Jul 2001 13:07:51 -0400
From: John C Klensin <klensin@jck.com>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
Message-ID: <15419447.995548071@P2>
In-Reply-To: <3B571197.9831A97@ehsco.com>
References:  <3B571197.9831A97@ehsco.com>
X-Mailer: Mulberry/2.1.0b2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Thursday, 19 July, 2001 11:57 -0500 "Eric A. Hall"
<ehall@ehsco.com> wrote:

> I am getting very frustrated over these specious claims. Sorry
> if it comes out harsh. Let's think this through though, please.
> 
> 1) We have the owners and operators of IDNS. They will want to
>    upgrade their servers to get the full benefits of an UTF-8
>...

Eric,

As in our earlier (offline) conversation about use of TCP
options to negotiate the use of alternate character sets, it is
clear that our assumptions and experience are enough different
that we are not communicating well and, more important, unlikely
to convince each other of anything.   I see the landscape
differently than you do.  I have a certain amount of experience,
with and in major ISPs, that conditions my vision.   You can
reasonably disagree with either the value of my experience or my
conclusions (as I disagree with your conclusions).  But even
categorizing my experience and/or conclusions as "specious" is,
IMO, probably a little much.

regards,
    john




From owner-idn@ops.ietf.org  Thu Jul 19 13:56:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA25018
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 13:56:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NHey-000Okl-00
	for idn-data@psg.com; Thu, 19 Jul 2001 10:32:24 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NHeu-000Oka-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 10:32:22 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f6JHTtd71079;
	Thu, 19 Jul 2001 13:29:55 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107191729.f6JHTtd71079@nic-naa.net>
To: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
cc: idn@ops.ietf.org, jseng@pobox.org.sg, brunner@nic-naa.net
Subject: Re: [idn] new list of wg documents and next steps 
In-Reply-To: Your message of "Thu, 19 Jul 2001 12:03:07 EDT."
             <5.1.0.14.1.20010719114902.02ea6358@mail.viagenie.qc.ca> 
Date: Thu, 19 Jul 2001 13:29:55 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Marc,

draft-ietf-idn-requirements-08.txt, statement of scope, contains this:

	It is recommended that solutions not necessarily be within
	the DNS itself, but could be a layer interjected between the
	application and the DNS.

While this may be the most popular point of view, it isn't appropriate
to place a recommendation prior to completion of requirements gathering.

I've mentioned this before, but the editors haven't made any change or
comment.

I'd like to know if there is working group consensus on the inclusion of
any recommendation in a working group requirements draft. It seems novel
to me.

Eric



From owner-idn@ops.ietf.org  Thu Jul 19 13:59:15 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA25894
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 13:59:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NHf3-000Ol3-00
	for idn-data@psg.com; Thu, 19 Jul 2001 10:32:29 -0700
Received: from epa.secret.org ([206.220.140.150] ident=0)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NHf2-000Okq-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 10:32:28 -0700
Received: from localhost (lucid@localhost)
	by epa.secret.org (8.9.3/8.9.1) with ESMTP id NAA63955;
	Thu, 19 Jul 2001 13:29:55 -0400 (EDT)
Date: Thu, 19 Jul 2001 13:29:55 -0400 (EDT)
From: *click* <lucid@epa.secret.org>
To: John C Klensin <klensin@jck.com>
cc: "Eric A. Hall" <ehall@ehsco.com>, <idn@ops.ietf.org>
Subject: Re: [idn] Debunking the ACE myth
In-Reply-To: <13913852.995546566@P2>
Message-ID: <Pine.BSF.4.33.0107191313100.61325-100000@epa.secret.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk



On Thu, 19 Jul 2001, John C Klensin wrote:
> I think that was my point.  The people that want "it" will
> upgrade, if they can.   The ISPs who run the servers may not see
> "want" the same way.   So, once again, if you want rapid
> deployment, pick a solution that leaves the upgrading in the
> hands of those who need the functionality --the users in this
> case-- rather than entertaining fantasies about what ISPs and
> other server operators will do.

I am in operations, I have spoken with the people who decide when
DNS servers get upgraded at a few regional ISPs, this is not a fantasy.

-Bill




From owner-idn@ops.ietf.org  Thu Jul 19 14:04:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA27669
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 14:04:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NHrn-000OwM-00
	for idn-data@psg.com; Thu, 19 Jul 2001 10:45:39 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NHrm-000OwA-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 10:45:38 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA05147;
        Thu, 19 Jul 2001 13:08:22 -0400 (EDT)
Message-Id: <200107191708.NAA05147@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: Keith Moore <moore@cs.utk.edu>,
        Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>,
        Martin Duerst <duerst@w3.org>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth 
In-reply-to: Your message of "Thu, 19 Jul 2001 12:01:27 CDT."
             <3B571267.6D364B08@ehsco.com> 
Date: Thu, 19 Jul 2001 13:08:21 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Give me one example where it fails. Just one.

I'll give two.

1. an email message gets delivered to a flat file which is read by 
a user agent.  the process that delivers the message has no idea
whether the user agent can support native IDNs or not, and this
is subject to change at any time. 

2. an HTML document is saved in a flat file on a disk.  the process
that saves the file has no idea whether every browser that will ever
be asked to read that file can properly support IDNs.

and you're dreaming if you think that folks are going to add
explicit IDN negotiation even into those protocols that have
the ability to negotiate options.  option negotiation 
tends to add complexity and additional failure modes that 
make diagnosing and fixing bugs more difficult (because they
increase the complexity of the case analysis). the more
options you add to a protocol, the worse it gets.
on-the-fly format conversion adds it own set of problems.

Ketih



From owner-idn@ops.ietf.org  Thu Jul 19 14:11:09 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA29950
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 14:11:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NHxB-000P0v-00
	for idn-data@psg.com; Thu, 19 Jul 2001 10:51:13 -0700
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NHxA-000P07-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 10:51:12 -0700
Received: from [24.252.219.84] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 180170; Wed, 18 Jul 2001 12:49:23 -0500
Message-ID: <3B571DCF.C6194D12@ehsco.com>
Date: Thu, 19 Jul 2001 12:50:07 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>,
        Martin Duerst 
	<duerst@w3.org>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <200107191708.NAA05147@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> > Give me one example where it fails. Just one.
> 
> I'll give two.

You gave me two application failures, not protocol failures.

Try again.

> 1. an email message gets delivered to a flat file which is read by
> a user agent.  the process that delivers the message has no idea
> whether the user agent can support native IDNs or not, and this
> is subject to change at any time.

You're assuming that the headers won't have to signify content, and that
the SMTP folk won't consider this in protocol design. Considering the
store-and-forward nature of mail, this is absurd.

> 2. an HTML document is saved in a flat file on a disk.  the process
> that saves the file has no idea whether every browser that will ever
> be asked to read that file can properly support IDNs.

Compliant HTML has a version tag.

> on-the-fly format conversion adds it own set of problems.

Such as?

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Thu Jul 19 14:33:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA06602
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 14:33:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NIFe-000PYN-00
	for idn-data@psg.com; Thu, 19 Jul 2001 11:10:18 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NIFb-000PYF-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 11:10:17 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA05668;
        Thu, 19 Jul 2001 14:09:43 -0400 (EDT)
Message-Id: <200107191809.OAA05668@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: Keith Moore <moore@cs.utk.edu>,
        Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>,
        Martin Duerst <duerst@w3.org>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth 
In-reply-to: Your message of "Thu, 19 Jul 2001 12:50:07 CDT."
             <3B571DCF.C6194D12@ehsco.com> 
Date: Thu, 19 Jul 2001 14:09:43 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > > Give me one example where it fails. Just one.
> > 
> > I'll give two.
> 
> You gave me two application failures, not protocol failures.

delivering to a file is a protocol.  not all protocols involve
direct interaction between the producer and the consumer.
 
> > 1. an email message gets delivered to a flat file which is read by
> > a user agent.  the process that delivers the message has no idea
> > whether the user agent can support native IDNs or not, and this
> > is subject to change at any time.
> 
> You're assuming that the headers won't have to signify content, and that
> the SMTP folk won't consider this in protocol design. Considering the
> store-and-forward nature of mail, this is absurd.

Considering the store-and-forward nature of mail, it's absurd to think
that you can use message headers for interactive feature negotiation.

> > 2. an HTML document is saved in a flat file on a disk.  the process
> > that saves the file has no idea whether every browser that will ever
> > be asked to read that file can properly support IDNs.
> 
> Compliant HTML has a version tag.

Version tags don't help if the browser doesn't understand the version.
(we realized that MIME-Version was essentially useless only after
RFC 1341 made it mandatory.  by the time we realized this, it was
too late to deprecate it - too many UAs refused to recognize MIME without it.)

> > on-the-fly format conversion adds it own set of problems.
> 
> Such as?

It introduces errors that are difficult to trace and to fix.
It adds complexity (for example into MTAs) that shouldn't be
modifying their payloads.  It forces intermediaries to be aware
of their payloads' formats when those formats should be transparent.

Keith



From owner-idn@ops.ietf.org  Thu Jul 19 14:47:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA10297
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 14:47:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NIMf-000Pf5-00
	for idn-data@psg.com; Thu, 19 Jul 2001 11:17:33 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NIMe-000Pek-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 11:17:32 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA05723;
        Thu, 19 Jul 2001 14:12:01 -0400 (EDT)
Message-Id: <200107191812.OAA05723@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: John C Klensin <klensin@jck.com>, lucid@epa.secret.org, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth 
In-reply-to: Your message of "Thu, 19 Jul 2001 11:28:28 CDT."
             <3B570AAB.5D7E0B92@ehsco.com> 
Date: Thu, 19 Jul 2001 14:12:01 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > Folks, this is important.  Let's get real.
> 
> Yes let's.
> 
> How many users of HTTP 1.1 didn't upgrade?
> 
> How many users of LDAP v3 didn't upgrade?

lots of folks are still using HTTP 1.0 and LDAP v2.
HTTP at least took great pains to allow interoperation between the two.

and changing either HTTP or LDAP doesn't break most of the other
protocols on the Internet.

Keith



From owner-idn@ops.ietf.org  Thu Jul 19 14:58:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA13889
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 14:58:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NITx-000PmD-00
	for idn-data@psg.com; Thu, 19 Jul 2001 11:25:05 -0700
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NITw-000PkY-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 11:25:04 -0700
Received: from [24.252.219.84] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 180191; Wed, 18 Jul 2001 13:23:15 -0500
Message-ID: <3B5725BE.BB704BE3@ehsco.com>
Date: Thu, 19 Jul 2001 13:23:59 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: John C Klensin <klensin@jck.com>, lucid@epa.secret.org, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <200107191812.OAA05723@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> lots of folks are still using HTTP 1.0 and LDAP v2.

Because they didn't find the upgrade necessary/compelling/whatever. That
is exactly the point.

> and changing either HTTP or LDAP doesn't break most of the other
> protocols on the Internet.

Neither does the dual-mode approach

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Thu Jul 19 15:01:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA14633
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 15:01:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NISs-000PkW-00
	for idn-data@psg.com; Thu, 19 Jul 2001 11:23:58 -0700
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NISr-000PjX-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 11:23:57 -0700
Received: from [24.252.219.84] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 180189; Wed, 18 Jul 2001 13:22:07 -0500
Message-ID: <3B57257B.57550DF5@ehsco.com>
Date: Thu, 19 Jul 2001 13:22:51 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>,
        Martin Duerst 
	<duerst@w3.org>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <200107191809.OAA05668@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> delivering to a file is a protocol.  not all protocols involve
> direct interaction between the producer and the consumer.

If there is no direct interaction, there has to be an out-of-band
negotiation. However you do this is entirely up to you. Until you come up
with a mechanism that works reliably however, I would suggest that SMTP
should not be upgraded.

The dual-mode model helps you deliver on whatever you decide you can|wan't
to do. It won't break anything on it's own.

The example you cited is a broken SMTP implementation, and has absolutely
nothing to do with the DNS model.

> Version tags don't help if the browser doesn't understand the version.
> (we realized that MIME-Version was essentially useless only after
> RFC 1341 made it mandatory.  by the time we realized this, it was
> too late to deprecate it - too many UAs refused to recognize MIME
> without it.)

Thanks for proving my point; the only time that there will be bleed-over
is when the applications fail. You can use your MIME experience to prevent
this from happening again.

The dual-mode protocol won't break anything. Applications that implement
it poorly will.

> > > on-the-fly format conversion adds it own set of problems.
> >
> > Such as?
> 
> It introduces errors that are difficult to trace and to fix.

ACE even moreso.

> It adds complexity (for example into MTAs) that shouldn't be
> modifying their payloads. It forces intermediaries to be aware
> of their payloads' formats when those formats should be transparent.

If you want to insist that MTAs should track message formats on a
per-destination basis, that is your call.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Thu Jul 19 15:35:44 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA25473
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 15:35:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NJ2U-0000hg-00
	for idn-data@psg.com; Thu, 19 Jul 2001 12:00:46 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NJ2R-0000hR-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 12:00:44 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA06276;
        Thu, 19 Jul 2001 15:00:07 -0400 (EDT)
Message-Id: <200107191900.PAA06276@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: Keith Moore <moore@cs.utk.edu>,
        Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>,
        Martin Duerst <duerst@w3.org>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth 
In-reply-to: Your message of "Thu, 19 Jul 2001 13:22:51 CDT."
             <3B57257B.57550DF5@ehsco.com> 
Date: Thu, 19 Jul 2001 15:00:07 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > delivering to a file is a protocol.  not all protocols involve
> > direct interaction between the producer and the consumer.
> 
> If there is no direct interaction, there has to be an out-of-band
> negotiation. 

no there doesn't.

> However you do this is entirely up to you. Until you come up
> with a mechanism that works reliably however, I would suggest that SMTP
> should not be upgraded.

and this is one of the reasons why introduction of IDNs into email
will not be dependent on an SMTP option.

> The dual-mode model helps you deliver on whatever you decide you can|wan't
> to do. It won't break anything on it's own.

it will break things merely because it requires additional software changes.
changes invariably introduce new bugs.

> The example you cited is a broken SMTP implementation, and has absolutely
> nothing to do with the DNS model.

precisely! it's an example of why dual mode models cause problems - 
because implementations will fail to implement them correctly.

> > Version tags don't help if the browser doesn't understand the version.
> > (we realized that MIME-Version was essentially useless only after
> > RFC 1341 made it mandatory.  by the time we realized this, it was
> > too late to deprecate it - too many UAs refused to recognize MIME
> > without it.)
> 
> Thanks for proving my point; the only time that there will be bleed-over
> is when the applications fail. You can use your MIME experience to prevent
> this from happening again.

nothing in the MIME experience helps us to keep applications from being
buggy.

> The dual-mode protocol won't break anything. Applications that implement
> it poorly will.

poorly-implemented applications are a given, I'm afraid.
and the more complex we require them to be, the more likely they are to
be buggy.

Keith



From owner-idn@ops.ietf.org  Thu Jul 19 15:59:44 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA02948
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 15:59:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NJKZ-0001Ho-00
	for idn-data@psg.com; Thu, 19 Jul 2001 12:19:27 -0700
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NJKY-0001EV-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 12:19:26 -0700
Received: from [24.252.219.84] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 180201; Wed, 18 Jul 2001 14:17:32 -0500
Message-ID: <3B573276.B1E7CC09@ehsco.com>
Date: Thu, 19 Jul 2001 14:18:15 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>,
        Martin Duerst 
	<duerst@w3.org>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <200107191900.PAA06276@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> > The dual-mode model helps you deliver on whatever you decide you
> > can|wan't to do. It won't break anything on it's own.
> 
> it will break things merely because it requires additional software
> changes. changes invariably introduce new bugs.

> poorly-implemented applications are a given, I'm afraid.
> and the more complex we require them to be, the more likely they are to
> be buggy.

These are all arguments against ACE transliteration (and IPv6 and just
about everything else for that matter).

The only way that UTF-8 IDNs will get into the legacy path is if a
particular implementation goes out of its way to use them where it
shouldn't. It will have to explicitly call the new API and then explicitly
pass data that is not supported by the application protocol. This scenario
is completely unrealistic.

You are essentially arguing that if an application makes two unrealistic
errors then UTF-8 IDNs will break the application.

Your initial comment was:

 | in most cases, it's simply not feasible to separate the use of IDNs
 | from the use of ASCII DNS names and negotiate or convert at the
 | boundaries.

You have yet to prove this point. On the contrary, I have shown that it
requires explicit effort for problems to occur, and even then the problems
are not due to anything inherent with the protocol itself.

Please, let's drop this FUD and move on.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Thu Jul 19 16:02:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA03685
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 16:02:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NJEl-00013v-00
	for idn-data@psg.com; Thu, 19 Jul 2001 12:13:27 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NJEh-00013e-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 12:13:24 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f6JJBNd73567
	for <idn@ops.ietf.org>; Thu, 19 Jul 2001 15:11:23 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107191911.f6JJBNd73567@nic-naa.net>
To: idn@ops.ietf.org
Subject: Re: [idn] Re: language scripts classified
Date: Thu, 19 Jul 2001 15:11:23 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Soobok,

I was looking over an Indian list's traffic this morning and found this,
from the newpaper of record in Canada. The article understates a problem
with the residential school system, but that is another subject. It does
contain a useful newspaper-level survey of the state of languages in the
northern third of North America, and offer some numbers not found in the
Unicode Consortrum's compendium of things useful to printer vendors.

There are some surprising numbers.

Eric

Subject: Fw: Aboriginal languages to vanish, report says
Date: Wed, 20 Jun 2001 12:33:18 -0700
...
http://www.globeandmail.com

------- Forwarded Message

The Globe and Mail, Wednesday, June 20, 2001

Aboriginal languages to vanish, report says

By Sean Fine


His people have entered the modern communications era with their own Web 
site -- but their language is on the brink of extinction.

"In everyday use it's already dead -- almost," said Kevin Littlelight, a 
council member of the Tsuu T'ina Nation, just southwest of Calgary,
referring to the aboriginal language known by the same name, Tsuu T'ina.
"A few people use it with their parents, the older people, but when those
people are gone, it will vanish."

At least half of the world's 6,800 languages, and perhaps as many as 90 
per cent, face a similar fate, according to the Worldwatch Institute.

It reports that half of all languages are spoken by fewer than 2,500 
people each.

In Canada, only three of 50 aboriginal languages -- Cree, Inuktitut and 
Ojibway -- have large enough populations to be considered safe. And only
about one in every four of the 800,000 people who claimed an aboriginal
identity in 1996 had an aboriginal language as their mother tongue, according
to Statistics Canada. Even fewer spoke it at home.

Not surprisingly, then, at least a dozen languages are in immediate peril, 
and 10 became extinct last century.

Around the world, war, natural disasters, the spread of more dominant 
languages such as Chinese, Russian and English, and government bans on
language have contributed to the death of mother tongues.

"In some ways, it's similar to what threatens species," said Payal Sampat, 
a Worldwatch researcher who wrote about the topic for the institute's
May-June magazine.

Tsuu T'ina means "a great number of people," but the reserve (also known 
as Sarcee) has just 1,250 residents.

Of those, 40 speak the language, which has three dialects.

Mr. Littlelight said the loss of his people's language has devastating 
implications.

It endangers "our ability to think as Sarcee people," he said.

"So then when we all become English-speaking natives, we sort of belong to
the Pan-American group -- it's just a generalization of an Indian. It's like
lumping all the fishes as a fish, rather than as salmon, trout, all the pike.
We lose that individuality."

The reserve holds language classes and workshops, and is putting together 
a topical dictionary full of everyday Tsuu T'ina terms. But Mr. Littlelight,
who speaks the language "at the kindergarten level," is not optimistic.

The language's future has already been undermined by the residential 
schools that "indoctrinated" his people in the use of English (many barred
the use of native languages), the proximity to English-speaking Calgary and
an internal struggle among the Tsuu T'ina over which dialect should be
taught.

"It starts at the top with leadership," he said.

New Zealand's Maoris have been a model for indigenous peoples in preserving
their mother tongue. For instance, they have set up "language nests" --
children's centres with elders who speak their first language to those whose
parents may have lost the language, said Arok Wolvengray, a professor of
Indian languages and linguistics at the Saskatchewan Indian Federated College.

In Canada, some native groups, such as the Crees who live near James Bay 
in Quebec, are offering immersion training for children. At the Six Nations
Reserve in southern Ontario, about 500 children are enrolled in bilingual
schools teaching English-Cayuga or English-Mohawk.

"Each language has its own way of seeing the world, of dealing with the 
world," Prof. Wolvengray said. "When you lose a language, you lose that
knowledge base and that world view, and that impoverishes us a little bit."

He relates a story from the 1950s, told to him by his wife, a Cree, about 
a white boy who learned some Cree from his peers in a residential school.
In sympathy with his friends, who were not allowed to speak their language,
he spoke up in class in Cree -- only to be punished by someone placing a
tin wastebasket on his head, and then striking it.

"This shows the extremes they went to, to try and stomp out the language," 
he said of residential schools that were operated for much of this century
by Canadian churches and administered by the federal government.

Manners of speaking

Eight countries account for more than half of all languages: Papua New Guinea,
832 languages; Indonesia, 731; Nigeria, 515; India, 400; Mexico, Cameroon and
Australia, just under 300 each; and Brazil, 234.

The island of New Guinea, which Papua New Guinea shares with the Indonesian
state of Irian Jaya, is home to just 0.1 per cent of the world's population,
yet its residents speak one-sixth of all languages -- about 1,100 tongues.

More than 100 languages can be heard on the tiny archipelago of Vanuatu. It
is home to about 190,000 people.

India has 15 official languages, more than any other country.

The five most common first languages, and number of speakers: Mandarin Chinese,
885 million; Spanish, 332 million; English, 322 million; Arabic, 220 million;
Bengali, 189 million.

World of language

The following graph shows the percent of languages originating from 
different parts of the world.
Asian       32%
African     30%
Pacific     19%
American    15%
European     4%
------- End of Forwarded Message




From owner-idn@ops.ietf.org  Thu Jul 19 16:08:17 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA04506
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 16:08:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NJBS-0000vq-00
	for idn-data@psg.com; Thu, 19 Jul 2001 12:10:02 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NJBR-0000tY-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 12:10:01 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id VAA01493;
	Thu, 19 Jul 2001 21:01:28 +0200 (MET DST)
Date: Thu, 19 Jul 2001 20:46:01 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: "Eric A. Hall" <ehall@ehsco.com>, John C Klensin <klensin@jck.com>
cc: lucid@epa.secret.org, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
Message-ID: <2267944.995575561@localhost>
In-Reply-To: <3B571197.9831A97@ehsco.com>
References: <3B570AAB.5D7E0B92@ehsco.com> <13913852.995546566@P2>
 <3B571197.9831A97@ehsco.com>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA04506

--On 01-07-19 11.57 -0500 "Eric A. Hall" <ehall@ehsco.com> wrote:

> 1) We have the owners and operators of IDNS. They will want to
>    upgrade their servers to get the full benefits of an UTF-8
>    IDN approach. The only operators who are not likely to
>    upgrade immediately are speculators; they won't be getting
>    much traffic anyway.

Eric, it is sad to use the same arguments on your mail as you are using on
mine.

As evidence that you are completely wrong I take Hotmail as an example.
This site is one of the largest in the world regarding free email to people
from all over the world. It is not only something which is targeting the
US. One can even choose when registering "Hotmail på svenska" which means
"Hotmail in Swedish" in English.

Now, do you think Hotmail can handle other characters than US-ASCII in
headers (header encoding of for example my last name "Fältström")? Do you
think Hotmail can handle other characters than US-ASCII in even the body of
a message?

Let me tell you the answers: No, and No.

Is Hotmail one site which "won't be getting much traffic anyway"?

Definitly not.

Hotmail is one of the largest problems we have on the Internet at the
moment just because they (a) don't follow the standards and (b) still get
lots of usage from users.

Now, why is this an argument for my discussion about "leakage"?

Just because Hotmail which have not even implemented non-US-ASCII
characters in MIME correctly, which have been around for quite some time,
what is the chance that it will implement suddenly non-US-ASCII characters
for IDN and addresses correctly?

The reason is that software companies which mainly is based in the US don't
have the experience (the programmers don't) of using non-US-ASCII
characters and because of that the implementations are "good enough" for
the largest portion of the market of the Internet -- which is the US.

Yes, I have tried to buy software from several US companies to Sweden, and
it is hard, very hard, because there is just no understanding of what
internationalization means.

And, I in Sweden still uses almost the same script as people in the english
speaking world. We only have three more characters which are "weird". It is
MUCH worse for people which do not even use the same kind of characters.

   paf




From owner-idn@ops.ietf.org  Thu Jul 19 16:50:22 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA11550
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 16:50:21 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NKYe-00037h-00
	for idn-data@psg.com; Thu, 19 Jul 2001 13:38:04 -0700
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NKYd-00037O-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 13:38:03 -0700
Received: from [24.252.219.84] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.7)
  with ESMTP-TLS id 180217; Wed, 18 Jul 2001 15:36:13 -0500
Message-ID: <3B5744E9.DD20B63F@ehsco.com>
Date: Thu, 19 Jul 2001 15:36:57 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Martin Duerst <duerst@w3.org>
CC: "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] Re: Just send UTF-8 with nameprep
References: <20010719005402.D19841@arwen.cs.berkeley.edu> <4.2.0.58.J.20010719161607.030afe70@sh.w3.mag.keio.ac.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> > Using these IDNs to answer legacy queries will absolutely
> > definitely cause some kind of unintended consequence, and we
> > will get a lot of heat for the failure.
> 
> The chance that when a legacy resolver passes through a local encoding
> and this matches with a UTF-8 entry is extremely low. The reason for
> this is that UTF-8 has a very peculiar byte pattern.

I agree that it is low probability. However, for charsets like MacRoman
and Windows-1252 that reuse the C1 codepoint space, there is a measurable
probability of it happening.

IMO, if we are to take a risk, we should simply say that any label which
contains eight-bit characters must be processed through the IDN path, and
that any eight-bit queries which arrive via the legacy path are to be
rejected (we may also want a new RCODE to signify the exact failure).
Otherwise we end up in a situation where freak labels have to be compared
to the UTF-8 profile and then processed or rejected based on match level.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Thu Jul 19 17:59:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA25241
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 17:59:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NLPM-0004mI-00
	for idn-data@psg.com; Thu, 19 Jul 2001 14:32:32 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NLPL-0004mA-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 14:32:31 -0700
Received: from zetnet.co.uk (man-s346.dialup.zetnet.co.uk [194.247.45.217])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6JLVkC08481;
	Thu, 19 Jul 2001 22:31:51 +0100
Message-ID: <3B5751FA.EE1A7755@zetnet.co.uk>
Date: Thu, 19 Jul 2001 22:32:42 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <5.0.2.1.2.20010717173427.02ff3330@localhost>
	 <200107180221.WAA22344@astro.cs.utk.edu>
	 <20010718064656.15762.qmail@cr.yp.to> <1351242.995543524@localhost>
Content-Type: text/plain; charset=iso-8859-1
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA25241

-----BEGIN PGP SIGNED MESSAGE-----

Patrik Fältström wrote:
> --On 01-07-18 06.46 +0000 "D. J. Bernstein" <djb@cr.yp.to> wrote:
> 
> > What went wrong is that the browser displayed the address as Unicode
> > characters. The address then passed through the (CTEXT UTF-8, although
> > UTF8_STRING would be better) copy-and-paste mechanism, the UTF-8 xterm,
> > the mail client, and the 8-bit-clean MTA, none of which converted back
> > to ACE. The resulting UTF-8 DNS lookup produced NXDOMAIN.
> 
> In the IDNA proposal we have specified that an application which handle
> IDNA (like you seem to say that the browser is) only support IDNA if also
> the content of the clipboard is converted to ACE before the domainname is
> passed to other applications (which doesn't handle IDNA/ACE solution).

That is practical in *some* situations: when the application uses a widget
that is specifically designed to display a domain name (or email address
or URI). In fact I've partially implemented a name entry widget in Java that
does exactly that. It is *not* practical for domain names appearing in free
text. Therefore, in order for cut and paste to work properly, ACE names must
be restricted as far as possible to a minimal set of well-defined contexts -
which is what IDN-8 does.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO1dR2DkCAxeYt5gVAQHXJAf/X4DITHk19yLRBmFyVBfUSv0pizoz0ROs
+q153nvR8cMge+vSksfSu9ddZChwdjbvwl8XgNa6SyCd6oSa3iQ41JJMaU8Q9+hJ
NnYA82iGQ0FSsS4v7HyvSZZkkV+X+b6q7c6z4+SPoDGlRCKMSgTAojTnfdMW3hLm
k0ZEUOWON1VEa1evICvgmUQIS3hL66Yz/DbIq5wMs31kKZmO5DHBF3cmxF2k8l8v
wlMiyT0cXL6yAWXpMsCfwgNxr1yWInub6B7Ajojust+gRdLh9cVDnrYMpXCUAqQh
jx+f90pPFoR9wK/TR7CqChIUHsbiPi35le3NcgcEedw03lM1wyvAXA==
=ZcRP
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Thu Jul 19 18:18:06 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA29516
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 18:18:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NLlC-0005W3-00
	for idn-data@psg.com; Thu, 19 Jul 2001 14:55:06 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NLlB-0005Vx-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 14:55:05 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id RAA06929;
        Thu, 19 Jul 2001 17:44:49 -0400 (EDT)
Message-Id: <200107192144.RAA06929@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: Keith Moore <moore@cs.utk.edu>,
        Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>,
        Martin Duerst <duerst@w3.org>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth 
In-reply-to: Your message of "Thu, 19 Jul 2001 14:18:15 CDT."
             <3B573276.B1E7CC09@ehsco.com> 
Date: Thu, 19 Jul 2001 17:44:48 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> The only way that UTF-8 IDNs will get into the legacy path is if a
> particular implementation goes out of its way to use them where it
> shouldn't. It will have to explicitly call the new API and then explicitly
> pass data that is not supported by the application protocol. This scenario
> is completely unrealistic.

This is complete and utter nonsense, and I'm not going to dignify it
further by continuing the discussion.



From owner-idn@ops.ietf.org  Thu Jul 19 18:22:20 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA00506
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 18:22:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NLwb-0005l1-00
	for idn-data@psg.com; Thu, 19 Jul 2001 15:06:53 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NLwZ-0005kv-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 15:06:52 -0700
Received: from zetnet.co.uk (man-s346.dialup.zetnet.co.uk [194.247.45.217])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6JM5pC14329;
	Thu, 19 Jul 2001 23:05:52 +0100
Message-ID: <3B575A08.6BEC35C1@zetnet.co.uk>
Date: Thu, 19 Jul 2001 23:07:04 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>,
        idn@ops.ietf.org
Subject: Re: [idn] new list of wg documents and next steps
References: <200107191729.f6JHTtd71079@nic-naa.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

Eric Brunner-Williams in Portland Maine wrote:
> draft-ietf-idn-requirements-08.txt, statement of scope, contains this:
> 
>         It is recommended that solutions not necessarily be within
>         the DNS itself, but could be a layer interjected between the
>         application and the DNS.
> 
> While this may be the most popular point of view, it isn't appropriate
> to place a recommendation prior to completion of requirements gathering.

I agree entirely. The following would be reasonable:

          Part of the solution may be to interject a layer between the
          application and the DNS, either in addition to or instead of
          making changes to DNS protocols.

but AFAICS, there is no concensus for the statement as currently written.
It is also ambiguous, since it depends on whether resolvers are considered
to be "within the DNS itself". The choice of whether part of the resolver
functionality is in-process or implemented by the OS, say, is an
implementation detail, not a fundamental part of *any* of the proposals.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO1dZwDkCAxeYt5gVAQEYewf/X1z7dnQC8L0dM/UhjcKxJxc4bdYepaoF
ACi0VHm1Rn2AhxkNZNlOUUuGecW2cUsLWTCGkoWM8su1qE64mrte8P+YdBMX+tfW
zKbn102bS+JHakCgqNMz+k8l2l0Kq393ueNQotRLlm3NrWzlAR6xfd++yYKnueXB
ios4/FjfuE8BW7/x7r1ApMOpytFiGpOsG1rtQ1SuySZKkL6vOMfl6vRt+C0BkDU5
KR7PvVA4YHrfnuK0881eZLhyekAzPeArYjWA9yNB6DhAJEy2xArcksvjliIIbzzn
Ehz8oJQQoIVxOADgsZRo/sOwwOY5Y+u+vy6wscApzJqrYRJi9NFdmQ==
=70HC
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Thu Jul 19 18:41:22 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA04821
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 18:41:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NM3I-000635-00
	for idn-data@psg.com; Thu, 19 Jul 2001 15:13:48 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NM3H-00062y-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 15:13:47 -0700
Received: from zetnet.co.uk (man-s346.dialup.zetnet.co.uk [194.247.45.217])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6JMCYC15389;
	Thu, 19 Jul 2001 23:13:34 +0100
Message-ID: <3B575B9B.CA6F0943@zetnet.co.uk>
Date: Thu, 19 Jul 2001 23:13:47 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: "Brian W. Spolarich" <briansp@walid.com>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <FJEPLIJJEDBNPIOAEIHDAEMHCGAA.briansp@walid.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

"Brian W. Spolarich" wrote:
> 
> | My idea is that servers would be upgraded quite quickly,
> | much more quickly than applications.
> 
>   Martin, I suspect you are being extremely over-optimistic on this point.
> :-)
> 
>   I've had discussions with a number of WALID clients who are interested in
> deploying IDN resolution capabilities and have tried other, so-called
> "server-side" approaches.  Those that in particular focus on requiring ISPs
> to make changes have met with limited success in getting them to do so.
> 
>   There is a tremendous amount of inertia in the deployed nameserver
> infrastructure.

If, for example, a proposal required upgrading of the authoritative
servers *for zones that include IDNs* (but not necessarily any other
servers or proxies), I don't see any reason why that couldn't be done
quickly. Such zones have sufficient incentive to upgrade, if necessary.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO1dbfDkCAxeYt5gVAQHR5Af/dODY6L4QljtcI1uganbBhD9khLdKl/3q
aiyN0lrRHP5SYFnU/7D8tYegyofmJC0iO2ySIRq7VpEcshHauxDl910aWNNGFB5Z
EnziPX5W2QzSE5AI9inmvZazOLTxVADDkVEr2C7JtxnkLzsOiBsQyShEZOKD+9hX
uuNtoKjowBoZYbCEysfJc4hPb2tGdxf4Jw++BntxElBe/phegOyzzXoZ33H88Xwx
B8lhZa0sOURJE9zy7gJHK2UxIGZjXsJAUB5IQrltE7ofCFE7KPX26rbGgLnPohFh
UrURsIgDkFF7T4O2r6H3zi3Wdogklhgy4vX/yGIO/1tuHpc5lyatRQ==
=4XwA
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Thu Jul 19 18:59:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA07227
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 18:59:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NMPV-0006e4-00
	for idn-data@psg.com; Thu, 19 Jul 2001 15:36:45 -0700
Received: from mail.lysator.liu.se ([130.236.254.3])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NMPU-0006dx-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 15:36:44 -0700
Received: from sandra.lysator.liu.se (sandra.lysator.liu.se [130.236.254.203])
	by mail.lysator.liu.se (Postfix) with ESMTP
	id 51DCA82F520; Fri, 20 Jul 2001 00:36:37 +0200 (MET DST)
Received: from localhost (mag@localhost)
	by sandra.lysator.liu.se (8.9.0/8.8.7) with ESMTP id AAA14230;
	Fri, 20 Jul 2001 00:36:36 +0200 (MET DST)
X-Authentication-Warning: sandra.lysator.liu.se: mag owned process doing -bs
Date: Fri, 20 Jul 2001 00:36:36 +0200 (MET DST)
From: C C Magnus Gustavsson <mag@lysator.liu.se>
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
Cc: "Eric A. Hall" <ehall@ehsco.com>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
In-Reply-To: <2267944.995575561@localhost>
Message-ID: <Pine.GSO.4.00.10107200034500.14218-100000@sandra.lysator.liu.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8BIT

On Thu, 19 Jul 2001, Patrik Fältström wrote:

> As evidence that you are completely wrong I take Hotmail as an example.

I agree. Whatever experience I have tells me that a lot of companies won't
bother with internationalization. They will upgrade for security reasons
but as we know, recently discovered vulnerabilities usually only affect
newer versions. (E g, recent exploits have been for BIND 8 while a lot of
people still run BIND 4.)

I'd just like to point out that scenarios like this is one of the 
arguments a number of people have tried to present in support of UTF-8. 
Software vendors won't test their products enough or prioritize fixing
problems which is why we'll most likely get problems with "leakage" of
ACE. And that's precisely the reason why we need to move toward the Single
Encoding in all protocols...

/Magnus




From owner-idn@ops.ietf.org  Thu Jul 19 19:59:04 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22760
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 19:59:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NNFg-0007uG-00
	for idn-data@psg.com; Thu, 19 Jul 2001 16:30:40 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.31 #1)
	id 15NNFd-0007tu-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 16:30:37 -0700
Received: (qmail 17761 invoked from network); 20 Jul 2001 06:46:18 -0000
Received: from chubby.internal.realnames.com (HELO heaven.internal.realnames.com) (10.1.5.39)
  by friendly.realnames.com with SMTP; 20 Jul 2001 06:46:18 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:3438]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <121219@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Thu, 19 Jul 2001 4:28:45 PM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2650.21)
	id <PFRKCM5Z>; Thu, 19 Jul 2001 16:30:08 -0700
Message-ID: <B7233BD6980AD411875700508B5BD5D2014CC6F5@elporto.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: idn@ops.ietf.org
Subject: RE: [idn] IDN security and ACE leakage
Date: Thu, 19 Jul 2001 16:30:08 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="KS_C_5601-1987"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I think this is an issue we'll have to live with. I don't think displaying
ACE, or  hexadecimal, would help. Unless you expect people to remember the
ACE labels for all the people they deal with and whose identity needs to be
established. I believe that if you need this kind of authentication, other
existing solutions like digital signatures are more likely to solve your
needs.

YA



From owner-idn@ops.ietf.org  Thu Jul 19 20:31:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA05355
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 20:31:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NNVE-0008Mq-00
	for idn-data@psg.com; Thu, 19 Jul 2001 16:46:44 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NNVD-0008Mk-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 16:46:43 -0700
Received: from [165.227.249.20] (ip20.proper.com [165.227.249.20])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f6JNkdq11695
	for <idn@ops.ietf.org>; Thu, 19 Jul 2001 16:46:39 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100324b77d20d3ba7a@[165.227.249.20]>
In-Reply-To: <3B575B9B.CA6F0943@zetnet.co.uk>
References: <FJEPLIJJEDBNPIOAEIHDAEMHCGAA.briansp@walid.com>
 <3B575B9B.CA6F0943@zetnet.co.uk>
Date: Thu, 19 Jul 2001 16:45:28 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] Debunking the ACE myth
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 11:13 PM +0100 7/19/01, David Hopwood wrote:
>If, for example, a proposal required upgrading of the authoritative
>servers *for zones that include IDNs* (but not necessarily any other
>servers or proxies), I don't see any reason why that couldn't be done
>quickly. Such zones have sufficient incentive to upgrade, if necessary.

That's not what most of the proposals at hand require. They require 
that any name server that might do IDN queries be upgraded. This 
means the DNS caching servers run at every large company and every 
ISP. This probably also includes every DNS server that gets hit a 
recursive query (even if that server has no IDNs itself), such as the 
root servers and all the TLD servers.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Thu Jul 19 20:37:27 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA07680
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 20:37:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NNvh-0009H8-00
	for idn-data@psg.com; Thu, 19 Jul 2001 17:14:05 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15NNvf-0009Gg-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 17:14:03 -0700
Received: (qmail 15973 invoked by uid 1001); 20 Jul 2001 00:14:19 -0000
Date: 20 Jul 2001 00:14:19 -0000
Message-ID: <20010720001419.13439.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
Automatic-Legal-Notices: Copyright 2001, D. J. Bernstein. My transmission of this message to you does not constitute a copyright waiver or any other limitation of my rights, even if you have told me otherwise.
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: [idn] Hotmail's 8-bit handling
References: <3B570AAB.5D7E0B92@ehsco.com> <13913852.995546566@P2> <3B571197.9831A97@ehsco.com> <2267944.995575561@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Patrik writes:
> Now, do you think Hotmail can handle other characters than US-ASCII in
> headers (header encoding of for example my last name

More details, please.

What exactly shows up on the Hotmail mail-reading web page if the
message contains your name in UTF-8, without further encoding?

What exactly shows up on the Hotmail mail-reading web page if the
message contains your name in Moore's =?...?= MIME encoding?

What about replying to messages with 8-bit bytes? Is there any problem?
What about 8-bit bytes in domain names?

Of course, Hotmail has central control over their software and can
rapidly deploy a new version, so this is all much less important than
what traditional mail clients do, but it's still an interesting example.

---Dan



From owner-idn@ops.ietf.org  Thu Jul 19 20:46:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA11198
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 20:46:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NO0A-0009WA-00
	for idn-data@psg.com; Thu, 19 Jul 2001 17:18:42 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NO09-0009W4-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 17:18:41 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15NO08-0007IC-00; Thu, 19 Jul 2001 17:18:40 -0700
Date: Fri, 20 Jul 2001 00:18:40 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
Message-ID: <20010720001840.D27207@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <004601c11063$a8283aa0$1001a8c0@neteka.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Edmon <edmon@neteka.com> wrote:

> The point I am trying to make is that DNS has to move first, it has
> been from the begining, or else, why would the other protocols have
> depended on DNS at all?

DNS does not have to move first.

Assertion:  Very few applications/protocols interact with DNS directly;
the vast majority go through a resolver.

Consequence:  Most applications/protocols, while they might be
influenced by the presence or absence of a resolver API that supports
UTF-8, have no way to know (and hence no reason to care) whether the
resolver and DNS server communicate using ACE or EDNS/UTF-8.

Do you doubt the assertion?  Do you doubt that the consequence follows
from the assertion?

If you want to work on extending DNS, then do so.  You don't need to
sell us on the urgency or importance.

AMC



From owner-idn@ops.ietf.org  Thu Jul 19 20:56:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA14393
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 20:56:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NONP-000A0o-00
	for idn-data@psg.com; Thu, 19 Jul 2001 17:42:43 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NONN-000A0h-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 17:42:41 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6K0enp01279;
	Fri, 20 Jul 2001 09:40:53 +0900 (KST)
Message-ID: <008301c110b4$f898b680$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Yves Arrouye" <yves@realnames.com>, <idn@ops.ietf.org>
References: <B7233BD6980AD411875700508B5BD5D2014CC6F5@elporto.internal.realnames.com>
Subject: Re: [idn] IDN security and ACE leakage
Date: Fri, 20 Jul 2001 09:42:19 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,
----- Original Message ----- 
From: "Yves Arrouye" <yves@realnames.com>
To: <idn@ops.ietf.org>
Sent: Friday, July 20, 2001 8:30 AM
Subject: RE: [idn] IDN security and ACE leakage


> I think this is an issue we'll have to live with. I don't think displaying
> ACE, or  hexadecimal, would help. Unless you expect people to remember the
> ACE labels for all the people they deal with and whose identity needs to be
> established. 

ACE or hex dump should be an "AUXILIARY" representation of IDN, 
supplementing native-script representation.

But, for me,
Arabic domain names seem as randomly-gererated string as hexdump string.
Displaying arabic names in its native-scripts  does not help me to identify or
differentiate the site from others. (I would call it "utf8 leakage".)


>I believe that if you need this kind of authentication, other
> existing solutions like digital signatures are more likely to solve your
> needs.
> 

In your argument,
There is a "Missing link" between automatic digital
signature verification and  its "human" association with 
"often undistinguishable or unrecognizable" 
IDN email/site name.

Moreover, scam email account owners are often able to get  
his/her personal email certificate issued without any face-to-face 
authentication from major certificate vendors.  

But, I believe  encouraging using digital signatures will make internet
more secure.
 
Soobok
 
> YA
> 




From owner-idn@ops.ietf.org  Thu Jul 19 21:45:00 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA01392
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 21:45:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NOwM-000B9P-00
	for idn-data@psg.com; Thu, 19 Jul 2001 18:18:50 -0700
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NOwL-000B6x-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 18:18:49 -0700
Received: from [24.252.219.84] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.8)
  with ESMTP-TLS id 190014; Wed, 18 Jul 2001 20:17:00 -0500
Message-ID: <3B5786B7.8346A066@ehsco.com>
Date: Thu, 19 Jul 2001 20:17:44 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Paul Hoffman / IMC <phoffman@imc.org>
CC: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <FJEPLIJJEDBNPIOAEIHDAEMHCGAA.briansp@walid.com>
	 <3B575B9B.CA6F0943@zetnet.co.uk> <p05100324b77d20d3ba7a@[165.227.249.20]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> That's not what most of the proposals at hand require. They require
> that any name server that might do IDN queries be upgraded.

This is true only if the operators of that domain want to provide UTF-8
IDNs to their users. If they are happy with the level of service provided
by ACE, they can stick with it.

NB: the choice is ACE or ACE-with-UTF-8. The operators do not have to
upgrade if they don't want to. No upgrades are *required* (the word you
used in your comment) by either the operators or end-users.

I'm not sure I understand where the confusion on this point comes from,
nor why it is proving to be so hard to dispel.

> This probably also includes every DNS server that gets hit a
> recursive query (even if that server has no IDNs itself), such as the
> root servers and all the TLD servers.

This is accurate. Every 3LD has the authority to create their own IDN
labels, so every TLD must be able to process the resulting queries.

However, it is important to point out that most of these servers are
upgraded frequently, so the threat of lag is not very high. The only
question would be if the TLD operators want to support UTF-8 IDNs or not
(very probable, IMO). We can certainly ask them if they would refuse to
implement such a technology if it were the standard.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Thu Jul 19 22:01:28 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA06934
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 22:01:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NPOh-000C7d-00
	for idn-data@psg.com; Thu, 19 Jul 2001 18:48:07 -0700
Date: Thu, 19 Jul 2001 11:26:33 -0700 (PDT)
From: ned.freed@mrochek.com
Subject: Re: [idn] Debunking the ACE myth
To: John C Klensin <klensin@jck.com>
Cc: idn@ops.ietf.org
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15NPOh-000C7d-00@psg.com>

> I think that was my point.  The people that want "it" will
> upgrade, if they can.   The ISPs who run the servers may not see
> "want" the same way. So, once again, if you want rapid
> deployment, pick a solution that leaves the upgrading in the
> hands of those who need the functionality --the users in this
> case-- rather than entertaining fantasies about what ISPs and
> other server operators will do.

I don't work for an ISP, but I do work on email software that a fair
number of
large ISPs buy. And I believe that John is right on target here.

Here's a specific example. Some time back we released a new version of
our
email software. The primary goal of this particular release was to
improve our
internationalization and localization capabilities. A large number of
enhancements were made and a large number of internationalization bugs
were
fixed. In particular, any number of issues relating to the ability to
handle
non-ASCII user information properly were addressed.

But uptake of this new release has been very slow, even with customers
who said
they urgently needed the new internationalization and localization
support and
bug fixes in this release. And this continues to be the case despite
many
reports from the field saying the new release is actually more stable,
more
reliable, faster, and generally easier to deal with than the old
version.

And even in cases where the new release has been deployed the new
functionality
hasn't always been exposed to end users. This is because having the
support in
the product is only the first step. Provisioning issues have to be dealt
with.
And large ISPs often have their own provisioning tools, some of which
are quite
convoluted, and these tools have to be updated before they can usefully
offer
new functionality.

The bottom line is that large ISPs are conservative. No, make that
*extremely*
conservative. Marketing may be crying for new features, but operations
isn't
willing to sacrifice stability to get those new features. When it comes
to
software deployment they proceed slowly, they test everything six ways
from
Sunday, and even if it all looks good they still wait for an opportune
time to
upgrade cautiously. And at the first sign of trouble they call the whole
thing
off. And then you wait for another windoe in, say, 6 months or so.

And guess what? Even with all the care they take, they still have
problems all
the time. Our industry doesn't exactly have a stellar track record when
it
comes to quality and reliability. So I don't expect any of this to
change any
time soon.

But what if there was a security hole? As it happens I have experience
with
this as well. Happily, we haven't found holes in our code, but we depend
on
lots of other libraries and components from other sources, and several
vulnerabilities have been found in a couple of these. When such things
are
found and found to matter our customers get a patch for the software
they are
running. They don't upgrade to fix security holes. They demand patches.
And
they get them.

Now, you may argue that my experience isn't typical, that experience
with email
deployment says nothing about DNS deployment, that IDN deployment is
somehow
different or whatever. But you now have two people with real world
deployment
experience saying that John's experience in this area matches our own.
Make of
that what you will.

Ned





From owner-idn@ops.ietf.org  Thu Jul 19 23:57:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA17720
	for <idn-archive@lists.ietf.org>; Thu, 19 Jul 2001 23:57:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NR7I-000Fkm-00
	for idn-data@psg.com; Thu, 19 Jul 2001 20:38:16 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NR7H-000Fkg-00
	for idn@ops.ietf.org; Thu, 19 Jul 2001 20:38:15 -0700
Received: from zetnet.co.uk (man-s088.dialup.zetnet.co.uk [194.247.41.215])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6K3boC15568;
	Fri, 20 Jul 2001 04:37:52 +0100
Message-ID: <3B57A7D3.88A58BE5@zetnet.co.uk>
Date: Fri, 20 Jul 2001 04:38:59 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: Paul Hoffman / IMC <phoffman@imc.org>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <FJEPLIJJEDBNPIOAEIHDAEMHCGAA.briansp@walid.com>
	 <3B575B9B.CA6F0943@zetnet.co.uk> <p05100324b77d20d3ba7a@[165.227.249.20]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

Paul Hoffman / IMC wrote:
> At 11:13 PM +0100 7/19/01, David Hopwood wrote:
> >If, for example, a proposal required upgrading of the authoritative
> >servers *for zones that include IDNs* (but not necessarily any other
> >servers or proxies), I don't see any reason why that couldn't be done
> >quickly. Such zones have sufficient incentive to upgrade, if necessary.
> 
> That's not what most of the proposals at hand require. They require
> that any name server that might do IDN queries be upgraded.

Well, UDNS does. In general it depends on why the servers are being
upgraded. To support labels longer than 63 octets (or names longer than
255 octets), yes, it's necessary to negotiate use of a new DNS version,
which requires updates to all servers in the query path. AFAICS it should
not be necessary to require updates to all servers in the path for any
other reason, though (for example, it is not necessary in order to change
the algorithm by which names as encoded on the wire are canonicalised for
matching against names that come from zone files).

So, I think pretty much any reasonable design could be tweaked to have
the property that names that fit the octet limits in their wire-encoded
form, are resolvable with at most changes to authoritative servers for
zones with IDNs. What, if anything, am I missing?

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO1enoTkCAxeYt5gVAQGdPgf/Xf4PKbH6oAtjn/6KzSKO5mWaXS5b6AFn
gdn61hhgVRuCjNzgocJcOfLsVP+5kP1srjJm15uBKv4dnShuw9YQ8YIkDnIOPoPv
yb6OdG9Xm7xFu2K6eeEh0jr7mqGNtNoeSE+6MRovoEI6FBoI7z3e7CdLMP3Ga1SQ
jdz1NAqhbH+wYX3Xv7Mw4d4vBBGjjnHvHEJinOl+DMdd6L43h6ZX5o+hRETI8aMC
H0sSc+jNobyT5hnRjsoHo4NGhA2Ibsnp+JMdAv5rhaseV/pksUR9u9JPjVnuAoyw
Xxg952WzdXFrAJuFKyIOe8sdTXPJKUNBlAxro5uXIq9kilKd7ZNOaQ==
=xEmw
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Fri Jul 20 07:20:15 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA00260
	for <idn-archive@lists.ietf.org>; Fri, 20 Jul 2001 07:20:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NXw8-0003FO-00
	for idn-data@psg.com; Fri, 20 Jul 2001 03:55:12 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NXw7-0003Dq-00
	for idn@ops.ietf.org; Fri, 20 Jul 2001 03:55:11 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id MAA29962
	for <idn@ops.ietf.org>; Fri, 20 Jul 2001 12:54:52 +0200 (MET DST)
Date: Fri, 20 Jul 2001 09:31:20 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: idn@ops.ietf.org
Subject: Re: [idn] Hotmail's 8-bit handling
Message-ID: <2881998.995621480@localhost>
In-Reply-To: <20010720001419.13439.qmail@cr.yp.to>
References: <3B570AAB.5D7E0B92@ehsco.com> <13913852.995546566@P2>
 <3B571197.9831A97@ehsco.com> <2267944.995575561@localhost>
 <20010720001419.13439.qmail@cr.yp.to>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA00260

--On 01-07-20 00.14 +0000 "D. J. Bernstein" <djb@cr.yp.to> wrote:

> Patrik writes:
>> Now, do you think Hotmail can handle other characters than US-ASCII in
>> headers (header encoding of for example my last name
> 
> More details, please.

(a) I registered at Hotmail, using a Microsoft Internet Explorer Browser
just to be sure I used a Microsoft product talking with a Microsoft service
(b) It asked about my name, and I entered "Fältström" as my last name
(c) I composed an email, and entered Swedish characters in both the subject
and the body of the email
(d) I sent the mail to a host where I could look at exactly what arrives
over SMTP from the Hotmail system

Result:

(1) The From: header look like this (well, not really, because I now use a
Mac, and there is a translation of ISO 8859-1 to the local Mac charset
which makes things not exactly what they should, but anyway):

From: "Patrik F?ltstr?m" <pfaltstr@hotmail.com>

I.e. my last name include 8bit characters, and it is the ISO 8859-1 ones
which are sent directly on the wire.

No header encoding of the name.

(2) The Subject: have the same problem as the From: header.

Subject: Nu s?nder jag en r?ksm?rgÂs

ISO 8859-1 without any header encoding at all.

(3) The MIME-type is not correct. It is the following:

Content-Type: text/plain; format=flowed

No charset parameter.

The SMTP server I have do handle the ESMTP extension 8bitmime so I didn't
expect ant content-transfer-encoding.



I.e. my conclusion of working with charset issues in Internet protocols now
for 10 years is that all people should try to change their native language
to something which is not english for a couple of months and see how bad
implemented internationalization and handling of non-US-ASCII is in
applications. This regardless of whether the transport is 8bit clean or not.

     Patrik




From owner-idn@ops.ietf.org  Fri Jul 20 09:15:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA23696
	for <idn-archive@lists.ietf.org>; Fri, 20 Jul 2001 09:15:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NZv3-000797-00
	for idn-data@psg.com; Fri, 20 Jul 2001 06:02:13 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NZv2-00077h-00
	for idn@ops.ietf.org; Fri, 20 Jul 2001 06:02:12 -0700
Received: from enoshima (g055040.ppp.asahi-net.or.jp [211.132.55.40])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id WAA24829;
	Fri, 20 Jul 2001 22:02:11 +0900 (JST)
Message-Id: <4.2.0.58.J.20010720142924.02cb5100@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 20 Jul 2001 14:31:47 +0900
To: Paul Hoffman / IMC <phoffman@imc.org>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Debunking the ACE myth
In-Reply-To: <p05100324b77d20d3ba7a@[165.227.249.20]>
References: <3B575B9B.CA6F0943@zetnet.co.uk>
 <FJEPLIJJEDBNPIOAEIHDAEMHCGAA.briansp@walid.com>
 <3B575B9B.CA6F0943@zetnet.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 16:45 01/07/19 -0700, Paul Hoffman / IMC wrote:
>At 11:13 PM +0100 7/19/01, David Hopwood wrote:
>>If, for example, a proposal required upgrading of the authoritative
>>servers *for zones that include IDNs* (but not necessarily any other
>>servers or proxies), I don't see any reason why that couldn't be done
>>quickly. Such zones have sufficient incentive to upgrade, if necessary.
>
>That's not what most of the proposals at hand require. They require that 
>any name server that might do IDN queries be upgraded. This means the DNS 
>caching servers run at every large company and every ISP. This probably 
>also includes every DNS server that gets hit a recursive query (even if 
>that server has no IDNs itself), such as the root servers and all the TLD 
>servers.

Is that 'all the TLD servers' or 'all the TLD servers that allow IDNs'?
Would it be possible to have it so that e.g. if Switzerland (.ch) would
decide they don't need IDNs anywhere, they could just prohibit it?

Regards,   Martin.



From owner-idn@ops.ietf.org  Fri Jul 20 09:15:41 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA23722
	for <idn-archive@lists.ietf.org>; Fri, 20 Jul 2001 09:15:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NZvl-0007AO-00
	for idn-data@psg.com; Fri, 20 Jul 2001 06:02:57 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NZvk-0007AG-00
	for idn@ops.ietf.org; Fri, 20 Jul 2001 06:02:56 -0700
Received: from enoshima (g055040.ppp.asahi-net.or.jp [211.132.55.40])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id WAA24854;
	Fri, 20 Jul 2001 22:02:21 +0900 (JST)
Message-Id: <4.2.0.58.J.20010720174327.03f2e7d0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 20 Jul 2001 17:44:19 +0900
To: "Mark Davis" <mark@macchiato.com>, "Keith Moore" <moore@cs.utk.edu>,
        "Soobok Lee" <lsb@postel.co.kr>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Re: Back to work (Nameprep) (was: Re: Just send
  UTF-8 with nameprep (was: RE: [idn] Reality Check)) 
Cc: "Keith Moore" <moore@cs.utk.edu>, <idn@ops.ietf.org>
In-Reply-To: <00bc01c11066$640cbeb0$0c680b41@c1340594a>
References: <Your message of "Wed, 18 Jul 2001 17:28:42 +0900." <031601c10f63$a8ca6560$ed1bd9d2@postel.co.kr>
 <4.2.0.58.J.20010719155703.034369f0@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 08:20 01/07/19 -0700, Mark Davis wrote:
> > Very low for lower case. Between Latin and Greek, or Cyrillic and Greek,
> > it's only the 'o'.
>
>This is inaccurate.

This came in in an extremely small font. Was that on purpose :-) ?

Regards,   Martin.




From owner-idn@ops.ietf.org  Fri Jul 20 09:18:07 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA24059
	for <idn-archive@lists.ietf.org>; Fri, 20 Jul 2001 09:18:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NZvF-00079j-00
	for idn-data@psg.com; Fri, 20 Jul 2001 06:02:25 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NZvE-00079a-00
	for idn@ops.ietf.org; Fri, 20 Jul 2001 06:02:24 -0700
Received: from enoshima (g055040.ppp.asahi-net.or.jp [211.132.55.40])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id WAA24832;
	Fri, 20 Jul 2001 22:02:12 +0900 (JST)
Message-Id: <4.2.0.58.J.20010720143232.02c3cbe0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 20 Jul 2001 14:37:25 +0900
To: "Brian W. Spolarich" <briansp@walid.com>
From: Martin Duerst <duerst@w3.org>
Subject: RE: [idn] Debunking the ACE myth
Cc: <idn@ops.ietf.org>
In-Reply-To: <FJEPLIJJEDBNPIOAEIHDAEMHCGAA.briansp@walid.com>
References: <4.2.0.58.J.20010719165243.0346b640@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hello Brian - I acknowledge the amount of inertia. And I would be
very inert myself as an ISP at this point in the game. But if the IETF
work is done, and e.g. here in Japan, JPNIC officially announces things,
and the trade press runs articles and surveys (they do tons of
statistics here in Japan, there is a magazine that comes out
every month telling you at what time of the day which access
points of which provider are how buisy), how many ISPs would
resist how long?

Regards,   Martin.

At 08:04 01/07/19 -0400, Brian W. Spolarich wrote:

>| My idea is that servers would be upgraded quite quickly,
>| much more quickly than applications.
>
>   Martin, I suspect you are being extremely over-optimistic on this point.
>:-)
>
>   I've had discussions with a number of WALID clients who are interested in
>deploying IDN resolution capabilities and have tried other, so-called
>"server-side" approaches.  Those that in particular focus on requiring ISPs
>to make changes have met with limited success in getting them to do so.
>
>   There is a tremendous amount of inertia in the deployed nameserver
>infrastructure.
>
>   -bws
>




From owner-idn@ops.ietf.org  Fri Jul 20 09:40:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA00644
	for <idn-archive@lists.ietf.org>; Fri, 20 Jul 2001 09:40:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NZv0-000781-00
	for idn-data@psg.com; Fri, 20 Jul 2001 06:02:10 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NZuz-00077k-00
	for idn@ops.ietf.org; Fri, 20 Jul 2001 06:02:09 -0700
Received: from enoshima (g055040.ppp.asahi-net.or.jp [211.132.55.40])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id WAA24826;
	Fri, 20 Jul 2001 22:02:10 +0900 (JST)
Message-Id: <4.2.0.58.J.20010720140014.037c8950@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 20 Jul 2001 14:22:05 +0900
To: Patrik F=?ISO-2022-JP?B?GyRCZ00bKEI=?=tstr
 =?ISO-2022-JP?B?GyRCi04bKEI=?= <paf@cisco.com>,
        "D. J. Bernstein" <djb@cr.yp.to>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Clipboard handling (was: Re: [idn] Debunking the ACE myth)
In-Reply-To: <1351242.995543524@localhost>
References: <20010718064656.15762.qmail@cr.yp.to>
 <5.0.2.1.2.20010717173427.02ff3330@localhost>
 <200107180221.WAA22344@astro.cs.utk.edu>
 <20010718064656.15762.qmail@cr.yp.to>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

At 11:52 01/07/19 +0200, Patrik F$BgM(Btstr$B‹N(B wrote:
>In the IDNA proposal we have specified that an application which handle
>IDNA (like you seem to say that the browser is) only support IDNA if also
>the content of the clipboard is converted to ACE before the domainname is
>passed to other applications (which doesn't handle IDNA/ACE solution).

The clipboard doesn't have any protocol to distinguish whether the
target will be IDNA-enabled or not. [Most clipboards now have mechanisms
to distinguish the encoding, but ACE won't work with that. It's also
possible to create new clipboard categories, but again old applications
won't pick that up.]

Of course, IDNA could require that the clipboard is always in ACE,
but then imagine the following: User A sees a cool website, and
copies the address (mostly a domain name) into a mail to user B.
The paste operation will suddenly show some random garbage rather
than the actual address. The user will retry the cut/paste a few
more times, with the same result. It will then decide that the
browser or the mailer, or both, are buggy, and will type in the
address by hand.

Also, assume that the clipboard is tagged and that the receiving
mailer actually gets the ace and understands it. Should that then
go into the mail body as characters, as the user expects? Or would
idna prescribe that it goes there as ace? Do we want idna to require
behavior that users will clearly see as buggy and not accept, and
that therefore reasonable implementers won't implement? And if
we take the napkin as another kind of clipboard, is there a way
to get the user to somehow change the things she sees to ACE?
Is this what we are working on this effort for? In my eyes,
clearly not.

By the way, what if user B receives the web address in characters
(rather than ace)? Well, they'll put it into their browser, and
it will either work or not. If it doesn't work, they'll blame the
browser. They may find out that they have to upgrade if they want
this functionality. To most, it should not be too difficult to
understand that to make browsers work with non-ASCII addresses
where they have up to now only worked with ascii addresses needs
some change somewhere. It's definitely much easier to understand
than the clipbord bug, and it's something that users will have
to learn anyway, *whatever approach we take*.

So my proposal would be: Don't try to be too intelligent with
the clipboard.

Regards,   Martin.








From owner-idn@ops.ietf.org  Fri Jul 20 11:05:38 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA28747
	for <idn-archive@lists.ietf.org>; Fri, 20 Jul 2001 11:05:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Nao0-0008wM-00
	for idn-data@psg.com; Fri, 20 Jul 2001 06:59:00 -0700
Received: from femail2.sdc1.sfba.home.com ([24.0.95.82])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Nanz-0008wE-00
	for idn@ops.ietf.org; Fri, 20 Jul 2001 06:58:59 -0700
Received: from c1340594a ([65.11.104.12]) by femail2.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20010720135848.LAKR5252.femail2.sdc1.sfba.home.com@c1340594a>;
          Fri, 20 Jul 2001 06:58:48 -0700
Message-ID: <005701c11124$4f4632e0$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "Keith Moore" <moore@cs.utk.edu>, "Soobok Lee" <lsb@postel.co.kr>,
        "Martin Duerst" <duerst@w3.org>
Cc: "Keith Moore" <moore@cs.utk.edu>, <idn@ops.ietf.org>
References: <Your message of "Wed, 18 Jul 2001 17:28:42 +0900." <031601c10f63$a8ca6560$ed1bd9d2@postel.co.kr><4.2.0.58.J.20010719155703.034369f0@sh.w3.mag.keio.ac.jp> <4.2.0.58.J.20010720174327.03f2e7d0@sh.w3.mag.keio.ac.jp>
Subject: Re: [idn] Re: Back to work (Nameprep) (was: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check)) 
Date: Fri, 20 Jul 2001 06:59:53 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Yes, it was in 9pt, which is the lower end of normal body text (9-12pt).
What I couldn't show in the message is the variation among the typefaces
that people could be looking at domain names with.

Mark
—————

πάντων μέτρον ἄνθρωπος — Πρωταγόρας
[http://www.macchiato.com]

----- Original Message -----
From: "Martin Duerst" <duerst@w3.org>
To: "Mark Davis" <mark@macchiato.com>; "Keith Moore" <moore@cs.utk.edu>;
"Soobok Lee" <lsb@postel.co.kr>
Cc: "Keith Moore" <moore@cs.utk.edu>; <idn@ops.ietf.org>
Sent: Friday, July 20, 2001 01:44
Subject: Re: [idn] Re: Back to work (Nameprep) (was: Re: Just send UTF-8
with nameprep (was: RE: [idn] Reality Check))


> At 08:20 01/07/19 -0700, Mark Davis wrote:
> > > Very low for lower case. Between Latin and Greek, or Cyrillic and
Greek,
> > > it's only the 'o'.
> >
> >This is inaccurate.
>
> This came in in an extremely small font. Was that on purpose :-) ?
>
> Regards,   Martin.
>
>
>




From owner-idn@ops.ietf.org  Fri Jul 20 13:46:49 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA10325
	for <idn-archive@lists.ietf.org>; Fri, 20 Jul 2001 13:46:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ne29-000ErN-00
	for idn-data@psg.com; Fri, 20 Jul 2001 10:25:49 -0700
Received: from [207.65.203.98] (helo=goose.ehsco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ne28-000Epe-00
	for idn@ops.ietf.org; Fri, 20 Jul 2001 10:25:48 -0700
Received: from [24.252.219.84] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.8)
  with ESMTP-TLS id 190212; Thu, 19 Jul 2001 12:23:59 -0500
Message-ID: <3B58695A.A1242C8D@ehsco.com>
Date: Fri, 20 Jul 2001 12:24:42 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Martin Duerst <duerst@w3.org>
CC: Paul Hoffman / IMC <phoffman@imc.org>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <3B575B9B.CA6F0943@zetnet.co.uk>
	 <FJEPLIJJEDBNPIOAEIHDAEMHCGAA.briansp@walid.com>
	 <3B575B9B.CA6F0943@zetnet.co.uk> <4.2.0.58.J.20010720142924.02cb5100@sh.w3.mag.keio.ac.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> Is that 'all the TLD servers' or 'all the TLD servers that allow IDNs'?
> Would it be possible to have it so that e.g. if Switzerland (.ch) would
> decide they don't need IDNs anywhere, they could just prohibit it?

The root and TLD servers would only need to understand the extended label
type for UTF-8 IDN referrals (for downstream 4LD labels) to work.

If there is a need for a particular (root|TLD) zone to hold UTF-8 IDN
entries in particular (essentially, does it need to hold UTF-8 NS records
for delegation purposes), then the servers for that TLD would need to
support the ACE-plus-UTF8 dual-mode protocol.

It is feasible for each TLD to incrementally support the dual-mode IDN
according to their own i18n schedule. They would have to support the
extended label type at a minimim, but they would not need to run
ACE-plus-UTF8 immediately (COM can run without it forever, for example).

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Fri Jul 20 18:41:20 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA18921
	for <idn-archive@lists.ietf.org>; Fri, 20 Jul 2001 18:41:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NhZG-000K1s-00
	for idn-data@psg.com; Fri, 20 Jul 2001 14:12:14 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.31 #1)
	id 15NhZF-000K1l-00
	for idn@ops.ietf.org; Fri, 20 Jul 2001 14:12:13 -0700
Received: (qmail 12312 invoked from network); 21 Jul 2001 04:31:12 -0000
Received: from chubby.internal.realnames.com (HELO heaven.internal.realnames.com) (10.1.5.39)
  by friendly.realnames.com with SMTP; 21 Jul 2001 04:31:12 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:1551]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <6064@heaven.internal.realnames.com>
	 for <duerst@w3.org>; Fri, 20 Jul 2001 2:10:32 PM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2650.21)
	id <PJWHH9CY>; Fri, 20 Jul 2001 14:11:55 -0700
Message-ID: <B7233BD6980AD411875700508B5BD5D2011E9686@elporto.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: "'Soobok Lee'" <lsb@postel.co.kr>, Yves Arrouye <yves@realnames.com>,
        idn@ops.ietf.org, Martin Duerst <duerst@w3.org>
Subject: RE: [idn] Should we add U+FF0E FULLWIDTH FULL STOP to section  5.
	10 of Nameprep?
Date: Fri, 20 Jul 2001 14:11:55 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> FULLWIDTH FULLSTOP(U+FF0E) is already compatibility 
> decomposed into Latin FULLSTOP (U+002E)  in KC Normalization 
> step in NAMEPREP. You can confirm that in page 4 of 
> http://www.unicode.org/charts/PDF/UFF00.pdf .
> 
> If any label contains U+ff0e to be mapped into u+002e in kc 
> norm in nameprep, it will be treated as error  in the 
> following prohibition stage in nameprep , since
> u+002E. is prohibited.

But that is exactly the problem I want to address: if you type:

	SOMETHING<U+FF0E>JP

For example, it will not be seen as a domain name in the .JP domain, even
though this was the intent (let's say also that JP can be in full-width
ASCII, which makes the U+FF0E very plausible). Just like typing:

	SOMETHING<U+3002>JP

won't. This is the exact same thing. So I think we need to handle it just
like U+3002 is handled.

YA



From owner-idn@ops.ietf.org  Fri Jul 20 18:42:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA19214
	for <idn-archive@lists.ietf.org>; Fri, 20 Jul 2001 18:42:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NiZY-000LeA-00
	for idn-data@psg.com; Fri, 20 Jul 2001 15:16:36 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.31 #1)
	id 15NiZX-000Le3-00
	for idn@ops.ietf.org; Fri, 20 Jul 2001 15:16:35 -0700
Received: (qmail 16425 invoked from network); 21 Jul 2001 05:35:35 -0000
Received: from chubby.internal.realnames.com (HELO heaven.internal.realnames.com) (10.1.5.39)
  by friendly.realnames.com with SMTP; 21 Jul 2001 05:35:35 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:1907]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <7548@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Fri, 20 Jul 2001 3:14:42 PM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2650.21)
	id <PJWH2ABM>; Fri, 20 Jul 2001 15:16:05 -0700
Message-ID: <B7233BD6980AD411875700508B5BD5D2011E968A@elporto.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: "'idn@ops.ietf.org'" <idn@ops.ietf.org>
Subject: RE: [idn] Should we add U+FF0E FULLWIDTH FULL STOP to section  5.
	10 of Nameprep?
Date: Fri, 20 Jul 2001 15:16:04 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> But that is exactly the problem I want to address: if you type:
> 
> 	SOMETHING<U+FF0E>JP
> 
> For example, it will not be seen as a domain name in the .JP 
> domain, even though this was the intent (let's say also that 
> JP can be in full-width ASCII, which makes the U+FF0E very 
> plausible). Just like typing:
> 
> 	SOMETHING<U+3002>JP
> 
> won't. This is the exact same thing. So I think we need to 
> handle it just like U+3002 is handled.

I wasn't really clear. Since it's forbidden because of the compatibility
mapping, all I want is some text that identifies that as a caveat for IDN
implementers, so that they don't just map U+3002 to U+002E before Nameprep
and then wonder why this one doesn't work.

YA



From owner-idn@ops.ietf.org  Fri Jul 20 18:44:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA19581
	for <idn-archive@lists.ietf.org>; Fri, 20 Jul 2001 18:44:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Nir2-000M0K-00
	for idn-data@psg.com; Fri, 20 Jul 2001 15:34:40 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Nir0-000M06-00
	for idn@ops.ietf.org; Fri, 20 Jul 2001 15:34:38 -0700
Received: from zetnet.co.uk (man-s214.dialup.zetnet.co.uk [194.247.45.85])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6KMYNv15963;
	Fri, 20 Jul 2001 23:34:24 +0100
Message-ID: <3B58B235.2B1B94C5@zetnet.co.uk>
Date: Fri, 20 Jul 2001 23:35:33 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: Yves Arrouye <yves@realnames.com>, idn@ops.ietf.org
Subject: Re: [idn] Should we add U+FF0E FULLWIDTH FULL STOP to section  5.10 of 
 Nameprep?
References: <B7233BD6980AD411875700508B5BD5D2011E9686@elporto.internal.realnames.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

Yves Arrouye wrote:
> > FULLWIDTH FULLSTOP(U+FF0E) is already compatibility
> > decomposed into Latin FULLSTOP (U+002E)  in KC Normalization
> > step in NAMEPREP. You can confirm that in page 4 of
> > http://www.unicode.org/charts/PDF/UFF00.pdf.
> >
> > If any label contains U+ff0e to be mapped into u+002e in kc
> > norm in nameprep, it will be treated as error  in the
> > following prohibition stage in nameprep , since
> > u+002E. is prohibited.
> 
> But that is exactly the problem I want to address: if you type:
> 
>         SOMETHING<U+FF0E>JP
> 
> For example, it will not be seen as a domain name in the .JP domain, even
> though this was the intent (let's say also that JP can be in full-width
> ASCII, which makes the U+FF0E very plausible). Just like typing:
> 
>         SOMETHING<U+3002>JP
> 
> won't. This is the exact same thing. So I think we need to handle it just
> like U+3002 is handled.

I agree (and the same for anything that compatibility-maps to U+002E in
future versions of the tables).

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO1iyITkCAxeYt5gVAQE6NQf/XZDVIZS2DDCxAvO+CDrjyW4RXGQI7d1x
Yo5Mwr/EgfYKarCBBC/24gO/lEYjpUBdciDtKB6sL63oJaejTgzgtGn7AJzDTJEh
KoqvpTK3RPMu8nL4sFOzs0142WdZtlDURzXSPShhU6UjVd9QxZLAqueAzw9WSJT3
FJM03+7q50k3gkz0h0v+6pY3RKy7MhsCiZ3e3jMfBkwI1IeJW3ZQfZGLG2BMueKx
dAo1OJ243AKbLb+WAx3sdbs5J27nKYAk6yMzSXv6TW7KI+j8nRJU0/qjQhjOvjma
psChvZqDNwU9ARoIPBnOS//LmCwoRqmTwehiyVoOyg9OclDfYlvo5Q==
=mR62
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Fri Jul 20 20:23:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA27602
	for <idn-archive@lists.ietf.org>; Fri, 20 Jul 2001 20:23:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NkFu-000NcM-00
	for idn-data@psg.com; Fri, 20 Jul 2001 17:04:26 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NkFu-000NcF-00
	for idn@ops.ietf.org; Fri, 20 Jul 2001 17:04:26 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15NkFp-0008AR-00; Fri, 20 Jul 2001 17:04:21 -0700
Date: Sat, 21 Jul 2001 00:04:21 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Should we add U+FF0E FULLWIDTH FULL STOP to section  5. 10 of Nameprep?
Message-ID: <20010721000421.F30405@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B7233BD6980AD411875700508B5BD5D2011E968A@elporto.internal.realnames.com> <B7233BD6980AD411875700508B5BD5D2011E9686@elporto.internal.realnames.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Yves Arrouye <yves@realnames.com> wrote:

> I wasn't really clear.  Since it's forbidden because of the
> compatibility mapping, all I want is some text that identifies that as
> a caveat for IDN implementers, so that they don't just map U+3002 to
> U+002E before Nameprep and then wonder why this one doesn't work.

I'm still not sure what you want, but I just noticed that the existing
explanation of the prohibition of U+3002 is a bit misleading.  It
currently says:

    U+3002 is used as if it were U+002E in many input mechanisms,
    particularly in Asia.  This prohibition allows input mechanisms to
    safely map U+3002 to U+002E before doing nameprep without worrying
    about preventing users from accessing legitimate host name parts.

However, mapping U+3002 to U+002E "before doing nameprep" isn't specific
enough.  If it happens immediately before doing nameprep, then nameprep
will fail.  It needs to happen before the domain name is split into
labels.  Therefore I think the text should read:

    U+3002 is used as if it were U+002E in many input mechanisms,
    particularly in Asia.  This prohibition allows input mechanisms to
    safely map U+3002 to U+002E before splitting a domain name into
    labels, without worrying about preventing users from accessing
    legitimate host name parts.

This recalls an earlier discussion about just how much processing
should be done before a domain name is split into labels.  Should
fullwidth-full-stop be mapped to full-stop before the splitting?
Probably.  How about one-dot-leader (for which full-stop is a
compatibility decomposition)?  Maybe.  Should digit-one-full-stop be
replaced by its compatibility decomposition "1."?  Or square-CO by its
compatibility decomposition "CO."?  Maybe not.

Should this be left up to the user interface designer, or should there
be recommendations or requirements?

AMC



From owner-idn@ops.ietf.org  Sat Jul 21 06:41:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA16781
	for <idn-archive@lists.ietf.org>; Sat, 21 Jul 2001 06:41:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NpGS-000415-00
	for idn-data@psg.com; Fri, 20 Jul 2001 22:25:20 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.31 #1)
	id 15NpGR-00040r-00
	for idn@ops.ietf.org; Fri, 20 Jul 2001 22:25:19 -0700
Received: (qmail 11518 invoked from network); 21 Jul 2001 12:44:17 -0000
Received: from chubby.internal.realnames.com (HELO heaven.internal.realnames.com) (10.1.5.39)
  by friendly.realnames.com with SMTP; 21 Jul 2001 12:44:17 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:1738]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <17879@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Fri, 20 Jul 2001 10:23:23 PM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2650.21)
	id <PJWH2MRJ>; Fri, 20 Jul 2001 22:24:47 -0700
Message-ID: <B7233BD6980AD411875700508B5BD5D2011E9691@elporto.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: idn@ops.ietf.org
Subject: RE: [idn] Should we add U+FF0E FULLWIDTH FULL STOP to section  5.
	 10 of Nameprep?
Date: Fri, 20 Jul 2001 22:24:46 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> However, mapping U+3002 to U+002E "before doing nameprep" 
> isn't specific
> enough.  If it happens immediately before doing nameprep, 
> then nameprep
> will fail.  It needs to happen before the domain name is split into
> labels.  Therefore I think the text should read:
> 
>     U+3002 is used as if it were U+002E in many input mechanisms,
>     particularly in Asia.  This prohibition allows input mechanisms to
>     safely map U+3002 to U+002E before splitting a domain name into
>     labels, without worrying about preventing users from accessing
>     legitimate host name parts.

Yes, it would be better. "Before Nameprep" is misleading you're right. Also,
the two uses of "input mechanisms" are misleading too. I think it should be
applications in the second case. Now, it could read:

    U+3002 is generated instead of U+002E by many input mechanisms,
    particularly in Asia.  This prohibition allows applications to
    safely map U+3002 to U+002E before splitting a domain name into
    labels, without worrying about preventing users from accessing
    legitimate host name parts.  Implementors should also be aware
    that U+FF0E is also generated instead of U+002E by many input
    mechanisms, and applications may want to map it to U+002E for
    the same reason they map U+3002 to U+002E.

(I did actually say "is generated instead of U+002E by many input
mechanisms" instead of "is used as it were U+002E in many input mechanisms".
I think that's clearer.)

> This recalls an earlier discussion about just how much processing
> should be done before a domain name is split into labels.  Should
> fullwidth-full-stop be mapped to full-stop before the splitting?
> Probably.  How about one-dot-leader (for which full-stop is a
> compatibility decomposition)?  Maybe.  Should digit-one-full-stop be
> replaced by its compatibility decomposition "1."?  Or square-CO by its
> compatibility decomposition "CO."?  Maybe not.
> 
> Should this be left up to the user interface designer, or should there
> be recommendations or requirements?

It's a big can of worms, yes. It's going to be interesting indeed to see (as
in see on your screen) some dots that are not label separators. Another case
of glyphs vs characters issues. Oh well.

Note that my rationale for asking for U+FF0E (as U+3002) is not about the
fact that it decomposes to U+002E. It is that when one user *physically
types the name* using a keyboard, her "dot" key does not produce the ASCII
dot (a workaround is to use the numerical keypad on Windows; oh great:
switch keyboard parts!). Since the only key that is labelled "." does not
produce a "." in some cases, this sounds like a very good idea. Also note
that applications still can decide not to do it. But who would do that to
their users? So I argue that we should at least acknowledge these physical
limitations to help implementers of applications. 

The other cases you present are definitely interesting. It points one of the
main interesting things of this work which is that everything is done at the
level of a label, and never at the level of a full domain name... This is
not only interesting because of the examples you're giving but also because
it will raise interesting questions about what does an application, versus
say a new UTF-16 gethostbyiname() [i for internationalized] API call: will
gethostbyiname() do these kind of mappings (U+3002 etc... to U+002E) for
application's convenience? If so, will it also pre-NFKD the whole thing,
adding more labels through decomposition? Hmm... The less we recommend or
standardize on this, the more changes for non-interoperable DNS resolver
interfaces (or other uses of DNS with IDNs) there may be.

But first, we can address the simple thing: physical limitations of input
methods that prevent users from getting the expected behavior in an
internationalized context.

YA




From owner-idn@ops.ietf.org  Sat Jul 21 06:41:30 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA16797
	for <idn-archive@lists.ietf.org>; Sat, 21 Jul 2001 06:41:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Npks-0004hG-00
	for idn-data@psg.com; Fri, 20 Jul 2001 22:56:46 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.31 #1)
	id 15Npkr-0004hA-00
	for idn@ops.ietf.org; Fri, 20 Jul 2001 22:56:45 -0700
Received: (qmail 13586 invoked from network); 21 Jul 2001 13:15:39 -0000
Received: from chubby.internal.realnames.com (HELO heaven.internal.realnames.com) (10.1.5.39)
  by friendly.realnames.com with SMTP; 21 Jul 2001 13:15:39 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:3836]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <18662@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Fri, 20 Jul 2001 10:54:27 PM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2650.21)
	id <PJWH2NPA>; Fri, 20 Jul 2001 22:55:51 -0700
Message-ID: <B7233BD6980AD411875700508B5BD5D2011E9695@elporto.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: idn@ops.ietf.org
Subject: RE: [idn] nameprep failures
Date: Fri, 20 Jul 2001 22:55:49 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> >At least, a cheater or a fraud would deliberately try  it.
> 
> Cheaters won't try to put in on namecards.
> They may try to put it into an email, and get you to
> click on it.

It's not a may, it's a will...

YA



From owner-idn@ops.ietf.org  Sat Jul 21 08:46:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA04844
	for <idn-archive@lists.ietf.org>; Sat, 21 Jul 2001 08:46:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Nvul-000CLw-00
	for idn-data@psg.com; Sat, 21 Jul 2001 05:31:23 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Nvuk-000CLh-00
	for idn@ops.ietf.org; Sat, 21 Jul 2001 05:31:23 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id OAA08065;
	Sat, 21 Jul 2001 14:30:33 +0200 (MET DST)
Date: Sat, 21 Jul 2001 11:30:39 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Martin Duerst <duerst@w3.org>, "Adam M. Costello" <amc@cs.berkeley.edu>,
        idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
Message-ID: <2163741.995715039@localhost>
In-Reply-To: <4.2.0.58.J.20010720143840.02cd5670@sh.w3.mag.keio.ac.jp>
References: <4.2.0.58.J.20010719163929.039b4100@sh.w3.mag.keio.ac.jp>
 <20010719011709.3228.qmail@cr.yp.to>
 <4.2.0.58.J.20010719163929.039b4100@sh.w3.mag.keio.ac.jp>
 <4.2.0.58.J.20010720143840.02cd5670@sh.w3.mag.keio.ac.jp>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-07-20 14.46 +0900 Martin Duerst <duerst@w3.org> wrote:

>> I.e. the problem with using non-ascii in the labels in DNS, is that it is
>> really easy to get what I would call leakage into the application layer
>> protocols which can not handle other characters than ASCII.
> 
> As Dan and others have shown, that's really easy also for ACE.
> Even if we get all software doing it as planned, users will leak.

But if ACE leak to a non-IDN aware application the user will be able to use
the domainname.

  paf




From owner-idn@ops.ietf.org  Sat Jul 21 09:14:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA10495
	for <idn-archive@lists.ietf.org>; Sat, 21 Jul 2001 09:14:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Nvu4-000CKe-00
	for idn-data@psg.com; Sat, 21 Jul 2001 05:30:40 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Nvu3-000CKY-00
	for idn@ops.ietf.org; Sat, 21 Jul 2001 05:30:39 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id OAA08070
	for <idn@ops.ietf.org>; Sat, 21 Jul 2001 14:30:36 +0200 (MET DST)
Date: Sat, 21 Jul 2001 11:31:18 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: idn@ops.ietf.org
Subject: Re: Clipboard handling (was: Re: [idn] Debunking the ACE myth)
Message-ID: <2166092.995715078@localhost>
In-Reply-To: <4.2.0.58.J.20010720140014.037c8950@sh.w3.mag.keio.ac.jp>
References: <20010718064656.15762.qmail@cr.yp.to>
 <5.0.2.1.2.20010717173427.02ff3330@localhost>
 <200107180221.WAA22344@astro.cs.utk.edu><20010718064656.15762.qmail@cr.yp.to>
  <4.2.0.58.J.20010720140014.037c8950@sh.w3.mag.keio.ac.jp>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-07-20 14.22 +0900 Martin Duerst <duerst@w3.org> wrote:

> The clipboard doesn't have any protocol to distinguish whether the
> target will be IDNA-enabled or not.

It depends on what operating system you are using. Saying that the protocol
doesn't exist is wrong.

  paf




From owner-idn@ops.ietf.org  Sat Jul 21 09:14:31 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA10501
	for <idn-archive@lists.ietf.org>; Sat, 21 Jul 2001 09:14:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NwEM-000Cq2-00
	for idn-data@psg.com; Sat, 21 Jul 2001 05:51:38 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NwEL-000Cpw-00
	for idn@ops.ietf.org; Sat, 21 Jul 2001 05:51:37 -0700
Received: from enoshima (g055040.ppp.asahi-net.or.jp [211.132.55.40])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id VAA28471;
	Sat, 21 Jul 2001 21:51:45 +0900 (JST)
Message-Id: <4.2.0.58.J.20010721214409.03f0e700@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Sat, 21 Jul 2001 21:50:11 +0900
To: Patrik F=?ISO-2022-JP?B?GyRCZ00bKEI=?=tstr
 =?ISO-2022-JP?B?GyRCi04bKEI=?= <paf@cisco.com>,
        idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: Clipboard handling (was: Re: [idn] Debunking the ACE myth)
In-Reply-To: <2166092.995715078@localhost>
References: <4.2.0.58.J.20010720140014.037c8950@sh.w3.mag.keio.ac.jp>
 <20010718064656.15762.qmail@cr.yp.to>
 <5.0.2.1.2.20010717173427.02ff3330@localhost>
 <200107180221.WAA22344@astro.cs.utk.edu>
 <20010718064656.15762.qmail@cr.yp.to>
 <4.2.0.58.J.20010720140014.037c8950@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello Patrick,

At 11:31 01/07/21 +0200, Patrik F$BgM(Btstr$B‹N(B wrote:
>--On 01-07-20 14.22 +0900 Martin Duerst <duerst@w3.org> wrote:
>
> > The clipboard doesn't have any protocol to distinguish whether the
> > target will be IDNA-enabled or not.
>
>It depends on what operating system you are using. Saying that the protocol
>doesn't exist is wrong.

Sorry, I wrote:

 >>>>
The clipboard doesn't have any protocol to distinguish whether the
target will be IDNA-enabled or not. [Most clipboards now have mechanisms
to distinguish the encoding, but ACE won't work with that. It's also
possible to create new clipboard categories, but again old applications
won't pick that up.]
 >>>>

The text in [] speaks exactly about what you said above.
Maybe I'll try to reword:

The DNS protocol has lot's of bells and whistles that could be
used to distinguish utf-8 and ace. Clipboard protocols do have
some bells and whistles that could be used to distinguish utf-8
and ace.

The DNS doesn't currently have a protocol to distinguish utf-8
and ace. Clipboards currently don't have a protocol to distinguish
utf-8 and ace.

Could you agree with that?

Regards,   Martin.



From owner-idn@ops.ietf.org  Sat Jul 21 09:14:32 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA10528
	for <idn-archive@lists.ietf.org>; Sat, 21 Jul 2001 09:14:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Nw6y-000CfG-00
	for idn-data@psg.com; Sat, 21 Jul 2001 05:44:00 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Nw6x-000CfA-00
	for idn@ops.ietf.org; Sat, 21 Jul 2001 05:43:59 -0700
Received: from enoshima (g055040.ppp.asahi-net.or.jp [211.132.55.40])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id VAA28419;
	Sat, 21 Jul 2001 21:43:59 +0900 (JST)
Message-Id: <4.2.0.58.J.20010721213642.03d2b2f0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Sat, 21 Jul 2001 21:41:02 +0900
To: Patrik F=?ISO-2022-JP?B?GyRCZ00bKEI=?=tstr
 =?ISO-2022-JP?B?GyRCi04bKEI=?= <paf@cisco.com>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Debunking the ACE myth
In-Reply-To: <2163741.995715039@localhost>
References: <4.2.0.58.J.20010720143840.02cd5670@sh.w3.mag.keio.ac.jp>
 <4.2.0.58.J.20010719163929.039b4100@sh.w3.mag.keio.ac.jp>
 <20010719011709.3228.qmail@cr.yp.to>
 <4.2.0.58.J.20010719163929.039b4100@sh.w3.mag.keio.ac.jp>
 <4.2.0.58.J.20010720143840.02cd5670@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

At 11:30 01/07/21 +0200, Patrik F$BgM(Btstr$B‹N(B wrote:
>--On 01-07-20 14.46 +0900 Martin Duerst <duerst@w3.org> wrote:
>
> >> I.e. the problem with using non-ascii in the labels in DNS, is that it is
> >> really easy to get what I would call leakage into the application layer
> >> protocols which can not handle other characters than ASCII.
> >
> > As Dan and others have shown, that's really easy also for ACE.
> > Even if we get all software doing it as planned, users will leak.
>
>But if ACE leak to a non-IDN aware application the user will be able to use
>the domainname.

Sorry Patrick, I was most probably too short. What I meant is:

Even with ACE, it's possible that real IDNs (i.e. non-ACEd) leak
to non-IDN-aware applications, via the user, some billboard or
napkin,... I.e. we cannot guarantee that all non-IDN-aware
applications only get ACE input.

Regards,   Martin.



From owner-idn@ops.ietf.org  Sat Jul 21 11:08:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA06496
	for <idn-archive@lists.ietf.org>; Sat, 21 Jul 2001 11:08:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15NyFg-000FRM-00
	for idn-data@psg.com; Sat, 21 Jul 2001 08:01:08 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15NyFf-000FRG-00
	for idn@ops.ietf.org; Sat, 21 Jul 2001 08:01:07 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id LAA20163;
        Sat, 21 Jul 2001 11:01:02 -0400 (EDT)
Message-Id: <200107211501.LAA20163@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Martin Duerst <duerst@w3.org>
cc: Patrik F=?ISO-2022-JP?B?GyRCZ00bKEI=?=tstr =?ISO-2022-JP?B?GyRCi04bKEI=?= <paf@cisco.com>,
        idn@ops.ietf.org
Subject: Re: Clipboard handling (was: Re: [idn] Debunking the ACE myth) 
In-reply-to: Your message of "Sat, 21 Jul 2001 21:50:11 +0900."
             <4.2.0.58.J.20010721214409.03f0e700@sh.w3.mag.keio.ac.jp> 
Date: Sat, 21 Jul 2001 11:01:02 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> The DNS protocol has lot's of bells and whistles that could be
> used to distinguish utf-8 and ace. Clipboard protocols do have
> some bells and whistles that could be used to distinguish utf-8
> and ace.
> 
> The DNS doesn't currently have a protocol to distinguish utf-8
> and ace. Clipboards currently don't have a protocol to distinguish
> utf-8 and ace.

Either of these could be true; both could be misleading.
The devil is in the details.  

Can you make a DNS extension that distinguishes between utf-8 and 
ace which provides consistent results between utf-8 and ace, doesn't 
significantly delay either type of query, and doesn't require 
upgrades to intermediaries before it works?  Maybe, but we're still 
waiting for an existence proof.

For some particular OS or GUI environment, can you define a clipboard
interface such that non-IDN-aware applications  get the ACE form
of a domain name and IDN-aware applications get a native form of that
domain name, for arbitrary text that is copied into the clipboard
(not just domain names by themselves, but email addresses, URIs, 
and anything else that uses domain names)   Maybe, but I have my
doubts. 

(Do we really want a clipboard interface that treats almost any string 
with dots in it as a domain name?)

Keith



From owner-idn@ops.ietf.org  Sun Jul 22 01:03:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA29447
	for <idn-archive@lists.ietf.org>; Sun, 22 Jul 2001 01:03:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15O9Uv-00030y-00
	for idn-data@psg.com; Sat, 21 Jul 2001 20:01:37 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15O9Ut-00030K-00
	for idn@ops.ietf.org; Sat, 21 Jul 2001 20:01:36 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6M319B21654
	for <idn@ops.ietf.org>; Sun, 22 Jul 2001 12:01:09 +0900 (KST)
Message-ID: <002701c1125a$64578b20$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Subject: [idn] Indian scripts and similarities
Date: Sun, 22 Jul 2001 11:59:57 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

Recently, I found many similarities between Indian language scripts.

  Go to http://www.aczone.com/itrans/tblall/tblall.html
  and click 'Vowel', 'Consonant' and 'Digits' links and look into
  the script comparison tables.

Compare these pairs of scripts:
  1.  Devanagari vs Bengali
  2.  Gujarati  vs Gurmukhi
  3.  Kannada vs Telugu

If indian business names in an Indian state can be expressed 
both in its official language scripts
and in its second language scripts (maybe the official one of another state),
there may be name collisions across Indian states.

Do we need equivalence-conversion tables among Indian language scripts
like that of Traditional/Simplified chinese conversion table
proposed by CNNIC?

Regards,

Soobok Lee




From owner-idn@ops.ietf.org  Mon Jul 23 01:21:54 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA22112
	for <idn-archive@lists.ietf.org>; Mon, 23 Jul 2001 01:21:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OTiO-000KjS-00
	for idn-data@psg.com; Sun, 22 Jul 2001 17:36:52 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15OTiM-000KjK-00
	for idn@ops.ietf.org; Sun, 22 Jul 2001 17:36:50 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH8mrHnsaLWiwwcht8ikFbPNN50DlcJ0SEA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GAZAAATA; Sun, 22 Jul 2001 20:36:22 EDT
To: Internet-Drafts@ietf.org
Cc: idn@ops.ietf.org, liana.ydisg@juno.com
Date: Sun, 22 Jul 2001 17:52:00 -0700
Subject: [idn] draft-liana-idn-step-1
Message-ID: <20010722.175204.-810189.0.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.11
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=--__JNP_000_7c06.7909.59bc
X-Juno-Att: 1
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This message is in MIME format.  Since your mail reader does not understand
this format, some or all of this message may not be legible.

----__JNP_000_7c06.7909.59bc
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Internationalized Domain Name Working
Group of the IETF.

	Title		: StepCode- A Romanized Mnemonic IDN Encoding
	Author(s)	: Liana Ye
	Filename	: draft-liana-idn-step-1.txt
	Pages		: 25
	Date		: 22-July-2001
	
This document describes Romanization of localized internet 
domain names of different languages to US-ASCII [a-z0-9] strings 
in a fashion that is completely compatible with the current DNS.
Two related documents, IDN tags and Mnemonic mapping, will be summitted
shortly. 

----__JNP_000_7c06.7909.59bc
Content-Type: text/plain; name="draft-liana-idn-step-1.txt"
Content-Transfer-Encoding: base64

SW50ZXJuZXQgRHJhZnQgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgTGlhbmEg
WWUNCmRyYWZ0LUxpYW5hLWlkbi1zdGVwLTAxLnR4dCAgICAgICAgICAgICAgICAgICAgICAgICAg
WSZEIElTRw0KSnVseSAyMCwgMjAwMQ0KRXhwaXJlcyBpbiBzaXggbW9udGhzIChEZWNlbWJlciAy
MDAxKSAgICAgICAgICAgICAgICAgICAgICAgICANCgkJICAgDQoJIFN0ZXBDb2RlLSBBIFJvbWFu
aXplZCBNbmVtb25pYyBJRE4gRW5jb2RpbmcNCgkJDQpTdGF0dXMgb2YgdGhpcyBtZW1vDQoNClRo
aXMgZG9jdW1lbnQgaXMgYW4gSW50ZXJuZXQtRHJhZnQgYW5kIGlzIGluIGZ1bGwgY29uZm9ybWFu
Y2Ugd2l0aA0KYWxsIHByb3Zpc2lvbnMgb2YgU2VjdGlvbiAxMCBvZiBSRkMyMDI2Lg0KDQpJbnRl
cm5ldC1EcmFmdHMgYXJlIHdvcmtpbmcgZG9jdW1lbnRzIG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVl
cmluZw0KVGFzayBGb3JjZSAoSUVURiksIGl0cyBhcmVhcywgYW5kIGl0cyB3b3JraW5nIGdyb3Vw
cy4gTm90ZSB0aGF0DQpvdGhlciBncm91cHMgbWF5IGFsc28gZGlzdHJpYnV0ZSB3b3JraW5nIGRv
Y3VtZW50cyBhcw0KSW50ZXJuZXQtRHJhZnRzLg0KDQpJbnRlcm5ldC1EcmFmdHMgYXJlIGRyYWZ0
IGRvY3VtZW50cyB2YWxpZCBmb3IgYSBtYXhpbXVtIG9mIHNpeA0KbW9udGhzIGFuZCBtYXkgYmUg
dXBkYXRlZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRlZCBieSBvdGhlciBkb2N1bWVudHMNCmF0IGFu
eSB0aW1lLiBJdCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMgcmVm
ZXJlbmNlDQptYXRlcmlhbCBvciB0byBjaXRlIHRoZW0gb3RoZXIgdGhhbiBhcyAid29yayBpbiBw
cm9ncmVzcy4iDQoNCiAgICAgVGhlIGxpc3Qgb2YgY3VycmVudCBJbnRlcm5ldC1EcmFmdHMgY2Fu
IGJlIGFjY2Vzc2VkIGF0DQogICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvaWV0Zi8xaWQtYWJzdHJh
Y3RzLnR4dA0KDQogICAgIFRoZSBsaXN0IG9mIEludGVybmV0LURyYWZ0IFNoYWRvdyBEaXJlY3Rv
cmllcyBjYW4gYmUgYWNjZXNzZWQNCgkgYXQgaHR0cDovL3d3dy5pZXRmLm9yZy9zaGFkb3cuaHRt
bC4NCg0KDQpBYnN0cmFjdA0KDQpUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBSb21hbml6YXRpb24g
b2YgbG9jYWxpemVkIGludGVybmV0IA0KZG9tYWluIG5hbWVzIG9mIGRpZmZlcmVudCBsYW5ndWFn
ZXMgdG8gVVMtQVNDSUkgW2EtejAtOV0gc3RyaW5ncyANCmluIGEgZmFzaGlvbiB0aGF0IGlzIGNv
bXBsZXRlbHkgY29tcGF0aWJsZSB3aXRoIHRoZSBjdXJyZW50IEROUy4gIA0KDQoxLiBJbnRyb2R1
Y3Rpb24NCg0KMS4xIENvbnRleHQNCg0KV29ybGQtd2lkZSBkZXNpcmUgdG8gdXNlIGNoYXJhY3Rl
cnMgb3RoZXIgdGhhbiBwbGFpbiBBU0NJSSBpbiANCmhvc3RuYW1lcyBpcyBidWJibGluZyB1cCBh
bmQgYWNjZWxlcmF0aW5nLiBIb3N0bmFtZXMgaGF2ZSBiZWNvbWUgDQp0aGUgZXF1aXZhbGVudCBv
ZiBidXNpbmVzcyBvciBwcm9kdWN0IG5hbWVzIGZvciBtYW55IHNlcnZpY2VzIA0Kb24gdGhlIElu
dGVybmV0LCBoZXJlIGFsc28gcmVmZXJyZWQgYXMgdHJhZGVuYW1lcy4gIFRoZSBuZWVkIHRvIA0K
bWFrZSB0aGVtIHVzYWJsZSBieSBwZW9wbGUgd2hvc2UgbmF0aXZlIHNjcmlwdHMgYXJlIG5vdCBk
aXJlY3RseSANCnJlcHJlc2VudGFibGUgYnkgQVNDSUksIHRoZSBuZWVkIGZvciBuZXR3b3JrIHN1
cHBvcnQgd29ya2VycyB0bw0KZGlhZ25vcyBVUkwsIHRoZSBuZWVkIGZvciBleHBhbmRlZCBhbmQg
ZGl2ZXJzZSBuYW1lIHNlcnZlciANCm5ldHdvcmsgdG8gc29ydCBhbmQgbWFuYWdlIHpvbmVmaWxl
cywgdGhlIG5lZWQgZm9yIGluY3JlYXNpbmcgDQpudW1iZXIgb2Ygbm9uLW5hdGl2ZSByZWFkZXJz
LCB3aG8gYXJlIG5vdCB1c2luZyB0aGVpciBuYXRpdmUgDQpzY3JpcHRzIHRvIHJlZmVyIHRvIHRy
YWRlbmFtZXMgaW4gZGFpbHkgYWN0aXZpdGllcywgYW5kIHRoZSBuZWVkDQp0byBtaW5pbWl6ZSBw
b3NzaWJsZSBzZWN1cml0eSBsZWFrcyB3aGVuIGludGVybmF0aW9uYWwgZG9tYWluIA0KbmFtZXMg
YXJlIGltcGxlbWV0ZWQgaW4gRGRvbWFpbiBOYW1lIFNlcnZlcnMgKEROUykgaGF2ZSB0byBiZSAN
CmFkZHJlc3NlZC4gVGhlIHJlcXVpcmVtZW50cyBmb3IgaW50ZXJuYXRpb25hbGl6aW5nIGhvc3Ru
YW1lcyBhcmUgDQpkZXNjcmliZWQgaW4gdGhlIElETiBXRydzIHJlcXVpcmVtZW50cyBkb2N1bWVu
dCwgW0lETlJlcV0uDQoNClRvIGZhY2lsaXRhdGUgb25lIEROUyBzeW1ib2wgc2V0IGZvciB1c2Vy
cyBvZiBkaWZmZXJlbnQgbGFuZ3VhZ2VzIA0KaW4gYWJvdmUgdGVjaG5pY2FsIGFuZCBzZWN1cml0
eSBjb25zaWRlcmF0aW9ucywgYSBSb21hbml6YXRpb24gDQpwcm9jZXNzIGZyb20gZGlmZmVyZW50
IGxhbmd1YWdlcyB0byBVUy1BU0NJSSBpcyB1bmF2b2lkYWJsZS4NCkxhbmd1YWdlIFJvbWFuaXph
dGlvbiBoYXMgYmVlbiBhIGZhY3QgYXJvdW5kIHRoZSBnbG9iZSANCnNpbmNlIFJ1c3NpYSBzdGFu
ZGFyZGl6ZWQgQ3lyaWxsaWMgZm9yIG1hbnkgZWFzdGVuIEV1cm9wZWFuIA0KbGFuZ3VhZ2VzIGlu
IHRoZSAxOTIwJ3MsIFR1cmtleSBjaGFuZ2VkIGZyb20gQXJhYmljIHRvIExhdGluDQpzY3JpcHQg
aW4gMTkyOCwgYW5kIENoaW5hIGFkYXB0ZWQgUGlueWluIGFzIGEgc3VwcGxlbWVudGFsDQpwaG9u
ZXRpYyBzeXN0ZW0gZm9yIEhhbiBzY3JpcHQgaW4gMTk1OC4gSW4gdGhlIHBhc3QgdGhyZWUgDQpk
ZWNhZGVzLCBzb2Z0d2FyZSBpbXBsZW1lbnRhdGlvbiBvZiBzdWNoIGEgcHJvY2VzcyBoYXMgZXh0
ZW50ZWQgDQpmcm9tIGEgdXNlciB0byBoaXMgcXdlcnR5IGtleWJvYXJkLCBmcm9tIGEga2V5Ym9h
cmQgdG8gdGV4dCANCmVkaXRvcnMgb2YgdmFyaW91cyBraW5kcywgZnJvbSB0ZXh0IGVkaXRvcnMg
dG8gbWFpbCBzZXJ2aWNlcywgDQpmcm9tIG1haWwgc2VydmljZXMgdG8gaW50ZXJuZXQgYWRkcmVz
cyByZXNvbHZlcnMuICBUbyB1bmlmeSBhIA0KZnJhZ21lbnRlZCBSb21hbml6YXRpb24gaW1wbGVt
ZW50YXRpb24gcmVhbGl0eSBmb3IgdXNlIGFzIA0KSUROIGhvc3RuYW1lIGlkZW50aWZpZXIsIGEg
d3JpdHRlbiBkb2N1bWVudGF0aW9uIGlzIG92ZXJkdWUgdG8gDQphZGRyZXNzIGlzc3VlcyBhcyBi
YXNpYyBhcyBzdGF0ZWQgYnkgW0RlRnJhbmNpcyAxOTg5XToNCiAgICJUaGUgYWRhcHRhdGlvbiBv
ZiBMYXRpbiBhbHBoYWJldCB0byByZXByZXNlbnQgYSBncmVhdCB2YXJpZXR5DQpvZiBzcG9rZW4g
bGFuZ3VhZ2VzIG1lYW5zIG9mIGNvdXJzZSB0aGF0IHRoZSB2YWx1ZSBvZiBzcGVjaWZpYyANCnN5
bWJvbHMgdmFyaWVzIGZyb20gbGFuZ3VhZ2UgdG8gbGFuZ3VhZ2UuICBUaGlzIGlzIHRydWUgYm90
aCBvZg0KdGhlIEV1cm9wZWFuIGFkYXB0YXRpb25zLCB3aGljaCBpbiBtb3N0IGNhc2VzIGNhbWUg
YWJvdXQgcmF0aGVyIA0KaGFwaGF6YXJkbHksIGFuZCBvZiB0aGUgbW9yZSByZWNlbnQgY3JlYXRp
b25zIGJhc2VkIG9uIG1vcmUgDQpjYXJlZnVsbHkgdGhvdWdodC1vdXQgbGluZ3Vpc3RpYyBwcmlu
Y2lwbGVzLiAgU28gaXQgaXMgdGhhdCB0aGUgDQpGcmVuY2ggJ3UnIGhhcyBhIGRpZmZlcmVudCB2
YWx1ZSBmcm9tIHRoYXQgaW4gRW5nbGlzaC4gIFRoZSBsZXR0ZXINCidqJyByZXByZXNlbnRzIG9u
ZSBzb3VuZCBpbiBFbmdsaXNoICdqYW0nLCBhbm90aGVyIGluIEdlcm1hbiAnamEnLg0KVGhlIGlu
aXRpYWwgc291bmQgb2YgRW5nbGlzaCAnc3VyZScgaXMgd3JpdHRlbiAnc3onLCBpbiBQb2xpc2gs
IA0KQ3plY2guIFRoZSBzb3VuZCByZXByZXNlbnRlZCBieSBFbmdsaXNoICd0cycgaXMgd3JpdHRl
biBpbiAnYycNCmluIFBvbGlzaCwgQ3plY2gsIEh1bmdhcmlhbiwgU2VyYm8tQ3JvYXRpYW4sIGFu
ZCBDaGluZXNlLiINCg0KT25lIHN0ZXAgZnVydGhlciBmcm9tIHRoZSBhYm92ZSBsaW5ndWlzdGlj
IGlzc3VlcyBpcyBzb3J0aW5nIGFuZCANCnNlYXJjaGluZyB6b25lZmlsZXMgb3IgbmFtZSBzZXJ2
ZXJzIG9mIGhvc3RuYW1lIGlkZW50aWZpZXJzIA0KY29udGFpbmluZyBkaWZmZXJlbnQgd3JpdHRl
biBsYW5ndWFnZXMgZm9yIHBvdGVudGlhbGx5IHZlcnkgDQpsYXJnZSBudW1iZXJzIG9mIHVzZXJz
IG9ubGluZSwgc2F5IDEwJSBvZiB0aGUgd29ybGQncyBwb3B1bGF0aW9uLiAgDQpIb3N0bmFtZSBp
ZGVudGlmaWNhdGlvbiBjb3VsZCBiZWNvbWUgYSBib3R0bGVuZWNrIGZvciBpbnRlcm5ldCANCnRy
YWZmaWMgaWYgc29ydGluZyBhbmQgc2VhcmNoaW5nIGhhcyB0byBiZSB0cmVhdGVkIDEuIGluIG1v
cmUgDQp0aGFuIG9uZSBzZXQgb2YgcGFydGlhbGx5IG92ZXJsYXBwaW5nIG9yIG1peGVkIG9yIHBv
c3NpYmx5IG1peGVkIA0Kc3ltYm9saWMgcmVwcmVzZW50YXRpb25zOyBhbmQgMi4gaW4gY29tcHJl
c3NlZCBvciBzZW1hbnRpY2FsbHkgDQpyYW5kb20gb3JkZXJlZCB6b25lZmlsZXMgc2NhdHRlcmVk
IGFyb3VuZCB0aGUgZ2xvYmUuDQoNCkhpc3RvcmljYWxseSwgQ2hhcmFjdGVyLWZvcm1lZCBzY3Jp
cHQgc3VjaCBhcyBDSksgY2hhcmFjdGVycyBoYXMgDQppbmhlcmVudCBzb3J0aW5nIGFuZCBpbmRl
eGluZyBkaWZmaWN1bHRpZXMgYW5kIGlzIHVzZWQgdG8gYmUgDQphbiBpbnRlbGxlY3R1YWwgYWN0
aXZpdHkganVzdCB0byB1c2UgYSBkaWN0aW9uYXJ5LiBTdXBwb3NlIHdlIGhhdmUgDQpzb2x2ZWQg
c3VjaCBhbiBpbmRleGluZyBwcm9ibGVtIHdpdGggc3Vic3RhbnRpYWwgcmVzb3VyY2VzIGFuZA0K
SUROIGdvZXMgdG8gYSBDaGFyYWN0ZXItZm9ybSBiYXNlZCBzeXN0ZW0sIHRoZW4gaXQgaXMgZm9y
c2VlYWJsZSANCnRoYXQgSUROUyBzeXN0ZW0gd2lsbCBoYXZlIHRvIHN1cHBvcnQgYSB0ZXh0IGJh
c2VkIEROUyBzeXN0ZW0gYXMgDQp3ZWxsIGZvciBhIGxvbmcgdGltZS4gIEFmdGVyIGFsbCwgdGhl
IEROUyBzeXN0ZW0gaXMgYSBoaXN0b3JpY2FsbHkgDQpzdWNjZXNzZnVsIHN5c3RlbS4gVG8gdGhy
b3cgc3VjaCBhIHN5c3RlbSBhd2F5IGlzIGxpa2UgYXNraW5nIA0KcGVvcGxlIHRvIHN0b3Agc2hv
cHBpbmcgYXQgc3VwZXJtYXJrZXRzLiANCg0KVGhlIFJvbWFuaXplZCBQaW55aW4gc3lzdGVtIGZv
ciBDSksgY2hhcmFjdGVyIGluZGV4aW5nIGhhcyANCnByb3ZpZGVkIGEgZmVhc2libGUgYnV0IHBh
cnRpYWwgc29sdXRpb24uIFRoZSBjdXJyZW50bHkgdXNlZCANCmNvbXBsZXRlIHNvbHV0aW9uIGlz
IHRvIGdvIHRocm91Z2ggYSBzb2Z0d2FyZSBwcm9jZXNzIG9mIGJvdGggDQpzZWFyY2hpbmcgZGF0
YWJhc2VzIGZvciBwb3NzaWJsZSBtYXRjaGVzIChub3QgZXhhY3QtbWF0Y2ggRE5TIA0KbG9va3Vw
cykgYW5kLCB3aGVyZSBuZWNlc3NhcnksIGRpYWxvZ3VlIHdpdGggdGhlIHVzZXJzLCBhbmQgYXJy
aXZlIA0KYXQgc3Ryb25nIGNhbmRpZGF0ZXMgZm9yIHRoZSBnbHlwaCByZXByZXNlbnRhdGlvbiwg
ZXNwZWNpYWxseSANCndoZXJlIHRoZSB1c2VycyB3ZXJlIG5vdCBlYXNpbHkgYWJsZSB0byBlbnRl
ciBtb3JlIGRpcmVjdCANCnJlcHJlc2VudGF0aW9ucyBvZiB0aGUgY2hhcmFjdGVycyBmcm9tIGtl
eWJvYXJkcy4gSWYgdGhpcyANCnNlbGVjdGlvbiBwcm9jZXNzIGNhbiBiZSBjb2RpZmllZCBpbiBM
YXRpbiBhbHBoYWJldCwgdGhlbiBhIA0KY29tcGxldGUgUm9tYW5pemVkIHN5bGxhYmljIHN5c3Rl
bSB3aWxsIGJlIHJlYWxpdHksIGFuZCBzb3J0aW5nIA0KYW5kIHNlYXJjaGluZyBpbnRlcm5hdGlv
bmFsIGRvbWFpbiBuYW1lcyB3aXRoIG9uZSBzZXQgb2Ygc3ltYm9saWMgDQpyZXByZXNlbnRhdGlv
biB3aWxsIGJlIHNwZWVkeSBhbmQgZmVhc2libGUuIA0KDQpSZXByZXNlbnRhdGlvbiBzeXN0ZW0g
Zm9yIGhvc3RuYW1lcyBpcyBkdWUgdG8gYmUgdW5pZmllZC4gSW4gDQpmYWN0LCB3cml0aW5nIHN5
c3RlbSB1bmlmaWNhdGlvbiBoYXMgYmVlbiBzZWVuIHdpdGggQXJhYmljLCBMYXRpbiANCmFuZCBD
aGluZXNlLiAgRWFjaCBvZiB0aGVtIGlzIHVzZWQgYnkgbWFueSBkaWZmZXJlbnQgc3Bva2VuIA0K
bGFuZ3VhZ2UgZ3JvdXBzLiAgQWNjb3JkaW5nIHRvIFtEZUZyYW5jaXMgMTk4OV0sIGh1bWFuIHNj
cmlwdHMNCmNhbiBiZSBvcmdhbml6ZWQgaW50byB0aHJlZSBncm91cHMgZm9yIHRoZWlyIHBob25l
dGljIA0KY2hhcmFjdGVyaXN0aWNzOiANCjEuIFN5bGxhYmljIHN5c3RlbXMsIGZvciBleGFtcGxl
LCBDaGluZXNlLCBKYXBhbmVzZSwgTWF5YSBhbmQgWWk7IA0KMi4gQ29uc29uYW50YWwgc3lzdGVt
cywgaWUuIEhlYnJldywgQXJhYmljIGFuZCBJbmRpYW4gbGFuZ3VhZ2VzOyANCmFuZCAzLiBBbHBo
YWJldGljIHN5c3RlbXMsIGluY2x1ZGluZyBHcmVlaywgTGF0aW4sIEN5cmlsbGljLCANCktvcmVh
biBhbmQgRW5nbGlzaC4gIEFscGhhYmV0aWMgc3lzdGVtcyBjYW4gYmUgdW5pZmllZCBieQ0KZW1i
ZWRkaW5nIHNvbWUgZGlmZmVyZW5jZXMgdW5kZXIgdGhlIGhhdCBvZiBtbmVtb25pYyANCnJlcHJl
c2VudGF0aW9uIG9mIGxhbmd1YWdlIHN5bWJvbHMsIHNvIHRoYXQgdGhlIEZyZW5jaCAndScgaXMg
DQpwZXJtaXR0ZWQgdG8gaGF2ZSBhIGRpZmZlcmVudCBzb3VuZCB2YWx1ZSBmcm9tIHRoZSBFbmds
aXNoICd1Jy4NCg0KTWFwcGluZyBhIGNvbnNvbmFudGFsIHN5c3RlbSB0byBhbiBhbHBoYWJldCBz
eW1ib2wgc2V0IGlzLCBlc3NlbnRpYWxseQ0KZW1iZWRkaW5nIHNvbWUgcGhvbmV0aWMgZGlmZmVy
ZW5jZXMsIHVzaW5nIGEgTGF0aW4gbW5lbW9uaWMgaGF0Lg0KQWRkaXRpb25hbGx5LCB0aGVyZSBp
cyB0aGUgcXVlc3Rpb24gb24gaG93IHRvIHJlcHJlc2VudCB0aGUgdm93ZWxzDQpvZiB0aGUgbGFu
Z3VhZ2UuIFR1cmtleSBoYXMgcHJvdmlkZWQgYW4gYW5zd2VyIHRvIHRoaXMgcXVlc3Rpb24uDQoN
CkFzIHRvIHVuaWZ5aW5nIGEgc3lsbGFiaWMgc3lzdGVtIHdpdGggYW4gYWxwaGFiZXQgc3lzdGVt
LCB0d28gaXNzdWVzIA0KbmVlZCB0byBiZSBhZGRyZXNzZWQuICBUaGUgZmlyc3QgaXMgcmV2ZXJz
aWJpbGl0eSBmcm9tIHRoZSANCmFscGhhYmV0aWMgc3lzdGVtIGJhY2sgdG8gdGhlIHN5bGxhYmlj
IHN5c3RlbSwgYW5kIHRoZSBzZWNvbmQgaXMgIA0KZXhwcmVzc2liaWxpdHkgd2l0aCB0aGUgYWxw
aGFiZXQgc3lzdGVtIG9mIGFkZGl0aW9uYWwgaW5mb3JtYXRpb24gDQppbmNsdWRlZCBpbiB0aGUg
c3lsbGFiaWMgc3lzdGVtLiANCiANClVuaWZpY2F0aW9uIG9mIHN5bWJvbCBzeXN0ZW1zIGFsd2F5
cyBicmluZ3MgYWJvdXQgc29tZSBsb3NzIGZyb20gDQp0aGUgb3JpZ2luYWwgc3lzdGVtcywgZXNw
ZWNpYWxseSBpbiB0aGlzIGZhc3QgZ3Jvd2luZyBpbnRlcm5ldA0KZXJhLCBhbmQgdGhlIG5hdGl2
ZSBsYW5ndWFnZSBvZiBhIGhvdXNlaG9sZCBjYW4gYmUgbG9zdCBpbiBvbmx5IG9uZSANCmdlbmVy
YXRpb24gaW4gYSBsb2NhbGl6ZWQgYmlsaW5ndWFsIGVudmlyb25tZW50LiBJbiBvcmRlciB0byAN
CnJldGFpbiB0aGUgY29sb3JmdWwgaGVyaXRhZ2Ugb2YgdGhlIHdvcmxkLCBtZWFucyB0byBwcm92
aWRlIGVhc3kNCnJlZmVyZW5jZSB0byB0aGUgb3JpZ2luYWwgc3lzdGVtIHNob3VsZCBiZSBpbXBs
ZW1lbnRlZC4NCg0KVGhlIHByb3Bvc2VkIHNvbHV0aW9uIGlzIGNhbGxlZCBTdGVwQ29kZSwgZm9y
IGl0cyBwcmlvcml0aXplZA0Kc3RlcHMgaW4gc3VjaCBhIFJvbWFuaXphdGlvbiBwcm9jZWR1cmUu
IEZpcnN0LCBzcGVjaWZ5IHRoZSANCnBob25ldGljIGRpZmZlcmVuY2VzIHRvIGJlIGVtYmVkZGVk
IGluIHRoZSByZXByZXNlbnRhdGlvbiwgDQp3aGVyZSBhbiBJbnRlcm5hdGlvbmFsIFBob25ldGlj
IEFscGhhYmV0IChJUEEpIGRlc2NyaXB0aW9uIG9mIA0KdGhlIGVtYmVkZGVkIGRpZmZlcmVuY2Vz
IHNoYWxsIGJlIHJlY29yZGVkLiBTZWNvbmQsIGlmIHRoZSANClJvbWFpemVkIGVtYmVkZGluZyBp
cyBub3Qgc3VmZmljaWVudCB0byBjb3ZlciB0aGUgZGlmZmVyZW5jZXMsIA0KdGhlbiBleHRlbmQg
dGhlIG1hcHBpbmcgc3BhY2UgdG8gYSAyNngxMCB0YWJsZSBmb3Igc2Vjb25kYXJ5IA0KcGhvbmV0
aWMgZWxlbWVudHMgd2hpY2ggY2FuIG5vdCBiZSBlbWJlZGRlZCB1bmRlciB0aGUgTGF0aW4gDQpt
bmVtb25pYyBoYXQuIFRoaXJkLCBpZiB0aGUgMjZ4MTAgc3BhY2UgaXMgbm90IHN1ZmZpY2llbnQs
IHRoZW4gDQpsaW5lYXJpemUgdGhlIHN5bWJvbCBieSBzcGVjaWZpbmcgZWFjaCBvZiBpdHMgY29t
cG9uZW50cy4gVGhpcyANCmxhc3QgcGFydCBtYXkgYmVjb21lIHJlY3Vyc2l2ZS4gVGhpcyBvcGVu
IGVuZGVkIHNvbHV0aW9uIG5vdCBvbmx5IA0KcHJvdmlkZXMgYSBwYXRoIHRvIHVuaWZ5IGEgbGFy
Z2Ugc3lsbGFiaWMgc3lzdGVtIHVzaW5nIGFuIGFscGhhYmV0IA0Kc3lzdGVtLCBidXQgYWxzbyBl
bnN1cmVzIHRoYXQgbW9yZSBzZW1hbnRpY2FsbHkgc3BlY2lmaWMgc3ltYm9scywgDQpzdWNoIGFz
IHRyYWRlbWFya3MgYW5kIGxvZ29zLCBjYW4gYmUgcmVwcmVzZW50ZWQgb25saW5lIGFuZCBzb3J0
ZWQgDQpmb3Igc3BlZWR5IHJlZmVyZW5jaW5nLiBEdWUgdG8gaXRzIHN0ZXAgbmF0dXJlLCB0aGUg
cmVwcmVzbmV0YXRpb24NCmNhbiAoYW5kIHNob3VsZCkgc3RvcCBmb3IgZWFjaCBzeW1ib2wsIGFz
IHNvb24gYXMgdGhlIHN5bWJvbCBjYW4gDQpiZSBpZGVudGlmaWVkIHdpdGhpbiBpdHMgZGVzaWdu
YXRlZCBjb250ZXh0LiBGb3IgZXhhbXBsZSwgDQoieGluemh1cWluZ2h1YTEyMTJxaW4xamluMGdl
MWdlMHNodWkxcWluZzBodWEyc2hpMC5jb20iLCBpcyBhIA0KdW5pcXVlIGV4cHJlc3Npb24gcmVz
dWx0ZWQgZnJvbSB0d28gY29tcGxldGUgaXRlcmF0aW9ucyBvZiBhcHBseWluZyANClN0ZXBDb2Rl
IHRvIGZvdXIgY29kZXBvaW50cyBvZiBbSVNPMTA2NDZdLCB3aGlsZSBvbmUgY29tcGxldGUgDQpz
dGVwIHdvdWxkIHJlc3VsdCBpbiAieGluemh1cWluZ2h1YTEyMTIiLCB3aGljaCBpcyBtb3N0IGxp
a2VseSANCnN1ZmZpY2llbnQgZm9yIGlkZW50aWZpbmcgYSBzaG9ydCB0cmFkZW5hbWUuIEZvciBh
IGxvbmdlciANCnRyYWRlbmFtZSB0aGUgZGlnaXRzIG1heSBiZSB0cnVuY2F0ZWQsIGFuZCB0aGUg
bWV0aG9kIHJlc2VtYmxlcyANCnRyYW5zbGl0ZXJhdGlvbiBvZiBhIGhvc3RuYW1lIHN1Y2ggdGhh
dCBhIENKSyBzdHJpbmcgYXBwZWFycyBhcyANCmEgbm9ybWFsIHJlYWRhYmxlIFJvbWFuaXplZCBl
eHByZXNzaW9uLCBzdWNoIGFzICJ4aW56aHVxaW5naHVhIiBvZiANCnRoZSBzYW1lIGV4YW1wbGUg
YWJvdmUuICBGb3IgYXBwbHlpbmcgU3RlcENvZGUgdG8gaG9zdG5hbWVzLCAgDQpleGNlcHQgZm9y
IHRlcm1pbm9sb2d5IGRlZmluaXRpb25zLCB0aGlzIGRvY3VtZW50IHdpbGwgbGltaXQgdGhlIA0K
ZGlzY3Vzc2lvbiB0byB0aGUgZmlyc3QgdHdvIG9mIHRob3NlIHRocmVlIHBhcnRzLiANCg0KVGhl
IElETiBXRydzIGNvbXBhcmlzb24gZG9jdW1lbnQgW0lETkNvbXBdIGRlc2NyaWJlcyB0aHJlZSBw
b3RlbnRpYWwNCm1haW4gYXJjaGl0ZWN0dXJlcyBmb3IgSUROOiBhcmNoLTEgKGp1c3Qgc2VuZCBi
aW5hcnkpLCBhcmNoLTIgKHNlbmQNCmJpbmFyeSBvciBBU0NJSSBDb21wYXRpYmxlIEVuY29kaW5n
LCBBQ0UpLCBhbmQgYXJjaC0zIChqdXN0IHNlbmQgQUNFKS4NClN0ZXBDb2RlIGlzIGFuIEFDRSB0
aGF0IGNhbiBiZSB1c2VkIHdpdGggcHJvdG9jb2xzIHRoYXQgbWF0Y2ggYXJjaC0yIA0Kb3IgYXJj
aC0zLiANCiAgDQpUaGUgU3RlcENvZGUgcHJvdG9jb2wgaGFzIHRoZSBmb2xsb3dpbmcgZmVhdHVy
ZXM6DQoNCi0gVGhlcmUgaXMgZXhhY3RseSBvbmUgd2F5IHRvIGNvbnZlcnQgaW50ZXJuYXRpb25h
bGl6ZWQgaG9zdCBwYXJ0cw0KdG8gYW5kIGZyb20gTGFuZ3VhZ2UgdGFnZ2VkIEFDRSBlbmNvZGVk
IHN0cmluZ3MuIEl0IHBlcm1pdHMgDQpkaWZmZXJlbnQgc2NyaXB0IHRhZ3MgdG8gYWNjZXNzIHRo
ZSBzYW1lIGdseXBoIGluIFtJU08xMDY0Nl0gc2ltaWxhciANCnRvIHRoZSBtZXRob2QgdXNlZCBm
b3Igc2VhcmNoaW5nIGJvb2tzIGluIGEgbGlicmFyeSwgc3VjaCB0aGF0IENKSyANCmNoYXJhY3Rl
ciBzZXQgbWF5IGJlIGFjY2Vzc2VkIGJ5IGRpZmZlcmVudCBsYW5ndWFnZSB1c2VycyB3aXRoIA0K
ZGlmZmVyZW50IGhvc3RuYW1lcy4gV2hlcmUgZWFjaCBpZiB0aGUgaG9zdG5hbWVzIGFsd2F5cyBp
cyBhIHVuaXF1ZSANCmV4cHJlc3Npb24gb24gdGhlIGludGVybmV0LiAgSWYgYW4gaW5wdXQgc3Ry
aW5nIGNhbiBub3QgbWF0Y2ggc3VjaCANCmEgaG9zdG5hbWUsIHRoZW4gaXQgaXMgY29uc2lkZXJl
ZCBhcyB1c2VyIGlucHV0IGVycm9yLg0KDQotW25hbWVwcmVwXSBhcHBsaWNhYmxlIHRvIFVOSUNP
REUgYW5kIG90aGVyIGNvcnJlc3BvbmRpbmcgDQpsb2NhbCBjb2Rpbmcgc3RhbmRhcmRzLg0KDQot
W0lETiBUYWddIGluY2x1ZGVzIGVhY2ggbGFuZ3VhZ2UgdGFnIGFuZCBpdHMgY29ycmVzcG9uZGlu
ZyANCmNvZGUgYmxvY2tzIG9mIFVOSUNPREUgYW5kIG90aGVyIGxvY2FsIGNvZGluZyBzdGFuZGFy
ZHMuIA0KDQotW01uZW1vbmljc10gaW5jbHVkZXMgbGFuZ3VhZ2UgdGFncywgbG9jYWwgc2NyaXB0
cyB0byBMYXRpbiANCmFscGhhYmV0IHN5bWJvbCBtYXBwaW5nLCBhbmQgSVBBIHBob25ldGljIHZh
bHVlIGRlc2NyaXB0aW9uIG9mIA0KZWFjaCBwaG9uZXRpYyBzeW1ib2wgb2YgYSBsYW5ndWFnZSBz
Y3JpcHQuIEl0IHNoYWxsIGJlIGEgUm9zZXR0YSANClN0b25lIG9mIHRoZSBpbnRlcm5ldC4NCg0K
LSBIb3N0IHBhcnRzIGhhdmUgbm8gaW50ZXJuYXRpb25hbCBnbHlwaHMgYnV0IFVTLUFTQ0lJLiBU
aGUgDQpTdGVwQ29kZSBwcm9jZWR1cmUgU0hPVUxEIGJlIGFmdGVyIFtuYW1lcHJlcF0gd2hpY2gg
aGFzIHByZXBhcmVkIA0KdGhlIGhvc3RuYW1lIHBhcnRzIGluIGFwcGxpY2FibGUgY29kZSBzdGFu
ZGFyZHMuDQoNCi0gRm9yIGFwcGxpY2FibGUgdGFncywgbG9jYWwgZGlzcGxheSBjb2RlcyBvZiBk
aWZmZXJlbnQNCmNvZGUgc3RhbmRhcmRzIHdpdGggY29ycmVzcG9uZGluZyByZWdpc3RlcmVkIGhv
c3RuYW1lcyBTSE9VTEQNCmJlIHJldGFpbmVkIGZvciBpbnF1aXJpZXMgZnJvbSBvdGhlciBJRE4g
aG9zdHMsIGFuZCByZXF1ZXN0IGZvcg0KdGhlICJyZWZlcmVuY2UgdG8gYmUgc2VudCIgcHJvdG9j
b2wgU0hPVUxEIGJlIGRyYWZ0ZWQuDQogDQotIE5hbWVzIHVzaW5nIFN0ZXBDb2RlIGhhdmUgbGVu
Z3RocyBwcm9wb3J0aW9uYWwgdG8gdGhlIG51bWJlcg0Kb2YgZ2x5cGhzIGluIHRoZSBuYW1lcyB0
aGVtc2VsdmVzIHBsdXMgdGhlIGxhbmd1YWdlIHRhZy4gIA0KSG93ZXZlciwgU3RlcENvZGUgZm9y
IGFsbCB0aGUgbm9uLUxhdGluIHBob25ldGljIGdseXBocyBTSE9VTEQNCmJlIGNvbmZpbmVkIHdp
dGhpbiB0d28gb2N0ZXRzLCBzaW5jZSBhbGwgdGhlIGN1cnJlbnQgcGhvbmV0aWMgDQpiYXNlZCBz
Y3JpcHRzIGNhbiBiZSByZXByZXNlbnRlZCB3aXRoaW4gdHdvIG9jdGV0cyBhbmQgaXRzDQptbmVt
b25pYyByZXByZXNlbnRhdGlvbiBTSE9VTEQgYmUgcHJlc2VydmVkLiBGb3IgYSByZWxhdGl2ZWx5
IGxvbmcNCkNKSywgWWkgYW5kIEhhbmd1bCBnbHlwaCBzcXVlbmNlLCBzYXkgYWJvdmUgdGVuIGds
eXBocywgdGhlIGF2ZXJhZ2UgDQpsZW5ndGggcGVyIGdseXBoIGlzIGFib3V0IDMuNyBMYXRpbiBs
ZXR0ZXJzLg0KDQotIFRoaXMgc3BlY2lmaWNhdGlvbiBhbGxvd3Mgc3RhbmRhcmQgY29tcHJlc3Np
b24gb3Igc2VjdXJpdHkgDQp0cmVhdG1lbnQgY29tcGF0aWJsZSB3aXRoIGV4aXN0aW5nIGhvc3Ru
YW1lcy4NCg0KSXQgaXMgaW1wb3J0YW50IHRvIG5vdGUgdGhhdCB0aGUgZm9sbG93aW5nIHNlY3Rp
b25zIGNvbnRhaW4gbWFueQ0Kbm9ybWF0aXZlIHN0YXRlbWVudHMgd2l0aCAiTVVTVCIgYW5kICJN
VVNUIE5PVCIuIEFueSBpbXBsZW1lbnRhdGlvbg0KdGhhdCBkb2VzIG5vdCBmb2xsb3cgdGhlc2Ug
c3RhdGVtZW50cyBleGFjdGx5IGlzIGxpa2VseSB0byBjYXVzZQ0KZGFtYWdlIHRvIHRoZSBJbnRl
cm5ldCBieSBjcmVhdGluZyBub24tdW5pcXVlIHJlcHJlc2VudGF0aW9ucyBvZg0KaG9zdG5hbWVz
Lg0KDQoxLjIgQXV0aG9yJ3MgRGlzY2xhaW1lcg0KDQpUaGlzIGRvY3VtZW50IGlzIGZvciBjb2xs
ZWN0aW5nIGFuIGludGVybmF0aW9uYWwgY28tYXV0aG9yc2hpcCANCm9mIHRoZSBJRE4gV0csIHRv
IHByb3Bvc2UgYSBzY3JpcHQtc3BlY2lmaWMgUm9tYW5pemF0aW9uIGVuY29kaW5nDQpzdGFuZGFy
ZCBmb3IgYW4gaW50ZXJuYXRpb25hbCB0cmFkZW5hbWUgc29sdXRpb24gb24gdGhlIGludGVybmV0
Lg0KU2luY2UgdGhlIG1ham9yaXR5IG9mIFVOSUNPREUgc3ltYm9scyBoYXZlIFJvbWFuaXplZCBu
YW1lcyANCnNwZWNpZmllZCBpbiBVTklDT0RFIHN0YW5kYXJkIGFscmVhZHksIHRoZSBhZGRpdGlv
bmFsIHdvcmsgbmVlZGVkDQppcyB0byBzZWxlY3QgZWFjaCBzeW1ib2wsIGV4Y2x1ZGluZyBmb250
IG9yIGNhc2UgdmFyaWF0aW9ucywgdG8gYmUgDQpyb21hbml6ZWQgb250byBMYXRpbiBhbHBoYWJl
dCBmb3IgRE5TIGVuY29kaW5nIHN0YW5kYXJkLiBUaGUgbW9zdCANCnRlY2huaWNhbGx5IGRpZmZp
Y3VsdCBwYXJ0IG9mIHRoaXMgcHJvcG9zYWwgaXMgdG8gY29udmVydCBhIA0Kcm9tYW5pemVkIENK
SyBhbmQgSGFuZ3VsIHN0cmluZyBiYWNrIHRvIGl0cyBjb2RlcG9pbnRzIG9mIA0KZGlzcGxheSBj
b2RlIHN0YW5kYXJkIHN1cHBvcnRlZCBieSBpdHMgbG9jYWwgaG9zdCwgd2hlcmUgc3VjaCANCnBy
b2NlZHVyZXMgZXhpc3QgaW4gbWFueSBwdWJsaWMgZG9tYWlucy4gQSBzYW1wbGUgcHJvY2VkdXJl
IGluIEMgDQpsYW5ndWFnZSBmb3IgQ2hpbmVzZSBpcyBwcm92aWRlZCBpbiBBcHBlbmRpeCBELiAN
Cg0KMS4zIFRlcm1pbm9sb2d5DQoNClRoZSBrZXkgd29yZHMgIk1VU1QiLCAiU0hBTEwiLCAiUkVR
VUlSRUQiLCAiU0hPVUxEIiwgIlJFQ09NTUVOREVEIiwNCmFuZCAiTUFZIiBpbiB0aGlzIGRvY3Vt
ZW50IGFyZSB0byBiZSBpbnRlcnByZXRlZCBhcyBkZXNjcmliZWQgaW4NCiBbUkZDMjExOV0uDQoN
CkhleGFkZWNpbWFsIHZhbHVlcyBhcmUgc2hvd24gcHJlY2VkZWQgd2l0aCBhbiAiMHgiLiBGb3Ig
ZXhhbXBsZSwNCiIweGExYjUiIGluZGljYXRlcyB0d28gb2N0ZXRzLCAweGExIGZvbGxvd2VkIGJ5
IDB4YjUuIEJpbmFyeSB2YWx1ZXMNCmFyZSBzaG93biBwcmVjZWRlZCB3aXRoIGFuICIwYiIuIEZv
ciBleGFtcGxlLCBhIG5pbmUtYml0IHZhbHVlIG1pZ2h0DQpiZSBzaG93biBhcyAiMGIxMDExMDEx
MTEiLg0KDQpFeGFtcGxlcyBpbiB0aGlzIGRvY3VtZW50IHVzZSB0aGUgbm90YXRpb24gZnJvbSB0
aGUgVW5pY29kZSBTdGFuZGFyZA0KW1VuaWNvZGUzXSBhcyB3ZWxsIGFzIHRoZSBJU08gMTA2NDYg
bmFtZXMuIEZvciBleGFtcGxlLCB0aGUgbGV0dGVyDQoiYSIgbWF5IGJlIHJlcHJlc2VudGVkIGFz
IGVpdGhlciAiVSswMDYxIiBvciAiTEFUSU4gU01BTEwgTEVUVEVSIEEiLg0KDQpTdGVwQ29kZSBj
b252ZXJ0cyBzdHJpbmdzIGF0IGEgY2xpZW50IHNpdGUgd2l0aCBpbnRlcm5hdGlvbmFsaXplZCAN
CmNoYXJhY3RlcnMgaW50byBzdHJpbmdzIG9mIFVTLUFTQ0lJIHRoYXQgYXJlIGFjY2VwdGFibGUg
YXMgaG9zdCANCm5hbWUgcGFydHMgaW4gY3VycmVudCBETlMgaG9zdCBuYW1pbmcgdXNhZ2UuIFRo
ZSBmb3JtZXIgYXJlIGNhbGxlZA0KInByZS1jb252ZXJ0ZWQiIGFuZCBhICJnbHlwaCIgZm9yIGEg
c3ltYm9sIHJlcGVzZW50ZWQgYnkgb25lIA0KY29kZXBvaW50IGluIFtJU08xMDY0Nl0gb3IgImds
eXBocyIgZm9yIGEgc3RyaW5nIG9mIGdseXBocyBhbmQgdGhlIA0KbGF0dGVyIGFyZSBjYWxsZWQg
InBvc3QtY29udmVydGVkIi4NCg0KVGhlICJwcmUtY29udmVydGVkIiBzdHJpbmdzIGF0IGEgY2xp
ZW50IHNpdGUgbWF5IGJlIHJlcHJlc2VudGVkIA0KYnkgVW5pY29kZSwgR0IgY29kZSwgSklTIGNv
ZGUsIEJJRzUgYW5kIG90aGVycyB3aGljaCBtYXkgY29udGFpbiANCmZvbnQgaW5mb3JtYXRpb24u
ICBUaGVzZSBjb2RlIGZvcm1zIGFyZSByZWZlcnJlZCBhcyBsYW5ndWFnZSANCnNwZWNpZmljICJs
b2NhbGl6ZWQgY29kZXBvaW50cyIuICANCg0KVGhlIHByb3RvY29sIGNvbnRhaW5zIG9uZSBwcm9j
ZWR1cmUgYW5kIGNhbGxzIGZvciBhIG1pbmltdW0gDQpudW1iZXIgb2Ygc3ltYm9scyBvZiBhIGxh
bmd1YWdlIHRvIGJlIG1hcHBlZCBvbnRvIGEgTGF0aW4gDQphbHBoYWJldCBpbiBhIG1uZW1vbmlj
IG1hbm5lci4gRm9yIGxhbmd1YWdlcyB3aXRoIGEgbGFyZ2UgbnVtYmVyIA0Kb2YgZ2x5cGhzIGFu
ZCBpcyBpbXBvc3NpYmxlIHRvIG1hcCBvbnRvIGEgTGF0aW4gYWxwaGFiZXQgDQpkaXJlY3RseSwg
YSB0aHJlZSBsYXllcmVkIHNjaGVtZSBpcyBSRUNPTU1FTkRFRCwgYW5kIGEgbWluaW11bSANCnNl
dCBvZiBnbHlwaHMgb2YgYSBzY3JpcHQgd2hpY2ggYXJlIG9mdGVuIHVzZWQgYXMgcGFydHMgb2Yg
b3RoZXIgDQpnbHlwaHMgaXMgaWRlbnRpZmllZC4gVGhlIGdseXBocyBpbiB0aGUgc21hbGxlciBz
ZXQgc29tZXRpbWVzIA0KYXJlIGNhbGxlZCByYWRpY2Fscywgb3IgcGFydGljbGVzIG9mIGEgQ0pL
IGNoYXJhY3RlciwgYnV0IA0KbmVpdGhlciByZWZsZWN0cyB0aGUgbmF0dXJlIG9mIHRoZSBzZXQg
b2YgZ2x5cGhzIHdoaWNoIGFyZSBtb3N0IA0KZnJlcXVlbnRseSB1c2VkIGdseXBocyBieSB0aGVt
c2VsdmVzIGFuZCBhcmUgcGFydHMgb2Ygb3RoZXIgZ2x5cGhzLiANClRoZSBtaW5pbXVtIHNldCBv
ZiBnbHlwaHMgaXMgY2FsbGVkICJQaWFucGFuZyIsIGEgSGFuIHdvcmQgbWVhbmluZyANCiJhIGNo
YXJhY3RlciBzdGFuZGluZyBvbiB0aGUgc2lkZSIsIGEgY29tbW9uIHdvcmQgaW4gQ2hpbmVzZS4g
QSANCnNldCBvZiBhc3NvY2lhdGVkIGRlZmluaXRpb25zIGluIHRoaXMgYXJlYSBpcyBnaXZlbiBo
ZXJlOg0KInBhbmciIC0gYSBjaGFyYWN0ZXIgb24gdGhlIGxlZnQ7DQoiYmlhbiIgLSBhIGNoYXJh
Y3RlciBvbiB0aGUgcmlnaHQ7DQoidG91IiAgLSBhIGNoYXJhY3RlciBvbiB0aGUgdG9wOw0KImRp
IiAgIC0gYSBjaGFyYWN0ZXIgb24gdGhlIGJvdHRvbTsNCiJ4aW4iICAtIGEgY2hhcmFjdGVyIGlu
IHRoZSBtaWRkbGU7DQoia3VhbmciLSBhIGNvbnRhaW5lciBvciBhIGZyYW1lIGNoYXJhY3Rlci4N
ClNpbmNlIENKSyBjaGFyYWN0ZXJzIGFyZSB3cml0ZW4gZnJvbSBsZWZ0IHRvIHJpZ2h0IGFuZCBm
cm9tIHRvcCANCmRvd24sIG9mdGVuIHRoZSAicGFuZyIgaXMgdGhlIGZpcnN0IHBhcnQgb2YgYSBj
aGFyYWN0ZXIgdG8gYmUgdXNlZCANCmFzIHRoZSBrZXkgZm9yIHNlYXJjaGluZyBpbnRvIGRpY3Rp
b25hcmllcyBhbmQgaXMgcGFydGlhbGx5IG9yZGVyZWQgDQppbiBVTklDT0RFLCBzbyAicGFuZyIg
aXMgYWxzbyByZWZlcnJlZCBhcyByYWRpY2Fscy4NCg0KVGhlIHRocmVlIGxheWVycyBvZiBnbHlw
aHMgb2YgYSBsYXJnZSBsYW5ndWFnZSBzY3JpcHQgYXJlIA0KTGF5ZXIgb25lOiBwaG9uZXRpYyBn
bHlwaHMsIHdoaWNoIGNhbiBiZSBkaXJlY3RseSBtYXBwZWQgb250bw0KCWFuIGFscGhhYmV0aWMg
c3lzdGVtIHVuZGVyIHRoZSBMYXRpbiBtbmVtb25pYyBoYXQ7DQpMYXllciB0d286IGEgbWluaW11
bSBudW1iZXIgb2YgZnJlcXVlbnRseSB1c2VkIGdseXBocyANCgl3aGljaCBhcmUgYWxzbyB1c2Vk
IGFzIFBpYW5wYW5ncyBpbiBvdGhlciBnbHlwaHM7DQpMYXllciB0aHJlZTogdGhlIHJlc3Qgb2Yg
dGhlIGdseXBocyBpbiB0aGUgbGFuZ3VhZ2Ugc2NyaXB0Lg0KDQpUaGUgcHJvdG9jb2wgdXNlcyBV
Uy1BU0NJSSB0byBkZW5vdGUgdGhlIHBob25ldGljIGVsZW1lbnRzIG9mIA0KYSBzY3JpcHQgYW5k
IGNhbGxzIGZvciBzdGFuZGFyZGl6aW5nIHN1Y2ggYSBtYXBwaW5nIGZvciBlYWNoIA0Kc2NyaXB0
IHRhZy4gVGhlIHBob25ldGljIGVsZW1lbnRzIG9mIGEgZ2x5cGggaXMgY2FsbGVkICJzcGVsbGlu
ZyIgDQpvZiB0aGUgZ2x5cGggYW5kIGlzIGNhbGxlZCAic3RlbSIgZm9yIHRoYXQgb2YgYSAiUGlh
bnBhbmciLg0KDQpUaGUgcHJvdG9jb2wgc3BlY2lmaWVzIEFTQ0lJIENvbXBhdGlibGUgW0FDRV0g
RW5jb2RpbmcgbWFwcyBmb3IgDQptYWpvciBsYW5ndWFnZXMgYW5kIHByb3ZpZGVzIG1lYW5zIG9m
IGVtYm9kaW1lbnQgb2Ygc3VjaCANCmltcGxlbWVudGF0aW9uIHdpdGggQ2hpbmVzZSBzY3JpcHQg
YW5kIGhlcmUgaXMgcmVmZXJyZWQgdG8gYXMgYSANCiJsYW5ndWFnZSB0YWdnZWQgQUNFIiBwcm9j
ZXNzLCBvciAiVC1BQ0UiLiANCg0KMS40IElETiBzdW1tYXJ5DQoNClVzaW5nIHRoZSB0ZXJtaW5v
bG9neSBpbiBbSUROQ29tcF0sIFN0ZXBDb2RlIHNwZWNpZmllcyBhbiBBQ0UgZm9ybWF0IA0KZm9y
IGFyY2gtMiAoc2VuZCBiaW5hcnkgb3IgQUNFKSwgYW5kIGFyY2gtMyAoanVzdCBzZW5kIEFDRSku
DQoNClRoZSBjaGFyYWN0ZXJpc3RpYyBvZiBTdGVwQ29kZSBsZW5ndGggZGlzY3Vzc2VkIGFib3Zl
ICgxLjEgQ29udGV4dCkgDQppcyBhIHZhcmlhYmxlIGRlcGVuZGluZyBvbiB1c2VycycgY2hvaWNl
IGFtb25nIG1hbnkgZmFjdG9ycy4gSXQgDQpmaXRzIHdlbGwgd2l0aCBleGlzdGluZyBjb21wcmVz
c2lvbiBhbmQgc2VjdXJpdHkgdHJlYXRtZW50cy4gDQoNCkl0IGNhbGxzIGZvciBzdGFuZGFyZGl6
aW5nIHBob25ldGljIGVsZW1lbnRzIHdpdGhpbiBpdHMgdXNlciANCmxhbmd1YWdlIGdyb3VwcyBz
cGVjaWZpZWQgaW4gdGhlIFtJU08gNjM5XSwgd2hpbGUgYXNraW5nIHRoZSANCmludGVybmV0IGlu
ZHVzdHJ5IHRvIGVuZm9yY2UgdGhlIHN0YW5kYXJkIGFuZCBwcm92aWRpbmcgY3Jvc3MgDQpyZWZl
cmVuY2UgdG8gZGlmZmVyZW50IHNjcmlwdCB0YWdzIGludG8gVW5pY29kZSBzdGFuZGFyZC4NCg0K
Mi4gSG9zdCBQYXJ0IFRyYW5zZm9ybWF0aW9uDQoNCkFjY29yZGluZyB0byBbU1REMTNdLCBob3N0
IHBhcnRzIG11c3QgYmUgY2FzZS1pbnNlbnNpdGl2ZSwgc3RhcnQNCmFuZCBlbmQgd2l0aCBhIGxl
dHRlciBvciBkaWdpdCwgYW5kIGNvbnRhaW4gb25seSBsZXR0ZXJzLCBkaWdpdHMsIA0KYW5kIHRo
ZSBoeXBoZW4gY2hhcmFjdGVyICgiLSIpLiBUaGlzIGV4Y2x1ZGVzIGFueSANCmludGVybmF0aW9u
YWxpemVkIGNoYXJhY3RlcnMsIGFueSBmb250IHZhcmlhdGlvbnMsIENoaW5lc2UgDQpUcmFkaXRp
b25hbC9TaW1wbGlmaWVkIGNoYXJhY3RlciBzZXQgdmFyaWF0aW9ucywgYXMgd2VsbCBhcyBtYW55
IA0Kb3RoZXIgY2hhcmFjdGVycyBpbiB0aGUgQVNDSUkgY2hhcmFjdGVyIHJlcGVydG9pcmUuIEZ1
cnRoZXIsIA0KZG9tYWluIG5hbWUgcGFydHMgbXVzdCBiZSA2MyBvY3RldHMgb3Igc2hvcnRlciBp
biBsZW5ndGggDQppbmNsdWRpbmcgdGhlIGxhbmd1YWdlIHRhZy4gDQoNCjIuMSBOYW1lIHRhZ2dp
bmcNCg0KQWxsIHBvc3QtY29udmVydGVkIG5hbWUgcGFydHMgdGhhdCBjb250YWluIGludGVybmF0
aW9uYWxpemVkDQpjaGFyYWN0ZXJzIGJlZ2luIHdpdGggYSBsYW5ndWFnZSB0YWcgZGVmaW5lZCBl
aXRoZXIgaW4gW0lTTyA2MzktMi9UXSANCm9yIGxpc3RlZCBpbiBBcHBlbmRpeCBFIG9mIHRoaXMg
ZG9jdW1lbnQgaW4gdGhlIGZvcm0gb2YgInh4eC0iLCANCndoZXJlICJ4eHgiIGRlbm90ZSB0aGUg
bGFuZ3VhZ2Ugb3Igc2NyaXB0IGVuY29kZWQsIGl0IFNIT1VMRCANCnVzZSBhbiBbSVNPIDEwNjQ2
XSBkZWZpbmVkIHNjcmlwdCBmb3IgdGhlIHBob25ldGljIHN0YW5kYXJkIA0KaW1wbGVtZW50ZWQu
ICBUaGUgaGVyZWluIGxpc3RlZCBsYW5ndWFnZSB0YWdzIGFyZSB3cml0aW5nIHN5c3RlbXMgDQph
cyBvcHBvc3NlZCB0byBzcG9rZW4gbGFuZ3VhZ2VzIHNwZWNpZmllZCBpbiBbSVNPIDYzOV0gdGhv
dWdoIA0KdGhleSBhcmUgYmFzZWQgb24gc3Bva2VuIGxhbmd1YWdlcy4gRm9yIGV4YW1wbGUgInVz
YS0iIGZvciANClVTLUFTQ0lJIGlzIG5vdCBjb25zaWRlcmVkIGFzIGEgc3Bva2VuIGxhbmd1YWdl
IGFuZCBzbyBpdCBpcyANCm5vdCBpbmNsdWRlZCBpbiB0aGUgW0lTTyA2MzldLg0KDQpTaW5jZSBb
SVNPNjM5XSBkZWZpbml0aW9uIGJhc2VkIG9uIHNwb2tlbiBsYW5ndWFnZXMsIHdoaWxlIHNjcmlw
dA0KYmFzZSBkZWZpbml0aW9uIGhhdmUgYmVlbiBkZWZpbmVkIGluIFtJU08gMTA2NDZdLCBTdGVw
Q29kZSANCmltcGxlbWVudGF0aW9uIGFwcGxpZWQgdG8gbGFuZ3VhZ2VzIGRlZmluZWQgaW4gW0lT
TyAxMDY0Nl0gd2l0aA0KbGFiZWxzIGRlZmluZWQgaW4gW0lTTzYzOV0uIA0KDQpUaGUgcGhvbmV0
aWMgc3ltYm9scyBpbXBsZW1lbnRlZCBpbiB0aGUgZW5jb2RpbmcgTVVTVCBoYXZlIA0KYmVlbiBp
bmNsdWRlZCBpbiBbSVNPIDEwNjQ2XS4gDQoNCkEgbGFuZ3VhZ2UgdGFnIE1VU1QgYmUgcmVnaXN0
ZXJlZCB3aXRoIElBTkEgd2l0aCBjb2RlcG9pbnQgYmxvY2tzDQpvZiBVTklDT0RFIGFzc29jaWF0
ZWQgd2l0aCB0aGUgdGFnLCBmb3IgW25hbWVwcmVwXSB0byByZWNvZ25pemUsIA0KdG8gYXBwbHkg
QUNFIHByb2Nlc3MgYW5kIHRvIGF0dGFjaCB0aGUgdGFnIHRvIHRoZSBwb3N0LWNvbnZlcnRlZCAN
Cmhvc3RuYW1lIGFuZCBmb3IgYSByZWNlaXZpbmcgaG9zdCB0byByZXZlcnNlIGl0cyBob3N0bmFt
ZSBiYWNrIHRvIA0KZWl0aGVyIFVOSUNPREUgb3IgaXRzIGxvY2FsIGNvZGVwb2ludHMuIA0KDQpB
IHpvbmUgYWRtaW5pc3RyYXRvciBNQVkgc3RpbGwgY2hvb3NlIHRvIHVzZSAidXNhLSIgYXQgdGhl
IA0KYmVnaW5uaW5nIG9mIGEgaG9zdG5hbWUgcGFydCBldmVuIGlmIHRoYXQgcGFydCBkb2VzIG5v
dCBjb250YWluDQppbnRlcm5hdGlvbmFsaXplZCBjaGFyYWN0ZXJzLiBab25lIGFkbWluaXN0cmF0
b3JzIE1BWSBjcmVhdGUNCmhvc3QgcGFydCBuYW1lcyB0aGF0IGJlZ2luIHdpdGggInVzYS0iIHdo
aWNoIG1lYW5zIG5vIGNvbnZlcnNpb24NCmlzIGRvbmUgYW5kIGRpc3BsYXkgc3lzdGVtcyBTSE9V
TEQgaWdub3JlIGNvbnZlcnRpbmcgDQppbnRlcm5hdGlvbmFsaXplZCBjaGFyYWN0ZXJzIGJhY2sg
Zm9yIGRpc3BsYXkuDQoNCjIuMiBDb252ZXJ0aW5nIGFuIGludGVybmF0aW9uYWxpemVkIG5hbWUg
dG8gYSBULUFDRSBuYW1lIHBhcnQNCg0KVG8gY29udmVydCBhIHN0cmluZyBvZiBpbnRlcm5hdGlv
bmFsaXplZCBjaGFyYWN0ZXJzIGludG8gYSANClQtQUNFIG5hbWUgcGFydCwgdGhlIGZvbGxvd2lu
ZyBzdGVwcyBNVVNUIGJlIHBlcmZvcm1lZCBpbiB0aGUgDQpleGFjdCBvcmRlciBvZiB0aGUgc3Vi
c2VjdGlvbnMgZ2l2ZW4gaGVyZS4NCg0KMi4yLjEuIFRhZyBjaGVja2luZw0KSWYgYSBuYW1lIHBh
cnQgY29uc2lzdHMgZXhjbHVzaXZlbHkgb2YgY2hhcmFjdGVycyB0aGF0IGNvbmZvcm0gdG8NCnRo
ZSBob3N0bmFtZSByZXF1aXJlbWVudHMgaW4gW1NURDEzXSBvciB0aGUgc3RyaW5nICJ1c2EtIiwg
DQp0aGUgbmFtZSBNVVNUIE5PVCBiZSBjb252ZXJ0ZWQgdG8gVC1BQ0UuIFRoYXQgaXMsIGEgbmFt
ZSBwYXJ0IA0KdGhhdCBjYW4gYmUgcmVwcmVzZW50ZWQgd2l0aG91dCBULUFDRSBNVVNUIE5PVCBi
ZSBjaGFuZ2VkLiANClRoaXMgYWJzb2x1dGUgcmVxdWlyZW1lbnQgcHJldmVudHM6DQoJMS4gZG91
YmxlIGVuY29kaW5nIGZyb20gYSBjbGllbnQgb2YgdXNlciBrZXlib2FyZCBpbnB1dCANCgkgYW5k
IGEgc2VydmVyIHByb3ZpZGVyOw0KCTIuIG1lc3NpbmcgdXAgZXhpc3RpbmcgcmVnaXN0ZXJlZCBk
b21haW4gbmFtZXM7DQoJMy4gdGhlcmUgYmVpbmcgdHdvIGRpZmZlcmVudCBlbmNvZGluZ3MgZm9y
IGEgc2luZ2xlIEROUyANCglyZWdpc3RlcmVkIGhvc3RuYW1lOw0KCTQuIGludGVyZmVyaW5nIHdp
dGggcmVnaXN0ZXJlZCBnbHlwaHMgd2l0aCBtb3JlIHRoYW4gb25lDQoJcGhvbmV0aWMgc3RhbmRh
cmQsIHN1Y2ggYXMgQ2hpbmVzZSBzY3JpcHQuDQoNCklmIGFueSBjaGVja2luZyBmb3IgcHJvaGli
aXRlZCBuYW1lIHBhcnRzIChzdWNoIGFzIG9uZXMgdGhhdCBhcmUNCnByb2hpYml0ZWQgY2hhcmFj
dGVycywgY2FzZS1mb2xkaW5nLCBvciBjYW5vbmljYWxpemF0aW9uKSBpcyB0byANCmJlIGRvbmUs
IGl0IE1VU1QgYmUgZG9uZSBiZWZvcmUgZG9pbmcgdGhlIGNvbnZlcnNpb24gdG8gYSANClQtQUNF
IG5hbWUgcGFydCBhcyBpdCBpcyBzcGVjaWZpZWQgaW4gW25hbWVwcmVwXS4gDQoNCkNoYXJhY3Rl
cnMgb3V0c2lkZSB0aGUgZmlyc3QgcGxhbmUgb2YgY2hhcmFjdGVycyAodGhvc2Ugd2l0aA0KY29k
ZXBvaW50cyBhYm92ZSBVK0ZGRkYpIE1VU1QgYmUgcmVwcmVzZW50ZWQgdXNpbmcgc3Vycm9nYXRl
cywgDQphcyBkZXNjcmliZWQgaW4gdGhlIFVURi0xNiBkZXNjcmlwdGlvbiBpbiBbSVNPIDEwNjQ2
XS4NCg0KVGhlIGlucHV0IG5hbWUgc3RyaW5nIGNvbnNpc3RzIG9mIGNoYXJhY3RlcnMgZnJvbSB0
aGUgSVNPIDEwNjQ2DQpjaGFyYWN0ZXIgc2V0IGluIGJpZy1lbmRpYW4gVVRGLTE2IGVuY29kaW5n
LiBUaGlzIGlzIHRoZQ0KcHJlLWNvbnZlcnRlZCBzdHJpbmcuDQoNCjIuMi4yLiBDaGVjayB0aGUg
aW5wdXQgc3RyaW5nIGZvciBkaXNhbGxvd2VkIG5hbWVzDQoNCklmIHRoZSBpbnB1dCBzdHJpbmcg
Y29uc2lzdHMgb25seSBvZiBjaGFyYWN0ZXJzIHRoYXQgY29uZm9ybSB0byANCnRoZSBob3N0bmFt
ZSByZXF1aXJlbWVudHMgaW4gW1NURDEzXSwgb3IgdGhlIGlucHV0IHN0cmluZyBjb25zaXN0cyAN
CmEgbnVsbCBsYW5ndWFnZSB0YWcsIHRoZSBjb252ZXJzaW9uIE1VU1Qgc3RvcCB3aXRoIGFuIGVy
cm9yLg0KDQoyLjIuMy4gVC1BQ0UgZW5jb2RpbmcNCkZpbmQgdGhlIGNvcnJlc3BvbmRpbmcgdGFn
LCBULCB3aXRoIFtJRE4gVEFHXSBmb3IgYSBpbnB1dCBzdHJpbmcuIA0KSWYgYWxsIHRoZSBjb2Rl
cG9pbnRzIGFyZSBpbiB0aGUgZmlyc3QgdGFnIFgsIHRoZW4gVD0gWCwgaXQgDQoJaXMgYSB2YWxp
ZCBJRE47IA0Kb3RoZXJ3aXNlLCBUID0gZHVkLg0KDQpCcmFuY2ggdG8gVCwgZW5jb2RlIHRoZSBp
bnB1dCBzdHJpbmcgd2l0aCBwcm9jZWR1cmUgVCwgY29uZm9ybWluZyANCgl0byBbU1REMTNdLCBv
YnRhaW4gQUNFIHN0cmluZywgQS4gDQoNClByZS1wZW5kIHRoZSB0YWcsIFQtLCB0byBBQ0Ugc3Ry
aW5nLCBBLCB0byBvYnRhaW4gYSBULUFDRSBob3N0bmFtZS4NCg0KDQoyLjMuIFN0ZXBDb2RlIE1l
dGhvZA0KDQpTdGVwQ29kZSBzdGFydHMgYXQgYSBwaG9uZXRpYyByZXByZXNlbnRhdGlvbiB3aXRo
IExhdGluIGFscGhhYmV0DQpvZiBhIGdseXBoLiAgV2hlbiB0aGlzIGlzIG5vdCBzdWZmaWNpZW50
IGluIGlkZW50aWZ5IHRoZSBnbHlwaCwgDQppdCBzdXBwbGVtZW50cyB0aGUgcmVwcmVzZW50YXRp
b24gd2l0aCBhIGRpZ2l0LiBEdWUgdG8gdGhlIGZhY3QgDQp0aGF0IGFscGhhYmV0IGJhc2VkIHNj
cmlwdHMgY29ubmVjdCBzZXZlcmFsIHN5bGxhYmxlcyBpbnRvIG9uZSANCnNlbWFudGljIHVuaXQg
b3IgYSB3b3JkLCBpdCBub3JtYWxseSBpZGVudGlmaWVzIGEgd29yZCB1bmlxdWVseSANCndpdGhp
biB0aGUgbGFuZ3VhZ2UuIFdoaWxlIGEgY2hhcmFjdGVyLWZvcm0gYmFzZWQgc2NyaXB0IHN1Y2gg
DQphcyBDSkssIGNoYXJhY3Rlcml6ZWQgYnkgb25lIHN5bGxhYmxlIHBlciBnbHlwaCwgb2Z0ZW4g
Y2FuIG5vdCANCnVuaXF1ZWx5IGlkZW50aWZ5IGEgY2hhcmFjdGVyIGJ5IGl0cyBzeWxsYWJsZSBh
bG9uZSwgYnV0IGEgDQpzZXF1ZW5jZSBvZiBzeWxsYWJsZXMgd2lsbCBvZnRlbiBpZGVudGlmeSBh
IHN0cmluZyBvZiBjaGFyYWN0ZXJzIA0KdW5pcXVlbHkgd2l0aGluIHRoZSBsYW5ndWFnZSBpbiBh
IHNpbWlsYXIgd2F5IHdpdGggYWxwaGFiZXQgDQpsYW5ndWFnZXMuIFN0ZXBDb2RlIG9ic2VydmVz
IHN1Y2ggYSBwaGVub21lbm9uIGFuZCByZXByZXNlbnRzIGEgDQpwaHJhc2Ugb2YgYSBzeWxsYWJp
YyBsYW5ndWFnZSBhcyBvbmUgc2VtYW50aWMgdW5pdCBjb250YWluaW5nIA0KbW9yZSB0aGFuIG9u
ZSBzeWxsYWJsZSwgYW5kIGVuY291cmFnZXMgc3VjaCBhIHJlcHJlc2VudGF0aW9uIG9mIA0KYSBj
aGFyYWN0ZXIgc3RyaW5nLiBGb3IgZXhhbXBsZSwgdGhlIHN5bGxhYmljIHN0cmluZyAgDQoieGlu
IHpodSBxaW5nIGh1YSIgb2YgZm91ciBjaGFyYWN0ZXJzIGlzIHdyaXR0ZW4gaW4gdGhlIHByZWZl
cnJlZCANCmZvcm0gInhpbnpodXFpbmdodWEiLiANCg0KV2hlbiBMYXRpbiBhbHBoYWJldCBpcyBu
b3Qgc3VmZmljaWVudCB0byByZXByZXNlbnQgdGhlIHNvdW5kIG9mIGEgDQpnbHlwaCwgdGhlIHJl
cHJlc2VudGF0aW9uIGlzIHN1cHBsaW1lbnRlZCB3aXRoIGEgZGlnaXQsIGRlbm90aW5nIA0KYSBz
ZWNvbmRhcnkgcGhvbmV0aWMgY2hhcmFjdGVyaXN0aWMgb2YgdGhlIGdseXBoLCBvciB0aGUgcGhy
YXNlLiANClRvZ2V0aGVyLCB0aGUgZGVzY3JpYmVkIHByb2Nlc3MgZm9ybXMgdGhlIGZpcnN0IHN0
ZXAgb2YgU3RlcENvZGUgDQplbmNvZGluZywgYW5kIGlzIHRoZSBtb3N0IHZpc2libGUgcGFydCBv
ZiB0aGUgbWV0aG9kIGFzIHdlbGwuDQoNClN0ZXBDb2RlIHN0ZXBzOg0KUzEuMS4gUm9tYW5pemUg
dGhlIHByaW1hcnkgcGhvbmV0aWMgY2hhcmFjdGVyaXN0aWMgb2YgYSANCglnbHlwaC9waHJhc2U7
DQpTMS4yLiBTdXBwbGVtZW50IHRoZSBzZWNvbmRhcnkgcGhvbmV0aWMgY2hhcmFjdGVyaXN0aWMg
b2YgdGhlIA0KCWdseXBoIHdpdGggYSBkaWdpdC9kaWdpdHMuDQoNClRoZSBzZWNvbmQgc3RlcCBv
ZiBTdGVwQ29kZSBpcyBhcHBsaWVkIHRvIGNvbXBvbmVudHMgb2YgZWFjaA0KZ2x5cGgsIFBpYW5w
YW5nLCBpbiB0aGUgc2FtZSB3YXkgc3BlY2lmaWVkIGluIFMxLjEuDQpTMi4xLiBSb21hbml6ZSB0
aGUgcHJpbWFyeSBwaG9uZXRpYyBjaGFyYWN0ZXJpc3RpYyBvZiBhIFBpYW5wYW5nLCBCOw0KUzIu
Mi4gU3BlY2lmeSBob3cgdGhlIG5leHQgcGlhbnBhbmcgaXMgcmVsYXRlZCB0byB0aGUgY3VycmVu
dCANCglwaWFucGFuZywgQiwgd2l0aCBhIGRpZ2l0Ow0KUzIuMy4gSWYgdGhlIHBpYW5wYW5nIGNv
bnRhaW5zIGFub3RoZXIgcGlhbnBhbmcsIFggb2YgQiwgDQoJdGhlbiBnb3RvIFMyLjEgb2YgWCAo
YW5kIGl0IGlzIFMyKzEuMShYKSk7DQoJb3RoZXJ3aXNlIGdvdG8gdGhlIG5leHQgcGlhbnBhbmcs
IEIrMS4NCg0KMi4zLjEgIFN0ZXBDb2RlIHBob25ldGljIHN5bWJvbCB0YWJsZXMNCg0KQSBnbHlw
aCBvZiBhbHBoYWJldGljIGxhbmd1YWdlIGhhcyBhIHNvdW5kIHZhbHVlIGFzc29jaWF0ZWQgd2l0
aCANCml0LiAgVW5kZXIgdGhpcyBwcm9wb3NhbCwgYSBzZXQgb2Ygc291bmRzIHdpdGggYSBzaW1p
bGFyIHZhbHVlDQpmcm9tIGRpZmZlcmVudCBsYW5ndWFnZXMgU0hPVUxEIGJlIGFzc29jaWF0ZWQg
d2l0aCBhIGdseXBoIGluIA0KVVMtQVNDSUksIGFzIHNob3duIGluIEFwcGVuZGl4IEEuIA0KDQpB
IGdseXBoIG9mIGNvbnNvbmFudGFsIHN5c3RlbXMgYW5kIGEgcGhvbmV0aWMgZ2x5cGggb2Ygc3ls
bGFiaWMgDQpzeXN0ZW1zIFNIT1VMRCBiZSBkZXRlcm1pbmVkIGZvciBhIGJlc3QgZml0IG9udG8g
YW4gZXhpc3RpbmcgDQpzZXQgb2Ygc291bmQgdmFsdWVzIG9mIFVTLUFTQ0lJLiBbVU5JQ09ERV0g
c3RhbmRhcmQgDQpoYXMgc3BlY2lmaWVkIGEgcm9tYW5pemVkIG5hbWUgZm9yIGVhY2ggb2YgZ2x5
cGggaW4gdGhlIA0Kc3RhbmRhcmQuIFRoZSBtYXBwaW5nIE1BWSBiZSBiYXNlZCBvbiBzdWNoIGEg
cm9tYW5pemVkIG5hbWUuICANCg0KMi4zLjIuIFN0ZXBDb2RlIENvbmNlcHRpYWwgRGVmaW5pdGlv
biBmb3IgRGlnaXRzDQoNCldpdGggMjYgTGF0aW4gYWxwaGFiZXQgbGltaXQsIG1hbnkgbGFuZ3Vh
Z2VzIHBvc3Nlc3MgYSANCnNldCBvZiBzb3VuZCBlbGVtZW50cyB3aGljaCAgYXJlIG5vdCBwb3Nz
aWJsZSB0byBiZSBpbmNsdWRlZCwNCnRoZW4gdGhlIGV4Y2x1ZGVkIHNvdW5kIGVsZW1lbnRzIGFy
ZSB0aGUgc2Vjb25kYXJ5IHBob25ldGljIA0KZWxlbWVudHMsIGFuZCBTSE9VTEQgYmUgYXNzaWdu
ZWQgdG8gYWRkaXRpb25hbCBzeW1ib2wgMC05Lg0KDQoyLjMuMi4xIFNlY29uZGFyeSBTb3VuZCBW
YWx1ZXMgaW4gU3RlcCBvbmUgZW5jb2Rpbmc6DQoNCkFsdGhvdWdoIDI2eDEwIGlzIGEgdHdvIGRp
bWVuc2lvbmFsIG1hcCwgaXQgY2FuIGJlIGZpbGxlZCANCndpdGggbW9yZSB0aGFuIHR3byBwaG9u
ZXRpYyBhc3BlY3RzIG9mIGEgc2NyaXB0LiAgV2l0aCANCmluY3JlYXNlZCBjb21wbGV4aXR5LCB0
aGUgbW5lbW9uaWMgZWZmb3J0cyBkaW1pbmlzaCBncmFkdWFseS4gDQpGb3Igc2ltcGxpY2l0eSwg
Zm91ciBwaG9uZXRpYyBtYXBwaW5nIHJ1bGVzIFNIT1VMRCBiZQ0Kb2JzZXJ2ZWQ6IFIxLiBEaWFj
cml0aWMgbWFyayBtYXBwaW5nOyBSMi4gUGhvbmVtZSBNYXBwaW5nOyANClIzLiBPdmVyZmxvdyBj
b25zZWN1dGl2ZSBzbG90IG1hcHBpbmc7IFI0LiBQcmlvcml0eSANCmVsZW1lbnRzIG1hcHBpbmcu
DQoNCltSMV0gRGlhY3JpdGljIG1hcmsgbWFwcGluZy4gRm9yIHNvbWUgbGFuZ3VhZ2Ugc2NyaXB0
cyBhIA0Kc2Vjb25kYXJ5IHBob25ldGljIGVsZW1lbnRzIGhhdmUgdG8gYmUgbWFya2VkIGZvciB0
aGVpciANCnVzZXJzLiBGb3IgZXhhbXBsZSBFdXJvcGVhbiBzY3JpcHRzLCBhIHNpbXBsZSBUb25l
IG1hcmsNCm1hcHBpbmcgU0hPVUxEIGJlIHVzZWQsIHdoZXJlIHRoZSBkaWdpdHMgb25seSBkZW5v
dGUgY29tbW9uIA0KZGlhY3JpdGljIG1hcmtzIFtNYWNtaWxsYW45M10gYXMgdGhlIGZvbGxvd2lu
Zy4gDQogDQowCWxldHRlcnMgd2l0aCBubyB0b25lDQoxCWZsYXQvbWFjcm9uICgtKQ0KMglyaXNl
L2FjdXRlICgvKQ0KMwlkaXAvYnJldmUgKHYpDQo0CWRyb3AvZ3JhdmUgKFwpDQo1CXRocm93L2Np
cmN1bWZsZXggKF4pDQo2CXRocmlsbC90aWxkZSAofikNCjcJZGllcmVzaXMgKCIpDQo4CWNlZGls
bGEJKGhvb2spDQo5CXVzZXIgYXNzaWduZWQNCg0KVGhlIHBvc2l0aW9uIG9mIGEgc2ltaWxhciBt
YXJrcyBTSE9VTEQgc3RheSBpbiBpdHMNCnJlc3BlY3RpdmUgcG9zaXRpb24gZm9yIGVhc3kgcmVm
ZXJlbmNlIGNyb3NzIHNjcmlwdCANCmJvdW5kYXJ5IGFuZCBmb3IgdXNlcnMgbG9va2luZyBmb3Ig
cmVwbGFjZW1lbnQgbWFya3MuIA0KQSBGcmVuY2ggZGlhY3JpdGljIG1hcmsgYXNzaWdubWVudCBp
cyBpbiBbQXBwZW5kaXggQi4xXS4gDQoNCltSMl0gUGhvbmVtZSB0YWJsZSBtYXBwaW5nLCB3aGVy
ZSBlYWNoIGRpZ2l0IHNwZWNpZmllcyBhIA0KdmFyaWFudCBvZiBhIGJhc2UgcGhvbmVtZSwgYW5k
IGEgbWF4aW11bSBvZiBuaW5lIHZhcmlhbnRzIG1heSANCmJlIGFjY29tbW9kYXRlZC4gVGhpcyBy
dWxlIGhhcyBhIGJlc3QgbW5lbW9uaWMgcmVzdWx0IGNyb3NzIA0KZGlmZmVyZW50IHNjcmlwdHMu
IEZvciBleGFtcGxlLCBJUEEgc3ltYm9sIG1hcHBpbmcgW0FwcGVuZGl4IEIuMl0uDQoNCltSM10g
T3ZlcmZsb3cgU3ltYm9sIG1hcHBpbmctIHdoZXJlIHRoZSBzeW1ib2xzIFNIT1VMRCBmaWxsIA0K
aW4gb25seSBjb25zZWN1dGl2ZSBzbG90cyBpbiB0aGUgb3Bwb3NpdGUgZGlyZWN0aW9ucw0KaW4g
dGhlIHRhYmxlIGZvciBlYXNlIG9mIGluZGV4IGNvbXB1dGF0aW9uLCB3aGVyZSB0aGUgbWlkZGxl
IA0Kc2VjdGlvbiBvZiB0aGUgdGFibGUgU0hPVUxEIGJlIGxlZnQgZm9yIHVzZXIgc2VsZWN0ZWQg
DQpkZWZpbml0aW9ucy4gVGhpcyBydWxlIGlzIHN1aXRlZCB0d28gc2V0cyBvZiBjb3JyZXNwb25k
aW5nIA0Kc3ltYm9scyBvZiB0aGUgc2FtZSBzY3JpcHQsIGZvciBleGFtcGxlIENoaW5lc2UgaW4g
W0FwcGVuZGl4IEIuM10uDQoNCltSNF0gUHJpb3JpdHkgZWxlbWVudHMgbWFwcGluZy0gU2VsZWN0
aW5nIGEgc2V0IG9mIG9mdGVuIHVzZWQNCnN5bWJvbHMgdG8gYmUgcGxhY2VkIGluIHRoZSB0YWJs
ZS4gW0FwcGVuZGl4IEIuNF0NCg0KVGhlIGFib3ZlIGFzc2lnbm1lbnQgcnVsZXMgbWF5IGJlIHVz
ZWQgaW4gYSBjb21iaW5hdGlvbiBhY2NvcmRpbmcgDQp0byBhbiBvcmRlciBvZiB3ZWlnaHRzIGlu
IHN1Y2ggYW4gYXNzaWdubWVudC4gIFN1Y2ggYW4gb3JkZXINCm9mIHdlaWdodHMgU0hPVUxEIGJl
IHNwZWNpZmllZCBpbiB0aGUgZm9ybSBbUngtUnktUnotUjRdLiANCg0KMi4zLjIuMi4gRGlnaXRz
IGluIFN0ZXAgMiBlbmNvZGluZzoNCiANCkEgdW5pZmllZCBDSksgY2hhcmFjdGVyIGlzIG9mdGVu
IGEgY29tcG9zaXRpb24gb2Ygc2V2ZXJhbCBpbmRlcGVuZGVudCANCnN5bWJvbHMgb2YgdGhlIGxh
bmd1YWdlLiBJdCBpcyBwb3NzaWJsZSB0byBkZXNjcmliZSBhIENKSyBjaGFyYWN0ZXIgIA0KYnkg
cmVwcmVzZW50aW5nIGEgY2hhcmFjdGVyIHdpdGggb25seSBpdHMgcGFydHMvUGlhbnBhbmdzLiAg
DQpBbHRob3VnaCBpdCBjYW4gaWRlbnRpZnkgYSBjaGFyYWN0ZXIgdW5pcXVlbHksIG5vcm1hbGx5
IGl0IGlzIA0KYWNjb21wYW5pZWQgd2l0aCBhIG51bWJlciBvZiBydWxlcyB3aXRoIHRvbyBtYW55
IGV4Y2VwdGlvbnMNCmZvciB0aGUgbWFqb3JpdHkgb2YgdXNlcnMgdG8gY29tcHJlaGVuZC4gU3Rl
cENvZGUgZW5jb2RpbmcgaGFzIA0KcmVkdWNlZCB0aGUgY29tcGxleGl0eSBvZiB0aGUgcnVsZXMg
YnkgY29uc2lkZXJpbmcgYSBDSksgDQpjaGFyYWN0ZXIgYXMgYSBzaW1wbGUgZ3JpZCBvZiAxIHRv
IDEwIHVuaXRzLCBkZXBlbmRpbmcgb24gdGhlIA0KdXNlcidzIHZpZXdwb2ludC4gIE5hbWluZyB0
aGUgMSB0byAxMCB1bml0cyBpbiBhIGxpbmVhciBmYXNoaW9uIA0KcmVzdWx0cyBhIGxpbmVhciBy
ZXByZXNlbnRhdGlvbiBvZiB0aGUgZ2x5cGggb3IgaXRzIGVuY29kaW5nLiANClRoaXMgaXMgdXNl
ZCBhcyBzZWNvbmRhcnkgZW5jb2RpbmcgbW9zdCBvZiB0aGUgdGltZSwgd2hpbGUgDQpzb21ldGlt
ZXMgaXQgaGFzIHRvIGJlIHRoZSBwcmltYXJ5IHJlcHJlc2VudGF0aW9uLCB3aGVuIHRoZSANCmNv
cnJlY3Qgc291bmQgb2YgYSBjaGFyYWN0ZXIgaXMgbm90IGF2YWlsYWJsZSB0byB0aGUgdXNlcnMu
IA0KVGhlIGRpZ2l0cyBpbiBTdGVwIDIgYW5kIHRoZXJlYWZ0ZXIsIHNwZWNpZmluZyBob3cgYSBw
aWFucGFuZw0Kb2YgYSBnbHlwaCBvbiBpdHMgZ3JpZCBhcmUgcmVsYXRlZCB0byB0aGUgbmV4dCBw
aWFucGFuZywgYXJlIA0KY2FsbGVkIGxheW91dCBkaWdpdHMuIA0KDQpMYXlvdXQgZGlnaXRzIHNw
ZWNpZnkgdGhlIHJlbGF0aW9uIHRvIHRoZSBuZXh0IHBpYW5wYW5nIGluIGxpbmUuICANClRoZSBs
ZWZ0IGFuZCByaWdodCBkaXJlY3Rpb24gYXJlIGRlZmluZWQgYnkgYSB1c2VyJ3MgbGVmdCBvciAN
CnJpZ2h0IGhhbmQgd2hpbGUgc2l0dGluZyBpbiBmcm9udCBvZiBhIGRpc3BsYXkgc2NyZWVuIG9y
IGEgDQpwaWVjZSBvZiBwYXBlci4gDQoNClRoZSBnbHlwaCBsYXlvdXQgZGlnaXRzIGFyZToNCgkw
IC0gZW5kIG9mIGEgY2hhcmFjdGVyIG9yIGEgUGlhbnBhbmcNCgkxIC0gdG8gaXRzIHJpZ2h0DQoJ
MiAtIHRvIGl0cyB1bmRlcnNpZGUNCgkzIC0gdG8gY29udGFpbiB0aGUgZm9sbG93aW5nDQoJNCAt
IHRvIGRpdmlkZSB0aGUgZm9sbG93aW5nDQoJNSAtIHRvIGl0cyBsZWZ0DQoJNiAtIHRvIGl0cyB0
b3ANCg0KCVRoZSBmb2xsb3dpbmcgc2VsZWN0YWJsZSBkaWdpdHMgYXJlIHRvIHNwZWNpZnkgYWRk
aXRpb25hbCANCglnbHlwaHMgb2YgdGhlIHNjcmlwdCBhbmQgZGlyZWN0aW9ucyBvZiBsYXlvdXQu
DQoNCgk3IC0gdG8gb3ZlcmxheSBpdHNlbGYgd2l0aCBYIHRoZW4gdG8gaXRzIHJpZ2h0Ow0KCTgg
LSB0byBvdmVybGF5IGl0c2VsZiB3aXRoIFggdGhlbiB0byBpdHMgbGVmdDsNCgk5IC0gdG8gb3Zl
cmxheSBpdHNlbGYgd2l0aCBYIHRoZW4gdG8gaXRzIHVuZGVyc2lkZS4NCgkNClRoZSBwaWFucGFu
ZyBsYXlvdXQgc2NoZW1lIHRyYWRlcyBjb21wbGV4aXR5IG9mIGEgZ2x5cGggd2l0aA0KY29kZSBs
ZW5ndGgsIHN1Y2ggdGhhdCB0aGUgY29tcGxleGl0eSBjYW4gYmUgZWxpbWluYXRlZCB3aGVuDQp0
cnVuY2F0aW5nIHRoZSBjb2RlIGlzIHBlcm1pdHRlZC4NCg0KMi4zLjMuIFN0ZXBDb2RlIEZvcm1h
dA0KDQpGb3JtYXQgRGVmaW5hdGlvbjogQSBTdGVwY29kZSB1bml0IGlzIGEgc3RyaW5nIG9mIFtB
LVphLXowLTldDQpjaGFyYWN0ZXJzIHdpdGhvdXQgYW55IHdoaXRlIHNwYWNlcywgQkxBTkssIGlu
IGJldHdlZW4uIEZvciBlYWNoIA0KU3RlcENvZGUgdW5pdCwgdGhlcmUgYXJlIGRhdGEgZWxlbWVu
dHMgaW5kaWNhdGVkIGJ5ICIiLCB3aGljaCBpcyBhIA0KTVVTVCBzdXBwbGllZCBlbGVtZW50LCBh
bmQgW10gd2hlcmUgdGhlIGVsZW1lbnQgaXMgb3B0aW9uYWwsIA0KYW5kIC8gd2hlcmUgdGhlIGRh
dGEgaXMgc2VsZWN0YWJsZS4NCg0KU3ggc3RhbmRzIGZvciBwcmltYXJ5IHNvdW5kIHZhbHVlIG9y
IFNwZWxsaW5nIG9mIHh0aCBnbHlwaDsNClR4IHN0YW5kcyBmb3Igc2Vjb25kYXJ5IHNvdW5kIHZh
bHVlIG9yIHRvbmUgb2YgeHRoIGdseXBoOw0KUHkgc3RhbmRzIGZvciBTdGVtIGZvciB5dGggUGlh
bnBhbmc7DQpMeSBzdGFuZHMgZm9yIExheW91dCByZWxhdGlvbiBmcm9tIHkgdG8geSsxOw0KUHgu
eSBzdGFuZHMgZm9yIFN0ZW0gZm9yIFh0aCBnbHlwaCBhbmQgaXRzIHl0aCBQaWFucGFuZzsNCkx4
Lnkgc3RhbmRzIGZvciBMYXlvdXQgcmVsYXRpb24gZnJvbSBYdGggZ2x5cGggYW5kIGl0cyB5IHRv
IHkrMS4NCgkgDQoyLjMuMy4xLiBPbmUgZ2x5cGgNCgkiUyIiVCJbUDFdW0wxXVtQMl1bTDJdLi4u
W1B5XVswL0JMQU5LXQ0KDQpFeGFtcGxlOnhpbjENCgl4aW4xcWluMWppbjAgDQoNCjIuMy4zLjIu
IEdseXBocw0KIlMxUzJTMy4uLlN4IltUMVQyLi4uVHhdW1AxLjFdW0wxLjFdW1AxLjJdW0wxLjJd
Li4uW1AxLnldWzBdDQoJCVtQMi4xXVtMMi4xXVtQMi4yXVtMMi4yXS4uLltQMi55XVswXQ0KCQkJ
Li4uIA0KCQlbUHguMV1bTHguMV1bUHguMl1bTHguMl0uLi5bUHgueV1bMC9CTEFOS10NCg0KRXhh
bXBsZSBvZiBnbHlwaHMgb2YgZm91cjoNCgl4aW56aHVxaW5naHVhDQoJeGluemh1cWluZ2h1YTEy
MTINCgl4aW56aHVxaW5naHVhMTIxMnFpbg0KCXhpbnpodXFpbmdodWExMjEycWluMWppbjBnZTFn
ZTBzaHVpMXFpbmcwaHVhDQoJeGluemh1cWluZ2h1YTEyMTJxaW4xamluMGdlMWdlMHNodWkxcWlu
ZzBodWEyc2hpMA0KDQpXaGljaCB0aGVzZSBmaXZlIGVxdWl2YWxlbnQgU3RlcENvZGVzIGlzIHVz
ZWQsIGRlcGVuZHMgb24gd2hlcmUgDQppdCBpcyBzdG9yZWQsIHRoZSBzaXplIGFuZCB0eXBlIG9m
IHRoZSBkYXRhYmFzZSwgYXMgd2VsbCBhcyB3aGV0aGVyDQp0aGVyZSBleGlzdCBzaW1pbGFyIGhv
c3RuYW1lcyBpdCBoYXMgY29uZmljdCB3aXRoLiANCg0KMi40LiBTdGVwQ29kZSBFbmNvZGluZyBQ
cm9jZXNzDQoNCkdvIHRocm91Z2ggW25hbWVwcmVwXSwgY2hlY2tpbmcgZm9yIHByb2hpYml0ZWQg
Y2hhcmFjdGVycywgDQpjYXNlLWZvbGRpbmcsIG9yIGNhbm9uaWNhbGl6YXRpb24uIA0KDQpFaXRo
ZXIsIFN0ZXBDb2RlIG1heSBiZSBvYnRhaW5lZCBmcm9tIFVuaWNvZGUgYW5kL29yIG90aGVyIGxv
Y2FsDQpjb2RlcyB0byBTdGVwQ29kZSBnbHlnaC9waHJhc2UgY29udmVyc2lvbiB0YWJsZXMuIA0K
DQpPciwgaXQgaXMgaW5wdXQgZGlyZWN0bHkgZnJvbSBrZXlib2FyZHMsIHdoZXJlIGFuIGlucHV0
IA0KcHJvY2Vzc2luZyBtb2R1bGUgdG8gdmVyaWZ5IGNvcnJlY3RuZXNzIG9mIGludGVudGVkIGds
eXBocyBpcw0KbmVjZXNzYXJ5LiAoU2VlIEMgY29kZSBpbiBbQXBwZW5kaXggRC4xXSkNCg0KUHJl
cGVuZCBzY3JpcHQgdGFnIGluIHRoZSBmb3JtIG9mICJ4eHgtIiB0byBwb3N0LWNvbnZlcnRlZCAN
CnN0cmluZzsgIGZpbmlzaC4gVGhpcyBpcyB0aGUgaG9zdG5hbWUgcGFydCB0aGF0IA0KY2FuIGJl
IHVzZWQgaW4gRE5TIHJlZ2lzdHJhdGlvbiBhcyB3ZWxsIGFzIHJlc29sdXRpb24uIA0KDQoyLjUu
IENvbnZlcnRpbmcgYSBTdGVwQ29kZSBob3N0bmFtZSB0byBhbiBpbnRlcm5hdGlvbmFsaXplZCBu
YW1lDQoNClRoZSBwcm9jZXNzIGhhcyB0aHJlZSBwYXJ0cyB3aXRoIHNjcmlwdCB0YWcgdW50b3Vj
aGVkOg0KDQpQMS5JZiBhIGRvbWFpbiBuYW1lIHBhcnQgY29uc2lzdHMgbm8gc2NyaXB0IHRhZyBv
ciAidXNhLSJ0YWcsIA0KCXRoZW4gZ290byBQMzsNCglPdGhlcndpc2Ugc2VhcmNoIGZvciBwcm9j
ZXNzIG5hbWVkICJ4eHgiIGZyb20gU3RlcENvZGUgIA0KCQl0byBVbmljb2RlIG9yIG90aGVyIGNv
ZGUgY29udmVyc2lvbiwgb2J0YWluIHRoZSANCgkJY29ycmVzcG9uZGluZyBjb2Rlcy4gDQoJKEF0
IHRoaXMgcG9pbnQsIG9ubHkgYSBzeWxsYWJpYyBzeXN0ZW0gbWlnaHQgZmFpbC4pDQpQMi5JZiB0
aGUgY29ycmVzcG9uZGluZyBjb2RlIGlzIGV4aXQgdGhlbiBnb3RvIFN0ZXAgMzsNCglPdGhlcndp
c2UgZGVjb21wb3NlcyB0aGUgcG9zdC1jb252ZXJ0ZWQgc3RyaW5nIGludG8gYSBudW1iZXINCgkg
ICBvZiBpbmRpdmlkdWFsIGdseXBocyANCgkJc3BlY2lmaWVkIGluIHRoZSAiVCIgZmllbGQsIG9y
DQoJICAgCWJ5IHN5bGxhYmxlIHJlY29nbml0aW9uOyAoU2VlIFtBcHBlbmRpeCBELjJdKQ0KCVNl
YXJjaCBmb3IgZWFjaCBnbHlwaDsNCglJZiBhbnkgZ2x5cGggaXMgbm90IGZvdW5kIG9yIGlzIG5v
dCB1bmlxdWUsIA0KCQljb21wb3NlIGFuIGVycm9yIG1lc3NhZ2UgYW5kIA0KCQlSZXF1ZXN0IHRo
ZSBtaXNzaW5nIGdseXBocyB0byBiZSBzdXBwbGllZCANCgkJICAgZnJvbSB0aGUgc2VuZGVyIGVp
dGhlciBpbiB0aGUgZm9ybQ0KCQkgICBvZiBVbmljb2RlIG9yIA0KCQkJb3RoZXIgY29kZSBzdHJl
YW0gDQoJCQlvciBpbiBhIDI0eDI0IGJpdCBtYXAgc3RyZWFtLiANClAzLkRpc3BsYXkgYXZhaWxh
YmxlIGdseXBoLCB3aGVyZSBtaXNzaW5nIGdseXBoIGlzIHNob3duIHdpdGggU3RlcENvZGU7DQoJ
SWYgYXBwbGlhYmxlLCBzYXZlIHRoZSBjb3JyZXNwb25kaW5nIGhvc3RuYW1lIGFuZCBkaXNwbGF5
IGNvZGVzLiANCg0KMy4gU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMNCg0KTXVjaCBvZiB0aGUgc2Vj
dXJpdHkgb2YgdGhlIEludGVybmV0IHJlbGllcyBvbiB0aGUgRE5TLiBUaHVzLCBhbnkNCmNoYW5n
ZSB0byB0aGUgY2hhcmFjdGVyaXN0aWNzIG9mIHRoZSBETlMgY2FuIGNoYW5nZSB0aGUgc2VjdXJp
dHkgb2YNCm11Y2ggb2YgdGhlIEludGVybmV0LiBUaHVzLCBTdGVwQ29kZSBtYWtlcyBubyBjaGFu
Z2VzIHRvIHRoZSBETlMgDQppdHNlbGYuDQoNCkhvc3RuYW1lcyBhcmUgdXNlZCBieSB1c2VycyB0
byBjb25uZWN0IHRvIEludGVybmV0IHNlcnZlcnMuIFRoZQ0Kc2VjdXJpdHkgb2YgdGhlIEludGVy
bmV0IHdvdWxkIGJlIGNvbXByb21pc2VkIGlmIGEgdXNlciBlbnRlcmluZyBhDQpzaW5nbGUgaW50
ZXJuYXRpb25hbGl6ZWQgbmFtZSBjb3VsZCBiZSBjb25uZWN0ZWQgdG8gZGlmZmVyZW50DQpzZXJ2
ZXJzIGJhc2VkIG9uIGRpZmZlcmVudCBpbnRlcnByZXRhdGlvbnMgb2YgdGhlIGludGVybmF0aW9u
YWxpemVkDQpob3N0bmFtZS4gVGh1cyB0aGUgcmVzdHJpY3Rpb24gb2YgRE5TIG5hbWVzIHRvIGEg
c21hbGwgc3ltYm9sIHNldCBpcw0KbmVjZXNzYXJ5IGFuZCBlZmZlY3RpdmUsIHdoZXJlIGFkZGlu
ZyBhbnkgb3RoZXIgZGF0YSBmb3JtYXQgc3VjaCBhcyANClVURi04IG9ubHkgb3BlbnMgdGhlIHNl
Y3VyaXR5IGdhdGUgdG8gY29tcGxpY2F0aW9ucy4gIA0KDQo0LkludGVybmF0aW9uYWxpemF0aW9u
IGNvbnNpZGVyYXRpb25zDQoNClN0ZXBDb2RlIGlzIGRlc2lnbmVkIHNvIHRoYXQgZXZlcnkgaW50
ZXJuYXRpb25hbGl6ZWQgaG9zdG5hbWUgcGFydCBjYW4NCmJlIHJlcHJlc2VudGVkIGFzIG9uZSBh
bmQgb25seSBvbmUgRE5TLWNvbXBhdGlibGUgc3RyaW5nLiBJZiB0aGVyZQ0KYXJlIHR3byBkaWZm
ZXJlbnQgd2F5cyB0byBvYnRhaW4gdGhlIHNhbWUgZ2x5cGggb24gYSBkaXNwbGF5IGRldmljZSwN
CnRoZW4gdGhleSBhcmUgc3RpbGwgdHdvIGRpc3RpbmN0IGhvc3RuYW1lcywgd2l0aCBubyBiZWFy
aW5nIG9uIA0Kc2VjdXJpdHkgaXNzdWVzLiBJZiB0aGVyZSBpcyBhbnkgd2F5IHRvIGZvbGxvdyB0
aGUgc3RlcHMgaW4gdGhpcyANCmRvY3VtZW50IGFuZCBnZXQgdHdvIG9yIG1vcmUgZGlmZmVyZW50
IHJlc3VsdHMsIGl0IGlzIGRlY2F1c2Ugb2YgYW4gZXJyb3IgDQppbiB0aGUgZG9tYWluIG5hbWUg
cmVnaXN0cmF0aW9uIHByb2Nlc3MsIHdoZXJlIG9uZSBkb21haW4gbmFtZSByZWdpc3Rlcg0KZmFp
bHMgdG8gdXBkYXRlIG90aGVyIGRvbWFpbiBuYW1lIHJlZ2lzdGVyIHNlcnZlcnMgYWJvdXQgYSBu
ZXdseSANCnJlZ2lzdGVyZWQgYW5kIHdlbGwgcmVzZWFyY2hlZCBob3N0bmFtZS4gDQoNCjUuIFJl
ZmVyZW5jZXMNCg0KW0FwcGVuZGl4IEFdIEV4YW1wbGUgUGhvbmV0aWMgc3ltYm9scyB0byBMYXRp
biBzbWFsbCBsZXR0ZXIgbWFwcGluZw0KW0FwcGVuZGl4IEJdIFNlY29uZGFyeSBzb3VuZCB2YWx1
ZXMgdG8gZGlnaXRzIG1hcHBpbmcuDQpbQXBwZW5kaXggQ10gU3RlcENvZGUgbGF5b3V0IGRpZ2l0
IHNwZWNpZmljYXRpb24uDQpbQXBwZW5kaXggRF0gRXhhbXBsZSBDIGNvZGUgaW1wbGVtZW50YXRp
b24gb24gZW5jb2RpbmcgYW5kIGRlY29kaW5nLg0KW0FwcGVuZGl4IEVdIEV4YW1wbGUgb2YgSURO
IExhbmd1YWdlIHRhZ3MuDQoNCltBU0NJSV0gQW1lcmljYW4gTmF0aW9uYWwgU3RhbmRhcmRzIElu
c3RpdHV0ZSAoZm9ybWVybHkgVW5pdGVkDQpTdGF0ZXMgb2YgQW1lcmljYSBTdGFuZGFyZHMgSW5z
dGl0dXRlKSwgWDMuNCwgMTk2OCwgIlVTQSBDb2RlIGZvcg0KSW5mb3JtYXRpb24gSW50ZXJjaGFu
Z2UiLiAoQU5TSSBYMy40LTE5NjgpDQoNCltEZUZyYW5jaXMgMTk4OV0gSm9obiBEZUZyYW5jaXMs
ICJWaXNpYmxlIFNwZWVjaCAtIFRoZSBEaXZlcnNlIA0KCU9uZW5lc3Mgb2YgV3JpdGluZyBTeXN0
ZW1zIiwgMTk4OSwgSVNCTiAwLTgyNDgtMTIwNy03Lg0KDQpbRGljdGlvbmFyeTc5XSBCZWlqaW5n
IEZvcmllZ24gTGFuZ3VhZ2UgRGVwdC4sICJBIENoaW5lc2UtRW5nbGlzaCANCglEaWN0aW9uYXJ5
IiwgMTk3OSwgQksjIDkwMTcuODEwLg0KDQpbSUROQ09NUF0gICAiQ29tcGFyaXNvbiBvZiBJbnRl
cm5hdGlvbmFsaXplZCBEb21haW4gTmFtZSBQcm9wb3NhbHMiLA0KICAgICAgICAgICAgZHJhZnQt
aWV0Zi1pZG4tY29tcGFyZS0wMC50eHQsIEp1bmUgMjAwMCwgUC4gSG9mZm1hbi4NCg0KW0lETlJl
cV0gWml0YSBXZW56ZWwgYW5kIEphbWVzIFNlbmcsICJSZXF1aXJlbWVudHMgb2YgSW50ZXJuYXRp
b25hbGl6ZWQgDQoJRG9tYWluIE5hbWVzIiwgZHJhZnQtaWV0Zi1pZG4tcmVxdWlyZW1lbnRzLiBN
YXkgMjAwMS4pDQoNCltJRE4gVEFHXSBEcmFmdC1MaWFuYS1pZG4tdGFncywgSUROIExhbmd1YWdl
IHRhZ3MuDQoNCltJU082MzldW0lTTzYzOS0yL1RdIElTTy9JRUMgNjM5LTIgMjAwMSBDb2RlcyBm
b3IgdGhlIFJlcHJlc2VudGF0aW9uIG9mIA0KCU5hbWVzIG9mIExhbmd1YWdlcy4NCg0KW0lTTzEw
NjQ2XSAgSVNPL0lFQyAxMDY0Ni0xOjIwMDAgKG5vdGUgdGhhdCBhbiBhbWVuZG1lbnQgMSBpcyBp
bg0KICAgICAgICAgICAgcHJlcGFyYXRpb24pLCBJU08vSUVDIDEwNjQ2LTIgKGluIHByZXBhcmF0
aW9uKSwgcGx1cw0KICAgICAgICAgICAgY29ycmlnZW5kYSBhbmQgYW1lbmRtZW50cyB0byB0aGVz
ZSBzdGFuZGFyZHMuDQoNCltNYWNtaWxsYW45M10gVGhlIE1hY21pbGxhbiBWaXN1YWwgRGVzayBS
ZWZlcmVuY2UsIDE5OTMsIA0KCUlTQk4gMC0wMi01MzEzMTAteC4NCg0KW01uZW1vbmljc10gIkRy
YWZ0LUxpYW5hLWlkbi1tbmVtb25pY3MiLCBMYW5ndWFnZSBzeW1ib2xzIG9mIA0KCVtJU08xMDY0
Nl0gdG8gTGF0aW4gYWxwaGFiZXQgbWFwcGluZ3MgZm9yIHVuaWZpZWQgSUROIA0KCXN5bWJvbCBy
ZXByZXNlbnRhdGlvbi4NCg0KW1JGQzIyNzddICAgIklFVEYgUG9saWN5IG9uIENoYXJhY3RlciBT
ZXRzIGFuZCBMYW5ndWFnZXMiLA0KICAgICAgICAgICAgcmZjMjI3Ny50eHQsIEphbnVhcnkgMTk5
OCwgSC4gQWx2ZXN0cmFuZC4NCg0KW1JGQzIxMTldIFNjb3R0IEJyYWRuZXIsICJLZXkgd29yZHMg
Zm9yIHVzZSBpbiBSRkNzIHRvIEluZGljYXRlDQoJUmVxdWlyZW1lbnQgTGV2ZWxzIiwgTWFyY2gg
MTk5NywgUkZDIDIxMTkuDQoNCltTVEQxM10gUGF1bCBNb2NrYXBldHJpcywgIkRvbWFpbiBuYW1l
cyAtIGltcGxlbWVudGF0aW9uIGFuZA0KCXNwZWNpZmljYXRpb24iLCBOb3ZlbWJlciAxOTg3LCBT
VEQgMTMgKFJGQyAxMDM1KS4NCg0KW1VOSUNPREVdIFRoZSBVbmljb2RlIENvbnNvcnRpdW0sICJU
aGUgVW5pY29kZSBTdGFuZGFyZCIuIERlc2NyaWJlZCBhdA0KICAgICAgICAgICAgaHR0cDovL3d3
dy51bmljb2RlLm9yZy91bmljb2RlL3N0YW5kYXJkL3ZlcnNpb25zLy4NCg0KW1VOSUNPREUzMF0g
VGhlIFVuaWNvZGUgQ29uc29ydGl1bSwgIlRoZSBVbmljb2RlIFN0YW5kYXJkIC0tIFZlcnNpb24N
CiAgICAgICAgICAgIDMuMCIsIElTQk4gMC0yMDEtNjE2MzMtNS4gU2FtZSByZXBlcnRvaXJlIGFz
IElTTy9JRUMNCiAgICAgICAgICAgIDEwNjQ2LTE6MjAwMC4gRGVzY3JpYmVkIGF0IGh0dHA6Ly93
d3cudW5pY29kZS5vcmcvdW5pY29kZS8NCiAgICAgICAgICAgIHN0YW5kYXJkL3ZlcnNpb25zL1Vu
aWNvZGUzLjAuaHRtbC4NCg0KW1llOTVdIExpYW5hIFllLCAiQSBMYW5ndWFnZSBPcmllbnRlZCBD
aGluZXNlIEVuY29kaW5nIGZvciANCk11bHRpbGluZ3VhbCBDb21wdXRpbmcgRW52aXJvbm1lbnRz
IiwgaW4gIlByb2NlZWRpbmcgb2YgdGhlIDE5OTUgDQpJbnRlcm5hdGlvbmFsIENvbmZlcmVuY2Ug
b24gQ29tcHV0ZXIgUHJvY2Vzc2luZyBvZiBPcmllbnRhbA0KTGFuZ3VhZ2VzIiwgUGFnZSAzMjMu
DQoNCjYuIEFja25vd2xlZGdlbWVudHMNCg0KVGhlIGF1dGhvciBoYXMgcmV1c2VkIGV4aXN0aW5n
IElETiBkcmFmdCBkb2N1bWVudHMgYW5kIGxhbmd1YWdlIGFzIA0KbXVjaCBhcyBwb3NzaWJsZSB0
byBkZW1vbnN0cmF0ZSBkZWVwIHJlc3BlY3QgZm9yIHRoZSB3b3JrIGRvbmUgYnkgDQptZW1iZXJz
IG9mIHRoaXMgd29ya2luZyBncm91cC4gQW1vbmcgdGhlbSwgc3BlY2lhbCBjb21tZW50cyB3aGlj
aCANCmhhdmUgY29udHJpYnV0ZWQgdG8gaW1wcm92ZSB0aGlzIGRvY3VtZW50IHdlcmUgcmVjZWl2
ZWQgZnJvbSBKb2huIEMgDQpLbGVuc2luLCBFcmljIEJydW5uZXItV2lsbGlhbXMgYW5kIFdpbGxp
YW0gRGF2aXMuIEFhcm9uIElydmluZSBoYXMgDQpjb250cmlidXRlZCBFc3BlcmFudG8gc3BlY2lm
aWNhdGlvbnMuDQoNCjcuIElBTkEgQ29uc2lkZXJhdGlvbnMNCg0KVGhpcyBkb2N1bWVudCByZXF1
aXJlcyBJQU5BIGFjdGlvbiBmb3IgYXZhaWxpYmlsaXR5IG9mIGxhbmd1YWdlIHRhZywgDQphbmQg
cmVnaXN0cmF0aW9uIGZvciBlYWNoIHRhZyBhbmQgcG9zc2libHkgaXRzIHN1Yi1maWVsZCBmb3Ig
DQpwaG9uZXRpYyBzeXN0ZW0gdXNlZC4NCg0KOC4gQXV0aG9ycycgQ29udGFjdCBJbmZvcm1hdGlv
bg0KDQpMaWFuYSBZZQ0KWSZEIElTRw0KMjYwNyBSZWFkIEF2ZS4NCkJlbG1vbnQsIENBIDk0MDAy
LCBVU0EuDQooNjUwKSA1OTItNzA5Mg0KbGlhbmEueWRpc2dAanVuby5jb20NCg0KQWFyb24gSXJ2
aW5lLCBQaEQuIA0KPGFhcm9uLmlydmluZUBvcGVud2F2ZS5jb20+DQoNCkV4cGlyZXMgSmFudWFy
eSAyMDAyDQoNCg0KW0FwcGVuZGl4IEFdIFNhbXBsZSBQaG9uZXRpYyBTeW1ib2wgdG8gTGF0aW4g
YWxwaGFiZXQgbWFwcGluZw0KDQpUaGUgcGhvbmV0aWMgc3ltYm9scyBvZiBDaGluZXNlIGFyZSBC
b3BvbW9mbywgb3IgWmh1eWluIHN5bWJvbHMgDQpmcm9tIFUrMzEwNSB0byBVKzMxMmMsIHdoZXJl
IHRoZSBzb3VuZCB2YWx1ZSBtYXBwaW5nIGlzIHRyYW5zY3JpYmVkDQpmcm9tIFpodXlpbiBzdGFu
ZGFyZCBvZiAxOTQyIGFuZCBbRGljdGlvbmFyeSAxOTc5XS4gDQoNCkRlZmluaXRpb25zOg0KDQot
eCAJVGhlIHN5bWJvbCAneCcgb2NjdXJzIGF0IGVuZCBvZiBhIHVuaXQuDQp4IC8geQlCb3RoIHN5
bWJvbHMgYXJlIGFwcGxpY2FibGUuDQp4IFUrMzEwNSAnIAlBIHNlcXVlbmNlIG9mIHN5bWJvbHMg
d2hlcmUgdGhlcmUgaXMgbm8gZXF1aXZhbGVudA0KCUFTQ0lJIHJlcHJlc2VudGF0aW9uLCBhIFVu
aWNvZGUgcG9pbnQgd2l0aCBibGFua3MgYXMgDQoJZGVsaW1pdG9ycyBpcyB1c2VkLg0KDQoJTW5l
bW9uaWNzCVVuaWNvZGUJCUlQQSBkZXNjcmlwdGlvbg0KDQp6aG8tDQoJUGlueWluCQlCb3BvbW9m
bwlJUEENCgliCQlVKzMxMDUJCXANCglwCQlVKzMxMDYJCXAnDQoJbQkJVSszMTA3CQltDQoJZgkJ
VSszMTA4CQlmDQoJZAkJVSszMTA5CQl0DQoJdAkJVSszMTBhCQl0Jw0KCW4JCVUrMzEwYgkJbg0K
CWwJCVUrMzEwYwkJbA0KCWcJCVUrMzEwZAkJaw0KCWsJCVUrMzEwZQkJaycNCgloCQlVKzMxMGYJ
CXgNCglqCQlVKzMxMTAJCXQgVSswMjU1DQoJcQkJVSszMTExCQl0IFUrMDI1NSAnDQoJeAkJVSsz
MTEyCQlVKzAyNTUNCg0KCXpoCQlVKzMxMTMJCXQgVSswMjgyDQoJY2gJCVUrMzExNAkJdCBVKzAy
ODIgJw0KCXNoCQlVKzMxMTUJCVUrMDI4Mg0KCS1pCQkJCVUrMDI4NQ0KDQoJcgkJVSszMTE2CQlV
KzAyOTANCgl6CQlVKzMxMTcJCXRzDQoJYwkJVSszMTE4CQl0cycNCglzCQlVKzMxMTkJCXMNCgkt
aQkJCQlVKzAyN2YNCg0KCXkJCQkJag0KCXcJCQkJdw0KDQoJYQkJVSszMTFhCQlhDQoJbwkJVSsz
MTFiCQlvDQoJZQkJVSszMTFjCQlVKzAyNTkNCgllaAkJVSszMTFkCQlVKzAyNWINCglhaQkJVSsz
MTFlCQlhaQ0KCWVpCQlVKzMxMWYJCWVpDQoJYW8JCVUrMzEyMAkJYXUNCglvdQkJVSszMTIxCQlV
KzAyNTkgdQ0KCWFuCQlVKzMxMjIJCWFuDQoJZW4JCVUrMzEyMwkJVSswMjU5IG4NCglhbmcJCVUr
MzEyNAkJYSBVKzAxNGINCgllbmcJCVUrMzEyNQkJVSswMjU5IFUrMDE0Yg0KCW9uZwkJCQl1IFUr
MDE0Yg0KCWVyCQlVKzMxMjYJCVUrMDI1OSByDQoJaQkJVSszMTI3CQlpDQoJdQkJVSszMTI4CQl1
DQoJaXUJCVUrMzEyOQkJaSBVKzAyNTkgdQ0KCXYgLyB1IgkJVSszMTJhCQl5DQoJbmcJCVUrMzEy
YgkJVSswMTRiDQoJZ24JCVUrMzEyYwkJZ24NCg0KCWlhCQkJCWlhDQoJaWUJCQkJaSBVKzAyNWIN
CglpYW8JCQkJaWF1DQoJaWFuCQkJCWlhbg0KCWluCQkJCWluDQoJaWFuZwkJCQlpYSBVKzAxNGIN
CglpbmcJCQkJaSBVKzAxNGINCglpb25nCQkJCXkgVSswMTRiDQoJdWEJCQkJdWENCgl1bwkJCQl1
IFUrMDI1OQ0KCXVhaQkJCQl1YWkNCgl1aSAJCQkJdWVpDQoJdWVpCQkJCXVlaQ0KCXVhbgkJCQl1
YW4NCgl1bgkJCQl1IFUrMDI1OSBuDQoJdWVuCQkJCXUgVSswMjU5IG4NCgl1YW5nIAkJCQl1YSBV
KzAxNGINCgl2ZQkJCQl5cw0KCXZhbgkJCQl5YW4NCgl2bgkJCQl5bg0KCS0gLyAnIAkoY2hhcmFj
dGVyIHNwZWxsaW5nIHNlcGFyYXRvcikNCg0KDQpbQXBwZW5kaXggQi4xXSBFeGFtcGxlIG9uIERp
YWNyaXRpYyBtYXJrIG1hcHBpbmcNCg0KRnJlbmNoIGhhcyBsZXNzIHRoYW4gZWlnaHQgYnV0IG1v
cmUgdGhhbiBmb3VyIGRpYWNyaXRpYyBtYXJrcywgDQppdCBpcyBhbiBleGFtcGxlIG9mIHBob25l
dGljIG1hcHBpbmcgW1IxXS4NCg0KZnJlLQ0KMAlubyB0b25lDQoxCVNpbGVudCBvciBMaWFpc29u
ICcNCjIJcmlzZS9hY3V0ZSAoLykNCjMJKGRpcC9icmV2ZSBpcyBub3QgdXNlZCkNCjQJZHJvcC9n
cmF2ZSAoXCkNCjUJdGhyb3cvY2lyY3VtZmxleCAoXikNCjYJdGhyaWxsL3RpbGRlICh+KQ0KNwlk
aWVyZXNpcyAoIikNCjgJKG5vdCB1c2VkIGZvciBGcmVuY2gpDQo5CVN1cGVyY3JpcHQgb3IgbmFz
YWwgbg0KDQoNCltBcHBlbmRpeCBCLjJdIEV4YW1wbGUgb24gUGhvbmVtZSBNYXBwaW5nDQoNCklQ
QSBzeW1ib2wgbWFwcGluZywgW1IyXSB3aGVyZSBlYWNoIGRpZ2l0IHNwZWNpZnlzIGEgDQp2YXJp
YW50IG9mIGEgYmFzZSBwaG9uZW1lLCBhbmQgZm91ciB2YXJpYW50cyBhcmUgYXNzaWduZWQuIFRo
ZSANCnRhYmxlIGFsbG93cyBvdGhlciB2YXJpYW50cyB0byBiZSBmaWxsZWQgYXMgbmVlZGVkLiAN
ClRoZSBVbmljb2RlIGNvZGVwb2ludCBuZXh0IHRvIExhdGluIGFscGhhYmV0IGNvbHVtbiBpbmRp
Y2F0ZXMNCnRoZSByZXBsYWNlbWVudCBvZiB0aGUgY29ycmVzcG9uZGluZyBjb2RlcG9pbnQgb2Yg
TGF0aW4gbGV0dGVyLiAgDQoNCmlwYS0NCjAJMQkJMgkJMw0KDQphIAlVKzAyNTEgCQlhZSBVKzAw
ZTYJIFUrMDI5Mg0KYg0KYwljaCBVKzAyYTcNCmQJDQplCVUrMDI1YiAJCS5lIFUrMDI1OQkuZTog
VSswMjVjICAJCQ0KZg0KZw0KaA0KaQkJCQkNCmoJZDMgVSswMmE0DQprDQpsDQptDQpuCW5nIFUr
MDE0Yg0KbwlVKzAyNTIJbzogVSswMjU0ICAJCQ0KcA0KcQ0Kcg0KcwlzaCBVKzAyODMNCnQJdGgg
VSswM2I4CVUrMDBmMA0KdSAJVSswMjhjICAgCVUrMDI4YSAgCVUrMDA3NSAgDQp2DQp3DQp4DQp5
DQp6CXpoIFUrMDI5Mg0KDQo0CXVuc2lnbmVkDQo1CXVuc2lnbmVkDQoNCjYJdW5zaWduZWQNCjcJ
dW5zaWduZWQNCjgJdW5zaWduZWQNCjkJdW5zaWduZWQNCg0KW0FwcGVuZGl4IEIuM10gRXhhbXBs
ZSBvbiBPdmVyZmxvdyBDb25zZWN1dGl2ZSBzbG90IE1hcHBpbmcNCg0KQ2hpbmVzZSBzY3JpcHQg
dXNpbmcgT3ZlcmZsb3cgYW5kIFRvbmUgTWFyayBtYXBwaW5nIA0KYXJjaGl0ZWN0dXJlLCBbUjEt
UjNdLCBXaGVyZSB0aGUgdGFibGUgaXMgcGFydGl0aW9uZWQgdG8gDQpzZWxlY3QgdHdvIGRpZmZl
cmVudCBnbHlwaCBzZXRzIG9mIHRoZSBzY3JpcHQ6DQoNCnpoby0NCgkwCW5vIHRvbmUNCgkxCWZs
YXQvbWFjcm9uICgtKQ0KCTIJcmlzZS9hY3V0ZSAoLykNCgkzCWRpcC9icmV2ZSAodikNCgk0CWRy
b3AvZ3JhdmUgKFwpDQoNCgk1CWNsYXNzaWMgY2hhcmFjdGVyIGRyb3AvZ3JhdmUgKFwpDQoJNglj
bGFzc2ljIGNoYXJhY3RlciBkaXAvYnJldmUgKHYpCQ0KCTcJY2xhc3NpYyBjaGFyYWN0ZXIgcmlz
ZS9hY3V0ZSAoLykNCgk4CWNsYXNzaWMgY2hhcmFjdGVyIGZsYXQvbWFjcm9uICgtKQkNCgk5CWNs
YXNzaWMgY2hhcmFjdGVyIG5vIHRvbmUNCg0KW0FwcGVuZGl4IEIuNF0gUHJpb3JpdHkgZWxlbWVu
dHMgbWFwcGluZyBmb3IgRW5nbGlzaC4gDQpETlMgbmFtZSByZXNvbHZlciB0cmVhdHMgdXBwZXJj
YXNlIHNhbWUgYXMgbG93ZXIgY2FzZSwNCkl0IHByb3ZpZGVzIG5vIGFkZGl0aW9uYWwgdmFsdWUg
Zm9yIHVzZXJzIHRvIGFzc2lnbiANCmFueSBzcGVjaWZpYyB2YWx1ZSB0byB1cHBlciBjYXNlIGxl
dHRlcnMgYmVzaWRlcyBhcyBvbmUNCm9mIG1hbnkgZm9udHMuIFRoZSBFbmdsaXNoIG1hcHBpbmcg
YXNzaWdubWVudCB0YWtlcw0KW1IxLVIyLVI0XSwgd2hlcmUgZGlnaXQgOCBpcyBkZXNpZ25hdGVk
IGZvciBsZXR0ZXINCnJlbGF0ZWQgZGluZ2JhdHMuDQoNCmVuZy0NCjAJYS16QS1aDQoxCWZsYXQv
bWFjcm9uICgtKQ0KMglyaXNlL2FjdXRlICgvKQ0KMwlkaXAvYnJldmUgKHYpDQo0CWRyb3AvZ3Jh
dmUgKFwpDQo1CXRocm93L2NpcmN1bWZsZXggKF4pDQo2CXRocmlsbC90aWxkZSAofikNCjcJZGll
cmVzaXMgKCIpDQo4CURpbmdiYXRzIA0KOQlHcmVlayBhLXpBLVoNCg0KCTAJOAkJDQoJYSAJVSsy
NjA0CS8qYXJlbyBvciBjb21ldCovDQoJYgkNCgljCVUrMjRiOAkvKmNvcHlyaWdodCovDQoJZAlV
KzI1Y2EJLypkaWFtb25kKi8NCgllCVUrMjRkNCAJLyplbGV0cm9uKi8gIAkJDQoJZglVKzI3MDkJ
LypmbHkqLw0KCWcJDQoJaAlVKzI2MjQJLypoZWFsdGggb3IgQ2FkdWNldXMqLw0KCWkJVSsyNjFl
ICAvKmluZGV4IG9yIHdoaXRlIHJpZ2h0IHBvaW50aW5nIGluZGV4Ki8JCQkNCglqCQ0KCWsJVSsy
NjU0CS8qa2luZyovDQoJbAlVKzI2NjEJLypsb3ZlIG9yIHdoaXRlIGhlYXJ0IHN1aXQqLw0KCW0J
VSsyNzA5CS8qbWFpbCBvciBlbnZlbG9wZSovDQoJbglVKzI2NmIJLypub3RlIG9yIEJhcnJlZCBl
aWdodGggbm90ZSovDQoJbyAgCQ0KCXAJVSsyNjJlCS8qcGVhY2Ugc3ltYm9sKi8NCglxCVUrMjY1
NQkvKnF1ZWVuKi8NCglyCVUrMjYwMgkvKnJhaW4gb3IgdW1icmVsbGEgKi8NCglzCVUrMjYzYQkv
KnNtaWxlKi8NCgl0CVUrMjMxYQkvKnRpbWUgb3Igd2F0Y2gqLw0KCXUgCVUrMjMyOCAJLyp1dGls
aXR5IG9yIGtleWJvYXJkKi8gIA0KCXYJVSsyNjBlCS8qdm9pY2Ugb3IgcGhvbmUqLw0KCXcJVSsy
NzBkCS8qd3JpdGluZyovDQoJeAkNCgl5CVUrMjYyZgkvKiB5aW55YW5nICovDQoJegkNCg0KW0Fw
cGVuZGl4IENdIFRoZSBnbHlwaCBsYXlvdXQgZGlnaXRzOg0KDQoJMCAtIGVuZCBvZiBhIGNoYXJh
Y3RlciBvciBhIFBpYW5wYW5nDQoJMSAtIHRvIGl0cyByaWdodA0KCTIgLSB0byBpdHMgdW5kZXIN
CgkzIC0gdG8gY29udGFpbiB0aGUgZm9sbG93aW5nDQoJNCAtIHRvIGRpdmlkZSB0aGUgZm9sbG93
aW5nDQoJNSAtIHRvIGl0cyBsZWZ0DQoJNiAtIHRvIGl0cyB0b3ANCg0KCVRoZSBmb2xsb3dpbmcg
c2VsbGVjdGFibGUgZGlnaXRzIGZvciBzcGVjaWZ5IGFkZGl0aW9uYWwgDQoJZ2x5cGggb2YgdGhl
IHNjcmlwdCBhbmQgZGlyZWN0aW9uIG9mIGxheW91dC4NCg0KCTcgLSB0byBvdmVybGF5IGl0c2Vs
ZiB3aXRoIFggdGhlbiB0byBpdHMgcmlnaHQNCgk4IC0gdG8gb3ZlcmxheSBpdHNlbGYgd2l0aCBY
IHRoZW4gdG8gaXRzIGxlZnQNCgk5IC0gdG8gb3ZlcmxheSBpdHNlbGYgd2l0aCBYIHRoZW4gdG8g
aXRzIHVuZGVyDQoNCltBcHBlbmRpeCBELjFdIFN0ZXBDb2RlIGtleWJvYXJkIGlucHV0IHByb2Nl
c3MNCg0KLyogYnVmZi5jICBTdGVwQ29kZSBwcm9jZXNzb3IgaW50ZXJmYWNlICAgQ29weXJpZ2h0
IFkmRCBJU0csIEluYy4gMTk5NA0KICotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSoNCiAqICBmaW5kX2dseSAgZmlu
ZCBhIGdseXBoIG9ubGluZS4NCiAqICBmaW5kX3dkICAgZmluZCBhIHdvcmQgb25saW5lLg0KICov
DQoNCiNpbmNsdWRlIDxzdGRpby5oPg0KI2luY2x1ZGUgPGN0eXBlLmg+DQojaW5jbHVkZSAic3Rl
cGxpYi5oIg0KDQppbnQgYXV0b19sZWFybj0gVFJVRTsNCmludCB1ZGljX2xhcmdlPSBGQUxTRTsN
CmludCB1ZGljX2RhdGFiYXNlPSBGQUxTRTsNCmludCBvZGljX2V4cGFuZCA9IEZBTFNFOw0KaW50
IGRpY19zYXZlZCA9IEZBTFNFOw0KaW50IGtleWJvYXJkX2luID0gVFJVRTsNCmludCBhbHRfbWVt
YiA9IDI7CS8qIGV4dHJhIG1lbWJlcnMgb2YgYSBwb2x5LWNvZGUgdG8gYmUgcmVjb3JkZWQgKi8N
Cg0KLyogDQogKiBmaW5kX2dseSAgdXNpbmcgYSBTdGVwQ29kZSB0byBmaW5kIHRoZSBHQiBjb2Rl
IGZvciBkaXNwbGF5IGEgZ2x5cGguDQogKi8NCmludCBmaW5kX2dseShzdGVwLCBzdGVwY2QsIGlu
Zm9yLCBnYiwga2V5KQ0KCWNoYXIgKnN0ZXAsICpzdGVwY2QsICppbmZvciwgKmdiOw0KCWludCAq
a2V5Ow0Kew0KCUZJTEUgKmJ1ZnA7DQoJaW50IGxpbmVjbnQsIGJ5dGVzOw0KCWNoYXIgbGluZVtN
QVhkYXRhbGVuXSwgKnA7DQoJY2hhciBidWZuYW1lW0ZJTEVOQU1TSVpdOw0KCQ0KCXN0cm5jcHko
c3RlcGNkLCBzdGVwLCBzdHJsZW4oc3RlcCkrMSk7DQoJaWYgKGhpdF9nbHkoc3RlcGNkLCBnYikp
IA0KCQl7ICprZXk9R0I7IHJldHVybihBX3RvX0IpO30NCg0KCXN0cm5jcHkoYnVmbmFtZSwgQlVG
RklMRSwgRklMRU5BTVNJWik7DQoJYnVmcCA9IChGSUxFICopZm9wZW4oYnVmbmFtZSwgIncrYiIp
Ow0KCWlmKCBidWZwID09IE5VTEwgKSANCgl7DQoJCXN0cmNweSggbWVzc2FnZSwgIkJ1ZmZlciBm
aWxlIHVuYXZhaWxhYmxlLiIpOw0KCQl0eXBvKG1lc3NhZ2UsIHdvcmQpOyANCgkJcmV0dXJuKEVS
Uk9SKTsNCiAgCX0NCglzZWFyY2hfZGljKFNURVAsIDEsIHN0ZXBjZCwgYnVmbmFtZSwgJmJ1ZnAs
ICZsaW5lY250KTsJDQoJaWYgKGxpbmVjbnQ8PTApDQoJew0KCQlpZih2ZXJib3NlKQ0KCQl0eXBv
KCJObyBlbnRyeSBmb3VuZCBpbiBHQiB0YWJsZS4gWW91IG1heSBjcmVhdGUgb25lLiIsIHN0ZXAp
Ow0KCQkNCgkJZmNsb3NlKGJ1ZnApOw0KCQlyZXR1cm4oQV90b19aSUwpOw0KCX0NCglmc2Vlaygg
YnVmcCwgMEwsIDAgKTsJCS8qIHRvIGJlZ2lubmluZyBzYWtlIHJlYWQgKi8NCglpZihmZ2V0cyhs
aW5lLCBNQVhkYXRhbGVuLCAgYnVmcCk9PSBOVUxMKQ0KCXsJaWYodmVyYm9zZSkNCgkJZnByaW50
ZihzdGRlcnIsICJFUlJPUi0gYnVmZmVyIGZpbGUgcmVhZCBlcnJvci5cbiIpOw0KCQlmY2xvc2Uo
YnVmcCk7DQoJCXJldHVybihFUlJPUik7DQoJfQ0KCXNzY2FuZihsaW5lLCAiJXMlZCVzJXNcbiIs
IHN0ZXBjZCwga2V5LCBnYiwgaW5mb3IpOw0KCWhhc2hfZ2x5KHN0ZXBjZCwgZ2IpOw0KCWZjbG9z
ZShidWZwKTsNCglpZiAobGluZWNudD4xKQ0KCXsNCgkJcmV0dXJuKCBBX3RvX04pOw0KCX1lbHNl
IHsgIA0KCQlyZXR1cm4oIEFfdG9fQik7DQoJfQ0KfQ0KDQppbnQgZmluZF93ZChzdGVwLCBzdGVw
Y2QsIGluZm9yLCBnYiwgY250LCBrZXkpDQoJY2hhciAqc3RlcCwgKnN0ZXBjZCwgKmluZm9yLCAq
Z2I7DQoJaW50IGNudCwgKmtleTsNCnsNCglGSUxFICpidWZwOw0KCWludCBsaW5lY250Ow0KCWNo
YXIgbGluZVtNQVhkYXRhbGVuXSwgKnA7DQoJY2hhciBidWZuYW1lW0ZJTEVOQU1TSVpdOw0KCQ0K
CXN0cm5jcHkoc3RlcGNkLCBzdGVwLCBzdHJsZW4oc3RlcCkrMSk7DQoJaWYgKCBoaXRfd2Qoc3Rl
cGNkLCBnYikpDQoJCXsgKmtleSA9IEdCOyByZXR1cm4oQV90b19CKTt9DQoNCglzdHJuY3B5KGJ1
Zm5hbWUsIEJVRkZJTEUsIEZJTEVOQU1TSVopOw0KCWJ1ZnAgPSAoRklMRSAqKWZvcGVuKGJ1Zm5h
bWUsICJ3K2IiKTsNCglpZiggYnVmcCA9PSBOVUxMICkgDQoJew0KCQlmcHJpbnRmKCBzdGRlcnIs
ICJCdWZmZXIgZmlsZSB1bmF2YWlsYWJsZS4iKTsNCgkJcmV0dXJuKEVSUk9SKTsNCiAgCX0NCglz
ZWFyY2hfZGljKFNURVAsIGNudCwgc3RlcGNkLCBidWZuYW1lLCAmYnVmcCwgJmxpbmVjbnQpOw0K
CWlmIChsaW5lY250PD0wKQ0KCXsJaWYgKCFhdXRvX2xlYXJuKQ0KCQl7ICANCgkJICAgaWYodmVy
Ym9zZSkNCgkJCXR5cG8oIk5vdCBmb3VuZC4gIFlvdSBtYXkgY3JlYXRlIHRoZSB3b3JkLiIsIHN0
ZXApOw0KCQkgICBmY2xvc2UoYnVmcCk7DQoJCSAgIHJldHVybihBX3RvX1pJTCk7DQoJCX1lbHNl
DQoJCXsNCgkJCW5ld3cgPSBsZWFybndvcmQoY250LCBzdGVwY2QsIGdiKTsNCgkJCS8qIERvIHdo
YXRldmVyIHdpdGggbmV3dyBoZXJlICovDQoJCQlpZihkaWNfc2F2ZWQpIA0KCQkJCXsJDQoJCQkJ
CWhhc2hfd2Qoc3RlcGNkLCBnYik7DQoJCQkJCWRpY19zYXZlZCA9IEZBTFNFOw0KCQkJCX0NCgkJ
CWVsc2UgDQoJCQl7DQoJCQkgICB0eXBvKCJUaGUgbmV3IHdvcmQgaGFzIG5vdCBzYXZlZC4iLCBz
dGVwY2QpOw0KCQkJfSAgIA0KCQkJZmNsb3NlKGJ1ZnApOw0KCQkJbmV3dyA9IHJlc2V0X3dvcmQo
bmV3dyk7DQoJCQlyZXR1cm4oWklMX3RvX0EpOw0KCQl9DQoJfQ0KCWZzZWVrKCBidWZwLCAwTCwg
MCApOwkJLyogdG8gYmVnaW5uaW5nIHNha2UgcmVhZCAqLw0KCWZnZXRzKGxpbmUsIE1BWGRhdGFs
ZW4sICBidWZwKTsNCglpZihsaW5lID09IE5VTEwpDQoJewkNCgkJaWYgKGZlcnJvcihidWZwKSE9
MCAmJiB2ZXJib3NlKSANCgkJCWZwcmludGYoc3RkZXJyLCAiRXJyb3IgZHVyaW5nIGJ1ZmZlciBy
ZWFkLlxuIik7DQoJCWlmIChmZW9mKGJ1ZnApICE9MCAmJiB2ZXJib3NlKSANCgkJCWZwcmludGYo
c3RkZXJyLCAiQnVmZmVyIGZpbGUgZW5kZWQuXG4iKTsNCgkJY2xlYXJlcnIoYnVmcCk7DQoJCWZj
bG9zZShidWZwKTsNCgkJcmV0dXJuKEFfdG9fWklMKTsNCgl9DQoJc3NjYW5mKGxpbmUsICIlcyVk
JXMlc1xuIiwgc3RlcGNkLCBrZXksIGdiLCBpbmZvcik7DQoJaGFzaF93ZChzdGVwY2QsIGdiKTsN
CglmY2xvc2UoYnVmcCk7DQoJaWYgKGxpbmVjbnQ+MSkNCgl7DQoJCXJldHVybiggQV90b19OKTsN
Cgl9ZWxzZSB7ICANCgkJcmV0dXJuIChBX3RvX0IpOw0KCX0NCn0NCg0KDQoNCi8qIC0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tDQogKiBGaWd1cmUgb3V0IHRoZSBudW1iZXIgb2YgZ2x5cGhzIGluIGEgd29yZC4gVGhlIG5l
eHQgdHdvIHJvdXRpbmVzIGFyZSANCiAqIGJhc2VkIG9uIFBJTllJTiBzeXN0ZW0uDQogKi8NCmlu
dCBvbmVfbGV0dGVyX3NvdW5kKHdvcmQpDQoJY2hhciAqd29yZDsNCnsNCglpbnQgY250PTA7DQoJ
Y2hhciAqdywgKnY7DQoJDQoJdz13b3JkOw0KCXdoaWxlICgqdz09J20nfHwqdz09J00nfHwqdz09
J24nfHwqdz09J04nKQ0KCQkJeyArK2NudDsgKyt3O30NCglpZiAoY250PjApDQoJew0KCQl2ID0g
dzsgLS12Ow0KCQlpZigoKnc9PSdnJ3x8Knc9PSdHJykmJiAoKnY9PSduJ3x8KnY9PSdOJykpDQoJ
CQkrK3c7CS8qZXg6IG1uZyBubm5nKi8NCgl9DQoJaWYoY250PT0wKSB3aGlsZSAoKnc9PSdhJ3x8
Knc9PSdBJyl7ICsrY250OyArK3c7fQ0KCWlmKGNudD09MCkgd2hpbGUgKCp3PT0nbyd8fCp3PT0n
TycpeyArK2NudDsgKyt3O30NCglpZihjbnQ9PTApIHdoaWxlICgqdz09J2UnfHwqdz09J0UnKXsg
KytjbnQ7ICsrdzt9DQoJaWYgKCFpc2FscGhhKCp3KSkgDQoJCXJldHVybihjbnQpOyAvKmV4OmEg
YWEgb29vIGVlZS0gbW1tIG5tbiovDQoJZWxzZSBjbnQ9MDsJCS8qZXg6IGFuIGhoaCBvb25nICov
DQoJcmV0dXJuKGNudCk7DQp9DQoNCmludCB0ZWxsX3dvcmQod29yZCkNCgljaGFyICp3b3JkOw0K
ew0KCWNoYXIgKncsICp2Ow0KCWludCAgY250Ow0KCWNudD0wOw0KCQ0KCWlmKCFpc2FscGhhKCp3
b3JkKSkgcmV0dXJuIChOVUxMKTsNCgkNCglmb3IgKHc9d29yZDtpc2FscGhhKCp3KTsrK3cpOyAv
KnNraXAgUGlueWluICovDQoJd2hpbGUgKGlzZGlnaXQoKncpKSB7Y250Kys7ICsrdzt9IC8qY291
bnQgdGhlIG51bWJlciBvZiB0b25lIG1hcmtzKi8NCg0KCWlmIChjbnQ8MSkJCS8qc3BlY2lhbCBz
aWdsZSBsZXR0ZXIgZ2x5cGggY2FzZXMqLw0KCXsNCgkJY250ID0gb25lX2xldHRlcl9zb3VuZCh3
b3JkKTsNCgkJaWYgKGNudD49MSkgcmV0dXJuKGNudCk7IC8qIGVsc2UgZG8gc3lsbGFibGUgYW5h
bHlzaXMgKi8NCgl9DQoJZWxzZSByZXR1cm4oY250KTsNCg0KCS8qDQoJICogZmluZCB0aGUgbnVt
YmVyIG9mIHN5bGxhYmxlcyBieSB2b3dlbCBydWxlcyANCgkgKiBUaGlzIGltcGxlbWVudGF0aW9u
IGlzIGFjY3VhdGUgZXZlbiB3aXRob3V0IHVzaW5nIGFwb3N0cm9waGUNCgkgKi8NCgl3PXdvcmQ7
CQkNCgl3aGlsZSAoaXNhbHBoYSgqdykpIC8qY2hlY2sgdGhlIFBpbnlpbiBvbmx5Ki8NCgl7DQoJ
CXN3aXRjaCAoKncpDQoJCXsNCgkJY2FzZSAnYSc6DQoJCWNhc2UgJ2knOg0KCQljYXNlICdlJzoN
CgkJY2FzZSAnbyc6DQoJCWNhc2UgJ3UnOiB2PXc7ICsrdzsgY250Kys7IC8qb25lIHZvd2VsIGNh
c2UqLw0KCQkJc3dpdGNoICgqdykNCgkJCXsNCgkJCWNhc2UgJ2knOg0KCQkJY2FzZSAnZSc6DQoJ
CQljYXNlICdvJzoNCgkJCWNhc2UgJ3UnOiArK3c7YnJlYWs7IC8qdHdvIHZvd2VscyBzb3VuZCov
DQoJCQljYXNlICdhJzogKyt3Ow0KCQkJCWlmICgqdj09J3UnICYmICp3PT0naScpIGJyZWFrOy8q
dWFpKi8NCgkJCQlpZiAoKnY9PSdpJyAmJiAqdz09J28nKSBicmVhazsvKmlhbyovCQkJCQkJCQ0K
CQkJCWVsc2Ugew0KCQkJCQktLXc7ICAgICAvKnN0aWxsIHR3byB2b3dlbHMqLw0KCQkJCQlicmVh
azsNCgkJCQl9DQoJCQlkZWZhdWx0OiBicmVhazsNCgkJCX0NCgkJZGVmYXVsdDoNCgkJCS8qYWxy
ZWFkeSBnZXQgb3V0IG9mZiB0aGUgY29tcG91bmQgdm93ZWwqLw0KCQlicmVhazsNCgkgICAgICAg
IH0JCSAgDQoJCSsrdzsgICANCgl9LypjaGVjayBzeWxsYWJsZXMqLw0KCXJldHVybihjbnQpOw0K
fQ0KDQovKiANCiAqIC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQogKiBJbnRlcmFjdGl2ZSBpbnB1dCBwcm9jZXNzIHBy
b2NlZHVyZQ0KICogLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCiAqLw0KaW5wdXRwKGNoYXIgKndvcmQsIGNoYXIgKmdi
KSANCnsNCglpbnQgIGksICBnbHlwaGNudDsNCgljaGFyIGMsICp3Ow0KCWludCBjbnQsIGtleSwg
c3RhdDsNCgljaGFyIGR1bXBbTUFYZGF0YWxlbl07DQoJDQoJZm9yICg7OykNCgl7DQoJCSp3b3Jk
PSdcMCc7DQoJCWZnZXRzKHdvcmQsIE1BWGxpbmVsZW4sIHN0ZGluKTsNCgkJaWYgKGlzc3BhY2Uo
KndvcmQpKQ0KCQkJYnJlYWs7IA0KDQoJCS8qIENoZWNrIGlmIHRoZSBlbnRyeSBpcyBhIGdseXBo
IHN0cmluZyBieSAqLw0KCQlnbHlwaGNudCA9IHRlbGxfd29yZCh3b3JkKTsNCgkJaWYgKGdseXBo
Y250ID09IE5VTEwpIA0KCQl7DQoJCQlwcmludGYoIiVzIiwgKndvcmQpOw0KCQkJZmZsdXNoKHN0
ZGluKTsgDQoJCQljb250aW51ZTsNCgkJfQ0KCQkNCgkJdz13b3JkOw0KCQl3aGlsZSAoaXNhbG51
bSgqdykpICsrdzsNCgkJKncgPSAnXDAnOw0KCQlpZih2ZXJib3NlKQ0KCQkJcHJpbnRmKCJ0ZWxs
X3dvcmQgZmlndXJlOiAgJWQgZ2x5cGhzXG4iLCBnbHlwaGNudCk7DQoNCgkJLyogRGV0ZXJtaW4g
dGhlIGVudHJ5IGlzIGtub3duIHRocm91Z2ggZGljdGlvbmFyeQ0KCQkgKiBhbmQgY2FjaGUgbG9v
a3VwLg0KCQkgKi8NCgkJaWYoZ2x5cGhjbnQgPj0yKSANCgkJCXN0YXQgPSBmaW5kX3dkKHdvcmQs
IHN0ZXBjZCwgZHVtcCxnYixnbHlwaGNudCwgJmtleSk7DQoJCWVsc2Ugc3RhdCA9IGZpbmRfZ2x5
KHdvcmQsIHN0ZXBjZCwgZHVtcCxnYiwgJmtleSk7DQoNCgkJLyogUHJpbnQgb3V0IHdpdGggR0Ig
Y29kZSAqLw0KCQlpZiAoIXN0YXQ9PUVSUk9SKSBmb250X2NvZGUoc3RlcGNkLCBnYiwgJmtleSwg
c3RkZXJyKTsNCgkJaWYodmVyYm9zZSkgcHJpbnRmKCIlc1xuIiwgc3RlcGNkKTsNCgkJZmZsdXNo
KHN0ZGluKTsNCgkJZmZsdXNoKHN0ZGVycik7DQoJfQ0KCXJldHVybigwKTsNCn0NCg0KDQpbQXBw
ZW5kaXggRC4yXQ0KDQovKiBEaXNhc3NlbWJsZSBhIENoaW5lc2Ugc3RlcHdvcmQgaW50byBzdGVw
Z2x5cGhlcy4NCiAqLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLSoNCiAqLw0KaW50IGRpc2Fzc2VtYihjbnQsIHdvcmQsIHN0cywg
cGhvbnN5cykNCglpbnQgY250Ow0KCWNoYXIgKndvcmQ7DQoJY2hhciAqc3RzW107DQoJaW50IHBo
b25zeXM7DQp7DQoJY2hhciAqdywgKmhkLCAqbnQsICp2aDsgIC8qU3RhbmQgZm9yIGhlYWQsIG5l
eHQsIHZvd2VsX2hlYWQqLw0KCWludCAgaSwgaiwgbmMsIGFsX2ZsYWc7DQoJY2hhciAqczsNCg0K
LyogaW5pdGlhbGl6ZSovDQoJZm9yIChpPTA7aTwoY250KzMpOysraSkNCgkgICBmb3IgKGo9MCwg
cz1zdHNbaV07ajw9U1RFUFNJWkU7KytqLCArK3MpDQoJCSpzPU5VTEw7DQoJaGQ9dz13b3JkOw0K
CWk9aj1uYz0wOw0KDQoJc3dpdGNoIChwaG9uc3lzKQ0KCXsNCgljYXNlIFBJTllJTjogYnJlYWs7
DQoJY2FzZSBaSFVZSU46IC8qIGJyYW5jaCB0byBkaXNhc3NlbWJfemh1eWluKCk7IHJldHVybjsq
Lw0KCWNhc2UgS0FOVE9OOiAvKiBicmFuY2ggdG8gZGlzYXNzZW1iX2thbnRvbigpOyByZXR1cm47
Ki8NCglkZWZhdWx0Og0KCQlicmVhazsNCgl9DQoJIA0KLyogbm9uLWNvbnNvbmVudCBvciBub24t
dm93ZWwgc2luZ2xlIGxldHRlciBnbHlwaHMgKi8NCgluYz1vbmVfbGV0dGVyX3NvdW5kKHdvcmQp
Ow0KCWlmKG5jPjApDQoJew0KCQlmb3IoaT0wO2k8bmM7aSsrLCB3KyspIHN0c1tpXVswXT0qdzsN
CgkJKyt3Ow0KCQlpZiAoKnc9PSdnJ3x8Knc9PSdHJykgLypjYXNlIG9mIG5nKi8NCgkJewlzdHNb
aV1bMV09Knc7CXJldHVybihuYyk7IH0NCg0KCQlmb3IgKGk9MDtpPG5jO2krKykJLyogYWRkIHRo
ZSB0b25lcyAqLw0KCQl7DQoJCSAgIGlmIChzdHNbaV1bMF09PSdhJ3x8c3RzW2ldWzBdPT0nQScp
IHN0c1tpXVsxXT0nMSc7DQoJCSAgIGlmIChzdHNbaV1bMF09PSdtJ3x8c3RzW2ldWzBdPT0nbScp
IHN0c1tpXVsxXT0nMic7DQoJCX0NCgkJLyogQ2FzZXMgb2YgTyBhbmQgRSBhcmUgdmVyeSBsaW1p
dGVkICovDQoJCXJldHVybihuYyk7DQoJfQ0KDQovKiBkZWxldGUgdGhlIGVuZGluZyAtciAqLw0K
CXMgPSB3b3JkOw0KCXdoaWxlIChpc2FscGhhKCpzKSkgcysrOw0KCS0tczsNCglpZiAoKnM9PSdy
JyAmJiAqKHMtMSkhPSAnZScpDQoJewkNCgkJZXJfZmxhZz0gVFJVRTsNCgkJd2hpbGUgKGlzYWxu
dW0oKnMpKSAqcz0qKCsrcyk7DQoJfQ0KDQovKiBFbmRpbmcgLXogYW5kIC1sIGFyZSBhY2NvbW1v
ZGF0ZWQgaGVyZSAqLw0KDQoNCiAgLyogQnkgUGlueWluIHJ1bGVzOg0KICAgKiBJdCBvbmx5IHRy
eXMgdG8gcmVjb2duaXplIGEgcG9zc2libGUgc3lsbGFibGUsIGFuZCBwYXlzIGxpdHRsZQ0KICAg
KiBhdHRlbnRpb24gb2YgY29ycmVjdCBzcGVsbGluZy4gQSB3b3JkIGxpa2UgJ3Blbycgd2lsbCBw
YXNzLA0KICAgKiBidXQgJ2xlZWsnIHdpbGwgbm90LiBUaGlzIHNjaGVtZSBpcyBub3QgYSBzcGVs
bGVyIGNoZWNrZXIsIGFuZA0KICAgKiB0b2xlcmF0ZXMgZm9yZWlnbiB2b2NhYnVsYXJ5Lg0KICAg
Ki8NCgloZD13PXdvcmQ7DQoJaT1qPW5jPWFsX2ZsYWc9MDsNCgl3aGlsZSAoaXNhbHBoYSgqdykp
CQkvKmNoZWNrIHRoZSBQaW55aW4gb25seSovDQoJewl3aGlsZSAoaXNhbHBoYSgqdykmJiFpc3Zv
d2VsKCp3KSkgKyt3Ow0KCQl2aD13OyArK3c7IG50PXc7IG5jKys7CSAvKm9uZSB2b3dlbCBjYXNl
Ki8NCgkJDQoJCQlzd2l0Y2ggKCp3KQ0KCQkJew0KCQkJY2FzZSAnaSc6DQoJCQljYXNlICdlJzoN
CgkJCWNhc2UgJ3UnOiArK3c7bnQ9dzsNCgkJCQlicmVhazsJCS8qdHdvIHZvd2VscyBjYXNlKi8N
Cg0KCQkJY2FzZSAnbyc6ICsrdztudD13O250Kys7DQoJCQkJaWYgKCp2aD09J2knJiYgKnc9PSdu
JyYmICpudD09J2cnKQ0KCQkJCSAgeyBudCsrOyB3PW50O30gLyogaW9uZyBjYXNlIG9ubHkgKi8N
CgkJCQllbHNlIG50PXc7DQoJCQkJYnJlYWs7DQoJCQkNCgkJCWNhc2UgJ2EnOiArK3c7bnQ9dzsJ
ICAgICAgLyogLWE/ICovDQoJCQkJaWYgKCFpc2FscGhhKCp3KSB8fA0KCQkJCSAgICAoaXNhbHBo
YSgqdykgJiYNCgkJCQkgICAgICgqdyE9J28nKSYmKCp3IT0naScpJiYoKnchPSduJykpKQ0KCQkJ
CQlicmVhazsNCgkJCQkrK250OwkJICAgIC8qIHNwZWNpYWwgY2FzZXMgKi8NCgkJCQlpZigoKnZo
PT0ndScgJiYgKnc9PSdpJykgfHwgICAgICAvKnVhaSovDQoJCQkJICAgKCp2aD09J2knICYmICp3
PT0nbycpKSAgICAgICAgLyppYW8qLw0KCQkJCXsgaWYoKG5jPGNudCkmJighaXNhbHBoYSgqbnQp
KSkNCgkJCQkJewkJICAvKnR3byBnbHlwaHMqLw0KCQkJCQkgICBzdHJuY3B5KHN0c1tpXSxoZCwo
Kyt2aCktaGQpOw0KCQkJCQkgICArK2k7bmMrKzsgaGQ9dmg7dz1udDsNCgkJCQkJICAgYnJlYWs7
DQoJCQkJCX0NCgkJCQkgIGVsc2UgeyB3PW50OyBicmVhazt9CSAvKiBvbmUgZ2x5cGgqLw0KCQkJ
CX0NCgkJCQlpZigqbnQ9PSdnJyludCsrOyAgICAgLyotYW4rIG9yIC1hbmcrKi8NCgkJCQlpZiAo
aXNhbHBoYSgqbnQpJiYoIWlzdm93ZWwoKm50KSkpDQoJCQkJCXt3PW50OwlicmVhazsJfQ0KCQkJ
CWlmKGlzdm93ZWxuYSgqbnQpKXstLW50OyB3PW50O2JyZWFrO30NCgkJCQlpZigobmM8Y250KSYm
KCFpc2FscGhhKCpudCkpKQ0KCQkJCXsJICAgLyp1YW4gb3IgaWFuZzp0d28gZ2x5cGhzKi8NCgkJ
CQkJc3RybmNweShzdHNbaV0saGQsKCsrdmgpLWhkKTsNCgkJCQkJKytpO25jKys7IGhkPXZoO3c9
bnQ7DQoJCQkJCWJyZWFrOw0KCQkJCX0NCgkJCQlpZiAoIWlzYWxwaGEoKm50KSkgYnJlYWs7IC8q
IGVuZCBvZiBQaW55aW4qLw0KCQkJCQktLW50OwkgICAgICAgLyotYW5hIG9yIGFuZ2EqLw0KCQkJ
CQkrK2FsX2ZsYWc7DQoJCQkJYnJlYWs7DQoJCQljYXNlICduJzogbnQ9dzsrK250Ow0KCQkJCWlm
KCpudD09J2cnKW50Kys7DQoJCQkJaWYgKCFpc2FscGhhKCpudCl8fCANCgkJCQkgICAgKGlzYWxw
aGEoKm50KSYmKCFpc3Zvd2VsKCpudCkpKSkNCgkJCQkgICAgICAgICAgIHsgdz1udDsgYnJlYWs7
fQ0KCQkJCWlmIChpc3Zvd2VsbmEoKm50KSl7LS1udDsgdz1udDticmVhazt9DQoJCQkJaWYoKm50
PT0nYScpDQoJCQkJeyArK3c7IGlmKCp2aD09J28nJiYqdz09J2EnKSAtLW50OyAvKi1vIG5hICov
DQoJCQkJICAgICAgIGlmKCp2aD09J28nJiYqdz09J2cnKSB7fTsgICAvKi1vbmcgYSovDQoJCQkJ
ICAgICAgIGlmKCp2aD09J3UnJiYqdz09J2cnKSAtLW50OyAvKi11biBnYSovDQoJCQkJIGVsc2UN
CgkJCQkgeyAvKiBUaGVyZSBhcmUgdHdvIHBvc3NpYmxlIHdheXMgDQoJCQkJICAgIHN0cm5jcHko
c3RzW2ldLGhkLCgtLW50KS1oZCk7DQoJCQkJICAgICsraTtuYysrOyBoZD1udDt3PW50KzE7DQoJ
CQkJICAgICAgICAgICAgICAgLypuYSBnYSBoYXZlIGhpZ2hlciBjaGFuY2UqLw0KCQkJCSAgICAr
K2FsX2ZsYWc7LS1udDsNCgkJCQkgICAgDQoJCQkJIH19DQoJCQkJYnJlYWs7DQoJCQljYXNlICdy
JzogbnQ9dzsgKytudDsNCgkJCQlpZiAoaXN2b3dlbCgqbnQpKXstLW50OyBicmVhazt9DQoJCQkJ
aWYgKGlzYWxwaGEoKm50KXx8KnZoPT0nZScpIHc9bnQ7DQoJCQkJYnJlYWs7DQoJCQlkZWZhdWx0
Om50PXc7IC8qY29uc29uZW50cyAqLw0KCQkJYnJlYWs7DQoJCQl9LyogZW5kIG9mIHN3aXRjaCov
CQkNCg0KCQlzdHJuY3B5KHN0c1tpXSxoZCxudC1oZCk7ICANCgkJKytpO2hkPW50OyB3PW50Ow0K
CX0vKiB3aGlsZSBjaGVjayBzeWxsYWJsZXMqLw0KDQoJYXBwZW5kX3N1ZmZpeChudCwgMCwgY250
KTsNCg0KLyoNCiAqIHN1cHBseSBhIHdvcmQgIGVuZGluZyB3aXRoIGVyMnAxIGdseXBoLiAoZXh0
ZW50ZWQgZnJvbSBQaW55aW4gcnVsZSkNCiAqLw0KCWlmIChlcl9mbGFnKQ0KCXsNCgkJc3RyY3B5
KHN0c1tjbnRdLCAiZXIycDEiKTsNCgkJbmM9Y250KzE7DQoJfWVsc2UgbmM9Y250Ow0KCWlmICgh
YWxfZmxhZykgcmV0dXJuKG5jKTsNCgkNCi8qDQogKiBzdXBwbHkgYW4gYWx0ZXJuYXRpdmUgZGlz
YXNzZW1ibGVkIHN0ZXBjb2RlcyANCiAqLw0KCXc9d29yZCsxOw0KCXdoaWxlIChhbF9mbGFnKQ0K
CXsNCgkJd2hpbGUoaXNhbHBoYSgqdykmJiBhbF9mbGFnKQ0KCQl7IA0KCQkgIGlmICgqdz09J24n
KQ0KCQkgIHsgKyt3OyBudD13OysrbnQ7IA0KCQkJICBpZigqdz09J2EnfHwoKnc9PSdnJyYmKm50
PT0nYScpKSAvKmZvdW5kICovDQoJCQkgIHsNCgkJCSAgICAgaGQ9dy0yOyAtLWFsX2ZsYWc7DQoJ
CQkgICAgIHdoaWxlIChoZD53b3JkICYmIGlzdm93ZWwoKmhkKSkgLS1oZDsNCgkJCSAgICAgaWYg
KCpoZD09J2gnKQ0KCQkJICAgICB7ICB2aD1oZC0xOw0KCQkJICAgICAgICBpZiAoaXN1cHBlcigq
dmgpKSAqdmg9dG9sb3dlcigqdmgpOw0KCQkJICAgICAgICBpZiAoKnZoPT0neid8fCp2aD09J2Mn
fHwqdmg9PSdzJykgaGQ9dmg7DQoJCQkgICAgIH0NCgkJCSAgICAgaWYgKCp3PT0nYScpbnQ9dzsg
IC8qIGVsc2Ugbm8gY2hhbmdlKi8NCgkJCSAgICAgc3RybmNweShzdHNbbmNdLCBoZCwgbnQtaGQp
Ow0KCQkJICAgICArK25jOyB3PW50O2hkPW50Ow0KCQkgICB9ICAgICAgfQ0KCQkgICArK3c7DQoJ
CX0NCgkJd2hpbGUgKGlzYWxwaGEoKm50KSkgKytudDsNCgkJc3RybmNweShzdHNbbmNdLCBoZCwg
bnQtaGQpOw0KCQluYysrOw0KCX0NCglhcHBlbmRfc3VmZml4KG50LCBuYy1jbnQsIG5jKTsNCgly
ZXR1cm4obmMpOw0KfQ0KDQoNCltBcHBlbmRpeCBFXSBTYW1wbGUgTGFuZ3VhZ2UgdGFncyBvZiBb
VU5JQ09ERV0gQmxvY2tzDQoNClRhZwlTdGFydAlFbmQJU3RhcnQJRW5kCVN0YXJ0CUVuZA0KQ3ly
LQlVKzA0MDEJVSswNGNjCQkJCQkobm90IGluIFtJU082MzldKQ0KY2prLQlVKzMxMDUJVSszMTJj
CVUrMzQwMAlVKzRkYmYgVSs0ZTAwCVUrOWZmZgkoVW5pZmllZCBDSkspDQprcm8tCVUrMzQwMCAg
VSszZDJkDQpsYXQtCVUrMDAzMAlVKzAzZjUJCQkJCShpbmNsdWRlIEdyZWVrKQ0KdXNhLSAJVSsw
MDMwCVUrMDAzOQlVKzAwNjEgVSswMDdhICBVKzAwMmQgVSswMDJkICAobm90IGluIFtJU082Mzld
KQ0K
----__JNP_000_7c06.7909.59bc--



From owner-idn@ops.ietf.org  Mon Jul 23 14:53:22 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA15757
	for <idn-archive@lists.ietf.org>; Mon, 23 Jul 2001 14:53:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OkGI-000ETU-00
	for idn-data@psg.com; Mon, 23 Jul 2001 11:16:58 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15OkGH-000ETK-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 11:16:57 -0700
Received: from [24.252.219.84] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.8)
  with ESMTP-TLS id 190563; Sun, 22 Jul 2001 13:16:07 -0500
Message-ID: <3B5C6A12.6BDD6AAF@ehsco.com>
Date: Mon, 23 Jul 2001 13:16:50 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Paul Hoffman / IMC <phoffman@imc.org>
CC: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <200107231126.NAA05269@valinor.malmo.trab.se> <p05100317b782111dc570@[165.227.249.20]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> > > In the IDNA proposal we have specified that an application which
> > > handle IDNA (like you seem to say that the browser is) only
> > > support IDNA if also the content of the clipboard is converted
> > > to ACE before the domainname is passed to other applications
> > > (which doesn't handle IDNA/ACE solution).
> >
> >In that case IDNA is impossible. It is impossible for a browser to
> >know what text in a web page is a host name.
> 
> Not true. ACE names are quite easy to pick out of document content:
> they have the name prefixes.

This assumes that it wasn't written and stored in transliterated form. I
would think that the native format will be the most common for
user-written material (especially email bodies), not ACE. This goes
against the original argument. Requiring these products to encode email
addresses as ACE will be difficult, if not impossible. Every string that
looked like an email address which really wasn't an email address (this
goes into the realm of document contents; passwords can have ldh@ldh.ldh
syntax, for example) would be broken by the converter.

For HTML with links, URLs will require ACE for some time, so the argument
is more valid there (at least until HTML makes the URL guessing invalid).
But for things like HTML lists of POP3 servers which do not have common or
widely-used URLs, it once again becomes difficult for an agent to
automatically convert native-format hostnames into ACE.

I really don't think a mandatory look-alike conversion will work. The
strongest emphasis I would put on it would be MAY, with a strong caveat.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Mon Jul 23 14:54:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA15842
	for <idn-archive@lists.ietf.org>; Mon, 23 Jul 2001 14:54:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ojcf-000DFH-00
	for idn-data@psg.com; Mon, 23 Jul 2001 10:36:01 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ojce-000DFA-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 10:36:00 -0700
Received: from [165.227.249.20] (ip20.proper.com [165.227.249.20])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f6NHZvq00764
	for <idn@ops.ietf.org>; Mon, 23 Jul 2001 10:35:58 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100315b7820b646d61@[165.227.249.20]>
In-Reply-To: <200107230925.LAA05222@valinor.malmo.trab.se>
References: <200107230925.LAA05222@valinor.malmo.trab.se>
Date: Mon, 23 Jul 2001 10:34:52 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality   
 Check)
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 11:25 AM +0200 7/23/01, Dan Oscarsson wrote:
>Also it does not matter if nameprep is not applied at the client
>end, the DNS server will do nameprep before comparing names - so it
>will work anyway.

Dan, it is not clear from the udns-02 document that the protocol 
requires nameprep on the name server for every query. This is a 
fairly important design choice of UDNS that should probably be 
highlighted in the document. As you have seen, some people who 
thought they were supporting udns-02 don't think this is such a great 
idea, and it is quite controversial for name servers that run high 
volumes of queries (like tens of thousands a second).

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Mon Jul 23 15:06:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA16503
	for <idn-archive@lists.ietf.org>; Mon, 23 Jul 2001 15:06:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OdW9-0005Jx-00
	for idn-data@psg.com; Mon, 23 Jul 2001 04:04:53 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15OdW8-0005Jk-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 04:04:52 -0700
Received: from valinor.malmo.trab.se (valinor [131.115.48.20]) by malmo.trab.se (8.10.1/TRAB-primary-2) with ESMTP id f6NB31P23878; Mon, 23 Jul 2001 13:03:02 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Mon, 23 Jul 2001 13:02:05 +0200 (MEST) (MET)
Message-Id: <200107231102.NAA05257@valinor.malmo.trab.se>
Date: Mon, 23 Jul 2001 13:02:05 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: [idn] Debunking the ACE myth
To: idn@ops.ietf.org, amc@cs.berkeley.edu
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: qskEuHFTii/MxHRIs3B8WQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Adam M. Costello wrote:


>It's undeniable that ACE is more backward-compatible, and fails in fewer
>instances, than any 8-bit encoding.  

Especially if ACE is never decoded into the non-ASCII characters it represent.
The moment ACE is decoded, ACE will have the same failures that using UTF-8
would result in.

  Dan




From owner-idn@ops.ietf.org  Mon Jul 23 15:06:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA16568
	for <idn-archive@lists.ietf.org>; Mon, 23 Jul 2001 15:06:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OjfV-000DJw-00
	for idn-data@psg.com; Mon, 23 Jul 2001 10:38:57 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15OjfU-000DJq-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 10:38:56 -0700
Received: from [165.227.249.20] (ip20.proper.com [165.227.249.20])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f6NHcrq00824
	for <idn@ops.ietf.org>; Mon, 23 Jul 2001 10:38:53 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100317b782111dc570@[165.227.249.20]>
In-Reply-To: <200107231126.NAA05269@valinor.malmo.trab.se>
References: <200107231126.NAA05269@valinor.malmo.trab.se>
Date: Mon, 23 Jul 2001 10:37:48 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] Debunking the ACE myth
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 1:26 PM +0200 7/23/01, Dan Oscarsson wrote:
>Patrik said:
>  >In the IDNA proposal we have specified that an application which handle
>>IDNA (like you seem to say that the browser is) only support IDNA if also
>>the content of the clipboard is converted to ACE before the domainname is
>>passed to other applications (which doesn't handle IDNA/ACE solution).
>>
>
>In that case IDNA is impossible. It is impossible for a browser to know
>what text in a web page is a host name.

Not true. ACE names are quite easy to pick out of document content: 
they have the name prefixes.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Mon Jul 23 15:11:54 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17013
	for <idn-archive@lists.ietf.org>; Mon, 23 Jul 2001 15:11:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Oc14-0003w1-00
	for idn-data@psg.com; Mon, 23 Jul 2001 02:28:42 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Oc13-0003vv-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 02:28:41 -0700
Received: from valinor.malmo.trab.se (valinor [131.115.48.20]) by malmo.trab.se (8.10.1/TRAB-primary-2) with ESMTP id f6N9QqP17837; Mon, 23 Jul 2001 11:26:52 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Mon, 23 Jul 2001 11:25:56 +0200 (MEST) (MET)
Message-Id: <200107230925.LAA05222@valinor.malmo.trab.se>
Date: Mon, 23 Jul 2001 11:25:56 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality    Check)
To: paf@cisco.com, duerst@w3.org
Cc: idn@ops.ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=ISO-8859-1
Content-MD5: OOBVEhN9SYwqmWvE0TfTSA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by ietf.org id PAA17013


>At 19:04 01/07/17 +0200, Patrik F$BgM(Btstr$B‹N(B wrote:
>>--On 01-07-18 01.12 +0900 Martin Duerst <duerst@w3.org> wrote:
>>
>> > Again, nameprep only is easier than nameprep+ACE.
>> > And as I have explained to Patrick, while on the registration
>> > side, 100% nameprep and nothing less is extremely important,
>> > on the application side, it's not really that important.
>>
>>The day an online stock trader doesn't get his bid in to the broker because
>>he typed the wrong version of what according to nameprep is the wrong
>>character, you loose.
>
>This is just spreading FUD. No halfway serious online trader types
>in the broker address every time he trades. For that, there are
>things such as bookmarks and autocompletion.

Also it does not matter if nameprep is not applied at the client
end, the DNS server will do nameprep before comparing names - so it
will work anyway.

   Dan




From owner-idn@ops.ietf.org  Mon Jul 23 15:13:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17095
	for <idn-archive@lists.ietf.org>; Mon, 23 Jul 2001 15:13:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OkuX-000FdE-00
	for idn-data@psg.com; Mon, 23 Jul 2001 11:58:33 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15OkuW-000Fcu-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 11:58:32 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA04525;
        Mon, 23 Jul 2001 14:58:29 -0400 (EDT)
Message-Id: <200107231858.OAA04525@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Paul Hoffman / IMC <phoffman@imc.org>
cc: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth 
In-reply-to: Your message of "Mon, 23 Jul 2001 10:37:48 PDT."
             <p05100317b782111dc570@[165.227.249.20]> 
Date: Mon, 23 Jul 2001 14:58:28 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Not true. ACE names are quite easy to pick out of document content:
> they have the name prefixes.

actually, ACE names are far easier to pick out of a document than
UTF-8 names.  while we have conventions for which characters are
allowable (for many applications) in an ASCII name (letters, digits,
hypens embedded within a label), we no such conventions for UTF-8 names.

Keith



From owner-idn@ops.ietf.org  Mon Jul 23 15:13:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17106
	for <idn-archive@lists.ietf.org>; Mon, 23 Jul 2001 15:13:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OdfB-0005T5-00
	for idn-data@psg.com; Mon, 23 Jul 2001 04:14:13 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15OdfA-0005Sz-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 04:14:12 -0700
Received: from valinor.malmo.trab.se (valinor [131.115.48.20]) by malmo.trab.se (8.10.1/TRAB-primary-2) with ESMTP id f6NBCNP24111; Mon, 23 Jul 2001 13:12:23 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Mon, 23 Jul 2001 13:11:26 +0200 (MEST) (MET)
Message-Id: <200107231111.NAA05262@valinor.malmo.trab.se>
Date: Mon, 23 Jul 2001 13:11:26 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: [idn] nameprep failures
To: idn@ops.ietf.org, amc@cs.berkeley.edu
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: SqWvXRBJJdWq1vLA6KLp4w==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Adam M. Costello wrote:


>> If I see WWW.AOL.COM, where the A is actually a capital Alpha, then
>> I'm sure I'll type it incorrectly.  So why doesn't nameprep prohibit
>> Alpha?
>
>[Nitpick:  I wouldn't say you typed it incorrectly, I'd say you read it
>incorrectly, then typed exactly what you intended to type.]

Actually the A used in English has the same origin as the Greek Alpha.
So you could very well see them as the same letter. The difference is
that when using Greek you use a different glyph for the lower case
form. I am sure there are many names in Greek or using Cyrillic letters
that will use only glyphs that are exactely the same as in "Latin" making
it impossible to from a printed paper identify what alphabet they belong
to.

So there is sure to be problems unless matching glyphs are matched
as equivalent.

   Dan




From owner-idn@ops.ietf.org  Mon Jul 23 15:13:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17128
	for <idn-archive@lists.ietf.org>; Mon, 23 Jul 2001 15:13:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Odth-0005hv-00
	for idn-data@psg.com; Mon, 23 Jul 2001 04:29:13 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Odtg-0005hp-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 04:29:12 -0700
Received: from valinor.malmo.trab.se (valinor [131.115.48.20]) by malmo.trab.se (8.10.1/TRAB-primary-2) with ESMTP id f6NBRLP24546; Mon, 23 Jul 2001 13:27:21 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Mon, 23 Jul 2001 13:26:25 +0200 (MEST) (MET)
Message-Id: <200107231126.NAA05269@valinor.malmo.trab.se>
Date: Mon, 23 Jul 2001 13:26:25 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: [idn] Debunking the ACE myth
To: djb@cr.yp.to, idn@ops.ietf.org, paf@cisco.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: x2GkUpR11n/lcgQhB9rK4Q==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Patrik said:

>--On 01-07-18 06.46 +0000 "D. J. Bernstein" <djb@cr.yp.to> wrote:
>
>> What went wrong is that the browser displayed the address as Unicode
>> characters. The address then passed through the (CTEXT UTF-8, although
>> UTF8_STRING would be better) copy-and-paste mechanism, the UTF-8 xterm,
>> the mail client, and the 8-bit-clean MTA, none of which converted back
>> to ACE. The resulting UTF-8 DNS lookup produced NXDOMAIN.
>
>In the IDNA proposal we have specified that an application which handle
>IDNA (like you seem to say that the browser is) only support IDNA if also
>the content of the clipboard is converted to ACE before the domainname is
>passed to other applications (which doesn't handle IDNA/ACE solution).
>

In that case IDNA is impossible. It is impossible for a browser to know
what text in a web page is a host name. A host name can occur anywhere in
the text of a document. And I can cut and paste any part of it.
It will be impossible or a browser to identify what parts are host names
and ACE encode them.
Also quite confusing for a user if it should happen, because when they
copy and paste a host name from the browser into a mail application the
pasted text is suddenly totally different.

   Dan




From owner-idn@ops.ietf.org  Mon Jul 23 15:14:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17189
	for <idn-archive@lists.ietf.org>; Mon, 23 Jul 2001 15:14:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Oe7k-0005vs-00
	for idn-data@psg.com; Mon, 23 Jul 2001 04:43:44 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Oe7j-0005vl-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 04:43:43 -0700
Received: from valinor.malmo.trab.se (valinor [131.115.48.20]) by malmo.trab.se (8.10.1/TRAB-primary-2) with ESMTP id f6NBfsP26433; Mon, 23 Jul 2001 13:41:54 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Mon, 23 Jul 2001 13:40:58 +0200 (MEST) (MET)
Message-Id: <200107231140.NAA05286@valinor.malmo.trab.se>
Date: Mon, 23 Jul 2001 13:40:58 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: [idn] Debunking the ACE myth
To: idn@ops.ietf.org, djb@cr.yp.to
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: jgAUtin79wUJ/zRAdaMgaA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk

D. J. Bernstein said:

>
>Wrong again. UTF-8 poses no problems for DNS servers. As Mark Andrews
>says: ``UTF8 does not require a server upgrade.''
>

No that is not correct. For both ACE and UTF-8 there are two
ways that it can be done:
1) All names are transmitted in a form/semantic insensitive format
   (that is what nameprep is for) so that names can be compared
   using binary matching.
   
   In this case a server upgrade is NOT required.
   
2) Names are transmitted with form retained (that is any form, though
   they should be normalised).
   In this case the applications that do name comparing need to to
   convert them into the form/semantic insensitive format before comparing
   them (or do it on the fly while comparing them).
   
   In this case the DNS servers need to be upgraded.
   
   
1) Is the IDNA case and also in Microsofts draft-skwan-utf8-dns.
   This results in that for example upper case characters cannot be
   used in responses from DNS. Probably very irritating some people
   who have spent a lot of mony on their nice company name which uses
   mixed case and will break some programs expecting mixed case
   in PTR responses.
   

   Dan




From owner-idn@ops.ietf.org  Mon Jul 23 15:14:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17241
	for <idn-archive@lists.ietf.org>; Mon, 23 Jul 2001 15:14:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OcPq-0004I6-00
	for idn-data@psg.com; Mon, 23 Jul 2001 02:54:18 -0700
Received: from [209.187.148.217] (helo=P2)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15OcPp-0004I0-00; Mon, 23 Jul 2001 02:54:18 -0700
Date: Mon, 23 Jul 2001 05:54:16 -0400
From: John C Klensin <klensin@jck.com>
To: Dan Oscarsson <Dan.Oscarsson@trab.se>
cc: idn@ops.ietf.org
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn]
 Reality    Check)
Message-ID: <44679221.995867656@P2>
In-Reply-To: <200107230925.LAA05222@valinor.malmo.trab.se>
References:  <200107230925.LAA05222@valinor.malmo.trab.se>
X-Mailer: Mulberry/2.1.0b2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Monday, 23 July, 2001 11:25 +0200 Dan Oscarsson
<Dan.Oscarsson@trab.se> wrote:

> 
>> At 19:04 01/07/17 +0200, Patrik F$BgM(Btstr$B?N(B wrote:
>>> --On 01-07-18 01.12 +0900 Martin Duerst <duerst@w3.org>
>>> wrote:
>>> 
>>> > Again, nameprep only is easier than nameprep+ACE.
>>> > And as I have explained to Patrick, while on the
>>> > registration side, 100% nameprep and nothing less is
>>> > extremely important, on the application side, it's not
>>> > really that important.
>>> 
>>> The day an online stock trader doesn't get his bid in to the
>>> broker because he typed the wrong version of what according
>>> to nameprep is the wrong character, you loose.
>> 
>> This is just spreading FUD. No halfway serious online trader
>> types in the broker address every time he trades. For that,
>> there are things such as bookmarks and autocompletion.
> 
> Also it does not matter if nameprep is not applied at the
> client end, the DNS server will do nameprep before comparing
> names - so it will work anyway.

Dan,

The above sounds to me as if we are back to requiring that all
servers need to be upgraded in order to have things work
properly.  Certainly no DNS server deployed today does nameprep
before comparing names.  That assumption of massive, more or
less concurrent, upgrades, or its alternative, that we are
willing to tolerate a long-ish period in which things don't work
predictably, are the ones I though the WG concluded it could not
make.

   john






From owner-idn@ops.ietf.org  Mon Jul 23 15:15:01 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17260
	for <idn-archive@lists.ietf.org>; Mon, 23 Jul 2001 15:15:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OciD-0004ZY-00
	for idn-data@psg.com; Mon, 23 Jul 2001 03:13:17 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15OciC-0004ZQ-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 03:13:16 -0700
Received: from enoshima (dhcp-100-151.mag.keio.ac.jp [133.27.195.151])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id TAA02689;
	Mon, 23 Jul 2001 19:09:30 +0900 (JST)
Message-Id: <4.2.0.58.J.20010723185321.03521330@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Mon, 23 Jul 2001 18:58:58 +0900
To: Dan Oscarsson <Dan.Oscarsson@trab.se>, paf@cisco.com
From: Martin Duerst <duerst@w3.org>
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality   
  Check)
Cc: idn@ops.ietf.org
In-Reply-To: <200107230925.LAA05222@valinor.malmo.trab.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

At 11:25 01/07/23 +0200, Dan Oscarsson wrote:

> >At 19:04 01/07/17 +0200, Patrik F$BgM(Btstr$B$B5/(B(B wrote:
> >>--On 01-07-18 01.12 +0900 Martin Duerst <duerst@w3.org> wrote:
> >>
> >> > Again, nameprep only is easier than nameprep+ACE.
> >> > And as I have explained to Patrick, while on the registration
> >> > side, 100% nameprep and nothing less is extremely important,
> >> > on the application side, it's not really that important.
> >>
> >>The day an online stock trader doesn't get his bid in to the broker because
> >>he typed the wrong version of what according to nameprep is the wrong
> >>character, you loose.
> >
> >This is just spreading FUD. No halfway serious online trader types
> >in the broker address every time he trades. For that, there are
> >things such as bookmarks and autocompletion.
>
>Also it does not matter if nameprep is not applied at the client
>end, the DNS server will do nameprep before comparing names - so it
>will work anyway.

I was not assuming that nameprep is done in the servers.
I think it's not a good idea to do that; it's too much load on
the servers, and too difficult to upgrade,...

But from private mail that I got, it seemed like others also
understood that I was commenting under that assumption.

Regards,    Martin.



From owner-idn@ops.ietf.org  Mon Jul 23 15:40:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA18739
	for <idn-archive@lists.ietf.org>; Mon, 23 Jul 2001 15:40:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ol5e-000Fvi-00
	for idn-data@psg.com; Mon, 23 Jul 2001 12:10:02 -0700
Received: from mail07a.vwh1.net ([209.238.9.57])
	by psg.com with smtp (Exim 3.31 #1)
	id 15Ol5c-000FvN-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 12:10:01 -0700
Received: from www.langoo.net (208.55.128.123)
	by mail07a.vwh1.net (RS ver 1.0.60s) with SMTP id 024466128;
	Mon, 23 Jul 2001 15:00:13 -0400 (EDT)
From: "Deven Kalra" <kalra@langoo.net>
To: <idn@ops.ietf.org>
Cc: "Soobok Lee" <lsb@postel.co.kr>
Subject: RE: [idn] Indian scripts and similarities
Date: Mon, 23 Jul 2001 12:00:20 -0700
Message-ID: <JMEEJIPINNOMDJMPPAMKMEHADGAA.kalra@langoo.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <002701c1125a$64578b20$ed1bd9d2@postel.co.kr>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
X-Loop-Detect: 1
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

This is indeed an interesting and potentially complex problem.
BTW, I am from India. Here is my take on it.
The North Indian languages (Hindi, Gujarati, Punjabi (using the Gurmukhi
script), Bengali etc.) are similar in structure and have been derived from
and closely related to the Devanagari script. Similarly the South Indian
languages have similar structure having been derived from another heritage
though most use Sanskrit words also (written in the respective script, not
in Devanagari).

Building a conversion table between the languages, in my opinion, will not
be a good solution since it will make a large number of URLs not usable. If
a person in Gujarat gets a URL for his business, it effectively will prevent
that URL in any of the other languages to be used. This could be tens of
languages for the Indian scenario.

I think that for the Indian languages the straight unicode based scheme
should be retained. Consider the following scenarios:

1) A guy in types namaskar.com in Bengali. He expects to either go to a
bengali site or be told that no such (bengali) site exists. Suppose there
was a gujarati namaskar.com site and we had implemented equivalence, and
took the bengali guy to the gujarati site, it would be completely
disorienting to him.

2) When the guy is registering, he will hopefully be registering with a
wysiwig input method (one of which is made by my company, Langoo.com), where
he will see the in-language characters. Therefore, domain registration
should be unambiguous as it relates to the Indian scripts.

If a URL was in a written form, as in an e-mail, there would be no problem.
The script will tell what language the url is in. If the URL was conveyed in
the spoken form then the ambiguity could exist. Again, if both the speaker
and the listener were of similar cultural and language background, they
would guess pretty accurately what was meant. One scenario where ambiguity
will exist will be for people who know more than one Indian language and
cannot tell by context which language url was in.  For example, if I called
someone on the phone and said, "Check out namaskar.com"  (namaskar is the
word for "greetings" in most of India) and my recepient knew both Gujarati
and Hindi. Since he knows me to be a Hindi speaker, he might think I meant
the Hindi URL. Since he is Gujarati, he might also think that I meant the
Gujarati URL.

Though this is possible, it will not be that frequent. In some sense, it is
similar to the English homonym problems where more than one word has the
same pronunciation and one has to disambiguate by context or by trial. In my
opinion, in India though the languages have similarity, they are spoken by
different and disjoint groups of people. The cultural background of these
groups is also quite different. Chinese speakers probably share more common
cultural background and have more potential for simplified/traditional
confusion.

Deven


-----Original Message-----
From: owner-idn@ops.ietf.org [mailto:owner-idn@ops.ietf.org]On Behalf Of
Soobok Lee
Sent: Saturday, July 21, 2001 8:00 PM
To: idn@ops.ietf.org
Subject: [idn] Indian scripts and similarities


Hi,

Recently, I found many similarities between Indian language scripts.

  Go to http://www.aczone.com/itrans/tblall/tblall.html
  and click 'Vowel', 'Consonant' and 'Digits' links and look into
  the script comparison tables.

Compare these pairs of scripts:
  1.  Devanagari vs Bengali
  2.  Gujarati  vs Gurmukhi
  3.  Kannada vs Telugu

If indian business names in an Indian state can be expressed
both in its official language scripts
and in its second language scripts (maybe the official one of another
state),
there may be name collisions across Indian states.

Do we need equivalence-conversion tables among Indian language scripts
like that of Traditional/Simplified chinese conversion table
proposed by CNNIC?

Regards,

Soobok Lee





From owner-idn@ops.ietf.org  Mon Jul 23 16:06:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA20285
	for <idn-archive@lists.ietf.org>; Mon, 23 Jul 2001 16:06:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Olix-000H0K-00
	for idn-data@psg.com; Mon, 23 Jul 2001 12:50:39 -0700
Received: from shell.nominum.com ([204.152.187.59])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Oliw-000H09-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 12:50:38 -0700
Received: from drc-toshiba.nominum.com (shell.nominum.com [204.152.187.59])
	by shell.nominum.com (Postfix) with ESMTP
	id A598931914; Mon, 23 Jul 2001 12:50:25 -0700 (PDT)
Message-Id: <5.0.2.1.2.20010723124833.03150ed0@localhost>
X-Sender: drc@localhost
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Mon, 23 Jul 2001 12:50:25 -0700
To: Keith Moore <moore@cs.utk.edu>, Paul Hoffman / IMC <phoffman@imc.org>
From: "David R. Conrad" <david.conrad@nominum.com>
Subject: Re: [idn] Debunking the ACE myth 
Cc: idn@ops.ietf.org
In-Reply-To: <200107231858.OAA04525@astro.cs.utk.edu>
References: <Your message of "Mon, 23 Jul 2001 10:37:48 PDT." <p05100317b782111dc570@[165.227.249.20]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hi,

At 02:58 PM 7/23/2001 -0400, Keith Moore wrote:
>actually, ACE names are far easier to pick out of a document than
>UTF-8 names.

I thought the point of UTF-8 was that you wouldn't need to.

Rgds,
-drc




From owner-idn@ops.ietf.org  Mon Jul 23 20:49:56 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA05080
	for <idn-archive@lists.ietf.org>; Mon, 23 Jul 2001 20:49:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Oput-000OZP-00
	for idn-data@psg.com; Mon, 23 Jul 2001 17:19:15 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Opus-000OZH-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 17:19:15 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15Opus-0002BL-00; Mon, 23 Jul 2001 17:19:14 -0700
Date: Tue, 24 Jul 2001 00:19:14 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
Message-ID: <20010724001913.J5061@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200107231140.NAA05286@valinor.malmo.trab.se>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dan Oscarsson <Dan.Oscarsson@trab.se> wrote:

> For both ACE and UTF-8 there are two ways that it can be done:
>
> 1) All names are transmitted in a form/semantic insensitive format
> (that is what nameprep is for) so that names can be compared using
> binary matching.
>
> 2) Names are transmitted with form retained (that is any form, though
> they should be normalised).
>
> 1) is the IDNA case and also in Microsofts draft-skwan-utf8-dns.  This
> results in that for example upper case characters cannot be used in
> responses from DNS.

For the UTF-8 case, as I've pointed out before, it is not necessary
for DNS queries and DNS responses to use the same rules.  It would
be perfectly reasonable to use nameprep'd UTF-8 in queries and
non-nameprep'd UTF-8 in responses.

For the ACE case, as I've pointed out before, mixed-case ACE can easily
be used to represent mixed-case Unicode.  You would lose things like
circled-digit-one (which becomes a regular digit-one), but mixed case
can be conveyed in ACE.

By the way, it would be pointless to combine ACE with option 2 (no
nameprep).

AMC



From owner-idn@ops.ietf.org  Tue Jul 24 01:24:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA15444
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 01:24:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ou9U-0005IS-00
	for idn-data@psg.com; Mon, 23 Jul 2001 21:50:36 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ou9T-0005IF-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 21:50:35 -0700
Received: from zetnet.co.uk (man-s266.dialup.zetnet.co.uk [194.247.45.137])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6O4kw626389;
	Tue, 24 Jul 2001 05:46:59 +0100
Message-ID: <3B5C9B87.BC228E7@zetnet.co.uk>
Date: Mon, 23 Jul 2001 22:47:51 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: John C Klensin <klensin@jck.com>, idn@ops.ietf.org
Subject: [idn] Re: Just send UTF-8 with nameprep
References: <200107230925.LAA05222@valinor.malmo.trab.se> <44679221.995867656@P2>
Content-Type: text/plain; charset=UTF-8
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id BAA15444

-----BEGIN PGP SIGNED MESSAGE-----

John C Klensin wrote:
> Dan Oscarsson <Dan.Oscarsson@trab.se> wrote:
> >> Patrik Fältström wrote:
> >>> The day an online stock trader doesn't get his bid in to the
> >>> broker because he typed the wrong version of what according
> >>> to nameprep is the wrong character, you loose.
> >>
> >> This is just spreading FUD. No halfway serious online trader
> >> types in the broker address every time he trades. For that,
> >> there are things such as bookmarks and autocompletion.
> >
> > Also it does not matter if nameprep is not applied at the
> > client end, the DNS server will do nameprep before comparing
> > names - so it will work anyway.
> 
> Dan,
> 
> The above sounds to me as if we are back to requiring that all
> servers need to be upgraded in order to have things work
> properly.

No: only authoritative servers for zones that include IDNs (for proposals
where these servers do nameprep). It doesn't matter that intermediate
servers and proxies don't do nameprep, as long as they are 8-bit clean [*],
which they should be already according to RFC 1034 ("we may someday need
to add full binary domain names for new services"), and RFC 2181 ("any
binary string whatever can be used as the label of any resource record").


[*] "8-bit clean" here means able to handle LDH bytes and bytes >= 0x80.
    For example, if a server cannot handle zero bytes, even though that
    is not compliant with RFC 2181, it would not prevent the server from
    being 8-bit clean in this sense.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO1ybUjkCAxeYt5gVAQG0Sgf9FbaaDY7WeNJq+jc9QjvXBeo07cf84Y7b
bNp69SXMk8FaoTMOdxfGX6oAME3ipQsA0EmqMoOTl7djrZqAZ/QDbflPQVSe1idX
+RGE8wZVI5hRGFIYhnPHm75/m0iZGEj23BDsXBWRmChmK4GzGD/4VxY8q24B0zek
VxCjvcwSyCbxp3e61f6o21jdT8t81Xqb4MLsBUB18Q2mnXOyyT2ONzv067R1ECJl
jayiWOjPmULWK6dabCMzlHwpEsTug2G9siCDVEPnFG+fbjk+wPrugDLtDrCRJ4cQ
lETdvo9bFiVxplK99RRej8BivCp1Z0VO8YXgbP1nY9yoHifB7IUSzg==
=c2MH
-----END PGP SIGNATURE-----





From owner-idn@ops.ietf.org  Tue Jul 24 01:24:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA15457
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 01:24:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OuTA-0005v2-00
	for idn-data@psg.com; Mon, 23 Jul 2001 22:10:56 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.31 #1)
	id 15OuT9-0005us-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 22:10:56 -0700
Received: (qmail 9038 invoked from network); 24 Jul 2001 12:29:46 -0000
Received: from chubby.internal.realnames.com (HELO heaven.internal.realnames.com) (10.1.5.39)
  by friendly.realnames.com with SMTP; 24 Jul 2001 12:29:46 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:3173]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <127313@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Mon, 23 Jul 2001 10:09:19 PM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2650.21)
	id <PJWHMNBV>; Mon, 23 Jul 2001 22:10:45 -0700
Message-ID: <B7233BD6980AD411875700508B5BD5D2011E96BC@elporto.internal.realnames.com>
From: =?utf-8?B?WXZlcyBBcnJvdXll?= <yves@realnames.com>
To: idn@ops.ietf.org
Subject: [idn] =?utf-8?B?UkU6IFtpZG5dIERlYnVua2luZyB0aGUgQUNFIG15dGg=?=
Date: Mon, 23 Jul 2001 22:10:44 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="utf-8"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> You're going to rely on the dq-- or whatever prefix to find 
> names in free
> text? Now I like IDNA even less than I did before.

FWIW a lot of MUAs do this today to let you follow a link in plain text
e-mail. They recognize URIs, even www.*, ftp.*, ..., host names, and turn
them into links. Nothing new.

YA



From owner-idn@ops.ietf.org  Tue Jul 24 01:24:15 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA15483
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 01:24:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ou6q-0005Ci-00
	for idn-data@psg.com; Mon, 23 Jul 2001 21:47:52 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ou6p-0005CZ-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 21:47:51 -0700
Received: from zetnet.co.uk (man-s266.dialup.zetnet.co.uk [194.247.45.137])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6O4lK626419;
	Tue, 24 Jul 2001 05:47:21 +0100
Message-ID: <3B5CA488.3192EB47@zetnet.co.uk>
Date: Mon, 23 Jul 2001 23:26:17 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: Paul Hoffman / IMC <phoffman@imc.org>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <200107231126.NAA05269@valinor.malmo.trab.se> <p05100317b782111dc570@[165.227.249.20]>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

Paul Hoffman / IMC wrote:
> At 1:26 PM +0200 7/23/01, Dan Oscarsson wrote:
> >Patrik said:
> >>In the IDNA proposal we have specified that an application which handle
> >>IDNA (like you seem to say that the browser is) only support IDNA if also
> >>the content of the clipboard is converted to ACE before the domainname is
> >>passed to other applications (which doesn't handle IDNA/ACE solution).
> >
> >In that case IDNA is impossible. It is impossible for a browser to know
> >what text in a web page is a host name.
> 
> Not true. ACE names are quite easy to pick out of document content:
> they have the name prefixes.

You're going to rely on the dq-- or whatever prefix to find names in free
text? Now I like IDNA even less than I did before.

IMHO, finding names in free text is excessively complicated, probably
unreliable, and should not be attempted. It *is* practical to define
special cut and paste behaviour for specific well-defined contexts (like
RFC 2822 headers and browser location bars, for example), because an
application can use specially designed widgets for display and editing
in those contexts. Such widgets can also help users to type valid names
(by doing what Dan Bernstein calls "fast nameprep", although speed is
not the main advantage).

Trying to do anything more complicated than that to make cut and paste
work is simply a bad idea.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO1ykZDkCAxeYt5gVAQGUNwgAoqAy7KqCtGT7koT0WKRN5mbNsJqLT/+9
V6ssp8++Jj+/CJXP7Z0wyxZN/x4oML1G7xBNFUauOQahAlE4Ju98WO///pppFY9P
uTf93zs0CBtNQzvneou+99lSw1tQKqXlxB5S3awOu4UsCw3ZxioMy4vtO68uC8Kh
C0eKagSVvCJoWVODY7D9DTgAHYVZG0FFTZoUg8qBKm9C/WJ9LZ8iYfwvJme+NCx0
+rP/ZXqbVCyO3kkpTsvOrbV//zl2EGL1i5e84JI/nPcvqMA3NDdNTJ9ldxMhOKef
ypgjDK2sVL6/GnWIcHthakT0oTGJzyBQdnWfqbkeh9wJWjBSYI29eg==
=UDsR
-----END PGP SIGNATURE-----





From owner-idn@ops.ietf.org  Tue Jul 24 01:24:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA15495
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 01:24:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ou7z-0005Fi-00
	for idn-data@psg.com; Mon, 23 Jul 2001 21:49:03 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ou7y-0005Fc-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 21:49:02 -0700
Received: from zetnet.co.uk (man-s266.dialup.zetnet.co.uk [194.247.45.137])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6O4l8626403;
	Tue, 24 Jul 2001 05:47:11 +0100
Message-ID: <3B5CA433.B5EAF9CC@zetnet.co.uk>
Date: Mon, 23 Jul 2001 23:24:51 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: Dan Oscarsson <Dan.Oscarsson@trab.se>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <200107231140.NAA05286@valinor.malmo.trab.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

Dan Oscarsson wrote:
> 1) [names on the wire are always canonicalised]
>    is the IDNA case and also in Microsofts draft-skwan-utf8-dns.
>    This results in that for example upper case characters cannot be
>    used in responses from DNS. Probably very irritating some people
>    who have spent a lot of mony on their nice company name which uses
>    mixed case and will break some programs expecting mixed case
>    in PTR responses.

What programs will break in this case? That doesn't sound remotely
plausible to me. If it turns out to be difficult to support case
preservation then that would be the first thing I'd discard: other
properties are far more important.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO1ykHTkCAxeYt5gVAQGHCAgAq3GNNVRoKdriRSvRja5JR9u2rltZRD/E
52LAqFE4T+F2kxRLUl97kFtCd0Q00vTasWIIWyKIG1aNwlalVjQy/7Y5jt9gQGc/
99ksiiad3jdEVGRrtDJNhYnMiuxx+rV8UH27+bfYDtMdDymt7CNfq5onNsdfKSgQ
PKUxxrvBeWhSB/p5oV5qOVlhSupWwksyqtE8DJLfUx+wq11dKaBOzvu/fnugpwPE
EyB4EDJhcaxm6hLvMRWP+fJDMX6hXujhrc1QXD3Tlgv0x0cOX0IvzN3V4qaRFwZj
a6GtzO5eq/UCtFt6ZHPqmud7sCD1NwGANRPxEe4MtTVcSL2oJtt43Q==
=GVWF
-----END PGP SIGNATURE-----





From owner-idn@ops.ietf.org  Tue Jul 24 01:30:54 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA15475
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 01:24:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ou8R-0005Ft-00
	for idn-data@psg.com; Mon, 23 Jul 2001 21:49:31 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ou8Q-0005Fn-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 21:49:31 -0700
Received: from zetnet.co.uk (man-s266.dialup.zetnet.co.uk [194.247.45.137])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6O4lb626451;
	Tue, 24 Jul 2001 05:47:39 +0100
Message-ID: <3B5CF9B3.236917BC@zetnet.co.uk>
Date: Tue, 24 Jul 2001 05:29:39 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: Dan Oscarsson <Dan.Oscarsson@trab.se>, idn@ops.ietf.org
Subject: Re: [idn] nameprep failures
References: <200107231111.NAA05262@valinor.malmo.trab.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

Dan Oscarsson wrote:
> Adam M. Costello wrote:
> >> If I see WWW.AOL.COM, where the A is actually a capital Alpha, then
> >> I'm sure I'll type it incorrectly.  So why doesn't nameprep prohibit
> >> Alpha?
> >
> >[Nitpick:  I wouldn't say you typed it incorrectly, I'd say you read it
> >incorrectly, then typed exactly what you intended to type.]
> 
> Actually the A used in English has the same origin as the Greek Alpha.
> So you could very well see them as the same letter. The difference is
> that when using Greek you use a different glyph for the lower case
> form. I am sure there are many names in Greek or using Cyrillic letters
> that will use only glyphs that are exactely the same as in "Latin" making
> it impossible to from a printed paper identify what alphabet they belong
> to.
> 
> So there is sure to be problems unless matching glyphs are matched
> as equivalent.

This is only a problem if someone is actually allowed to register
www.<alpha>ol.com. Even then, no-one will actually type "WWW.<Alpha>OL.COM"
by accident. So the only issue is that someone might put that in an
email or news article, say, in an attempt to mislead users who expect it
to point to AOL. Attacks that achieve the same effect are possible with
the current DNS (e.g. by sending an HTML e-mail but making it look like
text), and the sky isn't falling in because they are possible.

Nameprep may be able to catch some cases of ambiguous glyphs, but no
matter how much nameprep is tweaked, it will still be necessary for a
human employee of the relevant registrar to vet applications, to check
that names do not *look* (in any case permutation) as though they would
belong to some other entity not associated with the applicant.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO1z5hzkCAxeYt5gVAQGoFAf/eDHcwjohK5i7M56Qkzf/iwMXL58qHiem
0zlstmkMWYg4Xzd2jAaduaya5AwV9hDGLXXStQMEl/dLfQz/nyLMYDYcoH4WHjsR
VfNihlyyfAEXRhRRYLnBZxVNRILudknSOjXRm+KZrv9hEvfdZU0COJSgVaWo697x
IwYaUMrSPZSuCQ0QYtqxlvvZVQ11rAzRSrAgi6sWAokmpAsmh3Mf7FLORLTA5+ZS
DbXF124rPl1eqUL63uKqZk+TPXJrCIhKWwcYaf/NGXwDEyew0v7F8sfwIETukAev
Uu/PWC8nUAfEJgvB/9ogJjBaByxPl9VmO4uIRqqOHGgkN9kC7stxPw==
=H7HG
-----END PGP SIGNATURE-----





From owner-idn@ops.ietf.org  Tue Jul 24 02:55:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA02614
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 02:55:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OvbO-0008Y7-00
	for idn-data@psg.com; Mon, 23 Jul 2001 23:23:30 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15OvbN-0008Y1-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 23:23:30 -0700
Received: from valinor.malmo.trab.se (valinor [131.115.48.20]) by malmo.trab.se (8.10.1/TRAB-primary-2) with ESMTP id f6O6LfP16917; Tue, 24 Jul 2001 08:21:41 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Tue, 24 Jul 2001 08:20:43 +0200 (MEST) (MET)
Message-Id: <200107240620.IAA05372@valinor.malmo.trab.se>
Date: Tue, 24 Jul 2001 08:20:43 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality    Check)
To: klensin@jck.com
Cc: idn@ops.ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: /8sulNyJIfobq3lZeMlatw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk

John wrote:

>>> 
>>> This is just spreading FUD. No halfway serious online trader
>>> types in the broker address every time he trades. For that,
>>> there are things such as bookmarks and autocompletion.
>> 
>> Also it does not matter if nameprep is not applied at the
>> client end, the DNS server will do nameprep before comparing
>> names - so it will work anyway.

>The above sounds to me as if we are back to requiring that all
>servers need to be upgraded in order to have things work
>properly.  Certainly no DNS server deployed today does nameprep
>before comparing names.  That assumption of massive, more or
>less concurrent, upgrades, or its alternative, that we are
>willing to tolerate a long-ish period in which things don't work
>predictably, are the ones I though the WG concluded it could not
>make.

Only the authorative DNS servers handling non-ASCII names need to
be upgraded. Caching and non-authorative servers can do binary matching.
It will result in those servers seeing each different from of
the same name as different domains, but that does not matter as it will
work anyway.

   Dan




From owner-idn@ops.ietf.org  Tue Jul 24 02:55:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA02620
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 02:55:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OvtC-00095D-00
	for idn-data@psg.com; Mon, 23 Jul 2001 23:41:54 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15OvtB-000957-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 23:41:53 -0700
Received: from valinor.malmo.trab.se (valinor [131.115.48.20]) by malmo.trab.se (8.10.1/TRAB-primary-2) with ESMTP id f6O6e4P18369; Tue, 24 Jul 2001 08:40:04 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Tue, 24 Jul 2001 08:39:06 +0200 (MEST) (MET)
Message-Id: <200107240639.IAA05377@valinor.malmo.trab.se>
Date: Tue, 24 Jul 2001 08:39:06 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: [idn] Debunking the ACE myth
To: idn@ops.ietf.org, amc@cs.berkeley.edu
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: nzuV8YweMELIlqeg0CmEQw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Adam M. Costello wrote:

>> 1) All names are transmitted in a form/semantic insensitive format
>> (that is what nameprep is for) so that names can be compared using
>> binary matching.

>> 1) is the IDNA case and also in Microsofts draft-skwan-utf8-dns.  This
>> results in that for example upper case characters cannot be used in
>> responses from DNS.
>
>For the UTF-8 case, as I've pointed out before, it is not necessary
>for DNS queries and DNS responses to use the same rules.  It would
>be perfectly reasonable to use nameprep'd UTF-8 in queries and
>non-nameprep'd UTF-8 in responses.
>
>For the ACE case, as I've pointed out before, mixed-case ACE can easily
>be used to represent mixed-case Unicode.  You would lose things like
>circled-digit-one (which becomes a regular digit-one), but mixed case
>can be conveyed in ACE.
>
>By the way, it would be pointless to combine ACE with option 2 (no
>nameprep).

1) above is used to allow only binary matching to be done on a DNS server.
This means that the client is required to send nameprepped names to
the server, if they are going to match. If we allow a response to
have non-namprepped names (ACE or UTF-8), only a IDN aware client can
use that name to send new queries because only those will do nameprep
before sending the query. So all other clients may fail when using
a name returned from DNS.

You can allow non-nameprepped answers if you require the DNS server
to do nameprep on names in queries (if needed). For those who
think it is too expensive to do nameprep in the server (it is not for
areas like latin, greek or cyrillic) to have most names in queries
being nameprepped might reduce the burden on the server. That depend
on if a already nameprepped name can quickly be checked.

   Dan




From owner-idn@ops.ietf.org  Tue Jul 24 03:03:06 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA02731
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 03:03:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ow00-0009Kl-00
	for idn-data@psg.com; Mon, 23 Jul 2001 23:48:56 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ovzz-0009Kc-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 23:48:55 -0700
Received: from enoshima (e147244.ppp.asahi-net.or.jp [211.13.147.244])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id PAA07889;
	Tue, 24 Jul 2001 15:48:22 +0900 (JST)
Message-Id: <4.2.0.58.J.20010724154118.0366e6e0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 24 Jul 2001 15:43:49 +0900
To: "Eric A. Hall" <ehall@ehsco.com>, Paul Hoffman / IMC <phoffman@imc.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Debunking the ACE myth
Cc: idn@ops.ietf.org
In-Reply-To: <3B5C6A12.6BDD6AAF@ehsco.com>
References: <200107231126.NAA05269@valinor.malmo.trab.se>
 <p05100317b782111dc570@[165.227.249.20]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 13:16 01/07/23 -0500, Eric A. Hall wrote:

[Paul Hoffman wrote:]

> > Not true. ACE names are quite easy to pick out of document content:
> > they have the name prefixes.
>
>This assumes that it wasn't written and stored in transliterated form. I
>would think that the native format will be the most common for
>user-written material (especially email bodies), not ACE. This goes
>against the original argument.

And please let's not forget: There is at least one form where
if things are going to work, ACE won't be used. That's paper.
If anybody is so stupid to buy an IDN to put its ACE on paper,
s/he can of course do that, but I doubt that's what many
people would want to do.


Regards,   Martin.



From owner-idn@ops.ietf.org  Tue Jul 24 03:03:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA02742
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 03:03:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OvzV-0009K3-00
	for idn-data@psg.com; Mon, 23 Jul 2001 23:48:25 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15OvzU-0009Jx-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 23:48:25 -0700
Received: from enoshima (e147244.ppp.asahi-net.or.jp [211.13.147.244])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id PAA07883;
	Tue, 24 Jul 2001 15:48:20 +0900 (JST)
Message-Id: <4.2.0.58.J.20010724152033.03663240@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 24 Jul 2001 15:36:44 +0900
To: Yves Arrouye <yves@realnames.com>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Clipboard (was: Re: [idn] RE: [idn] Debunking the ACE myth)
In-Reply-To: <B7233BD6980AD411875700508B5BD5D2011E96BC@elporto.internal.
 realnames.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 22:10 01/07/23 -0700, Yves Arrouye wrote:
> > You're going to rely on the dq-- or whatever prefix to find
> > names in free
> > text? Now I like IDNA even less than I did before.
>
>FWIW a lot of MUAs do this today to let you follow a link in plain text
>e-mail. They recognize URIs, even www.*, ftp.*, ..., host names, and turn
>them into links. Nothing new.

Yes, nothing new, and it works well enough to be more of a help than a
nuissance, to a human user who can apply final judgement. But it does
not work well enough to build a protocol on it, such as the 'clipboard
protocol' that is implicitly proposed.

If we really want to go down
that path, I would expect IDNA to contain very exact and explicit
details about how exactly that would work. Currently, clipboards
are covered in a sentence or so; to have any chance
to make this work, at least a page or so may be necessary. Also, please
note that detecting ACE isn't the only thing necessary. We also have
to be able to detect arbitrary IDNs in free text. Assume we have
application A, which is a new application and therefore works
only with UTF-8, throughout, except for the calls to the DNS
(which are most probably done via an UTF-8+nameprep resolver
interface). Now this application gets some free text that contains
some IDN. Some of this free text is then cut or copied into
the clipboard. To adhere to IDNA, the application has to know
which parts of the free text are IDNs. Can it really do that?
If yes, how exactly? Can those who think it should work please
write up a draft?

Also, please think about the following:
How many 'clipboard protocols' has the IETF already defined?
Is the IETF involved in/does it have experience in defining
'clipboard protocols'? Does the IDNA draft require any other
protocol to use ACE for domain names? Does the IDNA draft
describe how any other protocols (except DNS itself) deal
with IDNs?

So one solution may be to just not speak about clipboards
at all.


Regards,    Martin.







From owner-idn@ops.ietf.org  Tue Jul 24 03:05:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA02783
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 03:05:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ow90-0009eP-00
	for idn-data@psg.com; Mon, 23 Jul 2001 23:58:14 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ow8z-0009eJ-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 23:58:13 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15Ow8z-0002P7-00; Mon, 23 Jul 2001 23:58:13 -0700
Date: Tue, 24 Jul 2001 06:58:13 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
Message-ID: <20010724065812.D8846@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200107240639.IAA05377@valinor.malmo.trab.se>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dan Oscarsson <Dan.Oscarsson@trab.se> wrote:

> If we allow a response to have non-namprepped names (ACE or UTF-8),
> only a IDN aware client can use that name to send new queries because
> only those will do nameprep before sending the query. So all other
> clients may fail when using a name returned from DNS.

Non-nameprep'd ACE is pointless, so forget about that.  You're right
that it would be bad to return non-nameprep'd UTF-8 to IDN-unaware
clients, but I think it would be bad to return any non-ASCII names to
IDN-unaware clients.

> For those who think it is too expensive to do nameprep in the server
> (it is not for areas like latin, greek or cyrillic) to have most names
> in queries being nameprepped might reduce the burden on the server.
> That depend on if a already nameprepped name can quickly be checked.

I suspect that the cost of doing nameprep depends on the length of the
string, but not much on its contents.  I doubt that checking whether a
name is nameprep'd is much cheaper than performing nameprep on it.

AMC



From owner-idn@ops.ietf.org  Tue Jul 24 03:23:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA03042
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 03:23:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OwIi-000ALI-00
	for idn-data@psg.com; Tue, 24 Jul 2001 00:08:16 -0700
Received: from drugs.dv.isc.org ([130.155.191.236])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15OwIf-000AL2-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 00:08:14 -0700
Received: from nominum.com (localhost.dv.isc.org [127.0.0.1])
	by drugs.dv.isc.org (8.11.3/8.11.2) with ESMTP id f6O77nu13640;
	Tue, 24 Jul 2001 17:07:50 +1000 (EST)
	(envelope-from marka@nominum.com)
Message-Id: <200107240707.f6O77nu13640@drugs.dv.isc.org>
To: Martin Duerst <duerst@w3.org>
Cc: "Eric A. Hall" <ehall@ehsco.com>, Paul Hoffman / IMC <phoffman@imc.org>,
        idn@ops.ietf.org
From: Mark.Andrews@nominum.com
Subject: Re: [idn] Debunking the ACE myth 
In-reply-to: Your message of "Tue, 24 Jul 2001 15:43:49 +0900."
             <4.2.0.58.J.20010724154118.0366e6e0@sh.w3.mag.keio.ac.jp> 
Date: Tue, 24 Jul 2001 17:07:49 +1000
Sender: owner-idn@ops.ietf.org
Precedence: bulk


> At 13:16 01/07/23 -0500, Eric A. Hall wrote:
> 
> [Paul Hoffman wrote:]
> 
> > > Not true. ACE names are quite easy to pick out of document content:
> > > they have the name prefixes.
> >
> >This assumes that it wasn't written and stored in transliterated form. I
> >would think that the native format will be the most common for
> >user-written material (especially email bodies), not ACE. This goes
> >against the original argument.
> 
> And please let's not forget: There is at least one form where
> if things are going to work, ACE won't be used. That's paper.
> If anybody is so stupid to buy an IDN to put its ACE on paper,
> s/he can of course do that, but I doubt that's what many
> people would want to do.

	Just same way as they don't put the real numbers after
	1 800 SOMENUMBER (1 800 7663686237).  It they want you
	to contact them then the ace form is quite likely to
	be there as well.

	Mark
> 
> 
> Regards,   Martin.
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@nominum.com



From owner-idn@ops.ietf.org  Tue Jul 24 03:23:12 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA03049
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 03:23:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ovyt-0009IA-00
	for idn-data@psg.com; Mon, 23 Jul 2001 23:47:47 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ovys-0009I4-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 23:47:46 -0700
Received: from valinor.malmo.trab.se (valinor [131.115.48.20]) by malmo.trab.se (8.10.1/TRAB-primary-2) with ESMTP id f6O6joP19158; Tue, 24 Jul 2001 08:45:50 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Tue, 24 Jul 2001 08:44:52 +0200 (MEST) (MET)
Message-Id: <200107240644.IAA05382@valinor.malmo.trab.se>
Date: Tue, 24 Jul 2001 08:44:52 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: [idn] Debunking the ACE myth
To: idn@ops.ietf.org, david.hopwood@zetnet.co.uk
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: BiixSFgeraCwtYZj5XP+tQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk

David Hopwood wrote:

>Dan Oscarsson wrote:
>> 1) [names on the wire are always canonicalised]
>>    is the IDNA case and also in Microsofts draft-skwan-utf8-dns.
>>    This results in that for example upper case characters cannot be
>>    used in responses from DNS. Probably very irritating some people
>>    who have spent a lot of mony on their nice company name which uses
>>    mixed case and will break some programs expecting mixed case
>>    in PTR responses.
>
>What programs will break in this case? That doesn't sound remotely
>plausible to me. If it turns out to be difficult to support case
>preservation then that would be the first thing I'd discard: other
>properties are far more important.

Many programs still do case exact matching on host names despite
that DNS have had case insensitive matching from the start. I have seen
Unixprograms fail due to people prefering host names with the first
letter in upper case and have had to use exactely the same case in
my configuration files as in the DNS answers.


But yes, if we want we could require all results to be in the
nameprepped state (including ASCII only names) and add a new RR in
answers to supply the "true" from of the name where needed (for example
in PTR answers).

   Dan




From owner-idn@ops.ietf.org  Tue Jul 24 03:23:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA03063
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 03:23:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OwD8-0009we-00
	for idn-data@psg.com; Tue, 24 Jul 2001 00:02:30 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.31 #1)
	id 15OwD7-0009wV-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 00:02:29 -0700
Received: (qmail 16601 invoked from network); 24 Jul 2001 14:21:19 -0000
Received: from chubby.internal.realnames.com (HELO heaven.internal.realnames.com) (10.1.5.39)
  by friendly.realnames.com with SMTP; 24 Jul 2001 14:21:19 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:2507]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <130144@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Tue, 24 Jul 2001 12:00:51 AM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2650.21)
	id <PJWHMQJ9>; Tue, 24 Jul 2001 00:02:17 -0700
Message-ID: <B7233BD6980AD411875700508B5BD5D2011E96CC@elporto.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: idn@ops.ietf.org
Subject: RE: Clipboard (was: Re: [idn] RE: [idn] Debunking the ACE myth)
Date: Tue, 24 Jul 2001 00:02:15 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > > You're going to rely on the dq-- or whatever prefix to find
> > > names in free
> > > text? Now I like IDNA even less than I did before.
> >
> >FWIW a lot of MUAs do this today to let you follow a link in 
> plain text
> >e-mail. They recognize URIs, even www.*, ftp.*, ..., host 
> names, and turn
> >them into links. Nothing new.
> 
> Yes, nothing new, and it works well enough to be more of a help than a
> nuissance, to a human user who can apply final judgement. But it does
> not work well enough to build a protocol on it, such as the 'clipboard
> protocol' that is implicitly proposed.

No doubt about that. Nor is it going to help when one really wants to
discuss the details of an ACE encoding on e-mail and write dq--whatever only
to see it turned into an internationalized string. Some frustration
guaranteed. I was only pointing out that looking for text in free text is
not hard ;)

YA



From owner-idn@ops.ietf.org  Tue Jul 24 03:23:15 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA03069
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 03:23:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OwBE-0009m2-00
	for idn-data@psg.com; Tue, 24 Jul 2001 00:00:32 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15OwBD-0009lt-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 00:00:32 -0700
Received: from valinor.malmo.trab.se (valinor [131.115.48.20]) by malmo.trab.se (8.10.1/TRAB-primary-2) with ESMTP id f6O6wiP19597 for <idn@ops.ietf.org>; Tue, 24 Jul 2001 08:58:44 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Tue, 24 Jul 2001 08:57:47 +0200 (MEST) (MET)
Message-Id: <200107240657.IAA05387@valinor.malmo.trab.se>
Date: Tue, 24 Jul 2001 08:57:47 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality    Check)
To: idn@ops.ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: qQ1VRosE88UkNoYSxImNTw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Paul Hoffman wrote:

>
>Dan, it is not clear from the udns-02 document that the protocol 
>requires nameprep on the name server for every query. This is a 
>fairly important design choice of UDNS that should probably be 
>highlighted in the document. As you have seen, some people who 
>thought they were supporting udns-02 don't think this is such a great 
>idea, and it is quite controversial for name servers that run high 
>volumes of queries (like tens of thousands a second).

It would be interesting if somebody have some real data to show
if it really is that CPU heavy.
In UDNS all character data is required to be normalised.
Because of this a lot of the form insensitive matching that nameprep
represents can be done "on the fly" just like the case insensitive
matching of ASCII that is done today.

If we want to compare what things are expensive (take a lot of CPU
or memory) we should try to get data on several things. For example:
- UTF-8 (UCS) to/from ACE
- normalisation of a text (Unicode from C or KC)
- full nameprep (with both normalisation and form folding)
- just form folding
- optimised name matching where the input strings are normalised
  strings and the form insensitive matching according to nameprep
  is done in most efficient manner.

I am sure there are more things that we need data to decide how
things best should be done.

    Dan




From owner-idn@ops.ietf.org  Tue Jul 24 03:23:15 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA03080
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 03:23:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OwAL-0009j1-00
	for idn-data@psg.com; Mon, 23 Jul 2001 23:59:37 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15OwAL-0009ip-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 23:59:37 -0700
Received: from enoshima (e147244.ppp.asahi-net.or.jp [211.13.147.244])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id PAA07886;
	Tue, 24 Jul 2001 15:48:21 +0900 (JST)
Message-Id: <4.2.0.58.J.20010724153735.03554340@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 24 Jul 2001 15:40:01 +0900
To: Dan Oscarsson <Dan.Oscarsson@trab.se>, klensin@jck.com
From: Martin Duerst <duerst@w3.org>
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality   
  Check)
Cc: idn@ops.ietf.org
In-Reply-To: <200107240620.IAA05372@valinor.malmo.trab.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 08:20 01/07/24 +0200, Dan Oscarsson wrote:
>Only the authorative DNS servers handling non-ASCII names need to
>be upgraded. Caching and non-authorative servers can do binary matching.
>It will result in those servers seeing each different from of
>the same name as different domains, but that does not matter as it will
>work anyway.

Doing nameprep during operation on the server side is still a bad idea.
If we really need the original spelling of the name (which I'm not sure
we do), a new RR may be quite a bit better.

Regards,  Martin.



From owner-idn@ops.ietf.org  Tue Jul 24 03:23:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA03089
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 03:23:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ow95-0009ea-00
	for idn-data@psg.com; Mon, 23 Jul 2001 23:58:19 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ow94-0009eS-00
	for idn@ops.ietf.org; Mon, 23 Jul 2001 23:58:18 -0700
Received: from zetnet.co.uk (man-s170.dialup.zetnet.co.uk [194.247.45.41])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6O6wD607968;
	Tue, 24 Jul 2001 07:58:13 +0100
Message-ID: <3B5D1ADD.C61C752D@zetnet.co.uk>
Date: Tue, 24 Jul 2001 07:51:09 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: Yves Arrouye <yves@realnames.com>, idn@ops.ietf.org
Subject: Re: [idn] RE: [idn] Debunking the ACE myth
References: <B7233BD6980AD411875700508B5BD5D2011E96BC@elporto.internal.realnames.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

Yves Arrouye wrote:
> David Hopwood wrote:
> > You're going to rely on the dq-- or whatever prefix to find
> > names in free text? Now I like IDNA even less than I did before.
> 
> FWIW a lot of MUAs do this today to let you follow a link in plain text
> e-mail. They recognize URIs, even www.*, ftp.*, ..., host names, and turn
> them into links. Nothing new.

Yes, and they frequently get it wrong. However, the appearance of the text
doesn't change apart from being underlined, so you can see when the client
has got it wrong (and compensate by cutting and pasting instead).
In IDNA, the client would be trying to decode ACE and redisplay it as
Unicode.

Also, URIs are only recognised now in some situations, certainly not all
those in which an ACE name could appear in a proposal like IDNA.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO10aqDkCAxeYt5gVAQFXeggAu/soGaUdoe3zS5m2yTyiuUPEWCxR3USW
TrUMlYG2cMOozMi/FQR6G2DRiseZLoMbz7iygF2h1zzVkF60NI3TJv4JiZlR8ZXi
CvMhxmN5EgLgIT1cNj2j9ZbA+vzlbNB6zQ4ruwl27aqaKCHoGpOaH+7CTM1uUJMH
cKOEKN3DkFHb4jTmIHaRWn01k0r2JXm6f89wgehoKwtjz6UIjIA+cFN4pL1F4pUK
5pjM3woPKrmeCi4FmqqVUuwqY95OIC53AOH9EQqYbeJ7zrc7VonijSNQCIebp2UK
J873cdFF2JpQrar5EMWVH+NzUczGxyTQ1lvk6GTSeKWOPcn769n7aA==
=ksXK
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Tue Jul 24 04:40:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA04033
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 04:40:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ox9K-000C3t-00
	for idn-data@psg.com; Tue, 24 Jul 2001 01:02:38 -0700
From: =?iso-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
To: Martin Duerst <duerst@w3.org>
Cc: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15Ox9K-000C3t-00@psg.com>
Date: Tue, 24 Jul 2001 01:02:38 -0700

Subject: Re: [idn] Debunking the ACE myth Date: Tue, Jul 24, 2001 at
03:43:49PM +0900 Quoting Martin Duerst (duerst@w3.org):
>
> And please let's not forget: There is at least one form where
> if things are going to work, ACE won't be used. That's paper.
> If anybody is so stupid to buy an IDN to put its ACE on paper,
> s/he can of course do that, but I doubt that's what many
> people would want to do.
>

You forget the legal hassle that would arise if a TLD Registry
forgot to tell people what their ACE-encoded string is. Or the
support hell that arises -- think angry customer who screams "I
wanted "räksmörgås", not this bq-- blaha!!". I see a strong need
for registries to print out the ACE encoded form in all kinds of
correspondance with their domain name holders -- provided that ACE
is chosen.

--
Måns Nilsson MN1334-RIPE
http://vvv.besserwisser.org


How do you explain Wayne Newton's POWER over millions?  It's th'
MOUSTACHE ...  Have you ever noticed th' way it radiates SINCERITY,
HONESTY & WARMTH?  It's a MOUSTACHE you want to take HOME and introduce
to NANCY SINATRA!





From owner-idn@ops.ietf.org  Tue Jul 24 05:21:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA04667
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 05:21:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Oy8J-000DxX-00
	for idn-data@psg.com; Tue, 24 Jul 2001 02:05:39 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Oy8J-000DxO-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 02:05:39 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id LAA22418;
	Tue, 24 Jul 2001 11:05:16 +0200 (MET DST)
Date: Tue, 24 Jul 2001 10:48:36 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Martin Duerst <duerst@w3.org>, "Eric A. Hall" <ehall@ehsco.com>,
        "Paul Hoffman / IMC" <phoffman@imc.org>
cc: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
Message-ID: <5074730.995971716@localhost>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA04667

--On 01-07-24 15.43 +0900 Martin Duerst <duerst@w3.org> wrote:

> If anybody is so stupid to buy an IDN to put its ACE on paper,
> s/he can of course do that, but I doubt that's what many
> people would want to do.

I would ABSOLUTELY do it on my buissness card as an alternative form of my
email as I know that people in many countries don't know how to enter 'ä'
(adiaeresis) on their keyboard, and I want people to be able to create an
email and send it to me.

And, I would appreciate getting an ACE version of a japanese domainname
because even though I can enter japanese characters on my Mac, I don't know
the input system well enough (or japanese characters enough to say whether
I have entered the correct name or not).

Now kill me on this list if you want to...

   paf




From owner-idn@ops.ietf.org  Tue Jul 24 05:21:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA04673
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 05:21:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OxzC-000DgC-00
	for idn-data@psg.com; Tue, 24 Jul 2001 01:56:14 -0700
Received: from [209.187.148.217] (helo=P2)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15OxzB-000DeY-00; Tue, 24 Jul 2001 01:56:13 -0700
Date: Tue, 24 Jul 2001 04:55:55 -0400
From: John C Klensin <klensin@jck.com>
To: Martin Duerst <duerst@w3.org>, Dan Oscarsson <Dan.Oscarsson@trab.se>
cc: idn@ops.ietf.org
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn]
 Reality    Check)
Message-ID: <127591451.995950555@localhost>
In-Reply-To: <4.2.0.58.J.20010724153735.03554340@sh.w3.mag.keio.ac.jp>
References:  <4.2.0.58.J.20010724153735.03554340@sh.w3.mag.keio.ac
 .jp>
X-Mailer: Mulberry/2.1.0b2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On Tuesday, 24 July, 2001 15:40 +0900 Martin Duerst
<duerst@w3.org> wrote:

> Doing nameprep during operation on the server side is still a
> bad idea. If we really need the original spelling of the name
> (which I'm not sure we do), a new RR may be quite a bit better.

Martin,

It was trying to think through an approach based on a new RR
that brought me to the conclusion that, if one went down that
path, a whole new class would be needed.   Please work the cases
yourself, remembering the various issues raised by CNAME, MX,
and PTR RRs that might or might not have IDN values (targets)
and see if you come to the same conclusion.

    john




From owner-idn@ops.ietf.org  Tue Jul 24 05:33:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA04856
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 05:33:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OyBq-000E5g-00
	for idn-data@psg.com; Tue, 24 Jul 2001 02:09:18 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15OyBq-000E5Y-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 02:09:18 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id LAA22429;
	Tue, 24 Jul 2001 11:05:19 +0200 (MET DST)
Date: Tue, 24 Jul 2001 10:54:36 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Dan Oscarsson <Dan.Oscarsson@trab.se>, idn@ops.ietf.org
cc: Rob Austein <sra@hactrn.net>
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality    Check)
Message-ID: <5096309.995972076@localhost>
In-Reply-To: <200107240657.IAA05387@valinor.malmo.trab.se>
References:  <200107240657.IAA05387@valinor.malmo.trab.se>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-07-24 08.57 +0200 Dan Oscarsson <Dan.Oscarsson@trab.se> wrote:

> It would be interesting if somebody have some real data to show
> if it really is that CPU heavy.

We have problems today with DNS as it is without DNSSEC, A6, DNAME, etc etc
and as I said before, I really want changes to the way DNS works today to
be handled in the DNSOP and DNSEXT wg's and not this.

Regarding only doing nameprep in the authoritative servers, that is
definitly not enough. That means that you might get a query after owner A,
which nameprepped is B, and because of this, one send a query for owner A,
but get B as a response.

I really want DNS servers to reject those kind of responses (where the
owner in the response doesn't match the owner in the query), and I hope
they do check this today, or we would have cache poisoning all over the
place.

I.e. doing nameprep only in authoritative servers is firstly a security
issue and secondly a performance issue.

But, most importantly, I don't find this group being the one which can even
think about DNS complexity.

  paf




From owner-idn@ops.ietf.org  Tue Jul 24 07:24:02 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA09265
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 07:24:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15OzUK-000GlA-00
	for idn-data@psg.com; Tue, 24 Jul 2001 03:32:28 -0700
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15OzUJ-000Gl4-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 03:32:27 -0700
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06327;
	Tue, 24 Jul 2001 06:31:28 -0400 (EDT)
Message-Id: <200107241031.GAA06327@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: idn@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [idn] I-D ACTION:draft-ietf-idn-nameprep-05.txt
Date: Tue, 24 Jul 2001 06:31:27 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internationalized Domain Name Working Group of the IETF.

	Title		: Preparation of Internationalized Host Names
	Author(s)	: P. Hoffman, M. Blanchet
	Filename	: draft-ietf-idn-nameprep-05.txt
	Pages		: 
	Date		: 23-Jul-01
	
This document describes how to prepare internationalized host names for
use in the DNS. The steps include:
- mapping characters to other characters, such as to change their case
- normalizing the characters
- excluding characters that are prohibited from appearing in
internationalized host names
This document does not specify a wire protocol. This preparation should
be done before the DNS request.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idn-nameprep-05.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-idn-nameprep-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-idn-nameprep-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010723140748.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idn-nameprep-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idn-nameprep-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010723140748.I-D@ietf.org>

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Tue Jul 24 08:57:02 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA14829
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 08:57:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15P1BL-000Kjt-00
	for idn-data@psg.com; Tue, 24 Jul 2001 05:20:59 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15P1BJ-000Kjg-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 05:20:57 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id IAA09124;
        Tue, 24 Jul 2001 08:20:51 -0400 (EDT)
Message-Id: <200107241220.IAA09124@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Mark.Andrews@nominum.com
cc: Martin Duerst <duerst@w3.org>, "Eric A. Hall" <ehall@ehsco.com>,
        Paul Hoffman / IMC <phoffman@imc.org>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth 
In-reply-to: Your message of "Tue, 24 Jul 2001 17:07:49 +1000."
             <200107240707.f6O77nu13640@drugs.dv.isc.org> 
Date: Tue, 24 Jul 2001 08:20:51 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

        Just same way as they don't put the real numbers after
        1 800 SOMENUMBER (1 800 7663686237).  It they want you
        to contact them then the ace form is quite likely to
        be there as well.

nobody is going to expect people to type in an ACE name.
if they want to be reached by anybody who doesn't speak the
native dialect, or who doesn't have IDN support, they're 
going to have an ASCII DNS name, at least as an alternative
to the IDN.




From owner-idn@ops.ietf.org  Tue Jul 24 09:46:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA17525
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 09:46:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15P22W-000MsL-00
	for idn-data@psg.com; Tue, 24 Jul 2001 06:15:56 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15P22V-000MsC-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 06:15:55 -0700
Received: from CLASSIC.viagenie.qc.ca (modemcable245.48-201-24.que.mc.videotron.ca [24.201.48.245])
	by jazz.viagenie.qc.ca (Viagenie/8.11.0) with ESMTP id f6ODbE176714;
	Tue, 24 Jul 2001 09:37:14 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010724091314.03ff6a40@mail.viagenie.qc.ca>
X-Sender: blanchet@mail.viagenie.qc.ca
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 24 Jul 2001 09:17:47 -0400
To: Keith Moore <moore@cs.utk.edu>, Mark.Andrews@nominum.com
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: ace leaking (was: Re: [idn] Debunking the ACE myth)
Cc: idn@ops.ietf.org
In-Reply-To: <200107241220.IAA09124@astro.cs.utk.edu>
References: <Your message of "Tue, 24 Jul 2001 17:07:49 +1000." <200107240707.f6O77nu13640@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

At/À 08:20 2001-07-24 -0400, Keith Moore you wrote/vous écriviez:
>         Just same way as they don't put the real numbers after
>         1 800 SOMENUMBER (1 800 7663686237).  It they want you
>         to contact them then the ace form is quite likely to
>         be there as well.
>
>nobody is going to expect people to type in an ACE name.
>if they want to be reached by anybody who doesn't speak the
>native dialect, or who doesn't have IDN support, they're
>going to have an ASCII DNS name, at least as an alternative
>to the IDN.

I agree with your point, but not the way you wrote it. It is more than 
possible than the user shown choices would be:
- an ascii domain name as today
- the idn represented with the right script (not shown in ace).

but, as many were saying since more than 2 years now, the ace encoding will 
leak in many places.

So I would say that people will try to avoid it, but in the run, we will 
expose it, which is bad.

ace has good advantages, but also drawbacks. we don't live in a perfect world.
Just has to find the least pain...
(and the least pain is not yet a concensus in this wg...).

Marc.






From owner-idn@ops.ietf.org  Tue Jul 24 10:16:21 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA19435
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 10:16:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15P2E3-000NSJ-00
	for idn-data@psg.com; Tue, 24 Jul 2001 06:27:51 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15P2E2-000NSB-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 06:27:50 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA09700;
        Tue, 24 Jul 2001 09:27:45 -0400 (EDT)
Message-Id: <200107241327.JAA09700@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
cc: Keith Moore <moore@cs.utk.edu>, Mark.Andrews@nominum.com, idn@ops.ietf.org
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth) 
In-reply-to: Your message of "Tue, 24 Jul 2001 09:17:47 EDT."
             <5.1.0.14.1.20010724091314.03ff6a40@mail.viagenie.qc.ca> 
Date: Tue, 24 Jul 2001 09:27:45 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> At/À 08:20 2001-07-24 -0400, Keith Moore you wrote/vous écriviez:
> >         Just same way as they don't put the real numbers after
> >         1 800 SOMENUMBER (1 800 7663686237).  It they want you
> >         to contact them then the ace form is quite likely to
> >         be there as well.
> >
> >nobody is going to expect people to type in an ACE name.
> >if they want to be reached by anybody who doesn't speak the
> >native dialect, or who doesn't have IDN support, they're
> >going to have an ASCII DNS name, at least as an alternative
> >to the IDN.
> 
> I agree with your point, but not the way you wrote it. It is more than
> possible than the user shown choices would be:
> - an ascii domain name as today
> - the idn represented with the right script (not shown in ace).
> 
> but, as many were saying since more than 2 years now, the ace encoding will
> leak in many places.

right.  I was talking about deliberate exposure of an ACE, not accidental
exposure of an ACE.  I don't think that many people will deliberately 
show people ACE names (say on a business card) and expect people to
type them in.  They'll either show the native form of the name, or they'll
show an ASCII DNS name, or both.

Keith



From owner-idn@ops.ietf.org  Tue Jul 24 11:59:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA26925
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 11:59:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15P47A-0002i8-00
	for idn-data@psg.com; Tue, 24 Jul 2001 08:28:52 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15P479-0002i1-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 08:28:51 -0700
Received: from [24.252.219.84] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.8)
  with ESMTP-TLS id 190731; Mon, 23 Jul 2001 10:28:06 -0500
Message-ID: <3B5D942A.6A120DB6@ehsco.com>
Date: Tue, 24 Jul 2001 10:28:43 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dan Oscarsson <Dan.Oscarsson@trab.se>
CC: idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <200107240639.IAA05377@valinor.malmo.trab.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> think it is too expensive to do nameprep in the server (it is not for
> areas like latin, greek or cyrillic) to have most names in queries
> being nameprepped might reduce the burden on the server. That depend
> on if a already nameprepped name can quickly be checked.

One solution is to have the authoritative servers nameprep on load, such
that they check when they read the database, A/IXFR, DDNS update, etc.

We should also separate the reasons for having nameprep in two places, and
why they are both needed.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Tue Jul 24 11:59:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA26943
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 11:59:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15P4NT-0003J0-00
	for idn-data@psg.com; Tue, 24 Jul 2001 08:45:43 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15P4NS-0003I3-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 08:45:42 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id RAA05510;
	Tue, 24 Jul 2001 17:44:17 +0200 (MET DST)
Date: Tue, 24 Jul 2001 17:39:31 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Keith Moore <moore@cs.utk.edu>,
        Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
cc: Keith Moore <moore@cs.utk.edu>, Mark.Andrews@nominum.com, idn@ops.ietf.org
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth) 
Message-ID: <5468535.995996371@localhost>
In-Reply-To: <200107241327.JAA09700@astro.cs.utk.edu>
References:  <200107241327.JAA09700@astro.cs.utk.edu>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-07-24 09.27 -0400 Keith Moore <moore@cs.utk.edu> wrote:

> right.  I was talking about deliberate exposure of an ACE, not accidental
> exposure of an ACE.  I don't think that many people will deliberately 
> show people ACE names (say on a business card) and expect people to
> type them in.  They'll either show the native form of the name, or they'll
> show an ASCII DNS name, or both.

Just to continue this discussion in absurdum:

I don't want to be forced to register more than one domainname. Why should
I register something in US-ASCII only when we have IDN? I am not interested
in paying some registry and ISP for hosting an extra domain just because
some people can not type in adiaeresis. I rather expose the ACE and let
people fight with it (ugly as it is).

   paf




From owner-idn@ops.ietf.org  Tue Jul 24 12:43:21 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA00602
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 12:43:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15P4lz-00047E-00
	for idn-data@psg.com; Tue, 24 Jul 2001 09:11:03 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15P4ly-00046c-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 09:11:03 -0700
Received: from CLASSIC.viagenie.qc.ca (modemcable245.48-201-24.que.mc.videotron.ca [24.201.48.245])
	by jazz.viagenie.qc.ca (Viagenie/8.11.0) with ESMTP id f6OGWK179504;
	Tue, 24 Jul 2001 12:32:20 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010724120919.0216e138@mail.viagenie.qc.ca>
X-Sender: blanchet@mail.viagenie.qc.ca
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 24 Jul 2001 12:10:30 -0400
To: Patrik Fältström <paf@cisco.com>, Keith Moore <moore@cs.utk.edu>
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth) 
Cc: Keith Moore <moore@cs.utk.edu>, Mark.Andrews@nominum.com, idn@ops.ietf.org
In-Reply-To: <5468535.995996371@localhost>
References: <200107241327.JAA09700@astro.cs.utk.edu>
 <200107241327.JAA09700@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

At/À 17:39 2001-07-24 +0200, Patrik Fältström you wrote/vous écriviez:
>--On 01-07-24 09.27 -0400 Keith Moore <moore@cs.utk.edu> wrote:
>
> > right.  I was talking about deliberate exposure of an ACE, not accidental
> > exposure of an ACE.  I don't think that many people will deliberately
> > show people ACE names (say on a business card) and expect people to
> > type them in.  They'll either show the native form of the name, or they'll
> > show an ASCII DNS name, or both.
>
>Just to continue this discussion in absurdum:
>
>I don't want to be forced to register more than one domainname. Why should
>I register something in US-ASCII only when we have IDN? I am not interested
>in paying some registry and ISP for hosting an extra domain just because
>some people can not type in adiaeresis. I rather expose the ACE and let
>people fight with it (ugly as it is).

a per-user choice.
I would guess the opposite (i.e. two domain names: one pure ascii and one 
full-idn (without showing the ace equivalent) ,
but who knows the future...

Marc.


>    paf





From owner-idn@ops.ietf.org  Tue Jul 24 13:07:06 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA02657
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 13:07:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15P5Id-00052X-00
	for idn-data@psg.com; Tue, 24 Jul 2001 09:44:47 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15P5Ic-00052R-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 09:44:46 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id MAA10770;
        Tue, 24 Jul 2001 12:44:38 -0400 (EDT)
Message-Id: <200107241644.MAA10770@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
cc: Keith Moore <moore@cs.utk.edu>,
        Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>, Mark.Andrews@nominum.com,
        idn@ops.ietf.org
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth) 
In-reply-to: Your message of "Tue, 24 Jul 2001 17:39:31 +0200."
             <5468535.995996371@localhost> 
Date: Tue, 24 Jul 2001 12:44:38 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > right.  I was talking about deliberate exposure of an ACE, not accidental
> > exposure of an ACE.  I don't think that many people will deliberately
> > show people ACE names (say on a business card) and expect people to
> > type them in.  They'll either show the native form of the name, or they'll
> > show an ASCII DNS name, or both.
> 
> Just to continue this discussion in absurdum:
> 
> I don't want to be forced to register more than one domainname. Why should
> I register something in US-ASCII only when we have IDN? I am not interested
> in paying some registry and ISP for hosting an extra domain just because
> some people can not type in adiaeresis. I rather expose the ACE and let
> people fight with it (ugly as it is).

it's your choice, of course.  my guess is that most folks will choose the
opposite (if they want to be reachable by non-natives)

Keith



From owner-idn@ops.ietf.org  Tue Jul 24 14:12:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA08119
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 14:12:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15P69W-0006jp-00
	for idn-data@psg.com; Tue, 24 Jul 2001 10:39:26 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.31 #1)
	id 15P69V-0006jd-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 10:39:26 -0700
Received: (qmail 28474 invoked from network); 25 Jul 2001 00:57:30 -0000
Received: from chubby.internal.realnames.com (HELO heaven.internal.realnames.com) (10.1.5.39)
  by friendly.realnames.com with SMTP; 25 Jul 2001 00:57:30 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:4383]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <146489@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Tue, 24 Jul 2001 10:36:35 AM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2650.21)
	id <PJWHNDB9>; Tue, 24 Jul 2001 10:38:02 -0700
Message-ID: <B7233BD6980AD411875700508B5BD5D2011E96D5@elporto.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: idn@ops.ietf.org
Subject: RE: [idn] I-D ACTION:draft-ietf-idn-nameprep-05.txt
Date: Tue, 24 Jul 2001 10:38:01 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> A URL for this Internet-Draft is: 
> http://www.ietf.org/internet-drafts/draft-ietf-idn-nameprep-05
.txt

Still no feedback from this I.D.'s editor on the suggestions Adam and I made
for the handling of  common input mechanisms behaviors. Do they not make
sense?

YA



From owner-idn@ops.ietf.org  Tue Jul 24 14:25:23 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA09068
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 14:25:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15P69P-0006jT-00
	for idn-data@psg.com; Tue, 24 Jul 2001 10:39:19 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15P69N-0006jN-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 10:39:18 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA11407;
        Tue, 24 Jul 2001 13:38:24 -0400 (EDT)
Message-Id: <200107241738.NAA11407@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: liana.ydisg@juno.com
cc: paf@cisco.com, moore@cs.utk.edu, Marc.Blanchet@viagenie.qc.ca,
        Mark.Andrews@nominum.com, idn@ops.ietf.org
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth) 
In-reply-to: Your message of "Tue, 24 Jul 2001 10:49:02 PDT."
             <20010724.104905.-819277.0.liana.ydisg@juno.com> 
Date: Tue, 24 Jul 2001 13:38:24 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

why should you bother keeping two sites, when two domains that refer
to the same address will suffice?

maybe because it will get you more customers/viewers?

again, it's your choice.

> I agree.  Why should I keep two different sites, when I have a lot
> of other things to take care of? 



From owner-idn@ops.ietf.org  Tue Jul 24 15:08:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA12288
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 15:08:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15P6x1-0008Qb-00
	for idn-data@psg.com; Tue, 24 Jul 2001 11:30:35 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15P6x0-0008QV-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 11:30:34 -0700
Received: from [64.1.5.87] (ip20.proper.com [165.227.249.20])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f6OIUTG03117;
	Tue, 24 Jul 2001 11:30:29 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100319b7836e2ccf33@[64.1.5.87]>
In-Reply-To: <5.1.0.14.1.20010724120919.0216e138@mail.viagenie.qc.ca>
References: <200107241327.JAA09700@astro.cs.utk.edu>
 <200107241327.JAA09700@astro.cs.utk.edu>
 <5.1.0.14.1.20010724120919.0216e138@mail.viagenie.qc.ca>
Date: Tue, 24 Jul 2001 11:29:04 -0700
To: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>, idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth)
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 12:10 PM -0400 7/24/01, Marc Blanchet wrote:
>I would guess the opposite (i.e. two domain names: one pure ascii 
>and one full-idn (without showing the ace equivalent) ,
>but who knows the future...

That's easy for someone whose company name makes reasonable sense in 
pure ASCII to say. Telling Chinese and Indian speakers that they must 
register a domain name in pure ASCII is quite different. Romanization 
works poorly for many languages; few Americans and Europeans realize 
that.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Tue Jul 24 15:25:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA13452
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 15:25:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15P7UP-0009cN-00
	for idn-data@psg.com; Tue, 24 Jul 2001 12:05:05 -0700
Received: from r1.boston.juno.com ([64.136.24.45])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15P7UO-0009bs-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 12:05:04 -0700
Received: from m2.boston.juno.com (m2.boston.juno.com [64.136.24.65])
 by r1.boston.juno.com (8.8.6.Beta0/8.8.7/juno-1.2) with ESMTP id NAAAA05947
 for <idn@ops.ietf.org>; Tue, 24 Jul 2001 13:40:01 -0400 (EDT)
From: liana.ydisg@juno.com
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH8mrHnsaLWiw3qMM2fw4d7H5nwD9BxFgUw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GA5NUZLM; Tue, 24 Jul 2001 13:33:16 EDT
To: paf@cisco.com
Cc: moore@cs.utk.edu, Marc.Blanchet@viagenie.qc.ca, Mark.Andrews@nominum.com,
        idn@ops.ietf.org
Date: Tue, 24 Jul 2001 10:49:02 -0700
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth)
Message-ID: <20010724.104905.-819277.0.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.11
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-7,9-36
X-Juno-Att: 0
X-Juno-RefParts: 0
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I agree.  Why should I keep two different sites, when I have a lot
of other things to take care of?   Unless I want two different sites
to separate the respondends.  In that case, I prefer to register two
sites.  I would not want an IDN, it may be one or two sites.

Liana


On Tue, 24 Jul 2001 17:39:31 +0200 =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?=
<paf@cisco.com> writes:
> --On 01-07-24 09.27 -0400 Keith Moore <moore@cs.utk.edu> wrote:
> 
> > right.  I was talking about deliberate exposure of an ACE, not 
> accidental
> > exposure of an ACE.  I don't think that many people will 
> deliberately 
> > show people ACE names (say on a business card) and expect people 
> to
> > type them in.  They'll either show the native form of the name, or 
> they'll
> > show an ASCII DNS name, or both.
> 
> Just to continue this discussion in absurdum:
> 
> I don't want to be forced to register more than one domainname. Why 
> should
> I register something in US-ASCII only when we have IDN? I am not 
> interested
> in paying some registry and ISP for hosting an extra domain just 
> because
> some people can not type in adiaeresis. I rather expose the ACE and 
> let
> people fight with it (ugly as it is).
> 
>    paf
> 
> 



From owner-idn@ops.ietf.org  Tue Jul 24 15:31:25 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA13922
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 15:31:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15P7Sj-0009Y9-00
	for idn-data@psg.com; Tue, 24 Jul 2001 12:03:21 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15P7Si-0009Y1-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 12:03:20 -0700
Received: from zetnet.co.uk (man-s239.dialup.zetnet.co.uk [194.247.45.110])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6OJ2wp22036;
	Tue, 24 Jul 2001 20:02:59 +0100
Message-ID: <3B5DC4AA.AA422763@zetnet.co.uk>
Date: Tue, 24 Jul 2001 19:55:38 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] Debunking the ACE myth
References: <20010724065812.D8846@arwen.cs.berkeley.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

"Adam M. Costello" wrote:
> I doubt that checking whether a name is nameprep'd is much cheaper than
> performing nameprep on it.

It is, actually: see UAX #15 Annexes 3 and 8, at
http://www.unicode.org/unicode/reports/tr15/

(The code in Annex 8 would need to be modified to also check for lowercase.
It also has to be checked that the name is a valid UTF-8 encoding.)

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO13EkzkCAxeYt5gVAQFJSwf+OaFXUPMfQ4i1hK170/3IzyEToUoQelA+
BYabTEjp3WnzRI9H0eaaFyvQd7qJv626A118KJljaKdSIx+ISZTkBRy3w6JcjVxv
ZOD4EJ0oULbheXTHmeCjuh4ncG4iOCFTGH5soIlmzjmzAv+grk8NE2nJfpNkNQ4s
6JgC3Z1lwN0sidpwQ0lmTMR2H+iQtjDPaSO8oXklwwJyV2/X2Sg9EJJlKzoB0iSZ
3j1YQu3UwKuFoTAT+hCd93c+quYhCaU1b/sVbAznlKVKLRLwzkzH7whxpk5k4vl+
xVusEMGLnb4qQwHTmLkgTuaSklNY5u88ktFP4UlJv2sDEYijCgOwcw==
=sf0m
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Tue Jul 24 15:31:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA13932
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 15:31:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15P7e8-0009yc-00
	for idn-data@psg.com; Tue, 24 Jul 2001 12:15:08 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15P7e7-0009yO-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 12:15:07 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA12103;
        Tue, 24 Jul 2001 15:15:04 -0400 (EDT)
Message-Id: <200107241915.PAA12103@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Paul Hoffman / IMC <phoffman@imc.org>
cc: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>, idn@ops.ietf.org
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth) 
In-reply-to: Your message of "Tue, 24 Jul 2001 11:29:04 PDT."
             <p05100319b7836e2ccf33@[64.1.5.87]> 
Date: Tue, 24 Jul 2001 15:15:04 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> That's easy for someone whose company name makes reasonable sense in
> pure ASCII to say. Telling Chinese and Indian speakers that they must
> register a domain name in pure ASCII is quite different. 

nobody has suggested that this be done.

in general, an organization that has an IDN in one language or script
might find it useful to have other IDNs in other langauges or scripts -
so that it can be reached by more people.  Having a pure-ASCII IDN
as one of those alternate IDNs is just a special case of this - one 
that I expect will be fairly common.



From owner-idn@ops.ietf.org  Tue Jul 24 16:42:27 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA20664
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 16:42:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15P8b3-000BuR-00
	for idn-data@psg.com; Tue, 24 Jul 2001 13:16:01 -0700
Received: from mail07b.vwh1.net ([209.238.9.59])
	by psg.com with smtp (Exim 3.31 #1)
	id 15P8b2-000BuL-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 13:16:00 -0700
Received: from www.langoo.net (208.55.128.123)
	by mail07b.vwh1.net (RS ver 1.0.60s) with SMTP id 020529946;
	Tue, 24 Jul 2001 16:15:45 -0400 (EDT)
From: "Deven Kalra" <kalra@langoo.net>
To: "Paul Hoffman / IMC" <phoffman@imc.org>,
        "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>, <idn@ops.ietf.org>
Subject: RE: ace leaking (was: Re: [idn] Debunking the ACE myth)
Date: Tue, 24 Jul 2001 13:15:47 -0700
Message-ID: <JMEEJIPINNOMDJMPPAMKMENDDGAA.kalra@langoo.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <p05100319b7836e2ccf33@[64.1.5.87]>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
X-Loop-Detect: 1
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Paul:

You have an interesting point. I can definitely speak for the Indian
scenario.

As you might know, Indian languages share a common derivation. Northern
Indian languages are derived from Sanskrit/Devanagri. Similarly southern
Indian languages share a common heritage. This is complicated by the fact
that southern Indian languages use many sanskrit words though they write
them in their own scripts.

Because of the British influence in India, almost every Indian language has
developed a romanization. Names of people and places are commonly written
both in the romanized form and the native script form. Because the same
words are used in multiple languages, the romanized forms are quite similar
if not same. For example, namaskar.com will be transliterated or romanized
in the same for in Hindi and Gujarati. Therefore, if we provide the ascii
name by default to the the Hindi namaskar.com, the gujarati will not have
any ascii
form.

I think part of the problem is that we are thinking of the problem in a very
English oriented manner. In my opinion, one of the big reasons that people
will want to get IDN is because they want their customers/users to be able
to be able to use their language. The fact that people should be able to
reach their site through ascii is a nice to have but not either a motivation
or a barrier to get the IDN.

One part of the solution will be to provide people tools to enter the data
in thier language on any platform without requiring excessive localization
or major software rehaul so they are not forced to type ascii to get to a
website if it has and IDN.

Deven
---------------
Langoo.com / Langoo.net
The Source for Multilingual Products and Services

-----Original Message-----
From: owner-idn@ops.ietf.org [mailto:owner-idn@ops.ietf.org]On Behalf Of
Paul Hoffman / IMC
Sent: Tuesday, July 24, 2001 11:29 AM
To: Marc Blanchet; idn@ops.ietf.org
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth)


At 12:10 PM -0400 7/24/01, Marc Blanchet wrote:
>I would guess the opposite (i.e. two domain names: one pure ascii
>and one full-idn (without showing the ace equivalent) ,
>but who knows the future...

That's easy for someone whose company name makes reasonable sense in
pure ASCII to say. Telling Chinese and Indian speakers that they must
register a domain name in pure ASCII is quite different. Romanization
works poorly for many languages; few Americans and Europeans realize
that.

--Paul Hoffman, Director
--Internet Mail Consortium




From owner-idn@ops.ietf.org  Tue Jul 24 17:48:07 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA26463
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 17:48:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15P9lN-000E7U-00
	for idn-data@psg.com; Tue, 24 Jul 2001 14:30:45 -0700
Received: from shell.nominum.com ([204.152.187.59])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15P9lN-000E7L-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 14:30:45 -0700
Received: by shell.nominum.com (Postfix, from userid 1411)
	id 7B4A031919; Tue, 24 Jul 2001 14:30:32 -0700 (PDT)
To: Patrik =?iso-8859-1?q?F=E4ltstr=F6m?= <paf@cisco.com>
Cc: Dan Oscarsson <Dan.Oscarsson@trab.se>, idn@ops.ietf.org,
        Rob Austein <sra@hactrn.net>
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality    Check)
References: <200107240657.IAA05387@valinor.malmo.trab.se>
	<5096309.995972076@localhost>
From: Bob Halley <Bob.Halley@nominum.com>
Date: 24 Jul 2001 14:30:32 -0700
In-Reply-To: <5096309.995972076@localhost>
Message-ID: <ywsu2023thj.fsf@shell.nominum.com>
Lines: 16
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.5
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA26463

Patrik Fältström <paf@cisco.com> writes:

> Regarding only doing nameprep in the authoritative servers, that is
> definitly not enough. That means that you might get a query after owner A,
> which nameprepped is B, and because of this, one send a query for owner A,
> but get B as a response.

This is a good point!

> I really want DNS servers to reject those kind of responses (where the
> owner in the response doesn't match the owner in the query),

BIND 4, 8, and 9 will reject such responses, both in "named" and in
libresolv.

/Bob



From owner-idn@ops.ietf.org  Tue Jul 24 23:57:21 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA11216
	for <idn-archive@lists.ietf.org>; Tue, 24 Jul 2001 23:57:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PEEk-000Mvh-00
	for idn-data@psg.com; Tue, 24 Jul 2001 19:17:22 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PEEj-000Mvb-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 19:17:21 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH1CgsnopVcwqB9IkmQnKtOQdVJylkrcxDw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GA6LSJGA; Tue, 24 Jul 2001 22:16:12 EDT
To: kalra@langoo.net
Cc: phoffman@imc.org, Marc.Blanchet@viagenie.qc.ca, idn@ops.ietf.org
Date: Tue, 24 Jul 2001 19:32:01 -0700
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth)
Message-ID: <20010724.193210.-665585.0.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.11
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-7,9-92
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

For each language, there is one language tag, so  
hin-namaskar.com is different with guj-namaskar.com.
The tag provide over 17,000 different language labels for
the issue you addressed.

Liana


On Tue, 24 Jul 2001 13:15:47 -0700 "Deven Kalra" <kalra@langoo.net>
writes:
> Paul:
> 
> You have an interesting point. I can definitely speak for the Indian
> scenario.
> 
> As you might know, Indian languages share a common derivation. 
> Northern
> Indian languages are derived from Sanskrit/Devanagri. Similarly 
> southern
> Indian languages share a common heritage. This is complicated by the 
> fact
> that southern Indian languages use many sanskrit words though they 
> write
> them in their own scripts.
> 
> Because of the British influence in India, almost every Indian 
> language has
> developed a romanization. Names of people and places are commonly 
> written
> both in the romanized form and the native script form. Because the 
> same
> words are used in multiple languages, the romanized forms are quite 
> similar
> if not same. For example, namaskar.com will be transliterated or 
> romanized
> in the same for in Hindi and Gujarati. Therefore, if we provide the 
> ascii
> name by default to the the Hindi namaskar.com, the gujarati will not 
> have
> any ascii
> form.
> 
> I think part of the problem is that we are thinking of the problem 
> in a very
> English oriented manner. In my opinion, one of the big reasons that 
> people
> will want to get IDN is because they want their customers/users to 
> be able
> to be able to use their language. The fact that people should be 
> able to
> reach their site through ascii is a nice to have but not either a 
> motivation
> or a barrier to get the IDN.
> 
> One part of the solution will be to provide people tools to enter 
> the data
> in thier language on any platform without requiring excessive 
> localization
> or major software rehaul so they are not forced to type ascii to get 
> to a
> website if it has and IDN.
> 
> Deven
> ---------------
> Langoo.com / Langoo.net
> The Source for Multilingual Products and Services
> 
> -----Original Message-----
> From: owner-idn@ops.ietf.org [mailto:owner-idn@ops.ietf.org]On 
> Behalf Of
> Paul Hoffman / IMC
> Sent: Tuesday, July 24, 2001 11:29 AM
> To: Marc Blanchet; idn@ops.ietf.org
> Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth)
> 
> 
> At 12:10 PM -0400 7/24/01, Marc Blanchet wrote:
> >I would guess the opposite (i.e. two domain names: one pure ascii
> >and one full-idn (without showing the ace equivalent) ,
> >but who knows the future...
> 
> That's easy for someone whose company name makes reasonable sense in
> pure ASCII to say. Telling Chinese and Indian speakers that they 
> must
> register a domain name in pure ASCII is quite different. 
> Romanization
> works poorly for many languages; few Americans and Europeans realize
> that.
> 
> --Paul Hoffman, Director
> --Internet Mail Consortium
> 
> 



From owner-idn@ops.ietf.org  Wed Jul 25 02:58:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA02585
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 02:58:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PHko-0003wE-00
	for idn-data@psg.com; Tue, 24 Jul 2001 23:02:42 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PHkn-0003w4-00
	for idn@ops.ietf.org; Tue, 24 Jul 2001 23:02:42 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH1CgsnopVcwqrnszRbLwVDRpcJQUZ+TxxA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GA6ZPJZD; Wed, 25 Jul 2001 02:01:46 EDT
To: kalra@langoo.net
Cc: idn@ops.ietf.org
Date: Tue, 24 Jul 2001 23:16:03 -0700
Subject: [idn] Romanization is only a mean to register hostname
Message-ID: <20010724.231719.-619809.0.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.11
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

To all:
	draft-liana-idn-step is proposing Romanization 
for all languages in DNS only, as a script block specific ACE.
Advantages are: 1
to reduce fonts of different scripts to confuse users.
2.  It also proposes for  [nameprep] to include all other local
code standards, such that where an IDN is supported, 
it doesn't matter what display code it is, a user always
finds a local input keyboard to be used and the hostname 
is properly [nameprep]ed to be convered to access DNS.  
[nameprep] is huge already.  To add a few corresponding
subsets codepoints will not increase too much of its complexity.
3.  I suspect it may speed up [nameprep] processing, since it 
limits many scripts to very specific codeblocks quickly, for 
example Kana script,  to very small sections of [nameprep].

4.  In fact, for each hostname, there will be more than one
presentations to its users, an  ASCII version and a local script
version.  For Chinese, I can see there may be four  presentations:
 one for the Mainland users, one for Taiwan users,  one for Hong 
Kong users, one in ASCII.  (Traditional and simplied characters are 
often used together in Hong Kong.)

Liana 



From owner-idn@ops.ietf.org  Wed Jul 25 07:31:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA11294
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 07:31:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PM1d-000DSQ-00
	for idn-data@psg.com; Wed, 25 Jul 2001 03:36:21 -0700
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PM1c-000DSK-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 03:36:20 -0700
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07829;
	Wed, 25 Jul 2001 06:35:19 -0400 (EDT)
Message-Id: <200107251035.GAA07829@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: idn@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [idn] I-D ACTION:draft-ietf-idn-idna-03.txt
Date: Wed, 25 Jul 2001 06:35:18 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internationalized Domain Name Working Group of the IETF.

	Title		: Internationalizing Host Names In Applications (IDNA)
	Author(s)	: P. Hoffman, P. Faltstrom
	Filename	: draft-ietf-idn-idna-03.txt
	Pages		: 
	Date		: 24-Jul-01
	
The current DNS infrastructure does not provide a way to use
internationalized host names (IDN). This document describes a mechanism
that requires no changes to any DNS server or resolver that will allow
internationalized host names to be used by end users with changes only
to applications. It allows flexibility for user input and display, and
assures that host names that have non-ASCII characters are not sent to
DNS servers or resolvers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idn-idna-03.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-idn-idna-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-idn-idna-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010724132554.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idn-idna-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idn-idna-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010724132554.I-D@ietf.org>

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Wed Jul 25 07:31:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA11304
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 07:31:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PKIu-0009wi-00
	for idn-data@psg.com; Wed, 25 Jul 2001 01:46:04 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PKIs-0009wb-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 01:46:03 -0700
Received: from valinor.malmo.trab.se (valinor [131.115.48.20]) by malmo.trab.se (8.10.1/TRAB-primary-2) with ESMTP id f6P8iEP06595 for <idn@ops.ietf.org>; Wed, 25 Jul 2001 10:44:14 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Wed, 25 Jul 2001 10:45:59 +0200 (MEST) (MET)
Message-Id: <200107250845.KAA08220@valinor.malmo.trab.se>
Date: Wed, 25 Jul 2001 10:45:59 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: [idn] Forbidden characters
To: idn@ops.ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: RvskUqxwnbJ2HBbBvoAqlQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk


If we define that nameprep must be done before names are sent over the
DNS protocol we get a lot of characters that are forbidden in host names.

For example: all upper case letters, double width and circled letters.

This is quite a change from current usage where both upper and lower case
is allowed in host names.

   Dan




From owner-idn@ops.ietf.org  Wed Jul 25 08:32:31 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA15553
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 08:32:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PNfx-000HDO-00
	for idn-data@psg.com; Wed, 25 Jul 2001 05:22:05 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PNfw-000H4D-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 05:22:05 -0700
Received: from enoshima (i204121.ppp.asahi-net.or.jp [61.125.204.121])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id VAA17061;
	Wed, 25 Jul 2001 21:10:54 +0900 (JST)
Message-Id: <4.2.0.58.J.20010725181455.0346d600@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 25 Jul 2001 18:18:06 +0900
To: John C Klensin <klensin@jck.com>, Dan Oscarsson <Dan.Oscarsson@trab.se>
From: Martin Duerst <duerst@w3.org>
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn]Reality   
  Check)
Cc: idn@ops.ietf.org
In-Reply-To: <127591451.995950555@localhost>
References: <4.2.0.58.J.20010724153735.03554340@sh.w3.mag.keio.ac.jp>
 <4.2.0.58.J.20010724153735.03554340@sh.w3.mag.keio.ac .jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hello John,

I read your Internet Draft proposing a new class, and
it looked very good to me. I'll send you a few detail comments
separately later.

I don't want to disagree with your conclusion, but I'm not
sure about the premise (that we need the original spelling),
so I didn't get into the details of what would follow.

Regards,   Martin.

At 04:55 01/07/24 -0400, John C Klensin wrote:


>--On Tuesday, 24 July, 2001 15:40 +0900 Martin Duerst
><duerst@w3.org> wrote:
>
> > Doing nameprep during operation on the server side is still a
> > bad idea. If we really need the original spelling of the name
> > (which I'm not sure we do), a new RR may be quite a bit better.
>
>Martin,
>
>It was trying to think through an approach based on a new RR
>that brought me to the conclusion that, if one went down that
>path, a whole new class would be needed.   Please work the cases
>yourself, remembering the various issues raised by CNAME, MX,
>and PTR RRs that might or might not have IDN values (targets)
>and see if you come to the same conclusion.
>
>     john
>




From owner-idn@ops.ietf.org  Wed Jul 25 08:37:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA16087
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 08:37:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PNVK-000Gi3-00
	for idn-data@psg.com; Wed, 25 Jul 2001 05:11:06 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PNVJ-000Ghx-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 05:11:05 -0700
Received: from enoshima (i204121.ppp.asahi-net.or.jp [61.125.204.121])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id VAA17058;
	Wed, 25 Jul 2001 21:10:53 +0900 (JST)
Message-Id: <4.2.0.58.J.20010725180743.0620f7a0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 25 Jul 2001 18:12:40 +0900
To: Paul Hoffman / IMC <phoffman@imc.org>,
        Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth)
In-Reply-To: <p05100319b7836e2ccf33@[64.1.5.87]>
References: <5.1.0.14.1.20010724120919.0216e138@mail.viagenie.qc.ca>
 <200107241327.JAA09700@astro.cs.utk.edu>
 <200107241327.JAA09700@astro.cs.utk.edu>
 <5.1.0.14.1.20010724120919.0216e138@mail.viagenie.qc.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 11:29 01/07/24 -0700, Paul Hoffman / IMC wrote:
>At 12:10 PM -0400 7/24/01, Marc Blanchet wrote:
>>I would guess the opposite (i.e. two domain names: one pure ascii and one 
>>full-idn (without showing the ace equivalent) ,
>>but who knows the future...
>
>That's easy for someone whose company name makes reasonable sense in pure 
>ASCII to say. Telling Chinese and Indian speakers that they must register 
>a domain name in pure ASCII is quite different. Romanization works poorly 
>for many languages; few Americans and Europeans realize that.

Yes, romanization works quite purely for some languages. Many Chinese
sites for example use mostly numeric names. But even where romanization
(or whatever else is currently used in these places) works purely, it will
work much better than openly exposed ACE, in many if not most cases.
Of course that doesn't mean everybody should be forced to get an ASCII
name, but we should at least assume that many will.

Regards,   Martin.



From owner-idn@ops.ietf.org  Wed Jul 25 08:45:23 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA16839
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 08:45:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PNVU-000GiR-00
	for idn-data@psg.com; Wed, 25 Jul 2001 05:11:16 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PNVT-000GiL-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 05:11:15 -0700
Received: from enoshima (i204121.ppp.asahi-net.or.jp [61.125.204.121])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id VAA17055;
	Wed, 25 Jul 2001 21:10:51 +0900 (JST)
Message-Id: <4.2.0.58.J.20010725180547.02c9eab0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 25 Jul 2001 18:07:07 +0900
To: Keith Moore <moore@cs.utk.edu>, liana.ydisg@juno.com
From: Martin Duerst <duerst@w3.org>
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth) 
Cc: paf@cisco.com, moore@cs.utk.edu, Marc.Blanchet@viagenie.qc.ca,
        Mark.Andrews@nominum.com, idn@ops.ietf.org
In-Reply-To: <200107241738.NAA11407@astro.cs.utk.edu>
References: <Your message of "Tue, 24 Jul 2001 10:49:02 PDT." <20010724.104905.-819277.0.liana.ydisg@juno.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Well, it can be the same site, but I guess what will happen
quite a bit is that the IDN site(s) will be in the respective
language, and the ASCII site in English, in cases where only
these two variants are done.

Regards,    Martin.

At 13:38 01/07/24 -0400, Keith Moore wrote:
>why should you bother keeping two sites, when two domains that refer
>to the same address will suffice?
>
>maybe because it will get you more customers/viewers?
>
>again, it's your choice.
>
> > I agree.  Why should I keep two different sites, when I have a lot
> > of other things to take care of?




From owner-idn@ops.ietf.org  Wed Jul 25 08:46:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA16965
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 08:46:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PNet-000HAy-00
	for idn-data@psg.com; Wed, 25 Jul 2001 05:20:59 -0700
Received: from [168.126.3.54] (helo=mail.kornet.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PNes-000HAr-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 05:20:58 -0700
Received: from soobok ([210.217.27.237])
	by mail.kornet.net (8.11.3/8.11.3) with SMTP id f6PCJns09887
	for <idn@ops.ietf.org>; Wed, 25 Jul 2001 21:19:54 +0900 (KST)
Message-ID: <007f01c11505$04a31160$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
References: <200107251035.GAA07829@ietf.org>
Subject: Re: [idn] I-D ACTION:draft-ietf-idn-idna-03.txt
Date: Wed, 25 Jul 2001 21:26:17 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I found the following addition in  section 2.1.4 of new IDNA-3:

>If an application decodes an ACE name but cannot show all of the
>characters in the decoded name, such as if the name contains characters
>that the output system cannot display, the application SHOULD show the
>name in ACE format instead of displaying the name with the replacement
>character (U+FFFD). This is to make it easier for the user to transfer
>the name correctly to other programs. Programs that by default show the
>ACE form when they cannot show all the characters in a name part SHOULD
>also have a mechanism to show the name with as many characters as
>possible and replacement characters in the positions where characters
>cannot be displayed.  (from IDNA-02)

>In many cases, the application doesn't know exactly
>what the underlying rendering engine can or cannot display.  (new)

I suggest to add the following sentence to the end of this paragraph:

  Likewise, in some cases,  end users don't know exactly what characters
the rendered glyphs represent, especially when they are not familiar
with the glyphs or the glyphs have other similarly-looking glyphs.

>In addition to the condition above, if an application decodes an ACE
>name but finds that the decoded name was not properly prepared according
>to [NAMEPREP] (for example, if it has illegal characters in it), the
>application SHOULD show the name in ACE format and SHOULD NOT display
>the name in its decoded form. This is to avoid security issues described
>in [NAMEPREP].

I suggest to insert the following sentence before the last sentence above:

  If the decoded ACE name contains ambiguous characters that are allowed
 in [NAMEPREP] but may cause confusion to end users, the application
 SHOULD display the name not only in its decoded form  but also
 in ACE format or in disambiguating user interfaces.


Soobok Lee, lsb@postel.co.kr


----- Original Message -----
From: <Internet-Drafts@ietf.org>
To: <IETF-Announce:>
Cc: <idn@ops.ietf.org>
Sent: Wednesday, July 25, 2001 7:35 PM
Subject: [idn] I-D ACTION:draft-ietf-idn-idna-03.txt


> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> This draft is a work item of the Internationalized Domain Name Working Group
of the IETF.
>
> Title : Internationalizing Host Names In Applications (IDNA)
> Author(s) : P. Hoffman, P. Faltstrom
> Filename : draft-ietf-idn-idna-03.txt
> Pages :
> Date : 24-Jul-01
>
> The current DNS infrastructure does not provide a way to use
> internationalized host names (IDN). This document describes a mechanism
> that requires no changes to any DNS server or resolver that will allow
> internationalized host names to be used by end users with changes only
> to applications. It allows flexibility for user input and display, and
> assures that host names that have non-ASCII characters are not sent to
> DNS servers or resolvers.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-idn-idna-03.txt
>
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> "get draft-ietf-idn-idna-03.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> mailserv@ietf.org.
> In the body type:
> "FILE /internet-drafts/draft-ietf-idn-idna-03.txt".
>
> NOTE: The mail server at ietf.org can return the document in
> MIME-encoded form by using the "mpack" utility.  To use this
> feature, insert the command "ENCODING mime" before the "FILE"
> command.  To decode the response(s), you will need "munpack" or
> a MIME-compliant mail reader.  Different MIME-compliant mail readers
> exhibit different behavior, especially when dealing with
> "multipart" MIME messages (i.e. documents which have been split
> up into multiple messages), so check your local documentation on
> how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>





From owner-idn@ops.ietf.org  Wed Jul 25 08:49:17 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA17343
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 08:49:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PNVG-000Ghv-00
	for idn-data@psg.com; Wed, 25 Jul 2001 05:11:02 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PNVF-000Ghp-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 05:11:01 -0700
Received: from enoshima (i204121.ppp.asahi-net.or.jp [61.125.204.121])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id VAA17064;
	Wed, 25 Jul 2001 21:10:55 +0900 (JST)
Message-Id: <4.2.0.58.J.20010725182335.06319630@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 25 Jul 2001 18:25:30 +0900
To: M=?ISO-2022-JP?B?GyRCaU8bKEI=?=s Nilsson <mansaxel@besserwisser.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Debunking the ACE myth
Cc: idn@ops.ietf.org
In-Reply-To: <E15Ox9K-000C3t-00@psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

At 01:02 01/07/24 -0700, M$BiO(Bs Nilsson wrote:
>You forget the legal hassle that would arise if a TLD Registry
>forgot to tell people what their ACE-encoded string is. Or the
>support hell that arises -- think angry customer who screams "I
>wanted "r$Bdk(Bsm$Bvr(Bg$Bes(B", not this bq-- blaha!!". I see a strong need
>for registries to print out the ACE encoded form in all kinds of
>correspondance with their domain name holders -- provided that ACE
>is chosen.

That's definitely a good point. But that's not the general case
(i.e. making your domain name/email address known to the public).

Regards,   Martin.



From owner-idn@ops.ietf.org  Wed Jul 25 09:20:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA19873
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 09:20:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PNVR-000GiJ-00
	for idn-data@psg.com; Wed, 25 Jul 2001 05:11:13 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PNVQ-000Gi9-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 05:11:12 -0700
Received: from enoshima (i204121.ppp.asahi-net.or.jp [61.125.204.121])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id VAA17067;
	Wed, 25 Jul 2001 21:10:56 +0900 (JST)
Message-Id: <4.2.0.58.J.20010725182609.03001c30@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 25 Jul 2001 18:36:20 +0900
To: Patrik F=?ISO-2022-JP?B?GyRCZ00bKEI=?=tstr
 =?ISO-2022-JP?B?GyRCi04bKEI=?= <paf@cisco.com>,
        Keith Moore <moore@cs.utk.edu>,
        Marc 
 Blanchet <Marc.Blanchet@viagenie.qc.ca>
From: Martin Duerst <duerst@w3.org>
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth) 
Cc: Keith Moore <moore@cs.utk.edu>, Mark.Andrews@nominum.com, idn@ops.ietf.org
In-Reply-To: <5468535.995996371@localhost>
References: <200107241327.JAA09700@astro.cs.utk.edu>
 <200107241327.JAA09700@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

At 17:39 01/07/24 +0200, Patrik F$BgM(Btstr$B‹N(B wrote:
>--On 01-07-24 09.27 -0400 Keith Moore <moore@cs.utk.edu> wrote:
>
> > right.  I was talking about deliberate exposure of an ACE, not accidental
> > exposure of an ACE.  I don't think that many people will deliberately
> > show people ACE names (say on a business card) and expect people to
> > type them in.  They'll either show the native form of the name, or they'll
> > show an ASCII DNS name, or both.
>
>Just to continue this discussion in absurdum:

Hello Patrick - I'm not sure there is anything absurd in this
discussion. I very much agree with Keith. Deliberate exposure
of ace (if we go for ace) will be rare if not very rare.


>I don't want to be forced to register more than one domainname. Why should
>I register something in US-ASCII only when we have IDN? I am not interested
>in paying some registry and ISP for hosting an extra domain just because
>some people can not type in adiaeresis. I rather expose the ACE and let
>people fight with it (ugly as it is).

You may want to do that because you know how things work, and you don't
care if other people have problems reaching you because you get too much
email anyway. But for people who want to get reached by their business
partners, I very much agree with Keith and others that they may want
an ASCII address.

Also, it may be that some more people using Latin script may not want
another address because they feel that there is no natural boundary
(or there shouldn't be) between ASCII and the rest of Latin. It may
be difficult for them to understand, or to want to admit, that a few
of the letters they use should be more difficult to enter. Indeed
I guess you don't put your downgraded spelling of Faltstrom on your
business card, besides the full spelling or on the other side of it.
On the other hand, people in Japan or in the Arabic countries,... are
very much aware that the rest of the world doesn't read their
letters, so they will be much more inclined for a double registration.

A separate reason for double registration in cases like yours may be
preemptive registration because you don't want anybody else to get
faltstrom.


Regards,   Martin.



From owner-idn@ops.ietf.org  Wed Jul 25 11:08:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA29253
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 11:08:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PPci-000Mrs-00
	for idn-data@psg.com; Wed, 25 Jul 2001 07:26:52 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PPch-000Mrm-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 07:26:52 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net for <idn@ops.ietf.org>;
          Wed, 25 Jul 2001 07:37:27 -0700
Message-ID: <016b01c11517$09e02480$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: <idn@ops.ietf.org>
Subject: [idn] different (yet similiar) scripts
Date: Wed, 25 Jul 2001 10:35:22 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0168_01C114F5.82516540"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0168_01C114F5.82516540
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I have a idea on what to do about the need for converting of different =
scripts that are of the same spoken language (ie.  Chinese, Indian =
scripts.)  It will certainly be good to implement this idea. =20

Can anyone tell me if it is too late to submit a draft?  Also, do I need =
to have more then 7 supporters inorder for it to be even considered?  If =
it is too late, that is ok...=20

Thanks
Ben Chan

------=_NextPart_000_0168_01C114F5.82516540
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4616.200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I have a idea on what to do about the =
need for=20
converting of different scripts that are of the same spoken language =
(ie.&nbsp;=20
Chinese, Indian scripts.)&nbsp; </FONT><FONT face=3DArial size=3D2>It =
will certainly=20
be&nbsp;good to implement this idea.&nbsp; </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Can anyone tell me if it is too late to =
submit a=20
draft?&nbsp; Also, do I need to have more then 7 supporters inorder for =
it to be=20
even considered? &nbsp;If it is too late, that is ok... </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Ben Chan</FONT></DIV></BODY></HTML>

------=_NextPart_000_0168_01C114F5.82516540--




From owner-idn@ops.ietf.org  Wed Jul 25 11:32:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA01539
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 11:32:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PQDU-000OQy-00
	for idn-data@psg.com; Wed, 25 Jul 2001 08:04:52 -0700
Received: from sina.sharif.ac.ir ([62.41.32.2] ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PQD2-000OMS-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 08:04:27 -0700
Received: from bamdad.org (IDENT:root@gilas.bamdad.org [62.41.28.76])
	by Sina.sharif.ac.ir (8.9.3/8.9.3) with ESMTP id TAA22080;
	Wed, 25 Jul 2001 19:33:09 +0430
Received: from localhost (roozbeh@localhost)
	by bamdad.org (8.11.2/8.11.2) with ESMTP id f6PF3ow04196;
	Wed, 25 Jul 2001 19:33:53 +0430
X-Authentication-Warning: gilas.bamdad.org: roozbeh owned process doing -bs
Date: Wed, 25 Jul 2001 19:33:48 +0430 (IRST)
From: Roozbeh Pournader <roozbeh@sharif.edu>
X-X-Sender:  <roozbeh@gilas.bamdad.org>
To: Martin Duerst <duerst@w3.org>
cc: John C Klensin <klensin@jck.com>, Dan Oscarsson <Dan.Oscarsson@trab.se>,
        <idn@ops.ietf.org>
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn]Reality     Check)
In-Reply-To: <4.2.0.58.J.20010725181455.0346d600@sh.w3.mag.keio.ac.jp>
Message-ID: <Pine.LNX.4.33.0107251929480.2575-100000@gilas.bamdad.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Wed, 25 Jul 2001, Martin Duerst wrote:

> I don't want to disagree with your conclusion, but I'm not
> sure about the premise (that we need the original spelling),
> so I didn't get into the details of what would follow.

We may need original spelling, for example if we decide that we need to
stop Arabic letters from joining, by using a ZWNJ between them (since a
space is not available). Multiword Arabic domain names will be unreadable
if the words join. But since ZNWJ is stripped at nameprep, we will
sometimes need to get to the original. You get the idea.

roozbeh




From owner-idn@ops.ietf.org  Wed Jul 25 12:31:49 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA07938
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 12:31:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PQuk-0000V8-00
	for idn-data@psg.com; Wed, 25 Jul 2001 08:49:34 -0700
Received: from lobo.enic.cc ([209.237.72.66] helo=mail.enic.cc)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PQuj-0000SX-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 08:49:33 -0700
Received: from enic.cc (tailback.nic.cc [209.237.72.17])
	by mail.enic.cc (Postfix) with ESMTP
	id 254656A915; Wed, 25 Jul 2001 08:48:58 -0700 (PDT)
Message-ID: <3B5EEA6A.E1CDB594@enic.cc>
Date: Wed, 25 Jul 2001 08:48:58 -0700
From: Dan Ebert <dan@enic.cc>
Organization: eNIC Corporation
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Roozbeh Pournader <roozbeh@sharif.edu>
Cc: Martin Duerst <duerst@w3.org>, John C Klensin <klensin@jck.com>,
        Dan Oscarsson <Dan.Oscarsson@trab.se>, idn@ops.ietf.org
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn]Reality     Check)
References: <Pine.LNX.4.33.0107251929480.2575-100000@gilas.bamdad.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Roozbeh Pournader wrote:
> 
> On Wed, 25 Jul 2001, Martin Duerst wrote:
> 
> > I don't want to disagree with your conclusion, but I'm not
> > sure about the premise (that we need the original spelling),
> > so I didn't get into the details of what would follow.
> 
> We may need original spelling, for example if we decide that we need to
> stop Arabic letters from joining, by using a ZWNJ between them (since a
> space is not available). Multiword Arabic domain names will be unreadable
> if the words join. But since ZNWJ is stripped at nameprep, we will
> sometimes need to get to the original. You get the idea.
> 
> roozbeh

It is possible to prevent Arabic letters from joining by separating
words by hyphens.  While I don't think this isn't something which should
be incoporated into any kind of proposal, it may be a useful convention
for the registration of Arabic names. I am not an Arabic speaker so I
don't know how acceptable this would be, but it is a possible solution.

-- 
Dan Ebert      <dan@enic.cc>       eNIC Corporation
------------------------------------------------------------



From owner-idn@ops.ietf.org  Wed Jul 25 14:04:18 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA17746
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 14:04:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PSYh-0005XE-00
	for idn-data@psg.com; Wed, 25 Jul 2001 10:34:55 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.31 #1)
	id 15PSYg-0005X8-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 10:34:54 -0700
Received: (qmail 6779 invoked from network); 26 Jul 2001 00:53:41 -0000
Received: from chubby.internal.realnames.com (HELO heaven.internal.realnames.com) (10.1.5.39)
  by friendly.realnames.com with SMTP; 26 Jul 2001 00:53:41 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:4136]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <173842@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Wed, 25 Jul 2001 10:33:00 AM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2650.21)
	id <PJWH3D6V>; Wed, 25 Jul 2001 10:34:27 -0700
Message-ID: <B7233BD6980AD411875700508B5BD5D2011E971C@elporto.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: idn@ops.ietf.org
Subject: RE: [idn] Forbidden characters
Date: Wed, 25 Jul 2001 10:34:27 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> If we define that nameprep must be done before names are sent 
> over the DNS protocol we get a lot of characters that are 
> forbidden in host names.
> 
> For example: all upper case letters, double width and circled letters.
> 
> This is quite a change from current usage where both upper 
> and lower case is allowed in host names.

They are not forbidden: they will get folded to something else. So you can
still write and register your names with, say, U+00DC LATIN CAPITAL LETTER U
WITH DIAERESIS and U+2462 CIRCLED DIGIT THREE. They can be used in your
applications and by your users. They are just strictly euqivalent to U+00FC
LATIN SAMLL LETTER U WITH DIAERESIS and U+0031 DIGIT ONE. Just like 'A' and
'a' are strictly equivalent today in DNS.

YA



From owner-idn@ops.ietf.org  Wed Jul 25 16:34:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA04593
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 16:34:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PV9z-000CUU-00
	for idn-data@psg.com; Wed, 25 Jul 2001 13:21:35 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PV9x-000CUC-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 13:21:34 -0700
Received: from zetnet.co.uk (man-s229.dialup.zetnet.co.uk [194.247.45.100])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6PKJrp11205;
	Wed, 25 Jul 2001 21:19:53 +0100
Message-ID: <3B5F247E.1D3711C8@zetnet.co.uk>
Date: Wed, 25 Jul 2001 20:56:46 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: Roozbeh Pournader <roozbeh@sharif.edu>, idn@ops.ietf.org
Subject: [idn] Re: Just send UTF-8 with nameprep
References: <Pine.LNX.4.33.0107251929480.2575-100000@gilas.bamdad.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

Roozbeh Pournader wrote:
> On Wed, 25 Jul 2001, Martin Duerst wrote:
> 
> > I don't want to disagree with your conclusion, but I'm not
> > sure about the premise (that we need the original spelling),
> > so I didn't get into the details of what would follow.
> 
> We may need original spelling, for example if we decide that we need to
> stop Arabic letters from joining, by using a ZWNJ between them (since a
> space is not available). Multiword Arabic domain names will be unreadable
> if the words join.

What's wrong with using hyphens to separate words?

(Remember that English domain names don't look like English sentences,
either.)

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO18kTDkCAxeYt5gVAQFmawgAk70aIEMWAe//blYvqhjw3+htqxdGjldw
XbngLCF+td5LNixhVK7ITiY3G+S9T7ScgIQiREACVulPsyvwo+W0IdDNDczOOhqh
V5MeP1mf4azNdczF9B1kgw7Tw2G17GdP2avKi7n599ywbckC+Ubb6Lbek51udWoR
lU62u8Ch+r2mMvu3DnPRPENGGly3BMqZPKTFcuwpk1wPRYG+rJyZmxa6kgmrd+Fg
TPEBCy2ZiabZr0YmZds0CWIiKDEPrDT6Cu+Qgqf3SeujO8gw44ouuKKwS0wAPMaQ
MTt2WsmXLXOOhxfTbTk8/D0rWj6ZJXScPa+y+9BD6Z0qHECgEVNR6A==
=5whD
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Wed Jul 25 20:08:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA23531
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 20:08:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PXiu-000Lj0-00
	for idn-data@psg.com; Wed, 25 Jul 2001 16:05:48 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PXiu-000Lis-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 16:05:48 -0700
Received: from bbthead.dcrocker.net ([200.37.188.21])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id QAA06552
	for <idn@ops.ietf.org>; Wed, 25 Jul 2001 16:05:45 -0700
Message-Id: <5.1.0.14.2.20010725165933.0217a030@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 25 Jul 2001 17:48:39 -0500
To: idn@ops.ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Subject: [idn] iDN Transition Support Requirements
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk



What portions of the Internet must support the relevant DNS mechanisms, for 
ACE versus UTF-8?

Let's make sure we have in mind the full set of components that might be 
relevant.  So, here is a rough topology of the generic Internet space, for 
DNS processing:


Client                                  Server
App                                             App

         Client
         DNS

                 DNS                     DNS
                 Srv1                    Srv2

                         DNS Srv1
                         Admin Tools


And application specifics for email:

Mail            Submit          MTA1    List            MTA2    POP 
or          Mail
UA2             Srv                     Expander                IMAP 
Srv        UA2


(Web cognoscenti are invited to add specifics for that part of the 
world.  I hate ascii charts.)


Let look at 2 scenarios:

1.  Minimal use.  Here we want someone to be able to specify an iDN and 
have the associated application make contact with the desired host.  Only 
the requesting user is relevant to this case.

2.  Comfortable use.  This goes beyond Minimal use by also providing some 
end-to-end comfort for the other participating users.



Minimal use, ACE
----------------

a.  Administrative Tools for target DNS name must be upgraded to permit 
adding iDN strings into domain name table.

b.  Requesting user enters the domain name in the 'native' character 
set.  This, of course, means that the application taking the data in must 
support the character set.  This is entirely independent of ACE versus UTF-8.

c.  Application hands the string to the client DNS software.  It therefore 
must understand the native character set and convert it to ACE form.  (One 
might wrap a layer around the client DNS code, to make iDN transparent to 
the client code, but I'm guessing that there is no major benefit; in any 
event, please treat the implementation choice as irrelevant:  some code 
around this area needs to handle iDN strings in native character sets and 
to make it then comform to iDN specifications.

c.  End of list.  No other portions of the system need to handle iDN.  All 
other DNS components behave as always.  Other users might see ugly strings, 
but the strings will not need "interpretation" as iDN strings.  Nothing breaks.


Comfortable use, ACE
--------------------

c.  Other participants' applications must support iDN, though each can be 
upgraded at their own convenience.

d.  End of list.



Minimal use, UTF-8
------------------

a.  same as ACE

b.  same as ACE

c.  Every DNS component through the lookup sequence needs to support iDN, 
before a successful lookup can be achieved.

d.  The target host application must support iDN, if it does any domain 
name processing, such as to comfirm IP address and domain name matching, or 
to display the string in native form.

e.  End of list.


Comfortable use, UTF-8
----------------------

same as Minimal use, UTF8.


So...

ACE permits incremental adoption.  For a first level of utility, only the 
requesting user's software and the target host' domain server 
administrative tools need to be enhanced.  On reflection, it will probably 
seem obvious that one cannot get more minimal than that.

By contrast, UTF-8 does not achieve minimal utility unless and until all 
DNS-aware applications in the processing path are able to support iDN.

Taking a look at the email set of applications, we should note that most of 
them are under independent administrative control.  So that a great many 
independent administrators must ensure their software has been upgraded 
before iDN is useful.  As an example, I'll note that besides having no 
control over the intermediate MTAs, I have no control over the POP server 
software I access.  And then there are all those List servers...


My question then, are:

a)  What technical errors are there in the above?

b)  What guarantees do we have about breakage/non-breakage when UTF-8 is 
received by each of the relevant applications components, or how much 
effort is needed obtain those guarantees?  And please note that the answer 
to the equivalent question, for ACE, is already known:  No breakage.

c)  Unless someone has done a stellar job with a), above, please remind 
me/us why this debate has continued for so long...

d/
---------,-
Dave Crocker  <mailto:dcrocker@brandenburg.com>
Brandenburg InternetWorking  <http://www.brandenburg.com>
tel +1.408.246.8253;  fax +1.408.273.6464




From owner-idn@ops.ietf.org  Wed Jul 25 20:09:01 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA23566
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 20:09:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PXjV-000Lky-00
	for idn-data@psg.com; Wed, 25 Jul 2001 16:06:25 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PXjU-000Lkh-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 16:06:24 -0700
Received: from bbthead.dcrocker.net ([200.37.188.21])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id QAA06587
	for <idn@ops.ietf.org>; Wed, 25 Jul 2001 16:06:22 -0700
Message-Id: <5.1.0.14.2.20010724223525.02918d60@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 24 Jul 2001 22:42:17 -0500
To: idn@ops.ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Subject: [idn] Debunking the UTF-8 myth
In-Reply-To: <3B5C6A12.6BDD6AAF@ehsco.com>
References: <200107231126.NAA05269@valinor.malmo.trab.se>
 <p05100317b782111dc570@[165.227.249.20]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk



Please forgive a minor distraction, but it occurs to me that the ACE vs. 
UTF-8 debate has UTF-8 positioned inaccurately..

ACE is purported to be ugly because it translates clean data into an ASCII 
form.

By contrast, UTF-8 is purported to be better because it is 8-bit clean.

Indeed, it IS 8-bit clean, but the source UTF table needs more than 8 bits.

In other words, UTF-8 plays havoc with encoding rules, in order to work 
with an 8-bit model.  As such, some characters take 8-bits, but some take 
24, no?

In other words, UTF-8 also requires a special encoding pass, albeit one 
that maps the data to 8-bit chunks rather than ASCII chunks.  But it 
appears to be no more pure or direct than ASCII.

At the same time, UTF-8 requires more of the infrastructure to be upgraded 
before there is much utility for iDN.  ACE requires less.

Please do provide a counter-explanation, folks.  I'll be honestly delighted 
to be wrong about this assessment, as long as the 'wrong' is in technical 
terms from a system-wide perspective.

d/

----------
Dave Crocker  <mailto:dcrocker@brandenburg.com>
Brandenburg InternetWorking  <http://www.brandenburg.com>
tel +1.408.246.8253;  fax +1.408.273.6464




From owner-idn@ops.ietf.org  Wed Jul 25 20:14:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA23878
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 20:14:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PYSx-000OUJ-00
	for idn-data@psg.com; Wed, 25 Jul 2001 16:53:23 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PYSw-000OU7-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 16:53:22 -0700
Received: from bbthead.dcrocker.net ([200.37.188.21])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id QAA08121
	for <idn@ops.ietf.org>; Wed, 25 Jul 2001 16:53:20 -0700
Message-Id: <5.1.0.14.2.20010725183744.044caaa0@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 25 Jul 2001 18:39:53 -0500
To: idn@ops.ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth)
In-Reply-To: <p05100319b7836e2ccf33@[64.1.5.87]>
References: <5.1.0.14.1.20010724120919.0216e138@mail.viagenie.qc.ca>
 <200107241327.JAA09700@astro.cs.utk.edu>
 <200107241327.JAA09700@astro.cs.utk.edu>
 <5.1.0.14.1.20010724120919.0216e138@mail.viagenie.qc.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

this mini-debate about registering multiple domain names is really about 
marketing.  less grandly, it is about convenience for the people you 
communicate with.

an organization will choose whatever set of domain name strings it deems 
helpful for communicating with various audiences.    organizations have 
been doing this a long time and there is nothing really special about 
domain names, in this regard...  as long as we do not impose peculiar 
requirements on them.

So,

At 10:39 AM 7/24/2001, Patrik Fältström wrote:
>  I am not interested in paying some registry and ISP for hosting an extra 
> domain just because
>some people can not type in adiaeresis. I rather expose the ACE and let 
>people fight with it (ugly as it is).

is offset by earlier comments about difficulty in finding the right 
keystrokes for generating the characters, and your own desire for a way to 
type a japanese iDN without having to know how to generate the japanese 
characters.

The point is that domain holders will (and do) pay attention to the 
conveniences of those who must type their domain names.  Those wishing 
maximum ease will choose a range of names.

Just as there is www.ca.gov and www.state.ca.us, there will be (multiple 
domain names in multiple character sets, for the same organization.)

An entirely different matter would be this standards body doing anything 
that required or prevented that choice.

d/




d/


----------
Dave Crocker  <mailto:dcrocker@brandenburg.com>
Brandenburg InternetWorking  <http://www.brandenburg.com>
tel +1.408.246.8253;  fax +1.408.273.6464




From owner-idn@ops.ietf.org  Wed Jul 25 20:26:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA24471
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 20:26:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PYfV-000PFp-00
	for idn-data@psg.com; Wed, 25 Jul 2001 17:06:21 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PYfT-000PFe-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 17:06:20 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id UAA21382;
        Wed, 25 Jul 2001 20:06:17 -0400 (EDT)
Message-Id: <200107260006.UAA21382@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Dave Crocker <dhc@dcrocker.net>
cc: idn@ops.ietf.org
Subject: Re: [idn] Debunking the UTF-8 myth 
In-reply-to: Your message of "Tue, 24 Jul 2001 22:42:17 CDT."
             <5.1.0.14.2.20010724223525.02918d60@dcrocker.net> 
Date: Wed, 25 Jul 2001 20:06:16 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> By contrast, UTF-8 is purported to be better because it is 8-bit clean.

UTF-8 is purported to be better largely on the assumption that everything
else in the world either already uses, or will soon use UTF-8 anyway.  
I could be wrong, but I don't share that assumption.  

Keith

p.s. what does it mean for a character set to be "8-bit clean", anyway?



From owner-idn@ops.ietf.org  Wed Jul 25 21:36:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA00033
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 21:36:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PZfc-0002aS-00
	for idn-data@psg.com; Wed, 25 Jul 2001 18:10:32 -0700
Received: from mail07a.vwh1.net ([209.238.9.57])
	by psg.com with smtp (Exim 3.31 #1)
	id 15PZfb-0002aM-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 18:10:31 -0700
Received: from www.langoo.net (208.55.128.123)
	by mail07a.vwh1.net (RS ver 1.0.60s) with SMTP id 026342450;
	Wed, 25 Jul 2001 21:10:13 -0400 (EDT)
Message-ID: <004301c11570$1e551f20$67a8a8c0@siteops>
From: "Gary Krall" <gary@langoo.net>
To: "Dave Crocker" <dhc@dcrocker.net>
Cc: <idn@ops.ietf.org>
References: <5.1.0.14.1.20010724120919.0216e138@mail.viagenie.qc.ca> <200107241327.JAA09700@astro.cs.utk.edu> <200107241327.JAA09700@astro.cs.utk.edu> <5.1.0.14.1.20010724120919.0216e138@mail.viagenie.qc.ca> <5.1.0.14.2.20010725183744.044caaa0@dcrocker.net>
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth)
Date: Wed, 25 Jul 2001 18:12:52 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Loop-Detect: 1
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Dave:

This is an excellent point.  In the original spirit of the internet users
should be given choices and they should have the flexibility to select the
appropriate solution for them.  In that regard if a company wants to
register both ML as well as ASCII names and how they want to create the
ASCII names should be up to them.

Patrik's proposal, if I understand it, of letting users with use the ACE
representation does provide an option for  ASCII "only" users.  But, as
Patrik points out is quite "ugly" given the current "bq--xxxx" structure.
Instead, a company can make a much better choice of how to create
alternatives for their in language names.  For example if a domain is "täg"
a company may want to regsiter the ASCII domain "taag" and provide both
alternatives as links to their domain.

But the point that Patrik makes about not forcing people to regsiter
multiple domain names just because they need a ML name is well taken.  IMHO,
a correct solution would be to solve the basic problem of being able to
input mulitlingual characters on any platform without requiring multilingual
OS support.  Software such as this that would co-exist within an ASCII
infrastucture and enable users the ability to input ML characters might be
worth considering.

Gary.

----- Original Message -----
From: "Dave Crocker" <dhc@dcrocker.net>
To: <idn@ops.ietf.org>
Sent: Wednesday, July 25, 2001 4:39 PM
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth)


> this mini-debate about registering multiple domain names is really about
> marketing.  less grandly, it is about convenience for the people you
> communicate with.
>
> an organization will choose whatever set of domain name strings it deems
> helpful for communicating with various audiences.    organizations have
> been doing this a long time and there is nothing really special about
> domain names, in this regard...  as long as we do not impose peculiar
> requirements on them.
>
> So,
>
> At 10:39 AM 7/24/2001, Patrik Fältström wrote:
> >  I am not interested in paying some registry and ISP for hosting an
extra
> > domain just because
> >some people can not type in adiaeresis. I rather expose the ACE and let
> >people fight with it (ugly as it is).
>
> is offset by earlier comments about difficulty in finding the right
> keystrokes for generating the characters, and your own desire for a way to
> type a japanese iDN without having to know how to generate the japanese
> characters.
>
> The point is that domain holders will (and do) pay attention to the
> conveniences of those who must type their domain names.  Those wishing
> maximum ease will choose a range of names.
>
> Just as there is www.ca.gov and www.state.ca.us, there will be (multiple
> domain names in multiple character sets, for the same organization.)
>
> An entirely different matter would be this standards body doing anything
> that required or prevented that choice.
>
> d/
>
>
>
>
> d/
>
>
> ----------
> Dave Crocker  <mailto:dcrocker@brandenburg.com>
> Brandenburg InternetWorking  <http://www.brandenburg.com>
> tel +1.408.246.8253;  fax +1.408.273.6464
>
>




From owner-idn@ops.ietf.org  Wed Jul 25 21:59:23 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA02012
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 21:59:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Pa6e-0003pB-00
	for idn-data@psg.com; Wed, 25 Jul 2001 18:38:28 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Pa6d-0003jl-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 18:38:27 -0700
Received: from enoshima (e147011.ppp.asahi-net.or.jp [211.13.147.11])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id KAA20392;
	Thu, 26 Jul 2001 10:25:44 +0900 (JST)
Message-Id: <4.2.0.58.J.20010726102046.05fa8100@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 26 Jul 2001 10:25:29 +0900
To: Roozbeh Pournader <roozbeh@sharif.edu>
From: Martin Duerst <duerst@w3.org>
Subject: [idn] ZWNJ (was: Re: Just send UTF-8 with nameprep (was: RE:
  [idn]Reality     Check))
Cc: John C Klensin <klensin@jck.com>, Dan Oscarsson <Dan.Oscarsson@trab.se>,
        <idn@ops.ietf.org>, idn-nameprep@viagenie.qc.ca
In-Reply-To: <Pine.LNX.4.33.0107251929480.2575-100000@gilas.bamdad.org>
References: <4.2.0.58.J.20010725181455.0346d600@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 19:33 01/07/25 +0430, Roozbeh Pournader wrote:
>On Wed, 25 Jul 2001, Martin Duerst wrote:
>
> > I don't want to disagree with your conclusion, but I'm not
> > sure about the premise (that we need the original spelling),
> > so I didn't get into the details of what would follow.
>
>We may need original spelling, for example if we decide that we need to
>stop Arabic letters from joining, by using a ZWNJ between them (since a
>space is not available). Multiword Arabic domain names will be unreadable
>if the words join. But since ZNWJ is stripped at nameprep, we will
>sometimes need to get to the original. You get the idea.

Hello Roozbeh,

Many thanks for your comment. As far as I remember, currently ZNWJ is
dropped by nameprep without complaining. I think that if that leads to
problems as you describe above, we should very carefully reexamine
this decision. I have already told the nameprep design team that
I think that this should be moved to 'disallowed' to avoid surprises
like the above. But I'm not sure moving it to 'disallowed' would
solve all problems (assuming that the hyphen is used for concatenating
words).

Regards,   Martin.




From owner-idn@ops.ietf.org  Wed Jul 25 23:43:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA08560
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 23:43:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Pbih-000A0d-00
	for idn-data@psg.com; Wed, 25 Jul 2001 20:21:51 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Pbig-000A0V-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 20:21:50 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id MAA04977;
	Thu, 26 Jul 2001 12:21:37 +0900
Message-ID: <008d01c11581$5e4a0bc0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, <idn-nameprep@viagenie.qc.ca>
References: <4.2.0.58.J.20010725181455.0346d600@sh.w3.mag.keio.ac.jp> <4.2.0.58.J.20010726102046.05fa8100@sh.w3.mag.keio.ac.jp>
Subject: [idn] Arabic hyphen-like glyph
Date: Thu, 26 Jul 2001 12:16:31 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Arabic glyph U+0640 (Arabic TATWEEL) looks like Latin hyphen(-).

Arabic FULLSTOP U+06D4  looks like Latin 'underline' (or 'hyphen' ).

Using hyphen instead of punctuation char NWNJ(U+200C,No-width No joiner)
 may not help but cause confusion to native-Arabic people.


Soobok Lee, lsb@postel.co.kr

----- Original Message -----
From: "Martin Duerst" <duerst@w3.org>
To: "Roozbeh Pournader" <roozbeh@sharif.edu>
Cc: "John C Klensin" <klensin@jck.com>; "Dan Oscarsson" <Dan.Oscarsson@trab.se>;
<idn@ops.ietf.org>; <idn-nameprep@viagenie.qc.ca>
Sent: Thursday, July 26, 2001 10:25 AM
Subject: [idn] ZWNJ (was: Re: Just send UTF-8 with nameprep (was: RE:
[idn]Reality Check))


> At 19:33 01/07/25 +0430, Roozbeh Pournader wrote:
> >On Wed, 25 Jul 2001, Martin Duerst wrote:
> >
> > > I don't want to disagree with your conclusion, but I'm not
> > > sure about the premise (that we need the original spelling),
> > > so I didn't get into the details of what would follow.
> >
> >We may need original spelling, for example if we decide that we need to
> >stop Arabic letters from joining, by using a ZWNJ between them (since a
> >space is not available). Multiword Arabic domain names will be unreadable
> >if the words join. But since ZNWJ is stripped at nameprep, we will
> >sometimes need to get to the original. You get the idea.
>
> Hello Roozbeh,
>
> Many thanks for your comment. As far as I remember, currently ZNWJ is
> dropped by nameprep without complaining. I think that if that leads to
> problems as you describe above, we should very carefully reexamine
> this decision. I have already told the nameprep design team that
> I think that this should be moved to 'disallowed' to avoid surprises
> like the above. But I'm not sure moving it to 'disallowed' would
> solve all problems (assuming that the hyphen is used for concatenating
> words).
>
> Regards,   Martin.
>
>




From owner-idn@ops.ietf.org  Wed Jul 25 23:44:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA08631
	for <idn-archive@lists.ietf.org>; Wed, 25 Jul 2001 23:44:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Pbkt-000A86-00
	for idn-data@psg.com; Wed, 25 Jul 2001 20:24:07 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Pbks-0009tm-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 20:24:06 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH1CgsnopVcwq8mnpPmkaHGj5dzYNfeIzGg==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GA9ABV32; Wed, 25 Jul 2001 23:11:10 EDT
To: dan@enic.cc
Cc: roozbeh@sharif.edu, duerst@w3.org, klensin@jck.com, Dan.Oscarsson@trab.se,
        idn@ops.ietf.org
Date: Wed, 25 Jul 2001 20:00:05 -0700
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn]Reality     Check)
Message-ID: <20010725.202708.-758259.1.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.11
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

This use of  hyphen is permitted in [nameprep], and is often
used by Chinese from Taiwan.  As far as I know, it is occasionally
needed for Korean, and I think it should be used to replace " ' " 
of Pinyin standard for IDN names. 

Liana

On Wed, 25 Jul 2001 08:48:58 -0700 Dan Ebert <dan@enic.cc> writes:
> 
> Roozbeh Pournader wrote:
> > 
> > On Wed, 25 Jul 2001, Martin Duerst wrote:
> > 
> > > I don't want to disagree with your conclusion, but I'm not
> > > sure about the premise (that we need the original spelling),
> > > so I didn't get into the details of what would follow.
> > 
> > We may need original spelling, for example if we decide that we 
> need to
> > stop Arabic letters from joining, by using a ZWNJ between them 
> (since a
> > space is not available). Multiword Arabic domain names will be 
> unreadable
> > if the words join. But since ZNWJ is stripped at nameprep, we will
> > sometimes need to get to the original. You get the idea.
> > 
> > roozbeh
> 
> It is possible to prevent Arabic letters from joining by separating
> words by hyphens.  While I don't think this isn't something which 
> should
> be incoporated into any kind of proposal, it may be a useful 
> convention
> for the registration of Arabic names. I am not an Arabic speaker so 
> I
> don't know how acceptable this would be, but it is a possible 
> solution.
> 
> -- 
> Dan Ebert      <dan@enic.cc>       eNIC Corporation
> ------------------------------------------------------------
> 



From owner-idn@ops.ietf.org  Thu Jul 26 00:01:30 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA09326
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 00:01:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Pc4g-000BNS-00
	for idn-data@psg.com; Wed, 25 Jul 2001 20:44:34 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Pc4e-000BNJ-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 20:44:33 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id MAA12148
	for <idn@ops.ietf.org>; Thu, 26 Jul 2001 12:44:23 +0900
Message-ID: <00c501c11584$8cca2950$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Subject: [idn] Cherokee letters look like uppercase Latin letters
Date: Thu, 26 Jul 2001 12:39:18 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

If you look into http://www.unicode.org/charts/PDF/U13A0.pdf,
You can find most of the Cherokee letters look identical to Latin Uppercase
letters.

Do we need to allow Cherokee letters in IDN?

Soobok Lee
----------------------------------------------------------------------------

http://www.omniglot.com/writing/cherokee.htm

Origin
The Cherokee syllabary, reputedly invented by Chief Sequoyah of the Cherokee,
was introduced in 1819. Sequoyah's descendants claim that he was the last
surviving member of his tribe's scribe clan and the Cherokee syllabary was
invented by persons unknown at a much earlier date.
By 1820, thousands of Cherokees had learnt the syllabary, and by 1830, 90% were
literate in their own language. Books, religious texts, almanacs and newspapers
were all published using the syllabary, which was widely used for over 100
years.
The syllabary is still used, but only by a fairly small number of people.
Efforts, such the Carnegie Cherokee Project, are being made to revive both the
Cherokee language and the Cherokee syllabary.
Used to write:
Cherokee (Tsalagi), a Southern Iroquoian language spoken by around 22,500 people
in North Carolina and Oklahoma.




From owner-idn@ops.ietf.org  Thu Jul 26 00:51:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA11572
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 00:51:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PcZs-000DFM-00
	for idn-data@psg.com; Wed, 25 Jul 2001 21:16:48 -0700
Received: from mail.fm-net.ne.jp ([211.15.66.133])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PcZr-000DFG-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 21:16:47 -0700
Received: from bruce (bruce.fm-net.ne.jp [211.15.66.163])
	by mail.fm-net.ne.jp (8.9.3/8.8.7) with SMTP id NAA27093
	for <idn@ops.ietf.org>; Thu, 26 Jul 2001 13:16:45 +0900
Message-ID: <012d01c11589$a258b570$a3420fd3@bruce>
From: "Bruce Thomson" <bthomson@fm-net.ne.jp>
To: <idn@ops.ietf.org>
References: <20010725.202708.-758259.1.liana.ydisg@juno.com>
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn]Reality     Check)
Date: Thu, 26 Jul 2001 13:15:41 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Using hyphen in Japanese would be a bit confusing, as a different
dash is used to indicate long vowels.

----- Original Message -----
From: <liana.ydisg@juno.com>
To: <dan@enic.cc>
Cc: <roozbeh@sharif.edu>; <duerst@w3.org>; <klensin@jck.com>;
<Dan.Oscarsson@trab.se>; <idn@ops.ietf.org>
Sent: Thursday, July 26, 2001 12:00 PM
Subject: Re: Just send UTF-8 with nameprep (was: RE: [idn]Reality Check)


> This use of  hyphen is permitted in [nameprep], and is often
> used by Chinese from Taiwan.  As far as I know, it is occasionally
> needed for Korean, and I think it should be used to replace " ' "
> of Pinyin standard for IDN names.
>
> Liana
>
> On Wed, 25 Jul 2001 08:48:58 -0700 Dan Ebert <dan@enic.cc> writes:
> >
> > Roozbeh Pournader wrote:
> > >
> > > On Wed, 25 Jul 2001, Martin Duerst wrote:
> > >
> > > > I don't want to disagree with your conclusion, but I'm not
> > > > sure about the premise (that we need the original spelling),
> > > > so I didn't get into the details of what would follow.
> > >
> > > We may need original spelling, for example if we decide that we
> > need to
> > > stop Arabic letters from joining, by using a ZWNJ between them
> > (since a
> > > space is not available). Multiword Arabic domain names will be
> > unreadable
> > > if the words join. But since ZNWJ is stripped at nameprep, we will
> > > sometimes need to get to the original. You get the idea.
> > >
> > > roozbeh
> >
> > It is possible to prevent Arabic letters from joining by separating
> > words by hyphens.  While I don't think this isn't something which
> > should
> > be incoporated into any kind of proposal, it may be a useful
> > convention
> > for the registration of Arabic names. I am not an Arabic speaker so
> > I
> > don't know how acceptable this would be, but it is a possible
> > solution.
> >
> > --
> > Dan Ebert      <dan@enic.cc>       eNIC Corporation
> > ------------------------------------------------------------
> >
>
>




From owner-idn@ops.ietf.org  Thu Jul 26 15:04:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA04067
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 15:04:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PhvW-0007fE-00
	for idn-data@psg.com; Thu, 26 Jul 2001 02:59:30 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PhvV-0007eY-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 02:59:29 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 896B9FFC0B; Thu, 26 Jul 2001 18:01:11 +0800 (SGT)
Message-ID: <022a01c115b9$9ea9b660$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "ben" <ben@cc-www.com>, <idn@ops.ietf.org>
References: <016b01c11517$09e02480$d43f7018@mtag1.on.home.com>
Subject: Re: [idn] different (yet similiar) scripts
Date: Thu, 26 Jul 2001 17:59:11 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0227_01C115FC.AC9A9BC0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0227_01C115FC.AC9A9BC0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Ben,

It is never too late. but write your draft and submit it as a personal =
draft. \

-James Seng
  ----- Original Message -----=20
  From: ben=20
  To: idn@ops.ietf.org=20
  Sent: Wednesday, July 25, 2001 10:35 PM
  Subject: [idn] different (yet similiar) scripts


  I have a idea on what to do about the need for converting of different =
scripts that are of the same spoken language (ie.  Chinese, Indian =
scripts.)  It will certainly be good to implement this idea. =20
  =20
  Can anyone tell me if it is too late to submit a draft?  Also, do I =
need to have more then 7 supporters inorder for it to be even =
considered?  If it is too late, that is ok...=20
  =20
  Thanks
  Ben Chan

------=_NextPart_000_0227_01C115FC.AC9A9BC0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Hi Ben,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>It is never too late. but write your draft and =
submit it as a=20
personal draft. \</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>-James Seng</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A href=3D"mailto:ben@cc-www.com" title=3Dben@cc-www.com>ben</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
href=3D"mailto:idn@ops.ietf.org"=20
  title=3Didn@ops.ietf.org>idn@ops.ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, July 25, 2001 =
10:35=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [idn] different (yet =
similiar)=20
  scripts</DIV>
  <DIV><BR></DIV>
  <DIV><FONT face=3DArial size=3D2>I have a idea on what to do about the =
need for=20
  converting of different scripts that are of the same spoken language=20
  (ie.&nbsp; Chinese, Indian scripts.)&nbsp; </FONT><FONT face=3DArial =
size=3D2>It=20
  will certainly be&nbsp;good to implement this idea.&nbsp; =
</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Can anyone tell me if it is too late =
to submit a=20
  draft?&nbsp; Also, do I need to have more then 7 supporters inorder =
for it to=20
  be even considered? &nbsp;If it is too late, that is ok... =
</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Ben =
Chan</FONT></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0227_01C115FC.AC9A9BC0--




From owner-idn@ops.ietf.org  Thu Jul 26 15:04:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA04072
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 15:04:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PpHM-0009rP-00
	for idn-data@psg.com; Thu, 26 Jul 2001 10:50:32 -0700
Received: from mail-blue.research.att.com ([135.207.30.102])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PpHL-0009rA-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 10:50:31 -0700
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id B0A794CEBA; Thu, 26 Jul 2001 13:50:30 -0400 (EDT)
Received: from wave-172.research.att.com (wave-172.research.att.com [135.207.10.172])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id NAA18684;
	Thu, 26 Jul 2001 13:50:29 -0400 (EDT)
Date: Thu, 26 Jul 2001 13:50:08 -0400
From: John C Klensin <klensin@research.att.com>
To: Soobok Lee <lsb@postel.co.kr>
Cc: idn@ops.ietf.org
Subject: Re: [idn] Cherokee letters look like uppercase Latin
 letters
Message-ID: <15855507.996155408@wave-172.research.att.com>
In-Reply-To: <013601c115af$1f3f8080$ed1bd9d2@postel.co.kr>
References:  <013601c115af$1f3f8080$ed1bd9d2@postel.co.kr>
X-Mailer: Mulberry/2.1.0b2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Thursday, 26 July, 2001 17:44 +0900 Soobok Lee
<lsb@postel.co.kr> wrote:

> The initial ascii domain idea  was not a mistake, but a
> practical choice  in so early stage of the internet when  
> we had no standard for UNICODE-like universal character set .

Without getting involved in the other issues in this thread, the
above statement might be historically misleading although it is
correct.  

The original decisions came in  more than one stage, and predated
the Internet by some years.  In at least one of those cases,
internationalization issues were explicitly considered
--obviously in the context of things that evolved into ISO 646
national variants, rather than Unicode-- and the conclusion was
to focus the identifier character set on a set of characters that
was as common, broadly available, and usable at the time.  The
usability discussions considered issues very similar to those we
have discussed, including transcription from other media
(including hand-written text).  

The choice of that ASCII subset was reasonable --for identifier,
not language-- purposes at the time, but obviously is not
appropriate if one is dealing with people or devices that can't
render ASCII characters.

But at no time where non-"hostname" or non-ASCII characters
ignored in the process.  The decisions were made on the basis
that the names were identifiers, that they would rarely be seen
by ordinary users, that absolute precision of the identifiers was
a requirement, and that all users who did need to look at the
names would be able to create and render ASCII-subset characters.
We are having the discussions we are today because changes in
Internet protocols and usage patterns have called some of those
assumptions into question.

    john




From owner-idn@ops.ietf.org  Thu Jul 26 15:04:06 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA04082
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 15:04:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PpLF-000A4a-00
	for idn-data@psg.com; Thu, 26 Jul 2001 10:54:33 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PpLE-000A4H-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 10:54:32 -0700
Received: from soobok ([210.217.27.237] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id CAA17846;
	Fri, 27 Jul 2001 02:51:24 +0900
Message-ID: <024701c115fc$06772ce0$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <triballaw@thecity.sfsu.edu>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
References: <200107261426.f6QEQbN06574@nic-naa.net>
Subject: [idn] how to solve idn security problem : Re: Morning Humor .....
Date: Fri, 27 Jul 2001 02:54:32 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I know that NAMEPREP is not designed for eliminating ambiguities.
Only for making ease to type in intended IDN hostname conveniently.

OTOW, katakana 'ka' and chinese letter 'power(U+529B)' look the same.
When we(IETF participants) try to normalize them in either direction,
there may be conflict of interests between  Japan and China.
It's not wise for IETF to trigger a war between the two countries!
I had never believed it will be possible.

Likewise, normalizing  minorities' scripts in IDN into others is also
almost impossible. Your humor proved that just now.

Conclusion:
We will live with  plenty of IDN security holes forever and
IDN security relies on zone/mail administrators' faithfullness to
IDN security guidelines by IETF.

The guidelines for registries should not allow Capital 'A'-like letters
in the registered host name in authoriative dns servers in order to
secure IDN from ambiguities.
Now we came to the starting point again. Then, let's each TLD
registry to make its own guideline for strict normalizations.
And then we IETFers are free and no more responsible
for any conflicts of ethnical interests and IDN security breaches.

Read between the lines. What i want to say:
IDN security problem should be addressed in either NAMEPREP or  guidelines
if we regard it as severe one and we believe it is our duty to solve
the problem.

Soobok



----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: <triballaw@thecity.sfsu.edu>
Cc: <idn@ops.ietf.org>
Sent: Thursday, July 26, 2001 11:26 PM
Subject: [idn] Morning humor, Korean IETF participant proposes "no Cherokee"
rule


> Oki all,
>
> Background: A technical body [1] is working on allowing languages other than
> English to be used for domain names found in Web names and email addresses.
> The goal is to prevent "looks like" confusion, such as "dot-like" characters
> found in several scripts. The beneficiaries of this goal are trademark owners
> using the Net. The non-beneficiaries are cybersquatters ... and some NDNs,
neh?
>
> The acronymn "IDN" that appears in the original note (attached below) means
> "internationalized domain name", not some off-shore variation of "NDN" ;-)
>
> The "morning humor" for all triballaw subscribers, not to mention the odd
> CNO, UKB, and ECN enrollees and unenrolled Tsalagi both on this list and in
> the frequent-forwarding paths, is assume the body [2] adopting the proposed
> rule is a California 501(c)(3) acting as the technical coordination body for
> the Internet, under contract to the US DoC.
>
> What potential lines of attack may be considered by the FIL practitioner?
>
> Does it matter if "consultation" has never taken place?
>
> Generalizing, several NDN langauges other than Tsalagi use roman and non-roman
> characters, e.g., Abenaki and several other Eastern Algonquin languages use
> an "u-above-o" character for the "w" sound, reflecting the absence of the "w"
> character in 17th century French. This character is usually written as the
> numeral eight ("8"), but now, like the Tsalagi syllabary characters, is in
> an international standard. The "no confusion" principle would prevent these
> characters from being used in Web names and email addresses. Repeat for the
> sets of Roman look-alike characters used when writing <insert your language
> here>.
>
> The extension of this rule to scripts not yet in this international character
> standard would be to require the use of characters from the European "block",
> and any remaining non-European characters from a distinct "block", rather than
> creating a seperate block for all characters for any particular language.
>
> This makes collation (sorting and searching) very difficult to implement.
> The authors of the standard referenced (Unicode) are printer manufacturers,
> who are both indifferent to anything other than putting ink on paper, and
> don't do a lot of sales in Indian Country.
>
> The second bit of "morning humor" is that the standard for Tsalagi used a
> mid-19th century source, and the "correctness" of this source was confirmed
> by a non-literate Swimmer-regime CNO official.
>
> For extra credit, the Triballaw subscribers may comment on the legal issues
> posed by non-governmental bodies normatively defining living languages. The
> government of the People's Republic of China isn't amused by the same group's
> treatment of Chinese.
>
> Humorous replies to me, forward responsibly, and try not to comment on the
> visual similarity of Koreans.
>
> Kitakitamatsinopowaw,
> Eric
>
> [1] IDN Working Group of the Internet Engineering Task Force aka "IETF"
> [2] Internet Corporation for Assigned Names and Numbers, aka "ICANN"
>
> P.S. It is interesting that the Omniglot source doesn't have the usual
> borrowed-from-Europeans origin story. They also manage to cite Cree oral
> history for Cree syllabics, though they give more prominance to James
> Evans. Their Cree page is worth a detour!
> http://www.omniglot.com/writing/cree.htm
>
>
> ------- Forwarded Message
>
> Message-ID: <00c501c11584$8cca2950$ec1bd9d2@temp>
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: <idn@ops.ietf.org>
> Subject: [idn] Cherokee letters look like uppercase Latin letters
> Date: Thu, 26 Jul 2001 12:39:18 +0900
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="ks_c_5601-1987"
> Content-Transfer-Encoding: 7bit
> X-Priority: 3
> X-MSMail-Priority: Normal
> X-Mailer: Microsoft Outlook Express 6.00.2462.0000
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
> Sender: owner-idn@ops.ietf.org
> Precedence: bulk
>
> If you look into http://www.unicode.org/charts/PDF/U13A0.pdf,
> You can find most of the Cherokee letters look identical to Latin Uppercase
> letters.
>
> Do we need to allow Cherokee letters in IDN?
>
> Soobok Lee
> - ----------------------------------------------------------------------------
>
> http://www.omniglot.com/writing/cherokee.htm
>
> Origin
> The Cherokee syllabary, reputedly invented by Chief Sequoyah of the Cherokee,
> was introduced in 1819. Sequoyah's descendants claim that he was the last
> surviving member of his tribe's scribe clan and the Cherokee syllabary was
> invented by persons unknown at a much earlier date.
> By 1820, thousands of Cherokees had learnt the syllabary, and by 1830, 90%
were
> literate in their own language. Books, religious texts, almanacs and
newspapers
> were all published using the syllabary, which was widely used for over 100
> years.
> The syllabary is still used, but only by a fairly small number of people.
> Efforts, such the Carnegie Cherokee Project, are being made to revive both the
> Cherokee language and the Cherokee syllabary.
> Used to write:
> Cherokee (Tsalagi), a Southern Iroquoian language spoken by around 22,500
people
> in North Carolina and Oklahoma.
>
>
>
> ------- End of Forwarded Message
>
>




From owner-idn@ops.ietf.org  Thu Jul 26 15:04:09 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA04123
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 15:04:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Pm8B-000N5X-00
	for idn-data@psg.com; Thu, 26 Jul 2001 07:28:51 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Pm89-000N5N-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 07:28:50 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f6QEQbN06574;
	Thu, 26 Jul 2001 10:26:37 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107261426.f6QEQbN06574@nic-naa.net>
To: triballaw@thecity.sfsu.edu
cc: idn@ops.ietf.org
Subject: [idn] Morning humor, Korean IETF participant proposes "no Cherokee" rule
Date: Thu, 26 Jul 2001 10:26:36 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Oki all,

Background: A technical body [1] is working on allowing languages other than
English to be used for domain names found in Web names and email addresses.
The goal is to prevent "looks like" confusion, such as "dot-like" characters
found in several scripts. The beneficiaries of this goal are trademark owners
using the Net. The non-beneficiaries are cybersquatters ... and some NDNs, neh?

The acronymn "IDN" that appears in the original note (attached below) means
"internationalized domain name", not some off-shore variation of "NDN" ;-)

The "morning humor" for all triballaw subscribers, not to mention the odd
CNO, UKB, and ECN enrollees and unenrolled Tsalagi both on this list and in
the frequent-forwarding paths, is assume the body [2] adopting the proposed
rule is a California 501(c)(3) acting as the technical coordination body for
the Internet, under contract to the US DoC.

What potential lines of attack may be considered by the FIL practitioner?

Does it matter if "consultation" has never taken place?

Generalizing, several NDN langauges other than Tsalagi use roman and non-roman
characters, e.g., Abenaki and several other Eastern Algonquin languages use
an "u-above-o" character for the "w" sound, reflecting the absence of the "w"
character in 17th century French. This character is usually written as the
numeral eight ("8"), but now, like the Tsalagi syllabary characters, is in
an international standard. The "no confusion" principle would prevent these
characters from being used in Web names and email addresses. Repeat for the
sets of Roman look-alike characters used when writing <insert your language
here>.

The extension of this rule to scripts not yet in this international character
standard would be to require the use of characters from the European "block",
and any remaining non-European characters from a distinct "block", rather than
creating a seperate block for all characters for any particular language.

This makes collation (sorting and searching) very difficult to implement.
The authors of the standard referenced (Unicode) are printer manufacturers,
who are both indifferent to anything other than putting ink on paper, and
don't do a lot of sales in Indian Country.

The second bit of "morning humor" is that the standard for Tsalagi used a
mid-19th century source, and the "correctness" of this source was confirmed
by a non-literate Swimmer-regime CNO official.

For extra credit, the Triballaw subscribers may comment on the legal issues
posed by non-governmental bodies normatively defining living languages. The
government of the People's Republic of China isn't amused by the same group's
treatment of Chinese.

Humorous replies to me, forward responsibly, and try not to comment on the
visual similarity of Koreans.

Kitakitamatsinopowaw,
Eric

[1] IDN Working Group of the Internet Engineering Task Force aka "IETF"
[2] Internet Corporation for Assigned Names and Numbers, aka "ICANN"

P.S. It is interesting that the Omniglot source doesn't have the usual
borrowed-from-Europeans origin story. They also manage to cite Cree oral
history for Cree syllabics, though they give more prominance to James
Evans. Their Cree page is worth a detour!
http://www.omniglot.com/writing/cree.htm


------- Forwarded Message

Message-ID: <00c501c11584$8cca2950$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Subject: [idn] Cherokee letters look like uppercase Latin letters
Date: Thu, 26 Jul 2001 12:39:18 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk

If you look into http://www.unicode.org/charts/PDF/U13A0.pdf,
You can find most of the Cherokee letters look identical to Latin Uppercase
letters.

Do we need to allow Cherokee letters in IDN?

Soobok Lee
- ----------------------------------------------------------------------------

http://www.omniglot.com/writing/cherokee.htm

Origin
The Cherokee syllabary, reputedly invented by Chief Sequoyah of the Cherokee,
was introduced in 1819. Sequoyah's descendants claim that he was the last
surviving member of his tribe's scribe clan and the Cherokee syllabary was
invented by persons unknown at a much earlier date.
By 1820, thousands of Cherokees had learnt the syllabary, and by 1830, 90% were
literate in their own language. Books, religious texts, almanacs and newspapers
were all published using the syllabary, which was widely used for over 100
years.
The syllabary is still used, but only by a fairly small number of people.
Efforts, such the Carnegie Cherokee Project, are being made to revive both the
Cherokee language and the Cherokee syllabary.
Used to write:
Cherokee (Tsalagi), a Southern Iroquoian language spoken by around 22,500 people
in North Carolina and Oklahoma.



------- End of Forwarded Message




From owner-idn@ops.ietf.org  Thu Jul 26 15:04:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA04134
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 15:04:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Pl8g-000JOI-00
	for idn-data@psg.com; Thu, 26 Jul 2001 06:25:18 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Pl8f-000JOC-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 06:25:17 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Thu, 26 Jul 2001 06:35:41 -0700
Message-ID: <003e01c115d7$95f81520$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "James Seng/Personal" <James@Seng.cc>, <idn@ops.ietf.org>
References: <016b01c11517$09e02480$d43f7018@mtag1.on.home.com> <022a01c115b9$9ea9b660$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] different (yet similiar) scripts
Date: Thu, 26 Jul 2001 09:27:59 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0038_01C115B5.42AECB60"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0038_01C115B5.42AECB60
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi James,

Thanks for the info.  I will write a small intro to my I-D by tomorrow =
and post it .

Ben Chan

----- Original Message -----=20
From: James Seng/Personal=20
To: ben ; idn@ops.ietf.org=20
Sent: Thursday, July 26, 2001 5:59 AM
Subject: Re: [idn] different (yet similiar) scripts


Hi Ben,

It is never too late. but write your draft and submit it as a personal =
draft. \

-James Seng
  ----- Original Message -----=20
  From: ben=20
  To: idn@ops.ietf.org=20
  Sent: Wednesday, July 25, 2001 10:35 PM
  Subject: [idn] different (yet similiar) scripts


  I have a idea on what to do about the need for converting of different =
scripts that are of the same spoken language (ie.  Chinese, Indian =
scripts.)  It will certainly be good to implement this idea. =20

  Can anyone tell me if it is too late to submit a draft?  Also, do I =
need to have more then 7 supporters inorder for it to be even =
considered?  If it is too late, that is ok...=20

  Thanks
  Ben Chan

------=_NextPart_000_0038_01C115B5.42AECB60
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4616.200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi James,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks for the info.&nbsp; </FONT><FONT =
face=3DArial=20
size=3D2>I will write a small intro to my I-D by tomorrow and post it=20
.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Ben Chan</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV style=3D"FONT: 10pt arial">----- Original Message -----=20
<DIV style=3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A=20
title=3DJames@Seng.cc href=3D"mailto:James@Seng.cc">James =
Seng/Personal</A> </DIV>
<DIV><B>To:</B> <A title=3Dben@cc-www.com =
href=3D"mailto:ben@cc-www.com">ben</A> ;=20
<A title=3Didn@ops.ietf.org =
href=3D"mailto:idn@ops.ietf.org">idn@ops.ietf.org</A>=20
</DIV>
<DIV><B>Sent:</B> Thursday, July 26, 2001 5:59 AM</DIV>
<DIV><B>Subject:</B> Re: [idn] different (yet similiar) =
scripts</DIV></DIV>
<DIV><BR></DIV>
<DIV><FONT size=3D2>Hi Ben,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>It is never too late. but write your draft and =
submit it as a=20
personal draft. \</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>-James Seng</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dben@cc-www.com href=3D"mailto:ben@cc-www.com">ben</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Didn@ops.ietf.org =

  href=3D"mailto:idn@ops.ietf.org">idn@ops.ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, July 25, 2001 =
10:35=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [idn] different (yet =
similiar)=20
  scripts</DIV>
  <DIV><BR></DIV>
  <DIV><FONT face=3DArial size=3D2>I have a idea on what to do about the =
need for=20
  converting of different scripts that are of the same spoken language=20
  (ie.&nbsp; Chinese, Indian scripts.)&nbsp; </FONT><FONT face=3DArial =
size=3D2>It=20
  will certainly be&nbsp;good to implement this idea.&nbsp; =
</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Can anyone tell me if it is too late =
to submit a=20
  draft?&nbsp; Also, do I need to have more then 7 supporters inorder =
for it to=20
  be even considered? &nbsp;If it is too late, that is ok... =
</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Ben =
Chan</FONT></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0038_01C115B5.42AECB60--




From owner-idn@ops.ietf.org  Thu Jul 26 15:04:12 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA04144
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 15:04:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Pl9g-000JRq-00
	for idn-data@psg.com; Thu, 26 Jul 2001 06:26:20 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Pl9f-000JRk-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 06:26:19 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Thu, 26 Jul 2001 06:30:05 -0700
Message-ID: <003b01c115d6$cd833fc0$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "James Seng/Personal" <James@Seng.cc>, <idn@ops.ietf.org>
References: <016b01c11517$09e02480$d43f7018@mtag1.on.home.com> <022a01c115b9$9ea9b660$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] different (yet similiar) scripts
Date: Thu, 26 Jul 2001 09:27:59 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0038_01C115B5.42AECB60"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0038_01C115B5.42AECB60
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi James,

Thanks for the info.  I will write a small intro to my I-D by tomorrow =
and post it .

Ben Chan

----- Original Message -----=20
From: James Seng/Personal=20
To: ben ; idn@ops.ietf.org=20
Sent: Thursday, July 26, 2001 5:59 AM
Subject: Re: [idn] different (yet similiar) scripts


Hi Ben,

It is never too late. but write your draft and submit it as a personal =
draft. \

-James Seng
  ----- Original Message -----=20
  From: ben=20
  To: idn@ops.ietf.org=20
  Sent: Wednesday, July 25, 2001 10:35 PM
  Subject: [idn] different (yet similiar) scripts


  I have a idea on what to do about the need for converting of different =
scripts that are of the same spoken language (ie.  Chinese, Indian =
scripts.)  It will certainly be good to implement this idea. =20

  Can anyone tell me if it is too late to submit a draft?  Also, do I =
need to have more then 7 supporters inorder for it to be even =
considered?  If it is too late, that is ok...=20

  Thanks
  Ben Chan

------=_NextPart_000_0038_01C115B5.42AECB60
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4616.200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi James,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks for the info.&nbsp; </FONT><FONT =
face=3DArial=20
size=3D2>I will write a small intro to my I-D by tomorrow and post it=20
.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Ben Chan</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV style=3D"FONT: 10pt arial">----- Original Message -----=20
<DIV style=3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A=20
title=3DJames@Seng.cc href=3D"mailto:James@Seng.cc">James =
Seng/Personal</A> </DIV>
<DIV><B>To:</B> <A title=3Dben@cc-www.com =
href=3D"mailto:ben@cc-www.com">ben</A> ;=20
<A title=3Didn@ops.ietf.org =
href=3D"mailto:idn@ops.ietf.org">idn@ops.ietf.org</A>=20
</DIV>
<DIV><B>Sent:</B> Thursday, July 26, 2001 5:59 AM</DIV>
<DIV><B>Subject:</B> Re: [idn] different (yet similiar) =
scripts</DIV></DIV>
<DIV><BR></DIV>
<DIV><FONT size=3D2>Hi Ben,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>It is never too late. but write your draft and =
submit it as a=20
personal draft. \</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D2>-James Seng</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dben@cc-www.com href=3D"mailto:ben@cc-www.com">ben</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Didn@ops.ietf.org =

  href=3D"mailto:idn@ops.ietf.org">idn@ops.ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, July 25, 2001 =
10:35=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [idn] different (yet =
similiar)=20
  scripts</DIV>
  <DIV><BR></DIV>
  <DIV><FONT face=3DArial size=3D2>I have a idea on what to do about the =
need for=20
  converting of different scripts that are of the same spoken language=20
  (ie.&nbsp; Chinese, Indian scripts.)&nbsp; </FONT><FONT face=3DArial =
size=3D2>It=20
  will certainly be&nbsp;good to implement this idea.&nbsp; =
</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Can anyone tell me if it is too late =
to submit a=20
  draft?&nbsp; Also, do I need to have more then 7 supporters inorder =
for it to=20
  be even considered? &nbsp;If it is too late, that is ok... =
</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Ben =
Chan</FONT></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0038_01C115B5.42AECB60--




From owner-idn@ops.ietf.org  Thu Jul 26 15:04:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA04164
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 15:04:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Pies-000ARe-00
	for idn-data@psg.com; Thu, 26 Jul 2001 03:46:22 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Pieq-000ARY-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 03:46:21 -0700
Received: from soobok ([210.217.27.237] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id TAA14707;
	Thu, 26 Jul 2001 19:46:07 +0900
Message-ID: <017e01c115c0$dad9de60$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <James@Seng.cc>, <idn@ops.ietf.org>
References: <4.2.0.58.J.20010725181455.0346d600@sh.w3.mag.keio.ac.jp> <4.2.0.58.J.20010726102046.05fa8100@sh.w3.mag.keio.ac.jp> <008d01c11581$5e4a0bc0$ec1bd9d2@temp> <01f201c115b9$143c1720$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] Re: [idn-nameprep] Arabic hyphen-like glyph
Date: Thu, 26 Jul 2001 19:50:58 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Using hyphen in place of NWNJ in Arabic multi-word domains
may cause confusion because arabic script already contains
hyphen-like letters already. that's the point.
That's not related directly to nameprep, but to IDN security.

I hope those small ratholes may not become security holes in
IDN.

Soobok Lee

----- Original Message -----
From: "James Seng/Personal" <James@Seng.cc>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>;
<idn-nameprep@viagenie.qc.ca>
Sent: Thursday, July 26, 2001 6:55 PM
Subject: [idn] Re: [idn-nameprep] Arabic hyphen-like glyph


> I think this discussion take a strange twist.
>
> I am not sure where the discussion about "folding look-alive characters"
> but that is certainly not the intention of nameprep, nor jpchar nor
> tsconv.
>
> Please keep the discussion within the focus of the core interest, namely
> nameprep, jpchar or tsconv for "matching problems".
>
> If there is intention to talk about "folding look-alive characters" then
> please write an I-D, get your 7 core interest then come back to the wg.
> Personally, I do not suggest anyone going into this rathole...
>
> -James Seng
>
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: <idn@ops.ietf.org>; <idn-nameprep@viagenie.qc.ca>
> Sent: Thursday, July 26, 2001 11:16 AM
> Subject: [idn-nameprep] Arabic hyphen-like glyph
>
>
> > Arabic glyph U+0640 (Arabic TATWEEL) looks like Latin hyphen(-).
> >
> > Arabic FULLSTOP U+06D4  looks like Latin 'underline' (or 'hyphen' ).
> >
> > Using hyphen instead of punctuation char NWNJ(U+200C,No-width No
> joiner)
> >  may not help but cause confusion to native-Arabic people.
> >
> >
> > Soobok Lee, lsb@postel.co.kr
> >
> > ----- Original Message -----
> > From: "Martin Duerst" <duerst@w3.org>
> > To: "Roozbeh Pournader" <roozbeh@sharif.edu>
> > Cc: "John C Klensin" <klensin@jck.com>; "Dan Oscarsson"
> <Dan.Oscarsson@trab.se>;
> > <idn@ops.ietf.org>; <idn-nameprep@viagenie.qc.ca>
> > Sent: Thursday, July 26, 2001 10:25 AM
> > Subject: [idn] ZWNJ (was: Re: Just send UTF-8 with nameprep (was: RE:
> > [idn]Reality Check))
> >
> >
> > > At 19:33 01/07/25 +0430, Roozbeh Pournader wrote:
> > > >On Wed, 25 Jul 2001, Martin Duerst wrote:
> > > >
> > > > > I don't want to disagree with your conclusion, but I'm not
> > > > > sure about the premise (that we need the original spelling),
> > > > > so I didn't get into the details of what would follow.
> > > >
> > > >We may need original spelling, for example if we decide that we
> need to
> > > >stop Arabic letters from joining, by using a ZWNJ between them
> (since a
> > > >space is not available). Multiword Arabic domain names will be
> unreadable
> > > >if the words join. But since ZNWJ is stripped at nameprep, we will
> > > >sometimes need to get to the original. You get the idea.
> > >
> > > Hello Roozbeh,
> > >
> > > Many thanks for your comment. As far as I remember, currently ZNWJ
> is
> > > dropped by nameprep without complaining. I think that if that leads
> to
> > > problems as you describe above, we should very carefully reexamine
> > > this decision. I have already told the nameprep design team that
> > > I think that this should be moved to 'disallowed' to avoid surprises
> > > like the above. But I'm not sure moving it to 'disallowed' would
> > > solve all problems (assuming that the hyphen is used for
> concatenating
> > > words).
> > >
> > > Regards,   Martin.
> > >
> > >
> >
>
>




From owner-idn@ops.ietf.org  Thu Jul 26 15:04:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA04175
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 15:04:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Phro-0007Rv-00
	for idn-data@psg.com; Thu, 26 Jul 2001 02:55:40 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Phrm-0007R7-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 02:55:38 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 52D07FFC0B; Thu, 26 Jul 2001 17:57:19 +0800 (SGT)
Message-ID: <01f201c115b9$143c1720$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>,
        <idn-nameprep@viagenie.qc.ca>
References: <4.2.0.58.J.20010725181455.0346d600@sh.w3.mag.keio.ac.jp> <4.2.0.58.J.20010726102046.05fa8100@sh.w3.mag.keio.ac.jp> <008d01c11581$5e4a0bc0$ec1bd9d2@temp>
Subject: [idn] Re: [idn-nameprep] Arabic hyphen-like glyph
Date: Thu, 26 Jul 2001 17:55:19 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I think this discussion take a strange twist.

I am not sure where the discussion about "folding look-alive characters"
but that is certainly not the intention of nameprep, nor jpchar nor
tsconv.

Please keep the discussion within the focus of the core interest, namely
nameprep, jpchar or tsconv for "matching problems".

If there is intention to talk about "folding look-alive characters" then
please write an I-D, get your 7 core interest then come back to the wg.
Personally, I do not suggest anyone going into this rathole...

-James Seng

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>; <idn-nameprep@viagenie.qc.ca>
Sent: Thursday, July 26, 2001 11:16 AM
Subject: [idn-nameprep] Arabic hyphen-like glyph


> Arabic glyph U+0640 (Arabic TATWEEL) looks like Latin hyphen(-).
>
> Arabic FULLSTOP U+06D4  looks like Latin 'underline' (or 'hyphen' ).
>
> Using hyphen instead of punctuation char NWNJ(U+200C,No-width No
joiner)
>  may not help but cause confusion to native-Arabic people.
>
>
> Soobok Lee, lsb@postel.co.kr
>
> ----- Original Message -----
> From: "Martin Duerst" <duerst@w3.org>
> To: "Roozbeh Pournader" <roozbeh@sharif.edu>
> Cc: "John C Klensin" <klensin@jck.com>; "Dan Oscarsson"
<Dan.Oscarsson@trab.se>;
> <idn@ops.ietf.org>; <idn-nameprep@viagenie.qc.ca>
> Sent: Thursday, July 26, 2001 10:25 AM
> Subject: [idn] ZWNJ (was: Re: Just send UTF-8 with nameprep (was: RE:
> [idn]Reality Check))
>
>
> > At 19:33 01/07/25 +0430, Roozbeh Pournader wrote:
> > >On Wed, 25 Jul 2001, Martin Duerst wrote:
> > >
> > > > I don't want to disagree with your conclusion, but I'm not
> > > > sure about the premise (that we need the original spelling),
> > > > so I didn't get into the details of what would follow.
> > >
> > >We may need original spelling, for example if we decide that we
need to
> > >stop Arabic letters from joining, by using a ZWNJ between them
(since a
> > >space is not available). Multiword Arabic domain names will be
unreadable
> > >if the words join. But since ZNWJ is stripped at nameprep, we will
> > >sometimes need to get to the original. You get the idea.
> >
> > Hello Roozbeh,
> >
> > Many thanks for your comment. As far as I remember, currently ZNWJ
is
> > dropped by nameprep without complaining. I think that if that leads
to
> > problems as you describe above, we should very carefully reexamine
> > this decision. I have already told the nameprep design team that
> > I think that this should be moved to 'disallowed' to avoid surprises
> > like the above. But I'm not sure moving it to 'disallowed' would
> > solve all problems (assuming that the hyphen is used for
concatenating
> > words).
> >
> > Regards,   Martin.
> >
> >
>




From owner-idn@ops.ietf.org  Thu Jul 26 15:04:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA04187
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 15:04:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PhDy-0004wW-00
	for idn-data@psg.com; Thu, 26 Jul 2001 02:14:30 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PhDx-0004vl-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 02:14:29 -0700
Received: from soobok ([210.217.27.237] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id SAA18138;
	Thu, 26 Jul 2001 18:14:16 +0900
Message-ID: <014e01c115b4$0ed7ba00$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
References: <B7233BD6980AD411875700508B5BD5D2011E9738@elporto.internal.realnames.com> <013601c115af$1f3f8080$ed1bd9d2@postel.co.kr>
Subject: Re: [idn] Cherokee letters look like uppercase Latin letters
Date: Thu, 26 Jul 2001 18:19:22 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

http://www.unicode.org/unicode/standard/unsupported.html will help us
to find that UNICODE 3.1 does not contain all the modern scripts that
may be added in near future.

Soobok Lee
-------------------------------------------------


Modern Scripts
The following scripts in current use in living communities are not yet
supported in Unicode. Extensions to Unicode (and ISO/IEC 10646) which
will address the needs of these scripts are being developed and
evaluated by both the Unicode Technical Committee and by ISO JTC1/SC2/WG2.
See Proposed New Scripts for details.

Kirat (Limbu)
Manipuri (Meithei, Kanglei)
Moso (Naxi)
Pahawh Hmong
Rong (Lepcha)
Tai Lu
Tai Mau
Tifinagh



Scripts awaiting approval or proposed

Philippine Scripts

Tagalog
Hanunoo
Buhid
Tagbanwa

Cham
Tai (Dai) scripts
Glagolitic
Coptic
Buginese
Old Hungarian
Phoenician
Avestan
Tifinagh (Berber)
Javanese
Lepcha (Rong)
For Plane 1 (surrogates)

Basic Egyptian Hieroglyphics
Meroitic
Old Persian Cuneiform
Ugaritic Cuneiform
Tengwar
Cirth
tlhIngan Hol
Brahmi
Old Permic
South Arabian
Pollard
Blissymbolics
Soyombo
Last updated 27-March-2001


----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Sent: Thursday, July 26, 2001 5:44 PM
Subject: Re: [idn] Cherokee letters look like uppercase Latin letters


>
> The initial ascii domain idea  was not a mistake, but a
> practical choice  in so early stage of the internet when
> we had no standard for UNICODE-like universal character set .
>
> Uppercase Latin 'A' is case-folded into latin 'a'.
> Cyrillic 'A' is also case-folded into cyrillic 'a'.
> (latin 'a' and cyrillic 'a' still look the same.)
>
> But Cherokee 'A' has no lowercase letter for it.
>
> Prefix-based Versioning on ACE may help to ease this situation around
> Cherokee and new scripts blocks to be added to UCS
> in the future.
>
> For future script additions to UCS ,we have no nameprep rules now.
> As long as we should enforce current NAMEPREP rules, we are also prohibiting
> future script additions from being used in IDN that will have to be
nameprepped
> by the future versions of ACE and NAMEPREP rules.
>
> http://www.unicode.org/unicode/alloc/Pipeline.html will help to guess
> the agenda for future ACE and NAMEPREP versioning.
>
> Regards, Soobok Lee
>
> ----- Original Message -----
> From: "Yves Arrouye" <yves@realnames.com>
> To: <idn@ops.ietf.org>
> Sent: Thursday, July 26, 2001 4:25 PM
> Subject: RE: [idn] Cherokee letters look like uppercase Latin letters
>
>
> >
> > > Do we need to allow Cherokee letters in IDN?
> >
> > It would be quite bad to deny access to IDN to one population, yes! After
> > all, we're internationalizing DNS because some populations have been left
> > over initially and we want to fix that.
> >
> > I find very interesting (and ironic) to see these suggestions about
> > removing characters whose glyphs may confuse some people. It is a similar
> > reasoning that led to the choice of the initial set of characters allowed
> > in DNS labels, and I am sure that in the world of then, complex scripts or
> > even exotic scripts would have been dismissed for fear of confusion for the
> > typical user. Are you really seriously suggesting to do the same mistake
> > again, but with different populations?!
> >
> > YA
> >
>
>




From owner-idn@ops.ietf.org  Thu Jul 26 15:04:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA04195
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 15:04:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Pgfc-0002ny-00
	for idn-data@psg.com; Thu, 26 Jul 2001 01:39:00 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Pgfb-0002nr-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 01:38:59 -0700
Received: from soobok ([210.217.27.237] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id RAA06954
	for <idn@ops.ietf.org>; Thu, 26 Jul 2001 17:38:48 +0900
Message-ID: <013601c115af$1f3f8080$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
References: <B7233BD6980AD411875700508B5BD5D2011E9738@elporto.internal.realnames.com>
Subject: Re: [idn] Cherokee letters look like uppercase Latin letters
Date: Thu, 26 Jul 2001 17:44:02 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


The initial ascii domain idea  was not a mistake, but a
practical choice  in so early stage of the internet when  
we had no standard for UNICODE-like universal character set .

Uppercase Latin 'A' is case-folded into latin 'a'.
Cyrillic 'A' is also case-folded into cyrillic 'a'.
(latin 'a' and cyrillic 'a' still look the same.)

But Cherokee 'A' has no lowercase letter for it.

Prefix-based Versioning on ACE may help to ease this situation around
Cherokee and new scripts blocks to be added to UCS
in the future. 

For future script additions to UCS ,we have no nameprep rules now.
As long as we should enforce current NAMEPREP rules, we are also prohibiting
future script additions from being used in IDN that will have to be nameprepped
by the future versions of ACE and NAMEPREP rules.

http://www.unicode.org/unicode/alloc/Pipeline.html will help to guess
the agenda for future ACE and NAMEPREP versioning.

Regards, Soobok Lee

----- Original Message ----- 
From: "Yves Arrouye" <yves@realnames.com>
To: <idn@ops.ietf.org>
Sent: Thursday, July 26, 2001 4:25 PM
Subject: RE: [idn] Cherokee letters look like uppercase Latin letters


> 
> > Do we need to allow Cherokee letters in IDN?
> 
> It would be quite bad to deny access to IDN to one population, yes! After
> all, we're internationalizing DNS because some populations have been left
> over initially and we want to fix that.
> 
> I find very interesting (and ironic) to see these suggestions about
> removing characters whose glyphs may confuse some people. It is a similar
> reasoning that led to the choice of the initial set of characters allowed
> in DNS labels, and I am sure that in the world of then, complex scripts or
> even exotic scripts would have been dismissed for fear of confusion for the
> typical user. Are you really seriously suggesting to do the same mistake
> again, but with different populations?!
> 
> YA
> 




From owner-idn@ops.ietf.org  Thu Jul 26 15:04:17 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA04207
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 15:04:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PgZ9-0002Nc-00
	for idn-data@psg.com; Thu, 26 Jul 2001 01:32:19 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PgZ8-0002NW-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 01:32:18 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15PgZ7-00055I-00; Thu, 26 Jul 2001 01:32:17 -0700
Date: Thu, 26 Jul 2001 08:32:17 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Debunking the UTF-8 myth
Message-ID: <20010726083217.E18533@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B7233BD6980AD411875700508B5BD5D2011E9734@elporto.internal.realnames.com>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Yves Arrouye <yves@realnames.com> wrote:

> and the fact that ACE starts from UTF-16 only doesn't help.

That was true of some of the earlier ACEs (like RACE and LACE), but none
of the ACEs left in the pool (DUDE, AMC-ACE-Z, MACE) is based on UTF-16.
The encoders take as input a sequence of Unicode code points (integers
in the range 0..10FFFF).

AMC



From owner-idn@ops.ietf.org  Thu Jul 26 15:04:19 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA04217
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 15:04:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PgQa-0001oy-00
	for idn-data@psg.com; Thu, 26 Jul 2001 01:23:28 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PgQZ-0001oP-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 01:23:27 -0700
Received: from valinor.malmo.trab.se (valinor [131.115.48.20]) by malmo.trab.se (8.10.1/TRAB-primary-2) with ESMTP id f6Q8LbP18495; Thu, 26 Jul 2001 10:21:37 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Thu, 26 Jul 2001 10:23:22 +0200 (MEST) (MET)
Message-Id: <200107260823.KAA00949@valinor.malmo.trab.se>
Date: Thu, 26 Jul 2001 10:23:22 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: RE: [idn] Forbidden characters
To: idn@ops.ietf.org, yves@realnames.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 3yabBlM5ijyUXuoY2DfWFg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk


>> If we define that nameprep must be done before names are sent 
>> over the DNS protocol we get a lot of characters that are 
>> forbidden in host names.
>> 
>> For example: all upper case letters, double width and circled letters.
>> 
>> This is quite a change from current usage where both upper 
>> and lower case is allowed in host names.
>
>They are not forbidden: they will get folded to something else. So you can
>still write and register your names with, say, U+00DC LATIN CAPITAL LETTER U
>WITH DIAERESIS and U+2462 CIRCLED DIGIT THREE. They can be used in your
>applications and by your users. They are just strictly euqivalent to U+00FC
>LATIN SAMLL LETTER U WITH DIAERESIS and U+0031 DIGIT ONE. Just like 'A' and
>'a' are strictly equivalent today in DNS.
>

But today the name service itself can handle both 'A' and 'a', and you
can register a name with 'A' in it. When nameprep is required to be
done before a name enters the name service, the name service cannot
itself handle the above characters. So in the name service they are
forbidden and cannot be returned from it.
So for the DNS service (which includes the DNS servers and the protocol)
the characters are forbidden.

   Dan




From owner-idn@ops.ietf.org  Thu Jul 26 15:04:20 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA04228
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 15:04:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PfXF-000OWf-00
	for idn-data@psg.com; Thu, 26 Jul 2001 00:26:17 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.31 #1)
	id 15PfXE-000OWZ-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 00:26:16 -0700
Received: (qmail 24554 invoked from network); 26 Jul 2001 14:45:00 -0000
Received: from chubby.internal.realnames.com (HELO heaven.internal.realnames.com) (10.1.5.39)
  by friendly.realnames.com with SMTP; 26 Jul 2001 14:45:00 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:3204]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <191780@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Thu, 26 Jul 2001 12:24:28 AM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2650.21)
	id <PJWH3ZJ1>; Thu, 26 Jul 2001 00:25:55 -0700
Message-ID: <B7233BD6980AD411875700508B5BD5D2011E9738@elporto.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: idn@ops.ietf.org
Subject: RE: [idn] Cherokee letters look like uppercase Latin letters
Date: Thu, 26 Jul 2001 00:25:55 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="KS_C_5601-1987"
Sender: owner-idn@ops.ietf.org
Precedence: bulk


> Do we need to allow Cherokee letters in IDN?

It would be quite bad to deny access to IDN to one population, yes! After
all, we're internationalizing DNS because some populations have been left
over initially and we want to fix that.

I find very interesting (and ironic) to see these suggestions about
removing characters whose glyphs may confuse some people. It is a similar
reasoning that led to the choice of the initial set of characters allowed
in DNS labels, and I am sure that in the world of then, complex scripts or
even exotic scripts would have been dismissed for fear of confusion for the
typical user. Are you really seriously suggesting to do the same mistake
again, but with different populations?!

YA



From owner-idn@ops.ietf.org  Thu Jul 26 15:04:22 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA04241
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 15:04:21 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Pexw-000M7l-00
	for idn-data@psg.com; Wed, 25 Jul 2001 23:49:48 -0700
Received: from mail07b.vwh1.net ([209.238.9.59])
	by psg.com with smtp (Exim 3.31 #1)
	id 15Pexv-000M7f-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 23:49:47 -0700
Received: from www.langoo.net (208.55.128.123)
	by mail07b.vwh1.net (RS ver 1.0.60s) with SMTP id 021480709;
	Thu, 26 Jul 2001 02:49:42 -0400 (EDT)
From: "Deven Kalra" <kalra@langoo.net>
To: <liana.ydisg@juno.com>
Cc: <phoffman@imc.org>, <Marc.Blanchet@viagenie.qc.ca>, <idn@ops.ietf.org>
Subject: RE: ace leaking (was: Re: [idn] Debunking the ACE myth)
Date: Wed, 25 Jul 2001 23:49:50 -0700
Message-ID: <EPEIKIAPPPCAHCJJKPFGIEODCIAA.kalra@langoo.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
In-Reply-To: <20010724.193210.-665585.0.liana.ydisg@juno.com>
X-Loop-Detect: 1
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

As my colleague, Gary Krall mentioned in an earlier post, would it not
be best to let a user/company determine their ascii version of a
multi-lingual
url. Depending on the culture, company policies, language etc, different
organizations will "asciify" their ML url differently. IMHO, it will be
unrealistic to expect that casual users will remember the language tag
for each url, especially in a multi-lingual country as India. Instead,
the creativity of the IDN users will generate some very interesting
and memorable ascii version of ML IDNs.

Deven Kalra
Langoo.com/Langoo.net

-----Original Message-----
From: owner-idn@ops.ietf.org [mailto:owner-idn@ops.ietf.org]On Behalf Of
liana.ydisg@juno.com
Sent: Tuesday, July 24, 2001 7:32 PM
To: kalra@langoo.net
Cc: phoffman@imc.org; Marc.Blanchet@viagenie.qc.ca; idn@ops.ietf.org
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth)


For each language, there is one language tag, so
hin-namaskar.com is different with guj-namaskar.com.
The tag provide over 17,000 different language labels for
the issue you addressed.

Liana






From owner-idn@ops.ietf.org  Thu Jul 26 15:04:23 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA04247
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 15:04:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PdXL-000GmT-00
	for idn-data@psg.com; Wed, 25 Jul 2001 22:18:15 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.31 #1)
	id 15PdXK-000GmN-00
	for idn@ops.ietf.org; Wed, 25 Jul 2001 22:18:14 -0700
Received: (qmail 17486 invoked from network); 26 Jul 2001 12:36:59 -0000
Received: from chubby.internal.realnames.com (HELO heaven.internal.realnames.com) (10.1.5.39)
  by friendly.realnames.com with SMTP; 26 Jul 2001 12:36:59 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:3390]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <189143@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Wed, 25 Jul 2001 10:16:31 PM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2650.21)
	id <PJWH3W1A>; Wed, 25 Jul 2001 22:17:59 -0700
Message-ID: <B7233BD6980AD411875700508B5BD5D2011E9734@elporto.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: idn@ops.ietf.org
Subject: RE: [idn] Debunking the UTF-8 myth
Date: Wed, 25 Jul 2001 22:17:58 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

A technical difference, I think, would be that according to UTR #17
(http://www.unicode.org/unicode/reports/tr17/) an ACE is more a transfer
encoding syntax (TES) (section 7 of the above document) than a character
encoding scheme (CES) like UTF-8 is (UTF-8 is also a CEF). But then I always
get confused when I think too much about all of these :) and the fact that
ACE starts from UTF-16 only doesn't help. I'm sure Mark Davis could
confirm/infirm that theory.

YA



From owner-idn@ops.ietf.org  Thu Jul 26 16:15:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA09149
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 16:15:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PrAl-000Heb-00
	for idn-data@psg.com; Thu, 26 Jul 2001 12:51:51 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PrAk-000HeV-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 12:51:50 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f6QJncN07409;
	Thu, 26 Jul 2001 15:49:38 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107261949.f6QJncN07409@nic-naa.net>
To: "Soobok Lee" <lsb@postel.co.kr>
cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] how to solve idn security problem : Re: Morning Humor ..... 
In-Reply-To: Your message of "Fri, 27 Jul 2001 02:54:32 +0900."
             <024701c115fc$06772ce0$ed1bd9d2@postel.co.kr> 
Date: Thu, 26 Jul 2001 15:49:38 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Soobok,

... [katakana 'ka(U+30AB)' and chinese letter 'power(U+529B)'
> Likewise, normalizing  minorities' scripts in IDN into others is also
> almost impossible. Your humor proved that just now.

This is why [30] (which vanished silently from the requirements) is of such
interest -- universal scope is so attractive, until some specific cases are
considered. I know what equivalences to make for these:

	U+0222 LATIN CAPITAL LETTER OU
	U+0223 LATIN SMALL LETTER OU

I don't expect anyone else to. Is "8abenaki" "wabenaki" and "ouabenaki" and ...

Glad you enjoyed my note!

Eric



From owner-idn@ops.ietf.org  Thu Jul 26 17:02:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA11985
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 17:02:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Prpg-000KFh-00
	for idn-data@psg.com; Thu, 26 Jul 2001 13:34:08 -0700
Received: from mail-blue.research.att.com ([135.207.30.102])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Prpf-000KFb-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 13:34:07 -0700
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id B94964CF03; Thu, 26 Jul 2001 16:34:06 -0400 (EDT)
Received: from wave-172.research.att.com (wave-172.research.att.com [135.207.10.172])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id QAA12522;
	Thu, 26 Jul 2001 16:34:05 -0400 (EDT)
Date: Thu, 26 Jul 2001 16:25:05 -0400
From: John C Klensin <klensin@research.att.com>
To: Soobok Lee <lsb@postel.co.kr>
Cc: "James Seng/Personal" <James@Seng.cc>, idn@ops.ietf.org
Subject: Re: [idn] Re: [idn-nameprep] Arabic hyphen-like glyph
Message-ID: <25153036.996164705@wave-172.research.att.com>
In-Reply-To: <017e01c115c0$dad9de60$ed1bd9d2@postel.co.kr>
References:  <017e01c115c0$dad9de60$ed1bd9d2@postel.co.kr>
X-Mailer: Mulberry/2.1.0b2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Thursday, 26 July, 2001 19:50 +0900 Soobok Lee
<lsb@postel.co.kr> wrote:

> Using hyphen in place of NWNJ in Arabic multi-word domains
> may cause confusion because arabic script already contains
> hyphen-like letters already. that's the point.
> That's not related directly to nameprep, but to IDN security.
> 
> I hope those small ratholes may not become security holes in
> IDN.

It seems to me, regardless of other IDN work and its outcomes,
that an analysis that identifies these "small ratholes" in
matching and character identification and their security
implications would be a very useful contribution.  Its text might
ultimately become part of something else, or it might be
published separately.  And I would hope that the WG Co-chairs
would not impose an "interest level" requirement on drafts or
components of such an analysis, treating it instead as part of
the general requirement on the WG to produce a "security
considerations" analysis of any proposed standards-track
materials it produces.

    john




From owner-idn@ops.ietf.org  Thu Jul 26 18:17:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA17439
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 18:17:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Pt7B-000PGl-00
	for idn-data@psg.com; Thu, 26 Jul 2001 14:56:17 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Pt7A-000PGe-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 14:56:16 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15Pt79-0005Rn-00; Thu, 26 Jul 2001 14:56:15 -0700
Date: Thu, 26 Jul 2001 21:56:15 +0000
To: idn@ops.ietf.org
Subject: [idn] names returned by DNS are rarely seen
Message-ID: <20010726215615.B20626@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <024701c115fc$06772ce0$ed1bd9d2@postel.co.kr>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Soobok Lee <lsb@postel.co.kr> wrote:

> The guidelines for registries should not allow Capital 'A'-like
> letters in the registered host name in authoriative dns servers in
> order to secure IDN from ambiguities.

This is the exact opposite of the point than Dan Oscarsson has asserted
many times.  If I understand him correctly, he argues that it's
important for DNS to be able to return names in the form the registrant
intended (mixed case, for example), because that's what DNS is currently
capable of and that's what people will demand.

You seem to be arguing that it's important for DNS not to return names
in visually ambiguous forms (for example, always return lowercase alpha
rather than uppercase alpha).

I don't think enabling/forbidding certain equivalent forms in DNS
responses is going to make much difference one way or the other, because
names returned from DNS are very rarely seen by most users.

Consider the domain cs.berkeley.edu.  That's how it always
appears in the From: field of my messages.  When you paste
http://www.cs.berkeley.edu/~amc/ into your browser, or follow a link to
it, that's how the URL appears in the Location field.  If instead you
followed a link to http://WWW.CS.BERKELEY.EDU/~amc/, then that's how it
would appear.  Actually neither of those forms is ever returned from
DNS, only "CS.Berkeley.EDU" is ever returned.  But you won't see it in
that form unless you go digging for it in Received: header fields or log
files or other places that most users almost never see.

Regardless of what forms are possible/forbidden in DNS responses, people
will still be able to present the names in whatever equivalent forms
they like, for better or worse, to trick people or to make the name more
readable.

AMC



From owner-idn@ops.ietf.org  Thu Jul 26 18:34:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA18378
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 18:34:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PtTB-0000mV-00
	for idn-data@psg.com; Thu, 26 Jul 2001 15:19:01 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PtTA-0000mO-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 15:19:00 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id AAA06561;
	Fri, 27 Jul 2001 00:18:42 +0200 (MET DST)
Date: Fri, 27 Jul 2001 00:12:08 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: "James Seng/Personal" <James@seng.cc>, Soobok Lee <lsb@postel.co.kr>,
        idn@ops.ietf.org, idn-nameprep@viagenie.qc.ca
Subject: [idn] Re: [idn-nameprep] Arabic hyphen-like glyph
Message-ID: <1734964.996192728@localhost>
In-Reply-To: <01f201c115b9$143c1720$dd00a8c0@jamessonyvaio>
References: <4.2.0.58.J.20010725181455.0346d600@sh.w3.mag.keio.ac.jp>
 <4.2.0.58.J.20010726102046.05fa8100@sh.w3.mag.keio.ac.jp>
 <008d01c11581$5e4a0bc0$ec1bd9d2@temp>
 <01f201c115b9$143c1720$dd00a8c0@jamessonyvaio>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-07-26 17.55 +0800 "James Seng/Personal" <James@seng.cc> wrote:

> If there is intention to talk about "folding look-alive characters" then
> please write an I-D, get your 7 core interest then come back to the wg.
> Personally, I do not suggest anyone going into this rathole...

Before you do this, think about what this means:

- In the IETF, we have been extremely careful NOT talking about
  individual characters, codepoints or such, but instead all the time
  referenced other standards bodies when talking about such details.
- In various protocols, we have been pointing to different bodies,
  depending on mood, time of day or even technical merits(!).

Now, IF you are unhappy with nameprep of today, I want you to be extremely
clear whether:

[A] You think the Unicode tables, unification rules etc are wrong, and you
want to change those and instead do the work in the IETF (basically, scrap
what is defined in the Unicode Consortium or ISO because you belive IETF
can do a better job).

[B] You think a different organization than Unicode Consortium is better to
reference than the Unicode Technical Reports (and we still will not do
character by character definitions in the IETF).

Is it [A] or [B] you are after?

If [A], why would IETF be better on this, and don't you think yet another
standard body doing character things would be bad for the world?

If [B], which body are you thinking of?


My point is, if you are unhappy with work done by an organization which we
reference we in the IETF should either bring the issues over there, or
reference some other organization. And, we need to make up our mind on
which one of these two paths we want to follow. Doing both is often a bad
idea (and a waste of time and resources).

     paf




From owner-idn@ops.ietf.org  Thu Jul 26 18:34:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA18387
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 18:34:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PtSx-0000lp-00
	for idn-data@psg.com; Thu, 26 Jul 2001 15:18:47 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PtSv-0000lM-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 15:18:45 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id AAA06558;
	Fri, 27 Jul 2001 00:18:39 +0200 (MET DST)
Date: Fri, 27 Jul 2001 00:04:40 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Soobok Lee <lsb@postel.co.kr>, idn@ops.ietf.org
Subject: Re: [idn] Cherokee letters look like uppercase Latin letters
Message-ID: <1708113.996192280@localhost>
In-Reply-To: <013601c115af$1f3f8080$ed1bd9d2@postel.co.kr>
References: <B7233BD6980AD411875700508B5BD5D2011E9738@elporto.internal.realna
 mes.com> <013601c115af$1f3f8080$ed1bd9d2@postel.co.kr>
X-Mailer: Mulberry/2.1.0b2 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-07-26 17.44 +0900 Soobok Lee <lsb@postel.co.kr> wrote:

> For future script additions to UCS ,we have no nameprep rules now.
> As long as we should enforce current NAMEPREP rules, we are also
> prohibiting future script additions from being used in IDN that will have
> to be nameprepped by the future versions of ACE and NAMEPREP rules.

No, the versioning issues are explicitly described in the nameprep
document. See how to take care of versioning and unassigned codepoints.

It might be wrong, but we have some text talking about it.

  paf




From owner-idn@ops.ietf.org  Thu Jul 26 19:31:41 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22207
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 19:31:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Pu0R-0002tV-00
	for idn-data@psg.com; Thu, 26 Jul 2001 15:53:23 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Pu0Q-0002tP-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 15:53:22 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH1CgsnopVcwqbIi9Cos2QE7t5lsG58YW2g==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GBBDXKXF; Thu, 26 Jul 2001 18:52:50 EDT
To: lsb@postel.co.kr
Cc: idn@ops.ietf.org, idn-nameprep@viagenie.qc.ca
Date: Thu, 26 Jul 2001 15:59:12 -0700
Subject: Re: [idn] Arabic hyphen-like glyph
Message-ID: <20010726.160902.-742527.0.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.11
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-7,9-69
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

It seems to me  Arabic glyph U+0640 (Arabic TATWEEL)
	 looks like Latin hyphen(-). is used to stretch characters,
 and  Arabic FULLSTOP U+06D4  looks like Latin 'underline' (or 'hyphen' )
  is used as period.  Both are not phonetic characters, so they are not
conflict with a word separator 'hypen'.
 
Liana

On Thu, 26 Jul 2001 12:16:31 +0900 "Soobok Lee" <lsb@postel.co.kr>
writes:
> Arabic glyph U+0640 (Arabic TATWEEL) looks like Latin hyphen(-).
> 
> Arabic FULLSTOP U+06D4  looks like Latin 'underline' (or 'hyphen' ).
> 
> Using hyphen instead of punctuation char NWNJ(U+200C,No-width No 
> joiner)
>  may not help but cause confusion to native-Arabic people.
> 
> 
> Soobok Lee, lsb@postel.co.kr
> 
> ----- Original Message -----
> From: "Martin Duerst" <duerst@w3.org>
> To: "Roozbeh Pournader" <roozbeh@sharif.edu>
> Cc: "John C Klensin" <klensin@jck.com>; "Dan Oscarsson" 
> <Dan.Oscarsson@trab.se>;
> <idn@ops.ietf.org>; <idn-nameprep@viagenie.qc.ca>
> Sent: Thursday, July 26, 2001 10:25 AM
> Subject: [idn] ZWNJ (was: Re: Just send UTF-8 with nameprep (was: 
> RE:
> [idn]Reality Check))
> 
> 
> > At 19:33 01/07/25 +0430, Roozbeh Pournader wrote:
> > >On Wed, 25 Jul 2001, Martin Duerst wrote:
> > >
> > > > I don't want to disagree with your conclusion, but I'm not
> > > > sure about the premise (that we need the original spelling),
> > > > so I didn't get into the details of what would follow.
> > >
> > >We may need original spelling, for example if we decide that we 
> need to
> > >stop Arabic letters from joining, by using a ZWNJ between them 
> (since a
> > >space is not available). Multiword Arabic domain names will be 
> unreadable
> > >if the words join. But since ZNWJ is stripped at nameprep, we 
> will
> > >sometimes need to get to the original. You get the idea.
> >
> > Hello Roozbeh,
> >
> > Many thanks for your comment. As far as I remember, currently ZNWJ 
> is
> > dropped by nameprep without complaining. I think that if that 
> leads to
> > problems as you describe above, we should very carefully reexamine
> > this decision. I have already told the nameprep design team that
> > I think that this should be moved to 'disallowed' to avoid 
> surprises
> > like the above. But I'm not sure moving it to 'disallowed' would
> > solve all problems (assuming that the hyphen is used for 
> concatenating
> > words).
> >
> > Regards,   Martin.
> >
> >
> 
> 



From owner-idn@ops.ietf.org  Thu Jul 26 19:31:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22219
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 19:31:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Pu2m-00031o-00
	for idn-data@psg.com; Thu, 26 Jul 2001 15:55:48 -0700
Received: from fm200.sybase.com ([192.138.151.122])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Pu2l-00031D-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 15:55:47 -0700
Received: from smtp2.sybase.com (sybgate2.sybase.com [130.214.88.21])
	by fm200.sybase.com  with ESMTP id PAA21390
	for <idn@ops.ietf.org>; Thu, 26 Jul 2001 15:55:42 -0700 (PDT)
Received: from olympus.sybase.com (localhost [127.0.0.1])
	by smtp2.sybase.com  with ESMTP id PAA28589
	for <idn@ops.ietf.org>; Thu, 26 Jul 2001 15:55:15 -0700 (PDT)
Received: from birdie.sybase.com by olympus.sybase.com (8.8.8+Sun/SMI-SVR4/SybEC3.5)
	id PAA08730; Thu, 26 Jul 2001 15:55:13 -0700 (PDT)
Received: (from kenw@localhost)
	by birdie.sybase.com (8.8.8+Sun/8.8.8) id PAA18164;
	Thu, 26 Jul 2001 15:55:13 -0700 (PDT)
Date: Thu, 26 Jul 2001 15:55:13 -0700 (PDT)
From: Kenneth Whistler <kenw@sybase.com>
Message-Id: <200107262255.PAA18164@birdie.sybase.com>
To: idn@ops.ietf.org
Subject: Re: [idn] names returned by DNS are rarely seen
Cc: kenw@sybase.com
X-Sun-Charset: US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

AMC wrote:

> 
> Regardless of what forms are possible/forbidden in DNS responses, people
> will still be able to present the names in whatever equivalent forms
> they like, for better or worse, to trick people or to make the name more
> readable.

I agree.

WWW.LOOT.COM takes you to an eBay wannabe buying/selling site.

WWW.L00T.COM is also a registered domain, and goes to an EasySpace client.

Coincidence? Probably not. This kind of stuff is done all the time,
and it doesn't depend on glyph lookalikes to create confusion. Similar
spellings, semantic replacements, or substitution of plausible TLD's
can all do the job. I don't see how moving to Unicode for IDN's makes
the problem significantly different, except that it exposes DNS
implementers to a much wider variety of characters that could be visually
confused for each other.

I don't think the IDN WG concerns with nameprep should extend beyond
ensuring that the output of nameprep doesn't produce any characters
that interfere with the formally reserved characters for URL syntax
and the like. Beyond that, just let the Unicode equivalence tables
take care of things.

--Ken

> 
> AMC
> 
> 




From owner-idn@ops.ietf.org  Thu Jul 26 20:40:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA26216
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 20:40:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PvJt-0008D0-00
	for idn-data@psg.com; Thu, 26 Jul 2001 17:17:33 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PvJt-0008Cu-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 17:17:33 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH1CgsnopVcwqsAdLXUdaLts8ovINn07OlQ==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GBBJSHLW; Thu, 26 Jul 2001 20:17:26 EDT
To: kalra@langoo.net
Cc: liana.ydisg@juno.com, phoffman@imc.org, Marc.Blanchet@viagenie.qc.ca,
        idn@ops.ietf.org
Date: Thu, 26 Jul 2001 17:32:07 -0700
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth)
Message-ID: <20010726.173331.-742527.3.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.11
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-5,7-44
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I think this is a case of two different hostname, one is choosen
by the user, the other is given by T-ACE.  The latter is mainly
for non-native speakers, and can be hitten from the natives.

Liana

On Wed, 25 Jul 2001 23:49:50 -0700 "Deven Kalra" <kalra@langoo.net>
writes:
> As my colleague, Gary Krall mentioned in an earlier post, would it 
> not
> be best to let a user/company determine their ascii version of a
> multi-lingual
> url. Depending on the culture, company policies, language etc, 
> different
> organizations will "asciify" their ML url differently. IMHO, it will 
> be
> unrealistic to expect that casual users will remember the language 
> tag
> for each url, especially in a multi-lingual country as India. 
> Instead,
> the creativity of the IDN users will generate some very interesting
> and memorable ascii version of ML IDNs.
> 
> Deven Kalra
> Langoo.com/Langoo.net
> 
> -----Original Message-----
> From: owner-idn@ops.ietf.org [mailto:owner-idn@ops.ietf.org]On 
> Behalf Of
> liana.ydisg@juno.com
> Sent: Tuesday, July 24, 2001 7:32 PM
> To: kalra@langoo.net
> Cc: phoffman@imc.org; Marc.Blanchet@viagenie.qc.ca; idn@ops.ietf.org
> Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth)
> 
> 
> For each language, there is one language tag, so
> hin-namaskar.com is different with guj-namaskar.com.
> The tag provide over 17,000 different language labels for
> the issue you addressed.
> 
> Liana
> 
> 
> 



From owner-idn@ops.ietf.org  Thu Jul 26 20:40:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA26222
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 20:40:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PvL4-0008K1-00
	for idn-data@psg.com; Thu, 26 Jul 2001 17:18:46 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PvL3-0008Jh-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 17:18:45 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH1CgsnopVcwqa98TWCeMegVAzOWmvpbtKg==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GBBJSHM4; Thu, 26 Jul 2001 20:17:26 EDT
To: ben@cc-www.com
Cc: idn@ops.ietf.org
Date: Thu, 26 Jul 2001 17:33:24 -0700
Subject: [idn] Fw: Autoreply from Internet Draft Submission Manager
Message-ID: <20010726.173331.-742527.4.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.11
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,  Ben and all:

The following is the message I got from IETF.  So, I stop to work 
and wait for Aug. 14 to resummit my I-D and the other two that
I planned to summit shortly after.

If it is not too late to summit a new I-D, please send me a 
e-mail for the WG's consideration of draft-liana-idn-step-1
titled as "StepCode- A Romanized Mnemonic IDN Encoding".

Thank you for your support.

Liana

 
--------- Forwarded message ----------
From: ietfauto@ietf.org (Internet Draft Submission Manager)
To: liana.ydisg@juno.com
Date: Sun, 22 Jul 2001 20:35:51 -0400 (EDT)
Subject: Autoreply from Internet Draft Submission Manager
Message-ID: <200107230035.UAA15422@ietf.org>
References: <20010722.175204.-810189.0.liana.ydisg@juno.com>

Greetings,

We are sorry, but the cut-off for Internet-Draft submissions was Friday,
July 20, 2001 at 5pm ET. Your submission will not be retained (i.e. you
need to resubmit) after August 14th.

If you receive this announcement, your submission will NOT be processed.

Any submissions received prior to August 14, 2001 will not be retained;
they must be resubmitted. Internet-Draft submissions received on or after
August 14 will be processed. However, Internet-Draft announcements will
not be sent until after the meeting concludes.


Thank you for your understanding.


IETF Secretariat



From owner-idn@ops.ietf.org  Thu Jul 26 20:47:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA26470
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 20:47:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PvC2-0007mc-00
	for idn-data@psg.com; Thu, 26 Jul 2001 17:09:26 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PvC1-0007mN-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 17:09:25 -0700
Received: from bbthead.dcrocker.net ([200.37.188.23])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id RAA21262;
	Thu, 26 Jul 2001 17:09:18 -0700
Message-Id: <5.1.0.14.2.20010726185903.0315f3d0@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 26 Jul 2001 19:00:12 -0500
To: "Gary Krall" <gary@langoo.net>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: ace leaking (was: Re: [idn] Debunking the ACE myth)
Cc: <idn@ops.ietf.org>
In-Reply-To: <004301c11570$1e551f20$67a8a8c0@siteops>
References: <5.1.0.14.1.20010724120919.0216e138@mail.viagenie.qc.ca>
 <200107241327.JAA09700@astro.cs.utk.edu>
 <200107241327.JAA09700@astro.cs.utk.edu>
 <5.1.0.14.1.20010724120919.0216e138@mail.viagenie.qc.ca>
 <5.1.0.14.2.20010725183744.044caaa0@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 08:12 PM 7/25/2001, Gary Krall wrote:
>Patrik's proposal, if I understand it, of letting users with use the ACE
>representation does provide an option for  ASCII "only" users.  But, as
>Patrik points out is quite "ugly" given the current "bq--xxxx" structure.

Patrik was not making a proposal, simply because the ascii version of the 
iDN string will exist and we cannot control how people spread it around and 
use it.

On the other hand, yes, there will be people who are entirely satisfied 
with that as their only ascii version of domain name.

d/


----------
Dave Crocker  <mailto:dcrocker@brandenburg.com>
Brandenburg InternetWorking  <http://www.brandenburg.com>
tel +1.408.246.8253;  fax +1.408.273.6464




From owner-idn@ops.ietf.org  Thu Jul 26 21:00:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA26946
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 21:00:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Pvth-000AkZ-00
	for idn-data@psg.com; Thu, 26 Jul 2001 17:54:33 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Pvth-000AkP-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 17:54:33 -0700
Received: from enoshima (e147197.ppp.asahi-net.or.jp [211.13.147.197])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id JAA25854;
	Fri, 27 Jul 2001 09:54:02 +0900 (JST)
Message-Id: <4.2.0.58.J.20010726235516.05bb7100@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 27 Jul 2001 00:01:09 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>,
        <idn-nameprep@viagenie.qc.ca>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Arabic hyphen-like glyph
In-Reply-To: <008d01c11581$5e4a0bc0$ec1bd9d2@temp>
References: <4.2.0.58.J.20010725181455.0346d600@sh.w3.mag.keio.ac.jp>
 <4.2.0.58.J.20010726102046.05fa8100@sh.w3.mag.keio.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 12:16 01/07/26 +0900, Soobok Lee wrote:
>Arabic glyph U+0640 (Arabic TATWEEL) looks like Latin hyphen(-).
>
>Arabic FULLSTOP U+06D4  looks like Latin 'underline' (or 'hyphen' ).
>
>Using hyphen instead of punctuation char NWNJ(U+200C,No-width No joiner)
>  may not help but cause confusion to native-Arabic people.

Hello Soobok,

Glyphs in Arabic are not isolated. The hyphen would be isolated,
but tatweel/kashida is always connected. The hyphen would be higher
than both tatweel and Arabic full stop (used in Urdu).

So rather than just looking at the glyph charts, please get an
understanding of how Arabic formatting works before trying to
comment on it.

Regards,   Martin.



From owner-idn@ops.ietf.org  Thu Jul 26 21:54:43 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA29760
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 21:54:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PwUM-000Ccb-00
	for idn-data@psg.com; Thu, 26 Jul 2001 18:32:26 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.31 #1)
	id 15PwUL-000CcV-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 18:32:25 -0700
Received: (qmail 16055 invoked from network); 27 Jul 2001 08:51:03 -0000
Received: from chubby.internal.realnames.com (HELO heaven.internal.realnames.com) (10.1.5.39)
  by friendly.realnames.com with SMTP; 27 Jul 2001 08:51:03 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:2795]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <217364@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Thu, 26 Jul 2001 6:30:15 PM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2650.21)
	id <PJWHPXDP>; Thu, 26 Jul 2001 18:31:43 -0700
Message-ID: <B7233BD6980AD411875700508B5BD5D2011E975B@elporto.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: idn@ops.ietf.org
Subject: RE: [idn] Forbidden characters
Date: Thu, 26 Jul 2001 18:31:41 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> >They are not forbidden: they will get folded to something 
> else. So you 
> >can still write and register your names with, say, U+00DC 
> LATIN CAPITAL 
> >LETTER U WITH DIAERESIS and U+2462 CIRCLED DIGIT THREE. They can be 
> >used in your applications and by your users. They are just strictly 
> >euqivalent to U+00FC LATIN SAMLL LETTER U WITH DIAERESIS and U+0031 
> >DIGIT ONE. Just like 'A' and 'a' are strictly equivalent 
> today in DNS.
> >
> 
> But today the name service itself can handle both 'A' and 
> 'a', and you can register a name with 'A' in it. When 
> nameprep is required to be done before a name enters the name 
> service, the name service cannot itself handle the above 
> characters. So in the name service they are forbidden and 
> cannot be returned from it. So for the DNS service (which 
> includes the DNS servers and the protocol) the characters are 
> forbidden.

Again, they are not forbidden. They can be used as input. What is not clear
(and controversial here) is whether you will ever get them back or not when
you decode the ACE. Some ACE preserve case. But normalization can't be
undone, so as you said, the name service cannot return them. We won't get
about adding a new RR for that here, but while I am for preserving case but
may live without it (after all, DNS names are not pretty, if I want
prettiness I'll use a layer above it), Roozbeh's comments about Arabic names
becoming different to their reader because of spontaneous joining of glyphs
certainly may spark some thinking.

YA



From owner-idn@ops.ietf.org  Thu Jul 26 22:29:43 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA00950
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 22:29:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Pwzq-000EBI-00
	for idn-data@psg.com; Thu, 26 Jul 2001 19:04:58 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Pwzp-000EBB-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 19:04:58 -0700
Received: from zetnet.co.uk (man-s108.dialup.zetnet.co.uk [194.247.41.235])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6R24nR12077
        for <idn@ops.ietf.org>; Fri, 27 Jul 2001 03:04:49 +0100
Message-ID: <3B60BE9B.6E7266ED@zetnet.co.uk>
Date: Fri, 27 Jul 2001 02:06:35 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: idn@ops.ietf.org
Subject: [idn] Common-case optimization of nameprep (was Debunking the ACE myth)
References: <20010724065812.D8846@arwen.cs.berkeley.edu> <3B5DC4AA.AA422763@zetnet.co.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

David Hopwood wrote:
> "Adam M. Costello" wrote:
> > I doubt that checking whether a name is nameprep'd is much cheaper than
> > performing nameprep on it.
> 
> It is, actually: see UAX #15 Annexes 3 and 8, at
> http://www.unicode.org/unicode/reports/tr15/
> 
> (The code in Annex 8 would need to be modified to also check for lowercase.

Correction: it is slightly more complicated than just checking for lowercase
(but this doesn't change the efficiency).

Let getCanonicalClassX(ch) be the Canonical Combining Class of ch, except that
it returns a negative value if ch \in X. The set X is defined as the union of:

 - characters that are mapped to something else (or mapped out) by the nameprep
   mapping step,
 - characters for which the NFC flag in DerivedNormalizationProperties.txt
   is either NFC_NO or NFC_MAYBE,
 - characters that are prohibited in the output of nameprep (i.e. category D).

[X is a superset of MN union D. It would be interesting to see what kind
of characters, if any, are in X \ (MN union D); I'll try to work that out.]

Then the Java-like pseudocode would look like this:

public String nameprep(String source) {
    short lastCanonicalClass = 0;

    for (int i = 0; i < source.length(); ++i) {
        char ch = source.charAt(i);
        short canonicalClass = getCanonicalClassX(ch);
        if (lastCanonicalClass > canonicalClass && canonicalClass != 0) {
            return fullNameprep(source, i);
        }
        lastCanonicalClass = canonicalClass;
    }
    // The string was already nameprepped, and has no disallowed characters.
    return string;
}

public String fullNameprep(String source, int i) {
    // Full nameprep algorithm (including checking for disallowed characters),
    // where the first character that may need mapping is at index i.
}

> It also has to be checked that the name is a valid UTF-8 encoding.)

This can be done in the same loop.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO2C+eDkCAxeYt5gVAQEU/QgAj47s6KYVxnzTI2DPrfK6dyv3pGh93o9o
y5y7OJIrSyJMq2bsAZZ0vGw+NF+ysQilY+glcR3ZsZ3xEQuh9lW3Rc0P8AvPEHLu
6OB2OwsWPm8LIxg1zuKokOwf11nSGZnniYOwntkNUVgSEC0PeQ0Ry8B4vAL4dgGl
Xu5Emk5DUw0mOLZ1BTJ/5XuyTv55xTpnCNY4/BMTWW9hD+X9BX/XNCe9H2zWLBTw
/m4eGhyulPPQwO2eF80Xu3HDSLaslSHO/upnAcfSz4jzpC8tOeeN19+frcZ4PTYF
S8YBodfWhZYOiD3W80yxXZteRcCFCkj4I/OXaAqyBQdLFn9M4JWpSg==
=rlhv
-----END PGP SIGNATURE-----




From owner-idn@ops.ietf.org  Thu Jul 26 22:36:28 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA02138
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 22:36:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Px1Z-000EGl-00
	for idn-data@psg.com; Thu, 26 Jul 2001 19:06:45 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Px1Y-000EGF-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 19:06:44 -0700
Received: from zetnet.co.uk (man-s108.dialup.zetnet.co.uk [194.247.41.235])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6R24iR12067;
	Fri, 27 Jul 2001 03:04:44 +0100
Message-ID: <3B609B35.B03F2276@zetnet.co.uk>
Date: Thu, 26 Jul 2001 23:35:33 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: Dan Oscarsson <Dan.Oscarsson@trab.se>, idn@ops.ietf.org
Subject: Re: [idn] Forbidden characters
References: <200107260823.KAA00949@valinor.malmo.trab.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

Dan Oscarsson wrote:
> Yves Arrouye <yves@realnames.com> wrote:
> >Dan Oscarsson wrote:
> >> If we define that nameprep must be done before names are sent
> >> over the DNS protocol we get a lot of characters that are
> >> forbidden in host names.
> >>
> >> For example: all upper case letters, double width and circled letters.
> >>
> >> This is quite a change from current usage where both upper
> >> and lower case is allowed in host names.
> >
> >They are not forbidden: they will get folded to something else. So you can
> >still write and register your names with, say, U+00DC LATIN CAPITAL LETTER U
> >WITH DIAERESIS and U+2462 CIRCLED DIGIT THREE. They can be used in your
> >applications and by your users. They are just strictly euqivalent to U+00FC
> >LATIN SAMLL LETTER U WITH DIAERESIS and [U+0033 DIGIT THREE]. Just like 'A'
> >and 'a' are strictly equivalent today in DNS.
> 
> But today the name service itself can handle both 'A' and 'a', and you
> can register a name with 'A' in it. When nameprep is required to be
> done before a name enters the name service, the name service cannot
> itself handle the above characters. So in the name service they are
> forbidden and cannot be returned from it.

So what? Why is it a problem if uppercase non-ASCII characters (and various
other non-NFKC-normalised characters) are not returned in reverse lookups?
End-users see the results of a reverse lookup quite infrequently, and when
they do, I doubt that they care whether it has uppercase characters or not.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO2CbJDkCAxeYt5gVAQFDKggAlEErZa0J4/qAw1XSYRAMDg1pp8rQX9dk
aaaXq6jqbgm0r6fpnd7l0eQ1JOojl+bXYttnwVY+0dcWXVRYbpNmHrje1als6T5i
SguKwcV+gj5jtCZgirCZD83dA7gBtkaJYnU2+w3HwnHR9qoboCHL5+8W5otE4NMQ
tPQd1+1QzW8JzuvNCW+8cFdJ8O+Y5ooi9aag8zZ10EayXb2L1NvI5AZ9L+EwVden
/ThIFeKgk/s54GVIv7unSlwNhYIVchAvnkL0kDzSzqPBtA6ZA42cENh6mVDsliNI
mSrzjGNitjQZv6N4H8MdXFg+758T83H6GDnqGQlK+ZYvxtOCFiv63g==
=QZTY
-----END PGP SIGNATURE-----





From owner-idn@ops.ietf.org  Thu Jul 26 22:37:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA02175
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 22:37:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PxCN-000Enz-00
	for idn-data@psg.com; Thu, 26 Jul 2001 19:17:55 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PxCM-000Ent-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 19:17:54 -0700
Received: from soobok ([210.217.27.237] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id LAA14256;
	Fri, 27 Jul 2001 11:17:47 +0900
Message-ID: <001e01c11643$2da39640$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <4.2.0.58.J.20010725181455.0346d600@sh.w3.mag.keio.ac.jp> <4.2.0.58.J.20010726102046.05fa8100@sh.w3.mag.keio.ac.jp> <4.2.0.58.J.20010726235516.05bb7100@sh.w3.mag.keio.ac.jp>
Subject: Re: [idn] Arabic hyphen-like glyph
Date: Fri, 27 Jul 2001 11:23:52 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>;
<idn-nameprep@viagenie.qc.ca>
Sent: Friday, July 27, 2001 12:01 AM
Subject: Re: [idn] Arabic hyphen-like glyph


> At 12:16 01/07/26 +0900, Soobok Lee wrote:
> >Arabic glyph U+0640 (Arabic TATWEEL) looks like Latin hyphen(-).
> >
> >Arabic FULLSTOP U+06D4  looks like Latin 'underline' (or 'hyphen' ).
> >
> >Using hyphen instead of punctuation char NWNJ(U+200C,No-width No joiner)
> >  may not help but cause confusion to native-Arabic people.
>
> Hello Soobok,
>
> Glyphs in Arabic are not isolated. The hyphen would be isolated,
> but tatweel/kashida is always connected. The hyphen would be higher
> than both tatweel and Arabic full stop (used in Urdu).
>

Your are correct. the hyphen is slightly higher than the arabic
script baseline.
BTW, when a hyphen is put between two arabic words,
the hyphen look disconnected from the right word, but looks
connected to the left word in cases with some arabic leading consonants.
I am not sure that problem come from the used arabic font.

> So rather than just looking at the glyph charts, please get an
> understanding of how Arabic formatting works before trying to
> comment on it.

Anyway, thanks for your corrections.

Regards, Soobok

>
> Regards,   Martin.
>




From owner-idn@ops.ietf.org  Thu Jul 26 22:37:41 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA02198
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 22:37:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Px6J-000ETR-00
	for idn-data@psg.com; Thu, 26 Jul 2001 19:11:39 -0700
Received: from drugs.dv.isc.org ([130.155.191.236])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Px6I-000ESd-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 19:11:38 -0700
Received: from nominum.com (localhost.dv.isc.org [127.0.0.1])
	by drugs.dv.isc.org (8.11.3/8.11.2) with ESMTP id f6R2BDu48396;
	Fri, 27 Jul 2001 12:11:21 +1000 (EST)
	(envelope-from marka@nominum.com)
Message-Id: <200107270211.f6R2BDu48396@drugs.dv.isc.org>
To: Yves Arrouye <yves@realnames.com>
Cc: idn@ops.ietf.org
From: Mark.Andrews@nominum.com
Subject: Re: [idn] Forbidden characters 
In-reply-to: Your message of "Thu, 26 Jul 2001 18:31:41 MST."
             <B7233BD6980AD411875700508B5BD5D2011E975B@elporto.internal.realnames.com> 
Date: Fri, 27 Jul 2001 12:11:13 +1000
Sender: owner-idn@ops.ietf.org
Precedence: bulk


> Again, they are not forbidden. They can be used as input. What is not clear
> (and controversial here) is whether you will ever get them back or not when
> you decode the ACE. Some ACE preserve case. But normalization can't be
> undone, so as you said, the name service cannot return them. We won't get
> about adding a new RR for that here, but while I am for preserving case but
> may live without it (after all, DNS names are not pretty, if I want
> prettiness I'll use a layer above it), Roozbeh's comments about Arabic names
> becoming different to their reader because of spontaneous joining of glyphs
> certainly may spark some thinking.
> 
> YA
> 
	We have the same problem in English today.

	Say I had a store called "To Get Her Gifts".  Smashing the
	word together to get a domain name might not be what you
	what, e.g. togethergifts.com.  Especially if next door is
	"Together Gifts".

	There are also plenty of cases where a made up word in one
	language turns out to be a real word in a different language.

	You need to think before you register / create a domain name,
	not just run on automatic pilot.

	Mark
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@nominum.com



From owner-idn@ops.ietf.org  Thu Jul 26 23:24:23 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA04143
	for <idn-archive@lists.ietf.org>; Thu, 26 Jul 2001 23:24:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15PxxO-000HCb-00
	for idn-data@psg.com; Thu, 26 Jul 2001 20:06:30 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15PxxN-000HCV-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 20:06:29 -0700
Received: from zetnet.co.uk (man-s108.dialup.zetnet.co.uk [194.247.41.235])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6R36NR16858
        for <idn@ops.ietf.org>; Fri, 27 Jul 2001 04:06:26 +0100
Message-ID: <3B60CE2C.FAAA76C9@zetnet.co.uk>
Date: Fri, 27 Jul 2001 03:13:00 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: idn@ops.ietf.org
Subject: Re: [idn] Common-case optimization of nameprep - correction
References: <20010724065812.D8846@arwen.cs.berkeley.edu> <3B5DC4AA.AA422763@zetnet.co.uk> <3B60BE9B.6E7266ED@zetnet.co.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

I wrote:
> Let getCanonicalClassX(ch) be the Canonical Combining Class of ch, except that
> it returns a negative value if ch \in X. The set X is defined as the union of:
> 
>  - characters that are mapped to something else (or mapped out) by the nameprep
>    mapping step,
>  - characters for which the NFC flag in DerivedNormalizationProperties.txt
>    is either NFC_NO or NFC_MAYBE,

This should be:
   - characters for which the NFKC_QuickCheck flag in
     DerivedNormalizationProperties-3_1_0.txt is either NFKC_NO or NFKC_MAYBE.

>  - characters that are prohibited in the output of nameprep (i.e. category D).

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO2DN/zkCAxeYt5gVAQEA7ggAz02hyNDSXb+poa/ABJJDAkwsnjCij8rH
c+xTVfpjpw7rE/yybb7tKnrZWpmTlMlh8KojjG4dMDzjVErdDZCgztlg1RzaX+NS
MQPxU8lQzAJHjSy8VPnf8IfFp6MDQAQafLI/KmtgYuFMGjHRm9UiXDKLlW1EjwjC
IVNen7lCey+MX0f+KsJXlW2vOwHRSnfjp0/98FC0iqOKL/UMxNqCm8DddebFoZAG
im/zAYZZoFZeccnk/OpS1jVEi7GnogS5OaQ7jeUTG5DVSo0UTYvqD4qamkJVYw8f
NMbwcrAkXN/iTrH/hWIM/0iEHTklvYf3rUCBb6v46fcEEGerTkbq2w==
=usdP
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Fri Jul 27 03:24:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA27984
	for <idn-archive@lists.ietf.org>; Fri, 27 Jul 2001 03:24:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Q1F0-00020I-00
	for idn-data@psg.com; Thu, 26 Jul 2001 23:36:54 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Q1Ez-000205-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 23:36:53 -0700
Received: from zetnet.co.uk (man-s044.dialup.zetnet.co.uk [194.247.41.171])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6R6akR00515
        for <idn@ops.ietf.org>; Fri, 27 Jul 2001 07:36:46 +0100
Message-ID: <3B60FF51.6B800822@zetnet.co.uk>
Date: Fri, 27 Jul 2001 06:42:41 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: idn@ops.ietf.org
Subject: [idn] Re: Common-case optimization of nameprep
References: <20010724065812.D8846@arwen.cs.berkeley.edu> <3B5DC4AA.AA422763@zetnet.co.uk> <3B60BE9B.6E7266ED@zetnet.co.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

I wrote:
> Let getCanonicalClassX(ch) be the Canonical Combining Class of ch, except that
> it returns a negative value if ch \in X. The set X is defined as the union of:
> 
>  - characters that are mapped to something else (or mapped out) by the nameprep
>    mapping step,
[  - characters for which the NFKC_QuickCheck flag in
     DerivedNormalizationProperties-3.1.0.txt is either NFKC_NO or NFKC_MAYBE.]
>  - characters that are prohibited in the output of nameprep (i.e. category D).

To answer my question about what X \ (MN union D) is:

Let M be the set of characters that are mapped to something else or mapped out.
Then we have the following:
  X = M union NFKC_NO union NFKC_MAYBE union D.
  MN = (M union NFKC_NO) \ D.

Therefore X \ (MN union D) = X \ (M union NFKC_NO union D)
                           = NFKC_MAYBE \ (M union NFKC_NO union D)
                           = NFKC_MAYBE.

NFKC_MAYBE is:

 - a subset of the Combining Diacritical Marks block (0300..0345).
 - some Arabic combining marks (0653..0655).
 - vowel signs and length marks for Devanagari, Bengali, Oriya, Tamil,
   Telugu, Kannada, Malayam, Sinhala, and Myanmar.
 - the combining Katakana-Hiragana voiced and semi-voiced sound marks.
 - a subset of the Hangul Jamo medial vowels (1161..1175).
 - a subset of the Hangul Jamo final consonants (11A8..11C2).

These are the characters that can occur in a nameprepped name, but will
inhibit the optimization if nameprep is applied again. All of them are
combining characters of one type or another, which makes sense because
it is complicated to check that there is no corresponding precomposed
form.

Should the common case optimization be described in the next version of
the nameprep draft?

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO2D/QTkCAxeYt5gVAQFnuwgAtzYRQqnOqZZ5SPiuhONCn3RQsv2K7H2G
YoOYvd4CsVrO8ggtpSbCCfd7o1gtCjVoJnpteTG0OTASSFQFM/dTZMYJlN9CJvmo
U20GoIWXpK6PomzB3CKzrn83O0f/HRh7tNou6Ks/80V8UmDHM08GcRtGoWqenyeY
iuOny+3GqSlFJtJ3QVR/IzFMCd2l35MIibyMZcbY32bOI2+OIgg4WLN2tR1jwbW5
g/tz1Rf+/SH+b5p/jNk5syoCM6b54e52g4Ha/stHb92BsAFz+mAtdk1vYNlfSbJc
SSw1+v4o1uoBQv5Ajqz948ThB7nQFx6bdYkNLVgXlSpFk2wJ0w4msQ==
=HrQd
-----END PGP SIGNATURE-----




From owner-idn@ops.ietf.org  Fri Jul 27 03:24:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA27997
	for <idn-archive@lists.ietf.org>; Fri, 27 Jul 2001 03:24:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Q1cz-0003LB-00
	for idn-data@psg.com; Fri, 27 Jul 2001 00:01:41 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Q1cy-0003Ka-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 00:01:40 -0700
Received: from valinor.malmo.trab.se (valinor [131.115.48.20]) by malmo.trab.se (8.10.1/TRAB-primary-2) with ESMTP id f6R6xqP24135 for <idn@ops.ietf.org>; Fri, 27 Jul 2001 08:59:52 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Fri, 27 Jul 2001 09:01:37 +0200 (MEST) (MET)
Message-Id: <200107270701.JAA01256@valinor.malmo.trab.se>
Date: Fri, 27 Jul 2001 09:01:37 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: [idn] Do we need ACE?
To: idn@ops.ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 3ebBkjPS2Oyf44aeHjgcXg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk


John Klensin have written a draft for using a separate class to handle
IDNs. This to really separate the IDN world from the old.

As software following the current rules on what characters are
allowed in a host name should reject queries and responses when
an invalid host name is used, could we get this separation between
old and new by just using UTF-8 in DNS?

If the DNS queries and responses having forbidden characters in host names
are ignored/rejected, an old software will not be able to lookup or
receive records with non-ASCII host names. I know that at least
some resolver routines (it is all in the client, DNS does not forbid
the characters) rejects PTR responses with non-ASCII in them.
If it is like this, the new IDN world will be hidden for all old clients.
This would the result in the old clients will not get any host names
through DNS that they cannot handle. Of course they will still get
invalid names by cut and past between new and old applications, but that
problem we have in all cases.
This way we would get the separate IDN and old DNS world without a new
class, instead we would get it because old software will see IDNs as
invalid.

But I have the feeling that most do not want the break with the old, instead
they want the old software to in some way to be able to handle IDNs too?
Though with all the mess it sometimes feels like, a break with the old
might be better.

   Dan




From owner-idn@ops.ietf.org  Fri Jul 27 03:24:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA28008
	for <idn-archive@lists.ietf.org>; Fri, 27 Jul 2001 03:24:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Q1M8-0002Sy-00
	for idn-data@psg.com; Thu, 26 Jul 2001 23:44:16 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Q1M6-0002Sr-00
	for idn@ops.ietf.org; Thu, 26 Jul 2001 23:44:15 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 2507EFFC06; Fri, 27 Jul 2001 14:45:52 +0800 (SGT)
Message-ID: <00a701c11667$8090f270$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "John C Klensin" <klensin@research.att.com>,
        "Soobok Lee" <lsb@postel.co.kr>
Cc: <idn@ops.ietf.org>
References:  <017e01c115c0$dad9de60$ed1bd9d2@postel.co.kr> <25153036.996164705@wave-172.research.att.com>
Subject: Re: [idn] Re: [idn-nameprep] Arabic hyphen-like glyph
Date: Fri, 27 Jul 2001 14:43:52 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John,

I do agree an analysis of the security implications are useful at least
as informational.

But I need to stress the wg need to proceed with internet drafts. We can
talk endlessly on ideas in emails but it will remains as what it is, ie,
email. This is the message I am trying to bring across to Lee: Write
draft first, then we can discuss based upon it.

As wg co-chair, I will make no judgement about what goes into the pool
or what's not so long there is sufficient interest and request (and of
course within our charter).

But on a personal note, I think Patrik hits the nails on the head. I am
not sure if IDN WG is the right forum to discuss 'look-alive characters'
issues. Remember we not only talking about codepoints, reportairs and
also fonts rendering and font variants...

-James Seng

----- Original Message -----
From: "John C Klensin" <klensin@research.att.com>
To: "Soobok Lee" <lsb@postel.co.kr>
Cc: "James Seng/Personal" <James@Seng.cc>; <idn@ops.ietf.org>
Sent: Friday, July 27, 2001 4:25 AM
Subject: Re: [idn] Re: [idn-nameprep] Arabic hyphen-like glyph


> --On Thursday, 26 July, 2001 19:50 +0900 Soobok Lee
> <lsb@postel.co.kr> wrote:
>
> > Using hyphen in place of NWNJ in Arabic multi-word domains
> > may cause confusion because arabic script already contains
> > hyphen-like letters already. that's the point.
> > That's not related directly to nameprep, but to IDN security.
> >
> > I hope those small ratholes may not become security holes in
> > IDN.
>
> It seems to me, regardless of other IDN work and its outcomes,
> that an analysis that identifies these "small ratholes" in
> matching and character identification and their security
> implications would be a very useful contribution.  Its text might
> ultimately become part of something else, or it might be
> published separately.  And I would hope that the WG Co-chairs
> would not impose an "interest level" requirement on drafts or
> components of such an analysis, treating it instead as part of
> the general requirement on the WG to produce a "security
> considerations" analysis of any proposed standards-track
> materials it produces.
>
>     john
>




From owner-idn@ops.ietf.org  Fri Jul 27 04:26:27 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA00884
	for <idn-archive@lists.ietf.org>; Fri, 27 Jul 2001 04:26:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Q2gV-0006yD-00
	for idn-data@psg.com; Fri, 27 Jul 2001 01:09:23 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Q2gT-0006y6-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 01:09:22 -0700
Received: from valinor.malmo.trab.se (valinor [131.115.48.20]) by malmo.trab.se (8.10.1/TRAB-primary-2) with ESMTP id f6R87MP27767; Fri, 27 Jul 2001 10:07:27 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Fri, 27 Jul 2001 10:09:07 +0200 (MEST) (MET)
Message-Id: <200107270809.KAA01275@valinor.malmo.trab.se>
Date: Fri, 27 Jul 2001 10:09:07 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: [idn] iDN Transition Support Requirements
To: idn@ops.ietf.org, dhc@dcrocker.net
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: IgW+KJEAFQmz/DE0d2lYfQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dave Crocker wrote:

>
>
>What portions of the Internet must support the relevant DNS mechanisms, for 
>ACE versus UTF-8?

I assume you mean the UTF-8 case where not ACE is used for backward
compatibility.


>
>Minimal use, UTF-8
>------------------
>
>a.  same as ACE
>
>b.  same as ACE
>
>c.  Every DNS component through the lookup sequence needs to support iDN, 
>before a successful lookup can be achieved.

No, you can use UTF-8 in a way that is just like the ACE handling.
Lookup by sending UTF-8 through DNS servers works fine with the current
DNS servers without change (if you use namepreped UTF-8 names just like
you do in the ACE case).

>
>d.  The target host application must support iDN, if it does any domain 
>name processing, such as to comfirm IP address and domain name matching, or 
>to display the string in native form.

The same is needed for the ACE case, the taget host must understand ACE
to display the string in native form, and must understand ACE to be able
to match a name in native form with the ACE encoded form.

>
>So...
>
>ACE permits incremental adoption.  For a first level of utility, only the 
>requesting user's software and the target host' domain server 
>administrative tools need to be enhanced.  On reflection, it will probably 
>seem obvious that one cannot get more minimal than that.

Well, if you use UTF-8 and your system uses UTF-8 as native format,
there is a good possibility that you can edit the zone files directely
using UTF-8 and start using UTF-8 without enhancing the administrative tools.
Though you probably would like to have a tool to check that the names you
enter are in the nameprepped format.

>
>By contrast, UTF-8 does not achieve minimal utility unless and until all 
>DNS-aware applications in the processing path are able to support iDN.

As indicated above, minimal usage is the same in both cases.


>My question then, are:
>
>a)  What technical errors are there in the above?

See above. You can also see in the archives for the mailing list. Not long
ago I wrote about some of the cases and the result was that the
problems were more or less equivalent.

>
>b)  What guarantees do we have about breakage/non-breakage when UTF-8 is 
>received by each of the relevant applications components, or how much 
>effort is needed obtain those guarantees?  And please note that the answer 
>to the equivalent question, for ACE, is already known:  No breakage.

ACE will give a lot of breakage. Decoded ACE names will leak into other
applications resulting in applications breaking (or just not being able
to find the host). The same will occur by using UTF-8.

No soulution is really good, both will result in a mess of host names
in ACE, UTF-8 and native forms being used in applications and protocols
which cannot handle them.

One important reason why I think people want UTF-8 is that then you can
use the same character coding on all character data and UTF-8 is the
most favoured format for interoperability today. A lot of systems work
on supporting it. ACE will always be a special DNS host name encoding.

   Dan





From owner-idn@ops.ietf.org  Fri Jul 27 06:25:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA05391
	for <idn-archive@lists.ietf.org>; Fri, 27 Jul 2001 06:25:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Q4ZB-000Ctx-00
	for idn-data@psg.com; Fri, 27 Jul 2001 03:09:57 -0700
Received: from sina.sharif.ac.ir ([62.41.32.2] ident=roozbeh)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Q4Z9-000CsI-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 03:09:55 -0700
Received: from localhost (roozbeh@localhost)
	by Sina.sharif.ac.ir (8.9.3/8.9.3) with ESMTP id OAA08333;
	Fri, 27 Jul 2001 14:39:15 +0430
Date: Fri, 27 Jul 2001 14:39:13 +0430 (IRDT)
From: Roozbeh Pournader <roozbeh@sharif.edu>
X-Sender: roozbeh@Sina.sharif.ac.ir
To: David Hopwood <david.hopwood@zetnet.co.uk>
cc: idn@ops.ietf.org
Subject: Re: [idn] Re: Just send UTF-8 with nameprep
In-Reply-To: <3B5F247E.1D3711C8@zetnet.co.uk>
Message-ID: <Pine.LNX.4.10.10107271434430.7928-100000@Sina.sharif.ac.ir>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk



On Wed, 25 Jul 2001, David Hopwood wrote:

> > We may need original spelling, for example if we decide that we need to
> > stop Arabic letters from joining, by using a ZWNJ between them (since a
> > space is not available). Multiword Arabic domain names will be unreadable
> > if the words join.
> 
> What's wrong with using hyphens to separate words?

Nothing's wrong. I only see using ZWNJ as an alternative. With English
domain names, you can have both 'damnthisworld.com' and
'damn-this-world.com'. With Arabic, you will have only the second choice,
since the first one will not be readable. I think that using ZWNJ may help
having more choices...




From owner-idn@ops.ietf.org  Fri Jul 27 07:10:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA07021
	for <idn-archive@lists.ietf.org>; Fri, 27 Jul 2001 07:10:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Q59Y-000Eml-00
	for idn-data@psg.com; Fri, 27 Jul 2001 03:47:32 -0700
Received: from sina.sharif.ac.ir ([62.41.32.2] ident=roozbeh)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Q59W-000EjO-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 03:47:31 -0700
Received: from localhost (roozbeh@localhost)
	by Sina.sharif.ac.ir (8.9.3/8.9.3) with ESMTP id PAA09717;
	Fri, 27 Jul 2001 15:13:47 +0430
Date: Fri, 27 Jul 2001 15:13:46 +0430 (IRDT)
From: Roozbeh Pournader <roozbeh@sharif.edu>
X-Sender: roozbeh@Sina.sharif.ac.ir
To: Martin Duerst <duerst@w3.org>
cc: John C Klensin <klensin@jck.com>, Dan Oscarsson <Dan.Oscarsson@trab.se>,
        idn@ops.ietf.org, idn-nameprep@viagenie.qc.ca
Subject: Re: ZWNJ (was: Re: Just send UTF-8 with nameprep (was: RE:  [idn]Reality
     Check))
In-Reply-To: <4.2.0.58.J.20010726102046.05fa8100@sh.w3.mag.keio.ac.jp>
Message-ID: <Pine.LNX.4.10.10107271440590.7928-100000@Sina.sharif.ac.ir>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk



On Thu, 26 Jul 2001, Martin Duerst wrote:

> As far as I remember, currently ZNWJ is dropped by nameprep without
> complaining. I think that if that leads to problems as you describe
> above, we should very carefully reexamine this decision. I have
> already told the nameprep design team that I think that this should be
> moved to 'disallowed' to avoid surprises like the above. But I'm not
> sure moving it to 'disallowed' would solve all problems (assuming that
> the hyphen is used for concatenating words).

I think dropping it without complain should be much better than making it
disallowed. I really like to be able to display my Arabic domain name with
proper joining. Example: I register an Arabic equivalent of
RoozbehPournader.com, which will be:

	Reh Waw Zain Beh Heh Peh Waw Reh Noon Alef Dal Reh .something

This will create problems when displayed: Heh and Peh, while belonging to
different words, will join, which is a bad thing.

With the current nameprep rules (good), I can put a ZWNJ between Heh and
Peh, so they get separated, and nameprep will rip it out when resolving
the name, which is also fine.

Other solutions:

1. Disallow ZWNJ: bad. I should then use a hyphen between Roozbeh and
Pournader, which I don't like.

2. Allow ZWNJ in names: worse. Someone will put a ZWNJ between two letters
that do not join (like Reh and Alef), leading to no difference in shape,
by a difference in resolving.

3. Rip ZWNJ in nameprep, but also have some DNS (or WHOIS) mechanism to
get to the non-nameprepped name: great. This way any protocol can get to
the original name if it wants.

I want to recommend the third option. How this may happen, I don't know.
But this can be considered a reason for having the reverse mechanism in
place, which was the subject of the thread I replied to.

roozbeh




From owner-idn@ops.ietf.org  Fri Jul 27 07:56:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA09683
	for <idn-archive@lists.ietf.org>; Fri, 27 Jul 2001 07:56:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Q5oe-000H0q-00
	for idn-data@psg.com; Fri, 27 Jul 2001 04:30:00 -0700
Received: from sina.sharif.ac.ir ([62.41.32.2] ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Q5oc-000H0X-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 04:29:59 -0700
Received: from bamdad.org (IDENT:root@gilas.bamdad.org [62.41.28.76])
	by Sina.sharif.ac.ir (8.9.3/8.9.3) with ESMTP id PAA11288;
	Fri, 27 Jul 2001 15:59:52 +0430
Received: from localhost (roozbeh@localhost)
	by bamdad.org (8.11.2/8.11.2) with ESMTP id f6RBU7b04709;
	Fri, 27 Jul 2001 16:00:07 +0430
X-Authentication-Warning: gilas.bamdad.org: roozbeh owned process doing -bs
Date: Fri, 27 Jul 2001 16:00:07 +0430 (IRST)
From: Roozbeh Pournader <roozbeh@sharif.edu>
X-X-Sender:  <roozbeh@gilas.bamdad.org>
To: Soobok Lee <lsb@postel.co.kr>
cc: James Seng/Personal <James@Seng.cc>, <idn@ops.ietf.org>
Subject: Re: [idn] Re: [idn-nameprep] Arabic hyphen-like glyph
In-Reply-To: <017e01c115c0$dad9de60$ed1bd9d2@postel.co.kr>
Message-ID: <Pine.LNX.4.33.0107271555530.4468-100000@gilas.bamdad.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Thu, 26 Jul 2001, Soobok Lee wrote:

> Using hyphen in place of NWNJ in Arabic multi-word domains
> may cause confusion because arabic script already contains
> hyphen-like letters already. that's the point.

No, it won't cause confusion. Feel free. You can take my word as a native
writer of Persian (which uses the Arabic script). I can be proven wrong,
but only by a native writer of Urdu for example, or someone providing good
enough details.

The point I raised about ZWNJ usage, is not that hyphens are bad, just
that ZWNJ may be considered better by many. I like to see both supported.

roozbeh




From owner-idn@ops.ietf.org  Fri Jul 27 08:07:22 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA10437
	for <idn-archive@lists.ietf.org>; Fri, 27 Jul 2001 08:07:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Q5gl-000GaP-00
	for idn-data@psg.com; Fri, 27 Jul 2001 04:21:51 -0700
Received: from sina.sharif.ac.ir ([62.41.32.2] ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Q5gj-000GXI-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 04:21:50 -0700
Received: from bamdad.org (IDENT:root@gilas.bamdad.org [62.41.28.76])
	by Sina.sharif.ac.ir (8.9.3/8.9.3) with ESMTP id PAA11078;
	Fri, 27 Jul 2001 15:51:23 +0430
Received: from localhost (roozbeh@localhost)
	by bamdad.org (8.11.2/8.11.2) with ESMTP id f6RBLb904583;
	Fri, 27 Jul 2001 15:51:39 +0430
X-Authentication-Warning: gilas.bamdad.org: roozbeh owned process doing -bs
Date: Fri, 27 Jul 2001 15:51:37 +0430 (IRST)
From: Roozbeh Pournader <roozbeh@sharif.edu>
X-X-Sender:  <roozbeh@gilas.bamdad.org>
To: Soobok Lee <lsb@postel.co.kr>
cc: <idn@ops.ietf.org>, <idn-nameprep@viagenie.qc.ca>
Subject: Re: [idn] Arabic hyphen-like glyph
In-Reply-To: <008d01c11581$5e4a0bc0$ec1bd9d2@temp>
Message-ID: <Pine.LNX.4.33.0107271546110.4468-100000@gilas.bamdad.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Thu, 26 Jul 2001, Soobok Lee wrote:

> Arabic glyph U+0640 (Arabic TATWEEL) looks like Latin hyphen(-).

But this is a joining character (something like a letter). We need
something non-joining.

> Arabic FULLSTOP U+06D4  looks like Latin 'underline' (or 'hyphen' ).

This is a very rare character, only used in Urdu.

> Using hyphen instead of punctuation char NWNJ(U+200C,No-width No joiner)
>  may not help but cause confusion to native-Arabic people.

I can't get what you really mean. Using hyphen will not cause confusion of
Arabic users, be sure about it. Hyphen is used in many languages that use
the Arabic script.

roozbeh




From owner-idn@ops.ietf.org  Fri Jul 27 09:24:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA16305
	for <idn-archive@lists.ietf.org>; Fri, 27 Jul 2001 09:24:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Q7PL-000MYQ-00
	for idn-data@psg.com; Fri, 27 Jul 2001 06:11:59 -0700
Received: from mail-blue.research.att.com ([135.207.30.102])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Q7PK-000MYJ-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 06:11:58 -0700
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 86A6B4D09D; Fri, 27 Jul 2001 09:11:56 -0400 (EDT)
Received: from KLENSIN-VAIO (secure.research.att.com [135.207.24.10])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id JAA11007;
	Fri, 27 Jul 2001 09:11:54 -0400 (EDT)
Date: Fri, 27 Jul 2001 08:54:23 -0400
From: John C Klensin <klensin@research.att.com>
To: "James Seng/Personal" <James@Seng.cc>
Cc: idn@ops.ietf.org
Subject: Re: [idn] Re: [idn-nameprep] Arabic hyphen-like glyph
Message-ID: <2522581.996224063@localhost>
In-Reply-To: <00a701c11667$8090f270$dd00a8c0@jamessonyvaio>
References:  <00a701c11667$8090f270$dd00a8c0@jamessonyvaio>
X-Mailer: Mulberry/2.1.0b2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Friday, 27 July, 2001 14:43 +0800 "James Seng/Personal"
<James@Seng.cc> wrote:

> John,
> 
> I do agree an analysis of the security implications are useful
> at least as informational.
> 
> But I need to stress the wg need to proceed with internet
> drafts. We can talk endlessly on ideas in emails but it will
> remains as what it is, ie, email. This is the message I am
> trying to bring across to Lee: Write draft first, then we can
> discuss based upon it.
>...

I hope my note was not taken to imply anything else.  I meant to
suggest that a security-focused draft might receive somewhat
different handling than the "need supporters to post" model for
protocol-focused or process-focused drafts.  I share your view
that we should stop having discussions about things that people
reference, but don't write drafts about.

     john




From owner-idn@ops.ietf.org  Fri Jul 27 09:47:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA18048
	for <idn-archive@lists.ietf.org>; Fri, 27 Jul 2001 09:47:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Q7d7-000NLi-00
	for idn-data@psg.com; Fri, 27 Jul 2001 06:26:13 -0700
Received: from sina.sharif.ac.ir ([62.41.32.2] ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Q7d5-000NLX-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 06:26:12 -0700
Received: from bamdad.org (IDENT:root@gilas.bamdad.org [62.41.28.76])
	by Sina.sharif.ac.ir (8.9.3/8.9.3) with ESMTP id RAA02768;
	Fri, 27 Jul 2001 17:55:59 +0430
Received: from localhost (roozbeh@localhost)
	by bamdad.org (8.11.2/8.11.2) with ESMTP id f6RDQCf02910;
	Fri, 27 Jul 2001 17:56:13 +0430
X-Authentication-Warning: gilas.bamdad.org: roozbeh owned process doing -bs
Date: Fri, 27 Jul 2001 17:56:11 +0430 (IRST)
From: Roozbeh Pournader <roozbeh@sharif.edu>
X-X-Sender:  <roozbeh@gilas.bamdad.org>
To: David Hopwood <david.hopwood@zetnet.co.uk>
cc: <idn@ops.ietf.org>
Subject: Re: [idn] Common-case optimization of nameprep - correction
In-Reply-To: <3B60CE2C.FAAA76C9@zetnet.co.uk>
Message-ID: <Pine.LNX.4.33.0107271741530.1750-100000@gilas.bamdad.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Fri, 27 Jul 2001, David Hopwood wrote:

> This should be:
>    - characters for which the NFKC_QuickCheck flag in
>      DerivedNormalizationProperties-3_1_0.txt is either NFKC_NO or NFKC_MAYBE.

I think refering to Unicode data files other than the originals is a bad
thing. The format will change, the level of information they provide will
change, ...

For example, take a look at what happened to 'PropList.txt' between 3.0.1:

	http://www.unicode.org/Public/3.0-Update1/PropList-3.0.1.txt

and 3.1.0:

	http://www.unicode.org/Public/3.1-Update/PropList-3.1.0.txt

roozbeh




From owner-idn@ops.ietf.org  Fri Jul 27 10:45:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA23116
	for <idn-archive@lists.ietf.org>; Fri, 27 Jul 2001 10:45:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Q7iT-000Ndv-00
	for idn-data@psg.com; Fri, 27 Jul 2001 06:31:45 -0700
Received: from mail-blue.research.att.com ([135.207.30.102])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Q7iS-000Ndb-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 06:31:44 -0700
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 0E55D4D0B9; Fri, 27 Jul 2001 09:31:43 -0400 (EDT)
Received: from KLENSIN-VAIO (secure.research.att.com [135.207.24.10])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id JAA13950;
	Fri, 27 Jul 2001 09:31:40 -0400 (EDT)
Date: Fri, 27 Jul 2001 09:30:10 -0400
From: John C Klensin <klensin@research.att.com>
To: Roozbeh Pournader <roozbeh@sharif.edu>
Cc: idn@ops.ietf.org
Subject: [idn] Re: [idn-nameprep] Re: ZWNJ (was: Re: Just send UTF-8
 with nameprep (was: RE:  [idn]Reality Check))
Message-ID: <4669646.996226210@KLENSIN-VAIO>
In-Reply-To: <Pine.LNX.4.10.10107271440590.7928-100000@Sina.sharif.ac.ir>
References:  <Pine.LNX.4.10.10107271440590.7928-100000@Sina.sharif.
 ac.ir>
X-Mailer: Mulberry/2.1.0b2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Friday, 27 July, 2001 15:13 +0430 Roozbeh Pournader
<roozbeh@sharif.edu> wrote:

> Other solutions:
> 
> 1. Disallow ZWNJ: bad. I should then use a hyphen between
> Roozbeh and Pournader, which I don't like.

Of course, what seems to me, not knowing Arabic, to be a near
equivalent, a space between words, is disallowed in the current
naming rules and always has been.  Hence, if "Joes Pizza" goes
into the DNS, it goes in either as "joespizza" or "joes-pizza".
No other options.  I think this situation should be improved for
both Arabic and English, and all other languages where it is
relevant, but it seems to me that the perceived requirement makes
another "not in the DNS" argument.


> 3. Rip ZWNJ in nameprep, but also have some DNS (or WHOIS)
> mechanism to get to the non-nameprepped name: great. This way
> any protocol can get to the original name if it wants.
> 2. Allow ZWNJ in names: worse. Someone will put a ZWNJ between
> two letters that do not join (like Reh and Alef), leading to no
> difference in shape, by a difference in resolving.

> I want to recommend the third option. How this may happen, I
> don't know. But this can be considered a reason for having the
> reverse mechanism in place, which was the subject of the thread
> I replied to.

Well, to use my silly example again, we have had mechamisms for
putting "Joes Pizza" in whois since the beginning, even if it
points to a domain containing joespizza.  If that meets your
needs, I suggest you want to cover the whois BOF at IETF, but
that this is not an IDN problem.   If you want to be able to
access the information automatically, when names are displayed to
users, whois is too slow and you have a number of interesting
database and coordination problems, none of which appear to be in
the scope of the IDN WG.

    john




From owner-idn@ops.ietf.org  Fri Jul 27 13:22:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA09747
	for <idn-archive@lists.ietf.org>; Fri, 27 Jul 2001 13:22:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QB7f-000AH4-00
	for idn-data@psg.com; Fri, 27 Jul 2001 10:09:59 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QB7e-000AGy-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 10:09:58 -0700
Received: from [24.252.219.84] (account ehall HELO ehsco.com)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.8)
  with ESMTP-TLS id 191273; Thu, 26 Jul 2001 12:09:13 -0500
Message-ID: <3B61A05F.A5B0D30D@ehsco.com>
Date: Fri, 27 Jul 2001 12:09:51 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dan Oscarsson <Dan.Oscarsson@trab.se>
CC: idn@ops.ietf.org
Subject: Re: [idn] Do we need ACE?
References: <200107270701.JAA01256@valinor.malmo.trab.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> As software following the current rules on what characters are
> allowed in a host name should reject queries and responses when
> an invalid host name is used, could we get this separation between
> old and new by just using UTF-8 in DNS?

I don't think this is a safe assumption, due to the fact that there are
likely to be many applications generating lookups for IDNs based on a
local encoding. Windows-1252, MacRoman, and other charsets that use the C1
codepoint space are able to generate byte sequences that look like UTF-8,
and it would be pretty difficult to test these sequences given that the
label length can be very small.

There's also the consideration that we need to know if an IDN is valid.
Just because an IDN shows up in UTF-8 doesn't mean that it has been
validated through nameprep and application-specific rules.

IOW, we need to reject malformed queries, especially those that look valid
but aren't. In order to do that, we have to tag the queries at the source.
There's no just no other way around it that I can see.

There's also an upside to using the extended label type tags, which is
that future generations can add more tags if they want to. If a UCS-3 CES
were to emerge for the unified 21-bit codepoint space and become
sufficiently popular, then that format can be added with another tag.

One other related point--we may want to encourage implementors to reject
legacy queries that contain eight-bit characters. This would force failure
with applications that are eight-bit "friendly" when they shouldn't be.
I've been looking through the RR types and so far I haven't come up with
anything that requires eight-bit names. I've only found some names that
don't comply with the LDH rules (SRV uses underscore, for example) but
they are still seven-bit ASCII.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/



From owner-idn@ops.ietf.org  Fri Jul 27 18:09:43 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA08703
	for <idn-archive@lists.ietf.org>; Fri, 27 Jul 2001 18:09:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QE3W-000KeD-00
	for idn-data@psg.com; Fri, 27 Jul 2001 13:17:54 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15QE3V-000Ke7-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 13:17:53 -0700
Message-ID: <00d401c116d9$cae2f3b0$0b01a8c0@davidvaio>
From: "David Leung" <david@neteka.com>
To: "ben" <ben@cc-www.com>, <idn@ops.ietf.org>
References: <003d01c116d7$39b7a180$d43f7018@mtag1.on.home.com>
Subject: Re: [idn] Intro to my I-D
Date: Fri, 27 Jul 2001 16:21:59 -0400
Organization: Neteka Inc.
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00D1_01C116B8.43061470"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_00D1_01C116B8.43061470
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I think there is already an Internet Draft on SC-TC(Simplified Chinese =
and Traditional Chinese) folding.

  ----- Original Message -----=20
  From: ben=20
  To: idn@ops.ietf.org=20
  Sent: Friday, July 27, 2001 4:03 PM
  Subject: [idn] Intro to my I-D


  It appears that I-D will not be accepted til Aug 14, so there is =
plenty of time for me to prepare it.  But anyways, here is a very simple =
intro to why I am interested in "the need for conversion between =
different (yet similiar) scripts":

  I have a very small company that offers CDNs (Chinese domain names).  =
My hope is to be able to take the benefits from other systems and =
combine them together to form a supreme.  (Although I want to emphasize =
that other systems are 100% fine exactly the way they are.)  Combining =
the following 2 benefits together is crucial to my supreme system with =
both weighting EXACTLY THE SAME IMPORTANCE:

  Benefit A-  A simplified CDN points to a website that is written in =
simplified Chinese (GB encoding) for visitors in mainland China or =
Singapore while a traditional CDN points to a website written in =
traditional Chinese (Big5 encoding) for visitors in Taiwan or Hong Kong.

  Benefit B-  When a registrant registers a simplified CDN, the =
corresponding traditional CDN(s) is automatically reserved and visa =
versa.

  I will put all the details into the draft and submit it by Aug 14.  =
Hopefully, I can get 7 supporters- thank you very much!

  Ben Chan


------=_NextPart_000_00D1_01C116B8.43061470
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2462.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I think there is already an Internet =
Draft on=20
SC-TC(Simplified Chinese and Traditional Chinese) folding.</FONT></DIV>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dben@cc-www.com href=3D"mailto:ben@cc-www.com">ben</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Didn@ops.ietf.org =

  href=3D"mailto:idn@ops.ietf.org">idn@ops.ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Friday, July 27, 2001 =
4:03 PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [idn] Intro to my =
I-D</DIV>
  <DIV><BR></DIV>
  <DIV><FONT face=3DArial size=3D2>It appears that I-D will not be =
accepted til Aug=20
  14, so there is plenty of time for me to prepare it.&nbsp; But =
anyways, here=20
  is a very simple intro to why I am interested in&nbsp;"the need for =
conversion=20
  between different (yet similiar) scripts":</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>I have a very small company that =
offers CDNs=20
  (Chinese domain names).&nbsp;&nbsp;My&nbsp;hope is to be able to =
take&nbsp;the=20
  benefits&nbsp;from other systems and combine them together to form a=20
  supreme.&nbsp; (Although I want to emphasize that other systems are =
100% fine=20
  exactly the way they are.)&nbsp;&nbsp;Combining the&nbsp;following 2 =
benefits=20
  together&nbsp;is crucial to my supreme system with both weighting =
EXACTLY THE=20
  SAME IMPORTANCE:</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Benefit&nbsp;A-&nbsp; A simplified =
CDN points to=20
  a website that is written in simplified Chinese (GB encoding) for =
visitors in=20
  mainland China or Singapore while a traditional CDN points to a =
website=20
  written&nbsp;in traditional Chinese&nbsp;(Big5 encoding) for visitors =
in=20
  Taiwan or Hong Kong.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Benefit B-&nbsp; When a registrant =
registers a=20
  simplified CDN, the corresponding traditional CDN(s) is automatically =
reserved=20
  and visa versa.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>I will put all the details into the =
draft and=20
  submit it by Aug 14.&nbsp; Hopefully, I can get 7 supporters- thank =
you very=20
  much!</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Ben Chan</FONT></DIV>
  <DIV><FONT face=3DArial =
size=3D2></FONT>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_00D1_01C116B8.43061470--




From owner-idn@ops.ietf.org  Sun Jul 29 01:52:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA13792
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:52:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QLXI-000MZD-00
	for idn-data@psg.com; Fri, 27 Jul 2001 21:17:08 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QLXH-000MYX-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 21:17:07 -0700
Received: from zetnet.co.uk (man-s080.dialup.zetnet.co.uk [194.247.41.207])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6S4H3r13838
        for <idn@ops.ietf.org>; Sat, 28 Jul 2001 05:17:04 +0100
Message-ID: <3B622DC1.7ADAA40C@zetnet.co.uk>
Date: Sat, 28 Jul 2001 04:13:05 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: idn@ops.ietf.org
Subject: Re: [idn] Common-case optimization of nameprep - correction
References: <Pine.LNX.4.33.0107271741530.1750-100000@gilas.bamdad.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

Roozbeh Pournader wrote:
> On Fri, 27 Jul 2001, David Hopwood wrote:
> 
> > This should be:
> >    - characters for which the NFKC_QuickCheck flag in
> >      DerivedNormalizationProperties-3_1_0.txt is either NFKC_NO or NFKC_MAYBE.
> 
> I think refering to Unicode data files other than the originals is a bad
> thing.

It would not be a normative reference: the information would be used to
calculate the set X, and that set would be given in the nameprep spec.
This causes no problems because each version of nameprep corresponds to a
specific version of Unicode.

> The format will change, the level of information they provide will change,
> ...
> 
> For example, take a look at what happened to 'PropList.txt' between 3.0.1:
> 
>         http://www.unicode.org/Public/3.0-Update1/PropList-3.0.1.txt
> 
> and 3.1.0:
> 
>         http://www.unicode.org/Public/3.1-Update/PropList-3.1.0.txt

The latter is the standard machine readable format used by all the Unicode
files; the former isn't, so it's obvious why the format changed in this case.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO2HSrTkCAxeYt5gVAQElJQf/VF9zF0mCSP84dMV5yQE9/dpHsaZRciFl
9QdYHHIcWN4mXITv+fDFvCaF3ATb7UR+r8GFhVuqmCkkYAI2ePrcc+XfKntmsn+G
0ZinLKF5MMs+rTD6R06TrT5EAAk/czx/GOYGDfNq6HPuU2WQsNXJ1uaS9BHofNCB
Ml/jdv2eHuxSO1HHkrG3CP6r7wfPfCpZHDu9VWGWrC/OuVN6Yko/68D0N0unjqyZ
jTHhryv+WlXpTfWKQNF08egf0xywb/dh1SaYEU/b83LR0HtR4XK1o0qUgGTWVMP+
TnrYSO9KMybgjGczO05blR2MbDG6r06kP2vJ5twEbN/5P6HP84tCHw==
=QoV0
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Sun Jul 29 01:52:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA13811
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:52:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Qh67-0005la-00
	for idn-data@psg.com; Sat, 28 Jul 2001 20:18:31 -0700
Received: from web5505.mail.yahoo.com ([216.115.106.188])
	by psg.com with smtp (Exim 3.31 #1)
	id 15Qh66-0005lU-00
	for idn@ops.ietf.org; Sat, 28 Jul 2001 20:18:30 -0700
Message-ID: <20010729031829.25658.qmail@web5505.mail.yahoo.com>
Received: from [159.226.7.65] by web5505.mail.yahoo.com via HTTP; Sat, 28 Jul 2001 20:18:29 PDT
Date: Sat, 28 Jul 2001 20:18:29 -0700 (PDT)
From: wenhui zhang <zwh6810@yahoo.com>
Subject: Re: [idn] Intro to my I-D
To: ben <ben@cc-www.com>, John C Klensin <klensin@jck.com>
Cc: idn@ops.ietf.org
In-Reply-To: <005501c117b5$c6370ae0$d43f7018@mtag1.on.home.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1375653627-996376709=:24606"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--0-1375653627-996376709=:24606
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

hell Ben:

  I am wenhui from CNNIC, you can reach me via
zwh6810@yahoo.com or zwh@cnnic.net.cn.
  Our two drafts are as follows:
http://www.i-d-n.net/draft/draft-ietf-idn-tsconv-00.txt

  
  
Wenhui

--- ben <ben@cc-www.com> wrote:
> Hi John,
> 
> Thanks for your suggestion, I will do that.
> 
> By the way, fyi, under my supreme CDN system... a
> registrant has the
> choice of pointing the Simplified CDN and the
> Traditional CDN both to
> the same location OR to different locations.  (If
> you still don't
> understand... things will be more detailed / clear
> when my draft comes
> out.)
> 
> Thanks
> Ben
> 
> ----- Original Message -----
> From: "John C Klensin" <klensin@jck.com>
> To: "ben" <ben@cc-www.com>
> Cc: <idn@ops.ietf.org>
> Sent: Saturday, July 28, 2001 12:14 PM
> Subject: Re: [idn] Intro to my I-D
> 
> 
> 
> Ben (and David and Eric),
> 
> It seems to me that a high-level summary of the
> difficulty here
> is that you want to treat Simplified and Traditional
> Chinese as
> different so that you can assign semantics (e.g.,
> different web
> sites written respectively in the two forms) to the
> two writing
> styles.  Our CNNIC colleagues believe that
> Simplified and
> Traditional writing forms to express the same word
> should be
> treated as equivalent and mapped into each other.
> 
> That is very fundamental; we can't have it both ways
> in the DNS
> (although one can imagine "treat these alike and see
> what is
> found" instructions to a search system).  As I
> understand what
> they have said, mixtures of simplified and
> traditional systems
> within a given phrase are also possible, which
> eliminates the
> simplification you propose of automatically
> registering "both"
> forms.
> 
> I agree with David and Eric that you should
> carefully examine
> the Lee and Deng drafts.  But, since there seems to
> be a more
> basic philosophical difference here, I suggest that
> you try to
> work with them to understand each other's positions
> and see if
> some collectively acceptable position can be found.
> 
>     john
> 
> 
> 
> 


__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
--0-1375653627-996376709=:24606
Content-Type: text/plain; name=draft-ietf-idn-icdns-00
Content-Description: draft-ietf-idn-icdns-00
Content-Disposition: inline; filename=draft-ietf-idn-icdns-00

Internet Draft                                     Authors: Xiang Deng
<draft-ietf-idn-icdn-00.txt>                                Yan Fang Wang   		  
July , 2001                                                    
Expires in six months		                                   
                                                           
                                                           
                                                           
                                                              
       The Implementation of Chinese character in IDN

Status of this Memo

This document is an Internet-Draft and is in full conformance with all 
provisions of Section 10 of RFC2026.

Internet-Drafts are working documents of the Internet Engineering Task 
Force (IETF), its areas, and its working groups. Note that other groups 
may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months 
and may be updated, replaced, or obsoleted by other documents at any 
time. It is inappropriate to use Internet-Drafts as reference material 
or to cite them other than as "work in progress."

    The list of current Internet-Drafts can be accessed at
    http://www.ietf.org/ietf/1id-abstracts.txt

    The list of Internet-Draft Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html

Terminology

The key words "MUST", "SHALL", "REQUIRED", "SHOULD", "RECOMMENDED", and
"MAY" in this document are to be interpreted as described in RFC 2119
[RFC2119].

Abstract

This document mainly talks about Chinese characters and two proposed 
schemes of implemention based on [IDNREQ] and [NAMEPREP],though 
there are some differences among them.The distinction between these two schemes 
is the position of the implementation function:
    -- client side processing 
or 
    -- server side processing

In China, the most popular character set are [GBK],[BIG5],[GB18030],while
in this document,all examples are based on [UCS].


1.  Charateristics of Chinese characters and Chinese languange
1.1 The context dependent semantics of Chinese characters 
    In [UCS],each Chinese character is a codepoint,which is composed of two
    bytes.
    
    Chinese character can be classified as two groups. In one group,each
    character does its own meaning(notional character) while that of the
    other group has not(empty characters). Both notional characters and
    empty characters can be made words by combining with other 
    character(s),even sentences. the notional character 
    is the basic unit of Chinese language which has meaning similar to phonems.
    
1.2 A Chinese characters may have several writing forms.
    
    Chinese characters were continuously evolved and widely spread during
    5,000-year-long Chinese history. They were also largely introduced 
    into other countries and became a major component of their languages.
    Therefore, it is inevitably for a Chinese character has many other
    writing forms. In Unicode encoding standards, the criterion for
    distributing codepoint is the shape of character. So the different 
    glyph of the same Chinese character have several different 
    codepoint according to the international encoding standard.
    
    Currently,there are two forms of writing Chinese character:
      -- simplified character(SC): mainland of China
      -- traditional character(TC): Taiwan,Hongkong,Macao
    
    Except for some special writing forms of certain character, their 
    meaning had also been changed in the long history. Generally different
    writing forms of a Chinese character can substituted by each other 
    without changing the meaning of the word(phrase).    
 
   
1.3 The Usage of Appellation in China
    In China, Generally speaking,every companies,organizations and people
    have two names: full name and abbreviation.
    
    The abbreviated name is easy to remember and to communicate.The full
    name is a formal name which is used in formal document,situation.
    
    To the name owners,the two names are equal necessary and important. 
    So,in domain name registration,they usually register both full name 
    and the corresponding abbreviations in order to permit people to access
    the same domain name by typing the full name or the abbreviatied name.
    Some of the full names are quite long,that's why the length of domain 
    name is important for Chinese user.


2. Chinese characters in DNS
1.1 Traditional and Simplified Chinese Conversion has 3 forms:
    1-1 mapping: one traditional character(TC) maps to ONLY one simplified
                 characer(SC).
    1-n mapping: one TC has several SC writing forms	
    n-1 mapping: one SC has several forms of TC

1.2 Delimiter folding
    The full stop in chinese is "¡£". Therefore, the "¡£" in CDNS is equal 
    to the dot "." as the delimiter.

1.3 Label sequence
   Currently,the label sequence of LDH domain name is from left to right,
   (e.g.:abc.def.ghi.net),the subdomain is to the left and the superset 
   of the subdomain is to the right.
   
   In China,user has reverse convention of language. Considering the 
   culture different between the east and the west, it's necessary for
   people to access the Internet with the convention of using their native
   languages.for example:
   
        CDNLabel1.CDNLabel2.cn 
   perfer to :
        cn.CDNLabel2.CDNLabel1
         
   


3. Solutions  
3.1 Client side solution 

	    +-----------------------------------------------+
	    |                  user input 		    |
	    +-----------------------------------------------+
		   |				      ^
		   V				      |
	 +-------------------+			      |
	 | Delimiter folding |			      |
	 |    "¡£" -> "."    |			      |
	 +-------------------+			      |
	 	   |				      |	
	 	   V				      |	
    +------------------------------+	+------------------------------+
    | label sequence normalization |	| label sequence normalization |
    +------------------------------+	+------------------------------+
		   |				      ^
		   V				      |	
        +----------------------+  	   +----------------------+
  	| local encoding ->UCS |	   | UCS ->local encoding |
        +----------------------+	   +----------------------+
	  	   |				      ^
	  	   V				      |	
       +------------------------+	  +------------------------+
       | local mapping (TC - SC)|	  | local mapping (TC - SC)|
       +------------------------+	  +------------------------+
       		   |				      ^
       		   V				      |	
       	      +----------+                            |
              | NAMEPREP |                            |
              +----------+                            |
              	   |				      |	
              	   V				      |	
             +------------+			+-----------------+
             | UCS -> MDN |			| MDN -> UCS |
             +------------+			+-----------------+
             	   |				      ^	
             	   V				      |
             +-----------------------------------------------+
             | 		     	local resolver 		     |
             +-----------------------------------------------+
             |  		  DNS server		     |
             +-----------------------------------------------+


3.1 Server side solution

	    +-----------------------------------------------+
	    |                  user input 		    |
	    +-----------------------------------------------+
		   |				      ^
		   V				      |
	 +-------------------+			      |
	 | Delimiter folding |			      |
	 |    "¡£" -> "."    |			      |
	 +-------------------+			      |
	 	   |				      |	
	 	   V				      |	
    +------------------------------+	+------------------------------+
    | label sequence normalization |	| label sequence normalization |
    +------------------------------+	+------------------------------+
		   |				      ^
		   V				      |	
        +----------------------+  	   +----------------------+
  	| local encoding ->UCS |	   | UCS ->local encoding |
        +----------------------+	   +----------------------+
	  	   |				      ^
	  	   V				      |	
       	      +----------+                            |
              | NAMEPREP |                            |
              +----------+                            |
              	   |				      |	
              	   V				      |	
             +------------+			+-----------------+
             | UCS -> MDN |			| MDN -> UCS |
             +------------+			+-----------------+
             	   |				      ^	
             	   V				      |
             +-----------------------------------------------+
             | 		     	local resolver 		     |
             +-----------------------------------------------+
             			     |
             			     V
             +-----------------------------------------------+
             |  	    local mapping (TC - SC)	     |
             |-----------------------------------------------|
             |  		  DNS server		     |
             +-----------------------------------------------+


6 Authors' Address
Xiang Deng
China Internet Network Information Center 
NO.4  South 4th ST. Beijing, P.R.China, 100080, PO BOX 349
Tel: +86-10-62619750 

Yan Fang Wang
China Internet Network Information Center 
NO.4  South 4th ST. Beijing, P.R.China, 100080, PO BOX 349
Tel: +86-10-62619750 


7 References

[IDNREQ]  Requirements of Internationalized Domain Names, Zita Wenzel, 
                James Seng, draft-ietf-idn-requirements

[NAMEPREP] Paul Hoffman & Marc Blanchet, Preparation of
           Internationalized Host Names, draft-ietf-idn-nameprep

[RFC2119] Scott Bradner, Key words for use in RFCs to Indicate
          Requirement Levels, March 1997, RFC 2119.

[STD13]   Paul Mockapetris, Domain names - implementation and
          specification, November 1987, STD 13 (RFC 1034 and 1035).
             
[UNAME]   Internationalized Domain Names and Unique Identifiers/Names
                Li Ming TSENG, Jan Ming HO, Hua Lin QIAN, Kenny HUANG
                draft-ietf-idn-uname
                
[TSCONV]  Traditional and Simplified Chinese Conversion
		Xiao Dong Lee, Nai Wen Hsu, Erin Chen, Guo Nian Sun
		draft-ietf-idn-tsconv
		
[ISO10646] ISO/IEC 10646-1:2000. International Standard -- Information
           technology -- Universal Multiple-Octet Coded Character Set 
           (UCS) -- Part 1: Architecture and Basic Multilingual Plane.

[Unicode3] The Unicode Consortium, "The Unicode Standard -- Version3.0",
           ISBN 0-201-61633-5. 
           
           
--0-1375653627-996376709=:24606--



From owner-idn@ops.ietf.org  Sun Jul 29 01:52:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA13826
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:52:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QcZ7-000Nb6-00
	for idn-data@psg.com; Sat, 28 Jul 2001 15:28:09 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QcZ6-000Nak-00
	for idn@ops.ietf.org; Sat, 28 Jul 2001 15:28:08 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Sat, 28 Jul 2001 15:39:33 -0700
Message-ID: <005501c117b5$c6370ae0$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "John C Klensin" <klensin@jck.com>
Cc: <idn@ops.ietf.org>
References:  <003d01c116d7$39b7a180$d43f7018@mtag1.on.home.com> <6366219.996322484@localhost>
Subject: Re: [idn] Intro to my I-D
Date: Sat, 28 Jul 2001 18:36:41 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi John,

Thanks for your suggestion, I will do that.

By the way, fyi, under my supreme CDN system... a registrant has the
choice of pointing the Simplified CDN and the Traditional CDN both to
the same location OR to different locations.  (If you still don't
understand... things will be more detailed / clear when my draft comes
out.)

Thanks
Ben

----- Original Message -----
From: "John C Klensin" <klensin@jck.com>
To: "ben" <ben@cc-www.com>
Cc: <idn@ops.ietf.org>
Sent: Saturday, July 28, 2001 12:14 PM
Subject: Re: [idn] Intro to my I-D



Ben (and David and Eric),

It seems to me that a high-level summary of the difficulty here
is that you want to treat Simplified and Traditional Chinese as
different so that you can assign semantics (e.g., different web
sites written respectively in the two forms) to the two writing
styles.  Our CNNIC colleagues believe that Simplified and
Traditional writing forms to express the same word should be
treated as equivalent and mapped into each other.

That is very fundamental; we can't have it both ways in the DNS
(although one can imagine "treat these alike and see what is
found" instructions to a search system).  As I understand what
they have said, mixtures of simplified and traditional systems
within a given phrase are also possible, which eliminates the
simplification you propose of automatically registering "both"
forms.

I agree with David and Eric that you should carefully examine
the Lee and Deng drafts.  But, since there seems to be a more
basic philosophical difference here, I suggest that you try to
work with them to understand each other's positions and see if
some collectively acceptable position can be found.

    john






From owner-idn@ops.ietf.org  Sun Jul 29 01:52:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA13954
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:52:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QWk2-000DQV-00
	for idn-data@psg.com; Sat, 28 Jul 2001 09:15:02 -0700
Received: from [209.187.148.217] (helo=P2)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QWk1-000DQ1-00; Sat, 28 Jul 2001 09:15:01 -0700
Date: Sat, 28 Jul 2001 12:14:44 -0400
From: John C Klensin <klensin@jck.com>
To: ben <ben@cc-www.com>
cc: idn@ops.ietf.org
Subject: Re: [idn] Intro to my I-D
Message-ID: <6366219.996322484@localhost>
In-Reply-To: <003d01c116d7$39b7a180$d43f7018@mtag1.on.home.com>
References:  <003d01c116d7$39b7a180$d43f7018@mtag1.on.home.com>
X-Mailer: Mulberry/2.1.0b2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Friday, 27 July, 2001 16:03 -0400 ben <ben@cc-www.com>
wrote:

> I have a very small company that offers CDNs (Chinese domain
> names).  My hope is to be able to take the benefits from other
> systems and combine them together to form a supreme.
> (Although I want to emphasize that other systems are 100% fine
> exactly the way they are.)  Combining the following 2 benefits
> together is crucial to my supreme system with both weighting
> EXACTLY THE SAME IMPORTANCE:
> 
> Benefit A-  A simplified CDN points to a website that is
> written in simplified Chinese (GB encoding) for visitors in
> mainland China or Singapore while a traditional CDN points to
>..

Ben (and David and Eric),

It seems to me that a high-level summary of the difficulty here
is that you want to treat Simplified and Traditional Chinese as
different so that you can assign semantics (e.g., different web
sites written respectively in the two forms) to the two writing
styles.  Our CNNIC colleagues believe that Simplified and
Traditional writing forms to express the same word should be
treated as equivalent and mapped into each other.

That is very fundamental; we can't have it both ways in the DNS
(although one can imagine "treat these alike and see what is
found" instructions to a search system).  As I understand what
they have said, mixtures of simplified and traditional systems
within a given phrase are also possible, which eliminates the
simplification you propose of automatically registering "both"
forms.

I agree with David and Eric that you should carefully examine
the Lee and Deng drafts.  But, since there seems to be a more
basic philosophical difference here, I suggest that you try to
work with them to understand each other's positions and see if
some collectively acceptable position can be found.

    john




From owner-idn@ops.ietf.org  Sun Jul 29 01:52:30 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA13964
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:52:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QWY1-000D2Z-00
	for idn-data@psg.com; Sat, 28 Jul 2001 09:02:37 -0700
Received: from [209.187.148.217] (helo=P2)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QWXz-000D2O-00; Sat, 28 Jul 2001 09:02:35 -0700
Date: Sat, 28 Jul 2001 12:02:30 -0400
From: John C Klensin <klensin@jck.com>
To: Roozbeh Pournader <roozbeh@sharif.edu>
cc: idn@ops.ietf.org
Subject: Re: [idn] ZWNJ
Message-ID: <5632254.996321750@localhost>
In-Reply-To: <Pine.LNX.4.33.0107281714490.21040-100000@gilas.bamdad.org>
References:  <Pine.LNX.4.33.0107281714490.21040-100000@gilas.bamda
 d.org>
X-Mailer: Mulberry/2.1.0b2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Saturday, 28 July, 2001 17:31 +0430 Roozbeh Pournader
<roozbeh@sharif.edu> wrote:

>> Arabic alphabets put together may have different rendering
>> forms depends whether there is a break between the alphabets
>> or not. But it is not neccessary a 'space' because there is
>> no gap. Someone told me that ZWNJ was suggested as a way to
>> insert this break without adding a space altho that was not
>> the reason ZWNJ was there in the first place.
> 
> You have some idea. The ZWNJ is actually used in languages
> like Persian, which are not Arabic (language) based, but only
> use the Arabic script. Since in this languages the words are
> longer than Arabic words, and there is a need to separate
> parts of the word. Consider the case of German: those long
> words are really hard to read. Add the Arabic joinging to this,
> you will surely have problems finding subword boundaries.
> Persian typography then introduced ZWNJ (which is called
> semi-space in Persian traditional typography) to break the
> words so they become readable.

Roozbeh,

My apologies for my lack of understanding and poor statement of
what I did understand.  Let me try again..

DNS names are identifiers and, as identifiers, are subject to
certain restrictions.  Length is one of them -- we even have
words in English that are over 63 character long, although there
aren't many of them, and they can't be used in domain names.  A
second is that, as identifiers, labels are what computer languge
syntax folks call "atoms" or "atomic".  That typically means
"one label, one "word".  There is a long history of pushing
words together to make one DNS labels and using either the one
joining character available (hyphen) or just catenating them.
In the latter case, we just hope the user will figure out what
is going on to preserve whatever mneumonic value we intend.  

Parenthetically, this is one place where our colleagues with
ideographic languages have a huge advantage: they can actually
write multi-word phrases into DNS labels/identifiers without
doing violence to the natural rules of the writing system.

So I don't know quite what to do with ZWNJ and other separators
or near-separators without opening the door to other characters
normally used in other languages as near-separators or
punctuation or near-punctuation, e.g., ":", "'", "!", or "&",
which have been used, normally or artistically, in Indo-European
languages using Roman-derived character sets for many years, and
even recognizing distinct interpretations for some of the
distinct spacing characters and hyphenation ones in Unicode.

For example, while I would _strongly_ not recommend going down
this path, we could, in principle, adopt presentation and coding
rules that would permit, e.g., 

   "O'Reilly & Associates"

to use the domain name

   www."O'Reilly & Associates".com

by coding the key second label as
   O(U+0027)Reilly(U+00A0)(U+0026)(U+00A0)Associates

Again, I don't suggest doing this, but, ultimately, the DNS
itself would have no problems with it and, if one starts
introducing near-space characters from other scripts, then there
is little justification for prohibiting this type of usage in
Roman-based ones.

     john




From owner-idn@ops.ietf.org  Sun Jul 29 01:52:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA14006
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:52:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QWF4-000CLX-00
	for idn-data@psg.com; Sat, 28 Jul 2001 08:43:02 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QWF3-000CL3-00
	for idn@ops.ietf.org; Sat, 28 Jul 2001 08:43:01 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f6SFf3N16708;
	Sat, 28 Jul 2001 11:41:03 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107281541.f6SFf3N16708@nic-naa.net>
To: "ben" <ben@cc-www.com>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Intro to my I-D 
In-Reply-To: Your message of "Sat, 28 Jul 2001 00:46:18 EDT."
             <00a701c11720$3e377a20$d43f7018@mtag1.on.home.com> 
Date: Sat, 28 Jul 2001 11:41:03 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Ben,

Section 6 of draft-ietf-idn-tsconv-00.txt has the authors' addresses:

XiaoDong LEE and GuoNian SUN may both be reached at the CNNIC. Both attended
IETF-50, and I'd the pleasure of meeting them in Beijing earlier this month
at the 5th ChineInet Conference.

China Network Information Center (CNNIC)
NO.4  South 4th ST. Beijing, P.R.China, 100080, PO BOX 349
Email: lee@cnnic.net.cn
Tel: +86-10-62619750#3020
Email: sun@cnnic.net.cn
Tel: +86-10-62619750#3016


HSU, NAI-WEN and Erin (Yu Hsuan) Chen may both be reached at the TWNIC. I've
not met with either.

Taiwan Network Information Center (TWNIC)
4F-2, No.9 Sec. 2, Roosevelt Rd., Taipei, 100 Taiwan, R.O.C.
Email: snw@twnic.net.tw
Tel: +886-2-23411313#500
Email: erin@twnic.net.tw
Tel: +886-2-23411313#502

I'm interested in your questions also, and you may write to me privately,
though I am no substitute for the authors.

Eric



From owner-idn@ops.ietf.org  Sun Jul 29 01:52:44 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA14115
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:52:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QTjl-0003t3-00
	for idn-data@psg.com; Sat, 28 Jul 2001 06:02:33 -0700
Received: from sina.sharif.ac.ir ([62.41.32.2] ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QTje-0003oW-00
	for idn@ops.ietf.org; Sat, 28 Jul 2001 06:02:29 -0700
Received: from bamdad.org (IDENT:root@gilas.bamdad.org [62.41.28.76])
	by Sina.sharif.ac.ir (8.9.3/8.9.3) with ESMTP id RAA03007;
	Sat, 28 Jul 2001 17:30:48 +0430
Received: from localhost (roozbeh@localhost)
	by bamdad.org (8.11.2/8.11.2) with ESMTP id f6SD13T22002;
	Sat, 28 Jul 2001 17:31:06 +0430
X-Authentication-Warning: gilas.bamdad.org: roozbeh owned process doing -bs
Date: Sat, 28 Jul 2001 17:31:03 +0430 (IRST)
From: Roozbeh Pournader <roozbeh@sharif.edu>
X-X-Sender:  <roozbeh@gilas.bamdad.org>
To: James Seng/Personal <James@Seng.cc>
cc: John C Klensin <klensin@research.att.com>, <idn@ops.ietf.org>
Subject: Re: [idn] ZWNJ
In-Reply-To: <010601c11718$83bb03d0$dd00a8c0@jamessonyvaio>
Message-ID: <Pine.LNX.4.33.0107281714490.21040-100000@gilas.bamdad.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


On Sat, 28 Jul 2001, James Seng/Personal wrote:

> Arabic alphabets put together may have different rendering forms depends
> whether there is a break between the alphabets or not. But it is not
> neccessary a 'space' because there is no gap. Someone told me that ZWNJ
> was suggested as a way to insert this break without adding a space altho
> that was not the reason ZWNJ was there in the first place.

You have some idea. The ZWNJ is actually used in languages like Persian,
which are not Arabic (language) based, but only use the Arabic script.
Since in this languages the words are longer than Arabic words, and there
is a need to separate parts of the word. Consider the case of German:
those long words are really hard to read. Add the Arabic joinging to this,
you will surely have problems finding subword boundaries. Persian
typography then introduced ZWNJ (which is called semi-space in Persian
traditional typography) to break the words so they become readable.

<off-topic>
There are still a bunch of Nastaliq calligraphers, who do not
use the ZWNJ, to be able to create long long words which gives the
calligrapher the ability to play with the slanted baseline. People
consider this to be artistic.
</off-topic>

> btw, can arabic keyboard actually enter ZWNJ? I am asking because I
> could not find a way to do so.

On Persian keyboards, this is usally on Shift+Space (or Shift+B when the
OS can't handle the Shift+Space combination). Microsoft keyboards do not
support it, but if you're using Windows 2000, all the Arabic keyboards and
the Persian keyboard have it on Ctrl+Shift+2 (why there, don't ask me).

roozbeh




From owner-idn@ops.ietf.org  Sun Jul 29 01:52:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA14130
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:52:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QLrG-000Nvq-00
	for idn-data@psg.com; Fri, 27 Jul 2001 21:37:46 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QLrF-000Nvk-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 21:37:45 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Fri, 27 Jul 2001 21:48:12 -0700
Message-ID: <00a701c11720$3e377a20$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
References: <200107280313.f6S3D8N12323@nic-naa.net>
Subject: Re: [idn] Intro to my I-D 
Date: Sat, 28 Jul 2001 00:46:18 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Eric,

Thanks for the info.  I just looked over the drafts quite quickly and
there are many things that I agree with.  However, there is one very
important point that I strongly disagree with (no intend of disrespect
to the authors).  Is it possible for me to ask Mr.Lee a couple of
questions directly inorder to clarify something before I make my
comments?

Thanks
Ben Chan

----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: "ben" <ben@cc-www.com>
Sent: Friday, July 27, 2001 11:13 PM
Subject: Re: [idn] Intro to my I-D


Ben,

ftp to ftp.isi.edu, login anonymous; password <your-email-address>;
set prompt; cd internet-drafts; dir *idn*; mget *tsconv* *icdn*

or

http://search.ietf.org/internet-drafts/draft-ietf-idn-tsconv-00.txt
http://search.ietf.org/internet-drafts/draft-deng-idn-icdn-00.txt

Eric




From owner-idn@ops.ietf.org  Sun Jul 29 01:52:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA14144
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:52:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QLWu-000MVJ-00
	for idn-data@psg.com; Fri, 27 Jul 2001 21:16:44 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QLWt-000MVD-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 21:16:43 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id E9E20FFC04; Sat, 28 Jul 2001 12:18:24 +0800 (SGT)
Message-ID: <012601c1171c$1265d030$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
Cc: <lsb@postel.co.kr>
References: <004701c1170f$1eb34d20$ed1bd9d2@postel.co.kr>
Subject: Re: [idn] new I-D: Safely Encoding of  likeness information into ACE label   version 0.2 
Date: Sat, 28 Jul 2001 12:16:27 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Lets do a test. This email is written in UTF-8.

U+529B in UTF-8 is 力
U+30AB in UTF-8 is カ

Does it look similar? Well, to a non-native maybe. To me, given that i
know some kana and some chinese (hopefully), it is not the same.

Perhaps some may say it "looks" totally different depending what UTF-8
fonts you have. Not to mention there are different written forms of
Chinese ideograph which ends up with different fonts. (For those
interest, should read z-Variant section of the Unicode book).

Now to make it more interesting, lets take this Chinese ideograph

U+65E5 in UTF-8 日
U+66F0 in UTF-8 曰

Same? Well, they are actually very very different meaning...and used in
different ways. (Notice the first one is 'thinner'? Yes, that is how it
is written, one fatter and one thinner)

Or make how about U+6046 and U+6052? Different? Well, they are used
similarly at least when we refer to hang shang bank of HK. (Depending
what IME you use, they produce U+6046 or U+6052).

And these are not even a complete list. Lets not forget about other
languages too.

Bottomline: This is not an easy task. We need to ask ourselves in IDN WG
if we have the right expertise to do this. Honestly, if you are saying
we normalized U+529B and U+30AB, neither Chinese nor Japanese would be
very happy about it.

-James Seng

>  For example, Katakana 'ka' (U+30AB) and Chinese letter 'power'
(U+529B).
>  look the same. We can assign  likenessindex 0 and 1 to 'ka' and
'power',
>  respectively.





From owner-idn@ops.ietf.org  Sun Jul 29 01:52:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA14163
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:52:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QLRD-000MBH-00
	for idn-data@psg.com; Fri, 27 Jul 2001 21:10:51 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QLRB-000MBB-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 21:10:50 -0700
Received: from zetnet.co.uk (man-s080.dialup.zetnet.co.uk [194.247.41.207])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6S4ANr13264;
	Sat, 28 Jul 2001 05:10:24 +0100
Message-ID: <3B622C31.91AAB63B@zetnet.co.uk>
Date: Sat, 28 Jul 2001 04:06:25 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: Soobok Lee <lsb@postel.co.kr>, idn@ops.ietf.org
Subject: Re: [idn] new I-D: Safely Encoding of  likeness information into ACE 
 label   version 0.2
References: <004701c1170f$1eb34d20$ed1bd9d2@postel.co.kr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

Soobok Lee wrote:
>   Let's assume we have a unicode  look-alike normalization NFLA in the
>   future version of the unicode standard.

That's a big assumption. AFAIK there are no plans to develop such a
normalisation format. Even if there were, waiting for it would unreasonably
delay deployment of IDNs, IMHO.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO2IsBjkCAxeYt5gVAQFehggAqxqhYWYotcJd24tB895xwKCjv6Xg6pPE
ezL7AZGxv6/F/A72YxEdyiD8FL1ZtVsMkXFiEv+g6prTPU/TA2OrLz4AmOdBaZrH
lklmj8322BjNbgXiQ5EEjfyy4cFAigdVkGXghEYkLmN0PzFtmsTasRCL8ubDajhb
zdMSXyCuFj4CdhHi9rYAXd9oPwyAnN/byKoUuo2Tw4EGAHsucq6QG6lLKsufOW5d
BEWerH28Eex6PfJSxWcPxjdUOyrvq0irajxaEdX8fZsRnaCrtQi5UexdCpGVVyUw
Aspbo5oLJIEYaGp2LoRlSt82hTkbKJ6D+NSMeTuLmWCr99aeU6jjoQ==
=admj
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Sun Jul 29 01:52:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA14181
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:52:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QLAM-000L6Q-00
	for idn-data@psg.com; Fri, 27 Jul 2001 20:53:26 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QLAL-000L6J-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 20:53:26 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f6S3pHN12415;
	Fri, 27 Jul 2001 23:51:17 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107280351.f6S3pHN12415@nic-naa.net>
To: "Soobok Lee" <lsb@postel.co.kr>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE label version 0.2 
In-Reply-To: Your message of "Sat, 28 Jul 2001 11:43:44 +0900."
             <004701c1170f$1eb34d20$ed1bd9d2@postel.co.kr> 
Date: Fri, 27 Jul 2001 23:51:17 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Soobok,

Your example of U+30AB and U+529B is clear, but as you mention, most
Han/Hangeul do not have look-alike characters.

Consider a hypothetical proposal to place distinct abstract character
repertoires in disjoint blocks in some equally hypothetical standard
coded character set, and assume that some character(s) have "look-alike"
correspondences in multiple disjoint blocks.

In particular, assume that in blocks i, j, and k, there exists code-points
for the characters A(i), A(j), and A(k), and that A(i) "looks-like" A(j)
and A(j) "looks-like" A(k).

Further assume that for this property of "similarity" or "borrowing" (at
least of the visual form) in each of these blocks is unlike the case in
Han/Hangeul (sparce), and most do have look-alike characters (dense). Is
there some point at which the "non-rarity" of "look-alike" would make a
scheme such as the one you've proposed cumbersome? If so, this could be
a constraint upon future modifications of a particular CCS.

Thanks for taking the time to think about this, I know it isn't what you
had in mind when taking on the Latin/Greek and Han/Hangeul similarities.

Eric



From owner-idn@ops.ietf.org  Sun Jul 29 01:52:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA14198
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:52:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QL8G-000KrL-00
	for idn-data@psg.com; Fri, 27 Jul 2001 20:51:16 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QL8F-000Kqq-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 20:51:15 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id E2D76FFC04; Sat, 28 Jul 2001 11:52:56 +0800 (SGT)
Message-ID: <010601c11718$83bb03d0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "John C Klensin" <klensin@research.att.com>,
        "Roozbeh Pournader" <roozbeh@sharif.edu>
Cc: <idn@ops.ietf.org>
References:  <Pine.LNX.4.10.10107271440590.7928-100000@Sina.sharif. ac.ir> <4669646.996226210@KLENSIN-VAIO>
Subject: Re: [idn] Re: [idn-nameprep] Re: ZWNJ (was: Re: Just send UTF-8 with nameprep (was: RE:  [idn]Reality Check))
Date: Sat, 28 Jul 2001 11:50:59 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Of course, what seems to me, not knowing Arabic, to be a near
> equivalent, a space between words, is disallowed in the current
> naming rules and always has been.  Hence, if "Joes Pizza" goes
> into the DNS, it goes in either as "joespizza" or "joes-pizza".
> No other options.  I think this situation should be improved for
> both Arabic and English, and all other languages where it is
> relevant, but it seems to me that the perceived requirement makes
> another "not in the DNS" argument.

Arabic alphabets put together may have different rendering forms depends
whether there is a break between the alphabets or not. But it is not
neccessary a 'space' because there is no gap. Someone told me that ZWNJ
was suggested as a way to insert this break without adding a space altho
that was not the reason ZWNJ was there in the first place.

btw, can arabic keyboard actually enter ZWNJ? I am asking because I
could not find a way to do so.

-James Seng




From owner-idn@ops.ietf.org  Sun Jul 29 01:52:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA14210
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:52:52 -0400 (EDT)
From: owner-idn@ops.ietf.org
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QKwz-000KEP-00
	for idn-data@psg.com; Fri, 27 Jul 2001 20:39:37 -0700
Message-Id: <E15QKwz-000KEP-00@psg.com>
To: idn-data@psg.com
Date: Fri, 27 Jul 2001 20:39:37 -0700

Fri, 27 Jul 2001 22:49:33 +0100
Date: Fri, 27 Jul 2001 21:45:27 +0100
From: David Hopwood <hopwood@zetnet.co.uk>
To: Roozbeh Pournader <roozbeh@sharif.edu>, idn@ops.ietf.org
Subject: Re: [idn] Common-case optimization of nameprep - correction
Sender: owner-idn@ops.ietf.org
Precedence: bulk

-----BEGIN PGP SIGNED MESSAGE-----

Roozbeh Pournader wrote:
> On Fri, 27 Jul 2001, David Hopwood wrote:
>
> > This should be:
> >    - characters for which the NFKC_QuickCheck flag in
> >      DerivedNormalizationProperties-3_1_0.txt is either NFKC_NO or
NFKC_MAYBE.
>
> I think refering to Unicode data files other than the originals is a
bad
> thing.

It would not be a normative reference: the information would be used to
calculate the set X, and that set would be given in the nameprep spec.
This causes no problems because each version of nameprep corresponds to
a
specific version of Unicode.

> The format will change, the level of information they provide will
change,
> ...
>
> For example, take a look at what happened to 'PropList.txt' between
3.0.1:
>
>         http://www.unicode.org/Public/3.0-Update1/PropList-3.0.1.txt
>
> and 3.1.0:
>
>         http://www.unicode.org/Public/3.1-Update/PropList-3.1.0.txt

The latter is the standard machine readable format used by all the
Unicode
files; the former isn't, so it's obvious why the format changed in this
case.

- --
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15
01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has
been
seized under the Regulation of Investigatory Powers Act; see
www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO2HSrTkCAxeYt5gVAQElJQf/VF9zF0mCSP84dMV5yQE9/dpHsaZRciFl
9QdYHHIcWN4mXITv+fDFvCaF3ATb7UR+r8GFhVuqmCkkYAI2ePrcc+XfKntmsn+G
0ZinLKF5MMs+rTD6R06TrT5EAAk/czx/GOYGDfNq6HPuU2WQsNXJ1uaS9BHofNCB
Ml/jdv2eHuxSO1HHkrG3CP6r7wfPfCpZHDu9VWGWrC/OuVN6Yko/68D0N0unjqyZ
jTHhryv+WlXpTfWKQNF08egf0xywb/dh1SaYEU/b83LR0HtR4XK1o0qUgGTWVMP+
TnrYSO9KMybgjGczO05blR2MbDG6r06kP2vJ5twEbN/5P6HP84tCHw==
=QoV0
-----END PGP SIGNATURE-----





From owner-idn@ops.ietf.org  Sun Jul 29 01:52:54 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA14229
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:52:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QKGe-000Ha2-00
	for idn-data@psg.com; Fri, 27 Jul 2001 19:55:52 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QKGd-000HZv-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 19:55:51 -0700
Received: from enoshima (e147197.ppp.asahi-net.or.jp [211.13.147.197])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id LAA02079;
	Sat, 28 Jul 2001 11:55:41 +0900 (JST)
Message-Id: <4.2.0.58.J.20010727113140.009ea540@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 27 Jul 2001 11:33:36 +0900
To: Mark.Andrews@nominum.com, Yves Arrouye <yves@realnames.com>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Forbidden characters 
Cc: idn@ops.ietf.org
In-Reply-To: <200107270211.f6R2BDu48396@drugs.dv.isc.org>
References: <Your message of "Thu, 26 Jul 2001 18:31:41 MST." <B7233BD6980AD411875700508B5BD5D2011E975B@elporto.internal.realnames.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 12:11 01/07/27 +1000, Mark.Andrews@nominum.com wrote:

> > Again, they are not forbidden. They can be used as input. What is not clear
> > (and controversial here) is whether you will ever get them back or not when
> > you decode the ACE. Some ACE preserve case. But normalization can't be
> > undone, so as you said, the name service cannot return them. We won't get
> > about adding a new RR for that here, but while I am for preserving case but
> > may live without it (after all, DNS names are not pretty, if I want
> > prettiness I'll use a layer above it), Roozbeh's comments about Arabic 
> names
> > becoming different to their reader because of spontaneous joining of glyphs
> > certainly may spark some thinking.
> >
> > YA
> >
>         We have the same problem in English today.

Yes and no. In Arabic, you cannot just put together two words as you
can in English; if you do that, then cursive joining kicks in and
you may get another word (same as below) or something completely
unreadable.

Regards, Martin.



>         Say I had a store called "To Get Her Gifts".  Smashing the
>         word together to get a domain name might not be what you
>         what, e.g. togethergifts.com.  Especially if next door is
>         "Together Gifts".
>
>         There are also plenty of cases where a made up word in one
>         language turns out to be a real word in a different language.
>
>         You need to think before you register / create a domain name,
>         not just run on automatic pilot.
>
>         Mark
>--
>Mark Andrews, Nominum Inc.
>1 Seymour St., Dundas Valley, NSW 2117, Australia
>PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@nominum.com




From owner-idn@ops.ietf.org  Sun Jul 29 01:52:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA14239
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:52:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QJzL-000GX4-00
	for idn-data@psg.com; Fri, 27 Jul 2001 19:37:59 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QJzK-000GUx-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 19:37:58 -0700
Received: from soobok ([210.217.27.237] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id LAA20071;
	Sat, 28 Jul 2001 11:37:46 +0900
Message-ID: <004701c1170f$1eb34d20$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Cc: <lsb@postel.co.kr>
Subject: [idn] new I-D: Safely Encoding of  likeness information into ACE label   version 0.2 
Date: Sat, 28 Jul 2001 11:43:44 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,
I post this new I-D to this mailing list to be reviewed  before
14/AUG. This I-D is somewhat half-baked, but helps to solve
the problems of look-alike characters with some pains.
I will repost the revised one next week.

Welcome any criticisms and supports for further discussions.

Regards,

Soobok Lee, lsb@postel.co.kr

=========================================================================
Internet Draft                                              Soobok Lee
draft-lsb-lookalike-00.txt                        Postel Services, Inc
28 Jul, 2001
Expires in six months


        Safely Encoding of likeness information into ACE label
                        version 0.2


Status of this Memo

    This document is an Internet-Draft and is in full conformance with
    all provisions of Section 10 of RFC2026.

    Distribution of this document is unlimited.  Please send comments to
    the author lsb@postel.co.kr


Abstract

  For a unicode character which has one or more other look-alike characters,
  we define both its look-alike normalization form and a likeness index and
  suggest new ACE prefixing rule for likeness indices which are encoded using
  a sequence of mixed-case latin alphabets. The likeness index is used to
  restore the pre-normalization form of the ACE-decoded label and in the same
  time does not affect case-insensitive label comparison 
  in existing applications and DNS servers.


Contents

 Overview
 ACE comparison
 Maximum length of ACE label
 Implication of restoring pre-normaliation forms
 More works to be done
 Security considerations
 References
 Author


Overview

 The Unicode Standard has many sets of look-alike characters that are not
 documented in detail yet. But introducing the unicode characters set
 into IDN, the primary internet identifier, require some rigorous works
 to be done in this area near future for security reasons.

 ACE algorithms such as [DUDE],[AMC-ACE-Z], preserve the case information
 in the original IDN label by augmenting base32 latin digits to their
 uppercase ones, which do not affect case-insensitive label comparison
 operations in applications and DNS servers, while preserving the case
 information.

 This draft is based on such case-preserving and case-insensitive nature
 of IDNA architecture and extends them to fullful the need to map
 look-alike letters into a unified one while retaining the information
 about the pre-unification letter for later rendering of ACE-decoded
 labels for end users.

  Let's assume we have a unicode  look-alike normalization NFLA in the future
  version of the unicode standard.

  For certain unicode points a1,a2,a3 that satisfy
     NFLA(a1) ==NFLA(a2)  == NFLA(a3) == a1.
  let's define a function LA_SET(uc) so that:
     LA_SET(a1)={a1,a2,a3}

  In this case
     the size of LA_SET(a1) is 3, is called 'current minimal likeness size',
 
  We shoud define 'maximal likeness size' for each unicode point. 
  For that, we define a function LikeSize(uc) so that
     LikeSize(a1) = 4, LikeSize(a2)= 4, LIkeSize(a3)=4.

  It is wise to choose 4 instead of 3  to make room for future additions 
  to UNICODE repertoire of scripts that may contain new look-alike characters.
  We need to look carefully into proposed or approved new scripts to be added
  unicode standards near future.
   

  We can express a1,a2,a3  as  these binary tuples
   a1=(a1,0)
   a2=(a1,1)
   a3=(a1,2)
  The each second index value of these tuples is called 'likeness index',
  for which we define a function so that
    LikeIndex(a1) =  0,
    LikeIndex(a2) =  1,
    LikeIndex(a3) =  2.

  Let's define a function
    LA_TUPLE(uc) = ( NFLA(uc), LikeIndex(uc), LikeSize(LA_SET(uc))  ).

  Let's define a restoring function LA_CHAR(uc,i)  so that:
    LA_CHAR(a1,0)=a1,
    LA_CHAR(a1,1)=a2,
    LA_CHAR(a1,2)=a3.


 The main idea of this draft is to incorporate the ascii encoded likeness
 index and likeness size of a ambiguous character of a IDN label
 using a sequence of uppercase and lowercase latin alpahbets inserted after
 ACE prefix.

 For example, for an cyrillic IDN label <cyrillic a><cyrillic zhe><cyrillic o>:
 we have a ACE label without looka-like normalization of

    dq--{<cyrillic a>}{cyrillic zhe}{<cyrillic o>}

 Only cyrillic 'a' and 'o' has latin look-alikes, so that we can make
 new ACE label WITH  looka-like normalization

    dq--AaCcC--{<latin a>}{cyrillic zhe}{<latin o>}

 The uppercase letters in "aAcCc" denote bit '1' and
 lowercase letters denote bit '0' and these sequence of uppercase and lower
 case letters of a alphabet form a bitstring to denote the likeness index.
 The alpabet (a-z) denotes the offset index of the corresponding unicode
 character in the IDN label character sequence.

 In the example above, "aA" denote a likeness index value 1 and a likeness
 size 4. "cCc" denote a likeness index value 2 and a likeness size 8.
 "aA" supplements to <latin a> to form <cyrillic a> and
 "cCc" supplements to <latin o> to form <cyrillic o>.
 <cyrillic zhe> has no case information since it is assumed to have no
lookalike..

 2^(The number of repeated alphabets) is identical to the likeness size and
 shall be large enough not to be changed in future version of unicode
 look-alike normalization.

 If the offset index of a long IDN label needs to exceed 26, we can insert
 un-used digit '9' to mark a milestone from which the offset is added by 26
 and the alphbet should begin with 'a' again.

 If applications and dns server would not casefold ACE label, this
 look-alike information would be retained throught the process to
 restore the pre-normalization native-script.

 The restoring process is as follows:

  First,
   we ACE-decode the label part of our new ACE label and get
   a sequence of unicode points LABEL.

  Second,
   from likeness indices part of our new ACE label, we construct
   a array of binary tuples of likeness index and offset index of
   target character into the decoded label LABEL.

  Third,
   for each binary tuple (i,offset), we replace each target
   code point in the decoded label LABEL with the restored original
   character LA_CHAR(LABEL[offset],i).


ACE comparison

  We have three IDN labels like these:

    IDN1 =  <cyrillic a><cyrillic zhe><cyrillic o>
    IDN2 =  <latin a><cyrillic zhe><cyrillic o>
    IDN3 =  <latin a><cyrillic zhe><latin o>

    ACE(IDN1)  =  dq--aAcCc--{<latin a>}{cyrillic zhe}{<latin o>}
    ACE(IDN2)  =  dq--aacCc--{<latin a>}{cyrillic zhe}{<latin o>}
    ACE(IDN3)  =  dq--aaccc--{<latin a>}{cyrillic zhe}{<latin o>}

  IDN1,IDN2,IDN3 are equivalent modulo look-alike normalization,
  but these three ACE labels have differently-cased likeness indices,
  but are regarded as the same domain in case-insensitive comparison
  in applications and dns servers.

  If a IDN has no ambiguous characters, we can omit '--' in some ACEs.

   IDN4 =  <cyrillic zhe><cyrillic zhe>
   ACE(IDN4)  =  dq--{<cyrillic zhe>}{cyrillic zhe}

  And if an IDN is look-alike normalized into all-latin LDH domain,
  it should not be registered as a IDN but as an LDH domain, and in
  this case, we cannot provide likeness preservation.



Maximum length of ACE label

 This new scheme comes with some overheads in ACE label :
   additional "--" and encoded likeness informations.

 If we assume the mean average of likeness size to be 2 (1 bit):
   overhead  = 2 + 1 * (number of ambiguous characters in a label)

 Since most Han/Hangeul letters have no other look-alike characters,
 Overall ACE label efficiency for han/hangeul would not be affected.

 Latin,Greek,Cyrillic,Katakana and many Indian scripts have
 many look-alike characters.

 Efficient ACE-encoding of IDN label is required for this scheme.



Implication of restoring pre-normalization forms

 This new ACE prefixing scheme retains the look-alike information,
 so that we can restore the original native-script labels before
 look-alike normalization even when they contain  look-alike characters
 across scripts.


 For example, Katakana 'ka' (U+30AB) and Chinese letter 'power' (U+529B).
 look the same. We can assign  likenessindex 0 and 1 to 'ka' and 'power',
 respectively.

 If we normalized 'ka' into 'power' without encoded case information,
 we could not restore 'ka' anymore. We could not avoid font-rendering
 problems and conflicts of interests between related countries.

 But, with this encoded likeness information, we can restore 'ka'
 and we have no such problem.


More works to be done

 Some sequences of characters look similiar to a character or
 other sequences of characters.

 Most of these sequences are normalized and unified in KC
 Normalization in NAMEPREP. But still some visual similarities
 are not completely eliminated.

 We need more elaborations on this subject.



Security Consideration

 These scheme suggests ACE labels to be prefixed  by additional
 look-alike information encoded in sequences of cased alphabets
 and does not introduce any security hole into IDN.


References

    [UNICODE] The Unicode Consortium, "The Unicode Standard",
    http://www.unicode.org/unicode/standard/standard.html.

    [IDNA] Patrik Faltstrom, Paul Hoffman, "Internationalizing Host
    Names In Applications (IDNA)", draft-ietf-idn-idna-03.

    [NAMEPREP03] Paul Hoffman, Marc Blanchet, "Preparation
    of Internationalized Host Names", July 19, 2001
    draft-ietf-idn-nameprep-05.

    [DUDE02] Mark Welter, Brian Spolarich, Adam Costello,
    "DUDE: Differential Unicode Domain Encoding", 2001-May-31,
    draft-ietf-idn-dude-02.

    [AMCACEZ] Adam Costello, "AMC-ACE-z version 0.2.1",
    2001-May-31, draft-ietf-idn-amc-ace-z-00, latest version at
    http://www.cs.berkeley.edu/~amc/charset/amc-ace-z.gz


Author

    Soobok Lee <lsb@postel.co.kr>
    Postel Services, Inc.
    http://www.postel.co.kr
    Tel: +82-11-9774-2737









From owner-idn@ops.ietf.org  Sun Jul 29 01:52:56 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA14256
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:52:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QIoB-000C7l-00
	for idn-data@psg.com; Fri, 27 Jul 2001 18:22:23 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QIoB-000C7f-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 18:22:23 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Fri, 27 Jul 2001 18:32:50 -0700
Message-ID: <001101c11704$f2976280$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "David Leung" <david@neteka.com>, <idn@ops.ietf.org>
References: <003d01c116d7$39b7a180$d43f7018@mtag1.on.home.com> <00d401c116d9$cae2f3b0$0b01a8c0@davidvaio>
Subject: Re: [idn] Intro to my I-D
Date: Fri, 27 Jul 2001 21:30:54 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000E_01C116E3.6ADDE9C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_000E_01C116E3.6ADDE9C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi David,

Can you tell me where to find the I-D?

Thanks,
Ben Chan

----- Original Message -----=20
From: David Leung=20
To: ben ; idn@ops.ietf.org=20
Sent: Friday, July 27, 2001 4:21 PM
Subject: Re: [idn] Intro to my I-D


I think there is already an Internet Draft on SC-TC(Simplified Chinese =
and Traditional Chinese) folding.

  ----- Original Message -----=20
  From: ben=20
  To: idn@ops.ietf.org=20
  Sent: Friday, July 27, 2001 4:03 PM
  Subject: [idn] Intro to my I-D


  It appears that I-D will not be accepted til Aug 14, so there is =
plenty of time for me to prepare it.  But anyways, here is a very simple =
intro to why I am interested in "the need for conversion between =
different (yet similiar) scripts":

  I have a very small company that offers CDNs (Chinese domain names).  =
My hope is to be able to take the benefits from other systems and =
combine them together to form a supreme.  (Although I want to emphasize =
that other systems are 100% fine exactly the way they are.)  Combining =
the following 2 benefits together is crucial to my supreme system with =
both weighting EXACTLY THE SAME IMPORTANCE:

  Benefit A-  A simplified CDN points to a website that is written in =
simplified Chinese (GB encoding) for visitors in mainland China or =
Singapore while a traditional CDN points to a website written in =
traditional Chinese (Big5 encoding) for visitors in Taiwan or Hong Kong.

  Benefit B-  When a registrant registers a simplified CDN, the =
corresponding traditional CDN(s) is automatically reserved and visa =
versa.

  I will put all the details into the draft and submit it by Aug 14.  =
Hopefully, I can get 7 supporters- thank you very much!

  Ben Chan


------=_NextPart_000_000E_01C116E3.6ADDE9C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4616.200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>
<DIV><FONT face=3DArial size=3D2>Hi David,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Can you tell me where to find the =
I-D?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Ben Chan</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></DIV>
<DIV style=3D"FONT: 10pt arial">----- Original Message -----=20
<DIV style=3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A=20
title=3Ddavid@neteka.com href=3D"mailto:david@neteka.com">David =
Leung</A> </DIV>
<DIV><B>To:</B> <A title=3Dben@cc-www.com =
href=3D"mailto:ben@cc-www.com">ben</A> ;=20
<A title=3Didn@ops.ietf.org =
href=3D"mailto:idn@ops.ietf.org">idn@ops.ietf.org</A>=20
</DIV>
<DIV><B>Sent:</B> Friday, July 27, 2001 4:21 PM</DIV>
<DIV><B>Subject:</B> Re: [idn] Intro to my I-D</DIV></DIV>
<DIV><BR></DIV>
<DIV><FONT face=3DArial size=3D2>I think there is already an Internet =
Draft on=20
SC-TC(Simplified Chinese and Traditional Chinese) folding.</FONT></DIV>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dben@cc-www.com href=3D"mailto:ben@cc-www.com">ben</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Didn@ops.ietf.org =

  href=3D"mailto:idn@ops.ietf.org">idn@ops.ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Friday, July 27, 2001 =
4:03 PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [idn] Intro to my =
I-D</DIV>
  <DIV><BR></DIV>
  <DIV><FONT face=3DArial size=3D2>It appears that I-D will not be =
accepted til Aug=20
  14, so there is plenty of time for me to prepare it.&nbsp; But =
anyways, here=20
  is a very simple intro to why I am interested in&nbsp;"the need for =
conversion=20
  between different (yet similiar) scripts":</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>I have a very small company that =
offers CDNs=20
  (Chinese domain names).&nbsp;&nbsp;My&nbsp;hope is to be able to =
take&nbsp;the=20
  benefits&nbsp;from other systems and combine them together to form a=20
  supreme.&nbsp; (Although I want to emphasize that other systems are =
100% fine=20
  exactly the way they are.)&nbsp;&nbsp;Combining the&nbsp;following 2 =
benefits=20
  together&nbsp;is crucial to my supreme system with both weighting =
EXACTLY THE=20
  SAME IMPORTANCE:</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Benefit&nbsp;A-&nbsp; A simplified =
CDN points to=20
  a website that is written in simplified Chinese (GB encoding) for =
visitors in=20
  mainland China or Singapore while a traditional CDN points to a =
website=20
  written&nbsp;in traditional Chinese&nbsp;(Big5 encoding) for visitors =
in=20
  Taiwan or Hong Kong.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Benefit B-&nbsp; When a registrant =
registers a=20
  simplified CDN, the corresponding traditional CDN(s) is automatically =
reserved=20
  and visa versa.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>I will put all the details into the =
draft and=20
  submit it by Aug 14.&nbsp; Hopefully, I can get 7 supporters- thank =
you very=20
  much!</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Ben Chan</FONT></DIV>
  <DIV><FONT face=3DArial =
size=3D2></FONT>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_000E_01C116E3.6ADDE9C0--




From owner-idn@ops.ietf.org  Sun Jul 29 01:52:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA14271
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:52:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QIqg-000C9q-00
	for idn-data@psg.com; Fri, 27 Jul 2001 18:24:58 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QIqg-000C9k-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 18:24:58 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Fri, 27 Jul 2001 18:35:25 -0700
Message-ID: <001901c11705$4f560f80$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>, <brunner@nic-naa.net>
References: <200107280019.f6S0JbN11849@nic-naa.net>
Subject: Re: [idn] Intro to my I-D 
Date: Fri, 27 Jul 2001 21:33:27 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Eric,

My apologies... can you tell me where to find the drafts?  I am new
here.

Thanks
Ben Chan


----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: "ben" <ben@cc-www.com>
Cc: <idn@ops.ietf.org>; <brunner@nic-naa.net>
Sent: Friday, July 27, 2001 8:19 PM
Subject: Re: [idn] Intro to my I-D


Ben,

Please see the following:

Traditional and Simplified Chinese Conversion, by Lee, XiaoDong, et
al,
draft-ietf-idn-tsconv-00.txt

and also

The Implementation of Chinese character in IDN, by Deng Xiang and Wang
Yan
Fang,
draft-ietf-idn-icdn-00.txt

If I may comment on your statement of benefits:

A) Using the sole, or dominant encoding used for data accessible via
http
(or ftp, or telnet, or ...) as a means of selecting which encoding to
use
for the dns label associated with the data (or endpoint from which the
data
may be accessed) is only one of many "guides for implementors" (or in
this
case, for site encoding and label selection), and

B) Equivalence classes (or duplicate A records or ... ) for labels is
more
interesting when mechanism details are offered, both for the
"equivalence"
offered, and for the reservation algorithm(s) employed.

Please do comment on the drafts by Lee and Deng.

Eric






From owner-idn@ops.ietf.org  Sun Jul 29 01:52:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA14290
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:52:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QHrO-0008Xh-00
	for idn-data@psg.com; Fri, 27 Jul 2001 17:21:38 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QHrN-0008Xa-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 17:21:37 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f6S0JbN11849;
	Fri, 27 Jul 2001 20:19:37 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107280019.f6S0JbN11849@nic-naa.net>
To: "ben" <ben@cc-www.com>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Intro to my I-D 
In-Reply-To: Your message of "Fri, 27 Jul 2001 16:03:37 EDT."
             <003d01c116d7$39b7a180$d43f7018@mtag1.on.home.com> 
Date: Fri, 27 Jul 2001 20:19:37 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Ben,

Please see the following:

Traditional and Simplified Chinese Conversion, by Lee, XiaoDong, et al,
draft-ietf-idn-tsconv-00.txt

and also

The Implementation of Chinese character in IDN, by Deng Xiang and Wang Yan
Fang,
draft-ietf-idn-icdn-00.txt

If I may comment on your statement of benefits:

A) Using the sole, or dominant encoding used for data accessible via http
(or ftp, or telnet, or ...) as a means of selecting which encoding to use
for the dns label associated with the data (or endpoint from which the data
may be accessed) is only one of many "guides for implementors" (or in this
case, for site encoding and label selection), and

B) Equivalence classes (or duplicate A records or ... ) for labels is more
interesting when mechanism details are offered, both for the "equivalence"
offered, and for the reservation algorithm(s) employed.

Please do comment on the drafts by Lee and Deng.

Eric



From owner-idn@ops.ietf.org  Sun Jul 29 01:53:01 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA14314
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 01:53:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QDhS-000JPJ-00
	for idn-data@psg.com; Fri, 27 Jul 2001 12:55:06 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QDhR-000JPD-00
	for idn@ops.ietf.org; Fri, 27 Jul 2001 12:55:06 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net for <idn@ops.ietf.org>;
          Fri, 27 Jul 2001 13:05:33 -0700
Message-ID: <003d01c116d7$39b7a180$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: <idn@ops.ietf.org>
Subject: [idn] Intro to my I-D
Date: Fri, 27 Jul 2001 16:03:37 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0038_01C116B5.B2181960"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0038_01C116B5.B2181960
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

It appears that I-D will not be accepted til Aug 14, so there is plenty =
of time for me to prepare it.  But anyways, here is a very simple intro =
to why I am interested in "the need for conversion between different =
(yet similiar) scripts":

I have a very small company that offers CDNs (Chinese domain names).  My =
hope is to be able to take the benefits from other systems and combine =
them together to form a supreme.  (Although I want to emphasize that =
other systems are 100% fine exactly the way they are.)  Combining the =
following 2 benefits together is crucial to my supreme system with both =
weighting EXACTLY THE SAME IMPORTANCE:

Benefit A-  A simplified CDN points to a website that is written in =
simplified Chinese (GB encoding) for visitors in mainland China or =
Singapore while a traditional CDN points to a website written in =
traditional Chinese (Big5 encoding) for visitors in Taiwan or Hong Kong.

Benefit B-  When a registrant registers a simplified CDN, the =
corresponding traditional CDN(s) is automatically reserved and visa =
versa.

I will put all the details into the draft and submit it by Aug 14.  =
Hopefully, I can get 7 supporters- thank you very much!

Ben Chan


------=_NextPart_000_0038_01C116B5.B2181960
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4616.200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>It appears that I-D will not be =
accepted til Aug=20
14, so there is plenty of time for me to prepare it.&nbsp; But anyways, =
here is=20
a very simple intro to why I am interested in&nbsp;"the need for =
conversion=20
between different (yet similiar) scripts":</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I have a very small company that offers =
CDNs=20
(Chinese domain names).&nbsp;&nbsp;My&nbsp;hope is to be able to =
take&nbsp;the=20
benefits&nbsp;from other systems and combine them together to form a=20
supreme.&nbsp; (Although I want to emphasize that other systems are 100% =
fine=20
exactly the way they are.)&nbsp;&nbsp;Combining the&nbsp;following 2 =
benefits=20
together&nbsp;is crucial to my supreme system with both weighting =
EXACTLY THE=20
SAME IMPORTANCE:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Benefit&nbsp;A-&nbsp; A simplified CDN =
points to a=20
website that is written in simplified Chinese (GB encoding) for visitors =
in=20
mainland China or Singapore while a traditional CDN points to a website=20
written&nbsp;in traditional Chinese&nbsp;(Big5 encoding) for visitors in =
Taiwan=20
or Hong Kong.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Benefit B-&nbsp; When a registrant =
registers a=20
simplified CDN, the corresponding traditional CDN(s) is automatically =
reserved=20
and visa versa.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I will put all the details into the =
draft and=20
submit it by Aug 14.&nbsp; Hopefully, I can get 7 supporters- thank you =
very=20
much!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Ben Chan</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0038_01C116B5.B2181960--




From owner-idn@ops.ietf.org  Sun Jul 29 03:14:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA01465
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 03:14:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QkKX-000BZi-00
	for idn-data@psg.com; Sat, 28 Jul 2001 23:45:37 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QkKW-000BZS-00
	for idn@ops.ietf.org; Sat, 28 Jul 2001 23:45:36 -0700
Received: from soobok ([210.217.27.237] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id PAA26506;
	Sun, 29 Jul 2001 15:45:15 +0900
Message-ID: <002901c117fa$d0c63cc0$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <James@Seng.cc>, <idn@ops.ietf.org>
References: <004701c1170f$1eb34d20$ed1bd9d2@postel.co.kr> <012601c1171c$1265d030$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] new I-D: Safely Encoding of  likeness information into ACE label   version 0.2 
Date: Sun, 29 Jul 2001 15:50:54 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message ----- 
From: "James Seng/Personal" <James@Seng.cc>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
 > Now to make it more interesting, lets take this Chinese ideograph
> 
> U+65E5 in UTF-8 ??
> U+66F0 in UTF-8 ??
> 
 > Or make how about U+6046 and U+6052? Different? Well, they are used
> similarly at least when we refer to hang shang bank of HK. (Depending
> what IME you use, they produce U+6046 or U+6052).
> 

Even If we normalize U+6046 into U+6052 ( or U+30AB -> U+529B ),
my I-D's likeness encoding will allow recover U+6046 (or U+30AB) 
as long as applications do not casefold the produced ACE label.

Likeness encoding prohibits  look-alike domains to be registered automatically
, while it allows  multiple representations of an IDN to be typed in and 
interchanged and displayed. 

With likeness encoding, look-alike normalization is not so expensive.
 
> 
> Bottomline: This is not an easy task. We need to ask ourselves in IDN WG
> if we have the right expertise to do this.   

I agree it will take much time.  
But I oppose to give birth to "immuno-deficient" premature IDN standard.
We or other relevant organizations should hurry up for it. 

Soobok Lee


> -James Seng
 




From owner-idn@ops.ietf.org  Sun Jul 29 03:59:19 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA09716
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 03:59:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ql6V-000D3Y-00
	for idn-data@psg.com; Sun, 29 Jul 2001 00:35:11 -0700
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ql6B-000D30-00
	for idn@ops.ietf.org; Sun, 29 Jul 2001 00:34:56 -0700
Received: from deng ([159.226.7.68]) by whale.cnnic.net.cn
          (Netscape Messaging Server 4.15) with SMTP id GH854T00.P7P; Sun,
          29 Jul 2001 15:36:29 +0800 
Message-ID: <009d01c117ff$d90d9590$4407e29f@deng>
From: "xiang deng" <deng@cnnic.net.cn>
To: "wenhui zhang" <zwh6810@yahoo.com>, "ben" <ben@cc-www.com>,
        "John C Klensin" <klensin@jck.com>
Cc: <idn@ops.ietf.org>
References: <20010729031829.25658.qmail@web5505.mail.yahoo.com>
Subject: Re: [idn] Intro to my I-D
Date: Sun, 29 Jul 2001 15:26:56 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by ietf.org id DAA09716

Dear Ben:
I'm apologies of missing "o"  from "Hello".

Best regards.
Deng Xiang

----- Original Message ----- 
From: "wenhui zhang" <zwh6810@yahoo.com>
To: "ben" <ben@cc-www.com>; "John C Klensin" <klensin@jck.com>
Cc: <idn@ops.ietf.org>
Sent: Sunday, July 29, 2001 11:18 AM
Subject: Re: [idn] Intro to my I-D


> hell Ben:
> 
>   I am wenhui from CNNIC, you can reach me via
> zwh6810@yahoo.com or zwh@cnnic.net.cn.
>   Our two drafts are as follows:
> http://www.i-d-n.net/draft/draft-ietf-idn-tsconv-00.txt
> 
>   
>   
> Wenhui
> 
> --- ben <ben@cc-www.com> wrote:
> > Hi John,
> > 
> > Thanks for your suggestion, I will do that.
> > 
> > By the way, fyi, under my supreme CDN system... a
> > registrant has the
> > choice of pointing the Simplified CDN and the
> > Traditional CDN both to
> > the same location OR to different locations.  (If
> > you still don't
> > understand... things will be more detailed / clear
> > when my draft comes
> > out.)
> > 
> > Thanks
> > Ben
> > 
> > ----- Original Message -----
> > From: "John C Klensin" <klensin@jck.com>
> > To: "ben" <ben@cc-www.com>
> > Cc: <idn@ops.ietf.org>
> > Sent: Saturday, July 28, 2001 12:14 PM
> > Subject: Re: [idn] Intro to my I-D
> > 
> > 
> > 
> > Ben (and David and Eric),
> > 
> > It seems to me that a high-level summary of the
> > difficulty here
> > is that you want to treat Simplified and Traditional
> > Chinese as
> > different so that you can assign semantics (e.g.,
> > different web
> > sites written respectively in the two forms) to the
> > two writing
> > styles.  Our CNNIC colleagues believe that
> > Simplified and
> > Traditional writing forms to express the same word
> > should be
> > treated as equivalent and mapped into each other.
> > 
> > That is very fundamental; we can't have it both ways
> > in the DNS
> > (although one can imagine "treat these alike and see
> > what is
> > found" instructions to a search system).  As I
> > understand what
> > they have said, mixtures of simplified and
> > traditional systems
> > within a given phrase are also possible, which
> > eliminates the
> > simplification you propose of automatically
> > registering "both"
> > forms.
> > 
> > I agree with David and Eric that you should
> > carefully examine
> > the Lee and Deng drafts.  But, since there seems to
> > be a more
> > basic philosophical difference here, I suggest that
> > you try to
> > work with them to understand each other's positions
> > and see if
> > some collectively acceptable position can be found.
> > 
> >     john
> > 
> > 
> > 
> > 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Make international calls for as low as $.04/minute with Yahoo! Messenger
> http://phonecard.yahoo.com/


--------------------------------------------------------------------------------


Internet Draft                                     Authors: Xiang Deng
<draft-ietf-idn-icdn-00.txt>                                Yan Fang Wang     
July , 2001                                                    
Expires in six months                                    
                                                           
                                                           
                                                           
                                                              
       The Implementation of Chinese character in IDN

Status of this Memo

This document is an Internet-Draft and is in full conformance with all 
provisions of Section 10 of RFC2026.

Internet-Drafts are working documents of the Internet Engineering Task 
Force (IETF), its areas, and its working groups. Note that other groups 
may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months 
and may be updated, replaced, or obsoleted by other documents at any 
time. It is inappropriate to use Internet-Drafts as reference material 
or to cite them other than as "work in progress."

    The list of current Internet-Drafts can be accessed at
    http://www.ietf.org/ietf/1id-abstracts.txt

    The list of Internet-Draft Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html

Terminology

The key words "MUST", "SHALL", "REQUIRED", "SHOULD", "RECOMMENDED", and
"MAY" in this document are to be interpreted as described in RFC 2119
[RFC2119].

Abstract

This document mainly talks about Chinese characters and two proposed 
schemes of implemention based on [IDNREQ] and [NAMEPREP],though 
there are some differences among them.The distinction between these two schemes 
is the position of the implementation function:
    -- client side processing 
or 
    -- server side processing

In China, the most popular character set are [GBK],[BIG5],[GB18030],while
in this document,all examples are based on [UCS].


1.  Charateristics of Chinese characters and Chinese languange
1.1 The context dependent semantics of Chinese characters 
    In [UCS],each Chinese character is a codepoint,which is composed of two
    bytes.
    
    Chinese character can be classified as two groups. In one group,each
    character does its own meaning(notional character) while that of the
    other group has not(empty characters). Both notional characters and
    empty characters can be made words by combining with other 
    character(s),even sentences. the notional character 
    is the basic unit of Chinese language which has meaning similar to phonems.
    
1.2 A Chinese characters may have several writing forms.
    
    Chinese characters were continuously evolved and widely spread during
    5,000-year-long Chinese history. They were also largely introduced 
    into other countries and became a major component of their languages.
    Therefore, it is inevitably for a Chinese character has many other
    writing forms. In Unicode encoding standards, the criterion for
    distributing codepoint is the shape of character. So the different 
    glyph of the same Chinese character have several different 
    codepoint according to the international encoding standard.
    
    Currently,there are two forms of writing Chinese character:
      -- simplified character(SC): mainland of China
      -- traditional character(TC): Taiwan,Hongkong,Macao
    
    Except for some special writing forms of certain character, their 
    meaning had also been changed in the long history. Generally different
    writing forms of a Chinese character can substituted by each other 
    without changing the meaning of the word(phrase).    
 
   
1.3 The Usage of Appellation in China
    In China, Generally speaking,every companies,organizations and people
    have two names: full name and abbreviation.
    
    The abbreviated name is easy to remember and to communicate.The full
    name is a formal name which is used in formal document,situation.
    
    To the name owners,the two names are equal necessary and important. 
    So,in domain name registration,they usually register both full name 
    and the corresponding abbreviations in order to permit people to access
    the same domain name by typing the full name or the abbreviatied name.
    Some of the full names are quite long,that's why the length of domain 
    name is important for Chinese user.


2. Chinese characters in DNS
1.1 Traditional and Simplified Chinese Conversion has 3 forms:
    1-1 mapping: one traditional character(TC) maps to ONLY one simplified
                 characer(SC).
    1-n mapping: one TC has several SC writing forms 
    n-1 mapping: one SC has several forms of TC

1.2 Delimiter folding
    The full stop in chinese is "¡£". Therefore, the "¡£" in CDNS is equal 
    to the dot "." as the delimiter.

1.3 Label sequence
   Currently,the label sequence of LDH domain name is from left to right,
   (e.g.:abc.def.ghi.net),the subdomain is to the left and the superset 
   of the subdomain is to the right.
   
   In China,user has reverse convention of language. Considering the 
   culture different between the east and the west, it's necessary for
   people to access the Internet with the convention of using their native
   languages.for example:
   
        CDNLabel1.CDNLabel2.cn 
   perfer to :
        cn.CDNLabel2.CDNLabel1
         
   


3. Solutions  
3.1 Client side solution 

    +-----------------------------------------------+
    |                  user input     |
    +-----------------------------------------------+
   |       ^
   V       |
+-------------------+       |
| Delimiter folding |       |
|    "¡£" -> "."    |       |
+-------------------+       |
   |       | 
   V       | 
    +------------------------------+ +------------------------------+
    | label sequence normalization | | label sequence normalization |
    +------------------------------+ +------------------------------+
   |       ^
   V       | 
        +----------------------+     +----------------------+
  | local encoding ->UCS |    | UCS ->local encoding |
        +----------------------+    +----------------------+
     |       ^
     V       | 
       +------------------------+   +------------------------+
       | local mapping (TC - SC)|   | local mapping (TC - SC)|
       +------------------------+   +------------------------+
          |       ^
          V       | 
             +----------+                            |
              | NAMEPREP |                            |
              +----------+                            |
                 |       | 
                 V       | 
             +------------+ +-----------------+
             | UCS -> MDN | | MDN -> UCS |
             +------------+ +-----------------+
                |       ^ 
                V       |
             +-----------------------------------------------+
             |      local resolver      |
             +-----------------------------------------------+
             |    DNS server      |
             +-----------------------------------------------+


3.1 Server side solution

    +-----------------------------------------------+
    |                  user input     |
    +-----------------------------------------------+
   |       ^
   V       |
+-------------------+       |
| Delimiter folding |       |
|    "¡£" -> "."    |       |
+-------------------+       |
   |       | 
   V       | 
    +------------------------------+ +------------------------------+
    | label sequence normalization | | label sequence normalization |
    +------------------------------+ +------------------------------+
   |       ^
   V       | 
        +----------------------+     +----------------------+
  | local encoding ->UCS |    | UCS ->local encoding |
        +----------------------+    +----------------------+
     |       ^
     V       | 
             +----------+                            |
              | NAMEPREP |                            |
              +----------+                            |
                 |       | 
                 V       | 
             +------------+ +-----------------+
             | UCS -> MDN | | MDN -> UCS |
             +------------+ +-----------------+
                |       ^ 
                V       |
             +-----------------------------------------------+
             |      local resolver      |
             +-----------------------------------------------+
                  |
                  V
             +-----------------------------------------------+
             |      local mapping (TC - SC)      |
             |-----------------------------------------------|
             |    DNS server      |
             +-----------------------------------------------+


6 Authors' Address
Xiang Deng
China Internet Network Information Center 
NO.4  South 4th ST. Beijing, P.R.China, 100080, PO BOX 349
Tel: +86-10-62619750 

Yan Fang Wang
China Internet Network Information Center 
NO.4  South 4th ST. Beijing, P.R.China, 100080, PO BOX 349
Tel: +86-10-62619750 


7 References

[IDNREQ]  Requirements of Internationalized Domain Names, Zita Wenzel, 
                James Seng, draft-ietf-idn-requirements

[NAMEPREP] Paul Hoffman & Marc Blanchet, Preparation of
           Internationalized Host Names, draft-ietf-idn-nameprep

[RFC2119] Scott Bradner, Key words for use in RFCs to Indicate
          Requirement Levels, March 1997, RFC 2119.

[STD13]   Paul Mockapetris, Domain names - implementation and
          specification, November 1987, STD 13 (RFC 1034 and 1035).
             
[UNAME]   Internationalized Domain Names and Unique Identifiers/Names
                Li Ming TSENG, Jan Ming HO, Hua Lin QIAN, Kenny HUANG
                draft-ietf-idn-uname
                
[TSCONV]  Traditional and Simplified Chinese Conversion
Xiao Dong Lee, Nai Wen Hsu, Erin Chen, Guo Nian Sun
draft-ietf-idn-tsconv

[ISO10646] ISO/IEC 10646-1:2000. International Standard -- Information
           technology -- Universal Multiple-Octet Coded Character Set 
           (UCS) -- Part 1: Architecture and Basic Multilingual Plane.

[Unicode3] The Unicode Consortium, "The Unicode Standard -- Version3.0",
           ISBN 0-201-61633-5. 
           



From owner-idn@ops.ietf.org  Sun Jul 29 10:49:20 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA22555
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 10:49:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QrDw-000MFs-00
	for idn-data@psg.com; Sun, 29 Jul 2001 07:07:16 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QrDv-000MFJ-00
	for idn@ops.ietf.org; Sun, 29 Jul 2001 07:07:15 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f6TE5ON20079
	for <idn@ops.ietf.org>; Sun, 29 Jul 2001 10:05:24 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107291405.f6TE5ON20079@nic-naa.net>
To: idn@ops.ietf.org
Subject: Fwd: Re: [idn] Intro to my I-D
Date: Sun, 29 Jul 2001 10:05:24 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

The list (idn@ops.ietf.org) was not included in my reply to Ben's note to the
tsconv authors and myself.

------- Forwarded Message

Date: Sun, 29 Jul 2001 07:22:00 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>

Ben,

You've proposed to place the locus of control for scope of equivalance
rules in the hands of the registrant. 

	One of the benefits offered under this system is that a
	Traditional CDN will be able to go to a location that is
	different from the Simplified CDN, if the registrant so
	chooses.                                  ^^^^^^^^^^

In the requirements draft, up to revision 6, there was a condition [30]
([35] in revision 4 and earlier), whch read as follows:

	[30] Within a single zone, the zone manager MAY be able to define
	equivalence rules that suit the purpose of the zone, such as, but not
	limited to, and not necessarily, non-ASCII case folding, Unicode
	normalizations (if Unicode is chosen), Cyrillic/Greek/Latin folding, or
	traditional/simplified Chinese equivalence. Such defined equivalences
	MUST NOT remove equivalences that are assumed by (old or
	local-rule-ignorant) caches.

The important difference in scope is that in [30] equivalence rules are made
for zones. In your comment, equivalence rules are made for entries in zones,
or are defined not to exist, to disambiguate Simplified from Traditional forms
of Chinese characters.

So, what I propose you expand is how to express a requirement, which may be
optional, that modifies the sense of [30] to be consistent with the view you
have of what is useful.

Please ignore for the moment that [30] is no longer in the requirements
document, and the probability that few may find your proposal interesting,
and just try and get your idea expressed as well as you can.

Eric

------- End of Forwarded Message




From owner-idn@ops.ietf.org  Sun Jul 29 10:49:23 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA22611
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 10:49:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QoZ5-000ICX-00
	for idn-data@psg.com; Sun, 29 Jul 2001 04:16:55 -0700
Received: from sina.sharif.ac.ir ([62.41.32.2] ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QoYn-000IBT-00
	for idn@ops.ietf.org; Sun, 29 Jul 2001 04:16:39 -0700
Received: from bamdad.org (IDENT:root@gilas.bamdad.org [62.41.28.76])
	by Sina.sharif.ac.ir (8.9.3/8.9.3) with ESMTP id PAA06079;
	Sun, 29 Jul 2001 15:46:10 +0430
Received: from localhost (roozbeh@localhost)
	by bamdad.org (8.11.2/8.11.2) with ESMTP id f6TBGp416810;
	Sun, 29 Jul 2001 15:46:51 +0430
X-Authentication-Warning: gilas.bamdad.org: roozbeh owned process doing -bs
Date: Sun, 29 Jul 2001 15:46:50 +0430 (IRST)
From: Roozbeh Pournader <roozbeh@sharif.edu>
X-X-Sender:  <roozbeh@gilas.bamdad.org>
To: John C Klensin <klensin@jck.com>
cc: <idn@ops.ietf.org>
Subject: Re: [idn] ZWNJ
In-Reply-To: <5632254.996321750@localhost>
Message-ID: <Pine.LNX.4.33.0107291427360.15511-100000@gilas.bamdad.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


John,

You're right about the identifier nature of DNS names. Being brought up in
such a world, I'm already well familiar with the way this impacts the
language. For a good example, see Arthur C Clarke's The Light of Other
Days, ISBN 0812576403, where words like SearchEngine are common. The DNS
and other identifier restrictions have changed the shape of English
language, for sure.

Getting back to the thread, Arabic lacks many of the possiblities of the
Latin script, for getting a distinguished sense out of a sequence of
letters (which we will call identifiers). I consider the use of ZWNJ to be
equivalent to the use of inter-identifier captialization. Just like that,
it should be ignored, just like that, it will help the reader, and just
like that, the original should be retreivable in some way.

Please note that even in single words, ZWNJ is used. In many single words
like the Persian words for "houses", "circular", "eraser", "compatriot",
and "synonymous", or single-word names of places, it may not be dropped in
any way, or the word becomes completely unreadable.

Arabic is connected, unlike Latin where the letters are separate enough
that you can sometimes omit the space (like in domain names, or German).
It's also unlike Han, where there is a good boundary between the words,
without even the need for spaces. So it should use spaces and ZWNJ heavily
to stop joining where it will ruin the meaning or readablity of the
phrases. Please note that ZWNJ is somehow considered a *nothing* in the
Unicode recommendation. It should only affect contextual shaping, and
nothing else...

While I see the use of space-like characters in Latin problematic (mainly
because of indistinguishablity of the written word), the case is
difference with ZWNJ. It is not a space character.

BTW, there are also many other needs for being able to retreive the
original non-nameprepped name. Have you thought about national digit
shapes (as used in Arabic and Indic scripts), for example? Many countries
do not use European digits (which Europeans call Arabic).

roozbeh

On Sat, 28 Jul 2001, John C Klensin wrote:

> DNS names are identifiers and, as identifiers, are subject to
> certain restrictions.  Length is one of them -- we even have
> words in English that are over 63 character long, although there
> aren't many of them, and they can't be used in domain names.  A
> second is that, as identifiers, labels are what computer languge
> syntax folks call "atoms" or "atomic".  That typically means
> "one label, one "word".  There is a long history of pushing
> words together to make one DNS labels and using either the one
> joining character available (hyphen) or just catenating them.
> In the latter case, we just hope the user will figure out what
> is going on to preserve whatever mneumonic value we intend.
>
> Parenthetically, this is one place where our colleagues with
> ideographic languages have a huge advantage: they can actually
> write multi-word phrases into DNS labels/identifiers without
> doing violence to the natural rules of the writing system.
>
> So I don't know quite what to do with ZWNJ and other separators
> or near-separators without opening the door to other characters
> normally used in other languages as near-separators or
> punctuation or near-punctuation, e.g., ":", "'", "!", or "&",
> which have been used, normally or artistically, in Indo-European
> languages using Roman-derived character sets for many years, and
> even recognizing distinct interpretations for some of the
> distinct spacing characters and hyphenation ones in Unicode.
>
> For example, while I would _strongly_ not recommend going down
> this path, we could, in principle, adopt presentation and coding
> rules that would permit, e.g.,
>
>    "O'Reilly & Associates"
>
> to use the domain name
>
>    www."O'Reilly & Associates".com
>
> by coding the key second label as
>    O(U+0027)Reilly(U+00A0)(U+0026)(U+00A0)Associates
>
> Again, I don't suggest doing this, but, ultimately, the DNS
> itself would have no problems with it and, if one starts
> introducing near-space characters from other scripts, then there
> is little justification for prohibiting this type of usage in
> Roman-based ones.
>
>      john
>






From owner-idn@ops.ietf.org  Sun Jul 29 11:29:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA23760
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 11:29:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QsMW-000OBh-00
	for idn-data@psg.com; Sun, 29 Jul 2001 08:20:12 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QsMV-000OBb-00
	for idn@ops.ietf.org; Sun, 29 Jul 2001 08:20:11 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f6TFHvN20321;
	Sun, 29 Jul 2001 11:17:57 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107291517.f6TFHvN20321@nic-naa.net>
To: "ben" <ben@cc-www.com>
cc: "xiang deng" <deng@cnnic.net.cn>, lee@cnnic.net.cn, sun@cnnic.net.cn,
        brunner@nic-naa.net, brunner@nic-naa.net, harald@alvestrand.no,
        idn@ops.ietf.org
Subject: Re: [idn] Intro to my I-D 
In-Reply-To: Your message of "Sun, 29 Jul 2001 10:03:31 EDT."
             <022901c11837$4081c980$d43f7018@mtag1.on.home.com> 
Date: Sun, 29 Jul 2001 11:17:56 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

[I've added idn@ops.ietf.org back to the cc'd list.
 Harald, please read and reconsider the "principle of least surprise".
 Thx.]

Ben,

What you've proposed is that for some collection of code-points, and for
some equivalency rules (whether zone-scoped or global-scoped), allocation
of one code-point in the collection results in pre-allocation (reservation)
of all code-points in the collection.

Additionally, you've proposed the registrant (recipient of the allocated
code-point equivalency class) may then modify the equivalency rule which
created the class, and assert distinct semantics for distinct elements of
the original (intact), now fragmented class.

To help me understand your proposal, I'll consider ASCII strings and the
Pan-Algonquin "OU" character (U+0222) and (U+0223). A locally constructed
French character, not present in 17th century French. I know that most of
the North Americans and Europeans will find this choice strange, but more
accessible, as "Indian French", than an ideogramatic example, and I know
that my friends at CNNIC will speak to the Chinese language specifics.

Assertion: (zone scope)

	In the Algonquin-preferred zone(s), e.g., abenaki.dst.me.us,
	the following code-points and code-point sequences are
	equivalent:
		U+0070		"8"	when in an alpha-string
		U+0222		"8"	LATIN CAPITAL LETTER OU
		U+0223		"8"	LATIN SMALL LETTER OU
		U+0117,U+0125	"OU"
		U+O117,U+0165	"Ou"
		U+0157,U+0165	"ou"
		U+0127		"W"
		U+0167		"w"

Under your proposal, in my zone (abenaki.dst.me.us.), with ASCII case folding
(applied to the two Latin Extended-B code points), the registrant for
"ki8na.abenaki.dst.me.us" ("ki8na" means ourselves or nous-memes), would be
allocated or reserved:

		ki{set of 4 code-point sequences}na.abenaki.dst.me.us 

The registrant could then be able to associate between 0 and eight unique
ip addresses to these 4 allocated domain names in my zone, e.g.,

	ki(U+0070)na.abenaki.dst.me.us and 1.2.3.1
	ki(U+0222)na.abenaki.dst.me.us and 1.2.3.2
	ki(U+0223)na.abenaki.dst.me.us and 1.2.3.2
	ki(U+0117,U+0125)na.abenaki.dst.me.us and 1.2.3.3
	ki(U+O117,U+0165)na.abenaki.dst.me.us and 1.2.3.3
	ki(U+0157,U+0165)na.abenaki.dst.me.us and 1.2.3.3
	ki(U+0127)na.abenaki.dst.me.us and 1.2.3.4
	ki(U+0167)na.abenaki.dst.me.us and 1.2.3.4

Without case folding there could be 8 distinct addresses rather than just 4.

This would be very surprising to a modern literate North-Eastern Indian, and
to scholars of the Contact Period and French and Indian literatures of the
17th and 18th centuries. As the abenaki.dst.me.us zone manager, I don't think
I would allow it. I would expect the equivalency rule (above) to be adopted
by the {penobscot,passamquoddy,maliseet,micmac}.dst.me.us zone managers, and
by other "Algonquin-aware" NSN.US zone managers. I would not expect these to
be adopted by the dst.me.us or superior zone managers. I would expect the same
rule and scope to exist in the .ca zone and its dependent zones.

My preference is that ki{set of 4 code-point sequences}na.abenaki.dst.me.us
all map to a single internet address.

In the Chinese language area, which includes North America as well as China,
your "registrant election" proposal appears to have the same surprising set
of consequences as one registrant following one ideosyncratic convention for
"ki8na" and another registrant, possibly the same one, following a different
ideosyncratic convention for "ni8na" (we and you or nous et vous), and this
only gets worse as we consider strings such as k8sk8ranmsh8dans8 (sift).

Just what makes your proposal superior?

Eric

P.S. The advantage of [30], formerly "in" the IDN WG requirements draft, was
that it made zone-specific semantics possible. Writing in modern Abenaki (or
any "8" using French-originating modern script) using ASCII equivalency rules
presents a problem for 0x70 to 0x127,0x167 mapping (simplest case).



From owner-idn@ops.ietf.org  Sun Jul 29 16:10:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA02154
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 16:10:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QvAn-0003Gj-00
	for idn-data@psg.com; Sun, 29 Jul 2001 11:20:17 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QvAm-0003Gd-00
	for idn@ops.ietf.org; Sun, 29 Jul 2001 11:20:17 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f6TIIJN20709;
	Sun, 29 Jul 2001 14:18:20 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107291818.f6TIIJN20709@nic-naa.net>
To: "ben" <ben@cc-www.com>
cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        "xiang deng" <deng@cnnic.net.cn>, lee@cnnic.net.cn, sun@cnnic.net.cn,
        "wenhui zhang" <zwh@cnnic.net.cn>, brunner@nic-naa.net,
        idn@ops.ietf.org
Subject: Re: [idn] Intro to my I-D 
In-Reply-To: Your message of "Sun, 29 Jul 2001 12:43:05 EDT."
             <02f601c1184d$8d3fc680$d43f7018@mtag1.on.home.com> 
Date: Sun, 29 Jul 2001 14:18:19 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Ben,

The example offered by Deng, which should cause you less of a headache
than French-Indian.

For example:

Deng registers a Simplified Chinese domain name: XYZ.cn. (ip addr 1.2.3.1)

	Assume Simplified characters X, Y, and Z, each have just one
	Traditional form, characters U, V and W, respectively.

	The names formed from the union of these three equivalence classes
	are:
		XYZ, XYW, XVZ, XVW, UYZ, UYW, UVZ, UVW

Under your proposal (pending), XYZ is registered in .cn, and the remaing set
of seven (7) names are reserved to the registrant.
	
Deng wants users to be able to visit his domain name. Some live in Mainland
China, some in Hongkong, some in Maco, some in Taiwan, and some in North
America.

Deng now has to register or otherwise map the following seven (7) names to
the same ip address (1.2.3.1):

	{XYZ, XYW, XVZ, XVW, UYZ, UYW, UVZ, UVW}.cn (ip addr 1.2.3.1)

This will avoid surprising Chinese who are accustomed to the SC <-> TC
equivalence, who _know_ that all eight (8) are equivalent as identifiers,
even if they appear to non-Chinese eyes as distinct "words" or characters.

In your proposal the registrant can create new equivalence rules, in the
worst case, only known to the registrant, e.g., ignoring the Y <-> V map,
creating
	{XYZ, XYW, UYZ, UYW}.cn (ip addr 1.2.3.1)
and
	{XVZ, XVW, UVZ, UVW}.cn (ip addr 1.2.3.2)

An additional issue is the temporal duration of your proposal. In the SC/TC
map, there is no expiry of the equivalence mapping. In your proposal there
is a reservation, how long does it last?

Eric



From owner-idn@ops.ietf.org  Sun Jul 29 16:50:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA03622
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 16:50:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Qx8z-0005rX-00
	for idn-data@psg.com; Sun, 29 Jul 2001 13:26:33 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Qx8y-0005rC-00
	for idn@ops.ietf.org; Sun, 29 Jul 2001 13:26:32 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f6TKOcN21107;
	Sun, 29 Jul 2001 16:24:38 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107292024.f6TKOcN21107@nic-naa.net>
To: "ben" <ben@cc-www.com>
cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        "xiang deng" <deng@cnnic.net.cn>, lee@cnnic.net.cn, sun@cnnic.net.cn,
        "wenhui zhang" <zwh@cnnic.net.cn>, brunner@nic-naa.net,
        idn@ops.ietf.org
Subject: Re: [idn] Intro to my I-D 
In-Reply-To: Your message of "Sun, 29 Jul 2001 15:46:34 EDT."
             <003801c11867$2cff1fe0$d43f7018@mtag1.on.home.com> 
Date: Sun, 29 Jul 2001 16:24:37 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Ben,

Assume Simplified characters X, Y and Z, each have just one
Traditional form, characters U, V and W, respectively.

The names formed from the union of these three equivalence classes
are:
	XYZ, XYW, XVZ, XVW, UYZ, UYW, UVZ, UVW

If the registrant is able to do the following as he or she so chooses:
XYZ.cn (ip addr 1.2.3.1)
XYW.cn (ip addr 1.2.3.2)
UYZ.cn (ip addr 1.2.3.3)
UYW.cn (ip addr 1.2.3.4)
XVZ.cn (ip addr 1.2.3.5)
XVW.cn (ip addr 1.2.3.6)
UVZ.cn (ip addr 1.2.3.7)
UVW.cn (ip addr 1.2.3.8)

Then the following is possible, neh? (Assume subnet of 1.2.3 throughout)

+-------+-------+-------+-------+-------+-------+-------+-------+---------
Number of characters with only one equivalent character (SC/TC, simple case)
1 (2)		2 (4)		3 (8)		4 (16)		...
Registrat A	Registrant B	Registrant C	Registrant D	...
+-------+-------+-------+-------+-------+-------+-------+-------+---------
				XYZ.cn (1)
				XYW.cn (2)
                XY.cn (127)	UYZ.zn (3)
X.cn (254)	UY.cn (127)	UYW.cn (4)
U.cn (253)      XV.cn (127)	XVZ.cn (5)
		UV.cn (127)	XVW.cn (6)
				UVZ.cn (7)
				UVW.cn (8)
+-------+-------+-------+-------+-------+-------+-------+-------+---------
multiple	unique		multiple	...		...

I'm glad you intend to comment on any draft, whether by writing a comment,
or an alternative draft. However, this appears to require users to have
access into the ideosyncratic (private) semantic preferenances of the
registrant. How, as a set of labels is expanded from one initial character
to some maximum number of characters, each a single character suffix to
the preceeding label's set of characters, e.g., a, ab, abc, abcd, ...
are labels to be understood? As having consistent equivalence rules, or as
having label-unique equivalence rules? All this is within a single zone.

Not that I consider the interests of trademark holders to be the only ones
worth examining, but if some set of SC and TC characters are registered
marks in some jurisdiction, then how would a mix of SC and TC characters
from both registered marks appear to the trademark holder? It appears that
the advantage of your proposal is that users must engage in vastly more
complex name-to-address management, as must marks enforcers.

Your initial note claimed the benefits are mapping content script to label
script, and user-defined, reserved character equivalence definition. Have
I got your proposal's main points?

Eric



From owner-idn@ops.ietf.org  Sun Jul 29 17:54:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA05325
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 17:54:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QxzV-0006n5-00
	for idn-data@psg.com; Sun, 29 Jul 2001 14:20:49 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QxzV-0006my-00
	for idn@ops.ietf.org; Sun, 29 Jul 2001 14:20:49 -0700
Received: from bbthead.dcrocker.net ([200.37.188.21])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id OAA05487;
	Sun, 29 Jul 2001 14:19:38 -0700
Message-Id: <5.1.0.14.2.20010729161325.032a1f90@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 29 Jul 2001 16:13:35 -0500
To: Dan Oscarsson <Dan.Oscarsson@trab.se>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] iDN Transition Support Requirements
Cc: idn@ops.ietf.org
In-Reply-To: <200107270809.KAA01275@valinor.malmo.trab.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 03:09 AM 7/27/2001, Dan Oscarsson wrote:
>Dave Crocker wrote:
> >What portions of the Internet must support the relevant DNS mechanisms, for
> >ACE versus UTF-8?
>
>I assume you mean the UTF-8 case where not ACE is used for backward
>compatibility.

correct.

d/


----------
Dave Crocker  <mailto:dcrocker@brandenburg.com>
Brandenburg InternetWorking  <http://www.brandenburg.com>
tel +1.408.246.8253;  fax +1.408.273.6464




From owner-idn@ops.ietf.org  Sun Jul 29 19:20:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA06908
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 19:20:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15QzIU-0008Au-00
	for idn-data@psg.com; Sun, 29 Jul 2001 15:44:30 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15QzIU-0008Ao-00
	for idn@ops.ietf.org; Sun, 29 Jul 2001 15:44:30 -0700
Received: from bbthead.brandenburg.com ([200.37.188.21])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id PAA07605
	for <idn@ops.ietf.org>; Sun, 29 Jul 2001 15:44:28 -0700
Message-Id: <5.1.0.14.2.20010729172557.0302f008@brandenburg.com>
X-Sender: dcrocker@brandenburg.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 29 Jul 2001 17:31:05 -0500
To: idn@ops.ietf.org
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: [idn] We are quibbling about WHAT?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

UTF-8 takes a set of table entries, and maps them to 8-bit strings.

ACE takes the same set of table entries and maps them to a subset of 7-bit 
ASCII.  For order-of-magnitude convenience, let us call this 6.5-bit ASCII.

Never having been any good at math, I'm still going to suggest that the 
entire debate that has garnered such religious positions -- and, far worse, 
is causing continuing delay to this working group -- concerns an encoding 
efficiency difference of, at most, 19 percent.

For strings that are less than 100 characters long!

Unless someone can refute the transition impact discussion in my "iDN 
Transition Support Requirements" note, is it not time to choose an ACE and 
move on?

d/

----------
Dave Crocker  <mailto:dcrocker@brandenburg.com>
Brandenburg InternetWorking  <http://www.brandenburg.com>
tel +1.408.246.8253;  fax +1.408.273.6464




From owner-idn@ops.ietf.org  Sun Jul 29 20:51:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA08141
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 20:51:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15R0sn-0009rU-00
	for idn-data@psg.com; Sun, 29 Jul 2001 17:26:05 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15R0sm-0009rO-00
	for idn@ops.ietf.org; Sun, 29 Jul 2001 17:26:05 -0700
Received: from soobok ([210.217.27.237] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id JAA31699;
	Mon, 30 Jul 2001 09:25:56 +0900
Message-ID: <006e01c1188e$ed3e72c0$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "Dave Crocker" <dcrocker@brandenburg.com>
References: <5.1.0.14.2.20010729172557.0302f008@brandenburg.com>
Subject: Re: [idn] We are quibbling about WHAT?
Date: Mon, 30 Jul 2001 09:31:08 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message ----- 
From: "Dave Crocker" <dcrocker@brandenburg.com>


 > Never having been any good at math, I'm still going to suggest that the 
> entire debate that has garnered such religious positions -- and, far worse, 
> is causing continuing delay to this working group -- concerns an encoding 
> efficiency difference of, at most, 19 percent.
> 
> For strings that are less than 100 characters long!
> 

some ACE proposals produce about 40% shorter ACE labels  even for
 10 characters long  han/hangeul native labels, compared to that of DUDE.

> Unless someone can refute the transition impact discussion in my "iDN 
> Transition Support Requirements" note, is it not time to choose an ACE and 
> move on?
> 
> d/
> 
> ----------
> Dave Crocker  <mailto:dcrocker@brandenburg.com>
> Brandenburg InternetWorking  <http://www.brandenburg.com>
> tel +1.408.246.8253;  fax +1.408.273.6464
> 
> 




From owner-idn@ops.ietf.org  Sun Jul 29 20:51:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA08147
	for <idn-archive@lists.ietf.org>; Sun, 29 Jul 2001 20:51:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15R0id-0009fV-00
	for idn-data@psg.com; Sun, 29 Jul 2001 17:15:35 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15R0ic-0009ew-00
	for idn@ops.ietf.org; Sun, 29 Jul 2001 17:15:34 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f6U0DON21674;
	Sun, 29 Jul 2001 20:13:24 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107300013.f6U0DON21674@nic-naa.net>
To: Dave Crocker <dcrocker@brandenburg.com>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] We are quibbling about WHAT? 
In-Reply-To: Your message of "Sun, 29 Jul 2001 17:31:05 CDT."
             <5.1.0.14.2.20010729172557.0302f008@brandenburg.com> 
Date: Sun, 29 Jul 2001 20:13:24 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hi Dave. How's Bolivia (or Peru)?

Not to quibble overly, but ...

There are 63 elements in the -0-9A-Za-z set, or 6 bits (minus one).

Worse, with case folding, there are 37 elements in the -0-9Aa-Zz set,
or 5 bits (plus 5).

The "6.5-bit ASCII" tag is ... generous. How about "sub-6-bit-SKI",
or "Modern Baudot" (Baudot used 5 bits, with the LTRS and FIGS chars
to switch between two 31 valued repetoires, of which 27 had unique
values). It is very much in the spirit of ACE.

UTF-8 does not take an 8859-1 string and transform it into what some
have referred to as "ASCII-gibberish". Repeat for -2, -3, ... -9.

That said, I don't think anyone working on an 8-bit proposal, which
means those in which the value of "A" is 0100 0001 (8859-1), rather
than x100 0001 (ASCII), where "x" indicates "don't care", and allows
for some multi-byte extension, e.g., UTF-8, picked an 8-bit clean
approach for length reasons. I also don't think anyone working on
any 7-bit proposal, favorably referred to as "ACE", and available
in more shapes, colors and sizes than shoes, picked an 8-bit dirty
approach for length reasons.

I think the encapsulate vs extend debate is about architecture. It
just happens that 63 bytes does focus some attention on effective
characters per mechanism, and encapsulation schemes using only 5 bits
plus a nickle per octet are at a disadvantage over extension schemes
that use at least 7 bits per octet.

Most of the ACE variation numbers are concerned with CJK character
repetoires, I don't recall seeing any for 8859-* repetoires. This
may be selective memory on my part, but if it isn't, this is a topic
worth visiting.

The transition impact discussion can't be refuted. It was the subject
of RFC 801, and others. I'm particularly fond of lines 51 - 64 of
that transition plan by the way.

Time to choose an ACE and move on? I'll pass thanks. A half-dozen
browser-hack marketeers, a trio of monopolies, and the DNSO food
fight, is inadequate motivation to solve a complex problem. A good
solution is, and differences in that are why we are where we are.

Bifurcation of the WG is a possibility, it has its merits. So too
has closure. Or, the co-chairs can find "rough consensus" and try
and get working code creditable.

Eric
P.S. I'd like a reproduction Quipu, please.
Eric



From owner-idn@ops.ietf.org  Mon Jul 30 03:41:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA05349
	for <idn-archive@lists.ietf.org>; Mon, 30 Jul 2001 03:41:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15R4oi-000EXq-00
	for idn-data@psg.com; Sun, 29 Jul 2001 21:38:08 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15R4oh-000EXk-00
	for idn@ops.ietf.org; Sun, 29 Jul 2001 21:38:07 -0700
Received: from amc by nicemice.net with local (Exim 3.31 #1 (Debian))
	id 15R4oh-000237-00; Sun, 29 Jul 2001 21:38:07 -0700
Date: Mon, 30 Jul 2001 04:38:07 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] ZWNJ
Message-ID: <20010730043806.H6836@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.33.0107291427360.15511-100000@gilas.bamdad.org>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Roozbeh Pournader <roozbeh@sharif.edu> wrote:

> BTW, there are also many other needs for being able to retreive the
> original non-nameprepped name.

It will be nice to be able to use non-nameprepped names, but what do
you mean by "retrieve"?  If you mean recover them from ACE, that's too
much to hope for; ACE can store the nameprepped name and the mixed-case
info, but anything more would be difficult and inefficient.  If you mean
retrieve from DNS, I don't think that's helpful, because names retrieved
from DNS are very rarely seen by typical users.

I think what you really want is simply to be able to use non-nameprepped
names in application protocols, so that users can see them.  That will
be possible as soon the protocol adds explicit support for IDNs, so that
it no longer relies on ACE as the sole means of representing IDNs.

Maybe you were imagining that an application, after receiving an ACE
name in an application message, would do a DNS lookup to retrieve a
non-nameprepped version of the name.  That would not only increase the
load on the DNS, but might also return the wrong version of the name,
from the sender's point of view.  For example, if mail user agents did
that, everyone would see my email address as "amc@CS.Berkeley.EDU",
which I think is ugly.  If we want to allow users to see non-nameprepped
names, we should aim for the spelling chosen by the sender, not the
spelling chosen by the registrant.  That means the non-nameprepped
spelling has to be taken from the application message, not from the DNS.

AMC



From owner-idn@ops.ietf.org  Mon Jul 30 03:47:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA05613
	for <idn-archive@lists.ietf.org>; Mon, 30 Jul 2001 03:47:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15R4dy-000EJu-00
	for idn-data@psg.com; Sun, 29 Jul 2001 21:27:02 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15R4dw-000EJn-00
	for idn@ops.ietf.org; Sun, 29 Jul 2001 21:27:01 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 86D02FFC04; Mon, 30 Jul 2001 12:28:39 +0800 (SGT)
Message-ID: <01f001c118af$d7831500$68da15a5@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: <idn@ops.ietf.org>, "Adam M. Costello" <amc@cs.berkeley.edu>
References: <20010730040119.G6836@arwen.cs.berkeley.edu>
Subject: Re: [idn] new I-D: Safely Encoding of  likeness information into ACE label   version 0.2
Date: Mon, 30 Jul 2001 12:26:45 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Okay folk.

I have recieved some offline comments that this topic on "look-alive" is
way out-of-scope for the IDN WG, which I agree, I have to kill this
topic on the wg. I think it is inappropriate to continue this discussion
given that it is not within the Pool and beyond the charter for this wg.
We should focus on what is in the Pool and to build consensus around it.

Therefore, I would appreciate if this discussion would be carried
off-line with the author or to some other forum (suggestion: try Unicode
Consortium) on the topic of normalization of "look-alive" characters.

The portion of this work that does related to IDN is probably the
security concern of "look alike" characters. If the authors is still
interested to pursue this within the idn wg, then I would suggest the
draft to be modified to be an investigation of the security impacts.

Thanks!

-James Seng


----- Original Message -----
From: "Adam M. Costello" <amc@cs.berkeley.edu>
To: <idn@ops.ietf.org>
Sent: Monday, July 30, 2001 12:01 PM
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into
ACE label version 0.2


> Soobok Lee <lsb@postel.co.kr> wrote:
>
> > Even If we normalize U+6046 into U+6052 ( or U+30AB -> U+529B ), my
> > I-D's likeness encoding will allow recover U+6046 (or U+30AB) as
long
> > as applications do not casefold the produced ACE label.
>
> Today's ASCII domain names already allow visually similar characters
> that don't match (0O 1lI 2Z 5S 6G) and people have lived with it for
> a long time, so I don't think we should feel obligated to eliminate
> this problem in IDNs, especially if it means significantly increasing
> complexity and decreasing efficiency, which it appears to do.
>
> AMC
>




From owner-idn@ops.ietf.org  Mon Jul 30 03:47:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA05644
	for <idn-archive@lists.ietf.org>; Mon, 30 Jul 2001 03:47:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15R4F7-000DmP-00
	for idn-data@psg.com; Sun, 29 Jul 2001 21:01:21 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15R4F6-000DmI-00
	for idn@ops.ietf.org; Sun, 29 Jul 2001 21:01:20 -0700
Received: from amc by nicemice.net with local (Exim 3.31 #1 (Debian))
	id 15R4F5-00020U-00; Sun, 29 Jul 2001 21:01:19 -0700
Date: Mon, 30 Jul 2001 04:01:19 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] new I-D: Safely Encoding of  likeness information into ACE label   version 0.2
Message-ID: <20010730040119.G6836@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <002901c117fa$d0c63cc0$ed1bd9d2@postel.co.kr>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Soobok Lee <lsb@postel.co.kr> wrote:

> Even If we normalize U+6046 into U+6052 ( or U+30AB -> U+529B ), my
> I-D's likeness encoding will allow recover U+6046 (or U+30AB) as long
> as applications do not casefold the produced ACE label.

Today's ASCII domain names already allow visually similar characters
that don't match (0O 1lI 2Z 5S 6G) and people have lived with it for
a long time, so I don't think we should feel obligated to eliminate
this problem in IDNs, especially if it means significantly increasing
complexity and decreasing efficiency, which it appears to do.

AMC



From owner-idn@ops.ietf.org  Mon Jul 30 03:48:01 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA05652
	for <idn-archive@lists.ietf.org>; Mon, 30 Jul 2001 03:47:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15R4x6-000Ej7-00
	for idn-data@psg.com; Sun, 29 Jul 2001 21:46:48 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15R4x5-000Ej1-00
	for idn@ops.ietf.org; Sun, 29 Jul 2001 21:46:47 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id NAA17632;
	Mon, 30 Jul 2001 13:46:39 +0900
Message-ID: <012401c118b1$e72cde80$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "Adam M. Costello" <amc@cs.berkeley.edu>
References: <20010730040119.G6836@arwen.cs.berkeley.edu>
Subject: Re: [idn] new I-D: Safely Encoding of  likeness information into ACE label   version 0.2
Date: Mon, 30 Jul 2001 13:41:30 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Adam M. Costello" <amc@cs.berkeley.edu>
To: <idn@ops.ietf.org>
Sent: Monday, July 30, 2001 1:01 PM
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE
label version 0.2


> Soobok Lee <lsb@postel.co.kr> wrote:
>
> > Even If we normalize U+6046 into U+6052 ( or U+30AB -> U+529B ), my
> > I-D's likeness encoding will allow recover U+6046 (or U+30AB) as long
> > as applications do not casefold the produced ACE label.
>
> Today's ASCII domain names already allow visually similar characters
> that don't match (0O 1lI 2Z 5S 6G) and people have lived with it for
> a long time, so I don't think we should feel obligated to eliminate
> this problem in IDNs, especially if it means significantly increasing
> complexity and decreasing efficiency, which it appears to do.
>
> AMC
>
Choosing a disambiguating  font may eliminate such similarities. But,
We should not forget the problem around borrored glyphs that look identical.
Cherokee 'A' and Latin 'A' and latin 'a' and cyrillia 'a' look identical than
look similiar.
I haven't ever seen any identifier system that has duplicate  atoms (in BNF):
  IDN   :=  (atom)+
  atom :=   'a'|'a'|'a'|'b'|'b'|'c'|'c' ......


Soobok Lee




From owner-idn@ops.ietf.org  Mon Jul 30 10:51:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA25484
	for <idn-archive@lists.ietf.org>; Mon, 30 Jul 2001 10:51:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RAj7-000NaV-00
	for idn-data@psg.com; Mon, 30 Jul 2001 03:56:45 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RAj6-000Na7-00
	for idn@ops.ietf.org; Mon, 30 Jul 2001 03:56:44 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id TAA05620;
	Mon, 30 Jul 2001 19:56:18 +0900
Message-ID: <02a401c118e5$8ba183c0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <James@Seng.cc>, <idn@ops.ietf.org>,
        "Adam M. Costello" <amc@cs.berkeley.edu>
References: <20010730040119.G6836@arwen.cs.berkeley.edu> <01f001c118af$d7831500$68da15a5@jamessonyvaio>
Subject: Re: [idn] new I-D: Safely Encoding of  likeness information into ACE label   version 0.2
Date: Mon, 30 Jul 2001 19:51:10 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "James Seng/Personal" <James@Seng.cc>
 version 0.2


>. If the authors is still
> interested to pursue this within the idn wg, then I would suggest the
> draft to be modified to be an investigation of the security impacts.
>

Security impacts of premature IDN on the global  internet  may  be
Deep and Disastrous.

1) facillitate  DNS spoofing

    Anyone can get  <russian a>ol.com  from the registry if lucky and make a
spoofing site easily.
    they no more  need to  hire a hacker for rocket-science DNS hijacking .

2) easy impersonation attack on  email addresses

    From: V<cherokee i>ntCerf@ic<Cyrillic a>nn.org
    To:  bush@whitehouse.gov
    Subject:  I oppose MD!

    From: m<greek o>mmy@aol.com
    To:   daughter@msn.com
    Subject: i am your mom.  I lost my creditcard, let me know your card#.


3) defeat anti-spoofing efforts like DNSSEC

   anyone can get  the valid certificate issued  for his scam email address/site
name.

4) more on my next draft


Soobok Lee





> Thanks!
>
> -James Seng
>




From owner-idn@ops.ietf.org  Mon Jul 30 10:53:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA25645
	for <idn-archive@lists.ietf.org>; Mon, 30 Jul 2001 10:53:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15R97W-000LMf-00
	for idn-data@psg.com; Mon, 30 Jul 2001 02:13:50 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15R97V-000LMY-00
	for idn@ops.ietf.org; Mon, 30 Jul 2001 02:13:49 -0700
Received: from valinor.malmo.trab.se (valinor [131.115.48.20]) by malmo.trab.se (8.10.1/TRAB-primary-2) with ESMTP id f6U9C0P09044 for <idn@ops.ietf.org>; Mon, 30 Jul 2001 11:12:01 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Mon, 30 Jul 2001 11:13:46 +0200 (MEST) (MET)
Message-Id: <200107300913.LAA02165@valinor.malmo.trab.se>
Date: Mon, 30 Jul 2001 11:13:46 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: [idn] How should labels be encoded?
To: idn@ops.ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 9Tk/j+MFv99fa5Z5kp04wQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk


The IDNA (ACE+nameprep) discussions have been focused on how to
encode "host names" to be used in DNS.

In DNS there are records that have an owner name and can include
names and text elements. All names are composed of labels.
A label is today maximum 63 bytes and can contain any character.
RFC 2181 defines that the DNS protocol and servers may not
restrict the characters that may be used in a label. But an
application can.

IDNA defines that a "host name" is to be nameprepped and ACEd before
being sent into the DNS protocol. As using nameprep results in
some characters being forbidden, it cannot be used as a general
mechanism on all labels.

So now my question is: how should the labels in the DNS protocol
be encoded? 
Which labels are "host names"?
The SOA record contains one that is an e-mail address.
The SRV record has an owner name that represents a protocol.
Also not every thing which has an IP-address is a "host".
As DNS is more than "host names", how are labels that are not
"host names" to be encoded when non-ASCII is used?

IDNA does not answer this and it does not define which labels
are "host names" and must be ACE+nameprep encoded.
It can happen that one application thinks a label in a
DNS record is a host names, and another application uses it
as something else (using some other encoding that ACE+nameprep).

There is a possibility of difficulties here.

   Dan




From owner-idn@ops.ietf.org  Mon Jul 30 10:53:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA25656
	for <idn-archive@lists.ietf.org>; Mon, 30 Jul 2001 10:53:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RDL9-0001Mn-00
	for idn-data@psg.com; Mon, 30 Jul 2001 06:44:11 -0700
Received: from [209.187.148.217] (helo=P2)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RDL8-0001Mh-00; Mon, 30 Jul 2001 06:44:10 -0700
Date: Mon, 30 Jul 2001 09:44:08 -0400
From: John C Klensin <klensin@jck.com>
To: Dan Oscarsson <Dan.Oscarsson@trab.se>, roozbeh@sharif.edu
cc: idn@ops.ietf.org
Subject: Re: [idn] ZWNJ
Message-ID: <10232548.996486248@P2>
In-Reply-To: <200107301324.PAA02427@valinor.malmo.trab.se>
References:  <200107301324.PAA02427@valinor.malmo.trab.se>
X-Mailer: Mulberry/2.1.0b2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Monday, 30 July, 2001 15:24 +0200 Dan Oscarsson
<Dan.Oscarsson@trab.se> wrote:

>> But, if the goal is to
>> be able to retrieve and examine the original name, then, it
>> seems to me that the way to do that is to store the original
>> name somewhere, rather than hoping that nameprep can both do
>> its job and be reversible.
> 
> Today DNS stores the original name, and the case insensitive
> matching is done by case insensitive compare.
> 
> Using UCS, the DNS could store all names using the original
> form in UTF-8.
> When matching names you do form insensitive compare (one way
> to do this is nameprep(query) = nameprep(original name), and
> the nameprep(original name) can be cached to avoid doing it
> more than once). If also ACE encoding is used, the DNS server
> do ACE->UTF-8 decode followed by the same compare as above.

Yes, but this implies that nameprep has to be done on the
server, which requires fairly significant changes to servers
that serve out, or might serve out (authoritatively or from a
cache, I think) an IDN name.  If nameprep(original-name) is to
be cached, that requires further changes, changes that I imagine
would reach fairly close to the architecture of the server
designs.  It isn't the processing time that concerns me here
(not to say that might be significant, I just don't know), but
the deployment process.   And, while I haven't worked the cases,
my hunch is that un-upgraded servers might get themselves into
trouble (e.g., risk of matching errors yielding false positives)
if they didn't recognize a name that required special (nameprep)
handling.

> The difference between current matching and a IDN based
> matching is just the matching algorithm (and ACE decode). I
> expect that the IDN matching algorthm can be done good enough
> so that it will not overburden the DNS server.

For a network consisting exclusively of upgraded servers, I
expect you are correct.

   john




From owner-idn@ops.ietf.org  Mon Jul 30 10:53:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA25679
	for <idn-archive@lists.ietf.org>; Mon, 30 Jul 2001 10:53:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RD2K-0000rO-00
	for idn-data@psg.com; Mon, 30 Jul 2001 06:24:44 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RD2J-0000qR-00
	for idn@ops.ietf.org; Mon, 30 Jul 2001 06:24:43 -0700
Received: from valinor.malmo.trab.se (valinor [131.115.48.20]) by malmo.trab.se (8.10.1/TRAB-primary-2) with ESMTP id f6UDMdP27272; Mon, 30 Jul 2001 15:22:39 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Mon, 30 Jul 2001 15:24:25 +0200 (MEST) (MET)
Message-Id: <200107301324.PAA02427@valinor.malmo.trab.se>
Date: Mon, 30 Jul 2001 15:24:25 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: [idn] ZWNJ
To: roozbeh@sharif.edu, klensin@jck.com
Cc: idn@ops.ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: z4I1uSjPsrNKKRhEn/kURQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk


> But, if the goal is to
>be able to retrieve and examine the original name, then, it
>seems to me that the way to do that is to store the original
>name somewhere, rather than hoping that nameprep can both do its
>job and be reversible.

Today DNS stores the original name, and the case insensitive
matching is done by case insensitive compare.

Using UCS, the DNS could store all names using the original form
in UTF-8.
When matching names you do form insensitive compare (one way
to do this is nameprep(query) = nameprep(original name), and the
nameprep(original name) can be cached to avoid doing it more than once).
If also ACE encoding is used, the DNS server do ACE->UTF-8 decode followed
by the same compare as above.

The difference between current matching and a IDN based matching
is just the matching algorithm (and ACE decode). I expect that
the IDN matching algorthm can be done good enough so that it
will not overburden the DNS server.


   Dan




From owner-idn@ops.ietf.org  Mon Jul 30 10:53:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA25704
	for <idn-archive@lists.ietf.org>; Mon, 30 Jul 2001 10:53:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RCme-0000Ti-00
	for idn-data@psg.com; Mon, 30 Jul 2001 06:08:32 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RCmd-0000Tc-00
	for idn@ops.ietf.org; Mon, 30 Jul 2001 06:08:31 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Mon, 30 Jul 2001 06:19:51 -0700
Message-ID: <006a01c118f9$edaf5a60$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
References: <200107291517.f6TFHvN20321@nic-naa.net>
Subject: Re: [idn] Intro to my I-D 
Date: Mon, 30 Jul 2001 09:17:04 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Eric,

As you are probably somewhat aware, I am indeed working very hard.  I
want you to know that I am keeping all your questions /input in the
back of my mind as I work and that can only help.  So I just want to
thank you for all your efforts.

The only question I want to address at this moment is something that
caught my eye.  At the very end of your email below, you concluded by
saying- "Just what makes your proposal superior?".  Perhaps this is a
good time to reiterate what I said at the very beginning:

My system recognizes the same equal importance for:

1.  Registrants given the freedom/choice to point Tradition CDN to
tradition website and Simplifed CDN to simplified website.
2.  A need for Tradition CDN to Simplified CDN conversion.

(However, I also believe that other CDN systems are absolutely fine
exactly the way they are.)

Thanks
Ben Chan



----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: "ben" <ben@cc-www.com>
Cc: "xiang deng" <deng@cnnic.net.cn>; <lee@cnnic.net.cn>;
<sun@cnnic.net.cn>; <brunner@nic-naa.net>; <brunner@nic-naa.net>;
<harald@alvestrand.no>; <idn@ops.ietf.org>
Sent: Sunday, July 29, 2001 11:17 AM
Subject: Re: [idn] Intro to my I-D


[I've added idn@ops.ietf.org back to the cc'd list.
 Harald, please read and reconsider the "principle of least surprise".
 Thx.]

Ben,

What you've proposed is that for some collection of code-points, and
for
some equivalency rules (whether zone-scoped or global-scoped),
allocation
of one code-point in the collection results in pre-allocation
(reservation)
of all code-points in the collection.

Additionally, you've proposed the registrant (recipient of the
allocated
code-point equivalency class) may then modify the equivalency rule
which
created the class, and assert distinct semantics for distinct elements
of
the original (intact), now fragmented class.

To help me understand your proposal, I'll consider ASCII strings and
the
Pan-Algonquin "OU" character (U+0222) and (U+0223). A locally
constructed
French character, not present in 17th century French. I know that most
of
the North Americans and Europeans will find this choice strange, but
more
accessible, as "Indian French", than an ideogramatic example, and I
know
that my friends at CNNIC will speak to the Chinese language specifics.

Assertion: (zone scope)

In the Algonquin-preferred zone(s), e.g., abenaki.dst.me.us,
the following code-points and code-point sequences are
equivalent:
U+0070 "8" when in an alpha-string
U+0222 "8" LATIN CAPITAL LETTER OU
U+0223 "8" LATIN SMALL LETTER OU
U+0117,U+0125 "OU"
U+O117,U+0165 "Ou"
U+0157,U+0165 "ou"
U+0127 "W"
U+0167 "w"

Under your proposal, in my zone (abenaki.dst.me.us.), with ASCII case
folding
(applied to the two Latin Extended-B code points), the registrant for
"ki8na.abenaki.dst.me.us" ("ki8na" means ourselves or nous-memes),
would be
allocated or reserved:

ki{set of 4 code-point sequences}na.abenaki.dst.me.us

The registrant could then be able to associate between 0 and eight
unique
ip addresses to these 4 allocated domain names in my zone, e.g.,

ki(U+0070)na.abenaki.dst.me.us and 1.2.3.1
ki(U+0222)na.abenaki.dst.me.us and 1.2.3.2
ki(U+0223)na.abenaki.dst.me.us and 1.2.3.2
ki(U+0117,U+0125)na.abenaki.dst.me.us and 1.2.3.3
ki(U+O117,U+0165)na.abenaki.dst.me.us and 1.2.3.3
ki(U+0157,U+0165)na.abenaki.dst.me.us and 1.2.3.3
ki(U+0127)na.abenaki.dst.me.us and 1.2.3.4
ki(U+0167)na.abenaki.dst.me.us and 1.2.3.4

Without case folding there could be 8 distinct addresses rather than
just 4.

This would be very surprising to a modern literate North-Eastern
Indian, and
to scholars of the Contact Period and French and Indian literatures of
the
17th and 18th centuries. As the abenaki.dst.me.us zone manager, I
don't think
I would allow it. I would expect the equivalency rule (above) to be
adopted
by the {penobscot,passamquoddy,maliseet,micmac}.dst.me.us zone
managers, and
by other "Algonquin-aware" NSN.US zone managers. I would not expect
these to
be adopted by the dst.me.us or superior zone managers. I would expect
the same
rule and scope to exist in the .ca zone and its dependent zones.

My preference is that ki{set of 4 code-point
sequences}na.abenaki.dst.me.us
all map to a single internet address.

In the Chinese language area, which includes North America as well as
China,
your "registrant election" proposal appears to have the same
surprising set
of consequences as one registrant following one ideosyncratic
convention for
"ki8na" and another registrant, possibly the same one, following a
different
ideosyncratic convention for "ni8na" (we and you or nous et vous), and
this
only gets worse as we consider strings such as k8sk8ranmsh8dans8
(sift).

Just what makes your proposal superior?

Eric

P.S. The advantage of [30], formerly "in" the IDN WG requirements
draft, was
that it made zone-specific semantics possible. Writing in modern
Abenaki (or
any "8" using French-originating modern script) using ASCII
equivalency rules
presents a problem for 0x70 to 0x127,0x167 mapping (simplest case).




From owner-idn@ops.ietf.org  Mon Jul 30 10:53:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA25711
	for <idn-archive@lists.ietf.org>; Mon, 30 Jul 2001 10:53:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RCGS-000Pg8-00
	for idn-data@psg.com; Mon, 30 Jul 2001 05:35:16 -0700
Received: from [209.187.148.217] (helo=P2)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RCGR-000Pg1-00; Mon, 30 Jul 2001 05:35:16 -0700
Date: Mon, 30 Jul 2001 08:35:14 -0400
From: John C Klensin <klensin@jck.com>
To: Roozbeh Pournader <roozbeh@sharif.edu>
cc: idn@ops.ietf.org
Subject: Re: [idn] ZWNJ
Message-ID: <6098219.996482114@P2>
In-Reply-To: <Pine.LNX.4.33.0107291427360.15511-100000@gilas.bamdad.org>
References:  <Pine.LNX.4.33.0107291427360.15511-100000@gilas.bamda
 d.org>
X-Mailer: Mulberry/2.1.0b2 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Sunday, 29 July, 2001 15:46 +0430 Roozbeh Pournader
<roozbeh@sharif.edu> wrote:

> You're right about the identifier nature of DNS names. Being
> brought up in such a world, I'm already well familiar with the
> way this impacts the language. For a good example, see Arthur
> C Clarke's The Light of Other Days, ISBN 0812576403, where
> words like SearchEngine are common. The DNS and other
> identifier restrictions have changed the shape of English
> language, for sure.

Conceptually, however, these are _new_ words and new
identifiers, albeit with funny spellings.  The association
between "SearchEngine" and "search engine" is mostly in the mind
of the observer.  It is certainly not in the DNS.

But, to the extent that preservation of those forms is an
advantage, an external-to-the-database process such as nameprep
throws them away.  Either nameprep would have to be reversible
(which seems impossible) or we would need to store the "raw"
names in the DNS, put nameprep in the servers, and make matching
comparisons based on 
  (nameprep (query)) = nameprep (stored-raw-value)
or, worse, I suspect
  encoding(nameprep(query)) =
nameprep(encoding(stored-raw-value))

Those approaches don't seem likely to be workable and certainly
would require massive protocol and server changes -- changes
which the WG has been trying to avoid and which it has been told
are out of its scope.

Perhaps that is part of the point you are trying to make.
 
> Getting back to the thread, Arabic lacks many of the
> possiblities of the Latin script, for getting a distinguished
> sense out of a sequence of letters (which we will call
> identifiers). I consider the use of ZWNJ to be equivalent to
> the use of inter-identifier captialization. Just like that, it
> should be ignored, just like that, it will help the reader,
> and just like that, the original should be retreivable in some
> way.

I think I have understood this, although I haven't been
expressing it very well.  I think that almost every language has
one or another of these issues.  The FooBar convention, for
which believe C and UNIX get the credit (or blame), rather than
the DNS, is really not satisfactory for English, although it is
a hack that sort of works there and not for Arabic.  The basic
Han-folding decisions of Unicode submerge distinctions among the
several languages using derivations of those characters.  And so
on.

> Please note that even in single words, ZWNJ is used. In many
> single words like the Persian words for "houses", "circular",
> "eraser", "compatriot", and "synonymous", or single-word names
> of places, it may not be dropped in any way, or the word
> becomes completely unreadable.

If it is an integral part of the word, such that the word
changes or loses meaning without it, then you, indeed, have a
strong case for its preservation.  I would think that what would
then be needed would be a simple rule (i.e., one that does not
require a program to understand Arabic or consult dictionaries)
to know when it can (and should) be removed and when not.

> Arabic is connected, unlike Latin where the letters are
> separate enough that you can sometimes omit the space (like in
> domain names, or German). It's also unlike Han, where there is
> a good boundary between the words, without even the need for
> spaces. So it should use spaces and ZWNJ heavily to stop
> joining where it will ruin the meaning or readablity of the
> phrases. Please note that ZWNJ is somehow considered a
> *nothing* in the Unicode recommendation. It should only affect
> contextual shaping, and nothing else...

There is a now-traditional nasty comment about standards that
have their origins in printer drivers, but we are stuck with the
thing.

> While I see the use of space-like characters in Latin
> problematic (mainly because of indistinguishablity of the
> written word), the case is difference with ZWNJ. It is not a
> space character.

But it seems to me that, despite the fact (if I have understood
you) that the same character is used in both situations, ZWNJ is
used both within words (your examples from Persian above) and to
separate words.  The "identifier" notion says that we don't get
phrases in identifiers in alphabetic languages.  Non-alphabetic
languages and character sets get lucky in this case, since there
doesn't seem to be any point in confining them to single "words"
rather than short phrases.

> BTW, there are also many other needs for being able to
> retreive the original non-nameprepped name. Have you thought
> about national digit shapes (as used in Arabic and Indic
> scripts), for example? Many countries do not use European
> digits (which Europeans call Arabic).

Of course.  The many examples of this sort of thing, and more
flexible treatment for characters and separators that are not
part of the basic DNS model, are among the things that have
driven me to conclude that we need something with search-like,
rather than lookup, properties to handle international names
without doing violence to the underlying languages.  Any
canonicalization scheme, and any scheme that maps one character
into another, will lose information that would be desirable in
some context, and that isn't a good thing.

But, in the more limited situations you identify, it seems to me
that it would be possible to do a bit of new protocol work and
then adopt some conventions that would be of help.  Suppose, for
example, that we created a new RR type, specifically for
non-"Hosttable"-format labels, for which the "data" (target) was
a raw (no nameprep or other canonicalization or mappings)
Unicode string.  And suppose a convention were adopted such that
any non-traditional label was associated with one of these
records as well as whatever A, MX, AAAA, or equivalent RR it
pointed to (this might force us to make an exception to the "one
record only" rule for CNAME, but maybe that is just a minor
details).

Now, the IDN WG could clearly not do this -- we would need to
get DNSEXT or some other group involved.  But, if the goal is to
be able to retrieve and examine the original name, then, it
seems to me that the way to do that is to store the original
name somewhere, rather than hoping that nameprep can both do its
job and be reversible.

   john




From owner-idn@ops.ietf.org  Mon Jul 30 11:20:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA27606
	for <idn-archive@lists.ietf.org>; Mon, 30 Jul 2001 11:20:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15REh1-0003hm-00
	for idn-data@psg.com; Mon, 30 Jul 2001 08:10:51 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15REh0-0003hg-00
	for idn@ops.ietf.org; Mon, 30 Jul 2001 08:10:50 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f6UF91N23867;
	Mon, 30 Jul 2001 11:09:01 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107301509.f6UF91N23867@nic-naa.net>
To: "ben" <ben@cc-www.com>
cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Intro to my I-D 
In-Reply-To: Your message of "Mon, 30 Jul 2001 09:17:04 EDT."
             <006a01c118f9$edaf5a60$d43f7018@mtag1.on.home.com> 
Date: Mon, 30 Jul 2001 11:09:01 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Ben,

Now that Deng and I have had the chance to develop your ideas in this series
of letters, here are our conclusions:

> 1.  Registrants given the freedom/choice to point Tradition CDN to
> tradition website and Simplifed CDN to simplified website.

Restated in the sense of [30]:

	[30bis] Within a single equivalence class ["zone"],
	the registrant ["zone manager"] MUST be able to define
	traditional/simplified Chinese equivalence rules
	that suit the purpose of the registrant [zone].

	Such defined equivalences MUST [MUST NOT] remove equivalences
	that are assumed by (old or local-rule-ignorant) caches.

That is the scope issue. To paraphrase Harald Alvestrand, this creates
a possibility of "maximal surprise".

As Deng pointed out, your #1 has a geometric scailing property, with
any character string of N Chinese characters having 2^^N zone file
representations, when the character string is a name label. As a UTF-8
Chinese string may be up to 21 three-octet characters long, and each
character may have one (or more!) equivalences, this yields 2,097,152
possible distinct "names" reserved from one SC or TC IDN registration.
Slightly smaller numbers are used in the ACE discussions, so here I use
18.

A zone with bi-modal length distribution of Chinese business names, with
clusters at 8 characters and 18 characters, and 1M distinct registrants,
would have a zone file with 130,000,000,000 entries.

	.5M x 2^^8 + .5M x 2^^18 (dual "short" and "maximal" form)
	1.28e+08   + 1.31e+11 (xcalc numbers)

This appears to be "very large". You are aware of this, neh?

> 2.  A need for Tradition CDN to Simplified CDN conversion.

This goal, which you state your system recognizes with equal importance as
for goal #1, appears to be depricated (impossible) by the requirements of
goal #1.

Further, as I mentioned previously, and above in the stilted language of
scope for rules, the "conversion" is per-registrant, and effects a private
system of translating names to addresses.

What is the key value for users "opting out" of SC/TC equivalences?

Eric



From owner-idn@ops.ietf.org  Mon Jul 30 12:22:56 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA03069
	for <idn-archive@lists.ietf.org>; Mon, 30 Jul 2001 12:22:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RFc5-0004pw-00
	for idn-data@psg.com; Mon, 30 Jul 2001 09:09:49 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15RFc4-0004pp-00
	for idn@ops.ietf.org; Mon, 30 Jul 2001 09:09:48 -0700
Message-ID: <007001c11913$35d159b0$0b01a8c0@davidvaio>
From: "David Leung" <david@neteka.com>
To: "ben" <ben@cc-www.com>, <idn@ops.ietf.org>
References: <003d01c116d7$39b7a180$d43f7018@mtag1.on.home.com> <00d401c116d9$cae2f3b0$0b01a8c0@davidvaio> <001101c11704$f2976280$d43f7018@mtag1.on.home.com>
Subject: Re: [idn] Intro to my I-D
Date: Mon, 30 Jul 2001 12:18:02 -0400
Organization: Neteka Inc.
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_006D_01C118F1.AE06C9F0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_006D_01C118F1.AE06C9F0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Ben,

When IDN WG started, James the co-chair posted a draft on Han folding =
which is similar to what you are trying to propose. Also CNNIC and TWNIC =
on that last IETF proposed the TC-SC folding as well. If you look under =
the section of IDN WG at www.ietf.org, you should see the drafts there. =
Also www.i-d-n.net is another good place to look at to follow up on =
what's IDN and where it is going.

David

  ----- Original Message -----=20
  From: ben=20
  To: David Leung ; idn@ops.ietf.org=20
  Sent: Friday, July 27, 2001 9:30 PM
  Subject: Re: [idn] Intro to my I-D


  Hi David,

  Can you tell me where to find the I-D?

  Thanks,
  Ben Chan

  ----- Original Message -----=20
  From: David Leung=20
  To: ben ; idn@ops.ietf.org=20
  Sent: Friday, July 27, 2001 4:21 PM
  Subject: Re: [idn] Intro to my I-D


  I think there is already an Internet Draft on SC-TC(Simplified Chinese =
and Traditional Chinese) folding.

    ----- Original Message -----=20
    From: ben=20
    To: idn@ops.ietf.org=20
    Sent: Friday, July 27, 2001 4:03 PM
    Subject: [idn] Intro to my I-D


    It appears that I-D will not be accepted til Aug 14, so there is =
plenty of time for me to prepare it.  But anyways, here is a very simple =
intro to why I am interested in "the need for conversion between =
different (yet similiar) scripts":

    I have a very small company that offers CDNs (Chinese domain names). =
 My hope is to be able to take the benefits from other systems and =
combine them together to form a supreme.  (Although I want to emphasize =
that other systems are 100% fine exactly the way they are.)  Combining =
the following 2 benefits together is crucial to my supreme system with =
both weighting EXACTLY THE SAME IMPORTANCE:

    Benefit A-  A simplified CDN points to a website that is written in =
simplified Chinese (GB encoding) for visitors in mainland China or =
Singapore while a traditional CDN points to a website written in =
traditional Chinese (Big5 encoding) for visitors in Taiwan or Hong Kong.

    Benefit B-  When a registrant registers a simplified CDN, the =
corresponding traditional CDN(s) is automatically reserved and visa =
versa.

    I will put all the details into the draft and submit it by Aug 14.  =
Hopefully, I can get 7 supporters- thank you very much!

    Ben Chan


------=_NextPart_000_006D_01C118F1.AE06C9F0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2462.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi Ben,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>When IDN WG started, James the co-chair =
posted a=20
draft on Han folding which is similar to what you are trying to propose. =
Also=20
CNNIC and TWNIC on that last IETF proposed the TC-SC folding as well. If =
you=20
look&nbsp;under the section of IDN WG at <A=20
href=3D"http://www.ietf.org">www.ietf.org</A>, you should see the drafts =
there.=20
Also <A href=3D"http://www.i-d-n.net">www.i-d-n.net</A> is another good =
place to=20
look at&nbsp;to follow up on what's IDN and where it is =
going.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>David</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dben@cc-www.com href=3D"mailto:ben@cc-www.com">ben</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Ddavid@neteka.com =

  href=3D"mailto:david@neteka.com">David Leung</A> ; <A =
title=3Didn@ops.ietf.org=20
  href=3D"mailto:idn@ops.ietf.org">idn@ops.ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Friday, July 27, 2001 =
9:30 PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [idn] Intro to my =
I-D</DIV>
  <DIV><BR></DIV>
  <DIV>
  <DIV><FONT face=3DArial size=3D2>Hi David,</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Can you tell me where to find the=20
  I-D?</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Ben Chan</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></DIV>
  <DIV style=3D"FONT: 10pt arial">----- Original Message -----=20
  <DIV style=3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A=20
  title=3Ddavid@neteka.com href=3D"mailto:david@neteka.com">David =
Leung</A> </DIV>
  <DIV><B>To:</B> <A title=3Dben@cc-www.com =
href=3D"mailto:ben@cc-www.com">ben</A> ;=20
  <A title=3Didn@ops.ietf.org =
href=3D"mailto:idn@ops.ietf.org">idn@ops.ietf.org</A>=20
  </DIV>
  <DIV><B>Sent:</B> Friday, July 27, 2001 4:21 PM</DIV>
  <DIV><B>Subject:</B> Re: [idn] Intro to my I-D</DIV></DIV>
  <DIV><BR></DIV>
  <DIV><FONT face=3DArial size=3D2>I think there is already an Internet =
Draft on=20
  SC-TC(Simplified Chinese and Traditional Chinese) =
folding.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
    <DIV=20
    style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
    <A title=3Dben@cc-www.com href=3D"mailto:ben@cc-www.com">ben</A> =
</DIV>
    <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Didn@ops.ietf.org=20
    href=3D"mailto:idn@ops.ietf.org">idn@ops.ietf.org</A> </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Friday, July 27, 2001 =
4:03=20
    PM</DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [idn] Intro to my =
I-D</DIV>
    <DIV><BR></DIV>
    <DIV><FONT face=3DArial size=3D2>It appears that I-D will not be =
accepted til=20
    Aug 14, so there is plenty of time for me to prepare it.&nbsp; But =
anyways,=20
    here is a very simple intro to why I am interested in&nbsp;"the need =
for=20
    conversion between different (yet similiar) scripts":</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>I have a very small company that =
offers CDNs=20
    (Chinese domain names).&nbsp;&nbsp;My&nbsp;hope is to be able to=20
    take&nbsp;the benefits&nbsp;from other systems and combine them =
together to=20
    form a supreme.&nbsp; (Although I want to emphasize that other =
systems are=20
    100% fine exactly the way they are.)&nbsp;&nbsp;Combining =
the&nbsp;following=20
    2 benefits together&nbsp;is crucial to my supreme system with both =
weighting=20
    EXACTLY THE SAME IMPORTANCE:</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>Benefit&nbsp;A-&nbsp; A simplified =
CDN points=20
    to a website that is written in simplified Chinese (GB encoding) for =

    visitors in mainland China or Singapore while a traditional CDN =
points to a=20
    website written&nbsp;in traditional Chinese&nbsp;(Big5 encoding) for =

    visitors in Taiwan or Hong Kong.</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>Benefit B-&nbsp; When a registrant =
registers a=20
    simplified CDN, the corresponding traditional CDN(s) is =
automatically=20
    reserved and visa versa.</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>I will put all the details into the =
draft and=20
    submit it by Aug 14.&nbsp; Hopefully, I can get 7 supporters- thank =
you very=20
    much!</FONT></DIV>
    <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2>Ben Chan</FONT></DIV>
    <DIV><FONT face=3DArial=20
size=3D2></FONT>&nbsp;</DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_006D_01C118F1.AE06C9F0--




From owner-idn@ops.ietf.org  Mon Jul 30 14:08:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA11824
	for <idn-archive@lists.ietf.org>; Mon, 30 Jul 2001 14:08:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RGXe-00067h-00
	for idn-data@psg.com; Mon, 30 Jul 2001 10:09:18 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RGXc-00067X-00
	for idn@ops.ietf.org; Mon, 30 Jul 2001 10:09:17 -0700
Received: from zetnet.co.uk (man-s155.dialup.zetnet.co.uk [194.247.45.26])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6UH8v000317;
	Mon, 30 Jul 2001 18:08:58 +0100
Message-ID: <3B658372.C8B05B3C@zetnet.co.uk>
Date: Mon, 30 Jul 2001 16:55:30 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: Dave Crocker <dcrocker@brandenburg.com>, idn@ops.ietf.org
Subject: Re: [idn] We are quibbling about WHAT?
References: <5.1.0.14.2.20010729172557.0302f008@brandenburg.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

Dave Crocker wrote:
> UTF-8 takes a set of table entries, and maps them to 8-bit strings.
> 
> ACE takes the same set of table entries and maps them to a subset of 7-bit
> ASCII.  For order-of-magnitude convenience, let us call this 6.5-bit ASCII.
> 
> Never having been any good at math, I'm still going to suggest that the
> entire debate that has garnered such religious positions -- and, far worse,
> is causing continuing delay to this working group -- concerns an encoding
> efficiency difference of, at most, 19 percent.

The debate between ACE and UTF-8 has nothing to do with encoding
efficiency. The benefit of UTF-8 is in having DNS names in the same
encoding as the surrounding text, rather than having to treat them as a
special case.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO2WDWzkCAxeYt5gVAQG9UAf8DBkbBaMJGYG/lC2mI+4R4D1rbnXbWMvq
0mIK/gLF9ZbvfgAejaWmGtlwkh5Q0NnSU5ZnYreZ8g3CBsLxgz6pRhNovwHrLyfz
QdVrxeU7ReSMtfCL6axSacdO/ZzsEkW1j9/Eez7S1RBwAXl1b+jh9efWcKsQg7V/
wXwF/6vfx8+sy/5LmTucFH/NnIUZaT3u3ArR+jx8DH/PdYYFBdvT28BH8vVFVlo1
7M+ZfdOmUEu1m3hCparx+CEEKpzak6CQqkGyZRlSPi3jxKreRlz/MKd/4tskPdRf
D28EXeUoqPh620YyQLFIXm0rVRImO5HbuNdAbXw9ChR/lakQ+sax4g==
=CZ0m
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Mon Jul 30 14:39:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA14739
	for <idn-archive@lists.ietf.org>; Mon, 30 Jul 2001 14:39:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RHjY-00089y-00
	for idn-data@psg.com; Mon, 30 Jul 2001 11:25:40 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RHjX-00089s-00
	for idn@ops.ietf.org; Mon, 30 Jul 2001 11:25:39 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Mon, 30 Jul 2001 11:36:50 -0700
Message-ID: <016301c11926$350a3e80$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
References: <200107301509.f6UF91N23867@nic-naa.net>
Subject: Re: [idn] Intro to my I-D 
Date: Mon, 30 Jul 2001 14:34:02 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Eric,

For over 2 years I have been working on a CDN system that takes the
benefits from other CDNs and combine them to form a supreme.  Within
that time, I have also gathered thousands upon thousands of
registrations, criticism, enquiries, ideas, needs, suggestions, etc,
from ordinary everyday people all over the world- from China to Canada
and everywhere else in between.

I am surprised that you can come to a conclusion in 2 days... and
without even reading my I-D.  However, I do appreciate someone with
your brilliant mind and technical knowledge constantly on my back as
that will only serve to help us all.

Thanks,
Ben Chan



----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: "ben" <ben@cc-www.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
<idn@ops.ietf.org>; <brunner@nic-naa.net>
Sent: Monday, July 30, 2001 11:09 AM
Subject: Re: [idn] Intro to my I-D


Ben,

Now that Deng and I have had the chance to develop your ideas in this
series
of letters, here are our conclusions:

> 1.  Registrants given the freedom/choice to point Tradition CDN to
> tradition website and Simplifed CDN to simplified website.

Restated in the sense of [30]:

[30bis] Within a single equivalence class ["zone"],
the registrant ["zone manager"] MUST be able to define
traditional/simplified Chinese equivalence rules
that suit the purpose of the registrant [zone].

Such defined equivalences MUST [MUST NOT] remove equivalences
that are assumed by (old or local-rule-ignorant) caches.

That is the scope issue. To paraphrase Harald Alvestrand, this creates
a possibility of "maximal surprise".

As Deng pointed out, your #1 has a geometric scailing property, with
any character string of N Chinese characters having 2^^N zone file
representations, when the character string is a name label. As a UTF-8
Chinese string may be up to 21 three-octet characters long, and each
character may have one (or more!) equivalences, this yields 2,097,152
possible distinct "names" reserved from one SC or TC IDN registration.
Slightly smaller numbers are used in the ACE discussions, so here I
use
18.

A zone with bi-modal length distribution of Chinese business names,
with
clusters at 8 characters and 18 characters, and 1M distinct
registrants,
would have a zone file with 130,000,000,000 entries.

.5M x 2^^8 + .5M x 2^^18 (dual "short" and "maximal" form)
1.28e+08   + 1.31e+11 (xcalc numbers)

This appears to be "very large". You are aware of this, neh?

> 2.  A need for Tradition CDN to Simplified CDN conversion.

This goal, which you state your system recognizes with equal
importance as
for goal #1, appears to be depricated (impossible) by the requirements
of
goal #1.

Further, as I mentioned previously, and above in the stilted language
of
scope for rules, the "conversion" is per-registrant, and effects a
private
system of translating names to addresses.

What is the key value for users "opting out" of SC/TC equivalences?

Eric








From owner-idn@ops.ietf.org  Mon Jul 30 20:26:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA03923
	for <idn-archive@lists.ietf.org>; Mon, 30 Jul 2001 20:26:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RMpq-0008jU-00
	for idn-data@psg.com; Mon, 30 Jul 2001 16:52:30 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RMpo-0008b1-00
	for idn@ops.ietf.org; Mon, 30 Jul 2001 16:52:29 -0700
Received: from soobok ([210.217.27.237] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id IAA20439;
	Tue, 31 Jul 2001 08:52:07 +0900
Message-ID: <00df01c11953$7b40aa60$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
References: <200107280351.f6S3pHN12415@nic-naa.net>
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE label version 0.2 
Date: Tue, 31 Jul 2001 08:58:07 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi, Eric

For pure Han labels (150,000 sample domains),
  the mean average # of distinct code points is roughly the same as
  # of code points in the label. i.e. most of letters are distinct.

For Latin (European ) labels ( in 44000 sample domains)
  the mean average # of distinct code points is roughly HALF of
  # of code points.
  We need only one lookalike encoding for a distinct code point.
  I guess only half or two-thirds of them are look-alike ones.

This will partly answer for some of your questions.

Look into ATOM# columns of the next statistics if you have time. :-)

Soobok Lee
------------------------------------------------------------------------

For .Latin

N:            length of a domain label ( # of code points)
FREQ:         number domains of length N
N*FREQ:       sum of # of code points of domains of length N
SUM OF AMCZ:  sum of lengths of AMCZ labels
X:            SUM OF AMCZ / N * FREQ
SUM OF LAMCZ: sum of lengths of LAMCZ labels
Y:            SUM OF LAMCZ / N * FREQ
COMP:         (SUM OF LAMCZ - SUM OF AMCZ) / SUM OF AMCZ * 100
ATOM#:        MEAN AVERAGE of # of DISTINCT ATOMS

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP| ATOM#

|  1|      85|        85|       169(1.99)|       169(1.99)|0.00|1.00
|  2|    1026|      2052|      4031(1.96)|      4031(1.96)|0.00|1.96
|  3|     993|      2979|      4954(1.66)|      4954(1.66)|0.00|2.84
|  4|    1730|      6920|     10440(1.51)|     10440(1.51)|0.00|3.81
|  5|    3089|     15445|     22020(1.43)|     22020(1.43)|0.00|4.75
|  6|    3760|     22560|     30529(1.35)|     30529(1.35)|0.00|5.57
|  7|    4134|     28938|     37669(1.30)|     37669(1.30)|0.00|6.32
|  8|    4405|     35240|     44532(1.26)|     44532(1.26)|0.00|7.02
|  9|    4286|     38574|     47653(1.24)|     47653(1.24)|0.00|7.73
| 10|    4027|     40270|     49106(1.22)|     49106(1.22)|0.00|8.33
| 11|    3523|     38753|     47178(1.22)|     47178(1.22)|0.00|8.89
| 12|    2777|     33324|     40538(1.22)|     40538(1.22)|0.00|9.43
| 13|    2325|     30225|     36672(1.21)|     36672(1.21)|0.00|9.96
| 14|    1928|     26992|     32752(1.21)|     32752(1.21)|0.00|10.44
| 15|    1537|     23055|     27801(1.21)|     27801(1.21)|0.00|10.86
| 16|    1276|     20416|     24422(1.20)|     24422(1.20)|0.00|11.24
| 17|    1029|     17493|     20741(1.19)|     20741(1.19)|0.00|11.68
| 18|     776|     13968|     16438(1.18)|     16438(1.18)|0.00|12.05
| 19|     588|     11172|     13057(1.17)|     13057(1.17)|0.00|12.40
| 20|     429|      8580|      9956(1.16)|      9956(1.16)|0.00|12.67
| 21|     296|      6216|      7146(1.15)|      7146(1.15)|0.00|12.93
| 22|     177|      3894|      4476(1.15)|      4476(1.15)|0.00|13.20
| 23|     116|      2668|      3032(1.14)|      3032(1.14)|0.00|13.59
| 24|      65|      1560|      1772(1.14)|      1772(1.14)|0.00|13.40
| 25|      67|      1675|      1899(1.13)|      1899(1.13)|0.00|14.16
| 26|      36|       936|      1054(1.13)|      1054(1.13)|0.00|13.53
| 27|      29|       783|       880(1.12)|       880(1.12)|0.00|15.00
| 28|      10|       280|       317(1.13)|       317(1.13)|0.00|14.60
| 29|      10|       290|       321(1.11)|       321(1.11)|0.00|18.30
| 30|       7|       210|       231(1.10)|       231(1.10)|0.00|14.14
| 31|       7|       217|       243(1.12)|       243(1.12)|0.00|19.00
| 32|       9|       288|       321(1.11)|       321(1.11)|0.00|15.67
| 33|       4|       132|       146(1.11)|       146(1.11)|0.00|18.50


For .Unihan

N:            length of a domain label ( # of code points)
FREQ:         number domains of length N
N*FREQ:       sum of # of code points of domains of length N
SUM OF AMCZ:  sum of lengths of AMCZ labels
X:            SUM OF AMCZ / N * FREQ
SUM OF LAMCZ: sum of lengths of LAMCZ labels
Y:            SUM OF LAMCZ / N * FREQ
COMP:         (SUM OF LAMCZ - SUM OF AMCZ) / SUM OF AMCZ * 100
ATOM#:        MEAN AVERAGE of # of DISTINCT ATOMS

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP| ATOM#

|  1|    3735|      3735|     14940(4.00)|     14940(4.00)|0.00|1.00
|  2|   42793|     85586|    322222(3.76)|    289658(3.38)|10.11|1.99
|  3|   28033|     84099|    295183(3.51)|    256250(3.05)|13.19|2.98
|  4|   54607|    218428|    740073(3.39)|    608569(2.79)|17.77|3.98
|  5|   12591|     62955|    208185(3.31)|    167839(2.67)|19.38|4.97
|  6|    7680|     46080|    149606(3.25)|    116532(2.53)|22.11|5.95
|  7|    2761|     19327|     61992(3.21)|     47043(2.43)|24.11|6.94
|  8|    1336|     10688|     33890(3.17)|     25154(2.35)|25.78|7.83
|  9|     641|      5769|     18131(3.14)|     13383(2.32)|26.19|8.86
| 10|     298|      2980|      9260(3.11)|      6821(2.29)|26.34|9.72
| 11|     137|      1507|      4712(3.13)|      3330(2.21)|29.33|10.79
| 12|      57|       684|      2114(3.09)|      1569(2.29)|25.78|11.40
| 13|      25|       325|      1008(3.10)|       760(2.34)|24.60|12.44
| 14|       6|        84|       259(3.08)|       187(2.23)|27.80|13.17
| 15|       6|        90|       272(3.02)|       199(2.21)|26.84|14.50
| 17|       1|        17|        49(2.88)|        33(1.94)|32.65|16.00

|   |  154707|    542354|   1861896(3.43)|   1552267(2.86)|16.63|



----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: "Soobok Lee" <lsb@postel.co.kr>
Cc: <idn@ops.ietf.org>; <brunner@nic-naa.net>
Sent: Saturday, July 28, 2001 12:51 PM
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE
label version 0.2


> Soobok,
>
> Your example of U+30AB and U+529B is clear, but as you mention, most
> Han/Hangeul do not have look-alike characters.
>
> Consider a hypothetical proposal to place distinct abstract character
> repertoires in disjoint blocks in some equally hypothetical standard
> coded character set, and assume that some character(s) have "look-alike"
> correspondences in multiple disjoint blocks.
>
> In particular, assume that in blocks i, j, and k, there exists code-points
> for the characters A(i), A(j), and A(k), and that A(i) "looks-like" A(j)
> and A(j) "looks-like" A(k).
>
> Further assume that for this property of "similarity" or "borrowing" (at
> least of the visual form) in each of these blocks is unlike the case in
> Han/Hangeul (sparce), and most do have look-alike characters (dense). Is
> there some point at which the "non-rarity" of "look-alike" would make a
> scheme such as the one you've proposed cumbersome? If so, this could be
> a constraint upon future modifications of a particular CCS.
>
> Thanks for taking the time to think about this, I know it isn't what you
> had in mind when taking on the Latin/Greek and Han/Hangeul similarities.
>
> Eric
>




From owner-idn@ops.ietf.org  Mon Jul 30 22:07:25 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA09490
	for <idn-archive@lists.ietf.org>; Mon, 30 Jul 2001 22:07:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RNre-0007rd-00
	for idn-data@psg.com; Mon, 30 Jul 2001 17:58:26 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RNrb-0007k7-00
	for idn@ops.ietf.org; Mon, 30 Jul 2001 17:58:24 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f6V0uSN25816
	for <idn@ops.ietf.org>; Mon, 30 Jul 2001 20:56:28 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107310056.f6V0uSN25816@nic-naa.net>
To: idn@ops.ietf.org
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE label version 0.2 
In-Reply-To: Your message of "Mon, 30 Jul 2001 12:26:45 +0800."
             <01f001c118af$d7831500$68da15a5@jamessonyvaio> 
Date: Mon, 30 Jul 2001 20:56:28 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk


I agree with the co-chair's conclusion that the subject matter itself is
outside of the scope of the working group.

Fundamentally, the issue that is the subject of "look-alike" discussion is
elements of an abstract character repertoire within a coded character set,
which have a property of visual similarity. From a broad scripts frame of
reference, e.g., "Han Unification", to a macro-scale "things that look like
circles", to the micro-scale of individual characters, this is the work of
bodies which create abstract character repertoires and coded character sets.

It would hardly matter if such a draft was "in the pool" or not.

I don't agree with the suggestion made by the co-chair that perhaps there
is a security concern for "look-alike" characters.

In the requirements draft, section 3 (Security Considerations) there is the 
hopeful statement that "a solution" not be "less secure" than the current
DNS. Skipping over the minor problem that this may be an underspecification,
hostname-based authentication is historic (and inachievable, hence dnssec),
and invocation of identd is ... unusual in the normal course of app/resolver
/transport/nameserver/transport/app sequences.

The existance of "misleading identifiers" formed with an extended repetoire
(independent of whether elements of the extended repetoire are transported
in encapsulated, or native forms) appears to require that two or more "near"
(Hamming distence) identifiers exist.

A protocol that is capable of signaling the existence of name proximality
is something other than the DNS. That protocol, whatever it is, can have a
"Security Considerations" section that treats the subject of minimal Hamming
distance (or any other form of similarity metric), hence some property that
relates to authentication et al, and "misleading identifiers", hence of
"look-alike" characters.

So, after all this (which I'm sorry to say took me much longer to write than
for many to read), I think "safely encoding" is not "safe", and we should
not do "encoding".

Eric



From owner-idn@ops.ietf.org  Mon Jul 30 23:15:27 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA13444
	for <idn-archive@lists.ietf.org>; Mon, 30 Jul 2001 23:15:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RPmv-000Af8-00
	for idn-data@psg.com; Mon, 30 Jul 2001 20:01:41 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RPmt-000Af2-00
	for idn@ops.ietf.org; Mon, 30 Jul 2001 20:01:39 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 000FAFFC07; Tue, 31 Jul 2001 11:03:17 +0800 (SGT)
Message-ID: <05f701c1196d$15d11c40$68da15a5@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "ben" <ben@cc-www.com>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
References: <200107291517.f6TFHvN20321@nic-naa.net> <006a01c118f9$edaf5a60$d43f7018@mtag1.on.home.com>
Subject: Re: [idn] Intro to my I-D 
Date: Tue, 31 Jul 2001 11:01:24 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Ben,

Wearing my i-DNS.net hat, there is a research work we been doing on
Onomastic Normalization Engine (ONE) for Chinese, Japanese and Korean
for registration purposes.

For your I-D on Chinese, maybe it is worthwhile for you to take a look
at ONE-C. You can find it at
http://playground.i-dns.net/one/onec_sum.htm

-James Seng

----- Original Message -----
From: "ben" <ben@cc-www.com>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
Sent: Monday, July 30, 2001 9:17 PM
Subject: Re: [idn] Intro to my I-D


> Hi Eric,
>
> As you are probably somewhat aware, I am indeed working very hard.  I
> want you to know that I am keeping all your questions /input in the
> back of my mind as I work and that can only help.  So I just want to
> thank you for all your efforts.
>
> The only question I want to address at this moment is something that
> caught my eye.  At the very end of your email below, you concluded by
> saying- "Just what makes your proposal superior?".  Perhaps this is a
> good time to reiterate what I said at the very beginning:
>
> My system recognizes the same equal importance for:
>
> 1.  Registrants given the freedom/choice to point Tradition CDN to
> tradition website and Simplifed CDN to simplified website.
> 2.  A need for Tradition CDN to Simplified CDN conversion.
>
> (However, I also believe that other CDN systems are absolutely fine
> exactly the way they are.)
>
> Thanks
> Ben Chan
>
>
>
> ----- Original Message -----
> From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
> To: "ben" <ben@cc-www.com>
> Cc: "xiang deng" <deng@cnnic.net.cn>; <lee@cnnic.net.cn>;
> <sun@cnnic.net.cn>; <brunner@nic-naa.net>; <brunner@nic-naa.net>;
> <harald@alvestrand.no>; <idn@ops.ietf.org>
> Sent: Sunday, July 29, 2001 11:17 AM
> Subject: Re: [idn] Intro to my I-D
>
>
> [I've added idn@ops.ietf.org back to the cc'd list.
>  Harald, please read and reconsider the "principle of least surprise".
>  Thx.]
>
> Ben,
>
> What you've proposed is that for some collection of code-points, and
> for
> some equivalency rules (whether zone-scoped or global-scoped),
> allocation
> of one code-point in the collection results in pre-allocation
> (reservation)
> of all code-points in the collection.
>
> Additionally, you've proposed the registrant (recipient of the
> allocated
> code-point equivalency class) may then modify the equivalency rule
> which
> created the class, and assert distinct semantics for distinct elements
> of
> the original (intact), now fragmented class.
>
> To help me understand your proposal, I'll consider ASCII strings and
> the
> Pan-Algonquin "OU" character (U+0222) and (U+0223). A locally
> constructed
> French character, not present in 17th century French. I know that most
> of
> the North Americans and Europeans will find this choice strange, but
> more
> accessible, as "Indian French", than an ideogramatic example, and I
> know
> that my friends at CNNIC will speak to the Chinese language specifics.
>
> Assertion: (zone scope)
>
> In the Algonquin-preferred zone(s), e.g., abenaki.dst.me.us,
> the following code-points and code-point sequences are
> equivalent:
> U+0070 "8" when in an alpha-string
> U+0222 "8" LATIN CAPITAL LETTER OU
> U+0223 "8" LATIN SMALL LETTER OU
> U+0117,U+0125 "OU"
> U+O117,U+0165 "Ou"
> U+0157,U+0165 "ou"
> U+0127 "W"
> U+0167 "w"
>
> Under your proposal, in my zone (abenaki.dst.me.us.), with ASCII case
> folding
> (applied to the two Latin Extended-B code points), the registrant for
> "ki8na.abenaki.dst.me.us" ("ki8na" means ourselves or nous-memes),
> would be
> allocated or reserved:
>
> ki{set of 4 code-point sequences}na.abenaki.dst.me.us
>
> The registrant could then be able to associate between 0 and eight
> unique
> ip addresses to these 4 allocated domain names in my zone, e.g.,
>
> ki(U+0070)na.abenaki.dst.me.us and 1.2.3.1
> ki(U+0222)na.abenaki.dst.me.us and 1.2.3.2
> ki(U+0223)na.abenaki.dst.me.us and 1.2.3.2
> ki(U+0117,U+0125)na.abenaki.dst.me.us and 1.2.3.3
> ki(U+O117,U+0165)na.abenaki.dst.me.us and 1.2.3.3
> ki(U+0157,U+0165)na.abenaki.dst.me.us and 1.2.3.3
> ki(U+0127)na.abenaki.dst.me.us and 1.2.3.4
> ki(U+0167)na.abenaki.dst.me.us and 1.2.3.4
>
> Without case folding there could be 8 distinct addresses rather than
> just 4.
>
> This would be very surprising to a modern literate North-Eastern
> Indian, and
> to scholars of the Contact Period and French and Indian literatures of
> the
> 17th and 18th centuries. As the abenaki.dst.me.us zone manager, I
> don't think
> I would allow it. I would expect the equivalency rule (above) to be
> adopted
> by the {penobscot,passamquoddy,maliseet,micmac}.dst.me.us zone
> managers, and
> by other "Algonquin-aware" NSN.US zone managers. I would not expect
> these to
> be adopted by the dst.me.us or superior zone managers. I would expect
> the same
> rule and scope to exist in the .ca zone and its dependent zones.
>
> My preference is that ki{set of 4 code-point
> sequences}na.abenaki.dst.me.us
> all map to a single internet address.
>
> In the Chinese language area, which includes North America as well as
> China,
> your "registrant election" proposal appears to have the same
> surprising set
> of consequences as one registrant following one ideosyncratic
> convention for
> "ki8na" and another registrant, possibly the same one, following a
> different
> ideosyncratic convention for "ni8na" (we and you or nous et vous), and
> this
> only gets worse as we consider strings such as k8sk8ranmsh8dans8
> (sift).
>
> Just what makes your proposal superior?
>
> Eric
>
> P.S. The advantage of [30], formerly "in" the IDN WG requirements
> draft, was
> that it made zone-specific semantics possible. Writing in modern
> Abenaki (or
> any "8" using French-originating modern script) using ASCII
> equivalency rules
> presents a problem for 0x70 to 0x127,0x167 mapping (simplest case).
>
>




From owner-idn@ops.ietf.org  Mon Jul 30 23:59:31 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA15468
	for <idn-archive@lists.ietf.org>; Mon, 30 Jul 2001 23:59:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RQNU-000BS4-00
	for idn-data@psg.com; Mon, 30 Jul 2001 20:39:28 -0700
Received: from femail44.sdc1.sfba.home.com ([24.254.60.38])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RQNT-000BRx-00
	for idn@ops.ietf.org; Mon, 30 Jul 2001 20:39:27 -0700
Received: from c1340594a ([65.11.104.12]) by femail44.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20010731033921.NDEE28154.femail44.sdc1.sfba.home.com@c1340594a>;
          Mon, 30 Jul 2001 20:39:21 -0700
Message-ID: <003e01c11972$9d715160$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "Roozbeh Pournader" <roozbeh@sharif.edu>
Cc: <idn@ops.ietf.org>
References: <Pine.LNX.4.33.0107291427360.15511-100000@gilas.bamdad.org>
Subject: Re: [idn] ZWNJ
Date: Mon, 30 Jul 2001 20:40:59 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

After giving this some thought, I agree with Roozbeh that the ZWNJ should be
removed from the prohibited list, and added to the Mapped Out list.

There is a strong difference between this and the BIDI codes. Those could be
used to provide a display that was very much different than the default
ordering, and could lead to confusion or be used for spoofing. ZWNJ on the
other hand, is harmless. The only effect it would have is to break a normal
cursive join, which would be easily recognized for what it is.

Mark

—————

πάντων μέτρον ἄνθρωπος — Πρωταγόρας
[http://www.macchiato.com]

----- Original Message -----
From: "Roozbeh Pournader" <roozbeh@sharif.edu>
To: "John C Klensin" <klensin@jck.com>
Cc: <idn@ops.ietf.org>
Sent: Sunday, July 29, 2001 04:16
Subject: Re: [idn] ZWNJ


>
> John,
>
> You're right about the identifier nature of DNS names. Being brought up in
> such a world, I'm already well familiar with the way this impacts the
> language. For a good example, see Arthur C Clarke's The Light of Other
> Days, ISBN 0812576403, where words like SearchEngine are common. The DNS
> and other identifier restrictions have changed the shape of English
> language, for sure.
>
> Getting back to the thread, Arabic lacks many of the possiblities of the
> Latin script, for getting a distinguished sense out of a sequence of
> letters (which we will call identifiers). I consider the use of ZWNJ to be
> equivalent to the use of inter-identifier captialization. Just like that,
> it should be ignored, just like that, it will help the reader, and just
> like that, the original should be retreivable in some way.
>
> Please note that even in single words, ZWNJ is used. In many single words
> like the Persian words for "houses", "circular", "eraser", "compatriot",
> and "synonymous", or single-word names of places, it may not be dropped in
> any way, or the word becomes completely unreadable.
>
> Arabic is connected, unlike Latin where the letters are separate enough
> that you can sometimes omit the space (like in domain names, or German).
> It's also unlike Han, where there is a good boundary between the words,
> without even the need for spaces. So it should use spaces and ZWNJ heavily
> to stop joining where it will ruin the meaning or readablity of the
> phrases. Please note that ZWNJ is somehow considered a *nothing* in the
> Unicode recommendation. It should only affect contextual shaping, and
> nothing else...
>
> While I see the use of space-like characters in Latin problematic (mainly
> because of indistinguishablity of the written word), the case is
> difference with ZWNJ. It is not a space character.
>
> BTW, there are also many other needs for being able to retreive the
> original non-nameprepped name. Have you thought about national digit
> shapes (as used in Arabic and Indic scripts), for example? Many countries
> do not use European digits (which Europeans call Arabic).
>
> roozbeh
>
> On Sat, 28 Jul 2001, John C Klensin wrote:
>
> > DNS names are identifiers and, as identifiers, are subject to
> > certain restrictions.  Length is one of them -- we even have
> > words in English that are over 63 character long, although there
> > aren't many of them, and they can't be used in domain names.  A
> > second is that, as identifiers, labels are what computer languge
> > syntax folks call "atoms" or "atomic".  That typically means
> > "one label, one "word".  There is a long history of pushing
> > words together to make one DNS labels and using either the one
> > joining character available (hyphen) or just catenating them.
> > In the latter case, we just hope the user will figure out what
> > is going on to preserve whatever mneumonic value we intend.
> >
> > Parenthetically, this is one place where our colleagues with
> > ideographic languages have a huge advantage: they can actually
> > write multi-word phrases into DNS labels/identifiers without
> > doing violence to the natural rules of the writing system.
> >
> > So I don't know quite what to do with ZWNJ and other separators
> > or near-separators without opening the door to other characters
> > normally used in other languages as near-separators or
> > punctuation or near-punctuation, e.g., ":", "'", "!", or "&",
> > which have been used, normally or artistically, in Indo-European
> > languages using Roman-derived character sets for many years, and
> > even recognizing distinct interpretations for some of the
> > distinct spacing characters and hyphenation ones in Unicode.
> >
> > For example, while I would _strongly_ not recommend going down
> > this path, we could, in principle, adopt presentation and coding
> > rules that would permit, e.g.,
> >
> >    "O'Reilly & Associates"
> >
> > to use the domain name
> >
> >    www."O'Reilly & Associates".com
> >
> > by coding the key second label as
> >    O(U+0027)Reilly(U+00A0)(U+0026)(U+00A0)Associates
> >
> > Again, I don't suggest doing this, but, ultimately, the DNS
> > itself would have no problems with it and, if one starts
> > introducing near-space characters from other scripts, then there
> > is little justification for prohibiting this type of usage in
> > Roman-based ones.
> >
> >      john
> >
>
>
>
>
>




From owner-idn@ops.ietf.org  Tue Jul 31 00:03:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA15691
	for <idn-archive@lists.ietf.org>; Tue, 31 Jul 2001 00:03:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RQMP-000BQw-00
	for idn-data@psg.com; Mon, 30 Jul 2001 20:38:21 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RQMP-000BQp-00
	for idn@ops.ietf.org; Mon, 30 Jul 2001 20:38:21 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Mon, 30 Jul 2001 20:49:38 -0700
Message-ID: <00f501c11973$71796880$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "James Seng/Personal" <James@Seng.cc>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
References: <200107291517.f6TFHvN20321@nic-naa.net> <006a01c118f9$edaf5a60$d43f7018@mtag1.on.home.com> <05f701c1196d$15d11c40$68da15a5@jamessonyvaio>
Subject: Re: [idn] Intro to my I-D 
Date: Mon, 30 Jul 2001 23:46:54 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi James,

Thanks, I will take a look at it.  If I have any questions, I will
email you.

Ben Chan


----- Original Message -----
From: "James Seng/Personal" <James@Seng.cc>
To: "ben" <ben@cc-www.com>; "Eric Brunner-Williams in Portland Maine"
<brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
Sent: Monday, July 30, 2001 11:01 PM
Subject: Re: [idn] Intro to my I-D


Ben,

Wearing my i-DNS.net hat, there is a research work we been doing on
Onomastic Normalization Engine (ONE) for Chinese, Japanese and Korean
for registration purposes.

For your I-D on Chinese, maybe it is worthwhile for you to take a look
at ONE-C. You can find it at
http://playground.i-dns.net/one/onec_sum.htm

-James Seng

----- Original Message -----
From: "ben" <ben@cc-www.com>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
Sent: Monday, July 30, 2001 9:17 PM
Subject: Re: [idn] Intro to my I-D


> Hi Eric,
>
> As you are probably somewhat aware, I am indeed working very hard.
I
> want you to know that I am keeping all your questions /input in the
> back of my mind as I work and that can only help.  So I just want to
> thank you for all your efforts.
>
> The only question I want to address at this moment is something that
> caught my eye.  At the very end of your email below, you concluded
by
> saying- "Just what makes your proposal superior?".  Perhaps this is
a
> good time to reiterate what I said at the very beginning:
>
> My system recognizes the same equal importance for:
>
> 1.  Registrants given the freedom/choice to point Tradition CDN to
> tradition website and Simplifed CDN to simplified website.
> 2.  A need for Tradition CDN to Simplified CDN conversion.
>
> (However, I also believe that other CDN systems are absolutely fine
> exactly the way they are.)
>
> Thanks
> Ben Chan
>
>
>
> ----- Original Message -----
> From: "Eric Brunner-Williams in Portland Maine"
<brunner@nic-naa.net>
> To: "ben" <ben@cc-www.com>
> Cc: "xiang deng" <deng@cnnic.net.cn>; <lee@cnnic.net.cn>;
> <sun@cnnic.net.cn>; <brunner@nic-naa.net>; <brunner@nic-naa.net>;
> <harald@alvestrand.no>; <idn@ops.ietf.org>
> Sent: Sunday, July 29, 2001 11:17 AM
> Subject: Re: [idn] Intro to my I-D
>
>
> [I've added idn@ops.ietf.org back to the cc'd list.
>  Harald, please read and reconsider the "principle of least
surprise".
>  Thx.]
>
> Ben,
>
> What you've proposed is that for some collection of code-points, and
> for
> some equivalency rules (whether zone-scoped or global-scoped),
> allocation
> of one code-point in the collection results in pre-allocation
> (reservation)
> of all code-points in the collection.
>
> Additionally, you've proposed the registrant (recipient of the
> allocated
> code-point equivalency class) may then modify the equivalency rule
> which
> created the class, and assert distinct semantics for distinct
elements
> of
> the original (intact), now fragmented class.
>
> To help me understand your proposal, I'll consider ASCII strings and
> the
> Pan-Algonquin "OU" character (U+0222) and (U+0223). A locally
> constructed
> French character, not present in 17th century French. I know that
most
> of
> the North Americans and Europeans will find this choice strange, but
> more
> accessible, as "Indian French", than an ideogramatic example, and I
> know
> that my friends at CNNIC will speak to the Chinese language
specifics.
>
> Assertion: (zone scope)
>
> In the Algonquin-preferred zone(s), e.g., abenaki.dst.me.us,
> the following code-points and code-point sequences are
> equivalent:
> U+0070 "8" when in an alpha-string
> U+0222 "8" LATIN CAPITAL LETTER OU
> U+0223 "8" LATIN SMALL LETTER OU
> U+0117,U+0125 "OU"
> U+O117,U+0165 "Ou"
> U+0157,U+0165 "ou"
> U+0127 "W"
> U+0167 "w"
>
> Under your proposal, in my zone (abenaki.dst.me.us.), with ASCII
case
> folding
> (applied to the two Latin Extended-B code points), the registrant
for
> "ki8na.abenaki.dst.me.us" ("ki8na" means ourselves or nous-memes),
> would be
> allocated or reserved:
>
> ki{set of 4 code-point sequences}na.abenaki.dst.me.us
>
> The registrant could then be able to associate between 0 and eight
> unique
> ip addresses to these 4 allocated domain names in my zone, e.g.,
>
> ki(U+0070)na.abenaki.dst.me.us and 1.2.3.1
> ki(U+0222)na.abenaki.dst.me.us and 1.2.3.2
> ki(U+0223)na.abenaki.dst.me.us and 1.2.3.2
> ki(U+0117,U+0125)na.abenaki.dst.me.us and 1.2.3.3
> ki(U+O117,U+0165)na.abenaki.dst.me.us and 1.2.3.3
> ki(U+0157,U+0165)na.abenaki.dst.me.us and 1.2.3.3
> ki(U+0127)na.abenaki.dst.me.us and 1.2.3.4
> ki(U+0167)na.abenaki.dst.me.us and 1.2.3.4
>
> Without case folding there could be 8 distinct addresses rather than
> just 4.
>
> This would be very surprising to a modern literate North-Eastern
> Indian, and
> to scholars of the Contact Period and French and Indian literatures
of
> the
> 17th and 18th centuries. As the abenaki.dst.me.us zone manager, I
> don't think
> I would allow it. I would expect the equivalency rule (above) to be
> adopted
> by the {penobscot,passamquoddy,maliseet,micmac}.dst.me.us zone
> managers, and
> by other "Algonquin-aware" NSN.US zone managers. I would not expect
> these to
> be adopted by the dst.me.us or superior zone managers. I would
expect
> the same
> rule and scope to exist in the .ca zone and its dependent zones.
>
> My preference is that ki{set of 4 code-point
> sequences}na.abenaki.dst.me.us
> all map to a single internet address.
>
> In the Chinese language area, which includes North America as well
as
> China,
> your "registrant election" proposal appears to have the same
> surprising set
> of consequences as one registrant following one ideosyncratic
> convention for
> "ki8na" and another registrant, possibly the same one, following a
> different
> ideosyncratic convention for "ni8na" (we and you or nous et vous),
and
> this
> only gets worse as we consider strings such as k8sk8ranmsh8dans8
> (sift).
>
> Just what makes your proposal superior?
>
> Eric
>
> P.S. The advantage of [30], formerly "in" the IDN WG requirements
> draft, was
> that it made zone-specific semantics possible. Writing in modern
> Abenaki (or
> any "8" using French-originating modern script) using ASCII
> equivalency rules
> presents a problem for 0x70 to 0x127,0x167 mapping (simplest case).
>
>






From owner-idn@ops.ietf.org  Tue Jul 31 00:22:04 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA16346
	for <idn-archive@lists.ietf.org>; Tue, 31 Jul 2001 00:22:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RQlf-000BwN-00
	for idn-data@psg.com; Mon, 30 Jul 2001 21:04:27 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RQle-000BwH-00
	for idn@ops.ietf.org; Mon, 30 Jul 2001 21:04:26 -0700
Received: from soobok ([210.217.27.237] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id NAA03355;
	Tue, 31 Jul 2001 13:04:13 +0900
Message-ID: <013301c11976$af706aa0$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
References: <200107310056.f6V0uSN25816@nic-naa.net>
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE label version 0.2 
Date: Tue, 31 Jul 2001 13:10:07 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: <idn@ops.ietf.org>
Sent: Tuesday, July 31, 2001 9:56 AM
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE
label version 0.2


 > In the requirements draft, section 3 (Security Considerations) there is the
> hopeful statement that "a solution" not be "less secure" than the current
> DNS. Skipping over the minor problem that this may be an underspecification,
> hostname-based authentication is historic (and inachievable, hence dnssec),
> and invocation of identd is ... unusual in the normal course of app/resolver
> /transport/nameserver/transport/app sequences.
>
DNSSEC is low-level protocol, hidden from human eyes.
HTTPS and SMIME depends on end users' spontaneous association of
verified signature with the displayed i18n-identifier which could contain
misleading <cyrillic a>ol.com.


> The existance of "misleading identifiers" formed with an extended repetoire
> (independent of whether elements of the extended repetoire are transported
> in encapsulated, or native forms) appears to require that two or more "near"
> (Hamming distence) identifiers exist.
>
> A protocol that is capable of signaling the existence of name proximality
> is something other than the DNS. That protocol, whatever it is, can have a
> "Security Considerations" section that treats the subject of minimal Hamming
> distance (or any other form of similarity metric), hence some property that
> relates to authentication et al, and "misleading identifiers", hence of
> "look-alike" characters.

Yes, some parents who give birth to premature babies, should have employ
machine incubators for protecting their babies from infections by bacteria.

Then, let's make a IDN incubator protocol... :-))

>
> So, after all this (which I'm sorry to say took me much longer to write than
> for many to read), I think "safely encoding" is not "safe", and we should
> not do "encoding".
>
> Eric
>
I don't care for that... The half-baked I-D only took a few hours
from conception to finalization....

Thanks for your criticisms.

Soobok Lee





From owner-idn@ops.ietf.org  Tue Jul 31 02:59:12 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA08269
	for <idn-archive@lists.ietf.org>; Tue, 31 Jul 2001 02:59:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RT4j-000EbV-00
	for idn-data@psg.com; Mon, 30 Jul 2001 23:32:17 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RT4i-000EbP-00
	for idn@ops.ietf.org; Mon, 30 Jul 2001 23:32:16 -0700
Received: from amc by nicemice.net with local (Exim 3.31 #1 (Debian))
	id 15RT4i-0004u4-00; Mon, 30 Jul 2001 23:32:16 -0700
Date: Tue, 31 Jul 2001 06:32:16 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] How should labels be encoded?
Message-ID: <20010731063216.I16859@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200107300913.LAA02165@valinor.malmo.trab.se>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dan Oscarsson <Dan.Oscarsson@trab.se> wrote:

> Which labels are "host names"?
> The SOA record contains one that is an e-mail address.

Not a problem.  RFC 1035 tells how to represent an email address as
a domain name:  Prepend the local-part as a single label to the mail
domain.  IDNA affects the mail domain part, but not the local-part.  If
and when a working group forms to specify internationalized local-parts,
they will decide how to handle it here.  Until then, local-parts follow
the same rules as they do today, so there's nothing new to worry about
here.

> The SRV record has an owner name that represents a protocol.

Sorry, I'm not familiar with SRV, but perhaps the same argument would
apply.  Until some other working group specifies internationalized
owner-names (whatever those are), there's nothing new to be done here.

> Also not every thing which has an IP-address is a "host".

I'm not sure what you have in mind.  What's an example of something with
an IP address that's not a host?

> As DNS is more than "host names", how are labels that are not "host
> names" to be encoded when non-ASCII is used?
>
> IDNA does not answer this and it does not define which labels are
> "host names" and must be ACE+nameprep encoded.  It can happen that
> one application thinks a label in a DNS record is a host names, and
> another application uses it as something else (using some other
> encoding that ACE+nameprep).

IDNA says how to represent the labels of domain names.  It has nothing
to say about how to represent labels that are not labels of domain
names (that would be out-of-scope for IDN).  Not every sequence of
labels is a domain name; a domain name is the name of a domain.  When
amc.cs.berkeley.edu appears in an SOA record, amc.cs.berkeley.edu
is *not* a domain name, because it does not name a domain.  It is a
sequence of labels, the first of which is the local-part of an email
address.  The remaining labels form a domain name, and IDNA would apply
to them.

Maybe this is not clear enough in the IDNA draft, but I have no doubt
that this is the intention.

Maybe part of the confusion is that RFC 1035 uses the notation
<domain-name> to mean any sequence of labels, even when it's not really
a domain name.

AMC



From owner-idn@ops.ietf.org  Tue Jul 31 08:34:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA14014
	for <idn-archive@lists.ietf.org>; Tue, 31 Jul 2001 08:34:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RYL4-0004jL-00
	for idn-data@psg.com; Tue, 31 Jul 2001 05:09:30 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RYL2-0004jD-00
	for idn@ops.ietf.org; Tue, 31 Jul 2001 05:09:29 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f6VC7XN27590;
	Tue, 31 Jul 2001 08:07:33 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107311207.f6VC7XN27590@nic-naa.net>
To: "Soobok Lee" <lsb@postel.co.kr>
cc: idn@ops.ietf.org,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        brunner@nic-naa.net
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE label version 0.2 
In-Reply-To: Your message of "Tue, 31 Jul 2001 13:10:07 +0900."
             <013301c11976$af706aa0$ed1bd9d2@postel.co.kr> 
Date: Tue, 31 Jul 2001 08:07:33 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Soobok,

There is a difference between altering the assocation between a name and an
address, whether this operation is performed with global or local scope, and
creating an association beteen a name and another name.

The first is an integrity problem for the DNS, the second is a disambiguation
problem for something other than the DNS.

Eric



From owner-idn@ops.ietf.org  Tue Jul 31 08:56:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA14538
	for <idn-archive@lists.ietf.org>; Tue, 31 Jul 2001 08:56:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RYu2-0005ZP-00
	for idn-data@psg.com; Tue, 31 Jul 2001 05:45:38 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RYu1-0005ZJ-00
	for idn@ops.ietf.org; Tue, 31 Jul 2001 05:45:37 -0700
Received: from zetnet.co.uk (man-s109.dialup.zetnet.co.uk [194.247.41.236])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6VCjUx02644;
	Tue, 31 Jul 2001 13:45:30 +0100
Message-ID: <3B669523.55D6B42F@zetnet.co.uk>
Date: Tue, 31 Jul 2001 12:23:15 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: Mark Davis <mark@macchiato.com>, idn@ops.ietf.org
Subject: Re: [idn] ZWNJ
References: <Pine.LNX.4.33.0107291427360.15511-100000@gilas.bamdad.org> <003e01c11972$9d715160$0c680b41@c1340594a>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

Mark Davis wrote:
> After giving this some thought, I agree with Roozbeh that the ZWNJ should be
> removed from the prohibited list, and added to the Mapped Out list.

ZWNJ already is in the Mapped Out list
(draft-ietf-idn-nameprep-05.txt section 3.3).

A related question is whether names that are returned in reverse lookups have
to be nameprepped. If they don't, then they can include ZWNJ, uppercase,
national digit shapes, and similar presentation differences. If they do, then
such differences would be lost. (I'm talking here about queries by "new"
applications that can handle an arbitrary Unicode response to a reverse lookup.
For "old" applications that get an ACE response, it's desirable that there
should only be one form of the ACE name for a given equivalence class of
Unicode names.)

I don't think it's a big deal because the results of reverse lookups aren't
seen very often by users, but I'm coming round to the view that they shouldn't
need to be nameprepped (although they must still satisfy the validity rules,
obviously). This is still far less important than other considerations when
choosing a proposal, though.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO2Zw9TkCAxeYt5gVAQHRFAgApMt/R/KizU6HMgmIxlYqkl2fUwYRgqLI
d+YDdkwllt0uiZ+B6Mo0j7YkAvusxxHJtwKtXBiGw3Fe0d9QryDcTsdy1Zn8v3Ci
ZU8+4VvePDf9EtRozIyn/jepJIAASCRL3vshG0xBdYHQVsN+HLIvd/7D6l4b3sLk
cRSi/JzGwRMQz85Ve2B8ZZaVy1AyFDfalBBZdmLlGiT+fiIqJbOcKDu8pkHPAC7x
5EjIgyFrZJqOW6Kp7jNvaulu3+WayBxQAyvqqCbPw3e8N+5CK59djFbTJ6Ciqq4X
zN8ne5rY5HWSJ5opTqUM3BeHauPrb38soCztR9jyldVKpKL70uF0AQ==
=vnGL
-----END PGP SIGNATURE-----




From owner-idn@ops.ietf.org  Tue Jul 31 09:18:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA15292
	for <idn-archive@lists.ietf.org>; Tue, 31 Jul 2001 09:18:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RZHJ-0005zy-00
	for idn-data@psg.com; Tue, 31 Jul 2001 06:09:41 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RZHI-0005zr-00
	for idn@ops.ietf.org; Tue, 31 Jul 2001 06:09:40 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id WAA13498;
	Tue, 31 Jul 2001 22:09:14 +0900
Message-ID: <038d01c119c1$47d6da50$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
References: <200107311207.f6VC7XN27590@nic-naa.net>
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE label version 0.2 
Date: Tue, 31 Jul 2001 22:04:06 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric,

 If my favorite internet  phone company ever  issue two  internet phone numbers:
   1)   254-5628   ( all latin digits )
   2)   254-5628   (8  is Bengali '4'  )
 for two distinct entities,
 We can say the integrity of the number system is already severely flawed , even
before
 the first  innocent victim takes 2) for 1) and actually makes a dangerous phone
call.

 Uniqueness of identifiers depends partly on human mental distinction between
names.
 For the blind, even the 'a.com' and 'x.com' displayed on the screen , do not
provide
 any clues for mutual distinction.

 DNS contains the core internet identifier system which MUST provide  name
 uniqueness to audiences from diverse cultural and educational backgrounds ,
 while the global network of DNS protocol implementations adds universality .

Soobok

----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: "Soobok Lee" <lsb@postel.co.kr>
Cc: <idn@ops.ietf.org>; "Eric Brunner-Williams in Portland Maine"
<brunner@nic-naa.net>; <brunner@nic-naa.net>
Sent: Tuesday, July 31, 2001 9:07 PM
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE
label version 0.2


> Soobok,
>
> There is a difference between altering the assocation between a name and an
> address, whether this operation is performed with global or local scope, and
> creating an association beteen a name and another name.
>
> The first is an integrity problem for the DNS, the second is a disambiguation
> problem for something other than the DNS.
>
> Eric
>




From owner-idn@ops.ietf.org  Tue Jul 31 09:50:25 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA15891
	for <idn-archive@lists.ietf.org>; Tue, 31 Jul 2001 09:50:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RZmQ-0006f7-00
	for idn-data@psg.com; Tue, 31 Jul 2001 06:41:50 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RZmP-0006ez-00
	for idn@ops.ietf.org; Tue, 31 Jul 2001 06:41:50 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f6VDe4N27824;
	Tue, 31 Jul 2001 09:40:04 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107311340.f6VDe4N27824@nic-naa.net>
To: "Soobok Lee" <lsb@postel.co.kr>
cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE label version 0.2 
In-Reply-To: Your message of "Tue, 31 Jul 2001 22:04:06 +0900."
             <038d01c119c1$47d6da50$ec1bd9d2@temp> 
Date: Tue, 31 Jul 2001 09:40:04 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Soobok,

I'm glad you mentioned the access issue (visual impairment, aka "blind"), as
this is an area where the W3C has some interesting work.

Eric
(wearing a W3C hat)



From owner-idn@ops.ietf.org  Tue Jul 31 10:01:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA16249
	for <idn-archive@lists.ietf.org>; Tue, 31 Jul 2001 10:01:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RZzT-0006w6-00
	for idn-data@psg.com; Tue, 31 Jul 2001 06:55:19 -0700
Received: from femail36.sdc1.sfba.home.com ([24.254.60.26])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RZzS-0006w0-00
	for idn@ops.ietf.org; Tue, 31 Jul 2001 06:55:18 -0700
Received: from c1340594a ([65.11.104.12]) by femail36.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20010731135509.GPFW20441.femail36.sdc1.sfba.home.com@c1340594a>;
          Tue, 31 Jul 2001 06:55:09 -0700
Message-ID: <029801c119c8$a4447cf0$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
References: <200107311207.f6VC7XN27590@nic-naa.net> <038d01c119c1$47d6da50$ec1bd9d2@temp>
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE label version 0.2 
Date: Tue, 31 Jul 2001 06:56:47 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

This is a pipe-dream. See my messages of
Wednesday, July 18, 2001 09:45
Thursday, July 19, 2001 08:20

One might be fooled by how easy it is to come with with a simple list
between two scripts, such as Greek and Latin. But then the complications
arise: are rho and p to be considered confusable? Then there are extended
characters, like Latin small letter open e (ɛ) and epsilon (ε).  You rapidly
(I almost wrote "rabidly") slide off into gray areas even with just two
scripts. When it comes to comparing all the characters of the world, in many
combinations of fonts, the problem quickly becomes intractible.

We have had a lot of experience dealing with huge numbers of characters. It
is harder than it looks.

Mark
—————

πάντων μέτρον ἄνθρωπος — Πρωταγόρας
[http://www.macchiato.com]

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
Sent: Tuesday, July 31, 2001 06:04
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE
label version 0.2


> Eric,
>
>  If my favorite internet  phone company ever  issue two  internet phone
numbers:
>    1)   254-5628   ( all latin digits )
>    2)   254-5628   (8  is Bengali '4'  )
>  for two distinct entities,
>  We can say the integrity of the number system is already severely flawed
, even
> before
>  the first  innocent victim takes 2) for 1) and actually makes a dangerous
phone
> call.
>
>  Uniqueness of identifiers depends partly on human mental distinction
between
> names.
>  For the blind, even the 'a.com' and 'x.com' displayed on the screen , do
not
> provide
>  any clues for mutual distinction.
>
>  DNS contains the core internet identifier system which MUST provide  name
>  uniqueness to audiences from diverse cultural and educational backgrounds
,
>  while the global network of DNS protocol implementations adds
universality .
>
> Soobok
>
> ----- Original Message -----
> From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
> To: "Soobok Lee" <lsb@postel.co.kr>
> Cc: <idn@ops.ietf.org>; "Eric Brunner-Williams in Portland Maine"
> <brunner@nic-naa.net>; <brunner@nic-naa.net>
> Sent: Tuesday, July 31, 2001 9:07 PM
> Subject: Re: [idn] new I-D: Safely Encoding of likeness information into
ACE
> label version 0.2
>
>
> > Soobok,
> >
> > There is a difference between altering the assocation between a name and
an
> > address, whether this operation is performed with global or local scope,
and
> > creating an association beteen a name and another name.
> >
> > The first is an integrity problem for the DNS, the second is a
disambiguation
> > problem for something other than the DNS.
> >
> > Eric
> >
>
>
>




From owner-idn@ops.ietf.org  Tue Jul 31 10:35:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA18306
	for <idn-archive@lists.ietf.org>; Tue, 31 Jul 2001 10:35:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RaUi-0007cy-00
	for idn-data@psg.com; Tue, 31 Jul 2001 07:27:36 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RaUh-0007cr-00
	for idn@ops.ietf.org; Tue, 31 Jul 2001 07:27:35 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f6VEPkN28082;
	Tue, 31 Jul 2001 10:25:46 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200107311425.f6VEPkN28082@nic-naa.net>
To: "Mark Davis" <mark@macchiato.com>
cc: "Soobok Lee" <lsb@postel.co.kr>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE label version 0.2 
In-Reply-To: Your message of "Tue, 31 Jul 2001 06:56:47 PDT."
             <029801c119c8$a4447cf0$0c680b41@c1340594a> 
Date: Tue, 31 Jul 2001 10:25:46 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> This is a pipe-dream. See my messages of
> Wednesday, July 18, 2001 09:45
> Thursday, July 19, 2001 08:20

Those were good reading. I enjoyed the font example. I look forward to
stuffing 1x1 pixel gifs into <urk> HTMLized </urk> email, particularly
around what appear to be domain names.

...
> We have had a lot of experience dealing with huge numbers of characters.

The "We" here is the UTC, and other character standards body participants and
character rendering/processessing implementors. Not the run-of-the-mill IETF
contributors. Which is my first point:
	this is the work of bodies which create abstract character
	repertoires and coded character sets

> It is harder than it looks.

And it isn't DNS. We could be playing this game with:

	a) any system using all of ASCII, (What do unprintable characters
	   look like?)
	b) any system using all of 8859-*, (Ditto plus Latin/Greek)
	c) any system using just about any 8-, 15-, or 16-bit encoding,
	   whether of propriatary, national, or international origins,
and
	d) any system that "discovered" and "negociated" encodings, e.g., 
	   any of a), b), and c) above,
as well as
	e) Unicode.

Which is my second point:
	A protocol that is capable of signaling the existence of name
	proximality is something other than the DNS.

Eric

P.S. Someone, in the spirit of i18n-friendliness, changed the sanity check
     in Solaris 2.3 syslogd from isprint() to isascii(). I unpatched it. 
     I'll pay one beer to the first person who correctly identifies the
     real bug. Hint: Its a real security bug, has little to do with any
     specific Un*x, and is related to C0 Controls.



From owner-idn@ops.ietf.org  Tue Jul 31 10:45:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA18896
	for <idn-archive@lists.ietf.org>; Tue, 31 Jul 2001 10:45:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RadW-0007pi-00
	for idn-data@psg.com; Tue, 31 Jul 2001 07:36:42 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RadV-0007pb-00
	for idn@ops.ietf.org; Tue, 31 Jul 2001 07:36:42 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id XAA08309;
	Tue, 31 Jul 2001 23:36:22 +0900
Message-ID: <03c201c119cd$7499ef80$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Mark Davis" <mark@macchiato.com>
Cc: <idn@ops.ietf.org>
References: <200107311207.f6VC7XN27590@nic-naa.net> <038d01c119c1$47d6da50$ec1bd9d2@temp> <029801c119c8$a4447cf0$0c680b41@c1340594a>
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE label version 0.2 
Date: Tue, 31 Jul 2001 23:31:15 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Mark,

How about recommending a disambiguaing  full-unicode-wide reference font set
for IDN
with the best font size in IETF implementation guidelines for IDN-aware
OS/application vendors ?
The font set will help to reduce the list of pairs of ambiguous characters to be
compared,
and encourge all application vendors to adopt  it as the default IDN font.
For example, Greek 'rho' and latin 'p' may  look very different in that font,
while
Cyrillic 'a' (borrowed from latin 'a') and Latin 'a' may still look identical.
Then
we need normalize only 'a' s.

Do think this is feasible ?

 I found  http://www.unicode.org/charts already uses such good font. Is the font
for public domain?


Soobok



----- Original Message -----
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>; "Eric Brunner-Williams in Portland Maine"
<brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
Sent: Tuesday, July 31, 2001 10:56 PM
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE
label version 0.2


> This is a pipe-dream. See my messages of
> Wednesday, July 18, 2001 09:45
> Thursday, July 19, 2001 08:20
>
> One might be fooled by how easy it is to come with with a simple list
> between two scripts, such as Greek and Latin. But then the complications
> arise: are rho and p to be considered confusable? Then there are extended
> characters, like Latin small letter open e (ɛ) and epsilon (ε).  You rapidly
> (I almost wrote "rabidly") slide off into gray areas even with just two
> scripts. When it comes to comparing all the characters of the world, in many
> combinations of fonts, the problem quickly becomes intractible.
>
> We have had a lot of experience dealing with huge numbers of characters. It
> is harder than it looks.
>
> Mark
> —————
>
> πάντων μέτρον ἄνθρωπος — Πρωταγόρας
> [http://www.macchiato.com]
>




From owner-idn@ops.ietf.org  Tue Jul 31 11:37:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA21889
	for <idn-archive@lists.ietf.org>; Tue, 31 Jul 2001 11:37:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RbT0-0009Jv-00
	for idn-data@psg.com; Tue, 31 Jul 2001 08:29:54 -0700
Received: from femail34.sdc1.sfba.home.com ([24.254.60.24])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RbSz-0009JY-00
	for idn@ops.ietf.org; Tue, 31 Jul 2001 08:29:53 -0700
Received: from c1340594a ([65.11.104.12]) by femail34.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20010731152927.DCYF1299.femail34.sdc1.sfba.home.com@c1340594a>;
          Tue, 31 Jul 2001 08:29:27 -0700
Message-ID: <016701c119d5$d124c1a0$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>
Cc: <idn@ops.ietf.org>
References: <200107311207.f6VC7XN27590@nic-naa.net> <038d01c119c1$47d6da50$ec1bd9d2@temp> <029801c119c8$a4447cf0$0c680b41@c1340594a> <03c201c119cd$7499ef80$ec1bd9d2@temp>
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE label version 0.2 
Date: Tue, 31 Jul 2001 08:31:06 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Such a disambiguating font is certainly possible, and one of the possible
approaches to GUI-assists. What we could do is add text to IDNA to recommend
that domain names be displayed in such a way as to disambiguate confusibles.

Mark
—————

πάντων μέτρον ἄνθρωπος — Πρωταγόρας
[http://www.macchiato.com]

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Mark Davis" <mark@macchiato.com>
Cc: <idn@ops.ietf.org>
Sent: Tuesday, July 31, 2001 07:31
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE
label version 0.2


> Mark,
>
> How about recommending a disambiguaing  full-unicode-wide reference font
set
> for IDN
> with the best font size in IETF implementation guidelines for IDN-aware
> OS/application vendors ?
> The font set will help to reduce the list of pairs of ambiguous characters
to be
> compared,
> and encourge all application vendors to adopt  it as the default IDN font.
> For example, Greek 'rho' and latin 'p' may  look very different in that
font,
> while
> Cyrillic 'a' (borrowed from latin 'a') and Latin 'a' may still look
identical.
> Then
> we need normalize only 'a' s.
>
> Do think this is feasible ?
>
>  I found  http://www.unicode.org/charts already uses such good font. Is
the font
> for public domain?
>
>
> Soobok
>
>
>
> ----- Original Message -----
> From: "Mark Davis" <mark@macchiato.com>
> To: "Soobok Lee" <lsb@postel.co.kr>; "Eric Brunner-Williams in Portland
Maine"
> <brunner@nic-naa.net>
> Cc: <idn@ops.ietf.org>
> Sent: Tuesday, July 31, 2001 10:56 PM
> Subject: Re: [idn] new I-D: Safely Encoding of likeness information into
ACE
> label version 0.2
>
>
> > This is a pipe-dream. See my messages of
> > Wednesday, July 18, 2001 09:45
> > Thursday, July 19, 2001 08:20
> >
> > One might be fooled by how easy it is to come with with a simple list
> > between two scripts, such as Greek and Latin. But then the complications
> > arise: are rho and p to be considered confusable? Then there are
extended
> > characters, like Latin small letter open e (ɛ) and epsilon (ε).  You
rapidly
> > (I almost wrote "rabidly") slide off into gray areas even with just two
> > scripts. When it comes to comparing all the characters of the world, in
many
> > combinations of fonts, the problem quickly becomes intractible.
> >
> > We have had a lot of experience dealing with huge numbers of characters.
It
> > is harder than it looks.
> >
> > Mark
> > —————
> >
> > πάντων μέτρον ἄνθρωπος — Πρωταγόρας
> > [http://www.macchiato.com]
> >
>
>




From owner-idn@ops.ietf.org  Tue Jul 31 12:02:18 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA23174
	for <idn-archive@lists.ietf.org>; Tue, 31 Jul 2001 12:02:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RbqS-000A0g-00
	for idn-data@psg.com; Tue, 31 Jul 2001 08:54:08 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RbqR-000A0Y-00
	for idn@ops.ietf.org; Tue, 31 Jul 2001 08:54:07 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id AAA32647;
	Wed, 1 Aug 2001 00:53:54 +0900
Message-ID: <041501c119d8$491ad490$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Mark Davis" <mark@macchiato.com>
Cc: <idn@ops.ietf.org>
References: <200107311207.f6VC7XN27590@nic-naa.net> <038d01c119c1$47d6da50$ec1bd9d2@temp> <029801c119c8$a4447cf0$0c680b41@c1340594a> <03c201c119cd$7499ef80$ec1bd9d2@temp> <016701c119d5$d124c1a0$0c680b41@c1340594a>
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE label version 0.2 
Date: Wed, 1 Aug 2001 00:48:46 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

In summary, I suggest two principles:

  -  disambiguate as many look-alike letters as possible
       only by assistance of  reference fonts and GUIs

  -  normalize as few look-alike letters as possible :
      - only these cases for _identical_ glyph:
        - borrowed glyph
        - sibling glyphs from the same origin

Any constructuve modfication wanted...


Soobok Lee

----- Original Message -----
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>
Cc: <idn@ops.ietf.org>
Sent: Wednesday, August 01, 2001 12:31 AM
Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE label version 0.2


> Such a disambiguating font is certainly possible, and one of the possible
> approaches to GUI-assists. What we could do is add text to IDNA to recommend
> that domain names be displayed in such a way as to disambiguate confusibles.
>
> Mark
> —————
>
> πάντων μέτρον ἄνθρωπος — Πρωταγόρας
> [http://www.macchiato.com]
>
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: "Mark Davis" <mark@macchiato.com>
> Cc: <idn@ops.ietf.org>
> Sent: Tuesday, July 31, 2001 07:31
> Subject: Re: [idn] new I-D: Safely Encoding of likeness information into ACE
> label version 0.2
>
>
> > Mark,
> >
> > How about recommending a disambiguaing  full-unicode-wide reference font
> set
> > for IDN
> > with the best font size in IETF implementation guidelines for IDN-aware
> > OS/application vendors ?
> > The font set will help to reduce the list of pairs of ambiguous characters
> to be
> > compared,
> > and encourge all application vendors to adopt  it as the default IDN font.
> > For example, Greek 'rho' and latin 'p' may  look very different in that
> font,
> > while
> > Cyrillic 'a' (borrowed from latin 'a') and Latin 'a' may still look
> identical.
> > Then
> > we need normalize only 'a' s.
> >
> > Do think this is feasible ?
> >
> >  I found  http://www.unicode.org/charts already uses such good font. Is
> the font
> > for public domain?
> >
> >
> > Soobok
> >
> >
> >
> > ----- Original Message -----
> > From: "Mark Davis" <mark@macchiato.com>
> > To: "Soobok Lee" <lsb@postel.co.kr>; "Eric Brunner-Williams in Portland
> Maine"
> > <brunner@nic-naa.net>
> > Cc: <idn@ops.ietf.org>
> > Sent: Tuesday, July 31, 2001 10:56 PM
> > Subject: Re: [idn] new I-D: Safely Encoding of likeness information into
> ACE
> > label version 0.2
> >
> >
> > > This is a pipe-dream. See my messages of
> > > Wednesday, July 18, 2001 09:45
> > > Thursday, July 19, 2001 08:20
> > >
> > > One might be fooled by how easy it is to come with with a simple list
> > > between two scripts, such as Greek and Latin. But then the complications
> > > arise: are rho and p to be considered confusable? Then there are
> extended
> > > characters, like Latin small letter open e (ɛ) and epsilon (ε).  You
> rapidly
> > > (I almost wrote "rabidly") slide off into gray areas even with just two
> > > scripts. When it comes to comparing all the characters of the world, in
> many
> > > combinations of fonts, the problem quickly becomes intractible.
> > >
> > > We have had a lot of experience dealing with huge numbers of characters.
> It
> > > is harder than it looks.
> > >
> > > Mark
> > > —————
> > >
> > > πάντων μέτρον ἄνθρωπος — Πρωταγόρας
> > > [http://www.macchiato.com]
> > >
> >
> >
>
>




From owner-idn@ops.ietf.org  Tue Jul 31 17:10:28 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA22186
	for <idn-archive@lists.ietf.org>; Tue, 31 Jul 2001 17:10:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RgZO-000HIB-00
	for idn-data@psg.com; Tue, 31 Jul 2001 13:56:50 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RgZN-000HI5-00
	for idn@ops.ietf.org; Tue, 31 Jul 2001 13:56:49 -0700
Received: from zetnet.co.uk (man-s048.dialup.zetnet.co.uk [194.247.41.175])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f6VKsux15078;
	Tue, 31 Jul 2001 21:54:57 +0100
Message-ID: <3B6707BD.2D813760@zetnet.co.uk>
Date: Tue, 31 Jul 2001 20:32:13 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: Dan Oscarsson <Dan.Oscarsson@trab.se>, idn@ops.ietf.org
Subject: Re: [idn] How should labels be encoded?
References: <200107300913.LAA02165@valinor.malmo.trab.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

Dan Oscarsson wrote:
> So now my question is: how should the labels in the DNS protocol
> be encoded?

RFC 2181 forces the answer to that: they are 8-bit clean binary.
They can also be interpreted as text at the edges of DNS, i.e. when
preparing a name to be resolved, and when comparing against a zone
file. (What encoding is used when interpreting them as non-ASCII text
is obviously not decided yet.)

> Which labels are "host names"?

That is defined by the application protocol.

> The SOA record contains one that is an e-mail address.

Since the local part of an email address is internationalizable text,
and is subject to exactly the same compatibility and normalization
considerations as domain names, it should use the same encoding as
domain names, IMHO.

> The SRV record has an owner name that represents a protocol.

The encoding of the protocol name is defined by RFC 2782. Since it is
ASCII ('_' followed by an LDH identifier), it is not affected by ACE
encoding or nameprep. So even though the protocol name is not
internationalizable, it won't matter if something applies ACE and/or
nameprep to it.

This does make clear, however, that it is not correct for a general
purpose resolver interface to reject non-LDH ASCII characters; instead,
it should pass through such characters (if no non-LDH characters are
used in that domain, the query will simply fail).

> Also not every thing which has an IP-address is a "host".

That doesn't matter. Any domain name can map to zero or more IP
addresses. Normally there should be a machine at each address that
satisfies the requirements on hosts (RFCs 1122 & 1123), but if there
isn't, that is no concern of DNS.

> As DNS is more than "host names", how are labels that are not
> "host names" to be encoded when non-ASCII is used?

If the protocol that uses DNS defines the label to be binary, or
some type of identifier that does not need to be internationalized,
its interpretation should stay exactly as it is. If it defines the
label to be internationalizable text, the obvious design decision
would be to use the same encoding as for host names.

> IDNA does not answer this and it does not define which labels
> are "host names" and must be ACE+nameprep encoded.
> It can happen that one application thinks a label in a
> DNS record is a host names, and another application uses it
> as something else (using some other encoding that ACE+nameprep).

I don't see any situation where this would happen in practice,
although I may be missing something. Are there any protocols that
currently allow text DNS labels in some 8-bit encoding other than
ASCII, or labels that are likely to be confused with an ACE encoding?
(SRV and SOA don't pose any problems in this respect. Is there an
exhaustive list of DNS RRs and query types anywhere?)

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO2cHsjkCAxeYt5gVAQHZsQgAj94X3vDuUHn/fP3mjU1Sm89hptMaJ/1d
/6Adll/i3s/d7z1gFDH81To+ZiGCFUnkGkDWy6ZfERmDpcnPYcGzXHRF8ZlCI3Jh
0pvilWTRmdClOIxBtuNAX10zVt/WgV9yHz8Hik83K8qZ0yTGREwJ+mKI7VKE0qDn
vvuClgYYsdeBVu6uGIRKvIVKcNjwb3GjAo2d057gdzIBlVIq01QNWAtBiWBgp3f1
OS9WuugEBrBBXOKkVWHhPx7lJrqu5Q8b6TZM2iMZ68Lkd1wsbWk3qgTzPWzJ/zGx
ta1NAKXdlHqejlJQ95qsFQb+Ttd3A+kedNu92kyT0V5ZVnBDAfrrPA==
=kMKH
-----END PGP SIGNATURE-----




From owner-idn@ops.ietf.org  Tue Jul 31 17:27:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA23393
	for <idn-archive@lists.ietf.org>; Tue, 31 Jul 2001 17:27:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Rgwb-000HmY-00
	for idn-data@psg.com; Tue, 31 Jul 2001 14:20:49 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Rgwa-000HmS-00
	for idn@ops.ietf.org; Tue, 31 Jul 2001 14:20:48 -0700
Received: from amc by nicemice.net with local (Exim 3.31 #1 (Debian))
	id 15Rgwa-0005N1-00; Tue, 31 Jul 2001 14:20:48 -0700
Date: Tue, 31 Jul 2001 21:20:48 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] ZWNJ
Message-ID: <20010731212048.C20351@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B669523.55D6B42F@zetnet.co.uk>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

David Hopwood <david.hopwood@zetnet.co.uk> wrote:

> A related question is whether names that are returned in reverse
> lookups have to be nameprepped.

In my opinion, nameprep is for defining the equivalence between names,
and therefore it needs to be invoked only when comparing names.  I
see no advantage to perform nameprep before sending a name, and the
disadvantage is that it loses information that might be helpful to
humans.

There are two exceptions to that rule:  First, ACEs must always be
nameprepped, because the whole point of ACE is to be compatible with
old applications, which don't know about nameprep.  Second, non-ACE
DNS queries (not responses) should be nameprepped on the client as a
performance optimization, because that would always be the first thing
the server would do anyway (there is no human user on the server side to
lament the loss of information, and the client can retain the original
form).  If there are other protocols in which a server would always
apply nameprep to all incoming names and discard the original form, the
same argument could apply to them.  But in general, for non-ACE names, I
think nameprepped names should not be shipped around; nameprep should be
performed as part of the comparison operation.

AMC

P.S. Actually, the easiest way to compare two labels is to convert both
to ASCII (using nameprep, and ACE if necessary) and then compare using
the customary case-insensitive ASCII comparison.  This not only catches
the equivalence between two old-style labels, two ACE labels, and two
non-ASCII labels, but also handles the case where one label is non-ASCII
and the other is the corresponding ACE form, and the case where one
label is simple non-ACE ASCII and the other is a non-ASCII equivalent
form (using full-width Latin letters, for example).



From owner-idn@ops.ietf.org  Tue Jul 31 18:01:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA25760
	for <idn-archive@lists.ietf.org>; Tue, 31 Jul 2001 18:01:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RhKv-000IIg-00
	for idn-data@psg.com; Tue, 31 Jul 2001 14:45:57 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RhKu-000IIa-00
	for idn@ops.ietf.org; Tue, 31 Jul 2001 14:45:56 -0700
Received: from amc by nicemice.net with local (Exim 3.31 #1 (Debian))
	id 15RhKu-0005Pl-00; Tue, 31 Jul 2001 14:45:56 -0700
Date: Tue, 31 Jul 2001 21:45:56 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] How should labels be encoded?
Message-ID: <20010731214555.E20351@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B6707BD.2D813760@zetnet.co.uk>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

David Hopwood <david.hopwood@zetnet.co.uk> wrote:

> > The SOA record contains one that is an e-mail address.
>
> Since the local part of an email address is internationalizable text,
> and is subject to exactly the same compatibility and normalization
> considerations as domain names, it should use the same encoding as
> domain names, IMHO.

This working group is not the place to decide how to internationalize
email address local-parts.  Local-parts do not have exactly the same
compatibility and normalization considerations as domain names: they
may contain non-LDH ASCII characters, they may be case-sensitive, and
they may be structured using separators other than "." (for example,
owner-FOO and FOO-request and FOO+TAG are common constructions that have
particular relationships to FOO).  I once tried to start discussing this
issue and was told (correctly) that it's off-topic for this working
group.

> This does make clear, however, that it is not correct for a general
> purpose resolver interface to reject non-LDH ASCII characters;
> instead, it should pass through such characters (if no non-LDH
> characters are used in that domain, the query will simply fail).

You seem to be confusing queries and responses, or domain names and
resource records.  Currently, all domain names (which are the things
that appear in queries) are advised to use the preferred name syntax
(LDH characters in labels).  The resource records (the things that
appear in responses, like SOA and SRV data) already contain non-LDH
characters, and of course they are not rejected for that.  Some resource
records contain domain names (like CNAME and PTR) but some contain
other things.  The mailbox field of the SOA record, even though it is
formatted as a sequence of labels, is not a domain name and is not
expected to conform to the preferred name syntax (although after you
chop off the first label, the result is a domain name and is expected to
conform).  I gather than the same is true of the SRV record.

AMC



From owner-idn@ops.ietf.org  Tue Jul 31 22:22:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA16332
	for <idn-archive@lists.ietf.org>; Tue, 31 Jul 2001 22:22:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15RlQm-000NYx-00
	for idn-data@psg.com; Tue, 31 Jul 2001 19:08:16 -0700
Received: from sraigw.sra.co.jp ([202.32.10.2])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15RlQl-000NYr-00
	for idn@ops.ietf.org; Tue, 31 Jul 2001 19:08:15 -0700
Received: from sranhe.sra.co.jp (sranhe [133.137.44.3])
	by sraigw.sra.co.jp (8.8.7/3.7W-sraigw) with ESMTP id LAA02714;
	Wed, 1 Aug 2001 11:08:12 +0900 (JST)
Received: from srapc1567.sra.co.jp (srapc1567 [133.137.44.38])
	by sranhe.sra.co.jp (8.8.7/3.6Wbeta7-srambox) with ESMTP id LAA11805;
	Wed, 1 Aug 2001 11:08:11 +0900 (JST)
Received: from localhost (localhost [127.0.0.1]) by srapc1567.sra.co.jp (8.11.1/3.4W-sra) with ESMTP id f7128B986840; Wed, 1 Aug 2001 11:08:11 +0900 (JST)
To: idn@ops.ietf.org
Cc: yone@nic.ad.jp, ishisone@sra.co.jp
Subject: [idn] ACE Candidates: Dropping MACE in favor of AMC-ACE-Z
From: Makoto Ishisone <ishisone@sra.co.jp>
X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010801110811R.ishisone@sra.co.jp>
Date: Wed, 01 Aug 2001 11:08:11 +0900
X-Dispatcher: imput version 20000228(IM140)
Lines: 37
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

We, the authors of MACE, which is one of the proposed ACEs, would like
to annouce that we now support AMCE-ACE-Z over MACE as the ACE
standard.

Currently there are 3 ACE candidates in Pool W -- DUDE, AMC-ACE-Z and
MACE.

DUDE has the simplest algorithm, but we feel that it is not very
efficient, especially for CJK scripts.  Typically it allows 15 Han
characters (in the worst case 14) as the report from the ACE design
team says (draft-ietf-idn-ace-report-00), but many people seem to be
feeling 15 is insufficient.  Also this figure is worse than 17 that is
RACE's worst case in CJK.  We think choosing ACE that is not only
simpler but also more efficient than RACE is important.

That's why we proposed MACE.  We focused on improving the worst case
behavior especially for CJK.  It is designed to allow at least 19 Han
(or Hangul) characters, but it is slightly worse compression for
Western scripts. Also it has additional complexity by the introduction
of "encoding modes."

AMC-ACE-Z uses a brand new compression algorithm, and has clearly the
better compression for Western scripts compared to DUDE/MACE.  And we
found it also has the efficiency comparable to MACE for CJK (at least
Japanese) names.  We have done an evaluation using 50,000 registered
Japanese domain names, and it showed that AMC-ACE-Z does better
compression on average than MACE, and slightly worse compression for
worst case (but by only one or two octets, which is still better than
RACE).  Also AMC-ACE-Z's algorithm is simpler than MACE.

So, considering all the factors, we decided to support AMC-ACE-Z
rather than revising/enhancing MACE.

						Makoto Ishisone
						ishisone@sra.co.jp
						Yoshiro Yoneya
						yone@nic.ad.jp



