From owner-idn@ops.ietf.org  Wed Aug  1 06:28:08 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA25793
	for <idn-archive@lists.ietf.org>; Wed, 1 Aug 2001 06:28:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Rt02-0008UY-00
	for idn-data@psg.com; Wed, 01 Aug 2001 03:13:10 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Rt01-0008UR-00
	for idn@ops.ietf.org; Wed, 01 Aug 2001 03:13:09 -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, 1 Aug 2001 03:24:23 -0700
Message-ID: <001101c11a73$c39ea5c0$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "James Seng/Personal" <James@Seng.cc>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
References: <200107291517.f6TFHvN20321@nic-naa.net> <006a01c118f9$edaf5a60$d43f7018@mtag1.on.home.com> <05f701c1196d$15d11c40$68da15a5@jamessonyvaio>
Subject: Re: [idn] Intro to my I-D 
Date: Wed, 1 Aug 2001 06:21:43 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi James,

After reading ONE-C as you have suggested, I would like to add a 3rd
benefit to my Supreme system (the draft will be released on Aug 14th):

Benefit C-  A mechanism to match the meaning of the user's input (of
CDN) to the intended meaning of the registrant's CDN thus acting
almost like a "Onomastic Normalization Engine" for the Chinese
language as decribed by the document:
http://playground.i-dns.net/one/onec_sum.htm

(By the way, I can't say that the mechanism will cover everything
described by the "Onomastic Normalization Engine", but it will
certainly be a very good attempt at it.)

Thanks
Ben Chan



----- Original Message -----
From: "James Seng/Personal" <James@Seng.cc>
To: "ben" <ben@cc-www.com>; "Eric Brunner-Williams in Portland Maine"
<brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
Sent: Monday, July 30, 2001 11:01 PM
Subject: Re: [idn] Intro to my I-D


Ben,

Wearing my i-DNS.net hat, there is a research work we been doing on
Onomastic Normalization Engine (ONE) for Chinese, Japanese and Korean
for registration purposes.

For your I-D on Chinese, maybe it is worthwhile for you to take a look
at ONE-C. You can find it at
http://playground.i-dns.net/one/onec_sum.htm

-James Seng

----- Original Message -----
From: "ben" <ben@cc-www.com>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
Sent: Monday, July 30, 2001 9:17 PM
Subject: Re: [idn] Intro to my I-D


> Hi Eric,
>
> As you are probably somewhat aware, I am indeed working very hard.
I
> want you to know that I am keeping all your questions /input in the
> back of my mind as I work and that can only help.  So I just want to
> thank you for all your efforts.
>
> The only question I want to address at this moment is something that
> caught my eye.  At the very end of your email below, you concluded
by
> saying- "Just what makes your proposal superior?".  Perhaps this is
a
> good time to reiterate what I said at the very beginning:
>
> My system recognizes the same equal importance for:
>
> 1.  Registrants given the freedom/choice to point Tradition CDN to
> tradition website and Simplifed CDN to simplified website.
> 2.  A need for Tradition CDN to Simplified CDN conversion.
>
> (However, I also believe that other CDN systems are absolutely fine
> exactly the way they are.)
>
> Thanks
> Ben Chan
>
>
>
> ----- Original Message -----
> From: "Eric Brunner-Williams in Portland Maine"
<brunner@nic-naa.net>
> To: "ben" <ben@cc-www.com>
> Cc: "xiang deng" <deng@cnnic.net.cn>; <lee@cnnic.net.cn>;
> <sun@cnnic.net.cn>; <brunner@nic-naa.net>; <brunner@nic-naa.net>;
> <harald@alvestrand.no>; <idn@ops.ietf.org>
> Sent: Sunday, July 29, 2001 11:17 AM
> Subject: Re: [idn] Intro to my I-D
>
>
> [I've added idn@ops.ietf.org back to the cc'd list.
>  Harald, please read and reconsider the "principle of least
surprise".
>  Thx.]
>
> Ben,
>
> What you've proposed is that for some collection of code-points, and
> for
> some equivalency rules (whether zone-scoped or global-scoped),
> allocation
> of one code-point in the collection results in pre-allocation
> (reservation)
> of all code-points in the collection.
>
> Additionally, you've proposed the registrant (recipient of the
> allocated
> code-point equivalency class) may then modify the equivalency rule
> which
> created the class, and assert distinct semantics for distinct
elements
> of
> the original (intact), now fragmented class.
>
> To help me understand your proposal, I'll consider ASCII strings and
> the
> Pan-Algonquin "OU" character (U+0222) and (U+0223). A locally
> constructed
> French character, not present in 17th century French. I know that
most
> of
> the North Americans and Europeans will find this choice strange, but
> more
> accessible, as "Indian French", than an ideogramatic example, and I
> know
> that my friends at CNNIC will speak to the Chinese language
specifics.
>
> Assertion: (zone scope)
>
> In the Algonquin-preferred zone(s), e.g., abenaki.dst.me.us,
> the following code-points and code-point sequences are
> equivalent:
> U+0070 "8" when in an alpha-string
> U+0222 "8" LATIN CAPITAL LETTER OU
> U+0223 "8" LATIN SMALL LETTER OU
> U+0117,U+0125 "OU"
> U+O117,U+0165 "Ou"
> U+0157,U+0165 "ou"
> U+0127 "W"
> U+0167 "w"
>
> Under your proposal, in my zone (abenaki.dst.me.us.), with ASCII
case
> folding
> (applied to the two Latin Extended-B code points), the registrant
for
> "ki8na.abenaki.dst.me.us" ("ki8na" means ourselves or nous-memes),
> would be
> allocated or reserved:
>
> ki{set of 4 code-point sequences}na.abenaki.dst.me.us
>
> The registrant could then be able to associate between 0 and eight
> unique
> ip addresses to these 4 allocated domain names in my zone, e.g.,
>
> ki(U+0070)na.abenaki.dst.me.us and 1.2.3.1
> ki(U+0222)na.abenaki.dst.me.us and 1.2.3.2
> ki(U+0223)na.abenaki.dst.me.us and 1.2.3.2
> ki(U+0117,U+0125)na.abenaki.dst.me.us and 1.2.3.3
> ki(U+O117,U+0165)na.abenaki.dst.me.us and 1.2.3.3
> ki(U+0157,U+0165)na.abenaki.dst.me.us and 1.2.3.3
> ki(U+0127)na.abenaki.dst.me.us and 1.2.3.4
> ki(U+0167)na.abenaki.dst.me.us and 1.2.3.4
>
> Without case folding there could be 8 distinct addresses rather than
> just 4.
>
> This would be very surprising to a modern literate North-Eastern
> Indian, and
> to scholars of the Contact Period and French and Indian literatures
of
> the
> 17th and 18th centuries. As the abenaki.dst.me.us zone manager, I
> don't think
> I would allow it. I would expect the equivalency rule (above) to be
> adopted
> by the {penobscot,passamquoddy,maliseet,micmac}.dst.me.us zone
> managers, and
> by other "Algonquin-aware" NSN.US zone managers. I would not expect
> these to
> be adopted by the dst.me.us or superior zone managers. I would
expect
> the same
> rule and scope to exist in the .ca zone and its dependent zones.
>
> My preference is that ki{set of 4 code-point
> sequences}na.abenaki.dst.me.us
> all map to a single internet address.
>
> In the Chinese language area, which includes North America as well
as
> China,
> your "registrant election" proposal appears to have the same
> surprising set
> of consequences as one registrant following one ideosyncratic
> convention for
> "ki8na" and another registrant, possibly the same one, following a
> different
> ideosyncratic convention for "ni8na" (we and you or nous et vous),
and
> this
> only gets worse as we consider strings such as k8sk8ranmsh8dans8
> (sift).
>
> Just what makes your proposal superior?
>
> Eric
>
> P.S. The advantage of [30], formerly "in" the IDN WG requirements
> draft, was
> that it made zone-specific semantics possible. Writing in modern
> Abenaki (or
> any "8" using French-originating modern script) using ASCII
> equivalency rules
> presents a problem for 0x70 to 0x127,0x167 mapping (simplest case).
>
>





From owner-idn@ops.ietf.org  Wed Aug  1 07:06:47 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA26836
	for <idn-archive@lists.ietf.org>; Wed, 1 Aug 2001 07:06:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Rth8-0009N6-00
	for idn-data@psg.com; Wed, 01 Aug 2001 03:57:42 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Rth6-0009Mz-00
	for idn@ops.ietf.org; Wed, 01 Aug 2001 03:57:41 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 6FF98FFC08; Wed,  1 Aug 2001 18:59:17 +0800 (SGT)
Message-ID: <008701c11a78$bf5793f0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "ben" <ben@cc-www.com>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
References: <200107291517.f6TFHvN20321@nic-naa.net> <006a01c118f9$edaf5a60$d43f7018@mtag1.on.home.com> <05f701c1196d$15d11c40$68da15a5@jamessonyvaio> <001101c11a73$c39ea5c0$d43f7018@mtag1.on.home.com>
Subject: Re: [idn] Intro to my I-D 
Date: Wed, 1 Aug 2001 18:57:24 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sure, I look forward to your I-D.

Our (as in i-DNS.net) approach have been working on Onomastic
Normalization Engine for registration time to handle possible multiple
names since Nov last year. The work on ONE turns out to be much more
complex and time consuming then originally expected. And there is
different ONE for each language (See ONE-J and ONE-K at
http://playground.i-dns.net/one/index.html).

If you have a better approach, I would love to see it.

*cheers*

-James Seng

----- Original Message -----
From: "ben" <ben@cc-www.com>
To: "James Seng/Personal" <James@seng.cc>; "Eric Brunner-Williams in
Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
Sent: Wednesday, August 01, 2001 6:21 PM
Subject: Re: [idn] Intro to my I-D


> Hi James,
>
> After reading ONE-C as you have suggested, I would like to add a 3rd
> benefit to my Supreme system (the draft will be released on Aug 14th):
>
> Benefit C-  A mechanism to match the meaning of the user's input (of
> CDN) to the intended meaning of the registrant's CDN thus acting
> almost like a "Onomastic Normalization Engine" for the Chinese
> language as decribed by the document:
> http://playground.i-dns.net/one/onec_sum.htm
>
> (By the way, I can't say that the mechanism will cover everything
> described by the "Onomastic Normalization Engine", but it will
> certainly be a very good attempt at it.)
>
> Thanks
> Ben Chan
>
>
>
> ----- Original Message -----
> From: "James Seng/Personal" <James@Seng.cc>
> To: "ben" <ben@cc-www.com>; "Eric Brunner-Williams in Portland Maine"
> <brunner@nic-naa.net>
> Cc: <idn@ops.ietf.org>
> Sent: Monday, July 30, 2001 11:01 PM
> Subject: Re: [idn] Intro to my I-D
>
>
> Ben,
>
> Wearing my i-DNS.net hat, there is a research work we been doing on
> Onomastic Normalization Engine (ONE) for Chinese, Japanese and Korean
> for registration purposes.
>
> For your I-D on Chinese, maybe it is worthwhile for you to take a look
> at ONE-C. You can find it at
> http://playground.i-dns.net/one/onec_sum.htm
>
> -James Seng
>
> ----- Original Message -----
> From: "ben" <ben@cc-www.com>
> To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
> Cc: <idn@ops.ietf.org>
> Sent: Monday, July 30, 2001 9:17 PM
> Subject: Re: [idn] Intro to my I-D
>
>
> > Hi Eric,
> >
> > As you are probably somewhat aware, I am indeed working very hard.
> I
> > want you to know that I am keeping all your questions /input in the
> > back of my mind as I work and that can only help.  So I just want to
> > thank you for all your efforts.
> >
> > The only question I want to address at this moment is something that
> > caught my eye.  At the very end of your email below, you concluded
> by
> > saying- "Just what makes your proposal superior?".  Perhaps this is
> a
> > good time to reiterate what I said at the very beginning:
> >
> > My system recognizes the same equal importance for:
> >
> > 1.  Registrants given the freedom/choice to point Tradition CDN to
> > tradition website and Simplifed CDN to simplified website.
> > 2.  A need for Tradition CDN to Simplified CDN conversion.
> >
> > (However, I also believe that other CDN systems are absolutely fine
> > exactly the way they are.)
> >
> > Thanks
> > Ben Chan
> >
> >
> >
> > ----- Original Message -----
> > From: "Eric Brunner-Williams in Portland Maine"
> <brunner@nic-naa.net>
> > To: "ben" <ben@cc-www.com>
> > Cc: "xiang deng" <deng@cnnic.net.cn>; <lee@cnnic.net.cn>;
> > <sun@cnnic.net.cn>; <brunner@nic-naa.net>; <brunner@nic-naa.net>;
> > <harald@alvestrand.no>; <idn@ops.ietf.org>
> > Sent: Sunday, July 29, 2001 11:17 AM
> > Subject: Re: [idn] Intro to my I-D
> >
> >
> > [I've added idn@ops.ietf.org back to the cc'd list.
> >  Harald, please read and reconsider the "principle of least
> surprise".
> >  Thx.]
> >
> > Ben,
> >
> > What you've proposed is that for some collection of code-points, and
> > for
> > some equivalency rules (whether zone-scoped or global-scoped),
> > allocation
> > of one code-point in the collection results in pre-allocation
> > (reservation)
> > of all code-points in the collection.
> >
> > Additionally, you've proposed the registrant (recipient of the
> > allocated
> > code-point equivalency class) may then modify the equivalency rule
> > which
> > created the class, and assert distinct semantics for distinct
> elements
> > of
> > the original (intact), now fragmented class.
> >
> > To help me understand your proposal, I'll consider ASCII strings and
> > the
> > Pan-Algonquin "OU" character (U+0222) and (U+0223). A locally
> > constructed
> > French character, not present in 17th century French. I know that
> most
> > of
> > the North Americans and Europeans will find this choice strange, but
> > more
> > accessible, as "Indian French", than an ideogramatic example, and I
> > know
> > that my friends at CNNIC will speak to the Chinese language
> specifics.
> >
> > Assertion: (zone scope)
> >
> > In the Algonquin-preferred zone(s), e.g., abenaki.dst.me.us,
> > the following code-points and code-point sequences are
> > equivalent:
> > U+0070 "8" when in an alpha-string
> > U+0222 "8" LATIN CAPITAL LETTER OU
> > U+0223 "8" LATIN SMALL LETTER OU
> > U+0117,U+0125 "OU"
> > U+O117,U+0165 "Ou"
> > U+0157,U+0165 "ou"
> > U+0127 "W"
> > U+0167 "w"
> >
> > Under your proposal, in my zone (abenaki.dst.me.us.), with ASCII
> case
> > folding
> > (applied to the two Latin Extended-B code points), the registrant
> for
> > "ki8na.abenaki.dst.me.us" ("ki8na" means ourselves or nous-memes),
> > would be
> > allocated or reserved:
> >
> > ki{set of 4 code-point sequences}na.abenaki.dst.me.us
> >
> > The registrant could then be able to associate between 0 and eight
> > unique
> > ip addresses to these 4 allocated domain names in my zone, e.g.,
> >
> > ki(U+0070)na.abenaki.dst.me.us and 1.2.3.1
> > ki(U+0222)na.abenaki.dst.me.us and 1.2.3.2
> > ki(U+0223)na.abenaki.dst.me.us and 1.2.3.2
> > ki(U+0117,U+0125)na.abenaki.dst.me.us and 1.2.3.3
> > ki(U+O117,U+0165)na.abenaki.dst.me.us and 1.2.3.3
> > ki(U+0157,U+0165)na.abenaki.dst.me.us and 1.2.3.3
> > ki(U+0127)na.abenaki.dst.me.us and 1.2.3.4
> > ki(U+0167)na.abenaki.dst.me.us and 1.2.3.4
> >
> > Without case folding there could be 8 distinct addresses rather than
> > just 4.
> >
> > This would be very surprising to a modern literate North-Eastern
> > Indian, and
> > to scholars of the Contact Period and French and Indian literatures
> of
> > the
> > 17th and 18th centuries. As the abenaki.dst.me.us zone manager, I
> > don't think
> > I would allow it. I would expect the equivalency rule (above) to be
> > adopted
> > by the {penobscot,passamquoddy,maliseet,micmac}.dst.me.us zone
> > managers, and
> > by other "Algonquin-aware" NSN.US zone managers. I would not expect
> > these to
> > be adopted by the dst.me.us or superior zone managers. I would
> expect
> > the same
> > rule and scope to exist in the .ca zone and its dependent zones.
> >
> > My preference is that ki{set of 4 code-point
> > sequences}na.abenaki.dst.me.us
> > all map to a single internet address.
> >
> > In the Chinese language area, which includes North America as well
> as
> > China,
> > your "registrant election" proposal appears to have the same
> > surprising set
> > of consequences as one registrant following one ideosyncratic
> > convention for
> > "ki8na" and another registrant, possibly the same one, following a
> > different
> > ideosyncratic convention for "ni8na" (we and you or nous et vous),
> and
> > this
> > only gets worse as we consider strings such as k8sk8ranmsh8dans8
> > (sift).
> >
> > Just what makes your proposal superior?
> >
> > Eric
> >
> > P.S. The advantage of [30], formerly "in" the IDN WG requirements
> > draft, was
> > that it made zone-specific semantics possible. Writing in modern
> > Abenaki (or
> > any "8" using French-originating modern script) using ASCII
> > equivalency rules
> > presents a problem for 0x70 to 0x127,0x167 mapping (simplest case).
> >
> >
>
>
>




From owner-idn@ops.ietf.org  Wed Aug  1 09:49:07 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA03295
	for <idn-archive@lists.ietf.org>; Wed, 1 Aug 2001 09:49:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Rw0K-000CU1-00
	for idn-data@psg.com; Wed, 01 Aug 2001 06:25:40 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Rw0J-000CTv-00
	for idn@ops.ietf.org; Wed, 01 Aug 2001 06:25:39 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net for <idn@ops.ietf.org>;
          Wed, 1 Aug 2001 06:36:53 -0700
Message-ID: <012701c11a8e$a8411400$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: <idn@ops.ietf.org>
References: <200107291517.f6TFHvN20321@nic-naa.net> <006a01c118f9$edaf5a60$d43f7018@mtag1.on.home.com> <05f701c1196d$15d11c40$68da15a5@jamessonyvaio> <001101c11a73$c39ea5c0$d43f7018@mtag1.on.home.com> <008701c11a78$bf5793f0$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] Intro to my I-D 
Date: Wed, 1 Aug 2001 09:34:13 -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

If after reading my draft, i-dns.net or anybody else thinks that it is
a good idea... please feel free to implement my idea as I will only be
so honoured / honored.

Thanks
Ben Chan


----- Original Message -----
From: "James Seng/Personal" <James@Seng.cc>
To: "ben" <ben@cc-www.com>; "Eric Brunner-Williams in Portland Maine"
<brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
Sent: Wednesday, August 01, 2001 6:57 AM
Subject: Re: [idn] Intro to my I-D


Sure, I look forward to your I-D.

Our (as in i-DNS.net) approach have been working on Onomastic
Normalization Engine for registration time to handle possible multiple
names since Nov last year. The work on ONE turns out to be much more
complex and time consuming then originally expected. And there is
different ONE for each language (See ONE-J and ONE-K at
http://playground.i-dns.net/one/index.html).

If you have a better approach, I would love to see it.

*cheers*

-James Seng

----- Original Message -----
From: "ben" <ben@cc-www.com>
To: "James Seng/Personal" <James@seng.cc>; "Eric Brunner-Williams in
Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
Sent: Wednesday, August 01, 2001 6:21 PM
Subject: Re: [idn] Intro to my I-D


> Hi James,
>
> After reading ONE-C as you have suggested, I would like to add a 3rd
> benefit to my Supreme system (the draft will be released on Aug
14th):
>
> Benefit C-  A mechanism to match the meaning of the user's input (of
> CDN) to the intended meaning of the registrant's CDN thus acting
> almost like a "Onomastic Normalization Engine" for the Chinese
> language as decribed by the document:
> http://playground.i-dns.net/one/onec_sum.htm
>
> (By the way, I can't say that the mechanism will cover everything
> described by the "Onomastic Normalization Engine", but it will
> certainly be a very good attempt at it.)
>
> Thanks
> Ben Chan
>
>
>
> ----- Original Message -----
> From: "James Seng/Personal" <James@Seng.cc>
> To: "ben" <ben@cc-www.com>; "Eric Brunner-Williams in Portland
Maine"
> <brunner@nic-naa.net>
> Cc: <idn@ops.ietf.org>
> Sent: Monday, July 30, 2001 11:01 PM
> Subject: Re: [idn] Intro to my I-D
>
>
> Ben,
>
> Wearing my i-DNS.net hat, there is a research work we been doing on
> Onomastic Normalization Engine (ONE) for Chinese, Japanese and
Korean
> for registration purposes.
>
> For your I-D on Chinese, maybe it is worthwhile for you to take a
look
> at ONE-C. You can find it at
> http://playground.i-dns.net/one/onec_sum.htm
>
> -James Seng
>
> ----- Original Message -----
> From: "ben" <ben@cc-www.com>
> To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
> Cc: <idn@ops.ietf.org>
> Sent: Monday, July 30, 2001 9:17 PM
> Subject: Re: [idn] Intro to my I-D
>
>
> > Hi Eric,
> >
> > As you are probably somewhat aware, I am indeed working very hard.
> I
> > want you to know that I am keeping all your questions /input in
the
> > back of my mind as I work and that can only help.  So I just want
to
> > thank you for all your efforts.
> >
> > The only question I want to address at this moment is something
that
> > caught my eye.  At the very end of your email below, you concluded
> by
> > saying- "Just what makes your proposal superior?".  Perhaps this
is
> a
> > good time to reiterate what I said at the very beginning:
> >
> > My system recognizes the same equal importance for:
> >
> > 1.  Registrants given the freedom/choice to point Tradition CDN to
> > tradition website and Simplifed CDN to simplified website.
> > 2.  A need for Tradition CDN to Simplified CDN conversion.
> >
> > (However, I also believe that other CDN systems are absolutely
fine
> > exactly the way they are.)
> >
> > Thanks
> > Ben Chan
> >
> >
> >
> > ----- Original Message -----
> > From: "Eric Brunner-Williams in Portland Maine"
> <brunner@nic-naa.net>
> > To: "ben" <ben@cc-www.com>
> > Cc: "xiang deng" <deng@cnnic.net.cn>; <lee@cnnic.net.cn>;
> > <sun@cnnic.net.cn>; <brunner@nic-naa.net>; <brunner@nic-naa.net>;
> > <harald@alvestrand.no>; <idn@ops.ietf.org>
> > Sent: Sunday, July 29, 2001 11:17 AM
> > Subject: Re: [idn] Intro to my I-D
> >
> >
> > [I've added idn@ops.ietf.org back to the cc'd list.
> >  Harald, please read and reconsider the "principle of least
> surprise".
> >  Thx.]
> >
> > Ben,
> >
> > What you've proposed is that for some collection of code-points,
and
> > for
> > some equivalency rules (whether zone-scoped or global-scoped),
> > allocation
> > of one code-point in the collection results in pre-allocation
> > (reservation)
> > of all code-points in the collection.
> >
> > Additionally, you've proposed the registrant (recipient of the
> > allocated
> > code-point equivalency class) may then modify the equivalency rule
> > which
> > created the class, and assert distinct semantics for distinct
> elements
> > of
> > the original (intact), now fragmented class.
> >
> > To help me understand your proposal, I'll consider ASCII strings
and
> > the
> > Pan-Algonquin "OU" character (U+0222) and (U+0223). A locally
> > constructed
> > French character, not present in 17th century French. I know that
> most
> > of
> > the North Americans and Europeans will find this choice strange,
but
> > more
> > accessible, as "Indian French", than an ideogramatic example, and
I
> > know
> > that my friends at CNNIC will speak to the Chinese language
> specifics.
> >
> > Assertion: (zone scope)
> >
> > In the Algonquin-preferred zone(s), e.g., abenaki.dst.me.us,
> > the following code-points and code-point sequences are
> > equivalent:
> > U+0070 "8" when in an alpha-string
> > U+0222 "8" LATIN CAPITAL LETTER OU
> > U+0223 "8" LATIN SMALL LETTER OU
> > U+0117,U+0125 "OU"
> > U+O117,U+0165 "Ou"
> > U+0157,U+0165 "ou"
> > U+0127 "W"
> > U+0167 "w"
> >
> > Under your proposal, in my zone (abenaki.dst.me.us.), with ASCII
> case
> > folding
> > (applied to the two Latin Extended-B code points), the registrant
> for
> > "ki8na.abenaki.dst.me.us" ("ki8na" means ourselves or nous-memes),
> > would be
> > allocated or reserved:
> >
> > ki{set of 4 code-point sequences}na.abenaki.dst.me.us
> >
> > The registrant could then be able to associate between 0 and eight
> > unique
> > ip addresses to these 4 allocated domain names in my zone, e.g.,
> >
> > ki(U+0070)na.abenaki.dst.me.us and 1.2.3.1
> > ki(U+0222)na.abenaki.dst.me.us and 1.2.3.2
> > ki(U+0223)na.abenaki.dst.me.us and 1.2.3.2
> > ki(U+0117,U+0125)na.abenaki.dst.me.us and 1.2.3.3
> > ki(U+O117,U+0165)na.abenaki.dst.me.us and 1.2.3.3
> > ki(U+0157,U+0165)na.abenaki.dst.me.us and 1.2.3.3
> > ki(U+0127)na.abenaki.dst.me.us and 1.2.3.4
> > ki(U+0167)na.abenaki.dst.me.us and 1.2.3.4
> >
> > Without case folding there could be 8 distinct addresses rather
than
> > just 4.
> >
> > This would be very surprising to a modern literate North-Eastern
> > Indian, and
> > to scholars of the Contact Period and French and Indian
literatures
> of
> > the
> > 17th and 18th centuries. As the abenaki.dst.me.us zone manager, I
> > don't think
> > I would allow it. I would expect the equivalency rule (above) to
be
> > adopted
> > by the {penobscot,passamquoddy,maliseet,micmac}.dst.me.us zone
> > managers, and
> > by other "Algonquin-aware" NSN.US zone managers. I would not
expect
> > these to
> > be adopted by the dst.me.us or superior zone managers. I would
> expect
> > the same
> > rule and scope to exist in the .ca zone and its dependent zones.
> >
> > My preference is that ki{set of 4 code-point
> > sequences}na.abenaki.dst.me.us
> > all map to a single internet address.
> >
> > In the Chinese language area, which includes North America as well
> as
> > China,
> > your "registrant election" proposal appears to have the same
> > surprising set
> > of consequences as one registrant following one ideosyncratic
> > convention for
> > "ki8na" and another registrant, possibly the same one, following a
> > different
> > ideosyncratic convention for "ni8na" (we and you or nous et vous),
> and
> > this
> > only gets worse as we consider strings such as k8sk8ranmsh8dans8
> > (sift).
> >
> > Just what makes your proposal superior?
> >
> > Eric
> >
> > P.S. The advantage of [30], formerly "in" the IDN WG requirements
> > draft, was
> > that it made zone-specific semantics possible. Writing in modern
> > Abenaki (or
> > any "8" using French-originating modern script) using ASCII
> > equivalency rules
> > presents a problem for 0x70 to 0x127,0x167 mapping (simplest
case).
> >
> >
>
>
>






From owner-idn@ops.ietf.org  Wed Aug  1 10:59:18 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA07415
	for <idn-archive@lists.ietf.org>; Wed, 1 Aug 2001 10:59:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Rx3y-000EL9-00
	for idn-data@psg.com; Wed, 01 Aug 2001 07:33:30 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Rx3x-000EL2-00
	for idn@ops.ietf.org; Wed, 01 Aug 2001 07:33:29 -0700
Received: from zetnet.co.uk (man-s078.dialup.zetnet.co.uk [194.247.41.205])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f71EWxx02454;
	Wed, 1 Aug 2001 15:33:00 +0100
Message-ID: <3B67FE19.29536D40@zetnet.co.uk>
Date: Wed, 01 Aug 2001 14:03:21 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: [idn] Which names are valid? (was How should labels be encoded?)
References: <20010731214555.E20351@arwen.cs.berkeley.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

[I'll discuss the relevance of email address internationalization
to this working group in another reply.]

"Adam M. Costello" wrote:
> David Hopwood wrote:
> > This does make clear, however, that it is not correct for a general
> > purpose resolver interface to reject non-LDH ASCII characters;
> > instead, it should pass through such characters (if no non-LDH
> > characters are used in that domain, the query will simply fail).
> 
> You seem to be confusing queries and responses, or domain names and
> resource records.  Currently, all domain names (which are the things
> that appear in queries) are advised to use the preferred name syntax
> (LDH characters in labels).  The resource records (the things that
> appear in responses, like SOA and SRV data) already contain non-LDH
> characters, and of course they are not rejected for that.

I think you're missing the point, possibly from not having read RFC 2782.
In a query for SRV records, a non-LDH character ('_') is used in the
query string (QNAME), not just the response. The same may apply to a
query with QTYPE=MAILB (RFC 1035 section 8), and possibly others
(although I don't think MAILB is commonly used?)

More generally, nothing in RFCs 1034, 1035 or 2181 prohibited use of
non-LDH names in queries or in registered names; that was simply a
strong recommendation. So, prohibiting them now (as the current IDNA
draft does [*], for example) would be a backward-incompatible change.


[*] From section 3 of draft-ietf-idn-idna-03.txt:

    # If names that are not legal in [NAMEPREP] are passed to an
    # application, it will result in an error being passed to the
    # application with no error being reported to the name server.
    # Further, no application will ever ask for a name that is not
    # legal in [NAMEPREP] because requests always go through [NAMEPREP]
    # before getting to the DNS.

    Since the names used in SRV queries would result in an error from
    nameprep, it's clear that either the protocol labels in a SRV query
    (and other similar cases) must not go through nameprep, or nameprep
    must be changed so that it does not prohibit non-LDH ASCII
    characters, or both.

> Some resource
> records contain domain names (like CNAME and PTR) but some contain
> other things.  The mailbox field of the SOA record, even though it is
> formatted as a sequence of labels, is not a domain name and is not
> expected to conform to the preferred name syntax (although after you
> chop off the first label, the result is a domain name and is expected to
> conform).  I gather than the same is true of the SRV record.

What do you propose to call the query string used for a SRV lookup
(e.g. "_ldap._tcp.example.com"), if not a domain name? It is certainly
a domain name as defined and used in RFCs 1034, 1035 and 2181 (although
not a host name).

However, as I said, this does not cause any problem provided that
resolver interfaces don't reject non-LDH US-ASCII octets in queries.

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

iQEVAwUBO2f9qjkCAxeYt5gVAQHFcQf/Uz3mSIDKKZWZAx60CW3SYac7KN+y6xk3
O+Mw3W5wXo6oHKBxnqP+ySQS25BFTuooXQo/RKB7ORyG2HP/+zuCYhXrbaqjoYpL
/gZw6zV8iRwlH8z8Grh3TRaNgxQiTZAaBpRy3BMqMuXP5Q3FeAjDR1lzQoNd9Wrk
jB4yrxk4oZGunKBYZzomfbUOq/vD+KzoFEeaSNLcjhxn5oHjUaeZJ7pzXUSxbtrl
6v6902h2fsWom+k/6xWlbcZZLN0zsLKJUpig3JWT/wRls2BiNRvgHhBeZb86swdM
ijE+oGSZytVmSRV76RoomzauoqzNKKGa80hrFtDJEB73B4B43tT6Ag==
=PjT8
-----END PGP SIGNATURE-----





From owner-idn@ops.ietf.org  Wed Aug  1 11:40:46 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA17189
	for <idn-archive@lists.ietf.org>; Wed, 1 Aug 2001 11:40:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Rxmw-000FU5-00
	for idn-data@psg.com; Wed, 01 Aug 2001 08:19:58 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Rxmv-000FTz-00
	for idn@ops.ietf.org; Wed, 01 Aug 2001 08:19:57 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f71FIJN32766;
	Wed, 1 Aug 2001 11:18:19 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200108011518.f71FIJN32766@nic-naa.net>
To: idn@ops.ietf.org
cc: J.Crowcroft@cs.ucl.ac.uk
Subject: [idn] UTF8 Dinner (curry) at London (Tuesday)
Date: Wed, 01 Aug 2001 11:18:19 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I propose we (UTF8 afficianados) go out for curry Tuesday evening.

I will put up a sign-up sheet on the rendevous boards at the usual
place (the secretariate-proximal-milling-about-area).

I've cc'd Jon Crowcroft in the hope that pointers to simply fabulous
Indian restaurants will materialize.

Curry, the real reason to hold IETFs in London.

Eric



From owner-idn@ops.ietf.org  Wed Aug  1 18:27:52 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA07667
	for <idn-archive@lists.ietf.org>; Wed, 1 Aug 2001 18:27:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15S44c-000OhB-00
	for idn-data@psg.com; Wed, 01 Aug 2001 15:02:38 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15S44b-000Oh5-00
	for idn@ops.ietf.org; Wed, 01 Aug 2001 15:02:37 -0700
Received: from amc by nicemice.net with local (Exim 3.31 #1 (Debian))
	id 15S44a-0006Hg-00; Wed, 01 Aug 2001 15:02:36 -0700
Date: Wed, 1 Aug 2001 22:02:36 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Which names are valid? (was How should labels be encoded?)
Message-ID: <20010801220236.F23628@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B67FE19.29536D40@zetnet.co.uk>
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

David Hopwood <david.hopwood@zetnet.co.uk> wrote:

> In a query for SRV records, a non-LDH character ('_') is used in the
> query string (QNAME), not just the response.

I stand corrected.  I was not aware that non-LDH characters were welcome
in DNS queries.

This raises the question:  Is _ldap._tcp.example.com a domain?  Or is it
a creature like the mailbox field of SOA records, a sequence of labels
that does not name a domain?

Could the name server for example.com contain SOA and NS records for
_tcp.example.com, and the name server for the latter contain the SRV
record for _ldap._tcp.example.com?  If we want the answer to be yes,
then _ldap._tcp.example.com must really be a domain.  If the answer is
no, we could say it's not a domain, just a sequence of labels, of which
all but the first two form a domain name, and IDNA would apply only to
those labels.

Perhaps nameprep is not the right layer for the non-LDH ASCII
prohibition.  Maybe that belongs at a higher layer, the same layer that
checks for beginning/ending hyphens.  In other words, put all the checks
related to preferred name syntax in one place, where they can be skipped
if they don't apply.

By the way, I already had plans to make a slight change to AMC-ACE-Z
so that all ASCII characters are encoded literally, not just LDH
characters, because it makes the encoder slightly simpler, and has no
effect for names that avoid non-LDH ASCII characters.

AMC



From owner-idn@ops.ietf.org  Wed Aug  1 19:20:02 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA09706
	for <idn-archive@lists.ietf.org>; Wed, 1 Aug 2001 19:20:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15S5BX-0000pN-00
	for idn-data@psg.com; Wed, 01 Aug 2001 16:13:51 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15S5BW-0000pH-00
	for idn@ops.ietf.org; Wed, 01 Aug 2001 16:13:50 -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 191988 for idn@ops.ietf.org; Tue, 31 Jul 2001 18:13:08 -0500
Message-ID: <3B688D29.D8CFDBB6@ehsco.com>
Date: Wed, 01 Aug 2001 18:13:45 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: idn@ops.ietf.org
Subject: Re: [idn] Which names are valid? (was How should labels be encoded?)
References: <20010801220236.F23628@arwen.cs.berkeley.edu> <3B688BF8.F31A2907@ehsco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> Hostnames have naming prohibitions due to the legacy of RFCs 972/1123

should be 952/1123

one of my common typos

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



From owner-idn@ops.ietf.org  Wed Aug  1 19:25:11 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA09975
	for <idn-archive@lists.ietf.org>; Wed, 1 Aug 2001 19:25:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15S56c-0000eR-00
	for idn-data@psg.com; Wed, 01 Aug 2001 16:08:46 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15S56b-0000eL-00
	for idn@ops.ietf.org; Wed, 01 Aug 2001 16:08:45 -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 191985; Tue, 31 Jul 2001 18:08:03 -0500
Message-ID: <3B688BF8.F31A2907@ehsco.com>
Date: Wed, 01 Aug 2001 18:08:40 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Adam M. Costello" <amc@cs.berkeley.edu>
CC: idn@ops.ietf.org
Subject: Re: [idn] Which names are valid? (was How should labels be encoded?)
References: <20010801220236.F23628@arwen.cs.berkeley.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> This raises the question:  Is _ldap._tcp.example.com a domain?

It is a domain name associated with one or more resource records.

> Or is it a creature like the mailbox field of SOA records, a sequence
> of labels that does not name a domain?

Email addresses are stored as data in a resource record. They use the
domain name syntax so they can be compressed in the DNS message, but do
not otherwise fall under the purview of any domain name rules (an email
address can exist as DNS data, be a completely invalid domain name, and
still exist -- just not as a piece of data that is probably useful).

> Perhaps nameprep is not the right layer for the non-LDH ASCII
> prohibition.  Maybe that belongs at a higher layer, the same layer
> that checks for beginning/ending hyphens.

That is the application layer.

Hostnames have naming prohibitions due to the legacy of RFCs 972/1123 (the
old HOSTS.TXT database naming spec). Domain names in particular do not
have these prohibitions, but instead, applications apply (or ignore) the
hostname prohibitions when they have to use the hostname for a lookup
operation. EG, since the hostname could exist in /etc/hosts or in DNS, the
"hostname rules" apply regardless of where the data is stored or the
mechanism used to retrieve it.

Applications will continue to have these rules until they choose to extend
their specific ruleset.

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



From owner-idn@ops.ietf.org  Wed Aug  1 19:57:39 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA11590
	for <idn-archive@lists.ietf.org>; Wed, 1 Aug 2001 19:57:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15S5Ze-0001bz-00
	for idn-data@psg.com; Wed, 01 Aug 2001 16:38:46 -0700
Received: from drugs.dv.isc.org ([130.155.191.236])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15S5Zc-0001bs-00
	for idn@ops.ietf.org; Wed, 01 Aug 2001 16:38:44 -0700
Received: from nominum.com (localhost.dv.isc.org [127.0.0.1])
	by drugs.dv.isc.org (8.11.3/8.11.2) with ESMTP id f71NcHu30042;
	Thu, 2 Aug 2001 09:38:22 +1000 (EST)
	(envelope-from marka@nominum.com)
Message-Id: <200108012338.f71NcHu30042@drugs.dv.isc.org>
To: "Adam M. Costello" <amc@cs.berkeley.edu>
Cc: idn@ops.ietf.org
From: Mark.Andrews@nominum.com
Subject: Re: [idn] Which names are valid? (was How should labels be encoded?) 
In-reply-to: Your message of "Wed, 01 Aug 2001 22:02:36 GMT."
             <20010801220236.F23628@arwen.cs.berkeley.edu> 
Date: Thu, 02 Aug 2001 09:38:17 +1000
Sender: owner-idn@ops.ietf.org
Precedence: bulk


> David Hopwood <david.hopwood@zetnet.co.uk> wrote:
> 
> > In a query for SRV records, a non-LDH character ('_') is used in the
> > query string (QNAME), not just the response.
> 
> I stand corrected.  I was not aware that non-LDH characters were welcome
> in DNS queries.

	The DNS doesn't care about the contents of labels.  It's the
	applications that use the DNS that care.

> 
> This raises the question:  Is _ldap._tcp.example.com a domain?

	Yes.  It's not a hostname however.  Underscore was prepended
	to these labels to avoid collisions with hostnames.  This
	allows you to delegate a tcp domain with having problems
	with using SRV records for the parent domain.

	A real life example that used to exist.  CSIRO had a division
	called Tropical Crops and Pastures.  Its domainname was
	tcp.csiro.au.  Without the underscores you would have had
	to put the SRV records for csiro.au in the tcp.csiro.au
	zone.  This was bad.  Paul had trouble convicing Jon of
	this which is why the first SRV RFC didn't have the
	underscores and the second one does.

> Or is it
> a creature like the mailbox field of SOA records, a sequence of labels
> that does not name a domain?

	The RNAME field is a domainname, however it is not a hostname
	(maildomain) though it contains a hostname (maildomain).

> 
> Could the name server for example.com contain SOA and NS records for
> _tcp.example.com, and the name server for the latter contain the SRV
> record for _ldap._tcp.example.com?

	Yes.  People do this all the time to intergate W2K into
	BIND where they don't want example.com to be modified but
	they still want to support the dynamic updates of the DNS
	by W2K AD.

>  If we want the answer to be yes,
> then _ldap._tcp.example.com must really be a domain.

	It is.

> If the answer is
> no, we could say it's not a domain, just a sequence of labels, of which
> all but the first two form a domain name, and IDNA would apply only to
> those labels.

	I tried very, very hard to get the concept of hostname,
	maildomain and domainname across very early in this process.
	You are only now realising that domainname is a supperset
	of hostname and maildomain.

> 
> Perhaps nameprep is not the right layer for the non-LDH ASCII
> prohibition.  Maybe that belongs at a higher layer, the same layer that
> checks for beginning/ending hyphens.  In other words, put all the checks
> related to preferred name syntax in one place, where they can be skipped
> if they don't apply.

	That's where these checks are today.  They are in the
	get*by*() routines not in the res_*() though there are
	res_*() subroutines that will tell you if the name is valid
	in a particular context.

	I also don't consider get*by*() to be resolver routines
	even though they are sometimes in libresolv.  get*by*()
	sit above several databases of which the DNS is one.

	Mark
> 
> By the way, I already had plans to make a slight change to AMC-ACE-Z
> so that all ASCII characters are encoded literally, not just LDH
> characters, because it makes the encoder slightly simpler, and has no
> effect for names that avoid non-LDH ASCII characters.
> 
> AMC
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@nominum.com



From owner-idn@ops.ietf.org  Thu Aug  2 12:13:32 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA04301
	for <idn-archive@lists.ietf.org>; Thu, 2 Aug 2001 12:13:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15SJfF-000Bi3-00
	for idn-data@psg.com; Thu, 02 Aug 2001 07:41:29 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15SJfE-000BZl-00
	for idn@ops.ietf.org; Thu, 02 Aug 2001 07:41:28 -0700
Received: from bbthead.brandenburg.com ([63.250.132.1])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id HAA03279;
	Thu, 2 Aug 2001 07:38:10 -0700
Message-Id: <5.1.0.14.2.20010802102733.03ef7140@brandenburg.com>
X-Sender: dcrocker@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 02 Aug 2001 10:36:03 -0400
To: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: Re: [idn] We are quibbling about WHAT? 
Cc: idn@ops.ietf.org, brunner@nic-naa.net
In-Reply-To: <200107300013.f6U0DON21674@nic-naa.net>
References: <Your message of "Sun, 29 Jul 2001 17:31:05 CDT." <5.1.0.14.2.20010729172557.0302f008@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:13 PM 7/29/2001, Eric Brunner-Williams in Portland Maine wrote:
>I think the encapsulate vs extend debate is about architecture. It
>just happens that 63 bytes does focus some attention on effective
>characters per mechanism, and encapsulation schemes using only 5 bits
>plus a nickle per octet are at a disadvantage over extension schemes
>that use at least 7 bits per octet.

1.  My impression is that, in fact, expressions of concern have more often 
had, really, to do with encoding efficiency than anything else.  Or, at 
least, the arguments with the most substance.  And to continue the 
analytical quibble, my impression is that the character sets that are more 
restricted with UTF-8 *AND* with ACE have more information density that 
such un-dense stuff as ASCII.

2.  The name of "architecture" is a very double-edged sword.  Architecture 
that worries only about computer science purity, for example, often winds 
up being highly impractical.  It does not attend to a sufficient range of 
real-world requirements/constraints.

That was why I went through the transition discussion, separately.  The 
difference in transition ease, risk, etc., between ACE and UTF-8 is exactly 
the reason that the horrible technology, called MIME, was used for 
introducing binary, segmented, labeled data to email content.

>The transition impact discussion can't be refuted. It was the subject
>of RFC 801, and others. I'm particularly fond of lines 51 - 64 of
>that transition plan by the way.
>Time to choose an ACE and move on? I'll pass thanks. A half-dozen
>browser-hack marketeers, a trio of monopolies, and the DNSO food
>fight, is inadequate motivation to solve a complex problem. A good
>solution is, and differences in that are why we are where we are.

Having not yet seen any response to the analysis I offered, I beginning 
whether folks really are not interested in attending to transition pragmatics.

Where is the detailed response, rather than just rejection or 
acceptance?  Please skip the personalization of this.

Just as the tendency in the IETF is to say that the primary -- and maybe 
the only -- design concern is scaling, I've come to believe that the only 
concern when upgrading an installed base is the transition ease.

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 Aug  2 13:24:59 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA08240
	for <idn-archive@lists.ietf.org>; Thu, 2 Aug 2001 13:24:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15SLjP-000GgO-00
	for idn-data@psg.com; Thu, 02 Aug 2001 09:53:55 -0700
Received: from [213.86.25.246] (helo=mirth.lon.lab)
	by psg.com with smtp (Exim 3.31 #1)
	id 15SLjN-000GZx-00
	for idn@ops.ietf.org; Thu, 02 Aug 2001 09:53:54 -0700
Received: (qmail 2191 invoked from network); 2 Aug 2001 17:49:07 -0000
Received: from localhost (127.0.0.1)
  by localhost with SMTP; 2 Aug 2001 17:49:07 -0000
Date: Thu, 2 Aug 2001 17:49:07 +0000 (GMT)
From: Mike Astle <astle@new.net>
X-X-Sender:  <astle@mirth.lon.lab>
Reply-To: <astle@new.net>
To: Martin Duerst <duerst@w3.org>
cc: <idn@ops.ietf.org>
Subject: [idn] Re: [idn-nameprep] nameprep back-compatibility
In-Reply-To: <Pine.LNX.4.33.0107301313590.14437-100000@mirth.lon.lab>
Message-ID: <Pine.LNX.4.33.0108021741450.3665-100000@mirth.lon.lab>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

The silence from the idn-nameprep list is leading me to believe that I
might be asking a stupid question here, but I'll give it a go nonetheless.

Please see below...

On Mon, 30 Jul 2001, Mike Astle wrote:

> Heya Martin,
>
> First off, let me say thanks for taking the time to answer my questions.
>
> I agree that the handling of newly assigned codepoints is very sensible
> and will ease the adoption process.  I'm interested in what happens to
> "reassigned" codepoints.  To use the language of Section 6 of the draft,
> what if a character in MN changes mappings between two versions of
> nameprep?  That is:
>
> nameprep_version1( X ) = A
> nameprep_version2( X ) = B
>
> where X is in MN and A and B are in AO.  X remains in MN.
>
> If I'm a client with a resolver that uses nameprep_version1, I expect X to
> always map to A.  When I upgrade my resolver to nameprep_version2, X
> now maps to B - possibly leading me to a different IP address than what I
> intended.
>
> Is this kind of remapping forbidden by the draft or an associated
> document?
>
> -mike
>
> On Mon, 30 Jul 2001, Martin Duerst wrote:
>
> > Hello Mike,
> >
> > Here's a short summary.
> > The main thing that can happen is that new characters get
> > defined in Unicode/iso10646. For these codepoints, the
> > current version of nameprep requires that registrars/registries/
> > dns administrators reject such domain names, otherwise it would
> > be possible to have domain names with undefined characters.
> >
> > After new characters have been defined, nameprep will be updated.
> > Some of the new characters (those that make sense in domain names)
> > will be newly excluded, others will be prohibited. New implementations
> > of nameprep can then use the new rules, and registrars/registries/
> > dns administrators can start to add names with such new characters.
> >
> > For clients on the resolving side, nameprep says that they should
> > not reject names with unassigned characters. So for the new characters,
> > client software will not have to be updated.
> >
> > That's basically how it works, and how it is described in the
> > Internet-Draft. Please read it again. If you have any suggestions
> > on how to improve the wording, please send them in (of course,
> > suggestions on different ways of handling the problem of newly
> > assigned characters are also of interest, but I think we are
> > pretty sure we got the most reasonable solution for what is
> > inherently not an easy problem).
> >
> > Regards,   Martin.
> >
> > At 00:57 01/07/30 +0000, Mike Astle wrote:
> > >I'm new to this process, so please let me know if this message is
> > >misdirected.  After reading over what I believe to be the newest version
> > >fo the nameprep draft:
> > >
> > >http://www.ietf.org/internet-drafts/draft-ietf-idn-nameprep-05.txt
> > >
> > >I was left wondering what happens if the mapping of a code point changes
> > >between versions of nameprep.  That is, the case where:
> > >
> > >nameprep_v1(S) != nameprep_v2(S)
> > >
> > >and S contains no unassigned codepoints (as of v1).
> > >
> > >I read back over the document and found this paragraph in section 6.2:
> > >
> > >"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."
> > >
> > >Does this paragraph mean that nameprep(S) will always be the same no
> > >matter what the version of nameprep (provided that S does not contain any
> > >previously unassigned codepoints)?
> > >
> > >-mike
> > >
> >
> >
>
>




From owner-idn@ops.ietf.org  Thu Aug  2 17:21:57 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA20516
	for <idn-archive@lists.ietf.org>; Thu, 2 Aug 2001 17:21:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15SPII-000LR4-00
	for idn-data@psg.com; Thu, 02 Aug 2001 13:42:10 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15SPIH-000LQy-00
	for idn@ops.ietf.org; Thu, 02 Aug 2001 13:42:09 -0700
Received: from [10.0.1.3] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id WAA15733;
	Thu, 2 Aug 2001 22:34:38 +0200 (MET DST)
Date: Thu, 02 Aug 2001 22:30:34 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: astle@new.net, Martin Duerst <duerst@w3.org>
cc: idn@ops.ietf.org
Subject: Re: [idn] Re: [idn-nameprep] nameprep back-compatibility
Message-ID: <748041.996791434@localhost>
In-Reply-To: <Pine.LNX.4.33.0108021741450.3665-100000@mirth.lon.lab>
References:  <Pine.LNX.4.33.0108021741450.3665-100000@mirth.lon.lab>
X-Mailer: Mulberry/2.1.0b3 (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 08/02/2001 5:49 PM +0000 Mike Astle <astle@new.net> wrote:

> The silence from the idn-nameprep list is leading me to believe that I
> might be asking a stupid question here, but I'll give it a go nonetheless.
> 
> Please see below...

As myself and Mark came up with section 6, I will respond to this.

> On Mon, 30 Jul 2001, Mike Astle wrote:
> 
>> I agree that the handling of newly assigned codepoints is very sensible
>> and will ease the adoption process.  I'm interested in what happens to
>> "reassigned" codepoints.  To use the language of Section 6 of the draft,
>> what if a character in MN changes mappings between two versions of
>> nameprep?

According to Unicode Consortium, this will not happen. Yes, it happened a
few months ago, but that was a change that was agreed could be made at that
point in time as the tables are not referenced by any standard (yet). The
same decision would be different if IDN/Nameprep was a done deal.

I got this as a response when I as liason from IETF asked this very
question.

>>  That is:
>> 
>> nameprep_version1( X ) = A
>> nameprep_version2( X ) = B
>> 
>> where X is in MN and A and B are in AO.  X remains in MN.
>> 
>> If I'm a client with a resolver that uses nameprep_version1, I expect X
>> to always map to A.  When I upgrade my resolver to nameprep_version2, X
>> now maps to B - possibly leading me to a different IP address than what I
>> intended.
>> 
>> Is this kind of remapping forbidden by the draft or an associated
>> document?

See above, forbidden in the Unicode Consortium.

   paf




From owner-idn@ops.ietf.org  Thu Aug  2 19:56:22 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA02195
	for <idn-archive@lists.ietf.org>; Thu, 2 Aug 2001 19:56:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15SSAg-0000E1-00
	for idn-data@psg.com; Thu, 02 Aug 2001 16:46:30 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15SSAf-0000DY-00
	for idn@ops.ietf.org; Thu, 02 Aug 2001 16:46:29 -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 f72NkGs25955;
	Fri, 3 Aug 2001 00:46:17 +0100
Message-ID: <3B69D303.3682EA47@zetnet.co.uk>
Date: Thu, 02 Aug 2001 23:24:03 +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: astle@new.net, idn@ops.ietf.org
Subject: Re: [idn] nameprep back-compatibility
References: <Pine.LNX.4.33.0108021741450.3665-100000@mirth.lon.lab>
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-----

Mike Astle wrote:
> If I'm a client with a resolver that uses nameprep_version1, I expect X to
> always map to A.  When I upgrade my resolver to nameprep_version2, X
> now maps to B - possibly leading me to a different IP address than what I
> intended.
>
> Is this kind of remapping forbidden by the draft or an associated
> document?

Yes, it is forbidden, provided that X does not contain any characters that
were unassigned in the version of Unicode used by nameprep_version1.

At 00:57 01/07/30 +0000, Mike Astle wrote:
> I'm new to this process, so please let me know if this message is
> misdirected.  After reading over what I believe to be the newest version
> of the nameprep draft:
>
> http://www.ietf.org/internet-drafts/draft-ietf-idn-nameprep-05.txt
>
> I was left wondering what happens if the mapping of a code point changes
> between versions of nameprep.  That is, the case where:
>
> nameprep_v1(S) != nameprep_v2(S)
>
> and S contains no unassigned codepoints (as of v1).
>
> I read back over the document and found this paragraph in section 6.2:
>
> "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."

This is obviously not correct; it should be something like:

  "The processing in this document is always stable. If a string X
  contains no characters that are unassigned in the version of Unicode
  used by oldVersion, then the result of processing X on oldVersion and
  on newVersion will be the same."

> Does this paragraph mean that nameprep(S) will always be the same no
> matter what the version of nameprep (provided that S does not contain
> any previously unassigned codepoints)?

Yes, that's what the corrected version means.

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

iQEVAwUBO2nS6zkCAxeYt5gVAQHxQAgAi5vQlW48LwBT3VDWho0B6D0qB5Ce6GDO
Pqsb/6lYxMScdM3bzIX+ZKySYajHENM587SyLhilGMvUwlFnA8SvsWFihBt+fgHD
QaYm8cvBhMwlGjZDOuou1KMSfR1sVRiYJ1cu9vfOaqDyBTbvKhu+ECsEMM0nFSkD
E9fvmp+FY7iiX6NprdKP/b1q9OAcRupebVA+5YW1q3Dw9wu7yscpkjKAlqsE2TJN
IN2/vCAPa9rieyVKaB8RtNkYJhWW5tqtdBbEyWbbuW1y1umL/YUvBsJRuFpecBdF
H/xWL7Zibf/Rw8j4GA9JK1Em5JrPBjAzGBW/UnGSFkXD9lWQ/3f8LA==
=SAWP
-----END PGP SIGNATURE-----




From owner-idn@ops.ietf.org  Thu Aug  2 22:57:02 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA14290
	for <idn-archive@lists.ietf.org>; Thu, 2 Aug 2001 22:57:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15SUPV-0004DJ-00
	for idn-data@psg.com; Thu, 02 Aug 2001 19:09:57 -0700
Received: from postoffice.sarnoff.com ([130.33.10.147])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15SUPU-00049u-01
	for idn@ops.ietf.org; Thu, 02 Aug 2001 19:09:57 -0700
Received: from postoffice.sarnoff.com ([127.0.0.1]) by
          postoffice.sarnoff.com (Netscape Messaging Server 4.15) with
          SMTP id GHGZ4K00.PCN for <idn@ops.ietf.org>; Thu, 2 Aug 2001
          22:05:08 -0400 
Received: from nova.sarnoff.com ([130.33.8.27]) by
          postoffice.sarnoff.com (Netscape Messaging Server 4.15) with
          ESMTP id GH5TH800.BG8; Fri, 27 Jul 2001 21:29:32 -0400 
Received: from loki.ietf.org (loki.ietf.org [132.151.1.177])
	by nova.sarnoff.com (8.9.2/8.9.2) with ESMTP id MAA17545;
	Tue, 24 Jul 2001 12:01:30 -0400 (EDT)
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id LAA17436
	for ietf-123-outbound.05@ietf.org; Tue, 24 Jul 2001 11:35:00 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id GAA12793
	for <all-ietf@loki.ietf.org>; Tue, 24 Jul 2001 06:31:29 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06327;
	Tue, 24 Jul 2001 06:31:28 -0400 (EDT)
Message-Id: <200107241031.GAA06327@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: idn@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [idn] I-D ACTION:draft-ietf-idn-nameprep-05.txt
Date: Tue, 24 Jul 2001 06:31:27 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: Preparation of Internationalized Host Names
	Author(s)	: P. Hoffman, M. Blanchet
	Filename	: draft-ietf-idn-nameprep-05.txt
	Pages		: 
	Date		: 23-Jul-01
	
This document describes how to prepare internationalized host names for
use in the DNS. The steps include:
- mapping characters to other characters, such as to change their case
- normalizing the characters
- excluding characters that are prohibited from appearing in
internationalized host names
This document does not specify a wire protocol. This preparation should
be done before the DNS request.

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

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-idn-nameprep-05.txt

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

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

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Thu Aug  2 23:14:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA14983
	for <idn-archive@lists.ietf.org>; Thu, 2 Aug 2001 23:14:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15SUPQ-0004CP-00
	for idn-data@psg.com; Thu, 02 Aug 2001 19:09:52 -0700
Received: from postoffice.sarnoff.com ([130.33.10.147])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15SUPP-00049u-00
	for idn@ops.ietf.org; Thu, 02 Aug 2001 19:09:51 -0700
Received: from postoffice.sarnoff.com ([127.0.0.1]) by
          postoffice.sarnoff.com (Netscape Messaging Server 4.15) with
          SMTP id GHGYUA00.QC6 for <idn@ops.ietf.org>; Thu, 2 Aug 2001
          21:58:58 -0400 
Received: from nova.sarnoff.com ([130.33.8.27]) by
          postoffice.sarnoff.com (Netscape Messaging Server 4.15) with
          ESMTP id GH5OXW00.AB1; Fri, 27 Jul 2001 19:51:32 -0400 
Received: from loki.ietf.org (loki.ietf.org [132.151.1.177])
	by nova.sarnoff.com (8.9.2/8.9.2) with ESMTP id MAA06706;
	Wed, 25 Jul 2001 12:43:39 -0400 (EDT)
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id MAA00547
	for ietf-123-outbound.05@ietf.org; Wed, 25 Jul 2001 12:25:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id GAA25641
	for <all-ietf@loki.ietf.org>; Wed, 25 Jul 2001 06:35:23 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07829;
	Wed, 25 Jul 2001 06:35:19 -0400 (EDT)
Message-Id: <200107251035.GAA07829@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: idn@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [idn] I-D ACTION:draft-ietf-idn-idna-03.txt
Date: Wed, 25 Jul 2001 06:35:18 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: Internationalizing Host Names In Applications (IDNA)
	Author(s)	: P. Hoffman, P. Faltstrom
	Filename	: draft-ietf-idn-idna-03.txt
	Pages		: 
	Date		: 24-Jul-01
	
The current DNS infrastructure does not provide a way to use
internationalized host names (IDN). This document describes a mechanism
that requires no changes to any DNS server or resolver that will allow
internationalized host names to be used by end users with changes only
to applications. It allows flexibility for user input and display, and
assures that host names that have non-ASCII characters are not sent to
DNS servers or resolvers.

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

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-idn-idna-03.txt

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

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

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Fri Aug  3 05:24:58 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA10732
	for <idn-archive@lists.ietf.org>; Fri, 3 Aug 2001 05:24:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Saj9-000JTV-00
	for idn-data@psg.com; Fri, 03 Aug 2001 01:54:39 -0700
Received: from postoffice.sarnoff.com ([130.33.10.147])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Saj8-000JRW-00
	for idn@ops.ietf.org; Fri, 03 Aug 2001 01:54:38 -0700
Received: from postoffice.sarnoff.com ([127.0.0.1]) by
          postoffice.sarnoff.com (Netscape Messaging Server 4.15) with
          SMTP id GHHF9L00.KQG for <idn@ops.ietf.org>; Fri, 3 Aug 2001
          03:53:45 -0400 
Received: from nova.sarnoff.com ([130.33.8.27]) by
          postoffice.sarnoff.com (Netscape Messaging Server 4.15) with
          ESMTP id GH5OXW00.AB1; Fri, 27 Jul 2001 19:51:32 -0400 
Received: from loki.ietf.org (loki.ietf.org [132.151.1.177])
	by nova.sarnoff.com (8.9.2/8.9.2) with ESMTP id MAA06706;
	Wed, 25 Jul 2001 12:43:39 -0400 (EDT)
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id MAA00547
	for ietf-123-outbound.05@ietf.org; Wed, 25 Jul 2001 12:25:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id GAA25641
	for <all-ietf@loki.ietf.org>; Wed, 25 Jul 2001 06:35:23 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07829;
	Wed, 25 Jul 2001 06:35:19 -0400 (EDT)
Message-Id: <200107251035.GAA07829@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: idn@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [idn] I-D ACTION:draft-ietf-idn-idna-03.txt
Date: Wed, 25 Jul 2001 06:35:18 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: Internationalizing Host Names In Applications (IDNA)
	Author(s)	: P. Hoffman, P. Faltstrom
	Filename	: draft-ietf-idn-idna-03.txt
	Pages		: 
	Date		: 24-Jul-01
	
The current DNS infrastructure does not provide a way to use
internationalized host names (IDN). This document describes a mechanism
that requires no changes to any DNS server or resolver that will allow
internationalized host names to be used by end users with changes only
to applications. It allows flexibility for user input and display, and
assures that host names that have non-ASCII characters are not sent to
DNS servers or resolvers.

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

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-idn-idna-03.txt

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

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

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Fri Aug  3 05:27:33 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA10807
	for <idn-archive@lists.ietf.org>; Fri, 3 Aug 2001 05:27:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15SajF-000JUL-00
	for idn-data@psg.com; Fri, 03 Aug 2001 01:54:45 -0700
Received: from postoffice.sarnoff.com ([130.33.10.147])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15SajD-000JRW-01
	for idn@ops.ietf.org; Fri, 03 Aug 2001 01:54:44 -0700
Received: from postoffice.sarnoff.com ([127.0.0.1]) by
          postoffice.sarnoff.com (Netscape Messaging Server 4.15) with
          SMTP id GHHFEI00.AQP for <idn@ops.ietf.org>; Fri, 3 Aug 2001
          03:56:42 -0400 
Received: from nova.sarnoff.com ([130.33.8.27]) by
          postoffice.sarnoff.com (Netscape Messaging Server 4.15) with
          ESMTP id GH5TH800.BG8; Fri, 27 Jul 2001 21:29:32 -0400 
Received: from loki.ietf.org (loki.ietf.org [132.151.1.177])
	by nova.sarnoff.com (8.9.2/8.9.2) with ESMTP id MAA17545;
	Tue, 24 Jul 2001 12:01:30 -0400 (EDT)
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id LAA17436
	for ietf-123-outbound.05@ietf.org; Tue, 24 Jul 2001 11:35:00 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id GAA12793
	for <all-ietf@loki.ietf.org>; Tue, 24 Jul 2001 06:31:29 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06327;
	Tue, 24 Jul 2001 06:31:28 -0400 (EDT)
Message-Id: <200107241031.GAA06327@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: idn@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [idn] I-D ACTION:draft-ietf-idn-nameprep-05.txt
Date: Tue, 24 Jul 2001 06:31:27 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: Preparation of Internationalized Host Names
	Author(s)	: P. Hoffman, M. Blanchet
	Filename	: draft-ietf-idn-nameprep-05.txt
	Pages		: 
	Date		: 23-Jul-01
	
This document describes how to prepare internationalized host names for
use in the DNS. The steps include:
- mapping characters to other characters, such as to change their case
- normalizing the characters
- excluding characters that are prohibited from appearing in
internationalized host names
This document does not specify a wire protocol. This preparation should
be done before the DNS request.

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

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-idn-nameprep-05.txt

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

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

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Fri Aug  3 10:47:45 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA17309
	for <idn-archive@lists.ietf.org>; Fri, 3 Aug 2001 10:47:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Sfqz-0004v5-00
	for idn-data@psg.com; Fri, 03 Aug 2001 07:23:05 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Sfqz-0004rH-00
	for idn@ops.ietf.org; Fri, 03 Aug 2001 07:23:05 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net for <idn@ops.ietf.org>;
          Fri, 3 Aug 2001 07:31:41 -0700
Message-ID: <009901c11c28$a4fb80a0$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: <idn@ops.ietf.org>
Subject: [idn] <.traditional> and <.simplified> TLDs for Supreme CDN
Date: Fri, 3 Aug 2001 10:29:02 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0094_01C11C07.1D746280"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0094_01C11C07.1D746280
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Although my draft is not ready to be released until Aug 14, the =
following should provide some insight as to how it may work...

Currently the English system uses ".com", ".net", "org", etc as the TLD. =
 The purpose of such a symbology is to represent a company, a network, =
an organization, etc..  However, for the Chinese culture, the concept of =
the ".com" representing a company takes a back seat to the much more =
important need for TLDs to represent Traditional Chinese and Simplified =
Chinese.  (Imagine the use of the ccTLDs ".tc" and ".sc" to serve such a =
purpose.)

In the <idn>.<idn> system, the Chinese culture will benefit with TLDs of =
<idn>.<traditional> and <idn>.<simplified>.

The word "traditional" in traditional Chinese is "=E7=B9=81=E9=AB=94" =
(7E41)(9AD4)
The word "traditional" in simplified Chinese is "=E7=B9=81=E4=BD=93" =
(7E41)(4F53)
The word "simplified" in simplified Chinese is "=E7=AE=80=E4=BD=93" =
(7B80)(4F53)
The word "simplified" in traditional Chinese is "=E7=B0=A1=E9=AB=94" =
(7C21)(9AD4)

I have registered the domains (=E7=B9=81=E9=AB=94.cn, =
=E7=B0=A1=E9=AB=94.cn, =E7=B9=81=E4=BD=93.cn, =E7=AE=80=E4=BD=93.cn) =
under my company in China called "Notneb Company".  I have already =
express my intentions to CNNIC and I just want to make it a public =
statement for the record- "if the domains are indeed to become TLDs as I =
would like, I plan to donate them back to CNNIC where I believe they can =
do a much better job than I to benefit the Chinese culture."

It is not a straight forward concept as there must be a relationship =
between the ".<traditional>" and the ".<simplified>" TLDs.  The =
techniques will be detailed in my draft.

Thanks
Ben Chan


------=_NextPart_000_0094_01C11C07.1D746280
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<META content=3D"MSHTML 5.50.4616.200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>Although&nbsp;my draft&nbsp;is not =
ready to be=20
released until Aug 14, the following should provide some insight as to =
how it=20
may work...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Currently the English system uses =
".com", ".net",=20
"org", etc as the TLD.&nbsp; The purpose of such a symbology is to =
represent a=20
company, a network, an organization, etc..&nbsp; However, for the =
Chinese=20
culture, the concept of the ".com" representing a company takes a back =
seat to=20
the much more important&nbsp;need for TLDs to represent Traditional =
Chinese and=20
Simplified Chinese.&nbsp; (Imagine the use of the ccTLDs ".tc" and ".sc" =
to=20
serve such a purpose.)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>In the &lt;idn&gt;.&lt;idn&gt; system, =
the Chinese=20
culture will benefit with TLDs of &lt;idn&gt;.&lt;traditional&gt; and=20
&lt;idn&gt;.&lt;simplified&gt;.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The&nbsp;word "traditional" in =
traditional Chinese=20
is&nbsp;"=E7=B9=81=E9=AB=94" (7E41)(9AD4)</FONT></DIV>
<DIV>The word "traditional" in simplified Chinese is =
"=E7=B9=81=E4=BD=93" (7E41)(4F53)</DIV>
<DIV><FONT face=3DArial size=3D2>The word "simplified" in simplified =
Chinese is "=E7=AE=80=E4=BD=93"=20
(7B80)(4F53)</FONT></DIV>
<DIV>The word "simplified" in traditional Chinese is =
"=E7=B0=A1=E9=AB=94" (7C21)(9AD4)</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I have registered the =
domains&nbsp;(=E7=B9=81=E9=AB=94.cn, =E7=B0=A1=E9=AB=94.cn,=20
=E7=B9=81=E4=BD=93.cn, =E7=AE=80=E4=BD=93.cn) under my company in China =
called "Notneb Company".&nbsp; I have=20
already express my intentions to CNNIC and I just want to make it a =
public=20
statement for the record- "if the domains&nbsp;are indeed to become TLDs =
as I=20
would like, I plan to donate them back to CNNIC where I believe they can =
do a=20
much better job&nbsp;than I&nbsp;to benefit the Chinese =
culture."</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>It is not a straight forward concept as =
there must=20
be a relationship&nbsp;between the ".&lt;traditional&gt;" and the=20
".&lt;simplified&gt;" TLDs.&nbsp; The techniques will be detailed in my=20
draft.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Ben Chan</FONT></DIV>
<DIV><FONT face=3DArial =
size=3D2></FONT>&nbsp;</DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_0094_01C11C07.1D746280--




From owner-idn@ops.ietf.org  Fri Aug  3 16: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 QAA29035
	for <idn-archive@lists.ietf.org>; Fri, 3 Aug 2001 16:53:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15SlV7-000HgF-00
	for idn-data@psg.com; Fri, 03 Aug 2001 13:24:53 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15SlV6-000HaE-00
	for idn@ops.ietf.org; Fri, 03 Aug 2001 13:24:52 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f73KKpN41911;
	Fri, 3 Aug 2001 16:20:51 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200108032020.f73KKpN41911@nic-naa.net>
To: idn@ops.ietf.org
cc: J.Crowcroft@cs.ucl.ac.uk, brunner@nic-naa.net
Subject: Re: [idn] UTF8 Dinner (curry) at London (Tuesday) 
In-Reply-To: Your message of "Wed, 01 Aug 2001 11:18:19 EDT."
             <200108011518.f71FIJN32766@nic-naa.net> 
Date: Fri, 03 Aug 2001 16:20:51 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Thank you Jon for dependable, Indian Dinning Notes (IDN) service!

Assuming that yesterday's bombing proximal to Euston Station hasn't affected
service at Dihawana's Bel Pourri house in Drummond Street, by Euston Station,
("vegetarian  and really unusually and VERY good") or the other two other good
places Jon mentioned, I propose we meet in front of the Hilton Rooms 9/10 on
Tuesday at 1930 (7:30pm for civilians).

This will allow for anyone who wants or needs to participate in the dnssec
status meeting, which is in Hilton Rooms 9/10 on Tuesday at 1830-1930, for
folks working on dnssec experiments and/or implementations.

This will also allow for some traffic calming (shorter cab/tube time to
Euston), and necessary visits to hotel rooms to dump laptops, notes, and
allow some time for attitude adjustment, as necessary.

People who plan to go directly from their hotel to Dihawana's Bel Pourri
please don't bother to make the loop past the Hilton Rooms. Just go and
enjoy!

Eric 



From owner-idn@ops.ietf.org  Fri Aug  3 19:26: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 TAA00855
	for <idn-archive@lists.ietf.org>; Fri, 3 Aug 2001 19:26:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15So1G-000N0a-00
	for idn-data@psg.com; Fri, 03 Aug 2001 16:06:14 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15So1F-000Mwh-00
	for idn@ops.ietf.org; Fri, 03 Aug 2001 16:06:13 -0700
Received: from bbthead.brandenburg.com (2Cust75.tnt3.mia1.da.uu.net [63.38.30.75])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id PAA27877;
	Fri, 3 Aug 2001 15:11:40 -0700
Message-Id: <5.1.0.14.2.20010803135104.032186f0@brandenburg.com>
X-Sender: dcrocker@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 03 Aug 2001 13:52:31 -0400
To: David Hopwood <david.hopwood@zetnet.co.uk>
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: Re: [idn] We are quibbling about WHAT?
Cc: idn@ops.ietf.org
In-Reply-To: <3B658372.C8B05B3C@zetnet.co.uk>
References: <5.1.0.14.2.20010729172557.0302f008@brandenburg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 11:55 AM 7/30/2001, David Hopwood wrote:
>The debate between ACE and UTF-8 has nothing to do with encoding
>efficiency. The benefit of UTF-8 is in having DNS names in the same
>encoding as the surrounding text, rather than having to treat them as a
>special case.

"surrounding text"???  you mean like this message?

sorry, no.  DNS strings occur in many situations.  Most do not, today, use 
UTF-8,

As to predictions of the future, well, thety are always wrong.  (No doubt 
including this one.)

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 Aug  4 10:35: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 KAA26674
	for <idn-archive@lists.ietf.org>; Sat, 4 Aug 2001 10:35:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15T26c-000O1q-00
	for idn-data@psg.com; Sat, 04 Aug 2001 07:08:42 -0700
Received: from mail2-smtp.szptt.net.cn ([202.96.136.222] helo=public.szptt.net.cn)
	by psg.com with smtp (Exim 3.31 #1)
	id 15T26b-000O1k-00
	for idn@ops.ietf.org; Sat, 04 Aug 2001 07:08:41 -0700
Received: from public.szptt.net.cn([202.96.136.225]) by public.szptt.net.cn(JetMail 2.5.3.0)
	with SMTP id jm43b6c02be; Sat,  4 Aug 2001 14:06:03 -0000
Received: from loki.ietf.org([132.151.1.177]) by public.szptt.net.cn(JetMail 2.5.3.0)
	with SMTP id jm53b5f502b; Wed, 25 Jul 2001 22:31:58 -0000
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id MAA00543
	for ietf-123-outbound.01@ietf.org; Wed, 25 Jul 2001 12:25:00 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id GAA25641
	for <all-ietf@loki.ietf.org>; Wed, 25 Jul 2001 06:35:23 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07829;
	Wed, 25 Jul 2001 06:35:19 -0400 (EDT)
Message-Id: <200107251035.GAA07829@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: idn@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [idn] I-D ACTION:draft-ietf-idn-idna-03.txt
Date: Wed, 25 Jul 2001 06:35:18 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: Internationalizing Host Names In Applications (IDNA)
	Author(s)	: P. Hoffman, P. Faltstrom
	Filename	: draft-ietf-idn-idna-03.txt
	Pages		: 
	Date		: 24-Jul-01
	
The current DNS infrastructure does not provide a way to use
internationalized host names (IDN). This document describes a mechanism
that requires no changes to any DNS server or resolver that will allow
internationalized host names to be used by end users with changes only
to applications. It allows flexibility for user input and display, and
assures that host names that have non-ASCII characters are not sent to
DNS servers or resolvers.

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

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-idn-idna-03.txt

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

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

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Tue Aug  7 05:04: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 FAA28274
	for <idn-archive@lists.ietf.org>; Tue, 7 Aug 2001 05:04:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15U2JF-000IEh-00
	for idn-data@psg.com; Tue, 07 Aug 2001 01:33:53 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15U2JE-000IEX-00
	for idn@ops.ietf.org; Tue, 07 Aug 2001 01:33:52 -0700
Received: from amc by nicemice.net with local (Exim 3.31 #1 (Debian))
	id 15U2JD-0002b4-00; Tue, 07 Aug 2001 01:33:51 -0700
Date: Tue, 7 Aug 2001 08:33:51 +0000
To: idn working group <idn@ops.ietf.org>
Subject: [idn] AMC-ACE-Z version 0.3.0
Message-ID: <20010807083351.B7519@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.18i
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I've made three very slight changes to AMC-ACE-Z, one to fix a small
bug, and two to make it very slightly simpler and a little more
flexible, with virtually no effect on the encoding length.  The new spec
is available at:

http://www.cs.berkeley.edu/~amc/charset/

I won't be able to submit it as an internet-draft until after the next
IETF meeting.

The rest of this message describes the changes.

First change:  Formerly, LDH characters were encoded literally and
non-LDH ASCII characters were forbidden.  Now all ASCII characters
are encoded literally.  This has no consequence for LDH names, but is
reasonable behavior for less restrictive names (like the names of SRV
records).  (And it matches the behavior of UTF-8.)

Second change:  The initial value of n is now 0x80 instead of 0xA1 (this
is an incompatible change).

With these two changes, the encoder no longer needs to check for invalid
input, because there is no such thing anymore; AMC-ACE-Z can now encode
any Unicode string as an ASCII string.  The ASCII string will contain
non-LDH ASCII characters only if the Unicode string does.

Third change (bug fix):  The decoder had neglected to verify that the
input contains only ASCII characters.

AMC



From owner-idn@ops.ietf.org  Tue Aug  7 08:59: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 IAA02739
	for <idn-archive@lists.ietf.org>; Tue, 7 Aug 2001 08:59:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15U6GQ-000OHd-00
	for idn-data@psg.com; Tue, 07 Aug 2001 05:47:14 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15U6GP-000OHV-00
	for idn@ops.ietf.org; Tue, 07 Aug 2001 05:47:13 -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 f77DAkQ57887
	for <idn@ops.ietf.org>; Tue, 7 Aug 2001 09:10:46 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010807082439.03681ec0@127.0.0.1>
X-Sender: blanchet@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 07 Aug 2001 08:50:05 -0400
To: idn@ops.ietf.org
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: [idn] agenda v1.0 ietf-london
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hi,
  here is a first cut of the proposed agenda. The idea here is to leave 
room for concensus building.

==================================================
Agenda:
  agenda bashing, 1 min., Marc Blanchet
  wg update, 5 min., Marc Blanchet
  ACE encoding
   ACE comparison, 5 min., Yoshiro Yoneya
   Reordering, 5 min., Soobok Lee
   ACE concensus building (Choosing an ACE if we need one), 5 min.
  Matching
   Nameprep update, 5 min., Paul Hoffman
   TSconv, 5 min., Xiang Deng
   Hangulchar, 5 min., Soobok Lee
   Matching concensus building, 10 min.
  Protocol
   Protocol comparison, 10 min., Dave Crocker
   Protocol concensus building, 55 min.
  Conclusion and next steps, 10 min.
================================================

Marc & James.

PS1. I was on vacation for the past few weeks, so that is why both the 
agenda and the pool were not updated.
PS2. I will update the web site shortly and will announce in a separate 
email the document pool (a few are not yet there because of PS1 above).




From owner-idn@ops.ietf.org  Wed Aug  8 04:09: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 EAA07821
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 04:09:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UNya-0003qx-00
	for idn-data@psg.com; Wed, 08 Aug 2001 00:42:00 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UNyZ-0003qq-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 00:41:59 -0700
Received: from [217.33.138.59] (host217-33-138-59.ietf.ignite.net [217.33.138.59])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f787fvN16893
	for <idn@ops.ietf.org>; Wed, 8 Aug 2001 00:41:58 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100324b7967c8db4b7@[217.33.138.59]>
In-Reply-To: <5.1.0.14.1.20010807082439.03681ec0@127.0.0.1>
References: <5.1.0.14.1.20010807082439.03681ec0@127.0.0.1>
Date: Wed, 8 Aug 2001 06:28:52 +0100
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: [idn] Proposed agenda v2.0 ietf-london
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 8:50 AM -0400 8/7/01, Marc Blanchet wrote:
>Hi,
>  here is a first cut of the proposed agenda. The idea here is to 
>leave room for concensus building.

The first proposed agenda has a lot of valuable time spent giving 
presentations about Internet Drafts. Although this has been common in 
the IDN WG (and many other WGs) at past IETF meetings, it is probably 
not a good use of the WG's time, given our limited meeting slot. 
People at the meeting should have read the drafts before the meeting, 
and the meeting should be used for discussing technical merits and 
consensus building.

Original proposal:

>  agenda bashing, 1 min., Marc Blanchet
>  wg update, 5 min., Marc Blanchet
>  ACE encoding
>   ACE comparison, 5 min., Yoshiro Yoneya
>   Reordering, 5 min., Soobok Lee
>   ACE concensus building (Choosing an ACE if we need one), 5 min.
>  Matching
>   Nameprep update, 5 min., Paul Hoffman
>   TSconv, 5 min., Xiang Deng
>   Hangulchar, 5 min., Soobok Lee
>   Matching concensus building, 10 min.
>  Protocol
>   Protocol comparison, 10 min., Dave Crocker
>   Protocol concensus building, 55 min.
>  Conclusion and next steps, 10 min.

Proposal without Internet Draft presentations:

  agenda bashing, 1 min., Marc Blanchet
  wg update, 5 min., Marc Blanchet
  ACE encoding
   ACE comparison, 5 min., Yoshiro Yoneya
   ACE consensus building (Choosing an ACE if we need one), 10 min.
  Matching
   Matching consensus building, 20 min.
  Protocol
   Protocol comparison, 10 min., Dave Crocker
   Protocol consensus building, 60 min.
  Conclusion and next steps, 10 min.

Do other folks at the London meeting agree with this proposed agenda revision?

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Wed Aug  8 05:32: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 FAA08897
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 05:32:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UPU0-0006OV-00
	for idn-data@psg.com; Wed, 08 Aug 2001 02:18: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.31 #1)
	id 15UPTz-0006NM-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 02:18:31 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f789Fw311494;
	Wed, 8 Aug 2001 05:15:58 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200108080915.f789Fw311494@nic-naa.net>
To: Paul Hoffman / IMC <phoffman@imc.org>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Proposed agenda v2.0 ietf-london 
In-Reply-To: Your message of "Wed, 08 Aug 2001 06:28:52 BST."
             <p05100324b7967c8db4b7@[217.33.138.59]> 
Date: Wed, 08 Aug 2001 05:15:58 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> >Hi,
> >  here is a first cut of the proposed agenda. The idea here is to 
> >leave room for concensus building.

Some, fine.
...
> Do other folks at the London meeting agree with this proposed agenda revision?

Blowing off most of the meeting time on vague "consensus building"?

No thanks. Far too much list-time is spent on that subject, and turning
the remaining technical time into more of the same is odd.

In my personal opinion, chairs should meet with presenters prior and
where needed, improve individual presenters presentations.

> --Paul Hoffman, Director
> --Internet Mail Consortium




From owner-idn@ops.ietf.org  Wed Aug  8 05:37: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 FAA08972
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 05:37:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UPTx-0006O7-00
	for idn-data@psg.com; Wed, 08 Aug 2001 02:18:29 -0700
Received: from heron.verisign.com ([216.168.233.95])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UPTw-0006MO-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 02:18:28 -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 FAA27026
	for <idn@ops.ietf.org>; Wed, 8 Aug 2001 05:17:57 -0400 (EDT)
Received: by VSVAPOSTALGW1.prod.netsol.com with Internet Mail Service (5.5.2653.19)
	id <NP4FJDJ6>; Wed, 8 Aug 2001 05:17:53 -0400
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60B8455@vsvapostal3.prod.netsol.com>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: idn@ops.ietf.org
Subject: RE: [idn] Proposed agenda v2.0 ietf-london
Date: Wed, 8 Aug 2001 05:12:28 -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, August 08, 2001 1:29 AM
>To: idn@ops.ietf.org
>Subject: [idn] Proposed agenda v2.0 ietf-london
>
>
>At 8:50 AM -0400 8/7/01, Marc Blanchet wrote:
>>Hi,
>>  here is a first cut of the proposed agenda. The idea here is to 
>>leave room for concensus building.
>
>The first proposed agenda has a lot of valuable time spent giving 
>presentations about Internet Drafts. Although this has been common in 
>the IDN WG (and many other WGs) at past IETF meetings, it is probably 
>not a good use of the WG's time, given our limited meeting slot. 
>People at the meeting should have read the drafts before the meeting, 
>and the meeting should be used for discussing technical merits and 
>consensus building.
>
>Original proposal:
>
>>  agenda bashing, 1 min., Marc Blanchet
>>  wg update, 5 min., Marc Blanchet
>>  ACE encoding
>>   ACE comparison, 5 min., Yoshiro Yoneya
>>   Reordering, 5 min., Soobok Lee
>>   ACE concensus building (Choosing an ACE if we need one), 5 min.
>>  Matching
>>   Nameprep update, 5 min., Paul Hoffman
>>   TSconv, 5 min., Xiang Deng
>>   Hangulchar, 5 min., Soobok Lee
>>   Matching concensus building, 10 min.
>>  Protocol
>>   Protocol comparison, 10 min., Dave Crocker
>>   Protocol concensus building, 55 min.
>>  Conclusion and next steps, 10 min.
>
>Proposal without Internet Draft presentations:
>
>  agenda bashing, 1 min., Marc Blanchet
>  wg update, 5 min., Marc Blanchet
>  ACE encoding
>   ACE comparison, 5 min., Yoshiro Yoneya
>   ACE consensus building (Choosing an ACE if we need one), 10 min.
>  Matching
>   Matching consensus building, 20 min.
>  Protocol
>   Protocol comparison, 10 min., Dave Crocker
>   Protocol consensus building, 60 min.
>  Conclusion and next steps, 10 min.
>
>Do other folks at the London meeting agree with this proposed 
>agenda revision?

I support this change.  As Paul noted, we have quite a bit to talk about
around technical merits and consensus building and I'd prefer to ensure that
we cover all of the _really_ pressing issues.

<Scott/>



From owner-idn@ops.ietf.org  Wed Aug  8 05:40: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 FAA09007
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 05:40:21 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UPVk-0006RC-00
	for idn-data@psg.com; Wed, 08 Aug 2001 02:20:20 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15UPVj-0006R6-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 02:20:19 -0700
Message-ID: <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net>
From: "Edmon" <edmon@neteka.com>
To: "ben" <ben@cc-www.com>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
References: <200107301509.f6UF91N23867@nic-naa.net>
Subject: [idn] opting out of SC/TC equivalence
Date: Wed, 8 Aug 2001 05:24:39 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
> What is the key value for users "opting out" of SC/TC equivalences?

There are two main scenarios that I could think of that I would like to see
SC/TC opted out.
Say I wanted to have different online identities in the PRC, HongKong and
Taiwan with two Chinese charcters.  And I want to use:
<SC><SC> in PRC
<SC><TC> in HK and
<TC><TC> in Taiwan

I want them to resolve to different places. If SC/TC is folded, I will not
be able to do so.  Which means if I have an employee John in both the PRC
and Taiwan, I could not use John@<SC><SC> and John@<TC><TC> at the same time
and use it for different person.

Scenario two:
If I have a franchisee/partnership operations in the above three regions and
the ownership of each is very different, but we want to maintain the name.
We wont be able to use the SC/TC/mix to distinguish our domains.

Edmon












From owner-idn@ops.ietf.org  Wed Aug  8 06:26: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 GAA09687
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 06:26:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UQIb-00081D-00
	for idn-data@psg.com; Wed, 08 Aug 2001 03:10: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.31 #1)
	id 15UQIa-000817-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 03:10:49 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f78A8H312742;
	Wed, 8 Aug 2001 06:08:17 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200108081008.f78A8H312742@nic-naa.net>
To: "Edmon" <edmon@neteka.com>
cc: "ben" <ben@cc-www.com>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] opting out of SC/TC equivalence 
In-Reply-To: Your message of "Wed, 08 Aug 2001 05:24:39 EDT."
             <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net> 
Date: Wed, 08 Aug 2001 06:08:17 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

In a previous note I commented on the scaling issue I understand this form
of [30] (registrant assigned equivalence rules, vs zone manager assigned
equivalence rules, in obsoleted versions of the requirements draft) to pose.
Insight into proposed mechanism and its scaling properties would be of real
interest.

I also suggested to the earlier proponent of this form of [30] that s/he
attempt to state a variation of [30] that would express his or her, and now
your, desired policy.

Eric



From owner-idn@ops.ietf.org  Wed Aug  8 07:01: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 HAA10068
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 07:01:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UQnP-000941-00
	for idn-data@psg.com; Wed, 08 Aug 2001 03:42:39 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UQnO-00093q-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 03:42:38 -0700
Received: from test.ncu.edu.tw ([140.115.5.251])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f78Al6710103;
	Wed, 8 Aug 2001 18:47:07 +0800 (CST)
Message-ID: <001601c11fed$a80b2f20$fb05738c@ncu.edu.tw>
From: =?big5?B?dHNlbmdsbUCtcLr0pKSk3y6kpKRqLnR3?= <tsenglm@cc.ncu.edu.tw>
To: "Edmon" <edmon@neteka.com>, "ben" <ben@cc-www.com>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
References: <200107301509.f6UF91N23867@nic-naa.net> <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Wed, 8 Aug 2001 17:36:51 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Edmon" <edmon@neteka.com>
To: "ben" <ben@cc-www.com>; "Eric Brunner-Williams in Portland Maine"
<brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
Sent: Wednesday, August 08, 2001 5:24 PM
Subject: [idn] opting out of SC/TC equivalence


> From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
> > What is the key value for users "opting out" of SC/TC equivalences?
>
> There are two main scenarios that I could think of that I would like to
see
> SC/TC opted out.
> Say I wanted to have different online identities in the PRC, HongKong and
> Taiwan with two Chinese charcters.  And I want to use:
> <SC><SC> in PRC
> <SC><TC> in HK and
> <TC><TC> in Taiwan
>
> I want them to resolve to different places. If SC/TC is folded, I will not
> be able to do so.  Which means if I have an employee John in both the PRC
> and Taiwan, I could not use John@<SC><SC> and John@<TC><TC> at the same
time
> and use it for different person.
>
> Scenario two:
> If I have a franchisee/partnership operations in the above three regions
and
> the ownership of each is very different, but we want to maintain the name.
> We wont be able to use the SC/TC/mix to distinguish our domains.
         In  HongKong, people use BIG5 code that is major in traditional
chinese characters,
After 1997,  Hong-Kong Goverment announce an extension set including fonts
of TC/SC.
MicroSoft provided them with GBK code but display the message in TC font.
GBK is the extension of GB, and  China use them in MicroSoft IE now.  GBK
include the font of some traditional chinese character.  The TC/SC
translation  majorly focus on BIG5 <-> UNICODE <-> GBK , especially for BIG5
<--> GB/GBK.
         If TC/SC  one to one  font/script mapping is fiexed, it shoud be
processed in normalization/unification phase .  But  one to many font/script
mapping can not be easily solved by this way,  if the mixing type
<SC><TC><SC><TC>  are all one one mapping in each character then they will
be reduced to one canonical  representation.  If the mixing type including
one to many characters  one string are assigned by the registrant in
registration time.
         That draft is just to solve your 2  problems.  Hope these can help
understanding.
>
> Edmon


L.M.Tseng




From owner-idn@ops.ietf.org  Wed Aug  8 07:01: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 HAA10069
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 07:01:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UQgF-0008ou-00
	for idn-data@psg.com; Wed, 08 Aug 2001 03:35:15 -0700
Received: from mail-blue.research.att.com ([135.207.30.102])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UQgE-0008oo-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 03:35:14 -0700
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id F3E084CE0C; Wed,  8 Aug 2001 06:35:13 -0400 (EDT)
Received: from host217-33-136-108.ietf.ignite.net (secure.research.att.com [135.207.24.10])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id GAA24951;
	Wed, 8 Aug 2001 06:35:08 -0400 (EDT)
Date: Wed, 08 Aug 2001 06:34:21 -0400
From: John C Klensin <klensin@research.att.com>
To: Edmon <edmon@neteka.com>
Cc: idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <13749451.997252461@host217-33-136-108.ietf.ignite.net>
In-Reply-To: <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net>
References:  <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net>
X-Mailer: Mulberry/2.1.0b3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Wednesday, 08 August, 2001 05:24 -0400 Edmon
<edmon@neteka.com> wrote:

> From: "Eric Brunner-Williams in Portland Maine"
> <brunner@nic-naa.net>
>> What is the key value for users "opting out" of SC/TC
>> equivalences?
> 
> There are two main scenarios that I could think of that I would
> like to see SC/TC opted out.
> Say I wanted to have different online identities in the PRC,
> HongKong and Taiwan with two Chinese charcters.  And I want to
> use: <SC><SC> in PRC
> <SC><TC> in HK and
> <TC><TC> in Taiwan
> 
> I want them to resolve to different places. If SC/TC is folded,
> I will not be able to do so.  Which means if I have an employee
> John in both the PRC and Taiwan, I could not use John@<SC><SC>
> and John@<TC><TC> at the same time and use it for different
> person.
> 
> Scenario two:
> If I have a franchisee/partnership operations in the above
> three regions and the ownership of each is very different, but
> we want to maintain the name. We wont be able to use the
> SC/TC/mix to distinguish our domains.

Edmon,

I think we have been here before --in terms of things the DNS
can't do and should not be expected to do-- in only slightly
different form.

Briefly, either SC and TC are equivalent, or they are not.  If
they are, we shouldn't be having this discussion.  If they are
not, we shouldn't be having this discussion either.  In the
particular case of TC and SC, what we have been told, repeatedly,
is that people (normal human beings, not computer experts), will
expect to be able to use them interchangably.   If you try to do
this, you will get errors in the hosts or sites that are found
when people forget your subtle distinctions/ clues and get them
wrong.

What you are asking for is, IMO, really 

Scenario one: 
  Different resolution for <name> based on whether it is resolved
wrt a site in PRC, HK, or Taiwan.

Scenario two:
  Different resolution for <name> based on whether it is resolved
by a user located in PRC, HK, or Taiwan.

Both of those desires generalize to other places, other scripts,
and other languages.  Both are legitimate.  But they require
information about context, not little tricks of script-choice,
especially on a per-character basis.

Now, while I don't think the idea is satisfactory for many
reasons, you could get that context from the TLD.  <name>.CN,
<name>.HK, and <name>.TW are clearly different; we would expect
them to resolve differently (although they could be made to
resolve to the same target if someone wished).  And we would
expect that behavior whether we fold SC and TC together or not.  

Otherwise, IMO, you need to get the context from something else,
and that means "outside the DNS".

    john




From owner-idn@ops.ietf.org  Wed Aug  8 07:03: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 HAA10093
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 07:03:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UQiP-0008tj-00
	for idn-data@psg.com; Wed, 08 Aug 2001 03:37:29 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15UQiO-0008tM-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 03:37:28 -0700
Message-ID: <001301c11ff7$3d9bfa20$5b8d21d9@ietf.ignite.net>
From: "Edmon" <edmon@neteka.com>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: "ben" <ben@cc-www.com>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        <idn@ops.ietf.org>
References: <200108081008.f78A8H312742@nic-naa.net>
Subject: Re: [idn] opting out of SC/TC equivalence 
Date: Wed, 8 Aug 2001 06:43:18 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Eric,
I dont really have a specific "policy" in mind, its just some scenarios that
I think needs consideration when making such policies.
Edmon


----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
> In a previous note I commented on the scaling issue I understand this form
> of [30] (registrant assigned equivalence rules, vs zone manager assigned
> equivalence rules, in obsoleted versions of the requirements draft) to
pose.
> Insight into proposed mechanism and its scaling properties would be of
real
> interest.
>
> I also suggested to the earlier proponent of this form of [30] that s/he
> attempt to state a variation of [30] that would express his or her, and
now
> your, desired policy.
>
> Eric




From owner-idn@ops.ietf.org  Wed Aug  8 09:32: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 JAA12232
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 09:32:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UT71-000DeO-00
	for idn-data@psg.com; Wed, 08 Aug 2001 06:11:03 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15UT70-000DeI-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 06:11:02 -0700
Message-ID: <001201c1200c$b00e2d20$5b8d21d9@ietf.ignite.net>
From: "Edmon" <edmon@neteka.com>
To: "John C Klensin" <klensin@research.att.com>
Cc: <idn@ops.ietf.org>
References:  <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net> <13749451.997252461@host217-33-136-108.ietf.ignite.net>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Wed, 8 Aug 2001 09:18:56 -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

First of all, sorry for missing out on the previous discussions.
Anyway, I think the point I want to make is that perhaps it makes sense for
SC/TC equivalence to be an optional technical policy matter for different
registries.  Perhaps ccTLDs such as .hk, .tw, .cn, .sg will adopt the SC=TC
and gTLDs might opt not to adopt it.  Does anyone think this is sensible?
Or does everyone believe that SC=TC should be part of nameprep?
Edmon


----- Original Message -----
From: "John C Klensin" <klensin@research.att.com>
To: "Edmon" <edmon@neteka.com>
Cc: <idn@ops.ietf.org>
Sent: Wednesday, August 08, 2001 6:34 AM
Subject: Re: [idn] opting out of SC/TC equivalence


> --On Wednesday, 08 August, 2001 05:24 -0400 Edmon
> <edmon@neteka.com> wrote:
>
> > From: "Eric Brunner-Williams in Portland Maine"
> > <brunner@nic-naa.net>
> >> What is the key value for users "opting out" of SC/TC
> >> equivalences?
> >
> > There are two main scenarios that I could think of that I would
> > like to see SC/TC opted out.
> > Say I wanted to have different online identities in the PRC,
> > HongKong and Taiwan with two Chinese charcters.  And I want to
> > use: <SC><SC> in PRC
> > <SC><TC> in HK and
> > <TC><TC> in Taiwan
> >
> > I want them to resolve to different places. If SC/TC is folded,
> > I will not be able to do so.  Which means if I have an employee
> > John in both the PRC and Taiwan, I could not use John@<SC><SC>
> > and John@<TC><TC> at the same time and use it for different
> > person.
> >
> > Scenario two:
> > If I have a franchisee/partnership operations in the above
> > three regions and the ownership of each is very different, but
> > we want to maintain the name. We wont be able to use the
> > SC/TC/mix to distinguish our domains.
>
> Edmon,
>
> I think we have been here before --in terms of things the DNS
> can't do and should not be expected to do-- in only slightly
> different form.
>
> Briefly, either SC and TC are equivalent, or they are not.  If
> they are, we shouldn't be having this discussion.  If they are
> not, we shouldn't be having this discussion either.  In the
> particular case of TC and SC, what we have been told, repeatedly,
> is that people (normal human beings, not computer experts), will
> expect to be able to use them interchangably.   If you try to do
> this, you will get errors in the hosts or sites that are found
> when people forget your subtle distinctions/ clues and get them
> wrong.
>
> What you are asking for is, IMO, really
>
> Scenario one:
>   Different resolution for <name> based on whether it is resolved
> wrt a site in PRC, HK, or Taiwan.
>
> Scenario two:
>   Different resolution for <name> based on whether it is resolved
> by a user located in PRC, HK, or Taiwan.
>
> Both of those desires generalize to other places, other scripts,
> and other languages.  Both are legitimate.  But they require
> information about context, not little tricks of script-choice,
> especially on a per-character basis.
>
> Now, while I don't think the idea is satisfactory for many
> reasons, you could get that context from the TLD.  <name>.CN,
> <name>.HK, and <name>.TW are clearly different; we would expect
> them to resolve differently (although they could be made to
> resolve to the same target if someone wished).  And we would
> expect that behavior whether we fold SC and TC together or not.
>
> Otherwise, IMO, you need to get the context from something else,
> and that means "outside the DNS".
>
>     john
>




From owner-idn@ops.ietf.org  Wed Aug  8 09:45: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 JAA12504
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 09:45:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UT8b-000DiF-00
	for idn-data@psg.com; Wed, 08 Aug 2001 06:12:41 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UT8a-000Di9-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 06:12:40 -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, 8 Aug 2001 06:24:19 -0700
Message-ID: <005001c1200d$01f85480$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: =?big5?B?dHNlbmdsbUCtcLr0pKSk3y6kpKRqLnR3?= <tsenglm@cc.ncu.edu.tw>,
        "Edmon" <edmon@neteka.com>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        "John C Klensin" <klensin@research.att.com>
Cc: <idn@ops.ietf.org>
References: <200107301509.f6UF91N23867@nic-naa.net> <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net> <001601c11fed$a80b2f20$fb05738c@ncu.edu.tw>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Wed, 8 Aug 2001 09:21:17 -0400
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.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Although the current ccTLDs and gTLDs will work for IDNs, they cannot
totally satisfy the needs of the users of CDNs.  Another type of TLD
must be created and I will tentatively call it lsTLDs (Language Script
TLDs).  lsTLDs are in native language script... not English- thus
bringing out the issue of <IDN>.<IDN> that ICANN has already expressed
their interest in.

This is not just an issue for ICANN.  I do still need to write a draft
and submit it to the IDN WG because lsTLDs are not a simple straight
forward concept as ccTLDs and gTLDs.  2 techniques / mechanism must be
documented:

1.  A relationship exist between the <.traditional> and <.simplified>
lsTLDs
2.  During Nameprep, an error checking is done to disallow improper
characters for a lsTLD.

Thanks
Ben Chan



----- Original Message -----
From: "tsenglm@­pºô¤¤¤ß.¤¤¤j.tw" <tsenglm@cc.ncu.edu.tw>
To: "Edmon" <edmon@neteka.com>; "ben" <ben@cc-www.com>; "Eric
Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
Sent: Wednesday, August 08, 2001 5:36 AM
Subject: Re: [idn] opting out of SC/TC equivalence



----- Original Message -----
From: "Edmon" <edmon@neteka.com>
To: "ben" <ben@cc-www.com>; "Eric Brunner-Williams in Portland Maine"
<brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
Sent: Wednesday, August 08, 2001 5:24 PM
Subject: [idn] opting out of SC/TC equivalence


> From: "Eric Brunner-Williams in Portland Maine"
<brunner@nic-naa.net>
> > What is the key value for users "opting out" of SC/TC
equivalences?
>
> There are two main scenarios that I could think of that I would like
to
see
> SC/TC opted out.
> Say I wanted to have different online identities in the PRC,
HongKong and
> Taiwan with two Chinese charcters.  And I want to use:
> <SC><SC> in PRC
> <SC><TC> in HK and
> <TC><TC> in Taiwan
>
> I want them to resolve to different places. If SC/TC is folded, I
will not
> be able to do so.  Which means if I have an employee John in both
the PRC
> and Taiwan, I could not use John@<SC><SC> and John@<TC><TC> at the
same
time
> and use it for different person.
>
> Scenario two:
> If I have a franchisee/partnership operations in the above three
regions
and
> the ownership of each is very different, but we want to maintain the
name.
> We wont be able to use the SC/TC/mix to distinguish our domains.
         In  HongKong, people use BIG5 code that is major in
traditional
chinese characters,
After 1997,  Hong-Kong Goverment announce an extension set including
fonts
of TC/SC.
MicroSoft provided them with GBK code but display the message in TC
font.
GBK is the extension of GB, and  China use them in MicroSoft IE now.
GBK
include the font of some traditional chinese character.  The TC/SC
translation  majorly focus on BIG5 <-> UNICODE <-> GBK , especially
for BIG5
<--> GB/GBK.
         If TC/SC  one to one  font/script mapping is fiexed, it shoud
be
processed in normalization/unification phase .  But  one to many
font/script
mapping can not be easily solved by this way,  if the mixing type
<SC><TC><SC><TC>  are all one one mapping in each character then they
will
be reduced to one canonical  representation.  If the mixing type
including
one to many characters  one string are assigned by the registrant in
registration time.
         That draft is just to solve your 2  problems.  Hope these can
help
understanding.
>
> Edmon


L.M.Tseng






From owner-idn@ops.ietf.org  Wed Aug  8 10:35: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 KAA13693
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 10:35:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UU2u-000Fix-00
	for idn-data@psg.com; Wed, 08 Aug 2001 07:10:52 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UU2u-000Fil-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 07:10:52 -0700
Received: from bbthead.dcrocker.net (host217-33-136-170.ietf.ignite.net [217.33.136.170])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id HAA23097;
	Wed, 8 Aug 2001 07:10:47 -0700
Message-Id: <5.1.0.14.2.20010808143501.03f52140@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 08 Aug 2001 14:35:26 +0100
To: "Edmon" <edmon@neteka.com>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] opting out of SC/TC equivalence
Cc: "John C Klensin" <klensin@research.att.com>, <idn@ops.ietf.org>
In-Reply-To: <001201c1200c$b00e2d20$5b8d21d9@ietf.ignite.net>
References: <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net>
 <13749451.997252461@host217-33-136-108.ietf.ignite.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 02:18 PM 8/8/2001, Edmon wrote:
>SC/TC equivalence to be an optional technical policy matter for different
>registries

sorry, no.  it makes the standard useless.

d/


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




From owner-idn@ops.ietf.org  Wed Aug  8 10:35: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 KAA13704
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 10:35:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UUI7-000GIk-00
	for idn-data@psg.com; Wed, 08 Aug 2001 07:26:35 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UUI6-000GIe-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 07:26:34 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.4/8.9.3) with ESMTP id f78ENK318595;
	Wed, 8 Aug 2001 10:23:20 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200108081423.f78ENK318595@nic-naa.net>
To: "ben" <ben@cc-www.com>
cc: =?big5?B?dHNlbmdsbUCtcLr0pKSk3y6kpKRqLnR3?= <tsenglm@cc.ncu.edu.tw>,
        "Edmon" <edmon@neteka.com>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        "John C Klensin" <klensin@research.att.com>, idn@ops.ietf.org,
        brunner@nic-naa.net
Subject: Re: [idn] opting out of SC/TC equivalence 
In-Reply-To: Your message of "Wed, 08 Aug 2001 09:21:17 EDT."
             <005001c1200d$01f85480$d43f7018@mtag1.on.home.com> 
Date: Wed, 08 Aug 2001 10:23:19 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

do let me know when one is added to the root.



From owner-idn@ops.ietf.org  Wed Aug  8 10:43: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 KAA13895
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 10:43:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UUOv-000GZt-00
	for idn-data@psg.com; Wed, 08 Aug 2001 07:33:37 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UUOu-000GZj-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 07:33:36 -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, 8 Aug 2001 07:45:14 -0700
Message-ID: <00bb01c12018$501d83a0$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: =?iso-8859-1?B?dHNlbmdsbUCtcLr0pKSk3y6kpKRqLnR3?= <tsenglm@cc.ncu.edu.tw>,
        "Edmon" <edmon@neteka.com>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        "John C Klensin" <klensin@research.att.com>, <idn@ops.ietf.org>
References: <200108081423.f78ENK318595@nic-naa.net>
Subject: Re: [idn] opting out of SC/TC equivalence 
Date: Wed, 8 Aug 2001 10:42:11 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

The Chinese culture is paramount.

----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: "ben" <ben@cc-www.com>
Cc: "tsenglm@­pºô¤¤¤ß.¤¤¤j.tw" <tsenglm@cc.ncu.edu.tw>; "Edmon"
<edmon@neteka.com>; "Eric Brunner-Williams in Portland Maine"
<brunner@nic-naa.net>; "John C Klensin" <klensin@research.att.com>;
<idn@ops.ietf.org>; <brunner@nic-naa.net>
Sent: Wednesday, August 08, 2001 10:23 AM
Subject: Re: [idn] opting out of SC/TC equivalence


do let me know when one is added to the root.




From owner-idn@ops.ietf.org  Wed Aug  8 11: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 LAA15019
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 11:27:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UV8C-000IKE-00
	for idn-data@psg.com; Wed, 08 Aug 2001 08:20:24 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15UV8C-000IK8-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 08:20:24 -0700
Received: (qmail 14693 invoked by uid 1001); 8 Aug 2001 15:16:02 -0000
Date: 8 Aug 2001 15:16:02 -0000
Message-ID: <20010808151602.2805.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] http://pi.cr.yp.to
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

http://pi.cr.yp.to is a collection of tests for a typical UTF-8 domain
name. Try it with your browser and mailer, and let me know what happens.

---Dan



From owner-idn@ops.ietf.org  Wed Aug  8 12:14: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 MAA16084
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 12:14:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UVdm-000JrZ-00
	for idn-data@psg.com; Wed, 08 Aug 2001 08:53:02 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UVdk-000Jpd-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 08:53:01 -0700
Received: from test.ncu.edu.tw ([140.115.5.251])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f78FvE713412;
	Wed, 8 Aug 2001 23:57:14 +0800 (CST)
Message-ID: <005901c12018$f999e180$fb05738c@ncu.edu.tw>
From: =?big5?B?dHNlbmdsbUCtcLr0pKSk3y6kpKRqLnR3?= <tsenglm@cc.ncu.edu.tw>
To: "ben" <ben@cc-www.com>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: "Edmon" <edmon@neteka.com>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        "John C Klensin" <klensin@research.att.com>, <idn@ops.ietf.org>
References: <200108081423.f78ENK318595@nic-naa.net>
Subject: Re: [idn] opting out of SC/TC equivalence 
Date: Wed, 8 Aug 2001 22:46:56 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> do let me know when one is added to the root.
>
   TC/SC  translation  are these ponits that users need them to reduced the
complexity of number of name registration and user can key in the name they
more familiar.
    This ia a problem of normalization/canonicalization in nameprep, why it
need to add to the root ?   There are many solutions , lsTLD  is just one of
them.

L.M. Tseng




From owner-idn@ops.ietf.org  Wed Aug  8 12:25: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 MAA16321
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 12:25:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UW1l-000KxJ-00
	for idn-data@psg.com; Wed, 08 Aug 2001 09:17:49 -0700
Received: from shell.nominum.com ([128.177.192.160])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UW1k-000Kx4-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 09:17:48 -0700
Received: from drc-toshiba.nominum.com (shell.nominum.com [128.177.192.160])
	by shell.nominum.com (Postfix) with ESMTP
	id DBEF03190C; Wed,  8 Aug 2001 09:17:35 -0700 (PDT)
Message-Id: <5.0.2.1.2.20010808091610.03094c40@localhost>
X-Sender: drc@localhost
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Wed, 08 Aug 2001 09:17:35 -0700
To: "D. J. Bernstein" <djb@cr.yp.to>, idn@ops.ietf.org
From: "David R. Conrad" <david.conrad@nominum.com>
Subject: Re: [idn] http://pi.cr.yp.to
In-Reply-To: <20010808151602.2805.qmail@cr.yp.to>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dan,

You web page is deceitful (as is typical).

Rgds,
-drc

At 03:16 PM 8/8/2001 +0000, D. J. Bernstein wrote:
>http://pi.cr.yp.to is a collection of tests for a typical UTF-8 domain
>name. Try it with your browser and mailer, and let me know what happens.
>
>---Dan




From owner-idn@ops.ietf.org  Wed Aug  8 12:45: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 MAA16882
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 12:45:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UWCY-000LW0-00
	for idn-data@psg.com; Wed, 08 Aug 2001 09:28:58 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UWCX-000LVu-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 09:28:57 -0700
Received: from bbthead.dcrocker.net (host217-33-136-170.ietf.ignite.net [217.33.136.170])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id JAA29126;
	Wed, 8 Aug 2001 09:28:43 -0700
Message-Id: <5.1.0.14.2.20010808172937.02912af0@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 08 Aug 2001 17:30:11 +0100
To: "D. J. Bernstein" <djb@cr.yp.to>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] http://pi.cr.yp.to
Cc: idn@ops.ietf.org
In-Reply-To: <20010808151602.2805.qmail@cr.yp.to>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 04:16 PM 8/8/2001, D. J. Bernstein wrote:
>http://pi.cr.yp.to is a collection of tests for a typical UTF-8 domain
>name. Try it with your browser and mailer, and let me know what happens.

the "pi" links did not work.  i run vanilla Win 2000 and IE.

d/


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




From owner-idn@ops.ietf.org  Wed Aug  8 12: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 MAA17136
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 12:57:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UWXJ-000MSL-00
	for idn-data@psg.com; Wed, 08 Aug 2001 09:50:25 -0700
Received: from ns1.ar.com ([63.194.205.74] helo=mail.ar.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UWXI-000MRn-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 09:50:24 -0700
Received: from loki (IDENT:wessorh@loki [10.10.10.88])
	by mail.ar.com (8.11.2/8.11.2) with ESMTP id f78Go2r10918;
	Wed, 8 Aug 2001 09:50:02 -0700
Date: Wed, 8 Aug 2001 09:50:02 -0700 (PDT)
From: Rick H Wesson <wessorh@ar.com>
To: "D. J. Bernstein" <djb@cr.yp.to>
cc: <idn@ops.ietf.org>
Subject: Re: [idn] http://pi.cr.yp.to
In-Reply-To: <20010808151602.2805.qmail@cr.yp.to>
Message-ID: <Pine.LNX.4.30.0108080949300.1097-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


Dan,

your links didn't work for me. Linux/Netscape-4.77

-rick

On 8 Aug 2001, D. J. Bernstein wrote:

> http://pi.cr.yp.to is a collection of tests for a typical UTF-8 domain
> name. Try it with your browser and mailer, and let me know what happens.
>
> ---Dan
>




From owner-idn@ops.ietf.org  Wed Aug  8 12:58: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 MAA17163
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 12:58:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UWZH-000MYZ-00
	for idn-data@psg.com; Wed, 08 Aug 2001 09:52:27 -0700
Received: from lobo.enic.cc ([209.237.72.66] helo=mail.enic.cc)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UWZG-000MYQ-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 09:52:26 -0700
Received: from enic.cc (tailback.nic.cc [209.237.72.17])
	by mail.enic.cc (Postfix) with ESMTP
	id 5EDCF6A938; Wed,  8 Aug 2001 09:52:21 -0700 (PDT)
Message-ID: <3B716E45.44B5E710@enic.cc>
Date: Wed, 08 Aug 2001 09:52:21 -0700
From: Dan Ebert <dan@enic.cc>
Organization: eNIC Corporation
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: idn@ops.ietf.org
Subject: Re: [idn] http://pi.cr.yp.to
References: <20010808151602.2805.qmail@cr.yp.to>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


"D. J. Bernstein" wrote:
> 
> http://pi.cr.yp.to is a collection of tests for a typical UTF-8 domain
> name. Try it with your browser and mailer, and let me know what happens.
> 
> ---Dan

I tried all four links on your page. 

IE 5.5 on Win98 failed.  
Nescape 4.76 on Linux failed. 
Nescape 4.78 on Win98 went to a web page, but the address in the
location bar did not display a 'pi' in the host name.

-- 
Dan Ebert      <dan@enic.cc>       eNIC Corporation
------------------------------------------------------------
I've had a perfectly wonderful evening. But this wasn't it.
   -- Groucho Marx



From owner-idn@ops.ietf.org  Wed Aug  8 13:08: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 NAA17351
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 13:08:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UWd5-000Mj2-00
	for idn-data@psg.com; Wed, 08 Aug 2001 09:56:23 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UWd4-000Miw-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 09:56:22 -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, 8 Aug 2001 10:08:00 -0700
Message-ID: <001701c1202c$420eca80$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: =?big5?B?dHNlbmdsbUCtcLr0pKSk3y6kpKRqLnR3?= <tsenglm@cc.ncu.edu.tw>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: "Edmon" <edmon@neteka.com>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        "John C Klensin" <klensin@research.att.com>, <idn@ops.ietf.org>
References: <200108081423.f78ENK318595@nic-naa.net> <005901c12018$f999e180$fb05738c@ncu.edu.tw>
Subject: Re: [idn] opting out of SC/TC equivalence 
Date: Wed, 8 Aug 2001 13:04:58 -0400
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.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi L.M. Tseng

I agree.  Solutions need not be mutually exclusive.  Infact, the
"TC<->SC" conversion will only make the "lsTLD system" even better.

Thanks
Ben Chan



----- Original Message -----
From: "tsenglm@­pºô¤¤¤ß.¤¤¤j.tw" <tsenglm@cc.ncu.edu.tw>
To: "ben" <ben@cc-www.com>; "Eric Brunner-Williams in Portland Maine"
<brunner@nic-naa.net>
Cc: "Edmon" <edmon@neteka.com>; "Eric Brunner-Williams in Portland
Maine" <brunner@nic-naa.net>; "John C Klensin"
<klensin@research.att.com>; <idn@ops.ietf.org>
Sent: Wednesday, August 08, 2001 10:46 AM
Subject: Re: [idn] opting out of SC/TC equivalence


> do let me know when one is added to the root.
>
   TC/SC  translation  are these ponits that users need them to
reduced the
complexity of number of name registration and user can key in the name
they
more familiar.
    This ia a problem of normalization/canonicalization in nameprep,
why it
need to add to the root ?   There are many solutions , lsTLD  is just
one of
them.

L.M. Tseng







From owner-idn@ops.ietf.org  Wed Aug  8 13:20: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 NAA17640
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 13:20:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UWqM-000NZI-00
	for idn-data@psg.com; Wed, 08 Aug 2001 10:10:06 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15UWqL-000NZA-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 10:10:05 -0700
Received: (qmail 30376 invoked by uid 1001); 8 Aug 2001 16:51:37 -0000
Date: 8 Aug 2001 16:51:37 -0000
Message-ID: <20010808165137.24572.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] http://pi.cr.yp.to
References: <20010808151602.2805.qmail@cr.yp.to>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

IE 5.1 for MacOS X follows the links. However, I've heard from a couple
of sources that recent versions of IE for Windows screw up. Apparently
IE is sending a corrupted \357\200 instead of \317\200.

I'm interested in hearing an explanation from the Microsoft people here.

---Dan



From owner-idn@ops.ietf.org  Wed Aug  8 13:22: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 NAA17678
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 13:22:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UWrm-000Ncf-00
	for idn-data@psg.com; Wed, 08 Aug 2001 10:11:34 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15UWrl-000NcX-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 10:11:33 -0700
Message-ID: <007601c1202e$478d1fa0$5b8d21d9@ietf.ignite.net>
From: "Edmon" <edmon@neteka.com>
To: "Dave Crocker" <dhc@dcrocker.net>
Cc: "John C Klensin" <klensin@research.att.com>, <idn@ops.ietf.org>
References: <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net> <13749451.997252461@host217-33-136-108.ietf.ignite.net> <5.1.0.14.2.20010808143501.03f52140@dcrocker.net>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Wed, 8 Aug 2001 13:19:23 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

From: "Dave Crocker" <dhc@dcrocker.net>
> >SC/TC equivalence to be an optional technical policy matter for different
> >registries
> sorry, no.  it makes the standard useless.

why would it make the standard useless?
I think the "standard" is a standard way of processing mapping of SC=TC
(this is almost independent of DNS), but with the background of issues
pertaining DNS in mind.
it will be used by TLDs who wish to adopt it and not by those who dont... A
lot of standards have options...??...
if we force it into nameprep, then it would mean that all TLDs must adopt
it.  Also, it means that I can't have <net in TC>.domain.example go to one
IP and <net in SC>.domain.example go to another one, even if I own
domain.example.
Edmon




From owner-idn@ops.ietf.org  Wed Aug  8 13:41: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 NAA18086
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 13:41:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UX7h-000Ofw-00
	for idn-data@psg.com; Wed, 08 Aug 2001 10:28:01 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UX7g-000Ofo-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 10:28:00 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA14984;
        Wed, 8 Aug 2001 13:27:59 -0400 (EDT)
Message-Id: <200108081727.NAA14984@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] http://pi.cr.yp.to 
In-reply-to: Your message of "08 Aug 2001 16:51:37 -0000."
             <20010808165137.24572.qmail@cr.yp.to> 
Date: Wed, 08 Aug 2001 13:27:58 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> I'm interested in hearing an explanation from the Microsoft people here.

garbage in, garbage out.  what did you expect?



From owner-idn@ops.ietf.org  Wed Aug  8 13:43: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 NAA18101
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 13:43:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UXFG-000PEi-00
	for idn-data@psg.com; Wed, 08 Aug 2001 10:35:50 -0700
From: "D. J. Bernstein" <"djb-pibounce-Ï"@cr.yp.to>
To: idn@ops.ietf.org
Subject: [idn] A UTF-8 test for mail clients
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15UXFG-000PEi-00@psg.com>
Date: Wed, 08 Aug 2001 10:35:50 -0700

1. This is a MIME message with charset=utf-8. Your mail client should
display the two-byte UTF-8 sequence \317\200 in the message body as the
Greek letter pi. Here's a pi between brackets: [Ï€]


2. This message also includes a pi in the From line, right before the @:

   From: "D. J. Bernstein" <djb-pibounce-Ï€@cr.yp.to>

Of course, there's no character-set declaration for that address, but
your client should display it as UTF-8 anyway. The most common mistake
will be to treat it as 8859-1: a double-dotted I and a block.


3. Try replying to this message. Your mail client and mail server should
be able to handle the djb-pibounce-Ï€@cr.yp.to address. You will receive
a bounce from muncher.math.uic.edu showing the exact contents of your
mail as received by my mail server.

Note that there's no IDN here. The non-ASCII characters in the address
are in the box part, not the domain part. But that difference doesn't
matter for typical mail clients. This test avoids triggering DNS client
bugs, such as the BIND gethostbyname() bug.

The address will be corrupted if your message passes through Sendmail:
the second pi byte, \200, will be stripped. You will still receive a
bounce from muncher in this case.

Finally, send a message to results@pi.cr.yp.to telling me what happened.

---Dan





From owner-idn@ops.ietf.org  Wed Aug  8 13:48: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 NAA18171
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 13:48:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UXKc-000PXd-00
	for idn-data@psg.com; Wed, 08 Aug 2001 10:41:22 -0700
Received: from lobo.enic.cc ([209.237.72.66] helo=mail.enic.cc)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UXKb-000PXX-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 10:41:21 -0700
Received: from enic.cc (tailback.nic.cc [209.237.72.17])
	by mail.enic.cc (Postfix) with ESMTP
	id DE9726A909; Wed,  8 Aug 2001 10:41:20 -0700 (PDT)
Message-ID: <3B7179C0.D0C4D814@enic.cc>
Date: Wed, 08 Aug 2001 10:41:20 -0700
From: Dan Ebert <dan@enic.cc>
Organization: eNIC Corporation
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Edmon <edmon@neteka.com>
Cc: Dave Crocker <dhc@dcrocker.net>, John C Klensin <klensin@research.att.com>,
        idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
References: <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net> <13749451.997252461@host217-33-136-108.ietf.ignite.net> <5.1.0.14.2.20010808143501.03f52140@dcrocker.net> <007601c1202e$478d1fa0$5b8d21d9@ietf.ignite.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


It seems to me that it would be more confusing if TC/SC behaved
differently for different TLDs.  One of the (I think beneficial)
features of DNS is that the behavior is uniform across all TLDs (com
works like net works like org ...).  I would suggest that it may be a
better idea to use have a script on the web server look at user IP or
browser environment variable to determine what page should be displayed
(or redirect to a different server).

-- 
Dan Ebert      <dan@enic.cc>       eNIC Corporation
------------------------------------------------------------
I've had a perfectly wonderful evening. But this wasn't it.
   -- Groucho Marx

Edmon wrote:
> 
> From: "Dave Crocker" <dhc@dcrocker.net>
> > >SC/TC equivalence to be an optional technical policy matter for different
> > >registries
> > sorry, no.  it makes the standard useless.
> 
> why would it make the standard useless?
> I think the "standard" is a standard way of processing mapping of SC=TC
> (this is almost independent of DNS), but with the background of issues
> pertaining DNS in mind.
> it will be used by TLDs who wish to adopt it and not by those who dont... A
> lot of standards have options...??...
> if we force it into nameprep, then it would mean that all TLDs must adopt
> it.  Also, it means that I can't have <net in TC>.domain.example go to one
> IP and <net in SC>.domain.example go to another one, even if I own
> domain.example.
> Edmon



From owner-idn@ops.ietf.org  Wed Aug  8 13:54: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 NAA18251
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 13:54:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UXRY-000PuI-00
	for idn-data@psg.com; Wed, 08 Aug 2001 10:48:32 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UXRX-000Pty-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 10:48:31 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA15343;
        Wed, 8 Aug 2001 13:48:29 -0400 (EDT)
Message-Id: <200108081748.NAA15343@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "D. J. Bernstein" <"djb-pibounce- "@cr.yp.to>
cc: idn@ops.ietf.org
Subject: Re: [idn] A UTF-8 test for mail clients 
In-reply-to: Your message of "Wed, 08 Aug 2001 10:35:50 PDT."
             <E15UXFG-000PEi-00@psg.com> 
Date: Wed, 08 Aug 2001 13:48:29 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> 1. This is a MIME message with charset=utf-8. Your mail client should
> display the two-byte UTF-8 sequence \317\200 in the message body as the
> Greek letter pi. 

no it shouldn't, as nothing in the MIME standard requires support for UTF-8.
 
> 2. This message also includes a pi in the From line, right before the @:
> 
>    From: "D. J. Bernstein" <djb-pibounce-Ï<80>@cr.yp.to>
> 
> Of course, there's no character-set declaration for that address, but
> your client should display it as UTF-8 anyway. 

No it shouldn't, since addresses are defined to be ASCII in both RFC 822
and RFC 2822.

> 3. Try replying to this message. Your mail client and mail server should
> be able to handle the djb-pibounce-Ï<80>@cr.yp.to address. 

My mail client treats the CF and 80 as invalid characters when composing
the reply.  This is reasonable behavior given that they are illegal.

Keith



From owner-idn@ops.ietf.org  Wed Aug  8 14:03: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 OAA18405
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 14:03:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UXW7-00009n-00
	for idn-data@psg.com; Wed, 08 Aug 2001 10:53:15 -0700
Received: from c3po.netscape.com ([205.217.237.46] helo=netscape.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UXW6-00009a-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 10:53:14 -0700
Received: from gotmail-a.red.iplanet.com (gotmail-a.red.iplanet.com [192.18.73.248])
	by netscape.com (8.10.0/8.10.0) with ESMTP id f78HqFd19528;
	Wed, 8 Aug 2001 10:52:15 -0700 (PDT)
Received: from eng.sun.com (h-192-18-127-177.red.iplanet.com [192.18.127.177])
 by we-gotmail.red.iplanet.com
 (iPlanet Messaging Server 5.1 (built May  7 2001))
 with ESMTPS id <0GHR0089XGAQ4Z@we-gotmail.red.iplanet.com>; Wed,
 08 Aug 2001 10:52:03 -0700 (PDT)
Date: Wed, 08 Aug 2001 10:51:36 -0700
From: "A. Vine" <avine@eng.sun.com>
Subject: Re: [idn] A UTF-8 test for mail clients
To: "D. J. Bernstein" <djb-pibounce-*@cr.yp.to>
Cc: idn@ops.ietf.org
Message-id: <3B717C28.C1CD7F15@eng.sun.com>
MIME-version: 1.0
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 8BIT
X-Accept-Language: fr,en,de,it,ja,ru
References: <E15UXFG-000PEi-00@psg.com>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8BIT



"D. J. Bernstein" wrote:
> 
> 1. This is a MIME message with charset=utf-8. Your mail client should
> display the two-byte UTF-8 sequence \317\200 in the message body as the
> Greek letter pi. Here's a pi between brackets: [Ï€]
> 
> 2. This message also includes a pi in the From line, right before the @:
> 
>    From: "D. J. Bernstein" <djb-pibounce-Ï€@cr.yp.to>
> 
> Of course, there's no character-set declaration for that address, but
> your client should display it as UTF-8 anyway. The most common mistake
> will be to treat it as 8859-1: a double-dotted I and a block.

Or Windows CP1252 including euro, which causes a euro symbol to be displayed
next to the capital I with diaeresis.

> 
> 3. Try replying to this message. Your mail client and mail server should
> be able to handle the djb-pibounce-Ï€@cr.yp.to address. You will receive
> a bounce from muncher.math.uic.edu showing the exact contents of your
> mail as received by my mail server.
> 
> Note that there's no IDN here. The non-ASCII characters in the address
> are in the box part, not the domain part. But that difference doesn't
> matter for typical mail clients. This test avoids triggering DNS client
> bugs, such as the BIND gethostbyname() bug.
> 
> The address will be corrupted if your message passes through Sendmail:
> the second pi byte, \200, will be stripped. You will still receive a
> bounce from muncher in this case.
> 
> Finally, send a message to results@pi.cr.yp.to telling me what happened.
> 
> ---Dan



From owner-idn@ops.ietf.org  Wed Aug  8 14:47: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 OAA19111
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 14:47:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UYFT-0002Gm-00
	for idn-data@psg.com; Wed, 08 Aug 2001 11:40:07 -0700
Received: from koobera.math.uic.edu ([131.193.178.181] helo=muncher.math.uic.edu)
	by psg.com with smtp (Exim 3.31 #1)
	id 15UYFS-0002Gc-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 11:40:06 -0700
Received: (qmail 12297 invoked by uid 1001); 8 Aug 2001 18:40:22 -0000
Date: 8 Aug 2001 18:40:22 -0000
Message-ID: <20010808184022.27107.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
Reply-To: "D. J. Bernstein" <"djb-pibounce-Ï"@cr.yp.to>
To: idn@ops.ietf.org
Subject: [idn] A UTF-8 test for mail clients
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Sender: owner-idn@ops.ietf.org
Precedence: bulk

[The first version of this message was corrupted by the mailing-list
manager. The From line wasn't an approved submitter, so the message was
put on hold pending approval; the approval mechanism generated a new
header, omitting the relevant MIME header fields.]


1. This is a MIME message with charset=utf-8. Your mail client should
display the two-byte UTF-8 sequence \317\200 in the message body as the
Greek letter pi. Here's a pi between brackets: [Ï€]


2. This message also includes a pi in the Reply-To line, right before
the @:

   Reply-To: "D. J. Bernstein" <djb-pibounce-Ï€@cr.yp.to>

Of course, there's no character-set declaration for that address, but
your client should display it as UTF-8 anyway. The most common mistake
will be to treat it as 8859-1: a double-dotted I and a block.


3. Try replying to this message. Your mail client and mail server should
be able to handle the djb-pibounce-Ï€@cr.yp.to address. You will receive
a bounce from muncher.math.uic.edu showing the exact contents of your
mail as received by my mail server.

Note that there's no IDN here. The non-ASCII characters in the address
are in the box part, not the domain part. But that difference doesn't
matter for typical mail clients. This test avoids triggering DNS client
bugs, such as the BIND gethostbyname() bug.

The address will be corrupted if your message passes through Sendmail:
the second pi byte, \200, will be stripped. You will still receive a
bounce from muncher in this case.

Finally, send a message to results@pi.cr.yp.to telling me what happened.

---Dan



From owner-idn@ops.ietf.org  Wed Aug  8 16:43: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 QAA21143
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 16:43:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UZwy-0008Eu-00
	for idn-data@psg.com; Wed, 08 Aug 2001 13:29:08 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UZww-0008Ed-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 13:29:06 -0700
Received: from zetnet.co.uk (man-s300.dialup.zetnet.co.uk [194.247.45.171])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f78KSsx23600;
	Wed, 8 Aug 2001 21:28:55 +0100
Message-ID: <3B711FBC.AAD1F378@zetnet.co.uk>
Date: Wed, 08 Aug 2001 12:17:17 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: Edmon <edmon@neteka.com>, idn@ops.ietf.org
Subject: [idn] SC/TC equivalence
References: <200107301509.f6UF91N23867@nic-naa.net> <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.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-----

Edmon wrote:
> From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
> > What is the key value for users "opting out" of SC/TC equivalences?
> 
> There are two main scenarios that I could think of that I would like to see
> SC/TC opted out.
> Say I wanted to have different online identities in the PRC, HongKong and
> Taiwan with two Chinese charcters.  And I want to use:
> <SC><SC> in PRC
> <SC><TC> in HK and
> <TC><TC> in Taiwan

Unless I'm missing something, SC/TC equivalence doesn't affect the protocol;
it's purely a local issue for administrators of zones that include names
with Chinese characters. They could configure the authoritative servers for
those zones to use any of the following approaches:

1. have zone entries for each combination.
2. have zone entries only for folded names, and do folding in the server.
3. have the server try to match the unfolded name first, and if not found,
   try to match the folded name.

Intermediate servers will cache the variants that are actually used (which
is probably only a small subset of the possible variants).

So the WG doesn't need to decide this, apart from pointing out the options.

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

iQEVAwUBO3EfjDkCAxeYt5gVAQEiwwf/ZD4a7sFKXRaePXRImGOlZM8NRu32CCty
X8D2uEtyo1ZATDjUXK71Um92wiOLHOp6m2DwZbXzT8YT6mt/8pnDdfQs5iug218D
Byi137qwBXDrwPKv1mKqAXsC9dSHBGZly1w7Mmwg+ugJ7vuv0pqwmSHIy+UoCTnP
vU010nVfqj5c/kt7cH6Gkt2Tan5uoii1WpZRRj0tXYezuqsTKC/f5D4GFWtvdzAN
iTyMlI4lM3znZOCI1vwfxOPgBU4ONHugvrrjv72pTrDbt3qrivpgndvcFI4Mo4El
bsHGqumZhRq5qMC8vSF9tJDKtJJMOoTY831yQJprdyASVKNvEKItkw==
=u31z
-----END PGP SIGNATURE-----




From owner-idn@ops.ietf.org  Wed Aug  8 16:51: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 QAA21241
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 16:51:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ua7V-0008Xu-00
	for idn-data@psg.com; Wed, 08 Aug 2001 13:40:01 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ua7U-0008Xj-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 13:40:00 -0700
Received: from zetnet.co.uk (man-s300.dialup.zetnet.co.uk [194.247.45.171])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f78Kdrx25640;
	Wed, 8 Aug 2001 21:39:53 +0100
Message-ID: <3B71A3DE.8DF843B4@zetnet.co.uk>
Date: Wed, 08 Aug 2001 21:41:02 +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: ben <ben@cc-www.com>, idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
References: <200107301509.f6UF91N23867@nic-naa.net> <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net> <001601c11fed$a80b2f20$fb05738c@ncu.edu.tw> <005001c1200d$01f85480$d43f7018@mtag1.on.home.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-----

ben wrote:
> Although the current ccTLDs and gTLDs will work for IDNs, they cannot
> totally satisfy the needs of the users of CDNs.  Another type of TLD
> must be created and I will tentatively call it lsTLDs (Language Script
> TLDs).  lsTLDs are in native language script... not English- thus
> bringing out the issue of <IDN>.<IDN> that ICANN has already expressed
> their interest in.

I don't see why there would be any technical problem associated with
having non-ASCII TLDs. They're just like any other label, except that
the first octet must not be US-ASCII '0'-'9' (to allow a domain name to
be distinguished from an IPv4 address).

(Obviously there are plenty of political problems associated with adding
any TLD, but that's ICANN's problem.)

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

iQEVAwUBO3GjpzkCAxeYt5gVAQFHKwgAgVYwRwrUHqle97iXSQGajmNeL5CJLjub
OvHESgdLKTdT9HUxXx9Z71Iq5lzY+/5CZ5xQDV9UFKToKD79jzTh2YCVyr1cD67B
Ng8G3nq2mmsDWVWy4atwhgdhmSEf+XkDydsYvkOCOOy/u4o/LDMfS52vYtCyso6F
ZfvX/cy++kzBKnZ8zNDo+pP4hdzjJYZQl4bDG2xaZaZnakYjFVXRW8OFCNBdl0qL
1/zrfi0RTe5aSnxMCcqaxMxvI4Jp8hai6O+LnAaPrSTdeX3vTqFMRkau7vybCn5Q
rpMTVNjGP/xc4o6JESwOtUl8o9MyHyACwvpjFyL0EA0IbetMf9cAoA==
=OLJz
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Wed Aug  8 17:43: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 RAA22109
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 17:43:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UavP-000Aie-00
	for idn-data@psg.com; Wed, 08 Aug 2001 14:31:35 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UavO-000AiX-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 14:31:34 -0700
Received: from zetnet.co.uk (man-s300.dialup.zetnet.co.uk [194.247.45.171])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f78LVQx02467;
	Wed, 8 Aug 2001 22:31:27 +0100
Message-ID: <3B71AFF6.9B2ED0C4@zetnet.co.uk>
Date: Wed, 08 Aug 2001 22:32:38 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: "D. J. Bernstein" <djb@cr.yp.to>, idn@ops.ietf.org
Subject: Re: [idn] http://pi.cr.yp.to
References: <20010808151602.2805.qmail@cr.yp.to>
Content-Type: text/plain; charset=UTF-8
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA22109

-----BEGIN PGP SIGNED MESSAGE-----

"D. J. Bernstein" wrote:
> http://pi.cr.yp.to is a collection of tests for a typical UTF-8 domain
> name. Try it with your browser and mailer, and let me know what happens.

Netscape 4.7 on Windows resolves Ï€.cr.yp.to correctly (but with the URI
in the location bar displayed as if it was ISO-Latin-1, on my system).

Mozilla build 2001062815 on Windows fails (displays a blank page, with
http://%CF%80.cr.yp.to in the location bar).

MSIE 5.50.4134.0600 on Windows fails with "Cannot find server or DNS Error".

The Netscape mail client doesn't allow typing or pasting non-ISO-Latin-1
into a To: field without adding quotes around the local part, and this
causes an error from the server when sending the mail.

The Mozilla mail client fails sending to bounce@Ï€.cr.yp.to because it tries
to convert the address to "=?UTF-8?B?...=".

This message is text/plain; charset=utf-8 - try this link:

  http://Ï€.cr.yp.to/

(works in Netscape 4.7 on Windows).

However, to send this mail from NS4.7 I had to cheat slightly: set the
character set in the View menu to UTF-8, but ignore the fact that characters
are displayed in the text composition window as ISO-Latin-1. Sending UTF-8
mail works better in Mozilla.

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

iQEVAwUBO3GvsDkCAxeYt5gVAQE8bggAjcIr7GF2o9kRyQ7gNbH4SS3lg4tn0C1A
IMObJeAabahBG/3cTFB2P7iv8+wIHoq+F2FgVOGwuLRMbs4Mh0PmwK29gWqJMNdz
ZNNbhI/bdHHAqaY5kYtO+4QrgqOT+0InnMOGEMiqKBezeWLHXwQmLhNvr03TVDMe
WUjBFsRRni5PFPIGChMVE/hWm3Qq8tVV+Eb8VELC5T7kjuPqFXXK/QWZy+uzokWB
FColNw2nHNGKb9nwUiBPmrlGwchSkAJhOVGMWuums9exp6Iw4xh962JGy56TPLaf
wvUVCjOZ0+XqEuKEu/fcOu49cfLp+wLRJuvOfjGZHTogpTYi5dXKkg==
=zz4m
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Wed Aug  8 17: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 RAA22123
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 17:44:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Uami-000AIE-00
	for idn-data@psg.com; Wed, 08 Aug 2001 14:22:36 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Uamh-000AI3-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 14:22:36 -0700
Received: from amc by nicemice.net with local (Exim 3.31 #1 (Debian))
	id 15Uamh-0003z2-00
	for <idn@ops.ietf.org>; Wed, 08 Aug 2001 14:22:35 -0700
Date: Wed, 8 Aug 2001 21:22:35 +0000
From: "Adam M. Costello" <amc@cs.berkeley.edu>
To: idn@ops.ietf.org
Subject: Re: [idn] SC/TC equivalence
Message-ID: <20010808212235.E14888@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B711FBC.AAD1F378@zetnet.co.uk>
User-Agent: Mutt/1.3.18i
Sender: owner-idn@ops.ietf.org
Precedence: bulk

David Hopwood <david.hopwood@zetnet.co.uk> wrote:

> Unless I'm missing something, SC/TC equivalence doesn't affect the
> protocol; it's purely a local issue for administrators of zones that
> include names with Chinese characters.
>
> So the WG doesn't need to decide this, apart from pointing out the
> options.

Thank you!  One thing that should be considered by anyone contemplating
server-side equivalence rules is that clients will not know that the
names are equivalent.  For web browsers, this will affect visited link
coloring, page caching, cookie permissions, etc.  Similar pitfalls will
exist in other applications.  Zone administrators willing to tolerate
such limitations are free to do server-side equivalence matching to
their heart's content.  It would be ludicrous for this working group to
try to prohibit this practice, because it's equivalent to populating the
zone with identical data for all the matching names, which is obviously
permitted.

AMC



From owner-idn@ops.ietf.org  Wed Aug  8 17: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 RAA22191
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 17:50:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ub3M-000B5R-00
	for idn-data@psg.com; Wed, 08 Aug 2001 14:39:48 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ub3L-000B5L-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 14:39:47 -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, 8 Aug 2001 14:51:25 -0700
Message-ID: <001901c12053$da3eaec0$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
References: <200107301509.f6UF91N23867@nic-naa.net> <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net> <001601c11fed$a80b2f20$fb05738c@ncu.edu.tw> <005001c1200d$01f85480$d43f7018@mtag1.on.home.com> <3B71A3DE.8DF843B4@zetnet.co.uk>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Wed, 8 Aug 2001 17:48:24 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi David,

The ICANN Board's Internal Working Group asked:  "Presumably there
will be a demand for top level IDNs, i.e., [IDN].[IDN]. What role
should ICANN play with respect to the selection of these top level
names and their registries? What should be the role of the country
code registry of the country where a particular script is a native
script? And what if a particular script is a native script in more
than one country?"

I know ICANN is interested and I will show ICANN why in my 2 years of
gathering data from everyday people from all over the world that there
is indeed a need for lsTLDs (Language Script TLDs).

Thanks
Ben Chan

----- Original Message -----
From: "David Hopwood" <david.hopwood@zetnet.co.uk>
To: "ben" <ben@cc-www.com>; <idn@ops.ietf.org>
Sent: Wednesday, August 08, 2001 4:41 PM
Subject: Re: [idn] opting out of SC/TC equivalence


-----BEGIN PGP SIGNED MESSAGE-----

ben wrote:
> Although the current ccTLDs and gTLDs will work for IDNs, they
cannot
> totally satisfy the needs of the users of CDNs.  Another type of TLD
> must be created and I will tentatively call it lsTLDs (Language
Script
> TLDs).  lsTLDs are in native language script... not English- thus
> bringing out the issue of <IDN>.<IDN> that ICANN has already
expressed
> their interest in.

I don't see why there would be any technical problem associated with
having non-ASCII TLDs. They're just like any other label, except that
the first octet must not be US-ASCII '0'-'9' (to allow a domain name
to
be distinguished from an IPv4 address).

(Obviously there are plenty of political problems associated with
adding
any TLD, but that's ICANN's problem.)

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

iQEVAwUBO3GjpzkCAxeYt5gVAQFHKwgAgVYwRwrUHqle97iXSQGajmNeL5CJLjub
OvHESgdLKTdT9HUxXx9Z71Iq5lzY+/5CZ5xQDV9UFKToKD79jzTh2YCVyr1cD67B
Ng8G3nq2mmsDWVWy4atwhgdhmSEf+XkDydsYvkOCOOy/u4o/LDMfS52vYtCyso6F
ZfvX/cy++kzBKnZ8zNDo+pP4hdzjJYZQl4bDG2xaZaZnakYjFVXRW8OFCNBdl0qL
1/zrfi0RTe5aSnxMCcqaxMxvI4Jp8hai6O+LnAaPrSTdeX3vTqFMRkau7vybCn5Q
rpMTVNjGP/xc4o6JESwOtUl8o9MyHyACwvpjFyL0EA0IbetMf9cAoA==
=OLJz
-----END PGP SIGNATURE-----






From owner-idn@ops.ietf.org  Wed Aug  8 21:40: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 VAA25988
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 21:40:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UeQA-000LYP-00
	for idn-data@psg.com; Wed, 08 Aug 2001 18:15:34 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UeQ9-000LYG-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 18:15:33 -0700
Received: from zetnet.co.uk (man-s307.dialup.zetnet.co.uk [194.247.45.178])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f791FQx00458;
	Thu, 9 Aug 2001 02:15:26 +0100
Message-ID: <3B71D034.63F361B6@zetnet.co.uk>
Date: Thu, 09 Aug 2001 00:50:12 +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: ben <ben@cc-www.com>, idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
References: <200107301509.f6UF91N23867@nic-naa.net> <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net> <001601c11fed$a80b2f20$fb05738c@ncu.edu.tw> <005001c1200d$01f85480$d43f7018@mtag1.on.home.com> <3B71A3DE.8DF843B4@zetnet.co.uk> <001901c12053$da3eaec0$d43f7018@mtag1.on.home.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-----

ben wrote:
> The ICANN Board's Internal Working Group asked:  "Presumably there
> will be a demand for top level IDNs, i.e., [IDN].[IDN]. What role
> should ICANN play with respect to the selection of these top level
> names and their registries? What should be the role of the country
> code registry of the country where a particular script is a native
> script? And what if a particular script is a native script in more
> than one country?"

These are policy issues, not technical issues, so it isn't the role of
the IDN WG to take any position on them. (That doesn't prevent you or
anyone else making an individual comment on this subject to ICANN, of
course. I suggest reading RFC 3071 first.)

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

iQEVAwUBO3HP1zkCAxeYt5gVAQE0OAf/XRUdkKvEiOeEaUjC+UutG3wejoD74XeW
+4XCW2Ixy8R31M7roUby21FpUvpgaPNAWIaCQf4opE0rV9STz0+6eUVT6IhQ7FEL
zfCO+z1yBD2nwz9fySF6vrqjrzLI0qRKiM7lBOBFbSvX6zhB2Gl6hXIunEJeKcmi
xB55Umm5RPurAPgRW/sfum13Kw1QP96qKeOwTZbZTqVhDoGv3Zm6e3oCZBWa8poI
7SV8brg+Iprpn+8sgAPFEsTbdE2zUsegMTgF2DIaU0sN1a19J4VdEy7QaRPAKa0j
biz24RziNj98SJ8KUjOohcglb0dT9GyxoKHH9KRFMZM0g5utoSF0pg==
=Y4L+
-----END PGP SIGNATURE-----





From owner-idn@ops.ietf.org  Wed Aug  8 21:46: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 VAA26049
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 21:46:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UeQO-000LaE-00
	for idn-data@psg.com; Wed, 08 Aug 2001 18:15:48 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UeQM-000La2-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 18:15:46 -0700
Received: from zetnet.co.uk (man-s307.dialup.zetnet.co.uk [194.247.45.178])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f791FWx00471;
	Thu, 9 Aug 2001 02:15:33 +0100
Message-ID: <3B71E3CD.CCC80166@zetnet.co.uk>
Date: Thu, 09 Aug 2001 02:13:49 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: Dave Crocker <dcrocker@brandenburg.com>, idn@ops.ietf.org
Subject: [idn] Transparent vs. ACE representations (was We are quibbling about WHAT?)
References: <5.1.0.14.2.20010729172557.0302f008@brandenburg.com> <5.1.0.14.2.20010803135104.032186f0@brandenburg.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

Dave Crocker wrote:
> Content-Type: text/plain; charset=us-ascii; format=flowed
> ...
>
> At 11:55 AM 7/30/2001, David Hopwood wrote:
> >The debate between ACE and UTF-8 has nothing to do with encoding
> >efficiency. The benefit of UTF-8 is in having DNS names in the same
> >encoding as the surrounding text, rather than having to treat them as a
> >special case.
> 
> "surrounding text"???  you mean like this message?

Yes, like that message: the domain name "www.brandenburg.com" and the
email address "dcrocker@brandenburg.com" were in the same encoding as the
surrounding text. That's why they looked right when I viewed the message,
rather than looking like gibberish.

But, you may say, that encoding wasn't UTF-8. Doesn't matter. Suppose for
the sake of argument that the message had contained characters outside the
US-ASCII repertoire (in a domain name or elsewhere). In that case, your
mail client would have automatically chosen an encoding that is capable
of representing those characters. That still might not be UTF-8, but the
important point is that a text message or file can always be losslessly
transcoded into any UTF, including UTF-8 [*]. So, any domain names in
the message (regardless of whether they are pasted, typed, come from a
.signature file, or whatever), will both "look right", and will be
losslessly convertable to the format needed for a lookup. They can also
be pasted into other applications, and will still look right - even in
applications that don't and shouldn't need to know anything about IDNs.

[*] The transcoder may or may not be NFC-normalizing; that doesn't matter
    because nameprep(NFC(X)) = NFC(nameprep(X)) = nameprep(X) for all X.


Although most of the discussion on this list has been categorising the
possible architectures as "UTF-8-only", "UTF-8 + ACE", and "ACE-only",
this misses the point slightly, and I should have been clearer about
that in my previous message. Call a domain name representation within
some surrounding text (or other protocol elements) "transparent", if the
representation is of a character string such that each character in the
string stands for the same character in the domain name. I.e.:

                charset
  octet string  <----->  character string     =     domain name

as opposed to:

                charset                      ACE
  octet string  <----->  character string  <----->  domain name

A more fundamental categorisation of IDN architectures is then
"transparent-only" vs. "transparent + ACE" vs. "ACE-only".


The representation of LDH domain names has always been transparent: even
if you transcode a message containing domain names into, say, EBCDIC,
each character still stands for itself in the EBCDIC encoding.
Similarly, in proposals that support transparent non-ASCII domain
names, there will be no difficulty with transcoding a message into
UTF-16, UTF-EBCDIC, or anything else that is capable of representing
all the characters in that message.

[I use EBCDIC and UTF-EBCDIC as examples, to make the point that it's not
the fact that the encoding is a superset of US-ASCII that is relied on;
only that it is capable of representing all the characters in the name
(up to Unicode compatibility equivalence), and all the characters in the
surrounding message text. Of course, using an encoding that is a superset
of US-ASCII is very convenient in practice, and a UTF will always be able
to represent the necessary characters - hence the attractiveness of UTF-8.)


The thesis behind the ACE-only proposals seems to be that most existing
protocols, formats, and implementations assume that domain names only
use US-ASCII characters, and so using a non-ASCII representation will
break them. In the vast majority of cases, that simply isn't true: most
things don't assume that the representation is ASCII, but they *do* very
often assume that it is transparent. The main flaw in the argument that
ACE is just another encoding, is that it ignores how important
transparency is as a simplification.

> sorry, no.  DNS strings occur in many situations.  Most do not, today,
> use UTF-8,

I've been searching through all RFCs to try to produce a list of all
the IETF-standardized protocols where domain names are encoded (including
email addresses and URIs/URLs), and actually quite a large proportion of
them use UTF-8 already for the rest of the protocol. There are very, very
few protocols that require use of a different 8-bit character set.
Overall, I don't see anything that would interfere with straightforwardly
adopting UTF-8 as the preferred encoding for domain names, with ACE just
used for a handful of problematic cases such as SMTP.

In the case of protocols where messages are tagged with their charsets,
receiving software might have to transcode a message from whatever it is
tagged as into a UTF before further processing. However, that is what a
Unicode-based program would normally do anyway, and after that, the entire
message (or file, or whatever) can be treated uniformly. ACE domain names,
OTOH, will always have to be treated as a special case. So transparent
solutions have an advantage over ACE-only solutions even when the encoding
is not initially UTF-8.

If anything, maximum name lengths are a bigger compatibility problem than
encodings, and in that respect there is little difference between UTF-8
and the proposed ACEs (some languages win, some lose, but either UTF-8 or
AMC-ACE-Z would be adequate in practice).

> As to predictions of the future, well, they are always wrong.

That's obvious nonsense. It is a perfectly safe prediction that the
default encoding (often the only encoding) used in almost all Internet
protocols in the near future will be UTF-8. In a sense there is nothing
to predict; the decision has already been made in RFC 2277 / BCP 18, and
the process of making the necessary modifications to existing standards
is already well underway.

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

iQEVAwUBO3HjuTkCAxeYt5gVAQGH5Af/U8UodcH1fleoT/ug7jbS8S6aZixQrEEa
oAAPjxUMGyxthjqwcbPVluWLuyWGiJ79q9JFIx1ub6VJ8QvEa1lAXU/Z1KGIOTmD
9w2TOZD6qt+NYfFS5PNW/GsgjEcOMKOaSKPGHP2q21V8fw5CuJGx5PzPWDKpANUd
GRHLxeclUXabQfIgyQL6X9WSj9QyRIClb3bmZEqhRazhwxRTa6hTPZVbRFCW0X02
LdmawzjXwIiPOf/hbW+TNRjn9FyUf7R5B5M/56rBAIYJmhP8Er6cQJ048fkXsrhH
3RdkusyVIjK4kZXKC89rIGsLeXyZzXPv7DrvBovz8EyD48IwJW+RbQ==
=Sp8e
-----END PGP SIGNATURE-----




From owner-idn@ops.ietf.org  Wed Aug  8 22: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 WAA27326
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 22:40:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UfG5-000Nyc-00
	for idn-data@psg.com; Wed, 08 Aug 2001 19:09:13 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UfG4-000NyW-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 19:09:12 -0700
Received: from amc by nicemice.net with local (Exim 3.31 #1 (Debian))
	id 15UfG4-0004GQ-00
	for <idn@ops.ietf.org>; Wed, 08 Aug 2001 19:09:12 -0700
Date: Thu, 9 Aug 2001 02:09:12 +0000
From: "Adam M. Costello" <amc@cs.berkeley.edu>
To: idn@ops.ietf.org
Subject: Re: [idn] Transparent vs. ACE representations (was We are quibbling about WHAT?)
Message-ID: <20010809020911.B15655@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3B71E3CD.CCC80166@zetnet.co.uk>
User-Agent: Mutt/1.3.18i
Sender: owner-idn@ops.ietf.org
Precedence: bulk

David Hopwood <david.hopwood@zetnet.co.uk> wrote:

> The thesis behind the ACE-only proposals

What ACE-only proposals?  I think the strongest ACE supporters
merely say that you have to obey existing standards.  If a protocol
specification (like the URI spec, or the SMTP spec, or the TLS spec)
says that the domain name in a particular slot may contain only certain
characters, then ACE is the only way you can use IDNs while still
obeying the standard.

But new standards can of course specify looser rules.  I don't think
anyone here wants to prohibit new protocols/interfaces from using UTF-8
(or their favorite charset).

> most things don't assume that the representation is ASCII

As Dan Bernstein's recent tests have shown, lots of software stops
working when domain names contain bytes greater than 127, including
browsers, resolvers, mail user agents, and mail transfer agents.

And one thing's for sure:  No deployed software today knows how to
properly compare two IDNs (which requires nameprep).

Even if you're right about most things not breaking on 8-bit domain
names, things are connected to each other.  Domain names get passed
around.  If you feed an 8-bit domain name to an IDN-unaware agent, it
might not break that agent, but it's probably going to break something
else a little later.  Therefore 8-bit domain names ought to be passed
around only among IDN-aware agents/protocols, and converted to ACE when
interfacing with IDN-unaware agents/protocols.

AMC



From owner-idn@ops.ietf.org  Wed Aug  8 23:12: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 XAA27604
	for <idn-archive@lists.ietf.org>; Wed, 8 Aug 2001 23:12:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Ug2t-0000Z9-00
	for idn-data@psg.com; Wed, 08 Aug 2001 19:59:39 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Ug2s-0000Yz-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 19:59:38 -0700
Received: from amc by nicemice.net with local (Exim 3.31 #1 (Debian))
	id 15Ug2s-0004Jo-00
	for <idn@ops.ietf.org>; Wed, 08 Aug 2001 19:59:38 -0700
Date: Thu, 9 Aug 2001 02:59:38 +0000
From: "Adam M. Costello" <amc@cs.berkeley.edu>
To: idn working group <idn@ops.ietf.org>
Subject: [idn] rederivation of an IDN architecture
Message-ID: <20010809025938.C15655@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.18i
Sender: owner-idn@ops.ietf.org
Precedence: bulk

idn-arch-deriv 0.0.0 (2001-Aug-09-Thu)
Adam M. Costello <amc@cs.berkeley.edu>

This is a derivation of an Internationalized Domain Name architecture
that is extremely similar (if not perfectly identical) to IDNA.  My
purpose in composing this derivation is to expose dependencies between
requirements, goals, and assumptions, in order to facilitate fruitful
discussions.  For example, if a certain requirement is necessary to
achieve a certain goal, it is pointless to attack the requirement when
arguing with someone who believes in the goal; ones needs to argue
against the goal itself, and perhaps against the assumptions underlying
the goal.

The bulk of this derivation is definitions.  Readers may wish to skip
the definitions the first time through, and refer back to them when
necessary.

Since there is a preexisting standard for domain name syntax, it is
useful to have some definitions for talking about that syntax:

    basic character:  Any of the 128 characters in the ASCII repertoire
    (not to be confused with the integers or octets mapped to those
    characters in the ASCII coded character set).

    basic string:  A sequence of basic characters.

    tolower():  A function from a basic string to a basic string.  It
    converts A-Z to a-z respectively, and leaves the other characters
    unchanged.  [Observation: tolower() is idempotent, that is, for any
    basic string B, tolower(B) = tolower(tolower(B)).]

    equivalent basic strings:  Basic strings for which tolower()
    gives identical results.  [Observation:  Because tolower() is
    idempotent, a basic string and its tolower() image are equivalent
    basic strings.]

    basic label:  A basic string containing from 1 to 63 characters.
    [This is the preexisting standard for textual domain labels.]

    host restrictions (applicable to any sequence of characters):
    Contains no basic characters other than the letters, digits, and
    hyphen-minus; and neither begins nor ends with hyphen-minus.

    basic host label:  A basic label that satisfies the host
    restrictions.  [This is the preexisting standard for host labels.]

    equivalent basic labels:  Basic labels that are equivalent basic
    strings.  [This is the preexisting standard for equivalence of
    textual domain labels.]

    basic domain name:  A sequence of basic labels (typically separated
    by full-stop characters).  [This is the preexisting standard for
    textual domain names.]

    basic host name:  A basic domain name for which every label is a
    basic host label.  [This is the preexisting standard for internet
    host names.]

    equivalent basic domain names:  Basic domain names that have the
    same number of labels and for which corresponding labels are
    equivalent basic labels.  [This is the preexisting standard for
    equivalence of textual domain names.]

    domain name slot:  A field or sub-field in a protocol message, or a
    function argument in an interface, etc, explicitly designated for
    carrying a domain name.

Fact 1:  Many existing protocols, interfaces, etc. have domain name
slots and require the names in those slots to conform to the syntax and
equivalence rules for basic host names (or at least basic domain names).

Fact 2:  Even when existing protocols, interfaces, etc. do not
require domain names to conform to the preexisting syntax, different
implementations of the same protocol/interface will sometimes behave
differently if presented with domain names that do not conform, because
there has been no preexisting standard for how such domain names should
be handled.  (For example, some implementations will reject the names,
some will alter the names, and some will pass them through unchanged.
There is similar uncertainty when names are compared.)

Fact 3:  Many people would like to use domain names containing
additional characters not allowed by the preexisting syntax.

Conjecture 1:  Many people will be reluctant to create domains using
additional characters if those domains would be inaccessible to
preexisting protocols, interfaces, software, etc.

Goal 1 (motivated by facts 1-3 and conjecture 1):  Allow domain names to
contain additional characters, while still allowing all domains to be
referred to by all preexisting protocols, interfaces, software, etc.

Requirement 1 (follows from goal 1):  Part of the preexisting namespace
must be used to represent names containing additional characters,
which requires altering the semantics of that part of the preexisting
namespace.

Goal 2:  The part of the preexisting namespace that is repurposed should
be a part that is not currently in use, or at least is used to an
extremely small extent, so that disruption is minimized.

Goal 3:  The part of the preexisting namespace that is repurposed
should be easily identifiable and easily avoidable (both by humans and
machines).

Fact 4:  Many protocols and standards split domain names into labels,
re-join them, count the number of labels, and test whether two domain
names agree on individual labels.

Goal 4 (motivated by fact 4):  The way that preexisting names are used
to represent names containing additional characters should not disrupt
operations that treat labels individually.

Requirement 2 (follows from goals 2-4):  The representation of
previously disallowed names by previously allowed names must be done
independently per label, and labels using this representation must have
a well-known prefix or suffix that was almost never in use.

Fact 5:  Internet protocols usually support US-ASCII, and future
internet protocols are encouraged to support UTF-8.

Fact 6:  UTF-8 is an extension of US-ASCII, that is, characters in the
ASCII repertoire are represented by the same bytes in UTF-8 as in ASCII.

Goal 5 (motivated by facts 5 and 6):  Given a protocol that uses ASCII
to encode domain names, it should be easy to design an updated version
of the protocol that uses UTF-8 to encode domain names.

Requirement 3 (follows from goal 5):  The preexisting restrictions on
what ASCII characters are allowed in host names, and in what positions,
must be retained in the expanded namespace.

Requirements 1, 2, and 3 motivate the following definitions for the
expanded namespace:

    international character:  A character in the Unicode repertoire (not
    to be confused with the integers or byte sequences used to represent
    those characters in the various encodings defined by the Unicode
    standard).

    international string:  A sequence of international characters.
    [Observation:  Every basic string is an international string.]

    canon():  A function (defined elsewhere) from an international
    string to an international string.  It is an extension of tolower(),
    that is, for any basic string B, canon(B) = tolower(B).  Like
    tolower(), canon() is defined everywhere and is idempotent (canon(S)
    = canon(canon(S)) for any international string S), but unlike
    tolower(), canon(S) and S might have different lengths.

    equivalent international strings:  International strings for which
    canon() gives identical results.  [This is consistent with the
    definition of equivalence of basic strings, because canon() behaves
    like tolower() for basic strings.  Observation:  Because canon()
    is idempotent, an international string and its canon() image are
    equivalent international strings.]

    degenerate international string:  An international string that
    is equivalent to a basic string.  [The definitions of equivalent
    international strings and canon() imply that an international string
    S is degenerate iff canon(S) is a basic string.]

    ACE prefix:  A particular sequence of basic characters (defined
    elsewhere).  [A suffix would work as well as a prefix.  The phrase
    "begins with the ACE prefix" should be understood to mean "ends with
    the ACE suffix" if a suffix is used instead.]

    compat():  A function (defined elsewhere) from an international
    string to a basic label.  For some international strings S,
    compat(S) does not exist, either for policy reasons, or because
    of the length restriction on basic labels.  The compat() function
    satisfies the following properties:

        Stability:  For any basic string B, compat(B) = B.

        Preservation of equivalence:  For any equivalent international
        strings S1 and S2, if compat(S1) exists, then compat(S2) exists,
        and compat(S1) and compat(S2) are equivalent basic labels.

        Preservation of non-equivalence:  For any nondegenerate
        international strings S1 and S2 for which compat(S1) and
        compat(S2) exist, if S1 and S2 are not equivalent international
        strings, then compat(S1) and compat(S2) are not equivalent basic
        labels.

        Preservation of host restrictions:  For any international string
        S, if S satisfies the host restrictions and compat(S) exists,
        then compat(S) satisfies the host restrictions.

        Tagging:  For any nondegenerate international string S, if
        compat(S) exists then it begins with the ACE prefix.

        Non-recursion of tagging:  For any nondegenerate international
        string S that begins with the ACE prefix, compat(S) does not
        exist.

    [Observation:  The preservation of equivalence and non-equivalence
    implies that the definition of compat() will include the definition
    of canon().]

    international label:  An international string S for which compat(S)
    exists.  [Observation:  Every basic label is an international
    label.]

    equivalent international labels:  International labels for which
    compat() yields equivalent basic labels.  [This is consistent with
    the definition of equivalent basic labels, because compat(B) = B for
    any basic label B.  Observation:  For any international labels L1
    and L2 for which canon(L1) and canon(L2) do not begin with the ACE
    prefix, L1 and L2 are equivalent international labels iff they are
    equivalent international strings.]

    international domain name:  A sequence of international labels
    (typically separated by full-stop characters).  [Observation:  Every
    basic domain name is an international domain name.]

    equivalent international domain names:  International domain names
    that have the same number of labels and for which corresponding
    labels are equivalent international labels.  [This is consistent
    with the definition of equivalent basic domain names, because
    equivalence of international labels is consistent with equivalence
    of basic labels.  Observation:  For any international domain name
    there exists a basic domain name equivalent to it, which can be
    obtained by applying compat() to each label.]

    decompat():  A function from basic labels to international labels.
    For any basic label B, if there exists a nondegenerate international
    string S such that compat(S) and B are equivalent basic labels, then
    S and decompat(B) are equivalent international labels, otherwise
    decompat(B) = B.

    simple label:  A basic label that does not begin with the ACE
    prefix.  [Observation:  Simple labels have the same semantics as in
    the preexisting standard.]

    ACE label:  A basic label that is altered by decompat().
    [Observation:  All ACE labels begin with the ACE prefix.  ACE labels
    have new semantics not present in the preexisting standard.]

    invalid label:  A basic label that begins with the ACE prefix but is
    not altered by decompat().  [Observation:  Every basic label that is
    neither a simple label nor an ACE label is an invalid label.  These
    labels carry a semantic dubiousness that was not present in the
    preexisting standard.]

Fact 7:  Software that was not deliberately written to handle
international domain names cannot properly compare two international
domain names.

Fact 8:  Even though many software entities do not compare domain
names, it is common for them to pass domain names on to other software
entities, which might need to compare them.

Goal 6 (motivated by facts 2, 7, and 8):  Whenever possible, keep
non-basic international domain names out of the hands of software that
was not deliberately written to handle them.

The following definition is motivated by goal 6:

    international domain name slot:  A domain name slot explicitly
    designated to carry an international domain name.  The designation
    may be static (for example, in the specification of the protocol or
    interface) or dynamic (for example, as a result of negotiation in an
    interactive session).

Requirement 4 (follows from goal 6):  Non-basic international domain
names must not be put into non-international domain name slots.  (But of
course the equivalent basic domain name, obtainable via compat(), can
be put into the slot instead.)

Observation 1:  Obviously, requirement 4 can apply only to IDN-aware
entities.  A non-IDN-aware entity is not normally supposed to have any
non-basic international domain names in the first place, but if it
somehow obtains one, perhaps via manual entry, then of course it cannot
be expected to obey a requirement that it knows nothing about.  It will
obey whatever requirements it was written to obey.

Observation 2:  DNS is a protocol with non-international domain name
slots (in both directions).  Therefore requirement 4 applies to those
slots.  Extensions to DNS could of course define new fields that are
international domain name slots.

Observation 3:  Existing resolver interfaces have non-international
domain name slots (in both directions).  Therefore requirement 4 applies
to those slots (regardless of whether the resolver is IDN-aware, and
regardless of whether it makes use of any DNS extensions).  New resolver
interfaces could of course define new arguments that are international
domain name slots.

Goal 7:  Whenever possible, show users the meaningful form of an
international domain name rather than the ACE form (unless they request
otherwise).

Requirement 5 (follows from goal 7):  IDN-aware entities should by
default apply decompat() to all domain labels before displaying them
to the user, and before putting the domain name into an international
domain name slot likely to be seen by a user.

End of idn-arch-deriv.



From owner-idn@ops.ietf.org  Thu Aug  9 03:04: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 DAA16241
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 03:04:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UjXX-000BsA-00
	for idn-data@psg.com; Wed, 08 Aug 2001 23:43:31 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
To: <idn@ops.ietf.org>
References: <20010808151602.2805.qmail@cr.yp.to>
Subject: [idn] Dan's UTF-8 tests
Date: Wed, 8 Aug 2001 18:31:37 -0500
Organization: EHS Company
MIME-Version: 1.0
Content-Type: text/plain;
Message-Id: <E15UjXX-000BsA-00@psg.com>

charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk



[I'd do more testing but I'm still getting my lab together after moving]


Internet Explorer/Outlook Express 5.5, Windows 2000 Professional, SP2

Asking for http://Ï€.cr.yp.to with IE 5.5 on Win2000, failed when
browser
issued lookup query for 5-byte label of C3 AF E2 82 AC instead of Ï€.
Got a
negative response, and then the resolver appended .ntrg.com. onto the
end of
the query, tried again, and failed that one too. IE reports error an
error
to the user.

Asking for http://Ï€.cr.yp.to/index.html goes through the same steps but
doesn't report an error to the user. It just goes off into lala land.

Trying to paste the domain name into Outlook Express resulted in a
message
addressed to djb@p.cr.yp.to

Replying to the test address gives djb-pibounce-p@cr.yp.to, which is the
same results as pasting the URL from test 1.


Netscape Communicator 4.78, Windows 2000 Professional, SP2

Netscape Communicator 4.78 on Win2000 fails on the hyperlink altogether
with
an error. The name doesn't go out on the wire in any DNS lookups
whatsoever,
suggesting that Navigator is filtering it locally.

Trying to paste the domain name into Communicator's mail client resulted
in
Ã�â‚¬.cr.yp.to, with "djb"@Ã�â‚¬.cr.yp.to being forced for djb@.

Replying to the test address gives "D. J. Bernstein"
<"djb-pibounce-Ã�â‚¬"@cr.yp.to>, same results as pasting


Internet Explorer/Outlook Express 5, MacOS 8.5

Ï€ is transliterated into MacRoman, displaying as Å“Ã„ in the statusbar
and the
input bar. But the browser was able to get to the web site okay.

Pasting the domain name into OE works, resulting in djb@Ï€.cr.yp.to.
*BUT* OE
won't let me send the message, as it greys out the Send button and puts
a
big question mark next to the address.

Replying to the test address gives "djb-pibounce-??"@cr.yp.to


Netscape Communicator 4.75, MacOS 8.5

Ï€ is transliterated into MacRoman, displaying as Å“Ã„ in the statusbar.
But
the browser was able to get to the web site okay.

Pasting the domain name into a message showed it in MacRoman form while
editing, but the domain showed properly after moving to the next field.
However, it still showed as "djb"@ on the left-hand-side.

Replying to the test address gives "djb-pibounce-XX"@cr.yp.to where XX
are
characters I can't be bothered to decode (one looks like lowercase
I-with-umlaut and the other looks like a snippet of DNA sequencing).


Netscape Communicator 4.75, Sparc Solaris 8

The name doesn't go onto the wire and Communicator reports a rejection,
suggesting that the resolver is rejecting the lookup. Note that the name
displayed in the status bar is http://Ã� .cr.yp.to (note the space after
the
I-with-umlaut character).

Pasting the name into a message gives djb@?.cr.yp.to

Replying to the test address gives similar results to Mac test


CDE Mail, Sparc Solaris 8

Replying to the test message gives "djb-pibounce-Ã� "@cr.yp.to (note the
space after I-with-umlaut).


Netscape Communicator 4.75, Digital Unix 4.0d

The domain name is malformed with an I-with-Umlaut and a block (unknown
char) but the web page is opened.

Pasting the domain name into a message gives djb@?.cr.yp.to

Replying to the test message gives "djb-pibounce-Ã�?"@cr.yp.to


Konquerer 2.1.1, KDE 2.1.2, Mandrake Linux 8.0

Clicking the link does nothing. The status bar shows ? instead of pi.


KMail 1.2, KDE 2.1.2, Mandrake Linux 8.0

Replying to the test message gives "djb-pibounce-Ã� "@cr.yp.to (note the
space after I-with-umlaut).


Hopefully this sufficiently proves that just-do-UTF8 is a non-starter.
Dan
we have to do it through a different message type to keep these problems
from happening.


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







From owner-idn@ops.ietf.org  Thu Aug  9 03:06: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 DAA16311
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 03:05:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UjSz-000Bhd-00
	for idn-data@psg.com; Wed, 08 Aug 2001 23:38:49 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15UjSy-000BhX-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 23:38:48 -0700
Received: (qmail 21375 invoked by uid 1001); 9 Aug 2001 06:38:36 -0000
Date: 9 Aug 2001 06:38:36 -0000
Message-ID: <20010809063836.18303.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] rederivation of an IDN architecture
References: <20010809025938.C15655@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Adam M. Costello writes:
> Conjecture 1:  Many people will be reluctant to create domains using
> additional characters if those domains would be inaccessible to
> preexisting protocols, interfaces, software, etc.

No. All that people care about is whether the software works. Protocols,
interfaces, and so on are relevant only to the extent that they help the
software work. Also, people don't care about ``preexisting'' software
unless that software is still in use.

> Goal 1 (motivated by facts 1-3 and conjecture 1):  Allow domain names to
> contain additional characters, while still allowing all domains to be
> referred to by all preexisting protocols, interfaces, software, etc.

Here you've lost sight of the goal of actually DISPLAYING THE NAMES
PROPERLY. This is the whole point of internationalized domain names!

ACE IDNs don't work today, and they aren't going to work in the
foreseeable future. They can, however, be ``referred to.'' Given these
facts, and given your confusion over the basic goal, it's entirely
unsurprising that you end up advocating ACE IDNs.

---Dan



From owner-idn@ops.ietf.org  Thu Aug  9 03:07: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 DAA16326
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 03:07:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UjbI-000C20-00
	for idn-data@psg.com; Wed, 08 Aug 2001 23:47:24 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15UjbH-000C1u-00
	for idn@ops.ietf.org; Wed, 08 Aug 2001 23:47:23 -0700
Received: (qmail 3631 invoked by uid 1001); 9 Aug 2001 06:47:12 -0000
Date: 9 Aug 2001 06:47:12 -0000
Message-ID: <20010809064712.1211.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] Transparent vs. ACE representations (was We are quibbling about WHAT?)
References: <3B71E3CD.CCC80166@zetnet.co.uk> <20010809020911.B15655@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Adam M. Costello writes:
> As Dan Bernstein's recent tests have shown, lots of software stops
> working when domain names contain bytes greater than 127, including
> browsers, resolvers, mail user agents, and mail transfer agents.

Lots of software _already_ works with UTF-8 IDNs, including browsers,
resolvers, mail user agents, and mail transfer agents. A small number of
easily fixed bugs account for all the reported failures.

UTF-8 is way ahead of ACE.

---Dan



From owner-idn@ops.ietf.org  Thu Aug  9 03:10: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 DAA16374
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 03:10:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UjXY-000BsJ-00
	for idn-data@psg.com; Wed, 08 Aug 2001 23:43:32 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15UjXY-000BsJ-00@psg.com>
To: idn-data@psg.com
Date: Wed, 08 Aug 2001 23:43:32 -0700

That's the last time I report UTF-8 test results with OE.

Regardless, none of the tests had 100%. Not a single one. Two of the
tests
were able to open the target URL but they didn't display the domain name
properly, which is not a win as far as Joe Sixpack goes.

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





From owner-idn@ops.ietf.org  Thu Aug  9 03:53: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 DAA16707
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 03:53:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UkQw-000Eep-00
	for idn-data@psg.com; Thu, 09 Aug 2001 00:40:46 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UkQv-000Ect-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 00:40:45 -0700
Received: from [0.0.0.0] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id JAA15176
	for <idn@ops.ietf.org>; Thu, 9 Aug 2001 09:40:13 +0200 (MET DST)
Date: Thu, 09 Aug 2001 08:39:57 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: idn@ops.ietf.org
Subject: Re: [idn] rederivation of an IDN architecture
Message-ID: <1130379.997346397@localhost>
In-Reply-To: <20010809063836.18303.qmail@cr.yp.to>
References: <20010809025938.C15655@arwen.cs.berkeley.edu>
 <20010809063836.18303.qmail@cr.yp.to>
X-Mailer: Mulberry/2.1.0b3 (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 08/09/2001 6:38 AM +0000 "D. J. Bernstein" <djb@cr.yp.to> wrote:

> No. All that people care about is whether the software works. Protocols,
> interfaces, and so on are relevant only to the extent that they help the
> software work. Also, people don't care about ``preexisting'' software
> unless that software is still in use.

Everyone want functionality, but we seem to disagree on how to reach it.

People come to the IETF because they see a standard is needed to ensure
functionality. If a standard was not needed (and you claim that a standard
is not needed, as software already "work" (we have all seen the results of
the tests on this list that we obviously disagree on what "work" means)).

If you don't want standards, or don't think they are needed, please don't
disrupt the people which are discussing new standards in the IETF.

The IETF is not forcing, and can not force people using it's standards.
People can either follow them or not. It is the choice of the implementors.

   paf




From owner-idn@ops.ietf.org  Thu Aug  9 05:48: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 FAA19301
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 05:48:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UmC5-000Ipg-00
	for idn-data@psg.com; Thu, 09 Aug 2001 02:33:33 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UmC4-000IpT-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 02:33:32 -0700
Received: from bbthead.dcrocker.net (host217-33-136-170.ietf.ignite.net [217.33.136.170])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id CAA28855;
	Thu, 9 Aug 2001 02:33:26 -0700
Message-Id: <5.1.0.14.2.20010809101843.034d1eb0@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 09 Aug 2001 10:31:19 +0100
To: David Hopwood <david.hopwood@zetnet.co.uk>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] Transparent vs. ACE representations (was We are
  quibbling about WHAT?)
Cc: idn@ops.ietf.org
In-Reply-To: <3B71E3CD.CCC80166@zetnet.co.uk>
References: <5.1.0.14.2.20010729172557.0302f008@brandenburg.com>
 <5.1.0.14.2.20010803135104.032186f0@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:13 AM 8/9/2001, David Hopwood wrote:
>But, you may say, that encoding wasn't UTF-8. Doesn't matter.

well, actually it does.


>Suppose for
>the sake of argument that the message had contained characters outside the
>US-ASCII repertoire (in a domain name or elsewhere).

If the text switches from one character set to another, then no, it is 
unlikely the processing software will handle that well.  If you mean that 
the text is all in the UTF-8, then, no, it isn't.  Mine is in ASCII.  Hence 
your suggestion means we would have mixed Ascii, UTF-8.

The real point is that you appear to be assuming a much more simplified and 
consistent processing environment for characters, across applications, than 
actually exists.


>Call a domain name representation within
>some surrounding text (or other protocol elements) "transparent", if the
>representation is of a character string such that each character in the
>string stands for the same character in the domain name.

By that definition, UTF-8 is not transparent.  It is an encoding scheme, as 
is ACE.


>The thesis behind the ACE-only proposals seems to be that most existing
>protocols, formats, and implementations assume that domain names only
>use US-ASCII characters, and so using a non-ASCII representation will 
>break them. he vast majority of cases, that simply isn't true

The premise has been present in the design of Internet protocols from the 
beginning.  Much has changed since then, but not everything.

The premise that all software will correctly process UTF-8 has been 
demonstrated to be false.


> > As to predictions of the future, well, they are always wrong.
>
>That's obvious nonsense. It is a perfectly safe prediction that the
>default encoding (often the only encoding) used in almost all Internet
>protocols in the near future will be UTF-8.

I do not know how many such confident predictions of the future you have 
suffered through, but many of us have watched them made repeatedly over the 
last 25 years and, I am sorry to say, they are usually incorrect.  Not 
always, no.  But frequently.


>  In a sense there is nothing
>to predict; the decision has already been made in RFC 2277 / BCP 18, and
>the process of making the necessary modifications to existing standards
>is already well underway.

You should review the history of "decisions" that were made around the 
world, by businesses and governments, for many other technical choices, 
such as ADA, OSI, CMIP, ATM, ...

Nothing is over until it is over.  No decision is firm until it is in the past.

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 Aug  9 05:49: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 FAA19361
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 05:49:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UmC4-000IpZ-00
	for idn-data@psg.com; Thu, 09 Aug 2001 02:33:32 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UmC3-000IpS-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 02:33:31 -0700
Received: from bbthead.dcrocker.net (host217-33-136-170.ietf.ignite.net [217.33.136.170])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id CAA28858;
	Thu, 9 Aug 2001 02:33:27 -0700
Message-Id: <5.1.0.14.2.20010809103327.02259990@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 09 Aug 2001 10:34:22 +0100
To: "D. J. Bernstein" <djb@cr.yp.to>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] Transparent vs. ACE representations (was We are
  quibbling about WHAT?)
Cc: idn@ops.ietf.org
In-Reply-To: <20010809064712.1211.qmail@cr.yp.to>
References: <3B71E3CD.CCC80166@zetnet.co.uk>
 <20010809020911.B15655@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 07:47 AM 8/9/2001, D. J. Bernstein wrote:
>Lots of software _already_ works with UTF-8 IDNs, including browsers,
>resolvers, mail user agents, and mail transfer agents. A small number of
>easily fixed bugs account for all the reported failures.
>
>UTF-8 is way ahead of ACE.

Fortunately, the IETF has a history of choosing to be less cavalier about 
global impact of transition processes.

d/


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




From owner-idn@ops.ietf.org  Thu Aug  9 06:34: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 GAA20348
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 06:34:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Umre-000KRQ-00
	for idn-data@psg.com; Thu, 09 Aug 2001 03:16:30 -0700
Received: from twnic.net.tw ([211.72.210.250])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Umrd-000KRH-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 03:16:29 -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 SAA12946;
	Thu, 9 Aug 2001 18:18:59 +0800
Message-ID: <3B7266F8.308023B0@twnic.net.tw>
Date: Thu, 09 Aug 2001 18:33:28 +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: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
CC: idn@ops.ietf.org, "=?big5?B?pP2kaqyw?=" <wdw@iis.sinica.edu.tw>,
        "
	=?big5?B?p2SrVL+z?= Wu Chun-Hsin" <wuch@gate.sinica.edu.tw>
Subject: Re: [idn] agenda v1.0 ietf-london
References: <5.1.0.14.1.20010807082439.03681ec0@127.0.0.1>
Content-Type: text/plain; charset=big5
Content-Transfer-Encoding: 8bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Marc & James

I have sent mail to both of you to request 15 minutes for present UNAME
by D.W. Wang ( He is in London now) .
But I can not find UNAME topic in the agenda.
Would you please modify it?

Erin Chen

Marc Blanchet ¼g¤J¡G

> Hi,
>   here is a first cut of the proposed agenda. The idea here is to leave
> room for concensus building.
>
> ==================================================
> Agenda:
>   agenda bashing, 1 min., Marc Blanchet
>   wg update, 5 min., Marc Blanchet
>   ACE encoding
>    ACE comparison, 5 min., Yoshiro Yoneya
>    Reordering, 5 min., Soobok Lee
>    ACE concensus building (Choosing an ACE if we need one), 5 min.
>   Matching
>    Nameprep update, 5 min., Paul Hoffman
>    TSconv, 5 min., Xiang Deng
>    Hangulchar, 5 min., Soobok Lee
>    Matching concensus building, 10 min.
>   Protocol
>    Protocol comparison, 10 min., Dave Crocker
>    Protocol concensus building, 55 min.
>   Conclusion and next steps, 10 min.
> ================================================
>
> Marc & James.
>
> PS1. I was on vacation for the past few weeks, so that is why both the
> agenda and the pool were not updated.
> PS2. I will update the web site shortly and will announce in a separate
> email the document pool (a few are not yet there because of PS1 above).




From owner-idn@ops.ietf.org  Thu Aug  9 07:00: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 HAA20746
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 07:00:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UnCc-000LNm-00
	for idn-data@psg.com; Thu, 09 Aug 2001 03:38:10 -0700
Received: from twnic.net.tw ([211.72.210.250])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UnCb-000LNf-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 03:38:09 -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 SAA14436;
	Thu, 9 Aug 2001 18:40:38 +0800
Message-ID: <3B726C0A.1B34C3A@twnic.net.tw>
Date: Thu, 09 Aug 2001 18:55:07 +0800
From: Erin Chen <erin@twnic.net.tw>
Organization: TWNIC
X-Mailer: Mozilla 4.51 [zh-tw]C-CCK-MCD   (WinNT; U)
X-Accept-Language: zh-TW,en,pdf
MIME-Version: 1.0
To: internet-drafts@ietf.org, jseng@pobox.org.sg, Marc.Blanchet@viagenie.qc.ca,
        idn@ops.ietf.org, abelyang@twnic.net.tw
Subject: Re: [idn] draft about Evaluation of various ACEs with existing Chinese 
 (BIG5) Domain Names
References: <00de01c0ffd0$cd17bfa0$4607e29f@xiaodonglee> <3B4EE960.DD253971@twnic.net.tw>
Content-Type: text/plain; charset=big5
Content-Transfer-Encoding: 8bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Dear all

Till now I did not see this draft have been announce by IETF IDN WG.
Neither find it on the IETF I-Draft web site.
Would some one please help me to check it?

Erin Chen

Erin Chen ¼g¤J¡G

> Dear IETF & IDN WG:
>
> Attached is the draft of :
> Evaluation of various ACEs with existing Chinese (BIG5) Domain Names
>
> This document offer an overview of the results of various ACEs that
> being
> applied to Chinese (BIG5) Domain Names. And give a brief summary of
> the evaluation result.
>
> Thanks for any suggestion and comment!
>
> Erin Chen
> TWNIC
>  
>
>   ------------------------------------------------------------------------
> Internet Draft                                                 Abel Yang
> draft-ietf-idn-ace-eval-tw-00.txt                              Erin Chen
> Jul 13, 2001                                                       TWNIC
> Expires Jan 13, 2002
>
>    Evaluation of various ACEs with existing Chinese (BIG5) Domain Names
>
> Status of this memo
>
>     This document is an Internet-Draft and is in full conformance with
>     all provisions of Section 10 of RFC2026.
>
>     Internet-Drafts are working documents of the Internet Engineering
>     Task Force (IETF), its areas, and its working groups.  Note that
>     other groups may also distribute working documents as
>     Internet-Drafts.
>
>     Internet-Drafts are draft documents valid for a maximum of six
>     months and may be updated, replaced, or obsoleted by other documents
>     at any time.  It is inappropriate to use Internet-Drafts as reference
>     material or to cite them other than as "work in progress."
>
>     The list of current Internet-Drafts can be accessed at
>     http://www.ietf.org/ietf/1id-abstracts.txt
>
>     The list of Internet-Draft Shadow Directories can be accessed at
>     http://www.ietf.org/shadow.html.
>
> Abstract
>
>     In order to help the ACE (ASCII Compatible Encoding) Design Team in
>     IDN Working Group to selecting an appropriate ACE proposal. This
>     document offer an overview of the results of various ACEs that being
>     applied to Chinese (BIG5) Domain Names. And give a brief summary of
>     the evaluation result.
>
> 1. Test data and tools
>
>     The sample data were come from TWNIC registration database. All of
>     them are in BIG5 encoding. The amount of the data is 28454. And the
>     data distribution by the length is:
>
>       Length of data     quantity of BIG5 Domain Names
>         2 chars                 3762
>         3 chars                 3914
>         4 chars                 4613
>         5 chars                 1723
>         6 chars                 1851
>         7 chars                 4282
>         8 chars                 1621
>         9 chars                 1254
>        10 chars                 2075
>        11 chars                 1215
>        12 chars                  753
>        13 chars                  646
>        14 chars                  745
>
>                         amount=28454
>
>     TWNIC just accept 2 to 14 BIG5 chars in a Chinese Domain Name. Those
>     data are all in local encoding of BIG5 ( or CP950 ). Base on those
>     data, apply them to various ACEs. There are RACE-03 [RACE], BRACE-00
>     [BRACE], LACE-01 [LACE], UTF-6-00 [UTF6], DUDE-02 [DUDE],
>     AMC-ACE-M-00 [AMCACEM], AltDUDE-01 [AltDUDE], AMC-ACE-O-00 [AMCACEO],
>     and AMC-ACE-R-01 [AMCACER].
>
> 2. Result of each ACE length
>
>     The CHN_len is the length of Chinese (BIG5) domain name in byte
>     before apply ACE encoding. All of the data in the same CHN_len, the
>     max_len is the maximum length, the min_len is the minimum length,
>     the aver_len is the averager length of them after apply ACE encoding.
>
>   2.1 AMC-ACE-M
>
>     CHN_len    max_len  min_len  aver_len
>     -----------  -------- -------- --------
>         2                8       5       8
>         3               11       6      11
>         4               17       8      14
>         5               17      11      17
>         6               21      11      20
>         7               24      13      22
>         8               27      15      25
>         9               30      16      28
>         10              33      18      31
>         11              36      22      34
>         12              39      19      37
>         13              42      21      40
>         14              45      23      43
>
>   2.2 AMC-ACE-O
>
>     CHN_len    max_len  min_len  aver_len
>     -----------  -------- -------- --------
>         2                8       5       8
>         3               12       6      11
>         4               20       9      15
>         5               20      11      18
>         6               24      11      22
>         7               27      13      25
>         8               31      15      29
>         9               35      16      32
>         10              39      18      36
>         11              42      24      38
>         12              46      19      41
>         13              50      21      44
>         14              54      23      48
>
>   2.3 AMC-ACE-R
>
>     CHN_len    max_len  min_len  aver_len
>     -----------  -------- -------- --------
>         2                8       5       8
>         3               12       6      12
>         4               20       9      16
>         5               20      11      19
>         6               24      11      23
>         7               28      13      26
>         8               32      15      30
>         9               36      16      34
>         10              40      18      38
>         11              44      24      41
>         12              48      19      44
>         13              52      21      48
>         14              56      24      51
>  
>
>   2.4 AltDUDE
>
>     CHN_len    max_len  min_len  aver_len
>     -----------  -------- -------- --------
>         2                8       5       8
>         3               12       6      11
>         4               20       8      16
>         5               20      13      19
>         6               24      11      23
>         7               28      14      26
>         8               32      15      30
>         9               36      18      34
>         10              40      21      38
>         11              44      26      41
>         12              48      26      46
>         13              52      25      48
>         14              56      30      53
>
>   2.5 BRACE
>
>     CHN_len    max_len  min_len  aver_len
>     -----------  -------- -------- --------
>         2                7       5       7
>         3               10       7      10
>         4               17       8      14
>         5               17      11      17
>         6               20      11      20
>         7               23      13      23
>         8               28      14      26
>         9               30      15      30
>         10              33      17      33
>         11              36      22      36
>         12              39      18      39
>         13              42      20      42
>         14              46      23      46
>
>   2.6 DUDE
>
>     CHN_len    max_len  min_len  aver_len
>     -----------  -------- -------- --------
>         2                8       5       8
>         3               12       6      11
>         4               20       8      16
>         5               20      13      19
>         6               24      11      23
>         7               28      15      26
>         8               32      15      30
>         9               36      18      34
>         10              40      21      38
>         11              44      27      41
>         12              48      26      46
>         13              52      25      48
>         14              56      30      53
>
>   2.7 LACE
>
>     CHN_len    max_len  min_len  aver_len
>     -----------  -------- -------- --------
>         2                8       7       8
>         3               12       8      12
>         4               18      10      15
>         5               18      18      18
>         6               21      16      21
>         7               24      21      24
>         8               31      23      28
>         9               31      24      31
>         10              34      26      34
>         11              37      34      37
>         12              40      29      40
>         13              44      31      44
>         14              47      36      47
>
>   2.8 RACE
>
>     CHN_len    max_len  min_len  aver_len
>     -----------  -------- -------- --------
>         2                8       5       8
>         3               12       7      12
>         4               18       8      15
>         5               18      18      18
>         6               21      20      21
>         7               24      24      24
>         8               31      28      28
>         9               31      31      31
>         10              34      34      34
>         11              37      37      37
>         12              40      40      40
>         13              44      44      44
>         14              47      47      47
>
>   2.9 UTF-6
>
>     CHN_len    max_len  min_len  aver_len
>     -----------  -------- -------- --------
>         2                8       5       8
>         3               12       6      12
>         4               20       9      16
>         5               20      14      20
>         6               24      14      24
>         7               28      18      28
>         8               32      20      32
>         9               36      21      36
>         10              40      23      40
>         11              44      30      44
>         12              48      28      48
>         13              52      29      52
>         14              56      33      56
>
> 3. Result of each ACE conversion speed
>
>                 UTF-6   RACE    LACE    BRACE   DUDE    ALTDUDE
>         MAX     0.80    0.75    0.82    0.86    0.74    0.70
>         MIN     0.56    0.55    0.52    0.62    0.53    0.53
>         AVERAGE 0.68    0.64    0.62    0.73    0.64    0.62
>
>                 AMC-ACE-M       AMC-AMC-O       AMC-ACE-R
>         MAX     1.12            1.92            0.99
>         MIN     0.86            1.69            0.67
>         AVERAGE 0.98            1.81            0.82
>
> 4. Summary of the result
>
>     All the ACE max_length is less than 64, because the Chinese
>     Domain Name is limited from 2 to 14 BIG5 chars. For those sample
>     data, the result of LENGTH and SPEED, it seems the LACE and RACE
>     are better than others.
>
> 5. Acknowledgements
>
>     This ACE evaluation testing tool was provided by JPNIC.
>     TWNIC provide the real registered Chinese ( BIG5 ) domain names.
>     Hsu Nai-Wen <snw@twnic.net.tw> and TWNIC MDNS technical team give
>     a lot of suggestion.
>
> 6. Author's Address
>
>     Abel Yang
>     Taiwan Network Information Center (TWNIC)
>     4F-2, No. 9, Sec. 2, Roosevelt Rd., Taipei, 100 Taiwan.
>     Email: abelyang@twnic.net.tw
>     Tel: +886-23411313#505
>
>     Erin Chen
>     Taiwan Network Information Center (TWNIC)
>     4F-2, No. 9, Sec. 2, Roosevelt Rd., Taipei, 100 Taiwan.
>     Email: erin@twnic.net.tw
>     Tel: +886-23411313#502
>
> 7. References
>
>     [RFC1035]  "DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION",
>                RFC1034, Nov 1987, P. Mockapetris
>     [RACE]     "RACE: Row-based ASCII Compatible Encoding for IDN",
>                draft-ietf-idn-race-03.txt, Nov 2000, P Hoffman
>     [BRACE]    "BRACE: Bi-mode Row-based ASCII-Compatible Encoding
>                for IDN version 0.1.2"
>                draft-ietf-idn-brace-00.txti, Sep 2000, A Costello
>     [LACE]     "LACE: Length-based ASCII Compatible Encoding for IDN"
>                draft-ietf-idn-lace-01.txt, Jan 2001, M Davis, P Hoffman
>     [UTF6]     "UTF-6 - Yet Another ASCII-Compatible Encoding for IDN"
>                draft-ietf-idn-utf6-00, Nov 2000, M Welter, B Spolarich
>     [DUDE]     "Differential Unicode Domain Encoding (DUDE)"
>                draft-ietf-idn-dude-02.txt, Jun 2001, M Welter,
>                B Spolarich, A Costello
>     [AMCACEM]  "AMC-ACE-M version 0.1.0"
>                draft-ietf-idn-amc-ace-m-00.txt, Feb 2001, A Costello
>     [AltDUDE]  "AltDUDE version 0.0.2"
>                draft-ietf-idn-altdude-00.txt, Mar 2001, A Costello
>     [AMCACEO]  "AMC-ACE-O version 0.0.3"
>                draft-ietf-idn-amc-ace-o-00.txt, Mar 2001, A Costello
>     [AMCACER]  "AMC-ACE-R version 0.2.1"
>                draft-ietf-idn-amc-ace-r-01.txt, May 2001, A Costello
>     [AMCACEV]  "AMC-ACE-V version 0.1.0"
>                draft-ietf-idn-amc-ace-v-00.txt, May 2001, A Costello
>     [AMCACEW]  "AMC-ACE-W version 0.1.0"
>                draft-ietf-idn-amc-ace-w-00.txt, May 2001, A Costello
>     [MACE]     "MACE: Modal ASCII Compatible Encoding for IDN"
>                draft-ietf-idn-mace-00.txt, Jun 2001, M Ishisone, Y Yoneya
>     [LDUDE]    "Improving ACE using code point reordering v0.9"
>                draft-ietf-idn-lsb-ace-00.txt, Jun 2001, Soobok Lee
>     [MDNKIT]   "Multilingual Domain Name tool Kit",
>              http://www.nic.ad.jp/jp/research/idn/mdnkit/download/
>     [NAMEPREP] "Preparation of Internationalized Host Names",
>                draft-ietf-idn-nameprep-03.txt, Feb 2001, P Hoffman,
>                M Blanchet
>  




From owner-idn@ops.ietf.org  Thu Aug  9 07:37: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 HAA21116
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 07:37:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Unq1-000N4V-00
	for idn-data@psg.com; Thu, 09 Aug 2001 04:18:53 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15Unq0-000N4P-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 04:18:52 -0700
Message-ID: <001301c120c6$31f15ec0$5b8d21d9@ietf.ignite.net>
From: "Edmon" <edmon@neteka.com>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
References: <200107301509.f6UF91N23867@nic-naa.net> <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net> <3B711FBC.AAD1F378@zetnet.co.uk>
Subject: Re: [idn] SC/TC equivalence
Date: Thu, 9 Aug 2001 07:26:53 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I concur.
Edmon

----- Original Message -----
From: "David Hopwood" <david.hopwood@zetnet.co.uk>
>
> Unless I'm missing something, SC/TC equivalence doesn't affect the
protocol;
> it's purely a local issue for administrators of zones that include names
> with Chinese characters. They could configure the authoritative servers
for
> those zones to use any of the following approaches:
>
> 1. have zone entries for each combination.
> 2. have zone entries only for folded names, and do folding in the server.
> 3. have the server try to match the unfolded name first, and if not found,
>    try to match the folded name.
>
> Intermediate servers will cache the variants that are actually used (which
> is probably only a small subset of the possible variants).
>
> So the WG doesn't need to decide this, apart from pointing out the
options.
>
> - --





From owner-idn@ops.ietf.org  Thu Aug  9 07:38: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 HAA21130
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 07:38:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Unun-000NHE-00
	for idn-data@psg.com; Thu, 09 Aug 2001 04:23:49 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15Unum-000NGy-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 04:23:48 -0700
Message-ID: <002601c120c6$e2d4e0e0$5b8d21d9@ietf.ignite.net>
From: "Edmon" <edmon@neteka.com>
To: "Dan Ebert" <dan@enic.cc>
Cc: "Dave Crocker" <dhc@dcrocker.net>,
        "John C Klensin" <klensin@research.att.com>, <idn@ops.ietf.org>
References: <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net> <13749451.997252461@host217-33-136-108.ietf.ignite.net> <5.1.0.14.2.20010808143501.03f52140@dcrocker.net> <007601c1202e$478d1fa0$5b8d21d9@ietf.ignite.net> <3B7179C0.D0C4D814@enic.cc>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Thu, 9 Aug 2001 07:31:48 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

From: "Dan Ebert" <dan@enic.cc>
> It seems to me that it would be more confusing if TC/SC behaved
> differently for different TLDs.  One of the (I think beneficial)
> features of DNS is that the behavior is uniform across all TLDs (com
> works like net works like org ...)

This is not true.  Registration restrictions differ from TLD to TLD.

> I would suggest that it may be a
> better idea to use have a script on the web server look at user IP or
> browser environment variable to determine what page should be displayed
> (or redirect to a different server).
> 

What about emails?

Edmon




From owner-idn@ops.ietf.org  Thu Aug  9 07: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 HAA21201
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 07:42:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Unoh-000N04-00
	for idn-data@psg.com; Thu, 09 Aug 2001 04:17:31 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15Unoh-000Mzu-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 04:17:31 -0700
Message-ID: <000b01c120c5$fef99460$5b8d21d9@ietf.ignite.net>
From: "Edmon" <edmon@neteka.com>
To: "Erin Chen" <erin@twnic.net.tw>,
        "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>
Cc: <idn@ops.ietf.org>, =?big5?B?pP2kaqyw?= <wdw@iis.sinica.edu.tw>,
        "=?big5?B?p2SrVL+zIFd1IENodW4tSHNpbg==?=" <wuch@gate.sinica.edu.tw>
References: <5.1.0.14.1.20010807082439.03681ec0@127.0.0.1> <3B7266F8.308023B0@twnic.net.tw>
Subject: Re: [idn] agenda v1.0 ietf-london
Date: Thu, 9 Aug 2001 07:25:25 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I was trying to put in a last effort for the enhanced ACE form (ACE16x -
simplified DUDE or ACE37 - combination of the 3 primary ACEs identified by
the ACE design team) hoping to generate some support from the WG through my
presentation which would clarify much of the work. This was also not
included in the agenda.
Edmon

PS. I also sent mail, quite some time ago, requesting for 5-10 minutes for
the presentation.

----- Original Message -----
From: "Erin Chen" <erin@twnic.net.tw>
> Marc & James
>
> I have sent mail to both of you to request 15 minutes for present UNAME
> by D.W. Wang ( He is in London now) .
> But I can not find UNAME topic in the agenda.
> Would you please modify it?
>
> Erin Chen
>





From owner-idn@ops.ietf.org  Thu Aug  9 07: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 HAA21320
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 07:52:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Uo9F-000Npw-00
	for idn-data@psg.com; Thu, 09 Aug 2001 04:38:45 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Uo9E-000Np5-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 04:38:45 -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 f79C2FQ10623
	for <idn@ops.ietf.org>; Thu, 9 Aug 2001 08:02:15 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010809073959.06079ec8@127.0.0.1>
X-Sender: blanchet@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 09 Aug 2001 07:41:21 -0400
To: idn@ops.ietf.org
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: [idn] updated pool
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hi,
	I updated the web site with the other documents that showed core of 
interest and went in just around the start of my vacations. Hope that I 
haven't forgot one.

Marc.




From owner-idn@ops.ietf.org  Thu Aug  9 07:52: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 HAA21331
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 07:52:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Uo9W-000Nrh-00
	for idn-data@psg.com; Thu, 09 Aug 2001 04:39:02 -0700
Received: from twnic.net.tw ([211.72.210.250])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Uo9V-000NrQ-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 04:39:01 -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 TAA18082;
	Thu, 9 Aug 2001 19:41:43 +0800
Message-ID: <3B727A5C.1CC27297@twnic.net.tw>
Date: Thu, 09 Aug 2001 19:56:12 +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: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>, idn@ops.ietf.org,
        "
	=?big5?B?pP2kaqyw?=" <wdw@iis.sinica.edu.tw>,
        "=?big5?B?p2SrVL+z?= Wu 
	Chun-Hsin" <wuch@gate.sinica.edu.tw>
Subject: Re: [idn] agenda v1.0 ietf-london
References: <5.1.0.14.1.20010807082439.03681ec0@127.0.0.1> <3B7266F8.308023B0@twnic.net.tw> <01a501c120bf$e4785be0$e48b21d9@jamessonyvaio>
Content-Type: text/plain; charset=big5
Content-Transfer-Encoding: 8bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Dear James,

Thank you for your promply reply.
I think we are not just only present on the draft, but introduce more about
UNAME update, how to implement uname, how uname compatible with
IDNA & NAMEPREP, and so on.... I think that would be help for make
consensus.

You can verify the topic with the Dr. D.W. Wang, he is in your London
meeting.

As we know, before discuss building Matching concensus,  there are three
drafts
will present in advance. So, I think briefly report on UNAME would be help
for
understanding and make consensus.

Erin Chen

James Seng/Personal ¼g¤J¡G

> Hi Eric,
>
> I am sorry that we didnt make it clear.
>
> We discussed and decided there should be no "presentation" on
> internet-draft this time. Instead, we will focus on the discussion and
> comparison. This is to allow us to focus to get consensus within the WG.
>
> -James Seng
>
> ----- Original Message -----
> From: "Erin Chen" <erin@twnic.net.tw>
> To: "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>
> Cc: <idn@ops.ietf.org>; "¤ý¤j¬°" <wdw@iis.sinica.edu.tw>; " §d«T¿³ Wu
> Chun-Hsin" <wuch@gate.sinica.edu.tw>
> Sent: Thursday, August 09, 2001 6:33 PM
> Subject: Re: [idn] agenda v1.0 ietf-london
>
> > Marc & James
> >
> > I have sent mail to both of you to request 15 minutes for present
> UNAME
> > by D.W. Wang ( He is in London now) .
> > But I can not find UNAME topic in the agenda.
> > Would you please modify it?
> >
> > Erin Chen
> >
> > Marc Blanchet ¼g¤J¡G
> >
> > > Hi,
> > > ?here is a first cut of the proposed agenda. The idea here is to
> leave
> > > room for concensus building.
> > >
> > > ==================================================
> > > Agenda:
> > > ?agenda bashing, 1 min., Marc Blanchet
> > > ?wg update, 5 min., Marc Blanchet
> > > ?ACE encoding
> > > ? ACE comparison, 5 min., Yoshiro Yoneya
> > > ? Reordering, 5 min., Soobok Lee
> > > ? ACE concensus building (Choosing an ACE if we need one), 5 min.
> > > ?Matching
> > > ? Nameprep update, 5 min., Paul Hoffman
> > > ? TSconv, 5 min., Xiang Deng
> > > ? Hangulchar, 5 min., Soobok Lee
> > > ? Matching concensus building, 10 min.
> > > ?Protocol
> > > ? Protocol comparison, 10 min., Dave Crocker
> > > ? Protocol concensus building, 55 min.
> > > ?Conclusion and next steps, 10 min.
> > > ================================================
> > >
> > > Marc & James.
> > >
> > > PS1. I was on vacation for the past few weeks, so that is why both
> the
> > > agenda and the pool were not updated.
> > > PS2. I will update the web site shortly and will announce in a
> separate
> > > email the document pool (a few are not yet there because of PS1
> above).
> >
> >




From owner-idn@ops.ietf.org  Thu Aug  9 07: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 HAA21344
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 07:53:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Uo3g-000NcA-00
	for idn-data@psg.com; Thu, 09 Aug 2001 04:33:00 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Uo3f-000Nc2-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 04:33:00 -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, 9 Aug 2001 04:44:35 -0700
Message-ID: <002d01c120c8$403ef3a0$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
References: <200107301509.f6UF91N23867@nic-naa.net> <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net> <001601c11fed$a80b2f20$fb05738c@ncu.edu.tw> <005001c1200d$01f85480$d43f7018@mtag1.on.home.com> <3B71A3DE.8DF843B4@zetnet.co.uk> <001901c12053$da3eaec0$d43f7018@mtag1.on.home.com> <3B71D034.63F361B6@zetnet.co.uk>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Thu, 9 Aug 2001 07:41:37 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi David,

Thanks for the info-  I will certainly take a look at that.

As far as there being "no technical issues", I don't think I am quite
off the hook yet.  The IDN WG may still tear apart my idea because it
is not a straight forward concept as gTLDs/ccTLDs and involves:
1.  Relationship between lsTLDs of the same language.
2.  Nameprep to prohibit invalid scripts of lsTLDs.

You may not be so generous when you read my draft on the 14th.

Thanks
Ben Chan


----- Original Message -----
From: "David Hopwood" <david.hopwood@zetnet.co.uk>
To: "ben" <ben@cc-www.com>; <idn@ops.ietf.org>
Sent: Wednesday, August 08, 2001 7:50 PM
Subject: Re: [idn] opting out of SC/TC equivalence


-----BEGIN PGP SIGNED MESSAGE-----

ben wrote:
> The ICANN Board's Internal Working Group asked:  "Presumably there
> will be a demand for top level IDNs, i.e., [IDN].[IDN]. What role
> should ICANN play with respect to the selection of these top level
> names and their registries? What should be the role of the country
> code registry of the country where a particular script is a native
> script? And what if a particular script is a native script in more
> than one country?"

These are policy issues, not technical issues, so it isn't the role of
the IDN WG to take any position on them. (That doesn't prevent you or
anyone else making an individual comment on this subject to ICANN, of
course. I suggest reading RFC 3071 first.)

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

iQEVAwUBO3HP1zkCAxeYt5gVAQE0OAf/XRUdkKvEiOeEaUjC+UutG3wejoD74XeW
+4XCW2Ixy8R31M7roUby21FpUvpgaPNAWIaCQf4opE0rV9STz0+6eUVT6IhQ7FEL
zfCO+z1yBD2nwz9fySF6vrqjrzLI0qRKiM7lBOBFbSvX6zhB2Gl6hXIunEJeKcmi
xB55Umm5RPurAPgRW/sfum13Kw1QP96qKeOwTZbZTqVhDoGv3Zm6e3oCZBWa8poI
7SV8brg+Iprpn+8sgAPFEsTbdE2zUsegMTgF2DIaU0sN1a19J4VdEy7QaRPAKa0j
biz24RziNj98SJ8KUjOohcglb0dT9GyxoKHH9KRFMZM0g5utoSF0pg==
=Y4L+
-----END PGP SIGNATURE-----







From owner-idn@ops.ietf.org  Thu Aug  9 09:27: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 JAA23079
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 09:27:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UpYA-0002SG-00
	for idn-data@psg.com; Thu, 09 Aug 2001 06:08:34 -0700
Received: from [217.13.28.204] (helo=eikenes.alvestrand.no)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UpY9-0002Of-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 06:08:34 -0700
Received: from HALVESTR-W2K.cisco.com (eikenes.alvestrand.no [217.13.28.203])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id BD82961CC4; Thu,  9 Aug 2001 15:04:56 +0200 (CEST)
Date: Thu, 09 Aug 2001 13:54:46 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: David Hopwood <david.hopwood@zetnet.co.uk>, idn@ops.ietf.org
Subject: Re: [idn] Which names are valid? (was How should labels be
 encoded?)
Message-ID: <541958495.997365286@localhost>
In-Reply-To: <3B67FE19.29536D40@zetnet.co.uk>
References:  <3B67FE19.29536D40@zetnet.co.uk>
X-Mailer: Mulberry/2.1.0b3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On 1. august 2001 14:03 +0100 David Hopwood <david.hopwood@zetnet.co.uk> 
wrote:

> What do you propose to call the query string used for a SRV lookup
> (e.g. "_ldap._tcp.example.com"), if not a domain name? It is certainly
> a domain name as defined and used in RFCs 1034, 1035 and 2181 (although
> not a host name).

with respect:
draft-ietf-idn-requirements-08.txt has been in the group for a LONG time.

                Harald

1.3 Definition of "hostname" and "Internationalized Domain Name"

In the DNS protocols, a name is referred to as a sequence of octets.
However, when discussing requirements for internationalized domain
names, what we are looking for are ways to represent characters that
are meaningful for humans.

In this document, this is referred to as a "hostname". While this term
has been used for many different purposes over the years, it is used
here in the sense of sequence of characters (not octets) representing a
domain name conforming to the limited hostname syntax RFC 952.

This document attempts to define the requirements for an
"Internationalized Domain Name" (IDN). This is defined as a sequence of
characters that can be used in the context of functions where a hostname
is used today, but contains one or more characters that are outside the
set of characters specified as legal characters for host names
RFC 1123.



From owner-idn@ops.ietf.org  Thu Aug  9 09:35: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 JAA23296
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 09:35:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Upnu-000342-00
	for idn-data@psg.com; Thu, 09 Aug 2001 06:24:50 -0700
Received: from mail-blue.research.att.com ([135.207.30.102])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Upnt-00033v-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 06:24:49 -0700
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id D98AF4CE24; Thu,  9 Aug 2001 09:24:48 -0400 (EDT)
Received: from host217-33-136-108.ietf.ignite.net (secure.research.att.com [135.207.24.10])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id JAA20189;
	Thu, 9 Aug 2001 09:24:44 -0400 (EDT)
Date: Thu, 09 Aug 2001 09:01:49 -0400
From: John C Klensin <klensin@research.att.com>
To: Edmon <edmon@neteka.com>
Cc: idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <2109737.997347709@localhost>
In-Reply-To: <002601c120c6$e2d4e0e0$5b8d21d9@ietf.ignite.net>
References:  <002601c120c6$e2d4e0e0$5b8d21d9@ietf.ignite.net>
X-Mailer: Mulberry/2.1.0b3 (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, 09 August, 2001 07:31 -0400 Edmon
<edmon@neteka.com> wrote:

> From: "Dan Ebert" <dan@enic.cc>
>> It seems to me that it would be more confusing if TC/SC behaved
>> differently for different TLDs.  One of the (I think
>> beneficial) features of DNS is that the behavior is uniform
>> across all TLDs (com works like net works like org ...)
> 
> This is not true.  Registration restrictions differ from TLD to
> TLD.

But a query is interpreted independent of TLD.  And once the
query is made, the name is resolved exactly the same way,
regardless of the TLD.

Those things, which are the important issues in determining
whether a given name "means" the same thing to you as it does to
me, are, and would be, true even if a particular domain violates
the current LDH rules in the names it accepts/ registers.

   john




From owner-idn@ops.ietf.org  Thu Aug  9 09: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 JAA23651
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 09:50:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Uq4P-0003u5-00
	for idn-data@psg.com; Thu, 09 Aug 2001 06:41:53 -0700
Received: from shell.nominum.com ([128.177.192.160])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Uq4O-0003tL-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 06:41:52 -0700
Received: from BarrFS9RB01 (shell.nominum.com [128.177.192.160])
	by shell.nominum.com (Postfix) with SMTP
	id DCF033190C; Thu,  9 Aug 2001 06:41:39 -0700 (PDT)
Reply-To: <Barr.Hibbs@Nominum.com>
From: "Barr Hibbs" <Barr.Hibbs@Nominum.com>
To: "Adam M. Costello" <amc@cs.berkeley.edu>,
        "idn working group" <idn@ops.ietf.org>
Subject: RE: [idn] rederivation of an IDN architecture
Date: Thu, 9 Aug 2001 06:41:34 -0700
Message-ID: <KDENKEIHMAKJMEHNCDFAMEFMCCAA.Barr.Hibbs@Nominum.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-reply-to: <20010809025938.C15655@arwen.cs.berkeley.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Importance: Normal
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Adam--

thank you for your well-considered work!  I have a few minor comments...

>     basic character:  Any of the 128 characters in the ASCII repertoire
>     (not to be confused with the integers or octets mapped to those
>     characters in the ASCII coded character set).
>
...ignoring the ability of DNS servers to transparently handle binary
labels, I think you really mean that a basic character is any one of the
characters which (a) has an associated glyph, (b) is the "non-printing"
space character, or (c) is a diacritical or punctuation symbol.  These
limitations, which essentially are required for characters to be
"human-readable," result in the set of characters being 31-127 of the whole
set.



>     host restrictions (applicable to any sequence of characters):
>     Contains no basic characters other than the letters, digits, and
>     hyphen-minus; and neither begins nor ends with hyphen-minus.
>
...this is not quite correct:  DNS does not make this restriction, although
I believe it is correct for the current standard for host names...

...also, I would observe that certain other characters, such as the
underscore ("_") are commonly permitted in URLs, which many non-experts find
indistinguishable from host names...


>     basic host label:  A basic label that satisfies the host
>     restrictions.  [This is the preexisting standard for host labels.]
>     basic domain name:  A sequence of basic labels (typically separated
>     by full-stop characters).  [This is the preexisting standard for
>     textual domain names.]
>
...one should be very clear that the label element separator (full-stop) is
the x'2E' character (".") and not something similar


> Goal 1 (motivated by facts 1-3 and conjecture 1):  Allow domain names to
> contain additional characters, while still allowing all domains to be
> referred to by all preexisting protocols, interfaces, software, etc.
>
> Requirement 1 (follows from goal 1):  Part of the preexisting namespace
> must be used to represent names containing additional characters,
> which requires altering the semantics of that part of the preexisting
> namespace.
>


--Barr





From owner-idn@ops.ietf.org  Thu Aug  9 10:37: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 KAA25436
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 10:37:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UqnJ-00068t-00
	for idn-data@psg.com; Thu, 09 Aug 2001 07:28:17 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15UqnI-00068n-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 07:28:16 -0700
Message-ID: <003001c120e0$a8382720$5b8d21d9@ietf.ignite.net>
From: "Edmon" <edmon@neteka.com>
To: "John C Klensin" <klensin@research.att.com>
Cc: <idn@ops.ietf.org>
References:  <002601c120c6$e2d4e0e0$5b8d21d9@ietf.ignite.net> <2109737.997347709@localhost>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Thu, 9 Aug 2001 10:36:15 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

From: "John C Klensin" <klensin@research.att.com>
> <edmon@neteka.com> wrote:
> > From: "Dan Ebert" <dan@enic.cc>
> >> It seems to me that it would be more confusing if TC/SC behaved
> >> differently for different TLDs.  One of the (I think
> >> beneficial) features of DNS is that the behavior is uniform
> >> across all TLDs (com works like net works like org ...)
> >
> > This is not true.  Registration restrictions differ from TLD to
> > TLD.
>
> But a query is interpreted independent of TLD.  And once the
> query is made, the name is resolved exactly the same way,
> regardless of the TLD.
>

You are right.  I should re-write my point:
You wont expect to go to the same place if you typed in abc.com vs abc.ca
so I dont think you would be too surprised to see that <SC>.com doesnt go to
the same place as <TC>.cn
Which means that TLD dependent SC=TC should not create any problem on a user
expectation stand point.
If you know that typing <SC>.cn and <TC>.cn goes to the same place, it will
happen no matter where you are connected to the network.
But that doesnt mean that <SC>.tld and <TC>.tld must therefore go to the
same place.
There should be no compelling user expectation for this to happen.
Edmon





From owner-idn@ops.ietf.org  Thu Aug  9 10:59: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 KAA26076
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 10:59:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Uqyn-0006hc-00
	for idn-data@psg.com; Thu, 09 Aug 2001 07:40:09 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15Uqym-0006hW-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 07:40:08 -0700
Message-ID: <003b01c120e2$515afde0$5b8d21d9@ietf.ignite.net>
From: "Edmon" <edmon@neteka.com>
To: <idn@ops.ietf.org>
Subject: [idn] Nameprep & Uniprep
Date: Thu, 9 Aug 2001 10:48:09 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0038_01C120C0.C79AB8A0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0038_01C120C0.C79AB8A0
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: quoted-printable

The Uniprep issue Paul brought up during the wg meeting I think is very =
interesting and personally, I have thought that there should be =
something like this all along.  Anyway, these are my thoughts:

Uniprep - Unicode Identifier Preparations
Nameprep - Domain Name Preparations

Uniprep will be a looser specification for general Unicode Identifiers.

Nameprep will be include mandatory compliance with Uniprep and then on =
top of it will include some or all of the following:
- additional mandatory preparations specifically for domain names (might =
not be required)
- Optional elements for zone operators
    - TS Conversion
    - Jpchar
    - Hangulchar
    - others...

In other words, most of the existing Nameprep might be moved to Uniprep, =
while Nameprep becomes an architectural document for prepping domain =
names which references to Uniprep and the other language specific =
mappings, plus possibly some additional preparations specifically for =
domain names.

Does this make sense?

Edmon

PS. perhaps Uniprep might better be discussed outside of the IDN =
wg...?...

------=_NextPart_000_0038_01C120C0.C79AB8A0
Content-Type: text/html;
	charset="big5"
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=3Dbig5">
<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>The Uniprep issue Paul brought up =
during the wg=20
meeting I think is very interesting and personally, I have thought that =
there=20
should be something like this all along.&nbsp; Anyway, these are my=20
thoughts:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Uniprep - Unicode Identifier=20
Preparations</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Nameprep - Domain Name =
Preparations</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Uniprep will be a looser specification =
for general=20
Unicode Identifiers.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Nameprep will be include mandatory =
compliance with=20
Uniprep and then on top of it will include some or all of the=20
following:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- additional mandatory preparations =
specifically=20
for domain names (might not be required)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- Optional elements for zone =
operators</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; - TS =
Conversion</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; - =
Jpchar</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; - =
Hangulchar</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; - =
others...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>In other words, most of the existing =
Nameprep might=20
be moved to Uniprep, while Nameprep becomes an architectural document =
for=20
prepping domain names which references to Uniprep and the other language =

specific mappings, plus possibly&nbsp;some additional preparations =
specifically=20
for domain names.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Does&nbsp;this make sense?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Edmon</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>PS. perhaps Uniprep might better be =
discussed=20
outside of the IDN wg...?...</FONT></DIV></BODY></HTML>

------=_NextPart_000_0038_01C120C0.C79AB8A0--




From owner-idn@ops.ietf.org  Thu Aug  9 11:14: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 LAA26599
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 11:14:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UrNa-0007uj-00
	for idn-data@psg.com; Thu, 09 Aug 2001 08:05:46 -0700
Received: from mail-blue.research.att.com ([135.207.30.102])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UrNZ-0007uS-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 08:05:45 -0700
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id EBF6D4CE15; Thu,  9 Aug 2001 11:05:44 -0400 (EDT)
Received: from host217-33-136-108.ietf.ignite.net (secure.research.att.com [135.207.24.10])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id LAA04226;
	Thu, 9 Aug 2001 11:05:44 -0400 (EDT)
Date: Thu, 09 Aug 2001 11:03:24 -0400
From: John C Klensin <klensin@research.att.com>
To: Edmon <edmon@neteka.com>
Cc: idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <9405368.997355004@host217-33-136-108.ietf.ignite.net>
In-Reply-To: <003001c120e0$a8382720$5b8d21d9@ietf.ignite.net>
References:  <003001c120e0$a8382720$5b8d21d9@ietf.ignite.net>
X-Mailer: Mulberry/2.1.0b3 (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, 09 August, 2001 10:36 -0400 Edmon
<edmon@neteka.com> wrote:

> Which means that TLD dependent SC=TC should not create any
> problem on a user expectation stand point.
> If you know that typing <SC>.cn and <TC>.cn goes to the same
> place, it will happen no matter where you are connected to the
> network. But that doesnt mean that <SC>.tld and <TC>.tld must
> therefore go to the same place.
> There should be no compelling user expectation for this to
> happen.

Edmon,

Let me say to you --and the WG-- what I said to Dave Crocker
after our exchange of comments at the mike.  It seems to me that
the WG is singing one song, but dancing to a different tune.
There are, I think, two, perfectly reasonable, positions:

	(i) The IDN effort is about identifiers and characters,
	not about languages or even strings.
	
	(ii) The IDN effort is about making it possible to put
	non-English words and phrases into the DNS, just as it is
	feasible to put English ones (with some constraints)
	there today.

Now, if we really believe the first, then it is not clear how
much of nameprep is needed (somewhat less, I think, although
probably not zero).  But discussions of SC/TC equivalence, Arabic
non-spacing break characters, similarity of characters with
non-similar glyphs between languages, distinctions between CJK
contexts, similar characters in different scripts or blocks, and
so on, are all irrelevant and inappropriate -- those are _all_
conversations about words, languages, and the way language
phrases are written.

But many people --I would suggest a majority of those who care
about the IDN issue, independent of those explicitly represented
in the WG-- are interested in words and languages.  To the extent
that they really represent the requirement for this work, all of
the issues excluded above are important and cannot be excluded.
Your assertion about "no compelling user expectation" is, in that
context, false: a compelling user expectation has been asserted
by CNNIC and others.   

And, if any of those language issues are part of the real
requirement, the WG is simply at risk of being irrelevant.  Not
wrong, but irrelevant.   If one reaches that conclusion, then
there is a procedural and responsibility question as to whether
the WG should (and can) report that it can't, within its charter,
do anything relevant or whether it is obligated to report
_something_ out anyway.

    john



From owner-idn@ops.ietf.org  Thu Aug  9 11:17: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 LAA26705
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 11:17:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UrRa-00087s-00
	for idn-data@psg.com; Thu, 09 Aug 2001 08:09:54 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UrRZ-00087P-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 08:09:53 -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 f79FXSQ13977;
	Thu, 9 Aug 2001 11:33:29 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010809111000.05caff20@127.0.0.1>
X-Sender: blanchet@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 09 Aug 2001 11:12:07 -0400
To: "Edmon" <edmon@neteka.com>, <idn@ops.ietf.org>
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: Re: [idn] Nameprep & Uniprep
In-Reply-To: <003b01c120e2$515afde0$5b8d21d9@ietf.ignite.net>
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

- i called it stringprep when we (Paul and I) first discuss it, but anyway.
- it is sure that this stringprep work is outside of the idn charter. it 
will be forwarded to the i18n ietf community (mailing list to be found 
later (there is some works on this these days)) and to the idn wg for 
information. but work and discussion on the generalized case will be done 
outside of the idn wg.
- only work related to idn is in the idn charter.

Marc.

At/À 10:48 2001-08-09 -0400, Edmon you wrote/vous écriviez:
>The Uniprep issue Paul brought up during the wg meeting I think is very 
>interesting and personally, I have thought that there should be something 
>like this all along.  Anyway, these are my thoughts:
>
>Uniprep - Unicode Identifier Preparations
>Nameprep - Domain Name Preparations
>
>Uniprep will be a looser specification for general Unicode Identifiers.
>
>Nameprep will be include mandatory compliance with Uniprep and then on top 
>of it will include some or all of the following:
>- additional mandatory preparations specifically for domain names (might 
>not be required)
>- Optional elements for zone operators
>     - TS Conversion
>     - Jpchar
>     - Hangulchar
>     - others...
>
>In other words, most of the existing Nameprep might be moved to Uniprep, 
>while Nameprep becomes an architectural document for prepping domain names 
>which references to Uniprep and the other language specific mappings, plus 
>possibly some additional preparations specifically for domain names.
>
>Does this make sense?
>
>Edmon
>
>PS. perhaps Uniprep might better be discussed outside of the IDN wg...?...





From owner-idn@ops.ietf.org  Thu Aug  9 11:48: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 LAA27992
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 11:48:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UrrY-0009Q8-00
	for idn-data@psg.com; Thu, 09 Aug 2001 08:36:44 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15UrrX-0009Pp-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 08:36:43 -0700
Message-ID: <009501c120ea$31aad580$5b8d21d9@ietf.ignite.net>
From: "Edmon" <edmon@neteka.com>
To: "John C Klensin" <klensin@research.att.com>
Cc: <idn@ops.ietf.org>
References:  <003001c120e0$a8382720$5b8d21d9@ietf.ignite.net> <9405368.997355004@host217-33-136-108.ietf.ignite.net>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Thu, 9 Aug 2001 11:44:33 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi John,

I completely concur with you, perhaps you misunderstand my statement.  What
I am saying is that if CNNIC believes that there is compelling user
expectation within their registry to have SC=TC, then they should absolutely
implement it.  However, if another TLD say .tld believes that preserving
TC/SC information is important, then they will have the option to do so.
The registrant will always have the option to make them equivalent.

I also concur that IDN should strive to solve some language issues, however,
I also think that it is the IDN "implementations" that should solve the
problem and not the "core protocol" which we should concern ourselves with
at this moment.

Edmon


> Your assertion about "no compelling user expectation" is, in that
> context, false: a compelling user expectation has been asserted
> by CNNIC and others.
>
> And, if any of those language issues are part of the real
> requirement, the WG is simply at risk of being irrelevant.  Not
> wrong, but irrelevant.   If one reaches that conclusion, then
> there is a procedural and responsibility question as to whether
> the WG should (and can) report that it can't, within its charter,
> do anything relevant or whether it is obligated to report
> _something_ out anyway.
>





From owner-idn@ops.ietf.org  Thu Aug  9 11:52: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 LAA28142
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 11:52:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Urwt-0009l9-00
	for idn-data@psg.com; Thu, 09 Aug 2001 08:42:15 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15Urws-0009l1-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 08:42:14 -0700
Message-ID: <009b01c120ea$f6182c60$5b8d21d9@ietf.ignite.net>
From: "Edmon" <edmon@neteka.com>
To: "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>, <idn@ops.ietf.org>
References: <5.1.0.14.1.20010809111000.05caff20@127.0.0.1>
Subject: Re: [idn] Nameprep & Uniprep
Date: Thu, 9 Aug 2001 11:50: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

From: "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>
> - it is sure that this stringprep work is outside of the idn charter. it
> will be forwarded to the i18n ietf community (mailing list to be found
> later (there is some works on this these days)) and to the idn wg for
> information. but work and discussion on the generalized case will be done
> outside of the idn wg.

This is fine and great.  Then do we want to revisit the Nameprep document to
change it into an architecture doc that would reference String/Uniprep
(personally I like the name uniprep more...)?  I think this only makes sense
as we know that there would be a universal preping mechanism.

> >Anyway, these are my thoughts:
> >
> >Uniprep - Unicode Identifier Preparations
> >Nameprep - Domain Name Preparations
> >
> >Uniprep will be a looser specification for general Unicode Identifiers.
> >
> >Nameprep will be include mandatory compliance with Uniprep and then on
top
> >of it will include some or all of the following:
> >- additional mandatory preparations specifically for domain names (might
> >not be required)
> >- Optional elements for zone operators
> >     - TS Conversion
> >     - Jpchar
> >     - Hangulchar
> >     - others...
> >
> >In other words, most of the existing Nameprep might be moved to Uniprep,
> >while Nameprep becomes an architectural document for prepping domain
names
> >which references to Uniprep and the other language specific mappings,
plus
> >possibly some additional preparations specifically for domain names.
> >
> >Does this make sense?
> >
> >Edmon
> >
> >PS. perhaps Uniprep might better be discussed outside of the IDN
wg...?...
>




From owner-idn@ops.ietf.org  Thu Aug  9 12:14: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 MAA29009
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 12:14:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UsHR-000AtO-00
	for idn-data@psg.com; Thu, 09 Aug 2001 09:03:29 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15UsHQ-000AtI-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 09:03:28 -0700
Received: (qmail 10731 invoked by uid 1001); 9 Aug 2001 15:36:59 -0000
Date: 9 Aug 2001 15:36:59 -0000
Message-ID: <20010809153659.5511.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] Re: how well UTF-8 works
References: <E15UjXY-000BsJ-00@psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Eric A. Hall writes:
> Two of the tests were able to open the target URL but they didn't
> display the domain name properly, which is not a win as far as Joe
> Sixpack goes.

Sounds just like ACE.

The difference, of course, is that only a small amount of code has to be
fixed to make UTF-8 work perfectly, while ACE requires massive upgrades
in literally _thousands_ of programs.

The main argument for ACE was the ACE myth, which says that ACE can be
safely deployed before all the software has been upgraded. That myth has
already been dispelled.

---Dan



From owner-idn@ops.ietf.org  Thu Aug  9 12:15: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 MAA29021
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 12:14:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UsEF-000Ahe-00
	for idn-data@psg.com; Thu, 09 Aug 2001 09:00:11 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UsEE-000AhN-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 09:00:11 -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 f79GNlQ14888;
	Thu, 9 Aug 2001 12:23:47 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010809115604.06145f70@127.0.0.1>
X-Sender: blanchet@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 09 Aug 2001 11:57:02 -0400
To: "Edmon" <edmon@neteka.com>, <idn@ops.ietf.org>
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: Re: [idn] Nameprep & Uniprep
In-Reply-To: <009b01c120ea$f6182c60$5b8d21d9@ietf.ignite.net>
References: <5.1.0.14.1.20010809111000.05caff20@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

At/À 11:50 2001-08-09 -0400, Edmon you wrote/vous écriviez:
>From: "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>
> > - it is sure that this stringprep work is outside of the idn charter. it
> > will be forwarded to the i18n ietf community (mailing list to be found
> > later (there is some works on this these days)) and to the idn wg for
> > information. but work and discussion on the generalized case will be done
> > outside of the idn wg.
>
>This is fine and great.  Then do we want to revisit the Nameprep document to
>change it into an architecture doc that would reference String/Uniprep
>(personally I like the name uniprep more...)?  I think this only makes sense
>as we know that there would be a universal preping mechanism.

- uniprep/stringprep is a larger problem that may take a lot of time to do 
and will consider things that are not related to idn.
- I think stringprep should not be in sync with the idn work.

Marc.



> > >Anyway, these are my thoughts:
> > >
> > >Uniprep - Unicode Identifier Preparations
> > >Nameprep - Domain Name Preparations
> > >
> > >Uniprep will be a looser specification for general Unicode Identifiers.
> > >
> > >Nameprep will be include mandatory compliance with Uniprep and then on
>top
> > >of it will include some or all of the following:
> > >- additional mandatory preparations specifically for domain names (might
> > >not be required)
> > >- Optional elements for zone operators
> > >     - TS Conversion
> > >     - Jpchar
> > >     - Hangulchar
> > >     - others...
> > >
> > >In other words, most of the existing Nameprep might be moved to Uniprep,
> > >while Nameprep becomes an architectural document for prepping domain
>names
> > >which references to Uniprep and the other language specific mappings,
>plus
> > >possibly some additional preparations specifically for domain names.
> > >
> > >Does this make sense?
> > >
> > >Edmon
> > >
> > >PS. perhaps Uniprep might better be discussed outside of the IDN
>wg...?...
> >





From owner-idn@ops.ietf.org  Thu Aug  9 12:15: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 MAA29055
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 12:15:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UsBr-000AZn-00
	for idn-data@psg.com; Thu, 09 Aug 2001 08:57:43 -0700
Received: from lobo.enic.cc ([209.237.72.66] helo=mail.enic.cc)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UsBr-000AZh-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 08:57:43 -0700
Received: from enic.cc (tailback.nic.cc [209.237.72.17])
	by mail.enic.cc (Postfix) with ESMTP
	id DF3216A901; Thu,  9 Aug 2001 08:57:42 -0700 (PDT)
Message-ID: <3B72B2F6.735380F3@enic.cc>
Date: Thu, 09 Aug 2001 08:57:42 -0700
From: Dan Ebert <dan@enic.cc>
Organization: eNIC Corporation
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Edmon <edmon@neteka.com>
Cc: Dave Crocker <dhc@dcrocker.net>, John C Klensin <klensin@research.att.com>,
        idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
References: <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net> <13749451.997252461@host217-33-136-108.ietf.ignite.net> <5.1.0.14.2.20010808143501.03f52140@dcrocker.net> <007601c1202e$478d1fa0$5b8d21d9@ietf.ignite.net> <3B7179C0.D0C4D814@enic.cc> <002601c120c6$e2d4e0e0$5b8d21d9@ietf.ignite.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Edmon wrote:
> 
> From: "Dan Ebert" <dan@enic.cc>
> > It seems to me that it would be more confusing if TC/SC behaved
> > differently for different TLDs.  One of the (I think beneficial)
> > features of DNS is that the behavior is uniform across all TLDs (com
> > works like net works like org ...)
> 
> This is not true.  Registration restrictions differ from TLD to TLD.
> 

I should have been more specific.  I was thinking in terms of
resolution, not registration.
I just think it could be confusing if each TLD makes up their own rules
regarding resolution.

i.e. <TC>.tld1 may-or-may-not-be-equivalent-to <SC>.tld1
 but <TC>.tld2 is-always-equivalent-to <SC>.tld2

> > I would suggest that it may be a
> > better idea to use have a script on the web server look at user IP or
> > browser environment variable to determine what page should be displayed
> > (or redirect to a different server).
> >
> 
> What about emails?
> 

Good point.

> Edmon

-- 
Dan Ebert      <dan@enic.cc>       eNIC Corporation
------------------------------------------------------------
I've had a perfectly wonderful evening. But this wasn't it.
   -- Groucho Marx



From owner-idn@ops.ietf.org  Thu Aug  9 12:30: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 MAA29517
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 12:30:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UsV1-000BgT-00
	for idn-data@psg.com; Thu, 09 Aug 2001 09:17:31 -0700
Received: from mail-blue.research.att.com ([135.207.30.102])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UsV0-000BgM-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 09:17:30 -0700
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 764FC4CE53; Thu,  9 Aug 2001 12:17:29 -0400 (EDT)
Received: from host217-33-136-108.ietf.ignite.net (secure.research.att.com [135.207.24.10])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id MAA14441;
	Thu, 9 Aug 2001 12:17:28 -0400 (EDT)
Date: Thu, 09 Aug 2001 12:01:42 -0400
From: John C Klensin <klensin@research.att.com>
To: Edmon <edmon@neteka.com>
Cc: idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <12902168.997358502@localhost>
In-Reply-To: <009501c120ea$31aad580$5b8d21d9@ietf.ignite.net>
References:  <009501c120ea$31aad580$5b8d21d9@ietf.ignite.net>
X-Mailer: Mulberry/2.1.0b3 (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, 09 August, 2001 11:44 -0400 Edmon
<edmon@neteka.com> wrote:

> Hi John,
> 
> I completely concur with you, perhaps you misunderstand my
> statement.  What I am saying is that if CNNIC believes that
> there is compelling user expectation within their registry to
> have SC=TC, then they should absolutely implement it.  

And they should somehow to contrive to be sure that no records
are cached outside China, where other rules would apply as a
query is applied to a cached record?   I continue to be afraid
that the choices are between 

	-- the whole DNS using the same procedures or
	
	-- fragmenting the network

Now, if CNNIC says, "ok, we are going to register only SC, and to
get TC translations, you need to use our translating software 
However, if you have client software that doesn't use our
translation software and tables, you had better make queries in
SC, and reverse mapping records are going to return SC no matter
what you do", that would work with your model.  But I haven't
heard from them going that route is an accceptable model.

> if another TLD say .tld believes that preserving TC/SC
> information is important, then they will have the option to do
> so. The registrant will always have the option to make them
> equivalent.

As I think others have pointed out, this works only if you assume
that TC/SC equivalence can be solved by exactly two
registrations, one of each.  As soon as there are combinations of
the two forms, the combinatorics get you in major ways.

> I also concur that IDN should strive to solve some language
> issues, however, I also think that it is the IDN
> "implementations" that should solve the problem and not the
> "core protocol" which we should concern ourselves with at this
> moment.

If language issues are left to "implementations", we almost
certainly end up with different implementations interpreting the
same string in different ways and resolving it to different
targets.  That is, in essence, the fragmentation problem.
 
     john




From owner-idn@ops.ietf.org  Thu Aug  9 12:33: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 MAA29574
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 12:33:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UscA-000C5Q-00
	for idn-data@psg.com; Thu, 09 Aug 2001 09:24:54 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15Usc9-000C5K-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 09:24:53 -0700
Message-ID: <001701c120f0$f3b74a40$5b8d21d9@ietf.ignite.net>
From: "Edmon" <edmon@neteka.com>
To: <idn@ops.ietf.org>, "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>
References: <5.1.0.14.1.20010809111000.05caff20@127.0.0.1> <5.1.0.14.1.20010809115604.06145f70@127.0.0.1>
Subject: Re: [idn] Nameprep & Uniprep
Date: Thu, 9 Aug 2001 12:32:54 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

From: "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>
> - uniprep/stringprep is a larger problem that may take a lot of time to do
> and will consider things that are not related to idn.
> - I think stringprep should not be in sync with the idn work.
>

But doesnt that defeat part of the purpose for uniprep as being a universal
prep mechanism that one of the most important identifiers on the internet,
the DNS doesnt even refer to it or use it?
I understand that uniprep is a larger problem, and I also understand the
time pressure seemingly surrounding this wg, but I think it is important
that ONCE it actually is there, it will be used by the DNS.  We should have
some provisions for it.  That is my main point.
Edmon

> Marc.
>
>
>
> > > >Anyway, these are my thoughts:
> > > >
> > > >Uniprep - Unicode Identifier Preparations
> > > >Nameprep - Domain Name Preparations
> > > >
> > > >Uniprep will be a looser specification for general Unicode
Identifiers.
> > > >
> > > >Nameprep will be include mandatory compliance with Uniprep and then
on
> >top
> > > >of it will include some or all of the following:
> > > >- additional mandatory preparations specifically for domain names
(might
> > > >not be required)
> > > >- Optional elements for zone operators
> > > >     - TS Conversion
> > > >     - Jpchar
> > > >     - Hangulchar
> > > >     - others...
> > > >
> > > >In other words, most of the existing Nameprep might be moved to
Uniprep,
> > > >while Nameprep becomes an architectural document for prepping domain
> >names
> > > >which references to Uniprep and the other language specific mappings,
> >plus
> > > >possibly some additional preparations specifically for domain names.
> > > >
> > > >Does this make sense?
> > > >
> > > >Edmon
> > > >
> > > >PS. perhaps Uniprep might better be discussed outside of the IDN
> >wg...?...
> > >
>




From owner-idn@ops.ietf.org  Thu Aug  9 13:14: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 NAA00548
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 13:14:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UtF9-000E5Q-00
	for idn-data@psg.com; Thu, 09 Aug 2001 10:05:11 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UtF8-000E5F-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 10:05:10 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA22764;
        Thu, 9 Aug 2001 13:04:59 -0400 (EDT)
Message-Id: <200108091704.NAA22764@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: John C Klensin <klensin@research.att.com>
cc: Edmon <edmon@neteka.com>, idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence 
In-reply-to: Your message of "Thu, 09 Aug 2001 12:01:42 EDT."
             <12902168.997358502@localhost> 
Date: Thu, 09 Aug 2001 13:04:59 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > I completely concur with you, perhaps you misunderstand my
> > statement.  What I am saying is that if CNNIC believes that
> > there is compelling user expectation within their registry to
> > have SC=TC, then they should absolutely implement it.
> 
> And they should somehow to contrive to be sure that no records
> are cached outside China, where other rules would apply as a
> query is applied to a cached record?   I continue to be afraid
> that the choices are between
> 
>         -- the whole DNS using the same procedures or
> 
>         -- fragmenting the network
> 

I don't think that's an accurate characterization.   As a practical
manner, any DNS zone can create multiple names within that zone that
resolve to equivalent RRs, and any DNS zone can establish procedures
for keeping those names consistent, without affecting the DNS protocol
or the applications that use it.  Similarly, if two zones are controlled
by the same party, that party can maintain those zones such that
label X in zone A and label X' in zone B resolve to an equivalent set of 
RRs, and the party controlling those zones can keep those two zones 
consistent with one another.

I don't see this as inherently undesirable.  True, caches will not recognize 
that these zones are equivalent, but this mainly serves to increase lookup 
delay for names in those zones and to increase load on the authoritative 
servers for those zones.  Each zone can decide for itself whether it's 
worth the additional delay and cost.

Nothing that IDN does is going to change the ability to create multiple
names that produce equivalent RRs.  Nor do I think that IDN can build a 
better way to solve this problem.  We certainly don't want to embed 
knowledge of SC/TC equivalence into applications, DNS libraries, or 
DNS servers.

Users can tell the difference between TC and SC.  So they will be able
to figure out that even if TC and SC names are equivalent within some
particular TLD, they are not necessarily equivalent elsewhere.

Bascially I think this issue is out of scope for IDN, because you can't 
expect a networking protocol to fix all naming equivalence problems in 
all languages.

Keith



From owner-idn@ops.ietf.org  Thu Aug  9 13:55: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 NAA01572
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 13:55:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Utpy-000G6S-00
	for idn-data@psg.com; Thu, 09 Aug 2001 10:43:14 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15Utpx-000G6K-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 10:43:13 -0700
Message-ID: <005101c120fb$db651700$5b8d21d9@ietf.ignite.net>
From: "Edmon" <edmon@neteka.com>
To: "John C Klensin" <klensin@research.att.com>
Cc: <idn@ops.ietf.org>
References:  <009501c120ea$31aad580$5b8d21d9@ietf.ignite.net> <12902168.997358502@localhost>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Thu, 9 Aug 2001 13:50:52 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John,

> And they should somehow to contrive to be sure that no records
> are cached outside China, where other rules would apply as a
> query is applied to a cached record?   I continue to be afraid
> that the choices are between
>
They do not have to contrive.  If a UserA types in <TC>.cn in Finland, the
.cn registry will do the TC=SC folding and respond saying that <TC>.cn=IP
and this will be cached in the Finland ISP resolver.  Now if a UserB types
in <TC>.cn, this could be responded using the cache.  If a User C types in
<SC>.cn, then the request will reach CNNIC and will resolve <SC>=IP and this
will be cached in the Finland ISP resolver.  This does not fragment the DNS.

> Now, if CNNIC says, "ok, we are going to register only SC, and to
> get TC translations, you need to use our translating software
> However, if you have client software that doesn't use our
> translation software and tables, you had better make queries in
> SC, and reverse mapping records are going to return SC no matter
> what you do", that would work with your model.  But I haven't
> heard from them going that route is an accceptable model.

The TC=SC mechanism could be done on the TLD server end.

> As I think others have pointed out, this works only if you assume
> that TC/SC equivalence can be solved by exactly two
> registrations, one of each.  As soon as there are combinations of
> the two forms, the combinatorics get you in major ways.

If you employ a server-end mapping mechanism, there would be only one
registration.

> If language issues are left to "implementations", we almost
> certainly end up with different implementations interpreting the
> same string in different ways and resolving it to different
> targets.  That is, in essence, the fragmentation problem.
>

I think I need to rephrase.  What I meant is that language issues should be
dealt with in a higher layer than the core DNS, that is implementation of
applications that will access the DNS.  Perhaps an application when prompted
with a particular name will perform multiple DNS requests to determine the
closest semantic representation.  If more than one is found, then it would
prompt the user to choose.  This is just a very very crude idea, but my
point is that linguistic/semantic issues should and could be dealt with in a
higher layer.

Edmon




From owner-idn@ops.ietf.org  Thu Aug  9 14: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 OAA01850
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 14:12:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Uu6f-000H0Q-00
	for idn-data@psg.com; Thu, 09 Aug 2001 11:00:29 -0700
Received: from lobo.enic.cc ([209.237.72.66] helo=mail.enic.cc)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Uu6f-000H0K-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 11:00:29 -0700
Received: from enic.cc (tailback.nic.cc [209.237.72.17])
	by mail.enic.cc (Postfix) with ESMTP
	id B20CF6A927; Thu,  9 Aug 2001 11:00:28 -0700 (PDT)
Message-ID: <3B72CFBC.2E0DFF2F@enic.cc>
Date: Thu, 09 Aug 2001 11:00:28 -0700
From: Dan Ebert <dan@enic.cc>
Organization: eNIC Corporation
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Edmon <edmon@neteka.com>
Cc: John C Klensin <klensin@research.att.com>, idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
References: <009501c120ea$31aad580$5b8d21d9@ietf.ignite.net> <12902168.997358502@localhost> <005101c120fb$db651700$5b8d21d9@ietf.ignite.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Edmon wrote:
> 

<snip>

> 
> The TC=SC mechanism could be done on the TLD server end.
> 
> > As I think others have pointed out, this works only if you assume
> > that TC/SC equivalence can be solved by exactly two
> > registrations, one of each.  As soon as there are combinations of
> > the two forms, the combinatorics get you in major ways.
> 
> If you employ a server-end mapping mechanism, there would be only one
> registration.

Yes, but if nameprep is done on the client side wouldn't that cause
problems?

> Edmon

-- 
Dan Ebert      <dan@enic.cc>       eNIC Corporation
------------------------------------------------------------
I've had a perfectly wonderful evening. But this wasn't it.
   -- Groucho Marx



From owner-idn@ops.ietf.org  Thu Aug  9 14:47: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 OAA02742
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 14:47:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UuKv-000HkC-00
	for idn-data@psg.com; Thu, 09 Aug 2001 11:15:13 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UuKu-000Hk3-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 11:15:12 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+3nwGBQ7c9H2AhUCMPzzlVthTpEapuRcA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCEXK4XQ; Thu, 09 Aug 2001 14:14:33 EDT
To: edmon@neteka.com
Cc: klensin@research.att.com, idn@ops.ietf.org
Date: Thu, 9 Aug 2001 11:09:07 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010809.113129.-789831.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-39,41,43,45-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



On Thu, 9 Aug 2001 10:36:15 -0400 "Edmon" <edmon@neteka.com> writes:
> From: "John C Klensin" <klensin@research.att.com>
> > <edmon@neteka.com> wrote:
> > > From: "Dan Ebert" <dan@enic.cc>
> > >> It seems to me that it would be more confusing if TC/SC behaved
> > >> differently for different TLDs.  One of the (I think
> > >> beneficial) features of DNS is that the behavior is uniform
> > >> across all TLDs (com works like net works like org ...)
> > >
> > > This is not true.  Registration restrictions differ from TLD to
> > > TLD.
> >
> > But a query is interpreted independent of TLD.  And once the
> > query is made, the name is resolved exactly the same way,
> > regardless of the TLD.
> >
> 
> You are right.  I should re-write my point:
> You wont expect to go to the same place if you typed in abc.com vs 
> abc.ca
> so I dont think you would be too surprised to see that <SC>.com 
> doesnt go to
> the same place as <TC>.cn
> Which means that TLD dependent SC=TC should not create any problem 
> on a user
> expectation stand point.
> If you know that typing <SC>.cn and <TC>.cn goes to the same place, 
> it will
> happen no matter where you are connected to the network.
> But that doesnt mean that <SC>.tld and <TC>.tld must therefore go to 
> the
> same place.
> There should be no compelling user expectation for this to happen.
> Edmon
> 
> 
> 

This is not true!  As a Chinese, I do want my hostname to go to the same
place
no matter what the system, either BIG5, GBK, or Unicoded, I've happent to

have at hand! This is the whole point of the IDN.  If I want two places,
I can
take care of that by registering at two places.

Liana



From owner-idn@ops.ietf.org  Thu Aug  9 16:08: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 QAA04398
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 16:08:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Uvw0-000NsP-00
	for idn-data@psg.com; Thu, 09 Aug 2001 12:57:36 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>
Cc: <idn@ops.ietf.org>
Subject: Re: [idn] Transparent vs. ACE representations (was We are
Message-Id: <E15Uvw0-000NsP-00@psg.com>
Date: Thu, 09 Aug 2001 12:57:36 -0700

quibbling about WHAT?)
Date: Thu, 9 Aug 2001 09:04:29 -0500
Organization: EHS Company
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> >Suppose for the sake of argument that the message had contained
> >characters outside the US-ASCII repertoire (in a domain name or
> >elsewhere).
>
> If the text switches from one character set to another, then no, it is
> unlikely the processing software will handle that well.

Exactly. Text that contains UTF-8 IDNs is likely to be stored as an
UTF-8 body part. Conversely, text that contains ACE IDNs (which must be
transliterated) is not likely to be stored as an ACE body part since ACE
is not suitable for MIME.

> The real point is that you appear to be assuming a much more
simplified
> and  consistent processing environment for characters, across
> applications, than  actually exists.

Conversely, you appear to be assuming that everybody will want to write
ACE-exception-handling code that scans through body parts, tries to find
a string that looks like ACE, transliterate it, and redisplay the body
part. Give me a break.

Think about this: nobody will be able to explain how ACE works over
email. Everytime you give an example, the software transliterates it. Oh
so now we need exception handling for the exception handling.

ACE is needed for backwards compatibility. That is totally separate from
whether or not it is useful or usable or good for future usage models.
You shouldn't get them confused.








From owner-idn@ops.ietf.org  Thu Aug  9 17:34: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 RAA06032
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 17:34:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UxDg-0002Iv-00
	for idn-data@psg.com; Thu, 09 Aug 2001 14:19:56 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15UxDf-0002Ip-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 14:19:55 -0700
Received: (qmail 25828 invoked by uid 1001); 9 Aug 2001 20:26:35 -0000
Date: 9 Aug 2001 20:26:35 -0000
Message-ID: <20010809202635.7814.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] A UTF-8 test for mail clients
References: <E15UXFG-000PEi-00@psg.com> <200108081748.NAA15343@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:
> addresses are defined to be ASCII in both RFC 822 and RFC 2822

Wake up, Keith! We're changing this definition. The whole point of IDN
is to allow _non-ASCII_ characters, such as the Greek pi, in addresses.

Which character encoding are we going to use instead of ASCII? Maybe
UTF-8. Maybe ACE-FUBAR-8675309. Either way, the interpretation of
address bytes as ASCII will be obsolete.

> My mail client treats the CF and 80 as invalid characters when composing
> the reply.

Thanks for the data point. Are you still using MH 6.8.4? Have you tried
the new MH?

---Dan



From owner-idn@ops.ietf.org  Thu Aug  9 19: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 TAA07340
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 19:21:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Uyzb-0007zL-00
	for idn-data@psg.com; Thu, 09 Aug 2001 16:13:31 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15UyzZ-0007z4-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 16:13:30 -0700
Received: from zetnet.co.uk (man-s232.dialup.zetnet.co.uk [194.247.45.103])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f79NDL428616;
	Fri, 10 Aug 2001 00:13:21 +0100
Message-ID: <3B731891.8258BDC9@zetnet.co.uk>
Date: Fri, 10 Aug 2001 00:11:13 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: Dave Crocker <dhc@dcrocker.net>, idn@ops.ietf.org
Subject: Re: [idn] Transparent vs. ACE representations
References: <5.1.0.14.2.20010729172557.0302f008@brandenburg.com>
	 <5.1.0.14.2.20010803135104.032186f0@brandenburg.com> <5.1.0.14.2.20010809101843.034d1eb0@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:
> At 02:13 AM 8/9/2001, David Hopwood wrote:
> >But, you may say, that encoding wasn't UTF-8. Doesn't matter.
> 
> well, actually it does.
> 
> >Suppose for the sake of argument that the message had contained characters
> >outside the US-ASCII repertoire (in a domain name or elsewhere).
> 
> If the text switches from one character set to another,

When did I say anything about switching charsets within a text? The example
you chose didn't support your argument because the message only contained
characters from the US-ASCII repertoire (and so it obviously wouldn't show
up differences between any IDN proposals). I'm talking about a message that
includes some abstract characters with Unicode code points > 0x7F.

> then no, it is unlikely the processing software will handle that well.
> If you mean that the text is all in the UTF-8, then, no, it isn't.

If I had meant that, I would have said that.

> Mine is in ASCII. Hence your suggestion means we would have mixed Ascii, UTF-8.

Mixed ASCII and UTF-8 is identical to UTF-8, which is one reason why it would
have been much clearer for you to use a different example.

More generally, the sending MUA can choose any single encoding for a MIME text
part, but a properly internationalized MUA should always choose an encoding
that is able to represent all the characters that are used in the text. [It's
possible to use multiparts to switch charsets in a somewhat klunky fashion,
but practically no user agents actually do that. If a compliant receiving MUA
did come across such a message, it would interpret each part according to its
tagged charset, though, so there would be no problem.]

For example, if the message contains only characters from the ISO-8859-1
repertoire, then a compliant MUA might send it as "text/plain; charset=iso-8859-1".
In that case a transparent representation means that any domain names, email
addresses, URIs, etc. will also be ISO-8859-1. The receiving internationalized
MUA transcodes the message into a UTF, so that if the user clicks on a link or
cuts/copies text from the message, it will be encoded correctly. In no case
does a MUA (or any other application) have to do any additional work in order
to display transparently represented domain names properly.

> The real point is that you appear to be assuming a much more simplified and
> consistent processing environment for characters, across applications, than
> actually exists.

I'm assuming that users that want internationalization support will use
software that provides that support. All the proposals assume that.

> >Call a domain name representation within
> >some surrounding text (or other protocol elements) "transparent", if the
> >representation is of a character string such that each character in the
> >string stands for the same character in the domain name.
> 
> By that definition, UTF-8 is not transparent.

Again you're missing the point. Transparency is a property of "a domain name
representation within some surrounding text"; it's not dependent on which
charset is used to represent that text. For any charset X, a domain name
encoded using X is transparent if it appears in a message or protocol that
also uses X. That property never applies to a name encoded as ACE, because
ACE will never be used as a general-purpose charset.

[...]
> >The thesis behind the ACE-only proposals seems to be that most existing
> >protocols, formats, and implementations assume that domain names only
> >use US-ASCII characters, and so using a non-ASCII representation will
> >break them. In the vast majority of cases, that simply isn't true
> 
> The premise has been present in the design of Internet protocols from the
> beginning.  Much has changed since then, but not everything.
> 
> The premise that all software will correctly process UTF-8 has been
> demonstrated to be false.

My argument doesn't depend on all software being able to correctly process
UTF-8. No software correctly processes ACE at the moment. Remember that
the point of IDNs is to be able to enter and display non-ASCII characters
correctly; if that doesn't work, then a more meaningful ASCII alias for the
domain might as well have been used instead.

> > > As to predictions of the future, well, they are always wrong.
> >
> >That's obvious nonsense. It is a perfectly safe prediction that the
> >default encoding (often the only encoding) used in almost all Internet
> >protocols in the near future will be UTF-8.
> 
> I do not know how many such confident predictions of the future you have
> suffered through, but many of us have watched them made repeatedly over the
> last 25 years and, I am sorry to say, they are usually incorrect.  Not
> always, no.  But frequently.

Congratulations; you've gone from "always" to "usually", then "frequently",
all in one paragraph. "frequently" is much better, although I would say
"sometimes". There is also a reporting bias to be taken into account: cases
where the prediction was wrong are more interesting, so they get cited more
often. Confident predictions of the near future that turn out to be absolutely
correct are rarely commented on.

In any case, my statement stands: "It is a perfectly safe prediction that
the default encoding (often the only encoding) used in almost all Internet
protocols in the near future will be UTF-8." Note that the effect of BCP 18
is to block progression on the standards track of new protocols and protocol
updates that don't allow UTF-8, unless an exemption is granted.

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

iQEVAwUBO3MYgzkCAxeYt5gVAQG3QAf+IsBl2Nju0VOaTByWUMndLcsMbM+AZhIB
q29heZ9jRP82Eodcqhep9o0E6DKEAtWAnw5e7RztMdYuQJO+FHnteuk6rV4hAO3N
wFpm1QyrdXqOo4RJMlspryRYk5kHnpO5AxF3EHuFIBjQNoq/SfZ8j019A7XUVk6z
99AQu6GL1qog0ByOkr38lOiSeTEadpinfDZ23ujXMvngHc3NDINAszoN27izc79S
WU3rzpmOkMCu5e+hr2KLK4XkU5EMoJensqtwFghNL3fOZZun4Dy7Tb3gbBOXYDK4
2LWCwjuYC1qcnQBEuT3/lyb8J41GdnCkKYu/hMvpY7W1udeLVykXzg==
=qIJ/
-----END PGP SIGNATURE-----




From owner-idn@ops.ietf.org  Thu Aug  9 19:32: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 TAA07513
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 19:32:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Uz71-0008Tr-00
	for idn-data@psg.com; Thu, 09 Aug 2001 16:21:11 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Uz70-0008Tk-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 16:21:10 -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 f79Nj0Q21186
	for <idn@ops.ietf.org>; Thu, 9 Aug 2001 19:45:01 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010809190611.0214bc68@127.0.0.1>
X-Sender: blanchet@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 09 Aug 2001 19:07:13 -0400
To: idn@ops.ietf.org
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: [idn] meeting presentations online
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hi,
  meeting presentations are on the wg web page: 
http://www.i-d-n.net/#meetings. Meeting notes should be sent as soon as 
possible.

Marc.




From owner-idn@ops.ietf.org  Thu Aug  9 19:35: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 TAA07545
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 19:35:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15UzFi-0008zp-00
	for idn-data@psg.com; Thu, 09 Aug 2001 16:30:10 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15UzFd-0008zO-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 16:30:10 -0700
Received: (qmail 19213 invoked by uid 1001); 9 Aug 2001 23:10:52 -0000
Date: 9 Aug 2001 23:10:52 -0000
Message-ID: <20010809231052.23796.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] rederivation of an IDN architecture
References: <20010809025938.C15655@arwen.cs.berkeley.edu> <20010809063836.18303.qmail@cr.yp.to> <1130379.997346397@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:
> you claim that a standard is not needed, as software already "work"

Liar. I have consistently stated that some software needs to be upgraded
for UTF-8. The reason I support this approach is that it will give us
working IDNs much sooner and at much lower cost than the ACE approach.

---Dan



From owner-idn@ops.ietf.org  Thu Aug  9 20:59: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 UAA08432
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 20:58:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15V0U8-000D6U-00
	for idn-data@psg.com; Thu, 09 Aug 2001 17:49:08 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15V0U7-000D6L-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 17:49:07 -0700
Received: from amc by nicemice.net with local (Exim 3.31 #1 (Debian))
	id 15V0U6-0005Rh-00
	for <idn@ops.ietf.org>; Thu, 09 Aug 2001 17:49:06 -0700
Date: Fri, 10 Aug 2001 00:49:06 +0000
From: "Adam M. Costello" <amc@cs.berkeley.edu>
To: idn@ops.ietf.org
Subject: Re: [idn] rederivation of an IDN architecture
Message-ID: <20010810004906.F19975@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <KDENKEIHMAKJMEHNCDFAMEFMCCAA.Barr.Hibbs@Nominum.com> <20010809063836.18303.qmail@cr.yp.to>
User-Agent: Mutt/1.3.18i
Sender: owner-idn@ops.ietf.org
Precedence: bulk

"D. J. Bernstein" <djb@cr.yp.to> wrote:

> > Goal 1
> 
> Here you've lost sight of the goal of actually DISPLAYING THE NAMES
> PROPERLY.

That's goal 7.

Barr Hibbs <Barr.Hibbs@Nominum.com> wrote:

> >     basic character:  Any of the 128 characters in the ASCII
> >     repertoire
>
> I think you really mean that a basic character is any one of
> the characters which (a) has an associated glyph, (b) is the
> "non-printing" space character, or (c) is a diacritical or punctuation
> symbol.

In this section I was merely trying to write formal definitions of
existing standards.  The existing domain name standards talk about ASCII
characters and the more limited set of LDH characters, but as far as I
know they do not mention the set of printable ASCII characters.

> >     host restrictions (applicable to any sequence of characters):
> >     Contains no basic characters other than the letters, digits, and
> >     hyphen-minus; and neither begins nor ends with hyphen-minus.
>
> ...this is not quite correct:  DNS does not make this restriction,
> although I believe it is correct for the current standard for host
> names...

I never claimed that DNS made this restriction.  I just wanted to have
the term "host restrictions" available for defining "basic host label"
and later for defining one of the properties of the compat() function.

Thanks for the feedback,
AMC



From owner-idn@ops.ietf.org  Thu Aug  9 21:02: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 VAA08468
	for <idn-archive@lists.ietf.org>; Thu, 9 Aug 2001 21:02:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15V0a8-000DSa-00
	for idn-data@psg.com; Thu, 09 Aug 2001 17:55:20 -0700
Received: from ciel.hio.jp ([202.224.192.42] helo=hio.jp)
	by psg.com with smtp (Exim 3.31 #1)
	id 15V0a6-000DPL-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 17:55:19 -0700
Received: (qmail 19634 invoked from network); 10 Aug 2001 09:51:01 +0900
Received: from unknown (HELO rain) (192.168.8.35)
  by ciel.hio.jp with SMTP; 10 Aug 2001 09:51:01 +0900
Date: Fri, 10 Aug 2001 09:56:03 +0900
From: YAMASHINA Hio <hio@hio.jp>
To: idn@ops.ietf.org
Subject: [idn] idn-proxy for Windows
Message-Id: <20010810084446.D459.HIO@hio.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.00.06
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hello.

I'm creating HTTP-Proxy "Lychee", that treat domain name encoding
RACE. For reason of using RACE, .jp domains are registried RACE now.

But, Lychee is in developement, and raise many application errors...
Moreover Lychee displays Japanese (although logs are english).

Charsets that Lychee supports now are UTF8 and Japanese (ShiftJIS,
eucjp, and jis-2012).


Note that, Lychee send `Host' HTTP Header in RACE encode.

Lychee is in http://lychee.jp/index.html.en
(This page written in utf-8)

--
 YAMASHINA Hio
 <hio@hio.jp>




From owner-idn@ops.ietf.org  Fri Aug 10 03:08: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 DAA00127
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 03:08:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15V67f-0006hJ-00
	for idn-data@psg.com; Thu, 09 Aug 2001 23:50:19 -0700
Received: from mercury.sun.com ([192.9.25.1])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15V67e-0006hB-00
	for idn@ops.ietf.org; Thu, 09 Aug 2001 23:50:18 -0700
Received: from bebop.France.Sun.COM ([129.157.179.15])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id XAA03379;
	Thu, 9 Aug 2001 23:50:16 -0700 (PDT)
Received: from lillen (vpn133-11.EBay.Sun.COM [129.150.133.11])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f7A6oD219235;
	Fri, 10 Aug 2001 08:50:14 +0200 (MET DST)
Date: Fri, 10 Aug 2001 08:47:32 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [idn] SC/TC equivalence
To: "Adam M. Costello" <amc@cs.berkeley.edu>
Cc: idn@ops.ietf.org
In-Reply-To: "Your message with ID" <20010808212235.E14888@arwen.cs.berkeley.edu>
Message-ID: <Roam.SIMC.2.0.6.997426052.4136.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


> Thank you!  One thing that should be considered by anyone contemplating
> server-side equivalence rules is that clients will not know that the
> names are equivalent.  For web browsers, this will affect visited link
> coloring, page caching, cookie permissions, etc.  Similar pitfalls will
> exist in other applications.  Zone administrators willing to tolerate
> such limitations are free to do server-side equivalence matching to
> their heart's content.  It would be ludicrous for this working group to
> try to prohibit this practice, because it's equivalent to populating the
> zone with identical data for all the matching names, which is obviously
> permitted.

I don't think this WG prohibits this - it shouldn't as far as I can tell.
But the ability of the client to tell
that it got the right answer to a DNS query does add some severe constraints.
[I assume DNS protocol experts will correct me if I got thins wrong.]

If the client asks for A and gets a respose with QNAME A' and answer X then how
does the client know that it wasn't spoofed? Applying DNSSEC would just tell
the client that X is indeed the answer to the question for A'.

So unless the server mains records for both A and A' (with their SIGs)
(where A and A' really expand to all the possible combinations as in
the UNAME) then the client needs to verify that A and A'
match.


Thus there seem to be two choices:
 - client sends A to server
 - server folds A to A' (A' := nameprep(A)), looks up A' and responds to client
 - client verifies that A and A' are the same by checking nameprep(A) = A'
   (to prevent being spoofed)

OR
 - client does A' := nameprep(A), sends A' to server
 - server looks up A' and responds to client
 - done

Thus client might as well do the nameprep before composing the query
and save the work in the server.

  Erik





From owner-idn@ops.ietf.org  Fri Aug 10 05:59: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 FAA02201
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 05:59:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15V8ts-000Fi6-00
	for idn-data@psg.com; Fri, 10 Aug 2001 02:48:16 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>
Subject: Re: [idn] Transparent vs. ACE representations (was We are
Message-Id: <E15V8ts-000Fi6-00@psg.com>
Date: Fri, 10 Aug 2001 02:48:16 -0700

quibbling about WHAT?)
Date: Thu, 9 Aug 2001 09:04:29 -0500
Organization: EHS Company
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> >Suppose for the sake of argument that the message had contained
> >characters outside the US-ASCII repertoire (in a domain name or
> >elsewhere).
>
> If the text switches from one character set to another, then no, it is
> unlikely the processing software will handle that well.

Exactly. Text that contains UTF-8 IDNs is likely to be stored as an
UTF-8 body part. Conversely, text that contains ACE IDNs (which must be
transliterated) is not likely to be stored as an ACE body part since ACE
is not suitable for MIME.

> The real point is that you appear to be assuming a much more
simplified
> and  consistent processing environment for characters, across
> applications, than  actually exists.

Conversely, you appear to be assuming that everybody will want to write
ACE-exception-handling code that scans through body parts, tries to find
a string that looks like ACE, transliterate it, and redisplay the body
part. Give me a break.

Think about this: nobody will be able to explain how ACE works over
email. Everytime you give an example, the software transliterates it. Oh
so now we need exception handling for the exception handling.

ACE is needed for backwards compatibility. That is totally separate from
whether or not it is useful or usable or good for future usage models.
You shouldn't get them confused.








From owner-idn@ops.ietf.org  Fri Aug 10 06:39: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 GAA02978
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 06:39:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15V9Tv-000HZ5-00
	for idn-data@psg.com; Fri, 10 Aug 2001 03:25:31 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15V9Tu-000HYv-00
	for idn@ops.ietf.org; Fri, 10 Aug 2001 03:25:30 -0700
Message-ID: <003801c12187$d93957c0$5b8d21d9@ietf.ignite.net>
From: "Edmon" <edmon@neteka.com>
To: <liana.ydisg@juno.com>
Cc: <klensin@research.att.com>, <idn@ops.ietf.org>
References: <20010809.113129.-789831.0.liana.ydisg@juno.com>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 10 Aug 2001 06:33:05 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

----- Original Message -----
From: <liana.ydisg@juno.com>
> If I want two places, I can
> take care of that by registering at two places.
>

That is precisely my point.  If we force SC=TC into Nameprep I wont be able
to register the TC and SC as different domains.  I dont have a choice.
Edmon




From owner-idn@ops.ietf.org  Fri Aug 10 06:54: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 GAA03326
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 06:54:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15V9l2-000IUM-00
	for idn-data@psg.com; Fri, 10 Aug 2001 03:43:12 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15V9l1-000IUB-00
	for idn@ops.ietf.org; Fri, 10 Aug 2001 03:43:11 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Fri, 10 Aug 2001 03:54:43 -0700
Message-ID: <001001c1218a$753e38a0$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "John C Klensin" <klensin@research.att.com>, "Edmon" <edmon@neteka.com>
Cc: <idn@ops.ietf.org>
References:  <003001c120e0$a8382720$5b8d21d9@ietf.ignite.net> <9405368.997355004@host217-33-136-108.ietf.ignite.net>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 10 Aug 2001 06:51:48 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi John,

I agree with what you said below.

Thanks
Ben Chan

----- Original Message ----- 
From: "John C Klensin" <klensin@research.att.com>
To: "Edmon" <edmon@neteka.com>
Cc: <idn@ops.ietf.org>
Sent: Thursday, August 09, 2001 11:03 AM
Subject: Re: [idn] opting out of SC/TC equivalence


--On Thursday, 09 August, 2001 10:36 -0400 Edmon
<edmon@neteka.com> wrote:

> Which means that TLD dependent SC=TC should not create any
> problem on a user expectation stand point.
> If you know that typing <SC>.cn and <TC>.cn goes to the same
> place, it will happen no matter where you are connected to the
> network. But that doesnt mean that <SC>.tld and <TC>.tld must
> therefore go to the same place.
> There should be no compelling user expectation for this to
> happen.

Edmon,

Let me say to you --and the WG-- what I said to Dave Crocker
after our exchange of comments at the mike.  It seems to me that
the WG is singing one song, but dancing to a different tune.
There are, I think, two, perfectly reasonable, positions:

(i) The IDN effort is about identifiers and characters,
not about languages or even strings.

(ii) The IDN effort is about making it possible to put
non-English words and phrases into the DNS, just as it is
feasible to put English ones (with some constraints)
there today.

Now, if we really believe the first, then it is not clear how
much of nameprep is needed (somewhat less, I think, although
probably not zero).  But discussions of SC/TC equivalence, Arabic
non-spacing break characters, similarity of characters with
non-similar glyphs between languages, distinctions between CJK
contexts, similar characters in different scripts or blocks, and
so on, are all irrelevant and inappropriate -- those are _all_
conversations about words, languages, and the way language
phrases are written.

But many people --I would suggest a majority of those who care
about the IDN issue, independent of those explicitly represented
in the WG-- are interested in words and languages.  To the extent
that they really represent the requirement for this work, all of
the issues excluded above are important and cannot be excluded.
Your assertion about "no compelling user expectation" is, in that
context, false: a compelling user expectation has been asserted
by CNNIC and others.   

And, if any of those language issues are part of the real
requirement, the WG is simply at risk of being irrelevant.  Not
wrong, but irrelevant.   If one reaches that conclusion, then
there is a procedural and responsibility question as to whether
the WG should (and can) report that it can't, within its charter,
do anything relevant or whether it is obligated to report
_something_ out anyway.

    john






From owner-idn@ops.ietf.org  Fri Aug 10 07:15: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 HAA03578
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 07:15:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VA4p-000JVh-00
	for idn-data@psg.com; Fri, 10 Aug 2001 04:03:39 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15VA4o-000JVa-00
	for idn@ops.ietf.org; Fri, 10 Aug 2001 04:03:39 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Fri, 10 Aug 2001 04:15:11 -0700
Message-ID: <002701c1218d$5123f1a0$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "cc-www.com \(Ben\)" <ben@cc-www.com>,
        "John C Klensin" <klensin@research.att.com>,
        "Edmon" <edmon@neteka.com>
Cc: <idn@ops.ietf.org>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 10 Aug 2001 07:12:16 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Actually, let me clarify what I agree with...

How one feels about this SC/TC equivalence problem really does depend
on which position one takes as decribed by John.

Thanks
Ben Chan

----- Original Message -----
From: "cc-www.com (Ben)" <ben@cc-www.com>
To: "John C Klensin" <klensin@research.att.com>; "Edmon"
<edmon@neteka.com>
Cc: <idn@ops.ietf.org>
Sent: Friday, August 10, 2001 6:51 AM
Subject: Re: [idn] opting out of SC/TC equivalence


Hi John,

I agree with what you said below.

Thanks
Ben Chan

----- Original Message -----
From: "John C Klensin" <klensin@research.att.com>
To: "Edmon" <edmon@neteka.com>
Cc: <idn@ops.ietf.org>
Sent: Thursday, August 09, 2001 11:03 AM
Subject: Re: [idn] opting out of SC/TC equivalence


--On Thursday, 09 August, 2001 10:36 -0400 Edmon
<edmon@neteka.com> wrote:

> Which means that TLD dependent SC=TC should not create any
> problem on a user expectation stand point.
> If you know that typing <SC>.cn and <TC>.cn goes to the same
> place, it will happen no matter where you are connected to the
> network. But that doesnt mean that <SC>.tld and <TC>.tld must
> therefore go to the same place.
> There should be no compelling user expectation for this to
> happen.

Edmon,

Let me say to you --and the WG-- what I said to Dave Crocker
after our exchange of comments at the mike.  It seems to me that
the WG is singing one song, but dancing to a different tune.
There are, I think, two, perfectly reasonable, positions:

(i) The IDN effort is about identifiers and characters,
not about languages or even strings.

(ii) The IDN effort is about making it possible to put
non-English words and phrases into the DNS, just as it is
feasible to put English ones (with some constraints)
there today.

Now, if we really believe the first, then it is not clear how
much of nameprep is needed (somewhat less, I think, although
probably not zero).  But discussions of SC/TC equivalence, Arabic
non-spacing break characters, similarity of characters with
non-similar glyphs between languages, distinctions between CJK
contexts, similar characters in different scripts or blocks, and
so on, are all irrelevant and inappropriate -- those are _all_
conversations about words, languages, and the way language
phrases are written.

But many people --I would suggest a majority of those who care
about the IDN issue, independent of those explicitly represented
in the WG-- are interested in words and languages.  To the extent
that they really represent the requirement for this work, all of
the issues excluded above are important and cannot be excluded.
Your assertion about "no compelling user expectation" is, in that
context, false: a compelling user expectation has been asserted
by CNNIC and others.

And, if any of those language issues are part of the real
requirement, the WG is simply at risk of being irrelevant.  Not
wrong, but irrelevant.   If one reaches that conclusion, then
there is a procedural and responsibility question as to whether
the WG should (and can) report that it can't, within its charter,
do anything relevant or whether it is obligated to report
_something_ out anyway.

    john







From owner-idn@ops.ietf.org  Fri Aug 10 10: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 KAA05548
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 10:38:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VDET-0003Vl-00
	for idn-data@psg.com; Fri, 10 Aug 2001 07:25:49 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15VDES-0003Vf-00
	for idn@ops.ietf.org; Fri, 10 Aug 2001 07:25:48 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Fri, 10 Aug 2001 07:37:20 -0700
Message-ID: <000b01c121a9$8ef69980$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "Keith Moore" <moore@cs.utk.edu>,
        "John C Klensin" <klensin@research.att.com>
Cc: "Edmon" <edmon@neteka.com>, <idn@ops.ietf.org>
References: <200108091704.NAA22764@astro.cs.utk.edu>
Subject: Re: [idn] opting out of SC/TC equivalence 
Date: Fri, 10 Aug 2001 10:34:26 -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 Keith,

As unpleasant as the bath water may be, we cannot throw out the baby-
it will come back and haunt each and everyone of us.

Thanks
Ben Chan


----- Original Message -----
From: "Keith Moore" <moore@cs.utk.edu>
To: "John C Klensin" <klensin@research.att.com>
Cc: "Edmon" <edmon@neteka.com>; <idn@ops.ietf.org>
Sent: Thursday, August 09, 2001 1:04 PM
Subject: Re: [idn] opting out of SC/TC equivalence


> > I completely concur with you, perhaps you misunderstand my
> > statement.  What I am saying is that if CNNIC believes that
> > there is compelling user expectation within their registry to
> > have SC=TC, then they should absolutely implement it.
>
> And they should somehow to contrive to be sure that no records
> are cached outside China, where other rules would apply as a
> query is applied to a cached record?   I continue to be afraid
> that the choices are between
>
>         -- the whole DNS using the same procedures or
>
>         -- fragmenting the network
>

I don't think that's an accurate characterization.   As a practical
manner, any DNS zone can create multiple names within that zone that
resolve to equivalent RRs, and any DNS zone can establish procedures
for keeping those names consistent, without affecting the DNS protocol
or the applications that use it.  Similarly, if two zones are
controlled
by the same party, that party can maintain those zones such that
label X in zone A and label X' in zone B resolve to an equivalent set
of
RRs, and the party controlling those zones can keep those two zones
consistent with one another.

I don't see this as inherently undesirable.  True, caches will not
recognize
that these zones are equivalent, but this mainly serves to increase
lookup
delay for names in those zones and to increase load on the
authoritative
servers for those zones.  Each zone can decide for itself whether it's
worth the additional delay and cost.

Nothing that IDN does is going to change the ability to create
multiple
names that produce equivalent RRs.  Nor do I think that IDN can build
a
better way to solve this problem.  We certainly don't want to embed
knowledge of SC/TC equivalence into applications, DNS libraries, or
DNS servers.

Users can tell the difference between TC and SC.  So they will be able
to figure out that even if TC and SC names are equivalent within some
particular TLD, they are not necessarily equivalent elsewhere.

Bascially I think this issue is out of scope for IDN, because you
can't
expect a networking protocol to fix all naming equivalence problems in
all languages.

Keith






From owner-idn@ops.ietf.org  Fri Aug 10 10:46: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 KAA05653
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 10:46:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VDPN-000476-00
	for idn-data@psg.com; Fri, 10 Aug 2001 07:37:05 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15VDPM-00046j-00
	for idn@ops.ietf.org; Fri, 10 Aug 2001 07:37:04 -0700
Received: from zetnet.co.uk (man-s289.dialup.zetnet.co.uk [194.247.45.160])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f7AEatv30433;
	Fri, 10 Aug 2001 15:36:55 +0100
Message-ID: <3B73E151.63E1D59D@zetnet.co.uk>
Date: Fri, 10 Aug 2001 14:27:45 +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: Erik Nordmark <Erik.Nordmark@eng.sun.com>, idn@ops.ietf.org
Subject: Re: [idn] SC/TC equivalence
References: <Roam.SIMC.2.0.6.997426052.4136.nordmark@bebop.france>
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-----

Erik Nordmark wrote:
> Adam M. Costello <amc@cs.berkeley.edu> wrote:
> > Thank you!  One thing that should be considered by anyone contemplating
> > server-side equivalence rules is that clients will not know that the
> > names are equivalent.  For web browsers, this will affect visited link
> > coloring, page caching, cookie permissions, etc.  Similar pitfalls will
> > exist in other applications.  Zone administrators willing to tolerate
> > such limitations are free to do server-side equivalence matching to
> > their heart's content.  It would be ludicrous for this working group to
> > try to prohibit this practice, because it's equivalent to populating the
> > zone with identical data for all the matching names, which is obviously
> > permitted.
> 
> I don't think this WG prohibits this - it shouldn't as far as I can tell.
> But the ability of the client to tell that it got the right answer to a
> DNS query does add some severe constraints.
> [I assume DNS protocol experts will correct me if I got this wrong.]
> 
> If the client asks for A and gets a response with QNAME A' and answer X
> then ...

It won't - it will get a response with QNAME A.

For DNSSEC, all responses for names that are actually used will have to be
signed. This is an inevitable consequence of wanting TC/SC equivalence without
putting TC/SC folding in nameprep (that is, the client-side canonicalization
function). The decision that WG has to make is whether TC/SC folding is in
nameprep or not. If that answer is "yes", it also has to define the folding,
and require that all clients implement it.

Personally I don't think nameprep should include any folding that depends
on the semantics of particular languages - even if that causes inefficiencies
for DNSSEC. The 'ONE' work demonstrates how complicated "semantic folding"
can be:

James Seng wrote:
# Our (as in i-DNS.net) approach have been working on Onomastic
# Normalization Engine for registration time to handle possible multiple
# names since Nov last year. The work on ONE turns out to be much more
# complex and time consuming then originally expected. And there is
# different ONE for each language (See ONE-J and ONE-K at
# http://playground.i-dns.net/one/index.html).

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

iQEVAwUBO3PhLjkCAxeYt5gVAQHFQwgAn1B631hvNs0zJSNGA04BCU4tNsxwWE9O
3PKmKt49Rm9zpGh5Sq3HEHr1bmsQQoZshXzk1w+jmg9U3d4Fsst4ry03PT7ScjFX
wPBJ6gyZ/A/R2KdZ770F9kLjg9jqSTnFtQIc2nsHGYXP1MmdWlPHH5qWDSoqhURU
IFBhWcOGSY1J+6c8+CqopG63RVLrISoB4oDMxCboQPcwt30e5RVLbHR6V+bM0gY6
GdqmSIv3w7xXEMoMKed8d9vIkKG3aGsYwAzHI/8jde7AuwS+LBWgPbOt0LzRZPau
UzATGhdcI+hDxe0AVO2ynz7vHt8MKZd7AxSGLnqBCXWhiqlpxLmLaw==
=FNbG
-----END PGP SIGNATURE-----




From owner-idn@ops.ietf.org  Fri Aug 10 12:42: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 MAA08058
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 12:42:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VFCM-000A2y-00
	for idn-data@psg.com; Fri, 10 Aug 2001 09:31:46 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15VFCL-000A2r-00
	for idn@ops.ietf.org; Fri, 10 Aug 2001 09:31:45 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id MAA28959;
        Fri, 10 Aug 2001 12:31:41 -0400 (EDT)
Message-Id: <200108101631.MAA28959@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] A UTF-8 test for mail clients 
In-reply-to: Your message of "09 Aug 2001 20:26:35 -0000."
             <20010809202635.7814.qmail@cr.yp.to> 
Date: Fri, 10 Aug 2001 12:31:41 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > addresses are defined to be ASCII in both RFC 822 and RFC 2822
> 
> Wake up, Keith! We're changing this definition. 

get back on your meds, Dan.  IDN is *not* changing the format of addresses 
used in any protocol, with the possible exception of DNS.

Keith



From owner-idn@ops.ietf.org  Fri Aug 10 12:43: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 MAA08071
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 12:43:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VFAj-0009z9-00
	for idn-data@psg.com; Fri, 10 Aug 2001 09:30:05 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15VFAi-0009yu-00
	for idn@ops.ietf.org; Fri, 10 Aug 2001 09:30:04 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id MAA28935;
        Fri, 10 Aug 2001 12:29:58 -0400 (EDT)
Message-Id: <200108101629.MAA28935@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: "David Hopwood" <david.hopwood@zetnet.co.uk>, idn@ops.ietf.org
Subject: Re: [idn] Transparent vs. ACE representations (was We are 
In-reply-to: Your message of "Thu, 09 Aug 2001 12:57:36 PDT."
             <E15Uvw0-000NsP-00@psg.com> 
Date: Fri, 10 Aug 2001 12:29:58 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Conversely, you appear to be assuming that everybody will want to write
> ACE-exception-handling code that scans through body parts, tries to find
> a string that looks like ACE, transliterate it, and redisplay the body
> part. Give me a break.

why is that any stranger than code that scans through text body parts,
tries to find strings that look like URLs, and displays those URLs as
clickable links?  And ACE strings are easier to recognize than URLs.

I'm not saying that "everybody" will do this, but it's certainly feasible.

Keith



From owner-idn@ops.ietf.org  Fri Aug 10 13: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 NAA08661
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 13:26:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VFwc-000CZT-00
	for idn-data@psg.com; Fri, 10 Aug 2001 10:19:34 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15VFwb-000CZK-00
	for idn@ops.ietf.org; Fri, 10 Aug 2001 10:19:33 -0700
Received: (qmail 26072 invoked by uid 1001); 10 Aug 2001 17:19:35 -0000
Date: 10 Aug 2001 17:19:35 -0000
Message-ID: <20010810171935.6159.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] IDNs do not use ASCII
References: <20010809202635.7814.qmail@cr.yp.to> <200108101631.MAA28959@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:
> > > addresses are defined to be ASCII in both RFC 822 and RFC 2822
> > Wake up, Keith! We're changing this definition. 
> get back on your meds, Dan.  IDN is *not* changing the format of addresses 
> used in any protocol, with the possible exception of DNS.

On the contrary. IDN is replacing ASCII with another character encoding
in every Internet protocol that uses domain names.

The ASCII standard specifies, for example, that the byte string bq--blah
(i.e., \142\161\055\055\142\154\141\150) represents characters bq--blah.
Under a typical ACE IDN proposal, however, that byte string represents a
different sequence of characters, and there's another byte string that
represents the characters bq--blah.

Sure, ASCII and ACE both use 7-bit bytes; this doesn't mean that ASCII
and ACE are the same! A character encoding is not a set of byte strings;
it is a _mapping_ between character strings and byte strings.

---Dan



From owner-idn@ops.ietf.org  Fri Aug 10 13:31: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 NAA08733
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 13:31:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VG3I-000Cwi-00
	for idn-data@psg.com; Fri, 10 Aug 2001 10:26:28 -0700
Received: from femail42.sdc1.sfba.home.com ([24.254.60.36])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15VG3H-000Cwc-00
	for idn@ops.ietf.org; Fri, 10 Aug 2001 10:26:27 -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 <20010810172618.BOGP19537.femail42.sdc1.sfba.home.com@c1340594a>;
          Fri, 10 Aug 2001 10:26:18 -0700
Message-ID: <0cd501c121c1$d0e751f0$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>,
        "Adam M. Costello" <amc@cs.berkeley.edu>
Cc: <idn@ops.ietf.org>
References: <Roam.SIMC.2.0.6.997426052.4136.nordmark@bebop.france>
Subject: Re: [idn] SC/TC equivalence
Date: Fri, 10 Aug 2001 10:28: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 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

For SC/TC equivalence, the feedback I have gotten is that "In practice, most
Chinese would expect either simplified or traditional, but not a mixture of
both", and from another writer, "Simplified and traditional are
usually used in their own contexts, and a domain name is a single context,
and thus wouldn't result in a mixture of the two systems."

If that is true, then for TC/SC, unlike case, registering exactly two
variants of any particular domain name would be sufficient; one would not
have to register n^2 combinations. Given that, registering SC/TC variants is
much more like registering two different languages and/or scripts, something
best left to documentation instead of changing nameprep.

Mark

â€”â€”â€”â€”â€”

Ï€Î¬Î½Ï„Ï‰Î½ Î¼Î­Ï„Ï�Î¿Î½ á¼„Î½Î¸Ï�Ï‰Ï€Î¿Ï‚ â€” Î Ï�Ï‰Ï„Î±Î³ÏŒÏ�Î±Ï‚
[http://www.macchiato.com]

----- Original Message -----
From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
To: "Adam M. Costello" <amc@cs.berkeley.edu>
Cc: <idn@ops.ietf.org>
Sent: Thursday, August 09, 2001 23:47
Subject: Re: [idn] SC/TC equivalence


>
> > Thank you!  One thing that should be considered by anyone contemplating
> > server-side equivalence rules is that clients will not know that the
> > names are equivalent.  For web browsers, this will affect visited link
> > coloring, page caching, cookie permissions, etc.  Similar pitfalls will
> > exist in other applications.  Zone administrators willing to tolerate
> > such limitations are free to do server-side equivalence matching to
> > their heart's content.  It would be ludicrous for this working group to
> > try to prohibit this practice, because it's equivalent to populating the
> > zone with identical data for all the matching names, which is obviously
> > permitted.
>
> I don't think this WG prohibits this - it shouldn't as far as I can tell.
> But the ability of the client to tell
> that it got the right answer to a DNS query does add some severe
constraints.
> [I assume DNS protocol experts will correct me if I got thins wrong.]
>
> If the client asks for A and gets a respose with QNAME A' and answer X
then how
> does the client know that it wasn't spoofed? Applying DNSSEC would just
tell
> the client that X is indeed the answer to the question for A'.
>
> So unless the server mains records for both A and A' (with their SIGs)
> (where A and A' really expand to all the possible combinations as in
> the UNAME) then the client needs to verify that A and A'
> match.
>
>
> Thus there seem to be two choices:
>  - client sends A to server
>  - server folds A to A' (A' := nameprep(A)), looks up A' and responds to
client
>  - client verifies that A and A' are the same by checking nameprep(A) = A'
>    (to prevent being spoofed)
>
> OR
>  - client does A' := nameprep(A), sends A' to server
>  - server looks up A' and responds to client
>  - done
>
> Thus client might as well do the nameprep before composing the query
> and save the work in the server.
>
>   Erik
>
>
>
>




From owner-idn@ops.ietf.org  Fri Aug 10 14:50: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 OAA09691
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 14:50:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VH7T-000FyG-00
	for idn-data@psg.com; Fri, 10 Aug 2001 11:34:51 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15VH7S-000Fy9-00
	for idn@ops.ietf.org; Fri, 10 Aug 2001 11:34:50 -0700
Received: from zetnet.co.uk (man-s109.dialup.zetnet.co.uk [194.247.41.236])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f7AIYhv14421;
	Fri, 10 Aug 2001 19:34:43 +0100
Message-ID: <3B742989.C3E562D7@zetnet.co.uk>
Date: Fri, 10 Aug 2001 19:35:53 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: Harald Tveit Alvestrand <harald@alvestrand.no>, idn@ops.ietf.org
Subject: Re: [idn] Which names are valid?
References: <3B67FE19.29536D40@zetnet.co.uk> <541958495.997365286@localhost>
Content-Type: text/plain; charset=UTF-8
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA09691

-----BEGIN PGP SIGNED MESSAGE-----

Harald Tveit Alvestrand wrote:
> --On 1. august 2001 14:03 +0100 David Hopwood <david.hopwood@zetnet.co.uk>
> wrote:
>
> > What do you propose to call the query string used for a SRV lookup
> > (e.g. "_ldap._tcp.example.com"), if not a domain name? It is certainly
> > a domain name as defined and used in RFCs 1034, 1035 and 2181 (although
> > not a host name).
>
> with respect:
> draft-ietf-idn-requirements-08.txt has been in the group for a LONG time.

The definitions in that draft are not entirely satisfactory. For example,
consider "_ldap._tcp.Ï€.com". This is clearly a domain name, and it is
clearly internationalized, so the most sensible thing to call it would be
an internationalized domain name. However, it is not a hostname (although
"Ï€.com" is). It makes no sense to lose the useful distinction between
hostnames and domain names just because they are internationalized.

Note that the remit of this WG is to develop standards for internationalized
domain names, not just internationalized hostnames. Users will not be very
happy if lookups for SRV records below a non-ASCII domain don't work.

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

iQEVAwUBO3QKxzkCAxeYt5gVAQFP9wf/Qk5LwyDNWYWDz/2uYeRscIAHQhftBii6
o48A9wPIerUyDzOajiCxepEsX4oso3Hy7htj8k4QFNrQyga0BF4J/xGyRKqo4lwt
qOizKvDaCKjBUDvcsY6ThVTwqN75jNFyJvSSCFGmbDSWB6N4u0yqFL/4uKN6O8rZ
y+DqNn1rohtlchoXPGhcAKTucrp15xDbB9e8lBBAmHx6/J/Y7s6H+Ewx/fUyNy7L
fT7VF6g0XjWH6w0jdp7vIX/gtHzyjT5w9pUWp5cLWexqnmT4MsICXbhn5OSaEHm+
54sLzjpucfP8YGRa5XF0fm9agPXSsWk5n8B+15hAHo6FgKNl1rtk8w==
=ARLN
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Fri Aug 10 15: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 PAA10471
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 15:33:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VHdg-000HSH-00
	for idn-data@psg.com; Fri, 10 Aug 2001 12:08:08 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15VHdf-000HS1-00
	for idn@ops.ietf.org; Fri, 10 Aug 2001 12:08:07 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+3nwGBQ7c9H1CzBLl2DR1gl/UH0KlU1bg==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCHLZWBV; Fri, 10 Aug 2001 15:07:34 EDT
To: edmon@neteka.com
Cc: liana.ydisg@juno.com, klensin@research.att.com, idn@ops.ietf.org
Date: Fri, 10 Aug 2001 12:24:21 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010810.122425.-821511.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

You got my point wrong.  We are not in the same discussion 
space.  SC=TC discussion is only regarding font difference.  
The semantics are basicaly the same, but the reader groups 
are different.  It may be said, this is analogy to Latin uppercase
and lowercase folding.   As a registrant, if the choice is two 
places: SC+TC, then it is a reality already, we don't need this 
standard discussion right now.   And to Ben Chan also, 
 we have TLD are doing exactly the same thing:  .tw and .cn
too.  As a server provider, you may choose to display .tw in TC, and cn
in SC as an equivalent solution to your suggestion without
get into this WG.

Liana


On Fri, 10 Aug 2001 06:33:05 -0400 "Edmon" <edmon@neteka.com> writes:
> ----- Original Message -----
> From: <liana.ydisg@juno.com>
> > If I want two places, I can
> > take care of that by registering at two places.
> >
> 
> That is precisely my point.  If we force SC=TC into Nameprep I wont 
> be able
> to register the TC and SC as different domains.  I dont have a 
> choice.
> Edmon
> 



From owner-idn@ops.ietf.org  Fri Aug 10 16:01: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 QAA10848
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 16:01:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VI11-000ISd-00
	for idn-data@psg.com; Fri, 10 Aug 2001 12:32:15 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15VI10-000ISW-00
	for idn@ops.ietf.org; Fri, 10 Aug 2001 12:32:14 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+3nwGBQ7c9HUmf72q2Jm+0wCKcrNhyyRA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCHNEG4D; Fri, 10 Aug 2001 15:31:55 EDT
To: mark@macchiato.com
Cc: Erik.Nordmark@eng.sun.com, amc@cs.berkeley.edu, idn@ops.ietf.org
Date: Fri, 10 Aug 2001 12:48:50 -0700
Subject: Re: [idn] SC/TC equivalence
Message-ID: <20010810.124900.-821511.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-6,8-111
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

The statement is correct to the extent that every home has
a good collection of books, but the extent to the satement is:
 so we don't need a library in the city, that is where we depart.

Liana


On Fri, 10 Aug 2001 10:28:02 -0700 "Mark Davis" <mark@macchiato.com>
writes:
> For SC/TC equivalence, the feedback I have gotten is that "In 
> practice, most
> Chinese would expect either simplified or traditional, but not a 
> mixture of
> both", and from another writer, "Simplified and traditional are
> usually used in their own contexts, and a domain name is a single 
> context,
> and thus wouldn't result in a mixture of the two systems."
> 
> If that is true, then for TC/SC, unlike case, registering exactly two
> variants of any particular domain name would be sufficient; one 
> would not
> have to register n^2 combinations. Given that, registering SC/TC 
> variants is
> much more like registering two different languages and/or scripts, 
> something
> best left to documentation instead of changing nameprep.
> 
> Mark
> 
> â€”â€”â€”â€”â€?
> 
> Ï€Î¬Î½Ï„Ï‰Î½ Î¼Î­Ï„Ï�Î¿Î½ á¼„Î½Î¸Ï�Ï‰Ï€Î¿Ï‚ â€?Î Ï�Ï‰Ï„Î±Î³ÏŒÏ�Î±Ï‚
> [http://www.macchiato.com]
> 
> ----- Original Message -----
> From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> To: "Adam M. Costello" <amc@cs.berkeley.edu>
> Cc: <idn@ops.ietf.org>
> Sent: Thursday, August 09, 2001 23:47
> Subject: Re: [idn] SC/TC equivalence
> 
> 
> >
> > > Thank you!  One thing that should be considered by anyone 
> contemplating
> > > server-side equivalence rules is that clients will not know that 
> the
> > > names are equivalent.  For web browsers, this will affect 
> visited link
> > > coloring, page caching, cookie permissions, etc.  Similar 
> pitfalls will
> > > exist in other applications.  Zone administrators willing to 
> tolerate
> > > such limitations are free to do server-side equivalence matching 
> to
> > > their heart's content.  It would be ludicrous for this working 
> group to
> > > try to prohibit this practice, because it's equivalent to 
> populating the
> > > zone with identical data for all the matching names, which is 
> obviously
> > > permitted.
> >
> > I don't think this WG prohibits this - it shouldn't as far as I 
> can tell.
> > But the ability of the client to tell
> > that it got the right answer to a DNS query does add some severe
> constraints.
> > [I assume DNS protocol experts will correct me if I got thins 
> wrong.]
> >
> > If the client asks for A and gets a respose with QNAME A' and 
> answer X
> then how
> > does the client know that it wasn't spoofed? Applying DNSSEC would 
> just
> tell
> > the client that X is indeed the answer to the question for A'.
> >
> > So unless the server mains records for both A and A' (with their 
> SIGs)
> > (where A and A' really expand to all the possible combinations as 
> in
> > the UNAME) then the client needs to verify that A and A'
> > match.
> >
> >
> > Thus there seem to be two choices:
> >  - client sends A to server
> >  - server folds A to A' (A' := nameprep(A)), looks up A' and 
> responds to
> client
> >  - client verifies that A and A' are the same by checking 
> nameprep(A) = A'
> >    (to prevent being spoofed)
> >
> > OR
> >  - client does A' := nameprep(A), sends A' to server
> >  - server looks up A' and responds to client
> >  - done
> >
> > Thus client might as well do the nameprep before composing the 
> query
> > and save the work in the server.
> >
> >   Erik
> >
> >
> >
> >
> 
> 



From owner-idn@ops.ietf.org  Fri Aug 10 16:19: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 QAA11027
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 16:19:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VINQ-000JWx-00
	for idn-data@psg.com; Fri, 10 Aug 2001 12:55:24 -0700
Received: from femail39.sdc1.sfba.home.com ([24.254.60.33])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15VINP-000JWr-00
	for idn@ops.ietf.org; Fri, 10 Aug 2001 12:55:23 -0700
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 <20010810195516.FYLD6528.femail39.sdc1.sfba.home.com@c1340594a>;
          Fri, 10 Aug 2001 12:55:16 -0700
Message-ID: <0d9d01c121d6$a0c7a140$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: <liana.ydisg@juno.com>
Cc: <Erik.Nordmark@eng.sun.com>, <amc@cs.berkeley.edu>, <idn@ops.ietf.org>
References: <20010810.124900.-821511.1.liana.ydisg@juno.com>
Subject: Re: [idn] SC/TC equivalence
Date: Fri, 10 Aug 2001 12:57:04 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Huh?
â€”â€”â€”â€”â€”

Ï€Î¬Î½Ï„Ï‰Î½ Î¼Î­Ï„Ï�Î¿Î½ á¼„Î½Î¸Ï�Ï‰Ï€Î¿Ï‚ â€” Î Ï�Ï‰Ï„Î±Î³ÏŒÏ�Î±Ï‚
[http://www.macchiato.com]

----- Original Message -----
From: <liana.ydisg@juno.com>
To: <mark@macchiato.com>
Cc: <Erik.Nordmark@eng.sun.com>; <amc@cs.berkeley.edu>; <idn@ops.ietf.org>
Sent: Friday, August 10, 2001 12:48
Subject: Re: [idn] SC/TC equivalence


> The statement is correct to the extent that every home has
> a good collection of books, but the extent to the satement is:
>  so we don't need a library in the city, that is where we depart.
>
> Liana
>
>
> On Fri, 10 Aug 2001 10:28:02 -0700 "Mark Davis" <mark@macchiato.com>
> writes:
> > For SC/TC equivalence, the feedback I have gotten is that "In
> > practice, most
> > Chinese would expect either simplified or traditional, but not a
> > mixture of
> > both", and from another writer, "Simplified and traditional are
> > usually used in their own contexts, and a domain name is a single
> > context,
> > and thus wouldn't result in a mixture of the two systems."
> >
> > If that is true, then for TC/SC, unlike case, registering exactly two
> > variants of any particular domain name would be sufficient; one
> > would not
> > have to register n^2 combinations. Given that, registering SC/TC
> > variants is
> > much more like registering two different languages and/or scripts,
> > something
> > best left to documentation instead of changing nameprep.
> >
> > Mark
> >
> > â€”â€”â€”â€”?
> >
> >  Î¬Î½Ï„Ï‰Î½ Î¼Î­Ï„Ï�Î¿Î½ á¼„Î½Î¸Ï�Ï‰Ï€Î¿Ï‚ ? Ï�Ï‰Ï„Î±Î³ÏŒÏ�Î±Ï‚
> > [http://www.macchiato.com]
> >
> > ----- Original Message -----
> > From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> > To: "Adam M. Costello" <amc@cs.berkeley.edu>
> > Cc: <idn@ops.ietf.org>
> > Sent: Thursday, August 09, 2001 23:47
> > Subject: Re: [idn] SC/TC equivalence
> >
> >
> > >
> > > > Thank you!  One thing that should be considered by anyone
> > contemplating
> > > > server-side equivalence rules is that clients will not know that
> > the
> > > > names are equivalent.  For web browsers, this will affect
> > visited link
> > > > coloring, page caching, cookie permissions, etc.  Similar
> > pitfalls will
> > > > exist in other applications.  Zone administrators willing to
> > tolerate
> > > > such limitations are free to do server-side equivalence matching
> > to
> > > > their heart's content.  It would be ludicrous for this working
> > group to
> > > > try to prohibit this practice, because it's equivalent to
> > populating the
> > > > zone with identical data for all the matching names, which is
> > obviously
> > > > permitted.
> > >
> > > I don't think this WG prohibits this - it shouldn't as far as I
> > can tell.
> > > But the ability of the client to tell
> > > that it got the right answer to a DNS query does add some severe
> > constraints.
> > > [I assume DNS protocol experts will correct me if I got thins
> > wrong.]
> > >
> > > If the client asks for A and gets a respose with QNAME A' and
> > answer X
> > then how
> > > does the client know that it wasn't spoofed? Applying DNSSEC would
> > just
> > tell
> > > the client that X is indeed the answer to the question for A'.
> > >
> > > So unless the server mains records for both A and A' (with their
> > SIGs)
> > > (where A and A' really expand to all the possible combinations as
> > in
> > > the UNAME) then the client needs to verify that A and A'
> > > match.
> > >
> > >
> > > Thus there seem to be two choices:
> > >  - client sends A to server
> > >  - server folds A to A' (A' := nameprep(A)), looks up A' and
> > responds to
> > client
> > >  - client verifies that A and A' are the same by checking
> > nameprep(A) = A'
> > >    (to prevent being spoofed)
> > >
> > > OR
> > >  - client does A' := nameprep(A), sends A' to server
> > >  - server looks up A' and responds to client
> > >  - done
> > >
> > > Thus client might as well do the nameprep before composing the
> > query
> > > and save the work in the server.
> > >
> > >   Erik
> > >
> > >
> > >
> > >
> >
> >
>
>




From owner-idn@ops.ietf.org  Fri Aug 10 16:22: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 QAA11080
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 16:22:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VIaa-000KGD-00
	for idn-data@psg.com; Fri, 10 Aug 2001 13:09:00 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
Subject: Re: [idn] Transparent vs. ACE representations (was We are
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15VIaa-000KGD-00@psg.com>
Date: Fri, 10 Aug 2001 13:09:00 -0700

> why is that any stranger than code that scans through text body parts,
> tries to find strings that look like URLs, and displays those URLs as
> clickable links?  And ACE strings are easier to recognize than URLs.

Most of the apps that do this for URLs are already manipulating
rich-text and
so its not that big of a deal to underline or colorize text. It is a big
deal
for everything else though. How many logfile viewers do it?

How many apps are going to do ACE transliteration? Will ping?
traceroute?
netstat? etc?

> I'm not saying that "everybody" will do this, but it's certainly
> feasible.

Lots of things are feasible but so impractical that they are unexpected








From owner-idn@ops.ietf.org  Fri Aug 10 18:47: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 SAA12719
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 18:47:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VKlI-00016w-00
	for idn-data@psg.com; Fri, 10 Aug 2001 15:28:12 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15VKlI-00016i-00
	for idn@ops.ietf.org; Fri, 10 Aug 2001 15:28:12 -0700
Received: from amc by nicemice.net with local (Exim 3.31 #1 (Debian))
	id 15VKlH-0006IP-00
	for <idn@ops.ietf.org>; Fri, 10 Aug 2001 15:28:11 -0700
Date: Fri, 10 Aug 2001 22:28:11 +0000
From: "Adam M. Costello" <amc@cs.berkeley.edu>
To: idn@ops.ietf.org
Subject: Re: [idn] SC/TC equivalence
Message-ID: <20010810222811.C23949@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Roam.SIMC.2.0.6.997426052.4136.nordmark@bebop.france>
User-Agent: Mutt/1.3.18i
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Erik Nordmark <Erik.Nordmark@eng.sun.com> wrote:

> If the client asks for A and gets a respose with QNAME A'...
>
> So unless the server mains records for both A and A' (with their SIGs)
> (where A and A' really expand to all the possible combinations as in
> the UNAME) then the client needs to verify that A and A' match.

I think the server is always supposed to answer the query that was asked
(A, not A').  If maintaining records for all equivalent variants of
A' is too expensive, it could instead generate the response (and the
signature) on the fly.  It could use caching to remember the responses
for the most common variants.

AMC



From owner-idn@ops.ietf.org  Fri Aug 10 18: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 SAA12816
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 18:55:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VKzw-0001op-00
	for idn-data@psg.com; Fri, 10 Aug 2001 15:43:20 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15VKzv-0001oj-00
	for idn@ops.ietf.org; Fri, 10 Aug 2001 15:43:19 -0700
Received: from amc by nicemice.net with local (Exim 3.31 #1 (Debian))
	id 15VKzv-0006JK-00
	for <idn@ops.ietf.org>; Fri, 10 Aug 2001 15:43:19 -0700
Date: Fri, 10 Aug 2001 22:43:19 +0000
From: "Adam M. Costello" <amc@cs.berkeley.edu>
To: idn@ops.ietf.org
Subject: Re: [idn] IDNs do not use ASCII
Message-ID: <20010810224319.D23949@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20010810171935.6159.qmail@cr.yp.to>
User-Agent: Mutt/1.3.18i
Sender: owner-idn@ops.ietf.org
Precedence: bulk

"D. J. Bernstein" <djb@cr.yp.to> wrote:

> The ASCII standard specifies, for example, that the byte string
> bq--blah (i.e., \142\161\055\055\142\154\141\150) represents
> characters bq--blah.  Under a typical ACE IDN proposal, however, that
> byte string represents a different sequence of characters, and there's
> another byte string that represents the characters bq--blah.

Strings beginning with the ACE prefix are never ACE-encoded.

Here's the way I think of it now:  In the current system, FOO and
foo and Foo and fOo etc. are all equivalent.  We don't say that FOO
represents foo, or that foo represents FOO.  They are distinct ASCII
strings, but they are equivalent labels.

The new system merely expands the set of strings and expands the notion
of equivalence.  Now <lowercase-pi> and <uppercase-pi> and bq--blah
and BQ--BLAH etc. are all equivalent.  Sometimes we like to think that
bq--blah represents <lowercase-pi>, and sometimes we like to think
that <lowercase-pi> represents bq--blah, but actually it's a symmetric
equivalence relationship.  They are distinct Unicode strings, but they
are equivalent labels, just like FOO and foo above.

Having each equivalence class include at least one element containing
only ASCII characters is convenient for interoperating with legacy
software/protocols/interfaces.

AMC



From owner-idn@ops.ietf.org  Fri Aug 10 20:25: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 UAA13408
	for <idn-archive@lists.ietf.org>; Fri, 10 Aug 2001 20:25:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VMPx-000603-00
	for idn-data@psg.com; Fri, 10 Aug 2001 17:14:17 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.31 #1)
	id 15VMPw-0005zx-00
	for idn@ops.ietf.org; Fri, 10 Aug 2001 17:14:16 -0700
Received: (qmail 9898 invoked by uid 1001); 11 Aug 2001 00:14:31 -0000
Date: 11 Aug 2001 00:14:31 -0000
Message-ID: <20010811001431.22378.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] IDNs do not use ASCII
References: <20010810171935.6159.qmail@cr.yp.to> <20010810224319.D23949@arwen.cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Adam M. Costello writes:
> Now <lowercase-pi> and <uppercase-pi> and bq--blah and BQ--BLAH etc.
> are all equivalent.

That's ridiculous. The user wants to see lowercase pi. He might tolerate
uppercase pi, but he will kick and scream if he sees bq--blah.

This is typical of your arguments: you show us the road to failure, you
define failure as being equivalent to success, and you claim success.
Sorry, Adam, but that isn't what the users want to see.

---Dan



From owner-idn@ops.ietf.org  Sat Aug 11 05:52: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 FAA05242
	for <idn-archive@lists.ietf.org>; Sat, 11 Aug 2001 05:52:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VVDk-000Nio-00
	for idn-data@psg.com; Sat, 11 Aug 2001 02:38:16 -0700
Received: from attila.bofh.it ([213.92.8.2] ident=postfix)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15VVDi-000Nii-00
	for idn@ops.ietf.org; Sat, 11 Aug 2001 02:38:16 -0700
Received: by attila.bofh.it (Postfix, from userid 10)
	id 381DB5FF71; Sat, 11 Aug 2001 11:38:12 +0200 (CEST)
Received: by wonderland.linux.it (Postfix/Md, from userid 1001)
	id 0691D17EF9; Sat, 11 Aug 2001 11:37:39 +0200 (CEST)
Date: Sat, 11 Aug 2001 11:37:39 +0200
From: "Marco d'Itri" <md@Linux.IT>
To: idn@ops.ietf.org
Subject: Re: [idn] IDNs do not use ASCII
Message-ID: <20010811113739.A627@wonderland.linux.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20010811001431.22378.qmail@cr.yp.to>
User-Agent: Mutt/1.3.18i
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Aug 11, "D. J. Bernstein" <djb@cr.yp.to> wrote:

 >That's ridiculous. The user wants to see lowercase pi. He might tolerate
 >uppercase pi, but he will kick and scream if he sees bq--blah.
Did you do some kind of usability survey among users or are you just
speculating?

-- 
ciao,
Marco



From owner-idn@ops.ietf.org  Sat Aug 11 06:51: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 GAA05479
	for <idn-archive@lists.ietf.org>; Sat, 11 Aug 2001 06:51:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VWCR-000P3d-00
	for idn-data@psg.com; Sat, 11 Aug 2001 03:40:59 -0700
Received: from bodin.infinit.se ([195.198.39.30])
	by psg.com with smtp (Exim 3.31 #1)
	id 15VWCQ-000P3V-00
	for idn@ops.ietf.org; Sat, 11 Aug 2001 03:40:58 -0700
Received: (qmail 3258 invoked by uid 569); 11 Aug 2001 10:40:52 -0000
Date: Sat, 11 Aug 2001 12:40:52 +0200
From: Magnus Bodin <magnus@bodin.org>
To: "Marco d'Itri" <md@Linux.IT>
Cc: idn@ops.ietf.org
Subject: Re: [idn] IDNs do not use ASCII
Message-ID: <20010811124051.A22698@bodin.org>
References: <20010811001431.22378.qmail@cr.yp.to> <20010811113739.A627@wonderland.linux.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20010811113739.A627@wonderland.linux.it>
User-Agent: Mutt/1.3.20i
X-message-flag: NOTE: This mail was originally covered with Belgian chocolate
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Sat, Aug 11, 2001 at 11:37:39AM +0200, Marco d'Itri wrote:
> On Aug 11, "D. J. Bernstein" <djb@cr.yp.to> wrote:
> 
>  >That's ridiculous. The user wants to see lowercase pi. He might tolerate
>  >uppercase pi, but he will kick and scream if he sees bq--blah.
>
> Did you do some kind of usability survey among users or are you just
> speculating?

Thats quite obvious anyway, but if ACE is gonna happen, then I really hope
that the users won't see bq-blah in the URL-line. 

That would be a sure way to kill IDN before it goes popular.
 
/magnus

-- 
This message secured by Rot-52 encryption technology.
Unauthorized decryption prohibited under the DMCA.
Violators will be prosecuted to the full extent of the law.



From owner-idn@ops.ietf.org  Sat Aug 11 13:39: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 NAA07682
	for <idn-archive@lists.ietf.org>; Sat, 11 Aug 2001 13:39:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VcFL-0006ha-00
	for idn-data@psg.com; Sat, 11 Aug 2001 10:08:23 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15VcFK-0006hU-00
	for idn@ops.ietf.org; Sat, 11 Aug 2001 10:08:22 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+3nwGBQ7c9H0HVYbWC8dFsWiQnoz2wuAA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCKYKDJM; Sat, 11 Aug 2001 13:07:50 EDT
To: djb@cr.yp.to
Cc: idn@ops.ietf.org
Date: Sat, 11 Aug 2001 10:08:08 -0700
Subject: Re: [idn] IDNs do not use ASCII
Message-ID: <20010811.102452.-1034535.1.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.11
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

1. The world has to tolerate English only DNS long enough. 
2. For IDN, if a user kick and scream when he sees bq--blah
 then he can buy an application which only shows BQ--BLAH.

Liana

On 11 Aug 2001 00:14:31 -0000 "D. J. Bernstein" <djb@cr.yp.to> writes:
> Adam M. Costello writes:
> > Now <lowercase-pi> and <uppercase-pi> and bq--blah and BQ--BLAH 
> etc.
> > are all equivalent.
> 
> That's ridiculous. The user wants to see lowercase pi. He might 
> tolerate
> uppercase pi, but he will kick and scream if he sees bq--blah.
> 
> This is typical of your arguments: you show us the road to failure, 
> you
> define failure as being equivalent to success, and you claim 
> success.
> Sorry, Adam, but that isn't what the users want to see.
> 
> ---Dan
> 



From owner-idn@ops.ietf.org  Sat Aug 11 13:41: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 NAA07703
	for <idn-archive@lists.ietf.org>; Sat, 11 Aug 2001 13:41:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VcFN-0006hi-00
	for idn-data@psg.com; Sat, 11 Aug 2001 10:08:25 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15VcFM-0006hc-00
	for idn@ops.ietf.org; Sat, 11 Aug 2001 10:08:24 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+3nwGBQ7c9H0HVYbWC8dFs79Jtq+16bEQ==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCKYKDHN; Sat, 11 Aug 2001 13:07:50 EDT
To: mark@macchiato.com
Cc: liana.ydisg@juno.com, Erik.Nordmark@eng.sun.com, amc@cs.berkeley.edu,
        idn@ops.ietf.org
Date: Sat, 11 Aug 2001 09:47:00 -0700
Subject: Re: [idn] SC/TC equivalence
Message-ID: <20010811.102452.-1034535.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-3,5-145
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

Sorry, I can not read your reply.

Liana 

On Fri, 10 Aug 2001 12:57:04 -0700 "Mark Davis" <mark@macchiato.com>
writes:
> Huh?
> â€”â€”â€”â€”â€?
> 
> Ï€Î¬Î½Ï„Ï‰Î½ Î¼Î­Ï„Ï�Î¿Î½ á¼„Î½Î¸Ï�Ï‰Ï€Î¿Ï‚ â€?Î Ï�Ï‰Ï„Î±Î³ÏŒÏ�Î±Ï‚
> [http://www.macchiato.com]
> 
> ----- Original Message -----
> From: <liana.ydisg@juno.com>
> To: <mark@macchiato.com>
> Cc: <Erik.Nordmark@eng.sun.com>; <amc@cs.berkeley.edu>; 
> <idn@ops.ietf.org>
> Sent: Friday, August 10, 2001 12:48
> Subject: Re: [idn] SC/TC equivalence
> 
> 
> > The statement is correct to the extent that every home has
> > a good collection of books, but the extent to the satement is:
> >  so we don't need a library in the city, that is where we depart.
> >
> > Liana
> >
> >
> > On Fri, 10 Aug 2001 10:28:02 -0700 "Mark Davis" 
> <mark@macchiato.com>
> > writes:
> > > For SC/TC equivalence, the feedback I have gotten is that "In
> > > practice, most
> > > Chinese would expect either simplified or traditional, but not a
> > > mixture of
> > > both", and from another writer, "Simplified and traditional are
> > > usually used in their own contexts, and a domain name is a single
> > > context,
> > > and thus wouldn't result in a mixture of the two systems."
> > >
> > > If that is true, then for TC/SC, unlike case, registering 
> exactly two
> > > variants of any particular domain name would be sufficient; one
> > > would not
> > > have to register n^2 combinations. Given that, registering SC/TC
> > > variants is
> > > much more like registering two different languages and/or 
> scripts,
> > > something
> > > best left to documentation instead of changing nameprep.
> > >
> > > Mark
> > >
> > > â€”â€”â€”â€?
> > >
> > >  Î¬Î½Ï„Ï‰Î½ Î¼Î­Ï„Ï�Î¿Î½ á¼„Î½Î¸Ï�Ï‰Ï€Î¿Ï‚ ? Ï�Ï‰Ï„Î±Î³ÏŒÏ�Î±Ï‚
> > > [http://www.macchiato.com]
> > >
> > > ----- Original Message -----
> > > From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> > > To: "Adam M. Costello" <amc@cs.berkeley.edu>
> > > Cc: <idn@ops.ietf.org>
> > > Sent: Thursday, August 09, 2001 23:47
> > > Subject: Re: [idn] SC/TC equivalence
> > >
> > >
> > > >
> > > > > Thank you!  One thing that should be considered by anyone
> > > contemplating
> > > > > server-side equivalence rules is that clients will not know 
> that
> > > the
> > > > > names are equivalent.  For web browsers, this will affect
> > > visited link
> > > > > coloring, page caching, cookie permissions, etc.  Similar
> > > pitfalls will
> > > > > exist in other applications.  Zone administrators willing to
> > > tolerate
> > > > > such limitations are free to do server-side equivalence 
> matching
> > > to
> > > > > their heart's content.  It would be ludicrous for this 
> working
> > > group to
> > > > > try to prohibit this practice, because it's equivalent to
> > > populating the
> > > > > zone with identical data for all the matching names, which is
> > > obviously
> > > > > permitted.
> > > >
> > > > I don't think this WG prohibits this - it shouldn't as far as I
> > > can tell.
> > > > But the ability of the client to tell
> > > > that it got the right answer to a DNS query does add some 
> severe
> > > constraints.
> > > > [I assume DNS protocol experts will correct me if I got thins
> > > wrong.]
> > > >
> > > > If the client asks for A and gets a respose with QNAME A' and
> > > answer X
> > > then how
> > > > does the client know that it wasn't spoofed? Applying DNSSEC 
> would
> > > just
> > > tell
> > > > the client that X is indeed the answer to the question for A'.
> > > >
> > > > So unless the server mains records for both A and A' (with 
> their
> > > SIGs)
> > > > (where A and A' really expand to all the possible combinations 
> as
> > > in
> > > > the UNAME) then the client needs to verify that A and A'
> > > > match.
> > > >
> > > >
> > > > Thus there seem to be two choices:
> > > >  - client sends A to server
> > > >  - server folds A to A' (A' := nameprep(A)), looks up A' and
> > > responds to
> > > client
> > > >  - client verifies that A and A' are the same by checking
> > > nameprep(A) = A'
> > > >    (to prevent being spoofed)
> > > >
> > > > OR
> > > >  - client does A' := nameprep(A), sends A' to server
> > > >  - server looks up A' and responds to client
> > > >  - done
> > > >
> > > > Thus client might as well do the nameprep before composing the
> > > query
> > > > and save the work in the server.
> > > >
> > > >   Erik
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> 



From owner-idn@ops.ietf.org  Sat Aug 11 14:18: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 OAA07975
	for <idn-archive@lists.ietf.org>; Sat, 11 Aug 2001 14:18:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Vd9I-0007a9-00
	for idn-data@psg.com; Sat, 11 Aug 2001 11:06:12 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Vd9H-0007a3-00
	for idn@ops.ietf.org; Sat, 11 Aug 2001 11:06:11 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+3nwGBQ7c9HFq0ITbmfBJfCDezllAvj8g==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCK3UU74; Sat, 11 Aug 2001 14:05:27 EDT
To: mark@macchiato.com
Cc: mark@macchiato.com, Erik.Nordmark@eng.sun.com, amc@cs.berkeley.edu,
        idn@ops.ietf.org
Date: Sat, 11 Aug 2001 11:22:15 -0700
Subject: [idn] SC/TC equivalence
Message-ID: <20010811.112220.-841419.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

The statement is correct to the extent that every home has
a good collection of books, but the extent to the satement is:
 so we don't need a library in the city, that is where we depart.

[nameprep] is the place for case folding for Latin, then it should
be the place for other script folding as well.  If [nameprep]
is too complex, than it can be a directory type architecture using
language tag as keys.  If [nameprep] does not deal with 
SC/TC equivalence then we are back to the discussion to
two months ago.   Are there any draft demostrating how 
 [nameprep] process each incoming Unicode string step by 
step?

Liana

On Fri, 10 Aug 2001 10:28:02 -0700 "Mark Davis" <mark@macchiato.com>
writes:
> For SC/TC equivalence, the feedback I have gotten is that "In 
> practice, most
> Chinese would expect either simplified or traditional, but not a 
> mixture of
> both", and from another writer, "Simplified and traditional are
> usually used in their own contexts, and a domain name is a single 
> context,
> and thus wouldn't result in a mixture of the two systems."
> 
> If that is true, then for TC/SC, unlike case, registering exactly two
> variants of any particular domain name would be sufficient; one 
> would not
> have to register n^2 combinations. Given that, registering SC/TC 
> variants is
> much more like registering two different languages and/or scripts, 
> something
> best left to documentation instead of changing nameprep.
> 
> Mark
> 
> â€”â€”â€”â€”â€?
> 
> Ï€Î¬Î½Ï„Ï‰Î½ Î¼Î­Ï„Ï�Î¿Î½ á¼„Î½Î¸Ï�Ï‰Ï€Î¿Ï‚ â€?Î Ï�Ï‰Ï„Î±Î³ÏŒÏ�Î±Ï‚
> [http://www.macchiato.com]
> 
> ----- Original Message -----
> From: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
> To: "Adam M. Costello" <amc@cs.berkeley.edu>
> Cc: <idn@ops.ietf.org>
> Sent: Thursday, August 09, 2001 23:47
> Subject: Re: [idn] SC/TC equivalence
> 
> 
> >
> > > Thank you!  One thing that should be considered by anyone 
> contemplating
> > > server-side equivalence rules is that clients will not know that 
> the
> > > names are equivalent.  For web browsers, this will affect 
> visited link
> > > coloring, page caching, cookie permissions, etc.  Similar 
> pitfalls will
> > > exist in other applications.  Zone administrators willing to 
> tolerate
> > > such limitations are free to do server-side equivalence matching 
> to
> > > their heart's content.  It would be ludicrous for this working 
> group to
> > > try to prohibit this practice, because it's equivalent to 
> populating the
> > > zone with identical data for all the matching names, which is 
> obviously
> > > permitted.
> >
> > I don't think this WG prohibits this - it shouldn't as far as I 
> can tell.
> > But the ability of the client to tell
> > that it got the right answer to a DNS query does add some severe
> constraints.
> > [I assume DNS protocol experts will correct me if I got thins 
> wrong.]
> >
> > If the client asks for A and gets a respose with QNAME A' and 
> answer X
> then how
> > does the client know that it wasn't spoofed? Applying DNSSEC would 
> just
> tell
> > the client that X is indeed the answer to the question for A'.
> >
> > So unless the server mains records for both A and A' (with their 
> SIGs)
> > (where A and A' really expand to all the possible combinations as 
> in
> > the UNAME) then the client needs to verify that A and A'
> > match.
> >
> >
> > Thus there seem to be two choices:
> >  - client sends A to server
> >  - server folds A to A' (A' := nameprep(A)), looks up A' and 
> responds to
> client
> >  - client verifies that A and A' are the same by checking 
> nameprep(A) = A'
> >    (to prevent being spoofed)
> >
> > OR
> >  - client does A' := nameprep(A), sends A' to server
> >  - server looks up A' and responds to client
> >  - done
> >
> > Thus client might as well do the nameprep before composing the 
> query
> > and save the work in the server.
> >
> >   Erik
> >
> >
> >
> >
> 
> 



From owner-idn@ops.ietf.org  Sat Aug 11 15:22: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 PAA08350
	for <idn-archive@lists.ietf.org>; Sat, 11 Aug 2001 15:22:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VeCq-0008c7-00
	for idn-data@psg.com; Sat, 11 Aug 2001 12:13:56 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15VeCq-0008c1-00
	for idn@ops.ietf.org; Sat, 11 Aug 2001 12:13:56 -0700
Received: from amc by nicemice.net with local (Exim 3.31 #1 (Debian))
	id 15VeCp-0007CP-00
	for <idn@ops.ietf.org>; Sat, 11 Aug 2001 12:13:55 -0700
Date: Sat, 11 Aug 2001 19:13:55 +0000
From: "Adam M. Costello" <amc@cs.berkeley.edu>
To: idn@ops.ietf.org
Subject: Re: [idn] SC/TC equivalence
Message-ID: <20010811191355.A27606@nicemice.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20010811.112220.-841419.0.liana.ydisg@juno.com>
User-Agent: Mutt/1.3.18i
Sender: owner-idn@ops.ietf.org
Precedence: bulk

liana.ydisg@juno.com wrote:

> [nameprep] is the place for case folding for Latin, then it should be
> the place for other script folding as well.

That's a valid argument, but there are also some counter-arguments:

Existing domain names are already case-insensitive, so IDNs ought to
be case-insensitive for consistency with the current standard.  This
consistency constraint does not apply to SC/TC equivalence.

With very few exceptions, case mapping is one-to-one.  SC/TC mapping is
more complex more often.

The case mapping rules are already defined in the Unicode standard.
This is not true for SC/TC mapping.

Some people have expressed a desire to be able to register the
simplified and traditional versions of a name as separate domain names.
No one has expressed an analogous desire to be able to register the
all-uppercase and all-lowercase versions of a name as separate domain
names.

AMC



From owner-idn@ops.ietf.org  Sat Aug 11 16:53: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 QAA08845
	for <idn-archive@lists.ietf.org>; Sat, 11 Aug 2001 16:53:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VfZp-0009qI-00
	for idn-data@psg.com; Sat, 11 Aug 2001 13:41:45 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15VfZo-0009qA-00
	for idn@ops.ietf.org; Sat, 11 Aug 2001 13:41:44 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Sat, 11 Aug 2001 13:53:12 -0700
Message-ID: <004001c122a7$3e1daea0$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>
References: <20010811.102452.-1034535.2.liana.ydisg@juno.com>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Sat, 11 Aug 2001 16:50:22 -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, Ben,
>    .tw is used mostly by users who want TC characters,
> and .cn users mostly wants SC characters.  As a service

"used mostly" is not good enough.  Either they use all TC or all SC.
If not, then there must be a SC/TC equivalence

> provider, you can display .tw as .taiwan in TC, and display
> .cn as .china in SC character set.   When people click on
> the URL, you send out .tw to DNS instead of .taiwan in TC.
> This way you can provide what the user wants to see
> without bother DNS.

Yes, you are correct that .tw is the same as <.taiwan> and .cn is the
same as <.china>- BUT ONLY if the either the ISP or the client
downloaded special software.  Also, TC and SC are used interchangeably
regardless of country so <.taiwan> does not mean TC and <.china> does
not mean SC.  That is the whole point of TC<->SC equivalence.

Thanks
Ben Chan



>
> Liana
>
> On Sat, 11 Aug 2001 09:54:56 -0400 "ben" <ben@cc-www.com> writes:
> > Hi Liana,
> >
> > I am not sure I understand what you are trying to say.
> >
> > Thanks
> > Ben Chan
> >
> >
> > ----- Original Message -----
> > From: <liana.ydisg@juno.com>
> > To: <edmon@neteka.com>
> > Cc: <liana.ydisg@juno.com>; <klensin@research.att.com>;
> > <idn@ops.ietf.org>
> > Sent: Friday, August 10, 2001 3:24 PM
> > Subject: Re: [idn] opting out of SC/TC equivalence
> >
> >
> > You got my point wrong.  We are not in the same discussion
> > space.  SC=TC discussion is only regarding font difference.
> > The semantics are basicaly the same, but the reader groups
> > are different.  It may be said, this is analogy to Latin uppercase
> > and lowercase folding.   As a registrant, if the choice is two
> > places: SC+TC, then it is a reality already, we don't need this
> > standard discussion right now.   And to Ben Chan also,
> >  we have TLD are doing exactly the same thing:  .tw and .cn
> > too.  As a server provider, you may choose to display .tw in TC,
and
> > cn
> > in SC as an equivalent solution to your suggestion without
> > get into this WG.
> >
> > Liana
> >





From owner-idn@ops.ietf.org  Sat Aug 11 22:05: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 WAA11407
	for <idn-archive@lists.ietf.org>; Sat, 11 Aug 2001 22:05:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Vk5N-000E5I-00
	for idn-data@psg.com; Sat, 11 Aug 2001 18:30:37 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Vk5M-000E5C-00
	for idn@ops.ietf.org; Sat, 11 Aug 2001 18:30:36 -0700
Received: from soobok ([210.217.27.237] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id KAA06298
	for <idn@ops.ietf.org>; Sun, 12 Aug 2001 10:30:25 +0900
Message-ID: <014201c122ce$cd181740$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
References: <20010811191355.A27606@nicemice.net>
Subject: Re: [idn] SC/TC equivalence
Date: Sun, 12 Aug 2001 10:33:33 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Adam M. Costello" <amc@cs.berkeley.edu>

> liana.ydisg@juno.com wrote:
>
> > [nameprep] is the place for case folding for Latin, then it should be
> > the place for other script folding as well.
>
> That's a valid argument, but there are also some counter-arguments:
>
> Existing domain names are already case-insensitive, so IDNs ought to
> be case-insensitive for consistency with the current standard.  This
> consistency constraint does not apply to SC/TC equivalence.
>

This is a really controversial issue.

NAMEPREP also applies additional equivalence rules in addition to
case-folding:
   1) compatibility decomposition
   2) canonical composition

What is the difference between these equivalences and SC/TC equivalence?


> With very few exceptions, case mapping is one-to-one.  SC/TC mapping is
> more complex more often.
>
> The case mapping rules are already defined in the Unicode standard.
> This is not true for SC/TC mapping.
>
The Unicord Standard is not the only document we can refer to.
I have no doubt about the accuracy of CNNIC-provided SC/TC mapping tables.


> Some people have expressed a desire to be able to register the
> simplified and traditional versions of a name as separate domain names
> No one has expressed an analogous desire to be able to register the
> all-uppercase and all-lowercase versions of a name as separate domain
> names.
>

If  SC/TC equivalence is like the equivalence between  "humor" and "humour",
registration/dispute resolution policy may be the right path to solve this
issue.

But, if SC/TC equivalence is like the equivalence between "H" and "h",
we should fold them. BTW, in which direction ?    SC->TC or TC->SC?
How can we recover the pre-normalization form of folded TC/SC domains?


--LSB





From owner-idn@ops.ietf.org  Sun Aug 12 02:57: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 CAA00458
	for <idn-archive@lists.ietf.org>; Sun, 12 Aug 2001 02:57:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Vopn-000IuS-00
	for idn-data@psg.com; Sat, 11 Aug 2001 23:34:51 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Vopm-000IuM-00
	for idn@ops.ietf.org; Sat, 11 Aug 2001 23:34:51 -0700
Received: from jamessonyvaio (58foxtrot177.singnet.com.sg [165.21.222.218])
	by mail.i-dns.net (Postfix) with SMTP
	id 83F4EFFC03; Sun, 12 Aug 2001 14:36:15 +0800 (SGT)
Message-ID: <002201c122f8$dcff30b0$0201000a@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
References: <20010810171935.6159.qmail@cr.yp.to> <20010810224319.D23949@arwen.cs.berkeley.edu> <20010811001431.22378.qmail@cr.yp.to>
Subject: Re: [idn] IDNs do not use ASCII
Date: Sun, 12 Aug 2001 01:37: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.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Adam M. Costello writes:
> > Now <lowercase-pi> and <uppercase-pi> and bq--blah and BQ--BLAH etc.
> > are all equivalent.
>
> That's ridiculous. The user wants to see lowercase pi. He might
tolerate
> uppercase pi, but he will kick and scream if he sees bq--blah.

Agree. ACE leaks horribly. When ACE leaks, users will see bq--gibberish
and they would be scratching their head.

But when UTF-8 leaks, which is common, users will see some 8-bit
gibberish and they would be scratching their head too.

Bottomline: Both ACE and UTF-8 leaks. No one can make sure it wont
without fixing the UI/Application.

-James Seng





From owner-idn@ops.ietf.org  Sun Aug 12 03:14: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 DAA01508
	for <idn-archive@lists.ietf.org>; Sun, 12 Aug 2001 03:14:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VpJt-000JZN-00
	for idn-data@psg.com; Sun, 12 Aug 2001 00:05:57 -0700
Date: Sun, 12 Aug 2001 03:38:35 +0000
From: "Adam M. Costello" <amc@cs.berkeley.edu>
To: idn@ops.ietf.org
Subject: Re: [idn] SC/TC equivalence
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15VpJt-000JZN-00@psg.com>

Soobok Lee <lsb@postel.co.kr> wrote:

>    1) compatibility decomposition
>    2) canonical composition
>
> What is the difference between these equivalences and SC/TC
equivalence?

That's a good question.  I consulted the Unicode standard for the
answer.  Canonically equivalent sequences are defined to be fully
equivalent.  Conformant processes are required to interpret canonically
equivalent sequences as the same (section 3.1 Conformance Requirements
--> Interpretation --> C9).  Compatibility characters are characters
that have compatibility decompositions.  They only reason they are
included in Unicode is for compatibility with other standards (to
allow lossless round-trip conversions).  Performing compatibility
decomposition removes only formatting information (which shouldn't
really be present in plain text in the first place).  (See section 3.6
Decomposition, and section 2.2 Unicode Design Principles --> Unification
--> Compatibility Characters.)

Apparently the Unicode folks judged that the difference between
simplified Chinese characters and traditional Chinese characters is
more significant than just formatting information, because they are not
compatible equivalents.

I think users understand that a simplified character and a traditional
character are two distinguishable things, even though some users might
wish for them to be interchangeable.  If they're not interchangeable,
some users might be a little annoyed, but at least they won't be
mystified.

Compatible equivalents, on the other hand, are things like ligature
fi versus separate fi.  Most people have never noticed that f and
i sometimes get joined.  People would be completely mystified if
ligature fi were not treated the same as separate fi.  Other compatible
equivalents are roman numeral IV versus letters IV, and fullwidth
A versus halfwidth A.  These are not merely characters with the
same meaning, they are really the same characters, just formatted
differently.

> If SC/TC equivalence is like the equivalence between "humor" and
> "humour",
>
> But, if SC/TC equivalence is like the equivalence between "H" and "h",

It's not exactly like either of those, but to me it looks closer to
humor/humour.

AMC





From owner-idn@ops.ietf.org  Sun Aug 12 08: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 IAA13999
	for <idn-archive@lists.ietf.org>; Sun, 12 Aug 2001 08:16:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15VtsB-000OHV-00
	for idn-data@psg.com; Sun, 12 Aug 2001 04:57:39 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Vts9-000OHO-00
	for idn@ops.ietf.org; Sun, 12 Aug 2001 04:57:37 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+3nwGBQ7c9HXQdTMjrcbN/BhES3ggqy0g==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCMY7F4Z; Sun, 12 Aug 2001 07:57:17 EDT
To: amc@cs.berkeley.edu
Cc: idn@ops.ietf.org
Date: Sun, 12 Aug 2001 05:14:07 -0700
Subject: Re: [idn] SC/TC equivalence
Message-ID: <20010812.051415.-1034443.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-64,66-75,77-106
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

All the counter-arguments are valid.

1. SC/TC equivalence is similar to case folding for Latin, only 
it is a lot more larger.  When it is large, there comes with a variety
cases of equivalence.  All the examples mentioned exist for CJK,
but it is not deter the primary characteristics of a case folding.

2. From a user's viewpoint, the requirement is multitude.  
SC is a simpler set of CJK then TC. But users in China want 
TC in their names for artistic, special appealing, and specific
semantics in the TC.  Users outside of China, want SC for 
marketing to China, and simpler names (especial  the 
younger generations) for themselves to master.  Hong Kong 
is a good place to observe both of these users' wish-lists. 

3. To be handled reasonably for the above requirements, it is
reasonable to treat SC/TC as case-insensitive identifiers, 
consistent with DNS tradition, and only provide simple and
portable communication functionality to users from this 
standard body, and let applications deal with secondary 
equivalence issues. 

4. Unicode is large, so [nameprep] is large too.  However,
Unicode is a database.  It is up to us to use it efficiently.   
SC/TC case folding is large too,  but it is just a large table
sitting inside or next to Unicode for a look up search.  If we 
are  thinking [nameprep] in term of database lookup, then 
we can exclude many possible ACE leaks.  For example,
a string of whatever bit-stream comes in.  [nameprep]
trys to interpret it in, say, as 16-bits unit, and limits the 
range of searching say to Hindi script.   Anything outside
this Hindi script range, the input  becomes illegal and is 
kicked back as bad input.   Everything inside Hindi script 
range is filtered out for case folding and etc.  It is unlikely, 
we will have any script look alike confusion with this 
exclusion method. 

5.  If the above input is a CJK string, then we have a huge
range to worry about, it is another C[nameprep], J[nameprep]
and K[nameprep].  CNNIC have plenty of experts in 
handling this indivadually and very efficient too.  It is just an 
AI oriented code table search.

6. Though, [nameprep] becomes at least four [nameprep]s, 
which sounds a lot more complex,  by treating
[nameprep] as a database, and treating [nameprep] 
processing as a switch box,   a divide and conquer scheme
shall handle the problem and each section of the problem 
becomes minimal.

7. As to SC/TC case folding, I am proposing to fold to muemonic
ACE.  The ACE can be recovered to either SC or TC at the 
mercy of the application, or the presentation layer.  It is likely
that servers in the Mainland display everything in SC, and servers
in Taiwan display everything TC, regardless where the original
e-mail comes from.   I would be happy to see either regardless
where the e-mail comes from.   

If someone wants both versions then he can ask for a feature
 from the application to display 
either.   If he wants two different hostnames, he can do 1) what is
available now, by registering one in China, another one in Taiwan.  
2) By using the second step of StepCode to specify particular 
parts of its character, to get a different mnemonic ACE from the
first registered hostname, which shall force the application to
either interprate the ACE differently, or get the original registered
copy.
 If  the application does a good job to make its user happy, then 
there is no need to ask for the pre-folded case.  If someone 
demand the original copy, then the application shall request one
 from the original registrar, (not from [nameprep]) and keep that 
copy in its cache. 

Liana 


On Sat, 11 Aug 2001 19:13:55 +0000 "Adam M. Costello"
<amc@cs.berkeley.edu> writes:
> liana.ydisg@juno.com wrote:
> 
> > [nameprep] is the place for case folding for Latin, then it should 
> be
> > the place for other script folding as well.
> 
> That's a valid argument, but there are also some counter-arguments:
> 
> Existing domain names are already case-insensitive, so IDNs ought to
> be case-insensitive for consistency with the current standard.  This
> consistency constraint does not apply to SC/TC equivalence.
> 
> With very few exceptions, case mapping is one-to-one.  SC/TC mapping 
> is
> more complex more often.
> 
> The case mapping rules are already defined in the Unicode standard.
> This is not true for SC/TC mapping.
> 
> Some people have expressed a desire to be able to register the
> simplified and traditional versions of a name as separate domain 
> names.
> No one has expressed an analogous desire to be able to register the
> all-uppercase and all-lowercase versions of a name as separate 
> domain
> names.
> 
> AMC
> 



From owner-idn@ops.ietf.org  Sun Aug 12 08:16: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 IAA14000
	for <idn-archive@lists.ietf.org>; Sun, 12 Aug 2001 08:16:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Vts2-000OGx-00
	for idn-data@psg.com; Sun, 12 Aug 2001 04:57:30 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Vts1-000OGi-00
	for idn@ops.ietf.org; Sun, 12 Aug 2001 04:57:29 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+3nwGBQ7c9HH3O3omoGSEVzDa3/VTRQDQ==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCMY7F3P; Sun, 12 Aug 2001 07:57:17 EDT
To: ben@cc-www.com
Cc: liana.ydisg@juno.com, idn@ops.ietf.org
Date: Sun, 12 Aug 2001 04:06:43 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010812.051415.-1034443.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

Agree.  That is the reason we have to do this standard.

Liana

On Sat, 11 Aug 2001 16:50:22 -0400 "ben" <ben@cc-www.com> writes:
> > Hi, Ben,
> >    .tw is used mostly by users who want TC characters,
> > and .cn users mostly wants SC characters.  As a service
> 
> "used mostly" is not good enough.  Either they use all TC or all SC.
> If not, then there must be a SC/TC equivalence
> 
> > provider, you can display .tw as .taiwan in TC, and display
> > .cn as .china in SC character set.   When people click on
> > the URL, you send out .tw to DNS instead of .taiwan in TC.
> > This way you can provide what the user wants to see
> > without bother DNS.
> 
> Yes, you are correct that .tw is the same as <.taiwan> and .cn is 
> the
> same as <.china>- BUT ONLY if the either the ISP or the client
> downloaded special software.  Also, TC and SC are used 
> interchangeably
> regardless of country so <.taiwan> does not mean TC and <.china> 
> does
> not mean SC.  That is the whole point of TC<->SC equivalence.
> 
> Thanks
> Ben Chan
> 
> 
> 
> >
> > Liana
> >
> > On Sat, 11 Aug 2001 09:54:56 -0400 "ben" <ben@cc-www.com> writes:
> > > Hi Liana,
> > >
> > > I am not sure I understand what you are trying to say.
> > >
> > > Thanks
> > > Ben Chan
> > >
> > >
> > > ----- Original Message -----
> > > From: <liana.ydisg@juno.com>
> > > To: <edmon@neteka.com>
> > > Cc: <liana.ydisg@juno.com>; <klensin@research.att.com>;
> > > <idn@ops.ietf.org>
> > > Sent: Friday, August 10, 2001 3:24 PM
> > > Subject: Re: [idn] opting out of SC/TC equivalence
> > >
> > >
> > > You got my point wrong.  We are not in the same discussion
> > > space.  SC=TC discussion is only regarding font difference.
> > > The semantics are basicaly the same, but the reader groups
> > > are different.  It may be said, this is analogy to Latin 
> uppercase
> > > and lowercase folding.   As a registrant, if the choice is two
> > > places: SC+TC, then it is a reality already, we don't need this
> > > standard discussion right now.   And to Ben Chan also,
> > >  we have TLD are doing exactly the same thing:  .tw and .cn
> > > too.  As a server provider, you may choose to display .tw in TC,
> and
> > > cn
> > > in SC as an equivalent solution to your suggestion without
> > > get into this WG.
> > >
> > > Liana
> > >
> 
> 



From joinda1@hotmail.com  Sun Aug 12 18:21: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 SAA19415
	for <idn-archive@lists.ietf.org>; Sun, 12 Aug 2001 18:21:51 -0400 (EDT)
Received: from [211.186.118.26] (helo=hong)
	by psg.com with smtp (Exim 3.31 #1)
	id 15W3C6-0009jN-00
	for idn-data@psg.com; Sun, 12 Aug 2001 14:54:50 -0700
From: =?ks_c_5601-1987?B?yKu8usf2?= <joinda1@hotmail.com>
To: idn-data@psg.com
Subject: =?ks_c_5601-1987?B?aWRuLWRhdGG01CC9x7fKx9W0z7TZLg==?=
Date: Mon, 13 Aug 2001 07:01:23 +0900
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0077_01C0F13A.93A01C00"
X-Priority: 3
Message-Id: <E15W3C6-0009jN-00@psg.com>

This is a multi-part message in MIME format.

------=_NextPart_000_0077_01C0F13A.93A01C00
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

vsiz58fPvLy/5A0Kvsiz58fPvLy/5CBpZG4tZGF0YbTULi4uICANCsClILytx87B3yBodHRw
Oi8vbm5jLm5pYy5vci5rci9tYWlsL3dnLWRlcGxveS8wMDM3Lmh0bWwgsNS9w8bHv6Egtem+
7rCstNmwoSC6y7DUtce+7iDAzLe4sNQguN7Az8C7ILXlt8G6vrTPtNkuIA0Kx+O29L74wMwg
uN7Az8C7ILq4s7u15bfBIMHLvNvHz7/AuOcsIMGkwd/I9yC+58fYuKYgus7FubXluK6w2r3A
tM+02S4gDQrHz8H2uLggwaS4uyC1tb/ywMwgtcm89sDWtMIgwcHAusGkuri4piC+y7fBteW4
rrDtIL3Nvu68rSDAzLe4sNQgw6O+xrrLsNQgtce++r3AtM+02SANCi0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0K
DQoxLr7cxvm/oSC068fPv6kuLi4NCiAgICAgaHR0cDovL3d3dy5hdHBob25lLmNvbSAvIMfg
u+cgxKvFu7fOsdcgLyC+3Mb5vLO47Q0KICrH2rXlxvkvvcOzuy+9w7/cIMD8yK2woSC/+TE4
MDAwv/ggwMy46SDG8rv9ILmrwabH0SC757/rKg0KICAgDQoyLrvnvvfGxMaus8oguPDB/SjF
rLivx9jB1ry8v+QpDQogIA0Ks6Gx7sH2IMDQvu4gwda8xbytIMGkuLsgsKi757XluK645w0K
ILDHsK3Hz73DsO0gx8+9w7TCIMDPIMDftce9w7HmILnZtvi0z7TZLg0KILHXt7Mgvsiz58j3
Li4uDQoNCiq+3Mb5QLmuwMcgOiDApSDG+SCY3iAoQlNsaW5lKSA6IDAyLTU0NS02MTk5DQoq
u+e+98bExq6zyiC5rsDHIDogMDItNTE3LTAxMjYgLyAwMTktOTczMi02MDk2DQo=

------=_NextPart_000_0077_01C0F13A.93A01C00
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

PGh0bWw+DQoNCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1MYW5ndWFnZSIg
Y29udGVudD0ia28iPg0KPG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50
PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9a3NfY181NjAxLTE5ODciPg0KPG1ldGEgbmFtZT0iR0VO
RVJBVE9SIiBjb250ZW50PSJNaWNyb3NvZnQgRnJvbnRQYWdlIDQuMCI+DQo8bWV0YSBuYW1l
PSJQcm9nSWQiIGNvbnRlbnQ9IkZyb250UGFnZS5FZGl0b3IuRG9jdW1lbnQiPg0KPHRpdGxl
Pr7Is+fHz7y8v+Q8L3RpdGxlPg0KPC9oZWFkPg0KDQo8Ym9keT4NCg0KPHA+PGZvbnQgc2l6
ZT0iMiI+vsiz58fPvLy/5CA8Zm9udCBjb2xvcj0iIzAwMDBmZiI+aWRuLWRhdGE8L2ZvbnQ+
tNQuLi4mbmJzcDsgPGZvbnQgZmFjZT0isby4ssO8Ij48Zm9udCBmYWNlPSKxvLiyw7wiIGNv
bG9yPSIjMDAwMGZmIj48YnI+DQo8L2ZvbnQ+wKUgvK3HzsHfPGZvbnQgZmFjZT0isby4ssO8
IiBjb2xvcj0iIzAwMDBmZiI+IGh0dHA6Ly9ubmMubmljLm9yLmtyL21haWwvd2ctZGVwbG95
LzAwMzcuaHRtbDwvZm9udD48Zm9udCBjb2xvcj0iYmx1ZSI+ICAgDQo8L2ZvbnQ+PGZvbnQg
Y29sb3I9IiMwMDAwZmYiPrDUvcPGxzwvZm9udD6/oTxmb250IGNvbG9yPSIjMDAwMGZmIj4g
PC9mb250PjwvZm9udD616b7usKy02bChICAgIA0Kusuw1LXHvu4gwMy3uLDUILjewM/AuyC1
5bfBur60z7TZLiA8YnI+ICAgDQrH47b0vvjAzCC43sDPwLsgurizu7Xlt8Egwcu828fPv8C4
5ywgwaTB38j3IDxmb250IGNvbG9yPSIjMDAwMGZmIj48Yj6+58fYPC9iPjwvZm9udD64piAg
ICANCrrOxbm15biusNq9wLTPtNkuIDxicj4NCsfPwfa4uCDBpLi7ILW1v/LAzCC1ybz2wNa0
wiA8Zm9udCBjb2xvcj0iIzAwMDBmZiI+PGI+wcHAusGkurg8L2I+PC9mb250PrimICAgIA0K
vsu3wbXluK6w7SC9zb7uvK0gwMy3uLDUIMOjvsa6y7DUILXHvvq9wLTPtNk8L2ZvbnQ+PGZv
bnQgc2l6ZT0iMyI+ICAgIA0KPGJyPg0KPC9mb250Pi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTwvcD4NCjxwPjxi
Pjxmb250IHNpemU9IjQiPjEuPGZvbnQgY29sb3I9IiNGRjAwMDAiPr7cxvk8L2ZvbnQ+v6Eg
tOvHz7+pPC9mb250Pjxmb250IHNpemU9IjMiPi4uLjxicj4gDQombmJzcDsgPC9mb250Pjwv
Yj4mbmJzcDsgPGI+PGZvbnQgc2l6ZT0iNCI+PGEgaHJlZj0iaHR0cDovL3d3dy5hdHBob25l
LmNvbSI+aHR0cDovL3d3dy5hdHBob25lLmNvbTwvYT4gICANCi8gPGEgaHJlZj0iaHR0cDov
L215LmRyZWFtd2l6LmNvbS9haWdvMS9hdCI+x+C75yDEq8W7t86x1zwvYT4gLyA8YSBocmVm
PSJodHRwOi8vbXkuZHJlYW13aXouY29tL2FpZ28xL2F0LWxpbmsiPr7cxvm8s7jtPC9hPjwv
Zm9udD48L2I+PGZvbnQgc2l6ZT0iNSI+PGI+PGEgaHJlZj0iaHR0cDovL3d3dy5hdHBob25l
LmNvbSI+PGJyPg0KPC9hPjwvYj48L2ZvbnQ+Jm5ic3A7PGI+PGZvbnQgY29sb3I9IiNmZjAw
MDAiIHNpemU9IjQiPirH2rXlxvkvvcOzuy+9w7/cIA0KwPzIrbChIDwvZm9udD48Zm9udCBz
aXplPSI1IiBjb2xvcj0iIzAwMDBGRiI+v/kxODAwML/4PC9mb250Pjxmb250IGNvbG9yPSIj
ZmYwMDAwIiBzaXplPSI0Ij4gDQrAzLjpIMbyu/0guavBpsfRILvnv+s8L2ZvbnQ+PGZvbnQg
Y29sb3I9IiNmZjAwMDAiIHNpemU9IjQiPio8YnI+DQo8L2ZvbnQ+PC9iPiZuYnNwOzxiPjxm
b250IHNpemU9IjQiPiZuYnNwOyA8L2ZvbnQ+PGZvbnQgc2l6ZT0iNSI+PGJyPg0KPC9mb250
PjwvYj48Yj48Zm9udCBzaXplPSI0Ij4yLjxhIGhyZWY9Imh0dHA6Ly9teS5kcmVhbXdpei5j
b20vYWlnbzEvc3AtbGluayI+u+e+98bExq6zyiANCrjwwf0oxay4r8fYwda8vL/kKTwvYT48
YnI+DQombmJzcDsgPC9mb250PjwvYj48Zm9udCBzaXplPSI0Ij48Yj48YnI+DQqzobHuwfYg
wNC+7iDB1rzFvK0gwaS4uyCwqLvnteW4rrjnPGJyPiANCrDHsK3Hz73DsO0gx8+9w7TCIMDP
IMDftce9w7HmILnZtvi0z7TZLjwvYj48L2ZvbnQ+PGI+PGJyPiANCrHXt7Mgvsiz58j3Li4u
PGZvbnQgc2l6ZT0iNCI+PGJyPg0KPGJyPg0KKjxmb250IGNvbG9yPSIjMDAwMGZmIj6+3Mb5
QLmuwMc8L2ZvbnQ+IDogwKUgxvkgmN48L2ZvbnQ+PGZvbnQgc2l6ZT0iMSI+IDwvZm9udD48
Zm9udCBzaXplPSI0Ij4oQlNsaW5lKSANCjogMDItNTQ1LTYxOTk8YnI+DQoqPC9mb250Pjxm
b250IGNvbG9yPSIjZmYwMDAwIiBzaXplPSI1Ij675773xsTGrrPKPC9mb250Pjxmb250IHNp
emU9IjQiPiANCrmuwMcgOiAwMi01MTctMDEyNiAvIDAxOS05NzMyLTYwOTY8L2ZvbnQ+PC9i
PjwvcD4NCg0KPC9ib2R5Pg0KDQo8L2h0bWw+DQo=

------=_NextPart_000_0077_01C0F13A.93A01C00--



From owner-idn@ops.ietf.org  Mon Aug 13 10:11: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 KAA20646
	for <idn-archive@lists.ietf.org>; Mon, 13 Aug 2001 10:11:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15WI9W-000PYw-00
	for idn-data@psg.com; Mon, 13 Aug 2001 06:53:10 -0700
Received: from patan.sun.com ([192.18.98.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15WI9V-000PYq-00
	for idn@ops.ietf.org; Mon, 13 Aug 2001 06:53:09 -0700
Received: from bebop.France.Sun.COM ([129.157.179.15])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA25259;
	Mon, 13 Aug 2001 07:53:06 -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 f7DDr2221641;
	Mon, 13 Aug 2001 15:53:02 +0200 (MET DST)
Date: Mon, 13 Aug 2001 15:50:23 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [idn] SC/TC equivalence
To: David Hopwood <david.hopwood@zetnet.co.uk>
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>, idn@ops.ietf.org
In-Reply-To: "Your message with ID" <3B73E151.63E1D59D@zetnet.co.uk>
Message-ID: <Roam.SIMC.2.0.6.997710623.4370.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


David Hopwood wrote:

> Erik Nordmark wrote:
> > If the client asks for A and gets a response with QNAME A' and answer X
> > then ...
> 
> It won't - it will get a response with QNAME A.
>
> For DNSSEC, all responses for names that are actually used will have to be
> signed. This is an inevitable consequence of wanting TC/SC equivalence
> without putting TC/SC folding in nameprep (that is, the client-side
> canonicalization function). The decision that WG has to make is whether
> TC/SC folding is in nameprep or not. If that answer is "yes", it also has to
> define the folding, and require that all clients implement it.

If it gets a response with QNAME A then there must be a separate SIG for
QNAME A' and QNAME A for each RRset. Since DNSsec should be capable of
operating  with offline private keys this means that the signature couldn't
have been  created when the server received the query.

Thus I think you are pointing at the same type of solution to this as
Keith was: the server maintains the same responses (all RRsets) for
queries on A and A'.

That is quite different than what I've heard discribed as the DNS server
doing a mapping on the fly.

The former might have result in combinatorial explosion but works
with DNS including DNSsec.
The latter can avoid the combinatorial explosion but doesn't work with the
DNS as I pointed out.

> Personally I don't think nameprep should include any folding that depends
> on the semantics of particular languages - even if that causes inefficiencies
> for DNSSEC.

Agreed. IDN is about identifiers and not words and languages.
(And just like in the current non-IDN world folks will try to overload
words and phrases on IDN but that should really be a separate problem.)

  Erik




From owner-idn@ops.ietf.org  Mon Aug 13 10:12: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 KAA20673
	for <idn-archive@lists.ietf.org>; Mon, 13 Aug 2001 10:12:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15WIFZ-000Pem-00
	for idn-data@psg.com; Mon, 13 Aug 2001 06:59:25 -0700
Received: from mercury.sun.com ([192.9.25.1])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15WIFY-000Peg-00
	for idn@ops.ietf.org; Mon, 13 Aug 2001 06:59:24 -0700
Received: from bebop.France.Sun.COM ([129.157.179.15])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA05562;
	Mon, 13 Aug 2001 06:59:22 -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 f7DDxH222804;
	Mon, 13 Aug 2001 15:59:17 +0200 (MET DST)
Date: Mon, 13 Aug 2001 15:56:38 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [idn] IDNs do not use ASCII
To: "D. J. Bernstein" <djb@cr.yp.to>
Cc: idn@ops.ietf.org
In-Reply-To: "Your message with ID" <20010810171935.6159.qmail@cr.yp.to>
Message-ID: <Roam.SIMC.2.0.6.997710998.13440.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


> On the contrary. IDN is replacing ASCII with another character encoding
> in every Internet protocol that uses domain names.

Dan,

I don't know whether the above use of "IDN" refers to this working group
or some larger problem statement. I'm assuming you mean the WG.

If updating RFC 822, 2822 for smtp as well as all other application protocols
was in scope for the IDN working group, they would have been explicitly
listed in the WG charter.

They are not.

Having said that, when thinking about different solutions to the 
Internationalized Domain Name problem it is critical to understand the
impact on the application protocols (and other "users" of domain names)
in particular as it relates to the transition.

   Erik




From owner-idn@ops.ietf.org  Mon Aug 13 10:18: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 KAA20902
	for <idn-archive@lists.ietf.org>; Mon, 13 Aug 2001 10:18:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15WILI-000Pl8-00
	for idn-data@psg.com; Mon, 13 Aug 2001 07:05:20 -0700
Received: from patan.sun.com ([192.18.98.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15WILI-000Pl2-00
	for idn@ops.ietf.org; Mon, 13 Aug 2001 07:05:20 -0700
Received: from bebop.France.Sun.COM ([129.157.179.15])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA03611;
	Mon, 13 Aug 2001 08:05:16 -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 f7DE5D224240;
	Mon, 13 Aug 2001 16:05:13 +0200 (MET DST)
Date: Mon, 13 Aug 2001 16:02:34 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [idn] SC/TC equivalence
To: "Adam M. Costello" <amc@cs.berkeley.edu>
Cc: idn@ops.ietf.org
In-Reply-To: "Your message with ID" <20010810222811.C23949@arwen.cs.berkeley.edu>
Message-ID: <Roam.SIMC.2.0.6.997711354.17445.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


> I think the server is always supposed to answer the query that was asked
> (A, not A').  If maintaining records for all equivalent variants of
> A' is too expensive, it could instead generate the response (and the
> signature) on the fly.  It could use caching to remember the responses
> for the most common variants.

DNSsec is specified to work without keeping the private key on-line
(doing the signing off-line can be made secure) thus you
can't assume that servers will be able to sign on the fly.

  Erik
 




From owner-idn@ops.ietf.org  Mon Aug 13 10:27: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 KAA21013
	for <idn-archive@lists.ietf.org>; Mon, 13 Aug 2001 10:27:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15WIYw-00001z-00
	for idn-data@psg.com; Mon, 13 Aug 2001 07:19:26 -0700
Received: from patan.sun.com ([192.18.98.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15WIYv-00001t-00
	for idn@ops.ietf.org; Mon, 13 Aug 2001 07:19:25 -0700
Received: from bebop.France.Sun.COM ([129.157.179.15])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA13674;
	Mon, 13 Aug 2001 08:19:22 -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 f7DEJI225772;
	Mon, 13 Aug 2001 16:19:18 +0200 (MET DST)
Date: Mon, 13 Aug 2001 16:16:39 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [idn] Which names are valid?
To: David Hopwood <david.hopwood@zetnet.co.uk>
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, idn@ops.ietf.org
In-Reply-To: "Your message with ID" <3B742989.C3E562D7@zetnet.co.uk>
Message-ID: <Roam.SIMC.2.0.6.997712199.2208.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by ietf.org id KAA21013


> The definitions in that draft are not entirely satisfactory. For example,
> consider "_ldap._tcp.Ï€.com". This is clearly a domain name, and it is
> clearly internationalized, so the most sensible thing to call it would be
> an internationalized domain name. However, it is not a hostname (although
> "Ï€.com" is). It makes no sense to lose the useful distinction between
> hostnames and domain names just because they are internationalized.

So is "_ldap._tcp.Ï€.com"" a domain name with a hostname component??
[my mail UA seems to have problems with the characters above - it might not
look the way you sent it.]

The reason we can't just drop the distinction between host names and domain
names is that many application protocols handle host names under the
restrictive specification of valid host names. When looking at transition
issues the impact on those application protocols is key.

So should we say something specific (e.g. as part of the scope
in the requirements document) about domain names with
host name components or substrings?

   Erik




From owner-idn@ops.ietf.org  Mon Aug 13 11:52: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 LAA22695
	for <idn-archive@lists.ietf.org>; Mon, 13 Aug 2001 11:52:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15WJoA-0001dM-00
	for idn-data@psg.com; Mon, 13 Aug 2001 08:39:14 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15WJo8-0001dC-00
	for idn@ops.ietf.org; Mon, 13 Aug 2001 08:39:13 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id LAA15161;
        Mon, 13 Aug 2001 11:39:03 -0400 (EDT)
Message-Id: <200108131539.LAA15161@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
cc: David Hopwood <david.hopwood@zetnet.co.uk>, idn@ops.ietf.org
Subject: Re: [idn] SC/TC equivalence 
In-reply-to: Your message of "Mon, 13 Aug 2001 15:50:23 +0200."
             <Roam.SIMC.2.0.6.997710623.4370.nordmark@bebop.france> 
Date: Mon, 13 Aug 2001 11:39:02 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Thus I think you are pointing at the same type of solution to this as
> Keith was: the server maintains the same responses (all RRsets) for
> queries on A and A'.
> 
> That is quite different than what I've heard discribed as the DNS server
> doing a mapping on the fly.

In my mind, the choice of mechanism used to keep the RRsets equivalent for
the sets of equivalent labels is up to the maintainer of the zone.
Of course, if the maintainer of the zone uses DNSsec, that will influence 
the choice.  

Doing a mapping on the fly might be attractive for some zones that
did not use DNSsec.  But I wouldn't specify such a mechanism as part 
of the standard.

Keith



From owner-idn@ops.ietf.org  Mon Aug 13 11:59: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 LAA22966
	for <idn-archive@lists.ietf.org>; Mon, 13 Aug 2001 11:59:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15WK0N-0001tQ-00
	for idn-data@psg.com; Mon, 13 Aug 2001 08:51:51 -0700
Received: from goose.ehsco.com ([207.65.203.98])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15WK0M-0001tJ-00
	for idn@ops.ietf.org; Mon, 13 Aug 2001 08:51:50 -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 221114; Sun, 12 Aug 2001 10:51:12 -0500
Message-ID: <3B77F793.2C3A3CAB@ehsco.com>
Date: Mon, 13 Aug 2001 10:51:47 -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: Erik Nordmark <Erik.Nordmark@eng.sun.com>
CC: David Hopwood <david.hopwood@zetnet.co.uk>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, idn@ops.ietf.org
Subject: Re: [idn] Which names are valid?
References: <Roam.SIMC.2.0.6.997712199.2208.nordmark@bebop.france>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Erik Nordmark wrote:

> So should we say something specific (e.g. as part of the scope
> in the requirements document) about domain names with
> host name components or substrings?

I think that this question needs to be answered by management.

It would be nice to drop the hostname rules, but at the same time, there
are many many techno-political issues in doing so. The security issues are
just convoluted, for example, as are the intellectual property issues
faced by ICANN and the registrars/registries.

One quick example: RFC1035 allows a period in the middle of a label by
escaping it, and the only reason we don't have www/.aol.com issues now is
because the hostname rules prevent www/.aol from being registered as a
domain. Many similar shenanigans will be possible with IDN.

This kind of situation can go away, but I don't think its in the IDN WG
scope to make that call. We should only be worrying about the technology
issues, and leave policy to the policy makers.

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



From owner-idn@ops.ietf.org  Tue Aug 14 05:23: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 FAA24619
	for <idn-archive@lists.ietf.org>; Tue, 14 Aug 2001 05:23:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15WZvP-000D9M-00
	for idn-data@psg.com; Tue, 14 Aug 2001 01:51:47 -0700
Received: from [217.13.28.204] (helo=eikenes.alvestrand.no)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15WZvO-000D8m-00
	for idn@ops.ietf.org; Tue, 14 Aug 2001 01:51:47 -0700
Received: from [10.0.4.108] (eikenes.alvestrand.no [217.13.28.203])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id B2D7E61E98; Tue, 14 Aug 2001 10:47:57 +0200 (CEST)
Date: Tue, 14 Aug 2001 09:16:47 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: David Hopwood <david.hopwood@zetnet.co.uk>, idn@ops.ietf.org
Subject: Re: [idn] Which names are valid?
Message-ID: <168032788.997780607@localhost>
In-Reply-To: <3B742989.C3E562D7@zetnet.co.uk>
References:  <3B742989.C3E562D7@zetnet.co.uk>
X-Mailer: Mulberry/2.1.0b3 (Win32)
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 FAA24619



--On 10. august 2001 19:35 +0100 David Hopwood <david.hopwood@zetnet.co.uk> 
wrote:

> The definitions in that draft are not entirely satisfactory. For example,
> consider "_ldap._tcp.Ï?.com". This is clearly a domain name, and it is
> clearly internationalized, so the most sensible thing to call it would be
> an internationalized domain name. However, it is not a hostname (although
> "Ï?.com" is). It makes no sense to lose the useful distinction between
> hostnames and domain names just because they are internationalized.

the draft was written after we had already established the IDN WG's name.
It would be logical to call Ï.com an Internationalized Host Name, and 
_ldap._tcp.Ï.com an Internationalized Domain Name, but at the time, 
changing the definition of an IDN that most people in the group had in 
their minds didn't seem worth it.

This may have been a mistake.

                Harald




From owner-idn@ops.ietf.org  Tue Aug 14 10:52: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 KAA06445
	for <idn-archive@lists.ietf.org>; Tue, 14 Aug 2001 10:52:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Wf9m-000Guo-00
	for idn-data@psg.com; Tue, 14 Aug 2001 07:26:58 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Wf9l-000Gue-00
	for idn@ops.ietf.org; Tue, 14 Aug 2001 07:26:57 -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; Tue, 14 Aug 2001 07:38:12 -0700
Message-ID: <00eb01c124ce$60f338e0$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>, <idn@ops.ietf.org>
References: <200107301509.f6UF91N23867@nic-naa.net> <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net> <001601c11fed$a80b2f20$fb05738c@ncu.edu.tw> <005001c1200d$01f85480$d43f7018@mtag1.on.home.com> <3B71A3DE.8DF843B4@zetnet.co.uk> <001901c12053$da3eaec0$d43f7018@mtag1.on.home.com> <3B71D034.63F361B6@zetnet.co.uk>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Tue, 14 Aug 2001 10:35:34 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi

I am looking for support for my Supreme Chinese Domain Name System so
that it will become a standard.  It involves a standard way of
registration by all registries that offers CDNs as well as adding a
prohibit function to nameprep of CDNs.

However, if I don't have your support in making it a standard, that is
absolutely fine.  Perhaps you can still comment on my other
alternative to implementing this system by creating a new type of
lsTLD.  If you are concerned that discussions of <IDN>.<IDN> is out of
the scope of the IDN WG, please do email me privately.

Attached below is my draft.

Thanks for your support
Ben Chan


_________________________________



Internet Draft
Author: Ben Chan
July 14, 2001
Expires in six months


  Supreme Chinese Domain Name System



Status of this Memo

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

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

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

    The list of current Internet-Drafts can be accessed at
    http://www.ietf.org/ietf/1id-abstracts.txt

    The list of Internet-Draft Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html


Abstract

Chinese can be written in 2 different scripts, traditional Chinese and
simplified Chinese, that cannot be distinguished by many people of
certain background/cultures/groups who use them interchangeably.  As a
result, users of Chinese Domain Names (CDN) have special needs that
can only be satisfied by adding a label to CDNs that distinguish a CDN
with traditional characters from a CDN with simplified characters.
This labeling is an entire system that can be accomplished with SLDs
or by creating a new type of TLD called Language Script TLD (lsTLD).
This draft describes the benefits that the system will provide and the
techniques involved in implementing it.


1.  Introduction

(Labeling of a CDN can be accomplished with either SLDs or lsTLDs.
However, for simplicity, most of this draft will only use lsTLD to
describe the system and its techniques.  For more information on how
SLDs can be used, please see section 5.2.)

The <.traditional> and <.simplified> TLDs in Chinese characters are:
a) <.traditional> in traditional Chinese is ".ç¹�é«”" (U+7E41)(
U+9AD4)
b) <.traditional> in simplified Chinese is ".ç¹�ä½“" (U+7E41)( U+4F53)
c) <.simplified> in simplified Chinese is ".ç®€ä½“" (U+7B80)( U+4F53)
d) <.simplified> in traditional Chinese is ".ç°¡é«”" (U+7C21)( U+9AD4)

Using the 4 language script TLDs above, a Chinese Domain Name System
can be created to satisfy the needs of CDN users by combining together
the following 3 benefits:

Benefit A- A registrant is given the choice of pointing a traditional
CDN to one location (ie. traditional Chinese website) and pointing the
corresponding simplified CDN to another location (ie. simplified
Chinese website).

Benefit B- The registration of a simplified CDN will automatically
reserves the corresponding traditional CDN(s) and visa versa thus
giving users the flexibility of using either script.

Benefit C- A method that will guide users to enter a CDN in their
applications (ie. web browsers) matching the meaning that was intended
by the registrant when the CDN was registered.


2.  Description of the Importance of the Benefits

It is important to understand the needs of ordinary everyday people
who will be the users of CDNs.  The following subsections will explain
in detail the 3 benefits of this system that satisfied those needs.


2.1  Importance of Benefit A.

It would be appropriate for a traditional CDN to be pointing to a
traditional website with contents that are suitable for visitors from
Hong Kong or Taiwan.  On the same line, it would be appropriate for a
simplified CDN to be pointing to a simplified website with contents
that are suitable for visitors from China or Singapore.


2.2  Importance of Benefit B.

Since many Chinese can read / write in both scripts, it is only
appropriate for a traditional CDN to be mapped to its corresponding
simplified CDN by applying a conversion.  This will ensure that no
matter what script the user types in, he will always be able to reach
the intended location(s).


2.3  Importance of Benefit C.

The relationship between simplified Chinese and traditional Chinese is
very complicated.  A TC character that corresponds to a SC character
may not have the same meaning.  To complicate the situation, one TC
character can be mapped into many different SC and visa versa.  One
CDN can potential have a great number of different written variations.
Without a method, a user can be given a CDN and type in the correct
CDN but still cannot reach the proper destination because it is a
variation of the original CDN not intended by the registrant.


3.  Solution / Method

The method for implementing this system is done both at the
registration system and at the client end.


3.1  Implemented at the registration system

The solution to delivering the 3 benefits explained above is a Chinese
domain name system that uses language script TLDs- a TLD of
<.traditional> for traditional CDNs (defined here as a CDN that uses
all traditional characters) and a TLD of <.simplified> for simplified
CDNs (defined here as a CDN that uses all simplified characters).
During registration, a person is allowed to register CDNs in either
all traditional Chinese characters or all simplified Chinese
characters but not by mixing the 2 scripts together.  If he registers
in traditional characters, he will be given a traditional CDN (with
the TLD of <.traditional>) and any similar traditional CDNs will be
reserved.  At the same time, the corresponding simplified CDN(s) (with
the TLD of <.simplified>) will also be reserved- to be activated at a
later date if the registrant chooses to do so.  If he registers in
simplified characters, he will be given a simplified CDN (with the TLD
of <.simplified>) and any similar simplified CDNs will be reserved.
At the same time, the corresponding traditional CDN(s) (with the TLD
of <.traditional>) is reserved.


3.2 Implemented at the client end.

If a user types in a traditional CDN (with the <.traditional>), error
checking can be done by the application (ie. web browser- nameprep to
prohibit invalid entries) on the CDN by searching for the characters
in a Unicode table containing all the valid traditional Chinese
characters.  If a certain character is found not to be a valid
traditional character, an error will be displayed to point out which
character is invalid.  If a user types in a simplified CDN (with the
<.simplified>), the same error checking will be performed by searching
for valid simplified Chinese character.  (Please see Appendix A for a
list of the disallowed Unicodes for traditional CDNs and simplified
CDNs.)


4.  Conclusion

Under such a method of creating a relationship between the lsTLDs, all
3 benefits will be satisfied.  Benefit A will be satisfied because he
can point <whatever>.<traditional> to a traditional website and point
<whatever>.<simplified> to a simplified website.  Benefit B will be
satisfied because when a user is given a <whatever>.<traditional> CDN,
but because he is from mainland China and is more comfortable using
the simplified script, he can simply use the corresponding CDN of
<whatever>.<simplified>.  In other words, a user can use the script of
his choice whether it is traditional Chinese or simplified Chinese and
still reach the location(s) intended by the registrant.  Benefit C
will be satisfied because when the user is given the
<whatever>.<traditional> CDN, the <.traditional> tells him that he
must set his Chinese Input editor to recognize TC only and thereby
preserving the original intended meaning of the CDN when it was first
registered.  In other words, the language script TLDs give the users
much more control and eliminates any guess work.


5.  Other Comments

There are 2 important related issues- â€œTC<->SC equivalenceâ€� and
â€œlsSLDsâ€�.


5.1  TC<->SC equivalence

An interest question is how this system is effect with TC<->SC
equivalence in the DNS protocol?  The answer is that it will even be
better.  With TC<->SC equivalence in the DNS protocol, all 4 lsTLDs
are used.  No error checking will be performed.  The <.traditional>
lsTLD in both simplified and traditional forms are consider equivalent
and point to the same location (ie.  traditional website).  The
<.simplified> lsTLD in both simplified and traditional forms are
considered equivalent and point to the same location (ie.  simplified
website).  The author of this draft strongly endorse any efforts made
in finding a reasonable solution to the TC<->SC equivalence.


5.2 lsSLDs

The same techniques documented in this draft can also be applied to
the current gTLD and ccTLD registries by using SLDs.  In order to be
fair, everyone must agree to this system and make it a standard.  In
addition, every registry must change their current registered second
level domains to third level domains (ie.
<whatever>.<traditional>.TLD, <whatever>.<simplified>.TLD)


6.  Authorâ€™s Address

Ben Chan
cc-www.com
Box 92241
2900 Warden Avenue
Scarborough, Ontario
Canada
M1W 3Y9


7.  References

[IDNREQ]  Requirements of Internationalized Domain Names, Zita Wenzel,
James Seng, draft-ietf-idn-requirements



Appendix A-  Error checking for Unicodes of traditional/simplified
Chinese characters

(The following is a partial list for information only.  A complete
list will be presented upon actual implementation.)


Acceptable Unicodes         Acceptable Unicodes
for a simplified                    for a traditional
CDN                                 CDN


7691                                    769A
788D                                   7919
7231                                    611B
8884                                    8956
5965                                    5967
575D                                   58E9
7F62                                    7F77
6446                                    64FA
8D25                                   6557
9881                                    9812
529E                                    8FA6
7ECA                                  7D46
5E2E                                   5E6B
7ED1                                   7D81
9551                                    938A
8C24                                   8B17
5265                                    525D
9971                                    98FD
5B9D                                   5BF6
62A5                                    5831
9C8D                                   9B91
8F88                                    8F29
8D1D                                   8C9D
94A1                                    92C7
72C8                                    72FD
5907                                     5099
60EB                                    618A
7EF7                                    7E43
7B14                                    7B46
6BD5                                    7562
6BD9                                    6583
5E01                                     5E63
95ED                                    9589
8FB9                                    908A
7F16                                    7DE8
8D2C                                   8CB6
53D8                                    8B8A

etc.










From owner-idn@ops.ietf.org  Tue Aug 14 17:04: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 RAA15104
	for <idn-archive@lists.ietf.org>; Tue, 14 Aug 2001 17:04:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Wl59-0001Yt-00
	for idn-data@psg.com; Tue, 14 Aug 2001 13:46:35 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Wl59-0001Yn-00
	for idn@ops.ietf.org; Tue, 14 Aug 2001 13:46:35 -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; Tue, 14 Aug 2001 13:57:48 -0700
Message-ID: <001e01c12503$6942ce40$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>
References: <20010814.114119.-917217.0.liana.ydisg@juno.com>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Tue, 14 Aug 2001 16:55:11 -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



>  1. What is SLD?  It is easier  for a reader to see it's definition
> before abbreviation.

For the benefit of everyone, SLD is "second level domain". 

Thanks
Ben Chan




From owner-idn@ops.ietf.org  Tue Aug 14 22:34: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 WAA21458
	for <idn-archive@lists.ietf.org>; Tue, 14 Aug 2001 22:34:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Wq6x-0007EM-00
	for idn-data@psg.com; Tue, 14 Aug 2001 19:08:47 -0700
From: "Adam M. Costello" <amc@cs.berkeley.edu>
To: idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E15Wq6x-0007EM-00@psg.com>
Date: Tue, 14 Aug 2001 19:08:47 -0700

ben <ben@cc-www.com> wrote:

> The solution to delivering the 3 benefits explained above is a
> Chinese domain name system that uses language script TLDs- a TLD of
> <.traditional> for traditional CDNs (defined here as a CDN that uses
> all traditional characters) and a TLD of <.simplified> for simplified
> CDNs (defined here as a CDN that uses all simplified characters).

This would limit people's choice of registration authority.

> The same techniques documented in this draft can also be applied
> to the current gTLD and ccTLD registries by using SLDs.  In order
> to be fair, everyone must agree to this system and make it a
> standard.  In addition, every registry must change their current
> registered second level domains to third level domains (ie.
> <whatever>.<traditional>.TLD, <whatever>.<simplified>.TLD)

I don't think there's any need to require that all domains containing
Chinese characters follow this convention.  It could be left up
to each registrant whether they want to include <traditional> or
<simplified> in their domain name.  It needn't be at the second
level either.  The convention could be that clients with the added
Chinese support would be suspicious of simplified characters
anywhere to the left of .<traditional>. (wherever it appears) and
be suspicious of traditional characters anywhere to the left of
>.<simplified>. (wherever it appears).  This would allow things
like <FOO>.<traditional>.ac.uk.  It could be recommended (but
probably not required) that registration authorities never allow
<traditional> or <simplified> to be registered under any zone, but
rather require registrants to register <something>.<traditional> or
<something>.<simplified>.  It could be recommended (but probably not
required) that registrars register such names in pairs.

One nice thing about your proposal is that it appears to be orthogonal
to IDNA.  Clients without the added Chinese support can still access
all domain names, they just won't provide the extra hints when mistyped
names fail.

AMC





From owner-idn@ops.ietf.org  Wed Aug 15 01:19: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 BAA25130
	for <idn-archive@lists.ietf.org>; Wed, 15 Aug 2001 01:19:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15WswX-000A2Q-00
	for idn-data@psg.com; Tue, 14 Aug 2001 22:10:13 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15WswW-000A2J-00
	for idn@ops.ietf.org; Tue, 14 Aug 2001 22:10:12 -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; Tue, 14 Aug 2001 22:21:29 -0700
Message-ID: <000901c12549$c6f882a0$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "Adam M. Costello" <amc@cs.berkeley.edu>, <idn@ops.ietf.org>
References: <E15Wq6x-0007EM-00@psg.com>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Wed, 15 Aug 2001 01:18:53 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Adam,

> > The solution to delivering the 3 benefits explained above is a
> > Chinese domain name system that uses language script TLDs- a TLD
of
> > <.traditional> for traditional CDNs (defined here as a CDN that
uses
> > all traditional characters) and a TLD of <.simplified> for
simplified
> > CDNs (defined here as a CDN that uses all simplified characters).
>
> This would limit people's choice of registration authority.

In my system, CDNs cannot be a mix of TC and SC.  If that is
considered "limit people's choices..." then I am afraid I am guilty.
However, can you come up with even one good reason why we should allow
a CDN to have mixed TC and SC?

>
> > The same techniques documented in this draft can also be applied
> > to the current gTLD and ccTLD registries by using SLDs.  In order
> > to be fair, everyone must agree to this system and make it a
> > standard.  In addition, every registry must change their current
> > registered second level domains to third level domains (ie.
> > <whatever>.<traditional>.TLD, <whatever>.<simplified>.TLD)
>
> I don't think there's any need to require that all domains
containing
> Chinese characters follow this convention.  It could be left up
> to each registrant whether they want to include <traditional> or
> <simplified> in their domain name.  It needn't be at the second
> level either.  The convention could be that clients with the added
> Chinese support would be suspicious of simplified characters
> anywhere to the left of .<traditional>. (wherever it appears) and
> be suspicious of traditional characters anywhere to the left of
> >.<simplified>. (wherever it appears).  This would allow things
> like <FOO>.<traditional>.ac.uk.  It could be recommended (but
> probably not required) that registration authorities never allow
> <traditional> or <simplified> to be registered under any zone, but
> rather require registrants to register <something>.<traditional> or
> <something>.<simplified>.  It could be recommended (but probably not

> required) that registrars register such names in pairs.
>
> One nice thing about your proposal is that it appears to be
orthogonal
> to IDNA.  Clients without the added Chinese support can still access
> all domain names, they just won't provide the extra hints when
mistyped
> names fail.
>
> AMC
>

I feel very strongly that there is a need to create a new type of TLD
(lsTLD- as described in my draft) to implement my idea to satisfy the
needs of CDN users.  Do you have any opinions on that?

Thanks
Ben Chan










From owner-idn@ops.ietf.org  Wed Aug 15 02:23: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 CAA09934
	for <idn-archive@lists.ietf.org>; Wed, 15 Aug 2001 02:23:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Wttj-000Aw5-00
	for idn-data@psg.com; Tue, 14 Aug 2001 23:11:23 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Wtth-000Avt-00
	for idn@ops.ietf.org; Tue, 14 Aug 2001 23:11:21 -0700
Received: from test.ncu.edu.tw ([140.115.5.251])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f7F6GB727295;
	Wed, 15 Aug 2001 14:16:11 +0800 (CST)
Message-ID: <000501c12551$1501c220$fb05738c@ncu.edu.tw>
From: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: "ben" <ben@cc-www.com>, "Adam M. Costello" <amc@cs.berkeley.edu>,
        <idn@ops.ietf.org>
References: <E15Wq6x-0007EM-00@psg.com> <000901c12549$c6f882a0$d43f7018@mtag1.on.home.com>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Wed, 15 Aug 2001 14:11:09 +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.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 ! Ben:
> >
> > This would limit people's choice of registration authority.
>
> In my system, CDNs cannot be a mix of TC and SC.  If that is
> considered "limit people's choices..." then I am afraid I am guilty.
> However, can you come up with even one good reason why we should allow
> a CDN to have mixed TC and SC?
>
       In HongKong , Taiwan,  user use BIG5 code . This code set has no
simpified chinese scripts. In China , GB code set has no traditional chinese
scripts . So there are no mixed type of  GB and BIG5 .  But you know
VeriSign/NSI  announced ML.com  with any UNICODE can be mixed.
That is the key problems.
       Any suggestions must be considered  what to do for .COM in this WG.
If english character is treated as case folding, Why  CJK can not treated as
the same way to reduce the number of registrations for trade mark
considerations?  Case folding is also not a protocol issue .  It is
othogonal to IDNA too.

L. M. Tseng,
> >
> > > The same techniques documented in this draft can also be applied
> > > to the current gTLD and ccTLD registries by using SLDs.  In order
> > > to be fair, everyone must agree to this system and make it a
> > > standard.  In addition, every registry must change their current
> > > registered second level domains to third level domains (ie.
> > > <whatever>.<traditional>.TLD, <whatever>.<simplified>.TLD)
> >
> > I don't think there's any need to require that all domains
> containing
> > Chinese characters follow this convention.  It could be left up
> > to each registrant whether they want to include <traditional> or
> > <simplified> in their domain name.  It needn't be at the second
> > level either.  The convention could be that clients with the added
> > Chinese support would be suspicious of simplified characters
> > anywhere to the left of .<traditional>. (wherever it appears) and
> > be suspicious of traditional characters anywhere to the left of
> > >.<simplified>. (wherever it appears).  This would allow things
> > like <FOO>.<traditional>.ac.uk.  It could be recommended (but
> > probably not required) that registration authorities never allow
> > <traditional> or <simplified> to be registered under any zone, but
> > rather require registrants to register <something>.<traditional> or
> > <something>.<simplified>.  It could be recommended (but probably not
>
> > required) that registrars register such names in pairs.
> >
> > One nice thing about your proposal is that it appears to be
> orthogonal
> > to IDNA.  Clients without the added Chinese support can still access
> > all domain names, they just won't provide the extra hints when
> mistyped
> > names fail.
> >
> > AMC
> >
>
> I feel very strongly that there is a need to create a new type of TLD
> (lsTLD- as described in my draft) to implement my idea to satisfy the
> needs of CDN users.  Do you have any opinions on that?
>
> Thanks
> Ben Chan
>
>
>
>
>
>
>
>
>




From owner-idn@ops.ietf.org  Wed Aug 15 04:05: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 EAA10734
	for <idn-archive@lists.ietf.org>; Wed, 15 Aug 2001 04:05:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15WvIT-000CV0-00
	for idn-data@psg.com; Wed, 15 Aug 2001 00:41:01 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15WvIS-000CUl-00
	for idn@ops.ietf.org; Wed, 15 Aug 2001 00:41: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 QAA19044;
	Wed, 15 Aug 2001 16:39:37 +0900
Message-ID: <014701c1255c$aa757d50$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: =?UTF-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>,
        <idn@ops.ietf.org>
References: <E15Wq6x-0007EM-00@psg.com> <000901c12549$c6f882a0$d43f7018@mtag1.on.home.com> <000501c12551$1501c220$fb05738c@ncu.edu.tw>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Wed, 15 Aug 2001 16:34:06 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit


----- Original Message -----
From: "tsenglm@è¨ˆç¶²ä¸­å¿ƒ.ä¸­å¤§.tw" <tsenglm@cc.ncu.edu.tw>
 >        In HongKong , Taiwan,  user use BIG5 code . This code set has no
> simpified chinese scripts. In China , GB code set has no traditional chinese
> scripts . So there are no mixed type of  GB and BIG5 .  But you know
> VeriSign/NSI  announced ML.com  with any UNICODE can be mixed.
> That is the key problems.
>        Any suggestions must be considered  what to do for .COM in this WG.
> If english character is treated as case folding, Why  CJK can not treated as
> the same way to reduce the number of registrations for trade mark
> considerations?  Case folding is also not a protocol issue .  It is
> othogonal to IDNA too.
>
> L. M. Tseng,

Tseng, which solution do you support ?

 1. Registration/Dispute Resolution Policy that assures:

     The first registrant of a SC or TC .com domain should take
     all of its SC/TC equivalent alternatives.

 2. The new version of Unicode Standard   defines
     additional case-mapping rules  for SC/TC equivalences and
     NAMEPREP  refers to that standard document  for doing SC/TC case folding.

Soobok Lee




From owner-idn@ops.ietf.org  Wed Aug 15 05:26: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 FAA11274
	for <idn-archive@lists.ietf.org>; Wed, 15 Aug 2001 05:26:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15WwmE-000Duz-00
	for idn-data@psg.com; Wed, 15 Aug 2001 02:15:50 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15WwmC-000DuY-00
	for idn@ops.ietf.org; Wed, 15 Aug 2001 02:15:49 -0700
Received: from test.ncu.edu.tw ([140.115.5.251])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f7F9Kl704925;
	Wed, 15 Aug 2001 17:20:47 +0800 (CST)
Message-ID: <002201c1256a$dd99f4a0$fb05738c@ncu.edu.tw>
From: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
References: <E15Wq6x-0007EM-00@psg.com> <000901c12549$c6f882a0$d43f7018@mtag1.on.home.com> <000501c12551$1501c220$fb05738c@ncu.edu.tw> <014701c1255c$aa757d50$ec1bd9d2@temp>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Wed, 15 Aug 2001 17:15:44 +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.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit




> > VeriSign/NSI  announced ML.com  with any UNICODE can be mixed.
> > That is the key problems.
> >        Any suggestions must be considered  what to do for .COM in this
WG.
> > If english character is treated as case folding, Why  CJK can not
treated as
> > the same way to reduce the number of registrations for trade mark
> > considerations?  Case folding is also not a protocol issue .  It is
> > othogonal to IDNA too.
> >
> > L. M. Tseng,
>
> Tseng, which solution do you support ?
>
Lee,  sorry, some IDN problems need them both.
    Method 1 is policy based approach.  Method 2 is technique approach.  To
solve problems ,  first one is technique possibility then  policy is
considered finally .  For  chinese scripts ,  Method 2 only applied to case
of bidirectional one one mapping . It also has one trouble : In a set of
scripts, which script is the canonical form ? If  script display is needed .
The transformed ACE code can not recover to the original  scripts . So it
solve only partial problems.
    Method 1 is considered to reduce the complexity of  1 to n or n to n
mapping case ,  if there are no simple way to solve the difficulty, 1 to n
scrpts mapping are forecd to selected one by user in registration time.
Actually,  1 to n  and n to n or forbidden one are always solved by policy.
But these selection need assign one SC or TC as the primary form , so ACE
encoding is the mapping table form to map IDN(TC) and IDN(SC) to primary
ACE(IDN) .  This is a policy of selecting best one .  It also solve partial
problems too.
     So, both are need . If you considered the suitable display  scripts
form, Another table mapping method should be included to reverse reference
them.

L.M.Tseng

>  1. Registration/Dispute Resolution Policy that assures:
>
>      The first registrant of a SC or TC .com domain should take
>      all of its SC/TC equivalent alternatives.
>
>  2. The new version of Unicode Standard   defines
>      additional case-mapping rules  for SC/TC equivalences and
>      NAMEPREP  refers to that standard document  for doing SC/TC case
folding.
>
> Soobok Lee
>
>




From owner-idn@ops.ietf.org  Wed Aug 15 06: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 GAA11687
	for <idn-archive@lists.ietf.org>; Wed, 15 Aug 2001 06:09:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15WxUa-000Eaz-00
	for idn-data@psg.com; Wed, 15 Aug 2001 03:01: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.31 #1)
	id 15WxUZ-000Ear-00
	for idn@ops.ietf.org; Wed, 15 Aug 2001 03:01: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 f7F9vnO08242;
	Wed, 15 Aug 2001 05:57:49 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200108150957.f7F9vnO08242@nic-naa.net>
To: "Soobok Lee" <lsb@postel.co.kr>
cc: =?UTF-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] opting out of SC/TC equivalence 
In-Reply-To: Your message of "Wed, 15 Aug 2001 16:34:06 +0900."
             <014701c1255c$aa757d50$ec1bd9d2@temp> 
Date: Wed, 15 Aug 2001 05:57:49 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Soobok,

Perhaps you wrote in haste. 

Mechanism: Specification of SC/TC equivalance sufficient for dns identifier
comparison may be done in nameprep.

Additionally, Specification of SC/TC equivalance necessary but not sufficient
for dns identifier comparison may be done in a seperate document in this WG,
e.g., the existing tsconv or suggested uniprep drafts.

Further, Specification of SC/TC equivalance sufficient for other forms of
comparison which exceede those for dns identifier comparison may be done in
a seperate document, external to this WG.

Policy: Specification of policy, e.g., "first-come, first-served", whether
scoped or unscoped, is out of scope for this WG.

Scope: Specification of mechanism scope, e.g., registry specific, may be
done, but see the discussion of [30].

Eric



From owner-idn@ops.ietf.org  Wed Aug 15 06:36: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 GAA12004
	for <idn-archive@lists.ietf.org>; Wed, 15 Aug 2001 06:36:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15WxwY-000F4I-00
	for idn-data@psg.com; Wed, 15 Aug 2001 03:30:34 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15WxwX-000F4A-00
	for idn@ops.ietf.org; Wed, 15 Aug 2001 03:30:33 -0700
Received: from soobok ([210.217.27.237] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id TAA07506;
	Wed, 15 Aug 2001 19:30:09 +0900
Message-ID: <003801c12575$f56dce20$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: "=?ks_c_5601-1987?B?dHNlbmdsbUDoqIjntrLkuD+/gy7kuD+kpy50dw==?=" <tsenglm@cc.ncu.edu.tw>,
        <idn@ops.ietf.org>, <brunner@nic-naa.net>
References: <200108150957.f7F9vnO08242@nic-naa.net>
Subject: Re: [idn] opting out of SC/TC equivalence 
Date: Wed, 15 Aug 2001 19:35:09 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Some participants suggest we need to recover the pre-normalization/pre-folding
characters from folded domains for various reasons (political or aesthetical).
Do we really support this need in nameprep and uniprep contexts?

IMHO,under current version of "light-weight" nameprep, we don't need do that.

But for future heavier uniprep( or nameprep ) that includes SC/TC mappings,
i am sure we should devise some mechanisms (in DNS scope or out of DNS scope)
to recover the pre-normalization forms.


Soobok Lee

----- Original Message ----- 
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
 

> Soobok,
> 
> Perhaps you wrote in haste. 
> 
> Mechanism: Specification of SC/TC equivalance sufficient for dns identifier
> comparison may be done in nameprep.
> 
> Additionally, Specification of SC/TC equivalance necessary but not sufficient
> for dns identifier comparison may be done in a seperate document in this WG,
> e.g., the existing tsconv or suggested uniprep drafts.
> 
> Further, Specification of SC/TC equivalance sufficient for other forms of
> comparison which exceede those for dns identifier comparison may be done in
> a seperate document, external to this WG.
 




From owner-idn@ops.ietf.org  Wed Aug 15 06:43: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 GAA12104
	for <idn-archive@lists.ietf.org>; Wed, 15 Aug 2001 06:43:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Wy2o-000FBd-00
	for idn-data@psg.com; Wed, 15 Aug 2001 03:37:02 -0700
Received: from twnic.net.tw ([211.72.210.250])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Wy2n-000FBX-00
	for idn@ops.ietf.org; Wed, 15 Aug 2001 03:37:01 -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 SAA31279;
	Wed, 15 Aug 2001 18:36:43 +0800
Message-ID: <3B7A54D5.FA3B2F11@twnic.net.tw>
Date: Wed, 15 Aug 2001 18:54:13 +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: "Adam M. Costello" <amc@cs.berkeley.edu>
CC: idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
References: <E15Wq6x-0007EM-00@psg.com>
Content-Type: text/plain; charset=big5
Content-Transfer-Encoding: 8bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Dar Adam,

"Adam M. Costello" ¼g¤J¡G

> ben <ben@cc-www.com> wrote:
>
> > The solution to delivering the 3 benefits explained above is a
> > Chinese domain name system that uses language script TLDs- a TLD of
> > <.traditional> for traditional CDNs (defined here as a CDN that uses
> > all traditional characters) and a TLD of <.simplified> for simplified
> > CDNs (defined here as a CDN that uses all simplified characters).

<.traditional> and <.simplified> maybe not the only one and not the
best one method of manage CDN. But it really could reduce the size
of the zone file. Because which is no more need to reserve the all possible

mixed TC/SC CDN for equivalent match .

If existing ccTLD or a new possible IDNccTLD could imply particular
scripe, then it do not necessary have the additional <.traditional> nor
<.simplified>

> This would limit people's choice of registration authority.

Certainly, we should consider carefully  not to limit people's choice when
they register CDN. But, how if the people live in PRC, Taiwan, Hongkong,
Macao and the Chinese some other where they do not use Chinese in the
way of mixed TC/SC ? In such case, that is not limit the piople, it should
be fit the people.

Maybe people may ask how if some of the people they do not familar
Chinese culture and custom might to use the CND in mixed TC/SC ?
Fine, nameprep it as case folding before send the request to resolver as
defined in IDNA. Or some intelligent match service could help things like
that.

> > The same techniques documented in this draft can also be applied
> > to the current gTLD and ccTLD registries by using SLDs.  In order
> > to be fair, everyone must agree to this system and make it a
> > standard.  In addition, every registry must change their current
> > registered second level domains to third level domains (ie.
> > <whatever>.<traditional>.TLD, <whatever>.<simplified>.TLD)

If the TLD could imply certain scripe, it does can provide the registration

of <certain scripe IDN>.TLD(imply certain scripe)

> I don't think there's any need to require that all domains containing
> Chinese characters follow this convention.  It could be left up
> to each registrant whether they want to include <traditional> or
> <simplified> in their domain name.  It needn't be at the second
> level either.  The convention could be that clients with the added
> Chinese support would be suspicious of simplified characters
> anywhere to the left of .<traditional>. (wherever it appears) and
> be suspicious of traditional characters anywhere to the left of
> >.<simplified>. (wherever it appears).  This would allow things
> like <FOO>.<traditional>.ac.uk.  It could be recommended (but
> probably not required) that registration authorities never allow
> <traditional> or <simplified> to be registered under any zone, but
> rather require registrants to register <something>.<traditional> or
> <something>.<simplified>.  It could be recommended (but probably not
> required) that registrars register such names in pairs.

In TWNIC testbed, when the registrants register an TCDN.tw we let them
to use the corresponding one SCDN.tw . We makes such names in pairs.

> One nice thing about your proposal is that it appears to be orthogonal
> to IDNA.  Clients without the added Chinese support can still access
> all domain names, they just won't provide the extra hints when mistyped
> names fail.
>
> AMC

After the fight of IDNA-NAMEPREP-ACE solution, hope the IDN WG would
face  forward to consider about mutilayer resolution,  a new Class. It
would not
be treat as orthogonal to IDNA, it could be the expansion.

Erin Chen
 
 
 




From owner-idn@ops.ietf.org  Wed Aug 15 07: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 HAA12714
	for <idn-archive@lists.ietf.org>; Wed, 15 Aug 2001 07:10:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15WyPq-000FaC-00
	for idn-data@psg.com; Wed, 15 Aug 2001 04:00:50 -0700
Received: from heron.verisign.com ([216.168.233.95])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15WyPp-000FZ7-00
	for idn@ops.ietf.org; Wed, 15 Aug 2001 04:00:49 -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 HAA29827
	for <idn@ops.ietf.org>; Wed, 15 Aug 2001 07:00:17 -0400 (EDT)
Received: by VSVAPOSTALGW1.prod.netsol.com with Internet Mail Service (5.5.2653.19)
	id <NP4F30T1>; Wed, 15 Aug 2001 07:00:02 -0400
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60B849C@vsvapostal3.prod.netsol.com>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: idn@ops.ietf.org
Subject: RE: [idn] opting out of SC/TC equivalence
Date: Wed, 15 Aug 2001 06:54:35 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="utf-8"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

>-----Original Message-----
>From: tsenglm@cc.ncu.edu.tw [mailto:tsenglm@cc.ncu.edu.tw]
>Sent: Wednesday, August 15, 2001 2:11 AM
>To: ben; Adam M. Costello; idn@ops.ietf.org
>Subject: Re: [idn] opting out of SC/TC equivalence
>
>
>       In HongKong , Taiwan,  user use BIG5 code . This code set has no
>simpified chinese scripts. In China , GB code set has no 
>traditional chinese
>scripts . So there are no mixed type of  GB and BIG5 .  But you know
>VeriSign/NSI  announced ML.com  with any UNICODE can be mixed.
>That is the key problems.
>       Any suggestions must be considered  what to do for .COM 
>in this WG.

If composing labels of "mixed" Unicode code points is believed to be a key
problem, that's an issue with current draft documents being developed and
discussed in this WG -- which clearly permit this method of composition.  If
such a composition method doesn't make sense in a particular local context,
it likely won't be widely used to create labels in that local context -- but
that doesn't imply that the conventions of the local context should be
applied everywhere else.

This WG shouldn't attempt to produce solutions particular to a specific name
space.  The end result should be applicable to _any_ name space.

<Scott/>



From owner-idn@ops.ietf.org  Wed Aug 15 10:15: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 KAA21732
	for <idn-archive@lists.ietf.org>; Wed, 15 Aug 2001 10:15:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15X1Dk-000Ixx-00
	for idn-data@psg.com; Wed, 15 Aug 2001 07:00:32 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15X1Dj-000Ixp-00
	for idn@ops.ietf.org; Wed, 15 Aug 2001 07:00:31 -0700
Message-ID: <001b01c12592$fc156cc0$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: "ben" <ben@cc-www.com>, <idn@ops.ietf.org>
References: <E15Wq6x-0007EM-00@psg.com> <000901c12549$c6f882a0$d43f7018@mtag1.on.home.com>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Wed, 15 Aug 2001 10:02:54 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Ben

Your observation:
> However, can you come up with even one good reason why we should allow
> a CDN to have mixed TC and SC?

is rather irresponsible.  TC-SC mix is already common place in HK.

Edmon




From owner-idn@ops.ietf.org  Wed Aug 15 10:17: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 KAA21769
	for <idn-archive@lists.ietf.org>; Wed, 15 Aug 2001 10:17:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15X1HH-000J39-00
	for idn-data@psg.com; Wed, 15 Aug 2001 07:04:11 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15X1HG-000J33-00
	for idn@ops.ietf.org; Wed, 15 Aug 2001 07:04:10 -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, 15 Aug 2001 07:15:20 -0700
Message-ID: <003b01c12594$5c374c80$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, <idn@ops.ietf.org>
References: <E15Wq6x-0007EM-00@psg.com> <000901c12549$c6f882a0$d43f7018@mtag1.on.home.com> <000501c12551$1501c220$fb05738c@ncu.edu.tw>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Wed, 15 Aug 2001 10:12:46 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi L. M. Tseng

I understand that "SC/TC equivalence" is very important to users of
CDNs.  That is why I've made it very clear that I am totally behind
any efforts in finding a reasonable solution to this issue.  I
understand (and I am sure you also understand) that what is considered
a reasonable solution to some, is total unacceptable to others.  The
question then becomes exactly what is it that we can all (or atleast a
majority of us) agree on that can be provided to the users of CDNs- as
ultimately, it is the users of CDNs that should benefit from our work.

If everyone can agree that my Supreme CDN system is indeed "supreme"
(with all humbleness), then there is indeed a need to implement this
supreme system to benefit the users of CDN.  In my opinion, I feel
that the best way is to create a new type of TLD (<.traditional> and
<.simplified>) as described in my draft.

(Everytime I talk about <IDN>.<IDN>, I am so afraid that someone will
respond by saying "this is out of the scope of this IDN WG"... which
is probably true... but anyways...)

Thanks
Ben Chan






----- Original Message -----
From: "tsenglm@è¨ˆç¶²ä¸­å¿ƒ.ä¸­å¤§.tw" <tsenglm@cc.ncu.edu.tw>
To: "ben" <ben@cc-www.com>; "Adam M. Costello" <amc@cs.berkeley.edu>;
<idn@ops.ietf.org>
Sent: Wednesday, August 15, 2001 2:11 AM
Subject: Re: [idn] opting out of SC/TC equivalence


> Hi ! Ben:
> > >
> > > This would limit people's choice of registration authority.
> >
> > In my system, CDNs cannot be a mix of TC and SC.  If that is
> > considered "limit people's choices..." then I am afraid I am
guilty.
> > However, can you come up with even one good reason why we should
allow
> > a CDN to have mixed TC and SC?
> >
>        In HongKong , Taiwan,  user use BIG5 code . This code set has
no
> simpified chinese scripts. In China , GB code set has no traditional
chinese
> scripts . So there are no mixed type of  GB and BIG5 .  But you know
> VeriSign/NSI  announced ML.com  with any UNICODE can be mixed.
> That is the key problems.
>        Any suggestions must be considered  what to do for .COM in
this WG.
> If english character is treated as case folding, Why  CJK can not
treated as
> the same way to reduce the number of registrations for trade mark
> considerations?  Case folding is also not a protocol issue .  It is
> othogonal to IDNA too.
>
> L. M. Tseng,
> > >
> > > > The same techniques documented in this draft can also be
applied
> > > > to the current gTLD and ccTLD registries by using SLDs.  In
order
> > > > to be fair, everyone must agree to this system and make it a
> > > > standard.  In addition, every registry must change their
current
> > > > registered second level domains to third level domains (ie.
> > > > <whatever>.<traditional>.TLD, <whatever>.<simplified>.TLD)
> > >
> > > I don't think there's any need to require that all domains
> > containing
> > > Chinese characters follow this convention.  It could be left up
> > > to each registrant whether they want to include <traditional> or
> > > <simplified> in their domain name.  It needn't be at the second
> > > level either.  The convention could be that clients with the
added
> > > Chinese support would be suspicious of simplified characters
> > > anywhere to the left of .<traditional>. (wherever it appears)
and
> > > be suspicious of traditional characters anywhere to the left of
> > > >.<simplified>. (wherever it appears).  This would allow things
> > > like <FOO>.<traditional>.ac.uk.  It could be recommended (but
> > > probably not required) that registration authorities never allow
> > > <traditional> or <simplified> to be registered under any zone,
but
> > > rather require registrants to register <something>.<traditional>
or
> > > <something>.<simplified>.  It could be recommended (but probably
not
> >
> > > required) that registrars register such names in pairs.
> > >
> > > One nice thing about your proposal is that it appears to be
> > orthogonal
> > > to IDNA.  Clients without the added Chinese support can still
access
> > > all domain names, they just won't provide the extra hints when
> > mistyped
> > > names fail.
> > >
> > > AMC
> > >
> >
> > I feel very strongly that there is a need to create a new type of
TLD
> > (lsTLD- as described in my draft) to implement my idea to satisfy
the
> > needs of CDN users.  Do you have any opinions on that?
> >
> > Thanks
> > Ben Chan
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>




From owner-idn@ops.ietf.org  Wed Aug 15 10: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 KAA22447
	for <idn-archive@lists.ietf.org>; Wed, 15 Aug 2001 10:35:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15X1eq-000JoB-00
	for idn-data@psg.com; Wed, 15 Aug 2001 07:28:32 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15X1ep-000Jo2-00
	for idn@ops.ietf.org; Wed, 15 Aug 2001 07:28:31 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Wed, 15 Aug 2001 07:39:47 -0700
Message-ID: <005701c12597$c6855200$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "Edmon" <edmon@neteka.com>, <idn@ops.ietf.org>
References: <E15Wq6x-0007EM-00@psg.com> <000901c12549$c6f882a0$d43f7018@mtag1.on.home.com> <001b01c12592$fc156cc0$1001a8c0@neteka.com>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Wed, 15 Aug 2001 10:37:13 -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 Edmon,

You are correct, TC-SC is indeed mixed and that is a reality.  I have
said all along that TC and SC are used interchangeably by certain
groups/cultures/background and that is why they are indistinguishable
to those people.

However, my question is "...can you come up with even one good reason
why we should allow a CDN to have mixed TC and SC?"

In other words, just because people mix them, a "supreme CDN system"
should not add to the confusion by allowing a CDN to have mixed TC and
SC (unless you can come up with even one good reason why I should then
I may modify my draft as necessary.)

Thanks
Ben Chan





----- Original Message -----
From: "Edmon" <edmon@neteka.com>
To: "ben" <ben@cc-www.com>; <idn@ops.ietf.org>
Sent: Wednesday, August 15, 2001 10:02 AM
Subject: Re: [idn] opting out of SC/TC equivalence


> Hi Ben
>
> Your observation:
> > However, can you come up with even one good reason why we should
allow
> > a CDN to have mixed TC and SC?
>
> is rather irresponsible.  TC-SC mix is already common place in HK.
>
> Edmon
>




From owner-idn@ops.ietf.org  Wed Aug 15 15: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 PAA29472
	for <idn-archive@lists.ietf.org>; Wed, 15 Aug 2001 15:12:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15X5lD-0006BQ-00
	for idn-data@psg.com; Wed, 15 Aug 2001 11:51:23 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15X5lC-0006BJ-00
	for idn@ops.ietf.org; Wed, 15 Aug 2001 11:51:22 -0700
Received: from zetnet.co.uk (man-s265.dialup.zetnet.co.uk [194.247.45.136])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f7FIoX304454;
	Wed, 15 Aug 2001 19:50:47 +0100
Message-ID: <3B7A5EDD.E0FD316D@zetnet.co.uk>
Date: Wed, 15 Aug 2001 12:37:01 +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: tsenglm@cc.ncu.edu.tw, idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
References: <E15Wq6x-0007EM-00@psg.com> <000901c12549$c6f882a0$d43f7018@mtag1.on.home.com> <000501c12551$1501c220$fb05738c@ncu.edu.tw>
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-----

tsenglm@cc.ncu.edu.tw wrote:
> "ben" <ben@cc-www.com> wrote:
> > "Adam M. Costello" <amc@cs.berkeley.edu> wrote:
> > > This [top-level <.traditional> and <.simplified>] would limit people's
> > > choice of registration authority.

I agree. A TLD (regardless of what script it is in) should specify which
registration authority is responsible for allocations below that TLD.
If language script specifiers are needed then they should go to the left
of the TLD.

However, I don't see any need to require script specifiers; the following
algorithm (to be performed when typing a name into a browser location
field, for example), would seem to be sufficient:

 1. Find the rightmost character (i.e. last in logical order [*]) that is
    specific to TC or SC. Call its script the "rightmost script", and the
    other Chinese script the "opposite script". If there is no such
    character, use the name as-is.
 2. If the name contains any characters from the opposite script, convert
    them to the rightmost script and ask the user whether that's what he/she
    meant.

Support for this would be OPTIONAL; the fact that a name with mixed TC and
SC can be converted to a valid name would not mean that the mixed name is
valid.

[*] Labels that mix Chinese and right-to-left scripts are unlikely; this is
    specified just to make the algorithm unambiguous.

> > In my system, CDNs cannot be a mix of TC and SC.  If that is
> > considered "limit people's choices..." then I am afraid I am guilty.
> > However, can you come up with even one good reason why we should allow
> > a CDN to have mixed TC and SC?

I don't think Adam was suggesting that. The issue is who handles registrations
under <.traditional> and <.simplified> in your scheme.

>        In HongKong , Taiwan,  user use BIG5 code . This code set has no
> simpified chinese scripts. In China , GB code set has no traditional chinese
> scripts . So there are no mixed type of  GB and BIG5 .  But you know
> VeriSign/NSI  announced ML.com  with any UNICODE can be mixed.
> That is the key problems.

Verisign/NSI would be highly premature in announcing any policy about Unicode
names - they don't know what the protocol will support yet. Where did they
announce this?

>        Any suggestions must be considered  what to do for .COM in this WG.
> If english character is treated as case folding, Why  CJK can not treated as
> the same way to reduce the number of registrations for trade mark
> considerations?

Because this type of folding requires only two (or at least a small number
of) registrations if it is done at the server end, whereas case folding
would require on the order of 2^n registrations. Therefore, the trade-off
between client complexity (i.e. the complexity of nameprep) and any server-
side or registration difficulties is quite different.

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

iQEVAwUBO3oggTkCAxeYt5gVAQHUZAf/a8InwXiS6kBsSIulZ4xX/Vdq/CJLO26i
Hc0rDLUVf9BVGGk/5JlFLDXuqIaT6tM8pPWoaJyAe/EYdO4eVo/GqQdltj2iRCUd
b03mJe7Q0405bv8LZpRzQ4DuRsAP55dnNv4X4efP7o/ggbCHZ0NHTvNFyhsvivdI
TKY7oLjKb5YkTCYmjp7MmBKK6dFoeIRErd4nE6/NXTX0x284YOyoaK6qyLe97uTs
LU09FBFpYkvoZI1N226ZL2EM8biUpYOjbIH2en23QHLx9zAroYrmVEsuBTTUBiLq
z8XimX+VnTZS9FhEDI8gLwVHFN+zKj3GG35s4ZuYDAZibM53NnNxEA==
=NRtj
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Wed Aug 15 19:27: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 TAA02883
	for <idn-archive@lists.ietf.org>; Wed, 15 Aug 2001 19:27:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15X9rP-000Ch6-00
	for idn-data@psg.com; Wed, 15 Aug 2001 16:14:03 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15X9rO-000Ch0-00
	for idn@ops.ietf.org; Wed, 15 Aug 2001 16:14:02 -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, 15 Aug 2001 16:25:10 -0700
Message-ID: <002801c125e1$2cb65260$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "David Hopwood" <david.hopwood@zetnet.co.uk>, <tsenglm@cc.ncu.edu.tw>,
        <idn@ops.ietf.org>
References: <E15Wq6x-0007EM-00@psg.com> <000901c12549$c6f882a0$d43f7018@mtag1.on.home.com> <000501c12551$1501c220$fb05738c@ncu.edu.tw> <3B7A5EDD.E0FD316D@zetnet.co.uk>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Wed, 15 Aug 2001 19:22:37 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi David,

>
>  1. Find the rightmost character (i.e. last in logical order [*])
that is
>     specific to TC or SC. Call its script the "rightmost script",
and the
>     other Chinese script the "opposite script". If there is no such
>     character, use the name as-is.
>  2. If the name contains any characters from the opposite script,
convert
>     them to the rightmost script and ask the user whether that's
what he/she
>     meant.
>
>

As much as both Tseng and I want your algorithm to work for the
benefit of the Chinese culture, I think you have over simplified the
problem by leaving out the "one to many" and "many to one" issue in
your algorithm.


> I don't think Adam was suggesting that. The issue is who handles
registrations
> under <.traditional> and <.simplified> in your scheme.
>

I don't think that is my decision.  (By the way, I misinterpreted what
Adam was trying to say so thanks for pointing that out.)

Thanks
Ben Chan






From owner-idn@ops.ietf.org  Thu Aug 16 04:19: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 EAA25968
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 04:19:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XHtj-000OEU-00
	for idn-data@psg.com; Thu, 16 Aug 2001 00:48:59 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XHth-000OEI-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 00:48:57 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+3nwGBQ7c9H9gcyo9/mP+H1ZwaGXUiUHQ==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCXUJEP9; Thu, 16 Aug 2001 03:48:17 EDT
To: shollenbeck@verisign.com
Cc: idn@ops.ietf.org
Date: Thu, 16 Aug 2001 01:05:21 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010816.010531.-830469.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-107,109-147
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, Scott,
  I think you have raised a good question.  However, there is 
no such an " end result should be applicable to _any_ name
 space."  The uppper to low case folding only apply to alphabet
systems, the SC/TC folding only apply to character based 
systems, consonant system has many small scripts all within
128 codepoints.  Following you assertion,  we shall take Latin 
case folding out of [nameprep] too.

From what I have been studing in the past serveral weeks, 
  mixed use of a script is a common situation.  English mixes with
Greek,  French and German in the States, Arabic script used by
several different languages, where each is subset of the Unicode
Aracbic block, Devanagari transcribs Tamil symbols, and the 
current discussion on TC/SC is well known case. 

  We can not affort to have each spoken language to be a 
processing entity in [nameprep], since they are normaly a
subset of a particular script.  

We can allow script based entity to be the processing unit, that 
is CJK, Latin, Cyrillic, Arabic and Indian languages as a few 
script pools.  How many would be there is up to political
debate as it is done in United Nations.  Lately, I have come 
across an article in "San Jose Mercury News" which  says
 "Azerbaijan mandates use of Latin alphabet". From technical side, 
we can say how many of the pools is technically sensible, and
let other languages, such as Tibetan, Vietnanese, Lao to
decide which pool they want to be in, depend on their users as 
well as how their scripts can be best handled technically.  

My initial thought on the pools are:
character based: Chinese, Japanese, Yi
Alphabetic: Latin, Greek, Cyrillic, any IPA based languages
Consonant languages: Indian languages, Arabic, Tibetan

The reason for such pools are simple non-semantic 
handling for [nameprep]:
Character based scripts do have large tables of case folding. 
SC/TC is an example.  I am certain that there will be
Kanji/SC folding and possibly Yi/SC folding too.  Will
there be Hangul/TC folding or  Vietnanese/TC folding? 
I have not heard that but there is historical possibility.  
SC/TC folding affects about 200 one-one folding 
(some 3-1 too), and 146 block to block foldings
affects over 2000 characters. 
 
Alphabet languages all have upper--to-lower case foldings, 
including IPA, which is used for newly created scripts in Africa.  
And they do borrow diacritics from other languages, 
and letters from Greek.  The best example is American 
English.  This case folding affects Unicode block
002-04f,  four sets of scripts: Latin, IPA, Greek and 
Cyrillic, over 100 upper cases.

Consonant languages do not have case foldings but
they borrow symbols from each other.  They transcribe, 
but usally not include Latin or CJK in their writing. 
This group needs codepoint differenciation reducing script
confusion among Armenian, Lao, Thai, Georgian, and 
among a dozent of Indian scripts.  A codepoint verification
of its legal block (normally within 128 codepoints each) shall 
be sufficient.  (With political implication: do they want one 
pure script or more than one?)

I would say we shall divide the languages into several 
language pools, and "the end result should be applicable 
to _any_ name space" within that pool.

Now, I am back to SC/TC folding.  Depending on the
 character encoding used, the folding has four cases:
case 1: transliteration  encoding: no folding;
case 2:GB -to- ACE' : no folding;
case 3:Big5 -to- ACE":  no folding;
case 4:Unicode: block to block and one to one folding.
The first three are realy IDNA output, the last one is the 
case we have to consider in here.

Suppose TC folds to SC, (SC is a smaller than TC)
 in current IDNA> [nameprep]> ACE schem,  then:
GB > Unicode > [nameprep] > ACE;
Big5 > Unicode > fold to SC > [nameprep] > ACE;
Mixed Unicode > fold to SC > [nameprep] > ACE.

So, 
	IDNA?			[nameprep]?		ACE
GB > Unicode SC
Big5>Unicode > SC Unicode	Latin Case folding	ACE encoding
Mixed Unicode > SC Unicode	

If this is the case, then what IDNA is doing? What about other 
three cases IDNA is supposed to handle? What is the purpose for
SC Unicode go through [nameprep] at all, why not directly go
to ACE then?

I do not think the above is a reasonable processing model. 
 Instead all the above should be in [nameprep]. [nameprep]
should be divided into three pool cases (up for debate) and
 treated with somewhat uniformed procedure for each of the three:
alphabet: case folding 
character: case folding, allow GB, Big5, JIS, and KSC to Unicode 
	mapping too
consonant system:  allow ISCII to Unicode mapping and tag 
	identification for script specific process into ACE.

Liana


On Wed, 15 Aug 2001 06:54:35 -0400 "Hollenbeck, Scott"
<shollenbeck@verisign.com> writes:
> >-----Original Message-----
> >From: tsenglm@cc.ncu.edu.tw [mailto:tsenglm@cc.ncu.edu.tw]
> >Sent: Wednesday, August 15, 2001 2:11 AM
> >To: ben; Adam M. Costello; idn@ops.ietf.org
> >Subject: Re: [idn] opting out of SC/TC equivalence
> >
> >
> >       In HongKong , Taiwan,  user use BIG5 code . This code set 
> has no
> >simpified chinese scripts. In China , GB code set has no 
> >traditional chinese
> >scripts . So there are no mixed type of  GB and BIG5 .  But you 
> know
> >VeriSign/NSI  announced ML.com  with any UNICODE can be mixed.
> >That is the key problems.
> >       Any suggestions must be considered  what to do for .COM 
> >in this WG.
> 
> If composing labels of "mixed" Unicode code points is believed to be 
> a key
> problem, that's an issue with current draft documents being 
> developed and
> discussed in this WG -- which clearly permit this method of 
> composition.  If
> such a composition method doesn't make sense in a particular local 
> context,
> it likely won't be widely used to create labels in that local 
> context -- but
> that doesn't imply that the conventions of the local context should 
> be
> applied everywhere else.
> 
> This WG shouldn't attempt to produce solutions particular to a 
> specific name
> space.  The end result should be applicable to _any_ name space.
> 
> <Scott/>
> 



From owner-idn@ops.ietf.org  Thu Aug 16 10:44: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 KAA10170
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 10:44:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XO6n-0006yw-00
	for idn-data@psg.com; Thu, 16 Aug 2001 07:26:53 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15XO6n-0006yq-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 07:26:53 -0700
Message-ID: <001301c1265f$d061bf20$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: "ben" <ben@cc-www.com>, <idn@ops.ietf.org>
References: <E15Wq6x-0007EM-00@psg.com> <000901c12549$c6f882a0$d43f7018@mtag1.on.home.com> <001b01c12592$fc156cc0$1001a8c0@neteka.com> <005701c12597$c6855200$d43f7018@mtag1.on.home.com> <004c01c125bb$59d92680$1001a8c0@neteka.com> <004901c125e4$edcd23e0$d43f7018@mtag1.on.home.com>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Thu, 16 Aug 2001 10:29:05 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Ben

From: "ben" <ben@cc-www.com>
>
> "ColorCentre.com" and "ColourCenter.com" is ok in English.  However,
> "<tc><tc><sc><sc><tc><sc>.com" is a recipe for disaster.

So, can you come up with one good reason why BE+AE (British English -
American English) is OK and TC+SC is not?

I have seen quite a number of brand names now beginning to have TC-SC mix in
HK.  My point is that TC and SC are no longer simply a straight mapping of
each other, or in technical terms a compatible character or simply a
different script.  Each character in the Chinese repertoire is becoming a
character of its own right, the line between TC-SC is starting to blur.
They are all "Chinese Characters".

>
> From: "Edmon" <edmon@neteka.com>
> > Hi Ben,
> > Presently, I can have:
> >
> >    ColorCentre.com
> >
> > and someone else can have
> >
> >    ColourCenter.com
> >
> > I am mixing British-English and American-English.
> >
> > Are you saying that these two domain names should be mapped to
> >
> >    ColourCentre.com
> >    ColorCenter.com
> >
> > and all should be the same domain?
> >
> > From my perspective, this is the issue we are facing with TC/SC
> > mapping.
> > I respect that some registries and domain operators wish to have
> > TC=SC, but
> > I think, as a consumer, I wish to have the option to treat them
> > differently.
> >
> > Edmon
> >




From owner-idn@ops.ietf.org  Thu Aug 16 11:21: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 LAA12484
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 11:21:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XOqU-0008V0-00
	for idn-data@psg.com; Thu, 16 Aug 2001 08:14:06 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XOqT-0008Ut-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 08:14:06 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+3nwGBQ7c9HzVrHZpEK5GpJJYwD1z8cBw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCYMW8QK; Thu, 16 Aug 2001 11:12:12 EDT
To: shollenbeck@verisign.com
Cc: idn@ops.ietf.org
Date: Thu, 16 Aug 2001 08:29:28 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010816.082932.-806155.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

The following SC/TC equivalence comtains a mistake:

	IDNA?			[nameprep]?		ACE
GB > Unicode SC
Big5>Unicode > SC Unicode	Latin Case folding	ACE encoding
Mixed Unicode > SC Unicode	

and it should be:

	IDNA?			[nameprep]?		ACE
GB > SC Unicode 
Big5>SC Unicode		Latin Case folding	ACE encoding
Mixed Unicode > SC Unicode	

So, the proposal is:

	[nameprep]			ACE
GB > SC Unicode 
Big5>SC Unicode			ACE encoding
Mixed Unicode > SC Unicode	
Latin Case folding
JIS > SC Unicode
KSC > TC Unicode
ISCII > Indic Unicode

There are limited number of standards which is referenced 
by Unicode standard, where we can allow limited number of
them to make into [nameprep].  

Liana



From owner-idn@ops.ietf.org  Thu Aug 16 11:41: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 LAA13489
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 11:41:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XP0B-0008rX-00
	for idn-data@psg.com; Thu, 16 Aug 2001 08:24:07 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XP0A-0008rN-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 08:24:06 -0700
Received: from cs881964a ([24.112.63.212]) by mail.paconline.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-71798U5300L500S0V35)
          with SMTP id net; Thu, 16 Aug 2001 08:35:18 -0700
Message-ID: <006901c12668$b488c100$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "Edmon" <edmon@neteka.com>, <idn@ops.ietf.org>
References: <E15Wq6x-0007EM-00@psg.com> <000901c12549$c6f882a0$d43f7018@mtag1.on.home.com> <001b01c12592$fc156cc0$1001a8c0@neteka.com> <005701c12597$c6855200$d43f7018@mtag1.on.home.com> <004c01c125bb$59d92680$1001a8c0@neteka.com> <004901c125e4$edcd23e0$d43f7018@mtag1.on.home.com> <001301c1265f$d061bf20$1001a8c0@neteka.com>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Thu, 16 Aug 2001 11:32: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 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 Edmon,

I could care less about other registries and what they do.

However, I do care about my own "Supreme CDN system" because this
system takes the benefits of others to combine into a supreme.  It is
to be implemented for the benefit of everyday ordinary people who will
be the user of CDNs.  My supreme system does not allow mixing unless
you can give me a good reason.  If I think you have a good reason,
then I will modify my draft.  Otherwise I will not.

Tell me how confusing "ColorColourColor.com" and
"CentreCenterCentre.com" can be.  Then multiply that confusion
exponentially due to the "one to many" mapping of TC/SC chinese (among
others)... and you have the reason why I do not allow mixing of TC and
SC in my supreme CDN system.

Thanks
Ben Chan





----- Original Message -----
From: "Edmon" <edmon@neteka.com>
To: "ben" <ben@cc-www.com>; <idn@ops.ietf.org>
Sent: Thursday, August 16, 2001 10:29 AM
Subject: Re: [idn] opting out of SC/TC equivalence


> Hi Ben
>
> From: "ben" <ben@cc-www.com>
> >
> > "ColorCentre.com" and "ColourCenter.com" is ok in English.
However,
> > "<tc><tc><sc><sc><tc><sc>.com" is a recipe for disaster.
>
> So, can you come up with one good reason why BE+AE (British
English -
> American English) is OK and TC+SC is not?
>
> I have seen quite a number of brand names now beginning to have
TC-SC mix in
> HK.  My point is that TC and SC are no longer simply a straight
mapping of
> each other, or in technical terms a compatible character or simply a
> different script.  Each character in the Chinese repertoire is
becoming a
> character of its own right, the line between TC-SC is starting to
blur.
> They are all "Chinese Characters".
>
> >
> > From: "Edmon" <edmon@neteka.com>
> > > Hi Ben,
> > > Presently, I can have:
> > >
> > >    ColorCentre.com
> > >
> > > and someone else can have
> > >
> > >    ColourCenter.com
> > >
> > > I am mixing British-English and American-English.
> > >
> > > Are you saying that these two domain names should be mapped to
> > >
> > >    ColourCentre.com
> > >    ColorCenter.com
> > >
> > > and all should be the same domain?
> > >
> > > From my perspective, this is the issue we are facing with TC/SC
> > > mapping.
> > > I respect that some registries and domain operators wish to have
> > > TC=SC, but
> > > I think, as a consumer, I wish to have the option to treat them
> > > differently.
> > >
> > > Edmon
> > >
>
>




From owner-idn@ops.ietf.org  Thu Aug 16 12:20: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 MAA15065
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 12:20:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XPmj-000ANF-00
	for idn-data@psg.com; Thu, 16 Aug 2001 09:14:17 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XPmf-000AME-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 09:14:15 -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 f7GGArO52428;
	Thu, 16 Aug 2001 12:10:53 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200108161610.f7GGArO52428@nic-naa.net>
To: "ben" <ben@cc-www.com>
cc: "Edmon" <edmon@neteka.com>, idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] opting out of SC/TC equivalence 
In-Reply-To: Your message of "Thu, 16 Aug 2001 11:32:47 EDT."
             <006901c12668$b488c100$d43f7018@mtag1.on.home.com> 
Date: Thu, 16 Aug 2001 12:10:53 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> I could care less about other registries and what they do.

Then there is no IETF issue for you.

...
> then I will modify my draft.

What draft?



From owner-idn@ops.ietf.org  Thu Aug 16 12:23: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 MAA15156
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 12:23:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XPp4-000ARG-00
	for idn-data@psg.com; Thu, 16 Aug 2001 09:16:42 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XPp1-000AQx-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 09:16:40 -0700
Received: from test.ncu.edu.tw ([140.115.5.251])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f7GGL6710863;
	Fri, 17 Aug 2001 00:21:09 +0800 (CST)
Message-ID: <001001c1266e$bc43c2e0$fb05738c@ncu.edu.tw>
From: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: "Edmon" <edmon@neteka.com>, "ben" <ben@cc-www.com>, <idn@ops.ietf.org>
References: <E15Wq6x-0007EM-00@psg.com> <000901c12549$c6f882a0$d43f7018@mtag1.on.home.com> <001b01c12592$fc156cc0$1001a8c0@neteka.com> <005701c12597$c6855200$d43f7018@mtag1.on.home.com> <004c01c125bb$59d92680$1001a8c0@neteka.com> <004901c125e4$edcd23e0$d43f7018@mtag1.on.home.com> <001301c1265f$d061bf20$1001a8c0@neteka.com>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 17 Aug 2001 00:15:53 +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.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Edmon:
            I will try to give some explaination althought my english is not
good. I can told to you straightly that if many Chinese people (including
Taiwan, HongKong & Mainland China)see your example and wishness, they will
be very angry to your description. Why ?
            In Twaiwan,  HongKong we use BIG5 code and many simplified
scripts can not be key-in and displayed in their system. Many people they
know traditional chinese characters but they don't know its corresponding
simplified characters.  Reversely, in mainland china people only know
simplified characters. The corresponding TC/SC has the same pronunciation
and meanning.  Todday people want to communicate each other, they regist a
domain name for some trade mark reasons , but the ML.COM system can not
provide the same chance to protect their rights. People in Taiwan regists a
TC name but he can not key-in to regist the corresponding SC name because he
even don't know how to do it . Then one day , some people in mainland china
they regist the corresponding SC name in SC.COM , it is the same meanning
and prouncing in TC.COM . What will be happen ?  You know that PRC and
Taiwan , even HongKong are different goverenment ,  the argument in
intellegent right is a big trouble.  The case is very like that you allow
one people to regist ABC.com and also allowed another people to regist
abc.com and told them  that is an option and chance . Are you like english
are treated in this way ? Why case folding is needed ? Only the history
reason ? Why full case alphabet must be mapped to ASCII ?
             Are you like to make trouble to us ?  That is why department of
China  information industry against chinese.COM so deeply.
             I don't care the mixing of TC/SC , but I care why we are forced
.....

L.M.Tseng

----- Original Message -----
From: "Edmon" <edmon@neteka.com>
To: "ben" <ben@cc-www.com>; <idn@ops.ietf.org>
Sent: Thursday, August 16, 2001 10:29 PM
Subject: Re: [idn] opting out of SC/TC equivalence


> Hi Ben
>
> From: "ben" <ben@cc-www.com>
> >
> > "ColorCentre.com" and "ColourCenter.com" is ok in English.  However,
> > "<tc><tc><sc><sc><tc><sc>.com" is a recipe for disaster.
>
> So, can you come up with one good reason why BE+AE (British English -
> American English) is OK and TC+SC is not?
>
> I have seen quite a number of brand names now beginning to have TC-SC mix
in
> HK.  My point is that TC and SC are no longer simply a straight mapping of
> each other, or in technical terms a compatible character or simply a
> different script.  Each character in the Chinese repertoire is becoming a
> character of its own right, the line between TC-SC is starting to blur.
> They are all "Chinese Characters".
>
> >
> > From: "Edmon" <edmon@neteka.com>
> > > Hi Ben,
> > > Presently, I can have:
> > >
> > >    ColorCentre.com
> > >
> > > and someone else can have
> > >
> > >    ColourCenter.com
> > >
> > > I am mixing British-English and American-English.
> > >
> > > Are you saying that these two domain names should be mapped to
> > >
> > >    ColourCentre.com
> > >    ColorCenter.com
> > >
> > > and all should be the same domain?
> > >
> > > From my perspective, this is the issue we are facing with TC/SC
> > > mapping.
> > > I respect that some registries and domain operators wish to have
> > > TC=SC, but
> > > I think, as a consumer, I wish to have the option to treat them
> > > differently.
> > >
> > > Edmon
> > >
>
>
>




From owner-idn@ops.ietf.org  Thu Aug 16 12:30: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 MAA15274
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 12:30:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XPx2-000AhM-00
	for idn-data@psg.com; Thu, 16 Aug 2001 09:24:56 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XPx2-000AhF-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 09:24:56 -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, 16 Aug 2001 09:36:07 -0700
Message-ID: <00d901c12671$334b0900$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: "Edmon" <edmon@neteka.com>, <idn@ops.ietf.org>, <brunner@nic-naa.net>
References: <200108161610.f7GGArO52428@nic-naa.net>
Subject: Re: [idn] opting out of SC/TC equivalence 
Date: Thu, 16 Aug 2001 12:33:36 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Eric,

> > I could care less about other registries and what they do.
>
> Then there is no IETF issue for you.
>

My IETF issue is to get support for my "supreme CDN system" to be
implemented as a standard.  Do I have your support?

> ...
> > then I will modify my draft.
>
> What draft?

I said "draft", I did not say "Internet draft".

Thanks
Ben Chan






From owner-idn@ops.ietf.org  Thu Aug 16 12:53: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 MAA15866
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 12:53:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XQHG-000BLm-00
	for idn-data@psg.com; Thu, 16 Aug 2001 09:45:50 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XQHC-000BLe-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 09:45:47 -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 f7GGgjO53297;
	Thu, 16 Aug 2001 12:42:45 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200108161642.f7GGgjO53297@nic-naa.net>
To: "ben" <ben@cc-www.com>
cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        "Edmon" <edmon@neteka.com>, idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] opting out of SC/TC equivalence 
In-Reply-To: Your message of "Thu, 16 Aug 2001 12:33:36 EDT."
             <00d901c12671$334b0900$d43f7018@mtag1.on.home.com> 
Date: Thu, 16 Aug 2001 12:42:45 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> My IETF issue is to get support for my "supreme CDN system" to be
> implemented as a standard.  Do I have your support?

and

> I said "draft", I did not say "Internet draft".

What "supreme CDN system"? What draft?



From owner-idn@ops.ietf.org  Thu Aug 16 13:31: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 NAA16744
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 13:31:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XQsc-000CT8-00
	for idn-data@psg.com; Thu, 16 Aug 2001 10:24:26 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15XQsb-000CT2-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 10:24:25 -0700
Message-ID: <003d01c12678$932cc3c0$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: =?UTF-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>,
        "ben" <ben@cc-www.com>, <idn@ops.ietf.org>
References: <E15Wq6x-0007EM-00@psg.com> <000901c12549$c6f882a0$d43f7018@mtag1.on.home.com> <001b01c12592$fc156cc0$1001a8c0@neteka.com> <005701c12597$c6855200$d43f7018@mtag1.on.home.com> <004c01c125bb$59d92680$1001a8c0@neteka.com> <004901c125e4$edcd23e0$d43f7018@mtag1.on.home.com> <001301c1265f$d061bf20$1001a8c0@neteka.com> <001001c1266e$bc43c2e0$fb05738c@ncu.edu.tw>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Thu, 16 Aug 2001 13:26:20 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi Tseng,

First of all, I am all for a standardized SC=TC.  But I would rather see
that it is given as an option for registries or zone operators to determine
because SC and TC characters are characters in their own right.

The only real argument I see about this is the DNSSEC issue Erik Nordmark
pointed out, but I can see that there are ways around it but it would mean
that we would have to slightly adjust DNSSEC which we have agreed is totally
outside of the scope of this wg.  So if we are forced to make a decision on
this without the liberty to adjust DNSSEC (which as far as last IETF meeting
some of it might even never see day of light), then it is a rather
unfortunate situation.

Please do not confuse my thinking as to me being against SC=TC, I am
expressing my concern as a consumer wishing to have a choice.  Also,
philosophically I believe they are different characters.


From: "tsenglm@è¨ˆç¶²ä¸­å¿ƒ.ä¸­å¤§.tw" <tsenglm@cc.ncu.edu.tw>
>             In Twaiwan,  HongKong we use BIG5 code and many simplified
> scripts can not be key-in and displayed in their system. Many people they
> know traditional chinese characters but they don't know its corresponding
> simplified characters.  Reversely, in mainland china people only know
> simplified characters. The corresponding TC/SC has the same pronunciation
> and meanning.

That is the reason why we have unicode in the first place.  Also you have
pointed out a very good reason why TC and SC are different.  Many people
know TC and not SC and vice versa, so why and how would someone confuse a TC
domain with an SC domain?

> Todday people want to communicate each other, they regist a
> domain name for some trade mark reasons , but the ML.COM system can not
> provide the same chance to protect their rights. People in Taiwan regists
a
> TC name but he can not key-in to regist the corresponding SC name because
he
> even don't know how to do it . Then one day , some people in mainland
china
> they regist the corresponding SC name in SC.COM , it is the same meanning
> and prouncing in TC.COM . What will be happen ?  You know that PRC and
> Taiwan , even HongKong are different goverenment ,  the argument in
> intellegent right is a big trouble.

That is why I champion the SC=TC option for registries.  The problem about
forcing TC=SC into Nameprep is that we will loose the option at all levels.
Even if I own <TC>.com I wont be able to distinguish <TC>.<TC>.com from
<SC>.<TC>.com or worse, if I am now called abc.com I wont be able to have
distinct sub-zones <TC>.abc.com and <SC>.abc.com.  That is the main problem
I see and as a group we should contemplate on this matter too, not just the
second level domains that are sold.

> The case is very like that you allow
> one people to regist ABC.com and also allowed another people to regist
> abc.com and told them  that is an option and chance . Are you like english
> are treated in this way ? Why case folding is needed ? Only the history
> reason ? Why full case alphabet must be mapped to ASCII ?

I disagree to your analysis, TC and SC is rather like
Color and Colour AE and BE (American English and Bristish English)

so Color.com is different from Colour.com

and yes they are registered by two different parties.


>              Are you like to make trouble to us ?  That is why department
of
> China  information industry against chinese.COM so deeply.
>              I don't care the mixing of TC/SC , but I care why we are
forced
> .....
>
I dont really get your question here, but again I stress that I think it is
important to have a standardized TC-SC conversion mechanism, but we should
also allow individual zone operators to decide whether the TC=SC rule should
be applied.

Edmon




From owner-idn@ops.ietf.org  Thu Aug 16 13:50: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 NAA17524
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 13:50:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XRAF-000D17-00
	for idn-data@psg.com; Thu, 16 Aug 2001 10:42:39 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XRAD-000D10-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 10:42:38 -0700
Received: from zetnet.co.uk (man-s041.dialup.zetnet.co.uk [194.247.41.168])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f7GHgX201514;
	Thu, 16 Aug 2001 18:42:33 +0100
Message-ID: <3B7B4FED.820CBD5B@zetnet.co.uk>
Date: Thu, 16 Aug 2001 05:45: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] opting out of SC/TC equivalence
References: <20010816.010531.-830469.1.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:
> I think you have raised a good question.  However, there is
> no such an "end result should be applicable to _any_ name
> space."  The uppper to low case folding only apply to alphabet
> systems, the SC/TC folding only apply to character based
> systems, consonant system has many small scripts all within
> 128 codepoints.  Following you assertion,  we shall take Latin
> case folding out of [nameprep] too.

Case folding for domain names in Latin scripts is a historical accident.
If it wasn't there, no users of those scripts would miss it - they
would just always type lowercase. However, given that case folding is
defined for ASCII, that effectively forces the decision to extend it
to other Latin characters, because it would be inconsistent to have a
folding for, say, E -> e, but not E-acute -> e-acute. And given that
decision for Latin characters, the obvious approach is to use the
standard Unicode case-folding algorithm, which also applies to other
cased alphabetic scripts.

Note that there are plenty of identifier standards that are case-sensitive
and work fine (e.g. most parts of an URI). Most end-users probably don't
even notice the difference between case-sensitive and case-insensitive
identifiers.

So, use of alphabetic case folding does not imply anything about whether
TC and SC should be folded; that's a separate decision. There's a
"slippery slope" argument here: if TC/SC are folded, why not Latin <->
Cyrillic transliteration (used for Serbo-Croatian or in Azerbaijan, for
example), or any of the other cases where a language can be written in
more than one script? I see that later in your post you suggest Kanji/SC
and other foldings.

I think that that way lies pointless complication and unnecessary delay
in finalizing the standard, for a feature that is only of minor benefit
to users. In the case of guessing a web site name, if a user can't find
the name immediately then he/she will just use a search engine, and the
search engine will work regardless of what script is used. In other cases,
domain-name-based identifiers such as email addresses and URIs can't
realistically be guessed, so will come from either:

 - another electronic document; this presents no problems
 - a written source; again this presents no problems as long as the user
   has an appropriate input method for the script
 - a spoken source; in this case the script has to be specified to
   avoid ambiguity in general, but the context will often make it
   clear anyway.

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

iQEVAwUBO3tPnDkCAxeYt5gVAQG6JQgAwwu/t1PqSlE1gGIfujUNVyIFqDg/PXYG
giKRDVAgy18EpcLdmz6rnFT2jXaiGtqggK/znjx2HxcmZa5vLV8JeehEVTnZaJl1
qWSRgHWpZg2B2YNO1ZrtrpmwWMPJ9yyn+0GOXI8EUqKmSbAV3W5v9Vvdn8Cx0Yp+
/0zcKTAh6jtGBAIKVmVCRLy5q5yxPRnotzenyWxFxy3rYU35+CvMOMj3FGPk4OO0
17XyhFfJUA0kYILIYhmbWoQmreo8sjMqHw9vtQPG6chjPop+fxyMCX68Oqt4J9sj
ZkRcQY3og/RpB9iGXA5eYDZDdyb11I8CuAmPL8v2Fg5NIiUNclHeeQ==
=d9kT
-----END PGP SIGNATURE-----




From owner-idn@ops.ietf.org  Thu Aug 16 13:58: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 NAA17700
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 13:58:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XRHW-000DDh-00
	for idn-data@psg.com; Thu, 16 Aug 2001 10:50:10 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XRHS-000DCm-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 10:50: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 f7GHjwO54974;
	Thu, 16 Aug 2001 13:45:58 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200108161745.f7GHjwO54974@nic-naa.net>
To: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
cc: "Edmon" <edmon@neteka.com>, "ben" <ben@cc-www.com>, idn@ops.ietf.org,
        brunner@nic-naa.net
Subject: Re: [idn] opting out of SC/TC equivalence 
In-Reply-To: Your message of "Fri, 17 Aug 2001 00:15:53 +0800."
             <001001c1266e$bc43c2e0$fb05738c@ncu.edu.tw> 
Date: Thu, 16 Aug 2001 13:45:58 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk


Over dinner (in a chinese restaurant in the China Town district of London,
of course), a vendor (here nameless) offered his opinon that ASCII users
will enjoy the use of "$" as an alternative to "s" (or "S"), when "$" (and
POSIX shell meta-characters are added to the ACE-or-native-via-utf-* IDN
character repetorire.

Thus:

	www.johnnyca$h.com
	www.micro$oft.com

(Note: www.johnnycash.com is a site, operated by the Estate of Johnny Cash,
 and www.microsoft.com is a site, operated by the MicroSoft Corporation)

I was unamused. Vendor promotion of locally scoped "surprises" is infra dig.

The same vendor, and some others not associated with any known vendor or dns
operator, also advocates TC/SC equivalence rules by registrants, which as L.
M. Tseng notes, would not amuse users on the Mainland, in Taiwan, or in Hong
Kong.

It is not useful to continue down this path.

2^^(number-of-chars-in-name) non-equivalencies does not scale, and that is
only for simple case of 1-to-1 character mappings.

The equivalences for Chinese characters are not privately defined, at least
not interoperably.

Eric



From owner-idn@ops.ietf.org  Thu Aug 16 14:29: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 OAA18597
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 14:29:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XRnp-000EFK-00
	for idn-data@psg.com; Thu, 16 Aug 2001 11:23:33 -0700
Received: from tnt.isi.edu ([128.9.128.128])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XRnp-000EFE-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 11:23:33 -0700
Received: from zed.isi.edu (zed.isi.edu [128.9.160.57])
	by tnt.isi.edu (8.11.2/8.11.2) with ESMTP id f7GINLm04962;
	Thu, 16 Aug 2001 11:23:21 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Received: (from bmanning@localhost)
	by zed.isi.edu (8.11.0/8.8.6) id f7GINLU08493;
	Thu, 16 Aug 2001 11:23:21 -0700
Message-Id: <200108161823.f7GINLU08493@zed.isi.edu>
Subject: Re: [idn] opting out of SC/TC equivalence
To: ben@cc-www.com (ben)
Date: Thu, 16 Aug 2001 11:23:20 -0700 (PDT)
Cc: brunner@nic-naa.net (Eric Brunner-Williams in Portland Maine),
        edmon@neteka.com (Edmon), idn@ops.ietf.org
In-Reply-To: <00d901c12671$334b0900$d43f7018@mtag1.on.home.com> from "ben" at Aug 16, 2001 12:33:36 PM
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

% 
% Hi Eric,
% 
% > > I could care less about other registries and what they do.
% >
% > Then there is no IETF issue for you.
% >
% 
% My IETF issue is to get support for my "supreme CDN system" to be
% implemented as a standard.  Do I have your support?

	While I'll leave Eric to answer that question for himself,
	I am left cold by your attitude regarding IETF participation
	and consenses building. Until you are willing to learn from
	others and have responsible dialog, it is my opinion that
	you will not gain support for your flawed ideas.
	But, since you don't care about other registries, interoperability
	is not an issue... ergo, its not an IETF issue, your SCS is a closed,
	propriatary solution.  It will never be a standard.

% > ...
% > > then I will modify my draft.
% >
% > What draft?
% 
% I said "draft", I did not say "Internet draft".

	Again, what draft. Neither Eric or I mentioned "Internet Draft".
	Further evidence that your idea is closed and propriatary. Perhaps.
	
% Thanks
% Ben Chan


-- 
--bill



From owner-idn@ops.ietf.org  Thu Aug 16 14:45: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 OAA19313
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 14:45:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XRyE-000Ean-00
	for idn-data@psg.com; Thu, 16 Aug 2001 11:34:18 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XRyC-000Eah-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 11:34:16 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id F2A88FFC06; Fri, 17 Aug 2001 02:35:39 +0800 (SGT)
Message-ID: <03e601c12682$07fc8c40$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>,
        <idn@ops.ietf.org>
References: <E15Wq6x-0007EM-00@psg.com> <000901c12549$c6f882a0$d43f7018@mtag1.on.home.com> <001b01c12592$fc156cc0$1001a8c0@neteka.com> <005701c12597$c6855200$d43f7018@mtag1.on.home.com> <004c01c125bb$59d92680$1001a8c0@neteka.com> <004901c125e4$edcd23e0$d43f7018@mtag1.on.home.com> <001301c1265f$d061bf20$1001a8c0@neteka.com> <001001c1266e$bc43c2e0$fb05738c@ncu.edu.tw>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 17 Aug 2001 02:34:05 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi Prof Tseng,

I think this TC/SC issues have been discussed again and again. The only
contention is of course how to solve the the problem. I hope we can
agree that so long this TC/SC is been handled, the exact mechanism is
open for discussion.

I spend several hours discussing with eric chen, wenhui, deng xiang and
others on this in London and I hope they have brought back my
suggestions to you.

My stand on this is as I stated during the meeting. Nameprep must be
uniform. There should be no optional folding which would be done in some
but not in others. Not every application of domain names have the luxury
of user interface or asking the user for information (note: email
servers, digital certificate authorization etc).

Therefore, if TC/SC is to be done in Nameprep, then I would prefer it to
be done across the board. But of course, this would means languages
which uses Chinese script (like kanji and Hanja) would also do the
same folding.

This is why I suggested that TC/SC to be done on zone file level and not
Nameprep. For those who knows Chinese, TC/SC is not really a 2^n problem
so lets not continue this misconception (It is closer to a n*2 to n*4
opertionally). And the memory problem could be simplified by ultizing
some algorithm (since it is fairly structured) to reduce the memory
usage. It can be done and it have been done. (We done it for 2^n btw
with reasonable memory use).

Of course, ultimately, the decision would still lies on the document
authors to come to an agreement on the approach and consensus in the wg.
But lets not forget why we are doing IDN in the first place so lets not
get too carried away in our discussion.

In the meantime, I would like to recommend the authors for tsconv to
complete the draft. The tables mapping is not complete. I would suggest
submitting the draft to Unicode Consortium or some other code point
expert group for review if possible.

Thank you.

ps: No, I did not attend Eric Brunner's UTF-8 dinner. Both Marc and
myself are tied in meeting prepration. We are interested in the
discussion tho so if anyone keep notes, please post.

-James Seng

----- Original Message -----
From: "tsenglm@è¨ˆç¶²ä¸­å¿ƒ.ä¸­å¤§.tw" <tsenglm@cc.ncu.edu.tw>
To: "Edmon" <edmon@neteka.com>; "ben" <ben@cc-www.com>;
<idn@ops.ietf.org>
Sent: Friday, August 17, 2001 12:15 AM
Subject: Re: [idn] opting out of SC/TC equivalence


> Edmon:
>             I will try to give some explaination althought my english
is not
> good. I can told to you straightly that if many Chinese people
(including
> Taiwan, HongKong & Mainland China)see your example and wishness, they
will
> be very angry to your description. Why ?
>             In Twaiwan,  HongKong we use BIG5 code and many simplified
> scripts can not be key-in and displayed in their system. Many people
they
> know traditional chinese characters but they don't know its
corresponding
> simplified characters.  Reversely, in mainland china people only know
> simplified characters. The corresponding TC/SC has the same
pronunciation
> and meanning.  Todday people want to communicate each other, they
regist a
> domain name for some trade mark reasons , but the ML.COM system can
not
> provide the same chance to protect their rights. People in Taiwan
regists a
> TC name but he can not key-in to regist the corresponding SC name
because he
> even don't know how to do it . Then one day , some people in mainland
china
> they regist the corresponding SC name in SC.COM , it is the same
meanning
> and prouncing in TC.COM . What will be happen ?  You know that PRC and
> Taiwan , even HongKong are different goverenment ,  the argument in
> intellegent right is a big trouble.  The case is very like that you
allow
> one people to regist ABC.com and also allowed another people to regist
> abc.com and told them  that is an option and chance . Are you like
english
> are treated in this way ? Why case folding is needed ? Only the
history
> reason ? Why full case alphabet must be mapped to ASCII ?
>              Are you like to make trouble to us ?  That is why
department of
> China  information industry against chinese.COM so deeply.
>              I don't care the mixing of TC/SC , but I care why we are
forced
> .....
>
> L.M.Tseng
>
> ----- Original Message -----
> From: "Edmon" <edmon@neteka.com>
> To: "ben" <ben@cc-www.com>; <idn@ops.ietf.org>
> Sent: Thursday, August 16, 2001 10:29 PM
> Subject: Re: [idn] opting out of SC/TC equivalence
>
>
> > Hi Ben
> >
> > From: "ben" <ben@cc-www.com>
> > >
> > > "ColorCentre.com" and "ColourCenter.com" is ok in English.
However,
> > > "<tc><tc><sc><sc><tc><sc>.com" is a recipe for disaster.
> >
> > So, can you come up with one good reason why BE+AE (British
English -
> > American English) is OK and TC+SC is not?
> >
> > I have seen quite a number of brand names now beginning to have
TC-SC mix
> in
> > HK.  My point is that TC and SC are no longer simply a straight
mapping of
> > each other, or in technical terms a compatible character or simply a
> > different script.  Each character in the Chinese repertoire is
becoming a
> > character of its own right, the line between TC-SC is starting to
blur.
> > They are all "Chinese Characters".
> >
> > >
> > > From: "Edmon" <edmon@neteka.com>
> > > > Hi Ben,
> > > > Presently, I can have:
> > > >
> > > >    ColorCentre.com
> > > >
> > > > and someone else can have
> > > >
> > > >    ColourCenter.com
> > > >
> > > > I am mixing British-English and American-English.
> > > >
> > > > Are you saying that these two domain names should be mapped to
> > > >
> > > >    ColourCentre.com
> > > >    ColorCenter.com
> > > >
> > > > and all should be the same domain?
> > > >
> > > > From my perspective, this is the issue we are facing with TC/SC
> > > > mapping.
> > > > I respect that some registries and domain operators wish to have
> > > > TC=SC, but
> > > > I think, as a consumer, I wish to have the option to treat them
> > > > differently.
> > > >
> > > > Edmon
> > > >
> >
> >
> >
>
>





From owner-idn@ops.ietf.org  Thu Aug 16 14: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 OAA19324
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 14:45:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XS3O-000Ejw-00
	for idn-data@psg.com; Thu, 16 Aug 2001 11:39:38 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XS3N-000Ejp-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 11:39:37 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 4C1AFFFC07; Fri, 17 Aug 2001 02:41:01 +0800 (SGT)
Message-ID: <03ec01c12682$c780de40$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Bill Manning" <bmanning@ISI.EDU>, "ben" <ben@cc-www.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        "Edmon" <edmon@neteka.com>, <idn@ops.ietf.org>
References: <200108161823.f7GINLU08493@zed.isi.edu>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 17 Aug 2001 02:39:27 +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

Once again, wearing my co-chair hat, I need to cut this discussion on
"Supreme CDN". There is no Internet Draft, and neither is it in the core
interest. Hence, lets not waste working group bandwidth on this further.

Further discussion on Supreme CDN should be bring offline. Thanks.

Ben, it would also be worthwhile to look at "The Tao of IETF"
(http://www.ietf.org/tao.html) to get a understanding of how IETF
function. You should also read up RFC2026 on process.

-James Seng

----- Original Message -----
From: "Bill Manning" <bmanning@ISI.EDU>
To: "ben" <ben@cc-www.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
"Edmon" <edmon@neteka.com>; <idn@ops.ietf.org>
Sent: Friday, August 17, 2001 2:23 AM
Subject: Re: [idn] opting out of SC/TC equivalence


> %
> % Hi Eric,
> %
> % > > I could care less about other registries and what they do.
> % >
> % > Then there is no IETF issue for you.
> % >
> %
> % My IETF issue is to get support for my "supreme CDN system" to be
> % implemented as a standard.  Do I have your support?
>
> While I'll leave Eric to answer that question for himself,
> I am left cold by your attitude regarding IETF participation
> and consenses building. Until you are willing to learn from
> others and have responsible dialog, it is my opinion that
> you will not gain support for your flawed ideas.
> But, since you don't care about other registries, interoperability
> is not an issue... ergo, its not an IETF issue, your SCS is a closed,
> propriatary solution.  It will never be a standard.
>
> % > ...
> % > > then I will modify my draft.
> % >
> % > What draft?
> %
> % I said "draft", I did not say "Internet draft".
>
> Again, what draft. Neither Eric or I mentioned "Internet Draft".
> Further evidence that your idea is closed and propriatary. Perhaps.
>
> % Thanks
> % Ben Chan
>
>
> --
> --bill
>




From owner-idn@ops.ietf.org  Thu Aug 16 14:55: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 OAA19802
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 14:55:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XSD9-000F5X-00
	for idn-data@psg.com; Thu, 16 Aug 2001 11:49:43 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XSD8-000F5Q-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 11:49:42 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+3nwGBQ7c9HEfIaYvJSBKmvriOJEiyjsg==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCY2CJ7U; Thu, 16 Aug 2001 14:49:11 EDT
To: edmon@neteka.com
Cc: tsenglm@cc.ncu.edu.tw, ben@cc-www.com, idn@ops.ietf.org
Date: Thu, 16 Aug 2001 12:05:25 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010816.120620.-746899.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

It looks like that I have to do more explaination
on this "force SC/TC" into [nameprep] issue.  Reference
to the last message I have sent for the model:

	[nameprep]			ACE
GB > SC Unicode 
Big5>SC Unicode			ACE encoding > Tagged-ACE
Mixed Unicode > SC Unicode	
Latin Case folding
JIS > SC Unicode
KSC > TC Unicode
ISCII > Indic Unicode

For the display part of this model, the users do have choices
on what they want to see, and recall that [nameprep] is used as
a database, you have both referencing access through IDNA:

received		de-ACE & referred 		output
ACE		[nameprep]

Tagged-ACE	SC Unicode >GB			GB
		SC Unicode > TC Unicode > Big5	Big5	
		SC Unicode > TC Unicode 	select 2 SC only >Mixed Unicode
		SC Unicode > JIS		JIS

fre-casefolded.com 				PutDiacriticMarkBack.com
		TC Unicode > KSC		KSC
		Indic Unicode 			Indic Unicode 

Edmon:
Thank you for the reminder.

Liana


On Thu, 16 Aug 2001 13:26:20 -0400 "Edmon" <edmon@neteka.com> writes:
> Hi Tseng,
> 
> First of all, I am all for a standardized SC=TC.  But I would rather 
> see
> that it is given as an option for registries or zone operators to 
> determine
> because SC and TC characters are characters in their own right.
> 
> The only real argument I see about this is the DNSSEC issue Erik 
> Nordmark
> pointed out, but I can see that there are ways around it but it 
> would mean
> that we would have to slightly adjust DNSSEC which we have agreed is 
> totally
> outside of the scope of this wg.  So if we are forced to make a 
> decision on
> this without the liberty to adjust DNSSEC (which as far as last IETF 
> meeting
> some of it might even never see day of light), then it is a rather
> unfortunate situation.
> 
> Please do not confuse my thinking as to me being against SC=TC, I am
> expressing my concern as a consumer wishing to have a choice.  Also,
> philosophically I believe they are different characters.
> 
> 
> From: "tsenglm@è¨ˆç¶²ä¸­å¿ƒ.ä¸­å¤§.tw" <tsenglm@cc.ncu.edu.tw>
> >             In Twaiwan,  HongKong we use BIG5 code and many 
> simplified
> > scripts can not be key-in and displayed in their system. Many 
> people they
> > know traditional chinese characters but they don't know its 
> corresponding
> > simplified characters.  Reversely, in mainland china people only 
> know
> > simplified characters. The corresponding TC/SC has the same 
> pronunciation
> > and meanning.
> 
> That is the reason why we have unicode in the first place.  Also you 
> have
> pointed out a very good reason why TC and SC are different.  Many 
> people
> know TC and not SC and vice versa, so why and how would someone 
> confuse a TC
> domain with an SC domain?
> 
> > Todday people want to communicate each other, they regist a
> > domain name for some trade mark reasons , but the ML.COM system 
> can not
> > provide the same chance to protect their rights. People in Taiwan 
> regists
> a
> > TC name but he can not key-in to regist the corresponding SC name 
> because
> he
> > even don't know how to do it . Then one day , some people in 
> mainland
> china
> > they regist the corresponding SC name in SC.COM , it is the same 
> meanning
> > and prouncing in TC.COM . What will be happen ?  You know that PRC 
> and
> > Taiwan , even HongKong are different goverenment ,  the argument in
> > intellegent right is a big trouble.
> 
> That is why I champion the SC=TC option for registries.  The problem 
> about
> forcing TC=SC into Nameprep is that we will loose the option at all 
> levels.
> Even if I own <TC>.com I wont be able to distinguish <TC>.<TC>.com 
> from
> <SC>.<TC>.com or worse, if I am now called abc.com I wont be able to 
> have
> distinct sub-zones <TC>.abc.com and <SC>.abc.com.  That is the main 
> problem
> I see and as a group we should contemplate on this matter too, not 
> just the
> second level domains that are sold.
> 
> > The case is very like that you allow
> > one people to regist ABC.com and also allowed another people to 
> regist
> > abc.com and told them  that is an option and chance . Are you like 
> english
> > are treated in this way ? Why case folding is needed ? Only the 
> history
> > reason ? Why full case alphabet must be mapped to ASCII ?
> 
> I disagree to your analysis, TC and SC is rather like
> Color and Colour AE and BE (American English and Bristish English)
> 
> so Color.com is different from Colour.com
> 
> and yes they are registered by two different parties.
> 
> 
> >              Are you like to make trouble to us ?  That is why 
> department
> of
> > China  information industry against chinese.COM so deeply.
> >              I don't care the mixing of TC/SC , but I care why we 
> are
> forced
> > .....
> >
> I dont really get your question here, but again I stress that I 
> think it is
> important to have a standardized TC-SC conversion mechanism, but we 
> should
> also allow individual zone operators to decide whether the TC=SC 
> rule should
> be applied.
> 
> Edmon
> 
> 



From owner-idn@ops.ietf.org  Thu Aug 16 16: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 QAA22491
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 16:42:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XTlH-000I2e-00
	for idn-data@psg.com; Thu, 16 Aug 2001 13:29:03 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XTlG-000I2Y-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 13:29:02 -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, 16 Aug 2001 13:40:12 -0700
Message-ID: <001101c12693$4d7a6740$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "James Seng/Personal" <James@Seng.cc>, "Bill Manning" <bmanning@ISI.EDU>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        "Edmon" <edmon@neteka.com>, <idn@ops.ietf.org>
References: <200108161823.f7GINLU08493@zed.isi.edu> <03ec01c12682$c780de40$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Thu, 16 Aug 2001 16:37: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 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi James / Bill / Eric,

I sincerely apologize for my young cocky attitude.
I will submit my draft as an internet draft and hope very much to have
all your support for my Supreme CDN system.

Thanks
Ben Chan




----- Original Message -----
From: "James Seng/Personal" <James@Seng.cc>
To: "Bill Manning" <bmanning@ISI.EDU>; "ben" <ben@cc-www.com>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
"Edmon" <edmon@neteka.com>; <idn@ops.ietf.org>
Sent: Thursday, August 16, 2001 2:39 PM
Subject: Re: [idn] opting out of SC/TC equivalence


> Once again, wearing my co-chair hat, I need to cut this discussion
on
> "Supreme CDN". There is no Internet Draft, and neither is it in the
core
> interest. Hence, lets not waste working group bandwidth on this
further.
>
> Further discussion on Supreme CDN should be bring offline. Thanks.
>
> Ben, it would also be worthwhile to look at "The Tao of IETF"
> (http://www.ietf.org/tao.html) to get a understanding of how IETF
> function. You should also read up RFC2026 on process.
>
> -James Seng
>
> ----- Original Message -----
> From: "Bill Manning" <bmanning@ISI.EDU>
> To: "ben" <ben@cc-www.com>
> Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
> "Edmon" <edmon@neteka.com>; <idn@ops.ietf.org>
> Sent: Friday, August 17, 2001 2:23 AM
> Subject: Re: [idn] opting out of SC/TC equivalence
>
>
> > %
> > % Hi Eric,
> > %
> > % > > I could care less about other registries and what they do.
> > % >
> > % > Then there is no IETF issue for you.
> > % >
> > %
> > % My IETF issue is to get support for my "supreme CDN system" to
be
> > % implemented as a standard.  Do I have your support?
> >
> > While I'll leave Eric to answer that question for himself,
> > I am left cold by your attitude regarding IETF participation
> > and consenses building. Until you are willing to learn from
> > others and have responsible dialog, it is my opinion that
> > you will not gain support for your flawed ideas.
> > But, since you don't care about other registries, interoperability
> > is not an issue... ergo, its not an IETF issue, your SCS is a
closed,
> > propriatary solution.  It will never be a standard.
> >
> > % > ...
> > % > > then I will modify my draft.
> > % >
> > % > What draft?
> > %
> > % I said "draft", I did not say "Internet draft".
> >
> > Again, what draft. Neither Eric or I mentioned "Internet Draft".
> > Further evidence that your idea is closed and propriatary.
Perhaps.
> >
> > % Thanks
> > % Ben Chan
> >
> >
> > --
> > --bill
> >
>
>




From owner-idn@ops.ietf.org  Thu Aug 16 16:56: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 QAA22690
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 16:56:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XU47-000IbO-00
	for idn-data@psg.com; Thu, 16 Aug 2001 13:48:31 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XU46-000IbI-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 13:48:30 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id CB9F3FFC06; Fri, 17 Aug 2001 04:49:54 +0800 (SGT)
Message-ID: <04b601c12694$c8e2b300$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "ben" <ben@cc-www.com>
Cc: <idn@ops.ietf.org>
References: <200108161823.f7GINLU08493@zed.isi.edu> <03ec01c12682$c780de40$dd00a8c0@jamessonyvaio> <001101c12693$4d7a6740$d43f7018@mtag1.on.home.com>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 17 Aug 2001 04:48:20 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Ben,

Just like to make a clarification: I did not forbid the discussion of
supreme CDN because of your personality or attitude or whatever. It is
because of "Supreme CDN" as it is now is not within the core interest,
at least not yet. Therefore, please respect the working group process
and bring the discussion of supreme CDN offline.

Once you have an Internet Draft and gathered 7 supportors to demostrate
core interest, then we would welcome further discussion.

Aside, I strongly suggest reading RFC2026 on Internet Standard Process.
I recommend Tao of IETF also because it contains a lot of useful
information for newcomer to IETF (even tho you did not attend the
meeting itself).

Thank you.

-James Seng

----- Original Message -----
From: "ben" <ben@cc-www.com>
To: "James Seng/Personal" <James@seng.cc>; "Bill Manning"
<bmanning@ISI.EDU>
Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
"Edmon" <edmon@neteka.com>; <idn@ops.ietf.org>
Sent: Friday, August 17, 2001 4:37 AM
Subject: Re: [idn] opting out of SC/TC equivalence


> Hi James / Bill / Eric,
>
> I sincerely apologize for my young cocky attitude.
> I will submit my draft as an internet draft and hope very much to have
> all your support for my Supreme CDN system.
>
> Thanks
> Ben Chan
>
>
>
>
> ----- Original Message -----
> From: "James Seng/Personal" <James@Seng.cc>
> To: "Bill Manning" <bmanning@ISI.EDU>; "ben" <ben@cc-www.com>
> Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
> "Edmon" <edmon@neteka.com>; <idn@ops.ietf.org>
> Sent: Thursday, August 16, 2001 2:39 PM
> Subject: Re: [idn] opting out of SC/TC equivalence
>
>
> > Once again, wearing my co-chair hat, I need to cut this discussion
> on
> > "Supreme CDN". There is no Internet Draft, and neither is it in the
> core
> > interest. Hence, lets not waste working group bandwidth on this
> further.
> >
> > Further discussion on Supreme CDN should be bring offline. Thanks.
> >
> > Ben, it would also be worthwhile to look at "The Tao of IETF"
> > (http://www.ietf.org/tao.html) to get a understanding of how IETF
> > function. You should also read up RFC2026 on process.
> >
> > -James Seng
> >
> > ----- Original Message -----
> > From: "Bill Manning" <bmanning@ISI.EDU>
> > To: "ben" <ben@cc-www.com>
> > Cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>;
> > "Edmon" <edmon@neteka.com>; <idn@ops.ietf.org>
> > Sent: Friday, August 17, 2001 2:23 AM
> > Subject: Re: [idn] opting out of SC/TC equivalence
> >
> >
> > > %
> > > % Hi Eric,
> > > %
> > > % > > I could care less about other registries and what they do.
> > > % >
> > > % > Then there is no IETF issue for you.
> > > % >
> > > %
> > > % My IETF issue is to get support for my "supreme CDN system" to
> be
> > > % implemented as a standard.  Do I have your support?
> > >
> > > While I'll leave Eric to answer that question for himself,
> > > I am left cold by your attitude regarding IETF participation
> > > and consenses building. Until you are willing to learn from
> > > others and have responsible dialog, it is my opinion that
> > > you will not gain support for your flawed ideas.
> > > But, since you don't care about other registries, interoperability
> > > is not an issue... ergo, its not an IETF issue, your SCS is a
> closed,
> > > propriatary solution.  It will never be a standard.
> > >
> > > % > ...
> > > % > > then I will modify my draft.
> > > % >
> > > % > What draft?
> > > %
> > > % I said "draft", I did not say "Internet draft".
> > >
> > > Again, what draft. Neither Eric or I mentioned "Internet Draft".
> > > Further evidence that your idea is closed and propriatary.
> Perhaps.
> > >
> > > % Thanks
> > > % Ben Chan
> > >
> > >
> > > --
> > > --bill
> > >
> >
> >
>
>




From owner-idn@ops.ietf.org  Thu Aug 16 17:12: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 RAA23027
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 17:12:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XUMz-000J7e-00
	for idn-data@psg.com; Thu, 16 Aug 2001 14:08:01 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XUMv-000J7R-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 14:07:59 -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 f7GL3uO59853;
	Thu, 16 Aug 2001 17:03:56 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200108162103.f7GL3uO59853@nic-naa.net>
To: "ben" <ben@cc-www.com>
cc: "James Seng/Personal" <James@Seng.cc>, "Bill Manning" <bmanning@ISI.EDU>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        "Edmon" <edmon@neteka.com>, idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] opting out of SC/TC equivalence 
In-Reply-To: Your message of "Thu, 16 Aug 2001 16:37:39 EDT."
             <001101c12693$4d7a6740$d43f7018@mtag1.on.home.com> 
Date: Thu, 16 Aug 2001 17:03:56 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Absent mechanism, your policy desires are as binding as those of the State
Legislature which abolished snowfall in that State.



From owner-idn@ops.ietf.org  Thu Aug 16 17:19: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 RAA23113
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 17:19:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XUTe-000JLZ-00
	for idn-data@psg.com; Thu, 16 Aug 2001 14:14:54 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XUTa-000JLM-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 14:14:51 -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 f7GLCMO60062;
	Thu, 16 Aug 2001 17:12:22 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200108162112.f7GLCMO60062@nic-naa.net>
To: idn@ops.ietf.org
cc: brunner@nic-naa.net
Subject: [idn] Question for the Kanji & Hanja cognosentee
Date: Thu, 16 Aug 2001 17:12:22 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk


>                                      ...  this would means languages
> which uses Chinese script (like kanji and Hanja) would also do the
> same (TC/SC) folding.

Does anyone know what this might mean?

SC/TC equivalence in Kanji? In Hanja??

Eric



From owner-idn@ops.ietf.org  Thu Aug 16 17:26: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 RAA23211
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 17:26:21 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XUW8-000JRJ-00
	for idn-data@psg.com; Thu, 16 Aug 2001 14:17:28 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XUW7-000JRD-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 14:17:27 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+3nwGBQ7c9HhhSa1FseVPiQUfw5vq7+bA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCZATLMH; Thu, 16 Aug 2001 17:17:13 EDT
To: david.hopwood@zetnet.co.uk
Cc: liana.ydisg@juno.com, idn@ops.ietf.org
Date: Thu, 16 Aug 2001 14:34:31 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010816.143434.-746899.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,2-28
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, 16 Aug 2001 05:45:33 +0100 David Hopwood
<david.hopwood@zetnet.co.uk> writes:
> 
> I think that that way lies pointless complication and unnecessary 
> delay
> in finalizing the standard, for a feature that is only of minor 
> benefit
> to users. 

Are there any decisions on the architectural and relationship 
between all these drafts?  I thought it is an open question.  
Please enlight me.

In the case of guessing a web site name, if a user can't 
> find
> the name immediately then he/she will just use a search engine, and 
> the
> search engine will work regardless of what script is used. In other 
> cases,
> domain-name-based identifiers such as email addresses and URIs can't
> realistically be guessed, so will come from either:
> 

Are you suggesting an IDN hostname search engine below  
a current DNS search engine?  So for most "mixed script" 
of your definition would have to go through two searches to 
find its hostname?

Liana



From owner-idn@ops.ietf.org  Thu Aug 16 18:13: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 SAA26395
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 18:13:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XVFs-000Kn3-00
	for idn-data@psg.com; Thu, 16 Aug 2001 15:04:44 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.31 #1)
	id 15XVFs-000Kmx-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 15:04:44 -0700
Message-ID: <00a501c1269f$c2db6be0$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: =?UTF-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>,
        <idn@ops.ietf.org>
References: <E15Wq6x-0007EM-00@psg.com> <000901c12549$c6f882a0$d43f7018@mtag1.on.home.com> <001b01c12592$fc156cc0$1001a8c0@neteka.com> <005701c12597$c6855200$d43f7018@mtag1.on.home.com> <004c01c125bb$59d92680$1001a8c0@neteka.com> <004901c125e4$edcd23e0$d43f7018@mtag1.on.home.com> <001301c1265f$d061bf20$1001a8c0@neteka.com> <001001c1266e$bc43c2e0$fb05738c@ncu.edu.tw>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Thu, 16 Aug 2001 18:06:52 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Everyone,

Tseng has convinced me over a couple of emals on the need for an SC=TC
equivalence for some characters.  I now think that some characters might
benefit from an across the border SC=TC equivalence.  However, I still think
that this rule should not be applied for all SC characters.  I will take
some time to work on CNNIC & TWNIC's list in their TSconv draft and see if I
could improve the list a bit.  I would actually like to work with the
authors of the TSconv draft on this too.

In general, I now think that some characters should be mapped as equivalent
(I will give it some more thought) such as:

the chinese characters: U+7D71 = U+7EDF (for those who know Chinese they are
the TC and SC characters for "unite"... loosely translated)

But others which are not really similar should remain individual characters,
such as:

the chinese characters: U+5C08 != U+4E13

Edmon




From owner-idn@ops.ietf.org  Thu Aug 16 19:25: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 TAA27469
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 19:25:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XWJ0-000Muo-00
	for idn-data@psg.com; Thu, 16 Aug 2001 16:12:02 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XWIz-000Mui-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 16:12:01 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1TC7w3T2jVnZZDrwiQ18WUiA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCZHCFKG; Thu, 16 Aug 2001 19:11:16 EDT
To: brunner@nic-naa.net
Cc: idn@ops.ietf.org, brunner@nic-naa.net
Date: Thu, 16 Aug 2001 16:28:37 -0700
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Message-ID: <20010816.162841.-746899.6.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-10,12-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

Kanji is Han character in Japanese, while Hanji is 
Han character in Korean.  During historical transfering
in time or location differences to Japan and Korean, there are
some differences in forms between Hanji/SC and Hanji/SC,
but semanticly equivalent, as it is with TC/SC.  Unicode
combined all TC, SC, Hanji and Kanji into CJK character
table, and that is what we reference the set as CJK character
set.

Liana

On Thu, 16 Aug 2001 17:12:22 -0400 Eric Brunner-Williams in Portland
Maine <brunner@nic-naa.net> writes:
> 
> >                                      ...  this would means 
> languages
> > which uses Chinese script (like kanji and Hanja) would also do the
> > same (TC/SC) folding.
> 
> Does anyone know what this might mean?
> 
> SC/TC equivalence in Kanji? In Hanja??
> 
> Eric
> 



From owner-idn@ops.ietf.org  Thu Aug 16 19:25: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 TAA27480
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 19:25:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XWQh-000N7f-00
	for idn-data@psg.com; Thu, 16 Aug 2001 16:19:59 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XWQh-000N7Y-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 16:19:59 -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 QAA28810
	for <idn@ops.ietf.org>; Thu, 16 Aug 2001 16:19:57 -0700
Message-Id: <5.1.0.14.2.20010816161742.045d8d50@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 16 Aug 2001 16:20:40 -0700
To: idn@ops.ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] opting out of SC/TC equivalence
In-Reply-To: <13749451.997252461@host217-33-136-108.ietf.ignite.net>
References: <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net>
 <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 07:34 PM 8/7/2001, John C Klensin wrote:
>Briefly, either SC and TC are equivalent, or they are not.  If
>they are, we shouldn't be having this discussion.  If they are
>not, we shouldn't be having this discussion either.


The length of this topic thread, and its persistent recurrence, warrants 
making the point even more strongly than John's polite note:

Language equivalence has nothing at all to do with the iDN task of adding 
non-ASCII characters to the DNS.

iDNS concerns a richer set of characters, NOT "language".

Language equivalence is a worthy topic, but not in this forum!

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 Aug 16 19:43: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 TAA27767
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 19:43:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XWiT-000NeG-00
	for idn-data@psg.com; Thu, 16 Aug 2001 16:38:21 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XWiS-000NeA-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 16:38:20 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1TpySjgdli5q+LgaYrxEWx0Q==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCZJVHBS; Thu, 16 Aug 2001 19:38:04 EDT
To: david.hopwood@zetnet.co.uk
Cc: liana.ydisg@juno.com, idn@ops.ietf.org
Date: Thu, 16 Aug 2001 16:55:15 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010816.165517.-746899.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

david.hopwood@zetnet.co.uk wrote:

>So, use of alphabetic case folding does not imply anything about whether
>TC and SC should be folded; that's a separate decision. There's a
>"slippery slope" argument here: if TC/SC are folded, why not Latin <->
>Cyrillic transliteration (used for Serbo-Croatian or in Azerbaijan, for
>example), or any of the other cases where a language can be written in
>more than one script? I see that later in your post you suggest Kanji/SC
>and other foldings.

You have read this correctly.  It is not a "slippery slope" argument,
it is what we can do to finalize IDN without any additional search 
engine complication. Here is a graphic view:

Application  >	IDNA  use [nameprep]  
		do extended case folding >   tag-ACE  > DNS

Liana	



From owner-idn@ops.ietf.org  Thu Aug 16 20:39: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 UAA28165
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 20:39:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XXPO-000OgN-00
	for idn-data@psg.com; Thu, 16 Aug 2001 17:22:42 -0700
Received: from irwell.zetnet.co.uk
	([194.247.47.48] helo=zetnet.co.uk ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XXPN-000Og3-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 17:22:42 -0700
Received: from zetnet.co.uk (man-s115.dialup.zetnet.co.uk [194.247.41.242])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f7H0MW204752;
	Fri, 17 Aug 2001 01:22:32 +0100
Message-ID: <3B7B703D.E3530102@zetnet.co.uk>
Date: Thu, 16 Aug 2001 08:03:25 +0100
From: David Hopwood <david.hopwood@zetnet.co.uk>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en-GB,en,fr-FR,fr,de-DE,de,ru
MIME-Version: 1.0
To: liana.ydisg@juno.com, idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
References: <20010816.082932.-806155.0.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:
> So, the proposal is:
> 
>         [nameprep]                      ACE
> GB > SC Unicode
> Big5>SC Unicode                 ACE encoding
> Mixed Unicode > SC Unicode
> Latin Case folding
> JIS > SC Unicode
> KSC > TC Unicode
> ISCII > Indic Unicode
> 
> There are limited number of standards which is referenced
> by Unicode standard, where we can allow limited number of
> them to make into [nameprep].

Why would we want or need to make any restriction on other charsets that
can be mapped into Unicode? A name is assumed to be expressible as a
sequence of Unicode characters; that's all that is required. nameprep
is a step that is applied to labels *after* expressing them in that way
(so that if a label contains both alphabetic and ideographic or syllabic
characters, for example, case folding will apply to the alphabetic
characters). There is no difference in treatment of labels according to
which charset they may originally have been encoded as.

The only technical requirement needed to make this work is that nameprep
folds at least canonically equivalent strings, so that there are no
artificial differences introduced by transcoding, and so that
NFC-normalizing transcoders can be used (as recommended by the W3C
character model).


In any case, do we have a concensus on the following point: that any
TC/SC folding will not be implemented in nameprep? ('nameprep' here
refers to whatever client-side canonicalization algorithm is applied
automatically to all names.) That is the only thing we need to decide
about TC/SC equivalence as far as the protocol definition is concerned.

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

iQEVAwUBO3twITkCAxeYt5gVAQGCrgf8CbjaVd8ihghg7QZSpeDg5zGBXq+NuJgz
scgLo+1d1L/xyVMqXP6INqashL7nCMYn8NslwGMgzk9N8NAvXvV81KE0qdOuGhMq
BMM2tCexcIFsg35llJGA1m0B7CHtDQYLXW4HxfD19d+KVfE6A7f2TMlAUQobR5zB
A/CcQ7X1aWomXKAqM6hZ+3K9RCOeGTijSqYjM00T3ArfmSxiBRUXPUVxaBjcmLd/
GbE4wydLWEMyItxCOFg/wT7yw4nqar9WVZ9xT0JhLMcIuNt8ImN7j6PCY/Oudd8G
yfBwaJxQGltt10i3Yr+bBff8+Zr6FuCaoV1yJ9KEzYvijbm7Ix2Mgw==
=OXdg
-----END PGP SIGNATURE-----





From owner-idn@ops.ietf.org  Thu Aug 16 21:34: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 VAA28901
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 21:34:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XYIW-000Pzv-00
	for idn-data@psg.com; Thu, 16 Aug 2001 18:19:40 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XYIW-000Pzp-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 18:19:40 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1TUt6Lfe8m+fl5Ho/SarQQmw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCZQNQZE; Thu, 16 Aug 2001 21:19:14 EDT
To: david.hopwood@zetnet.co.uk
Cc: liana.ydisg@juno.com, idn@ops.ietf.org
Date: Thu, 16 Aug 2001 18:36:35 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010816.183637.-746899.8.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-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



On Thu, 16 Aug 2001 08:03:25 +0100 David Hopwood
<david.hopwood@zetnet.co.uk> writes:
> -----BEGIN PGP SIGNED MESSAGE-----
> 
> liana.ydisg@juno.com wrote:
> > So, the proposal is:
> > 
> >         [nameprep]                      ACE
> > GB > SC Unicode
> > Big5>SC Unicode                 ACE encoding
> > Mixed Unicode > SC Unicode
> > Latin Case folding
> > JIS > SC Unicode
> > KSC > TC Unicode
> > ISCII > Indic Unicode
> > 
> > There are limited number of standards which is referenced
> > by Unicode standard, where we can allow limited number of
> > them to make into [nameprep].
> 
> Why would we want or need to make any restriction on other charsets 
> that
> can be mapped into Unicode? A name is assumed to be expressible as a
> sequence of Unicode characters; that's all that is required. 

Because there are large existing user base using particular 
national standard, and the users do not want download 
anything large and they do not want to use.  For example,
the users in China are happy with their GB coded software.
In such a case, it is the server doing the IDN.  Other new
users can use a new IDN, Unicode enabled software directly.

> nameprep
> is a step that is applied to labels *after* expressing them in that 
> way
> (so that if a label contains both alphabetic and ideographic or 
> syllabic
> characters, for example, case folding will apply to the alphabetic
> characters). There is no difference in treatment of labels according 
> to
> which charset they may originally have been encoded as.

So, there will not be any consideration for CJK users as it was
in DNS system?

> 
> The only technical requirement needed to make this work is that 
> nameprep
> folds at least canonically equivalent strings, so that there are no
> artificial differences introduced by transcoding, and so that
> NFC-normalizing transcoders can be used (as recommended by the W3C
> character model).
> 

What is your definition of "artificial differences"?  Could you give me
some specific examples?

Liana

> 
> In any case, do we have a concensus on the following point: that any
> TC/SC folding will not be implemented in nameprep? ('nameprep' here
> refers to whatever client-side canonicalization algorithm is applied
> automatically to all names.) That is the only thing we need to 
> decide
> about TC/SC equivalence as far as the protocol definition is 
> concerned.
> 
> - -- 
> 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
> 
> iQEVAwUBO3twITkCAxeYt5gVAQGCrgf8CbjaVd8ihghg7QZSpeDg5zGBXq+NuJgz
> scgLo+1d1L/xyVMqXP6INqashL7nCMYn8NslwGMgzk9N8NAvXvV81KE0qdOuGhMq
> BMM2tCexcIFsg35llJGA1m0B7CHtDQYLXW4HxfD19d+KVfE6A7f2TMlAUQobR5zB
> A/CcQ7X1aWomXKAqM6hZ+3K9RCOeGTijSqYjM00T3ArfmSxiBRUXPUVxaBjcmLd/
> GbE4wydLWEMyItxCOFg/wT7yw4nqar9WVZ9xT0JhLMcIuNt8ImN7j6PCY/Oudd8G
> yfBwaJxQGltt10i3Yr+bBff8+Zr6FuCaoV1yJ9KEzYvijbm7Ix2Mgw==
> =OXdg
> -----END PGP SIGNATURE-----
> 
> 



From owner-idn@ops.ietf.org  Thu Aug 16 22:24: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 WAA00150
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 22:24:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XZ7a-0001Bc-00
	for idn-data@psg.com; Thu, 16 Aug 2001 19:12:26 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XZ7W-0001B7-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 19:12: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 f7H29YO66742;
	Thu, 16 Aug 2001 22:09:34 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200108170209.f7H29YO66742@nic-naa.net>
To: liana.ydisg@juno.com
cc: brunner@nic-naa.net, idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee 
In-Reply-To: Your message of "Thu, 16 Aug 2001 16:28:37 PDT."
             <20010816.162841.-746899.6.liana.ydisg@juno.com> 
Date: Thu, 16 Aug 2001 22:09:33 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Ms. Ydisg,

Is there a typo right about ...

> Kanji is Han character in Japanese, while Hanji is 
> Han character in Korean.  During historical transfering
> in time or location differences to Japan and Korean, there are
> some differences in forms between Hanji/SC and Hanji/SC,
                                    ^     ^^     ^     ^^
                                    here or here or here or here?

> but semanticly equivalent, as it is with TC/SC.  Unicode
> combined all TC, SC, Hanji and Kanji into CJK character
> table, and that is what we reference the set as CJK character
> set.

OK. I've found what had surprised me, simplified (Japan) Chinese characters.
I'll assume that simplified (Korea) Chinese characters also exist. Ditto for
Vietnamese.

The Chinese I learned as a kid (TC) and the Chinese I learned in Beijing (SC),
clearly isn't all the TC or SC available to choose from, so now I have a better
understanding of the original comment.

Thanks for your assistance,
Eric



From owner-idn@ops.ietf.org  Thu Aug 16 22:42: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 WAA01366
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 22:41:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XZRK-0001ev-00
	for idn-data@psg.com; Thu, 16 Aug 2001 19:32:50 -0700
Received: from mail.fm-net.ne.jp ([211.15.66.133])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XZRJ-0001eo-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 19:32:49 -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 LAA15398
	for <idn@ops.ietf.org>; Fri, 17 Aug 2001 11:32:47 +0900
Message-ID: <0e4501c126c4$c2ca5510$a3420fd3@bruce>
From: "Bruce Thomson" <bthomson@fm-net.ne.jp>
To: <idn@ops.ietf.org>
References: <200108162112.f7GLCMO60062@nic-naa.net>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Date: Fri, 17 Aug 2001 11:31:46 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

SC are not used in Kanji, and the folding is not particularly
useful for Japan. In practice it would mean that registering
a Kanji (TC) name in Japan would block the SC equivalent
from being registered in China, and vice versa. From the
Japanese perspective, excepting big multinational corporations,
this is counterproductive, as it just reduces the number
of names available.

----- Original Message ----- 
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: <idn@ops.ietf.org>
Cc: <brunner@nic-naa.net>
Sent: Friday, August 17, 2001 6:12 AM
Subject: [idn] Question for the Kanji & Hanja cognosentee


> 
> >                                      ...  this would means languages
> > which uses Chinese script (like kanji and Hanja) would also do the
> > same (TC/SC) folding.
> 
> Does anyone know what this might mean?
> 
> SC/TC equivalence in Kanji? In Hanja??
> 
> Eric
> 
> 




From owner-idn@ops.ietf.org  Thu Aug 16 23:08: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 XAA01630
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 23:08:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XZoR-0002EI-00
	for idn-data@psg.com; Thu, 16 Aug 2001 19:56: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.31 #1)
	id 15XZoN-0002EC-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 19:56:41 -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 f7H2rgO67793;
	Thu, 16 Aug 2001 22:53:42 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200108170253.f7H2rgO67793@nic-naa.net>
To: Dave Crocker <dhc@dcrocker.net>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] opting out of SC/TC equivalence 
In-Reply-To: Your message of "Thu, 16 Aug 2001 16:20:40 PDT."
             <5.1.0.14.2.20010816161742.045d8d50@dcrocker.net> 
Date: Thu, 16 Aug 2001 22:53:42 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dave,

My take on at least a part of this interminible thread is scope, [30],
not language. Some of the local scope proponents are flogging product,
others appear to be concerned with local, even private differentiation.
We may also be doing a Hamming-distance dance around trademarks, which
may account for some of the heat without light.

I find it perplexing. In the case of roman scripts used for Algonquin
languages, either in their diacritical rich or simplified forms, we use
latin or extended latin differently from Europeans and Euro-Americans.
Different languages and scripts, same character repitoires, with some few
exceptions (e.g., Eastern Algonquin "8" U+0222 and U+0223).

In this case, local scope [30] seems sensible. Ditto for Siouian, Athabascan,
...
In the SC/TC context, local scope [30] seems senseless.

If you and/or John could just sort out the issue of scope, we could all
leave the question of scoped rules to those who actually have clue.

Eric



From owner-idn@ops.ietf.org  Thu Aug 16 23: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 XAA01902
	for <idn-archive@lists.ietf.org>; Thu, 16 Aug 2001 23:30:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xa6Q-0002go-00
	for idn-data@psg.com; Thu, 16 Aug 2001 20:15:18 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xa5y-0002fv-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 20:14:50 -0700
Received: from test.ncu.edu.tw ([140.115.5.251])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f7H3Js709441;
	Fri, 17 Aug 2001 11:19:54 +0800 (CST)
Message-ID: <00a301c126ca$bf64fb40$fb05738c@ncu.edu.tw>
From: =?UTF-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: <idn@ops.ietf.org>, "Dave Crocker" <dhc@dcrocker.net>
References: <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net> <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net> <5.1.0.14.2.20010816161742.045d8d50@dcrocker.net>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 17 Aug 2001 11:14:37 +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.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 !  Friends in this WG:
     We have different culture and experiences and we should respect each
other !  I think John is concerned his duty and time limitation. I found
people in this WG they talk about foreign scripts or language characters as
it is their own mother language , and they care something so they worry some
case will happen and they applied some  partial case to full situations,
that is a basic wrong .
      In TC/SC  characters, there are small set of equivalent characters
that are exactly the same situation as  english case folding but if it is
neglected that will be more worse than other scripts, because there are many
sources of  confusing troubles. Another set of equivalent word (content
sensitive equivalent characters) are not the case of case folding. But
someone try to cut or mixed them together to one simple class , then the
hurt will happen.
      If your statements are meant John is the God father , so no one can
pass over the line he defined , I will ask what is the goal of this WG ?
Does it is used to hurt other people in this world ?
      IDN is very complex ,  but if  you try to neglect some truth then the
political issue will be introduced , then no one will be happy .

L.M.Tseng

----- Original Message -----
From: "Dave Crocker" <dhc@dcrocker.net>
To: <idn@ops.ietf.org>
Sent: Friday, August 17, 2001 7:20 AM
Subject: Re: [idn] opting out of SC/TC equivalence


> At 07:34 PM 8/7/2001, John C Klensin wrote:
> >Briefly, either SC and TC are equivalent, or they are not.  If
> >they are, we shouldn't be having this discussion.  If they are
> >not, we shouldn't be having this discussion either.
>
>
> The length of this topic thread, and its persistent recurrence, warrants
> making the point even more strongly than John's polite note:
>
> Language equivalence has nothing at all to do with the iDN task of adding
> non-ASCII characters to the DNS.
>
> iDNS concerns a richer set of characters, NOT "language".
>
> Language equivalence is a worthy topic, but not in this forum!
>
> 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 Aug 17 00: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 AAA02732
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 00:13:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XapW-0003n0-00
	for idn-data@psg.com; Thu, 16 Aug 2001 21:01:54 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XapV-0003mu-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 21:01:54 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1Tn1FRtxX/xzcJNL7S9WlicA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCZZXPME; Fri, 17 Aug 2001 00:01:24 EDT
To: bthomson@fm-net.ne.jp
Cc: idn@ops.ietf.org
Date: Thu, 16 Aug 2001 21:18:31 -0700
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Message-ID: <20010816.211834.-746899.9.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-44
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

That is a good news.  I hope to hear more comments
and more frequent from any non-English languages 
users.

By the way, how do you Romanize a word containing
Kanji and Kana?

Liana Ye


On Fri, 17 Aug 2001 11:31:46 +0900 "Bruce Thomson"
<bthomson@fm-net.ne.jp> writes:
> SC are not used in Kanji, and the folding is not particularly
> useful for Japan. In practice it would mean that registering
> a Kanji (TC) name in Japan would block the SC equivalent
> from being registered in China, and vice versa. From the
> Japanese perspective, excepting big multinational corporations,
> this is counterproductive, as it just reduces the number
> of names available.
> 
> ----- Original Message ----- 
> From: "Eric Brunner-Williams in Portland Maine" 
> <brunner@nic-naa.net>
> To: <idn@ops.ietf.org>
> Cc: <brunner@nic-naa.net>
> Sent: Friday, August 17, 2001 6:12 AM
> Subject: [idn] Question for the Kanji & Hanja cognosentee
> 
> 
> > 
> > >                                      ...  this would means 
> languages
> > > which uses Chinese script (like kanji and Hanja) would also do 
> the
> > > same (TC/SC) folding.
> > 
> > Does anyone know what this might mean?
> > 
> > SC/TC equivalence in Kanji? In Hanja??
> > 
> > Eric
> > 
> > 
> 
> 



From owner-idn@ops.ietf.org  Fri Aug 17 00:54: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 AAA03157
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 00:54:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XbOq-0004lz-00
	for idn-data@psg.com; Thu, 16 Aug 2001 21:38:24 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XbOp-0004lr-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 21:38: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 NAA25122;
	Fri, 17 Aug 2001 13:37:58 +0900
Message-ID: <052501c126d5$9cf3d6c0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Bruce Thomson" <bthomson@fm-net.ne.jp>, <idn@ops.ietf.org>
References: <200108162112.f7GLCMO60062@nic-naa.net> <0e4501c126c4$c2ca5510$a3420fd3@bruce>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Date: Fri, 17 Aug 2001 13:32:23 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 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

SC is also not used in Hanja ( Korean Han character sets, 4888  chars defined  in KSC5601).

Many  Korean(Hangeul) words have 1 or more TC representations.
The capital of Japan, "Tokyo" has both of its HIRAGANA & Kanji representation which are
used interchangeably very often. Japanese folks may pronounce Kanji "Tokyo" as the same
as Hiragana "Tokyo"over the phone line to interchange their IDN email addresses.
The same pronunciation and meaning, but with different words!!!
That's also true for Hangeul words and its TC equivalents.

These are related to trademark(out of IDN scope)/security (in  IDN scope)  problems.

Soobok Lee

----- Original Message ----- 
From: "Bruce Thomson" <bthomson@fm-net.ne.jp>
To: <idn@ops.ietf.org>
Sent: Friday, August 17, 2001 11:31 AM
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee


> SC are not used in Kanji, and the folding is not particularly
> useful for Japan. In practice it would mean that registering
> a Kanji (TC) name in Japan would block the SC equivalent
> from being registered in China, and vice versa. From the
> Japanese perspective, excepting big multinational corporations,
> this is counterproductive, as it just reduces the number
> of names available.
> 
> ----- Original Message ----- 
> From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
> To: <idn@ops.ietf.org>
> Cc: <brunner@nic-naa.net>
> Sent: Friday, August 17, 2001 6:12 AM
> Subject: [idn] Question for the Kanji & Hanja cognosentee
> 
> 
> > 
> > >                                      ...  this would means languages
> > > which uses Chinese script (like kanji and Hanja) would also do the
> > > same (TC/SC) folding.
> > 
> > Does anyone know what this might mean?
> > 
> > SC/TC equivalence in Kanji? In Hanja??
> > 
> > Eric
> > 
> > 
> 
> 




From owner-idn@ops.ietf.org  Fri Aug 17 01: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 BAA03258
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 01:02:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xbae-00057D-00
	for idn-data@psg.com; Thu, 16 Aug 2001 21:50:36 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xbac-000576-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 21: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 NAA28999;
	Fri, 17 Aug 2001 13:50:18 +0900
Message-ID: <053d01c126d7$559aff90$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>, "Bruce Thomson" <bthomson@fm-net.ne.jp>,
        <idn@ops.ietf.org>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Date: Fri, 17 Aug 2001 13:44:42 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I forgot to put the following comment:

  In Korea, unlike Japan, 
    verbal & written communication  hardly use TC-form korean words.
   Korean people use the TC-forms of their company names or personal names
   only when they communicate to Japanese or chinese partners.

 
----- Original Message ----- 
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Bruce Thomson" <bthomson@fm-net.ne.jp>; <idn@ops.ietf.org>
Sent: Friday, August 17, 2001 1:32 PM
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee


> SC is also not used in Hanja ( Korean Han character sets, 4888  chars defined  in KSC5601).
> 
> Many  Korean(Hangeul) words have 1 or more TC representations.
> The capital of Japan, "Tokyo" has both of its HIRAGANA & Kanji representation which are
> used interchangeably very often. Japanese folks may pronounce Kanji "Tokyo" as the same
> as Hiragana "Tokyo"over the phone line to interchange their IDN email addresses.
> The same pronunciation and meaning, but with different words!!!
> That's also true for Hangeul words and its TC equivalents.
> 
> These are related to trademark(out of IDN scope)/security (in  IDN scope)  problems.
> 
> Soobok Lee
> 
> ----- Original Message ----- 
> From: "Bruce Thomson" <bthomson@fm-net.ne.jp>
> To: <idn@ops.ietf.org>
> Sent: Friday, August 17, 2001 11:31 AM
> Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
> 
> 
> > SC are not used in Kanji, and the folding is not particularly
> > useful for Japan. In practice it would mean that registering
> > a Kanji (TC) name in Japan would block the SC equivalent
> > from being registered in China, and vice versa. From the
> > Japanese perspective, excepting big multinational corporations,
> > this is counterproductive, as it just reduces the number
> > of names available.
> > 
> > ----- Original Message ----- 
> > From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
> > To: <idn@ops.ietf.org>
> > Cc: <brunner@nic-naa.net>
> > Sent: Friday, August 17, 2001 6:12 AM
> > Subject: [idn] Question for the Kanji & Hanja cognosentee
> > 
> > 
> > > 
> > > >                                      ...  this would means languages
> > > > which uses Chinese script (like kanji and Hanja) would also do the
> > > > same (TC/SC) folding.
> > > 
> > > Does anyone know what this might mean?
> > > 
> > > SC/TC equivalence in Kanji? In Hanja??
> > > 
> > > Eric
> > > 
> > > 
> > 
> > 
> 




From owner-idn@ops.ietf.org  Fri Aug 17 01:08: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 BAA03725
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 01:08:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XblA-0005RZ-00
	for idn-data@psg.com; Thu, 16 Aug 2001 22:01:28 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xbl9-0005RP-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 22:01:27 -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 WAA06761
	for <idn@ops.ietf.org>; Thu, 16 Aug 2001 22:01:25 -0700
Message-Id: <5.1.0.14.2.20010816215936.033ef010@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 16 Aug 2001 22:02:11 -0700
To: <idn@ops.ietf.org>
From: Dave Crocker <dhc@dcrocker.net>
Subject: [idn] iDN Choices presentation
In-Reply-To: <00a301c126ca$bf64fb40$fb05738c@ncu.edu.tw>
References: <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net>
 <000101c11fec$7520a0a0$5b8d21d9@ietf.ignite.net>
 <5.1.0.14.2.20010816161742.045d8d50@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk



I've posted a copy of the slides used for my "iDN Choices" presentation at 
the London IETF, last week.

This version has minor corrections from the version used at the working 
group meeting, and I have added some commentary text that approximates the 
comments I made during the presentation.

The powerpoint file is at:

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

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 Aug 17 01:12: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 BAA04329
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 01:11:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xbpc-0005ac-00
	for idn-data@psg.com; Thu, 16 Aug 2001 22:06:04 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xbpb-0005aV-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 22:06:03 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1Tetvfm01bc5vew/OKfQZkog==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCZ5KSE2; Fri, 17 Aug 2001 01:04:48 EDT
To: tsenglm@cc.ncu.edu.tw
Cc: idn@ops.ietf.org, dhc@dcrocker.net
Date: Thu, 16 Aug 2001 22:17:12 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010816.222200.-746899.10.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,12-23
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 agree with Prof. Tseng's point.  And I suggest that
we shall collect inputs from each language users/engineers
 and ask them what do they think about their scripts should
be handled.  What are the non-semantic issues that 
could be dealed with [nameprep] type of simple scheme and 
benifit long term communication and identification of
a hostname on the internet. 

Liana

On Fri, 17 Aug 2001 11:14:37 +0800
=?UTF-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?=
<tsenglm@cc.ncu.edu.tw> writes:
       If your statements are meant John is the God father , so no 
> one can
> pass over the line he defined , I will ask what is the goal of this 
> WG ?
> Does it is used to hurt other people in this world ?
>       IDN is very complex ,  but if  you try to neglect some truth 
> then the
> political issue will be introduced , then no one will be happy .
> 
> L.M.Tseng
> 



From owner-idn@ops.ietf.org  Fri Aug 17 01:12: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 BAA04366
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 01:12:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xbp1-0005Zx-00
	for idn-data@psg.com; Thu, 16 Aug 2001 22:05:27 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xbp0-0005Zp-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 22:05:26 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1TytO76XAdDhiZPKJTzjZVCw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCZ5KSG7; Fri, 17 Aug 2001 01:04:48 EDT
To: brunner@nic-naa.net
Cc: liana.ydisg@juno.com, brunner@nic-naa.net, idn@ops.ietf.org
Date: Thu, 16 Aug 2001 22:21:52 -0700
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Message-ID: <20010816.222200.-746899.11.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-37
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, 16 Aug 2001 22:09:33 -0400 Eric Brunner-Williams in Portland
Maine <brunner@nic-naa.net> writes:
> Ms. Ydisg,
> 
> Is there a typo right about ...
> 
> > Kanji is Han character in Japanese, while Hanji is 
> > Han character in Korean.  During historical transfering
> > in time or location differences to Japan and Korean, there are
> > some differences in forms between Hanji/SC and Hanji/SC,
>                                     ^     ^^     ^     ^^
>                                     here or here or here or here?
> 
> > but semanticly equivalent, as it is with TC/SC.  Unicode
> > combined all TC, SC, Hanji and Kanji into CJK character
> > table, and that is what we reference the set as CJK character
> > set.
> 
> OK. I've found what had surprised me, simplified (Japan) Chinese 
> characters.
> I'll assume that simplified (Korea) Chinese characters also exist. 
> Ditto for
> Vietnamese.
> 
> The Chinese I learned as a kid (TC) and the Chinese I learned in 
> Beijing (SC),
> clearly isn't all the TC or SC available to choose from, so now I 
> have a better
> understanding of the original comment.
> 
> Thanks for your assistance,
> Eric

Which "original comment" do you refer to?  I forget what I have 
said.

Liana Ye



From owner-idn@ops.ietf.org  Fri Aug 17 02:02: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 CAA14020
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 02:02:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XcUh-0006kK-00
	for idn-data@psg.com; Thu, 16 Aug 2001 22:48:31 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XcUg-0006kE-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 22:48:30 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1TslID/R/mfIveOVqDqT+DXA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GCZ7Z7RM; Fri, 17 Aug 2001 01:47:38 EDT
To: lsb@postel.co.kr
Cc: bthomson@fm-net.ne.jp, idn@ops.ietf.org
Date: Thu, 16 Aug 2001 23:04:55 -0700
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Message-ID: <20010816.230501.-746899.12.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-68
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

What happen when people read newspapers with Hangul 
without Hanji such as it is in North Korean?  
How to you get a Hanji through hangul if it is one-to-many 
correspondence?

Liana

On Fri, 17 Aug 2001 13:32:23 +0900 "Soobok Lee" <lsb@postel.co.kr>
writes:
> SC is also not used in Hanja ( Korean Han character sets, 4888  chars 
> defined  in KSC5601).
> 
> Many  Korean(Hangeul) words have 1 or more TC representations.
> The capital of Japan, "Tokyo" has both of its HIRAGANA & Kanji 
> representation which are
> used interchangeably very often. Japanese folks may pronounce Kanji 
> "Tokyo" as the same
> as Hiragana "Tokyo"over the phone line to interchange their IDN 
> email addresses.
> The same pronunciation and meaning, but with different words!!!
> That's also true for Hangeul words and its TC equivalents.
> 
> These are related to trademark(out of IDN scope)/security (in  IDN 
> scope)  problems.
> 
> Soobok Lee
> 
> ----- Original Message ----- 
> From: "Bruce Thomson" <bthomson@fm-net.ne.jp>
> To: <idn@ops.ietf.org>
> Sent: Friday, August 17, 2001 11:31 AM
> Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
> 
> 
> > SC are not used in Kanji, and the folding is not particularly
> > useful for Japan. In practice it would mean that registering
> > a Kanji (TC) name in Japan would block the SC equivalent
> > from being registered in China, and vice versa. From the
> > Japanese perspective, excepting big multinational corporations,
> > this is counterproductive, as it just reduces the number
> > of names available.
> > 
> > ----- Original Message ----- 
> > From: "Eric Brunner-Williams in Portland Maine" 
> <brunner@nic-naa.net>
> > To: <idn@ops.ietf.org>
> > Cc: <brunner@nic-naa.net>
> > Sent: Friday, August 17, 2001 6:12 AM
> > Subject: [idn] Question for the Kanji & Hanja cognosentee
> > 
> > 
> > > 
> > > >                                      ...  this would means 
> languages
> > > > which uses Chinese script (like kanji and Hanja) would also do 
> the
> > > > same (TC/SC) folding.
> > > 
> > > Does anyone know what this might mean?
> > > 
> > > SC/TC equivalence in Kanji? In Hanja??
> > > 
> > > Eric
> > > 
> > > 
> > 
> > 
> 
> 



From owner-idn@ops.ietf.org  Fri Aug 17 02:10: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 CAA20069
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 02:10:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xcd7-0006yS-00
	for idn-data@psg.com; Thu, 16 Aug 2001 22:57:13 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xcd6-0006y7-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 22:57:12 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 73764FFC0E; Fri, 17 Aug 2001 13:58:28 +0800 (SGT)
Message-ID: <053d01c126e1$6d432aa0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: <tsenglm@cc.ncu.edu.tw>, <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>, <dhc@dcrocker.net>
References: <20010816.222200.-746899.10.liana.ydisg@juno.com>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 17 Aug 2001 13:56:56 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

As much as I agree with Prof Tseng well-intention, unfortunately, the
concept of "language" is out of scope for the working group.

This working is chartered to do "Internationalized access to Domain
Names". Unfortunately, domain names understand only "script" not
"language". It does not matter what you wish, it can't be done in Domain
Names (It can be done in some other mechanism of course).

And we are doing "Internationalization" not "Multilingualism". These may
just be terminology but the subtle differences in these terms makes a
lot of differences. I learn it the hard way for those who is with the WG
from the beginning.

Thus, I would modify your statement below to: "from each SCRIPT
users/engineers and ask them how they want their scripts to be use".
(ie. all han ideograph (CJK) users should talk about han folding
together if we going down the path of tsconv).

-James Seng

----- Original Message -----
From: <liana.ydisg@juno.com>
To: <tsenglm@cc.ncu.edu.tw>
Cc: <idn@ops.ietf.org>; <dhc@dcrocker.net>
Sent: Friday, August 17, 2001 1:17 PM
Subject: Re: [idn] opting out of SC/TC equivalence


> I agree with Prof. Tseng's point.  And I suggest that
> we shall collect inputs from each language users/engineers
>  and ask them what do they think about their scripts should
> be handled.  What are the non-semantic issues that
> could be dealed with [nameprep] type of simple scheme and
> benifit long term communication and identification of
> a hostname on the internet.
>
> Liana
>
> On Fri, 17 Aug 2001 11:14:37 +0800
> =?UTF-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?=
> <tsenglm@cc.ncu.edu.tw> writes:
>        If your statements are meant John is the God father , so no
> > one can
> > pass over the line he defined , I will ask what is the goal of this
> > WG ?
> > Does it is used to hurt other people in this world ?
> >       IDN is very complex ,  but if  you try to neglect some truth
> > then the
> > political issue will be introduced , then no one will be happy .
> >
> > L.M.Tseng
> >
>




From owner-idn@ops.ietf.org  Fri Aug 17 02:13: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 CAA20116
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 02:13:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xcks-0007Al-00
	for idn-data@psg.com; Thu, 16 Aug 2001 23:05:14 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xckr-0007AZ-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 23:05:13 -0700
Received: from soobok ([210.217.27.237] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id PAA19862;
	Fri, 17 Aug 2001 15:04:54 +0900
Message-ID: <012c01c126e2$b1784c40$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <liana.ydisg@juno.com>
Cc: <bthomson@fm-net.ne.jp>, <idn@ops.ietf.org>
References: <20010816.230501.-746899.12.liana.ydisg@juno.com>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Date: Fri, 17 Aug 2001 15:06:01 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi, Liana

----- Original Message ----- 
From: <liana.ydisg@juno.com>
> What happen when people read newspapers with Hangul 
> without Hanji such as it is in North Korean?  
> How to you get a Hanji through hangul if it is one-to-many 
> correspondence?
> 
Korean have been familiar with many hangeul homonyms that
share the same hangeul word but have different TC forms/meanings
and optionally different sounds (long or short vowel etc) .
Ordinary Korean can disambiguate them  only by the surrounding
semantical context (sentence or paragraph) in which they appear.

In DNS, we have no such contextual clue for disambiguations.

Soobok

> Liana
> 
 




From owner-idn@ops.ietf.org  Fri Aug 17 02: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 CAA20133
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 02:15:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XckV-0007A6-00
	for idn-data@psg.com; Thu, 16 Aug 2001 23:04:51 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XckT-0007A0-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 23:04:50 -0700
Received: from test.ncu.edu.tw ([140.115.5.251])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f7H69c703399;
	Fri, 17 Aug 2001 14:09:38 +0800 (CST)
Message-ID: <001701c126e2$752e0860$fb05738c@ncu.edu.tw>
From: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: "Bruce Thomson" <bthomson@fm-net.ne.jp>, <idn@ops.ietf.org>
References: <200108162112.f7GLCMO60062@nic-naa.net> <0e4501c126c4$c2ca5510$a3420fd3@bruce>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Date: Fri, 17 Aug 2001 14: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.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit


----- Original Message -----
From: "Bruce Thomson" <bthomson@fm-net.ne.jp>
To: <idn@ops.ietf.org>
Sent: Friday, August 17, 2001 10:31 AM
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee


> SC are not used in Kanji, and the folding is not particularly

     This is not always true , for example: nation,  TC(åœ‹) is not used in
Japan, China and Japan use SC(å›½).  Japan use a small set of CJK character
that are japan simplified traditional Kanji . Many of these are used in
Taiwan and China , these are not just the PRC simplified characters. I think
no Japanese will be happy  if æ—¥æœ¬åœ‹ will be confused with  æ—¥æœ¬å›½ .
     In the registed record of ML.mltbd.com ,  there are many mixed Kanji
and kana records,  if it can be treated and identified as a full recored of
mixing Kanji and Kana , then it is not need to do equivalence operation.
     I suggest draft of  tsconv should print/list  all the scripts form, and
people in CJK area  can review it quickly to reduce that table to fit of
nameprep  needing .
     Not all equivalent SC/TC should be put into nameprep of  client ,
there are just a small set of  PRC quick-written characters , for ex.
TC(çµ±) SC(ç»Ÿ) ,  TC(é ») SC(é¢‘) ...
     If you print them out in font form, you will find them just like  "fi"
in confusing  status.
     Today, CJK area use SJIS , unc-kr, GB, big5  so they can not meet in
each other , but if UNICODE table are build-in in your furture system ,
then your Kanji.com  trade mark name will be confused by an un-aware people
.
     I think the case is the same in Korean Hanja name(especially in
people's name) .
     No one want to hurt other people by the standardrization in IDN,  so
we need to check the final results and not to neglect them.

L.M.Tseng
> useful for Japan. In practice it would mean that registering
> a Kanji (TC) name in Japan would block the SC equivalent
> from being registered in China, and vice versa. From the
> Japanese perspective, excepting big multinational corporations,
> this is counterproductive, as it just reduces the number
> of names available.
>
> ----- Original Message -----
> From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
> To: <idn@ops.ietf.org>
> Cc: <brunner@nic-naa.net>
> Sent: Friday, August 17, 2001 6:12 AM
> Subject: [idn] Question for the Kanji & Hanja cognosentee
>
>
> >
> > >                                      ...  this would means languages
> > > which uses Chinese script (like kanji and Hanja) would also do the
> > > same (TC/SC) folding.
> >
> > Does anyone know what this might mean?
> >
> > SC/TC equivalence in Kanji? In Hanja??
> >
> > Eric
> >
> >
>
>
>




From owner-idn@ops.ietf.org  Fri Aug 17 02:25: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 CAA20230
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 02:25:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XcwJ-0007WN-00
	for idn-data@psg.com; Thu, 16 Aug 2001 23:17:03 -0700
Received: from mail.fm-net.ne.jp ([211.15.66.133])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XcwI-0007WH-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 23:17:02 -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 PAA16487
	for <idn@ops.ietf.org>; Fri, 17 Aug 2001 15:17:01 +0900
Message-ID: <0ea701c126e4$14dfe120$a3420fd3@bruce>
From: "Bruce Thomson" <bthomson@fm-net.ne.jp>
To: <idn@ops.ietf.org>
References: <20010816.211834.-746899.9.liana.ydisg@juno.com>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Date: Fri, 17 Aug 2001 15:15:58 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> By the way, how do you Romanize a word containing
> Kanji and Kana?
> 

There are two steps:

1) Convert all Kanji to kana. Anything that can be pronounced
in Japanese can be expressed as the kana equivalent of that
pronunciation. However, Kanji cannot be converted one at a time
as many words are unique combinations of Kanji with special
pronuncations. Also, there can be multiple pronunciations for the
same Kanji string.

2) Once you have everything in kana, convert to "Romaji"
(Romanized characters) using the Hepburn system. Here
are the Romaji equivalents of all the modern kana:

a  i  u  e  o
ka ki ku ke ko
sa shi su se so
ta chi tsu te to
na ni nu ne no
ha hi fu he ho
ma mi mu me mo
ya yu yo
ra ri ru re ro
wa wo
n

There is a further complication in that a small kana
tsu is used to represent a double consonant when
a word is written as kana, whereas the consonant
is merely written twice in the Romaji equivalent.

By the way, Japanese keyboard input is usually
handled by typing Romaji which can then be
converted to kana and further converted into
Kanji.

http://www.omniglot.com/writing/japanese.htm
http://www.kanjisite.com/wak1.html





From owner-idn@ops.ietf.org  Fri Aug 17 02:33: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 CAA20346
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 02:33:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xczi-0007dT-00
	for idn-data@psg.com; Thu, 16 Aug 2001 23:20:34 -0700
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xczh-0007dM-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 23:20:33 -0700
Received: from xiaodonglee ([159.226.7.70]) by
          whale.cnnic.net.cn (Netscape Messaging Server 4.15) with SMTP id
          GI78CY00.SE1; Fri, 17 Aug 2001 14:22:10 +0800 
Message-ID: <001b01c126e4$2b745dd0$4607e29f@xiaodonglee>
Reply-To: "Xiaodong LEE" <Xiaodong.Lee@cnnic.net.cn>
From: "xiaodong lee" <lee@whale.cnnic.net.cn>
To: "James Seng/Personal" <James@Seng.cc>, <tsenglm@cc.ncu.edu.tw>,
        <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>, <dhc@dcrocker.net>
References: <20010816.222200.-746899.10.liana.ydisg@juno.com> <053d01c126e1$6d432aa0$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 17 Aug 2001 14:16:36 +0800
Organization: CNIC-ICT
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
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 CAA20346

James, some opinion of mine
----- Original Message ----- 
From: "James Seng/Personal" <James@Seng.cc>
To: <tsenglm@cc.ncu.edu.tw>; <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>; <dhc@dcrocker.net>
Sent: Friday, August 17, 2001 1:56 PM
Subject: Re: [idn] opting out of SC/TC equivalence


> As much as I agree with Prof Tseng well-intention, unfortunately, the
> concept of "language" is out of scope for the working group.
> 
> This working is chartered to do "Internationalized access to Domain
> Names". Unfortunately, domain names understand only "script" not
> "language". It does not matter what you wish, it can't be done in Domain
> Names (It can be done in some other mechanism of course).
> 

you said it. Maybe we could not handle language problems in IDN, but we could 
not forget that all script have language characteristics of themselves, especially for 
Chinese. Internationalization means all users could use their familiar  ways to use
domain name, not means all users must follow one ways.

> And we are doing "Internationalization" not "Multilingualism". These may
> just be terminology but the subtle differences in these terms makes a
> lot of differences. I learn it the hard way for those who is with the WG
> from the beginning.
> 

Exactly, we are doing internationalization, but how do we explain for users what is 
internationalization, and what is multilingualism, I think ordinary users care about 
how to use , not what is.

> Thus, I would modify your statement below to: "from each SCRIPT
> users/engineers and ask them how they want their scripts to be use".
> (ie. all han ideograph (CJK) users should talk about han folding
> together if we going down the path of tsconv).
> 

Prof. Tseng care more about users requirements, I think, a technology developed without
enough users requirements, it makes no sense.


> -James Seng
> 
> ----- Original Message -----
> From: <liana.ydisg@juno.com>
> To: <tsenglm@cc.ncu.edu.tw>
> Cc: <idn@ops.ietf.org>; <dhc@dcrocker.net>
> Sent: Friday, August 17, 2001 1:17 PM
> Subject: Re: [idn] opting out of SC/TC equivalence
> 
> 
> > I agree with Prof. Tseng's point.  And I suggest that
> > we shall collect inputs from each language users/engineers
> >  and ask them what do they think about their scripts should
> > be handled.  What are the non-semantic issues that
> > could be dealed with [nameprep] type of simple scheme and
> > benifit long term communication and identification of
> > a hostname on the internet.
> >
> > Liana
> >
> > On Fri, 17 Aug 2001 11:14:37 +0800
> > =?UTF-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?=
> > <tsenglm@cc.ncu.edu.tw> writes:
> >        If your statements are meant John is the God father , so no
> > > one can
> > > pass over the line he defined , I will ask what is the goal of this
> > > WG ?
> > > Does it is used to hurt other people in this world ?
> > >       IDN is very complex ,  but if  you try to neglect some truth
> > > then the
> > > political issue will be introduced , then no one will be happy .
> > >
> > > L.M.Tseng
> > >
> >
> 
> 


From owner-idn@ops.ietf.org  Fri Aug 17 02:35: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 CAA20365
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 02:35:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xd73-0007rU-00
	for idn-data@psg.com; Thu, 16 Aug 2001 23:28:09 -0700
Received: from mail.fm-net.ne.jp ([211.15.66.133])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xd72-0007rO-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 23:28:08 -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 PAA16536
	for <idn@ops.ietf.org>; Fri, 17 Aug 2001 15:28:07 +0900
Message-ID: <0eb701c126e5$a1d8a2a0$a3420fd3@bruce>
From: "Bruce Thomson" <bthomson@fm-net.ne.jp>
To: <idn@ops.ietf.org>
References: <200108162112.f7GLCMO60062@nic-naa.net> <0e4501c126c4$c2ca5510$a3420fd3@bruce> <001701c126e2$752e0860$fb05738c@ncu.edu.tw>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Date: Fri, 17 Aug 2001 15:27:04 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 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


----- Original Message -----
From: "tsenglm@è¨ˆç¶²ä¸­å¿ƒ.ä¸­å¤§.tw" <tsenglm@cc.ncu.edu.tw>

>
> > SC are not used in Kanji, and the folding is not particularly
>
>      This is not always true , for example: nation,  TC(åœ‹) is not used in
> Japan, China and Japan use SC(å›½).  Japan use a small set of CJK character
> that are japan simplified traditional Kanji . Many of these are used in
> Taiwan and China , these are not just the PRC simplified characters. I
think
> no Japanese will be happy  if æ—¥æœ¬åœ‹ will be confused with  æ—¥æœ¬å›½ .

Right. I think we are making the same point here, which is that Japanese
users think of Kanji as a Japanese script, distinct from Chinese and Korean
scripts, and they will be dismayed if their domains are displayed in
different
script or if their registration of a Kanji name is blocked because of a
prior
registration of  the Chinese equivalent in a different script. Of course if
the
characters used are actually identical, they would probably accept that the
name was already taken.





From owner-idn@ops.ietf.org  Fri Aug 17 02:50: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 CAA20497
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 02:50:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XdMk-0008N5-00
	for idn-data@psg.com; Thu, 16 Aug 2001 23:44:22 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XdMi-0008Mp-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 23:44:20 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 42398FFC0A; Fri, 17 Aug 2001 14:45:41 +0800 (SGT)
Message-ID: <05d101c126e8$04b7d830$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Xiaodong LEE" <Xiaodong.Lee@cnnic.net.cn>, <tsenglm@cc.ncu.edu.tw>,
        <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>, <dhc@dcrocker.net>
References: <20010816.222200.-746899.10.liana.ydisg@juno.com> <053d01c126e1$6d432aa0$dd00a8c0@jamessonyvaio> <001b01c126e4$2b745dd0$4607e29f@xiaodonglee>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 17 Aug 2001 14:44: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

One note:

The WG is chartered in a narrow manner to solve a particular problem.
And if we were to expand it to solve a larger-set of problem, we could
but it would mean we would probably have to restart almost all over
again.

I was also reminded once in a while by some folk in IETF that this WG
should be prepare to declare "no-solution" because it does not meet the
"user requirements" (that is vaguely defined unfortunately). But I
remind optimistic that we can find a solution to an "internationalized
domain names" problem with the limited scope we have.

However, should we want to start discussing on "multilingual naming"
problem, then either (a) it is out of scope for this wg or (b) this wg
should declare "there is no solution in domain names space" and lets not
waste time in this wg.

While I am incline to (a) (altho I have not hear any formal complain
that multilingual naming is out-of-scope), (b) is an option I am prepare
to take if this is the consensus of the wg.

-James Seng

----- Original Message -----
From: "xiaodong lee" <lee@whale.cnnic.net.cn>
To: "James Seng/Personal" <James@Seng.cc>; <tsenglm@cc.ncu.edu.tw>;
<liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>; <dhc@dcrocker.net>
Sent: Friday, August 17, 2001 2:16 PM
Subject: Re: [idn] opting out of SC/TC equivalence


> > Thus, I would modify your statement below to: "from each SCRIPT
> > users/engineers and ask them how they want their scripts to be use".
> > (ie. all han ideograph (CJK) users should talk about han folding
> > together if we going down the path of tsconv).
> >
> Prof. Tseng care more about users requirements, I think, a technology
developed without
> enough users requirements, it makes no sense.






From owner-idn@ops.ietf.org  Fri Aug 17 03:05: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 DAA20697
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 03:05:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XdSp-0008Wz-00
	for idn-data@psg.com; Thu, 16 Aug 2001 23:50:39 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XdSo-0008Ws-00
	for idn@ops.ietf.org; Thu, 16 Aug 2001 23:50:38 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1TQXw5HYsoiK02n2p1Dgk6lg==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GC2BLVAL; Fri, 17 Aug 2001 02:50:15 EDT
To: lsb@postel.co.kr
Cc: liana.ydisg@juno.com, bthomson@fm-net.ne.jp, idn@ops.ietf.org
Date: Fri, 17 Aug 2001 00:08:00 -0700
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Message-ID: <20010817.000804.-746899.13.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-15,17-36
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

It is correct, there will be no disambiguations in 
DNS for anyone.  It has to be resolved at registration 
time.  Then do you need Hanja in Domain name at all?
Why? If Hanja names is only used for Chinese and Japanese,
then how do Korean people separated from each other? 
Are there many people with the same Hangul names?

I have heard a law suit case here, that a Vietnanese vs. 
another Vietnanese in the San Francisco area, both
sides of the case and a witness of the case all have 
exact the same name!  And they all need interpretations too.
Imagine the headaches for the lawyers!

Liana 


On Fri, 17 Aug 2001 15:06:01 +0900 "Soobok Lee" <lsb@postel.co.kr>
writes:
> Hi, Liana
> 
> ----- Original Message ----- 
> From: <liana.ydisg@juno.com>
> > What happen when people read newspapers with Hangul 
> > without Hanji such as it is in North Korean?  
> > How to you get a Hanji through hangul if it is one-to-many 
> > correspondence?
> > 
> Korean have been familiar with many hangeul homonyms that
> share the same hangeul word but have different TC forms/meanings
> and optionally different sounds (long or short vowel etc) .
> Ordinary Korean can disambiguate them  only by the surrounding
> semantical context (sentence or paragraph) in which they appear.
> 
> In DNS, we have no such contextual clue for disambiguations.
> 
> Soobok
> 



From owner-idn@ops.ietf.org  Fri Aug 17 03:21: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 DAA20895
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 03:21:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XdpR-0009QR-00
	for idn-data@psg.com; Fri, 17 Aug 2001 00:14:01 -0700
Received: from [203.207.0.132] (helo=mail.asiainfra.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XdpQ-0009PI-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 00:14:00 -0700
Received: from gix ([203.207.0.121])
	by mail.asiainfra.com (8.9.3/8.9.3) with SMTP id PAA26776;
	Fri, 17 Aug 2001 15:13:25 +0800
From: "Kenny Huang" <huangk@alum.sinica.edu>
To: "James Seng/Personal" <James@Seng.cc>, <tsenglm@cc.ncu.edu.tw>,
        <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>, <dhc@dcrocker.net>
Subject: RE: [idn] opting out of SC/TC equivalence
Date: Fri, 17 Aug 2001 15:17:39 +0800
Message-ID: <000701c126ec$b2aeebf0$7900cfcb@asiainfra.com>
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.00.2919.6700
In-Reply-To: <053d01c126e1$6d432aa0$dd00a8c0@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 DAA20895

Hi James,

"A script is a written form of a language". Again, we may want to question :
"What is the goal of this WG" or "What is the need of non-English speaker" ?
Are you proposing we should setup a MDN WG to replace things have
done so far ?


Kenny Huang

-----Original Message-----
From: owner-idn@ops.ietf.org [mailto:owner-idn@ops.ietf.org]On Behalf Of James Seng/Personal
Sent: Friday, August 17, 2001 1:57 PM
To: tsenglm@cc.ncu.edu.tw; liana.ydisg@juno.com
Cc: idn@ops.ietf.org; dhc@dcrocker.net
Subject: Re: [idn] opting out of SC/TC equivalence


As much as I agree with Prof Tseng well-intention, unfortunately, the
concept of "language" is out of scope for the working group.

This working is chartered to do "Internationalized access to Domain
Names". Unfortunately, domain names understand only "script" not
"language". It does not matter what you wish, it can't be done in Domain
Names (It can be done in some other mechanism of course).

And we are doing "Internationalization" not "Multilingualism". These may
just be terminology but the subtle differences in these terms makes a
lot of differences. I learn it the hard way for those who is with the WG
from the beginning.

Thus, I would modify your statement below to: "from each SCRIPT
users/engineers and ask them how they want their scripts to be use".
(ie. all han ideograph (CJK) users should talk about han folding
together if we going down the path of tsconv).

-James Seng

----- Original Message -----
From: <liana.ydisg@juno.com>
To: <tsenglm@cc.ncu.edu.tw>
Cc: <idn@ops.ietf.org>; <dhc@dcrocker.net>
Sent: Friday, August 17, 2001 1:17 PM
Subject: Re: [idn] opting out of SC/TC equivalence


> I agree with Prof. Tseng's point.  And I suggest that
> we shall collect inputs from each language users/engineers
>  and ask them what do they think about their scripts should
> be handled.  What are the non-semantic issues that
> could be dealed with [nameprep] type of simple scheme and
> benifit long term communication and identification of
> a hostname on the internet.
>
> Liana
>
> On Fri, 17 Aug 2001 11:14:37 +0800
> =?UTF-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?=
> <tsenglm@cc.ncu.edu.tw> writes:
>        If your statements are meant John is the God father , so no
> > one can
> > pass over the line he defined , I will ask what is the goal of this
> > WG ?
> > Does it is used to hurt other people in this world ?
> >       IDN is very complex ,  but if  you try to neglect some truth
> > then the
> > political issue will be introduced , then no one will be happy .
> >
> > L.M.Tseng
> >
>




From owner-idn@ops.ietf.org  Fri Aug 17 03:21: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 DAA20906
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 03:21:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XdpY-0009Qb-00
	for idn-data@psg.com; Fri, 17 Aug 2001 00:14:08 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XdpX-0009QV-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 00:14:07 -0700
Received: from soobok ([210.217.27.237] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id QAA09144;
	Fri, 17 Aug 2001 16:13:48 +0900
Message-ID: <015b01c126ec$3349daa0$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <liana.ydisg@juno.com>
Cc: <liana.ydisg@juno.com>, <bthomson@fm-net.ne.jp>, <idn@ops.ietf.org>
References: <20010817.000804.-746899.13.liana.ydisg@juno.com>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Date: Fri, 17 Aug 2001 16:14:04 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message ----- 
From: <liana.ydisg@juno.com>
To: <lsb@postel.co.kr>
Cc: <liana.ydisg@juno.com>; <bthomson@fm-net.ne.jp>; <idn@ops.ietf.org>
Sent: Friday, August 17, 2001 4:08 PM
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee


> It is correct, there will be no disambiguations in 
> DNS for anyone.  It has to be resolved at registration 
> time.  Then do you need Hanja in Domain name at all?

Yes, but rarely.
some japanese/chinese restaurants in SEOUL Korea
 have the primary name in Hanja(Kanji).
Most korean individuals/companies won't pay for
rarely used HANJA domains, I guess.

> Why? If Hanja names is only used for Chinese and Japanese,
> then how do Korean people separated from each other? 
> Are there many people with the same Hangul names?

Most Koreans have their TC-form fullnames. Many Korean
businesses , too. But they are not used so frequently
as hangul ones.


In my rough estimation, most frequent 5000 hangul personal full names 
form the set of distinct fullnames of about 90% of korean populations.

South Korean population reached  47,000,000 recently.

> 
> I have heard a law suit case here, that a Vietnanese vs. 
> another Vietnanese in the San Francisco area, both
> sides of the case and a witness of the case all have 
> exact the same name!  And they all need interpretations too.
> Imagine the headaches for the lawyers!
> 

:-))

Soobok

> Liana 
> 
> 
> On Fri, 17 Aug 2001 15:06:01 +0900 "Soobok Lee" <lsb@postel.co.kr>
> writes:
> > Hi, Liana
> > 
> > ----- Original Message ----- 
> > From: <liana.ydisg@juno.com>
> > > What happen when people read newspapers with Hangul 
> > > without Hanji such as it is in North Korean?  
> > > How to you get a Hanji through hangul if it is one-to-many 
> > > correspondence?
> > > 
> > Korean have been familiar with many hangeul homonyms that
> > share the same hangeul word but have different TC forms/meanings
> > and optionally different sounds (long or short vowel etc) .
> > Ordinary Korean can disambiguate them  only by the surrounding
> > semantical context (sentence or paragraph) in which they appear.
> > 
> > In DNS, we have no such contextual clue for disambiguations.
> > 
> > Soobok
> > 
> 




From owner-idn@ops.ietf.org  Fri Aug 17 03:23:10 2001
Received: from psg.com (exim@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20920
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 03:23:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xdme-0009Mr-00
	for idn-data@psg.com; Fri, 17 Aug 2001 00:11:08 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xdmc-0009Ml-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 00:11:07 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 7B0BDFFC0D; Fri, 17 Aug 2001 15:12:29 +0800 (SGT)
Message-ID: <05f401c126eb$c344f190$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Xiaodong LEE" <Xiaodong.Lee@cnnic.net.cn>, <tsenglm@cc.ncu.edu.tw>
Cc: <idn@ops.ietf.org>
References: <20010816.222200.-746899.10.liana.ydisg@juno.com> <053d01c126e1$6d432aa0$dd00a8c0@jamessonyvaio> <001b01c126e4$2b745dd0$4607e29f@xiaodonglee>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 17 Aug 2001 15:10:57 +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

Hi Xiangdong,

Now, responsing directly to your note:

First, I hope we can agree that the wg is well aware of the TC/SC
problem (after such a long discussion thread) and we are all actively
seeking a solution to it. We may disagree with the approach but we are
certainly not disagreeing with the principle.

> you said it. Maybe we could not handle language problems in IDN, but
we could
> not forget that all script have language characteristics of
themselves, especially for
> Chinese. Internationalization means all users could use their familiar
ways to use
> domain name, not means all users must follow one ways.

Lets use logic to discuss this: A. domain names B. scripts C. languages

Your reasoning:
domain names handle script. A->B
script are used by languages. B->C
Therefore, domain names handle language. A->C

basic logic tells us that the last statement is not always true. And in
this case, domain names is not able to handle language. This is a known
limitation of domain names.

> Exactly, we are doing internationalization, but how do we explain for
> users what is internationalization, and what is multilingualism, I
> think ordinary users care about how to use , not what is.

Agree. Very few people recongized the differences.

While there is an desire to solve 100% of the users problem today, all
developments started with one small step at a time. Without solving the
first 10%, we wont know what the next 10% problem. This wg is not the
first nor will be the last one to solve the whole I18N problem. It is
one of the puzzle piece for the IETF and there are many other puzzle to
solve in future. So lets not put too much task upon ourselves.

> > Thus, I would modify your statement below to: "from each SCRIPT
> > users/engineers and ask them how they want their scripts to be use".
> > (ie. all han ideograph (CJK) users should talk about han folding
> > together if we going down the path of tsconv).
> >
>
> Prof. Tseng care more about users requirements, I think, a technology
developed without
> enough users requirements, it makes no sense.

And so am I. This is why I can understand Prof Tseng's well-intention.

But the "users set" in IETF context are not limited to any particular
locale so the opinion to the solution may be slightly different due to
different perspective.

Anyhow, lets not argue further on these details anymore but lets focus
on doing the job. The tsconv draft requires more work so lets put more
effort into that to make sure it is completed.

*cheers*

-James Seng




From owner-idn@ops.ietf.org  Fri Aug 17 03: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 DAA20937
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 03:25:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XdqU-0009SB-00
	for idn-data@psg.com; Fri, 17 Aug 2001 00:15:06 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XdqT-0009S4-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 00:15:05 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1TWR+51qc3NtaZ9eD069vt2Q==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GC2CYTZH; Fri, 17 Aug 2001 03:14:16 EDT
To: bthomson@fm-net.ne.jp
Cc: idn@ops.ietf.org
Date: Fri, 17 Aug 2001 00:31:30 -0700
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Message-ID: <20010817.003135.-746899.14.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.11
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-5,7-51
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 can you say Romaji is a good enough IDN 
identifier?  Can you reverse Romaji to Kana or 
even to Kanji with say very high one-to-one rate?

Liana

On Fri, 17 Aug 2001 15:15:58 +0900 "Bruce Thomson"
<bthomson@fm-net.ne.jp> writes:
> > By the way, how do you Romanize a word containing
> > Kanji and Kana?
> > 
> 
> There are two steps:
> 
> 1) Convert all Kanji to kana. Anything that can be pronounced
> in Japanese can be expressed as the kana equivalent of that
> pronunciation. However, Kanji cannot be converted one at a time
> as many words are unique combinations of Kanji with special
> pronuncations. Also, there can be multiple pronunciations for the
> same Kanji string.
> 
> 2) Once you have everything in kana, convert to "Romaji"
> (Romanized characters) using the Hepburn system. Here
> are the Romaji equivalents of all the modern kana:
> 
> a  i  u  e  o
> ka ki ku ke ko
> sa shi su se so
> ta chi tsu te to
> na ni nu ne no
> ha hi fu he ho
> ma mi mu me mo
> ya yu yo
> ra ri ru re ro
> wa wo
> n
> 
> There is a further complication in that a small kana
> tsu is used to represent a double consonant when
> a word is written as kana, whereas the consonant
> is merely written twice in the Romaji equivalent.
> 
> By the way, Japanese keyboard input is usually
> handled by typing Romaji which can then be
> converted to kana and further converted into
> Kanji.
> 
> http://www.omniglot.com/writing/japanese.htm
> http://www.kanjisite.com/wak1.html
> 
> 
> 



From owner-idn@ops.ietf.org  Fri Aug 17 03:35: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 DAA21105
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 03:35:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xdzs-0009nb-00
	for idn-data@psg.com; Fri, 17 Aug 2001 00:24:48 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xdzr-0009nU-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 00:24:47 -0700
Received: from soobok ([210.217.27.237] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id QAA12501;
	Fri, 17 Aug 2001 16:24:34 +0900
Message-ID: <016a01c126ed$b3aabba0$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Bruce Thomson" <bthomson@fm-net.ne.jp>, <idn@ops.ietf.org>
References: <200108162112.f7GLCMO60062@nic-naa.net> <0e4501c126c4$c2ca5510$a3420fd3@bruce> <001701c126e2$752e0860$fb05738c@ncu.edu.tw> <0eb701c126e5$a1d8a2a0$a3420fd3@bruce>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Date: Fri, 17 Aug 2001 16:24:49 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message ----- 
From: "Bruce Thomson" <bthomson@fm-net.ne.jp>
 > 
> Right. I think we are making the same point here, which is that Japanese
> users think of Kanji as a Japanese script, distinct from Chinese and Korean
> scripts, and they will be dismayed if their domains are displayed in
> different script or 

Not always!
Future IDN-aware applications MAY carry the pre-normalization form of 
IDNs to display the original prefered forms of them .
This issue seems to be in the middle between application scope and iDN scope.

>if their registration of a Kanji name is blocked because of a
> prior registration of  the Chinese equivalent in a different script. 
>Of course if the
> characters used are actually identical, they would probably accept that the
> name was already taken.
> 
> 

It's wise for the registries  to give "already taken" message instead
of "blocked"  for registration failure  to avoid registrants'
complaints . :-))


Soobok Lee




From owner-idn@ops.ietf.org  Fri Aug 17 03:46: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 DAA21265
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 03:45:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XeC6-000AFS-00
	for idn-data@psg.com; Fri, 17 Aug 2001 00:37:26 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XeC5-000AFL-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 00:37:26 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1T0jRYJDvylVP7zCypKN/rlg==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GC2EAU5H; Fri, 17 Aug 2001 03:37:13 EDT
To: lsb@postel.co.kr
Cc: bthomson@fm-net.ne.jp, idn@ops.ietf.org
Date: Fri, 17 Aug 2001 00:54:29 -0700
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Message-ID: <20010817.005432.-746899.15.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-10,12-86
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 Hangul mapped to Latin letters like Romaji and then
add a number to select one Kanji among a few 
homophones, can this be good enough to idnetify a Hanja
name in DNS?

The same question goes to Bruce Thomson:
Can Romaji be revered back to Kanji-Kana sequece with
near 100% rate (with or without case ending)?

Liana

On Fri, 17 Aug 2001 16:14:04 +0900 "Soobok Lee" <lsb@postel.co.kr>
writes:
> 
> ----- Original Message ----- 
> From: <liana.ydisg@juno.com>
> To: <lsb@postel.co.kr>
> Cc: <liana.ydisg@juno.com>; <bthomson@fm-net.ne.jp>; 
> <idn@ops.ietf.org>
> Sent: Friday, August 17, 2001 4:08 PM
> Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
> 
> 
> > It is correct, there will be no disambiguations in 
> > DNS for anyone.  It has to be resolved at registration 
> > time.  Then do you need Hanja in Domain name at all?
> 
> Yes, but rarely.
> some japanese/chinese restaurants in SEOUL Korea
>  have the primary name in Hanja(Kanji).
> Most korean individuals/companies won't pay for
> rarely used HANJA domains, I guess.
> 
> > Why? If Hanja names is only used for Chinese and Japanese,
> > then how do Korean people separated from each other? 
> > Are there many people with the same Hangul names?
> 
> Most Koreans have their TC-form fullnames. Many Korean
> businesses , too. But they are not used so frequently
> as hangul ones.
> 
> 
> In my rough estimation, most frequent 5000 hangul personal full 
> names 
> form the set of distinct fullnames of about 90% of korean 
> populations.
> 
> South Korean population reached  47,000,000 recently.
> 
> > 
> > I have heard a law suit case here, that a Vietnanese vs. 
> > another Vietnanese in the San Francisco area, both
> > sides of the case and a witness of the case all have 
> > exact the same name!  And they all need interpretations too.
> > Imagine the headaches for the lawyers!
> > 
> 
> :-))
> 
> Soobok
> 
> > Liana 
> > 
> > 
> > On Fri, 17 Aug 2001 15:06:01 +0900 "Soobok Lee" <lsb@postel.co.kr>
> > writes:
> > > Hi, Liana
> > > 
> > > ----- Original Message ----- 
> > > From: <liana.ydisg@juno.com>
> > > > What happen when people read newspapers with Hangul 
> > > > without Hanji such as it is in North Korean?  
> > > > How to you get a Hanji through hangul if it is one-to-many 
> > > > correspondence?
> > > > 
> > > Korean have been familiar with many hangeul homonyms that
> > > share the same hangeul word but have different TC forms/meanings
> > > and optionally different sounds (long or short vowel etc) .
> > > Ordinary Korean can disambiguate them  only by the surrounding
> > > semantical context (sentence or paragraph) in which they appear.
> > > 
> > > In DNS, we have no such contextual clue for disambiguations.
> > > 
> > > Soobok
> > > 
> > 
> 



From owner-idn@ops.ietf.org  Fri Aug 17 03:46: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 DAA21278
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 03:46:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xe9p-000A8C-00
	for idn-data@psg.com; Fri, 17 Aug 2001 00:35:05 -0700
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xe9l-000A7y-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 00:35:01 -0700
Received: from xiaodonglee ([159.226.7.70]) by
          whale.cnnic.net.cn (Netscape Messaging Server 4.15) with SMTP id
          GI7BT500.3DA; Fri, 17 Aug 2001 15:36:41 +0800 
Message-ID: <005c01c126ee$953e3b00$4607e29f@xiaodonglee>
Reply-To: "Xiaodong LEE" <Xiaodong.Lee@cnnic.net.cn>
From: "xiaodong lee" <lee@whale.cnnic.net.cn>
To: "James Seng/Personal" <James@Seng.cc>,
        "Xiaodong LEE" <Xiaodong.Lee@cnnic.net.cn>, <tsenglm@cc.ncu.edu.tw>
Cc: <idn@ops.ietf.org>
References: <20010816.222200.-746899.10.liana.ydisg@juno.com> <053d01c126e1$6d432aa0$dd00a8c0@jamessonyvaio> <001b01c126e4$2b745dd0$4607e29f@xiaodonglee> <05f401c126eb$c344f190$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 17 Aug 2001 15:31:08 +0800
Organization: CNIC-ICT
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
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 DAA21278

Hello James
I think we made some misunderstanding on the difference between language and scripts.
I do have no interest to handle language problem in DNS, it is not a good idea as you know. :))
I mean that some problem like TSconv is a language problem originally in some sense. but it 
is not only a language problem finally.  
Right is you basic logic, so I suggest to handle such problem differently too. we need to adopt 
a properly ways to divide the problem into different part, and handle them in different method.
I agree with you, we should try to find a effective solution. we need try, including me.  :-))
ok!
Xiaodong Lee


----- Original Message ----- 
From: "James Seng/Personal" <James@Seng.cc>
To: "Xiaodong LEE" <Xiaodong.Lee@cnnic.net.cn>; <tsenglm@cc.ncu.edu.tw>
Cc: <idn@ops.ietf.org>
Sent: Friday, August 17, 2001 3:10 PM
Subject: Re: [idn] opting out of SC/TC equivalence


> Hi Xiangdong,
> 
> Now, responsing directly to your note:
> 
> First, I hope we can agree that the wg is well aware of the TC/SC
> problem (after such a long discussion thread) and we are all actively
> seeking a solution to it. We may disagree with the approach but we are
> certainly not disagreeing with the principle.
> 
> > you said it. Maybe we could not handle language problems in IDN, but
> we could
> > not forget that all script have language characteristics of
> themselves, especially for
> > Chinese. Internationalization means all users could use their familiar
> ways to use
> > domain name, not means all users must follow one ways.
> 
> Lets use logic to discuss this: A. domain names B. scripts C. languages
> 
> Your reasoning:
> domain names handle script. A->B
> script are used by languages. B->C
> Therefore, domain names handle language. A->C
> 
> basic logic tells us that the last statement is not always true. And in
> this case, domain names is not able to handle language. This is a known
> limitation of domain names.
> 
> > Exactly, we are doing internationalization, but how do we explain for
> > users what is internationalization, and what is multilingualism, I
> > think ordinary users care about how to use , not what is.
> 
> Agree. Very few people recongized the differences.
> 
> While there is an desire to solve 100% of the users problem today, all
> developments started with one small step at a time. Without solving the
> first 10%, we wont know what the next 10% problem. This wg is not the
> first nor will be the last one to solve the whole I18N problem. It is
> one of the puzzle piece for the IETF and there are many other puzzle to
> solve in future. So lets not put too much task upon ourselves.
> 
> > > Thus, I would modify your statement below to: "from each SCRIPT
> > > users/engineers and ask them how they want their scripts to be use".
> > > (ie. all han ideograph (CJK) users should talk about han folding
> > > together if we going down the path of tsconv).
> > >
> >
> > Prof. Tseng care more about users requirements, I think, a technology
> developed without
> > enough users requirements, it makes no sense.
> 
> And so am I. This is why I can understand Prof Tseng's well-intention.
> 
> But the "users set" in IETF context are not limited to any particular
> locale so the opinion to the solution may be slightly different due to
> different perspective.
> 
> Anyhow, lets not argue further on these details anymore but lets focus
> on doing the job. The tsconv draft requires more work so lets put more
> effort into that to make sure it is completed.
> 
> *cheers*
> 
> -James Seng
> 
> 


From owner-idn@ops.ietf.org  Fri Aug 17 03:57: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 DAA21400
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 03:57:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XeOH-000Acd-00
	for idn-data@psg.com; Fri, 17 Aug 2001 00:50:01 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XeOG-000AcS-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 00:50:00 -0700
Received: from soobok ([210.217.27.237] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id QAA20371;
	Fri, 17 Aug 2001 16:49:38 +0900
Message-ID: <018601c126f1$24d076a0$ed1bd9d2@postel.co.kr>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>, <liana.ydisg@juno.com>
Cc: <liana.ydisg@juno.com>, <bthomson@fm-net.ne.jp>, <idn@ops.ietf.org>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Date: Fri, 17 Aug 2001 16:49:27 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Two corrections:

----- Original Message ----- 
From: "Soobok Lee" <lsb@postel.co.kr>
To: <liana.ydisg@juno.com>
Cc: <liana.ydisg@juno.com>; <bthomson@fm-net.ne.jp>; <idn@ops.ietf.org>
Sent: Friday, August 17, 2001 4:14 PM
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee


> 
> ----- Original Message ----- 
> From: <liana.ydisg@juno.com>
> To: <lsb@postel.co.kr>
> Cc: <liana.ydisg@juno.com>; <bthomson@fm-net.ne.jp>; <idn@ops.ietf.org>
> Sent: Friday, August 17, 2001 4:08 PM
> Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
> 
> 
> > It is correct, there will be no disambiguations in 
> > DNS for anyone.  It has to be resolved at registration 
> > time.  Then do you need Hanja in Domain name at all?
> 
> Yes, but rarely.
> some japanese/chinese restaurants in SEOUL Korea
>  have the primary name in Hanja(Kanji).
> Most korean individuals/companies won't pay for
> rarely used HANJA domains, I guess.

That may change near future..

Recently, Korean Goverments began to encourage
HanJa education/Hanja Usages in addition to English ones.
You know the economic block of Eastern Asia is rapidly 
expanding its power... :-)


> 
> > Why? If Hanja names is only used for Chinese and Japanese,
> > then how do Korean people separated from each other? 
> > Are there many people with the same Hangul names?
> 
> Most Koreans have their TC-form fullnames. Many Korean
> businesses , too. But they are not used so frequently
> as hangul ones.
> 
> 
> In my rough estimation, most frequent 5000 hangul personal full names 
> form the set of distinct fullnames of about 90% of korean populations.
> 
Oh my mistake.  5000 ====> 100,000.

100,000 distinct fullnames, and 5,000 distinct given(first) names acount
for 90% of individual names of south korean population,based on the personal
study on 600,000 samples of korean fullnames.

Thanks.

> South Korean population reached  47,000,000 recently.
> 
> > 
> > I have heard a law suit case here, that a Vietnanese vs. 
> > another Vietnanese in the San Francisco area, both
> > sides of the case and a witness of the case all have 
> > exact the same name!  And they all need interpretations too.
> > Imagine the headaches for the lawyers!
> > 
> 
> :-))
> 
> Soobok
> 
> > Liana 
> > 
> > 
> > On Fri, 17 Aug 2001 15:06:01 +0900 "Soobok Lee" <lsb@postel.co.kr>
> > writes:
> > > Hi, Liana
> > > 
> > > ----- Original Message ----- 
> > > From: <liana.ydisg@juno.com>
> > > > What happen when people read newspapers with Hangul 
> > > > without Hanji such as it is in North Korean?  
> > > > How to you get a Hanji through hangul if it is one-to-many 
> > > > correspondence?
> > > > 
> > > Korean have been familiar with many hangeul homonyms that
> > > share the same hangeul word but have different TC forms/meanings
> > > and optionally different sounds (long or short vowel etc) .
> > > Ordinary Korean can disambiguate them  only by the surrounding
> > > semantical context (sentence or paragraph) in which they appear.
> > > 
> > > In DNS, we have no such contextual clue for disambiguations.
> > > 
> > > Soobok
> > > 
> > 
> 




From owner-idn@ops.ietf.org  Fri Aug 17 04:20: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 EAA21638
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 04:20:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xefi-000BCv-00
	for idn-data@psg.com; Fri, 17 Aug 2001 01:08:02 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xefh-000BCY-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 01:08:01 -0700
Received: from test.ncu.edu.tw ([140.115.5.251])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f7H8CB719026;
	Fri, 17 Aug 2001 16:12:12 +0800 (CST)
Message-ID: <006c01c126f3$93796740$fb05738c@ncu.edu.tw>
From: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: "Kenny Huang" <huangk@alum.sinica.edu>,
        "James Seng/Personal" <James@Seng.cc>, <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>, <dhc@dcrocker.net>
References: <000701c126ec$b2aeebf0$7900cfcb@asiainfra.com>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 17 Aug 2001 16:06:52 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi James,
             I  think you can display these chinese characters in your
system, so you can make
the explaination , and  tell me the answer how to treat them ?
TC(çµ±) , SC(ç»Ÿ)
TC(é »),  SC(é¢‘)

They are  the same chinese characters in pairs but they are coded with
different  UNICODE .
Does they are like the problems of   " fi " ?
And  tell me  why  ï½�ã€€ï¼¡ã€€should  be mapped to ASCII  "a" or "A" ?

I don't expect  this WG to solve all the equivalence of TC/SC. I just want
to know what is the guideline to reduce the confusing troubles in nameprep ?
Why so amall set of  PRC simplified quick-written scripts are not case
folding problem ?

L.M.Tseng

----- Original Message -----
From: "Kenny Huang" <huangk@alum.sinica.edu>
To: "James Seng/Personal" <James@Seng.cc>; <tsenglm@cc.ncu.edu.tw>;
<liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>; <dhc@dcrocker.net>
Sent: Friday, August 17, 2001 3:17 PM
Subject: RE: [idn] opting out of SC/TC equivalence


> Hi James,
>
> "A script is a written form of a language". Again, we may want to question
:
> "What is the goal of this WG" or "What is the need of non-English speaker"
?
> Are you proposing we should setup a MDN WG to replace things have
> done so far ?
>
>
> Kenny Huang
>
> -----Original Message-----
> From: owner-idn@ops.ietf.org [mailto:owner-idn@ops.ietf.org]On Behalf Of
James Seng/Personal
> Sent: Friday, August 17, 2001 1:57 PM
> To: tsenglm@cc.ncu.edu.tw; liana.ydisg@juno.com
> Cc: idn@ops.ietf.org; dhc@dcrocker.net
> Subject: Re: [idn] opting out of SC/TC equivalence
>
>
> As much as I agree with Prof Tseng well-intention, unfortunately, the
> concept of "language" is out of scope for the working group.
>
> This working is chartered to do "Internationalized access to Domain
> Names". Unfortunately, domain names understand only "script" not
> "language". It does not matter what you wish, it can't be done in Domain
> Names (It can be done in some other mechanism of course).
>
> And we are doing "Internationalization" not "Multilingualism". These may
> just be terminology but the subtle differences in these terms makes a
> lot of differences. I learn it the hard way for those who is with the WG
> from the beginning.
>
> Thus, I would modify your statement below to: "from each SCRIPT
> users/engineers and ask them how they want their scripts to be use".
> (ie. all han ideograph (CJK) users should talk about han folding
> together if we going down the path of tsconv).
>
> -James Seng
>
> ----- Original Message -----
> From: <liana.ydisg@juno.com>
> To: <tsenglm@cc.ncu.edu.tw>
> Cc: <idn@ops.ietf.org>; <dhc@dcrocker.net>
> Sent: Friday, August 17, 2001 1:17 PM
> Subject: Re: [idn] opting out of SC/TC equivalence
>
>
> > I agree with Prof. Tseng's point.  And I suggest that
> > we shall collect inputs from each language users/engineers
> >  and ask them what do they think about their scripts should
> > be handled.  What are the non-semantic issues that
> > could be dealed with [nameprep] type of simple scheme and
> > benifit long term communication and identification of
> > a hostname on the internet.
> >
> > Liana
> >
> > On Fri, 17 Aug 2001 11:14:37 +0800
> > =?UTF-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?=
> > <tsenglm@cc.ncu.edu.tw> writes:
> >        If your statements are meant John is the God father , so no
> > > one can
> > > pass over the line he defined , I will ask what is the goal of this
> > > WG ?
> > > Does it is used to hurt other people in this world ?
> > >       IDN is very complex ,  but if  you try to neglect some truth
> > > then the
> > > political issue will be introduced , then no one will be happy .
> > >
> > > L.M.Tseng
> > >
> >
>
>




From owner-idn@ops.ietf.org  Fri Aug 17 04:39: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 EAA21798
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 04:39:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xf0e-000Bks-00
	for idn-data@psg.com; Fri, 17 Aug 2001 01:29:40 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xf0d-000Bkl-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 01:29:39 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id RAA00371;
	Fri, 17 Aug 2001 17:29:20 +0900
Message-ID: <057e01c126f5$ef89e800$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <liana.ydisg@juno.com>
Cc: <bthomson@fm-net.ne.jp>, <idn@ops.ietf.org>
References: <20010817.005432.-746899.15.liana.ydisg@juno.com>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Date: Fri, 17 Aug 2001 17:23:45 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message ----- 
From: <liana.ydisg@juno.com>
To: <lsb@postel.co.kr>
Cc: <bthomson@fm-net.ne.jp>; <idn@ops.ietf.org>
Sent: Friday, August 17, 2001 4:54 PM
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee


> If Hangul mapped to Latin letters like Romaji and then
> add a number to select one Kanji among a few 
> homophones, can this be good enough to idnetify a Hanja
> name in DNS?

 some hangul  trailing jamos,
for example , di-geuth, hi-euth and ti-euth,
 have the same sound while their leading jamo 
have different sounds. You need some differenciating 
representation of trailing hangul jamos in romanizing hangeul and
That may cause some overheads...

Even a Hanja/Kanji/TC/SC letter often has multiple pronunciations 
in different words and so  multiple romanizations for a hanja 
letter are possible!!

IMHO,Pronunciation-based romanization on Hanja/Kanji/TC/SC 
should be performed in word/language context 
(not in individual unicode point context ) , but It's not achievable in DNS
which may have no language/script context (in .com) and often have no
word sematics in a label (single han letter label).


Soobok

> 
> The same question goes to Bruce Thomson:
> Can Romaji be revered back to Kanji-Kana sequece with
> near 100% rate (with or without case ending)?
> 
> Liana
> 
> On Fri, 17 Aug 2001 16:14:04 +0900 "Soobok Lee" <lsb@postel.co.kr>
> writes:
> > 
> > ----- Original Message ----- 
> > From: <liana.ydisg@juno.com>
> > To: <lsb@postel.co.kr>
> > Cc: <liana.ydisg@juno.com>; <bthomson@fm-net.ne.jp>; 
> > <idn@ops.ietf.org>
> > Sent: Friday, August 17, 2001 4:08 PM
> > Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
> > 
> > 
> > > It is correct, there will be no disambiguations in 
> > > DNS for anyone.  It has to be resolved at registration 
> > > time.  Then do you need Hanja in Domain name at all?
> > 
> > Yes, but rarely.
> > some japanese/chinese restaurants in SEOUL Korea
> >  have the primary name in Hanja(Kanji).
> > Most korean individuals/companies won't pay for
> > rarely used HANJA domains, I guess.
> > 
> > > Why? If Hanja names is only used for Chinese and Japanese,
> > > then how do Korean people separated from each other? 
> > > Are there many people with the same Hangul names?
> > 
> > Most Koreans have their TC-form fullnames. Many Korean
> > businesses , too. But they are not used so frequently
> > as hangul ones.
> > 
> > 
> > In my rough estimation, most frequent 5000 hangul personal full 
> > names 
> > form the set of distinct fullnames of about 90% of korean 
> > populations.
> > 
> > South Korean population reached  47,000,000 recently.
> > 
> > > 
> > > I have heard a law suit case here, that a Vietnanese vs. 
> > > another Vietnanese in the San Francisco area, both
> > > sides of the case and a witness of the case all have 
> > > exact the same name!  And they all need interpretations too.
> > > Imagine the headaches for the lawyers!
> > > 
> > 
> > :-))
> > 
> > Soobok
> > 
> > > Liana 
> > > 
> > > 
> > > On Fri, 17 Aug 2001 15:06:01 +0900 "Soobok Lee" <lsb@postel.co.kr>
> > > writes:
> > > > Hi, Liana
> > > > 
> > > > ----- Original Message ----- 
> > > > From: <liana.ydisg@juno.com>
> > > > > What happen when people read newspapers with Hangul 
> > > > > without Hanji such as it is in North Korean?  
> > > > > How to you get a Hanji through hangul if it is one-to-many 
> > > > > correspondence?
> > > > > 
> > > > Korean have been familiar with many hangeul homonyms that
> > > > share the same hangeul word but have different TC forms/meanings
> > > > and optionally different sounds (long or short vowel etc) .
> > > > Ordinary Korean can disambiguate them  only by the surrounding
> > > > semantical context (sentence or paragraph) in which they appear.
> > > > 
> > > > In DNS, we have no such contextual clue for disambiguations.
> > > > 
> > > > Soobok
> > > > 
> > > 
> > 
> 




From owner-idn@ops.ietf.org  Fri Aug 17 04:43: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 EAA21855
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 04:43:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xf5H-000Bvf-00
	for idn-data@psg.com; Fri, 17 Aug 2001 01:34:27 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xf5G-000BvZ-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 01:34:27 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1TTU7MpnuxkkFJMxPXek7byQ==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GC2HKFS6; Fri, 17 Aug 2001 04:34:20 EDT
To: lsb@postel.co.kr
Cc: lsb@postel.co.kr, liana.ydisg@juno.com, bthomson@fm-net.ne.jp,
        idn@ops.ietf.org
Date: Fri, 17 Aug 2001 01:51:39 -0700
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Message-ID: <20010817.015142.-746899.16.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-22,24-132
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

Now, this sounds better to me now.  There are about 2300
hangul characters and 4888 Hanja.  The 2300 x 2 is more than
the number of Hanja used by Korean.  But how many homophones
per hangul anyway?  Is it less than 10?   

I am proposing a [nameprep] case folding for Korean:

Legent:
> fold to
+ concatenating
= output

Hangul > Romaji  =  Hangul in ACE
hangul + a digit  >  Romaji + a digit to select a Hanja  = Hanja in ACE

Hangul in ACE + Hanja in ACE  = ACE  identifier for DNS 

 You can get your Hangul and Hanja back when you reverse
 the process.  All your work for IDN is to prepare a conversion
table like SC/TC, and put that in [Nameprep]?  What do you think? 

Liana

On Fri, 17 Aug 2001 16:49:27 +0900 "Soobok Lee" <lsb@postel.co.kr>
writes:
> Two corrections:
> 
> ----- Original Message ----- 
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: <liana.ydisg@juno.com>
> Cc: <liana.ydisg@juno.com>; <bthomson@fm-net.ne.jp>; 
> <idn@ops.ietf.org>
> Sent: Friday, August 17, 2001 4:14 PM
> Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
> 
> 
> > 
> > ----- Original Message ----- 
> > From: <liana.ydisg@juno.com>
> > To: <lsb@postel.co.kr>
> > Cc: <liana.ydisg@juno.com>; <bthomson@fm-net.ne.jp>; 
> <idn@ops.ietf.org>
> > Sent: Friday, August 17, 2001 4:08 PM
> > Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
> > 
> > 
> > > It is correct, there will be no disambiguations in 
> > > DNS for anyone.  It has to be resolved at registration 
> > > time.  Then do you need Hanja in Domain name at all?
> > 
> > Yes, but rarely.
> > some japanese/chinese restaurants in SEOUL Korea
> >  have the primary name in Hanja(Kanji).
> > Most korean individuals/companies won't pay for
> > rarely used HANJA domains, I guess.
> 
> That may change near future..
> 
> Recently, Korean Goverments began to encourage
> HanJa education/Hanja Usages in addition to English ones.
> You know the economic block of Eastern Asia is rapidly 
> expanding its power... :-)
> 
> 
> > 
> > > Why? If Hanja names is only used for Chinese and Japanese,
> > > then how do Korean people separated from each other? 
> > > Are there many people with the same Hangul names?
> > 
> > Most Koreans have their TC-form fullnames. Many Korean
> > businesses , too. But they are not used so frequently
> > as hangul ones.
> > 
> > 
> > In my rough estimation, most frequent 5000 hangul personal full 
> names 
> > form the set of distinct fullnames of about 90% of korean 
> populations.
> > 
> Oh my mistake.  5000 ====> 100,000.
> 
> 100,000 distinct fullnames, and 5,000 distinct given(first) names 
> acount
> for 90% of individual names of south korean population,based on the 
> personal
> study on 600,000 samples of korean fullnames.
> 
> Thanks.
> 
> > South Korean population reached  47,000,000 recently.
> > 
> > > 
> > > I have heard a law suit case here, that a Vietnanese vs. 
> > > another Vietnanese in the San Francisco area, both
> > > sides of the case and a witness of the case all have 
> > > exact the same name!  And they all need interpretations too.
> > > Imagine the headaches for the lawyers!
> > > 
> > 
> > :-))
> > 
> > Soobok
> > 
> > > Liana 
> > > 
> > > 
> > > On Fri, 17 Aug 2001 15:06:01 +0900 "Soobok Lee" 
> <lsb@postel.co.kr>
> > > writes:
> > > > Hi, Liana
> > > > 
> > > > ----- Original Message ----- 
> > > > From: <liana.ydisg@juno.com>
> > > > > What happen when people read newspapers with Hangul 
> > > > > without Hanji such as it is in North Korean?  
> > > > > How to you get a Hanji through hangul if it is one-to-many 
> > > > > correspondence?
> > > > > 
> > > > Korean have been familiar with many hangeul homonyms that
> > > > share the same hangeul word but have different TC 
> forms/meanings
> > > > and optionally different sounds (long or short vowel etc) .
> > > > Ordinary Korean can disambiguate them  only by the surrounding
> > > > semantical context (sentence or paragraph) in which they 
> appear.
> > > > 
> > > > In DNS, we have no such contextual clue for disambiguations.
> > > > 
> > > > Soobok
> > > > 
> > > 
> > 
> 



From owner-idn@ops.ietf.org  Fri Aug 17 05:02: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 FAA22021
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 05:02:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XfJi-000CQs-00
	for idn-data@psg.com; Fri, 17 Aug 2001 01:49:22 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XfJh-000CQZ-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 01:49:21 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1T5R9REBgXYynw2jfPCdYAwg==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GC2JEMRS; Fri, 17 Aug 2001 04:49:11 EDT
To: lsb@postel.co.kr
Cc: liana.ydisg@juno.com, bthomson@fm-net.ne.jp, idn@ops.ietf.org
Date: Fri, 17 Aug 2001 02:06:18 -0700
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Message-ID: <20010817.020621.-746899.17.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-135
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 you use another feature of the character not based on
sound in addition to pronounciation, and fix it in your 
case folding table, then  you will have one-to-one 
mapping, and the language/semantic context is out
of the table.   

Liana

On Fri, 17 Aug 2001 17:23:45 +0900 "Soobok Lee" <lsb@postel.co.kr>
writes:
> 
> ----- Original Message ----- 
> From: <liana.ydisg@juno.com>
> To: <lsb@postel.co.kr>
> Cc: <bthomson@fm-net.ne.jp>; <idn@ops.ietf.org>
> Sent: Friday, August 17, 2001 4:54 PM
> Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
> 
> 
> > If Hangul mapped to Latin letters like Romaji and then
> > add a number to select one Kanji among a few 
> > homophones, can this be good enough to idnetify a Hanja
> > name in DNS?
> 
>  some hangul  trailing jamos,
> for example , di-geuth, hi-euth and ti-euth,
>  have the same sound while their leading jamo 
> have different sounds. You need some differenciating 
> representation of trailing hangul jamos in romanizing hangeul and
> That may cause some overheads...
> 
> Even a Hanja/Kanji/TC/SC letter often has multiple pronunciations 
> in different words and so  multiple romanizations for a hanja 
> letter are possible!!
> 
> IMHO,Pronunciation-based romanization on Hanja/Kanji/TC/SC 
> should be performed in word/language context 
> (not in individual unicode point context ) , but It's not achievable 
> in DNS
> which may have no language/script context (in .com) and often have 
> no
> word sematics in a label (single han letter label).
> 
> 
> Soobok
> 
> > 
> > The same question goes to Bruce Thomson:
> > Can Romaji be revered back to Kanji-Kana sequece with
> > near 100% rate (with or without case ending)?
> > 
> > Liana
> > 
> > On Fri, 17 Aug 2001 16:14:04 +0900 "Soobok Lee" <lsb@postel.co.kr>
> > writes:
> > > 
> > > ----- Original Message ----- 
> > > From: <liana.ydisg@juno.com>
> > > To: <lsb@postel.co.kr>
> > > Cc: <liana.ydisg@juno.com>; <bthomson@fm-net.ne.jp>; 
> > > <idn@ops.ietf.org>
> > > Sent: Friday, August 17, 2001 4:08 PM
> > > Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
> > > 
> > > 
> > > > It is correct, there will be no disambiguations in 
> > > > DNS for anyone.  It has to be resolved at registration 
> > > > time.  Then do you need Hanja in Domain name at all?
> > > 
> > > Yes, but rarely.
> > > some japanese/chinese restaurants in SEOUL Korea
> > >  have the primary name in Hanja(Kanji).
> > > Most korean individuals/companies won't pay for
> > > rarely used HANJA domains, I guess.
> > > 
> > > > Why? If Hanja names is only used for Chinese and Japanese,
> > > > then how do Korean people separated from each other? 
> > > > Are there many people with the same Hangul names?
> > > 
> > > Most Koreans have their TC-form fullnames. Many Korean
> > > businesses , too. But they are not used so frequently
> > > as hangul ones.
> > > 
> > > 
> > > In my rough estimation, most frequent 5000 hangul personal full 
> > > names 
> > > form the set of distinct fullnames of about 90% of korean 
> > > populations.
> > > 
> > > South Korean population reached  47,000,000 recently.
> > > 
> > > > 
> > > > I have heard a law suit case here, that a Vietnanese vs. 
> > > > another Vietnanese in the San Francisco area, both
> > > > sides of the case and a witness of the case all have 
> > > > exact the same name!  And they all need interpretations too.
> > > > Imagine the headaches for the lawyers!
> > > > 
> > > 
> > > :-))
> > > 
> > > Soobok
> > > 
> > > > Liana 
> > > > 
> > > > 
> > > > On Fri, 17 Aug 2001 15:06:01 +0900 "Soobok Lee" 
> <lsb@postel.co.kr>
> > > > writes:
> > > > > Hi, Liana
> > > > > 
> > > > > ----- Original Message ----- 
> > > > > From: <liana.ydisg@juno.com>
> > > > > > What happen when people read newspapers with Hangul 
> > > > > > without Hanji such as it is in North Korean?  
> > > > > > How to you get a Hanji through hangul if it is one-to-many 
> 
> > > > > > correspondence?
> > > > > > 
> > > > > Korean have been familiar with many hangeul homonyms that
> > > > > share the same hangeul word but have different TC 
> forms/meanings
> > > > > and optionally different sounds (long or short vowel etc) .
> > > > > Ordinary Korean can disambiguate them  only by the 
> surrounding
> > > > > semantical context (sentence or paragraph) in which they 
> appear.
> > > > > 
> > > > > In DNS, we have no such contextual clue for disambiguations.
> > > > > 
> > > > > Soobok
> > > > > 
> > > > 
> > > 
> > 
> 



From owner-idn@ops.ietf.org  Fri Aug 17 05: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 FAA22156
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 05:11:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XfTr-000CkK-00
	for idn-data@psg.com; Fri, 17 Aug 2001 01:59:51 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XfTq-000CkE-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 01:59:50 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id RAA09760;
	Fri, 17 Aug 2001 17:59:32 +0900
Message-ID: <059c01c126fa$27c361c0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <liana.ydisg@juno.com>
Cc: <liana.ydisg@juno.com>, <bthomson@fm-net.ne.jp>, <idn@ops.ietf.org>
References: <20010817.020621.-746899.17.liana.ydisg@juno.com>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Date: Fri, 17 Aug 2001 17:53:58 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 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

For example,
 Han letter 'nation' is pronounced :
  1) in Korea:  kuk
  2) in Japan:  kuni, kok, ...
  3) in China:  kuo, ....
If you designate an unique romanization sequence in 3)  for han 'nation',
  1) and 2) and even someone in 3) will be unhappy for it  ,
   saying " looks like a RACE label! ", 
  since romanization lose its merit:  written as it is pronounced!!!

Soobok
  

----- Original Message ----- 
From: <liana.ydisg@juno.com>
To: <lsb@postel.co.kr>
Cc: <liana.ydisg@juno.com>; <bthomson@fm-net.ne.jp>; <idn@ops.ietf.org>
Sent: Friday, August 17, 2001 6:06 PM
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee


> If you use another feature of the character not based on
> sound in addition to pronounciation, and fix it in your 
> case folding table, then  you will have one-to-one 
> mapping, and the language/semantic context is out
> of the table.   
> 
> Liana
> 
> On Fri, 17 Aug 2001 17:23:45 +0900 "Soobok Lee" <lsb@postel.co.kr>
> writes:
> > 
> > ----- Original Message ----- 
> > From: <liana.ydisg@juno.com>
> > To: <lsb@postel.co.kr>
> > Cc: <bthomson@fm-net.ne.jp>; <idn@ops.ietf.org>
> > Sent: Friday, August 17, 2001 4:54 PM
> > Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
> > 
> > 
> > > If Hangul mapped to Latin letters like Romaji and then
> > > add a number to select one Kanji among a few 
> > > homophones, can this be good enough to idnetify a Hanja
> > > name in DNS?
> > 
> >  some hangul  trailing jamos,
> > for example , di-geuth, hi-euth and ti-euth,
> >  have the same sound while their leading jamo 
> > have different sounds. You need some differenciating 
> > representation of trailing hangul jamos in romanizing hangeul and
> > That may cause some overheads...
> > 
> > Even a Hanja/Kanji/TC/SC letter often has multiple pronunciations 
> > in different words and so  multiple romanizations for a hanja 
> > letter are possible!!
> > 
> > IMHO,Pronunciation-based romanization on Hanja/Kanji/TC/SC 
> > should be performed in word/language context 
> > (not in individual unicode point context ) , but It's not achievable 
> > in DNS
> > which may have no language/script context (in .com) and often have 
> > no
> > word sematics in a label (single han letter label).
> > 
> > 
> > Soobok
> > 
> > > 
> > > The same question goes to Bruce Thomson:
> > > Can Romaji be revered back to Kanji-Kana sequece with
> > > near 100% rate (with or without case ending)?
> > > 
> > > Liana
> > > 
> > > On Fri, 17 Aug 2001 16:14:04 +0900 "Soobok Lee" <lsb@postel.co.kr>
> > > writes:
> > > > 
> > > > ----- Original Message ----- 
> > > > From: <liana.ydisg@juno.com>
> > > > To: <lsb@postel.co.kr>
> > > > Cc: <liana.ydisg@juno.com>; <bthomson@fm-net.ne.jp>; 
> > > > <idn@ops.ietf.org>
> > > > Sent: Friday, August 17, 2001 4:08 PM
> > > > Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
> > > > 
> > > > 
> > > > > It is correct, there will be no disambiguations in 
> > > > > DNS for anyone.  It has to be resolved at registration 
> > > > > time.  Then do you need Hanja in Domain name at all?
> > > > 
> > > > Yes, but rarely.
> > > > some japanese/chinese restaurants in SEOUL Korea
> > > >  have the primary name in Hanja(Kanji).
> > > > Most korean individuals/companies won't pay for
> > > > rarely used HANJA domains, I guess.
> > > > 
> > > > > Why? If Hanja names is only used for Chinese and Japanese,
> > > > > then how do Korean people separated from each other? 
> > > > > Are there many people with the same Hangul names?
> > > > 
> > > > Most Koreans have their TC-form fullnames. Many Korean
> > > > businesses , too. But they are not used so frequently
> > > > as hangul ones.
> > > > 
> > > > 
> > > > In my rough estimation, most frequent 5000 hangul personal full 
> > > > names 
> > > > form the set of distinct fullnames of about 90% of korean 
> > > > populations.
> > > > 
> > > > South Korean population reached  47,000,000 recently.
> > > > 
> > > > > 
> > > > > I have heard a law suit case here, that a Vietnanese vs. 
> > > > > another Vietnanese in the San Francisco area, both
> > > > > sides of the case and a witness of the case all have 
> > > > > exact the same name!  And they all need interpretations too.
> > > > > Imagine the headaches for the lawyers!
> > > > > 
> > > > 
> > > > :-))
> > > > 
> > > > Soobok
> > > > 
> > > > > Liana 
> > > > > 
> > > > > 
> > > > > On Fri, 17 Aug 2001 15:06:01 +0900 "Soobok Lee" 
> > <lsb@postel.co.kr>
> > > > > writes:
> > > > > > Hi, Liana
> > > > > > 
> > > > > > ----- Original Message ----- 
> > > > > > From: <liana.ydisg@juno.com>
> > > > > > > What happen when people read newspapers with Hangul 
> > > > > > > without Hanji such as it is in North Korean?  
> > > > > > > How to you get a Hanji through hangul if it is one-to-many 
> > 
> > > > > > > correspondence?
> > > > > > > 
> > > > > > Korean have been familiar with many hangeul homonyms that
> > > > > > share the same hangeul word but have different TC 
> > forms/meanings
> > > > > > and optionally different sounds (long or short vowel etc) .
> > > > > > Ordinary Korean can disambiguate them  only by the 
> > surrounding
> > > > > > semantical context (sentence or paragraph) in which they 
> > appear.
> > > > > > 
> > > > > > In DNS, we have no such contextual clue for disambiguations.
> > > > > > 
> > > > > > Soobok
> > > > > > 
> > > > > 
> > > > 
> > > 
> > 
> 




From owner-idn@ops.ietf.org  Fri Aug 17 05:23: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 FAA22248
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 05:23:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XfZY-000Cxl-00
	for idn-data@psg.com; Fri, 17 Aug 2001 02:05:44 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XfZX-000Cxf-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 02:05:43 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id A5424FFC11; Fri, 17 Aug 2001 17:07:06 +0800 (SGT)
Message-ID: <004c01c126fb$c63d08a0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>,
        "Kenny Huang" <huangk@alum.sinica.edu>, <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>, <dhc@dcrocker.net>
References: <000701c126ec$b2aeebf0$7900cfcb@asiainfra.com> <006c01c126f3$93796740$fb05738c@ncu.edu.tw>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 17 Aug 2001 17:05:34 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Dear Prof Tseng,

> Hi James,
>              I  think you can display these chinese characters in your
> system, so you can make
> the explaination , and  tell me the answer how to treat them ?
> TC(çµ±) , SC(ç»Ÿ)
> TC(é »),  SC(é¢‘)

These example stated at first level simplication of chinese by radical.
They are equivalent in most context of Chinese language so I think we
can both agree on this. And yes, it is not handled in current
normalization or nameprep.

How can we solve this? Many ways, each one with its pros and cons. I
will provide some suggestions but I am sure there are other ways:

1. Do it inside Normalization Form KC (Standard Track)

Speak to the Unicode Consortium, convience them that these two ideograph
are equivalent and put into NFKC. This will go directly into Nameprep so
long Unicode Consortium agree with it since Nameprep just uses the code
points from Unicode Consortium.

The people at Unicode Consortium would probably question if these
ideograph are equivalent in Kanji and Hanja or olden Vietnamese so we
need to prepare for that.

Pros: it would be part of Nameprep standard. And if NFKC accept this, it
would also solve in other I18N efforts in future, and not just IDN.

Cons: we need to go thru the review process in Unicode Consortium.

2. Do this "optional folding" pre-Nameprep (Informational based)

We would define these mappings within IETF, but published it as
Informational based as an optional folding for Chinese system only.

Pros: We do this within IETF with probably assistant from other group
for review. It also open Nameprep for localized foldings depending on
other set.

Cons: It may be difficult to determine what optional folding rules
should apply for a name. A Japanese (or Cyrillic) names could be entered
using GBK for example and which rules do we apply? And who has priority
to decide what folding mechanism? The registrant of the name or the user
of the name? Is ä¸­å›½.com a Chinese domain name "zhongguo.com" referring to
China.com or is it a Japanese domain name "chugoku.com" referring to
another place in Japan?

3. Do this in the zonefile (Best Current Practice?)

We would define these mappings in the zonefile for DNS and hence
irregardless how the user type it in, they will end up with the same
resource records.

Pros: It is an opertional issues for Chinese domain names. Registrant of
names would controll what is equivalent and what is not and that may be
defined as a policy on a per-zone basis.

Cons: There would be multiples entries in the zonefiles but they can be
solve by software implementation to generate these entries on loading.

Therefore, there are many solutions to the TC/SC problem. Which path to
take would depend on the tsconv author decision and the wg consensus. No
solution is perfect and it is all engineering trade-off.

Speaking for myself, I would love to see this get done in (1) because it
means it will solve it for other protocol, not just domain names in
future. But I am not sure how to address Unicode Consortium concern. I
am strongly against (2) approach because it will solve the problem by
creating other problems. Implementation experience have been proven to
be very headache to maintain and 'guess' optional foldings to be
applied. I believe (3) is a reasonable approach altho not a perfect
solution either.

> They are  the same chinese characters in pairs but they are coded with
> different  UNICODE .
> Does they are like the problems of   " fi " ?
> And  tell me  why  ï½�ã€€ï¼¡ã€€should  be mapped to ASCII  "a" or "A" ?

Problems like "fi" and "a" vs "A" are handled in Nameprep not because
IETF decided so, but rather the code points from Unicode Consortium have
these mappings/normalization.

IETF is not in the business to define codepoint because we are not
script or language expert. We leave it to other groups who have more
expertise and we reference their work. Thus, this question is most
appropriate ask to the Unicode Consortium, and not in this WG.

> I don't expect  this WG to solve all the equivalence of TC/SC. I just
want
> to know what is the guideline to reduce the confusing troubles in
nameprep ?
> Why so amall set of  PRC simplified quick-written scripts are not case
> folding problem ?

God knows I agree with you. :-)

But this is a question which this WG have no answer for since it
references it code points from other place.

-James Seng




From owner-idn@ops.ietf.org  Fri Aug 17 05:48: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 FAA22478
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 05:48:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XfxU-000DkX-00
	for idn-data@psg.com; Fri, 17 Aug 2001 02:30:28 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XfxT-000DkR-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 02:30:28 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP id 3152BFFC0D
	for <idn@ops.ietf.org>; Fri, 17 Aug 2001 17:31:49 +0800 (SGT)
Message-ID: <013a01c126ff$39ddaeb0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: <idn@ops.ietf.org>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 17 Aug 2001 17:30:17 +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

Pardon me:

> While I am incline to (a) (altho I have not hear any formal complain
> that multilingual naming is out-of-scope), (b) is an option I am
prepare
> to take if this is the consensus of the wg.

Correction: I have formal note (not really complain) from wg members
that multilingual naming is out-of-scope.

-James Seng




From owner-idn@ops.ietf.org  Fri Aug 17 09:14: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 JAA29176
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 09:14:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XjFl-000IzP-00
	for idn-data@psg.com; Fri, 17 Aug 2001 06:01:33 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XjFi-000IzG-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 06:01:32 -0700
Received: from test.ncu.edu.tw ([140.115.5.251])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f7HD6M705259;
	Fri, 17 Aug 2001 21:06:22 +0800 (CST)
Message-ID: <00e601c1271c$aaba7b00$fb05738c@ncu.edu.tw>
From: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: "James Seng/Personal" <James@Seng.cc>,
        "Kenny Huang" <huangk@alum.sinica.edu>, <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>, <dhc@dcrocker.net>
References: <000701c126ec$b2aeebf0$7900cfcb@asiainfra.com> <006c01c126f3$93796740$fb05738c@ncu.edu.tw> <004c01c126fb$c63d08a0$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 17 Aug 2001 21:01:00 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit


Dear Co-chair James :
          I  only point out  PRC simplified quick-written (è�‰æ›¸) characters,
these characters are exactly the same as traditional formal-written (æ¥·æ›¸)
characters , but they have different scripts font , so it is different in
UNICODE.  These characters can be quickly recognized by the small difference
in components (ç³¸),  (é �)  . In Taiwan , if we writte them quickly, it is
the form of  SC(ç»Ÿ) SC(é¢‘) , but big5 character set is similiar to Japanese
Kanji , it is the normal-written traditional scripts form .  So , Japan,
Korean , Taiwan has not use these  quick-written SC scripts .
          If you use windows outlook mail and you trust its correctness, you
can verified it by change the  format code type to any language:  SJIS ,
koren, big5, gb2312(that is GBK).  If it is not one of the character set ,
it will be displayed as an blank mark in SC(ç»Ÿ) SC(é¢‘) .   So,  people of
Japan , Korean can not get feelings of why some (not all) TC/SC  equivalence
is needed .
          1.The major assumption is based on a well normalized UNICODE , but
it is not true in CJK area, because people are use different code system(
gb, big5, SJIS, UNC-KR).
          2. You can not expect all people to change to UNICODE at one
night.
          3. Global TLD , like ML.COM  is  pre-mature , ML.jp Ml.tw, ML.cn
can be work in their own way, but ML.com based on unicode mixing them
together then produce  confusing status.
          4. IE had help VeriSign/NSI  to resolve  ML.com ,  the external
auto.search.msn.com server and laguage-tagged HTTP parameters can solve
these complexity easily.  In my feeling, the server auto.search.msn.com will
be  a special super ROOT of name server  in the furture . The situation is
happen .

         We discuss many things in this WG for the  reasons that we all
support DNS, but if the conflicts can not be solved and more hurts are
happened again over again in the  proposed IDN system .
         I can understand the difficulties of IDN WG,  but the major
problems are  based on some false assumptions , and so many nonsense
forbidden concepts are preassigned,  these will let DNS  become  too old to
act as a furture name system.

L.M.Tseng
> >              I  think you can display these chinese characters in your
> > system, so you can make
> > the explaination , and  tell me the answer how to treat them ?
> > TC(çµ±) , SC(ç»Ÿ)
> > TC(é »),  SC(é¢‘)
>
> These example stated at first level simplication of chinese by radical.
> They are equivalent in most context of Chinese language so I think we
> can both agree on this. And yes, it is not handled in current
> normalization or nameprep.
>
> How can we solve this? Many ways, each one with its pros and cons. I
> will provide some suggestions but I am sure there are other ways:
>
> 1. Do it inside Normalization Form KC (Standard Track)
>
> Speak to the Unicode Consortium, convience them that these two ideograph
> are equivalent and put into NFKC. This will go directly into Nameprep so
> long Unicode Consortium agree with it since Nameprep just uses the code
> points from Unicode Consortium.
>
> The people at Unicode Consortium would probably question if these
> ideograph are equivalent in Kanji and Hanja or olden Vietnamese so we
> need to prepare for that.
>
> Pros: it would be part of Nameprep standard. And if NFKC accept this, it
> would also solve in other I18N efforts in future, and not just IDN.
>
> Cons: we need to go thru the review process in Unicode Consortium.
>
> 2. Do this "optional folding" pre-Nameprep (Informational based)
>
> We would define these mappings within IETF, but published it as
> Informational based as an optional folding for Chinese system only.
>
> Pros: We do this within IETF with probably assistant from other group
> for review. It also open Nameprep for localized foldings depending on
> other set.
>
> Cons: It may be difficult to determine what optional folding rules
> should apply for a name. A Japanese (or Cyrillic) names could be entered
> using GBK for example and which rules do we apply? And who has priority
> to decide what folding mechanism? The registrant of the name or the user
> of the name? Is ä¸­å›½.com a Chinese domain name "zhongguo.com" referring to
> China.com or is it a Japanese domain name "chugoku.com" referring to
> another place in Japan?
>
> 3. Do this in the zonefile (Best Current Practice?)
>
> We would define these mappings in the zonefile for DNS and hence
> irregardless how the user type it in, they will end up with the same
> resource records.
>
> Pros: It is an opertional issues for Chinese domain names. Registrant of
> names would controll what is equivalent and what is not and that may be
> defined as a policy on a per-zone basis.
>
> Cons: There would be multiples entries in the zonefiles but they can be
> solve by software implementation to generate these entries on loading.
>
> Therefore, there are many solutions to the TC/SC problem. Which path to
> take would depend on the tsconv author decision and the wg consensus. No
> solution is perfect and it is all engineering trade-off.
>
> Speaking for myself, I would love to see this get done in (1) because it
> means it will solve it for other protocol, not just domain names in
> future. But I am not sure how to address Unicode Consortium concern. I
> am strongly against (2) approach because it will solve the problem by
> creating other problems. Implementation experience have been proven to
> be very headache to maintain and 'guess' optional foldings to be
> applied. I believe (3) is a reasonable approach altho not a perfect
> solution either.
>
> > They are  the same chinese characters in pairs but they are coded with
> > different  UNICODE .
> > Does they are like the problems of   " fi " ?
> > And  tell me  why  ï½�ã€€ï¼¡ã€€should  be mapped to ASCII  "a" or "A" ?
>
> Problems like "fi" and "a" vs "A" are handled in Nameprep not because
> IETF decided so, but rather the code points from Unicode Consortium have
> these mappings/normalization.
>
> IETF is not in the business to define codepoint because we are not
> script or language expert. We leave it to other groups who have more
> expertise and we reference their work. Thus, this question is most
> appropriate ask to the Unicode Consortium, and not in this WG.
>
> > I don't expect  this WG to solve all the equivalence of TC/SC. I just
> want
> > to know what is the guideline to reduce the confusing troubles in
> nameprep ?
> > Why so amall set of  PRC simplified quick-written scripts are not case
> > folding problem ?
>
> God knows I agree with you. :-)
>
> But this is a question which this WG have no answer for since it
> references it code points from other place.
>
> -James Seng
>
>
>




From owner-idn@ops.ietf.org  Fri Aug 17 09: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 JAA00576
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 09:33:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xjc7-000JVw-00
	for idn-data@psg.com; Fri, 17 Aug 2001 06:24:39 -0700
Received: from heron.verisign.com ([216.168.233.95])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xjc6-000JUe-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 06:24:39 -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 JAA08835
	for <idn@ops.ietf.org>; Fri, 17 Aug 2001 09:24:07 -0400 (EDT)
Received: by VSVAPOSTALGW1.prod.netsol.com with Internet Mail Service (5.5.2653.19)
	id <NP4FSFT0>; Fri, 17 Aug 2001 09:23:49 -0400
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60B84B0@vsvapostal3.prod.netsol.com>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'idn@ops.ietf.org'" <idn@ops.ietf.org>
Subject: [idn] Test Prefix for AMC-ACE-Z
Date: Fri, 17 Aug 2001 09:18:22 -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

The secondary IDN WG web page [1] includes a registry of prefixes for
testing ACEs.  Two prefixes are currently identified: "bq--" for RACE and
"dq--" for DUDE.  AMC-ACE-Z is gaining a measure of acceptance, but no
prefix has been identified for testing.

Has anyone been testing with a particular prefix?  If not, I'd like to
propose use of "za--" as a test prefix for AMC-ACE-Z.

<Scott/>

[1] http://www.i-d-n.net/



From owner-idn@ops.ietf.org  Fri Aug 17 09:54: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 JAA01983
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 09:54:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xjv5-000JzR-00
	for idn-data@psg.com; Fri, 17 Aug 2001 06:44:15 -0700
Received: from mail.paconline.net ([66.51.160.50])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xjv4-000JzL-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 06:44: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; Fri, 17 Aug 2001 06:55:23 -0700
Message-ID: <00c701c12723$ebd618e0$d43f7018@mtag1.on.home.com>
From: "ben" <ben@cc-www.com>
To: "Bill Manning" <bmanning@ISI.EDU>, "James Seng/Personal" <James@Seng.cc>
Cc: <idn@ops.ietf.org>
References: <200108161823.f7GINLU08493@zed.isi.edu>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 17 Aug 2001 09:52:56 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi James/Bill,

> While I'll leave Eric to answer that question for himself,
> I am left cold by your attitude regarding IETF participation
> and consenses building. Until you are willing to learn from
> others and have responsible dialog, it is my opinion that
> you will not gain support for your flawed ideas.
> But, since you don't care about other registries, interoperability
> is not an issue... ergo, its not an IETF issue, your SCS is a
closed,
> propriatary solution.  It will never be a standard.
>

I have formally submitted my draft.  As James has suggested, I will
try to build up support off-line before I bring my "Supreme CDN
system" back to the public discussion.

I truly do want to apologize to the registries for saying stupid
things like "I don't care about the registries... I only care about
myself...".  I do want to learn how to build consenses as I am
starting to understand what interoperability is all about and the
importance of it.  I will email people privately to get support and I
hope that they can see beyond my past cocky attitude and look at my
idea for what it is worth.  With all humblenss, my idea is not only
not flawed, but if you take the time to understand it, you will find
that it indeed can be applied to solve many problems and issues we
have with CDNs.  I did not call it a Supreme for no reason.

I had a bad attitude... but my intentions had always been good.

Thanks
Ben Chan











From owner-idn@ops.ietf.org  Fri Aug 17 09:58: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 JAA02194
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 09:58:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xk1K-000K8e-00
	for idn-data@psg.com; Fri, 17 Aug 2001 06:50:42 -0700
Received: from ns1.ar.com ([63.194.205.74] helo=mail.ar.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xk1K-000K8X-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 06:50:42 -0700
Received: from loki (IDENT:wessorh@loki [10.10.10.88])
	by mail.ar.com (8.11.2/8.11.2) with ESMTP id f7HDodr22004;
	Fri, 17 Aug 2001 06:50:39 -0700
Date: Fri, 17 Aug 2001 06:50:39 -0700 (PDT)
From: Rick H Wesson <wessorh@ar.com>
To: James Seng/Personal <James@Seng.cc>
cc: <idn@ops.ietf.org>
Subject: [idn] Meeting Minutes?
Message-ID: <Pine.LNX.4.30.0108170648050.21220-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


James,

As chair of this wg, when do you expect to post the minutes. Quite a bit
of discussion is taking place my attendees for the last IETF, and those
that didn't attend need to read what happened.

please post the minutes ASAP.

Please post a note describing our next steps in the evolution of the idn
working group.

-rick





From owner-idn@ops.ietf.org  Fri Aug 17 10:32: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 KAA03566
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 10:32:21 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XkUV-000Kyl-00
	for idn-data@psg.com; Fri, 17 Aug 2001 07:20:51 -0700
Received: from mailout6-1.nyroc.rr.com ([24.92.226.177] helo=mailout6.nyroc.rr.com)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XkUU-000Kyf-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 07:20:50 -0700
Received: from fwbm8 (roc-24-93-29-84.rochester.rr.com [24.93.29.84])
	by mailout6.nyroc.rr.com (8.11.5/Road Runner 1.12) with SMTP id f7HEKnb02484
	for <idn@ops.ietf.org>; Fri, 17 Aug 2001 10:20:49 -0400 (EDT)
Message-ID: <00bd01c12727$4c7c31e0$541d5d18@rochester.rr.com>
From: "Suzanne Topping" <stopping@rochester.rr.com>
To: <idn@ops.ietf.org>
References: <20010816.222200.-746899.10.liana.ydisg@juno.com> <053d01c126e1$6d432aa0$dd00a8c0@jamessonyvaio> <001b01c126e4$2b745dd0$4607e29f@xiaodonglee> <05f401c126eb$c344f190$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 17 Aug 2001 10:17:07 -0400
Organization: Localization Unlimited
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


----- Original Message -----
From: "James Seng/Personal" <James@Seng.cc>

> While there is an desire to solve 100% of the users problem today, all
> developments started with one small step at a time. Without solving the
> first 10%, we wont know what the next 10% problem. This wg is not the
> first nor will be the last one to solve the whole I18N problem. It is
> one of the puzzle piece for the IETF and there are many other puzzle to
> solve in future. So lets not put too much task upon ourselves.

This is not the only issue which is beyond the initial scope of the WG. Is
there a mechanism in place for putting these issues into a holding bin for
later work? IDN is sure to be an evolving system. The first pass will be
just that; the first. Not the final. We have to look at this evolution as a
phased event, and we won't all be happy with the first iteration.

Perhaps if people felt more confident that a path forward exists, and knew
the process for working within it, focus could be better aimed at what needs
to be dealt with immediately. James, can you please outline the WGs method
or plan for phasing in expanded levels of support? Does such a plan exist?

Suzanne Topping
BizWonk Inc.
stopping@bizwonk.com




From owner-idn@ops.ietf.org  Fri Aug 17 14:16: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 OAA11204
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 14:16:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xnsf-0000LS-00
	for idn-data@psg.com; Fri, 17 Aug 2001 10:58:01 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xnse-0000LM-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 10:58:00 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1Tops8odjHDCz8oi8+TygNTA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GC3HR44N; Fri, 17 Aug 2001 13:57:13 EDT
To: lsb@postel.co.kr
Cc: liana.ydisg@juno.com, bthomson@fm-net.ne.jp, idn@ops.ietf.org
Date: Fri, 17 Aug 2001 11:14:24 -0700
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Message-ID: <20010817.111428.-985185.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-48,50-225
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

This is the core of the problem.  People want to use their
own script for names, and there will be character conflict
just as any symbol system, and this is the feature 
Internetionalization wanted, isn't this correct?   Let us
use your example for the solution and study the trade offs.

1. There should be:

>   1) in Korea:  kuk
>   2) in Japan:  kuni, kok, ...
>   3) in China:  kuo, ....

> If you designate an unique romanization sequence in 3)  for han 
> 'nation',
>   1) and 2) and even someone in 3) will be unhappy for it  ,

So we shall designate 3 mapping tables!  And remember, 
this is character code, not word codes.  When you do 
registration, the use is "zhongguo"  <china> and the registration 
system should do the Unicode checking for the Unicode
string is taken by Cinese already.  But this does not 
exclude a Korean name says: <KoreanChinaTrading>, 
since the convention for Chinese to to this is 
<ChinaKoreanTrading> so you will have 
>   1) in Korea:  kuk
>   2) in Japan:  kuni, kok, ...
>   3) in China:  kuo, ....
and Unicode <KoreanChinaTrading>.

The naming convention for names are quite different among
Chinese, Japanese and Korean using Kanji.  Similarly we
can look at sirnames to tell people's origins in US, and it is 
more then 95% correct.  The registration process is to catch 
the other say 5% name conflict.  

The three mapping tables are similar with Latin upper-to-lower
case folding, only larger. So for Korean it has five columns:

Unicode		Unicode 	KSC code 	KSC code 	StepCoded
Hangul		Hanja		Hanja		Hangul		Romaji

It is certain the Hanja will have longer list than Hangul. 
So there will be 2 Hangul to 1 Hanja, and your IDNA can decide
which one to use, not the [nameprep].  The StepCode is
concatenation of Romaji+digit and the author has to make it
one-to-one within this kro- table.

Liana

On Fri, 17 Aug 2001 17:53:58 +0900 "Soobok Lee" <lsb@postel.co.kr>
writes:
> For example,
>  Han letter 'nation' is pronounced :
>   1) in Korea:  kuk
>   2) in Japan:  kuni, kok, ...
>   3) in China:  kuo, ....
> If you designate an unique romanization sequence in 3)  for han 
> 'nation',
>   1) and 2) and even someone in 3) will be unhappy for it  ,
>    saying " looks like a RACE label! ", 
>   since romanization lose its merit:  written as it is pronounced!!!
> 
> Soobok
>   
> 
> ----- Original Message ----- 
> From: <liana.ydisg@juno.com>
> To: <lsb@postel.co.kr>
> Cc: <liana.ydisg@juno.com>; <bthomson@fm-net.ne.jp>; 
> <idn@ops.ietf.org>
> Sent: Friday, August 17, 2001 6:06 PM
> Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
> 
> 
> > If you use another feature of the character not based on
> > sound in addition to pronounciation, and fix it in your 
> > case folding table, then  you will have one-to-one 
> > mapping, and the language/semantic context is out
> > of the table.   
> > 
> > Liana
> > 
> > On Fri, 17 Aug 2001 17:23:45 +0900 "Soobok Lee" <lsb@postel.co.kr>
> > writes:
> > > 
> > > ----- Original Message ----- 
> > > From: <liana.ydisg@juno.com>
> > > To: <lsb@postel.co.kr>
> > > Cc: <bthomson@fm-net.ne.jp>; <idn@ops.ietf.org>
> > > Sent: Friday, August 17, 2001 4:54 PM
> > > Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
> > > 
> > > 
> > > > If Hangul mapped to Latin letters like Romaji and then
> > > > add a number to select one Kanji among a few 
> > > > homophones, can this be good enough to idnetify a Hanja
> > > > name in DNS?
> > > 
> > >  some hangul  trailing jamos,
> > > for example , di-geuth, hi-euth and ti-euth,
> > >  have the same sound while their leading jamo 
> > > have different sounds. You need some differenciating 
> > > representation of trailing hangul jamos in romanizing hangeul 
> and
> > > That may cause some overheads...
> > > 
> > > Even a Hanja/Kanji/TC/SC letter often has multiple 
> pronunciations 
> > > in different words and so  multiple romanizations for a hanja 
> > > letter are possible!!
> > > 
> > > IMHO,Pronunciation-based romanization on Hanja/Kanji/TC/SC 
> > > should be performed in word/language context 
> > > (not in individual unicode point context ) , but It's not 
> achievable 
> > > in DNS
> > > which may have no language/script context (in .com) and often 
> have 
> > > no
> > > word sematics in a label (single han letter label).
> > > 
> > > 
> > > Soobok
> > > 
> > > > 
> > > > The same question goes to Bruce Thomson:
> > > > Can Romaji be revered back to Kanji-Kana sequece with
> > > > near 100% rate (with or without case ending)?
> > > > 
> > > > Liana
> > > > 
> > > > On Fri, 17 Aug 2001 16:14:04 +0900 "Soobok Lee" 
> <lsb@postel.co.kr>
> > > > writes:
> > > > > 
> > > > > ----- Original Message ----- 
> > > > > From: <liana.ydisg@juno.com>
> > > > > To: <lsb@postel.co.kr>
> > > > > Cc: <liana.ydisg@juno.com>; <bthomson@fm-net.ne.jp>; 
> > > > > <idn@ops.ietf.org>
> > > > > Sent: Friday, August 17, 2001 4:08 PM
> > > > > Subject: Re: [idn] Question for the Kanji & Hanja 
> cognosentee
> > > > > 
> > > > > 
> > > > > > It is correct, there will be no disambiguations in 
> > > > > > DNS for anyone.  It has to be resolved at registration 
> > > > > > time.  Then do you need Hanja in Domain name at all?
> > > > > 
> > > > > Yes, but rarely.
> > > > > some japanese/chinese restaurants in SEOUL Korea
> > > > >  have the primary name in Hanja(Kanji).
> > > > > Most korean individuals/companies won't pay for
> > > > > rarely used HANJA domains, I guess.
> > > > > 
> > > > > > Why? If Hanja names is only used for Chinese and Japanese,
> > > > > > then how do Korean people separated from each other? 
> > > > > > Are there many people with the same Hangul names?
> > > > > 
> > > > > Most Koreans have their TC-form fullnames. Many Korean
> > > > > businesses , too. But they are not used so frequently
> > > > > as hangul ones.
> > > > > 
> > > > > 
> > > > > In my rough estimation, most frequent 5000 hangul personal 
> full 
> > > > > names 
> > > > > form the set of distinct fullnames of about 90% of korean 
> > > > > populations.
> > > > > 
> > > > > South Korean population reached  47,000,000 recently.
> > > > > 
> > > > > > 
> > > > > > I have heard a law suit case here, that a Vietnanese vs. 
> > > > > > another Vietnanese in the San Francisco area, both
> > > > > > sides of the case and a witness of the case all have 
> > > > > > exact the same name!  And they all need interpretations 
> too.
> > > > > > Imagine the headaches for the lawyers!
> > > > > > 
> > > > > 
> > > > > :-))
> > > > > 
> > > > > Soobok
> > > > > 
> > > > > > Liana 
> > > > > > 
> > > > > > 
> > > > > > On Fri, 17 Aug 2001 15:06:01 +0900 "Soobok Lee" 
> > > <lsb@postel.co.kr>
> > > > > > writes:
> > > > > > > Hi, Liana
> > > > > > > 
> > > > > > > ----- Original Message ----- 
> > > > > > > From: <liana.ydisg@juno.com>
> > > > > > > > What happen when people read newspapers with Hangul 
> > > > > > > > without Hanji such as it is in North Korean?  
> > > > > > > > How to you get a Hanji through hangul if it is 
> one-to-many 
> > > 
> > > > > > > > correspondence?
> > > > > > > > 
> > > > > > > Korean have been familiar with many hangeul homonyms 
> that
> > > > > > > share the same hangeul word but have different TC 
> > > forms/meanings
> > > > > > > and optionally different sounds (long or short vowel 
> etc) .
> > > > > > > Ordinary Korean can disambiguate them  only by the 
> > > surrounding
> > > > > > > semantical context (sentence or paragraph) in which they 
> 
> > > appear.
> > > > > > > 
> > > > > > > In DNS, we have no such contextual clue for 
> disambiguations.
> > > > > > > 
> > > > > > > Soobok
> > > > > > > 
> > > > > > 
> > > > > 
> > > > 
> > > 
> > 
> 
> 



From owner-idn@ops.ietf.org  Fri Aug 17 15:28: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 PAA13630
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 15:28:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xp8p-00027g-00
	for idn-data@psg.com; Fri, 17 Aug 2001 12:18:47 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xp8o-00027a-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 12:18:46 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1TmMysur2jVLYApO8Q5bHdtw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GC3NDVPV; Fri, 17 Aug 2001 15:17:55 EDT
To: James@Seng.cc
Cc: tsenglm@cc.ncu.edu.tw, huangk@alum.sinica.edu, liana.ydisg@juno.com,
        idn@ops.ietf.org, dhc@dcrocker.net
Date: Fri, 17 Aug 2001 12:35:10 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010817.123514.-985185.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-42,44-172
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 and all:

After some sleep, I am ready to type more.

I am proposing a [nameprep] case folding table for Chinese
where 
+ means concatenation, 
Px means xth radical in Latin letters.

zho-
Unicode    	Unicode    Big5      	GB	StepCode
TC	   	SC	    TC         	SC       Pinyin+tone+P1+P2

So the TC to SC mapping is embeded in, and IDNA can 
decide on how long the StepCode is needed to register
a unique name and the pre-registered form is kept at 
zonefile level. So the name can be over 63 octect limit without
burden other protocols. 

For Japanese, replace Pinyin with Romaji.  So there are
cases that one Unicode Kanji will have 3-4 Romaji entries.
(This is allowed for zho- table too.) Thus:

jap-
Unicode    	JIS		StepCode
Kana		Kana		Kunrei 
Kanji   		Kanji	   	Kunrei +P1 Kunrei +P2 Kunrei

Where Romaji shall use Kunrei system since it is the adopted
system by Unicode naming.

For IDNA processing: using radicals code in pre-registered
form, and register the short form (by truncate radical code) to keep
the name under 63-octect. 
	
I do not suggest Han characters for Vietnanese, since they seem
happy with the script using many tones.  While tone mapping can
be done in a similar way with Arabic.   But the option is open
for Vietnanese, since they can create a similar mapping table if
they can show an official adoption for a Romanization mapping.

Liana Ye

On Fri, 17 Aug 2001 17:05:34 +0800 "James Seng/Personal" <James@Seng.cc>
writes:
> Dear Prof Tseng,
> 
> > Hi James,
> >              I  think you can display these chinese characters in 
> your
> > system, so you can make
> > the explaination , and  tell me the answer how to treat them ?
> > TC(çµ? , SC(ç»?
> > TC(é ?,  SC(é¢?
> 
> These example stated at first level simplication of chinese by 
> radical.
> They are equivalent in most context of Chinese language so I think we
> can both agree on this. And yes, it is not handled in current
> normalization or nameprep.
> 
> How can we solve this? Many ways, each one with its pros and cons. I
> will provide some suggestions but I am sure there are other ways:
> 
> 1. Do it inside Normalization Form KC (Standard Track)
> 
> Speak to the Unicode Consortium, convience them that these two 
> ideograph
> are equivalent and put into NFKC. This will go directly into 
> Nameprep so
> long Unicode Consortium agree with it since Nameprep just uses the 
> code
> points from Unicode Consortium.
> 
> The people at Unicode Consortium would probably question if these
> ideograph are equivalent in Kanji and Hanja or olden Vietnamese so we
> need to prepare for that.
> 
> Pros: it would be part of Nameprep standard. And if NFKC accept 
> this, it
> would also solve in other I18N efforts in future, and not just IDN.
> 
> Cons: we need to go thru the review process in Unicode Consortium.
> 
> 2. Do this "optional folding" pre-Nameprep (Informational based)
> 
> We would define these mappings within IETF, but published it as
> Informational based as an optional folding for Chinese system only.
> 
> Pros: We do this within IETF with probably assistant from other group
> for review. It also open Nameprep for localized foldings depending on
> other set.
> 
> Cons: It may be difficult to determine what optional folding rules
> should apply for a name. A Japanese (or Cyrillic) names could be 
> entered
> using GBK for example and which rules do we apply? And who has 
> priority
> to decide what folding mechanism? The registrant of the name or the 
> user
> of the name? Is ä¸­å›½.com a Chinese domain name "zhongguo.com" 
> referring to
> China.com or is it a Japanese domain name "chugoku.com" referring to
> another place in Japan?
> 
> 3. Do this in the zonefile (Best Current Practice?)
> 
> We would define these mappings in the zonefile for DNS and hence
> irregardless how the user type it in, they will end up with the same
> resource records.
> 
> Pros: It is an opertional issues for Chinese domain names. 
> Registrant of
> names would controll what is equivalent and what is not and that may 
> be
> defined as a policy on a per-zone basis.
> 
> Cons: There would be multiples entries in the zonefiles but they can 
> be
> solve by software implementation to generate these entries on 
> loading.
> 
> Therefore, there are many solutions to the TC/SC problem. Which path 
> to
> take would depend on the tsconv author decision and the wg 
> consensus. No
> solution is perfect and it is all engineering trade-off.
> 
> Speaking for myself, I would love to see this get done in (1) 
> because it
> means it will solve it for other protocol, not just domain names in
> future. But I am not sure how to address Unicode Consortium concern. 
> I
> am strongly against (2) approach because it will solve the problem by
> creating other problems. Implementation experience have been proven 
> to
> be very headache to maintain and 'guess' optional foldings to be
> applied. I believe (3) is a reasonable approach altho not a perfect
> solution either.
> 
> > They are  the same chinese characters in pairs but they are coded 
> with
> > different  UNICODE .
> > Does they are like the problems of   " fi " ?
> > And  tell me  why  ï½�ã€€ï¼¡ã€€should  be mapped to ASCII  "a" or 
> "A" ?
> 
> Problems like "fi" and "a" vs "A" are handled in Nameprep not because
> IETF decided so, but rather the code points from Unicode Consortium 
> have
> these mappings/normalization.
> 
> IETF is not in the business to define codepoint because we are not
> script or language expert. We leave it to other groups who have more
> expertise and we reference their work. Thus, this question is most
> appropriate ask to the Unicode Consortium, and not in this WG.
> 
> > I don't expect  this WG to solve all the equivalence of TC/SC. I 
> just
> want
> > to know what is the guideline to reduce the confusing troubles in
> nameprep ?
> > Why so amall set of  PRC simplified quick-written scripts are not 
> case
> > folding problem ?
> 
> God knows I agree with you. :-)
> 
> But this is a question which this WG have no answer for since it
> references it code points from other place.
> 
> -James Seng
> 



From owner-idn@ops.ietf.org  Fri Aug 17 21:11: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 VAA17853
	for <idn-archive@lists.ietf.org>; Fri, 17 Aug 2001 21:11:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15XuG4-00071O-00
	for idn-data@psg.com; Fri, 17 Aug 2001 17:46:36 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15XuG3-00071I-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 17:46:35 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1TIvJdOeYf0PPYY9U5p7eMOw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GC386LFW; Fri, 17 Aug 2001 20:45:59 EDT
To: phoffman@imc.org
Cc: idn@ops.ietf.org, James@Seng.cc
Date: Fri, 17 Aug 2001 18:03:23 -0700
Subject: [idn] amending [IDNA]?
Message-ID: <20010817.180326.-726309.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, Paul:

I suggest the following procedure specification 
adds to [IDNA], this is only an idea, while I have no 
intention to put proper words in the document.

[IDNA] is the component of internetionalization of 
Domain Name system. It contains procedures preparing
localized domain name representation for DNS and 
supply display representation for local standard 
according to DNS registered hostnames.

The IDN-label protocol is:

idn-label(input, tag-file, input-std, zonefile, idn-name)
{
  tag = find-tag(input, tag-file, input-std);
  switch (tag)
	{
	case USASCII : return(input);  /* a legal DNS string*/
	case NIL: idn-name= 
		uni-compress(input, UNICODE, DEFAULT-ACE);
		return strcat(DEFAULT-ACE, idn-name);
	default:
	 idn-folding(input, input-std, tag, USASCII, output-list);
	 record-label(input, output-list, zonefile, tag);
	 if idn-label-length(output-list) >= MaxLabelLength
	 {	 
		record-label(input, output-list, zonefile, tag);
		idn-truncate-label(output-list, tag);
	 }
	 idn-label-concat(output-list, idn-name);
	 return  strcat(tag, idn-name);
	} 

The idn-display protocol is:

idn-display-code(input, local-std, zonefile, display-string)
{
  display-string = NIL;
  search-zone(input, zonefile, local-std, display-string);
  if display-string 
	return display-string;

  tag = find-tag (input, tag-file, USASCII);
  switch (tag)
	{
	case USASCII : return(input);  /* a legal DNS string*/
	case NIL: return(input); /* legacy name */
	case DEFAULT-TAG: 
		local-std = UNICODE;
		uni-decompress(input, display-string)
		return display-string;
	default:
	 idn-folding(input, USASCII, tag, local-std, display-string);
	 if length(inupt) >= MaxLabelLength)  /* truncated */
	 	idn-request-fullname(input, output-list, host1, host2);
	 return display-string;
	} 


[nameprep] shall be the host for and only deal with

 idn-folding(input, in-std, tag, out-std, out-list)

for case folding table lookups, and leave exclusion list to be 
checked by idn-label procedure  within a tagged Unicode block.

I am looking forward for your comments.

Liana Ye



From owner-idn@ops.ietf.org  Sat Aug 18 00:05: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 AAA21155
	for <idn-archive@lists.ietf.org>; Sat, 18 Aug 2001 00:05:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Xx8J-0008sv-00
	for idn-data@psg.com; Fri, 17 Aug 2001 20:50:47 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Xx8I-0008sp-00
	for idn@ops.ietf.org; Fri, 17 Aug 2001 20:50:47 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1Tpo+efdzZdwcbChtnoi/pRQ==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GC4KPEYD; Fri, 17 Aug 2001 23:49:57 EDT
To: phoffman@imc.org
Cc: idn@ops.ietf.org, James@Seng.cc
Date: Fri, 17 Aug 2001 21:07:12 -0700
Subject: Re: [idn] amending [IDNA]?
Message-ID: <20010817.210718.-794157.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

 A mistake is in previous idn-label. This one shall
replace it.  

Liana

idn-label(input, tag-file, input-std, zonefile, idn-name)
{
  tag = find-tag(input, tag-file, input-std);
  switch (tag)
	{
	case USASCII : return(input);  /* a legal DNS string*/
	case NIL: idn-name= 
		uni-compress(input, UNICODE, DEFAULT-ACE);
		return strcat(DEFAULT-ACE, idn-name);
	default:
	 idn-folding(input, input-std, tag, USASCII, output-list);
	 if idn-label-length(output-list) >= MaxLabelLength
	 {	 
		record-label(input, output-list, zonefile, tag);
		idn-truncate-label(output-list, tag);
	 }
	 idn-label-concat(output-list, idn-name);
	 return  strcat(tag, idn-name);
	} 



From owner-idn@ops.ietf.org  Sat Aug 18 05: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 FAA10079
	for <idn-archive@lists.ietf.org>; Sat, 18 Aug 2001 05:21:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Y26k-000Cze-00
	for idn-data@psg.com; Sat, 18 Aug 2001 02:09:30 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.195.38])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Y26j-000CzM-00
	for idn@ops.ietf.org; Sat, 18 Aug 2001 02:09:29 -0700
Received: from enoshima (i205012.ppp.asahi-net.or.jp [61.125.205.12])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id SAA19476;
	Sat, 18 Aug 2001 18:08:23 +0900 (JST)
Message-Id: <4.2.0.58.J.20010817171904.0394f840@133.27.195.38>
X-Sender: duerst@133.27.195.38
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 17 Aug 2001 17:21:35 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, "Soobok Lee" <lsb@postel.co.kr>,
        <liana.ydisg@juno.com>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Cc: <liana.ydisg@juno.com>, <bthomson@fm-net.ne.jp>, <idn@ops.ietf.org>
In-Reply-To: <018601c126f1$24d076a0$ed1bd9d2@postel.co.kr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 16:49 01/08/17 +0900, Soobok Lee wrote:
>Two corrections:
> > Yes, but rarely.
> > some japanese/chinese restaurants in SEOUL Korea
> >  have the primary name in Hanja(Kanji).
> > Most korean individuals/companies won't pay for
> > rarely used HANJA domains, I guess.
>
>That may change near future..
>
>Recently, Korean Goverments began to encourage
>HanJa education/Hanja Usages in addition to English ones.
>You know the economic block of Eastern Asia is rapidly
>expanding its power... :-)

I think the trend for more Hangul or more Hanja comes
and goes like waves in Korea. There are actually similar
waves in North Korea, but of course with different
amplitutde and wavelength.



> > In my rough estimation, most frequent 5000 hangul personal full names
> > form the set of distinct fullnames of about 90% of korean populations.
> >
>Oh my mistake.  5000 ====> 100,000.
>
>100,000 distinct fullnames, and 5,000 distinct given(first) names acount
>for 90% of individual names of south korean population,based on the personal
>study on 600,000 samples of korean fullnames.

Do you have the numbers for family names also? I guess it must
be something like "100 most frequent family names cover 99% of the population",
but it would be nice to know exact figures based on such a large sample.


Regards,    Martin.



From owner-idn@ops.ietf.org  Sat Aug 18 05:21: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 FAA10106
	for <idn-archive@lists.ietf.org>; Sat, 18 Aug 2001 05:21:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Y26c-000CzC-00
	for idn-data@psg.com; Sat, 18 Aug 2001 02:09:22 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.195.38])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Y26b-000Cz4-00
	for idn@ops.ietf.org; Sat, 18 Aug 2001 02:09:21 -0700
Received: from enoshima (i205012.ppp.asahi-net.or.jp [61.125.205.12])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id SAA19473;
	Sat, 18 Aug 2001 18:08:22 +0900 (JST)
Message-Id: <4.2.0.58.J.20010817170939.039bbe40@133.27.195.38>
X-Sender: duerst@133.27.195.38
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 17 Aug 2001 17:11:59 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, "Bruce Thomson" <bthomson@fm-net.ne.jp>,
        <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
In-Reply-To: <053d01c126d7$559aff90$ec1bd9d2@temp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 13:44 01/08/17 +0900, Soobok Lee wrote:
>I forgot to put the following comment:
>
>   In Korea, unlike Japan,
>     verbal & written communication  hardly use TC-form korean words.
>    Korean people use the TC-forms of their company names or personal names
>    only when they communicate to Japanese or chinese partners.

This may have changed recently, but only a few years ago,
when you got a name card from a Korean, it was either almost
completely in Hanja (traditional ideographs), or almost
completely in Hangul. I would say the probability was about
50/50.

Soobok, it would be nice if you could do a count through the
stack of namecards that you probably have, and tell us what
the proportions are nowadays. (replies from others of course
also very welcome).

Regards,   Martin.



From owner-idn@ops.ietf.org  Sat Aug 18 05:21: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 FAA10118
	for <idn-archive@lists.ietf.org>; Sat, 18 Aug 2001 05:21:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Y26f-000CzJ-00
	for idn-data@psg.com; Sat, 18 Aug 2001 02:09:25 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.195.38])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Y26e-000Cz6-00
	for idn@ops.ietf.org; Sat, 18 Aug 2001 02:09:24 -0700
Received: from enoshima (i205012.ppp.asahi-net.or.jp [61.125.205.12])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id SAA19479;
	Sat, 18 Aug 2001 18:08:25 +0900 (JST)
Message-Id: <4.2.0.58.J.20010817172155.03422bf0@133.27.195.38>
X-Sender: duerst@133.27.195.38
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 17 Aug 2001 17:24:10 +0900
To: liana.ydisg@juno.com, lsb@postel.co.kr
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Cc: bthomson@fm-net.ne.jp, idn@ops.ietf.org
In-Reply-To: <20010817.005432.-746899.15.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 00:54 01/08/17 -0700, liana.ydisg@juno.com wrote:
>If Hangul mapped to Latin letters like Romaji and then
>add a number to select one Kanji among a few
>homophones, can this be good enough to idnetify a Hanja
>name in DNS?
>
>The same question goes to Bruce Thomson:
>Can Romaji be revered back to Kanji-Kana sequece with
>near 100% rate (with or without case ending)?

Not at all. There are some cases where you can guess,
and there are cases where even guessing won't really
help. Of course adding a number or so always will be
able to do disambiguation, but one would essentially
have to use a separate number per kanji, because in
Japanese, new readings can be invented anytime.

Regards,  Martin.



From owner-idn@ops.ietf.org  Sat Aug 18 08:22: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 IAA11391
	for <idn-archive@lists.ietf.org>; Sat, 18 Aug 2001 08:22:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Y50a-000Euf-00
	for idn-data@psg.com; Sat, 18 Aug 2001 05:15:20 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Y50Z-000EuW-00
	for idn@ops.ietf.org; Sat, 18 Aug 2001 05:15: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 VAA32590;
	Sat, 18 Aug 2001 21:15:04 +0900
Message-ID: <08a901c127de$a2544820$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>, "Martin Duerst" <duerst@w3.org>
References: <4.2.0.58.J.20010817170939.039bbe40@133.27.195.38>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Date: Sat, 18 Aug 2001 21:09:28 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; "Bruce Thomson" <bthomson@fm-net.ne.jp>; <idn@ops.ietf.org>
Sent: Friday, August 17, 2001 5:11 PM
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee


> At 13:44 01/08/17 +0900, Soobok Lee wrote:
> >I forgot to put the following comment:
> >
> >   In Korea, unlike Japan,
> >     verbal & written communication  hardly use TC-form korean words.
> >    Korean people use the TC-forms of their company names or personal names
> >    only when they communicate to Japanese or chinese partners.
> 
> This may have changed recently, but only a few years ago,
> when you got a name card from a Korean, it was either almost
> completely in Hanja (traditional ideographs), or almost
> completely in Hangul. I would say the probability was about
> 50/50.

I have engineering backgrounds , but
many korean business men, especially responsible for
asian regions, have their two-sided namecards ,
one side in full ENGLISH, the other side in full Traditional
ideographs. For domestic partners, they prepare 
another set of namecards in Hangeul/English (no TC).

If you  got full Hangeul namecards from your korean partners,
they might have no time to prepare TC ones  for you.. :-)

> 
> Soobok, it would be nice if you could do a count through the
> stack of namecards that you probably have, and tell us what
> the proportions are nowadays. (replies from others of course
> also very welcome).
> 

I have  only  1  English/TC namecard which i got from a
partner working for a multinational corporation in korea.

Soobok

> Regards,   Martin.
> 




From owner-idn@ops.ietf.org  Sat Aug 18 08:41: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 IAA11652
	for <idn-archive@lists.ietf.org>; Sat, 18 Aug 2001 08:41:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15Y5I8-000FPI-00
	for idn-data@psg.com; Sat, 18 Aug 2001 05:33:28 -0700
Received: from bora.postel.to
	([164.124.123.206] helo=bora.lsb.org ident=root)
	by psg.com with esmtp (Exim 3.31 #1)
	id 15Y5I7-000FP9-00
	for idn@ops.ietf.org; Sat, 18 Aug 2001 05:33: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 VAA05767;
	Sat, 18 Aug 2001 21:32:56 +0900
Message-ID: <08af01c127e1$216f4630$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <liana.ydisg@juno.com>, "Martin Duerst" <duerst@w3.org>
Cc: <liana.ydisg@juno.com>, <bthomson@fm-net.ne.jp>, <idn@ops.ietf.org>
References: <4.2.0.58.J.20010817171904.0394f840@133.27.195.38>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Date: Sat, 18 Aug 2001 21:27:21 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; "Soobok Lee" <lsb@postel.co.kr>; <liana.ydisg@juno.com>
Cc: <liana.ydisg@juno.com>; <bthomson@fm-net.ne.jp>; <idn@ops.ietf.org>
Sent: Friday, August 17, 2001 5:21 PM
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee


> At 16:49 01/08/17 +0900, Soobok Lee wrote:
> >Two corrections:
> > > Yes, but rarely.
> > > some japanese/chinese restaurants in SEOUL Korea
> > >  have the primary name in Hanja(Kanji).
> > > Most korean individuals/companies won't pay for
> > > rarely used HANJA domains, I guess.
> >
> >That may change near future..
> >
> >Recently, Korean Goverments began to encourage
> >HanJa education/Hanja Usages in addition to English ones.
> >You know the economic block of Eastern Asia is rapidly
> >expanding its power... :-)
> 
> I think the trend for more Hangul or more Hanja comes
> and goes like waves in Korea. There are actually similar
> waves in North Korea, but of course with different
> amplitutde and wavelength.
> 

I agree.

> 
> 
> > > In my rough estimation, most frequent 5000 hangul personal full names
> > > form the set of distinct fullnames of about 90% of korean populations.
> > >
> >Oh my mistake.  5000 ====> 100,000.
> >
> >100,000 distinct fullnames, and 5,000 distinct given(first) names acount
> >for 90% of individual names of south korean population,based on the personal
> >study on 600,000 samples of korean fullnames.
> 
> Do you have the numbers for family names also? I guess it must
> be something like "100 most frequent family names cover 99% of the population",
> but it would be nice to know exact figures based on such a large sample.
>
I have  a report that says:
 Top 5 familiy names :  54%
 top  50 family names:  97%
  top 100   "                   : 99.6%

 Soobok


 
> 
> Regards,    Martin.
> 




From owner-idn@ops.ietf.org  Sat Aug 18 15:14: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 PAA14896
	for <idn-archive@lists.ietf.org>; Sat, 18 Aug 2001 15:14:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15YBFq-000JPL-00
	for idn-data@psg.com; Sat, 18 Aug 2001 11:55:30 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15YBFp-000JP7-00
	for idn@ops.ietf.org; Sat, 18 Aug 2001 11:55:30 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1Tn2osJqMb4aV35LEiptgxEg==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GC57GJSS; Sat, 18 Aug 2001 14:54:57 EDT
To: duerst@w3.org
Cc: lsb@postel.co.kr, liana.ydisg@juno.com, bthomson@fm-net.ne.jp,
        idn@ops.ietf.org
Date: Sat, 18 Aug 2001 11:20:31 -0700
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Message-ID: <20010818.121223.-836461.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-48,50,52-55
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, 17 Aug 2001 17:21:35 +0900 Martin Duerst <duerst@w3.org> writes:
> At 16:49 01/08/17 +0900, Soobok Lee wrote:
> >Two corrections:
> > > Yes, but rarely.
> > > some japanese/chinese restaurants in SEOUL Korea
> > >  have the primary name in Hanja(Kanji).
> > > Most korean individuals/companies won't pay for
> > > rarely used HANJA domains, I guess.
> >
> >That may change near future..
> >
> >Recently, Korean Goverments began to encourage
> >HanJa education/Hanja Usages in addition to English ones.
> >You know the economic block of Eastern Asia is rapidly
> >expanding its power... :-)
> 
> I think the trend for more Hangul or more Hanja comes
> and goes like waves in Korea. There are actually similar
> waves in North Korea, but of course with different
> amplitutde and wavelength.
> 
> 
> 
> > > In my rough estimation, most frequent 5000 hangul personal full 
> names
> > > form the set of distinct fullnames of about 90% of korean 
> populations.
> > >
> >Oh my mistake.  5000 ====> 100,000.
> >
> >100,000 distinct fullnames, and 5,000 distinct given(first) names 
> acount
> >for 90% of individual names of south korean population,based on the 
> personal
> >study on 600,000 samples of korean fullnames.
> 
> Do you have the numbers for family names also? I guess it must
> be something like "100 most frequent family names cover 99% of the 
> population",
> but it would be nice to know exact figures based on such a large 
> sample.
> 
> 
> Regards,    Martin.

I don't think we need exact figures here, people with some background
in the culture they speaking about do have some experience, which
serves as a good sample of the usage ( rough statistics). And the numbers

from current registration is a reference too, but a little more bias in
its
certainty.

Liana



From owner-idn@ops.ietf.org  Sat Aug 18 15:14: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 PAA14910
	for <idn-archive@lists.ietf.org>; Sat, 18 Aug 2001 15:14:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15YBFm-000JPE-00
	for idn-data@psg.com; Sat, 18 Aug 2001 11:55:26 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15YBFl-000JP7-00
	for idn@ops.ietf.org; Sat, 18 Aug 2001 11:55:25 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1Tn2osJqMb4aXiqzzEgmwgpQ==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GC57GJRM; Sat, 18 Aug 2001 14:54:57 EDT
To: duerst@w3.org
Cc: liana.ydisg@juno.com, lsb@postel.co.kr, bthomson@fm-net.ne.jp,
        idn@ops.ietf.org
Date: Sat, 18 Aug 2001 11:12:37 -0700
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Message-ID: <20010818.121223.-836461.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

So for Kanji shall be handled like Chinese character,
which means each shall be treated as an icon with 
itsown independency? Am I right? 

Liana

On Fri, 17 Aug 2001 17:24:10 +0900 Martin Duerst <duerst@w3.org> writes:
> At 00:54 01/08/17 -0700, liana.ydisg@juno.com wrote:
> >If Hangul mapped to Latin letters like Romaji and then
> >add a number to select one Kanji among a few
> >homophones, can this be good enough to idnetify a Hanja
> >name in DNS?
> >
> >The same question goes to Bruce Thomson:
> >Can Romaji be revered back to Kanji-Kana sequece with
> >near 100% rate (with or without case ending)?
> 
> Not at all. There are some cases where you can guess,
> and there are cases where even guessing won't really
> help. Of course adding a number or so always will be
> able to do disambiguation, but one would essentially
> have to use a separate number per kanji, because in
> Japanese, new readings can be invented anytime.
> 
> Regards,  Martin.



From owner-idn@ops.ietf.org  Sat Aug 18 15:15: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 PAA14922
	for <idn-archive@lists.ietf.org>; Sat, 18 Aug 2001 15:15:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15YBGC-000JPe-00
	for idn-data@psg.com; Sat, 18 Aug 2001 11:55:52 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15YBGB-000JPX-00
	for idn@ops.ietf.org; Sat, 18 Aug 2001 11:55:51 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1Tn2osJqMb4aVsw7lnwBBuAA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GC57GJTT; Sat, 18 Aug 2001 14:54:57 EDT
To: phoffman@imc.org
Cc: idn@ops.ietf.org, James@Seng.cc
Date: Sat, 18 Aug 2001 12:12:19 -0700
Subject: Re: [idn] amending [IDNA]?
Message-ID: <20010818.121223.-836461.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-28,30-113
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

After some thinking, I suggest more specific statement
in [IDNA] to explain its relationship with [nameprep]:


On Fri, 17 Aug 2001 18:03:23 -0700 liana.ydisg@juno.com writes:
> Hi, Paul:
> 
> I suggest the following procedure specification 
> adds to [IDNA], this is only an idea, while I have no 
> intention to put proper words in the document.
> 
> [IDNA] is the component of internetionalization of 
> Domain Name system. It contains procedures preparing
> localized domain name representation for DNS and 
> supply display representation for local standard 
> according to DNS registered hostnames.  

[IDNA] implements Unicode codepoint specifications
published in [nameprep]. 

> 
> The IDN-label protocol is:
> 
> idn-label(input, tag-file, input-std, zonefile, idn-name)
> {
>   tag = find-tag(input, tag-file, input-std);

     if error(tag) 
	{
	fprintf(stderr, "%s %s", idn-name, "illegal characters found in IDN
label.");
	return (ERROR);
	}

>   switch (tag)
> 	{
> 	case USASCII : return(input);  /* a legal DNS string*/
> 	case NIL: idn-name= 
> 		uni-compress(input, UNICODE, DEFAULT-ACE);
> 		return strcat(DEFAULT-ACE, idn-name);
> 	default:
> 	 idn-folding(input, input-std, tag, USASCII, output-list);
> 	 if idn-label-length(output-list) >= MaxLabelLength
> 	 {	 
> 		record-label(input, output-list, zonefile, tag);
> 		idn-truncate-label(output-list, tag);
> 	 }
> 	 idn-label-concat(output-list, idn-name);
> 	 return  strcat(tag, idn-name);
> 	} 
> 
> The idn-display protocol is:
> 
> idn-display-code(input, local-std, zonefile, display-string)
> {
>   display-string = NIL;
>   search-zone(input, zonefile, local-std, display-string);
>   if display-string 
> 	return display-string;
> 
>   tag = find-tag (input, tag-file, USASCII);

     if error(tag) 
	{
	fprintf(stderr, "%s %s", input, "WARNING: Error found in DNS label.");
	return (ERROR);
	}

>   switch (tag)
> 	{
> 	case USASCII : return(input);  /* a legal DNS string*/
> 	case NIL: return(input); /* legacy name */
> 	case DEFAULT-TAG: 
> 		local-std = UNICODE;
> 		uni-decompress(input, display-string)
> 		return display-string;
> 	default:
> 	 idn-folding(input, USASCII, tag, local-std, 
> display-string);
> 	 if length(inupt) >= MaxLabelLength)  /* truncated */
> 	 	idn-request-fullname(input, output-list, host1, 
> host2);
> 	 return display-string;
> 	} 
> 
> 
delete: > [nameprep] shall be the host for and only deal with
...
delete > for case folding table lookups, and leave exclusion list to be 
delete > checked by idn-label procedure  within a tagged Unicode block.

[nameprep] shall specify availble case folding tables for 
 idn-folding(input, in-std, tag, out-std, out-list) protocol,
and illegal codepoint exclusion shall be implemented in
   tag = find-tag(input, tag-file, input-std)

where tags are script based with naming defined in 
[ISO 639-2/T] and registered with IANA.  

The tags have values:
ERROR		/* contain [nameprep] has Excluded Codepoints */
USASCII		/* [A-Za-z0-9] */
NIL	/* Unicode string with no applicable script label found. */
ZHO	/* Chinese tag */
KOR	/* Korean */
JAP	/* Japanese */
LAT	/* Latin */
...

> 
> I am looking forward for your comments.
> 
> Liana Ye
> 



From owner-idn@ops.ietf.org  Sat Aug 18 15:22: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 PAA15010
	for <idn-archive@lists.ietf.org>; Sat, 18 Aug 2001 15:22:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.31 #1)
	id 15YBVO-000Jee-00
	for idn-data@psg.com; Sat, 18 Aug 2001 12:11:34 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.31 #1)
	id 15YBVN-000JeW-00
	for idn@ops.ietf.org; Sat, 18 Aug 2001 12:11:33 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1T0TiZnthnP7BWVgCX20HeVA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GC58C4QB; Sat, 18 Aug 2001 15:10:33 EDT
To: idn@ops.ietf.org
Date: Sat, 18 Aug 2001 12:27:53 -0700
Subject: Re: [idn] submit draft-liana-idn-step as ?
Message-ID: <20010818.122757.-836461.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-Att: 0
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello, all:

   Thank you for your participating in the discussion 
for alternative IDN solutions.  I hope to submit my
draft-liana-idn-step as draft-ietf-idn-step for the 
working group's formal consideration, do I have 
enough support for this action?

Sincerely,

Liana Ye
Y&D Information Systems Group, Inc. 
California, U.S.A.



From owner-idn@ops.ietf.org  Sun Aug 19 21:01: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 VAA17544
	for <idn-archive@lists.ietf.org>; Sun, 19 Aug 2001 21:01:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15YcxT-00031w-00
	for idn-data@psg.com; Sun, 19 Aug 2001 17:30:23 -0700
Received: from mail.fm-net.ne.jp ([211.15.66.133])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15YcxS-00031o-00
	for idn@ops.ietf.org; Sun, 19 Aug 2001 17:30:22 -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 JAA29855
	for <idn@ops.ietf.org>; Mon, 20 Aug 2001 09:30:14 +0900
Message-ID: <0f9d01c1290f$12b47870$a3420fd3@bruce>
From: "Bruce Thomson" <bthomson@fm-net.ne.jp>
To: <idn@ops.ietf.org>
References: <20010818.121223.-836461.0.liana.ydisg@juno.com>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Date: Mon, 20 Aug 2001 09:28:44 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Right. There should be no folding between Kanji and
other forms, as it is not even possible to do it well
by table lookup.

Also, in my opinion there should be no folding
amongst the two types of kana and Romaji either,
even it could be done easily enough. This might be
controversial, as the fastidious Bank of Japan
demonstrated by registering over twenty forms
of its name in the .com testbed (Kanji, hiragana,
katakana, for .com, .net, and .org, in addition to
the Romaji names registered previously.)

Bruce

----- Original Message -----
From: <liana.ydisg@juno.com>
To: <duerst@w3.org>
Cc: <liana.ydisg@juno.com>; <lsb@postel.co.kr>; <bthomson@fm-net.ne.jp>;
<idn@ops.ietf.org>
Sent: Sunday, August 19, 2001 3:12 AM
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee


> So for Kanji shall be handled like Chinese character,
> which means each shall be treated as an icon with
> itsown independency? Am I right?
>
> Liana
>
> On Fri, 17 Aug 2001 17:24:10 +0900 Martin Duerst <duerst@w3.org> writes:
> > At 00:54 01/08/17 -0700, liana.ydisg@juno.com wrote:
> > >If Hangul mapped to Latin letters like Romaji and then
> > >add a number to select one Kanji among a few
> > >homophones, can this be good enough to idnetify a Hanja
> > >name in DNS?
> > >
> > >The same question goes to Bruce Thomson:
> > >Can Romaji be revered back to Kanji-Kana sequece with
> > >near 100% rate (with or without case ending)?
> >
> > Not at all. There are some cases where you can guess,
> > and there are cases where even guessing won't really
> > help. Of course adding a number or so always will be
> > able to do disambiguation, but one would essentially
> > have to use a separate number per kanji, because in
> > Japanese, new readings can be invented anytime.
> >
> > Regards,  Martin.
>




From owner-idn@ops.ietf.org  Mon Aug 20 01: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 BAA24109
	for <idn-archive@lists.ietf.org>; Mon, 20 Aug 2001 01:32:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15YhFO-0007tB-00
	for idn-data@psg.com; Sun, 19 Aug 2001 22:05:10 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15YhFN-0007t5-00
	for idn@ops.ietf.org; Sun, 19 Aug 2001 22:05:09 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1TR4CAMHfraAWnxMHRvwiHeg==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GC9URQB4; Mon, 20 Aug 2001 01:04:41 EDT
To: James@Seng.cc
Cc: tsenglm@cc.ncu.edu.tw, huangk@alum.sinica.edu, liana.ydisg@juno.com,
        idn@ops.ietf.org, dhc@dcrocker.net
Date: Sun, 19 Aug 2001 22:21:59 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010819.222207.-979123.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-12,14-15,17-136
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,

 Thank you for the implementation analysis.  It is very
helpful for bringing  this discussion down to another
level.  I have serveral thoughts on this.

The SC character set has been used for decades and has went
through extensive nationwide testing in China.  SC is stable and they are
properly reflected in Unicode standard.   The question is a definition:
is TC/SC a case folding?  It seems that in this WG, there has no 
consensus on this definition yet. 

The primary reason, I guess, is everyone knows that CJK is a piece of
very hot sweet potato, and quite easy to get burned from it, but it
smells
so good, that none of us wants to give it up at this momment.  :-))
One solution is to push the hot sweet potato to zonefile, but as you have

pointed out, only Chinese zone will do this.  If I am in US, it may be 
hopeless for me  to see Chinese characters on my domain name 
forever.  

However, the implementation as you have described can be 
implemented in [nameprep] with Unicode as the primary reference 
code, provided the character mapping issue has been settled with
your option 1.  And we are back to the case folding definition.  
I offer my definition:  case folding is from a key with one look up 
into a data table, and you can obtain another key from the search. 

Example: 

Unicode		folds to
points
col-1		col-2

A  		a			(case 1)
TC-1  		SC-1			(case 2)
IPA letter ts	t s			(case 3)
Kanji-1		Kana-1			(case 4)
Kanji-1		Kana-2
Kanji-1		Kana-3
Hanja-1		Hangul-1		(case 5)
Hanja-2		Hangul-1
Hanja-3		Hangul-1

Case 1 is the current [nameprep],
Case 2 is the long lasting discussion of TC/SC,
Case 3 is possible mnemonic ACE assignment,
Case 4 and 5 is the extent of allowing TC/SC as 
	case folding into [nameprep].

With the above list, it is questionable about the above are 
case folding.  Because, from col-1 key Kanji-1, there are 
three lookups to get Kana-3 back in Case 4 and three 
lookups from Hangul-1 to Hanja-3 in Case 5. 

The problem is not so much with TC/SC even they are 
one-one mapping, it is with Kanji and Hanja.  Using
transliteration only, as in Case 3, is obvious not good enough,
as you have pointed out in your option 3.  Since what IDN
is realy wanted is an ACE to go into DNS, we can obtain
such an mnemonic ACE by assign another column to
this table, thus:

col-1 		col-2		 col-3 ACE  

A  		a		a			(case 1)
White Space	nil		nil
SC-1				Pinyin-1+part1+part2+part3  (case 2)
TC-1  		SC-1		Pinyin-1+part1+part2+part3  
IPA letter ts	t s		ts			  (case 3)

Kana-1				Romaji-1
Kanji-1		Kana-1		Romaji-1+part1+part2	(case 4)
Kanji-1		Kana-2		Romaji-2+part1+part2	(ruled out)
Kanji-1		Kana-3		Romaji-3+part1+part2	(ruled out)

Hangul-1			Hangul-1
Hanja-1		Hangul-1	Hangul-1+part-1.1	(case 5)
Hanja-2		Hangul-1	Hangul-1+part-2.1
Hanja-3		Hangul-1	Hangul-1+part-3.1

Now any key search from col-1 will get a unique  ACE from col-3,
except Kanji-1 to Kana-3 has to be ruled out by one search only
case folding.  If we can assign any identifier to it, the user has
 to take a one sound per Kanji within its Romaji system.  This 
is the "language" aspect that case folding can not solve.   Well, the 
alternative is a compressed ACE.  But from col-3 to col-1, there is 
always one success search.  

While any key from col-3 will get a display code from col-1.  This
table and search is within the pure technical "case folding" 
definition given above.

What if Hanja-1 = Kanji-1? This can be checked at registration 
time in addition to its ACE, which is checked with DNS.  I am
not certain, if IDN registration is part of this WG charter goal or 
not, and so I shall stop any discussing on its relation with 
[nameprep] or any related issues and hope that no one getting a 
hot sweet potato burn.

One issue on mnemonic ACE is its value assignment, since 
Unicode has given each symbol a Latin name, but the name 
is not intented to be used in case folding, and as a pure 
technical WG, we can assign any value to an identifier.  How 
much freedom do we have in such an assignment?

In any case, I agree with you that this WG needs a list to collect 
each SCRIPT user/engineers' input regarding user's wish list. 
 I've come up with the following questionary for comments.

1. Your script name (refer to a name defined in Unicode):

2. How familar are you with the script? How often do you 
  use the script? 

3. What do you expecting your IDN hostname look like?

4. Does your script is used interchagebly with another script?
   If yes, then which ones? Are they used as a mixed string? 

5. How does your script  dealing with foreign concept? 

6. How does your script  dealing with foreign sounds?

7. Do you wish your script could mix with other scripts?  
  If you do, then which script do you think is most useful
  for your script to accommodating?

8. As an engineer, what part of the use of your script is 
relatively universal such that there will be no serious 
controversal against it to be fixed by IDN implementation?

9. As an engineer, what part of the use of your script is 
often controversal, such that IDN shall avoid it in 
 IDN implementation?

Liana Ye



From owner-idn@ops.ietf.org  Mon Aug 20 01:33: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 BAA24320
	for <idn-archive@lists.ietf.org>; Mon, 20 Aug 2001 01:33:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15YhQv-00089p-00
	for idn-data@psg.com; Sun, 19 Aug 2001 22:17:05 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15YhQu-00089j-00
	for idn@ops.ietf.org; Sun, 19 Aug 2001 22:17:04 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1TKMUcwS148Hiaz3e3wXo2RA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GC9VE2KR; Mon, 20 Aug 2001 01:16:20 EDT
To: bthomson@fm-net.ne.jp
Cc: idn@ops.ietf.org
Date: Sun, 19 Aug 2001 22:33:46 -0700
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Message-ID: <20010819.223347.-979123.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-5,7-61
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

One Kanji to one unique ACE, is this good enough?
That is you do not allow one Kanji has several
ACE, such as Kanji to Romaji case. Is this correct?

Liana

On Mon, 20 Aug 2001 09:28:44 +0900 "Bruce Thomson"
<bthomson@fm-net.ne.jp> writes:
> Right. There should be no folding between Kanji and
> other forms, as it is not even possible to do it well
> by table lookup.
> 
> Also, in my opinion there should be no folding
> amongst the two types of kana and Romaji either,
> even it could be done easily enough. This might be
> controversial, as the fastidious Bank of Japan
> demonstrated by registering over twenty forms
> of its name in the .com testbed (Kanji, hiragana,
> katakana, for .com, .net, and .org, in addition to
> the Romaji names registered previously.)
> 
> Bruce
> 
> ----- Original Message -----
> From: <liana.ydisg@juno.com>
> To: <duerst@w3.org>
> Cc: <liana.ydisg@juno.com>; <lsb@postel.co.kr>; 
> <bthomson@fm-net.ne.jp>;
> <idn@ops.ietf.org>
> Sent: Sunday, August 19, 2001 3:12 AM
> Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
> 
> 
> > So for Kanji shall be handled like Chinese character,
> > which means each shall be treated as an icon with
> > itsown independency? Am I right?
> >
> > Liana
> >
> > On Fri, 17 Aug 2001 17:24:10 +0900 Martin Duerst <duerst@w3.org> 
> writes:
> > > At 00:54 01/08/17 -0700, liana.ydisg@juno.com wrote:
> > > >If Hangul mapped to Latin letters like Romaji and then
> > > >add a number to select one Kanji among a few
> > > >homophones, can this be good enough to idnetify a Hanja
> > > >name in DNS?
> > > >
> > > >The same question goes to Bruce Thomson:
> > > >Can Romaji be revered back to Kanji-Kana sequece with
> > > >near 100% rate (with or without case ending)?
> > >
> > > Not at all. There are some cases where you can guess,
> > > and there are cases where even guessing won't really
> > > help. Of course adding a number or so always will be
> > > able to do disambiguation, but one would essentially
> > > have to use a separate number per kanji, because in
> > > Japanese, new readings can be invented anytime.
> > >
> > > Regards,  Martin.
> >
> 
> 



From owner-idn@ops.ietf.org  Mon Aug 20 02:08: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 CAA05764
	for <idn-archive@lists.ietf.org>; Mon, 20 Aug 2001 02:08:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15Yi0R-0009BT-00
	for idn-data@psg.com; Sun, 19 Aug 2001 22:53:47 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15Yi0Q-0009BN-00
	for idn@ops.ietf.org; Sun, 19 Aug 2001 22:53:46 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 141AEFFC04; Mon, 20 Aug 2001 13:55:06 +0800 (SGT)
Message-ID: <047001c1293c$754901e0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: <liana.ydisg@juno.com>
Cc: <tsenglm@cc.ncu.edu.tw>, <huangk@alum.sinica.edu>, <liana.ydisg@juno.com>,
        <idn@ops.ietf.org>, <dhc@dcrocker.net>
References: <20010819.222207.-979123.0.liana.ydisg@juno.com>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Mon, 20 Aug 2001 13:53: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

> The SC character set has been used for decades and has went
> through extensive nationwide testing in China.  SC is stable and they
are
> properly reflected in Unicode standard.   The question is a
definition:
> is TC/SC a case folding?  It seems that in this WG, there has no
> consensus on this definition yet.

I am not sure what you mean by "properly reflected" in Unicode Standard.
If you mean it is in ISO10646 codepoints, then yes, both TC/SC are in
the code points. But if you saying Unicode Consortium have proper
definition of TC/SC, then I afraid to say there is none.

> One solution is to push the hot sweet potato to zonefile, but as you
have
> pointed out, only Chinese zone will do this.  If I am in US, it may be
> hopeless for me  to see Chinese characters on my domain name
> forever.

Correction: Assuming TC/SC is handled per zone, then it would be up to
the zone admin to decide if he wish to put in TC/SC in the zone or not.
It does not matter where you are, US or China.

> However, the implementation as you have described can be
> implemented in [nameprep] with Unicode as the primary reference
> code, provided the character mapping issue has been settled with
> your option 1.  And we are back to the case folding definition.
> I offer my definition:  case folding is from a key with one look up
> into a data table, and you can obtain another key from the search.

Yes, treating TC/SC like "case-folding" is one of the possible way to do
it altho it introduce other difficulties. However, this wg is not the
right place to discuss codepoint property or any "correction" to Unicode
case-folding/normalization tables/mappings.

The following questions does sound interesting. Would appreciate if you
can post the result to the wg after you gather the responses.

-James Seng

> In any case, I agree with you that this WG needs a list to collect
> each SCRIPT user/engineers' input regarding user's wish list.
>  I've come up with the following questionary for comments.
>
> 1. Your script name (refer to a name defined in Unicode):
>
> 2. How familar are you with the script? How often do you
>   use the script?
>
> 3. What do you expecting your IDN hostname look like?
>
> 4. Does your script is used interchagebly with another script?
>    If yes, then which ones? Are they used as a mixed string?
>
> 5. How does your script  dealing with foreign concept?
>
> 6. How does your script  dealing with foreign sounds?
>
> 7. Do you wish your script could mix with other scripts?
>   If you do, then which script do you think is most useful
>   for your script to accommodating?
>
> 8. As an engineer, what part of the use of your script is
> relatively universal such that there will be no serious
> controversal against it to be fixed by IDN implementation?
>
> 9. As an engineer, what part of the use of your script is
> often controversal, such that IDN shall avoid it in
>  IDN implementation?




From owner-idn@ops.ietf.org  Mon Aug 20 03:12: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 DAA08791
	for <idn-archive@lists.ietf.org>; Mon, 20 Aug 2001 03:12:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15Yizm-000Ab4-00
	for idn-data@psg.com; Sun, 19 Aug 2001 23:57:10 -0700
Received: from mail.fm-net.ne.jp ([211.15.66.133])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15Yizl-000Aax-00
	for idn@ops.ietf.org; Sun, 19 Aug 2001 23:57:09 -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 PAA31699
	for <idn@ops.ietf.org>; Mon, 20 Aug 2001 15:57:07 +0900
Message-ID: <12cf01c12945$1ca12690$a3420fd3@bruce>
From: "Bruce Thomson" <bthomson@fm-net.ne.jp>
To: <idn@ops.ietf.org>
References: <20010819.223347.-979123.1.liana.ydisg@juno.com>
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
Date: Mon, 20 Aug 2001 15:55:35 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Yes, that's fine.

Bruce

----- Original Message ----- 
From: <liana.ydisg@juno.com>
To: <bthomson@fm-net.ne.jp>
Cc: <idn@ops.ietf.org>
Sent: Monday, August 20, 2001 2:33 PM
Subject: Re: [idn] Question for the Kanji & Hanja cognosentee


> One Kanji to one unique ACE, is this good enough?
> That is you do not allow one Kanji has several
> ACE, such as Kanji to Romaji case. Is this correct?
> 
> Liana
> 
> On Mon, 20 Aug 2001 09:28:44 +0900 "Bruce Thomson"
> <bthomson@fm-net.ne.jp> writes:
> > Right. There should be no folding between Kanji and
> > other forms, as it is not even possible to do it well
> > by table lookup.
> > 
> > Also, in my opinion there should be no folding
> > amongst the two types of kana and Romaji either,
> > even it could be done easily enough. This might be
> > controversial, as the fastidious Bank of Japan
> > demonstrated by registering over twenty forms
> > of its name in the .com testbed (Kanji, hiragana,
> > katakana, for .com, .net, and .org, in addition to
> > the Romaji names registered previously.)
> > 
> > Bruce
> > 
> > ----- Original Message -----
> > From: <liana.ydisg@juno.com>
> > To: <duerst@w3.org>
> > Cc: <liana.ydisg@juno.com>; <lsb@postel.co.kr>; 
> > <bthomson@fm-net.ne.jp>;
> > <idn@ops.ietf.org>
> > Sent: Sunday, August 19, 2001 3:12 AM
> > Subject: Re: [idn] Question for the Kanji & Hanja cognosentee
> > 
> > 
> > > So for Kanji shall be handled like Chinese character,
> > > which means each shall be treated as an icon with
> > > itsown independency? Am I right?
> > >
> > > Liana
> > >
> > > On Fri, 17 Aug 2001 17:24:10 +0900 Martin Duerst <duerst@w3.org> 
> > writes:
> > > > At 00:54 01/08/17 -0700, liana.ydisg@juno.com wrote:
> > > > >If Hangul mapped to Latin letters like Romaji and then
> > > > >add a number to select one Kanji among a few
> > > > >homophones, can this be good enough to idnetify a Hanja
> > > > >name in DNS?
> > > > >
> > > > >The same question goes to Bruce Thomson:
> > > > >Can Romaji be revered back to Kanji-Kana sequece with
> > > > >near 100% rate (with or without case ending)?
> > > >
> > > > Not at all. There are some cases where you can guess,
> > > > and there are cases where even guessing won't really
> > > > help. Of course adding a number or so always will be
> > > > able to do disambiguation, but one would essentially
> > > > have to use a separate number per kanji, because in
> > > > Japanese, new readings can be invented anytime.
> > > >
> > > > Regards,  Martin.
> > >
> > 
> > 
> 
> 




From owner-idn@ops.ietf.org  Mon Aug 20 13:44: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 NAA28257
	for <idn-archive@lists.ietf.org>; Mon, 20 Aug 2001 13:44:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15YsoF-00009F-00
	for idn-data@psg.com; Mon, 20 Aug 2001 10:25:55 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15YsoE-000099-00
	for idn@ops.ietf.org; Mon, 20 Aug 2001 10:25:54 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH6dIKGGQrq1T+NJY2tupm3ZLqvwKCazXYw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GDA66NUJ; Mon, 20 Aug 2001 13:25:46 EDT
To: idn@ops.ietf.org
Cc: liana.ydisg@juno.com
Date: Mon, 20 Aug 2001 10:43:08 -0700
Subject: [idn]How do you use your script?
Message-ID: <20010820.104312.-1004441.1.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.11
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

If you care about the way that IDN handles your native
script, please try your best to answer the following 
questions to help us sort out users' requirements.

Thank you very much!

Liana Ye

>The following questions does sound interesting. Would appreciate if you
>can post the result to the wg after you gather the responses.

>-James Seng

> In any case, I agree with you that this WG needs a list to collect
> each SCRIPT user/engineers' input regarding user's wish list.
>  I've come up with the following questionary for comments.
>
> 1. Your script name (refer to a name defined in Unicode):
>
> 2. How familar are you with the script? How often do you
>   use the script?
>
> 3. What do you expecting your IDN hostname look like?
>
> 4. Does your script is used interchagebly with another script?
>    If yes, then which ones? Are they used as a mixed string?
>
> 5. How does your script  dealing with foreign concept?
>
> 6. How does your script  dealing with foreign sounds?
>
> 7. Do you wish your script could mix with other scripts?
>   If you do, then which script do you think is most useful
>   for your script to accommodating?
>
> 8. As an engineer, what part of the use of your script is
> relatively universal such that there will be no serious
> controversal against it to be fixed by IDN implementation?
>
> 9. As an engineer, what part of the use of your script is
> often controversal, such that IDN shall avoid it in
>  IDN implementation?



From owner-idn@ops.ietf.org  Tue Aug 21 07:45: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 HAA05901
	for <idn-archive@lists.ietf.org>; Tue, 21 Aug 2001 07:45:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15Z9gL-000FBv-00
	for idn-data@psg.com; Tue, 21 Aug 2001 04:26:53 -0700
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15Z9gK-000FBT-00
	for idn@ops.ietf.org; Tue, 21 Aug 2001 04:26:52 -0700
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05039;
	Tue, 21 Aug 2001 07:25:33 -0400 (EDT)
Message-Id: <200108211125.HAA05039@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: idn@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [idn] I-D ACTION:draft-ietf-idn-udns-03.txt
Date: Tue, 21 Aug 2001 07:25:33 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: Using the Universal Character Set in the Domain Name 
                          System (UDNS)
	Author(s)	: D. Oscarsson
	Filename	: draft-ietf-idn-udns-03.txt
	Pages		: 10
	Date		: 20-Aug-01
	
Since the Domain Name System (DNS) [RFC1035] was created there have
been a desire to use other characters than ASCII in domain names.
Lately this desire have grown very strong and several groups have
started to experiment with non-ASCII names.  This document defines
how the Universal Character Set (UCS) [ISO10646] is to be used in
DNS.  It includes both a transition scheme for older software
supporting non-ASCII handling in applications only, as well as how to
use UCS in labels and having more than 63 octets in a label.

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

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-idn-udns-03.txt

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

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

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Tue Aug 21 14:49: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 OAA27638
	for <idn-archive@lists.ietf.org>; Tue, 21 Aug 2001 14:49:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ZGOI-0008Pu-00
	for idn-data@psg.com; Tue, 21 Aug 2001 11:36:42 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ZGOH-0008Po-00
	for idn@ops.ietf.org; Tue, 21 Aug 2001 11:36:41 -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 f7LJ1uQ59928
	for <idn@ops.ietf.org>; Tue, 21 Aug 2001 15:01:56 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010821122941.03451718@127.0.0.1>
X-Sender: blanchet@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 21 Aug 2001 14:17:21 -0400
To: idn@ops.ietf.org
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: [idn] ietf london idn wg meeting minutes
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

included is the first version of the idn wg meeting minutes.
please send editorial comments to me, substantive comments to the mailing list.

Marc.

===========================================

IETF IDN Working group session
9 August 2001
London, England

Agenda Bashing:

Agreement on the floor to cut
  Reordering, nameprep update, Uname proposal, Hangulchar, tsconv
from planned agenda.

================================================================

WG UPDATE, Marc Blanchet

Coordination with other groups/efforts:
- IETF apps area
    - "requirements" for encoding: ACE or UTF8
    - directory efforts: directory@apps.ietf.org
- Unicode/ISO
    - Any modifications to Unicode/ISO tables should be done by those
    parties, not IETF
- IETF dnsext WG
    - Any modification to DNS protocol should be discussed in dnsext
- ICANN/IANA
    - Policies

- Pool W, pool of documents that identify core of interest by WG
- Currently:
    - requirements
      co-chairs believe there is a wg rough concensus and intend to forward
      it to IESG for Informational.
    - idna
    - nameprep
    - dude
    - aceid
    - jpchar
    - ace-eval-jp
    - mace
    - uname
    - tsconv
    - udns
    - amc-ace-z
    - hangeulchar
    - lsb-ace
- Today's focus is on standards track proposals

================================================================

ACE EVALUATION WITH IDNs ALREADY REGISTERED, Yoshiro Yoneya

- Done by CNNIC, KRNIC, TWNIC and JPNIC with data they have for
   registered domain names, focusing on ACEs in Pool W.
- Most important evaluation criterion to study is to maximize number
   of characters, raw speed is less important because nameprep is the
   slow stage.
- Long IDNs (more than 15 Han characters) are already registered.
- Evaluated ACEs: DUDE, AMC-ACEZ, MACE and RACE
- Focus on DUDE and AMC-ACE-Z with MACE&RACE as reference

Graphs of efficiency of domain names from each of KRNIC and TWNIC,
where AMC-ACE-Z shows best compressions

Charts showing that the four NICs consider AMC-ACE-Z to be either good
or very good, while others were "bad" or "very bad" for at least one NIC.

MACE co-authors (including the presenter, Yoneya-san) support
AMC-ACE-Z.

Recommendation from the study is: AMC-ACE-Z

================
WG Questions for sense of the group:

Question: If there is a need for an ACE, choose one:
- DUDE                                  few hands
- AMC-ACE-Z                             most hands
- MACE                                  (removed at request of authors)
- don't care but want an ACE chosen     fair bunch of hands

Erik Nordmark: question is, if you use an ACE, this is the one. Not
saying you need to use an ACE anywhere.

?: What is re-ordering?

James Seng: pre-processing to make more frequently used chars more
compressed.

Paul Hoffman: Not binding vote. Should be comfirmed on mailing list.

Concensus: AMC-ACE-Z (with many don't care so long one is choosen)

Should we do reordering?
- Yes                                   some hands
- No                                    some hands
No clear result of poll.

Erik Nordmark: A lot fewer people participated in the former poll but
not the latter.  Why?

Bill Manning: We read the draft but didn't understand it, and need to
read it again.

Paul Hoffman: Don't understand the re-ordering draft. Does not
broaden to other scripts.

Larry Masinter: Re-ordering adds complexity.

Kilnam Chon: Re-ordering is critical for CJK but add complexity.

Paul Hoffman: This draft adds complexity, so perhaps people are waiting
to decide how to judge whether the added complexity is worth it.

Eric Chen: This is just intended to help CJK. Most of the interest
is in CJK. Why not?

James Seng: What I'm hearing is that the authors should do a
cost/benefit analysis, but it is clear the draft is not ready to move
forward.

Erik Nordmark: Can someone do a pro/con analysis draft, or someone do pro and
someone con, to help drive the discussion on the mailing list?

Paul Hoffman: Let's make Adam [Costello] do it. [laughter]

Kilnam Chon: This straw poll process isn't really valid because not
enough representation from people for whom this is really important.
There's always a trade-off.

James Seng: Could someone who voted against the lsb draft just explain
why you are against it?

Paul: I'd rather someone else did, but I will ... the reordering draft
is somewhat of a hack to optimize for certain scripts, but it is at
the cost of other scripts, isn't really generalized, and there has
been no analysis of how beneficial it is for DUDE and AMC-ACE-Z.

Dongman Lee: The author was not trying to propose this as a
generalized mechanism.  It is not surprising that since CJK is driving
internationalization, that proposals would be specific to that.

Ted Hardie: As Paul pointed out, this has different effects on
different scripts, but now that we are focused on one ACE we can ask
more specifically for the authors to focus on just how it affects
AMC-ACE-Z.

Concensus: discuss the reordering on mailing list and request authors
  of ACE and reordering to come to a proposal with analysis.

================================================================

MATCHING (NAMEPREP)

- Need for a standardized pre-processing step regardless of what IDN
    protocol we choose?
    Yes      lot of hands
    No       one hand

(Discussion clarified the question from the original.)

Other comments:

Patrik Faltstrom: Doesn't preclude other pre-processing before it,
which some people have worried it would.  But even so, IETF really
needs to have one standard way of processing Unicode.

James Seng: When you say one standard way, do you mean one with flexibility
for locale, or essentially fixed?

Patrik Falstrom: Essentially fixed.

Dave Crocker: I thank Patrik for his comments that helped clarify
things for me.  I used to be resistant to it, but am coming to accept
it.  It is quite a bit like the case-insensitive/sensitive thing we're
so used to in ASCII.  There are two processes here: case-mapping and
determining the legal character set.  Keep them cleanly separate.

? Russell:

Wenhui Zhang: Should have a standard that includes where local issues
can be defined, which can include their standarized pre-processing.

?: Goal of working group is noble, but are trying to kill all the
birds with one stone, and so we need a really large stone.  So many
legacy systems are optimized for their local languages, and will have
a lot of pain to switch to what is being planned.  They don't have
much of a voice here, those who are going to suffer most.

?: Look into what happened in the LDAP group, how they ended up with a
bunch of language-specific things.  It is difficult, but it can be
done, and since it has already been solved, build on it.

Erik Nordmark: Can we get back on the topic of this question?  We seem to be
wandering into the general requirements area.

POLL: Many to 1 in favour of standard pre-processing step.

Post poll:

John Klensin: I can agree that a standard pre-processing step is
needed, but I can't agree if that necessarily means having a single
binary result even in ambiguous situations.  Very concerned about that.
This working group might be resulting in something that is totally
irrelevant.

Eric Brunner-Williams: The ambiguity need not exist in "uniprep" (the
first of the stages observed by Dave Crocker), the problem arises in
the other part.

Paul: I think we should now work toward an architecture that includes
pre-nameprep, nameprep and post-nameprep.  The middle one can be
generally standardized while the other stages need not be.

Erik Nordmark: Addressing John's concern of irrelevance, I can see how
this work would eventually be superseded by something better, but that
doesn't mean we have to stop doing this very useful work now.

Dave Crocker: Dealing with "language" is out of scope for this group, this
working group should just be about expanding the set of strings that
are usable as domain names.  In that context canonicalization makes a
lot of sense, but not when we start talking about natual language.

Ted Hardie: I have to take exception to Paul describing a system that
is not standarized end-to-end; it can't include processing that is not
standardized.  Also agree with Dave that we can't work with natural
language, we don't have the expertise.

?: Rigorously avoid natural languages.

Eric Chen: We need to consider natual language!

Dave Crocker: The scope is very narrow and does not include languages.

Harald: "Yes."

Paul Hoffman: Please defer all questions of language, there will be a draft
soon that addresses where it should be addressed.

Next step will be for the authors to clarify the relation between
the various proposals for processing into a cohesive architecture,
namely nameprep, tsconv, jpchar, hangeulchar.

================================================================

PROTOCOL PROPOSALS, Dave Crocker

Dave's Disclaimers:
- System oriented person
- Not a Unicode expert, or even naif
- Entirely biased -- wanted to be objective, but failed

IDN Task:
- Enhance range of domain names that are useful
- Not human "name"
- Not "language"
- Has no sets
- Requires: fairness, efficiency, reliability, transition, ...

The Usual Suspects:
      Encoding            Approach
1. ACE only             IDNA
2. UTF-8 only           IDNA-mod, uDNS
3. ACE then UTF-8       IDNA-mod, uDNS
4. ACE & UTF-8 both     uDNS, uNAME
5. Anything goes        uNAME

Encoding efficiency:
- ACE is an encoding scheme
- UTF-8 is an encoding scheme
- Both map many bits to a variable length string
- All variable length strings are unfair to some poeple
- Fair vs unfair unfairness:
    - longer mapping mean shorter names
    - shorter names restricted to information dense character sets

Encoding comparison:
1. ACE is three minuses bad.
2. UTF-8  is two minuses bad.

Charts showing that there are a lot of modules in both systems, and we
have to worry about all the modules in both systems.

ACE has an extraordinarily minimal amount of change necessary to make
an IDN useful, just two applications.  This is about as good a
transition scheme as you can possibly get.

UTF-8 is an extreme in the opposite direction, it requires that
everything work end-to-end.

1. ACE only four pluses good
2. UTF-8 only five minuses bad

Transition Interactions:
-------------------------------------------------------------------------
-------------------------------------------------------------------------
                  Client->  Server->           ACE              UTF-8
                  Server    Client
-------------------------------------------------------------------------
1. old client   old dn    new dn          transparent     UTF-8 and ACE
     new server                                           maybe break client
-------------------------------------------------------------------------
2. new client,  new dn    old dn          transparent     break server?
     old server
-------------------------------------------------------------------------
-------------------------------------------------------------------------

Specification comparison:

-------------------------------------------------------------------------
-------------------------------------------------------------------------
                  Efficiency          Transition           Risk/Operational
                                                              Expense
-------------------------------------------------------------------------
IDNA (ACE)     bad(data)            automatic               none
-------------------------------------------------------------------------
                                      how to detect
uDNS (UTF-8)   poor(data)           when to use ACE?        high
                                      (poorly defined
                                      and not realistic)
-------------------------------------------------------------------------
                                      unstated
uName (both)   bad (round trip)     (and based on CNRP,     very, very
                                      with no meaningful      high
                                      deployment)
-------------------------------------------------------------------------
-------------------------------------------------------------------------

Olafur: Hard for me to say this to you Dave, given our history, but
good job.

Harald: Think you underestimate the cost of ACE a bit, in that leakage
will confuse users.  But UTF-8 leakage will also confuse users, but
likely even a bit more! But the ranking is still good.

Paul: uName doesn't actually have CNRP in it; it was put in the draft
and then explicitly shot down in the draft.  It uses a new RR, but the
end result is pretty much the same as far as your conclusions go.

Erik Nordmark: Can we vote on it without a UTF-8 draft in the pool?
Would need a draft very fast.

Poll:
- idna?
    Yes   Most
    No    Some
- udns?
    Yes   Few
    No    Most
- uname?
    Yes   Few
    No    Most

Interpretation by Harald and Marc was that: IDNA was the only strongly
supported proposal in the room and the other two had
strong opposition. Interpretation was agreed by the floor.

Nameprep discussion back (some time remaining)

Paul Hoffman: Good (from a marketing sense) user interfaces will do a lot of
mucking with input.  Really should have it defined how and where they
can do that. If you change machine, different local translation
tables can yield different names.

James Seng: It can be very hard to determine what local conversion
option to turn on. Not sure if this wg has capability to deal
with codepoint matching. We need to reference code points outside
the IETF, at Unicode Consortium.

Paul Hoffman: Unicode has put mapping tables out of scope.

Harald Alvestrand: This working group is internationalized access to domain
names, not localized.  This group is trying to specialize what a
client must do no matter where it is in the world.  I would accept a
statement that the relationship between the pre-processing drafts.  It
has to be made mandatory though or it should not be part of the output
of this group.

Wenhui Zheng: IDNA draft should be explicit where the local
interface/mapping should be done.

Eric Chen: We have built a house and opened some gates but not others.
Some languages can come in and others can not. IDNA should open its
gate to allow other languages to do their thing.

================================================================
NEXT STEPS

- AMC-ACE-Z as chosen ACE.
- Reordering to be discussed on mailing list.
- relation between nameprep/tsconv/hanguelchar/jpchar/stringprep
    to be consolidated into one architecture.
- Go forward with IDNA.





From owner-idn@ops.ietf.org  Wed Aug 22 00:04: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 AAA08164
	for <idn-archive@lists.ietf.org>; Wed, 22 Aug 2001 00:04:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ZOqC-000Bw1-00
	for idn-data@psg.com; Tue, 21 Aug 2001 20:38:04 -0700
Received: from [203.126.116.228] (helo=mail.i-dns.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ZOq4-000Bvr-00
	for idn@ops.ietf.org; Tue, 21 Aug 2001 20:37:57 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id A116CFFC10; Wed, 22 Aug 2001 11:38:58 +0800 (SGT)
Message-ID: <049001c12abb$c80c8840$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: <idn@ops.ietf.org>, "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>
References: <5.1.0.14.1.20010821122941.03451718@127.0.0.1>
Subject: Re: [idn] ietf london idn wg meeting minutes
Date: Wed, 22 Aug 2001 11:37:34 +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

One note:

The minutes is combination of notes from David Lawrence and Donald E.
Eastlake. Thanks for been the wg scribes.

-James Seng

----- Original Message -----
From: "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>
To: <idn@ops.ietf.org>
Sent: Wednesday, August 22, 2001 2:17 AM
Subject: [idn] ietf london idn wg meeting minutes


> included is the first version of the idn wg meeting minutes.
> please send editorial comments to me, substantive comments to the
mailing list.
>
> Marc.
>
> ===========================================
>
> IETF IDN Working group session
> 9 August 2001
> London, England
>
> Agenda Bashing:
>
> Agreement on the floor to cut
>   Reordering, nameprep update, Uname proposal, Hangulchar, tsconv
> from planned agenda.
>
> ================================================================
>
> WG UPDATE, Marc Blanchet
>
> Coordination with other groups/efforts:
> - IETF apps area
>     - "requirements" for encoding: ACE or UTF8
>     - directory efforts: directory@apps.ietf.org
> - Unicode/ISO
>     - Any modifications to Unicode/ISO tables should be done by those
>     parties, not IETF
> - IETF dnsext WG
>     - Any modification to DNS protocol should be discussed in dnsext
> - ICANN/IANA
>     - Policies
>
> - Pool W, pool of documents that identify core of interest by WG
> - Currently:
>     - requirements
>       co-chairs believe there is a wg rough concensus and intend to
forward
>       it to IESG for Informational.
>     - idna
>     - nameprep
>     - dude
>     - aceid
>     - jpchar
>     - ace-eval-jp
>     - mace
>     - uname
>     - tsconv
>     - udns
>     - amc-ace-z
>     - hangeulchar
>     - lsb-ace
> - Today's focus is on standards track proposals
>
> ================================================================
>
> ACE EVALUATION WITH IDNs ALREADY REGISTERED, Yoshiro Yoneya
>
> - Done by CNNIC, KRNIC, TWNIC and JPNIC with data they have for
>    registered domain names, focusing on ACEs in Pool W.
> - Most important evaluation criterion to study is to maximize number
>    of characters, raw speed is less important because nameprep is the
>    slow stage.
> - Long IDNs (more than 15 Han characters) are already registered.
> - Evaluated ACEs: DUDE, AMC-ACEZ, MACE and RACE
> - Focus on DUDE and AMC-ACE-Z with MACE&RACE as reference
>
> Graphs of efficiency of domain names from each of KRNIC and TWNIC,
> where AMC-ACE-Z shows best compressions
>
> Charts showing that the four NICs consider AMC-ACE-Z to be either good
> or very good, while others were "bad" or "very bad" for at least one
NIC.
>
> MACE co-authors (including the presenter, Yoneya-san) support
> AMC-ACE-Z.
>
> Recommendation from the study is: AMC-ACE-Z
>
> ================
> WG Questions for sense of the group:
>
> Question: If there is a need for an ACE, choose one:
> - DUDE                                  few hands
> - AMC-ACE-Z                             most hands
> - MACE                                  (removed at request of
authors)
> - don't care but want an ACE chosen     fair bunch of hands
>
> Erik Nordmark: question is, if you use an ACE, this is the one. Not
> saying you need to use an ACE anywhere.
>
> ?: What is re-ordering?
>
> James Seng: pre-processing to make more frequently used chars more
> compressed.
>
> Paul Hoffman: Not binding vote. Should be comfirmed on mailing list.
>
> Concensus: AMC-ACE-Z (with many don't care so long one is choosen)
>
> Should we do reordering?
> - Yes                                   some hands
> - No                                    some hands
> No clear result of poll.
>
> Erik Nordmark: A lot fewer people participated in the former poll but
> not the latter.  Why?
>
> Bill Manning: We read the draft but didn't understand it, and need to
> read it again.
>
> Paul Hoffman: Don't understand the re-ordering draft. Does not
> broaden to other scripts.
>
> Larry Masinter: Re-ordering adds complexity.
>
> Kilnam Chon: Re-ordering is critical for CJK but add complexity.
>
> Paul Hoffman: This draft adds complexity, so perhaps people are
waiting
> to decide how to judge whether the added complexity is worth it.
>
> Eric Chen: This is just intended to help CJK. Most of the interest
> is in CJK. Why not?
>
> James Seng: What I'm hearing is that the authors should do a
> cost/benefit analysis, but it is clear the draft is not ready to move
> forward.
>
> Erik Nordmark: Can someone do a pro/con analysis draft, or someone do
pro and
> someone con, to help drive the discussion on the mailing list?
>
> Paul Hoffman: Let's make Adam [Costello] do it. [laughter]
>
> Kilnam Chon: This straw poll process isn't really valid because not
> enough representation from people for whom this is really important.
> There's always a trade-off.
>
> James Seng: Could someone who voted against the lsb draft just explain
> why you are against it?
>
> Paul: I'd rather someone else did, but I will ... the reordering draft
> is somewhat of a hack to optimize for certain scripts, but it is at
> the cost of other scripts, isn't really generalized, and there has
> been no analysis of how beneficial it is for DUDE and AMC-ACE-Z.
>
> Dongman Lee: The author was not trying to propose this as a
> generalized mechanism.  It is not surprising that since CJK is driving
> internationalization, that proposals would be specific to that.
>
> Ted Hardie: As Paul pointed out, this has different effects on
> different scripts, but now that we are focused on one ACE we can ask
> more specifically for the authors to focus on just how it affects
> AMC-ACE-Z.
>
> Concensus: discuss the reordering on mailing list and request authors
>   of ACE and reordering to come to a proposal with analysis.
>
> ================================================================
>
> MATCHING (NAMEPREP)
>
> - Need for a standardized pre-processing step regardless of what IDN
>     protocol we choose?
>     Yes      lot of hands
>     No       one hand
>
> (Discussion clarified the question from the original.)
>
> Other comments:
>
> Patrik Faltstrom: Doesn't preclude other pre-processing before it,
> which some people have worried it would.  But even so, IETF really
> needs to have one standard way of processing Unicode.
>
> James Seng: When you say one standard way, do you mean one with
flexibility
> for locale, or essentially fixed?
>
> Patrik Falstrom: Essentially fixed.
>
> Dave Crocker: I thank Patrik for his comments that helped clarify
> things for me.  I used to be resistant to it, but am coming to accept
> it.  It is quite a bit like the case-insensitive/sensitive thing we're
> so used to in ASCII.  There are two processes here: case-mapping and
> determining the legal character set.  Keep them cleanly separate.
>
> ? Russell:
>
> Wenhui Zhang: Should have a standard that includes where local issues
> can be defined, which can include their standarized pre-processing.
>
> ?: Goal of working group is noble, but are trying to kill all the
> birds with one stone, and so we need a really large stone.  So many
> legacy systems are optimized for their local languages, and will have
> a lot of pain to switch to what is being planned.  They don't have
> much of a voice here, those who are going to suffer most.
>
> ?: Look into what happened in the LDAP group, how they ended up with a
> bunch of language-specific things.  It is difficult, but it can be
> done, and since it has already been solved, build on it.
>
> Erik Nordmark: Can we get back on the topic of this question?  We seem
to be
> wandering into the general requirements area.
>
> POLL: Many to 1 in favour of standard pre-processing step.
>
> Post poll:
>
> John Klensin: I can agree that a standard pre-processing step is
> needed, but I can't agree if that necessarily means having a single
> binary result even in ambiguous situations.  Very concerned about
that.
> This working group might be resulting in something that is totally
> irrelevant.
>
> Eric Brunner-Williams: The ambiguity need not exist in "uniprep" (the
> first of the stages observed by Dave Crocker), the problem arises in
> the other part.
>
> Paul: I think we should now work toward an architecture that includes
> pre-nameprep, nameprep and post-nameprep.  The middle one can be
> generally standardized while the other stages need not be.
>
> Erik Nordmark: Addressing John's concern of irrelevance, I can see how
> this work would eventually be superseded by something better, but that
> doesn't mean we have to stop doing this very useful work now.
>
> Dave Crocker: Dealing with "language" is out of scope for this group,
this
> working group should just be about expanding the set of strings that
> are usable as domain names.  In that context canonicalization makes a
> lot of sense, but not when we start talking about natual language.
>
> Ted Hardie: I have to take exception to Paul describing a system that
> is not standarized end-to-end; it can't include processing that is not
> standardized.  Also agree with Dave that we can't work with natural
> language, we don't have the expertise.
>
> ?: Rigorously avoid natural languages.
>
> Eric Chen: We need to consider natual language!
>
> Dave Crocker: The scope is very narrow and does not include languages.
>
> Harald: "Yes."
>
> Paul Hoffman: Please defer all questions of language, there will be a
draft
> soon that addresses where it should be addressed.
>
> Next step will be for the authors to clarify the relation between
> the various proposals for processing into a cohesive architecture,
> namely nameprep, tsconv, jpchar, hangeulchar.
>
> ================================================================
>
> PROTOCOL PROPOSALS, Dave Crocker
>
> Dave's Disclaimers:
> - System oriented person
> - Not a Unicode expert, or even naif
> - Entirely biased -- wanted to be objective, but failed
>
> IDN Task:
> - Enhance range of domain names that are useful
> - Not human "name"
> - Not "language"
> - Has no sets
> - Requires: fairness, efficiency, reliability, transition, ...
>
> The Usual Suspects:
>       Encoding            Approach
> 1. ACE only             IDNA
> 2. UTF-8 only           IDNA-mod, uDNS
> 3. ACE then UTF-8       IDNA-mod, uDNS
> 4. ACE & UTF-8 both     uDNS, uNAME
> 5. Anything goes        uNAME
>
> Encoding efficiency:
> - ACE is an encoding scheme
> - UTF-8 is an encoding scheme
> - Both map many bits to a variable length string
> - All variable length strings are unfair to some poeple
> - Fair vs unfair unfairness:
>     - longer mapping mean shorter names
>     - shorter names restricted to information dense character sets
>
> Encoding comparison:
> 1. ACE is three minuses bad.
> 2. UTF-8  is two minuses bad.
>
> Charts showing that there are a lot of modules in both systems, and we
> have to worry about all the modules in both systems.
>
> ACE has an extraordinarily minimal amount of change necessary to make
> an IDN useful, just two applications.  This is about as good a
> transition scheme as you can possibly get.
>
> UTF-8 is an extreme in the opposite direction, it requires that
> everything work end-to-end.
>
> 1. ACE only four pluses good
> 2. UTF-8 only five minuses bad
>
> Transition Interactions:
> ----------------------------------------------------------------------
---
> ----------------------------------------------------------------------
---
>                   Client->  Server->           ACE              UTF-8
>                   Server    Client
> ----------------------------------------------------------------------
---
> 1. old client   old dn    new dn          transparent     UTF-8 and
ACE
>      new server                                           maybe break
client
> ----------------------------------------------------------------------
---
> 2. new client,  new dn    old dn          transparent     break
server?
>      old server
> ----------------------------------------------------------------------
---
> ----------------------------------------------------------------------
---
>
> Specification comparison:
>
> ----------------------------------------------------------------------
---
> ----------------------------------------------------------------------
---
>                   Efficiency          Transition
Risk/Operational
>                                                               Expense
> ----------------------------------------------------------------------
---
> IDNA (ACE)     bad(data)            automatic               none
> ----------------------------------------------------------------------
---
>                                       how to detect
> uDNS (UTF-8)   poor(data)           when to use ACE?        high
>                                       (poorly defined
>                                       and not realistic)
> ----------------------------------------------------------------------
---
>                                       unstated
> uName (both)   bad (round trip)     (and based on CNRP,     very, very
>                                       with no meaningful      high
>                                       deployment)
> ----------------------------------------------------------------------
---
> ----------------------------------------------------------------------
---
>
> Olafur: Hard for me to say this to you Dave, given our history, but
> good job.
>
> Harald: Think you underestimate the cost of ACE a bit, in that leakage
> will confuse users.  But UTF-8 leakage will also confuse users, but
> likely even a bit more! But the ranking is still good.
>
> Paul: uName doesn't actually have CNRP in it; it was put in the draft
> and then explicitly shot down in the draft.  It uses a new RR, but the
> end result is pretty much the same as far as your conclusions go.
>
> Erik Nordmark: Can we vote on it without a UTF-8 draft in the pool?
> Would need a draft very fast.
>
> Poll:
> - idna?
>     Yes   Most
>     No    Some
> - udns?
>     Yes   Few
>     No    Most
> - uname?
>     Yes   Few
>     No    Most
>
> Interpretation by Harald and Marc was that: IDNA was the only strongly
> supported proposal in the room and the other two had
> strong opposition. Interpretation was agreed by the floor.
>
> Nameprep discussion back (some time remaining)
>
> Paul Hoffman: Good (from a marketing sense) user interfaces will do a
lot of
> mucking with input.  Really should have it defined how and where they
> can do that. If you change machine, different local translation
> tables can yield different names.
>
> James Seng: It can be very hard to determine what local conversion
> option to turn on. Not sure if this wg has capability to deal
> with codepoint matching. We need to reference code points outside
> the IETF, at Unicode Consortium.
>
> Paul Hoffman: Unicode has put mapping tables out of scope.
>
> Harald Alvestrand: This working group is internationalized access to
domain
> names, not localized.  This group is trying to specialize what a
> client must do no matter where it is in the world.  I would accept a
> statement that the relationship between the pre-processing drafts.  It
> has to be made mandatory though or it should not be part of the output
> of this group.
>
> Wenhui Zheng: IDNA draft should be explicit where the local
> interface/mapping should be done.
>
> Eric Chen: We have built a house and opened some gates but not others.
> Some languages can come in and others can not. IDNA should open its
> gate to allow other languages to do their thing.
>
> ================================================================
> NEXT STEPS
>
> - AMC-ACE-Z as chosen ACE.
> - Reordering to be discussed on mailing list.
> - relation between nameprep/tsconv/hanguelchar/jpchar/stringprep
>     to be consolidated into one architecture.
> - Go forward with IDNA.
>
>
>




From owner-idn@ops.ietf.org  Wed Aug 22 01:24: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 BAB11726
	for <idn-archive@lists.ietf.org>; Wed, 22 Aug 2001 01:24:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ZQFn-000HEA-00
	for idn-data@psg.com; Tue, 21 Aug 2001 22:08:35 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ZQFm-000HE4-00
	for idn@ops.ietf.org; Tue, 21 Aug 2001 22:08:34 -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 WAA16810;
	Tue, 21 Aug 2001 22:08:27 -0700
Message-Id: <5.1.0.14.2.20010821220717.0373d008@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 21 Aug 2001 22:08:37 -0700
To: "James Seng/Personal" <James@Seng.cc>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] ietf london idn wg meeting minutes
Cc: <idn@ops.ietf.org>, "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>
In-Reply-To: <049001c12abb$c80c8840$dd00a8c0@jamessonyvaio>
References: <5.1.0.14.1.20010821122941.03451718@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 08:37 PM 8/21/2001, James Seng/Personal wrote:
>The minutes is combination of notes from David Lawrence and Donald E.
>Eastlake. Thanks for been the wg scribes.

The minutes have much more detail than is usual.  How the heck did they 
manage to type that fast?

In fact the notes are so good that I'm tempted to complain that they should 
report what each speaker ate for lunch...

d/


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




From owner-idn@ops.ietf.org  Wed Aug 22 07:23: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 HAA29880
	for <idn-archive@lists.ietf.org>; Wed, 22 Aug 2001 07:23:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ZVm3-000CFZ-00
	for idn-data@psg.com; Wed, 22 Aug 2001 04:02:15 -0700
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ZVm2-000CF8-00
	for idn@ops.ietf.org; Wed, 22 Aug 2001 04:02:14 -0700
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29291;
	Wed, 22 Aug 2001 07:00:55 -0400 (EDT)
Message-Id: <200108221100.HAA29291@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: idn@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [idn] I-D ACTION:draft-ietf-idn-amc-ace-z-00.txt
Date: Wed, 22 Aug 2001 07:00:55 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: AMC-ACE-Z version 0.3.0
	Author(s)	: A. Costello
	Filename	: draft-ietf-idn-amc-ace-z-00.txt
	Pages		: 
	Date		: 21-Aug-01
	
AMC-ACE-Z is a simple and efficient ASCII-Compatible Encoding (ACE)
designed for use with Internationalized Domain Names [IDN] [IDNA].
It uniquely and reversibly transforms a Unicode string [UNICODE]
into an ASCII string.  ASCII characters in the Unicode string are
represented literally, and non-ASCII characters are represented
by ASCII characters that are allowed in hostname labels (letters,
digits, and hyphens).  Bootstring is a general algorithm that allows
a string of basic code points to uniquely represent any string of
code points drawn from a larger set.  AMC-ACE-Z is an instance
Bootstring that uses particular parameter values appropriate for
IDNA and uses an IDNA signature prefix (or suffix).  This document
specifies Bootstring and the parameter values for AMC-ACE-Z.

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Thu Aug 23 21: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 VAA06138
	for <idn-archive@lists.ietf.org>; Thu, 23 Aug 2001 21:57:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15a5qZ-000M2A-00
	for idn-data@psg.com; Thu, 23 Aug 2001 18:33:19 -0700
Received: from mail1.ics.ntts.co.jp ([202.32.24.45])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15a5qX-000M24-00
	for idn@ops.ietf.org; Thu, 23 Aug 2001 18:33:18 -0700
Received: from mail26.silk.ntts.co.jp by mail1.ics.ntts.co.jp (8.9.3/3.7W-NTTSOFT-SUR2.0)
	id KAA51049; Fri, 24 Aug 2001 10:33:12 +0900 (JST)
Received: from daemon.inl.ntts.co.jp by mail26.silk.ntts.co.jp (8.11.4/3.7W-silk-4.4)
	id f7O1XBR14938; Fri, 24 Aug 2001 10:33:12 +0900 (JST)
Received: (qmail 56501 invoked by alias); 24 Aug 2001 10:33:12 +0900
Received: (qmail 56493 invoked from network); 24 Aug 2001 10:33:11 +0900
Received: from daemon.inl.ntts.co.jp (HELO localhost)
  by daemon.inl.ntts.co.jp with SMTP; 24 Aug 2001 10:33:11 +0900
To: idn@ops.ietf.org
Subject: Re: [idn] Test Prefix for AMC-ACE-Z
In-Reply-To: <3CD14E451751BD42BA48AAA50B07BAD60B84B0@vsvapostal3.prod.netsol.com>
References: <3CD14E451751BD42BA48AAA50B07BAD60B84B0@vsvapostal3.prod.netsol.com>
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: <20010824103308U.yone@po.ntts.co.jp>
Date: Fri, 24 Aug 2001 10:33:08 +0900 (JST)
From: Yoshiro YONEYA <yone@po.ntts.co.jp>
X-Dispatcher: imput version 20000228(IM140)
Lines: 25
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Subject: [idn] Test Prefix for AMC-ACE-Z
Date: Fri, 17 Aug 2001 09:18:22 -0400

> The secondary IDN WG web page [1] includes a registry of prefixes for
> testing ACEs.  Two prefixes are currently identified: "bq--" for RACE and
> "dq--" for DUDE.  AMC-ACE-Z is gaining a measure of acceptance, but no
> prefix has been identified for testing.
> 
> Has anyone been testing with a particular prefix?  If not, I'd like to
> propose use of "za--" as a test prefix for AMC-ACE-Z.

I basically agree with your idea but I it should be differ from
existing ccTLDs to avoid confusion.  Unfortunately 'ZA' is ccTLD of
South Africa, so something other prefix such as "zq--" seems
preferable.

BTW, AMC-ACE-Z is tentative name, so choosing good name for AMC-ACE-Z
is also important discussion item, isn't it?

-- 
Yoshiro YONEYA <yone@po.ntts.co.jp>
           aka <yone@nic.ad.jp>



From owner-idn@ops.ietf.org  Fri Aug 24 07: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 HAA29556
	for <idn-archive@lists.ietf.org>; Fri, 24 Aug 2001 07:25:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15aEkE-0003ZY-00
	for idn-data@psg.com; Fri, 24 Aug 2001 04:03:22 -0700
Received: from heron.verisign.com ([216.168.233.95])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15aEkE-0003ZS-00
	for idn@ops.ietf.org; Fri, 24 Aug 2001 04:03:22 -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 HAA19797
	for <idn@ops.ietf.org>; Fri, 24 Aug 2001 07:03:20 -0400 (EDT)
Received: by VSVAPOSTALGW1.prod.netsol.com with Internet Mail Service (5.5.2653.19)
	id <NP4F73K4>; Fri, 24 Aug 2001 07:02:52 -0400
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD6C5F9A1@vsvapostal3.prod.netsol.com>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: idn@ops.ietf.org
Subject: RE: [idn] Test Prefix for AMC-ACE-Z
Date: Fri, 24 Aug 2001 06:57:27 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

>-----Original Message-----
>From: Yoshiro YONEYA [mailto:yone@po.ntts.co.jp]
>Sent: Thursday, August 23, 2001 9:33 PM
>To: idn@ops.ietf.org
>Subject: Re: [idn] Test Prefix for AMC-ACE-Z
>
>
>> Has anyone been testing with a particular prefix?  If not, I'd like to
>> propose use of "za--" as a test prefix for AMC-ACE-Z.
>
>I basically agree with your idea but I it should be differ from
>existing ccTLDs to avoid confusion.  Unfortunately 'ZA' is ccTLD of
>South Africa, so something other prefix such as "zq--" seems
>preferable.

I'd be OK with something other than za--, as long as something is agreed
upon.

>BTW, AMC-ACE-Z is tentative name, so choosing good name for AMC-ACE-Z
>is also important discussion item, isn't it?

Probably, but perhaps more appropriate if/when the WG decides to push it
forward to the IESG?

<Scott/>



From owner-idn@ops.ietf.org  Sun Aug 26 08:49: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 IAA11600
	for <idn-archive@lists.ietf.org>; Sun, 26 Aug 2001 08:49:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15aywm-000FuL-00
	for idn-data@psg.com; Sun, 26 Aug 2001 05:23:24 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15aywl-000FuE-00
	for idn@ops.ietf.org; Sun, 26 Aug 2001 05:23:23 -0700
Received: from terra (terra.malmo.trab.se [131.115.48.22]) by malmo.trab.se (8.10.1/TRAB-primary-2) with SMTP id f7QCLSP08191 for <idn@ops.ietf.org>; Sun, 26 Aug 2001 14:21:28 +0200 (MEST)
Message-Id: <200108261221.f7QCLSP08191@malmo.trab.se>
Date: Sun, 26 Aug 2001 14:25:00 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: [idn] ietf london idn wg meeting minutes
To: idn@ops.ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: D8f2kIEDP3kGsPDxfgZx7g==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk


>included is the first version of the idn wg meeting minutes.

Thanks. Reading through it I have several questions and see
incorrect statements. They are in the text below.

Does any of you who were at the meeting have any comments on
what happened related to IDN outside the session?



>ACE EVALUATION WITH IDNs ALREADY REGISTERED, Yoshiro Yoneya
>
>- Most important evaluation criterion to study is to maximize number
>   of characters, raw speed is less important because nameprep is the
>   slow stage.

This is not correct in general. At my site which uses the Latin-1 subset
of UCS, most ACE encodings are a very expensive step compared to nameprep.


>MATCHING (NAMEPREP)
>
>- Need for a standardized pre-processing step regardless of what IDN
>    protocol we choose?
>    Yes      lot of hands
>    No       one hand
>

I am not sure what you discussed to do in the pre-processing step.
The minimum mandatory pre-processing step should be normalisation
to Uncode form C.

To match two labels in DNS you should do:
1) Start with the normalised name.
2) Form-fold the name
3) Binary compare.

Form-folding may not remove any character that is suitable in a name
(any name includeing host names). Only an application may reject a name due to
unsuitable characters for the specific type of name.

In the context of nameprep some talk about canonicalisation.
What is a canonical name?
In RFC 1035 a CNAME record defines the canonical name for an alias.
From this I get that the canonical name is not the same as the
form-folded name. A canonical name may include mixed case and other
forms not significant in matching.


>Other comments:
>
>Patrik Faltstrom: Doesn't preclude other pre-processing before it,
>which some people have worried it would.  But even so, IETF really
>needs to have one standard way of processing Unicode.

Is DNS going to use the standard IETF way of handling UCS or a special
type? Nameprep as it is defined to day is not fit to be used for
other places except matching of "host names".



>================================================================
>
>PROTOCOL PROPOSALS, Dave Crocker
>

>
>Encoding efficiency:
>- ACE is an encoding scheme

It is much more. UTF-8 is a character encoding scheme. Most ACE today
is a character compression scheme followed by a binary data to ASCII
encoding scheme.


>    - longer mapping mean shorter names

Not really. Just use a long label type in DNS.



>
>ACE has an extraordinarily minimal amount of change necessary to make
>an IDN useful, just two applications.  This is about as good a
>transition scheme as you can possibly get.

Well, using plain UTF-8 you also only need two applications. So it is just
as good in that sense.

>
>UTF-8 is an extreme in the opposite direction, it requires that
>everything work end-to-end.

Not at all! A very simple UTF-8 with every thing form-folded is just like
ACE. A more well working solution with support for ACE when needed and
less requirement of the applications, only need support in two applications
and the authorative DNS servers for the domain queried.

>
>1. ACE only four pluses good
>2. UTF-8 only five minuses bad

No, UTF-8 is about the same as ACE. ACE as used in IDNA also has the
negative aspect that it requires form-folded names.



>
>Transition Interactions:
>-------------------------------------------------------------------------
>-------------------------------------------------------------------------
>                  Client->  Server->           ACE              UTF-8
>                  Server    Client
>-------------------------------------------------------------------------
>1. old client   old dn    new dn          transparent     UTF-8 and ACE
>     new server                                           maybe break client
>-------------------------------------------------------------------------
>2. new client,  new dn    old dn          transparent     break server?
>     old server
>-------------------------------------------------------------------------
>-------------------------------------------------------------------------

UTF-8 will not break server or client, if combined with ACE. Without ACE
it will break some clients.

>
>Specification comparison:
>-------------------------------------------------------------------------
>                  Efficiency          Transition           Risk/Operational
>                                                              Expense
>-------------------------------------------------------------------------
>IDNA (ACE)     bad(data)            automatic               none
>-------------------------------------------------------------------------
>                                      how to detect
>uDNS (UTF-8)   poor(data)           when to use ACE?        high
>                                      (poorly defined
>                                      and not realistic)
>-------------------------------------------------------------------------
I do not understand the comment about UDNS above. To me, who has
a deep technical background, there is low or none in operational risk
and there are no problems to detect when to use ACE.



When many compares IDNA (ACE) with UDNS they think it is very bad that
UDNS requires modifications in the DNS protocol and DNS server.
Why?
If you do not want to change the DNS protocol/DNS servers you will never
get DNSSEC, never be able to use IPv6, never be able to use new record
types like SRV or DNAME.

I cannot understand the resistance against updating the DNS protocol to
support non-ASCII in a complete and consisten way. Instead some want to
add non-ASCII support by just do it for "host names" and do it by adding
an additional layer on top of the DNS protocol.


I have since the start of the IDN discussions worked for an update of DNS,
just like DNSSEC and others. And I have for a long time felt that many
do not want to go there. Should we move the UDNS and other protocol
changing drafts over to DNSEXT and leave the non-DNS-protocol IDNA here?
For me the IDNA way will always be an incomplete solution and impossible
for me to support in a good way without changing my DNS servers.

   Dan




From owner-idn@ops.ietf.org  Sun Aug 26 10:02: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 KAA12707
	for <idn-archive@lists.ietf.org>; Sun, 26 Aug 2001 10:02:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15b0NC-000GtX-00
	for idn-data@psg.com; Sun, 26 Aug 2001 06:54:46 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15b0NB-000GtR-00
	for idn@ops.ietf.org; Sun, 26 Aug 2001 06:54:46 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 64213FFC01; Sun, 26 Aug 2001 21:55:58 +0800 (SGT)
Message-ID: <052d01c12e36$a60965f0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Dan Oscarsson" <Dan.Oscarsson@trab.se>, <idn@ops.ietf.org>
References: <200108261221.f7QCLSP08191@malmo.trab.se>
Subject: Re: [idn] ietf london idn wg meeting minutes
Date: Sun, 26 Aug 2001 21:54: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

> >ACE EVALUATION WITH IDNs ALREADY REGISTERED, Yoshiro Yoneya
> >
> >- Most important evaluation criterion to study is to maximize number
> >   of characters, raw speed is less important because nameprep is the
> >   slow stage.
>
> This is not correct in general. At my site which uses the Latin-1
subset
> of UCS, most ACE encodings are a very expensive step compared to
nameprep.

I am curious about this statement. Do you have any numbers for this?

You see, all datas from other sources, from Verisign, i-DNS.net, JPNIC
etc who have done Nameprep-ACE/UTF-8 have clearly shown that Nameprep ~=
10xACE in terms of CPU time.

http://www.i-d-n.net/ietf50/idn-minneapolis-implementors-zhuyu.ppt
http://www.i-d-n.net/ietf50/idn-implementors-colosi.ppt

ps: Sorry, only PPT since that is the presentation material given to us
by the presenter.

-James Seng




From owner-idn@ops.ietf.org  Sun Aug 26 10:49: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 KAA13299
	for <idn-archive@lists.ietf.org>; Sun, 26 Aug 2001 10:49:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15b13v-000HT5-00
	for idn-data@psg.com; Sun, 26 Aug 2001 07:38:55 -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 15b13u-000HSz-00
	for idn@ops.ietf.org; Sun, 26 Aug 2001 07:38:54 -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 f7QEZ1N38685;
	Sun, 26 Aug 2001 10:35:01 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200108261435.f7QEZ1N38685@nic-naa.net>
To: Dan Oscarsson <Dan.Oscarsson@trab.se>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] ietf london idn wg meeting minutes 
In-Reply-To: Your message of "Sun, 26 Aug 2001 14:25:00 +0200."
             <200108261221.f7QCLSP08191@malmo.trab.se> 
Date: Sun, 26 Aug 2001 10:35:01 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Morning Dan,

> Does any of you who were at the meeting have any comments on
> what happened related to IDN outside the session?

Hmm. Broad question. Could you be more specific?

> In the context of nameprep some talk about canonicalisation.

I don't think the reference is to CNAMEs.

>> [Patrik's comment, the general apps requirement (IMO under-specified)
>> and the idn requirement (IMO over-specified), harmonized.]
>
> Is DNS going to use the standard IETF way of handling UCS or a special
> type? Nameprep as it is defined to day is not fit to be used for
> other places except matching of "host names".

This was the subject of some jack-in-the-box back-and-forth to the mic on
my part. There is the "uniprep" problem, and layered on top that is the
"nameprep" problem.

In Marc's notes this was captured as "unichar" and the note about the tscconv
and similar range-specific drafts.

>                      ... Should we move the UDNS and other protocol
> changing drafts over to DNSEXT and leave the non-DNS-protocol IDNA here?

Erik Nordmark asked me to copy our eventual (sorry, I've got provreg, whois,
some related work a bunch of icann stuff, and a registry to take "live" to do
also) utf draft to this WG. 

We've set up a utf list, implementors welcome, just drop me a line.

Eric



From owner-idn@ops.ietf.org  Sun Aug 26 15:46: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 PAA15193
	for <idn-archive@lists.ietf.org>; Sun, 26 Aug 2001 15:46:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15b5bi-000KqC-00
	for idn-data@psg.com; Sun, 26 Aug 2001 12:30:06 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15b5bh-000Kq6-00
	for idn@ops.ietf.org; Sun, 26 Aug 2001 12:30:06 -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 f7QJtDQ32390;
	Sun, 26 Aug 2001 15:55:13 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010826103546.021720c8@127.0.0.1>
X-Sender: blanchet@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 26 Aug 2001 15:31:54 -0400
To: Dan Oscarsson <Dan.Oscarsson@trab.se>, idn@ops.ietf.org
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: Re: [idn] ietf london idn wg meeting minutes
In-Reply-To: <200108261221.f7QCLSP08191@malmo.trab.se>
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/À 14:25 2001-08-26 +0200, Dan Oscarsson you wrote/vous écriviez:

> >included is the first version of the idn wg meeting minutes.
>
>Thanks. Reading through it I have several questions and see
>incorrect statements.


to my knowledge you were not present at the wg session, so when you say: 
"incorrect statements", you mean that you disagree with what was said 
during the meeting, but you are not saying that this is incorrect minutes.


>They are in the text below.
>
>Does any of you who were at the meeting have any comments on
>what happened related to IDN outside the session?

While any useful information for the discussion of the wg is always 
welcome, here again, these activities outside the idn session would not be 
included in the meeting minutes.


> >ACE EVALUATION WITH IDNs ALREADY REGISTERED, Yoshiro Yoneya
> >
> >- Most important evaluation criterion to study is to maximize number
> >   of characters, raw speed is less important because nameprep is the
> >   slow stage.
>
>This is not correct in general. At my site which uses the Latin-1 subset
>of UCS, most ACE encodings are a very expensive step compared to nameprep.

that is not what we heard from most implementors. Maybe there is an 
understanding problem with the statement. I try to explain: the ACE cpu 
processing is much much less than the Nameprep cpu processing.



> >MATCHING (NAMEPREP)
> >
> >- Need for a standardized pre-processing step regardless of what IDN
> >    protocol we choose?
> >    Yes      lot of hands
> >    No       one hand
> >
>
>I am not sure what you discussed to do in the pre-processing step.

none. just making sure that we agree on a pre-processing step. The actual 
details of the step was discussed after.


>The minimum mandatory pre-processing step should be normalisation
>to Uncode form C.
>
>To match two labels in DNS you should do:
>1) Start with the normalised name.
>2) Form-fold the name
>3) Binary compare.
>
>Form-folding may not remove any character that is suitable in a name
>(any name includeing host names). Only an application may reject a name due to
>unsuitable characters for the specific type of name.
>
>In the context of nameprep some talk about canonicalisation.
>What is a canonical name?
>In RFC 1035 a CNAME record defines the canonical name for an alias.
> >From this I get that the canonical name is not the same as the
>form-folded name. A canonical name may include mixed case and other
>forms not significant in matching.
>
>
> >Other comments:
> >
> >Patrik Faltstrom: Doesn't preclude other pre-processing before it,
> >which some people have worried it would.  But even so, IETF really
> >needs to have one standard way of processing Unicode.
>
>Is DNS going to use the standard IETF way of handling UCS or a special
>type? Nameprep as it is defined to day is not fit to be used for
>other places except matching of "host names".


it was said that the current nameprep authors (Paul and I) were already 
working on a stringprep document which will discuss about i18n string 
preparation. But this would be a generalized nameprep that could be used by 
other apps/protocols. But the stringprep work is outside of the wg charter.





> >================================================================
> >
> >PROTOCOL PROPOSALS, Dave Crocker
> >
>
> >
> >Encoding efficiency:
> >- ACE is an encoding scheme
>
>It is much more. UTF-8 is a character encoding scheme. Most ACE today
>is a character compression scheme followed by a binary data to ASCII
>encoding scheme.
>
>
> >    - longer mapping mean shorter names
>
>Not really. Just use a long label type in DNS.
>
>
>
> >
> >ACE has an extraordinarily minimal amount of change necessary to make
> >an IDN useful, just two applications.  This is about as good a
> >transition scheme as you can possibly get.
>
>Well, using plain UTF-8 you also only need two applications. So it is just
>as good in that sense.
>
> >
> >UTF-8 is an extreme in the opposite direction, it requires that
> >everything work end-to-end.
>
>Not at all! A very simple UTF-8 with every thing form-folded is just like
>ACE. A more well working solution with support for ACE when needed and
>less requirement of the applications, only need support in two applications
>and the authorative DNS servers for the domain queried.
>
> >
> >1. ACE only four pluses good
> >2. UTF-8 only five minuses bad
>
>No, UTF-8 is about the same as ACE. ACE as used in IDNA also has the
>negative aspect that it requires form-folded names.
>
>
>
> >
> >Transition Interactions:
> >-------------------------------------------------------------------------
> >-------------------------------------------------------------------------
> >                  Client->  Server->           ACE              UTF-8
> >                  Server    Client
> >-------------------------------------------------------------------------
> >1. old client   old dn    new dn          transparent     UTF-8 and ACE
> >     new server                                           maybe break client
> >-------------------------------------------------------------------------
> >2. new client,  new dn    old dn          transparent     break server?
> >     old server
> >-------------------------------------------------------------------------
> >-------------------------------------------------------------------------
>
>UTF-8 will not break server or client, if combined with ACE. Without ACE
>it will break some clients.
>
> >
> >Specification comparison:
> >-------------------------------------------------------------------------
> >                  Efficiency          Transition           Risk/Operational
> >                                                              Expense
> >-------------------------------------------------------------------------
> >IDNA (ACE)     bad(data)            automatic               none
> >-------------------------------------------------------------------------
> >                                      how to detect
> >uDNS (UTF-8)   poor(data)           when to use ACE?        high
> >                                      (poorly defined
> >                                      and not realistic)
> >-------------------------------------------------------------------------
>I do not understand the comment about UDNS above. To me, who has
>a deep technical background, there is low or none in operational risk
>and there are no problems to detect when to use ACE.
>
>
>
>When many compares IDNA (ACE) with UDNS they think it is very bad that
>UDNS requires modifications in the DNS protocol and DNS server.
>Why?
>If you do not want to change the DNS protocol/DNS servers you will never
>get DNSSEC, never be able to use IPv6,

AAAA records are in bind since 4.9.5 and this was documented in RFC 1886, 
December 1995.
A6, bitlabels and dname have recently been moved to experimental.

>  never be able to use new record
>types like SRV or DNAME.


some dns records can be used without a full and complete deployment.


>I cannot understand the resistance

it is not "resistance". it is a compromise.  no proposal on the table is 
perfect. all have pros and cons.

>against updating the DNS protocol to
>support non-ASCII in a complete and consisten way. Instead some want to
>add non-ASCII support by just do it for "host names" and do it by adding
>an additional layer on top of the DNS protocol.
>
>
>I have since the start of the IDN discussions worked for an update of DNS,

me too: draft-ietf-idn-idne-xx.txt

>just like DNSSEC and others. And I have for a long time felt that many
>do not want to go there.

hopefully all wg participants are openminded...

>Should we move the UDNS and other protocol
>changing drafts over to DNSEXT and leave the non-DNS-protocol IDNA here?

it is sure that any proposal that changes the DNS would have to be 
discussed in the DNSext wg.

>For me the IDNA way will always be an incomplete solution and impossible
>for me to support in a good way without changing my DNS servers.

for me idna is not a perfect solution, but has the best support in the wg 
among all proposals.


>    Dan

Marc.




From owner-idn@ops.ietf.org  Sun Aug 26 16: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 QAA15525
	for <idn-archive@lists.ietf.org>; Sun, 26 Aug 2001 16:37:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15b6Lj-000LTQ-00
	for idn-data@psg.com; Sun, 26 Aug 2001 13:17:39 -0700
Received: from friendly.realnames.com ([63.251.238.102])
	by psg.com with smtp (Exim 3.33 #1)
	id 15b6Li-000LTJ-00
	for idn@ops.ietf.org; Sun, 26 Aug 2001 13:17:38 -0700
Received: (qmail 13074 invoked from network); 27 Aug 2001 03:34:59 -0000
Received: from chubby.internal.realnames.com (HELO heaven.internal.realnames.com) (10.1.5.39)
  by friendly.realnames.com with SMTP; 27 Aug 2001 03:34:59 -0000
Received: From RINCON.INTERNAL.REALNAMES.COM (10.1.5.99[10.1.5.99 port:3388]) by heaven.internal.realnames.com
	Mail essentials (server 2.422) with SMTP id: <131408@heaven.internal.realnames.com>
	 for <Dan.Oscarsson@trab.se>; Sun, 26 Aug 2001 1:15:08 PM -0700
	smtpmailfrom <yves@realnames.com> 
Received: by rincon.centraal.com with Internet Mail Service (5.5.2650.21)
	id <RWB7C1D6>; Sun, 26 Aug 2001 13:17:01 -0700
Message-ID: <7FC3066C236FD511BC5900508BAC86FE07D10B@trestles.internal.realnames.com>
From: Yves Arrouye <yves@realnames.com>
To: "'Dan Oscarsson'" <Dan.Oscarsson@trab.se>, idn@ops.ietf.org
Subject: RE: [idn] ietf london idn wg meeting minutes
Date: Sun, 26 Aug 2001 13:14:46 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> I am not sure what you discussed to do in the pre-processing 
> step. The minimum mandatory pre-processing step should be 
> normalisation to Uncode form C.

I am not sure either but there seems to be a need for common rules that
would apply to the whole domain name, and not the hostname/label which is
what IDN works on. A common example is the need to map U+3002 IDEOGRAPHIC
FULL STOP (and others like U+FF0E FULLWIDTH FULL STOP) to U+002E FULL STOP
which is the only label separator.

> In the context of nameprep some talk about canonicalisation. 
> What is a canonical name? In RFC 1035 a CNAME record defines 
> the canonical name for an alias. From this I get that the 
> canonical name is not the same as the form-folded name. A 
> canonical name may include mixed case and other forms not 
> significant in matching.

Pretty sure it's not a CNAME but the end result of Nameprep. Its "canonical"
as reduced to its "canonical form" which is (according to Merriam-Webster)
"the simplest form of something," an internationalized DNS label in our
case.
 
YA



From owner-idn@ops.ietf.org  Sun Aug 26 21: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 VAA17018
	for <idn-archive@lists.ietf.org>; Sun, 26 Aug 2001 21:12:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15bAeG-000Oz5-00
	for idn-data@psg.com; Sun, 26 Aug 2001 17:53: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 15bAeF-000Oyq-00
	for idn@ops.ietf.org; Sun, 26 Aug 2001 17:53:03 -0700
Received: (qmail 26700 invoked by uid 1001); 27 Aug 2001 00:53:12 -0000
Date: 27 Aug 2001 00:53:12 -0000
Message-ID: <20010827005312.22073.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] The ACE myth redivivus
References: <5.1.0.14.1.20010821122941.03451718@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

It has already been established that some common practices, such as
copy-and-paste for domain names, will be broken by the (horribly
expensive) ACE transition.

This goes far beyond ``leakage,'' i.e., bad displays. Login connections
will fail. Web pages won't be loaded. Mail will bounce.

Dave Crocker nevertheless claims, in his comparison table, that ACE
carries no ``risk'' (and no ``operational expense''). That's the ACE
myth. Are we going to have to tear it to pieces _again_?

---Dan



From owner-idn@ops.ietf.org  Mon Aug 27 22:33: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 WAA08896
	for <idn-archive@lists.ietf.org>; Mon, 27 Aug 2001 22:33:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15bYRx-000Ltj-00
	for idn-data@psg.com; Mon, 27 Aug 2001 19:17:57 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15bYRw-000Ltb-00
	for idn@ops.ietf.org; Mon, 27 Aug 2001 19:17:57 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP id 144C6FFC09
	for <idn@ops.ietf.org>; Tue, 28 Aug 2001 10:19:09 +0800 (SGT)
Message-ID: <000501c12f67$a49527e0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: <idn@ops.ietf.org>
Subject: [idn] draft-duerst-iri-bidi-00
Date: Tue, 28 Aug 2001 10:17:52 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Something useful to read.

 http://www.ietf.org/internet-drafts/draft-duerst-iri-bidi-00.txt




From owner-idn@ops.ietf.org  Tue Aug 28 08: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 IAA07231
	for <idn-archive@lists.ietf.org>; Tue, 28 Aug 2001 08:30:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15bhm0-0005Z6-00
	for idn-data@psg.com; Tue, 28 Aug 2001 05:15:16 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15bhlz-0005Yz-00
	for idn@ops.ietf.org; Tue, 28 Aug 2001 05:15:15 -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 f7SCDNj01438; Tue, 28 Aug 2001 14:13:23 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Tue, 28 Aug 2001 14:15:10 +0200 (MEST) (MET)
Message-Id: <200108281215.OAA03094@valinor.malmo.trab.se>
Date: Tue, 28 Aug 2001 14:15:10 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: [idn] ietf london idn wg meeting minutes
To: idn@ops.ietf.org, James@Seng.cc
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Ui2ix+a8bPNh9HOnsET2OQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk


>> >ACE EVALUATION WITH IDNs ALREADY REGISTERED, Yoshiro Yoneya
>> >
>> >- Most important evaluation criterion to study is to maximize number
>> >   of characters, raw speed is less important because nameprep is the
>> >   slow stage.
>>
>> This is not correct in general. At my site which uses the Latin-1
>subset
>> of UCS, most ACE encodings are a very expensive step compared to
>nameprep.
>
>I am curious about this statement. Do you have any numbers for this?
>
>You see, all datas from other sources, from Verisign, i-DNS.net, JPNIC
>etc who have done Nameprep-ACE/UTF-8 have clearly shown that Nameprep ~=
>10xACE in terms of CPU time.

The nameprep step for Latin-1 is as simple as for ASCII. Even larger sets
of UCS where simple alphabets are used will have a very simple and
quick nameprep step.
For Latin-1 it is like for ASCII - it can be done with a simple table lookup.
To do ACE with compression includes much more work - just look at some of
the algorithms.

Note that I said subset. At my site I do not need to support more
than Latin-1. host names outside that scope will remain ACE. And if I implement
this support in my DNS server, it will also only need to support
Latin-1 when comparing names as I will only have latin-1-names in
my authorative domains.

   Dan 




From owner-idn@ops.ietf.org  Tue Aug 28 08:51: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 IAA08240
	for <idn-archive@lists.ietf.org>; Tue, 28 Aug 2001 08:51:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15biAq-00065F-00
	for idn-data@psg.com; Tue, 28 Aug 2001 05:40:56 -0700
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15biAp-000658-00
	for idn@ops.ietf.org; Tue, 28 Aug 2001 05:40:55 -0700
Received: from [209.187.148.217] (helo=P2)
	by bs.jck.com with esmtp (Exim 3.32 #1)
	id 15biAl-0009pr-00; Tue, 28 Aug 2001 12:40:51 +0000
Date: Tue, 28 Aug 2001 08:40:50 -0400
From: John C Klensin <klensin@jck.com>
To: Martin Duerst <duerst@w3.org>
cc: idn-nameprep@viagenie.qc.ca, idn@ops.ietf.org
Subject: [idn] Re: [idn-nameprep] nameprep and others: hangeulchar
Message-ID: <67868501.998988050@localhost>
In-Reply-To: <4.2.0.58.J.20010828123600.036705b0@133.27.195.38>
References:  <4.2.0.58.J.20010828123600.036705b0@133.27.195.38>
X-Mailer: Mulberry/2.1.0b3 (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, 28 August, 2001 12:48 +0900 Martin Duerst
<duerst@w3.org> wrote:

>...
> Overall, I think you are arguing on the base that fillers will
> only be used together with Hangul. But what if people find out
> that they can use it as a kind of space in other scripts?
>...

Just to reinforce Martin's question a bit, _this_ is one of the
key questions of which I fear we keep losing sight as we look at
languages (or even scripts) one at a time.  (Full IDN list
included, since I think there is a general principle here that
everyone should think about.)

Unless we write rules that I think would be unbelievably
complicated and ultimately unsuccessful, the implication of using

	* [most of] Unicode and
	
	* no language tagging on either queries or registrations

is that, if
    L is a character from Latin-1
    C is a character from a Cyrillic script
    H is a character from a Han script
    A is a character from an Arabic script
    K is a katakana character
each of them chosen without restriction from the characters of
those scripts that we permit,

nothing is going to prevent labels of ECHAK, or any of its
permutations.  And, in particular, as Martin indirectly
suggests, if we permit Jamo fillers ("f" below), or Arabic
breaks (non-joiners, "n"), we will almost certainly see
    LLLfLLLL  and
    CCCnCCCC
as people figure out that things they can think about as
embedded spaces are "better" than funny case rules for
catenating multiple-word phrases.

I also just realized (most of you are probably ahead of me),
that I have no idea how LLLAL (or HHHAH) would be rendered if
the character chosen for "A" has different glyphs depending on
its joining position.  But, fortunately, that one is not our
problem.

Arggh.
   john




From owner-idn@ops.ietf.org  Tue Aug 28 09:27: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 JAA09758
	for <idn-archive@lists.ietf.org>; Tue, 28 Aug 2001 09:27:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15bik5-0006kl-00
	for idn-data@psg.com; Tue, 28 Aug 2001 06:17:21 -0700
Received: from [217.13.28.204] (helo=eikenes.alvestrand.no)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15bik4-0006hF-00
	for idn@ops.ietf.org; Tue, 28 Aug 2001 06:17:21 -0700
Received: from [192.168.1.31] (eikenes.alvestrand.no [217.13.28.203])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 308C661C4C; Tue, 28 Aug 2001 15:15:37 +0200 (CEST)
Date: Tue, 28 Aug 2001 15:14:52 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: liana.ydisg@juno.com, phoffman@imc.org
Cc: idn@ops.ietf.org, James@Seng.cc
Subject: Re: [idn] amending [IDNA]?
Message-ID: <317586845.999011691@[192.168.1.31]>
In-Reply-To: <20010817.180326.-726309.0.liana.ydisg@juno.com>
References:  <20010817.180326.-726309.0.liana.ydisg@juno.com>
X-Mailer: Mulberry/2.1.0b3 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On 17. august 2001 18:03 -0700 liana.ydisg@juno.com wrote:

> The IDN-label protocol is:
>
> idn-label(input, tag-file, input-std, zonefile, idn-name)
> {
>   tag = find-tag(input, tag-file, input-std);
>   switch (tag)
> 	{

I take it "idn-label" is a procedure to convert an input string into an IDN 
label for use in the DNS.

could you please explain a little more where the tag-file, input-std and 
zonefile arguments to the IDN-label protocol come from?

are these local parameters at the client, or does this occur at a different 
place in the system?

I do not understand.

             Harald






From owner-idn@ops.ietf.org  Tue Aug 28 12:57: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 MAA15817
	for <idn-archive@lists.ietf.org>; Tue, 28 Aug 2001 12:57:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15blpz-000AY0-00
	for idn-data@psg.com; Tue, 28 Aug 2001 09:35:39 -0700
Received: from femail27.sdc1.sfba.home.com ([24.254.60.17])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15blpy-000AXu-00
	for idn@ops.ietf.org; Tue, 28 Aug 2001 09:35:38 -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 <20010828163537.VLRW23732.femail27.sdc1.sfba.home.com@c1340594a>;
          Tue, 28 Aug 2001 09:35:37 -0700
Message-ID: <009001c12fdf$79c1efd0$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "John C Klensin" <klensin@jck.com>, "Martin Duerst" <duerst@w3.org>
Cc: <idn-nameprep@viagenie.qc.ca>, <idn@ops.ietf.org>
References:  <4.2.0.58.J.20010828123600.036705b0@133.27.195.38> <67868501.998988050@localhost>
Subject: Re: [idn] Re: [idn-nameprep] nameprep and others: hangeulchar
Date: Tue, 28 Aug 2001 09:35:40 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Well, ECHAK.com (with the substituted characters) wouldn't make much sense.
But neither do the currently permissible following names (generated
randomly):

9XGD5RY4PT0ZAVD7BD3WFBZV4BPJMCRKVWNJBWUPW5SK5BC71E34SG3TF3GZY5Q.com
QWHU884UNCUFTAZLP5P4ZSLKZSYRU5AGS5QLHLRZWVKV3EZXXXE3IHEJCQ0K5AJ.com
H6L8JGU2WKV1RDHYSXBD64Q421T1CRSWPR79RRB0EHATZ23AOIMMB8KKK4NBOA1.com
AZ733L21J15Q2JE2V4XYK5Y4AQJ3I5K2E5OOMFXFQ7TOVBLF4GCJYY3F7PFS5EY.com
ON1HB4ZZEP9XCKNQJ3D2BQ0FM79OU1NEMIYB5FR6R84OBCJJHVAH1781JBKMY18.com
A96FH1ASKQ0W1V8MOQD8PDNWBARY2I5JU4A0IZWGYT2YS5A1308T49WTN9P2L4R.com
4N6YFZNQP7W9ZZYWTNIZKJRFJTFP44F60GW84M5SNGJ7QGIH986GH7SG1JMZPJ1.com
GI5XHTM3Q2SMHGXKGTNIJQBHJG1EJDSQDX6TCH5WKH53V4ZV9YAB5TUH685YNX6.com
3PS2XQFCELAB75GHOXLQZ9SAQWCIDOQU2U62Y4S7LB8EORL8QNFKRIR0BBY1Y2A.com
I3HFH8772PW3CE4NY7MVPITUNOS7Q3I4LBOZNLKM2JSMU8VS9ACWQKBYW10BJ5J.com

The questions we need to focus on are:

- matching. Do two strings represent the same underlying abstract
characters?
- prohibition. Which are the characters that are clearly unsuitable for
inclusion in IDNs.

I believe, as I have said before, that it is too difficult to separate out
the legitimate mixes of scripts and symbols from the 'questionable' ones for
us to do anything. And adding language tags would simply make it more
complicated, not less. (How much good does it do me to know that the second
of the above is French, not German?)

There are tricky edge cases that we need to discuss or get help with. But we
can't let the edge cases prevent us from delivering the 99.9999% solution.

For fillers and joiners, there are a reasonable solutions on the floor. One
may be optimal, but many will work just fine.

Mark
â€”â€”â€”â€”â€”

Î“Î½á¿¶Î¸Î¹ ÏƒÎ±Ï…Ï„ÏŒÎ½ â€” Î˜Î±Î»á¿†Ï‚
[http://www.macchiato.com]
----- Original Message -----
From: "John C Klensin" <klensin@jck.com>
To: "Martin Duerst" <duerst@w3.org>
Cc: <idn-nameprep@viagenie.qc.ca>; <idn@ops.ietf.org>
Sent: Tuesday, August 28, 2001 05:40
Subject: [idn] Re: [idn-nameprep] nameprep and others: hangeulchar


> --On Tuesday, 28 August, 2001 12:48 +0900 Martin Duerst
> <duerst@w3.org> wrote:
>
> >...
> > Overall, I think you are arguing on the base that fillers will
> > only be used together with Hangul. But what if people find out
> > that they can use it as a kind of space in other scripts?
> >...
>
> Just to reinforce Martin's question a bit, _this_ is one of the
> key questions of which I fear we keep losing sight as we look at
> languages (or even scripts) one at a time.  (Full IDN list
> included, since I think there is a general principle here that
> everyone should think about.)
>
> Unless we write rules that I think would be unbelievably
> complicated and ultimately unsuccessful, the implication of using
>
> * [most of] Unicode and
>
> * no language tagging on either queries or registrations
>
> is that, if
>     L is a character from Latin-1
>     C is a character from a Cyrillic script
>     H is a character from a Han script
>     A is a character from an Arabic script
>     K is a katakana character
> each of them chosen without restriction from the characters of
> those scripts that we permit,
>
> nothing is going to prevent labels of ECHAK, or any of its
> permutations.  And, in particular, as Martin indirectly
> suggests, if we permit Jamo fillers ("f" below), or Arabic
> breaks (non-joiners, "n"), we will almost certainly see
>     LLLfLLLL  and
>     CCCnCCCC
> as people figure out that things they can think about as
> embedded spaces are "better" than funny case rules for
> catenating multiple-word phrases.
>
> I also just realized (most of you are probably ahead of me),
> that I have no idea how LLLAL (or HHHAH) would be rendered if
> the character chosen for "A" has different glyphs depending on
> its joining position.  But, fortunately, that one is not our
> problem.
>
> Arggh.
>    john
>
>
>




From owner-idn@ops.ietf.org  Tue Aug 28 13:30: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 NAA16525
	for <idn-archive@lists.ietf.org>; Tue, 28 Aug 2001 13:30:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15bmRZ-000BKA-00
	for idn-data@psg.com; Tue, 28 Aug 2001 10:14:29 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15bmRY-000BK4-00
	for idn@ops.ietf.org; Tue, 28 Aug 2001 10:14:28 -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 KAA26394;
	Tue, 28 Aug 2001 10:14:15 -0700
Message-Id: <5.1.0.14.2.20010828101145.03129830@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 28 Aug 2001 10:14:22 -0700
To: John C Klensin <klensin@jck.com>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] Re: [idn-nameprep] nameprep and others: hangeulchar
Cc: Martin Duerst <duerst@w3.org>, idn-nameprep@viagenie.qc.ca,
        idn@ops.ietf.org
In-Reply-To: <67868501.998988050@localhost>
References: <4.2.0.58.J.20010828123600.036705b0@133.27.195.38>
 <4.2.0.58.J.20010828123600.036705b0@133.27.195.38>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 05:40 AM 8/28/2001, John C Klensin wrote:
>nothing is going to prevent labels of ECHAK, or any of its
>permutations.
>...
>I also just realized (most of you are probably ahead of me),
>that I have no idea how LLLAL (or HHHAH) would be rendered if


Why is it the job of an iDNS standard to prevent users from defining silly 
strings, as long as the strings do not break the DNS?


At 09:35 AM 8/28/2001, Mark Davis wrote:
>I believe, as I have said before, that it is too difficult to separate out
>the legitimate mixes of scripts and symbols from the 'questionable' ones for
>us to do anything. And adding language tags would simply make it more
>complicated, not less.

exactly correct.

Too difficult and, to paraphrase Jeff Case, simply not our 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 Aug 28 13:35: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 NAA16678
	for <idn-archive@lists.ietf.org>; Tue, 28 Aug 2001 13:35:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15bmZA-000BUj-00
	for idn-data@psg.com; Tue, 28 Aug 2001 10:22:20 -0700
Received: from lobo.nic.cc ([206.253.214.247] helo=mail.enic.cc)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15bmZA-000BUZ-00
	for idn@ops.ietf.org; Tue, 28 Aug 2001 10:22:20 -0700
Received: from enic.cc (tailback.enic.cc [206.253.214.252])
	by mail.enic.cc (Postfix) with ESMTP id 540746A904
	for <idn@ops.ietf.org>; Tue, 28 Aug 2001 10:22:21 -0700 (PDT)
Message-ID: <3B8BD347.6573D0AC@enic.cc>
Date: Tue, 28 Aug 2001 10:22:15 -0700
From: Dan Ebert <dan@enic.cc>
Organization: eNIC Corporation
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: idn@ops.ietf.org
Subject: Re: [idn] Re: [idn-nameprep] nameprep and others: hangeulchar
References: <4.2.0.58.J.20010828123600.036705b0@133.27.195.38> <67868501.998988050@localhost>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


While names like you describe (LLLfLLLL, CCCnCCCC, etc.) are possbile
... wouldn't they be rather difficult to type?  I suppose they could be
utilized as click on links, but it seems unlikely that the owner of such
a domain could reasonably expect a user to be able to enter the name in
a browser or email client, etc.  Is it easy to type a 'Jamo filler'
character from a Latin1 OS.  I don't think we should restrict/prohibit
this type of name, but I don't think we need to spend too much time
worrying about nameprep/ACE efficency issues regarding them.


-- 
Dan Ebert      <dan@enic.cc>       eNIC Corporation
------------------------------------------------------------
I've had a perfectly wonderful evening. But this wasn't it.
   -- Groucho Marx


John C Klensin wrote:
> 
> --On Tuesday, 28 August, 2001 12:48 +0900 Martin Duerst
> <duerst@w3.org> wrote:
> 
> >...
> > Overall, I think you are arguing on the base that fillers will
> > only be used together with Hangul. But what if people find out
> > that they can use it as a kind of space in other scripts?
> >...
> 
> Just to reinforce Martin's question a bit, _this_ is one of the
> key questions of which I fear we keep losing sight as we look at
> languages (or even scripts) one at a time.  (Full IDN list
> included, since I think there is a general principle here that
> everyone should think about.)
> 
> Unless we write rules that I think would be unbelievably
> complicated and ultimately unsuccessful, the implication of using
> 
>         * [most of] Unicode and
> 
>         * no language tagging on either queries or registrations
> 
> is that, if
>     L is a character from Latin-1
>     C is a character from a Cyrillic script
>     H is a character from a Han script
>     A is a character from an Arabic script
>     K is a katakana character
> each of them chosen without restriction from the characters of
> those scripts that we permit,
> 
> nothing is going to prevent labels of ECHAK, or any of its
> permutations.  And, in particular, as Martin indirectly
> suggests, if we permit Jamo fillers ("f" below), or Arabic
> breaks (non-joiners, "n"), we will almost certainly see
>     LLLfLLLL  and
>     CCCnCCCC
> as people figure out that things they can think about as
> embedded spaces are "better" than funny case rules for
> catenating multiple-word phrases.
> 
> I also just realized (most of you are probably ahead of me),
> that I have no idea how LLLAL (or HHHAH) would be rendered if
> the character chosen for "A" has different glyphs depending on
> its joining position.  But, fortunately, that one is not our
> problem.
> 
> Arggh.
>    john



From owner-idn@ops.ietf.org  Tue Aug 28 13:36: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 NAA16696
	for <idn-archive@lists.ietf.org>; Tue, 28 Aug 2001 13:36:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15bmd8-000Baj-00
	for idn-data@psg.com; Tue, 28 Aug 2001 10:26:26 -0700
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15bmd7-000Bad-00
	for idn@ops.ietf.org; Tue, 28 Aug 2001 10:26:25 -0700
Received: from [209.187.148.217] (helo=P2)
	by bs.jck.com with esmtp (Exim 3.32 #1)
	id 15bmct-000A50-00; Tue, 28 Aug 2001 17:26:11 +0000
Date: Tue, 28 Aug 2001 13:26:11 -0400
From: John C Klensin <klensin@jck.com>
To: Dave Crocker <dhc@dcrocker.net>
cc: Martin Duerst <duerst@w3.org>, idn-nameprep@viagenie.qc.ca,
        idn@ops.ietf.org
Subject: Re: [idn] Re: [idn-nameprep] nameprep and others:
 hangeulchar
Message-ID: <84991615.999005171@P2>
In-Reply-To: <5.1.0.14.2.20010828101145.03129830@dcrocker.net>
References:  <5.1.0.14.2.20010828101145.03129830@dcrocker.net>
X-Mailer: Mulberry/2.1.0b3 (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, 28 August, 2001 10:14 -0700 Dave Crocker
<dhc@dcrocker.net> wrote:

> At 05:40 AM 8/28/2001, John C Klensin wrote:
>> nothing is going to prevent labels of ECHAK, or any of its
>> permutations.
>> ...
>> I also just realized (most of you are probably ahead of me),
>> that I have no idea how LLLAL (or HHHAH) would be rendered if
> 
> 
> Why is it the job of an iDNS standard to prevent users from
> defining silly  strings, as long as the strings do not break
> the DNS?

Not the point.   The point is that we need to be _very_ careful
about imposing nameprep or canonicalization rules based on how
particular characters are used or sequenced, at particular
times, in particular languages because they are likely to have
unexpected effects when those characters are used in what you
call "silly strings".   And it implies that we should probably
not try to prohibit particular character sequences because the
"never occur" in normal use of the relevant script to express
the language with which it is typically used.
 
   john






From owner-idn@ops.ietf.org  Tue Aug 28 13:38: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 NAA16753
	for <idn-archive@lists.ietf.org>; Tue, 28 Aug 2001 13:38:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15bmfU-000BfZ-00
	for idn-data@psg.com; Tue, 28 Aug 2001 10:28:52 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15bmfT-000BfR-00
	for idn@ops.ietf.org; Tue, 28 Aug 2001 10:28:51 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+EESdhpctSHDFB4zmyX0exNtYuFwLlSPw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GDXSGL6M; Tue, 28 Aug 2001 13:28:03 EDT
To: harald@alvestrand.no
Cc: liana.ydisg@juno.com, phoffman@imc.org, idn@ops.ietf.org, James@Seng.cc
Date: Tue, 28 Aug 2001 10:45:44 -0700
Subject: Re: [idn] amending [IDNA]?
Message-ID: <20010828.104552.-1034989.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-16,18-25,27-57
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,  Harald:

I am thinking a black box procedure, which can
be at a client site, or at local server site depending
on current network configuration.  If it is at client site,
then any existing transport scheme can be used.  If
it is at a server site, then it works like a gateway to
its current local clients using local character code 
standard, such as in Japan and China. 

idn-label(input, tag-file, input-std, zonefile, idn-name)
input: any input stream as a label in input-std
tag-file: script tags where its code blocks of Unicode table are defined,
	this should be registered and tested before distribution.
 example: lat-  block1	block2	block3
	This allows [nameprep] be divided by tags, and allows 
	mixed scripts within a tagged range. 
zonefile: applied to server site; for a client site, it may be default a
cookie?

All these local parameters shall be a part of config package. For
a user, one has to select a tag and a display code standard. 

Liana


On Tue, 28 Aug 2001 15:14:52 +0200 Harald Tveit Alvestrand
<harald@alvestrand.no> writes:
> 
> 
> --On 17. august 2001 18:03 -0700 liana.ydisg@juno.com wrote:
> 
> > The IDN-label protocol is:
> >
> > idn-label(input, tag-file, input-std, zonefile, idn-name)
> > {
> >   tag = find-tag(input, tag-file, input-std);
> >   switch (tag)
> > 	{
> 
> I take it "idn-label" is a procedure to convert an input string into 
> an IDN 
> label for use in the DNS.
> 
> could you please explain a little more where the tag-file, input-std 
> and 
> zonefile arguments to the IDN-label protocol come from?
> 
> are these local parameters at the client, or does this occur at a 
> different 
> place in the system?
> 
> I do not understand.
> 
>              Harald
> 
> 
> 



From owner-idn@ops.ietf.org  Tue Aug 28 16:36: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 QAA20808
	for <idn-archive@lists.ietf.org>; Tue, 28 Aug 2001 16:36:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15bpP4-000FXC-00
	for idn-data@psg.com; Tue, 28 Aug 2001 13:24:06 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15bpP3-000FX4-00
	for idn@ops.ietf.org; Tue, 28 Aug 2001 13:24:05 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+EESdhpctSHj5yKqDhYrq+EzYpUXWUl6g==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GDX4GWCE; Tue, 28 Aug 2001 16:22:58 EDT
To: James@Seng.cc
Cc: liana.ydisg@juno.com, tsenglm@cc.ncu.edu.tw, huangk@alum.sinica.edu,
        idn@ops.ietf.org, dhc@dcrocker.net
Date: Tue, 28 Aug 2001 13:40:36 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010828.134044.-1034989.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-11,13-29
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 and Chinese experts:
  You are right on the TC/SC equivalence not in Unicode.  
I know they wanted to put it in long time ago, so I assumed
it is reflected in there some how.   I have just read a reason
that it is not in there, because they think it is too difficult to 
put it in.   I happend to have an idea that 1100 half size  
code point may solve part of the problem and another 200
TC/SC listing completes it.  This can be used in [nameprep].
What do you think?
.
Liana 

On Mon, 20 Aug 2001 13:53:38 +0800 "James Seng/Personal" <James@Seng.cc>
writes:
> > The SC character set has been used for decades and has went
> > through extensive nationwide testing in China.  SC is stable and 
> they
> are
> > properly reflected in Unicode standard.   The question is a
> definition:
> > is TC/SC a case folding?  It seems that in this WG, there has no
> > consensus on this definition yet.
> 
> I am not sure what you mean by "properly reflected" in Unicode 
> Standard.
> If you mean it is in ISO10646 codepoints, then yes, both TC/SC are 
> in
> the code points. But if you saying Unicode Consortium have proper
> definition of TC/SC, then I afraid to say there is none.
> 



From owner-idn@ops.ietf.org  Tue Aug 28 16:36: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 QAA20819
	for <idn-archive@lists.ietf.org>; Tue, 28 Aug 2001 16:36:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15bpOt-000FWz-00
	for idn-data@psg.com; Tue, 28 Aug 2001 13:23:55 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15bpOt-000FWt-00
	for idn@ops.ietf.org; Tue, 28 Aug 2001 13:23:55 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+EESdhpctSHj5yKqDhYrq94QYphDplENw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GDX4GV87; Tue, 28 Aug 2001 16:22:58 EDT
To: dhc@dcrocker.net
Cc: klensin@jck.com, duerst@w3.org, idn-nameprep@viagenie.qc.ca,
        idn@ops.ietf.org
Date: Tue, 28 Aug 2001 12:48:07 -0700
Subject: Re: [idn] Re: [idn-nameprep] nameprep and others: hangeulchar
Message-ID: <20010828.134044.-1034989.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-1,3-35
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 Tue, 28 Aug 2001 10:14:22 -0700 Dave Crocker <dhc@dcrocker.net>
writes:
> At 05:40 AM 8/28/2001, John C Klensin wrote:
> >nothing is going to prevent labels of ECHAK, or any of its
> >permutations.
> >...
> >I also just realized (most of you are probably ahead of me),
> >that I have no idea how LLLAL (or HHHAH) would be rendered if
> 
> 
> Why is it the job of an iDNS standard to prevent users from defining 
> silly 
> strings, as long as the strings do not break the DNS?
> 
> 
> At 09:35 AM 8/28/2001, Mark Davis wrote:
> >I believe, as I have said before, that it is too difficult to 
> separate out
> >the legitimate mixes of scripts and symbols from the 'questionable' 
> ones for
> >us to do anything. And adding language tags would simply make it 
> more
> >complicated, not less.
> 
> exactly correct.
> 
> Too difficult and, to paraphrase Jeff Case, simply not our problem.
> 
> d/
> 

Do you mean nobody else can come up with a feasible 
solution within the list? Or you do not care about any solution?

Liana



From owner-idn@ops.ietf.org  Tue Aug 28 16:53: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 QAA21241
	for <idn-archive@lists.ietf.org>; Tue, 28 Aug 2001 16:53:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15bpjV-000G6w-00
	for idn-data@psg.com; Tue, 28 Aug 2001 13:45:13 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15bpjU-000G6q-00
	for idn@ops.ietf.org; Tue, 28 Aug 2001 13:45:12 -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 NAA01252;
	Tue, 28 Aug 2001 13:44:58 -0700
Message-Id: <5.1.0.14.2.20010828134402.03bca628@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 28 Aug 2001 13:45:51 -0700
To: John C Klensin <klensin@jck.com>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] Re: [idn-nameprep] nameprep and others: hangeulchar
Cc: Martin Duerst <duerst@w3.org>, idn-nameprep@viagenie.qc.ca,
        idn@ops.ietf.org
In-Reply-To: <84991615.999005171@P2>
References: <5.1.0.14.2.20010828101145.03129830@dcrocker.net>
 <5.1.0.14.2.20010828101145.03129830@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 10:26 AM 8/28/2001, John C Klensin wrote:
>Not the point.   The point is that we need to be _very_ careful
>about imposing nameprep or canonicalization rules based on how
>particular characters are used or sequenced, at particular
>times, in particular languages because they are likely to have
>unexpected effects when those characters are used in what you
>call "silly strings".

ahh.  indeed.  definitely.

that is why nameprep should be limited to the simplest set of rules, rather 
than trying to be sophisticated.


>And it implies that we should probably
>not try to prohibit particular character sequences because the
>"never occur" in normal use of the relevant script to express
>the language with which it is typically used.

I agree entirely!

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 Aug 28 19:51: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 TAA24069
	for <idn-archive@lists.ietf.org>; Tue, 28 Aug 2001 19:51:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15bsPb-000Jnj-00
	for idn-data@psg.com; Tue, 28 Aug 2001 16:36:51 -0700
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15bsPZ-000Jnd-00
	for idn@ops.ietf.org; Tue, 28 Aug 2001 16:36:50 -0700
Received: from [135.207.27.137] (helo=KLENSIN01)
	by bs.jck.com with esmtp (Exim 3.32 #1)
	id 15bsPX-000AJd-00; Tue, 28 Aug 2001 23:36:47 +0000
Date: Tue, 28 Aug 2001 19:36:08 -0400
From: John C Klensin <klensin@jck.com>
To: liana.ydisg@juno.com
cc: idn@ops.ietf.org
Subject: [idn] Re: Characters, scripts and words (was: Re: nameprep and
 others: hangeulchar)
Message-ID: <77199751.999027368@KLENSIN01>
X-Mailer: Mulberry/2.1.0b3 (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, August 28, 2001 12:48 PM -0700
liana.ydisg@juno.com wrote:

>> > nothing is going to prevent labels of ECHAK, or any of its
>> > permutations.
>> > ...
>> Why is it the job of an iDNS standard to prevent users from
>> defining  silly 
>> strings, as long as the strings do not break the DNS?
>>...
>> At 09:35 AM 8/28/2001, Mark Davis wrote:
>> > I believe, as I have said before, that it is too difficult
>> > to 
>> separate out
>> > the legitimate mixes of scripts and symbols from the
>> > 'questionable' 
>> ones for
>> > us to do anything. And adding language tags would simply
>> > make it 
>> more
>> > complicated, not less.
>> 
>> exactly correct.
>> 
>> Too difficult and, to paraphrase Jeff Case, simply not our
>> problem.
>...
> Do you mean nobody else can come up with a feasible 
> solution within the list? 
 
Liana,

Let me risk answering for Dave as well as for myself.  

The working group (and sometimes its various design teams) keeps
falling into the trap of believing that one can make
language-specific rules for what characters can be handled in
the DNS and how they can (or should) be handled.  By and large,
the DNS will work well as long as we can examine, and match, one
character at a time, rather than trying to do things by words.  

One of the advantages of Unicode is that it is one character
set, and not a collection of independent different ones with
per-script or per-language tagging (identification) information.
Despite the considerable deployment of character encoding
systems that use coding system identification methods (several
of the ISO 2022-based techniques for representing Japanese come
to mind), we have found that such systems have very poor
interchange properties among disparate systems.  But Unicode's
weakness is also that it is one character set: the designers
have made many decisions to not include some characters in areas
belonging to a particular script because those characters appear
elsewhere.  Conversely, they have permitted duplication in other
areas.  As far as I can tell, all of those decisions were
rational, in the sense that there were good reasons for them.
Whether they were right or wrong at the time is a separate
question, but one that is largely irrelevant to our needs: there
is simply no alternative to Unicode on the table that could
serve as the basis for a multilingual (actually multi-script)
interchange format.

So we need to keep reminding ourselves that we are dealing with
character sequences, with the characters taken one at  a time.
Whether the results have any linguistic meaning, whether a label
can be pronounced, whether the string makes any cognitive sense
at all, are all irrelevant.   And, if we try to ignore that
irrelevancy, we get ourselves, not into "silly strings" but to
extremely silly states in which we would need to worry about,
e.g., the "meaning" of an Arabic non-joining zero-width
separator in the middle of a string of Chinese characters or a
Korean filler in the middle of a strong of Roman-based ones.  It
also implies that a single label might contain a mix of Chinese,
Korean, and Japanese "words", using characters (code points)
that are not differentiated among the three languages.  Trying
to translate or transcode such a string on the assumption that
it is homogeneous in one of the languages could easily be the
beginning of big trouble.

We've had a lot of names for this problem over the last year or
so.  Sometimes we call it the "identifier versus word" problem,
sometimes a "script versus language" one, sometimes other
things.  Each of these problems is a bit different, but all have
the fundamental problem outlined above at their core.  

> Or you do not care about any solution?

I can't speak for others, but I care, and care deeply.  The
difficulty is that, for all of these problems that are really
language-specific (or even specific to the use of particular
scripts in particular languages, it seems to me that there are
four types of things we can do.

    (i) We can decide the problems are not worth trying to
    solve.  I can't accept that, I don't think you can either,
    but I can imagine that some sensible people would take that
    position.
    
    (ii) We can try to trick the DNS into doing these things.
    We've seen many solutions of this type suggested to the WG
    at one time or another, and I am sure there are many others
    out there.  Different approaches involve clever heuristics,
    naming restrictions that bind the use of particular
    languages to particular TLDs, tricks for sneaking in
    language tags, and so on.  My belief is that none of them
    will work very well because the DNS still requires exact
    matching and natural languages are an inherently fuzzy
    business.
    
    (iii) We can try to localize the problem somehow --
    preprocessors that are installed in particular environments,
    keyword systems hooked into browsers, search mechanisms that
    are semi-invisible to the users and that use non-DNS
    databases.
    
    (iv) Or we can try to layer something above the DNS that
    deals with the "language" problems while the DNS deals with
    the "character" ones.  Many systems like this are possible,
    and we call them by many names: keywords (although some of
    the systems in the third group are also keyword ones),
    word-mapping and transation, searching, and so on  The
    difference between these approaches and the third is that it
    appears that we can make them work globally.  For example,
    if you travel to a far away place, and ask the same question
    as you would at home -- admittedly a more complex question
    than you would ask the DNS -- you will get the same answer.
    And, given appropriate input and rendering software and
    hardware, these systems should be able to access the same
    naming structures from all over the world and regardless of
    where those names appear in the DNS.   The systems in the
    third group typically don't have these properties.

Now, both the way I've presented the above and the things I've
been saying for the last many months probably make it clear what
I believe about this.  I don't think anyone who takes the
problem seriously is giving up; we are just trying to recast and
relocate it technically into a layer and environment in which we
have better tools and more information than the DNS offers.

    john
 



From owner-idn@ops.ietf.org  Tue Aug 28 20:19: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 UAA24400
	for <idn-archive@lists.ietf.org>; Tue, 28 Aug 2001 20:19:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15bsxI-000Ki4-00
	for idn-data@psg.com; Tue, 28 Aug 2001 17:11:40 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15bsxH-000Khy-00
	for idn@ops.ietf.org; Tue, 28 Aug 2001 17:11:39 -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 RAA07668;
	Tue, 28 Aug 2001 17:11:34 -0700
Message-Id: <5.1.0.14.2.20010828170714.0262a978@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 28 Aug 2001 17:09:50 -0700
To: liana.ydisg@juno.com
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] Re: [idn-nameprep] nameprep and others: hangeulchar
Cc: klensin@jck.com, duerst@w3.org, idn-nameprep@viagenie.qc.ca,
        idn@ops.ietf.org
In-Reply-To: <20010828.134044.-1034989.1.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 12:48 PM 8/28/2001, liana.ydisg@juno.com wrote:
>On Tue, 28 Aug 2001 10:14:22 -0700 Dave Crocker <dhc@dcrocker.net>
>writes:
> > At 05:40 AM 8/28/2001, John C Klensin wrote:
> > At 09:35 AM 8/28/2001, Mark Davis wrote:
> > >I believe, as I have said before, that it is too difficult to
> > separate out
> > >the legitimate mixes of scripts and symbols from the 'questionable'
> > ones for
> > >us to do anything. And adding language tags would simply make it
> > more
> > >complicated, not less.
> >
> > exactly correct.
> >
> > Too difficult and, to paraphrase Jeff Case, simply not our problem.
>
>Do you mean nobody else can come up with a feasible
>solution within the list? Or you do not care about any solution?

1.  Though I am certainly not skilled about the details, my observation of 
the discussions for at least the last year make it clear that no one is 
going to come up with a feasible solution that achieves consensus in this 
group.

2.  It has become quite clear to me that this task is entirely outside the 
scope of this group.  The task is a good and useful task.  However it is 
neither good nor useful NOR NECESSARY for this group to pursue it.

Ignoring #2 is one of the reasons this group is taking 3-4 times longer 
than it should.

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 Aug 28 20: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 UAA24415
	for <idn-archive@lists.ietf.org>; Tue, 28 Aug 2001 20:20:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15bszb-000Klq-00
	for idn-data@psg.com; Tue, 28 Aug 2001 17:14: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 15bszZ-000Klj-00
	for idn@ops.ietf.org; Tue, 28 Aug 2001 17:14: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 JAA01072
	for <idn@ops.ietf.org>; Wed, 29 Aug 2001 09:13:50 +0900
Message-ID: <07fe01c1301f$c38865a0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Subject: [idn] spoofing by combining diacritical marks
Date: Wed, 29 Aug 2001 09:15:52 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi,
To exemplify what JCK pointed out,
I took two experiments with two labels with <acute>.
Look into the enclosed excerpts.

The second  one  has   <acute><acute>,but look the same with single-<acute> one.

Does this problem come from the rendering engine (of win2k)
or from the definition of <acute> itself ?

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

www.k%u0301ol.com

www.kÌ�ol.com



www.k%u0301%u0301ol.com


www.kÌ�Ì�ol.com



<html>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<body>
<Script>
str=("www.k%u0301ol.com");
document.write("<br><font size=+1 face='Times New Roman'>");
document.writeln(str);
document.write("<br><p><font size=+3 face='Times New Roman'>");
document.writeln(unescape(str)); document.write("</font><br><p>");
</script>
<Script>
str=("www.k%u0301%u0301ol.com");
document.write("<br><font size=+1 face='Times New Roman'>");
document.writeln(str);
document.write("<br><p><font size=+3 face='Times New Roman'>");
document.writeln(unescape(str)); document.write("</font><br><p>");
</script>

http://www.postel.co.kr/etc/f2.html




From owner-idn@ops.ietf.org  Wed Aug 29 02:35: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 CAA17223
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 02:35:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15bydB-0003Di-00
	for idn-data@psg.com; Tue, 28 Aug 2001 23:15:17 -0700
Received: from mail.asahi-net.or.jp ([202.224.39.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15bydB-0003Dc-00
	for idn@ops.ietf.org; Tue, 28 Aug 2001 23:15:17 -0700
Received: from enoshima (e145190.ppp.asahi-net.or.jp [211.13.145.190])
	by mail.asahi-net.or.jp (Postfix) with ESMTP
	id C5F8C31BEA; Wed, 29 Aug 2001 15:15:15 +0900 (JST)
Message-Id: <4.2.0.58.J.20010829123705.05d629f0@mail.asahi-net.or.jp>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 29 Aug 2001 12:40:02 +0900
To: John C Klensin <klensin@jck.com>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Re: [idn-nameprep] nameprep and others: hangeulchar
Cc: idn-nameprep@viagenie.qc.ca, idn@ops.ietf.org
In-Reply-To: <67868501.998988050@localhost>
References: <4.2.0.58.J.20010828123600.036705b0@133.27.195.38>
 <4.2.0.58.J.20010828123600.036705b0@133.27.195.38>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 08:40 01/08/28 -0400, John C Klensin wrote:
>I also just realized (most of you are probably ahead of me),
>that I have no idea how LLLAL (or HHHAH) would be rendered if
>the character chosen for "A" has different glyphs depending on
>its joining position.

That problem has been solved, the A does not join except with
other As, so the isolated form is used. A more difficult
problem is the visual order of the letters in the case of
mixed directionality. That's a problem that we have to
identify a solution to. Please see
http://www.ietf.org/internet-drafts/draft-duerst-iri-bidi-00.txt
for a (yet far from complete) proposal. Comments appreciated.

Regards,   Martin.





From owner-idn@ops.ietf.org  Wed Aug 29 04:41: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 EAA18426
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 04:41:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15c0cT-0006hG-00
	for idn-data@psg.com; Wed, 29 Aug 2001 01:22:41 -0700
Received: from [217.13.28.204] (helo=eikenes.alvestrand.no)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15c0cS-0006gG-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 01:22:40 -0700
Received: from [192.168.1.31] (eikenes.alvestrand.no [217.13.28.203])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 62A0A61C4C; Wed, 29 Aug 2001 10:20:55 +0200 (CEST)
Date: Wed, 29 Aug 2001 10:20:08 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: liana.ydisg@juno.com, James@Seng.cc
Cc: tsenglm@cc.ncu.edu.tw, huangk@alum.sinica.edu, idn@ops.ietf.org,
        dhc@dcrocker.net
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <386302353.999080407@[192.168.1.31]>
In-Reply-To: <20010828.134044.-1034989.2.liana.ydisg@juno.com>
References:  <20010828.134044.-1034989.2.liana.ydisg@juno.com>
X-Mailer: Mulberry/2.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On 28. august 2001 13:40 -0700 liana.ydisg@juno.com wrote:

> Hi, James and Chinese experts:
>   You are right on the TC/SC equivalence not in Unicode.
> I know they wanted to put it in long time ago, so I assumed
> it is reflected in there some how.   I have just read a reason
> that it is not in there, because they think it is too difficult to
> put it in.   I happend to have an idea that 1100 half size
> code point may solve part of the problem and another 200
> TC/SC listing completes it.  This can be used in [nameprep].
> What do you think?

I would be happy to see a complete proposal.

draft-ietf-idn-tsconv-00 describes a TC/SC mapping for 2064 traditional/
simplified pairs, saying that other tables are needed for single/many
and many/single mappings.

This means that we have a documented proposal on what to do with 4128 
characters.
In Unicoode 3.0, there are 23.658 *more* characters classified as "Han"; 
Unicode 3.1 adds 42.711 more, and it has been noted here that because of 
the way Chinese linguistics work, it is almost 100% certain that there will 
be more added.
I assume (foolishly) that for some large class of these characters, the 
answer is "don't touch them" when mapping TC/SC - but I have no way of 
telling which characters belong in that class.

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.

Until then, I have to say that I have not seen any complete proposal.
Remember - the implementations of the algorithm for the non-Chinese part of 
the world will mainly be done by non-Chinese-speaking programmers; it's got 
to be simple & complete enough that even I can get it right...

             Harald





> .
> Liana
>
> On Mon, 20 Aug 2001 13:53:38 +0800 "James Seng/Personal" <James@Seng.cc>
> writes:
>> > The SC character set has been used for decades and has went
>> > through extensive nationwide testing in China.  SC is stable and
>> they
>> are
>> > properly reflected in Unicode standard.   The question is a
>> definition:
>> > is TC/SC a case folding?  It seems that in this WG, there has no
>> > consensus on this definition yet.
>>
>> I am not sure what you mean by "properly reflected" in Unicode
>> Standard.
>> If you mean it is in ISO10646 codepoints, then yes, both TC/SC are
>> in
>> the code points. But if you saying Unicode Consortium have proper
>> definition of TC/SC, then I afraid to say there is none.
>>
>
>





From owner-idn@ops.ietf.org  Wed Aug 29 06:51: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 GAA19521
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 06:51:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15c2bx-0009uT-00
	for idn-data@psg.com; Wed, 29 Aug 2001 03:30:17 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15c2bw-0009uN-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 03:30:16 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+EESdhpctSHiWLcNMsJ8VpUXjq9XnsSRA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GDZLWG7C; Wed, 29 Aug 2001 06:29:15 EDT
To: harald@alvestrand.no
Cc: liana.ydisg@juno.com, James@Seng.cc, tsenglm@cc.ncu.edu.tw,
        huangk@alum.sinica.edu, idn@ops.ietf.org, dhc@dcrocker.net
Date: Wed, 29 Aug 2001 03:24:48 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010829.034712.-984571.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-54,56-141
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, Harald

You are quite right regarding how the Chinese linguistics
works, there are never complete!  Right now, there are
formally classified characters already exceed 100,000.
I am not advocate include the whole set in [nameprep]
at all.  Neither do I advocate to exclude any characters, since
it is what the user wants.  But I do recommend to include
the characters included in Big5 and GB standard, that is
about 23,658 code points in Unicode, while 2238 are TC/SC 
equivalence and 14 radical equivalence we have been
discussing.   

There are two questions, 1) how to we implement TC/SC
in Unicode standard, 2) how do we implement CJK in 
[nameprep].  

For 1), I said 1100 ( I don't have the table at this time) 
half sized new Unicode points is to put radicals into the Unicode 
standard, just as other scripts did for diacritics.  This gives a
 base for decomposing a character for IDN identifiers 
(but not good enough for user input interface). 
 Within these radicals, 1886  TC/SC equivalence can be 
addressed.  The  352 TC/SC equivalence and 14 radical 
equivalence can be addressed in a supplement document, 
which shall state how to treat the other 1886  TC/SC 
equivalence based on their radicals.  The radical class has
been quite different from early history to recent era.  The class
of radical definition I am proposing is for a Han speaker and 
parting away from a computer programmer or a dictionary 
editor:

CJK Radical set has two sections: the first section is traditional
dictionary radical set, such as "Kangxi" and "Cihai" radical
set.  The second set is any characters which have been used
as radicals for other characters are radical set members.
The first  set is about 200, depending which dictionary we are
based on, the second set is about 1000.  Since the two sets 
overlap, my estimate is 1100 code points. 

2) I assume (since I did not check)  that  about 23,658 code 
points in Unicode 3.0 has included Hanja and Kanji.  
The other codepoints in Unicode and future new comers, 
can be treated on needed base.  This means, only when
someone has used in a name at registration time, and 
supplied the name with a codepoint in Unicode, then the
codepoint is added to zonefile.  (Not in [nameprep]?)
 If such a character is not in Unicode, then a bit map of the 
new character has to be provided in the zonefile.  This is 
the reason, I propose a "Request for Reference to be sent" 
protocol to be drafted.  

Liana


On Wed, 29 Aug 2001 10:20:08 +0200 Harald Tveit Alvestrand
<harald@alvestrand.no> writes:
> 
> 
> --On 28. august 2001 13:40 -0700 liana.ydisg@juno.com wrote:
> 
> > Hi, James and Chinese experts:
> >   You are right on the TC/SC equivalence not in Unicode.
> > I know they wanted to put it in long time ago, so I assumed
> > it is reflected in there some how.   I have just read a reason
> > that it is not in there, because they think it is too difficult to
> > put it in.   I happend to have an idea that 1100 half size
> > code point may solve part of the problem and another 200
> > TC/SC listing completes it.  This can be used in [nameprep].
> > What do you think?
> 
> I would be happy to see a complete proposal.
> 
> draft-ietf-idn-tsconv-00 describes a TC/SC mapping for 2064 
> traditional/
> simplified pairs, saying that other tables are needed for 
> single/many
> and many/single mappings.
> 
> This means that we have a documented proposal on what to do with 
> 4128 
> characters.
> In Unicoode 3.0, there are 23.658 *more* characters classified as 
> "Han"; 
> Unicode 3.1 adds 42.711 more, and it has been noted here that 
> because of 
> the way Chinese linguistics work, it is almost 100% certain that 
> there will 
> be more added.
> I assume (foolishly) that for some large class of these characters, 
> the 
> answer is "don't touch them" when mapping TC/SC - but I have no way 
> of 
> telling which characters belong in that class.
> 
> 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.
> 
> Until then, I have to say that I have not seen any complete 
> proposal.
> Remember - the implementations of the algorithm for the non-Chinese 
> part of 
> the world will mainly be done by non-Chinese-speaking programmers; 
> it's got 
> to be simple & complete enough that even I can get it right...
> 
>              Harald
> 
> 
> 
> 
> 
> > .
> > Liana
> >
> > On Mon, 20 Aug 2001 13:53:38 +0800 "James Seng/Personal" 
> <James@Seng.cc>
> > writes:
> >> > The SC character set has been used for decades and has went
> >> > through extensive nationwide testing in China.  SC is stable 
> and
> >> they
> >> are
> >> > properly reflected in Unicode standard.   The question is a
> >> definition:
> >> > is TC/SC a case folding?  It seems that in this WG, there has 
> no
> >> > consensus on this definition yet.
> >>
> >> I am not sure what you mean by "properly reflected" in Unicode
> >> Standard.
> >> If you mean it is in ISO10646 codepoints, then yes, both TC/SC 
> are
> >> in
> >> the code points. But if you saying Unicode Consortium have proper
> >> definition of TC/SC, then I afraid to say there is none.
> >>
> >
> >
> 
> 



From owner-idn@ops.ietf.org  Wed Aug 29 06: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 GAA19548
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 06:53:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15c2bC-0009sd-00
	for idn-data@psg.com; Wed, 29 Aug 2001 03:29:30 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15c2bB-0009sW-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 03:29:29 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+EESdhpctSHiWLcNMsJ8VrTicq2EnApYA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GDZLWG84; Wed, 29 Aug 2001 06:29:15 EDT
To: klensin@jck.com
Cc: liana.ydisg@juno.com, idn@ops.ietf.org
Date: Wed, 29 Aug 2001 03:46:57 -0700
Subject: Re: [idn] Re: Characters, scripts and words (was: Re: nameprep and others: hangeulchar)
Message-ID: <20010829.034712.-984571.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-32,34-175
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

Thanks for the overview  run on the wg history.  I'd
like to put the script tagging idea up for discussion.
In addition to a script tag definition, 
a tag has tagged range, tagged conversion, 
tagged reversion and tagged display modules 
associated to it.  Tagged input is belong to regisration
part of IDN, that I only hear font confusion discussion on 
it.  This following is an excerpt from my to-be draft.  I'd 
like to hear critics.

Liana


2.1 Tagged Range

Name tagging is the primary method in IDN to police illegitimate use
of [ISO 10646] codepoints. Trade names are created by people who 
may need to use several scripts in one trade name, for example 
Japanese users. However, there are unlikely that any legitimate users 
who have to use symbols outside their native scripts to mix in their 
native names. With tagged range, the IDN local developer MUST set up 
its supported script in term of code blocks of [ISO 10646], and 
exclude any codepoints outside its tagged range as well as any
non-IDN-character inside its tagged range to catch unintended 
codepoints. It is certain that some developers may provide more 
friendly user interface for certain user groups than others, while
tagged range defines limited scope for each tagged blocks to be policed.
A tagged range MUST have a least one non-zero code block as its primary 
range, and is RECOMMENDED to test for operational complexity before 
increasing its associating number of blocks. 



On Tue, 28 Aug 2001 19:36:08 -0400 John C Klensin <klensin@jck.com>
writes:
> --On Tuesday, August 28, 2001 12:48 PM -0700
> liana.ydisg@juno.com wrote:
> 
> >> > nothing is going to prevent labels of ECHAK, or any of its
> >> > permutations.
> >> > ...
> >> Why is it the job of an iDNS standard to prevent users from
> >> defining  silly 
> >> strings, as long as the strings do not break the DNS?
> >>...
> >> At 09:35 AM 8/28/2001, Mark Davis wrote:
> >> > I believe, as I have said before, that it is too difficult
> >> > to 
> >> separate out
> >> > the legitimate mixes of scripts and symbols from the
> >> > 'questionable' 
> >> ones for
> >> > us to do anything. And adding language tags would simply
> >> > make it 
> >> more
> >> > complicated, not less.
> >> 
> >> exactly correct.
> >> 
> >> Too difficult and, to paraphrase Jeff Case, simply not our
> >> problem.
> >...
> > Do you mean nobody else can come up with a feasible 
> > solution within the list? 
>  
> Liana,
> 
> Let me risk answering for Dave as well as for myself.  
> 
> The working group (and sometimes its various design teams) keeps
> falling into the trap of believing that one can make
> language-specific rules for what characters can be handled in
> the DNS and how they can (or should) be handled.  By and large,
> the DNS will work well as long as we can examine, and match, one
> character at a time, rather than trying to do things by words.  
> 
> One of the advantages of Unicode is that it is one character
> set, and not a collection of independent different ones with
> per-script or per-language tagging (identification) information.
> Despite the considerable deployment of character encoding
> systems that use coding system identification methods (several
> of the ISO 2022-based techniques for representing Japanese come
> to mind), we have found that such systems have very poor
> interchange properties among disparate systems.  But Unicode's
> weakness is also that it is one character set: the designers
> have made many decisions to not include some characters in areas
> belonging to a particular script because those characters appear
> elsewhere.  Conversely, they have permitted duplication in other
> areas.  As far as I can tell, all of those decisions were
> rational, in the sense that there were good reasons for them.
> Whether they were right or wrong at the time is a separate
> question, but one that is largely irrelevant to our needs: there
> is simply no alternative to Unicode on the table that could
> serve as the basis for a multilingual (actually multi-script)
> interchange format.
> 
> So we need to keep reminding ourselves that we are dealing with
> character sequences, with the characters taken one at  a time.
> Whether the results have any linguistic meaning, whether a label
> can be pronounced, whether the string makes any cognitive sense
> at all, are all irrelevant.   And, if we try to ignore that
> irrelevancy, we get ourselves, not into "silly strings" but to
> extremely silly states in which we would need to worry about,
> e.g., the "meaning" of an Arabic non-joining zero-width
> separator in the middle of a string of Chinese characters or a
> Korean filler in the middle of a strong of Roman-based ones.  It
> also implies that a single label might contain a mix of Chinese,
> Korean, and Japanese "words", using characters (code points)
> that are not differentiated among the three languages.  Trying
> to translate or transcode such a string on the assumption that
> it is homogeneous in one of the languages could easily be the
> beginning of big trouble.
> 
> We've had a lot of names for this problem over the last year or
> so.  Sometimes we call it the "identifier versus word" problem,
> sometimes a "script versus language" one, sometimes other
> things.  Each of these problems is a bit different, but all have
> the fundamental problem outlined above at their core.  
> 
> > Or you do not care about any solution?
> 
> I can't speak for others, but I care, and care deeply.  The
> difficulty is that, for all of these problems that are really
> language-specific (or even specific to the use of particular
> scripts in particular languages, it seems to me that there are
> four types of things we can do.
> 
>     (i) We can decide the problems are not worth trying to
>     solve.  I can't accept that, I don't think you can either,
>     but I can imagine that some sensible people would take that
>     position.
>     
>     (ii) We can try to trick the DNS into doing these things.
>     We've seen many solutions of this type suggested to the WG
>     at one time or another, and I am sure there are many others
>     out there.  Different approaches involve clever heuristics,
>     naming restrictions that bind the use of particular
>     languages to particular TLDs, tricks for sneaking in
>     language tags, and so on.  My belief is that none of them
>     will work very well because the DNS still requires exact
>     matching and natural languages are an inherently fuzzy
>     business.
>     
>     (iii) We can try to localize the problem somehow --
>     preprocessors that are installed in particular environments,
>     keyword systems hooked into browsers, search mechanisms that
>     are semi-invisible to the users and that use non-DNS
>     databases.
>     
>     (iv) Or we can try to layer something above the DNS that
>     deals with the "language" problems while the DNS deals with
>     the "character" ones.  Many systems like this are possible,
>     and we call them by many names: keywords (although some of
>     the systems in the third group are also keyword ones),
>     word-mapping and transation, searching, and so on  The
>     difference between these approaches and the third is that it
>     appears that we can make them work globally.  For example,
>     if you travel to a far away place, and ask the same question
>     as you would at home -- admittedly a more complex question
>     than you would ask the DNS -- you will get the same answer.
>     And, given appropriate input and rendering software and
>     hardware, these systems should be able to access the same
>     naming structures from all over the world and regardless of
>     where those names appear in the DNS.   The systems in the
>     third group typically don't have these properties.
> 
> Now, both the way I've presented the above and the things I've
> been saying for the last many months probably make it clear what
> I believe about this.  I don't think anyone who takes the
> problem seriously is giving up; we are just trying to recast and
> relocate it technically into a layer and environment in which we
> have better tools and more information than the DNS offers.
> 
>     john
>  
> 



From owner-idn@ops.ietf.org  Wed Aug 29 07:47: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 HAA21103
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 07:47:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15c3b1-000BbZ-00
	for idn-data@psg.com; Wed, 29 Aug 2001 04:33:23 -0700
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15c3b0-000BbT-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 04:33:22 -0700
Received: from [209.187.148.217] (helo=P2)
	by bs.jck.com with esmtp (Exim 3.32 #1)
	id 15c3Yy-000AuV-00; Wed, 29 Aug 2001 11:31:16 +0000
Date: Wed, 29 Aug 2001 07:31:15 -0400
From: John C Klensin <klensin@jck.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>, liana.ydisg@juno.com,
        James@Seng.cc
cc: tsenglm@cc.ncu.edu.tw, huangk@alum.sinica.edu, idn@ops.ietf.org,
        dhc@dcrocker.net
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <150106250.999070275@P2>
In-Reply-To: <386302353.999080407@[192.168.1.31]>
References:  <386302353.999080407@[192.168.1.31]>
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 Wednesday, 29 August, 2001 10:20 +0200 Harald Tveit
Alvestrand <harald@alvestrand.no> wrote:

> draft-ietf-idn-tsconv-00 describes a TC/SC mapping for 2064
> traditional/ simplified pairs, saying that other tables are
> needed for single/many and many/single mappings.
> 
> This means that we have a documented proposal on what to do
> with 4128 characters. In Unicoode 3.0, there are 23.658 *more*
> characters classified as "Han"; Unicode 3.1 adds 42.711 more,
> and it has been noted here that because of the way Chinese
> linguistics work, it is almost 100% certain that there will be
> more added. I assume (foolishly) that for some large class of
> these characters, the answer is "don't touch them" when
> mapping TC/SC - but I have no way of telling which characters
> belong in that class.
> 
> 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.
> 
> Until then, I have to say that I have not seen any complete
> proposal. Remember - the implementations of the algorithm for
> the non-Chinese part of the world will mainly be done by
> non-Chinese-speaking programmers; it's got to be simple &
> complete enough that even I can get it right...

And, unless whatever is done is isolated -- through procedures,
structure, or layering-- in a way that is robust, accessible to
all users of URLs based in the Chinese language, and that does
not fragment the Internet, we also need to be sure that the
tables and mechanisms that do SC/TC equivalence don't
accidentally map Kanji or Hangul into SC.

   john




From owner-idn@ops.ietf.org  Wed Aug 29 08:02: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 IAA21738
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 08:02:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15c3ih-000BrU-00
	for idn-data@psg.com; Wed, 29 Aug 2001 04:41:19 -0700
Received: from [217.13.28.204] (helo=eikenes.alvestrand.no)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15c3ig-000Boq-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 04:41:18 -0700
Received: from [192.168.1.31] (eikenes.alvestrand.no [217.13.28.203])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id F27C961C4C; Wed, 29 Aug 2001 13:39:30 +0200 (CEST)
Date: Wed, 29 Aug 2001 13:24:45 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: liana.ydisg@juno.com
Cc: tsenglm@cc.ncu.edu.tw, huangk@alum.sinica.edu, idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <397380292.999091485@localhost>
In-Reply-To: <20010829.034712.-984571.1.liana.ydisg@juno.com>
References:  <20010829.034712.-984571.1.liana.ydisg@juno.com>
X-Mailer: Mulberry/2.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On 29. august 2001 03:24 -0700 liana.ydisg@juno.com wrote:

>  Hi, Harald
>
> You are quite right regarding how the Chinese linguistics
> works, there are never complete!  Right now, there are
> formally classified characters already exceed 100,000.
> I am not advocate include the whole set in [nameprep]
> at all.  Neither do I advocate to exclude any characters, since
> it is what the user wants.  But I do recommend to include
> the characters included in Big5 and GB standard, that is
> about 23,658 code points in Unicode, while 2238 are TC/SC
> equivalence and 14 radical equivalence we have been
> discussing.
>
> There are two questions, 1) how to we implement TC/SC
> in Unicode standard, 2) how do we implement CJK in
> [nameprep].
>
> For 1), I said 1100 ( I don't have the table at this time)
> half sized new Unicode points is to put radicals into the Unicode
> standard, just as other scripts did for diacritics.  This gives a
>  base for decomposing a character for IDN identifiers
> (but not good enough for user input interface).
>  Within these radicals, 1886  TC/SC equivalence can be
> addressed.  The  352 TC/SC equivalence and 14 radical
> equivalence can be addressed in a supplement document,
> which shall state how to treat the other 1886  TC/SC
> equivalence based on their radicals.  The radical class has
> been quite different from early history to recent era.  The class
> of radical definition I am proposing is for a Han speaker and
> parting away from a computer programmer or a dictionary
> editor:
>
> CJK Radical set has two sections: the first section is traditional
> dictionary radical set, such as "Kangxi" and "Cihai" radical
> set.  The second set is any characters which have been used
> as radicals for other characters are radical set members.
> The first  set is about 200, depending which dictionary we are
> based on, the second set is about 1000.  Since the two sets
> overlap, my estimate is 1100 code points.

The Unicode 3.0 standard contains 2 blocks of radicals - the 214 
traditional KangXi radicals encoded in U+2F00 through U+2FD5, and the CJK 
Radicals Extension block U+2E80 through U+2EF3.

There is some language on using those characters to construct unencoded Han 
characters in section 10.1 of Unicode 3.0.

Is this the same kind of thing you are talking about?
If changes to Unicode are needed, this has to go to the Unicode Consortium 
and ISO; this group can't do much about it.....

>
> 2) I assume (since I did not check)  that  about 23,658 code
> points in Unicode 3.0 has included Hanja and Kanji.
> The other codepoints in Unicode and future new comers,
> can be treated on needed base.  This means, only when
> someone has used in a name at registration time, and
> supplied the name with a codepoint in Unicode, then the
> codepoint is added to zonefile.  (Not in [nameprep]?)
>  If such a character is not in Unicode, then a bit map of the
> new character has to be provided in the zonefile.  This is
> the reason, I propose a "Request for Reference to be sent"
> protocol to be drafted.

Better check....

So you foresee a system where

- User upgrades his data entry system
- User types a new ideograph into his systemm
- The client software calls out to some global repository for the
  new canonical dideograph decomposition of the new ideograph
- The DNS system looks up the decomposition, not the original codepoint
- The server knows enough to canonically decompose the zonefile's ideograph
- All this works correctly for software written by Indian programmers for
  American companies?

Seems complicated to me....




From owner-idn@ops.ietf.org  Wed Aug 29 09:54: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 JAA27097
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 09:54:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15c5eU-000FT6-00
	for idn-data@psg.com; Wed, 29 Aug 2001 06:45:06 -0700
Received: from mail.asahi-net.or.jp ([202.224.39.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15c5eT-000FSx-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 06:45:05 -0700
Received: from enoshima (e145190.ppp.asahi-net.or.jp [211.13.145.190])
	by mail.asahi-net.or.jp (Postfix) with ESMTP
	id 688A731D2B; Wed, 29 Aug 2001 22:45:03 +0900 (JST)
Message-Id: <4.2.0.58.J.20010829203938.02d3cb40@mail.asahi-net.or.jp>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Wed, 29 Aug 2001 20:45:05 +0900
To: John C Klensin <klensin@jck.com>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, liana.ydisg@juno.com,
        James@Seng.cc
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] opting out of SC/TC equivalence
Cc: tsenglm@cc.ncu.edu.tw, huangk@alum.sinica.edu, idn@ops.ietf.org,
        dhc@dcrocker.net
In-Reply-To: <150106250.999070275@P2>
References: <386302353.999080407@[192.168.1.31]>
 <386302353.999080407@[192.168.1.31]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 07:31 01/08/29 -0400, John C Klensin wrote:
>And, unless whatever is done is isolated -- through procedures,
>structure, or layering-- in a way that is robust, accessible to
>all users of URLs based in the Chinese language, and that does
>not fragment the Internet, we also need to be sure that the
>tables and mechanisms that do SC/TC equivalence don't
>accidentally map Kanji or Hangul into SC.

No problem for Hangul, which is a completely different script.
But for most Hanja (ideographs as used in Korea) and many Kanji
(only many because some are already the same as SC, and in
some cases, Japan has it's own simplifications), there is
absolutely no chance to be successful (i.e. only map SC/TC,
but not Hanja or Kanji). If that's the requirement (and I
agree it is), then we don't have to continue the discussion.
Sorry if I disappoint anybody :-(.

Regards,   Martin.



From owner-idn@ops.ietf.org  Wed Aug 29 10:24: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 KAA28789
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 10:24:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15c68s-000GUB-00
	for idn-data@psg.com; Wed, 29 Aug 2001 07:16:30 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15c68r-000GU5-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 07:16:29 -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 HAA31754;
	Wed, 29 Aug 2001 07:16:24 -0700
Message-Id: <5.1.0.14.2.20010829070533.01db5b88@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 29 Aug 2001 07:07:57 -0700
To: Harald Tveit Alvestrand <harald@alvestrand.no>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] opting out of SC/TC equivalence
Cc: idn@ops.ietf.org
In-Reply-To: <386302353.999080407@[192.168.1.31]>
References: <20010828.134044.-1034989.2.liana.ydisg@juno.com>
 <20010828.134044.-1034989.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 01:20 AM 8/29/2001, Harald Tveit Alvestrand wrote:
>--On 28. august 2001 13:40 -0700 liana.ydisg@juno.com wrote:
>>    I happend to have an idea that 1100 half size
>>code point may solve part of the problem and another 200
>>TC/SC listing completes it.  This can be used in [nameprep].
>>What do you think?
>
>I would be happy to see a complete proposal.


Excuse me, but I had the impression that solving this problem was rather 
clearly outside of the requirements for this working group.

At a minimum, it would be very helpful to get explicit resolution about the 
requirement to solve this, in this working group, as well as the 
requirement to solve it immediately, rather than consider it for a later 
version of the working group effort.

d/


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




From owner-idn@ops.ietf.org  Wed Aug 29 11:52: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 LAA01826
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 11:52:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15c7Hf-000InX-00
	for idn-data@psg.com; Wed, 29 Aug 2001 08:29:39 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15c7He-000InQ-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 08:29:38 -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 RAA00613;
	Wed, 29 Aug 2001 17:27:35 +0200 (MET DST)
Date: Wed, 29 Aug 2001 17:23:28 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>, liana.ydisg@juno.com
cc: tsenglm@cc.ncu.edu.tw, huangk@alum.sinica.edu, idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <5822641.999105808@localhost>
In-Reply-To: <397380292.999091485@localhost>
References:  <20010829.034712.-984571.1.liana.ydisg@juno.com>
 <397380292.999091485@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-08-29 13.24 +0200 Harald Tveit Alvestrand <harald@alvestrand.no>
wrote:

>> 2) I assume (since I did not check)  that  about 23,658 code
>> points in Unicode 3.0 has included Hanja and Kanji.
>> The other codepoints in Unicode and future new comers,
>> can be treated on needed base.  This means, only when
>> someone has used in a name at registration time, and
>> supplied the name with a codepoint in Unicode, then the
>> codepoint is added to zonefile.  (Not in [nameprep]?)
>>  If such a character is not in Unicode, then a bit map of the
>> new character has to be provided in the zonefile.  This is
>> the reason, I propose a "Request for Reference to be sent"
>> protocol to be drafted.
> 
> Better check....
> 
> So you foresee a system where
> 
> - User upgrades his data entry system
> - User types a new ideograph into his systemm
> - The client software calls out to some global repository for the
>   new canonical dideograph decomposition of the new ideograph
> - The DNS system looks up the decomposition, not the original codepoint
> - The server knows enough to canonically decompose the zonefile's
> ideograph - All this works correctly for software written by Indian
> programmers for   American companies?
> 
> Seems complicated to me....

I rather see people come with comments on current text about versioning in
the nameprep document than starting all over again with new ideas.
Versioning is complicated, but Mark and myself though quite a lot on the
text which describes how clients and servers are to handle "unassigned"
codepoints.

  paf




From owner-idn@ops.ietf.org  Wed Aug 29 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 LAA02039
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 11:59:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15c7SV-000JBH-00
	for idn-data@psg.com; Wed, 29 Aug 2001 08:40:51 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15c7SU-000JBA-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 08:40: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 IAA02383;
	Wed, 29 Aug 2001 08:40:48 -0700
Message-Id: <5.1.0.14.2.20010829083954.0291d208@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 29 Aug 2001 08:40:40 -0700
To: Patrik Fältström <paf@cisco.com>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] opting out of SC/TC equivalence
Cc: idn@ops.ietf.org
In-Reply-To: <5822641.999105808@localhost>
References: <397380292.999091485@localhost>
 <20010829.034712.-984571.1.liana.ydisg@juno.com>
 <397380292.999091485@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

At 08:23 AM 8/29/2001, Patrik Fältström wrote:
>I rather see people come with comments on current text about versioning in
>the nameprep document than starting all over again with new ideas.


"versioning"?  please explain the problem.

thanks.

d/


----------

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




From owner-idn@ops.ietf.org  Wed Aug 29 13:52: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 NAA04354
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 13:52:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15c9M2-000N5e-00
	for idn-data@psg.com; Wed, 29 Aug 2001 10:42:18 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15c9M1-000N5X-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 10:42:17 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+EESdhpctSH7i1BWWuAS/kMWNbwplX8uw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GD2DMD4Q; Wed, 29 Aug 2001 13:41:12 EDT
To: harald@alvestrand.no
Cc: liana.ydisg@juno.com, tsenglm@cc.ncu.edu.tw, huangk@alum.sinica.edu,
        idn@ops.ietf.org
Date: Wed, 29 Aug 2001 10:59:01 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010829.105905.-913489.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-1,3-101,103,105-131
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 Wed, 29 Aug 2001 13:24:45 +0200 Harald Tveit Alvestrand
<harald@alvestrand.no> writes:
> 
> 
> --On 29. august 2001 03:24 -0700 liana.ydisg@juno.com wrote:
> 
> >  Hi, Harald
> >
> > You are quite right regarding how the Chinese linguistics
> > works, there are never complete!  Right now, there are
> > formally classified characters already exceed 100,000.
> > I am not advocate include the whole set in [nameprep]
> > at all.  Neither do I advocate to exclude any characters, since
> > it is what the user wants.  But I do recommend to include
> > the characters included in Big5 and GB standard, that is
> > about 23,658 code points in Unicode, while 2238 are TC/SC
> > equivalence and 14 radical equivalence we have been
> > discussing.
> >
> > There are two questions, 1) how to we implement TC/SC
> > in Unicode standard, 2) how do we implement CJK in
> > [nameprep].
> >
> > For 1), I said 1100 ( I don't have the table at this time)
> > half sized new Unicode points is to put radicals into the Unicode
> > standard, just as other scripts did for diacritics.  This gives a
> >  base for decomposing a character for IDN identifiers
> > (but not good enough for user input interface).
> >  Within these radicals, 1886  TC/SC equivalence can be
> > addressed.  The  352 TC/SC equivalence and 14 radical
> > equivalence can be addressed in a supplement document,
> > which shall state how to treat the other 1886  TC/SC
> > equivalence based on their radicals.  The radical class has
> > been quite different from early history to recent era.  The class
> > of radical definition I am proposing is for a Han speaker and
> > parting away from a computer programmer or a dictionary
> > editor:
> >
> > CJK Radical set has two sections: the first section is traditional
> > dictionary radical set, such as "Kangxi" and "Cihai" radical
> > set.  The second set is any characters which have been used
> > as radicals for other characters are radical set members.
> > The first  set is about 200, depending which dictionary we are
> > based on, the second set is about 1000.  Since the two sets
> > overlap, my estimate is 1100 code points.
> 
> The Unicode 3.0 standard contains 2 blocks of radicals - the 214 
> traditional KangXi radicals encoded in U+2F00 through U+2FD5, and 
> the CJK 
> Radicals Extension block U+2E80 through U+2EF3.
> 
> There is some language on using those characters to construct 
> unencoded Han 
> characters in section 10.1 of Unicode 3.0.
> 
> Is this the same kind of thing you are talking about?
> If changes to Unicode are needed, this has to go to the Unicode 
> Consortium 
> and ISO; this group can't do much about it.....
> 
> >
> > 2) I assume (since I did not check)  that  about 23,658 code
> > points in Unicode 3.0 has included Hanja and Kanji.
> > The other codepoints in Unicode and future new comers,
> > can be treated on needed base.  This means, only when
> > someone has used in a name at registration time, and
> > supplied the name with a codepoint in Unicode, then the
> > codepoint is added to zonefile.  (Not in [nameprep]?)
> >  If such a character is not in Unicode, then a bit map of the
> > new character has to be provided in the zonefile.  This is
> > the reason, I propose a "Request for Reference to be sent"
> > protocol to be drafted.
> 
> Better check....
> 
> So you foresee a system where

> - User upgrades his data entry system
Don't need if  1) supplier give them an existing display code to
ACE code map which includes all the local TC/SC equivalence
rendering procedure affecting Han characters. 2) before a transport
protocol calls, application calls for [IDNA] ACE conversion and
get the tagged ACE version to ship.  So this is application call 
[IDNA] black box operation. 

> - User types a new ideograph into his systemm
This is a future possibility, and up to the application to deal with.
That IS out of this WG's scope.  [nameprep] may update say once
 a year, to collect the new ones which has to be proved stable 
already, working like UNICODE updates.

> - The client software calls out to some global repository for the
>   new canonical dideograph decomposition of the new ideograph
Yes, at registration time for adminstration of such a use only.  
In fact, only Chinese has this repository and I belief, a few experts 
really like to be able to use this repository.  Why do we need 
Unicode Consultium to make this type of decision?

> - The DNS system looks up the decomposition, not the original 
> codepoint
No.  IDN-label only gets this from the registering server, if it is asked

for from a client (that is if the client know itself has unicode as
display
code).  This is outside DNS. DNS only deal with identifiers.

> - The server knows enough to canonically decompose the zonefile's 
> ideograph
No.  There are two separeted issue here.  DNS don't know about
this.  The sever who wants to display zonefile's ideograph has
to know there is a request for  the full code to be shipped and to
put in its zonefile.  It does not need to know decomposing  procedure.
The decomposing can be handled by [IDNA] with tagged conversion.

 This is all a Chinese tagged conversion, reversion  and
display procedures does, so does tagged Kanji and Hanja 
procedures.  That is the reason I propose to increase radical 
section in Unicode to cover 1000 radicals.

> - All this works correctly for software written by Indian 
> programmers for
>   American companies?

That is the reason I propose to increase radical section in 
Unicode to cover 1000 radicals, and for WG to agree a versioning
table to include GB, Big5, KSC, JIS to transliterated ACE map.

> 
> Seems complicated to me....
> 



From owner-idn@ops.ietf.org  Wed Aug 29 17:19: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 RAA10585
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 17:19:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cCRs-0003zB-00
	for idn-data@psg.com; Wed, 29 Aug 2001 14:00:32 -0700
Received: from [217.13.28.204] (helo=eikenes.alvestrand.no)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cCRr-0003wl-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 14:00:31 -0700
Received: from [192.168.1.31] (eikenes.alvestrand.no [217.13.28.203])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id C2C3661C4C; Wed, 29 Aug 2001 22:58:48 +0200 (CEST)
Date: Wed, 29 Aug 2001 22:58:08 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: liana.ydisg@juno.com
Cc: tsenglm@cc.ncu.edu.tw, huangk@alum.sinica.edu, idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <431782900.999125888@[192.168.1.31]>
In-Reply-To: <20010829.105905.-913489.0.liana.ydisg@juno.com>
References:  <20010829.105905.-913489.0.liana.ydisg@juno.com>
X-Mailer: Mulberry/2.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On 29. august 2001 10:59 -0700 liana.ydisg@juno.com wrote:

>
> That is the reason I propose to increase radical section in
> Unicode to cover 1000 radicals, and for WG to agree a versioning
> table to include GB, Big5, KSC, JIS to transliterated ACE map.

OK, so this proposal cannot be acted on by the IETF until the proposal for 
additional radicals in Unicode has been accepted.

Then I think it is not a possible solution at the timescale when this group 
is planning to deliver a product.

Thank you for the clarification.

          Harald




From owner-idn@ops.ietf.org  Wed Aug 29 20:32: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 UAA13979
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 20:32:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cFX9-000BSy-00
	for idn-data@psg.com; Wed, 29 Aug 2001 17:18: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 15cFX8-000BSn-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 17:18:11 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id JAA00593;
	Thu, 30 Aug 2001 09:17:57 +0900
Message-ID: <093c01c130e9$80066320$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
References: <07fe01c1301f$c38865a0$ec1bd9d2@temp>
Subject: Re: [idn] spoofing by combining diacritical marks
Date: Thu, 30 Aug 2001 09:19:57 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

More self-comment:

  Current unicode standard have _no_  normalization rules on
    repeated <acute>s ( and other diacritical marks)  to prevent them from
    looking differently according to their positions in unicode strings.

  The second <Acute> in the <acute><Acute> does not display in some
  cases.

  This problem is somewhat out of IDN WG scope and should be reviewed
  by relevant  standard organizations.

  Zone masters should be aware of this and filter out  spoofing domains..

 Soobok Lee


----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
Sent: Wednesday, August 29, 2001 9:15 AM
Subject: [idn] spoofing by combining diacritical marks


> Hi,
> To exemplify what JCK pointed out,
> I took two experiments with two labels with <acute>.
> Look into the enclosed excerpts.
>
> The second  one  has   <acute><acute>,but look the same with single-<acute> one.
>
> Does this problem come from the rendering engine (of win2k)
> or from the definition of <acute> itself ?
>
> Soobok Lee
> ---------------------------------------------------------------------------------------------------------------
>
> www.k%u0301ol.com
>
> www.kÌ�ol.com
>
>
>
> www.k%u0301%u0301ol.com
>
>
> www.kÌ�Ì�ol.com
>
>
>
> <html>
> <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
> <body>
> <Script>
> str=("www.k%u0301ol.com");
> document.write("<br><font size=+1 face='Times New Roman'>");
> document.writeln(str);
> document.write("<br><p><font size=+3 face='Times New Roman'>");
> document.writeln(unescape(str)); document.write("</font><br><p>");
> </script>
> <Script>
> str=("www.k%u0301%u0301ol.com");
> document.write("<br><font size=+1 face='Times New Roman'>");
> document.writeln(str);
> document.write("<br><p><font size=+3 face='Times New Roman'>");
> document.writeln(unescape(str)); document.write("</font><br><p>");
> </script>
>
> http://www.postel.co.kr/etc/f2.html
>
>




From owner-idn@ops.ietf.org  Wed Aug 29 20: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 UAA14046
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 20:42:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cFnQ-000CAK-00
	for idn-data@psg.com; Wed, 29 Aug 2001 17:35: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 15cFnP-000CAD-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 17:34: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 JAA05872;
	Thu, 30 Aug 2001 09:34:51 +0900
Message-ID: <094601c130eb$dc100610$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
References: <07fe01c1301f$c38865a0$ec1bd9d2@temp> <093c01c130e9$80066320$ec1bd9d2@temp>
Subject: (more)Re: [idn] spoofing by combining diacritical marks
Date: Thu, 30 Aug 2001 09:36:50 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

I found   all unicode characters with some _COMBINING SEMANTICS_
share the same problem.

To list some of them:
  Hangul fillers, Various signs in Hindi(Devanagari) and other Indian scripts,
  Combining Diacrticial Marks

We need some "registration guidelines" informational RFC to inform
zone-masters of this problem.

Soobok Lee

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
Sent: Thursday, August 30, 2001 9:19 AM
Subject: Re: [idn] spoofing by combining diacritical marks


> More self-comment:
>
>   Current unicode standard have _no_  normalization rules on
>     repeated <acute>s ( and other diacritical marks)  to prevent them from
>     looking differently according to their positions in unicode strings.
>
>   The second <Acute> in the <acute><Acute> does not display in some
>   cases.
>
>   This problem is somewhat out of IDN WG scope and should be reviewed
>   by relevant  standard organizations.
>
>   Zone masters should be aware of this and filter out  spoofing domains..
>
>  Soobok Lee
>
>
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: <idn@ops.ietf.org>
> Sent: Wednesday, August 29, 2001 9:15 AM
> Subject: [idn] spoofing by combining diacritical marks
>
>
> > Hi,
> > To exemplify what JCK pointed out,
> > I took two experiments with two labels with <acute>.
> > Look into the enclosed excerpts.
> >
> > The second  one  has   <acute><acute>,but look the same with single-<acute> one.
> >
> > Does this problem come from the rendering engine (of win2k)
> > or from the definition of <acute> itself ?
> >
> > Soobok Lee
> > ---------------------------------------------------------------------------------------------------------------
> >
> > www.k%u0301ol.com
> >
> > www.kÌ�ol.com
> >
> >
> >
> > www.k%u0301%u0301ol.com
> >
> >
> > www.kÌ�Ì�ol.com
> >
> >
> >
> > <html>
> > <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
> > <body>
> > <Script>
> > str=("www.k%u0301ol.com");
> > document.write("<br><font size=+1 face='Times New Roman'>");
> > document.writeln(str);
> > document.write("<br><p><font size=+3 face='Times New Roman'>");
> > document.writeln(unescape(str)); document.write("</font><br><p>");
> > </script>
> > <Script>
> > str=("www.k%u0301%u0301ol.com");
> > document.write("<br><font size=+1 face='Times New Roman'>");
> > document.writeln(str);
> > document.write("<br><p><font size=+3 face='Times New Roman'>");
> > document.writeln(unescape(str)); document.write("</font><br><p>");
> > </script>
> >
> > http://www.postel.co.kr/etc/f2.html
> >
> >
>




From owner-idn@ops.ietf.org  Wed Aug 29 21:14: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 VAA14298
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 21:14:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cGHx-000DN0-00
	for idn-data@psg.com; Wed, 29 Aug 2001 18:06:33 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cGHw-000DMY-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 18:06:32 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+EESdhpctSHzKXvRA6z4L4kqzSyaFtL3Q==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GD26PFK2; Wed, 29 Aug 2001 20:59:13 EDT
To: harald@alvestrand.no
Cc: liana.ydisg@juno.com, tsenglm@cc.ncu.edu.tw, huangk@alum.sinica.edu,
        idn@ops.ietf.org
Date: Wed, 29 Aug 2001 18:17:09 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010829.181717.-904857.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-45,47-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

That is not the case.  If IETF does not want to put TC/SC
folding in [nameprep], then it has no good reason to
agree a versioning table to include GB, Big5, KSC, JIS to
 transliterated ACE map.  In that case, I am no motivation
to push for Unicode to accept the long list of radicals.  
I can sit back and see how long this will go, as I have been
assumed that by now the TC/SC should have been in there 
long time ago, which has been proved by James that I
was wrong. 

As this point, I think a little more Han radical classification
background infor is helpful.  The Han radical has about
a dozen dictionary editor's classifications, which is the radicals
included in UCS.  There are about a multitude of hundreds 
of programmers' viewpoints on this.  The one I am in favor of
 and have been implemented by quite a few good encoding 
software are all AI and phonetic based approach, which is used 
by common people when they communicate specific characters 
mostly used in names.   Similar in the way, English speakers
say "D as it's in Dog."  Studys in the late 80's have been shown 
there are about 1000 -1200 such radicals conventionally not 
considered as radicals.  Since RADICAL in Chinese often 
means the indexing group in a dictionary, and only takes
one radical per character.  So radical set in this sense is not 
the complete listing of radicals in Han.  So it is not complete list 
for SC radicals, neither the UCS has a complete list for the 
same reason.

If IETF has no architecture to accomodate these types 
of script requirement, and is not planning to use a complete 
list of radicals,  please give me a reason for me to push it for 
Unicode standard.   

Another option is that IETF still can go ahead giving the world a 
simple listing of 4128 TC/SC equivalent listing some where 
else, catching up with your product delivering schedule, waiving
 hands and say: take care of it, but out of my sight.  The end result
 is just like Unicode imposing a misconception of  TC/SC are
 two different languges.  I hope my explaination can shed a little
 light on CNNIC's feeling about TC/SC arguements.  You also
can tell me that my input is out of the scope of this group, and
I am ready to leave too. 

Liana


On Wed, 29 Aug 2001 22:58:08 +0200 Harald Tveit Alvestrand
<harald@alvestrand.no> writes:
> 
> 
> --On 29. august 2001 10:59 -0700 liana.ydisg@juno.com wrote:
> 
> >
> > That is the reason I propose to increase radical section in
> > Unicode to cover 1000 radicals, and for WG to agree a versioning
> > table to include GB, Big5, KSC, JIS to transliterated ACE map.
> 
> OK, so this proposal cannot be acted on by the IETF until the 
> proposal for 
> additional radicals in Unicode has been accepted.
> 
> Then I think it is not a possible solution at the timescale when 
> this group 
> is planning to deliver a product.
> 
> Thank you for the clarification.
> 
>           Harald
> 
> 



From owner-idn@ops.ietf.org  Wed Aug 29 21:57: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 VAA15664
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 21:57:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cGkP-000EdW-00
	for idn-data@psg.com; Wed, 29 Aug 2001 18:35:57 -0700
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cGkK-000EdP-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 18:35:56 -0700
Received: from xiaodonglee ([159.226.7.70]) by
          whale.cnnic.net.cn (Netscape Messaging Server 4.15) with SMTP id
          GIUXUI00.DU8; Thu, 30 Aug 2001 09:37:30 +0800 
Message-ID: <002801c130f3$83012100$4607e29f@xiaodonglee>
Reply-To: "Xiaodong LEE" <Xiaodong.Lee@cnnic.net.cn>
From: "xiaodong lee" <lee@whale.cnnic.net.cn>
To: "Martin Duerst" <duerst@w3.org>
Cc: <idn@ops.ietf.org>
References: <386302353.999080407@[192.168.1.31]> <386302353.999080407@[192.168.1.31]> <4.2.0.58.J.20010829203938.02d3cb40@mail.asahi-net.or.jp>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Thu, 30 Aug 2001 09:31:37 +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 VAA15664

Martin 
I agree. we must consider Hanja and Kanji.
so we must find a feasible solution to avoid that. though the solution maybe not perfect.
do you think it is impossible to find that?


----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "John C Klensin" <klensin@jck.com>; "Harald Tveit Alvestrand" <harald@alvestrand.no>; <liana.ydisg@juno.com>; <James@Seng.cc>
Cc: <tsenglm@cc.ncu.edu.tw>; <huangk@alum.sinica.edu>; <idn@ops.ietf.org>; <dhc@dcrocker.net>
Sent: Wednesday, August 29, 2001 7:45 PM
Subject: Re: [idn] opting out of SC/TC equivalence


> At 07:31 01/08/29 -0400, John C Klensin wrote:
> >And, unless whatever is done is isolated -- through procedures,
> >structure, or layering-- in a way that is robust, accessible to
> >all users of URLs based in the Chinese language, and that does
> >not fragment the Internet, we also need to be sure that the
> >tables and mechanisms that do SC/TC equivalence don't
> >accidentally map Kanji or Hangul into SC.
> 
> No problem for Hangul, which is a completely different script.
> But for most Hanja (ideographs as used in Korea) and many Kanji
> (only many because some are already the same as SC, and in
> some cases, Japan has it's own simplifications), there is
> absolutely no chance to be successful (i.e. only map SC/TC,
> but not Hanja or Kanji). If that's the requirement (and I
> agree it is), then we don't have to continue the discussion.
> Sorry if I disappoint anybody :-(.
> 
> Regards,   Martin.
> 


From owner-idn@ops.ietf.org  Wed Aug 29 22:16: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 WAA15907
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 22:16:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cHCT-000FkP-00
	for idn-data@psg.com; Wed, 29 Aug 2001 19:04:57 -0700
Received: from [159.226.6.187] (helo=whale.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cHCS-000FkH-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 19:04:56 -0700
Received: from xiaodonglee ([159.226.7.70]) by
          whale.cnnic.net.cn (Netscape Messaging Server 4.15) with SMTP id
          GIUZ6Z00.QVR; Thu, 30 Aug 2001 10:06:35 +0800 
Message-ID: <003d01c130f7$92facd50$4607e29f@xiaodonglee>
Reply-To: "Xiaodong LEE" <Xiaodong.Lee@cnnic.net.cn>
From: "xiaodong lee" <lee@whale.cnnic.net.cn>
To: <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>
References: <20010829.181717.-904857.1.liana.ydisg@juno.com>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Thu, 30 Aug 2001 10:00:41 +0800
Organization: CNIC-ICT
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
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 WAA15907

Hi Liana

----- Original Message ----- 
From: <liana.ydisg@juno.com>
To: <harald@alvestrand.no>
Cc: <liana.ydisg@juno.com>; <tsenglm@cc.ncu.edu.tw>; <huangk@alum.sinica.edu>; <idn@ops.ietf.org>
Sent: Thursday, August 30, 2001 9:17 AM
Subject: Re: [idn] opting out of SC/TC equivalence


> That is not the case.  If IETF does not want to put TC/SC
> folding in [nameprep], then it has no good reason to
> agree a versioning table to include GB, Big5, KSC, JIS to
>  transliterated ACE map.  In that case, I am no motivation
> to push for Unicode to accept the long list of radicals.  
> I can sit back and see how long this will go, as I have been
> assumed that by now the TC/SC should have been in there 
> long time ago, which has been proved by James that I
> was wrong. 
> 
> As this point, I think a little more Han radical classification
> background infor is helpful.  The Han radical has about
> a dozen dictionary editor's classifications, which is the radicals
> included in UCS.  There are about a multitude of hundreds 
> of programmers' viewpoints on this.  The one I am in favor of
>  and have been implemented by quite a few good encoding 
> software are all AI and phonetic based approach, which is used 
> by common people when they communicate specific characters 
> mostly used in names.   Similar in the way, English speakers
> say "D as it's in Dog."  Studys in the late 80's have been shown 
> there are about 1000 -1200 such radicals conventionally not 
> considered as radicals.  Since RADICAL in Chinese often 
> means the indexing group in a dictionary, and only takes
> one radical per character.  So radical set in this sense is not 
> the complete listing of radicals in Han.  So it is not complete list 
> for SC radicals, neither the UCS has a complete list for the 
> same reason.
> 
> If IETF has no architecture to accomodate these types 
> of script requirement, and is not planning to use a complete 
> list of radicals,  please give me a reason for me to push it for 
> Unicode standard.   

I remember that someone in IETF suggest to provide an architecture 
to accomodate these requirement. to handle codepoint is not the task 
and superority of IETF, but we in IETF should define the architecture 
and leave the interface for other consortium to deal with that. If 
all consortium just push it to others without enough efforts, there 
may be deadlock to implement it.

> 
> Another option is that IETF still can go ahead giving the world a 
> simple listing of 4128 TC/SC equivalent listing some where 
> else, catching up with your product delivering schedule, waiving
>  hands and say: take care of it, but out of my sight.  The end result
>  is just like Unicode imposing a misconception of  TC/SC are
>  two different languges.  I hope my explaination can shed a little
>  light on CNNIC's feeling about TC/SC arguements.  You also
> can tell me that my input is out of the scope of this group, and
> I am ready to leave too. 

I agree with you. :)

> 
> Liana
> 
> 
> On Wed, 29 Aug 2001 22:58:08 +0200 Harald Tveit Alvestrand
> <harald@alvestrand.no> writes:
> > 
> > 
> > --On 29. august 2001 10:59 -0700 liana.ydisg@juno.com wrote:
> > 
> > >
> > > That is the reason I propose to increase radical section in
> > > Unicode to cover 1000 radicals, and for WG to agree a versioning
> > > table to include GB, Big5, KSC, JIS to transliterated ACE map.
> > 
> > OK, so this proposal cannot be acted on by the IETF until the 
> > proposal for 
> > additional radicals in Unicode has been accepted.
> > 
> > Then I think it is not a possible solution at the timescale when 
> > this group 
> > is planning to deliver a product.
> > 
> > Thank you for the clarification.
> > 
> >           Harald
> > 
> > 
> 


From owner-idn@ops.ietf.org  Wed Aug 29 22:44: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 WAA17175
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 22:44:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cHfV-000GI3-00
	for idn-data@psg.com; Wed, 29 Aug 2001 19:34:57 -0700
Received: from femail28.sdc1.sfba.home.com ([24.254.60.18])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cHfU-000GHx-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 19:34:56 -0700
Received: from c1340594a ([65.11.104.12]) by femail28.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20010830023455.GNYP11524.femail28.sdc1.sfba.home.com@c1340594a>;
          Wed, 29 Aug 2001 19:34:55 -0700
Message-ID: <006c01c130fc$5d70f420$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
References: <07fe01c1301f$c38865a0$ec1bd9d2@temp> <093c01c130e9$80066320$ec1bd9d2@temp>
Subject: Re: [idn] spoofing by combining diacritical marks
Date: Wed, 29 Aug 2001 19:34:59 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

The standard *does* specify the appropriate display behavior for such
circumstances. See http://www.unicode.org/unicode/uni2book/ch02.pdf, Section
2.6.

However, some implementations may not yet implement that behavior.

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: Wednesday, August 29, 2001 17:19
Subject: Re: [idn] spoofing by combining diacritical marks


> More self-comment:
>
>   Current unicode standard have _no_  normalization rules on
>     repeated <acute>s ( and other diacritical marks)  to prevent them from
>     looking differently according to their positions in unicode strings.
>
>   The second <Acute> in the <acute><Acute> does not display in some
>   cases.
>
>   This problem is somewhat out of IDN WG scope and should be reviewed
>   by relevant  standard organizations.
>
>   Zone masters should be aware of this and filter out  spoofing domains..
>
>  Soobok Lee
>
>
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: <idn@ops.ietf.org>
> Sent: Wednesday, August 29, 2001 9:15 AM
> Subject: [idn] spoofing by combining diacritical marks
>
>
> > Hi,
> > To exemplify what JCK pointed out,
> > I took two experiments with two labels with <acute>.
> > Look into the enclosed excerpts.
> >
> > The second  one  has   <acute><acute>,but look the same with
single-<acute> one.
> >
> > Does this problem come from the rendering engine (of win2k)
> > or from the definition of <acute> itself ?
> >
> > Soobok Lee
>
> --------------------------------------------------------------------------
-------------------------------------
> >
> > www.k%u0301ol.com
> >
> > www.kÌ�ol.com
> >
> >
> >
> > www.k%u0301%u0301ol.com
> >
> >
> > www.kÌ�Ì�ol.com
> >
> >
> >
> > <html>
> > <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
> > <body>
> > <Script>
> > str=("www.k%u0301ol.com");
> > document.write("<br><font size=+1 face='Times New Roman'>");
> > document.writeln(str);
> > document.write("<br><p><font size=+3 face='Times New Roman'>");
> > document.writeln(unescape(str)); document.write("</font><br><p>");
> > </script>
> > <Script>
> > str=("www.k%u0301%u0301ol.com");
> > document.write("<br><font size=+1 face='Times New Roman'>");
> > document.writeln(str);
> > document.write("<br><p><font size=+3 face='Times New Roman'>");
> > document.writeln(unescape(str)); document.write("</font><br><p>");
> > </script>
> >
> > http://www.postel.co.kr/etc/f2.html
> >
> >
>
>
>




From owner-idn@ops.ietf.org  Wed Aug 29 23:22: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 XAA17441
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 23:22:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cIKZ-000Ha4-00
	for idn-data@psg.com; Wed, 29 Aug 2001 20:17:23 -0700
Received: from mail.asahi-net.or.jp ([202.224.39.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cIKY-000HZy-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 20:17:22 -0700
Received: from enoshima (e145160.ppp.asahi-net.or.jp [211.13.145.160])
	by mail.asahi-net.or.jp (Postfix) with ESMTP
	id 0C56831C32; Thu, 30 Aug 2001 12:17:21 +0900 (JST)
Message-Id: <4.2.0.58.J.20010830114028.061a03f0@mail.asahi-net.or.jp>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 30 Aug 2001 11:43:39 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, "Soobok Lee" <lsb@postel.co.kr>,
        <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] spoofing by combining diacritical marks
In-Reply-To: <093c01c130e9$80066320$ec1bd9d2@temp>
References: <07fe01c1301f$c38865a0$ec1bd9d2@temp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 09:19 01/08/30 +0900, Soobok Lee wrote:
>More self-comment:
>
>   Current unicode standard have _no_  normalization rules on
>     repeated <acute>s ( and other diacritical marks)  to prevent them from
>     looking differently according to their positions in unicode strings.

Sorry, I don't understand that. Two acute accents after a
character are supposed to be displayed as two acute accents.
There is no need for normalization, because there is only
one way to have a sequence of two acute accents.


>   The second <Acute> in the <acute><Acute> does not display in some
>   cases.

That's a rendering problem. The implementation you use should needs
to be fixed.

Regards,   Martin.

>   This problem is somewhat out of IDN WG scope and should be reviewed
>   by relevant  standard organizations.
>
>   Zone masters should be aware of this and filter out  spoofing domains..
>
>  Soobok Lee




From owner-idn@ops.ietf.org  Wed Aug 29 23:40: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 XAA17951
	for <idn-archive@lists.ietf.org>; Wed, 29 Aug 2001 23:40:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cIQ9-000HrN-00
	for idn-data@psg.com; Wed, 29 Aug 2001 20:23: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 15cIQ8-000HrF-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 20:23: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 MAA27132;
	Thu, 30 Aug 2001 12:22:56 +0900
Message-ID: <09bb01c13103$57915610$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Mark Davis" <mark@macchiato.com>, <idn@ops.ietf.org>
References: <07fe01c1301f$c38865a0$ec1bd9d2@temp> <093c01c130e9$80066320$ec1bd9d2@temp> <006c01c130fc$5d70f420$0c680b41@c1340594a>
Subject: Re: [idn] spoofing by combining diacritical marks
Date: Thu, 30 Aug 2001 12:24:56 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

You are right.

The standard is specifying that double <Acute>s should be displayed with
stacked <acute>s  above the base character. But Win2K/98 doesn't display
them correctly. If <acute> is repeated 10 times, that is beyond most commercial
rendering engine's capability and that can be utilized for spoofing
ONly feasible solution to this problem is  prohibiting them by zone-masters,i believe.


BTW, Unicode Standard Chap2. Section 2.6, Figure 2-10 has an example:

  <latin a><combining dot below><combining dot above>
  <latin a><combining dot above><combining dot below>

 These two sequences are defined to have the same look
 But, I can't find yet any _NORMALIZATION_ rules to unify them.

 Does unicode standards have any rules to unify them  ?

 Soobok



----- Original Message -----
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
Sent: Thursday, August 30, 2001 11:34 AM
Subject: Re: [idn] spoofing by combining diacritical marks


> The standard *does* specify the appropriate display behavior for such
> circumstances. See http://www.unicode.org/unicode/uni2book/ch02.pdf, Section
> 2.6.
>
> However, some implementations may not yet implement that behavior.
>
> 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: Wednesday, August 29, 2001 17:19
> Subject: Re: [idn] spoofing by combining diacritical marks
>
>
> > More self-comment:
> >
> >   Current unicode standard have _no_  normalization rules on
> >     repeated <acute>s ( and other diacritical marks)  to prevent them from
> >     looking differently according to their positions in unicode strings.
> >
> >   The second <Acute> in the <acute><Acute> does not display in some
> >   cases.
> >
> >   This problem is somewhat out of IDN WG scope and should be reviewed
> >   by relevant  standard organizations.
> >
> >   Zone masters should be aware of this and filter out  spoofing domains..
> >
> >  Soobok Lee
> >
> >
> > ----- Original Message -----
> > From: "Soobok Lee" <lsb@postel.co.kr>
> > To: <idn@ops.ietf.org>
> > Sent: Wednesday, August 29, 2001 9:15 AM
> > Subject: [idn] spoofing by combining diacritical marks
> >
> >
> > > Hi,
> > > To exemplify what JCK pointed out,
> > > I took two experiments with two labels with <acute>.
> > > Look into the enclosed excerpts.
> > >
> > > The second  one  has   <acute><acute>,but look the same with
> single-<acute> one.
> > >
> > > Does this problem come from the rendering engine (of win2k)
> > > or from the definition of <acute> itself ?
> > >
> > > Soobok Lee
> >
> > --------------------------------------------------------------------------
> -------------------------------------
> > >
> > > www.k%u0301ol.com
> > >
> > > www.kÌ�ol.com
> > >
> > >
> > >
> > > www.k%u0301%u0301ol.com
> > >
> > >
> > > www.kÌ�Ì�ol.com
> > >
> > >
> > >
> > > <html>
> > > <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
> > > <body>
> > > <Script>
> > > str=("www.k%u0301ol.com");
> > > document.write("<br><font size=+1 face='Times New Roman'>");
> > > document.writeln(str);
> > > document.write("<br><p><font size=+3 face='Times New Roman'>");
> > > document.writeln(unescape(str)); document.write("</font><br><p>");
> > > </script>
> > > <Script>
> > > str=("www.k%u0301%u0301ol.com");
> > > document.write("<br><font size=+1 face='Times New Roman'>");
> > > document.writeln(str);
> > > document.write("<br><p><font size=+3 face='Times New Roman'>");
> > > document.writeln(unescape(str)); document.write("</font><br><p>");
> > > </script>
> > >
> > > http://www.postel.co.kr/etc/f2.html
> > >
> > >
> >
> >
> >
>
>




From owner-idn@ops.ietf.org  Thu Aug 30 00:20: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 AAA18318
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 00:20:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cJBY-000JZy-00
	for idn-data@psg.com; Wed, 29 Aug 2001 21:12:08 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cJBW-000JZC-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 21:12:07 -0700
Received: from LocalHost ([140.115.7.39])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f7U4GG719398;
	Thu, 30 Aug 2001 12:16:18 +0800 (CST)
Message-ID: <002301c13109$8d31c380$2707738c@q.j.tw>
From: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: "John C Klensin" <klensin@jck.com>,
        "Harald Tveit Alvestrand" <harald@alvestrand.no>,
        <liana.ydisg@juno.com>, <James@Seng.cc>
Cc: <huangk@alum.sinica.edu>, <idn@ops.ietf.org>, <dhc@dcrocker.net>
References:  <386302353.999080407@[192.168.1.31]> <150106250.999070275@P2>
Subject: [idn] A Search-based access model & SC/TC conversion 
Date: Thu, 30 Aug 2001 12:09:19 +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.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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  ?  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   ?
> >
> > 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 ?
Does IDNA and nameprep are in the layer of  Layer 2 ?  How a restrict facet
search system  communicate with Layer1 thru which module ?

> all users of URLs based in the Chinese language, and that does
> not fragment the Internet, we also need to be sure that the
> tables and mechanisms that do SC/TC equivalence don't
> accidentally map Kanji or Hangul into SC.

    Does there are a defined port or module interface to let the isolated
function module can be link to cooperation ?  Thanks !

L.M.Tseng




From owner-idn@ops.ietf.org  Thu Aug 30 01:32: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 BAA23248
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 01:32:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cKAT-000M1q-00
	for idn-data@psg.com; Wed, 29 Aug 2001 22:15:05 -0700
Received: from [203.126.116.228] (helo=mail.i-dns.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cKAM-000M1b-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 22:15:00 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id B908EFFC01; Thu, 30 Aug 2001 13:16:03 +0800 (SGT)
Message-ID: <0c9701c13112$b146bce0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Soobok Lee" <lsb@postel.co.kr>, "Mark Davis" <mark@macchiato.com>,
        <idn@ops.ietf.org>
References: <07fe01c1301f$c38865a0$ec1bd9d2@temp> <093c01c130e9$80066320$ec1bd9d2@temp> <006c01c130fc$5d70f420$0c680b41@c1340594a> <09bb01c13103$57915610$ec1bd9d2@temp>
Subject: Re: [idn] spoofing by combining diacritical marks
Date: Thu, 30 Aug 2001 13:14:49 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

What I am hearing is you are asking *standard* to avoid a problem
created by a *broken* implementation. This is too far fetched for me to
understand.

The right thing to do, engineering speaking, is to fix the broken
implementation.

-James Seng

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Mark Davis" <mark@macchiato.com>; <idn@ops.ietf.org>
Sent: Thursday, August 30, 2001 11:24 AM
Subject: Re: [idn] spoofing by combining diacritical marks


> You are right.
>
> The standard is specifying that double <Acute>s should be displayed
with
> stacked <acute>s  above the base character. But Win2K/98 doesn't
display
> them correctly. If <acute> is repeated 10 times, that is beyond most
commercial
> rendering engine's capability and that can be utilized for spoofing
> ONly feasible solution to this problem is  prohibiting them by
zone-masters,i believe.
>
>
> BTW, Unicode Standard Chap2. Section 2.6, Figure 2-10 has an example:
>
>   <latin a><combining dot below><combining dot above>
>   <latin a><combining dot above><combining dot below>
>
>  These two sequences are defined to have the same look
>  But, I can't find yet any _NORMALIZATION_ rules to unify them.
>
>  Does unicode standards have any rules to unify them  ?
>
>  Soobok
>
>
>
> ----- Original Message -----
> From: "Mark Davis" <mark@macchiato.com>
> To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
> Sent: Thursday, August 30, 2001 11:34 AM
> Subject: Re: [idn] spoofing by combining diacritical marks
>
>
> > The standard *does* specify the appropriate display behavior for
such
> > circumstances. See http://www.unicode.org/unicode/uni2book/ch02.pdf,
Section
> > 2.6.
> >
> > However, some implementations may not yet implement that behavior.
> >
> > 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: Wednesday, August 29, 2001 17:19
> > Subject: Re: [idn] spoofing by combining diacritical marks
> >
> >
> > > More self-comment:
> > >
> > >   Current unicode standard have _no_  normalization rules on
> > >     repeated <acute>s ( and other diacritical marks)  to prevent
them from
> > >     looking differently according to their positions in unicode
strings.
> > >
> > >   The second <Acute> in the <acute><Acute> does not display in
some
> > >   cases.
> > >
> > >   This problem is somewhat out of IDN WG scope and should be
reviewed
> > >   by relevant  standard organizations.
> > >
> > >   Zone masters should be aware of this and filter out  spoofing
domains..
> > >
> > >  Soobok Lee
> > >
> > >
> > > ----- Original Message -----
> > > From: "Soobok Lee" <lsb@postel.co.kr>
> > > To: <idn@ops.ietf.org>
> > > Sent: Wednesday, August 29, 2001 9:15 AM
> > > Subject: [idn] spoofing by combining diacritical marks
> > >
> > >
> > > > Hi,
> > > > To exemplify what JCK pointed out,
> > > > I took two experiments with two labels with <acute>.
> > > > Look into the enclosed excerpts.
> > > >
> > > > The second  one  has   <acute><acute>,but look the same with
> > single-<acute> one.
> > > >
> > > > Does this problem come from the rendering engine (of win2k)
> > > > or from the definition of <acute> itself ?
> > > >
> > > > Soobok Lee
> > >
> >
> ----------------------------------------------------------------------
----
> > -------------------------------------
> > > >
> > > > www.k%u0301ol.com
> > > >
> > > > www.kÌ�ol.com
> > > >
> > > >
> > > >
> > > > www.k%u0301%u0301ol.com
> > > >
> > > >
> > > > www.kÌ�Ì�ol.com
> > > >
> > > >
> > > >
> > > > <html>
> > > > <meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
> > > > <body>
> > > > <Script>
> > > > str=("www.k%u0301ol.com");
> > > > document.write("<br><font size=+1 face='Times New Roman'>");
> > > > document.writeln(str);
> > > > document.write("<br><p><font size=+3 face='Times New Roman'>");
> > > > document.writeln(unescape(str));
document.write("</font><br><p>");
> > > > </script>
> > > > <Script>
> > > > str=("www.k%u0301%u0301ol.com");
> > > > document.write("<br><font size=+1 face='Times New Roman'>");
> > > > document.writeln(str);
> > > > document.write("<br><p><font size=+3 face='Times New Roman'>");
> > > > document.writeln(unescape(str));
document.write("</font><br><p>");
> > > > </script>
> > > >
> > > > http://www.postel.co.kr/etc/f2.html
> > > >
> > > >
> > >
> > >
> > >
> >
> >
>
>




From owner-idn@ops.ietf.org  Thu Aug 30 02:07: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 CAA05439
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 02:07:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cKee-000N9t-00
	for idn-data@psg.com; Wed, 29 Aug 2001 22:46: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 15cKed-000N9n-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 22:46: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 OAA07641;
	Thu, 30 Aug 2001 14:45:58 +0900
Message-ID: <09fa01c13117$533eadb0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <James@Seng.cc>, "Mark Davis" <mark@macchiato.com>,
        <idn@ops.ietf.org>
References: <07fe01c1301f$c38865a0$ec1bd9d2@temp> <093c01c130e9$80066320$ec1bd9d2@temp> <006c01c130fc$5d70f420$0c680b41@c1340594a> <09bb01c13103$57915610$ec1bd9d2@temp> <0c9701c13112$b146bce0$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] spoofing by combining diacritical marks
Date: Thu, 30 Aug 2001 14:47:58 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

 Yes, if it is wrong, MS should fix it. But  I guess MS and other implementors would
 like to make a threshold on the max length
of  a sequence of  combining marks  for  single  base character. that is, there may be
some ignored marks in rendering time and that breaks the "unique look" constraint.

Anyway,  now, most people are using  Win2k/9x . aren't they?
Until MS finishes  fixing the rendering engine and  most people use the patched one,
allowing <acute><acute> in IDN label  should be postponed for security reasons.

"Postpone" cannot be put into nameprep, mechanical filtering.   clear.
"Guidelines for zone-masters", optional human filtering in registration phase,
 is the only feasible choice in this case.

That was my point   not clearly  described in my previous email.

Soobok


----- Original Message -----
From: "James Seng/Personal" <James@Seng.cc>
To: "Soobok Lee" <lsb@postel.co.kr>; "Mark Davis" <mark@macchiato.com>; <idn@ops.ietf.org>
Sent: Thursday, August 30, 2001 2:14 PM
Subject: Re: [idn] spoofing by combining diacritical marks


> What I am hearing is you are asking *standard* to avoid a problem
> created by a *broken* implementation. This is too far fetched for me to
> understand.
>
> The right thing to do, engineering speaking, is to fix the broken
> implementation.
>
> -James Seng
>
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: "Mark Davis" <mark@macchiato.com>; <idn@ops.ietf.org>
> Sent: Thursday, August 30, 2001 11:24 AM
> Subject: Re: [idn] spoofing by combining diacritical marks
>
>
> > You are right.
> >
> > The standard is specifying that double <Acute>s should be displayed
> with
> > stacked <acute>s  above the base character. But Win2K/98 doesn't
> display
> > them correctly. If <acute> is repeated 10 times, that is beyond most
> commercial
> > rendering engine's capability and that can be utilized for spoofing
> > ONly feasible solution to this problem is  prohibiting them by
> zone-masters,i believe.
> >
> >
> > BTW, Unicode Standard Chap2. Section 2.6, Figure 2-10 has an example:
> >
> >   <latin a><combining dot below><combining dot above>
> >   <latin a><combining dot above><combining dot below>
> >
> >  These two sequences are defined to have the same look
> >  But, I can't find yet any _NORMALIZATION_ rules to unify them.
> >
> >  Does unicode standards have any rules to unify them  ?
> >
> >  Soobok
> >
> >
> >
> > ----- Original Message -----
> > From: "Mark Davis" <mark@macchiato.com>
> > To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
> > Sent: Thursday, August 30, 2001 11:34 AM
> > Subject: Re: [idn] spoofing by combining diacritical marks
> >
> >
> > > The standard *does* specify the appropriate display behavior for
> such
> > > circumstances. See http://www.unicode.org/unicode/uni2book/ch02.pdf,
> Section
> > > 2.6.
> > >
> > > However, some implementations may not yet implement that behavior.
> > >
> > > 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: Wednesday, August 29, 2001 17:19
> > > Subject: Re: [idn] spoofing by combining diacritical marks
> > >
> > >
> > > > More self-comment:
> > > >
> > > >   Current unicode standard have _no_  normalization rules on
> > > >     repeated <acute>s ( and other diacritical marks)  to prevent
> them from
> > > >     looking differently according to their positions in unicode
> strings.
> > > >
> > > >   The second <Acute> in the <acute><Acute> does not display in
> some
> > > >   cases.
> > > >
> > > >   This problem is somewhat out of IDN WG scope and should be
> reviewed
> > > >   by relevant  standard organizations.
> > > >
> > > >   Zone masters should be aware of this and filter out  spoofing
> domains..
> > > >
> > > >  Soobok Lee
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: "Soobok Lee" <lsb@postel.co.kr>
> > > > To: <idn@ops.ietf.org>
> > > > Sent: Wednesday, August 29, 2001 9:15 AM
> > > > Subject: [idn] spoofing by combining diacritical marks
> > > >
> > > >
> > > > > Hi,
> > > > > To exemplify what JCK pointed out,
> > > > > I took two experiments with two labels with <acute>.
> > > > > Look into the enclosed excerpts.
> > > > >
> > > > > The second  one  has   <acute><acute>,but look the same with
> > > single-<acute> one.
> > > > >
> > > > > Does this problem come from the rendering engine (of win2k)
> > > > > or from the definition of <acute> itself ?
> > > > >
> > > > > Soobok Lee
> > > >
> > >
> > ----------------------------------------------------------------------
> ----
> > > -------------------------------------
> > > > >
> > > > > www.k%u0301ol.com
> > > > >
> > > > > www.kÌ�ol.com
> > > > >
> > > > >
> > > > >
> > > > > www.k%u0301%u0301ol.com
> > > > >
> > > > >
> > > > > www.kÌ�Ì�ol.com
> > > > >
> > > > >
> > > > >
> > > > > <html>
> > > > > <meta http-equiv="Content-Type" content="text/html;
> charset=utf-8">
> > > > > <body>
> > > > > <Script>
> > > > > str=("www.k%u0301ol.com");
> > > > > document.write("<br><font size=+1 face='Times New Roman'>");
> > > > > document.writeln(str);
> > > > > document.write("<br><p><font size=+3 face='Times New Roman'>");
> > > > > document.writeln(unescape(str));
> document.write("</font><br><p>");
> > > > > </script>
> > > > > <Script>
> > > > > str=("www.k%u0301%u0301ol.com");
> > > > > document.write("<br><font size=+1 face='Times New Roman'>");
> > > > > document.writeln(str);
> > > > > document.write("<br><p><font size=+3 face='Times New Roman'>");
> > > > > document.writeln(unescape(str));
> document.write("</font><br><p>");
> > > > > </script>
> > > > >
> > > > > http://www.postel.co.kr/etc/f2.html
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>




From owner-idn@ops.ietf.org  Thu Aug 30 03:00: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 DAA07068
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 03:00:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cLPA-000Ort-00
	for idn-data@psg.com; Wed, 29 Aug 2001 23:34:20 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cLP9-000Orn-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 23:34:19 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id C58C0FFC01; Thu, 30 Aug 2001 14:35:27 +0800 (SGT)
Message-ID: <0ce901c1311d$c8158270$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Soobok Lee" <lsb@postel.co.kr>, "Mark Davis" <mark@macchiato.com>,
        <idn@ops.ietf.org>
References: <07fe01c1301f$c38865a0$ec1bd9d2@temp> <093c01c130e9$80066320$ec1bd9d2@temp> <006c01c130fc$5d70f420$0c680b41@c1340594a> <09bb01c13103$57915610$ec1bd9d2@temp> <0c9701c13112$b146bce0$dd00a8c0@jamessonyvaio> <09fa01c13117$533eadb0$ec1bd9d2@temp>
Subject: Re: [idn] spoofing by combining diacritical marks
Date: Thu, 30 Aug 2001 14:34:12 +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.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, if it is wrong, MS should fix it. But  I guess MS and other
> implementors would like to make a threshold on the max length

There is no "I guess" in a standard. It is either it is compilence to a
standard or it is not.

> Anyway,  now, most people are using  Win2k/9x . aren't they?
> Until MS finishes  fixing the rendering engine and  most people use
the
> patched one, allowing <acute><acute> in IDN label  should be postponed
> for security reasons.

And the problem is? IETF has never been bias on any platform and I dont
expect we started to change our protocol just to accomodate any platform
in particular.

> "Postpone" cannot be put into nameprep, mechanical filtering.   clear.
> "Guidelines for zone-masters", optional human filtering in
registration phase,
>  is the only feasible choice in this case.

I disagree. What makes you sure that there wouldn't be a valid reason to
use a double or triple accute?

-James Seng




From owner-idn@ops.ietf.org  Thu Aug 30 03:02: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 DAA07095
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 03:02:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cLV2-000P6z-00
	for idn-data@psg.com; Wed, 29 Aug 2001 23:40:24 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cLV1-000P6t-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 23:40:23 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 96F4BFFC01; Thu, 30 Aug 2001 14:41:35 +0800 (SGT)
Message-ID: <0cf901c1311e$a350b580$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Soobok Lee" <lsb@postel.co.kr>, "Mark Davis" <mark@macchiato.com>,
        <idn@ops.ietf.org>
Subject: Re: [idn] spoofing by combining diacritical marks
Date: Thu, 30 Aug 2001 14:40:19 +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.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sorry didnt finish the last statement.

I disagree not because I do not think optional filtering is good. I
disagree about making filtering as part of Nameprep standard, especially
one which is optional.

If KRNIC decides that it will do filtering on its zone and registrations
only to accept hanguel characters and not any han ideographs and
european scripts, then it is KRNIC choice. Likewise, other NICs may
decide what is valid or not valid. However, this is a policy decision of
any particular NICs and should not be defined in any standard.

Nameprep is to do preparation of names for names matching, not to impose
filterings rules some NICs thinks it is useful to have.

-James Seng

> > "Postpone" cannot be put into nameprep, mechanical filtering.
clear.
> > "Guidelines for zone-masters", optional human filtering in
> registration phase,
> >  is the only feasible choice in this case.
>
> I disagree. What makes you sure that there wouldn't be a valid reason
to
> use a double or triple accute?
>
> -James Seng
>




From owner-idn@ops.ietf.org  Thu Aug 30 03:07: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 DAA07143
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 03:07:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cLgt-000PbS-00
	for idn-data@psg.com; Wed, 29 Aug 2001 23:52:39 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cLgs-000PbL-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 23:52:39 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id A123FFFC09; Thu, 30 Aug 2001 14:53:49 +0800 (SGT)
Message-ID: <0d0901c13120$58cf7530$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Soobok Lee" <lsb@postel.co.kr>, "Mark Davis" <mark@macchiato.com>,
        <idn@ops.ietf.org>
References: <07fe01c1301f$c38865a0$ec1bd9d2@temp> <093c01c130e9$80066320$ec1bd9d2@temp> <006c01c130fc$5d70f420$0c680b41@c1340594a> <09bb01c13103$57915610$ec1bd9d2@temp> <0c9701c13112$b146bce0$dd00a8c0@jamessonyvaio> <09fa01c13117$533eadb0$ec1bd9d2@temp> <0ce901c1311d$c8158270$dd00a8c0@jamessonyvaio> <0a0e01c1311f$93508740$ec1bd9d2@temp>
Subject: Re: [idn] spoofing by combining diacritical marks
Date: Thu, 30 Aug 2001 14:52:33 +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.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

If that is your intention, then it should not be in Nameprep. The
intention of Nameprep is for prepation for name matching. People who
reads Nameprep are implementors of IDN, not administrator.

What you are looking for is a Best Current Practice draft for operation
of IDN. Currently there is none so my best suggestion is to write a new
I-D on this.

-James Seng

> We seem to have different ideas  about  what "registration guideline"
should be like !
>
> THe "Guidelines"  _won't_ force every zone-master to follow it.
> I _will_ register double or triple <acute>s in my private zone even
with the guidelines!
>
> The guidelines only suggest, not enforce.
>
> It will advice " there are  some dangers
> in allowing various i18n characters in a label, be careful! "
>
> Do you have a different idea ?  enforcing one like nameprep ?
>
> Soobok
>
> > -James Seng
> >
>




From owner-idn@ops.ietf.org  Thu Aug 30 03:08: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 DAA07165
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 03:08:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cLjo-000Phk-00
	for idn-data@psg.com; Wed, 29 Aug 2001 23:55:40 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cLjn-000Phc-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 23:55:39 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id PAA30188;
	Thu, 30 Aug 2001 15:55:25 +0900
Message-ID: <0a2801c13121$07a3c660$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Soobok Lee" <lsb@postel.co.kr>, "Mark Davis" <mark@macchiato.com>,
        <idn@ops.ietf.org>
Subject: Re: [idn] spoofing by combining diacritical marks
Date: Thu, 30 Aug 2001 15:57:27 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message ----- 
From: "Soobok Lee" <lsb@postel.co.kr>
 > 
> BTW, Unicode Standard Chap2. Section 2.6, Figure 2-10 has an example:
> 
>   <latin a><combining dot below><combining dot above>
>   <latin a><combining dot above><combining dot below>
> 
>  These two sequences are defined to have the same look
>  But, I can't find yet any _NORMALIZATION_ rules to unify them.
> 
>  Does unicode standards have any rules to unify them  ?

Let me answer for myself. :-)

Yes.   UTR15 (unicode normalization)
 http://www.unicode.org/unicode/reports/tr15/

describes the concept of canonical ordering  and combining class 
of combining characters.

The two sequences in the example are normalized into one in NFC/NFKC.

Great!


> 
>  Soobok
 




From owner-idn@ops.ietf.org  Thu Aug 30 03:10: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 DAA07204
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 03:10:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cLkx-000Pmy-00
	for idn-data@psg.com; Wed, 29 Aug 2001 23:56:51 -0700
Received: from [217.13.28.204] (helo=eikenes.alvestrand.no)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cLkw-000Pha-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 23:56:50 -0700
Received: from [192.168.1.31] (eikenes.alvestrand.no [217.13.28.203])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id B0D1261DE9; Thu, 30 Aug 2001 08:55:02 +0200 (CEST)
Date: Thu, 30 Aug 2001 08:41:52 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: liana.ydisg@juno.com
Cc: tsenglm@cc.ncu.edu.tw, huangk@alum.sinica.edu, idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <466807223.999160912@localhost>
In-Reply-To: <20010829.181717.-904857.1.liana.ydisg@juno.com>
References:  <20010829.181717.-904857.1.liana.ydisg@juno.com>
X-Mailer: Mulberry/2.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

apologies if this was not clearly communicated....
I speak here as an (opinionated) participant, not as "the IETF".

--On 29. august 2001 18:17 -0700 liana.ydisg@juno.com wrote:

> That is not the case.  If IETF does not want to put TC/SC
> folding in [nameprep], then it has no good reason to
> agree a versioning table to include GB, Big5, KSC, JIS to
>  transliterated ACE map.  In that case, I am no motivation
> to push for Unicode to accept the long list of radicals.
> I can sit back and see how long this will go, as I have been
> assumed that by now the TC/SC should have been in there
> long time ago, which has been proved by James that I
> was wrong.

The group decided a long time ago to go for a single character set,
and chose UNICODE/ISO 10646 for that single character set.
So any place where GB, Big5 and so on touches the system MUST be
outside the parts that are standardized by this group.

..... informative and interesting stuff deleted ...

> If IETF has no architecture to accomodate these types
> of script requirement, and is not planning to use a complete
> list of radicals,  please give me a reason for me to push it for
> Unicode standard.

The IETF is the creation of its members.
We have created an architecture that is dependent on outside parties for 
character set and linguistic expertise as captured in character set 
standards.
When those standards are not available, we cannot use them.

> Another option is that IETF still can go ahead giving the world a
> simple listing of 4128 TC/SC equivalent listing some where
> else, catching up with your product delivering schedule, waiving
>  hands and say: take care of it, but out of my sight.  The end result
>  is just like Unicode imposing a misconception of  TC/SC are
>  two different languges.

Delivering broken solutions is abhorrent to me.
So this option is not an option.

>  I hope my explaination can shed a little
>  light on CNNIC's feeling about TC/SC arguements.  You also
> can tell me that my input is out of the scope of this group, and
> I am ready to leave too.

I think the group will have a better chance of delivering output that is 
useful to both you and me if we declare that the TC/SC issue is not going 
to be solved inside the IDN work.

I believe this problem is hard enough that it has to be solved at another 
level.
Sorry about that.

                Harald




From owner-idn@ops.ietf.org  Thu Aug 30 03:14: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 DAA07253
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 03:14:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cLZn-000PIR-00
	for idn-data@psg.com; Wed, 29 Aug 2001 23:45: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 15cLZm-000PIL-00
	for idn@ops.ietf.org; Wed, 29 Aug 2001 23:45: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 PAA26861;
	Thu, 30 Aug 2001 15:45:01 +0900
Message-ID: <0a0e01c1311f$93508740$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng/Personal" <James@Seng.cc>, "Mark Davis" <mark@macchiato.com>,
        <idn@ops.ietf.org>
References: <07fe01c1301f$c38865a0$ec1bd9d2@temp> <093c01c130e9$80066320$ec1bd9d2@temp> <006c01c130fc$5d70f420$0c680b41@c1340594a> <09bb01c13103$57915610$ec1bd9d2@temp> <0c9701c13112$b146bce0$dd00a8c0@jamessonyvaio> <09fa01c13117$533eadb0$ec1bd9d2@temp> <0ce901c1311d$c8158270$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] spoofing by combining diacritical marks
Date: Thu, 30 Aug 2001 15:47:02 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message ----- 
From: "James Seng/Personal" <James@Seng.cc>
 > > "Postpone" cannot be put into nameprep, mechanical filtering.   clear.
> > "Guidelines for zone-masters", optional human filtering in
> registration phase,
> >  is the only feasible choice in this case.
> 
> I disagree. What makes you sure that there wouldn't be a valid reason to
> use a double or triple accute?
> 
 
We seem to have different ideas  about  what "registration guideline" should be like !

THe "Guidelines"  _won't_ force every zone-master to follow it.
I _will_ register double or triple <acute>s in my private zone even with the guidelines!

The guidelines only suggest, not enforce. 

It will advice " there are  some dangers 
in allowing various i18n characters in a label, be careful! "

Do you have a different idea ?  enforcing one like nameprep ?

Soobok

> -James Seng
> 




From owner-idn@ops.ietf.org  Thu Aug 30 03:33: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 DAA07394
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 03:33:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cMBE-0001ED-00
	for idn-data@psg.com; Thu, 30 Aug 2001 00:24:00 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cMBD-0001E7-00
	for idn@ops.ietf.org; Thu, 30 Aug 2001 00:23: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 JAA12860;
	Thu, 30 Aug 2001 09:18:43 +0200 (MET DST)
Date: Thu, 30 Aug 2001 09:18:24 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>, liana.ydisg@juno.com
cc: tsenglm@cc.ncu.edu.tw, huangk@alum.sinica.edu, idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <9260386.999163103@localhost>
In-Reply-To: <466807223.999160912@localhost>
References:  <20010829.181717.-904857.1.liana.ydisg@juno.com>
 <466807223.999160912@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-08-30 08.41 +0200 Harald Tveit Alvestrand <harald@alvestrand.no>
wrote:

>>  I hope my explaination can shed a little
>>  light on CNNIC's feeling about TC/SC arguements.  You also
>> can tell me that my input is out of the scope of this group, and
>> I am ready to leave too.
> 
> I think the group will have a better chance of delivering output that is
> useful to both you and me if we declare that the TC/SC issue is not going
> to be solved inside the IDN work.
> 
> I believe this problem is hard enough that it has to be solved at another
> level. Sorry about that.

Just because nameprep and what the IDN group is doing is only mechanical
operations on individual characters in a single character set, my view is
that SC<->TC conversion can only be done in a keyword like system before
IDN is even started to be used.

Reason for this is because of the different kind of equality which James
described about a year ago and also described in this document. Especially
see section 2.4.3 about the need for user interaction.

http://www.basistech.com/articles/C2C.html

So, outside of IDN, but most certainly part of a system which is described
in the individual drafts by Dr. Klensin and Mr. Mealling.

Further, as James pointed out, if a registry want to set a policy on what
subset of the characters which IDN group is allowing is to be allowed
(only), that is perfectly alright, but also not part of what the IDN group
is doing.

    paf




From owner-idn@ops.ietf.org  Thu Aug 30 04:01: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 EAA07612
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 04:01:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cMbo-0002IL-00
	for idn-data@psg.com; Thu, 30 Aug 2001 00:51:28 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cMbn-0002IF-00
	for idn@ops.ietf.org; Thu, 30 Aug 2001 00:51:27 -0700
Received: from LocalHost ([140.115.7.39])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f7U7tE705233;
	Thu, 30 Aug 2001 15:55:14 +0800 (CST)
Message-ID: <004501c13128$21bbe760$2707738c@q.j.tw>
From: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: "Harald Tveit Alvestrand" <harald@alvestrand.no>, <liana.ydisg@juno.com>
Cc: <huangk@alum.sinica.edu>, <idn@ops.ietf.org>
References:  <20010829.181717.-904857.1.liana.ydisg@juno.com> <466807223.999160912@localhost>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Thu, 30 Aug 2001 15:48:16 +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.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> >  I hope my explaination can shed a little
> >  light on CNNIC's feeling about TC/SC arguements.  You also
> > can tell me that my input is out of the scope of this group, and
> > I am ready to leave too.
>
> I think the group will have a better chance of delivering output that is
> useful to both you and me if we declare that the TC/SC issue is not going
> to be solved inside the IDN work.
>
> I believe this problem is hard enough that it has to be solved at another
> level.
> Sorry about that.
           The major confusing of CJK  characters can not be solved
especially in gTLD but not in ccTLD. May we suggest the time limitation and
incompleteness of IDN work , so Multilingual.com should not be delivered. It
is too difficult to solve the confliction without local policy and language
related ccTLD as the implicit tag.
           Althout this is not a good method now, but it will not produce
more troubles. The postponding or not do wrong thing is important.

L.M.Tseng




From owner-idn@ops.ietf.org  Thu Aug 30 04:02: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 EAA07623
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 04:02:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cMWM-00023F-00
	for idn-data@psg.com; Thu, 30 Aug 2001 00:45:50 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cMWL-000234-00
	for idn@ops.ietf.org; Thu, 30 Aug 2001 00:45:50 -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 B5F367F49C; Thu, 30 Aug 2001 16:45:09 +0900 (JST)
Message-Id: <4.2.0.58.J.20010830135734.059bf650@mail.asahi-net.or.jp>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 30 Aug 2001 13:58:53 +0900
To: "Soobok Lee" <lsb@postel.co.kr>, "Mark Davis" <mark@macchiato.com>,
        <idn@ops.ietf.org>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] spoofing by combining diacritical marks
In-Reply-To: <09bb01c13103$57915610$ec1bd9d2@temp>
References: <07fe01c1301f$c38865a0$ec1bd9d2@temp>
 <093c01c130e9$80066320$ec1bd9d2@temp>
 <006c01c130fc$5d70f420$0c680b41@c1340594a>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 12:24 01/08/30 +0900, Soobok Lee wrote:
>BTW, Unicode Standard Chap2. Section 2.6, Figure 2-10 has an example:
>
>   <latin a><combining dot below><combining dot above>
>   <latin a><combining dot above><combining dot below>
>
>  These two sequences are defined to have the same look
>  But, I can't find yet any _NORMALIZATION_ rules to unify them.
>
>  Does unicode standards have any rules to unify them  ?

This is one of the main jobs of NFC (and by extension, of NFKC).

I suggest that ask such questions on a different list, e.g.
unicode@unicode.org.

Regards,   Martin.



From owner-idn@ops.ietf.org  Thu Aug 30 05:05: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 FAA08307
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 05:05:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cNaK-0004Ma-00
	for idn-data@psg.com; Thu, 30 Aug 2001 01:54:00 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cNaJ-0004M5-00
	for idn@ops.ietf.org; Thu, 30 Aug 2001 01:53: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 ABC947F49C; Thu, 30 Aug 2001 17:53:15 +0900 (JST)
Message-Id: <4.2.0.58.J.20010830142657.06153780@mail.asahi-net.or.jp>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 30 Aug 2001 17:13:57 +0900
To: liana.ydisg@juno.com, harald@alvestrand.no
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] opting out of SC/TC equivalence
Cc: liana.ydisg@juno.com, tsenglm@cc.ncu.edu.tw, huangk@alum.sinica.edu,
        idn@ops.ietf.org
In-Reply-To: <20010829.181717.-904857.1.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 18:17 01/08/29 -0700, liana.ydisg@juno.com wrote:
>That is not the case.  If IETF does not want to put TC/SC
>folding in [nameprep], then it has no good reason to
>agree a versioning table to include GB, Big5, KSC, JIS to
>  transliterated ACE map.  In that case, I am no motivation
>to push for Unicode to accept the long list of radicals.
>I can sit back and see how long this will go, as I have been
>assumed that by now the TC/SC should have been in there
>long time ago, which has been proved by James that I
>was wrong.

What you are implying here, and you have said elsewhere, is
that the TC/SC problem can be made easier by decomposing
Chinese characters into components (usually called radicals).

It is true that for the bulk of the straightforward TC/SC
equivalences, it is sufficient to just change a single radical,
and that in some other cases, it is sufficient to just change
more than one radical.

However, considering the operational complexities of:

A) Defining and maintaining decompositions of Chinese
    characters into radicals for use in TC/SC mapping.
B) Defining and maintaining TC/SC mappings directly.

are about the same. The size of the tables is the same
order. And in any case, there are exceptions that cannot
be covered by radical decomposition (in particular, there
are exceptions where radical decomposition would give
the WRONG result), so just doing B) is more straightforward.


**But all this is largely irrelevant**, as you say. There are
two problems that are orthogonal to the above choice:

1) The problem of 1-to-many, many-to-1, and many-to-many
    mappings. We have not yet seen a working proposal that
    addresses these.

2) The fact that we have to handle not only Chinese, but
    also Japanese and Korean.

So I agree with you that there is no reason to press the
Unicode consortium to add more radicals, for multiple reasons.

Regards,   Martin.

P.S.: Completely unrelated to IDN:
       I have spent about two years of my life doing research
       on decomposition of Kanji and related subjects, and
       published a few papers.
       If you are interested, please send me private mail,
       and I can send you a .ps version.



From owner-idn@ops.ietf.org  Thu Aug 30 10:31: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 KAA18370
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 10:31:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cSRo-000ETD-00
	for idn-data@psg.com; Thu, 30 Aug 2001 07:05:32 -0700
Received: from femail34.sdc1.sfba.home.com ([24.254.60.24])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cSRo-000ET7-00
	for idn@ops.ietf.org; Thu, 30 Aug 2001 07:05:32 -0700
Received: from c1340594a ([65.11.104.12]) by femail34.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20010830140531.TUMI28036.femail34.sdc1.sfba.home.com@c1340594a>;
          Thu, 30 Aug 2001 07:05:31 -0700
Message-ID: <000001c1315c$d73cc1c0$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
References: <07fe01c1301f$c38865a0$ec1bd9d2@temp> <093c01c130e9$80066320$ec1bd9d2@temp>
Subject: Re: [idn] spoofing by combining diacritical marks
Date: Wed, 29 Aug 2001 19:34:59 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

The standard *does* specify the appropriate display behavior for such
circumstances. See http://www.unicode.org/unicode/uni2book/ch02.pdf, Section
2.6.

However, some implementations may not yet implement that behavior.

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: Wednesday, August 29, 2001 17:19
Subject: Re: [idn] spoofing by combining diacritical marks


> More self-comment:
>
>   Current unicode standard have _no_  normalization rules on
>     repeated <acute>s ( and other diacritical marks)  to prevent them from
>     looking differently according to their positions in unicode strings.
>
>   The second <Acute> in the <acute><Acute> does not display in some
>   cases.
>
>   This problem is somewhat out of IDN WG scope and should be reviewed
>   by relevant  standard organizations.
>
>   Zone masters should be aware of this and filter out  spoofing domains..
>
>  Soobok Lee
>
>
> ----- Original Message -----
> From: "Soobok Lee" <lsb@postel.co.kr>
> To: <idn@ops.ietf.org>
> Sent: Wednesday, August 29, 2001 9:15 AM
> Subject: [idn] spoofing by combining diacritical marks
>
>
> > Hi,
> > To exemplify what JCK pointed out,
> > I took two experiments with two labels with <acute>.
> > Look into the enclosed excerpts.
> >
> > The second  one  has   <acute><acute>,but look the same with
single-<acute> one.
> >
> > Does this problem come from the rendering engine (of win2k)
> > or from the definition of <acute> itself ?
> >
> > Soobok Lee
>
> --------------------------------------------------------------------------
-------------------------------------
> >
> > www.k%u0301ol.com
> >
> > www.kÌ�ol.com
> >
> >
> >
> > www.k%u0301%u0301ol.com
> >
> >
> > www.kÌ�Ì�ol.com
> >
> >
> >
> > <html>
> > <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
> > <body>
> > <Script>
> > str=("www.k%u0301ol.com");
> > document.write("<br><font size=+1 face='Times New Roman'>");
> > document.writeln(str);
> > document.write("<br><p><font size=+3 face='Times New Roman'>");
> > document.writeln(unescape(str)); document.write("</font><br><p>");
> > </script>
> > <Script>
> > str=("www.k%u0301%u0301ol.com");
> > document.write("<br><font size=+1 face='Times New Roman'>");
> > document.writeln(str);
> > document.write("<br><p><font size=+3 face='Times New Roman'>");
> > document.writeln(unescape(str)); document.write("</font><br><p>");
> > </script>
> >
> > http://www.postel.co.kr/etc/f2.html
> >
> >
>
>
>




From owner-idn@ops.ietf.org  Thu Aug 30 10:41: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 KAA18638
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 10:41:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cSgm-000EuA-00
	for idn-data@psg.com; Thu, 30 Aug 2001 07:21:00 -0700
Received: from femail26.sdc1.sfba.home.com ([24.254.60.16])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cSgl-000Eu3-00
	for idn@ops.ietf.org; Thu, 30 Aug 2001 07:20:59 -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 <20010830142058.HTM568.femail26.sdc1.sfba.home.com@c1340594a>;
          Thu, 30 Aug 2001 07:20:58 -0700
Message-ID: <009301c1315f$00033970$0c680b41@c1340594a>
From: "Mark Davis" <mark@macchiato.com>
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
References: <07fe01c1301f$c38865a0$ec1bd9d2@temp> <093c01c130e9$80066320$ec1bd9d2@temp> <006c01c130fc$5d70f420$0c680b41@c1340594a> <09bb01c13103$57915610$ec1bd9d2@temp>
Subject: Re: [idn] spoofing by combining diacritical marks
Date: Thu, 30 Aug 2001 07:21:03 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

A display engine should differentiate between one acute and two acutes.
However, if it doesn't distinguish between 9 acutes and 10 acutes, the
likelyhood of that being used for spoofing is, shall we say, extremely
remote. Someone would have to have a legitimate URL with a singe character
having 9 acutes on it, for someone else to spoof it with 10.

BTW, the recommended fallback, when an accent cannot be properly stacked or
applied to the previous character, is to display it over a dotted circle
after the original base. There is information on this in chapter 5.

The newer versions of systems, using technology such as OpenType, do allow
the proper display of multiple accents.

Mark
â€”â€”â€”â€”â€”

Î“Î½á¿¶Î¸Î¹ ÏƒÎ±Ï…Ï„ÏŒÎ½ â€” Î˜Î±Î»á¿†Ï‚
[http://www.macchiato.com]
----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Mark Davis" <mark@macchiato.com>; <idn@ops.ietf.org>
Sent: Wednesday, August 29, 2001 20:24
Subject: Re: [idn] spoofing by combining diacritical marks


> You are right.
>
> The standard is specifying that double <Acute>s should be displayed with
> stacked <acute>s  above the base character. But Win2K/98 doesn't display
> them correctly. If <acute> is repeated 10 times, that is beyond most
commercial
> rendering engine's capability and that can be utilized for spoofing
> ONly feasible solution to this problem is  prohibiting them by
zone-masters,i believe.
>
>
> BTW, Unicode Standard Chap2. Section 2.6, Figure 2-10 has an example:
>
>   <latin a><combining dot below><combining dot above>
>   <latin a><combining dot above><combining dot below>
>
>  These two sequences are defined to have the same look
>  But, I can't find yet any _NORMALIZATION_ rules to unify them.
>
>  Does unicode standards have any rules to unify them  ?
>
>  Soobok
>
>
>
> ----- Original Message -----
> From: "Mark Davis" <mark@macchiato.com>
> To: "Soobok Lee" <lsb@postel.co.kr>; <idn@ops.ietf.org>
> Sent: Thursday, August 30, 2001 11:34 AM
> Subject: Re: [idn] spoofing by combining diacritical marks
>
>
> > The standard *does* specify the appropriate display behavior for such
> > circumstances. See http://www.unicode.org/unicode/uni2book/ch02.pdf,
Section
> > 2.6.
> >
> > However, some implementations may not yet implement that behavior.
> >
> > 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: Wednesday, August 29, 2001 17:19
> > Subject: Re: [idn] spoofing by combining diacritical marks
> >
> >
> > > More self-comment:
> > >
> > >   Current unicode standard have _no_  normalization rules on
> > >     repeated <acute>s ( and other diacritical marks)  to prevent them
from
> > >     looking differently according to their positions in unicode
strings.
> > >
> > >   The second <Acute> in the <acute><Acute> does not display in some
> > >   cases.
> > >
> > >   This problem is somewhat out of IDN WG scope and should be reviewed
> > >   by relevant  standard organizations.
> > >
> > >   Zone masters should be aware of this and filter out  spoofing
domains..
> > >
> > >  Soobok Lee
> > >
> > >
> > > ----- Original Message -----
> > > From: "Soobok Lee" <lsb@postel.co.kr>
> > > To: <idn@ops.ietf.org>
> > > Sent: Wednesday, August 29, 2001 9:15 AM
> > > Subject: [idn] spoofing by combining diacritical marks
> > >
> > >
> > > > Hi,
> > > > To exemplify what JCK pointed out,
> > > > I took two experiments with two labels with <acute>.
> > > > Look into the enclosed excerpts.
> > > >
> > > > The second  one  has   <acute><acute>,but look the same with
> > single-<acute> one.
> > > >
> > > > Does this problem come from the rendering engine (of win2k)
> > > > or from the definition of <acute> itself ?
> > > >
> > > > Soobok Lee
> > >
> >
> --------------------------------------------------------------------------
> > -------------------------------------
> > > >
> > > > www.k%u0301ol.com
> > > >
> > > > www.kÌ�ol.com
> > > >
> > > >
> > > >
> > > > www.k%u0301%u0301ol.com
> > > >
> > > >
> > > > www.kÌ�Ì�ol.com
> > > >
> > > >
> > > >
> > > > <html>
> > > > <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
> > > > <body>
> > > > <Script>
> > > > str=("www.k%u0301ol.com");
> > > > document.write("<br><font size=+1 face='Times New Roman'>");
> > > > document.writeln(str);
> > > > document.write("<br><p><font size=+3 face='Times New Roman'>");
> > > > document.writeln(unescape(str)); document.write("</font><br><p>");
> > > > </script>
> > > > <Script>
> > > > str=("www.k%u0301%u0301ol.com");
> > > > document.write("<br><font size=+1 face='Times New Roman'>");
> > > > document.writeln(str);
> > > > document.write("<br><p><font size=+3 face='Times New Roman'>");
> > > > document.writeln(unescape(str)); document.write("</font><br><p>");
> > > > </script>
> > > >
> > > > http://www.postel.co.kr/etc/f2.html
> > > >
> > > >
> > >
> > >
> > >
> >
> >
>
>




From owner-idn@ops.ietf.org  Thu Aug 30 11: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 LAA20085
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 11:51:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cTvP-000HPV-00
	for idn-data@psg.com; Thu, 30 Aug 2001 08:40:11 -0700
Received: from [213.86.25.246] (helo=mirth.lon.lab)
	by psg.com with smtp (Exim 3.33 #1)
	id 15cTvO-000HPP-00
	for idn@ops.ietf.org; Thu, 30 Aug 2001 08:40:11 -0700
Received: (qmail 22220 invoked from network); 30 Aug 2001 16:38:24 -0000
Received: from localhost (127.0.0.1)
  by localhost with SMTP; 30 Aug 2001 16:38:24 -0000
Date: Thu, 30 Aug 2001 16:38:24 +0000 (GMT)
From: Mike Astle <astle@new.net>
X-X-Sender:  <astle@mirth.lon.lab>
Reply-To: <idn@ops.ietf.org>
cc: <idn@ops.ietf.org>
Subject: Re: [idn] spoofing by combining diacritical marks
In-Reply-To: <0d0901c13120$58cf7530$dd00a8c0@jamessonyvaio>
Message-ID: <Pine.LNX.4.33.0108301636571.20658-100000@mirth.lon.lab>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Is anyone working on such a document?

On Thu, 30 Aug 2001, James Seng/Personal wrote:

> What you are looking for is a Best Current Practice draft for operation
> of IDN. Currently there is none so my best suggestion is to write a new
> I-D on this.




From owner-idn@ops.ietf.org  Thu Aug 30 12:54: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 MAA21749
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 12:54:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cUsq-000JQP-00
	for idn-data@psg.com; Thu, 30 Aug 2001 09:41: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 15cUsp-000JQH-00
	for idn@ops.ietf.org; Thu, 30 Aug 2001 09:41: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 BAA21039
	for <idn@ops.ietf.org>; Fri, 31 Aug 2001 01:41:21 +0900
Message-ID: <002d01c13172$dfd908a0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: <idn@ops.ietf.org>
References: <Pine.LNX.4.33.0108301636571.20658-100000@mirth.lon.lab>
Subject: [idn] BCP for IDN..
Date: Fri, 31 Aug 2001 01:43:19 +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

IMO,  BCP for IDN is the right place to put  these things:

   :   unassigned code points ( also in nameprep already)
   :   defective combining sequences
          -  umcombined diacritical mark and signs ( <acute>.com)
          -  invalid hangul jamo sequences   
   :   defective-rendering-engine-oriented  "equivalence"
         -  <acute><acute> vs <acute>
   :   similarly-looking characters that can be used for spoofing
         -  <latin 8> and  <bengali 4>
         -  <latin B> and  <cyrillic b>
         -  katakana ka and chinses 'power' letter
   :   special characters (mathematical,dingbets,music signs ...)
   :   other equivalences  relevant to  IPR issues
  
If  and only if TC/SC/Kanji/Hanja equivalences  can't be in nameprep,
  it may be put into here.

May BCP(as informational RFC) be revised and evolved 
even after it is finalized with the minimal set of guidelines for 
idn identifier security ?  
 
I have found some BCPs in the IETF homepage.

  3. http URL:draft-bouwen-megaco-isdn-bcp-01.txt
    Summary
    Title: Best Current Practice for Megaco-Sigtran Interaction in ISDN Acces...

  9. http URL:draft-nickless-ipv4-mcast-bcp-01.txt
    Summary
    Title: IPv4 Multicast Best Current Practice

I am not  a fulltime IETF participants like most of you.
I think  several co-authors with diverse expertise 
should work together to finish this BCP in timely manner.

Soobok


----- Original Message ----- 
From: "Mike Astle" <astle@new.net>
Cc: <idn@ops.ietf.org>
Sent: Friday, August 31, 2001 1:38 AM
Subject: Re: [idn] spoofing by combining diacritical marks


> Is anyone working on such a document?
> 
> On Thu, 30 Aug 2001, James Seng/Personal wrote:
> 
> > What you are looking for is a Best Current Practice draft for operation
> > of IDN. Currently there is none so my best suggestion is to write a new
> > I-D on this.
> 
> 




From owner-idn@ops.ietf.org  Thu Aug 30 13: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 NAA22025
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 13:04:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cV6e-000JuW-00
	for idn-data@psg.com; Thu, 30 Aug 2001 09:55:52 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cV6d-000JuI-00
	for idn@ops.ietf.org; Thu, 30 Aug 2001 09:55:51 -0700
Received: from [165.227.249.20] (ip20.proper.com [165.227.249.20])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7UGtkD12733;
	Thu, 30 Aug 2001 09:55:47 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0510030eb7b41f7a4da1@[165.227.249.20]>
In-Reply-To: <002d01c13172$dfd908a0$ec1bd9d2@temp>
References: <Pine.LNX.4.33.0108301636571.20658-100000@mirth.lon.lab>
 <002d01c13172$dfd908a0$ec1bd9d2@temp>
Date: Thu, 30 Aug 2001 09:55:38 -0700
To: "Soobok Lee" <lsb@postel.co.kr>, <idn@ops.ietf.org>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] BCP for IDN..
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 1:43 AM +0900 8/31/01, Soobok Lee wrote:
>I am not  a fulltime IETF participants like most of you.

Most of us are not "fulltime IETF participants". We have real jobs 
and participate in the IETF either as a small part of those jobs, or 
in our spare time because we feel that it is important. To the best 
of my knowledge, *none* of the people who you see posting regularly 
on this mailing list have the IETF as a full-time job.

>I think  several co-authors with diverse expertise
>should work together to finish this BCP in timely manner.

The first step is to start it. You have already posted a wide variety 
of different ideas as messages on this mailing list, and others have 
posted ideas as well. This is an excellent time for someone (maybe 
you?) to start collecting them into a cohesive Internet Draft that 
the Working Group could look at. Doing so would certainly help gain 
support for the whole concept, and would help focus the Working Group 
as well.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Thu Aug 30 13:46: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 NAA23179
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 13:46:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cVdK-000L8i-00
	for idn-data@psg.com; Thu, 30 Aug 2001 10:29:38 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cVdJ-000L8U-00
	for idn@ops.ietf.org; Thu, 30 Aug 2001 10:29:37 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.8.8/8.8.8) with ESMTP id NAA09989;
	Thu, 30 Aug 2001 13:32:46 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200108301732.NAA09989@nic-naa.net>
To: Mike Astle <astle@new.net>
cc: idn@ops.ietf.org
Subject: Re: [idn] spoofing by combining diacritical marks
Date: Thu, 30 Aug 2001 13:32:46 -0400
From: Eric Brunner <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk


> Is anyone working on such a document?
> 
> On Thu, 30 Aug 2001, James Seng/Personal wrote:
> 
> > What you are looking for is a Best Current Practice draft for operation
> > of IDN. Currently there is none so my best suggestion is to write a new
> > I-D on this.

The subject has come up on a gtldc (ICANN) list. The proposant assumed that
a standard was sufficient, universal, easy, and RSN, and that cc and g rules
were or would be harmonized. Last time I checked there were 267 TLDs in the
root, and a _larger_ number of delegated zones ...

Please see the discussion of scope, "[30]", earlier in this list.

Eric



From owner-idn@ops.ietf.org  Thu Aug 30 13: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 NAA23217
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 13:48:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cVlP-000LT3-00
	for idn-data@psg.com; Thu, 30 Aug 2001 10:37:59 -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 15cVlO-000LSk-00
	for idn@ops.ietf.org; Thu, 30 Aug 2001 10:37:58 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.8.8/8.8.8) with ESMTP id NAA10066;
	Thu, 30 Aug 2001 13:41:13 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200108301741.NAA10066@nic-naa.net>
To: "Soobok Lee" <lsb@postel.co.kr>, "Mark Davis" <mark@macchiato.com>
cc: idn@ops.ietf.org
Subject: Re: [idn] spoofing by combining diacritical marks
Date: Thu, 30 Aug 2001 13:41:13 -0400
From: Eric Brunner <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk


> patched one, allowing <acute><acute> in IDN label  should be postponed
> for security reasons.

Several North American languages use two or more diacriticals. Penobscot
uses as many as four on a single "character", as in (visualize as stacked )

	e''''

E''''ric



From owner-idn@ops.ietf.org  Thu Aug 30 16:00: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 QAA26718
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 16:00:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cXcu-000PkB-00
	for idn-data@psg.com; Thu, 30 Aug 2001 12:37:20 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cXct-000Pjz-00
	for idn@ops.ietf.org; Thu, 30 Aug 2001 12:37:19 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+EESdhpctSHRt+WmtIgKsErHrF+WFU08w==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GD46LWB7; Thu, 30 Aug 2001 15:36:19 EDT
To: harald@alvestrand.no
Cc: liana.ydisg@juno.com, tsenglm@cc.ncu.edu.tw, huangk@alum.sinica.edu,
        idn@ops.ietf.org
Date: Thu, 30 Aug 2001 12:54:17 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010830.125420.-1006133.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-54,56-114
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, Harald,

   I would like to question the original ONE CHARACTER
set charter goal.  Unicode is like a character library.  Even
Chinese had plenty of trouble to use 7,000 character
set through a keyboard.  I know, Japanese has screamed
that Japanese input is a chaos world.  How the large UCS 
would be used by more variety of users worldwide?  Don't
be offended if I say, it is like putting a library on the side of
a freeway and expecting drivers stop and buy a book. 

However, if a sign says:" Next Rest Area, FREE books!"  some
one will stop and look.   That is the Script-Tag is for.  If 
the sign says:"Next Rest Area, Chinese books!"  A non-Chinese
would thank you for that too.  

As to TC/SC, I think the problem can be divided into two 
levels. One level is the mechanical, one-to-one.  They are
the majority and bothering  the readers.  The minority as many
have said those n-to-1problem, normally one of them is
the major one, and the other are minor ones.  There are 
always exceptions!!!  So to benefit the majority, the way to deal
with it is to come up with an arbitary one-to-one, and let Chinese
to fight which one is the major one!   The same principle is
applied to decomposition of a Hanja and Kanji.  When there
is a base, the rest will follow , the application will have
something to conform to.  

I don't care how much information is collected in BCP, the 
solution is lying in IDN to come up with a base for application 
to work for.   If IDN is not the right level to argue this solution, 
then the name is MISLEADING.  However from [RFC 2825],
 I think this is the charter goal of this group.   That is the 
reason I am arguring  for an one-to-one TC/SC and GB, JIS ...
in [nameprep] here and not anywhere else.  You are asking 
for TC/SC equivalent table? It has been there for more than 
a decade already, in the form of GB<=>BIG5.  Why do we need 
a printout of  Unicode "U+3b33 version U+4550"  form to 
conforming with current [nameprep] .txt specification?

Speaking about other groups of linguistic experts.  The UCS
Kangxi radical is a standard set in 300 - 400 years ago, 
Shakespear time.  I would though they are at least should
hide that name to show it is more current.   They are quite
modest  about it, I guess.  We are discussing something like
[UAX15], but much larger.  Where are the experts? Does
linguistists have to be an expert about GB<=>BIG5?  All
the TC/SC and phonetics, radicals are common knowledge
in a grade school dictionary in China.  Only when this group is
ready to listen, and give a  good critics to proposals, given
the expertis this group already have, solution can be reached. 

Liana 


On Thu, 30 Aug 2001 08:41:52 +0200 Harald Tveit Alvestrand
<harald@alvestrand.no> writes:
> apologies if this was not clearly communicated....
> I speak here as an (opinionated) participant, not as "the IETF".
> 
> --On 29. august 2001 18:17 -0700 liana.ydisg@juno.com wrote:
> 
> > That is not the case.  If IETF does not want to put TC/SC
> > folding in [nameprep], then it has no good reason to
> > agree a versioning table to include GB, Big5, KSC, JIS to
> >  transliterated ACE map.  In that case, I am no motivation
> > to push for Unicode to accept the long list of radicals.
> > I can sit back and see how long this will go, as I have been
> > assumed that by now the TC/SC should have been in there
> > long time ago, which has been proved by James that I
> > was wrong.

 ..... informative and interesting stuff deleted ...
> 
> > If IETF has no architecture to accomodate these types
> > of script requirement, and is not planning to use a complete
> > list of radicals,  please give me a reason for me to push it for
> > Unicode standard.
> 
> The IETF is the creation of its members.
> We have created an architecture that is dependent on outside parties 
> for 
> character set and linguistic expertise as captured in character set 
> standards.
> When those standards are not available, we cannot use them.
> 
> > Another option is that IETF still can go ahead giving the world a
> > simple listing of 4128 TC/SC equivalent listing some where
> > else, catching up with your product delivering schedule, waiving
> >  hands and say: take care of it, but out of my sight.  The end 
> result
> >  is just like Unicode imposing a misconception of  TC/SC are
> >  two different languges.
> 
> Delivering broken solutions is abhorrent to me.
> So this option is not an option.
> 
> >  I hope my explaination can shed a little
> >  light on CNNIC's feeling about TC/SC arguements.  You also
> > can tell me that my input is out of the scope of this group, and
> > I am ready to leave too.
> 
> I think the group will have a better chance of delivering output 
> that is 
> useful to both you and me if we declare that the TC/SC issue is not 
> going 
> to be solved inside the IDN work.
> 
> I believe this problem is hard enough that it has to be solved at 
> another 
> level.
> Sorry about that.
> 
>                 Harald
> 



From owner-idn@ops.ietf.org  Thu Aug 30 18:09: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 SAA29007
	for <idn-archive@lists.ietf.org>; Thu, 30 Aug 2001 18:09:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cZcp-0003uv-00
	for idn-data@psg.com; Thu, 30 Aug 2001 14:45:23 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cZco-0003up-00
	for idn@ops.ietf.org; Thu, 30 Aug 2001 14:45:22 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+EESdhpctSHzPIW2iImuqoprjkOQkIqoQ==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GD5DJTHM; Thu, 30 Aug 2001 17:37:30 EDT
To: paf@cisco.com
Cc: harald@alvestrand.no, liana.ydisg@juno.com, tsenglm@cc.ncu.edu.tw,
        huangk@alum.sinica.edu, idn@ops.ietf.org
Date: Thu, 30 Aug 2001 14:55:33 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010830.145535.-990501.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-1,3-94
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, 30 Aug 2001 09:18:24 +0200 =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?=
<paf@cisco.com> writes:
> --On 2001-08-30 08.41 +0200 Harald Tveit Alvestrand 
> <harald@alvestrand.no>
> wrote:
> 
> >>  I hope my explaination can shed a little
> >>  light on CNNIC's feeling about TC/SC arguements.  You also
> >> can tell me that my input is out of the scope of this group, and
> >> I am ready to leave too.
> > 
> > I think the group will have a better chance of delivering output 
> that is
> > useful to both you and me if we declare that the TC/SC issue is 
> not going
> > to be solved inside the IDN work.
> > 
> > I believe this problem is hard enough that it has to be solved at 
> another
> > level. Sorry about that.
> 
> Just because nameprep and what the IDN group is doing is only 
> mechanical
> operations on individual characters in a single character set, my 
> view is
> that SC<->TC conversion can only be done in a keyword like system 
> before
> IDN is even started to be used.
> 
> Reason for this is because of the different kind of equality which 
> James
> described about a year ago and also described in this document. 
> Especially
> see section 2.4.3 about the need for user interaction.
> 
> http://www.basistech.com/articles/C2C.html
> 
> So, outside of IDN, but most certainly part of a system which is 
> described
> in the individual drafts by Dr. Klensin and Mr. Mealling.
> 
> Further, as James pointed out, if a registry want to set a policy on 
> what
> subset of the characters which IDN group is allowing is to be 
> allowed
> (only), that is perfectly alright, but also not part of what the IDN 
> group
> is doing.
> 
>     paf
> 

Chinese world is a complex world.  If we look at it from inside 
and outside, what we see is a mess, that is what I characterize
all the BDP is doing in this area.  In fact, the 80 vs. 20 rule 
applys all the time.  [nameprep] can be a simple list of 
one-to-one mapping to solve the 80% of TC/SC 
equivalence problem with 20% effort, and provide a door for 
GB to have an easy entry to exchange with Unicode, and let 
the other 20% problem to be dealt with under local treatment. 

I have been respecting John's draft and effort on this issue, but
John, I have to be canned about your view on directory search
too.  It makes the issue more complicate than it already is. 
Type and search is only good for character input.  It is painful
already.  None of Chinese will stand for it, that is why there are
a lot of research goes into a Chinese editor for twenty years
in China, and far behind US on computer software development.
Do you recall, that the first MSDOS was reverse engineered by
a Chinese, after Microsoft refused a source license to them?

The solution is to take care the 80% in a simplest way, and
try to hide 20% of the problems. You see this model in all
areas, especially in politics, where most people paying 
attention and criticizing.  When you hear Chinese 
administrators arguing about something, the 95% 
chances are over which one is belong to the 80% 
group :-)  So minority nationalities have over 
80% in numbers, so they are have higher priority on a 
lot of personnel issues regardless their populations.

To the keyword type of solutions, it is good for name 
registration only.  It is slow and painful, a good toy to
study with, but not good to use as day to day tool,
especially unthinkable if I want cut and paste type of
URL implementation.  So, I am agaist keyword search 
type of e-mail addresses, but still interested in
any solutions to guess how it can be implemented in 
English.  

Liana





From owner-idn@ops.ietf.org  Fri Aug 31 01:12: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 BAA09189
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 01:12:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cgGc-000FUb-00
	for idn-data@psg.com; Thu, 30 Aug 2001 21:50:54 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cgGb-000FUU-00
	for idn@ops.ietf.org; Thu, 30 Aug 2001 21:50:53 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 2B0E8FFC01; Fri, 31 Aug 2001 12:51:58 +0800 (SGT)
Message-ID: <008401c131d8$7ef6e050$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: <harald@alvestrand.no>, <liana.ydisg@juno.com>
Cc: <liana.ydisg@juno.com>, <tsenglm@cc.ncu.edu.tw>, <huangk@alum.sinica.edu>,
        <idn@ops.ietf.org>
References: <20010830.125420.-1006133.1.liana.ydisg@juno.com>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 31 Aug 2001 12:50:45 +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

Iiana,

I am not comment on other parts but your presumation that TC/SC can be
done by radical equivalence simplification is unfortunately misplaced.
No doubts there are *some* cases whereby TC->SC can be done by changing
radicals, it is not rule of the thumb.

Once again, you may want to read the problems with TC-SC paper by Jack
Halpern at http://www.basistech.com/articles/C2C.html first on basic
difficulties of TC/SC in general.
http://playground.i-dns.net/one/onec_sum.htm (also by Jack) describes
the more specific difficulties of doing TC-SC in Domain Names.

-James Seng

> As to TC/SC, I think the problem can be divided into two
> levels. One level is the mechanical, one-to-one.  They are
> the majority and bothering  the readers.  The minority as many
> have said those n-to-1problem, normally one of them is
> the major one, and the other are minor ones.  There are
> always exceptions!!!  So to benefit the majority, the way to deal
> with it is to come up with an arbitary one-to-one, and let Chinese
> to fight which one is the major one!   The same principle is
> applied to decomposition of a Hanja and Kanji.  When there
> is a base, the rest will follow , the application will have
> something to conform to.





From owner-idn@ops.ietf.org  Fri Aug 31 03:10: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 DAA26099
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 03:10:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ci2j-000HZB-00
	for idn-data@psg.com; Thu, 30 Aug 2001 23:44:41 -0700
Received: from [217.13.28.204] (helo=eikenes.alvestrand.no)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ci2j-000HXX-00
	for idn@ops.ietf.org; Thu, 30 Aug 2001 23:44:41 -0700
Received: from [192.168.1.31] (eikenes.alvestrand.no [217.13.28.203])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id BB91861C4C; Fri, 31 Aug 2001 08:42:55 +0200 (CEST)
Date: Fri, 31 Aug 2001 08:42:15 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: liana.ydisg@juno.com, paf@cisco.com
Cc: tsenglm@cc.ncu.edu.tw, huangk@alum.sinica.edu, idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <67488453.999247335@[192.168.1.31]>
In-Reply-To: <20010830.145535.-990501.0.liana.ydisg@juno.com>
References:  <20010830.145535.-990501.0.liana.ydisg@juno.com>
X-Mailer: Mulberry/2.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

to my mind, it seems that you can have keyword search with near-perfect 
TC/SC equivalence, OR cut-and-paste URLs and email addresses without TC/SC 
equivalence.

Not both in the same part of the user interface at the same time.

--On 30. august 2001 14:55 -0700 liana.ydisg@juno.com wrote:

> To the keyword type of solutions, it is good for name
> registration only.  It is slow and painful, a good toy to
> study with, but not good to use as day to day tool,
> especially unthinkable if I want cut and paste type of
> URL implementation.  So, I am agaist keyword search
> type of e-mail addresses, but still interested in
> any solutions to guess how it can be implemented in
> English.





From owner-idn@ops.ietf.org  Fri Aug 31 03: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 DAA26195
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 03:18:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ciOl-000IEl-00
	for idn-data@psg.com; Fri, 31 Aug 2001 00:07:27 -0700
Received: from toro.w3.mag.keio.ac.jp ([133.27.228.201])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ciOj-000IEe-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 00:07:25 -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 8A8097F4A2; Fri, 31 Aug 2001 16:06:36 +0900 (JST)
Message-Id: <4.2.0.58.J.20010831160508.037fba60@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 31 Aug 2001 16:07:04 +0900
To: Harald Tveit Alvestrand <harald@alvestrand.no>, liana.ydisg@juno.com,
        paf@cisco.com
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] opting out of SC/TC equivalence
Cc: tsenglm@cc.ncu.edu.tw, huangk@alum.sinica.edu, idn@ops.ietf.org
In-Reply-To: <67488453.999247335@[192.168.1.31]>
References: <20010830.145535.-990501.0.liana.ydisg@juno.com>
 <20010830.145535.-990501.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 08:42 01/08/31 +0200, Harald Tveit Alvestrand wrote:
>to my mind, it seems that you can have keyword search with near-perfect 
>TC/SC equivalence, OR cut-and-paste URLs and email addresses without TC/SC 
>equivalence.
>
>Not both in the same part of the user interface at the same time.

Well, not both in the same protocol at the same time, I fully agree.
But in the same user interface is possible. The newer versions of
both Netscape Navigator and Internet Explorer do a search if
a domain name isn't found.

Regards,   Martin.



From owner-idn@ops.ietf.org  Fri Aug 31 05:02: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 FAA26920
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 05:02:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cjrS-000Jcj-00
	for idn-data@psg.com; Fri, 31 Aug 2001 01:41:10 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cjrR-000Jcd-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 01:41:09 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+EESdhpctSHk50LongsXMYaj9+Jx7gjVQ==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GD6KHDC3; Fri, 31 Aug 2001 04:40:49 EDT
To: James@Seng.cc
Cc: idn@ops.ietf.org
Date: Fri, 31 Aug 2001 01:02:15 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010831.015848.-990501.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-27,29-62
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, 

  That was a miscommunication on my part, that I did not 
amend, since I did not see anyone care about except 
Martin, which I have answered indirectly.  This is
realy two issues. One is one-to-one TC/SC mapping
in [nameprep]. With this part, we shall include GB, Big5,
and a few other standards representing local access
directly to [nameprep] and speeding up hostname 
translation.  This is my 20% effort for 80% TC/SC cases
arguing for. [nameprep] shall only do one-to-one 
mapping, no guessing or second try shall be there at 
all.

Another issue is direct mapping to StepCode part of
the proposal which is mixed up in that short 
communication.  StepCode has Pinyin for each radical
already for SC character set.   More work is needed 
to check against with larger character set such as Big5
and Unicode.   I thought if some published listing may 
help out for Kanji and Hanja to encode,  just an idea to 
throw out to be criticized, it does not mean to play with
TC/SC AI treatment in [nameprep].   After that, I was a 
little regret, since  if the current architecture of [nameprep] 
does not change,  I am putting up more work for nothing. 

Liana

On Fri, 31 Aug 2001 12:50:45 +0800 "James Seng/Personal" <James@Seng.cc>
writes:
> Iiana,
> 
> I am not comment on other parts but your presumation that TC/SC can 
> be
> done by radical equivalence simplification is unfortunately 
> misplaced.
> No doubts there are *some* cases whereby TC->SC can be done by 
> changing
> radicals, it is not rule of the thumb.
> 
> Once again, you may want to read the problems with TC-SC paper by 
> Jack
> Halpern at http://www.basistech.com/articles/C2C.html first on basic
> difficulties of TC/SC in general.
> http://playground.i-dns.net/one/onec_sum.htm (also by Jack) 
> describes
> the more specific difficulties of doing TC-SC in Domain Names.
> 
> -James Seng
> 
> > As to TC/SC, I think the problem can be divided into two
> > levels. One level is the mechanical, one-to-one.  They are
> > the majority and bothering  the readers.  The minority as many
> > have said those n-to-1problem, normally one of them is
> > the major one, and the other are minor ones.  There are
> > always exceptions!!!  So to benefit the majority, the way to deal
> > with it is to come up with an arbitary one-to-one, and let Chinese
> > to fight which one is the major one!   The same principle is
> > applied to decomposition of a Hanja and Kanji.  When there
> > is a base, the rest will follow , the application will have
> > something to conform to.
> 
> 



From owner-idn@ops.ietf.org  Fri Aug 31 05: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 FAA27040
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 05:15:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cjs3-000Jcy-00
	for idn-data@psg.com; Fri, 31 Aug 2001 01:41:47 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cjs2-000Jcs-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 01:41:46 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+EESdhpctSHk50LongsXMZA6CIwdG9S+Q==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GD6KHDFN; Fri, 31 Aug 2001 04:40:49 EDT
To: harald@alvestrand.no
Cc: liana.ydisg@juno.com, paf@cisco.com, tsenglm@cc.ncu.edu.tw,
        huangk@alum.sinica.edu, idn@ops.ietf.org
Date: Fri, 31 Aug 2001 01:58:43 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010831.015848.-990501.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-27,29-49
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 in either/or not both as current ASCII
world.  If we go IDN, a good webpage can display 
IDN or send it out after [nameprep] it.  If you do not 
let TC/SC mapping into [nameprep], all the
 internationalized <Chinese>.com can only use the 
current cut and paste feature with ASCII version, 
which is uniform for everyone.  If you
do let TC/SC into [nameprep] it can have limited 
TC/SC rate, which is good enough for a lot of people. 
This is up to TSCON's definition listing.  Users will
treat technology with a little salt in it.  When a user 
application decide to translate a URL before it is 
displayed or sent out, cut and paste can have a good
 chance to be [nameprep].  Isn't this IDN's goal?  Or
are you thinking of changing everything into UTF-8?

If we follow John's keyword searching scheme, then 
<Chinese>.com has to go through another level of 
guessing stage.  Then it will be impossible for 
<Chinese>.com to get cut and paste feature.  Because  
this becomes an AI technique issue not a font 
display issue any more.  We are dealing with identifiers
not artistics expresstions of an address.  Chinese 
has a lot of aritistry, but hostname is not a place for 
that TC/SC perfection.  

Liana

On Fri, 31 Aug 2001 08:42:15 +0200 Harald Tveit Alvestrand
<harald@alvestrand.no> writes:
> to my mind, it seems that you can have keyword search with 
> near-perfect 
> TC/SC equivalence, OR cut-and-paste URLs and email addresses without 
> TC/SC 
> equivalence.
> 
> Not both in the same part of the user interface at the same time.
> 
> --On 30. august 2001 14:55 -0700 liana.ydisg@juno.com wrote:
> 
> > To the keyword type of solutions, it is good for name
> > registration only.  It is slow and painful, a good toy to
> > study with, but not good to use as day to day tool,
> > especially unthinkable if I want cut and paste type of
> > URL implementation.  So, I am agaist keyword search
> > type of e-mail addresses, but still interested in
> > any solutions to guess how it can be implemented in
> > English.
> 
> 



From owner-idn@ops.ietf.org  Fri Aug 31 06:29: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 GAA27529
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 06:29:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15clFS-000KpV-00
	for idn-data@psg.com; Fri, 31 Aug 2001 03:10:02 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15clFM-000KpI-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 03:09:56 -0700
Received: from LocalHost ([140.115.7.39])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f7VAFF723821;
	Fri, 31 Aug 2001 18:15:15 +0800 (CST)
Message-ID: <001b01c13204$d8e48f00$2707738c@q.j.tw>
From: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: <James@Seng.cc>, <liana.ydisg@juno.com>
Cc: <idn@ops.ietf.org>
References: <20010831.015848.-990501.2.liana.ydisg@juno.com>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 31 Aug 2001 18:08:13 +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.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi !  Liana:
        I have the same feeling . We try  to solve these SC/TC problem step
by step and  to reduce the complexity.  As John had pointed-out in this
listing , sometimes many scripts-only term  will be expand to lanaguage-term
and let some one to neglect the key-point.  1-1 mapping will reduce the
complexity like mixing case of alphabet that will reduce the number of
non-necessary registration and confusing of using.
        No one try to translate TC/SC in DNS. Even an expert of chinese
language also can not resolve  the different local naming  and habit of
personal name in different Province of China.  The PRC-SC is the frequently
used characters in chinese language, some of them can be differentiated by
different shape, but a little of them is easy-to-confuse ,  such as TC(é »)
SC(é¢‘)  SC (ç»Ÿ)  TC (çµ±). James seems avoid to answer what is the first step
to solution.
        If the easy-to-confuse characters can be reduced . Even a little ,
that is better than nothing to do.  Reducing the number of easy-to-confuse
characters in nameprep is a better help to CJK users.
        Always to point out the complexity of chinese language and never to
solve some problem step by step is not a coorect approach in engineering.

L.M.Tseng
----- Original Message -----
From: <liana.ydisg@juno.com>
To: <James@Seng.cc>
Cc: <idn@ops.ietf.org>
Sent: Friday, August 31, 2001 4:02 PM
Subject: Re: [idn] opting out of SC/TC equivalence


> Hi, James,
>
>   That was a miscommunication on my part, that I did not
> amend, since I did not see anyone care about except
> Martin, which I have answered indirectly.  This is
> realy two issues. One is one-to-one TC/SC mapping
> in [nameprep]. With this part, we shall include GB, Big5,
> and a few other standards representing local access
> directly to [nameprep] and speeding up hostname
> translation.  This is my 20% effort for 80% TC/SC cases
> arguing for. [nameprep] shall only do one-to-one
> mapping, no guessing or second try shall be there at
> all.
>
> Another issue is direct mapping to StepCode part of
> the proposal which is mixed up in that short
> communication.  StepCode has Pinyin for each radical
> already for SC character set.   More work is needed
> to check against with larger character set such as Big5
> and Unicode.   I thought if some published listing may
> help out for Kanji and Hanja to encode,  just an idea to
> throw out to be criticized, it does not mean to play with
> TC/SC AI treatment in [nameprep].   After that, I was a
> little regret, since  if the current architecture of [nameprep]
> does not change,  I am putting up more work for nothing.
>
> Liana
>
> On Fri, 31 Aug 2001 12:50:45 +0800 "James Seng/Personal" <James@Seng.cc>
> writes:
> > Iiana,
> >
> > I am not comment on other parts but your presumation that TC/SC can
> > be
> > done by radical equivalence simplification is unfortunately
> > misplaced.
> > No doubts there are *some* cases whereby TC->SC can be done by
> > changing
> > radicals, it is not rule of the thumb.
> >
> > Once again, you may want to read the problems with TC-SC paper by
> > Jack
> > Halpern at http://www.basistech.com/articles/C2C.html first on basic
> > difficulties of TC/SC in general.
> > http://playground.i-dns.net/one/onec_sum.htm (also by Jack)
> > describes
> > the more specific difficulties of doing TC-SC in Domain Names.
> >
> > -James Seng
> >
> > > As to TC/SC, I think the problem can be divided into two
> > > levels. One level is the mechanical, one-to-one.  They are
> > > the majority and bothering  the readers.  The minority as many
> > > have said those n-to-1problem, normally one of them is
> > > the major one, and the other are minor ones.  There are
> > > always exceptions!!!  So to benefit the majority, the way to deal
> > > with it is to come up with an arbitary one-to-one, and let Chinese
> > > to fight which one is the major one!   The same principle is
> > > applied to decomposition of a Hanja and Kanji.  When there
> > > is a base, the rest will follow , the application will have
> > > something to conform to.
> >
> >
>




From owner-idn@ops.ietf.org  Fri Aug 31 06: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 GAA27769
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 06:55:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15clmp-000LHG-00
	for idn-data@psg.com; Fri, 31 Aug 2001 03:44:31 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15clmo-000LHA-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 03:44:30 -0700
Received: from LocalHost ([140.115.7.39])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f7VAlK728505;
	Fri, 31 Aug 2001 18:47:20 +0800 (CST)
Message-ID: <002701c13209$544cd360$2707738c@q.j.tw>
From: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@cisco.com>,
        "Harald Tveit Alvestrand" <harald@alvestrand.no>,
        <liana.ydisg@juno.com>
Cc: <huangk@alum.sinica.edu>, <idn@ops.ietf.org>
References:  <20010829.181717.-904857.1.liana.ydisg@juno.com> <466807223.999160912@localhost> <9260386.999163103@localhost>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 31 Aug 2001 18:40:18 +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.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi !  FÃ¤ltstrÃ¶m :
        I had ask you a question in our discussion why not also put alphabet
case holding in keyword system ?
I do not like to push things in this way,  that must hurt everybody, but I
must point out how many cobinations of name in  case mixing of  Alphabet
will be produced in name registration ?
        Even in CJK area , we all have no complete total solution to reduce
the complexity in this open set characteristics, but it not means we do not
care it.  The confusing must be reduced as more as possible, no to produce
them more by keyword system. I think it is unfair to let keyword system
become a trouble sources of CJK characters.

> --On 2001-08-30 08.41 +0200 Harald Tveit Alvestrand <harald@alvestrand.no>
> wrote:
>
> >>  I hope my explaination can shed a little
> >>  light on CNNIC's feeling about TC/SC arguements.  You also
> >> can tell me that my input is out of the scope of this group, and
> >> I am ready to leave too.
> >
> > I think the group will have a better chance of delivering output that is
> > useful to both you and me if we declare that the TC/SC issue is not
going
> > to be solved inside the IDN work.
> >
> > I believe this problem is hard enough that it has to be solved at
another
> > level. Sorry about that.
>
> Just because nameprep and what the IDN group is doing is only mechanical
> operations on individual characters in a single character set, my view is
> that SC<->TC conversion can only be done in a keyword like system before
> IDN is even started to be used.
>
> Reason for this is because of the different kind of equality which James
> described about a year ago and also described in this document. Especially
> see section 2.4.3 about the need for user interaction.
>
> http://www.basistech.com/articles/C2C.html

I must  say that most of them are language related , not related to
easy-to-confuse scipts or characters.
>
> So, outside of IDN, but most certainly part of a system which is described
> in the individual drafts by Dr. Klensin and Mr. Mealling.
>
> Further, as James pointed out, if a registry want to set a policy on what
> subset of the characters which IDN group is allowing is to be allowed
> (only), that is perfectly alright, but also not part of what the IDN group
> is doing.
>

L.M.Tseng




From owner-idn@ops.ietf.org  Fri Aug 31 07:17: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 HAB28573
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 07:17:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cmAi-000LcY-00
	for idn-data@psg.com; Fri, 31 Aug 2001 04:09:12 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cmAh-000LcS-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 04:09:11 -0700
Received: from dhcp-64-103-49-17.cisco.com (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id NAA02740;
	Fri, 31 Aug 2001 13:07:42 +0200 (MET DST)
Date: Fri, 31 Aug 2001 13:07:13 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: "=?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?=" <tsenglm@cc.ncu.edu.tw>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, liana.ydisg@juno.com
cc: huangk@alum.sinica.edu, idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <3247187.999263233@localhost>
In-Reply-To: <002701c13209$544cd360$2707738c@q.j.tw>
References:  <20010829.181717.-904857.1.liana.ydisg@juno.com>
 <466807223.999160912@localhost> <9260386.999163103@localhost>
 <002701c13209$544cd360$2707738c@q.j.tw>
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-08-31 18.40 +0800
"=?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?="
<tsenglm@cc.ncu.edu.tw> wrote:

>         I had ask you a question in our discussion why not also put
> alphabet case holding in keyword system ?

The simple answer is that the Unicode Consortium have defined "case
folding", and other kind of equivalence tables. All of them are mechanical
mappings, and we have in the IDN group chosen to include them in the
nameprep algorithm.

If some of them should be removed, or if some should be added, that is a
valid discussion.

If a table existed which handled mappings between TC and SC, we could of
course use it.

The problem is that such a table doesn't seem to exist. I have seen in one
draft (as Harald points out) a table with approximately 2000 characters out
of the 20-40000 which exists. Harald have asked valid questions about what
to do with the other characters.

Further, you should not compare SC-TC equivalence with case folding inside
one script, for example Latin. Instead you should compare with the fact
that the same, and similar, characters exists in Greek, Latin and Cyrillic
scripts. For example the character which looks like 'A'.

We do _NOT_ have solutions to that kind of equivalence between different
scripts for non-chinese characters.

Because of that, I feel that if you don't have a table, then you ask for a
solution for chinese characters which we don't solve for other scripts in
the world.

Further, you say that the number of permutations will be high. Linguistics
I have talked with say that the number of permutations will be low, i.e.
that one label is in most cases either in SC or TC.

I don't know, and don't care, what the correct asnswer is. But what
troubles me is that people which really do know chinese characters and
scripts say so different things. I don't hear one story. That makes
discussions very problematic.

    Regards, Patrik




From owner-idn@ops.ietf.org  Fri Aug 31 08:59: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 IAA03188
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 08:59:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cnjP-000Mzr-00
	for idn-data@psg.com; Fri, 31 Aug 2001 05:49:07 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cnjO-000MzO-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 05:49:06 -0700
Received: from LocalHost ([140.115.7.39])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f7VCrw720731;
	Fri, 31 Aug 2001 20:53:58 +0800 (CST)
Message-ID: <000f01c1321b$03b9d260$2707738c@q.j.tw>
From: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@cisco.com>,
        "Harald Tveit Alvestrand" <harald@alvestrand.no>,
        <liana.ydisg@juno.com>
Cc: <huangk@alum.sinica.edu>, <idn@ops.ietf.org>
References:  <20010829.181717.-904857.1.liana.ydisg@juno.com> <466807223.999160912@localhost> <9260386.999163103@localhost> <002701c13209$544cd360$2707738c@q.j.tw> <3247187.999263233@localhost>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Fri, 31 Aug 2001 20:46:53 +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.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi ! FÃ¤ltstrÃ¶m :
> >         I had ask you a question in our discussion why not also put
> > alphabet case holding in keyword system ?
>
> The simple answer is that the Unicode Consortium have defined "case
> folding", and other kind of equivalence tables. All of them are mechanical
> mappings, and we have in the IDN group chosen to include them in the
> nameprep algorithm.
>
> If some of them should be removed, or if some should be added, that is a
> valid discussion.
>
       Thanks  your careful concern , I  expect that mechanism can be used
to all scripts to reduce the confusing. The work can not be completed at one
night ! But by this way , that can be improved step by step.
> If a table existed which handled mappings between TC and SC, we could of
> course use it.
>
> The problem is that such a table doesn't seem to exist. I have seen in one
> draft (as Harald points out) a table with approximately 2000 characters
out
> of the 20-40000 which exists. Harald have asked valid questions about what
> to do with the other characters.
>
      If you ask an expert of chinese language to give you this "completed
table", it will be never delivered , because the characters are in an open
set. Even we use chinese, we just use not more than 8000 frequently used
characters in our newspaper . So no one will answer this impossible
problems.  As I have mensioned  most PRC-SC are frequently used and some of
them are quick-written font that are very similar to formal-written font ,
so the problem of easy-to-confuse is serious, especially in Hong-Kong, the
mixing of  SC/TC  will produce more confusing domain name.  We can not
solved all of them , but we can reduce the troubles by doing some character
mapping .
> Further, you should not compare SC-TC equivalence with case folding inside
> one script, for example Latin. Instead you should compare with the fact
> that the same, and similar, characters exists in Greek, Latin and Cyrillic
> scripts. For example the character which looks like 'A'.
>
> We do _NOT_ have solutions to that kind of equivalence between different
> scripts for non-chinese characters.
>
    I  hope  IDN WG can inform the related NIC to propose the mapping table
in UNICODE  to reduce the confusing in their scripts.
> Because of that, I feel that if you don't have a table, then you ask for a
> solution for chinese characters which we don't solve for other scripts in
> the world.
>
> Further, you say that the number of permutations will be high. Linguistics
> I have talked with say that the number of permutations will be low, i.e.
> that one label is in most cases either in SC or TC.
>
        That is true in GB and BIG5 , so UNAME draft show the example of
registration in full SC (pure GB not  GBK) and full TC  not the mixing ,
but the GBK used in Hong-Kong including part of  frequently used TC
characters are  mixing  of  SC and TC .  The  chinese.com  does not limit
the mixing of  SC/TC in UNICODE form.

> I don't know, and don't care, what the correct asnswer is. But what
> troubles me is that people which really do know chinese characters and
> scripts say so different things. I don't hear one story. That makes
> discussions very problematic.
>
        The fact is that there are many part and many case applied in
different situations. The culture of chinese characters is the
characteristics of an open set. That is very different with western model
based on simple basic elements.
        Just  like we present mapping by table first and you may like to
present it by transformation formula first. That is all based on historic
experiences.

Thanks your help to solve our problems.

L.M.Tseng





From owner-idn@ops.ietf.org  Fri Aug 31 09:05: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 JAA03477
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 09:05:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cnt5-000N9R-00
	for idn-data@psg.com; Fri, 31 Aug 2001 05:59:07 -0700
Received: from [217.13.28.204] (helo=eikenes.alvestrand.no)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cnt4-000N7V-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 05:59:07 -0700
Received: from [192.168.1.31] (eikenes.alvestrand.no [217.13.28.203])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id D8E9161C4C; Fri, 31 Aug 2001 14:57:47 +0200 (CEST)
Date: Fri, 31 Aug 2001 14:56:38 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: "=?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?=" <tsenglm@cc.ncu.edu.tw>,
        "=?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?=" <paf@cisco.com>,
        liana.ydisg@juno.com
Cc: huangk@alum.sinica.edu, idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <18529644.999269797@[192.168.1.31]>
In-Reply-To: <000f01c1321b$03b9d260$2707738c@q.j.tw>
References:  <000f01c1321b$03b9d260$2707738c@q.j.tw>
X-Mailer: Mulberry/2.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



--On 31. august 2001 20:46 +0800 
"=?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?=" 
<tsenglm@cc.ncu.edu.tw> wrote:

>> The problem is that such a table doesn't seem to exist. I have seen in
>> one draft (as Harald points out) a table with approximately 2000
>> characters
> out
>> of the 20-40000 which exists. Harald have asked valid questions about
>> what to do with the other characters.
>>
>       If you ask an expert of chinese language to give you this "completed
> table", it will be never delivered , because the characters are in an open
> set. Even we use chinese, we just use not more than 8000 frequently used
> characters in our newspaper . So no one will answer this impossible
> problems.

Please then answer a simpler one:

When the matching algorithm you envision encounters a character where the 
tables do not tell what to do about it, what will the algorithm do to it?
Pass it through unmodified? Reject it? Does something else which you have 
not defined yet?

If you tell us this, and claim that this is acceptable treatment of the 
20-40.000 characters not in the tables, we can at least discuss this 
proposal (whether such a partial TC/SC mapping is acceptable), instead of 
asking again and again what to do about them.

But it is impossible to implement an algorithm which says "this part will 
be worked out later".

                  Harald




From owner-idn@ops.ietf.org  Fri Aug 31 11: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 LAA07583
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 11:14:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cpgS-000OlC-00
	for idn-data@psg.com; Fri, 31 Aug 2001 07:54:12 -0700
Received: from songbird.com ([208.184.79.7] helo=joy.songbird.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cpgR-000Ol6-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 07:54:11 -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 HAA24717
	for <idn@ops.ietf.org>; Fri, 31 Aug 2001 07:54:11 -0700
Message-Id: <5.1.0.14.2.20010831074928.03a06e28@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 31 Aug 2001 07:55:18 -0700
To: idn@ops.ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Subject: [idn] Working group focus -- and progress
In-Reply-To: <3247187.999263233@localhost>
References: <002701c13209$544cd360$2707738c@q.j.tw>
 <20010829.181717.-904857.1.liana.ydisg@juno.com>
 <466807223.999160912@localhost>
 <9260386.999163103@localhost>
 <002701c13209$544cd360$2707738c@q.j.tw>
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

Folks,

At 04:07 AM 8/31/2001, Patrik Fältström wrote:
>If a table existed which handled mappings between TC and SC, we could of
>course use it.
>...
>Further, you should not compare SC-TC equivalence with case folding inside
>one script, for example Latin. Instead you should compare with the fact
>that the same, and similar, characters exists in Greek, Latin and Cyrillic
>scripts. For example the character which looks like 'A'.


The second statement is the more important point:  It is the reason that 
this entire topic is entirely OUT OF SCOPE for this working group.  It is 
therefore the reason that the topic needs to be moved off of this list, so 
that the working group can work on finishing tasks that are WITHIN the charter.

There is a rumor that some people actually want to use the results of this 
working group, and that they want to use the results AS SOON AS POSSIBLE.

Having discussions that are outside the scope of the working group hurts 
that goal.

It does not matter that this discussion is both important and 
interesting.  What DOES matter is that it is causing further delay, for a 
working group effort that has already gone on much longer than it should have.

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 Aug 31 12:59: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 MAA10352
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 12:59:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15crQs-0000Tx-00
	for idn-data@psg.com; Fri, 31 Aug 2001 09:46:14 -0700
Received: from dove.cc.ncu.edu.tw ([140.115.17.111])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15crQr-0000Tm-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 09:46:13 -0700
Received: from LocalHost ([140.115.7.39])
	(authenticated tsenglm (0 bits))
	by dove.cc.ncu.edu.tw (8.11.2/8.11.2/dove/0.0.4) with ESMTP id f7VGpB703424;
	Sat, 1 Sep 2001 00:51:11 +0800 (CST)
Message-ID: <002c01c1323c$29b77500$2707738c@q.j.tw>
From: =?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>
To: "Harald Tveit Alvestrand" <harald@alvestrand.no>,
        "=?utf-8?B?UGF0cmlrIEbDg8KkbHRzdHLDg8K2bQ==?=" <paf@cisco.com>,
        <liana.ydisg@juno.com>, "hlqian" <hlqian@cnnic.net.cn>
Cc: <huangk@alum.sinica.edu>, <idn@ops.ietf.org>
References:  <000f01c1321b$03b9d260$2707738c@q.j.tw> <18529644.999269797@[192.168.1.31]>
Subject: Re: [idn] opting out of SC/TC equivalence
Date: Sat, 1 Sep 2001 00:44:05 +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.4522.1200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

> >> The problem is that such a table doesn't seem to exist. I have seen in
> >> one draft (as Harald points out) a table with approximately 2000
> >> characters
> > out
> >> of the 20-40000 which exists. Harald have asked valid questions about
> >> what to do with the other characters.
> >>
> >       If you ask an expert of chinese language to give you this
"completed
> > table", it will be never delivered , because the characters are in an
open
> > set. Even we use chinese, we just use not more than 8000 frequently used
> > characters in our newspaper . So no one will answer this impossible
> > problems.
>
> Please then answer a simpler one:
>
> When the matching algorithm you envision encounters a character where the
> tables do not tell what to do about it, what will the algorithm do to it?
> Pass it through unmodified? Reject it? Does something else which you have
> not defined yet?
>
           The 1-1 mapping table first treated the frequently used
characters in TC and SC . I  have suggest CJK  people to review the level of
easy-to-confuse in font scripts in draft of  tsconv and to remove some pair
that is concerned  in different language using.  I think  no  CJK people
like to use some characters to confuse with each others.  So , this is a
simple character mapping table in UNICODE TR 20 that can be  major concerned
to easy-to-confuse only.   A matching algorithm can be  table driven in
treat her input and stored data to check it is  in the equivalent set  and
convert it to the defined standard scripts, if it is a character not in the
defined equivalent set why it should be convertyed ?

> If you tell us this, and claim that this is acceptable treatment of the
> 20-40.000 characters not in the tables, we can at least discuss this
> proposal (whether such a partial TC/SC mapping is acceptable), instead of
> asking again and again what to do about them.
>
           As Patrik FÃƒÂ¤ltstrÃƒÂ¶m  described , if it is a mechanism in
UNICODE consosium , then they have the version update procedures and IDNA
also treat  the version update in UNICODE , why it can not be updated step
by step  to  increse it ?  The most important thing is tell user in
registration time what character set is treated as equivalence and what is
not  and what is the current rage of total characters can be used .  The
procedure and announcement is important and not the boundary of range is
important. If the range is monotonically increasing and new added will be
fully cross checked , it is in the correct way .
            The most important thing in CJK area is that the allowed
characters set must be announced by official organization of goverment .  So
, each  ccNIC  need time to exchange informations.

> But it is impossible to implement an algorithm which says "this part will
> be worked out later".
>
   The algorithm has no change , it just increase the data scale . If the
range of data is still in this type of algorithm defined  , why it can not
work ?
   The  problem is in version control if you change the function part. If
function is still applied to the new data , there are no problems in
algorithm.

L.M.Tseng





From owner-idn@ops.ietf.org  Fri Aug 31 14:24: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 OAA12830
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 14:24:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cspG-0001wW-00
	for idn-data@psg.com; Fri, 31 Aug 2001 11:15:30 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cspF-0001wO-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 11:15:29 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+EESdhpctSH+19xr8QL+5KoqF5RaLgojg==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GD7K8FBW; Fri, 31 Aug 2001 14:12:39 EDT
To: dhc@dcrocker.net
Cc: harald@alvestrand.no, idn@ops.ietf.org
Date: Fri, 31 Aug 2001 11:30:46 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010831.113049.-811311.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-44,46-76
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 do have a proposal, but it is not complete. I am 
waiting for references to be arrived from US mail.

The relevent part of the proposal of this discussion
has two parts: Using script tags to patrol certain 
range of UCS which is relevent to that scripts.  This
is posted a few days ago, no one seems to care
about.

The second relevent part of this discussion is a 
relational database model of [nameprep], I had
three postings on it too.  Nobody seems care about it 
either.  Why do I want to talk more about it?

Talking about scoping of this WG? which is defined
in [RFC 2825].  Please check it. 

To answer John's question:

>And, unless whatever is done is isolated -- through procedures,
>structure, or layering-- in a way that is robust, accessible to
>all users of URLs based in the Chinese language, and that does
>not fragment the Internet, we also need to be sure that the
>tables and mechanisms that do SC/TC equivalence don't
>accidentally map Kanji or Hangul into SC.
>
>   john
>

A part of the database table look like this:

Unicode	     Unicode    GB	  BIG5     Chinese		Unicode   KSC    Korean		
CJK	     TC	              		StepCode	Hangul		StepCode

For some rows Korean does not use, which would be empty.
This is one search operation for mapping and ACE encoding!
And this will take care of Kanji, Greek and Cyrillic mapping too.

When IETF accepting this model and let local standards have
direct access of [nameprep] the GB<=>BIG5 mapping takes
care of TC/SC mapping table. 

Liana


On Wed, 29 Aug 2001 07:07:57 -0700 Dave Crocker <dhc@dcrocker.net>
writes:
> At 01:20 AM 8/29/2001, Harald Tveit Alvestrand wrote:
> >--On 28. august 2001 13:40 -0700 liana.ydisg@juno.com wrote:
> >>    I happend to have an idea that 1100 half size
> >>code point may solve part of the problem and another 200
> >>TC/SC listing completes it.  This can be used in [nameprep].
> >>What do you think?
> >
> >I would be happy to see a complete proposal.
> 
> 
> Excuse me, but I had the impression that solving this problem was 
> rather 
> clearly outside of the requirements for this working group.
> 
> At a minimum, it would be very helpful to get explicit resolution 
> about the 
> requirement to solve this, in this working group, as well as the 
> requirement to solve it immediately, rather than consider it for a 
> later 
> version of the working group effort.
> 
> 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 Aug 31 14:30: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 OAA12980
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 14:30:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15csvs-00022u-00
	for idn-data@psg.com; Fri, 31 Aug 2001 11:22:20 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15csvr-00022o-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 11:22:19 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA01423;
        Fri, 31 Aug 2001 14:22:16 -0400 (EDT)
Message-Id: <200108311822.OAA01423@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Dave Crocker <dhc@dcrocker.net>
cc: idn@ops.ietf.org
Subject: Re: [idn] Working group focus -- and progress 
In-reply-to: Your message of "Fri, 31 Aug 2001 07:55:18 PDT."
             <5.1.0.14.2.20010831074928.03a06e28@dcrocker.net> 
Date: Fri, 31 Aug 2001 14:22:16 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> The second statement is the more important point:  It is the reason that
> this entire topic is entirely OUT OF SCOPE for this working group.
...
> There is a rumor that some people actually want to use the results of this
> working group, and that they want to use the results AS SOON AS POSSIBLE.

...regardless of whether or not those results work well.

yes, I am quite sure that you are correct.

it's also clear that any DNS-compatible solution will have significant 
problems with transcription (either written to typed or audible to typed)
in some languages.

addressing this may be out of scope for this WG, but that doesn't mean
that IDNs can be made to work well without addressing it.

and yet this WG clearly lacks sufficient expertise to solve this problem 
no matter what the WG charter says.

it appears that the best this WG can do is 

	- identify known limitations with its approach

	- state any known workarounds for those limitations

	- define or suggest some mechanism (if any can be found)
	  for the IDN resolution infrastructure to be upgraded
	  at a later date to better solve the transcription problems.

Keith



From owner-idn@ops.ietf.org  Fri Aug 31 14:35: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 OAA13111
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 14:35:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ct12-0002AE-00
	for idn-data@psg.com; Fri, 31 Aug 2001 11:27:40 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15ct11-0002A8-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 11:27:40 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+EESdhpctSH9B5JBnblR9FTP34rS2qvXg==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GD7LZGRV; Fri, 31 Aug 2001 14:26:20 EDT
To: duerst@w3.org
Cc: klensin@jck.com, harald@alvestrand.no, liana.ydisg@juno.com, James@Seng.cc,
        tsenglm@cc.ncu.edu.tw, huangk@alum.sinica.edu, idn@ops.ietf.org,
        dhc@dcrocker.net
Date: Fri, 31 Aug 2001 11:44:27 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010831.114430.-811311.1.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.11
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

That is the requirement, and we can make a new 
architecture proposal, and let Latin script go 
forward for ML.com in a timely maner, and let
CJK works on their own Tagged conversion,
reversion, display, and TC/SC procedures. 
The proposed architecture has no conflict with
the work already done in this group.

Anyway, you CAN deliever this ML.com and chuck
our input .  The world is not going to stop without
any of us.

Liana


On Wed, 29 Aug 2001 20:45:05 +0900 Martin Duerst <duerst@w3.org> writes:
> At 07:31 01/08/29 -0400, John C Klensin wrote:
> >And, unless whatever is done is isolated -- through procedures,
> >structure, or layering-- in a way that is robust, accessible to
> >all users of URLs based in the Chinese language, and that does
> >not fragment the Internet, we also need to be sure that the
> >tables and mechanisms that do SC/TC equivalence don't
> >accidentally map Kanji or Hangul into SC.
> 
> No problem for Hangul, which is a completely different script.
> But for most Hanja (ideographs as used in Korea) and many Kanji
> (only many because some are already the same as SC, and in
> some cases, Japan has it's own simplifications), there is
> absolutely no chance to be successful (i.e. only map SC/TC,
> but not Hanja or Kanji). If that's the requirement (and I
> agree it is), then we don't have to continue the discussion.
> Sorry if I disappoint anybody :-(.
> 
> Regards,   Martin.
> 



From owner-idn@ops.ietf.org  Fri Aug 31 15:21: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 PAA14542
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 15:21:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ctjZ-0002qZ-00
	for idn-data@psg.com; Fri, 31 Aug 2001 12:13:41 -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 15ctjY-0002qR-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 12:13:41 -0700
Received: from zetnet.co.uk (man-s044.dialup.zetnet.co.uk [194.247.41.171])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f7VJD5b20989;
	Fri, 31 Aug 2001 20:13:06 +0100
Message-ID: <3B8E5F56.9071F3FF@zetnet.co.uk>
Date: Thu, 30 Aug 2001 16:44:22 +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: tsenglm@cc.ncu.edu.tw, idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
References: <20010829.181717.-904857.1.liana.ydisg@juno.com> <466807223.999160912@localhost> <9260386.999163103@localhost> <002701c13209$544cd360$2707738c@q.j.tw> <3247187.999263233@localhost> <000f01c1321b$03b9d260$2707738c@q.j.tw>
Content-Type: text/plain; charset=UTF-8
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA14542

-----BEGIN PGP SIGNED MESSAGE-----

tsenglm@cc.ncu.edu.tw wrote:
> Patrick FÃ¤ltstrÃ¶m wrote:
> > Further, you say that the number of permutations will be high. [Linguists]
> > I have talked with say that the number of permutations will be low, i.e.
> > that one label is in most cases either in SC or TC.
>
>         That is true in GB and BIG5 , so UNAME draft show the example of
> registration in full SC (pure GB not  GBK) and full TC  not the mixing ,
> but the GBK used in Hong-Kong including part of  frequently used TC
> characters are  mixing  of  SC and TC .  The  chinese.com  does not limit
> the mixing of  SC/TC in UNICODE form.

Provided that input mechanisms can be set to produce all SC or all TC,
does that matter? In practice, would a Chinese input mechanism, as it
would be set up for a user in Hong Kong, say, typically produce an
arbitrary mix of SC and TC characters?

Note that there are other scripts which have special requirements for typing
domain names, URIs and email addresses - for example Arabic and Hebrew. So
in general, fully satisfactory user input of these identifiers will depend
on support from input mechanisms (and in some cases the user telling the
input mechanism that an identifier is being entered, if it appears in free
text). Chinese is just another case where this support would be useful.

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

iQEVAwUBO45fFzkCAxeYt5gVAQHyGwgAvGsc6tKwq5+eNoxAEfZPYkgO56Oz9yMT
tMK7Ggl+YtIxeJ53IWUcUKR0H0SUwXkqHxVsFo/unQXcU2iq/VMt57oG8HYBE/nh
oMrl4A3hpU4krjJQMnU8HTrkxJ4/N8NQ/85cPH3vXkH4GW4uV6SyWpiFzuwZDJdf
EUhE30t3X/3+8YHF2BU3RdQeH/zvljCsRcNrMLRIAQ6wUcwSyF07tKeH0uHu1QBt
p4pkGPIeztpvKNfqjCMwWzyvaG6N/zs+HSOwUE6dNZsz9jF0WCbJ0pLbDcMdMzv+
3IIpgYcoAiGyKWjWq8nkNZ5E4rn8/+oQ8zdMdKCUPdGBm5B5unLPNA==
=MU4x
-----END PGP SIGNATURE-----





From owner-idn@ops.ietf.org  Fri Aug 31 16:09: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 PAA14543
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 15:21:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15ctjW-0002qP-00
	for idn-data@psg.com; Fri, 31 Aug 2001 12:13:38 -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 15ctjV-0002qH-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 12:13:38 -0700
Received: from zetnet.co.uk (man-s044.dialup.zetnet.co.uk [194.247.41.171])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f7VJDBb21008;
	Fri, 31 Aug 2001 20:13:11 +0100
Message-ID: <3B8E67BC.5F9B8D9B@zetnet.co.uk>
Date: Thu, 30 Aug 2001 17:20:12 +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: tsenglm@cc.ncu.edu.tw, idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
References: <000f01c1321b$03b9d260$2707738c@q.j.tw> <18529644.999269797@[192.168.1.31]> <002c01c1323c$29b77500$2707738c@q.j.tw>
Content-Type: text/plain; charset=UTF-8
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA14543

-----BEGIN PGP SIGNED MESSAGE-----

tsenglm@cc.ncu.edu.tw wrote:
> Patrik FÃ¤ltstrÃ¶m wrote:
> > When the matching algorithm you envision encounters a character where the
> > tables do not tell what to do about it, what will the algorithm do to it?
> > Pass it through unmodified? Reject it? Does something else which you have
> > not defined yet?
>
> [pass it through unmodified]
> 
> > If you tell us this, and claim that this is acceptable treatment of the
> > 20-40.000 characters not in the tables, we can at least discuss this
> > proposal (whether such a partial TC/SC mapping is acceptable), instead of
> > asking again and again what to do about them.
>
>            As Patrik FÃ¤ltstrÃ¶m described, if it is a mechanism in
> UNICODE consortium, then they have the version update procedures and IDNA
> also treat the version update in UNICODE, why it can not be updated step
> by step to increase it?

Because that could cause existing domain names to break (i.e. fail to resolve
when processed by a new version of nameprep). This would happen when a
name contains a source character for one of the new mappings. In order to
avoid that problem, all authoritative servers with names in the affected
scripts would have to be upgraded before any resolvers or applications. That
is at least undesirable, and may be impractical.

Note that there are rules for updating nameprep and NFKC that ensure the
same problem doesn't happen for canonicalization or case mappings (roughly
speaking, no new mapping can be added from a previously assigned character;
see UAX #15 for a more precise statement of the update policy for 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

iQEVAwUBO45nhDkCAxeYt5gVAQGamwf9GrNjWTdM0MplX1wT/edxDgWcW0vQ/DgT
is52/SNWTbJlpk9/7nE1UzrLYzQoeBwPq1zNoRaB8xcup/5pH9qZGlgEzQ54gq0o
PZizCQ5leuIYtYUbqlfBb2xn599ivbnRVaicVhwsl2M7k2/tKO4WeQfm/4kCwCG4
317up0uP7x66jMD2VlvZ08+1BzPXvU+Ok9ZODvHrv7NaE9uGQwDbKGlFY+ca4iz7
pwuk6ruRTVQn6dbN82GHGzprVlw7MZwz4p2x8yDpBckJkSOomlyhAA4hhCdcisJF
llKmVRkhQH6p9y2R/jCaVOEIZVkkWdQ+hi9+EeuGMgSKkT3D+qwwTQ==
=KKv5
-----END PGP SIGNATURE-----




From owner-idn@ops.ietf.org  Fri Aug 31 17:12: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 RAA16208
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 17:12:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cvPA-0004VG-00
	for idn-data@psg.com; Fri, 31 Aug 2001 14:00:44 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cvP9-0004V9-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 14:00:44 -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 WAA16328;
	Fri, 31 Aug 2001 22:59:01 +0200 (MET DST)
Date: Fri, 31 Aug 2001 22:40:00 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: "=?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?=" <tsenglm@cc.ncu.edu.tw>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, liana.ydisg@juno.com,
        hlqian <hlqian@cnnic.net.cn>
cc: huangk@alum.sinica.edu, idn@ops.ietf.org
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <5188367.999297600@localhost>
In-Reply-To: <002c01c1323c$29b77500$2707738c@q.j.tw>
References:  <000f01c1321b$03b9d260$2707738c@q.j.tw>
 <18529644.999269797@[192.168.1.31]> <002c01c1323c$29b77500$2707738c@q.j.tw>
X-Mailer: Mulberry/2.1.0 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
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 RAA16208

--On 2001-09-01 00.44 +0800
"=?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?="
<tsenglm@cc.ncu.edu.tw> wrote:

>            As Patrik FÃ?Â¤ltstrÃ?Â¶m  described , if it is a mechanism in
> UNICODE consosium , then they have the version update procedures and IDNA
> also treat  the version update in UNICODE , why it can not be updated step
> by step  to  increse it ?

Very simple answer.

Let's assume that the table day one include the following characters:

A
B
C
D
E
F

We agree that the simple equivalence rules for 1-1 mapping maps A->B.

This means that the following characters are available for domain name
registration:

B
C
D
E
F

People register domainames such as:

B.example.com.
C.example.com.
D.example.com.
E.example.com.
F.example.com.

Five different people register these five domains, which are different.

If one type in A.example.com in the browser, nameprep will map that name to
B.example.com. So, A.example.com and B.example.com are treated as "the same
domain".

Now, let's say that we increase the size of that table, and decide that D
and E are equivalent, so D->E mapping should be added.

This means that only the following characters are allowed:

B
C
E
F

The domains D.example.com and E.example.com are equivalent.

Now the questions, and I want you to answer them. Short answers are
required:

(1) Should the holder of D.example.com or the holder of E.example.com be
forced to give back his domain?

(2) Who is making that descision?

(3) Who will tell the domain name holder that he is not allowed to have his
domain anymore?

     paf




From owner-idn@ops.ietf.org  Fri Aug 31 17:53: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 RAA16846
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 17:53:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cw4C-00054t-00
	for idn-data@psg.com; Fri, 31 Aug 2001 14:43:08 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cw4B-00054m-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 14:43:07 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+EESdhpctSHzBlUgdjhQNNyh2f8jJrdpQ==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GD7X8QRY; Fri, 31 Aug 2001 17:42:32 EDT
To: moore@cs.utk.edu
Cc: dhc@dcrocker.net, idn@ops.ietf.org
Date: Fri, 31 Aug 2001 15:00:33 -0700
Subject: Re: [idn] Working group focus -- and progress
Message-ID: <20010831.150036.-811311.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-Att: 0
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi, Keith:
From what you are suggesting, I feel that you are
listening, and I am graceful for it.       

I don't think the technical part of it is that difficult to 
understand, it is Computer Sci. 110.  It is the basics
of a simple ralational database, not a fancy one
like DB2 or even a MSACCESS, it is only a two 
dimensional Spread Sheet without computation
part of it.   

Also, I suggest that change the word "SCOPE of the WG"
 into the "current working target of the WG", at least, 
that does not irritate me as much, makes me feel 
like a fool on this list.

Liana

On Fri, 31 Aug 2001 14:22:16 -0400 Keith Moore <moore@cs.utk.edu> writes:
> > The second statement is the more important point:  It is the reason 
> that
> > this entire topic is entirely OUT OF SCOPE for this working group.
> ...
> > There is a rumor that some people actually want to use the results 
> of this
> > working group, and that they want to use the results AS SOON AS 
> POSSIBLE.
> 
> ...regardless of whether or not those results work well.
> 
> yes, I am quite sure that you are correct.
> 
> it's also clear that any DNS-compatible solution will have 
> significant 
> problems with transcription (either written to typed or audible to 
> typed)
> in some languages.
> 
> addressing this may be out of scope for this WG, but that doesn't 
> mean
> that IDNs can be made to work well without addressing it.
> 
> and yet this WG clearly lacks sufficient expertise to solve this 
> problem 
> no matter what the WG charter says.
> 
> it appears that the best this WG can do is 
> 
> 	- identify known limitations with its approach
> 
> 	- state any known workarounds for those limitations
> 
> 	- define or suggest some mechanism (if any can be found)
> 	  for the IDN resolution infrastructure to be upgraded
> 	  at a later date to better solve the transcription 
> problems.
> 
> Keith
> 



From owner-idn@ops.ietf.org  Fri Aug 31 18:07: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 SAA17010
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 18:07:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cwLX-0005Kv-00
	for idn-data@psg.com; Fri, 31 Aug 2001 15:01:03 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15cwLW-0005Kp-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 15:01:02 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+EESdhpctSHMV85zj/xuZEC5rF7islKBw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GD7Y83MR; Fri, 31 Aug 2001 18:00:11 EDT
To: paf@cisco.com
Cc: tsenglm@cc.ncu.edu.tw, harald@alvestrand.no, liana.ydisg@juno.com,
        hlqian@cnnic.net.cn, huangk@alum.sinica.edu, idn@ops.ietf.org
Date: Fri, 31 Aug 2001 15:18:14 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010831.151816.-811311.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-Line-Breaks: 0-13,15-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

Hi, Paf:

This exactly the type of question the CJK unification likes to
resolve for CJK domains.  That is the reason we argue for
not releasing [nameprep] prematurely until we know what
is the first step to be released without damage the long 
term goal of IDN. 

And that is the reason, Chinese only distribute numbers
in their domain registration. 

Liana
 

On Fri, 31 Aug 2001 22:40:00 +0200 =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?=
<paf@cisco.com> writes:
> --On 2001-09-01 00.44 +0800
> "=?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?="
> <tsenglm@cc.ncu.edu.tw> wrote:
> 
> >            As Patrik F?Â¤ltstr?Â¶m  described , if it is a 
> mechanism in
> > UNICODE consosium , then they have the version update procedures 
> and IDNA
> > also treat  the version update in UNICODE , why it can not be 
> updated step
> > by step  to  increse it ?
> 
> Very simple answer.
> 
> Let's assume that the table day one include the following 
> characters:
> 
> A
> B
> C
> D
> E
> F
> 
> We agree that the simple equivalence rules for 1-1 mapping maps 
> A->B.
> 
> This means that the following characters are available for domain 
> name
> registration:
> 
> B
> C
> D
> E
> F
> 
> People register domainames such as:
> 
> B.example.com.
> C.example.com.
> D.example.com.
> E.example.com.
> F.example.com.
> 
> Five different people register these five domains, which are 
> different.
> 
> If one type in A.example.com in the browser, nameprep will map that 
> name to
> B.example.com. So, A.example.com and B.example.com are treated as 
> "the same
> domain".
> 
> Now, let's say that we increase the size of that table, and decide 
> that D
> and E are equivalent, so D->E mapping should be added.
> 
> This means that only the following characters are allowed:
> 
> B
> C
> E
> F
> 
> The domains D.example.com and E.example.com are equivalent.
> 
> Now the questions, and I want you to answer them. Short answers are
> required:
> 
> (1) Should the holder of D.example.com or the holder of 
> E.example.com be
> forced to give back his domain?
> 
> (2) Who is making that descision?
> 
> (3) Who will tell the domain name holder that he is not allowed to 
> have his
> domain anymore?
> 
>      paf
> 



From owner-idn@ops.ietf.org  Fri Aug 31 19:37: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 TAA17686
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 19:37:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15cxiT-0006il-00
	for idn-data@psg.com; Fri, 31 Aug 2001 16:28:49 -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 15cxiS-0006if-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 16:28:48 -0700
Received: from zetnet.co.uk (man-s361.dialup.zetnet.co.uk [194.247.45.232])
        by zetnet.co.uk (8.11.3/8.11.3/Debian 8.11.2-1) with ESMTP id f7VNSib30371
        for <idn@ops.ietf.org>; Sat, 1 Sep 2001 00:28:45 +0100
Message-ID: <3B8EA6E9.5BF01724@zetnet.co.uk>
Date: Thu, 30 Aug 2001 21:49:45 +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] opting out of SC/TC equivalence
References: <000f01c1321b$03b9d260$2707738c@q.j.tw> <18529644.999269797@[192.168.1.31]> <002c01c1323c$29b77500$2707738c@q.j.tw> <3B8E67BC.5F9B8D9B@zetnet.co.uk>
Content-Type: text/plain; charset=UTF-8
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA17686

-----BEGIN PGP SIGNED MESSAGE-----

I wrote:
> tsenglm@cc.ncu.edu.tw wrote:
> > Patrik FÃ¤ltstrÃ¶m wrote:
> > > When the matching algorithm you envision encounters a character where the
> > > tables do not tell what to do about it, what will the algorithm do to it?
> > > Pass it through unmodified? Reject it? Does something else which you have
> > > not defined yet?
> >
> > [pass it through unmodified]
> >
> > > If you tell us this, and claim that this is acceptable treatment of the
> > > 20-40.000 characters not in the tables, we can at least discuss this
> > > proposal (whether such a partial TC/SC mapping is acceptable), instead of
> > > asking again and again what to do about them.
> >
> >            As Patrik FÃ¤ltstrÃ¶m described, if it is a mechanism in
> > UNICODE consortium, then they have the version update procedures and IDNA
> > also treat the version update in UNICODE, why it can not be updated step
> > by step to increase it?
> 
> Because that could cause existing domain names to break (i.e. fail to resolve
> when processed by a new version of nameprep). This would happen when a
> name contains a source character for one of the new mappings. In order to
> avoid that problem, all authoritative servers with names in the affected
> scripts would have to be upgraded before any resolvers or applications.

In fact it's worse than that, as Patrick FÃ¤ltstrÃ¶m pointed out: the source
and destination names may already be owned by different people/organizations.
So adding new mappings for already-assigned Unicode characters must be
prohibited.

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

iQEVAwUBO46mtzkCAxeYt5gVAQExGQf9GPIns+whxvrl9pkERCvDwWKPH08rNXnB
4+5+So7/o0yPj1ownIJhDNlSc0o6TguBIEOvbDGZbnfivZZwc6KPpa9tSYmClLFS
AgXlORj26FT26ALfPRE+xbPNbEltwp5BM1fscE9RouoKZiunQ32MX4rq64g7R1xL
+IRaBjS8YCX/Ojrk0JbccH96syaFIlIFsH78fbLZ8Wrm6AailOpkW4/tYqoxvtNh
WsRHPH3Gw7YlPCL39RboVUk+ULGca8yq5eCAFlk4g3nXj88OblACQY8dhgtdFPYj
LN9jsCsIcgbn6qgx8rD4u0hypK9qzET+yt8x7f/JVLPU1rfxGqTWaw==
=rh4B
-----END PGP SIGNATURE-----



From owner-idn@ops.ietf.org  Fri Aug 31 21:54: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 VAA19984
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 21:54:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15czdQ-0008Lv-00
	for idn-data@psg.com; Fri, 31 Aug 2001 18:31:44 -0700
Received: from bora.postel.to ([164.124.123.206] helo=bora.lsb.org)
	by psg.com with esmtp (Exim 3.33 #1)
	id 15czdP-0008Ll-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 18:31:43 -0700
Received: from marketing ([210.217.27.236] (may be forged))
	by bora.lsb.org (8.9.3/8.8.7) with SMTP id KAA18080;
	Sat, 1 Sep 2001 10:30:59 +0900
Message-ID: <01d601c13286$07ac3fa0$ec1bd9d2@temp>
From: "Soobok Lee" <lsb@postel.co.kr>
To: "Keith Moore" <moore@cs.utk.edu>, "Dave Crocker" <dhc@dcrocker.net>
Cc: <idn@ops.ietf.org>
References: <200108311822.OAA01423@astro.cs.utk.edu>
Subject: Re: [idn] Working group focus -- and progress 
Date: Sat, 1 Sep 2001 10:32:57 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


----- Original Message ----- 
From: "Keith Moore" <moore@cs.utk.edu>
To: "Dave Crocker" <dhc@dcrocker.net>
Cc: <idn@ops.ietf.org>
Sent: Saturday, September 01, 2001 3:22 AM
Subject: Re: [idn] Working group focus -- and progress 


> > The second statement is the more important point:  It is the reason that
> > this entire topic is entirely OUT OF SCOPE for this working group.
> ...
> > There is a rumor that some people actually want to use the results of this
> > working group, and that they want to use the results AS SOON AS POSSIBLE.
> 
> ...regardless of whether or not those results work well.
> 
> yes, I am quite sure that you are correct.


> 
> it's also clear that any DNS-compatible solution will have significant 
> problems with transcription (either written to typed or audible to typed)
> in some languages.
> 
> addressing this may be out of scope for this WG, but that doesn't mean
> that IDNs can be made to work well without addressing it.
> 
> and yet this WG clearly lacks sufficient expertise to solve this problem 
> no matter what the WG charter says.

I agree. Moreover,  even if we have the expertise,
most problems cannot be solved by mechanical processing 
like nameprep which is designed to be a "utility" for
input convenience and matching of IDN labels, 
_NOT_ to be the complete solution to ambiguities 
introduced by i18n characters from various scripts.

> 
> it appears that the best this WG can do is 
> 
> - identify known limitations with its approach
> 
> - state any known workarounds for those limitations
> 
> - define or suggest some mechanism (if any can be found)
>   for the IDN resolution infrastructure to be upgraded
>   at a later date to better solve the transcription problems.
> 

I agree. I am preparing the first  (maybe incomplete) BCP for IDN. 
I hope someone would make GPLed zone checking tools
based on that.. :-)

soobok

> Keith
> 




From owner-idn@ops.ietf.org  Fri Aug 31 23:27: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 XAA22897
	for <idn-archive@lists.ietf.org>; Fri, 31 Aug 2001 23:27:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.33 #1)
	id 15d1JC-0009gQ-00
	for idn-data@psg.com; Fri, 31 Aug 2001 20:18:58 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.33 #1)
	id 15d1JB-0009gK-00
	for idn@ops.ietf.org; Fri, 31 Aug 2001 20:18:57 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH+EESdhpctSHmmyT9YoHh8NlqlFmrwGqLQ==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id GD8KEX3X; Fri, 31 Aug 2001 23:17:59 EDT
To: tsenglm@cc.ncu.edu.tw
Cc: James@Seng.cc, liana.ydisg@juno.com, idn@ops.ietf.org
Date: Fri, 31 Aug 2001 20:36:02 -0700
Subject: Re: [idn] opting out of SC/TC equivalence
Message-ID: <20010831.203607.-737135.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-60,63-177
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, Prof. Tseng:

The first step of our solution is to open [nameprep] 
to let local standards in for easy code exchange.  This
is an equal access issue.  The best place to demonstrate
such a feature is the "cut and paste" of an IDN URL 
e-mail entry.  It shall be a universal treatment at the end.

The second step is to define the ranges of different
user groups who need their primary script tag.  No 
mix scripts is allowed at this stage.  But we can take 
wish list.  For example, English may wish to include
Greek, Korean may want Hanja on its wish list. 
 That way, we can identify conflicts of codepoints and 
possible confusion of codepoints, and start with a 
careful first step.  A survey on the existing registered 
names for possible conflict when Unicode is 
used for limited scripts is helpful to start a clean first
deployment of [nameprep].  

Someone wants to lunch an unmature version of
 [nameprep] are very smart.  They probally have put 
a lot of money behind this working group already , where 
we are just a decoration voices to lead people believing
 that this is an open discussion, democratic process.
 Meanwhile, when we started to speak out, they are pressing
the group to rush out a premature version,  so that they 
can get ahead of [nameprep] and make the future upgrade 
very hard for others, so CJK at a great disadvantage on 
this.  The Chinese domains using numbers for their names
at this time for globle consideration would be trashed.

My feeling on this, there are more politics and money 
then technical issues hidden behind us.  I am not an
expert on any of this, even I can point out feasible solutions,
why they can not see it.  Why the "Scope of this  WG" is
so tight on them is beyong me.  As a user, we have been 
waiting for years, why suddenly, a few months of extension 
making so many people nervous?  Even Microsoft has 
sliping their published product delievery dates as long as 
6 months, why such a multitude complexing issue has 
to be pushed to a rushing date?????????????

So your first step TC/SC simple mapping in [nameprep]
which should be on the same footing with Latin case
folding being pushed away by all kind of nonsense 
argurments.  I think we are too naive.  We are better to be 
prepared to leave this discussion and bring the whole
 thing onto the news media, and let the public to be the 
judge. 

Liana






The third step is to let safe range go online for ML.com.


On Fri, 31 Aug 2001 18:08:13 +0800
=?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?=
<tsenglm@cc.ncu.edu.tw> writes:
> Hi !  Liana:
>         I have the same feeling . We try  to solve these SC/TC 
> problem step
> by step and  to reduce the complexity.  As John had pointed-out in 
> this
> listing , sometimes many scripts-only term  will be expand to 
> lanaguage-term
> and let some one to neglect the key-point.  1-1 mapping will reduce 
> the
> complexity like mixing case of alphabet that will reduce the number 
> of
> non-necessary registration and confusing of using.
>         No one try to translate TC/SC in DNS. Even an expert of 
> chinese
> language also can not resolve  the different local naming  and habit 
> of
> personal name in different Province of China.  The PRC-SC is the 
> frequently
> used characters in chinese language, some of them can be 
> differentiated by
> different shape, but a little of them is easy-to-confuse ,  such as 
> TC(é ?
> SC(é¢?  SC (ç»?  TC (çµ?. James seems avoid to answer what is the 
> first step
> to solution.
>         If the easy-to-confuse characters can be reduced . Even a 
> little ,
> that is better than nothing to do.  Reducing the number of 
> easy-to-confuse
> characters in nameprep is a better help to CJK users.
>         Always to point out the complexity of chinese language and 
> never to
> solve some problem step by step is not a coorect approach in 
> engineering.
> 
> L.M.Tseng
> ----- Original Message -----
> From: <liana.ydisg@juno.com>
> To: <James@Seng.cc>
> Cc: <idn@ops.ietf.org>
> Sent: Friday, August 31, 2001 4:02 PM
> Subject: Re: [idn] opting out of SC/TC equivalence
> 
> 
> > Hi, James,
> >
> >   That was a miscommunication on my part, that I did not
> > amend, since I did not see anyone care about except
> > Martin, which I have answered indirectly.  This is
> > realy two issues. One is one-to-one TC/SC mapping
> > in [nameprep]. With this part, we shall include GB, Big5,
> > and a few other standards representing local access
> > directly to [nameprep] and speeding up hostname
> > translation.  This is my 20% effort for 80% TC/SC cases
> > arguing for. [nameprep] shall only do one-to-one
> > mapping, no guessing or second try shall be there at
> > all.
> >
> > Another issue is direct mapping to StepCode part of
> > the proposal which is mixed up in that short
> > communication.  StepCode has Pinyin for each radical
> > already for SC character set.   More work is needed
> > to check against with larger character set such as Big5
> > and Unicode.   I thought if some published listing may
> > help out for Kanji and Hanja to encode,  just an idea to
> > throw out to be criticized, it does not mean to play with
> > TC/SC AI treatment in [nameprep].   After that, I was a
> > little regret, since  if the current architecture of [nameprep]
> > does not change,  I am putting up more work for nothing.
> >
> > Liana
> >
> > On Fri, 31 Aug 2001 12:50:45 +0800 "James Seng/Personal" 
> <James@Seng.cc>
> > writes:
> > > Iiana,
> > >
> > > I am not comment on other parts but your presumation that TC/SC 
> can
> > > be
> > > done by radical equivalence simplification is unfortunately
> > > misplaced.
> > > No doubts there are *some* cases whereby TC->SC can be done by
> > > changing
> > > radicals, it is not rule of the thumb.
> > >
> > > Once again, you may want to read the problems with TC-SC paper by
> > > Jack
> > > Halpern at http://www.basistech.com/articles/C2C.html first on 
> basic
> > > difficulties of TC/SC in general.
> > > http://playground.i-dns.net/one/onec_sum.htm (also by Jack)
> > > describes
> > > the more specific difficulties of doing TC-SC in Domain Names.
> > >
> > > -James Seng
> > >
> > > > As to TC/SC, I think the problem can be divided into two
> > > > levels. One level is the mechanical, one-to-one.  They are
> > > > the majority and bothering  the readers.  The minority as many
> > > > have said those n-to-1problem, normally one of them is
> > > > the major one, and the other are minor ones.  There are
> > > > always exceptions!!!  So to benefit the majority, the way to 
> deal
> > > > with it is to come up with an arbitary one-to-one, and let 
> Chinese
> > > > to fight which one is the major one!   The same principle is
> > > > applied to decomposition of a Hanja and Kanji.  When there
> > > > is a base, the rest will follow , the application will have
> > > > something to conform to.
> > >
> > >
> >
> 



