Re: [idn] Report from the ACE design team

["Soobok Lee" <lsb@postel.co.kr>]

In IDNA, all domain labels are NAMEPREPed and then ACEed.

If any one would ever look into the  NAMEPREP implementations,
he/she could not understand why we adhere to  simple ACEs.

NAMEPREP already has HUGE unicode mapping tables and 
long lists of prohibited characters. It has  KC normalization 
code in it. Thousands lines of code for all.

Moreover, NAMEPREP and ACE may be coded into 
a single IDNA library by application vendors.
Choosing the simplest ACE (and saving  only one hundred 
lines of code)  does not greatly simplify  IDNA implementations and 
so lose its justification 
as long as we have still complex NAMEPREP process paired with ACE.

Soobok Lee, lsb@postel.co.kr


----- Original Message ----- 
From: "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>
To: "Kenneth Whistler" <kenw@sybase.com>
Cc: <idn@ops.ietf.org>
Sent: Wednesday, June 27, 2001 11:20 PM
Subject: Re: [idn] Report from the ACE design team


> At/?20:18 2001-06-26 -0700, Kenneth Whistler you wrote/vous ?riviez:
> >Soobok Lee wrote:
> >
> > > I believe long natural sentence/phrase domains escape your arguments.
> > >
> > > In CJK, "What is the nearest macdonald hamberger shop from 
> > here?".(kr|cn|jp|tw)
> >
> >??
> >
> >Why would someone want to type in:
> >
> >"konomawariniwaichibanchikaimakudonarudohambaaganomisewadokodeshooka.co.jp"
> 
> 
> Sorry Ken, but your argument of long-names-will-not-be-used does not stand. 
> In the .com zone file, there is _already_ some labels which are 63 
> characters long.  So even in english, there is a use (that one can 
> question, but...) of all space available.  The idn tax that give us ~ 20 
> chars max for some scripts is already a big tax compared to what is 
> available and _used_ in all ascii labels.  To me, the best compression we 
> can get is the best, (without necessarily forgetting the complexity).
> 
> Marc.
> 
> 
> 
> 
> >when they could go to
> >
> >mcdonalds.co.jp
> >
> >click on the "zenkoku no mise listo" (List of all stores in the country)
> >button on the home page and get the same results?
> >
> >If people wanted to do creative PR marketing, they could create
> >
> >my-makudonarudo.co.jp  (with "makudonarudo" in Katakana, if you like)
> >
> >and have the custom site *remember* where you live and which restaurant
> >you like to go to nearby.
> >
> >Maybe movie names or band names, and stuff like that -- sure. Marketers
> >love that stuff.
> >
> > > domain
> > > may  raise interests and easier to remember and that was not possible
> > > with LDH domains  for CJK peoples.
> >
> >Yes, but use of excessively long natural phrase domains like this is just
> >misuse of what domain names should be for, in my opinion, and will be
> >quickly outcompeted by more effective ways to get people to visit your
> >sites and get the information or whatever else they are looking for.
> >
> >--Ken
> >
> > >
> > > .kr .cn .jp domain suffices may be omitted in future localized web 
> > browsers, and
> > > it will make japanese and chinese sentence domains good for PR marketing.
> > >
> > > I think it is safe for us to leave much rooms for these creative naming
> > > conventions
> > > in our ACE proposals for the future.
> 
> 
>