From owner-idn@ops.ietf.org  Mon Oct  1 15:56:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29030
	for <idn-archive@lists.ietf.org>; Mon, 1 Oct 2001 15:56:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15o8mr-000LLn-00
	for idn-data@psg.com; Mon, 01 Oct 2001 12:31:33 -0700
Received: from r1.boston.juno.com ([64.136.24.45])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15o8mq-000LLg-00
	for idn@ops.ietf.org; Mon, 01 Oct 2001 12:31:32 -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 OAAAA11252
 for <idn@ops.ietf.org>; Mon, 1 Oct 2001 14:02:29 -0400 (EDT)
From: liana.ydisg@juno.com
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VV8qlhzNm+4MrEY31s8qXNkA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GGPDWLBZ; Mon, 01 Oct 2001 14:01:40 EDT
To: idn@ops.ietf.org
Date: Mon, 1 Oct 2001 11:21:21 -0700
Subject: [idn]Antibody warning
Message-ID: <20011001.112124.-812159.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
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello,
  Are you able to read my drafts? Is it worth 
consideration by the WG?

 I think there is tumor in the WG process.  I have
been receiving over 130 autoreplies for my
submission draft-liana-idn-stone-00 and 
draft-ietf-idn-step-01 in the last a few days,  
and my drafts have not appeared in the draft 
directory.  I can not refer to them.   What is going
wrong?

Liana



From owner-idn@ops.ietf.org  Mon Oct  1 21:29:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06681
	for <idn-archive@lists.ietf.org>; Mon, 1 Oct 2001 21:29:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oE63-0003Be-00
	for idn-data@psg.com; Mon, 01 Oct 2001 18:11:43 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15oE62-0003BY-00
	for idn@ops.ietf.org; Mon, 01 Oct 2001 18:11:43 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id C8DC2FFC0E; Tue,  2 Oct 2001 09:12:21 +0800 (SGT)
Message-ID: <002001c14adf$2fd1de10$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: <liana.ydisg@juno.com>, <idn@ops.ietf.org>
References: <20011001.112124.-812159.0.liana.ydisg@juno.com>
Subject: Re: [idn]Antibody warning
Date: Tue, 2 Oct 2001 09:11:38 +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

Liana,

if you are submitting your drafts, the way to do so is to send it to
internet-drafts@ietf.org. They will process it in time. Sometimes it is
faster, sometimes slower but in these times, please be more
understanding to them.

btw, sending your mail using a template similar to I-D editors to
announce the release of your draft is a bad idea. I was a bit confused
until I saw the sender address. Please try not to do it again. The I-D
will announce it for you when they publish it.

-James Seng

----- Original Message -----
From: <liana.ydisg@juno.com>
To: <idn@ops.ietf.org>
Sent: Tuesday, October 02, 2001 2:21 AM
Subject: [idn]Antibody warning


> Hello,
>   Are you able to read my drafts? Is it worth
> consideration by the WG?
>
>  I think there is tumor in the WG process.  I have
> been receiving over 130 autoreplies for my
> submission draft-liana-idn-stone-00 and
> draft-ietf-idn-step-01 in the last a few days,
> and my drafts have not appeared in the draft
> directory.  I can not refer to them.   What is going
> wrong?
>
> Liana
>




From owner-idn@ops.ietf.org  Mon Oct  1 22:19:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08465
	for <idn-archive@lists.ietf.org>; Mon, 1 Oct 2001 22:19:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oEzw-0004TM-00
	for idn-data@psg.com; Mon, 01 Oct 2001 19:09:28 -0700
Date: Fri, 28 Sep 2001 16:18:12 -0400
To: idn@ops.ietf.org
From: bill@mail.nic.nu (J. William Semich)
Subject: [idn] Is The IDN WGroup Still Active? Fwd: [IDNList] Registrar
Advisory: AMC-ACE- Z in the zones
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15oEzw-0004TM-00@psg.com>

Haven't heard anything on the IDN list since Sept 1, so I'm wondering if
maybe the list has gone dark?

FYI, this just in from Verisign

-- Bill Semich


>X-Authentication-Warning: imx3.pvt.lks.verisign-grs.net: majordomo set
>sender to owner-idntestbed@verisign-grs.com using -f
>Reply-To: <info@verisign-grs.com>
>From: "VeriSign Global Registry Services" <info@verisign-grs.com>
>To: <idntestbed@verisign-grs.com>
>Subject: [IDNList] Registrar Advisory: AMC-ACE- Z in the zones
>Date: Fri, 28 Sep 2001 14:10:00 -0400
>X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
>Importance: Normal
>Sender: owner-idntestbed@verisign-grs.com
>X-MIME-Autoconverted: from 8bit to quoted-printable by verisign-grs.com
id
>OAA23352
>
>To All IDN-Certified Registrars:
>
>VeriSign Global Registry Services (GRS) intends to move forward in the
>Internationalized Domain Name Testbed by placing the IDNs directly into
the
>.com, .net and .org zones.  The zones will be populated with the
AMC-ACE-Z
>v0.3.1 representation of the IDNs.  Registrars do not need to modify
any of
>their current registration processes to support this change.  All
existing
>IDNs originally registered with RACE will be valid under the AMC-ACE-Z
>encoding.

<snip>







From owner-idn@ops.ietf.org  Mon Oct  1 22:20:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08494
	for <idn-archive@lists.ietf.org>; Mon, 1 Oct 2001 22:20:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oEzH-0004SB-00
	for idn-data@psg.com; Mon, 01 Oct 2001 19:08:47 -0700
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: [idn] Announcing the clean-i18n mailing list
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15oEzH-0004SB-00@psg.com>
Date: Mon, 01 Oct 2001 19:08:47 -0700

I've set up a mailing list where we can discuss progress on UTF-8 IDNs.
To subscribe, send a message to clean-i18n-subscribe@list.cr.yp.to.

If you love the beauty of Quoted-Printable, if you think that ACE IDNs
are the long-term IDN solution, and if you think that it's acceptable to
deploy a 7-bit Internet MTA, then this is not the mailing list for you.

The rest of us agree that everyone will eventually move to UTF-8, even
if something else happens in the short term. Programs that have trouble
with UTF-8 need to be fixed. The clean-i18n list is a good place to
point out what works and what doesn't.

The overall topic for the mailing list is ``Eliminating the horrors of
multiple character sets and encodings.'' This is not an IETF list;
contributors are encouraged to focus on real problems and solutions.

---Dan

----- Original Message -----
From: <owner-idn@ops.ietf.org>
To: <jseng@pobox.org.sg>
Sent: Saturday, September 29, 2001 7:38 AM
Subject: BOUNCE idn@ops.ietf.org: Admin request of type /\bsubscribe\b/i
at line 2


> >From djb-dsn-1001720215.26644@cr.yp.to Fri Sep 28 16:38:41 2001
> Received: from muncher.math.uic.edu ([131.193.178.181])
> by psg.com with smtp (Exim 3.33 #1)
> id 15n7DN-000Kx7-00
> for idn@ops.ietf.org; Fri, 28 Sep 2001 16:38:41 -0700
> Received: (qmail 31793 invoked by uid 1001); 28 Sep 2001
23:36:55 -0000
> Date: 28 Sep 2001 23:36:55 -0000
> Message-ID: <20010928233655.26644.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: Announcing the clean-i18n mailing list
> Mime-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> I've set up a mailing list where we can discuss progress on UTF-8
IDNs.
> To subscribe, send a message to clean-i18n-subscribe@list.cr.yp.to.
>
> If you love the beauty of Quoted-Printable, if you think that ACE IDNs
> are the long-term IDN solution, and if you think that it's acceptable
to
> deploy a 7-bit Internet MTA, then this is not the mailing list for
you.
>
> The rest of us agree that everyone will eventually move to UTF-8, even
> if something else happens in the short term. Programs that have
trouble
> with UTF-8 need to be fixed. The clean-i18n list is a good place to
> point out what works and what doesn't.
>
> The overall topic for the mailing list is ``Eliminating the horrors of
> multiple character sets and encodings.'' This is not an IETF list;
> contributors are encouraged to focus on real problems and solutions.
>
> ---Dan
>




From owner-idn@ops.ietf.org  Mon Oct  1 22:21:23 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08517
	for <idn-archive@lists.ietf.org>; Mon, 1 Oct 2001 22:21:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oF0M-0004Ta-00
	for idn-data@psg.com; Mon, 01 Oct 2001 19:09:54 -0700
From: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>
To: idn@ops.ietf.org
Subject: Re: [idn] Prefix for testing AMC-Z implementations
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15oF0M-0004Ta-00@psg.com>
Date: Mon, 01 Oct 2001 19:09:54 -0700

Paul Hoffman / IMC <phoffman@imc.org> wrote:

> My ham-fisted, not-at-all-elegant Perl code is available for all to
> see; it gets the exact results as Adam's C code from the document.

Nitpick:  Whenever the C code from the document succeeds, the Perl
code also succeeds and yields the same result.  Whenever the C code
fails because of overflow, the Perl code might succeed or might return
garbage, because it does not check for overflow.

I think the same overflow detection logic used in the C code can be used
in the Perl code, the only question is what value to assign to maxint.
0x7FFFFFFF is probably safe for all Perl implementations, but it would
be nice to do a sanity check.  Here's one idea:

Check whether 0x7FFFFFFF % 46349 == 41779 (it should).  If it doesn't,
then we don't have 31 bits of precision.  Even if the test succeeds,
that doesn't prove that we have 31 bits of precision, but my intuition
is that it provides reasonable confidence.  (46349 is the smallest prime
greater than sqrt(0x7FFFFFFF).)

AMC





From owner-idn@ops.ietf.org  Mon Oct  1 22:30:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08710
	for <idn-archive@lists.ietf.org>; Mon, 1 Oct 2001 22:30:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oFDX-0004tb-00
	for idn-data@psg.com; Mon, 01 Oct 2001 19:23:31 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15oFDW-0004tN-00
	for idn@ops.ietf.org; Mon, 01 Oct 2001 19:23:30 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f922N5k21627;
	Mon, 1 Oct 2001 22:23:05 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110020223.f922N5k21627@nic-naa.net>
X-Mailer: exmh version 1.6.9 8/22/96
To: "D. J. Bernstein" <djb@cr.yp.to>
cc: idn@ops.ietf.org
Subject: Re: [idn] Announcing the clean-i18n mailing list 
In-Reply-To: Your message of "Mon, 01 Oct 2001 19:08:47 PDT."
             <E15oEzH-0004SB-00@psg.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 01 Oct 2001 22:23:05 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Thanks for setting up a list.




From owner-idn@ops.ietf.org  Mon Oct  1 23:21:02 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10589
	for <idn-archive@lists.ietf.org>; Mon, 1 Oct 2001 23:21:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oFuS-0005zP-00
	for idn-data@psg.com; Mon, 01 Oct 2001 20:07:52 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15oFuR-0005zI-00
	for idn@ops.ietf.org; Mon, 01 Oct 2001 20:07:51 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id XAA17946;
        Mon, 1 Oct 2001 23:07:48 -0400 (EDT)
Message-Id: <200110020307.XAA17946@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] Announcing the clean-i18n mailing list 
In-reply-to: Your message of "Mon, 01 Oct 2001 19:08:47 PDT."
             <E15oEzH-0004SB-00@psg.com> 
Date: Mon, 01 Oct 2001 23:07:48 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> contributors are encouraged to focus on real problems and solutions.

and to ignore real depolyment issues.



From owner-idn@ops.ietf.org  Tue Oct  2 01:02:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12992
	for <idn-archive@lists.ietf.org>; Tue, 2 Oct 2001 01:02:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oHYW-0008Ue-00
	for idn-data@psg.com; Mon, 01 Oct 2001 21:53:20 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.33 #1)
	id 15oHYV-0008UX-00
	for idn@ops.ietf.org; Mon, 01 Oct 2001 21:53:19 -0700
Received: (qmail 29752 invoked by uid 1001); 2 Oct 2001 04:53:31 -0000
Date: 2 Oct 2001 04:53:31 -0000
Message-ID: <20011002045331.24794.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] Announcing the clean-i18n mailing list
References: <E15oEzH-0004SB-00@psg.com> <200110020307.XAA17946@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:
> and to ignore real depolyment issues.

You pushed Quoted-Printable without ever rationally evaluating the
deployment costs. You are now pushing ACE IDNs in exactly the same way.
So it's funny to see you talking about deployment.

Anyway, for the record: Web server version surveys, MTA surveys, and
other facts about deployment of cleanly internationalized software are
within the scope of the clean-i18n mailing list.

The objective is to eliminate the horrors of multiple character sets and
encodings. Deploying UTF-8 support is obviously a big part of reaching
this objective.

---Dan



From owner-idn@ops.ietf.org  Tue Oct  2 14:02:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23679
	for <idn-archive@lists.ietf.org>; Tue, 2 Oct 2001 14:02:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oTgn-0000xF-00
	for idn-data@psg.com; Tue, 02 Oct 2001 10:50:41 -0700
Received: from mail5.speakeasy.net ([216.254.0.205])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15oTgm-0000x9-00
	for idn@ops.ietf.org; Tue, 02 Oct 2001 10:50:40 -0700
Received: (qmail 84775 invoked from network); 2 Oct 2001 17:50:39 -0000
Received: from unknown (HELO Magnus) ([64.81.85.4]) (envelope-sender <tim@xtns.net>)
          by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <idn.amc+0@nicemice.net.RemoveThisWord>; 2 Oct 2001 17:50:39 -0000
Message-ID: <00cc01c14b6a$b23c5700$0200a8c0@Magnus>
From: "Tim Langdell" <tim@xtns.net>
To: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>,
        <idn@ops.ietf.org>
References: <E15oF0M-0004Ta-00@psg.com>
Subject: [idn] Renaming "AMC-Z"
Date: Tue, 2 Oct 2001 10:50:13 -0700
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.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

If I recall correctly, it was mentioned that if adopted, AMC-ACE-Z would get
a new formal 'release' name prior to be unleashed on the public. With that
in mind, might I start the ball rolling on suggestions?

To kick things off I suggest "CHACE" (logic => "CHosenACE", ie the one we
ended up choosing, for want of a better reason ...)

Tim





From owner-idn@ops.ietf.org  Tue Oct  2 16:31:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28523
	for <idn-archive@lists.ietf.org>; Tue, 2 Oct 2001 16:31:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oVxo-0004lS-00
	for idn-data@psg.com; Tue, 02 Oct 2001 13:16:24 -0700
Received: from femail13.sdc1.sfba.home.com ([24.0.95.140])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15oVxn-0004lM-00
	for idn@ops.ietf.org; Tue, 02 Oct 2001 13:16:23 -0700
Received: from anteroom ([65.8.26.205]) by femail13.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20011002201622.JHKD18139.femail13.sdc1.sfba.home.com@anteroom>;
          Tue, 2 Oct 2001 13:16:22 -0700
Message-ID: <006c01c14b7f$15febb70$1000a8c0@anteroom>
From: "Bright Fulton" <bright@alldomains.com>
To: "Tim Langdell" <tim@xtns.net>,
        "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>,
        <idn@ops.ietf.org>
References: <E15oF0M-0004Ta-00@psg.com> <00cc01c14b6a$b23c5700$0200a8c0@Magnus>
Subject: Re: [idn] Renaming "AMC-Z"
Date: Tue, 2 Oct 2001 16:16:09 -0400
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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I kind of like AMC-ACE-Z, or maybe just dropping the -Z.

But if we have to come up with something cute, I'd suggest SUITCACE for
SUITably Convenient ACE.

Bright Fulton


> If I recall correctly, it was mentioned that if adopted, AMC-ACE-Z would
get
> a new formal 'release' name prior to be unleashed on the public. With
that
> in mind, might I start the ball rolling on suggestions?
>
> To kick things off I suggest "CHACE" (logic => "CHosenACE", ie the one
we
> ended up choosing, for want of a better reason ...)
>
> Tim





From owner-idn@ops.ietf.org  Wed Oct  3 01:13:18 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA14612
	for <idn-archive@lists.ietf.org>; Wed, 3 Oct 2001 01:13:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oe2L-000IBG-00
	for idn-data@psg.com; Tue, 02 Oct 2001 21:53:37 -0700
Date: Tue, 2 Oct 2001 23:19:42 +0000
From: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>
To: idn@ops.ietf.org
Subject: Re: [idn] Renaming "AMC-Z"
Message-ID: <20011002231942.E27342@nicemice.net>
Reply-To: IETF idn working group <idn@ops.ietf.org>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I sent some suggestions yesterday, but I'm not sure they ever made it to
the list.  Here they are again, just in case:

Bootstring-646 (because it's the Bootstring algorithm with parameters
chosen to favor transforming ISO-10646 (Unicode) ISO-646 (ASCII))

Minicode (because it's a representation of Unicode that uses as smaller
set of code points)

Unimplode (same idea, but intsead of changing the U to Mi, change the c
to mpl)

AMC





From owner-idn@ops.ietf.org  Wed Oct  3 01:13:38 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA14651
	for <idn-archive@lists.ietf.org>; Wed, 3 Oct 2001 01:13:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oe5T-000IGg-00
	for idn-data@psg.com; Tue, 02 Oct 2001 21:56:51 -0700
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <narten@raleigh.ibm.com>, <Erik.Nordmark@eng.sun.com>
Cc: <idn@ops.ietf.org>, <Marc.Blanchet@viagenie.qc.ca>
Subject: [idn] Request to advance "Requirements of Internationalized Domain
Message-Id: <E15oe5T-000IGg-00@psg.com>
Date: Tue, 02 Oct 2001 21:56:51 -0700

Names"
Date: Wed, 3 Oct 2001 09:04:35 +0800
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Erik & Thomas,

The chairs of the International Domain Names Working Group, on the
behalf of the working group, request that the following document be
published as a Informational RFC:

Title : Requirements of Internationalized Domain Names
Author(s) : Z. Wenzel, J. Seng
Filena    me : draft-ietf-idn-requirements-08.txt
Pages : 8
Date : 22-Jun-01

A working group last call was conducted on 13th Feb 2001. "-08" on 22th
Jun 2001 was produced in responsed to the comments made and subsequence
discussion. The wg agreed in the London IETF meeting to advance this
document.

James Seng / Marc Blanchet
IDN Working Group Co-chairs








From owner-idn@ops.ietf.org  Wed Oct  3 11:55:56 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19331
	for <idn-archive@lists.ietf.org>; Wed, 3 Oct 2001 11:55:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ooEX-0009bf-00
	for idn-data@psg.com; Wed, 03 Oct 2001 08:46:53 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ooEW-0009bZ-00
	for idn@ops.ietf.org; Wed, 03 Oct 2001 08:46:52 -0700
Received: from [165.227.249.20] (165-227-249-20.client.dsl.net [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f93FkmD07653
	for <idn@ops.ietf.org>; Wed, 3 Oct 2001 08:46:48 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100300b7e0e2fdad64@[165.227.249.20]>
In-Reply-To: <20011002231942.E27342@nicemice.net>
References: <20011002231942.E27342@nicemice.net>
Date: Wed, 3 Oct 2001 08:46:15 -0700
To: IETF idn working group <idn@ops.ietf.org>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] Renaming "AMC-Z"
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

How about just "ACE"? Or, if people really think there will be future 
ACEs, "ACE-1"?

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Wed Oct  3 12:10:18 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20065
	for <idn-archive@lists.ietf.org>; Wed, 3 Oct 2001 12:10:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ooU9-000A9T-00
	for idn-data@psg.com; Wed, 03 Oct 2001 09:03:01 -0700
Received: from heron.verisign.com ([216.168.233.95])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ooU8-000A8z-00
	for idn@ops.ietf.org; Wed, 03 Oct 2001 09:03:00 -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 MAA14762
	for <idn@ops.ietf.org>; Wed, 3 Oct 2001 12:02:56 -0400 (EDT)
Received: by VSVAPOSTALGW1.prod.netsol.com with Internet Mail Service (5.5.2653.19)
	id <R5WDR7FQ>; Wed, 3 Oct 2001 12:02:40 -0400
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD6C5FAEF@vsvapostal3.prod.netsol.com>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: IETF idn working group <idn@ops.ietf.org>
Subject: RE: [idn] Renaming "AMC-Z"
Date: Wed, 3 Oct 2001 11:55:59 -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

>-----Original Message-----
>From: Paul Hoffman / IMC [mailto:phoffman@imc.org]
>Sent: Wednesday, October 03, 2001 11:46 AM
>To: IETF idn working group
>Subject: Re: [idn] Renaming "AMC-Z"
>
>
>How about just "ACE"? Or, if people really think there will be future 
>ACEs, "ACE-1"?

I'm for this sort of convention, though I'd suggest ACE-63 to note the
maximum length of encoded values.  It's sort of a "utilitarian but
descriptive" name in the model of FIPS algorithms like SHA.

<Scott/>



From owner-idn@ops.ietf.org  Wed Oct  3 12:24:31 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20392
	for <idn-archive@lists.ietf.org>; Wed, 3 Oct 2001 12:24:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ooia-000Ae3-00
	for idn-data@psg.com; Wed, 03 Oct 2001 09:17:56 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ooiZ-000Adx-00
	for idn@ops.ietf.org; Wed, 03 Oct 2001 09:17:55 -0700
Received: from [165.227.249.20] (165-227-249-20.client.dsl.net [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f93GHrD13562
	for <idn@ops.ietf.org>; Wed, 3 Oct 2001 09:17:53 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100303b7e0e743ae2f@[165.227.249.20]>
Date: Wed, 3 Oct 2001 09:04:12 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: [idn] Stringprep mailing list
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Just a reminder that the new stringprep document 
(draft-hoffman-stringprep) is being discussed on the ietf-stringprep 
mailing list. Info on that mailing list can be found in the document 
or at <http://www.imc.org/ietf-stringprep/>.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Wed Oct  3 13:35:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23259
	for <idn-archive@lists.ietf.org>; Wed, 3 Oct 2001 13:35:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oplV-000CfU-00
	for idn-data@psg.com; Wed, 03 Oct 2001 10:25:01 -0700
Received: from mail12.speakeasy.net ([216.254.0.212])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15oplU-000CfK-00
	for idn@ops.ietf.org; Wed, 03 Oct 2001 10:25:00 -0700
Received: (qmail 26884 invoked from network); 3 Oct 2001 17:24:55 -0000
Received: from unknown (HELO Magnus) ([64.81.85.4]) (envelope-sender <tim@xtns.net>)
          by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <shollenbeck@verisign.com>; 3 Oct 2001 17:24:55 -0000
Message-ID: <009101c14c2f$d68b1ea0$0200a8c0@Magnus>
From: "Tim Langdell" <tim@xtns.net>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>,
        "IETF idn working group" <idn@ops.ietf.org>
References: <3CD14E451751BD42BA48AAA50B07BAD6C5FAEF@vsvapostal3.prod.netsol.com>
Subject: Re: [idn] Renaming "AMC-Z"
Date: Wed, 3 Oct 2001 10:20:59 -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.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Just to bear in mind that this name will be used widely around the globe in
association with the registration and WhoIs of IDNs. Thus entirely
non-technically minded people will be faced with and have to deal with this
name.  (We've already had one person who asked us why the "RACE" of the name
was being requested -- "what does the ethnic background of the name have to
do with anything ..." )

I'd thus prefer a name that is easy to remember, short, not confusing, and
which is non-techie-sounding (there can I suppose always be the full
technical name that has "-63" or whatever attached to it which is used in
the tech community but not burdened on the global consumer/business
communities).

Tim

----- Original Message -----
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "IETF idn working group" <idn@ops.ietf.org>
Sent: Wednesday, October 03, 2001 8:55 AM
Subject: RE: [idn] Renaming "AMC-Z"


> >-----Original Message-----
> >From: Paul Hoffman / IMC [mailto:phoffman@imc.org]
> >Sent: Wednesday, October 03, 2001 11:46 AM
> >To: IETF idn working group
> >Subject: Re: [idn] Renaming "AMC-Z"
> >
> >
> >How about just "ACE"? Or, if people really think there will be future
> >ACEs, "ACE-1"?
>
> I'm for this sort of convention, though I'd suggest ACE-63 to note the
> maximum length of encoded values.  It's sort of a "utilitarian but
> descriptive" name in the model of FIPS algorithms like SHA.
>
> <Scott/>
>
>




From owner-idn@ops.ietf.org  Wed Oct  3 13:44:38 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23657
	for <idn-archive@lists.ietf.org>; Wed, 3 Oct 2001 13:44:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15opvv-000D6L-00
	for idn-data@psg.com; Wed, 03 Oct 2001 10:35:47 -0700
Received: from heron.verisign.com ([216.168.233.95])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15opvv-000D6E-00
	for idn@ops.ietf.org; Wed, 03 Oct 2001 10:35:47 -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 NAA18449;
	Wed, 3 Oct 2001 13:35:15 -0400 (EDT)
Received: by VSVAPOSTALGW1.prod.netsol.com with Internet Mail Service (5.5.2653.19)
	id <R5WDSAF1>; Wed, 3 Oct 2001 13:34:59 -0400
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD6C5FAF8@vsvapostal3.prod.netsol.com>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'Tim Langdell'" <tim@xtns.net>,
        IETF idn working group
	 <idn@ops.ietf.org>
Subject: RE: [idn] Renaming "AMC-Z"
Date: Wed, 3 Oct 2001 13:28:16 -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

>-----Original Message-----
>From: Tim Langdell [mailto:tim@xtns.net]
>Sent: Wednesday, October 03, 2001 1:21 PM
>To: Hollenbeck, Scott; IETF idn working group
>Subject: Re: [idn] Renaming "AMC-Z"
>
>
>Just to bear in mind that this name will be used widely around the globe in
>association with the registration and WhoIs of IDNs. Thus entirely
>non-technically minded people will be faced with and have to deal with this
>name.  (We've already had one person who asked us why the "RACE" of the
name
>was being requested -- "what does the ethnic background of the name have to
>do with anything ..." )
>
>I'd thus prefer a name that is easy to remember, short, not confusing, and
>which is non-techie-sounding (there can I suppose always be the full
>technical name that has "-63" or whatever attached to it which is used in
>the tech community but not burdened on the global consumer/business
>communities).

Asking a bunch on engineers to come up with a marketeer-satisfying name may
prove to be an interesting challenge!  Nonetheless, there's nothing much
simpler and easier to remember than Paul's suggestion of just "ACE" or
"ACE-1".

<Scott/>



From owner-idn@ops.ietf.org  Wed Oct  3 13:51:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23886
	for <idn-archive@lists.ietf.org>; Wed, 3 Oct 2001 13:51:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oq3P-000DMP-00
	for idn-data@psg.com; Wed, 03 Oct 2001 10:43:31 -0700
Received: from bean.ar.com ([66.123.187.68])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15oq3P-000DLk-00
	for idn@ops.ietf.org; Wed, 03 Oct 2001 10:43:31 -0700
Received: from loki (IDENT:wessorh@loki [66.123.187.67])
	by bean.ar.com (8.12.0/8.12.0) with ESMTP id f93HhIJB019657;
	Wed, 3 Oct 2001 10:43:18 -0700 (PDT)
Date: Wed, 3 Oct 2001 10:43:18 -0700 (PDT)
From: Rick H Wesson <wessorh@ar.com>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
cc: "'Tim Langdell'" <tim@xtns.net>, IETF idn working group <idn@ops.ietf.org>
Subject: RE: [idn] Renaming "AMC-Z"
In-Reply-To: <3CD14E451751BD42BA48AAA50B07BAD6C5FAF8@vsvapostal3.prod.netsol.com>
Message-ID: <Pine.LNX.4.30.0110031042450.25858-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


Might I suggest BACE - Best ACE.

I think thats what we did is pick the best one...

-rick


On Wed, 3 Oct 2001, Hollenbeck, Scott wrote:

> >-----Original Message-----
> >From: Tim Langdell [mailto:tim@xtns.net]
> >Sent: Wednesday, October 03, 2001 1:21 PM
> >To: Hollenbeck, Scott; IETF idn working group
> >Subject: Re: [idn] Renaming "AMC-Z"
> >
> >
> >Just to bear in mind that this name will be used widely around the globe in
> >association with the registration and WhoIs of IDNs. Thus entirely
> >non-technically minded people will be faced with and have to deal with this
> >name.  (We've already had one person who asked us why the "RACE" of the
> name
> >was being requested -- "what does the ethnic background of the name have to
> >do with anything ..." )
> >
> >I'd thus prefer a name that is easy to remember, short, not confusing, and
> >which is non-techie-sounding (there can I suppose always be the full
> >technical name that has "-63" or whatever attached to it which is used in
> >the tech community but not burdened on the global consumer/business
> >communities).
>
> Asking a bunch on engineers to come up with a marketeer-satisfying name may
> prove to be an interesting challenge!  Nonetheless, there's nothing much
> simpler and easier to remember than Paul's suggestion of just "ACE" or
> "ACE-1".
>
> <Scott/>
>




From owner-idn@ops.ietf.org  Wed Oct  3 13:57:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24030
	for <idn-archive@lists.ietf.org>; Wed, 3 Oct 2001 13:57:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oqAt-000Dck-00
	for idn-data@psg.com; Wed, 03 Oct 2001 10:51:15 -0700
Received: from mail12.speakeasy.net ([216.254.0.212])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15oqAt-000Dcd-00
	for idn@ops.ietf.org; Wed, 03 Oct 2001 10:51:15 -0700
Received: (qmail 43171 invoked from network); 3 Oct 2001 17:51:14 -0000
Received: from unknown (HELO Magnus) ([64.81.85.4]) (envelope-sender <tim@xtns.net>)
          by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <shollenbeck@verisign.com>; 3 Oct 2001 17:51:14 -0000
Message-ID: <00e201c14c33$8178b860$0200a8c0@Magnus>
From: "Tim Langdell" <tim@xtns.net>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>,
        "IETF idn working group" <idn@ops.ietf.org>
References: <3CD14E451751BD42BA48AAA50B07BAD6C5FAF8@vsvapostal3.prod.netsol.com>
Subject: Re: [idn] Renaming "AMC-Z"
Date: Wed, 3 Oct 2001 10:47:37 -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.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Yes. Quite agree. I suppose I am just asking that the engineers try to bear
in mind somewhat the use to which this will be put ... and then I guess the
marketing types can always come up with their version.

I too wonder if a simple "ACE" might work, and then have version numbers (or
whatever) for technical reference purposes to differentiate one ACE from
others?

Tim

----- Original Message -----
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'Tim Langdell'" <tim@xtns.net>; "IETF idn working group"
<idn@ops.ietf.org>
Sent: Wednesday, October 03, 2001 10:28 AM
Subject: RE: [idn] Renaming "AMC-Z"


> >-----Original Message-----
> >From: Tim Langdell [mailto:tim@xtns.net]
> >Sent: Wednesday, October 03, 2001 1:21 PM
> >To: Hollenbeck, Scott; IETF idn working group
> >Subject: Re: [idn] Renaming "AMC-Z"
> >
> >
> >Just to bear in mind that this name will be used widely around the globe
in
> >association with the registration and WhoIs of IDNs. Thus entirely
> >non-technically minded people will be faced with and have to deal with
this
> >name.  (We've already had one person who asked us why the "RACE" of the
> name
> >was being requested -- "what does the ethnic background of the name have
to
> >do with anything ..." )
> >
> >I'd thus prefer a name that is easy to remember, short, not confusing,
and
> >which is non-techie-sounding (there can I suppose always be the full
> >technical name that has "-63" or whatever attached to it which is used in
> >the tech community but not burdened on the global consumer/business
> >communities).
>
> Asking a bunch on engineers to come up with a marketeer-satisfying name
may
> prove to be an interesting challenge!  Nonetheless, there's nothing much
> simpler and easier to remember than Paul's suggestion of just "ACE" or
> "ACE-1".
>
> <Scott/>
>




From owner-idn@ops.ietf.org  Wed Oct  3 13:58:15 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24107
	for <idn-archive@lists.ietf.org>; Wed, 3 Oct 2001 13:58:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oqBm-000Dek-00
	for idn-data@psg.com; Wed, 03 Oct 2001 10:52:10 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15oqBl-000Dee-00
	for idn@ops.ietf.org; Wed, 03 Oct 2001 10:52:09 -0700
Received: from [192.168.1.5] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id TAA24146;
	Wed, 3 Oct 2001 19:51:30 +0200 (MET DST)
Date: Wed, 03 Oct 2001 19:43:17 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>,
        "'Tim Langdell'" <tim@xtns.net>,
        IETF idn working group <idn@ops.ietf.org>
Subject: RE: [idn] Renaming "AMC-Z"
Message-ID: <42281643.1002138197@localhost>
In-Reply-To: <3CD14E451751BD42BA48AAA50B07BAD6C5FAF8@vsvapostal3.prod.netsol.com>
References:  <3CD14E451751BD42BA48AAA50B07BAD6C5FAF8@vsvapostal3.prod.netsol.
 com>
X-Mailer: Mulberry/2.1.0 (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-10-03 13.28 -0400 "Hollenbeck, Scott" <shollenbeck@verisign.com>
wrote:

> Asking a bunch on engineers to come up with a marketeer-satisfying name
> may prove to be an interesting challenge!  Nonetheless, there's nothing
> much simpler and easier to remember than Paul's suggestion of just "ACE"
> or "ACE-1".

My personal proposal would be to call whatever IDN recommends just "ACE".
If the algorithm is changed, the "official" name will still be "ACE".

Just like SMTP is still SMTP...

  paf




From owner-idn@ops.ietf.org  Wed Oct  3 15:54:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27616
	for <idn-archive@lists.ietf.org>; Wed, 3 Oct 2001 15:54:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oroH-000H00-00
	for idn-data@psg.com; Wed, 03 Oct 2001 12:36:01 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15oroG-000Gzu-00
	for idn@ops.ietf.org; Wed, 03 Oct 2001 12:36:00 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VV8X/lQAZmN4TkGpqpcy7D7w==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GGUPWMHT; Wed, 03 Oct 2001 15:32:39 EDT
To: bill@mail.nic.nu
Cc: idn@ops.ietf.org
Date: Wed, 3 Oct 2001 12:52:26 -0700
Subject: Re: [idn] Is The IDN WGroup Still Active? Fwd: [IDNList] Registrar
Message-ID: <20011003.125229.-816135.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-26,28-77
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 am thinking this FYI is important for the users and 
administrators to be aware of if the WG go with any 
laguage tagged scheme at all.  Since: 

It may lead to inconsistent exception conditions due to 
changes in language specific normalization procedure. 
 For example, a UCS code point A in language tag T is 
excluded in Version X, as there is no blocking for any 
UCS code points in place yet.  Due to upgrade Version X+1, 
T(A) has been newly included tagged code blocks, then
 an input contains A  fail in Version X, but will succeed
 in Version X+1.  Due to failure in X will be coded with a 
defaulted ACE as a legal name, then the same input 
will not be fail in X+1, an inconsistency will resulted. 

If the WG has consensus on NOT using language tag
mechanism, it is better to voice this and let 
VeriSign users go ahead.

I am upgrade idn-map draft  to address this problem
 too, I need to know the above too, so that I don't 
need work for this group any more. Thank you all  for
saving my time.

Liana 


On Fri, 28 Sep 2001 16:18:12 -0400 bill@mail.nic.nu (J. William Semich)
writes:
> Haven't heard anything on the IDN list since Sept 1, so I'm wondering 
> if
> maybe the list has gone dark?
> 
> FYI, this just in from Verisign
> 
> -- Bill Semich
> 
> 
> >X-Authentication-Warning: imx3.pvt.lks.verisign-grs.net: majordomo 
> set
> >sender to owner-idntestbed@verisign-grs.com using -f
> >Reply-To: <info@verisign-grs.com>
> >From: "VeriSign Global Registry Services" <info@verisign-grs.com>
> >To: <idntestbed@verisign-grs.com>
> >Subject: [IDNList] Registrar Advisory: AMC-ACE- Z in the zones
> >Date: Fri, 28 Sep 2001 14:10:00 -0400
> >X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
> >Importance: Normal
> >Sender: owner-idntestbed@verisign-grs.com
> >X-MIME-Autoconverted: from 8bit to quoted-printable by 
> verisign-grs.com
> id
> >OAA23352
> >
> >To All IDN-Certified Registrars:
> >
> >VeriSign Global Registry Services (GRS) intends to move forward in 
> the
> >Internationalized Domain Name Testbed by placing the IDNs directly 
> into
> the
> >.com, .net and .org zones.  The zones will be populated with the
> AMC-ACE-Z
> >v0.3.1 representation of the IDNs.  Registrars do not need to 
> modify
> any of
> >their current registration processes to support this change.  All
> existing
> >IDNs originally registered with RACE will be valid under the 
> AMC-ACE-Z
> >encoding.
> 
> <snip>
> 
> 
> 
> 
> 



From owner-idn@ops.ietf.org  Wed Oct  3 22:04:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07937
	for <idn-archive@lists.ietf.org>; Wed, 3 Oct 2001 22:04:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oxRl-000309-00
	for idn-data@psg.com; Wed, 03 Oct 2001 18:37:09 -0700
From: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>
To: IETF idn working group <idn@ops.ietf.org>
Subject: Re: [idn] Renaming "AMC-Z"
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15oxRl-000309-00@psg.com>
Date: Wed, 03 Oct 2001 18:37:09 -0700

> How about just "ACE"?  Or, if people really think there will be future
> ACEs, "ACE-1"?

First let me clarify what I am trying to name.  I want a name for the
transformation from any Unicode string to an ASCII string (and the
reverse transformation).  The thing I am naming does not include the
prefix (xx--), does not include syntax restrictions like the 63-octet
limit, and does not include nameprep.  The thing I am naming is the
operations performed by the pseudocode in the AMC-ACE-Z spec, and no
more.

If people are willing to use the name ACE or ACE-1 for this, that would
be fine with me.  But if you would rather use the name ACE to refer
to a larger operation, then I still want a name for the thing I just
described.

(Up to now, ACE has been a fuzzy term.  It hasn't been clear where its
boundaries were.)

I usually don't like acronyms, but ACE is not bad.  I never like
acronyms that are misspellings of real words, so I'd rather not use
BACE, CHACE, or SUITCACE.

AMC





From owner-idn@ops.ietf.org  Wed Oct  3 22:06:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07979
	for <idn-archive@lists.ietf.org>; Wed, 3 Oct 2001 22:06:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oxeY-0003W0-00
	for idn-data@psg.com; Wed, 03 Oct 2001 18:50:22 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15oxeW-0003V8-00
	for idn@ops.ietf.org; Wed, 03 Oct 2001 18:50:21 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP id 51993FFC01
	for <idn@ops.ietf.org>; Thu,  4 Oct 2001 09:50:57 +0800 (SGT)
Message-ID: <016c01c14c76$ea176c20$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <idn@ops.ietf.org>
Subject: [idn] WG Update
Date: Thu, 4 Oct 2001 09:50:15 +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

In the last London meeting, there are still some outstanding issues
which we agreed to bring it back to the mailing list to discuss.

First, the issue of nameprep. nameprep have been renamed to stringprep
and the new draft is available few days ago. Please review
draft-ietf-idn-nameprep-06.txt.

And related to nameprep are the jpchar, hanguelchar and tsconv drafts.
The authors should get together to consider an architecture document.
We should set a deadline for this to be concluded, probably sometime
before Salt Lake meeting.

This architecture document should take into consideration of:
a. the recommendation from the Unicode Consortium to the WG dated 02Sept
b. the source and stablity of the referenced work/codepoints

(Personally, I would strongly recommend that nameprep remains as it is
and the rest of the "localization" to be deal at a different level,
either at the input method or below at the zone file.)

Secondly, there is a reordering draft draft-ietf-idn-lsb-ace. We have
already seen some results on reordering but we have not seen much
discussion on the downside of reordering. In anycase, we would like
to encourage further discussion on reordering draft as we would like
to conduct a strawpoll on the draft soon.

Thirdly, we have seen a strong number of people who is against UNAME and
UDNS. Therefore, we will be removing UNAME and UDNS from the WG Pool in
the next few days. Please take note that this does not prevent someone
from coming forward with another proposal.

The wg chairs have also receive several request to make updates on the
goal & milestone of the charter to reflect the current wg position. We
will send out a first draft for comments very shortly.

Some other wg matters:

As agreed in London meeting, the requirements draft will be moving
forward for IETF Last Call.

Based on the hum in London, the chairs also believe we have consensus
on AMC-ACE-Z (draft-ietf-idn-amc-ace-z) as the choosen ACE. We feel
a wg last call would provide no further information for the chairs to
determine consensus since most people are in the "don't care but just
want to see one ACE choosen" group. We will move AMC-ACE-Z forward to
the IESG at an appropriate time.

(minor note: we also agree that we should look for another name for
AMC-Z but I think that discussion have already started :-)

A prefix for AMC-Z will be assigned using the normal IESG/IANA/
RFC-editor procedure for coordinating assignment of protocol
parameters during IETF last call and publication as an RFC.

Given this, we would like to advise people to start doing
interoperability testing on their implementation of AMC-Z.

For you information and comments.

James Seng
co-chair IDN wg




From owner-idn@ops.ietf.org  Wed Oct  3 22:08:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07995
	for <idn-archive@lists.ietf.org>; Wed, 3 Oct 2001 22:08:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oxes-0003Xw-00
	for idn-data@psg.com; Wed, 03 Oct 2001 18:50:42 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15oxer-0003Xd-00
	for idn@ops.ietf.org; Wed, 03 Oct 2001 18:50:41 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP id E2024FFC15
	for <idn@ops.ietf.org>; Thu,  4 Oct 2001 09:51:20 +0800 (SGT)
Message-ID: <017601c14c76$f8260e20$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <idn@ops.ietf.org>
Subject: [idn] WG Update
Date: Thu, 4 Oct 2001 09:50:39 +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

In the last London meeting, there are still some outstanding issues
which we agreed to bring it back to the mailing list to discuss.

First, the issue of nameprep. nameprep have been renamed to stringprep
and the new draft is available few days ago. Please review
draft-ietf-idn-nameprep-06.txt.

And related to nameprep are the jpchar, hanguelchar and tsconv drafts.
The authors should get together to consider an architecture document.
We should set a deadline for this to be concluded, probably sometime
before Salt Lake meeting.

This architecture document should take into consideration of:
a. the recommendation from the Unicode Consortium to the WG dated 02Sept
b. the source and stablity of the referenced work/codepoints

(Personally, I would strongly recommend that nameprep remains as it is
and the rest of the "localization" to be deal at a different level,
either at the input method or below at the zone file.)

Secondly, there is a reordering draft draft-ietf-idn-lsb-ace. We have
already seen some results on reordering but we have not seen much
discussion on the downside of reordering. In anycase, we would like
to encourage further discussion on reordering draft as we would like
to conduct a strawpoll on the draft soon.

Thirdly, we have seen a strong number of people who is against UNAME and
UDNS. Therefore, we will be removing UNAME and UDNS from the WG Pool in
the next few days. Please take note that this does not prevent someone
from coming forward with another proposal.

The wg chairs have also receive several request to make updates on the
goal & milestone of the charter to reflect the current wg position. We
will send out a first draft for comments very shortly.

Some other wg matters:

As agreed in London meeting, the requirements draft will be moving
forward for IETF Last Call.

Based on the hum in London, the chairs also believe we have consensus
on AMC-ACE-Z (draft-ietf-idn-amc-ace-z) as the choosen ACE. We feel
a wg last call would provide no further information for the chairs to
determine consensus since most people are in the "don't care but just
want to see one ACE choosen" group. We will move AMC-ACE-Z forward to
the IESG at an appropriate time.

(minor note: we also agree that we should look for another name for
AMC-Z but I think that discussion have already started :-)

A prefix for AMC-Z will be assigned using the normal IESG/IANA/
RFC-editor procedure for coordinating assignment of protocol
parameters during IETF last call and publication as an RFC.

Given this, we would like to advise people to start doing
interoperability testing on their implementation of AMC-Z.

For you information and comments.

James Seng
co-chair IDN wg





From owner-idn@ops.ietf.org  Wed Oct  3 22:17:27 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08129
	for <idn-archive@lists.ietf.org>; Wed, 3 Oct 2001 22:17:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15oxlg-0003jc-00
	for idn-data@psg.com; Wed, 03 Oct 2001 18:57:44 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15oxlf-0003jV-00
	for idn@ops.ietf.org; Wed, 03 Oct 2001 18:57:44 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id B13E7FFC15; Thu,  4 Oct 2001 09:58:22 +0800 (SGT)
Message-ID: <01a901c14c77$f393bf50$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: <bill@mail.nic.nu>, <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>
References: <20011003.125229.-816135.0.liana.ydisg@juno.com>
Subject: Re: [idn] Is The IDN WGroup Still Active? Fwd: [IDNList] Registrar
Date: Thu, 4 Oct 2001 09:57:41 +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

> It may lead to inconsistent exception conditions due to 
> changes in language specific normalization procedure. 
>  For example, a UCS code point A in language tag T is 
> excluded in Version X, as there is no blocking for any 
> UCS code points in place yet.  Due to upgrade Version X+1, 
> T(A) has been newly included tagged code blocks, then
>  an input contains A  fail in Version X, but will succeed
>  in Version X+1.  Due to failure in X will be coded with a 
> defaulted ACE as a legal name, then the same input 
> will not be fail in X+1, an inconsistency will resulted. 

See nameprep-08. it is discussed extensively how to deal with
this situation.
 
> If the WG has consensus on NOT using language tag
> mechanism, it is better to voice this and let 
> VeriSign users go ahead.

dont see how verisign testbed have anything to do with idn wg.
please keep things in focus.

-James Seng




From owner-idn@ops.ietf.org  Thu Oct  4 00:44:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12634
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 00:44:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15p0Fk-000A03-00
	for idn-data@psg.com; Wed, 03 Oct 2001 21:36:56 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15p0Fj-0009zx-00
	for idn@ops.ietf.org; Wed, 03 Oct 2001 21:36:55 -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; Wed, 3 Oct 2001 21:49:34 -0700
Message-ID: <000f01c14c8f$79578e20$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>,
        "IETF idn working group" <idn@ops.ietf.org>
References: <E15oxRl-000309-00@psg.com>
Subject: Re: [idn] Renaming "AMC-Z"
Date: Thu, 4 Oct 2001 00:46:03 -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 Adam,

>
> I usually don't like acronyms, but ACE is not bad.  I never like
> acronyms that are misspellings of real words, so I'd rather not use
> BACE, CHACE, or SUITCACE.
>
> AMC
>

How about GRACE?  GRACE is *not* a misspelling of real words.  NO...
no... not because my mother is called "Grace" and I want to name
something after her.

But... "With GRACE (defined as god's free and underserved favor to and
love for mankind) the world will become one."

Thanks,
Ben Chan




From owner-idn@ops.ietf.org  Thu Oct  4 00:50:35 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12823
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 00:50:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15p0Ks-000ADc-00
	for idn-data@psg.com; Wed, 03 Oct 2001 21:42:14 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15p0Ks-000ADS-00
	for idn@ops.ietf.org; Wed, 03 Oct 2001 21:42:14 -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, 3 Oct 2001 21:54:52 -0700
Message-ID: <004c01c14c90$3748bd00$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: <idn@ops.ietf.org>
References: <20011003.125229.-816135.0.liana.ydisg@juno.com> <01a901c14c77$f393bf50$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] Renaming "AMC-Z"
Date: Thu, 4 Oct 2001 00:51:21 -0400
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 Adam,

>
> I usually don't like acronyms, but ACE is not bad.  I never like
> acronyms that are misspellings of real words, so I'd rather not use
> BACE, CHACE, or SUITCACE.
>
> AMC
>

How about GRACE?  GRACE is *not* a misspelling of real words.  NO...
no... not because my mother is called "Grace" and I want to name
something after her.

But... "With GRACE (defined as god's free and underserved favor to and
love for mankind) the world will become one."

Thanks,
Ben Chan





From owner-idn@ops.ietf.org  Thu Oct  4 02:39:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27787
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 02:39:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15p1qV-000DsX-00
	for idn-data@psg.com; Wed, 03 Oct 2001 23:18:59 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15p1qU-000DsQ-00
	for idn@ops.ietf.org; Wed, 03 Oct 2001 23:18:59 -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 f946FgK00339 for <idn@ops.ietf.org>; Thu, 4 Oct 2001 08:16:38 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.11.4+Sun/TRM-1-KLIENT); Thu, 4 Oct 2001 08:16:28 +0200 (MEST) (MET)
Message-Id: <200110040616.f946GSj18617@valinor.malmo.trab.se>
Date: Thu, 4 Oct 2001 08:16:28 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: [idn] Renaming "AMC-Z"
To: idn@ops.ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: n+4cY972czHe7IrKn0C6ZQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.5_41 SunOS 5.9 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk


>First let me clarify what I am trying to name.  I want a name for the
>transformation from any Unicode string to an ASCII string (and the
>reverse transformation).  The thing I am naming does not include the
>prefix (xx--), does not include syntax restrictions like the 63-octet
>limit, and does not include nameprep.  The thing I am naming is the
>operations performed by the pseudocode in the AMC-ACE-Z spec, and no
>more.
>
>If people are willing to use the name ACE or ACE-1 for this, that would
>be fine with me.  But if you would rather use the name ACE to refer
>to a larger operation, then I still want a name for the thing I just
>described.
>
>(Up to now, ACE has been a fuzzy term.  It hasn't been clear where its
>boundaries were.)

I agree. ACE should stand for the UCS into ASCII A-Za-z0-9- encoding.
No length restrictions, no nameprep. Though the UCS must be normalised
so that it is well defined.
That is, ACE should stands for:
- UCS normalised into Unicode form C
- then encoded into the characters A-Za-z0-9-

The specific rules that could be used over DNS could be called
BCE (Backward Compatible Encoding).

   Dan




From owner-idn@ops.ietf.org  Thu Oct  4 03:14:20 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00428
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 03:14:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15p2Vq-000FRP-00
	for idn-data@psg.com; Thu, 04 Oct 2001 00:01:42 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15p2Vp-000FR0-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 00:01: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 f946xoK05527 for <idn@ops.ietf.org>; Thu, 4 Oct 2001 08:59:50 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.11.4+Sun/TRM-1-KLIENT); Thu, 4 Oct 2001 09:00:37 +0200 (MEST) (MET)
Message-Id: <200110040700.f9470bj18628@valinor.malmo.trab.se>
Date: Thu, 4 Oct 2001 09:00:37 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: [idn] I fear I cannot use IDN in the next 10 years
To: idn@ops.ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: lIcdwFb1xsPesmmwZEclDA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.5_41 SunOS 5.9 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk

As the IDN list have been only focused on ACE and are now removing the
proposals that support IDN nativly in the DNS protocol, I fear that
I will not be able to use non-ascii domain names for the next 10 years.

To understand why, you have to look at how domain names are used on your
computer systems.
When I look at mine, I enter or handle domain/host names in many places,
for example: host-files, logs, web pages, text documents and databases.
In all these places the names are using my systems local native character set.
All programs handle that.
To use non-ascii names, the only acceptable way to do it is to enter them
natively in all places. Natively does not mean ACEencoded names, it means
using the native character set. My web pages will never containg ACE in
URLs, they will containg ISO 8859-1 characters just like the rest of
my web pages. My host files may not contain ACE, the must use ISO 8859-1.
To use ACE-encoded host names can never be an application specific modification.
The only viable way to do it is to convert all names when they leav the
DNS protocol into local character set. Under Unix this could be done
in the resolver libraries so that applications never need to know the
protocol used over DNS.
To allow mixed usage of ACE-encoded and native names will result in a
terrible mess. The only usable way is for all names to be nativly encoded
within a system. 

The current groups wanting ACE-encoded names do not take this into
consideration. At least I have seen no discussions about it.

As all ACE-encoded names need to be decoded into native names when
entering a system, why not use UTF-8 over the wire to support simpler
handling of names?
There are two places where ACE-encoded names are needed:
1) When talking to ancient systems.
2) When not being able to represent an UCS name using the local native
   character set.
But in all other cases UTF-8 will do and will result for systems
using UTF-8 natively that they can use dns names without any
convertion. This will never happen with ACE, no system will ever
use ACE-encoded text as native character set.

So forget about quick use of non-ASCII names because of ACE. As long as my
applications cannot accept a native name or an UTF-8 name, non-ASCII
names cannot be used. I am not going to expose my users to the
mess and confusion that ACE-encoded names will result in.

When I can register a domain name using non-ASCII characters and can
query and get it returned in UTF-8 or ISO 8859-1, and my system stop
rejecting names because they conatin non-ASCII characters, then I can
start using IDNs.

    Dan




From owner-idn@ops.ietf.org  Thu Oct  4 03:26:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00789
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 03:26:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15p2kw-000GKK-00
	for idn-data@psg.com; Thu, 04 Oct 2001 00:17:18 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15p2kv-000GKB-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 00:17:17 -0700
Received: from bbprime.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 AAA13061;
	Thu, 4 Oct 2001 00:15:55 -0700
Message-Id: <5.1.0.14.2.20011004001400.039ff980@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 04 Oct 2001 00:16:35 -0700
To: Dan Oscarsson <Dan.Oscarsson@trab.se>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
Cc: idn@ops.ietf.org
In-Reply-To: <200110040700.f9470bj18628@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 12:00 AM 10/4/2001, Dan Oscarsson wrote:
>In all these places the names are using my systems local native character set.
>All programs handle that.

You seem to be confused about the difference between exchange standards and 
user interface behavior.  They are entirely different things, and operate 
quite independently.

Also, as has been pointed out repeatedly, UTF8 is no more "native" than is ACE.

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 Oct  4 05:53:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03691
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 05:53:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15p54m-000MO4-00
	for idn-data@psg.com; Thu, 04 Oct 2001 02:45:56 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15p54m-000MNW-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 02:45:56 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 43D887F4C5; Thu,  4 Oct 2001 18:45:11 +0900 (JST)
Message-Id: <4.2.0.58.J.20011004143132.02f16ae0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 04 Oct 2001 14:35:51 +0900
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>,
        "'Tim Langdell'" <tim@xtns.net>,
        IETF idn working group <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: RE: [idn] Renaming "AMC-Z"
In-Reply-To: <3CD14E451751BD42BA48AAA50B07BAD6C5FAF8@vsvapostal3.prod.ne
 tsol.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 13:28 01/10/03 -0400, Hollenbeck, Scott wrote:

>Nonetheless, there's nothing much
>simpler and easier to remember than Paul's suggestion of just "ACE" or
>"ACE-1".

I think ACE is already used for the general concept of mapping to
ASCII only. If we use ACE, quite a bit of the archives of this
group will become difficult to read for people who think that
ACE is ACM-Z. As for ACE-1, although we cannot exclude further
ACEs, I think it would be a bad idea to give the impression that
we are starting a series.

Some ideas: What about ZACE or Z-ACE, or ACE-Z ? I don't know
what the Z in ACM-Z stands for, but it seems to have served its
purpose well up to now.

Regards,   Martin.



From owner-idn@ops.ietf.org  Thu Oct  4 09:07:02 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10666
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 09:07:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15p7km-0003eY-00
	for idn-data@psg.com; Thu, 04 Oct 2001 05:37:28 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15p7kl-0003eS-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 05:37:27 -0700
Received: from CLASSIC.viagenie.qc.ca (retro.viagenie.qc.ca [206.123.31.22])
	by jazz.viagenie.qc.ca (Viagenie/8.11.0) with ESMTP id f94CeiK56710;
	Thu, 4 Oct 2001 08:40:44 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20011003153954.0288a008@127.0.0.1>
X-Sender: blanchet@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 03 Oct 2001 15:42:43 -0400
To: "Tim Langdell" <tim@xtns.net>,
        "Hollenbeck, Scott" <shollenbeck@verisign.com>,
        "IETF idn working group" <idn@ops.ietf.org>
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: Re: [idn] Renaming "AMC-Z"
In-Reply-To: <00e201c14c33$8178b860$0200a8c0@Magnus>
References: <3CD14E451751BD42BA48AAA50B07BAD6C5FAF8@vsvapostal3.prod.netsol.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

At/À 10:47 2001-10-03 -0700, Tim Langdell you wrote/vous écriviez:
>Yes. Quite agree. I suppose I am just asking that the engineers try to bear
>in mind somewhat the use to which this will be put ... and then I guess the
>marketing types can always come up with their version.
>
>I too wonder if a simple "ACE" might work, and then have version numbers (or
>whatever) for technical reference purposes to differentiate one ACE from
>others?

not sure if we really will have another ACE later. probability is pretty 
low. you never know, but given the potential spread of the ACE, the new one 
must be very appealing to overcome the deployment of it.

but if this ever happen,
then the current one can be identified as ACE
and the second one could be identified as ACE2 or ACEv2 or ....
(as with snmp, snmpv2, ip -> ipng, ...: i.e. the first one was the short 
name, the second one add a new suffix to it)

Marc.


>Tim
>
>----- Original Message -----
>From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
>To: "'Tim Langdell'" <tim@xtns.net>; "IETF idn working group"
><idn@ops.ietf.org>
>Sent: Wednesday, October 03, 2001 10:28 AM
>Subject: RE: [idn] Renaming "AMC-Z"
>
>
> > >-----Original Message-----
> > >From: Tim Langdell [mailto:tim@xtns.net]
> > >Sent: Wednesday, October 03, 2001 1:21 PM
> > >To: Hollenbeck, Scott; IETF idn working group
> > >Subject: Re: [idn] Renaming "AMC-Z"
> > >
> > >
> > >Just to bear in mind that this name will be used widely around the globe
>in
> > >association with the registration and WhoIs of IDNs. Thus entirely
> > >non-technically minded people will be faced with and have to deal with
>this
> > >name.  (We've already had one person who asked us why the "RACE" of the
> > name
> > >was being requested -- "what does the ethnic background of the name have
>to
> > >do with anything ..." )
> > >
> > >I'd thus prefer a name that is easy to remember, short, not confusing,
>and
> > >which is non-techie-sounding (there can I suppose always be the full
> > >technical name that has "-63" or whatever attached to it which is used in
> > >the tech community but not burdened on the global consumer/business
> > >communities).
> >
> > Asking a bunch on engineers to come up with a marketeer-satisfying name
>may
> > prove to be an interesting challenge!  Nonetheless, there's nothing much
> > simpler and easier to remember than Paul's suggestion of just "ACE" or
> > "ACE-1".
> >
> > <Scott/>
> >





From owner-idn@ops.ietf.org  Thu Oct  4 09:48:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12621
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 09:48:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15p8UQ-0005lc-00
	for idn-data@psg.com; Thu, 04 Oct 2001 06:24:38 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15p8UP-0005lW-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 06:24:37 -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, 4 Oct 2001 06:37:14 -0700
Message-ID: <001001c14cd9$31dd85a0$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "ben" <ben@cc-www.com>, <idn@ops.ietf.org>
References: <20011003.125229.-816135.0.liana.ydisg@juno.com> <01a901c14c77$f393bf50$dd00a8c0@jamessonyvaio> <004c01c14c90$3748bd00$d43f7018@mtag1.on.home.com>
Subject: Re: [idn] Renaming "AMC-Z"
Date: Thu, 4 Oct 2001 09:33:46 -0400
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

Forgot to say that GRACE stands for "Greatly Reduced ASCII Compatible
Encoding".

By the way, here is another definition:

"With GRACE (defined as a thing of beauty that is with pleasing or
agreeable quality) the world will become one."

Thanks
Ben Chan

>
> How about GRACE?  GRACE is *not* a misspelling of real words.  NO...
> no... not because my mother is called "Grace" and I want to name
> something after her.
>
> But... "With GRACE (defined as god's free and underserved favor to
and
> love for mankind) the world will become one."
>
> Thanks,
> Ben Chan
>
>
>
>




From owner-idn@ops.ietf.org  Thu Oct  4 12:15:43 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17711
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 12:15:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pB0l-000DLW-00
	for idn-data@psg.com; Thu, 04 Oct 2001 09:06:11 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.33 #1)
	id 15pB0j-000DLQ-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 09:06:09 -0700
Received: (qmail 28855 invoked by uid 1001); 4 Oct 2001 15:26:30 -0000
Date: 4 Oct 2001 15:26:30 -0000
Message-ID: <20011004152630.20354.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] 7CE
References: <20011003.125229.-816135.0.liana.ydisg@juno.com> <01a901c14c77$f393bf50$dd00a8c0@jamessonyvaio> <004c01c14c90$3748bd00$d43f7018@mtag1.on.home.com> <001001c14cd9$31dd85a0$d43f7018@mtag1.on.home.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

ASCII is a standard _encoding_ of characters as bytes: in other words, a
function from byte strings to character strings.

ASCII specifies that, for example, the byte string 100 122 45 45 102 111
111 represents the character string dz--foo.

UTF-8 is compatible with ASCII. The UTF-8 function, restricted to ASCII
byte strings, is exactly the ASCII function. 100 122 45 45 102 111 111
means dz--foo under UTF-8, just as it does under ASCII.

In contrast, if an encoding maps 100 122 45 45 102 111 111 to something
other than dz--foo, that encoding is _not_ compatible with ASCII.

``ASCII'' does not mean ``7-bit.'' It is simply not correct to refer to
Q-P-style Unicode encodings as ``ASCII compatible.'' ASCII is not merely
a set of numbers; it assigns _characters_ to those numbers.

The correct phrase is ``7-bit compatible.'' The encoded strings are
compatible with 7-bit channels. That's the point of these encodings.

---Dan



From owner-idn@ops.ietf.org  Thu Oct  4 12:28:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18418
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 12:28:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pBFv-000EBE-00
	for idn-data@psg.com; Thu, 04 Oct 2001 09:21:51 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pBFu-000EAu-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 09:21:50 -0700
Received: from bbprime.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 JAA32729;
	Thu, 4 Oct 2001 09:21:37 -0700
Message-Id: <5.1.0.14.2.20011004092041.03a887f8@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 04 Oct 2001 09:22:16 -0700
To: "D. J. Bernstein" <djb@cr.yp.to>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] 7CE
Cc: idn@ops.ietf.org
In-Reply-To: <20011004152630.20354.qmail@cr.yp.to>
References: <20011003.125229.-816135.0.liana.ydisg@juno.com>
 <01a901c14c77$f393bf50$dd00a8c0@jamessonyvaio>
 <004c01c14c90$3748bd00$d43f7018@mtag1.on.home.com>
 <001001c14cd9$31dd85a0$d43f7018@mtag1.on.home.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 08:26 AM 10/4/2001, D. J. Bernstein wrote:
>The correct phrase is ``7-bit compatible.'' The encoded strings are
>compatible with 7-bit channels. That's the point of these encodings.

30 years of consistent use tends to carry more weight than a single 
person's recent desire to impose linguistic changes.

And it is difficult to imagine how this line of discussion is in any way 
seriously helpful to the IDN working group reaching closure.

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 Oct  4 12:33:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18518
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 12:33:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pBKT-000EQg-00
	for idn-data@psg.com; Thu, 04 Oct 2001 09:26:33 -0700
Received: from angry.realnames.com ([216.35.85.219])
	by psg.com with smtp (Exim 3.33 #1)
	id 15pBKS-000EQY-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 09:26:32 -0700
Received: (qmail 6945 invoked by uid 104); 4 Oct 2001 16:26:31 -0000
Received: from yves@realnames.com by angry.realnames.com with qmail-scanner-0.96 (. Clean. Processed in 0.948126 secs); 04 Oct 2001 16:26:31 -0000
Received: from heaven.internal.realnames.com (10.1.5.39)
  by angry.realnames.com with SMTP; 4 Oct 2001 16:26:29 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:1976]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <16933@heaven.internal.realnames.com>
	 for <Dan.Oscarsson@trab.se>; Thu, 4 Oct 2001 9:24:00 AM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2653.19)
	id <T7GX239P>; Thu, 4 Oct 2001 09:26:24 -0700
Message-ID: <7FC3066C236FD511BC5900508BAC86FE1E62C0@trestles.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: "'Dan Oscarsson'" <Dan.Oscarsson@trab.se>, idn@ops.ietf.org
Subject: RE: [idn] Renaming "AMC-Z"
Date: Thu, 4 Oct 2001 09:23:23 -0700 
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

> I agree. ACE should stand for the UCS into ASCII A-Za-z0-9- encoding.
> No length restrictions, no nameprep. Though the UCS must be normalised
> so that it is well defined.
> That is, ACE should stands for:
> - UCS normalised into Unicode form C
> - then encoded into the characters A-Za-z0-9-

I wouldn't mix normalization with this. First, in the case of IDN, the
normalization is KC, and it follows some character mappings, and also
precedes some other code point validation (forbidden code points).

In addition to that, ACE drafts do not require the normalization. The RACE
one doesn't even mention it, and the AMC-ACE-Z simply acknowledges the fact
that this particular ACE, used in the context of IDNA, is applied on strings
that went through Nameprep first.

I am for keeping the separation between the two processes. Though I see why
one would want to mix them, since people typically refer (improperly I
believe) to the ACE-encoded IDN and not to the ACE-endoded Nameprepped-IDN,
while meaning the latter. Maybe it should be the IDNA-encoded IDN?

YA



From owner-idn@ops.ietf.org  Thu Oct  4 12:35:43 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18550
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 12:35:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pBMd-000EaK-00
	for idn-data@psg.com; Thu, 04 Oct 2001 09:28:47 -0700
Received: from angry.realnames.com ([216.35.85.219])
	by psg.com with smtp (Exim 3.33 #1)
	id 15pBMd-000Ea0-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 09:28:47 -0700
Received: (qmail 7175 invoked by uid 104); 4 Oct 2001 16:28:46 -0000
Received: from yves@realnames.com by angry.realnames.com with qmail-scanner-0.96 (. Clean. Processed in 0.948287 secs); 04 Oct 2001 16:28:46 -0000
Received: from heaven.internal.realnames.com (10.1.5.39)
  by angry.realnames.com with SMTP; 4 Oct 2001 16:28:45 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:2055]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <16948@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Thu, 4 Oct 2001 9:26:07 AM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2653.19)
	id <T7GX2398>; Thu, 4 Oct 2001 09:28:31 -0700
Message-ID: <7FC3066C236FD511BC5900508BAC86FE1E62C1@trestles.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: "'idn@ops.ietf.org'" <idn@ops.ietf.org>
Subject: RE: [idn] Renaming "AMC-Z"
Date: Thu, 4 Oct 2001 09:25:30 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1252"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I like Martin's suggestion of ACE-Z too. Simple, easy to remember, suggests
some kind of finality (please don't suggest AMC-OMEGA ;-))

YA



From owner-idn@ops.ietf.org  Thu Oct  4 13:12:43 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19410
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 13:12:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pBu2-000G7Z-00
	for idn-data@psg.com; Thu, 04 Oct 2001 10:03:18 -0700
Received: from femail43.sdc1.sfba.home.com ([24.254.60.37])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pBu2-000G7T-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 10:03:18 -0700
Received: from anteroom ([65.8.26.205]) by femail43.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20011004170317.OSLB10352.femail43.sdc1.sfba.home.com@anteroom>
          for <idn@ops.ietf.org>; Thu, 4 Oct 2001 10:03:17 -0700
Message-ID: <002e01c14cf6$6ff3f7d0$1000a8c0@anteroom>
From: "Bright Fulton" <bright@alldomains.com>
To: "IETF idn working group" <idn@ops.ietf.org>
References: <E15oxRl-000309-00@psg.com>
Subject: Re: [idn] Renaming "AMC-Z"
Date: Thu, 4 Oct 2001 13:03: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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Adam wrote:
> First let me clarify what I am trying to name.  I want a name for the
> transformation from any Unicode string to an ASCII string (and the
> reverse transformation).  The thing I am naming does not include the
> prefix (xx--), does not include syntax restrictions like the 63-octet
> limit, and does not include nameprep.  The thing I am naming is the
> operations performed by the pseudocode in the AMC-ACE-Z spec, and no
> more.
>
> If people are willing to use the name ACE or ACE-1 for this, that would
> be fine with me.  But if you would rather use the name ACE to refer
> to a larger operation, then I still want a name for the thing I just
> described.

Good point.  So, there is the larger process that does nameprep, the
length and syntax restrictions, AMC-ACE-Z, and prefix adding.  Most people
call this ACE.  Most people also call the encoding step (now AMC-ACE-Z)
ACE.

If people are comfortable with the naming overlap of the larger process
and the encoding step of that process then we should pick an ACE name that
describes both, leaving context to provide the cue as to which ACE you
mean.

And if people want to rename AMC-ACE-Z to something, be clear that you are
only renaming the encoding step.  This does not have to be a non-technical
name, as it will not be used by many non-technical people.  I'm for
leaving it alone, as we all know what it means.

I do think we should name the larger process.  We loosely call it ACE, but
ACE is a generic acronym, as someone pointed out earlier.

and Adam wrote:
> (Up to now, ACE has been a fuzzy term.  It hasn't been clear where its
> boundaries were.)

I think ACE is okay as a fuzzy term.  It is a broad concept, ACE.  Instead
of narrowing the defenition of what ACE means, we should make our ACE
terms more specific.

What we have here is two forms of ACE.  We have the encoding step,
AMC-ACE-Z, and we have the general ACE that is suitable for IDNs.  Maybe
we should call that larger process (including nameprep, syntax
restrictions and prefix prepending) IDN-ACE or something else which makes
clear that this process produces encoded strings which are suitable for
use in domain names.

> I usually don't like acronyms, but ACE is not bad.  I never like
> acronyms that are misspellings of real words, so I'd rather not use
> BACE, CHACE, or SUITCACE.

SUITCACE was tongue in cheek.  I think it is, like much baggage I've used,
too large to be of general use.  Sorry.

Bright Fulton





From owner-idn@ops.ietf.org  Thu Oct  4 14:00:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20652
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 14:00:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pCWT-000ICi-00
	for idn-data@psg.com; Thu, 04 Oct 2001 10:43:01 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pCWS-000ICc-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 10:43:00 -0700
Received: from [165.227.249.20] (165-227-249-20.client.dsl.net [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f94HgvD07757
	for <idn@ops.ietf.org>; Thu, 4 Oct 2001 10:42:57 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0510030db7e24dddbe55@[165.227.249.20]>
In-Reply-To: <4.2.0.58.J.20011004143132.02f16ae0@localhost>
References: <4.2.0.58.J.20011004143132.02f16ae0@localhost>
Date: Thu, 4 Oct 2001 10:34:45 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: RE: [idn] Renaming "AMC-Z"
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 2:35 PM +0900 10/4/01, Martin Duerst wrote:
>At 13:28 01/10/03 -0400, Hollenbeck, Scott wrote:
>
>>Nonetheless, there's nothing much
>>simpler and easier to remember than Paul's suggestion of just "ACE" or
>>"ACE-1".
>
>I think ACE is already used for the general concept of mapping to
>ASCII only.

As far as I can tell, the term "ACE" is only used in this WG and nowhere else.

>  If we use ACE, quite a bit of the archives of this
>group will become difficult to read for people who think that
>ACE is ACM-Z.

For all three people who read the archive...

>  As for ACE-1, although we cannot exclude further
>ACEs, I think it would be a bad idea to give the impression that
>we are starting a series.

Exactly why calling it "ACE" is probably better.

>Some ideas: What about ZACE or Z-ACE, or ACE-Z ? I don't know
>what the Z in ACM-Z stands for, but it seems to have served its
>purpose well up to now.

ZACE indicates other ACEs just as well as ACE-1 does.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Thu Oct  4 14:02:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20740
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 14:02:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pCYz-000IL2-00
	for idn-data@psg.com; Thu, 04 Oct 2001 10:45:37 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pCYy-000IKn-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 10:45:36 -0700
Received: from [165.227.249.20] (165-227-249-20.client.dsl.net [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f94HgwD07761;
	Thu, 4 Oct 2001 10:42:58 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0510030eb7e24eb9f210@[165.227.249.20]>
In-Reply-To: <200110040700.f9470bj18628@valinor.malmo.trab.se>
References: <200110040700.f9470bj18628@valinor.malmo.trab.se>
Date: Thu, 4 Oct 2001 10:41:49 -0700
To: Dan Oscarsson <Dan.Oscarsson@trab.se>, idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 9:00 AM +0200 10/4/01, Dan Oscarsson wrote:
>As all ACE-encoded names need to be decoded into native names when
>entering a system, why not use UTF-8 over the wire to support simpler
>handling of names?

For the same reasons people have been repeating on this list for the 
past year. UTF-8 is the "native" encoding for a very small number of 
people. Further, even for that very small number of people, UTF-8 is 
almost never the only encoding they have. Because of that, we need to 
assume that essentially all software that takes in or displays IDNs 
will have to do some conversion before putting the name parts on the 
wire. If we are going to require conversion, it is better to do that 
conversion to something that is already compatible with the current 
DNS protocol.

Updating all of the DNS servers in the world is an option, but not 
one that makes much sense.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Thu Oct  4 14:23:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21303
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 14:23:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pD0k-000Jvz-00
	for idn-data@psg.com; Thu, 04 Oct 2001 11:14:18 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.33 #1)
	id 15pD0j-000Jvs-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 11:14:17 -0700
Received: (qmail 5809 invoked by uid 1001); 4 Oct 2001 16:58:02 -0000
Date: 4 Oct 2001 16:58:02 -0000
Message-ID: <20011004165802.17656.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] 7CE
References: <20011003.125229.-816135.0.liana.ydisg@juno.com> <01a901c14c77$f393bf50$dd00a8c0@jamessonyvaio> <004c01c14c90$3748bd00$d43f7018@mtag1.on.home.com> <001001c14cd9$31dd85a0$d43f7018@mtag1.on.home.com> <20011004152630.20354.qmail@cr.yp.to> <5.1.0.14.2.20011004092041.03a887f8@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:
> 30 years of consistent use tends to carry more weight than a single 
> person's recent desire to impose linguistic changes.

You are making a fool of yourself, Dave.

As you can easily see from a web search, people consistently and
correctly refer to 8859-1, KOI-8, UTF-8, etc. as being ASCII-compatible.
This includes the authors of RFC 2376, RFC 2445, RFC 3023, the Linux
UTF-8 manual page, etc.

Meanwhile, people consistently and correctly refer to Baudot, for
example, as being incompatible with ASCII, even though Baudot fits
inside 7 bits with room to spare.

The use of ``ASCII'' to mean ``7-bit'' is a silly mistake in some recent
IETF documents: specifically, RFC 2130 and this group's ``ACE'' garbage.
Now that the error has been pointed out, it can easily be fixed.

---Dan



From owner-idn@ops.ietf.org  Thu Oct  4 14:23:41 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21320
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 14:23:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pD2N-000K2e-00
	for idn-data@psg.com; Thu, 04 Oct 2001 11:15:59 -0700
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pD2M-000K2Y-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 11:15:58 -0700
Received: from [209.187.148.217] (helo=P2)
	by bs.jck.com with esmtp (Exim 3.32 #1)
	id 15pD2L-000Gks-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 18:15:57 +0000
Date: Thu, 04 Oct 2001 14:15:57 -0400
From: John C Klensin <klensin@jck.com>
To: idn@ops.ietf.org
Subject: RE: [idn] Renaming "AMC-Z"
Message-ID: <17178196.1002204957@P2>
In-Reply-To: <p0510030db7e24dddbe55@[165.227.249.20]>
References:  <p0510030db7e24dddbe55@[165.227.249.20]>
X-Mailer: Mulberry/2.1.0 (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, 04 October, 2001 10:34 -0700 "Paul Hoffman / IMC"
<phoffman@imc.org> wrote:

Martin Duerst wrote...

>>  If we use ACE, quite a bit of the archives of this
>> group will become difficult to read for people who think that
>> ACE is ACM-Z.
> 
> For all three people who read the archive...

Let me say that a little more strongly.    Having spent too much
of my life going back through WG archives trying to figure out
what happened, almost none of them are comprehensible unless one
either reads backwards or understands that terminology and
perceptions about relevance change.  Or, most often, all three.
Remember that we quite often have a group chartered to do a
"foo" protocol and that, as they consider what to do, all sorts
of things are identified as "foo".  Mailing list archives
covering a long period are _always_ "difficult to read";
regardless of whether calling the final result "ACE" is a good
idea, the incremental damage to archive-reading caused by making
that choice is unlikely to be marginally significant.

Also, in the hope of shortening another non-productive thread
(for which neither Paul nor Martin are responsible)...


> ASCII is a standard _encoding_ of characters as bytes: in
> other words, a function from byte strings to character strings.
>...
> ``ASCII'' does not mean ``7-bit.'' It is simply not correct to
> refer to Q-P-style Unicode encodings as ``ASCII compatible.''
> ASCII is not merely a set of numbers; it assigns _characters_
> to those numbers.

"ASCII", as used in the IETF, is quite explicitly X3.4-1968, and
that is, quite explicitly, a seven bit character set.  Sometimes
we say "US-ASCII" to be even more clear but, as far as I know,
every one of the references points to X3.4-1968 and any that
don't are probably errors or sloppy work.

> The correct phrase is ``7-bit compatible.'' The encoded
> strings are compatible with 7-bit channels. That's the point
> of these encodings.

Well, actually, we utilize more of ASCII's rules and definitions
than just the 7 bit restriction.  E.g., we don't permit control
characters in these encodings, and the definition of a "control
character" comes straight from the ASCII spec.  I suppose we
could be really precise and call something an AGCCE (ASCII
graphic character compatible encoding, "graphic character" also
being well-defined in the ASCII spec) or an AISGCE (ASCII
internationally sensitive graphic character compatible
encoding), or its possibly more politically correct equivalents,
IS646BVCE  or IS646BVGCE, since we don't use the national-use
positions in these encodings.  

But I don't know how to pronounce any of those, and don't have
time for this, and suspect that the vast majority of the WG
would prefer useful work and moving IDN forward to having days
or weeks of this debate.

And "7 bit channels" are actually only part of the point.  The
other part has to do with sufficiently unambiguous
representation that the mappings work accurately and
consistently in both directions.  And many things that will go
down a seven bit channel don't have that property.

    john




From owner-idn@ops.ietf.org  Thu Oct  4 20:33:27 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26703
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 20:33:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pIdK-0009h0-00
	for idn-data@psg.com; Thu, 04 Oct 2001 17:14:30 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pIdJ-0009gu-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 17:14:30 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id JAA09830;
	Fri, 5 Oct 2001 09:13:44 +0900
Message-ID: <001e01c14d32$cd35c040$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
References: <20011003.125229.-816135.0.liana.ydisg@juno.com> <01a901c14c77$f393bf50$dd00a8c0@jamessonyvaio> <004c01c14c90$3748bd00$d43f7018@mtag1.on.home.com> <001001c14cd9$31dd85a0$d43f7018@mtag1.on.home.com> <20011004152630.20354.qmail@cr.yp.to> <5.1.0.14.2.20011004092041.03a887f8@dcrocker.net> <20011004165802.17656.qmail@cr.yp.to>
Subject: Re: [idn] 7CE
Date: Fri, 5 Oct 2001 09:14:57 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id UAA26703


----- Original Message ----- 
From: "D. J. Bernstein" <djb@cr.yp.to>
 > 
> As you can easily see from a web search, people consistently and
> correctly refer to 8859-1, KOI-8, UTF-8, etc. as being ASCII-compatible.
 
> The use of ``ASCII'' to mean ``7-bit'' is a silly mistake in some recent
> IETF documents: specifically, RFC 2130 and this group's ``ACE'' garbage.
> Now that the error has been pointed out, it can easily be fixed.
 
I  agree on dropping out "ASCII-compatible".
Rather, I suggest to use "ASCII coded" or "ASCII coding".

As Adam pointed out, it will be useful to have two seperate names for
  "bq--xxxxxx" and its subpart "xxxxxx".

Suggestion: for an unicode label A, the conversion of A into
the "xxxxxx"  is called as BOOTSTRING-646.
 
And the one into "bq--xxxxxx"   is  called  in IDN context  as
  "ACUD" (ASCII Coding of Unicode Domain) or
  "ACUL" (ASCII Coding of Unicode Label ) or
  "UTF-LDH".
 
 
Soobok Lee




From owner-idn@ops.ietf.org  Thu Oct  4 20:57:28 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26868
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 20:57:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pJA9-000B9X-00
	for idn-data@psg.com; Thu, 04 Oct 2001 17:48:25 -0700
Received: from angry.realnames.com ([216.35.85.219])
	by psg.com with smtp (Exim 3.33 #1)
	id 15pJA9-000B9R-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 17:48:25 -0700
Received: (qmail 15104 invoked by uid 104); 5 Oct 2001 00:48:24 -0000
Received: from yves@realnames.com by angry.realnames.com with qmail-scanner-0.96 (. Clean. Processed in 0.945848 secs); 05 Oct 2001 00:48:24 -0000
Received: from heaven.internal.realnames.com (10.1.5.39)
  by angry.realnames.com with SMTP; 5 Oct 2001 00:48:22 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:4091]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <19018@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Thu, 4 Oct 2001 5:45:42 PM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2653.19)
	id <42K7JY1V>; Thu, 4 Oct 2001 17:48:06 -0700
Message-ID: <7FC3066C236FD511BC5900508BAC86FE1E62E5@trestles.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: idn@ops.ietf.org
Subject: RE: [idn] 7CE
Date: Thu, 4 Oct 2001 17:44:57 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-idn@ops.ietf.org
Precedence: bulk

>   "UTF-LDH".

I am strongly against calling UTF-* anything that is not a UTF sanctioned by
the Unicode Consortium. And I am pretty sure they are too (witness the
recent renaming of UTF-8S to CESU-8). I think it would confuse, rather than
help, people. Don't you?

YA



From owner-idn@ops.ietf.org  Thu Oct  4 21:05:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26996
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 21:05:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pJJk-000BdC-00
	for idn-data@psg.com; Thu, 04 Oct 2001 17:58:20 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pJJj-000Bd5-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 17:58:19 -0700
Received: from bbprime.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 RAA18509;
	Thu, 4 Oct 2001 17:58:14 -0700
Message-Id: <5.1.0.14.2.20011004173713.02403308@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 04 Oct 2001 17:58:57 -0700
To: "D. J. Bernstein" <djb@cr.yp.to>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] 7CE
Cc: idn@ops.ietf.org
In-Reply-To: <20011004165802.17656.qmail@cr.yp.to>
References: <20011003.125229.-816135.0.liana.ydisg@juno.com>
 <01a901c14c77$f393bf50$dd00a8c0@jamessonyvaio>
 <004c01c14c90$3748bd00$d43f7018@mtag1.on.home.com>
 <001001c14cd9$31dd85a0$d43f7018@mtag1.on.home.com>
 <20011004152630.20354.qmail@cr.yp.to>
 <5.1.0.14.2.20011004092041.03a887f8@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 09:58 AM 10/4/2001, D. J. Bernstein wrote:
>Dave Crocker writes:
> > 30 years of consistent use tends to carry more weight than a single
> > person's recent desire to impose linguistic changes.
>
>You are making a fool of yourself, Dave.

Gosh.  This is the first time.

For both of us, no doubt.


>The use of ``ASCII'' to mean ``7-bit'' is a silly mistake in some recent
>IETF documents: specifically, RFC 2130 and this group's ``ACE'' garbage.
>Now that the error has been pointed out, it can easily be fixed.

We could, perhaps, have an extended side debate about the relative 
seriousness of making a fool of oneself, versus making a point of 
demonstrating aggressive (and, of course, hostile) ignorance of history.

"We could do it, but it would be wrong."  (Nixon was undervalued as a 
system engineer.)

The Internet use of the terms "ASCII" and "7-bit ASCII" are short-form for 
the complete, 1973 Telnet label of:

         7-bit ASCII
         in an 8-bit field
         with the 8th bit off.

Dick Clark's crew would give it a 9.  You CAN dance to it.  And it shows 
that Internet geeks were into rap long before hip hop came along.

Such short-hand notations are common, convenient, and valid.  Even you use 
them.  It is well understood that when you make ad hominems, whatever words 
you choose really serve as a reflexive shorthand for communicating your own 
insecurities.  Failure to accommodate disagreement has occupies bulky 
tomes.  We do not need to read them.  Your terse ad hominems provide all 
the insight one might otherwise get from extensive reading.

At any rate, Dan, feel free to rail against the weight of linguistic 
convention in this community.  It will be a nice distraction for you, and 
will thereby allowing others to get some real work done.

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 Oct  4 21:06:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27026
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 21:06:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pJLT-000Bhp-00
	for idn-data@psg.com; Thu, 04 Oct 2001 18:00:07 -0700
Received: from imo-m04.mx.aol.com ([64.12.136.7])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pJLS-000Bhj-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 18:00:06 -0700
Received: from DougEwell2@cs.com
	by imo-m04.mx.aol.com (mail_out_v31_r1.7.) id i.112.5a6d412 (4563);
	Thu, 4 Oct 2001 20:59:59 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <112.5a6d412.28ee600f@cs.com>
Date: Thu, 4 Oct 2001 20:59:59 EDT
Subject: Re: [idn] 7CE
To: idn@ops.ietf.org
CC: lsb@postel.co.kr
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a message dated 2001-10-04 17:46:44 Pacific Daylight Time, 
lsb@postel.co.kr writes:

> And the one into "bq--xxxxxx"   is  called  in IDN context  as
>    "ACUD" (ASCII Coding of Unicode Domain) or
>    "ACUL" (ASCII Coding of Unicode Label ) or
>    "UTF-LDH".

Please, not "UTF-" anything.  "UTF" has a very specific meaning in the 
Unicode and ISO/IEC 10646 world, and ACEs (in either sense of the term) 
aren't it.

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Thu Oct  4 21:21:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27106
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 21:21:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pJZO-000CJ5-00
	for idn-data@psg.com; Thu, 04 Oct 2001 18:14:30 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pJZN-000CIz-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 18:14:29 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id KAA28876;
	Fri, 5 Oct 2001 10:14:19 +0900
Message-ID: <003a01c14d3b$3b29f820$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Yves Arrouye" <yves@realnames.com>, <idn@ops.ietf.org>
References: <7FC3066C236FD511BC5900508BAC86FE1E62E5@trestles.internal.realnames.com>
Subject: Re: [idn] 7CE
Date: Fri, 5 Oct 2001 10:15:32 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA27106


----- Original Message ----- 
From: "Yves Arrouye" <yves@realnames.com>
To: <idn@ops.ietf.org>
Sent: Friday, October 05, 2001 9:44 AM
Subject: RE: [idn] 7CE


> >   "UTF-LDH".
> 
> I am strongly against calling UTF-* anything that is not a UTF sanctioned by
> the Unicode Consortium. 

Sure.  I want the Unicode Consortium to approve this useful new transfer encoding format 
as UTF-LDH. But UC is out of control of this WG. That was my point.  :-)


>And I am pretty sure they are too (witness the
> recent renaming of UTF-8S to CESU-8). I think it would confuse, rather than
> help, people. Don't you?
> 
> YA
> 




From owner-idn@ops.ietf.org  Thu Oct  4 22:12:09 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28605
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 22:12:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pK7O-000Dgw-00
	for idn-data@psg.com; Thu, 04 Oct 2001 18:49:38 -0700
Received: from inergen.sybase.com ([192.138.151.43])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pK7N-000Dgq-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 18:49:37 -0700
Received: from smtp2.sybase.com (sybgate2.sybase.com [130.214.69.6])
	by inergen.sybase.com  with ESMTP id SAA15116
	for <idn@ops.ietf.org>; Thu, 4 Oct 2001 18:48:55 -0700 (PDT)
Received: from olympus.sybase.com (localhost [127.0.0.1])
	by smtp2.sybase.com  with ESMTP id SAA20967
	for <idn@ops.ietf.org>; Thu, 4 Oct 2001 18:49:36 -0700 (PDT)
Received: from birdie.sybase.com by olympus.sybase.com (8.8.8+Sun/SMI-SVR4/SybEC3.5)
	id SAA05259; Thu, 4 Oct 2001 18:49:36 -0700 (PDT)
Received: (from kenw@localhost)
	by birdie.sybase.com (8.8.8+Sun/8.8.8) id SAA12288
	for idn@ops.ietf.org; Thu, 4 Oct 2001 18:49:35 -0700 (PDT)
Date: Thu, 4 Oct 2001 18:49:35 -0700 (PDT)
From: Kenneth Whistler <kenw@sybase.com>
Message-Id: <200110050149.SAA12288@birdie.sybase.com>
To: idn@ops.ietf.org
Subject: RE: [idn] 7CE
X-Sun-Charset: US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Yves Arrouye responded to the suggestion:

> >   "UTF-LDH".
> 
> I am strongly against calling UTF-* anything that is not a UTF sanctioned by
> the Unicode Consortium. And I am pretty sure they are too 

I cannot speak for the Unicode Consortium, but speaking as a
technical director of the Unicode Consortium, I would be
virulently opposed to any renaming of any form of an ACE to
"UTF-whatever". Not only would it be confusing, it would also
divert the debate from the technical details of the ACE and its
deployment to a fruitless debate over the confusion itself.

So please, don't start down that road, even in jest.

--Ken



From owner-idn@ops.ietf.org  Thu Oct  4 22:18:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28657
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 22:18:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pKNC-000EJS-00
	for idn-data@psg.com; Thu, 04 Oct 2001 19:05:58 -0700
From: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>
To: IETF idn working group <idn@ops.ietf.org>
Subject: Re: [idn] Renaming "AMC-Z"
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15pKNC-000EJS-00@psg.com>
Date: Thu, 04 Oct 2001 19:05:58 -0700

Martin Duerst <duerst@w3.org> wrote:

> I don't know what the Z in AMC-Z stands for, but it seems to have
> served its purpose well up to now.

AMC-ACE-Z simply means the 26th ACE algorithm designed by AMC.

Perhaps "ACE" should not be an operation/process at all, but rather
a kind of label/name.  For example, we might speak this way:

foobar is not an ACE, but xx--blahblah is an ACE.  The domain name
<Thai-word>.com does not contain any ACE labels, but it has an ACE
form, which is xx--blahblah.com.  In order to construct the ACE form of
a domain label, you need to apply certain operations, like Nameprep,
Bootstring with certain parameters, syntax checking, and prepending a
prefix.

("Bootstring with certain parameters" is what is currently known as
AMC-ACE-Z.)

If we were to take that approach, then the name for "Bootstring with
certain parameters" would not matter so much, because the general public
would seldom have reason to refer to it; they'd usually be speaking
about ACEs.

Here's a summary of the names under consideration:

First, there is ACE and a number of variants (ACE-1, ACE-Z, Z-ACE, etc).
If we go with any of those, I lean toward simply "ACE".

Next, there are a number of other acronyms, none of which I like.

Finally, there are some non-acronyms, all of which have been suggested
by me and which have received no comment:  Bootstring-646, Minicode,
Unimplode.  These names would be appropriate for the current AMC-ACE-Z
parameters, which were chosen to favor Unicode.  If we end up doing
reordering and changing the parameters to favor reordered Unicode, then
those names would not be appropriate for the new parameters.

AMC





From owner-idn@ops.ietf.org  Thu Oct  4 22:37:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29830
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 22:37:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pKj5-000FCm-00
	for idn-data@psg.com; Thu, 04 Oct 2001 19:28:35 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pKj4-000FCf-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 19:28:35 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id LAA19973;
	Fri, 5 Oct 2001 11:28:25 +0900
Message-ID: <006a01c14d45$95102530$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Kenneth Whistler" <kenw@sybase.com>, <idn@ops.ietf.org>
References: <200110050149.SAA12288@birdie.sybase.com>
Subject: Re: [idn] 7CE
Date: Fri, 5 Oct 2001 11:29:38 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id WAA29830


If the UTC embraces ACE and augments it to one of its offical unicode
encoding formats, it will _faciliate_ even future pure text/document 
applications or rendering engines to support ACE-rendering feature 
without their programmers' leaving out UTC standards for IETF ACE encoding details.

I hope UTC folks think about embracing ACE encodings seriously.
The naming for ACE (UTF-??? or ACUD or else) is not so important.

Soobok Lee

----- Original Message ----- 
From: "Kenneth Whistler" <kenw@sybase.com>
To: <idn@ops.ietf.org>
Sent: Friday, October 05, 2001 10:49 AM
Subject: RE: [idn] 7CE


> Yves Arrouye responded to the suggestion:
> 
> > >   "UTF-LDH".
> > 
> > I am strongly against calling UTF-* anything that is not a UTF sanctioned by
> > the Unicode Consortium. And I am pretty sure they are too 
> 
> I cannot speak for the Unicode Consortium, but speaking as a
> technical director of the Unicode Consortium, I would be
> virulently opposed to any renaming of any form of an ACE to
> "UTF-whatever". Not only would it be confusing, it would also
> divert the debate from the technical details of the ACE and its
> deployment to a fruitless debate over the confusion itself.
> 
> So please, don't start down that road, even in jest.
> 
> --Ken
> 




From owner-idn@ops.ietf.org  Thu Oct  4 22:45:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29951
	for <idn-archive@lists.ietf.org>; Thu, 4 Oct 2001 22:45:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pKrS-000FZc-00
	for idn-data@psg.com; Thu, 04 Oct 2001 19:37:14 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pKrQ-000FZW-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 19:37:13 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 16E60FFC1D; Fri,  5 Oct 2001 10:37:51 +0800 (SGT)
Message-ID: <042501c14d46$a0fab940$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Soobok Lee" <lsb@postel.co.kr>, "Kenneth Whistler" <kenw@sybase.com>,
        <idn@ops.ietf.org>
References: <200110050149.SAA12288@birdie.sybase.com> <006a01c14d45$95102530$ec1bd9d2@temp>
Subject: Re: [idn] 7CE
Date: Fri, 5 Oct 2001 10:37:08 +0800
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

Lets not go into the direction of UTF-* naming convention. We are
creating unnecessary confusion for ourselves.

-James Seng

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Kenneth Whistler" <kenw@sybase.com>; <idn@ops.ietf.org>
Sent: Friday, October 05, 2001 10:29 AM
Subject: Re: [idn] 7CE



If the UTC embraces ACE and augments it to one of its offical unicode
encoding formats, it will _faciliate_ even future pure text/document
applications or rendering engines to support ACE-rendering feature
without their programmers' leaving out UTC standards for IETF ACE
encoding details.

I hope UTC folks think about embracing ACE encodings seriously.
The naming for ACE (UTF-??? or ACUD or else) is not so important.

Soobok Lee

----- Original Message -----
From: "Kenneth Whistler" <kenw@sybase.com>
To: <idn@ops.ietf.org>
Sent: Friday, October 05, 2001 10:49 AM
Subject: RE: [idn] 7CE


> Yves Arrouye responded to the suggestion:
>
> > >   "UTF-LDH".
> >
> > I am strongly against calling UTF-* anything that is not a UTF
sanctioned by
> > the Unicode Consortium. And I am pretty sure they are too
>
> I cannot speak for the Unicode Consortium, but speaking as a
> technical director of the Unicode Consortium, I would be
> virulently opposed to any renaming of any form of an ACE to
> "UTF-whatever". Not only would it be confusing, it would also
> divert the debate from the technical details of the ACE and its
> deployment to a fruitless debate over the confusion itself.
>
> So please, don't start down that road, even in jest.
>
> --Ken
>






From owner-idn@ops.ietf.org  Fri Oct  5 00:37:12 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01214
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 00:37:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pMZK-000JpC-00
	for idn-data@psg.com; Thu, 04 Oct 2001 21:26:38 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pMZJ-000Jp6-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 21:26:37 -0700
Received: from [24.252.219.84] (account ehall HELO ferret)
  by goose.ehsco.com (CommuniGate Pro SMTP 3.4.8)
  with ESMTP-TLS id 17099; Wed, 03 Oct 2001 23:26:20 -0500
Message-ID: <003401c14d55$eba17330$0a0aa8c0@labs.ntrg.com>
From: "Eric A. Hall" <ehall@ehsco.com>
To: "Dan Oscarsson" <Dan.Oscarsson@trab.se>, <idn@ops.ietf.org>,
        "Paul Hoffman / IMC" <phoffman@imc.org>
References: <200110040700.f9470bj18628@valinor.malmo.trab.se> <p0510030eb7e24eb9f210@[165.227.249.20]>
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
Date: Thu, 4 Oct 2001 23:26:35 -0500
Organization: EHS Company
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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

From: "Paul Hoffman / IMC" <phoffman@imc.org>
To: "Dan Oscarsson" <Dan.Oscarsson@trab.se>; <idn@ops.ietf.org>
Sent: Thursday, October 04, 2001 12:41 PM
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years


> For the same reasons people have been repeating on this list for the
> past year. UTF-8 is the "native" encoding for a very small number of
> people.

Looking out the rear-view mirror, this is true. Looking out the
front-windshield, this is not true.

> UTF-8 is  almost never the only encoding they have.

It is the best option for getting to an "only encoding". Resistance in this
particular WG actively frustrates progress for everybody.

> Because of that, we need to
> assume that essentially all software that takes in or displays IDNs
> will have to do some conversion before putting the name parts on the
> wire. If we are going to require conversion, it is better to do that
> conversion to something that is already compatible with the current
> DNS protocol.

First of all, support for an UTF-8 encoding means that conversion is NOT
required for apps that generate UTF-8 natively. Secondarily, the DNS protocol
is NOT restricted to US-ASCII.

> Updating all of the DNS servers in the world is an option, but not
> one that makes much sense.

"all of the DNS servers" do not need to be upgraded for UDNS and similar
protocols to function properly. The only servers which need to be upgraded are
those servers where the network admin WANTS to serve IDNs as UTF-8 strings. If
an admin does not want to use UDNS, they can use ACE. We have been through
this many times.

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





From owner-idn@ops.ietf.org  Fri Oct  5 01:02:35 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01419
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 01:02:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pMvS-000KgP-00
	for idn-data@psg.com; Thu, 04 Oct 2001 21:49:30 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pMvR-000KgJ-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 21:49:29 -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 VAA25879;
	Thu, 4 Oct 2001 21:48:21 -0700
Message-Id: <5.1.0.14.2.20011004213749.02478cd0@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 04 Oct 2001 21:48:17 -0700
To: "Eric A. Hall" <ehall@ehsco.com>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
Cc: "Dan Oscarsson" <Dan.Oscarsson@trab.se>, <idn@ops.ietf.org>,
        "Paul Hoffman / IMC" <phoffman@imc.org>
In-Reply-To: <003401c14d55$eba17330$0a0aa8c0@labs.ntrg.com>
References: <200110040700.f9470bj18628@valinor.malmo.trab.se>
 <p0510030eb7e24eb9f210@[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 09:26 PM 10/4/2001, Eric A. Hall wrote:
> > For the same reasons people have been repeating on this list for the
> > past year. UTF-8 is the "native" encoding for a very small number of
> > people.
>
>Looking out the rear-view mirror, this is true. Looking out the
>front-windshield, this is not true.


no doubt your base of experience permits you to speak with such 
certitude.  those of us who have worked on Internet technology for less 
time, say only 20 or 30 years, find that such predictions are usually 
wrong.  sometimes right, but usually wrong.

However, in this case, it does not matter.

The physics of upgrading a large, infrastructure-critical service dictate a 
text-based encoding scheme.  Even better is that the performance (and 
storage) are not affected by the choice between UTF-8 or ACE.

It simply has no effect on significant system performance issues, other 
than transparency to the existing system... if an ACE is used.  UTF-8, on 
the other hand, will nicely break the existing system.

d/

ps.  please remember that "the system" is quite a bit more than the DNS 
servers.

----------
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  Fri Oct  5 02:45:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15217
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 02:45:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pOYz-000OaN-00
	for idn-data@psg.com; Thu, 04 Oct 2001 23:34:25 -0700
Received: from web11104.mail.yahoo.com ([216.136.131.151])
	by psg.com with smtp (Exim 3.33 #1)
	id 15pOYz-000OaH-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 23:34:25 -0700
Message-ID: <20011005063424.12355.qmail@web11104.mail.yahoo.com>
Received: from [203.162.57.81] by web11104.mail.yahoo.com via HTTP; Thu, 04 Oct 2001 23:34:24 PDT
Date: Thu, 4 Oct 2001 23:34:24 -0700 (PDT)
From: pham anh <vietanh1977@yahoo.com>
Subject: [idn] unicode and bind 9
To: idn@ops.ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I wonder at this time, bind 9 support unicode or not.
if now bind 9 doesn't support unicode, in ther future
it will be supported unicode.

is there any way to implement mutillingual domain
without set up a application to convert native
languges to DNS normal charater as iDNS mechanism.

thank you

__________________________________________________
Do You Yahoo!?
NEW from Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1



From owner-idn@ops.ietf.org  Fri Oct  5 02:59:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16054
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 02:59:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pOjp-000P2g-00
	for idn-data@psg.com; Thu, 04 Oct 2001 23:45:37 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pOjo-000P2a-00
	for idn@ops.ietf.org; Thu, 04 Oct 2001 23:45:36 -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 17109; Thu, 04 Oct 2001 01:45:19 -0500
Message-ID: <3BBD570D.AC65A345@ehsco.com>
Date: Fri, 05 Oct 2001 01:45:34 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dave Crocker <dhc@dcrocker.net>
CC: Dan Oscarsson <Dan.Oscarsson@trab.se>, idn@ops.ietf.org,
        Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
References: <200110040700.f9470bj18628@valinor.malmo.trab.se>
	 <p0510030eb7e24eb9f210@[165.227.249.20]> <5.1.0.14.2.20011004213749.02478cd0@dcrocker.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> >Looking out the rear-view mirror, this is true. Looking out the
> >front-windshield, this is not true.
> 
> no doubt your base of experience permits you to speak with such
> certitude.  those of us who have worked on Internet technology for less
> time, say only 20 or 30 years, find that such predictions are usually
> wrong.  sometimes right, but usually wrong.

My "base of experience" gives me an ability to follow current activities
well enough to see that there is more active development for UTF-8 than
any other charset. Do you dispute this? I can infer nothing else from your
comments above.

> The physics of upgrading a large, infrastructure-critical service
> dictate a text-based encoding scheme.

Debating this point requires more context. Certainly IP, BGP and many of
the other "large, infrastructure-critical services" don't rely on
text-based encodings. DNS itself is 8-bit clean, and only uses a
text-based encoding for payload data, and that's only to support the
legacy HOSTS.TXT requirements.

What particular aspect of UTF-8 isn't "text-based" anyway? DNS itself
doesn't even use a text-based encoding (supporting 0x00-0x1F and 0x80-0xFF
natively) by the yardstick you seem to be applying.

> It simply has no effect on significant system performance issues, other
> than transparency to the existing system... if an ACE is used. 

Transparency to users, admins and developers is also important. Think
about ACE in terms of everyday usage scenarios, particularly in markets
and development environments where people are trying to internationalize
their networks and services. The educational and implementation burden of
an ACE-only approach is massive. Worse, it is perpetually massive.

Allowing the users and developers to lower their implementation costs in a
non-disruptive form should be considered as our duty. Preventing it
without reasonable cause is pointless.

> UTF-8, on the other hand, will nicely break the existing system.

Dan J. is not arguing for UTF-8 *ONLY*. That's a non-starter. The UDNS
proposal allows for a dual-mode structure, one of which is ACE for
legacy-systems compatibility, the other of which is a UTF-8 for future
application support. They are COMPLEMENTARY.

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



From owner-idn@ops.ietf.org  Fri Oct  5 03:19:54 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16683
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 03:19:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pP1B-000Pnw-00
	for idn-data@psg.com; Fri, 05 Oct 2001 00:03:33 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pP19-000Pnq-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 00:03:31 -0700
Received: from bbprime.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 AAA29595;
	Fri, 5 Oct 2001 00:03:29 -0700
Message-Id: <5.1.0.14.2.20011004235936.023e1500@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 05 Oct 2001 00:04:06 -0700
To: "Eric A. Hall" <ehall@ehsco.com>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
Cc: idn@ops.ietf.org
In-Reply-To: <3BBD570D.AC65A345@ehsco.com>
References: <200110040700.f9470bj18628@valinor.malmo.trab.se>
 <p0510030eb7e24eb9f210@[165.227.249.20]>
 <5.1.0.14.2.20011004213749.02478cd0@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 11:45 PM 10/4/2001, Eric A. Hall wrote:
>My "base of experience" gives me an ability to follow current activities

It is "following" future events that is difficult.


> > The physics of upgrading a large, infrastructure-critical service
> > dictate a text-based encoding scheme.
>
>Debating this point requires more context. Certainly IP, BGP and many of
>the other "large, infrastructure-critical services" don't rely on
>text-based encodings. DNS itself is 8-bit clean

The topic is the DNS and, apparently, you did not fully appreciate the 
postscript I placed at the end of my previous message.


>What particular aspect of UTF-8 isn't "text-based" anyway?

There is a difference between "octet" and "text".  John K's recent note 
elaborated this point.


> > It simply has no effect on significant system performance issues, other
> > than transparency to the existing system... if an ACE is used.
>
>Transparency to users, admins and developers is also important.

See my previous comment about confusing user interface issues with protocol 
issues.


>Dan J. is not arguing for UTF-8 *ONLY*. That's a non-starter. The UDNS
>proposal allows for a dual-mode structure

When uDNS moves from proposal to specification, the real feasibility and 
tradeoffs associated with it can be debated.  Until then, it is closer to a 
Rorschach test than a basis for technical debate.

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  Fri Oct  5 03:36:00 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16780
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 03:35:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pPKC-0000my-00
	for idn-data@psg.com; Fri, 05 Oct 2001 00:23:12 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pPKB-0000mm-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 00:23:11 -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 17116; Thu, 04 Oct 2001 02:22:50 -0500
Message-ID: <3BBD5FD9.A86229A8@ehsco.com>
Date: Fri, 05 Oct 2001 02:23:05 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dave Crocker <dhc@dcrocker.net>
CC: idn@ops.ietf.org
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
References: <200110040700.f9470bj18628@valinor.malmo.trab.se>
	 <p0510030eb7e24eb9f210@[165.227.249.20]>
	 <5.1.0.14.2.20011004213749.02478cd0@dcrocker.net> <5.1.0.14.2.20011004235936.023e1500@dcrocker.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Dave Crocker wrote:

> >My "base of experience" gives me an ability to follow current
> >activities
> 
> It is "following" future events that is difficult.

Clearly the world wants a UCS. While it is true that nobody can guarantee
that this will be 10646/Unicode, we can all be certain that it absolutely
WON'T be ASCII. What we can also be sure of is that UTF-8 will be the
favored encoding for the future that we can see.

> >Dan J. is not arguing for UTF-8 *ONLY*. That's a non-starter. The UDNS
> >proposal allows for a dual-mode structure
> 
> When uDNS moves from proposal to specification, the real feasibility
> and tradeoffs associated with it can be debated.  Until then, it is
> closer to a Rorschach test than a basis for technical debate.

Hopefully there will be some meritorious debate at that time.

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



From owner-idn@ops.ietf.org  Fri Oct  5 06:26:38 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17953
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 06:26:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pRu3-0007EK-00
	for idn-data@psg.com; Fri, 05 Oct 2001 03:08:23 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pRu2-0007EA-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 03:08: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 f95A6UN14879; Fri, 5 Oct 2001 12:06:30 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.11.4+Sun/TRM-1-KLIENT); Fri, 5 Oct 2001 12:07:15 +0200 (MEST) (MET)
Message-Id: <200110051007.f95A7Fj19601@valinor.malmo.trab.se>
Date: Fri, 5 Oct 2001 12:07:15 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
To: phoffman@imc.org
Cc: idn@ops.ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: zlQu+aM3zdN4Dy+75c2uWw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.5_41 SunOS 5.9 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk


>For the same reasons people have been repeating on this list for the 
>past year. UTF-8 is the "native" encoding for a very small number of 
>people. Further, even for that very small number of people, UTF-8 is 
>almost never the only encoding they have. Because of that, we need to 
>assume that essentially all software that takes in or displays IDNs 
>will have to do some conversion before putting the name parts on the 
>wire. If we are going to require conversion, it is better to do that 
>conversion to something that is already compatible with the current 
>DNS protocol.
>
>Updating all of the DNS servers in the world is an option, but not 
>one that makes much sense.

Well, then we can say goodbye to IPv6, DNSSEC and all other new things.

UTF-8 works fine in todays DNS. The only ones you need to change are the ones
doing authorative lookups.

   Dan




From owner-idn@ops.ietf.org  Fri Oct  5 10:23:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22922
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 10:23:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pVVm-000GH5-00
	for idn-data@psg.com; Fri, 05 Oct 2001 06:59:34 -0700
Received: from imo-d05.mx.aol.com ([205.188.157.37])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pVVl-000GGx-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 06:59:33 -0700
Received: from DougEwell2@cs.com
	by imo-d05.mx.aol.com (mail_out_v31_r1.7.) id i.79.1c15b66d (4199);
	Fri, 5 Oct 2001 09:59:29 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <79.1c15b66d.28ef16c0@cs.com>
Date: Fri, 5 Oct 2001 09:59:28 EDT
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
To: idn@ops.ietf.org
CC: ehall@ehsco.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a message dated 2001-10-05 0:39:39 Pacific Daylight Time, ehall@ehsco.com 
writes:

>  Clearly the world wants a UCS. While it is true that nobody can guarantee
>  that this will be 10646/Unicode, we can all be certain that it absolutely
>  WON'T be ASCII. What we can also be sure of is that UTF-8 will be the
>  favored encoding for the future that we can see.

You can't be sure about UTF-8 unless you can guarantee 10646/Unicode.  UTF-8 
doesn't exist outside of Unicode.  Or perhaps I misunderstood Eric's 
statement.

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Fri Oct  5 10:31:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23117
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 10:31:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pVlr-000Gye-00
	for idn-data@psg.com; Fri, 05 Oct 2001 07:16:11 -0700
Received: from shell.nominum.com ([128.177.192.160])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pVlq-000GyX-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 07:16:11 -0700
Received: from drc-toshiba.nominum.com (shell.nominum.com [128.177.192.160])
	by shell.nominum.com (Postfix) with ESMTP
	id 8F60E3190C; Fri,  5 Oct 2001 07:16:02 -0700 (PDT)
Message-Id: <5.0.2.1.2.20011005071100.020c5528@localhost>
X-Sender: drc@localhost
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Fri, 05 Oct 2001 07:15:58 -0700
To: pham anh <vietanh1977@yahoo.com>, idn@ops.ietf.org
From: "David R. Conrad" <david.conrad@nominum.com>
Subject: Re: [idn] unicode and bind 9
In-Reply-To: <20011005063424.12355.qmail@web11104.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

BIND 9 is 8-bit clean.  Other than that, it doesn't do anything special to 
deal (or not deal) with Unicode.

Rgds,
-drc

At 11:34 PM 10/4/2001 -0700, pham anh wrote:
>I wonder at this time, bind 9 support unicode or not.
>if now bind 9 doesn't support unicode, in ther future
>it will be supported unicode.
>
>is there any way to implement mutillingual domain
>without set up a application to convert native
>languges to DNS normal charater as iDNS mechanism.
>
>thank you
>
>__________________________________________________
>Do You Yahoo!?
>NEW from Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
>http://geocities.yahoo.com/ps/info1




From owner-idn@ops.ietf.org  Fri Oct  5 14:34:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28235
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 14:34:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pZVO-00016U-00
	for idn-data@psg.com; Fri, 05 Oct 2001 11:15:26 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pZVN-00016O-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 11:15:25 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VV0XjjTkh4BneHq36BKjkOEw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GGZP8HRN; Fri, 05 Oct 2001 14:14:15 EDT
To: vietanh1977@yahoo.com
Cc: idn@ops.ietf.org
Date: Fri, 5 Oct 2001 10:59:19 -0700
Subject: Re: [idn] unicode and bind 9
Message-ID: <20011005.113417.-829693.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-6,8-24
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  idn-map proposal is good to accommodate
vietnamese in a local server.  Could you please 
read draft-liana-idn-map-00 and give some 
thought about it?

Liana

On Thu, 4 Oct 2001 23:34:24 -0700 (PDT) pham anh <vietanh1977@yahoo.com>
writes:
> I wonder at this time, bind 9 support unicode or not.
> if now bind 9 doesn't support unicode, in ther future
> it will be supported unicode.
> 
> is there any way to implement mutillingual domain
> without set up a application to convert native
> languges to DNS normal charater as iDNS mechanism.
> 
> thank you
> 
> __________________________________________________
> Do You Yahoo!?
> NEW from Yahoo! GeoCities - quick and easy web site hosting, just 
> $8.95/month.
> http://geocities.yahoo.com/ps/info1
> 



From owner-idn@ops.ietf.org  Fri Oct  5 14:37:01 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28261
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 14:37:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pZZB-0001Jq-00
	for idn-data@psg.com; Fri, 05 Oct 2001 11:19:21 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pZZA-00016O-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 11:19:20 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VV0XjjTkh4BnfQclfY+So/Rg==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GGZP8HWB; Fri, 05 Oct 2001 14:14:15 EDT
To: Dan.Oscarsson@trab.se
Cc: idn@ops.ietf.org
Date: Fri, 5 Oct 2001 11:32:53 -0700
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
Message-ID: <20011005.113418.-829693.2.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-82
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 just wander, is idn-map proposal will be a good 
structure to accommodate ISO-8859 as a local standard?  
Since CJK servers are all have their own local standards
 and applicantions, which can obtain direct access to 
map-nameprep or  idn-map on a local server without 
changing applicantions. idn-map proposal is described
in draft-liana-idn-map-00.

Liana

On Thu, 4 Oct 2001 09:00:37 +0200 (MEST) Dan Oscarsson
<Dan.Oscarsson@trab.se> writes:
> As the IDN list have been only focused on ACE and are now removing 
> the
> proposals that support IDN nativly in the DNS protocol, I fear that
> I will not be able to use non-ascii domain names for the next 10 
> years.
> 
> To understand why, you have to look at how domain names are used on 
> your
> computer systems.
> When I look at mine, I enter or handle domain/host names in many 
> places,
> for example: host-files, logs, web pages, text documents and 
> databases.
> In all these places the names are using my systems local native 
> character set.
> All programs handle that.
> To use non-ascii names, the only acceptable way to do it is to enter 
> them
> natively in all places. Natively does not mean ACEencoded names, it 
> means
> using the native character set. My web pages will never containg ACE 
> in
> URLs, they will containg ISO 8859-1 characters just like the rest of
> my web pages. My host files may not contain ACE, the must use ISO 
> 8859-1.
> To use ACE-encoded host names can never be an application specific 
> modification.
> The only viable way to do it is to convert all names when they leav 
> the
> DNS protocol into local character set. Under Unix this could be done
> in the resolver libraries so that applications never need to know 
> the
> protocol used over DNS.
> To allow mixed usage of ACE-encoded and native names will result in 
> a
> terrible mess. The only usable way is for all names to be nativly 
> encoded
> within a system. 
> 
> The current groups wanting ACE-encoded names do not take this into
> consideration. At least I have seen no discussions about it.
> 
> As all ACE-encoded names need to be decoded into native names when
> entering a system, why not use UTF-8 over the wire to support 
> simpler
> handling of names?
> There are two places where ACE-encoded names are needed:
> 1) When talking to ancient systems.
> 2) When not being able to represent an UCS name using the local 
> native
>    character set.
> But in all other cases UTF-8 will do and will result for systems
> using UTF-8 natively that they can use dns names without any
> convertion. This will never happen with ACE, no system will ever
> use ACE-encoded text as native character set.
> 
> So forget about quick use of non-ASCII names because of ACE. As long 
> as my
> applications cannot accept a native name or an UTF-8 name, non-ASCII
> names cannot be used. I am not going to expose my users to the
> mess and confusion that ACE-encoded names will result in.
> 
> When I can register a domain name using non-ASCII characters and can
> query and get it returned in UTF-8 or ISO 8859-1, and my system stop
> rejecting names because they conatin non-ASCII characters, then I 
> can
> start using IDNs.
> 
>     Dan
> 
> 



From owner-idn@ops.ietf.org  Fri Oct  5 17:09:06 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01599
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 17:09:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pbjx-0007HV-00
	for idn-data@psg.com; Fri, 05 Oct 2001 13:38:37 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pbjw-0007HN-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 13:38:36 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VVVFTUPKNzUyfHOPT0NqonYA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GGZYFWCL; Fri, 05 Oct 2001 16:38:06 EDT
To: jseng@pobox.org.sg
Cc: idn@ops.ietf.org
Date: Fri, 5 Oct 2001 13:58:06 -0700
Subject: Re: [idn] WG Update
Message-ID: <20011005.135811.-829693.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-1,3-107
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



On Thu, 4 Oct 2001 09:50:15 +0800 "James Seng/Personal"
<jseng@pobox.org.sg> writes:
> In the last London meeting, there are still some outstanding issues
> which we agreed to bring it back to the mailing list to discuss.
> 
> First, the issue of nameprep. nameprep have been renamed to 
> stringprep
> and the new draft is available few days ago. Please review
> draft-ietf-idn-nameprep-06.txt.
> 
> And related to nameprep are the jpchar, hanguelchar and tsconv 
> drafts.
> The authors should get together to consider an architecture 
> document.
> We should set a deadline for this to be concluded, probably sometime
> before Salt Lake meeting.
> 
> This architecture document should take into consideration of:
> a. the recommendation from the Unicode Consortium to the WG dated 
> 02Sept
> b. the source and stablity of the referenced work/codepoints
> 

I disagree Unicode Consortium to the WG dated 02Sept 
recommendation.  

Unicode has been very effective to collect scripts and glyphs
of all scripts, and even comes up with Unified CJK character
set, which is essential for IDN implementation.  I call this  
 the FIRST level of look-alike equivalence.  This equivalence
includes subset of secode level equivalency - semantics.  
However, it can not be very effective for dealing with large sets
 of SECOND level semantics, or usage-alike equivalence 
due to mear size in term of UCS space, but it is okay for 
smaller scripts such as Latin scripts. 

The nameprep is a place to take Unicode work and builds
onto it, not simply repeats it. 
 
Unicode can specify look-alike code points within a script 
but not cross scripts, IDN needs to do it;
Unicode can specify usage-alike code points within Latin
 as case mapping, but not for CJK, IDN needs to do it;
Unicode can provide all the glyphs available, but  can not 
provide effective access for large character set without 
some effective access support, for example on CJK 
character set, IDN needs to do it, and nameprep is the 
 place to start on it. 

> (Personally, I would strongly recommend that nameprep remains as it 
> is
> and the rest of the "localization" to be deal at a different level,
> either at the input method or below at the zone file.)
> 

Obviously, I disagree on " nameprep remain as is", since
Nameprep only dealing with Latin languages, it even includes
 code points form UCS Plane 1, resulted into 9 to 1 case
 mapping, which against John's earlier recommendation 
 to limit IDN mapping to Plane 0,  while Chinese TC/SC 
  mostly 1 to 1 mapping and a few are 3 to 1 mapping,
why do they have to be treated differently in nameprep? 

 If nameprep remains as it is, the other languages but 
Latin, Greek, Cyrillic and Armenian, have to go through
 another level of filtering.  This creates not only fair treatment
 issue, but also posts look-alike character consistency 
 treatment problem.  

Within the current nameprep spec first, take Armenian letter 
"n", which is identical to Latin "n", they are identical, but 
we don't have a way to treat this cross scripted look-alike
in nameprep flat mapping.

If we treate this Armenian case in two levels, how shall we 
do it?  Are there any differences the user will see? 


> Secondly, there is a reordering draft draft-ietf-idn-lsb-ace. We 
> have
> already seen some results on reordering but we have not seen much
> discussion on the downside of reordering. In anycase, we would like
> to encourage further discussion on reordering draft as we would like
> to conduct a strawpoll on the draft soon.
> 

In my opinion, draft-ietf-idn-lsb-ace plays a role that can not be 
clearly understood without the IDN architecture is clearly 
defined.  What is the user locality on UCS usage?
1) Language tagged mechanism, covers strong locality users,
 for example, Chinese, Japanese.  There are no proposals 
 reflecting how the Indic languages, Hebrew and Arabic
 languages shall  be handled yet.  Are there any strong local
  standards installed  and data for references?  It seems 
 ISO-8859 users has  voiced something, but no specifics.
2) The scattered script use can be handled by AMC, whatever 
 the name is. 
 
If we use option 2), there are clear benefit for some users, 
but it is worth the extra complexity for all, including Latin?

If we use option 1), then do we divide the UCS in script groups
as they are mentioned in idn-map proposal or not? If we do,
then there is place for localized compression scheme which 
will not effect users who do not need it. 

Liana



From owner-idn@ops.ietf.org  Fri Oct  5 18:22:01 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03099
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 18:21:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pdCd-000B1K-00
	for idn-data@psg.com; Fri, 05 Oct 2001 15:12:19 -0700
Received: from inergen.sybase.com ([192.138.151.43])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pdCc-000B1C-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 15:12:18 -0700
Received: from smtp2.sybase.com (sybgate2.sybase.com [130.214.69.6])
	by inergen.sybase.com  with ESMTP id PAA29836;
	Fri, 5 Oct 2001 15:11:35 -0700 (PDT)
Received: from olympus.sybase.com (localhost [127.0.0.1])
	by smtp2.sybase.com  with ESMTP id PAA23946;
	Fri, 5 Oct 2001 15:12:17 -0700 (PDT)
Received: from birdie.sybase.com by olympus.sybase.com (8.8.8+Sun/SMI-SVR4/SybEC3.5)
	id PAA01307; Fri, 5 Oct 2001 15:12:16 -0700 (PDT)
Received: (from kenw@localhost)
	by birdie.sybase.com (8.8.8+Sun/8.8.8) id PAA12435;
	Fri, 5 Oct 2001 15:12:15 -0700 (PDT)
Date: Fri, 5 Oct 2001 15:12:15 -0700 (PDT)
From: Kenneth Whistler <kenw@sybase.com>
Message-Id: <200110052212.PAA12435@birdie.sybase.com>
To: liana.ydisg@juno.com
Subject: Re: [idn] WG Update
Cc: idn@ops.ietf.org
X-Sun-Charset: US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Liana said:

>  If nameprep remains as it is, the other languages but 
> Latin, Greek, Cyrillic and Armenian,

These are not *languages* but *scripts*. 

> have to go through
>  another level of filtering.  This creates not only fair treatment
>  issue,

Huh? Are you suggesting that it is unfair that other scripts
which don't have case differences don't have to have those
nonexistent case differences folded together? Are you suggesting,
say, that Hebrew should introduce case differences so they can
be fairly folded away? Or that if Latin, Greek, Cyrillic,
and Armenian get to fold away their case differences that
users of every other script should be given a chance to fold
*some* distinction away, to be "fair", even if the distinction
in question has nothing to do with the domain name case folding
that is being grandfathered in for backwards compatibility?

> but also posts look-alike character consistency 
>  treatment problem.

On what basis do you make this claim?
  
> 
> Within the current nameprep spec first, take Armenian letter 
> "n", 

There is no Armenian letter "n". There is an Armenian letter NOW
for the /n/ sound...

> which is identical to Latin "n", they are identical, 

...but it is not identical to Latin "n". What are you going
on about?

> but 
> we don't have a way to treat this cross scripted look-alike
> in nameprep flat mapping.

It isn't a look-alike in the first place.

> 
> If we treate this Armenian case in two levels, how shall we 
> do it?  Are there any differences the user will see? 

Yes. Armenian is visually completely distinct from Latin.
That is obvious.

--Ken




From owner-idn@ops.ietf.org  Fri Oct  5 18:56:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03461
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 18:56:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pdgw-000BZ8-00
	for idn-data@psg.com; Fri, 05 Oct 2001 15:43:38 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pdgv-000BYz-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 15:43:37 -0700
Received: from bbprime.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 PAA27704;
	Fri, 5 Oct 2001 15:43:34 -0700
Message-Id: <5.1.0.14.2.20011005141903.04649150@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 05 Oct 2001 15:43:39 -0700
To: "Eric A. Hall" <ehall@ehsco.com>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
Cc: idn@ops.ietf.org
In-Reply-To: <3BBD5FD9.A86229A8@ehsco.com>
References: <200110040700.f9470bj18628@valinor.malmo.trab.se>
 <p0510030eb7e24eb9f210@[165.227.249.20]>
 <5.1.0.14.2.20011004213749.02478cd0@dcrocker.net>
 <5.1.0.14.2.20011004235936.023e1500@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 12:23 AM 10/5/2001, Eric A. Hall wrote:
>Clearly the world wants a UCS. While it is true that nobody can guarantee
>that this will be 10646/Unicode,

the world wants world peace.

such motivation is useful, but not sufficient, for achieving the desired goal.


>we can all be certain that it absolutely
>WON'T be ASCII. What we can also be sure of is that UTF-8 will be the
>favored encoding for the future that we can see.

what you seem to be missing is an appreciation of how often that phenomenon 
has occurred, yet proved wrong.


> > When uDNS moves from proposal to specification, the real feasibility
> > and tradeoffs associated with it can be debated.  Until then, it is
> > closer to a Rorschach test than a basis for technical debate.
>
>Hopefully there will be some meritorious debate at that time.

that would be nice.  the current, meretricious debate is wearing thin.

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  Fri Oct  5 19:32:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03851
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 19:32:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15peGc-000Cq0-00
	for idn-data@psg.com; Fri, 05 Oct 2001 16:20:30 -0700
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15peGb-000Cpt-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 16:20:29 -0700
Received: from zetnet.co.uk (man-s233.dialup.zetnet.co.uk [194.247.45.104])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f95NKJX01919;
	Sat, 6 Oct 2001 00:20:19 +0100
Message-ID: <3BBD92BF.B3ECECA7@zetnet.co.uk>
Date: Fri, 05 Oct 2001 12:00: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: DougEwell2@cs.com, idn@ops.ietf.org
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
References: <79.1c15b66d.28ef16c0@cs.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-----

DougEwell2@cs.com wrote:
> In a message dated 2001-10-05 0:39:39 Pacific Daylight Time, ehall@ehsco.com
> writes:
> 
> >  Clearly the world wants a UCS. While it is true that nobody can guarantee
> >  that this will be 10646/Unicode, we can all be certain that it absolutely
> >  WON'T be ASCII. What we can also be sure of is that UTF-8 will be the
> >  favored encoding for the future that we can see.
> 
> You can't be sure about UTF-8 unless you can guarantee 10646/Unicode.

ACE also relies on 10646/Unicode, so any speculation about hypothetical
UCSs other than 10646/Unicode isn't relevant to the arguments about the
merits of ACE and/or UTF-8.

It's perfectly clear that UTF-8 is the favoured charset for both new
IETF protocols and revisions of existing IETF protocols: [BCP18] says so,
and [BCP18] has widespread support among designers and implementors.
If anyone seriously disputes this, they must not be looking at the same
Internet that the rest of us are looking at.


[BCP18] IETF Policy on Character Sets and Languages. H. Alvestrand.
        January 1998. Also RFC2277.

- -- 
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

iQEVAwUBO72R6jkCAxeYt5gVAQErggf/aN04/J0qbzCQlGSSinNPUU0L+jApiOeu
l0wIf8b0zdOu3RdzerlSnG0YzE/RE3jmPnpsN2bCLJFzElggZRzS7Hn8HwA1qpyy
N3UNuRoWSAa8ezLpv5AFwhCpPz1o4NJOL5xzQNgt8vkXtJ5BtpVVjN+sBGQ19rtx
PV/QY7iuy62T2KQjg9C4jcf/S4U1kEYs9WGYCOwZEntUnQWtSTz4+heTGSFwdYI7
o8rhO5hlH05oknIanpooSlkDjmHy7bvqA9g8Uq+EIIWdN+btzJ4Otvdo3w2zpVdI
Jy9SopNM9EOk0NulM1HUjNLF6XLNcayrP+tBdwBWi6g2ur3+PkZQNg==
=zwNP
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Fri Oct  5 20:01:04 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04034
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 20:01:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pegR-000E0z-00
	for idn-data@psg.com; Fri, 05 Oct 2001 16:47:11 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pegQ-000E0j-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 16:47:10 -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 17235; Thu, 04 Oct 2001 18:46:54 -0500
Message-ID: <3BBE467C.A9797B21@ehsco.com>
Date: Fri, 05 Oct 2001 18:47:08 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dave Crocker <dhc@dcrocker.net>
CC: idn@ops.ietf.org
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
References: <200110040700.f9470bj18628@valinor.malmo.trab.se>
	 <p0510030eb7e24eb9f210@[165.227.249.20]>
	 <5.1.0.14.2.20011004213749.02478cd0@dcrocker.net>
	 <5.1.0.14.2.20011004235936.023e1500@dcrocker.net> <5.1.0.14.2.20011005141903.04649150@dcrocker.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Dave Crocker wrote:

> >WON'T be ASCII. What we can also be sure of is that UTF-8 will be the
> >favored encoding for the future that we can see.
> 
> what you seem to be missing is an appreciation of how often that
> phenomenon has occurred, yet proved wrong.

My statement is supported. What I am seeing is policy direction such as
RFC2130, the protocols and formatting specifications under development
which are implementing UTF-8 as the preferred or only encoding, and the
number of platforms which are implementing UTF-8. Items 2 and 3 in
particular illustrate that UTF-8 is and will be (for the "foreseeable
future" anyway) the favored encoding for new Internet protocols (and even
for new implementations, to the extent where other charsets are only
provided as subsets of 10646/Unicode).

I'm certainly willing to change my position if you can provide evidence
that all of the above is just a bad expirement, and that NEW protocols are
in fact favoring some other encoding instead of UTF-8. Got any?

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



From owner-idn@ops.ietf.org  Fri Oct  5 20:52:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04699
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 20:52:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pfPA-000G2V-00
	for idn-data@psg.com; Fri, 05 Oct 2001 17:33:24 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pfP9-000G2P-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 17:33:23 -0700
Received: from [165.227.249.20] (165-227-249-20.client.dsl.net [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f960XJD20799
	for <idn@ops.ietf.org>; Fri, 5 Oct 2001 17:33:19 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0510033ab7e3fc24f02c@[165.227.249.20]>
In-Reply-To: <3BBE467C.A9797B21@ehsco.com>
References: <200110040700.f9470bj18628@valinor.malmo.trab.se>	
 <p0510030eb7e24eb9f210@[165.227.249.20]>	
 <5.1.0.14.2.20011004213749.02478cd0@dcrocker.net>	
 <5.1.0.14.2.20011004235936.023e1500@dcrocker.net>
 <5.1.0.14.2.20011005141903.04649150@dcrocker.net>
 <3BBE467C.A9797B21@ehsco.com>
Date: Fri, 5 Oct 2001 17:32:57 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 6:47 PM -0500 10/5/01, Eric A. Hall wrote:
>My statement is supported. What I am seeing is policy direction such as
>RFC2130, the protocols and formatting specifications under development
>which are implementing UTF-8 as the preferred or only encoding, and the
>number of platforms which are implementing UTF-8.

Every specification with a "preferred" encoding has one or more 
non-preferred encodings. Saying that UTF-8 is preferred is correct 
and irrelevant. As long as there are many popular protocols with lots 
of encoding choices, picking one of those choices for the wire format 
doesn't help any protocol except those that use that one encoding. 
Look at the popular protocols: they are almost all multi-encoding. 
Picking UTF-8 won't help any of them.

Further, remember that UDNS requires that the UTF-8 sent to the DNS 
be marked specially. The cost of adding code for a new encoding for 
DNS (ACE) and adding code for a new way of doing DNS (UDNS) is 
similar. The coder needs to think about one or the other, and both 
will be a small chunk of code.

>  Items 2 and 3 in
>particular illustrate that UTF-8 is and will be (for the "foreseeable
>future" anyway) the favored encoding for new Internet protocols (and even
>for new implementations, to the extent where other charsets are only
>provided as subsets of 10646/Unicode).

True, and irrelevant.

>I'm certainly willing to change my position if you can provide evidence
>that all of the above is just a bad expirement, and that NEW protocols are
>in fact favoring some other encoding instead of UTF-8.

Then you won't change your position, even when faced with other 
better arguments about why UDNS won't work. Let's try those again:

- UDNS causes some strings that are legal in one encoding to be 
illegal in the other, and vice versa, meaning that some host names 
will be illegal part of the time, unpredictably

- UDNS requires more work to be done by authoritative DNS servers

- UDNS UTF-8 queries that fail will cause more load on the DNS

- UDNS is not compatible with DNS security

- UDNS requires that applications have the logic to send a new DNS query format

- Applications that implement the UTF-8 part of UDNS have to handle 
the inevitable errors that come from queries that bounce, have to 
recast those queries in ACE (assuming that the name is even legal in 
ACE, which some won't be), and then have to emit those queries again, 
causing more DNS traffic

- The errors caused by UTF-8 queries are the same as other legitimate 
DNS errors, meaning that applications will have to have their own 
(probably-nonstandard) logic for differentiating between expected 
errors and real errors

UDNS gives us all of these problems for the limited benefit that some 
applications don't have to implement one additional encoding for 
sending host names on the wire. Does that seem like a good balance?

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Fri Oct  5 23:16:12 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08086
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 23:16:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15phTM-000KzV-00
	for idn-data@psg.com; Fri, 05 Oct 2001 19:45:52 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15phTL-000KzO-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 19:45:51 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VV+kj31iUXJRd36Vp/cfD6Gw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GG2MGRMV; Fri, 05 Oct 2001 22:45:34 EDT
To: James@Seng.cc
Cc: bill@mail.nic.nu, liana.ydisg@juno.com, idn@ops.ietf.org
Date: Fri, 5 Oct 2001 20:05:31 -0700
Subject: Re: [idn] Is The IDN WGroup Still Active? Fwd: [IDNList] Registrar
Message-ID: <20011005.200540.-715373.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, James:
  Where is the nameprep-08, do you mean nameprep-06?

Liana

> 
> See nameprep-08. it is discussed extensively how to deal with
> this situation.
>  



From owner-idn@ops.ietf.org  Fri Oct  5 23:16:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08097
	for <idn-archive@lists.ietf.org>; Fri, 5 Oct 2001 23:16:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15phcz-000LL0-00
	for idn-data@psg.com; Fri, 05 Oct 2001 19:55:49 -0700
Received: from angry.realnames.com ([216.35.85.219])
	by psg.com with smtp (Exim 3.33 #1)
	id 15phcy-000LKs-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 19:55:48 -0700
Received: (qmail 21926 invoked by uid 104); 6 Oct 2001 02:55:47 -0000
Received: from yves@realnames.com by angry.realnames.com with qmail-scanner-0.96 (. Clean. Processed in 0.938295 secs); 06 Oct 2001 02:55:47 -0000
Received: from heaven.internal.realnames.com (10.1.5.39)
  by angry.realnames.com with SMTP; 6 Oct 2001 02:55:46 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:4135]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <23408@heaven.internal.realnames.com>
	 for <jseng@pobox.org.sg>; Fri, 5 Oct 2001 7:52:49 PM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2653.19)
	id <42K7J74Y>; Fri, 5 Oct 2001 19:55:15 -0700
Message-ID: <7FC3066C236FD511BC5900508BAC86FE1E62FF@trestles.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: "'liana.ydisg@juno.com'" <liana.ydisg@juno.com>, jseng@pobox.org.sg
Cc: idn@ops.ietf.org
Subject: RE: [idn] WG Update
Date: Fri, 5 Oct 2001 19:52:11 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> I disagree Unicode Consortium to the WG dated 02Sept
> recommendation.
> 
> Unicode has been very effective to collect scripts and glyphs
> of all scripts, and even comes up with Unified CJK character
> set, which is essential for IDN implementation.  I call this
>  the FIRST level of look-alike equivalence.

Unicode does not collect glyphs but characters (and cf. section 2.1 of UTR
#17, http://www.unicode.org/unicode/reports/tr17/). This is a fundamental
property of the Unicode standard. I am everything but a CJK expert, but
along the same idea, the Han characters were unified because they meant the
same thing (semantics) not because of glyph similarities.

YA




From owner-idn@ops.ietf.org  Sat Oct  6 00:30:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08907
	for <idn-archive@lists.ietf.org>; Sat, 6 Oct 2001 00:30:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15piun-000O63-00
	for idn-data@psg.com; Fri, 05 Oct 2001 21:18:17 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pium-000O5x-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 21:18:16 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 5B729FFC10; Sat,  6 Oct 2001 12:18:50 +0800 (SGT)
Message-ID: <017101c14e1d$e865d350$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <liana.ydisg@juno.com>
Cc: <bill@mail.nic.nu>, <liana.ydisg@juno.com>, <idn@ops.ietf.org>
References: <20011005.200540.-715373.0.liana.ydisg@juno.com>
Subject: Re: [idn] Is The IDN WGroup Still Active? Fwd: [IDNList] Registrar
Date: Sat, 6 Oct 2001 12:18:09 +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

Yes, I meant -06. Apologise for the typo.

-James Seng

----- Original Message -----
From: <liana.ydisg@juno.com>
To: <James@Seng.cc>
Cc: <bill@mail.nic.nu>; <liana.ydisg@juno.com>; <idn@ops.ietf.org>
Sent: Saturday, October 06, 2001 11:05 AM
Subject: Re: [idn] Is The IDN WGroup Still Active? Fwd: [IDNList]
Registrar


> Hi, James:
>   Where is the nameprep-08, do you mean nameprep-06?
>
> Liana
>
> >
> > See nameprep-08. it is discussed extensively how to deal with
> > this situation.
> >




From owner-idn@ops.ietf.org  Sat Oct  6 00:42:56 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09010
	for <idn-archive@lists.ietf.org>; Sat, 6 Oct 2001 00:42:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pizt-000OGO-00
	for idn-data@psg.com; Fri, 05 Oct 2001 21:23:33 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pizs-000OGI-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 21:23:32 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 6AF27FFC10; Sat,  6 Oct 2001 12:24:09 +0800 (SGT)
Message-ID: <017901c14e1e$a68dc9a0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Yves Arrouye" <yves@realnames.com>, <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>
References: <7FC3066C236FD511BC5900508BAC86FE1E62FF@trestles.internal.realnames.com>
Subject: Re: [idn] WG Update
Date: Sat, 6 Oct 2001 12:23:29 +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

> Unicode does not collect glyphs but characters (and cf. section 2.1 of
UTR
> #17, http://www.unicode.org/unicode/reports/tr17/). This is a
fundamental
> property of the Unicode standard. I am everything but a CJK expert,
but
> along the same idea, the Han characters were unified because they
meant the
> same thing (semantics) not because of glyph similarities.

erm, no. "meant the same thing" is not the right phrase for how CJK
unification works. The right answer is discussed in Section 2.2 (Unicode
Design Principle) of The Unicode Standard v3.0.

Anyhow, this thread does not belong IDN wg. Lets not get into this.

-James Seng




From owner-idn@ops.ietf.org  Sat Oct  6 01:19:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10102
	for <idn-archive@lists.ietf.org>; Sat, 6 Oct 2001 01:19:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pjcc-000Pcn-00
	for idn-data@psg.com; Fri, 05 Oct 2001 22:03:34 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pjcb-000PcY-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 22:03:34 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VV7nBXEbGq7IRX9/Zm7ndaHA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GG2VCLUE; Sat, 06 Oct 2001 01:03:06 EDT
To: kenw@sybase.com
Cc: liana.ydisg@juno.com, idn@ops.ietf.org
Date: Fri, 5 Oct 2001 21:55:55 -0700
Subject: Re: [idn] WG Update
Message-ID: <20011005.222310.-715373.2.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-1,3-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



On Fri, 5 Oct 2001 15:12:15 -0700 (PDT) Kenneth Whistler
<kenw@sybase.com> writes:
> Liana said:
> 
> >  If nameprep remains as it is, the other languages but 
> > Latin, Greek, Cyrillic and Armenian,
> 
> These are not *languages* but *scripts*. 
> 
> > have to go through
> >  another level of filtering.  This creates not only fair treatment
> >  issue,
> 
> Huh? Are you suggesting that it is unfair that other scripts
> which don't have case differences don't have to have those
> nonexistent case differences folded together? Are you suggesting,
> say, that Hebrew should introduce case differences so they can
> be fairly folded away? Or that if Latin, Greek, Cyrillic,
> and Armenian get to fold away their case differences that
> users of every other script should be given a chance to fold
> *some* distinction away, to be "fair", even if the distinction
> in question has nothing to do with the domain name case folding
> that is being grandfathered in for backwards compatibility?
> 
> > but also posts look-alike character consistency 
> >  treatment problem.
> 
> On what basis do you make this claim?
>
I am giving an example down here:
   
> > 
> > Within the current nameprep spec first, take Armenian letter 
> > "n", 
> 
> There is no Armenian letter "n". There is an Armenian letter NOW
> for the /n/ sound...
> 
> > which is identical to Latin "n", they are identical, 
> 
> ...but it is not identical to Latin "n". What are you going
> on about?
> 
> > but 
> > we don't have a way to treat this cross scripted look-alike
> > in nameprep flat mapping.
> 
> It isn't a look-alike in the first place.
> 

Please check U+0570 U+0578 U+057d U+0581 U+0584
 U+0585

Can you say these do not look like Latin letters? 

> > 
> > If we treate this Armenian case in two levels, how shall we 
> > do it?  Are there any differences the user will see? 
> 
> Yes. Armenian is visually completely distinct from Latin.
> That is obvious.
> 
> --Ken
> 
Then could you please try to think how should we do 
this as two different scripts?  

Liana



From owner-idn@ops.ietf.org  Sat Oct  6 01:20:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10190
	for <idn-archive@lists.ietf.org>; Sat, 6 Oct 2001 01:20:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pjca-000Pcf-00
	for idn-data@psg.com; Fri, 05 Oct 2001 22:03:32 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pjcZ-000PcY-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 22:03:32 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VV7nBXEbGq7ITNLMYTL9eZvA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GG2VCLVD; Sat, 06 Oct 2001 01:03:06 EDT
To: yves@realnames.com
Cc: liana.ydisg@juno.com, jseng@pobox.org.sg, idn@ops.ietf.org
Date: Fri, 5 Oct 2001 22:23:08 -0700
Subject: Re: [idn] WG Update
Message-ID: <20011005.222310.-715373.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-8,10-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

You are correct on what you have said here.  But
what I have said is correct too.  TC/SC mapping 
are examples of semantic equivalence and 
Unicode has not deal with them. 

So do some TC/SC equivalence in Kanji.  

Liana

On Fri, 5 Oct 2001 19:52:11 -0700 Yves Arrouye <yves@realnames.com>
writes:
> > I disagree Unicode Consortium to the WG dated 02Sept
> > recommendation.
> > 
> > Unicode has been very effective to collect scripts and glyphs
> > of all scripts, and even comes up with Unified CJK character
> > set, which is essential for IDN implementation.  I call this
> >  the FIRST level of look-alike equivalence.
> 
> Unicode does not collect glyphs but characters (and cf. section 2.1 
> of UTR
> #17, http://www.unicode.org/unicode/reports/tr17/). This is a 
> fundamental
> property of the Unicode standard. I am everything but a CJK expert, 
> but
> along the same idea, the Han characters were unified because they 
> meant the
> same thing (semantics) not because of glyph similarities.
> 
> YA
> 



From owner-idn@ops.ietf.org  Sat Oct  6 02:16:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20973
	for <idn-archive@lists.ietf.org>; Sat, 6 Oct 2001 02:16:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pkaD-00018J-00
	for idn-data@psg.com; Fri, 05 Oct 2001 23:05:09 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pkaB-00018C-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 23:05:08 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id PAA13866;
	Sat, 6 Oct 2001 15:04:44 +0900
Message-ID: <00f201c14e2c$f973d4d0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <yves@realnames.com>, <liana.ydisg@juno.com>
Cc: <jseng@pobox.org.sg>, <idn@ops.ietf.org>
References: <20011005.222310.-715373.3.liana.ydisg@juno.com>
Subject: Re: [idn] WG Update
Date: Sat, 6 Oct 2001 15:05:57 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id CAA20973


CJK participants are working hard offline to prepare  drafts for  new solution 
for TC/SC/Kanji equivalence within IDNA architecture .

Please take this into consideration before making further progress on your own.
Thanks

Soobok

----- Original Message ----- 
From: <liana.ydisg@juno.com>
To: <yves@realnames.com>
Cc: <liana.ydisg@juno.com>; <jseng@pobox.org.sg>; <idn@ops.ietf.org>
Sent: Saturday, October 06, 2001 2:23 PM
Subject: Re: [idn] WG Update


> You are correct on what you have said here.  But
> what I have said is correct too.  TC/SC mapping 
> are examples of semantic equivalence and 
> Unicode has not deal with them. 
> 
> So do some TC/SC equivalence in Kanji.  
> 
> Liana
> 
> On Fri, 5 Oct 2001 19:52:11 -0700 Yves Arrouye <yves@realnames.com>
> writes:
> > > I disagree Unicode Consortium to the WG dated 02Sept
> > > recommendation.
> > > 
> > > Unicode has been very effective to collect scripts and glyphs
> > > of all scripts, and even comes up with Unified CJK character
> > > set, which is essential for IDN implementation.  I call this
> > >  the FIRST level of look-alike equivalence.
> > 
> > Unicode does not collect glyphs but characters (and cf. section 2.1 
> > of UTR
> > #17, http://www.unicode.org/unicode/reports/tr17/). This is a 
> > fundamental
> > property of the Unicode standard. I am everything but a CJK expert, 
> > but
> > along the same idea, the Han characters were unified because they 
> > meant the
> > same thing (semantics) not because of glyph similarities.
> > 
> > YA
> > 
> 




From owner-idn@ops.ietf.org  Sat Oct  6 02:34:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21991
	for <idn-archive@lists.ietf.org>; Sat, 6 Oct 2001 02:34:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pkvv-0001r3-00
	for idn-data@psg.com; Fri, 05 Oct 2001 23:27:35 -0700
Received: from epervier.cqhost.net ([216.167.57.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pkvu-0001qx-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 23:27:34 -0700
Received: from mail.kanji.org (tsunami.hinocatv.ne.jp [210.175.87.130])
	by 216.167.42.124-cqhost (8.10.2/8.10.2) with SMTP id f966R8U30236;
	Sat, 6 Oct 2001 02:27:09 -0400
Message-Id: <200110062028.AA14613@mail.kanji.org>
Date: Sat, 06 Oct 2001 15:28:39 -0500
To: "Soobok Lee" <lsb@postel.co.kr>
Cc: <yves@realnames.com>, <liana.ydisg@juno.com>, <jseng@pobox.org.sg>,
        <idn@ops.ietf.org>
Subject: Re: [idn] WG Update
From: Jack Halpern <jack@kanji.org>
In-Reply-To: <00f201c14e2c$f973d4d0$ec1bd9d2@temp>
References: <00f201c14e2c$f973d4d0$ec1bd9d2@temp>
MIME-Version: 1.0
X-Mailer: AL-Mail32 Version 1.11
Content-Type: text/plain; charset=us-ascii
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Soobok Lee wrote...
 >
 >CJK participants are working hard offline to prepare  drafts for  new solution 
 >for TC/SC/Kanji equivalence within IDNA architecture .

 >Please take this into consideration before making further progress on your own.
 >Thanks

I haven't been following the discussion lately by TC/SC caught my eye. I am very curious 
about who is doing this work because for  the last five years we have engaged in the development 
of the world's most comprehensive dictionary and sophisticated system for converting between 
Simplified and Traditional Chinese. I have presented  papers on this at various international 
conferences  (see http://cjk.org/cjk/c2c/c2centry.htm), and am willing to be of help if this
is possible.


Regards, Jack Halpern
        President, The CJK Dictionary Institute, Inc. 
        http://www.cjk.org Phone: +81-48-473-3508 
  



From owner-idn@ops.ietf.org  Sat Oct  6 02:37:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22153
	for <idn-archive@lists.ietf.org>; Sat, 6 Oct 2001 02:37:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pkys-0001w0-00
	for idn-data@psg.com; Fri, 05 Oct 2001 23:30:38 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pkyr-0001vt-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 23:30:37 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VViaXnAUnFd4E1VtVtPavQZg==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GG22BV9L; Sat, 06 Oct 2001 02:30:06 EDT
To: lsb@postel.co.kr
Cc: yves@realnames.com, liana.ydisg@juno.com, jseng@pobox.org.sg,
        idn@ops.ietf.org
Date: Fri, 5 Oct 2001 23:50:36 -0700
Subject: Re: [idn] WG Update
Message-ID: <20011005.235038.-715373.7.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

Thank you for telling me this, could you please
update me, where they are?  When do I expect
to see the draft? 

Liana


On Sat, 6 Oct 2001 15:05:57 +0900 "Soobok Lee" <lsb@postel.co.kr> writes:
> 
> CJK participants are working hard offline to prepare  drafts for  
> new solution 
> for TC/SC/Kanji equivalence within IDNA architecture .
> 
> Please take this into consideration before making further progress 
> on your own.
> Thanks
> 
> Soobok
> 
> ----- Original Message ----- 
> From: <liana.ydisg@juno.com>
> To: <yves@realnames.com>
> Cc: <liana.ydisg@juno.com>; <jseng@pobox.org.sg>; <idn@ops.ietf.org>
> Sent: Saturday, October 06, 2001 2:23 PM
> Subject: Re: [idn] WG Update
> 
> 
> > You are correct on what you have said here.  But
> > what I have said is correct too.  TC/SC mapping 
> > are examples of semantic equivalence and 
> > Unicode has not deal with them. 
> > 
> > So do some TC/SC equivalence in Kanji.  
> > 
> > Liana
> > 
> > On Fri, 5 Oct 2001 19:52:11 -0700 Yves Arrouye 
> <yves@realnames.com>
> > writes:
> > > > I disagree Unicode Consortium to the WG dated 02Sept
> > > > recommendation.
> > > > 
> > > > Unicode has been very effective to collect scripts and glyphs
> > > > of all scripts, and even comes up with Unified CJK character
> > > > set, which is essential for IDN implementation.  I call this
> > > >  the FIRST level of look-alike equivalence.
> > > 
> > > Unicode does not collect glyphs but characters (and cf. section 
> 2.1 
> > > of UTR
> > > #17, http://www.unicode.org/unicode/reports/tr17/). This is a 
> > > fundamental
> > > property of the Unicode standard. I am everything but a CJK 
> expert, 
> > > but
> > > along the same idea, the Han characters were unified because 
> they 
> > > meant the
> > > same thing (semantics) not because of glyph similarities.
> > > 
> > > YA
> > > 
> > 
> 
> 



From owner-idn@ops.ietf.org  Sat Oct  6 03:10:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24073
	for <idn-archive@lists.ietf.org>; Sat, 6 Oct 2001 03:10:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15plQG-0002zc-00
	for idn-data@psg.com; Fri, 05 Oct 2001 23:58:56 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15plQF-0002zW-00
	for idn@ops.ietf.org; Fri, 05 Oct 2001 23:58:55 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id PAA30684;
	Sat, 6 Oct 2001 15:58:37 +0900
Message-ID: <012801c14e34$80a61b00$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <liana.ydisg@juno.com>
Cc: <yves@realnames.com>, <liana.ydisg@juno.com>, <jseng@pobox.org.sg>,
        <idn@ops.ietf.org>
References: <20011005.235038.-715373.7.liana.ydisg@juno.com>
Subject: Re: [idn] WG Update
Date: Sat, 6 Oct 2001 15:59:52 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id DAA24073

As one of the participants, I guess one of the drafts will  come out late october or early november.  

Soobok

----- Original Message ----- 
From: <liana.ydisg@juno.com>
To: <lsb@postel.co.kr>
Cc: <yves@realnames.com>; <liana.ydisg@juno.com>; <jseng@pobox.org.sg>; <idn@ops.ietf.org>
Sent: Saturday, October 06, 2001 3:50 PM
Subject: Re: [idn] WG Update


> Thank you for telling me this, could you please
> update me, where they are?  When do I expect
> to see the draft? 
> 
> Liana
> 
> 
> On Sat, 6 Oct 2001 15:05:57 +0900 "Soobok Lee" <lsb@postel.co.kr> writes:
> > 
> > CJK participants are working hard offline to prepare  drafts for  
> > new solution 
> > for TC/SC/Kanji equivalence within IDNA architecture .
> > 
> > Please take this into consideration before making further progress 
> > on your own.
> > Thanks
> > 
> > Soobok
> > 
> > ----- Original Message ----- 
> > From: <liana.ydisg@juno.com>
> > To: <yves@realnames.com>
> > Cc: <liana.ydisg@juno.com>; <jseng@pobox.org.sg>; <idn@ops.ietf.org>
> > Sent: Saturday, October 06, 2001 2:23 PM
> > Subject: Re: [idn] WG Update
> > 
> > 
> > > You are correct on what you have said here.  But
> > > what I have said is correct too.  TC/SC mapping 
> > > are examples of semantic equivalence and 
> > > Unicode has not deal with them. 
> > > 
> > > So do some TC/SC equivalence in Kanji.  
> > > 
> > > Liana
> > > 
> > > On Fri, 5 Oct 2001 19:52:11 -0700 Yves Arrouye 
> > <yves@realnames.com>
> > > writes:
> > > > > I disagree Unicode Consortium to the WG dated 02Sept
> > > > > recommendation.
> > > > > 
> > > > > Unicode has been very effective to collect scripts and glyphs
> > > > > of all scripts, and even comes up with Unified CJK character
> > > > > set, which is essential for IDN implementation.  I call this
> > > > >  the FIRST level of look-alike equivalence.
> > > > 
> > > > Unicode does not collect glyphs but characters (and cf. section 
> > 2.1 
> > > > of UTR
> > > > #17, http://www.unicode.org/unicode/reports/tr17/). This is a 
> > > > fundamental
> > > > property of the Unicode standard. I am everything but a CJK 
> > expert, 
> > > > but
> > > > along the same idea, the Han characters were unified because 
> > they 
> > > > meant the
> > > > same thing (semantics) not because of glyph similarities.
> > > > 
> > > > YA
> > > > 
> > > 
> > 
> > 
> 




From owner-idn@ops.ietf.org  Sat Oct  6 03:41:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24267
	for <idn-archive@lists.ietf.org>; Sat, 6 Oct 2001 03:41:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pln1-0004BH-00
	for idn-data@psg.com; Sat, 06 Oct 2001 00:22:27 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pln0-0004BB-00
	for idn@ops.ietf.org; Sat, 06 Oct 2001 00:22:26 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 6392CFFC10; Sat,  6 Oct 2001 15:23:03 +0800 (SGT)
Message-ID: <001701c14e37$a490ded0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>, <liana.ydisg@juno.com>
Cc: <yves@realnames.com>, <liana.ydisg@juno.com>, <idn@ops.ietf.org>
References: <20011005.235038.-715373.7.liana.ydisg@juno.com> <012801c14e34$80a61b00$ec1bd9d2@temp>
Subject: Re: [idn] WG Update
Date: Sat, 6 Oct 2001 15:22:23 +0800
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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Note: Until the I-D is published, reviewed and accepted into wg pool,
the wg have to proceed as if this activity does not happened.

The wg cannot wait or delay its schedule waiting for non-wg activities.

-James Seng


----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: <liana.ydisg@juno.com>
Cc: <yves@realnames.com>; <liana.ydisg@juno.com>; <jseng@pobox.org.sg>;
<idn@ops.ietf.org>
Sent: Saturday, October 06, 2001 2:59 PM
Subject: Re: [idn] WG Update


As one of the participants, I guess one of the drafts will  come out
late october or early november.

Soobok

----- Original Message -----
From: <liana.ydisg@juno.com>
To: <lsb@postel.co.kr>
Cc: <yves@realnames.com>; <liana.ydisg@juno.com>; <jseng@pobox.org.sg>;
<idn@ops.ietf.org>
Sent: Saturday, October 06, 2001 3:50 PM
Subject: Re: [idn] WG Update


> Thank you for telling me this, could you please
> update me, where they are?  When do I expect
> to see the draft?
>
> Liana
>
>
> On Sat, 6 Oct 2001 15:05:57 +0900 "Soobok Lee" <lsb@postel.co.kr>
writes:
> >
> > CJK participants are working hard offline to prepare  drafts for
> > new solution
> > for TC/SC/Kanji equivalence within IDNA architecture .
> >
> > Please take this into consideration before making further progress
> > on your own.
> > Thanks
> >
> > Soobok
> >
> > ----- Original Message -----
> > From: <liana.ydisg@juno.com>
> > To: <yves@realnames.com>
> > Cc: <liana.ydisg@juno.com>; <jseng@pobox.org.sg>; <idn@ops.ietf.org>
> > Sent: Saturday, October 06, 2001 2:23 PM
> > Subject: Re: [idn] WG Update
> >
> >
> > > You are correct on what you have said here.  But
> > > what I have said is correct too.  TC/SC mapping
> > > are examples of semantic equivalence and
> > > Unicode has not deal with them.
> > >
> > > So do some TC/SC equivalence in Kanji.
> > >
> > > Liana
> > >
> > > On Fri, 5 Oct 2001 19:52:11 -0700 Yves Arrouye
> > <yves@realnames.com>
> > > writes:
> > > > > I disagree Unicode Consortium to the WG dated 02Sept
> > > > > recommendation.
> > > > >
> > > > > Unicode has been very effective to collect scripts and glyphs
> > > > > of all scripts, and even comes up with Unified CJK character
> > > > > set, which is essential for IDN implementation.  I call this
> > > > >  the FIRST level of look-alike equivalence.
> > > >
> > > > Unicode does not collect glyphs but characters (and cf. section
> > 2.1
> > > > of UTR
> > > > #17, http://www.unicode.org/unicode/reports/tr17/). This is a
> > > > fundamental
> > > > property of the Unicode standard. I am everything but a CJK
> > expert,
> > > > but
> > > > along the same idea, the Han characters were unified because
> > they
> > > > meant the
> > > > same thing (semantics) not because of glyph similarities.
> > > >
> > > > YA
> > > >
> > >
> >
> >
>






From owner-idn@ops.ietf.org  Sat Oct  6 03:53:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24295
	for <idn-archive@lists.ietf.org>; Sat, 6 Oct 2001 03:53:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15plxU-0004Ys-00
	for idn-data@psg.com; Sat, 06 Oct 2001 00:33:16 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15plxR-0004Yf-00
	for idn@ops.ietf.org; Sat, 06 Oct 2001 00:33:14 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id QAA08823;
	Sat, 6 Oct 2001 16:32:50 +0900
Message-ID: <014201c14e39$49c898b0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <liana.ydisg@juno.com>
Cc: <yves@realnames.com>, <liana.ydisg@juno.com>, <idn@ops.ietf.org>
References: <20011005.235038.-715373.7.liana.ydisg@juno.com> <012801c14e34$80a61b00$ec1bd9d2@temp> <001701c14e37$a490ded0$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] WG Update
Date: Sat, 6 Oct 2001 16:34:05 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id DAA24295

I understand the chair's concerns.  Could you suggest this WG's agenda
for next 4 weeks ?  

----- Original Message ----- 
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>; <liana.ydisg@juno.com>
Cc: <yves@realnames.com>; <liana.ydisg@juno.com>; <idn@ops.ietf.org>
Sent: Saturday, October 06, 2001 4:22 PM
Subject: Re: [idn] WG Update


> Note: Until the I-D is published, reviewed and accepted into wg pool,
> the wg have to proceed as if this activity does not happened.
> 
> The wg cannot wait or delay its schedule waiting for non-wg activities.
> 
> -James Seng
> 
> 
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: <liana.ydisg@juno.com>
> Cc: <yves@realnames.com>; <liana.ydisg@juno.com>; <jseng@pobox.org.sg>;
> <idn@ops.ietf.org>
> Sent: Saturday, October 06, 2001 2:59 PM
> Subject: Re: [idn] WG Update
> 
> 
> As one of the participants, I guess one of the drafts will  come out
> late october or early november.
> 
> Soobok
> 
> 




From owner-idn@ops.ietf.org  Sat Oct  6 04:58:38 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24524
	for <idn-archive@lists.ietf.org>; Sat, 6 Oct 2001 04:58:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pmuV-0007Qg-00
	for idn-data@psg.com; Sat, 06 Oct 2001 01:34:15 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pmuU-0007Qa-00
	for idn@ops.ietf.org; Sat, 06 Oct 2001 01:34:14 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id RAA27768
	for <idn@ops.ietf.org>; Sat, 6 Oct 2001 17:34:01 +0900
Message-ID: <015b01c14e41$d3b6fc30$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Subject: [idn] Latin script and REORDERING
Date: Sat, 6 Oct 2001 17:35:16 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id EAA24524

This posting is to explain why REORDERING do something good only for non-latin scripts.

I have  47263 latin ML.com samples from various parts of Eastern and Western Europe.
 
  Total # of code points:      464915 
  # of basic latin letters:    409922
  # of extened latin letters:   54993 ( 0x00a0 ~ 0x0370)

This data shows that extended latin letters account for 12% (roughly   1/9 ) 
of code points in typical latin labels. But the mean average length of latin
labels is 10. Therefore,in most cases, latin labels contain only 1 extended latin letter.

As you know AMC-Z is designed to favor latin letters(called basic code points in AMC-Z),
because AMC-Z encodes basic latin letters in literal mode "as it is" 
for which reordering v2.0 does not do anything:

One typical latin domain of length 12: b<diaeresis u>stenhalter
U+0062 U+00FC U+0073 U+0074 U+0065 U+006E U+0068 U+0061 U+006C U+0074 U+0065 U+0072:

AMC-Z:            bstenhalter-thB

the non-basic(extended) latin letter <diaeresis u> is encoded into -thB 
in the latter part of the ACE label.

AMC-Z+REORDERING: bstenhalter-ymB     (the same length)

Reordering v2.0 reorders only the code point values of EXTENED latin letters
based on  frequency distribution data from ML.com samples from various countries.

Since most labels contain just 1 extened latin letters, reordering on
extened latin letters don't help, because reordering is designed to reduce
the successive code distances of the 2 or more non-basic code points.

I think it's fair to compensate AMC-Z-imposed disadvantage on non-latin scripts.

the next table in my I-D summarizes the reordering 
improvements for each latin ML.com  samples of length N:


(How to read the tables )
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




16. latin

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
|  1|      87|        87|       260(2.99)|       259(2.98)| 0.38|
|  2|    1043|      2086|      5140(2.46)|      5134(2.46)| 0.12|
|  3|    1046|      3138|      6274(2.00)|      6241(1.99)| 0.53|
|  4|    1812|      7248|     12750(1.76)|     12715(1.75)| 0.27|
|  5|    3238|     16190|     26129(1.61)|     26047(1.61)| 0.31|
|  6|    3956|     23736|     35894(1.51)|     35802(1.51)| 0.26|
|  7|    4340|     30380|     43756(1.44)|     43633(1.44)| 0.28|
|  8|    4639|     37112|     51351(1.38)|     51286(1.38)| 0.13|
|  9|    4551|     40959|     54994(1.34)|     54873(1.34)| 0.22|
| 10|    4289|     42890|     56159(1.31)|     56058(1.31)| 0.18|
| 11|    3778|     41558|     53227(1.28)|     53157(1.28)| 0.13|
| 12|    2967|     35604|     44820(1.26)|     44754(1.26)| 0.15|
| 13|    2501|     32513|     40264(1.24)|     40197(1.24)| 0.17|
| 14|    2058|     28812|     35212(1.22)|     35174(1.22)| 0.11|
| 15|    1653|     24795|     29947(1.21)|     29918(1.21)| 0.10|
| 16|    1372|     21952|     26264(1.20)|     26224(1.19)| 0.15|
| 17|    1094|     18598|     22053(1.19)|     21994(1.18)| 0.27|
| 18|     839|     15102|     17782(1.18)|     17722(1.17)| 0.34|
| 19|     632|     12008|     14045(1.17)|     13988(1.16)| 0.41|
| 20|     464|      9280|     10778(1.16)|     10721(1.16)| 0.53|
| 21|     312|      6552|      7539(1.15)|      7516(1.15)| 0.31|
| 22|     194|      4268|      4905(1.15)|      4876(1.14)| 0.59|
| 23|     124|      2852|      3242(1.14)|      3234(1.13)| 0.25|
| 24|      71|      1704|      1935(1.14)|      1925(1.13)| 0.52|
| 25|      71|      1775|      2011(1.13)|      2002(1.13)| 0.45|
| 26|      37|       962|      1083(1.13)|      1080(1.12)| 0.28|
| 27|      33|       891|      1004(1.13)|       996(1.12)| 0.80|
| 28|      17|       476|       535(1.12)|       529(1.11)| 1.12|
| 29|      13|       377|       422(1.12)|       420(1.11)| 0.47|
| 30|       9|       270|       298(1.10)|       299(1.11)|-0.34|
| 31|       7|       217|       243(1.12)|       238(1.10)| 2.06|
| 32|       9|       288|       321(1.11)|       316(1.10)| 1.56|
| 33|       4|       132|       146(1.11)|       144(1.09)| 1.37|
| 34|       2|        68|        76(1.12)|        74(1.09)| 2.63|
| 35|       1|        35|        38(1.09)|        38(1.09)| 0.00|


For arabic labels of length >13, the compression ratio is
close to 13%. compare this result with the one above.


1. arabic

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
|  1|      42|        42|       126(3.00)|       126(3.00)| 0.00|
|  2|      59|       118|       258(2.19)|       249(2.11)| 3.49|
|  3|     363|      1089|      2121(1.95)|      1992(1.83)| 6.08|
|  4|     888|      3552|      6359(1.79)|      5811(1.64)| 8.62|
|  5|    1122|      5610|      9550(1.70)|      8529(1.52)|10.69|
|  6|    1009|      6054|      9890(1.63)|      8620(1.42)|12.84|
|  7|     845|      5915|      9309(1.57)|      8134(1.38)|12.62|
|  8|     378|      3024|      4590(1.52)|      3992(1.32)|13.03|
|  9|     263|      2367|      3523(1.49)|      3063(1.29)|13.06|
| 10|     152|      1520|      2230(1.47)|      1941(1.28)|12.96|
| 11|     130|      1430|      2058(1.44)|      1787(1.25)|13.17|
| 12|     110|      1320|      1873(1.42)|      1614(1.22)|13.83|
| 13|      67|       871|      1230(1.41)|      1040(1.19)|15.45|
| 14|      61|       854|      1211(1.42)|      1015(1.19)|16.18|
| 15|      52|       780|      1085(1.39)|       924(1.18)|14.84|
| 16|      34|       544|       743(1.37)|       630(1.16)|15.21|
| 17|      11|       187|       256(1.37)|       218(1.17)|14.84|
| 18|      19|       342|       465(1.36)|       392(1.15)|15.70|
| 19|       8|       152|       201(1.32)|       175(1.15)|12.94|
| 20|      10|       200|       268(1.34)|       235(1.18)|12.31|
| 21|       3|        63|        85(1.35)|        75(1.19)|11.76|
| 22|       4|        88|       116(1.32)|        99(1.12)|14.66|
| 23|       3|        69|        89(1.29)|        76(1.10)|14.61|
| 24|       2|        48|        62(1.29)|        55(1.15)|11.29|
| 25|       5|       125|       165(1.32)|       143(1.14)|13.33|
| 26|       2|        52|        67(1.29)|        56(1.08)|16.42|
| 27|       2|        54|        73(1.35)|        61(1.13)|16.44|
| 33|       1|        33|        41(1.24)|        37(1.12)| 9.76|
| 34|       1|        34|        45(1.32)|        36(1.06)|20.00|

|All|    5646|     36537|     58089(1.59)|     51125(1.40)|11.99|


For hangul, the compression ratio reaches 31%.


8. hangul-1024

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
|  1|    1953|      1953|      7812(4.00)|      7812(4.00)| 0.00|
|  2|   17149|     34298|    124782(3.64)|    106238(3.10)|14.86|
|  3|   39643|    118929|    403205(3.39)|    323801(2.72)|19.69|
|  4|   62285|    249140|    816093(3.28)|    622067(2.50)|23.77|
|  5|   39675|    198375|    636102(3.21)|    470174(2.37)|26.09|
|  6|   23891|    143346|    452483(3.16)|    326242(2.28)|27.90|
|  7|   12448|     87136|    271953(3.12)|    192139(2.21)|29.35|
|  8|    5441|     43528|    134600(3.09)|     94322(2.17)|29.92|
|  9|    2264|     20376|     62405(3.06)|     43266(2.12)|30.67|
| 10|     895|      8950|     27223(3.04)|     18764(2.10)|31.07|
| 11|     373|      4103|     12420(3.03)|      8511(2.07)|31.47|
| 12|     141|      1692|      5080(3.00)|      3505(2.07)|31.00|
| 13|      77|      1001|      2986(2.98)|      2039(2.04)|31.71|
| 14|      32|       448|      1331(2.97)|       911(2.03)|31.56|
| 15|      20|       300|       884(2.95)|       603(2.01)|31.79|
| 16|      10|       160|       460(2.88)|       337(2.11)|26.74|
| 17|       7|       119|       354(2.97)|       243(2.04)|31.36|

|All|  206304|    913854|   2960173(3.24)|   2220974(2.43)|24.97|


REORDERING is consisted of only character mappings. It resembles
legacy-to-UCS2 mapping which preserves the character entity itself
while it assign new different code integer value to it.
It's clear that REORDERING adds just as much complexity as 
the legacy-to-UCS mappings  done by IDNA-aware applications 
before nameprep/ACE process.

Soobok Lee





From owner-idn@ops.ietf.org  Sat Oct  6 05:53:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24723
	for <idn-archive@lists.ietf.org>; Sat, 6 Oct 2001 05:53:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15pnyE-0009kD-00
	for idn-data@psg.com; Sat, 06 Oct 2001 02:42:10 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15pnyD-0009jr-00
	for idn@ops.ietf.org; Sat, 06 Oct 2001 02:42:09 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id SAA16196
	for <idn@ops.ietf.org>; Sat, 6 Oct 2001 18:41:57 +0900
Message-ID: <017101c14e4b$510ec240$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Subject: [idn] Arabic and REORDERING
Date: Sat, 6 Oct 2001 18:43:12 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA24723

This posting is to explain how REORDERING can help countries using even non-CJK scripts.

This is an arabic ML.com of length 34 :


U+0627 U+0644 U+0625 U+0645 U+0627 U+0631 U+0627 U+062A
U+0627 U+0644 U+062F U+0648 U+0644 U+064A U+0629 U+0644
U+0644 U+0627 U+0633 U+062A U+0634 U+0627 U+0631 U+0627
U+062A U+0627 U+0644 U+0642 U+0627 U+0646 U+0648 U+0646
U+064A U+0629

AMC-Z :           kgBDBAAAAAAARFFDC8E4AI9AV31A0AGBBAJH6CA8BR3CS     ( 45 )

REORDERING+AMC-Z: mgBKMSFCEFDBXAFHEQHNKCECCAFHDBBIDBBC   ( 36 )



This is another arabic label of length 55 which is constructed by
concatenating two arabic labels of length 34 and 21:

U+0627 U+0644 U+0625 U+0645 U+0627 U+0631 U+0627 U+062A
U+0627 U+0644 U+062F U+0648 U+0644 U+064A U+0629 U+0644
U+0644 U+0627 U+0633 U+062A U+0634 U+0627 U+0631 U+0627
U+062A U+0627 U+0644 U+0642 U+0627 U+0646 U+0648 U+0646
U+064A U+0629
U+0636 U+0645 U+064A U+0631 U+0627 U+0644 U+0645 U+062A
U+0643 U+0644 U+0645 U+0627 U+0644 U+0645 U+0636 U+0627
U+0641 U+0625 U+0644 U+064A U+0647

AMC-Z :           kgBAEBAAAAAAAAAAWFJDCE8GuBIF5B1A5DE43AuA1BHGBBAJGCBEEZDDC7AA2EMR1GsADQ     ( 69 > 59 = 63 - 4 : error!)

REORDERING+AMC-Z: lgBABCWPKSHQLCKLDBD7AAMHLOACAHHIQKDJCECCAFKDBEDDBBIDBBCJGD   ( 58 )
[ 58 / 53 = 1.094, close to the ratio for latin labels  in bare AMC-Z (1.09),
  compensation succeeded!  ]


Yet another arabic label of length :  47

U+0627 U+0644 U+0625 U+0645 U+0627 U+0631 U+0627 U+062A
U+0627 U+0644 U+062F U+0648 U+0644 U+064A U+0629 U+0644
U+0644 U+0627 U+0633 U+062A U+0634 U+0627 U+0631 U+0627
U+062A U+0627 U+0644 U+0642 U+0627 U+0646 U+0648 U+0646
U+064A U+0629
U+0636 U+0645 U+064A U+0631 U+0627 U+0644 U+0645 U+062A
U+0643 U+0644 U+0645 U+0627 U+0644

AMC-Z :           kgBDBAAAAAAAAATFHDCE8FrBIF1BzA1DyT7ADGBBAJGCBEZDD4AA2ER7ESD (  58 )

REORDERING+AMC-Z: lgBBPQQIHCGHDBDZAIHHOACDHILKDGECCAFKDBBDBBIDBBCJG   ( 49 )


These experiments on two  arabic samples shows that
the maximum length of arabic labels for bare AMC-Z
is about 47, while that for REORDERING+AMC-Z is 55  with some errors of 1~2 characters.

With REORDERING, arabic-using people will have less complaints about
their imposed disadvantage in arabic ACE labels.


Soobok Lee




From owner-idn@ops.ietf.org  Sat Oct  6 06:28:17 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA24804
	for <idn-archive@lists.ietf.org>; Sat, 6 Oct 2001 06:28:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15poXM-000B5J-00
	for idn-data@psg.com; Sat, 06 Oct 2001 03:18:28 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15poXL-000B5D-00
	for idn@ops.ietf.org; Sat, 06 Oct 2001 03:18:27 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id TAA27562
	for <idn@ops.ietf.org>; Sat, 6 Oct 2001 19:18:17 +0900
Message-ID: <017f01c14e50$64da68b0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Subject: [idn] Hindi and REORDERING 
Date: Sat, 6 Oct 2001 19:19:33 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id GAA24804

This posting is to explain how REORDERING can help countries using even non-CJK scripts.
(please skip if you're tired of this kind of stuff)

This is a hindi ML.com of length 10 :

U+0905 U+091A U+0932 U+0938 U+0902 U+092A U+0924 U+094D U+0924 U+093F
 
AMC-Z:             i1BF7DxBA8A4C7BzDtH    ( 19 )
REORDERING+amc-z:  e2BIM6AKAKI5A2B        ( 15 )


This is another arabic label of length 46 which is constructed by
concatenating four arabic labels:

U+0905 U+091A U+0932 U+0938 U+0902 U+092A U+0924 U+094D U+0924 U+093F
U+0909 U+091A U+094D U+091A U+0924 U+0915 U+0928 U+093E U+0932 U+093E U+091C U+0940
U+0915 U+093E U+0920 U+094D U+092E U+093E U+0923 U+094D U+0921 U+094C U+0902
U+0917 U+0943 U+0939 U+0935 U+094D U+092F U+0935 U+0938 U+094D U+0925 U+093E U+092A U+0915

AMC-Z :      i1BAHR4DABPVCAZ7CO3AIAD1A6C8AQ0G2A0DK3GB9DwA1A4MBCCKL2C9H1PuAEMDHD ( 66 )
REORDERING:  v1BIODUOI6ABAN0AEH4D0BNNRHAD2BIQTS0AW8ADN2ABT2AEJCHD7DBDDP         ( 58 )

This is another arabic label of length 40 which is constructed by
eliminating trailing 6 characters from the one above:

U+0905 U+091A U+0932 U+0938 U+0902 U+092A U+0924 U+094D U+0924 U+093F
U+0909 U+091A U+094D U+091A U+0924 U+0915 U+0928 U+093E U+0932 U+093E U+091C U+0940
U+0915 U+093E U+0920 U+094D U+092E U+093E U+0923 U+094D U+0921 U+094C U+0902
U+0917 U+0943 U+0939 U+0935 U+094D U+092F U+0935

AMC-Z :      i1BAHR4DAPSCAX3CN1AHAD7E4A5GzA1CK4FB0D5B0IBCCR7B1HsOpAEMDH ( 58 )




From owner-idn@ops.ietf.org  Sun Oct  7 05:49:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21591
	for <idn-archive@lists.ietf.org>; Sun, 7 Oct 2001 05:49:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qA96-000BJC-00
	for idn-data@psg.com; Sun, 07 Oct 2001 02:22:52 -0700
Received: from twnic.net.tw ([211.72.210.250])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qA95-000BJ5-00
	for idn@ops.ietf.org; Sun, 07 Oct 2001 02:22:51 -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 RAA21255;
	Sun, 7 Oct 2001 17:22:30 +0800
Message-ID: <3BC0236A.CDAC064@twnic.net.tw>
Date: Sun, 07 Oct 2001 17:42:02 +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: James Seng/Personal <jseng@pobox.org.sg>
CC: idn@ops.ietf.org, tsenglm@csie.ncu.edu.tw
Subject: Re: [idn] WG Update
References: <016c01c14c76$ea176c20$dd00a8c0@jamessonyvaio>
Content-Type: text/plain; charset=big5
Content-Transfer-Encoding: 8bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

James and Dear all,

As James mentioned in the WG Update infromation, the requirements draft will

be moving forward for IETF Last Call.

Actually we'v seen many people discusswed about what IDN were they expected
before and after Landon meeting. To define the requirement of IDN is an
fundamental and important goal of our IDN WG. If the draft requirement-08 is

going to moving forward for IETF Last Call, we are strongly suggest
equirement-08 should fully meet the real requirement of IDN.

As in the 2. General Requirements of 2.3 Canonicalization

[21] In order to retain backward compatibility with the current DNS,
the service MUST retain the case-insensitive comparison for US-ASCII
as specified in RFC 1035. For example, Latin capital letter A (U+0041)
MUST match Latin small letter a (U+0061). Unicode Technical Report #21
describes some of the issues with case mapping. Case-insensitivity for
non US-ASCII MUST be discussed in the protocol proposal.

I recommend modify the last line "MUST be discussed" to be
"MUST be provided", as to be " Case-insensitivity for non US-ASCII MUST be
provided in the protocol proposal"

Beside [21], I think draft requirement-08 still need all the WG members to
review
carefully to insure it meet the real IDN requirements.

Erin Chen

James Seng/Personal ¼g¤J¡G

> In the last London meeting, there are still some outstanding issues
> which we agreed to bring it back to the mailing list to discuss.
>
> First, the issue of nameprep. nameprep have been renamed to stringprep
> and the new draft is available few days ago. Please review
> draft-ietf-idn-nameprep-06.txt.
>
> And related to nameprep are the jpchar, hanguelchar and tsconv drafts.
> The authors should get together to consider an architecture document.
> We should set a deadline for this to be concluded, probably sometime
> before Salt Lake meeting.
>
> This architecture document should take into consideration of:
> a. the recommendation from the Unicode Consortium to the WG dated 02Sept
> b. the source and stablity of the referenced work/codepoints
>
> (Personally, I would strongly recommend that nameprep remains as it is
> and the rest of the "localization" to be deal at a different level,
> either at the input method or below at the zone file.)
>
> Secondly, there is a reordering draft draft-ietf-idn-lsb-ace. We have
> already seen some results on reordering but we have not seen much
> discussion on the downside of reordering. In anycase, we would like
> to encourage further discussion on reordering draft as we would like
> to conduct a strawpoll on the draft soon.
>
> Thirdly, we have seen a strong number of people who is against UNAME and
> UDNS. Therefore, we will be removing UNAME and UDNS from the WG Pool in
> the next few days. Please take note that this does not prevent someone
> from coming forward with another proposal.
>
> The wg chairs have also receive several request to make updates on the
> goal & milestone of the charter to reflect the current wg position. We
> will send out a first draft for comments very shortly.
>
> Some other wg matters:
>
> As agreed in London meeting, the requirements draft will be moving
> forward for IETF Last Call.
>
> Based on the hum in London, the chairs also believe we have consensus
> on AMC-ACE-Z (draft-ietf-idn-amc-ace-z) as the choosen ACE. We feel
> a wg last call would provide no further information for the chairs to
> determine consensus since most people are in the "don't care but just
> want to see one ACE choosen" group. We will move AMC-ACE-Z forward to
> the IESG at an appropriate time.
>
> (minor note: we also agree that we should look for another name for
> AMC-Z but I think that discussion have already started :-)
>
> A prefix for AMC-Z will be assigned using the normal IESG/IANA/
> RFC-editor procedure for coordinating assignment of protocol
> parameters during IETF last call and publication as an RFC.
>
> Given this, we would like to advise people to start doing
> interoperability testing on their implementation of AMC-Z.
>
> For you information and comments.
>
> James Seng
> co-chair IDN wg




From owner-idn@ops.ietf.org  Sun Oct  7 08:34:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22399
	for <idn-archive@lists.ietf.org>; Sun, 7 Oct 2001 08:34:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qCxF-000HpU-00
	for idn-data@psg.com; Sun, 07 Oct 2001 05:22:49 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qCxE-000HpN-00
	for idn@ops.ietf.org; Sun, 07 Oct 2001 05:22:49 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f97CMWm28057;
	Sun, 7 Oct 2001 08:22:32 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110071222.f97CMWm28057@nic-naa.net>
X-Mailer: exmh version 1.6.9 8/22/96
To: Erin Chen <erin@twnic.net.tw>
cc: James Seng/Personal <jseng@pobox.org.sg>, idn@ops.ietf.org,
        tsenglm@csie.ncu.edu.tw
Subject: Re: [idn] WG Update 
In-Reply-To: Your message of "Sun, 07 Oct 2001 17:42:02 +0800."
             <3BC0236A.CDAC064@twnic.net.tw> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 07 Oct 2001 08:22:32 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> As James mentioned in the WG Update infromation, the requirements draft
> will be moving forward for IETF Last Call.

The management of this document has been problematic, and the editors are
non-responsive to requests for modification -- the "Intended Scope" section
retains its ACE recommendation -- this appears to be an article of religious
conviction.

> Beside [21], I think draft requirement-08 still need all the WG members
> to review carefully to insure it meet the real IDN requirements.

I don't think the existing requirements document must be abandoned, but it
must be edited by editors who are _editors_ before it leaves this WG or its
valu is limited.

I've made process suggestions to the editors, without comment or reply, to
the co-chairs (some overlap), and to the ADs and the TA.

Eric Brunner-Williams




From owner-idn@ops.ietf.org  Sun Oct  7 11:07:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23868
	for <idn-archive@lists.ietf.org>; Sun, 7 Oct 2001 11:07:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qF6c-000MzQ-00
	for idn-data@psg.com; Sun, 07 Oct 2001 07:40:38 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qF6W-000MxN-00
	for idn@ops.ietf.org; Sun, 07 Oct 2001 07:40:33 -0700
Received: from LocalHost ([140.115.7.27])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f97EkQ729659;
	Sun, 7 Oct 2001 22:46:26 +0800 (CST)
Message-ID: <005401c14f3d$b103cc20$1b07738c@q.j.tw>
From: =?big5?B?dHNlbmdsbUCtcLr0pKSk3y6kpKRqLnR3?= <tsenglm@cc.ncu.edu.tw>
To: "Erin Chen" <erin@twnic.net.tw>,
        "James Seng/Personal" <jseng@pobox.org.sg>
Cc: <idn@ops.ietf.org>, <tsenglm@csie.ncu.edu.tw>
References: <016c01c14c76$ea176c20$dd00a8c0@jamessonyvaio> <3BC0236A.CDAC064@twnic.net.tw>
Subject: Re: [idn] WG Update
Date: Sun, 7 Oct 2001 22:38:08 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

> As in the 2. General Requirements of 2.3 Canonicalization
>
> [21] In order to retain backward compatibility with the current DNS,
> the service MUST retain the case-insensitive comparison for US-ASCII
> as specified in RFC 1035. For example, Latin capital letter A (U+0041)
> MUST match Latin small letter a (U+0061). Unicode Technical Report #21
> describes some of the issues with case mapping. Case-insensitivity for
> non US-ASCII MUST be discussed in the protocol proposal.
>
> I recommend modify the last line "MUST be discussed" to be
> "MUST be provided", as to be " Case-insensitivity for non US-ASCII MUST be
> provided in the protocol proposal"
>
        The term " Case-insenstivitty for non US-ASCII "  should be defined
and described clearly, especially in any phase before ACE translation.
        Unicode is the collection of all scripts in all native code.  Some
scripts  are  alphabetic  font of "Full size  or double character size ASCII
font" coded in  native code and collected in UNICODE table.  That part  are
treated the same as US-ASCII characters in nameprep by case mapping with the
table of Unicode Technical Reports #21. I think this part is not related to
the issue of Case-incenstivity for non-US-ASCII ".
         The TC/SC equivalent class is always conceptually described by the
similar properties of  case in ASCII characters ,  but one thing in
retaining the out-look of original form is very inportant in CJK characters
of equivalent class .  That is say, to retain the case-insensitive
comparison for US-ASCII should not be implemented with nameprep  by
"force-all-to-lower-case" , I think the approach of "forced all ASCII
characters to lower case and losing the information of case" is not
necessary in nameprep phase. So, the key point of "Case-insenstivity for non
US-ASCII " is to reserve the case information before ACE translation.
Because AMC-ACE-Z  encoding has the feature that can retain the case of
US-ASCII characters in  ACE formatted IDN.   And the comparison is
accomplished by the current LDH-DNS server in insensitive-case comparison.
        The backward compatibility in retainning  the out-look of case of
ASCII is important now . It is  not just to keep the compatibilty of past
ASCII name but also help to use the case anotation of AMC-ACE-Z to  support
CJK characters can be recovered to the original scripts form.  The
comparison of TC/SC equivalent class are also based on the same feature of
case-insensitive comparison in LDH-DNS but it need to retain all the
original case form in passing-thru all processing phase. So the non-ASCII
part of IDN can be recoveried to their original scripts form.

L.M.Tseng

> Beside [21], I think draft requirement-08 still need all the WG members to
> review carefully to insure it meet the real IDN requirements.
>
> Erin Chen
>
> James Seng/Personal ¼g¤J¡G
>
> > In the last London meeting, there are still some outstanding issues
> > which we agreed to bring it back to the mailing list to discuss.
> >
> > First, the issue of nameprep. nameprep have been renamed to stringprep
> > and the new draft is available few days ago. Please review
> > draft-ietf-idn-nameprep-06.txt.
> >
> > And related to nameprep are the jpchar, hanguelchar and tsconv drafts.
> > The authors should get together to consider an architecture document.
> > We should set a deadline for this to be concluded, probably sometime
> > before Salt Lake meeting.
> >
> > This architecture document should take into consideration of:
> > a. the recommendation from the Unicode Consortium to the WG dated 02Sept
> > b. the source and stablity of the referenced work/codepoints
> >
> > (Personally, I would strongly recommend that nameprep remains as it is
> > and the rest of the "localization" to be deal at a different level,
> > either at the input method or below at the zone file.)
> >
> >




From owner-idn@ops.ietf.org  Sun Oct  7 12:54:30 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24513
	for <idn-archive@lists.ietf.org>; Sun, 7 Oct 2001 12:54:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qH0k-0001qL-00
	for idn-data@psg.com; Sun, 07 Oct 2001 09:42:42 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qH0j-0001qF-00
	for idn@ops.ietf.org; Sun, 07 Oct 2001 09:42:41 -0700
Received: from bbprime.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 JAA31030
	for <idn@ops.ietf.org>; Sun, 7 Oct 2001 09:42:39 -0700
Message-Id: <5.1.0.14.2.20011007093209.0204a978@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 07 Oct 2001 09:34:38 -0700
To: idn@ops.ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] WG Update 
In-Reply-To: <200110071222.f97CMWm28057@nic-naa.net>
References: <Your message of "Sun, 07 Oct 2001 17:42:02 +0800." <3BC0236A.CDAC064@twnic.net.tw>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk


>  the "Intended Scope" section
>retains its ACE recommendation -- this appears to be an article of religious
>conviction.


Folks,

A requirements document needs to specify requirements, not solutions.  It 
is not for the purpose of choosing a technology.  It is for the purpose of 
specifying the functions that a technology must provide.

A requirements document that crosses over into making specific technical 
recommendations is LESS useful, not More.  It is creating an opportunity 
for controversy.

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 Oct  7 15:59:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25181
	for <idn-archive@lists.ietf.org>; Sun, 7 Oct 2001 15:59:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qJll-0008ZR-00
	for idn-data@psg.com; Sun, 07 Oct 2001 12:39:25 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qJlk-0008ZL-00
	for idn@ops.ietf.org; Sun, 07 Oct 2001 12:39:24 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f97JdCm37562;
	Sun, 7 Oct 2001 15:39:13 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110071939.f97JdCm37562@nic-naa.net>
X-Mailer: exmh version 1.6.9 8/22/96
To: Dave Crocker <dhc@dcrocker.net>
cc: idn@ops.ietf.org
Subject: Re: [idn] WG Update 
In-Reply-To: Your message of "Sun, 07 Oct 2001 09:34:38 PDT."
             <5.1.0.14.2.20011007093209.0204a978@dcrocker.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 07 Oct 2001 15:39:12 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> A requirements document that crosses over into making specific technical 
> recommendations is LESS useful, not More.  It is creating an opportunity 
> for controversy.

Dave,

If no one disagreed with the recommendation, it would still be bogus.

I disagree with the recommendation, but I'd be just as concerned about
an editing excess if it read:

    It is recommended that the solution necessarily entails more than 
    the DNS itself, can not be satisfactorily resolved by indirection
    (layering), and should not be resolved by an alternate mechanism
    (directorie service).

Requirements documents, particularly in complex and contentuous areas, are
not party favors, to be awarded uncritically to the party in favor.

Reading the damn thing critically, and taking the time to write carefully,
has been time wasted.

Eric





From owner-idn@ops.ietf.org  Sun Oct  7 15:59:19 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25192
	for <idn-archive@lists.ietf.org>; Sun, 7 Oct 2001 15:59:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qJml-0008cK-00
	for idn-data@psg.com; Sun, 07 Oct 2001 12:40:27 -0700
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qJmk-0008cD-00
	for idn@ops.ietf.org; Sun, 07 Oct 2001 12:40:26 -0700
Received: from zetnet.co.uk (man-s034.dialup.zetnet.co.uk [194.247.41.161])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f97JeMX03102
        for <idn@ops.ietf.org>; Sun, 7 Oct 2001 20:40:22 +0100
Message-ID: <3BBFF722.EA1D7B58@zetnet.co.uk>
Date: Sun, 07 Oct 2001 07:33:06 +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] WG Update
References: <016c01c14c76$ea176c20$dd00a8c0@jamessonyvaio> <3BC0236A.CDAC064@twnic.net.tw>
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-----

Erin Chen wrote:
> As in the 2. General Requirements of 2.3 Canonicalization
> 
> [21] In order to retain backward compatibility with the current DNS,
> the service MUST retain the case-insensitive comparison for US-ASCII
> as specified in RFC 1035. For example, Latin capital letter A (U+0041)
> MUST match Latin small letter a (U+0061). Unicode Technical Report #21
> describes some of the issues with case mapping. Case-insensitivity for
> non US-ASCII MUST be discussed in the protocol proposal.
> 
> I recommend modify the last line "MUST be discussed" to be
> "MUST be provided", as to be " Case-insensitivity for non US-ASCII MUST be
> provided in the protocol proposal"

I disagree. As it happens, all of the proposals provide case-insensitivity
for non-US-ASCII, but it is *not* a requirement. The protocol would work
fine and would be perfectly acceptable to users without it. We should be
clear about the difference between features that are *desirable* (in this
case for consistency), and *required* features.

In particular, preservation of case is wholly unnecessary, IMHO.
[21] is perfectly OK as it is (although much of the rest of the requirements
draft is not; I'll discuss that in another post).


<tsenglm@csie.ncu.edu.tw> wrote:
> The TC/SC equivalent class is always conceptually described by the
> similar properties of  case in ASCII characters, ...

No, it is not. TC/SC folding is an entirely separate issue to case
folding. As I've pointed out before, it is counterproductive to try to
argue by an analogy that a consensus of the WG does not accept.

- -- 
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

iQEVAwUBO7/2zTkCAxeYt5gVAQGvZQgAvWfiHcqPPog2htBBOhtLUXMP4dOSVI5/
F03Wk4oeYhyr32wMhjbDDsxCwdroAdhExEiAwLt31qpg7dSuyglzM3VILxznvvVu
/inTb1oari9SnGjwu2hDKlTs5lfeTHKiSsdm5D1xAwaUo6fA8RW0gaDWv20elt74
fm+WmS+3QHRxM4Y6MdCtjLpJdC0ywZUyDo/wfM9iMNsc7WHWzfWCE37xFQYH9nsJ
zvRxfzV9AaEkV0ZtxBJWRknP1E59Gv3zGBi60WHX21/1ZykGu/6e6pk8OZ+CEHx4
Ock7UKySbpkqXOncpCwJVSEdJyW+Y0hqfSCwzmlRXl5JIOpCoENHvQ==
=oyij
-----END PGP SIGNATURE-----




From ehdck9@lycos.co.kr  Sun Oct  7 16:34:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25358
	for <idn-archive@lists.ietf.org>; Sun, 7 Oct 2001 16:34:40 -0400 (EDT)
Received: from [211.51.63.171] (helo=kr-outmail2.lycos.co.kr)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qKJB-000A3C-00; Sun, 07 Oct 2001 13:13:57 -0700
From: "Á¶µ¿¼ö" <ehdck9@lycos.co.kr>
To: idea10@dongah.co.kr, idea10@hanmail.net, idea-1004@hanmail.net,
        idea11@cgnt.net, idea17@hitel.net, idea1914@lycos.co.kr,
        idea1979@naver.com, idea2000@mail.dwconst.co.kr, idea212@chollian.net,
        idea3478@chollian.net, idea4332@naver.com, idea714@hanmail.Hnet,
        idea7rose@hanmail.net, idea813@hanmail.net, idea87@hanmail.net,
        idea98@edunet4u.net, ideabank@chollian.net, ideabank@kitis.or.kr,
        ideabay@joins.com, ideabell@dreamwiz.com, ideabest@hanmail.net,
        ideabook@kware21.com, ideabox@unitel.c,
        ideabox7@aicore.Hchungbuk.ac.kr, ideaclok@ideaclock.co.kr,
        ideadb@hanmail.co.kr, ideadicc@netsgo.com, ideae@nownuri.net,
        ideafii@unitel.co.kr, idea-frank@hanmail.net, ideagood@mabub.com,
        ideagood@yahoo.co.kr, ideaid@dreamwiz.com, ideaidea@unitel.co.kr,
        ideainfo@ideaplaza.Hco.kr, ideajang@naver.com, ideajin@n-top.com,
        ideajob@hanmail.net, ideak@fknews.com, ideakang@lycos.co.kr,
        ideakr@korea.com, ideal@joongang.co.kr, ideal@plaza.snu.ac.kr,
        ideal@postech.ac.k, ideal@postech.ac.kr, ideal777@chollian.net,
        idealady@hanmail.netH, idealchaser@hotmail.com,
        idealcom@ms.sem.samsung.co.kr, ideale@shinbiro.com,
        idealgas@kornet.net, idealism@shinbiro.com, idealism@somsusic.co.kr,
        idealism@somusic.co.kr, idealist@hosanna.net, idealist@netian.com,
        ideallove@channeli.net, idealsys@soback.Hkornet.net,
        idealsys98@netsgo.com, ideaman@ideaplaza.co.kr, ideaman@krpost.net,
        ideaman@syworks.com, ideaman9@mail.kangwon.ac.kr,
        ideamd@ideaplaza.co.kr, ideanara@korea.com, ideanara@korea.com1,
        ideaone@unitel.co.kr, ideapjh@hanmail.net, ideaplay@sandoll.Hco.kr,
        idear@woongil.co.kr, idearo@hanmail.net, idears@daum.net,
        ideas@ventureport.co.kr, ideashipper@planeast.com, ideasman@joins.com,
        ideasmlee@ideaplaza.co.kr, ideasource@dreamwiz.com,
        ideawd@ideaworld.co.kr, ideaworld@juno.cs.pusan.ac.kr,
        ideayoun@posHco.co.kr, idec@netpia.com, idecmail@idec.re.pusan.ac.kr,
        idecreg@daisy.kwangwoon.ac.kr, idedtea@netsgo.com,
        idee@pine.sangmyung.ac.kr, idee21@korea.com, idego@unitel.co.kr,
        idegong@serome.net, idelee@hanmail.net, idelleatwater@prodigy.net,
        iden@chollian.net, idendy@hotmail.com, Idenial@lycos.co.kr,
        idensun-lee@hanmail.net, identist@dreamwiz.com, Identist@hitel.net,
        identity1014@hanmail.net, identop@hanmail.net, identy2825@orgio.net,
        ideologie@korea.com, ideong0416@kepad.or.kr, ideosync_1999@yahoo.co.kr,
        iderH@samsung.co.kr, idesly@hanmail.net, idesra@hanmail.net,
        ideux@hanmail.net, idev@wbweb.co.kr, idevil@ctown.net,
        idevil1@hanmail.net, idfc@baromtec.com, idfreeman@hanmail.net,
        idg0824@hamail.net, idg9954@shinbiro.com, idgagul@netok.co.kr,
        idgame@korea.com, Hidgaumsa@hanmail.net, idgeon@hanmir.com,
        idgerni@hanmail.net, idgogo@kebi.com, idgroup@hanmail.net
Cc: idh@2582875.com, idh@plaza1.snut.ac.kr, Idh@wisecontrol.com,
        idh1115@chollian.net, idh1122@hanmail.net, idh1796@mail.korail.go.kr,
        idha@kyungsan.ksucc.ac.kr, idha@uni-ocean.com, idha1111@hanmail.net,
        idhan@munhwa.co.kr, idhcp@hanmail.net, idhong@kjist.aHc.kr,
        idhong@pia.kjist.ac.kr, idhooo@hanmail.net, idhowdy@b2binternet.co.kr,
        idhsd@hanmail.net, idhsh1023@yahoo.co.kr, idhsy@hanmail.net,
        idhwang@dragon.taejon.ac.kr, idhwang@metro.seoul.kr,
        idhwang@www.metro.seoul.kr, idhyu@hanmail.net, idi@cfi.co.kr,
        idHi@dreamwiz.com, idi_1973@hanmail.net, idi0@hitel.net,
        idi120@hanmail.net, idi2022@hanmail.net, idi77@hanmail.net,
        idia7@idoban.net, idiary@internetdiary.co.kr, id-icando@hanmail.net,
        idicil@cdcs.changwon.ac.kr, idid0486@korea.com, idid2216@netia.com,
        ididH77@hanmail.net, ididf@hanmail.net, ididgood@hanmail.net,
        ididid@mail.metro.taegu.kr, ididstorm@hanmail.net,
        idiedv@induk-c.ac.kr, idify1@netian.com, id-inet@hanmail.net,
        idins@hanmail.net, idiny@chollian.net, idiny@joongang.co.kr,
        idio@hanmir.com, idio@hiHhome.com, idio2@dreamwiz.com,
        idiocy@kaist.ac.kr, idiom@angel1004.com, idiom@chollian.net,
        idiom@hanbox.com, idioma@hitel.net, idiosync@netian.com,
        idiot2@edunet.kmec.net, idiot32@gabia.com, idiot97@hanmail.net,
        idiot97@hotmail.com, idiot97@nownuri.net, iHdious@hanmail.net,
        idisha@edunet4u.net, idisheyjoon@hanmail.net, idisid@isthis.com,
        idisid@kyungmin.ac.kr, idisid@kyungmin-c.ac.kr, idisid79@hanmir.com,
        idisk@estsoft.com, idiskhs@hanmail.net, idiskjr@hanmail.net,
        idisksh@hanmail.net, idislee@kichoi.donggHuk.ac.kr, idisnot@kornet.net,
        idisnot@netian.com, idissora@daum.net, idissuckbin@hanmail.net,
        iditarod@gen.co.kr, iditec@cncedu.dongbu.co.kr, iditep@netian.com,
        i-ditto@hanmail.net, idj@khu.ac.kr, idj8651@hosanna.net,
        idjae@korexmail.korexmall.co.kr, idjeon@hte.co.Hkr,
        idjeon@pochulgo.net, idjini@jsc.ac.kr, idjrjy@hando-mc.co.kr,
        idjtoz@hi.wooil.co.kr, idjune@yahoo.co.kr, idjut@netmcr.com,
        IDjYJ@chollian.net, id-k@hosanna.net, idk@swcpa.co.kr,
        idk_aracy@hotmail.com, idk1968@hanmail.net, idk7005@cjt.or.kr,
        idk7209@haHnmail.net, idkang7@hanmail.net, idkey@hitel.net,
        id-khj0902@hanmail.net, idkhs@cans21.net, idkim@bear.kyungil.ac.kr,
        idkim@dolphin.pknu.ac.kr, idkim@doowon.ac.kr,
        idkim@explore.kwangwoon.ac.kr, idkim@hitech.co.kr, idkim@lgia.com,
        idkim@pknu.ac.kr, i-d-kimH@poongsan.co.kr, idkim@samsung.co.kr,
        idkim24@orgio.net, idkim58@hanmir.com, idkimhj@hanmail.net,
        idko7@hanmail.net, idkoh@kdi.re.kr, idkoh@kdiux.kdi.re.kr,
        idkorlee@hanmail.net, idkovan@msn.com, idkshs@sdi.re.kr,
        idkskim@rda.go.kr
Subject: ¸ñ·ÏÀԴϴÙ
Date: Mon, 8 Oct 2001 04:48:39 +0900 (KST)
MIME-Version: 1.0
X-Mailer: SoftForum-WebMail 1.0
Content-Type: multipart/mixed;
	boundary="==SoftForum-WebMail-1.0-32BF5B923BC0B197=="
Message-Id: <E15qKJB-000A3C-00@psg.com>

--==SoftForum-WebMail-1.0-32BF5B923BC0B197==
Content-Type: text/plain; charset=euc-kr
Content-Transfer-Encoding: 8bit

¾ȳçÇϼ¼¿ä
¸ÕÀú Çã¶ô¾øÀÌ ¸ÞÀϵå·Á Á˼ÛÇմϴÙ.. ºÒÇʿäÇϽźеéÀº »èÁ¦Çϼ¼¿ä

ÃֽÅCDÀ» Àú·ÅÇѰ¡°ݿ¡ ÆǸÅÇմϴÙ
ÃֽŰÔÀÓ.À¯ƿÇÁ·α׷¥.±׷¡ÇÈ.¸ÖƼ¹̵ð¾î.ĳµå.±³À°¿ë. VCD.µî
¿©·¯ºеéÀÌ Çʿä·ÎÇϽôÂ ½õðÀ» ´ٷ®º¸À¯Çϰí ÀֽÀ´ϴÙ

½ſëÀº ¹°·Ð 100ÇÁ·Î ¹ÏÀ¸¼ŵµ µ˴ϴÙ

÷ºεÈ ȭÀÏ(cd list. zip)À» ´ٿî¹ÞÀ¸½ÅÈĿ¡ µð½ºũ¿¡ ÀúÀåÇϽÅÈÄ                    
¾ÐÃàÀ»Ǯ°í »ìÆ캸½ʽÿä. 

¹ϰí °ŷ¡ÇϽøé ¸¸Á·ÇϽǰ̴ϴÙ

     ====== º¸³ʽºCDµµ µ帳´ϴÙ =====


Âü°í·Î ÀÌ ¸ÞÀÏÀ» º¸³½ ¾ÆÀ̵ð·δÂ ¿¬¶ôÀÌ µÇÁö ¾ʽÀ´ϴÙ.[÷ºÎȭÀϾȿ¡¿¬¶ôóÀֽÀ´ϴÙ]
´ٽÃÇѹø ¸ÞÀϵ帰°Å »ç°úµ帮¸ç
¿©·¯ºÐÀÇ ¾ÆÀ̵ð´Â ¹«ÀÛÀ§·Î ÂøÃâÇѰÍÀ̴Ï ´ٸ¥°ÆÁ¤Àº ÇÏÁö¾ÈÀ¸¼ŵµ µ˴ϴÙ   





 Next Entertainment, LYCOS
========================================================================
 Áñ°ÌÁö ¾ÊÀ¸¸é ÀÎÅͳÝÀÌ ¾ƴմϴÙ!!   http://www.lycos.co.kr
 ÅåÅåƢ´Â ¾ƹÙŸ õ±¹ - ¶óÀÌÄڽº äÆÃ (http://chat.lycos.co.kr)
 ³ª¸¸ÀÇ ±ôÂïÇÑ À½¾ǻóÀÚ - ¶óÀÌÄڽº ¶óµð¿À (http://radio.lycos.co.kr)

--==SoftForum-WebMail-1.0-32BF5B923BC0B197==
Content-Type: application/octet-stream;
 name="cd list.zip"
Content-Disposition: attachment;
 filename="cd list.zip"
Content-Transfer-Encoding: base64

UEsDBAoAAgAAAMW8RStj6XscVgQAAFYEAAAMAAAAsbjA1Lnmuf0uemlwUEsDBBQAAgAIAJC8RSti
osbA3AMAADwHAAAMAAAAsbjA1Lnmuf0uVFhUrVVNbxNHGL4j8R/eIyC8siEp7SEIqf0NvVQ9VDm2
KFI59edsE5wWNc5sdtc7+z0b157FONmQOiY0iikRJrFMrNC0xk0Tqe/M7sYlXFrB+GN3Pe/n8z7z
GOCtNZMtAI2yNtgv7TPWNhLj6WRr5vKly5fgGgSxvs8TzwtfKAp6+jXziHEgKtklJ9J74oz2APTI
3JdWxiqQQ60LZCyeKGUuuPvhgG9DVGY7eDF7VBduSpbJr4cD5oBNrA3SiBaCGNPWTRPMR5kV4Ls8
X1bf+7UgAn3fWHaIQ/Wm70hEbgNMsx5EHbvi16CEt9lmXqdwKn+A7PfTGaT9ZL3zyFrXnlj3ESSB
KU+0PWCnoQrak8leC4JhdQUIj0bXJZb2GZhDhEwCr+05LvubUWsdgkfkEMiBXzNWyRq6RZHPJIZf
1AeIsgpmPxgS1aG0D+6x58VvwNPp4ZdZMayt7UL8M0xdn2aJcB/pD3AONiEcn0xzdcyTaARBU4z4
ZfgKL/ZTTMtO4yW8hD9V/4g6kjEXu+PIDFoJjsmJ4ESd2ON4Hr3pawvz6A/ArkRlvk2e60sIxOpp
VOVJ+COOxG/6tZAp7wTj/De/JpyICvYz94wn2FEepPrneRDM2sfCw99Zy3zojYB1MkDSIVyTfP4X
ieUXabNfPv1MzqpQSGc2XSwWw/HEhC03QlppeBOTUvGCCXyexXjXZDJ+QTqsklcXBZa7Zg8ZmPcJ
rEUXgy1sF0DgZa0La0S8OpYtZGn+45q5eL5FMKTQTdZjLfcY7G6KzP8IKsOEr7wd6zlWz3reCBlG
TslBMEa6TMlmU2wVsA+MLmYjKh6vuILzewz1mn1Ay9il0AaZFs+dey4OOUTCDMN7mrOJHBMTp1vs
RNoaCXhbRtvsr6x4SxAOvR3ntZQSQWShNx2vHjwDvpU2ltaLVtoe0tvBEPUB3MDbVAEnUyHz8UKo
WstILn0p1zRNj/EH42EaTXkbRXsbxyT4X9PDNaBdlmCtOaRKzgjpAxB3jUHjLxAqXCyVClO3Pil8
fKv4UbYbNJCrR3J39t5Xd+fufPPd7Nw9ZXZO+frbnLUiQVxh6+KMukaTUUQijSplIGOVUIE2OKf0
h7z/85KRZisM5cKKcow2yZrZn5yEkiJBZL+C5/A2Kr7dZa6zIZ/gCiHMlZTlj50NSvNAePKvylZv
KFITBGvhihggFkVUba+6aFeQIxnRWScYno/naka8QuG2HHn0JhQswj+ZitRD2S7GRH5UhMhNovFm
+IK3FXGk4aaSqpUr6qU+FxTYTIHFzx2xwE6Ef91SM3mgNLLEGSQtSQNpJIH+B1BLAQIUABQAAgAI
AJC8RStiosbA3AMAADwHAAAMAAAAAAAAAAEAIAAAAAAAAACxuMDUuea5/S5UWFRQSwUGAAAAAAEA
AQA6AAAABgQAAAAAUEsDBAoAAgAAAMy8RSui0+ewpycAAKcnAAAMAAAAua7BpsfYsOEuemlwUEsD
BBQAAgAIAMmkNiucv1CTLScAANtQAAAMAAAAua7BpsfYsOEudHh0tXx7cxNX2uf/rvJ3OKFqZu3E
LaRuqSW53syWLMkXsI2RBLYTUlPCFsQbY1OyScL7x/sZ9is4XDKQYORIslqyLi1kSU7G2CHJcEsm
JFkYQgiEhIkhhFTt7zmnW5IvXHaXVc0EqbvPc57zXH7P5Zx2c1PsC/1zfZnll5LVxDmW+TR5S8+w
fCU1o1fZucexOws3q5f0BZbRstnCdUuz8Xz8NKsWUytzl1In8Jx+NZutXmDxhcJtDC7fzpW1YmEm
e4bl5mJfsPwvuparZteYfjGnJ1YTVwSRZGHp2JKmnWSxmYyWK2m3WKwMWtq95E1G93PV6jfpP8Ba
fZg5ZfEap74YT95gscepknmd8564nVnJfMrm/w2u5x4VL+bv5q8xIobf1c+ya81NJkHLZr4X7oOF
Gl3BItYa+yJXqlRBQF8u3K6ucm6TfxdMNTe9zPSzlcL8r6CRvqxrqZXYDO7X2aYnMGQ2f58Elysl
75VjsRlWODX3HdN/r/5bv1hcY/lP9EzxZDUGItVPCtcXZ6CSWBlz0/P5pcIM2NRvJMuNZJubXt3i
wxgrn0q9x4QAGXt16w8NZ6xwvfgLi58u6FC+kBwEQFNyWRYeZhYwM2S5zGIfp4r6RTwW+1fhR7Cv
pQ0pEhlIn+vb5JUYSC5xFiqL+iqGJ2/l79Lw5AmYkYUmt1lY4cfsHNNXcpnyTVb9h0GtuUm28JG5
EicIE4lf1LX5+5hb+zpXKq5h9vlrEHF8gS0uVhfK5yGmcm5hbe67gslF6jOWvDEPgafXGDEIaZJm
OBuxmWw5e4ZfHYmGR95i3J7518go4/NUHiV+xbylY7pp981NigXL5HcYX6OxsOoqBtdMilOlx+jm
AsvOlUtsaZFty6ThSKtz321j6bVKjCVOacdypdidNv58dTV5AwSFICA2mgO86svJQnWVeMX4K4VT
8YvrxtcYA4WWjFa+XVdgzTczzNu+byA6eTAaPsQ6x8YjU/saVmBIXliypdWgVTyZuI3ZMfNy4goZ
+vH8XZbPFH5isfP6Ckw1HcvfzWikSratkN7GIChaJwaYHNktTH+/FE/FmeEspE5jmicb7qs1wHmS
zT7Fkitnlx6wBjDLlUw4q5pyWWYLNwt34duLHyRvQGl7uzz0Ta9iuGksMK05Lb2mP9aX5+9D8Nw/
MOw2h8fEFX05lanMsiGmWmzcbJwWK4s9YgCKs/oyCGFuUhikrxkmwQpp7WTyFkmhpH9ZXdWvavP6
VZNX7XLpGuSbXtNmDd+CAT4srq3zkTbBBx+SYYqPrwCs5h9yiBBOgN/6avE4uM3fhO1UV025Vzm8
JM5x7UKHyyZG6l80uhwWlzMk1MYdurpUEwtUvPDj/PusSABQyMfP1r1LW4jd4ZRLF3Pl2tWW2HtG
IEB0SH2bq5K5GU7SCuvKxhdn1gFp3cW02dgdpp9KJgs/Ytq5n8F9QU/NJCvcGn29vYbnYeG4cgI4
mjoL0cKUvzR9Mv/74gXDw8UNCiPLC/erl4trhpSTSSCYriVWmX6TmOGWSvfO406+UrzIikUC9H8h
BtXFBMMW6IKHivnUb1hV8vf5+7C+bAbuXoZXIOJp6eJn8IBH6e+zn+ur2bXUKst9XMM3MAXHWzTs
FEviqxA6JPwC6eqF9ENWvUxxEbIofDj/b5a+Mv+wxobDwuar3CYMk3g6UOcr2TNthjQaALoBlU1r
XI9j+mr6n/rvhJttYkDGIACfMpGzBpckCk5tTuMoQLPV4d9wwS/qxKUtPqZwgEotS8f1TPZc/kEb
t5VWgKjBI/00QLIwk7gS2xxtFjhmCdjPwH8ASwa2AZYK52MxDtskeRMYqpdj35qGaOF5iNv9J4FU
zU0zly3QyNyXhlHyGJNKF9dyQAJtlmXOxv7F7eQlw2MbQhHQd3BsYnTynal9gcjByOjYtCXybgRm
Tbxyr+ve6R/+a+8ur6f3r30eb3dPv39f8OjUdOTQPu+RaDQyMe2dnJiOTo4HI9P7jK/7+sen9vVO
joTHIzSJCABz32UWYqdb2TYrfew2eRt79S+bLlvd2+B8xDF3Nv1mZqVSeiIe/19+KN8BfhwD0laL
2tlcRmnpioYnRtlAdOxdprSy7WbkQYR3/YkLShm1WCyFGXiy9nX2TD3Epz8ARpxECI/Bl1jiDB4Q
Y6G04nGkazyoV+ElI6OMGyY3VCSsPOAWTnFJc2Wb6hXI+jJb+GkOSmROBn5qPzDSSD30x6UsWzqj
3eJT1KjwK8uUWRKSVNfAAtxmtbkpfxeoSC5nmAkrvcdHJq5QHkPDLwM+c59k74ID4D2ShFhsLkPZ
kMkRpDWbzeYykIG+vFhgu0lSyybsx8+eO4HgXL1A9r2Sf2R4KogVj1djhGelc7/FZkTokKHtzxKG
dBBfdGRQ4N7royjxZbIAGvklA5KIhP5l/gGrnkB2dQUyLOhApHOfwKUBQN/jn+Ymbb7wIzirPNBX
yuehkeQJQibxHEt8VbqGa1w9xGb6Eg08VpwvHsdESFZOIAmCb7jdboMpukWICyIcfeHeXFANfItH
smWsbIPqsheLs5g78wPYKd3nwmXpP4y7pQvMKVu1r7HQ4vFkkrIhpFescDs1S47+CQmcYUEGoOUf
1uVIhMCIyNA1DZXCNcTI1Dmu+PQVwwxMLvSzuED8shb/kegk/8pzqN72fRFcoN/k7WZQognF13SV
Z3exjw1bbm4yARSwRYi1Piq+zDo7XeYqBcYIiIHICx+acpEt2j/0R8xrRObMD5gjdozfJV8X+jN0
C5VRGmnohp6h0LZASaemJW+hLjETVyMRLn+onYX9gg8g/q909RE9edMg77B4fYFdfVxtYs7mJtWS
uaN9xJNNeC59FxIwLuQ/LZlg7QVXoGxkvXSDSrUPBRmnhRYvpx+eizH9Bj1NM1E5hLAl1o6nXBbv
dnoOhDt6e/os/iG/AbLVCwaPbgsvAinqsuSSKTWblbMJZ4XTJRDvrwjc5ssx8ncRmsU1pHrpWWRw
J9n//LD0rWAR8Ps65UtkqIi15IJUzpG/LS7iIk2Af/xYnDnIYnkDc9ssIj/Dg4Vfig/0ZSNRI9PP
I2+qVIXcOGeLxcpsinxfv5orF2YozaBcIxuHl1yoRezllIaLdczjCwUbZqKCXONYcU3TLBZLA+6s
VotkM9Uik1j+buXBOVQ3D3IZHjTFb/qJRQt7reEqwSQHOyyt8rfYV1RJljgIEjsCkblNzPBMj5el
mwooxpRYnGDpolhF4gMaAynIsThLf4kYf450ltFIPppmwqsZZdnC/cRXuAujJTkRXZqh8HGWCnY4
uqhNwDFvLTQUZlxCmBsMxk+XtfgZMT+AuXiNscnDByajltHxcSy7LiCY6sFIOLp/8l1zIbiCh6bM
oi1+kafD8dPa59AmlgDu3wyPH5DGxw5EGp7hZSJPdY9OHomSrN6KHJ2/j99UjWu3QGNiGpca8gXO
b3B7Pz0JedFzeJzzufFBrDb9cOkYaex3PlfsEtBsgVcghtK7BhwAqL5d/cGQhyv69eJF7ec3YtTt
Edk5DazN6/XV6nDB4znDryjUx3FbiEJQNfyPyBjIxsPxZRBALKq5pWAEIa36ujwy+kY76yFmkODD
roL+0J4BU6gx8klxpWFgArheeWDfXr5eRuqdSvxhWCwyYFhyYW27fh4p2r8Sv2bubC/MkPXwmFE4
ARtYBh/ydnp46UH+bmqleFfZjrRfm499kUyx7dq9+O3KI21WZts7ezo9BOXb+zs8vT17/fy7dq+s
acf4+OJJHcVySUuwxYL2TfLG9tgd7Vg5ZnOy5N3kXcPHmAjiCzUHggyNK1wan6WKpoxL8E+mPaR1
8oZHNsuzIW6hp1FXCMRB9KiS0NOzxZNUCFYSq/BuTrLKL5raoQSC/z4nunGU6VY/Y7wdZ8IX6EgM
4LbBXblOTX+CS3gDHu9O9rrf94YIAYb1Gx5VvZy4aS50fY7OCmWChprqyZzylfQHnC8E4AZWU3O1
lIpXJZcQod2uPxE6LItabIFX4w3gZoJYela7084W/8nKYG6xsCbETrGc1SoeY80ChwTbDSMYCrtM
+TpSetEduShK5pHpw3XMQtnFyzVcZKZ1lo4R6FPjiUJ0rlT+qGaiuTJiVpXlr2nF9sKZalx/3AZN
5jKLH6CCyGRTN7NVwaewC9i9zWql7o1ohlJ1A7rUI+CFPk+Q6zZBGbIpOpEUL7DYGcgUpem3rMU7
HR1nrzDP+PQrzBcZj0xHRN+pvLTYSlwyCvACTYmEANS6yqmPyZtPAunLMVGtL9UXlylrEOVMFZGp
nSHhuEl5lhC8fsrtKNwWedxJJJxLRvU2f5+yr8Gefqi11qwjmPq0ZvV8QdyKzM4BHqt8uigCBkt/
zSPrBgMy+rDITcHVJX25MuuS29jib/py+ZTcFj9NV7SvYYHlU9psaTGXsSTvZfOVWaZYUGf/PPdd
/q7MDI81OqPJ9Cx7Z2yCMgbuXeDCKE1JIK1UvS8ZPmo0JQVyC4XUC0Ssrjivf1m9XPwmf42ZK8Qz
/8GnoJVuVVIayWr1Ao+nhRmL5S9GfRk4MoHCkqeWrAUcuh3b3a5WZsHXCV5ftvBvrTKm2VxeSlO8
vJRq5aVRXUpGdSmhupREdamAgPhmZo3UKufMEodU0PAlfcar6Awty3iu9F5sxnAhtk3UoNsYDDp5
AgqhTlW9TDUqFNEbtljMp/WF5iZCbpF5YkZKuwpn4HR3in/MfWfWhwbB08DghsoXIm8seJub0lc+
ugLlI8JhyCcW1lL8CY4jpoLTFJIUA4ykgDeB9M9xH9k8kgHeFxOVclutWS1KFwDyNSyTVy6YmNz2
Tmkxn6gZJGIGo6DB3G6ucm7WAgQTqyx2Sr9KewCPUVSeRNSivhcsOP5P7jeFD2PfGpsyL72EscUF
tvRRArFDZEH8QUYhrlpKraTOlt7jilmCYignbKMEqI1ogEGOIjQNyYITpq5dG+v19NemwmOlbPlU
FZZuaUF4+YIVHqaQNd6rPIKb6MuJK621aJ+/B7/DtzmewOkX84/ii2A0eQe/ctdyqJquNQJFsjD3
9cIfcuGrwnmWTOYyJAUujrkv83nquD4qzoo9CCyVRzZ9NbMAfVV+q8zyzJBv4phpLvViXDYH8LAF
RfvJSlUopbWtfweApY0aR40EIKzk71jknAaDnfuFMhiiAiTXc/lqS4iiWiuH1vhpLm0904Ygk6uK
IEsMl6ijUDgD/YiEXZjIsmCnLyj5dgUtAz2d8dNtXMP/9V/0i/FgTr034EpqtXg8Q7tdGQ1UzP58
W+zO3NdEnLRC5D17QruQO3ktHZ4Qg7S8u/o7e7osweEg77JDry20bQSSolFLfWCRGLVyxXEF8ayy
1nYg5NZutbFqPJsBmNCaqYFwi9K8ehJAairf0+b1x9k4V03m5+S9gk4zMpu6f2ya7whwoxc1MGE8
h2c24Al5u6lT+wsHZjGQjO5x7Pv8Q7IICosiWIuJMndSZ5M3ZNYWRBx4ebvAW++eYGhPXy0FNIsv
s+VOHXcrq2XuRdF4rvljPSvMZisfpc4qonapvPQSS5bxsJEsc+/OfNrG4wnnOV/JkEGYrCGxO59K
68vZMzKnQD1sVBi1GIQxFIAwQoSk9NcgyJt/+ACpIab2umgk4fAS245gWXlQeoCvhRm41Ox2Gk35
YzZr1uoi2Mb+vrD2em/ojUZOzF0UGiPCzLkGrf1GTyV+FSvWr5ayvLekr8TOs1iMl39enyTKWT/f
FyDENXoE3KS4+VUvx9fgY4ZtGyPFDJ7xsfAUGwy/HTkQRYxgfeGjYfa2YrHSbcr0qOygrQ2zw/3y
y2ykvTYHTEHUE4lzcBqRX6JmNR+me8hDesdGIhNTYxMHGWLRkcOUUHIlz+c+yZV4Q1k82NzEUzov
bz+bCZsZaqYOjoXfGa03XbCwkfZ94Xf2jUwe2heZHtnX8IBRlLQkrxb/EBtcv7TWNyFpkvVziBnC
79gso+FpM3ukYFQb8x+ikps8dPjIdCT6Fx4URblOm8qiiaAva+9zGZgR6Z81mdHmF26IB/lzGaBF
cd4EC6bdSaGwSX1G+RY3yDcnp6YnwocihA21PlVzU/7vcGxqBjQ28zUt/41IXQ+MR94dP8SmItG3
I9Ep2BP3z+I1Ss4w/vBkdJo57XbW0DpciC3XCAX9gb3+AINuV7AsNoDHqfVHlCsPKrNGe5l22tcz
QGcKCmRYQISNejLSff39xRmMHwhPv0lIyVOMmoBoRVCmZ3Cfd1ffBmU2N0ENFzYqhx43FkuUofDw
O38Vyyap8Ud5Iw6iXhBtfBTJj/QbNY3WjWf/2MS+8UPTk5PjUw3mJUK5+fS2kcmJA2MHj0TD02OT
E+wIt2aaD6Y9tU1E1wtkwbUHIw23y1UT3GqecSa9ZjDHtSuus5ZCup0dgg8qtDjkKI2SLa5R05QX
C41jnvvDC551Uh4/dDBqCNnbvq+z1z80fmjfJkE++eb45EHWYu7LVYoPkK/zOFF8UHyPNTKJlWw7
MtUgEoqfOcpIqKNCdQqBDKLa9JsRNs7hImJYsQFAjHbYkbZQNMAM26amw7Bl8QiDsg9PvhOJHjm8
jfFeCNFeL/BtQWAc8IfPT9NTd5R274dJQeL332rPEvHtwenJw9sDkWgkPEoqXE+POqSc25q2zK1y
mAFjggSfLxLdxhpasn9r6P1q84BlWYBtvYNKVdpGyFs6w20ScubfDKei8Q04mTzO+1OmqxhjRFCq
XjayLEpH+BWML6XPxYpXTLcniPurCXF/5eDTsvlaa+yPpWP1EpqqhsRt6lqyxM1NaLjAiseXZpce
sLnv9C/4Jkm9zDSzmeQKbwAXr5hIL9gzTu5slIGxcnPV2kmKs9QnNYlXY3cslL7yAvgRbyvzlgx3
/gumUAzsqAuP0iK+rUTh3xxfPJm/W6maSbYYU9tFQpGNR8iRqViuCFYAarUlos4XW4W06/xN7JjY
9TBKxc/Ebr0ojRALMIi3bijOX6Ran5w+X2ELf6Q+sBiSKl7Uq8UZyoBFp+mz+feZkn5oYsvlhjya
Y3b1kvYzD0jG89eILu1iGTvEosq1sPglBJ0HHJLMVgMRM2kZs3NjFR0tNv++Np+4UpfIUiybWaKC
f/ECLa9eCL+8+0g4+hbzv3s4GpmaYnbkeW32Nqv8Z3F9SFweCE9N8djEHaHWoaSurZ6D+Bc/qFZ5
q5aE1daGx44choVHKGGaiZ+mrbtZhCzuX8cwcPe7dqt85PDGFIJffvsA39Y27ICzAcgwt56bmxoG
mdPSajhrpIDmppdeevkFfpqb+Pmejx7m70Ki8V/51o/Ywf6q9I2+rC8vfkXHW1AYG3tLRQp3xIqh
oJb0P5M3gJ0mu6S6L1prts29hQo9DAb8HzZODB3gJ4b4+oUWmptMNezjJWFzU03spkjfPkCxm9zk
Aos9KMw0NJDI6EU1tcyrd9xiWjV9GazarK7mpv1HpyPscHh65M3IqHHcq9b9pJSXtiGph0+blSAB
tSZ1jS+Ys1j3ulhjo2ogaOGBZ+6u2LJF9UhOhcBD5v0JZbxGXpr/O2FAPWkhnYv9lG+Zfj9fKVxn
/51aAqk5uOPcJTrbWEms0nkHwYD97QMtuHsW1+7yxhZffeHM3HfGDuIcHRihjUQ6hJg4x6OiOBLB
iG7sY9pHEVUGaQis/Tp/n9PntwWXopVOPRiURoh3ohfa+OirL3Y3/1kERZFjHHFkz0WQdnCpGY+a
6FsW+xlF7NYf2u1oZ/2egEvq9OxQpR2eXrsUGN7hlOwu1Yk0/eM8CmyFNmH37HxKWiPoOBxWmyTb
7VaHbJMUm+pyWEHIrrqbm6qfJG/8mXffPmpn5AbVavVGpWTfmpBvuEORujxdLqnXE1Clzj2vqZLb
aQdD2bXKl+krvOtotdqexZDNYbVKdtnlssuKJLtdstvmIMZQy/V397Knk9hEyKG4bA6bW7LaZZvT
6pZkh4wi1heJHGaB8NgocqDnIGSVrQ6r+bE1N8XKhZ/0x/pPz8eHZ3ycZf/Qr7bZYIYi5KXea+d7
d/ojVjiuzVZm+dbi5qFeRQlIgSHVLXWGvMNSf0f3gOR0AOqX/lb4jR/aK2vlD7XZ4i9PY4B1eTpV
yevpsEtB/5BDem24V5VklQTBkDblPi7ebUEcuFG50Pr0lbhUVZHsblV12mRJcdsdTtUl2dyKnYLP
mcwP2udajJWxrnIml2kJHtl/KBwdm4iw0Nh0eGKqtU6oyzPc5/F17BqWnCF/N4X/Emqnf+RK6UUq
3JEF5S8mbxTObc2GVVGgTyjX6hYawcdlJbFos+VVcQgC69JXEK7T1C9l2ue52U1k1jPB03xTO2zx
q8XfyPLXzS72egyXbmey32bt8PZ39/S41D0Djr2iUggMdPEAcr6FQLVSbX2aQGHMO7GAAYmWEbRa
d1g9zk6ehRDr+orMWnwU7gORsYMTTG7dkkiXx6dKIT+0690z4JYGPAOq5HDIbjrBeS9fyVABTYTG
wvvHJzcTqdHZKftDki/Ur0qBneprkrePwISlfzR2BlnL3vChw2PRSGs70jr9Bkt/kEwuaetIQECy
FPT0ygCCkCIFPD5FUh12Uk327lymnXYlC2ss+ObkwSMT7aHJ6fA4GwxHN3ucStoFJNlt9X9Vu0yG
lridjsU/zJXmjsvP9j1Fcamy6pbddhXFAguh7giFxyamI6PPHmu3SYNqqNfbGxgMdbg65N5+ntPN
3xfnZfnRg6dT4OIIkDi8nqAhDsVhJ7/LfZwrGSC9eBUGVWnL39Nm08uV7DrcN8zEBmy2QiZcLMa/
dqdi4yqGnd5kzwdFVqtL2jEAvLe6XaRcbZ72gFj+MtPKqEJdTGLCare0j65uv9Muyw5HX4AXQ3QK
AqP5cZ9MNvUH20ohU9snCANlWLfidKkOF3X92YbTSk/6iMH7IxOytD884pT2H/lPVfof4VGFIguJ
MU7nr7intT4HjssUIBECXHaHKtlssmx30C8r10fx7vMTslrdTlly2xTZAbsEHbsLkUYmOw+OHRoZ
mz7KSLVPoScIud0dnYi/its6uJtQsH7m5NlMOFXVJrlIHcBBG5kCndcr39ZXny86YlbFJSl27p25
TOE8bfw919AOMusOT0fjf2TFIdfj0vNZY8dwL7xix54uRfJ5uhDjhvvs0IebvJyiSOYYHGOJ5f5X
i/fPXiaXM61PNGur0yFL6/9xOnikFCZuWLiTvS7s+w3WIus3WrcycazEoSrcxMUxCDp7aBAhGkqd
xrqxg53eLtmlIG3Z3YGxu/d4dvoV1p6vpNLx08+QRJfTNxAMhHq7PXLHoFfZwXvgvGXPwOazJYkc
xwpVOpHfKE6n5HA6XcAJSpnMDek0NUifjQ8kOMVuddoR3t2qedj3yVlurQ/7f5DpDoSj02O8G9gX
Pjg2wgaik8yB+nZLjgbo7Iy/P9jr9Uk244PKL8tP0npfeYV1HBkbpzSOKBSOlc8LDyqKWqM6m14r
nmWqzUZnH83zzvQhvIpf0j9vZ3u9AwMdDj8mxHygLhn/tzHz6Z3+YQoHkf3vQrzWd6npNTZx+Mh0
Q63NqIu18H3xJC+QVhAfl8EfR8Z2cRS7Xh1PHJjkm/bnHhfnW4TYXqnvc9Mtvpfe3ESBl94q4Nu5
T9BYMORzWa0y1C0D2qwK0jqnkywY3ogC/55+grpCGG7fKGEDBuxWmxXplNXm5A78tI/XB0nwpEV2
WZk3tMeKf+TOjr6OQTd7LdTd2+9FUOmRgm+GoxGmWBzS9OQ7WyK6IltJNi6SD7O6KbopnR2Qusct
AY/BUE+w2xPww4A9o+HD05ER5g9PHaXTN95oJDw9SSkDVmQTZ9AbSdtsVhQzik1k6ulbyZXE7dgx
Og3O9MdzaRZ7PHecFdeSSda6BWM7gjZIwu1C4R3c1RlifZ4B9pxoZrPV7fPA2AQdEHC7nnOsyw0l
QCTQg2pXMflSJb1SPA674ib0bALde/Cg5IEuJeTEDgjBqoKPuS8THzwPFzUyXXbJZgeAqC6bU7VL
voANGi2sJW+Usvw1J/KylkKS3sUonH4SHA96HdahjtBrkKSd2gXn7ibonDC9FdRi7EETydYnBVe7
00b26JZcDrfiQOnV3NQXFJou6NVqLsOFQgfD08v5NabqmzOmLq+6A9VoaLcqS50DLidKUXtnR0Dy
Kb4hF51L12hjQEh56UdqJT9dLjtJvH7oSAIcOW1OGeUkCuQLi4sGS24nGwjselbIdjsVuwN5JTzI
Cs9z1RZWI/Lsohapi1V2u90OMu8Pq98xcO94Xv0OI2GxYWZrHaWeaWE0tp35+7tQPXp9nb19fZJN
5p0G6UV+gOo/02nElr1jU2PGyXHmR6oePRwdm4o04jkT0ZvjeR3UzSRPsakOUhO+vWAWJWM+ofc1
euuH1Vh6mvSoBQHFc5y1OQHQzmdA7VafBuuxkgG5iBH4xGBPv2/XYJD1IYaV4sAM6sjqVwu3t2Ck
Q+0Y9kpqyOlFIT8wFBiU5KGdgx1S1/BeReEFrH6K8CL9KSrnVThX8XhukbX0jY2PRyYmxo4cYv5R
Hrtbn48k6MHhayyCNGxoV7+P+X09oZ5d/axzT28v2+sPBOkHp9fpVAZD0mC3T9kheX32vQFJ7hrc
6ZNCimvYt2HJAgjoSh41WfoHpGrUjac+wCXKg4letxoa3C2Fdu/uc0ndQzuGuySf6u50SgGXfW+f
Qe8d8T5SA711ZFpkr8/sXrSHnK7QkDQ01Ne3A9Wyb3BIGu4IuAalYbsytOOJ9ChRqlzPluMrNaoG
vU51oKtLsg8P+3ZISmenEpICiuwakJSOoVDXZvk901M7naEur+Qa7BvsklwD3o690t5ul9on2Ts7
XSGAOZ2vG2zk7xn0Ah0+r1vaGwp4XZLPSXXPDrdzx7A0ENjb9/+Bv0b9/jfQy2YXi3SEEllMtspa
6MRZbCbxcWsDvee2F6LHDRp5xJZ+S/S8wz5vtzTo9e7eK4UGB0Ky1KW6Q8PS0LC9T91Iz8F2BQPy
ExGY6AHp3Q5pl7+P/FZ22BCKHE6X26DUHxKZ2eCuwM5gyEM+0aI6nZSutm5GEZR6NhVVtLPNLjsk
m5t6mrYNlMSmZIvqsG4iUqPkBiXZ6pCdNvuLfs2N85L+Pv5J+l/rUk6zHyM7ZEVyAb6wSmPT6DxP
DbZKJHyDTup48ILE6rS6Ud9Y7YrVmKVynb/9IN4LUy2OnfUG4SCWH0AaYUdCLLmoxDVmcj1xJhdv
OclIFexOivaYiVoMix9T47rwYONIL4I9FeHIUqBXRZVsgOY6SeYdHPBw5vnHpIOogf+4G0jRw6/+
hdGjyNwkpJ8OpJ/1aUCGuc3e85MzyyfkkS9au2YetrcnuMfTyzo8wR4vP4TWYieIrJXjkKPTZVPd
qtVOZSSGBXf3mvvlT9C2HbJEfFRdJHaMQDrwAyrKHSjy1A3FneG8tZSIJ1ROt1Jn0BiMmuoUHb2D
vNYVhwaBltIFlScSz5M9rZvnRTsNEoq5NBLjxO2Fm/rjp+VwpGLZoRppAH7QcO1rlrxXXCsvAC9j
36dv0StZRgi3tNgpdWqtp9cyNxC7DbmgYoORJFcWfmDJQr7CBydu8+EUGlr8E2zk6P5ItLU2e49v
hy0o7XQBxGD5NrvbJpsAlPmBIltiFc64gQ5rUajZYnR9AiFAodPbiSxScUoeX4fdWEFlMZdZnDXG
iSFPKBCoeqQluBXVpVCRwaPa1gy43TVahnmqXHKKE2XBi1ZkcCAYNLwbk9lqVeE6C8MduV1BlWZH
HIBP94b3s71jkXfq1YvNOmT4+wtmb3J8bHRwMvqWEfr7QwQRZi8SF2hS5gRoMrtsV5EOBvxd3l0+
P+73BXxuXBjo3hXaZT5uqz/uUOnxTr8ntCdAj1uxNAbMVpkTywRQynx0z0BPfxfdtqHYgRrdDNpU
gNhOGbc9/T19ntAuriXqMQAMZfwHdT4ip/X/NZunZCV1ltosxiYT11QLZQSttc26jkEsjEKH7JRl
SXXbKSnOleKXtHm7bwi5qroBvcQ4lfYlrarMO/NWWaYA3xeZDo9QuwL58hTzhqPRcDTMbHy8sUHQ
aZUHOzolsgN4g+Tp72Z1DEPO+GllVkQ5M1UT4/p8nUPdyEGd3YOSOuRW7NJQyO6SJWVI7fZRz2Ry
f4T1HAofjAQi4dGjbK+txrQg4B/qg+6GhhS38YE/wxk6o5HIm/RW+tvuJ6BPZzfJR+LIQ4HS6ZJc
Ljft8jZMGpw+Oh6JNsxqjN0xaBOyVZwImIpLpneyZSvzRaZof2uvw2LbYtvB5/XLCryc+vT5SvlU
aiVzenM7q/b44E6Ut35qIaBSpzqwuanyoHydjnXEUB8oGEgaN/M/s/FBrHWLUQ7JTQVaaoUO7yDr
lMFWS+/kwUnWN2nUPmags0sOmwtQbHdRF94BLNa+pn4rNfr0ZSSs0N4KLM3BE0SjpekBUwHPaxCh
Q3E6pK6uIOWGwIjAm2MTk/SnTGwGk+JYERLsWv7kk2i/nhqUql1CKUnbnotXU9nkjdRK4Udu0euQ
09ibDwCsVUV1WwOKg791ofhQMHqGGD+xXHtY9LGQhcAirE5ZFbeQLYsWaHBwwL1nr/m8gQv2EXkk
PDJKTfuX6f2c+p/ZMf7qgDhfxY8gidfVMvz1EUBzLFY/C8v/7JH4OyLxhdrf0qBzffEF8xySMjp1
KPwunWkzjprSm330tp35Sh1t0F3nr2jjvnYHT9joaXG0+Jo4VGL+MZVl87yqMgqiBgn+hkADHfPt
tVjtXV36AyHiNXSIC2sQwqEzgbz0Ppd/QG9qxvmbeqfpUNoyvVRCsqJzNqZwFhool2miUpr/FQV+
OCZ8ZHoyOvaf4sTsyORohO+2iffNL4i/CqDnjEPj9CLFivkieO2PFJC4vzLeBwcbDX+sxePb1eFn
5BDZE9wqG33BNNDBQbvwUxV+JykKLKZzPDz15lZe1+jfvTROsqkqbFOmzT4K8ZR8i1lF0m5ObZU3
dPq3mFVgykA0cmgsEo1s3CUwsHBoiPxJ5R/yd4n7oZhyA+C71gMSwN7Fp7S5bapVcjlfeDXkgSpH
I1NvMU/A2x3ye0OUNQPu3pqePMy7jrXesVzb3jA77ZQIDLn696DI9nr4BaQygc2HX3h3YosUlpch
jKqUjn6K1oTa9D/bFs++FTlKhkas7OxTpSHVZpMC3bYOaei1If4mdL6izSI7o78CR+l7O+N9Inrt
VL9Kx0i54RpHVykZ4+ZJN/gfgKmJwTt56DB/6bKrByXBkTF8a1HWs29KxCm53U5q5DtqN02xDCpq
d32EgUNexdepyH7OLb0y5PMHd8Ifytc50zydLR7PLNDZvFbaVdtiSlvDFlPtpme7l2y70+ewexye
TbyYKmqYFEEqVr5cWmTJE4DvU+W8OKq8eTp583wbyb5Yc/zfUEsBAhQAFAACAAgAyaQ2K5y/UJMt
JwAA21AAAAwAAAAAAAAAAQAgAAAAAAAAALmuwabH2LDhLnR4dFBLBQYAAAAAAQABADoAAABXJwAA
AABQSwMECgACAAAAtbxFK4tEPLzoMQAA6DEAAAwAAAC8usDOv7XIrS56aXBQSwMEFAACAAgARVpC
K5zbyvduMQAAsZsAAAwAAAC8usDOv7XIrS50eHS0W21vHMeR/k6A/6EFA4HosxeiXnKK4bNByI5j
xLEC62A4MPwhdxGC4II7wE4Oyhf9lxUpyiTF5QxnZrfnvWffZiWtdkWa5pskUqJJUTTFFRnKS5qk
jKuqnpldSnbuQ5YrgOLOTPd0VVc99VRV8xWmbKgLTNl1C8Ym58Jm9qq/Hs46oywYFHfDWWascE2v
63PdXa8wsaKvst4T8PF3mZjCyym8HkybmbDuhtlrep6Z940Vt8DM3Up/riZvzQbTbkHZYLwhVkQt
aBoG827lgmDacfzl7i72Y59/a/swfIlZdSz/upj308oUvEY819dZOeSlsB40vYor5CIPD/ypDzw3
2D+Y/qf/DeBEV8pjluI4oq4uKf3BotQLLOMtxs6IFVQAqKNXrDBn1NpyrTaNssHBDiziancX/mPs
1VdfZawyGuwJi/FNo8YK0/a2uiCqqHr8rq3zTTEvqqWhaPdwSKJ/pb8ywIIgaDK+G04ot2EWzfbX
/TQLr7qFcFGqmMnnk/fRKDFkGP4Ts2pseg3YdH+UZ2BTbup5mKXKxLQcmmKX/vTffwyDXE2dyV1l
+pzfCOtOCdTC0RBYNGM0e/yGd97/+BMWHrhFWE9x3hh0tGL6uKiVbmv3/TTYKU7TA9aHBmZxt8DX
SAf5sWPHjkn5pHZ+7PNK8mGMb+XqkVbartMthjO8/s9/urs+/fjcO6zX3P0MJg12g+nKFnuDhROq
efykWOlJlmnx4kgx7Yvsd8x/wjN+OlczFRGCN4masosqrVs2OALKX97h/bCxgyz/1Gs4o8kcYoxv
gOftMt+ojEbO6g+DKeKM2nB2m/lDYl5JM1G151WrzRG9CuixxKw7oPHwptOMtNJJFZwkFaiatyr2
AYKCLDuOIvVE1vWmqKqm2BccjMl+ri7TUlOpFOOlygBcrzEx7zh4QUtrdjANeOCWhOtM8gxe9G7x
Jo11mr7R3RXWES9W+BrgjuVwHn4trdHipXXSjn8brIj3K1Pwn7caTrBgTinxDExgcT0vqqDcYEup
wn2Esu4umA6HwZtEFUBSIbUWFgtGOJnM/lZH1BXr6xTpy5nUHoAVOFbBCR8f1hh7s2A74LaHnwE8
V2e4wqwtY9MXKveXO7SseF2naV0fnD/37ge/Y799t+/cr17YSH9IF9HrMcT4t0F3utAGwYYDG7X+
pdwLHERK1ZcROUDVpeu5WtDwdtDaF5kRdnd5DTGNMoDeiyN8Ibvtfe1LDwgasEWFddjoXTSVWgqt
IFyOLVzZMBrhHft55AWpDm/OGVICBFLNH1I1e/UlFeBFsDFaQpXR4oTLTDO7jcGrs4v5uVxMf6X/
pYWAdcjrYB+ibqwdto5IOawyJuZBm/hkiG6vjCr98KS+Kt2o6i2qS6nY6vQ54fr9rHJVzINLimsw
EAeBznEakFmdCX4QNgic+Ag6TKd34F9J6PJd1ypnmDYsqvDfYdnJBOpKA0wi2gbXci3w8IKpPCJH
CSF+M3ENKI/6CL2fTEsbJ2WIscoA3JDPRqLTkEQjgOb5qy1DqyKgdlrKsyilMipWnZ0I9RPI9peD
v0McKVxhMjLC4tzC+LOcjpg1cWiHkzHBTnCFIiYEzkpG1MLZKA53dNG/kMHOXAsAi1mYMZvioKMv
6D0hMaiPeWWeye6z4xhPxRjuQ2mIZ8AmPJ7pOf5Bn7zfw44bvlErGD1kjok6elOARlcBb9Bs9QWe
Ye/0/Xs5pDgi9edMupYF6gXrxkcRzxISnFCKk732E/Cv+M0M5mkPU9pSZBvMewB+ZTF1WazADvFN
V7TNUnkEgX6PDMy4yrxmwWalEXm15BbUJbBJOw1W5xbAnaJwBlF+BfY92AU7n2qbi9g8MC4VmB1g
LrqHseY1LA4rWTKMVGv1J1NGzdzNK7DOeP3gKN5qSeENviGqoFyY54njupZ09DwxxJg1xcwtmsva
0m66VnYbfQTR3bFEzZvW6xwYqROCBYdTsUV2MiT1SnoV+Ynh288jZ4FtAMox498DRmuOBE1ugvr9
odyYkgbN9F34ZbmIqAgkAZfWThmVUW28OFJe/pfes+AgQ8qG/TyVMhpGA28WJsCD+j89jT+RS21/
Bk6FimVBU/kmYr6S0HZUTEmhYO0DUXhRRuGdrQ14E4Nf+31tHF2iBYBimowLh4FFF6+JKbIUR7Wf
g+lFj9nte8ryO7mb4A4YEsDINlg2ZK/Jz1udEg9fJwWUnAeQbSCC2MOEBwTEW6G9jUg8Ecd6bdiv
EKXVVzHMAk3EnVimJAgfbn0r/93etkz43t0lVrRRtPSyXtdmWIc5Uq8kScDRt4Duzr8oBfkGBkUG
IanEQQQD0mQWezUj5wFEOZX7Hvh+M78OXAgSqzSzvBb2IOpbyyALbYv5yLmrmkAFQwUu4XR0mQWL
/jJkdmGsq2CA2wn9lxON38ME/TVUxRQLhvAL48+yqDbCsPtyVTHZRcXj2o/EkSWvKu4HDX29wl+g
u/hN2wQSY8mFPUBMxWcJmfgaWrKlHCiP+WAqltc3bQMfw/wQ7SDwyiR3R1dNBOy//ufzi79nvcxb
NHwqSRD64b4EA4A8U4Irt1PmGs/CtqiPw+e+kfLKYLqQwBGPYoguqdRP5a34QeRl9rC5FllKCnMV
5bbEnXv+02DAMDokWiKb5FmYWUA0D1IapOKIBS96JiPeRNiKYYN526oDoIvmXcqBt3rjIDbBUzgB
D9gSUL4+xE4QW+xvna+IhmVDfQ7oI0ZdGgd7Ch9r0p0G1iZT184KelZiz+6PoA6wwzQmgBQGYO2o
BAJOCzN0Swl+gHXG3muOuA5zw/BxWDdAE+DOJDbPKUOJpPJJEDecQLWBnZrzwNFrxgY4l72axQxI
G1bSME5dqnArgHdJJURArOclo2jpnzQzEWfNncKzlnokqUMe4F93xUvbr972h/yGzHekGJiUgXaQ
5dCGEm9BpSG10UYpOwdd+tcLSy/YQRKgC464FoFjbPEp1BcYvL6u3wNDkKlhp4U9Kfmlc9e8rzxm
vARrOF4ZKT5sQRF+IxBEqogMAPncWnDl+Ns9IJNlV4qMC3uV6p7mgrLxGlMU2FN8BKDf8HMPMUdF
P4IZMc/iqyyYiWtmxX6VM8t0mpiHYHriTKoOJi79XhnDexNQWCyFzyTgbZiZKFlTNlIEIGgEAJNV
AnrwOwL9YCZO9wwfglKNgSNvwGyuD2ssDeFYAhj8ZpWsSOEwm9hXZyX6d7TM0a5vyd9yNZ4p8ZdS
aRnj2yJRUs0yH/tP1IVYLN7kJbSMgiekKljkW6WZ0pB+B9QR7V4QxIqWpdMqC7LqfZbVvEbwvHN1
r0MSSurmWuIa5KnKjRfsyRdMu2mOJIEZdhBlg7VzO6lgYOaeQRTFtNoaK+XFvqgGk2R+kNeq0VyG
oXLafIgtAlCL5hsXTA3Bi6i4j5O4t2W6GscbUcXcBis165yTv3JurEY0mlHeUzOuIgTHIygNAKC/
ld+JpkpuFTThIuMmTiKT6mE/H+FanDCTlWJln6oiSNWI0MhA3pqr0l+aB9Mf31U2qPb5ySetJKSq
zUQvThQ5pC5JuQl0E7aTPEjPnSxvsDfAevQFXBcrb4gwAKowFHjejr+LAI+xzJiApAXg6mnQTAhw
9Gb5NrTT8S+BZptV1YRfINwVAQnqbsm6Y6xFKm33nFRHkbllXJI2d3DiZGbJY0V1/Jl1kP8WuE1u
1X9C9YIYqikkVgGtMBNtcXLJQOMwdahS8jZ8Ou9gkjme+sPffv8F++LipUMoIur6PVZY8q8HWEin
1BqrvqyFcSDJ9dyNwg+IH1gPRu4M3GWZZ+AKL/lPXh5QHqvskL35LWljfYQx5ljAqoNpgJlccPht
BoD2PM9FborlGElQ6XF1b/z5oafRU5ZBbWTLwSS2OWQ5FOiB+bx90Qm20UCMFQjyj7HIg24iq3Gd
174sQXpPnSbkMaCEA1mSaQEcXEI9rXkNDDkhy17DzkYYznqLTJHJCAiX4wAH+aeVPUxBNnm/Xlcb
b8spVE7Vuso+oJJSjQIBzeqMIs14lkvHOvl/PoNX5IwIT7AmLaqUeLnvg0XII7ThOKDo3yG0Mkfj
Gyy8CVbv7QaTb/+DGfmz4kh2u1V6iaMLVub83fweQTHcS8OOOZNiRUkX0wSPgmeX/9FSY0EBmLQH
BO7miPd9VI6EF4l9jIdYBALthc8gzxduqvO7LHMBy9ZviH3AVnu11XkCZ4OohukV9uX0PHWSsOSK
TeZBYCdgF26pYId1NEUw4GPhRAQVfMtfKQUknv1Dd5ffpHQOAwJVKxA0gRtXi/PIoaw4qKMpAc5/
p9fxgYgce9PmCJlJe5Gsuys3Zn0bDGGXEh4DY/H2jSvU4uE5Zm1ZW3wV5wj6x0XQjGdJELvyFGSJ
NQ3f3VJ3l+w7waOaLccqJX0dwO+TT+Al3lVQQF2uCSABdYJhpJH3gzmYCO1ahiMwBRhqVsd3u7vw
J3ahBrEHhTM6ozmiz03kk8kaK+OVwXA2XpzkeUgxR8AIINVFsleyc/3AMbq7bL1InRZECwqE6l3s
j2kyP6sYt+imRBxUagu1wGRnIBrO2V8B0cQKCThVaaa7C29CIKyMRrzUUZFYtPpruK3HOk7Gz3Y4
usXzUkZz4fwFwKBVgJcgq6+zTzGUf3Y4Bz8LCgvpAX/Z3wXvCykNCh8oV1KpFtemdnt+Mb/I7Gv2
tWMdX+8pSkr+4+If2B//9PmfmfKlL33G3APa2tTz1N6JmhCEPGgUFEnQl2T0M9b0ubYI0ekVShov
DrLbfsPwK+1U3mm6N/kGFZnq8MVcIyuE2HdDOqnXyNqAXnzTm0Q/A79BP6FMJ9GwfxPznDnzB5AH
cIJeQViB7gRZATCxy62P91XnbeaUpPGVEeVLWY56Kw5wn+ojyDq1MWbexW0BXy0sy2MvN7Xhy58x
vy4O2LlfqhbEYL+B1RqQ3hyBAKQu6euwj8QfDjXljZWc6QKKTmEIL/lPEQk4ddow803SgRU3xDfC
q6imaafaikhoB7IRAU+CXUgHZ/GlmBCkOk9KT0lSyn7b99EH5z9i7/X95l2GpBv8i7jBXaQ/reMP
4iA8oC4/PgAeRlncBHyL4l2LYWEXvlV2iHoTqZwZNKwtbzMGRTQX0DhQNPDLL6VfHIGQkh9/+NfP
v7jILlz8z88v/uXPf2MX+n7Xx371/rm+X/fFHsDiOC6PX+A5DUmVY64Bib13C3BUXo0SKiyE0GGD
OIXyoxJSa1zU3a0pacvGWMnU2WDRT0s6BawXe7LFa/p60tpkRo1vYJ8pKTbHUzoOcFpRleW1I0AH
ydAdLWz6G1Tvijhispltt+g4A9DDO6yYyWlxCtyqEKEzaeuFJQhoMkUF9jMLHqDseZuyqv91PKTT
YkiqO37DfMTMO/ldIn3sBboLzFsTteg0i5IG7sM9pL8r2BijZniKWrFRf0bMuyVYdf6psJTbOKZd
VEN5jPWPcceiHqB1EJ1sgex3mCXnXLD7GwYAhg/ijnyewVx2Mo/kxrAI/RtdYO0EKQMmK2ByxobE
UJkgd1phEWusWTV28mVFYa0AO6zMz6EJgr50LCTa26U8/J6Ibd7xGtp0LCyqFSkeQ7qRVA3xUTCc
wpRvYDzOeJIR43cj9Pbam7bKrWCAZceyYO+smOZZJDQAs8g448JldNlYKyxiMSminW3qb9ukiD4Z
86V1p4lPcVE7kggrudC5j9798J2+1997/6MPQKUSVA9VT4mxJEDoFngmwEN6BKKzVEvOjVHTQV2i
YpEdZYovWAuLTtu4JW0YFBlsQaiSBZA23uM3tZG40AhQXEjmABuE9I1eg+ZIfYqkwNV51cgCtUzA
gWFAWmevKmEEwEkaGjVCwwmxD4avPsLueRNL7dQY9U1rS7Usk+V3+DgmCmWx53lYqkVQXmLlK2CF
w8AzxJPYgt0aaMZrqHvgWnyByljqHHP7pRsjhkevNO+HM1TnjVIH4Db9AMdFPHMGGvq+1XWlEF7p
hx/qDDhCZTwK76DyMTENrzMWimnyChkRadG41nnPi4phnQ50p090vMSUTC1Z46kTwbS2xM6cwJBP
HJLp65B9Hw6gcJ9sG6unr1EbtbyDlVJi5eKhuuX58MulS/Ls31o7xaSje9S8XIGtOnMimZKYKLF3
/RvlXuvoKm6ewOSJ7iFexmnWQnwfzGglv065PKS9N5IpqdMIppUA61EU505LMnpcSbvFHkBCrNMj
nYMVk2bawE5YdpPxwF4tT5Yd+iVqzFXRZa9HIV/6tNGSsHVQ5o1esFJik+qsvX3sKKQ5dXQWJlla
ucgfZre9Wf0712E/Y6Vls8ozSN3xiDKLzyjLwz90KqqVBzoORRYyTTkNk/MAkZLzwF23VLkK3v6A
BYvYhz+QGIreDeGdDNSbbp3EGsD8EfOZb4TFZNRn4ax/D3Q8KO6KqrcXTOLxFdii0oyYQu5/xw3D
OkCGfCOgEi6ltc3ZbUAElZd4uKjPAS44k2YGmbMpj/ykjkS1Z45u1yTRMheDgcK0V3H2WpL+5md9
kNAiAaCSelj3HoJ9Z7/D6gn2Heb0unKDWVtugO5eNatBE/u0VKJGBIialcim4wMkEUZAzDAfyZD5
oJyxMrQtPEclNWRUOwgjVobqvmJPXfL72V/+F2bAE+rAMRp4sGSa2nCE3nQuVx+h+ErJ2qVLsEdU
nKrHtS19vTKKKI6U1lt0NGbrxXQcZo9o1yQlu9D3cd9770KGduHC++c/jMsd2ACKNW1v66uQQolF
o4K09XKUl/q+YW+D6UPc0YwQMBHP/RM6tDULk3PRl4+kNXGaqFBHtZNM/YvOG3VycFgG0nN9F/o+
PP9x30+UqCP9h0F2HwsAmDFEBXCwNVcljeNJfXlfuQFMOO5GR0NVjme7EMiwJ0p/OVMpVjj78Pzl
y5ePRjIZxws3y2PqAlgRsfNj9EcxEJObyiMwceVhOWw7MzBj+F4F7nqr9KcnJ09YdzQbhDsFv7D8
VcI4MVbCNqNRplpQq15QNXfB1cWU0zQqyg6M/jkMwjFJv7TFzvHYDFVA27rIUZEs/oOZqQ73fdv0
crLjhhrPLENmYdottYIPpli/xqNIPez110nCNqGPZBWno8OXSj9E1fIurMENMbmXqzgC1z8jg85Z
Slrk7lJWmcI8qOclL2L01zbYQqFU/TSOokdpJH3FktoE/bFCutMEOlm0DGfIzOQ5h+O9Jx0nOl/e
E1cTW6v+lNJ5b7G4gSEq/xTzVz3vaNEpTohvaPss/hutxNpbL8DzHREsY0WfzoDEtV9g1eZ9Buui
u1/1tPq5eICUzhujTv6PuWt9buLK8t+3av+Hy5cpeRMLbN6araWELWxNbIm1DIRNZaq8iZNxJQsp
TLJJbc38L0p4DBBwN1JL/ZDU3dajFSJkTIiNIRknDrYhHhwyTozHmKk959zbUtsm+aTeWqcirFa7
dfr0ved9fsfRNjTM2WP54eZ6AdbRafzVqmFi4BYFObG2mExdSgVhD5iqwUsaTCA71Sw2ZG6ZBzmD
lO8TBDpzxgp8zwwldF5vuX+4d3+zn2Yjlwp07AHuc1LatsZy6ZZSY+C8qoa8DAYDnSzabOi5iHpo
6c/GinObarSCW3Qm2BgyeoM14z66Zm6pAu/iIndOvqv/SPYKBSiqjFt+jetsev6garVbdDIGidBe
bFSFuO1/zfIVH5h3QNSzZn42b6AphcGcf8Vt9W+eJGeTApeRuMdAM6FeyqGRo8xrEkb5sQwbi7sw
nqWal+wpdfFl7xKkxBfVXfmXrdjLtXwpWVhWr6V/flHqx/3MqtvfY1KT4iZUgPYIrB+sNHUjJz80
7Dm+hVtM674Wu9/uZbnKVubBd0BHQ//eo5w143uRZ4eb0qTsLVjG+SI5JZ5yB/dZ/QWe1fgX+oa9
Bs9XvsBz3d7KHMaDy25alWQyOO+vvtpYySIFRKIOk9r5sjwnPFNs8PuGNDzIsX/+J0WBL83K6emy
an2BsX3GryeVKftOBVLWolZruvKevkcKSsHz5ie0Ntbt8pV75ph5YHuwphR2Mu/5xCChMv4MjvL3
nqidtEGh5JaWVTcp2t2kaPcLKdot3rNfIinobnTbbbxuMYl7miR2vpDETpfE9mbf6nLawgoxXrEG
tGKU05SnMz/Lqnpf4cdFYB3LB/JCXKUuMyuf0+l24GCh0rgi7XOdV+7ki9I9XmxJHVZgi2a/ZViL
UOGtYpQ6BzdzEoSA9DUI50qVvDzyFZvhl5vg/LuLPNji+ux93BYitmhXgGWe703mTfSGr1FywQ1t
Y6sThWPF3hYbR1TS4qZifFfxDIG8IOueljPyazexAcxPeQb+MYuZFXPc0/fpscNbeb/CjBpTr5Xu
BRL9LK9XbuWqbd5G95BbHVnngXqyRLBJBAl6DTXwJjFvJLNJ+7l0p1kfIk+DR2Gw65+D/wJO/KRb
RrjiTKYmrYlc7oVF+q29TzJXODe1hU3lTZ4vdz/nRUQTGJyGp1yYakSX8O9o9Zdh9ZOs2115TEEN
OPMSqOtUE0XB/eFVTFtqmKiA6e8tzKK690mWRVEpVNUn5Xv41SE3jgkOJPgyeAgs2R948PECp2Gr
kd/qRqR9ooURLt7i/bqfNHm+nF6SVRRceHsBtIfyU1Yt6Kl0zzvSn/FpNltt2lpnALj3uZ8MACyP
cmnxcr+oYWdgfopZujxtreOCUM6zRr8gSOiMnLIvYMncoRZHS5r8IlVKDpwiPYStjXvRfSvKqNAq
E6taVnO6Usau8S1uERrQC+T/vSQiuOYnFAimzj/WWqttC5NJ92o17EUFty0kfhV7FmVxoSIlKc2E
tg+oJl3FRR5If6c9dBzzr/JcUE8rz+Cf4pT02HJwJwTbfOB4g2JSxaalbxQqlfusI9ip13kbL2rc
rN2scCQfr1BxPM1p+NZOz0iPsVXsy5ZaCr9IOP7HKSd1aF5KLxnPrXvFJW3hN/im3c5YsrTQLoAz
KGMfoqy7w/hpjfoI7L1oNLG//HLLaWdNWkmVyQ+lZOYp+w3T7mk1Z5W9hov7dZJ2tg22BDZSBdEZ
YukZO4Pda36QxAkinYPto/bznOnYQt/wzLepGIv2OctQ10RKy7qDO865a3+jKHhQemxealR0+PCE
OYmkLnL3wV8WAmsPa2f2bGqOJ7zrmPHDZPxFYZKUVarFCpavNKs+W8/A/+8/LvcObuXeXuAe8gvj
RBeUDYa1dcFG6WrJdBysks3ki+oiFg5d09YQJ6HRXANM9uFZc+QDUpTSgrGCoeur1nze4aU27cIO
wubOrDBlTIu6r91kq+d0e5bX32xzXnyjm1SqsaiBDcWhYtrDoyNDp1jX6XffHX57mHW9f3ZkeJQF
ukc++LC9/73ht/e0tdiEfAFRnVuJCvJIIcaxpA35HPOBIU1Jd4A0IIiVTHqJ5/NfMi3lSc4JZMfy
xUKlrb04mZXR7QABDj6+f3zgPmZ85F32u6H3hk4F+o9GekJ7D+i32l6iuOVjOWU8D4RH3wrt3Q8H
McyJQQfnmm9C9wBpLPmuojjfORsscMu8k1qvPku2hRL92b9TKu1fEBPLPwJIDRVmy1Lpnn9fsr/1
2TrPYyWt0D808s5pdvL9d0baE++/N3yGHTs18tbpM//Fd94bZ0dOn2LtagY7CayxsgTyQ06VNTNZ
+KxQgV91zVPxta3QzDfSuadBu6K96cO27z24px9eQns62trdfUs5Pgw8StTaSW9R6t01v2K51eKc
ucRtYKz5nmQ8R+sX3QdJPBfT1oaakeeI/KEPNnnh7W7yuGbcp7RCI8suPzCeq19QNPuQb4w9SHLY
7V/Uyyq4M6kx9id7Vtb+tO1wAA9XnDb/ttnBTm6ZWvfQjmIBnqtqdHDk626GxT8KSAoPDv3n6dOB
sqrX2zkJ8kzpE1gpn4AB1UR2CdqGaWWTPO2PXaa+PSaSyOqT8fMqdq2EmOMUKqkl2IqPyMsY/1j0
3ojGBo4ppViLVr7gSMkWl3VvYRiJ5vCpoXfZ6NAHQ6C7A860hqU+hdnc6qHQvk7UG4VZeKBrgT17
d1nzbS+F33iTJYaH2e7groB9Ll/SVu2xNv8WOcnuwT8Ms56P3hv9iP37+8PDp0YD4+cQ8++S+aWP
37y/wZuj7w6dGj4rFrTXrPHtu0nch8+cZaffYt3DoyNn4MmY86qNPoCWW39Zq7UhMtRFxIkkOWg5
Yse3OLq+lTA/CkfaPbBXJHTDiSMMcYtg11h51sECwnQqTjJCJEKLZccOsF30nFSmKC6VQatai+P2
26jr2E5d53bqDgjqzAlbBfVw/fPiOXPDzdNg7PkrTL5eNqv+EUqiWHqYL2Yn2Gu5q4VFdjzaHYmz
ru5AU4G1gbT+EhuJyAbzTzF07CK5nIh0DUQGWTuGqw1Lp4QvdvWz6jnspNS1Ww52MWcWqOffP96Q
PO4dHnqTHRk5M3qWBcJgP73xTvvwR8Nvsg9Ghv8bN93o8Idtv8o5/+gjmdwzdOptdhhfjr4/OvrR
G0NnXYX68S0fv5ukbfmmrmY1uM+bv8qB8k2tlprG0yyj8iA7pjxhzuym9i5PBN97UV4JqF0xHtoX
Kg41fV69vsobYillWVj2Qec17nE/N6XPnhn5MKCWK9fUsXyj0Iwrs82eK0HNGqxyC2/RmeTdLf8X
hJISoCIJNZO9rkpMXaGOWS7pX4Jt8hwMih07igvS1yhw+Fl4kpTk51jGoV9DW6L+uZL2tV43EeUN
L9coNRfqpKUZghcGNDt2kU7J6+Y/lIvs6BAqvVPDYCdRnpQaokXvs7lGKXlKXcITEGF8H6hrCC4O
w5iIxlhXdPAkC8e6WW94IN7Xzfqi/ZHQzuIU9iVJnxWWRb2MwDb0bU1wHMCjA5Hj0fixRN9JFo+x
gTDQdyLeH46FdnK0JcuhqMeC8zD9XZBj4SgKxpCojdSPpymoI7Uz2BsJ9gJ1kWA8FuzqDSciJ4N9
4VgEqRMBTPmmlERcW3uWmux5e5euSo+xFR37d1pcobaFTKGOXg3tzOmWEUxfktXUZVZ4Yl8oLCvn
c1eVRXs1qBauj9k/yg9aXTS5ZYWRNqqUMivpGasGEijkeZNawU6O3NVGwxOCI0jJIGblqdZkElHL
pHUO9go8kxZKSRtEMncmeL0PC/rISdJVynxmpXw+s5LTQzvddlXE9V7LrVJlDRcp4M1v6PXqY+ep
fBO28DxI/VK1xMyf5LmU4SOJPAcxnU1qmOM1VvIl4DEl1LiEa5DHP7SMJqhLtaSrFIKgLjDKwbku
vp/Lc7/YRexEFCTN4YHwYGgnikBM3CB+0Yx6nkLTCPCd+Ulkdnykh/QQSL2+yMDh8OFIAjbyNb4w
LUf6OltyJt1NHBR9gva5wrRl4DJVLernCgZT1VTVRxpJh0S7IigIIzHOL8vRZqVk5ieMGXG6yLk1
fOQVx1U7Eo6xwXDiJLYvIilYhrN7HIGX7hRzhaq0ALy5zksnqYET0eDdXkXQ8Bxy2kciSYkMxgcG
okeBzj58ouUn8gy23qgZQuSTCfUN+xqp29YvtdYkiceOkjhpQf+bdNVYDLHGW8vAPcoBrxASlvAv
RSULPlEzKU9jJ3AwWKjyTO2hRq2jbwSTDglUSsU5vQ5GokIrzH6OJVJ0zHhelUiWzCBuw6fVp6KD
1mVqEGEDudI7BOQSHup9P1zrJsmkavS6+gRY+VVxzp5tE4kwFCzqBSS+eCO95NwNuiCjap3XfPpJ
FamQQG65UuIShXwBkihAHhVDEPLwvHYNm9PMmyhdhMlQ89me4aBPAcLzVLO3VNXOOrdzq4W19Exb
kOPRm2uikVap04LkyGoIHQ+8Hbd3AL+zY+ZqZsVPNcxhi/6Ht3W7C+yPoOasOXu1eB5XGSgNAyWO
+NCj5WjEAoZPjOfSV7xJ2k9SSZkE0EZM9MZ7jsXaqMmUI+cFrQlpFQ0dbvBL5bSFqVhj0f9VSPrj
SDQxCEZ+uI/1nIxFuuJMCG8Hy+UQSIvb1l+qP8rLiHzCm+AQrtH8kjnfaetgec34RyTHxzkc7nql
Ox4fAAHOBo4lEn3h0E4qDEhNo+NGKq5G7eGWwecbtLgdfRtZpE6oVf9EbxwUyisR1hM+mQDzhV4G
e9ngiTjrine9kkiEmINB7kYDBkIQpi6n/6JKqUlsmJhKgRhXNPNTHezbQ35STRoHp3GA06/Mw2ZB
R4mrGEJoqUvr3I/KLfu5dzmKTH98MNLH+sODXb2hnVgnyGUhL56i3aCCn+kgtCXObiHkcB9p4iGy
8EB3V3wA/Das0AECasY99RG2qWH56E3cAtYsglnysnbnLtuxw0eaSE/gsIDQTnxVHqkqQj4J00Re
VlWsITKT3C7gBa66msOyWF9XPw+ZpTIrpSeZFbRa1iqOG9ui2JF6gXsaYNmBL1G96syKqj7rK6uO
/fXeCl6/nQuOVWKNZdNYQQyrHrH/qXNAhA4MhnC7AmxcNCCDeQJ/gOaJj4QdEE75sXCU9UbCfdFY
T2gnV7FWjdvEziQ9az93I+mB2Mn+oyDJ+iMDXdEwWPCIRFao4pZE04PjdDNbS89g43NGaumEkRdR
xbEp8unKfdWBRyZ+cwFJBW4LbQbRfFL4XHoMOn+igRG/5tzOXGSFZeUJxjYYdm6DdKmpFy3dva6P
5He4Dm1iMB6LMGzJDtHawlEhau6aPJcvppeCnt+5CUAzSfJFZzWXkx4KzDFh2ftJLmmGGKixbjYQ
OR6LxsGfRBMZe8LUC8UbiPFoXuJLgSPG+OIbNWJEHDjiePRYtJtC8aDweVAvqD2CF5SG4E0ocMDG
0SbFSVoKFKj2k02kJKKx/4iA0dQb7entg/8HwZVE+C1YXGN6Hc11HOBjYPEi8quJqSMwI+1pbp74
SCbpje7wSTRCQjuLc+DnUhiSwFqzNmLauWPWmPStrGm1YklbRT3rafDyjbp9XNOeCPf1Ied4fLT4
nWUUvwU9gJsbgwcIiYcYDIQUZd0xk+kZ5GJ6ictDHJPg3D7kI5mkNfoiPZFYN1ibg8dxMyIcGzYj
PUNkMpzTwEnxkwzSEYdhX5K12RdHS/hEDNumCFMupSi52xgtkBaoTsj+PLdq3sTD0obyKBjE98qj
1McIZsKNKL/DBBxooT8+EAN1xkPOVi0raw/UO9wj0wwXdhWOrGkP0AhQ70iPcYaaj+uOgzSE2eH4
8QhJ5ldikQj3djim0HXh9twEs5N8wtSSzyEgjq6Q1iv37dWcE9rpTJD44GKWD4lcp3+YNZ+7nR73
0zngiAaOk1nRauAbUNd5XVHcA1LSeA5if400lcHc9YaigkNqYyPmlLezhW2ZegL3lHWbpKkCqFkA
VJ3Xar4ok2a1agfHVbC+yJe5LFQesVDjHQloaz0rM3gZS88UpjB1pD5i5SvWBGLks3OTwXOT/iQF
BX2kW7rjPbDHj0cGEuy1cCzaD365m4l+nbXzQikpJbr9ENPpPnWwYz23mrqcv+GCI/ummDlMg2Jq
Ur5or4IniV5k3Z3PmMKlQR2GV7JfVJ82CrysdSll/Jz6mEJDGoaGfv97P9fyPpdIFtjTBt6lIa2r
hlWTU1oNGddMvjHKvrk5Oh8p2t+kaC9QhM/QRfDkXSnCqQMGpXFYI7Hrt7/1ox+o9e2NL7hfji3g
+9cc3PQ18NMd6YsOwisonu5jXYMIgQQLNGNNsAAOIG7ikiKal8PUjPpJ7nbmGctUqQC3MaR284Qa
AaGxMP7MqjWvIKb41mn4mvSJtgGr35oDsWhjBNyqPs3aYoILg8/q+OlYKYlpJM+ApSl3hBJenaPA
r0nnyVJ07qK1Q1tIzZSSrLBIZQqli9qnWCPQvMg2XDzfGC4wCzw/XfH+/nCsO8G2MZhoxmgAR3g3
RCXz9Rmt7p1lzFEIlnMpx8a2bO+wLPuC+iP+Dc0Zz61aUzh7iZWns2P2WuEWB+6mi5NfqFKvL4fw
8sxPZqmrpJ1SNKw7SBMe1Ax8FWgj1rHLvMSRwEUSF/HAktKGPyWFDS52bOEiWMO90e0c5JhioIY6
OfYnMI0myOAt44hUNZV+TIMSrq9az7CHByvcryumBzKK4KIJSVYtmyuc4XcpeypPM/kc5uUIfxpH
hbso/NoV0PEXgZvNa2DXFU1qEXUp40+xANFFx5Cn1eu0fRr1mdoMXPJCw0zwXOhSdiw/JdDWqYe9
slwscYARxMcvNMbT8AQYw62kuYOtfXocnVsXNVitJ1ns2EAiktj2UBDQ/zmGRlhqyarraQwf0Yxd
d+wsDTEYFyDOGIkgyGoPC8bpAjRGS1l0R9PCfaIRzBArx03Gm2QwMXu1NInOhmdJL5G+IlVLM8JE
EAStV5xt8sS6J+aCU+efXsfIpXdnCVBIuoBV49P0qB+xiSvlG7d3b+V2TzQW5on/vdv3AMpuzCFy
dG2+NnBpIGgPQeBqEu4H5TwZkhQlRc48QtvZ89AakMo0P2sVpyxx24Tkwd5diHvEUpOi8gqN2X+I
sRSZZy+6jO6dQO5jaVyDa3u2cm0wPBgNA+M6XJ55tmvhc8emghQ0DoFqq0YDO8xPjZV8sYx93ji0
is4QoLm4Uz0XAHE4lrrsIuTKumArLu30PVHHb9Wkp01EYp1Vx7C0yCO9V2kUO8JMYYe5mZrmC74R
EOGXxfaSa1IKk+8bmZ/8aS5ucHHvL3Gxc/vKs2dzOQobe/wdnN5rrZeLm4Y0kCyzYP9vGczsenDo
1gXxd70u3lt1GgxJBYj0MTGQ0BUnNpeT4p/Rh5XHhSpDk7EwRXMFQFTgdeizQkW7opyH54XPJj2e
XiLHzDcm7tvKxHAsFj4c6WNdvXFw+bcxkkDZcDyONQsrM2vbawwdLPVbVnQHocEyJOg/MUTC4Y2o
Nz3WmphVjEDXJAvuwlWsed0gWG95Ljvh3FAvek2KBqTXZjuJhqUjh/gfTXpNEY4CRbhq+XIBx0rl
664J1ryKtJH/jIBXqCoTCdfV/I180cfNv3+b1RU+EmFH+iKJ3ubKfQFGHnNmrA3rh2qJabVsEsFu
YR03xCWZZDpDGAjc8Orm21Tujd8wkwJfhoeQmDuQgc8UdCVCA13ZI4BWZITRRZVCY6NbPFl2O4cO
bOXQ78JHwzEeNNu6Ht2RsyIlCwQ608YKqz5DwLqJ1GU0N9cIjY8SCvL0+A2aTMgZ0bwOad67uuqC
4sDefSBOIgYg6rKYaogmFqvWCxbDrnr5gbvNfeLGNrco2td3DPFgX2CmY0Fvbp1sShpl7rDijfRn
2XGOgrbmGoWIDcFyOJXXXnO+EcmyzXadaxzyEmFGNcLO3VKS7DhCvqX4BRl5Da2BONwew4bPMKHK
jHluBOHpIBnK44XllGKp6iNf4tONybjbHJyBY4nBaIwdjZ+IDGzfat7NhpIE/D4aF18p0cgrt4Ke
/W9v19bTRBCF/8o+k0jES1oeS1qTRhBDC8b46whqRASn7LZuS+/2ogRKMBGC8kAIMSGGGm+VGCWe
78zspbMkxsRpXyCw3c2cnTmXb+Z8n2SqKlmtd8VtZNqwBjwUvoPJEdzF+c6M+0o0JNBJkalGY5Bz
yT1RwbOhpi9zGVc7ha/BLZD9+CfIkX1SWuS9Ry4qwZYm1aP6bsvETPTxothEJOLeS2eyqeSV5Fwq
MXPJfJSnfNlTKdVgKWwQ4X4vD+wj9kpSiIAjaug2X4q/6DZKABMKRUEhXfhWbDaQu+CHbNZg0kJK
VJBkOnX7sbkJFik2rDRDfhZ58ynKRS4xCepgL2qxMTw/DH4hGGSbrCTWmDm186PRB9XJMc63UYJR
+4iYGTEvN9Bt0J3FuZpZ3j1prXkRTga4zfLAmDEitcD/J+wJmDImYnoSbQ7wi2mZprlOs1gkHZu5
b2Vnb9+ftbLz2dk5nImjgDek6ldpcV2Ys1kz4CTgV/ZLRvxLcSsOpQUMkkuFG8ZdUG0WWULPhE/2
xxgzCieGXlvc8GsLnqTF6GRqaj6buJNNZS57Ybyt0ss/InNLOScKkUoKGPtWHElrhzjCpdUgQ8Ix
5BDQ1lx/LxYRIOh69eUtqa+DpmyO626hXll/HqIIdNcUPh1WxnviUWybs1JcC8d3U3fSGYtqjfRC
KjqzPbkx5uOFpBh2j5VwsqQ3parJ7TP+1Gl11uxNsRhinax9YhYsexFoiSU8vn7jYxwOkZV2Y6/F
mHBPHyCvTj6auxXoqUNqgBw+/D6UIEtQgxr2+WK13mXkAtQI9Z1wkaSSAgU0tZbqv1/9oEDYKJgi
+fIHfW1EKzp+fVQPujEq1xG/af5JfniJa+EFvCWVLnqdcLhFm6BSo8aubXwHjCyo3OnaXGDxahzq
6cJ6HMKbQEPIktK8er3ygCszCjrgFF+/WL+wqj1WQXHXXJdWp/3U4NmLuFZ2lwe1PPo0wJX9uboX
GTwvT+8inF0ZsE8FWoniqCml+q4DyGzvy/9yS1EIWgDfvjzBrAomCUayurXCaTkclPhSkPHt2PsG
LTCycBifHNEynbw6qgdplU9tudIsrtTOafaIs+Kp+mtz2X3R3XUOO2fMGHOtcwbqyrDQRelz9yh3
7H+dWcorTeHgl5BqrRb3OU+TqwhUx3vOgXtq1XtStGzlpaPazusb7QNgQQbNoNU7mfTM3emUNTU9
jxORKO4DXVPoIO9ajQJrWfreQmp9qt3WcXs9fyoLPt65QroS0Ju74oOE6Htiie2puMDHx4sHJdfg
ILU6ZipxLyl7pzOz89PWrQQ6AjRJv4X0QjpJ7pRqsK5wTsi/sYyqZAPVNFLfDr1baL4AoLLKufZL
XPJa8j4bHJ8W2zKJhXRUopBmqZ+TMghWFKKLxHTPU4VoP8v1aydBg355UP7J4Aggt46zq1AS7CpW
O41Dt8AmwFvWd9Hs3WpfUMB4mM8DlV/mhg8+7mONyQ+tnK/iXCxhZ4J5AquvQLXJ/KzOoYXT6r7O
xgOacy653pIrVrtvpDVpvGPeR/bu/41X4F8+fwBQSwECFAAUAAIACABFWkIrnNvK924xAACxmwAA
DAAAAAAAAAABACAAAAAAAAAAvLrAzr+1yK0udHh0UEsFBgAAAAABAAEAOgAAAJgxAAAAAFBLAwQK
AAIAAADWvEUr7w90zflQAAD5UAAADgAAAMCvxr/Hrrn2wPwuemlwUEsDBBQAAgAIAFCFRCvPKLGs
e1AAAFwZAQAOAAAAwK/Gv8euufbBry50eHTUWv9zE0eW/50q/ofH5X4wlGeQRt+pylXJkmyMLVtI
8hdCUpSwx1hBlnySbEPq/hnHYBYS7FGssUbfZyxL4xBjrwkLATZLlgIcQvCR42IcQrbudc9INuzu
7VUduqobV4Fmuvu9193vy+e9boD68z558P/lZTVfvQ7C60wFVCWzlrqduQjSXDFXm5NvptfTd+p9
9+/bv+89EJ6l/gTCTrEiPpckOQ/5zfJT9ZvCVVBm5XvqNyA+khbIKNJXuZWdU9eLap2srELqQS4v
/yqv0XHZ3+QclGrFivCs3reSXhJugqIUZcr6pLxWvb7wbXm6cFX4Kr/9EaGaE0QRKakXcdw0lHZw
xHWkUxazczVVE1kTVX6U3gSjAZ/yDmgN7F6xFi+llyD7rfioWIHszspMZk1r+ka5RUXi5Efyav7F
0kVpzuUmXVelOSlfknCWyq1CtXRf/YPGDP7h8/7/9NEkL1akudKLhY3sNs6wfDn1ANdNmRVV+Zay
DaVrco7OODunzKrfCH9e/BmWXiuL6nqhUH5ICMDszOz0//aPYZjZC4TWp7X5nFAoyOupB8KMcl9X
ivff/xdQN7I75Wmw4DoRRUCpn0Dhau6nYg6M9NuuMsDs7LsR6SKd4NvPe/WHvMjztTIQBQV1Lrut
zO9tf+89Ml77Y97ps3/fScrYZLVkdz4C53DsNM/6Qmd4b+gsH2cnbawBBTmJSoVaTJQV5MuiWP6R
6LYkAVrJd8J0+svmiWUmYpXl6sPlBfERcAYDV1+9FhTqIOzfFzjcA0fAbDAwRs5ktlht9v37XG7m
LH/+SNDscVt90DzpTEQ6dUOYllfFRy3qBq7QTvlK6sHB5rHkCEtvADznhkZD0TM8BPj4JB8nS2MA
TzTJx8fj4QRPVqh5QhiJEP3hxEQo4gqN8Hv5eobDyXAsCmZNc4g/go+aJ4mBSOKKxfkIDMTiwz4+
PsIPJdGBQu/ISHiIr6tMS2WD6AuxIKIwqDEDg74eP8MZuji7wWFwWJomo8XRMC1oj0WT+E8kHAMH
a/hrr6DL5u4bMBsNfg7jgNFiYWycbf++0pYo5n7Ib4L8uvwUar/U5kB6Lhc1z9aqXCgu656jETQo
xcqDzFLhRmvlQU0tvZTvtqYuCM/ST9Xv8put4nP5LgY1+V7pZVEVXkHqdvYeesb0ndKmuoE+sVKQ
ZnUq6rXyw8yauo4BhcRA+a74BD2lfAn7oTsXZAnDEHFemRvEM2Avs8EiLMiqPpwzGQzCAtKWV6UZ
bNVZKKXMLxgUNU6AwsxnvsZASjjoA+mkf8pvYkSR76ZuS4vL0/DP9lbcVCRWW8F4J99CelQGPYg2
axftus7j1lGd8sVj8Dfdur6H4D5hHTjOuE3tJzqYfruj7QRj7/J1OBj7iQGHt3ly2oicupvWvAJK
OsInUPBoKAIt8nppq6YerDtOtzvo62eCg95BG9PW1nHMwQx0nLB3MW2OjqNNlNJKpdQej7vDAy6n
F/ot6DRaXAfB5wweDfqdLg9Z4ASfnBgHVDcSbYqVqlCoInIr72jAC4ZiY+OxKB9NJgDfCqlqpY4p
9IGrsDC9cBVWllFlhuKhobMsf46HlavyOlHhtWKuuimuAOpurvpQmkN9PDwUGjvc+EAUepc1JSyv
Ll6qYzB++Aw/FElQmsiKkl2l/UWVWMuL6pK8Wtoq3QcNeLHNW1MawktfIQqrIZgp/0Vezf1A0PHv
iatYRAnMxOX8fbx30tnd6QycGnD2e9r9vT3BU17nCecpHIT+28jqS4VmDhBBzxpNhKNnYDwUT+I0
yz8WUiCoC9dg8Vt9lhyrrfaehdSMFSPzGT6KBk8WCciqEuDaClS00BQ7HEpCbZnujuvIhyMR/lxk
7EPtO5JY/kxVm76SFHXkCpkZxBzHcv+Z/pmGs/JM9bqqLL6QV5Ut3dcS/az3g3pHVKHKrWK1juvZ
urtLPUh/ibqRflrbAVHKSQ1HLd8tFLA9v6neRoQ8mkyOHzl8eGpqig1HaVBlUccPf3x6IhwZ5uOH
gWrkypy8Vlf0Zi0DhTfi73AzVsFK4rkeRUHbqz0tLW4+Mj4ahknysosGDrYMHYS2WDwSig5DA6t9
4vjYzoxPjJmjzJD1zCf/ig2oE/DeEYhPcYzt4yn8EOfPhBNIBtUkK5S2yjKi9EOH/PpXaDsPvlG0
+kOHAHtQo99AC2+FD6nO7d9Xe5X+uTy9R9+AxijnUDI8GaIApYs/j0PzvxVy2jI2UZ0oZgucPx1C
fBQ43g3O6PmpUT6OL8mJYYwnBGb/N4aprZrL43N1uY8f93ucTvTqZrPVaLRzJlPzxKYoz9Xr93Sz
AZ/HFXS6+rqdfnbAGfT4253d3QHW5+9lfUd7g73NE8KgQexUFpEPIuzU4/zmQbJWmMatKRk0tfwG
upbrUL6S38T9FHZya5jq5iS6pVDZkNBgD0BL+Wn+h5oqVRFImAySVN6hUJDhbCkVaZDBkH0ivCJe
CWGMuiHfRV+zcKv0Ssvp2dSCLCDuITqkCUMYYW+SkmcU6Qmh9oWM2bskaepEyeU35dfoxtJfCtMU
OxVuyI+E6eVpAmdu6ZTluwvf5X4vPilPI/T5QiZIS90g5KqSvFr7AmPNC9RS4VPd6WUfI3rboBLL
dzN/JtqPRJviCRqbYKYINjAxzscDsZHkVAhVtzt8Oh6Kn9cQxiRHFLhJzO171LCvJ+AJBlinv7ev
x80Gj3rYgV5/t7tpirgrBYVVPhe4O13QT+1Vx0+drrZAMOgwO8gKgLyubpBdb0U1kde1X6lsaav+
rSxqv8pivV/+RXFZ+6UVtcjvps3CuruWXqe/rdvDBj2DwT6/J/B/sIQUn5wEb+hcLMq6wlF+LMSa
3exgN9sZHYqwbbFh9OqhcDTJmty09MB6+7qDnd3Ono4+J0LEvTAEUUhZLG3hkiqLvxZz5Je8Ws0T
7EN+i4sE5tZDQx0uUFAS5xOxiThmhiREkB5LpZdvgj0d6NS/ocmLFxDB5covGnRMLJC6h7qOYSmT
VbZJ4VGaA+U+HO1y9bk/rJvJlNdldpMBZn3CZjf6KjJTOlGTmwypt5BwRAqT6FJAeFz+sRUyMxRA
Uqk0MKVlHFp00+CUDpUaJU2CTwqlYg6plf5DlorXipWyjEJb2AYjGOw+3OMJktJBOBQ5AjY0YqOB
4zDZZNqCjLeP6eph2tr377OyGH6ItONEWgbFrQ+xmskQi4Uzm/GzE3++63rDrt5QNOaMREJh9DvH
4hPRvfWGSROBH8dCkyFw+nx6NeTgP4ymx/yYkno8jMNhMDBWzmZgSMm1WTMw/f8BALtCc1qK5u10
+XsDve1BveADbaFEeGg3V9ttp/H5XiOzNJhxUa02o81ubZaIRh0c3ANveCgeS6DV0fWlQWmvltRl
MnKmepmwFYxGI2PUnmYJSNFLX4QPDYOXHw6H9P0mtQMKlQk+1poD5xHYjiUIstZEhVIt+xkUfkN8
cAXkm5klDXRXbgnPELHkfhKfl2WoPVN+K9yozZX/Uto6cIB2OHDgAFkR+a6UAeWl8qmyXd4hH2mj
dKtWyK6Kz0tb2tHHuvAMxDIGpReUFH3PPi7cS2Xl1YUrdEhZXLlKG2nRZxUkbNK8zUb6zsJtgrLw
bQszINKpdS+5xsvyWmUZxK0mrbKJwhNVXZjPZIkna2kPR0MRWvozkgpxgvosUvJr7/EbjZzZ2ixD
N1Gs4pwMD5+i233KRYoTyP/UpNHANo0rwSaU6eA4RrfEqUmSrTaLmbVhcwOdPe7egQB4PdDiDTAD
4SiaYSTCR6PhibF6IfgglF6mbmeypEIOWsr8N3xbR/ugzct0tfsH2pn+Aavbx7jb/CY/M+A+bu9v
1ky0eklN/J00l75SzFlZDk6SiTUKU5VrOUlDBK+zc8J0akvZRpW+iOjgcrVEGwpXs9v0c/pySkI7
LaYQxJdEKGzrwfmZNIdonURtjQmUt8pipaDMvsk4vYSQUFZV7ECrBHkQrmaW0BxvQkpSt2nykJ0r
XCVWlXpA6TlPh0nFG+FEMacqmSypRtXmoCM6MYb6PkQOG3EuaLvEAbRqkhDzluczCi02kDIurMwL
j1spPRQdG++WPy/mMvPlLcBNm1ZXoLCwPK11ontem8tsYmJykxagkUdpRbkg/0p5oIHT/IisGqWo
sSDrlFurXgd9AYSF7H35Llk00BdNF+2Nhasv0+7RqMvXh4riY2wWIAecyLv2uFYoba/MrMwDaWyp
3K+IR3ydnQwaPu1z0O/0Eqdv9bbtlmq1blYzfqN9+jvdnl7sRQ55ob/DqXcopmv36Cuhv/yZqJ8d
kLwDOwdiE9FhaIuEaDXiMHgSiUZHncCbXRpUvL19AQ9S8AboN/AFOBxPaWtuyhubwIClTwYbpcXy
j8Uc5e7t7ekM9vrJlMz/RIWTnqfXcWm13kbb3o/Iye0h0+cQqp0eT4DuBqXn4mXKTxtksXaRRnVd
fESCCGltKdxQFcSz+FPOYUaT0w6+CeClYhx1u4UdYQZJV24VbmA+bdDXsi4Hy3W06XuEi8tgf21c
bIwfD53hceCeGldomI+EoxPnSJHrXR9w7to6xZCadZ9ERzUcm0oQkMDurY2zU+HkKOYiSf5MPJTk
h9mAj2Ndsfh4jLx+VD9zbJaIFCRKi5jGXM6saVtQL+MP+iA3U5U4FMBs5Q5SU6ypQIL6X8HGlrEG
FJrSJgrnxmEcEcdpPhnigFCAs7E4H4o2bSoUOu49giCXKWoPC9WF+fpZe20DvS3Ut6KLpp+43iTJ
G2y3ubsY2yA34GW4435XkDnh8CNwM7cddXeQKR53DBz3Mkc5+zEfc9zU3t7GONq9Ph/TFbQe9zZr
ThRr7sJM/XgRd4aAuS66no3DT21/DhyAXZ0Bl5vp4s+j7rd7He0nIOhttx2HLleXC4G1I8g5INjW
1tbRLOm1c9JQFIXTJfcj6jwPbRMJTArRe/kioWgC3tCmQB03IWwmyZ7Z2Gg3mjH/VbYpEFW20+u4
oflf1Aqpbm8Wq+QShYiBSbkDwnV5lcSVtertha+FVxhJMejkXwjVzDQ58ruklbqE71eyOEiZFXb0
ZJ1cgdE5lLfFRxgdPy2Ud5lV76kVKf3WEBrFchid1iURyl8WVGx/y57IV0yc3x5F4HWrDlmVC8oF
DH7SHBEbv5P6HZmTWntZfQgrF9Alio8ya/JtbMjewXintaKLLL2E+mSQR+61NIMxjVw3wdbq59I8
jY67rJu01RxFw9k7uUtQfaIdVep+ry10mo+wwdg4S76yms6yus5+1CxxKCTujiUnEqw7NhaOxthJ
TB1ZO7ubnrFa1s6iN+gJNgu4crSCR04s0AmJF1EtMG7STAHcoWTo75YMNIAaCLrtuGh2xsBZbYzB
xFk5m81ksVi5PeMKBeF7kqBdxQ3XOeSyKQmyt6EvimGOT/KgKSIJtYwmzFq9q3yzsH1Ad+mH9Atu
lWvZO5h3iVD6AmFf8XPEZcJM+o+I38gds9pDeRWNgam7UVi5Kj0hylbMb6ceoAEurggC6qv0vLRJ
bGU7Ta1NY6txRahV2sp8mXmCUkBDYjRNguIoZwpp1RsaMtNr1vAWCYr0VjXt18RLScoianthQfhe
VDHb1FAMSFuQ3ZEkag60eCZ+1biscCj7BC0otyaT4p48TyqpkH5aWqlc3MtOAuaNV+SeeqAgTAep
CsUKwhJChtzpWyu9St8RpqlUuZ/yL5BqLkuOjXGIvCpdyn8tr2n7s7snZTKb9J+kuVYoqgjSEddu
K9tCFVFq/ntllpwT0znjAlFa3yzk00uEgXKh+vSNPW9cH7zZKBrCoWJVKaFpyquZ+WIO15Zchivt
1BeVAVfn0UYzSr5yrySiF8I5EXgmPieJBzqo++SEgNb96C0MbUtTn5GTVOxtIARqpGopSeKT0hZm
KUQgZXHpJaJ1cSV9B6eImQNmaOfGI+gD2E/C4w2upIxKIOImJbtH1L07DqU/6Nc8yASgMQNtkrV5
dKBEOk2VJBxMa6XU6TXNumla6o+djh31dPtYLcaxkw6aCAd6joC/l1T6nB8Y3YauD5pVM+MsWs0M
DXOtNle4SJQAbFSGZnGkwBYWrkjPwUIZUV70vV4pJx+Ghsk5KM0cSKmXIReLrA5ayu4f9NlM4OJ8
DosDuPaeQfdgBwTdAYfBaaU7+hbBlWV4k6IFKZqQoslhpxTN1tOjI5+AJcmPnB0B68jUufMjBjh9
bnTkjM3wzm8x7i4FBdDa6Qa4/c4BcsWqUZPUtMBssTJGo8nMGB12G/XZ/6Y5eWxz+x09fsbisHN+
k8lmoVN5i5iOu/XbpHbWgIiGeAs0ny/+nUAdUh3LCddBELTK2P59ehq9dI1Gf1o8K32VUZQd9BDS
DPUQq8oNtml2oVVxvSHErWOkJAXtmJGOQn9dW+oBzmC1m82M2caZ7IzDZCU72RR5KIzWb8P5RmPJ
WGA0Nq4VQ2k1VGupV0M7o0PsHiF9AwNWg8FvI2AUw7DDbG/awTNHETOQIw+tZtvf+QH0m8K05u3s
C2JyHejSCwr61UL8rR3SlFYwHJHCCWQfZ3/bDZtNE9bo0FSf3oP0xcPRJBylZQSOHmrswpi3a8rN
k4jCPvBNRIdGD7x5A42UAcDNJ8Jnou+S/S5r7QacazSEm0FqL/oGmqh+ucOJoTjPJ+mq6Cd95GpY
KxweSphO0Q1MAIIoGgT1W2K0839xd61fUVzZ/l85zny4OKu77ffDDzcXAZWJIANck1l33VmrAx3D
lYcX8SZ+uf8LJo7RCVBtd9HVRXVXtU0/TLRBYwCjUWN8JEFMDBMgata6e+9zqroaG5MPqXy4rIkD
dU6d99nP395lCwg4PnzyqHsI9CUbtkn+AP7JqyDmFO1yzW88t7CNxr1xuLed9XT07u8AHbIOd/U6
B/z1cf52EFTHYVAbravhM2mJOGYH93t9bd1t7nAsDD8xd8dfX3duTEFx9seG8bbCHSVfWl0sF54f
HxANENxhfdDVF4gFvWHnxhQQxKOPdbW+yYdxhCOit1trbMTDRI7CSN0Bn8/vi8VivAAZLRT0HzkQ
/fMh/gjmO4jGvfDAYGwwMugk3Nvnt9Ps8cTIELouGRFtS0DYVkoEXRgQ/riXde0zCbc3Eg65o1Gf
7R3kAuwEsoFDHbZ3+tq7QLLYF4j6gyFv1O33RazOehP/fXIIuiLUJ7AF2FUXkOyufay3tcvFoiH4
7WC7Cz0Useiero493f17/K9br3NUcX2wMFZDbZFlUnzID4ZgPeNn0HoUpTRFnDt9S9si+7k0hcjl
zfwmRQShe2s30410EZQP44E+STrQpPGAFU4nb1QWTK3NeM7RQyCNK6XMRR5NtF6RbLoHM87Oo1Gk
Om08gJ5lndiIcYZJX1zchN/ajyAcGySKe+pioQBKmb6Q+dKGbShsyDK1C68I92DlBSdkNWFrETY5
hC8WM2fLz0F8QXvWCffx4fjE26gTZG/Pn03ekz8T/eFbK9yY/2OmBvNAQz+85WL6R8kVaFza0j9i
xWxqBtTMwpJxFglhwzrytSgYKh9Sppb7ktayusmSyyAyVbDx4bHRo+53EsODtIi0EPkqLbt+LjOD
diBWnrk4iRh17h0pbBVXYa5Yo7Ra+cy2Cs7dAt92Sap9PBEfeTcRx/ALfrnrRKf9jTcwJCUCYorX
7Q8GozF3IBZDZ/32GoFQAMoikUDA7Qv4Y15n5C4fF2c64idOsbZ21gZDnxgbZ2iKQdPfxNDoyRFm
n4EwV/6RXC79B/4SdB/whtu63N2hA75DDgmrXi7GKLPAla9UVuZ11tLF3ScHgSsLWAcvZViMirx5
oLPLzJhJLxLuhY56ZaWU4WooFJW2XrIVMjQC3Ibi4h3jOR4rFzrSzpdvulhJQptj/pN8OTWXvOcC
7du4bDwqZfA6u0zbYPpH/B/K+0y6Qp5xbF/wfb6Orf1dbCQ+8A5aWF3sePzUccSswq/DYwPH3MeH
Bo4NjR51sYH4W8MJIO5sMAGySXzkrWF6bPWjrzX0tMuxI+4loa2zu68f0Z0HOzsOtYsIgt7DSNF9
Xo6OnG5mK2sbFPbtzr62vkNRNyiFXncM8TXe/o6uHucGHeHgmpH46ERiwNM9Nj4xNkpenPHRxISn
LzFwcnxo4hTaPH3Mpg6CmHa3tMLmHgEVe/VLQuvr7ehvHTqEt2f/yeHhhkgboIlfwPbn6RjminBA
bzJVyVetTcxXy5rNsIN2GeEgXmRSYSPzGsas6byAP3+W/hEjTxVNhW0H5VXMTwyVmUNl5lCZmF+j
J2L3y2/2JMZPkBy+Hzjou/Gh4WH+6i+/uUOf++MjQ8OnLN/HL7fTOjoxdGRo/OSJnTo2cfNsR2D8
CXO7B8Y8x8YxOIQHkxLajfTu9GrlDHFDvNpwPVVEZ6Zv6E8yNfkBGQrRsH+reJfsgRgVxS5upm9R
dV5VOYOcVL+vXSMzG5buUFfo+FgA1OcVFQ1DX7XrETxQmOWXNS2nUlWsNb9Wkurvmdi+a2z2LC8y
bsKhMAfEY2tz+J767ey6/th4RnFVeBKzG8aLhobQxy2dJ7aJwEg4lpXr+Gb5k/wmK56u18WIqqs0
4jN4Qy6Xp2mBrSGiJVJJ4VN4QO1BRTRHg3wwqaH926yhKNZLYhraBsU/W+uAIWcIac4+rE6p0yx5
ff40TRFfEc/ynygXmHI7V4TZGs+MB1jUmzg6MAznRnpGXih0pvN3Kl/pq3JVDHt2XZZpAPIl8QS6
qywrT4Felzcr1+VK/hmiLR7qj3m1j+0rKcJcaeqFJe2aubvCGs6XHZcK+pO+LnzATMgDSGcYoCHG
DDceA7/lim2zPEeH3ubsKb+UXgBGdFmr8PWvzlNtrIQnHiQt6Uvc0i9pP6zQcpPOoCmbac+TXzvF
lEnl7Ovp6GgHZaYH6Z/xojqFsedq7T+QPVxLR74tsXB6FU68fj5XBMFWX/1PMrkdTyQGu+LH4SVe
HzHwU/p3eDjr9WH//CEvrPPcevX9PfnNQt7qgdg6SIOFD1SFBQKKAnUFAt54kczCpuj3YSG0VFZi
WMciuBiAA5JopoZPYf1pr6viJRCUlb9LIDtDM8UMLDl5JfGxbWoWcRf9cdM3njV07K0x7TMu2Juj
w1B/jG+XMosuBufrOWx2cSl9Syop01TownjNSmGpcpdLG9kvpIepOUbzxXLEz8yxqoQIYP2cCdAx
rqNWAdstgojgbMt43S6bd8lYggcL1g1XMJ5FT1sWp/IMSNqyDn3g/JDJQFvF9/NlVbNuIl9928ZY
+2juR/s+/QqfhFqTJkVfIHmvMOk0FOtyfrMqybprbj1ZURe1aVICUGvCQS+ImE4CNtvcSLC09SWg
5aM2gd6braDSQY5VjP4rIl4xU4DxcnC0sQAXDujNeVpJlsJbbHyX3yxqLhoQnK91+Os1WFbYtMXy
JsM2zXHXczqIzoAg1N0UnpaXjylKn/UVwfGCVtTwt9k2rjTcAUKOieOBoSlQY5sfbYderNOvn693
s/3pb9UZnlFmHVIsN48pKrLSmvE5MTN+ohG2ReFt/Fy76Dfyus1/TqI3pptgKDnz42UsYWQfuiXF
EK0rgPivyopZyzquMJ3sFg2E80z8U3jht8+Wiiqm1lyez1d+3YS1jQzI8YUVIL17SbxN3WMR/Sem
zFH3sly8W0yjGQb+C7m4ARXpBt47pUAulAg+fn0ECjgQUrhfYyG2h8Wi8E93P/xDojMi0zhQLXnb
BK517usi8BeMIs9aeGlnJ4dQJSsYYIfANbJncFiVhVYD7R/LW5TbpQul+yDrcDcc3i71mjQpcCa9
h7uYP5j9WvuUv3+wvZ2FvF2EyTIhY5WVOWSNPq8/yN5kkXC03j1DtKbxrFJQJKhIT1oQBYbDFR0a
Ne0eUFXsE64MLjtIbcAPdzM3cK2mOK9jE4NCXPutVQFHuB63dObL6a9g8pXKIqaaofQcxassQjGQ
jgU8eLlFE0ibISRLXNX8E0UCGoVRLxiMZmW9QRNiRARlOjMcbsxUnxa+za+DXFc+R7al8PaIWJI2
cTRB50ByXm6KVO+XN9HDiratDxWZaddyqlM9crPP/D9S52fXnUUAermNpqsnUF9l1JCaaNv6R4Ul
F0H4TYEH35ovZDdKV4i0StPFL+lZ6X5pjmlLmUeaFY5cB+MBr8U6ukF9cdNopahMz19CcVR6ZrOb
LCAhD/jhGBDu1/ZaeVO5b8yhYdA0rmgbZKwQ6R2wqoCdoC9FX1CnQSTBGZj1pS0phbba1q4eF8Nf
eg61/hXEIfmJx4MUPld4hoCqp8kU6TvKrAhqcsyt7o9xS1RqtbQg5Gx9EzQ0vhvO9MgdZpWr8/OI
ePs+X3WqI+4ec6p17qDq2NeHwOG5/BNWVapTTnXGiXT1Q6F5rhIhwKworAWuxQUXaGzTuymRVQvi
6RnCk3cEemkpZW2v1RhdLpCB82XlLJoNWPZr6aFLRLrwo/nqHFpo8waemsWBXaGBkZFQmpQfejwe
p1ZEsI4bGAjJMrXsRnHTVMYlZiwnbyrTuY+QnbAAqtHNBo4BP7l5rtS/kFJySfkG820A38GtZJXF
nN2K4dREONORnusyyGlzP4NaBAPAgftJ/XekT85ccqXUeRBxQkCTMHKX6edQFHamR85cdENTc/O/
1yw5l9HQxWPcq24iiuuGDGv8qCo51GWUU9OcOruO/5mUofgxiMTmXF+diq5w51dXpVx/jq5glJPq
1v2vdzO6F8KRG3RQCvNHOdnO1tR0cRa4unHFsZ44CTdUVcKD0bjenEiqC5WrXAcDIkn4TtxSblfc
KN6Tq/LnoPoD9UxmU3PCrK3jOWtsTF6QrhufUmt0BvEvU0ghdf/a7FmWOq8baDZS9ccU06TMyt9j
CsXFZGXX9rPwB9j9TIqlV5NZy2IgfZ7TU8vpG//L/uDUgnE2hDOY+y6ZLWw41Q8n7uUfNDV5T99q
wQ53O9UXp7/KbfkuJt5wtCtOdotyZUHbAHUrFnGqI19jR6SfOzs1IdH3sew3IryPhyb/yh8gKmEL
HcJ8HnTBjI8NnhxAR4mZW83D9iXeHhtPsN6To6OYk6kP816J0oCn6eOgh/378aPj8UEs2BcfOGbC
hzzviRqhHWr0jcSHh+thIxy5L94JeyxTSHc/AgzF80jDc3SVHz5OvqIeytVDdaJ8cnHyL03Exwm4
NTSREMUxjy32xnJECQQzud+FmuTz2mtuy5Ioqvg82+LFG0r99tKe8bH3TjWWw5La1qNteCgxOsEX
F2vDko2IirDIfYn40fgE1Bo/dWIiPgwjf3tMlMICv5F4i7UOjgyNDp2AmU+MmT2EG8YnoJBd8dH4
UYK8NA4n0lC5u9UqdeRERzgrB7nyh/w6kx+g7q9+a57qgUFMi4VmABYOR7sOOKafRTgL7nT3vYPJ
aAKekHti7N1GdnBizyjbi0BOHFyUBuiN+X1ub2D/PrfP1xpzh+BpwN3Zd7C1tyPQTK4oreZKlqQL
B7RH2jJmtkH7m73nD4XTq8CteBQHpSUyZsgO7kjqsvqycCEBhP1pEPnnWCZb3ixuIlAZM3T9T2J4
7HhifDf34Ysks0gjQj7ltjTp1JjCpvloCU7M/D/K91lTJFzjj88Xc3JMoToaBn0/eqG8BuQ1xOO8
QbuhdJo+bxDHwOrr1UwWQpyomdntRt2B39gUvtxUX8z9ndLUlM5lTlP2lvwFyiWdL6cRa8ZTKqMi
RkBVNMQ3awS7IDwCBZj9DALXBQMtQI/kpfydyrX6FPmJ3eXUqgaFCSN5k1tO7KgHi/H5fIGXVtWZ
4XARJruYyaYX8huwhjxPLx+J7RK0oLMQEzJh8t7dL4XU/oki77HMuvl/Ql/yC4K42Z4Jb35Dze3b
hY0ZDxqqEGxNyRCusDpfynBXHkULIASZI5zgjJAf2DjDzRMtvLPdLij8QZlzYRsd7pH40LALxN/q
VPE0I78XqifYI40KDkYpq/9UIaqFPgMM7N9LG8Z7iYVaOjsohSFGxrtsBVFyWoSiYdbTxh0ROLOu
xMjY+Cn0VJD3wEWehoiX/+VxjvpziTG/gtmyrcgoQtxIL5xSiyJcerQywDZkW24kqQ2gXsGJGNvr
8wd84ZA75PXCb06N0mvdwXKFCJwN7YdS0o7UjI+S0MfBoDeAKeidsnWGY6ZYDALTf2G+5m1X0ql+
o2a/b4yNHzvxe/UaMXvtGhtNnPq9euVst7P9CAuHmEgPbfpo0reKGkPwY/aOdpPMpiYI+WXyx7kc
pY2+yAOe5YyppBuXpUsi5S7l4tUwLURVoUyMyWVFaWqrkWtaSZatzyVgijHhw5BSRk18Z4Fc/oUV
9amF6fole+v/sx9pTUojnOQGQZxzJYPYQc0eTip0wnwZuNr3TNvA1DDpS8yNaQpJcpWu54pABZAf
ZB8CPyCTDa9O+bZlHdlMfVmxiYbPQ4Aq1NiWvQXFVt+2N273vzJ9S5lGnAbGAgsfj6qUVsWbeFC0
TA0mRtHJ+pQ+2QABsP0kl6EY0zRfx2w4yjfWoOuDKN4p3ntpECRaFaF//JYGUxTMRV6f+cvjDnhs
6yJAefQ3yl7QJVNnqjPiFc+2BbsqqsIs/q3t4OFDhzpbuz3dHf0eNruOmWwuaRX7TSgswTRwK1/q
KHvjwlfZDevjE0JPJ4xYMaNyJCM595osFq56Mjv3LfkcQIAUnvmFwrXXgBssFDZgpaCgYse41DV9
jIphyhrh1lQFY5rlMyx9C9ZOXcTw3UvKNEHXGrsFNbVwR81SnmtrZ60NwnjpYgoz+yiPYKFyJamk
1ozPEfh3FWPA5SeZBYZ7Wp9E+oaRY0iSMADcauccK/Cc0iy/UZxjqfMYWsn+9jcmfVhS2WyF/t9m
CiSQhenq3DAeoQXxCkfbEt4bO0jewzBqjmWgCAVKtyT217asJMsqpbQKqkvj0u9ySooOC2vi5cwk
iYkBjNWYQf92E7KMYigeC+kZZRRl/PMTpIzQjPgTS9L07ERF0Z5s1sJgb0TLlZOqft+xWQZNptjX
2d/B+jp6j3T0MszlGAp6X6l1iZl39YEAi9QIdvciz8OlFO/aHFMeM/lWPVMCnKamsxd5qLARTACc
pKxbxbsu6YUybaU+MBTl0Ss5UP0IObZowil23fg0+5AGh3zdQoIECvmmS4X1ldvphcI0ih4upq5l
HgHdCXj8LnagF7bA74mGmk5NoKMITPmKXltQfcUz45QdlX/1hBVmtSRxo7lHMGYvopIspc2Zfn2m
NJ0lJhiL/QutBcLBMA68pqy5GrB5QKWbyP+2vQj7+elWFzPTFpbVBQ1zwCqltEDutkWortlNDBff
Muaaa/2IVxWEzucLwspUp/T7yS+Y8XP+LlCEfDl9kdqYY9pn/Fg3Pf/F9405fsTzThqn+LdamIi7
4HAiMgfhrXdcHg6ZiA71LEsti4i7kGmIsnbMmb6j9b7hzjwWffud6i4isGvK+9nLNEfTGNWClgyj
lpvPLqPMfQFRlSuYuzhTQwHHsflzXQSDqoqaUQM2SsljbSYXZ7oN7QTi+T3OW90YlgEGBP0GPaHf
odtAUwtwxONFgu1Up5w8G5cvPknfEBlPWoSTHzd9d1O2hBWIg+uPlWlC1+XLmUlcMKBdEmId8xeM
yyhBQxM4ek2Dyk35lKCCnnqbJNTxbBsXKMGGY5CbkM8CbnEXXyyCfIKksqnqVLniVL+cnIokLzPy
A7hUIb/zJ4x/DIAEY9ANMXiFyFlMBMDuYD9AqzRsC8cUI7wQhJAa85OXRJvK1CjcirtLpPet9Fkg
jTXd78KStJa9TR9UMA0XqKjNKGsg79lGhaF2DyjbcfNjcy4WxWFhfi3KY8oVDgpTMhORwrx4VtN7
uaJTch3/xIGYDFM+ZoRcRyh685vDS/XzGBq2rmk8d+on5ojxPY9nF8XGSC+kLW3K1Xz2auWuC401
HM3G9BVFgeVT/yn/hOaZD6okPHN0ff4TEIJNAWFX0+ZEZi0JxQ2f17vXxxWm6nSa56WXnipP+aOk
ok3jfzvs7YZyNvkQVvz84XxZmsTvWuyiGYMGC7L+JScFbP6VB9bR13a4t5/5iEmZxAmdKLi0LlJN
K8vZn3f/ko6CMQMuaU37FEMHaI0p/ogHEiBpKheWaAOvWq03X9pz+PUpYGTlaXUBw+W+ypflGpoR
SvpjOPZwXrnewfQnxgu0e+zQkKnvYNjjNZvIt8uKK2OzkiyjppwihxKOMf3ZK9ui1wPe7UqbY1vE
ZYnsN3ItvUpJaF/aIad6DpkqK//aA1zVluxlxPvsdE+xFPHLPIoV68ES4YZXN/nX8lbxKyEPxI4W
puvb0XTFsTl+FFz0nRs4EhcM+jQf2nmAw1lKMenEmLqCsR003h8p2oMwqjgutOBsWbfbmeULCiGB
8mTRXOQ8yAsoe7OgiKgwf5waA5eOuvs7af0x6nJeR/SAFeS93Tce4gfbqfEIwUmosTxrJ6hDe61H
FGwlranGLlBSZv+JWPySU/Jy0GcecOLuXJoR6XuV6ezl/EYjLGnb5w/b2hk0gKm+Qyy7BeJXPbt7
W/jPAfeB/r+E/e79PdFI2B0L7t/X624PtL8ZbTif0EbAenl7Ek6fz09f6aCQrGbKdYS+7MTw28fA
vyoSxkMup1eBl+BX4/CCSJMXz+DXie8XfiDpsNnlkLPSmrFE+ds8zB997TX6tiXiHJG5fmB+aXI7
F8TpM/rAJ34/14W52V0d7w0khl09Y+8mxv+PuGthbuLY0n+lobbuNbmS8Ohlia3sll+8jR3bAVNb
W7UCtIkqxqb8uCH7D/ZnODxueNgZIY01M3rMDJZnDHFkIAkJJsQbV4wJjllySWwDoWr7dPeMRvaI
5Fa5WarAQp7p09PTffqc0+d8X9dgamDE13zyZHJ42Nc5OtI/OPiB70B7pHFrM0HAzTrRnxp+38ms
qhkfipjTNpT4EAbcRn5iPLDtZ0eAmm9wYHjrrWH3rXjqQfISEPhtvTKCr+wfHYb8LLwF3ihY5u1d
fiHcSOLoZHYARRZK37+GdRHY54XxYrmBsHx659eb99VVeQKYG/F1QjiGr/NpJdISxPbTiw0fApj9
yi5f7lL6c2PNvI1gwwxs7VoUIXWuoFkGCvJiVAhS3g7bgw4HatMFIPy1B8pYgMCwTjkBnZBwEbHO
CB/kZ1S3KxukEAA2VvpF/TlVG6O9lPvYBgOYA/5wMFtpnog2p/+G9xRoiJf6piQbbh8+/CZ8eMqo
geRVvcLA7PiIoYbfjKlUPPM0+caHKKeGXeEHncDW908c5zelvmDFRsxp5SWKbvvp+9krNnRPPIYa
InFqMFoT3AaVlS2Soslx63b+Jx5og0GKdY96mw8fQr2dwIXCZbZU5dFNmvA/my/kCU2H9D4+olj2
cuIMYjBM4L5st4XtiAuyKpHpmQsB/YvidGBqMf84UDLTiwGbS5GPXKZiJrFWe0K8CeOVfTYrjomP
1Mp2r8SqaKp2bG/fxtZQK3ykUTWT+YasQigMBeZtwiLOR17EOT3RfsAmGdCyFNK89GlVrA2JjAdU
lUv/o8znl/kICrntZSf4h+0DNQ8G5y5PevBNwPJCJBL1Nwbj8XhE4NNLqqCyVwChzMBu5hpAnM8D
ircJddt8hDKY3yGSQY+EWCOnBURVFEPLt25ll9GUpM8rE1ykMZhdIFFDjEWNmMFc1RND0jUWSl8w
yVgaisf5CGuqBpXLQOkGnBf6rLmEdxuBkxJkmLb5ZWODZNTCGX5GfBiAgltWQEtwePkIpzrqUEsP
0p7jB9Yr5joDY0JcwAyqktkBkZGDcxrpqT6PTVwAjscTORJoDPERSlUWYCOCR8NHBlU41lRurHgV
hXjNGoEti7SiXLGeI/GGfr+Q5iOKKhlZnhmHLK1H2k8A0HefLApORe6ObAaJCaXBblnkrE15yEck
O434StWlHMkM4iOGqprsPfVZeYyPBKpY9ndio7ytvefAviOoq7u940B7Nx9xVJX0Do0mUc+ZxMkk
eMh8JFHV0ft+Er2bGkmdhgoz6xu1Yt3iI85WGvJEsYAADAe2ID6iqO7I/29BRcoDScLmKc2JUfmo
f4buohlF1VzH6l+TNAllV7ht5gzipZzBslzILJxNYoHBmZTncwXgrtJ+wg5kefoSH1mxLbIsy5ri
I6vJri1bw34wJJWA3ZK9Jy3xERetFRdB251UURUVqbr54KBhl7RBuWotBma+k7/iNEnC1aCQ8ip3
w3jFRwzLUMkVVesmXgaclKTA0DxgHtoAreZtPpKEbUfUqbbtUhhFS7nC6aXYCB0U+gR4zLTL+WXO
WonhaCiPMpPyNCBqYrGclhNDz3BBrToIW/EYH4lRBjagL0s/EqD83ENe26bAECgcYXplqsBPWHiT
sHntKj9hoU3D+IKf9SE4SBRMGEzI/DI/ccz4AIb0gio+5COEwf2Mz4xnl/HEyL+yJuDck4Mohg1A
WBCZ315+kFMLFh9pVHsc2X/Idoy4Kiu7tH4FyrKZ7uAjiMHvzJYW0oskeMonfCmwInhtSoZMdEgH
ljQ+XqzAKsO1L8rfoda//AUQOPhs+k02B1xHb+cRvLKUCW6rlxUhH/TDST/ajT/0Jvo/2F7gjaow
qiqmRW2sPM9HAtUTEPBTnnJyDap1vy2dnYdQz/72w3v5CGIhjPFimURLCeAdzeYhGQzTV+VMyTQn
fMBs3KhdMkqwtQCSNdyizzIYB6ceAlCD4Rcq1G08V0VINl0wzssTFPuK1AYhvFNcKVr6bOYyuUEc
M85DssTNwpoFZ5DSDfHzat2scRH/k7teGPeJC/pL/MO4C0FrfF9puVj2QUomLf8vjOeeyxcZlycq
XStakPBV2iAZBDRdmtzWsP9Y1y6SY0tKRrH0iew9fD3kT9ap+uJGxSiwkmezrK2V7im/cRJCFeXh
5Mh/EPrqjziJoWoyt6w+ls8hZV4RRV4PFGaYW+KYPUE5CQqxiDsBswRkY+ZjchIXZMpLWrJmiiqX
7dMlTWAPh02QNWIvQvbNo6LFSRxLw59XZqVKYY0SzJjWLifxfQFyQPPLxl2fdtm65WAHEXjNecIc
DqWehPeraM2se50ZGmNTZRsp3c4QhRZdjd1CIjQFbTg1iLxWd6QaTULiZO5TmdM0ZWVT+qclU1uB
s/HtPql2iaIKSzad8lGewqjiam5ptQMTxSyvpc5qoABicbstIZcQqrgKunkN/JjtDum4BIWYh6G8
QqaVu8lLY7GCphJeYUDMTs4/OUmytRUQA2xv/N4lxAaFUR5Kmm6psvgJH0FhliT4cUGLNyFs0lyR
z6UXOcmi2uFo+5Hed7ubuWXpVeWxENKCcsXYYC4nJ0lUP0iTeOuyoXIV8YZeRJzkUR0hT6jP1Tn0
BkaSVQIQZCms2Xt795JMYo4qlyX+W7cLd4mobZUClrQth519z5WAsml74yyupxGqQGvOCYHDbvpW
hpT0Ag2Ogv9VK/Bp+jqtgIXPhfsFdcaET3g8xuFnySxOlUz2eVlfhk+kqVxFXJ0qoKmPddrKBWBY
pHeWlsnPtewK/JwZF8ndcDxBukSLyny8MMAElqKtp6GvRCLvykeBpUDDMQxA40RQjcj/4iOTajkK
n/rn4SqaHUF0qlt/RskY96CWaMvxVn+0t6k15A939XUf8wf7DrUc8+87fjQU4jVMTW4IMqfnJKFa
+1z7iSTR7yGGlg8gN3wl7IWoF4oq/AdZX6l5Xh2L1u9Y86m/JgZOJk+hYVpGYUMq1hnX/dHeY+/4
e995pyPm39938Pg+f1s0vrfJ3x0LH+3g1f1I/e731Pbai1x6yzP0NsV6+/x9fR0dB/1tvW3H+vzH
W7pjx/zHw6G+g7yeIVz/Gaok8UAA/TsvYG+0a98+f/j48baD/tDevaFef3coGOvyh1r6evfx6nyo
di3+473ubmlrjfuP9na3xvxtTfGmoP9gvOngcX9X99EObr0OevR6yyznI1rwEF1/pfHpA9knelo7
0bsDqbOQIxD+4+Db/Go+BJbtfsgvT2QvF1UU5VXsIbD89tJn1y+gnCItWX9H/GWyPFJsvQKfT1vn
sZ4/x2Oop72hUCgb0pI2Jj0tWLv479ks570l2dnzRgA4hGrS+33PJ0fs0fc0qBVzCtDYXlNGnslr
K3sITIFuoXg8sxjRnmtjlHVhBlFKdqLvKSTejHG+oOqzaPJe6Unmsjc0NRJXpR+hfky6EAhQSLjS
OuRYmROmRcvSbpNCMshgZ5wO1FL3bm0Mpf+eM/S7BB+uZEoSKlzHDVpQkIzCrCycVGRmVsomaZkX
FIcQdEDFulInR0aHkujAFmhRd+ej0Qgt7vVEVjM2fBC8hsGe3qB1uOP6/A6ChlVlf97B61noZiM9
zUGxRixQ7xnsP6GmaN1nYRgY0Air6s9c1r60I4mQVM6y2UHEtDdqJ54g1/AgyKtFK/9MrQBzKh0P
Xs9Pt613+5OJU/llO93eydoA65EmfLnWjufDQ/k0YQimZGWrxqvCHQoZsoMiH8/LOWSsGx8Dg5l3
AaZrhGA2ABcakjRybg/tkf8rDwv30wo9/alDqkQu1udJ9SeBpiGlnLez90itsR2Oh4u8ATtcIn32
f8qVqTL2tXi9BLqBtyY+SH6YGPqAgLxsnYbeZiZCTUAAj/8KjUIkHott+X3rsa7meKNT0c3nCRpd
Rx3mOilbjSQ4CWP1IZaV+TSnUMXDgHeZz0MXIkcoGYFVizgsZsA7BlFSDkxn/x8EZwIrUAFiN8Cv
qftg2TljDZ7Lt1W9gSZjjwz4Kd7aDjBVbldB/I81HyU4rPSYjK/mF6puqvIoc1N5uKkA3fOZ23q7
fEg8Z1o+ZK5DfZ/0hB5oTy1iR4sc8bmPnrxBQQAEpPSEgKKWZv67ehaiV8RpEiMCNNmpmwB0ye3h
qfn0ziiom/azZ4aAZAY//5/oN330i67E8PCZwaER+E3Qc1RsjLHf9HkYAR1QkOVVvJEcaOnA7zMz
yO0Bwk4eBd6sCmWNwAhxNztZYY+mF+44yIb8hQadeji2wqY31DnsVrwGZd6GRlo0ZGzJltbZfmjO
ZDcYlhmAT10kqB3YigSrUlz1LqMkoAoSuap0E89ZPFXTyAVbRHMtAIOBaeD6hC22oYUVWfZX9Q5+
EpgnY4Vxhr8Clk/1KTW9+ESWpnGHv/RujErG4wD1QlhwCXA8IVcEuNex9scfX9gc6HzeTBXKZWaq
rH9F4FKr74SGrRsiAiE42eX9iuQ87jRNNsGDC9BCeBSIWcxOLR3tWMODUQfV6zyjlDQteZoAhdWc
hAMmhvgCfzt95ToeK3GMNxqpwIq69M+LxclntM5RCAgNYPGTDVFbwe8XdHCd0bFRpxwaPLxdaHMF
FU/IzC+wMWLNQxqrZQsKeA8PMQXF78UXDsEH0u8XVOwrSg4eHXCpM8BYCNJbdVqi9TJ4BGEj1u/i
6SqOGTl4bwABDqlKPyJ5nnHU6PMIOqnn6zQGaUduaFgWudMr0oXsPReyMu5m8aq2hoeCYSnXf8oa
4LG6mP7hCHFnHIhcBgiI1ye0QUhIXXjVmby+RFKxvJurdh+SsuyULPY+3nrrLcILCx84zTVWxEfP
a8jbZchT0UDkEPqH9i+7167F+dqRZK8DlirYCNiwMSYAFfFGFc6P1wpjdYRqIXcOG5KQ9tkymuo/
lRwim1MNdbjLp4gKgocf6/zBrb3KfK1/sQcdbe3qaom017uw5wj9CYQmgp/9Fepdfaj9OLs6nDxx
1h8MNZ5F8kWUGjgzOkLcu8w4Aac/i78EYHteQ1bNm1N/yf5KgFQ93H7scIX4RSZZ2aT0iQmZkJGt
NO+4Jyyww9W6YPWUmj75bPoq1ovIzU1OwNr5Wzis0pL1IRZodEcQG6KRRrZ/8hHu4EtQsGxYQtHN
r4OGE99AwJqVZgJi/zuH6fA31fNLenYfeTscjfsbG4VoLBwkv3HsAzGjLOjzeCFd++7aPQfmfPIZ
3pdI08oE3o6u6aj0WcksLSCCbUhaoDsbUs/BjoMAiV6vOJ0hhlpxmjKtoSO9ZF/W70saN/UmbFJv
ZMUClnnr7h7Ed1Y2ukUfdATX0al8ehG3k7np5EQHvWYn907EaiALWVdghhjrW3tDeAuqqrRe3MoO
HN4GDmlinqZl9WdphsK53UZVV4JXmIPVtTIVDO7/9FV4htJTc2L3G9F8rNS1qvj4S2S8J6+wt5Xf
utUhwDrUl/AOnV1RXmkbkP7ns+bS36HiDdMSv/dZS8orfdm0CndIaqAPSljhtiC7TZmwlhqsW/rf
MqvYFjIuat/u8tGmkKakiSMXYpcWMuUxX831u3zGmnFen899T6PM7EZJKoyLv+FXVLijLxE7gdjV
wHpN3EYf0UlYNVEiDUkyLVZaSzQaHIYAxNQD3EK0kYBXAkkhgphw9jrQr3CbYGFGZjc0MproRz0j
o6cYMVmA1Er8G8x+IYJH498doikGspN+iGfiogOdGQzQoy7K7xuPOYRKXa1AmUHVMAHTEj/LrwH+
s0NtRG4E4DlGQ8SALJ1vovY3FPjPnhIEVLN/05cUWNP9ZZP33aRap/YrMLfMdb0COZ72dyVT+yX3
yH1hLOCKADixU3CQIMORkRQzhLvmU4MnkhRrc/j9wTMOM3HNr1P9/aOM95dCuDFu4lDbsL8jcRYS
jP6EjiQ/RGf6R99L2XieQtBupSNxcmjwdPJUKoHaUkPJk7gd7E84JMVQLbz55CK9qLxyyInd9w8l
E6c/TCb+mhwKOT2J4J6QmZEaxLLOou5kfzIxnESc8oZYXXi7v2Vw8AM6Fyk1JTt+hG+I6ktndNHF
88OpN0EXQiJ29eU8B1gIlzhqTEiV/GNSP4n1C9QtaedoGYMNRom1YYQhJXPqh50pLH8nPTXWpm+5
e+Pkntm4SPz6EXN5zOpjeWL66+wc9pddnXHvDhz7EXOIh7SvjMmilZurkyrCeTwY0MVj8H82D0U8
jvyk1nHrnlkXmFbSJJjNxLqBpmC34ksPzAriyRSXtJK56QneRNINK5PvSIwcTpzAG06Iu1HDauV7
unp6KEEGf4nMaWzu3Y//HmhtJuZjZAs+f72sJ069ouoUhv1oCm9pf+QPmQle5VAMVFxo7HNhgZN5
TQu9iM0BYUKC2A3f4edWyjmFBA7ccWdCjeEI0HS8vitFtTxvGUjCrvWl3KcQMVyjgdL0YnqR0TBb
c9ol5o7KF10tEC7KbzIlWqplR/h55UAz/ADXqwYnkMBTs6MUeNG81hLdKXqau+jm1ADGrDcNAr6G
ZA7oszOUCZ1onfZToycTI6nBAQgj+I4MDvSnBpLk7Ihe4qm+iC9WUAP4hQJ/I5KUkoltZThPaIIJ
ThKNStdySnoRz3ZAx5585tmQPQsEMUM4QunyEMfST/RZB+hdG8veI06feas8RkgR+YwlA04ALUFc
LU6LkCEmHOpJfyk+QKJVyKgVZ9P4/T+e7xaS0vDKAJRcZQJ4XGehWmVBhCQ14zz2mcUKTU7Dy3Kl
oOoqstaM9XphWAgFST8SGlLxM+NX7GuTMxHXqbR0w3l1nPYpBvSgv8T7lBOzwhsUKezchbLfimMs
EAW+3Y4/NkxpGbuq2P9DMy+lH/FOm19OL2rnUOYmttHVn4u3OVuzDFNC3DDOU05L+7mIB9ogrpKT
Fkczzhp3/nUX7y2BwU909XQdaG3fEmGoGUVJKqpTHxO1vjMQ2P0+doZGEv39geTZJNqd2kkOgrEJ
tD8xfKZtKIWdGOD4xT48JSSadYr4dw4nR0bPwG30HvLdAdoY6khhdwj1pE5DSvd7Q4nTwygxcAod
Tp0YSgylksM7geca1bllb+J0qv8jNPifcDNWbCP0crj6QNueJvgDn/HOteef4APp3dfyz7Rg/4G0
VJxCO0lzw7i1tuRw6r0BvFnuBJJl1g7cgoxS7nusRN2jgHYP7USEYanm+VmjwBdifYOMu6UnEEv9
Elo6lgJXHZ1iTuNHeNmexmIDqYEUvhHOOWwCtsKacR7uAB6IxHvJkY/OJN8+kRhOnUT+f0HuL50e
k6c80PHu4ebezu63d3YNn8EuOB1xfEv1N1098IvmNvTPSHqpzVgXSE/hbmduwhvagToP7eC3gzJc
ktodlJMoxy47jLfDSCCIuro7OYlikfrkCPbw6RbbmhjCszhBclF4W9kMq6Q4lflankThNtR3mIRi
eVu+DMEEb9o2xpfNNxDnLpshm8iTeJGBEVZ6CoQ5ZgFQ23iLZiHwpBPN2TuUTL4Puiv+mqzhUMQj
93l498AetHf/McjaxFad0OgPNwWbYv5YLB7mRBDBoEJoSEyfA6ZrcwJMdXhx9fsfjnDkZWLIInv7
UHcy0X+aBcGGUetQMkHSysmHwSG8nCL4l3ioE/2DA0kvSiKom5SfSp/Iks81M30ofUURfUh5kVPw
99+Kj/QKCdDplpdpVJzG1sLGDiSbRdUHc8wHhwGQxKzPqo99lDeQZmL68OAt4yH8wasdcm5GoGUI
WATBlwm1Ofs+ZWicyn2a/lqvOFSIXg1NWoTpfapQm8UDl3OyyhgKC6NIZOhioUDc5ehwElxTseY5
TV+TnP8aJmhjMv0AZW+mf7AWjDVIzZk1LmLtgS3FhdfQLFJDEluRy+TEAC+BHVtLQbmMQ2jrODgB
boKF+rrYwuvGgWRIQ7IruH0qcdrSMiHfIjEt2iRxxWgCza2yZ3YIS/yrQW7iZLpGg+6xwEvgljnB
zgPqV5tEGkNbFa5dnyFf0/+mrPnw4lOKV6tJiKHsSm2attv58YiY3FRlfR77Xtl7OexgAOX3KgIi
WkipNLjS+zHUncxl+SnSL0BSAl4Y4d+tWkFhoe6opBXsgdltsTAl/FibWiSGvT4/+bKo5tK8HUKG
8EOnPGPCe7JpxvORzIB2qLJHVNtvMqU8BzVqkxZ6JHXiLaQ6v7C//ZLw6IbapjemJ1H6vFkmAljF
UP7X3BeiZ44rZLHiFVrVPYgr7SeDAgq19WALug8rfsGHbS6bQqo6EK/RM9gsg7RMcpZElinZ7koz
EEKCIJ8s/19xV/fUxnXF3zvT/+HmpSPSlawPJEFm0oyCqOsWDDUk6UynMyUgbNUYMRjb9Uv/F9eJ
qeMYVhYLq89dWYjFsQ04ToztJE2GsY0xsZIpGaQ4ZqbnnHtXWsjKvHQpD4y02nv3fu09v3PuOb8D
/YGK4SY0+SzaGikWLy5O8zxucLNoAHqy3Cx9oFWsm7MZ1erUeAgHAbFxEOZs5nJt2WYxAw+NGWb/
1DbnkPjR6hrtqe82HIxQjJdDPQhZlJQY11J6B+KjmGYq5PHadYEnx8AZp5wZPNUp9KesYrpz7QIi
K8IhqTuFinxRed6E905LFy9hNAe6idfquW4RVBhQWIR4ZGE29c+M5Xwp6Vw4i2BnWqgWp2izdOgp
BGH4/nXkFKjsfRPnR2CYLZ5s/lDYQU+2oA12iIC68n6MIjhOMn0luVa4hjbbmRsSpjZ32rnQzFg/
DViDnNkBGPuC5ACaL6lThS3YBchxRLN4ou/GMg6bxwQxVGQkPnAaEGaQDYO+cbT/FYEV9fckVZk1
nYI9rzENw4FW8d3QKNn6dklBRxOylAeiQjdpmqfKok03cq2zwk0YI5AkjfzqvR1Qu5kn3aER8Qqf
ldg5RtlUWXdiKDYSHz3O+hJnxgdBLYs682RBa2V58u5wCpdwh7WXO1HhQ4GSSwzS4RhaGMdOnJeY
sSrXJMwofr0qIQMYaYy28yEbpW8OwSTIEpGJH5pPqdPl2/Dlu9KTuR8llkumH4Iy+W3x3qFkJrt+
CKkPbSsCySRjACn+L1Sw6LuHjmmbjHUlzjHW8/7fYoMTEobaVktVbROeZ1dJd0IYlsZQIwaV0tdO
1KoUR/MIt2Mm/5PNXymvys/VKaRMtasl9dHM5UIFdj8O2wGuQqHA9apWEzqesgFvYnIVQOBP6ofM
j7/Y1XP9JRTFPd11PD68UFVvtmD4ENUJi7MjCvoVynj5OSDh5Cp/gm3uX4oywKOjyuw1EAWFdRAE
dccuSmevLxmfWs/39oqYN9/8DXNlHnGHInQXp5gHVnxAEXQgbjIryga0J18uZdMPZmtUh0Mbr+BI
E1v/6BBZaV36Es821bIPZMBo/swzCvuRL+iPGcb9YVDkh7x4uQZjjOc/xnL6K9A28M23n2XTcQS6
vwkjUvwJpvyFpR7AUiDFL88toddJYQGfaFdNXTsyYQ/UpTxEWQ3DiUExX+dv6F+85gjnlmB/ozgh
WOIyyIvA/kCcg/HWZmDcpBeokwswZ91KBbEcknrB2s4Zfo+PuboSxxPibd5vQVBAaSBK5S2CgYJL
dmmnqBnAkAWdM9EJzrqu+PETE6xvcGAsBvPhd0gWC8K6/CX9lvIYLWZvmFgGPnP8UK7ZDRjlGTdW
tBo3rUGZuSVlkXGhi/5d9UGkl0lfSq7ZKvazP7D0VPES3YLmrkyWG0ooxBEWf+ZlsSbfxmt1we/Q
SHAkd+xEfDSBncfzBArtE82yVTlT4sx/hbMeIFcItNnipkDdQeUJwPYaHpHaBmULrQv3U6wYXUnF
Fi+O6x2D6YLV79jAee4piT0PerzNo1z7jqLcdwe9PjfGHYVa3b5w2Bu0NRDfmlMxQXgS/gWimp55
VpzkcmMnl7HEyiUrbzXubQrX4Nd6GL/6ibGE0ovXMaOn5tGs9hY/dCbTEH1CBa9JbbDdLydVfhtF
+weiDttaBLOhJXkUngG8YYaxwZJvBI46GQzVaBAHnW+PoycxTHurx3sgrmqCa5D2t/cGzsZgvYUc
oq0ItNV1IWYqQz4kyQq1cgMLvlsOPTpspooEwf4zmgNHnhiyIKLI8ERsvHN4GPDuae4mF2qv95jz
HznUimCD3IZ1JBIjsLL8B9F7k2HeajJhvZEjR/s7j5FJ873Y+7GhOEF7xxvDZck7XZ2RKOvGk0uh
KGHGYH9zg5awmTfIcIRStTC9WGXqD8YSernDxseB9+xk3X3IZp8jhyIK5OcaPsF+S2Ax953nrEOF
ikDzNvUYyxgLUDOW1Q0zSghbwrffGrME6ToykoKumvA6Nj+t3xURxjinLr7afzs+cCrWPXCSAnCD
LU75VAjSv12GvSgy/pmxBA49tsnpf3ubQw/0N4zzmWdIgt+g+UEtAbM3uHp/19PfwyLH+luYr7gj
+Ys7+3Em7WEgMz7PZQASFbZL2dRVTD4y1eBgUK+B7C59/Q+HRLGgDbTrHzH/40Yp36MfbM/7gqJ7
vDMNiW5mWjEPmiXGa5GIypjzDfGjaTy5grtTldktrdIYKVDBHy/coVd+V638PiplrGW3XmPQArh8
7eb1H2krIQye+kjTrTuBpRC8rKqauuiwyVcwI9oNa/cAiCNkEUUuJVjQIvQIxDD7O6jyXon5Qt1s
HsYNuvX73s7DrLBS+oYGQuShAUxXugO7PFpi0L3MhRzUxRfyv6TUR+kr3I6TL6nfYOab5Fe5ux5P
C/fOrNth8Kmg6uP5AJGmART9hAlYIGzmuw0fmJlQ22Rq2VjCZkusETTUuNaIsGLp+7hypTqzAZQV
l3iM7/fF7YVrJltb/WYKIGschZrXzfv0LwpVpIoQl7sjf+K10QF134nEmARSdjw2AvB94JzEjojI
qzj6cCgVWFIYUJR+qU+C7E9fMe7MbM5uMeM+CAD5ReF7EesG4PNTVS1fBShcHwBHVkio6Qqh/jSC
0jJ5V2tbi6RdVifpg3xBz/IPX2rf0Qc08rn8rXDFgA/hYIuECcUKC/otV8DfwgcpqaqTxvJMyeUL
tUjXbrjC7XD7C32Z7uAz7/LDR26Qo9qyzwpVuq/wtfwEy1FF6SvKY1erF+58qH1MD+P+vFQk+YTq
Sz+YeUDfuXmRrunLpbV6JUqa6evFF3QPtlV/Wd50hcMttIKpifJTuYLlHBr94D6j7zNH/8+0u/vc
Xt9fXP6gt4VR2nopB/9cM1dapIXaQlXCgYV5mVvKbYsuM+1LS3G/2+s3i/fHR2KnEkMxTP5DAyUt
zCsKTImUL2eWaDB3Fw64vQGzsP4gu568LeHUKhuScT8zLeWmCutSeil3N1XRb0nyc3jl8qBz76qi
1e1trVcBv16vwgsEr9uqOlWo0KqByea9gGpn/q3OQotwXnLb6Y8Xr1Jl/8tpqFPpCy7PjkjDPwmm
oAPwcvfAaTwkPACvPsHBuacNkfHBE4PQjoPwaRQsmHta0DOOF9o9vgOIJzIpICPd1hbgWQQzl0nu
w/05lH/5CxfFb9NH5vOA+JGvuktK8YOF/6gbsNHiEQhSHjWe8mu6hxULxuf4OP2hvv5Xig32e1j2
O+1beNGeMje1RPm+vKovQwlY5JnkF8yl6eVHlDPX5ydZxvmV6IAm4GGlrPYtT4fgBpg2D1Jp5kt9
Mpeb2UTCSGyQmXI5cmYigWtuCOQGHjQNDUwMsGF4T3mX/Lu6lJnKPqMuUWcyK8an9c5I9GPxkiFj
KNKT3FXeja7Di1eNFXdmqrj9K3jhoYeWSCV6S/kdyP4bTq0xrABgin6L2AmxmHab8YIgxIv3yiW5
Jl9EElKW3SpUQajhdwQ+HPHkjeIlKCHLeobN6KlLPDLDEhu1rChzyyD5ivcshhY+aPpyvlycVZ+7
Gf5HD/GXcyVlkb6hb3p6B7e+p+kdJqe0R8gImZOf6tM5ZObAScLTpmRqbkqcJmVWYEcERVurAQCE
/VGpSNDm6xfSMszehYX1cgGPoIyl8mUEEIYxu5X+TGIzGQ3AyUN9uk5/pV3Ol7NbBBoRGu9kd2Bk
uNRCnKxsAJKDxmJf9Kc5g0+saIMlHTBeZ26Wy6DPEcijjC4xbRODFeUaNhGXopbOz+uPJeww0z4u
rbGf1QLITU7B2l5N3TB9FIl6EYkDYKQRZhCqIGNarqYonCqM3ykOkwXKUtN63mPch64pAErCQe/r
Ia/3dQCABM3uehyyd/m9jcBbbRuU3kXGFzePuvMFfe2twdYAMrv4wuFwIEwUAGZMXrg9HICffW4K
zPN72xwiQGm32xXRbNA5ejw+GgPpgBgp7jw/UJutkIr0H4kcSHipYEPdK6De6e/BS12Ro1EW7Xy3
s6unt7vzaD987vtDf0+v880K2TYL9tKh2OmT6Kp+YjQ+CIpOFL5OJMbI9rbHt8GRdgWbYIqTsfOW
GOT/T0IAW7xD76EphF7BZO5w2wKvnM+OxKmxkdhEjB0+0sf6zsTh0962NY9Hh7/BIR9svVjdIMG7
MRbY6wC2626/5e4ujHOIxs7GRhJjp2KjE+aSekXxgCjO2x4/Gx/hAVexUTzO8jtFRP3KIfzjmfjg
SQEqnSK8tGtA7p46Bfr7ZHEvmRcLBh08vRXkm/aNqeYz9DJaG2OeoTvRGFthsgcXAgJZSaYURd2Q
BNhESIPfncic2giytpVzkWgf602cAynX2/E28+9h23WiHWH7IVKn8hlC2eFXEVSbwSeX29sIhusP
WS4FwI+YgW6pkwBo0dGfU1GkMODQES9uuy7wsEW66rgvtz1S6EZCopOnD0KbbW3SgkDQeyB00YF9
QdtZ/wFo1HatODI6ERsZiZNW3caGxxOn2Lvx0/GE84jErjX4SqHFFAOL0EqOKZMda8d/AVBLAQIU
ABQAAgAIAFCFRCvPKLGse1AAAFwZAQAOAAAAAAAAAAEAIAAAAAAAAADAr8a/x6659sGvLnR4dFBL
BQYAAAAAAQABADwAAACnUAAAAABQSwMECgACAAAAvbxFK995FjPoNwAA6DcAAAwAAADD1r3FsNTA
0y56aXBQSwMEFAACAAgAklpCK0H7znl2NwAAZ7IAAAgAAACw1MDTLnR4dLxba3MTV5P+7ir/h05R
lbVTkbDlG3bV7pYvAhzwZW2HJKgo1Vgay1OWZryjUcD5N8aBhCSIMbKskazLCF3G8AoLEmIwbELC
hhACdkx4MQ4hW9t9RrZlAtnd5J1VYnSZM+f0Oae7n6f79KQXI/eMcjKZ+e5fa2tyy6kCqNf0L7Rw
KlEM69fmynMr9toa/e7cPVCn1a/0BLQ0NDRAZrNyDXYuleJGbAkc3T2gL7FOsHFjgx2bb7WurUl+
PntNW4f0U/1mLhKLQPxZ4UwqF11XVWysP5v9mr7MXYCFe5kHRjm7AelLKd28VV2d/RrUTWqgafqC
2eTLioC1NYD/79ljjluKfAJGNrY0ez12SjdAv5lMGlchspB5gKMUHqQKWjYznTwLqVn1GqR/1rWU
kdwAfXlrKKAX9RTNLM4satppnGBCS+W0+6AWsENtPXqPXU8Zxjfx3/RS9b1aHAeJRjM/48/Ri5DN
4tfFj4vf6aXsRvT+9pLW1owrymTH3r3Hjx+3SxM+LsDbPZJ9Qn7hEl2QFem4aBd55SXXApyXE32v
vDXAezi8GHjJJf6EoLxwyZRiXAqGxJfcJPLHPeNcYPIV/Y35ueD4KwX5QBJ5R+Mrbg2OS8rW/GgX
s8vxsFFOGfMfoS7Ev4reTeUgvrk4g/rFLt3ILqdy6ipoa/pdfQnXNQqoQSVI/y2WzS6TMlc28SWv
f37Fa2ts2lfAvQ6nH79JylZQUQbtUayciZFi6c8WH6nTkNAiC9kbYNoJxMPZ08YN9dv5JxeeZ+fj
K/NP7fZdKgmkKTQJbIh3x28v/GaUUZ3M+zPT+jJNdLsXoG5Mq6xeEtSkJpxwaeExxL/eUji8fHrm
9PRf/u9D6uhk8VxCTSb18uwddSZ729RWXLJ/AeNqfDMzDS04PtkeM4bk2cSjFBo5+y16V4tQ69Mn
qaPT/wCJTrHJ/eHLBUY4vpE9Zy7yMbqhtsb2D33V1rjM3hvhGI44PC75QiKMSArnh3c4uYP+8Uuy
F5xeQREkEeocHm+9ZVI4mBTOE4qMtg0H0FYV6AoFFV4OQl0jG3lrcdLF/EW9FL3LbmQKWXnp52IX
0RUtwNxmNox+0Cij9hVvZR+92FCbz5Oqz95SVxOrjsxlwP3OoiuldpbNsIlmaFnvzdR74ZK6irPR
z88/Tt4Ct3F19lbRcMMIL/pCwIleeNuPzkwSfXBIknlO3Npby6RqIakyp4p5vZReg4ye+BHSi7mn
4AxMCjIP0hgo4zx0ikoQ4I39gsj534D/yTZeeNV56mFYkTmF903BfkEOKhbaSivNp7iqG9lph4XD
tNEw+Xx8DfIZ7RvUdAdE15Nn0SPH4nqpGM6uubqlwCinuPEtgBvrdrh7+CACqnuIU4LHLBNsHwlm
ZLWwtszewDUoCwHO7x6U+Snrhm1nzmEEVeUw7+NRjwc5WQFHBwzzHplH5UFF6vRzgZBCCuHQ71rn
pxobmCy4D0sJLfMQNaJwXS8VzsDcSmYN6oY4QRyVjsOwcALcI9wEDz3Iceq3TfEVyo1KfKizrxOc
Ijo8BfsI8CLTY48XJvipjtax5tbG9jGx0TPqa20dO2Hd9Ew00IoIhDcAQfwpWqt+mdBcOw+uPu6E
EAgFYHhSknHZK+7auo1vNGEhejc2rf6ErGLuCeKyDXKX5sqFz2Jx/MJ8SvGrl6yrq0fmfJI4JHgJ
Q2zQPS5LouDx80xdBnlZtFBu5uwhcj2+AZmZ6C9QNJCcb4D2BQYiLlLkfv59Xsb99grojfdzosIF
p6CP84wLopXr2by1vQkoXsF4BvneJfyMwQ3tLdrVlMhDlySGgvibhXK07JaDBnezwS0ckzlvJJxz
ZcSiNtdbIVGQZGizcMQ2U3v/a/YORB6g93YRUB0f5WV5yt0vKbzbhGF3BYYtlIQ5bkicykWgoOml
/E/gOoIuJiTz7pGpyXFJEu0oi/0Y2NBQ/BjTAN39Eqvq7rGhQ4IOEPcH22wtTftGbZIkTdkk+X3J
OvFNAIivZNAJFHD/iuDqko773X2cKHDWLZvDdPb6OYjGcPsin6DD13+Adw/DYDe43pNC7h5JVNyH
ROm4+y3OM+F+97B7sNtCeUzvHF1Ppxfu6SViU9eThquH9whB4X0kUh5r1chhuuN8DMP+JcicLJxB
HuDqxtiZE3zIJj0TgdC438LxTbeazGAgG88TFypcbkar4gQ/Im4g5OcUtOhmCwUw/adhpBLGfzIG
hA4svkIaiSxt/nH0AbwO8U/xR+tE2HKdjBvOPUFu6OrjPeMVJsjLbgeLF2fvZDXdwAA9lVNnQH8e
+3R70ZKG+ozi8gSG7HMr2qkXr5rZpiXY1W1tDfaW/KK4asfmRIFBW00mMNhKP529HpumgMzA8Br0
j4wb0NSDsJfdVJ9BIVFIYGSlLxUuU64olYgt4QLpd43btTWUZ7NunUx3H43GS3PlzAXcrPnHND6x
Z5ZFMww06dfZJhZW5p68lEFIAQFBQgwivxX4oELv0uQ4Mk43kW4kvQpPaxNkK46u8ZDzvY7GhoYG
W1tDa7OF0Z7DRBac0TUtnC7SvCDxdy2ceAS9I/aBIXv/wIhrqHfwsPO9YXuX83Cv84jTvn3FQvsw
cQYjvlu0zz8Uz0PxKUS/dTUjm3Bh1MfLktwBXZyi+HkYQ2PtCSHmu4geH/sd3gzv7QdEGmhoasWX
rbW1+s3R7mi0bh4m4PQ5D3RCX2c/HHYecPb3DCNR765HDOwc7B7osy5RYKJO9sf5x2hP6mZmE5qg
7q2QzAWDgodinwlo6oAeQZSghx9jGlj/f4yad4XPRxA7kIjC2yJ+kIOc37qpmQDWPeXxE+9F+OZ8
SINJiP2SJxS0bmATuYYVToYRmZ9gn/b7eV6BiofrgAGZ0lyDAuUSgkymXgrHJv3cVLVqVswcmhsa
9tlGm9sbbY1eT5OtYazVY534JvCNDAzC8MGBkWHo7TV1sbN7pPdI73DvQL91Y5uYx9ZC5IhgcH7o
lgXPBC0eN0nhKjKlhkboDI7jwm3lC/+MRtKUnH2DvUNOczwOCc37fPXawyHGPo8MdrfYmvqHWmy9
LfsOWTf3lsrcvfwk2Zno4SkvSqkHCuKcXh9LYnWPc1IQdnIP8CdfzLv0iugXfTIdH1iIIE0mPAYV
bhQ9cYCjTCvbxWpVz57WHtGJUjQK6b8BO0uaW0nlDGQI32vzL2ZV5/4juUmHW5qmJyB9Cf/RvtDC
eG/q2/Rto6yugnoym9YWoveRPGQ/TNAB1MLD4sOEpq7u9LJYjOXonlz+Kl0Ao5w5gwQGcfymXtLu
M2GIqui/IkPR78VLkbMW521NrE3lsutQTObLkJgx8TYJdcM8pVNhxDSGLi7Ij3J+v3XZp6ZKHDdT
DEfOI/OrOyLwisgFWC5sEsMANM1ORAkfSyBZKIeJj4mfIYEoxUhoXZfggy5ZUsZJkeotzHSb8JhM
Ins9MEJ74OPwQ33FhCzN/jVX0mPrGM4/08KQ/zS7EXmA+6FOUy5qOrqeNOr6JFGalPxT6ByDhNFH
UMBtt2ihbI6Kbmxpp7Y+e4tMmvamopnQJ/lCfvajlTtUCdPORu9RCjFMxLtwBplgLB7fwHAt5EVP
Skl7YYJH3JcpFXYM3LAY1u8Wr4LbOsFMKCsuGuX4SrVo6WWMBSiD+3vf7RrkOdnvPsjJo5LsNoV2
dyruHu64eMy139bYBnGMmY5ZuJwmCKUSBa0Yjp1kH1KzgMF3uHAZMhtGFhwvi162yU6dXM/4TnBc
mETk5lmUjDA2iTTCSrkrCbeNQoTirDKGiOuut/iJKdRDOow6OOXlaXgqn0hGCBOW9SV1E9063RK/
uXCvrke2g3lHPVp7dA3jRjrTo6wHpNeid1lCiw22q9/aGi9vR/TSby3co+aVlog3xqn49wyK9GVd
i3zCetK1GCVCsaF6WS8BerPIJ/pClKDH0gi12QQWCkCLv4Jrv8wzawhYuSX7duJGyr0OdVdlUqBu
SJgMcCfo151sioUOq72SJGc5h0panBHMoIVL0GLCR+oi5G+iJV0mQxECGAUwCoSX3GAe1pAfqq0J
YgzawYiRDf+aGs33hva2fTbHPkeThXKaUJMuRj4pnIktRR7idrk6Rc5DxxjSiWM7WFdbk7udi1Yz
sV32kbkMsatGDvf4OiVttMj5qpaUujEWQStkHsKioZ00yto9KkHCeyF7HfndTtP4p+lfjDLazOJD
/Q7axylIb5LNzGhaZppyoxeQIeq3LOViLSbGdcoeTgwF3ANj6JB5LnBckifMlEwf50Mu5h4YDXow
XraaDrRUgC5JvpgOuXGPto766oY5jyyMCRgx7D5shz8bIFBE2jk6FQy+KjaiuBSVdXCo96itr3+g
0fZvzkONtv53HSPWrYCJqHXmpOuj6+liYpXK5aCYn/0U9W02kV129QgYZUhuh/uwJHtp13r4oCKH
trLVu+fAT3VA62D/oK2nbfCA7eDRfX22waP9g9Ssqvs6s09imujL02vp27BdNWfVXE0cPsqHgrjI
UpAXvLibzhOTnBhkBTJUiSDwsszt7Q1MynyQfrUupdFiwqt5Ih6EgTHoE3zjCoNAZgaVeLKpZ4DW
bpg5MnCMNrTbHM2eVlv7vvZmm6dx3xgtvHVStlXcWLykGciQ02vomAo5qOuUA1PQhzywAzoFGToV
hfNM1LNFZBJbJY+JgCxoQFYchP0C0iLRV1msYeeBTuvGbq8c32CM/BgZR1xNzpPpJD83ssWwdW6q
1YQ8KrUJBkLyGPgxWPXhn19CLa62v1RC+wLpJPGBVMmsr9q5mLud/okhyOLZSkO7vZgv5u32+Uvz
l3TWXtM+iq/rpV1VWSUW8Gvz+gKrTs1HtHP6AqiP5h9XBmKc7sVsAuUKgFLbhVt492Jm7iLjacjO
MOj/kioErVqtrUO27NpcmcZj2exzMJdAtNTCiR+rFyz9jTpD2Y41TdVLmQfw0pzI1Ur5biV7UZW0
YNVqBKr0N/uMGoD+PLtp3EBAVadfsiymWAv31OexnNktrcrs6dw5PWEp9Laa0Dt3EylTMpkhOqKF
o79Uci9VK8KWAtl6JoofT0P8h8zD2TuQzUajsTKoq+nF6OLvZhV5EJvGlUksaTPIzTNnYufU6ewG
6wKMKykdCQaVHkeNyopYN0sT0Zt6gOp3YRJ9UvXkmkgsVMcmr7mjEL2fXqOkWPVkMvr831MGikxt
VHX3xfRaLJtZqygEpBbVAjIq+pb4XP04+wTUi5qauML0Qv/I6pLEVhO9O0XlA6jrC/kVwc+hKxz0
1FfOBWSfYF1xYKuJp5mzxlP17OLMTr0ijX1o6AAEpTHl1UlVChfekWS/lzKwByUFutCdeV8kW9V9
Ve9k/qsYkX+qhEbHpk6nctD0Jqvph4Qajb5m3axN2EY9uKIvoXeZWymcgWbEQ1Z1IYjMTffQGU8z
1DNQooRwJR9c12QlnW01sXpgEsklW7z9VPo+KQmiwtaxW/LyZqY4CHvALCIH1GMj+Zt+E73VRdhj
nWwmbndxfm9I/qcgHOAUHnp7KQ8v08Ih/eka5zj/dhJ9++Tmdzw6fpuVkWG3pWIYqeSercSThdK3
b6dwoHAfDCNdrKOMjCJNCpxpbE5kky8we4uEaTPpQIEdxxe+08LgqLIM/bl+K6HNrVRCQ3RSsz+f
/5XlTBaexJYyl7ObYN6mTlfdFjm/N3Nmb+TB3uTnYHyuXsbgEG/NPpr9vnJugI77ut3SQva2SnJ2
Xi/HltBJzz3Q1o0fTLfiBkpPc973zaInchl9AoYPL3iLP390s6scWZAFzrppmkA8IAs+Kphm51E7
3rpag6wOf9sqp5JSgJuAYQ4HZIdiqNbjMCzh12FFkqfgjw7GUI9iW9GjPTM7e8euq8kE5aRohHog
E7YzT/MZ+stSvJTdeO21/+02sb1wOnvad9fVgv2N7sMD/c7unjdY5EMy0ANUZ2InTa2lh1oI2w2E
Zm2eqA5SrMJn2jnjBh0+mVeRxxQwnkFiGInOrZB1/KaepId7sMeqp640rdIFxDeKKkSXQKU8ZDST
yiFDYJ2y52Hs1sWtbSbKtzc2Yqy1n+ruX4chPugJ8ZVD7i14sU4CE+nzkVQKFs9RJWy6uJ0zoGMS
qgYxi2AFbktbYGeX/kLCpIuTpX8PWehMTTgf4qbGOJNtvD0qDBNx0e9qMx2VJFwe3BTqaMab5EOR
7ZyNLr5JD/hYd9bRZoL5O8IYf5hskURjxfqAgKeXEwt21sw6zGszEbtwwfhSv4as+TmxnEMSL8AI
J0xIIWh2w1vcJCfyQX77dIzSr39h3xnboyH2wI7DSF/JfWPlPE1szzzLrmG8qs2rK9EYEdNAEDrl
AOfjvZQmgjfg7cHilfy0nfmZ4lPj2muv/VW4oemO8FyAKo2te+ajQhfOaOF82UFPyW5Vf5hfXKYd
H/uDyTBK5vTzHoWV4OO6KER1PPY6Z2flWYJ6C3NQ+0xiwJJPxafFMJM7ocV+awJXpyDT+MB+OyL5
Qxj1NVn4AI2jwlGobA/VpXheCyMOuPo4WaBjRd4v8HKlLPxY1dJaJY6J4Jno7IdImC48N4zMBXAd
8CNs2wfG7N30WKxg1oYzgf4fJDLB6ihCVSpRzEASg2t6eAyNy3W0AxkFz/uRXPi9ApVdwp+rMtqF
envfET7gZO87dIZg3bRMBFx8inHfEs6l8Nn843Sx8Bk9/5DXS5FzkPu4cDmVeMn580Felv6bt2t/
auPK0r9Txf9w41RlMEPLegGGqq0tIQlBDIhIsvGsykU1ogENQu2SUDLMf0McOw/HIFkSar2Q2uiB
MzZknIfH8SSZYYIdxzFO1rGNEzu159zbLYTt3ezW1oUqHmqkvqfv47zud74Lod9e+QrDHtFqOUQe
nZ5nAFRekjMDV7+WOUty99CKpbdZ0Fo6o74P4omRkDQ33hcSJ6VxjFvHbeFpKYR1YmwbjZ9kzMKx
PfG1WsHvA7931mAPzi+cYl3HfbIe1XZwM4u1QvKvpH45VyD+0RBEz+HYnGE0GEbQBcfNzKPM9qjn
imswk8ofwNCUfqWl25mN9NlSWUsXvgwd8DruT0jR8bFgaHJ8TIrOj3sgvJfHHcFoWFrgKHMPsye1
W+o5rZLAWn2y8hNia/yjYvjPoP/0ioLouHXcJ09EYrPjVhPH8kJmH7Ln1UfxJMaP4KVeTCjEr1Xz
GQYkiGkMYzPISOCKHYBe7jFrIXpqk6yfgbWGgHVQiFj4XL1q/h9trt8nhxcMA+Jbs7+LGkYjssE7
K4KKMOtKnJ/QzJjAzNsm1YekvIE1KvC33yOLk2ReRhhlUDx1EDitHqu261TMVa8ry5ir/iq+CD/S
26nNYs5v8/qcnsGTBgR4G4ZtjhGn18uxY5jyr/+tXif1f6HKPH0aRkiORTi22aX5PLhncq94hfSD
rwOWhDjEcIDWHJ5q0/O8dk9QDwo6OAcFPd2aWJUvkneziF7yOwNyWJ4Dr3BM5NkfTFVXSqyCGq3u
ZiZN/HYZ/T9MJo4GQ/L8qbZhr9DvZe4gSwtynKVMeytfgQnbqD0ub5LKeVw7H2ZSWNMDzvJpORQE
0w/uCbGHYhMcCwSNTCsjPcieo+z3SAgoZS5y9ED7xmQ0aTidYgG6pfoY3cH30z+ATUO8zumoHI4a
7JhBBffUOx+bDMo8e4fp45MCiS+mt/0nBVcMxoRng0yX1n5W4sU1iBRon/tH5dAChMtBkb4+4PFg
KnU4SpR09X3QqBTyr2XO/XB5KBiejbKre5iIUfDIeHaTDo2snC9foZ509Sp416YeaydMk9mFfkRE
gHs8jld4ysG0bWJrdR10SzWZWQYb7Rq0jfgMxwaHhpwer8HMs3nNE76p/khKT9LbHFs6+gJmcQoh
ixxb1JRkVUUVUPkh+wijJF6tafQO8c+oQ+13OcEz+IP31AG4LCaNeqF0dnUnsVWNZ+5aiN85J0Wm
pXBggXhkeY5nYsKkUS2sPKDhQ/1+XaVRHrpLxD8kRufJgBiawo0TDPJAC0V5CmPR0iQUoUk5HlIP
YfgTW5T/IZMFM/l7sFO4g8VRCqbyEtdXHiLyjJj/m3SCle+8YDoO3MVogzHHIYFHbWYbHIhkwq9X
ifpOsWJQEsqSumOg7FGvcpSKaTw6J4aCUxLpJX2hmES8M8Gp+WYonEtC5PyfmrYK7Q7CKARMPSaT
YLaYrBbBZLZYOQrbrUHlxMkpWZ5HMPxkMDZH3FNTEYxNPCJ1iUc97lGnh3icozb7MTJ8fMg3OGQb
cf3/dgX37+BzfEammeN5XDJgA2GyuiBeZbv1Zj0Hi5vMHGXo0QEEYXIMKXpYq8PB2YgcnOTYsEbU
MBwMRGSKGvFFsCpxD8WuC6L/v6HPKZkdbjCas7vl7Q7cNcBXrxKOwpoadEa6JwuLQfNlCfNlqbz9
7pMcpWD6PnEr+wj0feISWFgaGLW5gqEJCcbOJcuTcxAYHf7fVzWyPSYpFEPf74g9shBFNjncDXtL
jEg8YaYmjRpCWUpv1y9SoAXECv8JpgMzJ2AtGNLwJQ/RNuS0Ofrdbh/x+myOwePDxN3f73HbHMRj
sw/C6jcZjAyH47H5+mwujo/AzI1Dkk6DVhcbyFTzb9cim3t6Onu6uyxdPUctHAVsFCJ9S7f252i3
DMvym8QlhTXQ0J5wh1Z3Lq2qjxhVaHkTHPT8s8QtEr9KNFrU5D/N5N+IHzre7Rkmpw5xlLyruaS+
tFtcKz/VdOLbX5Pyu+UvYIowGC5pLqzAemPs3+NGb6fgMhr/ILxh7nMZOQrKLFWlUl9TlkEYVWmz
y+GpUDAwT/5DDsNiZJrs+ESQriuOkjB7Un5WKNSTpZ0Dd3s0CobqD8pK+Wkh+RLn6yVqqfmVPnY+
k2Dr6ztqEcxHLWYrjioq+Mzdcp44eil6tpBU36EAp0KyskjxHTpHKa+H0yge9ldCtus7Ju10jO2O
E3uqcz+ApTE/GRiFYVfgeWihNauCMLBrlNprdb20SAvelNv6VXM8Wd5In2Wgl/LT3AbJZfO3W1uw
2pogdQxNkMV/JtkbFxHcQt+nfk1Owpfh5Emzck7rp+JH9A+S/gvf4guTRh3RhwWXrlgY1A0rHED4
kxu51FxSZE4MLzRV0fN2uRipROFa6X7uOyUdrzaPoFeOhfoioL41eosDkYfawFH5LWjTexqn1GhE
Jn2SGJjBre2QtEBrgA+wg6hFy/w1cwbZWhczGxC9Va/TkJLmidqJxz0ELraDuGwej9urXeUoELVg
iHykIml1Du1s1Nr3nBhHMCxiSppiouekSYTzPad8fPJCCEtttNhhP5CQo15kxA17RCYn5AXKodJL
nKHgPK0gDUjPZeC0IUd6sDeDUWqk9z2P3cECMnunYLQPeQVj/5BPMBo9NvhhNHF8FmrtsldolJ/e
VhKZZTIcIY5IECZrhAo9Is4F5GZxvVIEWQ4YDYhtyG4RnNaRMcFs/wNo+LEhJ0dpqUVUnlTjypM9
sPqwHJ5dwJ/TL4OeR7lCQU2Mh6H8ibqb2STm35NxdaWQKNdJ9sv4l+OkTf38cP5+IVd+Wv6CHMGK
BqTLg78GDG8YEDe035Vk1YN/hi9h/w+OdJRGfQKAr2MhwxAwkMHBQSLABA6GdNCaFJ2XtbgoCtKD
70NjOM4OCON6GJYigRkRbO4oKHNYWMwZp8yu5iM+MQTBG1c3jLE6eGJhzLAMgPqmlX4nxNAM/C2S
dufJUdsI8v+0a4t8IAajTAYwQaR12YtBT1vmDtyN+5YB44HIfl9XiekI67hJMTwR5NgiNTjI7I3f
pFConEkoTKW7wNTNS4EZjo1T45LbUL5a+UXbi2BNk9ngZBi+OTZNjYJtHizSfDDKmJKRQV3j2RYw
noR5jMaB/vN1ORZB+BCzdQj44CgbVfLPZ7K12TokTYtw7SDKHkyM/ACUNKxnFizoVbFdE5M9Qo/Y
2SVMBI52CtbOTo46m9EeJL9X34FQFKKahiVhWVN3v4+MuT1DDrpQudb7mBgXgjsYIr6FgKxXS8k8
FwmjNTgp2GESOJHpKnCADjKjD0ifBXPzzcqDdJo4pCgWO2HlDR54ALNwkuXWYZ3YQlhC8X/J/dLx
Oy2FQhNyLDx55ECeiKrYyk9kvYIEOhReCIpgNjg3IcOyPxZDpEeMIIaQ9XKEFq0fyHpj3AC5e5m3
X1u/wHKLygN09To0y4NeE+Uds01OCu5wg3eao0hURV9aTiDbi7Kr5DMqsXLMSrIa/fz9RFZ9ROK7
yr3yU56tMXd6X3kbOFO9pHgunS59r52/sNkcpiayyXytrlRLd9t1f+rFaf180R3c0TsDi+YtRrw/
xzPcYfX6OInIa0SbRrrG5Ngq1dHFqrpSfwJTpElHH1D2i5XsZ5co8E99Fx4azPb4MOhopKD9oxTQ
9ti8gxxloKo6eVc5o6h0/3NExgzLJM+AhlWZZxKpXVK9rqzQCL1wAZyZMKot3wytgoWQWzMaDvFN
CBM4HofA6sEbVTwU4NtLao/ji7U4ZScoFmkm4YVl02Zr1BpqMGAsvpIj0/L8vAQKOIrJg6YcM5FQ
JfcSY4/RJFiMXV1d3V2CxWLuNpqMQo/Z3M3xGfc7zRaEE2kVedjHEOKIwf2l2Nwkoeq58kX+297y
cma5Xl9dJ6VHbXY5GhUDs3iIgzMWkU9jkD0mRqIaetFxghaVUjgAkgagltPPnCldhVFSP9cP+Gli
w+aYqmQl3oxcLvcdJru0zXDiiwQnJNyObUfKomB4Wo/a2P85ikRNQyaLWNiGMvM4hwbtXiJgRBCR
ArEIqvNDbs+ga3DkkMDK59y+AZ/TztFoscLuSoWULlHuwtyPesUuuIgSQbdAnFh4sVB3/4rTskK9
xAxfwt4PY2cnx/wVK+suFGoXM8vEOo74C7atKyG/dSRKBk+QdgYnaGfdiRCJvgWwouS3DwGjmA5W
5jEO48O4KHg9CisKL15Wd8aZd/bKK6StvkkrV2uVWgHWGvoKa1vFNeVeb7Ga/ADP1sJ/7D2GtqMd
1bAqeEjPwvOZSMrwu78SbB8BDSMV0PSg1dTdbek2CWZjl/Vot1mwdJo47r2x+nF4iDmJkWxjhRrx
Iw4kiDiQU0x4g83wUomtncZuoRuUZ4/VLPR0WcGG9widncYejhKbn/ew+0LYya+RsRnMBWugjyGn
3edxjwzaic3j8zZtb77wDIdIGzNAFrPV0tUlWLuNZjMYILPxqOkw4bhBy0rJ18/gxn15E5R+9Wrb
gBydxyTgGJYvYIEgriCPOC3RXE6UDM1PaozF3KSilnG1VkJq/e/a3Md9Q4MnnIdhTdPVqCtvlg3c
V3mvr/qX66neQJdJspoE0TJl7eoUrF3d1gC8Ckjdpilqy7AbdNO1fi9/G09QAJuFdfEcn5Za38IF
5ZPkR8Qbm5uTw5KOnPENvNE0bywORjGo8wqS1N3yTY6CUXuqrKjnIHAv6JjjYdvrTq8PU9a+AScZ
cXvgl2eENBKiLN4d6Xe7PLZhp5f2a+Mepd1cntQ/4rnHywqwh6RpWfP2Gigsem1Y4upIs+rr2hKl
d8TquOYYprSrnsN+i4hTU6CEXUFMcHMEC2ol0vT00R0wKPkn0BNep2fQfdxLvLZhbW3bIzKyOR5x
GdwGBx0vU3mj8gEppmprhJ7hy3eesUrn/K+57/Abz8QUJ2Lj9Gcjh0x3UCBszn9nKH2jLKmLhvit
UhoXZgdXqiYTK2Km+37o++47RGNEnJAZZGzouN3mRS3PURBqdOjOKMKRyIngpCSTUXlWi8mc4QD4
ahzbp6YC6YTXnzGy61yBslwPBKdncONjj4hdY7+GfrFMcjyditUsq+fAcCkr5W260EgbeG4SGRb/
KIanxyFynp957rSvw9QFZGVXeJ8O/Nj6BZ7rkFUh15aUpfoa1dxXaAdhWHIaptIoDueLffeCu9aI
cRvnCK/WsueRBIpUFovV9QqFi9Q36WG6GjDklVc4xo2sRrl4WWP0bdPzWwhCntOYfV+2O9sXC4Wm
IvI0R8moEcCTj8A5o5GpdpZhm28G+Z6PQQw4Kc9h+rkfk2s6vpseXUgChzXAboMuB/oVuvdVMinH
JkKSEAgFwd2TGWnYoSl50hCRpg+RKXCbDFwnErUuI302wmJcBtygF4bQ/aEvf8PVj7KQ7VWNWxl8
/CZu5a6uHo54cFY2XTmf+wnLHUjpcl3FqgLEia7WcmermD9ldLsNxATGYuDcYxnpC3Gb3y5OSCER
d2anBFrs2kj+aBQFvB6E1VIrtdIjtKzWJlSCFJgBMxHBEw6tRKND0RDP6jv1eOV8vc5zgrCS6ouX
s7fLdQKqZiOT3ZdFpRtNbpfN4Qab5jvuGHQTw+CInaNA1GphcRRZe69eX/2BFBOkmEu9Xyn5GYug
TnZBWfK9YRkNGscSF1YtnfwAa9c0IJKV+EfEaAAsvAYqsp7S0gRajrCXuGz2bsHj7Dsq+I6f7BIc
NrtZ6D5q4Qj6ZaXUGhuqUlUfVZZ03FT14eqOn20fM8ZhWM6a5D4sbuaJ92Y11dTSlnYLv5avkMIK
TLXcj9mPidXffKmaX9tC79MPk/8UT4moEao+BNcEUcSCToBhoGOoGfd0PXELFqCSJ4mt1I2MWrpE
yjfrcfXr0iLlgVWvGUjpw1IWHUq8WEiQxHVS3khsxRfhPjQgTP60ei21yzhUyfCoJbNBkt+Xi+l1
nbgdGTGQoQzfHH8veyXzCeMi45jyZHXdDX7uwUHdBAskez7/rXqO/qnvZ+v77vauvm6hb+z1Y4Ln
mHVYGBs+4aTzvV0PLNtJM+23Wb+pBmKFfgF7f5umL6DR+mZ6G4Gu7CKEzGApW1uUz8o/E4d5VJwP
zIybjJ19BulPEkW3Uupd+hHUhhT5ilBWPHmIIFMTHheBqODWFjslFmn6nC5RXG8OOh9koLSI+v1o
+xQke42svPuyuzRao2yw8HoN5gKD7/Kcpywy/Li8UVt6jf1qqq0eFZHtE6NVBDzNk0ZpNUiEXB36
mYnxpk/RUwBSf4cnbvAgJ64rFyldMp5gh0/3KUMlw2QupfMP0nfKOYQbl6+olCP4xsW/M5pI6O51
pfwUuqyJQ8+An1OW4H/snIL7MKU3SjuwhLLnoFFsC3oPfiX2Ue8ZDMqOskPoRhIOVONy6naxCusD
BYHP5Z8VcnhyJchR2qVjldsAJ5K+Cc/xxI/D/wqJ6trzYuHZfOk7HST5oLyNv9Wvi5fjix1k/b0O
Et+Nn+kg6VI2XtrtQEHgZnhPeo7m2tvqCj3AqvR97V4pUbiQvhP/maZT8Wzru+XtDvpeUv6iWFXw
GM/4VZBUUdJ3dDLN6s36mpJK36G5yNrypcX0ndYW2uu0uAI0wV16HGfxQ+iovdM36XtgUDoIG0xY
NpWz+MYOonVxfDeB5zlc2s0/YrzcV6H50mb5KVGf1T9rbTEhS24cj2tJ3VAfJbZy5fQduEsHWbmF
h3+xg7/yzxJbVMy99+j3zz9I3c3eIvFFNQPNpO6iaoQOTP2LLkeN3xn+RoY0XJOtLVbWXCWNpb+0
o9aX47coch/5ErDjCzehsxL18jK+SGytn6G/WYPqj/Eq9EHhb6urew0WHhU/avRha4s22LmPlXvr
jwnMP1iFiZ31M4mt4mUSvwAfyF3DG6IYZxJK093ptUIh/u2+DqGDXF/SvOPMsrLEcT1TZ7Z586tQ
gEgUYjcbO50Oj8eFcI7qXTQmT+tP6dzL3kjdgFfVh9Dpiet0nGmSBUtHsaduFNcgOF3dSSaxM/6d
gh2xICGzgQuksT4qySQs2new+xTQplcJzHjkeadvqJPyL5TMOvc5vQm0r3Vc+mz1fTpzcJATX5L6
49XrdExhfOp4eGgchvpTqiPTdcodDsr4U+6HPJgZEQae7oVg9bVaAfwdTKOVr6SuIwEDHujhwywv
eju0zBD8nVOs9qS1JX7r0i8E2dnzz9JpMAA5Jf8Mn6r4TxK/DDaa8r3/g9oa9fPiR8W1UvkVWDsN
xvPss8xTsAP1fxB1F3Qc2vz4X/K3Qf8ktgo/44fZ82u97xMjyOPvEcPTEg4Z63I8Qk83J9dwAVPl
C81Q6VpbskvqObJ+IbFFxaGqgt0VRid1o1zcu1PhM3hD9TrCc6H3karchmUEZEwMzSIneym9A29o
bckpq7W9BzIoK5V3k/kO5Gz/Jv8QWkhevniTigWLV7u1+nXqLq6rfOoyFUNvhfZMa4t+K3QmDXTT
FjTmM9Dayg/p2/SgJlBuK+9m0dyCNbpFVUf+9spjuFXhWnmZWu7UeeyGYu1mfRMcgdugbZlCQ+9r
9b52DtTqzp7gujJtbTlzgVDr4TWMGWwGnwF6M/kBGHdY3Di74QGSOyBNb/0srKUcPGnqK9aJ/1Xb
9f+0cSXx3yPlf3j8RnqY2usv2KhXiS8hQRcIR4jSHooil7jBV7AjG1rR/wappCW5gB177V1/23XW
9tIrgSZNCJALaXulaUpASbkAJYl0M/N2bVNSnU7qEsV47eW92ffezHxm3rwZlAzpuDjFxLXYc+k5
y/6sTcFTA4o5NBh8Xqgv+RoITGPmMjQJpgikRgEr+djoKIg47XYjcwgkELU9sOTumAoh+3M5o2FM
VZ8bl6L8UF0VFZPZ7M1Or/0304GySde029Q/paX/BfrUviru5TVy6pBEEJwgK4vLrIFuS6QZngn6
d3U0jLEw5tRYowemsja0XacGSDAoT6UZBADmG50nlgY1tYjqVJkENs/dkWZKk6SUk/9CubYHzSW5
3m2q6ebCVzSF/HNY4MlpDPc1vob+DDUDDZ4LjAyFRwPmkGtLc6X0Qo2UYgpEEFb++g9c5PboofJ6
EeFF5Zfsa3Y5EImOB8eiKNA+hyWnLcVX4JfyS3FXnS/sgwbZYw6wuv0hdio4GpigPiuzmRg0QOcf
FWQUKVsDGtXHgZGRpMK3KIInzRfsZl2ilYYrdB/h/i0tkU4wdT52iz6Ojg8NBaIfjo+Q0ITpnpee
mGQePRJFoUIPhwyzQM9IbaufA9vdJUVIE6RsSZvUAqyl5eJOcsXkkAND20zCbRCTYpQfwAIqPD7P
zgVDFALme4+dDo1MNLG+QGgMT9UD+Ef86GeXMB//5XAkFLayFDZPFKRO5zPpb5ik5/RBoGxsOBK+
HMUCw+i8OW9IZ5BvxR3lKjACmAxPSFzQyMjXctdx/c0XHqFQpMnDueJTFN9iTeqCvswKuoQG5dxz
eZ5gJ0zcDXUVMzeT4Jln2acmAAIMt19GIQwQrriEIScLWMR0FQYe5wOHEC0EbJE4QP0uI4OIWAAu
3CnuAdQybFloITmdS1AFdWgARQu9IxIBqO3hfS9Rv0oGt+W2AC5bqR+5I0Ut/yA/NBwBg23jY+EP
/MMhw/o/b6Q96D070N/d2TbQRkZcCkCJeSMMA2ImrJExqa6zzCtpihWvFFNgRqHYurnLC2C8yn2T
vsnLvqyBHLvL6mTK0SMgVWKbuW9g9tKgXeEdoIQFGs34Z6RbEvcrM8pOeRpVBJjc0Ex2UpqBJSCm
EAJC28RJuBroDcrovBbfgkmMrwEO5AVYbhHP6z9hzZof9Z8OibVDjNHRdxarcNW4wWm39wx/Cssr
u/22tCY9AxpaGZak7mln/W099IWlHOLk+xMUzNHKFE26oV/NZ1AJX1HusUasaAWf93A/OSDG0yMT
o5fHo8fMuuzWUEWOpbld1BWDJwPB6Bj3dgGTYrFfMERERcthnC4afYmr2Qcmw1JpFJwGuH5JZkO9
qCp8W87qMVBT6PgBwQhcChyNbhRQsa8xCEyTF/D8uQo4656hONS70I4MoA+uTIDyFVqmr7AGy95c
hat9YF7MpokHOxKzUgpuNkgCbaHGXjHWZJoFN9R18gAAh8K6+WlOJmvMoDt+n8wYKVVcIjkMa5l/
iNy8UFxSdSyNTCZc3WKzcIG4eZwDLM6Z0rXBttFABODteSuXJDnLdB23jB6mMzldGLwc/PRTPxsK
h0IBKgzHLMyYJfCMWfpi4TtK9yk/AdxgYW88xm2zHMtNMdYRDn8UxEw54ctv2pTqCVzyd4VHRias
JMjHJxwMGzyM+7/ONfC4jzPosnO7nV6b2+F02lwur93m8PocHuvo5Om40o8TVyv58o+u/4NOl2C3
tQgeu93mdHTg/+MtFpLJz6bn7igqVTJ6Q7z4G+m19HSPYGT0EtdT2+Wp1HZjZ8Q/ND7iZwI/H4Yp
vc74Q0Nj4/7IxLHDw2gZWTxTC4yQTNHtgLkkY8OQ9g7N5Ez4EY/wBYMli87GXW3XQrJ49pXSr1gQ
2tnKKmqhkpbB4mV/Hcf4LviI59pviwRCfh5c1FlN0HA4JQsbONN+0tbS0XHC1tl3rs/WLpwasHld
R4+88w5FHwFcNOpWUv6Ed9+18NHc5og/4DHrGXVaXBenAJCxxu6hwCeA5FmnfyRwjB1MNVPLkWQZ
aTwxSzmdfM0Kz5IveNQ2M/fF2dnQRYAkVLQEEWUfHsX146GqN0QxVmOAHXZge/uBFytzDwlGerEu
x2/2EAP+KKox7J4CY8xaB/VE94bHAqy1dv1n+qldnxsOhJg/+lHgIkX6UA1HHkPITwxQ8za33e4W
XI7qb4/X6au10TcClARYCLpqYt1dbCI8TuUf/ayjv4MFIhFo+OI4JqtgwRCmbBppYn8fB/EwHBxj
wUsh0FEc58IjACohzLwuPoN5ymRjD9WXhNC5KWA4b9FTjc5n9EAtJm/GM8oPuKUBI4Sbr8oe7r1q
xWdIOyCxaquFR/kvES5NFncAQ2GsMWCoumKUxi4Cb6l0Tdk48CUY7kvFXcDtpd30bCUHxm4qUQAw
jxDyCdax+r4o0Y06ILryBtgaldlcBs33PGAr3jK6sCUJELm8B5ixSphBilrtCdtCv8eiuF4BBKvr
4jqFtxXxxMHN3Uzs6JG569AaVXRM6ckVMHCkMhgzWYBzQFA93fPm8ChPc3HudQJrYlqKsVKFLLt8
mSoCZjCftRZbJQqr1blik/DE2hLYPzvF5doA8a1AIAbNotgXonigSzCRtPiyYTYWlxL3OQF1t1Tu
wFsttS09wbzoqZgOD5MrY5XdO0zcNHepqlSkVgpbiavJReyZO3OMytLooQcwS7UMuV9I2cD1gnUw
X+r39EXq20Le9Fb3iTF2Q9IvpOXirIUpUgWeBK/0sLn8orlSUnaaMXNRB0ZUjYWN5CwHcxn9waTU
KOFZ8RIboG/MOJ3KrjIp77DG3jA7HQpQsE4UjyUFPg5EjhH6DIfCI8Gx4Wp2JTCfZMrfFV9j6n7s
YW4HGEvcAvPGWAMOn8ee3EALKIPSGy2XHe37JrrZ3EGaZ9Jzfaq2OuNy8QrtQdB+fTFV3IX3Z3u7
B95HY3sRjCYUKfgl7aeqd+Vr0K6kxe6a8WTM4SYnaH4eZvboER7NBhJJns/puEOEtcxvGxviuB9e
27DZv/GavDe4POHO4iMxlcO9ZGRL3gxttYtSRjIItm6t8FSA8oo6r6gY0ohpyJyMDSqiPFPRzzf2
B6LBi5jx6fjHwRH4pjcwCp9E7bWKgRbSRvBRzeiLTBGVF4yycHl42S5D7/Jd/Pe8gsvT7XK1u+1n
LCSHYGP5V5yg5AvmbixPpxeSi1hCpXkgPPoB6/cHESvU6qTwrH28rqLVoJbn7hO/KEsM9YEThiWd
xWocO0bIc2NnYGTMb2TnOYX+USM8qy4cotd93Gl7/72Tgu2Ez+u0+c69325rd/7tjHUBZAJP6afr
lRKH4EaARWNXd1cbR+BIHl+OwCyxGLIyZZgVddSbhtZE8VpeRulOm8UZdLIpe/AH+nIuAQycL8sz
uXihwDkLhcdibLOJ/UWaIac0bnRAe1s1Jw4oWBhK2uvJLGS+Rgd6jQaro1kEni4QswwXttOiYKz5
+og/oaPzfF0CCbtgb3F6bC7B6xY8NrvD4W1x2zxuu4U2p5EpEE+KACfIlLrQxjI/px+D2t9B0gDk
i8pTnxcRDEYMbOTL6mr6OypNTNLOCHJJroC6ltdUKVcGsFJLf2flAJNWPkA7Y9G3QzCSLW7B5nTZ
W1w2p89noWvByC9obJwfODQqUCZl3Aa3TDXzBIBpmVLroY6jbDHVkoiNmc10jIPoqokDf09/YEDS
udnsNqlQo5R04qpyl4BkXeX1x/J8jaN42+p8ahuRdgXLsueu407+gdrdU9AnOsBpl+Jg+dY6rEqE
oLOySmYdPq+1J8fSXx8ogY4QNnkAO/Ldsbq2rZtxnkEQ84h/WdxqbTRPK7YiCgqGQChHLtUlTkNb
uJoh6bDvhvO91+Nx2lw+j6fFAavW53K3eLw2h+8Py2VdRzxqYyS8qoB/Sw1Yvb4WweZzOAW33eYB
leTy2txwYeGI8gRPTwqPxPW6oxiO1nb/0EcTWLWk/jSB43cOvCKWOXm253TvCTwOdLx34Hj/QFt3
bw+8w7X/FiutyrfymfQsiClyFtWWWkODJM1dLyWk2fItAIyikriPd0hXmvnPWxY+O2r85IYcS/wj
r8U/Ew6d9KMF4nR6PYLHJ/hcHruFtKAWx+q5LHFdXQdhMNge8X8caO78xB8BgH/e8npVAmUl5JX6
KjO8JJthTPKaaJ3ByNgFqs92ge8RXjCLo1lIE2pIclPo6yBc3UhWppzGXwu6bmG/qNx6T57iiMrC
flCDVXZLi4yn1bGuJ0rTh9GeNLvSTOUGQA0z1tPCbh3UrXKLkgP+fqZfk99a2zEcvr2tvf4FmIN4
U/sna2hgsevpm0x7pInqA7hsoGrn6A/C/uQf8yX0Pu3HvpjbZfIOmYuwihcykvKU5Uv5DIZWYlv8
WCIegSU7tZyVV26sgY47c65tACiFduPLooheFtPKzD7O67kM3X3zV4rnktcMndpgwQAa44c6o7QK
ClqkJBQkbLXbZgy2Vb2iUqjs46npslbJQ89dwOfh8TEjbC7KWtsj4bHhQGQY40NOf2gU9awFh0ub
MCkLrL/vBLzylsi9gNHVMIAYsoibuKU/HTiEHLvfrGj6MhV+l1fhiubZgtGt//dfUEsBAhQAFAAC
AAgAklpCK0H7znl2NwAAZ7IAAAgAAAAAAAAAAQAgAAAAAAAAALDUwNMudHh0UEsFBgAAAAABAAEA
NgAAAJw3AAAAAFBLAQIWCwoAAgAAAMW8RStj6XscVgQAAFYEAAAMAAAAAAAAAAAAIACAgQAAAACx
uMDUuea5/S56aXBQSwECFgsKAAIAAADMvEUrotPnsKcnAACnJwAADAAAAAAAAAAAACAAgIGABAAA
ua7BpsfYsOEuemlwUEsBAhYLCgACAAAAtbxFK4tEPLzoMQAA6DEAAAwAAAAAAAAAAAAgAICBUSwA
ALy6wM6/tcitLnppcFBLAQIWCwoAAgAAANa8RSvvD3TN+VAAAPlQAAAOAAAAAAAAAAAAIACAgWNe
AADAr8a/x6659sD8LnppcFBLAQIWCwoAAgAAAL28RSvfeRYz6DcAAOg3AAAMAAAAAAAAAAAAIACA
gYivAADD1r3FsNTA0y56aXBQSwUGAAAAAAUABQAkAQAAmucAAAAA

--==SoftForum-WebMail-1.0-32BF5B923BC0B197==--


From owner-idn@ops.ietf.org  Sun Oct  7 21:15:41 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26562
	for <idn-archive@lists.ietf.org>; Sun, 7 Oct 2001 21:15:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qOh7-000L9H-00
	for idn-data@psg.com; Sun, 07 Oct 2001 17:54:57 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qOh5-000L7g-00
	for idn@ops.ietf.org; Sun, 07 Oct 2001 17:54:56 -0700
Received: from LocalHost ([140.115.7.27])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f9810f703385;
	Mon, 8 Oct 2001 09:00:41 +0800 (CST)
Message-ID: <001701c14f93$7ef11480$1b07738c@q.j.tw>
From: "tsenglm@????.??.tw" <tsenglm@cc.ncu.edu.tw>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
References: <016c01c14c76$ea176c20$dd00a8c0@jamessonyvaio> <3BC0236A.CDAC064@twnic.net.tw> <3BBFF722.EA1D7B58@zetnet.co.uk>
Subject: Re: [idn] WG Update
Date: Mon, 8 Oct 2001 08:52:22 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "David Hopwood" <david.hopwood@zetnet.co.uk>
> -----BEGIN PGP SIGNED MESSAGE-----
>
> Erin Chen wrote:
> > As in the 2. General Requirements of 2.3 Canonicalization
> >
> > [21] In order to retain backward compatibility with the current DNS,
> > the service MUST retain the case-insensitive comparison for US-ASCII
> > as specified in RFC 1035. For example, Latin capital letter A (U+0041)
> > MUST match Latin small letter a (U+0061). Unicode Technical Report #21
> > describes some of the issues with case mapping. Case-insensitivity for
> > non US-ASCII MUST be discussed in the protocol proposal.
> >
> > I recommend modify the last line "MUST be discussed" to be
> > "MUST be provided", as to be " Case-insensitivity for non US-ASCII MUST
be
> > provided in the protocol proposal"
>
> I disagree. As it happens, all of the proposals provide case-insensitivity
> for non-US-ASCII, but it is *not* a requirement. The protocol would work
> fine and would be perfectly acceptable to users without it. We should be
> clear about the difference between features that are *desirable* (in this
> case for consistency), and *required* features.
>
              I  think the requirement in case-insensitives for non-US-ASCII
should be specified in applied rang of UNICODE , that is only applied to
"Han" characters only.
> In particular, preservation of case is wholly unnecessary, IMHO.
> [21] is perfectly OK as it is (although much of the rest of the
requirements
> draft is not; I'll discuss that in another post).
>
>
> <tsenglm@csie.ncu.edu.tw> wrote:
> > The TC/SC equivalent class is always conceptually described by the
> > similar properties of  case in ASCII characters, ...
>
> No, it is not. TC/SC folding is an entirely separate issue to case
> folding. As I've pointed out before, it is counterproductive to try to
> argue by an analogy that a consensus of the WG does not accept.
>
         Right !  Describing TC/SC with the term "case folding" will
produce confusing .  TC/SC equivalence class will be translated to ACE ASCII
with CASE , so it can be caseinsensitive comparison  and  also be recoveried
to their original scripts form .  In this siyuation , it is very different
from pure-ASCII characters case folding.

L.M.Tseng




From owner-idn@ops.ietf.org  Mon Oct  8 02:36:12 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13284
	for <idn-archive@lists.ietf.org>; Mon, 8 Oct 2001 02:36:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qTfW-000889-00
	for idn-data@psg.com; Sun, 07 Oct 2001 23:13:38 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qTfV-00087m-00
	for idn@ops.ietf.org; Sun, 07 Oct 2001 23:13:37 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VVu9drkLLywDh0loXVMmqQqA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GG756KKL; Mon, 08 Oct 2001 02:13:18 EDT
To: david.hopwood@zetnet.co.uk
Cc: idn@ops.ietf.org
Date: Sun, 7 Oct 2001 23:33:29 -0700
Subject: Re: [idn] WG Update
Message-ID: <20011007.233332.-710781.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-6,8-83
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

David, 
 Are you saying that the possibility of recover uppercase
of Latin, Greek or Cyrillic is not a useful feature from 
deployment of IDN?

Liana

On Sun, 07 Oct 2001 07:33:06 +0100 David Hopwood
<david.hopwood@zetnet.co.uk> writes:
> -----BEGIN PGP SIGNED MESSAGE-----
> 
> Erin Chen wrote:
> > As in the 2. General Requirements of 2.3 Canonicalization
> > 
> > [21] In order to retain backward compatibility with the current 
> DNS,
> > the service MUST retain the case-insensitive comparison for 
> US-ASCII
> > as specified in RFC 1035. For example, Latin capital letter A 
> (U+0041)
> > MUST match Latin small letter a (U+0061). Unicode Technical Report 
> #21
> > describes some of the issues with case mapping. Case-insensitivity 
> for
> > non US-ASCII MUST be discussed in the protocol proposal.
> > 
> > I recommend modify the last line "MUST be discussed" to be
> > "MUST be provided", as to be " Case-insensitivity for non US-ASCII 
> MUST be
> > provided in the protocol proposal"
> 
> I disagree. As it happens, all of the proposals provide 
> case-insensitivity
> for non-US-ASCII, but it is *not* a requirement. The protocol would 
> work
> fine and would be perfectly acceptable to users without it. We 
> should be
> clear about the difference between features that are *desirable* (in 
> this
> case for consistency), and *required* features.
> 
> In particular, preservation of case is wholly unnecessary, IMHO.
> [21] is perfectly OK as it is (although much of the rest of the 
> requirements
> draft is not; I'll discuss that in another post).
> 
> 
> <tsenglm@csie.ncu.edu.tw> wrote:
> > The TC/SC equivalent class is always conceptually described by the
> > similar properties of  case in ASCII characters, ...
> 
> No, it is not. TC/SC folding is an entirely separate issue to case
> folding. As I've pointed out before, it is counterproductive to try 
> to
> argue by an analogy that a consensus of the WG does not accept.
> 
> - -- 
> 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
> 
> iQEVAwUBO7/2zTkCAxeYt5gVAQGvZQgAvWfiHcqPPog2htBBOhtLUXMP4dOSVI5/
> F03Wk4oeYhyr32wMhjbDDsxCwdroAdhExEiAwLt31qpg7dSuyglzM3VILxznvvVu
> /inTb1oari9SnGjwu2hDKlTs5lfeTHKiSsdm5D1xAwaUo6fA8RW0gaDWv20elt74
> fm+WmS+3QHRxM4Y6MdCtjLpJdC0ywZUyDo/wfM9iMNsc7WHWzfWCE37xFQYH9nsJ
> zvRxfzV9AaEkV0ZtxBJWRknP1E59Gv3zGBi60WHX21/1ZykGu/6e6pk8OZ+CEHx4
> Ock7UKySbpkqXOncpCwJVSEdJyW+Y0hqfSCwzmlRXl5JIOpCoENHvQ==
> =oyij
> -----END PGP SIGNATURE-----
> 
> 



From owner-idn@ops.ietf.org  Mon Oct  8 02:48:30 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13957
	for <idn-archive@lists.ietf.org>; Mon, 8 Oct 2001 02:48:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qU0P-0008zr-00
	for idn-data@psg.com; Sun, 07 Oct 2001 23:35:13 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qU0O-0008zi-00
	for idn@ops.ietf.org; Sun, 07 Oct 2001 23:35: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 f986XFT04172; Mon, 8 Oct 2001 08:33:15 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.11.4+Sun/TRM-1-KLIENT); Mon, 8 Oct 2001 08:33:56 +0200 (MEST) (MET)
Message-Id: <200110080633.f986Xuj26651@valinor.malmo.trab.se>
Date: Mon, 8 Oct 2001 08:33:56 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: [idn] WG Update
To: idn@ops.ietf.org, david.hopwood@zetnet.co.uk
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: bcwYbK5SqwW4vPIn5JTf+Q==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.5_41 SunOS 5.9 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk


>> I recommend modify the last line "MUST be discussed" to be
>> "MUST be provided", as to be " Case-insensitivity for non US-ASCII MUST be
>> provided in the protocol proposal"
>
>I disagree. As it happens, all of the proposals provide case-insensitivity
>for non-US-ASCII, but it is *not* a requirement. The protocol would work
>fine and would be perfectly acceptable to users without it. We should be
>clear about the difference between features that are *desirable* (in this
>case for consistency), and *required* features.

Well, I disagree to that.

It *is* a requirement that case-insensitivity shall work for all letters.
That has been the DNS standard so far. That is what people expect.
To have case-sensitive matching is not fine for everybody.

If we are not going to support case-insensivity and case preserving in
responses, then we should turn it of for ASCII too.
Either we support full backward compatibility (that includes having
case-insensitivity and case preserving in protocol for all letters),
or we kill it off for ASCII letters too.
Just because non-ASCII has not been used, does not mean that people
expect the same rules that exist for ASCII to exist for non-ASCII.
The current DNS standard has defined that case-insensitivity shall be
used and that case should be preserved in responses. We break that
if it is not done for non-ASCII letters too.

   Dan




From owner-idn@ops.ietf.org  Mon Oct  8 02:56:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14393
	for <idn-archive@lists.ietf.org>; Mon, 8 Oct 2001 02:56:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qU8p-0009NK-00
	for idn-data@psg.com; Sun, 07 Oct 2001 23:43:55 -0700
Received: from [203.126.116.228] (helo=mail.i-dns.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qU8o-0009NB-00
	for idn@ops.ietf.org; Sun, 07 Oct 2001 23:43:54 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id E13D0FFC0E; Mon,  8 Oct 2001 14:44:26 +0800 (SGT)
Message-ID: <02fd01c14fc4$952f8bb0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <david.hopwood@zetnet.co.uk>, <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>
References: <20011007.233332.-710781.0.liana.ydisg@juno.com>
Subject: Re: [idn] WG Update
Date: Mon, 8 Oct 2001 14:43:47 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

the keyword here "useful" (which you used) vs "required" feature.
think about it :-)

james

----- Original Message -----
From: <liana.ydisg@juno.com>
To: <david.hopwood@zetnet.co.uk>
Cc: <idn@ops.ietf.org>
Sent: Monday, October 08, 2001 2:33 PM
Subject: Re: [idn] WG Update


> David,
>  Are you saying that the possibility of recover uppercase
> of Latin, Greek or Cyrillic is not a useful feature from
> deployment of IDN?
>
> Liana
>
> On Sun, 07 Oct 2001 07:33:06 +0100 David Hopwood
> <david.hopwood@zetnet.co.uk> writes:
> > -----BEGIN PGP SIGNED MESSAGE-----
> >
> > Erin Chen wrote:
> > > As in the 2. General Requirements of 2.3 Canonicalization
> > >
> > > [21] In order to retain backward compatibility with the current
> > DNS,
> > > the service MUST retain the case-insensitive comparison for
> > US-ASCII
> > > as specified in RFC 1035. For example, Latin capital letter A
> > (U+0041)
> > > MUST match Latin small letter a (U+0061). Unicode Technical Report
> > #21
> > > describes some of the issues with case mapping. Case-insensitivity
> > for
> > > non US-ASCII MUST be discussed in the protocol proposal.
> > >
> > > I recommend modify the last line "MUST be discussed" to be
> > > "MUST be provided", as to be " Case-insensitivity for non US-ASCII
> > MUST be
> > > provided in the protocol proposal"
> >
> > I disagree. As it happens, all of the proposals provide
> > case-insensitivity
> > for non-US-ASCII, but it is *not* a requirement. The protocol would
> > work
> > fine and would be perfectly acceptable to users without it. We
> > should be
> > clear about the difference between features that are *desirable* (in
> > this
> > case for consistency), and *required* features.
> >
> > In particular, preservation of case is wholly unnecessary, IMHO.
> > [21] is perfectly OK as it is (although much of the rest of the
> > requirements
> > draft is not; I'll discuss that in another post).
> >
> >
> > <tsenglm@csie.ncu.edu.tw> wrote:
> > > The TC/SC equivalent class is always conceptually described by the
> > > similar properties of  case in ASCII characters, ...
> >
> > No, it is not. TC/SC folding is an entirely separate issue to case
> > folding. As I've pointed out before, it is counterproductive to try
> > to
> > argue by an analogy that a consensus of the WG does not accept.
> >
> > - --
> > 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
> >
> > iQEVAwUBO7/2zTkCAxeYt5gVAQGvZQgAvWfiHcqPPog2htBBOhtLUXMP4dOSVI5/
> > F03Wk4oeYhyr32wMhjbDDsxCwdroAdhExEiAwLt31qpg7dSuyglzM3VILxznvvVu
> > /inTb1oari9SnGjwu2hDKlTs5lfeTHKiSsdm5D1xAwaUo6fA8RW0gaDWv20elt74
> > fm+WmS+3QHRxM4Y6MdCtjLpJdC0ywZUyDo/wfM9iMNsc7WHWzfWCE37xFQYH9nsJ
> > zvRxfzV9AaEkV0ZtxBJWRknP1E59Gv3zGBi60WHX21/1ZykGu/6e6pk8OZ+CEHx4
> > Ock7UKySbpkqXOncpCwJVSEdJyW+Y0hqfSCwzmlRXl5JIOpCoENHvQ==
> > =oyij
> > -----END PGP SIGNATURE-----
> >
> >
>




From owner-idn@ops.ietf.org  Mon Oct  8 13:30:12 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27188
	for <idn-archive@lists.ietf.org>; Mon, 8 Oct 2001 13:30:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qduO-0001wU-00
	for idn-data@psg.com; Mon, 08 Oct 2001 10:09:40 -0700
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qduM-0001wO-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 10:09:39 -0700
Received: from zetnet.co.uk (man-s075.dialup.zetnet.co.uk [194.247.41.202])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f98H9XX19297;
	Mon, 8 Oct 2001 18:09:33 +0100
Message-ID: <3BC1DDCD.3F4209C@zetnet.co.uk>
Date: Mon, 08 Oct 2001 18:09: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: liana.ydisg@juno.com, idn@ops.ietf.org
Subject: Re: [idn] WG Update
References: <20011007.233332.-710781.0.liana.ydisg@juno.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-----

liana.ydisg@juno.com wrote:
> 
> David,
>  Are you saying that the possibility of recover uppercase
> of Latin, Greek or Cyrillic is not a useful feature from
> deployment of IDN?

I'm saying that it is not a high priority compared to any other
considerations. *If* it can be supported without making compromises
elsewhere, then it should be implemented.

- -- 
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

iQEVAwUBO8HdsjkCAxeYt5gVAQHJNQf+P5DhfPBXSrx+l/ewFbrglcVZkmPuYBXy
T3TqtTz/azkiLFD4/LgIr4Aphg2Q1NkWpXaywzNZINPnBg6/c8hVCi6fCCnKnaS4
iwm3vIbl7FMBQn10wMhMrI3jXWAClrKeXrvG040iZaM2hskQHAyDLaMAv6nL1vIt
Q1IDjtNHzsEXlkrSaobHdybbKQ4dhpwyAF5QMJcDqSlO3Q61GPw3Oz/fsY7AIWjk
6+wxSZkMTECHLEVYz/aT5mNf9DuFQ/7hQzQx/tJQcmpsom5jPOroWhyyle+Oc5Ci
aOGhrwILigvanJp583e/bOTbzdlvIvv1iNPa8l3icl9a+80Zib8XwA==
=aPqA
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Mon Oct  8 13:49:22 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27577
	for <idn-archive@lists.ietf.org>; Mon, 8 Oct 2001 13:49:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qeJw-0002bl-00
	for idn-data@psg.com; Mon, 08 Oct 2001 10:36:04 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qeJv-0002be-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 10:36:03 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VVFsisH+qcZFx2jyHJjCTS/Q==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GG9C3S4L; Mon, 08 Oct 2001 13:33:22 EDT
To: tsenglm@cc.ncu.edu.tw
Cc: david.hopwood@zetnet.co.uk, idn@ops.ietf.org
Date: Mon, 8 Oct 2001 10:53:24 -0700
Subject: Re: [idn] WG Update
Message-ID: <20011008.105327.-940711.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-26,28-97
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

From processing point of view, they are mappings
from one code point to another code point in 
[nameprep], it doesn't matter what the code 
point is.  It does not increase complexity nor 
decrease it.  In this sense, case folding or not is 
the same to every script. The matched values are
represented only in [a-z0-9].

On the other hand, when we speak about how to 
treat the code points, that is which one maps into
the other is linguistic issue. ( I hope at this point, 
no one dispute this with me anymore. :-)
If this is in a requirement to be discussed, then it has 
to be specific on different effects to different types
of scripts, otherwise there are little specifics to be a
useful study.  We can be here argue for Latin but not 
TC/SC forever.  To ask for more protocol to be provided 
is a good exercise for  the authors thinking through 
many different script use issues.  I suggest this to be
modified to "provide discussions on at least three different 
language users on how to implement the requirement, 
and among the three, one must from Alphabet language,
 one must from CJK languages and one must from 
the author's native language. "

Liana

On Mon, 8 Oct 2001 08:52:22 +0800 "tsenglm@????.??.tw"
<tsenglm@cc.ncu.edu.tw> writes:
> 
> ----- Original Message -----
> From: "David Hopwood" <david.hopwood@zetnet.co.uk>
> > -----BEGIN PGP SIGNED MESSAGE-----
> >
> > Erin Chen wrote:
> > > As in the 2. General Requirements of 2.3 Canonicalization
> > >
> > > [21] In order to retain backward compatibility with the current 
> DNS,
> > > the service MUST retain the case-insensitive comparison for 
> US-ASCII
> > > as specified in RFC 1035. For example, Latin capital letter A 
> (U+0041)
> > > MUST match Latin small letter a (U+0061). Unicode Technical 
> Report #21
> > > describes some of the issues with case mapping. 
> Case-insensitivity for
> > > non US-ASCII MUST be discussed in the protocol proposal.
> > >
> > > I recommend modify the last line "MUST be discussed" to be
> > > "MUST be provided", as to be " Case-insensitivity for non 
> US-ASCII MUST
> be
> > > provided in the protocol proposal"
> >
> > I disagree. As it happens, all of the proposals provide 
> case-insensitivity
> > for non-US-ASCII, but it is *not* a requirement. The protocol 
> would work
> > fine and would be perfectly acceptable to users without it. We 
> should be
> > clear about the difference between features that are *desirable* 
> (in this
> > case for consistency), and *required* features.
> >
>               I  think the requirement in case-insensitives for 
> non-US-ASCII
> should be specified in applied rang of UNICODE , that is only 
> applied to
> "Han" characters only.
> > In particular, preservation of case is wholly unnecessary, IMHO.
> > [21] is perfectly OK as it is (although much of the rest of the
> requirements
> > draft is not; I'll discuss that in another post).
> >
> >
> > <tsenglm@csie.ncu.edu.tw> wrote:
> > > The TC/SC equivalent class is always conceptually described by 
> the
> > > similar properties of  case in ASCII characters, ...
> >
> > No, it is not. TC/SC folding is an entirely separate issue to case
> > folding. As I've pointed out before, it is counterproductive to 
> try to
> > argue by an analogy that a consensus of the WG does not accept.
> >
>          Right !  Describing TC/SC with the term "case folding" will
> produce confusing .  TC/SC equivalence class will be translated to 
> ACE ASCII
> with CASE , so it can be caseinsensitive comparison  and  also be 
> recoveried
> to their original scripts form .  In this siyuation , it is very 
> different
> from pure-ASCII characters case folding.
> 
> L.M.Tseng
> 
> 



From owner-idn@ops.ietf.org  Mon Oct  8 13:58:38 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27720
	for <idn-archive@lists.ietf.org>; Mon, 8 Oct 2001 13:58:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qeRQ-0002qg-00
	for idn-data@psg.com; Mon, 08 Oct 2001 10:43:48 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qeRP-0002qZ-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 10:43:47 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VVFNRro5R0sKUXotfilUDz+g==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GG9DMTR6; Mon, 08 Oct 2001 13:43:12 EDT
To: david.hopwood@zetnet.co.uk
Cc: idn@ops.ietf.org
Date: Mon, 8 Oct 2001 11:03:29 -0700
Subject: Re: [idn] WG Update
Message-ID: <20011008.110331.-940711.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-3,5-21
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

Then I think we should give more careful consideration
on what can we do with that code point budget. 


On Mon, 08 Oct 2001 18:09:33 +0100 David Hopwood
<david.hopwood@zetnet.co.uk> writes:
> -----BEGIN PGP SIGNED MESSAGE-----
> 
> liana.ydisg@juno.com wrote:
> > 
> > David,
> >  Are you saying that the possibility of recover uppercase
> > of Latin, Greek or Cyrillic is not a useful feature from
> > deployment of IDN?
> 
> I'm saying that it is not a high priority compared to any other
> considerations. *If* it can be supported without making compromises
> elsewhere, then it should be implemented.
> 
> - -- 
> David Hopwood <david.hopwood@zetnet.co.uk>
> 



From owner-idn@ops.ietf.org  Mon Oct  8 14:20:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28210
	for <idn-archive@lists.ietf.org>; Mon, 8 Oct 2001 14:20:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qesF-0003ZN-00
	for idn-data@psg.com; Mon, 08 Oct 2001 11:11:31 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qesE-0003ZH-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 11:11:30 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VVvizMJa3LdQb/ox+yG4vZ1g==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GG9EYW6R; Mon, 08 Oct 2001 14:06:45 EDT
To: Dan.Oscarsson@trab.se
Cc: idn@ops.ietf.org, david.hopwood@zetnet.co.uk
Date: Mon, 8 Oct 2001 11:27:05 -0700
Subject: Re: [idn] WG Update
Message-ID: <20011008.112707.-940711.2.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-48
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

If IDN is going to be universal to all devices, then a 
handheld device may have uppercase support for 
a sick user to have a familar reading quickly.  So 
I think your case preserving arguement should be
considered. 

Liana

On Mon, 8 Oct 2001 08:33:56 +0200 (MEST) Dan Oscarsson
<Dan.Oscarsson@trab.se> writes:
> 
> >> I recommend modify the last line "MUST be discussed" to be
> >> "MUST be provided", as to be " Case-insensitivity for non 
> US-ASCII MUST be
> >> provided in the protocol proposal"
> >
> >I disagree. As it happens, all of the proposals provide 
> case-insensitivity
> >for non-US-ASCII, but it is *not* a requirement. The protocol would 
> work
> >fine and would be perfectly acceptable to users without it. We 
> should be
> >clear about the difference between features that are *desirable* 
> (in this
> >case for consistency), and *required* features.
> 
> Well, I disagree to that.
> 
> It *is* a requirement that case-insensitivity shall work for all 
> letters.
> That has been the DNS standard so far. That is what people expect.
> To have case-sensitive matching is not fine for everybody.
> 
> If we are not going to support case-insensivity and case preserving 
> in
> responses, then we should turn it of for ASCII too.
> Either we support full backward compatibility (that includes having
> case-insensitivity and case preserving in protocol for all letters),
> or we kill it off for ASCII letters too.
> Just because non-ASCII has not been used, does not mean that people
> expect the same rules that exist for ASCII to exist for non-ASCII.
> The current DNS standard has defined that case-insensitivity shall 
> be
> used and that case should be preserved in responses. We break that
> if it is not done for non-ASCII letters too.
> 
>    Dan
> 
> 



From owner-idn@ops.ietf.org  Mon Oct  8 14:50:21 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28730
	for <idn-archive@lists.ietf.org>; Mon, 8 Oct 2001 14:50:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qfHX-0004Fr-00
	for idn-data@psg.com; Mon, 08 Oct 2001 11:37:39 -0700
Received: from mail5.speakeasy.net ([216.254.0.205])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qfHX-0004Fl-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 11:37:39 -0700
Received: (qmail 46455 invoked from network); 8 Oct 2001 18:37:38 -0000
Received: from unknown (HELO Magnus) ([64.81.85.4]) (envelope-sender <tim@xtns.net>)
          by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <idn@ops.ietf.org>; 8 Oct 2001 18:37:38 -0000
Message-ID: <038a01c15027$cc27edc0$0200a8c0@Magnus>
From: "Tim Langdell" <tim@xtns.net>
To: <idn@ops.ietf.org>
References: <20011008.112707.-940711.2.liana.ydisg@juno.com>
Subject: [idn] Re: NN%<-->UTF8
Date: Mon, 8 Oct 2001 11:33:56 -0700
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.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Does anyone please have a link to a good conversion routine for NN% to and
from UTF8 for URI transport? Perl script would be good ...





From owner-idn@ops.ietf.org  Mon Oct  8 21:11:20 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05116
	for <idn-archive@lists.ietf.org>; Mon, 8 Oct 2001 21:11:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ql3m-000Ez9-00
	for idn-data@psg.com; Mon, 08 Oct 2001 17:47:50 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.33 #1)
	id 15ql3k-000Exm-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 17:47:48 -0700
Received: (qmail 27602 invoked by uid 1001); 9 Oct 2001 00:48:03 -0000
Date: 9 Oct 2001 00:48:03 -0000
Message-ID: <20011009004803.28618.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] WG Update
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Suppose we deploy uppercase IDNs. This could turn out to be a mistake---
in fact, a complete disaster---because uppercase Alpha looks just like
uppercase A. We won't be able to fix the mistake, because people will
already be relying on domain names that contain Alpha.

Suppose, on the other hand, we initially prohibit uppercase IDNs. If
this turns out to be a mistake, we can fix it later, adding support for
uppercase IDNs, without breaking anything.

Dan Oscarsson writes:
> If we are not going to support case-insensivity and case preserving in
> responses, then we should turn it of for ASCII too.

Deprecating uppercase ASCII is fine. Of course, caches and servers will
have to continue accepting uppercase ASCII for compatibility, but users
shouldn't type any new names in uppercase.

> It *is* a requirement that case-insensitivity shall work for all letters.
> That has been the DNS standard so far. That is what people expect.

``It *is* a requirement that host names shall be ASCII. That has been
the standard so far. That is what people expect.'' Stupid argument.

---Dan



From owner-idn@ops.ietf.org  Mon Oct  8 21:57:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06573
	for <idn-archive@lists.ietf.org>; Mon, 8 Oct 2001 21:57:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qlrG-000Gss-00
	for idn-data@psg.com; Mon, 08 Oct 2001 18:38:58 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qlrE-000Gsm-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 18:38: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 46312 for idn@ops.ietf.org; Sun, 07 Oct 2001 20:38:36 -0500
Message-ID: <3BC25528.FC918BB4@ehsco.com>
Date: Mon, 08 Oct 2001 20:38:48 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: idn@ops.ietf.org
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
References: <200110040700.f9470bj18628@valinor.malmo.trab.se>	
	 <p0510030eb7e24eb9f210@[165.227.249.20]>	
	 <5.1.0.14.2.20011004213749.02478cd0@dcrocker.net>	
	 <5.1.0.14.2.20011004235936.023e1500@dcrocker.net>
	 <5.1.0.14.2.20011005141903.04649150@dcrocker.net>
	 <3BBE467C.A9797B21@ehsco.com> <p0510033ab7e3fc24f02c@[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,

First of all, I'd like to thank you for taking the time to enumerate your
many perceived technical issues with the UDNS model. These points deserve
to be fully debated and discussed.

However, I think that your comments also represent a larger issue which
needs to be resolved first. We need to come to a group consensus on the
question of whether or not a UTF-8 namespace is necessary, desirable, or
neither of those, and this needs to happen before the technical points can
be debated in appropriate context. Without consensus on this underlying
point, debates over relative costs will be debates over half-full vs
half-empty, and will get us nowhere.

For example:

> UDNS gives us all of these problems for the limited benefit that some
> applications don't have to implement one additional encoding for
> sending host names on the wire. Does that seem like a good balance?

The above is a comparison of UDNS' perceived cost relative to a benefit,
but we haven't fully discussed the benefits as of yet. Clearly, ACE has
many costs, some of which are quite high AND ongoing, although most of us
agree that some form of ACE is necessary, and is therefore worth whatever
cost may be required. What we do not agree on is the benefit that UDNS (or
a similar mechanism) would provide. Making a decision based on cost alone
is misrepresentative of the true value of UDNS, just as a decision on ACE
which was based solely on cost would have misrepresented the true value of
its benefits (being necessary, it can have almost any cost).

Personally, I believe that UDNS is also necessary, and is therefore worth
almost any cost (although as I will show, I think the cost is somewhat
lower than you do). I base this on a few key arguments:

 * BCP18's is "Official Internet Policy" which requires support for
   UTF-8 in all new protocols, and in modifications to all existing
   protocols: "lack of an ability to use UTF-8 is a violation of this
   policy; such a violation would need a variance procedure". Simply
   put, policy requires this WG to devise some kind of support for
   UTF-8, unless it can be proven unreasonable. Nobody has proven it
   to be unreasonable.

 * Without a UTF-8 DNS interface, no new protocols or applications
   can be developed that are UTF-8 clean. Instead, they will be
   UTF-8 for everything EXCEPT domain names, and in some cases this
   will be fatal. One example we have already discussed for this is
   mapping between LDAPv3 distinguished names and DNS domain names
   (mapping dc= RDNs to DNS). Failure to support UTF-8 is a heavy
   blow to such efforts, requiring tremendous amounts of development
   effort and infrastructure oversight, likely hindering the use
   and development of LDAP in the Internet.

 * Global public networking is only in its infancy; there will
   likely be many thousands of new protocols and applications which
   are developed over the next few decades (some in the IETF WGs,
   most in business, educational or personal networks, and most will
   be developed outside of the US). If those applications follow the
   Official Internet Policy, they will be UTF-8 only or use it as the
   preferred encoding. However, those applications will also be
   saddled with ACE conversion wherever they have to interact with
   domain names, meaning they cannot be UTF-8 clean. This will be
   extremely acute in non-US development environments.

 * Towards the above point, UDNS provides an optional, user-driven
   transition path from ASCII to UTF-8. UDNS allows applications to
   be written so that they only function in UTF-8 environments.
   While this may not seem a reasonable objective of this WG, this
   should be the long-term vision of what we are trying to achieve.
   We should be enabling the development of a truly international
   Internet infrastructure which is UTF-8 clean throughout, and
   UDNS provides this transitional path. Conversely, ACE does not
   provide this transition. In fact, the goal of seamless backwards
   compatibility actively hinders migration.

   Let me restate this point, since it is somewhat complex. Although
   UDNS supports a dual-mode model, once UDNS (or something similar)
   were approved, developers could begin to work on applications
   which ONLY used UDNS, without any code for ASCII or ACE. At first
   this would be small private apps, but over the course of a couple
   of decades, it would likely be most of the new apps. Without UDNS
   (or something similar), it would still be ASCII at the end of that
   timeframe. In short, we need UDNS if we are ever to drop ASCII.

 * The modernization and internationalization of legacy protocols,
   applications and formats will almost certainly require a UTF-8
   DNS eventually. It will not be possible to build and deploy
   UTF-8 extensions to SMTP without a UTF-8 DNS infrastructure. As
   with the above points, once a UTF-8 approach has gained some
   critical mass, these extensions become feasible. Without the
   infrastructure, SMTP will continue to be bound to ASCII.
  
 * UDNS is optional and transitional, on a per-domain basis. This
   allows a transition to occur as users see fit, without requiring
   a replacement of the existing DNS infrastructure with an
   alternate naming service. While this is technically not a
   "requirement" per se, the seamless user-driven transitional
   aspects should be requirements. Something very much like UDNS
   will be required for this. A "new naming service" is unlikely to
   reach critical mass without some kind of backwards compatibility,
   which UDNS provides.

   Furthermore, the cost of UDNS is incremental to that of ACE,
   since they share many common features and functions. If a
   developer is going to add ACE support to an application (which
   they must do in the short term), it is incremental to add UDNS
   support at the same time. On the other hand, adding ACE now and
   then going back to glue on something else is a second development
   effort, with greater costs.

 * UTF-8 is infinitely more manageable and serviceable than ACE.
   By being able to use UTF-8 tools and services, the Internet can
   be kept running much easier than users having to transliterate
   ACE operations. We should not be contributing to frailty. When
   a network is already broken, ACE obfuscates the problem by
   displaying aq--gobbledygook in traceroute, netstat, tcpdump and
   all of the other tools. ACE libs can certainly address this part
   of the issue, the extent of the support for tasks like importing
   trace data into a spreadsheet or viewing it in an editor is not
   as compelling. The massive number of UTF-8 tools are extremely
   compelling in terms of general manageability and serviceability
   of the global DNS.

 * Finally, there are some problems that ACE cannot solve, which
   UDNS can. The clipboard problem practically goes away, if not
   directly then indirectly, simply because we can facilitate the
   use of UTF-8 everywhere, rather than having to transliterate
   between application- and protocol-specific encodings. EG, if we
   ALLOW for the consistent use of UTF-8, then it is more likely
   to happen than if we actively PROHIBIT it by mandating yet
   another encoding which MUST be accounted for in every operation.

So that's the "benefit" side of the argument. If we can agree that these
are important considerations, and that some kind of support for UTF-8 is a
requirement (as per item #1), then we can debate costs and features as
they compare to that benefit.

Here is my evaluation of your perceived costs.

> - UDNS causes some strings that are legal in one encoding to be
> illegal in the other, and vice versa, meaning that some host names
> will be illegal part of the time, unpredictably

This issue would have to be resolved if we were ever to move beyond ACE.
It is beneficial to design for such limits up front, rather than revoking
names later which will be incompatible. This is only a cost if ACE and
some other service are developed at different times, and is NOT a cost if
they are developed together. This is, in fact, a motivating factor for
beginning work on UDNS *NOW*.

> - UDNS requires more work to be done by authoritative DNS servers

Yes, UDNS requires authoritative servers to maintain name mapping
information. However, I see this as being a transitional cost. In the
beginning, few clients will support UDNS, but over the course of several
years, most clients will support UDNS. At some point (two decades out?
shorter?) it should be possible to switch entirely to UDNS, meaning that
there will no longer be a need for servers to store both versions. The
longer we delay beginning such a transition, the longer it will be before
we can complete that transition. If we never start it, we will never
complete it.

> - UDNS UTF-8 queries that fail will cause more load on the DNS

Yes, it will cause one additional lookup. This is equitable with requiring
one extra delegation server in the path. This is not a great cost to begin
with. Furthermore, seeing as how it is also transitional, it will only be
a cost for the short-term, and will not be a cost after a few years.

> - UDNS is not compatible with DNS security

I'm not sure I understand this point. Also, DNSSEC has many issues, and
appears to be destined for a redesign at this point.

> - UDNS requires that applications have the logic to send a new DNS query
> format

Yes, an alternative API is required to prevent clashes with legacy
applications (this was proven by DJB's pi test). However, this is not a
cost burden which is solely related to UDNS. For example, when hostnames
are extended beyond the RFC972/1123 rules, an alternative wide() API will
be required for several functions. Applications which transliterate ACE at
relatively deep levels (such as for DHCP) will also require this. For
these reasons, I consider this a cost of internationalization rather than
a cost for UDNS.

> - Applications that implement the UTF-8 part of UDNS have to handle
> the inevitable errors that come from queries that bounce, have to
> recast those queries in ACE (assuming that the name is even legal in
> ACE, which some won't be), and then have to emit those queries again,
> causing more DNS traffic

As with the other issues, this is a transitional cost which dissipates as
deployment goes up. It is a cost in the beginning, but it is not a
significant cost after a few years.

> - The errors caused by UTF-8 queries are the same as other legitimate
> DNS errors, meaning that applications will have to have their own
> (probably-nonstandard) logic for differentiating between expected
> errors and real errors

Because UDNS is an applicaton of EDNS, it uses the EDNS error codes. My
experience is that these codes are farily simple to work with.

From my perspective, you have raised four transitional costs (one of which
is nearly permanent but which does have an end), no perpetual costs, and
one cost I don't grok. That is not very expensive considering the benefits
and requirements, in my opinion. Conversely, ACE-only does have at least
one ongoing cost which is quite high (client-side name mutations), and
several perpetual costs in terms of usability and internationalization of
the global Internet.

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



From owner-idn@ops.ietf.org  Mon Oct  8 22:17:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06879
	for <idn-archive@lists.ietf.org>; Mon, 8 Oct 2001 22:17:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qmJB-000HxI-00
	for idn-data@psg.com; Mon, 08 Oct 2001 19:07:49 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qmJA-000Hwy-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 19:07:48 -0700
Received: from bbprime.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 TAA27474;
	Mon, 8 Oct 2001 19:07:43 -0700
Message-Id: <5.1.0.14.2.20011008184722.01fc2670@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 08 Oct 2001 19:07:21 -0700
To: "Eric A. Hall" <ehall@ehsco.com>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
Cc: idn@ops.ietf.org
In-Reply-To: <3BC25528.FC918BB4@ehsco.com>
References: <200110040700.f9470bj18628@valinor.malmo.trab.se>
 <p0510030eb7e24eb9f210@[165.227.249.20]>
 <5.1.0.14.2.20011004213749.02478cd0@dcrocker.net>
 <5.1.0.14.2.20011004235936.023e1500@dcrocker.net>
 <5.1.0.14.2.20011005141903.04649150@dcrocker.net>
 <3BBE467C.A9797B21@ehsco.com>
 <p0510033ab7e3fc24f02c@[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 06:38 PM 10/8/2001, Eric A. Hall wrote:
>  We need to come to a group consensus on the
>question of whether or not a UTF-8 namespace is necessary, desirable, or
>neither

Eric,

It is neither.

To repeat the conclusions from my presentation at the last IETF:  uDNS has 
no significant technical benefit over an ACE, but it does have a serious 
problem. It impedes transition, since it requires changes to the 
infrastructure, whereas an ACE does not.  A copy of the slides, from the 
presentation, is at:

         <http://www.brandenburg.com/presentations/iDN-choices-comments.ppt>

>The above is a comparison of UDNS' perceived cost relative to a benefit,

A more immediate problem is that uDNS is an idea, not a complete 
specification.  The current document is substantially incomplete.


>but we haven't fully discussed the benefits as of yet. Clearly, ACE has
>many costs, some of which are quite high AND ongoing

if you mean the encode/decode cost, please be serious.  remember how short 
the string is.  if you mean something else, please enumerate.

and please remember that UTF-8 is also an encoding and, therefore, carries 
an encode/decode cost.


>  * BCP18's is "Official Internet Policy" which requires support for
>    UTF-8 in all new protocols,

Please re-read section 2:

>    This document does not mandate a policy on name internationalization,
>    but requires that all protocols describe whether names are
>    internationalized or US-ASCII.

You are also neglecting to observe the fact that the DNS protocol already 
exists.  BCP18 is not mandating a change to existing protocols.


>  * Without a UTF-8 DNS interface, no new protocols or applications
>    can be developed that are UTF-8 clean. Instead, they will be
>    UTF-8 for everything EXCEPT domain names, and in some cases this
>    will be fatal.

"Fatal" is a very strong word.  Also an incorrect one.  Feel free to 
provide empirical data that supports your certitude.


>One example we have already discussed for this is
>    mapping between LDAPv3 distinguished names and DNS domain names
>    (mapping dc= RDNs to DNS). Failure to support UTF-8 is a heavy
>    blow to such efforts

Why would an encoding form affect the ability to translate between two 
different naming environment?  Encoding is for transport, rather than for 
"native" form.

A more serious limitation is the core difference between LDAP and DNS 
naming rules.

And this raises the major problem that protocol efforts, like the current 
one, must not be used to try to fix larger and unrelated problems, such as 
mapping between two, incompatible name spaces.


>  * UTF-8 is infinitely more manageable and serviceable than ACE.

What is the empiricial basis for this assertion?


>  * Finally, there are some problems that ACE cannot solve, which
>    UDNS can. The clipboard problem practically goes away,

1.  You are talking about representation inside a computer, rather than 
transport across a network.  Internet protocols pertain to transport, not 
storage.

2.  You are also wrong about this particular problem.  This choice does not 
affect the ability to clipboard a 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  Mon Oct  8 23:55:38 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09714
	for <idn-archive@lists.ietf.org>; Mon, 8 Oct 2001 23:55:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qnqh-000LsP-00
	for idn-data@psg.com; Mon, 08 Oct 2001 20:46:31 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qnqg-000LsJ-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 20:46:30 -0700
Received: from [165.227.249.20] (165-227-249-20.client.dsl.net [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f993kPD24417
	for <idn@ops.ietf.org>; Mon, 8 Oct 2001 20:46:25 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100303b7e8186c0b81@[165.227.249.20]>
In-Reply-To: <3BC25528.FC918BB4@ehsco.com>
References: <200110040700.f9470bj18628@valinor.malmo.trab.se>		
 <p0510030eb7e24eb9f210@[165.227.249.20]>		
 <5.1.0.14.2.20011004213749.02478cd0@dcrocker.net>		
 <5.1.0.14.2.20011004235936.023e1500@dcrocker.net>	
 <5.1.0.14.2.20011005141903.04649150@dcrocker.net>	
 <3BBE467C.A9797B21@ehsco.com> <p0510033ab7e3fc24f02c@[165.227.249.20]>
 <3BC25528.FC918BB4@ehsco.com>
Date: Mon, 8 Oct 2001 20:44:43 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 8:38 PM -0500 10/8/01, Eric A. Hall wrote:
>First of all, I'd like to thank you for taking the time to enumerate your
>many perceived technical issues with the UDNS model. These points deserve
>to be fully debated and discussed.

They have been; I was repeating what had already been said.

>However, I think that your comments also represent a larger issue which
>needs to be resolved first. We need to come to a group consensus on the
>question of whether or not a UTF-8 namespace is necessary, desirable, or
>neither of those, and this needs to happen before the technical points can
>be debated in appropriate context.

First, what the heck is a "UTF-8 namespace"? We're talking about 
Internet protcols, not namespaces. Second, the debate of "is there an 
advantage to carrying UTF-8 in the DNS protocol" has already been 
debated extensively. It was decided that debating in the abstract was 
not likely to produce a tangible result (namely a protocol); 
discussing specific proposals might lead to a good result. To date, 
there have been no UTF8-based proposals without major technical flaws.

>  Without consensus on this underlying
>point, debates over relative costs will be debates over half-full vs
>half-empty, and will get us nowhere.

We weren't debating them; again, I was restating what had already be 
said over and over. If you really feel that there may be a way to do 
UTF-8 in the DNS protocol, write an Internet Draft and submit it. 
"I'm too busy to write a proposal, but I have lots of time to argue 
about the basis for it" won't sway many people.

>For example:
>
>>  UDNS gives us all of these problems for the limited benefit that some
>>  applications don't have to implement one additional encoding for
>>  sending host names on the wire. Does that seem like a good balance?
>
>The above is a comparison of UDNS' perceived cost relative to a benefit,
>but we haven't fully discussed the benefits as of yet.

Some people would disagree with your definition of "fully".

>  Clearly, ACE has
>many costs, some of which are quite high AND ongoing, although most of us
>agree that some form of ACE is necessary, and is therefore worth whatever
>cost may be required.

Could you be specific about which parts of IDNA have "high" costs? 
The conversion from whatever local encoding to ACE is not much higher 
than converting to UTF-8. That's a pretty minor cost for all 
protocols that allow anything other than UTF-8.

>  What we do not agree on is the benefit that UDNS (or
>a similar mechanism) would provide.

That's one of the things. You skipped over the parts of my list that 
would make UDNS impossible to deploy for end users, namely the fact 
that some names would be illegal or legal in different parts of the 
Internet. That's a show-stopper.

>  Making a decision based on cost alone
>is misrepresentative of the true value of UDNS, just as a decision on ACE
>which was based solely on cost would have misrepresented the true value of
>its benefits (being necessary, it can have almost any cost).
>
>Personally, I believe that UDNS is also necessary, and is therefore worth
>almost any cost (although as I will show, I think the cost is somewhat
>lower than you do). I base this on a few key arguments:
>
>  * BCP18's is "Official Internet Policy" which requires support for
>    UTF-8 in all new protocols, and in modifications to all existing
>    protocols: "lack of an ability to use UTF-8 is a violation of this
>    policy; such a violation would need a variance procedure". Simply
>    put, policy requires this WG to devise some kind of support for
>    UTF-8, unless it can be proven unreasonable. Nobody has proven it
>    to be unreasonable.

This has been gone over many times; it is a red herring. Read the archives.

>  * Without a UTF-8 DNS interface, no new protocols or applications
>    can be developed that are UTF-8 clean. Instead, they will be
>    UTF-8 for everything EXCEPT domain names, and in some cases this
>    will be fatal. One example we have already discussed for this is
>    mapping between LDAPv3 distinguished names and DNS domain names
>    (mapping dc= RDNs to DNS). Failure to support UTF-8 is a heavy
>    blow to such efforts, requiring tremendous amounts of development
>    effort and infrastructure oversight, likely hindering the use
>    and development of LDAP in the Internet.

It is interesting that you are the only one who feels this way; none 
of the people active on LDAP protocol development or deployment have 
expressed the same concerns.

>  * Global public networking is only in its infancy; there will
>    likely be many thousands of new protocols and applications which
>    are developed over the next few decades (some in the IETF WGs,
>    most in business, educational or personal networks, and most will
>    be developed outside of the US). If those applications follow the
>    Official Internet Policy, they will be UTF-8 only or use it as the
>    preferred encoding. However, those applications will also be
>    saddled with ACE conversion wherever they have to interact with
>    domain names, meaning they cannot be UTF-8 clean. This will be
>    extremely acute in non-US development environments.

Again, this is based on a misreading of BCP18. Read the archives, 
particularly the messages from the author of BCP18. This is a dead 
horse, but feel free to beat it some more.

>  * Towards the above point, UDNS provides an optional, user-driven
>    transition path from ASCII to UTF-8.

"User-driven"? UDNS requires changes to name servers. How is that 
"user-driven"?

>  UDNS allows applications to
>    be written so that they only function in UTF-8 environments.

Not true at all. Every application would have to have an ACE fallback mode.

>    While this may not seem a reasonable objective of this WG, this
>    should be the long-term vision of what we are trying to achieve.
>    We should be enabling the development of a truly international
>    Internet infrastructure which is UTF-8 clean throughout, and
>    UDNS provides this transitional path.

Either you are assuming that all current protocols that allow user 
choice of charsets will disappear, or they will will require only 
UTF-8 in the future. Both of those do a severe disservice to the 
users.

>  Conversely, ACE does not
>    provide this transition. In fact, the goal of seamless backwards
>    compatibility actively hinders migration.

Hogwash. It has nothing to do with migration to UTF-8.

>
>    Let me restate this point, since it is somewhat complex. Although
>    UDNS supports a dual-mode model, once UDNS (or something similar)
>    were approved, developers could begin to work on applications
>    which ONLY used UDNS, without any code for ASCII or ACE.

You are not talking about the UDNS that is before the WG. That 
protocol *requires* an ACE fallback.

>  At first
>    this would be small private apps, but over the course of a couple
>    of decades, it would likely be most of the new apps. Without UDNS
>    (or something similar), it would still be ASCII at the end of that
>    timeframe. In short, we need UDNS if we are ever to drop ASCII.

That's too bad, because UDNS it fatally flawed, as described before.

>  * The modernization and internationalization of legacy protocols,
>    applications and formats will almost certainly require a UTF-8
>    DNS eventually. It will not be possible to build and deploy
>    UTF-8 extensions to SMTP without a UTF-8 DNS infrastructure. As
>    with the above points, once a UTF-8 approach has gained some
>    critical mass, these extensions become feasible. Without the
>    infrastructure, SMTP will continue to be bound to ASCII.

Some people reading that paragraph might assume that you are, or have 
been, active in the development of the protocols you are writing 
about. Of course, that isn't true. What is true is that most of the 
people who have been active in developing those protocols are pushing 
IDNA (or are at least rejecting UDNS as fatally flawed).

>    * UDNS is optional and transitional, on a per-domain basis. This
>    allows a transition to occur as users see fit, without requiring
>    a replacement of the existing DNS infrastructure with an
>    alternate naming service.

Again, this is simply wrong. Users don't control name servers.

>  While this is technically not a
>    "requirement" per se, the seamless user-driven transitional
>    aspects should be requirements. Something very much like UDNS
>    will be required for this. A "new naming service" is unlikely to
>    reach critical mass without some kind of backwards compatibility,
>    which UDNS provides.
>
>    Furthermore, the cost of UDNS is incremental to that of ACE,
>    since they share many common features and functions. If a
>    developer is going to add ACE support to an application (which
>    they must do in the short term),

So, if you admit that here, why did you contradict it above?

>  it is incremental to add UDNS
>    support at the same time. On the other hand, adding ACE now and
>    then going back to glue on something else is a second development
>    effort, with greater costs.

You haven't shown any need to go back and glue.

>  * UTF-8 is infinitely more manageable and serviceable than ACE.
>    By being able to use UTF-8 tools and services, the Internet can
>    be kept running much easier than users having to transliterate
>    ACE operations.

Users don't have to do that. Red herring.

>  We should not be contributing to frailty. When
>    a network is already broken, ACE obfuscates the problem by
>    displaying aq--gobbledygook in traceroute, netstat, tcpdump and
>    all of the other tools.

So, you are saying that those tools today correctly display UTF-8? Yeah, right.

>  ACE libs can certainly address this part
>    of the issue, the extent of the support for tasks like importing
>    trace data into a spreadsheet or viewing it in an editor is not
>    as compelling. The massive number of UTF-8 tools are extremely
>    compelling in terms of general manageability and serviceability
>    of the global DNS.

"Massive", eh? Could you catalog those?

>  * Finally, there are some problems that ACE cannot solve, which
>    UDNS can. The clipboard problem practically goes away, if not
>    directly then indirectly, simply because we can facilitate the
>    use of UTF-8 everywhere, rather than having to transliterate
>    between application- and protocol-specific encodings. EG, if we
>    ALLOW for the consistent use of UTF-8, then it is more likely
>    to happen than if we actively PROHIBIT it by mandating yet
>    another encoding which MUST be accounted for in every operation.

This again takes the view that all current protocols will eventually 
go to UTF-8 only. That is insulting to the people throughout the 
world who have a strong preference to their own character sets.

>So that's the "benefit" side of the argument. If we can agree that these
>are important considerations, and that some kind of support for UTF-8 is a
>requirement (as per item #1), then we can debate costs and features as
>they compare to that benefit.

So far, no agreement.

>  > - UDNS causes some strings that are legal in one encoding to be
>>  illegal in the other, and vice versa, meaning that some host names
>>  will be illegal part of the time, unpredictably
>
>This issue would have to be resolved if we were ever to move beyond ACE.
>It is beneficial to design for such limits up front, rather than revoking
>names later which will be incompatible. This is only a cost if ACE and
>some other service are developed at different times, and is NOT a cost if
>they are developed together. This is, in fact, a motivating factor for
>beginning work on UDNS *NOW*.

Sorry, but I missed the part where you explain how to fix the 
problem. Without a fix, UDNS is dead in the water.

>  > - UDNS requires more work to be done by authoritative DNS servers
>
>Yes, UDNS requires authoritative servers to maintain name mapping
>information. However, I see this as being a transitional cost.

And you demand that all of the other people running name servers will 
agree with you.

>  In the
>beginning, few clients will support UDNS, but over the course of several
>years, most clients will support UDNS. At some point (two decades out?
>shorter?) it should be possible to switch entirely to UDNS, meaning that
>there will no longer be a need for servers to store both versions. The
>longer we delay beginning such a transition, the longer it will be before
>we can complete that transition. If we never start it, we will never
>complete it.

In other words, you don't think that making the com/net/org servers 
and the root servers do normalization and mapping is a problem. I 
take it you don't run any of those.

>  > - UDNS UTF-8 queries that fail will cause more load on the DNS
>
>Yes, it will cause one additional lookup. This is equitable with requiring
>one extra delegation server in the path. This is not a great cost to begin
>with. Furthermore, seeing as how it is also transitional, it will only be
>a cost for the short-term, and will not be a cost after a few years.

You blithely double the load on the DNS during the "transition". Nice.

>  > - UDNS is not compatible with DNS security
>
>I'm not sure I understand this point. Also, DNSSEC has many issues, and
>appears to be destined for a redesign at this point.

Yeah, that's a popular argument.

>  > - UDNS requires that applications have the logic to send a new DNS query
>>  format
>
>Yes, an alternative API is required to prevent clashes with legacy
>applications (this was proven by DJB's pi test). However, this is not a
>cost burden which is solely related to UDNS. For example, when hostnames
>are extended beyond the RFC972/1123 rules, an alternative wide() API will
>be required for several functions. Applications which transliterate ACE at
>relatively deep levels (such as for DHCP) will also require this. For
>these reasons, I consider this a cost of internationalization rather than
>a cost for UDNS.

IDNA internationalizes just as well as UDNS, at lower cost.

>  > - Applications that implement the UTF-8 part of UDNS have to handle
>>  the inevitable errors that come from queries that bounce, have to
>>  recast those queries in ACE (assuming that the name is even legal in
>>  ACE, which some won't be), and then have to emit those queries again,
>>  causing more DNS traffic
>
>As with the other issues, this is a transitional cost which dissipates as
>deployment goes up.

Wrong. It is with us as long as there are current applications running.

>  It is a cost in the beginning, but it is not a
>significant cost after a few years.

First you said "twenty", now it's down to "a few". Some of us think 
there is a difference.

>  > - The errors caused by UTF-8 queries are the same as other legitimate
>>  DNS errors, meaning that applications will have to have their own
>>  (probably-nonstandard) logic for differentiating between expected
>>  errors and real errors
>
>Because UDNS is an applicaton of EDNS, it uses the EDNS error codes. My
>experience is that these codes are farily simple to work with.

You have misread UDNS, then. The query errors from un-upgraded 
servers will not be EDNS errors: they will be format errors from the 
current DNS.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Tue Oct  9 00:20:56 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09907
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 00:20:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qoFc-000Mz6-00
	for idn-data@psg.com; Mon, 08 Oct 2001 21:12:16 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qoFc-000Myz-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 21:12:16 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id NAA21272;
	Tue, 9 Oct 2001 13:11:49 +0900
Message-ID: <00b501c15078$afb77ce0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se> <20011009004803.28618.qmail@cr.yp.to>
Subject: [idn] case preservation
Date: Tue, 9 Oct 2001 13:13:01 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA09907


----- Original Message ----- 
From: "D. J. Bernstein" <djb@cr.yp.to>
To: <idn@ops.ietf.org>
Sent: Tuesday, October 09, 2001 9:48 AM
Subject: Re: [idn] WG Update


> Suppose we deploy uppercase IDNs. This could turn out to be a mistake---
> in fact, a complete disaster---because uppercase Alpha looks just like
> uppercase A. We won't be able to fix the mistake, because people will
> already be relying on domain names that contain Alpha.

Greek small 'o' and Cyrillic small 'B' have the same looks with their
latin counterparts. This does not lead us to ban both of them.
It makes sense to map greek 'o' into latin 'o', but prohibiting greek 'o'
does not make sense. we have no standard yet on such look-alike mappings.

Desirable case preservation feature in ACE  is :

  to encode  Greek capital 'A'  as Greek small 'a' with 
     a case flag for 'Capital'.

  For example, AMC-ACE-Z encodes greek <alpha><epsilon><kappa>,
  
  all capital : U+03B1 U+03B5 U+03BA:  mxAIP 
  all small   : u+03B1 u+03B5 u+03BA:  mxaip

  Two output ACE labels are case-insensitively equivalent.

> 
> Suppose, on the other hand, we initially prohibit uppercase IDNs. If
> this turns out to be a mistake, we can fix it later, adding support for
> uppercase IDNs, without breaking anything.
> 

someone sticking to un-fixed old applications would lose.


> Dan Oscarsson writes:
> > If we are not going to support case-insensivity and case preserving in
> > responses, then we should turn it of for ASCII too.
> 
> Deprecating uppercase ASCII is fine. Of course, caches and servers will
> have to continue accepting uppercase ASCII for compatibility, but users
> shouldn't type any new names in uppercase.

The case information carries valuable preferred formating of a label:
 for example,  UN.org, WHO.org are much easier to recogize.
That's one of the reasons why Most browers and email clients preserve the case informations.

Soobok

> 
> > It *is* a requirement that case-insensitivity shall work for all letters.
> > That has been the DNS standard so far. That is what people expect.
> 
> ``It *is* a requirement that host names shall be ASCII. That has been
> the standard so far. That is what people expect.'' Stupid argument.
> 
> ---Dan
> 




From owner-idn@ops.ietf.org  Tue Oct  9 00:53:30 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10216
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 00:53:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qodu-000O3E-00
	for idn-data@psg.com; Mon, 08 Oct 2001 21:37:22 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.33 #1)
	id 15qodt-000O2e-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 21:37:21 -0700
Received: (qmail 4956 invoked by uid 1001); 9 Oct 2001 04:37:34 -0000
Date: 9 Oct 2001 04:37:34 -0000
Message-ID: <20011009043734.15576.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] case preservation
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se> <20011009004803.28618.qmail@cr.yp.to> <00b501c15078$afb77ce0$ec1bd9d2@temp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Soobok Lee writes:
> for example,  UN.org, WHO.org are much easier to recogize.

If you actually visit the UN and WHO web sites, you'll see that they
consistently give their own DNs in lowercase: who.int, for example.

> prohibiting greek 'o' does not make sense

If someone is allowed to register aol.com with a Greek lowercase o, then
nameprep is a bad joke.

---Dan



From owner-idn@ops.ietf.org  Tue Oct  9 00:57:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10252
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 00:57:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qooW-000OW7-00
	for idn-data@psg.com; Mon, 08 Oct 2001 21:48:20 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.33 #1)
	id 15qooV-000OW1-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 21:48:19 -0700
Received: (qmail 30400 invoked by uid 1001); 9 Oct 2001 04:48:38 -0000
Date: 9 Oct 2001 04:48:38 -0000
Message-ID: <20011009044838.16785.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] I fear I cannot use IDN in the next 10 years
References: <200110040700.f9470bj18628@valinor.malmo.trab.se> <p0510030eb7e24eb9f210@[165.227.249.20]> <5.1.0.14.2.20011004213749.02478cd0@dcrocker.net> <5.1.0.14.2.20011004235936.023e1500@dcrocker.net> <5.1.0.14.2.20011005141903.04649150@dcrocker.net> <3BBE467C.A9797B21@ehsco.com> <p0510033ab7e3fc24f02c@[165.227.249.20]> <3BC25528.FC918BB4@ehsco.com> <p05100303b7e8186c0b81@[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:
> To date, 
> there have been no UTF8-based proposals without major technical flaws.

One exception is the straightforward set of Unicode/UTF-8 IDN operations
described in http://pi.cr.yp.to.

Yes, Unicode and UTF-8 require many software upgrades, but (1) those are
upgrades that we want to do anyway, and (2) all the other IDN proposals
require even more software upgrades.

---Dan



From owner-idn@ops.ietf.org  Tue Oct  9 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 ESMTP id BAA10835
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 01:15:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qp4E-000PFV-00
	for idn-data@psg.com; Mon, 08 Oct 2001 22:04:34 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qp4D-000PFP-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 22:04:33 -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 46492; Mon, 08 Oct 2001 00:04:18 -0500
Message-ID: <3BC2855E.F3B8796F@ehsco.com>
Date: Tue, 09 Oct 2001 00:04:31 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dave Crocker <dhc@dcrocker.net>
CC: idn@ops.ietf.org
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
References: <200110040700.f9470bj18628@valinor.malmo.trab.se>
	 <p0510030eb7e24eb9f210@[165.227.249.20]>
	 <5.1.0.14.2.20011004213749.02478cd0@dcrocker.net>
	 <5.1.0.14.2.20011004235936.023e1500@dcrocker.net>
	 <5.1.0.14.2.20011005141903.04649150@dcrocker.net>
	 <3BBE467C.A9797B21@ehsco.com>
	 <p0510033ab7e3fc24f02c@[165.227.249.20]> <5.1.0.14.2.20011008184722.01fc2670@dcrocker.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Dave Crocker wrote:

> uDNS has no significant technical benefit over an ACE

It advances the state of the Internet to a point beyond ASCII hackology,
which directly translates into a significant technical benefit for EVERY
OTHER PROTOCOL. Whereas there may not be any significant technical
difference between the two encodings from a high-level perspective, the
difference they make on the ground -- inside the applications which use
the encodings, particularly those applications and formats which already
use UTF-8 -- is tremendous.

> but it does have a serious problem. It impedes transition, since it
> requires changes to the infrastructure, whereas an ACE does not.

I disagree with both of those assertions:

 1) The changes which are required are optional. Admins that don't
    want to use IDNs will never have to change anything. Admins
    that want to use IDNs can deploy UDNS at their leisure. The
    root servers are the only servers that MUST be upgraded. It is
    entirely optional for every other zone, including the gTLDs,
    ccTLDs and end-user domains. It does not "require changes to
    the infrastructure" in the context you imply (unless your
    implication of "the infrastructure" was "the root servers").
    It can be rolled out at the whim of each and every other zone.

 2) ACE does require every application to implement transliteration
    for the applications to be usable as intended. ACE requires a
    fork-lift upgrade of the entire Internet, and we're left with
    ASCII hacks when that's over. UDNS is an incremental cost to
    this upgrade process, and leaves us with an infrastructure
    which is completely internationalized.

> >but we haven't fully discussed the benefits as of yet. Clearly, ACE
> >has many costs, some of which are quite high AND ongoing
> 
> if you mean the encode/decode cost, please be serious.  remember how
> short the string is.  if you mean something else, please enumerate.

As was illustrated, the principle ongoing cost is that every application
which is compliant with BCP18 will have to maintain separate mapping
services for ACE. Many protocols are intimately tied to domain names, and
all of them will have to implement a secondary mapping service.

> and please remember that UTF-8 is also an encoding and, therefore,
> carries an encode/decode cost.

If the OS and/or development environment is already UTF-8 clean, there is
minimal cost for the UTF-8 mode, but only for the ACE mode.

> >  * BCP18's is "Official Internet Policy" which requires support for
> >    UTF-8 in all new protocols,
> 
> Please re-read section 2:
> 
> >    This document does not mandate a policy on name internationalization,
> >    but requires that all protocols describe whether names are
> >    internationalized or US-ASCII.

It is hard to imagine how any application can comply with the objectives
given in BCP18 and not use UTF-8 for protocol data such as embedded domain
name components. That section 2 disclaims "names" in the context of
protocol labels is no surprise. That it would be interpreted as reasonable
cause to enforce yet another mandatory encoding on every protocol not yet
invented is questionable, IMO. That is the result of ACE-only.

Is there some unspoken intention of promoting ACE to the status of
~Internet-standard-encoding for new applications?

> You are also neglecting to observe the fact that the DNS protocol
> already exists.  BCP18 is not mandating a change to existing protocols.

It appears that I misread section 3.2. I concede this point.

> >  * Without a UTF-8 DNS interface, no new protocols or applications
> >    can be developed that are UTF-8 clean. Instead, they will be
> >    UTF-8 for everything EXCEPT domain names, and in some cases this
> >    will be fatal.
> 
> "Fatal" is a very strong word.  Also an incorrect one.  Feel free to
> provide empirical data that supports your certitude.

"Extreme hindrance to the point of not bothering" is more accurate,
although that translates to "fatal". One example is cited below.

> >One example we have already discussed for this is
> >    mapping between LDAPv3 distinguished names and DNS domain names
> >    (mapping dc= RDNs to DNS). Failure to support UTF-8 is a heavy
> >    blow to such efforts
> 
> Why would an encoding form affect the ability to translate between two
> different naming environment?  Encoding is for transport, rather than
> for "native" form.

So what's the solution? Should LDAP DNs store dc components as ACE-encoded
strings, even though the DN is UTF-8 aware already? Or should LDAP clients
and servers transliterate every DN they encounter for comparison?

Why force this choice of lesser evils, when we do not have to, and when we
arguable should not do so in the first place?

> A more serious limitation is the core difference between LDAP and DNS
> naming rules.

No, the dc= syntax already implies these rules. The problem is reflective
of applications which embrace UTF-8 and which also use DNS names as
protocol data. Every such application invented from here on out will face
this dilemma.

> And this raises the major problem that protocol efforts, like the
> current one, must not be used to try to fix larger and unrelated
> problems, such as mapping between two, incompatible name spaces.

The incompatibilities between dc= and DNS are exaggerated by ACE.

> >  * UTF-8 is infinitely more manageable and serviceable than ACE.
> 
> What is the empiricial basis for this assertion?

 | ACE libs can certainly address [] part
 | of the issue, the extent of the support for tasks like importing
 | trace data into a spreadsheet or viewing it in an editor is not
 | as compelling. The massive number of UTF-8 tools are extremely
 | compelling in terms of general manageability and serviceability
 | of the global DNS.

For example, there are plenty of large network admins who still maintain
address assignment spreadsheets. International users manipulating this
data in ACE form are faced with much greater tasks than would be required
if they could use UTF-8. At the least, UTF-8 is likely to be a supported
encoding in the OS, if not the spreadsheet app, while ACE is likely to be
supported in neither. These things add up to affect serviceability; where
did I transliterate that name wrong?

> >  * Finally, there are some problems that ACE cannot solve, which
> >    UDNS can. The clipboard problem practically goes away,
> 
> 1.  You are talking about representation inside a computer, rather than
> transport across a network.  Internet protocols pertain to transport,
> not storage.

We sure spent a lot of time talking about it.

> 2.  You are also wrong about this particular problem.  This choice does
> not affect the ability to clipboard a name.

It does affect transliteration requirements.

> A more immediate problem is that uDNS is an idea, not a complete
> specification.  The current document is substantially incomplete.

Yes, it needs some work, but the underlying principles are sound (IMO).

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



From owner-idn@ops.ietf.org  Tue Oct  9 01:21:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA11133
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 01:21:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qp8J-000PQ2-00
	for idn-data@psg.com; Mon, 08 Oct 2001 22:08:47 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qp8I-000PPw-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 22:08:46 -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 46494 for idn@ops.ietf.org; Mon, 08 Oct 2001 00:08:31 -0500
Message-ID: <3BC2865B.44C9C734@ehsco.com>
Date: Tue, 09 Oct 2001 00:08:44 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
CC: idn@ops.ietf.org
Subject: Re: [idn] I fear I cannot use IDN in the next 10 years
References: <200110040700.f9470bj18628@valinor.malmo.trab.se>		
	 <p0510030eb7e24eb9f210@[165.227.249.20]>		
	 <5.1.0.14.2.20011004213749.02478cd0@dcrocker.net>		
	 <5.1.0.14.2.20011004235936.023e1500@dcrocker.net>	
	 <5.1.0.14.2.20011005141903.04649150@dcrocker.net>	
	 <3BBE467C.A9797B21@ehsco.com> <p0510033ab7e3fc24f02c@[165.227.249.20]>
	 <3BC25528.FC918BB4@ehsco.com> <p05100303b7e8186c0b81@[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 wrote:

[overlapping comments and non-responses eliminated]

> >    Let me restate this point, since it is somewhat complex. Although
> >    UDNS supports a dual-mode model, once UDNS (or something similar)
> >    were approved, developers could begin to work on applications
> >    which ONLY used UDNS, without any code for ASCII or ACE.
> 
> You are not talking about the UDNS that is before the WG. That
> protocol *requires* an ACE fallback.

The fallback mode also serves transitional purposes. After the majority of
queries start succeeding, only a minority of queries will fallback. After
a few more years, they all succeed, and there are no fallbacks. Dual-mode
facilitates transition.

> >  While this is technically not a
> >    "requirement" per se, the seamless user-driven transitional
> >    aspects should be requirements. Something very much like UDNS
> >    will be required for this. A "new naming service" is unlikely to
> >    reach critical mass without some kind of backwards compatibility,
> >    which UDNS provides.
> >
> >    Furthermore, the cost of UDNS is incremental to that of ACE,
> >    since they share many common features and functions. If a
> >    developer is going to add ACE support to an application (which
> >    they must do in the short term),
> 
> So, if you admit that here, why did you contradict it above?

There's no contradiction with UDNS providing ACE+UTF8 in the short term
and eventually turning into UTF-8 only.

> >This issue would have to be resolved if we were ever to move beyond
> >ACE. It is beneficial to design for such limits up front, rather than
> >revoking names later which will be incompatible. This is only a cost
> >if ACE and some other service are developed at different times, and is
> >NOT a cost if they are developed together. This is, in fact, a
> >motivating factor for beginning work on UDNS *NOW*.
> 
> Sorry, but I missed the part where you explain how to fix the
> problem. Without a fix, UDNS is dead in the water.

The "fix" that would be required is to define common maximum lengths. This
will be required in any event, and doing it up front makes most sense.

> >  > - UDNS requires more work to be done by authoritative DNS servers
> >
> >Yes, UDNS requires authoritative servers to maintain name mapping
> >information. However, I see this as being a transitional cost.
> 
> And you demand that all of the other people running name servers will
> agree with you.

Versus the ACE-only demand that every application support a secondary
encoding that isn't used anywhere else in the world. Forever.

> >  In the
> >beginning, few clients will support UDNS, but over the course of several
> >years, most clients will support UDNS. At some point (two decades out?
> >shorter?) it should be possible to switch entirely to UDNS, meaning that
> >there will no longer be a need for servers to store both versions. The
> >longer we delay beginning such a transition, the longer it will be before
> >we can complete that transition. If we never start it, we will never
> >complete it.
> 
> In other words, you don't think that making the com/net/org servers
> and the root servers do normalization and mapping is a problem. I
> take it you don't run any of those.

The com/net/org servers don't HAVE to do it. The question of whether or
not sufficient computing resources are available on the market to service
those zones is a question for those admins, not for you or me. I wouldn't
be shocked if it wasn't rolled out on those zones right away.

> >  > - UDNS UTF-8 queries that fail will cause more load on the DNS
> >
> >Yes, it will cause one additional lookup. This is equitable with requiring
> >one extra delegation server in the path. This is not a great cost to begin
> >with. Furthermore, seeing as how it is also transitional, it will only be
> >a cost for the short-term, and will not be a cost after a few years.
> 
> You blithely double the load on the DNS during the "transition". Nice.

It's only doubled if every lookup fails. Where would this load come from?
Are there going to be URLs with non-existent IDNs floating around that
users will always try to follow with their non-existing apps? Please.

Most of the early delegations will result in failed queries. Once
compliant apps were released and servers were deployed, less queries would
fail. Eventually the load will return to normal. At some point it shifts
from fallback-to-ACE to don't-fallback-it-worked, and that shouldn't be
impossibly far away.

The sooner it is started, the sooner we will finish, anyway. Better to do
it now than to do it 10 years from now when the loads are higher.

> >  > - Applications that implement the UTF-8 part of UDNS have to handle
> >>  the inevitable errors that come from queries that bounce, have to
> >>  recast those queries in ACE (assuming that the name is even legal in
> >>  ACE, which some won't be), and then have to emit those queries again,
> >>  causing more DNS traffic
> >
> >As with the other issues, this is a transitional cost which dissipates as
> >deployment goes up.
> 
> Wrong. It is with us as long as there are current applications running.

And they will always be with us in their current form if we go with
ACE-only. Do we really want to be designing for ARPANET forever? At what
point do we start thinking about laying the necessary groundwork for
migration to eight-bit technology?

> >  It is a cost in the beginning, but it is not a
> >significant cost after a few years.
> 
> First you said "twenty", now it's down to "a few". Some of us think
> there is a difference.

What I said was that ACE mode could be disabled in twenty years if not
sooner, when the transition is complete. Processing a "significant number"
of failovers should only be an issue for a few years, until the common
case is UTF-8 success. These are different scenarios and they have
different timetables.

> >  > - The errors caused by UTF-8 queries are the same as other legitimate
> >>  DNS errors, meaning that applications will have to have their own
> >>  (probably-nonstandard) logic for differentiating between expected
> >>  errors and real errors
> >
> >Because UDNS is an applicaton of EDNS, it uses the EDNS error codes. My
> >experience is that these codes are farily simple to work with.
> 
> You have misread UDNS, then. The query errors from un-upgraded
> servers will not be EDNS errors: they will be format errors from the
> current DNS.

No, they aren't different. The same errors that EDNS is intended to
trigger should be the errors which UDNS triggers. If this doesn't work
with UDNS, then it won't work with EDNS either.

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



From owner-idn@ops.ietf.org  Tue Oct  9 01:27:28 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA11409
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 01:27:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qpCZ-000PeM-00
	for idn-data@psg.com; Mon, 08 Oct 2001 22:13:11 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qpCY-000PeG-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 22:13:10 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id OAA08078;
	Tue, 9 Oct 2001 14:12:57 +0900
Message-ID: <00e601c15081$3a291a20$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se> <20011009004803.28618.qmail@cr.yp.to> <00b501c15078$afb77ce0$ec1bd9d2@temp> <20011009043734.15576.qmail@cr.yp.to>
Subject: Re: [idn] case preservation
Date: Tue, 9 Oct 2001 14:14:09 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id BAA11409


----- Original Message ----- 
From: "D. J. Bernstein" <djb@cr.yp.to>
To: <idn@ops.ietf.org>
Sent: Tuesday, October 09, 2001 1:37 PM
Subject: Re: [idn] case preservation


> Soobok Lee writes:
> > for example,  UN.org, WHO.org are much easier to recogize.
> 
> If you actually visit the UN and WHO web sites, you'll see that they
> consistently give their own DNs in lowercase: who.int, for example.

That does not fully reflect the preferences of the staffs and end users.
Uppercased ones help people to recogize them more fast.
WIPO always come with uppercase one in all newspapers ever i'd read.
It's very natural for applications 
to respect its uppercase forms that end users perfer and type in.
 
> 
> > prohibiting greek 'o' does not make sense
> 
> If someone is allowed to register aol.com with a Greek lowercase o, then
> nameprep is a bad joke.
> 

I heard that nameprep is for enforcing uniqueness, but only for
input convenience. There are so many equivlances that are too complex
to be solved in nameprep.
I hope you do not mix the case issue within a script block 
with look-alikeness issue across script blocks.

> ---Dan
> 




From owner-idn@ops.ietf.org  Tue Oct  9 01:45:09 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12323
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 01:45:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qpTD-0000VC-00
	for idn-data@psg.com; Mon, 08 Oct 2001 22:30:23 -0700
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qpTC-0000Uz-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 22:30:22 -0700
Received: from zetnet.co.uk (man-s367.dialup.zetnet.co.uk [194.247.45.238])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f995UDX30675
        for <idn@ops.ietf.org>; Tue, 9 Oct 2001 06:30:14 +0100
Message-ID: <3BC28B6A.D1F3331A@zetnet.co.uk>
Date: Tue, 09 Oct 2001 06:30:18 +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] WG Update
References: <20011008.112707.-940711.2.liana.ydisg@juno.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-----

liana.ydisg@juno.com wrote:
> If IDN is going to be universal to all devices, then a
> handheld device may have uppercase support for
> a sick user to have a familar reading quickly.  So
> I think your case preserving arguement should be
> considered.

That doesn't sound like a very strong argument for case preservation
to me. Suppose for the sake of argument that a user does find
uppercase characters easier to read [*]. In that case, all names should
be displayed as uppercase to that user, not just names that were
originally entered as uppercase. That could be done regardless of
whether the IDN proposal supports case preservation.


[*] Personally I find them less readable. Font size and style is much
    more important than 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

iQEVAwUBO8KKXTkCAxeYt5gVAQHIaAf+IXHT2LT9GSD0YuH4YP0xwBUwuNz0d0Vv
saVQvk92sE4msxxCTTxNC5F1PEATgVKr5sNES8s6BYC3MfhN0RKA75JdvMBHupIR
AhpDSQCPBnW8KzXS7e2BWBS9jsK6Cz2pkm1lVgBcvTXAozE4IWdQhLIugj79ADIE
fziL26m/AQZZmmGRJ269w44xmLN41uNTl4LPwXh864a2nIAH/dV86oSb2hzCBv5K
xmHnd6fQ2os3fTh3ycLFwDt6R/rU42XrbIippWfkIXoSFCEnJpwG6HmwS1TiHz7A
ujruLVnJwTFOiixEzBRfqUuWrDUM+SAT3U26cOTlMxfdZqZNgVvIlQ==
=Ws7+
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Tue Oct  9 01:45:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12384
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 01:45:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qpTx-0000Xw-00
	for idn-data@psg.com; Mon, 08 Oct 2001 22:31:09 -0700
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qpTv-0000Xq-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 22:31:08 -0700
Received: from zetnet.co.uk (man-s367.dialup.zetnet.co.uk [194.247.45.238])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f995V1X30975
        for <idn@ops.ietf.org>; Tue, 9 Oct 2001 06:31:01 +0100
Message-ID: <3BC28B99.E4E7CFB0@zetnet.co.uk>
Date: Tue, 09 Oct 2001 06:31: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: [idn] Overspecifications in draft-ietf-idn-requirements-08
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-----

The original (-08) document is quoted using '>', and my suggested changes
are quoted using '=>'.

> 6. A transfer encoding syntax (TES) is a reversible transform of encoded
>    data which may (or may not) include textual data represented in
>    one or more character encoding schemes. Examples: 8bit,
>    Quoted-Printable, BASE64, UTF-7 (defunct), UTF-5, and RACE.

This definition is never used.

> ... This document attempts to
> set requirements for an equivalent of the "used services" given above,
> where "hostname" is replaced by "Internationalized Domain Name". This
> does not preclude the fact that IDN should work with any kind of DNS
> queries. IDN is a new service. Since existing protocols like SMTP or
> HTTP use the old service, it is a matter of great concern how the new
> and old services work together, and how other protocols can take
> advantage of the new service.

IDN is not a new service; it makes more sense to consider it as an
extension of all the existing services. For example, in IDNA, the
existing IP-to-hostname service can return an (ACE-encoded) IDN, or a
non-IDN query can follow a DNAME record that points to an IDN. These
cases wouldn't be possible if IDN was a separate service.

=> ... This document attempts to
=> set requirements for extensions of the "used services" given above,
=> where "hostname" is replaced by "Internationalized Domain Name".
=> That is, IDN should work with any kind of DNS queries. Since we are
=> extending services used by existing protocols like SMTP or HTTP,
=> compatibility with these existing uses is a matter of great concern,
=> as well as how both new and old protocols can take advantage of the
=> new facilities.


> 2. General Requirements
> 
> These requirements address two concerns: The service offered to the
> users (the application service), and the protocol extensions, if needed,
> added to support this service.
> 
> In the requirements, we attempt to use the term "service" whenever a
> requirement concerns the service, and "protocol" whenever a requirement
> is believed to constrain the possible implementation.

What we are setting requirements for are IDN proposals. Some (not all)
of the cases where "service" or "protocol" is used should actually say
"proposal", IMHO. I've made those changes below without further comment.


> [1] The DNS is essential to the entire Internet. Therefore, the service
> MUST NOT damage present DNS protocol interoperability. It MUST make the
> minimum number of changes to existing protocols on all layers of the
> stack.

Requiring the "minimum number of changes" fails to consider the cost
or feasibility of any change; it is requiring an absolute, which is
always a bad idea.

I.e. if proposal B needs protocol changes in addition to those of proposal
A, then no matter how insignificant the cost of those changes are, or what
other advantages B has, this requirement would eliminate B. The effect is
that minimising protocol changes overrides every other consideration.

> It MUST continue to allow any system anywhere that implements
> the IDN specification to resolve any internationalized domain name.

"continue to" should be deleted. Obviously no system can resolve an IDN
at the moment.

=> [1] The DNS is essential to the entire Internet. Therefore, the proposal
=> MUST NOT damage present DNS protocol interoperability. It MUST allow any
=> system anywhere that implements the IDN specification to resolve any
=> internationalized domain name. The overall cost and feasibility of
=> changes to existing protocols, on all layers of the stack, is of great
=> importance when evaluating any IDN proposal.


> [3] The DNS protocol (the packet formats that go on the wire) MUST
> NOT limit the codepoints that can be used. A service defined on top of
> the DNS, for instance the IDN-to-address function, MAY limit the
> codepoints that can be used. The service descriptions MUST describe
> what limitations are imposed.

The packet formats that go on the wire use octet strings, not strings
of codepoints. In order to maintain compatibility with the requirements
of RFC 2181, it is the set of octet strings that must not be limited.

Also, there may be other restrictions on host names besides the set of
allowed codepoints (for example relating to mixing of left-to-right and
right-to-left scripts, or names that start with an ACE prefix).

=> [3] The DNS protocol (the packet formats that go on the wire) MUST
=> NOT limit, apart from in length, the set of octet strings that can be
=> used as an encoded domain name. A service defined on top of the DNS,
=> for instance the IDN-to-address function, MUST define a mapping between
=> host name strings and these octet string encodings, and MAY impose
=> limitations on host names, for example by restricting the set of
=> allowed codepoints. The service descriptions MUST describe what
=> limitations are imposed.


> [4] The protocol MUST work for all features of DNS, IPv4, and
> IPv6. The protocol MUST NOT allow an IDN to be returned to a requestor
> that requests the IP-to-(old)-domain-name mapping service.

This is unclear. Returning an ACE name to an "old" requestor will
clearly not break anything, and an ACE name is an (encoded) IDN. It also
doesn't take into account that some resolver interfaces are already
Unicode-aware, in which case they would not require any distinction
between old and new requests (this is true for InetAddress.getHostName
in the Java API, for example, or for getipnodebyaddr, etc. in Plan-9).

=> [4] The proposal MUST work for all features of DNS, IPv4, and IPv6.
=> The proposal MUST ensure that the responses to requests for an IP
=> to domain name mapping will not break existing requestors.


> [5] The same name resolution request MUST generate the same response,
> regardless of the location or localization settings in the resolver, in
> the master server, and in any slave servers involved in the resolution
> process.

This is also unclear (with respect to the resolver; I agree about the
rest). Surely it wasn't meant to prohibit any use of locale information
in defining the API to the resolver?

=> [5] The same name resolution request MUST generate the same response,
=> regardless of the location or localization settings in the master
=> server, or in any slave servers involved in the resolution process.
=> Any description of functionality required of a resolver API MUST
=> discuss any dependency of the API on localization settings in the
=> client.


> [8] The service MAY modify the DNS protocol RFC 1035 and other related
> work undertaken by the DNSEXT WG. However, these changes SHOULD be as
> small as possible and any changes SHOULD be coordinated with the
> DNSEXT WG.

"As small as possible" is too strong - it is possible to support IDNs
without changing the DNS/DNSEXT protocol at all, and so this is equivalent
to "the DNS/DNSEXT protocol SHOULD NOT be changed". Nevertheless, changing
it may have advantages.

=> [8] The proposal MAY modify the DNS protocol RFC 1035 and other related
=> work undertaken by the DNSEXT WG. However, any such changes SHOULD be as
=> small as needed to support the basic design of the proposal, and SHOULD
=> be coordinated with the DNSEXT WG.


> [9] The protocol supporting the service SHOULD be as simple as possible
> from the user's perspective. Ideally, users SHOULD NOT realize that IDN
> was added on to the existing DNS.

A better way of expressing this is

=> [9] The user's perspective of each service SHOULD be as simple as can
=> be practically achieved. Ideally, users will find the services no more
=> difficult to use than if internationalised names had always been
=> supported by the DNS.


> [11] The protocol should handle with care new revisions of the CCS.
> Undefined codepoints should not be allowed unless a new revision of
> the protocol can handle it. Protocol revisions should be tagged.

The current version of nameprep allows unassigned code points in queries
without revision tagging, for good reasons.

=> [11] The proposal should handle with care new revisions of the CCS.
=> Proposals MUST discuss how undefined codepoints are handled.


> [12] Internationalized characters MUST be allowed to be represented and
> used in DNS names and records. The protocol MUST specify what charset is
> used when resolving domain names and how characters are encoded in DNS
> records.

Note that "charset" usually means a MIME-registered charset, which is
not necessarily the case here (for example when the encoding is ACE, or
when more than one possible encoding is allowed - see [18] below).

In fact the modified version of [3] above requires the mapping between
host names and the octet strings used on the wire to be specified (and
in any case, not doing this would be a violation of BCP 18), so the
second sentence is now redundant.

=> [12] Internationalized characters MUST be allowed to be represented and
=> used in DNS names and records.


[14], [15], [16], [17]: protocol -> proposal.


> [18] While there are a wide range of devices that use the DNS and a
> wide range of characteristics of international scripts and methods of
> domain name input and display, IDN is only concerned with the
> protocol. Therefore, there MUST be a single way of encoding an
> internationalized domain name within the DNS.

No, there does not need to be a single way of encoding an IDN (there is
not even for pure ASCII names, because equivalent names that differ in
case are allowed in the DNS protocol). For example, a solution where
names on the wire can be either ACE or UTF-8 will work perfectly well.
The wire encoding isn't even directly visible to users or applications,
so I don't see why the requirements document should be saying anything
about it.

If the intention was to refer to the external representation of a name,
rather than the wire encoding, that would prohibit any solution that
involves a transition from ACE to transparent names, or simultaneous use
of ACE and transparent names. Either way, this requirement is unnecessary
and should be deleted.


> [19] To achieve interoperability, canonicalization MUST be done at a
> single well-defined place in the DNS resolution process. The protocol
> MUST specify canonicalization; it MUST specify exactly where in the
> DNS that canonicalization happens and does not happen; it MUST specify
> how additions to ISO 10646 will affect the stability of the DNS and
> the amount of work done on the root DNS servers.

The overspecification here is "at a *single* ... place". For example,
if canonicalization is specified by nameprep, it is idempotent, i.e.
nameprep(nameprep(x)) = x. So doing it more than once only hurts
efficiency, not interoperability or any other requirement. It doesn't
even hurt efficiency very much, since the common case where a name is
already in the correct form can be optimised.

> ... The protocol MUST specify canonicalization; ...

This is meaningless without specifying what the goal of canonicalization
is. The minimum requirement is to ensure that characters that are
indistinguishable to users are treated the same, and so that is what
should be stated:

=> [19] Characters that appear absolutely indistinguishable to users
=> MUST be canonicalized. To achieve interoperability, canonicalization
=> MUST be done at a well-defined place or places in the DNS resolution
=> process, i.e. the proposal MUST specify exactly where in the DNS
=> canonicalization can and cannot happen.

[I changed "happens and does not happen" to "can and cannot happen",
because whether a particular piece of the infrastructure actually does
canonicalization will depend on which pieces have been upgraded. If they
haven't been upgraded, then they obviously won't do canonicalization,
regardless of whether the IDN proposal says that they should.
Note that this is a potential motivation for a proposal to specify that
canonicalization may be done in more than one place.]


> [23] If other canonicalization is done, it MUST be done before the
> domain name is resolved.

It makes perfect sense to do canonicalization as part of resolution, not
before it. Also, canonicalizing after resolution is certainly feasible,
even if it is inefficient.

> ... Further, the canonicalization MUST be easily
> upgradable as new languages and writing systems are added.

It *will not* be easy to upgrade canonicalization, no matter where or how
it is done, because the incentive to upgrade to support scripts that most
people will consider completely obscure, is much less than the incentive
to get IDN support working the first time round.

=> [23] Consideration MUST be given to the ease of upgrading
=> canonicalization as new languages and writing systems are added.
=> As long as a name containing new characters has been canonicalized
=> according to the latest canonicalization version, resolving that name
=> MUST NOT depend on further upgrades to the resolver or DNS servers.


> [25] If the charset can be normalized, then it SHOULD be normalized
> before it is used in IDN. Normalization SHOULD follow Unicode
> Technical Report #15.

Although this describes a perfectly reasonable approach, it does not
belong in a requirements document. [26] already captures part of the
requirement ("The protocol SHOULD avoid inventing a new normalization
form provided a technically sufficient one is available."), and the
modified [19] above captures the rest. So, delete this requirement.


[29]: service -> proposal.
[30]: protocol -> proposal.


> 3. Security Considerations
> 
> Any solution that meets the requirements in this document MUST NOT be
> less secure than the current DNS.

That is not necessarily achievable. The main issue is name spoofing using
look-alike characters: even if a proposal specifically tries to address
that (by registration procedures, for example), it can't absolutely
guarantee that there will not be cases of this that rely on IDNs.

> Specifically, the mapping of
> internationalized host names to and from IP addresses MUST have the
> same characteristics as the mapping of today's host names.
> 
> Specifying requirements for internationalized domain names does not
> itself raise any new security issues. However, any change to the DNS MAY
> affect the security of any protocol that relies on the DNS or on
> DNS names. A thorough evaluation of those protocols for security
> concerns will be needed when they are developed.

That evaluation is needed for existing protocols, not just new protocols.

- -- 
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

iQEVAwUBO8KFlzkCAxeYt5gVAQEafAf/R+2BDy2pOLoJ5ONBuatbYTzM9/qguLij
EUSBoMwpsjg5Sbzb9brrdgNH1sfeCKLaZn1Hzd/k5Swky5JdgyVGIpyHvUkacXYY
WXf/hrmQGwM/TTDCSnX2wfTPx3ij+QnSAoxgFODI++QKk8MbVkLe+PvbmdG4gjdt
N4EysjWJuq2KLV8qZJBVrmDEwDlTT/+AqwRYoEvYLydIChpdut369s3kTOI0ZOHd
mw/KGU6ZOs83/NFc7sKhtu13fYtFVYyV0uVU7R639U4QV+/00LYb7sTpALjTwcBz
0RIdTHATp1MbxLLR7cMLf4PjePB3Mzt1dZB1s+CLph4R/2OjEIbd+w==
=r5Gk
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Tue Oct  9 02:04:04 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17836
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 02:04:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qpqf-0001dB-00
	for idn-data@psg.com; Mon, 08 Oct 2001 22:54:37 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qpqe-0001d5-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 22:54:36 -0700
Received: from [192.168.1.5] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id HAA14503
	for <idn@ops.ietf.org>; Tue, 9 Oct 2001 07:54:33 +0200 (MET DST)
Date: Tue, 09 Oct 2001 07:54:20 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: idn@ops.ietf.org
Subject: Re: [idn] case preservation
Message-ID: <58648759.1002614060@localhost>
In-Reply-To: <20011009043734.15576.qmail@cr.yp.to>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se>
 <20011009004803.28618.qmail@cr.yp.to> <00b501c15078$afb77ce0$ec1bd9d2@temp>
 <20011009043734.15576.qmail@cr.yp.to>
X-Mailer: Mulberry/2.1.0 (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-10-09 04.37 +0000 "D. J. Bernstein" <djb@cr.yp.to> wrote:

>> prohibiting greek 'o' does not make sense
> 
> If someone is allowed to register aol.com with a Greek lowercase o, then
> nameprep is a bad joke.

Already today, people can register domainnames with characters which look
"similar" like 'o' and 0, or '1' and 'l'. I.e. this is not a new problem.
It is well-known for the people which work with domain name dispute
resolution.

Further, this wg has chosen to use the Unicode Character Set and
Normalization according to UTC TR#15, normalization form KC. If you are
unhappy with how individual characters are normalized, please to go the
Unicode Consortium after reading the criteria for the normalization process
chosen.

If you are unhappy with the choice of refering to the work in the Unicode
Consortium, that is a valid concern, but should have been brought up some
1.5-2 years ago.

That horse is already dead.

   paf




From owner-idn@ops.ietf.org  Tue Oct  9 02:51:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24314
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 02:51:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qqYr-0003fL-00
	for idn-data@psg.com; Mon, 08 Oct 2001 23:40:17 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qqYq-0003fF-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 23:40:17 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id PAA02807;
	Tue, 9 Oct 2001 15:39:58 +0900
Message-ID: <011f01c1508d$624144e0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>, <idn@ops.ietf.org>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se> <20011009004803.28618.qmail@cr.yp.to> <00b501c15078$afb77ce0$ec1bd9d2@temp> <20011009043734.15576.qmail@cr.yp.to> <58648759.1002614060@localhost>
Subject: Re: [idn] case preservation
Date: Tue, 9 Oct 2001 15:41:10 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id CAA24314


----- Original Message ----- 
From: "Patrik Fältström" <paf@cisco.com>
To: <idn@ops.ietf.org>
Sent: Tuesday, October 09, 2001 2:54 PM
Subject: Re: [idn] case preservation


> --On 01-10-09 04.37 +0000 "D. J. Bernstein" <djb@cr.yp.to> wrote:
> 
> >> prohibiting greek 'o' does not make sense
> > 
> > If someone is allowed to register aol.com with a Greek lowercase o, then
> > nameprep is a bad joke.
> 
> Already today, people can register domainnames with characters which look
> "similar" like 'o' and 0, or '1' and 'l'. I.e. this is not a new problem.
> It is well-known for the people which work with domain name dispute
> resolution.
> 
But, the real problem lies in the increased number of such ambiguities.
For LDH domains, we need to know about only 'O','o','1','l' .
But for IDN, almost _ALL_ of 'a' ~ 'z' have their look-alike characters in
greek,cyrillic and cherokee script. Seeing them printed  on papers,
most people can't know whether they are LDH domains or IDN ones.

ICANN/DNSO/ccSO should make some recommendations/enforcement 
on IDN registration and dispute resolution policies 
before IDN's being deployed and owned.

Soobok Lee


> Further, this wg has chosen to use the Unicode Character Set and
> Normalization according to UTC TR#15, normalization form KC. If you are
> unhappy with how individual characters are normalized, please to go the
> Unicode Consortium after reading the criteria for the normalization process
> chosen.
> 
> If you are unhappy with the choice of refering to the work in the Unicode
> Consortium, that is a valid concern, but should have been brought up some
> 1.5-2 years ago.
> 
> That horse is already dead.
> 
>    paf
> 
> 




From owner-idn@ops.ietf.org  Tue Oct  9 03:01:30 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24993
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 03:01:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qqki-0004Cc-00
	for idn-data@psg.com; Mon, 08 Oct 2001 23:52:32 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qqkd-0004CQ-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 23:52:30 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id BFA02FFC0F; Tue,  9 Oct 2001 14:52:50 +0800 (SGT)
Message-ID: <052501c1508e$ecae7980$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>,
        =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        <idn@ops.ietf.org>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se> <20011009004803.28618.qmail@cr.yp.to> <00b501c15078$afb77ce0$ec1bd9d2@temp> <20011009043734.15576.qmail@cr.yp.to> <58648759.1002614060@localhost> <011f01c1508d$624144e0$ec1bd9d2@temp>
Subject: Re: [idn] case preservation
Date: Tue, 9 Oct 2001 14:52:12 +0800
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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Okay, wrong forum then. You should bring this to ICANN/DNSO/ccSO on
this, not IDN WG.

-James Seng

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Patrik Fältström" <paf@cisco.com>; <idn@ops.ietf.org>
Sent: Tuesday, October 09, 2001 2:41 PM
Subject: Re: [idn] case preservation

But, the real problem lies in the increased number of such ambiguities.
For LDH domains, we need to know about only 'O','o','1','l' .
But for IDN, almost _ALL_ of 'a' ~ 'z' have their look-alike characters
in
greek,cyrillic and cherokee script. Seeing them printed  on papers,
most people can't know whether they are LDH domains or IDN ones.

ICANN/DNSO/ccSO should make some recommendations/enforcement
on IDN registration and dispute resolution policies
before IDN's being deployed and owned.

Soobok Lee


> Further, this wg has chosen to use the Unicode Character Set and
> Normalization according to UTC TR#15, normalization form KC. If you
are
> unhappy with how individual characters are normalized, please to go
the
> Unicode Consortium after reading the criteria for the normalization
process
> chosen.
>
> If you are unhappy with the choice of refering to the work in the
Unicode
> Consortium, that is a valid concern, but should have been brought up
some
> 1.5-2 years ago.
>
> That horse is already dead.
>
>    paf
>
>






From owner-idn@ops.ietf.org  Tue Oct  9 03:02:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25116
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 03:02:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qqjI-00049J-00
	for idn-data@psg.com; Mon, 08 Oct 2001 23:51:04 -0700
Received: from koobera.math.uic.edu ([131.193.178.181] helo=muncher.math.uic.edu)
	by psg.com with smtp (Exim 3.33 #1)
	id 15qqjI-000499-00
	for idn@ops.ietf.org; Mon, 08 Oct 2001 23:51:04 -0700
Received: (qmail 16389 invoked by uid 1001); 9 Oct 2001 06:51:20 -0000
Date: 9 Oct 2001 06:51:20 -0000
Message-ID: <20011009065120.28737.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] case preservation
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se> <20011009004803.28618.qmail@cr.yp.to> <00b501c15078$afb77ce0$ec1bd9d2@temp> <20011009043734.15576.qmail@cr.yp.to> <58648759.1002614060@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:
> characters which look "similar" like 'o' and 0, or '1' and 'l'

I am not talking about the momentary confusion between ao1.com and
aol.com. I am not talking about characters that merely look ``similar.'' 
I am talking about characters whose standard glyphs are IDENTICAL.

A properly typeset uppercase Alpha is IDENTICAL to a properly typeset
uppercase A, just as a properly typeset tab is IDENTICAL to a properly
typeset sequence of spaces. It is simply NOT POSSIBLE to tell the
difference between AOL.com and AOL.com.

This does not mean that Alpha and A are the same character, or that tab
and space are the same character. It does mean, however, that you've
done a half-assed job with the current version of nameprep.

If you're not going to do a thorough job of nameprep, then you shouldn't
be trying to deceive users into believing that IDNs can be safely typed
from textual printouts. It would be better to omit nameprep entirely;
then users will stick to mechanisms that work, such as clicking on URLs.
(Bad characters should still be avoided in registrations, of course.)

---Dan



From owner-idn@ops.ietf.org  Tue Oct  9 03:25:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25588
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 03:25:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qr6W-0005Yl-00
	for idn-data@psg.com; Tue, 09 Oct 2001 00:15:04 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qr6V-0005Yf-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 00:15:04 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id QAA13658;
	Tue, 9 Oct 2001 16:14:42 +0900
Message-ID: <014c01c15092$3cdb0b00$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se> <20011009004803.28618.qmail@cr.yp.to> <00b501c15078$afb77ce0$ec1bd9d2@temp> <20011009043734.15576.qmail@cr.yp.to> <58648759.1002614060@localhost> <20011009065120.28737.qmail@cr.yp.to>
Subject: Re: [idn] case preservation
Date: Tue, 9 Oct 2001 16:15:55 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id DAA25588


----- Original Message ----- 
From: "D. J. Bernstein" <djb@cr.yp.to>
To: <idn@ops.ietf.org>
Sent: Tuesday, October 09, 2001 3:51 PM
Subject: Re: [idn] case preservation


> Patrik writes:
> > characters which look "similar" like 'o' and 0, or '1' and 'l'
> 
> I am not talking about the momentary confusion between ao1.com and
> aol.com. I am not talking about characters that merely look ``similar.'' 
> I am talking about characters whose standard glyphs are IDENTICAL.
> 
> A properly typeset uppercase Alpha is IDENTICAL to a properly typeset
> uppercase A, just as a properly typeset tab is IDENTICAL to a properly
> typeset sequence of spaces. It is simply NOT POSSIBLE to tell the
> difference between AOL.com and AOL.com.
> 
> This does not mean that Alpha and A are the same character, or that tab
> and space are the same character. It does mean, however, that you've
> done a half-assed job with the current version of nameprep.
> 
> If you're not going to do a thorough job of nameprep, then you shouldn't
> be trying to deceive users into believing that IDNs can be safely typed
> from textual printouts. 

Recent Nameprep revision already contains one statement for caution
wrt similarly-looking characters it don't solve.

>It would be better to omit nameprep entirely;

nameprep is not mature but _useful_ for input convenience even with its inability to solve look-alike problems. 


> then users will stick to mechanisms that work, such as clicking on URLs.
> (Bad characters should still be avoided in registrations, of course.)
> 
> ---Dan
> 




From owner-idn@ops.ietf.org  Tue Oct  9 04:13:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25925
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 04:13:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qrpz-0007cG-00
	for idn-data@psg.com; Tue, 09 Oct 2001 01:02:03 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qrpy-0007cA-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 01:02:02 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VVmUlzGBPWYfy7Vkiws97Dug==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GHAWQ78E; Tue, 09 Oct 2001 04:01:23 EDT
To: david.hopwood@zetnet.co.uk
Cc: idn@ops.ietf.org
Date: Tue, 9 Oct 2001 01:21:39 -0700
Subject: Re: [idn] WG Update
Message-ID: <20011009.012141.-723299.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-20,22-47
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

Case preserving has been there, and it is nice 
for people who wants to support it.  To make it 
a requirement will ensure a uniform support, 
and ensure a clear path for mixed use of 
scripts and CJK character recovery cross all 
types of devices, which adds more software work 
but benefit a general public on a long run.  Given 
this does not effect DNS structurally,  I don't see 
why we can not make it a requirement. 

If you only think in terms of all Latin upper case, it 
may not make that much a difference.  If you think 
SomethingLikeThis.com it does make a lot of 
difference, since we don't have that white space 
already.  When we speak about CJK characters,
people can tell some Kanji from Han in an 
equivalent CJK set. 

Liana


On Tue, 09 Oct 2001 06:30:18 +0100 David Hopwood
<david.hopwood@zetnet.co.uk> writes:
> -----BEGIN PGP SIGNED MESSAGE-----
> 
> liana.ydisg@juno.com wrote:
> > If IDN is going to be universal to all devices, then a
> > handheld device may have uppercase support for
> > a sick user to have a familar reading quickly.  So
> > I think your case preserving arguement should be
> > considered.
> 
> That doesn't sound like a very strong argument for case preservation
> to me. Suppose for the sake of argument that a user does find
> uppercase characters easier to read [*]. In that case, all names 
> should
> be displayed as uppercase to that user, not just names that were
> originally entered as uppercase. That could be done regardless of
> whether the IDN proposal supports case preservation.
> 
> 
> [*] Personally I find them less readable. Font size and style is 
> much
>     more important than case.
> 
> - -- 
> David Hopwood <david.hopwood@zetnet.co.uk>
> 



From owner-idn@ops.ietf.org  Tue Oct  9 04:40:49 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26046
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 04:40:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qsH8-0008tp-00
	for idn-data@psg.com; Tue, 09 Oct 2001 01:30:06 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qsH7-0008th-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 01:30:05 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id RAA04686;
	Tue, 9 Oct 2001 17:29:48 +0900
Message-ID: <019e01c1509c$bb7ff510$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se> <20011009004803.28618.qmail@cr.yp.to> <00b501c15078$afb77ce0$ec1bd9d2@temp> <20011009043734.15576.qmail@cr.yp.to> <58648759.1002614060@localhost> <011f01c1508d$624144e0$ec1bd9d2@temp> <052501c1508e$ecae7980$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] case preservation
Date: Tue, 9 Oct 2001 17:31:00 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id EAA26046


----- Original Message ----- 
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>; "Patrik Fältström" <paf@cisco.com>; <idn@ops.ietf.org>
Sent: Tuesday, October 09, 2001 3:52 PM
Subject: Re: [idn] case preservation


> Okay, wrong forum then. You should bring this to ICANN/DNSO/ccSO on
> this, not IDN WG.

Partly No. The problem has some aspects that lies between IETF and ICANN.
For example, some equilvalences are now being solved by NFKC,
while others are not  only because UTC has no standard for them NOW.
Therefore, human interventions on them and its social/financial overheads
are inevitable. Explanation and justification for that cannot be done 
only in ICANN . IDN WG should provide some techinical rationale for
them and that's what i have concerns about. What if some ICANN members
ask back  "why didn't you solve that problem ?". This WG has been  for
about 2 years.

I got an impression that you says " we IETFer's are never responsible for that issues!". I hope my impression was  false.

Soobok

> 
> -James Seng
> 
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: "Patrik Fältström" <paf@cisco.com>; <idn@ops.ietf.org>
> Sent: Tuesday, October 09, 2001 2:41 PM
> Subject: Re: [idn] case preservation
> 
> But, the real problem lies in the increased number of such ambiguities.
> For LDH domains, we need to know about only 'O','o','1','l' .
> But for IDN, almost _ALL_ of 'a' ~ 'z' have their look-alike characters
> in
> greek,cyrillic and cherokee script. Seeing them printed  on papers,
> most people can't know whether they are LDH domains or IDN ones.
> 
> ICANN/DNSO/ccSO should make some recommendations/enforcement
> on IDN registration and dispute resolution policies
> before IDN's being deployed and owned.
> 
> Soobok Lee
> 
> 
> > Further, this wg has chosen to use the Unicode Character Set and
> > Normalization according to UTC TR#15, normalization form KC. If you
> are
> > unhappy with how individual characters are normalized, please to go
> the
> > Unicode Consortium after reading the criteria for the normalization
> process
> > chosen.
> >
> > If you are unhappy with the choice of refering to the work in the
> Unicode
> > Consortium, that is a valid concern, but should have been brought up
> some
> > 1.5-2 years ago.
> >
> > That horse is already dead.
> >
> >    paf
> >
> >
> 
> 
> 
> 




From owner-idn@ops.ietf.org  Tue Oct  9 05:28:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26277
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 05:28:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qsyp-000Aub-00
	for idn-data@psg.com; Tue, 09 Oct 2001 02:15:15 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qsym-000AuV-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 02:15:13 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id E3466FFC08; Tue,  9 Oct 2001 17:15:37 +0800 (SGT)
Message-ID: <063401c150a2$dee44370$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se> <20011009004803.28618.qmail@cr.yp.to> <00b501c15078$afb77ce0$ec1bd9d2@temp> <20011009043734.15576.qmail@cr.yp.to> <58648759.1002614060@localhost> <011f01c1508d$624144e0$ec1bd9d2@temp> <052501c1508e$ecae7980$dd00a8c0@jamessonyvaio> <019e01c1509c$bb7ff510$ec1bd9d2@temp>
Subject: Re: [idn] case preservation
Date: Tue, 9 Oct 2001 17:14:58 +0800
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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

I agree with your assessment that it maybe appropriate for this wg to
publish a document on the shortfalls of the work we doing. perhaps this
document could contain information on operational issues & localization
consideration etc for domain names holder, zone administrator,
registries etc. This idea have been bouncing around for a while but it
is more important for someone to pick this up and write a draft on it.
(You will have my support in my personal capacity :-)

However, do take note that it is inappropriate for this wg to instruct
ICANN on the deployment of IDN or write a document for their
education/purpose.

"The group will not address the question of what, if any, body should
administer or control usage of names that use this functionality"

-James Seng

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>; <idn@ops.ietf.org>
Sent: Tuesday, October 09, 2001 4:31 PM
Subject: Re: [idn] case preservation



----- Original Message -----
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>; "Patrik Fältström" <paf@cisco.com>;
<idn@ops.ietf.org>
Sent: Tuesday, October 09, 2001 3:52 PM
Subject: Re: [idn] case preservation


> Okay, wrong forum then. You should bring this to ICANN/DNSO/ccSO on
> this, not IDN WG.

Partly No. The problem has some aspects that lies between IETF and
ICANN.
For example, some equilvalences are now being solved by NFKC,
while others are not  only because UTC has no standard for them NOW.
Therefore, human interventions on them and its social/financial
overheads
are inevitable. Explanation and justification for that cannot be done
only in ICANN . IDN WG should provide some techinical rationale for
them and that's what i have concerns about. What if some ICANN members
ask back  "why didn't you solve that problem ?". This WG has been  for
about 2 years.

I got an impression that you says " we IETFer's are never responsible
for that issues!". I hope my impression was  false.

Soobok

>
> -James Seng
>
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: "Patrik Fältström" <paf@cisco.com>; <idn@ops.ietf.org>
> Sent: Tuesday, October 09, 2001 2:41 PM
> Subject: Re: [idn] case preservation
>
> But, the real problem lies in the increased number of such
ambiguities.
> For LDH domains, we need to know about only 'O','o','1','l' .
> But for IDN, almost _ALL_ of 'a' ~ 'z' have their look-alike
characters
> in
> greek,cyrillic and cherokee script. Seeing them printed  on papers,
> most people can't know whether they are LDH domains or IDN ones.
>
> ICANN/DNSO/ccSO should make some recommendations/enforcement
> on IDN registration and dispute resolution policies
> before IDN's being deployed and owned.
>
> Soobok Lee
>
>
> > Further, this wg has chosen to use the Unicode Character Set and
> > Normalization according to UTC TR#15, normalization form KC. If you
> are
> > unhappy with how individual characters are normalized, please to go
> the
> > Unicode Consortium after reading the criteria for the normalization
> process
> > chosen.
> >
> > If you are unhappy with the choice of refering to the work in the
> Unicode
> > Consortium, that is a valid concern, but should have been brought up
> some
> > 1.5-2 years ago.
> >
> > That horse is already dead.
> >
> >    paf
> >
> >
>
>
>
>






From owner-idn@ops.ietf.org  Tue Oct  9 05:28:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26293
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 05:28:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qt2p-000B6x-00
	for idn-data@psg.com; Tue, 09 Oct 2001 02:19:23 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qt2o-000B6d-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 02:19:22 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 862C17F437; Tue,  9 Oct 2001 18:18:52 +0900 (JST)
Message-Id: <4.2.0.58.J.20011005145034.03152170@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 09 Oct 2001 18:05:25 +0900
To: Dave Crocker <dhc@dcrocker.net>, "D. J. Bernstein" <djb@cr.yp.to>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] 7CE
Cc: idn@ops.ietf.org
In-Reply-To: <5.1.0.14.2.20011004092041.03a887f8@dcrocker.net>
References: <20011004152630.20354.qmail@cr.yp.to>
 <20011003.125229.-816135.0.liana.ydisg@juno.com>
 <01a901c14c77$f393bf50$dd00a8c0@jamessonyvaio>
 <004c01c14c90$3748bd00$d43f7018@mtag1.on.home.com>
 <001001c14cd9$31dd85a0$d43f7018@mtag1.on.home.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 09:22 01/10/04 -0700, Dave Crocker wrote:
>At 08:26 AM 10/4/2001, D. J. Bernstein wrote:
>>The correct phrase is ``7-bit compatible.'' The encoded strings are
>>compatible with 7-bit channels. That's the point of these encodings.
>
>30 years of consistent use tends to carry more weight than a single 
>person's recent desire to impose linguistic changes.

Hello Dave,

I think Dan has a certain point in making a difference between
ASCII-compatible and 7-bit compatible, or between characters and
bytes in general. Even 30 years of continued (not consistent)
use doesn't change the fact that they are not the same, and
doesn't help internationalization.


>And it is difficult to imagine how this line of discussion is in any way 
>seriously helpful to the IDN working group reaching closure.

I think it might help quite a few people who don't really
like ACE to know that the (key) ACE proponents understand
that ACE is a layer violation in the (character) encoding
stack, and will have its serious negative consequences like
any other layer violation. At least it would help me.


Regards,    Martin.




From owner-idn@ops.ietf.org  Tue Oct  9 05:29:20 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26309
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 05:29:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qt2k-000B6l-00
	for idn-data@psg.com; Tue, 09 Oct 2001 02:19:18 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qt2k-000B6f-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 02:19:18 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 0558E7F45B; Tue,  9 Oct 2001 18:18:56 +0900 (JST)
Message-Id: <4.2.0.58.J.20011009175309.03cb5c40@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 09 Oct 2001 17:55:33 +0900
To: "Tim Langdell" <tim@xtns.net>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Re: NN%<-->UTF8
In-Reply-To: <038a01c15027$cc27edc0$0200a8c0@Magnus>
References: <20011008.112707.-940711.2.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

Hello Tim,

At 11:33 01/10/08 -0700, Tim Langdell wrote:
>Does anyone please have a link to a good conversion routine for NN% to and
>from UTF8 for URI transport? Perl script would be good ...

You probably mean the %HH convention used in URIs?
Converting from UTF-8 to %HH is rather easy; I can write
that code in Perl if you can use it (I should write it
anyway as an example).
Converting from %HH to UTF-8 is not as easy, unless you
know that the %HHs you are dealing with indeed came from
a decent string (e.g. no controls,...) decently encoded
in UTF-8.

Regards,   Martin.





From owner-idn@ops.ietf.org  Tue Oct  9 05:32:32 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26341
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 05:32:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qt2p-000B6y-00
	for idn-data@psg.com; Tue, 09 Oct 2001 02:19:23 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qt2o-000B6e-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 02:19:22 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 9425A7F457; Tue,  9 Oct 2001 18:18:54 +0900 (JST)
Message-Id: <4.2.0.58.J.20011009174223.03c9e400@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 09 Oct 2001 17:51:56 +0900
To: "D. J. Bernstein" <djb@cr.yp.to>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] case preservation
In-Reply-To: <20011009065120.28737.qmail@cr.yp.to>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se>
 <20011009004803.28618.qmail@cr.yp.to>
 <00b501c15078$afb77ce0$ec1bd9d2@temp>
 <20011009043734.15576.qmail@cr.yp.to>
 <58648759.1002614060@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 06:51 01/10/09 +0000, D. J. Bernstein wrote:
>If you're not going to do a thorough job of nameprep, then you shouldn't
>be trying to deceive users into believing that IDNs can be safely typed
>from textual printouts.

I think it was never a goal to have mixed-script names
(e.g. <A-Greek><O-Cyrillic><L-Latin>) to be easy to type.
The main problem in such cases for actual input is that
you have to switch (software) keyboards, even if it is
very clear which script the character comes from.
There was never even a goal to fully support completely
mixed-script labels, because they don't really make sense.
However, because names e.g. of the form latin-greek
could make sense, mixed-script labels as such were
included in the requirements.


>It would be better to omit nameprep entirely;
>then users will stick to mechanisms that work, such as clicking on URLs.
>(Bad characters should still be avoided in registrations, of course.)

Bad character combinations should be avoided with registration.
The only registrations for things like <A-Greek><O-Cyrillic><L-Latin>
will come from spoofers, and the only way such spoofers have
a chance is through clicking on URIs or a similar interface.


Regards,    Martin.



From owner-idn@ops.ietf.org  Tue Oct  9 05:42:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26396
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 05:42:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qtDF-000Bge-00
	for idn-data@psg.com; Tue, 09 Oct 2001 02:30:09 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qtDD-000BgW-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 02:30:07 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP id C621DFFC01
	for <idn@ops.ietf.org>; Tue,  9 Oct 2001 17:30:40 +0800 (SGT)
Message-ID: <065601c150a4$f907ef70$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <idn@ops.ietf.org>
Subject: [idn] core interest of the wg
Date: Tue, 9 Oct 2001 17:30:02 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

UDNS & UNAME have been removed from the core interest of the wg. In
addition, with the selection of AMC-Z as the choosen ACE, the following
I-Ds will also be removed from core interest as it is not relevant
anymore.

MACE: Modal ASCII Compatible Encoding for IDN (draft-ietf-idn-mace)
DUDE: Differential Unicode Domain Encoding(draft-ietf-idn-dude)
Evaluation of various ACEs with existing Japanese Domain Names
(draft-ietf-idn-ace-eval-jp)

In addition,

Requirements of Internationalized Domain Names
(draft-ietf-idn-requirements)

have been move forward for IESG action, probably an IETF-wide Last Call.
Hence, any modification this draft will have to hold.

With this, the following drafts remains in the core interest of the wg.
I would like to remind the wg members to keep wg discussion to these
I-Ds only.

Internationalizing Host Names In Applications (IDNA)
(draft-ietf-idn-idna)
Preparation of Internationalized Host Names (draft-ietf-idn-nameprep)
Proposal for a determining process of ACE identifier
(draft-ietf-idn-aceid)
Japanese characters in multiling ual domain name label
(draft-ietf-idn-jpchar)
Traditional and Simplified Chinese Conversion (draft-ietf-idn-tsconv)
Hangeul NAMEPREP recommendation version 1.0(draft-ietf-idn-hangeulchar)
Improving ACE using code point reordering v1.0(draft-ietf-idn-lsb-ace)
AMC-ACE-Z version 0.2.1(draft-costello-idn-amc-ace-z)

The wg charter page is outdated and will be updated to reflect this.

We encourage further submission of drafts but take note that no draft
will be accepted as wg drafts unless it comes with at least 7
supportors.

Lastly, we should relook at the the charter, goal&milestone. I will post
a prelimary draft for wg reviews sometime this week.

-James Seng




From owner-idn@ops.ietf.org  Tue Oct  9 06:06:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26562
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 06:06:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qtcE-000Cxe-00
	for idn-data@psg.com; Tue, 09 Oct 2001 02:55:58 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qtcD-000Cwr-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 02:55:58 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id SAA31408;
	Tue, 9 Oct 2001 18:55:37 +0900
Message-ID: <01cf01c150a8$b7fc0800$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se> <20011009004803.28618.qmail@cr.yp.to> <00b501c15078$afb77ce0$ec1bd9d2@temp> <20011009043734.15576.qmail@cr.yp.to> <58648759.1002614060@localhost> <4.2.0.58.J.20011009174223.03c9e400@localhost>
Subject: Re: [idn] case preservation
Date: Tue, 9 Oct 2001 18:56:51 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id GAA26562


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "D. J. Bernstein" <djb@cr.yp.to>; <idn@ops.ietf.org>
 > 
> >It would be better to omit nameprep entirely;
> >then users will stick to mechanisms that work, such as clicking on URLs.
> >(Bad characters should still be avoided in registrations, of course.)
> 
> Bad character combinations should be avoided with registration.
> The only registrations for things like <A-Greek><O-Cyrillic><L-Latin>
> will come from spoofers, and the only way such spoofers have
> a chance is through clicking on URIs or a similar interface.

You forgot to mention this type :
All-cyrillic(or All cherokee) uppercase "SEX,CISCO,ATT,HOME,IBM" have the
same look with all-latin uppercase ones.

SOobok


> 
> 
> Regards,    Martin.
> 




From owner-idn@ops.ietf.org  Tue Oct  9 10:35:07 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04849
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 10:35:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qxd8-000PfL-00
	for idn-data@psg.com; Tue, 09 Oct 2001 07:13:10 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qxd7-000PfE-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 07:13:09 -0700
Received: from dhcp-64-103-48-125.cisco.com (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id QAA06000
	for <idn@ops.ietf.org>; Tue, 9 Oct 2001 16:13:07 +0200 (MET DST)
Date: Tue, 09 Oct 2001 15:44:38 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: idn@ops.ietf.org
Subject: Re: [idn] case preservation
Message-ID: <59165160.1002642278@localhost>
In-Reply-To: <20011009065120.28737.qmail@cr.yp.to>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se>
 <20011009004803.28618.qmail@cr.yp.to> <00b501c15078$afb77ce0$ec1bd9d2@temp>
 <20011009043734.15576.qmail@cr.yp.to> <58648759.1002614060@localhost>
 <20011009065120.28737.qmail@cr.yp.to>
X-Mailer: Mulberry/2.1.0 (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-10-09 06.51 +0000 "D. J. Bernstein" <djb@cr.yp.to> wrote:

> If you're not going to do a thorough job of nameprep, then you shouldn't
> be trying to deceive users into believing that IDNs can be safely typed
> from textual printouts.

I have definitly never said that. The contrary.

I have said that nameprep _only_ follow the technical note which Unicode
Consortium have created, because systems which handle Unicode will also use
the same mechanism, which means that data in Unicode _might_ be normalized
inside a unicode system without the knowledge of the user.

Note the might.

  paf




From owner-idn@ops.ietf.org  Tue Oct  9 11:16:04 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05780
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 11:16:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qySG-0002di-00
	for idn-data@psg.com; Tue, 09 Oct 2001 08:06:00 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qySF-0002dS-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 08:05:59 -0700
Received: from bbprime.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 IAA18888;
	Tue, 9 Oct 2001 08:05:43 -0700
Message-Id: <5.1.0.14.2.20011009075910.03f78008@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 09 Oct 2001 08:00:47 -0700
To: "D. J. Bernstein" <djb@cr.yp.to>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] case preservation
Cc: idn@ops.ietf.org
In-Reply-To: <20011009065120.28737.qmail@cr.yp.to>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se>
 <20011009004803.28618.qmail@cr.yp.to>
 <00b501c15078$afb77ce0$ec1bd9d2@temp>
 <20011009043734.15576.qmail@cr.yp.to>
 <58648759.1002614060@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 11:51 PM 10/8/2001, D. J. Bernstein wrote:
>A properly typeset uppercase Alpha is IDENTICAL to a properly typeset
>uppercase A, just as a properly typeset tab is IDENTICAL to a properly
>typeset sequence of spaces. It is simply NOT POSSIBLE to tell the
>difference between AOL.com and AOL.com.

Thank you for providing an example that very nicely shows this to be an old 
problem  for which there is no known solution.

Feel free to offer text to add to the specification, if you feel it will 
solve the problem.

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 Oct  9 11:24:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05906
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 11:24:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qyaU-0003AL-00
	for idn-data@psg.com; Tue, 09 Oct 2001 08:14:30 -0700
Received: from lobo.nic.cc ([206.253.214.247] helo=mail.enic.cc)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qyaT-0003AF-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 08:14:29 -0700
Received: from enic.cc (tailback.enic.cc [206.253.214.252])
	by mail.enic.cc (Postfix) with ESMTP
	id D30896A905; Tue,  9 Oct 2001 08:14:52 -0700 (PDT)
Message-ID: <3BC31457.3649CC9C@enic.cc>
Date: Tue, 09 Oct 2001 08:14:31 -0700
From: Dan Ebert <dan@enic.cc>
Organization: eNIC Corporation
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-12 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Soobok Lee <lsb@postel.co.kr>
Cc: "D. J. Bernstein" <djb@cr.yp.to>, idn@ops.ietf.org,
        Martin Duerst <duerst@w3.org>
Subject: Re: [idn] case preservation
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se> <20011009004803.28618.qmail@cr.yp.to> <00b501c15078$afb77ce0$ec1bd9d2@temp> <20011009043734.15576.qmail@cr.yp.to> <58648759.1002614060@localhost> <4.2.0.58.J.20011009174223.03c9e400@localhost> <01cf01c150a8$b7fc0800$ec1bd9d2@temp>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Soobok Lee wrote:
> 
> ----- Original Message -----
> From: "Martin Duerst" <duerst@w3.org>
> To: "D. J. Bernstein" <djb@cr.yp.to>; <idn@ops.ietf.org>
>  >
> > >It would be better to omit nameprep entirely;
> > >then users will stick to mechanisms that work, such as clicking on URLs.
> > >(Bad characters should still be avoided in registrations, of course.)
> >
> > Bad character combinations should be avoided with registration.
> > The only registrations for things like <A-Greek><O-Cyrillic><L-Latin>
> > will come from spoofers, and the only way such spoofers have
> > a chance is through clicking on URIs or a similar interface.
> 
> You forgot to mention this type :
> All-cyrillic(or All cherokee) uppercase "SEX,CISCO,ATT,HOME,IBM" have the
> same look with all-latin uppercase ones.

But, as Martin said, those links will only be 'used' by spoofers and
only work via clicking on URIs.  (Things like this already happen anyway
... i.e. Someone registers AOL-billing.foo then spams AOL users asking
for updated credit card info ...) If the spoofed domain were printed on
paper the end user would (most likely) interpret the characters as Latin
and type them in accordingly and go to the 'real' site, not the spoofed
site.

> 
> SOobok
> 
> >
> >
> > Regards,    Martin.
> >

-- 
Dan Ebert      <dan@enic.cc>       eNIC Corporation
-----------------------------------------------------
 "What is wanted is not the will to believe, but the 
    will to find out, which is the exact opposite."
       -- Bertrand Russell, "Skeptical_Essays", 1928
-----------------------------------------------------



From owner-idn@ops.ietf.org  Tue Oct  9 12:16:07 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07019
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 12:16:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15qzHu-0005mC-00
	for idn-data@psg.com; Tue, 09 Oct 2001 08:59:22 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15qzHt-0005m2-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 08:59: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 for <idn@ops.ietf.org>;
          Tue, 9 Oct 2001 09:11:43 -0700
Message-ID: <006601c150dc$a4eff120$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: <idn@ops.ietf.org>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se> <20011009004803.28618.qmail@cr.yp.to> <00b501c15078$afb77ce0$ec1bd9d2@temp> <20011009043734.15576.qmail@cr.yp.to> <58648759.1002614060@localhost>
Subject: Re: [idn] case preservation
Date: Tue, 9 Oct 2001 12:08:32 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>
> Already today, people can register domainnames with characters which
look
> "similar" like 'o' and 0, or '1' and 'l'. I.e. this is not a new
>problem.

I have been discussing my Supreme CDN system offline and have come to
the conclusion that it will *never* become a standard because it is
simply not interoperable with existing systems.  But as I have said,
that is okay as I believe all along that all the other CDN systems
(although not as perfect as mine) are absolutely 100% fine exactly the
way they are.

Offline, I have gotten less then pleasant remarks about why "some
people are trying to cause trouble/delay the progress/make things more
difficult then they really are/etc, etc."  Those remarks are made
*not* because of a lack of respect for people's contribution to this
WG but simply because of a lack of understanding of the Chinese
culture and why TC<->SC is so important- which can lead to fustrations
that are fully understandable.  Although we may never come up with a
solution that will be agreed upon by the majority of this WG, the fact
remains that TC<->SC is of paramount importance to the users of
CDNs... and the above 'O', '0','1','l' issue just gave me a good idea
on how to explain why it is so (not sure if this analogy had ever been
made before, but it shouldn't hurt to repeat it.)

At first, the '1','l' may not seem like a good analogy for TC<->SC
conversion because we definitely do *not* want to map 'l' with '1'.
However, the confusion of '1' and 'l' does illustrate why TC<->SC is
so important.  For example, when a person is given 'l.TLD', he can
easy type in '1.TLD' instead and have absolutely no idea why he cannot
reach the intended website.  In English the chance of such a confusion
is only limited to a few cases (such as '0' and '1') where as for
Chinese, *every single* Chinese character poises the opportunity for
such confusion.  Remember, Simplified Chinese and Traditional Chinese
are indistinguishable to many users of CDNs of certain
backgroud/education/location/culture.  (Given certain Chinese
characters, even someone as educated in Chinese as I, cannot tell you
whether it is traditional Chinese or simplified Chinese.)

Thanks
Ben Chan










From owner-idn@ops.ietf.org  Tue Oct  9 15:35:22 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12156
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 15:35:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15r2LM-000IW6-00
	for idn-data@psg.com; Tue, 09 Oct 2001 12:15:08 -0700
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15r2LL-000IVV-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 12:15:07 -0700
Received: from zetnet.co.uk (man-s271.dialup.zetnet.co.uk [194.247.45.142])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f99JF1q14889;
	Tue, 9 Oct 2001 20:15:01 +0100
Message-ID: <3BC3495F.B4FB0F2@zetnet.co.uk>
Date: Tue, 09 Oct 2001 20:00: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: liana.ydisg@juno.com, idn@ops.ietf.org
Subject: Re: [idn] WG Update
References: <20011009.012141.-723299.1.liana.ydisg@juno.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-----

liana.ydisg@juno.com wrote:
> 
> Case preserving has been there, and it is nice
> for people who wants to support it.  To make it
> a requirement will ensure a uniform support,
> and ensure a clear path for mixed use of
> scripts and CJK character recovery cross all
> types of devices, which adds more software work
> but benefit a general public on a long run.  Given
> this does not effect DNS structurally,  I don't see
> why we can not make it a requirement.

Case preservation does affect DNS structurally. In particular,
there have been IDN proposals discussed in this WG that do
not support case preservation; Just-send-UTF-8 is one example.

(That Just-send-UTF-8 has other problems is completely
beside the point; the example is sufficient to demonstrate
that requiring case preservation would eliminate some parts
of the design space, IMHO without justification.)

- -- 
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

iQEVAwUBO8NJIjkCAxeYt5gVAQEucggAp0laoDeqsG1XTfAhVHdSebfw2dGzz9j6
bf9GUOReaKm4gpyue2BXZfG/BzQFvB9mai0/P50t3UNDrIrEhz78IK37c2NIbZnT
ioEPdN/BkMsqRpRTM41s0R6XZBLZC5M4he7lXEIw/kxSP3iDoFvpy8VVo3Pdlm2g
qYvy03H+bayh2BiAaP/sqGWwjlm3shBJldCdmgPguE3n1OabwbNoMEnEphW1do3v
WM86ZcqUummqUYMu0I9y38j9wYYnNQ3t1yo3RmFgRhJqQgqHdCVMr6hRCuEQDRBA
DDZf7kx1X6y5FWIi3mi/3xrgAd7ytZou5c13+KEDPsieE0jyJAHWkA==
=crFz
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Tue Oct  9 17:15:56 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13658
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 17:15:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15r427-000Pze-00
	for idn-data@psg.com; Tue, 09 Oct 2001 14:03:23 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15r426-000PzY-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 14:03:22 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VV8+kyMe1h9L4xi8cRkxBTPg==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GHCBGEH8; Tue, 09 Oct 2001 17:03:01 EDT
To: david.hopwood@zetnet.co.uk
Cc: idn@ops.ietf.org
Date: Tue, 9 Oct 2001 14:23:18 -0700
Subject: Re: [idn] WG Update
Message-ID: <20011009.142321.-726277.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

Educate me please.

> 
> Case preservation does affect DNS structurally. In particular,
> there have been IDN proposals discussed in this WG that do
> not support case preservation; Just-send-UTF-8 is one example.
> 
> (That Just-send-UTF-8 has other problems is completely
> beside the point; the example is sufficient to demonstrate
> that requiring case preservation would eliminate some parts
> of the design space, IMHO without justification.)
> 
> - -- 
> David Hopwood <david.hopwood@zetnet.co.uk>



From owner-idn@ops.ietf.org  Tue Oct  9 17:36:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13905
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 17:36:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15r4QJ-0001oS-00
	for idn-data@psg.com; Tue, 09 Oct 2001 14:28:23 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15r4QI-0001oL-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 14:28:22 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VVAgfqDuwz67BjAQOP76VWtw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GHCCUYHP; Tue, 09 Oct 2001 17:27:21 EDT
To: dhc@dcrocker.net
Cc: djb@cr.yp.to, idn@ops.ietf.org
Date: Tue, 9 Oct 2001 14:46:52 -0700
Subject: Re: [idn] case preservation
Message-ID: <20011009.144741.-726277.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-18,20-45
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 have offered a solution to the old problem in 
  draft-liana-idn-map-00. 
Have you read it?  

If you have read it, then I would ask your support 
for the WG's consideration.  May I?  And please DO
tell me why you are NOT support it for your 
consideration? 

If I have enough support for the submission, I will
address the following in an updated draft:
 Limits of IDN-map (This section is for you)
 Limits of language tags(mostly mixed use of scripts)
 Mix Scripts and Multiple Languages of a Script 
 Multiple Standards vs. DNS Format 
 and some implementation of language specific procedures.

Liana

On Tue, 09 Oct 2001 08:00:47 -0700 Dave Crocker <dhc@dcrocker.net>
writes:
> At 11:51 PM 10/8/2001, D. J. Bernstein wrote:
> >A properly typeset uppercase Alpha is IDENTICAL to a properly 
> typeset
> >uppercase A, just as a properly typeset tab is IDENTICAL to a 
> properly
> >typeset sequence of spaces. It is simply NOT POSSIBLE to tell the
> >difference between AOL.com and AOL.com.
> 
> Thank you for providing an example that very nicely shows this to be 
> an old 
> problem  for which there is no known solution.
> 
> Feel free to offer text to add to the specification, if you feel it 
> will 
> solve the problem.
> 
> 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 Oct  9 17:59:43 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14199
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 17:59:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15r4n2-0003aK-00
	for idn-data@psg.com; Tue, 09 Oct 2001 14:51:52 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15r4n1-0003aE-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 14:51:51 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VVuwy7JfMJXIO76ATeSAxaiQ==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GHCD83KS; Tue, 09 Oct 2001 17:51:26 EDT
To: ben@cc-www.com
Cc: idn@ops.ietf.org
Date: Tue, 9 Oct 2001 15:08:57 -0700
Subject: Re: [idn] case preservation
Message-ID: <20011009.151143.-726277.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

You are right, that many people do not have experiences
with 4000+ symbols to use on a daily bases, and they 
think an international standard to cover alphabet languages 
of three: Latin, Greek and may be Cyrillic is good enough
to call it an IDN.  Chinese can offer a Five Stroke analogy 
to the 26 letter case, at least it is a 5:26 problem:-)

Liana

On Tue, 9 Oct 2001 12:08:32 -0400 "ben" <ben@cc-www.com> writes:
> >
> > Already today, people can register domainnames with characters 
> which
> look
> > "similar" like 'o' and 0, or '1' and 'l'. I.e. this is not a new
> >problem.
> 
> I have been discussing my Supreme CDN system offline and have come 
> to
> the conclusion that it will *never* become a standard because it is
> simply not interoperable with existing systems.  But as I have said,
> that is okay as I believe all along that all the other CDN systems
> (although not as perfect as mine) are absolutely 100% fine exactly 
> the
> way they are.
> 
> Offline, I have gotten less then pleasant remarks about why "some
> people are trying to cause trouble/delay the progress/make things 
> more
> difficult then they really are/etc, etc."  Those remarks are made
> *not* because of a lack of respect for people's contribution to this
> WG but simply because of a lack of understanding of the Chinese
> culture and why TC<->SC is so important- which can lead to 
> fustrations
> that are fully understandable.  Although we may never come up with a
> solution that will be agreed upon by the majority of this WG, the 
> fact
> remains that TC<->SC is of paramount importance to the users of
> CDNs... and the above 'O', '0','1','l' issue just gave me a good 
> idea
> on how to explain why it is so (not sure if this analogy had ever 
> been
> made before, but it shouldn't hurt to repeat it.)
> 
> At first, the '1','l' may not seem like a good analogy for TC<->SC
> conversion because we definitely do *not* want to map 'l' with '1'.
> However, the confusion of '1' and 'l' does illustrate why TC<->SC is
> so important.  For example, when a person is given 'l.TLD', he can
> easy type in '1.TLD' instead and have absolutely no idea why he 
> cannot
> reach the intended website.  In English the chance of such a 
> confusion
> is only limited to a few cases (such as '0' and '1') where as for
> Chinese, *every single* Chinese character poises the opportunity for
> such confusion.  Remember, Simplified Chinese and Traditional 
> Chinese
> are indistinguishable to many users of CDNs of certain
> backgroud/education/location/culture.  (Given certain Chinese
> characters, even someone as educated in Chinese as I, cannot tell 
> you
> whether it is traditional Chinese or simplified Chinese.)
> 
> Thanks
> Ben Chan
> 
> 
> 
> 
> 
> 
> 
> 



From owner-idn@ops.ietf.org  Tue Oct  9 18:13:09 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14291
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 18:13:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15r4xb-0004PM-00
	for idn-data@psg.com; Tue, 09 Oct 2001 15:02:47 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15r4xa-0004PF-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 15:02:46 -0700
Received: from amc by nicemice.net with local (Exim 3.32 #1 (Debian))
	id 15r4xZ-0000Ua-00
	for <idn@ops.ietf.org>; Tue, 09 Oct 2001 15:02:45 -0700
Date: Tue, 9 Oct 2001 22:02:45 +0000
From: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>
To: idn@ops.ietf.org
Subject: Re: [idn] core interest of the wg
Message-ID: <20011009220245.D1163@nicemice.net>
Reply-To: IETF idn working group <idn@ops.ietf.org>
References: <065601c150a4$f907ef70$dd00a8c0@jamessonyvaio>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <065601c150a4$f907ef70$dd00a8c0@jamessonyvaio>
User-Agent: Mutt/1.3.22i
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James Seng/Personal <jseng@pobox.org.sg> wrote:

> AMC-ACE-Z version 0.2.1 (draft-costello-idn-amc-ace-z)

Version 0.2.1 (draft-costello-idn-amc-ace-z-00) was superceded a month
ago by version 0.3.1 (draft-ietf-idn-amc-ace-z-01).

AMC



From owner-idn@ops.ietf.org  Tue Oct  9 18:22:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14352
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 18:22:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15r59C-0005Hz-00
	for idn-data@psg.com; Tue, 09 Oct 2001 15:14:46 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15r59B-0005Ht-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 15:14:45 -0700
Received: from amc by nicemice.net with local (Exim 3.32 #1 (Debian))
	id 15r59A-0000W2-00
	for <idn@ops.ietf.org>; Tue, 09 Oct 2001 15:14:44 -0700
Date: Tue, 9 Oct 2001 22:14:44 +0000
From: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>
To: idn@ops.ietf.org
Subject: Re: [idn] WG Update
Message-ID: <20011009221444.E1163@nicemice.net>
Reply-To: IETF idn working group <idn@ops.ietf.org>
References: <20011009.012141.-723299.1.liana.ydisg@juno.com> <3BC3495F.B4FB0F2@zetnet.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3BC3495F.B4FB0F2@zetnet.co.uk>
User-Agent: Mutt/1.3.22i
Sender: owner-idn@ops.ietf.org
Precedence: bulk

David Hopwood <david.hopwood@zetnet.co.uk> wrote:

> In particular, there have been IDN proposals discussed in this WG that
> do not support case preservation; Just-send-UTF-8 is one example.

Actually, just-send-UTF-8 supports case preservation just fine; it's
send-nameprepped-UTF-8 that doesn't.  If the sender already requires the
receiver to support UTF-8, it might be reasonable to further require the
receiver to do normalization and case-folding when comparing strings.
The one exception is DNS queries, where for performance reasons you
would want to do it at the requestor, but who cares if DNS queries don't
preserve case (DNS responses still could).

AMC



From owner-idn@ops.ietf.org  Tue Oct  9 18:37:54 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14547
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 18:37:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15r5Mx-0006Kt-00
	for idn-data@psg.com; Tue, 09 Oct 2001 15:28:59 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15r5Mw-0006Kn-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 15:28:58 -0700
Received: from amc by nicemice.net with local (Exim 3.32 #1 (Debian))
	id 15r5Mv-0000X2-00
	for <idn@ops.ietf.org>; Tue, 09 Oct 2001 15:28:57 -0700
Date: Tue, 9 Oct 2001 22:28:57 +0000
From: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>
To: idn@ops.ietf.org
Subject: Re: [idn] 7CE
Message-ID: <20011009222857.F1163@nicemice.net>
Reply-To: IETF idn working group <idn@ops.ietf.org>
References: <20011004152630.20354.qmail@cr.yp.to> <20011003.125229.-816135.0.liana.ydisg@juno.com> <01a901c14c77$f393bf50$dd00a8c0@jamessonyvaio> <004c01c14c90$3748bd00$d43f7018@mtag1.on.home.com> <001001c14cd9$31dd85a0$d43f7018@mtag1.on.home.com> <4.2.0.58.J.20011005145034.03152170@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4.2.0.58.J.20011005145034.03152170@localhost>
User-Agent: Mutt/1.3.22i
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Martin Duerst <duerst@w3.org> wrote:

> I think it might help quite a few people who don't really like ACE
> to know that the (key) ACE proponents understand that ACE is a layer
> violation in the (character) encoding stack, and will have its serious
> negative consequences like any other layer violation.

I usually think of a "layer violation" as a case of one layer being too
interdependent on the inner working of another layer, instead of knowing
only the interfaces to the layers immediately above and below it.

ACE merely inserts a new layer, but the layers can still be cleanly
separated.

If the old stack looks like this:

    arrangement of glyphs
    sequence of characters
    sequence of code points
    sequence of octets

then the new stack looks like this:

    arrangement of glyphs
    sequence of characters
    sequence of code points
    sequence of basic code points
    sequence of octets

The old transformations between glyphs and characters, and between
characters and code points, are unaffected.  The transformation between
basic code points and octets is exactly like the old transformation
between code points and octets (except that the repertoire is smaller,
so a more primitive serialization is likely to be used, typically
ASCII).  A new translation between code points and basic code points is
introduced, but it is orthogonal to the transformations at the other
layers.

AMC



From owner-idn@ops.ietf.org  Tue Oct  9 23:01:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA19261
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 23:01:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15r9GE-000OeX-00
	for idn-data@psg.com; Tue, 09 Oct 2001 19:38:18 -0700
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15r9GD-000OeR-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 19:38:17 -0700
Received: from zetnet.co.uk (man-s334.dialup.zetnet.co.uk [194.247.45.205])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f9A2cEq14773
        for <idn@ops.ietf.org>; Wed, 10 Oct 2001 03:38:14 +0100
Message-ID: <3BC3B146.16790870@zetnet.co.uk>
Date: Wed, 10 Oct 2001 03:24:06 +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: IETF idn working group <idn@ops.ietf.org>
Subject: Re: [idn] WG Update
References: <20011009.012141.-723299.1.liana.ydisg@juno.com> <3BC3495F.B4FB0F2@zetnet.co.uk> <20011009221444.E1163@nicemice.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-----

"Adam M. Costello" wrote:
> David Hopwood <david.hopwood@zetnet.co.uk> wrote:
> 
> > In particular, there have been IDN proposals discussed in this WG that
> > do not support case preservation; Just-send-UTF-8 is one example.
> 
> Actually, just-send-UTF-8 supports case preservation just fine; it's
> send-nameprepped-UTF-8 that doesn't.

Just-send-UTF-8 requires users to type lowercase names, and does not allow
storing or registering names with uppercase (if I understand the intention
correctly; there was never an I-D). Send-nameprepped-UTF-8, OTOH, does
support case preservation, since names can be stored with uppercase and
then mapped to lowercase-NFKC by the resolver (or application).

- -- 
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

iQEVAwUBO8OP7zkCAxeYt5gVAQEk4wf+OItK8GFCKbbjYhbY9RQcPTrVmnfc3lEM
16wLsJtVny5mnjn4EX3yXI+fP+CjmKq7bwVUIW/rXt3G0TmdSQpLQGRBK/0vVCmd
ejuvD0kcKtormpNLFp8uC/msB/9nbhZuArk/eHiFJVInzgzjwXCZCJkm8yp5KD1p
wpmLHGWP3zOMvU1mvFGZ+3ZjVLMrVuOHZsU/KzmcEHqkf1uNKmnwZz3AnJQmnACF
k9mbsrqR9sIhbLmosHF4PjMyT/5JuYK70uzJ224s9TwbkFdC0stT0/drQS3Ax/Uz
C1rERc+J31GRxP2VZtVaH5cbuNGNDkVGVQnXqn4ik7TCCR3UIa18Cw==
=YoPW
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Tue Oct  9 23:10:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA19380
	for <idn-archive@lists.ietf.org>; Tue, 9 Oct 2001 23:10:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15r9XD-00005Z-00
	for idn-data@psg.com; Tue, 09 Oct 2001 19:55:51 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15r9X8-000Pyl-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 19:55:46 -0700
Received: from LocalHost ([140.115.7.27])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f9A30x729903
	for <idn@ops.ietf.org>; Wed, 10 Oct 2001 11:01:02 +0800 (CST)
Message-ID: <004901c15136$9bb1f720$1b07738c@q.j.tw>
From: "tsenglm@????.??.tw" <tsenglm@cc.ncu.edu.tw>
To: "IETF idn working group" <idn@ops.ietf.org>
References: <20011009.012141.-723299.1.liana.ydisg@juno.com> <3BC3495F.B4FB0F2@zetnet.co.uk> <20011009221444.E1163@nicemice.net>
Subject: Re: [idn] WG Update
Date: Wed, 10 Oct 2001 10:52:29 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> David Hopwood <david.hopwood@zetnet.co.uk> wrote:
>
> > In particular, there have been IDN proposals discussed in this WG that
> > do not support case preservation; Just-send-UTF-8 is one example.
>
> Actually, just-send-UTF-8 supports case preservation just fine; it's
> send-nameprepped-UTF-8 that doesn't.  If the sender already requires the
> receiver to support UTF-8, it might be reasonable to further require the
> receiver to do normalization and case-folding when comparing strings.
> The one exception is DNS queries, where for performance reasons you
> would want to do it at the requestor, but who cares if DNS queries don't
> preserve case (DNS responses still could).
       The reason is not for performance of DNS. We use ACE only for
backward compatability of  existed LDH-DNS server. All LDH-server do
comarison case-insenstively and keep case preserving in response.
       Nameprep will map all Full-Width-english-character in unicode
directly to lower-case ASCII  is considered the confusing of  TLD and  ASCII
name. To force all case to lower case is over-specifications in
requirements. UTF-8 can keep the case of ASCII
but can not preserve the case of non-ASCII . But now AMC-ACE-Z can preserve
one case of non-ASCII , it is an excellent improvements over UTF-8 . We
should consider the specification based on new technology ---AMC-ACE-Z.
      Mapping all Full-Width-english-characters to ASCII is necessary , but
mapping all case of  ASCII to lower case in Nameprep is not necessary .
That will be more compatible with historical  DNS and let all non-ASCII has
the chance to view the name in their like form.
      Only in  case-insensive comparison and case preserving of non-ASCII ,
ACE is more suitable for next step in DNS developing.

L.M.Tseng




From owner-idn@ops.ietf.org  Wed Oct 10 00:02:02 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20128
	for <idn-archive@lists.ietf.org>; Wed, 10 Oct 2001 00:02:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15rAQl-0004Vm-00
	for idn-data@psg.com; Tue, 09 Oct 2001 20:53:15 -0700
Received: from imo-d09.mx.aol.com ([205.188.157.41])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15rAQk-0004Vg-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 20:53:14 -0700
Received: from DougEwell2@cs.com
	by imo-d09.mx.aol.com (mail_out_v31_r1.8.) id i.107.6d35471 (4398);
	Tue, 9 Oct 2001 23:53:11 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <107.6d35471.28f52026@cs.com>
Date: Tue, 9 Oct 2001 23:53:10 EDT
Subject: Re: [idn] WG Update
To: idn@ops.ietf.org
CC: tsenglm@cc.ncu.edu.tw
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a message dated 2001-10-09 20:20:32 Pacific Daylight Time, 
tsenglm@cc.ncu.edu.tw writes:

>  UTF-8 can keep the case of ASCII
>  but can not preserve the case of non-ASCII . But now AMC-ACE-Z can preserve
>  one case of non-ASCII , it is an excellent improvements over UTF-8 . We
>  should consider the specification based on new technology ---AMC-ACE-Z.

I have generally stayed out of the UTF-8 versus ACE debate, but the above 
statement cannot go unpunished.  UTF-8 is a character encoding scheme for 
*every single code point* in ISO/IEC 10646.  That means every character, 
upper- and lower-case, in every script, has its own UTF-8 representation.

To say that UTF-8 does not preserve case distinctions is complete nonsense.  
It is the nameprep stage that folds away case distinctions (for better or 
worse).

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Wed Oct 10 00:23:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20226
	for <idn-archive@lists.ietf.org>; Wed, 10 Oct 2001 00:23:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15rAhL-0005nj-00
	for idn-data@psg.com; Tue, 09 Oct 2001 21:10:23 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15rAhK-0005nd-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 21:10:22 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id NAA14883;
	Wed, 10 Oct 2001 13:10:14 +0900
Message-ID: <032c01c15141$9fc7cc80$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp>
Subject: [idn] call for comments for REORDERING
Date: Wed, 10 Oct 2001 13:11:23 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA20226

Hi, all

I am ready to receive any criticisms on REORDERING.
Any suggestions of improvements or downsides of REORDERING are all welcome.

I expect many feedbacks from non-US and non-European participants and observers.

Thanks.

Soobok Lee

----- Original Message ----- 
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Sent: Sunday, September 30, 2001 8:12 PM
Subject: Re: [idn] I-D ACTION:draft-ietf-idn-lsb-ace-02.txt


> Hi, all
> 
> This table summarizes the # of max chars in labels in each script block.
> This will be included the next revision of reordering I-D.
> For han/hangul block, REORDERING+ACE-Z outperforms DUDE by nearly 200%.
> If you have suggestions or other label samples to test with, 
> please leave me a note.
>  
> Thanks.
> 
> Soobok Lee,   lsb@postel.co.kr
> 
> 
> +------------------------------------------------------------+
> |Maximum number of characters in a label in each script block|
> |                                                            |
> |                max char = (63 - 4) / ratio                 |
> |   ACE length = 4 + ratio * N ( N : # of chars in label)    |
> +---------------+-------------------+-------------------+----+
> | Script Block  |     AMC-ACE-Z     |   Reordering +    |Gain|
> |               |                   |     AMC-ACE-Z     |    |
> +---------+-----+---------+---------+---------+---------+    |
> |  Name   |Size |  ratio  |max char |  ratio  |max char |    |
> +---------+-----+---------+---------+---------+---------+----+
> |   Han   |20992|  2.98   |   19    |  2.21   |   26    | +7 |
> +---------+-----+---------+---------+---------+---------+----+
> | Hangeul |11172|  2.97   |   19    |  2.04   |   28    | +9 |
> +---------+-----+---------+---------+---------+---------+----+
> |  Greek  | 144 |  1.29   |   45    |  1.14   |   51    | +6 |
> +---------+-----+---------+---------+---------+---------+----+
> | Arabic  | 256 |  1.34   |   44    |  1.28   |   46    | +2 |
> +---------+-----+---------+---------+---------+---------+----+
> |Cyrillic | 304 |  1.23   |   47    |  1.15   |   51    | +4 |
> +---------+-----+---------+---------+---------+---------+----+
> | Hebrew  | 102 |  1.29   |   45    |  1.18   |   50    | +5 |
> +---------+-----+---------+---------+---------+---------+----+
> |  Hindi  | 128 |  1.31   |   45    |  1.17   |   50    | +5 |
> +---------+-----+---------+---------+---------+---------+----+
> |Hiragana | 96  |  1.50   |   39    |  1.45   |   40    | +1 |
> +---------+-----+---------+---------+---------+---------+----+
> |Katakana | 96  |  1.44   |   40    |  1.33   |   44    | +4 |
> +---------+-----+---------+---------+---------+---------+----+
> |  Tamil  | 128 |  1.62   |   36    |  1.14   |   51    |+15 |
> +---------+-----+---------+---------+---------+---------+----+
> |  Thai   | 128 |  1.39   |   42    |  1.13   |   52    |+10 |
> +---------+-----+---------+---------+---------+---------+----+
> |Ethiopic | 416 |  2.10   |   28    |  1.60   |   36    | +8 |
> +---------+-----+---------+---------+---------+---------+----+
> 
> 
> ----- Original Message ----- 
> From: <Internet-Drafts@ietf.org>
> To: <IETF-Announce:>
> Cc: <idn@ops.ietf.org>
> Sent: Tuesday, September 18, 2001 10:33 PM
> Subject: [idn] I-D ACTION:draft-ietf-idn-lsb-ace-02.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 : Improving ACE using code point reordering v2.0
> > Author(s) : S. Lee
> > Filename : draft-ietf-idn-lsb-ace-02.txt
> > Pages : 
> > Date : 17-Sep-01
> > 
> > This document describes a method to improve ACE label efficiency by
> > frequency-based temporal reordering of code points in ACE encoding
> > and decoding processes in order to relocate scattered frequent 
> > characters into much more compact area in reordered code space.
> > 
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-idn-lsb-ace-02.txt
> > 
> > To remove yourself from the IETF Announcement list, send a message to 
> > ietf-announce-request with the word unsubscribe in the body of the message.
> > 
> > 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-02.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-02.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 Oct 10 01:34:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22121
	for <idn-archive@lists.ietf.org>; Wed, 10 Oct 2001 01:34:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15rBjh-000Av5-00
	for idn-data@psg.com; Tue, 09 Oct 2001 22:16:53 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15rBjb-000Auj-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 22:16:47 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id E8AE77F457; Wed, 10 Oct 2001 14:16:17 +0900 (JST)
Message-Id: <4.2.0.58.J.20011010135249.03d9c860@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 10 Oct 2001 13:55:00 +0900
To: David Hopwood <david.hopwood@zetnet.co.uk>,
        IETF idn working group <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] WG Update
In-Reply-To: <3BC3B146.16790870@zetnet.co.uk>
References: <20011009.012141.-723299.1.liana.ydisg@juno.com>
 <3BC3495F.B4FB0F2@zetnet.co.uk>
 <20011009221444.E1163@nicemice.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 03:24 01/10/10 +0100, David Hopwood wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>
>"Adam M. Costello" wrote:
> > David Hopwood <david.hopwood@zetnet.co.uk> wrote:
> >
> > > In particular, there have been IDN proposals discussed in this WG that
> > > do not support case preservation; Just-send-UTF-8 is one example.
> >
> > Actually, just-send-UTF-8 supports case preservation just fine; it's
> > send-nameprepped-UTF-8 that doesn't.
>
>Just-send-UTF-8 requires users to type lowercase names, and does not allow
>storing or registering names with uppercase (if I understand the intention
>correctly; there was never an I-D).

There was an I-D with UTF-8 in the old days (1997? 1998?) at least,
which proposed that the client map to lower case (according to the
user preferences/locale settings at the client).

Regards,   Martin.



From owner-idn@ops.ietf.org  Wed Oct 10 01:36:12 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22284
	for <idn-archive@lists.ietf.org>; Wed, 10 Oct 2001 01:36:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15rBjc-000Auw-00
	for idn-data@psg.com; Tue, 09 Oct 2001 22:16:48 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15rBjb-000Aui-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 22:16:47 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 0223B7F437; Wed, 10 Oct 2001 14:16:15 +0900 (JST)
Message-Id: <4.2.0.58.J.20011010133945.03d99100@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 10 Oct 2001 13:49:01 +0900
To: "ben" <ben@cc-www.com>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] case preservation
In-Reply-To: <006601c150dc$a4eff120$d43f7018@mtag1.on.home.com>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se>
 <20011009004803.28618.qmail@cr.yp.to>
 <00b501c15078$afb77ce0$ec1bd9d2@temp>
 <20011009043734.15576.qmail@cr.yp.to>
 <58648759.1002614060@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 12:08 01/10/09 -0400, ben wrote:
>At first, the '1','l' may not seem like a good analogy for TC<->SC
>conversion because we definitely do *not* want to map 'l' with '1'.
>However, the confusion of '1' and 'l' does illustrate why TC<->SC is
>so important.  For example, when a person is given 'l.TLD', he can
>easy type in '1.TLD' instead and have absolutely no idea why he cannot
>reach the intended website.  In English the chance of such a confusion
>is only limited to a few cases (such as '0' and '1') where as for
>Chinese, *every single* Chinese character poises the opportunity for
>such confusion.  Remember, Simplified Chinese and Traditional Chinese
>are indistinguishable to many users of CDNs of certain
>backgroud/education/location/culture.  (Given certain Chinese
>characters, even someone as educated in Chinese as I, cannot tell you
>whether it is traditional Chinese or simplified Chinese.)

This is a good point. But please note that you don't actually have
to know whether a character is simplified or traditional. If you
work on a simplified Chinese system or with a simplified Chinese
input method, you will just get simplified Chinese characters
as the first choice from you input method. Same thing the other
way round for traditional Chinese.

This means that if somebody wants to have a domain name usable
both is China,Singapore,.. and in Taiwan,Hong Kong,..., they
have to do two registrations. Of course, there are cases where
there are more registrations needed (e.g. for simplified
characters used in Taiwan), but these are exceptions.

Also, for most characters where there is actually a difference
(there are many cases where there is none, and which are
therefore unified), it is quite easy to tell whether they
are simplified or not. The main reason for this is that
most simplifications are very systematic. Of course, because
there are so many Chinese characters, there are always some
that you don't know. That is something that applies to any
other aspect of Chinese characters.


Regards,    Martin.



From owner-idn@ops.ietf.org  Wed Oct 10 01:44:02 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22692
	for <idn-archive@lists.ietf.org>; Wed, 10 Oct 2001 01:44:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15rBjd-000Av3-00
	for idn-data@psg.com; Tue, 09 Oct 2001 22:16:49 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15rBjc-000Auv-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 22:16:48 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id EE39F7F45B; Wed, 10 Oct 2001 14:16:18 +0900 (JST)
Message-Id: <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 10 Oct 2001 14:16:21 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
In-Reply-To: <032c01c15141$9fc7cc80$ec1bd9d2@temp>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hello Soobok,

Here are my comments on reordering. Apologies if they are
too clear.

The additional complexity introduced by reordering is a very
serious problem. It is true that this complexity is somewhat
similar to the complexity of e.g. nameprep or conversion from
a legacy encoding. However, on many platforms, both conversion
from a legacy encoding as well as many aspects of nameprep
are available as libraries, and are used for other purposes.
In particular on constrained devices (mobile phones,...),
most of nameprep can be simplified a lot if one knows what
kinds of characters can be input.

On the other hand, the benefits for the users are actually
very small. Nobody wants to input domain names with 15 or
more Hanzi or Hangul. Nobody will be able to remember them.
Writing them down on a napkin will take a long time.
Every company or organization that has such a long label
in their domain name, and no shorter alternative, will
simply not get any contacts directly to their web site.
If they have a short alternative, why do they need a
long version? (please note that there is no danger of
spoofing by somebody else getting the long version :-).

So this is a solution in search of a real problem,
not worth bothering the whole world with additional
complexity.


Regards,   Martin.


At 13:11 01/10/10 +0900, Soobok Lee wrote:
>Hi, all
>
>I am ready to receive any criticisms on REORDERING.
>Any suggestions of improvements or downsides of REORDERING are all welcome.
>
>I expect many feedbacks from non-US and non-European participants and 
>observers.
>
>Thanks.
>
>Soobok Lee




From owner-idn@ops.ietf.org  Wed Oct 10 02:26:18 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03293
	for <idn-archive@lists.ietf.org>; Wed, 10 Oct 2001 02:26:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15rCby-000FUL-00
	for idn-data@psg.com; Tue, 09 Oct 2001 23:12:58 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15rCbw-000FUE-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 23:12:57 -0700
Received: from LocalHost ([140.115.7.27])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f9A6Ic725330;
	Wed, 10 Oct 2001 14:18:38 +0800 (CST)
Message-ID: <003b01c15152$31b506c0$1b07738c@q.j.tw>
From: "tsenglm@????.??.tw" <tsenglm@cc.ncu.edu.tw>
To: <DougEwell2@cs.com>, <idn@ops.ietf.org>
References: <107.6d35471.28f52026@cs.com>
Subject: Re: [idn] WG Update
Date: Wed, 10 Oct 2001 14:09: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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: <DougEwell2@cs.com>


> In a message dated 2001-10-09 20:20:32 Pacific Daylight Time,
> tsenglm@cc.ncu.edu.tw writes:
>
> >  UTF-8 can keep the case of ASCII
> >  but can not preserve the case of non-ASCII . But now AMC-ACE-Z can
preserve
> >  one case of non-ASCII , it is an excellent improvements over UTF-8 . We
> >  should consider the specification based on new technology ---AMC-ACE-Z.
>
> I have generally stayed out of the UTF-8 versus ACE debate, but the above
> statement cannot go unpunished.  UTF-8 is a character encoding scheme for
> *every single code point* in ISO/IEC 10646.  That means every character,
> upper- and lower-case, in every script, has its own UTF-8 representation.
>
> To say that UTF-8 does not preserve case distinctions is complete
nonsense.
> It is the nameprep stage that folds away case distinctions (for better or
> worse).
                 If  you mean casing of  Latin characters , you may be
right. but you can try the characters in (u+F94D , u+6dda), (u+F950, u+7e37)
that are compatibility CJK ideograph characters in www.unicode.org . If
these characters are mapped to single one code point like the  case mapping
in ASCII , you can not use UTF-8 to do case-like-insensitive comparation and
to keep case-prserving .  The difference come from the relative to LDH-DNS .
                I don not against UTF-8 , but AMC-ACE-Z  can support
case-code- mapping and case-preserving-after-code-mapping and
case-sensitive-comparation all coexisted. It is an intergreted properties in
LDH-DNS.

L.M.tseng




From owner-idn@ops.ietf.org  Wed Oct 10 03:00:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05364
	for <idn-archive@lists.ietf.org>; Wed, 10 Oct 2001 03:00:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15rD4j-000Hju-00
	for idn-data@psg.com; Tue, 09 Oct 2001 23:42:41 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15rD4i-000Hjo-00
	for idn@ops.ietf.org; Tue, 09 Oct 2001 23:42:41 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id PAA29651;
	Wed, 10 Oct 2001 15:42:32 +0900
Message-ID: <037501c15156$e6da5470$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
Subject: Re: [idn] call for comments for REORDERING
Date: Wed, 10 Oct 2001 15:43:41 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id DAA05364

thanks for you comment. Here goes my answer.

----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
Sent: Wednesday, October 10, 2001 2:16 PM
Subject: Re: [idn] call for comments for REORDERING


> 
> The additional complexity introduced by reordering is a very
> serious problem. It is true that this complexity is somewhat
> similar to the complexity of e.g. nameprep or conversion from
> a legacy encoding. However, on many platforms, both conversion
> from a legacy encoding as well as many aspects of nameprep
> are available as libraries, and are used for other purposes.

Current Windows 98,2K,XP and Linux  contain   NFKC codes ?

> In particular on constrained devices (mobile phones,...),
> most of nameprep can be simplified a lot if one knows what
> kinds of characters can be input.

In this case, the reordering table _also_ can be simplified
only to that input script blocks .

As for arabic/hindi/kata/hira/tamil/greek/hebrew, 
it adds only +10~+20 lines of simple character mapping array
for each script.
those additional lines of data are less than the # of  comment
lines in the ACE source code.



> 
> On the other hand, the benefits for the users are actually
> very small. Nobody wants to input domain names with 15 or
> more Hanzi or Hangul. Nobody will be able to remember them.
> Writing them down on a napkin will take a long time.
> Every company or organization that has such a long label
> in their domain name, and no shorter alternative, will
> simply not get any contacts directly to their web site.
> If they have a short alternative, why do they need a
> long version? (please note that there is no danger of
> spoofing by somebody else getting the long version :-).

lets' think about the shorter ACE label produced for the native label of 
mean _average_ length. 
The next table for hangul script block says:
  For N=6, 3.12*6 - 2.28*6 = 18 - 13 = 5 characters are saved.

The main benefits of REODERING is not only for very long domains,
but for average ones. It also helps administation,transcription and eye-
comparison on the ACE labels.
  
Moreover, as IDNA I-D recommends, 
ACE labels should be rendered "as it is",
when the decoded native-label contains characters which 
the rendering engine cannot display. For example,
if you have _no_ huge han script font set in your mobile phone (or PC),
the ACE labels for han/hangul email addresses of your friends should
be displayed "as it is". But, it may be often too long to be displayed 
in your narrow phone LCD lines of width 16~20, without REORDERING.


Moreover, If we get ACEed i18n email addresses in the future, 
its native form will look like XXXX@YYYYYY.com. In the case of han/hangul script , 
the sum of lengths of two non-latin strings (XXXX,YYYYYY) may 
exceed 10 very often. 
For such cases, the reordering would help  to save up to 8~9
characters for ACEed email addresess. Big saves..


8. hangul-1024

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
|  1|    1953|      1953|      7812(4.00)|      7812(4.00)| 0.00|
|  2|   17149|     34298|    124782(3.64)|    106238(3.10)|14.86|
|  3|   39643|    118929|    403205(3.39)|    323801(2.72)|19.69|
|  4|   62285|    249140|    816093(3.28)|    622067(2.50)|23.77|
|  5|   39675|    198375|    636102(3.21)|    470174(2.37)|26.09|
|  6|   23891|    143346|    452483(3.16)|    326242(2.28)|27.90|
|  7|   12448|     87136|    271953(3.12)|    192139(2.21)|29.35|
|  8|    5441|     43528|    134600(3.09)|     94322(2.17)|29.92|
|  9|    2264|     20376|     62405(3.06)|     43266(2.12)|30.67|
| 10|     895|      8950|     27223(3.04)|     18764(2.10)|31.07|
| 11|     373|      4103|     12420(3.03)|      8511(2.07)|31.47|
| 12|     141|      1692|      5080(3.00)|      3505(2.07)|31.00|
| 13|      77|      1001|      2986(2.98)|      2039(2.04)|31.71|
| 14|      32|       448|      1331(2.97)|       911(2.03)|31.56|
| 15|      20|       300|       884(2.95)|       603(2.01)|31.79|
| 16|      10|       160|       460(2.88)|       337(2.11)|26.74|
| 17|       7|       119|       354(2.97)|       243(2.04)|31.36|

|All|  206304|    913854|   2960173(3.24)|   2220974(2.43)|24.97|


non-CJK script often has long labels that exceeds 15.


1. arabic

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
|  1|      42|        42|       126(3.00)|       126(3.00)| 0.00|
|  2|      59|       118|       258(2.19)|       249(2.11)| 3.49|
|  3|     363|      1089|      2121(1.95)|      1992(1.83)| 6.08|
|  4|     888|      3552|      6359(1.79)|      5811(1.64)| 8.62|
|  5|    1122|      5610|      9550(1.70)|      8529(1.52)|10.69|
|  6|    1009|      6054|      9890(1.63)|      8620(1.42)|12.84|
|  7|     845|      5915|      9309(1.57)|      8134(1.38)|12.62|
|  8|     378|      3024|      4590(1.52)|      3992(1.32)|13.03|
|  9|     263|      2367|      3523(1.49)|      3063(1.29)|13.06|
| 10|     152|      1520|      2230(1.47)|      1941(1.28)|12.96|
| 11|     130|      1430|      2058(1.44)|      1787(1.25)|13.17|
| 12|     110|      1320|      1873(1.42)|      1614(1.22)|13.83|
| 13|      67|       871|      1230(1.41)|      1040(1.19)|15.45|
| 14|      61|       854|      1211(1.42)|      1015(1.19)|16.18|
| 15|      52|       780|      1085(1.39)|       924(1.18)|14.84|
| 16|      34|       544|       743(1.37)|       630(1.16)|15.21|
| 17|      11|       187|       256(1.37)|       218(1.17)|14.84|
| 18|      19|       342|       465(1.36)|       392(1.15)|15.70|
| 19|       8|       152|       201(1.32)|       175(1.15)|12.94|
| 20|      10|       200|       268(1.34)|       235(1.18)|12.31|
| 21|       3|        63|        85(1.35)|        75(1.19)|11.76|
| 22|       4|        88|       116(1.32)|        99(1.12)|14.66|
| 23|       3|        69|        89(1.29)|        76(1.10)|14.61|
| 24|       2|        48|        62(1.29)|        55(1.15)|11.29|
| 25|       5|       125|       165(1.32)|       143(1.14)|13.33|
| 26|       2|        52|        67(1.29)|        56(1.08)|16.42|
| 27|       2|        54|        73(1.35)|        61(1.13)|16.44|
| 33|       1|        33|        41(1.24)|        37(1.12)| 9.76|
| 34|       1|        34|        45(1.32)|        36(1.06)|20.00|

|All|    5646|     36537|     58089(1.59)|     51125(1.40)|11.99|

Regards,

Soobok Lee

> 
> So this is a solution in search of a real problem,
> not worth bothering the whole world with additional
> complexity.
> 
> 
> Regards,   Martin.
> 
> 
> At 13:11 01/10/10 +0900, Soobok Lee wrote:
> >Hi, all
> >
> >I am ready to receive any criticisms on REORDERING.
> >Any suggestions of improvements or downsides of REORDERING are all welcome.
> >
> >I expect many feedbacks from non-US and non-European participants and 
> >observers.
> >
> >Thanks.
> >
> >Soobok Lee
> 




From owner-idn@ops.ietf.org  Wed Oct 10 03:18:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05797
	for <idn-archive@lists.ietf.org>; Wed, 10 Oct 2001 03:18:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15rDPu-000JdG-00
	for idn-data@psg.com; Wed, 10 Oct 2001 00:04:34 -0700
Received: from imo-m06.mx.aol.com ([64.12.136.161])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15rDPs-000Jd9-00
	for idn@ops.ietf.org; Wed, 10 Oct 2001 00:04:33 -0700
Received: from DougEwell2@cs.com
	by imo-m06.mx.aol.com (mail_out_v31_r1.8.) id i.96.1b6205fb (24899);
	Wed, 10 Oct 2001 03:04:21 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <96.1b6205fb.28f54cf3@cs.com>
Date: Wed, 10 Oct 2001 03:04:19 EDT
Subject: Re: [idn] WG Update
To: idn@ops.ietf.org
CC: tsenglm@cc.ncu.edu.tw
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a message dated 2001-10-09 23:12:59 Pacific Daylight Time, 
tsenglm@cc.ncu.edu.tw writes:

>> To say that UTF-8 does not preserve case distinctions is complete
>> nonsense.  It is the nameprep stage that folds away case distinctions
>> (for better or worse).
>
>                   If  you mean casing of  Latin characters , you may be
>  right. but you can try the characters in (u+F94D , u+6dda), (u+F950, 
u+7e37)
>  that are compatibility CJK ideograph characters in www.unicode.org .

Neither the compatibility CJK ideographs nor any other CJK ideographs have 
"case" in the sense that bicameral alphabets like Latin, Greek, and Cyrillic 
have "case."  U+F94D and U+6DDA are not upper-case or lower-case forms of one 
another.  The great majority of the compatibility CJK ideographs, and 
specifically the two L.M. Tseng cited, exist solely for round-trip conversion 
from a legacy encoding.

>  If these characters are mapped to single one code point like the  case 
mapping
>  in ASCII , you can not use UTF-8 to do case-like-insensitive comparation 
and
>  to keep case-prserving .  The difference come from the relative to LDH-DNS 
.

Nothing in Unicode or ISO/IEC 10646, and certainly nothing in UTF-8, maps the 
two characters in such a pair to a single code point.  The standard 
cross-references the compatibility characters to the "real" characters, but 
in informative notes only.

>                  I don not against UTF-8 , but AMC-ACE-Z  can support
>  case-code- mapping and case-preserving-after-code-mapping and
>  case-sensitive-comparation all coexisted. It is an intergreted properties 
in
>  LDH-DNS.

I thought nameprep was the mechanism that handled equivalencies like this.  
If AMC-ACE-Z *without nameprep* can equate U+F94D with U+6DDA, it is a lot 
more complicated and requires much larger tables than Adam is letting on.

I suspect the real comparison here is between "UTF-8 without nameprep" and 
"ACE with nameprep."  This is like preferring fresh apples over rotten 
oranges; it has nothing to do with the relative merits of apples and oranges.

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Wed Oct 10 04:29:01 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06589
	for <idn-archive@lists.ietf.org>; Wed, 10 Oct 2001 04:28:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15rESc-000P40-00
	for idn-data@psg.com; Wed, 10 Oct 2001 01:11:26 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15rESb-000P3u-00
	for idn@ops.ietf.org; Wed, 10 Oct 2001 01:11:25 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id RAA24846;
	Wed, 10 Oct 2001 17:11:10 +0900
Message-ID: <03cd01c15163$49547b10$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Dan Ebert" <dan@enic.cc>
Cc: <idn@ops.ietf.org>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se> <20011009004803.28618.qmail@cr.yp.to> <00b501c15078$afb77ce0$ec1bd9d2@temp> <20011009043734.15576.qmail@cr.yp.to> <58648759.1002614060@localhost> <4.2.0.58.J.20011009174223.03c9e400@localhost> <01cf01c150a8$b7fc0800$ec1bd9d2@temp> <3BC31457.3649CC9C@enic.cc>
Subject: Re: [idn] case preservation
Date: Wed, 10 Oct 2001 17:12:19 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id EAA06589


----- Original Message ----- 
From: "Dan Ebert" <dan@enic.cc>
To: "Soobok Lee" <lsb@postel.co.kr>
Cc: "D. J. Bernstein" <djb@cr.yp.to>; <idn@ops.ietf.org>; "Martin Duerst" <duerst@w3.org>
Sent: Wednesday, October 10, 2001 12:14 AM
Subject: Re: [idn] case preservation


> Soobok Lee wrote:
> > 
> > ----- Original Message -----
> > From: "Martin Duerst" <duerst@w3.org>
> > To: "D. J. Bernstein" <djb@cr.yp.to>; <idn@ops.ietf.org>
> >  >
> > > >It would be better to omit nameprep entirely;
> > > >then users will stick to mechanisms that work, such as clicking on URLs.
> > > >(Bad characters should still be avoided in registrations, of course.)
> > >
> > > Bad character combinations should be avoided with registration.
> > > The only registrations for things like <A-Greek><O-Cyrillic><L-Latin>
> > > will come from spoofers, and the only way such spoofers have
> > > a chance is through clicking on URIs or a similar interface.
> > 
> > You forgot to mention this type :
> > All-cyrillic(or All cherokee) uppercase "SEX,CISCO,ATT,HOME,IBM" have the
> > same look with all-latin uppercase ones.
> 
> But, as Martin said, those links will only be 'used' by spoofers and
> only work via clicking on URIs.  

No. Regimate registrants could own the domains and use them publicly.
Cyrillic 'H'  ( cyrillic upper EN) is read differenly from Latin 'H'.
Cyrillic 'HOME' has nothing to do with English "HOME".

>(Things like this already happen anyway
> ... i.e. Someone registers AOL-billing.foo then spams AOL users asking
> for updated credit card info ...) 

the number of such severe security breaches  and confusions matters. 
AOL and  AOL  versus  AOL and AOL-billing ? not comparable.

>If the spoofed domain were printed on
> paper the end user would (most likely) interpret the characters as Latin
> and type them in accordingly and go to the 'real' site, not the spoofed
> site.

Most Russians would interpret them as Cyrillic ones, while non-Russian would not.

Soobok

> 
> > 
> > SOobok
> > 
> > >
> > >
> > > Regards,    Martin.
> > >
> 
> -- 
> Dan Ebert      <dan@enic.cc>       eNIC Corporation
> -----------------------------------------------------
>  "What is wanted is not the will to believe, but the 
>     will to find out, which is the exact opposite."
>        -- Bertrand Russell, "Skeptical_Essays", 1928
> -----------------------------------------------------
> 




From owner-idn@ops.ietf.org  Wed Oct 10 04:46:12 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06712
	for <idn-archive@lists.ietf.org>; Wed, 10 Oct 2001 04:46:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15rEqS-000116-00
	for idn-data@psg.com; Wed, 10 Oct 2001 01:36:04 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15rEqS-00010y-00
	for idn@ops.ietf.org; Wed, 10 Oct 2001 01:36:04 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 4D2E77F45B; Wed, 10 Oct 2001 17:35:33 +0900 (JST)
Message-Id: <4.2.0.58.J.20011010172748.031c8770@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 10 Oct 2001 17:31:08 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, "Dan Ebert" <dan@enic.cc>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] case preservation
Cc: <idn@ops.ietf.org>
In-Reply-To: <03cd01c15163$49547b10$ec1bd9d2@temp>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se>
 <20011009004803.28618.qmail@cr.yp.to>
 <00b501c15078$afb77ce0$ec1bd9d2@temp>
 <20011009043734.15576.qmail@cr.yp.to>
 <58648759.1002614060@localhost>
 <4.2.0.58.J.20011009174223.03c9e400@localhost>
 <01cf01c150a8$b7fc0800$ec1bd9d2@temp>
 <3BC31457.3649CC9C@enic.cc>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 17:12 01/10/10 +0900, Soobok Lee wrote:
>No. Regimate registrants could own the domains and use them publicly.
>Cyrillic 'H'  ( cyrillic upper EN) is read differenly from Latin 'H'.
>Cyrillic 'HOME' has nothing to do with English "HOME".

There is indeed a non-zero (but very, very small) probability
for such cases. But if domain names are written in lower case
the way they mostly have been up to now, a word in a language
written in Cyrillic looking the same as a word in a language
written in Latin would be about as rare as a four-leaf clover.

>Most Russians would interpret them as Cyrillic ones, while non-Russian 
>would not.

Most people will interpret them in context, if necessary.
Machines are very bad at using context, but people
are very good.


Regards,    Martin.



From owner-idn@ops.ietf.org  Wed Oct 10 12:11:27 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13302
	for <idn-archive@lists.ietf.org>; Wed, 10 Oct 2001 12:11:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15rLgl-000BIy-00
	for idn-data@psg.com; Wed, 10 Oct 2001 08:54:31 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15rLgk-000BIs-00
	for idn@ops.ietf.org; Wed, 10 Oct 2001 08:54:30 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id AAA06328;
	Thu, 11 Oct 2001 00:54:05 +0900
Message-ID: <03fa01c151a3$f5ef14d0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Dan Ebert" <dan@enic.cc>, "Martin Duerst" <duerst@w3.org>
Cc: <idn@ops.ietf.org>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se> <20011009004803.28618.qmail@cr.yp.to> <00b501c15078$afb77ce0$ec1bd9d2@temp> <20011009043734.15576.qmail@cr.yp.to> <58648759.1002614060@localhost> <4.2.0.58.J.20011009174223.03c9e400@localhost> <01cf01c150a8$b7fc0800$ec1bd9d2@temp> <3BC31457.3649CC9C@enic.cc> <4.2.0.58.J.20011010172748.031c8770@localhost>
Subject: Re: [idn] case preservation
Date: Thu, 11 Oct 2001 00:55:17 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA13302


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; "Dan Ebert" <dan@enic.cc>
Cc: <idn@ops.ietf.org>
Sent: Wednesday, October 10, 2001 5:31 PM
Subject: Re: [idn] case preservation


> At 17:12 01/10/10 +0900, Soobok Lee wrote:
> >No. Regimate registrants could own the domains and use them publicly.
> >Cyrillic 'H'  ( cyrillic upper EN) is read differenly from Latin 'H'.
> >Cyrillic 'HOME' has nothing to do with English "HOME".
> 
> There is indeed a non-zero (but very, very small) probability
> for such cases. But if domain names are written in lower case
> the way they mostly have been up to now, a word in a language
> written in Cyrillic looking the same as a word in a language
> written in Latin would be about as rare as a four-leaf clover.
> 
Now it may be rare as you said. 
But, LDH.com and LDH.RU are already saturated or
being saturated, while cyrillic ML.com are still 'fresh' 
and waiting for being populated with private companies
by the development of Russian market economy.


> >Most Russians would interpret them as Cyrillic ones, while non-Russian 
> >would not.
> 
> Most people will interpret them in context, if necessary.
> Machines are very bad at using context, but people
> are very good.

The amount of first-time confusions in IDN deployment in Russia may be 
very different than that in China and Korea.
It may need some research how to teach IDN to Russians familiar with
LDH.ru type of domains.

Regards,

Soobok Lee

> 
> 
> Regards,    Martin.
> 




From owner-idn@ops.ietf.org  Wed Oct 10 12:12:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13322
	for <idn-archive@lists.ietf.org>; Wed, 10 Oct 2001 12:12:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15rLjO-000BWW-00
	for idn-data@psg.com; Wed, 10 Oct 2001 08:57:14 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15rLjN-000BVr-00
	for idn@ops.ietf.org; Wed, 10 Oct 2001 08:57:13 -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; Wed, 10 Oct 2001 09:09:32 -0700
Message-ID: <004a01c151a5$8397c560$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se> <20011009004803.28618.qmail@cr.yp.to> <00b501c15078$afb77ce0$ec1bd9d2@temp> <20011009043734.15576.qmail@cr.yp.to> <58648759.1002614060@localhost> <4.2.0.58.J.20011010133945.03d99100@localhost>
Subject: Re: [idn] case preservation
Date: Wed, 10 Oct 2001 12:06:25 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


From: "Martin Duerst" <duerst@w3.org>

> This is a good point. But please note that you don't actually have
> to know whether a character is simplified or traditional. If you
> work on a simplified Chinese system or with a simplified Chinese
> input method, you will just get simplified Chinese characters
> as the first choice from you input method. Same thing the other
> way round for traditional Chinese.
>
You *do* need to know whether the characters of the CDN are
traditional or simplified.  This is analogous to the 'l','1' issue.
One must be aware enough to recognize that the 'l' is the 'lowercase
L' and not the 'number one'.

> This means that if somebody wants to have a domain name usable
> both is China,Singapore,.. and in Taiwan,Hong Kong,..., they
> have to do two registrations. Of course, there are cases where
> there are more registrations needed (e.g. for simplified
> characters used in Taiwan), but these are exceptions.

Yes, this is certainly one of the ways to achieve TC<->SC equivalence.
Again, this is analogous to someone registering both the '1.TLD' and
the 'l.TLD' (or maybe even 'I.TLC') to cover all bases.

>
> Also, for most characters where there is actually a difference
> (there are many cases where there is none, and which are
> therefore unified), it is quite easy to tell whether they
> are simplified or not. The main reason for this is that
> most simplifications are very systematic. Of course, because
> there are so many Chinese characters, there are always some
> that you don't know. That is something that applies to any
> other aspect of Chinese characters.
>

For people who use exclusively TC *or* exclusively SC in their
everyday lives,  it is easier.  However, for people who use them
interchangably, it is much harder.  But in any case, every user must
atleast make the conscious effort to be aware of whether a CND  is SC
or TC much the same as a user must make the conscious effort to be
aware whether 'l.TLD' is a 'number one' or a 'lowercase-L'.

Now... ofcourse, whether this justifies having TC<->SC conversion as a
standard is obviously not up to me to decide... but up to this WG.
(As I have humbly learned from my experience with my "Supreme CDN
system"- although supreme, is not interoperable with others.)
However, I do hope that this analogy using 'l','1','O','0' will
atleast offer much more understanding as to why TC<->SC is such a
critical issue for the Chinese culture.

Thanks,
Ben Chan












From owner-idn@ops.ietf.org  Wed Oct 10 17:16:22 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21437
	for <idn-archive@lists.ietf.org>; Wed, 10 Oct 2001 17:16:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15rQSF-000186-00
	for idn-data@psg.com; Wed, 10 Oct 2001 13:59:51 -0700
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15rQSE-00017y-00
	for idn@ops.ietf.org; Wed, 10 Oct 2001 13:59:50 -0700
Received: from zetnet.co.uk (man-s084.dialup.zetnet.co.uk [194.247.41.211])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f9AKxf406525
        for <idn@ops.ietf.org>; Wed, 10 Oct 2001 21:59:42 +0100
Message-ID: <3BC49CF4.6A1690D6@zetnet.co.uk>
Date: Wed, 10 Oct 2001 20:09:40 +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] Overspecifications in draft-ietf-idn-requirements-08
References: <3BC28B99.E4E7CFB0@zetnet.co.uk>
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-----

I see that there have been no comments on my suggested changes to
draft-ietf-idn-requirements-08.txt. Is that because no-one disagrees
with them, or because no-one has looked at them closely?

- -- 
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

iQEVAwUBO8ScyjkCAxeYt5gVAQEgDwgAkmM6xPhGv9vaAnijZRxbdYRKpBEZ6Ov6
Cc/9oRI3twCicIpaCRvSg3Glwj9kyGEZNcLKN9Mn6nE2rboSviEM7gL1THk8gBbd
+wf2bNAFGlJgQufMvQDIJevEYAKQARdH6xki5d6kqncY1NPcRl2PaTozrjTWv/t7
TZ+r5IGMJMu33GuLKMIx5/TYf8QQvRHEY1uj0q2zOCqE4o2SA6VF5INvJdh1b4io
ywSvbZYxW6z9wqrpKHz2zKOLK+a3Vqu2ChplMWn2+QucdFP4QTKmn1dawkVssj3R
wHx0P1w3ESRrH0og1w/nrDTZioYkT6y2N9RxZoKuLzopdumbA3Wyvw==
=eD2A
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Wed Oct 10 23:36:06 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27447
	for <idn-archive@lists.ietf.org>; Wed, 10 Oct 2001 23:36:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15rWDK-000Gb3-00
	for idn-data@psg.com; Wed, 10 Oct 2001 20:08:50 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15rWDI-000Gaw-00
	for idn@ops.ietf.org; Wed, 10 Oct 2001 20:08:48 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id A2929FFC08; Thu, 11 Oct 2001 11:09:17 +0800 (SGT)
Message-ID: <030701c15202$0742e000$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
References: <3BC28B99.E4E7CFB0@zetnet.co.uk> <3BC49CF4.6A1690D6@zetnet.co.uk>
Subject: Re: [idn] Overspecifications in draft-ietf-idn-requirements-08
Date: Thu, 11 Oct 2001 11:08:40 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I would say more likely the door is already closed on requirements since
we already move it forward. But you never know what would happen...

-James Seng

----- Original Message -----
From: "David Hopwood" <david.hopwood@zetnet.co.uk>
To: <idn@ops.ietf.org>
Sent: Thursday, October 11, 2001 3:09 AM
Subject: Re: [idn] Overspecifications in draft-ietf-idn-requirements-08


> -----BEGIN PGP SIGNED MESSAGE-----
>
> I see that there have been no comments on my suggested changes to
> draft-ietf-idn-requirements-08.txt. Is that because no-one disagrees
> with them, or because no-one has looked at them closely?
>
> - --
> 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
>
> iQEVAwUBO8ScyjkCAxeYt5gVAQEgDwgAkmM6xPhGv9vaAnijZRxbdYRKpBEZ6Ov6
> Cc/9oRI3twCicIpaCRvSg3Glwj9kyGEZNcLKN9Mn6nE2rboSviEM7gL1THk8gBbd
> +wf2bNAFGlJgQufMvQDIJevEYAKQARdH6xki5d6kqncY1NPcRl2PaTozrjTWv/t7
> TZ+r5IGMJMu33GuLKMIx5/TYf8QQvRHEY1uj0q2zOCqE4o2SA6VF5INvJdh1b4io
> ywSvbZYxW6z9wqrpKHz2zKOLK+a3Vqu2ChplMWn2+QucdFP4QTKmn1dawkVssj3R
> wHx0P1w3ESRrH0og1w/nrDTZioYkT6y2N9RxZoKuLzopdumbA3Wyvw==
> =eD2A
> -----END PGP SIGNATURE-----
>




From owner-idn@ops.ietf.org  Thu Oct 11 22:00:28 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01652
	for <idn-archive@lists.ietf.org>; Thu, 11 Oct 2001 22:00:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15rrOB-000Pf5-00
	for idn-data@psg.com; Thu, 11 Oct 2001 18:45:27 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15rrOA-000Pey-00
	for idn@ops.ietf.org; Thu, 11 Oct 2001 18:45:26 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id KAA21165;
	Fri, 12 Oct 2001 10:45:15 +0900
Message-ID: <006301c152bf$b24aeb10$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Subject: [idn] IDNA ACE fallbacks and REORDERING
Date: Fri, 12 Oct 2001 10:46:21 +0900
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_005F_01C1530B.21ABFDF0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_005F_01C1530B.21ABFDF0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit

It is well known that  han font set require very big memory (RAM) spaces.

For 16*16 font,  20992 *  16*16 * (1byte / 8bit) =  0.6 mega bytes
For 24*24 font,  20992 *  24*24 * (1byte / 8bit) =  1.5 mega bytes

For truetype fonts, it may reach 10 Mega bytes.

Therefore, many non-asian handheld devices and even PCs 
won't support  han/hangul rendering to save precious memory resources.
In that case, IDNA-application "SHOULD" show the ACE format of han labels
as the enclosed IDNA section recommends.

THat is, if you send an email to your european friend  with your XXXX@YYYYYY.jp
idn email address,  your friend's PDA (or PC) may not display your han/kana email address
but instead will display ACE format of your email address.
In that case, email address verification relies on eye-comparisons.
Without REORDERING applied, the length of the fallback ACE email address will be
much longer than could have  been shrinked by 10 characters with REORDERING
for many typical email addresses.
Hundreds of longer ACE email addresses will fill  the address book, and exhaust
precious flash memory resource in his/her PDA.

Like DNSSEC, future DNS extensions may require more spaces for long resource 
requests/responses. REORDERING help to solve the problem of lack of spaces 
in DNS packets. Even now, shorter ACE labels will  make it
easy  transcriptions and administrations and eye-comparisons. 
Many non-asian people would prefer to see and verify shorter ACE labels rather than
exotic han/hangul native-script labels which they cannot recognize at all.
Copy&Paste becomes more convenient with shorter ACE labels.

Full Reordering support for major 12 scripts  only requires 13 kbytes memory ram spaces.
This small memory requirement is much less than those for huge font sets,legacy-to-UCS
mappings, and NFKC codes and case mapping tables and prohibition lists in nameprep.

If you are doing cost/benefit analysis on REORDERING, please take these factors into
your considerations.

Thanks.

Soobok Lee

--------------------------------------------------------------------------------

http://www.ietf.org/internet-drafts/draft-ietf-idn-idna-03.txt

2.1.4 Avoiding exposing users to the raw ACE encoding

All applications that might show the user a host name that was received
from a gethostbyaddr or other such lookup SHOULD update as soon as
possible in order to prevent users from seeing the ACE. However, this is
not considered a big problem because so few applications show this type
of resolution to users.

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. In many cases, the application doesn't know exactly
what the underlying rendering engine can or cannot display.

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].


------=_NextPart_000_005F_01C1530B.21ABFDF0
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 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>It is well known =
that&nbsp; han font set=20
require very big memory (RAM)&nbsp;spaces.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>For 16*16 font, =
&nbsp;20992 *&nbsp; 16*16 *=20
(1byte / 8bit) =3D &nbsp;0.6 mega bytes</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>For 24*24 font, =
&nbsp;20992 *&nbsp; 24*24 *=20
(1byte / 8bit) =3D &nbsp;1.5 mega bytes</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>For truetype fonts, it =
may reach 10 Mega=20
bytes.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>Therefore, many =
non-asian handheld devices and=20
even PCs </FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>won't support&nbsp; =
han/hangul rendering=20
</FONT></STRONG><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>to save =
precious memory=20
resources.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>In that case, =
IDNA-application "SHOULD" show=20
the ACE format of han labels</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>as the enclosed =
</FONT></STRONG><STRONG><FONT=20
face=3D=B1=BC=B8=B2 size=3D2>IDNA section =
recommends.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>THat is, if you send an =
email to your european=20
friend &nbsp;with your <A=20
href=3D"mailto:XXXX@YYYYYY.jp">XXXX@YYYYYY.jp</A></FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>idn email address,&nbsp; =
your friend's PDA (or=20
PC)&nbsp;may not display your han/kana email =
address</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>but instead&nbsp;will =
display ACE format of=20
your email address.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>In that case, email =
address verification=20
relies on eye-comparisons.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>Without REORDERING =
applied, the length of the=20
fallback ACE email address will be</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>much longer than could =
have &nbsp;been=20
shrinked by 10 characters with REORDERING</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>for many typical email=20
addresses.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>Hundreds of longer ACE =
email addresses will=20
fill&nbsp; the address book, and exhaust</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>precious flash memory =
resource in his/her=20
PDA.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>Like DNSSEC, future DNS =
extensions may require=20
more spaces for long resource </FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>requests/responses. =
REORDERING help to solve=20
the problem of lack of spaces </FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>in DNS packets. =
</FONT></STRONG><STRONG><FONT=20
face=3D=B1=BC=B8=B2 size=3D2>Even now, shorter ACE labels will&nbsp; =
make=20
it</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>easy =
&nbsp;transcriptions and administrations=20
and eye-comparisons. </FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>Many non-asian people =
would prefer to see and=20
verify shorter ACE labels rather than</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>exotic han/hangul =
native-script&nbsp;labels=20
which they cannot recognize at all.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2>Copy&amp;Paste&nbsp;becomes more=20
</FONT></STRONG><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>convenient =
with shorter ACE=20
labels.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>Full Reordering support =
for major 12=20
scripts&nbsp; only requires 13 kbytes memory ram =
spaces.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>This small memory =
requirement is much less=20
than those for&nbsp;huge font sets,legacy-to-UCS</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>mappings, and NFKC codes =
and case mapping=20
tables and prohibition lists in nameprep.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>If you are doing =
cost/benefit analysis on=20
REORDERING, please take these factors into</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>your =
considerations.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2>Thanks.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>Soobok =
Lee</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2=20
size=3D2>----------------------------------------------------------------=
----------------</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-idn-idna-03.txt">h=
ttp://www.ietf.org/internet-drafts/draft-ietf-idn-idna-03.txt</A></FONT><=
/STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV>2.1.4 Avoiding exposing users to the raw ACE encoding<BR><BR>All=20
applications that might show the user a host name that was =
received<BR>from a=20
gethostbyaddr or other such lookup SHOULD update as soon as<BR>possible =
in order=20
to prevent users from seeing the ACE. However, this is<BR>not considered =
a big=20
problem because so few applications show this type<BR>of resolution to=20
users.<BR><BR>If an application decodes an ACE name but cannot show all =
of=20
the<BR>characters in the decoded name, such as if the name contains=20
characters<BR>that the output system cannot display, the application =
SHOULD show=20
the<BR>name in ACE format instead of displaying the name with the=20
replacement<BR>character (U+FFFD). This is to make it easier for the =
user to=20
transfer<BR>the name correctly to other programs. Programs that by =
default show=20
the<BR>ACE form when they cannot show all the characters in a name part=20
SHOULD<BR>also have a mechanism to show the name with as many characters =

as<BR>possible and replacement characters in the positions where=20
characters<BR>cannot be displayed. In many cases, the application =
doesn't know=20
exactly<BR>what the underlying rendering engine can or cannot =
display.<BR><BR>In=20
addition to the condition above, if an application decodes an =
ACE<BR>name but=20
finds that the decoded name was not properly prepared according<BR>to =
[NAMEPREP]=20
(for example, if it has illegal characters in it), the<BR>application =
SHOULD=20
show the name in ACE format and SHOULD NOT display<BR>the name in its =
decoded=20
form. This is to avoid security issues described<BR>in=20
[NAMEPREP].<BR></DIV></BODY></HTML>

------=_NextPart_000_005F_01C1530B.21ABFDF0--




From owner-idn@ops.ietf.org  Sun Oct 14 12:06:09 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00335
	for <idn-archive@lists.ietf.org>; Sun, 14 Oct 2001 12:06:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15snDY-0009FS-00
	for idn-data@psg.com; Sun, 14 Oct 2001 08:30:20 -0700
From: John C Klensin <klensin@jck.com>
To: idn@ops.ietf.org
Subject: [idn] Re: A Search-based access model & SC/TC conversion 
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15snDY-0009FS-00@psg.com>
Date: Sun, 14 Oct 2001 08:30:20 -0700

Dear L.M.Tseng,

I think I didn't answer this message (ill-formed RFC 2231
headers tend to route mail into a low-priority folder).  My
apologies.

Comments in line below...

--On Thursday, 30 August, 2001 12:09 +0800
"=?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?="
<tsenglm@cc.ncu.edu.tw> wrote:

> Hi !  Klensin:
>            May  I  ask a question related in
> draft-klensin-dns-search-01.txt ?
> 2. A three (or four) search-layer environment.
> (1) The DNS, with the existing lookup mechanisms
> (2) A restricted, facet-based, search system.
> (3) Commercial, localized, and potentially topic-specific,
> search    environments.
> (4) Something else?
> 
>           The current existed and used Letter-Digit-Hyphen DNS
> server is the Layer1 mechanism. Now ,what is the layer of
> nameprep + IDNA  ?

Since it is intended to go into the DNS, it is part of sublayer
1.  Or it is unnecessary, being superceded by better facilities
at sublayer 2.

>  Actually, the native coded multilingual
> domain name  will be treated by AP and passed to nameprep
> module and transfomed to ACE name, the ACE name will be feed to
> resolver of LDH-DNS , so it is backward compatible to pure
> ASCII  domain name.

>            The input of resolver module is the interface of
> Layer2 and Layer1   ?

I think I haven't effectively communicated what is going on
here.    Think about it this way:

Sublayer 3 provides two kinds of services: localization and
anything associated with it and any specialized "yellow pages"
services that may be appropriate to a given area.  While I would
expect that we would ultimately define some sample templates and
protocols, it is not assumed to be a homogeneous Internet-wide
service.

Sublayer 2 provides language-based services, and is sensitive to
a range of social/political issues.  I would expect TC <-> SC
mappings and country-specific case mappings --all of the things
that can't be done in Nameprep without heuristics to determine
what is intended, such as avoiding conversion of Kanji to SC,
French versus Canadian case mapping differences, national and
line of business trademark distinctions, etc-- to occur at
sublayer 2.  And, because this layer is _not_ the DNS, the
various nasty problems involving lengths, need to use
uncomfortable encodings for backward compatibility purposes,
etc., are just not relevant (or can be reconsidered with fewer/
different constraints).

Layer 1 is the DNS.  Whether or not IDN capability is needed
there (IDNA/ACE or otherwise) is an open question, but, if IDN
facilities do appear there, they can, and should, be strictly
character-based.  I.e., no special considerations for particular
languages, different rules for different scripts, etc.

If you read that description from the bottom up, you get the
motivation for doing this.  At sublayer 1 (the DNS) there is
considerable demand for capabilities that are difficult or
impossible to do correctly and consistently at that level,
including all of the language-related issues.  So we push those
issues up a level and use a different set of mechanisms.
Similarly, there is considerable demand for localization to
accomodate local or national needs, but, if localization occurs
at a sufficiently low level, it is a threat to overall
connectivity and interoperation of the Internet.  So we push
that yet another sublayer higher, so that it can be separated
from, e.g., language functions that are still international in
scope (e.g., Chinese is spoken in countries all over the world.
Even though it is not be the majority language in many of them,
it remains important.)

>> > If you can come up with a proposal that describes what to do
>> > about ALL the Han characters in Unicode, I will be very
>> > happy to hear it.

>> And, unless whatever is done is isolated -- through
>> procedures, structure, or layering-- in a way that is robust,
>> accessible to
>           I think the procedures, stucture, or layering is the
> module above layer1 ?
> But it must be between name-input of AP and Layer 1 input
> interface . My question is
> what is the relation betwwen IDNA , Layer 3 , Layaer 2 ,
> nameprep and  Layer 1 ?

I hope the above comments explain this; I will try to clarify it
further in the next revision of the internet draft.

> Does IDNA and nameprep are in the layer of  Layer 2 ?  How a
> restrict facet search system  communicate with Layer1 thru
> which module ?

The contents of the "directory" that is searched by such a
system contains DNS names.  I.e., additional information exists
at each sublayer, with more information (language, country,
etc., in those facets) at sublayer 2 than exists at sublayer 1
(the DNS), where only a string appears at the DNS sublayer.
Now, the DNS name that appears in sublayer 2 can be _any_ name
deemed valid in  the DNS.  If we make IDN names valid there
--via IDNA/ACE processing or otherwise-- it can contain those
names.  But it need not do so: in principle, one could have an
entry of 

{ layer-2-name (proabably an unrestricted,
Unicode-valid, string for the relevant language); TC;
Taiwan; ...} 

pointing to a FQDN most of whose labels were generated names,
i.e., essentially gibberish that conformed to the ASCII LDH
rules.  Whether or not that was desirable would depend on
whether you need mneumonic value in sublayer 1 (DNS) names.  If
you do, then it would make sense to put IDN names in the DNS,
and to push the output of sublayer 2 through stringprep, etc.
If not, one could avoid that small marginal overhead.

Similarly, sublayer 3 could, if desired, be used to map between
names in, e.g., Big5, and Unicode names on a _name_ basis,
resolving any ambiguities that might appear in a pure
character-by-character remapping of the two (conceptually
slightly different because of compromises made in Unicode)
character coding methods.

>     Does there are a defined port or module interface to let
> the isolated function module can be link to cooperation ?

I don't adequately understand this question.  But the purpose of
thinking about this multilayer approach is reexamine
requirements and expectations.  For those that require features
that are incompatible with the design of the DNS, such as
dependencies on the word-formation or grammatical rules of
particular languages, the idea is to provide a reasonable way to
accomodate those features without trying to "trick" the DNS into
supporting them.

I hope that helps clarify what is intended.  If you have
additional questions, I will try to respond to them much more
quickly.

regards,
    john






From owner-idn@ops.ietf.org  Tue Oct 16 02:45:28 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05554
	for <idn-archive@lists.ietf.org>; Tue, 16 Oct 2001 02:45:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15tNaS-000ID1-00
	for idn-data@psg.com; Mon, 15 Oct 2001 23:20:24 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15tNaR-000ICr-00
	for idn@ops.ietf.org; Mon, 15 Oct 2001 23:20:23 -0700
Received: from jamessonyvaio (hs0987.singnet.com.sg [165.21.201.45])
	by mail.i-dns.net (Postfix) with SMTP
	id 70B74FFC09; Tue, 16 Oct 2001 14:20:37 +0800 (SGT)
Message-ID: <001401c1560a$9b5d01b0$c3d715a5@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
References: <3BC28B99.E4E7CFB0@zetnet.co.uk> <3BC49CF4.6A1690D6@zetnet.co.uk> <030701c15202$0742e000$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] Overspecifications in draft-ietf-idn-requirements-08
Date: Tue, 16 Oct 2001 13:40:01 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Let me put it more correctly:

The document is currently under AD review thus it isnt a good idea to
issues an updated draft at this time. However, in the interest of
getting rough consensus, these comments will be taken into account.

-James Seng

----- Original Message -----
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>; <idn@ops.ietf.org>
Sent: Thursday, October 11, 2001 11:08 AM
Subject: Re: [idn] Overspecifications in draft-ietf-idn-requirements-08


> I would say more likely the door is already closed on requirements
since
> we already move it forward. But you never know what would happen...
>
> -James Seng
>
> ----- Original Message -----
> From: "David Hopwood" <david.hopwood@zetnet.co.uk>
> To: <idn@ops.ietf.org>
> Sent: Thursday, October 11, 2001 3:09 AM
> Subject: Re: [idn] Overspecifications in
draft-ietf-idn-requirements-08
>
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> >
> > I see that there have been no comments on my suggested changes to
> > draft-ietf-idn-requirements-08.txt. Is that because no-one disagrees
> > with them, or because no-one has looked at them closely?
> >
> > - --
> > 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
> >
> > iQEVAwUBO8ScyjkCAxeYt5gVAQEgDwgAkmM6xPhGv9vaAnijZRxbdYRKpBEZ6Ov6
> > Cc/9oRI3twCicIpaCRvSg3Glwj9kyGEZNcLKN9Mn6nE2rboSviEM7gL1THk8gBbd
> > +wf2bNAFGlJgQufMvQDIJevEYAKQARdH6xki5d6kqncY1NPcRl2PaTozrjTWv/t7
> > TZ+r5IGMJMu33GuLKMIx5/TYf8QQvRHEY1uj0q2zOCqE4o2SA6VF5INvJdh1b4io
> > ywSvbZYxW6z9wqrpKHz2zKOLK+a3Vqu2ChplMWn2+QucdFP4QTKmn1dawkVssj3R
> > wHx0P1w3ESRrH0og1w/nrDTZioYkT6y2N9RxZoKuLzopdumbA3Wyvw==
> > =eD2A
> > -----END PGP SIGNATURE-----
> >
>
>




From owner-idn@ops.ietf.org  Tue Oct 16 20:14:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23126
	for <idn-archive@lists.ietf.org>; Tue, 16 Oct 2001 20:14:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15tdeV-0009AQ-00
	for idn-data@psg.com; Tue, 16 Oct 2001 16:29:39 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15tdeT-0009AK-00
	for idn@ops.ietf.org; Tue, 16 Oct 2001 16:29:37 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VV0zfFSROqf8udXXJJ4mhzuA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GHWLKMH8; Tue, 16 Oct 2001 19:28:23 EDT
To: klensin@jck.com
Cc: tsenglm@cc.ncu.edu.tw, harald@alvestrand.no, James@Seng.cc,
        huangk@alum.sinica.edu, idn@ops.ietf.org, dhc@dcrocker.net
Date: Tue, 16 Oct 2001 16:49:13 -0700
Subject: [idn] Re: A Search-based access model & SC/TC conversion
Message-ID: <20011016.164915.-763873.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-66,68-222
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, John:
  I have redescribed all the models  
somewhat graphicly as following.  If this does 
not lineup clearly, please let me know.

 Raw input         ?IDN?                 output

DNS Model:
1) Key Stroke   --> Input Processing --> DNS

IDN Model:
   Vioce       |
2) URI line    |--> Input Processing --> DNS
   Input beffer|

John's Driectory Model:

   Vioce       |
3) URI line    |    layer1: [nameprep]   --> DNS
   Input beffer|
                \   layer2: TC/SC 
                 \  layer3: GB/BIG5
                  \         Yellow pages
                   \---^

CJK arguing for:

   Vioce       |[nameprep??]
4) URI line    |-->      layer1:          --> DNS
   Input beffer|
                \-->     layer2: TC/SC 
                 \->     layer3: GB/BIG5
                                 Yellow pages

Idn-map Proposed Model:                  

   Vioce       |[idnmap]
5) URI line    |-->     layer1:          --> DNS
   Input beffer|-->           TC/SC
                \-->          GB/BIG5
                 \     
                  \     Layer2: Yellow Page
                   \    Layer3: User error check   
                    \---^
  
The basic difference between 3) and 4,5) is where
the symbol table is used. In 3) the symbol table is 
UCS plane 0, from 0020 to d7af, about 56,000 symbols.

How to use the 56,000 symbol table is the difference
between 3) and 4,5). In 3) the process uses 

Local GB coded Yellow page search??
   |
   v
GB/BIG5 to Unicode conversion  
   |
   v
Unicode: TC/SC conversion
   |
   v
Unicode to ACE conversion for DNS

Am I correct in describing your model? 

Liana

On Sat, 13 Oct 2001 15:11:41 -0400 John C Klensin <klensin@jck.com>
writes:
> Dear L.M.Tseng,
> 
> I think I didn't answer this message (ill-formed RFC 2231
> headers tend to route mail into a low-priority folder).  My
> apologies.
> 
> Comments in line below...
> 
> --On Thursday, 30 August, 2001 12:09 +0800
> "=?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?="
> <tsenglm@cc.ncu.edu.tw> wrote:
> 
> > Hi !  Klensin:
> >            May  I  ask a question related in
> > draft-klensin-dns-search-01.txt ?
> > 2. A three (or four) search-layer environment.
> > (1) The DNS, with the existing lookup mechanisms
> > (2) A restricted, facet-based, search system.
> > (3) Commercial, localized, and potentially topic-specific,
> > search    environments.
> > (4) Something else?
> > 
> >           The current existed and used Letter-Digit-Hyphen DNS
> > server is the Layer1 mechanism. Now ,what is the layer of
> > nameprep + IDNA  ?
> 
> Since it is intended to go into the DNS, it is part of sublayer
> 1.  Or it is unnecessary, being superceded by better facilities
> at sublayer 2.
> 
> >  Actually, the native coded multilingual
> > domain name  will be treated by AP and passed to nameprep
> > module and transfomed to ACE name, the ACE name will be feed to
> > resolver of LDH-DNS , so it is backward compatible to pure
> > ASCII  domain name.
> 
> >            The input of resolver module is the interface of
> > Layer2 and Layer1   ?
> 
> I think I haven't effectively communicated what is going on
> here.    Think about it this way:
> 
> Sublayer 3 provides two kinds of services: localization and
> anything associated with it and any specialized "yellow pages"
> services that may be appropriate to a given area.  While I would
> expect that we would ultimately define some sample templates and
> protocols, it is not assumed to be a homogeneous Internet-wide
> service.
> 
> Sublayer 2 provides language-based services, and is sensitive to
> a range of social/political issues.  I would expect TC <-> SC
> mappings and country-specific case mappings --all of the things
> that can't be done in Nameprep without heuristics to determine
> what is intended, such as avoiding conversion of Kanji to SC,
> French versus Canadian case mapping differences, national and
> line of business trademark distinctions, etc-- to occur at
> sublayer 2.  And, because this layer is _not_ the DNS, the
> various nasty problems involving lengths, need to use
> uncomfortable encodings for backward compatibility purposes,
> etc., are just not relevant (or can be reconsidered with fewer/
> different constraints).
> 
> Layer 1 is the DNS.  Whether or not IDN capability is needed
> there (IDNA/ACE or otherwise) is an open question, but, if IDN
> facilities do appear there, they can, and should, be strictly
> character-based.  I.e., no special considerations for particular
> languages, different rules for different scripts, etc.
> 
> If you read that description from the bottom up, you get the
> motivation for doing this.  At sublayer 1 (the DNS) there is
> considerable demand for capabilities that are difficult or
> impossible to do correctly and consistently at that level,
> including all of the language-related issues.  So we push those
> issues up a level and use a different set of mechanisms.
> Similarly, there is considerable demand for localization to
> accomodate local or national needs, but, if localization occurs
> at a sufficiently low level, it is a threat to overall
> connectivity and interoperation of the Internet.  So we push
> that yet another sublayer higher, so that it can be separated
> from, e.g., language functions that are still international in
> scope (e.g., Chinese is spoken in countries all over the world.
> Even though it is not be the majority language in many of them,
> it remains important.)
> 
> >> > If you can come up with a proposal that describes what to do
> >> > about ALL the Han characters in Unicode, I will be very
> >> > happy to hear it.
> 
> >> And, unless whatever is done is isolated -- through
> >> procedures, structure, or layering-- in a way that is robust,
> >> accessible to
> >           I think the procedures, stucture, or layering is the
> > module above layer1 ?
> > But it must be between name-input of AP and Layer 1 input
> > interface . My question is
> > what is the relation betwwen IDNA , Layer 3 , Layaer 2 ,
> > nameprep and  Layer 1 ?
> 
> I hope the above comments explain this; I will try to clarify it
> further in the next revision of the internet draft.
> 
> > Does IDNA and nameprep are in the layer of  Layer 2 ?  How a
> > restrict facet search system  communicate with Layer1 thru
> > which module ?
> 
> The contents of the "directory" that is searched by such a
> system contains DNS names.  I.e., additional information exists
> at each sublayer, with more information (language, country,
> etc., in those facets) at sublayer 2 than exists at sublayer 1
> (the DNS), where only a string appears at the DNS sublayer.
> Now, the DNS name that appears in sublayer 2 can be _any_ name
> deemed valid in  the DNS.  If we make IDN names valid there
> --via IDNA/ACE processing or otherwise-- it can contain those
> names.  But it need not do so: in principle, one could have an
> entry of 
> 
> 	{ layer-2-name (proabably an unrestricted,
> 	Unicode-valid, string for the relevant language); TC;
> 	Taiwan; ...} 
> 
> pointing to a FQDN most of whose labels were generated names,
> i.e., essentially gibberish that conformed to the ASCII LDH
> rules.  Whether or not that was desirable would depend on
> whether you need mneumonic value in sublayer 1 (DNS) names.  If
> you do, then it would make sense to put IDN names in the DNS,
> and to push the output of sublayer 2 through stringprep, etc.
> If not, one could avoid that small marginal overhead.
> 
> Similarly, sublayer 3 could, if desired, be used to map between
> names in, e.g., Big5, and Unicode names on a _name_ basis,
> resolving any ambiguities that might appear in a pure
> character-by-character remapping of the two (conceptually
> slightly different because of compromises made in Unicode)
> character coding methods.
> 
> >     Does there are a defined port or module interface to let
> > the isolated function module can be link to cooperation ?
> 
> I don't adequately understand this question.  But the purpose of
> thinking about this multilayer approach is reexamine
> requirements and expectations.  For those that require features
> that are incompatible with the design of the DNS, such as
> dependencies on the word-formation or grammatical rules of
> particular languages, the idea is to provide a reasonable way to
> accomodate those features without trying to "trick" the DNS into
> supporting them.
> 
> I hope that helps clarify what is intended.  If you have
> additional questions, I will try to respond to them much more
> quickly.
> 
> regards,
>     john
> 



From owner-idn@ops.ietf.org  Tue Oct 16 21:38:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24806
	for <idn-archive@lists.ietf.org>; Tue, 16 Oct 2001 21:38:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15tfQz-000B8N-00
	for idn-data@psg.com; Tue, 16 Oct 2001 18:23:49 -0700
Received: from [203.207.0.132] (helo=mail.asiainfra.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15tfQx-000B8H-00
	for idn@ops.ietf.org; Tue, 16 Oct 2001 18:23:47 -0700
Received: from gix ([159.226.1.126])
	by mail.asiainfra.com (8.9.3/8.9.3) with SMTP id JAA10710;
	Wed, 17 Oct 2001 09:23:00 +0800
From: "Kenny Huang" <huangk@alum.sinica.edu>
To: <liana.ydisg@juno.com>, <klensin@jck.com>
Cc: <tsenglm@cc.ncu.edu.tw>, <harald@alvestrand.no>, <James@Seng.cc>,
        <idn@ops.ietf.org>, <dhc@dcrocker.net>
Subject: RE: [idn] Re: A Search-based access model & SC/TC conversion
Date: Wed, 17 Oct 2001 09:27:40 +0800
Message-ID: <IHELIFNJKJLDFEMBCENDKEPKCHAA.huangk@alum.sinica.edu>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
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.4807.1700
Importance: Normal
In-Reply-To: <20011016.164915.-763873.1.liana.ydisg@juno.com>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA24806

If IDN only take care internationalization issue, what is the mechanism to integrate
localization (TS/TC, JPCHAR..,etc) into the framework ?  If there is no clear interface
in IDN structure, the yellow search model would be the only way out.

Kenny Huang

> -----Original Message-----
> From: owner-idn@ops.ietf.org [mailto:owner-idn@ops.ietf.org]On Behalf Of
> liana.ydisg@juno.com
> Sent: Wednesday, October 17, 2001 7:49 AM
> To: klensin@jck.com
> Cc: tsenglm@cc.ncu.edu.tw; harald@alvestrand.no; James@Seng.cc;
> huangk@alum.sinica.edu; idn@ops.ietf.org; dhc@dcrocker.net
> Subject: [idn] Re: A Search-based access model & SC/TC conversion
> 
> The basic difference between 3) and 4,5) is where
> the symbol table is used. In 3) the symbol table is 
> UCS plane 0, from 0020 to d7af, about 56,000 symbols.
> 
> How to use the 56,000 symbol table is the difference
> between 3) and 4,5). In 3) the process uses 
> 
> Local GB coded Yellow page search??
>    |
>    v
> GB/BIG5 to Unicode conversion  
>    |
>    v
> Unicode: TC/SC conversion
>    |
>    v
> Unicode to ACE conversion for DNS
> 
> Am I correct in describing your model? 
> 
> Liana
> 




From owner-idn@ops.ietf.org  Tue Oct 16 22:29:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25225
	for <idn-archive@lists.ietf.org>; Tue, 16 Oct 2001 22:29:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15tgJ9-000CEd-00
	for idn-data@psg.com; Tue, 16 Oct 2001 19:19:47 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15tgJ8-000CEX-00
	for idn@ops.ietf.org; Tue, 16 Oct 2001 19:19:46 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id LAA22069;
	Wed, 17 Oct 2001 11:18:21 +0900
Message-ID: <002401c156b2$23272560$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Kenny Huang" <huangk@alum.sinica.edu>, <liana.ydisg@juno.com>,
        <klensin@jck.com>
Cc: <tsenglm@cc.ncu.edu.tw>, <harald@alvestrand.no>, <James@Seng.cc>,
        <idn@ops.ietf.org>, <dhc@dcrocker.net>
References: <IHELIFNJKJLDFEMBCENDKEPKCHAA.huangk@alum.sinica.edu>
Subject: Re: [idn] Re: A Search-based access model & SC/TC conversion
Date: Wed, 17 Oct 2001 11:19:23 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id WAA25225


----- Original Message ----- 
From: "Kenny Huang" <huangk@alum.sinica.edu>
To: <liana.ydisg@juno.com>; <klensin@jck.com>
Cc: <tsenglm@cc.ncu.edu.tw>; <harald@alvestrand.no>; <James@Seng.cc>; <idn@ops.ietf.org>; <dhc@dcrocker.net>
Sent: Wednesday, October 17, 2001 10:27 AM
Subject: RE: [idn] Re: A Search-based access model & SC/TC conversion


> If IDN only take care internationalization issue, what is the mechanism to integrate
> localization (TS/TC, JPCHAR..,etc) into the framework ?  If there is no clear interface
> in IDN structure, the yellow search model would be the only way out.
> 
I agree.   
Without a certain "mandatory & clear" interface between IDN and the DNS search 
facility,  some applications would bypass this search layer and  run without any
TC/SC, jpchar, hangeulchar filtering. That is, they may make a direct  function call
into  "gethostbyname(ACE("ML.com")) without any interaction with the
DNS search agent for resolving potential ambiguities.

the mandatory search-based access model  may not be applicable to
non-interative applications like  email clients. Most email composing interfaces
do  not provide  interactive hostname-part validator for  recipients' email addresses.

It is very clear that the i18n mailbox-parts in IDN email addresses 
will inherit  all the issues of ambiguities of IDN hostname-parts.
the existences/details of hostnames can verified publicly, but the mailbox names
are often kept privately and therefore  we cannot apply public yellow/white page
search model on them.

Careful registration procedures are required  for both of IDN hostnames and IDN mailbox
names, because we cannot completely eliminate ambiguities from IDN through
mechinical processes like NAMEPREP. 
To minimize such global management overheads of IDN deployments, 
we should do our best to make nameprep/ACE  as perfect and general and efficient as possible,  within  time and resources  given to us.


Soobok Lee

> Kenny Huang
> 
> > -----Original Message-----
> > From: owner-idn@ops.ietf.org [mailto:owner-idn@ops.ietf.org]On Behalf Of
> > liana.ydisg@juno.com
> > Sent: Wednesday, October 17, 2001 7:49 AM
> > To: klensin@jck.com
> > Cc: tsenglm@cc.ncu.edu.tw; harald@alvestrand.no; James@Seng.cc;
> > huangk@alum.sinica.edu; idn@ops.ietf.org; dhc@dcrocker.net
> > Subject: [idn] Re: A Search-based access model & SC/TC conversion
> > 
> > The basic difference between 3) and 4,5) is where
> > the symbol table is used. In 3) the symbol table is 
> > UCS plane 0, from 0020 to d7af, about 56,000 symbols.
> > 
> > How to use the 56,000 symbol table is the difference
> > between 3) and 4,5). In 3) the process uses 
> > 
> > Local GB coded Yellow page search??
> >    |
> >    v
> > GB/BIG5 to Unicode conversion  
> >    |
> >    v
> > Unicode: TC/SC conversion
> >    |
> >    v
> > Unicode to ACE conversion for DNS
> > 
> > Am I correct in describing your model? 
> > 
> > Liana
> > 
> 
> 




From owner-idn@ops.ietf.org  Thu Oct 18 03:44:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01807
	for <idn-archive@lists.ietf.org>; Thu, 18 Oct 2001 03:44:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15u7Lu-000HdE-00
	for idn-data@psg.com; Thu, 18 Oct 2001 00:12:26 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15u7Lt-000Hd8-00
	for idn@ops.ietf.org; Thu, 18 Oct 2001 00:12:25 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id QAA07731;
	Thu, 18 Oct 2001 16:11:58 +0900
Message-ID: <009901c157a4$55d3c700$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>, "Dan Ebert" <dan@enic.cc>,
        "Martin Duerst" <duerst@w3.org>
Cc: <idn@ops.ietf.org>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se> <20011009004803.28618.qmail@cr.yp.to> <00b501c15078$afb77ce0$ec1bd9d2@temp> <20011009043734.15576.qmail@cr.yp.to> <58648759.1002614060@localhost> <4.2.0.58.J.20011009174223.03c9e400@localhost> <01cf01c150a8$b7fc0800$ec1bd9d2@temp> <3BC31457.3649CC9C@enic.cc> <4.2.0.58.J.20011010172748.031c8770@localhost> <03fa01c151a3$f5ef14d0$ec1bd9d2@temp>
Subject: Re: [idn] case preservation
Date: Thu, 18 Oct 2001 16:13:01 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id DAA01807

some corrections:

----- Original Message ----- 
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Dan Ebert" <dan@enic.cc>; "Martin Duerst" <duerst@w3.org>
Cc: <idn@ops.ietf.org>
Sent: Thursday, October 11, 2001 12:55 AM
Subject: Re: [idn] case preservation


> 
> ----- Original Message ----- 
> From: "Martin Duerst" <duerst@w3.org>
> To: "Soobok Lee" <lsb@postel.co.kr>; "Dan Ebert" <dan@enic.cc>
> Cc: <idn@ops.ietf.org>
> Sent: Wednesday, October 10, 2001 5:31 PM
> Subject: Re: [idn] case preservation
> 
> 
> > At 17:12 01/10/10 +0900, Soobok Lee wrote:
> > >No. Regimate registrants could own the domains and use them publicly.
> > >Cyrillic 'H'  ( cyrillic upper EN) is read differenly from Latin 'H'.
> > >Cyrillic 'HOME' has nothing to do with English "HOME".
> > 
> > There is indeed a non-zero (but very, very small) probability
> > for such cases. But if domain names are written in lower case
> > the way they mostly have been up to now, a word in a language
> > written in Cyrillic looking the same as a word in a language
> > written in Latin would be about as rare as a four-leaf clover.
> > 

No. mcuh more  frequent than you guess.

Cyrillic small 'a' 'e' 'o' 'c' 'p' 'x' 'y'  'i' 'j' 's' have the exactly same look with latin small ones. All word combinations of them will collide with LDH.ru ones.
For example, lowercased Cyrillic  "cape, sexy, epoxy, ceo, pay, cpa "
cannot be distinguished from english ones in most rendering environments.

see http://www.unicode.org/charts/PDF/U0400.pdf

Only Cyrillic 'B' 'H' 'M' 'T' have lowercase forms which look the same with uppercase ones.

Soobok Lee


 




From owner-idn@ops.ietf.org  Thu Oct 18 05:42:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03024
	for <idn-archive@lists.ietf.org>; Thu, 18 Oct 2001 05:42:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15u9Xd-000Jd8-00
	for idn-data@psg.com; Thu, 18 Oct 2001 02:32:41 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15u9Xc-000Jd2-00
	for idn@ops.ietf.org; Thu, 18 Oct 2001 02:32:40 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id C51317F4B6; Thu, 18 Oct 2001 18:31:53 +0900 (JST)
Message-Id: <4.2.0.58.J.20011018182644.06bba6c0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 18 Oct 2001 18:32:20 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, "Soobok Lee" <lsb@postel.co.kr>,
        "Dan Ebert" <dan@enic.cc>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] case preservation
Cc: <idn@ops.ietf.org>
In-Reply-To: <009901c157a4$55d3c700$ec1bd9d2@temp>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se>
 <20011009004803.28618.qmail@cr.yp.to>
 <00b501c15078$afb77ce0$ec1bd9d2@temp>
 <20011009043734.15576.qmail@cr.yp.to>
 <58648759.1002614060@localhost>
 <4.2.0.58.J.20011009174223.03c9e400@localhost>
 <01cf01c150a8$b7fc0800$ec1bd9d2@temp>
 <3BC31457.3649CC9C@enic.cc>
 <4.2.0.58.J.20011010172748.031c8770@localhost>
 <03fa01c151a3$f5ef14d0$ec1bd9d2@temp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 16:13 01/10/18 +0900, Soobok Lee wrote:

> > > There is indeed a non-zero (but very, very small) probability
> > > for such cases. But if domain names are written in lower case
> > > the way they mostly have been up to now, a word in a language
> > > written in Cyrillic looking the same as a word in a language
> > > written in Latin would be about as rare as a four-leaf clover.
> > >
>
>No. mcuh more  frequent than you guess.
>
>Cyrillic small 'a' 'e' 'o' 'c' 'p' 'x' 'y'  'i' 'j' 's' have the exactly 
>same look with latin small ones.

Yes. But 'i' 'j' 's' are not actually used in most languages
that are written in Cyrillic. And in all languages, most of
the possible letter combinations are not actually used. And
the longer a word is, the more quickly the probabilities
approach zero.


Regards,   Martin.



From owner-idn@ops.ietf.org  Thu Oct 18 07:51:35 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04934
	for <idn-archive@lists.ietf.org>; Thu, 18 Oct 2001 07:51:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uBRn-000M2r-00
	for idn-data@psg.com; Thu, 18 Oct 2001 04:34:47 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uBRm-000M2l-00
	for idn@ops.ietf.org; Thu, 18 Oct 2001 04:34:46 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id UAA24982;
	Thu, 18 Oct 2001 20:34:23 +0900
Message-ID: <00f501c157c8$fee21670$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Dan Ebert" <dan@enic.cc>, "Martin Duerst" <duerst@w3.org>
Cc: <idn@ops.ietf.org>
References: <200110080633.f986Xuj26651@valinor.malmo.trab.se> <20011009004803.28618.qmail@cr.yp.to> <00b501c15078$afb77ce0$ec1bd9d2@temp> <20011009043734.15576.qmail@cr.yp.to> <58648759.1002614060@localhost> <4.2.0.58.J.20011009174223.03c9e400@localhost> <01cf01c150a8$b7fc0800$ec1bd9d2@temp> <3BC31457.3649CC9C@enic.cc> <4.2.0.58.J.20011010172748.031c8770@localhost> <03fa01c151a3$f5ef14d0$ec1bd9d2@temp> <4.2.0.58.J.20011018182644.06bba6c0@localhost>
Subject: Re: [idn] case preservation
Date: Thu, 18 Oct 2001 20:35:26 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA04934


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; "Soobok Lee" <lsb@postel.co.kr>; "Dan Ebert" <dan@enic.cc>
Cc: <idn@ops.ietf.org>
Sent: Thursday, October 18, 2001 6:32 PM
Subject: Re: [idn] case preservation


> At 16:13 01/10/18 +0900, Soobok Lee wrote:
> 
> > > > There is indeed a non-zero (but very, very small) probability
> > > > for such cases. But if domain names are written in lower case
> > > > the way they mostly have been up to now, a word in a language
> > > > written in Cyrillic looking the same as a word in a language
> > > > written in Latin would be about as rare as a four-leaf clover.
> > > >
> >
> >No. mcuh more  frequent than you guess.
> >
> >Cyrillic small 'a' 'e' 'o' 'c' 'p' 'x' 'y'  'i' 'j' 's' have the exactly 
> >same look with latin small ones.
> 
> Yes. But 'i' 'j' 's' are not actually used in most languages
> that are written in Cyrillic. And in all languages, most of
> the possible letter combinations are not actually used. And
> the longer a word is, the more quickly the probabilities
> approach zero.
> 


 the _SUM_ of the probability for every word length 1..big N   may converge to
a certain non-zero value that should not be neglected. With 'HMTB',it will be much bigger than that.

it's well known that all 3 letter labels are registered in LDH.com,.net,.org.
every 3-letter cyrillic label from 'aeocpxy' collides with a 3-letter LDH.com .
"copy.com" "coca.com" "ec.com" "ace.com" "eco.com" "ocx.com" "oxy.com" "cap.com" ....   :-))

 Cyrillic 'i' 'j' 's' are not used in Russian. But, as you know,
 'j' is used in serbian,azerbaijani language in cyrillic script.
 and 'i' is ByeloRussian-Ukrainian 'I'.  
Are these characters extinct or live?


Soobok Lee

> 
> Regards,   Martin.
> 




From owner-idn@ops.ietf.org  Thu Oct 18 23:05:02 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25024
	for <idn-archive@lists.ietf.org>; Thu, 18 Oct 2001 23:05:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uPY7-000Ld2-00
	for idn-data@psg.com; Thu, 18 Oct 2001 19:38:15 -0700
Received: from smtp23.singnet.com.sg ([165.21.101.203])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uPY6-000Lcw-00
	for idn@ops.ietf.org; Thu, 18 Oct 2001 19:38:14 -0700
Received: from jamessonyvaio (58alpha085.singnet.com.sg [165.21.208.95])
	by smtp23.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9J2eex18314;
	Fri, 19 Oct 2001 10:40:41 +0800
Message-ID: <024b01c15847$11e8b430$0501000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 09:09:03 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I would like to add my comments to this:

Reordering increases efficient of the encoding allowing longer labels.
This allows us to go sometimes as much as 25% more. OTOH, as IDN as a
form of identifiers, then practically, shorter labels are better. Aside,
re-ordering also increases the complexity of the algorithm. This is an
engineering trade-off we have to made should we consider re-ordering.

The bigger concern I have with re-ordering remains in the fact that
tables mappings proves efficient with existing IDN names in some
registries *BUT* it  does not indicate what performance it would be like
in the future. We do not know what happened when the names space get
saturated and would other names which would have been useable without
lsb become un-usuable due to lsb.

And with the existing draft, it does not explain how it going to deal
with new codepoints in ISO10646 in the future, nor does it explain the
process to implementing them. The critia here is stablity - if new code
is added and tables for re-ordering expand, then the algorithm should
not make existing names invalided.

Third, I would really prefer to reference a work from established expert
group if possible. For example, ISO/IEC JTC1/SC22/WG20 publishes ISO
14651 on weighted sorting. I am not sure how ISO 14651 would perform for
the IDN purpose but I thought it might be worthwhile to examine.

Whatever the case, we should make a decision quickly on this. Lets not
drag this further if possible.

-James Seng

----- Original Message -----
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
Sent: Wednesday, October 10, 2001 1:16 PM
Subject: Re: [idn] call for comments for REORDERING


> Hello Soobok,
>
> Here are my comments on reordering. Apologies if they are
> too clear.
>
> The additional complexity introduced by reordering is a very
> serious problem. It is true that this complexity is somewhat
> similar to the complexity of e.g. nameprep or conversion from
> a legacy encoding. However, on many platforms, both conversion
> from a legacy encoding as well as many aspects of nameprep
> are available as libraries, and are used for other purposes.
> In particular on constrained devices (mobile phones,...),
> most of nameprep can be simplified a lot if one knows what
> kinds of characters can be input.
>
> On the other hand, the benefits for the users are actually
> very small. Nobody wants to input domain names with 15 or
> more Hanzi or Hangul. Nobody will be able to remember them.
> Writing them down on a napkin will take a long time.
> Every company or organization that has such a long label
> in their domain name, and no shorter alternative, will
> simply not get any contacts directly to their web site.
> If they have a short alternative, why do they need a
> long version? (please note that there is no danger of
> spoofing by somebody else getting the long version :-).
>
> So this is a solution in search of a real problem,
> not worth bothering the whole world with additional
> complexity.
>
>
> Regards,   Martin.
>
>
> At 13:11 01/10/10 +0900, Soobok Lee wrote:
> >Hi, all
> >
> >I am ready to receive any criticisms on REORDERING.
> >Any suggestions of improvements or downsides of REORDERING are all
welcome.
> >
> >I expect many feedbacks from non-US and non-European participants and
> >observers.
> >
> >Thanks.
> >
> >Soobok Lee
>
>




From owner-idn@ops.ietf.org  Thu Oct 18 23:26:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25150
	for <idn-archive@lists.ietf.org>; Thu, 18 Oct 2001 23:26:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uQ54-000Mbp-00
	for idn-data@psg.com; Thu, 18 Oct 2001 20:12:18 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uQ53-000Mbj-00
	for idn@ops.ietf.org; Thu, 18 Oct 2001 20:12:17 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id MAA23721;
	Fri, 19 Oct 2001 12:12:00 +0900
Message-ID: <003d01c1584b$f90b66b0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 12:13:01 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id XAA25150

HI, James

I will answer one by one for your  questions.

----- Original Message ----- 
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>; "Martin Duerst" <duerst@w3.org>
Sent: Friday, October 19, 2001 10:09 AM
Subject: Re: [idn] call for comments for REORDERING


> 
> And with the existing draft, it does not explain how it going to deal
> with new codepoints in ISO10646 in the future, nor does it explain the
> process to implementing them. The critia here is stablity - if new code
> is added and tables for re-ordering expand, then the algorithm should
> not make existing names invalided.

REORDERING's mapping occurs within each script block, NOT across script blocks.
Therefore, new additions of script block won't invalidate or collide
with existing names. Even additions of new rarely used characters in 
existing script block won't affect the performance of REORDERING.
In this respect, REORDERING maintains stability over time.

Current IDNA/nameprep does not prohibit, but discourage including unassigned code points in legal IDN labels, because new normalization/case mappings
would be defined on them in the future. some ACE labels including unsigned code block (tagalog?) might be proven invalid in the future. Nameprep/NFKC Versioning tag schems using new ACE prefix will be needed in the future, i guess.

Therefore, REORDERING  follows the same IDNA/nameprep recommendations on the issues
of new SCTIPT blocks/unsigned code points. 

This statements will be included in the final version of REORDERING I-D.

Thanks.

Soobok Lee






From owner-idn@ops.ietf.org  Thu Oct 18 23:36:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25576
	for <idn-archive@lists.ietf.org>; Thu, 18 Oct 2001 23:36:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uQKh-000N7h-00
	for idn-data@psg.com; Thu, 18 Oct 2001 20:28:27 -0700
Received: from inergen.sybase.com ([192.138.151.43])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uQKg-000N7b-00
	for idn@ops.ietf.org; Thu, 18 Oct 2001 20:28:26 -0700
Received: from smtp2.sybase.com (sybgate2.sybase.com [130.214.69.6])
	by inergen.sybase.com  with ESMTP id UAA24698;
	Thu, 18 Oct 2001 20:27:33 -0700 (PDT)
Received: from olympus.sybase.com (localhost [127.0.0.1])
	by smtp2.sybase.com  with ESMTP id UAA09362;
	Thu, 18 Oct 2001 20:28:25 -0700 (PDT)
Received: from birdie.sybase.com by olympus.sybase.com (8.8.8+Sun/SMI-SVR4/SybEC3.5)
	id UAA11297; Thu, 18 Oct 2001 20:28:24 -0700 (PDT)
Received: (from kenw@localhost)
	by birdie.sybase.com (8.8.8+Sun/8.8.8) id UAA15512;
	Thu, 18 Oct 2001 20:28:24 -0700 (PDT)
Date: Thu, 18 Oct 2001 20:28:24 -0700 (PDT)
From: Kenneth Whistler <kenw@sybase.com>
Message-Id: <200110190328.UAA15512@birdie.sybase.com>
To: jseng@pobox.org.sg
Subject: Re: [idn] call for comments for REORDERING
Cc: idn@ops.ietf.org
X-Sun-Charset: US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James Seng said:

> Third, I would really prefer to reference a work from established expert
> group if possible. For example, ISO/IEC JTC1/SC22/WG20 publishes ISO
> 14651 on weighted sorting. I am not sure how ISO 14651 would perform for
> the IDN purpose but I thought it might be worthwhile to examine.

As one of the principal authors of ISO 14651, who has also implemented
the synchronized Unicode Technical Standard #10, the Unicode Collation
Algorithm, I can attest that this is a very tricky and complicated
area, and the algorithms to do all this correctly are not the kind
you can write on the back of a cocktail napkin. It is very complex
to get all the details right and to get good-performing algorithms
(in speed and in resource usage). It is also very difficult for
independent implementations to get themselves all exactly lined
up, and even more difficult for independent implementations to *prove*
that they are getting the same results for all data (as opposed to
a particular result for one set of data -- which is pretty easy).

IDN doesn't need to add this kind of headache to the already
complex enough issues of nameprep.

> 
> Whatever the case, we should make a decision quickly on this. Lets not
> drag this further if possible.
> 
> -James Seng
> 
> ----- Original Message -----
> From: "Martin Duerst" <duerst@w3.org>

> > So this is a solution in search of a real problem,
> > not worth bothering the whole world with additional
> > complexity.

I heartily concur with Martin's assessment.

--Ken Whistler




From owner-idn@ops.ietf.org  Fri Oct 19 00:16:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25945
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 00:16:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uQtC-000OEV-00
	for idn-data@psg.com; Thu, 18 Oct 2001 21:04:06 -0700
Received: from femail22.sdc1.sfba.home.com ([24.0.95.147])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uQtC-000OEP-00
	for idn@ops.ietf.org; Thu, 18 Oct 2001 21:04:06 -0700
Received: from c1340594a ([65.11.104.12]) by femail22.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20011019040404.HANT661.femail22.sdc1.sfba.home.com@c1340594a>;
          Thu, 18 Oct 2001 21:04:04 -0700
Message-ID: <006801c15853$3426c350$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "Kenneth Whistler" <kenw@sybase.com>, <jseng@pobox.org.sg>
Cc: <idn@ops.ietf.org>
References: <200110190328.UAA15512@birdie.sybase.com>
Subject: Re: [idn] call for comments for REORDERING
Date: Thu, 18 Oct 2001 21:04:45 -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 6.00.2600.0000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Ken is right; collation is *quite* complex. Anyone wanting to see some of
what is involved can look at the ICU implementation (which is UCA and ISO
14651 compliant, and open-source):

User Guide:
http://www-124.ibm.com/icu/userguide/Collate_Intro.html

Internal Design:
http://oss.software.ibm.com/cvs/icu/~checkout~/icuhtml/design/collation/ICU_
collation_design.htm
(source files are linked from there)

ICU home:
http://oss.software.ibm.com/icu/

While the perfomance is good, the code is many, many orders of magnitude
more complicated than the current nameprep. It is not appropriate for IDN.

Mark

—————

Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
[http://www.macchiato.com]

----- Original Message -----
From: "Kenneth Whistler" <kenw@sybase.com>
To: <jseng@pobox.org.sg>
Cc: <idn@ops.ietf.org>
Sent: Thursday, October 18, 2001 8:28 PM
Subject: Re: [idn] call for comments for REORDERING


> James Seng said:
>
> > Third, I would really prefer to reference a work from established expert
> > group if possible. For example, ISO/IEC JTC1/SC22/WG20 publishes ISO
> > 14651 on weighted sorting. I am not sure how ISO 14651 would perform for
> > the IDN purpose but I thought it might be worthwhile to examine.
>
> As one of the principal authors of ISO 14651, who has also implemented
> the synchronized Unicode Technical Standard #10, the Unicode Collation
> Algorithm, I can attest that this is a very tricky and complicated
> area, and the algorithms to do all this correctly are not the kind
> you can write on the back of a cocktail napkin. It is very complex
> to get all the details right and to get good-performing algorithms
> (in speed and in resource usage). It is also very difficult for
> independent implementations to get themselves all exactly lined
> up, and even more difficult for independent implementations to *prove*
> that they are getting the same results for all data (as opposed to
> a particular result for one set of data -- which is pretty easy).
>
> IDN doesn't need to add this kind of headache to the already
> complex enough issues of nameprep.
>
> >
> > Whatever the case, we should make a decision quickly on this. Lets not
> > drag this further if possible.
> >
> > -James Seng
> >
> > ----- Original Message -----
> > From: "Martin Duerst" <duerst@w3.org>
>
> > > So this is a solution in search of a real problem,
> > > not worth bothering the whole world with additional
> > > complexity.
>
> I heartily concur with Martin's assessment.
>
> --Ken Whistler
>
>
>




From owner-idn@ops.ietf.org  Fri Oct 19 00:25:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26031
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 00:25:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uR3Y-000OZW-00
	for idn-data@psg.com; Thu, 18 Oct 2001 21:14:48 -0700
Received: from smtp21.singnet.com.sg ([165.21.101.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uR3X-000OZJ-00
	for idn@ops.ietf.org; Thu, 18 Oct 2001 21:14:47 -0700
Received: from jamessonyvaio (58charlie253.singnet.com.sg [165.21.214.167])
	by smtp21.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9J4FSA03308;
	Fri, 19 Oct 2001 12:15:28 +0800
Message-ID: <045c01c15854$94e4bc00$0501000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <003d01c1584b$f90b66b0$ec1bd9d2@temp>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 12:14:37 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Your answer does not answer how we going to update re-ordering in future
with new codepoints. Do you expect to continue to work with this and to
have update RFC for it? And we going to update RFC again and again? The
typical solution IETF use for this is IANA action and that involves a
well-defined policy which IANA could reused for future addition. But if
we do so, we also need to consider if we are imposing codepoints issues
which is best dealt with other organisation.

As I repeated, I really like to point to another organisation for these
tables if possible. If ISO 14651 is not suitable (as Ken & Mark said),
then we look at some others. If there is none, then maybe we should
consider NOT to do it at all.

-James Seng

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>; <idn@ops.ietf.org>;
"Martin Duerst" <duerst@w3.org>
Sent: Friday, October 19, 2001 11:13 AM
Subject: Re: [idn] call for comments for REORDERING


HI, James

I will answer one by one for your  questions.

----- Original Message -----
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>; "Martin Duerst"
<duerst@w3.org>
Sent: Friday, October 19, 2001 10:09 AM
Subject: Re: [idn] call for comments for REORDERING


>
> And with the existing draft, it does not explain how it going to deal
> with new codepoints in ISO10646 in the future, nor does it explain the
> process to implementing them. The critia here is stablity - if new
code
> is added and tables for re-ordering expand, then the algorithm should
> not make existing names invalided.

REORDERING's mapping occurs within each script block, NOT across script
blocks.
Therefore, new additions of script block won't invalidate or collide
with existing names. Even additions of new rarely used characters in
existing script block won't affect the performance of REORDERING.
In this respect, REORDERING maintains stability over time.

Current IDNA/nameprep does not prohibit, but discourage including
unassigned code points in legal IDN labels, because new
normalization/case mappings
would be defined on them in the future. some ACE labels including
unsigned code block (tagalog?) might be proven invalid in the future.
Nameprep/NFKC Versioning tag schems using new ACE prefix will be needed
in the future, i guess.

Therefore, REORDERING  follows the same IDNA/nameprep recommendations on
the issues
of new SCTIPT blocks/unsigned code points.

This statements will be included in the final version of REORDERING I-D.

Thanks.

Soobok Lee








From owner-idn@ops.ietf.org  Fri Oct 19 00:25:49 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26043
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 00:25:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uR05-000OSC-00
	for idn-data@psg.com; Thu, 18 Oct 2001 21:11:13 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uR04-000OS5-00
	for idn@ops.ietf.org; Thu, 18 Oct 2001 21:11:12 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id NAA09592;
	Fri, 19 Oct 2001 13:10:54 +0900
Message-ID: <007601c15854$30c1f800$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 13:11:55 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA26043

Another answer for your concern.

----- Original Message ----- 
From: "James Seng/Personal" <jseng@pobox.org.sg>
> 
> The bigger concern I have with re-ordering remains in the fact that
> tables mappings proves efficient with existing IDN names in some
> registries *BUT* it  does not indicate what performance it would be like
> in the future. We do not know what happened when the names space get
> saturated and would other names which would have been useable without
> lsb become un-usuable due to lsb.
> 
 
1) saturations in TLD namespaces would require longer names for which
    REORDERING is designed to give greater benefits/compression ratio.

2) future variations on character usage frequency in each script

    2.0) the character frequency table are constructed from
         Verisign GRS' ML.com testbeds.
         Even for chinese han script, their
          registrations came from China/TAIWAN/JAPAN/KOREA and other
           non-asian squatters.
         Each country of the 4 have their own different han character
           usage patterns. The reordering table for han , therefore,
          cannot  for the worst case, the mutual difference in improvement ratios
          did not exceed  +- 2% around 20%.
           
    2.1) this issue is already answered by latest REORDERING I-D 2.0
         see the enclosed excerpts from it. The influence of this
         frequency variations is marginal.

3)

My REORDERING I-D contains experiments with various lengths of han
frequency tables : 1024,2048,3072,4096. In order to look into 
the influence of INs and OUTs of han characters from the most frequent 
2048 han characters.

For the two cases of table size 2048 and 4096, there was merely +- 1% of
differences in achieved improvements. I also reversed the order of the table itself,but it produced nearly the same result. 
The partial change in the order of the reordering table does not make big differences. some will lose and some will win. the net effect is near to zero.

I believe most of SJIS and KSC5601 han characters are  included in the
most frequent 4096 han character tables, because their governments bodies
selected   a few thousands of most frequent subset of entire han characters.

i believe that frequency fluctuation of han characters over time  is 
WITHIN the frequent set. INs and OUTs from 4096 ones are rare and does not invalidate the validity of most frequent 1024 and 2048 ones.
Moreover, TC/SC/KC characters are put side-by-side to avoid countriy-specific biases in han reordering table.

non-CJK scripts often haver small set of basic alphabets, and their
character usage patterns are more stable than those for han/hangeul.

REORDERING does not recommends reordering on shares latin scripts,
because latin characters are already encoded as it is (in literal mode,
the most efficient form ). latin script for europeans (0.6 billions) are the most favored one in ACE-Z. There shoulbe be some conpensations for
non europeans. Han script: 2 billions, Arabic: 0.7 billion, Hindi: 0.5 billion

This new frequency-based reordering is always more efficient than 
original lexicographical ordering in UCS 
even with some fluctuation in future script usage patterns.

We are not pursuing elusive "perfection and optimal" solution.
REORDERING tables cannot be modified if it is once freezed as standards.
Therefore,REORDERING is a sub-optimal solution in its nature but will be remain
as a valid and effective solution for a long time .


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

Unified Han and Hangeul

    11172 Hangul syllables and 20912 CJK Unified Han ideographs occupy 
    roughly two thirds of current assigned unicode code points.
    Their lexicographical ordering makes various ACE compression 
    algorithm work poorly for them, because they are spread evenly 
    through out those wide code blocks.

    According to one usage frequency statistics on hangeul syllables
    in general hangeul texts, the most frequent 256 Hangul syllables 
    have the cumulative frequency sum of 88.2% and for the case of top 
    512 ones, it reaches 99.9%. That means the maximum variation of 
    code point values(11172) can be shrinked into 512 in reordered
    hangeul block with a probability of 99.9%.

    Likewise, the most frequent 256 Han letters have the 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.
    That means the maximum variation of code point values (20912) can 
    be shrinked into 2048 with a probability of 95.4%.

    The han/hangul frequency mapping tables are constructed from 
    nameprepped ML.com domains from VGRS MultiLingual testbeds.
    The frequenet characters in the tables are organized by their
    increasing frequency order to minimize the AMC-ACE-Z bootstring 
    delta values which can be lowered when bigger code distances are 
    from the lower positions of the sorted labels in AMC-ACE-Z step 2.

    In general,character frequency distributions in any script block 
    may undergo some shifts within the frequent set by the passage of 
    time, but the in and out of some characters from the frequent set
    are very rare. So, their impacts may be as marginal and negligable 
    as the following comparison of experiment results shows.

    Reorering tables based on most frequent 1024,2048,3072 and 4096 han
    and hangul letters in increasing frequency order, produced marginal 
    differences in improvements:

      N is the length of sample labels and other
      decimal values (in percentage) are the improvement ratios for 
      all the combinations of all N and 4 reordering tables.



      |  N|  HAN-4096|  HAN-3072|  HAN-2048|  HAN-1024|
      |  1|     7.07 |     5.49 |     3.58 |      1.64|
      |  2|    13.61 |    13.22 |    11.57 |      8.06|
      |  3|    16.26 |    16.05 |    15.10 |     12.26|
      |  4|    20.80 |    20.71 |    20.19 |     18.11|
      |  5|    22.17 |    22.03 |    21.47 |     19.41|
      |  6|    24.85 |    24.77 |    24.41 |     22.48|
      |  7|    25.52 |    25.40 |    24.99 |     23.17|
      |  8|    26.47 |    26.36 |    26.00 |     24.15|
      |  9|    26.54 |    26.46 |    26.04 |     24.26|
      | 10|    27.47 |    27.40 |    27.01 |     25.09|
      | 11|    27.30 |    27.26 |    26.85 |     25.12|
      | 12|    27.74 |    27.64 |    27.41 |     25.60|
      | 13|    27.27 |    27.17 |    26.78 |     25.28|
      | 14|    27.48 |    27.35 |    27.08 |     24.94|
      | 15|    28.60 |    28.43 |    28.56 |     26.54|
      | 16|    27.70 |    27.84 |    27.70 |     25.51|
      | 17|    25.68 |    25.68 |    25.43 |     23.70| 
      |ALL|    20.30 |    20.14 |    19.43 |     17.09|


    Experiments with two reorering tables in increasing and descreasing 
    orders for most frequent 2048,4096 han letters,also produced 
    marginal differences in improvements:

     (4096D means: the ordering table is in decreasing frequency order) 


      |  N|  HAN-4096| HAN-4096D|  HAN-2048| HAN-2048D|
      |  1|     7.07 |     7.01 |     3.58 |     3.51 |
      |  2|    13.61 |    13.44 |    11.57 |    11.27 |
      |  3|    16.26 |    16.35 |    15.10 |    14.93 |
      |  4|    20.80 |    20.56 |    20.19 |    19.90 |
      |  5|    22.17 |    21.80 |    21.47 |    21.12 |
      |  6|    24.85 |    24.21 |    24.41 |    23.82 |
      |  7|    25.52 |    24.59 |    24.99 |    24.14 |
      |  8|    26.47 |    25.68 |    26.00 |    25.36 |
      |  9|    26.54 |    25.55 |    26.04 |    25.18 |
      | 10|    27.47 |    26.79 |    27.01 |    26.42 |
      | 11|    27.30 |    26.82 |    26.85 |    26.36 |
      | 12|    27.74 |    27.46 |    27.41 |    27.13 |
      | 13|    27.27 |    26.97 |    26.78 |    26.59 |
      | 14|    27.48 |    27.31 |    27.08 |    26.99 |
      | 15|    28.60 |    28.60 |    28.56 |    28.56 |
      | 16|    27.70 |    27.55 |    27.70 |    27.20 |
      | 17|    25.68 |    25.93 |    25.43 |    25.68 | 
      |ALL|    20.30 |    20.00 |    19.43 |    19.07 |

    These experiments show that the influences of some fluctations in 
    character frequency distributions in the frequent set of a script 
    would not be so great that could invalidate or outdate this 
    reordering approach in the forseeable future.

    But,to be as neutral and fair as possible in dealing with the cases 
    with different usage patterns in China,Japan,Korea and Taiwan, here 
    are provided some provisions for grouping country-specific variants
    of certain han letters. Especially, a group of simplified chainese 
    letter (SC) and traditional chinese letter (TC) and Kanji-specific
    letter (KC) are ranked by the sum of their frequecies and placed 
    side-by-side in the reordering table for Unified Han block. 
    For example, the reordering table looks like:
     (TC1) (TC2 SC2) (TC3 KC3) (TC4) (TC5 SC5 KC5) (TC6) .....
    This grouping will serve to prevent the frequency orders from being
    skewed toward one of those country-specific usage patterns.
    The experiments results 27 and 28 in [A3] shows that this reordering
    scheme improve 21.95% and 18.50% for SC and TC labels,respectively.

    According to experiments with huge han/hangeul domain samples,
    as for 15 or more letters of  han/hangeul domains, AMC-ACE-Z with 
    reordering produced the shortest ACE labels which length approximate
    to 2.0*n~2.2*n (n= number of han/hangul code points in a label), 
    33.3% more efficient than bare AMC-ACE-Z without the reordering.
    This efficiency is close to that of UCS-2 ( 2.0 * n) and much better
    than that of UTF8 ( 3.0*n ).

    The appendix [A3] also contains some tuning experiments on ACE-Z's
    skew and damp parameters. With skew==48 and damp==75, +1.3% in 
    compression ratio was achieved for han domains with some marginal 
    loss of efficiency in non-CJK scripts.

----------------
19. unihan-1024

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
|  1|    4427|      4427|     14957(3.38)|     14711(3.32)| 1.64|
|  2|   57418|    114836|    384468(3.35)|    353466(3.08)| 8.06|
|  3|   41335|    124005|    401283(3.24)|    352095(2.84)|12.26|
|  4|   89296|    357184|   1139404(3.19)|    933070(2.61)|18.11|
|  5|   21091|    105455|    332420(3.15)|    267893(2.54)|19.41|
|  6|   15128|     90768|    284134(3.13)|    220263(2.43)|22.48|
|  7|    5181|     36267|    112576(3.10)|     86487(2.38)|23.17|
|  8|    3082|     24656|     76272(3.09)|     57854(2.35)|24.15|
|  9|    1417|     12753|     39319(3.08)|     29779(2.34)|24.26|
| 10|    1203|     12030|     37136(3.09)|     27817(2.31)|25.09|
| 11|     474|      5214|     16072(3.08)|     12035(2.31)|25.12|
| 12|     398|      4776|     14714(3.08)|     10947(2.29)|25.60|
| 13|     164|      2132|      6532(3.06)|      4881(2.29)|25.28|
| 14|     122|      1708|      5232(3.06)|      3927(2.30)|24.94|
| 15|      50|       750|      2283(3.04)|      1677(2.24)|26.54|
| 16|      29|       464|      1419(3.06)|      1057(2.28)|25.51|
| 17|       8|       136|       405(2.98)|       309(2.27)|23.70|

|All|  240823|    897561|   2868626(3.20)|   2378268(2.65)|17.09|



20. unihan-2048

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
|  1|    4427|      4427|     14957(3.38)|     14422(3.26)| 3.58|
|  2|   57418|    114836|    384468(3.35)|    339996(2.96)|11.57|
|  3|   41335|    124005|    401283(3.24)|    340675(2.75)|15.10|
|  4|   89296|    357184|   1139404(3.19)|    909323(2.55)|20.19|
|  5|   21091|    105455|    332420(3.15)|    261039(2.48)|21.47|
|  6|   15128|     90768|    284134(3.13)|    214781(2.37)|24.41|
|  7|    5181|     36267|    112576(3.10)|     84440(2.33)|24.99|
|  8|    3082|     24656|     76272(3.09)|     56439(2.29)|26.00|
|  9|    1417|     12753|     39319(3.08)|     29082(2.28)|26.04|
| 10|    1203|     12030|     37136(3.09)|     27106(2.25)|27.01|
| 11|     474|      5214|     16072(3.08)|     11756(2.25)|26.85|
| 12|     398|      4776|     14714(3.08)|     10681(2.24)|27.41|
| 13|     164|      2132|      6532(3.06)|      4783(2.24)|26.78|
| 14|     122|      1708|      5232(3.06)|      3815(2.23)|27.08|
| 15|      50|       750|      2283(3.04)|      1631(2.17)|28.56|
| 16|      29|       464|      1419(3.06)|      1026(2.21)|27.70|
| 17|       8|       136|       405(2.98)|       302(2.22)|25.43|

|All|  240823|    897561|   2868626(3.20)|   2311297(2.58)|19.43|



21. unihan-2048-D ( the reordering in decreasing frequency order)

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
|  1|    4427|      4427|     14957(3.38)|     14432(3.26)| 3.51|
|  2|   57418|    114836|    384468(3.35)|    341134(2.97)|11.27|
|  3|   41335|    124005|    401283(3.24)|    341362(2.75)|14.93|
|  4|   89296|    357184|   1139404(3.19)|    912694(2.56)|19.90|
|  5|   21091|    105455|    332420(3.15)|    262224(2.49)|21.12|
|  6|   15128|     90768|    284134(3.13)|    216465(2.38)|23.82|
|  7|    5181|     36267|    112576(3.10)|     85401(2.35)|24.14|
|  8|    3082|     24656|     76272(3.09)|     56931(2.31)|25.36|
|  9|    1417|     12753|     39319(3.08)|     29420(2.31)|25.18|
| 10|    1203|     12030|     37136(3.09)|     27324(2.27)|26.42|
| 11|     474|      5214|     16072(3.08)|     11835(2.27)|26.36|
| 12|     398|      4776|     14714(3.08)|     10722(2.24)|27.13|
| 13|     164|      2132|      6532(3.06)|      4795(2.25)|26.59|
| 14|     122|      1708|      5232(3.06)|      3820(2.24)|26.99|
| 15|      50|       750|      2283(3.04)|      1631(2.17)|28.56|
| 16|      29|       464|      1419(3.06)|      1033(2.23)|27.20|
| 17|       8|       136|       405(2.98)|       301(2.21)|25.68|

|All|  240823|    897561|   2868626(3.20)|   2321524(2.59)|19.07|



22. unihan-3072

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
|  1|    4427|      4427|     14957(3.38)|     14136(3.19)| 5.49|
|  2|   57418|    114836|    384468(3.35)|    333660(2.91)|13.22|
|  3|   41335|    124005|    401283(3.24)|    336865(2.72)|16.05|
|  4|   89296|    357184|   1139404(3.19)|    903458(2.53)|20.71|
|  5|   21091|    105455|    332420(3.15)|    259189(2.46)|22.03|
|  6|   15128|     90768|    284134(3.13)|    213746(2.35)|24.77|
|  7|    5181|     36267|    112576(3.10)|     83977(2.32)|25.40|
|  8|    3082|     24656|     76272(3.09)|     56168(2.28)|26.36|
|  9|    1417|     12753|     39319(3.08)|     28917(2.27)|26.46|
| 10|    1203|     12030|     37136(3.09)|     26962(2.24)|27.40|
| 11|     474|      5214|     16072(3.08)|     11690(2.24)|27.26|
| 12|     398|      4776|     14714(3.08)|     10647(2.23)|27.64|
| 13|     164|      2132|      6532(3.06)|      4757(2.23)|27.17|
| 14|     122|      1708|      5232(3.06)|      3801(2.23)|27.35|
| 15|      50|       750|      2283(3.04)|      1634(2.18)|28.43|
| 16|      29|       464|      1419(3.06)|      1024(2.21)|27.84|
| 17|       8|       136|       405(2.98)|       301(2.21)|25.68|

|All|  240823|    897561|   2868626(3.20)|   2290932(2.55)|20.14|



23. unihan-4096

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
|  1|    4427|      4427|     14957(3.38)|     13899(3.14)| 7.07|
|  2|   57418|    114836|    384468(3.35)|    332156(2.89)|13.61|
|  3|   41335|    124005|    401283(3.24)|    336045(2.71)|16.26|
|  4|   89296|    357184|   1139404(3.19)|    902406(2.53)|20.80|
|  5|   21091|    105455|    332420(3.15)|    258709(2.45)|22.17|
|  6|   15128|     90768|    284134(3.13)|    213522(2.35)|24.85|
|  7|    5181|     36267|    112576(3.10)|     83844(2.31)|25.52|
|  8|    3082|     24656|     76272(3.09)|     56083(2.27)|26.47|
|  9|    1417|     12753|     39319(3.08)|     28883(2.26)|26.54|
| 10|    1203|     12030|     37136(3.09)|     26935(2.24)|27.47|
| 11|     474|      5214|     16072(3.08)|     11684(2.24)|27.30|
| 12|     398|      4776|     14714(3.08)|     10632(2.23)|27.74|
| 13|     164|      2132|      6532(3.06)|      4751(2.23)|27.27|
| 14|     122|      1708|      5232(3.06)|      3794(2.22)|27.48|
| 15|      50|       750|      2283(3.04)|      1630(2.17)|28.60|
| 16|      29|       464|      1419(3.06)|      1026(2.21)|27.70|
| 17|       8|       136|       405(2.98)|       301(2.21)|25.68|

|All|  240823|    897561|   2868626(3.20)|   2286300(2.55)|20.30|



24. unihan-4096-D

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
|  1|    4427|      4427|     14957(3.38)|     13909(3.14)| 7.01|
|  2|   57418|    114836|    384468(3.35)|    332799(2.90)|13.44|
|  3|   41335|    124005|    401283(3.24)|    335682(2.71)|16.35|
|  4|   89296|    357184|   1139404(3.19)|    905086(2.53)|20.56|
|  5|   21091|    105455|    332420(3.15)|    259944(2.46)|21.80|
|  6|   15128|     90768|    284134(3.13)|    215353(2.37)|24.21|
|  7|    5181|     36267|    112576(3.10)|     84893(2.34)|24.59|
|  8|    3082|     24656|     76272(3.09)|     56682(2.30)|25.68|
|  9|    1417|     12753|     39319(3.08)|     29273(2.30)|25.55|
| 10|    1203|     12030|     37136(3.09)|     27189(2.26)|26.79|
| 11|     474|      5214|     16072(3.08)|     11762(2.26)|26.82|
| 12|     398|      4776|     14714(3.08)|     10674(2.23)|27.46|
| 13|     164|      2132|      6532(3.06)|      4770(2.24)|26.97|
| 14|     122|      1708|      5232(3.06)|      3803(2.23)|27.31|
| 15|      50|       750|      2283(3.04)|      1630(2.17)|28.60|
| 16|      29|       464|      1419(3.06)|      1028(2.22)|27.55|
| 17|       8|       136|       405(2.98)|       300(2.21)|25.93|

|All|  240823|    897561|   2868626(3.20)|   2294777(2.56)|20.00|



25. unihan-4096-DAMP075-SKEW48

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
|  1|    4427|      4427|     14957(3.38)|     13899(3.14)| 7.07|
|  2|   57418|    114836|    375901(3.27)|    324587(2.83)|13.65|
|  3|   41335|    124005|    394416(3.18)|    330550(2.67)|16.19|
|  4|   89296|    357184|   1126357(3.15)|    890277(2.49)|20.96|
|  5|   21091|    105455|    329783(3.13)|    255913(2.43)|22.40|
|  6|   15128|     90768|    282751(3.12)|    211339(2.33)|25.26|
|  7|    5181|     36267|    112181(3.09)|     83126(2.29)|25.90|
|  8|    3082|     24656|     76111(3.09)|     55712(2.26)|26.80|
|  9|    1417|     12753|     39285(3.08)|     28699(2.25)|26.95|
| 10|    1203|     12030|     37150(3.09)|     26767(2.23)|27.95|
| 11|     474|      5214|     16028(3.07)|     11603(2.23)|27.61|
| 12|     398|      4776|     14712(3.08)|     10567(2.21)|28.17|
| 13|     164|      2132|      6528(3.06)|      4735(2.22)|27.47|
| 14|     122|      1708|      5248(3.07)|      3762(2.20)|28.32|
| 15|      50|       750|      2281(3.04)|      1628(2.17)|28.63|
| 16|      29|       464|      1425(3.07)|      1017(2.19)|28.63|
| 17|       8|       136|       404(2.97)|       301(2.21)|25.50|

|All|  240823|    897561|   2835518(3.16)|   2254482(2.51)|20.49|



26. unihan-4096-DUDE

|  N|    FREQ|    N*FREQ|  SUM OF DUDE(X)| SUM OF LDUDE(Y)| COMP|
|  1|    4427|      4427|     17708(4.00)|     17708(4.00)| 0.00|
|  2|   57418|    114836|    443874(3.87)|    409657(3.57)| 7.71|
|  3|   41335|    124005|    474117(3.82)|    408039(3.29)|13.94|
|  4|   89296|    357184|   1361917(3.81)|   1074237(3.01)|21.12|
|  5|   21091|    105455|    401146(3.80)|    308378(2.92)|23.13|
|  6|   15128|     90768|    344208(3.79)|    250925(2.76)|27.10|
|  7|    5181|     36267|    137275(3.79)|     99475(2.74)|27.54|
|  8|    3082|     24656|     93013(3.77)|     65889(2.67)|29.16|
|  9|    1417|     12753|     48000(3.76)|     34230(2.68)|28.69|
| 10|    1203|     12030|     45427(3.78)|     31663(2.63)|30.30|
| 11|     474|      5214|     19564(3.75)|     13708(2.63)|29.93|
| 12|     398|      4776|     18013(3.77)|     12468(2.61)|30.78|
| 13|     164|      2132|      7969(3.74)|      5590(2.62)|29.85|
| 14|     122|      1708|      6377(3.73)|      4476(2.62)|29.81|
| 15|      50|       750|      2811(3.75)|      1926(2.57)|31.48|
| 16|      29|       464|      1749(3.77)|      1213(2.61)|30.65|
| 17|       8|       136|       508(3.74)|       355(2.61)|30.12|

|All|  240823|    897561|   3423676(3.81)|   2739937(3.05)|19.97|



27. unihan-SC-4096 ( SC only or SC+TC mixed )

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
|  1|     769|       769|      2717(3.53)|      2378(3.09)|12.48|
|  2|   16065|     32130|    108598(3.38)|     92597(2.88)|14.73|
|  3|   14315|     42945|    139693(3.25)|    116054(2.70)|16.92|
|  4|   48871|    195484|    623650(3.19)|    491073(2.51)|21.26|
|  5|   12135|     60675|    190928(3.15)|    147721(2.43)|22.63|
|  6|   10463|     62778|    196038(3.12)|    146516(2.33)|25.26|
|  7|    3594|     25158|     77931(3.10)|     57412(2.28)|26.33|
|  8|    2373|     18984|     58686(3.09)|     42907(2.26)|26.89|
|  9|    1078|      9702|     29875(3.08)|     21736(2.24)|27.24|
| 10|     934|      9340|     28786(3.08)|     20855(2.23)|27.55|
| 11|     392|      4312|     13279(3.08)|      9612(2.23)|27.62|
| 12|     314|      3768|     11579(3.07)|      8376(2.22)|27.66|
| 13|     144|      1872|      5724(3.06)|      4158(2.22)|27.36|
| 14|     104|      1456|      4455(3.06)|      3226(2.22)|27.59|
| 15|      41|       615|      1868(3.04)|      1348(2.19)|27.84|
| 16|      25|       400|      1219(3.05)|       887(2.22)|27.24|
| 17|       7|       119|       353(2.97)|       264(2.22)|25.21|

|All|  111624|    470507|   1495379(3.18)|   1167120(2.48)|21.95|



28. unihan-TC-4096 ( TC only )

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
|  1|    3658|      3658|     12240(3.35)|     11521(3.15)| 5.87|
|  2|   41353|     82706|    275870(3.34)|    239559(2.90)|13.16|
|  3|   27020|     81060|    261590(3.23)|    219991(2.71)|15.90|
|  4|   40425|    161700|    515754(3.19)|    411333(2.54)|20.25|
|  5|    8956|     44780|    141492(3.16)|    110988(2.48)|21.56|
|  6|    4665|     27990|     88096(3.15)|     67006(2.39)|23.94|
|  7|    1587|     11109|     34645(3.12)|     26432(2.38)|23.71|
|  8|     709|      5672|     17586(3.10)|     13176(2.32)|25.08|
|  9|     339|      3051|      9444(3.10)|      7147(2.34)|24.32|
| 10|     269|      2690|      8350(3.10)|      6080(2.26)|27.19|
| 11|      82|       902|      2793(3.10)|      2072(2.30)|25.81|
| 12|      84|      1008|      3135(3.11)|      2256(2.24)|28.04|
| 13|      20|       260|       808(3.11)|       593(2.28)|26.61|
| 14|      18|       252|       777(3.08)|       568(2.25)|26.90|
| 15|       9|       135|       415(3.07)|       282(2.09)|32.05|
| 16|       4|        64|       200(3.12)|       139(2.17)|30.50|
| 17|       1|        17|        52(3.06)|        37(2.18)|28.85|

|All|  129199|    427054|   1373247(3.22)|   1119180(2.62)|18.50|

    




From owner-idn@ops.ietf.org  Fri Oct 19 00:31:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26097
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 00:31:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uR6b-000Ofg-00
	for idn-data@psg.com; Thu, 18 Oct 2001 21:17:58 -0700
Received: from smtp24.singnet.com.sg ([165.21.101.204])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uR6a-000OfL-00
	for idn@ops.ietf.org; Thu, 18 Oct 2001 21:17:56 -0700
Received: from jamessonyvaio (58charlie253.singnet.com.sg [165.21.214.167])
	by smtp24.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9J4IVS12297;
	Fri, 19 Oct 2001 12:18:31 +0800
Message-ID: <046001c15855$02854f40$0501000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <007601c15854$30c1f800$ec1bd9d2@temp>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 12:17:46 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

You dont get my point.

Reordering achieve shorter by putting more oftenly used characters in
one block and others at the back. BUT this also means less oftenly used
characters would result in a *LONGER* label then usual. And who are we
to say these less oftenly used characters are less important or worst,
become invalid (too long to fit) because of this reordering?

-James Seng

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>; <idn@ops.ietf.org>;
"Martin Duerst" <duerst@w3.org>
Sent: Friday, October 19, 2001 12:11 PM
Subject: Re: [idn] call for comments for REORDERING


> Another answer for your concern.
>
> ----- Original Message -----
> From: "James Seng/Personal" <jseng@pobox.org.sg>
> >
> > The bigger concern I have with re-ordering remains in the fact that
> > tables mappings proves efficient with existing IDN names in some
> > registries *BUT* it  does not indicate what performance it would be
like
> > in the future. We do not know what happened when the names space get
> > saturated and would other names which would have been useable
without
> > lsb become un-usuable due to lsb.
> >
>
> 1) saturations in TLD namespaces would require longer names for which
>     REORDERING is designed to give greater benefits/compression ratio.
>
> 2) future variations on character usage frequency in each script
>
>     2.0) the character frequency table are constructed from
>          Verisign GRS' ML.com testbeds.
>          Even for chinese han script, their
>           registrations came from China/TAIWAN/JAPAN/KOREA and other
>            non-asian squatters.
>          Each country of the 4 have their own different han character
>            usage patterns. The reordering table for han , therefore,
>           cannot  for the worst case, the mutual difference in
improvement ratios
>           did not exceed  +- 2% around 20%.
>
>     2.1) this issue is already answered by latest REORDERING I-D 2.0
>          see the enclosed excerpts from it. The influence of this
>          frequency variations is marginal.
>
> 3)
>
> My REORDERING I-D contains experiments with various lengths of han
> frequency tables : 1024,2048,3072,4096. In order to look into
> the influence of INs and OUTs of han characters from the most frequent
> 2048 han characters.
>
> For the two cases of table size 2048 and 4096, there was merely +- 1%
of
> differences in achieved improvements. I also reversed the order of the
table itself,but it produced nearly the same result.
> The partial change in the order of the reordering table does not make
big differences. some will lose and some will win. the net effect is
near to zero.
>
> I believe most of SJIS and KSC5601 han characters are  included in the
> most frequent 4096 han character tables, because their governments
bodies
> selected   a few thousands of most frequent subset of entire han
characters.
>
> i believe that frequency fluctuation of han characters over time  is
> WITHIN the frequent set. INs and OUTs from 4096 ones are rare and does
not invalidate the validity of most frequent 1024 and 2048 ones.
> Moreover, TC/SC/KC characters are put side-by-side to avoid
countriy-specific biases in han reordering table.
>
> non-CJK scripts often haver small set of basic alphabets, and their
> character usage patterns are more stable than those for han/hangeul.
>
> REORDERING does not recommends reordering on shares latin scripts,
> because latin characters are already encoded as it is (in literal
mode,
> the most efficient form ). latin script for europeans (0.6 billions)
are the most favored one in ACE-Z. There shoulbe be some conpensations
for
> non europeans. Han script: 2 billions, Arabic: 0.7 billion, Hindi: 0.5
billion
>
> This new frequency-based reordering is always more efficient than
> original lexicographical ordering in UCS
> even with some fluctuation in future script usage patterns.
>
> We are not pursuing elusive "perfection and optimal" solution.
> REORDERING tables cannot be modified if it is once freezed as
standards.
> Therefore,REORDERING is a sub-optimal solution in its nature but will
be remain
> as a valid and effective solution for a long time .
>
>
> Soobok
>
> ---------------------------
>
> Unified Han and Hangeul
>
>     11172 Hangul syllables and 20912 CJK Unified Han ideographs occupy
>     roughly two thirds of current assigned unicode code points.
>     Their lexicographical ordering makes various ACE compression
>     algorithm work poorly for them, because they are spread evenly
>     through out those wide code blocks.
>
>     According to one usage frequency statistics on hangeul syllables
>     in general hangeul texts, the most frequent 256 Hangul syllables
>     have the cumulative frequency sum of 88.2% and for the case of top
>     512 ones, it reaches 99.9%. That means the maximum variation of
>     code point values(11172) can be shrinked into 512 in reordered
>     hangeul block with a probability of 99.9%.
>
>     Likewise, the most frequent 256 Han letters have the 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.
>     That means the maximum variation of code point values (20912) can
>     be shrinked into 2048 with a probability of 95.4%.
>
>     The han/hangul frequency mapping tables are constructed from
>     nameprepped ML.com domains from VGRS MultiLingual testbeds.
>     The frequenet characters in the tables are organized by their
>     increasing frequency order to minimize the AMC-ACE-Z bootstring
>     delta values which can be lowered when bigger code distances are
>     from the lower positions of the sorted labels in AMC-ACE-Z step 2.
>
>     In general,character frequency distributions in any script block
>     may undergo some shifts within the frequent set by the passage of
>     time, but the in and out of some characters from the frequent set
>     are very rare. So, their impacts may be as marginal and negligable
>     as the following comparison of experiment results shows.
>
>     Reorering tables based on most frequent 1024,2048,3072 and 4096
han
>     and hangul letters in increasing frequency order, produced
marginal
>     differences in improvements:
>
>       N is the length of sample labels and other
>       decimal values (in percentage) are the improvement ratios for
>       all the combinations of all N and 4 reordering tables.
>
>
>
>       |  N|  HAN-4096|  HAN-3072|  HAN-2048|  HAN-1024|
>       |  1|     7.07 |     5.49 |     3.58 |      1.64|
>       |  2|    13.61 |    13.22 |    11.57 |      8.06|
>       |  3|    16.26 |    16.05 |    15.10 |     12.26|
>       |  4|    20.80 |    20.71 |    20.19 |     18.11|
>       |  5|    22.17 |    22.03 |    21.47 |     19.41|
>       |  6|    24.85 |    24.77 |    24.41 |     22.48|
>       |  7|    25.52 |    25.40 |    24.99 |     23.17|
>       |  8|    26.47 |    26.36 |    26.00 |     24.15|
>       |  9|    26.54 |    26.46 |    26.04 |     24.26|
>       | 10|    27.47 |    27.40 |    27.01 |     25.09|
>       | 11|    27.30 |    27.26 |    26.85 |     25.12|
>       | 12|    27.74 |    27.64 |    27.41 |     25.60|
>       | 13|    27.27 |    27.17 |    26.78 |     25.28|
>       | 14|    27.48 |    27.35 |    27.08 |     24.94|
>       | 15|    28.60 |    28.43 |    28.56 |     26.54|
>       | 16|    27.70 |    27.84 |    27.70 |     25.51|
>       | 17|    25.68 |    25.68 |    25.43 |     23.70|
>       |ALL|    20.30 |    20.14 |    19.43 |     17.09|
>
>
>     Experiments with two reorering tables in increasing and
descreasing
>     orders for most frequent 2048,4096 han letters,also produced
>     marginal differences in improvements:
>
>      (4096D means: the ordering table is in decreasing frequency
order)
>
>
>       |  N|  HAN-4096| HAN-4096D|  HAN-2048| HAN-2048D|
>       |  1|     7.07 |     7.01 |     3.58 |     3.51 |
>       |  2|    13.61 |    13.44 |    11.57 |    11.27 |
>       |  3|    16.26 |    16.35 |    15.10 |    14.93 |
>       |  4|    20.80 |    20.56 |    20.19 |    19.90 |
>       |  5|    22.17 |    21.80 |    21.47 |    21.12 |
>       |  6|    24.85 |    24.21 |    24.41 |    23.82 |
>       |  7|    25.52 |    24.59 |    24.99 |    24.14 |
>       |  8|    26.47 |    25.68 |    26.00 |    25.36 |
>       |  9|    26.54 |    25.55 |    26.04 |    25.18 |
>       | 10|    27.47 |    26.79 |    27.01 |    26.42 |
>       | 11|    27.30 |    26.82 |    26.85 |    26.36 |
>       | 12|    27.74 |    27.46 |    27.41 |    27.13 |
>       | 13|    27.27 |    26.97 |    26.78 |    26.59 |
>       | 14|    27.48 |    27.31 |    27.08 |    26.99 |
>       | 15|    28.60 |    28.60 |    28.56 |    28.56 |
>       | 16|    27.70 |    27.55 |    27.70 |    27.20 |
>       | 17|    25.68 |    25.93 |    25.43 |    25.68 |
>       |ALL|    20.30 |    20.00 |    19.43 |    19.07 |
>
>     These experiments show that the influences of some fluctations in
>     character frequency distributions in the frequent set of a script
>     would not be so great that could invalidate or outdate this
>     reordering approach in the forseeable future.
>
>     But,to be as neutral and fair as possible in dealing with the
cases
>     with different usage patterns in China,Japan,Korea and Taiwan,
here
>     are provided some provisions for grouping country-specific
variants
>     of certain han letters. Especially, a group of simplified chainese
>     letter (SC) and traditional chinese letter (TC) and Kanji-specific
>     letter (KC) are ranked by the sum of their frequecies and placed
>     side-by-side in the reordering table for Unified Han block.
>     For example, the reordering table looks like:
>      (TC1) (TC2 SC2) (TC3 KC3) (TC4) (TC5 SC5 KC5) (TC6) .....
>     This grouping will serve to prevent the frequency orders from
being
>     skewed toward one of those country-specific usage patterns.
>     The experiments results 27 and 28 in [A3] shows that this
reordering
>     scheme improve 21.95% and 18.50% for SC and TC
labels,respectively.
>
>     According to experiments with huge han/hangeul domain samples,
>     as for 15 or more letters of  han/hangeul domains, AMC-ACE-Z with
>     reordering produced the shortest ACE labels which length
approximate
>     to 2.0*n~2.2*n (n= number of han/hangul code points in a label),
>     33.3% more efficient than bare AMC-ACE-Z without the reordering.
>     This efficiency is close to that of UCS-2 ( 2.0 * n) and much
better
>     than that of UTF8 ( 3.0*n ).
>
>     The appendix [A3] also contains some tuning experiments on ACE-Z's
>     skew and damp parameters. With skew==48 and damp==75, +1.3% in
>     compression ratio was achieved for han domains with some marginal
>     loss of efficiency in non-CJK scripts.
>
> ----------------
> 19. unihan-1024
>
> |  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
> |  1|    4427|      4427|     14957(3.38)|     14711(3.32)| 1.64|
> |  2|   57418|    114836|    384468(3.35)|    353466(3.08)| 8.06|
> |  3|   41335|    124005|    401283(3.24)|    352095(2.84)|12.26|
> |  4|   89296|    357184|   1139404(3.19)|    933070(2.61)|18.11|
> |  5|   21091|    105455|    332420(3.15)|    267893(2.54)|19.41|
> |  6|   15128|     90768|    284134(3.13)|    220263(2.43)|22.48|
> |  7|    5181|     36267|    112576(3.10)|     86487(2.38)|23.17|
> |  8|    3082|     24656|     76272(3.09)|     57854(2.35)|24.15|
> |  9|    1417|     12753|     39319(3.08)|     29779(2.34)|24.26|
> | 10|    1203|     12030|     37136(3.09)|     27817(2.31)|25.09|
> | 11|     474|      5214|     16072(3.08)|     12035(2.31)|25.12|
> | 12|     398|      4776|     14714(3.08)|     10947(2.29)|25.60|
> | 13|     164|      2132|      6532(3.06)|      4881(2.29)|25.28|
> | 14|     122|      1708|      5232(3.06)|      3927(2.30)|24.94|
> | 15|      50|       750|      2283(3.04)|      1677(2.24)|26.54|
> | 16|      29|       464|      1419(3.06)|      1057(2.28)|25.51|
> | 17|       8|       136|       405(2.98)|       309(2.27)|23.70|
>
> |All|  240823|    897561|   2868626(3.20)|   2378268(2.65)|17.09|
>
>
>
> 20. unihan-2048
>
> |  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
> |  1|    4427|      4427|     14957(3.38)|     14422(3.26)| 3.58|
> |  2|   57418|    114836|    384468(3.35)|    339996(2.96)|11.57|
> |  3|   41335|    124005|    401283(3.24)|    340675(2.75)|15.10|
> |  4|   89296|    357184|   1139404(3.19)|    909323(2.55)|20.19|
> |  5|   21091|    105455|    332420(3.15)|    261039(2.48)|21.47|
> |  6|   15128|     90768|    284134(3.13)|    214781(2.37)|24.41|
> |  7|    5181|     36267|    112576(3.10)|     84440(2.33)|24.99|
> |  8|    3082|     24656|     76272(3.09)|     56439(2.29)|26.00|
> |  9|    1417|     12753|     39319(3.08)|     29082(2.28)|26.04|
> | 10|    1203|     12030|     37136(3.09)|     27106(2.25)|27.01|
> | 11|     474|      5214|     16072(3.08)|     11756(2.25)|26.85|
> | 12|     398|      4776|     14714(3.08)|     10681(2.24)|27.41|
> | 13|     164|      2132|      6532(3.06)|      4783(2.24)|26.78|
> | 14|     122|      1708|      5232(3.06)|      3815(2.23)|27.08|
> | 15|      50|       750|      2283(3.04)|      1631(2.17)|28.56|
> | 16|      29|       464|      1419(3.06)|      1026(2.21)|27.70|
> | 17|       8|       136|       405(2.98)|       302(2.22)|25.43|
>
> |All|  240823|    897561|   2868626(3.20)|   2311297(2.58)|19.43|
>
>
>
> 21. unihan-2048-D ( the reordering in decreasing frequency order)
>
> |  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
> |  1|    4427|      4427|     14957(3.38)|     14432(3.26)| 3.51|
> |  2|   57418|    114836|    384468(3.35)|    341134(2.97)|11.27|
> |  3|   41335|    124005|    401283(3.24)|    341362(2.75)|14.93|
> |  4|   89296|    357184|   1139404(3.19)|    912694(2.56)|19.90|
> |  5|   21091|    105455|    332420(3.15)|    262224(2.49)|21.12|
> |  6|   15128|     90768|    284134(3.13)|    216465(2.38)|23.82|
> |  7|    5181|     36267|    112576(3.10)|     85401(2.35)|24.14|
> |  8|    3082|     24656|     76272(3.09)|     56931(2.31)|25.36|
> |  9|    1417|     12753|     39319(3.08)|     29420(2.31)|25.18|
> | 10|    1203|     12030|     37136(3.09)|     27324(2.27)|26.42|
> | 11|     474|      5214|     16072(3.08)|     11835(2.27)|26.36|
> | 12|     398|      4776|     14714(3.08)|     10722(2.24)|27.13|
> | 13|     164|      2132|      6532(3.06)|      4795(2.25)|26.59|
> | 14|     122|      1708|      5232(3.06)|      3820(2.24)|26.99|
> | 15|      50|       750|      2283(3.04)|      1631(2.17)|28.56|
> | 16|      29|       464|      1419(3.06)|      1033(2.23)|27.20|
> | 17|       8|       136|       405(2.98)|       301(2.21)|25.68|
>
> |All|  240823|    897561|   2868626(3.20)|   2321524(2.59)|19.07|
>
>
>
> 22. unihan-3072
>
> |  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
> |  1|    4427|      4427|     14957(3.38)|     14136(3.19)| 5.49|
> |  2|   57418|    114836|    384468(3.35)|    333660(2.91)|13.22|
> |  3|   41335|    124005|    401283(3.24)|    336865(2.72)|16.05|
> |  4|   89296|    357184|   1139404(3.19)|    903458(2.53)|20.71|
> |  5|   21091|    105455|    332420(3.15)|    259189(2.46)|22.03|
> |  6|   15128|     90768|    284134(3.13)|    213746(2.35)|24.77|
> |  7|    5181|     36267|    112576(3.10)|     83977(2.32)|25.40|
> |  8|    3082|     24656|     76272(3.09)|     56168(2.28)|26.36|
> |  9|    1417|     12753|     39319(3.08)|     28917(2.27)|26.46|
> | 10|    1203|     12030|     37136(3.09)|     26962(2.24)|27.40|
> | 11|     474|      5214|     16072(3.08)|     11690(2.24)|27.26|
> | 12|     398|      4776|     14714(3.08)|     10647(2.23)|27.64|
> | 13|     164|      2132|      6532(3.06)|      4757(2.23)|27.17|
> | 14|     122|      1708|      5232(3.06)|      3801(2.23)|27.35|
> | 15|      50|       750|      2283(3.04)|      1634(2.18)|28.43|
> | 16|      29|       464|      1419(3.06)|      1024(2.21)|27.84|
> | 17|       8|       136|       405(2.98)|       301(2.21)|25.68|
>
> |All|  240823|    897561|   2868626(3.20)|   2290932(2.55)|20.14|
>
>
>
> 23. unihan-4096
>
> |  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
> |  1|    4427|      4427|     14957(3.38)|     13899(3.14)| 7.07|
> |  2|   57418|    114836|    384468(3.35)|    332156(2.89)|13.61|
> |  3|   41335|    124005|    401283(3.24)|    336045(2.71)|16.26|
> |  4|   89296|    357184|   1139404(3.19)|    902406(2.53)|20.80|
> |  5|   21091|    105455|    332420(3.15)|    258709(2.45)|22.17|
> |  6|   15128|     90768|    284134(3.13)|    213522(2.35)|24.85|
> |  7|    5181|     36267|    112576(3.10)|     83844(2.31)|25.52|
> |  8|    3082|     24656|     76272(3.09)|     56083(2.27)|26.47|
> |  9|    1417|     12753|     39319(3.08)|     28883(2.26)|26.54|
> | 10|    1203|     12030|     37136(3.09)|     26935(2.24)|27.47|
> | 11|     474|      5214|     16072(3.08)|     11684(2.24)|27.30|
> | 12|     398|      4776|     14714(3.08)|     10632(2.23)|27.74|
> | 13|     164|      2132|      6532(3.06)|      4751(2.23)|27.27|
> | 14|     122|      1708|      5232(3.06)|      3794(2.22)|27.48|
> | 15|      50|       750|      2283(3.04)|      1630(2.17)|28.60|
> | 16|      29|       464|      1419(3.06)|      1026(2.21)|27.70|
> | 17|       8|       136|       405(2.98)|       301(2.21)|25.68|
>
> |All|  240823|    897561|   2868626(3.20)|   2286300(2.55)|20.30|
>
>
>
> 24. unihan-4096-D
>
> |  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
> |  1|    4427|      4427|     14957(3.38)|     13909(3.14)| 7.01|
> |  2|   57418|    114836|    384468(3.35)|    332799(2.90)|13.44|
> |  3|   41335|    124005|    401283(3.24)|    335682(2.71)|16.35|
> |  4|   89296|    357184|   1139404(3.19)|    905086(2.53)|20.56|
> |  5|   21091|    105455|    332420(3.15)|    259944(2.46)|21.80|
> |  6|   15128|     90768|    284134(3.13)|    215353(2.37)|24.21|
> |  7|    5181|     36267|    112576(3.10)|     84893(2.34)|24.59|
> |  8|    3082|     24656|     76272(3.09)|     56682(2.30)|25.68|
> |  9|    1417|     12753|     39319(3.08)|     29273(2.30)|25.55|
> | 10|    1203|     12030|     37136(3.09)|     27189(2.26)|26.79|
> | 11|     474|      5214|     16072(3.08)|     11762(2.26)|26.82|
> | 12|     398|      4776|     14714(3.08)|     10674(2.23)|27.46|
> | 13|     164|      2132|      6532(3.06)|      4770(2.24)|26.97|
> | 14|     122|      1708|      5232(3.06)|      3803(2.23)|27.31|
> | 15|      50|       750|      2283(3.04)|      1630(2.17)|28.60|
> | 16|      29|       464|      1419(3.06)|      1028(2.22)|27.55|
> | 17|       8|       136|       405(2.98)|       300(2.21)|25.93|
>
> |All|  240823|    897561|   2868626(3.20)|   2294777(2.56)|20.00|
>
>
>
> 25. unihan-4096-DAMP075-SKEW48
>
> |  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
> |  1|    4427|      4427|     14957(3.38)|     13899(3.14)| 7.07|
> |  2|   57418|    114836|    375901(3.27)|    324587(2.83)|13.65|
> |  3|   41335|    124005|    394416(3.18)|    330550(2.67)|16.19|
> |  4|   89296|    357184|   1126357(3.15)|    890277(2.49)|20.96|
> |  5|   21091|    105455|    329783(3.13)|    255913(2.43)|22.40|
> |  6|   15128|     90768|    282751(3.12)|    211339(2.33)|25.26|
> |  7|    5181|     36267|    112181(3.09)|     83126(2.29)|25.90|
> |  8|    3082|     24656|     76111(3.09)|     55712(2.26)|26.80|
> |  9|    1417|     12753|     39285(3.08)|     28699(2.25)|26.95|
> | 10|    1203|     12030|     37150(3.09)|     26767(2.23)|27.95|
> | 11|     474|      5214|     16028(3.07)|     11603(2.23)|27.61|
> | 12|     398|      4776|     14712(3.08)|     10567(2.21)|28.17|
> | 13|     164|      2132|      6528(3.06)|      4735(2.22)|27.47|
> | 14|     122|      1708|      5248(3.07)|      3762(2.20)|28.32|
> | 15|      50|       750|      2281(3.04)|      1628(2.17)|28.63|
> | 16|      29|       464|      1425(3.07)|      1017(2.19)|28.63|
> | 17|       8|       136|       404(2.97)|       301(2.21)|25.50|
>
> |All|  240823|    897561|   2835518(3.16)|   2254482(2.51)|20.49|
>
>
>
> 26. unihan-4096-DUDE
>
> |  N|    FREQ|    N*FREQ|  SUM OF DUDE(X)| SUM OF LDUDE(Y)| COMP|
> |  1|    4427|      4427|     17708(4.00)|     17708(4.00)| 0.00|
> |  2|   57418|    114836|    443874(3.87)|    409657(3.57)| 7.71|
> |  3|   41335|    124005|    474117(3.82)|    408039(3.29)|13.94|
> |  4|   89296|    357184|   1361917(3.81)|   1074237(3.01)|21.12|
> |  5|   21091|    105455|    401146(3.80)|    308378(2.92)|23.13|
> |  6|   15128|     90768|    344208(3.79)|    250925(2.76)|27.10|
> |  7|    5181|     36267|    137275(3.79)|     99475(2.74)|27.54|
> |  8|    3082|     24656|     93013(3.77)|     65889(2.67)|29.16|
> |  9|    1417|     12753|     48000(3.76)|     34230(2.68)|28.69|
> | 10|    1203|     12030|     45427(3.78)|     31663(2.63)|30.30|
> | 11|     474|      5214|     19564(3.75)|     13708(2.63)|29.93|
> | 12|     398|      4776|     18013(3.77)|     12468(2.61)|30.78|
> | 13|     164|      2132|      7969(3.74)|      5590(2.62)|29.85|
> | 14|     122|      1708|      6377(3.73)|      4476(2.62)|29.81|
> | 15|      50|       750|      2811(3.75)|      1926(2.57)|31.48|
> | 16|      29|       464|      1749(3.77)|      1213(2.61)|30.65|
> | 17|       8|       136|       508(3.74)|       355(2.61)|30.12|
>
> |All|  240823|    897561|   3423676(3.81)|   2739937(3.05)|19.97|
>
>
>
> 27. unihan-SC-4096 ( SC only or SC+TC mixed )
>
> |  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
> |  1|     769|       769|      2717(3.53)|      2378(3.09)|12.48|
> |  2|   16065|     32130|    108598(3.38)|     92597(2.88)|14.73|
> |  3|   14315|     42945|    139693(3.25)|    116054(2.70)|16.92|
> |  4|   48871|    195484|    623650(3.19)|    491073(2.51)|21.26|
> |  5|   12135|     60675|    190928(3.15)|    147721(2.43)|22.63|
> |  6|   10463|     62778|    196038(3.12)|    146516(2.33)|25.26|
> |  7|    3594|     25158|     77931(3.10)|     57412(2.28)|26.33|
> |  8|    2373|     18984|     58686(3.09)|     42907(2.26)|26.89|
> |  9|    1078|      9702|     29875(3.08)|     21736(2.24)|27.24|
> | 10|     934|      9340|     28786(3.08)|     20855(2.23)|27.55|
> | 11|     392|      4312|     13279(3.08)|      9612(2.23)|27.62|
> | 12|     314|      3768|     11579(3.07)|      8376(2.22)|27.66|
> | 13|     144|      1872|      5724(3.06)|      4158(2.22)|27.36|
> | 14|     104|      1456|      4455(3.06)|      3226(2.22)|27.59|
> | 15|      41|       615|      1868(3.04)|      1348(2.19)|27.84|
> | 16|      25|       400|      1219(3.05)|       887(2.22)|27.24|
> | 17|       7|       119|       353(2.97)|       264(2.22)|25.21|
>
> |All|  111624|    470507|   1495379(3.18)|   1167120(2.48)|21.95|
>
>
>
> 28. unihan-TC-4096 ( TC only )
>
> |  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
> |  1|    3658|      3658|     12240(3.35)|     11521(3.15)| 5.87|
> |  2|   41353|     82706|    275870(3.34)|    239559(2.90)|13.16|
> |  3|   27020|     81060|    261590(3.23)|    219991(2.71)|15.90|
> |  4|   40425|    161700|    515754(3.19)|    411333(2.54)|20.25|
> |  5|    8956|     44780|    141492(3.16)|    110988(2.48)|21.56|
> |  6|    4665|     27990|     88096(3.15)|     67006(2.39)|23.94|
> |  7|    1587|     11109|     34645(3.12)|     26432(2.38)|23.71|
> |  8|     709|      5672|     17586(3.10)|     13176(2.32)|25.08|
> |  9|     339|      3051|      9444(3.10)|      7147(2.34)|24.32|
> | 10|     269|      2690|      8350(3.10)|      6080(2.26)|27.19|
> | 11|      82|       902|      2793(3.10)|      2072(2.30)|25.81|
> | 12|      84|      1008|      3135(3.11)|      2256(2.24)|28.04|
> | 13|      20|       260|       808(3.11)|       593(2.28)|26.61|
> | 14|      18|       252|       777(3.08)|       568(2.25)|26.90|
> | 15|       9|       135|       415(3.07)|       282(2.09)|32.05|
> | 16|       4|        64|       200(3.12)|       139(2.17)|30.50|
> | 17|       1|        17|        52(3.06)|        37(2.18)|28.85|
>
> |All|  129199|    427054|   1373247(3.22)|   1119180(2.62)|18.50|
>
>
>




From owner-idn@ops.ietf.org  Fri Oct 19 00:31:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26108
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 00:31:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uR9I-000Okw-00
	for idn-data@psg.com; Thu, 18 Oct 2001 21:20:44 -0700
Received: from smtp22.singnet.com.sg ([165.21.101.202])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uR9G-000Okf-00
	for idn@ops.ietf.org; Thu, 18 Oct 2001 21:20:42 -0700
Received: from jamessonyvaio (58charlie253.singnet.com.sg [165.21.214.167])
	by smtp22.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9J4NfJ08158;
	Fri, 19 Oct 2001 12:23:41 +0800
Message-ID: <048b01c15855$60e8d2a0$0501000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Mark Davis" <mark@macchiato.com>, "Kenneth Whistler" <kenw@sybase.com>
Cc: <idn@ops.ietf.org>
References: <200110190328.UAA15512@birdie.sybase.com> <006801c15853$3426c350$0c680b41@c1340594a>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 12:20:24 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Thanks Ken & Mark for note. I defer to your opinion in this.

-James Seng

----- Original Message -----
From: "Mark Davis" <mark@macchiato.com>
To: "Kenneth Whistler" <kenw@sybase.com>; <jseng@pobox.org.sg>
Cc: <idn@ops.ietf.org>
Sent: Friday, October 19, 2001 12:04 PM
Subject: Re: [idn] call for comments for REORDERING


> Ken is right; collation is *quite* complex. Anyone wanting to see some
of
> what is involved can look at the ICU implementation (which is UCA and
ISO
> 14651 compliant, and open-source):
>
> User Guide:
> http://www-124.ibm.com/icu/userguide/Collate_Intro.html
>
> Internal Design:
>
http://oss.software.ibm.com/cvs/icu/~checkout~/icuhtml/design/collation/
ICU_
> collation_design.htm
> (source files are linked from there)
>
> ICU home:
> http://oss.software.ibm.com/icu/
>
> While the perfomance is good, the code is many, many orders of
magnitude
> more complicated than the current nameprep. It is not appropriate for
IDN.
>
> Mark
>
> —————
>
> Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
> [http://www.macchiato.com]
>
> ----- Original Message -----
> From: "Kenneth Whistler" <kenw@sybase.com>
> To: <jseng@pobox.org.sg>
> Cc: <idn@ops.ietf.org>
> Sent: Thursday, October 18, 2001 8:28 PM
> Subject: Re: [idn] call for comments for REORDERING
>
>
> > James Seng said:
> >
> > > Third, I would really prefer to reference a work from established
expert
> > > group if possible. For example, ISO/IEC JTC1/SC22/WG20 publishes
ISO
> > > 14651 on weighted sorting. I am not sure how ISO 14651 would
perform for
> > > the IDN purpose but I thought it might be worthwhile to examine.
> >
> > As one of the principal authors of ISO 14651, who has also
implemented
> > the synchronized Unicode Technical Standard #10, the Unicode
Collation
> > Algorithm, I can attest that this is a very tricky and complicated
> > area, and the algorithms to do all this correctly are not the kind
> > you can write on the back of a cocktail napkin. It is very complex
> > to get all the details right and to get good-performing algorithms
> > (in speed and in resource usage). It is also very difficult for
> > independent implementations to get themselves all exactly lined
> > up, and even more difficult for independent implementations to
*prove*
> > that they are getting the same results for all data (as opposed to
> > a particular result for one set of data -- which is pretty easy).
> >
> > IDN doesn't need to add this kind of headache to the already
> > complex enough issues of nameprep.
> >
> > >
> > > Whatever the case, we should make a decision quickly on this. Lets
not
> > > drag this further if possible.
> > >
> > > -James Seng
> > >
> > > ----- Original Message -----
> > > From: "Martin Duerst" <duerst@w3.org>
> >
> > > > So this is a solution in search of a real problem,
> > > > not worth bothering the whole world with additional
> > > > complexity.
> >
> > I heartily concur with Martin's assessment.
> >
> > --Ken Whistler
> >
> >
> >
>




From owner-idn@ops.ietf.org  Fri Oct 19 00:33:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26123
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 00:33:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uRDv-000OxQ-00
	for idn-data@psg.com; Thu, 18 Oct 2001 21:25:31 -0700
Received: from smtp24.singnet.com.sg ([165.21.101.204])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uRDs-000Owy-00
	for idn@ops.ietf.org; Thu, 18 Oct 2001 21:25:29 -0700
Received: from jamessonyvaio (58charlie253.singnet.com.sg [165.21.214.167])
	by smtp24.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9J4Q3S15926;
	Fri, 19 Oct 2001 12:26:03 +0800
Message-ID: <04cf01c15856$1033da70$0501000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "James Seng/Personal" <jseng@pobox.org.sg>,
        "Mark Davis" <mark@macchiato.com>,
        "Kenneth Whistler" <kenw@sybase.com>
Cc: <idn@ops.ietf.org>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 12:24:57 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Erm, I mean I concur with your opinion. (s/defer/concur/) Sorry if
anyone misunderstood me.

-James Seng

----- Original Message -----
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Mark Davis" <mark@macchiato.com>; "Kenneth Whistler"
<kenw@sybase.com>
Cc: <idn@ops.ietf.org>
Sent: Friday, October 19, 2001 12:20 PM
Subject: Re: [idn] call for comments for REORDERING


> Thanks Ken & Mark for note. I defer to your opinion in this.
>
> -James Seng
>
> ----- Original Message -----
> From: "Mark Davis" <mark@macchiato.com>
> To: "Kenneth Whistler" <kenw@sybase.com>; <jseng@pobox.org.sg>
> Cc: <idn@ops.ietf.org>
> Sent: Friday, October 19, 2001 12:04 PM
> Subject: Re: [idn] call for comments for REORDERING
>
>
> > Ken is right; collation is *quite* complex. Anyone wanting to see
some
> of
> > what is involved can look at the ICU implementation (which is UCA
and
> ISO
> > 14651 compliant, and open-source):
> >
> > User Guide:
> > http://www-124.ibm.com/icu/userguide/Collate_Intro.html
> >
> > Internal Design:
> >
>
http://oss.software.ibm.com/cvs/icu/~checkout~/icuhtml/design/collation/
> ICU_
> > collation_design.htm
> > (source files are linked from there)
> >
> > ICU home:
> > http://oss.software.ibm.com/icu/
> >
> > While the perfomance is good, the code is many, many orders of
> magnitude
> > more complicated than the current nameprep. It is not appropriate
for
> IDN.
> >
> > Mark
> >
> > —————
> >
> > Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
> > [http://www.macchiato.com]
> >
> > ----- Original Message -----
> > From: "Kenneth Whistler" <kenw@sybase.com>
> > To: <jseng@pobox.org.sg>
> > Cc: <idn@ops.ietf.org>
> > Sent: Thursday, October 18, 2001 8:28 PM
> > Subject: Re: [idn] call for comments for REORDERING
> >
> >
> > > James Seng said:
> > >
> > > > Third, I would really prefer to reference a work from
established
> expert
> > > > group if possible. For example, ISO/IEC JTC1/SC22/WG20 publishes
> ISO
> > > > 14651 on weighted sorting. I am not sure how ISO 14651 would
> perform for
> > > > the IDN purpose but I thought it might be worthwhile to examine.
> > >
> > > As one of the principal authors of ISO 14651, who has also
> implemented
> > > the synchronized Unicode Technical Standard #10, the Unicode
> Collation
> > > Algorithm, I can attest that this is a very tricky and complicated
> > > area, and the algorithms to do all this correctly are not the kind
> > > you can write on the back of a cocktail napkin. It is very complex
> > > to get all the details right and to get good-performing algorithms
> > > (in speed and in resource usage). It is also very difficult for
> > > independent implementations to get themselves all exactly lined
> > > up, and even more difficult for independent implementations to
> *prove*
> > > that they are getting the same results for all data (as opposed to
> > > a particular result for one set of data -- which is pretty easy).
> > >
> > > IDN doesn't need to add this kind of headache to the already
> > > complex enough issues of nameprep.
> > >
> > > >
> > > > Whatever the case, we should make a decision quickly on this.
Lets
> not
> > > > drag this further if possible.
> > > >
> > > > -James Seng
> > > >
> > > > ----- Original Message -----
> > > > From: "Martin Duerst" <duerst@w3.org>
> > >
> > > > > So this is a solution in search of a real problem,
> > > > > not worth bothering the whole world with additional
> > > > > complexity.
> > >
> > > I heartily concur with Martin's assessment.
> > >
> > > --Ken Whistler
> > >
> > >
> > >
> >
>




From owner-idn@ops.ietf.org  Fri Oct 19 00:40:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26210
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 00:40:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uRM5-000PCe-00
	for idn-data@psg.com; Thu, 18 Oct 2001 21:33:57 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uRM4-000PCW-00
	for idn@ops.ietf.org; Thu, 18 Oct 2001 21:33:56 -0700
Received: from amc by nicemice.net with local (Exim 3.32 #1 (Debian))
	id 15uRM3-0004Ks-00
	for <idn@ops.ietf.org>; Thu, 18 Oct 2001 21:33:55 -0700
Date: Fri, 19 Oct 2001 04:33:55 +0000
From: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>
To: idn@ops.ietf.org
Subject: Re: [idn] call for comments for REORDERING
Message-ID: <20011019043355.E15989@nicemice.net>
Reply-To: IETF idn working group <idn@ops.ietf.org>
References: <200110190328.UAA15512@birdie.sybase.com> <006801c15853$3426c350$0c680b41@c1340594a>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <006801c15853$3426c350$0c680b41@c1340594a>
User-Agent: Mutt/1.3.22i
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Mark Davis <mark@macchiato.com> wrote:

> Ken is right; collation is *quite* complex.

I don't doubt that, but I don't see the relevance to the reordering
proposal, which would map each code point to another code point (in a
reversible way) just before ACE encoding, and would apply the reverse
mapping just after ACE decoding.  Complexity is indeed a concern, but
this is nowhere near as complex as collation, because it operates on
individual code points, not strings.

Do the NICs have some numbers for us?  Soobok Lee has used the names in
the VGRS testbed both to train his reordering tables and to evaluate
their effectiveness.  It would be very interesting to see how effective
the latest tables are for names from other registries, like the Japan,
China, and Taiwan NICs.

AMC



From owner-idn@ops.ietf.org  Fri Oct 19 00:58:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26419
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 00:58:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uRdC-000PbU-00
	for idn-data@psg.com; Thu, 18 Oct 2001 21:51:38 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uRdB-000PbO-00
	for idn@ops.ietf.org; Thu, 18 Oct 2001 21:51:37 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id NAA22269;
	Fri, 19 Oct 2001 13:51:26 +0900
Message-ID: <008d01c15859$da83aa00$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <003d01c1584b$f90b66b0$ec1bd9d2@temp> <045c01c15854$94e4bc00$0501000a@jamessonyvaio>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 13:52:28 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA26419


----- Original Message ----- 
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>; "Martin Duerst" <duerst@w3.org>
Sent: Friday, October 19, 2001 1:14 PM
Subject: Re: [idn] call for comments for REORDERING


> Your answer does not answer how we going to update re-ordering in future
> with new codepoints. Do you expect to continue to work with this and to
> have update RFC for it? And we going to update RFC again and again? The
> typical solution IETF use for this is IANA action and that involves a
> well-defined policy which IANA could reused for future addition. But if
> we do so, we also need to consider if we are imposing codepoints issues
> which is best dealt with other organisation.
> 
> As I repeated, I really like to point to another organisation for these
> tables if possible. If ISO 14651 is not suitable (as Ken & Mark said),
> then we look at some others. If there is none, then maybe we should
> consider NOT to do it at all.

James,
I full-heartedly welcome any change to REORDERING tables from authoritative
organizations. 

But i dont' agree on using ISO 14651  like Mark and Ken.

 REORDERING has no intersection with ISO 14651 (string comparison service), which is about collation of unicode points, how to sort unicode strings.
ISO 14651 has nothing to do with what REORDERING would provide with.

REORDERING exists for reducing successive code distances in ACE encodings.
REOREDERING is based on RENUMBERING code points values by character frequency, 
but ISO14651 takes some variants of lexicographical ordering for various needs
and exists for comparisons , not for supporing subtraction  between
any two code points values.

ISO 14651 is totally irrelvant to REORDERING.

REORDERING tables are hidden in the ACE routines, not for reference 
material for the general public. 
The reordering mappings are a kind of huge tuning paramters set geared for 
ACE.

Tuning parameters need authorities ?  NOT bad idea, but also not neccesary
because frequency based tables are always suboptimal in its nature  however
authoratitive organizations approve and issuse them.


Soobok Lee

 




From owner-idn@ops.ietf.org  Fri Oct 19 01:27:35 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27808
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 01:27:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uS5G-0000ZJ-00
	for idn-data@psg.com; Thu, 18 Oct 2001 22:20:38 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uS5F-0000Z8-00
	for idn@ops.ietf.org; Thu, 18 Oct 2001 22:20:37 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id OAA31322;
	Fri, 19 Oct 2001 14:20:26 +0900
Message-ID: <009601c1585d$e7612230$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <007601c15854$30c1f800$ec1bd9d2@temp> <046001c15855$02854f40$0501000a@jamessonyvaio>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 14:21:27 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id BAA27808


----- Original Message ----- 
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
Sent: Friday, October 19, 2001 1:17 PM
Subject: Re: [idn] call for comments for REORDERING


> You dont get my point.
> 
> Reordering achieve shorter by putting more oftenly used characters in
> one block and others at the back. BUT this also means less oftenly used
> characters would result in a *LONGER* label then usual. 

No. Even For GROUPS of those rare cases, we get Always SHORTER labels than usual.

For example, 
if REORDERING uses a frequent characters set of length 4096 in entire 20992-letter
han ideographic script block, rarely used han letter will be put
into the subblock of length 20992-4096 = 16896 which is 20% shorter than 20992.

let's assume we have with a label consisting of only those characters from 16896 block. without reordering, they are randomly distributed in 20992 letter block.
with reordering, they are in shorter 16896-letter block.
In the latter case, we got shorter successive code distances and shorter
ACE labels than in the former one.

 Even without REORDERING, ACE has favored some of them, and disfavored
others. But, with REORDERING, BOTH groups get shorter ACE labels.
That is the virtue of REORDERING.

Soobok

> And who are we
> to say these less oftenly used characters are less important or worst,
> become invalid (too long to fit) because of this reordering?
> 
> -James Seng
> 
 







From owner-idn@ops.ietf.org  Fri Oct 19 02:15:41 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08018
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 02:15:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uSn9-0001zc-00
	for idn-data@psg.com; Thu, 18 Oct 2001 23:05:59 -0700
Received: from imo-r05.mx.aol.com ([152.163.225.101])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uSn8-0001zW-00
	for idn@ops.ietf.org; Thu, 18 Oct 2001 23:05:58 -0700
Received: from DougEwell2@cs.com
	by imo-r05.mx.aol.com (mail_out_v31_r1.8.) id i.15f.2876ee9 (16488);
	Fri, 19 Oct 2001 02:05:53 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <15f.2876ee9.29011cc1@cs.com>
Date: Fri, 19 Oct 2001 02:05:53 EDT
Subject: Re: [idn] call for comments for REORDERING
To: idn@ops.ietf.org
CC: lsb@postel.co.kr, jseng@pobox.org.sg, duerst@w3.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a message dated 2001-10-18 21:33:55 Pacific Daylight Time, 
lsb@postel.co.kr writes:

>  1) saturations in TLD namespaces would require longer names for which
>      REORDERING is designed to give greater benefits/compression ratio.

Is it not the case that logographic/ideographic writing systems such as Han 
and the syllable-oriented Unicode encoding of Hangul, with their large 
numbers of characters, convey more information per character than alphabetic 
scripts?  How long, conceptually, does a domain name really need to be?

I would probably have a warmer spot in my heart for these script-specific 
compression proposals if I were convinced that the users of Han and Hangul 
were somehow being cheated by not being able to register the equivalent of 
"FourthDistrictCentralProvincialLibraryBoardOfDirectors.org" as a domain name.

>      2.0) the character frequency table are constructed from
>           Verisign GRS' ML.com testbeds.
>           Even for chinese han script, their
>            registrations came from China/TAIWAN/JAPAN/KOREA and other
>             non-asian squatters.

I know that Soobok is not specifically listing this as a goal, but I thought 
efforts to accommodate the 15-character-and-longer Han domain names that have 
already been registered was explicitly a non-goal, since those businesses and 
individuals were supposed to have waited until an IDN solution was in place.

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Fri Oct 19 02:39:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09298
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 02:39:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uTBV-0002nF-00
	for idn-data@psg.com; Thu, 18 Oct 2001 23:31:09 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uTBU-0002n8-00
	for idn@ops.ietf.org; Thu, 18 Oct 2001 23:31:08 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id PAA20703;
	Fri, 19 Oct 2001 15:30:48 +0900
Message-ID: <00ec01c15867$bc932440$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <DougEwell2@cs.com>, <idn@ops.ietf.org>
Cc: <jseng@pobox.org.sg>, <duerst@w3.org>
References: <15f.2876ee9.29011cc1@cs.com>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 15:31:50 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id CAA09298


----- Original Message ----- 
From: <DougEwell2@cs.com>
To: <idn@ops.ietf.org>
Cc: <lsb@postel.co.kr>; <jseng@pobox.org.sg>; <duerst@w3.org>
Sent: Friday, October 19, 2001 3:05 PM
Subject: Re: [idn] call for comments for REORDERING


> In a message dated 2001-10-18 21:33:55 Pacific Daylight Time, 
> lsb@postel.co.kr writes:
> 
> >  1) saturations in TLD namespaces would require longer names for which
> >      REORDERING is designed to give greater benefits/compression ratio.
> 
> Is it not the case that logographic/ideographic writing systems such as Han 
> and the syllable-oriented Unicode encoding of Hangul, with their large 
> numbers of characters, convey more information per character than alphabetic 
> scripts?  How long, conceptually, does a domain name really need to be?
> 
> I would probably have a warmer spot in my heart for these script-specific 
> compression proposals if I were convinced that the users of Han and Hangul 
> were somehow being cheated by not being able to register the equivalent of 
> "FourthDistrictCentralProvincialLibraryBoardOfDirectors.org" as a domain name.


First) REORDERING is  useful for very common  han/hangeul labels of length 4~8.

Second) If we take into consideration the additional length of subdomains of a
IDN, the total length of  <ML-subdomain>.<ML>.com  often  exceeds
14. ANd if we think about mailbox name in ML@Sub-ML.ML.com, it will exceed 20.
IN that case, the Sum of the lengths of  saved characters in each substring in ML@SUB-ML.ML.com will be great, around 15~20, i guess.

http://www.cnnic.net/daily/2001-8/9.shtml
will answer some of your questions.
We should not attempt to draw an upper limit on future  applications of 
han/hangeul IDN domains by imposing unfair disadvantage on max length 
of Han/hangeul labels .

Soobok Lee


> 
> >      2.0) the character frequency table are constructed from
> >           Verisign GRS' ML.com testbeds.
> >           Even for chinese han script, their
> >            registrations came from China/TAIWAN/JAPAN/KOREA and other
> >             non-asian squatters.
> 
> I know that Soobok is not specifically listing this as a goal, but I thought 
> efforts to accommodate the 15-character-and-longer Han domain names that have 
> already been registered was explicitly a non-goal, since those businesses and 
> individuals were supposed to have waited until an IDN solution was in place.
> 
> -Doug Ewell
>  Fullerton, California
> 




From owner-idn@ops.ietf.org  Fri Oct 19 04:34:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12455
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 04:34:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uUp2-0006I9-00
	for idn-data@psg.com; Fri, 19 Oct 2001 01:16:04 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uUp1-0006Hd-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 01:16:03 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 240D07F45F; Fri, 19 Oct 2001 17:15:11 +0900 (JST)
Message-Id: <4.2.0.58.J.20011019155811.03d67490@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 19 Oct 2001 16:05:35 +0900
To: DougEwell2@cs.com, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
Cc: lsb@postel.co.kr, jseng@pobox.org.sg
In-Reply-To: <15f.2876ee9.29011cc1@cs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 02:05 01/10/19 -0400, DougEwell2@cs.com wrote:
>In a message dated 2001-10-18 21:33:55 Pacific Daylight Time,
>lsb@postel.co.kr writes:
>
> >  1) saturations in TLD namespaces would require longer names for which
> >      REORDERING is designed to give greater benefits/compression ratio.
>
>Is it not the case that logographic/ideographic writing systems such as Han
>and the syllable-oriented Unicode encoding of Hangul, with their large
>numbers of characters, convey more information per character than alphabetic
>scripts?

Very much so, of course.

>How long, conceptually, does a domain name really need to be?

That's a very subjective question, because 'real need' is very
subjective.


>I would probably have a warmer spot in my heart for these script-specific
>compression proposals if I were convinced that the users of Han and Hangul
>were somehow being cheated by not being able to register the equivalent of
>"FourthDistrictCentralProvincialLibraryBoardOfDirectors.org" as a domain name.

In various Japanese translations, I get between 14 and 18 characters.
But I think the fact that such domain names can be (and is some strange
cases even are) registered in English is rather by accident (the designers
of the internal DNS format decided to reserve 2 out of 8 bits, which leaves
6 for the label length, thus a max length of 64. If it were 5 bits, it
would be 31. That wouldn't have affected the spread of the Internet and
the Web in any way.

Regards,   Martin.



From owner-idn@ops.ietf.org  Fri Oct 19 04:34:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12479
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 04:34:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uUp2-0006IA-00
	for idn-data@psg.com; Fri, 19 Oct 2001 01:16:04 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uUp1-0006Hc-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 01:16:03 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 5CF017F45E; Fri, 19 Oct 2001 17:15:10 +0900 (JST)
Message-Id: <4.2.0.58.J.20011019152610.037f1100@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 19 Oct 2001 15:46:26 +0900
To: "Soobok Lee" <lsb@postel.co.kr>,
        "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
In-Reply-To: <003d01c1584b$f90b66b0$ec1bd9d2@temp>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <024b01c15847$11e8b430$0501000a@jamessonyvaio>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 12:13 01/10/19 +0900, Soobok Lee wrote:

> > And with the existing draft, it does not explain how it going to deal
> > with new codepoints in ISO10646 in the future, nor does it explain the
> > process to implementing them. The critia here is stablity - if new code
> > is added and tables for re-ordering expand, then the algorithm should
> > not make existing names invalided.

I think this is an extremely important concern.


>REORDERING's mapping occurs within each script block, NOT across script 
>blocks.
>Therefore, new additions of script block won't invalidate or collide
>with existing names. Even additions of new rarely used characters in
>existing script block won't affect the performance of REORDERING.
>In this respect, REORDERING maintains stability over time.

For additions of rare characters, in most cases yes.
But let's assume that these are characters that are not
used in one language (A), but quite frequent in another (B).
People using language (B) might then come forward and ask
for a different reordering to fit their language better.

In general, it's easily possible that the statistics you
currently have favor e.g. the major language that uses
that script, but disfavor another language. It could e.g.
be that the reordering for Arabic makes Arabic names shorter,
but makes Farsi or Urdu names longer. Even if there may
be many more Arabic than Farsi or Urdu names, this would
be quite a bit unfair. And we just don't have enough data
at the moment to be able to say this is not the case.


>Current IDNA/nameprep does not prohibit, but discourage including 
>unassigned code points in legal IDN labels, because new normalization/case 
>mappings
>would be defined on them in the future. some ACE labels including unsigned 
>code block (tagalog?) might be proven invalid in the future. Nameprep/NFKC 
>Versioning tag schems using new ACE prefix will be needed in the future, i 
>guess.

Yes. But for the majority of really useful characters, in old
and new scripts, it's rather obvious that they will be allowed.
On the other hand, it's totally unclear how to reorder them.

Also, in case of some implementation mistake in Nameprep/NFKC,
in most cases, it will just make a few names unusable, but
not affect the rest. For reordering, a bug will completely
confuse a whole script.

Also, now we have a testbed, and you just think that the testbed
is representative. But once IDN is running, to run a testbed
for a new script will be difficult, because we need the testbed
data for the reordering statistics, but we need the reordering
for the testbed.


>Therefore, REORDERING  follows the same IDNA/nameprep recommendations on 
>the issues
>of new SCTIPT blocks/unsigned code points.
>
>This statements will be included in the final version of REORDERING I-D.

Well, in theory, this works. But I think it's just too unstable
to work in practice.


Regards,    Martin.



From owner-idn@ops.ietf.org  Fri Oct 19 04:47:19 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12607
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 04:47:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uV79-0006xi-00
	for idn-data@psg.com; Fri, 19 Oct 2001 01:34:47 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uV78-0006xZ-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 01:34:46 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id BCFE77F414; Fri, 19 Oct 2001 17:33:57 +0900 (JST)
Message-Id: <4.2.0.58.J.20011018183339.031fa100@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 19 Oct 2001 17:26:42 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
In-Reply-To: <037501c15156$e6da5470$ec1bd9d2@temp>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 15:43 01/10/10 +0900, Soobok Lee wrote:

>From: "Martin Duerst" <duerst@w3.org>

> > The additional complexity introduced by reordering is a very
> > serious problem. It is true that this complexity is somewhat
> > similar to the complexity of e.g. nameprep or conversion from
> > a legacy encoding. However, on many platforms, both conversion
> > from a legacy encoding as well as many aspects of nameprep
> > are available as libraries, and are used for other purposes.
>
>Current Windows 98,2K,XP and Linux  contain   NFKC codes ?

No. My personal preference would be for NFC, anyway, because
most of the additional mappings in NFKC are not really useful,
because they are from characters that are quite difficult
to type in. So these characters could just be forbidden rather
than mapped. The only exception I know is full-width ASCII,
which could either be included in the nameprep mapping step,
or could be done as a front-end 'quality of implementation'
step (similar to how the ideographic fullstop is currently
treated).

Anyway, it's not so much a question of whether current versions
contain that code (there are libraries that do), but how much
other software will use it. There will definitely be other
software that uses NFC, and quite probably also NFKC.
This is not at all the case for reordering.


> > In particular on constrained devices (mobile phones,...),
> > most of nameprep can be simplified a lot if one knows what
> > kinds of characters can be input.
>
>In this case, the reordering table _also_ can be simplified
>only to that input script blocks .

Yes. But NFC or NFKC boils down to nothing for many subsets,
while reordering doesn't.


>As for arabic/hindi/kata/hira/tamil/greek/hebrew,
>it adds only +10~+20 lines of simple character mapping array
>for each script.
>those additional lines of data are less than the # of  comment
>lines in the ACE source code.

The comment lines obviously don't get compiled and
put on a small device.


> > On the other hand, the benefits for the users are actually
> > very small. Nobody wants to input domain names with 15 or
> > more Hanzi or Hangul. Nobody will be able to remember them.
> > Writing them down on a napkin will take a long time.
> > Every company or organization that has such a long label
> > in their domain name, and no shorter alternative, will
> > simply not get any contacts directly to their web site.
> > If they have a short alternative, why do they need a
> > long version? (please note that there is no danger of
> > spoofing by somebody else getting the long version :-).
>
>lets' think about the shorter ACE label produced for the native label of
>mean _average_ length.
>The next table for hangul script block says:
>   For N=6, 3.12*6 - 2.28*6 = 18 - 13 = 5 characters are saved.
>
>The main benefits of REODERING is not only for very long domains,
>but for average ones. It also helps administation,transcription and eye-
>comparison on the ACE labels.

It doesn't really help. Transcription and eye-comparison of
ACE labels is a pain. If they are a bit shorter, it still
just hurts.


>Moreover, as IDNA I-D recommends,
>ACE labels should be rendered "as it is",
>when the decoded native-label contains characters which
>the rendering engine cannot display. For example,
>if you have _no_ huge han script font set in your mobile phone (or PC),
>the ACE labels for han/hangul email addresses of your friends should
>be displayed "as it is". But, it may be often too long to be displayed
>in your narrow phone LCD lines of width 16~20, without REORDERING.

Displaying ACE when nothing else is available is acceptable
as a 'best-effort' solution. But it is very far from a good
solution, and designing the rest of IDN for this doesn't
make sense.

I have no problem with IDNA (if it stays at a SHOULD level),
but on a mobile phone, I would probably just use a few question
marks to make clear that there is something that cannot be
displayed.


>Moreover, If we get ACEed i18n email addresses in the future,
>its native form will look like XXXX@YYYYYY.com. In the case of han/hangul 
>script ,
>the sum of lengths of two non-latin strings (XXXX,YYYYYY) may
>exceed 10 very often.
>For such cases, the reordering would help  to save up to 8~9
>characters for ACEed email addresess. Big saves..

For what? For transcribing ACE? Who wants to do that?
Is that what we are designing IDN for? I very much hope not.


Regards,   Martin.



From owner-idn@ops.ietf.org  Fri Oct 19 04:48:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12687
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 04:48:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uV7A-0006xv-00
	for idn-data@psg.com; Fri, 19 Oct 2001 01:34:48 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uV79-0006xh-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 01:34:47 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 30D0A7F498; Fri, 19 Oct 2001 17:34:00 +0900 (JST)
Message-Id: <4.2.0.58.J.20011019172746.03c91550@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 19 Oct 2001 17:34:33 +0900
To: "James Seng/Personal" <jseng@pobox.org.sg>,
        "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
In-Reply-To: <024b01c15847$11e8b430$0501000a@jamessonyvaio>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hello James,

I agree with most of what you said.

At 09:09 01/10/19 +0800, James Seng/Personal wrote:

>Third, I would really prefer to reference a work from established expert
>group if possible. For example, ISO/IEC JTC1/SC22/WG20 publishes ISO
>14651 on weighted sorting. I am not sure how ISO 14651 would perform for
>the IDN purpose but I thought it might be worthwhile to examine.

14651 just doesn't help at all. I think you already said so in
another mail. Sorting and compression are totally different
problems. [Well, except for the Burrows-Wheeler-Transform,
which uses sorting for compression, but doesn't care about
the sorting order used and only compresses long files,
see http://dogma.net/markn/articles/bwt/bwt.htm.] Also,
the algorithm contains a lot of details to work with
various alphabetic sort orders, but leaves Hangul
(which is already in the right order) and Han
(where there are many different orderings) just the
way they are.


Regards,   Martin.





From owner-idn@ops.ietf.org  Fri Oct 19 04:50:35 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12717
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 04:50:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uVBK-00074C-00
	for idn-data@psg.com; Fri, 19 Oct 2001 01:39:06 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uVBJ-000746-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 01:39:05 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id RAA28068;
	Fri, 19 Oct 2001 17:38:39 +0900
Message-ID: <017b01c15879$99dc8e20$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <4.2.0.58.J.20011019160708.037cccd0@localhost>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 17:39:39 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id EAA12717


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
> >
> >1) saturations in TLD namespaces would require longer names for which
> >     REORDERING is designed to give greater benefits/compression ratio.
> 
> No. What James referred to is that saturation tends to fill up the
> short name slots, and thus flatten the probability distribution.
> I.e. if somebody doesn't get the name they wanted, the chance is
> that they go for something like xq.com, because it's easy to
> remember because it's short. Neither x nor q are very frequent
> letters.

Han/hangeul characters carries meanings while latin alphabets
denote phonemes. Therefore your analogy between latin and han domains
may be false. Chinese people would rather choose to register 
digit-added variants of  alreagy taken desired domains in saturated ML.com,
instead of choosing non-sense irrelevant rare han characters.

Later time, I will provide some proofs that SC and TC only have
small partial set of frequent characters. That's already clear in
SJIS and KSC5601 han characters set which size is less than 5000.

> >INs and OUTs from 4096 ones are rare and does not invalidate the validity 
> >of most frequent 1024 and 2048 ones.
> >Moreover, TC/SC/KC characters are put side-by-side
> 
> Can you explain that better? What about Japanese cases?

KC means "Kanji-specific". ALready addressed. Korea share  TC with TAIWAN.
KC/TC/SC are put side by side in reordering table.

> 
> 
> >to avoid countriy-specific biases in han reordering table.
> >
> >non-CJK scripts often haver small set of basic alphabets, and their
> >character usage patterns are more stable than those for han/hangeul.
> 
> No, many other scripts are used for many more languages, with
> quite different usage patterns. (A lot of Han usage in Japan,
> and most of it in Korea, is due to loanwords from Chinese.)
> 

But, even without Urdu consideration in 
arabic reordering, the efficiency of reordering is always  better than
without it, because the lexicographic ordering in un-reordered 
arabic script block can be regarded as *RANDOM* ordering 
in frequency measure (maximum entropy).
Partial reordering (without Urdu consideration) is always better than
no reordering. 
If Urdu text samples  are available, my arabic reordering table may be
improved to reflect them, though.

SOobok Lee






From owner-idn@ops.ietf.org  Fri Oct 19 05:01:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12819
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 05:01:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uVJt-0007Rm-00
	for idn-data@psg.com; Fri, 19 Oct 2001 01:47:57 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uVJs-0007Rf-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 01:47:57 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id RAA30894;
	Fri, 19 Oct 2001 17:47:41 +0900
Message-ID: <018901c1587a$dd021480$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <4.2.0.58.J.20011019152610.037f1100@localhost>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 17:48:43 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA12819


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
 > 
> >Current IDNA/nameprep does not prohibit, but discourage including 
> >unassigned code points in legal IDN labels, because new normalization/case 
> >mappings
> >would be defined on them in the future. some ACE labels including unsigned 
> >code block (tagalog?) might be proven invalid in the future. Nameprep/NFKC 
> >Versioning tag schems using new ACE prefix will be needed in the future, i 
> >guess.
> 
> Yes. But for the majority of really useful characters, in old
> and new scripts, it's rather obvious that they will be allowed.
> On the other hand, it's totally unclear how to reorder them.
> 
> Also, in case of some implementation mistake in Nameprep/NFKC,
> in most cases, it will just make a few names unusable, but
> not affect the rest. For reordering, a bug will completely
> confuse a whole script.

Never.
REoredering does not touch on unassigned code points at all.
REORDERING is idempotent  for unassigned code points.

> 
> Also, now we have a testbed, and you just think that the testbed
> is representative. But once IDN is running, to run a testbed
> for a new script will be difficult, because we need the testbed
> data for the reordering statistics, but we need the reordering
> for the testbed.
> 
 
Optimal frequency table does not exist now and future and forever.
sub-optimal solutions are often very useful and accepted and 
REORDERING is just one of them.

Soobook Lee




From owner-idn@ops.ietf.org  Fri Oct 19 05:10:35 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12896
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 05:10:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uVPd-0007fA-00
	for idn-data@psg.com; Fri, 19 Oct 2001 01:53:53 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uVPc-0007ez-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 01:53:53 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id RAA32731;
	Fri, 19 Oct 2001 17:53:33 +0900
Message-ID: <018f01c1587b$af216e70$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <DougEwell2@cs.com>, <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
Cc: <jseng@pobox.org.sg>
References: <15f.2876ee9.29011cc1@cs.com> <4.2.0.58.J.20011019162040.03c95df0@localhost>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 17:54:35 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA12896


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; <DougEwell2@cs.com>; <idn@ops.ietf.org>
Cc: <jseng@pobox.org.sg>
Sent: Friday, October 19, 2001 5:12 PM
Subject: Re: [idn] call for comments for REORDERING


> At 15:31 01/10/19 +0900, Soobok Lee wrote:
> 
> >Second) If we take into consideration the additional length of subdomains of a
> >IDN, the total length of  <ML-subdomain>.<ML>.com  often  exceeds
> >14. ANd if we think about mailbox name in ML@Sub-ML.ML.com, it will exceed 20.
> >IN that case, the Sum of the lengths of  saved characters in each 
> >substring in ML@SUB-ML.ML.com will be great, around 15~20, i guess.
> 
> It is a very long standing lesson when working with computers
> that in case there is a tradeoff between a more stable and
> a more compact solution, it's in most cases, and definitely
> in the long term, much better to take the more stable and
> simpler one. The Y2K problem is the best example, but there
> are many other ones.
> 

Your menttion of Stability are presume the variations of frequency
distribtion of characters in a script block. But, as i stated before,
the influence is marginal and REORDERING is not optiomal solution,
but sub-optimal solution that have clear benefits for a long time.

Please read  2500-years-old chinese classic books, then you can 
find there has been no great change in frequent han characters.
Really!!!

You should suggest the proof that the frequency
change will be great in the future and hurt the statbility of
REOERDERING tables.


> 
> >We should not attempt to draw an upper limit on future  applications of
> >han/hangeul IDN domains by imposing unfair disadvantage on max length
> >of Han/hangeul labels .
> 
> I don't see any unfair disadvantage. Both in Latin and in Han/Hangul,
> it's already possible to make names longer than really useful.

You missed what the above examples really shows.
Please think again the sum of length of saved characters in
ML@SUB-ML.ML.com.


> To say that overly long names have been cut off at a different
> point for Latin and for Han or Hangul may be true, but it is
> rather irrelevant. And even with the most advanced compression,
> we will never be able to make sure that we are completely fair
> to everybody.
> 
> 
> Regards,   Martin.
> 




From owner-idn@ops.ietf.org  Fri Oct 19 05:28:27 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12456
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 04:34:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uUoz-0006Hw-00
	for idn-data@psg.com; Fri, 19 Oct 2001 01:16:01 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uUoy-0006Hj-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 01:16:00 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 266A97F469; Fri, 19 Oct 2001 17:15:13 +0900 (JST)
Message-Id: <4.2.0.58.J.20011019162040.03c95df0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 19 Oct 2001 17:12:05 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, <DougEwell2@cs.com>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
Cc: <jseng@pobox.org.sg>
In-Reply-To: <00ec01c15867$bc932440$ec1bd9d2@temp>
References: <15f.2876ee9.29011cc1@cs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 15:31 01/10/19 +0900, Soobok Lee wrote:

>Second) If we take into consideration the additional length of subdomains of a
>IDN, the total length of  <ML-subdomain>.<ML>.com  often  exceeds
>14. ANd if we think about mailbox name in ML@Sub-ML.ML.com, it will exceed 20.
>IN that case, the Sum of the lengths of  saved characters in each 
>substring in ML@SUB-ML.ML.com will be great, around 15~20, i guess.

It is a very long standing lesson when working with computers
that in case there is a tradeoff between a more stable and
a more compact solution, it's in most cases, and definitely
in the long term, much better to take the more stable and
simpler one. The Y2K problem is the best example, but there
are many other ones.


>We should not attempt to draw an upper limit on future  applications of
>han/hangeul IDN domains by imposing unfair disadvantage on max length
>of Han/hangeul labels .

I don't see any unfair disadvantage. Both in Latin and in Han/Hangul,
it's already possible to make names longer than really useful.
To say that overly long names have been cut off at a different
point for Latin and for Han or Hangul may be true, but it is
rather irrelevant. And even with the most advanced compression,
we will never be able to make sure that we are completely fair
to everybody.


Regards,   Martin.



From owner-idn@ops.ietf.org  Fri Oct 19 05:28:28 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12457
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 04:34:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uUoz-0006Hu-00
	for idn-data@psg.com; Fri, 19 Oct 2001 01:16:01 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uUox-0006Hi-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 01:15:59 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 7C9937F464; Fri, 19 Oct 2001 17:15:11 +0900 (JST)
Message-Id: <4.2.0.58.J.20011019160708.037cccd0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 19 Oct 2001 17:15:35 +0900
To: "Soobok Lee" <lsb@postel.co.kr>,
        "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
In-Reply-To: <007601c15854$30c1f800$ec1bd9d2@temp>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <024b01c15847$11e8b430$0501000a@jamessonyvaio>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 13:11 01/10/19 +0900, Soobok Lee wrote:
>Another answer for your concern.
>
>----- Original Message -----
>From: "James Seng/Personal" <jseng@pobox.org.sg>
> >
> > The bigger concern I have with re-ordering remains in the fact that
> > tables mappings proves efficient with existing IDN names in some
> > registries *BUT* it  does not indicate what performance it would be like
> > in the future. We do not know what happened when the names space get
> > saturated and would other names which would have been useable without
> > lsb become un-usuable due to lsb.
> >
>
>1) saturations in TLD namespaces would require longer names for which
>     REORDERING is designed to give greater benefits/compression ratio.

No. What James referred to is that saturation tends to fill up the
short name slots, and thus flatten the probability distribution.
I.e. if somebody doesn't get the name they wanted, the chance is
that they go for something like xq.com, because it's easy to
remember because it's short. Neither x nor q are very frequent
letters.


>2) future variations on character usage frequency in each script
>
>     2.0) the character frequency table are constructed from
>          Verisign GRS' ML.com testbeds.
>          Even for chinese han script, their
>           registrations came from China/TAIWAN/JAPAN/KOREA and other
>            non-asian squatters.
>          Each country of the 4 have their own different han character
>            usage patterns. The reordering table for han , therefore,
>           cannot  for the worst case, the mutual difference in 
> improvement ratios
>           did not exceed  +- 2% around 20%.
>
>     2.1) this issue is already answered by latest REORDERING I-D 2.0
>          see the enclosed excerpts from it. The influence of this
>          frequency variations is marginal.

Well, there are always some variations with marginal influence,
and there are others with much larger influence.


>i believe that frequency fluctuation of han characters over time  is
>WITHIN the frequent set.

Well, it's extremely difficult to predict the future. You may be
right, or you may be wrong.


>INs and OUTs from 4096 ones are rare and does not invalidate the validity 
>of most frequent 1024 and 2048 ones.
>Moreover, TC/SC/KC characters are put side-by-side

Can you explain that better? What about Japanese cases?


>to avoid countriy-specific biases in han reordering table.
>
>non-CJK scripts often haver small set of basic alphabets, and their
>character usage patterns are more stable than those for han/hangeul.

No, many other scripts are used for many more languages, with
quite different usage patterns. (A lot of Han usage in Japan,
and most of it in Korea, is due to loanwords from Chinese.)


>REORDERING does not recommends reordering on shares latin scripts,
>because latin characters are already encoded as it is (in literal mode,
>the most efficient form ). latin script for europeans (0.6 billions) are 
>the most favored one in ACE-Z. There shoulbe be some conpensations for
>non europeans. Han script: 2 billions, Arabic: 0.7 billion, Hindi: 0.5 billion

The main advantage for these scripts is the use of ACE-Z,
when e.g. compared to UTF-8. Reordering is rather minor.


>This new frequency-based reordering is always more efficient than
>original lexicographical ordering in UCS
>even with some fluctuation in future script usage patterns.
>
>We are not pursuing elusive "perfection and optimal" solution.
>REORDERING tables cannot be modified if it is once freezed as standards.

Very true.


>Therefore,REORDERING is a sub-optimal solution in its nature but will be 
>remain
>as a valid and effective solution for a long time .

Valid and effective for a long time is just something you have
to believe in, there is no way to prove it.


Regards,   Martin.



From owner-idn@ops.ietf.org  Fri Oct 19 05:33:22 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13040
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 05:33:21 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uVsK-0008ZJ-00
	for idn-data@psg.com; Fri, 19 Oct 2001 02:23:32 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uVsJ-0008ZC-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 02:23:31 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id SAA09568;
	Fri, 19 Oct 2001 18:23:19 +0900
Message-ID: <01d101c1587f$d6610d20$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <4.2.0.58.J.20011018183339.031fa100@localhost>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 18:24:21 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA13040

> 
> 
> > > In particular on constrained devices (mobile phones,...),
> > > most of nameprep can be simplified a lot if one knows what
> > > kinds of characters can be input.
> >
> >In this case, the reordering table _also_ can be simplified
> >only to that input script blocks .
> 
> Yes. But NFC or NFKC boils down to nothing for many subsets,
> while reordering doesn't.

Never. REORDERING tables are modular and groupd by script blocks.
If you never receive and send han domains, 
you can drop in your implementation.


> 
> 
> >As for arabic/hindi/kata/hira/tamil/greek/hebrew,
> >it adds only +10~+20 lines of simple character mapping array
> >for each script.
> >those additional lines of data are less than the # of  comment
> >lines in the ACE source code.
> 
> The comment lines obviously don't get compiled and
> put on a small device.

You are right. :-)))

Thank you very much  for your interests and comments.

Soobok Lee

 




From owner-idn@ops.ietf.org  Fri Oct 19 05:33:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13051
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 05:33:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uVpe-0008Va-00
	for idn-data@psg.com; Fri, 19 Oct 2001 02:20:46 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uVpd-0008VJ-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 02:20:45 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id SAA08688;
	Fri, 19 Oct 2001 18:20:30 +0900
Message-ID: <01cd01c1587f$71947490$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <4.2.0.58.J.20011018183339.031fa100@localhost>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 18:21:32 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA13051


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
Sent: Friday, October 19, 2001 5:26 PM
Subject: Re: [idn] call for comments for REORDERING


> At 15:43 01/10/10 +0900, Soobok Lee wrote:
> 
> >From: "Martin Duerst" <duerst@w3.org>
> 
> > > The additional complexity introduced by reordering is a very
> > > serious problem. It is true that this complexity is somewhat
> > > similar to the complexity of e.g. nameprep or conversion from
> > > a legacy encoding. However, on many platforms, both conversion
> > > from a legacy encoding as well as many aspects of nameprep
> > > are available as libraries, and are used for other purposes.
> >
> >Current Windows 98,2K,XP and Linux  contain   NFKC codes ?
> 
> No. My personal preference would be for NFC, anyway, because
> most of the additional mappings in NFKC are not really useful,
> because they are from characters that are quite difficult
> to type in. So these characters could just be forbidden rather
> than mapped. The only exception I know is full-width ASCII,
> which could either be included in the nameprep mapping step,
> or could be done as a front-end 'quality of implementation'
> step (similar to how the ideographic fullstop is currently
> treated).

My personal preference is NFKC. Because it solves the mappings between
the extended han ideographic block and han ideo block.

> 
> Anyway, it's not so much a question of whether current versions
> contain that code (there are libraries that do), but how much
> other software will use it. There will definitely be other
> software that uses NFC, and quite probably also NFKC.
> This is not at all the case for reordering.
> 
> 
 
I expect REODERING+ACE may be used also in mailbox name part
in IDN email addressess.
What if the reordering table will find  many other internet
applications in the future like NFC/NFKC. No one knows.

Soobok Lee







From owner-idn@ops.ietf.org  Fri Oct 19 05:38:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13078
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 05:38:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uVxe-0008lQ-00
	for idn-data@psg.com; Fri, 19 Oct 2001 02:29:02 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uVxd-0008lF-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 02:29:01 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id SAA11287;
	Fri, 19 Oct 2001 18:28:48 +0900
Message-ID: <01d501c15880$9a966410$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <4.2.0.58.J.20011018183339.031fa100@localhost>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 18:29:50 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA13078

 
> >
> >The main benefits of REODERING is not only for very long domains,
> >but for average ones. It also helps administation,transcription and eye-
> >comparison on the ACE labels.
> 
> It doesn't really help. Transcription and eye-comparison of
> ACE labels is a pain. If they are a bit shorter, it still
> just hurts.

The pain will be everywhere in mobile devices.
That is why The pain-killing drug are in the world.

> 
> 
> >Moreover, as IDNA I-D recommends,
> >ACE labels should be rendered "as it is",
> >when the decoded native-label contains characters which
> >the rendering engine cannot display. For example,
> >if you have _no_ huge han script font set in your mobile phone (or PC),
> >the ACE labels for han/hangul email addresses of your friends should
> >be displayed "as it is". But, it may be often too long to be displayed
> >in your narrow phone LCD lines of width 16~20, without REORDERING.
> 
> Displaying ACE when nothing else is available is acceptable
> as a 'best-effort' solution. But it is very far from a good
> solution, and designing the rest of IDN for this doesn't
> make sense.
> 
> I have no problem with IDNA (if it stays at a SHOULD level),
> but on a mobile phone, I would probably just use a few question
> marks to make clear that there is something that cannot be
> displayed.
> 
CJK peolple have problems without REORDERING.
Other european folks but You martin (han experts),
won't install han/hangeul fonts even in his/her PCs, i guess.
Most europeans will see leaked ACE labels sometime in the future
when IDN host/email addresses are everywhere and interchanged globally
like LDH ones.  surely,
IDNA WITHOUT REORDERING also become pains for non-CJK folks.

Thanks,

Soobok Lee




From owner-idn@ops.ietf.org  Fri Oct 19 06:05:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13312
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 06:05:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uWMW-0009c2-00
	for idn-data@psg.com; Fri, 19 Oct 2001 02:54:44 -0700
Received: from [133.27.228.201] (helo=toro.w3.mag.keio.ac.jp)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uWMV-0009bp-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 02:54:43 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 550D07F414; Fri, 19 Oct 2001 18:53:55 +0900 (JST)
Message-Id: <4.2.0.58.J.20011019174908.03d8c360@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 19 Oct 2001 17:58:28 +0900
To: "Soobok Lee" <lsb@postel.co.kr>,
        "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
In-Reply-To: <017b01c15879$99dc8e20$ec1bd9d2@temp>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <024b01c15847$11e8b430$0501000a@jamessonyvaio>
 <4.2.0.58.J.20011019160708.037cccd0@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 17:39 01/10/19 +0900, Soobok Lee wrote:

>----- Original Message -----
>From: "Martin Duerst" <duerst@w3.org>
> > >
> > >1) saturations in TLD namespaces would require longer names for which
> > >     REORDERING is designed to give greater benefits/compression ratio.
> >
> > No. What James referred to is that saturation tends to fill up the
> > short name slots, and thus flatten the probability distribution.
> > I.e. if somebody doesn't get the name they wanted, the chance is
> > that they go for something like xq.com, because it's easy to
> > remember because it's short. Neither x nor q are very frequent
> > letters.
>
>Han/hangeul characters carries meanings while latin alphabets
>denote phonemes. Therefore your analogy between latin and han domains
>may be false. Chinese people would rather choose to register
>digit-added variants of  alreagy taken desired domains in saturated ML.com,
>instead of choosing non-sense irrelevant rare han characters.

Some really rare and irrelevant han characters may indeed never
be chosen. But still if you want to name a company, there are
many different possibilities, and people will look for short,
not yet used possibilities (which still make some sense)
rather than use longer and longer names.


>Later time, I will provide some proofs that SC and TC only have
>small partial set of frequent characters. That's already clear in
>SJIS and KSC5601 han characters set which size is less than 5000.

Yes, this is true.


> > >to avoid countriy-specific biases in han reordering table.
> > >
> > >non-CJK scripts often haver small set of basic alphabets, and their
> > >character usage patterns are more stable than those for han/hangeul.
> >
> > No, many other scripts are used for many more languages, with
> > quite different usage patterns. (A lot of Han usage in Japan,
> > and most of it in Korea, is due to loanwords from Chinese.)
> >
>
>But, even without Urdu consideration in
>arabic reordering, the efficiency of reordering is always  better than
>without it, because the lexicographic ordering in un-reordered
>arabic script block can be regarded as *RANDOM* ordering
>in frequency measure (maximum entropy).

It's probably not, because most alphabets contain a few
'late additions'. And just using first order frequency
to bring the most frequent characters to the front may
not be the most efficient way for compression.


>Partial reordering (without Urdu consideration) is always better than
>no reordering.

I don't deny that you may be able to squeeze out a few bits.
But I don't think that should be the aim of this exercise.


>If Urdu text samples  are available, my arabic reordering table may be
>improved to reflect them, though.

Which might then make it less efficient for Arabic.


Regards,   Martin.



From owner-idn@ops.ietf.org  Fri Oct 19 06:05:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13324
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 06:05:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uWMY-0009cI-00
	for idn-data@psg.com; Fri, 19 Oct 2001 02:54:46 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uWMX-0009c6-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 02:54:45 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id DFD847F4D3; Fri, 19 Oct 2001 18:53:57 +0900 (JST)
Message-Id: <4.2.0.58.J.20011019181604.0312ad90@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 19 Oct 2001 18:23:15 +0900
To: "Soobok Lee" <lsb@postel.co.kr>,
        "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
In-Reply-To: <018901c1587a$dd021480$ec1bd9d2@temp>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <024b01c15847$11e8b430$0501000a@jamessonyvaio>
 <4.2.0.58.J.20011019152610.037f1100@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 17:48 01/10/19 +0900, Soobok Lee wrote:

>----- Original Message -----
>From: "Martin Duerst" <duerst@w3.org>
>  >
> > >Current IDNA/nameprep does not prohibit, but discourage including
> > >unassigned code points in legal IDN labels, because new 
> normalization/case
> > >mappings
> > >would be defined on them in the future. some ACE labels including 
> unsigned
> > >code block (tagalog?) might be proven invalid in the future. 
> Nameprep/NFKC
> > >Versioning tag schems using new ACE prefix will be needed in the 
> future, i
> > >guess.

Actually, because we do on purpose not prohibit unassigned codepoints
on the client side, it is completely impossible to introduce reordering
for any script that is added later.

The idea behind this is that if e.g. Tagalog gets added to
Unicode, and the IETF decides to add it to the allowed set
of characters for domain names, then the registries that
want to accept Tagalog have to update their software
immediately (no big deal for them), but deployed software
can use Tagalog without having to change nameprep/ACE
(unless they use characters which have to be normalized,
which may happen but will be rare). So existing clients
will already ACE the Tagalog codepoints without reordering,
and if we introduce reordering for Tagalog, there will
be a mess.


Regards,   Martin.



From owner-idn@ops.ietf.org  Fri Oct 19 06:05:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13336
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 06:05:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uWMW-0009c3-00
	for idn-data@psg.com; Fri, 19 Oct 2001 02:54:44 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uWMV-0009bq-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 02:54:44 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 506BD7F498; Fri, 19 Oct 2001 18:53:56 +0900 (JST)
Message-Id: <4.2.0.58.J.20011019180625.038105d0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 19 Oct 2001 18:09:35 +0900
To: "Soobok Lee" <lsb@postel.co.kr>,
        "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
In-Reply-To: <018901c1587a$dd021480$ec1bd9d2@temp>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <024b01c15847$11e8b430$0501000a@jamessonyvaio>
 <4.2.0.58.J.20011019152610.037f1100@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 17:48 01/10/19 +0900, Soobok Lee wrote:

>----- Original Message -----
>From: "Martin Duerst" <duerst@w3.org>
> > Also, in case of some implementation mistake in Nameprep/NFKC,
> > in most cases, it will just make a few names unusable, but
> > not affect the rest. For reordering, a bug will completely
> > confuse a whole script.
>
>Never.
>REoredering does not touch on unassigned code points at all.
>REORDERING is idempotent  for unassigned code points.

I didn't talk about unassigned code points.
What I mean is this: If you have two frequency tables,
and they differ by e.g. one forgetting a particular
character, then virtually all your compressed results
are different. If you have a wrong mapping in a
NFC or NFKC algorithm, then only that character is
affected.


>Optimal frequency table does not exist now and future and forever.
>sub-optimal solutions are often very useful and accepted and
>REORDERING is just one of them.

ACE-Z without reordering is also a sub-optimal solution.
I propose that we just use it.


Regards,   Martin.



From owner-idn@ops.ietf.org  Fri Oct 19 06:06:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13355
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 06:06:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uWMX-0009cC-00
	for idn-data@psg.com; Fri, 19 Oct 2001 02:54:45 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uWMW-0009c1-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 02:54:44 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 005237F4A8; Fri, 19 Oct 2001 18:53:56 +0900 (JST)
Message-Id: <4.2.0.58.J.20011019181226.0308f760@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 19 Oct 2001 18:15:30 +0900
To: "Soobok Lee" <lsb@postel.co.kr>,
        "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
In-Reply-To: <009601c1585d$e7612230$ec1bd9d2@temp>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <024b01c15847$11e8b430$0501000a@jamessonyvaio>
 <007601c15854$30c1f800$ec1bd9d2@temp>
 <046001c15855$02854f40$0501000a@jamessonyvaio>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 14:21 01/10/19 +0900, Soobok Lee wrote:

>----- Original Message -----
>From: "James Seng/Personal" <jseng@pobox.org.sg>
>To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
>Sent: Friday, October 19, 2001 1:17 PM
>Subject: Re: [idn] call for comments for REORDERING
>
>
> > You dont get my point.
> >
> > Reordering achieve shorter by putting more oftenly used characters in
> > one block and others at the back. BUT this also means less oftenly used
> > characters would result in a *LONGER* label then usual.
>
>No. Even For GROUPS of those rare cases, we get Always SHORTER labels than 
>usual.

Sorry, but this is nonsense. You cannot compress all labels
by reordering. It just doesn't work. The argument below is
about as foolproof as a perpetuum mobile design.

In reordering, you will always bring some codepoints closer
together (and names from these will then compress better)
at the expense of moving some farther appart (and thus
reducing compression).

You just have to think about a mixed label, with some
frequent and some not so frequent characters.

Regards,   Martin.



>For example,
>if REORDERING uses a frequent characters set of length 4096 in entire 
>20992-letter
>han ideographic script block, rarely used han letter will be put
>into the subblock of length 20992-4096 = 16896 which is 20% shorter than 
>20992.
>
>let's assume we have with a label consisting of only those characters from 
>16896 block. without reordering, they are randomly distributed in 20992 
>letter block.
>with reordering, they are in shorter 16896-letter block.
>In the latter case, we got shorter successive code distances and shorter
>ACE labels than in the former one.
>
>  Even without REORDERING, ACE has favored some of them, and disfavored
>others. But, with REORDERING, BOTH groups get shorter ACE labels.
>That is the virtue of REORDERING.
>
>Soobok
>
> > And who are we
> > to say these less oftenly used characters are less important or worst,
> > become invalid (too long to fit) because of this reordering?
> >
> > -James Seng
> >
>
>
>
>




From owner-idn@ops.ietf.org  Fri Oct 19 06:37:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13595
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 06:37:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uWnw-000AeB-00
	for idn-data@psg.com; Fri, 19 Oct 2001 03:23:04 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uWnv-000Ae2-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 03:23:03 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id TAA28153;
	Fri, 19 Oct 2001 19:22:51 +0900
Message-ID: <022001c15888$27fc5790$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <4.2.0.58.J.20011019152610.037f1100@localhost> <4.2.0.58.J.20011019180625.038105d0@localhost>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 19:23:54 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id GAA13595


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; "James Seng/Personal" <jseng@pobox.org.sg>; <idn@ops.ietf.org>
Sent: Friday, October 19, 2001 6:09 PM
Subject: Re: [idn] call for comments for REORDERING


> At 17:48 01/10/19 +0900, Soobok Lee wrote:
> 
> >----- Original Message -----
> >From: "Martin Duerst" <duerst@w3.org>
> > > Also, in case of some implementation mistake in Nameprep/NFKC,
> > > in most cases, it will just make a few names unusable, but
> > > not affect the rest. For reordering, a bug will completely
> > > confuse a whole script.
> >
> >Never.
> >REoredering does not touch on unassigned code points at all.
> >REORDERING is idempotent  for unassigned code points.
> 
> I didn't talk about unassigned code points.
> What I mean is this: If you have two frequency tables,
> and they differ by e.g. one forgetting a particular
> character, then virtually all your compressed results
> are different. If you have a wrong mapping in a
> NFC or NFKC algorithm, then only that character is
> affected.

Never. The REORDERING table for a script has *NO*
missing characters because it applies idempotent
mappings for even unassigned code points.

For one ACE prefix, one fixed reordering table!

If we should change the frequency table, new versioning
prefix should be introduced to avoid conflicts in the same
time when there is need to make major modifications to 
NFC/NFKC due to erros in them. 
If version 1 has "dq--" prefix, version 2 should have
other ones like "xq--". Reordering tables could be
improved at that time if needed.


SOobok Lee






From owner-idn@ops.ietf.org  Fri Oct 19 06:38:06 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13606
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 06:38:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uWtp-000Ash-00
	for idn-data@psg.com; Fri, 19 Oct 2001 03:29:09 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uWto-000AsV-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 03:29:09 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id TAA30054;
	Fri, 19 Oct 2001 19:28:57 +0900
Message-ID: <022601c15889$020aa360$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <4.2.0.58.J.20011019152610.037f1100@localhost> <4.2.0.58.J.20011019181604.0312ad90@localhost>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 19:30:00 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id GAA13606


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; "James Seng/Personal" <jseng@pobox.org.sg>; <idn@ops.ietf.org>
Sent: Friday, October 19, 2001 6:23 PM
Subject: Re: [idn] call for comments for REORDERING


> At 17:48 01/10/19 +0900, Soobok Lee wrote:
> 
> >----- Original Message -----
> >From: "Martin Duerst" <duerst@w3.org>
> >  >
> > > >Current IDNA/nameprep does not prohibit, but discourage including
> > > >unassigned code points in legal IDN labels, because new 
> > normalization/case
> > > >mappings
> > > >would be defined on them in the future. some ACE labels including 
> > unsigned
> > > >code block (tagalog?) might be proven invalid in the future. 
> > Nameprep/NFKC
> > > >Versioning tag schems using new ACE prefix will be needed in the 
> > future, i
> > > >guess.
> 
> Actually, because we do on purpose not prohibit unassigned codepoints
> on the client side, it is completely impossible to introduce reordering
> for any script that is added later.
> 
> The idea behind this is that if e.g. Tagalog gets added to
> Unicode, and the IETF decides to add it to the allowed set
> of characters for domain names, then the registries that
> want to accept Tagalog have to update their software
> immediately (no big deal for them), but deployed software
> can use Tagalog without having to change nameprep/ACE
> (unless they use characters which have to be normalized,
> which may happen but will be rare). So existing clients
> will already ACE the Tagalog codepoints without reordering,

maybe problematic and unsafe. 
What if future NFC/NFKC maps them into other code points ?
There will be a mess, too.

> and if we introduce reordering for Tagalog, there will
> be a mess.

Current REORDERING does nothing with TAGALOG and adds
no new problem into ACE. the problem is alerady inherent
in ACE and nameprep version scheme, and is not due to
REORDERING.

Prefix-based version scheme will solve those problems.

Soobok Lee






> 
> 
> Regards,   Martin.
> 




From owner-idn@ops.ietf.org  Fri Oct 19 07:15:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14180
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 07:15:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uXSf-000CFR-00
	for idn-data@psg.com; Fri, 19 Oct 2001 04:05:09 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uXSe-000CFL-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 04:05:08 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id UAA08851;
	Fri, 19 Oct 2001 20:04:56 +0900
Message-ID: <027801c1588e$09ac1f40$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <007601c15854$30c1f800$ec1bd9d2@temp> <046001c15855$02854f40$0501000a@jamessonyvaio> <4.2.0.58.J.20011019181226.0308f760@localhost>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 20:05:58 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA14180


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; "James Seng/Personal" <jseng@pobox.org.sg>; <idn@ops.ietf.org>
Sent: Friday, October 19, 2001 6:15 PM
Subject: Re: [idn] call for comments for REORDERING


> At 14:21 01/10/19 +0900, Soobok Lee wrote:
> 
> >----- Original Message -----
> >From: "James Seng/Personal" <jseng@pobox.org.sg>
> >To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
> >Sent: Friday, October 19, 2001 1:17 PM
> >Subject: Re: [idn] call for comments for REORDERING
> >
> >
> > > You dont get my point.
> > >
> > > Reordering achieve shorter by putting more oftenly used characters in
> > > one block and others at the back. BUT this also means less oftenly used
> > > characters would result in a *LONGER* label then usual.
> >
> >No. Even For GROUPS of those rare cases, we get Always SHORTER labels than 
> >usual.
> 
> Sorry, but this is nonsense. You cannot compress all labels
> by reordering. It just doesn't work. The argument below is
> about as foolproof as a perpetuum mobile design.

Never non-sense. You have misunderstandings.

See the word "GROUPS" in the above statement. 
I didn't assert them on  "every individual labels".

> 
> In reordering, you will always bring some codepoints closer
> together (and names from these will then compress better)
> at the expense of moving some farther appart (and thus
> reducing compression).

That's true for rare individual cases, but not in overall results, because
The expense in latter part is much less than the gain in former part.
The net gain is always positive for even rare groups of characters.


> 
> You just have to think about a mixed label, with some
> frequent and some not so frequent characters.

Sure. REORDERING also works for these kinds of lables.

Frequent charc: f1 f2 f3 f4 ...
Rare  chars   : r1 r2 r3 r4
We have a mixed reordered label:  f1 r1 f2 r2 f3 r4 . com
AMC-Z sort it into :  f1 f2 f3 f4 r1 r2 r3 r4 . com
AMC-Z encode them  :  label <f1 f2 f3 f4>  + junction overhead <f4 r1>+ label <r1 r2 r3 r4>

You know reordering works well for label <f1 f2 f3 f4 > and label <r1 r2 r3 r4>.

Soobok lee


> 
> Regards,   Martin.
> 
> 
> 
> >For example,
> >if REORDERING uses a frequent characters set of length 4096 in entire 
> >20992-letter
> >han ideographic script block, rarely used han letter will be put
> >into the subblock of length 20992-4096 = 16896 which is 20% shorter than 
> >20992.
> >
> >let's assume we have with a label consisting of only those characters from 
> >16896 block. without reordering, they are randomly distributed in 20992 
> >letter block.
> >with reordering, they are in shorter 16896-letter block.
> >In the latter case, we got shorter successive code distances and shorter
> >ACE labels than in the former one.
> >
> >  Even without REORDERING, ACE has favored some of them, and disfavored
> >others. But, with REORDERING, BOTH groups get shorter ACE labels.
> >That is the virtue of REORDERING.
> >
> >Soobok
> >
> > > And who are we
> > > to say these less oftenly used characters are less important or worst,
> > > become invalid (too long to fit) because of this reordering?
> > >
> > > -James Seng
> > >
> >
> >
> >
> >
> 




From owner-idn@ops.ietf.org  Fri Oct 19 07:24:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14359
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 07:24:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uXbr-000Cah-00
	for idn-data@psg.com; Fri, 19 Oct 2001 04:14:39 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uXbq-000CaW-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 04:14:38 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id UAA11831
	for <idn@ops.ietf.org>; Fri, 19 Oct 2001 20:14:27 +0900
Message-ID: <029f01c1588f$5d4e1350$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Subject: [idn] (in utf8) some CJK examples on REORDERING+ACE-Z
Date: Fri, 19 Oct 2001 20:15:29 +0900
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_029B_01C158DA.CC7CCB90"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_029B_01C158DA.CC7CCB90
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit

These examples show how compact the ACE label could be with REORDERING.

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

(here    LAMCZ  means    REORDERING + AMC-ACE-Z ).

INPUT -> 中國東方航空公司
U+4E2D U+570B U+6771 U+65B9 U+822A U+7A7A U+516C U+53F8

AMCZ     : fiQy2F5vC5vE46YolCwy4C23M
           25
LAMCZ    : nkT8IiFwQiB8ExDP     (see  last P )
           16



INPUT -> 中國南方航空公司
U+4E2D U+570B U+5357 U+65B9 U+822A U+7A7A U+516C U+53F8

AMCZ     : fiQy2FczBpS26Jj22Avg7A23M
           25
LAMCZ    : nkT8IiF7OrB6B4LpA
           17


INPUT -> 中國民用航空總局
U+4E2D U+570B U+6C11 U+7528 U+822A U+7A7A U+7E3D U+5C40

AMCZ     : fiQz9SjoEz4SpwKrxHvyGxvI
           24
LAMCZ    : p8S8UuNlEuO2F06BpA
           18

INPUT -> 富士銀行
U+5BCC U+58EB U+9280 U+884C

AMCZ     : zqSv0Er63DrsI
           13
LAMCZ    : vmT0D0FrL
           9


INPUT -> 東京大學
U+6771 U+4EAC U+5927 U+5B78

AMCZ     : 1lQ68W3xBh4U
           12
LAMCZ    : nrT3CHX
           7

------=_NextPart_000_029B_01C158DA.CC7CCB90
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

=EF=BB=BF<!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 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><STRONG><FONT face=3D=EA=B5=B4=EB=A6=BC size=3D2>These examples =
show how compact the ACE label=20
could be with REORDERING.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=EA=B5=B4=EB=A6=BC =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=EA=B5=B4=EB=A6=BC size=3D2>Soobok =
Lee</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=EA=B5=B4=EB=A6=BC=20
size=3D2>----------------------------------------------------------------=
-----------</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=EA=B5=B4=EB=A6=BC =
size=3D2>&nbsp;</FONT></STRONG></DIV>
<DIV>
<DIV><STRONG><FONT face=3D=EA=B5=B4=EB=A6=BC =
size=3D2>(here&nbsp;&nbsp;&nbsp; LAMCZ&nbsp;=20
means&nbsp;&nbsp; &nbsp;REORDERING + AMC-ACE-Z ).</FONT></STRONG></DIV>
<DIV><STRONG></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D"Courier New" size=3D4>INPUT -&gt; =
=E4=B8=AD=E5=9C=8B=E6=9D=B1=E6=96=B9=E8=88=AA=E7=A9=BA=E5=85=AC=E5=8F=B8<=
BR>U+4E2D=20
U+570B U+6771 U+65B9 U+822A U+7A7A U+516C=20
U+53F8<BR><BR>AMCZ&nbsp;&nbsp;&nbsp;&nbsp; :=20
fiQy2F5vC5vE46YolCwy4C23M<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=20
25<BR>LAMCZ&nbsp;&nbsp;&nbsp; : nkT8IiFwQiB8ExDP&nbsp;&nbsp;&nbsp;&nbsp; =

(see&nbsp; last P=20
)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
16</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D"Courier New" =
size=3D4></FONT></STRONG>&nbsp;</DIV>
<DIV><BR><STRONG><FONT face=3D"Courier New" size=3D4>&nbsp;<BR>INPUT =
-&gt;=20
=E4=B8=AD=E5=9C=8B=E5=8D=97=E6=96=B9=E8=88=AA=E7=A9=BA=E5=85=AC=E5=8F=B8<=
BR>U+4E2D U+570B U+5357 U+65B9 U+822A U+7A7A U+516C=20
U+53F8<BR><BR>AMCZ&nbsp;&nbsp;&nbsp;&nbsp; :=20
fiQy2FczBpS26Jj22Avg7A23M<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=20
25<BR>LAMCZ&nbsp;&nbsp;&nbsp; :=20
nkT8IiF7OrB6B4LpA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
17<BR><BR><BR>INPUT -&gt; =
=E4=B8=AD=E5=9C=8B=E6=B0=91=E7=94=A8=E8=88=AA=E7=A9=BA=E7=B8=BD=E5=B1=80<=
BR>U+4E2D U+570B U+6C11 U+7528 U+822A U+7A7A=20
U+7E3D U+5C40<BR><BR>AMCZ&nbsp;&nbsp;&nbsp;&nbsp; :=20
fiQz9SjoEz4SpwKrxHvyGxvI<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
24<BR>LAMCZ&nbsp;&nbsp;&nbsp; :=20
p8S8UuNlEuO2F06BpA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<=
BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
18<BR><BR>INPUT -&gt; =E5=AF=8C=E5=A3=AB=E9=8A=80=E8=A1=8C<BR>U+5BCC =
U+58EB U+9280=20
U+884C<BR><BR>AMCZ&nbsp;&nbsp;&nbsp;&nbsp;=20
:&nbsp;zqSv0Er63DrsI<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
13<BR>LAMCZ&nbsp;&nbsp;&nbsp; :=20
vmT0D0FrL<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
9<BR><BR><BR>INPUT -&gt; =E6=9D=B1=E4=BA=AC=E5=A4=A7=E5=AD=B8<BR>U+6771 =
U+4EAC U+5927=20
U+5B78<BR><BR>AMCZ&nbsp;&nbsp;&nbsp;&nbsp; :=20
1lQ68W3xBh4U<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
12<BR>LAMCZ&nbsp;&nbsp;&nbsp; : nrT3CHX&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
7</FONT></STRONG></DIV></DIV></BODY></HTML>

------=_NextPart_000_029B_01C158DA.CC7CCB90--




From owner-idn@ops.ietf.org  Fri Oct 19 08:44:21 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16833
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 08:44:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uYkC-000FPf-00
	for idn-data@psg.com; Fri, 19 Oct 2001 05:27:20 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uYkB-000FPW-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 05:27:19 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id VAA01764;
	Fri, 19 Oct 2001 21:26:56 +0900
Message-ID: <02c901c15899$809f7920$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <DougEwell2@cs.com>, <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
Cc: <jseng@pobox.org.sg>
References: <4.2.0.58.J.20011019155811.03d67490@localhost>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 21:27:57 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id IAA16833


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: <DougEwell2@cs.com>; <idn@ops.ietf.org>
Cc: <lsb@postel.co.kr>; <jseng@pobox.org.sg>
Sent: Friday, October 19, 2001 4:05 PM
Subject: Re: [idn] call for comments for REORDERING


> At 02:05 01/10/19 -0400, DougEwell2@cs.com wrote:
> >In a message dated 2001-10-18 21:33:55 Pacific Daylight Time,
> >lsb@postel.co.kr writes:
> >
> > >  1) saturations in TLD namespaces would require longer names for which
> > >      REORDERING is designed to give greater benefits/compression ratio.
> >
> >Is it not the case that logographic/ideographic writing systems such as Han
> >and the syllable-oriented Unicode encoding of Hangul, with their large
> >numbers of characters, convey more information per character than alphabetic
> >scripts?
> 
> Very much so, of course.

han/hangeul have huge lists of characters (20992/11172). 
To encode them, we need more digits and bits than latin letters. 
That ACE encoding overhead is so big that it cannot be compensated by the superiority in the information capacity of a han letter compared to a latin letter. The sizes of Latin alphabets or variants do not exceed 30.

In UCS-2, 2*N octets are need for latin/han lables of length N.
But ACE/UTF8 which favor latin script, require roughly 3.0*N octets for long han labels. REORDERING reduce those requirement into 2.2*N, close to that of UCS-2.

Soobok Lee




From owner-idn@ops.ietf.org  Fri Oct 19 09:25:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18306
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 09:25:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uZKW-000Gr9-00
	for idn-data@psg.com; Fri, 19 Oct 2001 06:04:52 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uZKV-000Gr0-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 06:04:51 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id WAA13404;
	Fri, 19 Oct 2001 22:04:34 +0900
Message-ID: <02e901c1589e$c1377a00$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <4.2.0.58.J.20011019160708.037cccd0@localhost> <4.2.0.58.J.20011019174908.03d8c360@localhost>
Subject: Re: [idn] call for comments for REORDERING
Date: Fri, 19 Oct 2001 22:05:36 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA18306


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; "James Seng/Personal" <jseng@pobox.org.sg>; <idn@ops.ietf.org>
Sent: Friday, October 19, 2001 5:58 PM
Subject: Re: [idn] call for comments for REORDERING


> At 17:39 01/10/19 +0900, Soobok Lee wrote:
> 
> >----- Original Message -----
> >From: "Martin Duerst" <duerst@w3.org>
> > > >
> > > >1) saturations in TLD namespaces would require longer names for which
> > > >     REORDERING is designed to give greater benefits/compression ratio.
> > >
> > > No. What James referred to is that saturation tends to fill up the
> > > short name slots, and thus flatten the probability distribution.
> > > I.e. if somebody doesn't get the name they wanted, the chance is
> > > that they go for something like xq.com, because it's easy to
> > > remember because it's short. Neither x nor q are very frequent
> > > letters.
> >
> >Han/hangeul characters carries meanings while latin alphabets
> >denote phonemes. Therefore your analogy between latin and han domains
> >may be false. Chinese people would rather choose to register
> >digit-added variants of  alreagy taken desired domains in saturated ML.com,
> >instead of choosing non-sense irrelevant rare han characters.
> 
> Some really rare and irrelevant han characters may indeed never
> be chosen. But still if you want to name a company, there are
> many different possibilities, and people will look for short,
> not yet used possibilities (which still make some sense)
> rather than use longer and longer names.
> 
In most cases, they add latin digits. CJK people would know what i am saying.


> 
> >Later time, I will provide some proofs that SC and TC only have
> >small partial set of frequent characters. That's already clear in
> >SJIS and KSC5601 han characters set which size is less than 5000.
> 
> Yes, this is true.
> 
> 
> > > >to avoid countriy-specific biases in han reordering table.
> > > >
> > > >non-CJK scripts often haver small set of basic alphabets, and their
> > > >character usage patterns are more stable than those for han/hangeul.
> > >
> > > No, many other scripts are used for many more languages, with
> > > quite different usage patterns. (A lot of Han usage in Japan,
> > > and most of it in Korea, is due to loanwords from Chinese.)
> > >
> >
> >But, even without Urdu consideration in
> >arabic reordering, the efficiency of reordering is always  better than
> >without it, because the lexicographic ordering in un-reordered
> >arabic script block can be regarded as *RANDOM* ordering
> >in frequency measure (maximum entropy).
> 
> It's probably not, because most alphabets contain a few
> 'late additions'.
 
If and only if the reordering table for a script needs
modifications for added characters, it can be done in the
next version of nameprep/ACE with new ACE prefix.


> And just using first order frequency
> to bring the most frequent characters to the front may
> not be the most efficient way for compression.
> 

Do you a good idea that can replace current first-order frequency reordering ?
Welcome any changes to that.

If someone devise new ordering scheme in the future, that may substitute 
current reordering scheme in the next namepre/ACE version with
new ACE prefix.


> 
> >Partial reordering (without Urdu consideration) is always better than
> >no reordering.
> 
> I don't deny that you may be able to squeeze out a few bits.
> But I don't think that should be the aim of this exercise.
> 
> >If Urdu text samples  are available, my arabic reordering table may be
> >improved to reflect them, though.
> 
> Which might then make it less efficient for Arabic.

Yes, but marginally.

> 
> 
> Regards,   Martin.
> 




From owner-idn@ops.ietf.org  Fri Oct 19 12:18:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22569
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 12:18:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ucDL-000OKZ-00
	for idn-data@psg.com; Fri, 19 Oct 2001 09:09:39 -0700
Received: from imo-r08.mx.aol.com ([152.163.225.104])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ucDK-000OKN-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 09:09:38 -0700
Received: from DougEwell2@cs.com
	by imo-r08.mx.aol.com (mail_out_v31_r1.8.) id i.ca.5b8bcd (4398);
	Fri, 19 Oct 2001 12:09:33 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <ca.5b8bcd.2901aa3d@cs.com>
Date: Fri, 19 Oct 2001 12:09:33 EDT
Subject: Re: [idn] call for comments for REORDERING
To: idn@ops.ietf.org
CC: lsb@postel.co.kr, duerst@w3.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In various messages, lsb@postel.co.kr writes:

> The sizes of Latin alphabets or variants do not exceed 30.

Russian Cyrillic has 33.  Many Central European implementations of the Latin 
script, with carons and acute accents and such, use quite a bit more than 30. 
 But this is nit-picking, and Soobok's point about the difference between 
Latin and Hangul is well taken.

>  If we should change the frequency table, new versioning
>  prefix should be introduced to avoid conflicts in the same
>  time when there is need to make major modifications to 
>  NFC/NFKC due to erros in them. 
>  If version 1 has "dq--" prefix, version 2 should have
>  other ones like "xq--". Reordering tables could be
>  improved at that time if needed.

I think Martin has already adequately explained the problematic nature of 
creating different versions of the whole IDN scheme.  Users, of course, will 
not generally understand that there is a nameprep part and a reordering* part 
and an ACE part and that only the reordering part has changed; they will 
simply see that IDN "works" or "doesn't work," and of course they will be 
right.  (*Note: the ordinary English word "reordering" is spelled here in 
normal lowercase letters.)

Requiring everyone to update browsers and server-side software to accommodate 
IDN will be an understandable costs for many.  Creating a new and 
incompatible version of IDN to add reordering for Tagalog -- a really minor 
optimization for a small alphabet, by Soobok's own admission -- will not.

>  > The idea behind this is that if e.g. Tagalog gets added to
>  > Unicode, and the IETF decides to add it to the allowed set
>  > of characters for domain names, then the registries that
>  > want to accept Tagalog have to update their software
>  > immediately (no big deal for them), but deployed software
>  > can use Tagalog without having to change nameprep/ACE
>  > (unless they use characters which have to be normalized,
>  > which may happen but will be rare). So existing clients
>  > will already ACE the Tagalog codepoints without reordering,
>
>  maybe problematic and unsafe. 
>  What if future NFC/NFKC maps them into other code points ?
>  There will be a mess, too.

You don't have to worry about that because the ISO 10646 and Unicode 
committees are firmly committed not to add any new compatibility characters 
that would break normalization in this way.  They can (and will) add Tagalog 
and other scripts, as well as adding new characters for existing scripts, but 
you will never see a precomposed Tagalog ligature that would cause NFC or 
NFKC to have to be updated.  To do so would break existing implementations 
and cause the same kind of havoc that "Reordering v2.0" would cause.

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Fri Oct 19 13:51:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25899
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 13:51:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15udUj-0001zI-00
	for idn-data@psg.com; Fri, 19 Oct 2001 10:31:41 -0700
Received: from smtp15.singnet.com.sg ([165.21.6.35])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15udUh-0001yy-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 10:31:39 -0700
Received: from jamessonyvaio ([165.21.104.137])
	by smtp15.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9JHTPh23059;
	Sat, 20 Oct 2001 01:29:25 +0800
Message-ID: <007e01c158c3$e2f41ac0$0601000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <4.2.0.58.J.20011019152610.037f1100@localhost> <4.2.0.58.J.20011019181604.0312ad90@localhost> <022601c15889$020aa360$ec1bd9d2@temp>
Subject: Re: [idn] call for comments for REORDERING
Date: Sat, 20 Oct 2001 01:31:29 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> maybe problematic and unsafe.
> What if future NFC/NFKC maps them into other code points ?
> There will be a mess, too.

read the design principle of NFC or NFKC. Future addition of scripts and
addition normalization will *NOT* cause existing normalized string to
changed.

do you have the same stability principle or ensure that to be the same
for re-ordering? or one which can be sure?

> Current REORDERING does nothing with TAGALOG and adds
> no new problem into ACE. the problem is alerady inherent
> in ACE and nameprep version scheme, and is not due to
> REORDERING.

But Tagalog may then come back to IDN to claim unfair treatment!
Are you going to deny them that?

> Prefix-based version scheme will solve those problems.

No no no. Lets not get into other scheme which involves playing with
multiples prefix or suffix as "version tag". Try not to make things more
complex here.

The key word here is stability. You have not address it yet.

And no, there is no such thing as "only compress" algorithm. It is
mathemtically impossible.

-James Seng




From owner-idn@ops.ietf.org  Fri Oct 19 13:51:35 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25898
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 13:51:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15udXa-00024L-00
	for idn-data@psg.com; Fri, 19 Oct 2001 10:34:38 -0700
Received: from smtp14.singnet.com.sg ([165.21.6.34])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15udXZ-00024D-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 10:34:37 -0700
Received: from jamessonyvaio ([165.21.104.137])
	by smtp14.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9JHWxJ32763;
	Sat, 20 Oct 2001 01:32:59 +0800
Message-ID: <008801c158c4$4f36cbb0$0601000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
References: <029f01c1588f$5d4e1350$ec1bd9d2@temp>
Subject: Re: [idn] (in utf8) some CJK examples on REORDERING+ACE-Z
Date: Sat, 20 Oct 2001 01:34:30 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0085_01C15907.5D33E610"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0085_01C15907.5D33E610
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

We know the efficient. We seen the result and I accepted it.

Now, lets talk about stability and referencing code from reputable =
source.

-James Seng
  ----- Original Message -----=20
  From: Soobok Lee=20
  To: idn@ops.ietf.org=20
  Sent: Friday, October 19, 2001 7:15 PM
  Subject: [idn] (in utf8) some CJK examples on REORDERING+ACE-Z


  These examples show how compact the ACE label could be with =
REORDERING.

  Soobok Lee
  =
-------------------------------------------------------------------------=
--

  (here    LAMCZ  means    REORDERING + AMC-ACE-Z ).

  INPUT -> =
=E4=B8=AD=E5=9C=8B=E6=9D=B1=E6=96=B9=E8=88=AA=E7=A9=BA=E5=85=AC=E5=8F=B8
  U+4E2D U+570B U+6771 U+65B9 U+822A U+7A7A U+516C U+53F8

  AMCZ     : fiQy2F5vC5vE46YolCwy4C23M
             25
  LAMCZ    : nkT8IiFwQiB8ExDP     (see  last P )
             16


  =20
  INPUT -> =
=E4=B8=AD=E5=9C=8B=E5=8D=97=E6=96=B9=E8=88=AA=E7=A9=BA=E5=85=AC=E5=8F=B8
  U+4E2D U+570B U+5357 U+65B9 U+822A U+7A7A U+516C U+53F8

  AMCZ     : fiQy2FczBpS26Jj22Avg7A23M
             25
  LAMCZ    : nkT8IiF7OrB6B4LpA     =20
             17


  INPUT -> =
=E4=B8=AD=E5=9C=8B=E6=B0=91=E7=94=A8=E8=88=AA=E7=A9=BA=E7=B8=BD=E5=B1=80
  U+4E2D U+570B U+6C11 U+7528 U+822A U+7A7A U+7E3D U+5C40

  AMCZ     : fiQz9SjoEz4SpwKrxHvyGxvI
             24
  LAMCZ    : p8S8UuNlEuO2F06BpA        =20
             18

  INPUT -> =E5=AF=8C=E5=A3=AB=E9=8A=80=E8=A1=8C
  U+5BCC U+58EB U+9280 U+884C

  AMCZ     : zqSv0Er63DrsI
             13
  LAMCZ    : vmT0D0FrL
             9


  INPUT -> =E6=9D=B1=E4=BA=AC=E5=A4=A7=E5=AD=B8
  U+6771 U+4EAC U+5927 U+5B78

  AMCZ     : 1lQ68W3xBh4U
             12
  LAMCZ    : nrT3CHX    =20
             7

------=_NextPart_000_0085_01C15907.5D33E610
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.4807.2300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3D"Courier New" size=3D2>We know the efficient. We seen =
the result=20
and I accepted it.</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Now, lets talk about stability =
and=20
referencing code from reputable source.</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2>-James Seng</FONT></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=3Dlsb@postel.co.kr href=3D"mailto:lsb@postel.co.kr">Soobok =
Lee</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, October 19, 2001 =
7:15=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [idn] (in utf8) some =
CJK=20
  examples on REORDERING+ACE-Z</DIV>
  <DIV><BR></DIV>
  <DIV><STRONG><FONT face=3D=EA=B5=B4=EB=A6=BC size=3D2>These examples =
show how compact the ACE=20
  label could be with REORDERING.</FONT></STRONG></DIV>
  <DIV><STRONG><FONT face=3D=EA=B5=B4=EB=A6=BC =
size=3D2></FONT></STRONG>&nbsp;</DIV>
  <DIV><STRONG><FONT face=3D=EA=B5=B4=EB=A6=BC size=3D2>Soobok =
Lee</FONT></STRONG></DIV>
  <DIV><STRONG><FONT face=3D=EA=B5=B4=EB=A6=BC=20
  =
size=3D2>----------------------------------------------------------------=
-----------</FONT></STRONG></DIV>
  <DIV><STRONG><FONT face=3D=EA=B5=B4=EB=A6=BC =
size=3D2></FONT></STRONG>&nbsp;</DIV>
  <DIV>
  <DIV><STRONG><FONT face=3D=EA=B5=B4=EB=A6=BC =
size=3D2>(here&nbsp;&nbsp;&nbsp; LAMCZ&nbsp;=20
  means&nbsp;&nbsp; &nbsp;REORDERING + AMC-ACE-Z =
).</FONT></STRONG></DIV>
  <DIV><STRONG></STRONG>&nbsp;</DIV>
  <DIV><STRONG><FONT face=3D"Courier New" size=3D4>INPUT -&gt; =
=E4=B8=AD=E5=9C=8B=E6=9D=B1=E6=96=B9=E8=88=AA=E7=A9=BA=E5=85=AC=E5=8F=B8<=
BR>U+4E2D=20
  U+570B U+6771 U+65B9 U+822A U+7A7A U+516C=20
  U+53F8<BR><BR>AMCZ&nbsp;&nbsp;&nbsp;&nbsp; :=20
  =
fiQy2F5vC5vE46YolCwy4C23M<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=20
  25<BR>LAMCZ&nbsp;&nbsp;&nbsp; : =
nkT8IiFwQiB8ExDP&nbsp;&nbsp;&nbsp;&nbsp;=20
  (see&nbsp; last P=20
  )<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  16</FONT></STRONG></DIV>
  <DIV><STRONG><FONT face=3D"Courier New" =
size=3D4></FONT></STRONG>&nbsp;</DIV>
  <DIV><BR><STRONG><FONT face=3D"Courier New" size=3D4>&nbsp;<BR>INPUT =
-&gt;=20
  =
=E4=B8=AD=E5=9C=8B=E5=8D=97=E6=96=B9=E8=88=AA=E7=A9=BA=E5=85=AC=E5=8F=B8<=
BR>U+4E2D U+570B U+5357 U+65B9 U+822A U+7A7A U+516C=20
  U+53F8<BR><BR>AMCZ&nbsp;&nbsp;&nbsp;&nbsp; :=20
  =
fiQy2FczBpS26Jj22Avg7A23M<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=20
  25<BR>LAMCZ&nbsp;&nbsp;&nbsp; :=20
  =
nkT8IiF7OrB6B4LpA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  17<BR><BR><BR>INPUT -&gt; =
=E4=B8=AD=E5=9C=8B=E6=B0=91=E7=94=A8=E8=88=AA=E7=A9=BA=E7=B8=BD=E5=B1=80<=
BR>U+4E2D U+570B U+6C11 U+7528 U+822A=20
  U+7A7A U+7E3D U+5C40<BR><BR>AMCZ&nbsp;&nbsp;&nbsp;&nbsp; :=20
  =
fiQz9SjoEz4SpwKrxHvyGxvI<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
  24<BR>LAMCZ&nbsp;&nbsp;&nbsp; :=20
  =
p8S8UuNlEuO2F06BpA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<=
BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  18<BR><BR>INPUT -&gt; =E5=AF=8C=E5=A3=AB=E9=8A=80=E8=A1=8C<BR>U+5BCC =
U+58EB U+9280=20
  U+884C<BR><BR>AMCZ&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
:&nbsp;zqSv0Er63DrsI<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
  13<BR>LAMCZ&nbsp;&nbsp;&nbsp; :=20
  =
vmT0D0FrL<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
  9<BR><BR><BR>INPUT -&gt; =
=E6=9D=B1=E4=BA=AC=E5=A4=A7=E5=AD=B8<BR>U+6771 U+4EAC U+5927=20
  U+5B78<BR><BR>AMCZ&nbsp;&nbsp;&nbsp;&nbsp; :=20
  =
1lQ68W3xBh4U<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
  12<BR>LAMCZ&nbsp;&nbsp;&nbsp; : nrT3CHX&nbsp;&nbsp;&nbsp;&nbsp;=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  7</FONT></STRONG></DIV></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0085_01C15907.5D33E610--




From owner-idn@ops.ietf.org  Fri Oct 19 14:43:04 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27646
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 14:43:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ueTp-0004jx-00
	for idn-data@psg.com; Fri, 19 Oct 2001 11:34:49 -0700
Received: from smtp14.singnet.com.sg ([165.21.6.34])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ueTn-0004jk-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 11:34:47 -0700
Received: from jamessonyvaio ([165.21.104.137])
	by smtp14.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9JIXGJ18713;
	Sat, 20 Oct 2001 02:33:16 +0800
Message-ID: <01f201c158cc$baa32030$0601000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <4.2.0.58.J.20011018183339.031fa100@localhost> <01d501c15880$9a966410$ec1bd9d2@temp>
Subject: Re: [idn] call for comments for REORDERING
Date: Sat, 20 Oct 2001 02:34:46 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> CJK peolple have problems without REORDERING.

I like to see some quantify prove for this.

as a chinese i am quite happy without reordering. (in fact, i am already
happy with utf5 15 label limtation but thats another story). nor have i
heard verisign (or other registries) registration stop due to lack of
reordering for CJK.

> Other european folks but You martin (han experts),
> won't install han/hangeul fonts even in his/her PCs, i guess.
> Most europeans will see leaked ACE labels sometime in the future
> when IDN host/email addresses are everywhere and interchanged globally
> like LDH ones.  surely,

> IDNA WITHOUT REORDERING also become pains for non-CJK folks.

so u mean a "zq--dskjssdljdssdds32" is better than
"zq--jdzpzxcklxx9jspsddsdsd" to naked eye? I cant believe this
statement.

-James Seng




From owner-idn@ops.ietf.org  Fri Oct 19 18:04:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02755
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 18:04:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uhZH-000DfO-00
	for idn-data@psg.com; Fri, 19 Oct 2001 14:52:39 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uhZH-000DfI-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 14:52:39 -0700
Received: from [165.227.249.20] (165-227-249-20.client.dsl.net [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f9JLqVD11663
	for <idn@ops.ietf.org>; Fri, 19 Oct 2001 14:52:35 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100316b7f64e9d5b98@[165.227.249.20]>
In-Reply-To: <02e901c1589e$c1377a00$ec1bd9d2@temp>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <024b01c15847$11e8b430$0501000a@jamessonyvaio>
 <4.2.0.58.J.20011019160708.037cccd0@localhost>
 <4.2.0.58.J.20011019174908.03d8c360@localhost>
 <02e901c1589e$c1377a00$ec1bd9d2@temp>
Date: Fri, 19 Oct 2001 14:51:30 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] call for comments for REORDERING
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Apologies for taking so long to comment on this thread. However, 
given the comments from the last 48 hours, it is clear that comments 
from more people are needed.

The reordering proposal and its proponent are based on the faulty 
premise that there will be a need for very long domain names for the 
scripts that have been reordered. The fact that there are very long 
names in the Asian languages is irrelevant because there is no 
assumption that anyone would use those long names in domain names. 
The author seems to think that domain names have the same properties 
and regular names, which is of course wrong.

It is very troubling that the proposal's author pretty much ignores 
requests for clarifications with statements like "if you were a CJK 
person, you would know this". He has said that to people who are, in 
fact, well-known CJK experts. This is not the way that good standards 
are created.

So far, there has been no significant support for the proposal, and a 
lot of people objecting. I am in the latter category for the simple 
reason that the proposal adds complexity and overhead to fix a 
non-existent problem.

The WG should ignore this proposal unless the author can respond to 
questions and concerns from the rest of the WG.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Fri Oct 19 19:33:21 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05543
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 19:33:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uizb-000I1H-00
	for idn-data@psg.com; Fri, 19 Oct 2001 16:23:55 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uiza-000I16-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 16:23:54 -0700
Received: from amc by nicemice.net with local (Exim 3.32 #1 (Debian))
	id 15uizY-0006eL-00
	for <idn@ops.ietf.org>; Fri, 19 Oct 2001 16:23:52 -0700
Date: Fri, 19 Oct 2001 23:23:52 +0000
From: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>
To: idn@ops.ietf.org
Subject: Re: [idn] call for comments for REORDERING
Message-ID: <20011019232352.G24104@nicemice.net>
Reply-To: IETF idn working group <idn@ops.ietf.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <007601c15854$30c1f800$ec1bd9d2@temp> <046001c15855$02854f40$0501000a@jamessonyvaio> <009601c1585d$e7612230$ec1bd9d2@temp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <009601c1585d$e7612230$ec1bd9d2@temp>
User-Agent: Mutt/1.3.22i
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Soobok Lee <lsb@postel.co.kr> wrote:

> Even For GROUPS of those rare cases, we get Always SHORTER labels than
> usual.

As has already been pointed out, this is impossible.  Here is one class
of labels that are made longer by reordering:  Labels that use lots of
"uncommon" code points from the bottom 2K (or whatever) of the block.
Without reordering, these code points are already close together, but
with reordering they will be scattered all over the block, resulting in
a longer ACE.  Of course such labels are supposed to be very rare.

All compression schemes must make some inputs shorter and some longer.
The goal is to makes the more common ones a lot shorter, and the very
rare ones only slightly longer.

> That ACE encoding overhead is so big that it cannot be compensated by
> the superiority in the information capacity of a han letter compared
> to a latin letter.

That's not obvious.  Here are the AMC-ACE-Z encodings of the same
sentence in English and Chinese (from the Examples section of the
AMC-ACE-Z spec):

              English: WhyCantTheyJustSpeakChinese
 Chinese (simplified): ihqwcrb4cv8a8dqg056pqjye
Chinese (traditional): ihqwctvzc91f659drss3x8bo0yb

Of course this is only one data point, but my hunch is that it's not
atypical.

Paul Hoffman / IMC <phoffman@imc.org> wrote:

> The reordering proposal and its proponent are based on the faulty
> premise that there will be a need for very long domain names for the
> scripts that have been reordered.

Actually, he has said many times that his goal is not only to allow long
domain names, but also to make average domain names easier for humans to
cope with when they are forced to see the ACE.  (And others have argued
that neither goal is important enough to justify the complexity.  I'd
like to know if the CJK NICs have opinions on the matter.)

AMC



From owner-idn@ops.ietf.org  Fri Oct 19 21:51:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11941
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 21:51:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ul7S-000OEl-00
	for idn-data@psg.com; Fri, 19 Oct 2001 18:40:10 -0700
Received: from [203.207.0.132] (helo=mail.asiainfra.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ul7R-000OEW-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 18:40:09 -0700
Received: from gix ([159.226.1.126])
	by mail.asiainfra.com (8.9.3/8.9.3) with SMTP id JAA30366;
	Sat, 20 Oct 2001 09:40:08 +0800
From: "Kenny Huang" <huangk@alum.sinica.edu>
To: "James Seng/Personal" <jseng@pobox.org.sg>,
        "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
Subject: RE: [idn] call for comments for REORDERING
Date: Sat, 20 Oct 2001 09:44:52 +0800
Message-ID: <IHELIFNJKJLDFEMBCENDEEBBCIAA.huangk@alum.sinica.edu>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <01f201c158cc$baa32030$0601000a@jamessonyvaio>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA11941

as a chinese i am quite happy with 8-bit clean DNS, nor have i heard TWNIC or
CNNIC registration stop due to BIG5/GB stored in the resource records. Besides,
both NIC provide resolution service, one step ahead Verisign service. 
If the discussion is based on this kind of scenario, that will be an endless loop.

> I like to see some quantify prove for this.
> 
> as a chinese i am quite happy without reordering. (in fact, i am already
> happy with utf5 15 label limtation but thats another story). nor have i
> heard verisign (or other registries) registration stop due to lack of
> reordering for CJK.
> 
> > Other european folks but You martin (han experts),
> > won't install han/hangeul fonts even in his/her PCs, i guess.
> > Most europeans will see leaked ACE labels sometime in the future
> > when IDN host/email addresses are everywhere and interchanged globally
> > like LDH ones.  surely,
> 
> > IDNA WITHOUT REORDERING also become pains for non-CJK folks.
> 
> so u mean a "zq--dskjssdljdssdds32" is better than
> "zq--jdzpzxcklxx9jspsddsdsd" to naked eye? I cant believe this
> statement.

These encoding are transparent to USER (NAKED EYE). Of course you should know it.

Kenny Huang




From owner-idn@ops.ietf.org  Fri Oct 19 21:52:27 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11973
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 21:52:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ulBe-000OO7-00
	for idn-data@psg.com; Fri, 19 Oct 2001 18:44:30 -0700
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ulBe-000OO1-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 18:44:30 -0700
Received: from zetnet.co.uk (man-s060.dialup.zetnet.co.uk [194.247.41.187])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f9K1iMl31870;
	Sat, 20 Oct 2001 02:44:22 +0100
Message-ID: <3BD0D3BD.9DEC4E5B@zetnet.co.uk>
Date: Sat, 20 Oct 2001 02:30:37 +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] call for comments for REORDERING
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <4.2.0.58.J.20011018183339.031fa100@localhost> <01cd01c1587f$71947490$ec1bd9d2@temp>
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-----

Soobok Lee wrote:
> "Martin Duerst" <duerst@w3.org> wrote:
> > Soobok Lee wrote:
> > >Current Windows 98,2K,XP and Linux  contain NFKC codes ?
> >
> > No. My personal preference would be for NFC, anyway, because
> > most of the additional mappings in NFKC are not really useful,
> > because they are from characters that are quite difficult
> > to type in. So these characters could just be forbidden rather
> > than mapped. The only exception I know is full-width ASCII,
> > which could either be included in the nameprep mapping step,
> > or could be done as a front-end 'quality of implementation'
> > step (similar to how the ideographic fullstop is currently
> > treated).
> 
> My personal preference is NFKC. Because it solves the mappings between
> the extended han ideographic block and han ideo block.

There are no compatibility mappings between any Han ideographs, either
in Extensions A and B or in the original U+4E00 block. If you're referring
to the CJK Compatibility Ideographs block, those are canonical mappings.

(There are some compatibility mappings from CJK *radicals* to
CJK ideographs. Those will be discussed in my post on NFC vs. NFKC.)

- -- 
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

iQEVAwUBO9DTezkCAxeYt5gVAQHhTgf/cl4yxhdqMVDHmxD405iZwYtJczS5sqR3
0zqu/mt8j2mBAXSGi0Ux116M0/55aQjhy8lMVSCBqgkhUC6WmWrdcOGmfVLh4Sj3
khsRxq91BRsOEUSSS1ZwbveZQkZpjmArMRPzwSz9V/ONet73D6tSbems8Az1qQ8z
BCS64ZtX6D8A+zJTOLUCWRfN7k1m/3ICDblge3wYd/pTnzqqbISs3hcfZeV3YFNr
b7y+6tri3CuR7ZEEkgiiiZq7qqGljEDf1ASOTNoKpg5vb8hF5lhv0GXlFeirsK5v
8siMXxTv+t/ltSjsqWTj8MnzgYaaQSwim3EjFjzq7K8EtJCNYK3MbA==
=FN0J
-----END PGP SIGNATURE-----





From owner-idn@ops.ietf.org  Fri Oct 19 21:52:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11998
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 21:52:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ulBh-000OOK-00
	for idn-data@psg.com; Fri, 19 Oct 2001 18:44:33 -0700
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ulBg-000OO0-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 18:44:32 -0700
Received: from zetnet.co.uk (man-s060.dialup.zetnet.co.uk [194.247.41.187])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f9K1iGl31863;
	Sat, 20 Oct 2001 02:44:16 +0100
Message-ID: <3BD0C257.A61BE893@zetnet.co.uk>
Date: Sat, 20 Oct 2001 01:16:23 +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: Martin Duerst <duerst@w3.org>, idn@ops.ietf.org
Subject: Re: [idn] call for comments for REORDERING
References: <200109181333.JAA19941@ietf.org>
	 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
	 <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <4.2.0.58.J.20011018183339.031fa100@localhost>
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-----

Martin Duerst wrote:
> At 15:43 01/10/10 +0900, Soobok Lee wrote:
> >From: "Martin Duerst" <duerst@w3.org>
> 
> > > The additional complexity introduced by reordering is a very
> > > serious problem. It is true that this complexity is somewhat
> > > similar to the complexity of e.g. nameprep or conversion from
> > > a legacy encoding. However, on many platforms, both conversion
> > > from a legacy encoding as well as many aspects of nameprep
> > > are available as libraries, and are used for other purposes.
> >
> >Current Windows 98,2K,XP and Linux  contain   NFKC codes ?
> 
> No. My personal preference would be for NFC, anyway, because
> most of the additional mappings in NFKC are not really useful,
> because they are from characters that are quite difficult
> to type in. So these characters could just be forbidden rather
> than mapped. The only exception I know is full-width ASCII,
> which could either be included in the nameprep mapping step,
> or could be done as a front-end 'quality of implementation'
> step (similar to how the ideographic fullstop is currently
> treated).

I absolutely agree with this - I've been preparing a detailed
rationale for using NFC in preference to NFKC, that considers all
the categories of compatibility mappings. I'll post it tomorrow.
An important consideration is that by disallowing a larger set of
characters, we can avoid the need for "additional foldings" - i.e.
it is possible to just apply NFC and the standard Unicode case
folding, in either order, which strengthens your argument above
about being able to use existing libraries.

> Displaying ACE when nothing else is available is acceptable
> as a 'best-effort' solution. But it is very far from a good
> solution, and designing the rest of IDN for this doesn't
> make sense.

A better solution for cases where a name can't be displayed in
its original script, is to use a transliteration (which unlike an
ACE encoding, has a chance of actually meaning something to end-
users). I have a proposal for a new RR that allows translations
and transliterations of a name to be looked up, and provides a
way to encode the language and script of each name. This is a new
feature that is independent of the rest of IDN; it doesn't break
the basic model of DNS as an untagged namespace.

- -- 
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

iQEVAwUBO9DB/DkCAxeYt5gVAQFn2Qf/TTGRpLlpuFyxZW4klkAGaGOPDF7wwsND
ovDc38ypkWm3psxJ9NunKzmEudNYA8LiUxxCxU2qO3NAaYnGbqI58/DkauMhiDGK
wb/LO54RcIEuRBiCBDM3R1q1Deznz04lAVudjrOAJX/OdGHTKlEg22E4PTZJPwMZ
FE5deUIk5rG73dtsG/XvXuPdsHe4wwD+70LxWnu7+H5AdBDb/WoUsB0CQor3yQbu
yFDcXSWof5OS4c+x1z53J/gU7I32YXWABxKABZcLHmmrjRDQmVytlMBLyYubf7yN
AVtGn25eB5Y91Z53Cn5grXrd7S/lYX/ZJjAuByA3Wku/cKqu7TmkxQ==
=8UbT
-----END PGP SIGNATURE-----





From owner-idn@ops.ietf.org  Fri Oct 19 21:53:00 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12009
	for <idn-archive@lists.ietf.org>; Fri, 19 Oct 2001 21:52:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ulBi-000OOM-00
	for idn-data@psg.com; Fri, 19 Oct 2001 18:44:34 -0700
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ulBf-000OO8-00
	for idn@ops.ietf.org; Fri, 19 Oct 2001 18:44:31 -0700
Received: from zetnet.co.uk (man-s060.dialup.zetnet.co.uk [194.247.41.187])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f9K1iQl31884;
	Sat, 20 Oct 2001 02:44:26 +0100
Message-ID: <3BD0D662.6428B3C2@zetnet.co.uk>
Date: Sat, 20 Oct 2001 02:41:54 +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] call for comments for REORDERING
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <4.2.0.58.J.20011019160708.037cccd0@localhost> <017b01c15879$99dc8e20$ec1bd9d2@temp>
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:
> From: "Martin Duerst" <duerst@w3.org>
> > >
> > >1) saturations in TLD namespaces would require longer names for which
> > >     REORDERING is designed to give greater benefits/compression ratio.
> >
> > No. What James referred to is that saturation tends to fill up the
> > short name slots, and thus flatten the probability distribution.
> > I.e. if somebody doesn't get the name they wanted, the chance is
> > that they go for something like xq.com, because it's easy to
> > remember because it's short. Neither x nor q are very frequent
> > letters.
> 
> Han/hangeul characters carries meanings while latin alphabets
> denote phonemes.

?? Unless I'm very confused about Hangul, it is at least as much
phonetically-based as Latin. Hangul Jamo are letters of an alphabet,
which happen to be arranged in square cells corresponding to syllables,
instead of linearly.

Moreover, each Hangul syllable (encoded as a single character when
NFC/NFKC-normalised), normally represents 3 Jamo. That should be taken
into account when assessing whether Hangul is encoded compactly enough.

> Therefore your analogy between latin and han domains
> may be false. Chinese people would rather choose to register
> digit-added variants of already taken desired domains in saturated
> ML.com, instead of choosing non-sense irrelevant rare han characters.
> 
> Later time, I will provide some proofs that SC and TC only have
> small partial set of frequent characters.

That's not in dispute. The argument is about whether the complexity of
reordering is worth the additional compression. IMHO it isn't -
AMC-Z (or UTF-8) encodings are sufficiently compact that the 63-octet
and 255-octet limits are not a serious problem for any language or script,
and the savings for average names are marginal.

- -- 
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

iQEVAwUBO9DO2zkCAxeYt5gVAQF/7AgAzp3KB/kPA2XAxb43hCSbrLBOxavd4WSq
DYfvw2UuwloLkEZB+tkkoOPucW/ElLmaYjuYMKt6nea2LZthLpTWDc8a8ENXqM34
Z+aP8nqN9XzeMTPisebpCcTE7PZYWdi87a0grmL0KFBzYG0PsxAB905Yvf12oU4U
u3da6Ku37YJeYK0jNi4/qhoAUZ8gyz+gW4MWWxCmuAIrvmIkaf/d4lX4Tu+75mg2
VcS3ezCGbOt3Wf0GIfUl869BBRbPB7bScBX0EjP/C+sQpCVR6gVs6SKDS9zY/W6k
XImrf7IuLg57za70dy5YiCgNBYOvlNa4Xgi3d+DFoW7jntmj4MEUYw==
=4Lmr
-----END PGP SIGNATURE-----




From owner-idn@ops.ietf.org  Sat Oct 20 09:11:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14787
	for <idn-archive@lists.ietf.org>; Sat, 20 Oct 2001 09:11:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15uvQU-0002Wq-00
	for idn-data@psg.com; Sat, 20 Oct 2001 05:40:30 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15uvQT-0002Wk-00
	for idn@ops.ietf.org; Sat, 20 Oct 2001 05:40:29 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id VAA28810
	for <idn@ops.ietf.org>; Sat, 20 Oct 2001 21:40:13 +0900
Message-ID: <00ef01c15964$83710b70$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <007601c15854$30c1f800$ec1bd9d2@temp> <046001c15855$02854f40$0501000a@jamessonyvaio> <009601c1585d$e7612230$ec1bd9d2@temp> <20011019232352.G24104@nicemice.net>
Subject: [idn] REORDERING : makes labels shorter or longer  ?
Date: Sat, 20 Oct 2001 21:41:13 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA14787

----- Original Message ----- 
From: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>
 
> Soobok Lee <lsb@postel.co.kr> wrote:
> 
> > Even For GROUPS of those rare cases, we get Always SHORTER labels than
> > usual.
> 
> As has already been pointed out, this is impossible.  Here is one class
> of labels that are made longer by reordering:  Labels that use lots of
> "uncommon" code points from the bottom 2K (or whatever) of the block.
> Without reordering, these code points are already close together, but
> with reordering they will be scattered all over the block, resulting in
> a longer ACE.  Of course such labels are supposed to be very rare.
> 
> All compression schemes must make some inputs shorter and some longer.
> The goal is to makes the more common ones a lot shorter, and the very
> rare ones only slightly longer.
> 
 
Exactly right! 
That is what i meant and already answered so in my previous article
you may have missed. Look at uppercased "GROUPS". "rare" characters
are ALL the ones not in the frequent set.

To make it more concrete, I took an experiment.
For 240823 han ML.com labels, I got the following statistics.

From now one, I will focus on only one question at a time
for productive discussions. 
I won't miss other pending questions. Please be patient.

Please comment on the next result.

Soobok Lee
====================================================================


AMCZ < LAMCZ :   4764    (Reordering got longer labels for 1.9% han ML.com )
AMCZ = LAMCZ :  24553
AMCZ > LAMCZ : 211506
Total:         240823



AMCZ < LAMCZ : # of overhead chars for each label length N

  N   labels   +overhead

  1      141   +1.00
  2     2840   +1.13
  3      948   +1.15
  4      675   +1.19
  5      107   +1.18
  6       32   +1.53
  7       12   +1.33
  8        8   +1.38
  9        1   +2.00


AMCZ > LAMCZ : # of saved chars for each label length N

  N   labels   -saved

  1     1199   -1.00
  2    42119   -1.32
  3    35280   -1.88
  4    85233   -2.79
  5    20589   -3.59
  6    15009   -4.71
  7     5151   -5.58
  8     3069   -6.58
  9     1412   -7.39
 10     1201   -8.49
 11      474   -9.26
 12      397   -10.28
 13      164   -10.86
 14      122   -11.79
 15       50   -13.06
 16       29   -13.55
 17        8   -13.00

For N>9, we  always get shorter ACE labels.
For each 1=<N<=9, the net gain is always positive.



27. unihan-4096

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
|  1|    4427|      4427|     14957(3.38)|     13899(3.14)| 7.07|
|  2|   57418|    114836|    384468(3.35)|    332156(2.89)|13.61|
|  3|   41335|    124005|    401283(3.24)|    336045(2.71)|16.26|
|  4|   89296|    357184|   1139404(3.19)|    902406(2.53)|20.80|
|  5|   21091|    105455|    332420(3.15)|    258709(2.45)|22.17|
|  6|   15128|     90768|    284134(3.13)|    213522(2.35)|24.85|
|  7|    5181|     36267|    112576(3.10)|     83844(2.31)|25.52|
|  8|    3082|     24656|     76272(3.09)|     56083(2.27)|26.47|
|  9|    1417|     12753|     39319(3.08)|     28883(2.26)|26.54|
| 10|    1203|     12030|     37136(3.09)|     26935(2.24)|27.47|
| 11|     474|      5214|     16072(3.08)|     11684(2.24)|27.30|
| 12|     398|      4776|     14714(3.08)|     10632(2.23)|27.74|
| 13|     164|      2132|      6532(3.06)|      4751(2.23)|27.27|
| 14|     122|      1708|      5232(3.06)|      3794(2.22)|27.48|
| 15|      50|       750|      2283(3.04)|      1630(2.17)|28.60|
| 16|      29|       464|      1419(3.06)|      1026(2.21)|27.70|
| 17|       8|       136|       405(2.98)|       301(2.21)|25.68|

|All|  240823|    897561|   2868626(3.20)|   2286300(2.55)|20.30|


The next part is hangul ML.com experiment.


AMCZ < LAMCZ :    697  ( 0.3 % )
AMCZ = LAMCZ :   6933
AMCZ > LAMCZ : 198674
Total:         206304

AMCZ < LAMCZ :

  N   labels   +overhead

  2      463   +1.09
  3      175   +1.07
  4       52   +1.25
  5        5   +1.00
  6        2   +2.00


AMCZ > LAMCZ :

  N   labels   -saved

  2    13491   -1.41
  3    38086   -2.09
  4    61900   -3.14
  5    39612   -4.19
  6    23880   -5.29
  7    12447   -6.41
  8     5441   -7.40
  9     2262   -8.46
 10      895   -9.45
 11      373   -10.48
 12      141   -11.17
 13       77   -12.30
 14       32   -13.12
 15       20   -14.05
 16       10   -12.30
 17        7   -15.86


9. hangul-1024

|  N|    FREQ|    N*FREQ|  SUM OF AMCZ(X)| SUM OF LAMCZ(Y)| COMP|
|  1|    1953|      1953|      7812(4.00)|      7812(4.00)| 0.00|
|  2|   17149|     34298|    124782(3.64)|    106238(3.10)|14.86|
|  3|   39643|    118929|    403205(3.39)|    323801(2.72)|19.69|
|  4|   62285|    249140|    816093(3.28)|    622067(2.50)|23.77|
|  5|   39675|    198375|    636102(3.21)|    470174(2.37)|26.09|
|  6|   23891|    143346|    452483(3.16)|    326242(2.28)|27.90|
|  7|   12448|     87136|    271953(3.12)|    192139(2.21)|29.35|
|  8|    5441|     43528|    134600(3.09)|     94322(2.17)|29.92|
|  9|    2264|     20376|     62405(3.06)|     43266(2.12)|30.67|
| 10|     895|      8950|     27223(3.04)|     18764(2.10)|31.07|
| 11|     373|      4103|     12420(3.03)|      8511(2.07)|31.47|
| 12|     141|      1692|      5080(3.00)|      3505(2.07)|31.00|
| 13|      77|      1001|      2986(2.98)|      2039(2.04)|31.71|
| 14|      32|       448|      1331(2.97)|       911(2.03)|31.56|
| 15|      20|       300|       884(2.95)|       603(2.01)|31.79|
| 16|      10|       160|       460(2.88)|       337(2.11)|26.74|
| 17|       7|       119|       354(2.97)|       243(2.04)|31.36|

|All|  206304|    913854|   2960173(3.24)|   2220974(2.43)|24.97|





From owner-idn@ops.ietf.org  Sat Oct 20 15:06:28 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18098
	for <idn-archive@lists.ietf.org>; Sat, 20 Oct 2001 15:06:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15v15O-000B3f-00
	for idn-data@psg.com; Sat, 20 Oct 2001 11:43:06 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15v15N-000B3X-00
	for idn@ops.ietf.org; Sat, 20 Oct 2001 11:43:05 -0700
Received: from [165.227.249.20] (165-227-249-20.client.dsl.net [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f9KIgvD26101
	for <idn@ops.ietf.org>; Sat, 20 Oct 2001 11:42:58 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0510030ab7f774fd857f@[165.227.249.20]>
In-Reply-To: <20011019232352.G24104@nicemice.net>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <024b01c15847$11e8b430$0501000a@jamessonyvaio>
 <007601c15854$30c1f800$ec1bd9d2@temp>
 <046001c15855$02854f40$0501000a@jamessonyvaio>
 <009601c1585d$e7612230$ec1bd9d2@temp> <20011019232352.G24104@nicemice.net>
Date: Sat, 20 Oct 2001 11:42:34 -0700
To: IETF idn working group <idn@ops.ietf.org>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] call for comments for REORDERING
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 11:23 PM +0000 10/19/01, Adam M. Costello wrote:
>  > The reordering proposal and its proponent are based on the faulty
>>  premise that there will be a need for very long domain names for the
>>  scripts that have been reordered.
>
>Actually, he has said many times that his goal is not only to allow long
>domain names, but also to make average domain names easier for humans to
>cope with when they are forced to see the ACE.

You are right, he has said that, but it is so absurd that I ignored 
it. A ten-character string of ASCII gibberish is as hard to "cope 
with" as a twelve-character string of ASCII gibberish. (These are 
approximately the lengths you would get for a name part that consists 
of four Han characters.)

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Sat Oct 20 21:49:15 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21203
	for <idn-archive@lists.ietf.org>; Sat, 20 Oct 2001 21:49:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15v7Sl-000LZE-00
	for idn-data@psg.com; Sat, 20 Oct 2001 18:31:39 -0700
From: "Adam M. Costello" <amc+5nb0vi@nicemice.net>
To: IETF idn working group <idn@ops.ietf.org>
Subject: [idn] Re: hi
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15v7Sl-000LZE-00@psg.com>
Date: Sat, 20 Oct 2001 18:31:39 -0700

Soobok Lee <lsb@postel.co.kr> wrote:

> I suggest you visit the next link which contains The Revelation of the
> Holy Bible in Chinese (GB) and English (Modern BBE and Old KJV).
>
>
http://www.ccim.org/cgi-user/bible/ob?version=hgb&version=kjv&version=bb
e&book=gen
>
> And then, come back to this WG with new estimations on information
> capacity of han letters, please.

In Genesis chapter 1, I counted the Han ideographs in the Chinese Union
version, and the Latin letters in the King James version.  In both cases
I excluded all other characters (punctuation, spaces, verse numbers,
etc).

Chinese ideographs:  778
English letters:    3168

This suggests that each Chinese ideograph carries the information
content of slighly over four English letters.  Therefore a maximal
Chinese domain label in AMC-ACE-Z (19 ideographs, using about 3 octets
each plus 4 octets for the prefix) holds about as much information as
76-letter English string, which is 21% more information than a maximal
English domain label (63 letters using 1 octet each).

The situation is much worse for Korean.  I think each Hangul character
carries the information of only about 1.5 English letters, but still
takes about 2.9 octets in AMC-ACE-Z, which means a maximal Korean domain
label (20 hangul) holds about as much information as a 30-letter English
string.  Of all the languages I've looked at, Korean is by far the least
dense when encoded using AMC-ACE-Z.

AMC





From owner-idn@ops.ietf.org  Sat Oct 20 21:53:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21249
	for <idn-archive@lists.ietf.org>; Sat, 20 Oct 2001 21:53:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15v7di-000LtK-00
	for idn-data@psg.com; Sat, 20 Oct 2001 18:42:58 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15v7dh-000LtE-00
	for idn@ops.ietf.org; Sat, 20 Oct 2001 18:42:57 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id KAA09275;
	Sun, 21 Oct 2001 10:42:43 +0900
Message-ID: <001101c159d1$cffce960$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <4.2.0.58.J.20011019160708.037cccd0@localhost> <017b01c15879$99dc8e20$ec1bd9d2@temp> <3BD0D662.6428B3C2@zetnet.co.uk>
Subject: Re: [idn] call for comments for REORDERING
Date: Sun, 21 Oct 2001 10:43:40 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA21249


----- Original Message ----- 
From: "David Hopwood" <david.hopwood@zetnet.co.uk>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
Sent: Saturday, October 20, 2001 10:41 AM
Subject: Re: [idn] call for comments for REORDERING


> -----BEGIN PGP SIGNED MESSAGE-----
> 
> Soobok Lee wrote:
> > From: "Martin Duerst" <duerst@w3.org>
> > > >
> > > >1) saturations in TLD namespaces would require longer names for which
> > > >     REORDERING is designed to give greater benefits/compression ratio.
> > >
> > > No. What James referred to is that saturation tends to fill up the
> > > short name slots, and thus flatten the probability distribution.
> > > I.e. if somebody doesn't get the name they wanted, the chance is
> > > that they go for something like xq.com, because it's easy to
> > > remember because it's short. Neither x nor q are very frequent
> > > letters.
> > 
> > Han/hangeul characters carries meanings while latin alphabets
> > denote phonemes.
> 
> ?? Unless I'm very confused about Hangul, it is at least as much
> phonetically-based as Latin. Hangul Jamo are letters of an alphabet,
> which happen to be arranged in square cells corresponding to syllables,
> instead of linearly.

You are only partly correct in that Hangul is phonetic.

If you ever read a hangul-to-hangul dictionary, you can find easily that
over 70~80% of modern hangul vocabularies came from 1:1 mappings of
Chinese words like  most english & french words  came from latin ones.
Therefore, one hangul character carries similar amount of information 
with its chinese character counterparts.

hangul/han both carries as much information  as  about 2 latins characters.


> 
> Moreover, each Hangul syllable (encoded as a single character when
> NFC/NFKC-normalised), normally represents 3 Jamo. That should be taken
> into account when assessing whether Hangul is encoded compactly enough.
> 
> > Therefore your analogy between latin and han domains
> > may be false. Chinese people would rather choose to register
> > digit-added variants of already taken desired domains in saturated
> > ML.com, instead of choosing non-sense irrelevant rare han characters.
> > 
> > Later time, I will provide some proofs that SC and TC only have
> > small partial set of frequent characters.
> 
> That's not in dispute. The argument is about whether the complexity of
> reordering is worth the additional compression. IMHO it isn't -
> AMC-Z (or UTF-8) encodings are sufficiently compact that the 63-octet
> and 255-octet limits are not a serious problem for any language or script,
> and the savings for average names are marginal.
> 
> - -- 
> 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
> 
> iQEVAwUBO9DO2zkCAxeYt5gVAQF/7AgAzp3KB/kPA2XAxb43hCSbrLBOxavd4WSq
> DYfvw2UuwloLkEZB+tkkoOPucW/ElLmaYjuYMKt6nea2LZthLpTWDc8a8ENXqM34
> Z+aP8nqN9XzeMTPisebpCcTE7PZYWdi87a0grmL0KFBzYG0PsxAB905Yvf12oU4U
> u3da6Ku37YJeYK0jNi4/qhoAUZ8gyz+gW4MWWxCmuAIrvmIkaf/d4lX4Tu+75mg2
> VcS3ezCGbOt3Wf0GIfUl869BBRbPB7bScBX0EjP/C+sQpCVR6gVs6SKDS9zY/W6k
> XImrf7IuLg57za70dy5YiCgNBYOvlNa4Xgi3d+DFoW7jntmj4MEUYw==
> =4Lmr
> -----END PGP SIGNATURE-----
> 
> 




From owner-idn@ops.ietf.org  Sat Oct 20 23:43:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23636
	for <idn-archive@lists.ietf.org>; Sat, 20 Oct 2001 23:43:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15v9Mt-000Oze-00
	for idn-data@psg.com; Sat, 20 Oct 2001 20:33:43 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15v9Ms-000OzY-00
	for idn@ops.ietf.org; Sat, 20 Oct 2001 20:33: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 MAA10848;
	Sun, 21 Oct 2001 12:33:26 +0900
Message-ID: <003c01c159e1$48504ba0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>,
        "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <4.2.0.58.J.20011019160708.037cccd0@localhost> <017b01c15879$99dc8e20$ec1bd9d2@temp> <3BD0D662.6428B3C2@zetnet.co.uk> <001101c159d1$cffce960$ec1bd9d2@temp>
Subject: [idn] false measure..
Date: Sun, 21 Oct 2001 12:34:25 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id XAA23636


----- Original Message ----- 
From: "Soobok Lee" <lsb@postel.co.kr>
 > > > Han/hangeul characters carries meanings while latin alphabets
> > > denote phonemes.
> > 
> > ?? Unless I'm very confused about Hangul, it is at least as much
> > phonetically-based as Latin. Hangul Jamo are letters of an alphabet,
> > which happen to be arranged in square cells corresponding to syllables,
> > instead of linearly.
> 
> You are only partly correct in that Hangul is phonetic.
> 
> If you ever read a hangul-to-hangul dictionary, you can find easily that
> over 70~80% of modern hangul vocabularies came from 1:1 mappings of
> Chinese words like  most english & french words  came from latin ones.
> Therefore, one hangul character carries similar amount of information 
> with its chinese character counterparts.
> 
> hangul/han both carries as much information  as  about 2 latins characters.

This estimation came from the fact :
  han labels of length N (==8)  have  reordered ACE lables of length 2.27*N
  and hangul labels have  2.17*N , while with bare AMC-ACE-Z , they have 3.1 * N.
  Reordered Greek  labels have 1.2*N for N>16.

hangul : han: Greek   = 2.17 : 2.27 : 1.2

 The amount of information in han/hangul  labels is proportional to the number of corresponding LDH characters in ACE labels?  Maybe false measure from
misconceptions because most han/hangul labels from  nouns or composite nouns.
 I won't use the term  "amount of carried information " from now on..

Soobok Lee
 




From owner-idn@ops.ietf.org  Sun Oct 21 10:12:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13151
	for <idn-archive@lists.ietf.org>; Sun, 21 Oct 2001 10:12:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vIvK-000Cz8-00
	for idn-data@psg.com; Sun, 21 Oct 2001 06:45:55 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vIvJ-000Cyv-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 06:45:53 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id WAA05501;
	Sun, 21 Oct 2001 22:45:29 +0900
Message-ID: <00cb01c15a36$ca8c4a10$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <4.2.0.58.J.20011019152610.037f1100@localhost> <4.2.0.58.J.20011019181604.0312ad90@localhost> <022601c15889$020aa360$ec1bd9d2@temp> <007e01c158c3$e2f41ac0$0601000a@jamessonyvaio>
Subject: [idn] REORDERING: stability issues and UTC solutions
Date: Sun, 21 Oct 2001 22:46:29 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA13151


----- Original Message ----- 
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>; "Martin Duerst" <duerst@w3.org>
Sent: Saturday, October 20, 2001 2:31 AM
Subject: Re: [idn] call for comments for REORDERING


> > maybe problematic and unsafe.
> > What if future NFC/NFKC maps them into other code points ?
> > There will be a mess, too.
> 
> read the design principle of NFC or NFKC. Future addition of scripts and
> addition normalization will *NOT* cause existing normalized string to
> changed.

My  question was that:
  1) newly-approved TAGALOG characters X,Y  have   NFC X -> Y,
  2) old Nameprep/ACE encodes X.com and Y.com as two distinct ACE labels,
      because it don't know about NFC X -> Y
  3) new Nameprep/ACE encodes X.com as the the same ACE label as Y.com's 
      with NFC  X -> Y.

  If X.com and Y.com are taken by two distinct registrants, there will
    be a mess. of course, it should have be blocked by careful registries.
  Even if new ACE libaries are distributed, some old ACE tools will still
    try to send X.com dns queries which may fail.
 

> 
> do you have the same stability principle or ensure that to be the same
> for re-ordering? or one which can be sure?

yes. Like old nameprep bypasses unassigned code points for future TAGALOG script,
REORDERING bypasses,too. No ACE improvement for taglog now.
See below.

> 
> > Current REORDERING does nothing with TAGALOG and adds
> > no new problem into ACE. the problem is alerady inherent
> > in ACE and nameprep version scheme, and is not due to
> > REORDERING.
> 
> But Tagalog may then come back to IDN to claim unfair treatment!
> Are you going to deny them that?

Are you saying ?:
   Tagalog folks may come back  with complaints about old nameprep 
   which has no NFC X->Y, saying "unfair treatment!" ??

Before TAGALOG is added, current nameprep/REORDERING have 
no reponsibility for inevitable missing supports of them.

Now I will propose two solutions.

1) last resort: somewhat tricky

Future TAGALOG may provides two sets of TAGALOG basic alphabets.
One set A in official lexicographical ordering and the other set B 
is in frequecy ordering (sub-optimal one OKAY) with 1:1 NFKC defined 
from A onto B.
Then all tagalog basic alphabets in Set A will be "reordered by NFKC"
in nameprep , not in ACE. A and B share the same font.
Then valid ACE labels of TAGALOG script only contains characters from B.
This may have some problems in comparisons which i have no full analysis.

2) UTC solution

IF UTC accepts REORDERING as an official normalization form like 
NF-REORDERING , then we need no such tricks like above, and
TAGALOG support can be done within that NF in the new 
NAMEPREP steps:  mapping/NFKC/PROHIBIT and then NF-REORDERING .

Frequency tables are always sub-optimal in its nature, and 
marginal frequency fluctuation will occurs to make marginal 
efficieny changes, but in most cases, i am sure, it will benefit
most of TAGALOG labels, and that's why i push REORDERING into UTC. 

In conclusion, 2) is the my preferenece.
It's the best way for acquiring stability and authority and applicability
of REORDERING.


> 
> > Prefix-based version scheme will solve those problems.
> 
> No no no. Lets not get into other scheme which involves playing with
> multiples prefix or suffix as "version tag". Try not to make things more
> complex here.
> 
> The key word here is stability. You have not address it yet.

Answered. with the above solutions we need no version tag..


> 
> And no, there is no such thing as "only compress" algorithm. It is
> mathemtically impossible.

Already answered in the separate thread "[idn] REORDERING : makes labels shorter or longer  ?".


Soobok Lee

> 
> -James Seng
> 
> 




From owner-idn@ops.ietf.org  Sun Oct 21 10:30:31 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13539
	for <idn-archive@lists.ietf.org>; Sun, 21 Oct 2001 10:30:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vJVG-000Dr4-00
	for idn-data@psg.com; Sun, 21 Oct 2001 07:23:02 -0700
Received: from smtp22.singnet.com.sg ([165.21.101.202])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vJVE-000Dqv-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 07:23:01 -0700
Received: from jamessonyvaio (bb104-101.singnet.com.sg [165.21.104.101])
	by smtp22.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9LEQ3J25949;
	Sun, 21 Oct 2001 22:26:03 +0800
Message-ID: <004201c15a3b$e0420d40$0e01000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <4.2.0.58.J.20011019152610.037f1100@localhost> <4.2.0.58.J.20011019181604.0312ad90@localhost> <022601c15889$020aa360$ec1bd9d2@temp> <007e01c158c3$e2f41ac0$0601000a@jamessonyvaio> <00cb01c15a36$ca8c4a10$ec1bd9d2@temp>
Subject: [idn] Re: REORDERING: stability issues and UTC solutions
Date: Sun, 21 Oct 2001 22: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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Firstly, lets not try to twist the whole argument to Normalization,
which you are doing here. We are talking about Reordering so lets focus
on it.

> My  question was that:
>   1) newly-approved TAGALOG characters X,Y  have   NFC X -> Y,
>   2) old Nameprep/ACE encodes X.com and Y.com as two distinct ACE
labels,
>       because it don't know about NFC X -> Y
>   3) new Nameprep/ACE encodes X.com as the the same ACE label as
Y.com's
>       with NFC  X -> Y.

My shortest answer is for you to read UTR#15. It is already addressed
there.

>   If X.com and Y.com are taken by two distinct registrants, there will
>     be a mess. of course, it should have be blocked by careful
registries.
>   Even if new ACE libaries are distributed, some old ACE tools will
still
>     try to send X.com dns queries which may fail.

No it wont. Patrik Faltstorm have already discuss this possiblities and
the work around this. It was one of the version of Nameprep but I
realised it is no longer in -06.

> Are you saying ?:
>    Tagalog folks may come back  with complaints about old nameprep
>    which has no NFC X->Y, saying "unfair treatment!" ??

No, I am saying REORDERING. Lets keep the topic on REORDERING.

> 1) last resort: somewhat tricky
>
> Future TAGALOG may provides two sets of TAGALOG basic alphabets.
> One set A in official lexicographical ordering and the other set B
> is in frequecy ordering (sub-optimal one OKAY) with 1:1 NFKC defined
> from A onto B.
> Then all tagalog basic alphabets in Set A will be "reordered by NFKC"
> in nameprep , not in ACE. A and B share the same font.
> Then valid ACE labels of TAGALOG script only contains characters from
B.
> This may have some problems in comparisons which i have no full
analysis.

Okay. This should go into ISO10646 SC2/WG2 then.

> 2) UTC solution
>
> IF UTC accepts REORDERING as an official normalization form like
> NF-REORDERING , then we need no such tricks like above, and
> TAGALOG support can be done within that NF in the new
> NAMEPREP steps:  mapping/NFKC/PROHIBIT and then NF-REORDERING .
>
> Frequency tables are always sub-optimal in its nature, and
> marginal frequency fluctuation will occurs to make marginal
> efficieny changes, but in most cases, i am sure, it will benefit
> most of TAGALOG labels, and that's why i push REORDERING into UTC.
>
> In conclusion, 2) is the my preferenece.
> It's the best way for acquiring stability and authority and
applicability
> of REORDERING.

Okay. This should go into UTC.

Both your solution unfortunately cannot be done in this WG.

-James Seng




From owner-idn@ops.ietf.org  Sun Oct 21 10:35:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13628
	for <idn-archive@lists.ietf.org>; Sun, 21 Oct 2001 10:35:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vJZ9-000Dxb-00
	for idn-data@psg.com; Sun, 21 Oct 2001 07:27:03 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vJZ8-000DxU-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 07:27:02 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id XAA18235;
	Sun, 21 Oct 2001 23:26:47 +0900
Message-ID: <00d701c15a3c$8f135130$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>,
        "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
Subject: [idn] (self-comment)Re: REORDERING: stability issues and UTC solutions
Date: Sun, 21 Oct 2001 23:27:48 +0900
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00D3_01C15A87.FEAD0040"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_00D3_01C15A87.FEAD0040
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Self-comments:

  ----- Original Message ----- 
  From: "Soobok Lee" <lsb@postel.co.kr>
   
  1) last resort: somewhat tricky

  Future TAGALOG may provides two sets of TAGALOG basic alphabets.
  One set A in official lexicographical ordering and the other set B 
  is in frequecy ordering (sub-optimal one OKAY) with 1:1 NFKC defined 
  from A onto B.
  Then all tagalog basic alphabets in Set A will be "reordered by NFKC"
  in nameprep , not in ACE. A and B share the same font.
  Then valid ACE labels of TAGALOG script only contains characters from B.
  This may have some problems in comparisons which i have no full analysis.

  2) UTC solution

  IF UTC accepts REORDERING as an official normalization form like 
  NF-REORDERING , then we need no such tricks like above, and
  TAGALOG support can be done within that NF in the new 
  NAMEPREP steps:  mapping/NFKC/PROHIBIT and then NF-REORDERING .
NF-REORDERING should work only for newly-added SCRIPT BLOCK like TAGALOG.
NF-REORDERING requires separate code points for reordered ones mapped from
 basic alphabets in the same TAGALOG script block like solutions 1).
The only difference between solution 1) and 2)  is whether the REORDERING is
in NFKC-trick or in Official new NF.

With these two sets of basic alphabets, old nameprep/ACE+REORDERING libaries
may encode the reordered character set and get the compression transparently
without any code/data upgrades in old applications.

If it uses the other un-reordered character set, it will have un-compressed 
different lACE label which is , of course, made to be equivalent to the other 
reordered ACE label  by zone-master's multiple-registrations provisions.

NF-REORDERING should be applied before ACE-encoding and 
should be reversed after ACE-decoding for rendering for new added SCRIPT.

Existing scripts could be reordered in ACE as  now.

Any suggestion welcomed.

 
Soobok Lee


  Frequency tables are always sub-optimal in its nature, and 
  marginal frequency fluctuation will occurs to make marginal 
  efficieny changes, but in most cases, i am sure, it will benefit
  most of TAGALOG labels, and that's why i push REORDERING into UTC. 

  In conclusion, 2) is the my preferenece.
  It's the best way for acquiring stability and authority and applicability
  of REORDERING.

   

------=_NextPart_000_00D3_01C15A87.FEAD0040
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.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV dir=3Dltr><FONT face=3D&#44404;&#47548; =
size=3D2><STRONG>Self-comments:</STRONG></FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV><FONT face=3D&#44404;&#47548; size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D&#44404;&#47548; size=3D2>----- Original Message =
----- </FONT>
  <DIV><FONT face=3D&#44404;&#47548; size=3D2>From: "Soobok Lee" =
&lt;</FONT><A=20
  href=3D"mailto:lsb@postel.co.kr"><FONT face=3D&#44404;&#47548;=20
  size=3D2>lsb@postel.co.kr</FONT></A><FONT face=3D&#44404;&#47548; =
size=3D2>&gt;</FONT></DIV>
  <DIV><FONT face=3D&#44404;&#47548; size=3D2>&nbsp;<BR>1) last resort: =
somewhat=20
  tricky<BR><BR>Future TAGALOG may provides two sets of TAGALOG basic=20
  alphabets.<BR>One set A in official lexicographical ordering and the =
other set=20
  B <BR>is in frequecy ordering (sub-optimal one OKAY) with 1:1 NFKC =
defined=20
  <BR>from A onto B.<BR>Then all tagalog basic alphabets in Set A will =
be=20
  "reordered by NFKC"<BR>in nameprep , not in ACE. A and B share the =
same=20
  font.<BR>Then valid ACE labels of TAGALOG script only contains =
characters from=20
  B.<BR>This may have some problems in comparisons which i have no full=20
  analysis.<BR><BR>2) UTC solution<BR><BR>IF UTC accepts REORDERING as =
an=20
  official normalization form like <BR>NF-REORDERING , then we need no =
such=20
  tricks like above, and<BR>TAGALOG support can be done within that NF =
in the=20
  new <BR>NAMEPREP steps:&nbsp; mapping/NFKC/PROHIBIT and then =
NF-REORDERING=20
  .</FONT></DIV><FONT face=3D&#44404;&#47548; =
size=3D2></FONT></DIV><FONT face=3D&#44404;&#47548;=20
size=3D2></FONT></BLOCKQUOTE><FONT face=3D&#44404;&#47548; size=3D2>
<DIV dir=3Dltr><STRONG><FONT face=3DArial size=3D3>NF-REORDERING should =
work only for=20
newly-added SCRIPT BLOCK like TAGALOG.</FONT></STRONG></DIV>
<DIV dir=3Dltr><STRONG><FONT face=3DArial size=3D3>NF-REORDERING =
requires separate=20
code points for reordered ones mapped from</FONT></STRONG></DIV>
<DIV dir=3Dltr><FONT size=3D3><FONT face=3DArial><STRONG>&nbsp;basic =
alphabets in the=20
same&nbsp;</STRONG><STRONG>TAGALOG script block like solutions=20
1).</STRONG></FONT></FONT></DIV>
<DIV dir=3Dltr><STRONG><FONT face=3DArial size=3D3>The only difference =
between=20
solution 1) and 2)&nbsp; is whether the REORDERING =
is</FONT></STRONG></DIV>
<DIV dir=3Dltr><STRONG><FONT face=3DArial size=3D3>in NFKC-trick or in =
Official=20
new&nbsp;NF.</FONT></STRONG></DIV>
<DIV dir=3Dltr><STRONG><FONT face=3DArial =
size=3D3></FONT></STRONG>&nbsp;</DIV>
<DIV dir=3Dltr><STRONG><FONT face=3DArial size=3D3>With these two sets =
of basic=20
alphabets, old nameprep/ACE+REORDERING libaries</FONT></STRONG></DIV>
<DIV dir=3Dltr><STRONG><FONT face=3DArial size=3D3>may encode&nbsp;the =
reordered=20
character set and get the compression =
transparently</FONT></STRONG></DIV>
<DIV dir=3Dltr><STRONG><FONT face=3DArial size=3D3>without any code/data =
upgrades in=20
old applications.</FONT></STRONG></DIV>
<DIV dir=3Dltr><STRONG><FONT face=3DArial =
size=3D3></FONT></STRONG>&nbsp;</DIV>
<DIV dir=3Dltr><STRONG><FONT face=3DArial size=3D3>If it uses the other =
un-reordered=20
</FONT></STRONG><STRONG><FONT face=3DArial size=3D3>character set, it =
will have=20
un-compressed </FONT></STRONG></DIV>
<DIV dir=3Dltr><STRONG><FONT face=3DArial size=3D3>different lACE label =
which=20
</FONT></STRONG><STRONG><FONT face=3DArial size=3D3>is , of course, made =
to=20
be&nbsp;equivalent to the other </FONT></STRONG></DIV>
<DIV dir=3Dltr><STRONG><FONT face=3DArial size=3D3>reordered ACE =
label&nbsp; by=20
zone-master's </FONT></STRONG><STRONG><FONT face=3DArial=20
size=3D3>multiple-registrations provisions.</FONT></STRONG></DIV>
<DIV dir=3Dltr><STRONG><FONT face=3DArial =
size=3D3></FONT></STRONG>&nbsp;</DIV>
<DIV dir=3Dltr><STRONG><FONT face=3DArial size=3D3>NF-REORDERING should =
be applied=20
before ACE-encoding and </FONT></STRONG></DIV>
<DIV dir=3Dltr><STRONG><FONT size=3D4><FONT face=3DArial><FONT =
size=3D3>should be=20
reversed after ACE-decoding for rendering for new added=20
SCRIPT.</FONT></FONT></FONT></STRONG></DIV>
<DIV dir=3Dltr><STRONG><FONT face=3DArial =
size=3D3></FONT></STRONG>&nbsp;</DIV>
<DIV dir=3Dltr><STRONG><FONT face=3DArial size=3D3>Existing scripts =
could be reordered=20
in ACE as&nbsp; now.</FONT></STRONG></DIV>
<DIV dir=3Dltr><STRONG><FONT face=3DArial =
size=3D3></FONT></STRONG>&nbsp;</DIV>
<DIV dir=3Dltr><STRONG><FONT face=3DArial size=3D3>Any suggestion=20
welcomed.</FONT></STRONG></DIV>
<DIV dir=3Dltr>&nbsp;</DIV>
<DIV dir=3Dltr><FONT size=3D4>&nbsp;</FONT></DIV>
<DIV dir=3Dltr><STRONG>Soobok Lee</STRONG></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV><BR><BR>Frequency tables are always sub-optimal in its nature, =
and=20
  <BR>marginal frequency fluctuation will occurs to make marginal =
<BR>efficieny=20
  changes, but in most cases, i am sure, it will benefit<BR>most of =
TAGALOG=20
  labels, and that's why i push REORDERING into UTC. <BR><BR>In =
conclusion, 2)=20
  is the my preferenece.<BR>It's the best way for acquiring stability =
and=20
  authority and applicability<BR>of=20
  =
REORDERING.<BR><BR><STRONG>&nbsp;</STRONG></FONT></DIV></BLOCKQUOTE></BOD=
Y></HTML>

------=_NextPart_000_00D3_01C15A87.FEAD0040--




From owner-idn@ops.ietf.org  Sun Oct 21 10:40:56 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13897
	for <idn-archive@lists.ietf.org>; Sun, 21 Oct 2001 10:40:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vJfG-000E9I-00
	for idn-data@psg.com; Sun, 21 Oct 2001 07:33:22 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vJfF-000E9A-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 07:33:21 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id XAA20230;
	Sun, 21 Oct 2001 23:33:08 +0900
Message-ID: <00ea01c15a3d$72a845e0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <4.2.0.58.J.20011019152610.037f1100@localhost> <4.2.0.58.J.20011019181604.0312ad90@localhost> <022601c15889$020aa360$ec1bd9d2@temp> <007e01c158c3$e2f41ac0$0601000a@jamessonyvaio> <00cb01c15a36$ca8c4a10$ec1bd9d2@temp> <004201c15a3b$e0420d40$0e01000a@jamessonyvaio>
Subject: [idn] Re: REORDERING: stability issues and UTC solutions
Date: Sun, 21 Oct 2001 23:34:10 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA13897


----- Original Message ----- 
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>; "Martin Duerst" <duerst@w3.org>
Sent: Sunday, October 21, 2001 11:22 PM
Subject: Re: REORDERING: stability issues and UTC solutions


> Firstly, lets not try to twist the whole argument to Normalization,
> which you are doing here. We are talking about Reordering so lets focus
> on it.
> 
> > My  question was that:
> >   1) newly-approved TAGALOG characters X,Y  have   NFC X -> Y,
> >   2) old Nameprep/ACE encodes X.com and Y.com as two distinct ACE
> labels,
> >       because it don't know about NFC X -> Y
> >   3) new Nameprep/ACE encodes X.com as the the same ACE label as
> Y.com's
> >       with NFC  X -> Y.
> 
> My shortest answer is for you to read UTR#15. It is already addressed
> there.

I read http://www.unicode.org/unicode/standard/policies.html and
http://www.unicode.org/unicode/reports/tr15/#3.1_Corrigendum.

Would anyone suggest more ?

Soobok Lee

> 
> >   If X.com and Y.com are taken by two distinct registrants, there will
> >     be a mess. of course, it should have be blocked by careful
> registries.
> >   Even if new ACE libaries are distributed, some old ACE tools will
> still
> >     try to send X.com dns queries which may fail.
> 
> No it wont. Patrik Faltstorm have already discuss this possiblities and
> the work around this. It was one of the version of Nameprep but I
> realised it is no longer in -06.
> 
> > Are you saying ?:
> >    Tagalog folks may come back  with complaints about old nameprep
> >    which has no NFC X->Y, saying "unfair treatment!" ??
> 
> No, I am saying REORDERING. Lets keep the topic on REORDERING.
> 
> > 1) last resort: somewhat tricky
> >
> > Future TAGALOG may provides two sets of TAGALOG basic alphabets.
> > One set A in official lexicographical ordering and the other set B
> > is in frequecy ordering (sub-optimal one OKAY) with 1:1 NFKC defined
> > from A onto B.
> > Then all tagalog basic alphabets in Set A will be "reordered by NFKC"
> > in nameprep , not in ACE. A and B share the same font.
> > Then valid ACE labels of TAGALOG script only contains characters from
> B.
> > This may have some problems in comparisons which i have no full
> analysis.
> 
> Okay. This should go into ISO10646 SC2/WG2 then.

YEs. When New script is added.

Soobok lee

> 
> > 2) UTC solution
> >
> > IF UTC accepts REORDERING as an official normalization form like
> > NF-REORDERING , then we need no such tricks like above, and
> > TAGALOG support can be done within that NF in the new
> > NAMEPREP steps:  mapping/NFKC/PROHIBIT and then NF-REORDERING .
> >
> > Frequency tables are always sub-optimal in its nature, and
> > marginal frequency fluctuation will occurs to make marginal
> > efficieny changes, but in most cases, i am sure, it will benefit
> > most of TAGALOG labels, and that's why i push REORDERING into UTC.
> >
> > In conclusion, 2) is the my preferenece.
> > It's the best way for acquiring stability and authority and
> applicability
> > of REORDERING.
> 
> Okay. This should go into UTC.
> 
> Both your solution unfortunately cannot be done in this WG.
> 
> -James Seng
> 




From owner-idn@ops.ietf.org  Sun Oct 21 11:12:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14366
	for <idn-archive@lists.ietf.org>; Sun, 21 Oct 2001 11:12:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vK96-000Euv-00
	for idn-data@psg.com; Sun, 21 Oct 2001 08:04:12 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vK95-000Euj-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 08:04:11 -0700
Received: from [165.227.249.20] (165-227-249-20.client.dsl.net [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f9LF49824893
	for <idn@ops.ietf.org>; Sun, 21 Oct 2001 08:04:09 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100324b7f8941bf1b9@[165.227.249.20]>
In-Reply-To: <004201c15a3b$e0420d40$0e01000a@jamessonyvaio>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <024b01c15847$11e8b430$0501000a@jamessonyvaio>
 <4.2.0.58.J.20011019152610.037f1100@localhost>
 <4.2.0.58.J.20011019181604.0312ad90@localhost>
 <022601c15889$020aa360$ec1bd9d2@temp>
 <007e01c158c3$e2f41ac0$0601000a@jamessonyvaio>
 <00cb01c15a36$ca8c4a10$ec1bd9d2@temp>
 <004201c15a3b$e0420d40$0e01000a@jamessonyvaio>
Date: Sun, 21 Oct 2001 08:03:32 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: [idn] Re: REORDERING: stability issues and UTC solutions
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 10:22 PM +0800 10/21/01, James Seng/Personal wrote:
>No it wont. Patrik Faltstorm have already discuss this possiblities and
>the work around this. It was one of the version of Nameprep but I
>realised it is no longer in -06.

It is in stringprep-00, which is where it should be.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Sun Oct 21 15:33:32 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16177
	for <idn-archive@lists.ietf.org>; Sun, 21 Oct 2001 15:33:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vO4L-000LJH-00
	for idn-data@psg.com; Sun, 21 Oct 2001 12:15:33 -0700
Received: from imo-r03.mx.aol.com ([152.163.225.99])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vO4L-000LJB-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 12:15:33 -0700
Received: from DougEwell2@cs.com
	by imo-r03.mx.aol.com (mail_out_v31_r1.8.) id i.14.1c53f460 (4206);
	Sun, 21 Oct 2001 15:15:21 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <14.1c53f460.290478ce@cs.com>
Date: Sun, 21 Oct 2001 15:15:26 EDT
Subject: Re: [idn] REORDERING: stability issues and UTC solutions
To: idn@ops.ietf.org
CC: lsb@postel.co.kr, unicode@unicode.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a message dated 2001-10-21 7:22:07 Pacific Daylight Time, lsb@postel.co.kr 
writes:

>  My  question was that:
>    1) newly-approved TAGALOG characters X,Y  have   NFC X -> Y,

This is simply not going to happen.  Unicode/10646 has promised us they are 
not going to add more compatibility characters, though, believe me, they have 
had plenty of requests.

>  Future TAGALOG may provides two sets of TAGALOG basic alphabets.
>  One set A in official lexicographical ordering and the other set B 
>  is in frequecy ordering (sub-optimal one OKAY) with 1:1 NFKC defined 
>  from A onto B.

Are you actually suggesting that UTC encode each character twice?

>  IF UTC accepts REORDERING as an official normalization form like 
>  NF-REORDERING , then we need no such tricks like above, and
>  TAGALOG support can be done within that NF in the new 
>  NAMEPREP steps:  mapping/NFKC/PROHIBIT and then NF-REORDERING .

Is this scheme of reordering for the sake of compression really UTC's concern?

I would suggest that Soobok read not only UTR #15, but also the page called 
"Unicode Policies" on the Unicode web site.  There is a very clear 
description of some things Unicode (and by extension ISO/IEC JTC1/SC2/WG2) 
simply will not do.  It may be a real eye-opener for some.

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Sun Oct 21 21:48:04 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20287
	for <idn-archive@lists.ietf.org>; Sun, 21 Oct 2001 21:48:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vTsH-0004Pv-00
	for idn-data@psg.com; Sun, 21 Oct 2001 18:27:29 -0700
Received: from smtp21.singnet.com.sg ([165.21.101.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vTsG-0004Po-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 18:27:28 -0700
Received: from jamessonyvaio (bb104-101.singnet.com.sg [165.21.104.101])
	by smtp21.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9M1SSp17998;
	Mon, 22 Oct 2001 09:28:28 +0800
Message-ID: <000901c15a98$b49d48a0$1001000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <DougEwell2@cs.com>, <idn@ops.ietf.org>
Cc: <lsb@postel.co.kr>, <unicode@unicode.org>
References: <14.1c53f460.290478ce@cs.com>
Subject: Re: [idn] REORDERING: stability issues and UTC solutions
Date: Mon, 22 Oct 2001 09:27:25 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Is this scheme of reordering for the sake of compression really UTC's
concern?

Actually, they might. See UTS#6 A Standard Compression.

But of course, this discussion is not for IDN WG.

-James Seng




From owner-idn@ops.ietf.org  Sun Oct 21 21:48:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20298
	for <idn-archive@lists.ietf.org>; Sun, 21 Oct 2001 21:48:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vToR-0004HV-00
	for idn-data@psg.com; Sun, 21 Oct 2001 18:23:31 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vToQ-0004HP-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 18:23:30 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id KAA25066
	for <idn@ops.ietf.org>; Mon, 22 Oct 2001 10:23:19 +0900
Message-ID: <002a01c15a98$44d0ada0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <4.2.0.58.J.20011019152610.037f1100@localhost> <4.2.0.58.J.20011019181604.0312ad90@localhost> <022601c15889$020aa360$ec1bd9d2@temp> <007e01c158c3$e2f41ac0$0601000a@jamessonyvaio> <00cb01c15a36$ca8c4a10$ec1bd9d2@temp> <004201c15a3b$e0420d40$0e01000a@jamessonyvaio>
Subject: Re: [idn] Re: REORDERING: stability issues and UTC solutions
Date: Mon, 22 Oct 2001 10:24:17 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA20298

We have no TAGALOG characters X,Y now. 
After we finalized nameprep/ACE,
TAGALOG script may be added to Unicode.
Then,
 
> My  question was that:
>   1) newly-approved TAGALOG characters X,Y  have   NFC X -> Y,
>   2) old Nameprep/ACE encodes X.com and Y.com as two distinct ACE labels,

unassingned code points are allowed in query from old version nameprep.
X.com Y.com are passed through into DNS servers which have no stored tagalog
labels before TAGALOG is added, but begin to accept it after it's approved & added.

>       because it don't know about NFC X -> Y
>   3) new Nameprep/ACE encodes X.com as the the same ACE label as
>       Y.com's       with NFC  X -> Y.
> 
> >   If X.com and Y.com are taken by two distinct registrants, there will
> >     be a mess. of course, it should have be blocked by careful
> registries.
> >   Even if new ACE libaries are distributed, some old ACE tools will
> still
> >     try to send X.com dns queries which may fail.
> 
this case is described in stringprep-00, section 6.3 paragraph 3.
that query should fail. Old nameprep/ACE applications should send
Y.com instead of X.com even when it gets native X.com from html page
(human input should contain only Y.com, not X.com). 
See the *HAS TO* sentence below.
In such case, end users should upgrade their old applications.
Until upgradea are finishied, someone would have complaints 
for such inconveniences.

****
Newer stored string -- Suppose that an requesting application is using
oldVersion and the stored string was created using a profile that uses
newVersion. Because the requesting application passed through any
unassigned code points, the user can query on stored strings that use
code points in newVersion. No stored strings can have code points that
are unassigned in newVersion, since that is illegal. In this case, the
querying application *HAS TO* enter the unassigned code points in the
correct order, and *HAS TO* to use unassigned code points that would make it
through both the mapping and the normalization steps.
*****
 
Soobok Lee
==============================================

http://www.ietf.org/internet-drafts/draft-hoffman-stringprep-00.txt


6.2 Reasons for difference between stored strings and requests

Different software using different versions of a stringprep profile need
to interoperate with maximal compatibility. The scheme described in this
section (stored strings MUST NOT contain unassigned code points,
requests MAY include unassigned code points) allows that compatibility
without introducing any known security or interoperability issues.

The list below shows what happens if a request contains a code point
from category U that is allowed in a newer version of a profile. The
request either matches the string that was intended, or matches no
string at all. In this list, the request comes from an application using
version "oldVersion" of a profile, the stored string was created using
version "newVersion" of the same profile, and the code point X was in
category U in oldVersion, and has changed category to AO, MN, or D.
There are 3 possible scenarios:

1. X is assigned to AO -- In newVersion, X is in category AO. Because
the application passed X through, it gets back a correct match with the
stored string. There is one exceptional case, where X is a combining
mark.

The order of combining marks is normalized, so if another combining mark
Y has a lower combining class than X then XY will be put in the
canonical order YX. (Unassigned code points are never reordered, so this
doesn't happen in oldVersion). If the request contains YX, the request
will get correct match with the stored string. However, no string can be
stored with XY, so a request with XY will correctly get a negative
answer to the test for matching.

2. X is assigned to MN -- In newVersion, X is normalized to code point
"nX" and therefore X is now put in category MN. This cannot exist in any
stored string, so any request containing X will correctly get a negative
answer to the test for matching. Note, however, if the request had
contained the letter nX, it would have correctly matched.

3. X is assigned to D -- In newVersion, X is in category D. This cannot
exist in any stored string, so any request containing X will correctly
get a negative answer to the test for matching.

In none of the cases does the request get data for a stored string other
than the one it actually tried to match against.

The processing in this document is always stable. If a string S is the
result of processing on newVersion, then it will remain the same when
processed on oldVersion.

6.3 Versions of applications and stored strings

Another way to see that this versioning system works is to compare what
happens when an application uses a newer or older version of this
document.

Newer query application -- Suppose that a requesting application is
using version newVersion and the stored string was created using version
oldVersion. This case is simple: there will be no characters in the
stored string that cannot be requested by the application because the
new profile uses a superset of the code points used for making the
stored string.

Newer stored string -- Suppose that an requesting application is using
oldVersion and the stored string was created using a profile that uses
newVersion. Because the requesting application passed through any
unassigned code points, the user can query on stored strings that use
code points in newVersion. No stored strings can have code points that
are unassigned in newVersion, since that is illegal. In this case, the
querying application has to enter the unassigned code points in the
correct order, and has to use unassigned code points that would make it
through both the mapping and the normalization steps.


7. Security Considerations

The Unicode and ISO/IEC 10646 repertoires have many characters that look
similar. In many cases, users of security protocols might do visual
matching, such as when comparing the names of trusted third parties.
Stringprep does nothing to map similar-looking characters together.





From owner-idn@ops.ietf.org  Sun Oct 21 23:26:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21907
	for <idn-archive@lists.ietf.org>; Sun, 21 Oct 2001 23:26:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vVZC-00079P-00
	for idn-data@psg.com; Sun, 21 Oct 2001 20:15:54 -0700
Received: from imo-r10.mx.aol.com ([152.163.225.106])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vVZB-00079J-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 20:15:53 -0700
Received: from DougEwell2@cs.com
	by imo-r10.mx.aol.com (mail_out_v31_r1.8.) id i.18.1420a617 (4208);
	Sun, 21 Oct 2001 23:15:46 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <18.1420a617.2904e961@cs.com>
Date: Sun, 21 Oct 2001 23:15:45 EDT
Subject: Re: [idn] Re: REORDERING: stability issues and UTC solutions
To: idn@ops.ietf.org
CC: lsb@postel.co.kr
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a message dated 2001-10-21 18:55:09 Pacific Daylight Time, 
lsb@postel.co.kr writes:

>  We have no TAGALOG characters X,Y now. 
>  After we finalized nameprep/ACE,
>  TAGALOG script may be added to Unicode.
>  Then,
>
>  > My  question was that:
>  >   1) newly-approved TAGALOG characters X,Y  have   NFC X -> Y,
>  >   2) old Nameprep/ACE encodes X.com and Y.com as two distinct ACE labels,

The point that I still don't think Soobok is getting is that his scenario (1) 
is not going to happen.  Everything he said from that point forward, 
including the lengthy quote from the stringprep document, has to do with 
assigned code points and unassigned code points, not with newly created 
compatibility variants -- and for good reason: there aren't going to be any.

The Tagalog characters that are proposed for inclusion in Unicode 3.2 are 
presented in chart form at:

    http://www.unicode.org/charts/draftunicode32/U32-1700.pdf

and will probably be added soon to the draft Unicode 3.2 data file at:

    http://www.unicode.org/Public/BETA/Unicode3.2/UnicodeData-3.2.0d1.txt

It might be a good idea to peruse these resources and verify for oneself that 
they do not contain any characters that are compatibility forms of other 
characters or combinations of characters.  Of course, nobody can predict the 
future with 100% accuracy but there are lots of good hints that the scenario 
"newly-approved 'S' characters X,Y  have   NFC X -> Y" for any script 'S' is 
simply not ever going to happen.

And in any event, by this point I have completely lost how this affects the 
case for reordering.

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Sun Oct 21 23:39:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22339
	for <idn-archive@lists.ietf.org>; Sun, 21 Oct 2001 23:39:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vVk0-0007Sb-00
	for idn-data@psg.com; Sun, 21 Oct 2001 20:27:04 -0700
Received: from imo-d01.mx.aol.com ([205.188.157.33])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vVjz-0007SV-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 20:27:03 -0700
Received: from DougEwell2@cs.com
	by imo-d01.mx.aol.com (mail_out_v31_r1.8.) id i.5f.1c928d27 (4208);
	Sun, 21 Oct 2001 23:26:46 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <5f.1c928d27.2904ebf5@cs.com>
Date: Sun, 21 Oct 2001 23:26:45 EDT
Subject: Re: [idn] REORDERING: stability issues and UTC solutions
To: idn@ops.ietf.org
CC: jseng@pobox.org.sg, unicode@unicode.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a message dated 2001-10-21 18:27:30 Pacific Daylight Time, 
jseng@pobox.org.sg writes:

> > Is this scheme of reordering for the sake of compression really UTC's
>  concern?
>
>  Actually, they might. See UTS#6 A Standard Compression.

I know a little about SCSU, having written the SCSU encoder and decoder used 
in the SC UniPad text editor, distributed by Sharmahd Computing (visit <
http://www.unipad.org> for more information).

SCSU works by defining 128-byte "windows" into the Unicode code space and 
using two slightly different mechanisms ("locking" and "non-locking") to 
refer to code points in those windows.  SCSU is intentionally a very 
lightweight solution, and does not depend on large tables of the sort 
required by the normalization forms or the proposed reordering scheme.  In 
particular, no reordering takes place in SCSU; code point order within each 
128-byte window is strictly adhered to.

Other forms of compression are unlikely to be of much interest to the UTC, 
which acknowledges that heavier-weight or application-specific compression 
schemes belong to the expertise of compression specialists or application 
vendors.

>  But of course, this discussion is not for IDN WG.

This is true, so I will not pursue it further on the IDN list.

Apologies to the Unicode list if this thread was inappropriate for 
cross-posting.

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Mon Oct 22 01:12:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23289
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 01:12:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vXF0-0009rE-00
	for idn-data@psg.com; Sun, 21 Oct 2001 22:03:10 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vXEz-0009qN-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 22:03:09 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 9DF077F498; Mon, 22 Oct 2001 14:02:51 +0900 (JST)
Message-Id: <4.2.0.58.J.20011022114110.03708b00@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Mon, 22 Oct 2001 11:45:32 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Re: REORDERING: stability issues and UTC solutions
In-Reply-To: <002a01c15a98$44d0ada0$ec1bd9d2@temp>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <024b01c15847$11e8b430$0501000a@jamessonyvaio>
 <4.2.0.58.J.20011019152610.037f1100@localhost>
 <4.2.0.58.J.20011019181604.0312ad90@localhost>
 <022601c15889$020aa360$ec1bd9d2@temp>
 <007e01c158c3$e2f41ac0$0601000a@jamessonyvaio>
 <00cb01c15a36$ca8c4a10$ec1bd9d2@temp>
 <004201c15a3b$e0420d40$0e01000a@jamessonyvaio>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 10:24 01/10/22 +0900, Soobok Lee wrote:
>We have no TAGALOG characters X,Y now.
>After we finalized nameprep/ACE,
>TAGALOG script may be added to Unicode.
>Then,
>
> > My  question was that:
> >   1) newly-approved TAGALOG characters X,Y  have   NFC X -> Y,
> >   2) old Nameprep/ACE encodes X.com and Y.com as two distinct ACE labels,
>
>unassingned code points are allowed in query from old version nameprep.
>X.com Y.com are passed through into DNS servers which have no stored tagalog
>labels before TAGALOG is added, but begin to accept it after it's approved 
>& added.

That makes a lot of sense. Or do you want to say it doesn't.



> >       because it don't know about NFC X -> Y
> >   3) new Nameprep/ACE encodes X.com as the the same ACE label as
> >       Y.com's       with NFC  X -> Y.
> >
> > >   If X.com and Y.com are taken by two distinct registrants, there will
> > >     be a mess. of course, it should have be blocked by careful
> > registries.
> > >   Even if new ACE libaries are distributed, some old ACE tools will
> > still
> > >     try to send X.com dns queries which may fail.
> >
>this case is described in stringprep-00, section 6.3 paragraph 3.
>that query should fail. Old nameprep/ACE applications should send
>Y.com instead of X.com even when it gets native X.com from html page
>(human input should contain only Y.com, not X.com).

Well, it shouldn't get X.com from the webpage, because the
web page should also be normalized. Please see
http://www.w3.org/TR/charmod :-).

Regards,   Martin.





From owner-idn@ops.ietf.org  Mon Oct 22 01:13:06 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23308
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 01:13:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vXEw-0009qf-00
	for idn-data@psg.com; Sun, 21 Oct 2001 22:03:06 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vXEv-0009qQ-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 22:03:05 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id A33A27F4D7; Mon, 22 Oct 2001 14:02:53 +0900 (JST)
Message-Id: <4.2.0.58.J.20011022120125.02cf97d0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Mon, 22 Oct 2001 12:11:56 +0900
To: "Soobok Lee" <lsb@postel.co.kr>,
        "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
In-Reply-To: <001101c159d1$cffce960$ec1bd9d2@temp>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <024b01c15847$11e8b430$0501000a@jamessonyvaio>
 <4.2.0.58.J.20011019160708.037cccd0@localhost>
 <017b01c15879$99dc8e20$ec1bd9d2@temp>
 <3BD0D662.6428B3C2@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 10:43 01/10/21 +0900, Soobok Lee wrote:

>From: "David Hopwood" <david.hopwood@zetnet.co.uk>

> > ?? Unless I'm very confused about Hangul, it is at least as much
> > phonetically-based as Latin. Hangul Jamo are letters of an alphabet,
> > which happen to be arranged in square cells corresponding to syllables,
> > instead of linearly.
>
>You are only partly correct in that Hangul is phonetic.
>
>If you ever read a hangul-to-hangul dictionary, you can find easily that
>over 70~80% of modern hangul vocabularies came from 1:1 mappings of
>Chinese words like  most english & french words  came from latin ones.
>Therefore, one hangul character carries similar amount of information
>with its chinese character counterparts.

First, the mappings are not 1:1. There are many Hanja that map to
the same Hangul (same pronunciation), and there are some Hanja
that have two or more pronunciations.

Second, the fact that much of Korean vocabulary (same for
Japanese) came from Chinese doesn't disprove that Hangul is
phonetic, in the same way as the fact that Much of English
or French came from the Latin language doesn't disprove that
the Latin script is phonetic.


>hangul/han both carries as much information  as  about 2 latins characters.

For han, Adam has shown that this easily can go up to 4.
By your arguments, this should be the same for Chinese-
origin Hangul. I would agree, and say that for names,
I expect a higher percentage of Chinese-origin Hangul
than for Korean running text.


Regards,   Martin.



From owner-idn@ops.ietf.org  Mon Oct 22 01:15:25 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23446
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 01:15:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vXEx-0009qt-00
	for idn-data@psg.com; Sun, 21 Oct 2001 22:03:07 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vXEw-0009qa-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 22:03:06 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 38F927F4D8; Mon, 22 Oct 2001 14:02:54 +0900 (JST)
Message-Id: <4.2.0.58.J.20011022121250.037081e0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Mon, 22 Oct 2001 12:23:26 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, <DougEwell2@cs.com>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
Cc: <jseng@pobox.org.sg>
In-Reply-To: <02c901c15899$809f7920$ec1bd9d2@temp>
References: <4.2.0.58.J.20011019155811.03d67490@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 21:27 01/10/19 +0900, Soobok Lee wrote:

>han/hangeul have huge lists of characters (20992/11172).
>To encode them, we need more digits and bits than latin letters.

It may be interesting to give some background information on
Hangul encoding in Unicode. In Unicode 1.0 and 1.1, only a
subset of the 11172 modern hangul syllables, 2000-3000
(taken from KS5601) were encoded, in the place where now
CJK Extension A is located. These represented the subset
of Hangul in actual practical use. However, at the request
of the Korean (ROK) national delegation to ISO/IEC JTC1
SC2/WG2, and after a long and painful discussions, these
codepoints were moved to the current location, and completed
in a regular fashion to the current 11172. A lot of reasons
were given at the time for having to make this change.
It was the only time at all that codepoints were moved,
and it resulted in very strong criticism (very much including
people from the IETF). The main benefit was that it made
the bodies involved understand how important stability is
to the users.

Anyway, if this change hadn't been done, all the frequent
Hangul would now be quite a bit closer together.

Regards,   Martin.


>That ACE encoding overhead is so big that it cannot be compensated by the 
>superiority in the information capacity of a han letter compared to a 
>latin letter. The sizes of Latin alphabets or variants do not exceed 30.
>
>In UCS-2, 2*N octets are need for latin/han lables of length N.
>But ACE/UTF8 which favor latin script, require roughly 3.0*N octets for 
>long han labels. REORDERING reduce those requirement into 2.2*N, close to 
>that of UCS-2.
>
>Soobok Lee




From owner-idn@ops.ietf.org  Mon Oct 22 01:15:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23500
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 01:15:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vXEx-0009qs-00
	for idn-data@psg.com; Sun, 21 Oct 2001 22:03:07 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vXEw-0009qd-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 22:03:06 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id E5B977F4D9; Mon, 22 Oct 2001 14:02:54 +0900 (JST)
Message-Id: <4.2.0.58.J.20011022122557.03774610@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Mon, 22 Oct 2001 12:28:35 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, <DougEwell2@cs.com>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
Cc: <jseng@pobox.org.sg>
In-Reply-To: <018f01c1587b$af216e70$ec1bd9d2@temp>
References: <15f.2876ee9.29011cc1@cs.com>
 <4.2.0.58.J.20011019162040.03c95df0@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 17:54 01/10/19 +0900, Soobok Lee wrote:

>Please read  2500-years-old chinese classic books, then you can
>find there has been no great change in frequent han characters.
>Really!!!

In some sense, there hasn't been much change. But there have
been very clear changes. The vocabulary has changed, and therefore
the more frequent and less frequent characters have changed.
Also, the introduction of simplified characters around 1950
has changed frequencies quite a bit; many of the simplified
characters are quite frequent but don't turn up in old texts.


Regards,  Martin.







From owner-idn@ops.ietf.org  Mon Oct 22 01:18:56 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23742
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 01:18:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vXF0-0009rF-00
	for idn-data@psg.com; Sun, 21 Oct 2001 22:03:10 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vXEz-0009qO-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 22:03:09 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 20D6E7F4A8; Mon, 22 Oct 2001 14:02:52 +0900 (JST)
Message-Id: <4.2.0.58.J.20011022114545.02c1ae70@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Mon, 22 Oct 2001 11:49:49 +0900
To: "Soobok Lee" <lsb@postel.co.kr>,
        "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
In-Reply-To: <022001c15888$27fc5790$ec1bd9d2@temp>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <024b01c15847$11e8b430$0501000a@jamessonyvaio>
 <4.2.0.58.J.20011019152610.037f1100@localhost>
 <4.2.0.58.J.20011019180625.038105d0@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 19:23 01/10/19 +0900, Soobok Lee wrote:
> > I didn't talk about unassigned code points.
> > What I mean is this: If you have two frequency tables,
> > and they differ by e.g. one forgetting a particular
> > character, then virtually all your compressed results
> > are different. If you have a wrong mapping in a
> > NFC or NFKC algorithm, then only that character is
> > affected.
>
>Never. The REORDERING table for a script has *NO*
>missing characters because it applies idempotent
>mappings for even unassigned code points.

What I meant is that e.g. somebody goes ahead and
implements reordering based on one of your tables.
Then e.g. the IETF includes reordering in IDN
(Don't misunderstand me, this is only an example,
of course I think this should never happen.), but
with a different table based on newer statistics.
The original implementer doesn't catch that he has
a different table, and as a result, we have total
chaos, nothing matches.

In comparison, if somebody by chance gets an old
NFC/KC table, a few labels won't match, but it won't
be a whole script or more that gets ruined.

Regards,   Martin.



From owner-idn@ops.ietf.org  Mon Oct 22 01:20:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23853
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 01:20:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vXEw-0009qc-00
	for idn-data@psg.com; Sun, 21 Oct 2001 22:03:06 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vXEv-0009qP-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 22:03:05 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 021427F4D3; Mon, 22 Oct 2001 14:02:53 +0900 (JST)
Message-Id: <4.2.0.58.J.20011022115559.0390cc70@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Mon, 22 Oct 2001 12:01:10 +0900
To: "Adam M. Costello" <amc+5nb0vi@nicemice.net>,
        IETF idn working group <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Re: hi
In-Reply-To: <E15v7Sl-000LZE-00@psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hello Adam,

At 18:31 01/10/20 -0700, Adam M. Costello wrote:

>The situation is much worse for Korean.  I think each Hangul character
>carries the information of only about 1.5 English letters,

It may be lower than Chinese, but I'm very surprised it should
be that low. Any pointers to sources? Are they for running text,
or for names? For running text, Korean uses spaces, but Chinese
doesn't, so that already could explain quite a bit of the
difference.


>but still
>takes about 2.9 octets in AMC-ACE-Z, which means a maximal Korean domain
>label (20 hangul) holds about as much information as a 30-letter English
>string.  Of all the languages I've looked at, Korean is by far the least
>dense when encoded using AMC-ACE-Z.

Even if this were true, a 30-letter limit in English would still be
nothing really bad in actual practice.

Regards,   Martin.



From owner-idn@ops.ietf.org  Mon Oct 22 01:40:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25061
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 01:40:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vXgQ-000Axq-00
	for idn-data@psg.com; Sun, 21 Oct 2001 22:31:30 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vXgP-000Axk-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 22:31:29 -0700
Received: from [192.168.1.5] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id HAA14141;
	Mon, 22 Oct 2001 07:30:47 +0200 (MET DST)
Date: Mon, 22 Oct 2001 07:29:57 +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] Re: REORDERING: stability issues and UTC solutions
Message-ID: <1979815.1003735797@localhost>
In-Reply-To: <4.2.0.58.J.20011022114110.03708b00@localhost>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <024b01c15847$11e8b430$0501000a@jamessonyvaio>
 <4.2.0.58.J.20011019152610.037f1100@localhost>
 <4.2.0.58.J.20011019181604.0312ad90@localhost>
 <022601c15889$020aa360$ec1bd9d2@temp>
 <007e01c158c3$e2f41ac0$0601000a@jamessonyvaio>
 <00cb01c15a36$ca8c4a10$ec1bd9d2@temp>
 <004201c15a3b$e0420d40$0e01000a@jamessonyvaio>
 <4.2.0.58.J.20011022114110.03708b00@localhost>
X-Mailer: Mulberry/2.1.0 (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 2001-10-22 11.45 +0900 Martin Duerst <duerst@w3.org> wrote:

>> > My  question was that:
>> >   1) newly-approved TAGALOG characters X,Y  have   NFC X -> Y,
>> >   2) old Nameprep/ACE encodes X.com and Y.com as two distinct ACE
>> >   labels,
>> 
>> unassingned code points are allowed in query from old version nameprep.
>> X.com Y.com are passed through into DNS servers which have no stored
>> tagalog labels before TAGALOG is added, but begin to accept it after
>> it's approved  & added.
> 
> That makes a lot of sense. Or do you want to say it doesn't.

I would appreciate if discussions on versioning uses the terminology etc
which is already established in earlier versions of the nameprep document,
and now moved to section 6 of draft-hoffman-stringprep-00.txt.

I especially see an embryo of reinvention of an already in this wg
established way of handling unassigned codepoints.

That this is handled the correct way is especially important as that
section of the stringprep/nameprep algorithm is in accordance with
agreements between IETF and UTC on how additional codepoints are assigned.

  paf




From owner-idn@ops.ietf.org  Mon Oct 22 02:10:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04858
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 02:10:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vY5g-000BgY-00
	for idn-data@psg.com; Sun, 21 Oct 2001 22:57:36 -0700
Received: from mail.fm-net.ne.jp ([211.15.66.133])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vY5f-000BgN-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 22:57:35 -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 OAA26753
	for <idn@ops.ietf.org>; Mon, 22 Oct 2001 14:57:32 +0900
Message-ID: <1c6001c15abe$3f442080$a3420fd3@bruce>
From: "Bruce Thomson" <bthomson@fm-net.ne.jp>
To: <idn@ops.ietf.org>
References: <4.2.0.58.J.20011022115559.0390cc70@localhost>
Subject: Re: [idn] Re: hi
Date: Mon, 22 Oct 2001 14:56:09 +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

Some Hangul characters are equivalent to only one English vowel,
but most are equivalent to one consonant and one vowel (like
Japanese kana). In addition there many are equivalent to 2 consonants
and 1 vowel so Hangul are more efficient than kana. Perhaps
2.2 English letters per Hangul character at a guess? Also
remember that Kanji are used together with Hangul, which tends
to increase that number.

Bruce

----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "Adam M. Costello" <amc+5nb0vi@nicemice.net>; "IETF idn working group" <idn@ops.ietf.org>
Sent: Monday, October 22, 2001 12:01 PM
Subject: Re: [idn] Re: hi


> Hello Adam,
> 
> At 18:31 01/10/20 -0700, Adam M. Costello wrote:
> 
> >The situation is much worse for Korean.  I think each Hangul character
> >carries the information of only about 1.5 English letters,
> 
> It may be lower than Chinese, but I'm very surprised it should
> be that low. Any pointers to sources? Are they for running text,
> or for names? For running text, Korean uses spaces, but Chinese
> doesn't, so that already could explain quite a bit of the
> difference.
> 
> 
> >but still
> >takes about 2.9 octets in AMC-ACE-Z, which means a maximal Korean domain
> >label (20 hangul) holds about as much information as a 30-letter English
> >string.  Of all the languages I've looked at, Korean is by far the least
> >dense when encoded using AMC-ACE-Z.
> 
> Even if this were true, a 30-letter limit in English would still be
> nothing really bad in actual practice.
> 
> Regards,   Martin.
> 
> 




From owner-idn@ops.ietf.org  Mon Oct 22 02:13:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23501
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 01:15:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vXEy-0009r1-00
	for idn-data@psg.com; Sun, 21 Oct 2001 22:03:08 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vXEx-0009qr-00
	for idn@ops.ietf.org; Sun, 21 Oct 2001 22:03:07 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id B871B7F4DB; Mon, 22 Oct 2001 14:02:55 +0900 (JST)
Message-Id: <4.2.0.58.J.20011022123314.03774340@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Mon, 22 Oct 2001 12:35:52 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
In-Reply-To: <02e901c1589e$c1377a00$ec1bd9d2@temp>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <024b01c15847$11e8b430$0501000a@jamessonyvaio>
 <4.2.0.58.J.20011019160708.037cccd0@localhost>
 <4.2.0.58.J.20011019174908.03d8c360@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 22:05 01/10/19 +0900, Soobok Lee wrote:

> > And just using first order frequency
> > to bring the most frequent characters to the front may
> > not be the most efficient way for compression.
> >
>
>Do you a good idea that can replace current first-order frequency reordering ?
>Welcome any changes to that.

Well, just for the record, if a script is used with two languages,
there are some characters used in both, others used only in one
language, and still others only used in the other, then it may
be better to arrange them to first have those characters used
in one language only, then those used in both, and then those
used only in the other language.

Although 'language' is not the right term, that would very clearly
apply to TC/SC.


Regards,   Martin.
  



From owner-idn@ops.ietf.org  Mon Oct 22 07:11:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10753
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 07:11:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vcgq-000KJm-00
	for idn-data@psg.com; Mon, 22 Oct 2001 03:52:16 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vcgo-000KJg-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 03:52:15 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id TAA11993;
	Mon, 22 Oct 2001 19:52:03 +0900
Message-ID: <004e01c15ae7$ba4761b0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <4.2.0.58.J.20011019152610.037f1100@localhost> <4.2.0.58.J.20011019180625.038105d0@localhost> <4.2.0.58.J.20011022114545.02c1ae70@localhost>
Subject: Re: [idn] call for comments for REORDERING
Date: Mon, 22 Oct 2001 19:53:03 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA10753


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
 > What I meant is that e.g. somebody goes ahead and
> implements reordering based on one of your tables.
> Then e.g. the IETF includes reordering in IDN
> (Don't misunderstand me, this is only an example,
> of course I think this should never happen.), but
> with a different table based on newer statistics.
> The original implementer doesn't catch that he has
> a different table, and as a result, we have total
> chaos, nothing matches.

But newer reordering table with newer statistics
cannot be deployed without new ACE PREFIX, as i said many times.

But current nameprep rules out the possibility of
newer PREFIX. Therefore, newer reordering table would not
occur until this objection to future new prefix is
un-freezed and lifted up by IETF.

With new prefix, there won't occur any confusion problems you raised
regarding to REORDERING.

Soobok Lee

> 
> In comparison, if somebody by chance gets an old
> NFC/KC table, a few labels won't match, but it won't
> be a whole script or more that gets ruined.
> 
> Regards,   Martin.
> 




From owner-idn@ops.ietf.org  Mon Oct 22 07:38:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11444
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 07:38:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vdBe-000LC6-00
	for idn-data@psg.com; Mon, 22 Oct 2001 04:24:06 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vdBd-000LBm-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 04:24:05 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id UAA21926;
	Mon, 22 Oct 2001 20:23:48 +0900
Message-ID: <006e01c15aec$2a367c00$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <DougEwell2@cs.com>, <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <4.2.0.58.J.20011019155811.03d67490@localhost> <4.2.0.58.J.20011022121250.037081e0@localhost>
Subject: Re: [idn] call for comments for REORDERING
Date: Mon, 22 Oct 2001 20:24:48 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA11444


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; <DougEwell2@cs.com>; <idn@ops.ietf.org>
Cc: <jseng@pobox.org.sg>
Sent: Monday, October 22, 2001 12:23 PM
Subject: Re: [idn] call for comments for REORDERING


> At 21:27 01/10/19 +0900, Soobok Lee wrote:
> 
> >han/hangeul have huge lists of characters (20992/11172).
> >To encode them, we need more digits and bits than latin letters.
> 
> It may be interesting to give some background information on
> Hangul encoding in Unicode. In Unicode 1.0 and 1.1, only a
> subset of the 11172 modern hangul syllables, 2000-3000
> (taken from KS5601) were encoded, in the place where now
> CJK Extension A is located. These represented the subset
> of Hangul in actual practical use. However, at the request
> of the Korean (ROK) national delegation to ISO/IEC JTC1
> SC2/WG2, and after a long and painful discussions, these
> codepoints were moved to the current location, and completed
> in a regular fashion to the current 11172. A lot of reasons
> were given at the time for having to make this change.
> It was the only time at all that codepoints were moved,
> and it resulted in very strong criticism (very much including
> people from the IETF). The main benefit was that it made
> the bodies involved understand how important stability is
> to the users.

Thanks for detailed history of Hangul in unicode.
But including 11172 hangul made Unicode more useful and 
widely acceptable to korean community, because existing 
KS5601's 2350 or more hangul has been criticized for not being
able to serve many scholarly purpose or book publishings.

The pain for inclufing 11172 hangul  was REWARDED!

I know current NFC/NFKC has *severely flawed* hangul jamo handling behaviors
that was put into UTR15 because of lack of careful reviews by both
Koreans represenatives and UTC members.
This pain was not from including 11172, but from careless reviewers.

I hope UTC cures this BUGGY NFC/NFKC jamo handling as an exceptional case
while it is in  strict adherence to UTR's backward compatiblity policy & promise.

Soobok Lee

> 
> Anyway, if this change hadn't been done, all the frequent
> Hangul would now be quite a bit closer together.
> 
> Regards,   Martin.
> 
> 
> >That ACE encoding overhead is so big that it cannot be compensated by the 
> >superiority in the information capacity of a han letter compared to a 
> >latin letter. The sizes of Latin alphabets or variants do not exceed 30.
> >
> >In UCS-2, 2*N octets are need for latin/han lables of length N.
> >But ACE/UTF8 which favor latin script, require roughly 3.0*N octets for 
> >long han labels. REORDERING reduce those requirement into 2.2*N, close to 
> >that of UCS-2.
> >
> >Soobok Lee
> 
> 




From owner-idn@ops.ietf.org  Mon Oct 22 09:53:22 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16905
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 09:53:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vfJC-000Oxx-00
	for idn-data@psg.com; Mon, 22 Oct 2001 06:40:02 -0700
Received: from smtp21.singnet.com.sg ([165.21.101.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vfJB-000Oxi-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 06:40:01 -0700
Received: from jamessonyvaio ([165.21.104.247])
	by smtp21.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9MDerp19152;
	Mon, 22 Oct 2001 21:40:53 +0800
Message-ID: <006b01c15aff$07348f90$1101000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <4.2.0.58.J.20011019152610.037f1100@localhost> <4.2.0.58.J.20011019180625.038105d0@localhost> <4.2.0.58.J.20011022114545.02c1ae70@localhost> <004e01c15ae7$ba4761b0$ec1bd9d2@temp>
Subject: Re: [idn] call for comments for REORDERING
Date: Mon, 22 Oct 2001 21:39:50 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Wait wait..new prefix??

You are going down a path whereby a *single* domain name may have *X*
number of ACE, each one with a different prefix, depending on the
version number of re-ordering & nameprep. Great, please explain how the
client going to do matching with different version, or client & server
without some form of communication?

No, going to multiple prefix is a BAD *BAD* **BAD** *B*A*D* idea. Lets
not even go there.

-James Seng

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>; "Martin Duerst" <duerst@w3.org>
Sent: Monday, October 22, 2001 6:53 PM
Subject: Re: [idn] call for comments for REORDERING



----- Original Message -----
From: "Martin Duerst" <duerst@w3.org>
 > What I meant is that e.g. somebody goes ahead and
> implements reordering based on one of your tables.
> Then e.g. the IETF includes reordering in IDN
> (Don't misunderstand me, this is only an example,
> of course I think this should never happen.), but
> with a different table based on newer statistics.
> The original implementer doesn't catch that he has
> a different table, and as a result, we have total
> chaos, nothing matches.

But newer reordering table with newer statistics
cannot be deployed without new ACE PREFIX, as i said many times.

But current nameprep rules out the possibility of
newer PREFIX. Therefore, newer reordering table would not
occur until this objection to future new prefix is
un-freezed and lifted up by IETF.

With new prefix, there won't occur any confusion problems you raised
regarding to REORDERING.

Soobok Lee

>
> In comparison, if somebody by chance gets an old
> NFC/KC table, a few labels won't match, but it won't
> be a whole script or more that gets ruined.
>
> Regards,   Martin.
>






From owner-idn@ops.ietf.org  Mon Oct 22 10:23:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18248
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 10:23:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vfnt-000PuY-00
	for idn-data@psg.com; Mon, 22 Oct 2001 07:11:45 -0700
Received: from mercury.sun.com ([192.9.25.1])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vfnt-000PuS-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 07:11:45 -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 HAB19295
	for <idn@ops.ietf.org>; Mon, 22 Oct 2001 07:11:42 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f9MEBeq16246;
	Mon, 22 Oct 2001 16:11:40 +0200 (MET DST)
Date: Mon, 22 Oct 2001 16:06:10 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: [idn] Which lanuages/scripts to reorder?
To: idn@ops.ietf.org
Cc: Erik.Nordmark@eng.sun.com
Message-ID: <Roam.SIMC.2.0.6.1003759570.7596.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


One issue with reordering that hasn't been put on the table
is that, as a process, I'm concerned that it might never complete.
This concern is in addition to the other concerns I've seen expressed on
the list.

Suppose that we start of defining a reordering scheme that allows for
longer labels for some set of languages/scripts.
Suppose this gets tested etc. and finished in the WG.
Duing IETF last call somebody objects that their favorite language/script
doesn't get the same benefits. What happens?

If we have accepted to do reordering for some languages/scripts what technical
argument do we have for saying "no" to any particular language/script?

In worst case the above can repeat over and over - each new attempt at
improving the maximum length labels for some subset of the worlds
languages/scripts can result in requests to add yet another language/script
to the set that needs to be supported.

Thus as far as I can tell embarking on solving reording as a pre-cursor to
getting IDN specified and usable, might result in delaying IDN for an
undetermined amount of time.

   Erik




From owner-idn@ops.ietf.org  Mon Oct 22 11:28:15 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19936
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 11:28:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vgWg-00015Z-00
	for idn-data@psg.com; Mon, 22 Oct 2001 07:58: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.33 #1)
	id 15vgWf-00015O-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 07:58:01 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9MEwPr29892;
	Mon, 22 Oct 2001 10:58:25 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110221458.f9MEwPr29892@nic-naa.net>
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Which lanuages/scripts to reorder? 
In-Reply-To: Your message of "Mon, 22 Oct 2001 16:06:10 +0200."
             <Roam.SIMC.2.0.6.1003759570.7596.nordmark@bebop.france> 
Date: Mon, 22 Oct 2001 10:58:25 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Erik,

The process, if any, of future revision of thie WG's product, again, if any,
is important. Either there is none, and it is "permanent" until discarded,
or there is some, which may work (allowing semi-graceful revisioning).

We have the assertion that reordering (blocks of the UTC's product) is useful
for labels composed in a well-defined range of code-points (aka "Chinese").

We have the assertion that the UTC's product is incomplete.

Both appear to be correct.

One possible course of action is to discard the first assertion (utility for
labels using Chinese characters), until the second assertion is false.

One possible course of action is to accept the first assertion, while the
second assertion remains true.

It is my view that the second course of action is the better of the two.

Eric



From owner-idn@ops.ietf.org  Mon Oct 22 12:08:21 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21444
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 12:08:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vhCF-0002aR-00
	for idn-data@psg.com; Mon, 22 Oct 2001 08:40:59 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vhCE-0002aK-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 08:40:58 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id AAA04156;
	Tue, 23 Oct 2001 00:40:21 +0900
Message-ID: <001801c15b10$01148190$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <DougEwell2@cs.com>, <idn@ops.ietf.org>
References: <18.1420a617.2904e961@cs.com>
Subject: Re: [idn] Re: REORDERING: stability issues and UTC solutions
Date: Tue, 23 Oct 2001 00:41:23 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA21444


----- Original Message ----- 
From: <DougEwell2@cs.com>
 > It might be a good idea to peruse these resources and verify for oneself that 
> they do not contain any characters that are compatibility forms of other 
> characters or combinations of characters.  Of course, nobody can predict the 
> future with 100% accuracy but there are lots of good hints that the scenario 
> "newly-approved 'S' characters X,Y  have   NFC X -> Y" for any script 'S' is 
> simply not ever going to happen.
> 
 
Instead of NFC, some script may need CASE mappings, i guess.
Current nameprep/ACE produce case-insensitively equivalent labels
for IDN  X.com and x.com.
Do you mean that all newly added SCRIPT won't have any case mapping ?

Doug, 
If you have lists of new scripts pending for approval,
please post them to this list for non-unicode experts.

Soobok Lee





From owner-idn@ops.ietf.org  Mon Oct 22 13:33:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24526
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 13:33:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15viYE-0004nF-00
	for idn-data@psg.com; Mon, 22 Oct 2001 10:07:46 -0700
Received: from mail-gw.im.se ([193.14.22.222])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15viYD-0004n9-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 10:07:45 -0700
Received: from msxsth3.im.se (msxsth3.im.se [193.14.16.192])
	by mail-gw.im.se (8.11.0/8.11.3) with ESMTP id f9MGx8M33082
	for <idn@ops.ietf.org>; Mon, 22 Oct 2001 18:59:08 +0200
Received: by msxsth3.im.se with Internet Mail Service (5.5.2653.19)
	id <VDBPFGYZ>; Mon, 22 Oct 2001 19:10:02 +0200
Message-ID: <C110A2268F8DD111AA1A00805F85E58D0115ACBC@ntgbg1>
From: Karlsson Kent - keka <keka@im.se>
To: idn@ops.ietf.org
Cc: Martin Duerst <duerst@w3.org>, DougEwell2@cs.com,
        "'Soobok Lee'"
	 <lsb@postel.co.kr>
Subject: RE: [idn] call for comments for REORDERING
Date: Mon, 22 Oct 2001 19:05:56 +0200
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



> -----Original Message-----
> From: Soobok Lee [mailto:lsb@postel.co.kr]
...
> But including 11172 hangul made Unicode more useful and 
> widely acceptable to korean community, because existing 
> KS5601's 2350 or more hangul has been criticized for not being
> able to serve many scholarly purpose or book publishings.
> 
> The pain for inclufing 11172 hangul  was REWARDED!

And still it is not sufficient, since historic Hangul
Jamo aren't covered by the precomposed Hangul syllable
characters. I have also indications that many useful
consonant (and vowel?) clusters aren't covered as separate
(Jamo) characters, but have to be constructed from multiple
'more basic' (non-cluster) Hangu Jamo characters. (The
cluster ones are the ones that had compatibility
decompositions in Unicode 2.0, but don't have such
decompositions in Unicode 3.0.)

> I know current NFC/NFKC has *severely flawed* hangul jamo 

Now that's a new complaint.  At least to me.  Not even the
delegations from DPRK complain about that. (And they have
all sorts of complaints.)  Do you care to say a little bit
more about what you mean?  Or are we just to take your word
for it?  There was a problem in earlier drafts of UAX 15
concerning Hangul and NFKC (Hangul syllables were not preserved),
but that problem was removed before that UTR became a UAX.

> I hope UTC cures this BUGGY NFC/NFKC jamo handling as an 
> exceptional case while it is in  strict adherence to UTR's backward 
> compatiblity policy & promise.

The normal forms for strings of already allocated characters
will not be changed any more.

		Kind regards
		/Kent K



From owner-idn@ops.ietf.org  Mon Oct 22 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 ESMTP id OAA26542
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 14:33:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vjW5-0005zX-00
	for idn-data@psg.com; Mon, 22 Oct 2001 11:09:37 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vjW4-0005zM-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 11:09:37 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id DAA17552;
	Tue, 23 Oct 2001 03:09:20 +0900
Message-ID: <003a01c15b24$d16f3100$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
Cc: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        "Paul Hoffman / IMC" <phoffman@imc.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <4.2.0.58.J.20011019152610.037f1100@localhost> <4.2.0.58.J.20011019180625.038105d0@localhost> <4.2.0.58.J.20011022114545.02c1ae70@localhost> <004e01c15ae7$ba4761b0$ec1bd9d2@temp> <006b01c15aff$07348f90$1101000a@jamessonyvaio>
Subject: [idn] suggestion: two prefices scheme for unassigned code points treatments.
Date: Tue, 23 Oct 2001 03:10:15 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA26542


----- Original Message ----- 
From: "James Seng/Personal" <jseng@pobox.org.sg>

> Wait wait..new prefix??
> 
> You are going down a path whereby a *single* domain name may have *X*
> number of ACE, 

Yes,it may happen, but  only if we do it loosely.

To treat unassigned code points more consistenly and safely 
through out  all nameprep upgrade paths with/without reordering,
i propose the next new prefixing scheme with two prefices: uq-- and zq--.


Let's assume we adopt "zq--" prefix for valid ACE labels.
I suggest we use another "uq--" prefix for invalid ACE labels which contains at least one unassigned code point at one time. When the unassigned code points become *defined* later, new nameprep/ACE libraries may encode them using "zq--", no more with "uq--". Then we could devise some fallback mechanims on all "uq--????" labels coming from old nameprep/ACE   in application sides  receiving the uq-- labels.

all 'zq--????' labels can be trusted if registries
are careful enough to enforce the integrity.

All "uq--????" labels should not be trusted and all application/dns servers should
have some fallback/warning mechanisms form them. 

Case 1) a newly assigned code point don't have any NFC/NFKC/Case mapping:
Then, the native label containing it would be ACE-encoded into :
"uq--abcd" from old nameprep/ACE, and 
"zq--efgh" from new nameprep/ACE.
then  the authoritative dns server  for the native label,
of course, sets "uq--abcd"  to be an alias to the other "zq--efgh".
 
Case 2) a newly assigned code point is mapped into other code point by one
of NFC/NFKC/CaseMapping ( X->Y ):
Then the native label would have related three different ACE labels:
"uq--abcd" from old nameprep/ACE for X and 
"uq--ijkl" from old nameprep/ACE for Y and 
"zq--mnop" from new nameprep/ACE for Y.
then  the authoritative dns server  for the native label, should
set "uq--abcd" and "uq--ijkl" to be  aliases to the right "zq--mnop".
The number of such aliased labels would be combinatorically multiplied 
if the native label contains more than 1 mapped characters.

no dns server upgrade is needed. additional zone adminstration is enough.

But, the applications should issue warnings for all occurrences of "uq--xxxx" for security reasons, because all old(out-dated) online/offline-mode applications may fail to match "uq--abcd" and "uq--ijkl" and "zq--mnop" in Case 2) which should be regards as equal.
 
certificate authories should not issue website/email
certificates applied with identity information containing "uq--abcd".
Applicants should be warned to retry with upgraded software to 
generate their new email/website ACE addresses with "zq--" prefix.

If old email clients receives senders' addresses with "uq--",
then they should give warnings to end users that something dangerous
string may be in it. If the email clients is upgraded to know both old and new nameprep, the uq-- label is decoded into native label and then re-encoded into zq--
label with new nameprep/ACE and can try successful comparisons!!!
This may be the unique feature that  cannot be provided by current nameprep
versioning scheme.

Without this  "two prefices scheme", online/offline applications ( dns servers  are
adminstrated by intelligent and careful zone masters) may not know
whether "zq--????" labels are from dangerous old nameprep or new nameprep, and
don't know whether "zq--????" is equal to "uq--????" from old nameprep/ACE.

These new prefixing scheme ,of course, cannot be used to correct false NFC/NFKC.
But it provide more security.

Moreover,it may used to incorporate new reordering tables for newly approved scripts/newly assigned code points  even with single "zq--" prefix, whenever the native labels contain at least one of previously-unassigned-but-now-added code block for which we can make new-statitiscs-backed new reordering tables that cover only the code ranges consisting of the new added code points. Old reordering tables don't touch the unassigned code points. There  will be no collision because new zq-- labels will be unique in that old zq-- labels don't contain new code points. "uq--" has no reordering support for unassigned code points, only "zq--" does. "uq--" labels are always unique, too.

halfbaked idea. welcome any corrections and suggestions.

Soobok Lee

> each one with a different prefix, depending on the
> version number of re-ordering & nameprep. Great, please explain how the
> client going to do matching with different version, or client & server
> without some form of communication?
> 
> 
> -James Seng





From owner-idn@ops.ietf.org  Mon Oct 22 15:00:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27149
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 15:00:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vjzX-0006Xo-00
	for idn-data@psg.com; Mon, 22 Oct 2001 11:40:03 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vjzW-0006XM-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 11:40:02 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id DAA26973;
	Tue, 23 Oct 2001 03:39:45 +0900
Message-ID: <004901c15b29$0c552d20$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Karlsson Kent - keka" <keka@im.se>, <idn@ops.ietf.org>
Cc: "Martin Duerst" <duerst@w3.org>, <DougEwell2@cs.com>
References: <C110A2268F8DD111AA1A00805F85E58D0115ACBC@ntgbg1>
Subject: Re: [idn] call for comments for REORDERING
Date: Tue, 23 Oct 2001 03:40:39 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA27149


----- Original Message ----- 
From: "Karlsson Kent - keka" <keka@im.se>
> 
> > I know current NFC/NFKC has *severely flawed* hangul jamo 
> 
> Now that's a new complaint.  At least to me.  Not even the
> delegations from DPRK complain about that. (And they have
> all sorts of complaints.)  Do you care to say a little bit
> more about what you mean?  Or are we just to take your word
> for it?  There was a problem in earlier drafts of UAX 15
> concerning Hangul and NFKC (Hangul syllables were not preserved),
> but that problem was removed before that UTR became a UAX.

two problems:

 1) NFKC maps   compatibility hangul jamo (U+32??) into
                conjoining hangul jamo without fillers.
    That converts compat hangul jamo sequences into conjoining
      jamo sequences and they are combined partially in some cases
        by the NFC following  compatibilty decomposition.
    Modern hangul informal texts contains compatibiilty jamos very often.
    If the texts contains choseong + jungseong sequence in compat jamo,
       they will be affected by this fault.
    This fault was found by Soobok Lee, too lately.

 2) NFC  does not combine  archaic(old) hangul trailing jamo into the
     preceding half-combined syllable (from choseong jamo + jungseong jamo),
      but leave it alone as an isolated conjoining jamo.
    That means archail hangul syllable which has old hangul trailing jamo 
      cannot be preserved through out NFKC.
    NFKC cannot be used for scholarly texts which contains archail hangul 
      syllables.  This fault was found by Martin, too lately.
    
Mark and Martin knew and told me why this happened.
Martin, would you comment on this?

Soobok Lee


> 
> > I hope UTC cures this BUGGY NFC/NFKC jamo handling as an 
> > exceptional case while it is in  strict adherence to UTR's backward 
> > compatiblity policy & promise.
> 
> The normal forms for strings of already allocated characters
> will not be changed any more.
> 
> Kind regards
> /Kent K
> 




From owner-idn@ops.ietf.org  Mon Oct 22 15:30:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27779
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 15:30:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vkVv-0007NO-00
	for idn-data@psg.com; Mon, 22 Oct 2001 12:13:31 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vkVu-0007NH-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 12:13:30 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id EAA04906;
	Tue, 23 Oct 2001 04:13:23 +0900
Message-ID: <005d01c15b2d$bfacbfb0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>, <idn@ops.ietf.org>
Cc: <Erik.Nordmark@eng.sun.com>
References: <Roam.SIMC.2.0.6.1003759570.7596.nordmark@bebop.france>
Subject: Re: [idn] Which lanuages/scripts to reorder?
Date: Tue, 23 Oct 2001 04:14:18 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA27779

Hi, Erik

I answered for your concerns on reordering supports for new scripts 
in the new postings  titled with
"idn] suggestion: two prefices scheme for unassigned code points treatments.".

I will answer for your other concerns later time.

Thanks.

Soobok Lee

----- Original Message ----- 
From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
To: <idn@ops.ietf.org>
Cc: <Erik.Nordmark@eng.sun.com>
Sent: Monday, October 22, 2001 11:06 PM
Subject: [idn] Which lanuages/scripts to reorder?


> 
> One issue with reordering that hasn't been put on the table
> is that, as a process, I'm concerned that it might never complete.
> This concern is in addition to the other concerns I've seen expressed on
> the list.
> 
> Suppose that we start of defining a reordering scheme that allows for
> longer labels for some set of languages/scripts.
> Suppose this gets tested etc. and finished in the WG.
> Duing IETF last call somebody objects that their favorite language/script
> doesn't get the same benefits. What happens?
> 
> If we have accepted to do reordering for some languages/scripts what technical
> argument do we have for saying "no" to any particular language/script?
> 
> In worst case the above can repeat over and over - each new attempt at
> improving the maximum length labels for some subset of the worlds
> languages/scripts can result in requests to add yet another language/script
> to the set that needs to be supported.
> 
> Thus as far as I can tell embarking on solving reording as a pre-cursor to
> getting IDN specified and usable, might result in delaying IDN for an
> undetermined amount of time.
> 
>    Erik
> 
> 




From owner-idn@ops.ietf.org  Mon Oct 22 16:22:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29108
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 16:22:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vlMN-0008w2-00
	for idn-data@psg.com; Mon, 22 Oct 2001 13:07:43 -0700
Received: from patan.sun.com ([192.18.98.43])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vlMM-0008vw-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 13:07:42 -0700
Received: from bebop.France.Sun.COM ([129.157.174.15])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA02275;
	Mon, 22 Oct 2001 14:07:15 -0600 (MDT)
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 f9MK7Zq22833;
	Mon, 22 Oct 2001 22:07:36 +0200 (MET DST)
Date: Mon, 22 Oct 2001 22:01:58 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [idn] Which lanuages/scripts to reorder? 
To: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>, idn@ops.ietf.org
In-Reply-To: "Your message with ID" <200110221458.f9MEwPr29892@nic-naa.net>
Message-ID: <Roam.SIMC.2.0.6.1003780918.20410.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


Eric, 

> The process, if any, of future revision of thie WG's product, again, if any,
> is important. Either there is none, and it is "permanent" until discarded,
> or there is some, which may work (allowing semi-graceful revisioning).

This is assuming that the WG actually produces something.
My concern in the area of reordering is that incremental requests for
supporting additional laguages/scripts for reordering benefits might mean
that the WG never gets to deliver anything - there are just too many
scripts/languages that can appear.

Thus my concern is completely unrelated to the version issues
others have brought up with respect to UTC.

If the WG embarks on doing reordering for 1,2,3,4 languages/scripts
how do we know that this will be sufficient? Next month there might be
requests for a few more languages/scripts. Etc.

  Erik




From owner-idn@ops.ietf.org  Mon Oct 22 17:13:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29917
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 17:13:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vm66-000AMA-00
	for idn-data@psg.com; Mon, 22 Oct 2001 13:54: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.33 #1)
	id 15vm65-000AM4-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 13:54:57 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9MKt2N05355;
	Mon, 22 Oct 2001 16:55:02 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110222055.f9MKt2N05355@nic-naa.net>
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
cc: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Which lanuages/scripts to reorder? 
In-Reply-To: Your message of "Mon, 22 Oct 2001 22:01:58 +0200."
             <Roam.SIMC.2.0.6.1003780918.20410.nordmark@bebop.france> 
Date: Mon, 22 Oct 2001 16:55:02 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Erik,

It is an assumption that this WG will actually produce something, which is
why "if any" appears twice in the first line of my remarks.

I appreciate the concern you expressed. I also appreciate that the question
"is IDNA/Nameprep/ACE enough?" can be answered in the negative, without the
reordering, even in the context of an ACE framework.

Restating the cautionary statement may helpful:

	Because an additional reordering request may be made for some
	as yet unspecified block of code-points, rough consensus for
	the reordering a specified block of code-points is undesireable.

This doesn't seem like prudent process. An alternative statement is:

	Because additional reordering requests will be made for some
        as yet unspecified blocks of code-points over time, rough
	consensus for a version identifier is desireable.

Eric



From owner-idn@ops.ietf.org  Mon Oct 22 17:25:31 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00056
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 17:25:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vmIX-000AlJ-00
	for idn-data@psg.com; Mon, 22 Oct 2001 14:07:49 -0700
Received: from mail-gw.im.se ([193.14.22.222])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vmIV-000AlB-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 14:07:47 -0700
Received: from msxsth3.im.se (msxsth3.im.se [193.14.16.192])
	by mail-gw.im.se (8.11.0/8.11.3) with ESMTP id f9MKx7M13290;
	Mon, 22 Oct 2001 22:59:07 +0200
Received: by msxsth3.im.se with Internet Mail Service (5.5.2653.19)
	id <VDBPFHX6>; Mon, 22 Oct 2001 23:10:01 +0200
Message-ID: <C110A2268F8DD111AA1A00805F85E58D0115ACBD@ntgbg1>
From: Karlsson Kent - keka <keka@im.se>
To: "'Soobok Lee'" <lsb@postel.co.kr>, idn@ops.ietf.org
Cc: Martin Duerst <duerst@w3.org>, DougEwell2@cs.com
Subject: RE: [idn] call for comments for REORDERING
Date: Mon, 22 Oct 2001 23:05:54 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C15B3D.56AA5260"
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_001_01C15B3D.56AA5260
Content-Type: text/plain;
	charset="iso-8859-1"


Please distinguish NFKC and NFC.  They are not the same, and have
different properties.  In several places below you have confused them,
and how they operate.

For your first problem it just shows that NFKD and NFKC should be
used with caution. They cannot be applied blindly, especially not
to text in general.  However, I don't see that this problem
(which is quite apparent to anyone reading UAX 15) hinders the use
of NFKC for for the particular application of IDNs.  Your first
problem does not affect NFD or NFC at all.

Your second problem does affect NFC (and thus also NFKC), but does
not affect NFD (fully decomposed).  This problem could, in principle,
have been avoided if there had been no Hangul syllable characters...
So for historic texts (using historic Jamo, or historic (or uncommon)
consonant (or vowel) clusters of otherwise modern Jamo) NFD would probably
be the cleanest approach, especially for rendering such substrings. As
I have read this, it just means that the conjoining Jamo can interact
with the Hangul syllables too (I'm not sure if they actually do in
any (rendering) implementation, nor if that was intended). However,
again I don't see that this would be a problem for the particular
application of IDNs, though I do see a problem for rendering engines.
(Sorting, by the way, when Jamo are supported, should support Hangul
syllables through canonical decomposition.)

The entire intent, IFAIK, with the Hangul syllables was as an
expedient for implementations that do not support Hangul Jamo at all.
For those that do support Hangul Jamo, Hangul syllable characters are
more of a pain than a help, and should decompose them for rendering
and sorting (at least), but need not do so for storage, or for IDNs...

Sorry for not following the IDN debate for a while, but I kind of
gave up when the focus turned solely onto "ACE"s, making the entire
exersice into something that may likely result in something that I
don't wish to see deployed, having very negative experiences with
"Quoted-Printable". And now there is suggestion for 'reordering' too!
This does not look good.  We don't need to have convoluted
'solutions' that are applicable only for IDNs.

		Kind regards
		/kent k


> -----Original Message-----
> From: Soobok Lee [mailto:lsb@postel.co.kr]
...
> two problems:
> 
>  1) NFKC maps   compatibility hangul jamo (U+32??) into
>                 conjoining hangul jamo without fillers.
>     That converts compat hangul jamo sequences into conjoining
>       jamo sequences and they are combined partially in some cases
>         by the NFC following  compatibilty decomposition.
>     Modern hangul informal texts contains compatibiilty jamos 
> very often.
>     If the texts contains choseong + jungseong sequence in 
> compat jamo,
>        they will be affected by this fault.
>     This fault was found by Soobok Lee, too lately.
> 
>  2) NFC  does not combine  archaic(old) hangul trailing jamo into the
>      preceding half-combined syllable (from choseong jamo + 
> jungseong jamo),
>       but leave it alone as an isolated conjoining jamo.
>     That means archail hangul syllable which has old hangul 
> trailing jamo 
>       cannot be preserved through out NFKC.
>     NFKC cannot be used for scholarly texts which contains 
> archail hangul 
>       syllables.  This fault was found by Martin, too lately.
>     
> Mark and Martin knew and told me why this happened.
> Martin, would you comment on this?
> 
> Soobok Lee
> 
> 
> > 
> > > I hope UTC cures this BUGGY NFC/NFKC jamo handling as an 
> > > exceptional case while it is in  strict adherence to 
> UTR's backward 
> > > compatiblity policy & promise.
> > 
> > The normal forms for strings of already allocated characters
> > will not be changed any more.
> > 
> > Kind regards
> > /Kent K
> > 
> 

------_=_NextPart_001_01C15B3D.56AA5260
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>RE: [idn] call for comments for REORDERING</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=2>Please distinguish NFKC and NFC.&nbsp; They are not the same, and have</FONT>
<BR><FONT SIZE=2>different properties.&nbsp; In several places below you have confused them,</FONT>
<BR><FONT SIZE=2>and how they operate.</FONT>
</P>

<P><FONT SIZE=2>For your first problem it just shows that NFKD and NFKC should be</FONT>
<BR><FONT SIZE=2>used with caution. They cannot be applied blindly, especially not</FONT>
<BR><FONT SIZE=2>to text in general.&nbsp; However, I don't see that this problem</FONT>
<BR><FONT SIZE=2>(which is quite apparent to anyone reading UAX 15) hinders the use</FONT>
<BR><FONT SIZE=2>of NFKC for for the particular application of IDNs.&nbsp; Your first</FONT>
<BR><FONT SIZE=2>problem does not affect NFD or NFC at all.</FONT>
</P>

<P><FONT SIZE=2>Your second problem does affect NFC (and thus also NFKC), but does</FONT>
<BR><FONT SIZE=2>not affect NFD (fully decomposed).&nbsp; This problem could, in principle,</FONT>
<BR><FONT SIZE=2>have been avoided if there had been no Hangul syllable characters...</FONT>
<BR><FONT SIZE=2>So for historic texts (using historic Jamo, or historic (or uncommon)</FONT>
<BR><FONT SIZE=2>consonant (or vowel) clusters of otherwise modern Jamo) NFD would probably</FONT>
<BR><FONT SIZE=2>be the cleanest approach, especially for rendering such substrings. As</FONT>
<BR><FONT SIZE=2>I have read this, it just means that the conjoining Jamo can interact</FONT>
<BR><FONT SIZE=2>with the Hangul syllables too (I'm not sure if they actually do in</FONT>
<BR><FONT SIZE=2>any (rendering) implementation, nor if that was intended). However,</FONT>
<BR><FONT SIZE=2>again I don't see that this would be a problem for the particular</FONT>
<BR><FONT SIZE=2>application of IDNs, though I do see a problem for rendering engines.</FONT>
<BR><FONT SIZE=2>(Sorting, by the way, when Jamo are supported, should support Hangul</FONT>
<BR><FONT SIZE=2>syllables through canonical decomposition.)</FONT>
</P>

<P><FONT SIZE=2>The entire intent, IFAIK, with the Hangul syllables was as an</FONT>
<BR><FONT SIZE=2>expedient for implementations that do not support Hangul Jamo at all.</FONT>
<BR><FONT SIZE=2>For those that do support Hangul Jamo, Hangul syllable characters are</FONT>
<BR><FONT SIZE=2>more of a pain than a help, and should decompose them for rendering</FONT>
<BR><FONT SIZE=2>and sorting (at least), but need not do so for storage, or for IDNs...</FONT>
</P>

<P><FONT SIZE=2>Sorry for not following the IDN debate for a while, but I kind of</FONT>
<BR><FONT SIZE=2>gave up when the focus turned solely onto &quot;ACE&quot;s, making the entire</FONT>
<BR><FONT SIZE=2>exersice into something that may likely result in something that I</FONT>
<BR><FONT SIZE=2>don't wish to see deployed, having very negative experiences with</FONT>
<BR><FONT SIZE=2>&quot;Quoted-Printable&quot;. And now there is suggestion for 'reordering' too!</FONT>
<BR><FONT SIZE=2>This does not look good.&nbsp; We don't need to have convoluted</FONT>
<BR><FONT SIZE=2>'solutions' that are applicable only for IDNs.</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2>Kind regards</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2>/kent k</FONT>
</P>
<BR>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: Soobok Lee [<A HREF="mailto:lsb@postel.co.kr">mailto:lsb@postel.co.kr</A>]</FONT>
<BR><FONT SIZE=2>...</FONT>
<BR><FONT SIZE=2>&gt; two problems:</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt;&nbsp; 1) NFKC maps&nbsp;&nbsp; compatibility hangul jamo (U+32??) into</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; conjoining hangul jamo without fillers.</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; That converts compat hangul jamo sequences into conjoining</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; jamo sequences and they are combined partially in some cases</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; by the NFC following&nbsp; compatibilty decomposition.</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Modern hangul informal texts contains compatibiilty jamos </FONT>
<BR><FONT SIZE=2>&gt; very often.</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; If the texts contains choseong + jungseong sequence in </FONT>
<BR><FONT SIZE=2>&gt; compat jamo,</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; they will be affected by this fault.</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; This fault was found by Soobok Lee, too lately.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt;&nbsp; 2) NFC&nbsp; does not combine&nbsp; archaic(old) hangul trailing jamo into the</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; preceding half-combined syllable (from choseong jamo + </FONT>
<BR><FONT SIZE=2>&gt; jungseong jamo),</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; but leave it alone as an isolated conjoining jamo.</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; That means archail hangul syllable which has old hangul </FONT>
<BR><FONT SIZE=2>&gt; trailing jamo </FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; cannot be preserved through out NFKC.</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; NFKC cannot be used for scholarly texts which contains </FONT>
<BR><FONT SIZE=2>&gt; archail hangul </FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; syllables.&nbsp; This fault was found by Martin, too lately.</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=2>&gt; Mark and Martin knew and told me why this happened.</FONT>
<BR><FONT SIZE=2>&gt; Martin, would you comment on this?</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Soobok Lee</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; I hope UTC cures this BUGGY NFC/NFKC jamo handling as an </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; exceptional case while it is in&nbsp; strict adherence to </FONT>
<BR><FONT SIZE=2>&gt; UTR's backward </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; compatiblity policy &amp; promise.</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; The normal forms for strings of already allocated characters</FONT>
<BR><FONT SIZE=2>&gt; &gt; will not be changed any more.</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Kind regards</FONT>
<BR><FONT SIZE=2>&gt; &gt; /Kent K</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C15B3D.56AA5260--



From owner-idn@ops.ietf.org  Mon Oct 22 20:39:04 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02114
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 20:39:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vpO9-000GQk-00
	for idn-data@psg.com; Mon, 22 Oct 2001 17:25:49 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vpO8-000GQQ-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 17:25:48 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id JAA03762;
	Tue, 23 Oct 2001 09:25:28 +0900
Message-ID: <004401c15b59$598d6460$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
References: <Roam.SIMC.2.0.6.1003780918.20410.nordmark@bebop.france>
Subject: Re: [idn] Which lanuages/scripts to reorder? 
Date: Tue, 23 Oct 2001 09:26:25 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id UAA02114


----- Original Message ----- 
From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>; <idn@ops.ietf.org>
Sent: Tuesday, October 23, 2001 5:01 AM
Subject: Re: [idn] Which lanuages/scripts to reorder? 


> 
> Eric, 
> 
> > The process, if any, of future revision of thie WG's product, again, if any,
> > is important. Either there is none, and it is "permanent" until discarded,
> > or there is some, which may work (allowing semi-graceful revisioning).
> 
> This is assuming that the WG actually produces something.
> My concern in the area of reordering is that incremental requests for
> supporting additional laguages/scripts for reordering benefits might mean
> that the WG never gets to deliver anything - there are just too many
> scripts/languages that can appear.
> 
> Thus my concern is completely unrelated to the version issues
> others have brought up with respect to UTC.
> 
> If the WG embarks on doing reordering for 1,2,3,4 languages/scripts
> how do we know that this will be sufficient? Next month there might be
> requests for a few more languages/scripts. Etc.

seamless upgrade idea for adding new script reordering tables and new nameprep rules (NF/casemappings) are described in the posting titled with "suggestion : two prefices ....". No newer prefix other than (zq-- and uq--) will be needed forever.
I recommend you to comment on the suggestion first before you go further.

Soobok Lee

> 
>   Erik
> 
> 




From owner-idn@ops.ietf.org  Mon Oct 22 21:06:21 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02294
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 21:06:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vprl-000H3b-00
	for idn-data@psg.com; Mon, 22 Oct 2001 17:56:25 -0700
Received: from smtp22.singnet.com.sg ([165.21.101.202])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vprk-000H3V-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 17:56:24 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp22.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9N0xvi25095;
	Tue, 23 Oct 2001 08:59:57 +0800
Message-ID: <00a101c15b5d$86aa04e0$1301000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
Cc: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        "Paul Hoffman / IMC" <phoffman@imc.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <024b01c15847$11e8b430$0501000a@jamessonyvaio> <4.2.0.58.J.20011019152610.037f1100@localhost> <4.2.0.58.J.20011019180625.038105d0@localhost> <4.2.0.58.J.20011022114545.02c1ae70@localhost> <004e01c15ae7$ba4761b0$ec1bd9d2@temp> <006b01c15aff$07348f90$1101000a@jamessonyvaio> <003a01c15b24$d16f3100$ec1bd9d2@temp>
Subject: [idn] Re: suggestion: two prefices scheme for unassigned code points treatments.
Date: Tue, 23 Oct 2001 08:56:18 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Lee,

Other may be too polite to say this but this proposal is so absurb that
I don't even know where to start.

[snip section on two prefix]
> halfbaked idea. welcome any corrections and suggestions.

You got this part right tho.

Suggest you go work on it further. Do not think of this as a problem of
"how can I get reordering into IDN" and forget the other issues of
general use of domain names, behavior and stability.

-James Sen




From owner-idn@ops.ietf.org  Mon Oct 22 21:24:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02393
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 21:24:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vqBK-000HXp-00
	for idn-data@psg.com; Mon, 22 Oct 2001 18:16:38 -0700
Received: from smtp22.singnet.com.sg ([165.21.101.202])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vqBJ-000HXi-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 18:16:37 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp22.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9N1KGi01963
	for <idn@ops.ietf.org>; Tue, 23 Oct 2001 09:20:16 +0800
Message-ID: <00b501c15b60$5d97c4e0$1301000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <idn@ops.ietf.org>
Subject: [idn] proposed wg charter, goal & milestone update
Date: Tue, 23 Oct 2001 09:16:38 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Apologise for the late update as it taken some time to get the wordings
right.

Changes 1: Add wordings to clarify the concept of "names vs identifiers"

"Domain names is one form of identifier. It does not have the technical
capability to encode names or languages information."

Changes 2: Add wordings to clarify DNSEXT & IDN WG

"The WG work may modify the DNS protocol and other related work
undertaken by the DNSEXT WG. But such changes must be co-ordinated with
the DNSEXT WG."


Description of Working Group:

The goal of the group is to specify the requirements for
internationalized access to domain names and to specify a standards
track protocol based on the requirements.

Domain names is one form of identifier. It does not have the
technical capability to encode names or languages information.

The scope of the group is to investigate the possible means of doing
this and what methods are feasible given the technical impact they
will have on the use of such names by humans as well as application
programs, as well as the impact on other users and administrators of
the domain name system.

A fundamental requirement in this work is to not disturb the current use
and operation of the domain name system, and for the DNS to continue to
allow any system anywhere to resolve any domain name.


The group will not address the question of what, if any, body should
administer or control usage of names that use this functionality.

The group must identify consequences to the current deployed DNS
infrastructure, the protocols and the applications as well as
transition scenarios, where applicable.

The WG will actively ensure good communication with interested groups
> > > who are studying the problem of internationalized access to domain
> > > names.
> > >
> > > The Action Item(s) for the Working Group are
> > >
> > > 1. An Informational RFC specifying the requirements for providing
> > > Internationalized access to domain names. The document should
>provide
> > > guidance for development solutions to this problem, taking
localized
> > > (e.g. writing order) and related operational issues into
> > consideration.
> > >
> > > <remove>2. An Informational RFC or RFC's documenting the various
> > > proposals and Implementations of Internationalization (i18n) of
>Domain
> > > Names. The document(s) should also provide a technical evaluation
of
> > the
> > > proposals by the Working Group.</remove>
> > >
> > > 2. A standard track specification on access to internationalized
> > domain
> > > names including specifying any transition issues.
> > >
> > > <add>3. A standard track specification on an ASCII Compatible
>Encoding
> > > (ACE). This may or may not be used in the standard track
>specification
> > > on access to internationalized domain names.</add>
> > >
> > > <add>4. A standard track specification on the string comparison of
> > > identifiers composed of character beyond the US-ASCII.</add>





From owner-idn@ops.ietf.org  Mon Oct 22 21:37:18 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03523
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 21:37:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vqLh-000HoO-00
	for idn-data@psg.com; Mon, 22 Oct 2001 18:27:21 -0700
Received: from smtp21.singnet.com.sg ([165.21.101.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vqLg-000HoI-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 18:27:20 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp21.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9N1SLp02316
	for <idn@ops.ietf.org>; Tue, 23 Oct 2001 09:28:21 +0800
Message-ID: <00fa01c15b61$dce07f20$1301000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <idn@ops.ietf.org>
Subject: [idn] proposed wg charter, goal & milestone update
Date: Tue, 23 Oct 2001 09:27:21 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

[Please ignore last mail: It got send out by accident.]

Apologise for the late update as it taken some time to get the wordings
right. I shall list all the changes first and then the complete charter
below. Please comment.

Changes 1: Add wordings to clarify the concept of "names vs identifiers"

"Domain names is one form of identifier. It does not have the technical
capability to encode names or languages information."

Changes 2: Add wordings to clarify DNSEXT & IDN WG

"The WG work may modify the DNS protocol and other related work
undertaken by the DNSEXT WG. But such changes must be co-ordinated with
the DNSEXT WG."

Changes 3: Add wordings to clarify IDN WG & other I18N organization

"The WG will reference work from ISO/IEC, the Unicode Consortium and
other established I18N group as much as possible. The consideration are
the policy and principle adopted by the I18N group on the stability of
published codepoints and future addition of codepoints. The discussion
of new codepoints, codepoints properties and mappings between codepoints
are out-of-scope for the working group and should be done in other
relevant expert group."

Changes 4: Remove Action Item 2: comparison RFC

As discussed with Paul, this is no longer a document he wish to
continue.

<remove>2. An Informational RFC or RFC's documenting the various
proposals and Implementations of Internationalization (i18n) of Domain
Names. The document(s) should also provide a technical evaluation of the
proposals by the Working Group.</remove>

Changes 5: Add Action Items to reflect IDN current work

3. A standard track specification on an ASCII Compatible Encoding
   (ACE). This may or may not be used in the standard track
   specification on access to internationalized domain names.


4. A standard track specification on normalization of identifiers
   for the purpuse of comparisons. This document may includes case
   folding, map outs, and prohibited characters.

Changes 6: Update goal & milestones

Nov 2001    Nameprep RFC wg last call
Dec 2001    Nameprep RFC send to IESG for advancement
Nov 2001    First draft of architecture draft specifying the
            relationship between input methods, namepreps and zonefile
Dec 2001    Protocol RFC wg last call
Dec 2001    Second draft of architecture draft
Jan 2002    Protocol RFC send to IESG for advancement
Feb 2002    Architecture draft last call
Mar 2002    Architecture draft send to IESG for advancement

-James Seng

--- CUT HERE ---
Description of Working Group:

The goal of the group is to specify the requirements for
internationalized access to domain names and to specify a standards
track protocol based on the requirements.

Domain names is one form of identifier. It does not have the technical
capability to encode names or languages information.

The scope of the group is to investigate the possible means of doing
this and what methods are feasible given the technical impact they will
have on the use of such names by humans as well as application programs,
as well as the impact on other users and administrators of the domain
name system.

A fundamental requirement in this work is to not disturb the current use
and operation of the domain name system, and for the DNS to continue to
allow any system anywhere to resolve any domain name.

The WG work may modify the DNS protocol and other related work
undertaken by the DNSEXT WG. But such changes must be co-ordinated with
the DNSEXT WG.

The WG will reference work from ISO/IEC, the Unicode Consortium and
other established I18N group as much as possible. The consideration are
the policy and principle adopted by the I18N group on the stability of
published codepoints and future addition of codepoints. The discussion
of new codepoints, codepoints properties and mappings between codepoints
are out-of-scope for the working group and should be done in other
relevant expert group.

The group will not address the question of what, if any, body should
administer or control usage of names that use this functionality.

The group must identify consequences to the current deployed DNS
infrastructure, the protocols and the applications as well as transition
scenarios, where applicable.

The WG will actively ensure good communication with interested groups
who are studying the problem of internationalized access to domain
names.

The Action Item(s) for the Working Group are

1. An Informational RFC specifying the requirements for providing
   Internationalized access to domain names. The document should
   provide guidance for development solutions to this problem,
   taking localized (e.g. writing order) and related operational
   issues into consideration.

2. A standard track specification on access to internationalized
   domain names including specifying any transition issues.

3. A standard track specification on an ASCII Compatible Encoding
   (ACE). This may or may not be used in the standard track
   specification on access to internationalized domain names.

4. A standard track specification on normalization of identifiers
   for the purpuse of comparisons. This document may includes case
   folding, map outs, and prohibited characters.

Goal & Milestone:

Nov 2001    Nameprep RFC wg last call
Dec 2001    Nameprep RFC send to IESG for advancement
Nov 2001    First draft of architecture draft specifying the
            relationship between input methods, namepreps and zonefile
Dec 2001    Protocol RFC wg last call
Dec 2001    Second draft of architecture draft
Jan 2002    Protocol RFC send to IESG for advancement
Feb 2002    Architecture draft last call
Mar 2002    Architecture draft send to IESG for advancement





From owner-idn@ops.ietf.org  Mon Oct 22 21:42:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03577
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 21:42:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vqNz-000Hqt-00
	for idn-data@psg.com; Mon, 22 Oct 2001 18:29:43 -0700
Received: from [203.207.0.132] (helo=mail.asiainfra.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vqNy-000Hqm-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 18:29:42 -0700
Received: from gix ([203.207.0.121])
	by mail.asiainfra.com (8.9.3/8.9.3) with SMTP id JAA15141;
	Tue, 23 Oct 2001 09:29:48 +0800
From: "Kenny Huang" <huangk@alum.sinica.edu>
To: "Soobok Lee" <lsb@postel.co.kr>, <DougEwell2@cs.com>, <idn@ops.ietf.org>
Subject: RE: [idn] Re: REORDERING: stability issues and UTC solutions
Date: Tue, 23 Oct 2001 09:34:33 +0800
Message-ID: <IHELIFNJKJLDFEMBCENDOECGCIAA.huangk@alum.sinica.edu>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
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.4807.1700
Importance: Normal
In-Reply-To: <001801c15b10$01148190$ec1bd9d2@temp>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA03577

We had very extensive discussion regarding SCRIPT case mapping in
JET meeting last week. Script case mapping would be very important.
CNNIC and TWNIC will propose drafts to address these issues soon.

Kenny Huang


> -----Original Message-----
> From: owner-idn@ops.ietf.org [mailto:owner-idn@ops.ietf.org]On 
> Behalf Of Soobok Lee
> Sent: Monday, October 22, 2001 11:41 PM
> To: DougEwell2@cs.com; idn@ops.ietf.org
> Subject: Re: [idn] Re: REORDERING: stability issues and UTC solutions
> 
> 
> 
> ----- Original Message ----- 
> From: <DougEwell2@cs.com>
>  > It might be a good idea to peruse these resources and verify 
> for oneself that 
> > they do not contain any characters that are compatibility forms 
> of other 
> > characters or combinations of characters.  Of course, nobody 
> can predict the 
> > future with 100% accuracy but there are lots of good hints that 
> the scenario 
> > "newly-approved 'S' characters X,Y  have   NFC X -> Y" for any 
> script 'S' is 
> > simply not ever going to happen.
> > 
>  
> Instead of NFC, some script may need CASE mappings, i guess.
> Current nameprep/ACE produce case-insensitively equivalent labels
> for IDN  X.com and x.com.
> Do you mean that all newly added SCRIPT won't have any case mapping ?
> 
> Doug, 
> If you have lists of new scripts pending for approval,
> please post them to this list for non-unicode experts.
> 
> Soobok Lee
> 
> 




From owner-idn@ops.ietf.org  Mon Oct 22 23:06:27 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05582
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 23:06:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vrkY-000JnJ-00
	for idn-data@psg.com; Mon, 22 Oct 2001 19:57:06 -0700
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vrkX-000Jmz-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 19:57:06 -0700
Received: from zetnet.co.uk (man-s298.dialup.zetnet.co.uk [194.247.45.169])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f9N2ump23894;
	Tue, 23 Oct 2001 03:56:49 +0100
Message-ID: <3BD4DC6E.F28A63EB@zetnet.co.uk>
Date: Tue, 23 Oct 2001 03: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: James Seng/Personal <jseng@pobox.org.sg>, idn@ops.ietf.org
Subject: Re: [idn] proposed wg charter, goal & milestone update
References: <00fa01c15b61$dce07f20$1301000a@jamessonyvaio>
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-----

James Seng/Personal wrote:
> Apologise for the late update as it taken some time to get the wordings
> right. I shall list all the changes first and then the complete charter
> below. Please comment.
> 
> Changes 1: Add wordings to clarify the concept of "names vs identifiers"
> 
> "Domain names is one form of identifier. It does not have the technical
> capability to encode names or languages information."

The DNS *could* encode language/script information (or relations between
corresponding names in different languages/scripts); all that would need
is a new RR. What is true is that the names themselves are not language-
tagged.

Also, the requirements draft makes a useful distinction between domain
names (which are octet strings) and host names (which are character
strings). Both are identifiers.

I suggest:

  "Domain names and host names are forms of identifier. Language
  information is not encoded in these names; that is, names from
  different languages are defined in a single namespace."

- -- 
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

iQEVAwUBO9TcUTkCAxeYt5gVAQHhzgf8CpwK9G3h3uHIBOHWirYBHsWKuo/TlqFQ
vzYCva6JxWOP+QVU2XY194bE7qtw1h5qof8XPCk4MPYwOjDm6XEk4XsY8zibVZhw
sMJKrn3CftnZVpTo1zPGyw9ooDe/3hAmq4lAW51MOeaLsPuMFDziA8+JVuhEE2++
wVPg5oQLbWS0K6vKYF8B2ig45CZGBqv/sWJH730sjeOe0IFe3VDqpsO/aNnIbAvX
medRFKdWwruMN82jxrgNAmZuA+hYcQrC3NSoucw97m8VD4MA2DS4V6ll+6tvYxdK
eR9B1ylHjvKwfcLD0/VIVvKaNZN0qHWiGjo9jyraQ3v3Gjdbn5Crww==
=ao+f
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Mon Oct 22 23:35:49 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06231
	for <idn-archive@lists.ietf.org>; Mon, 22 Oct 2001 23:35:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vs6j-000KM7-00
	for idn-data@psg.com; Mon, 22 Oct 2001 20:20:01 -0700
Received: from femail17.sdc1.sfba.home.com ([24.0.95.144])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vs6j-000KLx-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 20:20:01 -0700
Received: from c1340594a ([65.11.104.12]) by femail17.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20011023031959.HFYF14800.femail17.sdc1.sfba.home.com@c1340594a>;
          Mon, 22 Oct 2001 20:19:59 -0700
Message-ID: <006401c15b71$b6fb9e60$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
References: <200109181333.JAA19941@ietf.org> <024301c149a0$c65b1ee0$ec1bd9d2@temp> <032c01c15141$9fc7cc80$ec1bd9d2@temp>
Subject: Re: [idn] call for comments for REORDERING
Date: Mon, 22 Oct 2001 20:20:49 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

My only comments are:

1. Like others, I believe that it is unnecessary.
2. If it were adopted, to ensure stability of IDN over time, the reordering
should absolutely be permanent -- never changed in the future, even if new
characters are added. This is not an onerous restriction, since reordering
is only a permutation of code points for the purpose of compression, and
neither adds nor removes information.

Mark

—————

Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
[http://www.macchiato.com]

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
Sent: Tuesday, October 09, 2001 21:11
Subject: [idn] call for comments for REORDERING


Hi, all

I am ready to receive any criticisms on REORDERING.
Any suggestions of improvements or downsides of REORDERING are all welcome.

I expect many feedbacks from non-US and non-European participants and
observers.

Thanks.

Soobok Lee

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Sent: Sunday, September 30, 2001 8:12 PM
Subject: Re: [idn] I-D ACTION:draft-ietf-idn-lsb-ace-02.txt


> Hi, all
>
> This table summarizes the # of max chars in labels in each script block.
> This will be included the next revision of reordering I-D.
> For han/hangul block, REORDERING+ACE-Z outperforms DUDE by nearly 200%.
> If you have suggestions or other label samples to test with,
> please leave me a note.
>
> Thanks.
>
> Soobok Lee,   lsb@postel.co.kr
>
>
> +------------------------------------------------------------+
> |Maximum number of characters in a label in each script block|
> |                                                            |
> |                max char = (63 - 4) / ratio                 |
> |   ACE length = 4 + ratio * N ( N : # of chars in label)    |
> +---------------+-------------------+-------------------+----+
> | Script Block  |     AMC-ACE-Z     |   Reordering +    |Gain|
> |               |                   |     AMC-ACE-Z     |    |
> +---------+-----+---------+---------+---------+---------+    |
> |  Name   |Size |  ratio  |max char |  ratio  |max char |    |
> +---------+-----+---------+---------+---------+---------+----+
> |   Han   |20992|  2.98   |   19    |  2.21   |   26    | +7 |
> +---------+-----+---------+---------+---------+---------+----+
> | Hangeul |11172|  2.97   |   19    |  2.04   |   28    | +9 |
> +---------+-----+---------+---------+---------+---------+----+
> |  Greek  | 144 |  1.29   |   45    |  1.14   |   51    | +6 |
> +---------+-----+---------+---------+---------+---------+----+
> | Arabic  | 256 |  1.34   |   44    |  1.28   |   46    | +2 |
> +---------+-----+---------+---------+---------+---------+----+
> |Cyrillic | 304 |  1.23   |   47    |  1.15   |   51    | +4 |
> +---------+-----+---------+---------+---------+---------+----+
> | Hebrew  | 102 |  1.29   |   45    |  1.18   |   50    | +5 |
> +---------+-----+---------+---------+---------+---------+----+
> |  Hindi  | 128 |  1.31   |   45    |  1.17   |   50    | +5 |
> +---------+-----+---------+---------+---------+---------+----+
> |Hiragana | 96  |  1.50   |   39    |  1.45   |   40    | +1 |
> +---------+-----+---------+---------+---------+---------+----+
> |Katakana | 96  |  1.44   |   40    |  1.33   |   44    | +4 |
> +---------+-----+---------+---------+---------+---------+----+
> |  Tamil  | 128 |  1.62   |   36    |  1.14   |   51    |+15 |
> +---------+-----+---------+---------+---------+---------+----+
> |  Thai   | 128 |  1.39   |   42    |  1.13   |   52    |+10 |
> +---------+-----+---------+---------+---------+---------+----+
> |Ethiopic | 416 |  2.10   |   28    |  1.60   |   36    | +8 |
> +---------+-----+---------+---------+---------+---------+----+
>
>
> ----- Original Message -----
> From: <Internet-Drafts@ietf.org>
> To: <IETF-Announce:>
> Cc: <idn@ops.ietf.org>
> Sent: Tuesday, September 18, 2001 10:33 PM
> Subject: [idn] I-D ACTION:draft-ietf-idn-lsb-ace-02.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 : Improving ACE using code point reordering v2.0
> > Author(s) : S. Lee
> > Filename : draft-ietf-idn-lsb-ace-02.txt
> > Pages :
> > Date : 17-Sep-01
> >
> > This document describes a method to improve ACE label efficiency by
> > frequency-based temporal reordering of code points in ACE encoding
> > and decoding processes in order to relocate scattered frequent
> > characters into much more compact area in reordered code space.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-idn-lsb-ace-02.txt
> >
> > To remove yourself from the IETF Announcement list, send a message to
> > ietf-announce-request with the word unsubscribe in the body of the
message.
> >
> > 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-02.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-02.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  Tue Oct 23 00:04:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06529
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 00:04:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vsOQ-000Klg-00
	for idn-data@psg.com; Mon, 22 Oct 2001 20:38:18 -0700
Received: from femail18.sdc1.sfba.home.com ([24.0.95.145])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vsOP-000Kla-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 20:38:17 -0700
Received: from c1340594a ([65.11.104.12]) by femail18.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20011023033816.EIOD27771.femail18.sdc1.sfba.home.com@c1340594a>;
          Mon, 22 Oct 2001 20:38:16 -0700
Message-ID: <00b501c15b74$45047ae0$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>, "Karlsson Kent - keka" <keka@im.se>,
        <idn@ops.ietf.org>
Cc: "Martin Duerst" <duerst@w3.org>, <DougEwell2@cs.com>
References: <C110A2268F8DD111AA1A00805F85E58D0115ACBC@ntgbg1> <004901c15b29$0c552d20$ec1bd9d2@temp>
Subject: Re: [idn] call for comments for REORDERING
Date: Mon, 22 Oct 2001 20:39:02 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

1. The compatibility hangul jamo are not the preferred way to express
isolated jamo in Unicode. That would be by the use of conjoining jamo with
fillers. If the preferred forms are used, there are no problems.

2. NFC does not combine ancient Hangul into syllables because there are no
syllables that have ancient Hangul in them. It does combine as many modern
Jamo as possible into syllables. That does not -- at all -- prevent the use
of NFC with ancient Hangul.

Mark
—————

Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
[http://www.macchiato.com]

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Karlsson Kent - keka" <keka@im.se>; <idn@ops.ietf.org>
Cc: "Martin Duerst" <duerst@w3.org>; <DougEwell2@cs.com>
Sent: Monday, October 22, 2001 11:40
Subject: Re: [idn] call for comments for REORDERING



----- Original Message -----
From: "Karlsson Kent - keka" <keka@im.se>
>
> > I know current NFC/NFKC has *severely flawed* hangul jamo
>
> Now that's a new complaint.  At least to me.  Not even the
> delegations from DPRK complain about that. (And they have
> all sorts of complaints.)  Do you care to say a little bit
> more about what you mean?  Or are we just to take your word
> for it?  There was a problem in earlier drafts of UAX 15
> concerning Hangul and NFKC (Hangul syllables were not preserved),
> but that problem was removed before that UTR became a UAX.

two problems:

 1) NFKC maps   compatibility hangul jamo (U+32??) into
                conjoining hangul jamo without fillers.
    That converts compat hangul jamo sequences into conjoining
      jamo sequences and they are combined partially in some cases
        by the NFC following  compatibilty decomposition.
    Modern hangul informal texts contains compatibiilty jamos very often.
    If the texts contains choseong + jungseong sequence in compat jamo,
       they will be affected by this fault.
    This fault was found by Soobok Lee, too lately.

 2) NFC  does not combine  archaic(old) hangul trailing jamo into the
     preceding half-combined syllable (from choseong jamo + jungseong jamo),
      but leave it alone as an isolated conjoining jamo.
    That means archail hangul syllable which has old hangul trailing jamo
      cannot be preserved through out NFKC.
    NFKC cannot be used for scholarly texts which contains archail hangul
      syllables.  This fault was found by Martin, too lately.

Mark and Martin knew and told me why this happened.
Martin, would you comment on this?

Soobok Lee


>
> > I hope UTC cures this BUGGY NFC/NFKC jamo handling as an
> > exceptional case while it is in  strict adherence to UTR's backward
> > compatiblity policy & promise.
>
> The normal forms for strings of already allocated characters
> will not be changed any more.
>
> Kind regards
> /Kent K
>







From owner-idn@ops.ietf.org  Tue Oct 23 00:32:12 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06898
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 00:32:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vspE-000L9k-00
	for idn-data@psg.com; Mon, 22 Oct 2001 21:06:00 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vspD-000L9e-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 21:05:59 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id NAA07875;
	Tue, 23 Oct 2001 13:05:40 +0900
Message-ID: <016501c15b78$1d38a820$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Mark Davis" <mark@macchiato.com>, "Karlsson Kent - keka" <keka@im.se>,
        <idn@ops.ietf.org>
Cc: "Martin Duerst" <duerst@w3.org>, <DougEwell2@cs.com>
References: <C110A2268F8DD111AA1A00805F85E58D0115ACBC@ntgbg1> <004901c15b29$0c552d20$ec1bd9d2@temp> <00b501c15b74$45047ae0$0c680b41@c1340594a>
Subject: Re: [idn] call for comments for REORDERING
Date: Tue, 23 Oct 2001 13:06:38 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA06898


----- Original Message ----- 
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>; "Karlsson Kent - keka" <keka@im.se>; <idn@ops.ietf.org>
Cc: "Martin Duerst" <duerst@w3.org>; <DougEwell2@cs.com>
Sent: Tuesday, October 23, 2001 12:39 PM
Subject: Re: [idn] call for comments for REORDERING


> 1. The compatibility hangul jamo are not the preferred way to express
> isolated jamo in Unicode. That would be by the use of conjoining jamo with
> fillers. If the preferred forms are used, there are no problems.
> 
But, KSC5601-->Unicode mapping tables  maps  KSC5601 isolated hangul jamo
into compat hangul jamo. The mapping table was issued by UTC itself and
placed into WIN98,2K,XP and most unix and linux platforms.
Inconsistency!


> 2. NFC does not combine ancient Hangul into syllables because there are no
> syllables that have ancient Hangul in them. It does combine as many modern
> Jamo as possible into syllables. That does not -- at all -- prevent the use
> of NFC with ancient Hangul.

Rendering problem remains unsolved. 
"hangul  syllable ga + old jamo bansioth " != "old hangul syllable ga+bansioth".
There is defined no such false equivalence  in UTR15.
 Why rendering engine vendors should  make such false workarounds not
recommended in UTC standards?
NFC is  dangerous for ancient hangul.

> 
> Mark
> —————
> 
> Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
> [http://www.macchiato.com]
> 
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: "Karlsson Kent - keka" <keka@im.se>; <idn@ops.ietf.org>
> Cc: "Martin Duerst" <duerst@w3.org>; <DougEwell2@cs.com>
> Sent: Monday, October 22, 2001 11:40
> Subject: Re: [idn] call for comments for REORDERING
> 
> 
> 
> ----- Original Message -----
> From: "Karlsson Kent - keka" <keka@im.se>
> >
> > > I know current NFC/NFKC has *severely flawed* hangul jamo
> >
> > Now that's a new complaint.  At least to me.  Not even the
> > delegations from DPRK complain about that. (And they have
> > all sorts of complaints.)  Do you care to say a little bit
> > more about what you mean?  Or are we just to take your word
> > for it?  There was a problem in earlier drafts of UAX 15
> > concerning Hangul and NFKC (Hangul syllables were not preserved),
> > but that problem was removed before that UTR became a UAX.
> 
> two problems:
> 
>  1) NFKC maps   compatibility hangul jamo (U+32??) into
>                 conjoining hangul jamo without fillers.
>     That converts compat hangul jamo sequences into conjoining
>       jamo sequences and they are combined partially in some cases
>         by the NFC following  compatibilty decomposition.
>     Modern hangul informal texts contains compatibiilty jamos very often.
>     If the texts contains choseong + jungseong sequence in compat jamo,
>        they will be affected by this fault.
>     This fault was found by Soobok Lee, too lately.
> 
>  2) NFC  does not combine  archaic(old) hangul trailing jamo into the
>      preceding half-combined syllable (from choseong jamo + jungseong jamo),
>       but leave it alone as an isolated conjoining jamo.
>     That means archail hangul syllable which has old hangul trailing jamo
>       cannot be preserved through out NFKC.
>     NFKC cannot be used for scholarly texts which contains archail hangul
>       syllables.  This fault was found by Martin, too lately.
> 
> Mark and Martin knew and told me why this happened.
> Martin, would you comment on this?
> 
> Soobok Lee
> 
> 
> >
> > > I hope UTC cures this BUGGY NFC/NFKC jamo handling as an
> > > exceptional case while it is in  strict adherence to UTR's backward
> > > compatiblity policy & promise.
> >
> > The normal forms for strings of already allocated characters
> > will not be changed any more.
> >
> > Kind regards
> > /Kent K
> >
> 
> 
> 
> 




From owner-idn@ops.ietf.org  Tue Oct 23 00:32:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06899
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 00:32:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vsxQ-000LEm-00
	for idn-data@psg.com; Mon, 22 Oct 2001 21:14:28 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vsxP-000LEg-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 21:14:27 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9N4EIN15179;
	Tue, 23 Oct 2001 00:14:18 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110230414.f9N4EIN15179@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
cc: "Soobok Lee" <lsb@postel.co.kr>, Marc.Blanchet@viagenie.qc.ca,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Re: suggestion: two prefices scheme for unassigned code points treatments. 
In-Reply-To: Your message of "Tue, 23 Oct 2001 08:56:18 +0800."
             <00a101c15b5d$86aa04e0$1301000a@jamessonyvaio> 
Date: Tue, 23 Oct 2001 00:14:18 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Co-chair James Seng wrote to Soobok Lee:

> Other may be too polite to say this but this proposal is so absurb that
> I don't even know where to start.

It is the job of a chair of an IETF WG have access to sufficient expertise
to "know where to start", and usually it is a plus if the chair is civil.

> [snip section on two prefix]
> > halfbaked idea. welcome any corrections and suggestions.
> 
> You got this part right tho.

When a contributor to the IETF sollicits "corrections and suggestions",
he or she is working in the spirit of the IETF, which fundamentally is
a body which coordinates and harmonizes "corrections and suggestions"
(aka "interoperation") between network infrastructure implementors through
a formal specification process we refer to as "drafting protocols".

Anyone who fails to understand specification of at least two independent
interoperable implementations from different code bases, with sufficient
successful operational experience, is the core criteria for an IETF memo
to be a draft standard, fails also to understand that only constructive 
engagement between implementors leads to an interoperable outcome. There
is no place for non-constructive "wit", particularly in a chair.

> Suggest you go work on it further. Do not think of this as a problem of
> "how can I get reordering into IDN" and forget the other issues of
> general use of domain names, behavior and stability.

Exactly how does transformations on code-blocks at some point within the
proposed framework (e.g., unicode, nameprep, reordering (tc,sc,jc,kc), 
amc-z|utf-8) have a non-interoperable manifestation as "general use of
domain names, behavior and stability"?

Eric



From owner-idn@ops.ietf.org  Tue Oct 23 01:01:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07178
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 01:01:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vtOk-000LaY-00
	for idn-data@psg.com; Mon, 22 Oct 2001 21:42:42 -0700
Received: from smtp23.singnet.com.sg ([165.21.101.203])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vtOi-000LaR-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 21:42:40 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp23.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9N4iwx11437;
	Tue, 23 Oct 2001 12:44:58 +0800
Message-ID: <030e01c15b7d$1eb320e0$1301000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: "Soobok Lee" <lsb@postel.co.kr>, <Marc.Blanchet@viagenie.qc.ca>,
        <idn@ops.ietf.org>, <brunner@nic-naa.net>
Subject: Re: [idn] Re: suggestion: two prefices scheme for unassigned code points treatments. 
Date: Tue, 23 Oct 2001 12:42:28 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Normally I wont bother with a reply on this, but:

1. When I speak as a co-chair, I will normally state so. Until then, I
am
   a wg member like everyone else, entitled with my opinion. Do not
   confuse my various hats. I have too many of them, enough for you
   put my words into other context which is inappropriate.

2. Suggest you read the original proposal on two prefix *first* then
   maybe you could post something more technical constructive. Obviously
   from your questions, you have not even readLee's original proposal on
   two prefix.

-James Seng

----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
Cc: "Soobok Lee" <lsb@postel.co.kr>; <Marc.Blanchet@viagenie.qc.ca>;
<idn@ops.ietf.org>; <brunner@nic-naa.net>
Sent: Tuesday, October 23, 2001 12:14 PM
Subject: Re: [idn] Re: suggestion: two prefices scheme for unassigned
code points treatments.


> Co-chair James Seng wrote to Soobok Lee:
>
> > Other may be too polite to say this but this proposal is so absurb
that
> > I don't even know where to start.
>
> It is the job of a chair of an IETF WG have access to sufficient
expertise
> to "know where to start", and usually it is a plus if the chair is
civil.
>
> > [snip section on two prefix]
> > > halfbaked idea. welcome any corrections and suggestions.
> >
> > You got this part right tho.
>
> When a contributor to the IETF sollicits "corrections and
suggestions",
> he or she is working in the spirit of the IETF, which fundamentally is
> a body which coordinates and harmonizes "corrections and suggestions"
> (aka "interoperation") between network infrastructure implementors
through
> a formal specification process we refer to as "drafting protocols".
>
> Anyone who fails to understand specification of at least two
independent
> interoperable implementations from different code bases, with
sufficient
> successful operational experience, is the core criteria for an IETF
memo
> to be a draft standard, fails also to understand that only
constructive
> engagement between implementors leads to an interoperable outcome.
There
> is no place for non-constructive "wit", particularly in a chair.
>
> > Suggest you go work on it further. Do not think of this as a problem
of
> > "how can I get reordering into IDN" and forget the other issues of
> > general use of domain names, behavior and stability.
>
> Exactly how does transformations on code-blocks at some point within
the
> proposed framework (e.g., unicode, nameprep, reordering (tc,sc,jc,kc),
> amc-z|utf-8) have a non-interoperable manifestation as "general use of
> domain names, behavior and stability"?
>
> Eric
>





From owner-idn@ops.ietf.org  Tue Oct 23 01:03:22 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07201
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 01:03:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vtOz-000Lai-00
	for idn-data@psg.com; Mon, 22 Oct 2001 21:42:57 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vtOy-000Lac-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 21:42:56 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9N4gpN15830;
	Tue, 23 Oct 2001 00:42:52 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110230442.f9N4gpN15830@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        "Soobok Lee" <lsb@postel.co.kr>, Marc.Blanchet@viagenie.qc.ca,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Re: suggestion: two prefices scheme for unassigned code points treatments. 
In-Reply-To: Your message of "Tue, 23 Oct 2001 12:39:55 +0800."
             <02f401c15b7c$c3798d40$1301000a@jamessonyvaio> 
Date: Tue, 23 Oct 2001 00:42:51 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James,

I read Soobok's proposal last week.

Eric



From owner-idn@ops.ietf.org  Tue Oct 23 01:04:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07219
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 01:04:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vtX9-000LjA-00
	for idn-data@psg.com; Mon, 22 Oct 2001 21:51:23 -0700
Received: from smtp23.singnet.com.sg ([165.21.101.203])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vtX8-000Lix-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 21:51:22 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp23.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9N4rqx15367
	for <idn@ops.ietf.org>; Tue, 23 Oct 2001 12:53:52 +0800
Message-ID: <035701c15b7e$5d152bc0$1301000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <idn@ops.ietf.org>
References: <200110230442.f9N4gpN15830@nic-naa.net>
Subject: Re: [idn] Re: suggestion: two prefices scheme for unassigned code points treatments. 
Date: Tue, 23 Oct 2001 12:51:22 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Read his proposal dated today (23th Oct) please.

http://www.imc.org/idn/mail-archive/msg04332.html

-James Seng

----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
"Soobok Lee" <lsb@postel.co.kr>; <Marc.Blanchet@viagenie.qc.ca>;
<idn@ops.ietf.org>; <brunner@nic-naa.net>
Sent: Tuesday, October 23, 2001 12:42 PM
Subject: Re: [idn] Re: suggestion: two prefices scheme for unassigned
code points treatments.


> James,
>
> I read Soobok's proposal last week.
>
> Eric




From owner-idn@ops.ietf.org  Tue Oct 23 01:06:43 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07339
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 01:06:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vtSP-000Lek-00
	for idn-data@psg.com; Mon, 22 Oct 2001 21:46:29 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vtSO-000Lee-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 21:46:28 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9N4kXN15917;
	Tue, 23 Oct 2001 00:46:33 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110230446.f9N4kXN15917@nic-naa.net>
To: "Mark Davis" <mark@macchiato.com>
cc: "Soobok Lee" <lsb@postel.co.kr>, idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] call for comments for REORDERING 
In-Reply-To: Your message of "Mon, 22 Oct 2001 20:20:49 PDT."
             <006401c15b71$b6fb9e60$0c680b41@c1340594a> 
Date: Tue, 23 Oct 2001 00:46:33 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Mark,

...
> 2. If it were adopted, to ensure stability of IDN over time, the reordering
> should absolutely be permanent -- never changed in the future, even if new
> characters are added. ...

This is a different issue than the one raised by Erik Nordmark, which has to
do with WG process (exit criteria), and iterations of proposals to consider
reordering.

Does the same stability of IDN over time requirement lead to the same
conclusion for other transformations of blocks of code-points?

What is the "stability of IDN over time" requirement more specifically, and
in particular to reordering(s) that are not "absolutely [] permanent"? If
this question has already been answered, feel free to point to the item in
the archive where the answer can be found.

Eric



From owner-idn@ops.ietf.org  Tue Oct 23 01:08:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07522
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 01:08:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vtZx-000Lm0-00
	for idn-data@psg.com; Mon, 22 Oct 2001 21:54: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.33 #1)
	id 15vtZw-000Llt-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 21:54:16 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9N4s0N16099;
	Tue, 23 Oct 2001 00:54:00 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110230454.f9N4s0N16099@nic-naa.net>
To: "James Seng" <jseng@i-dns.net>
cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        "Soobok Lee" <lsb@postel.co.kr>, Marc.Blanchet@viagenie.qc.ca,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Re: suggestion: two prefices scheme for unassigned code points treatments. 
In-Reply-To: Your message of "Tue, 23 Oct 2001 12:50:48 +0800."
             <034b01c15b7e$48d77050$1301000a@jamessonyvaio> 
Date: Tue, 23 Oct 2001 00:54:00 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I read that also. What is your point?



From owner-idn@ops.ietf.org  Tue Oct 23 01:09:20 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07551
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 01:09:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vtMH-000LZO-00
	for idn-data@psg.com; Mon, 22 Oct 2001 21:40:09 -0700
Received: from smtp21.singnet.com.sg ([165.21.101.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vtMG-000LZI-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 21:40:08 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp21.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9N4etp30869;
	Tue, 23 Oct 2001 12:40:55 +0800
Message-ID: <02f401c15b7c$c3798d40$1301000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: "Soobok Lee" <lsb@postel.co.kr>, <Marc.Blanchet@viagenie.qc.ca>,
        <idn@ops.ietf.org>, <brunner@nic-naa.net>
References: <200110230414.f9N4EIN15179@nic-naa.net>
Subject: Re: [idn] Re: suggestion: two prefices scheme for unassigned code points treatments. 
Date: Tue, 23 Oct 2001 12:39:55 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Normally I wont bother with a reply on this, but:

1. When I speak as a co-chair, I will normally do so. Until then, I am
   a wg member like everyone else, entitled with my opinion. Do not
   confuse my various hats. I have too many of them, enough for you
   put my words into other context which is inappropriate.

2. Suggest you read the original proposal on two prefix *first* then
   maybe you could post something more technical constructive. Obviously
   from your questions, you have not even readLee's original proposal on
   two prefix.

-James Seng

----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
Cc: "Soobok Lee" <lsb@postel.co.kr>; <Marc.Blanchet@viagenie.qc.ca>;
<idn@ops.ietf.org>; <brunner@nic-naa.net>
Sent: Tuesday, October 23, 2001 12:14 PM
Subject: Re: [idn] Re: suggestion: two prefices scheme for unassigned
code points treatments.


> Co-chair James Seng wrote to Soobok Lee:
>
> > Other may be too polite to say this but this proposal is so absurb
that
> > I don't even know where to start.
>
> It is the job of a chair of an IETF WG have access to sufficient
expertise
> to "know where to start", and usually it is a plus if the chair is
civil.
>
> > [snip section on two prefix]
> > > halfbaked idea. welcome any corrections and suggestions.
> >
> > You got this part right tho.
>
> When a contributor to the IETF sollicits "corrections and
suggestions",
> he or she is working in the spirit of the IETF, which fundamentally is
> a body which coordinates and harmonizes "corrections and suggestions"
> (aka "interoperation") between network infrastructure implementors
through
> a formal specification process we refer to as "drafting protocols".
>
> Anyone who fails to understand specification of at least two
independent
> interoperable implementations from different code bases, with
sufficient
> successful operational experience, is the core criteria for an IETF
memo
> to be a draft standard, fails also to understand that only
constructive
> engagement between implementors leads to an interoperable outcome.
There
> is no place for non-constructive "wit", particularly in a chair.
>
> > Suggest you go work on it further. Do not think of this as a problem
of
> > "how can I get reordering into IDN" and forget the other issues of
> > general use of domain names, behavior and stability.
>
> Exactly how does transformations on code-blocks at some point within
the
> proposed framework (e.g., unicode, nameprep, reordering (tc,sc,jc,kc),
> amc-z|utf-8) have a non-interoperable manifestation as "general use of
> domain names, behavior and stability"?
>
> Eric
>




From owner-idn@ops.ietf.org  Tue Oct 23 01:24:19 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08536
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 01:24:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vtnl-000LzR-00
	for idn-data@psg.com; Mon, 22 Oct 2001 22:08: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.33 #1)
	id 15vtnk-000LzL-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 22:08:32 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9N58YN16449;
	Tue, 23 Oct 2001 01:08:34 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110230508.f9N58YN16449@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        "Soobok Lee" <lsb@postel.co.kr>, Marc.Blanchet@viagenie.qc.ca,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Re: suggestion: two prefices scheme for unassigned code points treatments. 
In-Reply-To: Your message of "Tue, 23 Oct 2001 12:39:55 +0800."
             <02f401c15b7c$c3798d40$1301000a@jamessonyvaio> 
Date: Tue, 23 Oct 2001 01:08:34 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James,

You are correct, you have a right to participate as an individual contributor,
not only as a co-chair.

That said, your reply to Soobok had no technical content and is wasted bits
in everyone's mail queue.

Eric



From owner-idn@ops.ietf.org  Tue Oct 23 01:27:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08788
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 01:27:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vtsm-000M4S-00
	for idn-data@psg.com; Mon, 22 Oct 2001 22:13:44 -0700
Received: from smtp23.singnet.com.sg ([165.21.101.203])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vtsl-000M4K-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 22:13:43 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp23.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9N5G0x25943;
	Tue, 23 Oct 2001 13:16:00 +0800
Message-ID: <03d501c15b81$749eaf70$1301000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        "Soobok Lee" <lsb@postel.co.kr>, <Marc.Blanchet@viagenie.qc.ca>,
        <idn@ops.ietf.org>
References: <200110230508.f9N58YN16449@nic-naa.net>
Subject: Re: [idn] Re: suggestion: two prefices scheme for unassigned code points treatments. 
Date: Tue, 23 Oct 2001 13:13:30 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I accept that if that is your opinion of my comments.

-James Seng

> You are correct, you have a right to participate as an individual
contributor,
> not only as a co-chair.
>
> That said, your reply to Soobok had no technical content and is wasted
bits
> in everyone's mail queue.
>
> Eric




From owner-idn@ops.ietf.org  Tue Oct 23 02:27:28 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20350
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 02:27:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vukN-000Mdx-00
	for idn-data@psg.com; Mon, 22 Oct 2001 23:09:07 -0700
Received: from imo-m09.mx.aol.com ([64.12.136.164])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vukM-000Mdr-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 23:09:06 -0700
Received: from DougEwell2@cs.com
	by imo-m09.mx.aol.com (mail_out_v31_r1.8.) id i.c3.17f24fee (4215);
	Tue, 23 Oct 2001 02:08:59 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <c3.17f24fee.2906637b@cs.com>
Date: Tue, 23 Oct 2001 02:08:59 EDT
Subject: [idn] Versioning schemes (was: Which lanuages/scripts to reorder?)
To: idn@ops.ietf.org
CC: Erik.Nordmark@eng.sun.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a message dated 2001-10-22 7:27:01 Pacific Daylight Time, 
Erik.Nordmark@eng.sun.com writes:

>  One issue with reordering that hasn't been put on the table
>  is that, as a process, I'm concerned that it might never complete.

This is indeed an important concern, and we need to look at this notion of 
versioning from a practical perspective.

Consider the GIF standard for graphic files, plain old garden-variety 
pictures.  The original GIF specification included a signature with a version 
number, so that new versions could be easily distinguished from old versions. 
 And in fact there was an original "GIF87a" standard and a "GIF89a" upgrade, 
which added things like transparency, interlacing, and multiple images.  
However, the presence of these two versions caused noticeable confusion in 
the marketplace, and despite the subsequent demand for further improvements 
to GIF (such as 24-bit color), there was never an upgrade beyond GIF89a, 
largely because of the versioning problems (as well as the well-known patent 
debacle).

The PNG (Portable Network Graphics) standard, invented to replace GIF, was 
designed with an even smarter versioning scheme.  The entire file format was 
built as a series of "blocks."  Each block was tagged to indicate whether it 
was essential or optional to the rendering of the image, and new blocks could 
be added with impunity, since processors would presumably be able to know 
which non-essential blocks could be safely ignored.  Yet, when the most 
obvious shortcoming of PNG was finally fixed (lack of support for multiple 
images), it was not added to the PNG format itself.  Rather, a new, related 
format (MNG) appeared, apparently because existing PNG processors had not in 
fact been built to handle new and unexpected blocks.

XML, possibly the most talked-about new file format in recent memory, has its 
own versioning scheme.  XML files are tagged in a prominent way with their 
version number.  But so far, all we have seen is version 1.0, despite some 
major improvements to XML (such as namespaces) and some non-trivial changes 
in the Unicode standard atop which XML is built.  The XML "Blueberry" 
proposal, which supports the latest changes in Unicode, has met with hot 
debate from those who fear that even a second version of XML would cause 
great instability to the XML standard.

Even Unicode/10646 is sometimes criticized (although usually by those who 
have much to learn) for its "ever-changing" nature, even though most of its 
changes consist of adding new characters.

The bottom line is that creating a new standard, such as the Lee reordering 
proposal, with an eye already cast toward version 1.1, version 2.0, etc. 
isn't as straightforward as it may seem.  There is the inherent instability 
of having two or more versions in the first place, and on top of that, there 
is the perception -- right or wrong -- of instability that has already 
delayed or stalled upgrades to standards like GIF, PNG, and XML.

Just something to think about before we decide that calling one version 
"zq--" and another version "uq--" will solve all the problems for software 
that has to perform IDN conversions.

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Tue Oct 23 02:34:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20756
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 02:34:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vukE-000Mdn-00
	for idn-data@psg.com; Mon, 22 Oct 2001 23:08:58 -0700
Received: from imo-m09.mx.aol.com ([64.12.136.164])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vukD-000Mdh-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 23:08:57 -0700
Received: from DougEwell2@cs.com
	by imo-m09.mx.aol.com (mail_out_v31_r1.8.) id i.164.2b71e6d (4215);
	Tue, 23 Oct 2001 02:08:50 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <164.2b71e6d.29066372@cs.com>
Date: Tue, 23 Oct 2001 02:08:50 EDT
Subject: Re: [idn] REORDERING: stability issues and UTC solutions
To: idn@ops.ietf.org
CC: lsb@postel.co.kr
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a message dated 2001-10-22 8:41:07 Pacific Daylight Time, lsb@postel.co.kr 
writes:

>  Instead of NFC, some script may need CASE mappings, i guess.
>  Current nameprep/ACE produce case-insensitively equivalent labels
>  for IDN  X.com and x.com.
>  Do you mean that all newly added SCRIPT won't have any case mapping ?

Of course there will be new scripts added to Unicode/10646 that have case 
mappings (although those proposed for Unicode 3.2 do not).  But I thought we 
were talking about reordering, not case mappings. I fear, once again, that 
the subject is being changed to divert us from the real issues surrounding 
the reordering proposal.

>  Doug, 
>  If you have lists of new scripts pending for approval,
>  please post them to this list for non-unicode experts.

See <http://www.unicode.org/pending/pending.html>.  This location always has 
the most up-to-date list of proposed scripts, along with an indication of how 
far along the "pending" path they are.

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Tue Oct 23 02:37:35 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20967
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 02:37:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vuw2-000Mlq-00
	for idn-data@psg.com; Mon, 22 Oct 2001 23:21:10 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vuw0-000Ml2-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 23:21:08 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 4C1B97F4D9; Tue, 23 Oct 2001 15:20:30 +0900 (JST)
Message-Id: <4.2.0.58.J.20011023120739.03830630@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 23 Oct 2001 12:36:55 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
Cc: <DougEwell2@cs.com>
In-Reply-To: <004901c15b29$0c552d20$ec1bd9d2@temp>
References: <C110A2268F8DD111AA1A00805F85E58D0115ACBC@ntgbg1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 03:40 01/10/23 +0900, Soobok Lee wrote:

>----- Original Message -----
>From: "Karlsson Kent - keka" <keka@im.se>
> >
> > > I know current NFC/NFKC has *severely flawed* hangul jamo
> >
> > Now that's a new complaint.  At least to me.  Not even the
> > delegations from DPRK complain about that. (And they have
> > all sorts of complaints.)  Do you care to say a little bit
> > more about what you mean?  Or are we just to take your word
> > for it?  There was a problem in earlier drafts of UAX 15
> > concerning Hangul and NFKC (Hangul syllables were not preserved),
> > but that problem was removed before that UTR became a UAX.
>
>two problems:
>
>  1) NFKC maps   compatibility hangul jamo (U+32??) into
>                 conjoining hangul jamo without fillers.

Well, NFKC is just a combination of many kinds of mappings,
and in most cases should be applied piece-by-piece, not
wholesale.


>  2) NFC  does not combine  archaic(old) hangul trailing jamo into the
>      preceding half-combined syllable (from choseong jamo + jungseong jamo),
>       but leave it alone as an isolated conjoining jamo.

Yes. To give a bit more of a background to those not too familiar
with the topic, Hangul Jamo can be categorized along two axes:

Position:
- Initial consonants (or consonant clusters)
- Vowels (or vowel clusters)
- Final consonants (or consonant clusters)

History:
- Used in modern times
- Historical use only

This gives six categories: Im, Ih, Vm, Vh, Fm, Fh

The huge block of 11172 is the result of forming all
the following combinations:

- Im Vm      (for later reference, let's denote that by IV)
- Im Vm Fm   (for later reference, let's denote that by IVF)

NFC (and therefore NFKC, by the fact that composition in NFKC is
the same as in NFC) whenever possible tries to use the precomposed
IV or IVF, rather than the individual Im, Vm, and Fm.

There was a design choice to make for the case where historical
components (Jamos) get involved. In all the following cases:

- Im Vh
- Im Vh Fm
- Im Vh Fh
- Ih Vm
- Ih Vm Fm
- Ih Vm Fh
- Ih Vh
- Ih Vh Fm
- Ih Vh Fh

It is not possible to do any composition, because the combinations
are not available. However, in the case of

- Im Vm Fh

i.e. a modern initial, a modern vowel (cluster), followed by a
historical final, the question was whether this should result in

a) IV Fh
b) Im Vm Fh

The arguments for the first were to precompose as much as possible
and to avoid to have to do lookahead. The arguments for the second
might have been that historical texts would be treated more uniformly
(which doesn't apply because syllables such as Im Vm Fm -> IVF
occur in historical texts and by NFC are definitely recomposed),
or that historical syllables might be treated more uniformly
(a syllable would be either completely decomposed or completely
precomposed). The second argument has some point, but neither
linguistic analysis (for which NFD is best) nor rendering
(which has to deal with lots of combinations anyway) are
severely affected.


>     That means archail hangul syllable which has old hangul trailing jamo
>       cannot be preserved through out NFKC.

First, NFKC isn't an issue here. It's the same for NFC. Second, the actual
syllable is always preserved, whether as IV Fh or whether as Im Vm Fh.
These represent one and the same thing (and that's why we need some kind
of normalization in the first place).


>     NFKC cannot be used for scholarly texts which contains archail hangul
>       syllables.

Again, it's an issue that applies to both NFKC and NFC.
And both can be used for archaic hangul syllables without
any problems.


>This fault was found by Martin, too lately.

It's not a fault, it's by design. And it wasn't found lately, either.
Actually, I remember that it was explicitly discussed at an Unicode
Technical Committee meeting in which I participated by phone.


>Mark and Martin knew and told me why this happened.
>Martin, would you comment on this?

As done above. Hope this helps.


Regards,   Martin.



From owner-idn@ops.ietf.org  Tue Oct 23 02:37:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20969
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 02:37:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vuw3-000Mlu-00
	for idn-data@psg.com; Mon, 22 Oct 2001 23:21:11 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vuw0-000Ml6-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 23:21:09 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 259C97F4DD; Tue, 23 Oct 2001 15:20:32 +0900 (JST)
Message-Id: <4.2.0.58.J.20011023141249.05a45620@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 23 Oct 2001 14:19:48 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, <DougEwell2@cs.com>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
In-Reply-To: <006e01c15aec$2a367c00$ec1bd9d2@temp>
References: <4.2.0.58.J.20011019155811.03d67490@localhost>
 <4.2.0.58.J.20011022121250.037081e0@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 20:24 01/10/22 +0900, Soobok Lee wrote:
>Thanks for detailed history of Hangul in unicode.
>But including 11172 hangul made Unicode more useful and
>widely acceptable to korean community, because existing
>KS5601's 2350 or more hangul has been criticized for not being
>able to serve many scholarly purpose or book publishings.
>
>The pain for inclufing 11172 hangul  was REWARDED!

It was quite a pain. And it is the reason you are now
asking for reordering, which would again be a very
serious pain, with not enough rewards.

If you could chose among:

a) Having the Unicode 1.1 layout, with the rest of the
    modern syllables either encoded with Jamos or in
    a separate area, thus favoring compression with
    ACE-Z over regularity.

b) Having the current block, without reordering, and
    therefore with slight inefficiency for ACE-Z.

Which one would you chose? Which one would other
people in Korea prefer, according to your opinion?

At some point, we cannot have the cake and eat it too.

Regards,   Martin.



From owner-idn@ops.ietf.org  Tue Oct 23 02:39:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21096
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 02:39:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vuwA-000Mm0-00
	for idn-data@psg.com; Mon, 22 Oct 2001 23:21:18 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vuw0-000Ml5-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 23:21:09 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 7CFC77F4DC; Tue, 23 Oct 2001 15:20:31 +0900 (JST)
Message-Id: <4.2.0.58.J.20011023135652.059ce4f0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 23 Oct 2001 14:10:20 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, "Mark Davis" <mark@macchiato.com>,
        "Karlsson Kent - keka" <keka@im.se>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
Cc: <DougEwell2@cs.com>
In-Reply-To: <016501c15b78$1d38a820$ec1bd9d2@temp>
References: <C110A2268F8DD111AA1A00805F85E58D0115ACBC@ntgbg1>
 <004901c15b29$0c552d20$ec1bd9d2@temp>
 <00b501c15b74$45047ae0$0c680b41@c1340594a>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 13:06 01/10/23 +0900, Soobok Lee wrote:

>----- Original Message -----
>From: "Mark Davis" <mark@macchiato.com>

> > 2. NFC does not combine ancient Hangul into syllables because there are no
> > syllables that have ancient Hangul in them. It does combine as many modern
> > Jamo as possible into syllables. That does not -- at all -- prevent the use
> > of NFC with ancient Hangul.
>
>Rendering problem remains unsolved.

What do you mean? Not all current implementations may be able to
render IV Fh correctly, but it's very easy to change the implementation
to do it correctly (assuming the application already renders
Im Vm Fh).


>"hangul  syllable ga + old jamo bansioth " != "old hangul syllable 
>ga+bansioth".

What kind of evidence do you have for the 'not equal'?

>There is defined no such false equivalence  in UTR15.

There is no character for "old hangul syllable ga+bansioth",
so in that sense indeed UTR 15 doesn't define such an equivalence.
What UTR 15 defines is the following equivalence

    Im Vm Fh <==> IV Fh
      (NFD)       (NFC)

This equivalence is clearly defined in UTR 15, in the same way
the following equivalences are defined:

    Im Vm Fm <==>   IV Fm   <==> IVF
     (NFD)     (intermediate)   (NFC)

UTR 15 doesn't have the concept of false equivalence.

>  Why rendering engine vendors should  make such false workarounds not
>recommended in UTC standards?

There is nothing false with making sure IV Fh is correctly
rendered. For some implementations, it may be a bit of a
workaround, but it's a very easy one.

Also UTR 15 (also called UAX 15) is an integral part of the Unicode
Standard. Please see http://www.unicode.org/unicode/reports/:

 >>>>
A Unicode Standard Annex (UAX) forms an integral part of the Unicode
Standard, carrying the same version number as the standard, but is
published as a separate document. Note that conformance to a version
of the Unicode Standard includes conformance to its Unicode Standard
Annexes.
 >>>>

It may be true that there is no part of The Unicode Standard that
explicitly says that IV Fh should be rendered as a single syllable
block, but there are many, many other details about rendering that
The Unicode Standard doesn't say explicitly.


>NFC is  dangerous for ancient hangul.

I wouldn't know why. If you know, please explain.


Regards,    Martin.



From owner-idn@ops.ietf.org  Tue Oct 23 02:44:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21407
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 02:44:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vuw7-000Mlx-00
	for idn-data@psg.com; Mon, 22 Oct 2001 23:21:15 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vuw0-000Ml3-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 23:21:08 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id E03DB7F457; Tue, 23 Oct 2001 15:20:29 +0900 (JST)
Message-Id: <4.2.0.58.J.20011023120325.0356c100@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 23 Oct 2001 12:04:16 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] call for comments for REORDERING
In-Reply-To: <004e01c15ae7$ba4761b0$ec1bd9d2@temp>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <024b01c15847$11e8b430$0501000a@jamessonyvaio>
 <4.2.0.58.J.20011019152610.037f1100@localhost>
 <4.2.0.58.J.20011019180625.038105d0@localhost>
 <4.2.0.58.J.20011022114545.02c1ae70@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 19:53 01/10/22 +0900, Soobok Lee wrote:

>----- Original Message -----
>From: "Martin Duerst" <duerst@w3.org>
>  > What I meant is that e.g. somebody goes ahead and
> > implements reordering based on one of your tables.
> > Then e.g. the IETF includes reordering in IDN
> > (Don't misunderstand me, this is only an example,
> > of course I think this should never happen.), but
> > with a different table based on newer statistics.
> > The original implementer doesn't catch that he has
> > a different table, and as a result, we have total
> > chaos, nothing matches.
>
>But newer reordering table with newer statistics
>cannot be deployed without new ACE PREFIX, as i said many times.

Hello Soobok,

I'm speaking about a BUG, without changing the prefix.
Bugs happen, unfortunately.

Regards,   Martin.




From owner-idn@ops.ietf.org  Tue Oct 23 02:57:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22178
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 02:57:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vvJw-000NIP-00
	for idn-data@psg.com; Mon, 22 Oct 2001 23:45:52 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vvJv-000NIG-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 23:45:51 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP id E5FC6FFC12
	for <idn@ops.ietf.org>; Tue, 23 Oct 2001 14:46:11 +0800 (SGT)
Message-ID: <023a01c15b8e$5b8d6000$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <idn@ops.ietf.org>
References: <065601c150a4$f907ef70$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] core interest of the wg
Date: Tue, 23 Oct 2001 14:45: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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> UDNS & UNAME have been removed from the core interest of the wg. In
> addition, with the selection of AMC-Z as the choosen ACE, the
following
> I-Ds will also be removed from core interest as it is not relevant
> anymore.
>
> MACE: Modal ASCII Compatible Encoding for IDN (draft-ietf-idn-mace)
> DUDE: Differential Unicode Domain Encoding(draft-ietf-idn-dude)
> Evaluation of various ACEs with existing Japanese Domain Names
> (draft-ietf-idn-ace-eval-jp)

I missed one more "ACE" draft

StepCode- A Mnemonic Internationalized Domain Name Encoding
(draft-ietf-idn-step)

-James Seng




From owner-idn@ops.ietf.org  Tue Oct 23 03:04:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22731
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 03:04:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vvG6-000ND4-00
	for idn-data@psg.com; Mon, 22 Oct 2001 23:41:54 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vvG6-000NCw-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 23:41:54 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VVF1gEtSAG2VNYSAri95ZrMQ==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GJETP4R2; Tue, 23 Oct 2001 02:41:01 EDT
To: david.hopwood@zetnet.co.uk
Cc: idn@ops.ietf.org
Date: Mon, 22 Oct 2001 22:57:23 -0700
Subject: Re: [idn] proposed wg charter, goal & milestone update
Message-ID: <20011022.225726.-150955.0.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.5
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-5,7-69
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana Ye <liana.ydisg@juno.com>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I have seen domain names and host names are used 
interchangeably.  What is the difference?  Do anyone 
care to give a little more context?

Liana

On Tue, 23 Oct 2001 03:56:46 +0100 David Hopwood
<david.hopwood@zetnet.co.uk> writes:
> -----BEGIN PGP SIGNED MESSAGE-----
> 
> James Seng/Personal wrote:
> > Apologise for the late update as it taken some time to get the 
> wordings
> > right. I shall list all the changes first and then the complete 
> charter
> > below. Please comment.
> > 
> > Changes 1: Add wordings to clarify the concept of "names vs 
> identifiers"
> > 
> > "Domain names is one form of identifier. It does not have the 
> technical
> > capability to encode names or languages information."
> 
> The DNS *could* encode language/script information (or relations 
> between
> corresponding names in different languages/scripts); all that would 
> need
> is a new RR. What is true is that the names themselves are not 
> language-
> tagged.
> 
> Also, the requirements draft makes a useful distinction between 
> domain
> names (which are octet strings) and host names (which are character
> strings). Both are identifiers.
> 
> I suggest:
> 
>   "Domain names and host names are forms of identifier. Language
>   information is not encoded in these names; that is, names from
>   different languages are defined in a single namespace."
> 
> - -- 
> 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
> 
> iQEVAwUBO9TcUTkCAxeYt5gVAQHhzgf8CpwK9G3h3uHIBOHWirYBHsWKuo/TlqFQ
> vzYCva6JxWOP+QVU2XY194bE7qtw1h5qof8XPCk4MPYwOjDm6XEk4XsY8zibVZhw
> sMJKrn3CftnZVpTo1zPGyw9ooDe/3hAmq4lAW51MOeaLsPuMFDziA8+JVuhEE2++
> wVPg5oQLbWS0K6vKYF8B2ig45CZGBqv/sWJH730sjeOe0IFe3VDqpsO/aNnIbAvX
> medRFKdWwruMN82jxrgNAmZuA+hYcQrC3NSoucw97m8VD4MA2DS4V6ll+6tvYxdK
> eR9B1ylHjvKwfcLD0/VIVvKaNZN0qHWiGjo9jyraQ3v3Gjdbn5Crww==
> =ao+f
> -----END PGP SIGNATURE-----
> 



From owner-idn@ops.ietf.org  Tue Oct 23 03:21:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23223
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 03:21:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vvgK-000Npq-00
	for idn-data@psg.com; Tue, 23 Oct 2001 00:09:00 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vvgI-000Npi-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 00:08:59 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 6BF2EFFC13; Tue, 23 Oct 2001 15:09:15 +0800 (SGT)
Message-ID: <034101c15b91$94289e40$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <david.hopwood@zetnet.co.uk>, "liana Ye" <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>
References: <20011022.225726.-150955.0.liana.ydisg@juno.com>
Subject: Re: [idn] proposed wg charter, goal & milestone update
Date: Tue, 23 Oct 2001 15:08:55 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

See Section 1.3 of draft-ietf-idn-requirements-08.txt

But please dont rehash old arguments on domain names & host names. It is
a story which have no right answer. Go thru the archives (early 2000) if
you want.

-James Seng

----- Original Message -----
From: "liana Ye" <liana.ydisg@juno.com>
To: <david.hopwood@zetnet.co.uk>
Cc: <idn@ops.ietf.org>
Sent: Tuesday, October 23, 2001 1:57 PM
Subject: Re: [idn] proposed wg charter, goal & milestone update


> I have seen domain names and host names are used
> interchangeably.  What is the difference?  Do anyone
> care to give a little more context?
>
> Liana
>
> On Tue, 23 Oct 2001 03:56:46 +0100 David Hopwood
> <david.hopwood@zetnet.co.uk> writes:
> > -----BEGIN PGP SIGNED MESSAGE-----
> >
> > James Seng/Personal wrote:
> > > Apologise for the late update as it taken some time to get the
> > wordings
> > > right. I shall list all the changes first and then the complete
> > charter
> > > below. Please comment.
> > >
> > > Changes 1: Add wordings to clarify the concept of "names vs
> > identifiers"
> > >
> > > "Domain names is one form of identifier. It does not have the
> > technical
> > > capability to encode names or languages information."
> >
> > The DNS *could* encode language/script information (or relations
> > between
> > corresponding names in different languages/scripts); all that would
> > need
> > is a new RR. What is true is that the names themselves are not
> > language-
> > tagged.
> >
> > Also, the requirements draft makes a useful distinction between
> > domain
> > names (which are octet strings) and host names (which are character
> > strings). Both are identifiers.
> >
> > I suggest:
> >
> >   "Domain names and host names are forms of identifier. Language
> >   information is not encoded in these names; that is, names from
> >   different languages are defined in a single namespace."
> >
> > - --
> > 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
> >
> > iQEVAwUBO9TcUTkCAxeYt5gVAQHhzgf8CpwK9G3h3uHIBOHWirYBHsWKuo/TlqFQ
> > vzYCva6JxWOP+QVU2XY194bE7qtw1h5qof8XPCk4MPYwOjDm6XEk4XsY8zibVZhw
> > sMJKrn3CftnZVpTo1zPGyw9ooDe/3hAmq4lAW51MOeaLsPuMFDziA8+JVuhEE2++
> > wVPg5oQLbWS0K6vKYF8B2ig45CZGBqv/sWJH730sjeOe0IFe3VDqpsO/aNnIbAvX
> > medRFKdWwruMN82jxrgNAmZuA+hYcQrC3NSoucw97m8VD4MA2DS4V6ll+6tvYxdK
> > eR9B1ylHjvKwfcLD0/VIVvKaNZN0qHWiGjo9jyraQ3v3Gjdbn5Crww==
> > =ao+f
> > -----END PGP SIGNATURE-----
> >
>




From owner-idn@ops.ietf.org  Tue Oct 23 03:26:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23249
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 03:26:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vvoR-000Nua-00
	for idn-data@psg.com; Tue, 23 Oct 2001 00:17:23 -0700
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vvoP-000NuS-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 00:17:21 -0700
Received: from zetnet.co.uk (man-s363.dialup.zetnet.co.uk [194.247.45.234])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f9N7HEp18615
        for <idn@ops.ietf.org>; Tue, 23 Oct 2001 08:17:14 +0100
Message-ID: <3BD5197B.1C280C5D@zetnet.co.uk>
Date: Tue, 23 Oct 2001 08:17: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: idn@ops.ietf.org
Subject: [idn] NFC vs NFKC
References: <200109181333.JAA19941@ietf.org>
			 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
			 <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <4.2.0.58.J.20011018183339.031fa100@localhost> <3BD0C257.A61BE893@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:
> ... I've been preparing a detailed rationale for using NFC in
> preference to NFKC, that considers all the categories of compatibility
> mappings. I'll post it tomorrow.

Took me a bit longer than I thought to finish, but here it is:

- -----
This post categorises and describes all of the compatibility
mappings in Unicode 3.1. The intention is to show that these
mappings are of little value for name preparation, because in
almost all cases, one or more of the following applies:

DISALLOWED: the source characters are already disallowed by
   nameprep-06, so removing the mapping has no effect.
NOT-USEFUL: the source characters are not useful in domain names.
PUNCT-SYMBOL: the source characters are punctuation or symbols,
   similar to characters that are disallowed for ASCII.
NOT-EQUIV: the source characters are not semantically equivalent
   to the target characters - i.e. folding them would be more
   confusing than not folding them (if, for the sake of argument,
   they were allowed).
LEGACY: the source characters are *only* intended to be used for
   round-trip mappings from legacy charsets.
DEPRECATED: the source characters are formally deprecated by
   Unicode 3.1.
OBSCURE: the source characters are very difficult to type, or
   produce using an input method, so not folding them is unlikely
   to cause any practical difficulty to users.
INTERNAL: the source characters are normally only intended for
   internal use within an application or rendering engine.
INCONSISTENT: a category of mappings is arbitrary and inconsistent,
   with only some of the potential mappings in that category being
   defined as compatibility equivalences.

There are a very small number of exceptions:

EXCEPTION: the mapping could be quite useful, and there is no
   reason to exclude it on any of the grounds above.

I claim that there are few enough exceptions to show that NFKC
is not the right mapping to use: *if* some of these [EXCEPTION]
mappings are wanted, they should be handled as an additional step
to NFC normalisation (similar to the mapped-out characters).


Here are the mapping categories. They're in no particular order,
and some characters appear in more than one category.

<nobreak>
  The source character is a non-breaking version of the target
  character:
    00A0 NO-BREAK SPACE                       [DISALLOWED]
    0F0C TIBETAN MARK DELIMITER TSHEG BSTAR   [NOT-USEFUL; see below]
    2007 FIGURE SPACE                         [DISALLOWED]
    2011 NON-BREAKING HYPHEN                  [EXCEPTION]
    202F NARROW NO-BREAK SPACE                [DISALLOWED]

  Tibetan script consists of morphemes separated by tseks (also
  transliterated as "tsheg"); see section 9.13 of the Unicode
  standard. U+0F0C is a non-breaking tsek (the character name is
  a mistake). In domain names, either an ordinary tsek (U+0F0B),
  or a hyphen should be used instead.

  It's possible that a document might use a non-breaking hyphen
  to prevent a domain name or URI being split over lines, and it
  could be useful to map it to a hyphen when cutting and pasting,
  so this is an [EXCEPTION].

<super> and <sub>
  The source character is a superscripted or subscripted version of
  the target character. These can be further categorised as:

    letters (ordinal indicators, modifier letters, and 'n')
       [NOT-EQUIV]

    digits [NOT-USEFUL, OBSCURE, NOT-EQUIV]

    symbols (including superscript SM and TM)
       [NOT-USEFUL, OBSCURE, NOT-EQUIV]

    Kanbun (annotation of classical Chinese in Japanese texts)
       [NOT-USEFUL, OBSCURE, NOT-EQUIV]

  Whether the letters are useful is arguable, but if they are, they
  should not be folded (since they are definitely not semantically
  equivalent to the target character).

<fraction>
  Various legacy character sets have characters for fractions, e.g.
  1/2, etc. [LEGACY, OBSCURE, NOT-USEFUL].

<circle> and <square>,
also <compat> 3036 CIRCLED POSTAL MARK

  Circled and squared variants. [NOT-USEFUL, NOT-EQUIV]

  (Note that the decomposition is to the uncircled/unsquared character
  on its own, without a U+20DD COMBINING ENCLOSING CIRCLE or
  U+20DE COMBINING ENCLOSING SQUARE. So the effect of this folding
  is that names with and without the circle/square are equivalent,
  despite being visually distinct.)

<wide> Full-width variants
  FF01..FF0C Full-width symbols/punctuation        [DISALLOWED, PUNCT-SYMBOL]
  FF0E       FULLWIDTH FULL STOP                   [DISALLOWED]
  FF0F       FULLWIDTH SOLIDUS                     [DISALLOWED, PUNCT-SYMBOL]
  FF1A..FF20 Full-width symbols/punctuation        [DISALLOWED, PUNCT-SYMBOL]
  FF3B..FF40 Full-width symbols/punctuation        [DISALLOWED, PUNCT-SYMBOL]
  FFE0..FFE6 Full-width symbols                    [PUNCT-SYMBOL]

  FF0D       FULLWIDTH HYPHEN-MINUS                [EXCEPTION]
  FF10..FF19 FULLWIDTH DIGIT ZERO..NINE            [EXCEPTION]
  FF21..FF3A FULLWIDTH LATIN CAPITAL LETTER A..Z   [EXCEPTION]
  FF41..FF5A FULLWIDTH LATIN SMALL LETTER A..Z     [EXCEPTION]

  CJK input methods can sometimes produce full-width characters,
  and it may be useful to map these to half-width (normal) LDH
  ASCII characters.

  However, nameprep is probably not the best place to do that.
  Doing it there would mean that it is valid for full-width ASCII
  to appear in an encoded name [*]. This will display as replacement
  boxes when viewed on a system without CJK fonts. It would be far
  preferable to make sure that encoded names always use normal
  ASCII. That suggests doing this folding in name input widgets,
  and/or defining a way to tell input methods when a domain name (or
  similar identifier) is being entered.

  Note that CJK users already have to set input methods to produce
  half-width ASCII characters, in order to type existing LDH ASCII
  domain names. So although this folding may improve usability, it
  isn't essential.

  [*] I'm making the assumption that whatever IDN solution is chosen
      will allow names to be encoded transparently in at least some
      cases, i.e. it won't force ACE to be used everywhere.

<narrow>
  FF61..FF64 Half-width punctuation          [PUNCT-SYMBOL]
  FF65..FF9F Half-width Katakana             [EXCEPTION]
  FFE8..FFEE Half-width symbols              [PUNCT-SYMBOL]

  The same comments apply to half-width Katakana as to the <wide>
  mappings above.

<compat>, <narrow> Hangul Compatibility Jamo
  3131..318E Full-width Compatibility Jamo
  FFA0..FFDC Half-width Compatibility Jamo

  The normal set of Jamo encoded at 1100..1100 is conjoining, that
  is, sequences of Jamo are displayed as, and are NFC-equivalent
  to, the corresponding syllables. The Compatibility Jamo (both
  full-width and half-width) are non-conjoining, i.e. they each
  take up a character cell; that is the only reason why they were
  encoded separately.

  So, the effect of using NFKC is that a domain name could be
  displayed with Jamo in separate character cells, but would
  actually be equivalent to the corresponding name displayed as
  syllables. I can't see any reason why that would be desirable.

  Also, section 10.4 of [Unicode3.0] says, "These characters are
  provided solely for compatibility with the KS C 5601 standard."
  [LEGACY, NOT-EQUIV].

<small>
  These are all in the CJK Compatibility Forms block (FE30..FE44).
  They were only encoded for compatibility with CNS 11643.

  Most are [DISALLOWED] because the corresponding ASCII symbol
  is disallowed; the following are not:
    FE51 SMALL IDEOGRAPHIC COMMA              [LEGACY, PUNCT-SYMBOL]
    FE58 SMALL EM DASH                        [LEGACY, PUNCT-SYMBOL]
    FE5D SMALL LEFT TORTOISE SHELL BRACKET    [LEGACY, PUNCT-SYMBOL]
    FE5E SMALL RIGHT TORTOISE SHELL BRACKET   [LEGACY, PUNCT-SYMBOL]
    FE63 SMALL HYPHEN-MINUS                   [LEGACY]

  Note that it would probably be more useful for a converter from
  CNS 11643 to map to the ordinary variants of these characters,
  anyway, rather than the small variants, which no-one uses.

<compat> Overline variants
  FE49..FE4C
  [NOT-USEFUL, PUNCT-SYMBOL]

<compat> Spaces
  (mapping is U+0020 SPACE; also <wide> 3000 IDEOGRAPHIC SPACE).
  [DISALLOWED]

<compat> Spacing marks
  (mapping starts with U+0020 SPACE)
  These are mappings from a spacing diacritical mark, to <space> +
  the corresponding combining mark. They are [DISALLOWED] because
  the <space> is disallowed.

<compat> Maps to disallowed ASCII (other than space)
  2024 ONE DOT LEADER
  2025 TWO DOT LEADER
  2026 HORIZONTAL ELLIPSIS
  203C DOUBLE EXCLAMATION MARK
  2048 QUESTION EXCLAMATION MARK
  2049 EXCLAMATION QUESTION MARK
  2474..2487 PARENTHESIZED DIGIT/NUMBER ONE..TWENTY
  2480..249B DIGIT/NUMBER ONE..TWENTY FULL STOP
  249C..245B PARENTHESIZED LATIN SMALL LETTER A..Z
  3200..321C PARENTHESIZED HANGUL *
  3220..3243 PARENTHESIZED IDEOGRAPH *
  FE4D DASHED LOW LINE
  FE4E CENTRELINE LOW LINE
  FE4F WAVY LOW LINE

  [DISALLOWED].

<compat> Hangzhou numerals
  3038 HANGZHOU NUMERAL TEN
  3039 HANGZHOU NUMERAL TWENTY
  303A HANGZHOU NUMERAL THIRTY

  These map to the ideographs U+5341 meaning ten (or complete or
  perfect), U+5344 meaning twenty, and U+5345 meaning thirty.
  I suspect that input methods will normally produce those
  ideographs, not the numeral characters (i.e. these characters
  are [OBSCURE]) - can anyone confirm that?

<compat> Ideographic telegraph symbols for months, hours, and days
  32C0..32CB
  3358..3370
  33E0..33FE

  These map to a decimal ASCII number, followed by the ideograph
  U+6708 (for months) or U+70B9 (for hours) or U+65E5 (for days).
  Again, I suspect that input methods will produce those sequences
  rather than the symbols. [OBSCURE].

<compat> CJK Radicals
  2E9F CJK RADICAL MOTHER
  2EF3 CJK RADICAL C-SIMPLIFIED TURTLE
  2F00..2FD5 KangXi radicals block

  See section 10.1 of [Unicode3.0] for a discussion of radicals. Their
  main uses are:
    - to categorize or collate ideographs (e.g. in an index)
    - to describe new ideographs, especially using the "ideographic
      description sequence" convention.

  The first of these isn't applicable to domain names, and nameprep
  already disallows ideographic description characters. Therefore,
  the simplest approach would be to disallow all radicals.

  Note that even if mapping from radicals to ideographs were a good
  idea, the selection of such mappings defined by NFKC is highly
  inconsistent - e.g. the following radicals from the CJK Radicals
  Supplement block correspond to unified ideographs:

    2E83 -> 4E5A  2E85 -> 4EB8  2E8E -> 5140  2E8F -> 5C23  2E90 -> 5C22
    2E92 -> 5DF3  2E96 -> 5FC4  2E98 -> 624C  2E9F -> 6BCD  2EC0 -> 535D
    2EA1 -> 6C35  2EA3 -> 706C  2EA8 -> 72AD  2EAD -> 793B  2EAF -> 7CF9
    2EB0 -> 7E9F  2EB1 -> 7F53  2EB2 -> 7F52  2EBD -> 81FC? 2EBE -> 8279
    2EC1 -> 864E  2EC2 -> 8864  2EC3 -> 8980  2EC8 -> 8BA0  2ECC -> 8FB6
    2ED0 -> 9485  2ED1 -> 9577  2ED2 -> 9578  2ED3 -> 957F  2ED4 -> 95E8
    2ED6 -> 961D  2ED8 -> 9752  2ED9 -> 97E6  2EDB -> 98CE  2EDC -> 98DE
    2EDD -> 98DF  2EDF -> 98E0  2EE0 -> 9963  2EE2 -> 9A6C  2EE3 -> 9AA8
    2EE5 -> 9C7C  2EE6 -> 9E1F  2EEA -> 9EFE  2EEC -> 9F50  2EEE -> 9F7F
    2EF0 -> 9F99  2EF1 -> 9F9C  2EF3 -> 9F9F

  but only two of these are compatibility mappings (2E9F and 2EF3).
  [NOT-USEFUL, NOT-EQUIV, INCONSISTENT]

  The Yi radicals should probably also be disallowed because they
  are not useful in domain names, even though they don't have any
  compatibility mappings.

<vertical>
  Presentation forms of symbols for use in vertical (top-to-bottom)
  layout. These are all in the Small Form Variants block (FE50..FE6B).
  These mappings are not useful because:

  - the corresponding left-to-right symbols are not normally
    used in domain names (most of them are brackets).
  - domain names are not normally laid out vertically (it would
    be better to use a left-to-right footnote in most cases).

  [NOT-USEFUL, PUNCT-SYMBOL]

<font>, <compat>, <initial>, <medial>, <final>, <isolated>
Presentation forms and some ligatures:

  Latin:    0132..0133, FB00..FB06
  Armenian: 0587, FB13..FB17
  Arabic:   0675..0678
  Lao:      0EDC..0EDD
  Hebrew:   FB20..FB29, FB4F
  Arabic:   <initial>, <medial>, <final>, <isolated>

  Presentation ligatures/forms are rendering variants, so these
  characters should not normally appear in external representations
  of text (they are often used internally as part of a rendering
  implementation, but that isn't relevant for nameprep).

  Note that the word "ligature" is overloaded: some ligatures behave
  like presentation forms (e.g. ff, fi, ffi, ij in Latin scripts),
  while others (e.g. oe and ae) are part of the spelling of words,
  such as "arch<ae>ology" (British English spelling). The argument
  above does not apply to the second type of ligature, but those
  don't have compatibility mappings.

  An input method/keyboard driver should never generate a ligature
  or presentation form, and lots of existing software would break
  if it did. (In general, language-specific rules are necessary to
  properly ligaturize text - e.g. in English the "ff" in "shelfful"
  should not ligaturize because the two "f"s are in different
  syllables.) Even if a user copies text containing presentation
  ligatures from a word processor, they will be decomposed on the
  clipboard, unless the word processor is completely broken in this
  respect.
  [INTERNAL, OBSCURE]

<compat> Deprecated characters
  0F77 TIBETAN VOWEL SIGN VOCALIC RR
  0F79 TIBETAN VOWEL SIGN VOCALIC LL

  The character descriptions say that "use of this character is
  strongly discouraged". (ISTR some text in the standard explaining
  why, but I can't find it now.)
  [DEPRECATED]

<compat> Combinations of spacing characters:
  013F LATIN CAPITAL LETTER L WITH MIDDLE DOT
  0140 LATIN SMALL LETTER L WITH MIDDLE DOT
  0149 LATIN SMALL LETTER N PRECEDED BY APOSTROPHE
  0E33 THAI CHARACTER SARA AM
  0EB3 LAO VOWEL SIGN AM
  1E9A LATIN SMALL LETTER A WITH RIGHT HALF RING

  These are combinations of characters that were encoded as a single
  character in other standards. The only reason why they aren't
  canonical equivalences, is that the decomposition is to two spacing
  characters, rather than a spacing character and a combining mark.

  These mappings could be treated as [EXCEPTION]s, although the
  combined characters are rare enough that it probably isn't worth
  the hassle to do that. I don't know whether they are produced by
  keyboard drivers.

<compat> Croatian digraphs:
  01C4..01CC
  01F1..01F3

  Chapter 7 of [Unicode3.0] says:

    Croatian Digraphs Matching Serbian Cyrillic Lettters.

    Serbo-Croatian is a single language with paired alphabets: a
    Latin script (Croatian) and a Cyrillic script (Serbian). A set
    of compatibility digraph codes is provided for one-to-one
    transliteration.

  IOW, these digraphs should occur only in text that has been
  automatically transliterated from Serbian to Croatian. Normally the
  digraph would be typed as two separate characters, so there is no
  need for a nameprep mapping. [OBSCURE]

<compat> Roman numerals
  2160..217F
  [NOT-USEFUL, OBSCURE]

<font>, <compat> Latin and Greek letter-like characters
  Most of the Letter-like Symbols block   [OBSCURE, NOT-USEFUL, NOT-EQUIV]
  00B5 MICRO SIGN                         [OBSCURE, NOT-USEFUL, NOT-EQUIV]
  20A8 RUPEE SIGN                    [INCONSISTENT, NOT-USEFUL, NOT-EQUIV]

  Various symbols that look like stylized letters, sometimes with
  mathematical meanings.

  (It's not clear why the Rupee sign should have a compatibility
  mapping to "Rs", when the same doesn't apply to other currency
  symbols - e.g. the Pesata sign does not have a compatibility
  mapping to "Pts". In any case, that doesn't really matter, since
  currency symbols are not useful in domain names.)

  Greek keyboard drivers will produce the "proper" lowercase mu
  character (U+03BC), not U+00B5.

  Note that the following are canonical equivalents, so they should
  not be disallowed (in order to satisfy the Unicode requirement of
  treating canonical equivalents identically):
    U+2126 OHM SIGN -> Omega
    U+212A KELVIN SIGN -> K
    U+212B ANGSTROM SIGN -> A with ring above

  All of the remaining Letter-like Symbols should be disallowed.

<font> Mathematical Alphanumeric Symbols block
  1D400..1D7FF

  These characters are for specialised use in mathematical text.
  (In fact the whole point of encoding them was that they are
  not semantically equivalent to the corresponding plain letters
  and digits - so folding them would be pointless.)

  [NOT-USEFUL, OBSCURE, NOT-EQUIV].

<compat> Greek symbols:
  03D0..03D6
  03F0..03F2
  03F4..03F5
  These are technical symbols, not normal Greek text.
  [NOT-USEFUL, OBSCURE, NOT-EQUIV]

<compat> Miscellaneous
  U+017F LATIN SMALL LETTER LONG S

  This is really a glyph variant of 's'. It is rarely used, so it
  doesn't really matter if it is not mapped to 's'. [OBSCURE].

<compat> Repeated characters
  2033 DOUBLE PRIME
  2034 TRIPLE PRIME
  2036 REVERSED DOUBLE PRIME
  2037 REVERSED TRIPLE PRIME
  203C DOUBLE EXCLAMATION MARK
  222C DOUBLE INTEGRAL
  222D TRIPLE INTEGRAL
  222F SURFACE INTEGRAL
  2230 VOLUME INTEGRAL

  [OBSCURE, PUNCT-SYMBOL].

- -- 
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

iQEVAwUBO9UXrDkCAxeYt5gVAQGspwf8DcHtURizKZj5I5mN/oE4krd7WfIXNwNj
F7KIdavHPkNrL9JUt9j1vBr8iJ7eaYaTZ0zns0l3kL9m9QUWpmCiuqyWsdRKPRJQ
w3mwDbartNV/en+OFp2qY8uHC1WAlcwZwcgS+RmSzfuSDdiYZ2gvXbySZjVNTAk1
+LjaGuoBu8bL+0YDNClWpwQha5uPUkYvw2WvKUr5+F0ASLwoMmSqnHSIlvHVX0rd
mOphfQfgo6k/4yG6YZKmp3F+8Onfs/IC2jZeorCWBMmre9uWO49Cf+WfO0C8CzOe
o17SWXla+oNqo5dasb9ewSAlehdGxMi5Lx4HDZoqshJe4Fh2P8Ea2A==
=iMh9
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Tue Oct 23 03:29:00 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20968
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 02:37:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vuw2-000Mlr-00
	for idn-data@psg.com; Mon, 22 Oct 2001 23:21:10 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vuw0-000Ml4-00
	for idn@ops.ietf.org; Mon, 22 Oct 2001 23:21:09 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 1BB9C7F4DB; Tue, 23 Oct 2001 15:20:31 +0900 (JST)
Message-Id: <4.2.0.58.J.20011023121348.0363c280@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 23 Oct 2001 12:16:44 +0900
To: Karlsson Kent - keka <keka@im.se>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: RE: [idn] call for comments for REORDERING
Cc: DougEwell2@cs.com, "'Soobok Lee'" <lsb@postel.co.kr>
In-Reply-To: <C110A2268F8DD111AA1A00805F85E58D0115ACBC@ntgbg1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 19:05 01/10/22 +0200, Karlsson Kent - keka wrote:

>And still it is not sufficient, since historic Hangul
>Jamo aren't covered by the precomposed Hangul syllable
>characters. I have also indications that many useful
>consonant (and vowel?) clusters aren't covered as separate
>(Jamo) characters, but have to be constructed from multiple
>'more basic' (non-cluster) Hangu Jamo characters.

Now that's new to me. Can you provide some evidence
(e.g. some scans)?

I use to write my last name as a Hangul syllable as a joke,
but as the 'rst' combination doesn't turn up in as a final
cluster, I have to do this using graphics. So I'm familliar
with the problem. But I assumed that all actual combinations
that have been used historically are actually available
in the Unicode Jamo block.


Regards,  Martin.




From owner-idn@ops.ietf.org  Tue Oct 23 05:18:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24259
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 05:18:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vxTe-000PXn-00
	for idn-data@psg.com; Tue, 23 Oct 2001 02:04:02 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vxTd-000PXa-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 02:04:02 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP id 1FB4F7F457
	for <idn@ops.ietf.org>; Tue, 23 Oct 2001 18:03:40 +0900 (JST)
Message-Id: <4.2.0.58.J.20011023171502.05811d00@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 23 Oct 2001 17:22:04 +0900
To: idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: [idn] half-width history (was: NFC vs NFKC)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dear IDN WG members,

This is a part of a message that I sent a while ago
to the nameprep design team about half-width Katakana
and full-width Latin. In the thread, somebody was makin
an analogy to upper/lower case, and how COBOL didn't
deal with the distinction, just to give you the context.

Regards,    Martin.


 >>>>>>>>

This is a completely inappropriate analogy. There are many very serious
differences between case and half-/full-width.

Upper/lower case is an important component of most writing systems
for languages using the relevant script. It is part of orthography,
and typography. Most people use the distinction also in handwriting.
It has been that way for about 500 years or so. Early computers had
very tight limitations, and ignored orthography and typography.
Fortunately, we are beyond this.


For half-width (kata)kana, the situation is completely reverse. It's
the equivalents of the 60's COBOL programmers that created them to
deal with the severe hardware limitations at that time. They are not
at all part of orthography or typography. They are not distinguished
in handwriting. They don't appear in any dictionary, or any serious
book or anything. Their use is very limited, in particular:

1) device limitations, e.g. the receipts printed by cash registers,
    displays on fax machines and copiers,... But not on mobile phones,
    which can use as many characters as Japanese PCs.

2) Sometimes in user interfaces on PCs where people try to be smart
    and save space by using half-width kana. Because a kanji can often
    replace several kana, and because in half-width kana, the diacritics
    take extra width, the saving of space is often minimal, but the
    decrease in legibility (using katakana instead of kanji and hiragana,
    and the half-width fonts having very bad legibility on their own)
    is often very drastic.

In addition, no Japanese input method produces half-width kana off
the shelf. The one I have has an option to prohibit half-width kana
alltogether. And Japanese email (using iso-2022-jp) isn't able to
transmit half-width kana (my Japanese version of Eudora converts
to full-width kana when sending). This significantly reduces any
cut/paste problems.

And out of 100 Japanese that you ask, about 100 will prefer decent
typography to half-width kana, as about 100 westerners will prefer
a decently set and printed page with case distinctions to a 60's
all-uppercase printout.


The situation is a bit (but not much) different for full-width Latin
letters. Their creation was an accident. For the predecessor of what
is now JIS X 0208, they were included because the designers of that
two-byte standard thought that it would be used (at least to some
extent) as a pure two-byte standard, and that of course Latin
letters were needed once in a while. What is now usually called
full-width variants was intended to be just a different encoding
of one and the same letter (think ebcdic).

As it turned out, the two-byte encoding was virtually always
combined with a 7-bit standard (ASCII or the Japanese 646 variant).
In addition, screencell-oriented software was adapted to Japanese
by preserving the invariant of one byte == one (half-width) screen
cell. This was then later adapted into so-called word processors,
and from there into current-day word processing software.

Again, neither decent typography nor orthography distinguish two
width variants of Latin letters. The general practice for
typesetting Latin letters is to use proportional fonts, and was
always like this where the tools allowed it. There is also no
distinction made in hand-writing.

There are some differences to half-width kana. Full-width Latin
can be sent in emails. Some input methods have initial settings
that use full-width for Latin (but all of them allow to set
preference to half-width Latin). Readability of full-width Latin
is better than for half-width kana, because it's not used as
a substitute for completely different-looking letters (kanji,
hiragana), and because the characters are larger, rather than
smaller, than their counterparts.


So both half-width kana and full-width Latin letters are products
(or accidents) of technologies of the 60's and 70's. They are not
at all established in typographic or orthographic practice, and
I guess they never will. Comparing their proposed exclusion from
nameprep with COBOL programmers from the 60's defending upper-case
only is completely backwards.


For nameprep, half-width kana are very much irrelevant, because
the user would have to go to extra lengths to input half-width kana.
We don't want to forbid anybody to fold them to full-width katakana,
but there is absolutely no need to include them in nameprep.

For full-width Latin letters, there is indeed a certain chance
that users input them e.g. in a location field in a browser.
In particular, this chance will be increasing when mixed
domain names (i.e. JJJJ.LLLL.JJJJ) are used. But this is the
same problem that we have for the dot, and can be dealt with
in the same way.


Regards,   Martin.





From owner-idn@ops.ietf.org  Tue Oct 23 05:18:28 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24270
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 05:18:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vxTe-000PXg-00
	for idn-data@psg.com; Tue, 23 Oct 2001 02:04:02 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vxTd-000PXY-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 02:04:01 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 8BF577F414; Tue, 23 Oct 2001 18:03:37 +0900 (JST)
Message-Id: <4.2.0.58.J.20011023164821.03594bc0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Tue, 23 Oct 2001 17:43:01 +0900
To: David Hopwood <david.hopwood@zetnet.co.uk>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] NFC vs NFKC
In-Reply-To: <3BD5197B.1C280C5D@zetnet.co.uk>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <4.2.0.58.J.20011018183339.031fa100@localhost>
 <3BD0C257.A61BE893@zetnet.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is very interesting material. Thanks a lot for all this work.

The conclusions coincide mostly with mine, although I haven't
done such an explicit analysis.

Some comments below:

At 08:17 01/10/23 +0100, David Hopwood wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>
>David Hopwood wrote:
> > ... I've been preparing a detailed rationale for using NFC in
> > preference to NFKC, that considers all the categories of compatibility
> > mappings. I'll post it tomorrow.
>
>Took me a bit longer than I thought to finish, but here it is:
>
>- -----
>This post categorises and describes all of the compatibility
>mappings in Unicode 3.1. The intention is to show that these
>mappings are of little value for name preparation, because in
>almost all cases, one or more of the following applies:
>
>DISALLOWED: the source characters are already disallowed by
>    nameprep-06, so removing the mapping has no effect.
>NOT-USEFUL: the source characters are not useful in domain names.
>PUNCT-SYMBOL: the source characters are punctuation or symbols,
>    similar to characters that are disallowed for ASCII.
>NOT-EQUIV: the source characters are not semantically equivalent
>    to the target characters - i.e. folding them would be more
>    confusing than not folding them (if, for the sake of argument,
>    they were allowed).
>LEGACY: the source characters are *only* intended to be used for
>    round-trip mappings from legacy charsets.
>DEPRECATED: the source characters are formally deprecated by
>    Unicode 3.1.
>OBSCURE: the source characters are very difficult to type, or
>    produce using an input method, so not folding them is unlikely
>    to cause any practical difficulty to users.
>INTERNAL: the source characters are normally only intended for
>    internal use within an application or rendering engine.
>INCONSISTENT: a category of mappings is arbitrary and inconsistent,
>    with only some of the potential mappings in that category being
>    defined as compatibility equivalences.
>
>There are a very small number of exceptions:
>
>EXCEPTION: the mapping could be quite useful, and there is no
>    reason to exclude it on any of the grounds above.
>
>I claim that there are few enough exceptions to show that NFKC
>is not the right mapping to use: *if* some of these [EXCEPTION]
>mappings are wanted, they should be handled as an additional step
>to NFC normalisation (similar to the mapped-out characters).

I fully agree.


>Here are the mapping categories. They're in no particular order,
>and some characters appear in more than one category.
>
><nobreak>
>   The source character is a non-breaking version of the target
>   character:
>     00A0 NO-BREAK SPACE                       [DISALLOWED]
>     0F0C TIBETAN MARK DELIMITER TSHEG BSTAR   [NOT-USEFUL; see below]
>     2007 FIGURE SPACE                         [DISALLOWED]
>     2011 NON-BREAKING HYPHEN                  [EXCEPTION]
>     202F NARROW NO-BREAK SPACE                [DISALLOWED]
>
>   Tibetan script consists of morphemes separated by tseks (also
>   transliterated as "tsheg"); see section 9.13 of the Unicode
>   standard. U+0F0C is a non-breaking tsek (the character name is
>   a mistake). In domain names, either an ordinary tsek (U+0F0B),
>   or a hyphen should be used instead.
>
>   It's possible that a document might use a non-breaking hyphen
>   to prevent a domain name or URI being split over lines, and it
>   could be useful to map it to a hyphen when cutting and pasting,
>   so this is an [EXCEPTION].

It seems inconsistent to treat a non-breaking hyphen as an
[EXCEPTION], but a non-breaking tsheg as [NOT-USEFUL].
The non-breaking tsheg will be as useful to Tibetan domain
names as the non-breaking hyphen to domain names that use it,
or actually more so because there is a tsheg between any
two syllables in Tibetan, but hyphens appear less often.


><fraction>
>   Various legacy character sets have characters for fractions, e.g.
>   1/2, etc. [LEGACY, OBSCURE, NOT-USEFUL].

This is a typical example of where there is no problem for
IDN, because the '/' produced is also disallowed, but where
problems will appear if NFKC is applied for something similar.


><wide> Full-width variants

>   FF0D       FULLWIDTH HYPHEN-MINUS                [EXCEPTION]
>   FF10..FF19 FULLWIDTH DIGIT ZERO..NINE            [EXCEPTION]
>   FF21..FF3A FULLWIDTH LATIN CAPITAL LETTER A..Z   [EXCEPTION]
>   FF41..FF5A FULLWIDTH LATIN SMALL LETTER A..Z     [EXCEPTION]
>
>   CJK input methods can sometimes produce full-width characters,
>   and it may be useful to map these to half-width (normal) LDH
>   ASCII characters.
>
>   However, nameprep is probably not the best place to do that.
>   Doing it there would mean that it is valid for full-width ASCII
>   to appear in an encoded name [*]. This will display as replacement
>   boxes when viewed on a system without CJK fonts. It would be far
>   preferable to make sure that encoded names always use normal
>   ASCII. That suggests doing this folding in name input widgets,

This could be handled together with the 'ideographic fullstop'
issue, for which special treatment is neccessary anyway.


>   and/or defining a way to tell input methods when a domain name (or
>   similar identifier) is being entered.
>
>   Note that CJK users already have to set input methods to produce
>   half-width ASCII characters, in order to type existing LDH ASCII
>   domain names. So although this folding may improve usability, it
>   isn't essential.

I disagree quite a bit. For current all-ASCII domain names, it's
not a big issue, but for mixed Kanji/Latin domain names, it's
much more of an issue. Users in particular in Japan are used to
switch to a different mode for ASCII-only work, but there are
a lot of input methods that produce full-width Latin.


><narrow>
>   FF61..FF64 Half-width punctuation          [PUNCT-SYMBOL]
>   FF65..FF9F Half-width Katakana             [EXCEPTION]
>   FFE8..FFEE Half-width symbols              [PUNCT-SYMBOL]
>
>   The same comments apply to half-width Katakana as to the <wide>
>   mappings above.

I have to disagree. Half-width Katakana is much less of a problem.
Some systems (e.g. Unix, Japanese Email) don't handle half-width
Katakana. And they look ugly and clearly 'not right' to the average
Japanese. To input them, you have to switch to a special mode.
(I wrote a longer piece about full-width Latin and half-width
Katakana a while ago for the nameprep design team; I'll
post it separately).



><compat>, <narrow> Hangul Compatibility Jamo
>   3131..318E Full-width Compatibility Jamo
>   FFA0..FFDC Half-width Compatibility Jamo
>
>   The normal set of Jamo encoded at 1100..1100 is conjoining, that
>   is, sequences of Jamo are displayed as, and are NFC-equivalent
>   to, the corresponding syllables. The Compatibility Jamo (both
>   full-width and half-width) are non-conjoining, i.e. they each
>   take up a character cell; that is the only reason why they were
>   encoded separately.
>
>   So, the effect of using NFKC is that a domain name could be
>   displayed with Jamo in separate character cells, but would
>   actually be equivalent to the corresponding name displayed as
>   syllables. I can't see any reason why that would be desirable.
>
>   Also, section 10.4 of [Unicode3.0] says, "These characters are
>   provided solely for compatibility with the KS C 5601 standard."
>   [LEGACY, NOT-EQUIV].

The half-width ones should be prohibited similar to the half-width
Katakana. There may be some point in allowing the full-width ones,
but the discussion on this in the nameprep team wasn't conclusive.
Anyway, as already discussed in the nameprep team, not folding
them into the basic Jamo (in the U+1100 block) would address
a problem that Soobok mentioned again very recently.


><compat> Hangzhou numerals
>   3038 HANGZHOU NUMERAL TEN
>   3039 HANGZHOU NUMERAL TWENTY
>   303A HANGZHOU NUMERAL THIRTY
>
>   These map to the ideographs U+5341 meaning ten (or complete or
>   perfect), U+5344 meaning twenty, and U+5345 meaning thirty.
>   I suspect that input methods will normally produce those
>   ideographs, not the numeral characters (i.e. these characters
>   are [OBSCURE]) - can anyone confirm that?

I can't confirm, but I would strongly suspect that to be true.


><compat> Ideographic telegraph symbols for months, hours, and days
>   32C0..32CB
>   3358..3370
>   33E0..33FE
>
>   These map to a decimal ASCII number, followed by the ideograph
>   U+6708 (for months) or U+70B9 (for hours) or U+65E5 (for days).
>   Again, I suspect that input methods will produce those sequences
>   rather than the symbols. [OBSCURE].

Same comment as above.


><vertical>
>   Presentation forms of symbols for use in vertical (top-to-bottom)
>   layout. These are all in the Small Form Variants block (FE50..FE6B).
>   These mappings are not useful because:
>
>   - the corresponding left-to-right symbols are not normally
>     used in domain names (most of them are brackets).
>   - domain names are not normally laid out vertically (it would
>     be better to use a left-to-right footnote in most cases).
>
>   [NOT-USEFUL, PUNCT-SYMBOL]

I slightly disagree with your second point. The current domain
names already appear in vertical print (each letter is turned 90
degrees clockwise) in Japanese newspapers and magazines.

But this doesn't change your classification, because for
punctuation, the correct glyph should be chosen automatically
based on the writing direction. That's what the present-day
system I know do.


><font>, <compat>, <initial>, <medial>, <final>, <isolated>
>Presentation forms and some ligatures:

>   Arabic:   0675..0678

I would be very careful with these.


>   Note that the word "ligature" is overloaded: some ligatures behave
>   like presentation forms (e.g. ff, fi, ffi, ij in Latin scripts),
>   while others (e.g. oe and ae) are part of the spelling of words,
>   such as "arch<ae>ology" (British English spelling). The argument
>   above does not apply to the second type of ligature, but those
>   don't have compatibility mappings.
>
>   An input method/keyboard driver should never generate a ligature
>   or presentation form, and lots of existing software would break
>   if it did. (In general, language-specific rules are necessary to
>   properly ligaturize text - e.g. in English the "ff" in "shelfful"
>   should not ligaturize because the two "f"s are in different
>   syllables.) Even if a user copies text containing presentation
>   ligatures from a word processor, they will be decomposed on the
>   clipboard, unless the word processor is completely broken in this
>   respect.

I wouldn't be completely sure about the last sentence. But anyway,
the dns has worked for ages without mapping ff, fi, ffi,..., and so
it's rather safe to assume that it will continue without these kinds
of mappings.


><compat> Combinations of spacing characters:
>   013F LATIN CAPITAL LETTER L WITH MIDDLE DOT
>   0140 LATIN SMALL LETTER L WITH MIDDLE DOT
>   0149 LATIN SMALL LETTER N PRECEDED BY APOSTROPHE
>   0E33 THAI CHARACTER SARA AM
>   0EB3 LAO VOWEL SIGN AM
>   1E9A LATIN SMALL LETTER A WITH RIGHT HALF RING
>
>   These are combinations of characters that were encoded as a single
>   character in other standards. The only reason why they aren't
>   canonical equivalences, is that the decomposition is to two spacing
>   characters, rather than a spacing character and a combining mark.

I'm not sure. There are some canonical decompositions into
two spacing characters. The algorithm in UTR 15 is carefully
designed to put them back again.


>   These mappings could be treated as [EXCEPTION]s, although the
>   combined characters are rare enough that it probably isn't worth
>   the hassle to do that. I don't know whether they are produced by
>   keyboard drivers.

This probably should be checked on a one-by-one base.


>   Note that the following are canonical equivalents, so they should
>   not be disallowed (in order to satisfy the Unicode requirement of
>   treating canonical equivalents identically):
>     U+2126 OHM SIGN -> Omega
>     U+212A KELVIN SIGN -> K
>     U+212B ANGSTROM SIGN -> A with ring above

I don't understand this. Prohibition happens after normalization,
so there is no need to discuss whether they should be prohibited
or not, they will just be normalized away.


><compat> Miscellaneous
>   U+017F LATIN SMALL LETTER LONG S
>
>   This is really a glyph variant of 's'. It is rarely used, so it
>   doesn't really matter if it is not mapped to 's'. [OBSCURE].

For some people, it might matter (Irish?).


>David Hopwood <david.hopwood@zetnet.co.uk>


Thanks again for your thorough work!


Regards,   Martin.



From owner-idn@ops.ietf.org  Tue Oct 23 06:50:04 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25281
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 06:50:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vypr-0001Wx-00
	for idn-data@psg.com; Tue, 23 Oct 2001 03:31:03 -0700
Received: from patan.sun.com ([192.18.98.43])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vypq-0001Wq-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 03:31:02 -0700
Received: from bebop.France.Sun.COM ([129.157.174.15])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA18071;
	Tue, 23 Oct 2001 04:30:35 -0600 (MDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f9NAUwq20938;
	Tue, 23 Oct 2001 12:30:58 +0200 (MET DST)
Date: Tue, 23 Oct 2001 12:25:25 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [idn] Which lanuages/scripts to reorder? 
To: Soobok Lee <lsb@postel.co.kr>
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>,
        Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>,
        idn@ops.ietf.org
In-Reply-To: "Your message with ID" <004401c15b59$598d6460$ec1bd9d2@temp>
Message-ID: <Roam.SIMC.2.0.6.1003832725.4114.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


> seamless upgrade idea for adding new script reordering tables and new
> nameprep rules (NF/casemappings) are described in the posting titled with
> "suggestion : two prefices ....". No newer prefix other than (zq-- and uq--)
> will be needed forever. I recommend you to comment on the suggestion first
> before you go further.

Soobok,

We seem to have a failure to communicate.
I've placed one new concern on the table which does not have anything to
do with how you could technically upgrade to new reordering tables.

My concern is about that the process of definition reordering tables
might never terminate (or might take a decade or so) since there might very
well be a request to add more and more languages/scripts to the tables before
we ever get to produce a single RFC.

I do not have anything to add to the techical issue of how upgrade
to new reordering tables as that was not the issue over which 
I expressed concern. Thus it makes no sense to me to comment on that issue.


Sincerely,
  Erik





From owner-idn@ops.ietf.org  Tue Oct 23 07:28:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26391
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 07:28:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15vzNi-0002QZ-00
	for idn-data@psg.com; Tue, 23 Oct 2001 04:06:02 -0700
Received: from pheidippides.md.chalmers.se ([129.16.237.91])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15vzNh-0002QS-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 04:06:01 -0700
Received: from chalmers95a69n (dhcp226-180.cs.chalmers.se [129.16.226.180])
	by pheidippides.md.chalmers.se (8.10.1/8.10.1) with SMTP id f9NB5mb08608;
	Tue, 23 Oct 2001 13:05:48 +0200 (MET DST)
Message-ID: <01b501c15bb1$8087b180$b4e21081@chalmers95a69n>
From: "Kent Karlsson" <kentk@md.chalmers.se>
To: <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
Cc: <DougEwell2@cs.com>, "'Soobok Lee'" <lsb@postel.co.kr>,
        <jshin@mailaps.org>
References: <4.2.0.58.J.20011023121348.0363c280@localhost>
Subject: Hangul Jamo consonant or vowel clusters (was: Re: [idn] call for comments for REORDERING)
Date: Tue, 23 Oct 2001 12:57:26 +0200
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.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
...
> At 19:05 01/10/22 +0200, Karlsson Kent - keka wrote:
> 
> >And still it is not sufficient, since historic Hangul
> >Jamo aren't covered by the precomposed Hangul syllable
> >characters. I have also indications that many useful
> >consonant (and vowel?) clusters aren't covered as separate
> >(Jamo) characters, but have to be constructed from multiple
> >'more basic' (non-cluster) Hangu Jamo characters.
> 
> Now that's new to me. Can you provide some evidence
> (e.g. some scans)?

I don't have any scans, but a quote from the public Unicode mailing list.
In http://www.unicode.org/mail-arch/unicode-ml/y2001-m10/0253.html:
:Unicode Hangul Jamo block has about 220 Hangul Jamos used in modern Korean 
:and middle Korean. Why are there so many? Because instead of encoding only 
:17 consonants and 11 vowels (one can go further down the 'reductionist' 
:road and say that only several base consonants and a few base vowels 
:along with 'diacritical' elements are all necessary to represent/encode 
:Hangul. See p. 143 of Sampson), Unicode encodes all forms of 'composite 
:Jamos' (consonant clusters, 'double' consonants to represent tense 
:consonants, complex diphtongs, etc). However, this is not sufficient 
:and Microsoft Word 2002/Windows XP/MS IE 6.0 comes with truetype fonts 
:that can be used by 'Uniscribe' to combine dynamically Hangul Jamos 
:beyond a simple I.C + M. V. (+ F.C.) model (I.C. = initial consonant, 
:M.V. = medial vowel, F.C= final consonant) as described in Unicode 3.0 
:.......... 
:
:  Jungshik Shin 

I assume that this functionality is not included just for fun...

            Kind regards
            /kent k


> I use to write my last name as a Hangul syllable as a joke,
> but as the 'rst' combination doesn't turn up in as a final
> cluster, I have to do this using graphics. So I'm familliar
> with the problem. But I assumed that all actual combinations
> that have been used historically are actually available
> in the Unicode Jamo block.
> 
> 
> Regards,  Martin.




From owner-idn@ops.ietf.org  Tue Oct 23 08:53:17 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29518
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 08:53:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w0l7-0004jP-00
	for idn-data@psg.com; Tue, 23 Oct 2001 05:34:17 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w0l6-0004jJ-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 05:34:16 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id VAA03413;
	Tue, 23 Oct 2001 21:33:46 +0900
Message-ID: <028701c15bbf$1b4396a0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        <idn@ops.ietf.org>
References: <Roam.SIMC.2.0.6.1003832725.4114.nordmark@bebop.france>
Subject: Re: [idn] Which lanuages/scripts to reorder? 
Date: Tue, 23 Oct 2001 21:34:43 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id IAA29518


----- Original Message ----- 
From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
To: "Soobok Lee" <lsb@postel.co.kr>
Cc: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>; "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>; <idn@ops.ietf.org>
Sent: Tuesday, October 23, 2001 7:25 PM
Subject: Re: [idn] Which lanuages/scripts to reorder? 


> 
> > seamless upgrade idea for adding new script reordering tables and new
> > nameprep rules (NF/casemappings) are described in the posting titled with
> > "suggestion : two prefices ....". No newer prefix other than (zq-- and uq--)
> > will be needed forever. I recommend you to comment on the suggestion first
> > before you go further.
> 
> Soobok,
> 
> We seem to have a failure to communicate.
> I've placed one new concern on the table which does not have anything to
> do with how you could technically upgrade to new reordering tables.
> 
> My concern is about that the process of definition reordering tables
> might never terminate (or might take a decade or so) since there might very
> well be a request to add more and more languages/scripts to the tables before
> we ever get to produce a single RFC.
> 

Erik,

new reordering tables can be added only when there comes new nameprep
revision for newly added scripts, because reordering tables is proposed as
one candidate of nameprep/ACE components. that is, reordering tables are
bound by the versioning of nameprep.
 
nameprep (as one profile of stringprep) upgrade paths also never terminate
because there will be more and more scripts pending for approval over time.

If you look into nameprep/stringprep document, each version of nameprep
should specify  the used unicode version and the list of unassigned code points in 
in that version. If new versions of unicode accumulate enough set of new scripts for justifying major nameprep revision, then IETF IDN WG should work again to give birth to new nameprep profile with new list (maybe reduced by the amount of new assigned code points) of unassgined code points and new version number of unicode.

Therefore, your concerns about long path of reordering revisioning is NOT new problem,but rather just one of never-terminaing nameprep/ACE revisioning problem.

if we finalize IDN  before TAGALOG is assigned and added, current nameprep's architecture for unassigned code points, does not allow us to register tagalog domains   until new nameprep version come out by IETF activities in the undefined time in the future.

My two prefix(uq-- and zq--) scheme proposal tries to solve this inherenet problem of user inconveniences in treatment of unassigned code points,  even before distributions of new version of nameprep which often take *too much time* to serve the TAGALOG users' need.
 
 

Soobok Lee

> I do not have anything to add to the techical issue of how upgrade
> to new reordering tables as that was not the issue over which 
> I expressed concern. Thus it makes no sense to me to comment on that issue.
> 
> 
> Sincerely,
>   Erik
> 
> 
> 




From owner-idn@ops.ietf.org  Tue Oct 23 09:31:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01260
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 09:31:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w1S4-00060h-00
	for idn-data@psg.com; Tue, 23 Oct 2001 06:18:40 -0700
Received: from mercury.sun.com ([192.9.25.1])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w1S3-00060T-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 06:18:39 -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 GAA18930;
	Tue, 23 Oct 2001 06:18:36 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f9NDIVq07294;
	Tue, 23 Oct 2001 15:18:31 +0200 (MET DST)
Date: Tue, 23 Oct 2001 15:12:57 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [idn] Which lanuages/scripts to reorder? 
To: Soobok Lee <lsb@postel.co.kr>
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>,
        Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>,
        idn@ops.ietf.org
In-Reply-To: "Your message with ID" <028701c15bbf$1b4396a0$ec1bd9d2@temp>
Message-ID: <Roam.SIMC.2.0.6.1003842777.280.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Therefore, your concerns about long path of reordering revisioning is NOT
> new problem,but rather just one of never-terminaing nameprep/ACE revisioning
> problem.

I think they are very different.

nameprep/stringprep would probably need to be revised if there are Unicode code
points added before the document becomes an RFC.

My point about reordering is that it might need to be revised
each time somebody requests adding support for one of the 
languages/scripts that are already supported in Unicode, even if Unicode
doesn't add anything. I don't know how many languages/scripts
that Unicode currently support but the number is presumably a few hundered.

  Erik




From owner-idn@ops.ietf.org  Tue Oct 23 09:31:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01272
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 09:31:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w1MO-0005re-00
	for idn-data@psg.com; Tue, 23 Oct 2001 06:12:48 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w1MN-0005rU-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 06:12:48 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id WAA15388
	for <idn@ops.ietf.org>; Tue, 23 Oct 2001 22:12:30 +0900
Message-ID: <029b01c15bc4$836a1650$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Subject: [idn] questions: unassigned code points in nameprep
Date: Tue, 23 Oct 2001 22:13:28 +0900
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0297_01C15C0F.F134D1C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0297_01C15C0F.F134D1C0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit

Hi, Paul and Patrick,

Unassigned code points have diverse  implications  on
stability of DNS and uniformity of global IDN experiences.

I found somewhat obscure and unclear terminologies in the section 6
of stringprep. That may come from my lack of knowledge for
previous discussions, but for all  late joiners including me,
please reply  with clear answers for  the following
**asterisked** interposed comments.

Thanks.



http://www.ietf.org/internet-drafts/draft-hoffman-stringprep-00.txt

6. Unassigned Code Points in Stringprep Profiles

This section describes two different types of strings in typical
protocols where internationalized strings are used: "stored strings" and
"queries". Of course, different Internet protocols use strings very
differently, so these terms cannot be used exactly in every protocol
that needs to use stringprep.

   ** "CANNOT BE USED EXACTLY in EVERY PROTOCOL" should  be more
   specific regarding to every other protocols  not mentioned in this paragraph
  in order to   eliminate confusions of implementors.

In general, "stored strings" are strings

  ** "IN GENERAL" ?   ANY Exceptional cases  worth to research ?

that are used in protocol identifiers and named entities, such as names
in digital certificates, DNS domain name parts, and names of SNMP objects.

   ** "DNS DOMAIN NAME PARTS"  point to what ?  maybe those in any zone files.
   all the host names in any webpages and
    all the email addresses in electronic address books is "queries" or "stored strings"?

"Queries" are strings that are used to match against strings that are
stored identifiers, such as user-entered names for digital certificate
authorities, DNS lookups, and SNMP requests.

    ** Email composing windows accept TO: addresee  before you send.
   Are  both sender/recipient addresses  "stored strings" or "queries" for email clients?
   DNS lookups do not occur in email composing/account-setup window. Recipient's
   IDN email address will be nameprep/ACE encoded in email clients without
   any DNS lookup.

   ** What occurs when TAGALOG email addresses are specified in the TO: addressee
   in the email clients composing window  based on current nameprep without TAGALOG
   supports ?

   ** SMTP servers receive sender/recipient addresses from email clients by SMTP protocol.  Then,Does SMTP server regard the
incoming  email addresses  as "stored ones" or "queries"?    it is true that most SMTP servers will simply pass through those ACE
hostnames  without any nameprep validity check.

   ** What if  sender's ACEed Tagalog email address which is unassigned and invalid  yet in the  current  version of  nameprep?
should the recipient be warned   for security reasons ?


All code points not assigned in the character repertoire named in the
stringprep profile are called "unassigned code points". Stored strings
using the profile MUST NOT contain any unassigned code points. Queries
for matching strings MAY contain unassigned code points. Note that this
is the only part of this document where the requirements for queries
differs from the requirements for stored strings.

    ** Does this mean that  old nameprep/ACE email applications can't  send
     emails to  recipients with future TAGALOG IDN email addresses
     without upgrading to new version of nameprep?   Or allowed with warnings?


Soobok Lee



------=_NextPart_000_0297_01C15C0F.F134D1C0
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 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><STRONG><FONT face=3D=B1=BC=B8=B2>Hi, Paul and =
Patrick,=20
</FONT></STRONG>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>Unassigned code points have =
diverse&nbsp;=20
implications&nbsp; on</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>stability of DNS and uniformity =
of global IDN=20
experiences.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>I found somewhat&nbsp;obscure and =
unclear=20
terminologies in the section 6</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>of stringprep. That may come from =
my lack of=20
knowledge for</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>previous discussions, but for =
all&nbsp; late joiners=20
including me,</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>p</FONT></STRONG><STRONG><FONT =
face=3D=B1=BC=B8=B2>lease=20
reply&nbsp; with clear answers for&nbsp;</FONT></STRONG><STRONG><FONT =
face=3D=B1=BC=B8=B2>=20
</FONT></STRONG><STRONG><FONT face=3D=B1=BC=B8=B2>the=20
following&nbsp;</FONT></STRONG><STRONG><FONT=20
face=3D=B1=BC=B8=B2>&nbsp;</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>**asterisked** =
</FONT></STRONG><STRONG><FONT=20
face=3D=B1=BC=B8=B2>interposed&nbsp;comments.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>Thanks.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-hoffman-stringprep-00.t=
xt">http://www.ietf.org/internet-drafts/draft-hoffman-stringprep-00.txt</=
A></FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV>6. Unassigned Code Points in Stringprep Profiles<BR><BR>This =
section=20
describes two different types of strings in typical<BR>protocols where=20
internationalized strings are used: "stored strings" and<BR>"queries". =
Of=20
course, different Internet protocols use strings very<BR>differently, so =
these=20
terms cannot be used exactly in every protocol<BR>that needs to use =
stringprep.=20
</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;&nbsp; ** "CANNOT BE USED =
EXACTLY in EVERY=20
PROTOCOL" should&nbsp; be more </FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;&nbsp; =
specific&nbsp;regarding to&nbsp;every=20
other protocols&nbsp;</FONT></STRONG><STRONG><FONT face=3D=B1=BC=B8=B2> =
not mentioned in=20
this paragraph</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;&nbsp;in order=20
to&nbsp;</FONT></STRONG><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp; =
eliminate=20
confusions&nbsp;of</FONT></STRONG><STRONG><FONT face=3D=B1=BC=B8=B2>=20
implementors.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV>In general, "stored strings" are strings</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;**<STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;"IN GENERAL" =
?&nbsp;&nbsp; ANY=20
Exceptional cases&nbsp; worth to&nbsp;research ?</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2></FONT></STRONG><BR>that =
are used in protocol=20
identifiers and named entities, such as names<BR>in digital =
certificates, DNS=20
domain name parts, and names of SNMP objects.</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;&nbsp;&nbsp;** "DNS DOMAIN =
NAME PARTS"&nbsp;=20
point to&nbsp;what ?&nbsp; maybe those in any zone =
files.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;&nbsp;&nbsp;all=20
the&nbsp;host&nbsp;</FONT></STRONG><STRONG><FONT =
face=3D=B1=BC=B8=B2>names&nbsp;in any=20
webpages and</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;&nbsp;&nbsp;&nbsp;all the =
email addresses in=20
electronic address books is "queries" or "stored =
strings"?</FONT></STRONG></DIV>
<DIV>&nbsp; <BR>"Queries" are strings that are used to match against =
strings=20
that are<BR>stored identifiers, such as user-entered names for digital=20
certificate<BR>authorities, DNS lookups, and SNMP requests.</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 size=3D2>&nbsp;&nbsp;&nbsp;<FONT =
size=3D3> ** Email=20
composing windows accept TO: addresee &nbsp;before you=20
send.</FONT></FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;&nbsp; Are&nbsp; both =
sender/recipient=20
addresses&nbsp; "stored strings" or "queries" for email=20
clients?</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;&nbsp; DNS lookups do not =
occur in email=20
composing/account-setup window. Recipient's</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;&nbsp; IDN email address =
will be nameprep/ACE=20
encoded in email clients without</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;&nbsp; any DNS =
lookup.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;&nbsp; ** What occurs when =
TAGALOG email=20
addresses are specified in the TO: addressee</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;&nbsp; in the email clients =
composing=20
window&nbsp; based on current nameprep without =
TAGALOG</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;&nbsp; supports =
?</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;&nbsp;&nbsp;** SMTP servers =
receive=20
sender/recipient addresses from email clients by SMTP=20
protocol.</FONT></STRONG><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp; =
Then,Does SMTP server=20
regard the incoming&nbsp;&nbsp;email=20
addresses&nbsp;</FONT></STRONG><STRONG><FONT face=3D=B1=BC=B8=B2> as =
"stored ones" or=20
"queries"?&nbsp;&nbsp;</FONT></STRONG><STRONG><FONT =
face=3D=B1=BC=B8=B2>&nbsp;&nbsp;it is=20
true that&nbsp;most SMTP servers&nbsp;will simply&nbsp;pass =
through&nbsp;those=20
ACE hostnames</FONT></STRONG><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp; =
without any nameprep=20
validity check.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;&nbsp; ** What if&nbsp; =
sender's ACEed Tagalog=20
email address&nbsp;which is unassigned and invalid&nbsp;&nbsp;yet in=20
the&nbsp;&nbsp;</FONT></STRONG><STRONG><FONT=20
face=3D=B1=BC=B8=B2>c</FONT></STRONG><STRONG><FONT=20
face=3D=B1=BC=B8=B2>urrent&nbsp;&nbsp;</FONT></STRONG><STRONG><FONT =
face=3D=B1=BC=B8=B2>version=20
of</FONT></STRONG><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp; =
nameprep?&nbsp;&nbsp;&nbsp;=20
should the recipient be warned&nbsp; &nbsp;for&nbsp;security reasons=20
?</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2></FONT></STRONG><BR><BR>All code =
points not assigned=20
in the character repertoire named in the<BR>stringprep profile are =
called=20
"unassigned code points". Stored strings<BR>using the profile MUST NOT =
contain=20
any unassigned code points. Queries<BR>for matching strings MAY contain=20
unassigned code points. Note that this<BR>is the only part of this =
document=20
where the requirements for queries<BR>differs from the requirements for =
stored=20
strings.<BR></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;&nbsp;&nbsp; ** Does this =
mean that&nbsp; old=20
nameprep/ACE email applications can't&nbsp; send</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;&nbsp;&nbsp;&nbsp; emails=20
to&nbsp;&nbsp;recipients with&nbsp;future TAGALOG IDN email =
addresses&nbsp;=20
&nbsp;</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>&nbsp;&nbsp;&nbsp;&nbsp; without =
upgrading to new=20
version of nameprep?&nbsp;&nbsp; Or allowed with =
warnings?</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2>Soobok Lee</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3D=B1=BC=B8=B2 =
size=3D2></FONT></STRONG>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0297_01C15C0F.F134D1C0--




From owner-idn@ops.ietf.org  Tue Oct 23 09:32:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01301
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 09:32:10 -0400 (EDT)
From: owner-idn@ops.ietf.org
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w1Tx-00065x-00
	for idn-data@psg.com; Tue, 23 Oct 2001 06:20:37 -0700
Message-Id: <E15w1Tx-00065x-00@psg.com>
To: idn-data@psg.com
Date: Tue, 23 Oct 2001 06:20:37 -0700

Tue, 23 Oct 2001 09:15:50 -0400
Date: Tue, 23 Oct 2001 09:15:50 -0400 (EDT)
From: Jungshik Shin <jshin@pantheon.yale.edu>
To: Kent Karlsson <kentk@md.chalmers.se>
cc: <idn@ops.ietf.org>
Subject: Re: Hangul Jamo consonant or vowel clusters (was: Re: [idn]
call
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Tue, 23 Oct 2001, Kent Karlsson wrote:

> ----- Original Message -----
> From: "Martin Duerst" <duerst@w3.org>
> ...
> > At 19:05 01/10/22 +0200, Karlsson Kent - keka wrote:
> >
> > >And still it is not sufficient, since historic Hangul
> > >Jamo aren't covered by the precomposed Hangul syllable
> > >characters. I have also indications that many useful
> > >consonant (and vowel?) clusters aren't covered as separate
> > >(Jamo) characters, but have to be constructed from multiple
> > >'more basic' (non-cluster) Hangu Jamo characters.
> >
> > Now that's new to me. Can you provide some evidence
> > (e.g. some scans)?
>
> I don't have any scans, but a quote from the public Unicode mailing
list.
> In http://www.unicode.org/mail-arch/unicode-ml/y2001-m10/0253.html:
> :Unicode Hangul Jamo block has about 220 Hangul Jamos used in modern
Korean
> :and middle Korean. Why are there so many? Because instead of encoding
only
> :17 consonants and 11 vowels (one can go further down the
'reductionist'
> :road and say that only several base consonants and a few base vowels
> :along with 'diacritical' elements are all necessary to
represent/encode
> :Hangul. See p. 143 of Sampson), Unicode encodes all forms of
'composite
> :Jamos' (consonant clusters, 'double' consonants to represent tense
> :consonants, complex diphtongs, etc). However, this is not sufficient
> :and Microsoft Word 2002/Windows XP/MS IE 6.0 comes with truetype
fonts
> :that can be used by 'Uniscribe' to combine dynamically Hangul Jamos
> :beyond a simple I.C + M. V. (+ F.C.) model (I.C. = initial consonant,
> :M.V. = medial vowel, F.C= final consonant) as described in Unicode
3.0
> :..........
> :
> :  Jungshik Shin
>
> I assume that this functionality is not included just for fun...

  Yes, they're necessary for the full representation of Middle
Korean, sometimes modern Korean (see below) and perhaps future Korean.


> > I use to write my last name as a Hangul syllable as a joke,
> > but as the 'rst' combination doesn't turn up in as a final
> > cluster, I have to do this using graphics. So I'm familliar
> > with the problem. But I assumed that all actual combinations
> > that have been used historically are actually available
> > in the Unicode Jamo block.

  Well, you seem to give too much trust in the way Korean standard body
came up with the list of Hangul Jamos to include in U+1100 block.
In early 1990's when ISO and Unicode asked them to provided the list,
what they did was to ask some Korean linguists to come up with the list
in a very short notice. If they had had a better understanding of the
standard-making-procedure, they would have taken longer time to come up
with a better/complete list. Needless to say, their list was incomplete.
How incomplete was the list? A few years ago, I even found a vowel
missing
which is frequently used by modern Korean speakers although it's not a
part of the official orthography. Later I found that the standard body
of DPRK(North Korea) proposed to ISO that this vowel along with several
others be included in U+1100 block.

  Microsoft developers in Korea, after consulting Korean linguists,
determined that  MS Windows XP/Office XP had to support a lot more Jamos
than listed in U+1100 block. Therefore, they have to support consonant
clusters and complex vowels  by combining existing Jamos.

   Jungshik Shin

P.S. If you can read Korean, you may refer
to http://www.korean.go.kr where you can find some articles posted the
issue.






From owner-idn@ops.ietf.org  Tue Oct 23 10:34:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05058
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 10:34:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w2Hz-0007tB-00
	for idn-data@psg.com; Tue, 23 Oct 2001 07:12:19 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w2Hx-0007t4-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 07:12:18 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id XAA01333;
	Tue, 23 Oct 2001 23:11:57 +0900
Message-ID: <02ba01c15bcc$d12edd50$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        <idn@ops.ietf.org>
References: <Roam.SIMC.2.0.6.1003842777.280.nordmark@bebop.france>
Subject: Re: [idn] Which lanuages/scripts to reorder? 
Date: Tue, 23 Oct 2001 23:12:56 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA05058


----- Original Message ----- 
From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
To: "Soobok Lee" <lsb@postel.co.kr>
Cc: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>; "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>; <idn@ops.ietf.org>
Sent: Tuesday, October 23, 2001 10:12 PM
Subject: Re: [idn] Which lanuages/scripts to reorder? 


> > Therefore, your concerns about long path of reordering revisioning is NOT
> > new problem,but rather just one of never-terminaing nameprep/ACE revisioning
> > problem.
> 
> I think they are very different.
> 
> nameprep/stringprep would probably need to be revised if there are Unicode code
> points added before the document becomes an RFC.
> 
> My point about reordering is that it might need to be revised
> each time somebody requests adding support for one of the 
> languages/scripts that are already supported in Unicode, even if Unicode
> doesn't add anything.
> I don't know how many languages/scripts
> that Unicode currently support but the number is presumably a few hundered.

Hundreds of languages, but, Not so many scripts. AFIAK,extended Latin scripts are shared by hundreds of languages as their writing systems. For latin labels which are already most favored by ACE, reordering does not help ( only 1% save on ACE length ). MY REORDERING I-D includes reordering on latin script but recommends not to include it because of its marginal gain on latin.

Each script has its ACE-Z label length constant which is listed in my
REORDERING I-D 2.0.
many scripts has relatively small set of basic alphabets, and their
ACE label length is less than 2*N.  han/hangeul ACE label length is
greater than 3*N without reordering. With reordering, it falls to 2.2*N.

MY REORDERING I-D 2.0 suggests one option of supporting only Han/HANGEUL 
which are most dis-favored scripts in ACE. If we decide to support all
major scripts in the current UNICODE, it will be done in the my I-D 3.0.

if we setup a certain threshold value on the label length constant for each script to determine the necessity of reordering supports, we could also restrict the set of new added scripts for which we should prepare reorderings in a regular fashion. I propose the threshold should be 1.7~ 2.2
with which threshold, only han/hangul/ethiopic/katakana/hiragana would be
supported in reordering.

And many script are archaic or used by too few native-speakers or scholars.
cost/benefits analysis based on the population using each script can be
performed and helps. That's already contained in My REORDERING I-D 2.0.

I enclose some proposed scripts in unicode. Most of them from minorities or 
un-industrialized countries or extinct/archaic ones. 
I expect those scripts would take fair amounts of time to be actively 
used in IDN in the future. That would determine when we will have major upgrades on  
reordering supports and namepre/ACE supports for them.

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

For the BMP 
  a.. Cham 
  b.. Tai (Dai) scripts 
  c.. Glagolitic 
  d.. Coptic 
  e.. Buginese 
  f.. Old Hungarian 
  g.. Phoenician 
  h.. Avestan 
  i.. Tifinagh (Berber) 
  j.. Javanese 
  k.. Lepcha (Rong) 
For Plane 1 (surrogates) 

  a.. Basic Egyptian Hieroglyphics 
  b.. Meroitic 
  c.. Old Persian Cuneiform 
  d.. Tengwar 
  e.. Cirth 
  f.. Brahmi 
  g.. Old Permic 
  h.. South Arabian 
  i.. Pollard 
  j.. Blissymbolics 
  k.. Soyombo 


Approved ones.

Philippine Scripts 

  a.. Tagalog 
  b.. Hanunóo 
  c.. Buhid 
  d.. Tagbanwa 

Pending..
  a.. Linear B (see also the overview for Aegean scripts) 
  b.. Ugaritic Cuneiform 
  c.. Shavian 
  d.. Osmanya 
  e.. Cypriot syllabary (see also the overview for Aegean scripts) 
For the BMP

  a.. Limbu 


> 
>   Erik
> 




From owner-idn@ops.ietf.org  Tue Oct 23 11:18:21 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07261
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 11:18:21 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w2xZ-0009DH-00
	for idn-data@psg.com; Tue, 23 Oct 2001 07:55:17 -0700
Received: from femail26.sdc1.sfba.home.com ([24.254.60.16])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w2xZ-0009DB-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 07:55:17 -0700
Received: from c1340594a ([65.11.104.12]) by femail26.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20011023145516.ADL2746.femail26.sdc1.sfba.home.com@c1340594a>;
          Tue, 23 Oct 2001 07:55:16 -0700
Message-ID: <009701c15bd2$d8701b50$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: <DougEwell2@cs.com>, <idn@ops.ietf.org>
Cc: <lsb@postel.co.kr>
References: <164.2b71e6d.29066372@cs.com>
Subject: Re: [idn] REORDERING: stability issues and UTC solutions
Date: Tue, 23 Oct 2001 07:56:07 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

I will mention also http://www.unicode.org/roadmaps/, which shows the future
planned allocations.

Mark
—————

Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
[http://www.macchiato.com]

----- Original Message -----
From: <DougEwell2@cs.com>
To: <idn@ops.ietf.org>
Cc: <lsb@postel.co.kr>
Sent: Monday, October 22, 2001 23:08
Subject: Re: [idn] REORDERING: stability issues and UTC solutions


> In a message dated 2001-10-22 8:41:07 Pacific Daylight Time,
lsb@postel.co.kr
> writes:
>
> >  Instead of NFC, some script may need CASE mappings, i guess.
> >  Current nameprep/ACE produce case-insensitively equivalent labels
> >  for IDN  X.com and x.com.
> >  Do you mean that all newly added SCRIPT won't have any case mapping ?
>
> Of course there will be new scripts added to Unicode/10646 that have case
> mappings (although those proposed for Unicode 3.2 do not).  But I thought
we
> were talking about reordering, not case mappings. I fear, once again, that
> the subject is being changed to divert us from the real issues surrounding
> the reordering proposal.
>
> >  Doug,
> >  If you have lists of new scripts pending for approval,
> >  please post them to this list for non-unicode experts.
>
> See <http://www.unicode.org/pending/pending.html>.  This location always
has
> the most up-to-date list of proposed scripts, along with an indication of
how
> far along the "pending" path they are.
>
> -Doug Ewell
>  Fullerton, California
>
>




From owner-idn@ops.ietf.org  Tue Oct 23 11:18:28 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07275
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 11:18:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w30w-0009Mv-00
	for idn-data@psg.com; Tue, 23 Oct 2001 07:58:46 -0700
Received: from femail38.sdc1.sfba.home.com ([24.254.60.32])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w30v-0009Mg-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 07:58:45 -0700
Received: from c1340594a ([65.11.104.12]) by femail38.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20011023145844.CQFU624.femail38.sdc1.sfba.home.com@c1340594a>;
          Tue, 23 Oct 2001 07:58:44 -0700
Message-ID: <00a001c15bd3$5448aa80$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>,
        "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        <idn@ops.ietf.org>
References: <Roam.SIMC.2.0.6.1003832725.4114.nordmark@bebop.france> <028701c15bbf$1b4396a0$ec1bd9d2@temp>
Subject: Re: [idn] Which lanuages/scripts to reorder? 
Date: Tue, 23 Oct 2001 07:59:34 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

>Therefore, your concerns about long path of reordering revisioning is NOT
new >problem,but rather just one of never-terminaing nameprep/ACE
revisioning >problem.

I disagree completely. Nameprep is designed so that it will work even if a
server and a client are on different versions, and without any version
number involved. That would absolutely fail if reordering were changed in
any future version.

Introducing explicit version numbers (and it could not be limited to 2)
would not help -- it would just make things worse.

Mark
—————

Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
[http://www.macchiato.com]

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
<idn@ops.ietf.org>
Sent: Tuesday, October 23, 2001 05:34
Subject: Re: [idn] Which lanuages/scripts to reorder?



----- Original Message -----
From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
To: "Soobok Lee" <lsb@postel.co.kr>
Cc: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>; "Eric Brunner-Williams in
Portland Maine" <brunner@nic-naa.net>; <idn@ops.ietf.org>
Sent: Tuesday, October 23, 2001 7:25 PM
Subject: Re: [idn] Which lanuages/scripts to reorder?


>
> > seamless upgrade idea for adding new script reordering tables and new
> > nameprep rules (NF/casemappings) are described in the posting titled
with
> > "suggestion : two prefices ....". No newer prefix other than (zq-- and
uq--)
> > will be needed forever. I recommend you to comment on the suggestion
first
> > before you go further.
>
> Soobok,
>
> We seem to have a failure to communicate.
> I've placed one new concern on the table which does not have anything to
> do with how you could technically upgrade to new reordering tables.
>
> My concern is about that the process of definition reordering tables
> might never terminate (or might take a decade or so) since there might
very
> well be a request to add more and more languages/scripts to the tables
before
> we ever get to produce a single RFC.
>

Erik,

new reordering tables can be added only when there comes new nameprep
revision for newly added scripts, because reordering tables is proposed as
one candidate of nameprep/ACE components. that is, reordering tables are
bound by the versioning of nameprep.

nameprep (as one profile of stringprep) upgrade paths also never terminate
because there will be more and more scripts pending for approval over time.

If you look into nameprep/stringprep document, each version of nameprep
should specify  the used unicode version and the list of unassigned code
points in
in that version. If new versions of unicode accumulate enough set of new
scripts for justifying major nameprep revision, then IETF IDN WG should work
again to give birth to new nameprep profile with new list (maybe reduced by
the amount of new assigned code points) of unassgined code points and new
version number of unicode.

Therefore, your concerns about long path of reordering revisioning is NOT
new problem,but rather just one of never-terminaing nameprep/ACE revisioning
problem.

if we finalize IDN  before TAGALOG is assigned and added, current nameprep's
architecture for unassigned code points, does not allow us to register
tagalog domains   until new nameprep version come out by IETF activities in
the undefined time in the future.

My two prefix(uq-- and zq--) scheme proposal tries to solve this inherenet
problem of user inconveniences in treatment of unassigned code points,  even
before distributions of new version of nameprep which often take *too much
time* to serve the TAGALOG users' need.



Soobok Lee

> I do not have anything to add to the techical issue of how upgrade
> to new reordering tables as that was not the issue over which
> I expressed concern. Thus it makes no sense to me to comment on that
issue.
>
>
> Sincerely,
>   Erik
>
>
>







From owner-idn@ops.ietf.org  Tue Oct 23 11:33:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07808
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 11:33:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w3ID-0009tA-00
	for idn-data@psg.com; Tue, 23 Oct 2001 08:16:37 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w3IB-0009s5-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 08:16:36 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id AAA21157;
	Wed, 24 Oct 2001 00:16:08 +0900
Message-ID: <032701c15bd5$c855ea80$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Mark Davis" <mark@macchiato.com>,
        "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        <idn@ops.ietf.org>
References: <Roam.SIMC.2.0.6.1003832725.4114.nordmark@bebop.france> <028701c15bbf$1b4396a0$ec1bd9d2@temp> <00a001c15bd3$5448aa80$0c680b41@c1340594a>
Subject: Re: [idn] Which lanuages/scripts to reorder? 
Date: Wed, 24 Oct 2001 00:17:08 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA07808


----- Original Message ----- 
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>; "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>; <idn@ops.ietf.org>
Sent: Tuesday, October 23, 2001 11:59 PM
Subject: Re: [idn] Which lanuages/scripts to reorder? 


> >Therefore, your concerns about long path of reordering revisioning is NOT
> new >problem,but rather just one of never-terminaing nameprep/ACE
> revisioning >problem.
> 
> I disagree completely. Nameprep is designed so that it will work even if a
> server and a client are on different versions, and without any version
> number involved. That would absolutely fail if reordering were changed in
> any future version.

Reordering won't be changed and  remains as sub-optimal frequency tables
forever without new prefix, as i repeated many time in this list.
 
What i mean is adding NEW reordering tables for *NEW SCRIPTS*
in accordance with new SCRIPT support in newer nameprep.
I agree with you that reordering table for old existing scripts should not be changed .

each Nameprep version defines unassigned code points which reordering should
not touch at all. That enforce  reordering  upgrade path strictly to  follow  that of nameprep.

Soobok Lee

> 
> Introducing explicit version numbers (and it could not be limited to 2)
> would not help -- it would just make things worse.
> 
> Mark
> —————
> 
> Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
> [http://www.macchiato.com]
> 
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
> <idn@ops.ietf.org>
> Sent: Tuesday, October 23, 2001 05:34
> Subject: Re: [idn] Which lanuages/scripts to reorder?
> 
> 
> 
> ----- Original Message -----
> From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> To: "Soobok Lee" <lsb@postel.co.kr>
> Cc: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>; "Eric Brunner-Williams in
> Portland Maine" <brunner@nic-naa.net>; <idn@ops.ietf.org>
> Sent: Tuesday, October 23, 2001 7:25 PM
> Subject: Re: [idn] Which lanuages/scripts to reorder?
> 
> 
> >
> > > seamless upgrade idea for adding new script reordering tables and new
> > > nameprep rules (NF/casemappings) are described in the posting titled
> with
> > > "suggestion : two prefices ....". No newer prefix other than (zq-- and
> uq--)
> > > will be needed forever. I recommend you to comment on the suggestion
> first
> > > before you go further.
> >
> > Soobok,
> >
> > We seem to have a failure to communicate.
> > I've placed one new concern on the table which does not have anything to
> > do with how you could technically upgrade to new reordering tables.
> >
> > My concern is about that the process of definition reordering tables
> > might never terminate (or might take a decade or so) since there might
> very
> > well be a request to add more and more languages/scripts to the tables
> before
> > we ever get to produce a single RFC.
> >
> 
> Erik,
> 
> new reordering tables can be added only when there comes new nameprep
> revision for newly added scripts, because reordering tables is proposed as
> one candidate of nameprep/ACE components. that is, reordering tables are
> bound by the versioning of nameprep.
> 
> nameprep (as one profile of stringprep) upgrade paths also never terminate
> because there will be more and more scripts pending for approval over time.
> 
> If you look into nameprep/stringprep document, each version of nameprep
> should specify  the used unicode version and the list of unassigned code
> points in
> in that version. If new versions of unicode accumulate enough set of new
> scripts for justifying major nameprep revision, then IETF IDN WG should work
> again to give birth to new nameprep profile with new list (maybe reduced by
> the amount of new assigned code points) of unassgined code points and new
> version number of unicode.
> 
> Therefore, your concerns about long path of reordering revisioning is NOT
> new problem,but rather just one of never-terminaing nameprep/ACE revisioning
> problem.
> 
> if we finalize IDN  before TAGALOG is assigned and added, current nameprep's
> architecture for unassigned code points, does not allow us to register
> tagalog domains   until new nameprep version come out by IETF activities in
> the undefined time in the future.
> 
> My two prefix(uq-- and zq--) scheme proposal tries to solve this inherenet
> problem of user inconveniences in treatment of unassigned code points,  even
> before distributions of new version of nameprep which often take *too much
> time* to serve the TAGALOG users' need.
> 
> 
> 
> Soobok Lee
> 
> > I do not have anything to add to the techical issue of how upgrade
> > to new reordering tables as that was not the issue over which
> > I expressed concern. Thus it makes no sense to me to comment on that
> issue.
> >
> >
> > Sincerely,
> >   Erik
> >
> >
> >
> 
> 
> 
> 




From owner-idn@ops.ietf.org  Tue Oct 23 11:36:15 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07976
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 11:36:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w3La-000A1I-00
	for idn-data@psg.com; Tue, 23 Oct 2001 08:20:06 -0700
Received: from femail29.sdc1.sfba.home.com ([24.254.60.19])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w3LZ-000A19-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 08:20:05 -0700
Received: from c1340594a ([65.11.104.12]) by femail29.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20011023152003.ICY21044.femail29.sdc1.sfba.home.com@c1340594a>;
          Tue, 23 Oct 2001 08:20:03 -0700
Message-ID: <00ba01c15bd6$4eb5f0c0$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
References: <200109181333.JAA19941@ietf.org>		 <024301c149a0$c65b1ee0$ec1bd9d2@temp>		 <4.2.0.58.J.20011010135529.03d9e6a0@localhost> <4.2.0.58.J.20011018183339.031fa100@localhost> <3BD0C257.A61BE893@zetnet.co.uk> <3BD5197B.1C280C5D@zetnet.co.uk>
Subject: Re: [idn] NFC vs NFKC
Date: Tue, 23 Oct 2001 08:20: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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

I disagree with your assessment. For example, I believe that it is a good
thing that the non-breaking feature is suppressed -- that is irrelevant to
IDNs.

However, it would make your paper much easier to examine if you removed all
the characters that end up getting disallowed -- they are not
counter-examples. Of the characters that are left that you feel are
problematic, there are three possibilities that the committee has to judge:

A. they don't matter if they are converted
B. they do matter, but they can be remapped, or prohibited*
C. they do matter, and enough to make us abandon NFKC

The downside of abandoning NFKC is that we lose the equivalence between
thousands of characters that do represent the same fundamental abstract
characters, such as width variants, Arabic ligatures, etc.

Note: a character can be deleted by the remapping phase. It can also be
effectively prohibited *before* NFKC by simply mapping it to an invalid
character, like space, that is not affected by normalization and ends up
being prohibited.

BTW I have very little hope that this committee will ever produce a result
if issues keep getting re-raised time and time and time again. For the
committee to ever reach some kind of resolution, people have to ask
themselves, *not* whether they think the current situation is absolutely
optimal (in their view) -- since it *never* will be -- but instead, whether
they can live with the result; whether there are really any results that
will cause significant problems in practice.

Mark
—————

Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
[http://www.macchiato.com]

----- Original Message -----
From: "David Hopwood" <david.hopwood@zetnet.co.uk>
To: <idn@ops.ietf.org>
Sent: Tuesday, October 23, 2001 00:17
Subject: [idn] NFC vs NFKC


> -----BEGIN PGP SIGNED MESSAGE-----
>
> David Hopwood wrote:
> > ... I've been preparing a detailed rationale for using NFC in
> > preference to NFKC, that considers all the categories of compatibility
> > mappings. I'll post it tomorrow.
>
> Took me a bit longer than I thought to finish, but here it is:
>
> - -----
> This post categorises and describes all of the compatibility
> mappings in Unicode 3.1. The intention is to show that these
> mappings are of little value for name preparation, because in
> almost all cases, one or more of the following applies:
>
> DISALLOWED: the source characters are already disallowed by
>    nameprep-06, so removing the mapping has no effect.
> NOT-USEFUL: the source characters are not useful in domain names.
> PUNCT-SYMBOL: the source characters are punctuation or symbols,
>    similar to characters that are disallowed for ASCII.
> NOT-EQUIV: the source characters are not semantically equivalent
>    to the target characters - i.e. folding them would be more
>    confusing than not folding them (if, for the sake of argument,
>    they were allowed).
> LEGACY: the source characters are *only* intended to be used for
>    round-trip mappings from legacy charsets.
> DEPRECATED: the source characters are formally deprecated by
>    Unicode 3.1.
> OBSCURE: the source characters are very difficult to type, or
>    produce using an input method, so not folding them is unlikely
>    to cause any practical difficulty to users.
> INTERNAL: the source characters are normally only intended for
>    internal use within an application or rendering engine.
> INCONSISTENT: a category of mappings is arbitrary and inconsistent,
>    with only some of the potential mappings in that category being
>    defined as compatibility equivalences.
>
> There are a very small number of exceptions:
>
> EXCEPTION: the mapping could be quite useful, and there is no
>    reason to exclude it on any of the grounds above.
>
> I claim that there are few enough exceptions to show that NFKC
> is not the right mapping to use: *if* some of these [EXCEPTION]
> mappings are wanted, they should be handled as an additional step
> to NFC normalisation (similar to the mapped-out characters).
>
>
> Here are the mapping categories. They're in no particular order,
> and some characters appear in more than one category.
>
> <nobreak>
>   The source character is a non-breaking version of the target
>   character:
>     00A0 NO-BREAK SPACE                       [DISALLOWED]
>     0F0C TIBETAN MARK DELIMITER TSHEG BSTAR   [NOT-USEFUL; see below]
>     2007 FIGURE SPACE                         [DISALLOWED]
>     2011 NON-BREAKING HYPHEN                  [EXCEPTION]
>     202F NARROW NO-BREAK SPACE                [DISALLOWED]
>
>   Tibetan script consists of morphemes separated by tseks (also
>   transliterated as "tsheg"); see section 9.13 of the Unicode
>   standard. U+0F0C is a non-breaking tsek (the character name is
>   a mistake). In domain names, either an ordinary tsek (U+0F0B),
>   or a hyphen should be used instead.
>
>   It's possible that a document might use a non-breaking hyphen
>   to prevent a domain name or URI being split over lines, and it
>   could be useful to map it to a hyphen when cutting and pasting,
>   so this is an [EXCEPTION].
>
> <super> and <sub>
>   The source character is a superscripted or subscripted version of
>   the target character. These can be further categorised as:
>
>     letters (ordinal indicators, modifier letters, and 'n')
>        [NOT-EQUIV]
>
>     digits [NOT-USEFUL, OBSCURE, NOT-EQUIV]
>
>     symbols (including superscript SM and TM)
>        [NOT-USEFUL, OBSCURE, NOT-EQUIV]
>
>     Kanbun (annotation of classical Chinese in Japanese texts)
>        [NOT-USEFUL, OBSCURE, NOT-EQUIV]
>
>   Whether the letters are useful is arguable, but if they are, they
>   should not be folded (since they are definitely not semantically
>   equivalent to the target character).
>
> <fraction>
>   Various legacy character sets have characters for fractions, e.g.
>   1/2, etc. [LEGACY, OBSCURE, NOT-USEFUL].
>
> <circle> and <square>,
> also <compat> 3036 CIRCLED POSTAL MARK
>
>   Circled and squared variants. [NOT-USEFUL, NOT-EQUIV]
>
>   (Note that the decomposition is to the uncircled/unsquared character
>   on its own, without a U+20DD COMBINING ENCLOSING CIRCLE or
>   U+20DE COMBINING ENCLOSING SQUARE. So the effect of this folding
>   is that names with and without the circle/square are equivalent,
>   despite being visually distinct.)
>
> <wide> Full-width variants
>   FF01..FF0C Full-width symbols/punctuation        [DISALLOWED,
PUNCT-SYMBOL]
>   FF0E       FULLWIDTH FULL STOP                   [DISALLOWED]
>   FF0F       FULLWIDTH SOLIDUS                     [DISALLOWED,
PUNCT-SYMBOL]
>   FF1A..FF20 Full-width symbols/punctuation        [DISALLOWED,
PUNCT-SYMBOL]
>   FF3B..FF40 Full-width symbols/punctuation        [DISALLOWED,
PUNCT-SYMBOL]
>   FFE0..FFE6 Full-width symbols                    [PUNCT-SYMBOL]
>
>   FF0D       FULLWIDTH HYPHEN-MINUS                [EXCEPTION]
>   FF10..FF19 FULLWIDTH DIGIT ZERO..NINE            [EXCEPTION]
>   FF21..FF3A FULLWIDTH LATIN CAPITAL LETTER A..Z   [EXCEPTION]
>   FF41..FF5A FULLWIDTH LATIN SMALL LETTER A..Z     [EXCEPTION]
>
>   CJK input methods can sometimes produce full-width characters,
>   and it may be useful to map these to half-width (normal) LDH
>   ASCII characters.
>
>   However, nameprep is probably not the best place to do that.
>   Doing it there would mean that it is valid for full-width ASCII
>   to appear in an encoded name [*]. This will display as replacement
>   boxes when viewed on a system without CJK fonts. It would be far
>   preferable to make sure that encoded names always use normal
>   ASCII. That suggests doing this folding in name input widgets,
>   and/or defining a way to tell input methods when a domain name (or
>   similar identifier) is being entered.
>
>   Note that CJK users already have to set input methods to produce
>   half-width ASCII characters, in order to type existing LDH ASCII
>   domain names. So although this folding may improve usability, it
>   isn't essential.
>
>   [*] I'm making the assumption that whatever IDN solution is chosen
>       will allow names to be encoded transparently in at least some
>       cases, i.e. it won't force ACE to be used everywhere.
>
> <narrow>
>   FF61..FF64 Half-width punctuation          [PUNCT-SYMBOL]
>   FF65..FF9F Half-width Katakana             [EXCEPTION]
>   FFE8..FFEE Half-width symbols              [PUNCT-SYMBOL]
>
>   The same comments apply to half-width Katakana as to the <wide>
>   mappings above.
>
> <compat>, <narrow> Hangul Compatibility Jamo
>   3131..318E Full-width Compatibility Jamo
>   FFA0..FFDC Half-width Compatibility Jamo
>
>   The normal set of Jamo encoded at 1100..1100 is conjoining, that
>   is, sequences of Jamo are displayed as, and are NFC-equivalent
>   to, the corresponding syllables. The Compatibility Jamo (both
>   full-width and half-width) are non-conjoining, i.e. they each
>   take up a character cell; that is the only reason why they were
>   encoded separately.
>
>   So, the effect of using NFKC is that a domain name could be
>   displayed with Jamo in separate character cells, but would
>   actually be equivalent to the corresponding name displayed as
>   syllables. I can't see any reason why that would be desirable.
>
>   Also, section 10.4 of [Unicode3.0] says, "These characters are
>   provided solely for compatibility with the KS C 5601 standard."
>   [LEGACY, NOT-EQUIV].
>
> <small>
>   These are all in the CJK Compatibility Forms block (FE30..FE44).
>   They were only encoded for compatibility with CNS 11643.
>
>   Most are [DISALLOWED] because the corresponding ASCII symbol
>   is disallowed; the following are not:
>     FE51 SMALL IDEOGRAPHIC COMMA              [LEGACY, PUNCT-SYMBOL]
>     FE58 SMALL EM DASH                        [LEGACY, PUNCT-SYMBOL]
>     FE5D SMALL LEFT TORTOISE SHELL BRACKET    [LEGACY, PUNCT-SYMBOL]
>     FE5E SMALL RIGHT TORTOISE SHELL BRACKET   [LEGACY, PUNCT-SYMBOL]
>     FE63 SMALL HYPHEN-MINUS                   [LEGACY]
>
>   Note that it would probably be more useful for a converter from
>   CNS 11643 to map to the ordinary variants of these characters,
>   anyway, rather than the small variants, which no-one uses.
>
> <compat> Overline variants
>   FE49..FE4C
>   [NOT-USEFUL, PUNCT-SYMBOL]
>
> <compat> Spaces
>   (mapping is U+0020 SPACE; also <wide> 3000 IDEOGRAPHIC SPACE).
>   [DISALLOWED]
>
> <compat> Spacing marks
>   (mapping starts with U+0020 SPACE)
>   These are mappings from a spacing diacritical mark, to <space> +
>   the corresponding combining mark. They are [DISALLOWED] because
>   the <space> is disallowed.
>
> <compat> Maps to disallowed ASCII (other than space)
>   2024 ONE DOT LEADER
>   2025 TWO DOT LEADER
>   2026 HORIZONTAL ELLIPSIS
>   203C DOUBLE EXCLAMATION MARK
>   2048 QUESTION EXCLAMATION MARK
>   2049 EXCLAMATION QUESTION MARK
>   2474..2487 PARENTHESIZED DIGIT/NUMBER ONE..TWENTY
>   2480..249B DIGIT/NUMBER ONE..TWENTY FULL STOP
>   249C..245B PARENTHESIZED LATIN SMALL LETTER A..Z
>   3200..321C PARENTHESIZED HANGUL *
>   3220..3243 PARENTHESIZED IDEOGRAPH *
>   FE4D DASHED LOW LINE
>   FE4E CENTRELINE LOW LINE
>   FE4F WAVY LOW LINE
>
>   [DISALLOWED].
>
> <compat> Hangzhou numerals
>   3038 HANGZHOU NUMERAL TEN
>   3039 HANGZHOU NUMERAL TWENTY
>   303A HANGZHOU NUMERAL THIRTY
>
>   These map to the ideographs U+5341 meaning ten (or complete or
>   perfect), U+5344 meaning twenty, and U+5345 meaning thirty.
>   I suspect that input methods will normally produce those
>   ideographs, not the numeral characters (i.e. these characters
>   are [OBSCURE]) - can anyone confirm that?
>
> <compat> Ideographic telegraph symbols for months, hours, and days
>   32C0..32CB
>   3358..3370
>   33E0..33FE
>
>   These map to a decimal ASCII number, followed by the ideograph
>   U+6708 (for months) or U+70B9 (for hours) or U+65E5 (for days).
>   Again, I suspect that input methods will produce those sequences
>   rather than the symbols. [OBSCURE].
>
> <compat> CJK Radicals
>   2E9F CJK RADICAL MOTHER
>   2EF3 CJK RADICAL C-SIMPLIFIED TURTLE
>   2F00..2FD5 KangXi radicals block
>
>   See section 10.1 of [Unicode3.0] for a discussion of radicals. Their
>   main uses are:
>     - to categorize or collate ideographs (e.g. in an index)
>     - to describe new ideographs, especially using the "ideographic
>       description sequence" convention.
>
>   The first of these isn't applicable to domain names, and nameprep
>   already disallows ideographic description characters. Therefore,
>   the simplest approach would be to disallow all radicals.
>
>   Note that even if mapping from radicals to ideographs were a good
>   idea, the selection of such mappings defined by NFKC is highly
>   inconsistent - e.g. the following radicals from the CJK Radicals
>   Supplement block correspond to unified ideographs:
>
>     2E83 -> 4E5A  2E85 -> 4EB8  2E8E -> 5140  2E8F -> 5C23  2E90 -> 5C22
>     2E92 -> 5DF3  2E96 -> 5FC4  2E98 -> 624C  2E9F -> 6BCD  2EC0 -> 535D
>     2EA1 -> 6C35  2EA3 -> 706C  2EA8 -> 72AD  2EAD -> 793B  2EAF -> 7CF9
>     2EB0 -> 7E9F  2EB1 -> 7F53  2EB2 -> 7F52  2EBD -> 81FC? 2EBE -> 8279
>     2EC1 -> 864E  2EC2 -> 8864  2EC3 -> 8980  2EC8 -> 8BA0  2ECC -> 8FB6
>     2ED0 -> 9485  2ED1 -> 9577  2ED2 -> 9578  2ED3 -> 957F  2ED4 -> 95E8
>     2ED6 -> 961D  2ED8 -> 9752  2ED9 -> 97E6  2EDB -> 98CE  2EDC -> 98DE
>     2EDD -> 98DF  2EDF -> 98E0  2EE0 -> 9963  2EE2 -> 9A6C  2EE3 -> 9AA8
>     2EE5 -> 9C7C  2EE6 -> 9E1F  2EEA -> 9EFE  2EEC -> 9F50  2EEE -> 9F7F
>     2EF0 -> 9F99  2EF1 -> 9F9C  2EF3 -> 9F9F
>
>   but only two of these are compatibility mappings (2E9F and 2EF3).
>   [NOT-USEFUL, NOT-EQUIV, INCONSISTENT]
>
>   The Yi radicals should probably also be disallowed because they
>   are not useful in domain names, even though they don't have any
>   compatibility mappings.
>
> <vertical>
>   Presentation forms of symbols for use in vertical (top-to-bottom)
>   layout. These are all in the Small Form Variants block (FE50..FE6B).
>   These mappings are not useful because:
>
>   - the corresponding left-to-right symbols are not normally
>     used in domain names (most of them are brackets).
>   - domain names are not normally laid out vertically (it would
>     be better to use a left-to-right footnote in most cases).
>
>   [NOT-USEFUL, PUNCT-SYMBOL]
>
> <font>, <compat>, <initial>, <medial>, <final>, <isolated>
> Presentation forms and some ligatures:
>
>   Latin:    0132..0133, FB00..FB06
>   Armenian: 0587, FB13..FB17
>   Arabic:   0675..0678
>   Lao:      0EDC..0EDD
>   Hebrew:   FB20..FB29, FB4F
>   Arabic:   <initial>, <medial>, <final>, <isolated>
>
>   Presentation ligatures/forms are rendering variants, so these
>   characters should not normally appear in external representations
>   of text (they are often used internally as part of a rendering
>   implementation, but that isn't relevant for nameprep).
>
>   Note that the word "ligature" is overloaded: some ligatures behave
>   like presentation forms (e.g. ff, fi, ffi, ij in Latin scripts),
>   while others (e.g. oe and ae) are part of the spelling of words,
>   such as "arch<ae>ology" (British English spelling). The argument
>   above does not apply to the second type of ligature, but those
>   don't have compatibility mappings.
>
>   An input method/keyboard driver should never generate a ligature
>   or presentation form, and lots of existing software would break
>   if it did. (In general, language-specific rules are necessary to
>   properly ligaturize text - e.g. in English the "ff" in "shelfful"
>   should not ligaturize because the two "f"s are in different
>   syllables.) Even if a user copies text containing presentation
>   ligatures from a word processor, they will be decomposed on the
>   clipboard, unless the word processor is completely broken in this
>   respect.
>   [INTERNAL, OBSCURE]
>
> <compat> Deprecated characters
>   0F77 TIBETAN VOWEL SIGN VOCALIC RR
>   0F79 TIBETAN VOWEL SIGN VOCALIC LL
>
>   The character descriptions say that "use of this character is
>   strongly discouraged". (ISTR some text in the standard explaining
>   why, but I can't find it now.)
>   [DEPRECATED]
>
> <compat> Combinations of spacing characters:
>   013F LATIN CAPITAL LETTER L WITH MIDDLE DOT
>   0140 LATIN SMALL LETTER L WITH MIDDLE DOT
>   0149 LATIN SMALL LETTER N PRECEDED BY APOSTROPHE
>   0E33 THAI CHARACTER SARA AM
>   0EB3 LAO VOWEL SIGN AM
>   1E9A LATIN SMALL LETTER A WITH RIGHT HALF RING
>
>   These are combinations of characters that were encoded as a single
>   character in other standards. The only reason why they aren't
>   canonical equivalences, is that the decomposition is to two spacing
>   characters, rather than a spacing character and a combining mark.
>
>   These mappings could be treated as [EXCEPTION]s, although the
>   combined characters are rare enough that it probably isn't worth
>   the hassle to do that. I don't know whether they are produced by
>   keyboard drivers.
>
> <compat> Croatian digraphs:
>   01C4..01CC
>   01F1..01F3
>
>   Chapter 7 of [Unicode3.0] says:
>
>     Croatian Digraphs Matching Serbian Cyrillic Lettters.
>
>     Serbo-Croatian is a single language with paired alphabets: a
>     Latin script (Croatian) and a Cyrillic script (Serbian). A set
>     of compatibility digraph codes is provided for one-to-one
>     transliteration.
>
>   IOW, these digraphs should occur only in text that has been
>   automatically transliterated from Serbian to Croatian. Normally the
>   digraph would be typed as two separate characters, so there is no
>   need for a nameprep mapping. [OBSCURE]
>
> <compat> Roman numerals
>   2160..217F
>   [NOT-USEFUL, OBSCURE]
>
> <font>, <compat> Latin and Greek letter-like characters
>   Most of the Letter-like Symbols block   [OBSCURE, NOT-USEFUL, NOT-EQUIV]
>   00B5 MICRO SIGN                         [OBSCURE, NOT-USEFUL, NOT-EQUIV]
>   20A8 RUPEE SIGN                    [INCONSISTENT, NOT-USEFUL, NOT-EQUIV]
>
>   Various symbols that look like stylized letters, sometimes with
>   mathematical meanings.
>
>   (It's not clear why the Rupee sign should have a compatibility
>   mapping to "Rs", when the same doesn't apply to other currency
>   symbols - e.g. the Pesata sign does not have a compatibility
>   mapping to "Pts". In any case, that doesn't really matter, since
>   currency symbols are not useful in domain names.)
>
>   Greek keyboard drivers will produce the "proper" lowercase mu
>   character (U+03BC), not U+00B5.
>
>   Note that the following are canonical equivalents, so they should
>   not be disallowed (in order to satisfy the Unicode requirement of
>   treating canonical equivalents identically):
>     U+2126 OHM SIGN -> Omega
>     U+212A KELVIN SIGN -> K
>     U+212B ANGSTROM SIGN -> A with ring above
>
>   All of the remaining Letter-like Symbols should be disallowed.
>
> <font> Mathematical Alphanumeric Symbols block
>   1D400..1D7FF
>
>   These characters are for specialised use in mathematical text.
>   (In fact the whole point of encoding them was that they are
>   not semantically equivalent to the corresponding plain letters
>   and digits - so folding them would be pointless.)
>
>   [NOT-USEFUL, OBSCURE, NOT-EQUIV].
>
> <compat> Greek symbols:
>   03D0..03D6
>   03F0..03F2
>   03F4..03F5
>   These are technical symbols, not normal Greek text.
>   [NOT-USEFUL, OBSCURE, NOT-EQUIV]
>
> <compat> Miscellaneous
>   U+017F LATIN SMALL LETTER LONG S
>
>   This is really a glyph variant of 's'. It is rarely used, so it
>   doesn't really matter if it is not mapped to 's'. [OBSCURE].
>
> <compat> Repeated characters
>   2033 DOUBLE PRIME
>   2034 TRIPLE PRIME
>   2036 REVERSED DOUBLE PRIME
>   2037 REVERSED TRIPLE PRIME
>   203C DOUBLE EXCLAMATION MARK
>   222C DOUBLE INTEGRAL
>   222D TRIPLE INTEGRAL
>   222F SURFACE INTEGRAL
>   2230 VOLUME INTEGRAL
>
>   [OBSCURE, PUNCT-SYMBOL].
>
> - --
> 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
>
> iQEVAwUBO9UXrDkCAxeYt5gVAQGspwf8DcHtURizKZj5I5mN/oE4krd7WfIXNwNj
> F7KIdavHPkNrL9JUt9j1vBr8iJ7eaYaTZ0zns0l3kL9m9QUWpmCiuqyWsdRKPRJQ
> w3mwDbartNV/en+OFp2qY8uHC1WAlcwZwcgS+RmSzfuSDdiYZ2gvXbySZjVNTAk1
> +LjaGuoBu8bL+0YDNClWpwQha5uPUkYvw2WvKUr5+F0ASLwoMmSqnHSIlvHVX0rd
> mOphfQfgo6k/4yG6YZKmp3F+8Onfs/IC2jZeorCWBMmre9uWO49Cf+WfO0C8CzOe
> o17SWXla+oNqo5dasb9ewSAlehdGxMi5Lx4HDZoqshJe4Fh2P8Ea2A==
> =iMh9
> -----END PGP SIGNATURE-----
>
>




From owner-idn@ops.ietf.org  Tue Oct 23 11:38:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08026
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 11:38:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w3PT-000AAK-00
	for idn-data@psg.com; Tue, 23 Oct 2001 08:24:07 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w3PT-000AA5-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 08:24:07 -0700
Received: from [192.168.1.5] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id RAA16678;
	Tue, 23 Oct 2001 17:23:52 +0200 (MET DST)
Date: Tue, 23 Oct 2001 17:18:01 +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] questions: unassigned code points in nameprep
Message-ID: <7628988.1003857481@localhost>
In-Reply-To: <029b01c15bc4$836a1650$ec1bd9d2@temp>
References:  <029b01c15bc4$836a1650$ec1bd9d2@temp>
X-Mailer: Mulberry/2.1.0 (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-10-23 22.13 +0900 Soobok Lee <lsb@postel.co.kr> wrote:

> I found somewhat obscure and unclear terminologies in the section 6 
> of stringprep. That may come from my lack of knowledge for 
> previous discussions, but for all  late joiners including me, 
> please reply  with clear answers for  the following   
> **asterisked** interposed comments. 

Ok.

First of all, what we try to explain is the robustness principle which is
quoted in many RFCs:

                "Be liberal in what you accept, and
                 conservative in what you send"

With this, we mean that if you generate a string, you should not use what
you belive is an unassigned codepoint. But, when receiving/reading a string
which someone else has generated, you should be prepared that unassigned
codepoints are used.

For example, if you have an older version of stringprep than I have, then I
might send codepoints to you which you belive is unassigned.

Now, given the principe Unicode Consortium has, to not change normalization
tables for assigned codepoints, the only thing that can happen between two
versions of the Unicode Tables are:

 - A previously unassigned codepoint is assigned.
 - A previously unassigned codepoint is assigned, and a normalization
   rule which normalizes it to another newly assigned codepoint.
 - A previously unassigned codepoint is assigned, and a normalization
   rule which normalizes it to another previously assigned codepoint.

This means that if you only create strings with codepoints you know how to
handle, and for others you codepoint by codepoint (on the normalized
string) you will still get a predictable result.

Because of this, no versioning is needed.

That said, I will try to explain what you ask.
 
> http://www.ietf.org/internet-drafts/draft-hoffman-stringprep-00.txt 
>   
> 6. Unassigned Code Points in Stringprep Profiles
> 
> This section describes two different types of strings in typical
> protocols where internationalized strings are used: "stored strings" and
> "queries". Of course, different Internet protocols use strings very
> differently, so these terms cannot be used exactly in every protocol
> that needs to use stringprep. 
>   
>    ** "CANNOT BE USED EXACTLY in EVERY PROTOCOL" should  be more 
>    specific regarding to every other protocols  not mentioned in this
> paragraph    in order to   eliminate confusions of implementors. 

Do you have a suggestion, given my explanation above?

The key is that an application can get a string in basically two different
ways:

 - Via some kind of interface where it is known that the string is
   not namepreped at all, for example a user interface or somewhere
   where non-namepreped text is used. We called this "stored".
 - Via some application protocol where the string is already
   namepreped, for example a DNS server which recieve a query. We
   call this "queries".

One can say "client" and "server", but that is not true either. The key
thing is whether the application is responsible for doing nameprep or not.

Suggest other words!

> In general, "stored strings" are strings 
>   
>   ** "IN GENERAL" ?   ANY Exceptional cases  worth to research ? 

See above. There are no exceptional cases, only possible to use other words
for the case when the application is responsible for doing nameprep.

> that are used in protocol identifiers and named entities, such as names
> in digital certificates, DNS domain name parts, and names of SNMP
> objects.    
>    ** "DNS DOMAIN NAME PARTS"  point to what ?  maybe those in any zone
> files.     all the host names in any webpages and 
>     all the email addresses in electronic address books is "queries" or
> "stored strings"?    

We explicitly don't talk about hostnames. We talk about the individual
labels. It is very important that we talk about labels and not hostnames.

Regarding the rest of this, see above about need for normalization.

> "Queries" are strings that are used to match against strings that are
> stored identifiers, such as user-entered names for digital certificate
> authorities, DNS lookups, and SNMP requests. 
>   
>     ** Email composing windows accept TO: addresee  before you send. 
>    Are  both sender/recipient addresses  "stored strings" or "queries"
> for email clients?     DNS lookups do not occur in email
> composing/account-setup window. Recipient's     IDN email address will be
> nameprep/ACE encoded in email clients without     any DNS lookup. 

If they are to be nameprepped, then they are "stored strings".

                "Be liberal in what you accept, and
                 conservative in what you send"
  
>    ** What occurs when TAGALOG email addresses are specified in the TO:
> addressee     in the email clients composing window  based on current
> nameprep without TAGALOG     supports ? 

If the address comes from for example a user interface where the
application belive it has to do nameprep on, an address with an unassigned
codepoint should be rejected. If the address comes from an address book
where the email application know that the address is namepreped already, it
can accept the address even though it contains unassigned codepoints.

It all boils down to the question on whether nameprep is needed or not.
 
>    ** SMTP servers receive sender/recipient addresses from email clients
> by SMTP protocol.  Then,Does SMTP server regard the incoming  email
> addresses  as "stored ones" or "queries"?    it is true that most SMTP
> servers will simply pass through those ACE hostnames  without any
> nameprep validity check.    

As queries. No nameprep is needed as the addresses should bee nameprepped
already.

>    ** What if  sender's ACEed Tagalog email address which is unassigned
> and invalid  yet in the  current  version of  nameprep?    should the
> recipient be warned   for security reasons ? 

See above. It depends on whether the email application belive it has to do
nameprep or not. If it does, unassigned codepoints can not be accepted.
Warning the user is one way of handling the case of the user wanting to use
some newly assigned codepoints before the email application is upgraded to
include the new codepoints in it's nameprep algorithm(s).

> All code points not assigned in the character repertoire named in the
> stringprep profile are called "unassigned code points". Stored strings
> using the profile MUST NOT contain any unassigned code points. Queries
> for matching strings MAY contain unassigned code points. Note that this
> is the only part of this document where the requirements for queries
> differs from the requirements for stored strings.
> 
>     ** Does this mean that  old nameprep/ACE email applications can't
> send       emails to  recipients with future TAGALOG IDN email addresses
>       without upgrading to new version of nameprep?   Or allowed with
> warnings?    

My take is that it is up to the application. The MUST NOT probably should
be SHOULD NOT instead, to give the ability for an email client (which is a
specific case) to allow such use. We were thinking of DNS Zonefiles which
is a more dangerous case, where unassigned codepoints is not to be.

   paf




From owner-idn@ops.ietf.org  Tue Oct 23 11:47:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08446
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 11:47:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w3ap-000AdT-00
	for idn-data@psg.com; Tue, 23 Oct 2001 08:35:51 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w3am-000AdE-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 08:35:48 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 146F2FFC01; Tue, 23 Oct 2001 23:36:03 +0800 (SGT)
Message-ID: <001101c15bd8$5f9246d0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>, "Mark Davis" <mark@macchiato.com>,
        "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        <idn@ops.ietf.org>
References: <Roam.SIMC.2.0.6.1003832725.4114.nordmark@bebop.france> <028701c15bbf$1b4396a0$ec1bd9d2@temp> <00a001c15bd3$5448aa80$0c680b41@c1340594a> <032701c15bd5$c855ea80$ec1bd9d2@temp>
Subject: Re: [idn] Which lanuages/scripts to reorder? 
Date: Tue, 23 Oct 2001 23:35:41 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

The problem is that there will be people who will request reordering (or
they complain unfair treatment). It is very hard to explain to X why
there is reordering for Y but not X.

Why create a potential timebomb for ourselves?

-James Seng

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Mark Davis" <mark@macchiato.com>; "Erik Nordmark"
<Erik.Nordmark@eng.sun.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
<idn@ops.ietf.org>
Sent: Tuesday, October 23, 2001 11:17 PM
Subject: Re: [idn] Which lanuages/scripts to reorder?



----- Original Message -----
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>; "Erik Nordmark"
<Erik.Nordmark@eng.sun.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
<idn@ops.ietf.org>
Sent: Tuesday, October 23, 2001 11:59 PM
Subject: Re: [idn] Which lanuages/scripts to reorder?


> >Therefore, your concerns about long path of reordering revisioning is
NOT
> new >problem,but rather just one of never-terminaing nameprep/ACE
> revisioning >problem.
>
> I disagree completely. Nameprep is designed so that it will work even
if a
> server and a client are on different versions, and without any version
> number involved. That would absolutely fail if reordering were changed
in
> any future version.

Reordering won't be changed and  remains as sub-optimal frequency tables
forever without new prefix, as i repeated many time in this list.

What i mean is adding NEW reordering tables for *NEW SCRIPTS*
in accordance with new SCRIPT support in newer nameprep.
I agree with you that reordering table for old existing scripts should
not be changed .

each Nameprep version defines unassigned code points which reordering
should
not touch at all. That enforce  reordering  upgrade path strictly to
follow  that of nameprep.

Soobok Lee

>
> Introducing explicit version numbers (and it could not be limited to
2)
> would not help -- it would just make things worse.
>
> Mark
> —————
>
> Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
> [http://www.macchiato.com]
>
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
> <idn@ops.ietf.org>
> Sent: Tuesday, October 23, 2001 05:34
> Subject: Re: [idn] Which lanuages/scripts to reorder?
>
>
>
> ----- Original Message -----
> From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> To: "Soobok Lee" <lsb@postel.co.kr>
> Cc: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>; "Eric
Brunner-Williams in
> Portland Maine" <brunner@nic-naa.net>; <idn@ops.ietf.org>
> Sent: Tuesday, October 23, 2001 7:25 PM
> Subject: Re: [idn] Which lanuages/scripts to reorder?
>
>
> >
> > > seamless upgrade idea for adding new script reordering tables and
new
> > > nameprep rules (NF/casemappings) are described in the posting
titled
> with
> > > "suggestion : two prefices ....". No newer prefix other than (zq--
and
> uq--)
> > > will be needed forever. I recommend you to comment on the
suggestion
> first
> > > before you go further.
> >
> > Soobok,
> >
> > We seem to have a failure to communicate.
> > I've placed one new concern on the table which does not have
anything to
> > do with how you could technically upgrade to new reordering tables.
> >
> > My concern is about that the process of definition reordering tables
> > might never terminate (or might take a decade or so) since there
might
> very
> > well be a request to add more and more languages/scripts to the
tables
> before
> > we ever get to produce a single RFC.
> >
>
> Erik,
>
> new reordering tables can be added only when there comes new nameprep
> revision for newly added scripts, because reordering tables is
proposed as
> one candidate of nameprep/ACE components. that is, reordering tables
are
> bound by the versioning of nameprep.
>
> nameprep (as one profile of stringprep) upgrade paths also never
terminate
> because there will be more and more scripts pending for approval over
time.
>
> If you look into nameprep/stringprep document, each version of
nameprep
> should specify  the used unicode version and the list of unassigned
code
> points in
> in that version. If new versions of unicode accumulate enough set of
new
> scripts for justifying major nameprep revision, then IETF IDN WG
should work
> again to give birth to new nameprep profile with new list (maybe
reduced by
> the amount of new assigned code points) of unassgined code points and
new
> version number of unicode.
>
> Therefore, your concerns about long path of reordering revisioning is
NOT
> new problem,but rather just one of never-terminaing nameprep/ACE
revisioning
> problem.
>
> if we finalize IDN  before TAGALOG is assigned and added, current
nameprep's
> architecture for unassigned code points, does not allow us to register
> tagalog domains   until new nameprep version come out by IETF
activities in
> the undefined time in the future.
>
> My two prefix(uq-- and zq--) scheme proposal tries to solve this
inherenet
> problem of user inconveniences in treatment of unassigned code points,
even
> before distributions of new version of nameprep which often take *too
much
> time* to serve the TAGALOG users' need.
>
>
>
> Soobok Lee
>
> > I do not have anything to add to the techical issue of how upgrade
> > to new reordering tables as that was not the issue over which
> > I expressed concern. Thus it makes no sense to me to comment on that
> issue.
> >
> >
> > Sincerely,
> >   Erik
> >
> >
> >
>
>
>
>






From owner-idn@ops.ietf.org  Tue Oct 23 11:59:04 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08895
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 11:59:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w3ZV-000AYz-00
	for idn-data@psg.com; Tue, 23 Oct 2001 08:34:29 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w3ZU-000AYr-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 08:34:28 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id AAA26684;
	Wed, 24 Oct 2001 00:34:07 +0900
Message-ID: <032f01c15bd8$4bf75b10$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Mark Davis" <mark@macchiato.com>,
        "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        <idn@ops.ietf.org>
References: <Roam.SIMC.2.0.6.1003832725.4114.nordmark@bebop.france> <028701c15bbf$1b4396a0$ec1bd9d2@temp> <00a001c15bd3$5448aa80$0c680b41@c1340594a>
Subject: Re: [idn] Which lanuages/scripts to reorder? 
Date: Wed, 24 Oct 2001 00:35:08 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA08895


----- Original Message ----- 
From: "Mark Davis" <mark@macchiato.com>
 > Introducing explicit version numbers (and it could not be limited to 2)
> would not help -- it would just make things worse.
> 

Mark, 
You may missed my point.
two prefix uq-- and zq-- does *not*  limit  the versioning into 2 times, but infinite times.

zq-- is for valid ACE labels  for the all version of nameprep and
uq-- is for invalid ACE labels including at least one unassigned code points for all versions of 
nameprep.

This differentiating ace prefixing scheme works  in all version of nameprep from 1 to infinity.

newly supported script in nameprep/ACE version 5 will be
encoded using  uq--????  with old nameprep/ACE version 4  and below.
But with namepre/ACE version 5 or above, it will be encoded zq--???? .

Likewise,
labels contain newly supported script in nameprep/ACE version 6 will be
encoded using  uq--????  with old nameprep/ACE version 5 and below.
But with namepre/ACE version 6 or above, it will be encoded zq--???? .

And so on.

There is no need for version numbered prefix  for each of version 2,3,4,5,6, .....

Current nameprep does not encode unassigned code points into ACE for
"saved strings", but my two prefix scheme allow it with "uq--" prefix  which
provide with  rooms for incorporating  some useful fallback mechanims.
Even with dealing with ACE foor lookup "query", it provide some clues
about the version of nameprep which encode the ACE lables by the
distintion of "uq--" and "zq--".
I am proposing new nameprep behavior for unassigned code points for 
"saved string" and "query" through out  nameprep versioning path. 
Not about  versioning nameprep itself!

Soobok Lee


> Mark
> —————
> 
> Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
> [http://www.macchiato.com]
> 
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
> <idn@ops.ietf.org>
> Sent: Tuesday, October 23, 2001 05:34
> Subject: Re: [idn] Which lanuages/scripts to reorder?
> 
> 
> 
> ----- Original Message -----
> From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> To: "Soobok Lee" <lsb@postel.co.kr>
> Cc: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>; "Eric Brunner-Williams in
> Portland Maine" <brunner@nic-naa.net>; <idn@ops.ietf.org>
> Sent: Tuesday, October 23, 2001 7:25 PM
> Subject: Re: [idn] Which lanuages/scripts to reorder?
> 
> 
> >
> > > seamless upgrade idea for adding new script reordering tables and new
> > > nameprep rules (NF/casemappings) are described in the posting titled
> with
> > > "suggestion : two prefices ....". No newer prefix other than (zq-- and
> uq--)
> > > will be needed forever. I recommend you to comment on the suggestion
> first
> > > before you go further.
> >
> > Soobok,
> >
> > We seem to have a failure to communicate.
> > I've placed one new concern on the table which does not have anything to
> > do with how you could technically upgrade to new reordering tables.
> >
> > My concern is about that the process of definition reordering tables
> > might never terminate (or might take a decade or so) since there might
> very
> > well be a request to add more and more languages/scripts to the tables
> before
> > we ever get to produce a single RFC.
> >
> 
> Erik,
> 
> new reordering tables can be added only when there comes new nameprep
> revision for newly added scripts, because reordering tables is proposed as
> one candidate of nameprep/ACE components. that is, reordering tables are
> bound by the versioning of nameprep.
> 
> nameprep (as one profile of stringprep) upgrade paths also never terminate
> because there will be more and more scripts pending for approval over time.
> 
> If you look into nameprep/stringprep document, each version of nameprep
> should specify  the used unicode version and the list of unassigned code
> points in
> in that version. If new versions of unicode accumulate enough set of new
> scripts for justifying major nameprep revision, then IETF IDN WG should work
> again to give birth to new nameprep profile with new list (maybe reduced by
> the amount of new assigned code points) of unassgined code points and new
> version number of unicode.
> 
> Therefore, your concerns about long path of reordering revisioning is NOT
> new problem,but rather just one of never-terminaing nameprep/ACE revisioning
> problem.
> 
> if we finalize IDN  before TAGALOG is assigned and added, current nameprep's
> architecture for unassigned code points, does not allow us to register
> tagalog domains   until new nameprep version come out by IETF activities in
> the undefined time in the future.
> 
> My two prefix(uq-- and zq--) scheme proposal tries to solve this inherenet
> problem of user inconveniences in treatment of unassigned code points,  even
> before distributions of new version of nameprep which often take *too much
> time* to serve the TAGALOG users' need.
> 
> 
> 
> Soobok Lee
> 
> > I do not have anything to add to the techical issue of how upgrade
> > to new reordering tables as that was not the issue over which
> > I expressed concern. Thus it makes no sense to me to comment on that
> issue.
> >
> >
> > Sincerely,
> >   Erik
> >
> >
> >
> 
> 
> 
> 




From owner-idn@ops.ietf.org  Tue Oct 23 12:07:35 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09237
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 12:07:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w3u4-000BOE-00
	for idn-data@psg.com; Tue, 23 Oct 2001 08:55:44 -0700
Received: from imo-d06.mx.aol.com ([205.188.157.38])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w3u3-000BO8-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 08:55:43 -0700
Received: from DougEwell2@cs.com
	by imo-d06.mx.aol.com (mail_out_v31_r1.8.) id i.15b.2e6239d (4380);
	Tue, 23 Oct 2001 11:55:34 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <15b.2e6239d.2906ecf6@cs.com>
Date: Tue, 23 Oct 2001 11:55:34 EDT
Subject: Re: [idn] Which lanuages/scripts to reorder? 
To: idn@ops.ietf.org
CC: lsb@postel.co.kr, mark@macchiato.com, Erik.Nordmark@eng.sun.com,
        brunner@nic-naa.net
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a message dated 2001-10-23 8:36:48 Pacific Daylight Time, lsb@postel.co.kr 
writes:

>  Reordering won't be changed and  remains as sub-optimal frequency tables
>  forever without new prefix, as i repeated many time in this list.
>
>  What i mean is adding NEW reordering tables for *NEW SCRIPTS*
>  in accordance with new SCRIPT support in newer nameprep.
>  I agree with you that reordering table for old existing scripts should not 
>  be changed .

Reordering is, first and last, based on the tables.  If you create new 
tables, you have by definition created a new version of reordering.  I don't 
think you can say "reordering won't be changed" and then suggest one sentence 
later that new tables could be added in the future.

However, I'm sure everyone will at least be glad to see that existing tables 
would not be touched.

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Tue Oct 23 12:08:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09296
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 12:08:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w3p6-000BG1-00
	for idn-data@psg.com; Tue, 23 Oct 2001 08:50:36 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w3p5-000BFu-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 08:50:35 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id AAA31657;
	Wed, 24 Oct 2001 00:50:11 +0900
Message-ID: <034501c15bda$8a5b1e30$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>,
        "Mark Davis" <mark@macchiato.com>,
        "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        <idn@ops.ietf.org>
References: <Roam.SIMC.2.0.6.1003832725.4114.nordmark@bebop.france> <028701c15bbf$1b4396a0$ec1bd9d2@temp> <00a001c15bd3$5448aa80$0c680b41@c1340594a> <032701c15bd5$c855ea80$ec1bd9d2@temp> <001101c15bd8$5f9246d0$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] Which lanuages/scripts to reorder? 
Date: Wed, 24 Oct 2001 00:51:12 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA09296


----- Original Message ----- 
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>; "Mark Davis" <mark@macchiato.com>; "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>; <idn@ops.ietf.org>
Sent: Wednesday, October 24, 2001 12:35 AM
Subject: Re: [idn] Which lanuages/scripts to reorder? 


> The problem is that there will be people who will request reordering (or
> they complain unfair treatment). It is very hard to explain to X why
> there is reordering for Y but not X.
> 
I will try to include as many script as possible in the final REORDERINg I-D.

But, Even without reordering,
some tagalog people will come and say  why ACE-Z  favors latin  with special
 literal mode supports.
Do you think this timebomb invalidates ACE-Z literal mode ?  No.

cost/benefits-based trade-off  can be the answer for this disputes on
special treatment in ACE-Z as well as REORDERING.

REORDERING's memory requirement is minimal  while it give 30% boostup
for hangul names. I don't recommend  reordering supports for latin and runic script.
You can find the rationale in my REORDERING I-D 2.0.


Soobok Lee


> Why create a potential timebomb for ourselves?
> 
> -James Seng
> 
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: "Mark Davis" <mark@macchiato.com>; "Erik Nordmark"
> <Erik.Nordmark@eng.sun.com>
> Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
> <idn@ops.ietf.org>
> Sent: Tuesday, October 23, 2001 11:17 PM
> Subject: Re: [idn] Which lanuages/scripts to reorder?
> 
> 
> 
> ----- Original Message -----
> From: "Mark Davis" <mark@macchiato.com>
> To: "Soobok Lee" <lsb@postel.co.kr>; "Erik Nordmark"
> <Erik.Nordmark@eng.sun.com>
> Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
> <idn@ops.ietf.org>
> Sent: Tuesday, October 23, 2001 11:59 PM
> Subject: Re: [idn] Which lanuages/scripts to reorder?
> 
> 
> > >Therefore, your concerns about long path of reordering revisioning is
> NOT
> > new >problem,but rather just one of never-terminaing nameprep/ACE
> > revisioning >problem.
> >
> > I disagree completely. Nameprep is designed so that it will work even
> if a
> > server and a client are on different versions, and without any version
> > number involved. That would absolutely fail if reordering were changed
> in
> > any future version.
> 
> Reordering won't be changed and  remains as sub-optimal frequency tables
> forever without new prefix, as i repeated many time in this list.
> 
> What i mean is adding NEW reordering tables for *NEW SCRIPTS*
> in accordance with new SCRIPT support in newer nameprep.
> I agree with you that reordering table for old existing scripts should
> not be changed .
> 
> each Nameprep version defines unassigned code points which reordering
> should
> not touch at all. That enforce  reordering  upgrade path strictly to
> follow  that of nameprep.
> 
> Soobok Lee
> 
> >
> > Introducing explicit version numbers (and it could not be limited to
> 2)
> > would not help -- it would just make things worse.
> >
> > Mark
> > —————
> >
> > Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
> > [http://www.macchiato.com]
> >
> > ----- Original Message -----
> > From: "Soobok Lee" <lsb@postel.co.kr>
> > To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> > Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
> > <idn@ops.ietf.org>
> > Sent: Tuesday, October 23, 2001 05:34
> > Subject: Re: [idn] Which lanuages/scripts to reorder?
> >
> >
> >
> > ----- Original Message -----
> > From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> > To: "Soobok Lee" <lsb@postel.co.kr>
> > Cc: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>; "Eric
> Brunner-Williams in
> > Portland Maine" <brunner@nic-naa.net>; <idn@ops.ietf.org>
> > Sent: Tuesday, October 23, 2001 7:25 PM
> > Subject: Re: [idn] Which lanuages/scripts to reorder?
> >
> >
> > >
> > > > seamless upgrade idea for adding new script reordering tables and
> new
> > > > nameprep rules (NF/casemappings) are described in the posting
> titled
> > with
> > > > "suggestion : two prefices ....". No newer prefix other than (zq--
> and
> > uq--)
> > > > will be needed forever. I recommend you to comment on the
> suggestion
> > first
> > > > before you go further.
> > >
> > > Soobok,
> > >
> > > We seem to have a failure to communicate.
> > > I've placed one new concern on the table which does not have
> anything to
> > > do with how you could technically upgrade to new reordering tables.
> > >
> > > My concern is about that the process of definition reordering tables
> > > might never terminate (or might take a decade or so) since there
> might
> > very
> > > well be a request to add more and more languages/scripts to the
> tables
> > before
> > > we ever get to produce a single RFC.
> > >
> >
> > Erik,
> >
> > new reordering tables can be added only when there comes new nameprep
> > revision for newly added scripts, because reordering tables is
> proposed as
> > one candidate of nameprep/ACE components. that is, reordering tables
> are
> > bound by the versioning of nameprep.
> >
> > nameprep (as one profile of stringprep) upgrade paths also never
> terminate
> > because there will be more and more scripts pending for approval over
> time.
> >
> > If you look into nameprep/stringprep document, each version of
> nameprep
> > should specify  the used unicode version and the list of unassigned
> code
> > points in
> > in that version. If new versions of unicode accumulate enough set of
> new
> > scripts for justifying major nameprep revision, then IETF IDN WG
> should work
> > again to give birth to new nameprep profile with new list (maybe
> reduced by
> > the amount of new assigned code points) of unassgined code points and
> new
> > version number of unicode.
> >
> > Therefore, your concerns about long path of reordering revisioning is
> NOT
> > new problem,but rather just one of never-terminaing nameprep/ACE
> revisioning
> > problem.
> >
> > if we finalize IDN  before TAGALOG is assigned and added, current
> nameprep's
> > architecture for unassigned code points, does not allow us to register
> > tagalog domains   until new nameprep version come out by IETF
> activities in
> > the undefined time in the future.
> >
> > My two prefix(uq-- and zq--) scheme proposal tries to solve this
> inherenet
> > problem of user inconveniences in treatment of unassigned code points,
> even
> > before distributions of new version of nameprep which often take *too
> much
> > time* to serve the TAGALOG users' need.
> >
> >
> >
> > Soobok Lee
> >
> > > I do not have anything to add to the techical issue of how upgrade
> > > to new reordering tables as that was not the issue over which
> > > I expressed concern. Thus it makes no sense to me to comment on that
> > issue.
> > >
> > >
> > > Sincerely,
> > >   Erik
> > >
> > >
> > >
> >
> >
> >
> >
> 
> 
> 




From owner-idn@ops.ietf.org  Tue Oct 23 12:09:44 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09338
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 12:09:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w3yZ-000BTW-00
	for idn-data@psg.com; Tue, 23 Oct 2001 09:00:23 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w3yY-000BTO-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 09:00:22 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id BAA02247;
	Wed, 24 Oct 2001 01:00:04 +0900
Message-ID: <035501c15bdb$eba0bd70$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <DougEwell2@cs.com>, <idn@ops.ietf.org>
Cc: <mark@macchiato.com>, <Erik.Nordmark@eng.sun.com>, <brunner@nic-naa.net>
References: <15b.2e6239d.2906ecf6@cs.com>
Subject: Re: [idn] Which lanuages/scripts to reorder? 
Date: Wed, 24 Oct 2001 01:01:04 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA09338


----- Original Message ----- 
From: <DougEwell2@cs.com>
To: <idn@ops.ietf.org>
Cc: <lsb@postel.co.kr>; <mark@macchiato.com>; <Erik.Nordmark@eng.sun.com>; <brunner@nic-naa.net>
Sent: Wednesday, October 24, 2001 12:55 AM
Subject: Re: [idn] Which lanuages/scripts to reorder? 


> In a message dated 2001-10-23 8:36:48 Pacific Daylight Time, lsb@postel.co.kr 
> writes:
> 
> >  Reordering won't be changed and  remains as sub-optimal frequency tables
> >  forever without new prefix, as i repeated many time in this list.
> >
> >  What i mean is adding NEW reordering tables for *NEW SCRIPTS*
> >  in accordance with new SCRIPT support in newer nameprep.
> >  I agree with you that reordering table for old existing scripts should not 
> >  be changed .
> 
> Reordering is, first and last, based on the tables.  If you create new 
> tables, you have by definition created a new version of reordering.  I don't 
> think you can say "reordering won't be changed" and then suggest one sentence 
> later that new tables could be added in the future.

yes. you are right. I missed "tables" in the first sentence.
"  Reordering <tables> won't be changed " is the right one.

Regards,
Soobok Lee


> 
> However, I'm sure everyone will at least be glad to see that existing tables 
> would not be touched.



> 
> -Doug Ewell
>  Fullerton, California
> 




From owner-idn@ops.ietf.org  Tue Oct 23 12:42:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10683
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 12:42:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w4TW-000CJ7-00
	for idn-data@psg.com; Tue, 23 Oct 2001 09:32:22 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w4TU-000CJ1-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 09:32:20 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP id 1C75EFFC12
	for <idn@ops.ietf.org>; Wed, 24 Oct 2001 00:32:39 +0800 (SGT)
Message-ID: <011701c15be0$4473db90$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <idn@ops.ietf.org>
Subject: [idn] (bias) summary of reordering discussion
Date: Wed, 24 Oct 2001 00:32:11 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On the questions posted:

1. Efficient - I accepted that reordering produce a shorter ACE string,
sometimes as much as 20%. This means instead of a "zq--zxcvbnmasdfg"
label, I get a "zq--zxcvbnmasd". I do not buy the arguments it is
helpful to naked eye, to memorised or save RAM however.

2. Compression efficient in future since statistic - Lee's counter that
compression "always SHORTER labels than usual". Mathematically, it can
be proven this is wrong (very basic pigeon hole principle).

3. Referencing from established I18N organisation - ISO14651 is deem
inappropriate and I agree with it. No alternative was proposed.

4. Stability of reordering - Lee's countered with the arguments that
reordering tables would never changed. I am not sure if that is possible
but I agree with the assessment that it is possible to design reordering
to be stable. However, I like to see explictive statement in future
draft.

5. Future additional of code points / changes to reordering - Lee's
proposal is a two prefix solution, using prefix as a versioning tag. I
do not like to solve a problem by creating others, especially one which
makes it even more complex. Lee have yet to address the process of how
future additional of code points or changes to reordering could be done.
(IDN WG is not going to exist forever...I dream of finishing our work
one day).

6. Reordering is never ending task - Lee's countered that so is
Nameprep. My thoughts is two wrong dont make one right. (OTOH, Nameprep
which is based on UTC work have explicit principles on how it can be
done. And Nameprep is not subjective to frequency analysis changes which
reordering is)

Of the people participate in the reordering discussion

Martin Duerst - explicit objection
Mark Davis - not very supportive, not explicit
Adam Costello - (no conclusion from comments)
Doug Ewell - explicit objection
Paul Hoffman - explicit objection
Eric Brunner-William - somewhat supportive, not explicit
Kenny Huang - (no conclusion from comments)
James Seng - explicit objection
Karlsson Kent - explicit objection
Erik Nordmark - not very supportive
David Hopwood - (no conclusion from comments)

This is my rough read of the discussion on reordering so far (please
correct me, and apologise in advance, if I am wrong).

(Wearing my co-chair's hat) It is not a vote or even a strawpoll here
obviously but I am trying to get a feel of the group consensus. But if
these discussion is any indication of the group consensus, it does not
indicate very little support for reordering. If there is other comments,
please bring them forward soon. Thanks.

-James Seng




From owner-idn@ops.ietf.org  Tue Oct 23 13:02:35 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11528
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 13:02:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w4mp-000CfV-00
	for idn-data@psg.com; Tue, 23 Oct 2001 09:52:19 -0700
Received: from femail42.sdc1.sfba.home.com ([24.254.60.36])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w4mo-000CfP-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 09:52:18 -0700
Received: from c1340594a ([65.11.104.12]) by femail42.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20011023165216.EAEP4145.femail42.sdc1.sfba.home.com@c1340594a>;
          Tue, 23 Oct 2001 09:52:16 -0700
Message-ID: <013301c15be3$30ff5c30$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
References: <011701c15be0$4473db90$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] (bias) summary of reordering discussion
Date: Tue, 23 Oct 2001 09:53:07 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Count me as against the reordering; I think there has been some interesting
work done on it, but I don't believe it is necessary for IDN.

Mark

—————

Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
[http://www.macchiato.com]

----- Original Message -----
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <idn@ops.ietf.org>
Sent: Tuesday, October 23, 2001 09:32
Subject: [idn] (bias) summary of reordering discussion


> On the questions posted:
>
> 1. Efficient - I accepted that reordering produce a shorter ACE string,
> sometimes as much as 20%. This means instead of a "zq--zxcvbnmasdfg"
> label, I get a "zq--zxcvbnmasd". I do not buy the arguments it is
> helpful to naked eye, to memorised or save RAM however.
>
> 2. Compression efficient in future since statistic - Lee's counter that
> compression "always SHORTER labels than usual". Mathematically, it can
> be proven this is wrong (very basic pigeon hole principle).
>
> 3. Referencing from established I18N organisation - ISO14651 is deem
> inappropriate and I agree with it. No alternative was proposed.
>
> 4. Stability of reordering - Lee's countered with the arguments that
> reordering tables would never changed. I am not sure if that is possible
> but I agree with the assessment that it is possible to design reordering
> to be stable. However, I like to see explictive statement in future
> draft.
>
> 5. Future additional of code points / changes to reordering - Lee's
> proposal is a two prefix solution, using prefix as a versioning tag. I
> do not like to solve a problem by creating others, especially one which
> makes it even more complex. Lee have yet to address the process of how
> future additional of code points or changes to reordering could be done.
> (IDN WG is not going to exist forever...I dream of finishing our work
> one day).
>
> 6. Reordering is never ending task - Lee's countered that so is
> Nameprep. My thoughts is two wrong dont make one right. (OTOH, Nameprep
> which is based on UTC work have explicit principles on how it can be
> done. And Nameprep is not subjective to frequency analysis changes which
> reordering is)
>
> Of the people participate in the reordering discussion
>
> Martin Duerst - explicit objection
> Mark Davis - not very supportive, not explicit
> Adam Costello - (no conclusion from comments)
> Doug Ewell - explicit objection
> Paul Hoffman - explicit objection
> Eric Brunner-William - somewhat supportive, not explicit
> Kenny Huang - (no conclusion from comments)
> James Seng - explicit objection
> Karlsson Kent - explicit objection
> Erik Nordmark - not very supportive
> David Hopwood - (no conclusion from comments)
>
> This is my rough read of the discussion on reordering so far (please
> correct me, and apologise in advance, if I am wrong).
>
> (Wearing my co-chair's hat) It is not a vote or even a strawpoll here
> obviously but I am trying to get a feel of the group consensus. But if
> these discussion is any indication of the group consensus, it does not
> indicate very little support for reordering. If there is other comments,
> please bring them forward soon. Thanks.
>
> -James Seng
>
>
>




From owner-idn@ops.ietf.org  Tue Oct 23 13:25:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12515
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 13:25:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w5B6-000DDF-00
	for idn-data@psg.com; Tue, 23 Oct 2001 10:17: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.33 #1)
	id 15w5B5-000DCg-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 10:17:23 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9NHH0N33043;
	Tue, 23 Oct 2001 13:17:01 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110231717.f9NHH0N33043@nic-naa.net>
X-Mailer: exmh version 1.6.9 8/22/96
To: jseng@pobox.org.sg
cc: idn@ops.ietf.org
Subject: Re: [idn] (bias) summary of reordering discussion 
Date: Tue, 23 Oct 2001 13:17:00 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Count me as for the reordering, some work remains to be done, a proposal may
be made before the Salt Lake cut-off, and I believe it is necessary for IDN.

Similar to Mark, with polarity reversed.

Eric 




From owner-idn@ops.ietf.org  Tue Oct 23 13:26:01 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12531
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 13:26:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w531-000D3j-00
	for idn-data@psg.com; Tue, 23 Oct 2001 10:09:03 -0700
Received: from femail27.sdc1.sfba.home.com ([24.254.60.17])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w530-000D3d-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 10:09:02 -0700
Received: from c1340594a ([65.11.104.12]) by femail27.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20011023170901.GWRF12089.femail27.sdc1.sfba.home.com@c1340594a>;
          Tue, 23 Oct 2001 10:09:01 -0700
Message-ID: <013901c15be5$87fabf00$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>,
        "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        <idn@ops.ietf.org>
References: <Roam.SIMC.2.0.6.1003832725.4114.nordmark@bebop.france> <028701c15bbf$1b4396a0$ec1bd9d2@temp> <00a001c15bd3$5448aa80$0c680b41@c1340594a> <032f01c15bd8$4bf75b10$ec1bd9d2@temp>
Subject: Re: [idn] Which lanuages/scripts to reorder? 
Date: Tue, 23 Oct 2001 10:09:52 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

That may work. However, I believe that it implies some limitiations on
reordering to preserve compatibility across versions.

Example: Suppose that at some time in the future there are 4 versions: A, B,
C, D.

I send you zq--XXX. It contains a character UA that is unassigned in A (but
not B), a character UB that is unassigned in B (but not C), and a character
UC that is unassigned in C (but not D). With normal nameprep this doesn't
matter. You should use version D of nameprep to read the IDN. If you use a
back-rev'd version, you will simply recognize that it has an unassigned
character, and reject the name.

Now suppose that we have reordering, and you are back-rev'ed, and support C
but not D. When you get UC, you have to be able to recognize that it is an
unassigned character to know to reject it. That means that within any
version (I think after the first), isUnassigned(x) if and only if
isUnassigned(reordered(x)). Thus any future changes in reordering have to
preserve the "unassigned" status: so the future reorderings have to be, in
some sense, "in place".

Mark
—————

Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
[http://www.macchiato.com]

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Mark Davis" <mark@macchiato.com>; "Erik Nordmark"
<Erik.Nordmark@eng.sun.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
<idn@ops.ietf.org>
Sent: Tuesday, October 23, 2001 08:35
Subject: Re: [idn] Which lanuages/scripts to reorder?



----- Original Message -----
From: "Mark Davis" <mark@macchiato.com>
 > Introducing explicit version numbers (and it could not be limited to 2)
> would not help -- it would just make things worse.
>

Mark,
You may missed my point.
two prefix uq-- and zq-- does *not*  limit  the versioning into 2 times, but
infinite times.

zq-- is for valid ACE labels  for the all version of nameprep and
uq-- is for invalid ACE labels including at least one unassigned code points
for all versions of
nameprep.

This differentiating ace prefixing scheme works  in all version of nameprep
from 1 to infinity.

newly supported script in nameprep/ACE version 5 will be
encoded using  uq--????  with old nameprep/ACE version 4  and below.
But with namepre/ACE version 5 or above, it will be encoded zq--???? .

Likewise,
labels contain newly supported script in nameprep/ACE version 6 will be
encoded using  uq--????  with old nameprep/ACE version 5 and below.
But with namepre/ACE version 6 or above, it will be encoded zq--???? .

And so on.

There is no need for version numbered prefix  for each of version 2,3,4,5,6,
.....

Current nameprep does not encode unassigned code points into ACE for
"saved strings", but my two prefix scheme allow it with "uq--" prefix  which
provide with  rooms for incorporating  some useful fallback mechanims.
Even with dealing with ACE foor lookup "query", it provide some clues
about the version of nameprep which encode the ACE lables by the
distintion of "uq--" and "zq--".
I am proposing new nameprep behavior for unassigned code points for
"saved string" and "query" through out  nameprep versioning path.
Not about  versioning nameprep itself!

Soobok Lee


> Mark
> —————
>
> Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
> [http://www.macchiato.com]
>
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
> <idn@ops.ietf.org>
> Sent: Tuesday, October 23, 2001 05:34
> Subject: Re: [idn] Which lanuages/scripts to reorder?
>
>
>
> ----- Original Message -----
> From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> To: "Soobok Lee" <lsb@postel.co.kr>
> Cc: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>; "Eric Brunner-Williams in
> Portland Maine" <brunner@nic-naa.net>; <idn@ops.ietf.org>
> Sent: Tuesday, October 23, 2001 7:25 PM
> Subject: Re: [idn] Which lanuages/scripts to reorder?
>
>
> >
> > > seamless upgrade idea for adding new script reordering tables and new
> > > nameprep rules (NF/casemappings) are described in the posting titled
> with
> > > "suggestion : two prefices ....". No newer prefix other than (zq-- and
> uq--)
> > > will be needed forever. I recommend you to comment on the suggestion
> first
> > > before you go further.
> >
> > Soobok,
> >
> > We seem to have a failure to communicate.
> > I've placed one new concern on the table which does not have anything to
> > do with how you could technically upgrade to new reordering tables.
> >
> > My concern is about that the process of definition reordering tables
> > might never terminate (or might take a decade or so) since there might
> very
> > well be a request to add more and more languages/scripts to the tables
> before
> > we ever get to produce a single RFC.
> >
>
> Erik,
>
> new reordering tables can be added only when there comes new nameprep
> revision for newly added scripts, because reordering tables is proposed as
> one candidate of nameprep/ACE components. that is, reordering tables are
> bound by the versioning of nameprep.
>
> nameprep (as one profile of stringprep) upgrade paths also never terminate
> because there will be more and more scripts pending for approval over
time.
>
> If you look into nameprep/stringprep document, each version of nameprep
> should specify  the used unicode version and the list of unassigned code
> points in
> in that version. If new versions of unicode accumulate enough set of new
> scripts for justifying major nameprep revision, then IETF IDN WG should
work
> again to give birth to new nameprep profile with new list (maybe reduced
by
> the amount of new assigned code points) of unassgined code points and new
> version number of unicode.
>
> Therefore, your concerns about long path of reordering revisioning is NOT
> new problem,but rather just one of never-terminaing nameprep/ACE
revisioning
> problem.
>
> if we finalize IDN  before TAGALOG is assigned and added, current
nameprep's
> architecture for unassigned code points, does not allow us to register
> tagalog domains   until new nameprep version come out by IETF activities
in
> the undefined time in the future.
>
> My two prefix(uq-- and zq--) scheme proposal tries to solve this inherenet
> problem of user inconveniences in treatment of unassigned code points,
even
> before distributions of new version of nameprep which often take *too much
> time* to serve the TAGALOG users' need.
>
>
>
> Soobok Lee
>
> > I do not have anything to add to the techical issue of how upgrade
> > to new reordering tables as that was not the issue over which
> > I expressed concern. Thus it makes no sense to me to comment on that
> issue.
> >
> >
> > Sincerely,
> >   Erik
> >
> >
> >
>
>
>
>







From owner-idn@ops.ietf.org  Tue Oct 23 13:27:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12620
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 13:27:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w58v-000D9q-00
	for idn-data@psg.com; Tue, 23 Oct 2001 10:15:09 -0700
Received: from femail26.sdc1.sfba.home.com ([24.254.60.16])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w58u-000D9k-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 10:15:08 -0700
Received: from c1340594a ([65.11.104.12]) by femail26.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20011023171507.EGHF2746.femail26.sdc1.sfba.home.com@c1340594a>;
          Tue, 23 Oct 2001 10:15:07 -0700
Message-ID: <014b01c15be6$62169f60$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>, "Karlsson Kent - keka" <keka@im.se>,
        <idn@ops.ietf.org>
Cc: "Martin Duerst" <duerst@w3.org>, <DougEwell2@cs.com>
References: <C110A2268F8DD111AA1A00805F85E58D0115ACBC@ntgbg1> <004901c15b29$0c552d20$ec1bd9d2@temp> <00b501c15b74$45047ae0$0c680b41@c1340594a> <016501c15b78$1d38a820$ec1bd9d2@temp>
Subject: Re: [idn] call for comments for REORDERING
Date: Tue, 23 Oct 2001 10:15:58 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

1. Yes, the mapping tables for (1) were singular mappings, so it was not
possible to add the fillers. I agree that ideally the decomposition could
have included fillers -- and that might have been a better choice in
retrospect-- but the compatibility mappings are intended to preserve
fundamental character identity, not formatting -- including whether the jamo
are grouped into a single box in display or not.

Some time ago I asked whether there were any cases where it was absolutely
necessary to have two different IDNs, one with a syllable and the other with
two separate Jamo. Nobody responded with any examples. If you have some,
that would be productive.

2. Martin wrote a very nice response on this, so I won't add anything.

Mark
—————

Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
[http://www.macchiato.com]

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Mark Davis" <mark@macchiato.com>; "Karlsson Kent - keka" <keka@im.se>;
<idn@ops.ietf.org>
Cc: "Martin Duerst" <duerst@w3.org>; <DougEwell2@cs.com>
Sent: Monday, October 22, 2001 21:06
Subject: Re: [idn] call for comments for REORDERING



----- Original Message -----
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>; "Karlsson Kent - keka" <keka@im.se>;
<idn@ops.ietf.org>
Cc: "Martin Duerst" <duerst@w3.org>; <DougEwell2@cs.com>
Sent: Tuesday, October 23, 2001 12:39 PM
Subject: Re: [idn] call for comments for REORDERING


> 1. The compatibility hangul jamo are not the preferred way to express
> isolated jamo in Unicode. That would be by the use of conjoining jamo with
> fillers. If the preferred forms are used, there are no problems.
>
But, KSC5601-->Unicode mapping tables  maps  KSC5601 isolated hangul jamo
into compat hangul jamo. The mapping table was issued by UTC itself and
placed into WIN98,2K,XP and most unix and linux platforms.
Inconsistency!


> 2. NFC does not combine ancient Hangul into syllables because there are no
> syllables that have ancient Hangul in them. It does combine as many modern
> Jamo as possible into syllables. That does not -- at all -- prevent the
use
> of NFC with ancient Hangul.

Rendering problem remains unsolved.
"hangul  syllable ga + old jamo bansioth " != "old hangul syllable
ga+bansioth".
There is defined no such false equivalence  in UTR15.
 Why rendering engine vendors should  make such false workarounds not
recommended in UTC standards?
NFC is  dangerous for ancient hangul.

>
> Mark
> —————
>
> Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
> [http://www.macchiato.com]
>
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: "Karlsson Kent - keka" <keka@im.se>; <idn@ops.ietf.org>
> Cc: "Martin Duerst" <duerst@w3.org>; <DougEwell2@cs.com>
> Sent: Monday, October 22, 2001 11:40
> Subject: Re: [idn] call for comments for REORDERING
>
>
>
> ----- Original Message -----
> From: "Karlsson Kent - keka" <keka@im.se>
> >
> > > I know current NFC/NFKC has *severely flawed* hangul jamo
> >
> > Now that's a new complaint.  At least to me.  Not even the
> > delegations from DPRK complain about that. (And they have
> > all sorts of complaints.)  Do you care to say a little bit
> > more about what you mean?  Or are we just to take your word
> > for it?  There was a problem in earlier drafts of UAX 15
> > concerning Hangul and NFKC (Hangul syllables were not preserved),
> > but that problem was removed before that UTR became a UAX.
>
> two problems:
>
>  1) NFKC maps   compatibility hangul jamo (U+32??) into
>                 conjoining hangul jamo without fillers.
>     That converts compat hangul jamo sequences into conjoining
>       jamo sequences and they are combined partially in some cases
>         by the NFC following  compatibilty decomposition.
>     Modern hangul informal texts contains compatibiilty jamos very often.
>     If the texts contains choseong + jungseong sequence in compat jamo,
>        they will be affected by this fault.
>     This fault was found by Soobok Lee, too lately.
>
>  2) NFC  does not combine  archaic(old) hangul trailing jamo into the
>      preceding half-combined syllable (from choseong jamo + jungseong
jamo),
>       but leave it alone as an isolated conjoining jamo.
>     That means archail hangul syllable which has old hangul trailing jamo
>       cannot be preserved through out NFKC.
>     NFKC cannot be used for scholarly texts which contains archail hangul
>       syllables.  This fault was found by Martin, too lately.
>
> Mark and Martin knew and told me why this happened.
> Martin, would you comment on this?
>
> Soobok Lee
>
>
> >
> > > I hope UTC cures this BUGGY NFC/NFKC jamo handling as an
> > > exceptional case while it is in  strict adherence to UTR's backward
> > > compatiblity policy & promise.
> >
> > The normal forms for strings of already allocated characters
> > will not be changed any more.
> >
> > Kind regards
> > /Kent K
> >
>
>
>
>






From owner-idn@ops.ietf.org  Tue Oct 23 13:39:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12991
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 13:39:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w5Fz-000DK9-00
	for idn-data@psg.com; Tue, 23 Oct 2001 10:22:27 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w5Fy-000DJz-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 10:22:26 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id CAA27643;
	Wed, 24 Oct 2001 02:22:16 +0900
Message-ID: <038f01c15be7$62eb3800$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
References: <011701c15be0$4473db90$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] (bias) summary of reordering discussion
Date: Wed, 24 Oct 2001 02:23:09 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA12991


----- Original Message ----- 
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <idn@ops.ietf.org>
Sent: Wednesday, October 24, 2001 1:32 AM
Subject: [idn] (bias) summary of reordering discussion


> On the questions posted:
> 
> 1. Efficient - I accepted that reordering produce a shorter ACE string,
> sometimes as much as 20%. This means instead of a "zq--zxcvbnmasdfg"
> label, I get a "zq--zxcvbnmasd". I do not buy the arguments it is
> helpful to naked eye, to memorised or save RAM however.

  the 20% is just the mean average. 40% improvement is not rare for
   most frequency words, especiall in the case of hangul 9-letter KRNIC ( 29->16).
   and Tokyo Univ in Han ( 11->7 ).

  i mentioned the limit in mobile device's narrow LCD panel and precious ram/rom resources.  
  Also Good for visually impaired one or childrens and elder ones and for me .
  
  In the case of  sub-ML.ML.com, The sum of saved characters
   are multiplied by 2 with reordering.

  Take this into your considerations.

> 
> 2. Compression efficient in future since statistic - Lee's counter that
> compression "always SHORTER labels than usual". Mathematically, it can
> be proven this is wrong (very basic pigeon hole principle).
> 
  ALready answered. You may have missed that.
   0.3% hangul labels get longer by 1 character, while 99.6% labels got shorter
    by greater amounts. the net gain is always positive for each length N.


> 3. Referencing from established I18N organisation - ISO14651 is deem
> inappropriate and I agree with it. No alternative was proposed.

  sub-optimal tuning parameters not revealed to outside of ACE. they  need authorities ?  i think it need not.

> 
> 4. Stability of reordering - Lee's countered with the arguments that
> reordering tables would never changed. I am not sure if that is possible
> but I agree with the assessment that it is possible to design reordering
> to be stable. However, I like to see explictive statement in future
> draft.
> 
> 5. Future additional of code points / changes to reordering - Lee's
> proposal is a two prefix solution, using prefix as a versioning tag. I
> do not like to solve a problem by creating others, especially one which
> makes it even more complex. Lee have yet to address the process of how
> future additional of code points or changes to reordering could be done.
> (IDN WG is not going to exist forever...I dream of finishing our work
> one day).

 Already answered. read my recent articles. 
 new reordering support of new script in Tandem with newer nameprep for
 the new script. no new prefix needed if there will be no change 
 in existing stable reordering tables.

 You have misunderstanding of my proposal. 

> 
> 6. Reordering is never ending task - Lee's countered that so is
> Nameprep. My thoughts is two wrong dont make one right. (OTOH, Nameprep
> which is based on UTC work have explicit principles on how it can be
> done. And Nameprep is not subjective to frequency analysis changes which
> reordering is)

 Statistical Frequency is always sub-optimal tuning parameters. better than not.
 What's your position on engineering tuning paramters in various 
 protocols ?, eg. Ethernet packet length, ttl, flag length in tcp/udp etc.... 
 

Soobok Lee




From owner-idn@ops.ietf.org  Tue Oct 23 13:39:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13002
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 13:39:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w5Mp-000DYL-00
	for idn-data@psg.com; Tue, 23 Oct 2001 10:29:31 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w5Mo-000DYF-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 10:29:30 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VV0lv9/VESVlwwUD0kHwNbKg==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GJFYRZJB; Tue, 23 Oct 2001 13:28:40 EDT
To: lsb@postel.co.kr
Cc: mark@macchiato.com, Erik.Nordmark@eng.sun.com, brunner@nic-naa.net,
        idn@ops.ietf.org
Date: Tue, 23 Oct 2001 10:35:33 -0700
Subject: Re: [idn] Which lanuages/scripts to reorder?
Message-ID: <20011023.103535.-133319.0.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.5
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-19,21-211
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana Ye <liana.ydisg@juno.com>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Soobok,
   I think the versioning in nameprep/stringprep can handle one 
type of change - addition to Unicode table .  To add another change 
such as recodering a Unicode code table, the complexity 
increases and it is dangerous to ask for.

 In addition, the reordering envolves individual code blocks of 
treatment, which is based on frequency of usage.  It is good 
for individual input, it is good for applications of particular user
group, for example a steel industry, a transportation industry or 
even news reporters, but it is not good when we're trying to find 
a common denominator to cross various scripts.  If you believe
there is a common denominating use of the frequency based
treatment, that should be a topic in Unicode group when forming 
such a table and providing guide in using these tables, such 
as advice like "no TC/SC in nameprep" (as IDN is the group
in making that decision).

Liana

On Wed, 24 Oct 2001 00:35:08 +0900 "Soobok Lee" <lsb@postel.co.kr>
writes:
> 
> ----- Original Message ----- 
> From: "Mark Davis" <mark@macchiato.com>
>  > Introducing explicit version numbers (and it could not be limited 
> to 2)
> > would not help -- it would just make things worse.
> > 
> 
> Mark, 
> You may missed my point.
> two prefix uq-- and zq-- does *not*  limit  the versioning into 2 
> times, but infinite times.
> 
> zq-- is for valid ACE labels  for the all version of nameprep and
> uq-- is for invalid ACE labels including at least one unassigned 
> code points for all versions of 
> nameprep.
> 
> This differentiating ace prefixing scheme works  in all version of 
> nameprep from 1 to infinity.
> 
> newly supported script in nameprep/ACE version 5 will be
> encoded using  uq--????  with old nameprep/ACE version 4  and below.
> But with namepre/ACE version 5 or above, it will be encoded zq--???? 
> .
> 
> Likewise,
> labels contain newly supported script in nameprep/ACE version 6 will 
> be
> encoded using  uq--????  with old nameprep/ACE version 5 and below.
> But with namepre/ACE version 6 or above, it will be encoded zq--???? 
> .
> 
> And so on.
> 
> There is no need for version numbered prefix  for each of version 
> 2,3,4,5,6, .....
> 
> Current nameprep does not encode unassigned code points into ACE for
> "saved strings", but my two prefix scheme allow it with "uq--" 
> prefix  which
> provide with  rooms for incorporating  some useful fallback 
> mechanims.
> Even with dealing with ACE foor lookup "query", it provide some 
> clues
> about the version of nameprep which encode the ACE lables by the
> distintion of "uq--" and "zq--".
> I am proposing new nameprep behavior for unassigned code points for 
> "saved string" and "query" through out  nameprep versioning path. 
> Not about  versioning nameprep itself!
> 
> Soobok Lee
> 
> 
> > Mark
> > ————â€?
> > 
> > Δός μοι ποá¿?στá¿? καá½?κινá¿?τὴÎ?γῆÎ?
> â€?Ἀρχιμήδης
> > [http://www.macchiato.com]
> > 
> > ----- Original Message -----
> > From: "Soobok Lee" <lsb@postel.co.kr>
> > To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> > Cc: "Eric Brunner-Williams in Portland Maine" 
> <brunner@nic-naa.net>;
> > <idn@ops.ietf.org>
> > Sent: Tuesday, October 23, 2001 05:34
> > Subject: Re: [idn] Which lanuages/scripts to reorder?
> > 
> > 
> > 
> > ----- Original Message -----
> > From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> > To: "Soobok Lee" <lsb@postel.co.kr>
> > Cc: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>; "Eric 
> Brunner-Williams in
> > Portland Maine" <brunner@nic-naa.net>; <idn@ops.ietf.org>
> > Sent: Tuesday, October 23, 2001 7:25 PM
> > Subject: Re: [idn] Which lanuages/scripts to reorder?
> > 
> > 
> > >
> > > > seamless upgrade idea for adding new script reordering tables 
> and new
> > > > nameprep rules (NF/casemappings) are described in the posting 
> titled
> > with
> > > > "suggestion : two prefices ....". No newer prefix other than 
> (zq-- and
> > uq--)
> > > > will be needed forever. I recommend you to comment on the 
> suggestion
> > first
> > > > before you go further.
> > >
> > > Soobok,
> > >
> > > We seem to have a failure to communicate.
> > > I've placed one new concern on the table which does not have 
> anything to
> > > do with how you could technically upgrade to new reordering 
> tables.
> > >
> > > My concern is about that the process of definition reordering 
> tables
> > > might never terminate (or might take a decade or so) since there 
> might
> > very
> > > well be a request to add more and more languages/scripts to the 
> tables
> > before
> > > we ever get to produce a single RFC.
> > >
> > 
> > Erik,
> > 
> > new reordering tables can be added only when there comes new 
> nameprep
> > revision for newly added scripts, because reordering tables is 
> proposed as
> > one candidate of nameprep/ACE components. that is, reordering 
> tables are
> > bound by the versioning of nameprep.
> > 
> > nameprep (as one profile of stringprep) upgrade paths also never 
> terminate
> > because there will be more and more scripts pending for approval 
> over time.
> > 
> > If you look into nameprep/stringprep document, each version of 
> nameprep
> > should specify  the used unicode version and the list of 
> unassigned code
> > points in
> > in that version. If new versions of unicode accumulate enough set 
> of new
> > scripts for justifying major nameprep revision, then IETF IDN WG 
> should work
> > again to give birth to new nameprep profile with new list (maybe 
> reduced by
> > the amount of new assigned code points) of unassgined code points 
> and new
> > version number of unicode.
> > 
> > Therefore, your concerns about long path of reordering revisioning 
> is NOT
> > new problem,but rather just one of never-terminaing nameprep/ACE 
> revisioning
> > problem.
> > 
> > if we finalize IDN  before TAGALOG is assigned and added, current 
> nameprep's
> > architecture for unassigned code points, does not allow us to 
> register
> > tagalog domains   until new nameprep version come out by IETF 
> activities in
> > the undefined time in the future.
> > 
> > My two prefix(uq-- and zq--) scheme proposal tries to solve this 
> inherenet
> > problem of user inconveniences in treatment of unassigned code 
> points,  even
> > before distributions of new version of nameprep which often take 
> *too much
> > time* to serve the TAGALOG users' need.
> > 
> > 
> > 
> > Soobok Lee
> > 
> > > I do not have anything to add to the techical issue of how 
> upgrade
> > > to new reordering tables as that was not the issue over which
> > > I expressed concern. Thus it makes no sense to me to comment on 
> that
> > issue.
> > >
> > >
> > > Sincerely,
> > >   Erik
> > >
> > >
> > >
> > 
> > 
> > 
> > 
> 
> 



From owner-idn@ops.ietf.org  Tue Oct 23 13:59:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13854
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 13:59:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w5em-000DxO-00
	for idn-data@psg.com; Tue, 23 Oct 2001 10:48:04 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w5el-000DxH-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 10:48:04 -0700
Received: from [192.168.1.5] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id TAA14569;
	Tue, 23 Oct 2001 19:47:21 +0200 (MET DST)
Date: Tue, 23 Oct 2001 19:41:11 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: "James Seng/Personal" <jseng@pobox.org.sg>, idn@ops.ietf.org
Subject: Re: [idn] (bias) summary of reordering discussion
Message-ID: <153522.1003866071@localhost>
In-Reply-To: <011701c15be0$4473db90$dd00a8c0@jamessonyvaio>
References:  <011701c15be0$4473db90$dd00a8c0@jamessonyvaio>
X-Mailer: Mulberry/2.1.0 (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 2001-10-24 00.32 +0800 "James Seng/Personal" <jseng@pobox.org.sg>
wrote:

> 6. Reordering is never ending task - Lee's countered that so is
> Nameprep.

I have not read all details in this long thread of reordering, but, I have
a strong feeling about some principal issues:

o Nameprep mappings is defined by UTC, not IETF.
  -> I am nervous when we in IETF talk about these things
o Versioning in Nameprep is stable for assigned codepoints, as
  the mappings for an assigned codepoint is never changed.
  -> My reading of the reordering is that some reordering rules
     might be added later for assigned codepoints
o Better compression is a good thing, but I don't see reordering
  gaining so much that it is worth it (see bullets above)

So, to conclude, I also oppose reordering.

For more details on versioning, and my view on it, see separate response to
Soobok Lee.

              paf




From owner-idn@ops.ietf.org  Tue Oct 23 14:08:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14217
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 14:08:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w5ko-000E3y-00
	for idn-data@psg.com; Tue, 23 Oct 2001 10:54:18 -0700
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w5kn-000E3s-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 10:54:18 -0700
Received: from ns.jck.com ([209.187.148.211] helo=wave-94.research.att.com)
	by bs.jck.com with esmtp (Exim 3.32 #1)
	id 15w5kb-000Kga-00; Tue, 23 Oct 2001 17:54:05 +0000
Date: Tue, 23 Oct 2001 09:21:58 -0400
From: John C Klensin <klensin@jck.com>
To: David Hopwood <david.hopwood@zetnet.co.uk>
cc: idn@ops.ietf.org
Subject: Currency symbols (was: Re: [idn] NFC vs NFKC)
Message-ID: <4520023.1003828918@localhost>
In-Reply-To: <3BD5197B.1C280C5D@zetnet.co.uk>
References:  <3BD5197B.1C280C5D@zetnet.co.uk>
X-Mailer: Mulberry/2.1.1 (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

David,

I found your note thought-provoking in several respects, although
I don't think along quite the dimensions you intended.  As many
people in the WG know, I'm extremely nervous about permitting
_any_ non-numeric symbol in domain names, where "non-numeric
symbol" can be crudely defined as something that does not
normally appear in the text of sentences (or the equivalent) of
in any language.  I'm especially concerned about symbols that
belong either to the typographical "dingbat" collection or those
that can be (are designed to be?) used to draw pictures.

Whether to have such a prohibition or not is ultimately a policy
problem, not a technical one --symbols pose no special technical
problems as long as we don't try to map similar looking ones--
but we had best figure out how to get an answer or at least some
opinions from people or groups with different perspectives.

But, in the context of those concerns, you wrote, as part of a
technical discussion of mappings, utility, and appropriatenes of
various Unicode characters:

>   (It's not clear why the Rupee sign should have a compatibility
>   mapping to "Rs", when the same doesn't apply to other currency
>   symbols - e.g. the Pesata sign does not have a compatibility
>   mapping to "Pts". In any case, that doesn't really matter,
>   since currency symbols are not useful in domain names.)

"Not useful", it seems to me, is somewhat in the eye of the
beholder.   For example, the term "Micro$oft" appears fairly
often in satirical (or sometimes just snide) articles, email, and
so forth.  I assume that, in the same spirit, if the dollar sign
character were available, there would be many applicants for
micro$oft.com as a domain name, and a fairly frightening
controversy as to whether it constituted legitimate satire (i.e.,
"free speech") or a trademark infringement.  I would assume that
there are similar potential puns and other amusing substitutions
of currency symbols in other languages or mixtures of them.

Again, this has nothing to do with your compatibility mapping
argument with which, from my very limited knowledge, I'm inclined
to agree, but with the "usefulness" of the currency symbols
themselves.

    john




From owner-idn@ops.ietf.org  Tue Oct 23 14:10:23 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14340
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 14:10:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w5kb-000E3a-00
	for idn-data@psg.com; Tue, 23 Oct 2001 10:54:05 -0700
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w5ka-000E3U-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 10:54:04 -0700
Received: from ns.jck.com ([209.187.148.211] helo=wave-94.research.att.com)
	by bs.jck.com with esmtp (Exim 3.32 #1)
	id 15w5kZ-000Kga-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 17:54:04 +0000
Date: Tue, 23 Oct 2001 08:59:23 -0400
From: John C Klensin <klensin@jck.com>
To: idn@ops.ietf.org
Subject: [idn] An ignorant question about TC<-> SC
Message-ID: <3165078.1003827563@localhost>
X-Mailer: Mulberry/2.1.1 (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

While reading David's NFC versus NFKC note, I had an odd thought.
I've been dissatisfied, as have many others, with the notion that
TC <-> SC mapping is analogous to case mapping in Roman-derived
alphabets.   Arguments about whether that analogy applies have
helped to make the discussion of what is, to me, a very difficult
topic even more obscure.

To quote the Unicode standard, "Serbo-Croatian is a single
language with paired alphabets".  This is a definition with which
native speakers of the language agree (although, when tensions in
the Balkans are high, I assume some of them are not completely
happy about it).  Would it be constructive to think about Chinese
as "one language, two alphabets"?  If it is, then nameprep or a
related process ought to be able to map back and forth between
the Roman-based characters usually used in Croatian contexts and
the Cyrillic characters usually used in Serbian ones (people do
this all the time, and certainly expect the two to match).

Of course, the analogy is not exact (these things never are):
perhaps partially because there are just fewer characters to deal
with, there are no cases in which there are potential ambiguities
in the mappings.  On the other hand, one problem is more severe
than in the Chinese case: in the general case, a Serbo-Croatian
string written in Cyrillic cannot be distinguished, on a
character string basis, from uses of Cyrillic for other languages
(e.g., Russian), which should not be mapped and, similarly, a
string written in Roman-based characters cannot be distinguished,
on a character string basis, from the Roman-based characters of
another language (English?) which, again, cannot be mapped.

In either case, the mapping becomes readily plausible if the
language, in addition to the content of the character string, is
known, but is hard to think about without causing side-effects in
other languages if not.

Is that helpful?
     john




From owner-idn@ops.ietf.org  Tue Oct 23 14:10:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14376
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 14:10:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w5jJ-000E24-00
	for idn-data@psg.com; Tue, 23 Oct 2001 10:52:45 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w5jI-000E1y-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 10:52:45 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id CAA04480;
	Wed, 24 Oct 2001 02:52:22 +0900
Message-ID: <03a801c15beb$977f0250$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "liana Ye" <liana.ydisg@juno.com>
Cc: <mark@macchiato.com>, <Erik.Nordmark@eng.sun.com>, <brunner@nic-naa.net>,
        <idn@ops.ietf.org>
References: <20011023.103535.-133319.0.liana.ydisg@juno.com>
Subject: Re: [idn] Which lanuages/scripts to reorder?
Date: Wed, 24 Oct 2001 02:53:15 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA14376


----- Original Message ----- 
From: "liana Ye" <liana.ydisg@juno.com>
To: <lsb@postel.co.kr>
Cc: <mark@macchiato.com>; <Erik.Nordmark@eng.sun.com>; <brunner@nic-naa.net>; <idn@ops.ietf.org>
Sent: Wednesday, October 24, 2001 2:35 AM
Subject: Re: [idn] Which lanuages/scripts to reorder?


> Soobok,
>    I think the versioning in nameprep/stringprep can handle one 
> type of change - addition to Unicode table .  To add another change 
> such as recodering a Unicode code table, the complexity 
> increases and it is dangerous to ask for.

It is hidden in ACE, not reveal to outer world. 
no complexity to childrens and elders.. but only for implementors.. :-)
the complexity of reordereing is exaggerated. look into the minimal reodering requirement
deescribed in my I-D.

> 
>  In addition, the reordering envolves individual code blocks of 
> treatment, which is based on frequency of usage.  It is good 
> for individual input, it is good for applications of particular user
> group, for example a steel industry, a transportation industry or 
> even news reporters, but it is not good when we're trying to find 
> a common denominator to cross various scripts.  If you believe
> there is a common denominating use of the frequency based
> treatment, that should be a topic in Unicode group when forming 
> such a table and providing guide in using these tables, such 
> as advice like "no TC/SC in nameprep" (as IDN is the group
> in making that decision).
> 

You missed  that frequency tables are always sub-optimal 
even with UTC's research.
Elders and chiledrens and teachers and programmers have different
set of frequent everyday vocabularies.
Who can decide the weights for their words usages to get word statistics?

Some good working registrations samples serve best for our reordering need.

your concerns are not wrong but not relevant to validity of reordering.

Soobok Lee

> Liana
> 
> On Wed, 24 Oct 2001 00:35:08 +0900 "Soobok Lee" <lsb@postel.co.kr>
> writes:
> > 
> > ----- Original Message ----- 
> > From: "Mark Davis" <mark@macchiato.com>
> >  > Introducing explicit version numbers (and it could not be limited 
> > to 2)
> > > would not help -- it would just make things worse.
> > > 
> > 
> > Mark, 
> > You may missed my point.
> > two prefix uq-- and zq-- does *not*  limit  the versioning into 2 
> > times, but infinite times.
> > 
> > zq-- is for valid ACE labels  for the all version of nameprep and
> > uq-- is for invalid ACE labels including at least one unassigned 
> > code points for all versions of 
> > nameprep.
> > 
> > This differentiating ace prefixing scheme works  in all version of 
> > nameprep from 1 to infinity.
> > 
> > newly supported script in nameprep/ACE version 5 will be
> > encoded using  uq--????  with old nameprep/ACE version 4  and below.
> > But with namepre/ACE version 5 or above, it will be encoded zq--???? 
> > .
> > 
> > Likewise,
> > labels contain newly supported script in nameprep/ACE version 6 will 
> > be
> > encoded using  uq--????  with old nameprep/ACE version 5 and below.
> > But with namepre/ACE version 6 or above, it will be encoded zq--???? 
> > .
> > 
> > And so on.
> > 
> > There is no need for version numbered prefix  for each of version 
> > 2,3,4,5,6, .....
> > 
> > Current nameprep does not encode unassigned code points into ACE for
> > "saved strings", but my two prefix scheme allow it with "uq--" 
> > prefix  which
> > provide with  rooms for incorporating  some useful fallback 
> > mechanims.
> > Even with dealing with ACE foor lookup "query", it provide some 
> > clues
> > about the version of nameprep which encode the ACE lables by the
> > distintion of "uq--" and "zq--".
> > I am proposing new nameprep behavior for unassigned code points for 
> > "saved string" and "query" through out  nameprep versioning path. 
> > Not about  versioning nameprep itself!
> > 
> > Soobok Lee
> > 
> > 
> > > Mark
> > > ?”———â€?
> > > 
> > > ??? μοι ?οá¿???á¿? καá½?κινá¿??ὴÎ?γῆÎ?
> > ??Ἀρχιμήδη?
> > > [http://www.macchiato.com]
> > > 
> > > ----- Original Message -----
> > > From: "Soobok Lee" <lsb@postel.co.kr>
> > > To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> > > Cc: "Eric Brunner-Williams in Portland Maine" 
> > <brunner@nic-naa.net>;
> > > <idn@ops.ietf.org>
> > > Sent: Tuesday, October 23, 2001 05:34
> > > Subject: Re: [idn] Which lanuages/scripts to reorder?
> > > 
> > > 
> > > 
> > > ----- Original Message -----
> > > From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> > > To: "Soobok Lee" <lsb@postel.co.kr>
> > > Cc: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>; "Eric 
> > Brunner-Williams in
> > > Portland Maine" <brunner@nic-naa.net>; <idn@ops.ietf.org>
> > > Sent: Tuesday, October 23, 2001 7:25 PM
> > > Subject: Re: [idn] Which lanuages/scripts to reorder?
> > > 
> > > 
> > > >
> > > > > seamless upgrade idea for adding new script reordering tables 
> > and new
> > > > > nameprep rules (NF/casemappings) are described in the posting 
> > titled
> > > with
> > > > > "suggestion : two prefices ....". No newer prefix other than 
> > (zq-- and
> > > uq--)
> > > > > will be needed forever. I recommend you to comment on the 
> > suggestion
> > > first
> > > > > before you go further.
> > > >
> > > > Soobok,
> > > >
> > > > We seem to have a failure to communicate.
> > > > I've placed one new concern on the table which does not have 
> > anything to
> > > > do with how you could technically upgrade to new reordering 
> > tables.
> > > >
> > > > My concern is about that the process of definition reordering 
> > tables
> > > > might never terminate (or might take a decade or so) since there 
> > might
> > > very
> > > > well be a request to add more and more languages/scripts to the 
> > tables
> > > before
> > > > we ever get to produce a single RFC.
> > > >
> > > 
> > > Erik,
> > > 
> > > new reordering tables can be added only when there comes new 
> > nameprep
> > > revision for newly added scripts, because reordering tables is 
> > proposed as
> > > one candidate of nameprep/ACE components. that is, reordering 
> > tables are
> > > bound by the versioning of nameprep.
> > > 
> > > nameprep (as one profile of stringprep) upgrade paths also never 
> > terminate
> > > because there will be more and more scripts pending for approval 
> > over time.
> > > 
> > > If you look into nameprep/stringprep document, each version of 
> > nameprep
> > > should specify  the used unicode version and the list of 
> > unassigned code
> > > points in
> > > in that version. If new versions of unicode accumulate enough set 
> > of new
> > > scripts for justifying major nameprep revision, then IETF IDN WG 
> > should work
> > > again to give birth to new nameprep profile with new list (maybe 
> > reduced by
> > > the amount of new assigned code points) of unassgined code points 
> > and new
> > > version number of unicode.
> > > 
> > > Therefore, your concerns about long path of reordering revisioning 
> > is NOT
> > > new problem,but rather just one of never-terminaing nameprep/ACE 
> > revisioning
> > > problem.
> > > 
> > > if we finalize IDN  before TAGALOG is assigned and added, current 
> > nameprep's
> > > architecture for unassigned code points, does not allow us to 
> > register
> > > tagalog domains   until new nameprep version come out by IETF 
> > activities in
> > > the undefined time in the future.
> > > 
> > > My two prefix(uq-- and zq--) scheme proposal tries to solve this 
> > inherenet
> > > problem of user inconveniences in treatment of unassigned code 
> > points,  even
> > > before distributions of new version of nameprep which often take 
> > *too much
> > > time* to serve the TAGALOG users' need.
> > > 
> > > 
> > > 
> > > Soobok Lee
> > > 
> > > > I do not have anything to add to the techical issue of how 
> > upgrade
> > > > to new reordering tables as that was not the issue over which
> > > > I expressed concern. Thus it makes no sense to me to comment on 
> > that
> > > issue.
> > > >
> > > >
> > > > Sincerely,
> > > >   Erik
> > > >
> > > >
> > > >
> > > 
> > > 
> > > 
> > > 
> > 
> > 
> 




From owner-idn@ops.ietf.org  Tue Oct 23 14:39:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15505
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 14:39:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w6Ha-000EsP-00
	for idn-data@psg.com; Tue, 23 Oct 2001 11:28:10 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w6HZ-000EsJ-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 11:28:09 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id DAA15464;
	Wed, 24 Oct 2001 03:27:48 +0900
Message-ID: <03dc01c15bf0$8a5ace10$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Mark Davis" <mark@macchiato.com>,
        "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        <idn@ops.ietf.org>
References: <Roam.SIMC.2.0.6.1003832725.4114.nordmark@bebop.france> <028701c15bbf$1b4396a0$ec1bd9d2@temp> <00a001c15bd3$5448aa80$0c680b41@c1340594a> <032f01c15bd8$4bf75b10$ec1bd9d2@temp> <013901c15be5$87fabf00$0c680b41@c1340594a>
Subject: Re: [idn] Which lanuages/scripts to reorder? 
Date: Wed, 24 Oct 2001 03:28:41 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA15505


----- Original Message ----- 
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>; "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>; <idn@ops.ietf.org>
Sent: Wednesday, October 24, 2001 2:09 AM
Subject: Re: [idn] Which lanuages/scripts to reorder? 


> That may work. However, I believe that it implies some limitiations on
> reordering to preserve compatibility across versions.
> 
> Example: Suppose that at some time in the future there are 4 versions: A, B,
> C, D.
> 
> I send you zq--XXX. It contains a character UA that is unassigned in A (but
> not B), a character UB that is unassigned in B (but not C), and a character
> UC that is unassigned in C (but not D). With normal nameprep this doesn't
> matter. You should use version D of nameprep to read the IDN. If you use a
> back-rev'd version, you will simply recognize that it has an unassigned
> character, and reject the name.
> 
> Now suppose that we have reordering, and you are back-rev'ed, and support C
> but not D. When you get UC, you have to be able to recognize that it is an
> unassigned character to know to reject it. That means that within any
> version (I think after the first), isUnassigned(x) if and only if
> isUnassigned(reordered(x)). Thus any future changes in reordering have to
> preserve the "unassigned" status: so the future reorderings have to be, in
> some sense, "in place".

No problem.

REORDERING  is defined  on  single contiguous block of  assigned characters
within a script block for one version of nameprep.

If  a part of contiguous block of  UNassigned characters of a script block was
 changed into  ASSIGNED in the new nameprep, REORDERING for new nameprep
might contain the REORDERING defined on the changed block part.

REORDERING can be  defined NOT across script blocks, nor,  across
unassigned sub-block and assignedsub-block in a script block at any time.
Since assigned and unassigned code points , in most cases, would not much orrelations
between their character usages, that is very natural consequence,too.

Soobok Lee

> 
> Mark
> —————
> 
> Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
> [http://www.macchiato.com]
> 
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: "Mark Davis" <mark@macchiato.com>; "Erik Nordmark"
> <Erik.Nordmark@eng.sun.com>
> Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
> <idn@ops.ietf.org>
> Sent: Tuesday, October 23, 2001 08:35
> Subject: Re: [idn] Which lanuages/scripts to reorder?
> 
> 
> 
> ----- Original Message -----
> From: "Mark Davis" <mark@macchiato.com>
>  > Introducing explicit version numbers (and it could not be limited to 2)
> > would not help -- it would just make things worse.
> >
> 
> Mark,
> You may missed my point.
> two prefix uq-- and zq-- does *not*  limit  the versioning into 2 times, but
> infinite times.
> 
> zq-- is for valid ACE labels  for the all version of nameprep and
> uq-- is for invalid ACE labels including at least one unassigned code points
> for all versions of
> nameprep.
> 
> This differentiating ace prefixing scheme works  in all version of nameprep
> from 1 to infinity.
> 
> newly supported script in nameprep/ACE version 5 will be
> encoded using  uq--????  with old nameprep/ACE version 4  and below.
> But with namepre/ACE version 5 or above, it will be encoded zq--???? .
> 
> Likewise,
> labels contain newly supported script in nameprep/ACE version 6 will be
> encoded using  uq--????  with old nameprep/ACE version 5 and below.
> But with namepre/ACE version 6 or above, it will be encoded zq--???? .
> 
> And so on.
> 
> There is no need for version numbered prefix  for each of version 2,3,4,5,6,
> .....
> 
> Current nameprep does not encode unassigned code points into ACE for
> "saved strings", but my two prefix scheme allow it with "uq--" prefix  which
> provide with  rooms for incorporating  some useful fallback mechanims.
> Even with dealing with ACE foor lookup "query", it provide some clues
> about the version of nameprep which encode the ACE lables by the
> distintion of "uq--" and "zq--".
> I am proposing new nameprep behavior for unassigned code points for
> "saved string" and "query" through out  nameprep versioning path.
> Not about  versioning nameprep itself!
> 
> Soobok Lee
> 
> 
> > Mark
> > —————
> >
> > Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
> > [http://www.macchiato.com]
> >
> > ----- Original Message -----
> > From: "Soobok Lee" <lsb@postel.co.kr>
> > To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> > Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
> > <idn@ops.ietf.org>
> > Sent: Tuesday, October 23, 2001 05:34
> > Subject: Re: [idn] Which lanuages/scripts to reorder?
> >
> >
> >
> > ----- Original Message -----
> > From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> > To: "Soobok Lee" <lsb@postel.co.kr>
> > Cc: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>; "Eric Brunner-Williams in
> > Portland Maine" <brunner@nic-naa.net>; <idn@ops.ietf.org>
> > Sent: Tuesday, October 23, 2001 7:25 PM
> > Subject: Re: [idn] Which lanuages/scripts to reorder?
> >
> >
> > >
> > > > seamless upgrade idea for adding new script reordering tables and new
> > > > nameprep rules (NF/casemappings) are described in the posting titled
> > with
> > > > "suggestion : two prefices ....". No newer prefix other than (zq-- and
> > uq--)
> > > > will be needed forever. I recommend you to comment on the suggestion
> > first
> > > > before you go further.
> > >
> > > Soobok,
> > >
> > > We seem to have a failure to communicate.
> > > I've placed one new concern on the table which does not have anything to
> > > do with how you could technically upgrade to new reordering tables.
> > >
> > > My concern is about that the process of definition reordering tables
> > > might never terminate (or might take a decade or so) since there might
> > very
> > > well be a request to add more and more languages/scripts to the tables
> > before
> > > we ever get to produce a single RFC.
> > >
> >
> > Erik,
> >
> > new reordering tables can be added only when there comes new nameprep
> > revision for newly added scripts, because reordering tables is proposed as
> > one candidate of nameprep/ACE components. that is, reordering tables are
> > bound by the versioning of nameprep.
> >
> > nameprep (as one profile of stringprep) upgrade paths also never terminate
> > because there will be more and more scripts pending for approval over
> time.
> >
> > If you look into nameprep/stringprep document, each version of nameprep
> > should specify  the used unicode version and the list of unassigned code
> > points in
> > in that version. If new versions of unicode accumulate enough set of new
> > scripts for justifying major nameprep revision, then IETF IDN WG should
> work
> > again to give birth to new nameprep profile with new list (maybe reduced
> by
> > the amount of new assigned code points) of unassgined code points and new
> > version number of unicode.
> >
> > Therefore, your concerns about long path of reordering revisioning is NOT
> > new problem,but rather just one of never-terminaing nameprep/ACE
> revisioning
> > problem.
> >
> > if we finalize IDN  before TAGALOG is assigned and added, current
> nameprep's
> > architecture for unassigned code points, does not allow us to register
> > tagalog domains   until new nameprep version come out by IETF activities
> in
> > the undefined time in the future.
> >
> > My two prefix(uq-- and zq--) scheme proposal tries to solve this inherenet
> > problem of user inconveniences in treatment of unassigned code points,
> even
> > before distributions of new version of nameprep which often take *too much
> > time* to serve the TAGALOG users' need.
> >
> >
> >
> > Soobok Lee
> >
> > > I do not have anything to add to the techical issue of how upgrade
> > > to new reordering tables as that was not the issue over which
> > > I expressed concern. Thus it makes no sense to me to comment on that
> > issue.
> > >
> > >
> > > Sincerely,
> > >   Erik
> > >
> > >
> > >
> >
> >
> >
> >
> 
> 
> 
> 
> 




From owner-idn@ops.ietf.org  Tue Oct 23 15:30:27 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17239
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 15:30:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w73T-000GdG-00
	for idn-data@psg.com; Tue, 23 Oct 2001 12:17:39 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w73S-000Gd6-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 12:17:38 -0700
Received: from [165.227.249.20] (165-227-249-20.client.dsl.net [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f9NJHR823637;
	Tue, 23 Oct 2001 12:17:27 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0510031fb7fb71e8a8fa@[165.227.249.20]>
In-Reply-To: <200110231717.f9NHH0N33043@nic-naa.net>
References: <200110231717.f9NHH0N33043@nic-naa.net>
Date: Tue, 23 Oct 2001 12:16:04 -0700
To: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>,
        jseng@pobox.org.sg
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] (bias) summary of reordering discussion
Cc: idn@ops.ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 1:17 PM -0400 10/23/01, Eric Brunner-Williams in Portland Maine wrote:
>Count me as for the reordering, some work remains to be done, a proposal may
>be made before the Salt Lake cut-off, and I believe it is necessary for IDN.

Could you say why you believe it is necessary? Which cases for 
reasonable name parts would be prohibited without reordering? Or are 
you agreeing that shortening some of the opaque ASCII strings by 20% 
will be useful to users for hand entry? Or something else that hasn't 
been brought forward yet?

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Tue Oct 23 16:14:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18693
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 16:14:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w7ky-000Hqc-00
	for idn-data@psg.com; Tue, 23 Oct 2001 13:02:36 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w7kx-000HqH-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 13:02:35 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VVYdJKQDoICdjUO1k/n2q/Xg==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GJF9BP6X; Tue, 23 Oct 2001 15:58:09 EDT
To: lsb@postel.co.kr
Cc: idn@ops.ietf.org
Date: Tue, 23 Oct 2001 11:51:03 -0700
Subject: Re: [idn] Which lanuages/scripts to reorder?
Message-ID: <20011023.130225.-133319.1.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.5
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana Ye <liana.ydisg@juno.com>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



> 
> > Soobok,
> >    I think the versioning in nameprep/stringprep can handle one 
> > type of change - addition to Unicode table .  To add another 
> change 
> > such as recodering a Unicode code table, the complexity 
> > increases and it is dangerous to ask for.
> 
> It is hidden in ACE, not reveal to outer world. 
> no complexity to childrens and elders.. but only for implementors.. 
> :-)
> the complexity of reordereing is exaggerated. look into the minimal 
> reodering requirement
> deescribed in my I-D.
> 

But you do change the order of codepoints in UCS, and others 
are depending on the order to do other things too.  That is my 
point, not how much is done to it in one procedure or it is hitten
or not. 

Liana

> > 
> >  In addition, the reordering envolves individual code blocks of 
> > treatment, which is based on frequency of usage.  It is good 
> > for individual input, it is good for applications of particular 
> user
> > group, for example a steel industry, a transportation industry or 
> > even news reporters, but it is not good when we're trying to find 
> > a common denominator to cross various scripts.  If you believe
> > there is a common denominating use of the frequency based
> > treatment, that should be a topic in Unicode group when forming 
> > such a table and providing guide in using these tables, such 
> > as advice like "no TC/SC in nameprep" (as IDN is the group
> > in making that decision).
> > 
> 
> You missed  that frequency tables are always sub-optimal 
> even with UTC's research.
> Elders and chiledrens and teachers and programmers have different
> set of frequent everyday vocabularies.
> Who can decide the weights for their words usages to get word 
> statistics?
> 
> Some good working registrations samples serve best for our 
> reordering need.
> 
> your concerns are not wrong but not relevant to validity of 
> reordering.
> 
> Soobok Lee
> 
> > Liana
> > 
> > On Wed, 24 Oct 2001 00:35:08 +0900 "Soobok Lee" <lsb@postel.co.kr>
> > writes:
> > > 
> > > ----- Original Message ----- 
> > > From: "Mark Davis" <mark@macchiato.com>
> > >  > Introducing explicit version numbers (and it could not be 
> limited 
> > > to 2)
> > > > would not help -- it would just make things worse.
> > > > 
> > > 
> > > Mark, 
> > > You may missed my point.
> > > two prefix uq-- and zq-- does *not*  limit  the versioning into 
> 2 
> > > times, but infinite times.
> > > 
> > > zq-- is for valid ACE labels  for the all version of nameprep 
> and
> > > uq-- is for invalid ACE labels including at least one unassigned 
> 
> > > code points for all versions of 
> > > nameprep.
> > > 
> > > This differentiating ace prefixing scheme works  in all version 
> of 
> > > nameprep from 1 to infinity.
> > > 
> > > newly supported script in nameprep/ACE version 5 will be
> > > encoded using  uq--????  with old nameprep/ACE version 4  and 
> below.
> > > But with namepre/ACE version 5 or above, it will be encoded 
> zq--???? 
> > > .
> > > 
> > > Likewise,
> > > labels contain newly supported script in nameprep/ACE version 6 
> will 
> > > be
> > > encoded using  uq--????  with old nameprep/ACE version 5 and 
> below.
> > > But with namepre/ACE version 6 or above, it will be encoded 
> zq--???? 
> > > .
> > > 
> > > And so on.
> > > 
> > > There is no need for version numbered prefix  for each of 
> version 
> > > 2,3,4,5,6, .....
> > > 
> > > Current nameprep does not encode unassigned code points into ACE 
> for
> > > "saved strings", but my two prefix scheme allow it with "uq--" 
> > > prefix  which
> > > provide with  rooms for incorporating  some useful fallback 
> > > mechanims.
> > > Even with dealing with ACE foor lookup "query", it provide some 
> > > clues
> > > about the version of nameprep which encode the ACE lables by the
> > > distintion of "uq--" and "zq--".
> > > I am proposing new nameprep behavior for unassigned code points 
> for 
> > > "saved string" and "query" through out  nameprep versioning 
> path. 
> > > Not about  versioning nameprep itself!
> > > 
> > > Soobok Lee
> > > 
> > > 
> > > > Mark
> > > > ?”———â€?
> > > > 
> > > > ??? μοι ?οá¿???á¿? καá½?κινá¿??ὴÎ?γῆÎ?
> > > ??Ἀρχιμήδη?
> > > > [http://www.macchiato.com]
> > > > 
> > > > ----- Original Message -----
> > > > From: "Soobok Lee" <lsb@postel.co.kr>
> > > > To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> > > > Cc: "Eric Brunner-Williams in Portland Maine" 
> > > <brunner@nic-naa.net>;
> > > > <idn@ops.ietf.org>
> > > > Sent: Tuesday, October 23, 2001 05:34
> > > > Subject: Re: [idn] Which lanuages/scripts to reorder?
> > > > 
> > > > 
> > > > 
> > > > ----- Original Message -----
> > > > From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> > > > To: "Soobok Lee" <lsb@postel.co.kr>
> > > > Cc: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>; "Eric 
> > > Brunner-Williams in
> > > > Portland Maine" <brunner@nic-naa.net>; <idn@ops.ietf.org>
> > > > Sent: Tuesday, October 23, 2001 7:25 PM
> > > > Subject: Re: [idn] Which lanuages/scripts to reorder?
> > > > 
> > > > 
> > > > >
> > > > > > seamless upgrade idea for adding new script reordering 
> tables 
> > > and new
> > > > > > nameprep rules (NF/casemappings) are described in the 
> posting 
> > > titled
> > > > with
> > > > > > "suggestion : two prefices ....". No newer prefix other 
> than 
> > > (zq-- and
> > > > uq--)
> > > > > > will be needed forever. I recommend you to comment on the 
> > > suggestion
> > > > first
> > > > > > before you go further.
> > > > >
> > > > > Soobok,
> > > > >
> > > > > We seem to have a failure to communicate.
> > > > > I've placed one new concern on the table which does not have 
> 
> > > anything to
> > > > > do with how you could technically upgrade to new reordering 
> > > tables.
> > > > >
> > > > > My concern is about that the process of definition 
> reordering 
> > > tables
> > > > > might never terminate (or might take a decade or so) since 
> there 
> > > might
> > > > very
> > > > > well be a request to add more and more languages/scripts to 
> the 
> > > tables
> > > > before
> > > > > we ever get to produce a single RFC.
> > > > >
> > > > 
> > > > Erik,
> > > > 
> > > > new reordering tables can be added only when there comes new 
> > > nameprep
> > > > revision for newly added scripts, because reordering tables is 
> 
> > > proposed as
> > > > one candidate of nameprep/ACE components. that is, reordering 
> > > tables are
> > > > bound by the versioning of nameprep.
> > > > 
> > > > nameprep (as one profile of stringprep) upgrade paths also 
> never 
> > > terminate
> > > > because there will be more and more scripts pending for 
> approval 
> > > over time.
> > > > 
> > > > If you look into nameprep/stringprep document, each version of 
> 
> > > nameprep
> > > > should specify  the used unicode version and the list of 
> > > unassigned code
> > > > points in
> > > > in that version. If new versions of unicode accumulate enough 
> set 
> > > of new
> > > > scripts for justifying major nameprep revision, then IETF IDN 
> WG 
> > > should work
> > > > again to give birth to new nameprep profile with new list 
> (maybe 
> > > reduced by
> > > > the amount of new assigned code points) of unassgined code 
> points 
> > > and new
> > > > version number of unicode.
> > > > 
> > > > Therefore, your concerns about long path of reordering 
> revisioning 
> > > is NOT
> > > > new problem,but rather just one of never-terminaing 
> nameprep/ACE 
> > > revisioning
> > > > problem.
> > > > 
> > > > if we finalize IDN  before TAGALOG is assigned and added, 
> current 
> > > nameprep's
> > > > architecture for unassigned code points, does not allow us to 
> > > register
> > > > tagalog domains   until new nameprep version come out by IETF 
> > > activities in
> > > > the undefined time in the future.
> > > > 
> > > > My two prefix(uq-- and zq--) scheme proposal tries to solve 
> this 
> > > inherenet
> > > > problem of user inconveniences in treatment of unassigned code 
> 
> > > points,  even
> > > > before distributions of new version of nameprep which often 
> take 
> > > *too much
> > > > time* to serve the TAGALOG users' need.
> > > > 
> > > > 
> > > > 
> > > > Soobok Lee
> > > > 
> > > > > I do not have anything to add to the techical issue of how 
> > > upgrade
> > > > > to new reordering tables as that was not the issue over 
> which
> > > > > I expressed concern. Thus it makes no sense to me to comment 
> on 
> > > that
> > > > issue.
> > > > >
> > > > >
> > > > > Sincerely,
> > > > >   Erik
> > > > >
> > > > >
> > > > >
> > > > 
> > > > 
> > > > 
> > > > 
> > > 
> > > 
> > 
> 



From owner-idn@ops.ietf.org  Tue Oct 23 16:15:25 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18715
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 16:15:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15w7kq-000HqQ-00
	for idn-data@psg.com; Tue, 23 Oct 2001 13:02:28 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15w7kp-000HqH-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 13:02:27 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VVYdJKQDoICdh7lcJH701q7Q==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GJF9BP7X; Tue, 23 Oct 2001 15:58:09 EDT
To: klensin@jck.com
Cc: idn@ops.ietf.org
Date: Tue, 23 Oct 2001 13:02:23 -0700
Subject: Re: [idn] An ignorant question about TC<-> SC
Message-ID: <20011023.130225.-133319.2.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.5
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-38,40-79
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana Ye <liana.ydisg@juno.com>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


 From screen display point view, TC/SC are different glyph 
 sets(who defines the sets? How is it used by 1/5 of the world 
population? Is Uicode group the only authoritive one? In 
China there are over 600 recorded views on this).

 From linguistic on phoneme analysis,  TC/SC are identical by 
all authoritive dictionaries and standards with exceptions 
listed (for dialective and historical use).

 From a higher level anaysis, the semantics are the same by 
all authoritive dictionaries and standards with exceptions listed
and historically differenciated (in different dictionaries) and 
frequence of usage in current sectors (by software implementors). 

If for Latin only with 26 letters and 10 numbers, there are upper
i and lower L looks alike, 'I' and 'l', and 'O' '0' looks alike, then 
for 4,000 to 20,000 symbols the ratio is 4:36, a 1/9 not one-one
mapping case.  This is a much higher ratio than standard TC/SC 
mapping.  So yes, all language symbols share the same types 
of characteristics but with defferent magnitude. 

To treat UCS code points on the same base, the 4,000 to 20,000
number needs to be doubled, and treat TC/SC in a general way 
is a test for correctly treat 8,000 to 56,000 symbols for the long run. 
Since the 2,000 has pair-mapping( for sloppy discussion), but not 
all one-to-one (for another 17), the others are not have case 
mapping on another 2000, so do Indian languages.  The 4000 are 
high frequency symbols, similarly for Kanji and Hanja. These
symbols have highest chance to collide in IDN names, and critical 
to map them in registration and IDN usage. 

With the 2000 pair-mapping taken care of as case mapping, the 
above 4000 increases to 6,000, a great drop in processing 
complexity.  If the other symbols follow the same equivalent 
mapping, then the number getting better and manageable. 

Liana

On Tue, 23 Oct 2001 08:59:23 -0400 John C Klensin <klensin@jck.com>
writes:
> While reading David's NFC versus NFKC note, I had an odd thought.
> I've been dissatisfied, as have many others, with the notion that
> TC <-> SC mapping is analogous to case mapping in Roman-derived
> alphabets.   Arguments about whether that analogy applies have
> helped to make the discussion of what is, to me, a very difficult
> topic even more obscure.
> 
> To quote the Unicode standard, "Serbo-Croatian is a single
> language with paired alphabets".  This is a definition with which
> native speakers of the language agree (although, when tensions in
> the Balkans are high, I assume some of them are not completely
> happy about it).  Would it be constructive to think about Chinese
> as "one language, two alphabets"?  If it is, then nameprep or a
> related process ought to be able to map back and forth between
> the Roman-based characters usually used in Croatian contexts and
> the Cyrillic characters usually used in Serbian ones (people do
> this all the time, and certainly expect the two to match).
> 
> Of course, the analogy is not exact (these things never are):
> perhaps partially because there are just fewer characters to deal
> with, there are no cases in which there are potential ambiguities
> in the mappings.  On the other hand, one problem is more severe
> than in the Chinese case: in the general case, a Serbo-Croatian
> string written in Cyrillic cannot be distinguished, on a
> character string basis, from uses of Cyrillic for other languages
> (e.g., Russian), which should not be mapped and, similarly, a
> string written in Roman-based characters cannot be distinguished,
> on a character string basis, from the Roman-based characters of
> another language (English?) which, again, cannot be mapped.
> 
> In either case, the mapping becomes readily plausible if the
> language, in addition to the content of the character string, is
> known, but is hard to think about without causing side-effects in
> other languages if not.
> 
> Is that helpful?
>      john
> 
> 



From owner-idn@ops.ietf.org  Tue Oct 23 20:07:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23204
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 20:07:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wBIC-000Q0n-00
	for idn-data@psg.com; Tue, 23 Oct 2001 16:49:08 -0700
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wBIA-000Q0c-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 16:49:06 -0700
Received: from zetnet.co.uk (man-s326.dialup.zetnet.co.uk [194.247.45.197])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f9NNmqS07678;
	Wed, 24 Oct 2001 00:48:52 +0100
Message-ID: <3BD5FFAC.4E066695@zetnet.co.uk>
Date: Wed, 24 Oct 2001 00:39:24 +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: James Seng/Personal <jseng@pobox.org.sg>, idn@ops.ietf.org
Subject: Re: [idn] (bias) summary of reordering discussion
References: <011701c15be0$4473db90$dd00a8c0@jamessonyvaio>
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-----

James Seng/Personal wrote:
> Of the people participate in the reordering discussion
> 
[snip]
> David Hopwood - (no conclusion from comments)

Make that an explicit objection - I think it's far too complicated to
justify the marginal benefits. Also, any changes or additions to
reordering would have disastrous consequences for name comparison, and
Soobok Lee's zq--/uq-- proposal does not fix this.

- -- 
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

iQEVAwUBO9Xd1TkCAxeYt5gVAQH3Zwf+LohUgxC4xfXulqSzQbzBGb/GYkHkE7di
rGpy7qcujsmoW9PPIcGkCppUvyQatxmGSkV9v4STyR1+sD1ea8XMXQy+I8hY7F4r
6oKYA6UMzXTwhIaZ3HPe0nAWjmbF59w/1WjGPFP2GJuu0Ol5+ZwF686DCDOoPNc+
upkF05YuXFUwS7L99RR+0w1CGkOmdoj3Cl577sXJ36WMNj760yG5Gd29KjfT3ucl
8Yk6KjaynT0ppDcX1ZIay5e0BAGmHbrlcaGmRYTXodWMvoNhP4JHuJvW6dfMrY1t
4qJJcTfFsj1qSV3fDZRbCqczIY0gYYxzsCyJbILmGHNndi26cE4wyw==
=FF+E
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Tue Oct 23 21:43:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25868
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 21:43:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wCs3-0003vQ-00
	for idn-data@psg.com; Tue, 23 Oct 2001 18:30:15 -0700
Received: from smtp23.singnet.com.sg ([165.21.101.203])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wCs1-0003vK-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 18:30:14 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp23.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9O1WYx11604;
	Wed, 24 Oct 2001 09:32:34 +0800
Message-ID: <011e01c15c2b$6a0de850$1401000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <klensin@jck.com>, "liana Ye" <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>
References: <20011023.130225.-133319.2.liana.ydisg@juno.com>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Wed, 24 Oct 2001 09:30:07 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>  From linguistic on phoneme analysis,  TC/SC are identical by
> all authoritive dictionaries and standards with exceptions
> listed (for dialective and historical use).

It should be "TC/SC Phrase" to be more exact.

There is also a problem with "identical by all authoritive
dictionaries". All dictionaries have (slight/some) differences in what
they considered identical. The devil is in the level of details.

> To treat UCS code points on the same base, the 4,000 to 20,000
> number needs to be doubled, and treat TC/SC in a general way
> is a test for correctly treat 8,000 to 56,000 symbols for the long
run.

There are 70,000+ han ideograph in ISO10646:2001.

-James Seng




From owner-idn@ops.ietf.org  Tue Oct 23 21:50:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26061
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 21:50:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wCwf-00041J-00
	for idn-data@psg.com; Tue, 23 Oct 2001 18:35:01 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wCwd-000417-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 18:35:00 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id KAA17508;
	Wed, 24 Oct 2001 10:34:44 +0900
Message-ID: <001701c15c2c$30323e00$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "liana Ye" <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>
References: <20011023.130225.-133319.1.liana.ydisg@juno.com>
Subject: Re: [idn] Which lanuages/scripts to reorder?
Date: Wed, 24 Oct 2001 10:35:39 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA26061


----- Original Message ----- 
From: "liana Ye" <liana.ydisg@juno.com>
To: <lsb@postel.co.kr>
Cc: <idn@ops.ietf.org>
Sent: Wednesday, October 24, 2001 3:51 AM
Subject: Re: [idn] Which lanuages/scripts to reorder?


> 
> 
> > 
> > > Soobok,
> > >    I think the versioning in nameprep/stringprep can handle one 
> > > type of change - addition to Unicode table .  To add another 
> > change 
> > > such as recodering a Unicode code table, the complexity 
> > > increases and it is dangerous to ask for.
> > 
> > It is hidden in ACE, not reveal to outer world. 
> > no complexity to childrens and elders.. but only for implementors.. 
> > :-)
> > the complexity of reordereing is exaggerated. look into the minimal 
> > reodering requirement
> > deescribed in my I-D.
> > 
> 
> But you do change the order of codepoints in UCS, and others 
> are depending on the order to do other things too. 

Never. reordering is done and reversed in ACE. so a kinf of huge lists of 
tuning parameters.
A kind of atomic operatoin. that does hinder any other UCS mappings.

Soobok Lee


> That is my 
> point, not how much is done to it in one procedure or it is hitten
> or not. 
> 
> Liana
> 
> > > 
> > >  In addition, the reordering envolves individual code blocks of 
> > > treatment, which is based on frequency of usage.  It is good 
> > > for individual input, it is good for applications of particular 
> > user
> > > group, for example a steel industry, a transportation industry or 
> > > even news reporters, but it is not good when we're trying to find 
> > > a common denominator to cross various scripts.  If you believe
> > > there is a common denominating use of the frequency based
> > > treatment, that should be a topic in Unicode group when forming 
> > > such a table and providing guide in using these tables, such 
> > > as advice like "no TC/SC in nameprep" (as IDN is the group
> > > in making that decision).
> > > 
> > 
> > You missed  that frequency tables are always sub-optimal 
> > even with UTC's research.
> > Elders and chiledrens and teachers and programmers have different
> > set of frequent everyday vocabularies.
> > Who can decide the weights for their words usages to get word 
> > statistics?
> > 
> > Some good working registrations samples serve best for our 
> > reordering need.
> > 
> > your concerns are not wrong but not relevant to validity of 
> > reordering.
> > 
> > Soobok Lee
> > 
> > > Liana
> > > 
> > > On Wed, 24 Oct 2001 00:35:08 +0900 "Soobok Lee" <lsb@postel.co.kr>
> > > writes:
> > > > 
> > > > ----- Original Message ----- 
> > > > From: "Mark Davis" <mark@macchiato.com>
> > > >  > Introducing explicit version numbers (and it could not be 
> > limited 
> > > > to 2)
> > > > > would not help -- it would just make things worse.
> > > > > 
> > > > 
> > > > Mark, 
> > > > You may missed my point.
> > > > two prefix uq-- and zq-- does *not*  limit  the versioning into 
> > 2 
> > > > times, but infinite times.
> > > > 
> > > > zq-- is for valid ACE labels  for the all version of nameprep 
> > and
> > > > uq-- is for invalid ACE labels including at least one unassigned 
> > 
> > > > code points for all versions of 
> > > > nameprep.
> > > > 
> > > > This differentiating ace prefixing scheme works  in all version 
> > of 
> > > > nameprep from 1 to infinity.
> > > > 
> > > > newly supported script in nameprep/ACE version 5 will be
> > > > encoded using  uq--????  with old nameprep/ACE version 4  and 
> > below.
> > > > But with namepre/ACE version 5 or above, it will be encoded 
> > zq--???? 
> > > > .
> > > > 
> > > > Likewise,
> > > > labels contain newly supported script in nameprep/ACE version 6 
> > will 
> > > > be
> > > > encoded using  uq--????  with old nameprep/ACE version 5 and 
> > below.
> > > > But with namepre/ACE version 6 or above, it will be encoded 
> > zq--???? 
> > > > .
> > > > 
> > > > And so on.
> > > > 
> > > > There is no need for version numbered prefix  for each of 
> > version 
> > > > 2,3,4,5,6, .....
> > > > 
> > > > Current nameprep does not encode unassigned code points into ACE 
> > for
> > > > "saved strings", but my two prefix scheme allow it with "uq--" 
> > > > prefix  which
> > > > provide with  rooms for incorporating  some useful fallback 
> > > > mechanims.
> > > > Even with dealing with ACE foor lookup "query", it provide some 
> > > > clues
> > > > about the version of nameprep which encode the ACE lables by the
> > > > distintion of "uq--" and "zq--".
> > > > I am proposing new nameprep behavior for unassigned code points 
> > for 
> > > > "saved string" and "query" through out  nameprep versioning 
> > path. 
> > > > Not about  versioning nameprep itself!
> > > > 
> > > > Soobok Lee
> > > > 
> > > > 
> > > > > Mark
> > > > > ?”———â€?
> > > > > 
> > > > > ??? μοι ?οá¿???á¿? καá½?κινá¿??ὴÎ?γῆÎ?
> > > > ??Ἀρχιμήδη?
> > > > > [http://www.macchiato.com]
> > > > > 
> > > > > ----- Original Message -----
> > > > > From: "Soobok Lee" <lsb@postel.co.kr>
> > > > > To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> > > > > Cc: "Eric Brunner-Williams in Portland Maine" 
> > > > <brunner@nic-naa.net>;
> > > > > <idn@ops.ietf.org>
> > > > > Sent: Tuesday, October 23, 2001 05:34
> > > > > Subject: Re: [idn] Which lanuages/scripts to reorder?
> > > > > 
> > > > > 
> > > > > 
> > > > > ----- Original Message -----
> > > > > From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> > > > > To: "Soobok Lee" <lsb@postel.co.kr>
> > > > > Cc: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>; "Eric 
> > > > Brunner-Williams in
> > > > > Portland Maine" <brunner@nic-naa.net>; <idn@ops.ietf.org>
> > > > > Sent: Tuesday, October 23, 2001 7:25 PM
> > > > > Subject: Re: [idn] Which lanuages/scripts to reorder?
> > > > > 
> > > > > 
> > > > > >
> > > > > > > seamless upgrade idea for adding new script reordering 
> > tables 
> > > > and new
> > > > > > > nameprep rules (NF/casemappings) are described in the 
> > posting 
> > > > titled
> > > > > with
> > > > > > > "suggestion : two prefices ....". No newer prefix other 
> > than 
> > > > (zq-- and
> > > > > uq--)
> > > > > > > will be needed forever. I recommend you to comment on the 
> > > > suggestion
> > > > > first
> > > > > > > before you go further.
> > > > > >
> > > > > > Soobok,
> > > > > >
> > > > > > We seem to have a failure to communicate.
> > > > > > I've placed one new concern on the table which does not have 
> > 
> > > > anything to
> > > > > > do with how you could technically upgrade to new reordering 
> > > > tables.
> > > > > >
> > > > > > My concern is about that the process of definition 
> > reordering 
> > > > tables
> > > > > > might never terminate (or might take a decade or so) since 
> > there 
> > > > might
> > > > > very
> > > > > > well be a request to add more and more languages/scripts to 
> > the 
> > > > tables
> > > > > before
> > > > > > we ever get to produce a single RFC.
> > > > > >
> > > > > 
> > > > > Erik,
> > > > > 
> > > > > new reordering tables can be added only when there comes new 
> > > > nameprep
> > > > > revision for newly added scripts, because reordering tables is 
> > 
> > > > proposed as
> > > > > one candidate of nameprep/ACE components. that is, reordering 
> > > > tables are
> > > > > bound by the versioning of nameprep.
> > > > > 
> > > > > nameprep (as one profile of stringprep) upgrade paths also 
> > never 
> > > > terminate
> > > > > because there will be more and more scripts pending for 
> > approval 
> > > > over time.
> > > > > 
> > > > > If you look into nameprep/stringprep document, each version of 
> > 
> > > > nameprep
> > > > > should specify  the used unicode version and the list of 
> > > > unassigned code
> > > > > points in
> > > > > in that version. If new versions of unicode accumulate enough 
> > set 
> > > > of new
> > > > > scripts for justifying major nameprep revision, then IETF IDN 
> > WG 
> > > > should work
> > > > > again to give birth to new nameprep profile with new list 
> > (maybe 
> > > > reduced by
> > > > > the amount of new assigned code points) of unassgined code 
> > points 
> > > > and new
> > > > > version number of unicode.
> > > > > 
> > > > > Therefore, your concerns about long path of reordering 
> > revisioning 
> > > > is NOT
> > > > > new problem,but rather just one of never-terminaing 
> > nameprep/ACE 
> > > > revisioning
> > > > > problem.
> > > > > 
> > > > > if we finalize IDN  before TAGALOG is assigned and added, 
> > current 
> > > > nameprep's
> > > > > architecture for unassigned code points, does not allow us to 
> > > > register
> > > > > tagalog domains   until new nameprep version come out by IETF 
> > > > activities in
> > > > > the undefined time in the future.
> > > > > 
> > > > > My two prefix(uq-- and zq--) scheme proposal tries to solve 
> > this 
> > > > inherenet
> > > > > problem of user inconveniences in treatment of unassigned code 
> > 
> > > > points,  even
> > > > > before distributions of new version of nameprep which often 
> > take 
> > > > *too much
> > > > > time* to serve the TAGALOG users' need.
> > > > > 
> > > > > 
> > > > > 
> > > > > Soobok Lee
> > > > > 
> > > > > > I do not have anything to add to the techical issue of how 
> > > > upgrade
> > > > > > to new reordering tables as that was not the issue over 
> > which
> > > > > > I expressed concern. Thus it makes no sense to me to comment 
> > on 
> > > > that
> > > > > issue.
> > > > > >
> > > > > >
> > > > > > Sincerely,
> > > > > >   Erik
> > > > > >
> > > > > >
> > > > > >
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > 
> > > > 
> > > 
> > 
> 




From owner-idn@ops.ietf.org  Tue Oct 23 21:54:38 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26153
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 21:54:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wD5v-0004J8-00
	for idn-data@psg.com; Tue, 23 Oct 2001 18:44:35 -0700
Received: from smtp22.singnet.com.sg ([165.21.101.202])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wD5t-0004Iw-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 18:44:34 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp22.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9O1lui04947;
	Wed, 24 Oct 2001 09:47:56 +0800
Message-ID: <014f01c15c2d$66f37700$1401000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
References: <011701c15be0$4473db90$dd00a8c0@jamessonyvaio> <038f01c15be7$62eb3800$ec1bd9d2@temp>
Subject: Re: [idn] (bias) summary of reordering discussion
Date: Wed, 24 Oct 2001 09:44:21 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>   the 20% is just the mean average. 40% improvement is not rare for

The mean is 20% from your data. The result I got using my data is around
12%, which I send you. Either way, I accept it improves efficiency
somewhat.

> > 2. Compression efficient in future since statistic - Lee's counter
that
> > compression "always SHORTER labels than usual". Mathematically, it
can
> > be proven this is wrong (very basic pigeon hole principle).
> >
>   ALready answered. You may have missed that.
>    0.3% hangul labels get longer by 1 character, while 99.6% labels
got shorter
>     by greater amounts. the net gain is always positive for each
length N.

Using *existing* data. I am talking about data in future if/when we
reach saturation. (No, never say we never going to run out. That is what
we say of IPv4).

> > 3. Referencing from established I18N organisation - ISO14651 is deem
> > inappropriate and I agree with it. No alternative was proposed.
>
>   sub-optimal tuning parameters not revealed to outside of ACE. they
need authorities ?  i think it need not.

Yes, I feel strong enough that we should.

>  Already answered. read my recent articles.
>  new reordering support of new script in Tandem with newer nameprep
for
>  the new script. no new prefix needed if there will be no change
>  in existing stable reordering tables.

Okay. Then who and how you going to define these new reordering table?
What is the process? Do we publish new version of reordering RFC? Or do
we do this as an IANA action (if so, where is the IANA consideration).

Does this explain why I really like to see an authoritive source who
would ensure continouity in the work?

>  You have misunderstanding of my proposal.

If you stop changing your proposal in every email, I think I have a
better chance to keep up to date with it.

>  Statistical Frequency is always sub-optimal tuning parameters. better
than not.
>  What's your position on engineering tuning paramters in various
>  protocols ?, eg. Ethernet packet length, ttl, flag length in tcp/udp
etc....

My position? What have protocol tuning have to do with code point
tuning?

IETF is a well-known wire-protocol expert group. We exist original to do
so.
But are we code point expert?

-James Seng




From owner-idn@ops.ietf.org  Tue Oct 23 22:13:44 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26461
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 22:13:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wDN6-0005A2-00
	for idn-data@psg.com; Tue, 23 Oct 2001 19:02:20 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wDN5-00059s-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 19:02:19 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id LAA26177;
	Wed, 24 Oct 2001 11:02:09 +0900
Message-ID: <006501c15c30$0527bb00$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>, "liana Ye" <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>
References: <20011023.130225.-133319.1.liana.ydisg@juno.com> <001701c15c2c$30323e00$ec1bd9d2@temp>
Subject: Re: [idn] Which lanuages/scripts to reorder?
Date: Wed, 24 Oct 2001 11:03:05 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id WAA26461


----- Original Message ----- 
From: "Soobok Lee" <lsb@postel.co.kr>
To: "liana Ye" <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>
Sent: Wednesday, October 24, 2001 10:35 AM
Subject: Re: [idn] Which lanuages/scripts to reorder?


> 
> ----- Original Message ----- 
> From: "liana Ye" <liana.ydisg@juno.com>
> To: <lsb@postel.co.kr>
> Cc: <idn@ops.ietf.org>
> Sent: Wednesday, October 24, 2001 3:51 AM
> Subject: Re: [idn] Which lanuages/scripts to reorder?
> 
> 
> > 
> > 
> > > 
> > > > Soobok,
> > > >    I think the versioning in nameprep/stringprep can handle one 
> > > > type of change - addition to Unicode table .  To add another 
> > > change 
> > > > such as recodering a Unicode code table, the complexity 
> > > > increases and it is dangerous to ask for.
> > > 
> > > It is hidden in ACE, not reveal to outer world. 
> > > no complexity to childrens and elders.. but only for implementors.. 
> > > :-)
> > > the complexity of reordereing is exaggerated. look into the minimal 
> > > reodering requirement
> > > deescribed in my I-D.
> > > 
> > 
> > But you do change the order of codepoints in UCS, and others 
> > are depending on the order to do other things too. 
> 
> Never. reordering is done and reversed in ACE. so a kinf of huge lists of 
> tuning parameters.
> A kind of atomic operatoin. that does hinder any other UCS mappings.

Oops.. that does NOT hinder any other mappings.
Sorry.

> 
> Soobok Lee
> 
> 
> > That is my 
> > point, not how much is done to it in one procedure or it is hitten
> > or not. 
> > 
> > Liana
> > 
> > > > 
> > > >  In addition, the reordering envolves individual code blocks of 
> > > > treatment, which is based on frequency of usage.  It is good 
> > > > for individual input, it is good for applications of particular 
> > > user
> > > > group, for example a steel industry, a transportation industry or 
> > > > even news reporters, but it is not good when we're trying to find 
> > > > a common denominator to cross various scripts.  If you believe
> > > > there is a common denominating use of the frequency based
> > > > treatment, that should be a topic in Unicode group when forming 
> > > > such a table and providing guide in using these tables, such 
> > > > as advice like "no TC/SC in nameprep" (as IDN is the group
> > > > in making that decision).
> > > > 
> > > 
> > > You missed  that frequency tables are always sub-optimal 
> > > even with UTC's research.
> > > Elders and chiledrens and teachers and programmers have different
> > > set of frequent everyday vocabularies.
> > > Who can decide the weights for their words usages to get word 
> > > statistics?
> > > 
> > > Some good working registrations samples serve best for our 
> > > reordering need.
> > > 
> > > your concerns are not wrong but not relevant to validity of 
> > > reordering.
> > > 
> > > Soobok Lee
> > > 
> > > > Liana
> > > > 
> > > > On Wed, 24 Oct 2001 00:35:08 +0900 "Soobok Lee" <lsb@postel.co.kr>
> > > > writes:
> > > > > 
> > > > > ----- Original Message ----- 
> > > > > From: "Mark Davis" <mark@macchiato.com>
> > > > >  > Introducing explicit version numbers (and it could not be 
> > > limited 
> > > > > to 2)
> > > > > > would not help -- it would just make things worse.
> > > > > > 
> > > > > 
> > > > > Mark, 
> > > > > You may missed my point.
> > > > > two prefix uq-- and zq-- does *not*  limit  the versioning into 
> > > 2 
> > > > > times, but infinite times.
> > > > > 
> > > > > zq-- is for valid ACE labels  for the all version of nameprep 
> > > and
> > > > > uq-- is for invalid ACE labels including at least one unassigned 
> > > 
> > > > > code points for all versions of 
> > > > > nameprep.
> > > > > 
> > > > > This differentiating ace prefixing scheme works  in all version 
> > > of 
> > > > > nameprep from 1 to infinity.
> > > > > 
> > > > > newly supported script in nameprep/ACE version 5 will be
> > > > > encoded using  uq--????  with old nameprep/ACE version 4  and 
> > > below.
> > > > > But with namepre/ACE version 5 or above, it will be encoded 
> > > zq--???? 
> > > > > .
> > > > > 
> > > > > Likewise,
> > > > > labels contain newly supported script in nameprep/ACE version 6 
> > > will 
> > > > > be
> > > > > encoded using  uq--????  with old nameprep/ACE version 5 and 
> > > below.
> > > > > But with namepre/ACE version 6 or above, it will be encoded 
> > > zq--???? 
> > > > > .
> > > > > 
> > > > > And so on.
> > > > > 
> > > > > There is no need for version numbered prefix  for each of 
> > > version 
> > > > > 2,3,4,5,6, .....
> > > > > 
> > > > > Current nameprep does not encode unassigned code points into ACE 
> > > for
> > > > > "saved strings", but my two prefix scheme allow it with "uq--" 
> > > > > prefix  which
> > > > > provide with  rooms for incorporating  some useful fallback 
> > > > > mechanims.
> > > > > Even with dealing with ACE foor lookup "query", it provide some 
> > > > > clues
> > > > > about the version of nameprep which encode the ACE lables by the
> > > > > distintion of "uq--" and "zq--".
> > > > > I am proposing new nameprep behavior for unassigned code points 
> > > for 
> > > > > "saved string" and "query" through out  nameprep versioning 
> > > path. 
> > > > > Not about  versioning nameprep itself!
> > > > > 
> > > > > Soobok Lee
> > > > > 
> > > > > 
> > > > > > Mark
> > > > > > ?”———â€?
> > > > > > 
> > > > > > ??? μοι ?οá¿???á¿? καá½?κινá¿??ὴÎ?γῆÎ?
> > > > > ??Ἀρχιμήδη?
> > > > > > [http://www.macchiato.com]
> > > > > > 
> > > > > > ----- Original Message -----
> > > > > > From: "Soobok Lee" <lsb@postel.co.kr>
> > > > > > To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> > > > > > Cc: "Eric Brunner-Williams in Portland Maine" 
> > > > > <brunner@nic-naa.net>;
> > > > > > <idn@ops.ietf.org>
> > > > > > Sent: Tuesday, October 23, 2001 05:34
> > > > > > Subject: Re: [idn] Which lanuages/scripts to reorder?
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > ----- Original Message -----
> > > > > > From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> > > > > > To: "Soobok Lee" <lsb@postel.co.kr>
> > > > > > Cc: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>; "Eric 
> > > > > Brunner-Williams in
> > > > > > Portland Maine" <brunner@nic-naa.net>; <idn@ops.ietf.org>
> > > > > > Sent: Tuesday, October 23, 2001 7:25 PM
> > > > > > Subject: Re: [idn] Which lanuages/scripts to reorder?
> > > > > > 
> > > > > > 
> > > > > > >
> > > > > > > > seamless upgrade idea for adding new script reordering 
> > > tables 
> > > > > and new
> > > > > > > > nameprep rules (NF/casemappings) are described in the 
> > > posting 
> > > > > titled
> > > > > > with
> > > > > > > > "suggestion : two prefices ....". No newer prefix other 
> > > than 
> > > > > (zq-- and
> > > > > > uq--)
> > > > > > > > will be needed forever. I recommend you to comment on the 
> > > > > suggestion
> > > > > > first
> > > > > > > > before you go further.
> > > > > > >
> > > > > > > Soobok,
> > > > > > >
> > > > > > > We seem to have a failure to communicate.
> > > > > > > I've placed one new concern on the table which does not have 
> > > 
> > > > > anything to
> > > > > > > do with how you could technically upgrade to new reordering 
> > > > > tables.
> > > > > > >
> > > > > > > My concern is about that the process of definition 
> > > reordering 
> > > > > tables
> > > > > > > might never terminate (or might take a decade or so) since 
> > > there 
> > > > > might
> > > > > > very
> > > > > > > well be a request to add more and more languages/scripts to 
> > > the 
> > > > > tables
> > > > > > before
> > > > > > > we ever get to produce a single RFC.
> > > > > > >
> > > > > > 
> > > > > > Erik,
> > > > > > 
> > > > > > new reordering tables can be added only when there comes new 
> > > > > nameprep
> > > > > > revision for newly added scripts, because reordering tables is 
> > > 
> > > > > proposed as
> > > > > > one candidate of nameprep/ACE components. that is, reordering 
> > > > > tables are
> > > > > > bound by the versioning of nameprep.
> > > > > > 
> > > > > > nameprep (as one profile of stringprep) upgrade paths also 
> > > never 
> > > > > terminate
> > > > > > because there will be more and more scripts pending for 
> > > approval 
> > > > > over time.
> > > > > > 
> > > > > > If you look into nameprep/stringprep document, each version of 
> > > 
> > > > > nameprep
> > > > > > should specify  the used unicode version and the list of 
> > > > > unassigned code
> > > > > > points in
> > > > > > in that version. If new versions of unicode accumulate enough 
> > > set 
> > > > > of new
> > > > > > scripts for justifying major nameprep revision, then IETF IDN 
> > > WG 
> > > > > should work
> > > > > > again to give birth to new nameprep profile with new list 
> > > (maybe 
> > > > > reduced by
> > > > > > the amount of new assigned code points) of unassgined code 
> > > points 
> > > > > and new
> > > > > > version number of unicode.
> > > > > > 
> > > > > > Therefore, your concerns about long path of reordering 
> > > revisioning 
> > > > > is NOT
> > > > > > new problem,but rather just one of never-terminaing 
> > > nameprep/ACE 
> > > > > revisioning
> > > > > > problem.
> > > > > > 
> > > > > > if we finalize IDN  before TAGALOG is assigned and added, 
> > > current 
> > > > > nameprep's
> > > > > > architecture for unassigned code points, does not allow us to 
> > > > > register
> > > > > > tagalog domains   until new nameprep version come out by IETF 
> > > > > activities in
> > > > > > the undefined time in the future.
> > > > > > 
> > > > > > My two prefix(uq-- and zq--) scheme proposal tries to solve 
> > > this 
> > > > > inherenet
> > > > > > problem of user inconveniences in treatment of unassigned code 
> > > 
> > > > > points,  even
> > > > > > before distributions of new version of nameprep which often 
> > > take 
> > > > > *too much
> > > > > > time* to serve the TAGALOG users' need.
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > Soobok Lee
> > > > > > 
> > > > > > > I do not have anything to add to the techical issue of how 
> > > > > upgrade
> > > > > > > to new reordering tables as that was not the issue over 
> > > which
> > > > > > > I expressed concern. Thus it makes no sense to me to comment 
> > > on 
> > > > > that
> > > > > > issue.
> > > > > > >
> > > > > > >
> > > > > > > Sincerely,
> > > > > > >   Erik
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > 
> > > > > 
> > > > 
> > > 
> > 
> 
> 




From owner-idn@ops.ietf.org  Tue Oct 23 22:44:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28199
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 22:44:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wDnu-0006Lx-00
	for idn-data@psg.com; Tue, 23 Oct 2001 19:30:02 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wDnt-0006La-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 19:30:02 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id LAA02481;
	Wed, 24 Oct 2001 11:29:46 +0900
Message-ID: <00a001c15c33$e0dd94f0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>,
        "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
References: <011701c15be0$4473db90$dd00a8c0@jamessonyvaio> <3BD5FFAC.4E066695@zetnet.co.uk>
Subject: Re: [idn] (bias) summary of reordering discussion
Date: Wed, 24 Oct 2001 11:30:42 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id WAA28199


----- Original Message ----- 
From: "David Hopwood" <david.hopwood@zetnet.co.uk>
 > 
> Make that an explicit objection - I think it's far too complicated to
> justify the marginal benefits. Also, any changes or additions to
> reordering would have disastrous consequences for name comparison, and
> Soobok Lee's zq--/uq-- proposal does not fix this.

I expect you clarify this assertions with detailed examples soon. 

Soobok Lee 




From owner-idn@ops.ietf.org  Tue Oct 23 23:11:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28695
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 23:11:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wEGO-0007JI-00
	for idn-data@psg.com; Tue, 23 Oct 2001 19:59:28 -0700
Received: from smtp22.singnet.com.sg ([165.21.101.202])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wEGN-0007JC-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 19:59:27 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp22.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9O332i08772
	for <idn@ops.ietf.org>; Wed, 24 Oct 2001 11:03:02 +0800
Message-ID: <030701c15c37$e463d8b0$1401000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <idn@ops.ietf.org>
Subject: [idn] Update Charter revision 2
Date: Wed, 24 Oct 2001 10:59:26 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Comments please.

-James Seng

--- CUT HERE ---
Description of Working Group:

The goal of the group is to specify the requirements for
internationalized access to domain names and to specify a standards
track protocol based on the requirements.

Domain names and host names are forms of identifier. Language
information is not encoded in these identifiers; that is, "names" from
different languages are defined in a single namespace.

The scope of the group is to investigate the possible means of doing
this and what methods are feasible given the technical impact they will
have on the use of such names by humans as well as application programs,
as well as the impact on other users and administrators of the domain
name system.

A fundamental requirement in this work is to not disturb the current use
and operation of the domain name system, and for the DNS to continue to
allow any system anywhere to resolve any domain name.

The WG work may modify the DNS protocol and other related work
undertaken by the DNSEXT WG. But such changes must be co-ordinated with
the DNSEXT WG.

The WG will reference work from ISO/IEC, the Unicode Consortium as much
as possible. The consideration are the policy and principle adopted by
the I18N group on the stability of published codepoints and future
addition
of codepoints. The discussion of new codepoints, codepoints properties
and
mappings between codepoints are out-of-scope for the working group and
should be done in other relevant expert group.

The group will not address the question of what, if any, body should
administer or control usage of names that use this functionality.

The group must identify consequences to the current deployed DNS
infrastructure, the protocols and the applications as well as transition
scenarios, where applicable.

The WG will actively ensure good communication with interested groups
who are studying the problem of internationalized access to domain
names.

The Action Item(s) for the Working Group are

1. An Informational RFC specifying the requirements for providing
   Internationalized access to domain names. The document should
   provide guidance for development solutions to this problem,
   taking localized (e.g. writing order) and related operational
   issues into consideration.

2. A standard track specification on access to internationalized
   domain names including specifying any transition issues.

3. A standard track specification on an ASCII Compatible Encoding
   (ACE). This may or may not be used in the standard track
   specification on access to internationalized domain names.

4. A standard track specification on normalization of identifiers
   for the purpuse of comparisons. This document may includes case
   folding, map outs, and prohibited characters.

Goal & Milestone:

Nov 2001    Nameprep RFC wg last call
Dec 2001    Nameprep RFC send to IESG for advancement
Nov 2001    First draft of architecture draft specifying the
            relationship between input methods, namepreps and zonefile
Dec 2001    Protocol RFC wg last call
Dec 2001    Second draft of architecture draft
Jan 2002    Protocol RFC send to IESG for advancement
Feb 2002    Architecture draft last call
Mar 2002    Architecture draft send to IESG for advancement





From owner-idn@ops.ietf.org  Tue Oct 23 23:43:35 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29629
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 23:43:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wEm1-0008m7-00
	for idn-data@psg.com; Tue, 23 Oct 2001 20:32:09 -0700
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wEm0-0008lt-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 20:32:09 -0700
Received: from zetnet.co.uk (man-s350.dialup.zetnet.co.uk [194.247.45.221])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f9O3VZS29129;
	Wed, 24 Oct 2001 04:31:35 +0100
Message-ID: <3BD633E3.A6A7BE2F@zetnet.co.uk>
Date: Wed, 24 Oct 2001 04:22:11 +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] (bias) summary of reordering discussion
References: <011701c15be0$4473db90$dd00a8c0@jamessonyvaio> <3BD5FFAC.4E066695@zetnet.co.uk> <00a001c15c33$e0dd94f0$ec1bd9d2@temp>
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:
> From: "David Hopwood" <david.hopwood@zetnet.co.uk>
> >
> > Make that an explicit objection - I think it's far too complicated to
> > justify the marginal benefits. Also, any changes or additions to
> > reordering would have disastrous consequences for name comparison, and
> > Soobok Lee's zq--/uq-- proposal does not fix this.
> 
> I expect you clarify this assertions with detailed examples soon.

The problem is this: how does an application that doesn't support the
latest version check whether a zq-- label is equivalent to a uq-- label?

For nameprep without reordering, an old application can perform matching
that will be correct provided that the inputs are nameprepped (i.e.
case folded NFC or NFKC), and this is sufficient for most purposes. In
your proposal, OTOH, it must just give up, because it has no information
about how characters are reordered in uq-- labels. I consider this to be
a fatal flaw in the proposal.

This flaw would not arise if reordering only applied to characters that
are assigned now (i.e. in Unicode 3.1), and new scripts were never
reordered. In that case the zq--/uq-- versioning wouldn't be needed.
However, I still don't think that reordering is worthwhile even in that
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

iQEVAwUBO9YzrzkCAxeYt5gVAQHtVAgAmjLhWyYvhTnBRHoIcN55JoTY+cTc6JlB
+kv6kYJ6x2CHJd4iG/3OyIY5J7ix4tqWbn9Zynhk0F4hleCZT+Yn1l7BRSNAnq7i
TERrhaj2L+0Aw6cI/S1/OCL9TVEBDKA70eSXQH8nzCejG1Zjy3N5dheKwNTpbCyV
UxpJ3g6CRsFzV1O7z3pItIS2M7DSDeKQzTYa3rJo42bepYv75oTmDfDEvHKLvcRD
o5qaEnYWOhrWkdvyPPGiG6eW5D7by4kWxyYsnsKJ4ZpThYqRyB70YnWcuBT+/7J1
k93JBDsgOg8iqCoXVVAxvhFB6IjN4knwIdkuBWCSmudQUleHYiJ4yg==
=bt61
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Tue Oct 23 23:45:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29732
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 23:45:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wEog-0008re-00
	for idn-data@psg.com; Tue, 23 Oct 2001 20:34:54 -0700
Received: from imo-d01.mx.aol.com ([205.188.157.33])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wEof-0008rV-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 20:34:53 -0700
Received: from DougEwell2@cs.com
	by imo-d01.mx.aol.com (mail_out_v31_r1.8.) id i.11b.649894e (4389);
	Tue, 23 Oct 2001 23:34:44 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <11b.649894e.290790d4@cs.com>
Date: Tue, 23 Oct 2001 23:34:44 EDT
Subject: Re: [idn] Update Charter revision 2
To: idn@ops.ietf.org
CC: jseng@pobox.org.sg
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a message dated 2001-10-23 20:13:49 Pacific Daylight Time, 
jseng@pobox.org.sg writes:

>  Comments please.
>  ...
>  The discussion of new codepoints, codepoints properties and
>  mappings between codepoints are out-of-scope for the working group and
>  should be done in other relevant expert group.

Basically this means that the entire reordering discussion and TC<->SC 
discussion are out of scope.

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Tue Oct 23 23:47:44 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29783
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 23:47:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wEtl-00098K-00
	for idn-data@psg.com; Tue, 23 Oct 2001 20:40:09 -0700
Received: from imo-m10.mx.aol.com ([64.12.136.165])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wEtk-00098E-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 20:40:08 -0700
Received: from DougEwell2@cs.com
	by imo-m10.mx.aol.com (mail_out_v31_r1.8.) id i.d1.e5aa6fc (4389);
	Tue, 23 Oct 2001 23:40:02 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <d1.e5aa6fc.29079212@cs.com>
Date: Tue, 23 Oct 2001 23:40:02 EDT
Subject: Re: [idn] Which lanuages/scripts to reorder? 
To: idn@ops.ietf.org
CC: lsb@postel.co.kr
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a message dated 2001-10-23 9:13:14 Pacific Daylight Time, lsb@postel.co.kr 
writes:

>  But, Even without reordering,
>  some tagalog people will come and say  why ACE-Z  favors latin  with 
special
>  literal mode supports.
>  Do you think this timebomb invalidates ACE-Z literal mode ?  No.

ACE-Z "favors" Latin with special literal mode supports because Latin is the 
only darned script the existing DNS supports, and it will probably continue 
to be the single most common script in which domain names are encoded in the 
future.  Deliberately handicapping Latin in an attempt to prove "fairness" to 
other scripts would be just petty.  Sheesh.

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Tue Oct 23 23:49:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29823
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 23:49:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wEsO-00093w-00
	for idn-data@psg.com; Tue, 23 Oct 2001 20:38:44 -0700
Received: from smtp23.singnet.com.sg ([165.21.101.203])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wEsM-00093p-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 20:38:43 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp23.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9O3f5x10725;
	Wed, 24 Oct 2001 11:41:05 +0800
Message-ID: <036301c15c3d$5e27c670$1401000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <DougEwell2@cs.com>, <idn@ops.ietf.org>
References: <11b.649894e.290790d4@cs.com>
Subject: Re: [idn] Update Charter revision 2
Date: Wed, 24 Oct 2001 11:38:37 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The discussion of these codepoints and the tables are out of scope. IETF
are not code point expert. The use of it (codepoints table if there is
one) is not.

-James Seng

----- Original Message -----
From: <DougEwell2@cs.com>
To: <idn@ops.ietf.org>
Cc: <jseng@pobox.org.sg>
Sent: Wednesday, October 24, 2001 11:34 AM
Subject: Re: [idn] Update Charter revision 2


> In a message dated 2001-10-23 20:13:49 Pacific Daylight Time,
> jseng@pobox.org.sg writes:
>
> >  Comments please.
> >  ...
> >  The discussion of new codepoints, codepoints properties and
> >  mappings between codepoints are out-of-scope for the working group
and
> >  should be done in other relevant expert group.
>
> Basically this means that the entire reordering discussion and TC<->SC
> discussion are out of scope.
>
> -Doug Ewell
>  Fullerton, California




From owner-idn@ops.ietf.org  Tue Oct 23 23:54:04 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29932
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 23:54:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wExB-0009Ka-00
	for idn-data@psg.com; Tue, 23 Oct 2001 20:43:41 -0700
Received: from imo-r01.mx.aol.com ([152.163.225.97])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wExA-0009KT-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 20:43:40 -0700
Received: from DougEwell2@cs.com
	by imo-r01.mx.aol.com (mail_out_v31_r1.8.) id i.ac.1cb74c09 (4389);
	Tue, 23 Oct 2001 23:43:30 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <ac.1cb74c09.290792e1@cs.com>
Date: Tue, 23 Oct 2001 23:43:29 EDT
Subject: Re: [idn] An ignorant question about TC<-> SC
To: idn@ops.ietf.org
CC: klensin@jck.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a message dated 2001-10-23 11:13:14 Pacific Daylight Time, klensin@jck.com 
writes:

>  On the other hand, one problem is more severe
>  than in the Chinese case: in the general case, a Serbo-Croatian
>  string written in Cyrillic cannot be distinguished, on a
>  character string basis, from uses of Cyrillic for other languages
>  (e.g., Russian), which should not be mapped and, similarly, a
>  string written in Roman-based characters cannot be distinguished,
>  on a character string basis, from the Roman-based characters of
>  another language (English?) which, again, cannot be mapped.

But this problem *does* exist in the Chinese case, because certain Han 
characters can also be used to write Japanese or (I've been told) Korean.  In 
a Japanese or Korean context, it wouldn't make any sense to map the correct 
"traditional" Han character to a simplified "equivalent"; the simplified 
character is only equivalent if the language is Chinese.  And we're not 
tagging languages, so we don't know when this mapping is appropriate and when 
it's not.

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Tue Oct 23 23:58:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29999
	for <idn-archive@lists.ietf.org>; Tue, 23 Oct 2001 23:58:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wF3K-0009cE-00
	for idn-data@psg.com; Tue, 23 Oct 2001 20:50:02 -0700
Received: from mail1.ics.ntts.co.jp ([202.32.24.45])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wF3I-0009c1-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 20:50:01 -0700
Received: from mail26.silk.ntts.co.jp by mail1.ics.ntts.co.jp (8.9.3/3.7W-NTTSOFT-SUR2.0)
	id MAA21708; Wed, 24 Oct 2001 12:49:58 +0900 (JST)
Received: from daemon.inl.ntts.co.jp by mail26.silk.ntts.co.jp (8.11.6/3.7W-silk-4.4)
	id f9O3nwe27335; Wed, 24 Oct 2001 12:49:58 +0900 (JST)
Received: (qmail 63400 invoked by alias); 24 Oct 2001 12:49:58 +0900
Received: (qmail 63384 invoked from network); 24 Oct 2001 12:49:57 +0900
Received: from daemon.inl.ntts.co.jp (HELO localhost)
  by daemon.inl.ntts.co.jp with SMTP; 24 Oct 2001 12:49:57 +0900
To: idn@ops.ietf.org
Subject: Re: [idn] Update Charter revision 2
In-Reply-To: <030701c15c37$e463d8b0$1401000a@jamessonyvaio>
References: <030701c15c37$e463d8b0$1401000a@jamessonyvaio>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20011024124949X.yone@po.ntts.co.jp>
Date: Wed, 24 Oct 2001 12:49:49 +0900 (JST)
From: Yoshiro YONEYA <yone@po.ntts.co.jp>
X-Dispatcher: imput version 20000228(IM140)
Lines: 56
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

From: "James Seng/Personal" <jseng@pobox.org.sg>
Subject: [idn] Update Charter revision 2
Date: Wed, 24 Oct 2001 10:59:26 +0800

Here are my comments.

- There is no target for 'Requirements' in milestone.  I think it
  should be.

- I think RFC target in milestone should be identical to action items.
  Is 'architecture' in milestone denoting item 2?  Is 'protocol'
  denoting item 3?  Please clarify relation between terms in milestone
  and action items.

- Nameprep is now divided into framework (stringprep) and profile
  (nameprep).  Is stringprep scope of this WG?  I think it is
  eventually yes at this moment but I'm not sure, so please clarify
  position of stringprep.

Best regards,

> The Action Item(s) for the Working Group are
> 
> 1. An Informational RFC specifying the requirements for providing
>    Internationalized access to domain names. The document should
>    provide guidance for development solutions to this problem,
>    taking localized (e.g. writing order) and related operational
>    issues into consideration.
> 
> 2. A standard track specification on access to internationalized
>    domain names including specifying any transition issues.
> 
> 3. A standard track specification on an ASCII Compatible Encoding
>    (ACE). This may or may not be used in the standard track
>    specification on access to internationalized domain names.
> 
> 4. A standard track specification on normalization of identifiers
>    for the purpuse of comparisons. This document may includes case
>    folding, map outs, and prohibited characters.
> 
> Goal & Milestone:
> 
> Nov 2001    Nameprep RFC wg last call
> Dec 2001    Nameprep RFC send to IESG for advancement
> Nov 2001    First draft of architecture draft specifying the
>             relationship between input methods, namepreps and zonefile
> Dec 2001    Protocol RFC wg last call
> Dec 2001    Second draft of architecture draft
> Jan 2002    Protocol RFC send to IESG for advancement
> Feb 2002    Architecture draft last call
> Mar 2002    Architecture draft send to IESG for advancement

-- 
Yoshiro YONEYA <yone@nic.ad.jp>



From owner-idn@ops.ietf.org  Wed Oct 24 00:21:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00285
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 00:21:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wFLH-000AIh-00
	for idn-data@psg.com; Tue, 23 Oct 2001 21:08:35 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wFLG-000AIb-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 21:08:34 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 312187F414; Wed, 24 Oct 2001 13:08:04 +0900 (JST)
Message-Id: <4.2.0.58.J.20011024123116.06271690@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 24 Oct 2001 12:32:49 +0900
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Update Charter revision 2
In-Reply-To: <030701c15c37$e463d8b0$1401000a@jamessonyvaio>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This looked good to me, except that it would seem more
natural to have the architecture doc out before the specs
nailing down the details, and that i'm not sure how
stringprep fits into this picture (it's not listed below,
but we depend on it).

Regards,   Martin.

At 10:59 01/10/24 +0800, James Seng/Personal wrote:
>Comments please.
>
>-James Seng
>
>--- CUT HERE ---
>Description of Working Group:
>
>The goal of the group is to specify the requirements for
>internationalized access to domain names and to specify a standards
>track protocol based on the requirements.
>
>Domain names and host names are forms of identifier. Language
>information is not encoded in these identifiers; that is, "names" from
>different languages are defined in a single namespace.
>
>The scope of the group is to investigate the possible means of doing
>this and what methods are feasible given the technical impact they will
>have on the use of such names by humans as well as application programs,
>as well as the impact on other users and administrators of the domain
>name system.
>
>A fundamental requirement in this work is to not disturb the current use
>and operation of the domain name system, and for the DNS to continue to
>allow any system anywhere to resolve any domain name.
>
>The WG work may modify the DNS protocol and other related work
>undertaken by the DNSEXT WG. But such changes must be co-ordinated with
>the DNSEXT WG.
>
>The WG will reference work from ISO/IEC, the Unicode Consortium as much
>as possible. The consideration are the policy and principle adopted by
>the I18N group on the stability of published codepoints and future
>addition
>of codepoints. The discussion of new codepoints, codepoints properties
>and
>mappings between codepoints are out-of-scope for the working group and
>should be done in other relevant expert group.
>
>The group will not address the question of what, if any, body should
>administer or control usage of names that use this functionality.
>
>The group must identify consequences to the current deployed DNS
>infrastructure, the protocols and the applications as well as transition
>scenarios, where applicable.
>
>The WG will actively ensure good communication with interested groups
>who are studying the problem of internationalized access to domain
>names.
>
>The Action Item(s) for the Working Group are
>
>1. An Informational RFC specifying the requirements for providing
>    Internationalized access to domain names. The document should
>    provide guidance for development solutions to this problem,
>    taking localized (e.g. writing order) and related operational
>    issues into consideration.
>
>2. A standard track specification on access to internationalized
>    domain names including specifying any transition issues.
>
>3. A standard track specification on an ASCII Compatible Encoding
>    (ACE). This may or may not be used in the standard track
>    specification on access to internationalized domain names.
>
>4. A standard track specification on normalization of identifiers
>    for the purpuse of comparisons. This document may includes case
>    folding, map outs, and prohibited characters.
>
>Goal & Milestone:
>
>Nov 2001    Nameprep RFC wg last call
>Dec 2001    Nameprep RFC send to IESG for advancement
>Nov 2001    First draft of architecture draft specifying the
>             relationship between input methods, namepreps and zonefile
>Dec 2001    Protocol RFC wg last call
>Dec 2001    Second draft of architecture draft
>Jan 2002    Protocol RFC send to IESG for advancement
>Feb 2002    Architecture draft last call
>Mar 2002    Architecture draft send to IESG for advancement
>




From owner-idn@ops.ietf.org  Wed Oct 24 00:21:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00310
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 00:21:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wFKq-000AIU-00
	for idn-data@psg.com; Tue, 23 Oct 2001 21:08:08 -0700
Received: from [203.207.0.132] (helo=mail.asiainfra.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wFKp-000AIO-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 21:08:07 -0700
Received: from gix ([203.207.0.121])
	by mail.asiainfra.com (8.9.3/8.9.3) with SMTP id MAA22870;
	Wed, 24 Oct 2001 12:08:17 +0800
From: "Kenny Huang" <huangk@alum.sinica.edu>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
Subject: RE: [idn] Update Charter revision 2
Date: Wed, 24 Oct 2001 12:12:44 +0800
Message-ID: <IHELIFNJKJLDFEMBCENDAEDPCIAA.huangk@alum.sinica.edu>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
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.4807.1700
In-Reply-To: <030701c15c37$e463d8b0$1401000a@jamessonyvaio>
Importance: Normal
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA00310

If the goal of the working group is changed, then many of our discussion will 
become useless. The original description of WG is attached.
Are we exploring an evolving goal with evolving activities ? If that is the case, then
we can discuss re-ordering or TC/SC issues right here.

Kenny Huang
---------------------------------------------------------------------

The goal of the group is to specify the requirements for internationalized access to domain names and to specify a standards track protocol based on the requirements. 

The scope of the group is to investigate the possible means of doing this and what methods are feasible given the technical impact they will have on the use of such names by humans as well as application programs, as well as the impact on other users and administrators of the domain name system. 

A fundamental requirement in this work is to not disturb the current use and operation of the domain name system, and for the DNS to continue to allow any system anywhere to resolve any domain name. 

The group will not address the question of what, if any, body should administer or control usage of names that use this functionality. 

The group must identify consequences to the current deployed DNS infrastructure, the protocols and the applications as well as transition scenarios, where applicable. 

The WG will actively ensure good communication with interested groups who are studying the problem of internationalized access to domain names. 

The Action Item(s) for the Working Group are: 

1. An Informational RFC specifying the requirements for providing Internationalized access to domain names. The document should provide guidance for development solutions to this problem, taking localized (e.g. writing order) and related operational issues into consideration. 

2. An Informational RFC or RFC's documenting the various proposals and Implementations of Internationalization (i18n) of Domain Names. The document(s) should also provide a technical evaluation of the proposals by the Working Group. 

3. A standards track specification on access to internationalized domain names including specifying any transition issues. 
---------------------------------------------------------------------

> -----Original Message-----
> From: owner-idn@ops.ietf.org [mailto:owner-idn@ops.ietf.org]On 
> Behalf Of James Seng/Personal
> Sent: Wednesday, October 24, 2001 10:59 AM
> To: idn@ops.ietf.org
> Subject: [idn] Update Charter revision 2
> 
> 
> Comments please.
> 
> -James Seng
> 
> --- CUT HERE ---
> Description of Working Group:
> 
> The goal of the group is to specify the requirements for
> internationalized access to domain names and to specify a standards
> track protocol based on the requirements.
> 
> Domain names and host names are forms of identifier. Language
> information is not encoded in these identifiers; that is, "names" from
> different languages are defined in a single namespace.
> 
> The scope of the group is to investigate the possible means of doing
> this and what methods are feasible given the technical impact they will
> have on the use of such names by humans as well as application programs,
> as well as the impact on other users and administrators of the domain
> name system.
> 
> A fundamental requirement in this work is to not disturb the current use
> and operation of the domain name system, and for the DNS to continue to
> allow any system anywhere to resolve any domain name.
> 
> The WG work may modify the DNS protocol and other related work
> undertaken by the DNSEXT WG. But such changes must be co-ordinated with
> the DNSEXT WG.
> 
> The WG will reference work from ISO/IEC, the Unicode Consortium as much
> as possible. The consideration are the policy and principle adopted by
> the I18N group on the stability of published codepoints and future
> addition
> of codepoints. The discussion of new codepoints, codepoints properties
> and
> mappings between codepoints are out-of-scope for the working group and
> should be done in other relevant expert group.
> 
> The group will not address the question of what, if any, body should
> administer or control usage of names that use this functionality.
> 
> The group must identify consequences to the current deployed DNS
> infrastructure, the protocols and the applications as well as transition
> scenarios, where applicable.
> 
> The WG will actively ensure good communication with interested groups
> who are studying the problem of internationalized access to domain
> names.
> 
> The Action Item(s) for the Working Group are
> 
> 1. An Informational RFC specifying the requirements for providing
>    Internationalized access to domain names. The document should
>    provide guidance for development solutions to this problem,
>    taking localized (e.g. writing order) and related operational
>    issues into consideration.
> 
> 2. A standard track specification on access to internationalized
>    domain names including specifying any transition issues.
> 
> 3. A standard track specification on an ASCII Compatible Encoding
>    (ACE). This may or may not be used in the standard track
>    specification on access to internationalized domain names.
> 
> 4. A standard track specification on normalization of identifiers
>    for the purpuse of comparisons. This document may includes case
>    folding, map outs, and prohibited characters.
> 
> Goal & Milestone:
> 
> Nov 2001    Nameprep RFC wg last call
> Dec 2001    Nameprep RFC send to IESG for advancement
> Nov 2001    First draft of architecture draft specifying the
>             relationship between input methods, namepreps and zonefile
> Dec 2001    Protocol RFC wg last call
> Dec 2001    Second draft of architecture draft
> Jan 2002    Protocol RFC send to IESG for advancement
> Feb 2002    Architecture draft last call
> Mar 2002    Architecture draft send to IESG for advancement
> 
> 




From owner-idn@ops.ietf.org  Wed Oct 24 00:27:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00512
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 00:27:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wFQd-000ANY-00
	for idn-data@psg.com; Tue, 23 Oct 2001 21:14:07 -0700
Received: from smtp22.singnet.com.sg ([165.21.101.202])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wFQc-000ANP-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 21:14:06 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp22.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9O4Hai14677;
	Wed, 24 Oct 2001 12:17:36 +0800
Message-ID: <03e501c15c42$4f6b8d10$1401000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Kenny Huang" <huangk@alum.sinica.edu>, <idn@ops.ietf.org>
References: <IHELIFNJKJLDFEMBCENDAEDPCIAA.huangk@alum.sinica.edu>
Subject: Re: [idn] Update Charter revision 2
Date: Wed, 24 Oct 2001 12:14:00 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I think the intention is this:

The discussion to do reordering is within scope. The table for
reordering in my view is a frequency analysis sorting and that maybe
within scope. If reordering creates any codepoints tables, then that
table is not.

The discussion of whether to do TC-SC equivalent matching, and if so,
where and how is also within scope.  The tables of TC-SC is not.


-James Seng

----- Original Message -----
From: "Kenny Huang" <huangk@alum.sinica.edu>
To: "James Seng/Personal" <jseng@pobox.org.sg>; <idn@ops.ietf.org>
Sent: Wednesday, October 24, 2001 12:12 PM
Subject: RE: [idn] Update Charter revision 2


> If the goal of the working group is changed, then many of our
discussion will
> become useless. The original description of WG is attached.
> Are we exploring an evolving goal with evolving activities ? If that
is the case, then
> we can discuss re-ordering or TC/SC issues right here.
>
> Kenny Huang
> ---------------------------------------------------------------------
>
> The goal of the group is to specify the requirements for
internationalized access to domain names and to specify a standards
track protocol based on the requirements.
>
> The scope of the group is to investigate the possible means of doing
this and what methods are feasible given the technical impact they will
have on the use of such names by humans as well as application programs,
as well as the impact on other users and administrators of the domain
name system.
>
> A fundamental requirement in this work is to not disturb the current
use and operation of the domain name system, and for the DNS to continue
to allow any system anywhere to resolve any domain name.
>
> The group will not address the question of what, if any, body should
administer or control usage of names that use this functionality.
>
> The group must identify consequences to the current deployed DNS
infrastructure, the protocols and the applications as well as transition
scenarios, where applicable.
>
> The WG will actively ensure good communication with interested groups
who are studying the problem of internationalized access to domain
names.
>
> The Action Item(s) for the Working Group are:
>
> 1. An Informational RFC specifying the requirements for providing
Internationalized access to domain names. The document should provide
guidance for development solutions to this problem, taking localized
(e.g. writing order) and related operational issues into consideration.
>
> 2. An Informational RFC or RFC's documenting the various proposals and
Implementations of Internationalization (i18n) of Domain Names. The
document(s) should also provide a technical evaluation of the proposals
by the Working Group.
>
> 3. A standards track specification on access to internationalized
domain names including specifying any transition issues.
> ---------------------------------------------------------------------
>
> > -----Original Message-----
> > From: owner-idn@ops.ietf.org [mailto:owner-idn@ops.ietf.org]On
> > Behalf Of James Seng/Personal
> > Sent: Wednesday, October 24, 2001 10:59 AM
> > To: idn@ops.ietf.org
> > Subject: [idn] Update Charter revision 2
> >
> >
> > Comments please.
> >
> > -James Seng
> >
> > --- CUT HERE ---
> > Description of Working Group:
> >
> > The goal of the group is to specify the requirements for
> > internationalized access to domain names and to specify a standards
> > track protocol based on the requirements.
> >
> > Domain names and host names are forms of identifier. Language
> > information is not encoded in these identifiers; that is, "names"
from
> > different languages are defined in a single namespace.
> >
> > The scope of the group is to investigate the possible means of doing
> > this and what methods are feasible given the technical impact they
will
> > have on the use of such names by humans as well as application
programs,
> > as well as the impact on other users and administrators of the
domain
> > name system.
> >
> > A fundamental requirement in this work is to not disturb the current
use
> > and operation of the domain name system, and for the DNS to continue
to
> > allow any system anywhere to resolve any domain name.
> >
> > The WG work may modify the DNS protocol and other related work
> > undertaken by the DNSEXT WG. But such changes must be co-ordinated
with
> > the DNSEXT WG.
> >
> > The WG will reference work from ISO/IEC, the Unicode Consortium as
much
> > as possible. The consideration are the policy and principle adopted
by
> > the I18N group on the stability of published codepoints and future
> > addition
> > of codepoints. The discussion of new codepoints, codepoints
properties
> > and
> > mappings between codepoints are out-of-scope for the working group
and
> > should be done in other relevant expert group.
> >
> > The group will not address the question of what, if any, body should
> > administer or control usage of names that use this functionality.
> >
> > The group must identify consequences to the current deployed DNS
> > infrastructure, the protocols and the applications as well as
transition
> > scenarios, where applicable.
> >
> > The WG will actively ensure good communication with interested
groups
> > who are studying the problem of internationalized access to domain
> > names.
> >
> > The Action Item(s) for the Working Group are
> >
> > 1. An Informational RFC specifying the requirements for providing
> >    Internationalized access to domain names. The document should
> >    provide guidance for development solutions to this problem,
> >    taking localized (e.g. writing order) and related operational
> >    issues into consideration.
> >
> > 2. A standard track specification on access to internationalized
> >    domain names including specifying any transition issues.
> >
> > 3. A standard track specification on an ASCII Compatible Encoding
> >    (ACE). This may or may not be used in the standard track
> >    specification on access to internationalized domain names.
> >
> > 4. A standard track specification on normalization of identifiers
> >    for the purpuse of comparisons. This document may includes case
> >    folding, map outs, and prohibited characters.
> >
> > Goal & Milestone:
> >
> > Nov 2001    Nameprep RFC wg last call
> > Dec 2001    Nameprep RFC send to IESG for advancement
> > Nov 2001    First draft of architecture draft specifying the
> >             relationship between input methods, namepreps and
zonefile
> > Dec 2001    Protocol RFC wg last call
> > Dec 2001    Second draft of architecture draft
> > Jan 2002    Protocol RFC send to IESG for advancement
> > Feb 2002    Architecture draft last call
> > Mar 2002    Architecture draft send to IESG for advancement
> >
> >
>




From owner-idn@ops.ietf.org  Wed Oct 24 00:34:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00610
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 00:34:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wFaB-000AYt-00
	for idn-data@psg.com; Tue, 23 Oct 2001 21:23:59 -0700
Received: from [211.254.82.194] (helo=nexus.spsoft.co.kr)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wFaA-000AYn-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 21:23:58 -0700
Received: (from newcat@localhost)
	by nexus.spsoft.co.kr (8.10.0/8.10.0) id f9O4NtG13830
	for idn@ops.ietf.org; Wed, 24 Oct 2001 13:23:55 +0900
Date: Wed, 24 Oct 2001 13:23:55 +0900
From: YangWoo Ko <newcat@spsoft.co.kr>
To: idn@ops.ietf.org
Subject: Re: [idn] An ignorant question about TC<-> SC
Message-ID: <20011024132355.F11881@spsoft.co.kr>
References: <ac.1cb74c09.290792e1@cs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <ac.1cb74c09.290792e1@cs.com>; from DougEwell2@cs.com on Tue, Oct 23, 2001 at 11:43:29PM -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Tue, Oct 23, 2001 at 11:43:29PM -0400, DougEwell2@cs.com wrote:
> In a message dated 2001-10-23 11:13:14 Pacific Daylight Time, klensin@jck.com 
> writes:
> 
> >  On the other hand, one problem is more severe
> >  than in the Chinese case: in the general case, a Serbo-Croatian
> >  string written in Cyrillic cannot be distinguished, on a
> >  character string basis, from uses of Cyrillic for other languages
> >  (e.g., Russian), which should not be mapped and, similarly, a
> >  string written in Roman-based characters cannot be distinguished,
> >  on a character string basis, from the Roman-based characters of
> >  another language (English?) which, again, cannot be mapped.
> 
> But this problem *does* exist in the Chinese case, because certain Han 
> characters can also be used to write Japanese or (I've been told) Korean.  In 
> a Japanese or Korean context, it wouldn't make any sense to map the correct 
> "traditional" Han character to a simplified "equivalent"; the simplified 
> character is only equivalent if the language is Chinese.

Dear Doug Ewell,

Even though your statement is not wrong, more clarification is needed.
There are two types of simplified chinese characters. One type is 
traditional (oops) one and the other type is relatively new one.

First type of traditional simplified chinese characters was invented
over long period of time among four countries (China, Korea, Japan, Taiwan).
Some of them are common to all for countries, some of them are only
used in one of those countries. (Let's call it type I)

Second type of relatively new simplified chinese characters was invented
around 50 years ago (I am not sure) by the People Republic of China
government. (Let's call it type II)

In Korea, we do not use type II. For type I, even though we do not
decided any policy, but we may easily prevent disputes by registration
policy.

But, if Unicode incorporate new rule to NFC, it may affect the usage
of chinese characters in any of those countries who are sharing CJK
area.

-- 
/*------------------------------------------------
YangWoo Ko : newcat@spsoft.co.kr
We Invent Enterprise Software Solutions
and Make You Secure & Powerful.
------------------------------------------------*/



From owner-idn@ops.ietf.org  Wed Oct 24 01:13:43 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01608
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 01:13:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wG40-000Bc2-00
	for idn-data@psg.com; Tue, 23 Oct 2001 21:54:48 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wG3z-000Bbv-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 21:54: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 NAA15515;
	Wed, 24 Oct 2001 13:54:25 +0900
Message-ID: <012701c15c48$16774340$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
References: <011701c15be0$4473db90$dd00a8c0@jamessonyvaio> <3BD5FFAC.4E066695@zetnet.co.uk> <00a001c15c33$e0dd94f0$ec1bd9d2@temp> <3BD633E3.A6A7BE2F@zetnet.co.uk>
Subject: Re: [idn] (bias) summary of reordering discussion
Date: Wed, 24 Oct 2001 13:55:22 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id BAA01608


----- Original Message ----- 
From: "David Hopwood" <david.hopwood@zetnet.co.uk>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
Sent: Wednesday, October 24, 2001 12:22 PM
Subject: Re: [idn] (bias) summary of reordering discussion


> -----BEGIN PGP SIGNED MESSAGE-----
> 
> Soobok Lee wrote:
> > From: "David Hopwood" <david.hopwood@zetnet.co.uk>
> > >
> > > Make that an explicit objection - I think it's far too complicated to
> > > justify the marginal benefits. Also, any changes or additions to
> > > reordering would have disastrous consequences for name comparison, and
> > > Soobok Lee's zq--/uq-- proposal does not fix this.
> > 
> > I expect you clarify this assertions with detailed examples soon.
> 
> The problem is this: how does an application that doesn't support the
> latest version check whether a zq-- label is equivalent to a uq-- label?
> 
> For nameprep without reordering, an old application can perform matching
> that will be correct provided that the inputs are nameprepped (i.e.
> case folded NFC or NFKC), and this is sufficient for most purposes. In
> your proposal, OTOH, it must just give up, because it has no information
> about how characters are reordered in uq-- labels. I consider this to be
> a fatal flaw in the proposal.

That's  not new problem in uq--/zq-- scheme, but already in current single zq-- scheme.

let's assume new nameprep with new added script  which contains mapping X-->Y.
The mapping may be one of case folding/NFC/NFKC or others.
Old and New nameprep applications  exchanged  differenetly-encoded two 
X.com ACE labels  and  each  did comparisons on two labels. What happens
with single  zq-- scheme ?  Both applications will fail.
even users of new applications  are left clueless for the failure.

But with zq--/uq-- scheme, the new application would succeed, but old application
should give up and issue warning to users that new nameprep labels come in.
zq--/uq-- scheme provides the clues for the failure/inpasse and teach what to to for fallback
mechanisms. That's the virture of uq--/zq-- scheme.

Even without its intended connection to REORDERING issues,  zq--/uq-- scheme are still
worth to research for its pros/cons  for the sake of  consistent/safer handling of 
unassigned code points.  Let's think about more...

Soobok Lee


> 
> This flaw would not arise if reordering only applied to characters that
> are assigned now (i.e. in Unicode 3.1), and new scripts were never
> reordered. In that case the zq--/uq-- versioning wouldn't be needed.
> However, I still don't think that reordering is worthwhile even in that
> 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
> 
> iQEVAwUBO9YzrzkCAxeYt5gVAQHtVAgAmjLhWyYvhTnBRHoIcN55JoTY+cTc6JlB
> +kv6kYJ6x2CHJd4iG/3OyIY5J7ix4tqWbn9Zynhk0F4hleCZT+Yn1l7BRSNAnq7i
> TERrhaj2L+0Aw6cI/S1/OCL9TVEBDKA70eSXQH8nzCejG1Zjy3N5dheKwNTpbCyV
> UxpJ3g6CRsFzV1O7z3pItIS2M7DSDeKQzTYa3rJo42bepYv75oTmDfDEvHKLvcRD
> o5qaEnYWOhrWkdvyPPGiG6eW5D7by4kWxyYsnsKJ4ZpThYqRyB70YnWcuBT+/7J1
> k93JBDsgOg8iqCoXVVAxvhFB6IjN4knwIdkuBWCSmudQUleHYiJ4yg==
> =bt61
> -----END PGP SIGNATURE-----
> 




From owner-idn@ops.ietf.org  Wed Oct 24 01:25:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02462
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 01:25:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wGMi-000CH3-00
	for idn-data@psg.com; Tue, 23 Oct 2001 22:14:08 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wGMh-000CGx-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 22:14:07 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9O5EFN50210;
	Wed, 24 Oct 2001 01:14:15 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110240514.f9O5EFN50210@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Update Charter revision 2 
In-Reply-To: Your message of "Wed, 24 Oct 2001 10:59:26 +0800."
             <030701c15c37$e463d8b0$1401000a@jamessonyvaio> 
Date: Wed, 24 Oct 2001 01:14:14 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James,

The changes you propose (and I grant that someone else may have written them
and it just appears under your name as the co-chair of the moment) to the WG
description aren't useful. There are three, the first ("names") is irrelevant,
the second (DNSEXT) is probably wrong (this WG is going to modify DNS??? How
in an IDNA program?), and the third refers to two undefined entities, an "I18N
group" and "other relevant expert group".

The changes to you (see above) propose to the WG goals are also problematic.
You've got the WG turned into an ACE-specific WG. That is consistent with a
rough consensus (I don't mind being "wrong"), but inconsistent with your new
bit in the description section that touts this WG as something that may change
the DNS, outside of the DNSEXT WG. Pick one, but not both.

The proposed deletion of an informational RFC(s) documenting various proposals
and implementations and providing a technical evaluation of the proposals is a
real loss. I guess we'll find out if the IESG is so tired of this mess that it
is willing to conclude "de minimus".

I'm so unfond of the way the requirements draft has been edited that I don't
mind if it never sees the light of day, I don't think it got a close reading
since -07, when John observed that it didn't appear to have ever been the
subject of a close and careful reading.

Overlooking the hand waving, you propose to wrap up the IDN WG in six months.
I have the impression that even with an IDNA/Nameprep/ACE (amc-z) site of
drafts (which I don't support, but that's not the point), that carefully
getting to the point of closure of a WG with a complex problem area would
take sligtly longer -- given that no draft has yet gone to LC (other than
the requirements draft back in February, and possibly more than once since
then, corrections welcome). The experience of the http WG comes to mind.

BTW, your "(bias) summary of reordering discussion" note was the most
constructive thing I've seen you do.

Eric



From owner-idn@ops.ietf.org  Wed Oct 24 01:33:19 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02882
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 01:33:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wGSf-000CVF-00
	for idn-data@psg.com; Tue, 23 Oct 2001 22:20:17 -0700
Received: from smtp22.singnet.com.sg ([165.21.101.202])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wGSe-000CV7-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 22:20:16 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp22.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9O5Nli13664;
	Wed, 24 Oct 2001 13:23:47 +0800
Message-ID: <055201c15c4b$8dc70ea0$1401000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>, <brunner@nic-naa.net>
References: <200110240514.f9O5EFN50210@nic-naa.net>
Subject: Re: [idn] Update Charter revision 2 
Date: Wed, 24 Oct 2001 13:20:10 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Then propose the changes you want in the update charter.

Broad comments like this lead us nowhere nearer to the goal, unless of
cos your goal is to derail the group as long as possible.

-James Seng

> The changes you propose (and I grant that someone else may have
written them
> and it just appears under your name as the co-chair of the moment) to
the WG
> description aren't useful. There are three, the first ("names") is
irrelevant,
> the second (DNSEXT) is probably wrong (this WG is going to modify
DNS??? How
> in an IDNA program?), and the third refers to two undefined entities,
an "I18N
> group" and "other relevant expert group".
>
> The changes to you (see above) propose to the WG goals are also
problematic.
> You've got the WG turned into an ACE-specific WG. That is consistent
with a
> rough consensus (I don't mind being "wrong"), but inconsistent with
your new
> bit in the description section that touts this WG as something that
may change
> the DNS, outside of the DNSEXT WG. Pick one, but not both.
>
> The proposed deletion of an informational RFC(s) documenting various
proposals
> and implementations and providing a technical evaluation of the
proposals is a
> real loss. I guess we'll find out if the IESG is so tired of this mess
that it
> is willing to conclude "de minimus".
>
> I'm so unfond of the way the requirements draft has been edited that I
don't
> mind if it never sees the light of day, I don't think it got a close
reading
> since -07, when John observed that it didn't appear to have ever been
the
> subject of a close and careful reading.
>
> Overlooking the hand waving, you propose to wrap up the IDN WG in six
months.
> I have the impression that even with an IDNA/Nameprep/ACE (amc-z) site
of
> drafts (which I don't support, but that's not the point), that
carefully
> getting to the point of closure of a WG with a complex problem area
would
> take sligtly longer -- given that no draft has yet gone to LC (other
than
> the requirements draft back in February, and possibly more than once
since
> then, corrections welcome). The experience of the http WG comes to
mind.
>
> BTW, your "(bias) summary of reordering discussion" note was the most
> constructive thing I've seen you do.
>
> Eric




From owner-idn@ops.ietf.org  Wed Oct 24 01:48:44 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04131
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 01:48:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wGjI-000CpM-00
	for idn-data@psg.com; Tue, 23 Oct 2001 22:37:28 -0700
Received: from imo-m04.mx.aol.com ([64.12.136.7])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wGjI-000CpE-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 22:37:28 -0700
Received: from DougEwell2@cs.com
	by imo-m04.mx.aol.com (mail_out_v31_r1.8.) id i.16f.2d15e17 (4562);
	Wed, 24 Oct 2001 01:37:20 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <16f.2d15e17.2907ad8f@cs.com>
Date: Wed, 24 Oct 2001 01:37:19 EDT
Subject: Re: [idn] (bias) summary of reordering discussion
To: idn@ops.ietf.org
CC: lsb@postel.co.kr, david.hopwood@zetnet.co.uk
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a message dated 2001-10-23 22:16:54 Pacific Daylight Time, 
lsb@postel.co.kr writes yet again:

> let's assume new nameprep with new added script  which contains mapping 
X-->Y.

No, let's not assume this, because UTC/WG2 have said repeatedly that this 
will not happen.  I keep saying this, and Soobok keeps ignoring it.

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Wed Oct 24 01:48:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04142
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 01:48:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wGgC-000Cmk-00
	for idn-data@psg.com; Tue, 23 Oct 2001 22:34:16 -0700
Received: from imo-d01.mx.aol.com ([205.188.157.33])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wGgB-000Cmc-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 22:34:15 -0700
Received: from DougEwell2@cs.com
	by imo-d01.mx.aol.com (mail_out_v31_r1.8.) id i.91.12422552 (4562);
	Wed, 24 Oct 2001 01:34:11 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <91.12422552.2907acd2@cs.com>
Date: Wed, 24 Oct 2001 01:34:10 EDT
Subject: Re: [idn] An ignorant question about TC<-> SC
To: idn@ops.ietf.org, unicode@unicode.org
CC: newcat@spsoft.co.kr
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a message dated 2001-10-23 21:38:30 Pacific Daylight Time, 
newcat@spsoft.co.kr writes:

>  ...
>  But, if Unicode incorporate new rule to NFC, it may affect the usage
>  of chinese characters in any of those countries who are sharing CJK
>  area.

If the goal is to get Unicode/10646 to endorse a mapping scheme between 
Traditional Chinese and Simplified Chinese, whether as part of a 
normalization form or otherwise, then that discussion belongs on the Unicode 
mailing list (to which I have cross-posted this message).

The banner for this cause needs to be carried by someone else other than me, 
who (a) thinks it is a good idea and (b) has the technical knowledge about 
CJK to support it.

-Doug Ewell
 Fullerton, California

> On Tue, Oct 23, 2001 at 11:43:29PM -0400, DougEwell2@cs.com wrote:
>> In a message dated 2001-10-23 11:13:14 Pacific Daylight Time, 
klensin@jck.com 
>> writes:
>>
>>>  On the other hand, one problem is more severe
>>>  than in the Chinese case: in the general case, a Serbo-Croatian
>>>  string written in Cyrillic cannot be distinguished, on a
>>>  character string basis, from uses of Cyrillic for other languages
>>>  (e.g., Russian), which should not be mapped and, similarly, a
>>>  string written in Roman-based characters cannot be distinguished,
>>>  on a character string basis, from the Roman-based characters of
>>>  another language (English?) which, again, cannot be mapped.
>>
>> But this problem *does* exist in the Chinese case, because certain Han 
>> characters can also be used to write Japanese or (I've been told) Korean.  
In 
>> a Japanese or Korean context, it wouldn't make any sense to map the 
correct 
>> "traditional" Han character to a simplified "equivalent"; the simplified 
>> character is only equivalent if the language is Chinese.
>
>  Dear Doug Ewell,
>
>  Even though your statement is not wrong, more clarification is needed.
>  There are two types of simplified chinese characters. One type is 
>  traditional (oops) one and the other type is relatively new one.
>
>  First type of traditional simplified chinese characters was invented
>  over long period of time among four countries (China, Korea, Japan, 
Taiwan).
>  Some of them are common to all for countries, some of them are only
>  used in one of those countries. (Let's call it type I)
>
>  Second type of relatively new simplified chinese characters was invented
>  around 50 years ago (I am not sure) by the People Republic of China
>  government. (Let's call it type II)
>
>  In Korea, we do not use type II. For type I, even though we do not
>  decided any policy, but we may easily prevent disputes by registration
>  policy.
>
>  But, if Unicode incorporate new rule to NFC, it may affect the usage
>  of chinese characters in any of those countries who are sharing CJK
>  area.



From owner-idn@ops.ietf.org  Wed Oct 24 01:50:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04257
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 01:50:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wGlJ-000Cpz-00
	for idn-data@psg.com; Tue, 23 Oct 2001 22:39:33 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wGlI-000Cpt-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 22:39: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 OAA29431;
	Wed, 24 Oct 2001 14:39:05 +0900
Message-ID: <014a01c15c4e$53d02940$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <DougEwell2@cs.com>, <idn@ops.ietf.org>
Cc: <david.hopwood@zetnet.co.uk>
References: <16f.2d15e17.2907ad8f@cs.com>
Subject: Re: [idn] (bias) summary of reordering discussion
Date: Wed, 24 Oct 2001 14:40:01 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id BAA04257


----- Original Message ----- 
From: <DougEwell2@cs.com>
To: <idn@ops.ietf.org>
Cc: <lsb@postel.co.kr>; <david.hopwood@zetnet.co.uk>
Sent: Wednesday, October 24, 2001 2:37 PM
Subject: Re: [idn] (bias) summary of reordering discussion


> In a message dated 2001-10-23 22:16:54 Pacific Daylight Time, 
> lsb@postel.co.kr writes yet again:
> 
> > let's assume new nameprep with new added script  which contains mapping 
> X-->Y.
> 
> No, let's not assume this, because UTC/WG2 have said repeatedly that this 
> will not happen.  I keep saying this, and Soobok keeps ignoring it.

What if X->Y is a Case mapping ?
You said case folding would happend in the future added script ? Didn't you?

Soobok Lee

> 
> -Doug Ewell
>  Fullerton, California
> 




From owner-idn@ops.ietf.org  Wed Oct 24 02:03:15 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08956
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 02:03:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wGxL-000DPL-00
	for idn-data@psg.com; Tue, 23 Oct 2001 22:51:59 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wGxJ-000DPE-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 22:51:57 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id OAA00888;
	Wed, 24 Oct 2001 14:51:41 +0900
Message-ID: <017401c15c50$16879d50$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>, <DougEwell2@cs.com>, <idn@ops.ietf.org>
Cc: <david.hopwood@zetnet.co.uk>
Subject: [idn] nfc/nfkc/case mappings are freezed up ?
Date: Wed, 24 Oct 2001 14:52:38 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id CAA08956

Mark and Martin and Doug,

Case mapping / NFC /NFKC tables are already freezed up and will
remain unchanged forever even with future newly added scripts ????

There is no need to modify or upgrade all the tables?
Congratulations on the birth of the perfect baby if Doug's assertion is right.
Please clarify.

Soobok Lee


----- Original Message ----- 
From: "Soobok Lee" <lsb@postel.co.kr>
To: <DougEwell2@cs.com>; <idn@ops.ietf.org>
Cc: <david.hopwood@zetnet.co.uk>
Sent: Wednesday, October 24, 2001 2:40 PM
Subject: Re: [idn] (bias) summary of reordering discussion



----- Original Message ----- 
From: <DougEwell2@cs.com>
To: <idn@ops.ietf.org>
Cc: <lsb@postel.co.kr>; <david.hopwood@zetnet.co.uk>
Sent: Wednesday, October 24, 2001 2:37 PM
Subject: Re: [idn] (bias) summary of reordering discussion


> In a message dated 2001-10-23 22:16:54 Pacific Daylight Time, 
> lsb@postel.co.kr writes yet again:
> 
> > let's assume new nameprep with new added script  which contains mapping 
> X-->Y.
> 
> No, let's not assume this, because UTC/WG2 have said repeatedly that this 
> will not happen.  I keep saying this, and Soobok keeps ignoring it.

What if X->Y is a Case mapping ?
You said case folding would happend in the future added script ? Didn't you?

Soobok Lee

> 
> -Doug Ewell
>  Fullerton, California
> 





From owner-idn@ops.ietf.org  Wed Oct 24 02:08:27 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13285
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 02:08:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wH2i-000DbH-00
	for idn-data@psg.com; Tue, 23 Oct 2001 22:57:32 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wH2h-000Db9-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 22:57:31 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9O5veN51223;
	Wed, 24 Oct 2001 01:57:41 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110240557.f9O5veN51223@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Update Charter revision 2 
In-Reply-To: Your message of "Wed, 24 Oct 2001 13:20:10 +0800."
             <055201c15c4b$8dc70ea0$1401000a@jamessonyvaio> 
Date: Wed, 24 Oct 2001 01:57:40 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James,

My goal isn't to delay anything, here. I plan to exercise the LC periods
responsibly, but I don't consider that "delay" as its absence is "haste".

Here is a specific recommendation.

Delete every one of your (caveat, someone else could have written them, etc.)
deltas on the description section.

Delete every one of your (caveat, see above) deltas on the goals section.

This includes leaving the informational memo(s) as part of what this WG is
committed to delivering to the IETF.

What you do with the requirements document is up to you. I suggest you ask
for someone who actually cares and is careful to take over editing of it.
If you do that, then add it to the set of informational memo(s) this WG has
a stake in reporting out.

That is the easy part. The harder part is milestones.

There is (ideally) a set of standards track memos, and a set of informational
track memos. I've given this a lot more thought than the space after the "."
usually conveys. Your drafts and your WG with its "rough consensus" (not mine,
thanks) ought to reach LC between the 1st and 2nd meetings of next year. The
drafts you don't have even started, input methods, namepreps, zonefile, and
the forgotten writing order, and other bits that surface as all the big items
are "solved" should take you and your WG out through the end of the year, and
a really careful basic evaluation memo (revision of Paul's) not quite that
long.

Eric



From owner-idn@ops.ietf.org  Wed Oct 24 02:12:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13606
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 02:12:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wH7s-000DmN-00
	for idn-data@psg.com; Tue, 23 Oct 2001 23:02:52 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wH7r-000Dlw-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 23:02:52 -0700
Received: from [192.168.1.5] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id IAA07307;
	Wed, 24 Oct 2001 08:02:41 +0200 (MET DST)
Date: Wed, 24 Oct 2001 07:59:59 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Soobok Lee <lsb@postel.co.kr>, DougEwell2@cs.com, idn@ops.ietf.org
cc: david.hopwood@zetnet.co.uk
Subject: Re: [idn] (bias) summary of reordering discussion
Message-ID: <2813301.1003910399@localhost>
In-Reply-To: <014a01c15c4e$53d02940$ec1bd9d2@temp>
References: <16f.2d15e17.2907ad8f@cs.com>
 <014a01c15c4e$53d02940$ec1bd9d2@temp>
X-Mailer: Mulberry/2.1.0 (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 2001-10-24 14.40 +0900 Soobok Lee <lsb@postel.co.kr> wrote:

>> In a message dated 2001-10-23 22:16:54 Pacific Daylight Time, 
>> lsb@postel.co.kr writes yet again:
>> 
>> > let's assume new nameprep with new added script  which contains
>> > mapping 
>> X-->Y.
>> 
>> No, let's not assume this, because UTC/WG2 have said repeatedly that
>> this  will not happen.  I keep saying this, and Soobok keeps ignoring it.
> 
> What if X->Y is a Case mapping ?
> You said case folding would happend in the future added script ? Didn't
> you?

Mappings X-->Y will happen, but, _never_ where X is a codepoint which is
assigned in an earlier version of the Unicode Spec. X has to be an earlier
not assigned codepoint.

   paf




From owner-idn@ops.ietf.org  Wed Oct 24 02:13:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13674
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 02:13:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wH7v-000Dn6-00
	for idn-data@psg.com; Tue, 23 Oct 2001 23:02:55 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wH7u-000Dmb-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 23:02:54 -0700
Received: from [192.168.1.5] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id IAA07304;
	Wed, 24 Oct 2001 08:02:38 +0200 (MET DST)
Date: Wed, 24 Oct 2001 07:58:50 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: DougEwell2@cs.com, idn@ops.ietf.org, unicode@unicode.org
cc: newcat@spsoft.co.kr
Subject: Re: [idn] An ignorant question about TC<-> SC
Message-ID: <2809159.1003910330@localhost>
In-Reply-To: <91.12422552.2907acd2@cs.com>
References:  <91.12422552.2907acd2@cs.com>
X-Mailer: Mulberry/2.1.0 (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 2001-10-24 01.34 -0400 DougEwell2@cs.com wrote:

> If the goal is to get Unicode/10646 to endorse a mapping scheme between 
> Traditional Chinese and Simplified Chinese, whether as part of a 
> normalization form or otherwise, then that discussion belongs on the
> Unicode  mailing list (to which I have cross-posted this message).

Correct, but Unicode Consortium have already made an explicit statement to
the IETF that they don't think such tables would be a good idea. So, the
chances of IETF being able to convince Unicode Consortium they should
create something they already made up their mind they will not do is what I
would call minimal.

But, you point out the correct process.

  paf




From owner-idn@ops.ietf.org  Wed Oct 24 02:16:01 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13873
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 02:15:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wH9L-000Dsa-00
	for idn-data@psg.com; Tue, 23 Oct 2001 23:04:23 -0700
Received: from smtp24.singnet.com.sg ([165.21.101.204])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wH9K-000DsT-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 23:04:22 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp24.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9O658Z02885;
	Wed, 24 Oct 2001 14:05:08 +0800
Message-ID: <05cc01c15c51$b351e680$1401000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        <idn@ops.ietf.org>
References: <200110240557.f9O5veN51223@nic-naa.net>
Subject: Re: [idn] Update Charter revision 2 
Date: Wed, 24 Oct 2001 14:04:10 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

No explaination other than asking for deletion?

-James Seng

----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
<idn@ops.ietf.org>; <brunner@nic-naa.net>
Sent: Wednesday, October 24, 2001 1:57 PM
Subject: Re: [idn] Update Charter revision 2


> James,
>
> My goal isn't to delay anything, here. I plan to exercise the LC
periods
> responsibly, but I don't consider that "delay" as its absence is
"haste".
>
> Here is a specific recommendation.
>
> Delete every one of your (caveat, someone else could have written
them, etc.)
> deltas on the description section.
>
> Delete every one of your (caveat, see above) deltas on the goals
section.
>
> This includes leaving the informational memo(s) as part of what this
WG is
> committed to delivering to the IETF.
>
> What you do with the requirements document is up to you. I suggest you
ask
> for someone who actually cares and is careful to take over editing of
it.
> If you do that, then add it to the set of informational memo(s) this
WG has
> a stake in reporting out.
>
> That is the easy part. The harder part is milestones.
>
> There is (ideally) a set of standards track memos, and a set of
informational
> track memos. I've given this a lot more thought than the space after
the "."
> usually conveys. Your drafts and your WG with its "rough consensus"
(not mine,
> thanks) ought to reach LC between the 1st and 2nd meetings of next
year. The
> drafts you don't have even started, input methods, namepreps,
zonefile, and
> the forgotten writing order, and other bits that surface as all the
big items
> are "solved" should take you and your WG out through the end of the
year, and
> a really careful basic evaluation memo (revision of Paul's) not quite
that
> long.
>
> Eric




From owner-idn@ops.ietf.org  Wed Oct 24 02:16:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13904
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 02:16:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wH83-000DnM-00
	for idn-data@psg.com; Tue, 23 Oct 2001 23:03:03 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wH82-000DnE-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 23:03:03 -0700
Received: from [192.168.1.5] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id IAA07300;
	Wed, 24 Oct 2001 08:02:36 +0200 (MET DST)
Date: Wed, 24 Oct 2001 07:54:53 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Soobok Lee <lsb@postel.co.kr>, David Hopwood <david.hopwood@zetnet.co.uk>,
        idn@ops.ietf.org
Subject: Re: [idn] (bias) summary of reordering discussion
Message-ID: <2794943.1003910093@localhost>
In-Reply-To: <012701c15c48$16774340$ec1bd9d2@temp>
References: <011701c15be0$4473db90$dd00a8c0@jamessonyvaio>
 <3BD5FFAC.4E066695@zetnet.co.uk> <00a001c15c33$e0dd94f0$ec1bd9d2@temp>
 <3BD633E3.A6A7BE2F@zetnet.co.uk> <012701c15c48$16774340$ec1bd9d2@temp>
X-Mailer: Mulberry/2.1.0 (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 2001-10-24 13.55 +0900 Soobok Lee <lsb@postel.co.kr> wrote:

> let's assume new nameprep with new added script  which contains mapping
> X-->Y. The mapping may be one of case folding/NFC/NFKC or others.
> Old and New nameprep applications  exchanged  differenetly-encoded two 
> X.com ACE labels  and  each  did comparisons on two labels. What happens
> with single  zq-- scheme ?  Both applications will fail.
> even users of new applications  are left clueless for the failure.

This is not correct.

Say that the mapping exists in version 3, but not in version 2 of nameprep.

This implies that X is not an assigned codepoint in version 2.

Y can have been assigned in version 2.

An application which read X from a keyboard or something else where the
name "enters the system" have to do nameprep. Two things can now have
happened. Either the application understand version 3 of nameprep, and X is
mapped to Y, or the application does not understand version 3, and then X
is not allowed, as no non-assigned codepoints is allowed.

In neither of these cases X will be transferred over to the other
application.

   paf




From owner-idn@ops.ietf.org  Wed Oct 24 02:40:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15534
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 02:40:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wHUC-000Eo5-00
	for idn-data@psg.com; Tue, 23 Oct 2001 23:25:56 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wHUB-000Enf-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 23:25:55 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id PAA11464;
	Wed, 24 Oct 2001 15:25:37 +0900
Message-ID: <01d101c15c54$d4065e80$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
References: <011701c15be0$4473db90$dd00a8c0@jamessonyvaio> <3BD5FFAC.4E066695@zetnet.co.uk> <00a001c15c33$e0dd94f0$ec1bd9d2@temp> <3BD633E3.A6A7BE2F@zetnet.co.uk> <012701c15c48$16774340$ec1bd9d2@temp> <2794943.1003910093@localhost>
Subject: [idn] stringprep and unassigned code points
Date: Wed, 24 Oct 2001 15:26:34 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id CAA15534


----- Original Message ----- 
From: "Patrik Fältström" <paf@cisco.com>
 > 
> Say that the mapping exists in version 3, but not in version 2 of nameprep.
> 
> This implies that X is not an assigned codepoint in version 2.
> 
> Y can have been assigned in version 2.
> 
> An application which read X from a keyboard or something else where the
> name "enters the system" have to do nameprep. Two things can now have
> happened. Either the application understand version 3 of nameprep, and X is
> mapped to Y, or the application does not understand version 3, and then X
> is not allowed, as no non-assigned codepoints is allowed.
> 
> In neither of these cases X will be transferred over to the other
> application.
> 

Do you mean that old nameprep application cannot encode unassigned code
points into ACE label at all ?  What do you mean by "query" that can 
contains unassigned code points  in your stringprep document ? 
Is it native label  or ACE one ?  Please suggest real applications 
which will process input native labels as "query"  or  "stored strings" .

Soobok Lee




From owner-idn@ops.ietf.org  Wed Oct 24 02:48:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16280
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 02:48:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wHba-000F48-00
	for idn-data@psg.com; Tue, 23 Oct 2001 23:33:34 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wHbZ-000F42-00
	for idn@ops.ietf.org; Tue, 23 Oct 2001 23:33:33 -0700
Received: from [192.168.1.5] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id IAA10686;
	Wed, 24 Oct 2001 08:33:22 +0200 (MET DST)
Date: Wed, 24 Oct 2001 08:33:11 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Soobok Lee <lsb@postel.co.kr>, David Hopwood <david.hopwood@zetnet.co.uk>,
        idn@ops.ietf.org
Subject: [idn] Re: stringprep and unassigned code points
Message-ID: <2932789.1003912391@localhost>
In-Reply-To: <01d101c15c54$d4065e80$ec1bd9d2@temp>
References: <011701c15be0$4473db90$dd00a8c0@jamessonyvaio>
 <3BD5FFAC.4E066695@zetnet.co.uk> <00a001c15c33$e0dd94f0$ec1bd9d2@temp>
 <3BD633E3.A6A7BE2F@zetnet.co.uk> <012701c15c48$16774340$ec1bd9d2@temp>
 <2794943.1003910093@localhost> <01d101c15c54$d4065e80$ec1bd9d2@temp>
X-Mailer: Mulberry/2.1.0 (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 2001-10-24 15.26 +0900 Soobok Lee <lsb@postel.co.kr> wrote:

> Do you mean that old nameprep application cannot encode unassigned code
> points into ACE label at all ?  What do you mean by "query" that can 
> contains unassigned code points  in your stringprep document ? 
> Is it native label  or ACE one ?  Please suggest real applications 
> which will process input native labels as "query"  or  "stored strings" .

As I responded to your question for clearifications in the stringprep
draft, and never got comments or questions back, I thought you understood.
And, as I said in that mail, I am happy to get other words than "query" and
"stored strings".

Please go back to that message of mine which already responds to this and
ask questions on that mail instead.

   paf




From owner-idn@ops.ietf.org  Wed Oct 24 03:22:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18357
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 03:22:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wI5X-000FnV-00
	for idn-data@psg.com; Wed, 24 Oct 2001 00:04:31 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wI5W-000FnP-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 00:04:30 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VVx4QNobLZno5chNH3etjPbA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GJHFEAXN; Wed, 24 Oct 2001 03:03:40 EDT
To: jseng@pobox.org.sg
Cc: klensin@jck.com, idn@ops.ietf.org
Date: Tue, 23 Oct 2001 18:15:17 -0700
Subject: Re: [idn] An ignorant question about TC<-> SC
Message-ID: <20011023.181520.-246775.0.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.5
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-1,3-95
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana Ye <liana.ydisg@juno.com>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



On Wed, 24 Oct 2001 09:30:07 +0800 "James Seng/Personal"
<jseng@pobox.org.sg> writes:
> >  From linguistic on phoneme analysis,  TC/SC are identical by
> > all authoritive dictionaries and standards with exceptions
> > listed (for dialective and historical use).
> 
> It should be "TC/SC Phrase" to be more exact.
>

Why it should be Phrase? The standards published by 
Chinese always are characters and we are talking about 
code points of UCS in [nameprep].  Are you referring to 
input disambiguation or are you talking about a dictionary.

If you are talking about stringprep, a string has to be 
decomposed into UCS code points anyway for matching,
then the place to start dealing with CJK for IDN identifiers 
is still in nameprep not in stringprep.
 
> There is also a problem with "identical by all authoritive
> dictionaries". All dictionaries have (slight/some) differences in 
> what
> they considered identical. The devil is in the level of details.

And we should following many standard bodies to draw the 
line to cut the details at approperate places.  I may call this
a transformation from analog to digital :-)

> 
> > To treat UCS code points on the same base, the 4,000 to 20,000
> > number needs to be doubled, and treat TC/SC in a general way
> > is a test for correctly treat 8,000 to 56,000 symbols for the long
> run.
> 
> There are 70,000+ han ideograph in ISO10646:2001.
> 
> -James Seng
> 

And there are over 100,000 han ideograph in database already.  
But how many of them are to be used by a common name? 
How do we know about it?  How do we design a system to 
accommodate all of them? 

  The conventional way is to regulate them with tables,  
all  CJKs have published the first 4000 as "required" 
for education standards. Then there comes the next 
4000 as they are often used in names.  

 Then the next 4000 are nice to have for an editing 
software. This brings the number of characters to 
12,000, the BIG5 standard. And it is a good indicator 
of how many characters are really needed for IDN 
application.  There are always unhappy users for 
not able to find the one he wants.  But for IDN 
application we need to consider the 12,000 first, and 
make the majority users happy.  To cover the 
12,000 necessary identifiers for each user group, 
the 21,003 UCS CJK release is a good base  for 
IDN group to consider.  

The rest of CJK characters are supported or not and 
how to be supported in IDN should be an open 
question after the first 21,003 is depoyed for at least 
10 years. (Well, I throw out the number to mean there 
is little demand to use these characters, and if they are 
allowed to be used, the tendency is a chaos even for 
Chinese, as it has been the case in two experiments, 
each lasts 5 - 10 years  in the last 50 years. ) 

At the same time, we shall consider mechanism to 
let people to be able to use the rest of the code points 
with minimum support since they are less controversal 
anyway. Some mechanism like AMC-Z may be good 
enough.   

Now, I'd like to say a few words about the 12,000 
characters, not strings. Unicode has combined the CJK 
into 21,003 code points  from possible 36,000.  In the 
21,003 code points, there are 2000 TC/SC cases, 
which may bring the 21,000 down to 18,000 due to
TC/SC in Chinese and Kanji. The process is as simple 
as Latin case map, why can not let it be treated the 
same? From code mapping point view, a table of 
56,000 entries include all UCS Plane 0 is politically more 
correct than only support a few blocks with "official" 
worded as "Scripts with case mapping" from 
Plane 0, Plane 1 and Plane 3, and leave Plane 0 CJK 
block of 21,003 to stringprep.  It sounds like a language 
tag zigzaging  through UCS space without a flag, good 
for a few, hard for others to follow, defeating the hard 
worked UCS table at hand.

Liana



From owner-idn@ops.ietf.org  Wed Oct 24 03:28:19 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18478
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 03:28:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wIHo-000GWy-00
	for idn-data@psg.com; Wed, 24 Oct 2001 00:17:12 -0700
Received: from smtp24.singnet.com.sg ([165.21.101.204])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wIHm-000GWs-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 00:17:11 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp24.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9O7HxZ09796;
	Wed, 24 Oct 2001 15:17:59 +0800
Message-ID: <06a701c15c5b$e00cf750$1401000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "liana Ye" <liana.ydisg@juno.com>
Cc: <klensin@jck.com>, <idn@ops.ietf.org>
References: <20011023.181520.-246775.0.liana.ydisg@juno.com>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Wed, 24 Oct 2001 15:17:00 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> On Wed, 24 Oct 2001 09:30:07 +0800 "James Seng/Personal"
> <jseng@pobox.org.sg> writes:
> > >  From linguistic on phoneme analysis,  TC/SC are identical by
> > > all authoritive dictionaries and standards with exceptions
> > > listed (for dialective and historical use).
> >
> > It should be "TC/SC Phrase" to be more exact.
> >
>
> Why it should be Phrase? The standards published by
> Chinese always are characters and we are talking about
> code points of UCS in [nameprep].  Are you referring to
> input disambiguation or are you talking about a dictionary.

Because accurate TC/SC (in dictionary) is usually done by "words"
not "characters".

> If you are talking about stringprep, a string has to be
> decomposed into UCS code points anyway for matching,
> then the place to start dealing with CJK for IDN identifiers
> is still in nameprep not in stringprep.

Huh? When is our discussion go into stringprep.

> And there are over 100,000 han ideograph in database already.

What "database" you referring to?

There are over 120,000 han ideographs in existence including some very
rare and old characters. Of which 70,000 already encoded in ISO10646 and
there are more waiting for approval in the IRG.

> Now, I'd like to say a few words about the 12,000
> characters, not strings. Unicode has combined the CJK
> into 21,003 code points  from possible 36,000.  In the
> 21,003 code points, there are 2000 TC/SC cases,
[snip]

If you are going to not happy with how ISO10646 is designed, then bring
it up to your ISO country representive.

But ISO 10646 is the only character set we have at the moment which
covers the most scripts of the world. And no, designing one within this
WG is definately out of scope.

-James Seng




From owner-idn@ops.ietf.org  Wed Oct 24 04:16:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18957
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 04:16:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wIrH-000Hu7-00
	for idn-data@psg.com; Wed, 24 Oct 2001 00:53:51 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wIrF-000Htm-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 00:53:49 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VVYS7I0OKFjIKpLo/SUvI/vQ==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GJHH8RWM; Wed, 24 Oct 2001 03:53:04 EDT
To: klensin@jck.com
Cc: idn@ops.ietf.org
Date: Tue, 23 Oct 2001 19:04:49 -0700
Subject: Re: [idn] An ignorant question about TC<-> SC
Message-ID: <20011023.190452.-246775.1.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.5
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana Ye <liana.ydisg@juno.com>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> 
> In either case, the mapping becomes readily plausible if the
> language, in addition to the content of the character string, is
> known, but is hard to think about without causing side-effects in
> other languages if not.
> 
> Is that helpful?
>      john
> 
> 

Yes, you have asked a good question.  I have an updated 
draft-liana-idn-map.01 to discuss preventions of the side-effects.
It is ready to be released, and I just do not know how much 
interest there is in this WG to read it.   If anyone is interested 
in reading it, please responding to this massege, I can send 
it out to individual requests.

Liana



From owner-idn@ops.ietf.org  Wed Oct 24 04:19:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19008
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 04:19:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wJ5G-000IGq-00
	for idn-data@psg.com; Wed, 24 Oct 2001 01:08:18 -0700
Received: from nat.alvestrand.no ([217.13.28.204] helo=eikenes.alvestrand.no)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wJ5F-000IGg-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 01:08:17 -0700
Received: from askvoll.hjemme.alvestrand.no (unknown [192.168.1.4])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 6073E61C62; Wed, 24 Oct 2001 10:08:15 +0200 (CEST)
Date: Wed, 24 Oct 2001 10:09:45 +0200
From: Harald Alvestrand <harald@alvestrand.no>
To: David Hopwood <david.hopwood@zetnet.co.uk>, idn@ops.ietf.org
Subject: Re: [idn] NFC vs NFKC
Message-ID: <2316070000.1003910983@askvoll.hjemme.alvestrand.no>
In-Reply-To: <3BD5197B.1C280C5D@zetnet.co.uk>
References: <200109181333.JAA19941@ietf.org>		
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>		
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <4.2.0.58.J.20011018183339.031fa100@localhost>
 <3BD0C257.A61BE893@zetnet.co.uk> <3BD5197B.1C280C5D@zetnet.co.uk>
X-Mailer: Mulberry/2.1.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
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 EAA19008

David,
trying to map your categories onto "what would happen at the DNS side".
I think Occam's razor on this problem is roughly:

- If there are 2 names that map to the same sequence of characters
  under NFKC, but not under NFC, and we think they should be DIFFERENT,
  NFKC is bad, and NFC should be used.
- If there are 2 names that map to the same characters under NFKC, but
  not under NFC, and we think the standard should force them to be ALWAYS 
THE
  SAME, NFKC is good.

Characters that do not produce valid domain names are Not A Problem.

--On tirsdag, oktober 23, 2001 08:17:15 +0100 David Hopwood 
<david.hopwood@zetnet.co.uk> wrote:

> This post categorises and describes all of the compatibility
> mappings in Unicode 3.1. The intention is to show that these
> mappings are of little value for name preparation, because in
> almost all cases, one or more of the following applies:
>
> DISALLOWED: the source characters are already disallowed by
>    nameprep-06, so removing the mapping has no effect.

Not A Problem.

> NOT-USEFUL: the source characters are not useful in domain names.

"Useful" is a value judgment, so we need to be careful.
Do you suggest outlawing this category?

> PUNCT-SYMBOL: the source characters are punctuation or symbols,
>    similar to characters that are disallowed for ASCII.

Do you suggest outlawing this category?

> NOT-EQUIV: the source characters are not semantically equivalent
>    to the target characters - i.e. folding them would be more
>    confusing than not folding them (if, for the sake of argument,
>    they were allowed).

This is the category that would argue strongly for NFC rather than NFKC.

> LEGACY: the source characters are *only* intended to be used for
>    round-trip mappings from legacy charsets.

I do not understand what you want to do with those.
Do you suggest outlawing this category?

> DEPRECATED: the source characters are formally deprecated by
>    Unicode 3.1.

Do you suggest outlawing this category?

> OBSCURE: the source characters are very difficult to type, or
>    produce using an input method, so not folding them is unlikely
>    to cause any practical difficulty to users.

Do you suggest outlawing this category?

> INTERNAL: the source characters are normally only intended for
>    internal use within an application or rendering engine.

Do you suggest outlawing this category?

> INCONSISTENT: a category of mappings is arbitrary and inconsistent,
>    with only some of the potential mappings in that category being
>    defined as compatibility equivalences.

I don't understand what you want to do with those.

> There are a very small number of exceptions:
>
> EXCEPTION: the mapping could be quite useful, and there is no
>    reason to exclude it on any of the grounds above.

This is the category that would argue in favour of NFKC and against NFC.

Below, I assume that you are proposing to do the following changes to
nameprep:

- Make NFC rather than NFKC the normalization function of nameprep
- Add NOT-USEFUL, FUNCT-SYMBOL, LEGACY, DEPRECATED, OBSCURE, INTERNAL
to the set of DISALLOWED characters
- Add the EXCEPTION rules to the nameprep ruleset

So the important categories are EXCEPTION (argue in favour of NFKC), 
NOT-EQUIV (argue strongly in favour of NFC) and INCONSISTENT.

>
> I claim that there are few enough exceptions to show that NFKC
> is not the right mapping to use: *if* some of these [EXCEPTION]
> mappings are wanted, they should be handled as an additional step
> to NFC normalisation (similar to the mapped-out characters).

Here is the list I worry about.
I have followed your recommendation on everything you regard as OBSCURE or 
NOT-USEFUL.

>    2011 NON-BREAKING HYPHEN                  [EXCEPTION]
>  FF0D       FULLWIDTH HYPHEN-MINUS                [EXCEPTION]
>  FF10..FF19 FULLWIDTH DIGIT ZERO..NINE            [EXCEPTION]
>  FF21..FF3A FULLWIDTH LATIN CAPITAL LETTER A..Z   [EXCEPTION]
>  FF41..FF5A FULLWIDTH LATIN SMALL LETTER A..Z     [EXCEPTION]
>  FF65..FF9F Half-width Katakana             [EXCEPTION]
>
><compat> Combinations of spacing characters:
>  013F LATIN CAPITAL LETTER L WITH MIDDLE DOT
>  0140 LATIN SMALL LETTER L WITH MIDDLE DOT
>  0149 LATIN SMALL LETTER N PRECEDED BY APOSTROPHE
>  0E33 THAI CHARACTER SARA AM
>  0EB3 LAO VOWEL SIGN AM
>  1E9A LATIN SMALL LETTER A WITH RIGHT HALF RING
>
>  These are combinations of characters that were encoded as a single
>  character in other standards. The only reason why they aren't
>  canonical equivalences, is that the decomposition is to two spacing
>  characters, rather than a spacing character and a combining mark.
>
>  These mappings could be treated as [EXCEPTION]s, although the
>  combined characters are rare enough that it probably isn't worth
>  the hassle to do that. I don't know whether they are produced by
>  keyboard drivers.

The INCONSISTENT label is used with the Radicals block and the Rupee sign, 
which is also labelled "NOT-USEFUL". Probably right.

*ALL* of the NOT-EQUIV cases are also labelled as NOT-USEFUL, OBSCURE or 
another marker I have interpreted as "don't want to use these".

So far, if I have interpreted your missive correctly, you argue for:

- Outlawing a lot of characters (I wouldn't mind that :-)
- Adding the rules from NFKC for the remaining problematic characters
  to Nameprep

Either I am missing something, or there isn't a single domain name that
would be legal under your proposed change to Nameprep where you could tell 
from the output of Nameprep whether NFKC or NFC was applied.

Did I understand you correctly?

                      Harald

Nit (mandatory lingua-political hobby-horse :-)

>  Note that the word "ligature" is overloaded: some ligatures behave
>  like presentation forms (e.g. ff, fi, ffi, ij in Latin scripts),
>  while others (e.g. oe and ae) are part of the spelling of words,
>  such as "arch<ae>ology" (British English spelling). The argument
>  above does not apply to the second type of ligature, but those
>  don't have compatibility mappings.

As a Scandinavian, I have to point out that æ (ae) is not a ligature, it is 
a letter. Others seemingly (ab)use it as a ligature, but it isn't :-)





From owner-idn@ops.ietf.org  Wed Oct 24 04:34:00 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19118
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 04:33:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wJJp-000Ih6-00
	for idn-data@psg.com; Wed, 24 Oct 2001 01:23:21 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wJJo-000Ih0-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 01:23:20 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VVlHIUjgRAqlZuql3RnV9Mxw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GJHKWR5L; Wed, 24 Oct 2001 04:22:34 EDT
To: jseng@pobox.org.sg
Cc: klensin@jck.com, idn@ops.ietf.org
Date: Tue, 23 Oct 2001 19:34:19 -0700
Subject: Re: [idn] An ignorant question about TC<-> SC
Message-ID: <20011023.193421.-246775.2.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.5
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-1,3-81
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana Ye <liana.ydisg@juno.com>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



On Wed, 24 Oct 2001 15:17:00 +0800 "James Seng/Personal"
<jseng@pobox.org.sg> writes:
> > On Wed, 24 Oct 2001 09:30:07 +0800 "James Seng/Personal"
> > <jseng@pobox.org.sg> writes:
> > > >  From linguistic on phoneme analysis,  TC/SC are identical by
> > > > all authoritive dictionaries and standards with exceptions
> > > > listed (for dialective and historical use).
> > >
> > > It should be "TC/SC Phrase" to be more exact.
> > >
> >
> > Why it should be Phrase? The standards published by
> > Chinese always are characters and we are talking about
> > code points of UCS in [nameprep].  Are you referring to
> > input disambiguation or are you talking about a dictionary.
> 
> Because accurate TC/SC (in dictionary) is usually done by "words"
> not "characters".
> 

That is for the readers of the dictionary, not for code tables.
And code tables are referred to individual character mappings.  
something like GB or BIG5 tables.  A dictionary table is a 
word/string mapping. I am, as well as Tseng, Huang, as I 
believe,  were speaking of code tables.  

> > If you are talking about stringprep, a string has to be
> > decomposed into UCS code points anyway for matching,
> > then the place to start dealing with CJK for IDN identifiers
> > is still in nameprep not in stringprep.
> 
> Huh? When is our discussion go into stringprep.
> 
> > And there are over 100,000 han ideograph in database already.
> 
> What "database" you referring to?

The one started in China serveral years ago, but I was not
following that though. 
 
> 
> There are over 120,000 han ideographs in existence including some 
> very
> rare and old characters. Of which 70,000 already encoded in ISO10646 
> and
> there are more waiting for approval in the IRG.
> 
So you have the current state of the collection work.

> > Now, I'd like to say a few words about the 12,000
> > characters, not strings. Unicode has combined the CJK
> > into 21,003 code points  from possible 36,000.  In the
> > 21,003 code points, there are 2000 TC/SC cases,
> [snip]
> 
> If you are going to not happy with how ISO10646 is designed, then 
> bring
> it up to your ISO country representive.
> 

True, I am not happy with the result.  If I have worked with 
it, I don't think I have better idea either  :-)

> But ISO 10646 is the only character set we have at the moment which
> covers the most scripts of the world. And no, designing one within 
> this
> WG is definately out of scope.
> 
> -James Seng
> 
I am not propose to redesign the table.  I do not know 
how did you get that impression on my comments.  My 
proposal is to let Latin case mapping mechanism to
be more general and allow TC/SC character set to be 
treated in a similar way by the CJK community.  We 
do not redefine TC/SC, it is the [Tsconv] author to provide
TC/SC listing and they can decide which subset of 
TC/SC to use case folding feature. 

Liana
 



From owner-idn@ops.ietf.org  Wed Oct 24 04:39:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19148
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 04:39:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wJLT-000Ilt-00
	for idn-data@psg.com; Wed, 24 Oct 2001 01:25:03 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wJLS-000IlX-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 01:25:02 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id RAA16163;
	Wed, 24 Oct 2001 17:24:30 +0900
Message-ID: <025501c15c65$71344db0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
References: <011701c15be0$4473db90$dd00a8c0@jamessonyvaio> <3BD5FFAC.4E066695@zetnet.co.uk> <00a001c15c33$e0dd94f0$ec1bd9d2@temp> <3BD633E3.A6A7BE2F@zetnet.co.uk> <012701c15c48$16774340$ec1bd9d2@temp> <2794943.1003910093@localhost> <01d101c15c54$d4065e80$ec1bd9d2@temp> <2932789.1003912391@localhost>
Subject: Re: [idn] Re: stringprep and unassigned code points
Date: Wed, 24 Oct 2001 17:25:26 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id EAA19148


----- Original Message ----- 
From: "Patrik Fältström" <paf@cisco.com>
To: "Soobok Lee" <lsb@postel.co.kr>; "David Hopwood" <david.hopwood@zetnet.co.uk>; <idn@ops.ietf.org>
Sent: Wednesday, October 24, 2001 3:33 PM
Subject: [idn] Re: stringprep and unassigned code points


> --On 2001-10-24 15.26 +0900 Soobok Lee <lsb@postel.co.kr> wrote:
> 
> > Do you mean that old nameprep application cannot encode unassigned code
> > points into ACE label at all ?  What do you mean by "query" that can 
> > contains unassigned code points  in your stringprep document ? 
> > Is it native label  or ACE one ?  Please suggest real applications 
> > which will process input native labels as "query"  or  "stored strings" .
> 
> As I responded to your question for clearifications in the stringprep
> draft, and never got comments or questions back, I thought you understood.
> And, as I said in that mail, I am happy to get other words than "query" and
> "stored strings".
> 
> Please go back to that message of mine which already responds to this and
> ask questions on that mail instead.

Thanks Patrick.

I finished careful reading your clear answers titled with
 "Re: [idn] questions: unassigned code points in nameprep".

What I understand is:

  "saved string" :  generated ACE labels by applications 
                      with known version of nameprep

  "query"        :  received ACE label from other applications
                      the ACE label may have been generated by 
                         unknown version of nameprep

 from this understanding,

 1) I will prefer to use "generated ACE label" and "received ACE label".
 They seem to be  more intuitive.

 2) Current stringprep prohibits old nameprep to encode into ACE labels 
  any unassigned code points. (MUST NOT).

 3) Therefore, Unassigned code points cannot even begin its trip to other applications from the old nameprep applications. 

 4) If we finalize IDN before TAGALOG is added, there is no way to support
  seamlessly support of TAGALOG input in older nameprep applications 
  but for users to upgrade their s/w.
 
 if anyone read and got more  from the answers, add them to this list please.

 Soobok Lee  
                      
                      


> 
>    paf
> 
> 




From owner-idn@ops.ietf.org  Wed Oct 24 04:42:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19173
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 04:42:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wJPM-000IwB-00
	for idn-data@psg.com; Wed, 24 Oct 2001 01:29:04 -0700
Received: from smtp22.singnet.com.sg ([165.21.101.202])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wJPL-000Ivv-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 01:29:03 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp22.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9O8WRi12484;
	Wed, 24 Oct 2001 16:32:27 +0800
Message-ID: <075901c15c65$e41d6af0$1401000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "liana Ye" <liana.ydisg@juno.com>
Cc: <klensin@jck.com>, <idn@ops.ietf.org>
References: <20011023.193421.-246775.2.liana.ydisg@juno.com>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Wed, 24 Oct 2001 16:28:42 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> That is for the readers of the dictionary, not for code tables.
> And code tables are referred to individual character mappings.  
> something like GB or BIG5 tables.  A dictionary table is a 
> word/string mapping. I am, as well as Tseng, Huang, as I 
> believe,  were speaking of code tables.  

Quote: "...TC/SC are identical by all authoritive dictionaries..."
 
-James Seng




From owner-idn@ops.ietf.org  Wed Oct 24 05:29:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19631
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 05:29:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wKAc-000KqV-00
	for idn-data@psg.com; Wed, 24 Oct 2001 02:17:54 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wKAa-000Kq4-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 02:17:53 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VVPxDnJoPBp/janfT5y5sNsA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GJHN3EDY; Wed, 24 Oct 2001 05:17:32 EDT
To: jseng@pobox.org.sg
Cc: klensin@jck.com, idn@ops.ietf.org
Date: Wed, 24 Oct 2001 02:14:33 -0700
Subject: Re: [idn] An ignorant question about TC<-> SC
Message-ID: <20011024.021638.-280935.0.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.5
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-6,8-18
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana Ye <liana.ydisg@juno.com>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dictionaries implement TC/SC tables. That is the 
reason they are presented as words.  The 
original statement is to indicate the reality, that
is TC/SC is one language.

Liana

On Wed, 24 Oct 2001 16:28:42 +0800 "James Seng/Personal"
<jseng@pobox.org.sg> writes:
> > That is for the readers of the dictionary, not for code tables.
> > And code tables are referred to individual character mappings.  
> > something like GB or BIG5 tables.  A dictionary table is a 
> > word/string mapping. I am, as well as Tseng, Huang, as I 
> > believe,  were speaking of code tables.  
> 
> Quote: "...TC/SC are identical by all authoritive dictionaries..."
>  
> -James Seng
> 



From owner-idn@ops.ietf.org  Wed Oct 24 05:30:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19653
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 05:30:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wKA8-000Kpb-00
	for idn-data@psg.com; Wed, 24 Oct 2001 02:17:24 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wKA7-000KpU-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 02:17:23 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id SAA32679;
	Wed, 24 Oct 2001 18:17:05 +0900
Message-ID: <02b801c15c6c$c8cc2550$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>,
        "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
Subject: [idn] old version nameprep applications
Date: Wed, 24 Oct 2001 18:18:02 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA19653

Hi, David

From clearer understanding of stringprep's strict restrictions on unassigned code points,
the exchange scenario of the enclosed second paragraph of my previous posting,
cannot happen and two cases have even no chance to fail or succeed.

To send new script label, old application should be upgraded.
Therefore, exchange scenario and its one direction of success case 
are possible only  under uq--/zq-- scheme which does not prohibit 
old nameprep application to encode  unassigned code points
 with uq-- prefix.

Soobok Lee


----- Original Message ----- 
From: "Soobok Lee" <lsb@postel.co.kr>
 
That's  not new problem in uq--/zq-- scheme, but already in current single zq-- scheme.

let's assume new nameprep with new added script  which contains mapping X-->Y.
The mapping may be one of case folding/NFC/NFKC or others.
Old and New nameprep applications  exchanged  differenetly-encoded two 
X.com ACE labels  and  each  did comparisons on two labels. What happens
with single  zq-- scheme ?  Both applications will fail.
even users of new applications  are left clueless for the failure.

But with zq--/uq-- scheme, the new application would succeed, but old application
should give up and issue warning to users that new nameprep labels come in.
zq--/uq-- scheme provides the clues for the failure/inpasse and teach what to to for fallback
mechanisms. That's the virture of uq--/zq-- scheme.

Even without its intended connection to REORDERING issues,  zq--/uq-- scheme are still
worth to research for its pros/cons  for the sake of  consistent/safer handling of 
unassigned code points.  Let's think about more...

Soobok Lee

 




From owner-idn@ops.ietf.org  Wed Oct 24 06:06:27 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20089
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 06:06:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wKjk-000MKS-00
	for idn-data@psg.com; Wed, 24 Oct 2001 02:54:12 -0700
Received: from [203.207.0.132] (helo=mail.asiainfra.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wKjj-000MKM-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 02:54:11 -0700
Received: from gix ([203.207.0.121])
	by mail.asiainfra.com (8.9.3/8.9.3) with SMTP id RAA24618;
	Wed, 24 Oct 2001 17:54:20 +0800
From: "Kenny Huang" <huangk@alum.sinica.edu>
To: "John C Klensin" <klensin@jck.com>, <idn@ops.ietf.org>
Subject: RE: [idn] An ignorant question about TC<-> SC
Date: Wed, 24 Oct 2001 17:59:05 +0800
Message-ID: <IHELIFNJKJLDFEMBCENDIEEGCIAA.huangk@alum.sinica.edu>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
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.4807.1700
Importance: Normal
In-Reply-To: <3165078.1003827563@localhost>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id GAA20089

Hi John,

The code re-ordering is transfering code from one code area to
the same area in different order. Therefore the situation you point
out is not going to happen.

Kenny Huang

> -----Original Message-----
> From: owner-idn@ops.ietf.org [mailto:owner-idn@ops.ietf.org]On 
> Behalf Of John C Klensin
> Sent: Tuesday, October 23, 2001 8:59 PM
> To: idn@ops.ietf.org
> Subject: [idn] An ignorant question about TC<-> SC
> 
> 
> While reading David's NFC versus NFKC note, I had an odd thought.
> I've been dissatisfied, as have many others, with the notion that
> TC <-> SC mapping is analogous to case mapping in Roman-derived
> alphabets.   Arguments about whether that analogy applies have
> helped to make the discussion of what is, to me, a very difficult
> topic even more obscure.
> 
> To quote the Unicode standard, "Serbo-Croatian is a single
> language with paired alphabets".  This is a definition with which
> native speakers of the language agree (although, when tensions in
> the Balkans are high, I assume some of them are not completely
> happy about it).  Would it be constructive to think about Chinese
> as "one language, two alphabets"?  If it is, then nameprep or a
> related process ought to be able to map back and forth between
> the Roman-based characters usually used in Croatian contexts and
> the Cyrillic characters usually used in Serbian ones (people do
> this all the time, and certainly expect the two to match).
> 
> Of course, the analogy is not exact (these things never are):
> perhaps partially because there are just fewer characters to deal
> with, there are no cases in which there are potential ambiguities
> in the mappings.  On the other hand, one problem is more severe
> than in the Chinese case: in the general case, a Serbo-Croatian
> string written in Cyrillic cannot be distinguished, on a
> character string basis, from uses of Cyrillic for other languages
> (e.g., Russian), which should not be mapped and, similarly, a
> string written in Roman-based characters cannot be distinguished,
> on a character string basis, from the Roman-based characters of
> another language (English?) which, again, cannot be mapped.
> 
> In either case, the mapping becomes readily plausible if the
> language, in addition to the content of the character string, is
> known, but is hard to think about without causing side-effects in
> other languages if not.
> 
> Is that helpful?
>      john
> 




From owner-idn@ops.ietf.org  Wed Oct 24 06:06:28 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20099
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 06:06:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wKlm-000MPk-00
	for idn-data@psg.com; Wed, 24 Oct 2001 02:56:18 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wKll-000MPS-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 02:56:17 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 2BE097F457; Wed, 24 Oct 2001 18:55:39 +0900 (JST)
Message-Id: <4.2.0.58.J.20011024173147.03995600@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 24 Oct 2001 17:39:20 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, "Soobok Lee" <lsb@postel.co.kr>,
        <DougEwell2@cs.com>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] nfc/nfkc/case mappings are freezed up ?
Cc: <david.hopwood@zetnet.co.uk>
In-Reply-To: <017401c15c50$16879d50$ec1bd9d2@temp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 14:52 01/10/24 +0900, Soobok Lee wrote:
>Mark and Martin and Doug,
>
>Case mapping / NFC /NFKC tables are already freezed up and will
>remain unchanged forever even with future newly added scripts ????
>
>There is no need to modify or upgrade all the tables?

There may indeed be a need to upgrade some of the tables.

For casing, you usually would add both lower and upper case
at the same time, and add that to the table. The way nameprep
is currently designed, the lower case form of the new characters
could be used with old client software. There would be a need
for a client upgrade to use uppercase letters from the new script.
This seems to be a reasonable tradeoff.
But anyway, as far as I know, the scripts in the pipeline are
single-case only, so this is only theory.

For NFC, there is the change that e.g. some new precomposed
character is added. This chance is very low because the Unicode
consortium is on record that it won't do it. But assume it
happens; assume q-cedilla get's added. Then what would happen is
that a decomposition q-cedilla -> q, cedilla gets added to the
big data file, and in addition, q-cedilla gets added to the
so-called composition exclusions.

Now an old application will only know about q and cedilla
and will use these to represent the combination. A new application
may know about the new character q-cedilla, but it would then
also know how to normalize that, and because of the composition
exclusion, it would normalize to q, cedilla, i.e. stay decomposed.

So in both cases, you get the same decomposed result.


Regards,    Martin.



From owner-idn@ops.ietf.org  Wed Oct 24 06:06:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20111
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 06:06:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wKlm-000MPm-00
	for idn-data@psg.com; Wed, 24 Oct 2001 02:56:18 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wKll-000MPT-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 02:56:17 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id E356D7F414; Wed, 24 Oct 2001 18:55:37 +0900 (JST)
Message-Id: <4.2.0.58.J.20011024172508.0392a170@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 24 Oct 2001 17:27:39 +0900
To: Patrik F=?ISO-2022-JP?B?GyRCZ00bKEI=?=tstr =?ISO-2022-JP?B?GyRCi04bKEI=?= <paf@cisco.com>,
        Soobok Lee <lsb@postel.co.kr>, DougEwell2@cs.com, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] (bias) summary of reordering discussion
Cc: david.hopwood@zetnet.co.uk
In-Reply-To: <2813301.1003910399@localhost>
References: <014a01c15c4e$53d02940$ec1bd9d2@temp>
 <16f.2d15e17.2907ad8f@cs.com>
 <014a01c15c4e$53d02940$ec1bd9d2@temp>
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 07:59 01/10/24 +0200, Patrik F$BgM(Btstr$B‹N(B wrote:
>--On 2001-10-24 14.40 +0900 Soobok Lee <lsb@postel.co.kr> wrote:
[Doug Ewell wrote:]

> >> No, let's not assume this, because UTC/WG2 have said repeatedly that
> >> this  will not happen.  I keep saying this, and Soobok keeps ignoring it.
> >
> > What if X->Y is a Case mapping ?
> > You said case folding would happend in the future added script ? Didn't
> > you?

I think he did. But I don't know about any script in the pipeline
that is bicameral (has two cases). (If I'm wrong, please tell me.)
So the chance we get any more bicameral script in Unicode are pretty
low.


>Mappings X-->Y will happen, but, _never_ where X is a codepoint which is
>assigned in an earlier version of the Unicode Spec. X has to be an earlier
>not assigned codepoint.

Yes, that's by design of NFC (and by extension, of NFKC).

Regards,   Martin.



From owner-idn@ops.ietf.org  Wed Oct 24 06:29:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20353
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 06:29:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wL5d-000NIs-00
	for idn-data@psg.com; Wed, 24 Oct 2001 03:16:49 -0700
Received: from [203.207.0.132] (helo=mail.asiainfra.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wL5c-000NIl-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 03:16:48 -0700
Received: from gix ([203.207.0.121])
	by mail.asiainfra.com (8.9.3/8.9.3) with SMTP id SAA24756;
	Wed, 24 Oct 2001 18:16:20 +0800
From: "Kenny Huang" <huangk@alum.sinica.edu>
To: "James Seng/Personal" <jseng@pobox.org.sg>,
        "liana Ye" <liana.ydisg@juno.com>
Cc: <klensin@jck.com>, <idn@ops.ietf.org>
Subject: RE: [idn] An ignorant question about TC<-> SC
Date: Wed, 24 Oct 2001 18:21:05 +0800
Message-ID: <IHELIFNJKJLDFEMBCENDAEEICIAA.huangk@alum.sinica.edu>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
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.4807.1700
Importance: Normal
In-Reply-To: <075901c15c65$e41d6af0$1401000a@jamessonyvaio>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id GAA20353

Dozens of engineers are still working on the final draft, I am not so
sure TC/SC are identical by "all authoritive dictionaries".  But anyway,
what we discuss here is identifier, not language.

Kenny Huang

> -----Original Message-----
> From: owner-idn@ops.ietf.org [mailto:owner-idn@ops.ietf.org]On 
> Behalf Of James Seng/Personal
> Sent: Wednesday, October 24, 2001 4:29 PM
> To: liana Ye
> Cc: klensin@jck.com; idn@ops.ietf.org
> Subject: Re: [idn] An ignorant question about TC<-> SC
> 
> 
> > That is for the readers of the dictionary, not for code tables.
> > And code tables are referred to individual character mappings.  
> > something like GB or BIG5 tables.  A dictionary table is a 
> > word/string mapping. I am, as well as Tseng, Huang, as I 
> > believe,  were speaking of code tables.  
> 
> Quote: "...TC/SC are identical by all authoritive dictionaries..."
>  
> -James Seng
> 




From owner-idn@ops.ietf.org  Wed Oct 24 07:02:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20619
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 07:02:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wLdo-000Oh9-00
	for idn-data@psg.com; Wed, 24 Oct 2001 03:52:08 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wLdm-000Oh3-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 03:52:07 -0700
Received: from dhcp-64-103-49-29.cisco.com (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id MAA04657;
	Wed, 24 Oct 2001 12:51:54 +0200 (MET DST)
Date: Wed, 24 Oct 2001 12:46:47 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Soobok Lee <lsb@postel.co.kr>, David Hopwood <david.hopwood@zetnet.co.uk>,
        idn@ops.ietf.org
Subject: Re: [idn] Re: stringprep and unassigned code points
Message-ID: <3761154.1003927607@localhost>
In-Reply-To: <025501c15c65$71344db0$ec1bd9d2@temp>
References: <011701c15be0$4473db90$dd00a8c0@jamessonyvaio>
 <3BD5FFAC.4E066695@zetnet.co.uk> <00a001c15c33$e0dd94f0$ec1bd9d2@temp>
 <3BD633E3.A6A7BE2F@zetnet.co.uk> <012701c15c48$16774340$ec1bd9d2@temp>
 <2794943.1003910093@localhost> <01d101c15c54$d4065e80$ec1bd9d2@temp>
 <2932789.1003912391@localhost> <025501c15c65$71344db0$ec1bd9d2@temp>
X-Mailer: Mulberry/2.1.1 (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-10-24 17.25 +0900 Soobok Lee <lsb@postel.co.kr> wrote:

> I finished careful reading your clear answers titled with
>  "Re: [idn] questions: unassigned code points in nameprep".
> 
> What I understand is:
> 
>   "saved string" :  generated ACE labels by applications 
>                       with known version of nameprep
> 
>   "query"        :  received ACE label from other applications
>                       the ACE label may have been generated by 
>                          unknown version of nameprep
> 
>  from this understanding,

Yes. Sounds like a good definition.

>  1) I will prefer to use "generated ACE label" and "received ACE label".
>  They seem to be  more intuitive.

Ok.

>  2) Current stringprep prohibits old nameprep to encode into ACE labels 
>   any unassigned code points. (MUST NOT).

Yes.

>  3) Therefore, Unassigned code points cannot even begin its trip to other
> applications from the old nameprep applications. 

Correct.

>  4) If we finalize IDN before TAGALOG is added, there is no way to support
>   seamlessly support of TAGALOG input in older nameprep applications 
>   but for users to upgrade their s/w.

I would like to rephrase this. Your wording is very drastic.

When the stringprep/nameprep documents is done, they will reference one
specific version of the Unicode standard. It looks like version 3.1 at the
moment. Applications made for this version will not be able to handle
codepoints which are unassigned in this version of Unicode.

Now, we all know that new versions of the Unicode Standard will come, with
more codepoints assigned.

If I were an application developer I would not hardcode the tables needed
in the application itself. This so when a new version of the
stringprep/nameprep document comes out after a new version of Unicode
tables is done, the user should be able to upgrade his software in a very
easy way. When the software is upgraded, he can use the newly assigned
codepoints.

And, yes, I have already dealt with this problem once as a programmer, and
saw that this was the easiest way of handling versioning in the software.

    paf




From owner-idn@ops.ietf.org  Wed Oct 24 07:57:32 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22544
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 07:57:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wMV7-00011h-00
	for idn-data@psg.com; Wed, 24 Oct 2001 04:47:13 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wMV6-00011b-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 04:47:12 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9OBlGh01108;
	Wed, 24 Oct 2001 07:47:16 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110241147.f9OBlGh01108@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Update Charter revision 2 
In-Reply-To: Your message of "Wed, 24 Oct 2001 14:04:10 +0800."
             <05cc01c15c51$b351e680$1401000a@jamessonyvaio> 
Date: Wed, 24 Oct 2001 07:47:16 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> No explaination other than asking for deletion?

The author (whomever that may be) of the proposed changes to the WG charter,
"Description", and "Action Items" sections, contributed nothing useful, as
my prior note pointed out.

To be pendantic, I'm not "asking for deletion", you (or someone else, whoever
that may be), is asking to change the charter -- description, action items,
and goals and milestones.

If anything, this surprise "rechartering" is something that begs explination.



From owner-idn@ops.ietf.org  Wed Oct 24 08:49:31 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25483
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 08:49:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wNGS-00030v-00
	for idn-data@psg.com; Wed, 24 Oct 2001 05:36:08 -0700
Received: from smtp22.singnet.com.sg ([165.21.101.202])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wNGR-00030p-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 05:36:07 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp22.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9OCdZi32727;
	Wed, 24 Oct 2001 20:39:36 +0800
Message-ID: <001b01c15c88$709b5420$1501000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        <idn@ops.ietf.org>
References: <200110241147.f9OBlGh01108@nic-naa.net>
Subject: Re: [idn] Update Charter revision 2 
Date: Wed, 24 Oct 2001 20:35:59 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> The author (whomever that may be) of the proposed changes to the WG
charter,
> "Description", and "Action Items" sections, contributed nothing
useful, as
> my prior note pointed out.
>
> To be pendantic, I'm not "asking for deletion", you (or someone else,
whoever
> that may be), is asking to change the charter -- description, action
items,
> and goals and milestones.

The reasoning behind the changes to the charter is stated in the first
revision of the update.
http://www.imc.org/idn/mail-archive/msg04341.html

I dont need to repeat here again.

> If anything, this surprise "rechartering" is something that begs
explination.

There is nothing surprising. It was asked and I have fore warn the group
about possible update to the charter, goal & milestone.

http://www.imc.org/idn/mail-archive/msg04217.html

-James Seng




From owner-idn@ops.ietf.org  Wed Oct 24 09:56:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29434
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 09:56:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wOEQ-0005q7-00
	for idn-data@psg.com; Wed, 24 Oct 2001 06:38:06 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wOEP-0005q1-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 06:38:05 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9ODcCh03756;
	Wed, 24 Oct 2001 09:38:12 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110241338.f9ODcCh03756@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Update Charter revision 2 
In-Reply-To: Your message of "Wed, 24 Oct 2001 20:35:59 +0800."
             <001b01c15c88$709b5420$1501000a@jamessonyvaio> 
Date: Wed, 24 Oct 2001 09:38:12 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James,

Your note of the 23rd got exactly one response -- David Hopwood's, who
offered the text present in your final version's first change, but has
no compelling value to motivate a "rechartering".

Your second proposed change hasn't been discussed in the DNSEXT WG, has
it? It really _is_ rechartering to add "the [IDN] WG may modify the DNS
protocol and other work undertaken by the DNSEXT WG", neh?

The ironic part is that having so avidly, even abusively, taken a apps
path, infrastructure now pops up. Humor me. What is the rational again?
What was "unclear" about the relation between IDN and DNSEXT? Since this
WG isn't going to do anything but applications, by existing rough (wrong)
consensus, what is the necessity for "clarification"?

Your third proposed change really flatters the Unicadettes, but "mappings
between codepoints are out-of-scope" is odd. What is an "ACE" if not a
mapping from one range of integers (codepoints) into another, possibly
identical, range of integers?

If your point is to kill off reordering, and all the related hard items
of living with rfc2130 on a diet of 63 octets, say so.

Incidently, the "I18N group" is undefined.

Similarly, the "other relevant expert group" is undefined.

Your fourth change is an abuse of process.

Individuals, and co-chairs, do not by themselves, add or delete work items
from a working group, at least not according to rfc2026. Paul doesn't want
to continue to edit draft-ietf-idn-compare, fine. Now it is time to look
for a capable and interested editor, or bump this issue to the ADs and the
appeals chain.

Now everything in this item of mail is a repeatition of what I wrote, in my
first note.

If you want to maintain that I've not offered an explination for suggesting
that these of your (and whomever) proposed changes are better not made than
made, that's up to you.

Eric

P.S. All the co-chairs need to accomplish is to reconcile the timeline with
their, and the WG's collective, hoped for future accomplishments. Actually
attempting a re-chartering while attempting to get closure on complex and
contentuous deliverables is risk-seeking, not risk-adverse.

Then again, this is the WG that puts a recommendation into the scope statement
of its requirements draft, so anything is possible.



From owner-idn@ops.ietf.org  Wed Oct 24 10:03:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29869
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 10:03:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wOTc-0006XW-00
	for idn-data@psg.com; Wed, 24 Oct 2001 06:53:48 -0700
Received: from smtp24.singnet.com.sg ([165.21.101.204])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wOTb-0006XQ-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 06:53:47 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp24.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9ODsUZ02272;
	Wed, 24 Oct 2001 21:54:30 +0800
Message-ID: <005a01c15c93$4610ab50$1501000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        <idn@ops.ietf.org>
References: <200110241338.f9ODcCh03756@nic-naa.net>
Subject: Re: [idn] Update Charter revision 2 
Date: Wed, 24 Oct 2001 21:53:34 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Your note of the 23rd got exactly one response -- David Hopwood's, who
> offered the text present in your final version's first change, but has
> no compelling value to motivate a "rechartering".

The recharter has been discussed for a while, some of them offline to
me. The note on 23rd is a notice that there will be a new update, not a
request for discussion. If you are surprised by it, then you have not
follow the list.

The idea is to explicitly limited the scope of work in IDN WG so we can
actually produce something. We been on a very vague charter for a long
time because we are exploring. But it is time to finish it up.

> Your second proposed change hasn't been discussed in the DNSEXT WG,
has
> it? It really _is_ rechartering to add "the [IDN] WG may modify the
DNS
> protocol and other work undertaken by the DNSEXT WG", neh?

The text is extracted from the requirements doc. Your sentence is not
incomplete without the second. "But such changes must be co-ordinated
with the DNSEXT WG". Dont pull statement out of context.

The intention: It is possible that an IDN solution (e.g. UTF-8 solution)
would requires modify DNS protocol. However, such solution need to be
co-ordinate with DNSEXT WG. And Olafur is already aware of this
intention for a while (since San Diego?).

> The ironic part is that having so avidly, even abusively, taken a apps
> path, infrastructure now pops up. Humor me. What is the rational
again?
> What was "unclear" about the relation between IDN and DNSEXT? Since
this
> WG isn't going to do anything but applications, by existing rough
(wrong)
> consensus, what is the necessity for "clarification"?

Because you are assuming that IDNA is the only one moving forward. I am
assuming we will get other proposal.

> Your third proposed change really flatters the Unicadettes, but
"mappings
> between codepoints are out-of-scope" is odd. What is an "ACE" if not a
> mapping from one range of integers (codepoints) into another, possibly
> identical, range of integers?

"Mappings between codepoints" refers to codepoint tables mapping. You
are stretching the meaning. Of course, you can stretch anything you
want. I could argue the existing charter allows us to redefine a new
character code set for the purpose of IDN.

> If your point is to kill off reordering, and all the related hard
items
> of living with rfc2130 on a diet of 63 octets, say so.

I repeat the intention again:

"The discussion to do reordering is within scope. The table for
reordering in my view is a frequency analysis sorting and that maybe
within scope. If reordering creates any codepoints tables, then that
table is not.

The discussion of whether to do TC-SC equivalent matching, and if so,
where and how is also within scope.  The tables of TC-SC is not."

You have obviously twist my words, as usual.

> Individuals, and co-chairs, do not by themselves, add or delete work
items
> from a working group, at least not according to rfc2026. Paul doesn't
want
> to continue to edit draft-ietf-idn-compare, fine. Now it is time to
look
> for a capable and interested editor, or bump this issue to the ADs and
the
> appeals chain.

The ADs have seen the proposed changes. The removed work item is deem no
longer neccessary or relevant at this moment in time. Some (or you) may
still argue it is relevant but on the whole, the topic of comparsion
have not and never been a focus of discussion in the group over the
24months.

> If you want to maintain that I've not offered an explination for
suggesting
> that these of your (and whomever) proposed changes are better not made
than
> made, that's up to you.

That is your opinion. I see no valid arguments in your comment.

Thank you but i like to hear from others.

-Jaes Seng




From owner-idn@ops.ietf.org  Wed Oct 24 10:10:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00263
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 10:10:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wOZl-0006vr-00
	for idn-data@psg.com; Wed, 24 Oct 2001 07:00:09 -0700
Received: from smtp24.singnet.com.sg ([165.21.101.204])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wOZj-0006vi-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 07:00:08 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp24.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9OE11Z05044;
	Wed, 24 Oct 2001 22:01:01 +0800
Message-ID: <006701c15c94$2efd4530$1501000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <idn@ops.ietf.org>, "Yoshiro YONEYA" <yone@po.ntts.co.jp>
References: <030701c15c37$e463d8b0$1401000a@jamessonyvaio> <20011024124949X.yone@po.ntts.co.jp>
Subject: Re: [idn] Update Charter revision 2
Date: Wed, 24 Oct 2001 22:00:03 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> - There is no target for 'Requirements' in milestone.  I think it
>   should be.

It is already move forward for IESG action. it is technically out of the
hand of the wg. (unless the iesg bounce it back to the group) so there
is no need for a explicit milestone.

I will put a changes there tho.

> - I think RFC target in milestone should be identical to action items.
>   Is 'architecture' in milestone denoting item 2?  Is 'protocol'
>   denoting item 3?  Please clarify relation between terms in milestone
>   and action items.

some action items may have more than one RFC.

> - Nameprep is now divided into framework (stringprep) and profile
>   (nameprep).  Is stringprep scope of this WG?  I think it is
>   eventually yes at this moment but I'm not sure, so please clarify
>   position of stringprep.

Good question. As far as it stand now, only draft-ietf-idn-nameprep is
part of IDN work. draft-hoffman-stringprep is not. How it goes will
depends on the author.

I suspect only nameprep will stay within IDN group and stringprep may
remains generic or go to other wg, which may not be formed yet.

-James Seng




From owner-idn@ops.ietf.org  Wed Oct 24 11:23:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03605
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 11:23:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wPbg-0009zh-00
	for idn-data@psg.com; Wed, 24 Oct 2001 08:06:12 -0700
Received: from imo-m09.mx.aol.com ([64.12.136.164])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wPbf-0009zK-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 08:06:11 -0700
Received: from DougEwell2@cs.com
	by imo-m09.mx.aol.com (mail_out_v31_r1.8.) id i.15c.2f21f30 (24898);
	Wed, 24 Oct 2001 11:05:55 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <15c.2f21f30.290832d1@cs.com>
Date: Wed, 24 Oct 2001 11:05:53 EDT
Subject: Re: [idn] (bias) summary of reordering discussion
To: idn@ops.ietf.org
CC: lsb@postel.co.kr
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a message dated 2001-10-23 22:39:40 Pacific Daylight Time, 
lsb@postel.co.kr writes:

>>> let's assume new nameprep with new added script  which contains mapping 
>> X-->Y.
>> 
>> No, let's not assume this, because UTC/WG2 have said repeatedly that this 
>> will not happen.  I keep saying this, and Soobok keeps ignoring it.
>
>  What if X->Y is a Case mapping ?
>  You said case folding would happend in the future added script ? Didn't 
you?

Case mapping has NOTHING to do with normalization, and NOTHING to do with 
reordering.  I will not say this again.

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Wed Oct 24 13:16:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07120
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 13:16:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wRNX-000F5H-00
	for idn-data@psg.com; Wed, 24 Oct 2001 09:59:43 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wRNW-000F5A-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 09:59:42 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9OGxhh08477;
	Wed, 24 Oct 2001 12:59:43 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110241659.f9OGxhh08477@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Update Charter revision 2 
In-Reply-To: Your message of "Wed, 24 Oct 2001 21:53:34 +0800."
             <005a01c15c93$4610ab50$1501000a@jamessonyvaio> 
Date: Wed, 24 Oct 2001 12:59:42 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James,

If writing "you have not follow the list" makes you feel better, enjoy.

In 030701c15c37$e463d8b0$1401000a@jamessonyvaio, Subject: [idn] Update
Charter revision 2, you wrote:
> Comments please.
>
>-James Seng
>
>--- CUT HERE ---
...

In 005a01c15c93$4610ab50$1501000a@jamessonyvaio, Re: [idn] Update Charter
revision 2, you wrote:
...
> The note on 23rd is a notice that there will be a new update, not a
> request for discussion.

Now, as to the substance.

Of the changes you propose to the Description section, only one, the 3rd,
has the effect of limiting scope. Whether the limit is useful is another
issue.

The second proposed change:

	The WG work may modify the DNS protocol and other related work
	undertaken by the DNSEXT WG.

	But such changes must be co-ordinated with the DNSEXT WG.

I left off comment on the second sentance because it is unnecessary, no
matter what the first sentance reads, in fact, the very idea that your
off-list discussion has extended to you controlling authority over DNSEXT
is comic.

As to the substance of the proposed change, which is interesting:

> Because you are assuming that IDNA is the only one moving forward. I am
> assuming we will get other proposal.

In your working group there is rough consensus to exclude any non-application
framework, and the DNSEXT WG exists for extensions to the DNS (and in this
context "DNS" is understood not to be an "application", though it sure as heck
is one).

I'm writing a UTF-8 draft (no surprise except how long its taking), and Erik
asked me to send a copy to your working group, but I'm submitting it to the
DNSEXT WG, for consideration to adopt as a working group document, not to your
WG, which I view as out of control and about the worst run WG I've seen in the
decade+ I've been participating in the IETF. To be fair, most of my work since
the mid-80's has been in a more collegial operating systems environment, where
higher levels of professional courtsey are the norm. 

Commenting on the third proposed change, you observed:
...
> I could argue the existing charter allows us to redefine a new
> character code set for the purpose of IDN.
...

Correct. This was the subject of a discussion (off-list) between myself,
the ADs (Erik and Tom), the technical advisors (John and Harald), Patrik,
and both you and Marc.

There is a difference between creating an alternative or alternatives to
iso10646, and discussing CRLF mapping. In your zeal to control the reordering
problem space (and it is complex), you over reached.

> You have obviously twist my words, as usual.

Maybe you made a mistake. Consider the possibility.

> ... I see no valid arguments in your comment.
>
> Thank you but i like to hear from others.

By all means, the work group is more than just some egos let loose on a list.

Eric



From owner-idn@ops.ietf.org  Wed Oct 24 14:08:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09728
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 14:08:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wSAV-000HIp-00
	for idn-data@psg.com; Wed, 24 Oct 2001 10:50:19 -0700
Received: from smtp15.singnet.com.sg ([165.21.6.35])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wSAU-000HIc-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 10:50:18 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp15.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9OHlwN07126;
	Thu, 25 Oct 2001 01:47:58 +0800
Message-ID: <006001c15cb4$5570f7a0$1501000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <idn@ops.ietf.org>, <brunner@nic-naa.net>
References: <005a01c15cb3$2d07c5b0$1501000a@jamessonyvaio>
Subject: Re: [idn] Update Charter revision 2 
Date: Thu, 25 Oct 2001 01:50:13 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric,

I see no further need for discussion since this has now degrade into a
personal attack, which is also typical of you.

Aside: If "higher levels of professional courtesy" means subtle sarcatic
personal attack on a continuous basis and derailing working group
because of private conflicts, I think I rather not have any part of
"higher levels of professional courtesy".

-James Seng

> James,
>
> If writing "you have not follow the list" makes you feel better,
enjoy.
>
> In , Subject: [idn] Update
> Charter revision 2, you wrote:
> > Comments please.
> >
> >-James Seng
> >
> >--- CUT HERE ---
> ...
>
> In , Re: [idn] Update Charter
> revision 2, you wrote:
> ...
> > The note on 23rd is a notice that there will be a new update, not a
> > request for discussion.
>
> Now, as to the substance.
>
> Of the changes you propose to the Description section, only one, the
> 3rd,
> has the effect of limiting scope. Whether the limit is useful is
another
> issue.
>
> The second proposed change:
>
> The WG work may modify the DNS protocol and other related work
> undertaken by the DNSEXT WG.
>
> But such changes must be co-ordinated with the DNSEXT WG.
>
> I left off comment on the second sentance because it is unnecessary,
no
> matter what the first sentance reads, in fact, the very idea that your
> off-list discussion has extended to you controlling authority over
> DNSEXT
> is comic.
>
> As to the substance of the proposed change, which is interesting:
>
> > Because you are assuming that IDNA is the only one moving forward. I
> am
> > assuming we will get other proposal.
>
> In your working group there is rough consensus to exclude any
> non-application
> framework, and the DNSEXT WG exists for extensions to the DNS (and in
> this
> context "DNS" is understood not to be an "application", though it sure
> as heck
> is one).
>
> I'm writing a UTF-8 draft (no surprise except how long its taking),
and
> Erik
> asked me to send a copy to your working group, but I'm submitting it
to
> the
> DNSEXT WG, for consideration to adopt as a working group document, not
> to your
> WG, which I view as out of control and about the worst run WG I've
seen
> in the
> decade+ I've been participating in the IETF. To be fair, most of my
work
> since
> the mid-80's has been in a more collegial operating systems
environment,
> where
> higher levels of professional courtsey are the norm.
>
> Commenting on the third proposed change, you observed:
> ...
> > I could argue the existing charter allows us to redefine a new
> > character code set for the purpose of IDN.
> ...
>
> Correct. This was the subject of a discussion (off-list) between
myself,
> the ADs (Erik and Tom), the technical advisors (John and Harald),
> Patrik,
> and both you and Marc.
>
> There is a difference between creating an alternative or alternatives
to
> iso10646, and discussing CRLF mapping. In your zeal to control the
> reordering
> problem space (and it is complex), you over reached.
>
> > You have obviously twist my words, as usual.
>
> Maybe you made a mistake. Consider the possibility.
>
> > ... I see no valid arguments in your comment.
> >
> > Thank you but i like to hear from others.
>
> By all means, the work group is more than just some egos let loose on
a
> list.
>
> Eric
>
>
>




From owner-idn@ops.ietf.org  Wed Oct 24 14:27:01 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10521
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 14:27:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wSW7-000IIk-00
	for idn-data@psg.com; Wed, 24 Oct 2001 11:12:39 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wSW6-000IIe-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 11:12:38 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9OICjh10119;
	Wed, 24 Oct 2001 14:12:45 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110241812.f9OICjh10119@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
cc: idn@ops.ietf.org, brunner@nic-naa.net, brunner@nic-naa.net
Subject: Re: [idn] Update Charter revision 2 
In-Reply-To: Your message of "Thu, 25 Oct 2001 01:50:13 +0800."
             <006001c15cb4$5570f7a0$1501000a@jamessonyvaio> 
Date: Wed, 24 Oct 2001 14:12:45 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James,

If everything I wrote about was you, not the charter, the items, and some
parts of the WG process, "you" are very ... large, and the charter, work
items, and some part of the WG process very ... small.

I don't see it that way.

I do think there are things you can do to be a more effective chair, but
you'll have to listen to someone you can listen to. Make the smallest set
of changes to the charter you can, keep and post clear dates and process
milestones, be civil to everone, seperate your self from your works, and
from the WG's works, delegate, use your co-chair, get better use out of
your tech advisors (John's departures into LDAP and Harald's worship of
Unicode can't be their only uses), and work on your parinoia. Just because
I think you are vastly less than perfect doesn't mean I'm trying to make
you less -- I've got better things to do.

This isn't netnews, it isn't the James Seng show, and this isn't real work.
Drafts are.

Now I'm going to give this a rest.

Eric



From owner-idn@ops.ietf.org  Wed Oct 24 16:22:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13648
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 16:22:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wUJI-000Mri-00
	for idn-data@psg.com; Wed, 24 Oct 2001 13:07:32 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wUJH-000Mrc-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 13:07:31 -0700
Received: from amc by nicemice.net with local (Exim 3.32 #1 (Debian))
	id 15wUJG-00029u-00
	for <idn@ops.ietf.org>; Wed, 24 Oct 2001 13:07:30 -0700
Date: Wed, 24 Oct 2001 20:07:30 +0000
From: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>
To: IETF idn working group <idn@ops.ietf.org>
Subject: [idn] information density in various languages (was Re: hi)
Message-ID: <20011024200729.A7803@nicemice.net>
Reply-To: IETF idn working group <idn@ops.ietf.org>
References: <E15v7Sl-000LZE-00@psg.com> <4.2.0.58.J.20011022115559.0390cc70@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4.2.0.58.J.20011022115559.0390cc70@localhost>
User-Agent: Mutt/1.3.22i
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Martin Duerst <duerst@w3.org> wrote:

> > I think each Hangul character carries the information of only about
> > 1.5 English letters,
>
> It may be lower than Chinese, but I'm very surprised it should be that
> low.

You're right.  My estimate must have been based on an anomalous sample.
Here are the counts for Genesis chapter 1:

King James:     3167 letters
Basic English:  3088 letters
Chinese Union:   778 ideographs
Korean Revised: 1201 Hangul

references:
http://www.ccim.org/bible/
http://bible.wisenet.co.kr/

So it's about 4.0 English letters per Chinese ideograph, and about 2.6
English letters per Korean Hangul.

Each Korean Hangul takes about 2.9 octets in AMC-ACE-Z, which means a
maximal Korean domain label (20 hangul) holds about as much information
as a 52-letter English string, which about 17% less information than
a maximal English domain label (63 letters), and about 38% less
information than a maximal Chinese domain label (19 ideographs).

I now retract this statement:

> Of all the languages I've looked at, Korean is by far the least dense
> when encoded using AMC-ACE-Z.

In light of the new data, I doubt that Korean is the least dense.

AMC



From owner-idn@ops.ietf.org  Wed Oct 24 19:21:36 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16807
	for <idn-archive@lists.ietf.org>; Wed, 24 Oct 2001 19:21:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wWs3-0002h2-00
	for idn-data@psg.com; Wed, 24 Oct 2001 15:51:35 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.33 #1)
	id 15wWs2-0002gw-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 15:51:34 -0700
Received: (qmail 7498 invoked by uid 104); 24 Oct 2001 22:51:32 -0000
Received: from yves@realnames.com by friendly.realnames.com with qmail-scanner-0.96 (. Clean. Processed in 0.831807 secs); 24 Oct 2001 22:51:32 -0000
Received: from heaven.internal.realnames.com (10.1.5.39)
  by friendly.realnames.com with SMTP; 24 Oct 2001 22:51:31 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:1956]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <5839@heaven.internal.realnames.com>
	 for <lsb@postel.co.kr>; Wed, 24 Oct 2001 3:48:27 PM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2653.19)
	id <V3D1F8P3>; Wed, 24 Oct 2001 15:51:08 -0700
Message-ID: <7FC3066C236FD511BC5900508BAC86FE4D7DE5@trestles.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: "'Soobok Lee'" <lsb@postel.co.kr>,
        =?iso-8859-1?Q?Patrik_F=E4ltstr=F6?=
	=?iso-8859-1?Q?m?= <paf@cisco.com>,
        idn@ops.ietf.org
Subject: RE: [idn] Re: stringprep and unassigned code points
Date: Wed, 24 Oct 2001 15:47:43 -0700
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

> I finished careful reading your clear answers titled with
>  "Re: [idn] questions: unassigned code points in nameprep".
> 
> What I understand is:
> 
>   "saved string" :  generated ACE labels by applications
>                       with known version of nameprep
> 
>   "query"        :  received ACE label from other applications
>                       the ACE label may have been generated by
>                          unknown version of nameprep
> 
>  from this understanding,
> 
>  1) I will prefer to use "generated ACE label" and "received ACE label".
>  They seem to be  more intuitive.

I don't think they really are more intuitive; the names still do not convey
the main point you wanted to show, which that the Nameprep version info is
known somehow. I understood the previous names better (at least query, in
the spirit of programming defensively and being prepared for the unassigned
code points).

Anybody cares to find good names conveying this (versioned/dated ACE label
and unversioned/undated ACE label do not sound that much better, form what I
could come up with)?

YA



From owner-idn@ops.ietf.org  Thu Oct 25 00:43:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24267
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 00:43:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wbhS-000BVK-00
	for idn-data@psg.com; Wed, 24 Oct 2001 21:00:58 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wbhR-000BV1-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 21:00:57 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id NAA23562;
	Thu, 25 Oct 2001 13:00:37 +0900
Message-ID: <00fd01c15d09$be6c4520$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Yves Arrouye" <yves@realnames.com>,
        =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        <idn@ops.ietf.org>
References: <7FC3066C236FD511BC5900508BAC86FE4D7DE5@trestles.internal.realnames.com>
Subject: Re: [idn] Re: stringprep and unassigned code points
Date: Thu, 25 Oct 2001 13:01:32 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA24267


----- Original Message ----- 
From: "Yves Arrouye" <yves@realnames.com>
To: "'Soobok Lee'" <lsb@postel.co.kr>; "Patrik Fältström" <paf@cisco.com>; <idn@ops.ietf.org>
Sent: Thursday, October 25, 2001 7:47 AM
Subject: RE: [idn] Re: stringprep and unassigned code points


> > I finished careful reading your clear answers titled with
> >  "Re: [idn] questions: unassigned code points in nameprep".
> > 
> > What I understand is:
> > 
> >   "saved string" :  generated ACE labels by applications
> >                       with known version of nameprep
> > 
> >   "query"        :  received ACE label from other applications
> >                       the ACE label may have been generated by
> >                          unknown version of nameprep
> > 
> >  from this understanding,
> > 
> >  1) I will prefer to use "generated ACE label" and "received ACE label".
> >  They seem to be  more intuitive.
> 
> I don't think they really are more intuitive; the names still do not convey
> the main point you wanted to show, which that the Nameprep version info is
> known somehow. I understood the previous names better (at least query, in
> the spirit of programming defensively and being prepared for the unassigned
> code points).

A generated ACE label become a received ACE label  once it leaves its mother
application and arrive at other applications/dns servers in the outer world.
Therefore,the two distinctions merely express two aspects of one ACE label in its trip from application to applications.

If you received unknown-nameprep-made ACE email addresses from others,
they are "saved" in your addressbook/mailbox. Should we call any received
IDN email address as  "query" (???, why?)  which may have no lookup sematics within email clients?   

If you type new native web address into your browser, they are ACEed and
sent to the dns and webservers. the ACE label is "saved string"(???, why?) 
for for browser, but "query" (right!) for dns and webservers.
 
Soobok Lee



> 
> Anybody cares to find good names conveying this (versioned/dated ACE label
> and unversioned/undated ACE label do not sound that much better, form what I
> could come up with)?
> 
> YA
> 





From owner-idn@ops.ietf.org  Thu Oct 25 02:50:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09975
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 02:50:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wdy0-000ECP-00
	for idn-data@psg.com; Wed, 24 Oct 2001 23:26:12 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wdxz-000ECC-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 23:26:11 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 7A2227F4DC; Thu, 25 Oct 2001 15:25:33 +0900 (JST)
Message-Id: <4.2.0.58.J.20011025143224.03e5b370@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 25 Oct 2001 15:23:14 +0900
To: "Mark Davis" <mark@macchiato.com>,
        "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] NFC vs NFKC
In-Reply-To: <00ba01c15bd6$4eb5f0c0$0c680b41@c1340594a>
References: <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <4.2.0.58.J.20011018183339.031fa100@localhost>
 <3BD0C257.A61BE893@zetnet.co.uk>
 <3BD5197B.1C280C5D@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 08:20 01/10/23 -0700, Mark Davis wrote:
(answering David Hopwood)

>I disagree with your assessment. For example, I believe that it is a good
>thing that the non-breaking feature is suppressed -- that is irrelevant to
>IDNs.

This is a detail that can go one way or another.
The fact that the current DNS has survived a few years
with a hyphen but without the non-breaking hyphen being
accepted suggests that not including it won't hurt too much.
But including it won't hurt too much, either.


>However, it would make your paper much easier to examine if you removed all
>the characters that end up getting disallowed -- they are not
>counter-examples.

I think they are very important. In terms of numbers, there
are I think 3165 compatibility mappings in
http://www.unicode.org/Public/UNIDATA/UnicodeData.txt.
According to David's analysis, which closely matches with
my understanding, something of the order of 50 of these
really need to be mapped. This shows that using NFKC is
serious overkill.

Also, there 1866 NFC mappings. Reducing the number of mappings
from 5031 to 1866 is a saving of over 60%.


>Of the characters that are left that you feel are
>problematic, there are three possibilities that the committee has to judge:
>
>A. they don't matter if they are converted

Yes, most of them will show up so rarely that it indeed
doesn't matter whether they get converted or prohibited.


>B. they do matter, but they can be remapped, or prohibited*
>C. they do matter, and enough to make us abandon NFKC
>
>The downside of abandoning NFKC is that we lose the equivalence between
>thousands of characters that do represent the same fundamental abstract
>characters, such as width variants, Arabic ligatures, etc.

Some of the width variants have been identified as exceptions.
How many of the Arabic ligatures will be entered by users
when they e.g. type in an arabic domain name on a keyboard?

Also, please note that the concept of 'fundamental abstract
character' is not something the IDN WG has been really
concerned about. As David has shown, many of the compatibility
(i.e. NFKC) equivalences are disputable. On the other hand,
for many characters not covered by NFKC you would easily
find some people claiming that some of them represent the
same 'fundamental abstract character'. As an example, many
people on this list might argue that there should be a
SC/TC mapping because the simplified and the traditional
variants represent one and the same 'fundamental abstract
character'.


What this WG has been concerned about is to avoid excluding
variants that could easily be input by the user in place
of some equivalent character (to distinguish this from
a lookalike that represents something completely different).

David's analysis, which coincides with my findings, has show
that about 50 out of about 3000 compatibility (i.e. NFKC)
equivalents are relevant for user input. Nobody has claimed
anything to the contrary, or brought up any evidence to the
contrary. If anybody has some such evidence, please send it in.


>Note: a character can be deleted by the remapping phase.

Which is not a good idea except for characters where deletion
doesn't make much of a difference (e.g. Arabic Tatweel,
non-spacing marks,...). If somebody would type in
fooBARbaz, and would get to foobaz, because B, A, and R
are mapped out, it would realy be quite bad.


>It can also be
>effectively prohibited *before* NFKC by simply mapping it to an invalid
>character, like space, that is not affected by normalization and ends up
>being prohibited.

Yes. If there were just *a few* characters that we wanted to prohibit
before doing NFKC, while we want to keep most of the NFKC mappings,
then that would be a reasonable idea. But as it turns out, we want
to ignore/prohibit most of the characters mapped by NFKC, while
only mapping very few of them.


>BTW I have very little hope that this committee will ever produce a result
>if issues keep getting re-raised time and time and time again.

How many times has this issue (NFC vs NFCK) been raised, on this list?
How much background material was provided in these discussions?


>For the
>committee to ever reach some kind of resolution, people have to ask
>themselves, *not* whether they think the current situation is absolutely
>optimal (in their view) -- since it *never* will be -- but instead, whether
>they can live with the result; whether there are really any results that
>will cause significant problems in practice.

It is the first time anybody has done such a careful analysis of
NFC vs. NFKC. The choice between NFC and NFKC is rather fundamental,
no the least because IDN also most probably will serve as an example
to other similar problems. The conclusions from this analysis are
quite clear, at least to me.

I agree that asking whether the solution is absolutely optimal
in somebody's personal view is not a question that leads to consensus.
But the question of whether some change is an overall improvement
that helps many while not causing problems for anybody is a very
relevant question.


Regards,    Martin.



From owner-idn@ops.ietf.org  Thu Oct 25 02:56:30 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10318
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 02:56:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wdxz-000ECN-00
	for idn-data@psg.com; Wed, 24 Oct 2001 23:26:11 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wdxy-000EC9-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 23:26:10 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 462BA7F4A8; Thu, 25 Oct 2001 15:25:32 +0900 (JST)
Message-Id: <4.2.0.58.J.20011025140007.0390aec0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 25 Oct 2001 14:32:04 +0900
To: Harald Alvestrand <harald@alvestrand.no>,
        David Hopwood <david.hopwood@zetnet.co.uk>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] NFC vs NFKC
In-Reply-To: <2316070000.1003910983@askvoll.hjemme.alvestrand.no>
References: <3BD5197B.1C280C5D@zetnet.co.uk>
 <200109181333.JAA19941@ietf.org>
 <024301c149a0$c65b1ee0$ec1bd9d2@temp>
 <4.2.0.58.J.20011010135529.03d9e6a0@localhost>
 <4.2.0.58.J.20011018183339.031fa100@localhost>
 <3BD0C257.A61BE893@zetnet.co.uk>
 <3BD5197B.1C280C5D@zetnet.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hello Harald,

I can't speak for David, but some answers below anyway.

At 10:09 01/10/24 +0200, Harald Alvestrand wrote:
>David,
>trying to map your categories onto "what would happen at the DNS side".
>I think Occam's razor on this problem is roughly:
>
>- If there are 2 names that map to the same sequence of characters
>  under NFKC, but not under NFC, and we think they should be DIFFERENT,
>  NFKC is bad, and NFC should be used.
>- If there are 2 names that map to the same characters under NFKC, but
>  not under NFC, and we think the standard should force them to be ALWAYS THE
>  SAME, NFKC is good.
>
>Characters that do not produce valid domain names are Not A Problem.
>
>--On tirsdag, oktober 23, 2001 08:17:15 +0100 David Hopwood 
><david.hopwood@zetnet.co.uk> wrote:

>>NOT-USEFUL: the source characters are not useful in domain names.
>
>"Useful" is a value judgment, so we need to be careful.
>Do you suggest outlawing this category?

Yes.

>>PUNCT-SYMBOL: the source characters are punctuation or symbols,
>>    similar to characters that are disallowed for ASCII.
>
>Do you suggest outlawing this category?

Yes.

>>NOT-EQUIV: the source characters are not semantically equivalent
>>    to the target characters - i.e. folding them would be more
>>    confusing than not folding them (if, for the sake of argument,
>>    they were allowed).
>
>This is the category that would argue strongly for NFC rather than NFKC.

Yes indeed.


>>LEGACY: the source characters are *only* intended to be used for
>>    round-trip mappings from legacy charsets.
>
>I do not understand what you want to do with those.
>Do you suggest outlawing this category?

Yes. IDN is a new system, with the goal of being able to
represent labels in a wide range of scripts. There is no
need to allow artefacts of legacy character encodings,
because IDN isn't designed to map existing names back
and forth from other naming systems.


>>DEPRECATED: the source characters are formally deprecated by
>>    Unicode 3.1.
>
>Do you suggest outlawing this category?

Yes.


>>OBSCURE: the source characters are very difficult to type, or
>>    produce using an input method, so not folding them is unlikely
>>    to cause any practical difficulty to users.
>
>Do you suggest outlawing this category?

Yes indeed. The argument for using NFKC that I have heard
most often is that we want to avoid the situation that
somebody types in a domain name from something s/he has
seen on a billboard,..., but the name is not found because
some compatibility equivalents instead of the actual
characters were input. This, and many of the other categories,
shows that (with exception of [EXCEPTION], of course) there
is really no such problem.


>>INTERNAL: the source characters are normally only intended for
>>    internal use within an application or rendering engine.
>
>Do you suggest outlawing this category?

Yes.


>>INCONSISTENT: a category of mappings is arbitrary and inconsistent,
>>    with only some of the potential mappings in that category being
>>    defined as compatibility equivalences.
>
>I don't understand what you want to do with those.

Outlawing them is the best way to go.

Please note that most characters and character classes in David's
analysis carry more than one label, and that in many if not most
such cases, all of the labels suggest outlawing.


>>There are a very small number of exceptions:
>>
>>EXCEPTION: the mapping could be quite useful, and there is no
>>    reason to exclude it on any of the grounds above.
>
>This is the category that would argue in favour of NFKC and against NFC.

Yes, or in favor of including it in the IDN-specific mapping
before the normalization step, or in delegating this to some
earlier process in the same way we have delegated the
ideographic fullstop to preprocessing.


>Below, I assume that you are proposing to do the following changes to
>nameprep:
>
>- Make NFC rather than NFKC the normalization function of nameprep

Yes.

>- Add NOT-USEFUL, FUNCT-SYMBOL, LEGACY, DEPRECATED, OBSCURE, INTERNAL
>to the set of DISALLOWED characters

Yes.

>- Add the EXCEPTION rules to the nameprep ruleset

Yes, add the relevant mappings to the mapping stage before
normalization.


>So the important categories are EXCEPTION (argue in favour of NFKC), 
>NOT-EQUIV (argue strongly in favour of NFC) and INCONSISTENT.

Yes. But the other categories are also important. They show
that NFKC maps around a lot of dubious, very rarely used, or
otherwise legacy characters. This means that NFKC does a lot
of work that isn't needed at all.

Changing from NFKC to NFC will simplify things, in particular
for standalone implementations that don't have access to
normalization data. The number of normalization mappings is
very significantly reduced. The number of pre-normalization
mappings is just slightly increased. The 'prohibited' data
is exactly the same.


>>I claim that there are few enough exceptions to show that NFKC
>>is not the right mapping to use: *if* some of these [EXCEPTION]
>>mappings are wanted, they should be handled as an additional step
>>to NFC normalisation (similar to the mapped-out characters).
>
>Here is the list I worry about.
>I have followed your recommendation on everything you regard as OBSCURE or 
>NOT-USEFUL.
>
>>    2011 NON-BREAKING HYPHEN                  [EXCEPTION]

This is open for discussion. We could go either way.


>>  FF0D       FULLWIDTH HYPHEN-MINUS                [EXCEPTION]
>>  FF10..FF19 FULLWIDTH DIGIT ZERO..NINE            [EXCEPTION]
>>  FF21..FF3A FULLWIDTH LATIN CAPITAL LETTER A..Z   [EXCEPTION]

These have to be dealt with in case mapping anyway.
We can just directly map them to halfwidt lowercase.


>>  FF41..FF5A FULLWIDTH LATIN SMALL LETTER A..Z     [EXCEPTION]

Yes.


>>  FF65..FF9F Half-width Katakana             [EXCEPTION]

As I have explained in two earlier postings, these are not
something we have to worry about. Just excluding them should
be fine.


>><compat> Combinations of spacing characters:
>>  013F LATIN CAPITAL LETTER L WITH MIDDLE DOT
>>  0140 LATIN SMALL LETTER L WITH MIDDLE DOT
>>  0149 LATIN SMALL LETTER N PRECEDED BY APOSTROPHE
>>  0E33 THAI CHARACTER SARA AM
>>  0EB3 LAO VOWEL SIGN AM
>>  1E9A LATIN SMALL LETTER A WITH RIGHT HALF RING
>>
>>  These are combinations of characters that were encoded as a single
>>  character in other standards. The only reason why they aren't
>>  canonical equivalences, is that the decomposition is to two spacing
>>  characters, rather than a spacing character and a combining mark.
>>
>>  These mappings could be treated as [EXCEPTION]s, although the
>>  combined characters are rare enough that it probably isn't worth
>>  the hassle to do that. I don't know whether they are produced by
>>  keyboard drivers.
>
>The INCONSISTENT label is used with the Radicals block and the Rupee sign, 
>which is also labelled "NOT-USEFUL". Probably right.
>
>*ALL* of the NOT-EQUIV cases are also labelled as NOT-USEFUL, OBSCURE or 
>another marker I have interpreted as "don't want to use these".
>
>So far, if I have interpreted your missive correctly, you argue for:
>
>- Outlawing a lot of characters (I wouldn't mind that :-)
>- Adding the rules from NFKC for the remaining problematic characters
>  to Nameprep

Yes.


>Either I am missing something, or there isn't a single domain name that
>would be legal under your proposed change to Nameprep where you could tell 
>from the output of Nameprep whether NFKC or NFC was applied.
>
>Did I understand you correctly?

Yes. The set of legal domain labels would stay exactly the same.

Regards,   Martin.



From owner-idn@ops.ietf.org  Thu Oct 25 02:57:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10393
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 02:57:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wdxy-000EC7-00
	for idn-data@psg.com; Wed, 24 Oct 2001 23:26:10 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wdxx-000EBv-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 23:26:09 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 350467F4D9; Thu, 25 Oct 2001 15:25:31 +0900 (JST)
Message-Id: <4.2.0.58.J.20011025123919.0681def0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 25 Oct 2001 12:46:53 +0900
To: John C Klensin <klensin@jck.com>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] An ignorant question about TC<-> SC
In-Reply-To: <3165078.1003827563@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 08:59 01/10/23 -0400, John C Klensin wrote:
>While reading David's NFC versus NFKC note, I had an odd thought.
>I've been dissatisfied, as have many others, with the notion that
>TC <-> SC mapping is analogous to case mapping in Roman-derived
>alphabets.   Arguments about whether that analogy applies have
>helped to make the discussion of what is, to me, a very difficult
>topic even more obscure.
>
>To quote the Unicode standard, "Serbo-Croatian is a single
>language with paired alphabets".  This is a definition with which
>native speakers of the language agree (although, when tensions in
>the Balkans are high, I assume some of them are not completely
>happy about it).  Would it be constructive to think about Chinese
>as "one language, two alphabets"?

It is, but it has similar problems as the 'case' analogy:
It can explain some parts of the problem, and can point
to some kind of solutions, but it won't explain or help
with the full problem/solution.


>If it is, then nameprep or a
>related process ought to be able to map back and forth between
>the Roman-based characters usually used in Croatian contexts and
>the Cyrillic characters usually used in Serbian ones (people do
>this all the time, and certainly expect the two to match).

On a good search engine, when searching for items in Serbo-Croatian,
expecting a match is very reasonable. On the other hand, it's
very easy for Serbo-Croatians to understand when and where
a match isn't happening, and what to do to find things nevertheless
(using the other alphabet). Also, there won't be mixups inside
single words, although I could expect some domain names such
as SERBO-croat or foo-FOO (uppercase standing for Cyrillic)
to turn up.


>Of course, the analogy is not exact (these things never are):
>perhaps partially because there are just fewer characters to deal
>with, there are no cases in which there are potential ambiguities
>in the mappings.  On the other hand, one problem is more severe
>than in the Chinese case: in the general case, a Serbo-Croatian
>string written in Cyrillic cannot be distinguished, on a
>character string basis, from uses of Cyrillic for other languages
>(e.g., Russian), which should not be mapped and, similarly, a
>string written in Roman-based characters cannot be distinguished,
>on a character string basis, from the Roman-based characters of
>another language (English?) which, again, cannot be mapped.
>
>In either case, the mapping becomes readily plausible if the
>language, in addition to the content of the character string, is
>known, but is hard to think about without causing side-effects in
>other languages if not.

I agree. For Han ideographs, there are other languages such
as Japanese and Korean. Also, adding some kind of language
identifier is not an option because billboards, napkins,
notebooks,... don't carry language (except implicitly, maybe).


Regards,   Martin.



From owner-idn@ops.ietf.org  Thu Oct 25 02:58:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10463
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 02:58:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wdxy-000EC8-00
	for idn-data@psg.com; Wed, 24 Oct 2001 23:26:10 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wdxx-000EBw-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 23:26:09 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id AD8537F4DB; Thu, 25 Oct 2001 15:25:31 +0900 (JST)
Message-Id: <4.2.0.58.J.20011025124759.068cb6a0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 25 Oct 2001 12:54:21 +0900
To: Patrik F=?ISO-2022-JP?B?GyRCZ00bKEI=?=tstr =?ISO-2022-JP?B?GyRCi04bKEI=?= <paf@cisco.com>,
        "James Seng/Personal" <jseng@pobox.org.sg>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] (bias) summary of reordering discussion
In-Reply-To: <153522.1003866071@localhost>
References: <011701c15be0$4473db90$dd00a8c0@jamessonyvaio>
 <011701c15be0$4473db90$dd00a8c0@jamessonyvaio>
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,

Just some clarifications below:

At 19:41 01/10/23 +0200, Patrik F$BgM(Btstr$B‹N(B wrote:

>o Nameprep mappings is defined by UTC, not IETF.
>   -> I am nervous when we in IETF talk about these things

The main mappings used by nameprep (casemapping and normalization)
are defined by the UTC. But it is IETF that chooses which mappings
to select (e.g. NFC vs. NFKC), it is IETF that may request other
mappings to be created (NFC was created based on a request by W3C,
an additional file was added to help IETF with case mapping,
a (tentative, implicit) request for TC/SC mappings was turned down).

Also, nameprep contains a few additional mappings and prohibitions
that are motivated by the specific situation of domain names,
without taking these from anywhere.


Regards,   Martin.



From owner-idn@ops.ietf.org  Thu Oct 25 02:59:35 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10534
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 02:59:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wdy4-000ECd-00
	for idn-data@psg.com; Wed, 24 Oct 2001 23:26:16 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wdy1-000EBt-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 23:26:13 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 4B0F77F4D7; Thu, 25 Oct 2001 15:25:30 +0900 (JST)
Message-Id: <4.2.0.58.J.20011025120138.065c8c80@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 25 Oct 2001 12:12:08 +0900
To: Patrik F=?ISO-2022-JP?B?GyRCZ00bKEI=?=tstr =?ISO-2022-JP?B?GyRCi04bKEI=?= <paf@cisco.com>,
        Soobok Lee <lsb@postel.co.kr>,
        David Hopwood <david.hopwood@zetnet.co.uk>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Re: stringprep and unassigned code points
In-Reply-To: <3761154.1003927607@localhost>
References: <025501c15c65$71344db0$ec1bd9d2@temp>
 <011701c15be0$4473db90$dd00a8c0@jamessonyvaio>
 <3BD5FFAC.4E066695@zetnet.co.uk>
 <00a001c15c33$e0dd94f0$ec1bd9d2@temp>
 <3BD633E3.A6A7BE2F@zetnet.co.uk>
 <012701c15c48$16774340$ec1bd9d2@temp>
 <2794943.1003910093@localhost>
 <01d101c15c54$d4065e80$ec1bd9d2@temp>
 <2932789.1003912391@localhost>
 <025501c15c65$71344db0$ec1bd9d2@temp>
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 12:46 01/10/24 +0200, Patrik F$BgM(Btstr$B‹N(B wrote:
>--On 01-10-24 17.25 +0900 Soobok Lee <lsb@postel.co.kr> wrote:
>
> > I finished careful reading your clear answers titled with
> >  "Re: [idn] questions: unassigned code points in nameprep".
> >
> > What I understand is:
> >
> >   "saved string" :  generated ACE labels by applications
> >                       with known version of nameprep
> >
> >   "query"        :  received ACE label from other applications
> >                       the ACE label may have been generated by
> >                          unknown version of nameprep
> >
> >  from this understanding,
>
>Yes. Sounds like a good definition.
>
> >  1) I will prefer to use "generated ACE label" and "received ACE label".
> >  They seem to be  more intuitive.
>
>Ok.

I'm a bit confused here. This is in the stringprep draft, isn't it?
But stringprep is a general framework, so it should be independent
of ACE or any character encoding or other form of encoding.

Either I'm totally confused (please tell me where I went wrong)
or this has to be changed.



> >  2) Current stringprep prohibits old nameprep to encode into ACE labels
> >   any unassigned code points. (MUST NOT).
>
>Yes.
>
> >  3) Therefore, Unassigned code points cannot even begin its trip to other
> > applications from the old nameprep applications.
>
>Correct.

 From the old, single-draft nameprep, I was under the strong impression
that clients may use codepoints for which they don't know whether
they are unassigned or not (they were unassigned when the client
software was released, but may have been assigned in the meantime).

It could be that what Soobok means is that unassigned (even in the last
version) codepoints cannot be entered into registries (because server
have more strict rules), and something that isn't registered won't
get on a billboard,... and therefore won't get to a client and will
therefore not be entered.


> >  4) If we finalize IDN before TAGALOG is added, there is no way to support
> >   seamlessly support of TAGALOG input in older nameprep applications
> >   but for users to upgrade their s/w.
>
>I would like to rephrase this. Your wording is very drastic.
>
>When the stringprep/nameprep documents is done, they will reference one
>specific version of the Unicode standard. It looks like version 3.1 at the
>moment. Applications made for this version will not be able to handle
>codepoints which are unassigned in this version of Unicode.

The way I was understanding things is that the server side where the
new name is registered has to be upgraded to the new version including
Tagalog (and this may be done by a new table, or whatever). The client,
and in particular the stringprep/nameprep/ace part of it, won't need
any upgrades. Of course, there may be a need for installing a Tagalog
keyboard driver or other components to input Tagalog, but that's
a separate problem.


Regards,  Martin.



From owner-idn@ops.ietf.org  Thu Oct 25 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 ESMTP id DAA10825
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 03:03:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wdy2-000ECb-00
	for idn-data@psg.com; Wed, 24 Oct 2001 23:26:14 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wdy1-000EBu-00
	for idn@ops.ietf.org; Wed, 24 Oct 2001 23:26:13 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id D66947F4D8; Thu, 25 Oct 2001 15:25:30 +0900 (JST)
Message-Id: <4.2.0.58.J.20011025122342.067d7100@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 25 Oct 2001 12:34:56 +0900
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>,
        "Yoshiro YONEYA" <yone@po.ntts.co.jp>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Update Charter revision 2
In-Reply-To: <006701c15c94$2efd4530$1501000a@jamessonyvaio>
References: <030701c15c37$e463d8b0$1401000a@jamessonyvaio>
 <20011024124949X.yone@po.ntts.co.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 22:00 01/10/24 +0800, James Seng/Personal wrote:

> > - Nameprep is now divided into framework (stringprep) and profile
> >   (nameprep).  Is stringprep scope of this WG?  I think it is
> >   eventually yes at this moment but I'm not sure, so please clarify
> >   position of stringprep.
>
>Good question. As far as it stand now, only draft-ietf-idn-nameprep is
>part of IDN work. draft-hoffman-stringprep is not. How it goes will
>depends on the author.
>
>I suspect only nameprep will stay within IDN group and stringprep may
>remains generic or go to other wg, which may not be formed yet.

Hello James,

I have raised this issue, too. The title of the 'nameprep' draft
is now "Stringprep Profile for Internationalized Host Names",
and this is an accurate reflection of it's content. 'nameprep'
therefore depends on 'stringprep'. If we want to go to Proposed
Standard with 'nameprep', we cannot have 'stringprep' still as
an I-D. Given your schedule for 'nameprep', it seems impossible
for a new WG to be formed and to take up and finish 'stringprep'
in time. Also, it seems quite dangerous to leave 'stringprep'
to it's authors without at least close coordination with this
WG. Leaving this at suspicions is not good enough. It shouldn't
be difficult to improve on this given that the authors of
stringprep are one of the co-chairs in this group and an
active participant of this group.

Regards,   Martin.




From owner-idn@ops.ietf.org  Thu Oct 25 03:16:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11064
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 03:16:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15weZw-000F11-00
	for idn-data@psg.com; Thu, 25 Oct 2001 00:05:24 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.33 #1)
	id 15weZv-000F0u-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 00:05:23 -0700
Received: (qmail 22541 invoked by uid 104); 25 Oct 2001 07:05:22 -0000
Received: from yves@realnames.com by friendly.realnames.com with qmail-scanner-0.96 (. Clean. Processed in 0.818338 secs); 25 Oct 2001 07:05:22 -0000
Received: from heaven.internal.realnames.com (10.1.5.39)
  by friendly.realnames.com with SMTP; 25 Oct 2001 07:05:21 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:3353]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <7395@heaven.internal.realnames.com>
	 for <david.hopwood@zetnet.co.uk>; Thu, 25 Oct 2001 12:02:28 AM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2653.19)
	id <V3D1F0KL>; Thu, 25 Oct 2001 00:05:09 -0700
Message-ID: <7FC3066C236FD511BC5900508BAC86FE4D7DFD@trestles.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: "'Martin Duerst'" <duerst@w3.org>, Patrik F?tstr ? <paf@cisco.com>,
        Soobok Lee <lsb@postel.co.kr>,
        David Hopwood <david.hopwood@zetnet.co.uk>, idn@ops.ietf.org
Subject: RE: [idn] Re: stringprep and unassigned code points
Date: Thu, 25 Oct 2001 00:01:41 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-2022-jp"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > >  4) If we finalize IDN before TAGALOG is added, there is 
> no way to support
> > >   seamlessly support of TAGALOG input in older nameprep 
> applications
> > >   but for users to upgrade their s/w.
> >
> >I would like to rephrase this. Your wording is very drastic.
> >
> 
> [...]
> 
> The way I was understanding things is that the server side where the
> new name is registered has to be upgraded to the new version including
> Tagalog (and this may be done by a new table, or whatever). 
> The client,
> and in particular the stringprep/nameprep/ace part of it, won't need
> any upgrades. Of course, there may be a need for installing a Tagalog
> keyboard driver or other components to input Tagalog, but that's
> a separate problem.

I have the same understanding you do re: when unassigned code points may be
generated (by an application that gets code points from a version of Unicode
that was released after the version of Nameprep it uses). Now let's suppose
Unicode encodes something new, for which a new Nameprep is released (because
some additions to the mapping table are needed). At this point, the DNS
servers may contain the ACE(Nameprep(names in this new thing)). And
applications get these new codepoints, but because they do not have the
appropriate mapping table, they will pass ACE(Old Nameprep(names in this new
thing)) which will sometimes match the new labels, and sometimes not. Am I
right in thinking that applications do not need to be updated only if
Nameprep does not change for the new code points (looks like common sense
anyway)?

YA



From owner-idn@ops.ietf.org  Thu Oct 25 03:28:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11122
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 03:28:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15weoA-000FRx-00
	for idn-data@psg.com; Thu, 25 Oct 2001 00:20:06 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.33 #1)
	id 15weo9-000FRi-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 00:20:05 -0700
Received: (qmail 24652 invoked by uid 104); 25 Oct 2001 07:20:04 -0000
Received: from yves@realnames.com by friendly.realnames.com with qmail-scanner-0.96 (. Clean. Processed in 0.826439 secs); 25 Oct 2001 07:20:04 -0000
Received: from heaven.internal.realnames.com (10.1.5.39)
  by friendly.realnames.com with SMTP; 25 Oct 2001 07:20:03 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:3804]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <7425@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Thu, 25 Oct 2001 12:16:55 AM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2653.19)
	id <V3D1F0LF>; Thu, 25 Oct 2001 00:19:36 -0700
Message-ID: <7FC3066C236FD511BC5900508BAC86FE4D7DFF@trestles.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: "'idn@ops.ietf.org'" <idn@ops.ietf.org>
Subject: RE: [idn] NFC vs NFKC
Date: Thu, 25 Oct 2001 00:16:05 -0700
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

[Sorry, sent before being done.]

> > >>LEGACY: the source characters are *only* intended to be used for
> > >>    round-trip mappings from legacy charsets.
> > >
> > >I do not understand what you want to do with those.
> > >Do you suggest outlawing this category?
> > 
> > Yes. IDN is a new system, with the goal of being able to
> > represent labels in a wide range of scripts. There is no
> > need to allow artefacts of legacy character encodings,
> > because IDN isn't designed to map existing names back
> > and forth from other naming systems.
> 
> So you do not think it is realistic, for example, to have a 
> document encoded in KS C 5601, containing domain names where 
> the labels would be written using non conjoining Jamo.
> 

[Edit] Is that because nobody uses these anymore, and so you would not
expect a modern invention like IDN to appear in an anachronic way? Is that
the case with all LEGACY characters?

> YA
> 



From owner-idn@ops.ietf.org  Thu Oct 25 03:31:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11154
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 03:31:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wem8-000FOq-00
	for idn-data@psg.com; Thu, 25 Oct 2001 00:18:00 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.33 #1)
	id 15wem7-000FOi-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 00:17:59 -0700
Received: (qmail 24361 invoked by uid 104); 25 Oct 2001 07:17:58 -0000
Received: from yves@realnames.com by friendly.realnames.com with qmail-scanner-0.96 (. Clean. Processed in 0.819335 secs); 25 Oct 2001 07:17:58 -0000
Received: from heaven.internal.realnames.com (10.1.5.39)
  by friendly.realnames.com with SMTP; 25 Oct 2001 07:17:57 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:3748]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <7420@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Thu, 25 Oct 2001 12:14:59 AM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2653.19)
	id <V3D1F0LC>; Thu, 25 Oct 2001 00:17:40 -0700
Message-ID: <7FC3066C236FD511BC5900508BAC86FE4D7DFE@trestles.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: idn@ops.ietf.org
Subject: RE: [idn] NFC vs NFKC
Date: Thu, 25 Oct 2001 00:14:11 -0700
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

> >>LEGACY: the source characters are *only* intended to be used for
> >>    round-trip mappings from legacy charsets.
> >
> >I do not understand what you want to do with those.
> >Do you suggest outlawing this category?
> 
> Yes. IDN is a new system, with the goal of being able to
> represent labels in a wide range of scripts. There is no
> need to allow artefacts of legacy character encodings,
> because IDN isn't designed to map existing names back
> and forth from other naming systems.

So you do not think it is realistic, for example, to have a document encoded
in KS C 5601, containing domain names where the labels would be written
using non conjoining Jamo.

YA



From owner-idn@ops.ietf.org  Thu Oct 25 03:42:32 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11290
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 03:42:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wev9-000FbB-00
	for idn-data@psg.com; Thu, 25 Oct 2001 00:27:19 -0700
Received: from [133.27.228.201] (helo=toro.w3.mag.keio.ac.jp)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wev8-000Fb4-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 00:27:18 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 1DF0F7F414; Thu, 25 Oct 2001 16:26:39 +0900 (JST)
Message-Id: <4.2.0.58.J.20011025160632.02e644e0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 25 Oct 2001 16:27:10 +0900
To: liana Ye <liana.ydisg@juno.com>, klensin@jck.com
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] An ignorant question about TC<-> SC
Cc: idn@ops.ietf.org
In-Reply-To: <20011023.130225.-133319.2.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

At 13:02 01/10/23 -0700, liana Ye wrote:

>  From screen display point view, TC/SC are different glyph
>  sets(who defines the sets? How is it used by 1/5 of the world
>population? Is Uicode group the only authoritive one? In
>China there are over 600 recorded views on this).

The Han ideographs in Unicode/ISO 10646 are defined by the
IRG (Ideographic Raporteur Group). This group reports to
ISO/IEC SC2 WG2, the ISO WG responsible for ISO 10646.
It is composed of representatives from all the countries
or similar entities interested in Han ideographs. That
includes China, Japan, Korea (both South and North), Taiwan,
Hong Kong, Singapore, and the US (I hope I didn't forget
anybody, and please excuse the maybe politically uncorrect
shortcuts). The US is the only country represented without
a tradition of using Han ideographs, but usually only
sends a small delegation and mainly helps with wording.
Many other countries may send rather large delegations
(given the number of characters, which means a lot of
work, this is no surprise). The Unicode consortium
participates in the IRG with an observer status only.

The IRG has published guidelines for deciding when to
unify two occurences and when not. Because of the very
huge number of characters, there is in some cases indeed
a thin line as to whether something should be unified or
not. And in these cases, the IRG just has to make a decision.

Overall, the guidelines are somewhat difficult to understand
at first, but they are designed mainly with a 'least surprise
to the average user' in mind, and I think they have achieved
this goal very well. The guidelines are based on earlier
ones used for the Japanese standard.

The core of the guidelines says that if two characters look
significantly different, then they are encoded with two codes
even if they e.g. are one-to-one SC/TC equivalents. This is
to avoid suddenly changing the appearance of letters for a
user who may not be familiar with the significantly differently
looking shape. On the other hand, cases where there is only
a small difference in shape are unified (i.e. only one code)
unless this small difference in shape makes an actual
difference in meaning.

Overall, the results are so that if you present a text
where you change the glyph shapes within the range that
is unified, people who have done basic education but don't
know about different shapes (e.g. people in Taiwan or
Hong Kong who only know about TC, or people in China or
Singapore who only know about SC, or people in Japan who
only know about the forms used in Japan) will read over
these changes without problems, and might at some points
say 'this looks a bit strange', but will still identify
the character.

There are some exceptions to these rule related to backwards-
compatible roundtripping (source separation rule).


Hope this helps,      Martin.



From owner-idn@ops.ietf.org  Thu Oct 25 04:05:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11467
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 04:05:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wfFz-000G28-00
	for idn-data@psg.com; Thu, 25 Oct 2001 00:48:51 -0700
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wfFy-000G21-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 00:48:50 -0700
Received: from zetnet.co.uk (man-s226.dialup.zetnet.co.uk [194.247.45.97])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f9P7mcd31476;
	Thu, 25 Oct 2001 08:48:39 +0100
Message-ID: <3BD7C0A0.86D101CE@zetnet.co.uk>
Date: Thu, 25 Oct 2001 08:34:56 +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: James Seng/Personal <jseng@pobox.org.sg>, idn@ops.ietf.org
Subject: Re: [idn] Update Charter revision 2
References: <030701c15c37$e463d8b0$1401000a@jamessonyvaio> <20011024124949X.yone@po.ntts.co.jp> <006701c15c94$2efd4530$1501000a@jamessonyvaio>
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-----

James Seng/Personal wrote:
> 
> > - There is no target for 'Requirements' in milestone.  I think it
> >   should be.
> 
> It is already move forward for IESG action. it is technically out of the
> hand of the wg.

Nonsense. There has been no Last Call. I made comments on the draft that
have not been adequately addressed (in fact none of my technical points
were addressed at all). Until the end of the Last Call period, the document
certainly isn't "out of the hands of the WG".

It is worth pointing out that:

 - IDNA does not satisfy requirements 11 (since it allows unassigned
   codepoints in queries without versioning) and 18 (since it allows
   more than one representation of a name, differing in case),

 - no solution that requires changes to the DNS protocol can satisfy
   requirement 1,

 - no solution that uses both ACE and transparent representations can
   satisify requirement 18.

IMHO there is little point in publishing a document specifying
requirements that are unachievable.


Here are my comments again, and hopefully we can have some substantive
technical discussion of them this time.

- -----

The original (-08) document is quoted using '>', and my suggested changes
are quoted using '=>'.

> 6. A transfer encoding syntax (TES) is a reversible transform of encoded
>    data which may (or may not) include textual data represented in
>    one or more character encoding schemes. Examples: 8bit,
>    Quoted-Printable, BASE64, UTF-7 (defunct), UTF-5, and RACE.

This definition is never used.

> ... This document attempts to
> set requirements for an equivalent of the "used services" given above,
> where "hostname" is replaced by "Internationalized Domain Name". This
> does not preclude the fact that IDN should work with any kind of DNS
> queries. IDN is a new service. Since existing protocols like SMTP or
> HTTP use the old service, it is a matter of great concern how the new
> and old services work together, and how other protocols can take
> advantage of the new service.

IDN is not a new service; it makes more sense to consider it as an
extension of all the existing services. For example, in IDNA, the
existing IP-to-hostname service can return an (ACE-encoded) IDN, or a
non-IDN query can follow a DNAME record that points to an IDN. These
cases wouldn't be possible if IDN was a separate service.

=> ... This document attempts to
=> set requirements for extensions of the "used services" given above,
=> where "hostname" is replaced by "Internationalized Domain Name".
=> That is, IDN should work with any kind of DNS queries. Since we are
=> extending services used by existing protocols like SMTP or HTTP,
=> compatibility with these existing uses is a matter of great concern,
=> as well as how both new and old protocols can take advantage of the
=> new facilities.


> 2. General Requirements
> 
> These requirements address two concerns: The service offered to the
> users (the application service), and the protocol extensions, if needed,
> added to support this service.
> 
> In the requirements, we attempt to use the term "service" whenever a
> requirement concerns the service, and "protocol" whenever a requirement
> is believed to constrain the possible implementation.

What we are setting requirements for are IDN proposals. Some (not all)
of the cases where "service" or "protocol" is used should actually say
"proposal", IMHO. I've made those changes below without further comment.


> [1] The DNS is essential to the entire Internet. Therefore, the service
> MUST NOT damage present DNS protocol interoperability. It MUST make the
> minimum number of changes to existing protocols on all layers of the
> stack.

Requiring the "minimum number of changes" fails to consider the cost
or feasibility of any change; it is requiring an absolute, which is
always a bad idea.

I.e. if proposal B needs protocol changes in addition to those of proposal
A, then no matter how insignificant the cost of those changes are, or what
other advantages B has, this requirement would eliminate B. The effect is
that minimising protocol changes overrides every other consideration.

> It MUST continue to allow any system anywhere that implements
> the IDN specification to resolve any internationalized domain name.

"continue to" should be deleted. Obviously no system can resolve an IDN
at the moment.

=> [1] The DNS is essential to the entire Internet. Therefore, the proposal
=> MUST NOT damage present DNS protocol interoperability. It MUST allow any
=> system anywhere that implements the IDN specification to resolve any
=> internationalized domain name. The overall cost and feasibility of
=> changes to existing protocols, on all layers of the stack, is of great
=> importance when evaluating any IDN proposal.


> [3] The DNS protocol (the packet formats that go on the wire) MUST
> NOT limit the codepoints that can be used. A service defined on top of
> the DNS, for instance the IDN-to-address function, MAY limit the
> codepoints that can be used. The service descriptions MUST describe
> what limitations are imposed.

The packet formats that go on the wire use octet strings, not strings
of codepoints. In order to maintain compatibility with the requirements
of RFC 2181, it is the set of octet strings that must not be limited.

Also, there may be other restrictions on host names besides the set of
allowed codepoints (for example relating to mixing of left-to-right and
right-to-left scripts, or names that start with an ACE prefix).

=> [3] The DNS protocol (the packet formats that go on the wire) MUST
=> NOT limit, apart from in length, the set of octet strings that can be
=> used as an encoded domain name. A service defined on top of the DNS,
=> for instance the IDN-to-address function, MUST define a mapping between
=> host name strings and these octet string encodings, and MAY impose
=> limitations on host names, for example by restricting the set of
=> allowed codepoints. The service descriptions MUST describe what
=> limitations are imposed.


> [4] The protocol MUST work for all features of DNS, IPv4, and
> IPv6. The protocol MUST NOT allow an IDN to be returned to a requestor
> that requests the IP-to-(old)-domain-name mapping service.

This is unclear. Returning an ACE name to an "old" requestor will
clearly not break anything, and an ACE name is an (encoded) IDN. It also
doesn't take into account that some resolver interfaces are already
Unicode-aware, in which case they would not require any distinction
between old and new requests (this is true for InetAddress.getHostName
in the Java API, for example, or for getipnodebyaddr, etc. in Plan-9).

=> [4] The proposal MUST work for all features of DNS, IPv4, and IPv6.
=> The proposal MUST ensure that the responses to requests for an IP
=> to domain name mapping will not break existing requestors.


> [5] The same name resolution request MUST generate the same response,
> regardless of the location or localization settings in the resolver, in
> the master server, and in any slave servers involved in the resolution
> process.

This is also unclear (with respect to the resolver; I agree about the
rest). Surely it wasn't meant to prohibit any use of locale information
in defining the API to the resolver?

=> [5] The same name resolution request MUST generate the same response,
=> regardless of the location or localization settings in the master
=> server, or in any slave servers involved in the resolution process.
=> Any description of functionality required of a resolver API MUST
=> discuss any dependency of the API on localization settings in the
=> client.


> [8] The service MAY modify the DNS protocol RFC 1035 and other related
> work undertaken by the DNSEXT WG. However, these changes SHOULD be as
> small as possible and any changes SHOULD be coordinated with the
> DNSEXT WG.

"As small as possible" is too strong - it is possible to support IDNs
without changing the DNS/DNSEXT protocol at all, and so this is equivalent
to "the DNS/DNSEXT protocol SHOULD NOT be changed". Nevertheless, changing
it may have advantages.

=> [8] The proposal MAY modify the DNS protocol RFC 1035 and other related
=> work undertaken by the DNSEXT WG. However, any such changes SHOULD be as
=> small as needed to support the basic design of the proposal, and SHOULD
=> be coordinated with the DNSEXT WG.


> [9] The protocol supporting the service SHOULD be as simple as possible
> from the user's perspective. Ideally, users SHOULD NOT realize that IDN
> was added on to the existing DNS.

A better way of expressing this is

=> [9] The user's perspective of each service SHOULD be as simple as can
=> be practically achieved. Ideally, users will find the services no more
=> difficult to use than if internationalised names had always been
=> supported by the DNS.


> [11] The protocol should handle with care new revisions of the CCS.
> Undefined codepoints should not be allowed unless a new revision of
> the protocol can handle it. Protocol revisions should be tagged.

The current version of nameprep allows unassigned code points in queries
without revision tagging, for good reasons.

=> [11] The proposal should handle with care new revisions of the CCS.
=> Proposals MUST discuss how undefined codepoints are handled.


> [12] Internationalized characters MUST be allowed to be represented and
> used in DNS names and records. The protocol MUST specify what charset is
> used when resolving domain names and how characters are encoded in DNS
> records.

Note that "charset" usually means a MIME-registered charset, which is
not necessarily the case here (for example when the encoding is ACE, or
when more than one possible encoding is allowed - see [18] below).

In fact the modified version of [3] above requires the mapping between
host names and the octet strings used on the wire to be specified (and
in any case, not doing this would be a violation of BCP 18), so the
second sentence is now redundant.

=> [12] Internationalized characters MUST be allowed to be represented and
=> used in DNS names and records.


[14], [15], [16], [17]: protocol -> proposal.


> [18] While there are a wide range of devices that use the DNS and a
> wide range of characteristics of international scripts and methods of
> domain name input and display, IDN is only concerned with the
> protocol. Therefore, there MUST be a single way of encoding an
> internationalized domain name within the DNS.

No, there does not need to be a single way of encoding an IDN (there is
not even for pure ASCII names, because equivalent names that differ in
case are allowed in the DNS protocol). For example, a solution where
names on the wire can be either ACE or UTF-8 will work perfectly well.
The wire encoding isn't even directly visible to users or applications,
so I don't see why the requirements document should be saying anything
about it.

If the intention was to refer to the external representation of a name,
rather than the wire encoding, that would prohibit any solution that
involves a transition from ACE to transparent names, or simultaneous use
of ACE and transparent names. Either way, this requirement is unnecessary
and should be deleted.


> [19] To achieve interoperability, canonicalization MUST be done at a
> single well-defined place in the DNS resolution process. The protocol
> MUST specify canonicalization; it MUST specify exactly where in the
> DNS that canonicalization happens and does not happen; it MUST specify
> how additions to ISO 10646 will affect the stability of the DNS and
> the amount of work done on the root DNS servers.

The overspecification here is "at a *single* ... place". For example,
if canonicalization is specified by nameprep, it is idempotent, i.e.
nameprep(nameprep(x)) = x. So doing it more than once only hurts
efficiency, not interoperability or any other requirement. It doesn't
even hurt efficiency very much, since the common case where a name is
already in the correct form can be optimised.

> ... The protocol MUST specify canonicalization; ...

This is meaningless without specifying what the goal of canonicalization
is. The minimum requirement is to ensure that characters that are
indistinguishable to users are treated the same, and so that is what
should be stated:

=> [19] Characters that appear absolutely indistinguishable to users
=> MUST be canonicalized. To achieve interoperability, canonicalization
=> MUST be done at a well-defined place or places in the DNS resolution
=> process, i.e. the proposal MUST specify exactly where in the DNS
=> canonicalization can and cannot happen.

[I changed "happens and does not happen" to "can and cannot happen",
because whether a particular piece of the infrastructure actually does
canonicalization will depend on which pieces have been upgraded. If they
haven't been upgraded, then they obviously won't do canonicalization,
regardless of whether the IDN proposal says that they should.
Note that this is a potential motivation for a proposal to specify that
canonicalization may be done in more than one place.]


> [23] If other canonicalization is done, it MUST be done before the
> domain name is resolved.

It makes perfect sense to do canonicalization as part of resolution, not
before it. Also, canonicalizing after resolution is certainly feasible,
even if it is inefficient.

> ... Further, the canonicalization MUST be easily
> upgradable as new languages and writing systems are added.

It *will not* be easy to upgrade canonicalization, no matter where or how
it is done, because the incentive to upgrade to support scripts that most
people will consider completely obscure, is much less than the incentive
to get IDN support working the first time round.

=> [23] Consideration MUST be given to the ease of upgrading
=> canonicalization as new languages and writing systems are added.
=> As long as a name containing new characters has been canonicalized
=> according to the latest canonicalization version, resolving that name
=> MUST NOT depend on further upgrades to the resolver or DNS servers.


> [25] If the charset can be normalized, then it SHOULD be normalized
> before it is used in IDN. Normalization SHOULD follow Unicode
> Technical Report #15.

Although this describes a perfectly reasonable approach, it does not
belong in a requirements document. [26] already captures part of the
requirement ("The protocol SHOULD avoid inventing a new normalization
form provided a technically sufficient one is available."), and the
modified [19] above captures the rest. So, delete this requirement.


[29]: service -> proposal.
[30]: protocol -> proposal.


> 3. Security Considerations
> 
> Any solution that meets the requirements in this document MUST NOT be
> less secure than the current DNS.

That is not necessarily achievable. The main issue is name spoofing using
look-alike characters: even if a proposal specifically tries to address
that (by registration procedures, for example), it can't absolutely
guarantee that there will not be cases of this that rely on IDNs.

> Specifically, the mapping of
> internationalized host names to and from IP addresses MUST have the
> same characteristics as the mapping of today's host names.
> 
> Specifying requirements for internationalized domain names does not
> itself raise any new security issues. However, any change to the DNS MAY
> affect the security of any protocol that relies on the DNS or on
> DNS names. A thorough evaluation of those protocols for security
> concerns will be needed when they are developed.

That evaluation is needed for existing protocols, not just new protocols.

- -- 
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

iQEVAwUBO9e+oDkCAxeYt5gVAQEOCgf8Dgk0sC/8cl1ltpRRy/CZKwSdj4Cs89EV
tRqu4+DOBRBRE5x0s1ZkQKxCx2VjKu2fJ73lHLDsqiWgwolfOlO0cx4iovfpempy
K2yPytC+n37yUjaxX3iTJYe48KNuozldNjdtV1F4SXQCbKfNRDQhHVqQj/2CTzCy
PNYPTZpcFoL/gXLJ94QyBCAH24EIS7n3FuAY0rDt3IWyG1Lbdkr1SkpDzf7iToji
msuMl00YOn6u1TL3DO9qBBzejHVav5Bpw9L/NXGEIgtjZl1ShPgLRwFBztLC0IrV
lewoJInjswf4sCXW2yEBOeyZq99pzQ1FLZpwTdkXf4zkm2nHOSn+Wg==
=FDVk
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Thu Oct 25 04:44:18 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11775
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 04:44:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wfun-000Ghx-00
	for idn-data@psg.com; Thu, 25 Oct 2001 01:31:01 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wfum-000Ghp-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 01:31:00 -0700
Received: from [192.168.1.5] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id KAA22607;
	Thu, 25 Oct 2001 10:30:06 +0200 (MET DST)
Date: Thu, 25 Oct 2001 10:08:48 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Martin Duerst <duerst@w3.org>, "James Seng/Personal" <jseng@pobox.org.sg>,
        idn@ops.ietf.org
Subject: Re: [idn] (bias) summary of reordering discussion
Message-ID: <7792146.1004004528@localhost>
In-Reply-To: <4.2.0.58.J.20011025124759.068cb6a0@localhost>
References: <011701c15be0$4473db90$dd00a8c0@jamessonyvaio>
 <011701c15be0$4473db90$dd00a8c0@jamessonyvaio>
 <4.2.0.58.J.20011025124759.068cb6a0@localhost>
X-Mailer: Mulberry/2.1.1 (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-10-25 12.54 +0900 Martin Duerst <duerst@w3.org> wrote:

> At 19:41 01/10/23 +0200, Patrik F$BgM(Btstr$B?N(B wrote:
> 
>> o Nameprep mappings is defined by UTC, not IETF.
>>   -> I am nervous when we in IETF talk about these things
> 
> The main mappings used by nameprep (casemapping and normalization)
> are defined by the UTC. But it is IETF that chooses which mappings
> to select (e.g. NFC vs. NFKC), it is IETF that may request other
> mappings to be created (NFC was created based on a request by W3C,
> an additional file was added to help IETF with case mapping,
> a (tentative, implicit) request for TC/SC mappings was turned down).
> 
> Also, nameprep contains a few additional mappings and prohibitions
> that are motivated by the specific situation of domain names,
> without taking these from anywhere.

You are correct, but I am still nervous.

   paf




From owner-idn@ops.ietf.org  Thu Oct 25 04:52:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11827
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 04:52:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wg98-000Gxm-00
	for idn-data@psg.com; Thu, 25 Oct 2001 01:45:50 -0700
Received: from smtp14.singnet.com.sg ([165.21.6.34])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wg97-000Gxe-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 01:45:49 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp14.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9P8hx414155;
	Thu, 25 Oct 2001 16:43:59 +0800
Message-ID: <008001c15d31$6b2a9ce0$1701000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
References: <030701c15c37$e463d8b0$1401000a@jamessonyvaio> <20011024124949X.yone@po.ntts.co.jp> <006701c15c94$2efd4530$1501000a@jamessonyvaio> <3BD7C0A0.86D101CE@zetnet.co.uk>
Subject: Re: [idn] Update Charter revision 2
Date: Thu, 25 Oct 2001 16:45:35 +0800
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.4807.1700
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Nonsense. There has been no Last Call. I made comments on the draft
that

Last Call is norm but not neccessary. It was agreed on London meeting to
move forward the doc since there is no comments or any changes proposed

> have not been adequately addressed (in fact none of my technical
points
> were addressed at all).

Your comments comes after the doc have been moved forward for IESG. Any
changes to it will have to wait after their review.

-James Seng




From owner-idn@ops.ietf.org  Thu Oct 25 04:55:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11897
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 04:55:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wg8b-000GxN-00
	for idn-data@psg.com; Thu, 25 Oct 2001 01:45:17 -0700
Received: from mercury.sun.com ([192.9.25.1])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wg8b-000GxG-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 01:45:17 -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 BAA20340;
	Thu, 25 Oct 2001 01:45:13 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f9P8jBq16196;
	Thu, 25 Oct 2001 10:45:11 +0200 (MET DST)
Date: Thu, 25 Oct 2001 10:39:32 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [idn] Update Charter revision 2
To: David Hopwood <david.hopwood@zetnet.co.uk>
Cc: James Seng/Personal <jseng@pobox.org.sg>, idn@ops.ietf.org
In-Reply-To: "Your message with ID" <3BD7C0A0.86D101CE@zetnet.co.uk>
Message-ID: <Roam.SIMC.2.0.6.1003999172.29378.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-LA_F631619425R-2A-1003999172=:100516NCE.IlHAFeR"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

---LA_F631619425R-2A-1003999172=:100516NCE.IlHAFeR
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII

> -----BEGIN PGP SIGNED MESSAGE-----
> 
> James Seng/Personal wrote:
> > 
> > > - There is no target for 'Requirements' in milestone.  I think it
> > >   should be.
> > 
> > It is already move forward for IESG action. it is technically out of the
> > hand of the wg.
> 
> Nonsense. There has been no Last Call. I made comments on the draft that
> have not been adequately addressed (in fact none of my technical points
> were addressed at all). Until the end of the Last Call period, the document
> certainly isn't "out of the hands of the WG".

David,

there was a WG last call on the document on the mailing list in February - see 
the attached email.

Based on this last call the chairs forwarded the requirements document
to us ADs on Oct 2. But as James later clarified this doesn't mean that
folks can't continue to discuss the document - it just means that the
chairs concluded there was rough consensus in the WG for moving the document
to the next step.

The process moving forward is that the ADs (Thomas and I) will read
the document to determine whether it is ready for IETF wide last call.
While we haven't completeled this yet it is very likely to result in
feedback to the WG that the document needs to be clarified.

So I'd urge other to participate in continued discussion on the requirements
document to make it clear and concise and also to verify that the solution(s)
that the WG are working on indeed match the requirements. (If they don't
either the requirements or the solution(s) need to be fixed.)

   Erik

> It is worth pointing out that:
> 
>  - IDNA does not satisfy requirements 11 (since it allows unassigned
>    codepoints in queries without versioning) and 18 (since it allows
>    more than one representation of a name, differing in case),
> 
>  - no solution that requires changes to the DNS protocol can satisfy
>    requirement 1,
> 
>  - no solution that uses both ACE and transparent representations can
>    satisify requirement 18.
> 
> IMHO there is little point in publishing a document specifying
> requirements that are unachievable.
> 
> 
> Here are my comments again, and hopefully we can have some substantive
> technical discussion of them this time.
> 
> - -----
> 
> The original (-08) document is quoted using '>', and my suggested changes
> are quoted using '=>'.
> 
> > 6. A transfer encoding syntax (TES) is a reversible transform of encoded
> >    data which may (or may not) include textual data represented in
> >    one or more character encoding schemes. Examples: 8bit,
> >    Quoted-Printable, BASE64, UTF-7 (defunct), UTF-5, and RACE.
> 
> This definition is never used.
> 
> > ... This document attempts to
> > set requirements for an equivalent of the "used services" given above,
> > where "hostname" is replaced by "Internationalized Domain Name". This
> > does not preclude the fact that IDN should work with any kind of DNS
> > queries. IDN is a new service. Since existing protocols like SMTP or
> > HTTP use the old service, it is a matter of great concern how the new
> > and old services work together, and how other protocols can take
> > advantage of the new service.
> 
> IDN is not a new service; it makes more sense to consider it as an
> extension of all the existing services. For example, in IDNA, the
> existing IP-to-hostname service can return an (ACE-encoded) IDN, or a
> non-IDN query can follow a DNAME record that points to an IDN. These
> cases wouldn't be possible if IDN was a separate service.
> 
> => ... This document attempts to
> => set requirements for extensions of the "used services" given above,
> => where "hostname" is replaced by "Internationalized Domain Name".
> => That is, IDN should work with any kind of DNS queries. Since we are
> => extending services used by existing protocols like SMTP or HTTP,
> => compatibility with these existing uses is a matter of great concern,
> => as well as how both new and old protocols can take advantage of the
> => new facilities.
> 
> 
> > 2. General Requirements
> > 
> > These requirements address two concerns: The service offered to the
> > users (the application service), and the protocol extensions, if needed,
> > added to support this service.
> > 
> > In the requirements, we attempt to use the term "service" whenever a
> > requirement concerns the service, and "protocol" whenever a requirement
> > is believed to constrain the possible implementation.
> 
> What we are setting requirements for are IDN proposals. Some (not all)
> of the cases where "service" or "protocol" is used should actually say
> "proposal", IMHO. I've made those changes below without further comment.
> 
> 
> > [1] The DNS is essential to the entire Internet. Therefore, the service
> > MUST NOT damage present DNS protocol interoperability. It MUST make the
> > minimum number of changes to existing protocols on all layers of the
> > stack.
> 
> Requiring the "minimum number of changes" fails to consider the cost
> or feasibility of any change; it is requiring an absolute, which is
> always a bad idea.
> 
> I.e. if proposal B needs protocol changes in addition to those of proposal
> A, then no matter how insignificant the cost of those changes are, or what
> other advantages B has, this requirement would eliminate B. The effect is
> that minimising protocol changes overrides every other consideration.
> 
> > It MUST continue to allow any system anywhere that implements
> > the IDN specification to resolve any internationalized domain name.
> 
> "continue to" should be deleted. Obviously no system can resolve an IDN
> at the moment.
> 
> => [1] The DNS is essential to the entire Internet. Therefore, the proposal
> => MUST NOT damage present DNS protocol interoperability. It MUST allow any
> => system anywhere that implements the IDN specification to resolve any
> => internationalized domain name. The overall cost and feasibility of
> => changes to existing protocols, on all layers of the stack, is of great
> => importance when evaluating any IDN proposal.
> 
> 
> > [3] The DNS protocol (the packet formats that go on the wire) MUST
> > NOT limit the codepoints that can be used. A service defined on top of
> > the DNS, for instance the IDN-to-address function, MAY limit the
> > codepoints that can be used. The service descriptions MUST describe
> > what limitations are imposed.
> 
> The packet formats that go on the wire use octet strings, not strings
> of codepoints. In order to maintain compatibility with the requirements
> of RFC 2181, it is the set of octet strings that must not be limited.
> 
> Also, there may be other restrictions on host names besides the set of
> allowed codepoints (for example relating to mixing of left-to-right and
> right-to-left scripts, or names that start with an ACE prefix).
> 
> => [3] The DNS protocol (the packet formats that go on the wire) MUST
> => NOT limit, apart from in length, the set of octet strings that can be
> => used as an encoded domain name. A service defined on top of the DNS,
> => for instance the IDN-to-address function, MUST define a mapping between
> => host name strings and these octet string encodings, and MAY impose
> => limitations on host names, for example by restricting the set of
> => allowed codepoints. The service descriptions MUST describe what
> => limitations are imposed.
> 
> 
> > [4] The protocol MUST work for all features of DNS, IPv4, and
> > IPv6. The protocol MUST NOT allow an IDN to be returned to a requestor
> > that requests the IP-to-(old)-domain-name mapping service.
> 
> This is unclear. Returning an ACE name to an "old" requestor will
> clearly not break anything, and an ACE name is an (encoded) IDN. It also
> doesn't take into account that some resolver interfaces are already
> Unicode-aware, in which case they would not require any distinction
> between old and new requests (this is true for InetAddress.getHostName
> in the Java API, for example, or for getipnodebyaddr, etc. in Plan-9).
> 
> => [4] The proposal MUST work for all features of DNS, IPv4, and IPv6.
> => The proposal MUST ensure that the responses to requests for an IP
> => to domain name mapping will not break existing requestors.
> 
> 
> > [5] The same name resolution request MUST generate the same response,
> > regardless of the location or localization settings in the resolver, in
> > the master server, and in any slave servers involved in the resolution
> > process.
> 
> This is also unclear (with respect to the resolver; I agree about the
> rest). Surely it wasn't meant to prohibit any use of locale information
> in defining the API to the resolver?
> 
> => [5] The same name resolution request MUST generate the same response,
> => regardless of the location or localization settings in the master
> => server, or in any slave servers involved in the resolution process.
> => Any description of functionality required of a resolver API MUST
> => discuss any dependency of the API on localization settings in the
> => client.
> 
> 
> > [8] The service MAY modify the DNS protocol RFC 1035 and other related
> > work undertaken by the DNSEXT WG. However, these changes SHOULD be as
> > small as possible and any changes SHOULD be coordinated with the
> > DNSEXT WG.
> 
> "As small as possible" is too strong - it is possible to support IDNs
> without changing the DNS/DNSEXT protocol at all, and so this is equivalent
> to "the DNS/DNSEXT protocol SHOULD NOT be changed". Nevertheless, changing
> it may have advantages.
> 
> => [8] The proposal MAY modify the DNS protocol RFC 1035 and other related
> => work undertaken by the DNSEXT WG. However, any such changes SHOULD be as
> => small as needed to support the basic design of the proposal, and SHOULD
> => be coordinated with the DNSEXT WG.
> 
> 
> > [9] The protocol supporting the service SHOULD be as simple as possible
> > from the user's perspective. Ideally, users SHOULD NOT realize that IDN
> > was added on to the existing DNS.
> 
> A better way of expressing this is
> 
> => [9] The user's perspective of each service SHOULD be as simple as can
> => be practically achieved. Ideally, users will find the services no more
> => difficult to use than if internationalised names had always been
> => supported by the DNS.
> 
> 
> > [11] The protocol should handle with care new revisions of the CCS.
> > Undefined codepoints should not be allowed unless a new revision of
> > the protocol can handle it. Protocol revisions should be tagged.
> 
> The current version of nameprep allows unassigned code points in queries
> without revision tagging, for good reasons.
> 
> => [11] The proposal should handle with care new revisions of the CCS.
> => Proposals MUST discuss how undefined codepoints are handled.
> 
> 
> > [12] Internationalized characters MUST be allowed to be represented and
> > used in DNS names and records. The protocol MUST specify what charset is
> > used when resolving domain names and how characters are encoded in DNS
> > records.
> 
> Note that "charset" usually means a MIME-registered charset, which is
> not necessarily the case here (for example when the encoding is ACE, or
> when more than one possible encoding is allowed - see [18] below).
> 
> In fact the modified version of [3] above requires the mapping between
> host names and the octet strings used on the wire to be specified (and
> in any case, not doing this would be a violation of BCP 18), so the
> second sentence is now redundant.
> 
> => [12] Internationalized characters MUST be allowed to be represented and
> => used in DNS names and records.
> 
> 
> [14], [15], [16], [17]: protocol -> proposal.
> 
> 
> > [18] While there are a wide range of devices that use the DNS and a
> > wide range of characteristics of international scripts and methods of
> > domain name input and display, IDN is only concerned with the
> > protocol. Therefore, there MUST be a single way of encoding an
> > internationalized domain name within the DNS.
> 
> No, there does not need to be a single way of encoding an IDN (there is
> not even for pure ASCII names, because equivalent names that differ in
> case are allowed in the DNS protocol). For example, a solution where
> names on the wire can be either ACE or UTF-8 will work perfectly well.
> The wire encoding isn't even directly visible to users or applications,
> so I don't see why the requirements document should be saying anything
> about it.
> 
> If the intention was to refer to the external representation of a name,
> rather than the wire encoding, that would prohibit any solution that
> involves a transition from ACE to transparent names, or simultaneous use
> of ACE and transparent names. Either way, this requirement is unnecessary
> and should be deleted.
> 
> 
> > [19] To achieve interoperability, canonicalization MUST be done at a
> > single well-defined place in the DNS resolution process. The protocol
> > MUST specify canonicalization; it MUST specify exactly where in the
> > DNS that canonicalization happens and does not happen; it MUST specify
> > how additions to ISO 10646 will affect the stability of the DNS and
> > the amount of work done on the root DNS servers.
> 
> The overspecification here is "at a *single* ... place". For example,
> if canonicalization is specified by nameprep, it is idempotent, i.e.
> nameprep(nameprep(x)) = x. So doing it more than once only hurts
> efficiency, not interoperability or any other requirement. It doesn't
> even hurt efficiency very much, since the common case where a name is
> already in the correct form can be optimised.
> 
> > ... The protocol MUST specify canonicalization; ...
> 
> This is meaningless without specifying what the goal of canonicalization
> is. The minimum requirement is to ensure that characters that are
> indistinguishable to users are treated the same, and so that is what
> should be stated:
> 
> => [19] Characters that appear absolutely indistinguishable to users
> => MUST be canonicalized. To achieve interoperability, canonicalization
> => MUST be done at a well-defined place or places in the DNS resolution
> => process, i.e. the proposal MUST specify exactly where in the DNS
> => canonicalization can and cannot happen.
> 
> [I changed "happens and does not happen" to "can and cannot happen",
> because whether a particular piece of the infrastructure actually does
> canonicalization will depend on which pieces have been upgraded. If they
> haven't been upgraded, then they obviously won't do canonicalization,
> regardless of whether the IDN proposal says that they should.
> Note that this is a potential motivation for a proposal to specify that
> canonicalization may be done in more than one place.]
> 
> 
> > [23] If other canonicalization is done, it MUST be done before the
> > domain name is resolved.
> 
> It makes perfect sense to do canonicalization as part of resolution, not
> before it. Also, canonicalizing after resolution is certainly feasible,
> even if it is inefficient.
> 
> > ... Further, the canonicalization MUST be easily
> > upgradable as new languages and writing systems are added.
> 
> It *will not* be easy to upgrade canonicalization, no matter where or how
> it is done, because the incentive to upgrade to support scripts that most
> people will consider completely obscure, is much less than the incentive
> to get IDN support working the first time round.
> 
> => [23] Consideration MUST be given to the ease of upgrading
> => canonicalization as new languages and writing systems are added.
> => As long as a name containing new characters has been canonicalized
> => according to the latest canonicalization version, resolving that name
> => MUST NOT depend on further upgrades to the resolver or DNS servers.
> 
> 
> > [25] If the charset can be normalized, then it SHOULD be normalized
> > before it is used in IDN. Normalization SHOULD follow Unicode
> > Technical Report #15.
> 
> Although this describes a perfectly reasonable approach, it does not
> belong in a requirements document. [26] already captures part of the
> requirement ("The protocol SHOULD avoid inventing a new normalization
> form provided a technically sufficient one is available."), and the
> modified [19] above captures the rest. So, delete this requirement.
> 
> 
> [29]: service -> proposal.
> [30]: protocol -> proposal.
> 
> 
> > 3. Security Considerations
> > 
> > Any solution that meets the requirements in this document MUST NOT be
> > less secure than the current DNS.
> 
> That is not necessarily achievable. The main issue is name spoofing using
> look-alike characters: even if a proposal specifically tries to address
> that (by registration procedures, for example), it can't absolutely
> guarantee that there will not be cases of this that rely on IDNs.
> 
> > Specifically, the mapping of
> > internationalized host names to and from IP addresses MUST have the
> > same characteristics as the mapping of today's host names.
> > 
> > Specifying requirements for internationalized domain names does not
> > itself raise any new security issues. However, any change to the DNS MAY
> > affect the security of any protocol that relies on the DNS or on
> > DNS names. A thorough evaluation of those protocols for security
> > concerns will be needed when they are developed.
> 
> That evaluation is needed for existing protocols, not just new protocols.
> 
> - -- 
> 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
> 
> iQEVAwUBO9e+oDkCAxeYt5gVAQEOCgf8Dgk0sC/8cl1ltpRRy/CZKwSdj4Cs89EV
> tRqu4+DOBRBRE5x0s1ZkQKxCx2VjKu2fJ73lHLDsqiWgwolfOlO0cx4iovfpempy
> K2yPytC+n37yUjaxX3iTJYe48KNuozldNjdtV1F4SXQCbKfNRDQhHVqQj/2CTzCy
> PNYPTZpcFoL/gXLJ94QyBCAH24EIS7n3FuAY0rDt3IWyG1Lbdkr1SkpDzf7iToji
> msuMl00YOn6u1TL3DO9qBBzejHVav5Bpw9L/NXGEIgtjZl1ShPgLRwFBztLC0IrV
> lewoJInjswf4sCXW2yEBOeyZq99pzQ1FLZpwTdkXf4zkm2nHOSn+Wg==
> =FDVk
> -----END PGP SIGNATURE-----
> 


---LA_F631619425R-2A-1003999172=:100516NCE.IlHAFeR
Content-Type: MESSAGE/rfc822; name=message-file
Content-Description: mail-message

Date: Tue, 13 Feb 2001 09:27:56 -0500
To: idn@ops.ietf.org
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: [idn] W.G. Last Call on "Requirements of Internationalized Domain
  Names"
MIME-Version: 1.0

This is a idn working group last call for comments on advancing the 
following document as a Informational RFC:

  	Title		: Requirements of Internationalized Domain Names
  	Author(s)	: Editors Zita Wenzel, James Seng
  	Filename	: 
http://www.ietf.org/internet-drafts/draft-ietf-idn-requirements-04.txt

Please send substantive comments to the idn mailing list, and minor
editorial comments to the authors.  This last call period will end two
week from today on February 28th, 2001.

Marc Blanchet and James Seng

(PS. stolen wg last call template from Bob Hinden, for those who recognize 
it...)

Marc Blanchet
Viagénie inc.
tel: 418-656-9254
http://www.viagenie.qc.ca

----------------------------------------------------------
Normos (http://www.normos.org): Internet standards portal:
IETF RFC, drafts, IANA, W3C, ATMForum, ISO, ... all in one place.




---LA_F631619425R-2A-1003999172=:100516NCE.IlHAFeR--



From owner-idn@ops.ietf.org  Thu Oct 25 05:07:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12050
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 05:07:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wgI4-000H9T-00
	for idn-data@psg.com; Thu, 25 Oct 2001 01:55:04 -0700
Received: from mercury.sun.com ([192.9.25.1])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wgI3-000H9I-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 01:55:03 -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 BAA23252;
	Thu, 25 Oct 2001 01:55:01 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f9P8sxq17307;
	Thu, 25 Oct 2001 10:54:59 +0200 (MET DST)
Date: Thu, 25 Oct 2001 10:49:20 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [idn] Update Charter revision 2
To: James Seng/Personal <jseng@pobox.org.sg>
Cc: David Hopwood <david.hopwood@zetnet.co.uk>, idn@ops.ietf.org
In-Reply-To: "Your message with ID" <008001c15d31$6b2a9ce0$1701000a@jamessonyvaio>
Message-ID: <Roam.SIMC.2.0.6.1003999760.18359.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


> > have not been adequately addressed (in fact none of my technical
> points
> > were addressed at all).
> 
> Your comments comes after the doc have been moved forward for IESG. Any
> changes to it will have to wait after their review.

The WG should discuss the comments and they can even decide how they'd like
to modify the document.
But it is best to not issue an updated I-D until the AD review comments 
are back.

  Erik




From owner-idn@ops.ietf.org  Thu Oct 25 05:30:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12311
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 05:30:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wgYS-000HST-00
	for idn-data@psg.com; Thu, 25 Oct 2001 02:12:00 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wgYR-000HSL-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 02:11:59 -0700
Received: from [192.168.1.5] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id LAA02369;
	Thu, 25 Oct 2001 11:11:30 +0200 (MET DST)
Date: Thu, 25 Oct 2001 11:10:58 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Yves Arrouye <yves@realnames.com>, "'Martin Duerst'" <duerst@w3.org>,
        Soobok Lee <lsb@postel.co.kr>,
        David Hopwood <david.hopwood@zetnet.co.uk>, idn@ops.ietf.org
Subject: RE: [idn] Re: stringprep and unassigned code points
Message-ID: <8015970.1004008258@localhost>
In-Reply-To: <7FC3066C236FD511BC5900508BAC86FE4D7DFD@trestles.internal.realnames.com>
References:  <7FC3066C236FD511BC5900508BAC86FE4D7DFD@trestles.internal.realna
 mes.com>
X-Mailer: Mulberry/2.1.1 (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-10-25 00.01 -0700 Yves Arrouye <yves@realnames.com> wrote:

> I have the same understanding you do re: when unassigned code points may
> be generated (by an application that gets code points from a version of
> Unicode that was released after the version of Nameprep it uses).

I must be extremely bad at expressing myself. This is now the third time
since monday I explain how things work.

> Now
> let's suppose Unicode encodes something new, for which a new Nameprep is
> released (because some additions to the mapping table are needed).

A mapping can only be from an earlier unassigned codepoint.

> At
> this point, the DNS servers may contain the ACE(Nameprep(names in this
> new thing)).

ACE have absolutely nothing to do with this. This is a stringprep issue.

Only nameservers which do understand the new version of stringprep can have
these names.

> And applications get these new codepoints,

What do you mean by "get these new codepoints"?

> but because they
> do not have the appropriate mapping table, they will pass ACE(Old
> Nameprep(names in this new thing))

No, because the codepoint is unassigned in old version of stringsprep, and
because of that MUST NOT be used.

> which will sometimes match the new
> labels, and sometimes not. Am I right in thinking that applications do
> not need to be updated only if Nameprep does not change for the new code
> points (looks like common sense anyway)?

You are wrong.

Summary (once again):

If a new version of Unicode comes out, which have a newly assigned
codepoint (X), and a mapping from X to Y, the following is true:

- X can not be part of the result of a nameprep which an old application
  creates. If an old application get X as input, the codepoint is unassigned
  and therefore illegal.
- If Y is an earlier assigned codepoint, an application understanding the
  new version of nameprep will when getting X map that to Y.
- If Y is a newly assigned codepoint, an application understanding the
  new version of nameprep will when getting X map that to Y.
- In neither case (old application or new application) X will be part of
  the output of the stringprep process.

         paf




From owner-idn@ops.ietf.org  Thu Oct 25 05:42:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12419
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 05:42:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wgtC-000HpM-00
	for idn-data@psg.com; Thu, 25 Oct 2001 02:33:26 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wgtB-000HpG-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 02:33:26 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 38F387F4A8; Thu, 25 Oct 2001 18:32:45 +0900 (JST)
Message-Id: <4.2.0.58.J.20011025182258.036b42e0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 25 Oct 2001 18:32:37 +0900
To: Yves Arrouye <yves@realnames.com>, "'idn@ops.ietf.org'" <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: RE: [idn] NFC vs NFKC
In-Reply-To: <7FC3066C236FD511BC5900508BAC86FE4D7DFF@trestles.internal.r
 ealnames.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 00:16 01/10/25 -0700, Yves Arrouye wrote:

> > > Yes. IDN is a new system, with the goal of being able to
> > > represent labels in a wide range of scripts. There is no
> > > need to allow artefacts of legacy character encodings,
> > > because IDN isn't designed to map existing names back
> > > and forth from other naming systems.
> >
> > So you do not think it is realistic, for example, to have a
> > document encoded in KS C 5601, containing domain names where
> > the labels would be written using non conjoining Jamo.

Hangul domain names in KS C 5601 would normally be encoded as
precombined syllables. KS C 5601 provides about 2300 of them,
the ones most often used. Users who want to used other Hangul
syllables won't use non-conjoining Jamo (compatibility Jamo),
because they will be displayed one Jamo at a time.

In the nameprep design team, we discussed some cases where users
might want to use sequences of independent consonant Jamo. There
are a few web pages with some examples of these, but not too many.
We are not sure whether they should be allowed in domain names or
not, and if they are, how they should be represented.


>[Edit] Is that because nobody uses these anymore, and so you would not
>expect a modern invention like IDN to appear in an anachronic way? Is that
>the case with all LEGACY characters?

I don't want IDN to carry unnecessary legacy compatibility
baggage. If it turns out that something really helps the user
(e.g. for the full-width Latin letters), I have nothing against
mapping them. But I don't think it's a good idea to map a
wholesale 3000, most of them not really used and very difficult
to type in, just to get a few dozen mapped the right way.
We can easily do the later without having to do the former.


Regards,   Martin.



From owner-idn@ops.ietf.org  Thu Oct 25 05:46:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12440
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 05:46:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wgyR-000HuP-00
	for idn-data@psg.com; Thu, 25 Oct 2001 02:38:51 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wgyQ-000HuJ-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 02:38:50 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VVVR6MPrrge3wJPpIMiWqGEw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GJLAM6VJ; Thu, 25 Oct 2001 05:38:18 EDT
To: duerst@w3.org
Cc: klensin@jck.com, idn@ops.ietf.org
Date: Thu, 25 Oct 2001 02:37:37 -0700
Subject: Re: [idn] An ignorant question about TC<-> SC
Message-ID: <20011025.023737.-360533.0.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.5
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana Ye <liana.ydisg@juno.com>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



On Thu, 25 Oct 2001 16:27:10 +0900 Martin Duerst <duerst@w3.org> writes:
> At 13:02 01/10/23 -0700, liana Ye wrote:
> 
> >  From screen display point view, TC/SC are different glyph
> >  sets(who defines the sets? How is it used by 1/5 of the world
> >population? Is Uicode group the only authoritive one? In
> >China there are over 600 recorded views on this).
> 
> The Han ideographs in Unicode/ISO 10646 are defined by the
> IRG (Ideographic Raporteur Group). This group reports to
> ISO/IEC SC2 WG2, the ISO WG responsible for ISO 10646.
> It is composed of representatives from all the countries
> or similar entities interested in Han ideographs. That
> includes China, Japan, Korea (both South and North), Taiwan,
> Hong Kong, Singapore, and the US (I hope I didn't forget
> anybody, and please excuse the maybe politically uncorrect
> shortcuts). The US is the only country represented without
> a tradition of using Han ideographs, but usually only
> sends a small delegation and mainly helps with wording.
> Many other countries may send rather large delegations
> (given the number of characters, which means a lot of
> work, this is no surprise). The Unicode consortium
> participates in the IRG with an observer status only.
> 
> The IRG has published guidelines for deciding when to
> unify two occurences and when not. Because of the very
> huge number of characters, there is in some cases indeed
> a thin line as to whether something should be unified or
> not. And in these cases, the IRG just has to make a decision.
> 
> Overall, the guidelines are somewhat difficult to understand
> at first, but they are designed mainly with a 'least surprise
> to the average user' in mind, and I think they have achieved
> this goal very well. The guidelines are based on earlier
> ones used for the Japanese standard.
> 
> The core of the guidelines says that if two characters look
> significantly different, then they are encoded with two codes
> even if they e.g. are one-to-one SC/TC equivalents. This is
> to avoid suddenly changing the appearance of letters for a
> user who may not be familiar with the significantly differently
> looking shape. On the other hand, cases where there is only
> a small difference in shape are unified (i.e. only one code)
> unless this small difference in shape makes an actual
> difference in meaning.
> 
> Overall, the results are so that if you present a text
> where you change the glyph shapes within the range that
> is unified, people who have done basic education but don't
> know about different shapes (e.g. people in Taiwan or
> Hong Kong who only know about TC, or people in China or
> Singapore who only know about SC, or people in Japan who
> only know about the forms used in Japan) will read over
> these changes without problems, and might at some points
> say 'this looks a bit strange', but will still identify
> the character.
> 
> There are some exceptions to these rule related to backwards-
> compatible roundtripping (source separation rule).
> 
> 
> Hope this helps,      Martin.

In another word, the fundimental work from UCS is the to table 
glyphs based on their visual distinction.  Then why this group 
get into the guide line work in normalization of characters? Why
they give advice such as "not put TC/SC into" another table 
for a different purpose?

Liana



From owner-idn@ops.ietf.org  Thu Oct 25 06:10:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12700
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 06:10:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15whHz-000IIo-00
	for idn-data@psg.com; Thu, 25 Oct 2001 02:59:03 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15whHy-000IIg-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 02:59:02 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0EJcmVjp3VVlUPQUZuU5L1IR/4AhcZD7A==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GJLBTKA8; Thu, 25 Oct 2001 05:58:43 EDT
To: paf@cisco.com
Cc: duerst@w3.org, jseng@pobox.org.sg, idn@ops.ietf.org
Date: Thu, 25 Oct 2001 02:57:03 -0700
Subject: Re: [idn] (bias) summary of reordering discussion
Message-ID: <20011025.025800.-360533.1.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.5
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-1,3-35
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana Ye <liana.ydisg@juno.com>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



On Thu, 25 Oct 2001 10:08:48 +0200 =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?=
<paf@cisco.com> writes:
> --On 01-10-25 12.54 +0900 Martin Duerst <duerst@w3.org> wrote:
> 
> > At 19:41 01/10/23 +0200, Patrik F$BgM(Btstr$B?N(B wrote:
> > 
> >> o Nameprep mappings is defined by UTC, not IETF.
> >>   -> I am nervous when we in IETF talk about these things
> > 
> > The main mappings used by nameprep (casemapping and normalization)
> > are defined by the UTC. But it is IETF that chooses which mappings
> > to select (e.g. NFC vs. NFKC), it is IETF that may request other
> > mappings to be created (NFC was created based on a request by W3C,
> > an additional file was added to help IETF with case mapping,
> > a (tentative, implicit) request for TC/SC mappings was turned 
> down).
> > 
> > Also, nameprep contains a few additional mappings and prohibitions
> > that are motivated by the specific situation of domain names,
> > without taking these from anywhere.
> 
> You are correct, but I am still nervous.
> 
>    paf
> 
> 

What if we define a frame and  make it possible to let any 
script to be mapped by their own user group, as long as 
the user group can come up with their agreement on how
to do the mapping. The [nameprep] is severing as example
of such mapping. BTW, is "PROFILE" have such meaning? 

Liana



From owner-idn@ops.ietf.org  Thu Oct 25 07:18:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13588
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 07:18:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wiHy-000JT9-00
	for idn-data@psg.com; Thu, 25 Oct 2001 04:03:06 -0700
Received: from smtp15.singnet.com.sg ([165.21.6.35])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wiHw-000JT2-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 04:03:05 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp15.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9PB0YN02673;
	Thu, 25 Oct 2001 19:00:34 +0800
Message-ID: <00d001c15d44$95d4b8f0$1701000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
Cc: "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
References: <Roam.SIMC.2.0.6.1003999760.18359.nordmark@bebop.france>
Subject: Re: [idn] Update Charter revision 2
Date: Thu, 25 Oct 2001 19:02:49 +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.4807.1700
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thanks Erik. Yes, that is what I mean.

Discussion of the points raised by David can and should continue.

But dont expect any update to the doc for a while.

-James Seng

----- Original Message -----
From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
To: "James Seng/Personal" <jseng@pobox.org.sg>
Cc: "David Hopwood" <david.hopwood@zetnet.co.uk>; <idn@ops.ietf.org>
Sent: Thursday, October 25, 2001 4:49 PM
Subject: Re: [idn] Update Charter revision 2


>
> > > have not been adequately addressed (in fact none of my technical
> > points
> > > were addressed at all).
> >
> > Your comments comes after the doc have been moved forward for IESG.
Any
> > changes to it will have to wait after their review.
>
> The WG should discuss the comments and they can even decide how they'd
like
> to modify the document.
> But it is best to not issue an updated I-D until the AD review
comments
> are back.
>
>   Erik
>




From owner-idn@ops.ietf.org  Thu Oct 25 11:25:21 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21528
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 11:25:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wm1Z-000OkL-00
	for idn-data@psg.com; Thu, 25 Oct 2001 08:02:25 -0700
Received: from [211.254.82.194] (helo=nexus.spsoft.co.kr)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wm1Y-000OkE-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 08:02:24 -0700
Received: (from newcat@localhost)
	by nexus.spsoft.co.kr (8.10.0/8.10.0) id f9PF2Cx01459
	for idn@ops.ietf.org; Fri, 26 Oct 2001 00:02:12 +0900
Date: Fri, 26 Oct 2001 00:02:12 +0900
From: YangWoo Ko <newcat@spsoft.co.kr>
To: idn@ops.ietf.org
Subject: Re: [idn] Re: stringprep and unassigned code points
Message-ID: <20011026000212.A1287@spsoft.co.kr>
References: <7FC3066C236FD511BC5900508BAC86FE4D7DFD@trestles.internal.realna <7FC3066C236FD511BC5900508BAC86FE4D7DFD@trestles.internal.realnames.com> <8015970.1004008258@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=EUC-KR
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5i
In-Reply-To: <8015970.1004008258@localhost>; from paf@cisco.com on Thu, Oct 25, 2001 at 11:10:58AM +0200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Dear Patrik Falstrom,

Thank you for your clear summary. Exeucuse me but would you do the
summary again for the following case ? This is really helpful when
we talk about Traditional Chinese / Simplified Chinese issue.

If a new version of Unicode comese out, which have a newly defined
rule to map codepoint (X) to codepoint (Y), where codepoint (X)
and (Y) was already defined in the previous version of Unicode and
there no rule for mapping or NF?C for either codepoint(X) or
codepoint(Y), the following is true:

...

On Thu, Oct 25, 2001 at 11:10:58AM +0200, Patrik Fältström wrote:
> Summary (once again):
> 
> If a new version of Unicode comes out, which have a newly assigned
> codepoint (X), and a mapping from X to Y, the following is true:
> 
> - X can not be part of the result of a nameprep which an old application
>   creates. If an old application get X as input, the codepoint is unassigned
>   and therefore illegal.
> - If Y is an earlier assigned codepoint, an application understanding the
>   new version of nameprep will when getting X map that to Y.
> - If Y is a newly assigned codepoint, an application understanding the
>   new version of nameprep will when getting X map that to Y.
> - In neither case (old application or new application) X will be part of
>   the output of the stringprep process.

-- 
/*------------------------------------------------
YangWoo Ko : newcat@spsoft.co.kr
We Invent Enterprise Software Solutions
and Make You Secure & Powerful.
------------------------------------------------*/



From owner-idn@ops.ietf.org  Thu Oct 25 12:09:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22488
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 12:09:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wmqw-0000Bi-00
	for idn-data@psg.com; Thu, 25 Oct 2001 08:55:30 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wmqv-0000Bc-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 08:55:30 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id AAA29424
	for <idn@ops.ietf.org>; Fri, 26 Oct 2001 00:55:17 +0900
Message-ID: <02ea01c15d6d$93e28940$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "IETF idn working group" <idn@ops.ietf.org>
References: <E15v7Sl-000LZE-00@psg.com> <4.2.0.58.J.20011022115559.0390cc70@localhost> <20011024200729.A7803@nicemice.net>
Subject: Re: [idn] information density in various languages (was Re: hi)
Date: Fri, 26 Oct 2001 00:56:15 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA22488


----- Original Message ----- 
From: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>
  You're right.  My estimate must have been based on an anomalous sample.
> Here are the counts for Genesis chapter 1:
> 
> King James:     3167 letters
> Basic English:  3088 letters
> Chinese Union:   778 ideographs
> Korean Revised: 1201 Hangul
> 
> references:
> http://www.ccim.org/bible/
> http://bible.wisenet.co.kr/
> 
> So it's about 4.0 English letters per Chinese ideograph, and about 2.6
> English letters per Korean Hangul.

That might have been a hard work. :-)

I know that chinese natural sentences contain many single-chinese-letter
verbs,pronouns,adjectives,adverbs and interrogatives, while most
chinese nouns are in two or three letters. composite chinese nouns
/business names are from combinations of those nouns.

If we take a research on chinese nouns and its corresponding english nouns/
transcriptions, the ratio 4.0 may be reduced to 2.X, i guess.
The ratio 2.6 for Hangul sentence  may be also reduced to lower 2.X, i believe.

I will suggest new source of chinese nouns, later time.
http://search.yahoo.com/bin/search?p=chinese+english will help for a while.

Chinese participanst are welcome to this analysis.

Thanks.

Soobok Lee
 



> 
> Each Korean Hangul takes about 2.9 octets in AMC-ACE-Z, which means a
> maximal Korean domain label (20 hangul) holds about as much information
> as a 52-letter English string, which about 17% less information than
> a maximal English domain label (63 letters), and about 38% less
> information than a maximal Chinese domain label (19 ideographs).
> 
> I now retract this statement:
> 
> > Of all the languages I've looked at, Korean is by far the least dense
> > when encoded using AMC-ACE-Z.
> 
> In light of the new data, I doubt that Korean is the least dense.
> 
> AMC
> 




From owner-idn@ops.ietf.org  Thu Oct 25 12:18:15 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22765
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 12:18:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wmzU-0000OY-00
	for idn-data@psg.com; Thu, 25 Oct 2001 09:04:20 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wmzT-0000OS-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 09:04:19 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id BAA32154;
	Fri, 26 Oct 2001 01:04:08 +0900
Message-ID: <02f401c15d6e$cca3b0f0$ec1bd9d2@temp>
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.20011025182258.036b42e0@localhost>
Subject: Re: [idn] NFC vs NFKC
Date: Fri, 26 Oct 2001 01:04:59 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA22765


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
 > 
> Hangul domain names in KS C 5601 would normally be encoded as
> precombined syllables. KS C 5601 provides about 2300 of them,
> the ones most often used. Users who want to used other Hangul
> syllables won't use non-conjoining Jamo (compatibility Jamo),
> because they will be displayed one Jamo at a time.
> 
> In the nameprep design team, we discussed some cases where users
> might want to use sequences of independent consonant Jamo. There
> are a few web pages with some examples of these, but not too many.
> We are not sure whether they should be allowed in domain names or
> not, and if they are, how they should be represented.
> 

Current windows 98 and above  support only  compatibility Jamo, does
not support "conjoining jamo + filler" sequence for isolated jamos 
which are often found in informal texts/business names.
No display and No input method for "conjoining jamo + filler" in
windows O/S.

Compatiliby Jamo became the defacto standard for isolated jamos
inadvertantly and contrary to the intent of ISO Korean representatives and UTC members.

NFKC maps Compatiblity Jamo to conjoining jamos withOUT fillers.

Nameprep's positions on NFKC's problematic handling of compat jamos
should be clarified. Two alternatives.

  1) NFC is used instead
  2) NFKC is used but bypass all characters from the compatibility jamo block

Soobok Lee


> 
> >[Edit] Is that because nobody uses these anymore, and so you would not
> >expect a modern invention like IDN to appear in an anachronic way? Is that
> >the case with all LEGACY characters?
> 
> I don't want IDN to carry unnecessary legacy compatibility
> baggage. If it turns out that something really helps the user
> (e.g. for the full-width Latin letters), I have nothing against
> mapping them. But I don't think it's a good idea to map a
> wholesale 3000, most of them not really used and very difficult
> to type in, just to get a few dozen mapped the right way.
> We can easily do the later without having to do the former.
> 
> 
> Regards,   Martin.
> 




From owner-idn@ops.ietf.org  Thu Oct 25 12:57:15 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23900
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 12:57:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wndK-0001Zr-00
	for idn-data@psg.com; Thu, 25 Oct 2001 09:45:30 -0700
Received: from femail33.sdc1.sfba.home.com ([24.254.60.23])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wndJ-0001Zl-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 09:45:29 -0700
Received: from c1340594a ([65.11.104.12]) by femail33.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20011025164528.IWHT26106.femail33.sdc1.sfba.home.com@c1340594a>;
          Thu, 25 Oct 2001 09:45:28 -0700
Message-ID: <025201c15d74$937b5ed0$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>, "Yves Arrouye" <yves@realnames.com>,
        <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <4.2.0.58.J.20011025182258.036b42e0@localhost> <02f401c15d6e$cca3b0f0$ec1bd9d2@temp>
Subject: Re: [idn] NFC vs NFKC
Date: Thu, 25 Oct 2001 09:46:21 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Either deletion, prohibition or producing fillers can be accomplished, if
desired, by adding mappings to "D. Mapping Tables" in
http://www.ietf.org/internet-drafts/draft-ietf-idn-nameprep-06.txt. And this
is *without* having to change anything else in nameprep. For example, for
U+3131 HANGUL LETTER KIYEOK here are the three options:

Deletion:
3131; ; Deletion

Prohibition:
3131; 0000; Prohibition

Additional folding
3131; 1100 1160; Additional Folding

In the last case, the medial filler is added. It is sufficient to do this
only for the initials, since that prevents any syllable formation. However,
if one wanted, the initial filler could be added before medials, such as for
U+314F HANGUL LETTER A below (or initial and final fillers could be added
before finals).

Additional folding
314F; 115F 1161; Additional Folding

Mark

—————

Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
[http://www.macchiato.com]

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Yves Arrouye" <yves@realnames.com>; <idn@ops.ietf.org>; "Martin Duerst"
<duerst@w3.org>
Sent: Thursday, October 25, 2001 09:04
Subject: Re: [idn] NFC vs NFKC



----- Original Message -----
From: "Martin Duerst" <duerst@w3.org>
 >
> Hangul domain names in KS C 5601 would normally be encoded as
> precombined syllables. KS C 5601 provides about 2300 of them,
> the ones most often used. Users who want to used other Hangul
> syllables won't use non-conjoining Jamo (compatibility Jamo),
> because they will be displayed one Jamo at a time.
>
> In the nameprep design team, we discussed some cases where users
> might want to use sequences of independent consonant Jamo. There
> are a few web pages with some examples of these, but not too many.
> We are not sure whether they should be allowed in domain names or
> not, and if they are, how they should be represented.
>

Current windows 98 and above  support only  compatibility Jamo, does
not support "conjoining jamo + filler" sequence for isolated jamos
which are often found in informal texts/business names.
No display and No input method for "conjoining jamo + filler" in
windows O/S.

Compatiliby Jamo became the defacto standard for isolated jamos
inadvertantly and contrary to the intent of ISO Korean representatives and
UTC members.

NFKC maps Compatiblity Jamo to conjoining jamos withOUT fillers.

Nameprep's positions on NFKC's problematic handling of compat jamos
should be clarified. Two alternatives.

  1) NFC is used instead
  2) NFKC is used but bypass all characters from the compatibility jamo
block

Soobok Lee


>
> >[Edit] Is that because nobody uses these anymore, and so you would not
> >expect a modern invention like IDN to appear in an anachronic way? Is
that
> >the case with all LEGACY characters?
>
> I don't want IDN to carry unnecessary legacy compatibility
> baggage. If it turns out that something really helps the user
> (e.g. for the full-width Latin letters), I have nothing against
> mapping them. But I don't think it's a good idea to map a
> wholesale 3000, most of them not really used and very difficult
> to type in, just to get a few dozen mapped the right way.
> We can easily do the later without having to do the former.
>
>
> Regards,   Martin.
>




From owner-idn@ops.ietf.org  Thu Oct 25 13:15:56 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24333
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 13:15:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wnsa-00022p-00
	for idn-data@psg.com; Thu, 25 Oct 2001 10:01:16 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wnsZ-00022i-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 10:01:15 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id CAA17208;
	Fri, 26 Oct 2001 02:00:55 +0900
Message-ID: <031801c15d76$bd1ca620$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>,
        "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
References: <030701c15c37$e463d8b0$1401000a@jamessonyvaio> <20011024124949X.yone@po.ntts.co.jp> <006701c15c94$2efd4530$1501000a@jamessonyvaio> <3BD7C0A0.86D101CE@zetnet.co.uk>
Subject: Re: [idn] Update Charter revision 2
Date: Fri, 26 Oct 2001 02:01:46 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA24333

----- Original Message ----- 
From: "David Hopwood" <david.hopwood@zetnet.co.uk>
> 
> It is worth pointing out that:
> 
>  - IDNA does not satisfy requirements 11 (since it allows unassigned
>    codepoints in queries without versioning) and 18 (since it allows
>    more than one representation of a name, differing in case),
> 
> IMHO there is little point in publishing a document specifying
> requirements that are unachievable.
> > 
> > [11] The protocol should handle with care new revisions of the CCS.
> > Undefined codepoints should not be allowed unless a new revision of
> > the protocol can handle it. Protocol revisions should be tagged.
> 
> The current version of nameprep allows unassigned code points in queries
> without revision tagging, for good reasons.
> 
> => [11] The proposal should handle with care new revisions of the CCS.
> => Proposals MUST discuss how undefined codepoints are handled.

I agree on this modification.

current nameprep I-D:

  1) old nameprep's applications may find its unassigned code points in
      received queries that come from newer nameprep's applications.
  2) but, old nameprep cannot generate ACE labels with at least one
      unassigned code point.

2) requires  old nameprep applications should be upgraded to
support newly assigned script. Auto-update  features will help 
some interative applications, but may not be available  for  
non-interative/offline-mode idn-aware applications or embedded IDNA
applets / OCX components which has no human or outerworld interaction.
Some disruption/failure in service may be caused by this latter situation.

Soobk Lee














From owner-idn@ops.ietf.org  Thu Oct 25 13:22:18 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24578
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 13:22:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wnzx-0002Dn-00
	for idn-data@psg.com; Thu, 25 Oct 2001 10:08:53 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wnzw-0002Db-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 10:08: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 CAA19622;
	Fri, 26 Oct 2001 02:08:35 +0900
Message-ID: <031e01c15d77$cd0e4380$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Mark Davis" <mark@macchiato.com>, "Yves Arrouye" <yves@realnames.com>,
        <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <4.2.0.58.J.20011025182258.036b42e0@localhost> <02f401c15d6e$cca3b0f0$ec1bd9d2@temp> <025201c15d74$937b5ed0$0c680b41@c1340594a>
Subject: Re: [idn] NFC vs NFKC
Date: Fri, 26 Oct 2001 02:09:26 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA24578


Not bad for future. But as for now, most current rendering platforms (on windows and unix/linux)
would fail to support rendering filler sequences and display fillers as "white spaces". 
That would cause confusions and misinterpretations for a long time until
all user platforms are upgraded to support fillers.

Soobok Lee

----- Original Message ----- 
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>; "Yves Arrouye" <yves@realnames.com>; <idn@ops.ietf.org>; "Martin Duerst" <duerst@w3.org>
Sent: Friday, October 26, 2001 1:46 AM
Subject: Re: [idn] NFC vs NFKC


> Either deletion, prohibition or producing fillers can be accomplished, if
> desired, by adding mappings to "D. Mapping Tables" in
> http://www.ietf.org/internet-drafts/draft-ietf-idn-nameprep-06.txt. And this
> is *without* having to change anything else in nameprep. For example, for
> U+3131 HANGUL LETTER KIYEOK here are the three options:
> 
> Deletion:
> 3131; ; Deletion
> 
> Prohibition:
> 3131; 0000; Prohibition
> 
> Additional folding
> 3131; 1100 1160; Additional Folding
> 
> In the last case, the medial filler is added. It is sufficient to do this
> only for the initials, since that prevents any syllable formation. However,
> if one wanted, the initial filler could be added before medials, such as for
> U+314F HANGUL LETTER A below (or initial and final fillers could be added
> before finals).
> 
> Additional folding
> 314F; 115F 1161; Additional Folding
> 
> Mark
> 
> —————
> 
> Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
> [http://www.macchiato.com]
> 
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: "Yves Arrouye" <yves@realnames.com>; <idn@ops.ietf.org>; "Martin Duerst"
> <duerst@w3.org>
> Sent: Thursday, October 25, 2001 09:04
> Subject: Re: [idn] NFC vs NFKC
> 
> 
> 
> ----- Original Message -----
> From: "Martin Duerst" <duerst@w3.org>
>  >
> > Hangul domain names in KS C 5601 would normally be encoded as
> > precombined syllables. KS C 5601 provides about 2300 of them,
> > the ones most often used. Users who want to used other Hangul
> > syllables won't use non-conjoining Jamo (compatibility Jamo),
> > because they will be displayed one Jamo at a time.
> >
> > In the nameprep design team, we discussed some cases where users
> > might want to use sequences of independent consonant Jamo. There
> > are a few web pages with some examples of these, but not too many.
> > We are not sure whether they should be allowed in domain names or
> > not, and if they are, how they should be represented.
> >
> 
> Current windows 98 and above  support only  compatibility Jamo, does
> not support "conjoining jamo + filler" sequence for isolated jamos
> which are often found in informal texts/business names.
> No display and No input method for "conjoining jamo + filler" in
> windows O/S.
> 
> Compatiliby Jamo became the defacto standard for isolated jamos
> inadvertantly and contrary to the intent of ISO Korean representatives and
> UTC members.
> 
> NFKC maps Compatiblity Jamo to conjoining jamos withOUT fillers.
> 
> Nameprep's positions on NFKC's problematic handling of compat jamos
> should be clarified. Two alternatives.
> 
>   1) NFC is used instead
>   2) NFKC is used but bypass all characters from the compatibility jamo
> block
> 
> Soobok Lee
> 
> 
> >
> > >[Edit] Is that because nobody uses these anymore, and so you would not
> > >expect a modern invention like IDN to appear in an anachronic way? Is
> that
> > >the case with all LEGACY characters?
> >
> > I don't want IDN to carry unnecessary legacy compatibility
> > baggage. If it turns out that something really helps the user
> > (e.g. for the full-width Latin letters), I have nothing against
> > mapping them. But I don't think it's a good idea to map a
> > wholesale 3000, most of them not really used and very difficult
> > to type in, just to get a few dozen mapped the right way.
> > We can easily do the later without having to do the former.
> >
> >
> > Regards,   Martin.
> >
> 
> 




From owner-idn@ops.ietf.org  Thu Oct 25 13:43:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25200
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 13:43:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15woHz-0002lV-00
	for idn-data@psg.com; Thu, 25 Oct 2001 10:27:31 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.33 #1)
	id 15woHz-0002lP-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 10:27:31 -0700
Received: (qmail 23898 invoked by uid 104); 25 Oct 2001 17:27:30 -0000
Received: from yves@realnames.com by friendly.realnames.com with qmail-scanner-0.96 (. Clean. Processed in 0.833823 secs); 25 Oct 2001 17:27:30 -0000
Received: from heaven.internal.realnames.com (10.1.5.39)
  by friendly.realnames.com with SMTP; 25 Oct 2001 17:27:29 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:4206]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <9369@heaven.internal.realnames.com>
	 for <david.hopwood@zetnet.co.uk>; Thu, 25 Oct 2001 10:24:43 AM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2653.19)
	id <V3D1GBHF>; Thu, 25 Oct 2001 10:27:24 -0700
Message-ID: <7FC3066C236FD511BC5900508BAC86FE4D7E06@trestles.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: =?iso-8859-1?Q?=27Patrik_F=E4ltstr=F6m=27?= <paf@cisco.com>,
        "'Martin Duerst'" <duerst@w3.org>, Soobok Lee <lsb@postel.co.kr>,
        David Hopwood <david.hopwood@zetnet.co.uk>, idn@ops.ietf.org
Subject: RE: [idn] Re: stringprep and unassigned code points
Date: Thu, 25 Oct 2001 10:23:58 -0700
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

> I must be extremely bad at expressing myself. This is now the third time
> since monday I explain how things work.

No, no, it's just me.

> > Now
> > let's suppose Unicode encodes something new, for which a new Nameprep is
> > released (because some additions to the mapping table are needed).
> 
> A mapping can only be from an earlier unassigned codepoint.

My case exactly.

> > At
> > this point, the DNS servers may contain the ACE(Nameprep(names in this
> > new thing)).
> 
> ACE have absolutely nothing to do with this. This is a stringprep issue.

I did not say it had anything to do with ACE. I used DNS and IDNA as an
example of the use of Nameprep, a stringprep profile.

> Only nameservers which do understand the new version of stringprep can
> have
> these names.
> 
> > And applications get these new codepoints,
> 
> What do you mean by "get these new codepoints"?

I mean that my mail client, for example, or my Web browser, after an OS
update, can now see these new code points, from an input method, for
example, whilst they were not generated before.

> > but because they
> > do not have the appropriate mapping table, they will pass ACE(Old
> > Nameprep(names in this new thing))
> 
> No, because the codepoint is unassigned in old version of stringsprep, and
> because of that MUST NOT be used.

See, that where there is where I get confused (must be me). The stringprep
says:

"Applications creating queries MUST treat U code points as if they were
AO when preparing the query to be entered in the process described by a
profile of stringprep. Those applications MAY optionally have a
preprocessor that provide stricter checks: treating unassigned code
points in the input as errors, or warning the user about the fact that
the code point is unassigned in the version of a profile that the
software is based on; such a choice is a local matter for the software."

And

" All code points not assigned in the character repertoire named in the
stringprep profile are called "unassigned code points". Stored strings
using the profile MUST NOT contain any unassigned code points. Queries
for matching strings MAY contain unassigned code points. Note that this
is the only part of this document where the requirements for queries
differs from the requirements for stored strings."

I take it from "MUST treat U code points as if they were AO when preparing
the query" that these code points MAY be used.

What is wrong (since you say I am wrong) with my reading of these two
paragraphs?

YA




From owner-idn@ops.ietf.org  Thu Oct 25 18:11:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01185
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 18:11:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wsLU-0009tU-00
	for idn-data@psg.com; Thu, 25 Oct 2001 14:47:24 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wsLT-0009tL-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 14:47:23 -0700
Received: from [165.227.249.20] (165-227-249-20.client.dsl.net [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f9PLlC802227;
	Thu, 25 Oct 2001 14:47:12 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100338b7fe36572a8b@[165.227.249.20]>
In-Reply-To: <4.2.0.58.J.20011025122342.067d7100@localhost>
References: <030701c15c37$e463d8b0$1401000a@jamessonyvaio>
 <20011024124949X.yone@po.ntts.co.jp>
 <4.2.0.58.J.20011025122342.067d7100@localhost>
Date: Thu, 25 Oct 2001 14:38:00 -0700
To: Martin Duerst <duerst@w3.org>, "James Seng/Personal" <jseng@pobox.org.sg>,
        <idn@ops.ietf.org>, "Yoshiro YONEYA" <yone@po.ntts.co.jp>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] Update Charter revision 2
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 12:34 PM +0900 10/25/01, Martin Duerst wrote:
>At 22:00 01/10/24 +0800, James Seng/Personal wrote:
>
>>  > - Nameprep is now divided into framework (stringprep) and profile
>>>    (nameprep).  Is stringprep scope of this WG?  I think it is
>>>    eventually yes at this moment but I'm not sure, so please clarify
>>>    position of stringprep.
>>
>>Good question. As far as it stand now, only draft-ietf-idn-nameprep is
>>part of IDN work. draft-hoffman-stringprep is not. How it goes will
>>depends on the author.
>>
>>I suspect only nameprep will stay within IDN group and stringprep may
>>remains generic or go to other wg, which may not be formed yet.
>
>Hello James,
>
>I have raised this issue, too. The title of the 'nameprep' draft
>is now "Stringprep Profile for Internationalized Host Names",
>and this is an accurate reflection of it's content. 'nameprep'
>therefore depends on 'stringprep'. If we want to go to Proposed
>Standard with 'nameprep', we cannot have 'stringprep' still as
>an I-D. Given your schedule for 'nameprep', it seems impossible
>for a new WG to be formed and to take up and finish 'stringprep'
>in time. Also, it seems quite dangerous to leave 'stringprep'
>to it's authors without at least close coordination with this
>WG. Leaving this at suspicions is not good enough. It shouldn't
>be difficult to improve on this given that the authors of
>stringprep are one of the co-chairs in this group and an
>active participant of this group.
>
>Regards,   Martin.

Martin is right: we cannot finish nameprep until stringprep is 
finished. If the WG chairs don't want it as part of the WG, that's 
fine, but it is going to go through the same IETF last call as 
nameprep will. There is no reason not to have it in this WG.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Thu Oct 25 18:28:12 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01367
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 18:28:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wsgb-000AUd-00
	for idn-data@psg.com; Thu, 25 Oct 2001 15:09:13 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wsga-000AUX-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 15:09:13 -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 PAA31182
	for <idn@ops.ietf.org>; Thu, 25 Oct 2001 15:09:11 -0700
Message-Id: <5.1.0.14.2.20011025150641.0391b768@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 25 Oct 2001 15:10:27 -0700
To: <idn@ops.ietf.org>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] Update Charter revision 2
In-Reply-To: <p05100338b7fe36572a8b@[165.227.249.20]>
References: <4.2.0.58.J.20011025122342.067d7100@localhost>
 <030701c15c37$e463d8b0$1401000a@jamessonyvaio>
 <20011024124949X.yone@po.ntts.co.jp>
 <4.2.0.58.J.20011025122342.067d7100@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 02:38 PM 10/25/2001, Paul Hoffman / IMC wrote:
>Martin is right: we cannot finish nameprep until stringprep is finished. 
>If the WG chairs don't want it as part of the WG, that's fine, but it is 
>going to go through the same IETF last call as nameprep will. There is no 
>reason not to have it in this WG.


In fact, there is every reason TO have it in this working group:

1.  the work has been done here.
2.  no other working group is laying claim to it.
3.  we need the work.
4.  we need it NOW.

People have confused the need to separate a specification into two parts 
with the idea of having the two parts done by different groups.

The problem with the previous combining into one document was not that the 
technical content was a bad idea or particularly badly written.  It was 
that having them combined proved to be very confusing to people and that 
separating the parts makes clearer what part is general and what part is 
specific to the DNS.

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 Oct 25 20:35:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03307
	for <idn-archive@lists.ietf.org>; Thu, 25 Oct 2001 20:35:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15wucP-000EBg-00
	for idn-data@psg.com; Thu, 25 Oct 2001 17:13:01 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15wucO-000EBZ-00
	for idn@ops.ietf.org; Thu, 25 Oct 2001 17:13:00 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 655D6FFC0E; Fri, 26 Oct 2001 08:13:17 +0800 (SGT)
Message-ID: <007e01c15db2$f8cd23c0$1801000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Martin Duerst" <duerst@w3.org>, <idn@ops.ietf.org>,
        "Yoshiro YONEYA" <yone@po.ntts.co.jp>,
        "Paul Hoffman / IMC" <phoffman@imc.org>
References: <030701c15c37$e463d8b0$1401000a@jamessonyvaio> <20011024124949X.yone@po.ntts.co.jp> <4.2.0.58.J.20011025122342.067d7100@localhost> <p05100338b7fe36572a8b@[165.227.249.20]>
Subject: Re: [idn] Update Charter revision 2
Date: Fri, 26 Oct 2001 08:12:41 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Agree with Martin too.

But clarification: whether stringprep should be within IDN wg is a bit
more complex. Obviously with the dependency, it should be.

-James Seng

> Martin is right: we cannot finish nameprep until stringprep is
> finished. If the WG chairs don't want it as part of the WG, that's
> fine, but it is going to go through the same IETF last call as
> nameprep will. There is no reason not to have it in this WG.
>
> --Paul Hoffman, Director
> --Internet Mail Consortium




From owner-idn@ops.ietf.org  Fri Oct 26 03:47:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25137
	for <idn-archive@lists.ietf.org>; Fri, 26 Oct 2001 03:47:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15x1T8-00001e-00
	for idn-data@psg.com; Fri, 26 Oct 2001 00:31:54 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15x1T7-000Q0c-00
	for idn@ops.ietf.org; Fri, 26 Oct 2001 00:31:53 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 4A3647F414; Fri, 26 Oct 2001 16:31:00 +0900 (JST)
Message-Id: <4.2.0.58.J.20011026155311.02ef0100@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 26 Oct 2001 16:04:11 +0900
To: Dave Crocker <dhc@dcrocker.net>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Update Charter revision 2
In-Reply-To: <5.1.0.14.2.20011025150641.0391b768@dcrocker.net>
References: <p05100338b7fe36572a8b@[165.227.249.20]>
 <4.2.0.58.J.20011025122342.067d7100@localhost>
 <030701c15c37$e463d8b0$1401000a@jamessonyvaio>
 <20011024124949X.yone@po.ntts.co.jp>
 <4.2.0.58.J.20011025122342.067d7100@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 15:10 01/10/25 -0700, Dave Crocker wrote:

>In fact, there is every reason TO have it in this working group:
>
>1.  the work has been done here.
>2.  no other working group is laying claim to it.
>3.  we need the work.
>4.  we need it NOW.
>
>People have confused the need to separate a specification into two parts 
>with the idea of having the two parts done by different groups.

Very much agreed up to here.


>The problem with the previous combining into one document was not that the 
>technical content was a bad idea or particularly badly written.  It was 
>that having them combined proved to be very confusing to people

This is the first time I have heard this argument.
It wasn't confusing to me, but maybe that's because I have
been involved in various discussions about it.


>and that separating the parts makes clearer what part is general and what 
>part is specific to the DNS.

To separate the general and the specific parts, in order to be able
to reuse the general parts, is a very valuable goal.

I'm personally not sure we already understand what part is really
general, and what part is specific. Of course, because for IDN we
need all of it, it doesn't really matter to this group.
But I'm a bit afraid that other groups might try to use the general
part of it (stringprep) without checking whether the level of
generality provided really works for them.


Regards,   Martin.



From owner-idn@ops.ietf.org  Fri Oct 26 03:48:18 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25162
	for <idn-archive@lists.ietf.org>; Fri, 26 Oct 2001 03:48:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15x1T8-00001f-00
	for idn-data@psg.com; Fri, 26 Oct 2001 00:31:54 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15x1T7-000Q0d-00
	for idn@ops.ietf.org; Fri, 26 Oct 2001 00:31:53 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id AD0637F4DB; Fri, 26 Oct 2001 16:31:00 +0900 (JST)
Message-Id: <4.2.0.58.J.20011026160859.02f495c0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 26 Oct 2001 16:31:31 +0900
To: liana Ye <liana.ydisg@juno.com>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] An ignorant question about TC<-> SC
Cc: klensin@jck.com, idn@ops.ietf.org
In-Reply-To: <20011025.023737.-360533.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

At 02:37 01/10/25 -0700, liana Ye wrote:

>In another word, the fundimental work from UCS is the to table
>glyphs based on their visual distinction.

That is simply not true. The fundamental work is to make
sure that the result is best usable by average users for
their average purpose (writing electronic texts).

There have been a lot of requests to use finer distinctions,
e.g. from researchers or from people who publish dictionaries.
They were rejected, because they would confuse the average
user and the average use more than they would help.

There have also been requests for more unification, e.g. to
simplify searching/lookup in some situations, but they
have again been rejected because they would confuse the
average user and the average use more than they would help.
[In addition, such unifications would have to deal with the
many-to-one and many-to-many mappings, which just wouldn't
work.]


>Then why this group
>get into the guide line work in normalization of characters?

Because they are experts on characters, they use normalization
in their implementations, and so on.


>Why
>they give advice such as "not put TC/SC into" another table
>for a different purpose?

Because many of them have been studying Han characters extensively,
and many others have worked with people who have done so, for
actual implementations and products, and they all have learned,
in one way or another, that TC/SC conversion is a very hard
problem that cannot be solved by a simple mapping table.

Do you really think that people from companies such as Microsoft,
IBM, Apple, and many others (see the list of members of the
Unicode Consortium at
http://www.unicode.org/unicode/consortium/memblogo.html),
and in particular the specialists for internationalization
in these companies, would want to tell you that TC/SC
mapping is difficult if they knew how to do it? Do you
think that any of these companies would not want to
sell products that did the conversion if it were easy
enough to make such a product? How much time do you think
engineers in each of these companies have spent studying
the problem and trying to come up with a simple but
satisfactory solution, without a satisfactory result?

I very much think that all of the people at the Unicode
Consortium would be very glad if there were a simple
mapping solution to the TC/SC problem, and would not
at all object to it being added to IDN, because they
understand that the TC/SC is an important one. But they
know from years, if not decades, of experience, that
it's all but an easy job, depeding a lot on context
(as James has said) which is not available in IDN,
and where a machine never gets perfect.


Hope this helps.    Regards,    Martin.



>Liana
>
>
>On Thu, 25 Oct 2001 16:27:10 +0900 Martin Duerst <duerst@w3.org> writes:
> > At 13:02 01/10/23 -0700, liana Ye wrote:
> >
> > >  From screen display point view, TC/SC are different glyph
> > >  sets(who defines the sets? How is it used by 1/5 of the world
> > >population? Is Uicode group the only authoritive one? In
> > >China there are over 600 recorded views on this).
> >
> > The Han ideographs in Unicode/ISO 10646 are defined by the
> > IRG (Ideographic Raporteur Group). This group reports to
> > ISO/IEC SC2 WG2, the ISO WG responsible for ISO 10646.
> > It is composed of representatives from all the countries
> > or similar entities interested in Han ideographs. That
> > includes China, Japan, Korea (both South and North), Taiwan,
> > Hong Kong, Singapore, and the US (I hope I didn't forget
> > anybody, and please excuse the maybe politically uncorrect
> > shortcuts). The US is the only country represented without
> > a tradition of using Han ideographs, but usually only
> > sends a small delegation and mainly helps with wording.
> > Many other countries may send rather large delegations
> > (given the number of characters, which means a lot of
> > work, this is no surprise). The Unicode consortium
> > participates in the IRG with an observer status only.
> >
> > The IRG has published guidelines for deciding when to
> > unify two occurences and when not. Because of the very
> > huge number of characters, there is in some cases indeed
> > a thin line as to whether something should be unified or
> > not. And in these cases, the IRG just has to make a decision.
> >
> > Overall, the guidelines are somewhat difficult to understand
> > at first, but they are designed mainly with a 'least surprise
> > to the average user' in mind, and I think they have achieved
> > this goal very well. The guidelines are based on earlier
> > ones used for the Japanese standard.
> >
> > The core of the guidelines says that if two characters look
> > significantly different, then they are encoded with two codes
> > even if they e.g. are one-to-one SC/TC equivalents. This is
> > to avoid suddenly changing the appearance of letters for a
> > user who may not be familiar with the significantly differently
> > looking shape. On the other hand, cases where there is only
> > a small difference in shape are unified (i.e. only one code)
> > unless this small difference in shape makes an actual
> > difference in meaning.
> >
> > Overall, the results are so that if you present a text
> > where you change the glyph shapes within the range that
> > is unified, people who have done basic education but don't
> > know about different shapes (e.g. people in Taiwan or
> > Hong Kong who only know about TC, or people in China or
> > Singapore who only know about SC, or people in Japan who
> > only know about the forms used in Japan) will read over
> > these changes without problems, and might at some points
> > say 'this looks a bit strange', but will still identify
> > the character.
> >
> > There are some exceptions to these rule related to backwards-
> > compatible roundtripping (source separation rule).
> >
> >
> > Hope this helps,      Martin.




From owner-idn@ops.ietf.org  Fri Oct 26 03:56:25 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25274
	for <idn-archive@lists.ietf.org>; Fri, 26 Oct 2001 03:56:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15x1T8-00001d-00
	for idn-data@psg.com; Fri, 26 Oct 2001 00:31:54 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15x1T7-000Q0b-00
	for idn@ops.ietf.org; Fri, 26 Oct 2001 00:31:53 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id 7A2107F4D8; Fri, 26 Oct 2001 16:31:00 +0900 (JST)
Message-Id: <4.2.0.58.J.20011026160616.02f49b30@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 26 Oct 2001 16:08:28 +0900
To: liana Ye <liana.ydisg@juno.com>, paf@cisco.com
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] (bias) summary of reordering discussion
Cc: idn@ops.ietf.org
In-Reply-To: <20011025.025800.-360533.1.liana.ydisg@juno.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 02:57 01/10/25 -0700, liana Ye wrote:

>What if we define a frame and  make it possible to let any
>script to be mapped by their own user group, as long as
>the user group can come up with their agreement on how
>to do the mapping. The [nameprep] is severing as example
>of such mapping. BTW, is "PROFILE" have such meaning?

Well, there is only one DNS for the whole world. That's
why profiles or frames (or whatever you call it) are not
a good idea.

Also, DNS server have heavy loads. That's why some kinds
of solutions designed by user groups may not be workable,
and why we have DNS experts in this group.

Regards,    Martin.



>Liana
>
>
>On Thu, 25 Oct 2001 10:08:48 +0200 =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?=
><paf@cisco.com> writes:
> > --On 01-10-25 12.54 +0900 Martin Duerst <duerst@w3.org> wrote:
> >
> > > At 19:41 01/10/23 +0200, Patrik F$BgM(Btstr$B?N(B wrote:
> > >
> > >> o Nameprep mappings is defined by UTC, not IETF.
> > >>   -> I am nervous when we in IETF talk about these things
> > >
> > > The main mappings used by nameprep (casemapping and normalization)
> > > are defined by the UTC. But it is IETF that chooses which mappings
> > > to select (e.g. NFC vs. NFKC), it is IETF that may request other
> > > mappings to be created (NFC was created based on a request by W3C,
> > > an additional file was added to help IETF with case mapping,
> > > a (tentative, implicit) request for TC/SC mappings was turned
> > down).
> > >
> > > Also, nameprep contains a few additional mappings and prohibitions
> > > that are motivated by the specific situation of domain names,
> > > without taking these from anywhere.
> >
> > You are correct, but I am still nervous.
> >
> >    paf
> >
> >




From owner-idn@ops.ietf.org  Fri Oct 26 03:58:44 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25320
	for <idn-archive@lists.ietf.org>; Fri, 26 Oct 2001 03:58:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15x1jy-0000Ub-00
	for idn-data@psg.com; Fri, 26 Oct 2001 00:49:18 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15x1jx-0000UU-00
	for idn@ops.ietf.org; Fri, 26 Oct 2001 00:49:18 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 32105FFC0E; Fri, 26 Oct 2001 15:49:31 +0800 (SGT)
Message-ID: <001901c15df2$b436bec0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Dave Crocker" <dhc@dcrocker.net>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <p05100338b7fe36572a8b@[165.227.249.20]> <4.2.0.58.J.20011025122342.067d7100@localhost> <030701c15c37$e463d8b0$1401000a@jamessonyvaio> <20011024124949X.yone@po.ntts.co.jp> <4.2.0.58.J.20011025122342.067d7100@localhost> <4.2.0.58.J.20011026155311.02ef0100@localhost>
Subject: Re: [idn] Update Charter revision 2
Date: Fri, 26 Oct 2001 15:49:12 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I presumed that other group would have to look at nameprep as an example
how they can create a "profile" for their own purpose and requirements.

james

> I'm personally not sure we already understand what part is really
> general, and what part is specific. Of course, because for IDN we
> need all of it, it doesn't really matter to this group.
> But I'm a bit afraid that other groups might try to use the general
> part of it (stringprep) without checking whether the level of
> generality provided really works for them.
>
>
> Regards,   Martin.





From owner-idn@ops.ietf.org  Fri Oct 26 04:04:22 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25400
	for <idn-archive@lists.ietf.org>; Fri, 26 Oct 2001 04:04:21 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15x1oz-0000b6-00
	for idn-data@psg.com; Fri, 26 Oct 2001 00:54:29 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15x1oy-0000az-00
	for idn@ops.ietf.org; Fri, 26 Oct 2001 00:54:29 -0700
Received: from [192.168.1.5] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id JAA05580;
	Fri, 26 Oct 2001 09:54:11 +0200 (MET DST)
Date: Fri, 26 Oct 2001 09:45:40 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: YangWoo Ko <newcat@spsoft.co.kr>, idn@ops.ietf.org
Subject: Re: [idn] Re: stringprep and unassigned code points
Message-ID: <12893046.1004089540@localhost>
In-Reply-To: <20011026000212.A1287@spsoft.co.kr>
References: <7FC3066C236FD511BC5900508BAC86FE4D7DFD@trestles.internal.realna
 <7FC3066C236FD511BC5900508BAC86FE4D7DFD@trestles.internal.realnames.com>
 <8015970.1004008258@localhost> <20011026000212.A1287@spsoft.co.kr>
X-Mailer: Mulberry/2.1.1 (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 EAA25400

--On 01-10-26 00.02 +0900 YangWoo Ko <newcat@spsoft.co.kr> wrote:

> If a new version of Unicode comese out, which have a newly defined
> rule to map codepoint (X) to codepoint (Y), where codepoint (X)
> and (Y) was already defined in the previous version of Unicode and
> there no rule for mapping or NF?C for either codepoint(X) or
> codepoint(Y), the following is true:

If you have an alreday assigned codepoint, a mapping will _NOT_ be added in
later versions of Nameprep.

So, what you ask for will never happen.

  paf

> ...
> 
> On Thu, Oct 25, 2001 at 11:10:58AM +0200, Patrik Fältström wrote:
>> Summary (once again):
>> 
>> If a new version of Unicode comes out, which have a newly assigned
>> codepoint (X), and a mapping from X to Y, the following is true:
>> 
>> - X can not be part of the result of a nameprep which an old application
>>   creates. If an old application get X as input, the codepoint is
>>   unassigned and therefore illegal.
>> - If Y is an earlier assigned codepoint, an application understanding the
>>   new version of nameprep will when getting X map that to Y.
>> - If Y is a newly assigned codepoint, an application understanding the
>>   new version of nameprep will when getting X map that to Y.
>> - In neither case (old application or new application) X will be part of
>>   the output of the stringprep process.
> 
> -- 
> /*------------------------------------------------
> YangWoo Ko : newcat@spsoft.co.kr
> We Invent Enterprise Software Solutions
> and Make You Secure & Powerful.
> ------------------------------------------------*/
>  



Patrik Fältström <paf@cisco.com>                         Cisco Systems
Consulting Engineer                                  Office of the CSO
Phone: (Stockholm) +46-8-6859131            (San Jose) +1-408-525-8509
        PGP: 2DFC AAF6 16F0 F276 7843  2DC1 BC79 51D9 7D25 B8DC




From owner-idn@ops.ietf.org  Fri Oct 26 04:28:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25691
	for <idn-archive@lists.ietf.org>; Fri, 26 Oct 2001 04:28:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15x2CS-00013b-00
	for idn-data@psg.com; Fri, 26 Oct 2001 01:18:44 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15x2CR-00013V-00
	for idn@ops.ietf.org; Fri, 26 Oct 2001 01:18:43 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id E11327F414; Fri, 26 Oct 2001 17:17:55 +0900 (JST)
Message-Id: <4.2.0.58.J.20011026170759.058dce80@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 26 Oct 2001 17:09:47 +0900
To: "James Seng/Personal" <jseng@pobox.org.sg>,
        "Dave Crocker" <dhc@dcrocker.net>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Update Charter revision 2
In-Reply-To: <001901c15df2$b436bec0$dd00a8c0@jamessonyvaio>
References: <p05100338b7fe36572a8b@[165.227.249.20]>
 <4.2.0.58.J.20011025122342.067d7100@localhost>
 <030701c15c37$e463d8b0$1401000a@jamessonyvaio>
 <20011024124949X.yone@po.ntts.co.jp>
 <4.2.0.58.J.20011025122342.067d7100@localhost>
 <4.2.0.58.J.20011026155311.02ef0100@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 15:49 01/10/26 +0800, James Seng/Personal wrote:
>I presumed that other group would have to look at nameprep as an example
>how they can create a "profile" for their own purpose and requirements.

Yes, definitely. But they also have to look at whether creating
just a stringprep profile as we do in nameprep works for them,
or whether they have requirements that make bigger changes
necessary.

Regards,   Martin.



>james
>
> > I'm personally not sure we already understand what part is really
> > general, and what part is specific. Of course, because for IDN we
> > need all of it, it doesn't really matter to this group.
> > But I'm a bit afraid that other groups might try to use the general
> > part of it (stringprep) without checking whether the level of
> > generality provided really works for them.
> >
> >
> > Regards,   Martin.
>




From owner-idn@ops.ietf.org  Fri Oct 26 06:57:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26796
	for <idn-archive@lists.ietf.org>; Fri, 26 Oct 2001 06:57:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15x4NI-0003Cz-00
	for idn-data@psg.com; Fri, 26 Oct 2001 03:38:04 -0700
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15x4NH-0003Cs-00
	for idn@ops.ietf.org; Fri, 26 Oct 2001 03:38:03 -0700
Received: from [209.187.148.217] (helo=P2)
	by bs.jck.com with esmtp (Exim 3.32 #1)
	id 15x4NF-00007l-00; Fri, 26 Oct 2001 10:38:02 +0000
Date: Fri, 26 Oct 2001 06:37:54 -0400
From: John C Klensin <klensin@jck.com>
To: Martin Duerst <duerst@w3.org>
cc: idn@ops.ietf.org
Subject: Re: [idn] An ignorant question about TC<-> SC
Message-ID: <78155142.1004078274@P2>
In-Reply-To: <4.2.0.58.J.20011026160859.02f495c0@localhost>
References:  <4.2.0.58.J.20011026160859.02f495c0@localhost>
X-Mailer: Mulberry/2.1.1 (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

Martin,

For better or worse, your explanation and history is somewhat
revisionist.   While I believe the UTC has done an outstanding
job in more recent years to try to clean things up and
generalize them --in the directions you suggest-- my strong
recollection of the battles over "UCS" and what became 10646
follows.   NOTE: most of the WG may not want (or need) to read
this.  It goes over ground that we've been over before, and I am
writing this primarily in the hope that we can avoid cycling
through it again, in pieces.  The conclusion is that
Unicode/10646 is what we have today, and what we are stuck with,
and that arguments about history and design criteria are largely
pointless.

For those who want the history, at least as I remember it, read
on...

The original UCS effort, leading to what was known as 10646 
DIS-1, was focused on an effort whose criteria included a strong
focus on comparability and generalized applications use.  That
effort included a rather extensive liaison/ requirements
statement from the then-ISO TC97 subcommittee on programming
languages to the then TC97 SC2 that was accepted by SC2.  That
statement of requirements asked for a UCS that contained many of
the properties that we've discovered in the last few years would
be really helpful if they were present in Unicode, but aren't
there.  For example, there was to be no mixing of precomposed
characters and those that were built up as a sequence of code
points, using either non-spacing or overstrike ideas.   And
there was to be no overlaying of characters that looked alike
but were different.   

This is obviously the dream of someone doing string comparisons
and report-writing (which programming language people do, or
did, very often), since every character image seen on a page
would represent exactly the same string length in a computer,
i.e., 
  length-in-visual-units (string) =
      length-in-character-units (string)
always.

And, e.g., what I see as the hardest part of the TC <-> SC
problem would not have existed, aince there would have been no
confusion between, e.g., a Chinese character and a
similar-looking Korean or Japanese one.

The result, coming into the DIS-1 vote, did not completely meet
those critera (for example, it did contain provision for
overlaying glyphs), although it was arguably close to it.  It
was also large (requiring four octets) and, in some ways, fairly
unwieldy.  And, of course, by virtue of not having overlaying,
transposition from written text in an unknown language into a
coded character set representation was a far worse problem than
the one we struggle with today.  And, if I recall, the draft
hadn't preserved contingency and ordering of important and
frequently used existing character sets as block subsets.

In the ISO ballot resolution process, supposedly to handle some
negative votes against DIS-1, the then-complete proposal was
replaced, as an editorial substitution, with the then-current
version of Unicode.  Doing it as an editorial substitution
prevented any further review by interests within most (or any?)
of the ISO Member Bodies, nor was it possible for the other
subcommittees who had stated requirement to SC2 to comment on
the new version.  

The Unicode standard of that time had come out of a consortium
of, essentially, printer manufacturers.  Their primary design
criteria apparently included preservation of existing and
heavily-used character sets as proper block subsets (to avoid
having to change ROMs); keeping to a minimum number of octets
per character, especially [then] frequently-used characters
(memory was expensive and printer memory (and "board real
estate") was even more expensive than computer memory); and, to
the extent that they didn't conflict with the above, "if they
look alike, they are alike" and "if it is possible to think of
it as a font difference, it is" rules.  And, using those rules,
they assumed that 16 bits would be enough, forever.

At this late date, the most reaaonable thing that can be said
about the different between the approaches represented by
Unicode and 10646 DIS-1 is that they started from different
criteria and made the tradeoffs differently.  Which approach is
"better" depends on where one starts and what one considers most
important.   And both represent compromises with their original
criteria, due to conflicts among their requirements, so neither
was (or would have been) completely consistent internally.

Any complex, international, character set effort that started
more or less from scratch would face similar tradeoffs, e.g.:

	* preservation of the properties and locality of
	existing, heavily-used character sets versus optimality
	for, e.g., collation (for example, in a mixed case
	language in which both cases are expected to be used
	regularly, it would be much more convenient to have the
	characters arranged as 
          {Upper1, Lower1, Upper2,	Lower2, ... }
	rather than
	  {Upper1, Upper2, ..., Lower1, Lower2, ... }

	* Accurate transcription from a printed form, especially
	in an unknown language, into the coded character set
	versus keeping languages distinct or scripts together.
	
	* String comparisons versus the compactness of a
	character set
	
	* Overall size versus avoiding "unification".

and so on.  

And, in my personal opinion (then and now) the Unicode designers
were a little naive about the number of characters which a UCS
would ulimately need to accomodate and were a little too biased
in their thinking by their then-existing market.  That market
was mostly North American and Western European, their deployed
products were primarily deployed in those markets, and backward
compatibility with existing devices and thinking probably
impacted optimization decisions about the character set's
organization.   But, as I said at the beginning, times have
changed -- the current UTC is clearly trying to work around the
design limitations imposed by that starting point.

The bottom line is that Unicode is what we have.  It is lots
better for our purposes than its 1.0 version.  ISO 10646 DIS-1
is an historical footnote (as is this entire note).  We _need_
to figure out how to make what we have work.  That implies
either abandoning other sorts of ideas, or ideas that would
depend on an entirely different coding structure.  Or we need to
move other sorts of ideas into additional layers where we can
create more flexibility than the DNS gives us.  Or, of course,
we can get used to the idea that reaching a conclusion on
internationalized domain names, or even internationalized access
to them, will take a _very_ long time.   

After all, it has taken us thousands of years to create the
large variety of languages and writing systems (some might say
"the total mess") we have in the world today.  Perhaps it is
hubris to believe that we can reconcile all of the differences
as part of a DNS effort.  But, since the alternative is giving
up, and the requirements are important, I think we need to focus
in on the important and solvable problems and try to move
forward, rather than getting stuck on the historical sequences
that got us here, or on interesting research ideas, or on
unsolvable problems.

     john




--On Friday, 26 October, 2001 16:31 +0900 Martin Duerst
<duerst@w3.org> wrote:

> At 02:37 01/10/25 -0700, liana Ye wrote:
> 
>> In another word, the fundimental work from UCS is the to table
>> glyphs based on their visual distinction.
> 
> That is simply not true. The fundamental work is to make
> sure that the result is best usable by average users for
> their average purpose (writing electronic texts).
> 
> There have been a lot of requests to use finer distinctions,
> e.g. from researchers or from people who publish dictionaries.
> They were rejected, because they would confuse the average
> user and the average use more than they would help.
>...






From owner-idn@ops.ietf.org  Fri Oct 26 10:11:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04335
	for <idn-archive@lists.ietf.org>; Fri, 26 Oct 2001 10:11:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15x7RW-00071a-00
	for idn-data@psg.com; Fri, 26 Oct 2001 06:54:38 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15x7RV-00071T-00
	for idn@ops.ietf.org; Fri, 26 Oct 2001 06:54:37 -0700
Received: from cs881964a ([24.43.70.205]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Fri, 26 Oct 2001 07:08:06 -0700
Message-ID: <003401c15e27$0d168640$cd462b18@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "liana Ye" <liana.ydisg@juno.com>, "Martin Duerst" <duerst@w3.org>
Cc: <klensin@jck.com>, <idn@ops.ietf.org>
References: <4.2.0.58.J.20011026160859.02f495c0@localhost>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Fri, 26 Oct 2001 10:03:39 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Martin,

> But they
> know from years, if not decades, of experience, that
> it's all but an easy job, depeding a lot on context
> (as James has said) which is not available in IDN,
> and where a machine never gets perfect.
>
>
> Hope this helps.    Regards,    Martin.
>

If that is the case, then why is it not a good idea to explicitly
label what type of script an IDN is in using 2LDs or TLDs?  (Other
then the fact that it is not interoperability and therefore should not
be a standard... )  This can be applied to all other language scripts
and not just <idn>.<traditional> and <idn>.<simplified> for Chinese
domain name users.  Users of IDNs are alot smarter and more
resourceful then we give them credit for, *as long as* we make it 100%
clear what script the IDN is in and not make it some kind of a
guessing game for them.

Thanks
Ben





From owner-idn@ops.ietf.org  Fri Oct 26 10:21:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04762
	for <idn-archive@lists.ietf.org>; Fri, 26 Oct 2001 10:21:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15x7h6-0007aZ-00
	for idn-data@psg.com; Fri, 26 Oct 2001 07:10:44 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15x7h5-0007aR-00
	for idn@ops.ietf.org; Fri, 26 Oct 2001 07:10:43 -0700
Received: from cs881964a ([24.43.70.205]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Fri, 26 Oct 2001 07:24:12 -0700
Message-ID: <003a01c15e29$4c9fdda0$cd462b18@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "John C Klensin" <klensin@jck.com>, "Martin Duerst" <duerst@w3.org>
Cc: <idn@ops.ietf.org>
References:  <4.2.0.58.J.20011026160859.02f495c0@localhost> <78155142.1004078274@P2>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Fri, 26 Oct 2001 10:20:00 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi John,

>
> For those who want the history, at least as I remember it, read
> on...
>

Thanks for the history lesson and I now have a much better
understanding of all the efforts that have gone into this.  So I have
the same question for you as I do for Martin.  Why can't we simply
label an IDN with the what language script it is in.  In my opinion,
it is much more important for an IDN user to know "what script the IDN
is in" and far less important to know "if the IDN will take them to a
company or goverment or military or organization website".

Thanks
Ben






From owner-idn@ops.ietf.org  Fri Oct 26 11:11:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06433
	for <idn-archive@lists.ietf.org>; Fri, 26 Oct 2001 11:11:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15x8QC-0009Mh-00
	for idn-data@psg.com; Fri, 26 Oct 2001 07:57:20 -0700
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15x8QB-0009MX-00
	for idn@ops.ietf.org; Fri, 26 Oct 2001 07:57:20 -0700
Received: from [209.187.148.217] (helo=P2)
	by bs.jck.com with esmtp (Exim 3.32 #1)
	id 15x8Q4-0000Rc-00; Fri, 26 Oct 2001 14:57:12 +0000
Date: Fri, 26 Oct 2001 10:56:55 -0400
From: John C Klensin <klensin@jck.com>
To: ben <ben@cc-www.com>
cc: idn@ops.ietf.org
Subject: Re: [idn] An ignorant question about TC<-> SC
Message-ID: <2544044.1004093815@localhost>
In-Reply-To: <003a01c15e29$4c9fdda0$cd462b18@mtag1.on.home.com>
References:  <003a01c15e29$4c9fdda0$cd462b18@mtag1.on.home.com>
X-Mailer: Mulberry/2.1.1 (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, 26 October, 2001 10:20 -0400 ben <ben@cc-www.com>
wrote:

> Hi John,
> 
>> 
>> For those who want the history, at least as I remember it,
>> read on...
>> 
> 
> Thanks for the history lesson and I now have a much better
> understanding of all the efforts that have gone into this.  So
> I have the same question for you as I do for Martin.  Why
> can't we simply label an IDN with the what language script it
> is in.  In my opinion, it is much more important for an IDN
> user to know "what script the IDN is in" and far less
> important to know "if the IDN will take them to a company or
> goverment or military or organization website".

I'm not sure I understand your question, but I think you are
asking a basic question about the organization of the DNS.
I.e., if we decide languages are really important, why don't we
reorganize things into a language-based hierarchy, rather than a
country-and-function-based one?

The only _technical_ answers are that it would be hard to get
there from here, and that, given the administrative nature of
the DNS delegation structure, finding a single, agreed-upon,
authority for each language would be extremely hard.  There are
also a number of administrative obstacles, not the least of
which is that many people would not agree with your opinion.

I hate to keep saying this, but your question takes me back to
what I think is the basic problem here.  The DNS was designed to
provide identifiers for computer resources, using an
administrative structure that was fairly convenient for those
computer resources.  If we need to find names, or understand
strings, along other dimensions, we are either going to need to
remove the problem from the DNS or we are going to be faced with
tradeoffs among a range of undesirable solutions.

    john




From owner-idn@ops.ietf.org  Fri Oct 26 11:21:56 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06840
	for <idn-archive@lists.ietf.org>; Fri, 26 Oct 2001 11:21:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15x8eX-000A1N-00
	for idn-data@psg.com; Fri, 26 Oct 2001 08:12:09 -0700
Received: from imo-r03.mx.aol.com ([152.163.225.99])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15x8eW-000A1F-00
	for idn@ops.ietf.org; Fri, 26 Oct 2001 08:12:09 -0700
Received: from DougEwell2@cs.com
	by imo-r03.mx.aol.com (mail_out_v31_r1.8.) id i.166.2ea4bac (3310);
	Fri, 26 Oct 2001 11:11:55 -0400 (EDT)
From: DougEwell2@cs.com
Message-ID: <166.2ea4bac.290ad741@cs.com>
Date: Fri, 26 Oct 2001 11:12:01 EDT
Subject: Re: [idn] An ignorant question about TC<-> SC
To: idn@ops.ietf.org
CC: ben@cc-www.com, duerst@w3.org, klensin@jck.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

In a message dated 2001-10-26 7:25:59 Pacific Daylight Time, ben@cc-www.com 
writes:

>  Why can't we simply label an IDN with the what language script it is in.

Be extremely careful with the words "language" and "script," and especially 
with mixing them in this way.

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Fri Oct 26 11:34:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07343
	for <idn-archive@lists.ietf.org>; Fri, 26 Oct 2001 11:34:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15x8rm-000Aj0-00
	for idn-data@psg.com; Fri, 26 Oct 2001 08:25:50 -0700
Received: from mail1.itu.ch ([156.106.192.17] helo=mail1.itu.int)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15x8rl-000Aib-00
	for idn@ops.ietf.org; Fri, 26 Oct 2001 08:25:50 -0700
Received: by mail1.itu.ch with Internet Mail Service (5.5.2650.21)
	id <V4X85MYM>; Fri, 26 Oct 2001 17:25:46 +0200
Message-ID: <B796A386E6C1D411B6FD00508B959DFE011F24DA@mailsrv4.itu.ch>
From: "Shaw, Robert" <Robert.Shaw@itu.int>
To: idn@ops.ietf.org
Subject: [idn] IDN Solution Providers Survey: please reply off list
Date: Fri, 26 Oct 2001 17:25:45 +0200
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

For research purposes, the ITU is preparing a 
survey of current or planned IDN technology 
solution providers. This is strictly an 
"agnostic survey" without any views on technology 
or administrative arrangements used.

We have identified the following technology solution 
providers:

Chinese Domain Name Consortium 
i-DNS 
NativeNames 
Neteka
Netpia 
New.net 
Realnames 
Verisign Global Registry Services 
Walid 
Worldnames 
XTNS 

If participants in the IETF's IDN WG can assist with
this list of IDN technology providers as well as 
providing relevant contact information, please forward 
them off the list to Ms. Avita Dodoo at <avita.dodoo@itu.int>.

Thanks in advance,

Robert Shaw
--
Robert Shaw <robert.shaw@itu.int>
ITU Internet Strategy and Policy Advisor
International Telecommunication Union <http://www.itu.int>
Place des Nations, 1211 Geneva, Switzerland




From owner-idn@ops.ietf.org  Fri Oct 26 12:50:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10599
	for <idn-archive@lists.ietf.org>; Fri, 26 Oct 2001 12:50:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xA1L-000DsZ-00
	for idn-data@psg.com; Fri, 26 Oct 2001 09:39:47 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xA1K-000DsT-00
	for idn@ops.ietf.org; Fri, 26 Oct 2001 09:39:46 -0700
Received: from cs881964a ([24.43.70.205]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Fri, 26 Oct 2001 09:53:16 -0700
Message-ID: <00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: <DougEwell2@cs.com>, <idn@ops.ietf.org>
Cc: <duerst@w3.org>, <klensin@jck.com>
References: <166.2ea4bac.290ad741@cs.com>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Fri, 26 Oct 2001 12:48:47 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Doug,

>
> >  Why can't we simply label an IDN with the what language script it
is in.
>
> Be extremely careful with the words "language" and "script," and
especially
> with mixing them in this way.
>

Thanks for pointing out the confusion.  Perhaps just the word "script"
is better.  To clarify what I mean, it is to label a Chinese domain
name as <idn>.<traditional> or <idn>.<simplified> (and not
<idn>.<chinese> as this serves no purpose) inorder to take out the
guess work for the CDN users.

Thanks
Ben









From owner-idn@ops.ietf.org  Fri Oct 26 13:42:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12516
	for <idn-archive@lists.ietf.org>; Fri, 26 Oct 2001 13:42:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xArQ-000GC8-00
	for idn-data@psg.com; Fri, 26 Oct 2001 10:33:36 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xArP-000GC1-00
	for idn@ops.ietf.org; Fri, 26 Oct 2001 10:33:36 -0700
Received: from [192.168.1.5] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id TAA15416;
	Fri, 26 Oct 2001 19:33:27 +0200 (MET DST)
Date: Fri, 26 Oct 2001 19:32:40 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: ben <ben@cc-www.com>, DougEwell2@cs.com, idn@ops.ietf.org
cc: duerst@w3.org, klensin@jck.com
Subject: Re: [idn] An ignorant question about TC<-> SC
Message-ID: <497812.1004124760@localhost>
In-Reply-To: <00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com>
References: <166.2ea4bac.290ad741@cs.com>
 <00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com>
X-Mailer: Mulberry/2.1.1 (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 2001-10-26 12.48 -0400 ben <ben@cc-www.com> wrote:

> Thanks for pointing out the confusion.  Perhaps just the word "script"
> is better.  To clarify what I mean, it is to label a Chinese domain
> name as <idn>.<traditional> or <idn>.<simplified> (and not
> <idn>.<chinese> as this serves no purpose) inorder to take out the
> guess work for the CDN users.

This implies that the DNS server need to know how to do matchings between
different charsets (I switch term), for example between BIG5 and some
version of GB, or between ISO-8859-1 and ISO-8859-11. Given some 1000
charsets, the server need to have huge equivalence tables, because in DNS,
we only do exact matchings.

Instead of asking the server to do all of this work, one can force the
client to translate the local charset to one and only one. The server then
only need to know how to match within that charset. And, the client only
need to know how to map from the local charset to the unified one.

We then took one more step and asked the clients to also do normalisation,
so the servers can do matchings based on direct comparison on the bits
which is the representation of the domain name itself.

   paf




From owner-idn@ops.ietf.org  Fri Oct 26 15:24:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16819
	for <idn-archive@lists.ietf.org>; Fri, 26 Oct 2001 15:24:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xCHK-000Jxl-00
	for idn-data@psg.com; Fri, 26 Oct 2001 12:04:26 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xCHJ-000Jxe-00
	for idn@ops.ietf.org; Fri, 26 Oct 2001 12:04:25 -0700
Received: from cs881964a ([24.43.70.205]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Fri, 26 Oct 2001 12:17:49 -0700
Message-ID: <010001c15e52$4cee4f20$cd462b18@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>, <DougEwell2@cs.com>,
        <idn@ops.ietf.org>
Cc: <duerst@w3.org>, <klensin@jck.com>
References: <166.2ea4bac.290ad741@cs.com> <00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com> <497812.1004124760@localhost>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Fri, 26 Oct 2001 15:13:18 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi Patrik,

Unfortunately, I am not as technically knowledgable as you are so I
rather not comment on what you have wrote.  However, what I am certain
is that you have illustrated the fact that
applications/clients/users/servers/etc can be made to take advantage
of this explicit labeling of what "script" an IDN is in and over time
(with people writing appropriate applications) can be developed into a
very powerful and useful system.  (Unlike TLD such as ".gov", ".ca"
which serves next to no purpose from an IDN's perspective.)

Thanks,
Ben


----- Original Message -----
From: "Patrik Fältström" <paf@cisco.com>
To: "ben" <ben@cc-www.com>; <DougEwell2@cs.com>; <idn@ops.ietf.org>
Cc: <duerst@w3.org>; <klensin@jck.com>
Sent: Friday, October 26, 2001 1:32 PM
Subject: Re: [idn] An ignorant question about TC<-> SC


> --On 2001-10-26 12.48 -0400 ben <ben@cc-www.com> wrote:
>
> > Thanks for pointing out the confusion.  Perhaps just the word
"script"
> > is better.  To clarify what I mean, it is to label a Chinese
domain
> > name as <idn>.<traditional> or <idn>.<simplified> (and not
> > <idn>.<chinese> as this serves no purpose) inorder to take out the
> > guess work for the CDN users.
>
> This implies that the DNS server need to know how to do matchings
between
> different charsets (I switch term), for example between BIG5 and
some
> version of GB, or between ISO-8859-1 and ISO-8859-11. Given some
1000
> charsets, the server need to have huge equivalence tables, because
in DNS,
> we only do exact matchings.
>
> Instead of asking the server to do all of this work, one can force
the
> client to translate the local charset to one and only one. The
server then
> only need to know how to match within that charset. And, the client
only
> need to know how to map from the local charset to the unified one.
>
> We then took one more step and asked the clients to also do
normalisation,
> so the servers can do matchings based on direct comparison on the
bits
> which is the representation of the domain name itself.
>
>    paf
>
>
>




From owner-idn@ops.ietf.org  Fri Oct 26 16:04:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17961
	for <idn-archive@lists.ietf.org>; Fri, 26 Oct 2001 16:04:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xCzE-000Lfu-00
	for idn-data@psg.com; Fri, 26 Oct 2001 12:49:48 -0700
Received: from inergen.sybase.com ([192.138.151.43])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xCzD-000Lfn-00
	for idn@ops.ietf.org; Fri, 26 Oct 2001 12:49:47 -0700
Received: from smtp2.sybase.com (sybgate2.sybase.com [130.214.69.6])
	by inergen.sybase.com  with ESMTP id MAA16025;
	Fri, 26 Oct 2001 12:48:48 -0700 (PDT)
Received: from olympus.sybase.com (localhost [127.0.0.1])
	by smtp2.sybase.com  with ESMTP id MAA08324;
	Fri, 26 Oct 2001 12:49:45 -0700 (PDT)
Received: from birdie.sybase.com by olympus.sybase.com (8.8.8+Sun/SMI-SVR4/SybEC3.5)
	id MAA28028; Fri, 26 Oct 2001 12:49:44 -0700 (PDT)
Received: (from kenw@localhost)
	by birdie.sybase.com (8.8.8+Sun/8.8.8) id MAA17507;
	Fri, 26 Oct 2001 12:49:44 -0700 (PDT)
Date: Fri, 26 Oct 2001 12:49:44 -0700 (PDT)
From: Kenneth Whistler <kenw@sybase.com>
Message-Id: <200110261949.MAA17507@birdie.sybase.com>
To: ben@cc-www.com
Subject: Re: [idn] An ignorant question about TC<-> SC
Cc: idn@ops.ietf.org
X-Sun-Charset: US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Ben said:

>  However, what I am certain
> is that you have illustrated the fact that
> applications/clients/users/servers/etc can be made to take advantage
> of this explicit labeling of what "script" an IDN is in and over time
> (with people writing appropriate applications) can be developed into a
> very powerful and useful system.  (Unlike TLD such as ".gov", ".ca"
> which serves next to no purpose from an IDN's perspective.)

I have to disagree. I am certain that labelling what script an
IDN is in will just cause problems.

At the very least, this will introduce an entire new class of
error conditions, where the label says one thing, but the
character content of the IDN does not in fact match the label.

Furthermore, the example we have been talking about here,
traditional versus simplified Chinese, is not even a script
difference in the first place. "Traditional" versus "Simplified"
in a character set context, and as typically implemented,
refers to distinctions between Code Page 950 (Big 5) and
Code Page 936 (GBK, etc.), together with the fonts, input methods,
message resource files, and such, as needed
to support them. And either of those character sets is actually
mixed script, since they both support Latin characters from
ASCII, as well as the basic Greek alphabet and Bopomofo.
"Simplified Chinese" also supports the basic Cyrillic alphabet
and Hiragana and Katakana for Japanese.

Even if you are just talking about Traditional versus
Simplified Chinese characters (ideographs) within the
Han script subparts of Code Page 950 or Code Page 936, the
distinction is not as clean as you might think it would be.
The PRC simplified set, even in its earlier forms in GB 2312,
contain *some* traditional forms for characters. But the
current extensions, first for GBK (~ Microsoft Code Page 936),
and now for GB 18030, incorporate *all* of the Han characters
from the Unicode 3.0 repertoire, which means that a
"Simplified" code page for China now contains *all* of the
traditional characters from Code Page 950, as well as all
the simplified characters from Unicode 3.0.

And of course, Unicode data itself encompasses both simplified
and traditional forms of Chinese ideographs. So what would the
IDN distinction between simplified and traditional mean if
data was encoded in Unicode?

Even the identification of scripts is non-trivial. Many
characters are *shared* between scripts, or are borrowed
from one script to the next. Cyrillic and Latin have a long
history of cross-borrowing forms from one script into the
other, for example, for special uses. And Japanese got all
its Chinese characters (kanji) in the first place by
borrowing them from Chinese.

See the Unicode Technical Report #24 Script Names, for more
discussion of this:

http://www.unicode.org/unicode/reports/tr24/

Note, in particular, that "Traditional (Chinese)" and
"Simplified (Chinese)" are nowhere mentioned in that report --
those are simply not script distinctions.

--Ken




From owner-idn@ops.ietf.org  Fri Oct 26 18:25:06 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20110
	for <idn-archive@lists.ietf.org>; Fri, 26 Oct 2001 18:25:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xFEL-0000os-00
	for idn-data@psg.com; Fri, 26 Oct 2001 15:13:33 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xFEK-0000oc-00
	for idn@ops.ietf.org; Fri, 26 Oct 2001 15:13:32 -0700
Received: from cs881964a ([24.43.70.205]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Fri, 26 Oct 2001 15:27:01 -0700
Message-ID: <011701c15e6c$b70f59c0$cd462b18@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "Kenneth Whistler" <kenw@sybase.com>
Cc: <idn@ops.ietf.org>
References: <200110261949.MAA17507@birdie.sybase.com>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Fri, 26 Oct 2001 18:22:21 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Ken,

Thanks for your input and below are my reponses:

> I have to disagree. I am certain that labelling what script an
> IDN is in will just cause problems.
>

It will *never* cause any problems because the script labelling of an
IDN by itself does not do anything.  The worst case is that it is just
part of the domain name that serves absolutely no purpose (like ".ca"
serves no purpose).  However, if and when people decide to make use of
it, then it becomes a very powerful system.

> At the very least, this will introduce an entire new class of
> error conditions, where the label says one thing, but the
> character content of the IDN does not in fact match the label.
>

With a .<traditional> label, if the IDN is entered as simplified
Chinese, then either an error will appear to alert the user or the
simplified Chinese will be converted automatically to traditional
Chinese.  An IDN that end with ".ca" abviously cannot provide such a
benefit.

> Furthermore, the example we have been talking about here,
> traditional versus simplified Chinese, is not even a script
> difference in the first place. "Traditional" versus "Simplified"
> in a character set context, and as typically implemented,
> refers to distinctions between Code Page 950 (Big 5) and
> Code Page 936 (GBK, etc.), together with the fonts, input methods,
> message resource files, and such, as needed
> to support them. And either of those character sets is actually
> mixed script, since they both support Latin characters from
> ASCII, as well as the basic Greek alphabet and Bopomofo.
> "Simplified Chinese" also supports the basic Cyrillic alphabet
> and Hiragana and Katakana for Japanese.
>

Depite how certain input method/tables/encodings/files/application/etc
may support others, simplified Chinese is simplified Chinese and
traditional Chinese is traditional Chinese- there are no Greek, no
Japanese, no English, and no funny symbols.

> Even if you are just talking about Traditional versus
> Simplified Chinese characters (ideographs) within the
> Han script subparts of Code Page 950 or Code Page 936, the
> distinction is not as clean as you might think it would be.
> The PRC simplified set, even in its earlier forms in GB 2312,
> contain *some* traditional forms for characters. But the
> current extensions, first for GBK (~ Microsoft Code Page 936),
> and now for GB 18030, incorporate *all* of the Han characters
> from the Unicode 3.0 repertoire, which means that a
> "Simplified" code page for China now contains *all* of the
> traditional characters from Code Page 950, as well as all
> the simplified characters from Unicode 3.0.
>

This is a good point.  It serves to illustrate how the line between
Traditional Chinese and Simplified Chinese is getting more blurred
because they are used so often interchangeably- hence the need for
TC<->SC conversion.  However, if you are trying to say that there is
no distinction between them because GBK/GB18030 has incorporated
everything then you are absolutely incorrect.  Traditional Chinese is
traditional Chinese and simplifed Chinese is simplified Chinese.

> And of course, Unicode data itself encompasses both simplified
> and traditional forms of Chinese ideographs. So what would the
> IDN distinction between simplified and traditional mean if
> data was encoded in Unicode?
>
> Even the identification of scripts is non-trivial. Many
> characters are *shared* between scripts, or are borrowed
> from one script to the next. Cyrillic and Latin have a long
> history of cross-borrowing forms from one script into the
> other, for example, for special uses. And Japanese got all
> its Chinese characters (kanji) in the first place by
> borrowing them from Chinese.
>

Characters that share the same Unicode can definitely be labeled as
different scripts- whether it is Chinese or Japanese or any other.
(Much like "same.com" and "same.ca".)  The benefit for this IDN
distinction should be obvious as the same character (with the same
unicode) may have completely  different meaning in different scripts.
One labeled as <same>.<traditional> (written in Traditional Chinese
ofcourse) and the other labeled as <same>.<simplified> (written in
Simplfied Chinese).


Thanks
Ben






From owner-idn@ops.ietf.org  Fri Oct 26 22:49:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23771
	for <idn-archive@lists.ietf.org>; Fri, 26 Oct 2001 22:49:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xJH1-0009zc-00
	for idn-data@psg.com; Fri, 26 Oct 2001 19:32:35 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xJGy-0009zF-00
	for idn@ops.ietf.org; Fri, 26 Oct 2001 19:32:34 -0700
Received: from test12345 ([140.115.6.240])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f9R2bjV06951;
	Sat, 27 Oct 2001 10:37:45 +0800 (CST)
Message-ID: <007101c15e8e$cc0919c0$f006738c@ncu.edu.tw>
From: =?UTF-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: =?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@cisco.com>,
        "ben" <ben@cc-www.com>, <DougEwell2@cs.com>, <idn@ops.ietf.org>
Cc: <duerst@w3.org>, <klensin@jck.com>
References: <166.2ea4bac.290ad741@cs.com> <00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com> <497812.1004124760@localhost>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Sat, 27 Oct 2001 10:26:30 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi !  Mr. Patrik Fältström:
        The problems of TC/SC in IDN come from the large amount of  chinese
SC characters which are derived from TC coexisted in UNICODE  table.
1. The SC announced in 7, March,1964 from PRC and re-announced in 24, June,
1986 are all characters in quick-written form which are derived from
original TC and most of them are the same meaning and used only in PRC.
These SC/TC characters are listed in "Total Table of  Simplified Characters"
in the announced documents.  In Taiwan , we have one  variants dictionary
related to Chinese, Japanese, Korean  in our web sites of Ministry of
Education .
http://140.111.1.40/fulu/fu5/fu6.htm
        CJK characters have about 4000 most-frequently-used characters , a
lot of TC/SC are in these catagory. If we remove some SC that are common
used in Japan(about 123 characters in PRC announced total table ) and all
1-n mapping characters,  there still have about 2000 pairs of
PRC-only-SC/TC 1-1 mapping characters. The probability of mixed TC/SC with
the same meanning will be very high.  As IDN is the identifier name in DNS ,
the confusing caused by using the same meanning  SC to replace the same
meanning TC from user will  let chinese IDN in troubles.
2. The SC, TC are co-existed for printing and display , they can not be
unified or one-way mapped (normalized) to one representaive code-point.
Because Japan, Taiwan, Korean use the TC part in their normal-written form.
On the other side, China use the SC part in quick-written form, but HK and
Mo will  use TC/SC mixed . TC/SC have different code points , so, it cause
the problems of  2^N registration records and consistency of  NS delegation.
3. TC/SC MUST be coded in bi-directional way to support
may-be-recoverable-display and comparison without care 1-1 mapped TC/SC in
LDH-DNS server.  It  MUST NOT be solved by forced-translating to one of
TC/SC.

L.M.Tseng

----- Original Message -----
From: "Patrik Fältström" <paf@cisco.com>


> --On 2001-10-26 12.48 -0400 ben <ben@cc-www.com> wrote:
>
> Instead of asking the server to do all of this work, one can force the
> client to translate the local charset to one and only one. The server then
> only need to know how to match within that charset. And, the client only
> need to know how to map from the local charset to the unified one.
>
> We then took one more step and asked the clients to also do normalisation,
> so the servers can do matchings based on direct comparison on the bits
> which is the representation of the domain name itself.
>
>    paf
>
>




From owner-idn@ops.ietf.org  Sat Oct 27 03:28:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10734
	for <idn-archive@lists.ietf.org>; Sat, 27 Oct 2001 03:28:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xNep-000KPd-00
	for idn-data@psg.com; Sat, 27 Oct 2001 00:13:27 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xNeo-000KPX-00
	for idn@ops.ietf.org; Sat, 27 Oct 2001 00:13:26 -0700
Received: from [192.168.1.5] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id JAA27502;
	Sat, 27 Oct 2001 09:12:55 +0200 (MET DST)
Date: Sat, 27 Oct 2001 08:58:45 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: "=?UTF-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?=" <tsenglm@cc.ncu.edu.tw>,
        ben <ben@cc-www.com>, DougEwell2@cs.com, idn@ops.ietf.org
cc: duerst@w3.org, klensin@jck.com
Subject: Re: [idn] An ignorant question about TC<-> SC
Message-ID: <3399691.1004173125@localhost>
In-Reply-To: <007101c15e8e$cc0919c0$f006738c@ncu.edu.tw>
References: <166.2ea4bac.290ad741@cs.com>
 <00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com>
 <497812.1004124760@localhost> <007101c15e8e$cc0919c0$f006738c@ncu.edu.tw>
X-Mailer: Mulberry/2.1.1 (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-10-27 10.26 +0800
"=?UTF-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?="
<tsenglm@cc.ncu.edu.tw> wrote:

> It  MUST NOT be solved by forced-translating to one of
> TC/SC.

I have not said it should. I like and appreciate the recommendation the
Unicode Consortium gave the IETF, and that is to _NOT_ do unification of
TC/SC or even try to come up with matching rules.

Instead, multiple registrations in DNS, one for the SC and one for the TC
version is recommended.

   paf




From owner-idn@ops.ietf.org  Sat Oct 27 03:29:38 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10747
	for <idn-archive@lists.ietf.org>; Sat, 27 Oct 2001 03:29:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xNeO-000KPL-00
	for idn-data@psg.com; Sat, 27 Oct 2001 00:13:00 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xNeN-000KPF-00
	for idn@ops.ietf.org; Sat, 27 Oct 2001 00:12:59 -0700
Received: from [192.168.1.5] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id JAA27498;
	Sat, 27 Oct 2001 09:12:50 +0200 (MET DST)
Date: Sat, 27 Oct 2001 08:54:40 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: ben <ben@cc-www.com>, DougEwell2@cs.com, idn@ops.ietf.org
cc: duerst@w3.org, klensin@jck.com
Subject: Re: [idn] An ignorant question about TC<-> SC
Message-ID: <3384987.1004172880@localhost>
In-Reply-To: <010001c15e52$4cee4f20$cd462b18@mtag1.on.home.com>
References: <166.2ea4bac.290ad741@cs.com>
 <00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com>
 <497812.1004124760@localhost>
 <010001c15e52$4cee4f20$cd462b18@mtag1.on.home.com>
X-Mailer: Mulberry/2.1.1 (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-10-26 15.13 -0400 ben <ben@cc-www.com> wrote:

> However, what I am certain
> is that you have illustrated the fact that
> applications/clients/users/servers/etc can be made to take advantage
> of this explicit labeling of what "script" an IDN is in and over time
> (with people writing appropriate applications) can be developed into a
> very powerful and useful system.

No, you misunderstood. It is exactly the contrary.

Comparison of characters from two different charsets is extremely
difficult. It can not be done effectively for all combination of charsets.

Only way of dealing with this problem is to map each of the two charsets to
one, and then use comparison rules for that charset.

This is the model which works in DNS, and that is why this wg have chose
this path. This has already been discussed, and discussing this again
doesn't help this wg make progress.

IF you want to start to tag a string (in whatever charset) with meta
information such as language, geographical location of creator of the data,
date and time when the string was created, and use this information when
you do a matching decision, then you talk about something different than
DNS, something which looks like a keyword system. John Klensin has
described such systems in drafts which have circulated on this list.

    paf





From owner-idn@ops.ietf.org  Sat Oct 27 10:45:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14000
	for <idn-archive@lists.ietf.org>; Sat, 27 Oct 2001 10:45:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xUMD-000968-00
	for idn-data@psg.com; Sat, 27 Oct 2001 07:22:41 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xUMC-00095t-00
	for idn@ops.ietf.org; Sat, 27 Oct 2001 07:22:40 -0700
Received: from cs881964a ([24.43.70.205]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Sat, 27 Oct 2001 07:36:07 -0700
Message-ID: <003301c15ef4$23a48420$cd462b18@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>, <DougEwell2@cs.com>,
        <idn@ops.ietf.org>
Cc: <duerst@w3.org>, <klensin@jck.com>
References: <166.2ea4bac.290ad741@cs.com> <00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com> <497812.1004124760@localhost> <010001c15e52$4cee4f20$cd462b18@mtag1.on.home.com> <3384987.1004172880@localhost>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Sat, 27 Oct 2001 10:31:45 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi Patrik,

I am not doing a good job in explaining my idea.  I am working on
actually setting up the entire system (for testing and data gathering
purposes) and I will let you know when it is completed so that you can
see exactly what I mean.

Thanks
Ben



----- Original Message -----
From: "Patrik Fältström" <paf@cisco.com>
To: "ben" <ben@cc-www.com>; <DougEwell2@cs.com>; <idn@ops.ietf.org>
Cc: <duerst@w3.org>; <klensin@jck.com>
Sent: Saturday, October 27, 2001 2:54 AM
Subject: Re: [idn] An ignorant question about TC<-> SC


> --On 01-10-26 15.13 -0400 ben <ben@cc-www.com> wrote:
>
> > However, what I am certain
> > is that you have illustrated the fact that
> > applications/clients/users/servers/etc can be made to take
advantage
> > of this explicit labeling of what "script" an IDN is in and over
time
> > (with people writing appropriate applications) can be developed
into a
> > very powerful and useful system.
>
> No, you misunderstood. It is exactly the contrary.
>
> Comparison of characters from two different charsets is extremely
> difficult. It can not be done effectively for all combination of
charsets.
>
> Only way of dealing with this problem is to map each of the two
charsets to
> one, and then use comparison rules for that charset.
>
> This is the model which works in DNS, and that is why this wg have
chose
> this path. This has already been discussed, and discussing this
again
> doesn't help this wg make progress.
>
> IF you want to start to tag a string (in whatever charset) with meta
> information such as language, geographical location of creator of
the data,
> date and time when the string was created, and use this information
when
> you do a matching decision, then you talk about something different
than
> DNS, something which looks like a keyword system. John Klensin has
> described such systems in drafts which have circulated on this list.
>
>     paf
>
>
>




From owner-idn@ops.ietf.org  Sat Oct 27 15:30:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16056
	for <idn-archive@lists.ietf.org>; Sat, 27 Oct 2001 15:30:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xYnZ-000Ixf-00
	for idn-data@psg.com; Sat, 27 Oct 2001 12:07:13 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xYnY-000IxY-00
	for idn@ops.ietf.org; Sat, 27 Oct 2001 12:07:12 -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 MAA17715
	for <idn@ops.ietf.org>; Sat, 27 Oct 2001 12:07:11 -0700
Message-Id: <5.1.0.14.2.20011027084819.03d3b6c0@brandenburg.com>
X-Sender: dcrocker@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sat, 27 Oct 2001 12:09:23 -0700
To: idn@ops.ietf.org
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: [idn] iDNS re-chartering proposal, take 2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Folks,

Perhaps the most important goals in re-chartering this effort are to:

         1.  Narrow the scope of work

         2.  Specify deliverables very precisely

         3.  Specify dates for deliverable that are very near-term.

This should make it easier to distinguish what is in-scope and what is not, 
as well as help the group focus on tasks that must be done soon.

Note the reference to near-term.  This eliminates discussion about work to 
be done in the future.  The issue is not that the work is not important, 
but that discussion about future work  gets in the way of discussion about 
current work, for producing something useful NOW.  When the working group 
has satisfied near-term requirements, it will be free to consider 
re-chartering for longer-term goals.

With these factors in mind, I offer some modifications to the proposed new 
charter.  The modifications are intended to:

1.  Make the opening paragraph comprehensive, so that it is useful by 
itself.  The first paragraph of a working group charter is distributed as 
an "abstract" of the charter.  That means it should summarize the problem, 
summarize the nature of the work to be done, summarize the technical 
approach, and possibly summarize the resulting benefit from the work.

2.  Focus on the production of a single technical specification to be 
offered as a standard.  Hence the working group is no longer exploring, 
researching or otherwise having broad discussions.

3.  Ensure the quickest possible milestones for delivering a specification 
that is immediately useful and will produce DNS changes that also are 
immediately useful.  This will reflect the past two years of discussion.

4.  Modify terminology a little bit, to reflect our better understanding of 
the task that is to be done.  This should help people avoid discussing 
issues that are not really helpful to the working group task.  It also 
should help people understand that we are specifying character codes, 
rather than anything as broad and amorphous as "access".


So, here is the proposed, modified re-chartering text:


Domain Names are Internet identifiers. They are used both for machine and 
human processing, so the form of a Domain Name must be convenient for both 
processing venues.  The current set of valid Domain Name characters is 
limited to common Internet ASCII, which is inadequate for the broad range 
of Internet human users.  This working group will produce a standards-track 
specification for extending the range of characters that can be used in 
Domain Names, by humans.  The enhancement will be designed to minimize 
changes to existing Domain Name software and operations.  In particular, 
changes to the DNS infrastructure of storage and exchange mechanisms will 
be avoided.

The technical approach for the current specification effort shall be to 
permit use of international character sets, as recommended by the IAB, and 
then encode the characters, to permit their transmission and storage within 
existing DNS mechanisms.  Hence this enhancement to the DNS involves only 
end-user software.  In particular software that needs to be changed is 
restricted to:  Human DNS input and output modules.  No other modules will 
need to be changed.

Language information is not encoded in these identifiers.  That is, "names" 
from different languages are defined in a single namespace.

The group will not address the question of what, if any, body should 
administer or control usage of names that use this functionality.

The group will identify consequences to the current deployed DNS 
infrastructure, the protocols and the applications as well as transition 
scenarios, where applicable.

The working group will actively ensure communication with interested groups 
who are studying the same, or related, topics.


Working Group action items are:

1. An Informational RFC documenting considerations for supporting 
International character sets in domain names. The document will discuss 
factors used to develop solutions to this problem, taking localized (e.g. 
writing order) and related operational issues into consideration.

    [[[  Question:  Why must we discuss writing order at all?  /Dave   ]]]

2. A standards track specification for internationalized domain name 
strings, to be used by humans, including specifying any transition issues.


The Action Item(s) for the Working Group are:

1.  An Informational RFC specifying the requirements for providing 
International character sets in domain names. The document should provide 
guidance for developing solutions to this problem, taking localized (e.g. 
writing order) and related operational issues into consideration.

2.  A standard track specification on permitting international characters 
in domain names, including specifying any transition issues.

3.  A standard track specification on an ASCII Compatible Encoding (ACE), 
to be used in the standard track specification on permitting international 
characters in domain names.

4.  A standard track specification on normalization of domain name 
identifiers for the purpose of string comparisons. This document may 
includes case folding, map outs, and prohibited characters.


Goal & Milestone:

Nov 2001        Draft of architecture relating input methods, namepreps
                 and zonefiles
Nov 2001        Draft of ACE specification
Nov 2001        Draft of DNS identifier normalization specification
Nov 2001        Draft of DNS character set enhancement specification
Jan 2002        Architecture draft submitted for informational publication
Jan 2002        ACE specification submitted for standardization
Jan 2002        DNS identifier normalization specification submitted
                 for standardization
Jan 2002        DNS Character set enhancement specification submitted
                 for standardization



----------
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  Sat Oct 27 17:19:17 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16725
	for <idn-archive@lists.ietf.org>; Sat, 27 Oct 2001 17:19:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xah6-000NKn-00
	for idn-data@psg.com; Sat, 27 Oct 2001 14:08:40 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xah5-000NKb-00
	for idn@ops.ietf.org; Sat, 27 Oct 2001 14:08:39 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9RLACr43867;
	Sat, 27 Oct 2001 17:10:12 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110272110.f9RLACr43867@nic-naa.net>
To: Dave Crocker <dcrocker@brandenburg.com>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] iDNS re-chartering proposal, take 2 
In-Reply-To: Your message of "Sat, 27 Oct 2001 12:09:23 PDT."
             <5.1.0.14.2.20011027084819.03d3b6c0@brandenburg.com> 
Date: Sat, 27 Oct 2001 17:10:12 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dave,

...
>    [[[  Question:  Why must we discuss writing order at all?  /Dave   ]]]
...

Because of the Colourd Books (JANET) experience, leakage, and a strong
preference for reverse ordering by large numbers of users for whom the
wee.small.mid.big.top identifier odering is as counter-intuitive as 
identifiers-in-ASCII.

Eric



From owner-idn@ops.ietf.org  Sat Oct 27 19:26:20 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17246
	for <idn-archive@lists.ietf.org>; Sat, 27 Oct 2001 19:26:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xcQB-0001HP-00
	for idn-data@psg.com; Sat, 27 Oct 2001 15:59:19 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xcQA-0001HJ-00
	for idn@ops.ietf.org; Sat, 27 Oct 2001 15:59:18 -0700
Received: from bbprime.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 PAA24700;
	Sat, 27 Oct 2001 15:59:14 -0700
Message-Id: <5.1.0.14.2.20011027154624.02025830@brandenburg.com>
X-Sender: dcrocker@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sat, 27 Oct 2001 15:55:43 -0700
To: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: Re: [idn] iDNS re-chartering proposal, take 2 
Cc: idn@ops.ietf.org, brunner@nic-naa.net
In-Reply-To: <200110272110.f9RLACr43867@nic-naa.net>
References: <Your message of "Sat, 27 Oct 2001 12:09:23 PDT." <5.1.0.14.2.20011027084819.03d3b6c0@brandenburg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 02:10 PM 10/27/2001, Eric Brunner-Williams in Portland Maine wrote:
> >    [[[  Question:  Why must we discuss writing order at all?  /Dave   ]]]
>
>Because of the Colourd Books (JANET) experience, leakage, and a strong
>preference for reverse ordering by large numbers of users for whom the
>wee.small.mid.big.top identifier odering is as counter-intuitive as
>identifiers-in-ASCII.


Hmmm.  Let me try to understand this, by starting from a really simple, 
really naive perspective:

         The registrant specifies a Domain Name that is series of 
characters. The characters are in whatever order the registrant chooses to 
put them.

         Translating them into ACE preserves the order.  The registrar and 
registry are preserve the order.  All other DNS processing modules preserve 
that order.

         The final module translates out of ACE, still preserving the order.

So it seems to me that the only job for the DNS international character set 
specifications is to make sure that the end-to-end behavior of the system 
is to preserve whatever ordering the registrant provided.

And now you, and others, can explain to me what it is that I am missing.

Encouragingly yours,

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  Sat Oct 27 22:37:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19974
	for <idn-archive@lists.ietf.org>; Sat, 27 Oct 2001 22:37:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xfSf-00087I-00
	for idn-data@psg.com; Sat, 27 Oct 2001 19:14:05 -0700
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xfSZ-000876-00
	for idn@ops.ietf.org; Sat, 27 Oct 2001 19:14:04 -0700
Received: from deng ([159.226.7.68]) by whale.cnnic.net.cn
          (Netscape Messaging Server 4.15) with SMTP id GLW8XR00.O1M; Sun,
          28 Oct 2001 10:15:27 +0800 
Message-ID: <003301c15f55$16f5a220$4407e29f@deng>
From: "xiang deng" <deng@cnnic.net.cn>
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        =?ISO-8859-1?B?dHNlbmdsbUDoqF7ntrLkuK3lv2Yu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>,
        "ben" <ben@cc-www.com>, <DougEwell2@cs.com>, <idn@ops.ietf.org>
Cc: <duerst@w3.org>, <klensin@jck.com>
References: <166.2ea4bac.290ad741@cs.com><00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com><497812.1004124760@localhost> <007101c15e8e$cc0919c0$f006738c@ncu.edu.tw> <3399691.1004173125@localhost>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Sun, 28 Oct 2001 10:06:00 +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 WAA19974


On  Saturday, October 27, 2001 2:58 PM, Patrik Fältström wrote:

 
> > It  MUST NOT be solved by forced-translating to one of
> > TC/SC.
> 
> I have not said it should. I like and appreciate the recommendation the
> Unicode Consortium gave the IETF, and that is to _NOT_ do unification of
> TC/SC or even try to come up with matching rules.
> 
> Instead, multiple registrations in DNS, one for the SC and one for the TC
> version is recommended.

Yes, multiple registrations in DNS is better than do nothing. 
But, there are still some problems can not solve:
1). Just do one for the SC and one for the TC, it isn't enough. Because other 
person can register mixed TC/SC domain name. How to deal with the disputations of
registration. Such disputations will not disappear, if we have no real solution about it.
it's policy issue.

2). multiple registrations in DNS can solve a part of the issue, How to solve the 
delegation issue of subdomain and keep the consistency. 
it's technology issue.

3). if we provide multiple registration solution for customs, we must guarantee the multiple
records belong to one custom. but from technology view, we can not guarantee it.

Deng xiang 




From owner-idn@ops.ietf.org  Sat Oct 27 22:50:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20088
	for <idn-archive@lists.ietf.org>; Sat, 27 Oct 2001 22:50:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xfrF-0008za-00
	for idn-data@psg.com; Sat, 27 Oct 2001 19:39:29 -0700
Received: from smtp11.singnet.com.sg ([165.21.6.31])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xfrE-0008zS-00
	for idn@ops.ietf.org; Sat, 27 Oct 2001 19:39:28 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp11.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9S2biP06880;
	Sun, 28 Oct 2001 10:37:44 +0800 (SGT)
Message-ID: <000701c15f59$89cdf9b0$1c01000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "xiang deng" <deng@cnnic.net.cn>,
        =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        =?iso-8859-1?B?dHNlbmdsbUDoqF7ntrLkuK3lv2Yu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>,
        "ben" <ben@cc-www.com>, <DougEwell2@cs.com>, <idn@ops.ietf.org>
Cc: <duerst@w3.org>, <klensin@jck.com>
References: <166.2ea4bac.290ad741@cs.com><00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com><497812.1004124760@localhost> <007101c15e8e$cc0919c0$f006738c@ncu.edu.tw> <3399691.1004173125@localhost> <003301c15f55$16f5a220$4407e29f@deng>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Sun, 28 Oct 2001 10:37:50 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Yes, multiple registrations in DNS is better than do nothing.
> But, there are still some problems can not solve:
> 1). Just do one for the SC and one for the TC, it isn't enough.
Because other
> person can register mixed TC/SC domain name. How to deal with the
disputations of
> registration. Such disputations will not disappear, if we have no real
solution about it.
> it's policy issue.

Such mixed TC/SC is possible but not useful in practice. It is neither
"TC" or "SC" and using it is fairly complex to use. Perhaps some
statistic of how many such TC/SC mixed label been registered in practice
will be useful.

> 2). multiple registrations in DNS can solve a part of the issue, How
to solve the
> delegation issue of subdomain and keep the consistency.
> it's technology issue.

Agree.

> 3). if we provide multiple registration solution for customs, we must
guarantee the multiple
> records belong to one custom. but from technology view, we can not
guarantee it.

I presumed you mean from a "policy view", not technology because if we
cannot guarantee from technology view, ie there is no technology, then
we cannot do so in IDN anyway

-James Seng




From owner-idn@ops.ietf.org  Sat Oct 27 23:00:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20186
	for <idn-archive@lists.ietf.org>; Sat, 27 Oct 2001 23:00:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xg1d-0009Qb-00
	for idn-data@psg.com; Sat, 27 Oct 2001 19:50:13 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xg1T-0009Nl-00
	for idn@ops.ietf.org; Sat, 27 Oct 2001 19:50:03 -0700
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id DFB617F4DF; Sun, 28 Oct 2001 11:49:40 +0900 (JST)
Message-Id: <4.2.0.58.J.20011028103527.03a361f0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Sun, 28 Oct 2001 11:16:39 +0900
To: Dave Crocker <dcrocker@brandenburg.com>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] iDNS re-chartering proposal, take 2
In-Reply-To: <5.1.0.14.2.20011027084819.03d3b6c0@brandenburg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Just a few comments:

At 12:09 01/10/27 -0700, Dave Crocker wrote:
>Folks,
>
>Perhaps the most important goals in re-chartering this effort are to:
>
>         1.  Narrow the scope of work
>
>         2.  Specify deliverables very precisely
>
>         3.  Specify dates for deliverable that are very near-term.
>
>This should make it easier to distinguish what is in-scope and what is 
>not, as well as help the group focus on tasks that must be done soon.
>
>Note the reference to near-term.  This eliminates discussion about work to 
>be done in the future.  The issue is not that the work is not important, 
>but that discussion about future work  gets in the way of discussion about 
>current work, for producing something useful NOW.  When the working group 
>has satisfied near-term requirements, it will be free to consider 
>re-chartering for longer-term goals.
>
>With these factors in mind, I offer some modifications to the proposed new 
>charter.  The modifications are intended to:
>
>1.  Make the opening paragraph comprehensive, so that it is useful by 
>itself.  The first paragraph of a working group charter is distributed as 
>an "abstract" of the charter.  That means it should summarize the problem, 
>summarize the nature of the work to be done, summarize the technical 
>approach, and possibly summarize the resulting benefit from the work.
>
>2.  Focus on the production of a single technical specification to be 
>offered as a standard.  Hence the working group is no longer exploring, 
>researching or otherwise having broad discussions.
>
>3.  Ensure the quickest possible milestones for delivering a specification 
>that is immediately useful and will produce DNS changes that also are 
>immediately useful.  This will reflect the past two years of discussion.
>
>4.  Modify terminology a little bit, to reflect our better understanding 
>of the task that is to be done.  This should help people avoid discussing 
>issues that are not really helpful to the working group task.  It also 
>should help people understand that we are specifying character codes, 
>rather than anything as broad and amorphous as "access".
>
>
>So, here is the proposed, modified re-chartering text:
>
>
>Domain Names are Internet identifiers. They are used both for machine and 
>human processing, so the form of a Domain Name must be convenient for both 
>processing venues.  The current set of valid Domain Name characters is 
>limited to common Internet ASCII, which is inadequate for the broad range 
>of Internet human users.  This working group will produce a standards-track

Internet human users -> human Internet users


>specification for extending the range of characters that can be used in 
>Domain Names, by humans.  The enhancement will be designed to minimize 
>changes to existing Domain Name software and operations.  In particular, 
>changes to the DNS infrastructure of storage and exchange mechanisms will 
>be avoided.
>
>The technical approach for the current specification effort shall be to 
>permit use of international character sets, as recommended by the IAB, and

character sets -> characters
(or even better, international character sets -> non-ASCII characters)

Character set is a very ambiguous term, and in some of its meanings,
may give the wrong impression.


>then encode the characters, to permit their transmission and storage 
>within existing DNS mechanisms.  Hence this enhancement to the DNS 
>involves only end-user software.  In particular software that needs to be 
>changed is restricted to:  Human DNS input and output modules.

Please be careful here. Assume somebody has software that allows to
find all domain names with the string 'FOO' in it, where 'FOO' isn't
necessarily a full label. Now assume this software should work with
idns, too. Can we do that by just changing the input module
(e.g. we just encoded 'FOO' as ace? We can't.

Also, assume that a protocol specifies that domain names be in
UTF-8 (or something else), or that a program decides to use
Unicode internally. Then the term 'Human DNS input and output'
seems to be rather inappropriate.


>No other modules will need to be changed.
>
>Language information is not encoded in these identifiers.  That is, 
>"names" from different languages are defined in a single namespace.
>
>The group will not address the question of what, if any, body should 
>administer or control usage of names that use this functionality.
>
>The group will identify consequences to the current deployed DNS 
>infrastructure, the protocols and the applications as well as transition 
>scenarios, where applicable.
>
>The working group will actively ensure communication with interested 
>groups who are studying the same, or related, topics.

This is a good point. Has this been done up to now (actively)?
Or is this new? What would these groups be?


>Working Group action items are:
>
>1. An Informational RFC documenting considerations for supporting 
>International character sets in domain names. The document will discuss 
>factors used to develop solutions to this problem, taking localized (e.g. 
>writing order) and related operational issues into consideration.
>
>    [[[  Question:  Why must we discuss writing order at all?  /Dave   ]]]

The problem Eric has mentioned is one problem, but actually the easier
one. The sequence of labels is something anyone can get used to.

The more serious problem is bidirectionality (Arabic, Hebrew).
For some more details of the problem and one possible solution, see e.g.
http://www.ietf.org/internet-drafts/draft-duerst-iri-bidi-00.txt.

After an informal 'bof' in Sept. at the Unicode Conference in San
Jose, Paul also set up a mailing list for discussion.

It's quite important that we solve this problem here, because:
- Many people who understand (part of) this problem have a serious
   hunch that there is some connection between this and nameprep.
- If we don't clearly say how this works, we will get various
   different solutions, with a complete chaos (i.e. no defined
   mapping) between what people see/write down and what is stored.


>2. A standards track specification for internationalized domain name 
>strings, to be used by humans, including specifying any transition issues.
>
>
>The Action Item(s) for the Working Group are:

What's the difference between

"Working Group action items are:" and
"The Action Item(s) for the Working Group are:"


>1.  An Informational RFC specifying the requirements for providing 
>International character sets in domain names. The document should provide 
>guidance for developing solutions to this problem, taking localized (e.g. 
>writing order) and related operational issues into consideration.
>
>2.  A standard track specification on permitting international characters 
>in domain names, including specifying any transition issues.
>
>3.  A standard track specification on an ASCII Compatible Encoding (ACE), 
>to be used in the standard track specification on permitting international 
>characters in domain names.
>
>4.  A standard track specification on normalization of domain name 
>identifiers for the purpose of string comparisons. This document may 
>includes case folding, map outs, and prohibited characters.

may includes -> may include



>Goal & Milestone:
>
>Nov 2001        Draft of architecture relating input methods, namepreps
>                 and zonefiles
>Nov 2001        Draft of ACE specification
>Nov 2001        Draft of DNS identifier normalization specification
>Nov 2001        Draft of DNS character set enhancement specification

'Character set enhancement' is a very weird term. This is the
IDNA spec, isn't it? Using the word 'architecture' in a generic
name would be better, I guess.


>Jan 2002        Architecture draft submitted for informational publication
>Jan 2002        ACE specification submitted for standardization
>Jan 2002        DNS identifier normalization specification submitted
>                 for standardization
>Jan 2002        DNS Character set enhancement specification submitted
>                 for standardization

Regards,  Martin.



From owner-idn@ops.ietf.org  Sat Oct 27 23:48:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21303
	for <idn-archive@lists.ietf.org>; Sat, 27 Oct 2001 23:48:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xgd1-000AlN-00
	for idn-data@psg.com; Sat, 27 Oct 2001 20:28:51 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xgd0-000AlB-00
	for idn@ops.ietf.org; Sat, 27 Oct 2001 20:28:50 -0700
Received: from bbprime.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 UAA32327;
	Sat, 27 Oct 2001 20:28:48 -0700
Message-Id: <5.1.0.14.2.20011027202302.03a94958@brandenburg.com>
X-Sender: dcrocker@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sat, 27 Oct 2001 20:28:32 -0700
To: Martin Duerst <duerst@w3.org>
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: Re: [idn] iDNS re-chartering proposal, take 2
Cc: idn@ops.ietf.org
In-Reply-To: <4.2.0.58.J.20011028103527.03a361f0@localhost>
References: <5.1.0.14.2.20011027084819.03d3b6c0@brandenburg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 08:16 PM 10/27/2001, Martin Duerst wrote:
>At 12:09 01/10/27 -0700, Dave Crocker wrote:
>>then encode the characters, to permit their transmission and storage 
>>within existing DNS mechanisms.  Hence this enhancement to the DNS 
>>involves only end-user software.  In particular software that needs to be 
>>changed is restricted to:  Human DNS input and output modules.
>
>Please be careful here. Assume somebody has software that allows to
>find all domain names with the string 'FOO' in it, where 'FOO' isn't
>necessarily a full label. Now assume this software should work with
>idns, too. Can we do that by just changing the input module
>(e.g. we just encoded 'FOO' as ace? We can't.

actually, I think we can.  the software doing the searching might not be a 
human, but it's place in the overall DNS system is the same place as human 
users.  That is, in the user agent, not the DNS infrastructure.

>Also, assume that a protocol specifies that domain names be in
>UTF-8 (or something else), or that a program decides to use
>Unicode internally.

I think you are confusing what goes on inside a random user program with 
what goes on inside the DNS.

>>    [[[  Question:  Why must we discuss writing order at all?  /Dave   ]]]
>
>The problem Eric has mentioned is one problem, but actually the easier
>one. The sequence of labels is something anyone can get used to.

If the DNS software CREATED strings, then making sure characters were in 
the correct order would make sense.

However the strings are created outside of DNS.  The only thing the DNS 
system must do is PRESERVE that order.


>>The Action Item(s) for the Working Group are:
>
>What's the difference between
>
>"Working Group action items are:" and
>"The Action Item(s) for the Working Group are:"

Fewer characters...

>>Goal & Milestone:
>>
>>Nov 2001        Draft of architecture relating input methods, namepreps
>>                 and zonefiles
>>Nov 2001        Draft of ACE specification
>>Nov 2001        Draft of DNS identifier normalization specification
>>Nov 2001        Draft of DNS character set enhancement specification
>
>'Character set enhancement' is a very weird term. This is the
>IDNA spec, isn't it? Using the word 'architecture' in a generic
>name would be better, I guess.

Glad to use other language.  Please suggest a term.  I simply used what was 
already in the previous draft.

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 Oct 28 00:07:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21578
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 00:07:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xh5d-000Br7-00
	for idn-data@psg.com; Sat, 27 Oct 2001 20:58:25 -0700
To: <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] An ignorant question about TC<-> SC
Cc: <klensin@jck.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
Message-Id: <E15xh5d-000Br7-00@psg.com>
Date: Sat, 27 Oct 2001 20:58:25 -0700
Content-Transfer-Encoding: 7bit

[JS: bounced to me for "Header line too long". Rebounce it back to the
list with header snip. Take note]

At 10:06 01/10/28 +0800, xiang deng wrote:

>On  Saturday, October 27, 2001 2:58 PM, Patrik F$BgM(Btstr$B‹N(B
wrote:

> > I have not said it should. I like and appreciate the recommendation
the
> > Unicode Consortium gave the IETF, and that is to _NOT_ do
unification of
> > TC/SC or even try to come up with matching rules.
> >
> > Instead, multiple registrations in DNS, one for the SC and one for
the TC
> > version is recommended.
>
>Yes, multiple registrations in DNS is better than do nothing.
>But, there are still some problems can not solve:
>1). Just do one for the SC and one for the TC, it isn't enough. Because
other
>person can register mixed TC/SC domain name. How to deal with the
>disputations of
>registration. Such disputations will not disappear, if we have no real
>solution about it.
>it's policy issue.

This is a valid concern. It is ultimately a policy issue. But
it should be possible to produce some data/guidelines (e.g. as
an informational RFC) that registrars/registries can adopt.

It is much easier in such a context to deal with 1-n correspondences
than it is if an actual mapping is required.


>2). multiple registrations in DNS can solve a part of the issue, How to
>solve the
>delegation issue of subdomain and keep the consistency.
>it's technology issue.

I'm not really a DNS expert, but I think with something called
CNAME or DNAME, there is a very easy solution that will keep
consistency.


>3). if we provide multiple registration solution for customs, we must
>guarantee the multiple
>records belong to one custom. but from technology view, we can not
>guarantee it.

It's the customer's job to do that, and the registrar's job
to help them. No need for this WG to do anything.

Regards,   Martin.





From owner-idn@ops.ietf.org  Sun Oct 28 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 ESMTP id AAA21701
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 00:24:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xhJa-000CMF-00
	for idn-data@psg.com; Sat, 27 Oct 2001 21:12:50 -0700
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xhJY-000CM0-00
	for idn@ops.ietf.org; Sat, 27 Oct 2001 21:12:48 -0700
Received: from deng ([159.226.7.68]) by whale.cnnic.net.cn
          (Netscape Messaging Server 4.15) with SMTP id GLWEFT00.QZS; Sun,
          28 Oct 2001 12:14:17 +0800 
Message-ID: <003a01c15f65$b0fe3570$4407e29f@deng>
From: "xiang deng" <deng@cnnic.net.cn>
To: "James Seng/Personal" <jseng@pobox.org.sg>,
        =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        =?ISO-8859-1?B?dHNlbmdsbUDoqF7ntrLkuK3lv2Yu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>,
        "ben" <ben@cc-www.com>, <DougEwell2@cs.com>, <idn@ops.ietf.org>
Cc: <duerst@w3.org>, <klensin@jck.com>
References: <166.2ea4bac.290ad741@cs.com><00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com><497812.1004124760@localhost> <007101c15e8e$cc0919c0$f006738c@ncu.edu.tw> <3399691.1004173125@localhost> <003301c15f55$16f5a220$4407e29f@deng> <000701c15f59$89cdf9b0$1c01000a@jamessonyvaio>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Sun, 28 Oct 2001 12:04:50 +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 AAA21701


On Sunday, October 28, 2001 10:37 AM , James Seng/Personal

> > Yes, multiple registrations in DNS is better than do nothing.
> > But, there are still some problems can not solve:
> > 1). Just do one for the SC and one for the TC, it isn't enough.
> Because other
> > person can register mixed TC/SC domain name. How to deal with the
> disputations of
> > registration. Such disputations will not disappear, if we have no real
> solution about it.
> > it's policy issue.
> 
> Such mixed TC/SC is possible but not useful in practice. It is neither
> "TC" or "SC" and using it is fairly complex to use. Perhaps some
> statistic of how many such TC/SC mixed label been registered in practice
> will be useful.

No, in HK and MO and mainland of china, many people use Mixed TC/SC.
This is fact we can not avoid. 

> 
> > 2). multiple registrations in DNS can solve a part of the issue, How
> to solve the
> > delegation issue of subdomain and keep the consistency.
> > it's technology issue.
> 
> Agree.
> 
> > 3). if we provide multiple registration solution for customs, we must
> guarantee the multiple
> > records belong to one custom. but from technology view, we can not
> guarantee it.
> 
> I presumed you mean from a "policy view", not technology because if we
> cannot guarantee from technology view, ie there is no technology, then
> we cannot do so in IDN anyway

No. In current profile of IDNA, there is no technology. 
But this does not mean that there no technology solution, and you  know it, 
but you refuse to accept this fact.

If we can not guarantee the solution satisfy custom's requirement, the answer is:
let user to suffer it, because there hasn't techonolgy solution(as your words) and 
we will push this  defective solution.

Deng xiang


From owner-idn@ops.ietf.org  Sun Oct 28 00:36:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21873
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 00:36:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xhTi-000Cjo-00
	for idn-data@psg.com; Sat, 27 Oct 2001 21:23:18 -0700
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xhTh-000Cji-00
	for idn@ops.ietf.org; Sat, 27 Oct 2001 21:23:17 -0700
Received: from deng ([159.226.7.68]) by whale.cnnic.net.cn
          (Netscape Messaging Server 4.15) with SMTP id GLWEXA00.0ZH; Sun,
          28 Oct 2001 12:24:46 +0800 
Message-ID: <004501c15f67$27df7270$4407e29f@deng>
From: "xiang deng" <deng@cnnic.net.cn>
To: "=?ISO-2022-JP?B?UGF0cmlrIEYbJEJnTRsoQiB0c3RyGyRCi04bKEI=?=" <paf@cisco.com>,
        =?ISO-2022-JP?B?dHNlbmdsbUAbJEJwKhsoQl4bJEJuOCUkaDolZRsoQg==?=
	=?ISO-2022-JP?B?GyRCakEbKEJmLhskQmg6JWVqJiUhGyhCLnR3?= <tsenglm@cc.ncu.edu.tw>,
        "ben" <ben@cc-www.com>, <DougEwell2@cs.com>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
Cc: <klensin@jck.com>
References: <166.2ea4bac.290ad741@cs.com><00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com><497812.1004124760@localhost><007101c15e8e$cc0919c0$f006738c@ncu.edu.tw><3399691.1004173125@localhost> <4.2.0.58.J.20011028114246.03932e70@localhost>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Sun, 28 Oct 2001 12:15:19 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-2022-JP"
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 AAA21873


On  Sunday, October 28, 2001 10:49 AM, Martin Duerst wrote:



>At 10:06 01/10/28 +0800, xiang deng wrote:

> >On  Saturday, October 27, 2001 2:58 PM, Patrik F$BgM(Btstr$B‹N(B wrote:

> > > I have not said it should. I like and appreciate the recommendation the
> > > Unicode Consortium gave the IETF, and that is to _NOT_ do unification of
> > > TC/SC or even try to come up with matching rules.
> > >
> > > Instead, multiple registrations in DNS, one for the SC and one for the TC
> > > version is recommended.
> >
> >Yes, multiple registrations in DNS is better than do nothing.
> >But, there are still some problems can not solve:
> >1). Just do one for the SC and one for the TC, it isn't enough. Because other
> >person can register mixed TC/SC domain name. How to deal with the 
> >disputations of
> >registration. Such disputations will not disappear, if we have no real 
> >solution about it.
> >it's policy issue.

> This is a valid concern. It is ultimately a policy issue. But
> it should be possible to produce some data/guidelines (e.g. as
> an informational RFC) that registrars/registries can adopt.

> It is much easier in such a context to deal with 1-n correspondences
> than it is if an actual mapping is required.

Thanks. 

> >2). multiple registrations in DNS can solve a part of the issue, How to 
> >solve the
> >delegation issue of subdomain and keep the consistency.
> >it's technology issue.

> I'm not really a DNS expert, but I think with something called
> CNAME or DNAME, there is a very easy solution that will keep
> consistency.

No, we can't keep consistency. 
Mr. James has agree with my opinion.

> >3). if we provide multiple registration solution for customs, we must 
> >guarantee the multiple
> >records belong to one custom. but from technology view, we can not 
> >guarantee it.

> It's the customer's job to do that, and the registrar's job
> to help them. No need for this WG to do anything.

If the fact is as your said. If a user register a domain name which include 
Chinese characters, he must register all variant forms of the domain name.
Then he can protect his intelligent property of this domain name.
why? just because he want register a Chinese domain name?
This answer will not satisfy any person.

Deng xiang





From owner-idn@ops.ietf.org  Sun Oct 28 00:50:41 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22023
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 00:50:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xhmo-000DOG-00
	for idn-data@psg.com; Sat, 27 Oct 2001 21:43:02 -0700
Received: from smtp24.singnet.com.sg ([165.21.101.204])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xhmm-000DOA-00
	for idn@ops.ietf.org; Sat, 27 Oct 2001 21:43:01 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp24.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9S4hBZ25369;
	Sun, 28 Oct 2001 12:43:11 +0800
Message-ID: <001501c15f6a$ef295500$1c01000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "xiang deng" <deng@cnnic.net.cn>,
        "=?ISO-2022-JP?B?UGF0cmlrIEYbJEJnTRsoQiB0c3RyGyRCi04bKEI=?=" <paf@cisco.com>,
        =?ISO-2022-JP?B?dHNlbmdsbUAbJEJwKhsoQl4bJEJuOCUkaDolZRsoQg==?=
	=?ISO-2022-JP?B?GyRCakEbKEJmLhskQmg6JWVqJiUhGyhCLnR3?= <tsenglm@cc.ncu.edu.tw>,
        "ben" <ben@cc-www.com>, <DougEwell2@cs.com>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
Cc: <klensin@jck.com>
References: <166.2ea4bac.290ad741@cs.com><00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com><497812.1004124760@localhost><007101c15e8e$cc0919c0$f006738c@ncu.edu.tw><3399691.1004173125@localhost> <4.2.0.58.J.20011028114246.03932e70@localhost> <004501c15f67$27df7270$4407e29f@deng>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Sun, 28 Oct 2001 12:42:21 +0800
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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > I'm not really a DNS expert, but I think with something called
> > CNAME or DNAME, there is a very easy solution that will keep
> > consistency.
>
> No, we can't keep consistency.
> Mr. James has agree with my opinion.

Let me clarify. I am saying this is a problem we need to look into. I
did not say there is no solution.

-James Seng




From owner-idn@ops.ietf.org  Sun Oct 28 00:51:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22034
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 00:51:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xhlb-000DNV-00
	for idn-data@psg.com; Sat, 27 Oct 2001 21:41:47 -0700
Received: from smtp23.singnet.com.sg ([165.21.101.203])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xhlZ-000DNJ-00
	for idn@ops.ietf.org; Sat, 27 Oct 2001 21:41:46 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp23.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9S4i2L04225;
	Sun, 28 Oct 2001 12:44:02 +0800
Message-ID: <000d01c15f6a$c74cdd40$1c01000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "xiang deng" <deng@cnnic.net.cn>,
        =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        =?iso-8859-1?B?dHNlbmdsbUDoqF7ntrLkuK3lv2Yu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>,
        "ben" <ben@cc-www.com>, <DougEwell2@cs.com>, <idn@ops.ietf.org>
Cc: <duerst@w3.org>, <klensin@jck.com>
References: <166.2ea4bac.290ad741@cs.com><00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com><497812.1004124760@localhost> <007101c15e8e$cc0919c0$f006738c@ncu.edu.tw> <3399691.1004173125@localhost> <003301c15f55$16f5a220$4407e29f@deng> <000701c15f59$89cdf9b0$1c01000a@jamessonyvaio> <003a01c15f65$b0fe3570$4407e29f@deng>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Sun, 28 Oct 2001 12:41:14 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > Such mixed TC/SC is possible but not useful in practice. It is
neither
> > "TC" or "SC" and using it is fairly complex to use. Perhaps some
> > statistic of how many such TC/SC mixed label been registered in
practice
> > will be useful.
>
> No, in HK and MO and mainland of china, many people use Mixed TC/SC.
> This is fact we can not avoid.

Yes, TC & SC are used in some place. Many text also have mixed TC/SC.

But I am saying mixing "TC" and "SC" in one single label is uncommon
simply because it is difficult to type. You need to switch from TC IME
to SC IME repeatively.

Do you have any statistic on how many mixed TC/SC registration have been
done so far?

> > I presumed you mean from a "policy view", not technology because if
we
> > cannot guarantee from technology view, ie there is no technology,
then
> > we cannot do so in IDN anyway
>
> No. In current profile of IDNA, there is no technology.
> But this does not mean that there no technology solution, and you
know it,
> but you refuse to accept this fact.

Wait, read my reply again. I am saying what you said is a "policy view"
not a "technology view". Whether we have this technology or not is not
my point.

If there is a technology to do TC/SC, then we can either do it at IDNA
or registration. If there is no technology, then we can do none.

> If we can not guarantee the solution satisfy custom's requirement, the
answer is:
> let user to suffer it, because there hasn't techonolgy solution(as
your words) and
> we will push this  defective solution.

It is all engineering trade off. No solution is perfect.

-James Seng




From owner-idn@ops.ietf.org  Sun Oct 28 01:06:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22238
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 01:06:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xi1j-000E1v-00
	for idn-data@psg.com; Sat, 27 Oct 2001 21:58:27 -0700
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xi1h-000E1p-00
	for idn@ops.ietf.org; Sat, 27 Oct 2001 21:58:25 -0700
Received: from deng ([159.226.7.68]) by whale.cnnic.net.cn
          (Netscape Messaging Server 4.15) with SMTP id GLWGJU00.5WZ; Sun,
          28 Oct 2001 12:59:54 +0800 
Message-ID: <005701c15f6c$109ebdf0$4407e29f@deng>
From: "xiang deng" <deng@cnnic.net.cn>
To: "James Seng/Personal" <jseng@pobox.org.sg>,
        =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        =?ISO-8859-1?B?dHNlbmdsbUDoqF7ntrLkuK3lv2Yu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>,
        "ben" <ben@cc-www.com>, <DougEwell2@cs.com>, <idn@ops.ietf.org>
Cc: <duerst@w3.org>, <klensin@jck.com>
References: <166.2ea4bac.290ad741@cs.com><00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com><497812.1004124760@localhost> <007101c15e8e$cc0919c0$f006738c@ncu.edu.tw> <3399691.1004173125@localhost> <003301c15f55$16f5a220$4407e29f@deng> <000701c15f59$89cdf9b0$1c01000a@jamessonyvaio> <003a01c15f65$b0fe3570$4407e29f@deng> <000d01c15f6a$c74cdd40$1c01000a@jamessonyvaio>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Sun, 28 Oct 2001 12:50:28 +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 BAA22238


On Sunday, October 28, 2001 12:41 PM, James Seng/Personal wrote:

> > > Such mixed TC/SC is possible but not useful in practice. It is
> neither
> > > "TC" or "SC" and using it is fairly complex to use. Perhaps some
> > > statistic of how many such TC/SC mixed label been registered in
> practice
> > > will be useful.
> >
> > No, in HK and MO and mainland of china, many people use Mixed TC/SC.
> > This is fact we can not avoid.
> 
> Yes, TC & SC are used in some place. Many text also have mixed TC/SC.
> 
> But I am saying mixing "TC" and "SC" in one single label is uncommon
> simply because it is difficult to type. You need to switch from TC IME
> to SC IME repeatively.

No, I do can type TC AND SC in a very usual IME without swich.
And, we can not regulate the register behavior,  whether or not mixing "TC" 
and "SC" is in one single label depend on customers.

> Do you have any statistic on how many mixed TC/SC registration have been
> done so far?

If there just has 1% or 0.1% , do you mean we can ignore it?

> > > I presumed you mean from a "policy view", not technology because if
> we
> > > cannot guarantee from technology view, ie there is no technology,
> then
> > > we cannot do so in IDN anyway
> >
> > No. In current profile of IDNA, there is no technology.
> > But this does not mean that there no technology solution, and you
> know it,
> > but you refuse to accept this fact.
> 
> Wait, read my reply again. I am saying what you said is a "policy view"
> not a "technology view". Whether we have this technology or not is not
> my point.
> 
> If there is a technology to do TC/SC, then we can either do it at IDNA
> or registration. If there is no technology, then we can do none.
> 
> > If we can not guarantee the solution satisfy custom's requirement, the
> answer is:
> > let user to suffer it, because there hasn't techonolgy solution(as
> your words) and
> > we will push this  defective solution.
> 
> It is all engineering trade off. No solution is perfect.
> 

You mean the problem is so tiny that we can ignore it, 
I think you are cheat yourself, because you know Chinese characters.

Deng xiang





From owner-idn@ops.ietf.org  Sun Oct 28 01:32:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23798
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 01:32:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xiPp-000Esk-00
	for idn-data@psg.com; Sat, 27 Oct 2001 22:23:21 -0700
Received: from smtp22.singnet.com.sg ([165.21.101.202])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xiPn-000Ese-00
	for idn@ops.ietf.org; Sat, 27 Oct 2001 22:23:19 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp22.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9S5Qii20665;
	Sun, 28 Oct 2001 13:26:44 +0800
Message-ID: <00d501c15f70$a6ea66c0$1c01000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
References: <011701c15be0$4473db90$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] (bias) summary of reordering discussion
Date: Sun, 28 Oct 2001 13:23:17 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I hope we can do a strawpoll on reordering draft before Salt Lake
meeting. We will announce the process to do so in the next few weeks. In
the meantime, if there is any more discussion, argument for/against on
reordering, please bring them forward.

Thanks.

-James Seng

----- Original Message -----
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <idn@ops.ietf.org>
Sent: Wednesday, October 24, 2001 12:32 AM
Subject: [idn] (bias) summary of reordering discussion


> On the questions posted:
>
> 1. Efficient - I accepted that reordering produce a shorter ACE
string,
> sometimes as much as 20%. This means instead of a "zq--zxcvbnmasdfg"
> label, I get a "zq--zxcvbnmasd". I do not buy the arguments it is
> helpful to naked eye, to memorised or save RAM however.
>
> 2. Compression efficient in future since statistic - Lee's counter
that
> compression "always SHORTER labels than usual". Mathematically, it can
> be proven this is wrong (very basic pigeon hole principle).
>
> 3. Referencing from established I18N organisation - ISO14651 is deem
> inappropriate and I agree with it. No alternative was proposed.
>
> 4. Stability of reordering - Lee's countered with the arguments that
> reordering tables would never changed. I am not sure if that is
possible
> but I agree with the assessment that it is possible to design
reordering
> to be stable. However, I like to see explictive statement in future
> draft.
>
> 5. Future additional of code points / changes to reordering - Lee's
> proposal is a two prefix solution, using prefix as a versioning tag. I
> do not like to solve a problem by creating others, especially one
which
> makes it even more complex. Lee have yet to address the process of how
> future additional of code points or changes to reordering could be
done.
> (IDN WG is not going to exist forever...I dream of finishing our work
> one day).
>
> 6. Reordering is never ending task - Lee's countered that so is
> Nameprep. My thoughts is two wrong dont make one right. (OTOH,
Nameprep
> which is based on UTC work have explicit principles on how it can be
> done. And Nameprep is not subjective to frequency analysis changes
which
> reordering is)
>
> Of the people participate in the reordering discussion
>
> Martin Duerst - explicit objection
> Mark Davis - not very supportive, not explicit
> Adam Costello - (no conclusion from comments)
> Doug Ewell - explicit objection
> Paul Hoffman - explicit objection
> Eric Brunner-William - somewhat supportive, not explicit
> Kenny Huang - (no conclusion from comments)
> James Seng - explicit objection
> Karlsson Kent - explicit objection
> Erik Nordmark - not very supportive
> David Hopwood - (no conclusion from comments)
>
> This is my rough read of the discussion on reordering so far (please
> correct me, and apologise in advance, if I am wrong).
>
> (Wearing my co-chair's hat) It is not a vote or even a strawpoll here
> obviously but I am trying to get a feel of the group consensus. But if
> these discussion is any indication of the group consensus, it does not
> indicate very little support for reordering. If there is other
comments,
> please bring them forward soon. Thanks.
>
> -James Seng
>
>




From owner-idn@ops.ietf.org  Sun Oct 28 01:25:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA26794
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 01:25:56 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xjCf-000Gdf-00
	for idn-data@psg.com; Sat, 27 Oct 2001 23:13:49 -0700
Received: from gate.sinica.edu.tw ([140.109.4.130])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xjCd-000GdT-00
	for idn@ops.ietf.org; Sat, 27 Oct 2001 23:13:48 -0700
Received: from itsnb (i2ot1.iis.sinica.edu.tw [140.109.21.153])
	by gate.sinica.edu.tw (8.11.3/8.11.3) with SMTP id f9S6DZJ29695;
	Sun, 28 Oct 2001 14:13:35 +0800 (CST)
Message-ID: <00e601c15f77$b105f870$4d0c7f8c@itsnb>
From: "Chun-Hsin Wu" <wuch@gate.sinica.edu.tw>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
References: <166.2ea4bac.290ad741@cs.com><00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com><497812.1004124760@localhost> <007101c15e8e$cc0919c0$f006738c@ncu.edu.tw> <3399691.1004173125@localhost> <003301c15f55$16f5a220$4407e29f@deng> <000701c15f59$89cdf9b0$1c01000a@jamessonyvaio> <003a01c15f65$b0fe3570$4407e29f@deng> <000d01c15f6a$c74cdd40$1c01000a@jamessonyvaio>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Sun, 28 Oct 2001 14:13:35 +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.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Yes, TC & SC are used in some place. Many text also have mixed TC/SC.
>
> But I am saying mixing "TC" and "SC" in one single label is uncommon
> simply because it is difficult to type. You need to switch from TC IME
> to SC IME repeatively.

As I know, mixing TC and SC may be neither uncommon nor difficult.
1. Most IMEs in Traditional Windows 2000 can support TC and SC
    directly without switching, even they can let the user type in
    Japanese characters without switching. It is not unusual for one IME
    to support all, or as many as possible, Unicode characters if the system
    supports Unicode. For examples, the phonetic imput method and the
    Boshimy input method. The former is the default method in all Chinese
    systems and almost every Chinese or Taiwanese who uses computers
    knows how to use it easily. The later is widely used by many people
    who want to have high Chinese input rate, especially for professional
    users.
2. In cases of "Taiwan" and "Taipei", the TC and SC characters for the
   first character "Tai", U53F0 and U81FA, are both widely and
   interchangeably used in Taiwan. You can find examples of mixed uses
   in Chinese Web sites, such as TAIpei City Government, National
   TAIwan University, TAIwan Semiconductor Manufacturing Company
   (TSMC), and so on. If we support top-level IDNs in the future, every
   domain and host below IDN.tw will have AT LEAST two records,
   one in  IDN.U53F0-wan and the other in IDN.U81FA-wan.

Chun-Hsin






From owner-idn@ops.ietf.org  Sun Oct 28 01:40:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27734
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 01:40:47 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xjQu-000H9e-00
	for idn-data@psg.com; Sat, 27 Oct 2001 23:28:32 -0700
Received: from smtp15.singnet.com.sg ([165.21.6.35])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xjQt-000H9Y-00
	for idn@ops.ietf.org; Sat, 27 Oct 2001 23:28:31 -0700
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp15.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9S6PuN05641;
	Sun, 28 Oct 2001 14:25:56 +0800
Message-ID: <004b01c15f79$bea28cd0$1c01000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Chun-Hsin Wu" <wuch@gate.sinica.edu.tw>, <idn@ops.ietf.org>
References: <166.2ea4bac.290ad741@cs.com><00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com><497812.1004124760@localhost> <007101c15e8e$cc0919c0$f006738c@ncu.edu.tw> <3399691.1004173125@localhost> <003301c15f55$16f5a220$4407e29f@deng> <000701c15f59$89cdf9b0$1c01000a@jamessonyvaio> <003a01c15f65$b0fe3570$4407e29f@deng> <000d01c15f6a$c74cdd40$1c01000a@jamessonyvaio> <00e601c15f77$b105f870$4d0c7f8c@itsnb>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Sun, 28 Oct 2001 14:28:23 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> 1. Most IMEs in Traditional Windows 2000 can support TC and SC
>     directly without switching, even they can let the user type in
>     Japanese characters without switching. It is not unusual for one
IME
>     to support all, or as many as possible, Unicode characters if the
system
[snip]

On Windows, you install 2 IME, one for TC and the other for SC. You
toggle between these two while you key in.

> 2. In cases of "Taiwan" and "Taipei", the TC and SC characters for the
>    first character "Tai", U53F0 and U81FA, are both widely and
>    interchangeably used in Taiwan. You can find examples of mixed uses
>    in Chinese Web sites, such as TAIpei City Government, National

They are both Traditional form one is T-T, the other is T-S. Both exist
on a TC IME.

I can understand the big problem of TC and SC domain names.

I am not too sure of the problem of "mixed TC & SC" identifiers. Please
do provide some statistic if you can. Thanks.

-James Seng




From owner-idn@ops.ietf.org  Sun Oct 28 05:04:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11485
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 05:04:34 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xmWw-000NxC-00
	for idn-data@psg.com; Sun, 28 Oct 2001 01:46:58 -0800
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xmWu-000Nwv-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 01:46:57 -0800
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9S9SJr21902;
	Sun, 28 Oct 2001 04:28:19 -0500 (EST)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110280928.f9S9SJr21902@nic-naa.net>
To: Martin Duerst <duerst@w3.org>
cc: Dave Crocker <dcrocker@brandenburg.com>, idn@ops.ietf.org,
        brunner@nic-naa.net
Subject: Re: [idn] iDNS re-chartering proposal, take 2 
In-Reply-To: Your message of "Sun, 28 Oct 2001 11:16:39 +0900."
             <4.2.0.58.J.20011028103527.03a361f0@localhost> 
Date: Sun, 28 Oct 2001 04:28:19 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Martin,

Thanks for catching bidi. I'm sorry I didn't notice you'd made a change from
your draft with Larry. We should discuss your #3 (numbers), using a different
subject line.

Eric



From owner-idn@ops.ietf.org  Sun Oct 28 05:06:17 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11497
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 05:06:15 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xmfQ-000OFS-00
	for idn-data@psg.com; Sun, 28 Oct 2001 01:55:44 -0800
Received: from mailb.telia.se ([131.115.15.109])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xmfP-000OFL-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 01:55:43 -0800
Received: from mailb.telia.se (localhost [127.0.0.1])
	by mailb.telia.se (8.9.3/8.9.3) with ESMTP id KAA12791
	for <idn@ops.ietf.org>; Sun, 28 Oct 2001 10:55:40 +0100 (MET)
Received: from trab.se (terra.malmo.trab.se [131.115.48.22])
	by mailb.telia.se (8.9.3/8.9.3) with ESMTP id KAA12781
	for <idn@ops.ietf.org>; Sun, 28 Oct 2001 10:55:38 +0100 (MET)
Message-ID: <3BDBD6B1.DDA9BBB0@trab.se>
Date: Sun, 28 Oct 2001 10:58:09 +0100
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.8 sun4u)
X-Accept-Language: sv, en
MIME-Version: 1.0
To: idn@ops.ietf.org
Subject: [idn] Need a new working group?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I have read the new ideas for charter modifications and read
the discussions for a long time. I am beginning to wonder
what is really the meaning of this IDN working group
and as it looks now, maybe we need another new group.

The focus so far by many of the members of the IDN group
have been "host names" with non-ASCII characters.
For me, my interest have always been in defining how
DNS should handle non-ASCII.

Should we split the group into two?

Group one: Non-ASCII in host names from user perspective
Group two: Internationalisation of DNS.

Group one could produce:
- An RFC on how to use ACE on host names to layer non-ASCII
names on top of the old DNS protocol. Must be coodinated with the
group two which defines the DNS protocol.

- An RFC on a good ACE.

- Discuss how domain names are to be input/presented to
the user. The DNS protocol only defines that a domain name
is a sequence of labels (containg any characters) of which
are ordered hiearchically. When displayed to the user, they could
be displayed from top to bottom label, the reverse or with
other separator character then ".".
Discuss on how zone files should be entered in a user friendly way.
Discuss and create recommendations in human handling of
domain names.


Group two should produce:
- An RFC specifying how non-ASCII characters in the DNS protocol
should be handled. It should be a unified solution without
respect to a label being a host name or something else. And should
include all character data, both in labels and in records.
This includes specifying how labels with non-ASCII characters should be
transmitted to software incapable of handling non-ASCII.

- An RFC specifying how to compare two labels to identify if
they match. Like the case-insensitive rule for ASCII today but
for all characters. There are no forbidden character here but
the matching algorithm man ignore some characters during matching.


The reason I would like to see something like this split, is
that the current group seems to have forgotten DNS.
DNS is much more than just host names. We need a basic general
definition of the DNS protocol that includes how to handle
non-ASCII. With that in place, one can build more restrictive
rules and solutions for special areas like host names.

   Dan



From owner-idn@ops.ietf.org  Sun Oct 28 05:26:19 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11554
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 05:26:18 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xmvC-000OsX-00
	for idn-data@psg.com; Sun, 28 Oct 2001 02:12:02 -0800
Received: from mailb.telia.se ([131.115.15.109])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xmvB-000Os9-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 02:12:01 -0800
Received: from mailb.telia.se (localhost [127.0.0.1])
	by mailb.telia.se (8.9.3/8.9.3) with ESMTP id LAA15531
	for <idn@ops.ietf.org>; Sun, 28 Oct 2001 11:11:59 +0100 (MET)
Received: from trab.se (terra.malmo.trab.se [131.115.48.22])
	by mailb.telia.se (8.9.3/8.9.3) with ESMTP id LAA15527
	for <idn@ops.ietf.org>; Sun, 28 Oct 2001 11:11:58 +0100 (MET)
Message-ID: <3BDBDA85.D843D9B5@trab.se>
Date: Sun, 28 Oct 2001 11:14:29 +0100
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.8 sun4u)
X-Accept-Language: sv, en
MIME-Version: 1.0
To: idn@ops.ietf.org
Subject: [idn] Does IDN in applications only, solve the right problem?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


IDNA was made to allow non-ASCII in host names by making
only applications understand them.
And I have seen that some are experimenting on adding this
to web browsers.

But is this were it is needed?

The basic need of ACE is to allow ancient programs to still
being able to get a name in ASCII only.
But a web browser is a new program, it is easy to modify
and it could use UTF-8 directely.
On the other hand, the programs that ACE is there to protect, like
for example a lot of system software under Unix, many of them
are programs that really need to be fixed to handle non-ASCII.
Before I can tell my Unix host that its name contains non-ASCII
and have programs like inetd, logging, telnet and ftp handle
them, ACE have less need as browsers work fine with UTF-8.
Note: the programs above handle non-ASCII names when I can
enter the names into the programs and configuration files using
non-ASCII characters. The names may not be in ACE. Native encoding
is required.

So maybe the easiest thing to do is to rewrite the
resolver libraries to decode/encode UTF-8 or ACE into native
character set so that all programs never see ACE or UTF-8?

I am very doubtfull that ACE in application only, will
allow me to use non-ASCII in my host names soon, as it will
not fix many of the programs that most need to be fixed. Maybe
after 10 years.

   Dan



From owner-idn@ops.ietf.org  Sun Oct 28 07:08:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12067
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 07:08:46 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xoav-0003Qa-00
	for idn-data@psg.com; Sun, 28 Oct 2001 03:59:13 -0800
Received: from smtp14.singnet.com.sg ([165.21.6.34])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xoau-0003QU-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 03:59:12 -0800
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp14.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9SBi3410494;
	Sun, 28 Oct 2001 19:44:03 +0800
Message-ID: <001401c15fa6$17d43e80$1c01000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Dan Oscarsson" <Dan.Oscarsson@trab.se>, <idn@ops.ietf.org>
References: <3BDBD6B1.DDA9BBB0@trab.se>
Subject: Re: [idn] Need a new working group?
Date: Sun, 28 Oct 2001 19:45: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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> The focus so far by many of the members of the IDN group
> have been "host names" with non-ASCII characters.
> For me, my interest have always been in defining how
> DNS should handle non-ASCII.
> 
> Should we split the group into two?
> 
> Group one: Non-ASCII in host names from user perspective
> Group two: Internationalisation of DNS.

There is a group for DNS. It is known as DNSEXT.

-James Seng




From owner-idn@ops.ietf.org  Sun Oct 28 07:20:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12174
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 07:20:02 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xolk-0003pw-00
	for idn-data@psg.com; Sun, 28 Oct 2001 04:10:24 -0800
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xolj-0003po-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 04:10:23 -0800
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9SCAhr25511;
	Sun, 28 Oct 2001 07:10:43 -0500 (EST)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110281210.f9SCAhr25511@nic-naa.net>
X-Mailer: exmh version 1.6.9 8/22/96
To: Dan Oscarsson <Dan.Oscarsson@trab.se>
cc: idn@ops.ietf.org
Subject: Re: [idn] Need a new working group? 
In-Reply-To: Your message of "Sun, 28 Oct 2001 10:58:09 +0100."
             <3BDBD6B1.DDA9BBB0@trab.se> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 28 Oct 2001 07:10:43 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dan,

The dns work should be done in dnsext.

That said, should _this_ working group divide?

A working group has technical advisors -- this one has Harald and John, both
have some expertise, but neither have the familiarity with CJK characters a
native speaker of a CJK language have. The second group could seek one or more
technical advisors, though I can't off-hand name any former or current IESG or
IAB member who wasn't culturally European.

A working group has area directors -- this one has Erik and Thomas. A second
set of ADs, or a second area advisor, may be necessary. Only Erik knows if he
has the bandwidth and interest in minding two groups.

A working group has a chair, or co-chairs. Process competency and a calm
disposition are required, and anything would be better than having chair
bounce to the microphone/mailing list after every speaker/poster to blurt
out some response. It is distracting, error-prone, and absurdly personal.

There is some generica in the IDNA/Nameprep/ACE work, which is useful for
an IDNI (the 2nd "I" is for "infrastructure"), and the current scope does
not include usefor (chars in netnews headers), 822 (chars in smtp headers),
or ... .

I'd like to see a working group that is more driven by data, implementation
experience, and experimentation, than is the norm in this group.

In any really hard problem area, when it appears that a critical moment is
at hand, it is hard to justify restructuring. Unfortunately, some structures
fail at critical moments.

As the IDN WG made UTF out-of-scope, and shortly will make intermediate
mappings likewise out-of-scope, can't fix its own requirements draft (the
ACE recommendation has been there -05, since April!), either it is shaking
off unnecessary stuff as it rapidly closes on a workable solution, or it is
doing something else less functional. I think its the second.

The critical questions are when does a "dns i18n" BoF form, how clearly do
the contributors to the eventual WG and the contributors to the standing DNS
EXT WG understand their relationship (one evaluates and recommends, either
"informational" or "experimental", the other specifies, "experimental" or
"draft standard"), and how to keep the second WG from being dominated by the
most vocal and least constructive participants of the first WG. Of course,
if the IESG doesn't approve a BoF, then the group would have to work outside
of the work group structure, or try to work within this group.

I've tried the latter, I'm not satisfied. You're not satisfied. Maybe there
are others who aren't satisfied either, and who think your note is useful.
I do.

Eric




From owner-idn@ops.ietf.org  Sun Oct 28 07:40:01 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12319
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 07:40:01 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xp6a-0004cU-00
	for idn-data@psg.com; Sun, 28 Oct 2001 04:31:56 -0800
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xp6Z-0004cC-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 04:31:55 -0800
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9SCXWr26123;
	Sun, 28 Oct 2001 07:33:33 -0500 (EST)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110281233.f9SCXWr26123@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
cc: "David Hopwood" <david.hopwood@zetnet.co.uk>, idn@ops.ietf.org,
        brunner@nic-naa.net
Subject: Re: [idn] Update Charter revision 2 
In-Reply-To: Your message of "Thu, 25 Oct 2001 16:45:35 +0800."
             <008001c15d31$6b2a9ce0$1701000a@jamessonyvaio> 
Date: Sun, 28 Oct 2001 07:33:32 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On October 25th, in reply to David Hopwood, you (James Seng) wrote:

> Last Call is norm but not neccessary. It was agreed on London meeting to
> move forward the doc since there is no comments or any changes proposed

Please note the following:

Message-Id: <200106200145.f5K1jWM16873@nic-naa.net>
To: Zita Wenzel <zita@ISI.EDU>
cc: idn@ops.ietf.org, brunner
Subject: Re: [idn] draft-ietf-idn-requirements-07.txt 
In-Reply-To: Your message of "Tue, 19 Jun 2001 20:46:34 GMT."
             <200106192046.UAA12542@gin.isi.edu> 
Date: Tue, 19 Jun 2001 21:45:32 -0400

Please also note the following:

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
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

A killfile isn't an explination, its disfunction.

Eric



From owner-idn@ops.ietf.org  Sun Oct 28 07:56:19 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12441
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 07:56:19 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xpLw-0005CJ-00
	for idn-data@psg.com; Sun, 28 Oct 2001 04:47:48 -0800
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xpLr-0005C7-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 04:47:43 -0800
Received: from test12345 ([140.115.6.240])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f9SCsCV01265;
	Sun, 28 Oct 2001 20:54:12 +0800 (CST)
Message-ID: <001e01c15fae$010900c0$f006738c@ncu.edu.tw>
From: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: <jet-member@nic.ad.jp>, <idn@ops.ietf.org>
References: <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp><01c801c15c3d$d9a7ae50$4407e29f@deng> <20011024130954A.yone@nic.ad.jp> <024101c15c42$372e1b50$4407e29f@deng> <007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio> <003f01c15f5c$1d4e5f70$ec1bd9d2@temp> <001101c15f64$7eb3b780$1c01000a@jamessonyvaio> <016601c15f7d$14325c40$ec1bd9d2@temp> <005501c15f80$9dd52a10$1c01000a@jamessonyvaio> <000d01c15f81$5573d900$ec1bd9d2@temp> <006301c15f82$da0cbe60$1c01000a@jamessonyvaio>
Subject: [idn] Re: [JET-member 443] Re: Fw: Re: new members invitation
Date: Sun, 28 Oct 2001 20:42:27 +0800
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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > TC/SC tables are just less than 10K, while NFKC/Legacy/Font
> requirements
> > is much higher. implementation complexity is for engineers.
> > but, deployment costs are transferred to innocent end users.
>
> I am not going to argue for or against TC/SC here. I am stuck in the
> middle myself, torn between been a Chinese and been a co-chair for IDN.
>
> But the arguments for inclusive of TC/SC or not should be done on a pure
> technical evaluation basis in IETF. Economy arguments as above is not a
> factor for consideration.
>
> This is why it is known as engineering trade off, not economy trade off.
>
> -James Seng
>
James:
             Let us to know what is pure technical evaluation basis in your
mind as you are a co-chair in an IETF working group.
             If an Engineering Requirement is not related to the user's cost
and what are user need that must be a very interest projects.  I think many
members in IDN WG of IETF also like to know the detail .  You give me a very
strange impression of IETF.  Can someone in IETF can help more ?

L.M.Tseng




From owner-idn@ops.ietf.org  Sun Oct 28 09:39:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13648
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 09:39:41 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xqqo-0008RB-00
	for idn-data@psg.com; Sun, 28 Oct 2001 06:23:46 -0800
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xqqo-0008R0-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 06:23:46 -0800
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id ACAE37F45B; Sun, 28 Oct 2001 23:23:38 +0900 (JST)
Message-Id: <4.2.0.58.J.20011028143213.0394bdd0@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Sun, 28 Oct 2001 14:42:32 +0900
To: Dave Crocker <dcrocker@brandenburg.com>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] iDNS re-chartering proposal, take 2
Cc: idn@ops.ietf.org
In-Reply-To: <5.1.0.14.2.20011027202302.03a94958@brandenburg.com>
References: <4.2.0.58.J.20011028103527.03a361f0@localhost>
 <5.1.0.14.2.20011027084819.03d3b6c0@brandenburg.com>
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/10/27 -0700, Dave Crocker wrote:
>At 08:16 PM 10/27/2001, Martin Duerst wrote:
>>At 12:09 01/10/27 -0700, Dave Crocker wrote:
>>>then encode the characters, to permit their transmission and storage 
>>>within existing DNS mechanisms.  Hence this enhancement to the DNS 
>>>involves only end-user software.  In particular software that needs to 
>>>be changed is restricted to:  Human DNS input and output modules.
>>
>>Please be careful here. Assume somebody has software that allows to
>>find all domain names with the string 'FOO' in it, where 'FOO' isn't
>>necessarily a full label. Now assume this software should work with
>>idns, too. Can we do that by just changing the input module
>>(e.g. we just encoded 'FOO' as ace? We can't.
>
>actually, I think we can.  the software doing the searching might not be a 
>human, but it's place in the overall DNS system is the same place as human 
>users.  That is, in the user agent, not the DNS infrastructure.

User agent is a wide term, and may be okay. Human input/output
is quite different, and inappropriate. As a human being I don't
like to be thrown into the same pot as some software. So can
we please change that to 'DNS input and output modules'?


>>Also, assume that a protocol specifies that domain names be in
>>UTF-8 (or something else), or that a program decides to use
>>Unicode internally.
>
>I think you are confusing what goes on inside a random user program with 
>what goes on inside the DNS.

No, I don't. I just wanted to make sure that the charter doesn't
give the impression that all software has to use ACE throughout
because conversion happens on 'Human input/output'.


>>>    [[[  Question:  Why must we discuss writing order at all?  /Dave   ]]]
>>
>>The problem Eric has mentioned is one problem, but actually the easier
>>one. The sequence of labels is something anyone can get used to.
>
>If the DNS software CREATED strings, then making sure characters were in 
>the correct order would make sense.
>
>However the strings are created outside of DNS.  The only thing the DNS 
>system must do is PRESERVE that order.

DNS names appear on paper and displays. If we are not sure that
the same internal string of characters will lead to the same display
and vice versa, then all our work on idn will just lead to a lot of
confusion. It may look as if just extending the set of characters
won't change anything here, but at least for Arabic and Hebrew,
that's not the case.


>>>The Action Item(s) for the Working Group are:
>>
>>What's the difference between
>>
>>"Working Group action items are:" and
>>"The Action Item(s) for the Working Group are:"
>
>Fewer characters...

I was asking something different, sorry. Why are there
two subtitles in your charter listing action items for
the WG, one of them with two action items, and one with
four?


>>>Goal & Milestone:
>>>
>>>Nov 2001        Draft of architecture relating input methods, namepreps
>>>                 and zonefiles
>>>Nov 2001        Draft of ACE specification
>>>Nov 2001        Draft of DNS identifier normalization specification
>>>Nov 2001        Draft of DNS character set enhancement specification
>>
>>'Character set enhancement' is a very weird term. This is the
>>IDNA spec, isn't it? Using the word 'architecture' in a generic
>>name would be better, I guess.
>
>Glad to use other language.  Please suggest a term.  I simply used what 
>was already in the previous draft.

Why not just call it 'DNS internationalization architecture specification'?

Regards,   Martin.



From owner-idn@ops.ietf.org  Sun Oct 28 09:40:07 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13663
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 09:40:07 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xqqp-0008RI-00
	for idn-data@psg.com; Sun, 28 Oct 2001 06:23:47 -0800
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xqqo-0008R9-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 06:23:47 -0800
Received: from enoshima (toro.w3.mag.keio.ac.jp [133.27.228.201])
	by toro.w3.mag.keio.ac.jp (Postfix) with ESMTP
	id B69277F4D3; Sun, 28 Oct 2001 23:23:39 +0900 (JST)
Message-Id: <4.2.0.58.J.20011028155518.040c9810@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Sun, 28 Oct 2001 15:58:58 +0900
To: "Chun-Hsin Wu" <wuch@gate.sinica.edu.tw>,
        "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] An ignorant question about TC<-> SC
In-Reply-To: <00e601c15f77$b105f870$4d0c7f8c@itsnb>
References: <166.2ea4bac.290ad741@cs.com>
 <00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com>
 <497812.1004124760@localhost>
 <007101c15e8e$cc0919c0$f006738c@ncu.edu.tw>
 <3399691.1004173125@localhost>
 <003301c15f55$16f5a220$4407e29f@deng>
 <000701c15f59$89cdf9b0$1c01000a@jamessonyvaio>
 <003a01c15f65$b0fe3570$4407e29f@deng>
 <000d01c15f6a$c74cdd40$1c01000a@jamessonyvaio>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 14:13 01/10/28 +0800, Chun-Hsin Wu wrote:

>2. In cases of "Taiwan" and "Taipei", the TC and SC characters for the
>    first character "Tai", U53F0 and U81FA, are both widely and
>    interchangeably used in Taiwan. You can find examples of mixed uses
>    in Chinese Web sites, such as TAIpei City Government, National
>    TAIwan University, TAIwan Semiconductor Manufacturing Company
>    (TSMC), and so on. If we support top-level IDNs in the future, every
>    domain and host below IDN.tw will have AT LEAST two records,
>    one in  IDN.U53F0-wan and the other in IDN.U81FA-wan.

This is a very specific case (there are others like this, but
not that many). For companies/organizations, they should just
register both variants. For the top-level domain, there should
be only one. It would probably be U53F0-wan. Please note that
this is very similar to two-letter combinations for countries
in ASCII; to a certain extent, people just have to learn them,
e.g. that it's 'jp' and not 'ja' for Japan,...

Regards,  Martin.



From owner-idn@ops.ietf.org  Sun Oct 28 10:28:17 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13941
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 10:28:16 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xrgy-000AIr-00
	for idn-data@psg.com; Sun, 28 Oct 2001 07:17:40 -0800
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xrgx-000AIl-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 07:17:39 -0800
Received: from cs881964a ([24.43.70.205]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Sun, 28 Oct 2001 07:31:01 -0800
Message-ID: <012c01c15fc4$fab6d780$cd462b18@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "John C Klensin" <klensin@jck.com>
Cc: <idn@ops.ietf.org>
References:  <003a01c15e29$4c9fdda0$cd462b18@mtag1.on.home.com> <2544044.1004093815@localhost>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Sun, 28 Oct 2001 10:26:28 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi John,

I understand and respect your knowledge/opinion (as I recall reading
something you wrote on the history of gTLD and ccTLD) on the
difficulties of setting up another type of script hierarchy for the
<idn>.<idn>.

However, if one day it is indeed brought to the table, I most
certainly would like your vote of confidence (assuming that I have not
missed other technical difficulties that you see with it.)

Thanks
Ben



----- Original Message -----
From: "John C Klensin" <klensin@jck.com>
To: "ben" <ben@cc-www.com>
Cc: <idn@ops.ietf.org>
Sent: Friday, October 26, 2001 9:56 AM
Subject: Re: [idn] An ignorant question about TC<-> SC


> --On Friday, 26 October, 2001 10:20 -0400 ben <ben@cc-www.com>
> wrote:
>
> > Hi John,
> >
> >>
> >> For those who want the history, at least as I remember it,
> >> read on...
> >>
> >
> > Thanks for the history lesson and I now have a much better
> > understanding of all the efforts that have gone into this.  So
> > I have the same question for you as I do for Martin.  Why
> > can't we simply label an IDN with the what language script it
> > is in.  In my opinion, it is much more important for an IDN
> > user to know "what script the IDN is in" and far less
> > important to know "if the IDN will take them to a company or
> > goverment or military or organization website".
>
> I'm not sure I understand your question, but I think you are
> asking a basic question about the organization of the DNS.
> I.e., if we decide languages are really important, why don't we
> reorganize things into a language-based hierarchy, rather than a
> country-and-function-based one?
>
> The only _technical_ answers are that it would be hard to get
> there from here, and that, given the administrative nature of
> the DNS delegation structure, finding a single, agreed-upon,
> authority for each language would be extremely hard.  There are
> also a number of administrative obstacles, not the least of
> which is that many people would not agree with your opinion.
>
> I hate to keep saying this, but your question takes me back to
> what I think is the basic problem here.  The DNS was designed to
> provide identifiers for computer resources, using an
> administrative structure that was fairly convenient for those
> computer resources.  If we need to find names, or understand
> strings, along other dimensions, we are either going to need to
> remove the problem from the DNS or we are going to be faced with
> tradeoffs among a range of undesirable solutions.
>
>     john
>
>




From owner-idn@ops.ietf.org  Sun Oct 28 10:42:38 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14119
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 10:42:37 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xrq4-000Ad0-00
	for idn-data@psg.com; Sun, 28 Oct 2001 07:27:04 -0800
Date: Sun, 28 Oct 2001 14:09:24 +0900
To: <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] An ignorant question about TC<-> SC
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15xrq4-000Ad0-00@psg.com>

[JS: bounced to me "header line too long" so I snip the header again.
Martin, can you trim your mail header before you post? Thanks.]

At 12:15 01/10/28 +0800, xiang deng wrote:

>On  Sunday, October 28, 2001 10:49 AM, Martin Duerst wrote:

> > This is a valid concern. It is ultimately a policy issue. But
> > it should be possible to produce some data/guidelines (e.g. as
> > an informational RFC) that registrars/registries can adopt.
>
> > It is much easier in such a context to deal with 1-n correspondences
> > than it is if an actual mapping is required.
>
>Thanks.
>
> > >2). multiple registrations in DNS can solve a part of the issue,
How to
> > >solve the
> > >delegation issue of subdomain and keep the consistency.
> > >it's technology issue.
>
> > I'm not really a DNS expert, but I think with something called
> > CNAME or DNAME, there is a very easy solution that will keep
> > consistency.
>
>No, we can't keep consistency.
>Mr. James has agree with my opinion.

Can somebody who really knows the DNS details please answer this:

Assume somebody registers SSSS as a domain with name servers,...
and registers TTTT CNAME SSSS, why would that not guarantee that
everybody looking for foo.SSSS and for foo.TTTT would get to
the same machine(s)?


> > >3). if we provide multiple registration solution for customs, we
must
> > >guarantee the multiple
> > >records belong to one custom. but from technology view, we can not
> > >guarantee it.
>
> > It's the customer's job to do that, and the registrar's job
> > to help them. No need for this WG to do anything.
>
>If the fact is as your said. If a user register a domain name which
include
>Chinese characters, he must register all variant forms of the domain
name.

No. What I'm assuming is that s/he registers two forms, an
all-simplified
and an all-traditional form. That's the customer's responsibility.
The rules I mentioned in my answer to your point 1), if applied, then
would guarantee that nobody else can register a name that is a mixture
of simplified and traditional characters of the already registered
names.


>Then he can protect his intelligent property of this domain name.
>why? just because he want register a Chinese domain name?
>This answer will not satisfy any person.

Registering a lot of domain names won't satisfy anybody. But
registering two domain names should not be too bad, I think.

Regards,    Martin.







From owner-idn@ops.ietf.org  Sun Oct 28 10:43:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14130
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 10:43:03 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xroI-000AYj-00
	for idn-data@psg.com; Sun, 28 Oct 2001 07:25:14 -0800
Received: from smtp23.singnet.com.sg ([165.21.101.203])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xroH-000AYc-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 07:25:13 -0800
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp23.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9SFRrL22073;
	Sun, 28 Oct 2001 23:27:53 +0800
Message-ID: <004101c15fc4$b9be74e0$1c01000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <jet-member@nic.ad.jp>, <idn@ops.ietf.org>
References: <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp><01c801c15c3d$d9a7ae50$4407e29f@deng> <20011024130954A.yone@nic.ad.jp> <024101c15c42$372e1b50$4407e29f@deng> <007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio> <003f01c15f5c$1d4e5f70$ec1bd9d2@temp> <001101c15f64$7eb3b780$1c01000a@jamessonyvaio> <016601c15f7d$14325c40$ec1bd9d2@temp> <005501c15f80$9dd52a10$1c01000a@jamessonyvaio> <000d01c15f81$5573d900$ec1bd9d2@temp> <006301c15f82$da0cbe60$1c01000a@jamessonyvaio> <001e01c15fae$010900c0$f006738c@ncu.edu.tw>
Subject: [idn] Re: [JET-member 446] Re: Fw: Re: new members invitation
Date: Sun, 28 Oct 2001 23:25:07 +0800
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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Prof Tseng,

I do not see what so strange about my comment. IETF is an engineering
group so we deal with technical issues. Political, economy and business
issues are really out not our concern.

But cc: IDN WG at this moment without relevant discussion which taken
place in JET mailing list is confusing to other so let me pull a piece
of our discussion:

Deng Xiang comment that TC-SC that:

"Because IDN should be global protocol and will force all Chinese users
to register all form TC/SC domain  name and pay unlimited money and face
unlimited domain name disputation. Do you still think it's the local
issue?

Yes. all over the world. If you want earn money from Chinese people."

I responded that

"While I sympathis with this argument, unfortunately, IETF usually do
not consider non-technical issues relevant. This is considered Layer 9
aka "political" issues from IETF perspective." (Lee then corrected me
that this is a "economy" issues, not "political")

and also

"We dont ask how much CNNIC charges per name, nor we care what Verisign
charges to their registrar. neither do we can how much Entrust or
Baltimore charges per certificate nor do we regulate how much hosting
companies going to charge to their customer.

None of these cost is a concern to IETF. We leave these to market force
to play it. That is the nature of the free-market forces."

-James Seng


> > > TC/SC tables are just less than 10K, while NFKC/Legacy/Font
> > requirements
> > > is much higher. implementation complexity is for engineers.
> > > but, deployment costs are transferred to innocent end users.
> >
> > I am not going to argue for or against TC/SC here. I am stuck in the
> > middle myself, torn between been a Chinese and been a co-chair for
IDN.
> >
> > But the arguments for inclusive of TC/SC or not should be done on a
pure
> > technical evaluation basis in IETF. Economy arguments as above is
not a
> > factor for consideration.
> >
> > This is why it is known as engineering trade off, not economy trade
off.
> >
> > -James Seng
> >
> James:
>              Let us to know what is pure technical evaluation basis in
your
> mind as you are a co-chair in an IETF working group.
>              If an Engineering Requirement is not related to the
user's cost
> and what are user need that must be a very interest projects.  I think
many
> members in IDN WG of IETF also like to know the detail .  You give me
a very
> strange impression of IETF.  Can someone in IETF can help more ?
>
> L.M.Tseng
>




From owner-idn@ops.ietf.org  Sun Oct 28 10:44:06 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14142
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 10:44:05 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xrqq-000Adc-00
	for idn-data@psg.com; Sun, 28 Oct 2001 07:27:52 -0800
To: <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] An ignorant question about TC<-> SC
Cc: <klensin@jck.com>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15xrqq-000Adc-00@psg.com>
Date: Sun, 28 Oct 2001 07:27:52 -0800

[JS: snip header again]

At 12:50 01/10/28 +0800, xiang deng wrote:

>On Sunday, October 28, 2001 12:41 PM, James Seng/Personal wrote:
>
> > > > Such mixed TC/SC is possible but not useful in practice. It is
> > neither
> > > > "TC" or "SC" and using it is fairly complex to use. Perhaps some
> > > > statistic of how many such TC/SC mixed label been registered in
> > practice
> > > > will be useful.
> > >
> > > No, in HK and MO and mainland of china, many people use Mixed
TC/SC.
> > > This is fact we can not avoid.
> >
> > Yes, TC & SC are used in some place. Many text also have mixed
TC/SC.
> >
> > But I am saying mixing "TC" and "SC" in one single label is uncommon
> > simply because it is difficult to type. You need to switch from TC
IME
> > to SC IME repeatively.
>
>No, I do can type TC AND SC in a very usual IME without swich.

Can you give an example? What is the IME you are using? What is
the name you are using?


>And, we can not regulate the register behavior,  whether or not mixing
"TC"
>and "SC" is in one single label depend on customers.

I think it is possible to make some restrictions on registrations:

If a user registers a TC-only and an SC-only name for the same thing,
others are forbidden to register mixtures.

This is in my eyes the most reasonable approach to the TC/SC problem,
because:

- It avoids large numbers of registrations for domain owners
   (they can still register as many variants as they think end
    users will actually use, which is something they can influence
    by what forms they publish)
- It avoids DNS server load increases
- It allows to deal with 1-many cases much easier than proposals
   that have to do actual mapping.

> > Do you have any statistic on how many mixed TC/SC registration have
been
> > done so far?
>
>If there just has 1% or 0.1% , do you mean we can ignore it?

It could be that we can ignore it, or that we can look for
lightweight solutions.


>You mean the problem is so tiny that we can ignore it,

It may be that the solutions available are so complicated and
imperfect that we better decide to ignore the problem, even
if we think it's not tiny.


Regards,   Martin.





From owner-idn@ops.ietf.org  Sun Oct 28 11:02:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14314
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 11:02:28 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xsGh-000Bid-00
	for idn-data@psg.com; Sun, 28 Oct 2001 07:54:35 -0800
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xsGf-000Bi9-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 07:54:34 -0800
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9SFtur30634;
	Sun, 28 Oct 2001 10:55:56 -0500 (EST)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110281555.f9SFtur30634@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
cc: jet-member@nic.ad.jp, idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Re: [JET-member 446] Re: Fw: Re: new members invitation 
In-Reply-To: Your message of "Sun, 28 Oct 2001 23:25:07 +0800."
             <004101c15fc4$b9be74e0$1c01000a@jamessonyvaio> 
Date: Sun, 28 Oct 2001 10:55:56 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James,

Substitute "cost" (or "economy") for "scale".

As Deng pointed out some _weeks_ ago, the buy-to-exhaustion "solution" to
the SC/TC issue DOESN'T SCALE. The same holds for any contention mechanism,
aka a "DRP". Even when both are "free".

Remember scaling?

Cheers,
Eric



From owner-idn@ops.ietf.org  Sun Oct 28 11:13:19 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14384
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 11:13:18 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xsMc-000BtU-00
	for idn-data@psg.com; Sun, 28 Oct 2001 08:00:42 -0800
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xsMX-000BtL-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 08:00:40 -0800
Received: from test12345 ([140.115.6.240])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f9SG7QV09347;
	Mon, 29 Oct 2001 00:07:26 +0800 (CST)
Message-ID: <005101c15fc8$fbcd05a0$f006738c@ncu.edu.tw>
From: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: <jet-member@nic.ad.jp>, <idn@ops.ietf.org>
References: <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp><01c801c15c3d$d9a7ae50$4407e29f@deng> <20011024130954A.yone@nic.ad.jp> <024101c15c42$372e1b50$4407e29f@deng> <007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio> <003f01c15f5c$1d4e5f70$ec1bd9d2@temp> <001101c15f64$7eb3b780$1c01000a@jamessonyvaio> <016601c15f7d$14325c40$ec1bd9d2@temp> <005501c15f80$9dd52a10$1c01000a@jamessonyvaio> <000d01c15f81$5573d900$ec1bd9d2@temp> <006301c15f82$da0cbe60$1c01000a@jamessonyvaio> <001e01c15fae$010900c0$f006738c@ncu.edu.tw> <004101c15fc4$b9be74e0$1c01000a@jamessonyvaio>
Subject: [idn] Re: [JET-member 448] Re: Fw: Re: new members invitation
Date: Sun, 28 Oct 2001 23:55:35 +0800
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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dear James:
                    I just have the question: In what condition , an
Enginnering problems is never related to cost , especially a protocol that
so many user will be used .
                    Many draft are discussed and comparing with the  the
cost and time of depolyment .  And that is the first time , I can not
understand the requirements are unrelated to users who will use the results
of them.
                    I  must be learn more , I need some help to let me
understand IETF more.

L.M.Tseng
----- Original Message -----
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <jet-member@nic.ad.jp>; <idn@ops.ietf.org>
Sent: Sunday, October 28, 2001 11:25 PM
Subject: [JET-member 448] Re: Fw: Re: new members invitation


> Prof Tseng,
>
> I do not see what so strange about my comment. IETF is an engineering
> group so we deal with technical issues. Political, economy and business
> issues are really out not our concern.
>
> But cc: IDN WG at this moment without relevant discussion which taken
> place in JET mailing list is confusing to other so let me pull a piece
> of our discussion:
>
> Deng Xiang comment that TC-SC that:
>
> "Because IDN should be global protocol and will force all Chinese users
> to register all form TC/SC domain  name and pay unlimited money and face
> unlimited domain name disputation. Do you still think it's the local
> issue?
>
> Yes. all over the world. If you want earn money from Chinese people."
>
> I responded that
>
> "While I sympathis with this argument, unfortunately, IETF usually do
> not consider non-technical issues relevant. This is considered Layer 9
> aka "political" issues from IETF perspective." (Lee then corrected me
> that this is a "economy" issues, not "political")
>
> and also
>
> "We dont ask how much CNNIC charges per name, nor we care what Verisign
> charges to their registrar. neither do we can how much Entrust or
> Baltimore charges per certificate nor do we regulate how much hosting
> companies going to charge to their customer.
>
> None of these cost is a concern to IETF. We leave these to market force
> to play it. That is the nature of the free-market forces."
>
> -James Seng
>
>
> > > > TC/SC tables are just less than 10K, while NFKC/Legacy/Font
> > > requirements
> > > > is much higher. implementation complexity is for engineers.
> > > > but, deployment costs are transferred to innocent end users.
> > >
> > > I am not going to argue for or against TC/SC here. I am stuck in the
> > > middle myself, torn between been a Chinese and been a co-chair for
> IDN.
> > >
> > > But the arguments for inclusive of TC/SC or not should be done on a
> pure
> > > technical evaluation basis in IETF. Economy arguments as above is
> not a
> > > factor for consideration.
> > >
> > > This is why it is known as engineering trade off, not economy trade
> off.
> > >
> > > -James Seng
> > >
> > James:
> >              Let us to know what is pure technical evaluation basis in
> your
> > mind as you are a co-chair in an IETF working group.
> >              If an Engineering Requirement is not related to the
> user's cost
> > and what are user need that must be a very interest projects.  I think
> many
> > members in IDN WG of IETF also like to know the detail .  You give me
> a very
> > strange impression of IETF.  Can someone in IETF can help more ?
> >
> > L.M.Tseng
> >
>




From owner-idn@ops.ietf.org  Sun Oct 28 12:16:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14697
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 12:16:37 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xtM7-000E99-00
	for idn-data@psg.com; Sun, 28 Oct 2001 09:04:15 -0800
Received: from smtp21.singnet.com.sg ([165.21.101.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xtM5-000E93-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 09:04:14 -0800
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp21.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9SH4sp15097;
	Mon, 29 Oct 2001 01:04:54 +0800
Message-ID: <01b001c15fd2$8d037730$1c01000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <jet-member@nic.ad.jp>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <jet-member@nic.ad.jp>, <idn@ops.ietf.org>, <brunner@nic-naa.net>
References: <200110281555.f9SFtur30634@nic-naa.net> <01a001c15fd1$fd848a90$1c01000a@jamessonyvaio>
Subject: [idn] Re: [JET-member 456] Re: Fw: Re: new members invitation 
Date: Mon, 29 Oct 2001 01:04:05 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Anyway, this is an overflow discussion from JET. If we wish to take

s/take/talk/

> about "scale" problem, lets wait for the draft which JET is preparing

s/JET/some of the JET members/

> first then others can participate the discussion in a more
constructive
> manner.

Sorry, need sleep now.

-James Seng




From owner-idn@ops.ietf.org  Sun Oct 28 12:17:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14708
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 12:17:24 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xtIH-000E0O-00
	for idn-data@psg.com; Sun, 28 Oct 2001 09:00:17 -0800
Received: from smtp23.singnet.com.sg ([165.21.101.203])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xtIG-000E0A-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 09:00:16 -0800
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp23.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9SH2oL23211;
	Mon, 29 Oct 2001 01:02:50 +0800
Message-ID: <01a001c15fd1$fd848a90$1c01000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <jet-member@nic.ad.jp>, <idn@ops.ietf.org>, <brunner@nic-naa.net>
References: <200110281555.f9SFtur30634@nic-naa.net>
Subject: Re: [idn] Re: [JET-member 446] Re: Fw: Re: new members invitation 
Date: Mon, 29 Oct 2001 01:00:04 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I agree with you - "scale" is an engineering consideration.
But "cost" (economy), OTOH, is not.

Anyway, this is an overflow discussion from JET. If we wish to take
about "scale" problem, lets wait for the draft which JET is preparing
first then others can participate the discussion in a more constructive
manner.

-James Seng

----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
Cc: <jet-member@nic.ad.jp>; <idn@ops.ietf.org>; <brunner@nic-naa.net>
Sent: Sunday, October 28, 2001 11:55 PM
Subject: Re: [idn] Re: [JET-member 446] Re: Fw: Re: new members
invitation


> James,
>
> Substitute "cost" (or "economy") for "scale".
>
> As Deng pointed out some _weeks_ ago, the buy-to-exhaustion "solution"
to
> the SC/TC issue DOESN'T SCALE. The same holds for any contention
mechanism,
> aka a "DRP". Even when both are "free".
>
> Remember scaling?
>
> Cheers,
> Eric




From owner-idn@ops.ietf.org  Sun Oct 28 12:23:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14758
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 12:23:11 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xtTV-000EQ4-00
	for idn-data@psg.com; Sun, 28 Oct 2001 09:11:53 -0800
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xtTU-000EPy-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 09:11:52 -0800
Received: from [165.227.249.20] (165-227-249-20.client.dsl.net [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f9SHBk815323
	for <idn@ops.ietf.org>; Sun, 28 Oct 2001 09:11:46 -0800 (PST)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05101004b801ea41011d@[165.227.249.20]>
In-Reply-To: <003301c15f55$16f5a220$4407e29f@deng>
References: 
 <166.2ea4bac.290ad741@cs.com><00b001c15e3e$1e64f280$cd462b18@mtag1.on.home
 .com><497812.1004124760@localhost>
 <007101c15e8e$cc0919c0$f006738c@ncu.edu.tw>
 <3399691.1004173125@localhost> <003301c15f55$16f5a220$4407e29f@deng>
Date: Sun, 28 Oct 2001 09:11:38 -0800
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] An ignorant question about TC<-> SC
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 10:06 AM +0800 10/28/01, xiang deng wrote:
>Yes, multiple registrations in DNS is better than do nothing.

Good, we agree here.

>But, there are still some problems can not solve:

And here too!

>1). Just do one for the SC and one for the TC, it isn't enough. Because other
>person can register mixed TC/SC domain name.

If anyone on this list has said "just do one for each", they are 
incorrect. The right solution is "do as many as are needed". That 
number will change with names, of course.

>How to deal with the disputations of
>registration. Such disputations will not disappear, if we have no 
>real solution about it.
>it's policy issue.

Exactly right. It has nothing to do with the IETF. The IETF has never 
dealt with the exact same policy issue for *any* language, nor have 
we even started writing up policy proposals for any. Many examples 
have already been given, such as "color" and "colour", or "koln" and 
"köln". Although not identical, these types of examples have the same 
kinds of problems to end users as Traditional and Simplified Chinese 
do.

>2). multiple registrations in DNS can solve a part of the issue, How 
>to solve the
>delegation issue of subdomain and keep the consistency.
>it's technology issue.

Yes, but not one for the IDN WG. This affects all host delegations, 
not just ones that use internationalized names, and it has been a 
real-world problem for over a decade. If people have technical 
solutions for this very thorny issue, they should definitely bring 
them to the DNSEXT working group.

>3). if we provide multiple registration solution for customs, we 
>must guarantee the multiple
>records belong to one custom. but from technology view, we can not 
>guarantee it.

Exactly right. That is the way it is for all languages (including US 
English), and it will affect everyone the same when we 
internationalize the DNS. In fact, it will also affect everyone the 
same for every internationalized protocol, not just DNS. There is no 
protocol now that says "mail sent to thom@example.com should be 
delivered to tom@example.com" even though those two are more 
equivalent to English-speakers than traditional and simplified 
Chinese characters are to Chinese-speakers.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Sun Oct 28 12:26:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14809
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 12:26:37 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xtTd-000EQv-00
	for idn-data@psg.com; Sun, 28 Oct 2001 09:12:01 -0800
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xtTd-000EQl-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 09:12:01 -0800
Received: from [165.227.249.20] (165-227-249-20.client.dsl.net [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f9SHBi815319;
	Sun, 28 Oct 2001 09:11:45 -0800 (PST)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05101003b801e8c9a90b@[165.227.249.20]>
In-Reply-To: <001e01c15fae$010900c0$f006738c@ncu.edu.tw>
References: 
 <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp><01c801c15
 c3d$d9a7ae50$4407e29f@deng> <20011024130954A.yone@nic.ad.jp>
 <024101c15c42$372e1b50$4407e29f@deng>
 <007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio>
 <003f01c15f5c$1d4e5f70$ec1bd9d2@temp>
 <001101c15f64$7eb3b780$1c01000a@jamessonyvaio>
 <016601c15f7d$14325c40$ec1bd9d2@temp>
 <005501c15f80$9dd52a10$1c01000a@jamessonyvaio>
 <000d01c15f81$5573d900$ec1bd9d2@temp>
 <006301c15f82$da0cbe60$1c01000a@jamessonyvaio>
 <001e01c15fae$010900c0$f006738c@ncu.edu.tw>
Date: Sun, 28 Oct 2001 09:00:43 -0800
To: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>,
        <jet-member@nic.ad.jp>, <idn@ops.ietf.org>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: [idn] Re: [JET-member 443] Re: Fw: Re: new members invitation
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 8:42 PM +0800 10/28/01, 
=?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= wrote:
>              If an Engineering Requirement is not related to the user's cost
>and what are user need that must be a very interest projects.

There is no inherent cost to multiple registrations. All registration 
cost is assigned by the registry (and, in some models, by the 
registry's agents, the registrars). A registry can have a policy that 
"if many names have identical meanings, all those names are 
registered for the same fee as a single name". It is up to the 
registry to decide what "identical" and "meanings" is, of course. For 
every language, there are different guidelines for those two words; 
it would be good to have some common advice on various languages.

>   I think many
>members in IDN WG of IETF also like to know the detail .

Yes, exactly. This discussion has elicited a lot of detail that was 
unknown to many people before now.

>   You give me a very
>strange impression of IETF.  Can someone in IETF can help more ?

If you listen to just one person's description of the IETF, you are 
sure to get a skewed picture. If you listen to many peoples' 
descriptions, you can weight and combine them yourself. The IETF is 
an extremely open organization. The mailing lists of all the WGs are 
freely available. And everyone has an email address at which you can 
contact them. :-)

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Sun Oct 28 12:35:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14865
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 12:35:49 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xtgp-000Eyv-00
	for idn-data@psg.com; Sun, 28 Oct 2001 09:25:39 -0800
Received: from vix.samspade.org ([204.152.186.148] helo=blighty.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xtgp-000Eyo-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 09:25:39 -0800
Received: by blighty.com (Postfix, from userid 1000)
	id B81D4650; Sun, 28 Oct 2001 09:27:44 -0800 (PST)
Date: Sun, 28 Oct 2001 09:27:44 -0800
From: Steve Atkins <steve@blighty.com>
To: idn@ops.ietf.org
Subject: [idn] List owner?
Message-ID: <20011028092744.A39943@blighty.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Could the list owner contact me off-list, please?

Cheers,
  Steve



From owner-idn@ops.ietf.org  Sun Oct 28 13:31:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15169
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 13:31:36 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xuVv-000GtR-00
	for idn-data@psg.com; Sun, 28 Oct 2001 10:18:27 -0800
Received: from gate.sinica.edu.tw ([140.109.4.130])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xuVu-000GtL-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 10:18:26 -0800
Received: from itsnb (140-109-225-197.adsl.sinica.edu.tw [140.109.225.197])
	by gate.sinica.edu.tw (8.11.3/8.11.3) with SMTP id f9SIICJ26916;
	Mon, 29 Oct 2001 02:18:13 +0800 (CST)
Message-ID: <005b01c15fdc$ebe39910$c5e16d8c@itsnb>
From: "Chun-Hsin Wu" <wuch@gate.sinica.edu.tw>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
References: <166.2ea4bac.290ad741@cs.com><00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com><497812.1004124760@localhost> <007101c15e8e$cc0919c0$f006738c@ncu.edu.tw> <3399691.1004173125@localhost> <003301c15f55$16f5a220$4407e29f@deng> <000701c15f59$89cdf9b0$1c01000a@jamessonyvaio> <003a01c15f65$b0fe3570$4407e29f@deng> <000d01c15f6a$c74cdd40$1c01000a@jamessonyvaio> <00e601c15f77$b105f870$4d0c7f8c@itsnb> <004b01c15f79$bea28cd0$1c01000a@jamessonyvaio>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Mon, 29 Oct 2001 02:18:18 +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.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > 1. Most IMEs in Traditional Windows 2000 can support TC and SC
> >  directly without switching, even they can let the user type in
> >  Japanese characters without switching. It is not unusual for one IME
> >  to support all, or as many as possible, Unicode characters if the
system
> [snip]
>
> On Windows, you install 2 IME, one for TC and the other for SC. You
> toggle between these two while you key in.

I'm curious about why you are so confident that I must install
TWO IMEs, one for TC and the other for SC. Do you use TC
Windows 2000 daily? :-) I don't know whether you do, but I
do use TC Windows 2000 to input TC quite often. Besides,
sometimes I also use the same input method software to input
SC and Japanese characters for Web queries, althouth it is
designed specially for TC.

Anyway, I'm sure I can install ONE IME to input TC and SC
together. As examples, let's try to input the second Chinese
character of China, U570B for TC and U56FD for SC, by
any ONE of the input methods I mentioned in my last message.
(The example character means country/nation in English.)

Method 1. Type "EJI6", specifying the pronouncing of the
example character, into the default TC phonetic input method
of TC Windows 2000, and it will list lots of characters with
the same pronouncing in pages, 10 candidates per page.
Among them, if you choose Candidate 1, you get U570B,
the TC example character. Or if you choose Candidate 5
on the 2nd page, you get U56FD, the SC example character.

Method 2. Type "OKD" into the Boshimy input method
software for TC Windows 2000. (This input method is widely
used for most users who want to input TC characters fast.)
Among the prompt candidates, Candidate 0 is U570B,
the TC example character, and Candidate 2 is U56FD,
the SC example character.

In addition, Mr. Xiang Deng had also explained that he can
type TC AND SC in a very usual SC IME without switching.

So it is clear that we don't need to install TWO IMEs to
input mixed TC and SC in TC Windows 2000. The user also
does not need to toggle between TC and SC while input. It
is natural that one TC input method software aims to make
the user input as many Unicode characters (and as easy)
as possible. Indeed, almost every add-on TC input method
software can support far more HAN characters than those
defined in Unicode, since some other charsets define more
characters than Unicode. The market will drive the software
company to do so, becoming a Uni-input method software
and supporting as many HAN characters as possible.

I sincerely hope you get chance to try the above examples
and verify them.

>
> > 2. In cases of "Taiwan" and "Taipei", the TC and SC characters for the
> >    first character "Tai", U53F0 and U81FA, are both widely and
> >    interchangeably used in Taiwan. You can find examples of mixed uses
> >    in Chinese Web sites, such as TAIpei City Government, National
>
> They are both Traditional form one is T-T, the other is T-S. Both exist
> on a TC IME.
> I can understand the big problem of TC and SC domain names.

It depends on how you define TC and SC. You can also say
it is an example character that can be found in both TC and
SC. As I know, several characters in SC scripts and Japanese
scripts are *commonly*  and interchangeably used in Taiwan,
and part of them are supported in TC charsets. Chinese people
can recognize these kinds of characters equivalently.

Personally, I prefer to say they are big problems of HAN
domain names rather than TC-SC domain names. As an
example, there are three Han characters in Unicode for
my surname 'Wu', one of the top ten surnames in Taiwan:
U5433 for TC, U5434 for SC, and U5449 for Japanese.

> I am not too sure of the problem of "mixed TC & SC" identifiers. Please
> do provide some statistic if you can. Thanks.

As I know, due to current TC/SC registration policies in the
*running* testbeds that support the tsconv draft, you can not
get the precise statistics.


Chun-Hsin Wu






From owner-idn@ops.ietf.org  Sun Oct 28 13:52:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15267
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 13:52:46 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xuri-000Hfv-00
	for idn-data@psg.com; Sun, 28 Oct 2001 10:40:58 -0800
Received: from gate.sinica.edu.tw ([140.109.4.130])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xurh-000Hfh-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 10:40:57 -0800
Received: from itsnb (140-109-225-197.adsl.sinica.edu.tw [140.109.225.197])
	by gate.sinica.edu.tw (8.11.3/8.11.3) with SMTP id f9SIetJ04129;
	Mon, 29 Oct 2001 02:40:55 +0800 (CST)
Message-ID: <008001c15fe0$17c67680$c5e16d8c@itsnb>
From: "Chun-Hsin Wu" <wuch@gate.sinica.edu.tw>
To: <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <166.2ea4bac.290ad741@cs.com><00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com><497812.1004124760@localhost><007101c15e8e$cc0919c0$f006738c@ncu.edu.tw><3399691.1004173125@localhost><003301c15f55$16f5a220$4407e29f@deng><000701c15f59$89cdf9b0$1c01000a@jamessonyvaio><003a01c15f65$b0fe3570$4407e29f@deng><000d01c15f6a$c74cdd40$1c01000a@jamessonyvaio> <4.2.0.58.J.20011028155518.040c9810@localhost>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Mon, 29 Oct 2001 02:41:01 +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.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> >2. In cases of "Taiwan" and "Taipei", the TC and SC characters for the
> >  first character "Tai", U53F0 and U81FA, are both widely and
> >  interchangeably used in Taiwan. You can find examples of mixed uses
> >  in Chinese Web sites, such as TAIpei City Government, National
> >  TAIwan University, TAIwan Semiconductor Manufacturing Company
> >  (TSMC), and so on. If we support top-level IDNs in the future, every
> >  domain and host below IDN.tw will have AT LEAST two records,
> >  one in  IDN.U53F0-wan and the other in IDN.U81FA-wan.
> 
> This is a very specific case (there are others like this, but
> not that many). For companies/organizations, they should just
> register both variants. For the top-level domain, there should
> be only one. It would probably be U53F0-wan. Please note that
> this is very similar to two-letter combinations for countries
> in ASCII; to a certain extent, people just have to learn them,
> e.g. that it's 'jp' and not 'ja' for Japan,...

According to your suggestion, we should also have only one
form for the second Chinese character of China, and you might
prefer U56FD (for SC) rather than U570B (for TC). I doubt
how many Chinese can accept your suggestion. *_*

I don't think the case is similar to two-letter combinations for
countries. It's more similar to that we should have only one
word for America, United States, and USA. For example,
people have to learn it is 'USA', and you can not use
neither 'United States' nor 'America' as the TLD. I also doubt
how many Americans can agree with this idea. :-)

Regards,

Chun-Hsin Wu




From owner-idn@ops.ietf.org  Sun Oct 28 14:26:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15461
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 14:26:07 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xvDN-000IU4-00
	for idn-data@psg.com; Sun, 28 Oct 2001 11:03:21 -0800
Received: from gate.sinica.edu.tw ([140.109.4.130])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xvDL-000ITw-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 11:03:20 -0800
Received: from itsnb (140-109-225-197.adsl.sinica.edu.tw [140.109.225.197])
	by gate.sinica.edu.tw (8.11.3/8.11.3) with SMTP id f9SJ31J10455;
	Mon, 29 Oct 2001 03:03:02 +0800 (CST)
Message-ID: <00b701c15fe3$2e87ef40$c5e16d8c@itsnb>
From: "Chun-Hsin Wu" <wuch@gate.sinica.edu.tw>
To: "James Seng/Personal" <jseng@pobox.org.sg>, <idn@ops.ietf.org>
References: <166.2ea4bac.290ad741@cs.com><00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com><497812.1004124760@localhost> <007101c15e8e$cc0919c0$f006738c@ncu.edu.tw> <3399691.1004173125@localhost> <003301c15f55$16f5a220$4407e29f@deng> <000701c15f59$89cdf9b0$1c01000a@jamessonyvaio> <003a01c15f65$b0fe3570$4407e29f@deng> <000d01c15f6a$c74cdd40$1c01000a@jamessonyvaio> <00e601c15f77$b105f870$4d0c7f8c@itsnb> <004b01c15f79$bea28cd0$1c01000a@jamessonyvaio> <005b01c15fdc$ebe39910$c5e16d8c@itsnb>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Mon, 29 Oct 2001 03:03:07 +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.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > I am not too sure of the problem of "mixed TC & SC" identifiers. Please
> > do provide some statistic if you can. Thanks.
> 
> As I know, due to current TC/SC registration policies in the
> *running* testbeds that support the tsconv draft, you can not
> get the precise statistics.

For example, if you register a two-char Chinese domain name
in one of the four combinations: SC-SC, SC-TC, TC-SC, and
TC-TC, the other three combinations will be reserved to
prevent confusion and dispute in the future.

I'm not so sure whether my explanation can answer your
question. WARNING: I do not know the policies
thoroughly. Just for your reference.

Regards,

Chun-Hsin Wu




From owner-idn@ops.ietf.org  Sun Oct 28 15:22:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15767
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 15:22:37 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xwAI-000Km8-00
	for idn-data@psg.com; Sun, 28 Oct 2001 12:04:14 -0800
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xwAG-000Klw-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 12:04:13 -0800
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9SK5mr36403;
	Sun, 28 Oct 2001 15:05:48 -0500 (EST)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110282005.f9SK5mr36403@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        jet-member@nic.ad.jp, idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Re: [JET-member 446] Re: Fw: Re: new members invitation 
In-Reply-To: Your message of "Mon, 29 Oct 2001 01:00:04 +0800."
             <01a001c15fd1$fd848a90$1c01000a@jamessonyvaio> 
Date: Sun, 28 Oct 2001 15:05:48 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James,

> I agree with you - "scale" is an engineering consideration.
> But "cost" (economy), OTOH, is not.

Assume that "registration" of a "name" containing characters in the SC and/or
TC character sets with the .FROTZ TLD registry is "free". No VISA card, no
wire transfer, postal coupons or micro-payments. Free. Like .US.

Assume also that "dispute resolution" of a "name" containing characters in
the SC and/or TC character sets under the Dispute Resolution Policy (DRP)
of the .FROTZ TLD registry is "free". No VISA card, no wire transfer, postal
coupons or micro-payments. Free. Also like .US, at least in theory.


Now that everything in the problem space is zero "cost", and "buy" means
only perform whatever non-cash ritual is required by the the .FROTZ registry
system (registrars don't charge money either), and "defend" in the .FROTZ DRP
means only perform whatever non-cash ritual is required by the .FROTZ registry
system (mediators and lawyers don't charge money either), and the non-cash
ritual is simply to read and write modest bits of email without the use of
any autonoma other than a comodity MUA ...

For a 10 character "name", assuming only 1-to-1 equivalences for all 10 of
the characters, 2^^10 items of email are required to "register" the name.
Another 2^^10 items to "defend" the name. That's about the total volume of
email on the IDN list this year (between 1K and 2K seperate mailings, but
I'm _not_ counting -- the point is tedium, saturation even boredom). Even
if there is no "cost" associated with any action, the take-to-exhaustion
"solution" has the effect of limiting the length of character strings to a
fraction of whatever scheme is employed to use the 63 bytes available.


You had this issue in another WG, where you thought that the authentication
mechanism could be, without cost, extended from a end-point set the size of
10^^3 or 10^^4, to an end-point set the size of 10^^6 or 10^^7.

Neither that activity nor this one is theoretical. Cost is not "layer 9",
if you really think it is, go sit in on variable- vs fixed-length forwarding
lookup or any equivalent problem in layers 2 or 3.


Now, on the registry side that was 2^^10 blips in the zone file for each
name, assume 10^^6 distinct names, each 10 character, plus 2^^10 extra
equivalences ... that's 10^^9 records. To be equitable, assume I/O, store,
and processing are "free", but not instantaneous. Even if there is no "cost"
associated with any action, the multiple entries in zone files recommended
(the UTC recommendataion) "solution" has the effect of limiting the length
of character strings to a fraction of whatever scheme is employed to use the
63 bytes available.

Eric



From owner-idn@ops.ietf.org  Sun Oct 28 15:49:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15875
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 15:49:02 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xwch-000Lq9-00
	for idn-data@psg.com; Sun, 28 Oct 2001 12:33:35 -0800
Received: from gate.sinica.edu.tw ([140.109.4.130])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xwcf-000Lq1-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 12:33:34 -0800
Received: from itsnb (140-109-225-197.adsl.sinica.edu.tw [140.109.225.197])
	by gate.sinica.edu.tw (8.11.3/8.11.3) with SMTP id f9SKXWJ04709;
	Mon, 29 Oct 2001 04:33:32 +0800 (CST)
Message-ID: <000901c15fef$d2d9b4f0$c5e16d8c@itsnb>
From: "Chun-Hsin Wu" <wuch@gate.sinica.edu.tw>
To: <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <166.2ea4bac.290ad741@cs.com><00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com><497812.1004124760@localhost><007101c15e8e$cc0919c0$f006738c@ncu.edu.tw><3399691.1004173125@localhost><003301c15f55$16f5a220$4407e29f@deng><000701c15f59$89cdf9b0$1c01000a@jamessonyvaio><003a01c15f65$b0fe3570$4407e29f@deng><000d01c15f6a$c74cdd40$1c01000a@jamessonyvaio> <4.2.0.58.J.20011028155518.040c9810@localhost> <008001c15fe0$17c67680$c5e16d8c@itsnb>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Mon, 29 Oct 2001 04:33:37 +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.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > >2. In cases of "Taiwan" and "Taipei", the TC and SC characters for the
> > >  first character "Tai", U53F0 and U81FA, are both widely and
> > >  interchangeably used in Taiwan. You can find examples of mixed uses
> > >  in Chinese Web sites, such as TAIpei City Government, National
> > >  TAIwan University, TAIwan Semiconductor Manufacturing Company
> > >  (TSMC), and so on. If we support top-level IDNs in the future, every
> > >  domain and host below IDN.tw will have AT LEAST two records,
> > >  one in  IDN.U53F0-wan and the other in IDN.U81FA-wan.
> > 
> > This is a very specific case (there are others like this, but
> > not that many). For companies/organizations, they should just
> > register both variants. For the top-level domain, there should
> > be only one. It would probably be U53F0-wan. Please note that
> > this is very similar to two-letter combinations for countries
> > in ASCII; to a certain extent, people just have to learn them,
> > e.g. that it's 'jp' and not 'ja' for Japan,...
> 
> According to your suggestion, we should also have only one
> form for the second Chinese character of China, and you might
> prefer U56FD (for SC) rather than U570B (for TC). I doubt
> how many Chinese can accept your suggestion. *_*
> 
> I don't think the case is similar to two-letter combinations for
> countries. It's more similar to that we should have only one
> word for America, United States, and USA. For example,
> people have to learn it is 'USA', and you can not use
> neither 'United States' nor 'America' as the TLD. I also doubt
> how many Americans can agree with this idea. :-)

For full-name DNS, White House may need to register at least
three records:
    "America"."USA"
    "United States"."USA"
    "USA"."USA"
If they forget to register "United States of America"."USA",
some other one may register it validly. This may imply that
every IDN customer must know and register all combinations
of the domain name he wants to register.

Besides, users must know
    "America"."America",
    "United States"."United States"
and so on that not ending with "USA" are invalid as
full-name DNS.

WARNING: This analogy can not reflect all problems
of Han characters (CJK+SC+TC). Analogize further
with caution. Hope I do not confuse you in an
unexpected way.

Sincerely,

Chun-Hsin Wu




From owner-idn@ops.ietf.org  Sun Oct 28 17:33:06 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16520
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 17:33:05 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xyII-000Ppw-00
	for idn-data@psg.com; Sun, 28 Oct 2001 14:20:38 -0800
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xyIH-000Ppq-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 14:20:37 -0800
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 204654 for idn@ops.ietf.org; Sat, 27 Oct 2001 17:20:29 -0500
Message-ID: <3BDC84B2.A90383C5@ehsco.com>
Date: Sun, 28 Oct 2001 16:20:34 -0600
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
CC: idn@ops.ietf.org
Subject: Re: [idn] iDNS re-chartering proposal, take 2
References: <5.1.0.14.2.20011027084819.03d3b6c0@brandenburg.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Dave Crocker wrote:

> Perhaps the most important goals in re-chartering this effort are to:
> 
>          1.  Narrow the scope of work
> 
>          2.  Specify deliverables very precisely
> 
>          3.  Specify dates for deliverable that are very near-term.

These are fine goals, but the specific objective items you cite are not
satisfactory to the weight of the task at hand. Instead, they raise more
artificial barriers.

> 2.  Focus on the production of a single technical specification to be
> offered as a standard.  Hence the working group is no longer exploring,
> researching or otherwise having broad discussions.

Some of the proposals are at odds with such an objective, and so the
adoption of this objective would only serve to narrow the work items. For
example, UDNS requires a coordinated release for at least two purposes: so
that name lengths can be synchronized, and so that delegation entities can
coordinate delegations they make as UTF-8 and ACE encoded representations
of the same UCS string. Adopting your work items would mean that those
considerations would not be incorporated (unless you added them to ACE
while I wasn't looking), and would therefore result in alternatives being
non-conformant with the WG output.

Additional beauracracy does not result in better science. Let's let the
technology compete on its own merits, okay?

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



From owner-idn@ops.ietf.org  Sun Oct 28 18:08:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16783
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 18:08:53 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xypJ-00016B-00
	for idn-data@psg.com; Sun, 28 Oct 2001 14:54:45 -0800
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xypJ-000165-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 14:54:45 -0800
Received: from jackie.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 OAA00421;
	Sun, 28 Oct 2001 14:54:14 -0800
Message-Id: <5.1.0.14.2.20011028145534.03d1f008@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 28 Oct 2001 15:05:10 -0800
To: "Eric A. Hall" <ehall@ehsco.com>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] iDNS re-chartering proposal, take 2
Cc: idn@ops.ietf.org
In-Reply-To: <3BDC84B2.A90383C5@ehsco.com>
References: <5.1.0.14.2.20011027084819.03d3b6c0@brandenburg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 04:20 PM 10/28/2001 -0600, Eric A. Hall wrote:
>  Instead, they raise more artificial barriers.

The purpose of a charter is to make clear what IS to be done and what IS 
NOT to be done.  As such, raising barriers is one of the requirements for a 
good charter, if the working group is ever to be productive.

Let us be clear about the term "productive".  Discussion, debate and 
learning are all interesting and worthy activities.  However, none of them 
is the goal of an IETF working group.

The goal of an IETF working group is to produce a specification that gets 
used.  Hence it must solve a real problem, solve it in a manner that others 
find useful, and solve it in a timely manner.

Protracted debate ensures that none of these criteria is satisfied.

For example, this group has gone at least one extra year longer than it 
should have, given the urgency of the problem it is trying to solve.  As 
such, there is some potential that independent, proprietary (ie, closed) 
solutions will render the IETF work irrelevant.


> > 2.  Focus on the production of a single technical specification to be
> > offered as a standard.  Hence the working group is no longer exploring,
> > researching or otherwise having broad discussions.
>
>Some of the proposals are at odds with such an objective

How very strange.  Some of the proposals do not want a single technical 
specification, or they do not want to stop researching?

In any event, that is the problem.  Failing to converge on a single 
specification often kills working group utility.


>, and so the
>adoption of this objective would only serve to narrow the work items.

Excellent!  That is exactly what the proposed working is intended to 
accomplish.  Unless the work items are narrowed, no work gets done.


>For example, UDNS requires a coordinated release for at least two 
>purposes: so that name lengths can be synchronized, and so that delegation 
>entities can
>coordinate delegations they make as UTF-8 and ACE encoded representations 
>of the same UCS string.

uDNS a) is not a complete specification, and b) imposes operational 
requirements that are not viable in the existing DNS infrastructure.

It also does not have much practical support.


>Additional beauracracy does not result in better science. Let's let the
>technology compete on its own merits, okay?

We are doing engineering, not science.  Perhaps that disparity of view is 
the source of some difficulties among participants.

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 Oct 28 18:14:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16820
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 18:14:14 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xz0c-0001e7-00
	for idn-data@psg.com; Sun, 28 Oct 2001 15:06:26 -0800
Received: from heron.verisign.com ([216.168.233.95])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xz0b-0001e1-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 15:06:25 -0800
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 SAA03803
	for <idn@ops.ietf.org>; Sun, 28 Oct 2001 18:06:24 -0500 (EST)
Received: by VSVAPOSTALGW1.prod.netsol.com with Internet Mail Service (5.5.2653.19)
	id <4VQ824JZ>; Sun, 28 Oct 2001 18:05:28 -0500
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD6C5FBCE@vsvapostal3.prod.netsol.com>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: idn@ops.ietf.org
Subject: RE: [idn] An ignorant question about TC<-> SC
Date: Sun, 28 Oct 2001 17:58:46 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="big5"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> -----Original Message-----
> From: Chun-Hsin Wu [mailto:wuch@gate.sinica.edu.tw]
> Sent: Sunday, October 28, 2001 3:34 PM
> 
> 
> For full-name DNS, White House may need to register at least
> three records:
>     "America"."USA"
>     "United States"."USA"
>     "USA"."USA"
> If they forget to register "United States of America"."USA",
> some other one may register it validly. This may imply that
> every IDN customer must know and register all combinations
> of the domain name he wants to register.

This situation isn't unique to IDNs.  I can register foobar.com, and someone
else can register foo-bar.com if I don't.  I have to make a conscious
decision to register the name forms that are important to me.  Why should
IDNs be treated differently?

-Scott-



From owner-idn@ops.ietf.org  Sun Oct 28 18:16:32 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16839
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 18:16:31 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xz2x-0001hm-00
	for idn-data@psg.com; Sun, 28 Oct 2001 15:08:51 -0800
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xz2w-0001hf-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 15:08:50 -0800
Received: from jackie.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 PAA00951;
	Sun, 28 Oct 2001 15:08:48 -0800
Message-Id: <5.1.0.14.2.20011028150538.01d70e88@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 28 Oct 2001 15:08:41 -0800
To: Martin Duerst <duerst@w3.org>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] iDNS re-chartering proposal, take 2
Cc: idn@ops.ietf.org
In-Reply-To: <4.2.0.58.J.20011028143213.0394bdd0@localhost>
References: <5.1.0.14.2.20011027202302.03a94958@brandenburg.com>
 <4.2.0.58.J.20011028103527.03a361f0@localhost>
 <5.1.0.14.2.20011027084819.03d3b6c0@brandenburg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 02:42 PM 10/28/2001 +0900, Martin Duerst wrote:
>At 20:28 01/10/27 -0700, Dave Crocker wrote:
>>   the software doing the searching might not be a human, but it's place 
>> in the overall DNS system is the same place as human users.  That is, in 
>> the user agent, not the DNS infrastructure.
>
>User agent is a wide term, and may be okay. Human input/output
>is quite different, and inappropriate. As a human being I don't
>like to be thrown into the same pot as some software. So can
>we please change that to 'DNS input and output modules'?

I am not thrilled with the term "human i/o" either.  The difficulty is in 
using a term that clearly marks the DNS end-points (including DNS server 
administration, since that is where names are first entered.)

In the world of email and perhaps directories, the term "user agent" is 
pretty clear.  In the world of the DNS, it is not.

"DNS input/output modules" could as easily refer to communication between 
DNS servers, hence it is not sufficiently specific.

In case it is not obvious, I am at a bit of a loss, so the best I can do is 
suggest that we keep seeking suggestions for a term that will 
work.  (Frankly I would be delighted if we could find a way to re-apply the 
UA/MTA model, the way the x.500 directory people did.)

And that prompts me to ask whether simply saying:

         DNS Client

would satisfy people???

>I just wanted to make sure that the charter doesn't
>give the impression that all software has to use ACE throughout
>because conversion happens on 'Human input/output'.

Does "DNS client" satisfy this concern?


>>However the strings are created outside of DNS.  The only thing the DNS 
>>system must do is PRESERVE that order.
>
>DNS names appear on paper and displays. If we are not sure that
>the same internal string of characters will lead to the same display
>and vice versa, then all our work on idn will just lead to a lot of
>confusion. It may look as if just extending the set of characters
>won't change anything here, but at least for Arabic and Hebrew,
>that's not the case.

I fear that my point is being missed:

1.  The registrant decides what order to write the characters.
2.  That is how they are put into the DNS and returned from the DNS and 
displayed by DNS client software.

As long as the system preserves whatever order the registrant specified, 
then how does the DNS have to know whether it is arabic, hebrew, kanji, or 
greek?

In other words, I believe the DNS is, and must be, entirely opaque with 
respect to character ordering.

With respect to strings on paper or displays, again, the point is that it 
must be shown in whatever order the registrant specified, it.


>>>What's the difference between "Working Group action items are:" and "The 
>>>Action Item(s) for the Working Group are:"
>...
>I was asking something different, sorry. Why are there two subtitles in 
>your charter listing action items for the WG, one of them with two action 
>items, and one with four?

My turn to apologize.  I had not noticed that there were two sections with 
essentially the same labels.  Yes they should be changed, possibly 
eliminating one altogether.  I'll do something about that for the next 
version of the text.


>>>>Nov 2001        Draft of DNS character set enhancement specification
>
>Why not just call it 'DNS internationalization architecture specification'?

Your suggestion is for a term that is clean and impressive.  However I 
believe it also is too broad.

There are, perhaps, other issues in internationalization of the DNS that we 
are NOT working on.  Hence we need a term that excludes, as well as includes.

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 Oct 28 18:27:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16917
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 18:27:57 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xzCW-0002CS-00
	for idn-data@psg.com; Sun, 28 Oct 2001 15:18:44 -0800
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xzCV-0002CJ-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 15:18:43 -0800
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 204662; Sat, 27 Oct 2001 18:18:36 -0500
Message-ID: <3BDC9251.6FD8C5FA@ehsco.com>
Date: Sun, 28 Oct 2001 17:18:41 -0600
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dave Crocker <dhc@dcrocker.net>
CC: idn@ops.ietf.org
Subject: Re: [idn] iDNS re-chartering proposal, take 2
References: <5.1.0.14.2.20011027084819.03d3b6c0@brandenburg.com> <5.1.0.14.2.20011028145534.03d1f008@dcrocker.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Dave Crocker wrote:

> We are doing engineering, not science.  Perhaps that disparity of view
> is the source of some difficulties among participants.

It is certainly clear that scientific analysis is being sacrificed in
favor of agenda manipulation and beauracracy, yes.

> uDNS a) is not a complete specification, and b) imposes operational
> requirements that are not viable in the existing DNS infrastructure.

IPv6 is different from IPv4, OSPF was different from RIP, IMAP is
different from POP, why is anybody surprised that a UTF-8 DNS which
provides a top-to-bottom internationalized DNS is going to be different
from a hostname-restricted IDNA?

Of course, last time this was brought up for discussion, the beauracracy
called technical analysis off-topic. No surprise you want to formalize
such a position through agenda reconstruction. Color me unimpressed.

> How very strange.  Some of the proposals do not want a single technical
> specification, or they do not want to stop researching?

What's so wrong with multiple complementary specifications? Why are you
committed to a single specification which only serves a single objective
of legacy compatibility and which does so at the expense of every protocol
and application yet to be written?

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



From owner-idn@ops.ietf.org  Sun Oct 28 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 ESMTP id SAA17026
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 18:47:56 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xzQP-0002qM-00
	for idn-data@psg.com; Sun, 28 Oct 2001 15:33:05 -0800
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xzQO-0002q8-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 15:33:04 -0800
Received: from jackie.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 PAA01812;
	Sun, 28 Oct 2001 15:32:34 -0800
Message-Id: <5.1.0.14.2.20011028152132.01c501c0@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 28 Oct 2001 15:32:24 -0800
To: "Eric A. Hall" <ehall@ehsco.com>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] iDNS re-chartering proposal, take 2
Cc: idn@ops.ietf.org
In-Reply-To: <3BDC9251.6FD8C5FA@ehsco.com>
References: <5.1.0.14.2.20011027084819.03d3b6c0@brandenburg.com>
 <5.1.0.14.2.20011028145534.03d1f008@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 05:18 PM 10/28/2001 -0600, Eric A. Hall wrote:
>It is certainly clear that scientific analysis is being sacrificed in
>favor of agenda manipulation and beauracracy, yes.

Ahh.  I see.  You have a complaint about working group process.

The procedures for redressing such grievances are well documented.  Please 
feel free to pursue them.  Note that a small amount of complaining on the 
working group mailing list is a legitimate part of that process, as a way 
of assessing support for your complaint.  However I suspect that you are 
already long beyond that part.


> > uDNS a) is not a complete specification, and b) imposes operational
> > requirements that are not viable in the existing DNS infrastructure.
>
>IPv6 is different from IPv4, OSPF was different from RIP, IMAP is
>different from POP, why is anybody surprised that a UTF-8 DNS which
>provides a top-to-bottom internationalized DNS is going to be different
>from a hostname-restricted IDNA?

No one is surprised that "UTF-8 DNS", whatever that means, might be 
different from the existing DNS.  However surprise or not is irrelevant to 
the current discussion.

The key point is that, after two years of debate, it is time to declare 
that changes to the core DNS protocols, including changes to official 
character representation by that core, is no longer the technical path 
being pursued for near-term support of internationalized characters.  The 
approach to be taken is  to have end-system encapsulation, in the style of ACE.


> > How very strange.  Some of the proposals do not want a single technical
> > specification, or they do not want to stop researching?
>
>What's so wrong with multiple complementary specifications?

What is wrong with that approach is that it does not work.

Please review the last 11 years of IETF history, in particular the results 
of its trying to support multiple "complementary" (but actually competing) 
specifications, versus the results of choosing a single specification.  By 
contrast, review the stellar history of the equivalent OSI protocols, since 
they very much attempted to provide support of multiple alternatives, as 
you desire.


>Why are you committed to a single specification which only serves a single 
>objective of legacy compatibility and which does so at the expense of 
>every protocol and application yet to be written?

It serves both legacy compatibility AND the primary objective of 
internationalized characters.

Your assessment that it does so at some sort of unspecified cost to some 
set of unspecified protocols, that will be created at some unspecified 
times and for some unspecified set of functions, is quite seriously 
irrelevant to the current  requirements.

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 Oct 28 19:02:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17137
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 19:02:39 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15xzg5-0003Y9-00
	for idn-data@psg.com; Sun, 28 Oct 2001 15:49:17 -0800
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15xzg4-0003Xx-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 15:49:16 -0800
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 204670; Sat, 27 Oct 2001 18:49:08 -0500
Message-ID: <3BDC9979.1EA641A4@ehsco.com>
Date: Sun, 28 Oct 2001 17:49:13 -0600
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dave Crocker <dhc@dcrocker.net>
CC: idn@ops.ietf.org
Subject: Re: [idn] iDNS re-chartering proposal, take 2
References: <5.1.0.14.2.20011027084819.03d3b6c0@brandenburg.com>
	 <5.1.0.14.2.20011028145534.03d1f008@dcrocker.net> <5.1.0.14.2.20011028152132.01c501c0@dcrocker.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Dave Crocker wrote:

> Ahh.  I see.  You have a complaint about working group process.

No, I have an issue with agenda railroading. I feel no need to run for
mommy's skirts when things don't go my way, however.

> The key point is that, after two years of debate, it is time to declare
> that changes to the core DNS protocols, including changes to official
> character representation by that core, is no longer the technical path
> being pursued for near-term support of internationalized characters.

Perhaps this can be represented through some measure other than an
unsolicited agenda reconstruction.

> What is wrong with that approach is that it does not work.
> 
> Please review the last 11 years of IETF history, in particular the
> results of its trying to support multiple "complementary" (but actually
> competing) specifications, versus the results of choosing a single
> specification.

SMTP, IMAP, NNTP are complementary. RIP, OSPF and BGP work well together
when needed. HTTP and FTP aren't burning each other down. Golly, it almost
seems like complementary is the norm.

> Your assessment that it does so at some sort of unspecified cost to some
> set of unspecified protocols, that will be created at some unspecified
> times and for some unspecified set of functions, is quite seriously
> irrelevant to the current  requirements.

Protocols which comply with BCP18 will use UTF-8 for all protocol data
_except_ domain names, where they will require ACE. Going with ACE-only
directly equates to two mandatory encodings. This is an incredibly high
cost to lay on the Internet for the sole purpose of backwards
compatibility, particularly given the fact that there is no reason to
limit the Internet to just one choice. Other costs were itemized in the
last thread, but we can go through it again if you are up to completing
the discussion.

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



From owner-idn@ops.ietf.org  Sun Oct 28 20:32:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17526
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 20:32:38 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y0yo-0006wP-00
	for idn-data@psg.com; Sun, 28 Oct 2001 17:12:42 -0800
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y0yn-0006wI-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 17:12:41 -0800
Received: from zetnet.co.uk (man-s286.dialup.zetnet.co.uk [194.247.45.157])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f9T1C6q19839;
	Mon, 29 Oct 2001 01:12:07 GMT
Message-ID: <3BDCBB13.8C75B5B7@zetnet.co.uk>
Date: Mon, 29 Oct 2001 02:12:35 +0000
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: James Seng/Personal <jseng@pobox.org.sg>, idn@ops.ietf.org
Subject: Re: [idn] Update Charter revision 2
References: <Roam.SIMC.2.0.6.1003999760.18359.nordmark@bebop.france> <00d001c15d44$95d4b8f0$1701000a@jamessonyvaio>
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-----

James Seng/Personal wrote (~4 days ago):
> > > > have not been adequately addressed (in fact none of my technical
> > > > points were addressed at all).
> > >
> > > Your comments comes after the doc have been moved forward for IESG.
> > > Any changes to it will have to wait after their review.
> >
> > The WG should discuss the comments and they can even decide how they'd
> > like to modify the document. But it is best to not issue an updated
> > I-D until the AD review comments are back.
> 
> Thanks Erik. Yes, that is what I mean.
> 
> Discussion of the points raised by David can and should continue.

Good, I'm glad we agree. Since you're a coauthor of the requirements
draft, is it too much to ask that you actually make some substantive
comments, rather than just expressing a vague notion that it might be
a good idea to do so?

Please reply to my previous post suggesting the changes, saying to what
extent you agree or disagree with each of them.

- -- 
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

iQEVAwUBO9y6+DkCAxeYt5gVAQHHcgf/bePQ/TlVmAUqTjFz8DyAFcUN2kzijvJv
bz0bAX92vYunZo+bLWgzQBTUkEHKC7zdoe6LUOvWHAQcAKwnn0RR3Jn6Vl2eXbMH
gsveKzntcXF9/6v9CjgUDW/i/UeuG7G5Mqr9v8c+tk6UkxfKrV4Ql57WHreC766K
J5a2eAEBJwfDES4k2zAVPk67o8xZUnErcmVS6sv0aJpGED0Cy4ITRk2eIIw1x9Ym
aucRZGzvLP6cTvr7Bhjd7NTbb5ptPMTBgj8iybvTAdhhcMzGKsjcw3nbz0uXHSKu
pWxvjxFPbsf56UIIu7ARWjJ3JjHXVCWuYAwZvjPql9a0lRk9vNGstQ==
=0kMs
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Sun Oct 28 21:00:24 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17632
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 21:00:23 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y1Wr-0008Pb-00
	for idn-data@psg.com; Sun, 28 Oct 2001 17:47:53 -0800
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y1Wq-0008PU-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 17:47:52 -0800
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id KAA03250;
	Mon, 29 Oct 2001 10:47:26 +0900
Message-ID: <008001c1601b$ce7b11c0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>, "Mark Davis" <mark@macchiato.com>,
        "Yves Arrouye" <yves@realnames.com>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <4.2.0.58.J.20011025182258.036b42e0@localhost> <02f401c15d6e$cca3b0f0$ec1bd9d2@temp> <025201c15d74$937b5ed0$0c680b41@c1340594a> <031e01c15d77$cd0e4380$ec1bd9d2@temp>
Subject: Re: [idn] NFC vs NFKC
Date: Mon, 29 Oct 2001 10:48:17 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA17632

Hi, Mark and Martin,
Still we have the round-trip conversion problem in 
   mapping compat jamo into  conjoining jamo + filler sequence .

 Current UTC standards do not specify how to convert
 conjoining jamo + filler sequence back  into compat jamo which can be 1:1  mapped
 to KS C 5601 isolated jamo for localized rendering platforms.
 Many korean mobile devices and applications supports only KS C 5601.

 For proper rendering of isolated jamos in unicode, 
  mapping from conjoining jamo+filler sequence int into compat jamo
  should be defined somewhere in UTC standards.
 That's missing now. Rendering engine vendors have no authoritative reference for it now.
 Without that,  Mark's suggestion will fail to work  on most korean
  commercial platforms now and even in the forseeable *FUTURE*.

Soobok Lee


----- Original Message ----- 
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Mark Davis" <mark@macchiato.com>; "Yves Arrouye" <yves@realnames.com>; <idn@ops.ietf.org>; "Martin Duerst" <duerst@w3.org>
Sent: Friday, October 26, 2001 2:09 AM
Subject: Re: [idn] NFC vs NFKC


> 
> Not bad for future. But as for now, most current rendering platforms (on windows and unix/linux)
> would fail to support rendering filler sequences and display fillers as "white spaces". 
> That would cause confusions and misinterpretations for a long time until
> all user platforms are upgraded to support fillers.
> 
> Soobok Lee
> 
> ----- Original Message ----- 
> From: "Mark Davis" <mark@macchiato.com>
> To: "Soobok Lee" <lsb@postel.co.kr>; "Yves Arrouye" <yves@realnames.com>; <idn@ops.ietf.org>; "Martin Duerst" <duerst@w3.org>
> Sent: Friday, October 26, 2001 1:46 AM
> Subject: Re: [idn] NFC vs NFKC
> 
> 
> > Either deletion, prohibition or producing fillers can be accomplished, if
> > desired, by adding mappings to "D. Mapping Tables" in
> > http://www.ietf.org/internet-drafts/draft-ietf-idn-nameprep-06.txt. And this
> > is *without* having to change anything else in nameprep. For example, for
> > U+3131 HANGUL LETTER KIYEOK here are the three options:
> > 
> > Deletion:
> > 3131; ; Deletion
> > 
> > Prohibition:
> > 3131; 0000; Prohibition
> > 
> > Additional folding
> > 3131; 1100 1160; Additional Folding
> > 
> > In the last case, the medial filler is added. It is sufficient to do this
> > only for the initials, since that prevents any syllable formation. However,
> > if one wanted, the initial filler could be added before medials, such as for
> > U+314F HANGUL LETTER A below (or initial and final fillers could be added
> > before finals).
> > 
> > Additional folding
> > 314F; 115F 1161; Additional Folding
> > 
> > Mark
> > 
> > —————
> > 
> > Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
> > [http://www.macchiato.com]
> > 
> > ----- Original Message -----
> > From: "Soobok Lee" <lsb@postel.co.kr>
> > To: "Yves Arrouye" <yves@realnames.com>; <idn@ops.ietf.org>; "Martin Duerst"
> > <duerst@w3.org>
> > Sent: Thursday, October 25, 2001 09:04
> > Subject: Re: [idn] NFC vs NFKC
> > 
> > 
> > 
> > ----- Original Message -----
> > From: "Martin Duerst" <duerst@w3.org>
> >  >
> > > Hangul domain names in KS C 5601 would normally be encoded as
> > > precombined syllables. KS C 5601 provides about 2300 of them,
> > > the ones most often used. Users who want to used other Hangul
> > > syllables won't use non-conjoining Jamo (compatibility Jamo),
> > > because they will be displayed one Jamo at a time.
> > >
> > > In the nameprep design team, we discussed some cases where users
> > > might want to use sequences of independent consonant Jamo. There
> > > are a few web pages with some examples of these, but not too many.
> > > We are not sure whether they should be allowed in domain names or
> > > not, and if they are, how they should be represented.
> > >
> > 
> > Current windows 98 and above  support only  compatibility Jamo, does
> > not support "conjoining jamo + filler" sequence for isolated jamos
> > which are often found in informal texts/business names.
> > No display and No input method for "conjoining jamo + filler" in
> > windows O/S.
> > 
> > Compatiliby Jamo became the defacto standard for isolated jamos
> > inadvertantly and contrary to the intent of ISO Korean representatives and
> > UTC members.
> > 
> > NFKC maps Compatiblity Jamo to conjoining jamos withOUT fillers.
> > 
> > Nameprep's positions on NFKC's problematic handling of compat jamos
> > should be clarified. Two alternatives.
> > 
> >   1) NFC is used instead
> >   2) NFKC is used but bypass all characters from the compatibility jamo
> > block
> > 
> > Soobok Lee
> > 
> > 
> > >
> > > >[Edit] Is that because nobody uses these anymore, and so you would not
> > > >expect a modern invention like IDN to appear in an anachronic way? Is
> > that
> > > >the case with all LEGACY characters?
> > >
> > > I don't want IDN to carry unnecessary legacy compatibility
> > > baggage. If it turns out that something really helps the user
> > > (e.g. for the full-width Latin letters), I have nothing against
> > > mapping them. But I don't think it's a good idea to map a
> > > wholesale 3000, most of them not really used and very difficult
> > > to type in, just to get a few dozen mapped the right way.
> > > We can easily do the later without having to do the former.
> > >
> > >
> > > Regards,   Martin.
> > >
> > 
> > 
> 
> 




From owner-idn@ops.ietf.org  Sun Oct 28 21:44:41 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18836
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 21:44:40 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y2CH-000ACJ-00
	for idn-data@psg.com; Sun, 28 Oct 2001 18:30:41 -0800
Received: from smtp14.singnet.com.sg ([165.21.6.34])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y2CF-000AC9-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 18:30:40 -0800
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp14.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9T2Snw01359;
	Mon, 29 Oct 2001 10:28:49 +0800
Message-ID: <002701c16021$ae577900$1e01000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Chun-Hsin Wu" <wuch@gate.sinica.edu.tw>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
References: <166.2ea4bac.290ad741@cs.com><00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com><497812.1004124760@localhost><007101c15e8e$cc0919c0$f006738c@ncu.edu.tw><3399691.1004173125@localhost><003301c15f55$16f5a220$4407e29f@deng><000701c15f59$89cdf9b0$1c01000a@jamessonyvaio><003a01c15f65$b0fe3570$4407e29f@deng><000d01c15f6a$c74cdd40$1c01000a@jamessonyvaio> <4.2.0.58.J.20011028155518.040c9810@localhost> <008001c15fe0$17c67680$c5e16d8c@itsnb> <000901c15fef$d2d9b4f0$c5e16d8c@itsnb>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Mon, 29 Oct 2001 10:30:31 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Just one comment: Domain names are identifiers, not names.

-James Seng

> > I don't think the case is similar to two-letter combinations for
> > countries. It's more similar to that we should have only one
> > word for America, United States, and USA. For example,
> > people have to learn it is 'USA', and you can not use
> > neither 'United States' nor 'America' as the TLD. I also doubt
> > how many Americans can agree with this idea. :-)




From owner-idn@ops.ietf.org  Sun Oct 28 21:45:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18849
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 21:45:58 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y2JT-000AUM-00
	for idn-data@psg.com; Sun, 28 Oct 2001 18:38:07 -0800
Received: from smtp14.singnet.com.sg ([165.21.6.34])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y2JS-000AUB-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 18:38:06 -0800
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp14.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9T2aKw06107;
	Mon, 29 Oct 2001 10:36:20 +0800
Message-ID: <005e01c16022$bb1c1960$1e01000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
References: <Roam.SIMC.2.0.6.1003999760.18359.nordmark@bebop.france> <00d001c15d44$95d4b8f0$1701000a@jamessonyvaio> <3BDCBB13.8C75B5B7@zetnet.co.uk>
Subject: Re: [idn] Update Charter revision 2
Date: Mon, 29 Oct 2001 10:38:02 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I am a co-author because I wrote -01. I relinquish that role to Zita
since -03 and since then, done very little editing.

-James Seng

> Good, I'm glad we agree. Since you're a coauthor of the requirements
> draft, is it too much to ask that you actually make some substantive
> comments, rather than just expressing a vague notion that it might be
> a good idea to do so?
>
> Please reply to my previous post suggesting the changes, saying to
what
> extent you agree or disagree with each of them.




From owner-idn@ops.ietf.org  Sun Oct 28 21:52:07 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18868
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 21:52:06 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y2Ny-000Ahu-00
	for idn-data@psg.com; Sun, 28 Oct 2001 18:42:46 -0800
Received: from femail39.sdc1.sfba.home.com ([24.254.60.33])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y2Nx-000Ahn-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 18:42:45 -0800
Received: from c1340594a ([65.11.104.12]) by femail39.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20011029024244.RAGA4194.femail39.sdc1.sfba.home.com@c1340594a>;
          Sun, 28 Oct 2001 18:42:44 -0800
Message-ID: <00a901c16023$84bbb320$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>, "Yves Arrouye" <yves@realnames.com>,
        <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <4.2.0.58.J.20011025182258.036b42e0@localhost> <02f401c15d6e$cca3b0f0$ec1bd9d2@temp> <025201c15d74$937b5ed0$0c680b41@c1340594a> <031e01c15d77$cd0e4380$ec1bd9d2@temp> <008001c1601b$ce7b11c0$ec1bd9d2@temp>
Subject: Re: [idn] NFC vs NFKC
Date: Sun, 28 Oct 2001 18:43:40 -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 6.00.2600.0000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

This is not an issue.

1. You still have never shown a need for compatibility Jamo. I have
requested real examples on several occasions, but they never showed up. Even
more useful would be hard data. In how many of the Korean domain names that
have been registered in testbeds are compatibility jamo an issue? That is,
how many cases does a name contains an initial jamo compatibility character
followed *immediately* by a medial jamo compatibility character?

2. It is a trivial exercise to map sequences of conjoining jamo (with
filters) back to compatibility jamo in converting Unicode to 5601 (e.g. for
display in a web browser). If you really want, I'm sure that we can get the
UTC to have an explicit statement of how to do this in the next version of
the Unicode Standard, 3.2, due 2002Q1.

Mark
—————

Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
[http://www.macchiato.com]

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>; "Mark Davis" <mark@macchiato.com>;
"Yves Arrouye" <yves@realnames.com>; <idn@ops.ietf.org>; "Martin Duerst"
<duerst@w3.org>
Sent: Sunday, October 28, 2001 17:48
Subject: Re: [idn] NFC vs NFKC


Hi, Mark and Martin,
Still we have the round-trip conversion problem in
   mapping compat jamo into  conjoining jamo + filler sequence .

 Current UTC standards do not specify how to convert
 conjoining jamo + filler sequence back  into compat jamo which can be 1:1
mapped
 to KS C 5601 isolated jamo for localized rendering platforms.
 Many korean mobile devices and applications supports only KS C 5601.

 For proper rendering of isolated jamos in unicode,
  mapping from conjoining jamo+filler sequence int into compat jamo
  should be defined somewhere in UTC standards.
 That's missing now. Rendering engine vendors have no authoritative
reference for it now.
 Without that,  Mark's suggestion will fail to work  on most korean
  commercial platforms now and even in the forseeable *FUTURE*.

Soobok Lee


----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Mark Davis" <mark@macchiato.com>; "Yves Arrouye" <yves@realnames.com>;
<idn@ops.ietf.org>; "Martin Duerst" <duerst@w3.org>
Sent: Friday, October 26, 2001 2:09 AM
Subject: Re: [idn] NFC vs NFKC


>
> Not bad for future. But as for now, most current rendering platforms (on
windows and unix/linux)
> would fail to support rendering filler sequences and display fillers as
"white spaces".
> That would cause confusions and misinterpretations for a long time until
> all user platforms are upgraded to support fillers.
>
> Soobok Lee
>
> ----- Original Message -----
> From: "Mark Davis" <mark@macchiato.com>
> To: "Soobok Lee" <lsb@postel.co.kr>; "Yves Arrouye" <yves@realnames.com>;
<idn@ops.ietf.org>; "Martin Duerst" <duerst@w3.org>
> Sent: Friday, October 26, 2001 1:46 AM
> Subject: Re: [idn] NFC vs NFKC
>
>
> > Either deletion, prohibition or producing fillers can be accomplished,
if
> > desired, by adding mappings to "D. Mapping Tables" in
> > http://www.ietf.org/internet-drafts/draft-ietf-idn-nameprep-06.txt. And
this
> > is *without* having to change anything else in nameprep. For example,
for
> > U+3131 HANGUL LETTER KIYEOK here are the three options:
> >
> > Deletion:
> > 3131; ; Deletion
> >
> > Prohibition:
> > 3131; 0000; Prohibition
> >
> > Additional folding
> > 3131; 1100 1160; Additional Folding
> >
> > In the last case, the medial filler is added. It is sufficient to do
this
> > only for the initials, since that prevents any syllable formation.
However,
> > if one wanted, the initial filler could be added before medials, such as
for
> > U+314F HANGUL LETTER A below (or initial and final fillers could be
added
> > before finals).
> >
> > Additional folding
> > 314F; 115F 1161; Additional Folding
> >
> > Mark
> >
> > —————
> >
> > Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
> > [http://www.macchiato.com]
> >
> > ----- Original Message -----
> > From: "Soobok Lee" <lsb@postel.co.kr>
> > To: "Yves Arrouye" <yves@realnames.com>; <idn@ops.ietf.org>; "Martin
Duerst"
> > <duerst@w3.org>
> > Sent: Thursday, October 25, 2001 09:04
> > Subject: Re: [idn] NFC vs NFKC
> >
> >
> >
> > ----- Original Message -----
> > From: "Martin Duerst" <duerst@w3.org>
> >  >
> > > Hangul domain names in KS C 5601 would normally be encoded as
> > > precombined syllables. KS C 5601 provides about 2300 of them,
> > > the ones most often used. Users who want to used other Hangul
> > > syllables won't use non-conjoining Jamo (compatibility Jamo),
> > > because they will be displayed one Jamo at a time.
> > >
> > > In the nameprep design team, we discussed some cases where users
> > > might want to use sequences of independent consonant Jamo. There
> > > are a few web pages with some examples of these, but not too many.
> > > We are not sure whether they should be allowed in domain names or
> > > not, and if they are, how they should be represented.
> > >
> >
> > Current windows 98 and above  support only  compatibility Jamo, does
> > not support "conjoining jamo + filler" sequence for isolated jamos
> > which are often found in informal texts/business names.
> > No display and No input method for "conjoining jamo + filler" in
> > windows O/S.
> >
> > Compatiliby Jamo became the defacto standard for isolated jamos
> > inadvertantly and contrary to the intent of ISO Korean representatives
and
> > UTC members.
> >
> > NFKC maps Compatiblity Jamo to conjoining jamos withOUT fillers.
> >
> > Nameprep's positions on NFKC's problematic handling of compat jamos
> > should be clarified. Two alternatives.
> >
> >   1) NFC is used instead
> >   2) NFKC is used but bypass all characters from the compatibility jamo
> > block
> >
> > Soobok Lee
> >
> >
> > >
> > > >[Edit] Is that because nobody uses these anymore, and so you would
not
> > > >expect a modern invention like IDN to appear in an anachronic way? Is
> > that
> > > >the case with all LEGACY characters?
> > >
> > > I don't want IDN to carry unnecessary legacy compatibility
> > > baggage. If it turns out that something really helps the user
> > > (e.g. for the full-width Latin letters), I have nothing against
> > > mapping them. But I don't think it's a good idea to map a
> > > wholesale 3000, most of them not really used and very difficult
> > > to type in, just to get a few dozen mapped the right way.
> > > We can easily do the later without having to do the former.
> > >
> > >
> > > Regards,   Martin.
> > >
> >
> >
>
>






From owner-idn@ops.ietf.org  Sun Oct 28 21:54:56 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18895
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 21:54:55 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y2PE-000AlH-00
	for idn-data@psg.com; Sun, 28 Oct 2001 18:44:04 -0800
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y2PC-000Aku-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 18:44:03 -0800
Received: from deng ([159.226.7.68]) by whale.cnnic.net.cn
          (Netscape Messaging Server 4.15) with SMTP id GLY4ZV00.EYY; Mon,
          29 Oct 2001 10:45:31 +0800 
Message-ID: <008901c16022$74b7c640$4407e29f@deng>
From: "xiang deng" <deng@cnnic.net.cn>
To: <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
Cc: <klensin@jck.com>
References: <E15xrqq-000Adc-00@psg.com>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Mon, 29 Oct 2001 10:36:04 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
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 VAA18895

On Sunday, October 28, 2001 11:27 PM, Martin Duerst wrote:

> > > Do you have any statistic on how many mixed TC/SC registration have
> been
> > > done so far?
> >
> >If there just has 1% or 0.1% , do you mean we can ignore it?
> 
> It could be that we can ignore it, or that we can look for
> lightweight solutions.

If A company register a SC-domain-name, and has a websit about it.
if B company is the challenger of A, he register a mixed TC/SC domain
name, and publish its websit.

Do you think this kind of cases will be minority?

The A company must face the disputation.But there will be 
so many variant domain names, A company will be tired to 
deal with it, Where is the intelligent property of domain name?
Whoes wrong?

Deng xiang
 


From owner-idn@ops.ietf.org  Sun Oct 28 22:03:55 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18936
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 22:03:55 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y2YT-000BH6-00
	for idn-data@psg.com; Sun, 28 Oct 2001 18:53:37 -0800
Received: from smtp15.singnet.com.sg ([165.21.6.35])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y2YR-000BGz-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 18:53:36 -0800
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp15.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9T2oYN01927;
	Mon, 29 Oct 2001 10:50:34 +0800
Message-ID: <00e801c16024$d4ea5260$1e01000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        <jet-member@nic.ad.jp>, <idn@ops.ietf.org>
References: <200110282005.f9SK5mr36403@nic-naa.net>
Subject: Re: [idn] Re: [JET-member 446] Re: Fw: Re: new members invitation 
Date: Mon, 29 Oct 2001 10:53:04 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

You whole long mail basically "scale" (not "economy cost") maybe a
problem we need to look into.

As I said, I agree with you that discussion of "scale" is within
technical scope, but not "economy cost" on how much V charges per name
or B charges per cert etc and how much it would cost C to use it.

-James Seng

----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
<jet-member@nic.ad.jp>; <idn@ops.ietf.org>; <brunner@nic-naa.net>
Sent: Monday, October 29, 2001 4:05 AM
Subject: Re: [idn] Re: [JET-member 446] Re: Fw: Re: new members
invitation


> James,
>
> > I agree with you - "scale" is an engineering consideration.
> > But "cost" (economy), OTOH, is not.
>
> Assume that "registration" of a "name" containing characters in the SC
and/or
> TC character sets with the .FROTZ TLD registry is "free". No VISA
card, no
> wire transfer, postal coupons or micro-payments. Free. Like .US.
>
> Assume also that "dispute resolution" of a "name" containing
characters in
> the SC and/or TC character sets under the Dispute Resolution Policy
(DRP)
> of the .FROTZ TLD registry is "free". No VISA card, no wire transfer,
postal
> coupons or micro-payments. Free. Also like .US, at least in theory.
>
>
> Now that everything in the problem space is zero "cost", and "buy"
means
> only perform whatever non-cash ritual is required by the the .FROTZ
registry
> system (registrars don't charge money either), and "defend" in the
.FROTZ DRP
> means only perform whatever non-cash ritual is required by the .FROTZ
registry
> system (mediators and lawyers don't charge money either), and the
non-cash
> ritual is simply to read and write modest bits of email without the
use of
> any autonoma other than a comodity MUA ...
>
> For a 10 character "name", assuming only 1-to-1 equivalences for all
10 of
> the characters, 2^^10 items of email are required to "register" the
name.
> Another 2^^10 items to "defend" the name. That's about the total
volume of
> email on the IDN list this year (between 1K and 2K seperate mailings,
but
> I'm _not_ counting -- the point is tedium, saturation even boredom).
Even
> if there is no "cost" associated with any action, the
take-to-exhaustion
> "solution" has the effect of limiting the length of character strings
to a
> fraction of whatever scheme is employed to use the 63 bytes available.
>
>
> You had this issue in another WG, where you thought that the
authentication
> mechanism could be, without cost, extended from a end-point set the
size of
> 10^^3 or 10^^4, to an end-point set the size of 10^^6 or 10^^7.
>
> Neither that activity nor this one is theoretical. Cost is not "layer
9",
> if you really think it is, go sit in on variable- vs fixed-length
forwarding
> lookup or any equivalent problem in layers 2 or 3.
>
>
> Now, on the registry side that was 2^^10 blips in the zone file for
each
> name, assume 10^^6 distinct names, each 10 character, plus 2^^10 extra
> equivalences ... that's 10^^9 records. To be equitable, assume I/O,
store,
> and processing are "free", but not instantaneous. Even if there is no
"cost"
> associated with any action, the multiple entries in zone files
recommended
> (the UTC recommendataion) "solution" has the effect of limiting the
length
> of character strings to a fraction of whatever scheme is employed to
use the
> 63 bytes available.
>
> Eric




From owner-idn@ops.ietf.org  Sun Oct 28 22:05:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18947
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 22:05:10 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y2Xt-000BDg-00
	for idn-data@psg.com; Sun, 28 Oct 2001 18:53:01 -0800
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y2Xs-000BDQ-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 18:53:00 -0800
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id LAA23964;
	Mon, 29 Oct 2001 11:52:43 +0900
Message-ID: <009901c16024$e72f4b10$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Mark Davis" <mark@macchiato.com>, "Yves Arrouye" <yves@realnames.com>,
        <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <4.2.0.58.J.20011025182258.036b42e0@localhost> <02f401c15d6e$cca3b0f0$ec1bd9d2@temp> <025201c15d74$937b5ed0$0c680b41@c1340594a> <031e01c15d77$cd0e4380$ec1bd9d2@temp> <008001c1601b$ce7b11c0$ec1bd9d2@temp> <00a901c16023$84bbb320$0c680b41@c1340594a>
Subject: Re: [idn] NFC vs NFKC
Date: Mon, 29 Oct 2001 11:53:35 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id WAA18947


----- Original Message ----- 
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>; "Yves Arrouye" <yves@realnames.com>; <idn@ops.ietf.org>; "Martin Duerst" <duerst@w3.org>
Sent: Monday, October 29, 2001 11:43 AM
Subject: Re: [idn] NFC vs NFKC


> This is not an issue.
> 
> 1. You still have never shown a need for compatibility Jamo. I have
> requested real examples on several occasions, but they never showed up. Even
> more useful would be hard data. In how many of the Korean domain names that
> have been registered in testbeds are compatibility jamo an issue? That is,
> how many cases does a name contains an initial jamo compatibility character
> followed *immediately* by a medial jamo compatibility character?

I will post you the live examples that I sent to Martin 2months ago in
offline nameprep mailling lists. Martin and I  will help you.

> 
> 2. It is a trivial exercise to map sequences of conjoining jamo (with
> filters) back to compatibility jamo in converting Unicode to 5601 (e.g. for
> display in a web browser). If you really want, I'm sure that we can get the
> UTC to have an explicit statement of how to do this in the next version of
> the Unicode Standard, 3.2, due 2002Q1.

Glad to hear that. Thanks.

> 
> Mark
> —————
> 
> Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
> [http://www.macchiato.com]
> 
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: "Soobok Lee" <lsb@postel.co.kr>; "Mark Davis" <mark@macchiato.com>;
> "Yves Arrouye" <yves@realnames.com>; <idn@ops.ietf.org>; "Martin Duerst"
> <duerst@w3.org>
> Sent: Sunday, October 28, 2001 17:48
> Subject: Re: [idn] NFC vs NFKC
> 
> 
> Hi, Mark and Martin,
> Still we have the round-trip conversion problem in
>    mapping compat jamo into  conjoining jamo + filler sequence .
> 
>  Current UTC standards do not specify how to convert
>  conjoining jamo + filler sequence back  into compat jamo which can be 1:1
> mapped
>  to KS C 5601 isolated jamo for localized rendering platforms.
>  Many korean mobile devices and applications supports only KS C 5601.
> 
>  For proper rendering of isolated jamos in unicode,
>   mapping from conjoining jamo+filler sequence int into compat jamo
>   should be defined somewhere in UTC standards.
>  That's missing now. Rendering engine vendors have no authoritative
> reference for it now.
>  Without that,  Mark's suggestion will fail to work  on most korean
>   commercial platforms now and even in the forseeable *FUTURE*.
> 
> Soobok Lee
> 
> 
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: "Mark Davis" <mark@macchiato.com>; "Yves Arrouye" <yves@realnames.com>;
> <idn@ops.ietf.org>; "Martin Duerst" <duerst@w3.org>
> Sent: Friday, October 26, 2001 2:09 AM
> Subject: Re: [idn] NFC vs NFKC
> 
> 
> >
> > Not bad for future. But as for now, most current rendering platforms (on
> windows and unix/linux)
> > would fail to support rendering filler sequences and display fillers as
> "white spaces".
> > That would cause confusions and misinterpretations for a long time until
> > all user platforms are upgraded to support fillers.
> >
> > Soobok Lee
> >
> > ----- Original Message -----
> > From: "Mark Davis" <mark@macchiato.com>
> > To: "Soobok Lee" <lsb@postel.co.kr>; "Yves Arrouye" <yves@realnames.com>;
> <idn@ops.ietf.org>; "Martin Duerst" <duerst@w3.org>
> > Sent: Friday, October 26, 2001 1:46 AM
> > Subject: Re: [idn] NFC vs NFKC
> >
> >
> > > Either deletion, prohibition or producing fillers can be accomplished,
> if
> > > desired, by adding mappings to "D. Mapping Tables" in
> > > http://www.ietf.org/internet-drafts/draft-ietf-idn-nameprep-06.txt. And
> this
> > > is *without* having to change anything else in nameprep. For example,
> for
> > > U+3131 HANGUL LETTER KIYEOK here are the three options:
> > >
> > > Deletion:
> > > 3131; ; Deletion
> > >
> > > Prohibition:
> > > 3131; 0000; Prohibition
> > >
> > > Additional folding
> > > 3131; 1100 1160; Additional Folding
> > >
> > > In the last case, the medial filler is added. It is sufficient to do
> this
> > > only for the initials, since that prevents any syllable formation.
> However,
> > > if one wanted, the initial filler could be added before medials, such as
> for
> > > U+314F HANGUL LETTER A below (or initial and final fillers could be
> added
> > > before finals).
> > >
> > > Additional folding
> > > 314F; 115F 1161; Additional Folding
> > >
> > > Mark
> > >
> > > —————
> > >
> > > Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
> > > [http://www.macchiato.com]
> > >
> > > ----- Original Message -----
> > > From: "Soobok Lee" <lsb@postel.co.kr>
> > > To: "Yves Arrouye" <yves@realnames.com>; <idn@ops.ietf.org>; "Martin
> Duerst"
> > > <duerst@w3.org>
> > > Sent: Thursday, October 25, 2001 09:04
> > > Subject: Re: [idn] NFC vs NFKC
> > >
> > >
> > >
> > > ----- Original Message -----
> > > From: "Martin Duerst" <duerst@w3.org>
> > >  >
> > > > Hangul domain names in KS C 5601 would normally be encoded as
> > > > precombined syllables. KS C 5601 provides about 2300 of them,
> > > > the ones most often used. Users who want to used other Hangul
> > > > syllables won't use non-conjoining Jamo (compatibility Jamo),
> > > > because they will be displayed one Jamo at a time.
> > > >
> > > > In the nameprep design team, we discussed some cases where users
> > > > might want to use sequences of independent consonant Jamo. There
> > > > are a few web pages with some examples of these, but not too many.
> > > > We are not sure whether they should be allowed in domain names or
> > > > not, and if they are, how they should be represented.
> > > >
> > >
> > > Current windows 98 and above  support only  compatibility Jamo, does
> > > not support "conjoining jamo + filler" sequence for isolated jamos
> > > which are often found in informal texts/business names.
> > > No display and No input method for "conjoining jamo + filler" in
> > > windows O/S.
> > >
> > > Compatiliby Jamo became the defacto standard for isolated jamos
> > > inadvertantly and contrary to the intent of ISO Korean representatives
> and
> > > UTC members.
> > >
> > > NFKC maps Compatiblity Jamo to conjoining jamos withOUT fillers.
> > >
> > > Nameprep's positions on NFKC's problematic handling of compat jamos
> > > should be clarified. Two alternatives.
> > >
> > >   1) NFC is used instead
> > >   2) NFKC is used but bypass all characters from the compatibility jamo
> > > block
> > >
> > > Soobok Lee
> > >
> > >
> > > >
> > > > >[Edit] Is that because nobody uses these anymore, and so you would
> not
> > > > >expect a modern invention like IDN to appear in an anachronic way? Is
> > > that
> > > > >the case with all LEGACY characters?
> > > >
> > > > I don't want IDN to carry unnecessary legacy compatibility
> > > > baggage. If it turns out that something really helps the user
> > > > (e.g. for the full-width Latin letters), I have nothing against
> > > > mapping them. But I don't think it's a good idea to map a
> > > > wholesale 3000, most of them not really used and very difficult
> > > > to type in, just to get a few dozen mapped the right way.
> > > > We can easily do the later without having to do the former.
> > > >
> > > >
> > > > Regards,   Martin.
> > > >
> > >
> > >
> >
> >
> 
> 
> 




From owner-idn@ops.ietf.org  Sun Oct 28 22:32:25 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20137
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 22:32:25 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y305-000Ca4-00
	for idn-data@psg.com; Sun, 28 Oct 2001 19:22:09 -0800
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y304-000CZj-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 19:22:08 -0800
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9T3Nor46127;
	Sun, 28 Oct 2001 22:23:52 -0500 (EST)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110290323.f9T3Nor46127@nic-naa.net>
X-Mailer: exmh version 1.6.9 8/22/96
To: "James Seng/Personal" <jseng@pobox.org.sg>
cc: jet-member@nic.ad.jp, idn@ops.ietf.org
Subject: Re: [idn] Re: [JET-member 446] Re: Fw: Re: new members invitation 
In-Reply-To: Your message of "Mon, 29 Oct 2001 10:53:04 +0800."
             <00e801c16024$d4ea5260$1e01000a@jamessonyvaio> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 28 Oct 2001 22:23:50 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk


Now I am confused. Deng, L.M. Tseng, and I write about scaling. You reply
that engineering isn't about "cost", then something about "economy cost".

What is "economy cost"?

Please clarify. 





From owner-idn@ops.ietf.org  Sun Oct 28 22:34:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20149
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 22:34:36 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y315-000Cd1-00
	for idn-data@psg.com; Sun, 28 Oct 2001 19:23:11 -0800
Received: from gate.sinica.edu.tw ([140.109.4.130])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y314-000Cch-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 19:23:10 -0800
Received: from itsnb (itsnb.iis.sinica.edu.tw [140.109.23.115])
	by gate.sinica.edu.tw (8.11.3/8.11.3) with SMTP id f9T3N9J18558
	for <idn@ops.ietf.org>; Mon, 29 Oct 2001 11:23:09 +0800 (CST)
Message-ID: <002b01c16029$0c19af20$73176d8c@itsnb>
From: "Chun-Hsin Wu" <wuch@gate.sinica.edu.tw>
To: <idn@ops.ietf.org>
References: <3CD14E451751BD42BA48AAA50B07BAD6C5FBCE@vsvapostal3.prod.netsol.com>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Mon, 29 Oct 2001 11:23:10 +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.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > For full-name DNS, White House may need to register at least
> > three records:
> >     "America"."USA"
> >     "United States"."USA"
> >     "USA"."USA"
> > If they forget to register "United States of America"."USA",
> > some other one may register it validly. This may imply that
> > every IDN customer must know and register all combinations
> > of the domain name he wants to register.
>
> This situation isn't unique to IDNs.  I can register foobar.com, and
someone
> else can register foo-bar.com if I don't.  I have to make a conscious
> decision to register the name forms that are important to me.  Why should
> IDNs be treated differently?

As the comment of James, domain names are identifiers, not names.
I'm sorry to mislead you into this situation in the above analogy.

As you might know, Chinese is an open-set character-based language.
I think the case is not similar to foobar.com and foo-bar.com; it's
more similar to 'A' and 'a', but this 'Aa' analogy still can not precisely
explain the case. I'm sorry I'm not a language expert to descibe this
issue exactly and completely. Hope I won't mislead you once.

Regards,

Chun-Hsin Wu








From owner-idn@ops.ietf.org  Sun Oct 28 22:37:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20179
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 22:37:46 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y35t-000CrF-00
	for idn-data@psg.com; Sun, 28 Oct 2001 19:28:09 -0800
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y35s-000Cr3-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 19:28:08 -0800
Received: from jackie.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 TAA09085;
	Sun, 28 Oct 2001 19:27:37 -0800
Message-Id: <5.1.0.14.2.20011028191806.03cd6468@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 28 Oct 2001 19:27:22 -0800
To: "Eric A. Hall" <ehall@ehsco.com>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] iDNS re-chartering proposal, take 2
Cc: idn@ops.ietf.org
In-Reply-To: <3BDC9979.1EA641A4@ehsco.com>
References: <5.1.0.14.2.20011027084819.03d3b6c0@brandenburg.com>
 <5.1.0.14.2.20011028145534.03d1f008@dcrocker.net>
 <5.1.0.14.2.20011028152132.01c501c0@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 05:49 PM 10/28/2001 -0600, Eric A. Hall wrote:
>Dave Crocker wrote:
> > Ahh.  I see.  You have a complaint about working group process.
>
>No, I have an issue with agenda railroading. I feel no need to run for
>mommy's skirts when things don't go my way, however.

Perhaps you see something constructive in plaintive and inflammatory 
language on an engineering discussion list.  However it is not, especially 
absent any specific, constructive engineering content.


> > Please review the last 11 years of IETF history, in particular the
> > results of its trying to support multiple "complementary" (but actually
> > competing) specifications, versus the results of choosing a single
> > specification.
>
>SMTP, IMAP, NNTP are complementary. RIP, OSPF and BGP work well together
>when needed. HTTP and FTP aren't burning each other down. Golly, it almost
>seems like complementary is the norm.


Hmmm.  Yes.  Whereas ACE and Raw UTF-8 DNS are most certainly NOT 
complementary.  They are competitive.  They both try to solve the same 
problem, albeit differently.


>Protocols which comply with BCP18 will use UTF-8 for all protocol data
>_except_ domain names, where they will require ACE.

Yes.  As with pretty much all existing protocols.  You need to distinguish 
between starting a new protocol, versus making changes to an existing one.


>  Going with ACE-only directly equates to two mandatory encodings. This is 
> an incredibly high
>cost to lay on the Internet

Thank you for that economic assessment.  As has been pointed out, however, 
it is not valid.

Please refer to the many earlier discussions about the relative cost -- or 
rather lack of it -- for ACE, particularly given the remarkably short 
string length for Domain Names.

However, it is nice to see that you agree that UTF-8 is also an 
encoding.  As such, the relative difference in cost, between an ACE and 
UTF-8, is negligible.


>  for the sole purpose of backwards compatibility

Indeed.  Very shallow thinking.  Why would anyone want to spend effort 
being compatible with an installed base of many millions of systems?  Can't 
imagine...

Unfortunately, Eric, this has now devolved into a tutorial on first 
principals of Internet protocol engineering.  It is unfortunate because an 
IETF working group is primarily for doing engineering, rather than 
instructing participants on the basics.  No doubt other venues are more 
appropriate for extended, basic pedagogy.

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 Oct 28 22:39:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20197
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 22:39:51 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y37o-000Cww-00
	for idn-data@psg.com; Sun, 28 Oct 2001 19:30:08 -0800
Received: from smtp14.singnet.com.sg ([165.21.6.34])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y37m-000CwW-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 19:30:07 -0800
Received: from jamessonyvaio (bb104-8.singnet.com.sg [165.21.104.8])
	by smtp14.singnet.com.sg (8.11.6/8.11.6) with SMTP id f9T3SFw05516;
	Mon, 29 Oct 2001 11:28:15 +0800
Message-ID: <015001c16029$fbcb39d0$1e01000a@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <jet-member@nic.ad.jp>
Cc: <jet-member@nic.ad.jp>, <idn@ops.ietf.org>
References: <200110290323.f9T3Nor46127@nic-naa.net>
Subject: [idn] Re: [JET-member 464] Re: Fw: Re: new members invitation 
Date: Mon, 29 Oct 2001 11:29:57 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

You are confusing me too. So let me put it in another way.

There are many different kind of 'cost'. 'scaling cost' like what you
described and 'economy cost' like what deng/tseng.

I am saying 'scaling cost' is an engineering considering, but not
'economy cost'.

Is this better?

-James Seng

----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
Cc: <jet-member@nic.ad.jp>; <idn@ops.ietf.org>
Sent: Monday, October 29, 2001 11:23 AM
Subject: [JET-member 464] Re: Fw: Re: new members invitation


>
> Now I am confused. Deng, L.M. Tseng, and I write about scaling. You
reply
> that engineering isn't about "cost", then something about "economy
cost".
>
> What is "economy cost"?
>
> Please clarify.
>
>




From owner-idn@ops.ietf.org  Sun Oct 28 23:20:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20393
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 23:20:45 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y3dg-000EQ1-00
	for idn-data@psg.com; Sun, 28 Oct 2001 20:03:04 -0800
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y3df-000EPh-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 20:03:03 -0800
Received: from [165.227.249.20] (165-227-249-18.client.dsl.net [165.227.249.18])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f9T42p829520;
	Sun, 28 Oct 2001 20:02:51 -0800 (PST)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0510100db8027d203d26@[165.227.249.20]>
In-Reply-To: <008901c16022$74b7c640$4407e29f@deng>
References: <E15xrqq-000Adc-00@psg.com>
 <008901c16022$74b7c640$4407e29f@deng>
Date: Sun, 28 Oct 2001 19:30:04 -0800
To: "xiang deng" <deng@cnnic.net.cn>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] An ignorant question about TC<-> SC
Cc: <klensin@jck.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 10:36 AM +0800 10/29/01, xiang deng wrote:
>On Sunday, October 28, 2001 11:27 PM, Martin Duerst wrote:
>
>>  > > Do you have any statistic on how many mixed TC/SC registration have
>>  been
>>  > > done so far?
>>  >
>>  >If there just has 1% or 0.1% , do you mean we can ignore it?
>>
>>  It could be that we can ignore it, or that we can look for
>>  lightweight solutions.
>
>If A company register a SC-domain-name, and has a websit about it.
>if B company is the challenger of A, he register a mixed TC/SC domain
>name, and publish its websit.
>
>Do you think this kind of cases will be minority?

Yes, and it happens all the time with the current ASCII-only names. 
The traditional-simplified mappings will cause more of the same thing 
we see now.

>The A company must face the disputation.But there will be
>so many variant domain names, A company will be tired to
>deal with it, Where is the intelligent property of domain name?
>Whoes wrong?

No one. That's the point. There is no technical means for determining 
all of the names that are similar for a particular audience. There 
are certainly non-technical human means for determining those names, 
and we currently use non-technical human means for dealing with the 
problems.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Sun Oct 28 23:40:54 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20908
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 23:40:54 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y42q-000Fcy-00
	for idn-data@psg.com; Sun, 28 Oct 2001 20:29:04 -0800
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y42n-000Fcf-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 20:29:02 -0800
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9T4U0r59326;
	Sun, 28 Oct 2001 23:30:01 -0500 (EST)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110290430.f9T4U0r59326@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
cc: jet-member@nic.ad.jp, idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Re: [JET-member 464] Re: Fw: Re: new members invitation 
In-Reply-To: Your message of "Mon, 29 Oct 2001 11:29:57 +0800."
             <015001c16029$fbcb39d0$1e01000a@jamessonyvaio> 
Date: Sun, 28 Oct 2001 23:30:00 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Is this better?

Nope.

You brought up "how much V charges per name or B charges per cert etc and
 how much it would cost C to use it".

I don't think these are relevant, and as your reply to LM Tseng was:
  > But the arguments for inclusive of TC/SC or not should be done on a pure
  > technical evaluation basis in IETF. Economy arguments as above is not a
  > factor for consideration.
it appears that you characterizing a fundamental scaling property of any
sequence of binary-valued tokens -- the 2^^N problem, as non-technical. You
also wrote:
  > This is considered Layer 9 aka `political' issues from IETF perspective..

I don't agree.

It doesn't change the scaling property to associate Verisign price points
or bits of colored glass to the required user- and registry-acts and the
stored state required for each if TC/SC isn't included.

Eric



From owner-idn@ops.ietf.org  Sun Oct 28 23:43:00 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20925
	for <idn-archive@lists.ietf.org>; Sun, 28 Oct 2001 23:43:00 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y46A-000FnE-00
	for idn-data@psg.com; Sun, 28 Oct 2001 20:32:30 -0800
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y469-000Fn8-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 20:32:30 -0800
Received: from deng ([159.226.7.68]) by whale.cnnic.net.cn
          (Netscape Messaging Server 4.15) with SMTP id GLYA0M00.Q0W; Mon,
          29 Oct 2001 12:33:58 +0800 
Message-ID: <012101c16031$9bbd4120$4407e29f@deng>
From: "xiang deng" <deng@cnnic.net.cn>
To: <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>,
        "Paul Hoffman / IMC" <phoffman@imc.org>
Cc: <klensin@jck.com>
References: <E15xrqq-000Adc-00@psg.com><008901c16022$74b7c640$4407e29f@deng> <p0510100db8027d203d26@[165.227.249.20]>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Mon, 29 Oct 2001 12:24:32 +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 XAA20925


On Monday, October 29, 2001 11:30 AM, Paul Hoffman / IMC wrote:

> >The A company must face the disputation.But there will be
> >so many variant domain names, A company will be tired to
> >deal with it, Where is the intelligent property of domain name?
> >Whoes wrong?
> 
> No one. That's the point. There is no technical means for determining 
> all of the names that are similar for a particular audience. There 
> are certainly non-technical human means for determining those names, 
> and we currently use non-technical human means for dealing with the 
> problems.

Yes, if there is non-technical solution which is really available and applicable.
why not?

And, there isn't a total technical solution about it. But we still can do 
something which will help to limit the scope of influence and which
will be limit in techical scope.

Deng xiang


From owner-idn@ops.ietf.org  Mon Oct 29 00:39:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21260
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 00:39:04 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y4x6-000Hgm-00
	for idn-data@psg.com; Sun, 28 Oct 2001 21:27:12 -0800
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y4x5-000Hgg-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 21:27:11 -0800
Received: from [165.227.249.18] (165-227-249-18.client.dsl.net [165.227.249.18])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f9T5R6801213
	for <idn@ops.ietf.org>; Sun, 28 Oct 2001 21:27:06 -0800 (PST)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05101000b80297d251e6@[165.227.249.18]>
In-Reply-To: <012101c16031$9bbd4120$4407e29f@deng>
References: 
 <E15xrqq-000Adc-00@psg.com><008901c16022$74b7c640$4407e29f@deng>
 <p0510100db8027d203d26@[165.227.249.20]>
 <012101c16031$9bbd4120$4407e29f@deng>
Date: Sun, 28 Oct 2001 21:27:05 -0800
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] An ignorant question about TC<-> SC
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 12:24 PM +0800 10/29/01, xiang deng wrote:
>On Monday, October 29, 2001 11:30 AM, Paul Hoffman / IMC wrote:
>
>>  >The A company must face the disputation.But there will be
>>  >so many variant domain names, A company will be tired to
>>  >deal with it, Where is the intelligent property of domain name?
>>  >Whoes wrong?
>>
>>  No one. That's the point. There is no technical means for determining
>>  all of the names that are similar for a particular audience. There
>>  are certainly non-technical human means for determining those names,
>>  and we currently use non-technical human means for dealing with the
>>  problems.
>
>Yes, if there is non-technical solution which is really available 
>and applicable.
>why not?

Why not, indeed? No one here is saying that it should not be done. We 
are saying that it should not be mandated in a technical 
specification. There are many types of non-technical specifications 
that would be very useful here. We have been told that the JET group 
is coming out with one Real Soon Now, so that might address the 
problem in a suitable fashion.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Mon Oct 29 00:59:54 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21330
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 00:59:53 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y5F4-000IAW-00
	for idn-data@psg.com; Sun, 28 Oct 2001 21:45:46 -0800
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y5F3-000IAO-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 21:45:45 -0800
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 GAA23173;
	Mon, 29 Oct 2001 06:45:28 +0100 (MET)
Date: Mon, 29 Oct 2001 06:30:22 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: "Paul Hoffman / IMC" <phoffman@imc.org>, xiang deng <deng@cnnic.net.cn>,
        idn@ops.ietf.org, Martin Duerst <duerst@w3.org>
cc: klensin@jck.com
Subject: Re: [idn] An ignorant question about TC<-> SC
Message-ID: <1180657.1004337022@localhost>
In-Reply-To: <p0510100db8027d203d26@[165.227.249.20]>
References: <E15xrqq-000Adc-00@psg.com><008901c16022$74b7c640$4407e29f@deng>
 <p0510100db8027d203d26@[165.227.249.20]>
X-Mailer: Mulberry/2.1.1 (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-10-28 19.30 -0800 "Paul Hoffman / IMC" <phoffman@imc.org> wrote:

>> The A company must face the disputation.But there will be
>> so many variant domain names, A company will be tired to
>> deal with it, Where is the intelligent property of domain name?
>> Whoes wrong?
> 
> No one. That's the point. There is no technical means for determining all
> of the names that are similar for a particular audience. There are
> certainly non-technical human means for determining those names, and we
> currently use non-technical human means for dealing with the problems.

Paul is completely correct. The important thing is to have one well-defined
set of rules for "equality". Given these rules, three things can happen:

  - A registry can create well-defined rules for what can be requested
    to be registered
  - A registry can create well-defined rules for what goes into the
    DNS zonefile given a registration request
  - The dispute resolution process for a specific domain can define
    their rules, and come up with their own practice for decision making

What is NOT acceptable is to have rules which doesn't settle down, changes
all the time etc.

Just like Paul I see too many players trying to come up with engineering
solutions to real world problems which have to do with "matching of words"
and not "matching of identifiers" which DNS is about.

      paf




From owner-idn@ops.ietf.org  Mon Oct 29 02:45:18 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06892
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 02:45:17 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y6sl-000KfG-00
	for idn-data@psg.com; Sun, 28 Oct 2001 23:30:51 -0800
Received: from twnic.net.tw ([211.72.210.250])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y6sk-000Kez-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 23:30:50 -0800
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 PAA08582;
	Mon, 29 Oct 2001 15:30:13 +0800
Message-ID: <3BDD0A4B.191D276E@twnic.net.tw>
Date: Mon, 29 Oct 2001 15:50:35 +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: Paul Hoffman / IMC <phoffman@imc.org>
CC: xiang deng <deng@cnnic.net.cn>, idn@ops.ietf.org,
        Martin Duerst <duerst@w3.org>, klensin@jck.com
Subject: Re: [idn] An ignorant question about TC<-> SC
References: <E15xrqq-000Adc-00@psg.com>
	 <008901c16022$74b7c640$4407e29f@deng> <p0510100db8027d203d26@[165.227.249.20]>
Content-Type: text/plain; charset=big5
Content-Transfer-Encoding: 8bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Paul Hoffman / IMC ¼g¤J¡G

> At 10:36 AM +0800 10/29/01, xiang deng wrote:
> >On Sunday, October 28, 2001 11:27 PM, Martin Duerst wrote:
> >
> >>  > > Do you have any statistic on how many mixed TC/SC registration have
> >>  been
> >>  > > done so far?
> >>  >
> >>  >If there just has 1% or 0.1% , do you mean we can ignore it?
> >>
> >>  It could be that we can ignore it, or that we can look for
> >>  lightweight solutions.
> >
> >If A company register a SC-domain-name, and has a websit about it.
> >if B company is the challenger of A, he register a mixed TC/SC domain
> >name, and publish its websit.
> >
> >Do you think this kind of cases will be minority?
>
> Yes, and it happens all the time with the current ASCII-only names.
> The traditional-simplified mappings will cause more of the same thing
> we see now.
>
> >The A company must face the disputation.But there will be
> >so many variant domain names, A company will be tired to
> >deal with it, Where is the intelligent property of domain name?
> >Whoes wrong?
>
> No one. That's the point. There is no technical means for determining
> all of the names that are similar for a particular audience.

If we consider TC/SC are not the names similar but just like
Uppercase/Lowercase English letter. But we do not want TC/SC
to be folding to one side.
User can use all TC(Uppercase) or all SC(Lowercase) or mixed
TC/SC(Uppercase/Lowercase) as they presumed. And we need the DNS
treat TC/SC(Uppercase/Lowercase) as the same when compare with
cache RR.

> There
> are certainly non-technical human means for determining those names,
> and we currently use non-technical human means for dealing with the
> problems.

If you think of TC/SC requirement is non-technical human means,
then hou about Uppercase/Lowercase English letter deal in DNS?

>  
> --Paul Hoffman, Director
> --Internet Mail Consortium

Erin Chen
 




From owner-idn@ops.ietf.org  Mon Oct 29 02:47:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06904
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 02:47:07 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y6u4-000Khp-00
	for idn-data@psg.com; Sun, 28 Oct 2001 23:32:12 -0800
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y6tx-000Kgj-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 23:32:07 -0800
Received: from test12345 ([140.115.6.240])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f9T7cjV05355;
	Mon, 29 Oct 2001 15:38:45 +0800 (CST)
Message-ID: <001101c1604b$0a2b2d20$f006738c@ncu.edu.tw>
From: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: <jet-member@nic.ad.jp>, <idn@ops.ietf.org>,
        "Paul Hoffman / IMC" <phoffman@imc.org>
References:  <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp><01c801c15 c3d$d9a7ae50$4407e29f@deng> <20011024130954A.yone@nic.ad.jp> <024101c15c42$372e1b50$4407e29f@deng> <007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio> <003f01c15f5c$1d4e5f70$ec1bd9d2@temp> <001101c15f64$7eb3b780$1c01000a@jamessonyvaio> <016601c15f7d$14325c40$ec1bd9d2@temp> <005501c15f80$9dd52a10$1c01000a@jamessonyvaio> <000d01c15f81$5573d900$ec1bd9d2@temp> <006301c15f82$da0cbe60$1c01000a@jamessonyvaio> <001e01c15fae$010900c0$f006738c@ncu.edu.tw> <p05101003b801e8c9a90b@[165.227.249.20]>
Subject: Re: [idn] Re: [JET-member 443] Re: Fw: Re: new members invitation
Date: Mon, 29 Oct 2001 15:26:34 +0800
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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Paul Hoffman / IMC"
> =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= wrote:
> >              If an Engineering Requirement is not related to the user's
cost
> >and what are user need that must be a very interest projects.
>
> There is no inherent cost to multiple registrations. All registration
> cost is assigned by the registry (and, in some models, by the
> registry's agents, the registrars). A registry can have a policy that
> "if many names have identical meanings, all those names are
> registered for the same fee as a single name". It is up to the
> registry to decide what "identical" and "meanings" is, of course. For
> every language, there are different guidelines for those two words;
> it would be good to have some common advice on various languages.
>
         I think  the cost assigned by the registry is the service charge.
it is not the inherent cost of multiple registrations of TC/SC name.
Charging can be reduced to zero by policy but the overhead or
non-effectiveness in technologies is inherent cost in the method or approach
, it is always evaluated and based them to improve or to  make decision.
         Some user register one domain name and setup a DNS to extend his
domain service for organizations' host name. To handle the multiple TC/SC
name registry is an overhead to treat them, the size of storage and the time
for careful treatment is an inherent cost of  complexity. The complexity
come from a neglection to reduce them in a proper level .  That complexity
and cost will let the system manager try to not provide TC/SC multple
records in his managed zone file, then the stability and trust to use CJK
domain name will be very low. Finally , it come back to reflect it is not a
workable approach.
> >   I think many
> >members in IDN WG of IETF also like to know the detail .
>
> Yes, exactly. This discussion has elicited a lot of detail that was
> unknown to many people before now.
>
> >   You give me a very
> >strange impression of IETF.  Can someone in IETF can help more ?
>
> If you listen to just one person's description of the IETF, you are
> sure to get a skewed picture. If you listen to many peoples'
> descriptions, you can weight and combine them yourself. The IETF is
> an extremely open organization. The mailing lists of all the WGs are
> freely available. And everyone has an email address at which you can
> contact them. :-)
>
> --Paul Hoffman, Director
> --Internet Mail Consortium
>
         Thanks your good suggestion.
L.M.Tseng




From owner-idn@ops.ietf.org  Mon Oct 29 03:02:50 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07069
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 03:02:50 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y7DO-000LCq-00
	for idn-data@psg.com; Sun, 28 Oct 2001 23:52:10 -0800
Received: from [211.254.82.194] (helo=nexus.spsoft.co.kr)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y7DM-000LBi-00
	for idn@ops.ietf.org; Sun, 28 Oct 2001 23:52:08 -0800
Received: (from newcat@localhost)
	by nexus.spsoft.co.kr (8.10.0/8.10.0) id f9T7pxo14111
	for idn@ops.ietf.org; Mon, 29 Oct 2001 16:51:59 +0900
Date: Mon, 29 Oct 2001 16:51:59 +0900
From: YangWoo Ko <newcat@spsoft.co.kr>
To: idn@ops.ietf.org
Subject: Re: [idn] Need a new working group?
Message-ID: <20011029165159.G10473@spsoft.co.kr>
References: <3BDBD6B1.DDA9BBB0@trab.se> <001401c15fa6$17d43e80$1c01000a@jamessonyvaio>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <001401c15fa6$17d43e80$1c01000a@jamessonyvaio>; from jseng@pobox.org.sg on Sun, Oct 28, 2001 at 07:45:45PM +0800
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Sun, Oct 28, 2001 at 07:45:45PM +0800, James Seng/Personal wrote:
> > Group two: Internationalisation of DNS.
> 
> There is a group for DNS. It is known as DNSEXT.

I am sorry but I have not followed up DNSEXT WG. Is DNSEXT WG currently 
dealing with this issue ? If no, what should I do for them to do it ?

-- 
/*------------------------------------------------
YangWoo Ko : newcat@spsoft.co.kr
We Invent Enterprise Software Solutions
and Make You Secure & Powerful.
------------------------------------------------*/



From owner-idn@ops.ietf.org  Mon Oct 29 04:07:12 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07661
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 04:07:12 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y85o-000Mqx-00
	for idn-data@psg.com; Mon, 29 Oct 2001 00:48:24 -0800
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y85n-000Mqp-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 00:48:24 -0800
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 222BBFFC09; Mon, 29 Oct 2001 16:48:28 +0800 (SGT)
Message-ID: <005301c16056$712d4250$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <jet-member@nic.ad.jp>
Cc: <jet-member@nic.ad.jp>, <idn@ops.ietf.org>, <brunner@nic-naa.net>
References: <200110290430.f9T4U0r59326@nic-naa.net>
Subject: [idn] Re: [JET-member 469] Re: Fw: Re: new members invitation 
Date: Mon, 29 Oct 2001 16:48:05 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > Is this better?
>
> Nope.
>
> You brought up "how much V charges per name or B charges per cert etc
and
>  how much it would cost C to use it".
>
> I don't think these are relevant, and as your reply to LM Tseng was:

Please dont misrepresent me. I bought that up to say it is not relevant
which you say so too.

-James Seng




From owner-idn@ops.ietf.org  Mon Oct 29 04:29:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07827
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 04:29:44 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y8Xf-000Ni0-00
	for idn-data@psg.com; Mon, 29 Oct 2001 01:17:11 -0800
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y8Xe-000Nhj-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 01:17:10 -0800
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 204752; Sun, 28 Oct 2001 03:17:03 -0600
Message-ID: <3BDD1E94.62F82A5F@ehsco.com>
Date: Mon, 29 Oct 2001 03:17:08 -0600
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dave Crocker <dhc@dcrocker.net>
CC: idn@ops.ietf.org
Subject: Re: [idn] iDNS re-chartering proposal, take 2
References: <5.1.0.14.2.20011027084819.03d3b6c0@brandenburg.com>
	 <5.1.0.14.2.20011028145534.03d1f008@dcrocker.net>
	 <5.1.0.14.2.20011028152132.01c501c0@dcrocker.net> <5.1.0.14.2.20011028191806.03cd6468@dcrocker.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Dave Crocker wrote:

> >  Going with ACE-only directly equates to two mandatory encodings.
> > This is an incredibly high cost to lay on the Internet
> 
> Thank you for that economic assessment.  As has been pointed out,
> however, it is not valid.

This is an outrageous assertion. It is not possible for two encodings to
be as efficient for the community as a single shared encoding. Using the
same encoding for DNS as is used for the protocol, the document formats,
the application I/O and the underlying operating system is the maximum
possible efficiency for the Internet commmunity as a whole. Conversely,
introducing an entirely separate mandatory encoding that has no tools, no
history, no experience and no users, is the antithesis of operational
efficiency. Claiming as much is unbelievable. I'm astounded by this.

> However, it is nice to see that you agree that UTF-8 is also an
> encoding.  As such, the relative difference in cost, between an ACE and
> UTF-8, is negligible.

Negligible? Does the phrase "you are right, ACE costs more to implement"
stick in your throat or something?

I have said several times quite clearly that ACE is necessary as a
backwards compatibility mode for legacy applications. Where we part is
that you also believe that this second mandatory untested encoding that is
jammed into a transliteration layer for every existing and future
application is the ultimate in practical design. Just admit that it has
problems which can be addressed by an optimized form with a different set
of priorities. Come on, just say it!

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



From owner-idn@ops.ietf.org  Mon Oct 29 04:30:30 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07844
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 04:30:29 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y8SH-000NQd-00
	for idn-data@psg.com; Mon, 29 Oct 2001 01:11:37 -0800
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y8S6-000NQT-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 01:11:30 -0800
Received: from test12345 ([140.115.6.240])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f9T9GWV23964;
	Mon, 29 Oct 2001 17:16:32 +0800 (CST)
Message-ID: <006701c16058$b2cc3340$f006738c@ncu.edu.tw>
From: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@cisco.com>,
        "Paul Hoffman / IMC" <phoffman@imc.org>,
        "xiang deng" <deng@cnnic.net.cn>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
Cc: <klensin@jck.com>
References: <E15xrqq-000Adc-00@psg.com><008901c16022$74b7c640$4407e29f@deng> <p0510100db8027d203d26@[165.227.249.20]> <1180657.1004337022@localhost>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Mon, 29 Oct 2001 17:04:20 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi ! Patrik Fältström :
----- Original Message -----
From: "Patrik Fältström" <paf@cisco.com>
>
> Paul is completely correct. The important thing is to have one
well-defined
> set of rules for "equality". Given these rules, three things can happen:
>
>   - A registry can create well-defined rules for what can be requested
>     to be registered
>   - A registry can create well-defined rules for what goes into the
>     DNS zonefile given a registration request
>   - The dispute resolution process for a specific domain can define
>     their rules, and come up with their own practice for decision making
>
> What is NOT acceptable is to have rules which doesn't settle down, changes
> all the time etc.
>
        Right , the PRC-only-SC is derived by some fixed rule and keep more
than 40 years.
> Just like Paul I see too many players trying to come up with engineering
> solutions to real world problems which have to do with "matching of words"
> and not "matching of identifiers" which DNS is about.
>
>       paf
>
            The terminology "word" is very easy confused between chinese
speaking and non-chinese speaking people. The "chinese word"  may be
presented as multiple Han character phrase and single Han character. 1-n
mapping is based on phrase , so it is content sensitive. But the 1-1 mapping
, especially the PRC-only-SC  that is derived from TC based on quick-written
form , that are characters with the same phonic and can be replaced each
other in character position of word phrase or word. The basic unit in CJK
code point is a single-character , it is also a single-character-word with
some meanning.  An identifier is just a string of symbol , the character
symbol in CJK has inherent meanning in each character, "a" "b" "c" have no
explicit meanning in each characters ,  but  CJK characters have , the
combination of them means the combination of meanning with each character's
meaning. That is why the identifier of CJK characters have more information
density in them. Even the characters has individual meanning , you can not
forget it is only a character in a string of identifier.
           1-1 mappimg TC/SC characters can be direct replaced each other,
but they are not presented in each area by the forbidden native code
encoding. The UNICODE based character input and display like win2000 has
break the separation  barrier . Now, the mixing of TC/SC is more like the
case of ASCII character.
           Matching with word is not the work of  layer 1 DNS , but
matching with identifier is . Even the identifier is composed by CJK
single-character-word , it is an indentifier and the 1-1 mapping TC/SC is
the script characters  too. The single chinese character has inherent
meanning like a word .  But  the IDN chinese identifier is composed by these
single character word , you can not forget the fact CJK character is a
character. 1-1 mapping of TC/SC is not to do the conversion of whole phrase
meanning. It only try to reduce the complexity of  combination in
pair-replacable-characters but with the restriction to dispay them in user
favor fom.

L.M.Tseng




From owner-idn@ops.ietf.org  Mon Oct 29 04:42:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07918
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 04:42:39 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y8hk-000NxW-00
	for idn-data@psg.com; Mon, 29 Oct 2001 01:27:36 -0800
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y8hj-000NxQ-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 01:27:36 -0800
Received: from deng ([159.226.7.68]) by whale.cnnic.net.cn
          (Netscape Messaging Server 4.15) with SMTP id GLYNOF00.G4I; Mon,
          29 Oct 2001 17:29:03 +0800 
Message-ID: <003101c1605a$d64df180$4407e29f@deng>
From: "xiang deng" <deng@cnnic.net.cn>
To: "ben" <ben@cc-www.com>, <DougEwell2@cs.com>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>,
        =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@cisco.com>,
        =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
Cc: "John C Klensin" <klensin@jck.com>
References: <166.2ea4bac.290ad741@cs.com><00b001c15e3e$1e64f280$cd462b18@mtag1.on.home.com><497812.1004124760@localhost><007101c15e8e$cc0919c0$f006738c@ncu.edu.tw><3399691.1004173125@localhost><4.2.0.58.J.20011028114246.03932e70@localhost> <4.2.0.58.J.20011028140234.040c9600@localhost>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Mon, 29 Oct 2001 17:19:40 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
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 EAA07918


On Sunday, October 28, 2001 1:09 PM, Martin Duerst wrote:

> Assume somebody registers SSSS as a domain with name servers,...
> and registers TTTT CNAME SSSS, why would that not guarantee that
> everybody looking for foo.SSSS and for foo.TTTT would get to
> the same machine(s)?

Yes, I give the other example:
IN NS SSSS.foo
SSSS IN A 1.1.1.1

IN NS TTTT.foo
TTTT IN A 1.1.1.1

How to config the 1.1.1.1 and its subdomain?

Deng xiang






From owner-idn@ops.ietf.org  Mon Oct 29 04:49:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07950
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 04:49:56 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y8qF-000OCy-00
	for idn-data@psg.com; Mon, 29 Oct 2001 01:36:23 -0800
Received: from twnic.net.tw ([211.72.210.250])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y8qE-000OCp-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 01:36:22 -0800
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 RAA17106;
	Mon, 29 Oct 2001 17:35:52 +0800
Message-ID: <3BDD27BD.76531364@twnic.net.tw>
Date: Mon, 29 Oct 2001 17:56:14 +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: Patrik =?UTF-8?B?RueTo2x0c3Ry57m5bQ==?= <paf@cisco.com>
CC: Paul Hoffman / IMC <phoffman@imc.org>, xiang deng <deng@cnnic.net.cn>,
        idn@ops.ietf.org, Martin Duerst <duerst@w3.org>, klensin@jck.com
Subject: Re: [idn] An ignorant question about TC<-> SC
References: <E15xrqq-000Adc-00@psg.com><008901c16022$74b7c640$4407e29f@deng>
	 <p0510100db8027d203d26@[165.227.249.20]> <1180657.1004337022@localhost>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Patrik Fältström ¼g¤J¡G

> --On 01-10-28 19.30 -0800 "Paul Hoffman / IMC" <phoffman@imc.org> wrote:
>
> >> The A company must face the disputation.But there will be
> >> so many variant domain names, A company will be tired to
> >> deal with it, Where is the intelligent property of domain name?
> >> Whoes wrong?
> >
> > No one. That's the point. There is no technical means for determining all
> > of the names that are similar for a particular audience. There are
> > certainly non-technical human means for determining those names, and we
> > currently use non-technical human means for dealing with the problems.
>
> Paul is completely correct. The important thing is to have one well-defined
> set of rules for "equality". Given these rules, three things can happen:
>
>   - A registry can create well-defined rules for what can be requested
>     to be registered
>   - A registry can create well-defined rules for what goes into the
>     DNS zonefile given a registration request
>   - The dispute resolution process for a specific domain can define
>     their rules, and come up with their own practice for decision making
>
> What is NOT acceptable is to have rules which doesn't settle down, changes
> all the time etc.
>
> Just like Paul I see too many players trying to come up with engineering
> solutions to real world problems which have to do with "matching of words"
> and not "matching of identifiers" which DNS is about.

As mentioned in draft TSCONV, there are mainly 3 categories of TC/SC
conversion. They are 1-1 , 1-n , n-1

In the case of 1-1 , do not to care about the meaning. the matching of TC/SC
can be achieved by a matching function or a finite matching table. That is to
say matching of TC/SC can be done as Uppercase/Lowercase English letter
(EX: A-a).

If we say matching of Uppercase/Lowercase English letter belong to
"matching of identifiers", what is different from 1-1 TC/SC ?

As regards to 1-n and n-1 , it need to know more information such as the
meaning of the phrase or sentence. Such kind of TC/SC would be deal in higher
layer service.

>       paf

Erin Chen
 
 




From owner-idn@ops.ietf.org  Mon Oct 29 05:26:18 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08116
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 05:26:18 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y9GY-000OvB-00
	for idn-data@psg.com; Mon, 29 Oct 2001 02:03:34 -0800
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y9GX-000Ov4-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 02:03:34 -0800
Received: from deng ([159.226.7.68]) by whale.cnnic.net.cn
          (Netscape Messaging Server 4.15) with SMTP id GLYPCE00.1Z3; Mon,
          29 Oct 2001 18:05:02 +0800 
Message-ID: <006201c1605f$dd0ef870$4407e29f@deng>
From: "xiang deng" <deng@cnnic.net.cn>
To: <idn@ops.ietf.org>, "Paul Hoffman / IMC" <phoffman@imc.org>
References: <E15xrqq-000Adc-00@psg.com><008901c16022$74b7c640$4407e29f@deng><p0510100db8027d203d26@[165.227.249.20]><012101c16031$9bbd4120$4407e29f@deng> <p05101000b80297d251e6@[165.227.249.18]>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Mon, 29 Oct 2001 17:55:38 +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 FAA08116


On Monday, October 29, 2001 1:27 PM, Paul Hoffman / IMC wrote:
 
> Why not, indeed? No one here is saying that it should not be done. We 
> are saying that it should not be mandated in a technical 
> specification. There are many types of non-technical specifications 
> that would be very useful here. We have been told that the JET group 
> is coming out with one Real Soon Now, so that might address the 
> problem in a suitable fashion.

I'm not sure what's your meaning.  I always hear two voices:
1. go to UTC.
the requirements are:
(1) preserve the characteristic of TC /SC.
(2) compare without care of TC/SC.
TC and SC are different character, there needn't mapping from 
TC(SC) to SC (TC), it will make a character disappear. 

2.two records solution, one is SC form and the other is TC fom.
it's not applicable.

Deng xiang




From owner-idn@ops.ietf.org  Mon Oct 29 05:32:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08175
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 05:32:37 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y9Qo-000PBy-00
	for idn-data@psg.com; Mon, 29 Oct 2001 02:14:10 -0800
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y9Qn-000PBI-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 02:14:09 -0800
Received: from deng ([159.226.7.68]) by whale.cnnic.net.cn
          (Netscape Messaging Server 4.15) with SMTP id GLYPTX00.B3E; Mon,
          29 Oct 2001 18:15:33 +0800 
Message-ID: <006d01c16061$55b60150$4407e29f@deng>
From: "xiang deng" <deng@cnnic.net.cn>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        "Paul Hoffman / IMC" <phoffman@imc.org>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
Cc: <klensin@jck.com>
References: <E15xrqq-000Adc-00@psg.com><008901c16022$74b7c640$4407e29f@deng><p0510100db8027d203d26@[165.227.249.20]> <1180657.1004337022@localhost>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Mon, 29 Oct 2001 18:06:10 +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 FAA08175


On Monday, October 29, 2001 1:30 PM, Patrik Fältström wrote:

> --On 01-10-28 19.30 -0800 "Paul Hoffman / IMC" <phoffman@imc.org> wrote:
>
> Paul is completely correct. The important thing is to have one well-defined
> set of rules for "equality". Given these rules, three things can happen:
> 
>   - A registry can create well-defined rules for what can be requested
>     to be registered
>   - A registry can create well-defined rules for what goes into the
>     DNS zonefile given a registration request
>   - The dispute resolution process for a specific domain can define
>     their rules, and come up with their own practice for decision making
> 
> What is NOT acceptable is to have rules which doesn't settle down, changes
> all the time etc.
> 
> Just like Paul I see too many players trying to come up with engineering
> solutions to real world problems which have to do with "matching of words"
> and not "matching of identifiers" which DNS is about.

we fall into a loop. we all know the registration solution isn't a solution in fact,
there are technical issues. it can't be a advice from a engineering organize.
but we still  discuss it as a topic.

Deng xiang  












From owner-idn@ops.ietf.org  Mon Oct 29 05:51:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08360
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 05:51:33 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15y9nk-000PpT-00
	for idn-data@psg.com; Mon, 29 Oct 2001 02:37:52 -0800
Received: from [203.207.0.132] (helo=mail.asiainfra.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15y9nj-000PpN-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 02:37:51 -0800
Received: from gix ([203.207.0.121])
	by mail.asiainfra.com (8.9.3/8.9.3) with SMTP id SAA22626;
	Mon, 29 Oct 2001 18:37:54 +0800
From: "Kenny Huang" <huangk@alum.sinica.edu>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, <idn@ops.ietf.org>
Subject: RE: [idn] An ignorant question about TC<-> SC
Date: Sat, 27 Oct 2001 06:15:28 +0800
Message-ID: <IHELIFNJKJLDFEMBCENDCEHGCIAA.huangk@alum.sinica.edu>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
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.4807.1700
In-Reply-To: <3CD14E451751BD42BA48AAA50B07BAD6C5FBCE@vsvapostal3.prod.netsol.com>
Importance: Normal
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA08360

Hi,

Let's deal with Math: Each Chinese code has two kinds of formation
basically (for 1-1 mapping only). Thus we will have 2^N permutation.
There are about 2000 pairs of  frequently used TC/SC codes,
so we have 2^2000 permutation. Here comes the most interesting part:
The issue can be easily solved through existing technology, but we rather
shift  the burden of 2^2000 permutation to the daily labor intensive operations. 
Not to mention other ripple effect : 2^N lawsuit, trademark enforcement...,etc.  
I was convinced that these problems were created, just because engineers 
dislike it.  I am also curious to know why things are urged to that direction and
their motivation.


Kenny Huang



> -----Original Message-----
> From: owner-idn@ops.ietf.org [mailto:owner-idn@ops.ietf.org]On Behalf Of
> Hollenbeck, Scott
> Sent: Monday, October 29, 2001 6:59 AM
> To: idn@ops.ietf.org
> Subject: RE: [idn] An ignorant question about TC<-> SC
> 
> 
> > -----Original Message-----
> > From: Chun-Hsin Wu [mailto:wuch@gate.sinica.edu.tw]
> > Sent: Sunday, October 28, 2001 3:34 PM
> > 
> > 
> > For full-name DNS, White House may need to register at least
> > three records:
> >     "America"."USA"
> >     "United States"."USA"
> >     "USA"."USA"
> > If they forget to register "United States of America"."USA",
> > some other one may register it validly. This may imply that
> > every IDN customer must know and register all combinations
> > of the domain name he wants to register.
> 
> This situation isn't unique to IDNs.  I can register foobar.com, 
> and someone
> else can register foo-bar.com if I don't.  I have to make a conscious
> decision to register the name forms that are important to me.  Why should
> IDNs be treated differently?
> 
> -Scott-




From owner-idn@ops.ietf.org  Mon Oct 29 06:21:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08555
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 06:21:43 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yAE7-0000Y7-00
	for idn-data@psg.com; Mon, 29 Oct 2001 03:05:07 -0800
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yAE6-0000Y1-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 03:05:06 -0800
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 MAA27266;
	Mon, 29 Oct 2001 12:04:14 +0100 (MET)
Date: Mon, 29 Oct 2001 11:43:52 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Erin Chen <erin@twnic.net.tw>
cc: "Paul Hoffman / IMC" <phoffman@imc.org>, xiang deng <deng@cnnic.net.cn>,
        idn@ops.ietf.org, Martin Duerst <duerst@w3.org>, klensin@jck.com
Subject: Re: [idn] An ignorant question about TC<-> SC
Message-ID: <2309278.1004355832@localhost>
In-Reply-To: <3BDD27BD.76531364@twnic.net.tw>
References: <E15xrqq-000Adc-00@psg.com><008901c16022$74b7c640$4407e29f@deng>
 <p0510100db8027d203d26@[165.227.249.20]> <1180657.1004337022@localhost>
 <3BDD27BD.76531364@twnic.net.tw>
X-Mailer: Mulberry/2.1.1 (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-10-29 17.56 +0800 Erin Chen <erin@twnic.net.tw> wrote:

> As mentioned in draft TSCONV, there are mainly 3 categories of TC/SC
> conversion. They are 1-1 , 1-n , n-1
> 
> In the case of 1-1 , do not to care about the meaning. the matching of
> TC/SC can be achieved by a matching function or a finite matching table.
> That is to say matching of TC/SC can be done as Uppercase/Lowercase
> English letter (EX: A-a).
> 
> If we say matching of Uppercase/Lowercase English letter belong to
> "matching of identifiers", what is different from 1-1 TC/SC ?

Because the 1-1 mappings of SC/TC are not part of any work by ISO or
Unicode Consortium and because these bodies which work with characters
explicitly have told the IETF that only doing a partial solution is NOT
good. Just like the same bodies have not added mappings between codepoints
in parallell scripts in Eastern/Western Europe.

If it was possible to do such tables, I am a beliver that we would have
seen them. And even if it was possible, the Unicode Consortium would not
have told us that it is was not possible. Just because the tables will be
forever partial.

You say in this mail that it is better to have SC/TC mappings for some
codepoints, but not all. What do you think the users would say about that?
Is that really what you want?

It is better to not have any table at all and ask the registrant to do
multiple registrations. This can happen explcitly or implicitly when a
request comes from the registrant all depending on the policy the registry
has on registrations.

This is how things have worked in DNS since it was invented. This is
nothing new, or special for chinese characters.

    paf




From owner-idn@ops.ietf.org  Mon Oct 29 06:32:12 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08646
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 06:32:12 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yARc-0000uZ-00
	for idn-data@psg.com; Mon, 29 Oct 2001 03:19:04 -0800
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yARb-0000uT-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 03:19:04 -0800
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id AB31EFFC01; Mon, 29 Oct 2001 19:19:18 +0800 (SGT)
Message-ID: <019b01c1606b$83801120$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "xiang deng" <deng@cnnic.net.cn>,
        =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        "Paul Hoffman / IMC" <phoffman@imc.org>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
Cc: <klensin@jck.com>
References: <E15xrqq-000Adc-00@psg.com><008901c16022$74b7c640$4407e29f@deng><p0510100db8027d203d26@[165.227.249.20]> <1180657.1004337022@localhost> <006d01c16061$55b60150$4407e29f@deng>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Mon, 29 Oct 2001 19:19:02 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Deng Xiang,

Could you explain why "registration solution isn't a solution"?

Not every one of us knows why...(so please dont say "we all know...")

Thanks.

-James Seng

> we fall into a loop. we all know the registration solution isn't a
solution in fact,
> there are technical issues. it can't be a advice from a engineering
organize.
> but we still  discuss it as a topic.




From owner-idn@ops.ietf.org  Mon Oct 29 06:40:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08709
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 06:40:29 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yAc2-0001B0-00
	for idn-data@psg.com; Mon, 29 Oct 2001 03:29:50 -0800
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yAc1-0001As-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 03:29:49 -0800
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 MAA03361;
	Mon, 29 Oct 2001 12:29:36 +0100 (MET)
Date: Mon, 29 Oct 2001 12:20:06 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: xiang deng <deng@cnnic.net.cn>, "Paul Hoffman / IMC" <phoffman@imc.org>,
        idn@ops.ietf.org, Martin Duerst <duerst@w3.org>
cc: klensin@jck.com
Subject: Re: [idn] An ignorant question about TC<-> SC
Message-ID: <2439729.1004358006@localhost>
In-Reply-To: <006d01c16061$55b60150$4407e29f@deng>
References: <E15xrqq-000Adc-00@psg.com><008901c16022$74b7c640$4407e29f@deng>
 <p0510100db8027d203d26@[165.227.249.20]> <1180657.1004337022@localhost>
 <006d01c16061$55b60150$4407e29f@deng>
X-Mailer: Mulberry/2.1.1 (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-10-29 18.06 +0800 xiang deng <deng@cnnic.net.cn> wrote:

> we all know the registration solution isn't a solution in fact,
> there are technical issues.

Be careful when you write "we all know...".

Multiple registrations is a solution to the problem, and the recommended
one by Unicode Consortium for the SC/TC issue.

  paf




From owner-idn@ops.ietf.org  Mon Oct 29 06:42:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08732
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 06:42:34 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yAeD-0001EU-00
	for idn-data@psg.com; Mon, 29 Oct 2001 03:32:05 -0800
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yAeC-0001EO-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 03:32:04 -0800
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 MAA03375;
	Mon, 29 Oct 2001 12:29:39 +0100 (MET)
Date: Mon, 29 Oct 2001 12:26:28 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Kenny Huang <huangk@alum.sinica.edu>,
        "Hollenbeck, Scott" <shollenbeck@verisign.com>, idn@ops.ietf.org
Subject: RE: [idn] An ignorant question about TC<-> SC
Message-ID: <2462631.1004358388@localhost>
In-Reply-To: <IHELIFNJKJLDFEMBCENDCEHGCIAA.huangk@alum.sinica.edu>
References:  <IHELIFNJKJLDFEMBCENDCEHGCIAA.huangk@alum.sinica.edu>
X-Mailer: Mulberry/2.1.1 (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-10-27 06.15 +0800 Kenny Huang <huangk@alum.sinica.edu> wrote:

> I was convinced that these problems were created, just because engineers 
> dislike it.  I am also curious to know why things are urged to that
> direction and their motivation.

IF a mapping table existed from SC to TC or the other way around, which was
accepted by authoritative bodies in the world like ISO and Unicode
Consortium we could add that table to the nameprep mapping tables.

But, it doesn't exist because the mappings are not 1:1. Only some are 1:1.
Others are 1:n or n:1. See the tsconv draft. It is explained there.

Because such a table doesn't exist, only partial solutions to the SC/TC
problem can be created, and recommendations IETF get say that it is  better
to NOT have such a mapping table than a partial one which only talk about
the 1:1 ones.

And, even if we add a table for the 1:1 mappings, I have not seen an
authoritative source for such a table. Only a list of codepoints in the
tsconv draft without any reference to the source of the table.

   paf




From owner-idn@ops.ietf.org  Mon Oct 29 06:53:22 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08823
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 06:53:22 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yAp7-0001YD-00
	for idn-data@psg.com; Mon, 29 Oct 2001 03:43:21 -0800
Received: from mailb.telia.se ([131.115.15.109])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yAp6-0001Y7-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 03:43:20 -0800
Received: from mailb.telia.se (localhost [127.0.0.1])
	by mailb.telia.se (8.9.3/8.9.3) with ESMTP id MAA08246
	for <idn@ops.ietf.org>; Mon, 29 Oct 2001 12:43:14 +0100 (MET)
Received: from trab.se (valinor.malmo.trab.se [131.115.48.20])
	by mailb.telia.se (8.9.3/8.9.3) with ESMTP id MAA07776;
	Mon, 29 Oct 2001 12:41:43 +0100 (MET)
Message-ID: <3BDD4003.83E21A57@trab.se>
Date: Mon, 29 Oct 2001 12:39:47 +0100
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
X-Mailer: Mozilla 4.76 [sv] (X11; U; SunOS 5.9 sun4u)
X-Accept-Language: sv, en
MIME-Version: 1.0
To: ehall@ehsco.com, dhc@dcrocker.net, idn@ops.ietf.org
Subject: Re: [idn] iDNS re-chartering proposal, take 2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


>>For example, UDNS requires a coordinated release for at least two
>>purposes: so that name lengths can be synchronized, and so that
delegation
>>entities can
>>coordinate delegations they make as UTF-8 and ACE encoded
representations
>>of the same UCS string.

It does not. Name lengths is specified and will be supported by all
supporting UDNS.
Though some name lengths will not be possible to have in ACE, but ACE is
just
for backward compatibility. Never expect everything new to work in all
old
systems.

And there is no need for coordinated delegations. UDNS only uses one
representaion
of a label. The ACE format is always created from the UTF-8 native form.

There is no double delegation.

>
>uDNS a) is not a complete specification, and b) imposes operational
>requirements that are not viable in the existing DNS infrastructure.
>
Easy to say, but I have not seen anything to prove it.

UDNS is  a complete specification, but it does leave specification of
ACE and
how DNSSEC sorting is to be done to other RFCs. IDNA is a very
incomplete
specification - it does not solve the problem of having non-ASCII
in DNS, it just defines how to encode non-ASCII in "host names" into
an ACE.

And I do not know what operational requirements you think of.
I can start using UDNS today in my DNS server and it will work
fine.

    Dan





From owner-idn@ops.ietf.org  Mon Oct 29 07:28:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09451
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 07:27:57 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yBIY-0002H8-00
	for idn-data@psg.com; Mon, 29 Oct 2001 04:13:46 -0800
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yBIX-0002H2-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 04:13:45 -0800
Received: from [209.187.148.217] (helo=P2)
	by bs.jck.com with esmtp (Exim 3.32 #1)
	id 15yBIJ-0006JX-00; Mon, 29 Oct 2001 12:13:31 +0000
Date: Mon, 29 Oct 2001 07:13:16 -0500
From: John C Klensin <klensin@jck.com>
To: "James Seng/Personal" <jseng@pobox.org.sg>, jet-member@nic.ad.jp
cc: idn@ops.ietf.org
Subject: Re: [idn] Re: [JET-member 464] Re: Fw: Re: new members
 invitation 
Message-ID: <54309798.1004339595@localhost>
In-Reply-To: <015001c16029$fbcb39d0$1e01000a@jamessonyvaio>
References:  <015001c16029$fbcb39d0$1e01000a@jamessonyvaio>
X-Mailer: Mulberry/2.1.1 (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, 29 October, 2001 11:29 +0800 "James Seng/Personal"
<jseng@pobox.org.sg> wrote:

> You are confusing me too. So let me put it in another way.
> 
> There are many different kind of 'cost'. 'scaling cost' like
> what you described and 'economy cost' like what deng/tseng.
> 
> I am saying 'scaling cost' is an engineering considering, but
> not 'economy cost'.
> 
> Is this better?

James, Eric, and others,

I suspect that what I'm about to say is similar to what others
have been saying, but there is apparently sufficient confusion
that perhaps a different way to say it will help.

I'm not sure the distinction you are trying to make above helps.
But, more important, we are getting into areas here that are not
only not within WG scope, but are not even IETF issues.  

Let's distinguish between two types of economic issues.  In one
case, there is a protocol choice in which one option is
_inherently_ more expensive than another.  For example, suppose
we had one way of doing something that was vastly more costly to
develop or operate than another but, presumably, offered some
technical benefits.   It would be reasonable, and necessary, for
the IETF to consider the tradeoffs involved.  And, if we get it
wrong, we presumably get punished in the market.  

By contrast, assume there is a choice that depends on a
difference in pricing, not on costs.   Pricing is not our
problem, although we might offer some advice to registrars,
registries, or to ICANN.  To take the present situation as an
example, someone (presumably not an IETF WG) could possibly
convince some registrar that, if they offered a two-for-one deal
on TC and SC registrations, they could sufficiently increase
their volume on such registrations to make up any losses on
costs and, therefore, that doing so would be in their economic
interest.  No protocol changes needed.  Or one might try to
convince ICANN to presuade registries to adopt a similar rule.

There are potential IETF issues here, but they aren't within
IDN's scope.  For example, if one wanted to make a "TC and SC
for price of one" strategy cheap and easy, it might be sensible
to put some specific features to support that option into a
registrar-registry protocol (I'd hope we do not go down that
path  until and unless we have clear direction from either ICANN
or some ccTLD registries that they want such a thing).  Or one
might want to think about facilitating such matching by
registering and installing, e.g., the SC name normally, but
putting in the TC name as a DNAME RR, rather than series of NS
RRs.  I'd want to get advice from DNSEXT or some other
collection of DNS experts, but it might help with the solution
in the registrar/ registry space.  But, again, it is not an IDN
decision matter.

To oversimplify this a bit, my financial and economist friends
make a very strong distinction between cost issues and pricing
ones.  Cost issues may well be constraints on protocols, and
hence are something IETF should, IMO, carefully consider.  But
pricing issues are another matter, since prices are determined
by policies -- about what one can get away with, about the
allocation of costs, and so on.    Pricing issues are not an
IETF matter and, realistically, we could not directly influence
them if we try.  And a conversation about what some registry or
registrar will charge for various services is clearly a pricing
issue.

That one should be taken somewhere else.  I'd suggest the ICANN
DNSO, or their new IDN committee.  And perhaps this is an area
in which MINC should organize a lobbying and educational effort.

But it does not appear to me to be within the scope of the IDN
WG.

    john




From owner-idn@ops.ietf.org  Mon Oct 29 09:32:31 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14890
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 09:32:30 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yD53-00056q-00
	for idn-data@psg.com; Mon, 29 Oct 2001 06:07:57 -0800
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yD52-00056k-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 06:07:56 -0800
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9TE9dr41372;
	Mon, 29 Oct 2001 09:09:39 -0500 (EST)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110291409.f9TE9dr41372@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
cc: jet-member@nic.ad.jp, idn@ops.ietf.org, brunner@nic-naa.net,
        brunner@nic-naa.net
Subject: Re: [idn] Re: [JET-member 469] Re: Fw: Re: new members invitation 
In-Reply-To: Your message of "Mon, 29 Oct 2001 16:48:05 +0800."
             <005301c16056$712d4250$dd00a8c0@jamessonyvaio> 
Date: Mon, 29 Oct 2001 09:09:39 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James,

It wasn't my intention to misrepresent you. Please represent yourself.

Why is SC/TC "economic" and not "technical"?

What is "pure technical" and how does it relate to technical?

As L.M.Tseng has asked similar questions [1] being the most recent in this
same thread, an answer to him might be an answer to me.

In a seperate thread (RE: [idn] An ignorant question about TC<-> SC), in a
reply to Scott Hollenbeck <shollenbeck@verisign.com>, Kenny Huang wrote to
a similar point in [2]. This thread isn't cc'd to the jet-member@nic.ad.jp
list.

In that same thread, Deng Xiang wrote [4] that "the registration solution
isn't a solution", having previously made the a similar scaling observation,
here in a reply to Patrik Faltstrom, an IDNA co-author, who replied "multiple
registrations is a solution to the problem, and the recommended one by [the]
Unicode Consortium for the SC/TC issue". 

Again, an anwer to one (L.M.Tseng, Kenny Huang, Deng, ...) may be an answer
to all. I appreciate that you may find it difficult to write to me.

Eric

[1] <001101c1604b$0a2b2d20$f006738c@ncu.edu.tw> 
[2] <IHELIFNJKJLDFEMBCENDCEHGCIAA.huangk@alum.sinica.edu>
[3] Mon, 29 Oct 2001 12:20:06 +0100
[4] <006d01c16061$55b60150$4407e29f@deng>

P.S. My comment [5] on the utility of the UTC's participation in the technical
question (SC/TC in "the protocol" or in "the zonefile") read:

	In this one note I'm troubled to see the UTC presume to know
	better than the sources available to the authors of tsconv,
	and to know better than the authors of some eventual STANDARD
	and/or BCP track APPS or DNS IDs.

[5] <200109030113.VAA19923@nic-naa.net>



From owner-idn@ops.ietf.org  Mon Oct 29 09:44:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15349
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 09:44:11 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yDRC-0005im-00
	for idn-data@psg.com; Mon, 29 Oct 2001 06:30:50 -0800
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yDRB-0005ig-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 06:30:49 -0800
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 954FEFFC11; Mon, 29 Oct 2001 22:31:04 +0800 (SGT)
Message-ID: <038e01c16086$4d490600$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <jet-member@nic.ad.jp>
Cc: <jet-member@nic.ad.jp>, <idn@ops.ietf.org>, <brunner@nic-naa.net>
References: <200110291409.f9TE9dr41372@nic-naa.net>
Subject: [idn] Re: [JET-member 473] Re: Fw: Re: new members invitation 
Date: Mon, 29 Oct 2001 22:30:48 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> It wasn't my intention to misrepresent you. Please represent yourself.
>
> Why is SC/TC "economic" and not "technical"?

This is why this thread should never be in IDN WG in the first place
because there are so many discussion which was never even in this group.
It is a carried over from JET list.

I did *not* say SC/TC is "economy". Deng bought up arguments on why
TC/SC is neccessary because of "economy cost" in JET list. I responsed
to say that "economy cost" is generally not a consideration for IETF.

I feel there is no need to continue this discussion in the IDN WG until
we have the draft they promised. If you wish to continue, then please
feel free to do so in the JET list where the original discussion have
taken place.

-James Seng




From owner-idn@ops.ietf.org  Mon Oct 29 09:44:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15390
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 09:44:59 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yDLe-0005Yz-00
	for idn-data@psg.com; Mon, 29 Oct 2001 06:25:06 -0800
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yDLd-0005Ys-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 06:25:05 -0800
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9TEQrr41742;
	Mon, 29 Oct 2001 09:26:53 -0500 (EST)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110291426.f9TEQrr41742@nic-naa.net>
To: John C Klensin <klensin@jck.com>
cc: "James Seng/Personal" <jseng@pobox.org.sg>, jet-member@nic.ad.jp,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Re: [JET-member 464] Re: Fw: Re: new members invitation 
In-Reply-To: Your message of "Mon, 29 Oct 2001 07:13:16 EST."
             <54309798.1004339595@localhost> 
Date: Mon, 29 Oct 2001 09:26:53 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

John,

It may not be apparent, but the question is SC/TC in the protocol or in
some other mechanism, e.g., the way the UTC want it. Someone, you pick,
wrote that this wasn't a technical question. I think that person erred.

I want my registries to interoperate with other registries, the point of
an IETF, for things (labels, keywords, etc) which use code-points from
a common reference that are associated with "CJKV".

Everything else, with the exception of bidi, appears to be vastly easier.

Eric



From owner-idn@ops.ietf.org  Mon Oct 29 09:59:04 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16038
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 09:59:03 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yDfu-000682-00
	for idn-data@psg.com; Mon, 29 Oct 2001 06:46:02 -0800
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yDft-00067v-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 06:46:02 -0800
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id AF604FFC09; Mon, 29 Oct 2001 22:46:16 +0800 (SGT)
Message-ID: <046c01c16088$6cedb120$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <jet-member@nic.ad.jp>, <idn@ops.ietf.org>
References: <200110291426.f9TEQrr41742@nic-naa.net>
Subject: Re: [idn] Re: [JET-member 464] Re: Fw: Re: new members invitation 
Date: Mon, 29 Oct 2001 22:46:00 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I must be very bad at expressing myself or someone have reading my mails
in a way he choose to interpret. So let me put it blantly:

1. I did not say TC/SC is an economy issue. Someone else did.

2. I did not say TC/SC is not an technical issue. Someone suggested I
did.

3. "I am saying that IETF is an engineering group which consider
   technical trade-off, not economy ones.

I suspect someone is can twist these fairly simple point again of
course, for example, since "I did not say TC/SC is not an technical
issues" => "I say TC/SC is an technical issues" => "TC/SC is within
scope".

I am not sure about others folk here but I find this childish game very
tiring. This is my last email on this.

-James Seng

> It may not be apparent, but the question is SC/TC in the protocol or
in
> some other mechanism, e.g., the way the UTC want it. Someone, you
pick,
> wrote that this wasn't a technical question. I think that person
erred.
>
> I want my registries to interoperate with other registries, the point
of
> an IETF, for things (labels, keywords, etc) which use code-points from
> a common reference that are associated with "CJKV".
>
> Everything else, with the exception of bidi, appears to be vastly
easier.




From owner-idn@ops.ietf.org  Mon Oct 29 10:07:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16460
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 10:07:58 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yDjw-0006Cn-00
	for idn-data@psg.com; Mon, 29 Oct 2001 06:50:12 -0800
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yDjv-0006Ch-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 06:50:11 -0800
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9TEq2r42356;
	Mon, 29 Oct 2001 09:52:02 -0500 (EST)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110291452.f9TEq2r42356@nic-naa.net>
To: "James Seng/Personal" <jseng@pobox.org.sg>
cc: jet-member@nic.ad.jp, idn@ops.ietf.org, brunner@nic-naa.net,
        brunner@nic-naa.net
Subject: [idn] Re: [JET-member 473] Re: Fw: Re: new members invitation 
In-Reply-To: Your message of "Mon, 29 Oct 2001 22:30:48 +0800."
             <038e01c16086$4d490600$dd00a8c0@jamessonyvaio> 
Date: Mon, 29 Oct 2001 09:52:02 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James,

> I did *not* say SC/TC is "economy".

OK. But earlier you wrote:

> But the arguments for inclusive of TC/SC or not should be done on a pure
> technical evaluation basis in IETF. Economy arguments as above is not a
> factor for consideration.

The "above" was a discussion of where the complexity exists, in the design
and implementation of a protocol, or in end-user use of that protocol. Two
design points -- the tsconv and similar drafts at one end, and the Unicode
Technical Committee recommendation at the other. You concluded with:

> This is why it is known as engineering trade off, not economy trade off.
>
> -James Seng

So, hence my questions about what you think scaling is, in this context.

> I feel there is no need to continue this discussion in the IDN WG until
> we have the draft they promised. If you wish to continue, then please
> feel free to do so in the JET list where the original discussion have
> taken place.

If you'd be responsive in that list, fine. Please make your response to
that list. Someone on the JET list will eventually forward your reply to
me. If you prefer to defer until that draft is posted to this list, fine.
The issue isn't going away.

Eric




From owner-idn@ops.ietf.org  Mon Oct 29 10:10:41 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16530
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 10:10:40 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yDtH-0006N8-00
	for idn-data@psg.com; Mon, 29 Oct 2001 06:59:51 -0800
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yDtG-0006N2-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 06:59:50 -0800
Received: from [209.187.148.217] (helo=P2)
	by bs.jck.com with esmtp (Exim 3.32 #1)
	id 15yDsu-0006XU-00; Mon, 29 Oct 2001 14:59:28 +0000
Date: Mon, 29 Oct 2001 09:59:27 -0500
From: John C Klensin <klensin@jck.com>
To: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
cc: "James Seng/Personal" <jseng@pobox.org.sg>, jet-member@nic.ad.jp,
        idn@ops.ietf.org
Subject: Re: [idn] Re: [JET-member 464] Re: Fw: Re: new members
 invitation 
Message-ID: <64282521.1004349567@P2>
In-Reply-To: <200110291426.f9TEQrr41742@nic-naa.net>
References:  <200110291426.f9TEQrr41742@nic-naa.net>
X-Mailer: Mulberry/2.1.1 (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, 29 October, 2001 09:26 -0500 Eric Brunner-Williams
in Portland Maine <brunner@nic-naa.net> wrote:

> It may not be apparent, but the question is SC/TC in the
> protocol or in some other mechanism, e.g., the way the UTC
> want it. Someone, you pick, wrote that this wasn't a technical
> question. I think that person erred.

The general question is certainly a technical one.  It is not
clear that it is in scope for the IDN WG (let me come back to
that in another note).  If it is within scope for the IDN WG,
then I believe solutions are not possible (i.e., not solutions)
unless they solve (or avoid worsening) some other problems,
which I've tried to outline in earlier notes.

However, if one says "we need to do this because otherwise we
have to do double (or more) registrations and those are too
costly", _that_ question is not a technical one, except, as I
suggested, it interacts with either registrar-registry protocols
(not in IDN's scope) or the registration and use of CNAME
records (not in IDN's scope, I think).

> I want my registries to interoperate with other registries,
> the point of an IETF, for things (labels, keywords, etc) which
> use code-points from a common reference that are associated
> with "CJKV".

Yes.  So do we all.  And?

> Everything else, with the exception of bidi, appears to be
> vastly easier.

Well, I think it depends on your perspective.  We have,
potentially, many nearly-equivalent problems with languages that
are written in multiple scripts or other variants: if we try to
match them correctly, we end up with side-effects in other
places.  The _users_ of those languages have been less present,
and less articulate, than those concerned about Chinese, and
there are certainly fewer of them than there are users of
Chinese (or other Han-based character sets), but the problem is
not, IMO, any easier.

    john




From owner-idn@ops.ietf.org  Mon Oct 29 10:41:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17327
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 10:41:29 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yELB-0006z2-00
	for idn-data@psg.com; Mon, 29 Oct 2001 07:28:41 -0800
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yELA-0006yv-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 07:28:40 -0800
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.5/8.9.3) with ESMTP id f9TFUTr43238;
	Mon, 29 Oct 2001 10:30:29 -0500 (EST)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110291530.f9TFUTr43238@nic-naa.net>
To: John C Klensin <klensin@jck.com>
cc: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>,
        "James Seng/Personal" <jseng@pobox.org.sg>, jet-member@nic.ad.jp,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Re: [JET-member 464] Re: Fw: Re: new members invitation 
In-Reply-To: Your message of "Mon, 29 Oct 2001 09:59:27 EST."
             <64282521.1004349567@P2> 
Date: Mon, 29 Oct 2001 10:30:29 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

John,

> However, if one says "we need to do this because otherwise we
> have to do double (or more) registrations and those are too

We're discussing exponential behavior. Scaling is the problem we are trying
to solve. Does an out-of-protocol SC/TC equivalance mechanism both exist and
scale, for the existing problem constraints?

Eric



From owner-idn@ops.ietf.org  Mon Oct 29 11:00:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17772
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 11:00:15 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yEdC-0007P1-00
	for idn-data@psg.com; Mon, 29 Oct 2001 07:47:18 -0800
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yEdB-0007Om-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 07:47:17 -0800
Received: from [209.187.148.217] (helo=P2)
	by bs.jck.com with esmtp (Exim 3.32 #1)
	id 15yEd4-0006cS-00; Mon, 29 Oct 2001 15:47:10 +0000
Date: Mon, 29 Oct 2001 10:47:09 -0500
From: John C Klensin <klensin@jck.com>
To: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
cc: "James Seng/Personal" <jseng@pobox.org.sg>, jet-member@nic.ad.jp,
        idn@ops.ietf.org
Subject: Re: [idn] Re: [JET-member 464] Re: Fw: Re: new members
 invitation 
Message-ID: <67144972.1004352429@P2>
In-Reply-To: <200110291530.f9TFUTr43238@nic-naa.net>
References:  <200110291530.f9TFUTr43238@nic-naa.net>
X-Mailer: Mulberry/2.1.1 (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, 29 October, 2001 10:30 -0500 Eric Brunner-Williams
in Portland Maine <brunner@nic-naa.net> wrote:

>> However, if one says "we need to do this because otherwise we
>> have to do double (or more) registrations and those are too
> 
> We're discussing exponential behavior. Scaling is the problem
> we are trying to solve. Does an out-of-protocol SC/TC
> equivalance mechanism both exist and scale, for the existing
> problem constraints?

Beats me.  I'm still not sure I understand the stated problem
constraints (e.g., I'm not sure whether we really have to
"translate" an arbitrary combination of mixed TC and SC
characters to some other arbitrary combination of them or
whether the problem can sensibly be constrained to translating
entirely-TC strings to entirely-SC strings and/or back).  The
two, obviously, have widely different scaling properties if one
tries to go the multiple registration route as most of us would
not spend a lot of effort on a factor of two.

Conversely, there are some potentially serious problem
constraints that I'm not sure I see being addressed.  And I
prefer to not try to guess at how (or whether) some proposal
will deal with them until I see the proposal.   Among those
constraints is that we don't language-label and we don't insist
that the labels of an FQDN be homogeneous (or even predictable
from each other) wrt language or even script embedded in Unicode.

    john
 



From owner-idn@ops.ietf.org  Mon Oct 29 11:13:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18128
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 11:13:58 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yEqs-0007gO-00
	for idn-data@psg.com; Mon, 29 Oct 2001 08:01:26 -0800
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yEqs-0007gI-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 08:01:26 -0800
Received: from bbprime.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 IAA32427;
	Mon, 29 Oct 2001 08:00:56 -0800
Message-Id: <5.1.0.14.2.20011029074912.05712110@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 29 Oct 2001 07:56:24 -0800
To: "Eric A. Hall" <ehall@ehsco.com>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] iDNS re-chartering proposal, take 2
Cc: idn@ops.ietf.org
In-Reply-To: <3BDD1E94.62F82A5F@ehsco.com>
References: <5.1.0.14.2.20011027084819.03d3b6c0@brandenburg.com>
 <5.1.0.14.2.20011028145534.03d1f008@dcrocker.net>
 <5.1.0.14.2.20011028152132.01c501c0@dcrocker.net>
 <5.1.0.14.2.20011028191806.03cd6468@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 03:17 AM 10/29/2001 -0600, Eric A. Hall wrote:
>Dave Crocker wrote:
> > >  Going with ACE-only directly equates to two mandatory encodings.
> > > This is an incredibly high cost to lay on the Internet
>
>It is not possible for two encodings to
>be as efficient for the community as a single shared encoding.

Please attend to the difference between "incredibly high cost" and "not as 
efficient".  There is nothing contradictory in having the former be NOT 
true at the same time as the latter IS true.

One of the problems with your use of injudicious language is that it lacks 
precision.  A cost can exist, but be small.


>I have said several times quite clearly that ACE is necessary as a
>backwards compatibility mode for legacy applications.

Doing one specific piece of work, now, and deferring pursuit of an 
additional specification, for additional changes to the DNS, is standard 
IETF practise.

Since you are (correctly) declaring that we do need to do an ACE approach, 
there is no debate.

So let's move on.

d/

ps.  this line of debate is now closed, since I will not be responding 
further and it takes two to have a debate.

----------
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 Oct 29 11:25:53 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18582
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 11:25:52 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yF60-00081r-00
	for idn-data@psg.com; Mon, 29 Oct 2001 08:17:04 -0800
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yF5z-00081l-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 08:17:03 -0800
Received: from bbprime.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 IAA00613;
	Mon, 29 Oct 2001 08:15:57 -0800
Message-Id: <5.1.0.14.2.20011029075717.01ebf548@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 29 Oct 2001 08:06:23 -0800
To: Dan Oscarsson <Dan.Oscarsson@trab.se>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] iDNS re-chartering proposal, take 2
Cc: idn@ops.ietf.org
In-Reply-To: <3BDD4003.83E21A57@trab.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 12:39 PM 10/29/2001 +0100, Dan Oscarsson wrote:
>And there is no need for coordinated delegations. UDNS only uses one
>representaion of a label. The ACE format is always created from the UTF-8 
>native form.

This means that uDNS is not useful until this broad infrastructure support 
for it.  That makes is vastly more difficult to deploy and THAT means that 
it takes much longer to become useful than does a straight ACE approach.


> >uDNS a) is not a complete specification, and b) imposes operational
> >requirements that are not viable in the existing DNS infrastructure.
>
>UDNS is  a complete specification, but it does leave specification of
>ACE and how DNSSEC sorting is to be done to other RFCs. IDNA is a very
>incomplete specification - it does not solve the problem of having non-ASCII
>in DNS, it just defines how to encode non-ASCII in "host names" into
>an ACE.

A complete specification is one that deals with an issue completely.  It 
does not matter whether this requires one document or many.  If there are 
issues left open, then the specification is incomplete.  A reader cannot 
evaluate all the details unless all of the details are presented.

So, thank you for agreeing that the uDNS specification is incomplete.


>And I do not know what operational requirements you think of.
>I can start using UDNS today in my DNS server and it will work
>fine.

Thank you for stating so clearly that you are attending only to viability 
on a small scale.  Attending to broad Internet deployment and utility is a 
very different process from what you are doing.

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 Oct 29 11:51:23 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19469
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 11:51:23 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yFT8-0008yo-00
	for idn-data@psg.com; Mon, 29 Oct 2001 08:40:58 -0800
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yFT8-0008yi-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 08:40:58 -0800
Received: from bbprime.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 IAA01596
	for <idn@ops.ietf.org>; Mon, 29 Oct 2001 08:40:57 -0800
Message-Id: <5.1.0.14.2.20011029083602.058c7830@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 29 Oct 2001 08:36:56 -0800
To: idn@ops.ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] iDNS re-chartering proposal, take 2
In-Reply-To: <5.1.0.14.2.20011029075717.01ebf548@dcrocker.net>
References: <3BDD4003.83E21A57@trab.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

oops.  typo:

At 08:06 AM 10/29/2001 -0800, Dave Crocker wrote:
>This means that uDNS is not useful until this

this => there is

>broad infrastructure support for it.  That makes is vastly more difficult 
>to deploy and THAT means that it takes much longer to become useful than 
>does a straight ACE approach.


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 Oct 29 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 ESMTP id MAA20657
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 12:23:37 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yFuh-000BI8-00
	for idn-data@psg.com; Mon, 29 Oct 2001 09:09:27 -0800
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yFug-000BI1-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 09:09:26 -0800
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 204806; Sun, 28 Oct 2001 11:09:19 -0600
Message-ID: <3BDD8D44.7D9F82B0@ehsco.com>
Date: Mon, 29 Oct 2001 11:09:24 -0600
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dave Crocker <dhc@dcrocker.net>
CC: idn@ops.ietf.org
Subject: Re: [idn] iDNS re-chartering proposal, take 2
References: <5.1.0.14.2.20011027084819.03d3b6c0@brandenburg.com>
	 <5.1.0.14.2.20011028145534.03d1f008@dcrocker.net>
	 <5.1.0.14.2.20011028152132.01c501c0@dcrocker.net>
	 <5.1.0.14.2.20011028191806.03cd6468@dcrocker.net> <5.1.0.14.2.20011029074912.05712110@dcrocker.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


I knew you couldn't say it.

Dave Crocker wrote:
> 
> At 03:17 AM 10/29/2001 -0600, Eric A. Hall wrote:
> >Dave Crocker wrote:
> > > >  Going with ACE-only directly equates to two mandatory encodings.
> > > > This is an incredibly high cost to lay on the Internet
> >
> >It is not possible for two encodings to
> >be as efficient for the community as a single shared encoding.
> 
> Please attend to the difference between "incredibly high cost" and "not as
> efficient".  There is nothing contradictory in having the former be NOT
> true at the same time as the latter IS true.
> 
> One of the problems with your use of injudicious language is that it lacks
> precision.  A cost can exist, but be small.
> 
> >I have said several times quite clearly that ACE is necessary as a
> >backwards compatibility mode for legacy applications.
> 
> Doing one specific piece of work, now, and deferring pursuit of an
> additional specification, for additional changes to the DNS, is standard
> IETF practise.
> 
> Since you are (correctly) declaring that we do need to do an ACE approach,
> there is no debate.
> 
> So let's move on.
> 
> d/
> 
> ps.  this line of debate is now closed, since I will not be responding
> further and it takes two to have a debate.
> 
> ----------
> Dave Crocker  <mailto:dcrocker@brandenburg.com>
> Brandenburg InternetWorking  <http://www.brandenburg.com>
> tel +1.408.246.8253;  fax +1.408.273.6464

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



From owner-idn@ops.ietf.org  Mon Oct 29 13:03:40 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22130
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 13:03:40 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yGVX-000C6m-00
	for idn-data@psg.com; Mon, 29 Oct 2001 09:47:31 -0800
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yGVW-000C6U-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 09:47:30 -0800
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.6/8.9.3) with ESMTP id f9THmp333266;
	Mon, 29 Oct 2001 12:48:51 -0500 (EST)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110291748.f9THmp333266@nic-naa.net>
To: John C Klensin <klensin@jck.com>
cc: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>,
        "James Seng/Personal" <jseng@pobox.org.sg>, jet-member@nic.ad.jp,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Re: [JET-member 464] Re: Fw: Re: new members invitation 
In-Reply-To: Your message of "Mon, 29 Oct 2001 10:47:09 EST."
             <67144972.1004352429@P2> 
Date: Mon, 29 Oct 2001 12:48:51 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

John,

"Beats me" is fine answer, as is looking critically at the stated, and
unstated, problem constraints.

If we were to consider Abenaki/Mikmaq/Maliseet/... (17th century French
script derived scripts) and other Indian languages (contemporary, even
modern Spanish and English derived scripts) character sets and "Roman",
we'd be looking at the following equivalence problem:

                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"

This just for the "8". "TC" in this context would be Abenaki (etc) written
with niche-market IBM Selectric type sets, similar to Inuktitut, and "SC"
would be the same written on an unforgiving 101 key IBM PC keyboard, ACSII.
We call it "diacritically simplified" characters -- basically everything is
promoted to its nearest ASCII look-alike, and all or almost all diacriticals
are stripped.

I don't claim that "solving for Abenaki <or even Cree or Dine'>" is nearly
as important as the SC/TC problem.

Eric



From owner-idn@ops.ietf.org  Mon Oct 29 14:50:19 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25270
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 14:50:19 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yI0V-000Dwi-00
	for idn-data@psg.com; Mon, 29 Oct 2001 11:23:35 -0800
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yI0U-000Dwa-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 11:23:34 -0800
Received: from [165.227.249.18] (165-227-249-18.client.dsl.net [165.227.249.18])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f9TJNU810480;
	Mon, 29 Oct 2001 11:23:30 -0800 (PST)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0510100fb8034e089e46@[165.227.249.18]>
In-Reply-To: <001101c1604b$0a2b2d20$f006738c@ncu.edu.tw>
References: 
 <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp><01c801c15
 c3d$d9a7ae50$4407e29f@deng> <20011024130954A.yone@nic.ad.jp>
 <024101c15c42$372e1b50$4407e29f@deng>
 <007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio>
 <003f01c15f5c$1d4e5f70$ec1bd9d2@temp>
 <001101c15f64$7eb3b780$1c01000a@jamessonyvaio>
 <016601c15f7d$14325c40$ec1bd9d2@temp>
 <005501c15f80$9dd52a10$1c01000a@jamessonyvaio>
 <000d01c15f81$5573d900$ec1bd9d2@temp>
 <006301c15f82$da0cbe60$1c01000a@jamessonyvaio>
 <001e01c15fae$010900c0$f006738c@ncu.edu.tw>
 <p05101003b801e8c9a90b@[165.227.249.20]>
 <001101c1604b$0a2b2d20$f006738c@ncu.edu.tw>
Date: Mon, 29 Oct 2001 11:22:17 -0800
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: [idn] Traditional-simplified, yet again
Cc: jet-member@nic.ad.jp
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 3:50 PM +0800 10/29/01, Erin Chen wrote:
>If we consider TC/SC are not the names similar but just like
>Uppercase/Lowercase English letter.

It has been shown that this is *not* just like case in English. That 
would only be true if Han characters could be converted 1:1, if there 
was a stable matching system that did not need human context, and if 
everyone in all countries that use Han agreed to the matching system. 
None of those three things are true.

>If you think of TC/SC requirement is non-technical human means,
>then hou about Uppercase/Lowercase English letter deal in DNS?

English case folding meets that set of requirements, and more. Note 
that, even though it is pretty much universally accepted, it still 
has its problems. Capitalization is very important to some people's 
names, and the case folding smashes their names in an unpleasant way.

At 5:56 PM +0800 10/29/01, Erin Chen wrote:
>As mentioned in draft TSCONV, there are mainly 3 categories of TC/SC
>conversion. They are 1-1 , 1-n , n-1
>
>In the case of 1-1 , do not to care about the meaning. the matching of TC/SC
>can be achieved by a matching function or a finite matching table. That is to
>say matching of TC/SC can be done as Uppercase/Lowercase English letter
>(EX: A-a).

Maybe this is a false analogy. From my understanding, some of the 
*characters* that would be mapped in a 1-to-1 mapping are part of 
*words* and *names* that would instead be mapped n-to-1, yes? If so, 
doing the 1-to-1 mapping would make the DNS label unreadable.

Further, and more important, please remember that many of the 
characters that would be mapped in the 1-to-1 table are used in 
languages other than Chinese. It is, of course, completely 
unacceptable to do a traditonal-to-simplified mapping in a Japanese 
or Korean name, yet it is impossible for a system that is doing the 
mapping to tell the language in the label.



At 5:55 PM +0800 10/29/01, xiang deng wrote:
>On Monday, October 29, 2001 1:27 PM, Paul Hoffman / IMC wrote:
>
>>  Why not, indeed? No one here is saying that it should not be done. We
>>  are saying that it should not be mandated in a technical
>>  specification. There are many types of non-technical specifications
>>  that would be very useful here. We have been told that the JET group
>>  is coming out with one Real Soon Now, so that might address the
>>  problem in a suitable fashion.
>
>I'm not sure what's your meaning.  I always hear two voices:
>1. go to UTC.
>the requirements are:
>(1) preserve the characteristic of TC /SC.
>(2) compare without care of TC/SC.
>TC and SC are different character, there needn't mapping from
>TC(SC) to SC (TC), it will make a character disappear.
>
>2.two records solution, one is SC form and the other is TC fom.
>it's not applicable.

Well, I'm sure you hear more than just two voices on this! :-) I have 
never talked about a "two record solution" because we know that there 
will need to be more than two for many Chinese names. What I am 
saying is that it seems likely that there can be good advice given to 
registries and registrants about equivalence for Han names that might 
be used when registering (or even after registering), and that such 
advice might be appropriate for this WG to work on.

The people who have said "go to the UTC" have been responding to the 
assertion that  a technical mapping of traditional-simplified is 
possible today. Other people have countered that there is no 
well-agreed-on table for the mapping; still others have said that 
such a table is impossible because of the need for context; and still 
others have said that this is all moot because 
traditional-to-simplified mapping must not be done on Japanese or 
Korean names, but there is no way to prevent that without context.

Assertions that "we can do this" are OK, but if it hasn't been 
approved by an international body that is respected, it probably 
won't be approved here. So, "go to the UTC" might mean "until we hear 
from such a body that this is finished, stable, and sensible, we 
cannot wait for it". Fortunately, we don't need to: 
traditional-simplified and other similar mappings can help DNS users 
of the world without having to be part of the IDN protocol.

Where JET and/or CDNC can definitely help here is in clearly 
articulating the problem for Han characters and a proposed solution 
for people registering names, and for the agencies doing the 
registering. We have not seen such a document yet, so the WG cannot 
decide if that would be something we want to work on. Even if it is 
not done in the IETF, such a document (and similar documents for the 
many other languages with similar problems) will be very useful in 
the world.



At 3:26 PM +0800 10/29/01, L.M.Tseng wrote:
>          I think  the cost assigned by the registry is the service charge.

This has nothing to do with the IDN specification. A registry can 
charge as much or as little (including zero) as it wants. The 
overhead for assigning three additional names to one person who asks 
for one is so small that it would make sense if the cost went away. 
This is analogous to Internet Service Providers allowing one person 
to have five mailboxes for the same price as one mailbox. Some ISPs 
do this, and they attract customers because of it; others don't do it.

>          Some user register one domain name and setup a DNS to extend his
>domain service for organizations' host name. To handle the multiple TC/SC
>name registry is an overhead to treat them, the size of storage and the time
>for careful treatment is an inherent cost of  complexity. The complexity
>come from a neglection to reduce them in a proper level .  That complexity
>and cost will let the system manager try to not provide TC/SC multple
>records in his managed zone file, then the stability and trust to use CJK
>domain name will be very low. Finally , it come back to reflect it is not a
>workable approach.

It is unfortunate that some people keep talking about this as if it 
was only a Chinese issue. It is *not*. The very same issue appears 
for every language where there are words and names with nearly 
identical meaning, and the issue appears in every language where 
there are words and names with nearly identical spellings.

This discussion has an undercurrent of Chinese vs. non-Chinese, and 
that is really ugly. The problems faced in traditional-simplified 
conversion (that the conversions are 1:1, 1:n, and n:1; that there is 
not a single, stable standard; that it cannot be applied to Japanese 
or Korean characters) are similar to those faced in throughout the 
world. Making this a Chinese issue is deeply disrespectful to all the 
other people throughout the world who have exactly the same problem 
as the Chinese do. Nor is this an issue of the number of speakers of 
the language: some of these issues arise in Indian and Arabic names.

Once again: the DNS is pretty bad at dealing with these kinds of 
issues for names. This was proven conclusively first for US English, 
then for all languages that can use Latin characters. IDN will simply 
make these problems apparent for many scripts throughout the world. 
The people who say "the IETF cannot move forwards with IDN until it 
is better for my language than for other people's language" are doing 
a disservice to everyone, including the people who use their own 
language.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Mon Oct 29 20:38:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01713
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 20:38:57 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yNYI-000M0u-00
	for idn-data@psg.com; Mon, 29 Oct 2001 17:18:50 -0800
Received: from [203.207.0.132] (helo=mail.asiainfra.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yNYG-000M0o-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 17:18:49 -0800
Received: from gix ([203.207.0.121])
	by mail.asiainfra.com (8.9.3/8.9.3) with SMTP id JAA26450;
	Tue, 30 Oct 2001 09:18:24 +0800
From: "Kenny Huang" <huangk@alum.sinica.edu>
To: "Eric A. Hall" <ehall@ehsco.com>, "Dave Crocker" <dhc@dcrocker.net>
Cc: <idn@ops.ietf.org>
Subject: RE: [idn] iDNS re-chartering proposal, take 2
Date: Sat, 27 Oct 2001 20:55:59 +0800
Message-ID: <IHELIFNJKJLDFEMBCENDGEHOCIAA.huangk@alum.sinica.edu>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <3BDD1E94.62F82A5F@ehsco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id UAA01713


I support UTF-8 based advanced DNS infrastructure, and support ACE 
since many people like to embrace legacy systems. DNS definitely 
is capable to take care more than one encoding scheme. The Internet
is composed by both legacy system and advanced system all the time.
Let the market decide whice one can survive.

Kenny Huang



> 
> I have said several times quite clearly that ACE is necessary as a
> backwards compatibility mode for legacy applications. Where we part is
> that you also believe that this second mandatory untested encoding that is
> jammed into a transliteration layer for every existing and future
> application is the ultimate in practical design. Just admit that it has
> problems which can be addressed by an optimized form with a different set
> of priorities. Come on, just say it!
> 
> -- 
> Eric A. Hall                                        http://www.ehsco.com/
> Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/




From owner-idn@ops.ietf.org  Mon Oct 29 20:42:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01788
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 20:42:32 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yNmS-000MUO-00
	for idn-data@psg.com; Mon, 29 Oct 2001 17:33:28 -0800
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yNmR-000MUI-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 17:33:27 -0800
Received: from zetnet.co.uk (man-s374.dialup.zetnet.co.uk [194.247.45.245])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f9U1XAB03027;
	Tue, 30 Oct 2001 01:33:21 GMT
Message-ID: <3BDE03E6.9476E5A3@zetnet.co.uk>
Date: Tue, 30 Oct 2001 01:35:34 +0000
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: stringprep and unassigned code points
References: <7FC3066C236FD511BC5900508BAC86FE4D7E46@trestles.internal.realnames.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-----

Yves Arrouye wrote:
> Honestly, I do not see any other way than to upgrade everybody to a newer
> Nameprep when the mapping tables change for new code points.

New unicameral scripts (without case distinctions), that have no NFC/NFKC
mappings can be supported without any changes to nameprep. That leaves
bicameral scripts, and scripts that have NFC mappings, i.e. they have
both precomposed and decomposed characters (compatibility mappings for
new scripts are extremely unlikely). In order for those scripts to
be used at all, the client's operating system will need to be updated to
support a new version of Unicode. If the OS provides case folding and
normalisation functions [*], then old applications calling the new
functions will work fine. Even if the OS doesn't provide all of the
needed functionality, it could do in new versions, and an IDN library
could use the OS whereever possible, falling back to its own
implementation otherwise.

Of course this requires that nameprep is defined strictly in terms of
standard Unicode mappings and properties. That is possible if we use NFC,
and define the disallowed characters in terms of Unicode character
properties (note that no "additional mappings" are needed to make
casefold o NFC idempotent, I think; I've recently asked on the Unicode
mailing list to confirm that).

[*] Win32 does for NFC normalisation, I'm not sure about case folding.

- -- 
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

iQEVAwUBO94D0TkCAxeYt5gVAQF6ygf/TAc63TwyAyNFZIv3kPS/m2Y+2+k8qhwf
aZz1uzodGofF6kXamHOMT4h/JzwH8luKm3mJP7dJ8dPlMoN+ZFVQqSmNULYDknND
Cy7f0H/W6usAKNOBCu+MqNKkD+S7sCdUz8kWFVftykmyM/aaKyK4y0ahvtvMjLq1
EQMpkCOZe2q2q/OW7x9dprvV1JxsxL31NP7LysYdOzpg0S6jY9uehBWH5TM1+Zko
3SD0GC4vjiH9XHYDp+JQ0bBY8dMLR3Y8EKxCZUTnrRpM6Ygjn6X3xi5q95UWFiic
gvl97efDZ1EZWz03Ns1T7oRwEYBfMD3oaLuhsqz+4G5c9YAHNMIExQ==
=PDXw
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Mon Oct 29 20:45:49 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01837
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 20:45:49 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yNpt-000Max-00
	for idn-data@psg.com; Mon, 29 Oct 2001 17:37:01 -0800
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yNpt-000Mar-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 17:37:01 -0800
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 RAA20431;
	Mon, 29 Oct 2001 17:36:55 -0800
Message-Id: <5.1.0.14.2.20011029172743.035ad008@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 29 Oct 2001 17:31:15 -0800
To: "Kenny Huang" <huangk@alum.sinica.edu>
From: Dave Crocker <dhc@dcrocker.net>
Subject: [idn] utf-8 "support"
Cc: <idn@ops.ietf.org>
In-Reply-To: <IHELIFNJKJLDFEMBCENDGEHOCIAA.huangk@alum.sinica.edu>
References: <3BDD1E94.62F82A5F@ehsco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 08:55 PM 10/27/2001 +0800, Kenny Huang wrote:
>I support UTF-8 based advanced DNS infrastructure, and support ACE

Kenny,

Thank you.  However support for a concept, such as "UTF-8", is not really a 
factor in this topic.  We are trying to make progress of concrete 
specifications.

The concerns now are:

         -  what is feasible for transition with the existing DNS installed 
base,

         -  what specifications are essentially complete, and

         -  what specifications have demonstrated good working group rough 
consensus.

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 Oct 29 21:59:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03665
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 21:59:33 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yOx4-000OWz-00
	for idn-data@psg.com; Mon, 29 Oct 2001 18:48:30 -0800
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yOx4-000OWp-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 18:48:30 -0800
Received: from cs881964a ([24.43.70.205]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Mon, 29 Oct 2001 19:01:49 -0800
Message-ID: <000d01c160ee$a8936740$cd462b18@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: <idn@ops.ietf.org>, "Paul Hoffman / IMC" <phoffman@imc.org>
Cc: <jet-member@nic.ad.jp>
References:  <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp><01c801c15 c3d$d9a7ae50$4407e29f@deng> <20011024130954A.yone@nic.ad.jp> <024101c15c42$372e1b50$4407e29f@deng> <007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio> <003f01c15f5c$1d4e5f70$ec1bd9d2@temp> <001101c15f64$7eb3b780$1c01000a@jamessonyvaio> <016601c15f7d$14325c40$ec1bd9d2@temp> <005501c15f80$9dd52a10$1c01000a@jamessonyvaio> <000d01c15f81$5573d900$ec1bd9d2@temp> <006301c15f82$da0cbe60$1c01000a@jamessonyvaio> <001e01c15fae$010900c0$f006738c@ncu.edu.tw> <p05101003b801e8c9a90b@[165.227.249.20]> <001101c1604b$0a2b2d20$f006738c@ncu.edu.tw> <p0510100fb8034e089e46@[165.227.249.18]>
Subject: Re: [idn] Traditional-simplified, yet again
Date: Mon, 29 Oct 2001 21:56:28 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Paul,

> This discussion has an undercurrent of Chinese vs. non-Chinese, and
> that is really ugly. The problems faced in traditional-simplified

> The people who say "the IETF cannot move forwards with IDN until it
> is better for my language than for other people's language" are
doing
> a disservice to everyone, including the people who use their own
> language.
>
> --Paul Hoffman, Director
> --Internet Mail Consortium
>

Although I generally like to stay out of discussions on TC<->SC (due
to my lack of technical knowledge compared to most people in this WG),
I must correct you on the above.  To blame the Chinese people in this
WG for delaying the progress of the IETF is so unfair.  How is it
possible for people to delay the progress of the IETF by simply
posting up messages and writing drafts?

Thanks,
Ben









From owner-idn@ops.ietf.org  Mon Oct 29 21:59:43 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03676
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 21:59:42 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yOuP-000OOx-00
	for idn-data@psg.com; Mon, 29 Oct 2001 18:45:45 -0800
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yOuO-000OOp-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 18:45:44 -0800
Received: from deng ([159.226.7.68]) by whale.cnnic.net.cn
          (Netscape Messaging Server 4.15) with SMTP id GLZZQ400.G5E; Tue,
          30 Oct 2001 10:46:52 +0800 
Message-ID: <008b01c160eb$cfc834b0$4407e29f@deng>
From: "xiang deng" <deng@cnnic.net.cn>
To: "James Seng/Personal" <jseng@pobox.org.sg>,
        =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        "Paul Hoffman / IMC" <phoffman@imc.org>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
Cc: <klensin@jck.com>
References: <E15xrqq-000Adc-00@psg.com><008901c16022$74b7c640$4407e29f@deng><p0510100db8027d203d26@[165.227.249.20]> <1180657.1004337022@localhost> <006d01c16061$55b60150$4407e29f@deng> <019b01c1606b$83801120$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Tue, 30 Oct 2001 10:37:26 +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 VAA03676


On Monday, October 29, 2001 7:19 PM,James Seng/Personal wrote:
 
> Could you explain why "registration solution isn't a solution"?
> Not every one of us knows why...(so please dont say "we all know...")

1.Adopting multiple records solution - analysis
If a multiple records solution are adopted, and all possible 
TC/SC forms of a single Chinese domain name are added into a 
zone file as the different forms of one identical domain name, 
then this approach has the following weakness:
(1)2^n problem. To ensure a Chinese domain name both TC/SC to 
be correctly resolved, 2^n records must be registered and all 
the records point to one IP address (Note: n indicates the total 
number of the TC/SC variants of the domain name). Chinese has 
over 4,000 variants, and most of them are in common use, a single 
ordinary domain name may have dozens of, hundreds of even thousands 
of TC/SC records, if all of them are to be registered, then total 
number of registrations will explode. In order to protect their 
domain name, users must register 2^n domain names, registration 
cost will increase rapidly, and this is obviously not practical.

(2)The lower level delegation domain name servers may adopt a 
different domain administrative policy or they simply don't support 
multiple records registration, therefore the consistency of TC/SC 
domain names cannot be ensured.

(3)How to ensure that the 2^n records are to be owned by a single 
registered user? This is also an inevitable question, if this cannot 
be ensured, there are will be a large number of domain name 
disputationes. Different registration authorities has different 
registration policies, even if the registration policies can prevent
gTLD and ccTLD practice; they don't have control over secondary or 
tertiary domain.

2.Adopting TC only records and SC only records solution - analysis
TC only records and SC only records solution has the following weakness:
(1)Not applicable to Hong Kong and Macao where both TC and SC are used, 
simplified Chinese is not used at all in Taiwan, TC only or SC only 
records cannot meet the requirements of the users.

(2)This approach cannot solve technically delegation domain problems either.

(3) How to ensure that the two kinds of records are to be owned by a 
single registered user? This is also an inevitable question, if this 
cannot be ensured, there are will be a large number of domain name 
disputationes. Different registration authorities has different 
registration policies, even if the registration policies can prevent 
gTLD and ccTLD practice; they don't have control over secondary or 
tertiary domain.

Please don't say what I say include policy issues, which havn't 
relationship with IETF, because you advise that this is a solution, 
but meanwhile, you don't take care of relevant policy issues 
caused by the solution.

Deng xiang


From owner-idn@ops.ietf.org  Mon Oct 29 22:45:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05069
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 22:45:40 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yPgI-000PqR-00
	for idn-data@psg.com; Mon, 29 Oct 2001 19:35:14 -0800
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yPgH-000PqD-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 19:35:13 -0800
Received: from [165.227.249.18] (165-227-249-18.client.dsl.net [165.227.249.18])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f9U3Z8825598;
	Mon, 29 Oct 2001 19:35:08 -0800 (PST)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05101013b803cdb9ed54@[165.227.249.18]>
In-Reply-To: <000d01c160ee$a8936740$cd462b18@mtag1.on.home.com>
References: 
 <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp><01c801c15
 c3d$d9a7ae50$4407e29f@deng> <20011024130954A.yone@nic.ad.jp>
 <024101c15c42$372e1b50$4407e29f@deng>
 <007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio>
 <003f01c15f5c$1d4e5f70$ec1bd9d2@temp>
 <001101c15f64$7eb3b780$1c01000a@jamessonyvaio>
 <016601c15f7d$14325c40$ec1bd9d2@temp>
 <005501c15f80$9dd52a10$1c01000a@jamessonyvaio>
 <000d01c15f81$5573d900$ec1bd9d2@temp>
 <006301c15f82$da0cbe60$1c01000a@jamessonyvaio>
 <001e01c15fae$010900c0$f006738c@ncu.edu.tw>
 <p05101003b801e8c9a90b@[165.227.249.20]>
 <001101c1604b$0a2b2d20$f006738c@ncu.edu.tw>
 <p0510100fb8034e089e46@[165.227.249.18]>
 <000d01c160ee$a8936740$cd462b18@mtag1.on.home.com>
Date: Mon, 29 Oct 2001 19:34:55 -0800
To: idn@ops.ietf.org, jet-member@nic.ad.jp
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] Traditional-simplified, yet again
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 9:56 PM -0500 10/29/01, ben wrote:
>Hi Paul,
>
>>  This discussion has an undercurrent of Chinese vs. non-Chinese, and
>>  that is really ugly. The problems faced in traditional-simplified
>
>>  The people who say "the IETF cannot move forwards with IDN until it
>>  is better for my language than for other people's language" are
>doing
>>  a disservice to everyone, including the people who use their own
>>  language.
>>
>>  --Paul Hoffman, Director
>>  --Internet Mail Consortium
>>
>
>Although I generally like to stay out of discussions on TC<->SC (due
>to my lack of technical knowledge compared to most people in this WG),
>I must correct you on the above.  To blame the Chinese people in this
>WG for delaying the progress of the IETF is so unfair.  How is it
>possible for people to delay the progress of the IETF by simply
>posting up messages and writing drafts?

Ben, that is both absurd and deeply offensive. You purposely put two 
unrelated quotes together and then misquote me. I never said "the 
Chinese people" did anything because I know that "the Chinese people" 
don't all agree on everything or do the same things. There have been 
folks from a number of different countries who have exhibited the 
behavior I was complaining about. Further, all of us together are 
responsible for the advance and delay in this Working Group.

Right now, we are waiting for a draft from a group of people that is 
comprised of both Chinese and non-Chinese folks who have a deeper 
understanding of an important topic that many of the rest of us do. 
The nationality of the people writing that document is mostly 
irrelevant: their knowledge of the topic is what most important here. 
Trying to draw nationalistic lines is not helpful, and is 
particularly silly in a body like the IETF.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Mon Oct 29 22:54:04 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05186
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 22:54:03 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yPkh-000Pzg-00
	for idn-data@psg.com; Mon, 29 Oct 2001 19:39:47 -0800
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yPkg-000PzZ-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 19:39:46 -0800
Received: from xiaodonglee ([159.226.7.70]) by
          whale.cnnic.net.cn (Netscape Messaging Server 4.15) with SMTP id
          GM028Q00.621; Tue, 30 Oct 2001 11:41:14 +0800 
Message-ID: <004d01c160f3$bc9f23f0$4607e29f@xiaodonglee>
Reply-To: "Xiaodong LEE" <lee@cnnic.net.cn>
From: "xiaodong lee" <lee@whale.cnnic.net.cn>
To: "Kenny Huang" <huangk@alum.sinica.edu>, "Dave Crocker" <dhc@dcrocker.net>
Cc: <idn@ops.ietf.org>
References: <3BDD1E94.62F82A5F@ehsco.com> <5.1.0.14.2.20011029172743.035ad008@dcrocker.net>
Subject: Re: [idn] utf-8 "support"
Date: Tue, 30 Oct 2001 11:34:09 +0800
Organization: CNIC-ICT
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.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
X-MIME-Autoconverted: from base64 to 8bit by ietf.org id WAA05186

Dear Dave:
I think UTF-8 is a good solution too.  Though it is not a feasible plan yet now.
In the future, we should not alaways use complex alogrithm to support IDN.
Xiaodong Lee

----- Original Message ----- 
From: "Dave Crocker" <dhc@dcrocker.net>
To: "Kenny Huang" <huangk@alum.sinica.edu>
Cc: <idn@ops.ietf.org>
Sent: Tuesday, October 30, 2001 9:31 AM
Subject: [idn] utf-8 "support"


> At 08:55 PM 10/27/2001 +0800, Kenny Huang wrote:
> >I support UTF-8 based advanced DNS infrastructure, and support ACE
> 
> Kenny,
> 
> Thank you.  However support for a concept, such as "UTF-8", is not really a 
> factor in this topic.  We are trying to make progress of concrete 
> specifications.
> 
> The concerns now are:
> 
>          -  what is feasible for transition with the existing DNS installed 
> base,
> 
>          -  what specifications are essentially complete, and
> 
>          -  what specifications have demonstrated good working group rough 
> consensus.
> 
> 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 Oct 29 22:55:41 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05198
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 22:55:39 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yPoS-00009o-00
	for idn-data@psg.com; Mon, 29 Oct 2001 19:43:40 -0800
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yPoQ-00009c-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 19:43:39 -0800
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 6AEF4FFC15; Tue, 30 Oct 2001 11:43:45 +0800 (SGT)
Message-ID: <003c01c160f5$0acc74f0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "xiang deng" <deng@cnnic.net.cn>,
        =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        "Paul Hoffman / IMC" <phoffman@imc.org>, <idn@ops.ietf.org>,
        "Martin Duerst" <duerst@w3.org>
Cc: <klensin@jck.com>
References: <E15xrqq-000Adc-00@psg.com><008901c16022$74b7c640$4407e29f@deng><p0510100db8027d203d26@[165.227.249.20]> <1180657.1004337022@localhost> <006d01c16061$55b60150$4407e29f@deng> <019b01c1606b$83801120$dd00a8c0@jamessonyvaio> <008b01c160eb$cfc834b0$4407e29f@deng>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Tue, 30 Oct 2001 11:43:30 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Since I am going to reply this with a registration side policy, some of
the points I raise is non-technical in nature. Take note.

> (1)2^n problem. To ensure a Chinese domain name both TC/SC to
> be correctly resolved, 2^n records must be registered and all
> the records point to one IP address (Note: n indicates the total

In practice, you only need to add 1 to 4 records (or as many as
required) into the DNS, the most common variant of the name. The
registrant could choose which the n.

The registry could forbid the registration of other 2^n possible
(including TSTTS, TSSST, TSTSS etc which is not likely to occur).

> number of registrations will explode. In order to protect their
> domain name, users must register 2^n domain names, registration
> cost will increase rapidly, and this is obviously not practical.

registration cost is not a point of discussion - it is a business issue.
If C offers TC/SC protection vs another V which doesn't, the market
force will decide who will wins out.

> (2)The lower level delegation domain name servers may adopt a
> different domain administrative policy or they simply don't support
> multiple records registration, therefore the consistency of TC/SC
> domain names cannot be ensured.

Then that is the problem on the lower delegation. If the owner of the
domain names decide not deal with the proper handling of his delegation
and causing user confusion, then it is his/her choice. Eventually, he is
going to suffer from the consequences.

> (3)How to ensure that the 2^n records are to be owned by a single
> registered user? This is also an inevitable question, if this cannot
> be ensured, there are will be a large number of domain name
> disputationes.

By proper designing your database to handle this. On DNS, use
CNAME/DNAME as neccessary. This is basically not a technical problem.

> Different registration authorities has different
> registration policies, even if the registration policies can prevent
> gTLD and ccTLD practice; they don't have control over secondary or
> tertiary domain.

Do you mean a ccTLD C should have a control over the policy over another
gTLD V or another ccTLD J?

> 2.Adopting TC only records and SC only records solution - analysis

I did not answer any of the problem raise here because I think no one
here thinks you should only do TC only or SC only.

-James Seg




From owner-idn@ops.ietf.org  Mon Oct 29 23:02:43 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05255
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 23:02:42 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yPs7-0000In-00
	for idn-data@psg.com; Mon, 29 Oct 2001 19:47:27 -0800
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yPs6-0000Ih-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 19:47:26 -0800
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id MAA30506;
	Tue, 30 Oct 2001 12:42:26 +0900
Message-ID: <011d01c160f5$0314bfb0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>,
        "Yves Arrouye" <yves@realnames.com>, <idn@ops.ietf.org>
References: <7FC3066C236FD511BC5900508BAC86FE4D7E46@trestles.internal.realnames.com> <3BDE03E6.9476E5A3@zetnet.co.uk>
Subject: Re: [idn] Re: stringprep and unassigned code points
Date: Tue, 30 Oct 2001 12:43:17 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id XAA05255


----- Original Message ----- 
From: "David Hopwood" <david.hopwood@zetnet.co.uk>
To: "Yves Arrouye" <yves@realnames.com>; <idn@ops.ietf.org>
Sent: Tuesday, October 30, 2001 10:35 AM
Subject: Re: [idn] Re: stringprep and unassigned code points


> -----BEGIN PGP SIGNED MESSAGE-----
> 
> Yves Arrouye wrote:
> > Honestly, I do not see any other way than to upgrade everybody to a newer
> > Nameprep when the mapping tables change for new code points.
> 
> New unicameral scripts (without case distinctions), that have no NFC/NFKC
> mappings can be supported without any changes to nameprep. That leaves
> bicameral scripts, and scripts that have NFC mappings, i.e. they have
> both precomposed and decomposed characters (compatibility mappings for
> new scripts are extremely unlikely). In order for those scripts to
> be used at all, 

  An old nameprep browser suggests a (newly added) TAGALOG web link in a web page
    <a href=http://<native tagalog>.com/>Hello, world!</a>
  and the end user clicks the links.

  In that case, the old platform does not need  TAGALOG IME and font sets to make
  a query. Should old nameprep webbrowsers encode unassigned code points 
  (to be tagalog) to ACE labels without tagalog-related nameprep mappings ?

  There will be many offline/non-interactive/in-house nameprep applications that 
   fall into the same category as this webpage input mode of webbrowser.

  Soobok Lee

> the client's operating system will need to be updated to
> support a new version of Unicode. If the OS provides case folding and
> normalisation functions [*], then old applications calling the new
> functions will work fine. Even if the OS doesn't provide all of the
> needed functionality, it could do in new versions, and an IDN library
> could use the OS whereever possible, falling back to its own
> implementation otherwise.
> 
> Of course this requires that nameprep is defined strictly in terms of
> standard Unicode mappings and properties. That is possible if we use NFC,
> and define the disallowed characters in terms of Unicode character
> properties (note that no "additional mappings" are needed to make
> casefold o NFC idempotent, I think; I've recently asked on the Unicode
> mailing list to confirm that).
> 
> [*] Win32 does for NFC normalisation, I'm not sure about case folding.
> 
> - -- 
> 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
> 
> iQEVAwUBO94D0TkCAxeYt5gVAQF6ygf/TAc63TwyAyNFZIv3kPS/m2Y+2+k8qhwf
> aZz1uzodGofF6kXamHOMT4h/JzwH8luKm3mJP7dJ8dPlMoN+ZFVQqSmNULYDknND
> Cy7f0H/W6usAKNOBCu+MqNKkD+S7sCdUz8kWFVftykmyM/aaKyK4y0ahvtvMjLq1
> EQMpkCOZe2q2q/OW7x9dprvV1JxsxL31NP7LysYdOzpg0S6jY9uehBWH5TM1+Zko
> 3SD0GC4vjiH9XHYDp+JQ0bBY8dMLR3Y8EKxCZUTnrRpM6Ygjn6X3xi5q95UWFiic
> gvl97efDZ1EZWz03Ns1T7oRwEYBfMD3oaLuhsqz+4G5c9YAHNMIExQ==
> =PDXw
> -----END PGP SIGNATURE-----
> 




From owner-idn@ops.ietf.org  Mon Oct 29 23:09:16 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05306
	for <idn-archive@lists.ietf.org>; Mon, 29 Oct 2001 23:09:16 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yPxM-0000UF-00
	for idn-data@psg.com; Mon, 29 Oct 2001 19:52:52 -0800
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yPxM-0000U8-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 19:52:52 -0800
Received: from [165.227.249.18] (165-227-249-18.client.dsl.net [165.227.249.18])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f9U3ql825929
	for <idn@ops.ietf.org>; Mon, 29 Oct 2001 19:52:47 -0800 (PST)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05101014b803d0759182@[165.227.249.18]>
In-Reply-To: <008b01c160eb$cfc834b0$4407e29f@deng>
References: 
 <E15xrqq-000Adc-00@psg.com><008901c16022$74b7c640$4407e29f@deng><p0510100d
 b8027d203d26@[165.227.249.20]> <1180657.1004337022@localhost>
 <006d01c16061$55b60150$4407e29f@deng>
 <019b01c1606b$83801120$dd00a8c0@jamessonyvaio>
 <008b01c160eb$cfc834b0$4407e29f@deng>
Date: Mon, 29 Oct 2001 19:49:10 -0800
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] An ignorant question about TC<-> SC
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Deng:

Thank you for the two analyses. This is a good basis for discussion 
for the users of many languages, not just Chinese.

At 10:37 AM +0800 10/30/01, xiang deng wrote:
>1.Adopting multiple records solution - analysis
>If a multiple records solution are adopted, and all possible
>TC/SC forms of a single Chinese domain name are added into a
>zone file as the different forms of one identical domain name,
>then this approach has the following weakness:

Why did you assume that all forms must be added? I thought it was 
generally agreed that a name that consisted of, say, four traditional 
characters would probably only have two forms (all-traditional, and 
all-simplified). A small number of names would have one or two more 
(maybe TTTS or STSS), but that the number would almost always be very 
much less that 2^n.

>(1)2^n problem. To ensure a Chinese domain name both TC/SC to
>be correctly resolved, 2^n records must be registered and all
>the records point to one IP address (Note: n indicates the total
>number of the TC/SC variants of the domain name). Chinese has
>over 4,000 variants, and most of them are in common use, a single
>ordinary domain name may have dozens of, hundreds of even thousands
>of TC/SC records, if all of them are to be registered, then total
>number of registrations will explode. In order to protect their
>domain name, users must register 2^n domain names, registration
>cost will increase rapidly, and this is obviously not practical.

Why is there any cost at all? If there is general agreement that all 
sensible spellings should be registered at once, why should a 
registry be able to charge by the record instead of by the name?

>(2)The lower level delegation domain name servers may adopt a
>different domain administrative policy or they simply don't support
>multiple records registration, therefore the consistency of TC/SC
>domain names cannot be ensured.

Exactly right. This is precisely the same problem faced in every 
language that has spelling variants or meaning variants. In fact, it 
also appears when company A buys company B and they try to run their 
domains in parallel.

>(3)How to ensure that the 2^n records are to be owned by a single
>registered user? This is also an inevitable question, if this cannot
>be ensured, there are will be a large number of domain name
>disputationes. Different registration authorities has different
>registration policies, even if the registration policies can prevent
>gTLD and ccTLD practice; they don't have control over secondary or
>tertiary domain.

Indeed. A single registry can ensure that all spellings of a name are 
held together in the one zone, but they cannot assure anything in a 
lower zone, and cannot assure anything in a different registry. 
Again, these problems are the same for almost every language.

>2.Adopting TC only records and SC only records solution - analysis
>TC only records and SC only records solution has the following weakness:
>(1)Not applicable to Hong Kong and Macao where both TC and SC are used,
>simplified Chinese is not used at all in Taiwan, TC only or SC only
>records cannot meet the requirements of the users.
>
>(2)This approach cannot solve technically delegation domain problems either.
>
>(3) How to ensure that the two kinds of records are to be owned by a
>single registered user? This is also an inevitable question, if this
>cannot be ensured, there are will be a large number of domain name
>disputationes. Different registration authorities has different
>registration policies, even if the registration policies can prevent
>gTLD and ccTLD practice; they don't have control over secondary or
>tertiary domain.

This sounds exactly right, and problems 2 and 3 match those above.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Tue Oct 30 00:12:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06098
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 00:12:59 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yQr6-0002K5-00
	for idn-data@psg.com; Mon, 29 Oct 2001 20:50:28 -0800
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yQr5-0002Jy-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 20:50:27 -0800
Received: from zetnet.co.uk (man-s374.dialup.zetnet.co.uk [194.247.45.245])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f9U4oEB22354;
	Tue, 30 Oct 2001 04:50:14 GMT
Message-ID: <3BDE3219.E665F43@zetnet.co.uk>
Date: Tue, 30 Oct 2001 04:52:41 +0000
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] Re: stringprep and unassigned code points
References: <7FC3066C236FD511BC5900508BAC86FE4D7E46@trestles.internal.realnames.com> <3BDE03E6.9476E5A3@zetnet.co.uk> <011d01c160f5$0314bfb0$ec1bd9d2@temp>
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-----

Soobok Lee wrote:
> David Hopwood wrote:
> > Yves Arrouye wrote:
> > > Honestly, I do not see any other way than to upgrade everybody to a newer
> > > Nameprep when the mapping tables change for new code points.
> >
> > New unicameral scripts (without case distinctions), that have no NFC/NFKC
> > mappings can be supported without any changes to nameprep. That leaves
> > bicameral scripts, and scripts that have NFC mappings, i.e. they have
> > both precomposed and decomposed characters (compatibility mappings for
> > new scripts are extremely unlikely). In order for those scripts to
> > be used at all,
> 
>   An old nameprep browser suggests a (newly added) TAGALOG

Tagalog is a unicameral script with no NFC/NFKC mappings, so there's no
point in using it as an example. That also applies to the other 3 scripts
added in Unicode 3.2.

>   web link in a
>   web page <a href=http://<native tagalog>.com/>Hello, world!</a>
>   and the end user clicks the links.

(BTW, strictly speaking neither RFC 2396 nor HTML 4.x allow non-ASCII here.
There wouldn't be any problem with relaxing this restriction, but I just
thought I'd point it out.)

>   In that case, the old platform does not need TAGALOG IME and font sets
>   to make a query.

However, the platform on which the HTML file is created does. Therefore
whatever process creates the file can apply nameprep to the hostname, and
the rest of the argument in my previous post applies to that.

Of course, the HTML file might be created by a general-purpose text editor,
or by an old HTML generator that doesn't conform to the IDN specifications.
However, that doesn't present any great problem: HTML files are already
required to be NFC-normalised, and compatibility mappings are not an issue
for new scripts, so all that remains is to make sure that the hostname is
case folded. In practice, that just means not typing it in uppercase.

>   There will be many offline/non-interactive/in-house nameprep applications
>   that fall into the same category as this webpage input mode of webbrowser.

In all cases, the process that encodes the hostname is responsible for
applying nameprep, not the process that makes the query.

- -- 
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

iQEVAwUBO94xzzkCAxeYt5gVAQEtkQf/eT02v1Z+ht6bNJge3+LyHWj4sf8lIAeu
s8bAkwH1NksOBIy6HSYLgaxJOiJFoIAGNyKLsH/ZW5eyOmCdWl0xWGm3+WSz2gW8
OCgLiiGl0T9BuNl+UiXnodcXy27dE5A9leeH2wFHh1EMF0riCGeQPLWaJMDALt5R
TUKsNLbktRguJEep7Dun/2dJ3DSDCSJPs4gYmUtYJQzReB0XvYkImyJxneU9L5U7
waQnnWToSC/j/6kM8GX7ZlZy/7eldVZPqalr74PxlCgBZvGIze5Lnt9FE09CuiMr
69qVJYvyJ53buyRp54MFMKvaoHYDqUbfblYyLCYLi8F4BU1ekyOxoA==
=6dgG
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Tue Oct 30 00:26:15 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06347
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 00:26:14 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yR7Z-0002mm-00
	for idn-data@psg.com; Mon, 29 Oct 2001 21:07:29 -0800
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yR7Y-0002mg-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 21:07:29 -0800
Received: from deng ([159.226.7.68]) by whale.cnnic.net.cn
          (Netscape Messaging Server 4.15) with SMTP id GM06AW00.O4Y; Tue,
          30 Oct 2001 13:08:56 +0800 
Message-ID: <00f301c160ff$a9a367f0$4407e29f@deng>
From: "xiang deng" <deng@cnnic.net.cn>
To: <idn@ops.ietf.org>, "Paul Hoffman / IMC" <phoffman@imc.org>
References: <E15xrqq-000Adc-00@psg.com><008901c16022$74b7c640$4407e29f@deng><p0510100db8027d203d26@[165.227.249.20]> <1180657.1004337022@localhost><006d01c16061$55b60150$4407e29f@deng><019b01c1606b$83801120$dd00a8c0@jamessonyvaio><008b01c160eb$cfc834b0$4407e29f@deng> <p05101014b803d0759182@[165.227.249.18]>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Tue, 30 Oct 2001 12:59:32 +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 AAA06347

Paul:

I'm sure you know it's a problem of IDN in fact, it's not created.
To refuse the existence of the problem will not help to solve it.

It isn't ASCII vs Chinese characters. IDN provide the platform for
all scirpts include ASCII and Chinese character and others. When 
IDN is created, it belongs to the whole world, anyone have selfish
motive haven't the qualification to say I'M IDN MEMBER.

IDN is important for all of us, we hope the dream of IDN to be true.
In my opinions, the right way is To dig the problem and Solve it. 

Deng xiang      and other comments below:

On Tuesday, October 30, 2001 11:49 AM, Paul Hoffman/IMC wrote:
> At 10:37 AM +0800 10/30/01, xiang deng wrote:
> >1.Adopting multiple records solution - analysis
> >If a multiple records solution are adopted, and all possible
> >TC/SC forms of a single Chinese domain name are added into a
> >zone file as the different forms of one identical domain name,
> >then this approach has the following weakness:
> 
> Why did you assume that all forms must be added? I thought it was 
> generally agreed that a name that consisted of, say, four traditional 
> characters would probably only have two forms (all-traditional, and 
> all-simplified). A small number of names would have one or two more 
> (maybe TTTS or STSS), but that the number would almost always be very 
> much less that 2^n.

n indicates the total number of the TC/SC variants of the domain name.
if a record named ABCD have 2 variants ( B->b, C->c),
there have 2*2=4 records:
ABCD  ABcD  AbCD  AbCD
So all 4 forms must be added into a zone file.
 
> >(1)2^n problem. To ensure a Chinese domain name both TC/SC to
> >be correctly resolved, 2^n records must be registered and all
> >the records point to one IP address (Note: n indicates the total
> >number of the TC/SC variants of the domain name). Chinese has
> >over 4,000 variants, and most of them are in common use, a single
> >ordinary domain name may have dozens of, hundreds of even thousands
> >of TC/SC records, if all of them are to be registered, then total
> >number of registrations will explode. In order to protect their
> >domain name, users must register 2^n domain names, registration
> >cost will increase rapidly, and this is obviously not practical.
> 
> Why is there any cost at all? If there is general agreement that all 
> sensible spellings should be registered at once, why should a 
> registry be able to charge by the record instead of by the name?

TC/SC is not spelling issue, TC/SC is same in anywhere, they just
are different in structural form.
 
> >(2)The lower level delegation domain name servers may adopt a
> >different domain administrative policy or they simply don't support
> >multiple records registration, therefore the consistency of TC/SC
> >domain names cannot be ensured.
> 
> Exactly right. This is precisely the same problem faced in every 
> language that has spelling variants or meaning variants. In fact, it 
> also appears when company A buys company B and they try to run their 
> domains in parallel.

TC/SC is not spelling variants and is not meaning variants.
My friend, my English is poor, please don't embarrass me.
 
> >(3)How to ensure that the 2^n records are to be owned by a single
> >registered user? This is also an inevitable question, if this cannot
> >be ensured, there are will be a large number of domain name
> >disputationes. Different registration authorities has different
> >registration policies, even if the registration policies can prevent
> >gTLD and ccTLD practice; they don't have control over secondary or
> >tertiary domain.
> 
> Indeed. A single registry can ensure that all spellings of a name are 
> held together in the one zone, but they cannot assure anything in a 
> lower zone, and cannot assure anything in a different registry. 
> Again, these problems are the same for almost every language.

Yes, there are about 2000 pairs of TC/SC. 
every language has the same situation?
 
> >2.Adopting TC only records and SC only records solution - analysis
> >TC only records and SC only records solution has the following weakness:
> >(1)Not applicable to Hong Kong and Macao where both TC and SC are used,
> >simplified Chinese is not used at all in Taiwan, TC only or SC only
> >records cannot meet the requirements of the users.
> >
> >(2)This approach cannot solve technically delegation domain problems either.
> >
> >(3) How to ensure that the two kinds of records are to be owned by a
> >single registered user? This is also an inevitable question, if this
> >cannot be ensured, there are will be a large number of domain name
> >disputationes. Different registration authorities has different
> >registration policies, even if the registration policies can prevent
> >gTLD and ccTLD practice; they don't have control over secondary or
> >tertiary domain.
> 
> This sounds exactly right, and problems 2 and 3 match those above.

thanks for your comments.
Deng xiang



From owner-idn@ops.ietf.org  Tue Oct 30 00:38:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06426
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 00:38:52 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yRPH-0003L5-00
	for idn-data@psg.com; Mon, 29 Oct 2001 21:25:47 -0800
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yRPG-0003Ky-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 21:25:46 -0800
Received: from cs881964a ([24.43.70.205]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Mon, 29 Oct 2001 21:39:06 -0800
Message-ID: <002801c16104$a2c27160$cd462b18@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: <idn@ops.ietf.org>, <jet-member@nic.ad.jp>,
        "Paul Hoffman / IMC" <phoffman@imc.org>
References:  <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp><01c801c15 c3d$d9a7ae50$4407e29f@deng> <20011024130954A.yone@nic.ad.jp> <024101c15c42$372e1b50$4407e29f@deng> <007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio> <003f01c15f5c$1d4e5f70$ec1bd9d2@temp> <001101c15f64$7eb3b780$1c01000a@jamessonyvaio> <016601c15f7d$14325c40$ec1bd9d2@temp> <005501c15f80$9dd52a10$1c01000a@jamessonyvaio> <000d01c15f81$5573d900$ec1bd9d2@temp> <006301c15f82$da0cbe60$1c01000a@jamessonyvaio> <001e01c15fae$010900c0$f006738c@ncu.edu.tw> <p05101003b801e8c9a90b@[165.227.249.20]> <001101c1604b$0a2b2d20$f006738c@ncu.edu.tw> <p0510100fb8034e089e46@[165.227.249.18]> <000d01c160ee$a8936740$cd462b18@mtag1.on.home.com> <p05101013b803cdb9ed54@[165.227.249.18]>
Subject: Re: [idn] Traditional-simplified, yet again
Date: Tue, 30 Oct 2001 00:34:49 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Paul,

I did *not purposely* misquote you.  I truly thought they were related
so I did not think there was a need to forward the entire quote-
especially since everyone has *already got* a copy of the original.
It was important for me that you clarify what you mean- thanks for
that.

However, I still don't understand how anyone (whether they are Chinese
or non-Chinese) can delay this process by posting up messages and
writing drafts?

Thanks,
Ben




----- Original Message -----
From: "Paul Hoffman / IMC" <phoffman@imc.org>
To: <idn@ops.ietf.org>; <jet-member@nic.ad.jp>
Sent: Monday, October 29, 2001 10:34 PM
Subject: Re: [idn] Traditional-simplified, yet again


> At 9:56 PM -0500 10/29/01, ben wrote:
> >Hi Paul,
> >
> >>  This discussion has an undercurrent of Chinese vs. non-Chinese,
and
> >>  that is really ugly. The problems faced in
traditional-simplified
> >
> >>  The people who say "the IETF cannot move forwards with IDN until
it
> >>  is better for my language than for other people's language" are
> >doing
> >>  a disservice to everyone, including the people who use their own
> >>  language.
> >>
> >>  --Paul Hoffman, Director
> >>  --Internet Mail Consortium
> >>
> >
> >Although I generally like to stay out of discussions on TC<->SC
(due
> >to my lack of technical knowledge compared to most people in this
WG),
> >I must correct you on the above.  To blame the Chinese people in
this
> >WG for delaying the progress of the IETF is so unfair.  How is it
> >possible for people to delay the progress of the IETF by simply
> >posting up messages and writing drafts?
>
> Ben, that is both absurd and deeply offensive. You purposely put two
> unrelated quotes together and then misquote me. I never said "the
> Chinese people" did anything because I know that "the Chinese
people"
> don't all agree on everything or do the same things. There have been
> folks from a number of different countries who have exhibited the
> behavior I was complaining about. Further, all of us together are
> responsible for the advance and delay in this Working Group.
>
> Right now, we are waiting for a draft from a group of people that is
> comprised of both Chinese and non-Chinese folks who have a deeper
> understanding of an important topic that many of the rest of us do.
> The nationality of the people writing that document is mostly
> irrelevant: their knowledge of the topic is what most important
here.
> Trying to draw nationalistic lines is not helpful, and is
> particularly silly in a body like the IETF.
>
> --Paul Hoffman, Director
> --Internet Mail Consortium
>
>




From owner-idn@ops.ietf.org  Tue Oct 30 00:40:48 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06443
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 00:40:48 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yROk-0003JM-00
	for idn-data@psg.com; Mon, 29 Oct 2001 21:25:14 -0800
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.33 #1)
	id 15yROj-0003JG-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 21:25:13 -0800
Received: (qmail 14534 invoked by uid 104); 30 Oct 2001 05:25:12 -0000
Received: from yves@realnames.com by friendly.realnames.com with qmail-scanner-0.96 (. Clean. Processed in 4.7564 secs); 30 Oct 2001 05:25:12 -0000
Received: from heaven.internal.realnames.com (10.1.5.39)
  by friendly.realnames.com with SMTP; 30 Oct 2001 05:25:06 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:3456]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <25221@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Mon, 29 Oct 2001 9:16:33 PM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2653.19)
	id <V3D1GP5C>; Mon, 29 Oct 2001 21:19:18 -0800
Message-ID: <7FC3066C236FD511BC5900508BAC86FE4D7E60@trestles.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: idn@ops.ietf.org
Subject: RE: [idn] Re: stringprep and unassigned code points
Date: Mon, 29 Oct 2001 21:15:38 -0800
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

Good point about the "no typing in uppercase" unless we consider other
mappings (e.g. deletions).

> In all cases, the process that encodes the hostname is responsible for
> applying nameprep, not the process that makes the query.

Hmmm. Is that true? And can it be enforced? It is interesting that you
consider that when one types a URL in an editor, the editor is the one
"encoding" the host name. But paste the same string in the browser, and  is
the browser then re-"encoding" it? Most likely.

I think that at the end of the day, while we agree that adding more code
points to Unicode will break some applications that use a Nameprep released
before the code points were assigned, it is also true that it is likely that
IDN will become an OS-based service and that it will be upgraded soon
enough. I can definitely imaging Microsoft shipping updates to a
Nameprep/Stringprep/IDN library as part as language support (e.g. you get
the support for the new language/script, you get the rest with it). But it
is still possible to generate perfectly legal Nameprepped data from an older
standard that cannot be matched agains the same data Nameprepped from a more
recent revision. 

YA



From owner-idn@ops.ietf.org  Tue Oct 30 00:52:42 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06501
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 00:52:41 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yRXo-0003bz-00
	for idn-data@psg.com; Mon, 29 Oct 2001 21:34:36 -0800
Received: from irwell.zetnet.co.uk ([194.247.47.48] helo=zetnet.co.uk)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yRXn-0003bt-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 21:34:35 -0800
Received: from zetnet.co.uk (man-s374.dialup.zetnet.co.uk [194.247.45.245])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f9U5YTB26363;
	Tue, 30 Oct 2001 05:34:29 GMT
Message-ID: <3BDE3C79.B09C0DD0@zetnet.co.uk>
Date: Tue, 30 Oct 2001 05:36:57 +0000
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 <dhc@dcrocker.net>, idn@ops.ietf.org
Subject: Re: [idn] iDNS re-chartering proposal, take 2
References: <5.1.0.14.2.20011027084819.03d3b6c0@brandenburg.com>
	 <5.1.0.14.2.20011028145534.03d1f008@dcrocker.net>
	 <5.1.0.14.2.20011028152132.01c501c0@dcrocker.net>
	 <5.1.0.14.2.20011028191806.03cd6468@dcrocker.net> <5.1.0.14.2.20011029074912.05712110@dcrocker.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-----

Dave Crocker wrote:
> Eric A. Hall wrote:
> >I have said several times quite clearly that ACE is necessary as a
> >backwards compatibility mode for legacy applications.
> 
> Doing one specific piece of work, now, and deferring pursuit of an
> additional specification, for additional changes to the DNS, is standard
> IETF practise.

You're assuming that a hybrid design will have completely independent
ACE and non-ACE components, and that deploying IDNA first will not cause
any problems for such a design. On the contrary, I think it is pretty
clear that this would cramp the possible design space of the non-ACE
component quite significantly.

- -- 
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

iQEVAwUBO948YTkCAxeYt5gVAQFhnggAjIEFHBjaT03y5Xyv2oHcJ/lprNmxvbbN
TXcIvigtlJg6mMRD0XdinVWIxCx63Yly3D9klcp4DkLlIIaHQ7qrizTKiyfjoj61
4pcp0I2Azg75F9/mR2Kjds6oi6ktXFz56q3U91QbTJal1D5ccqyqbUswUIA8rSQt
+St43Fu0NQDezMQP4TH5BNTH6VSg5HvqR5tX9AocgSu89uCkhJtJn0cTos65t83F
+eshNMlIeRhNx9UcoHw0p4SWA0vkvh5tcSyHRhJkCQ6rN6s68HWYOnTauZrFNBCv
9L8/xWJA8I1r5zhDnJmJFQSNquQgd6U1diUfcwCXS5+pxAesSrs39Q==
=zxtn
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Tue Oct 30 01:13:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07407
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 01:13:57 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yRqj-0004Dt-00
	for idn-data@psg.com; Mon, 29 Oct 2001 21:54:09 -0800
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yRqi-0004Dn-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 21:54:08 -0800
Received: from bbprime.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 VAA28961;
	Mon, 29 Oct 2001 21:53:04 -0800
Message-Id: <5.1.0.14.2.20011029214457.0385d498@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 29 Oct 2001 21:53:01 -0800
To: David Hopwood <david.hopwood@zetnet.co.uk>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] iDNS re-chartering proposal, take 2
Cc: idn@ops.ietf.org
In-Reply-To: <3BDE3C79.B09C0DD0@zetnet.co.uk>
References: <5.1.0.14.2.20011027084819.03d3b6c0@brandenburg.com>
 <5.1.0.14.2.20011028145534.03d1f008@dcrocker.net>
 <5.1.0.14.2.20011028152132.01c501c0@dcrocker.net>
 <5.1.0.14.2.20011028191806.03cd6468@dcrocker.net>
 <5.1.0.14.2.20011029074912.05712110@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 05:36 AM 10/30/2001 +0000, David Hopwood wrote:
>You're assuming that a hybrid design will have completely independent
>ACE and non-ACE components, and that deploying IDNA first will not cause
>any problems for such a design.

Two years for this working group.  No complete specification for a "hybrid" 
solution.

12 years of IETF work.  Every effort at "hybrid" solutions, particularly 
when they are done simultaneously, has gone badly.

The math is compelling.


>On the contrary, I think it is pretty clear that this would cramp the 
>possible design space of the non-ACE component quite significantly.

By extension you are arguing that we should never make any decisions now, 
because we might close off choices for some future (or separate) work?

We appear to be stuck on a theme of confusing engineering with science.

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 Oct 30 01:22:44 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08416
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 01:22:44 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yRyM-0004T5-00
	for idn-data@psg.com; Mon, 29 Oct 2001 22:02:02 -0800
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yRyL-0004Sy-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 22:02:01 -0800
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 HAA19554;
	Tue, 30 Oct 2001 07:01:55 +0100 (MET)
Date: Tue, 30 Oct 2001 07:01:55 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: ben <ben@cc-www.com>, idn@ops.ietf.org,
        "Paul Hoffman / IMC" <phoffman@imc.org>
cc: jet-member@nic.ad.jp
Subject: Re: [idn] Traditional-simplified, yet again
Message-ID: <4494016.1004425315@[0.0.0.0]>
In-Reply-To: <000d01c160ee$a8936740$cd462b18@mtag1.on.home.com>
References:  <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp>
 <01c801c15 c3d$d9a7ae50$4407e29f@deng> <20011024130954A.yone@nic.ad.jp>
 <024101c15c42$372e1b50$4407e29f@deng>
 <007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio>
 <003f01c15f5c$1d4e5f70$ec1bd9d2@temp>
 <001101c15f64$7eb3b780$1c01000a@jamessonyvaio>
 <016601c15f7d$14325c40$ec1bd9d2@temp>
 <005501c15f80$9dd52a10$1c01000a@jamessonyvaio>
 <000d01c15f81$5573d900$ec1bd9d2@temp>
 <006301c15f82$da0cbe60$1c01000a@jamessonyvaio>
 <001e01c15fae$010900c0$f006738c@ncu.edu.tw>
 <p05101003b801e8c9a90b@[165.227.249.20]>
 <001101c1604b$0a2b2d20$f006738c@ncu.edu.tw>
 <p0510100fb8034e089e46@[165.227.249.18]>
 <000d01c160ee$a8936740$cd462b18@mtag1.on.home.com>
X-Mailer: Mulberry/2.1.1 (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-10-29 21.56 -0500 ben <ben@cc-www.com> wrote:

> How is it
> possible for people to delay the progress of the IETF by simply
> posting up messages and writing drafts?

By

(a) Talking about an important issue
(b) People tell the author what part of that issue can be solved
    in the DNS, and how, and point to other solutions for
    the other part(s) of the issue
(c) Talking about the important issue again, with no changes
(d) People tell the author again that things have to be changed
    because the issue can not be solved in DNS
(e) Go to (c)

Myself, I have with the CNNIC people now passed point (e) four(!) times,
and I start to get tired on this. The proposals from CNNIC have not changed
at all since (a), and conversations have occurred on the IDN mailing list,
in private conversations (one is going on at the moment) and in face to
face meetings.

Further, at second pass of (e), myself and others talked with the
authorities on Chinese scripts we know to verify that we were not stupid or
misunderstood something. _ALL_ of these said that it was the CNNIC people
which had not understood the complexity of the problem. Further, the
Unicode Consortium have already been through the SC/TC problem once, and to
explicitly state this fact, the Unicode Consortium explicitly sent a liason
statement to the IETF stating this fact.

When all of these things was presented to the CNNIC people, the rough
consensus in the wg on what to do, the information from external sources,
and the liason statement from Unicode Consortium, the response is:

- The wg don't understand the problem
- The external sources don't understand the problem
- Unicode Consortium don't work on these issues
- ISO have nothing to do with Chinese Characters

And we go back to (c) again from (e).

Sorry, but this is absolutely NOTHING but a delaying process from ignorant
people.

Note that I am nowhere above saying that SC/TC is a problem. Just like
other equality (define the word equality whatever way you want) when you
use more than one script -- and in some cases even with one.

I am as you can see extremely tired on this wg not making process just
because one group of people is blocking the discussions.

This wg is not making any progress.

Absolutely NOTHING has been changed in the proposals which are on the table
the last couple of months, and as in all processes, we _could_ have been
able to discuss things which we still have to polish here and there. For
example, the part of the SC/TC issues which have to do with mappings from
local charsets to Unicode, use of Unicode in other protocol elements than
domain names etc.

So, at the moment it is CNNIC which effectively see that the world can not
use Chinese Characters in the DNS.

     paf




From owner-idn@ops.ietf.org  Tue Oct 30 01:26:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08871
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 01:26:02 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yS5S-0004hU-00
	for idn-data@psg.com; Mon, 29 Oct 2001 22:09:22 -0800
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yS5R-0004gr-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 22:09:21 -0800
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 HAA19715;
	Tue, 30 Oct 2001 07:04:11 +0100 (MET)
Date: Tue, 30 Oct 2001 07:04:11 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Yves Arrouye <yves@realnames.com>, idn@ops.ietf.org
Subject: RE: [idn] Re: stringprep and unassigned code points
Message-ID: <4502182.1004425451@[0.0.0.0]>
In-Reply-To: <7FC3066C236FD511BC5900508BAC86FE4D7E60@trestles.internal.realnames.com>
References:  <7FC3066C236FD511BC5900508BAC86FE4D7E60@trestles.internal.realna
 mes.com>
X-Mailer: Mulberry/2.1.1 (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-10-29 21.15 -0800 Yves Arrouye <yves@realnames.com> wrote:

> But it
> is still possible to generate perfectly legal Nameprepped data from an
> older standard that cannot be matched agains the same data Nameprepped
> from a more recent revision. 

Wrong. See the specification of stringprep, section 6.

   paf




From owner-idn@ops.ietf.org  Tue Oct 30 01:45:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA11579
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 01:45:59 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ySOM-0005M3-00
	for idn-data@psg.com; Mon, 29 Oct 2001 22:28:54 -0800
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ySOL-0005Lx-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 22:28:53 -0800
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 HAA21848;
	Tue, 30 Oct 2001 07:28:47 +0100 (MET)
Date: Tue, 30 Oct 2001 07:28:47 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        ben <ben@cc-www.com>, idn@ops.ietf.org,
        "Paul Hoffman / IMC" <phoffman@imc.org>
cc: jet-member@nic.ad.jp
Subject: Re: [idn] Traditional-simplified, yet again
Message-ID: <4590745.1004426927@[0.0.0.0]>
In-Reply-To: <4494016.1004425315@[0.0.0.0]>
References:  <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp>
 <01c801c15 c3d$d9a7ae50$4407e29f@deng>
 <20011024130954A.yone@nic.ad.jp><024101c15c42$372e1b50$4407e29f@deng>
 <007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio>
 <003f01c15f5c$1d4e5f70$ec1bd9d2@temp>
 <001101c15f64$7eb3b780$1c01000a@jamessonyvaio>
 <016601c15f7d$14325c40$ec1bd9d2@temp>
 <005501c15f80$9dd52a10$1c01000a@jamessonyvaio>
 <000d01c15f81$5573d900$ec1bd9d2@temp>
 <006301c15f82$da0cbe60$1c01000a@jamessonyvaio>
 <001e01c15fae$010900c0$f006738c@ncu.edu.tw>
 <p05101003b801e8c9a90b@[165.227.249.20]>
 <001101c1604b$0a2b2d20$f006738c@ncu.edu.tw>
 <p0510100fb8034e089e46@[165.227.249.18]>
 <000d01c160ee$a8936740$cd462b18@mtag1.on.home.com>
 <4494016.1004425315@[0.0.0.0]>
X-Mailer: Mulberry/2.1.1 (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 BAA11579

--On 01-10-30 07.01 +0100 Patrik Fältström <paf@cisco.com> wrote:

> Note that I am nowhere above saying that SC/TC is a problem.

s/is a/is not a/

  paf




From owner-idn@ops.ietf.org  Tue Oct 30 03:02:49 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22501
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 03:02:48 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yTac-0007ew-00
	for idn-data@psg.com; Mon, 29 Oct 2001 23:45:38 -0800
Received: from [203.207.0.132] (helo=mail.asiainfra.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yTab-0007ep-00
	for idn@ops.ietf.org; Mon, 29 Oct 2001 23:45:37 -0800
Received: from gix ([203.207.0.121])
	by mail.asiainfra.com (8.9.3/8.9.3) with SMTP id PAA28529;
	Tue, 30 Oct 2001 15:45:43 +0800
From: "Kenny Huang" <huangk@alum.sinica.edu>
To: <jet-member@nic.ad.jp>, "ben" <ben@cc-www.com>, <idn@ops.ietf.org>,
        "Paul Hoffman / IMC" <phoffman@imc.org>
Subject: RE: [JET-member 486] Re: [idn] Traditional-simplified, yet again
Date: Tue, 30 Oct 2001 15:48:19 +0800
Message-ID: <IHELIFNJKJLDFEMBCENDCEIECIAA.huangk@alum.sinica.edu>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <4494016.1004425315@[0.0.0.0]>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id DAA22501

Hi Patrik,

Sorry for bothering you and others so much time. I believe there are some
misunderstanding in the communication loop. I know CNNIC and TWNIC 
detail proposals  are almost completed. These documents will be sent
to JET mailing for feedback information gathering before 3rd Nov.  We can
discuss the technical details based on the written document.  The scenario 
will be much more clear. I want to encourage everyone not to give up right
now.  Although we are all exhausted for being sunk into  IDN endless loop 
for more than 2 years.


Kenny Huang


> -----Original Message-----
> From: owner-jet-member@nic.ad.jp 
> [mailto:owner-jet-member@nic.ad.jp]On Behalf Of Patrik Faltstrom
> Sent: Tuesday, October 30, 2001 2:02 PM
> To: ben; idn@ops.ietf.org; Paul Hoffman / IMC
> Cc: jet-member@nic.ad.jp
> Subject: [JET-member 486] Re: [idn] Traditional-simplified, yet again
> 
> 
> --On 01-10-29 21.56 -0500 ben <ben@cc-www.com> wrote:
> 
> > How is it
> > possible for people to delay the progress of the IETF by simply
> > posting up messages and writing drafts?
> 
> By
> 
> (a) Talking about an important issue
> (b) People tell the author what part of that issue can be solved
>     in the DNS, and how, and point to other solutions for
>     the other part(s) of the issue
> (c) Talking about the important issue again, with no changes
> (d) People tell the author again that things have to be changed
>     because the issue can not be solved in DNS
> (e) Go to (c)
> 
> Myself, I have with the CNNIC people now passed point (e) four(!) times,
> and I start to get tired on this. The proposals from CNNIC have 
> not changed
> at all since (a), and conversations have occurred on the IDN mailing list,
> in private conversations (one is going on at the moment) and in face to
> face meetings.
> 
> Further, at second pass of (e), myself and others talked with the
> authorities on Chinese scripts we know to verify that we were not 
> stupid or
> misunderstood something. _ALL_ of these said that it was the CNNIC people
> which had not understood the complexity of the problem. Further, the
> Unicode Consortium have already been through the SC/TC problem 
> once, and to
> explicitly state this fact, the Unicode Consortium explicitly 
> sent a liason
> statement to the IETF stating this fact.
> 
> When all of these things was presented to the CNNIC people, the rough
> consensus in the wg on what to do, the information from external sources,
> and the liason statement from Unicode Consortium, the response is:
> 
> - The wg don't understand the problem
> - The external sources don't understand the problem
> - Unicode Consortium don't work on these issues
> - ISO have nothing to do with Chinese Characters
> 
> And we go back to (c) again from (e).
> 
> Sorry, but this is absolutely NOTHING but a delaying process from ignorant
> people.
> 
> Note that I am nowhere above saying that SC/TC is a problem. Just like
> other equality (define the word equality whatever way you want) when you
> use more than one script -- and in some cases even with one.
> 
> I am as you can see extremely tired on this wg not making process just
> because one group of people is blocking the discussions.
> 
> This wg is not making any progress.
> 
> Absolutely NOTHING has been changed in the proposals which are on 
> the table
> the last couple of months, and as in all processes, we _could_ have been
> able to discuss things which we still have to polish here and there. For
> example, the part of the SC/TC issues which have to do with mappings from
> local charsets to Unicode, use of Unicode in other protocol elements than
> domain names etc.
> 
> So, at the moment it is CNNIC which effectively see that the world can not
> use Chinese Characters in the DNS.
> 
>      paf




From owner-idn@ops.ietf.org  Tue Oct 30 03:42:03 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22751
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 03:42:02 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yUC8-00094X-00
	for idn-data@psg.com; Tue, 30 Oct 2001 00:24:24 -0800
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yUC7-00093g-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 00:24:23 -0800
Received: from deng ([159.226.7.68]) by whale.cnnic.net.cn
          (Netscape Messaging Server 4.15) with SMTP id GM0FEY00.I5L; Tue,
          30 Oct 2001 16:25:46 +0800 
Message-ID: <013401c1611b$296ff960$4407e29f@deng>
From: "xiang deng" <deng@cnnic.net.cn>
To: <jet-member@nic.ad.jp>, "ben" <ben@cc-www.com>, <idn@ops.ietf.org>,
        "Paul Hoffman / IMC" <phoffman@imc.org>
Cc: <jet-member@nic.ad.jp>
References: <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp><01c801c15 c3d$d9a7ae50$4407e29f@deng> <20011024130954A.yone@nic.ad.jp><024101c15c42$372e1b50$4407e29f@deng><007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio><003f01c15f5c$1d4e5f70$ec1bd9d2@temp><001101c15f64$7eb3b780$1c01000a@jamessonyvaio><016601c15f7d$14325c40$ec1bd9d2@temp><005501c15f80$9dd52a10$1c01000a@jamessonyvaio><000d01c15f81$5573d900$ec1bd9d2@temp><006301c15f82$da0cbe60$1c01000a@jamessonyvaio><001e01c15fae$010900c0$f006738c@ncu.edu.tw><p05101003b801e8c9a90b@[165.227.249.20]><001101c1604b$0a2b2d20$f006738c@ncu.edu.tw><p0510100fb8034e089e46@[165.227.249.18]><000d01c160ee$a8936740$cd462b18@mtag1.on.home.com> <4494016.1004425315@[0.0.0.0]>
Subject: Re: [JET-member 486] Re: [idn] Traditional-simplified, yet again
Date: Tue, 30 Oct 2001 16:16:22 +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 DAA22751


Who give you the power to make this STATEMENTS?

Who give you the power to STIGMATIZE other people 
in the IETF AND JET-MEMBER FORUM?

Who give you the power to THREATEN AND TERRIFY others?

Who give you the power to DENY CNNIC's effort?

Who give you the power to COMMAND others
what should and what shouldn't do?

Deng xiang

----- Original Message ----- 
From: "Patrik Fältström" <paf@cisco.com>
To: "ben" <ben@cc-www.com>; <idn@ops.ietf.org>; "Paul Hoffman / IMC" <phoffman@imc.org>
Cc: <jet-member@nic.ad.jp>
Sent: Tuesday, October 30, 2001 2:01 PM
Subject: [JET-member 486] Re: [idn] Traditional-simplified, yet again


> --On 01-10-29 21.56 -0500 ben <ben@cc-www.com> wrote:
> 
> > How is it
> > possible for people to delay the progress of the IETF by simply
> > posting up messages and writing drafts?
> 
> By
> 
> (a) Talking about an important issue
> (b) People tell the author what part of that issue can be solved
>     in the DNS, and how, and point to other solutions for
>     the other part(s) of the issue
> (c) Talking about the important issue again, with no changes
> (d) People tell the author again that things have to be changed
>     because the issue can not be solved in DNS
> (e) Go to (c)
> 
> Myself, I have with the CNNIC people now passed point (e) four(!) times,
> and I start to get tired on this. The proposals from CNNIC have not changed
> at all since (a), and conversations have occurred on the IDN mailing list,
> in private conversations (one is going on at the moment) and in face to
> face meetings.
> 
> Further, at second pass of (e), myself and others talked with the
> authorities on Chinese scripts we know to verify that we were not stupid or
> misunderstood something. _ALL_ of these said that it was the CNNIC people
> which had not understood the complexity of the problem. Further, the
> Unicode Consortium have already been through the SC/TC problem once, and to
> explicitly state this fact, the Unicode Consortium explicitly sent a liason
> statement to the IETF stating this fact.
> 
> When all of these things was presented to the CNNIC people, the rough
> consensus in the wg on what to do, the information from external sources,
> and the liason statement from Unicode Consortium, the response is:
> 
> - The wg don't understand the problem
> - The external sources don't understand the problem
> - Unicode Consortium don't work on these issues
> - ISO have nothing to do with Chinese Characters
> 
> And we go back to (c) again from (e).
> 
> Sorry, but this is absolutely NOTHING but a delaying process from ignorant
> people.
> 
> Note that I am nowhere above saying that SC/TC is a problem. Just like
> other equality (define the word equality whatever way you want) when you
> use more than one script -- and in some cases even with one.
> 
> I am as you can see extremely tired on this wg not making process just
> because one group of people is blocking the discussions.
> 
> This wg is not making any progress.
> 
> Absolutely NOTHING has been changed in the proposals which are on the table
> the last couple of months, and as in all processes, we _could_ have been
> able to discuss things which we still have to polish here and there. For
> example, the part of the SC/TC issues which have to do with mappings from
> local charsets to Unicode, use of Unicode in other protocol elements than
> domain names etc.
> 
> So, at the moment it is CNNIC which effectively see that the world can not
> use Chinese Characters in the DNS.
> 
>      paf
> 
> 


From owner-idn@ops.ietf.org  Tue Oct 30 03:57:28 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22936
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 03:57:27 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yUTy-0009fI-00
	for idn-data@psg.com; Tue, 30 Oct 2001 00:42:50 -0800
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yUTv-0009fB-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 00:42:48 -0800
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP id CC774FFC28
	for <idn@ops.ietf.org>; Tue, 30 Oct 2001 16:43:00 +0800 (SGT)
Message-ID: <014a01c1611e$d8a045e0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <idn@ops.ietf.org>
References: <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp><01c801c15 c3d$d9a7ae50$4407e29f@deng> <20011024130954A.yone@nic.ad.jp><024101c15c42$372e1b50$4407e29f@deng><007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio><003f01c15f5c$1d4e5f70$ec1bd9d2@temp><001101c15f64$7eb3b780$1c01000a@jamessonyvaio><016601c15f7d$14325c40$ec1bd9d2@temp><005501c15f80$9dd52a10$1c01000a@jamessonyvaio><000d01c15f81$5573d900$ec1bd9d2@temp><006301c15f82$da0cbe60$1c01000a@jamessonyvaio><001e01c15fae$010900c0$f006738c@ncu.edu.tw><p05101003b801e8c9a90b@[165.227.249.20]><001101c1604b$0a2b2d20$f006738c@ncu.edu.tw><p0510100fb8034e089e46@[165.227.249.18]><000d01c160ee$a8936740$cd462b18@mtag1.on.home.com> <4494016.1004425315@[0.0.0.0]> <013401c1611b$296ff960$4407e29f@deng>
Subject: Re: [JET-member 489] Re: [idn] Traditional-simplified, yet again
Date: Tue, 30 Oct 2001 16:42:45 +0800
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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Deng and Pat & and all,

I suggest everyone take a time out...

The IETF works on drafts. So instead of having this conversation, the
time should be spend on working on draft.

The WG move forward with consensus. There will be differences in
opinions and it should not be taken personally. And it also means not
everyone will be happy with the result. We just do the best we can with
the existing technology and information available to us.

-James Seng

----- Original Message -----
From: "xiang deng" <deng@cnnic.net.cn>
To: <jet-member@nic.ad.jp>; "ben" <ben@cc-www.com>; <idn@ops.ietf.org>;
"Paul Hoffman / IMC" <phoffman@imc.org>
Cc: <jet-member@nic.ad.jp>
Sent: Tuesday, October 30, 2001 4:16 PM
Subject: [JET-member 489] Re: [idn] Traditional-simplified, yet again


>
> Who give you the power to make this STATEMENTS?
>
> Who give you the power to STIGMATIZE other people
> in the IETF AND JET-MEMBER FORUM?
>
> Who give you the power to THREATEN AND TERRIFY others?
>
> Who give you the power to DENY CNNIC's effort?
>
> Who give you the power to COMMAND others
> what should and what shouldn't do?
>
> Deng xiang
>
> ----- Original Message -----
> From: "Patrik Fältström" <paf@cisco.com>
> To: "ben" <ben@cc-www.com>; <idn@ops.ietf.org>; "Paul Hoffman / IMC"
<phoffman@imc.org>
> Cc: <jet-member@nic.ad.jp>
> Sent: Tuesday, October 30, 2001 2:01 PM
> Subject: [JET-member 486] Re: [idn] Traditional-simplified, yet again
>
>
> > --On 01-10-29 21.56 -0500 ben <ben@cc-www.com> wrote:
> >
> > > How is it
> > > possible for people to delay the progress of the IETF by simply
> > > posting up messages and writing drafts?
> >
> > By
> >
> > (a) Talking about an important issue
> > (b) People tell the author what part of that issue can be solved
> >     in the DNS, and how, and point to other solutions for
> >     the other part(s) of the issue
> > (c) Talking about the important issue again, with no changes
> > (d) People tell the author again that things have to be changed
> >     because the issue can not be solved in DNS
> > (e) Go to (c)
> >
> > Myself, I have with the CNNIC people now passed point (e) four(!)
times,
> > and I start to get tired on this. The proposals from CNNIC have not
changed
> > at all since (a), and conversations have occurred on the IDN mailing
list,
> > in private conversations (one is going on at the moment) and in face
to
> > face meetings.
> >
> > Further, at second pass of (e), myself and others talked with the
> > authorities on Chinese scripts we know to verify that we were not
stupid or
> > misunderstood something. _ALL_ of these said that it was the CNNIC
people
> > which had not understood the complexity of the problem. Further, the
> > Unicode Consortium have already been through the SC/TC problem once,
and to
> > explicitly state this fact, the Unicode Consortium explicitly sent a
liason
> > statement to the IETF stating this fact.
> >
> > When all of these things was presented to the CNNIC people, the
rough
> > consensus in the wg on what to do, the information from external
sources,
> > and the liason statement from Unicode Consortium, the response is:
> >
> > - The wg don't understand the problem
> > - The external sources don't understand the problem
> > - Unicode Consortium don't work on these issues
> > - ISO have nothing to do with Chinese Characters
> >
> > And we go back to (c) again from (e).
> >
> > Sorry, but this is absolutely NOTHING but a delaying process from
ignorant
> > people.
> >
> > Note that I am nowhere above saying that SC/TC is a problem. Just
like
> > other equality (define the word equality whatever way you want) when
you
> > use more than one script -- and in some cases even with one.
> >
> > I am as you can see extremely tired on this wg not making process
just
> > because one group of people is blocking the discussions.
> >
> > This wg is not making any progress.
> >
> > Absolutely NOTHING has been changed in the proposals which are on
the table
> > the last couple of months, and as in all processes, we _could_ have
been
> > able to discuss things which we still have to polish here and there.
For
> > example, the part of the SC/TC issues which have to do with mappings
from
> > local charsets to Unicode, use of Unicode in other protocol elements
than
> > domain names etc.
> >
> > So, at the moment it is CNNIC which effectively see that the world
can not
> > use Chinese Characters in the DNS.
> >
> >      paf
> >
> >




From owner-idn@ops.ietf.org  Tue Oct 30 04:21:12 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23178
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 04:21:12 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yUsP-000AWc-00
	for idn-data@psg.com; Tue, 30 Oct 2001 01:08:05 -0800
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yUsO-000AWW-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 01:08:04 -0800
Received: from xiaodonglee ([159.226.7.70]) by
          whale.cnnic.net.cn (Netscape Messaging Server 4.15) with SMTP id
          GM0HFW00.C5D; Tue, 30 Oct 2001 17:09:32 +0800 
Message-ID: <013601c16121$9b4bb690$4607e29f@xiaodonglee>
Reply-To: "Xiaodong LEE" <lee@cnnic.net.cn>
From: "xiaodong lee" <lee@whale.cnnic.net.cn>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        "ben" <ben@cc-www.com>, <idn@ops.ietf.org>,
        "Paul Hoffman / IMC" <phoffman@imc.org>
Cc: <jet-member@nic.ad.jp>
References: <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp> <01c801c15 c3d$d9a7ae50$4407e29f@deng> <20011024130954A.yone@nic.ad.jp> <024101c15c42$372e1b50$4407e29f@deng> <007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio> <003f01c15f5c$1d4e5f70$ec1bd9d2@temp> <001101c15f64$7eb3b780$1c01000a@jamessonyvaio> <016601c15f7d$14325c40$ec1bd9d2@temp> <005501c15f80$9dd52a10$1c01000a@jamessonyvaio> <000d01c15f81$5573d900$ec1bd9d2@temp> <006301c15f82$da0cbe60$1c01000a@jamessonyvaio> <001e01c15fae$010900c0$f006738c@ncu.edu.tw> <p05101003b801e8c9a90b@[165.227.249.20]> <001101c1604b$0a2b2d20$f006738c@ncu.edu.tw> <p0510100fb8034e089e46@[165.227.249.18]> <000d01c160ee$a8936740$cd462b18@mtag1.on.home.com> <4494016.1004425315@[0.0.0.0]>
Subject: Re: [idn] Traditional-simplified, yet again
Date: Tue, 30 Oct 2001 17:02:30 +0800
Organization: CNIC-ICT
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.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
X-MIME-Autoconverted: from base64 to 8bit by ietf.org id EAA23178

Dear Patrik:

Everyone is tired in IDN, you and all. We do not want to make this 
in the truth. We brought up such problem, but it is a difficult problem 
to be solved based on so-called principles said by someone of IDN.
So we must prompt new solution to solve the big problem for Chinese
people again and again, which is not our aspiration. Who want to do that?
not you, and not us too.

You said some authorities on Chinese scripts think it is a complex problem,
I think so, CNNIC people and all Chinese people think it is not easy to solve 
too.
To do TS/SC in context is a difficult problem, it should not be solved in DNS.
but any difficult problem could be reduced in some case, and based on some
priciples. DNS is identifier, so we solve part of TS/SC problem in DNS, which 
will solve most of the TS/SC problem.
I don't know how you explain such problem for those authorities, I still think there
are some misunderstanding in such problem, we have explain the special 
problem of TS/SC for our chinese scripts expert which is author of the RFC about 
Chinese character, he agree with us too. we must differ this conversion problem 
from other TS/SC conversion, which I have explain in my draft, and will be explain 
again in our new draft that will be submitted soon after.

So I think you might read our draft carefully and understand our question.
maybe I cannot explain it in my draft for you for my poor English, but I do want
to discuss this with you  in detail.

let's be more patient on such problem and more progress for IDN too. OK?

Xiaodong Lee



----- Original Message ----- 
From: "Patrik Fältström" <paf@cisco.com>
To: "ben" <ben@cc-www.com>; <idn@ops.ietf.org>; "Paul Hoffman / IMC" <phoffman@imc.org>
Cc: <jet-member@nic.ad.jp>
Sent: Tuesday, October 30, 2001 2:01 PM
Subject: Re: [idn] Traditional-simplified, yet again


> --On 01-10-29 21.56 -0500 ben <ben@cc-www.com> wrote:
> 
> > How is it
> > possible for people to delay the progress of the IETF by simply
> > posting up messages and writing drafts?
> 
> By
> 
> (a) Talking about an important issue
> (b) People tell the author what part of that issue can be solved
>     in the DNS, and how, and point to other solutions for
>     the other part(s) of the issue
> (c) Talking about the important issue again, with no changes
> (d) People tell the author again that things have to be changed
>     because the issue can not be solved in DNS
> (e) Go to (c)
> 
> Myself, I have with the CNNIC people now passed point (e) four(!) times,
> and I start to get tired on this. The proposals from CNNIC have not changed
> at all since (a), and conversations have occurred on the IDN mailing list,
> in private conversations (one is going on at the moment) and in face to
> face meetings.
> 
> Further, at second pass of (e), myself and others talked with the
> authorities on Chinese scripts we know to verify that we were not stupid or
> misunderstood something. _ALL_ of these said that it was the CNNIC people
> which had not understood the complexity of the problem. Further, the
> Unicode Consortium have already been through the SC/TC problem once, and to
> explicitly state this fact, the Unicode Consortium explicitly sent a liason
> statement to the IETF stating this fact.
> 
> When all of these things was presented to the CNNIC people, the rough
> consensus in the wg on what to do, the information from external sources,
> and the liason statement from Unicode Consortium, the response is:
> 
> - The wg don't understand the problem
> - The external sources don't understand the problem
> - Unicode Consortium don't work on these issues
> - ISO have nothing to do with Chinese Characters
> 
> And we go back to (c) again from (e).
> 
> Sorry, but this is absolutely NOTHING but a delaying process from ignorant
> people.
> 
> Note that I am nowhere above saying that SC/TC is a problem. Just like
> other equality (define the word equality whatever way you want) when you
> use more than one script -- and in some cases even with one.
> 
> I am as you can see extremely tired on this wg not making process just
> because one group of people is blocking the discussions.
> 
> This wg is not making any progress.
> 
> Absolutely NOTHING has been changed in the proposals which are on the table
> the last couple of months, and as in all processes, we _could_ have been
> able to discuss things which we still have to polish here and there. For
> example, the part of the SC/TC issues which have to do with mappings from
> local charsets to Unicode, use of Unicode in other protocol elements than
> domain names etc.
> 
> So, at the moment it is CNNIC which effectively see that the world can not
> use Chinese Characters in the DNS.
> 
>      paf
> 
> 


From owner-idn@ops.ietf.org  Tue Oct 30 08:00:18 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26941
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 08:00:17 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yYAv-000GiV-00
	for idn-data@psg.com; Tue, 30 Oct 2001 04:39:25 -0800
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yYAu-000Gi1-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 04:39:24 -0800
Received: from [209.187.148.217] (helo=P2)
	by bs.jck.com with esmtp (Exim 3.32 #1)
	id 15yYAl-0008YP-00; Tue, 30 Oct 2001 12:39:15 +0000
Date: Tue, 30 Oct 2001 07:39:14 -0500
From: John C Klensin <klensin@jck.com>
To: xiang deng <deng@cnnic.net.cn>, idn@ops.ietf.org
Subject: Re: [idn] An ignorant question about TC<-> SC
Message-ID: <142282191.1004427554@P2>
In-Reply-To: <00f301c160ff$a9a367f0$4407e29f@deng>
References: <E15xrqq-000Adc-00@psg.com>
 <008901c16022$74b7c640$4407e29f@deng>
 <p0510100db8027d203d26@[165.227.249.20]>
 <1180657.1004337022@localhost>
 <006d01c16061$55b60150$4407e29f@deng>
 <019b01c1606b$83801120$dd00a8c0@jamessonyvaio>
 <008b01c160eb$cfc834b0$4407e29f@deng>
 <p05101014b803d0759182@[165.227.249.18]>
 <00f301c160ff$a9a367f0$4407e29f@deng>
X-Mailer: Mulberry/2.1.1 (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, 30 October, 2001 12:59 +0800 xiang deng
<deng@cnnic.net.cn> wrote:

> Paul:
> 
> I'm sure you know it's a problem of IDN in fact, it's not
> created. To refuse the existence of the problem will not help
> to solve it.

I don't believe anyone is trying to "refuse the existence of the
problem".  Certainly I do not, nor have I seen even a hint that
Paul, or Patrik, or others have done so.
 
> It isn't ASCII vs Chinese characters. IDN provide the platform
> for all scirpts include ASCII and Chinese character and
> others. When  IDN is created, it belongs to the whole world,
> anyone have selfish motive haven't the qualification to say
> I'M IDN MEMBER.
> 
> IDN is important for all of us, we hope the dream of IDN to be
> true. In my opinions, the right way is To dig the problem and
> Solve it. 

I think we are all in complete agreement on that topic as well.
Where there may be a difference of opinion is about the problem
to be solved and the process for solving it.

(1) The Process

There are really two steps in the IETF.  The first step is
explaining to others that there is a problem to be solved and
convincing them.  You and your colleagues have done a very good
job of this, perhaps better than you realize.  Almost everyone
is convinced.  If anyone is not convinced, anyone who still
believes this is not a problem, they have been strangly silent.

The second step requires that a proposal be put before the WG.
A very specific proposal, that can be evaluated against _all_
criteria.  This is important for many reasons, but perhaps the
most important is that the solutions for "IDN" (including
solutions for TC <-> SC) exists in a very constrained solution
space, e.g., 

	* The DNS must work globally: Local-only solutions are
	quite easy, but most fragment the Internet and the IETF
	cannot accept a solution that encourages fragmentation.
	
	* More generally, the DNS must continue to work.  If we
	could start over and redesign the DNS itself to do IDN
	better, we could examine a broader range of solutions.
	Note that two approaches to "starting over..." within
	the DNS context have been put on the table, and that the
	WG has expressed little interest in either.  One is the
	series of suggestions that require EDNS mechanisms and
	the other was the proposal to move toward a new DNS
	Class, on that was multilingual from the beginning.
	Each has disadvantages, but they would permit changing
	the DNS rules.  As far as I can tell, the DNS has not
	chosen to change the DNS rules, and I haven't see you or
	your colleagues arguing for either of these approaches.
	
	* The solution that improves matching for one language
	may not destroy matching for another language.

	* Unicode is a given.  Several of us believe that design
	decisions made in Unicode are making the IDN work harder
	than it might be otherwise ("Han unification" is just
	one of these decisions).  But the IDN WG can't change
	Unicode, there are no other _global_ coded character
	sets around (waiting for another one would take a _very_
	long time), and I fear we need to figure out how to make
	it work.  If you have other proposals, they should be
	taken to either the Unicode Consortium, or to ISO/IEC
	JTC1/SC2, or to some other recognized global standards
	body and brought back to the IETF only when they have
	agreed with you on a solution.  Arguing in the IDN WG
	about what, e.g., UTC, should do or ought to have done
	is useless, whether you make those arguments or I do.

And so on.

Without a specific draft, the rest of us can't help you in
evaluating these things; we just go around in circles.

(2) The Problem.

Again, we are in agreement that there is a TC <-> SC problem.
What is not clear is whether that is a problem that can be
solved in the DNS.  No one is suggesting that, if it can't be
solved in the DNS, it is not a problem.  Instead, several of us
have been working very hard on alternatives that could be used
if the DNS is not adequate.  And, again, our hypothesis that the
DNS is not adequate for this problem is just an hypothesis.
Your proposal could convince us otherwise, but, for that, we
need to see a proposal.

   regards,
     john




From owner-idn@ops.ietf.org  Tue Oct 30 10:45:02 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04558
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 10:45:02 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yasf-000LUc-00
	for idn-data@psg.com; Tue, 30 Oct 2001 07:32:45 -0800
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yase-000LUW-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 07:32:44 -0800
Received: from dhcp-64-103-48-158.cisco.com (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id QAA26444
	for <idn@ops.ietf.org>; Tue, 30 Oct 2001 16:32:42 +0100 (MET)
Date: Tue, 30 Oct 2001 16:27:00 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: idn@ops.ietf.org
Subject: [idn] Excuses from myself
Message-ID: <5277704.1004459220@localhost>
In-Reply-To: <142282191.1004427554@P2>
References: <E15xrqq-000Adc-00@psg.com><008901c16022$74b7c640$4407e29f@deng>
 <p0510100db8027d203d26@[165.227.249.20]><1180657.1004337022@localhost>
 <006d01c16061$55b60150$4407e29f@deng>
 <019b01c1606b$83801120$dd00a8c0@jamessonyvaio>
 <008b01c160eb$cfc834b0$4407e29f@deng><p05101014b803d0759182@[165.227.249.18]>
 <00f301c160ff$a9a367f0$4407e29f@deng> <142282191.1004427554@P2>
X-Mailer: Mulberry/2.1.1 (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

I should have stayed silent and not have written the last mail.

Sorry.

   paf




From owner-idn@ops.ietf.org  Tue Oct 30 11:22:29 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05774
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 11:22:27 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ybRK-000MbO-00
	for idn-data@psg.com; Tue, 30 Oct 2001 08:08:34 -0800
Received: from femail7.sdc1.sfba.home.com ([24.0.95.87])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ybRK-000MbI-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 08:08:34 -0800
Received: from c1340594a ([65.11.104.12]) by femail7.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20011030160833.ITZE5034.femail7.sdc1.sfba.home.com@c1340594a>
          for <idn@ops.ietf.org>; Tue, 30 Oct 2001 08:08:33 -0800
Message-ID: <005f01c1615d$41bf1860$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: <idn@ops.ietf.org>
References: <E15xrqq-000Adc-00@psg.com> <008901c16022$74b7c640$4407e29f@deng> <p0510100db8027d203d26@[165.227.249.20]> <1180657.1004337022@localhost> <006d01c16061$55b60150$4407e29f@deng> <019b01c1606b$83801120$dd00a8c0@jamessonyvaio> <008b01c160eb$cfc834b0$4407e29f@deng> <p05101014b803d0759182@[165.227.249.18]> <00f301c160ff$a9a367f0$4407e29f@deng> <142282191.1004427554@P2>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Tue, 30 Oct 2001 08:09:30 -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 6.00.2600.0000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I should try to clarify a few things.

There have been some objections on this list to Han Unification. While there
are often typographic differences between fonts used for Han ideographs in
different countries, what is encoded represents the fundamental character,
as defined by the IRG (Ideographic Raporteur Group). This group reports to
ISO/IEC SC2 WG2, the ISO WG responsible for ISO 10646. As stated elsewhere,
the IRG includes official representatives from China, Japan, the Republic of
Korea and DPR of Korea, Taiwan via the Taipei Computer Society (TCA), Hong
Kong, Singapore, the US, and the Unicode Consortium.
Han unification is mostly irrelevant to the TC <-> SC issue. The major
stumbling block is not that the TCs are unified across different countries,
but that accurate TC<->SC mappings are (a) not 1-1, (b) contextual, (c)
dictionary-based.

If there were a recognized 1-1 subset mapping between SC characters and TC
characters, I don't think unification would be an issue in matching. For
example, it would matter little to Japanese users that an SC character could
be typed in instead of one of their TC characters, so long as two different
TC characters used in Japan were *not* matched. This could be done as long
as the mapping never identifies two different TC characters with the same SC
character.

It should be also made clear that the Unicode consortium is not at all
opposed to the development of a TC <-> SC mapping. However, it is not a
trivial process. The best body to take on that work would be the IRG --
given the composition and expertise of its membership. The process of
arriving at a uniform, well-developed, agreed-upon mapping would probably
take some substantial time, and from that mapping one would have to extract
the 1-1 subset. As stated elsewhere, the consortium has not seen evidence
that such a mapping is required in IDN (given other mechanisms), and does
have considerable concern that it would slow down the IDN development
process even further.





From owner-idn@ops.ietf.org  Tue Oct 30 11:43:25 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06611
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 11:43:25 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ybmY-000NJ2-00
	for idn-data@psg.com; Tue, 30 Oct 2001 08:30:30 -0800
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ybmX-000NIq-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 08:30:29 -0800
Received: from [165.227.249.20] (165-227-249-20.client.dsl.net [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f9UGUO804526;
	Tue, 30 Oct 2001 08:30:24 -0800 (PST)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05101004b8047fd96a26@[165.227.249.20]>
In-Reply-To: <013601c16121$9b4bb690$4607e29f@xiaodonglee>
References: 
 <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp>
 <01c801c15 c3d$d9a7ae50$4407e29f@deng> <20011024130954A.yone@nic.ad.jp>
 <024101c15c42$372e1b50$4407e29f@deng>
 <007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio>
 <003f01c15f5c$1d4e5f70$ec1bd9d2@temp>
 <001101c15f64$7eb3b780$1c01000a@jamessonyvaio>
 <016601c15f7d$14325c40$ec1bd9d2@temp>
 <005501c15f80$9dd52a10$1c01000a@jamessonyvaio>
 <000d01c15f81$5573d900$ec1bd9d2@temp>
 <006301c15f82$da0cbe60$1c01000a@jamessonyvaio>
 <001e01c15fae$010900c0$f006738c@ncu.edu.tw>
 <p05101003b801e8c9a90b@[165.227.249.20]>
 <001101c1604b$0a2b2d20$f006738c@ncu.edu.tw>
 <p0510100fb8034e089e46@[165.227.249.18]>
 <000d01c160ee$a8936740$cd462b18@mtag1.on.home.com>
 <4494016.1004425315@[0.0.0.0]>
 <013601c16121$9b4bb690$4607e29f@xiaodonglee>
Date: Tue, 30 Oct 2001 08:08:28 -0800
To: "Xiaodong LEE" <lee@cnnic.net.cn>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] Traditional-simplified, yet again
Cc: <idn@ops.ietf.org>, <jet-member@nic.ad.jp>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Thank you for this message, particularly the tone of it. You talk 
about a draft and ask us to read it carefully. I would very much like 
to do that (and would certainly like to read it more than the recent 
messages!), but I don't know which draft you are speaking about. Was 
it announced and I missed it? Or will it be ready soon?

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Tue Oct 30 12:11:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07495
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 12:11:45 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ycBz-000Nt8-00
	for idn-data@psg.com; Tue, 30 Oct 2001 08:56:47 -0800
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ycBy-000Nt2-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 08:56:46 -0800
Received: from [165.227.249.20] (165-227-249-20.client.dsl.net [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f9UGpg806596;
	Tue, 30 Oct 2001 08:51:42 -0800 (PST)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05101006b804866af412@[165.227.249.20]>
In-Reply-To: 
 <7FC3066C236FD511BC5900508BAC86FE4D7E60@trestles.internal.realnames.com>
References: 
 <7FC3066C236FD511BC5900508BAC86FE4D7E60@trestles.internal.realnames.com>
Date: Tue, 30 Oct 2001 08:37:41 -0800
To: Yves Arrouye <yves@realnames.com>, idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: RE: [idn] Re: stringprep and unassigned code points
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 9:15 PM -0800 10/29/01, Yves Arrouye wrote:
>I think that at the end of the day, while we agree that adding more code
>points to Unicode will break some applications that use a Nameprep released
>before the code points were assigned,

We don't agree here. Following the rules in stringprep, no 
application will be broken by adding new code points. We (or, more 
accurately, Patrik Fältström and Mark Davis) specifically designed it 
that way. Applications taking queries should look at characters that 
they think are unassigned and pass them in the query.

Nor will new code points "break" name servers. A name server that is 
told to store a name that has what it thinks is an unassigned code 
point will simply say "no". Nothing will break. In order to get it to 
say "yes", you update the table of unassigned characters to the 
newer, now-smaller table.

I heartily request that people read this section of the stringprep 
draft and, if you find places where we can make it clearer, by all 
means let me know soon.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Tue Oct 30 12:32:01 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08203
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 12:32:00 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ycSR-000OBa-00
	for idn-data@psg.com; Tue, 30 Oct 2001 09:13:47 -0800
Received: from mail12.speakeasy.net ([216.254.0.212])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ycSQ-000OBT-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 09:13:46 -0800
Received: (qmail 92633 invoked from network); 30 Oct 2001 17:13:35 -0000
Received: from unknown (HELO Magnus) ([64.81.85.4]) (envelope-sender <tim@xtns.net>)
          by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <lee@cnnic.net.cn>; 30 Oct 2001 17:13:35 -0000
Message-ID: <004101c16166$2efd5f80$0200a8c0@Magnus>
From: "Tim Langdell" <tim@xtns.net>
To: "Xiaodong LEE" <lee@cnnic.net.cn>,
        =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>,
        "ben" <ben@cc-www.com>, <idn@ops.ietf.org>,
        "Paul Hoffman / IMC" <phoffman@imc.org>
Cc: <jet-member@nic.ad.jp>, "xiang deng" <deng@cnnic.net.cn>,
        "Mark Davis" <mark@macchiato.com>
References: <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp> <01c801c15 c3d$d9a7ae50$4407e29f@deng> <20011024130954A.yone@nic.ad.jp> <024101c15c42$372e1b50$4407e29f@deng> <007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio> <003f01c15f5c$1d4e5f70$ec1bd9d2@temp> <001101c15f64$7eb3b780$1c01000a@jamessonyvaio> <016601c15f7d$14325c40$ec1bd9d2@temp> <005501c15f80$9dd52a10$1c01000a@jamessonyvaio> <000d01c15f81$5573d900$ec1bd9d2@temp> <006301c15f82$da0cbe60$1c01000a@jamessonyvaio> <001e01c15fae$010900c0$f006738c@ncu.edu.tw> <p05101003b801e8c9a90b@[165.227.249.20]> <001101c1604b$0a2b2d20$f006738c@ncu.edu.tw> <p0510100fb8034e089e46@[165.227.249.18]> <000d01c160ee$a8936740$cd462b18@mtag1.on.home.com> <4494016.1004425315@[0.0.0.0]> <013601c16121$9b4bb690$4607e29f@xiaodonglee>
Subject: Re: [idn] Traditional-simplified, yet again
Date: Tue, 30 Oct 2001 09:13:20 -0800
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.00.2919.6600
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

As many of your already know, we here at XTNS are proponents of a layer that
sits on top of DNS because we feel there are many issues and potential
future features of IDN resolution that are better handled (at this time,
anyway) via such a layer than seeking to devise and integrate solutions into
the root. And indeed, our XTNS System does just that, enabling IDNs to be
"resolved" within the Address Bar of Internet Explorer, and then being
translated -- if desired -- to ACE to be routed to the root, or simply at
this time to be resolved directly to specific URLs or IP addresses.

It seems to us that this issue of TC<->SC mapping is  a perfect example of a
problem that is perhaps best dealt with at this time in the layer that we
provide sitting on top of DNS, rather than perhaps seeking an elusive
'perfect' solution in order to integrate such mapping into the DNS itself at
this time. The power of dealing with the TC<->SC issues in the layer that we
provide is that it can be dynamic (allowing for evolution of TC<->SC mapping
in the future) and can enable the on-going development of a solution that
can eventually be integrated into the root system for all IDNs. Our layer is
perfect for dealing with issues that are not simple one-to-one mappings, and
where context dictionary based problems are to be dealt with.

Moreover, as our system also handles Japanese.Japanese, Korean.Korean, etc,
we can equally coordinate other mapping issues as and when they arise such
as the example given by Mark:

>If there were a recognized 1-1 subset mapping between SC characters and TC
>characters, I don't think unification would be an issue in matching. For
>example, it would matter little to Japanese users that an SC character
could
>be typed in instead of one of their TC characters, so long as two different
>TC characters used in Japan were *not* matched. This could be done as long
>as the mapping never identifies two different TC characters with the same
SC
>character.

Were there a situation where two different TC characters really "ought" to
be mapped to the same SC character (and I do not know if there would be)
then here would be a perfect example of an issue that can be easily handled
via the XTNS System sitting on top of DNS, but is complex to even consider
resolving within the core IDN system itself. One to one mapping could be
eventually integrated into the root, leaving the exceptions and complex
translation issues to remain to be dealt with in the layer sitting on top of
DNS.

Tim

Dr. Tim Langdell
CEO
XTNS

----- Original Message -----
From: "xiaodong lee" <lee@whale.cnnic.net.cn>
To: "Patrik Fältström" <paf@cisco.com>; "ben" <ben@cc-www.com>;
<idn@ops.ietf.org>; "Paul Hoffman / IMC" <phoffman@imc.org>
Cc: <jet-member@nic.ad.jp>
Sent: Tuesday, October 30, 2001 1:02 AM
Subject: Re: [idn] Traditional-simplified, yet again


> Dear Patrik:
>
> Everyone is tired in IDN, you and all. We do not want to make this
> in the truth. We brought up such problem, but it is a difficult problem
> to be solved based on so-called principles said by someone of IDN.
> So we must prompt new solution to solve the big problem for Chinese
> people again and again, which is not our aspiration. Who want to do that?
> not you, and not us too.
>
> You said some authorities on Chinese scripts think it is a complex
problem,
> I think so, CNNIC people and all Chinese people think it is not easy to
solve
> too.
> To do TS/SC in context is a difficult problem, it should not be solved in
DNS.
> but any difficult problem could be reduced in some case, and based on some
> priciples. DNS is identifier, so we solve part of TS/SC problem in DNS,
which
> will solve most of the TS/SC problem.
> I don't know how you explain such problem for those authorities, I still
think there
> are some misunderstanding in such problem, we have explain the special
> problem of TS/SC for our chinese scripts expert which is author of the RFC
about
> Chinese character, he agree with us too. we must differ this conversion
problem
> from other TS/SC conversion, which I have explain in my draft, and will be
explain
> again in our new draft that will be submitted soon after.
>
> So I think you might read our draft carefully and understand our question.
> maybe I cannot explain it in my draft for you for my poor English, but I
do want
> to discuss this with you  in detail.
>
> let's be more patient on such problem and more progress for IDN too. OK?
>
> Xiaodong Lee
>
>
>
> ----- Original Message -----
> From: "Patrik Fältström" <paf@cisco.com>
> To: "ben" <ben@cc-www.com>; <idn@ops.ietf.org>; "Paul Hoffman / IMC"
<phoffman@imc.org>
> Cc: <jet-member@nic.ad.jp>
> Sent: Tuesday, October 30, 2001 2:01 PM
> Subject: Re: [idn] Traditional-simplified, yet again
>
>
> > --On 01-10-29 21.56 -0500 ben <ben@cc-www.com> wrote:
> >
> > > How is it
> > > possible for people to delay the progress of the IETF by simply
> > > posting up messages and writing drafts?
> >
> > By
> >
> > (a) Talking about an important issue
> > (b) People tell the author what part of that issue can be solved
> >     in the DNS, and how, and point to other solutions for
> >     the other part(s) of the issue
> > (c) Talking about the important issue again, with no changes
> > (d) People tell the author again that things have to be changed
> >     because the issue can not be solved in DNS
> > (e) Go to (c)
> >
> > Myself, I have with the CNNIC people now passed point (e) four(!) times,
> > and I start to get tired on this. The proposals from CNNIC have not
changed
> > at all since (a), and conversations have occurred on the IDN mailing
list,
> > in private conversations (one is going on at the moment) and in face to
> > face meetings.
> >
> > Further, at second pass of (e), myself and others talked with the
> > authorities on Chinese scripts we know to verify that we were not stupid
or
> > misunderstood something. _ALL_ of these said that it was the CNNIC
people
> > which had not understood the complexity of the problem. Further, the
> > Unicode Consortium have already been through the SC/TC problem once, and
to
> > explicitly state this fact, the Unicode Consortium explicitly sent a
liason
> > statement to the IETF stating this fact.
> >
> > When all of these things was presented to the CNNIC people, the rough
> > consensus in the wg on what to do, the information from external
sources,
> > and the liason statement from Unicode Consortium, the response is:
> >
> > - The wg don't understand the problem
> > - The external sources don't understand the problem
> > - Unicode Consortium don't work on these issues
> > - ISO have nothing to do with Chinese Characters
> >
> > And we go back to (c) again from (e).
> >
> > Sorry, but this is absolutely NOTHING but a delaying process from
ignorant
> > people.
> >
> > Note that I am nowhere above saying that SC/TC is a problem. Just like
> > other equality (define the word equality whatever way you want) when you
> > use more than one script -- and in some cases even with one.
> >
> > I am as you can see extremely tired on this wg not making process just
> > because one group of people is blocking the discussions.
> >
> > This wg is not making any progress.
> >
> > Absolutely NOTHING has been changed in the proposals which are on the
table
> > the last couple of months, and as in all processes, we _could_ have been
> > able to discuss things which we still have to polish here and there. For
> > example, the part of the SC/TC issues which have to do with mappings
from
> > local charsets to Unicode, use of Unicode in other protocol elements
than
> > domain names etc.
> >
> > So, at the moment it is CNNIC which effectively see that the world can
not
> > use Chinese Characters in the DNS.
> >
> >      paf
> >
> >
>




From owner-idn@ops.ietf.org  Tue Oct 30 13:32:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10516
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 13:32:37 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ydSN-000PRu-00
	for idn-data@psg.com; Tue, 30 Oct 2001 10:17:47 -0800
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ydSA-000PRg-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 10:17:34 -0800
Received: from test12345 ([140.115.6.240])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f9UIO5V15235;
	Wed, 31 Oct 2001 02:24:05 +0800 (CST)
Message-ID: <002301c1616e$39fa8220$f006738c@ncu.edu.tw>
From: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: "Mark Davis" <mark@macchiato.com>, <idn@ops.ietf.org>
References: <E15xrqq-000Adc-00@psg.com> <008901c16022$74b7c640$4407e29f@deng> <p0510100db8027d203d26@[165.227.249.20]> <1180657.1004337022@localhost> <006d01c16061$55b60150$4407e29f@deng> <019b01c1606b$83801120$dd00a8c0@jamessonyvaio> <008b01c160eb$cfc834b0$4407e29f@deng> <p05101014b803d0759182@[165.227.249.18]> <00f301c160ff$a9a367f0$4407e29f@deng> <142282191.1004427554@P2> <005f01c1615d$41bf1860$0c680b41@c1340594a>
Subject: Re: [idn] An ignorant question about TC<-> SC
Date: Wed, 31 Oct 2001 02:10:57 +0800
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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi ! All:
             Someone give me the following information about  UTC joint
meeting.

http://www.unicode.org/unicode/consortium/utc-minutes/UTC-088-200108.html

IETF - IDN Name Preparation
[88-A51] Action Item for Michel Suignard: Give comments to Mark Davis and
Cathy Wissink on IDN name prep for them to forward to the appropriate
people. [L2/01-318]
[88-C5] Consensus: The UTC would like to see a paragraph added to the IDN
Internet Draft, Preparation of Internationalized Host Names, regarding name
preparation, which would clarify that alternate names may need to be
registered to handle variant spellings for different languages and
simplified and traditional forms. [L2/01-318]

[88-A52] Action Item for Mark Davis, Cathy Wissink: Write and submit a
paragraph on alternate names to the IDN working group. Include Michel
Suignard's comments. [L2/01-318]

[88-A53] Action Item for Asmus Freytag: Suggest text for UAX#15 Unicode
Normalization Forms about IDN name preparation. [L2/01-318]

Properties
[88-C6] Consensus: The UTC does not guarantee that casing preserves
normalization form, but in the future such a requirement may be considered.
[L2/01-321, 327]
[88-A54] Action Item for Lisa Moore: Forward the UTC response on preserving
normalization form when casing to Kent Karlsson. [L2/01-321, 327]

==========
          From the point of view of  TC/SC conversion . No chinese expert
will try to solve this problem in one simple approach.  The HAN scripts
mapping  can be divide to 1-1, 1-n, m-n catagory.  The 1-n , m-n are
sementic sensitive , they are language related and MUST be treated in high
level , so 88-C5 can be applied to these scripts by alternate name
registration.
          But ,  in actual case , PRC-ONLY-SC  that are directly derived
from TC used in China and some foreign country. Most of these PRC-ONLY-SC is
modified with the radical of quick-wriiten  form and they are frequently
used characters in chinese text. So it has high probability to mixed them or
confusing in browsing. Some of these PRC-ONLY-SC are 1-n  that can be
recognied and remove to 1-n catagory , and some of  SC are the same as
Japan's modified Kanchi , if they are different in meaning , then it can be
move to  1-1 local mapping table that belong to other catagory to reduce the
side effect of different language.  The final small set of  1-1 mapping
PRC-ONLY-SC/TC  can be get from the original PRC announced documents. If
these table is combined with the AMC-ACE-Z encoder/decoder with case
anotation output to ACE string, We can get a module that can input  TC/SC
unicoded data and  encode it to ouput  ACE string with pre-defined case ,
the reversing  to deocde ACE string with case will recover to each original
TC/SC by this module . It may be  forced the case to diplay a prefered TC/SC
form to meet the requirement of AP to display them.
          The encoder/decoder will recover to the original  TC/SC unicode
point , so UNICODE table will not be changed.
          By the same ACE string with different casing ,  LDH-DNS server
compare the ACE label case-insensitively . So 1-1 mapping TC/PRC-ONLY-SC
scripts are the same symbol of  name-identifier.
          The 1-1 mapinng PRC-ONLY-SC/TC encoding can not solve all the
problems of  TC/SC convertion . But it can reduce the complexity by level-1
DNS, so the 2^N problem can be reduced to a manageable condition.
          Based on the table that PRC  announced and keep more than 40
years.  It can be keep work quickly without to spend much time to argue.
This approach is not try to do the best or complete perfect solution. But by
this way , solving TC/SC conversion in each level , many troubles can be
reduced to be more managable.
          The numbers of  TC/SC 1-1 mapping pair is a scale factor,  2000
pairs are more than  26 pair of ASCII with 2 order of magnitude , people can
not remember them easily.

L.M.Tseng

----- Original Message -----
From: "Mark Davis" <mark@macchiato.com>
To: <idn@ops.ietf.org>
Sent: Wednesday, October 31, 2001 12:09 AM
Subject: Re: [idn] An ignorant question about TC<-> SC


> I should try to clarify a few things.
>
> There have been some objections on this list to Han Unification. While
there
> are often typographic differences between fonts used for Han ideographs in
> different countries, what is encoded represents the fundamental character,
> as defined by the IRG (Ideographic Raporteur Group). This group reports to
> ISO/IEC SC2 WG2, the ISO WG responsible for ISO 10646. As stated
elsewhere,
> the IRG includes official representatives from China, Japan, the Republic
of
> Korea and DPR of Korea, Taiwan via the Taipei Computer Society (TCA), Hong
> Kong, Singapore, the US, and the Unicode Consortium.
> Han unification is mostly irrelevant to the TC <-> SC issue. The major
> stumbling block is not that the TCs are unified across different
countries,
> but that accurate TC<->SC mappings are (a) not 1-1, (b) contextual, (c)
> dictionary-based.
>
> If there were a recognized 1-1 subset mapping between SC characters and TC
> characters, I don't think unification would be an issue in matching. For
> example, it would matter little to Japanese users that an SC character
could
> be typed in instead of one of their TC characters, so long as two
different
> TC characters used in Japan were *not* matched. This could be done as long
> as the mapping never identifies two different TC characters with the same
SC
> character.
>
> It should be also made clear that the Unicode consortium is not at all
> opposed to the development of a TC <-> SC mapping. However, it is not a
> trivial process. The best body to take on that work would be the IRG --
> given the composition and expertise of its membership. The process of
> arriving at a uniform, well-developed, agreed-upon mapping would probably
> take some substantial time, and from that mapping one would have to
extract
> the 1-1 subset. As stated elsewhere, the consortium has not seen evidence
> that such a mapping is required in IDN (given other mechanisms), and does

> have considerable concern that it would slow down the IDN development
> process even further.
>
>
>




From owner-idn@ops.ietf.org  Tue Oct 30 19:59:19 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18011
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 19:59:18 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yjPk-0007EJ-00
	for idn-data@psg.com; Tue, 30 Oct 2001 16:39:28 -0800
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.33 #1)
	id 15yjPk-0007EB-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 16:39:28 -0800
Received: (qmail 2342 invoked by uid 104); 31 Oct 2001 00:39:23 -0000
Received: from yves@realnames.com by friendly.realnames.com with qmail-scanner-0.96 (. Clean. Processed in 0.814783 secs); 31 Oct 2001 00:39:23 -0000
Received: from heaven.internal.realnames.com (10.1.5.39)
  by friendly.realnames.com with SMTP; 31 Oct 2001 00:39:22 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:1168]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <4978@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Tue, 30 Oct 2001 4:35:47 PM -0800
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2653.19)
	id <V3D1GYDR>; Tue, 30 Oct 2001 16:38:32 -0800
Message-ID: <7FC3066C236FD511BC5900508BAC86FE4D7E75@trestles.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: "'Paul Hoffman / IMC'" <phoffman@imc.org>, idn@ops.ietf.org
Subject: RE: [idn] Re: stringprep and unassigned code points
Date: Tue, 30 Oct 2001 16:34:58 -0800
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA18011

> At 9:15 PM -0800 10/29/01, Yves Arrouye wrote:
> >I think that at the end of the day, while we agree that adding more code
> >points to Unicode will break some applications that use a Nameprep
> released
> >before the code points were assigned,
> 
> We don't agree here. Following the rules in stringprep, no
> application will be broken by adding new code points. We (or, more
> accurately, Patrik Fältström and Mark Davis) specifically designed it
> that way. Applications taking queries should look at characters that
> they think are unassigned and pass them in the query.
>
> [...]
>
> I heartily request that people read this section of the stringprep
> draft and, if you find places where we can make it clearer, by all
> means let me know soon.

Well, I heartily request that people read my emails carefully or use replies
different than "you're wrong" (not you, Paul). I did read section 6 of
Stringprep, even before Patrick suggested I do so (would make sense,
right?). My understanding is still that the following scenario is possible
(rephrasing it since my previous attempts at quoting Stringprep section 6
were apparently unproductive):

- Application A uses a profile of Stringprep where say U+20000 and above are
unassigned, because U+20000 was not in Unicode at the time that application
was written. It generates queries for server S, getting Unicode code points
from an operating-system provided input method. Per the Stringprep spec, and
your explanation above, when A gets U+20000 it passes it untouched in the
query.

- Server S benefits from a more recent implementation whose profile of
Stringprep has U+20000 to U+200FF assigned. And it has some mapping for
U+20000. Let's say we're talking DNS (what people here relate the most to),
and it is using a Nameprep version with a map that says:

	20000; 20021; Case map

(I could use deletion as well to go around David's argument of bicameral
scripts). Strings that have been Name/String-prepped for server S have
U+20000 mapped to U+20021. As a result, S and A cannot understand each other
when S receives a string that has U+20000 in it. Unless you suggest that S
should reprocess A's query, but I do not think that has been suggested.

I will be glad to understand that I am wrong in saying that this scenario
shows that some queries from older applications won't have the expected
result against more recent servers (older/recent as far as Stringprep goes).
But can you please point out where my reasoning is then?

Thanks,
YA
 



From owner-idn@ops.ietf.org  Tue Oct 30 20:14:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18135
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 20:14:46 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yjm8-0007eS-00
	for idn-data@psg.com; Tue, 30 Oct 2001 17:02:36 -0800
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yjm7-0007e8-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 17:02:35 -0800
Received: from xiaodonglee ([159.226.7.70]) by
          whale.cnnic.net.cn (Netscape Messaging Server 4.15) with SMTP id
          GM1PMK00.G72; Wed, 31 Oct 2001 09:03:56 +0800 
Message-ID: <01f401c161a6$f51bcdb0$4607e29f@xiaodonglee>
Reply-To: "Xiaodong LEE" <lee@cnnic.net.cn>
From: "xiaodong lee" <lee@whale.cnnic.net.cn>
To: "Paul Hoffman / IMC" <phoffman@imc.org>
Cc: <idn@ops.ietf.org>, <jet-member@nic.ad.jp>
References: <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp> <01c801c15 c3d$d9a7ae50$4407e29f@deng> <20011024130954A.yone@nic.ad.jp> <024101c15c42$372e1b50$4407e29f@deng> <007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio> <003f01c15f5c$1d4e5f70$ec1bd9d2@temp> <001101c15f64$7eb3b780$1c01000a@jamessonyvaio> <016601c15f7d$14325c40$ec1bd9d2@temp> <005501c15f80$9dd52a10$1c01000a@jamessonyvaio> <000d01c15f81$5573d900$ec1bd9d2@temp> <006301c15f82$da0cbe60$1c01000a@jamessonyvaio> <001e01c15fae$010900c0$f006738c@ncu.edu.tw> <p05101003b801e8c9a90b@[165.227.249.20]> <001101c1604b$0a2b2d20$f006738c@ncu.edu.tw> <p0510100fb8034e089e46@[165.227.249.18]> <000d01c160ee$a8936740$cd462b18@mtag1.on.home.com> <4494016.1004425315@[0.0.0.0]> <013601c16121$9b4bb690$4607e29f@xiaodonglee> <p05101004b8047fd96a26@[165.227.249.20]>
Subject: Re: [idn] Traditional-simplified, yet again
Date: Wed, 31 Oct 2001 08:57:04 +0800
Organization: CNIC-ICT
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.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
X-MIME-Autoconverted: from base64 to 8bit by ietf.org id UAA18135

Dear Paul:

We are preparing a draft about requirement of Chinese Domain Name( approximately named as this) and a draft of how to treat this requirement. we do hope these two draft could be accepted by IDNese and these two draft are useful for IDNese to understand the real attempt to do that TSconv.  These draft will be made rough consensus in JET and submitted to IDN soon after.

You might read it about in less than two weeks. and We do hope to get your help and suggestion of these two draft too, just as your comprehension and help in Aug meeting in London and before.

Xiaodong Lee

----- Original Message ----- 
From: "Paul Hoffman / IMC" <phoffman@imc.org>
To: "Xiaodong LEE" <lee@cnnic.net.cn>
Cc: <idn@ops.ietf.org>; <jet-member@nic.ad.jp>
Sent: Wednesday, October 31, 2001 12:08 AM
Subject: Re: [idn] Traditional-simplified, yet again


> Thank you for this message, particularly the tone of it. You talk 
> about a draft and ask us to read it carefully. I would very much like 
> to do that (and would certainly like to read it more than the recent 
> messages!), but I don't know which draft you are speaking about. Was 
> it announced and I missed it? Or will it be ready soon?
> 
> --Paul Hoffman, Director
> --Internet Mail Consortium


From owner-idn@ops.ietf.org  Tue Oct 30 21:04:27 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18613
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 21:04:26 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ykXn-0008wI-00
	for idn-data@psg.com; Tue, 30 Oct 2001 17:51:51 -0800
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ykXl-0008wA-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 17:51:50 -0800
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP id 054B9FFC30
	for <idn@ops.ietf.org>; Wed, 31 Oct 2001 09:51:58 +0800 (SGT)
Message-ID: <01d701c161ae$97a21470$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <idn@ops.ietf.org>
References:  <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp> <01c801c15 c3d$d9a7ae50$4407e29f@deng> <20011024130954A.yone@nic.ad.jp> <024101c15c42$372e1b50$4407e29f@deng> <007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio> <003f01c15f5c$1d4e5f70$ec1bd9d2@temp> <001101c15f64$7eb3b780$1c01000a@jamessonyvaio> <016601c15f7d$14325c40$ec1bd9d2@temp> <005501c15f80$9dd52a10$1c01000a@jamessonyvaio> <000d01c15f81$5573d900$ec1bd9d2@temp> <006301c15f82$da0cbe60$1c01000a@jamessonyvaio> <001e01c15fae$010900c0$f006738c@ncu.edu.tw> <p05101003b801e8c9a90b@[165.227.249.20]> <001101c1604b$0a2b2d20$f006738c@ncu.edu.tw> <p0510100fb8034e089e46@[165.227.249.18]> <000d01c160ee$a8936740$cd462b18@mtag1.on.home.com> <4494016.1004425315@[0.0.0.0]> <013601c16121$9b4bb690$4607e29f@xiaodonglee> <p05101004b8047fd96a26@[165.227.249.20]> <009f01c161a9$aadcd110$dd00a8c0@jamessonyvaio>
Subject: Note: WG Process - Was Re: [idn] Traditional-simplified, yet again
Date: Wed, 31 Oct 2001 09:51:43 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I like to remind everyone that if a draft is not published AND have not
been accepted into this working group, the draft is as good as not exist
in the view of the working group. We will not and cannot wait
indefinately. Neither should we stall the process on a REAL-SOON-NOW
draft.

The working group should, must and will proceed with the drafts
currently in its pool, currently:

Internationalizing Host Names In Applications
(IDNA)(draft-ietf-idn-idna)
Preparation of Internationalized Host Names (draft-ietf-idn-nameprep)
Proposal for a determining process of ACE identifier
(draft-ietf-idn-aceid)
Japanese characters in multilingual domain name label
(draft-ietf-idn-jpchar)
Traditional and Simplified Chinese Conversion (draft-ietf-idn-tsconv)
Hangeul NAMEPREP recommendation version 1.0(draft-ietf-idn-hangeulchar)
Improving ACE using code point reordering v1.0(draft-ietf-idn-lsb-ace)
AMC-ACE-Z (draft-ietf-idn-amc-ace-z)

-James Seng

----- Original Message -----
From: "Paul Hoffman / IMC" <phoffman@imc.org>
To: "Xiaodong LEE" <lee@cnnic.net.cn>
Cc: <idn@ops.ietf.org>; <jet-member@nic.ad.jp>
Sent: Wednesday, October 31, 2001 12:08 AM
Subject: [JET-member 491] Re: [idn] Traditional-simplified, yet again


> Thank you for this message, particularly the tone of it. You talk
> about a draft and ask us to read it carefully. I would very much like
> to do that (and would certainly like to read it more than the recent
> messages!), but I don't know which draft you are speaking about. Was
> it announced and I missed it? Or will it be ready soon?
>
> --Paul Hoffman, Director
> --Internet Mail Consortium





From owner-idn@ops.ietf.org  Tue Oct 30 21:04:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18624
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 21:04:36 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ykUx-0008sl-00
	for idn-data@psg.com; Tue, 30 Oct 2001 17:48:55 -0800
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ykUw-0008sf-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 17:48:54 -0800
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id AF7FCFFC17; Wed, 31 Oct 2001 09:16:42 +0800 (SGT)
Message-ID: <009f01c161a9$aadcd110$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <jet-member@nic.ad.jp>, "Xiaodong LEE" <lee@cnnic.net.cn>
Cc: <idn@ops.ietf.org>, <jet-member@nic.ad.jp>
References:  <3BD556C6.6C49EF21@twnic.net.tw><20011024114321N.yone@nic.ad.jp> <01c801c15 c3d$d9a7ae50$4407e29f@deng> <20011024130954A.yone@nic.ad.jp> <024101c15c42$372e1b50$4407e29f@deng> <007a01c15f57$0f0cdfe0$1c01000a@jamessonyvaio> <003f01c15f5c$1d4e5f70$ec1bd9d2@temp> <001101c15f64$7eb3b780$1c01000a@jamessonyvaio> <016601c15f7d$14325c40$ec1bd9d2@temp> <005501c15f80$9dd52a10$1c01000a@jamessonyvaio> <000d01c15f81$5573d900$ec1bd9d2@temp> <006301c15f82$da0cbe60$1c01000a@jamessonyvaio> <001e01c15fae$010900c0$f006738c@ncu.edu.tw> <p05101003b801e8c9a90b@[165.227.249.20]> <001101c1604b$0a2b2d20$f006738c@ncu.edu.tw> <p0510100fb8034e089e46@[165.227.249.18]> <000d01c160ee$a8936740$cd462b18@mtag1.on.home.com> <4494016.1004425315@[0.0.0.0]> <013601c16121$9b4bb690$4607e29f@xiaodonglee> <p05101004b8047fd96a26@[165.227.249.20]>
Subject: Note: WG Process - Was Re: [idn] Traditional-simplified, yet again
Date: Wed, 31 Oct 2001 09:16: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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I like to remind everyone that if a draft is not published AND have not
been accepted into this working group, the draft is as good as not exist
in the view of the working group. We will not and cannot wait
indefinately. Neither should we stall the process on a REAL-SOON-NOW
draft.

The working group should, must and will proceed with the drafts
currently in its pool, currently:

Internationalizing Host Names In Applications
(IDNA)(draft-ietf-idn-idna)
Preparation of Internationalized Host Names (draft-ietf-idn-nameprep)
Proposal for a determining process of ACE identifier
(draft-ietf-idn-aceid)
Japanese characters in multiling ual domain name label
(draft-ietf-idn-jpchar)
Traditional and Simplified Chinese Conversion (draft-ietf-idn-tsconv)
Hangeul NAMEPREP recommendation version 1.0(draft-ietf-idn-hangeulchar)
Improving ACE using code point reordering v1.0(draft-ietf-idn-lsb-ace)
AMC-ACE-Z (draft-ietf-idn-amc-ace-z)

-James Seng

----- Original Message -----
From: "Paul Hoffman / IMC" <phoffman@imc.org>
To: "Xiaodong LEE" <lee@cnnic.net.cn>
Cc: <idn@ops.ietf.org>; <jet-member@nic.ad.jp>
Sent: Wednesday, October 31, 2001 12:08 AM
Subject: [JET-member 491] Re: [idn] Traditional-simplified, yet again


> Thank you for this message, particularly the tone of it. You talk
> about a draft and ask us to read it carefully. I would very much like
> to do that (and would certainly like to read it more than the recent
> messages!), but I don't know which draft you are speaking about. Was
> it announced and I missed it? Or will it be ready soon?
>
> --Paul Hoffman, Director
> --Internet Mail Consortium




From owner-idn@ops.ietf.org  Tue Oct 30 21:07:34 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18654
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 21:07:33 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ykeG-00092t-00
	for idn-data@psg.com; Tue, 30 Oct 2001 17:58:32 -0800
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ykeF-00092n-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 17:58:31 -0800
Received: from [165.227.249.20] (165-227-249-20.client.dsl.net [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f9V1wP824586;
	Tue, 30 Oct 2001 17:58:26 -0800 (PST)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05101003b80509f76b14@[165.227.249.20]>
In-Reply-To: 
 <7FC3066C236FD511BC5900508BAC86FE4D7E7F@trestles.internal.realnames.com>
References: 
 <7FC3066C236FD511BC5900508BAC86FE4D7E7F@trestles.internal.realnames.com>
Date: Tue, 30 Oct 2001 17:58:21 -0800
To: Yves Arrouye <yves@realnames.com>, idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: RE: [idn] Re: stringprep and unassigned code points
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 5:35 PM -0800 10/30/01, Yves Arrouye wrote:
>You are missing my point:

Sorry, I can now see that. I thought you were talking about software, 
not people's perceptions.

>  at the time the application gets the code point
>from its environment (the operating system), the code point *is* assigned.
>It is just not considered so because of the Stringprep profile compiled in
>the application. So while this code point is perfectly fine for 1/ the user,
>2/ the people who entered a properly processed string in Server S, the net
>effect, *from the user's perspective* may be that they see some literature
>that advertise going to \U00020000.com (where \U<eight-hex> represents a
>Unicode code point), type exactly that, but cannot get there.

Ah, I see what you are saying now. Sorry for my denseness. You are, 
of course, correct. Anyone who advertises a host name that only 
exists in some newer version of nameprep, and the string that they 
advertise will come out of the newer version different than it went 
in, will be doing a disservice to any user who has an old version.

I'll try to think up some wording relating to this and send it to the 
list for inclusion in the next draft.

>My only conclusion from that was that it is not correct to say that
>applications or their supporting libraries (for Stringprep/Nameprep) will
>not need to be upgraded.

No one ever said that they did not need to be upgraded. They do not 
need to be upgraded in order to enter characters that are valid in 
stored host names. There is a big difference.

>  It may be very easy to do as I said (e.g. on an OS
>where every app uses a shared lib for that, upgrade the lib when you add
>support for the code points in the OS through a language pack or whatever).
>It may also be a nightmare for users of many applications that each use
>their own implementation.

It is only a "nightmare" for the people who enter characters that are 
mapped. Again, it would be silly for someone to advertise a name 
knowing that people with older clients could not enter it.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Tue Oct 30 21:25:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18761
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 21:25:58 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ykuG-0009OA-00
	for idn-data@psg.com; Tue, 30 Oct 2001 18:15:04 -0800
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ykuF-0009Nr-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 18:15:03 -0800
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP id 6DA81FFC18
	for <idn@ops.ietf.org>; Wed, 31 Oct 2001 10:15:13 +0800 (SGT)
Message-ID: <033c01c161b1$d7548230$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <idn@ops.ietf.org>
Subject: [idn] mailing list malfunction
Date: Wed, 31 Oct 2001 10:14:58 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

there was a brief technical outrage on the mailing list on 31st oct
around 1:45GMT for 10-20mins. If you have send an email to the working
group during that period of time, please resend.

you can get the hint of whether your mail fails to go thru by
(a) you got a bounce from your mail
(b) you got an error from owner-idn@psg.com
(c) you did not see your mail from the list

-James Seng




From owner-idn@ops.ietf.org  Tue Oct 30 21:35:37 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19855
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 21:35:36 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yl4w-0009ZT-00
	for idn-data@psg.com; Tue, 30 Oct 2001 18:26:06 -0800
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yl4v-0009ZM-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 18:26:05 -0800
Received: from [165.227.249.20] (165-227-249-20.client.dsl.net [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f9V2Px825416;
	Tue, 30 Oct 2001 18:26:00 -0800 (PST)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05101005b80511b53bc3@[165.227.249.20]>
Date: Tue, 30 Oct 2001 18:25:59 -0800
To: Yves Arrouye <yves@realnames.com>, idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: RE: [idn] Re: stringprep and unassigned code points
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 4:34 PM -0800 10/30/01, Yves Arrouye wrote:
>I will be glad to understand that I am wrong in saying that this scenario
>shows that some queries from older applications won't have the expected
>result against more recent servers (older/recent as far as Stringprep goes).
>But can you please point out where my reasoning is then?

"won't have the expected result" is quite different than "breaks". In 
your scenario, the application has no idea what the expected result 
is. The application simply knows that it is entering a character that 
is (according to the version of nameprep it is using) unassigned. 
Thus, a response of "no such name" makes perfect sense to the 
application. Remember, the client might be talking to a server that 
is using the same version of nameprep, and such a server will 
certainly generate "no such name" for any name that contains an 
unassigned character.

There is no expectation that entering random unassigned characters 
will work. As you point out, those characters may be mapped or they 
may be prohibited in the version of nameprep that is running on the 
server. Further, even though the server might be running newer 
software, the character might still be unassigned.

In short, a client has no particular "expected result" for a query 
with unassigned characters in it.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Tue Oct 30 22:18:38 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20073
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 22:18:38 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yldb-000A97-00
	for idn-data@psg.com; Tue, 30 Oct 2001 19:01:55 -0800
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ylda-000A91-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 19:01:54 -0800
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.6/8.9.3) with ESMTP id f9V335m15499;
	Tue, 30 Oct 2001 22:03:06 -0500 (EST)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200110310303.f9V335m15499@nic-naa.net>
X-Mailer: exmh version 1.6.9 8/22/96
To: "James Seng/Personal" <jseng@pobox.org.sg>
cc: jet-member@nic.ad.jp, "Xiaodong LEE" <lee@cnnic.net.cn>, idn@ops.ietf.org
Subject: Re: Note: WG Process - Was Re: [idn] Traditional-simplified, yet 
 again
In-Reply-To: Your message of "Wed, 31 Oct 2001 09:16:28 +0800."
             <009f01c161a9$aadcd110$dd00a8c0@jamessonyvaio> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 30 Oct 2001 22:03:05 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James,

I remind you that the difference between the timeline you suggested and the
timeline I suggested is about six months, and one of the consequences your
schedule is the chance that when the greatest effort is made, it will be "too
late".

When Masanobu Katoh summarized the results of the IDN survey at Stockholm,
only five short months ago, the data available was that speculators and IP
holders were the overwhelming "users" of an IDN (the VGRS RACE product). We
have more time than fatigued contributors, or eager marketers, are willing
to allow.

There are lots of people I wouldn't "stall the process" for (your words, not
mine), some vendors come to mind. The JET membership is not among them, not
in my mind, as they are ccTLD NICs, with a "duty to serve the community" [1].

Please do not rush, and please do not spend time looking for the hidden
insult to you. The only content of this note is time.

Eric

[1] rfc1591, March 1994  




From owner-idn@ops.ietf.org  Tue Oct 30 22:34:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21142
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 22:34:12 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ym0G-000AWM-00
	for idn-data@psg.com; Tue, 30 Oct 2001 19:25:20 -0800
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ym0F-000AWG-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 19:25:19 -0800
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 60C5BFFC17; Wed, 31 Oct 2001 11:25:21 +0800 (SGT)
Message-ID: <03c201c161bb$a35e7620$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
References: <200110310303.f9V335m15499@nic-naa.net>
Subject: Re: Note: WG Process - Was Re: [idn] Traditional-simplified, yet  again
Date: Wed, 31 Oct 2001 11:25:06 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I remind you that the difference between the timeline you suggested
and the
> timeline I suggested is about six months, and one of the consequences
your
> schedule is the chance that when the greatest effort is made, it will
be "too
> late".

Yes, and that is still a discussion on another thread in the wg on that
topic so follow up there.

But so far, my take is that there are more people who wants IDN WG to
produce some work so we can move on to discuss other issues than people
who wants IDN WG to slow down. I may be wrong so lets wait for that
discussion to complete.

> There are lots of people I wouldn't "stall the process" for (your
words, not
> mine), some vendors come to mind. The JET membership is not among
them, not
> in my mind, as they are ccTLD NICs, with a "duty to serve the
community" [1].

My note is fairly simple reminder to all that the WG proceed on drafts
in its core interest. We should focus our discussion on the core
interest.

Unpublished drafts or promised draft (be it 2 weeks or 2 months) are not
part of core interest and there should not be foul call when the wg
proceed without them.

I recieve private mails regularly that he/she is going to send in a
draft for review but eventually never made the group at all, some as
long as 18 months ago. Therefore, I am not referring to anyone in
particular.

-James Seng




From owner-idn@ops.ietf.org  Tue Oct 30 23:09:09 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21616
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 23:09:08 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ymVU-000B1s-00
	for idn-data@psg.com; Tue, 30 Oct 2001 19:57:36 -0800
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ymVT-000B1f-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 19:57:35 -0800
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id MAA26767;
	Wed, 31 Oct 2001 12:57:19 +0900
Message-ID: <00d001c161c0$414f3690$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Yves Arrouye" <yves@realnames.com>, <idn@ops.ietf.org>,
        "Paul Hoffman / IMC" <phoffman@imc.org>
References:  <7FC3066C236FD511BC5900508BAC86FE4D7E7F@trestles.internal.realnames.com> <p05101003b80509f76b14@[165.227.249.20]>
Subject: Re: [idn] Re: stringprep and unassigned code points
Date: Wed, 31 Oct 2001 12:58:09 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id XAA21616


----- Original Message ----- 
From: "Paul Hoffman / IMC" <phoffman@imc.org>
 > 
> >My only conclusion from that was that it is not correct to say that
> >applications or their supporting libraries (for Stringprep/Nameprep) will
> >not need to be upgraded.
> 
> No one ever said that they did not need to be upgraded. They do not 
> need to be upgraded in order to enter characters that are valid in 
> stored host names. There is a big difference.

People are familiar with case-insensitiveness in hostnames in URL.
They often type in WWW.AOL.COM with CAPSLOCK ON inadvertantly even 
after they saw lowercased advertized hostnames and
have been successful so far in reaching the right webhost for
LDH ones and will be so even for future Cyrillic IDN ones.

If they experience failure at the first attemp to visit uppercased
NEW script IDN webhost from the old nameprep browser, 
may of them will guess the webhost does not exist, and
will give up trying another lowercased new script webhost from their
past experience of case-insensitiveness in hostnames.
  
Soobok Lee

> 
> It is only a "nightmare" for the people who enter characters that are 
> mapped. Again, it would be silly for someone to advertise a name 
> knowing that people with older clients could not enter it.

> --Paul Hoffman, Director
> --Internet Mail Consortium
> 




From owner-idn@ops.ietf.org  Tue Oct 30 23:55:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22331
	for <idn-archive@lists.ietf.org>; Tue, 30 Oct 2001 23:55:38 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ynH5-000BhH-00
	for idn-data@psg.com; Tue, 30 Oct 2001 20:46:47 -0800
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ynH4-000BhA-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 20:46:46 -0800
Received: from [165.227.249.20] (165-227-249-20.client.dsl.net [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f9V4kf828867
	for <idn@ops.ietf.org>; Tue, 30 Oct 2001 20:46:41 -0800 (PST)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0510100db80531229948@[165.227.249.20]>
In-Reply-To: <00d001c161c0$414f3690$ec1bd9d2@temp>
References: 
 <7FC3066C236FD511BC5900508BAC86FE4D7E7F@trestles.internal.realnames.com>
 <p05101003b80509f76b14@[165.227.249.20]>
 <00d001c161c0$414f3690$ec1bd9d2@temp>
Date: Tue, 30 Oct 2001 20:46:36 -0800
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] Re: stringprep and unassigned code points
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 12:58 PM +0900 10/31/01, Soobok Lee wrote:
>People are familiar with case-insensitiveness in hostnames in URL.
>They often type in WWW.AOL.COM with CAPSLOCK ON inadvertantly even
>after they saw lowercased advertized hostnames and
>have been successful so far in reaching the right webhost for
>LDH ones and will be so even for future Cyrillic IDN ones.

How is this statement at all relevant to the topic being discussed? 
Are there any scripts that are being encoded in future versions of 
ISO 10646 that will be affected by CAPS LOCK?

Please note that the discussion we are having is about future 
characters and scripts being encoded *that also have nameprep 
mappings to other characters*. If future characters are included 
without any mappings, everything works just as the user would expect.

What Yves brought up is only valid if there are mappings; that will 
have to be explained better in the stringprep document.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Wed Oct 31 00:24:26 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22599
	for <idn-archive@lists.ietf.org>; Wed, 31 Oct 2001 00:24:25 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ynjn-000C9a-00
	for idn-data@psg.com; Tue, 30 Oct 2001 21:16:27 -0800
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ynjm-000C9S-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 21:16:27 -0800
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id OAA19165;
	Wed, 31 Oct 2001 14:16:20 +0900
Message-ID: <010f01c161cb$4adf0630$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "Paul Hoffman / IMC" <phoffman@imc.org>
References:  <7FC3066C236FD511BC5900508BAC86FE4D7E7F@trestles.internal.realnames.com> <p05101003b80509f76b14@[165.227.249.20]> <00d001c161c0$414f3690$ec1bd9d2@temp> <p0510100db80531229948@[165.227.249.20]>
Subject: Re: [idn] Re: stringprep and unassigned code points
Date: Wed, 31 Oct 2001 14:17:10 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id AAA22599


----- Original Message ----- 
From: "Paul Hoffman / IMC" <phoffman@imc.org>
To: <idn@ops.ietf.org>
Sent: Wednesday, October 31, 2001 1:46 PM
Subject: Re: [idn] Re: stringprep and unassigned code points


> At 12:58 PM +0900 10/31/01, Soobok Lee wrote:
> >People are familiar with case-insensitiveness in hostnames in URL.
> >They often type in WWW.AOL.COM with CAPSLOCK ON inadvertantly even
> >after they saw lowercased advertized hostnames and
> >have been successful so far in reaching the right webhost for
> >LDH ones and will be so even for future Cyrillic IDN ones.
> 
> How is this statement at all relevant to the topic being discussed? 
> Are there any scripts that are being encoded in future versions of 
> ISO 10646 that will be affected by CAPS LOCK?


Switching cases in Greek/Cyrillic IME need CAPS LOCK. Don't they?
New bicameral script IME's behavior on CAPS LOCK  may resemble them
as a natural choice.
 

> 
> Please note that the discussion we are having is about future 
> characters and scripts being encoded *that also have nameprep 
> mappings to other characters*. If future characters are included 
> without any mappings, everything works just as the user would expect.

X and Y  always look identical in the case of NFC X->Y . And,
script IME (or platform) often has its own preferred form between X or Y.
That's often beyond the choice and capability of the end user.
I am not sure how many NFC will be defined for new script.
But that theory will work if any.


Soobok Lee

> 
> What Yves brought up is only valid if there are mappings; that will 
> have to be explained better in the stringprep document.
> 
> --Paul Hoffman, Director
> --Internet Mail Consortium
> 




From owner-idn@ops.ietf.org  Wed Oct 31 00:34:49 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22729
	for <idn-archive@lists.ietf.org>; Wed, 31 Oct 2001 00:34:47 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yntB-000CJM-00
	for idn-data@psg.com; Tue, 30 Oct 2001 21:26:09 -0800
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yntA-000CJE-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 21:26:08 -0800
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 GAA22925;
	Wed, 31 Oct 2001 06:25:55 +0100 (MET)
Date: Wed, 31 Oct 2001 06:24:12 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Yves Arrouye <yves@realnames.com>,
        "'Paul Hoffman / IMC'" <phoffman@imc.org>, idn@ops.ietf.org
Subject: RE: [idn] Re: stringprep and unassigned code points
Message-ID: <6060855.1004509452@localhost>
In-Reply-To: <7FC3066C236FD511BC5900508BAC86FE4D7E75@trestles.internal.realnames.com>
References:  <7FC3066C236FD511BC5900508BAC86FE4D7E75@trestles.internal.realna
 mes.com>
X-Mailer: Mulberry/2.1.1 (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-10-30 16.34 -0800 Yves Arrouye <yves@realnames.com> wrote:

> - Application A uses a profile of Stringprep where say U+20000 and above
> are unassigned, because U+20000 was not in Unicode at the time that
> application was written. It generates queries for server S, getting
> Unicode code points from an operating-system provided input method. Per
> the Stringprep spec, and your explanation above, when A gets U+20000 it
> passes it untouched in the query.
> 
> - Server S benefits from a more recent implementation whose profile of
> Stringprep has U+20000 to U+200FF assigned. And it has some mapping for
> U+20000. Let's say we're talking DNS (what people here relate the most
> to), and it is using a Nameprep version with a map that says:
> 
> 	20000; 20021; Case map
> 
> (I could use deletion as well to go around David's argument of bicameral
> scripts). Strings that have been Name/String-prepped for server S have
> U+20000 mapped to U+20021. As a result, S and A cannot understand each
> other when S receives a string that has U+20000 in it. Unless you suggest
> that S should reprocess A's query, but I do not think that has been
> suggested.

The _intention_ of the versioning (I am not saying that is what the wording
is) is that the application which first encounters U+20000 must do one of
these two things:

 If it has support of the new version of stringprep
 - Reject the character because it belive it is unassigned

 If it doesn't have support for new version of stringprep
 - Map U+20000 -> U+20021

This implies that a user which happen to have support for a new version of
stringprep can register a domainname which include U+20000 (even though
U+20021 ends up in the DNS zonefile). This user presents the new domainname
to another user which have an old application.

Now, what happens?

The goal is (once again, this might not be what the text says) that the
application which the second user uses, which belive U+20000 is unassigned
should reject the domainname which this user entered.

This implies that the second user can not type in / use / whatever the
domainname which the first user have registered.


I saw that Paul said he has some ideas on how to explain this in text in
the document, so, yes, we will be more clear on this.

It is basically the same thing as someone else commented, that we in the
document have to be much more clear about what it means by "the first
application which encounters the domainname".

    paf




From owner-idn@ops.ietf.org  Wed Oct 31 00:51:21 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22834
	for <idn-archive@lists.ietf.org>; Wed, 31 Oct 2001 00:51:20 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yoAF-000CaD-00
	for idn-data@psg.com; Tue, 30 Oct 2001 21:43:47 -0800
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.33 #1)
	id 15yoAE-000Ca7-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 21:43:46 -0800
Received: (qmail 15487 invoked by uid 104); 31 Oct 2001 05:43:42 -0000
Received: from yves@realnames.com by friendly.realnames.com with qmail-scanner-0.96 (. Clean. Processed in 0.822525 secs); 31 Oct 2001 05:43:42 -0000
Received: from heaven.internal.realnames.com (10.1.5.39)
  by friendly.realnames.com with SMTP; 31 Oct 2001 05:43:41 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:1104]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <16553@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Tue, 30 Oct 2001 9:40:22 PM -0800
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2653.19)
	id <V3D1HDMH>; Tue, 30 Oct 2001 21:43:08 -0800
Message-ID: <7FC3066C236FD511BC5900508BAC86FE4D7E96@trestles.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: =?iso-8859-1?Q?=27Patrik_F=E4ltstr=F6m=27?= <paf@cisco.com>,
        "'Paul Hoffman / IMC'" <phoffman@imc.org>, idn@ops.ietf.org
Subject: RE: [idn] Re: stringprep and unassigned code points
Date: Tue, 30 Oct 2001 21:39:35 -0800
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

> The _intention_ of the versioning (I am not saying that is what the
> wording
> is) is that the application which first encounters U+20000 must do one of
> these two things:
> 
>  If it has support of the new version of stringprep
>  - Reject the character because it belive it is unassigned
> 
>  If it doesn't have support for new version of stringprep
>  - Map U+20000 -> U+20021

I think you meant the opposite (i.e. reject if not new version, map
otherwise). Right?

> This implies that a user which happen to have support for a new version of
> stringprep can register a domainname which include U+20000 (even though
> U+20021 ends up in the DNS zonefile). This user presents the new
> domainname
> to another user which have an old application.

Is the user required to have the stringprep support, or the registrar's
registration software (or even some other guy's software down the chain)? I
would think the latter. I don't think we want to ask the HTML people for a
new kind of input attribute to specify that the input should be
Stringprepped/Nameprepped just to support the business of name registration
;)

> Now, what happens?
> 
> The goal is (once again, this might not be what the text says) that the
> application which the second user uses, which belive U+20000 is unassigned
> should reject the domainname which this user entered.

No. I don't think so. Remember this section 6 of stringprep, that says that
for queries (which is what I believe you are talking about now) applications
should treat U code points the same as AO? Well U+20000 being U, it will be
passed on, since this second application is making queries.

Anyway, I think Paul understands what I wanted to make sure people would be
aware of. I'm happy with that and ready to dispose of this particular
thread...

> It is basically the same thing as someone else commented, that we in the
> document have to be much more clear about what it means by "the first
> application which encounters the domainname".

That is definitely true! It may also be a can of worms: think multi-tiered
registration systems. Maybe an avenue is to look at the first application
which *needs* to process the string according to a profile in order to be
able to manipulate it. Don't know if that's easier to define...

YA




From owner-idn@ops.ietf.org  Wed Oct 31 01:18:38 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24641
	for <idn-archive@lists.ietf.org>; Wed, 31 Oct 2001 01:18:37 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yoOm-000Cot-00
	for idn-data@psg.com; Tue, 30 Oct 2001 21:58:48 -0800
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yoOl-000Con-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 21:58:47 -0800
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 GAA25370;
	Wed, 31 Oct 2001 06:58:32 +0100 (MET)
Date: Wed, 31 Oct 2001 06:58:16 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Yves Arrouye <yves@realnames.com>,
        "'Paul Hoffman / IMC'" <phoffman@imc.org>, idn@ops.ietf.org
Subject: RE: [idn] Re: stringprep and unassigned code points
Message-ID: <6183514.1004511496@localhost>
In-Reply-To: <7FC3066C236FD511BC5900508BAC86FE4D7E96@trestles.internal.realnames.com>
References:  <7FC3066C236FD511BC5900508BAC86FE4D7E96@trestles.internal.realna
 mes.com>
X-Mailer: Mulberry/2.1.1 (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-10-30 21.39 -0800 Yves Arrouye <yves@realnames.com> wrote:

>> The _intention_ of the versioning (I am not saying that is what the
>> wording
>> is) is that the application which first encounters U+20000 must do one of
>> these two things:
>> 
>>  If it has support of the new version of stringprep
>>  - Reject the character because it belive it is unassigned
>> 
>>  If it doesn't have support for new version of stringprep
>>  - Map U+20000 -> U+20021
> 
> I think you meant the opposite (i.e. reject if not new version, map
> otherwise). Right?

Oh, sorry. Absolutely. You are right.

>> This implies that a user which happen to have support for a new version
>> of stringprep can register a domainname which include U+20000 (even
>> though U+20021 ends up in the DNS zonefile). This user presents the new
>> domainname
>> to another user which have an old application.
> 
> Is the user required to have the stringprep support, or the registrar's
> registration software (or even some other guy's software down the chain)?

You are talking about the registration process? To be honest....I don't
care. I think this is up to the policy a registry has.

My personal take (note, personal) is that the following steps have to be
taken before a newly assigned codepoint is registered in any zone:

- A new version of stringprep is registered with the new codepoint and
  also mapping
- The registry make a decision to use this new version of nameprep,
  and change communication methods with registrars so it is possible
  to in some way pass the domain name to the registry
- The registrars accept domain names from registrants which use the new
  codepoint

My point is that I see it being an "opt-in" system for every registry (as
in zone administrator) to make a decision on what version (if any) of
stringprep is accepted, and given such a decision, the ability to enter new
strings goes down the chain towards the registrant.

> I would think the latter. I don't think we want to ask the HTML people
> for a new kind of input attribute to specify that the input should be
> Stringprepped/Nameprepped just to support the business of name
> registration ;)

As I said above, it is out of scope (1) forcing a registry adopting a
specific registry and (2) forcing a registrar to be able to accept domain
names via specific communication channels. Yes, many registrars use "the
web", but far from all. In some cases, paper is used which give much
different problems. What about "voice over the phone"?

The way I see it, this is how registrars can compete with each other. And I
say this in a positive manner.

>> Now, what happens?
>> 
>> The goal is (once again, this might not be what the text says) that the
>> application which the second user uses, which belive U+20000 is
>> unassigned should reject the domainname which this user entered.
> 
> No. I don't think so. Remember this section 6 of stringprep, that says
> that for queries (which is what I believe you are talking about now)
> applications should treat U code points the same as AO? Well U+20000
> being U, it will be passed on, since this second application is making
> queries.

Ok. I understand where the text is unclear. What I am talking about is a
query, yes. The idea is that the application which is generating/sending
the query is doing the stringprep, has the old version, and reject the
codepoint. So the codepoint is not even sent to the server (which _DO_
understand the new codepoint).

Of course, _any_ application which see a domain name and understand
nameprep can do nameprep, and (a) pass on unassigned codepoints and (b)
pass/map/reject codepoints it understand.

The important thing is that nothing unassigned end up in the zonefile.
Reason for this is that if someone register a domainname with U+20000
before that codepoint is added to Unicode, users will end up in trouble at
the point in time when the codepoint is added, and mapped to something
different.

So, the policy the registry has is the most important.

> Anyway, I think Paul understands what I wanted to make sure people would
> be aware of. I'm happy with that and ready to dispose of this particular
> thread...

Yes, I think he understand.

>> It is basically the same thing as someone else commented, that we in the
>> document have to be much more clear about what it means by "the first
>> application which encounters the domainname".
> 
> That is definitely true! It may also be a can of worms: think multi-tiered
> registration systems. Maybe an avenue is to look at the first application
> which *needs* to process the string according to a profile in order to be
> able to manipulate it. Don't know if that's easier to define...

I don't know either.

Let's see when we have some new text on the table. We agree it should be
changed so it is more clear.

   paf




From owner-idn@ops.ietf.org  Wed Oct 31 01:33:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA26675
	for <idn-archive@lists.ietf.org>; Wed, 31 Oct 2001 01:33:57 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yof1-000D3F-00
	for idn-data@psg.com; Tue, 30 Oct 2001 22:15:35 -0800
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.33 #1)
	id 15yof0-000D33-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 22:15:34 -0800
Received: (qmail 19735 invoked by uid 104); 31 Oct 2001 06:15:33 -0000
Received: from yves@realnames.com by friendly.realnames.com with qmail-scanner-0.96 (. Clean. Processed in 0.82999 secs); 31 Oct 2001 06:15:33 -0000
Received: from heaven.internal.realnames.com (10.1.5.39)
  by friendly.realnames.com with SMTP; 31 Oct 2001 06:15:32 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:3473]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <18278@heaven.internal.realnames.com>
	 for <idn@ops.ietf.org>; Tue, 30 Oct 2001 10:11:54 PM -0800
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2653.19)
	id <V3D1HFAW>; Tue, 30 Oct 2001 22:14:40 -0800
Message-ID: <7FC3066C236FD511BC5900508BAC86FE4D7E97@trestles.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: =?iso-8859-1?Q?=27Patrik_F=E4ltstr=F6m=27?= <paf@cisco.com>,
        "'Paul Hoffman / IMC'" <phoffman@imc.org>, idn@ops.ietf.org
Subject: RE: [idn] Re: stringprep and unassigned code points
Date: Tue, 30 Oct 2001 22:11:08 -0800
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

> > No. I don't think so. Remember this section 6 of stringprep, that says
> > that for queries (which is what I believe you are talking about now)
> > applications should treat U code points the same as AO? Well U+20000
> > being U, it will be passed on, since this second application is making
> > queries.
> 
> Ok. I understand where the text is unclear. What I am talking about is a
> query, yes. The idea is that the application which is generating/sending
> the query is doing the stringprep, has the old version, and reject the
> codepoint. So the codepoint is not even sent to the server (which _DO_
> understand the new codepoint).

That is actually against Stringprep section 6.1 which states (note the
MUST):

"Applications creating queries MUST treat U code points as if they were
AO when preparing the query to be entered in the process described by a
profile of stringprep."

Which makes sense since it provides for a very good chance that the
application will be able to cope with later revisions of Unicode (modulo the
caveats that started this whole thread).

> The important thing is that nothing unassigned end up in the zonefile.

Agreed. Stringprep is clear on that, no ambiguity there. I think it is also
clear on the query (the part I quoted above). The ambiguities are in the
assumptions that are then made and that can be broken (eg: passing
unassigned code points is a 100% guarantee of working with future
registrations; it is not if mapping tables change but is in the other
cases). That is what will benefit from some clarifications.

YA




From owner-idn@ops.ietf.org  Wed Oct 31 02:41:51 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08486
	for <idn-archive@lists.ietf.org>; Wed, 31 Oct 2001 02:41:50 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15yppj-000E3u-00
	for idn-data@psg.com; Tue, 30 Oct 2001 23:30:43 -0800
Received: from imo-m07.mx.aol.com ([64.12.136.162])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15yppi-000E3o-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 23:30:42 -0800
Received: from DougEwell2@cs.com
	by imo-m07.mx.aol.com (mail_out_v31_r1.8.) id i.140.3da7427 (24899);
	Wed, 31 Oct 2001 02:30:35 -0500 (EST)
From: DougEwell2@cs.com
Message-ID: <140.3da7427.29110299@cs.com>
Date: Wed, 31 Oct 2001 02:30:33 EST
Subject: Re: [idn] mailing list malfunction
To: idn@ops.ietf.org
CC: jseng@pobox.org.sg
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: CompuServe 2000 32-bit sub 113
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

jseng@pobox.org.sg wrote:

> there was a brief technical outrage on the mailing list

At first I thought James meant there had been an "outage," but I like his 
version much better.  \u263a

-Doug Ewell
 Fullerton, California



From owner-idn@ops.ietf.org  Wed Oct 31 02:48:13 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08539
	for <idn-archive@lists.ietf.org>; Wed, 31 Oct 2001 02:48:12 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ypuy-000E9M-00
	for idn-data@psg.com; Tue, 30 Oct 2001 23:36:08 -0800
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ypux-000E9G-00
	for idn@ops.ietf.org; Tue, 30 Oct 2001 23:36:08 -0800
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 361FFFFC31; Wed, 31 Oct 2001 15:36:21 +0800 (SGT)
Message-ID: <075a01c161de$b3624380$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <jseng@pobox.org.sg>
To: <DougEwell2@cs.com>, <idn@ops.ietf.org>
References: <140.3da7427.29110299@cs.com>
Subject: Re: [idn] mailing list malfunction
Date: Wed, 31 Oct 2001 15:36:06 +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.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Took me 2 private mails to discover my own joke, which my lousy
grammer/speller checker have a habit of doing so.

(Yes, blame the software if you can! Damnit. Technology is supposed to
solve everything! :-)

-James Seng

----- Original Message -----
From: <DougEwell2@cs.com>
To: <idn@ops.ietf.org>
Cc: <jseng@pobox.org.sg>
Sent: Wednesday, October 31, 2001 3:30 PM
Subject: Re: [idn] mailing list malfunction


> jseng@pobox.org.sg wrote:
>
> > there was a brief technical outrage on the mailing list
>
> At first I thought James meant there had been an "outage," but I like
his
> version much better.  \u263a
>
> -Doug Ewell
>  Fullerton, California




From owner-idn@ops.ietf.org  Wed Oct 31 15:27:43 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29944
	for <idn-archive@lists.ietf.org>; Wed, 31 Oct 2001 15:27:41 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15z1WV-000OoS-00
	for idn-data@psg.com; Wed, 31 Oct 2001 11:59:39 -0800
Received: from femail37.sdc1.sfba.home.com ([24.254.60.31])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15z1WU-000OoM-00
	for idn@ops.ietf.org; Wed, 31 Oct 2001 11:59:38 -0800
Received: from c1340594a ([65.11.104.12]) by femail37.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20011031195936.EFNH1908.femail37.sdc1.sfba.home.com@c1340594a>;
          Wed, 31 Oct 2001 11:59:36 -0800
Message-ID: <014101c16246$b4438080$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "John C Klensin" <klensin@jck.com>
Cc: <idn@ops.ietf.org>
References:  <4.2.0.58.J.20011026160859.02f495c0@localhost> <78155142.1004078274@P2>
Subject: Unicode/10646 History (was Re: [idn] An ignorant question about TC<-> SC)
Date: Wed, 31 Oct 2001 12:00:35 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

The history of the Unicode/10646 merger is really irrelevant to TC<->SC, but
there are some inaccuracies that should not be left hanging.


> This is obviously the dream of someone ...

Your dream of having every character image seen on a page representing
exactly the same string length in a computer basically only works for ASCII.
Most of the properties that you find unhelpful in Unicode are a property of
human scripts, and many were already in DIS-1 (the 10646 DIS that failed its
ballot). Scripts such as Arabic, Hebrew, and most South and Southeast Asian
languages require combining marks; so for them your equation is broken. For
compatibility with the ISO bibliographic standards, combining marks are also
required for Latin, Cyrillic and Greek.

What the Unicode standard did put into place is a programmatic mechanism for
*identifying* sequences that should always be visually indistinguishable and
should always be considered equivalent -- the equivalency issue happens even
if there are no precomposed characters simply because of the possibility of
different orderings of combining characters. So there is a well-defined,
standard mechanism, rather than leaving the identification up to each
individual implementer, and having thousands of different implementations
have different rules.

DIS-1 suffered from a number of severe flaws:

* Since no code points were permitted where any byte was a C0 or C1 control,
there were only 35,271 possible code points on the BMP, instead of 64K.
Moreover, there were compatibility issues with C wide characters, since
zero-extended ASCII was not a valid DIS 10646 wide char.

* The 2-byte form in DIS-1 was variable -- one would use announcer sequences
to pick subsets in the 2-byte form. This is ISO 2022 all over again, and
horrible to process. The adoption rate by industry would have been
*severely* compromised at the unpalatable choice of either quadrupling text
memory (and it was hard enough to get them to move to 16 bits per character)
or having a 2022-like mess to deal with. There would still be no getting
around the multiple representations for what would otherwise be
indistinguishable characters shared by the CJK languages.

* There was no UTF-8: the first UTF (UTF-1) was developed by Unicode to
encapsulate the merged Unicode/10646 in a sequence of compatible bytes. That
UTF was superceded by the superior UTF-8, but the principles were the same.

For these and other reasons, the DIS-1 failed its ballot. The result of the
merger between Unicode and 10646 is far better, has been widely implemented
and meets the requirements of many organizations: software vendors, W3C,
ECMA, and the many national standards organizations such as Japan, China,
Republic of Korea, Denmark, Sweden and many other countries that have
adopted and translated the ISO standard.

> Doing it as an editorial substitution
> prevented any further review by interests within most (or any?)
> of the ISO Member Bodies, nor was it possible for the other
> subcommittees who had stated requirement to SC2 to comment on
> the new version.

There was a rather long ballot period for the DIS, with ample time for
comment by both member bodies and other ISO subcommittees.

> The Unicode standard of that time had come out of a consortium
> of, essentially, printer manufacturers.

We have heard the "printer company" urban legend before. Some of the
companies originally involved might be thought of as "printer companies",
but most were not. For example, Microsoft and IBM are not usually thought of
as "printer companies"! From the beginning, the focus was on Unicode as an
encoding that would work as an internal process code in implemenations, as
well as an encoding for interchange. Items that *look* like printer-ROM
hacks, like the addition of the Zapf dingbats, were pushed by software
companies like WordPerfect, and not by HP, Apple, or Xerox.

We are very curious as to the origin of this "printer company" story; where
did you hear this?

> Their primary design
> criteria apparently included

The design criteria were not at all as you state:

> preservation of existing and
> heavily-used character sets as proper block subsets (to avoid
> having to change ROMs); keeping to a minimum number of octets

Both the DIS-1 and Unicode segmented scripts into blocks, and generally
ordered characters in a script to match existing ordering in standards in
use if there were not reasons to change it, and both preserved Latin-1, but
that was just the sensible thing to do. There was no notion of having
unchanged printer ROMs.

> keeping to a minimum number of octets per character, especially [then]
frequently-used characters
> (memory was expensive and printer memory (and "board real
> estate") was even more expensive than computer memory);

Unicode was designed as a 16 bit standard. Before the merger, there was no
UTF-8. The design was precisely 2 octets per character, independent of
frequency.

>  and, to
> the extent that they didn't conflict with the above, "if they
> look alike, they are alike" and "if it is possible to think of
> it as a font difference, it is" rules.

The design criteria was to encode characters, not glyphs. For more on the
difference, see http://www.unicode.org/unicode/reports/tr17/

> And, using those rules,
> they assumed that 16 bits would be enough, forever.

Yes, under the original design principles of Unicode -- although not
matching your list -- 16 bits would have been enough for the commercially
significant characters of the world. (That depended on the use of IDS-like
mechanisms for uncommon CJK characters, using jamo sequences instead of
composed Hangul syllables, etc.) One of the changes brought about by the
merger was the recognition that in the new merged architecture -- and with
the increased number of presentation forms – this was insufficient. This led
to the development of UTF-16.

> * preservation of the properties and locality of
> existing, heavily-used character sets versus optimality
> for, e.g., collation (for example, in a mixed case
> language in which both cases are expected to be used
> regularly, it would be much more convenient to have the
> characters arranged as
>           {Upper1, Lower1, Upper2, Lower2, ... }
> rather than
>   {Upper1, Upper2, ..., Lower1, Lower2, ... }

This actually does *not* solve the collation problem for any language that I
know of. Case (and usually accent) differences are at a different level than
base letter differences. They *cannot* be solved by a rearrangement of
codes.  See UCA (or the synchronized, equivalent ISO standard ISO/IEC 14651)
for more details (http://www.unicode.org/unicode/reports/tr10/).

However, you are right in terms of implemenation that if upper/lowercase
differences had always been at a fixed offset, it would be somewhat easier
to build more compact mapping tables for upper/lower/titlecasing operations.
And there are other cases where in hindsight a rearrangement of codes would
have lead to simpler implementations.

> * Accurate transcription from a printed form, especially
> in an unknown language, into the coded character set
> versus keeping languages distinct or scripts together.

I see what you are trying to get at, but *no* character standard attempts to
preserve printed forms (see the discussion of characters vs glyphs).

This is perhaps better stated as:

* Determining the set of underlying abstract characters -- and the
interactions among them -- that are to represent the wide variety of glyphs
used to write different languages.

> * String comparisons versus the compactness of a
> character set
>
> * Overall size versus avoiding "unification".

As in the last point -- *every* character standard "unifies" glyphs into
abstract characters. GB is unified. JIS is unified. The rules for
unification used by the IRG was developed from the original rules used in
unifying JIS. Even Latin-1 is unified: after all, we could also have encoded
different Ö, Ü, á, etc. for French, German, Polish, etc, since there are
different typographic standards in those countries for the placement and
shape of accents.

>
> and so on.
>
> And, in my personal opinion (then and now) the Unicode designers
> were a little naive about the number of characters which a UCS
> would ulimately need to accomodate and were a little too biased
> in their thinking by their then-existing market.  That market
> was mostly North American and Western European, their deployed
> products were primarily deployed in those markets, and backward
> compatibility with existing devices and thinking probably
> impacted optimization decisions about the character set's
> organization.   But, as I said at the beginning, times have
> changed -- the current UTC is clearly trying to work around the
> design limitations imposed by that starting point.

This is absolutely untrue. The developers of Unicode had worked
*extensively* with non-Roman markets. Although many of the developers were
Americans, many were not. And the companies forming Unicode had active
subsidiaries in a wide range of non-Roman markets -- including CJK, and
those subsidiaries certainly made their issues known.

Joe Becker was up front in 1989 that the number of "things" that people
would eventually want to represent was somewhere in the vicinity of 250,000:
that estimate has held up remarkably well, 12 years later. The naivite  was
not regarding the number of characters, but rather regarding the prospects
for being able to constrain the architecture of the UCS (as discussed
above), and use Private Use for archaic scripts, special-use symbols, etc.

>
> The bottom line is that Unicode is what we have.  It is lots
> better for our purposes than its 1.0 version.  ISO 10646 DIS-1
> is an historical footnote (as is this entire note).  We _need_
> to figure out how to make what we have work. That implies
> either abandoning other sorts of ideas, or ideas that would
> depend on an entirely different coding structure.

Yes, Unicode/10646 is what we have now. It is not perfect -- those of us who

worked on it from the beginning know the warts the best! But most of the
complexities are simply due to the complexities of human scripts, and the
Unicode consortium continually works to enhance the standard, data tables,
properties, technical reports, technical standards, guidelines, and other
information. This information is absolutely vital for producing
interoperable implementations.

Unicode/10646 is in widespread use, has a large body of implementations and
is the foundation for any system that is to deal with text around the world.

> Or we need to
> move other sorts of ideas into additional layers where we can
> create more flexibility than the DNS gives us.  Or, of course,
> we can get used to the idea that reaching a conclusion on
> internationalized domain names, or even internationalized access
> to them, will take a _very_ long time.
>
> After all, it has taken us thousands of years to create the
> large variety of languages and writing systems (some might say
> "the total mess") we have in the world today.  Perhaps it is
> hubris to believe that we can reconcile all of the differences
> as part of a DNS effort.  But, since the alternative is giving
> up, and the requirements are important, I think we need to focus
> in on the important and solvable problems and try to move
> forward, rather than getting stuck on the historical sequences
> that got us here, or on interesting research ideas, or on
> unsolvable problems.

Your bottom line is core, and absolutely correct: "I think we need to focus
in on the important and solvable problems and try to move forward".

I only take the time to correct some of the items above because a mistaken
impression of the process of development of Unicode and ISO 10646 might lead
people to have a mistaken impression of the quality of Unicode and 10646, or
the organizations behind them.

>      john



Mark


—————

Δός μοι ποῦ στῶ, καὶ κινῶ τὴν γῆν — Ἀρχιμήδης
[http://www.macchiato.com]

----- Original Message -----
From: "John C Klensin" <klensin@jck.com>
To: "Martin Duerst" <duerst@w3.org>
Cc: <idn@ops.ietf.org>
Sent: Friday, October 26, 2001 02:37
Subject: Re: [idn] An ignorant question about TC<-> SC


> Martin,
>
> For better or worse, your explanation and history is somewhat
> revisionist.   While I believe the UTC has done an outstanding
> job in more recent years to try to clean things up and
> generalize them --in the directions you suggest-- my strong
> recollection of the battles over "UCS" and what became 10646
> follows.   NOTE: most of the WG may not want (or need) to read
> this.  It goes over ground that we've been over before, and I am
> writing this primarily in the hope that we can avoid cycling
> through it again, in pieces.  The conclusion is that
> Unicode/10646 is what we have today, and what we are stuck with,
> and that arguments about history and design criteria are largely
> pointless.
>
> For those who want the history, at least as I remember it, read
> on...
>
> The original UCS effort, leading to what was known as 10646
> DIS-1, was focused on an effort whose criteria included a strong
> focus on comparability and generalized applications use.  That
> effort included a rather extensive liaison/ requirements
> statement from the then-ISO TC97 subcommittee on programming
> languages to the then TC97 SC2 that was accepted by SC2.  That
> statement of requirements asked for a UCS that contained many of
> the properties that we've discovered in the last few years would
> be really helpful if they were present in Unicode, but aren't
> there.  For example, there was to be no mixing of precomposed
> characters and those that were built up as a sequence of code
> points, using either non-spacing or overstrike ideas.   And
> there was to be no overlaying of characters that looked alike
> but were different.
>
> This is obviously the dream of someone doing string comparisons
> and report-writing (which programming language people do, or
> did, very often), since every character image seen on a page
> would represent exactly the same string length in a computer,
> i.e.,
>   length-in-visual-units (string) =
>       length-in-character-units (string)
> always.
>
> And, e.g., what I see as the hardest part of the TC <-> SC
> problem would not have existed, aince there would have been no
> confusion between, e.g., a Chinese character and a
> similar-looking Korean or Japanese one.
>
> The result, coming into the DIS-1 vote, did not completely meet
> those critera (for example, it did contain provision for
> overlaying glyphs), although it was arguably close to it.  It
> was also large (requiring four octets) and, in some ways, fairly
> unwieldy.  And, of course, by virtue of not having overlaying,
> transposition from written text in an unknown language into a
> coded character set representation was a far worse problem than
> the one we struggle with today.  And, if I recall, the draft
> hadn't preserved contingency and ordering of important and
> frequently used existing character sets as block subsets.
>
> In the ISO ballot resolution process, supposedly to handle some
> negative votes against DIS-1, the then-complete proposal was
> replaced, as an editorial substitution, with the then-current
> version of Unicode.  Doing it as an editorial substitution
> prevented any further review by interests within most (or any?)
> of the ISO Member Bodies, nor was it possible for the other
> subcommittees who had stated requirement to SC2 to comment on
> the new version.
>
> The Unicode standard of that time had come out of a consortium
> of, essentially, printer manufacturers.  Their primary design
> criteria apparently included preservation of existing and
> heavily-used character sets as proper block subsets (to avoid
> having to change ROMs); keeping to a minimum number of octets
> per character, especially [then] frequently-used characters
> (memory was expensive and printer memory (and "board real
> estate") was even more expensive than computer memory); and, to
> the extent that they didn't conflict with the above, "if they
> look alike, they are alike" and "if it is possible to think of
> it as a font difference, it is" rules.  And, using those rules,
> they assumed that 16 bits would be enough, forever.
>
> At this late date, the most reaaonable thing that can be said
> about the different between the approaches represented by
> Unicode and 10646 DIS-1 is that they started from different
> criteria and made the tradeoffs differently.  Which approach is
> "better" depends on where one starts and what one considers most
> important.   And both represent compromises with their original
> criteria, due to conflicts among their requirements, so neither
> was (or would have been) completely consistent internally.
>
> Any complex, international, character set effort that started
> more or less from scratch would face similar tradeoffs, e.g.:
>
> * preservation of the properties and locality of
> existing, heavily-used character sets versus optimality
> for, e.g., collation (for example, in a mixed case
> language in which both cases are expected to be used
> regularly, it would be much more convenient to have the
> characters arranged as
>           {Upper1, Lower1, Upper2, Lower2, ... }
> rather than
>   {Upper1, Upper2, ..., Lower1, Lower2, ... }
>
> * Accurate transcription from a printed form, especially
> in an unknown language, into the coded character set
> versus keeping languages distinct or scripts together.
>
> * String comparisons versus the compactness of a
> character set
>
> * Overall size versus avoiding "unification".
>
> and so on.
>
> And, in my personal opinion (then and now) the Unicode designers
> were a little naive about the number of characters which a UCS
> would ulimately need to accomodate and were a little too biased
> in their thinking by their then-existing market.  That market
> was mostly North American and Western European, their deployed
> products were primarily deployed in those markets, and backward
> compatibility with existing devices and thinking probably
> impacted optimization decisions about the character set's
> organization.   But, as I said at the beginning, times have
> changed -- the current UTC is clearly trying to work around the
> design limitations imposed by that starting point.
>
> The bottom line is that Unicode is what we have.  It is lots
> better for our purposes than its 1.0 version.  ISO 10646 DIS-1
> is an historical footnote (as is this entire note).  We _need_
> to figure out how to make what we have work.  That implies
> either abandoning other sorts of ideas, or ideas that would
> depend on an entirely different coding structure.  Or we need to
> move other sorts of ideas into additional layers where we can
> create more flexibility than the DNS gives us.  Or, of course,
> we can get used to the idea that reaching a conclusion on
> internationalized domain names, or even internationalized access
> to them, will take a _very_ long time.
>
> After all, it has taken us thousands of years to create the
> large variety of languages and writing systems (some might say
> "the total mess") we have in the world today.  Perhaps it is
> hubris to believe that we can reconcile all of the differences
> as part of a DNS effort.  But, since the alternative is giving
> up, and the requirements are important, I think we need to focus
> in on the important and solvable problems and try to move
> forward, rather than getting stuck on the historical sequences
> that got us here, or on interesting research ideas, or on
> unsolvable problems.
>
>      john
>
>
>
>
> --On Friday, 26 October, 2001 16:31 +0900 Martin Duerst
> <duerst@w3.org> wrote:
>
> > At 02:37 01/10/25 -0700, liana Ye wrote:
> >
> >> In another word, the fundimental work from UCS is the to table
> >> glyphs based on their visual distinction.
> >
> > That is simply not true. The fundamental work is to make
> > sure that the result is best usable by average users for
> > their average purpose (writing electronic texts).
> >
> > There have been a lot of requests to use finer distinctions,
> > e.g. from researchers or from people who publish dictionaries.
> > They were rejected, because they would confuse the average
> > user and the average use more than they would help.
> >...
>
>
>
>
>





From owner-idn@ops.ietf.org  Wed Oct 31 21:15:14 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07464
	for <idn-archive@lists.ietf.org>; Wed, 31 Oct 2001 21:15:14 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15z76p-0003q1-00
	for idn-data@psg.com; Wed, 31 Oct 2001 17:57:31 -0800
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15z76n-0003pt-00
	for idn@ops.ietf.org; Wed, 31 Oct 2001 17:57:29 -0800
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.6/8.9.3) with ESMTP id fA11xIm20211;
	Wed, 31 Oct 2001 20:59:18 -0500 (EST)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200111010159.fA11xIm20211@nic-naa.net>
To: "Mark Davis" <mark@macchiato.com>
cc: "John C Klensin" <klensin@jck.com>, idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: Unicode/10646 History (was Re: [idn] An ignorant question about TC<-> SC) 
In-Reply-To: Your message of "Wed, 31 Oct 2001 12:00:35 PST."
             <014101c16246$b4438080$0c680b41@c1340594a> 
Date: Wed, 31 Oct 2001 20:59:18 -0500
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Mark,

As you're feeling your oats.

>                                                                  ... but
> there are some inaccuracies that should not be left hanging.

I wish the UTC felt that way about a) making any recommendation as a
body concerning any any attempt by another body to utilize the work
product of the UTC, and b) specifically making an operational suggestion
that does not appear to be accompanied by operational data, or a non-naive
understanding of the dns.

...

> We are very curious as to the origin of this "printer company" story; where
> did you hear this?

That's "printer consortia". Private, with $$ to sit at the table. Like W3C
now, but worse.

It was my impression in 1991, at UTR#4-time, at 2.0-time, and at UTR#8-time.

It [Unicode] didn't spring out of the operating system industry. So which
peripheral device consortia is left? Disks? Modems?

It is still my impression today. Having writ XPG/1, and XPG/4.2, and knowing
most of the P1003.x particpants of the 90's, and the business and technical
managements of Bull, ICL, Siemens, Olivetti, Nixdorf, IBM, Sun, SGI, and HP
during the 90's -- I really don't care how much you'd prefer to believe that
the non-printer lines of business considered Unicode as strategic. I watched
them staff-up for the iso2022 period, and down-staff, and staff-up for the
File-System-Safe period, and down-staff. "Them" means Unix vendor business
core unit, not printer unit.

Just because we (first Apple, then MicroSoft, then us Unix vendors) all got
within a transform format of Unicode by 1996 doesn't mean that Unicode was
a core value proposition. At HP HP-15 was vastly more important, and at SMI
the multi-byte code-path for sort(1) was simply abominable, HP-UX 10.0 and
Solaris 2.4 and 2.5 -- when we multi-byted (UTF-8'd the tty, the file system,
and all the user libs and apps).

> I only take the time to correct some of the items above because a mistaken
> impression of the process of development of Unicode and ISO 10646 might lead
> people to have a mistaken impression of the quality of Unicode and 10646, or
> the organizations behind them.

Jeez. I made mistakes in XPG/1. I let Nixdorff shave bits off a pid for an
early SMP-which-processor identifier. I made mistakes in Spec1170 also.
You guys act as if you never goofed -- and you guys actually put Klingon,
Esperanto and Pharonic Egyptian in your runqueue -- ahead of living languages.

We could replace Unicode as the basis for work on internationalizing the dns.
It wouldn't be a lark, but at least we already know what _not_ to do when
creating encoding for identifiers, and in terms of incongruity, it couldn't
be worse than ACE-for-labels, something-else-for-everything-else.

To quote from the report of the 1996 invitational workshop (not one was a
Unix implementor)

   E: The IAB should encourage the IRTF to create a research group to
   explore the open issues of character sets on the Internet. This group
   should set its sights much higher than this workshop did.

That was a sound recommendation. It hasn't been acted on. It should have
been, and it still should be in the present.

Just to keep things honest, from rfc2044:

   UTF-8 was originally a project of the X/Open Joint
   Internationalization Group XOJIG with the objective to specify a File
   System Safe UCS Transformation Format [FSS-UTF] that is compatible
   with UNIX systems, supporting multilingual text in a single encoding.
   The original authors were Gary Miller, Greger Leijonhufvud and John
   Entenmann.

I replaced John Entenmann (SMI) on XOJIG in 1995, and Gary Miller (IBM)
and I came out with our code-set independent architectures for our two
repsective operating systems (AIX and Solaris) in 1995/6.

We have bigger fish to fry than the ruffled feathers of Unicadettes, or
anyone else for that matter.

Anyone who wants to say they heard it from me is free to so state.

Some days I look at national standards and think, is that really any worse
than this mess?

Eric



From owner-idn@ops.ietf.org  Wed Oct 31 23:52:05 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10760
	for <idn-archive@lists.ietf.org>; Wed, 31 Oct 2001 23:52:05 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15z9cR-0005xZ-00
	for idn-data@psg.com; Wed, 31 Oct 2001 20:38:19 -0800
Received: from mx-out.daemonmail.net ([209.75.5.3])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15z9cQ-0005xR-00
	for idn@ops.ietf.org; Wed, 31 Oct 2001 20:38:18 -0800
Received: from mx0.emailqueue.net (localhost.daemonmail.net [127.0.0.1])
	by mx-out.daemonmail.net (8.9.3/8.9.3) with SMTP id UAA39270;
	Wed, 31 Oct 2001 20:38:15 -0800 (PST)
	(envelope-from rosenne@qsm.co.il)
Received: from Jony (Jony [212.150.108.110])
	by mail.qsm.co.il with ESMTP id IDA0oHG2
	Wed, 31 Oct 2001 20:38:09 -0700 (PST)
From: "Jonathan Rosenne" <rosenne@qsm.co.il>
To: "'Eric Brunner-Williams in Portland Maine'" <brunner@nic-naa.net>,
        "'Mark Davis'" <mark@macchiato.com>
Cc: <idn@ops.ietf.org>
Subject: RE: Unicode/10646 History (was Re: [idn] An ignorant question about TC<-> SC) 
Date: Thu, 1 Nov 2001 06:37:54 +0200
Message-ID: <000b01c1628e$fd4c5200$74640ac2@smartel>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <200111010159.fA11xIm20211@nic-naa.net>
Importance: Normal
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

For the record: 

1. ISO-10646 DIS 1 was unacceptable from our point of view, i.e. Hebrew,
and Israel voted against it without any other consideration.

2. There was a proposal that ISO should consider printer codes, as a
follow on to ISO 6429, but it did not get very far.

Jony





