From owner-idn@ops.ietf.org  Tue May  1 09:17:12 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA25976
	for <idn-archive@lists.ietf.org>; Tue, 1 May 2001 09:17:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14uZeH-0007HR-00
	for idn-data@psg.com; Tue, 01 May 2001 05:53:01 -0700
Received: from blake.i-email.net ([203.126.116.232])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14uZeG-0007H9-00
	for idn@ops.ietf.org; Tue, 01 May 2001 05:53:00 -0700
Received: from maynardibm (mcns7.docsis186.singa.pore.net [202.156.186.7])
	by blake.i-email.net (Postfix) with SMTP
	id BB5B4A890A; Tue,  1 May 2001 20:52:56 +0800 (SGT)
Message-ID: <006101c0d23d$a1d47fb0$0200000a@maynardibm>
From: "Maynard Kang" <maynard@pobox.org.sg>
To: "James Seng/Personal" <jseng@pobox.org.sg>,
        "Tan Tin Wee" <tinwee@bic.nus.edu.sg>
Cc: <idn@ops.ietf.org>
References: <3AEE3769.7DA077F@bic.nus.edu.sg> <005401c0d1ff$2323ac60$0201000a@jamessonyvaio>
Subject: Re: Re: [idn] Zone rules (was: wg milestones update)]
Date: Tue, 1 May 2001 20:52:02 +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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

> Yes, there are TC which maps to two or more SC :-) There are ~4 of them
> on a single character basic. More if you look into 2-3 character words.
>
> -James Seng

Yes, that is true. But I think that is not what Tin Wee is trying to point
out.

One TC character does not map to a two or more SC character "phrase" (the
keyword being "phrase", as used by John in his previous mail), which is the
error in John's understanding that Tin Wee was trying to point out.

TC-SC equivalence would best be described as "many cases of 1-1 mappings
for the same source TC character" and not "1-n mappings" which is gives the
false impression of a possible decomposition process where one character
becomes two (e.g. one character "a with umlaut" -> two characters "a" +
"umlaut")

Although one Chinese character may map to a two or more Chinese character
phrase, that is not strictly a TC-SC equivalence rule, but rather just a
relationship between synonyms (e.g. "å½•" = "é�’"). The semantic meaning may be
equivalent, but the pronunciation and number of syllables would be
different (e.g. in English, "car" = "automobile").

This is in contrast to Japanese, where one abstract character in Kanji may
map to a two or more abstract characters in Katakana, and yet still bear
exactly the same semantic meaning, pronunciation, and number of syllables.
But I am no Japanese expert so please correct me if I am wrong here.

maynard




From owner-idn@ops.ietf.org  Tue May  1 09:46:14 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA27071
	for <idn-archive@lists.ietf.org>; Tue, 1 May 2001 09:46:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14ua1i-0008N9-00
	for idn-data@psg.com; Tue, 01 May 2001 06:17:14 -0700
Received: from ns.jck.com ([209.187.148.211] helo=A4.JCK.COM)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14ua1h-0008N2-00
	for idn@ops.ietf.org; Tue, 01 May 2001 06:17:13 -0700
Received: from P2 ("port 2790"@[209.187.148.217])
 by a4.jck.com (PMDF V6.0-24 #44844) with ESMTP id <0GCN00A95RKNWQ@a4.jck.com>
 for idn@ops.ietf.org; Tue, 01 May 2001 09:17:12 -0400 (EDT)
Date: Tue, 01 May 2001 09:17:11 -0400
From: John C Klensin <klensin@jck.com>
Subject: Re: Re: [idn] Zone rules (was: wg milestones update)]
In-reply-to: <006101c0d23d$a1d47fb0$0200000a@maynardibm>
To: Maynard Kang <maynard@pobox.org.sg>
Cc: James Seng/Personal <jseng@pobox.org.sg>,
        Tan Tin Wee <tinwee@bic.nus.edu.sg>, idn@ops.ietf.org
Message-id: <866152980.988708631@P2>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.8 (Win32)
Content-type: text/plain; charset=iso-8859-1
Content-disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA27071

Maynard (and James and Tin Wee),

I think I understood this.  But many thanks for the
clarifications and my apologies for my less-than-precise
language.

   john


--On Tuesday, 01 May, 2001 20:52 +0800 Maynard Kang
<maynard@pobox.org.sg> wrote:

> Yes, that is true. But I think that is not what Tin Wee is
> trying to point out.
> > One TC character does not map to a two or more SC character
> "phrase" (the keyword being "phrase", as used by John in his
> previous mail), which is the error in John's understanding
> that Tin Wee was trying to point out.
> > TC-SC equivalence would best be described as "many cases of
> 1-1 mappings for the same source TC character" and not "1-n
> mappings" which is gives the false impression of a possible
> decomposition process where one character becomes two (e.g.
> one character "a with umlaut" -> two characters "a" + "umlaut")
> > Although one Chinese character may map to a two or more
> Chinese character phrase, that is not strictly a TC-SC
> equivalence rule, but rather just a relationship between
> synonyms (e.g. "å½?" = "é??"). The semantic meaning may be
> equivalent, but the pronunciation and number of syllables
> would be different (e.g. in English, "car" = "automobile").




From owner-idn@ops.ietf.org  Tue May  1 12:12:13 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA02523
	for <idn-archive@lists.ietf.org>; Tue, 1 May 2001 12:12:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14ucQp-000FTM-00
	for idn-data@psg.com; Tue, 01 May 2001 08:51:19 -0700
Received: from ns.jck.com ([209.187.148.211] helo=A4.JCK.COM)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14ucQo-000FTF-00
	for idn@ops.ietf.org; Tue, 01 May 2001 08:51:18 -0700
Received: from P2 ("port 2885"@[209.187.148.217])
 by a4.jck.com (PMDF V6.0-24 #44844) with ESMTP id <0GCN00AF9YPHWQ@a4.jck.com>
 for idn@ops.ietf.org; Tue, 01 May 2001 11:51:17 -0400 (EDT)
Date: Tue, 01 May 2001 11:51:16 -0400
From: John C Klensin <klensin@jck.com>
Subject: [idn] requirements-05
To: idn@ops.ietf.org
Message-id: <875398750.988717876@P2>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.8 (Win32)
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

Marc, James, and Zita,

I have just finished giving requirements-05 a careful read.  I
suggest that it is not yet ready for the IESG, either
substantively or editorially, although we are arguably getting
close.  Contrary to normal practice, I'm including editorial
comments at the bottom of this note, partially to suggest that
few people have read it carefully.

A few of these issues have already been spotted by others and
I want to reinforce them and give the editors a more
consolidated list.  Apologies if I have missed anything already
noted by others.

    --john

------------

1. Substantive.

(i) Section 1, end of first paragraph.  I believe that it
would be useful if the document made the "assumption" a bit
more explicit by pointing out that there may not be consensus
in the IETF community on that assumption and that several
sections of the document, including the "definitions and
conventions" are likely to be useful even if the assumption is
false.

(ii) Section 1.5, third bullet: "ip6.int" should be
"ip6.arpa". 

(iii) Section 2.1, requirement [1], last sentence.  This
statement appears to me to be inherently false.  Since
internationalized domain names cannot be resolved (within
existing protocols) today, it is an impossibility to require
that any system that exists today must be able to continue
resolving such names.

(iv) Section 2.2, requirement [14].  It is not clear to me
what this requirement means.  I believe that some of nameprep
is intended precisely to reject some characters.  And the
recent "testbed" introduction of registrations of dingbats and
other symbols as domain names may call for further
consideration of some of the related issues.  The requirement
at least needs clarification.

(v) Requirements [22] and [30] appear to me to be inconsistent
and contradictory.  Case folding is ultimately just an
equivalence rule.  [22] says that the equivalence rule must be
the same globally.   [30] says that equivalence rules may
differ by zone.  I don't think one can have it both ways.  Or,
if I misunderstand what is intended, the text is badly in need
of clarification.

2. Editorial

(i) Section 1.1, second paragraph.  "trough" should presumably
be "through"

(ii) Section 1.2, third paragraph, last sentence.  The comma
after "contexts" probably belongs after "document" or should
be deleted or the sentence rewritten.

(iii) Section 1.4, second bullet.  There is a missing right
paranthesis matching the one before "listed".   And the final
sentence should probably contain "what is being transferred",
not "what are".

(iv) Section 1.5, fourth bullet.  "who provides" should be
"who provide" (hosts is plural) and I think "who" should be
"which" unless those hosts are human.

(v) Section 2.4.  There is no section 2.3, so this should
probably be renumbered.

(vi) There is certainly precedent for leaving this for the RFC
Editor, but the references are not consistent about the
ordering of author, title, rfc reference (where appropriate),
and date.





From owner-idn@ops.ietf.org  Tue May  1 18:05:12 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA11256
	for <idn-archive@lists.ietf.org>; Tue, 1 May 2001 18:05:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14uhwn-0005TQ-00
	for idn-data@psg.com; Tue, 01 May 2001 14:44:41 -0700
Received: from inergen.sybase.com ([192.138.151.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14uhwm-0005Rk-00
	for idn@ops.ietf.org; Tue, 01 May 2001 14:44:40 -0700
Received: from smtp2.sybase.com (sybgate2.sybase.com [130.214.88.21])
	by inergen.sybase.com  with ESMTP id OAA07200
	for <idn@ops.ietf.org>; Tue, 1 May 2001 14:44:08 -0700 (PDT)
Received: from olympus.sybase.com (olympus [130.214.160.74])
	by smtp2.sybase.com  with ESMTP id OAA19682
	for <idn@ops.ietf.org>; Tue, 1 May 2001 14:44:08 -0700 (PDT)
Received: from birdie.sybase.com by olympus.sybase.com (8.8.8+Sun/SMI-SVR4/SybEC3.5)
	id OAA00746; Tue, 1 May 2001 14:44:02 -0700 (PDT)
Received: (from kenw@localhost)
	by birdie.sybase.com (8.8.8+Sun/8.8.8) id OAA10940;
	Tue, 1 May 2001 14:44:02 -0700 (PDT)
Date: Tue, 1 May 2001 14:44:02 -0700 (PDT)
From: Kenneth Whistler <kenw@sybase.com>
Message-Id: <200105012144.OAA10940@birdie.sybase.com>
To: idn@ops.ietf.org
Subject: Re: traditional/simplified (Re: [idn] wg milestones update)
Cc: kenw@sybase.com
X-Sun-Charset: US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Harald Alvestrand responded to Sun Guonian:

> >==============================
> >I think the traditional/simplified Chinese equivalence SHOULD be defined
> >as a single rule anywhere so that we can make user use IDN, or chinese
> >part in IDN, without confusion.
> 
> If it was possible to write down this equivalence rule on a single sheet of 
> paper (without the codepoints), I would agree.
> Unfortunately not even the definitions of the different classes of 
> traditional/simplified Chinese equivalence seems to fit on a single sheet 
> of paper (the 1-n, n-1 and contextual mappings in particular).
> 
> A complex specification is prone to implementation errors, especially when 
> there are large markets (US, Western Europe) where a sloppy implementation 
> will not be challenged by real-life usage of the functionality.

With respect to the issue of whether it makes sense to have a bunch of
localized equivalence behavior in different zones, I have to agree that
what we need are globally determined equivalence rules. Anything else
invites chaotic mismatches.

With respect to the issue of whether traditional/simplified Chinese equivalence
should be included in the specification for idn matching, I quote an
exchange on traditional/simplified conversion that just occurred on
the unicode discussion list. (See below.)

The main point here is that a traditional/simplified Chinese converter
is a full-blown commercial application, which in this case comes with a set
of dictionaries with nearly 170,000 entries in them. This is not the
sort of thing that can be written down as a single-page algorithm
to be included in nameprep. As Harald suggests, it just invites
implementation errors to demand this level of complexity in matching.

Incidentally, for those who cannot directly envision the issues for
trying to match traditional and simplified Chinese domain names, a
roughly comparable problem would be trying to match "traditional"
British English spellings and lexical conventions with "simplified"
American English spellings and lexical conventions, so that, for
example:

    www.theatre.com  and  www.theater.com

would resolve to the same domain name, to avoid "confusions" among
users who might be using the "traditional" forms or the "simplified"
forms of the "same" name. But of course no such matching is attempted
now for English-based domain names, let alone all Latin-character-based
domain names -- and in fact "theatre.com" and "theater.com" are two
completely distinct existing domains that are, unfortunately or
fortunately (depending on which side of the divide you are on),
easy to confuse. A little digging could turn up dozens or hundreds
more such pairs of domains that have the "same" name already.

--Ken 

> To: "'Michal Gerling'" <michal.gerling@exlibris.co.il>
> Cc: "'John H. Jenkins'" <jenkins@apple.com>,
>         "Magda Danish (Unicode)"
> 	 <v-magdad@microsoft.com>,
>         unicode@unicode.org
> Subject: RE: FW: chinese conversion tables
> Date: Tue, 1 May 2001 16:01:30 -0400 
> Sender: unicode-bounce@unicode.org
> X-original-sender: Ted@basistech.com
> 
> Hi Michal,
> 
> Our company produces a product that addresses your problem, including all
> the issues mentioned by John Jenkins below. We call it our
> Chinese-to-Chinese Script Converter, or C2C for short.
> 
> In particular it does not only code-point conversion but also orthographic
> and lexemic conversions, based on a set of cross-idiom dictionaries and word
> identification in streams of Chinese text. It is fully Unicode based
> internally, although conversion to and from other character sets is also
> supported.
> 
> You can read more about it at
> http://www.basistech.com/products/Chinese-Converter.html, or contact me
> directly for more information.
> 
> ==============================
> Ted Peck
> Director of Product Management
> 
> Basis Technology Corp.
> One Kendall Square
> Cambridge, MA 02139
> 
> tel: 617-386-7158
> fax: 617-386-2021
> tpeck@basistech.com
> 
> -----Original Message-----
> From: John H. Jenkins [mailto:jenkins@apple.com]
> Sent: Tuesday, May 01, 2001 2:54 PM
> To: Magda Danish (Unicode); unicode@unicode.org
> Subject: Re: FW: chinese conversion tables
> 
> 
> At 11:21 AM -0700 5/1/01, Magda Danish (Unicode) wrote:
> >-----Original Message-----
> >From: Michal Gerling [mailto:michal.gerling@exlibris.co.il]
> >Sent: Tuesday, May 01, 2001 7:24 AM
> >To: 'info@unicode.org'
> >Subject: chinese conversion tables
> >
> >
> >I am working with UNICODE and the CJK market and need to know: Is there
> >any one table or formula for moving from simplified to traditional
> >characters and back in UNICODE? thank you very much for your help!
> >Michelle g.
> 
> Partial data to interconvert between simplified and traditional 
> characters is available through the Unihan database.  However, the 
> problem is not a simple one, as there are frequently multiple 
> traditional forms that correspond to a single simplified form. 
> Moreover, the vocabulary used in the PRC with simplified characters 
> differs on occasion from the vocabulary used in Taiwan and elsewhere 
> for traditional ones (e.g., the names of the chemical elements, until 
> recently the word for "computer").  It really isn't possible to 
> convert between simplified and traditional characters without doing a 
> lexical analysis.
> 
> -- 
> =====
> John H. Jenkins
> jenkins@apple.com
> jenkins@mac.com
> http://homepage.mac.com/jenkins/



From owner-idn@ops.ietf.org  Tue May  1 20:35:35 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA13051
	for <idn-archive@lists.ietf.org>; Tue, 1 May 2001 20:35:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14ukSu-000Ch9-00
	for idn-data@psg.com; Tue, 01 May 2001 17:26:00 -0700
Received: from ns1.neteka.com ([205.150.182.130] helo=neteka.com)
	by psg.com with smtp (Exim 3.16 #1)
	id 14ukSt-000Ch3-00
	for idn@ops.ietf.org; Tue, 01 May 2001 17:25:59 -0700
Message-ID: <003401c0d29e$d8d86560$1001a8c0@vaioedmon>
From: "Edmon" <edmon@neteka.com>
To: "Kenneth Whistler" <kenw@sybase.com>, <idn@ops.ietf.org>
Cc: <kenw@sybase.com>
References: <200105012144.OAA10940@birdie.sybase.com>
Subject: Re: traditional/simplified (Re: [idn] wg milestones update)
Date: Tue, 1 May 2001 20:28:36 -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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Incidentally, for those who cannot directly envision the issues for
> trying to match traditional and simplified Chinese domain names, a
> roughly comparable problem would be trying to match "traditional"
> British English spellings and lexical conventions with "simplified"
> American English spellings and lexical conventions, so that, for
> example:
>
>     www.theatre.com  and  www.theater.com
>
> would resolve to the same domain name, to avoid "confusions" among
> users who might be using the "traditional" forms or the "simplified"
> forms of the "same" name. But of course no such matching is attempted
> now for English-based domain names, let alone all Latin-character-based
> domain names

I totally agree with this analogy as I have pointed it out a long time ago
at the Pittsburg IETF. (with a different word: colour vs color)
It is still best left to the policy makers of a registry (or domain admin of
any domain for that matter) to determine trad-simp mapping.

Edmon




From owner-idn@ops.ietf.org  Tue May  1 20:38:58 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA13075
	for <idn-archive@lists.ietf.org>; Tue, 1 May 2001 20:38:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14ukOn-000CXA-00
	for idn-data@psg.com; Tue, 01 May 2001 17:21:45 -0700
Received: from ns1.neteka.com ([205.150.182.130] helo=neteka.com)
	by psg.com with smtp (Exim 3.16 #1)
	id 14ukOm-000CX4-00
	for idn@ops.ietf.org; Tue, 01 May 2001 17:21:44 -0700
Message-ID: <002e01c0d29e$1a80faa0$1001a8c0@vaioedmon>
From: "Edmon" <edmon@neteka.com>
To: "Russ Rolfe" <rrolfe@exchange.microsoft.com>,
        "Dave Crocker" <dhc@dcrocker.net>
Cc: <idn@ops.ietf.org>
References: <5.1.0.14.2.20010430101932.038a4fb0@dcrocker.net>
Subject: [idn] Alternative Solutions
Date: Tue, 1 May 2001 20:23: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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> At 09:26 AM 4/30/2001, Russ Rolfe wrote:
> >Instead of waiting for Walid, should we be looking at what other
> >alternatives exists.  Do people have any thoughts on what the possible
> >two-three major alternatives may be.
>
> and I entirely concur with pursuing alternatives immediately.
>

There are a number of alternatives, but I see two main streams:

Server-side ACE - ACE transformation takes place at server end
Protocol Extension - use extension mechanisms such as EDNS or other bit
flagging & use UTF

Edmon





From owner-idn@ops.ietf.org  Tue May  1 21:12:55 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA13534
	for <idn-archive@lists.ietf.org>; Tue, 1 May 2001 21:12:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14ukw7-000EFv-00
	for idn-data@psg.com; Tue, 01 May 2001 17:56:11 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14ukw6-000EFe-00
	for idn@ops.ietf.org; Tue, 01 May 2001 17:56:10 -0700
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id RAA25985;
	Tue, 1 May 2001 17:56:05 -0700
Message-Id: <5.1.0.14.2.20010501174039.00b44740@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 01 May 2001 17:43:53 -0700
To: "Edmon" <edmon@neteka.com>
From: Dave Crocker <dhc@dcrocker.net>
Subject: [idn] Re: Alternative Solutions
Cc: <idn@ops.ietf.org>
In-Reply-To: <002e01c0d29e$1a80faa0$1001a8c0@vaioedmon>
References: <5.1.0.14.2.20010430101932.038a4fb0@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 05:23 PM 5/1/2001, Edmon wrote:
>Server-side ACE - ACE transformation takes place at server end

If the transformation is done at the server, then the data travel from the 
client as binary.  How is that different from your second alternative?

For that matter, why bother with an ACE transformation at that point?

Please clarify.


>Protocol Extension - use extension mechanisms such as EDNS or other bit
>flagging & use UTF

This is a class, "dual-stack" operation.  One stack is the original system 
and the second is the new.

(By way of raising a warning flag early, one danger with this approach is 
what we have seen with IPv6.  Namely, people will try to add zillions of 
changes and features, thereby delaying the effort by years.)

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 May  1 21:28:24 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA13677
	for <idn-archive@lists.ietf.org>; Tue, 1 May 2001 21:28:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14ulGQ-000F58-00
	for idn-data@psg.com; Tue, 01 May 2001 18:17:10 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14ulGP-000F4t-00
	for idn@ops.ietf.org; Tue, 01 May 2001 18:17:09 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 14ulGO-0002BL-00; Tue, 01 May 2001 18:17:08 -0700
Date: Wed, 2 May 2001 01:17:08 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Alternative Solutions
Message-ID: <20010502011708.C6619@arwen.cs.berkeley.edu>
References: <5.1.0.14.2.20010430101932.038a4fb0@dcrocker.net> <002e01c0d29e$1a80faa0$1001a8c0@vaioedmon>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <002e01c0d29e$1a80faa0$1001a8c0@vaioedmon>; from edmon@neteka.com on Tue, May 01, 2001 at 08:23:15PM -0400
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Edmon <edmon@neteka.com> wrote:

> Server-side ACE - ACE transformation takes place at server end

If it's on the server, it doesn't have to be an algorithmic
transformation; it can just be a distributed lookup table (which is what
DNS is anyway).

Two new resource record types could be created, one that gives the
Unicode domain name associated with an LDH (letter/digit/hyphen) name,
and one that gives the LDH name associated with a Unicode name.  This
is analogous to the A and PTR records that map between LDH names and IP
addresses in both directions.

Example scenario:  I type a Cyrillic email address into my IDN-aware
email program.  It performs nameprep and sends the result in a DNS
query using a canonical encoding (UTF-16 say).  It gets back both an IP
address (which it uses to connect to the remote SMTP server if there is
no MX record) and an LDH domain name.  It puts the LDH name in the To:
field of the message header, in order to conform to RFC 822.

Suppose the message is sent to multiple recipients.  They can all reply
to everyone in the To: field, because the domain names there are LDH
names.  Additionally, IDN-aware mail programs can do a DNS lookup on the
LDH domain names to discover the corresponding Unicode domain names, and
show the latter to the user.

I don't think this requires any changes to the DNS protocol, only the
addition of two new resource record types.

I don't like this idea as much as ACE, for two reasons:  First, the
mapping between LDH names and Unicode names cannot be done offline.
Second, there is no guarantee that the mapping is consistent in the
two directions (just as there is currently no guarantee of consistency
between A and PTR records).  It has one advantage over ACE, though:  The
LDH names can be chosen arbitrarily, and need not look like gibberish.

AMC



From owner-idn@ops.ietf.org  Tue May  1 21:35:37 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA14744
	for <idn-archive@lists.ietf.org>; Tue, 1 May 2001 21:35:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14ulLK-000FOV-00
	for idn-data@psg.com; Tue, 01 May 2001 18:22:14 -0700
Received: from ns1.neteka.com ([205.150.182.130] helo=neteka.com)
	by psg.com with smtp (Exim 3.16 #1)
	id 14ulLK-000FOD-00
	for idn@ops.ietf.org; Tue, 01 May 2001 18:22:14 -0700
Message-ID: <004601c0d2a6$b40c8f60$1001a8c0@vaioedmon>
From: "Edmon" <edmon@neteka.com>
To: "Dave Crocker" <dhc@dcrocker.net>
Cc: <idn@ops.ietf.org>
References: <5.1.0.14.2.20010430101932.038a4fb0@dcrocker.net> <5.1.0.14.2.20010501174039.00b44740@dcrocker.net>
Subject: [idn] Re: Alternative Solutions
Date: Tue, 1 May 2001 21:24: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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> At 05:23 PM 5/1/2001, Edmon wrote:
> >Server-side ACE - ACE transformation takes place at server end
>
> If the transformation is done at the server, then the data travel from the
> client as binary.  How is that different from your second alternative?
>
> For that matter, why bother with an ACE transformation at that point?
>
> Please clarify.

There are a number of reasons, including:
- ACE domain can be used after the DNS, such as web & mail (part of the
argument for using ACE)
- ACE domain could be used for administration purposes, for sys admins to
configure and edit zone files, etc.
- will be able to transition to the "long-term" protocol extension solution
easily

>
>
> >Protocol Extension - use extension mechanisms such as EDNS or other bit
> >flagging & use UTF
>
> This is a class, "dual-stack" operation.  One stack is the original system
> and the second is the new.
>
> (By way of raising a warning flag early, one danger with this approach is
> what we have seen with IPv6.  Namely, people will try to add zillions of
> changes and features, thereby delaying the effort by years.)

EDNS is pretty much in place and other extension mechanisms could be easily
introduced also.  As to lengthy discussions, it depends on whether we are
zoomed into providing a multilingual dns only and leave bells and whistles
to the implementors.  So long as the core platform is there, if implementors
decide to add features and delay their own roll out then its their decision.

Edmon







From owner-idn@ops.ietf.org  Tue May  1 21:44:28 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA14884
	for <idn-archive@lists.ietf.org>; Tue, 1 May 2001 21:44:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14ulSJ-000FlE-00
	for idn-data@psg.com; Tue, 01 May 2001 18:29:27 -0700
Received: from blake.i-email.net ([203.126.116.232])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14ulSI-000Fl8-00
	for idn@ops.ietf.org; Tue, 01 May 2001 18:29:26 -0700
Received: from maynardibm (bianca.i-email.net [202.55.72.10])
	by blake.i-email.net (Postfix) with SMTP
	id 5222DA890A; Wed,  2 May 2001 09:29:24 +0800 (SGT)
Message-ID: <000701c0d2a7$4f450a70$0200000a@maynardibm>
From: "Maynard Kang" <maynard@pobox.org.sg>
To: <idn@ops.ietf.org>, "Adam M. Costello" <amc@cs.berkeley.edu>
References: <5.1.0.14.2.20010430101932.038a4fb0@dcrocker.net> <002e01c0d29e$1a80faa0$1001a8c0@vaioedmon> <20010502011708.C6619@arwen.cs.berkeley.edu>
Subject: Re: [idn] Alternative Solutions
Date: Wed, 2 May 2001 09:29:19 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I don't like this idea as much as ACE, for two reasons:  First, the
> mapping between LDH names and Unicode names cannot be done offline.
> Second, there is no guarantee that the mapping is consistent in the
> two directions (just as there is currently no guarantee of consistency
> between A and PTR records).  It has one advantage over ACE, though:  The
> LDH names can be chosen arbitrarily, and need not look like gibberish.

I think that this approach would be a major impediment to e-mail users;
after all, one of the main features of e-mail is that the user can
read/compose/reply mail offline, and connect only as and when required to
send/receive.

Alternatively, the e-mail application might be absolved of any code
transformation duties and leave that entirely up to the originating SMTP
server. Since most MUAs these days depend on a relay MTA and do not send
directly to destination hosts anyway, perhaps it might make sense to do the
code conversion at that particular relay MTA instead of at the MUA itself.

The MUA would have to be made aware of the MTA's code transformation
feature though; maybe this can be achieved by an SMTP extension. But I
digress; this is not the working group to do this. =)

maynard






From owner-idn@ops.ietf.org  Tue May  1 21:50:27 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA14925
	for <idn-archive@lists.ietf.org>; Tue, 1 May 2001 21:50:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14ulb3-000GAd-00
	for idn-data@psg.com; Tue, 01 May 2001 18:38:29 -0700
Received: from blake.i-email.net ([203.126.116.232])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14ulb2-000GAW-00
	for idn@ops.ietf.org; Tue, 01 May 2001 18:38:28 -0700
Received: from maynardibm (bianca.i-email.net [202.55.72.10])
	by blake.i-email.net (Postfix) with SMTP
	id 7C171A890A; Wed,  2 May 2001 09:38:26 +0800 (SGT)
Message-ID: <001101c0d2a8$92769ec0$0200000a@maynardibm>
From: "Maynard Kang" <maynard@pobox.org.sg>
To: "Edmon" <edmon@neteka.com>, "Dave Crocker" <dhc@dcrocker.net>
Cc: <idn@ops.ietf.org>
References: <5.1.0.14.2.20010430101932.038a4fb0@dcrocker.net> <5.1.0.14.2.20010501174039.00b44740@dcrocker.net> <004601c0d2a6$b40c8f60$1001a8c0@vaioedmon>
Subject: Re: [idn] Re: Alternative Solutions
Date: Wed, 2 May 2001 09:38:21 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> > >Server-side ACE - ACE transformation takes place at server end
> >
> > If the transformation is done at the server, then the data travel from
the
> > client as binary.  How is that different from your second alternative?
> >
> > For that matter, why bother with an ACE transformation at that point?
> >
> > Please clarify.
>
> There are a number of reasons, including:
> - ACE domain can be used after the DNS, such as web & mail (part of the
> argument for using ACE)
> - ACE domain could be used for administration purposes, for sys admins to
> configure and edit zone files, etc.
> - will be able to transition to the "long-term" protocol extension
solution
> easily

Web & Mail involve the application layer. A DNS server-side ACE approach
would require that web and mail applications communicate in binary (ok,
8-bit, "binary" sounds a little ASCII-bigoted), and neither of these
applications are perfectly capable of doing this.

I always thought it has been established that the IDN problem does not lie
with the DNS protocol or RFC 1034/35, but rather, that the applications
will balk and die upon seeing "binary" data in places where it is not
supposed to appear.

maynard





From owner-idn@ops.ietf.org  Wed May  2 00:00:28 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA17403
	for <idn-archive@lists.ietf.org>; Wed, 2 May 2001 00:00:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14unQh-000LZJ-00
	for idn-data@psg.com; Tue, 01 May 2001 20:35:55 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14unQg-000LZD-00
	for idn@ops.ietf.org; Tue, 01 May 2001 20:35:54 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id XAA11064;
        Tue, 1 May 2001 23:35:39 -0400 (EDT)
Message-Id: <200105020335.XAA11064@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Edmon" <edmon@neteka.com>
cc: "Russ Rolfe" <rrolfe@exchange.microsoft.com>,
        "Dave Crocker" <dhc@dcrocker.net>, idn@ops.ietf.org
Subject: Re: [idn] Alternative Solutions 
In-reply-to: Your message of "Tue, 01 May 2001 20:23:15 EDT."
             <002e01c0d29e$1a80faa0$1001a8c0@vaioedmon> 
Date: Tue, 01 May 2001 23:35:39 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Server-side ACE - ACE transformation takes place at server end

even if you set up another way to do queries for IDNs
(whether this is a separate protocol or a mode bit or whatever)
you still need ACE for client protocols that only support ASCII names.



From owner-idn@ops.ietf.org  Wed May  2 00:05:20 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA17452
	for <idn-archive@lists.ietf.org>; Wed, 2 May 2001 00:05:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14unZU-000M0T-00
	for idn-data@psg.com; Tue, 01 May 2001 20:45:00 -0700
Received: from ns1.neteka.com ([205.150.182.130] helo=neteka.com)
	by psg.com with smtp (Exim 3.16 #1)
	id 14unZT-000M0N-00
	for idn@ops.ietf.org; Tue, 01 May 2001 20:44:59 -0700
Message-ID: <006001c0d2ba$9db4dd80$1001a8c0@vaioedmon>
From: "Edmon" <edmon@neteka.com>
To: <idn@ops.ietf.org>, "Adam M. Costello" <amc@cs.berkeley.edu>
References: <5.1.0.14.2.20010430101932.038a4fb0@dcrocker.net> <002e01c0d29e$1a80faa0$1001a8c0@vaioedmon> <20010502011708.C6619@arwen.cs.berkeley.edu>
Subject: Re: [idn] Alternative Solutions
Date: Tue, 1 May 2001 23:47:24 -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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Extending your idea back to an algorithmic approach, we could set it so that
the LDH names be created using ACE and that nameservers during loading would
check that they are consistent with the unicode name.  When the LDH response
is received by the DNS, it will be utilized for other protocols such as
mail.
Edmon

> Edmon <edmon@neteka.com> wrote:
>
> > Server-side ACE - ACE transformation takes place at server end
>
> If it's on the server, it doesn't have to be an algorithmic
> transformation; it can just be a distributed lookup table (which is what
> DNS is anyway).
>
> Two new resource record types could be created, one that gives the
> Unicode domain name associated with an LDH (letter/digit/hyphen) name,
> and one that gives the LDH name associated with a Unicode name.  This
> is analogous to the A and PTR records that map between LDH names and IP
> addresses in both directions.
>
> Example scenario:  I type a Cyrillic email address into my IDN-aware
> email program.  It performs nameprep and sends the result in a DNS
> query using a canonical encoding (UTF-16 say).  It gets back both an IP
> address (which it uses to connect to the remote SMTP server if there is
> no MX record) and an LDH domain name.  It puts the LDH name in the To:
> field of the message header, in order to conform to RFC 822.
>
> Suppose the message is sent to multiple recipients.  They can all reply
> to everyone in the To: field, because the domain names there are LDH
> names.  Additionally, IDN-aware mail programs can do a DNS lookup on the
> LDH domain names to discover the corresponding Unicode domain names, and
> show the latter to the user.
>
> I don't think this requires any changes to the DNS protocol, only the
> addition of two new resource record types.
>
> I don't like this idea as much as ACE, for two reasons:  First, the
> mapping between LDH names and Unicode names cannot be done offline.
> Second, there is no guarantee that the mapping is consistent in the
> two directions (just as there is currently no guarantee of consistency
> between A and PTR records).  It has one advantage over ACE, though:  The
> LDH names can be chosen arbitrarily, and need not look like gibberish.
>
> AMC




From owner-idn@ops.ietf.org  Wed May  2 00:36:36 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA17748
	for <idn-archive@lists.ietf.org>; Wed, 2 May 2001 00:36:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14uo6G-000NmS-00
	for idn-data@psg.com; Tue, 01 May 2001 21:18:52 -0700
Received: from blake.i-email.net ([203.126.116.232])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14uo6F-000NmM-00
	for idn@ops.ietf.org; Tue, 01 May 2001 21:18:52 -0700
Received: from maynardibm (bianca.i-email.net [202.55.72.10])
	by blake.i-email.net (Postfix) with SMTP
	id 25D18A890A; Wed,  2 May 2001 12:18:49 +0800 (SGT)
Message-ID: <000701c0d2be$fa5aae80$0200000a@maynardibm>
From: "Maynard Kang" <maynard@pobox.org.sg>
To: "Edmon" <edmon@neteka.com>, <idn@ops.ietf.org>,
        "Adam M. Costello" <amc@cs.berkeley.edu>
References: <5.1.0.14.2.20010430101932.038a4fb0@dcrocker.net> <002e01c0d29e$1a80faa0$1001a8c0@vaioedmon> <20010502011708.C6619@arwen.cs.berkeley.edu> <006001c0d2ba$9db4dd80$1001a8c0@vaioedmon>
Subject: Re: [idn] Alternative Solutions
Date: Wed, 2 May 2001 12:18:43 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Actually I think there was a similar approach presented by the JPNIC team in
Pittsburgh, which proposes using the DNS server to perform canonicalization.
This can be extended to do transformation to ACE or mapping to an LDH.

However, the problem with these solutions is that we are lacing DNS with
meta-records which cause additional burden on applications as they have yet
again another layer to deal with when processing these identifiers.

Again, this makes me seriously doubt that a pretty solution to
internationalized identifiers can be found by tweaking DNS as it is.

maynar

----- Original Message -----
From: "Edmon" <edmon@neteka.com>
To: <idn@ops.ietf.org>; "Adam M. Costello" <amc@cs.berkeley.edu>
Sent: Wednesday, May 02, 2001 11:47 AM
Subject: Re: [idn] Alternative Solutions


> Extending your idea back to an algorithmic approach, we could set it so
that
> the LDH names be created using ACE and that nameservers during loading
would
> check that they are consistent with the unicode name.  When the LDH
response
> is received by the DNS, it will be utilized for other protocols such as
> mail.
> Edmon
>
> > Edmon <edmon@neteka.com> wrote:
> >
> > > Server-side ACE - ACE transformation takes place at server end
> >
> > If it's on the server, it doesn't have to be an algorithmic
> > transformation; it can just be a distributed lookup table (which is what
> > DNS is anyway).
> >
> > Two new resource record types could be created, one that gives the
> > Unicode domain name associated with an LDH (letter/digit/hyphen) name,
> > and one that gives the LDH name associated with a Unicode name.  This
> > is analogous to the A and PTR records that map between LDH names and IP
> > addresses in both directions.
> >
> > Example scenario:  I type a Cyrillic email address into my IDN-aware
> > email program.  It performs nameprep and sends the result in a DNS
> > query using a canonical encoding (UTF-16 say).  It gets back both an IP
> > address (which it uses to connect to the remote SMTP server if there is
> > no MX record) and an LDH domain name.  It puts the LDH name in the To:
> > field of the message header, in order to conform to RFC 822.
> >
> > Suppose the message is sent to multiple recipients.  They can all reply
> > to everyone in the To: field, because the domain names there are LDH
> > names.  Additionally, IDN-aware mail programs can do a DNS lookup on the
> > LDH domain names to discover the corresponding Unicode domain names, and
> > show the latter to the user.
> >
> > I don't think this requires any changes to the DNS protocol, only the
> > addition of two new resource record types.
> >
> > I don't like this idea as much as ACE, for two reasons:  First, the
> > mapping between LDH names and Unicode names cannot be done offline.
> > Second, there is no guarantee that the mapping is consistent in the
> > two directions (just as there is currently no guarantee of consistency
> > between A and PTR records).  It has one advantage over ACE, though:  The
> > LDH names can be chosen arbitrarily, and need not look like gibberish.
> >
> > AMC
>
>




From owner-idn@ops.ietf.org  Wed May  2 04:15:15 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA03620
	for <idn-archive@lists.ietf.org>; Wed, 2 May 2001 04:15:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14urS2-0008hJ-00
	for idn-data@psg.com; Wed, 02 May 2001 00:53:34 -0700
Received: from ns.jck.com ([209.187.148.211] helo=A4.JCK.COM)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14urS2-0008hD-00
	for idn@ops.ietf.org; Wed, 02 May 2001 00:53:34 -0700
Received: from slip-32-101-77-235.dc.us.prserv.net
 ("port 1077"@[32.101.77.235]) by a4.jck.com (PMDF V6.0-24 #44844)
 with ESMTPA id <0GCP00B4A795CP@a4.jck.com> for idn@ops.ietf.org; Wed,
 02 May 2001 03:53:32 -0400 (EDT)
Date: Wed, 02 May 2001 03:53:28 -0400
From: John C Klensin <klensin@jck.com>
Subject: Re: [idn] Alternative Solutions
In-reply-to: <200105020335.XAA11064@astro.cs.utk.edu>
To: Keith Moore <moore@cs.utk.edu>
Cc: idn@ops.ietf.org
Message-id: <933130610.988775608@slip-32-101-77-235.dc.us.prserv.net>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.8 (Win32)
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, 01 May, 2001 23:35 -0400 Keith Moore
<moore@cs.utk.edu> wrote:

>> Server-side ACE - ACE transformation takes place at server end
> 
> even if you set up another way to do queries for IDNs
> (whether this is a separate protocol or a mode bit or whatever)
> you still need ACE for client protocols that only support ASCII
> names.

Unless we go either into a new class (or some EDNS-required
mechanism) that prevents an "international" name from being seen,
and an "international" query from being made, except by IDN-aware
applications.  If unconverted client protocols, and unconverted
clients using converted protocols, cannot access
international-format names or have such names returned to them,
one doesn't _need_ ACE to protect them from damage.

There are, of course, still some advantages of using ACE
encodings rather than something else with such mechanisms, but
they could presumably be used without a tagging prefix, saving
some of the strange appearance of the things and four characters
of label length.

     john








From owner-idn@ops.ietf.org  Wed May  2 05:44:27 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA04508
	for <idn-archive@lists.ietf.org>; Wed, 2 May 2001 05:44:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14uswD-000D6Y-00
	for idn-data@psg.com; Wed, 02 May 2001 02:28:49 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14uswC-000D6R-00
	for idn@ops.ietf.org; Wed, 02 May 2001 02:28:49 -0700
Received: from [192.168.1.34] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id LAA25077;
	Wed, 2 May 2001 11:28:37 +0200 (MET DST)
Date: Wed, 02 May 2001 11:28:26 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Dave Crocker <dhc@dcrocker.net>, Edmon <edmon@neteka.com>
cc: idn@ops.ietf.org
Subject: Re: [idn] Re: Alternative Solutions
Message-ID: <5905547.988802906@[192.168.1.34]>
In-Reply-To: <5.1.0.14.2.20010501174039.00b44740@dcrocker.net>
References: <5.1.0.14.2.20010430101932.038a4fb0@dcrocker.net>
 <5.1.0.14.2.20010501174039.00b44740@dcrocker.net>
X-Mailer: Mulberry/2.1.0a5 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-05-01 17.43 -0700 Dave Crocker <dhc@dcrocker.net> wrote:

> At 05:23 PM 5/1/2001, Edmon wrote:
>> Server-side ACE - ACE transformation takes place at server end
> 
> If the transformation is done at the server, then the data travel from
> the  client as binary.  How is that different from your second
> alternative?
> 
> For that matter, why bother with an ACE transformation at that point?
> 
> Please clarify.

...and how does this solve the problem with domainnames used as protocol
parameters in applications?

  paf




From owner-idn@ops.ietf.org  Wed May  2 06:47:29 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA05097
	for <idn-archive@lists.ietf.org>; Wed, 2 May 2001 06:47:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14utzH-000GDz-00
	for idn-data@psg.com; Wed, 02 May 2001 03:36:03 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14utzG-000GDs-00
	for idn@ops.ietf.org; Wed, 02 May 2001 03:36:02 -0700
Received: from jamessonyvaio (dialupA2111.exasia.net [202.2.65.111])
	by mail.i-dns.net (Postfix) with SMTP
	id D62D7FFC16; Wed,  2 May 2001 18:38:50 +0800 (SGT)
Message-ID: <026601c0d2f3$8ee3e600$0201000a@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Edmon" <edmon@neteka.com>, "Kenneth Whistler" <kenw@sybase.com>,
        <idn@ops.ietf.org>
Cc: <kenw@sybase.com>
References: <200105012144.OAA10940@birdie.sybase.com> <003401c0d29e$d8d86560$1001a8c0@vaioedmon>
Subject: Re: traditional/simplified (Re: [idn] wg milestones update)
Date: Wed, 2 May 2001 18:29:14 +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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Saying TC-SC is like "color" and "colour" is a naive view of the whole
TC-SC problem.

-James Seng

----- Original Message -----
From: "Edmon" <edmon@neteka.com>
To: "Kenneth Whistler" <kenw@sybase.com>; <idn@ops.ietf.org>
Cc: <kenw@sybase.com>
Sent: Wednesday, May 02, 2001 8:28 AM
Subject: Re: traditional/simplified (Re: [idn] wg milestones update)


> > Incidentally, for those who cannot directly envision the issues for
> > trying to match traditional and simplified Chinese domain names, a
> > roughly comparable problem would be trying to match "traditional"
> > British English spellings and lexical conventions with "simplified"
> > American English spellings and lexical conventions, so that, for
> > example:
> >
> >     www.theatre.com  and  www.theater.com
> >
> > would resolve to the same domain name, to avoid "confusions" among
> > users who might be using the "traditional" forms or the "simplified"
> > forms of the "same" name. But of course no such matching is
attempted
> > now for English-based domain names, let alone all
Latin-character-based
> > domain names
>
> I totally agree with this analogy as I have pointed it out a long time
ago
> at the Pittsburg IETF. (with a different word: colour vs color)
> It is still best left to the policy makers of a registry (or domain
admin of
> any domain for that matter) to determine trad-simp mapping.
>
> Edmon
>
>




From owner-idn@ops.ietf.org  Wed May  2 08:44:14 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA08351
	for <idn-archive@lists.ietf.org>; Wed, 2 May 2001 08:44:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14uviI-000LeU-00
	for idn-data@psg.com; Wed, 02 May 2001 05:26:38 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14uviH-000LeO-00
	for idn@ops.ietf.org; Wed, 02 May 2001 05:26:37 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id IAA11009;
        Wed, 2 May 2001 08:26:30 -0400 (EDT)
Message-Id: <200105021226.IAA11009@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: John C Klensin <klensin@jck.com>
cc: Keith Moore <moore@cs.utk.edu>, idn@ops.ietf.org
Subject: Re: [idn] Alternative Solutions 
In-reply-to: Your message of "Wed, 02 May 2001 03:53:28 EDT."
             <933130610.988775608@slip-32-101-77-235.dc.us.prserv.net> 
Date: Wed, 02 May 2001 08:26:30 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> >> Server-side ACE - ACE transformation takes place at server end
> > 
> > even if you set up another way to do queries for IDNs
> > (whether this is a separate protocol or a mode bit or whatever)
> > you still need ACE for client protocols that only support ASCII
> > names.
> 
> Unless we go either into a new class (or some EDNS-required
> mechanism) that prevents an "international" name from being seen,
> and an "international" query from being made, except by IDN-aware
> applications.  

*AND* we insist that "international" names are never leaked 
*by any protocol* (including, say, SMTP) to an application that
doesn't understand them.  In practice this means not just a mode
bit for DNS but also a mode bit for every protocol that carries
DNS names.

which doesn't seem like a very attractive path to me.

Keith



From owner-idn@ops.ietf.org  Wed May  2 16:22:55 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA22409
	for <idn-archive@lists.ietf.org>; Wed, 2 May 2001 16:22:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14v2i5-000IuL-00
	for idn-data@psg.com; Wed, 02 May 2001 12:54:53 -0700
Received: from inergen.sybase.com ([192.138.151.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14v2i4-000IsX-00
	for idn@ops.ietf.org; Wed, 02 May 2001 12:54:52 -0700
Received: from smtp2.sybase.com (sybgate2.sybase.com [130.214.88.21])
	by inergen.sybase.com  with ESMTP id MAA10986;
	Wed, 2 May 2001 12:54:19 -0700 (PDT)
Received: from olympus.sybase.com (olympus [130.214.160.74])
	by smtp2.sybase.com  with ESMTP id MAA01504;
	Wed, 2 May 2001 12:54:19 -0700 (PDT)
Received: from birdie.sybase.com by olympus.sybase.com (8.8.8+Sun/SMI-SVR4/SybEC3.5)
	id MAA12721; Wed, 2 May 2001 12:54:17 -0700 (PDT)
Received: (from kenw@localhost)
	by birdie.sybase.com (8.8.8+Sun/8.8.8) id MAA11126;
	Wed, 2 May 2001 12:54:16 -0700 (PDT)
Date: Wed, 2 May 2001 12:54:16 -0700 (PDT)
From: Kenneth Whistler <kenw@sybase.com>
Message-Id: <200105021954.MAA11126@birdie.sybase.com>
To: James@Seng.cc
Subject: Re: traditional/simplified (Re: [idn] wg milestones update)
Cc: idn@ops.ietf.org, kenw@sybase.com
X-Sun-Charset: US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James,

> Saying TC-SC is like "color" and "colour" is a naive view of the whole
> TC-SC problem.

And I think this is a misleading characterization of my use of analogy
to try to illustrate the level of complexity of the problem;

> 
> > > Incidentally, for those who cannot directly envision the issues for
> > > trying to match traditional and simplified Chinese domain names, a
> > > roughly comparable problem would be trying to match "traditional"
> > > British English spellings and lexical conventions with "simplified"
> > > American English spellings and lexical conventions, 

The analogy is on the requirement for lexical analysis and dictionary
lookup to solve the problem of matching alternate forms of representation
of the "same" words in the "same" language.

And the second level of the analogy is to point out that the kind
of variant form problem that TC-SC folding is aiming to avoid is
already tolerated among ASCII-based domain names.

I'm not claiming that TC-SC can just be characterized as a spelling
issue.

Incidentally, for those claiming that simplified/traditional folding
should be done for Chinese for idn matching, it seems naive to assume
that the problem of Han character matching can stop there.

What about the problem of Z-variant folding for all the Han
characters in Unicode? Z-variants included in Unicode (because of
the source separation rule, for example) are *less* distinct, by
any reasonable criterion, than a simplified/traditional pair.

So we have the traditional: U+570B 'country'
        and the simplified: U+56FD 'country'

But what about the Chinese Z-variant: U+56EF guo2 'country'

Or U+797F and U+7984?

And many, many other examples.

As far as I know, no one has a reliable and complete Z-variant folding
table for all of the unified Han in Unicode, especially now with the
recent addition of Vertical Extension B, with another 42,711 ideographs.

And besides the large, but reasonably easy-to-identify set of
simplified ideographs introduced by the PRC, what about:

Japanese- and/or Korean-specific simplifications?

Pre-revolutionary simplifications within the traditional set of
ideographs?

Traditional synonymic alternates that have not been unified
because their gross glyphic structure is distinct?

Kaishu forms of guwen variants that were included in Vertical
Extension B for complete coverage of the traditional Han dictionaries?
(For example, see U+20006, U+20007, and U+20009, which are apparently 
all guwen variants of the common ideograph U+4E2D 'middle'.)

Where exactly do you draw a principled line that will be understood
and which can be reliably implemented everywhere to do idn
name matching?

--Ken



From owner-idn@ops.ietf.org  Wed May  2 20:05:55 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA26781
	for <idn-archive@lists.ietf.org>; Wed, 2 May 2001 20:05:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14v6Kv-00061R-00
	for idn-data@psg.com; Wed, 02 May 2001 16:47:13 -0700
Received: from ns1.neteka.com ([205.150.182.130] helo=neteka.com)
	by psg.com with smtp (Exim 3.16 #1)
	id 14v6Ku-00061J-00
	for idn@ops.ietf.org; Wed, 02 May 2001 16:47:12 -0700
Message-ID: <002101c0d362$96b3dec0$1001a8c0@vaioedmon>
From: "Edmon" <edmon@neteka.com>
To: "James Seng/Personal" <James@Seng.cc>,
        "Kenneth Whistler" <kenw@sybase.com>, <idn@ops.ietf.org>
Cc: <kenw@sybase.com>
References: <200105012144.OAA10940@birdie.sybase.com> <003401c0d29e$d8d86560$1001a8c0@vaioedmon> <026601c0d2f3$8ee3e600$0201000a@jamessonyvaio>
Subject: Re: traditional/simplified (Re: [idn] wg milestones update)
Date: Wed, 2 May 2001 19:49:46 -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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

TC/SC and Brit/US (colour vs color) are neither a simplistic problem.
From my experience of TC/SC usage in HK and Brit/US English in Canada, there
is a growing trend to mix the two.  Both are accepted and sometimes mixed.
Edmon

> Saying TC-SC is like "color" and "colour" is a naive view of the whole
> TC-SC problem.
>
> -James Seng
>
> ----- Original Message -----
> From: "Edmon" <edmon@neteka.com>
> To: "Kenneth Whistler" <kenw@sybase.com>; <idn@ops.ietf.org>
> Cc: <kenw@sybase.com>
> Sent: Wednesday, May 02, 2001 8:28 AM
> Subject: Re: traditional/simplified (Re: [idn] wg milestones update)
>
>
> > > Incidentally, for those who cannot directly envision the issues for
> > > trying to match traditional and simplified Chinese domain names, a
> > > roughly comparable problem would be trying to match "traditional"
> > > British English spellings and lexical conventions with "simplified"
> > > American English spellings and lexical conventions, so that, for
> > > example:
> > >
> > >     www.theatre.com  and  www.theater.com
> > >
> > > would resolve to the same domain name, to avoid "confusions" among
> > > users who might be using the "traditional" forms or the "simplified"
> > > forms of the "same" name. But of course no such matching is
> attempted
> > > now for English-based domain names, let alone all
> Latin-character-based
> > > domain names
> >
> > I totally agree with this analogy as I have pointed it out a long time
> ago
> > at the Pittsburg IETF. (with a different word: colour vs color)
> > It is still best left to the policy makers of a registry (or domain
> admin of
> > any domain for that matter) to determine trad-simp mapping.
> >
> > Edmon
> >
> >




From owner-idn@ops.ietf.org  Wed May  2 20:20:30 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA27038
	for <idn-archive@lists.ietf.org>; Wed, 2 May 2001 20:20:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14v6Yf-0006xG-00
	for idn-data@psg.com; Wed, 02 May 2001 17:01:25 -0700
Received: from ns1.neteka.com ([205.150.182.130] helo=neteka.com)
	by psg.com with smtp (Exim 3.16 #1)
	id 14v6Ye-0006xA-00
	for idn@ops.ietf.org; Wed, 02 May 2001 17:01:24 -0700
Message-ID: <004201c0d364$94b2a5a0$1001a8c0@vaioedmon>
From: "Edmon" <edmon@neteka.com>
To: "Keith Moore" <moore@cs.utk.edu>, "John C Klensin" <klensin@jck.com>
Cc: "Keith Moore" <moore@cs.utk.edu>, <idn@ops.ietf.org>
References: <200105021226.IAA11009@astro.cs.utk.edu>
Subject: Re: [idn] Alternative Solutions 
Date: Wed, 2 May 2001 20:03:57 -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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

What about this:
since for IDNA we assume that there needs to be a client upgrade anyway,
adding more stuff should be ok.

- client sends DNS request with mode bit in UTF
- Server returns UTF=A/A6/MX, etc AND UTF=LDH(in an ACE)
- client then chooses to use straight UTF or LDH info when using DNS info in
other apps
  based on - if the other app is IDN aware, it uses UTF with mode bit
                 - if the other app is nonIDN aware, it uses LDH in ACE

This gives us the benefits of ACE being able to be used for other protocols
which are not upgraded yet and also provides a clear path foward towards a
UTF+mode bit longer term solution.

Edmon


> > >> Server-side ACE - ACE transformation takes place at server end
> > >
> > > even if you set up another way to do queries for IDNs
> > > (whether this is a separate protocol or a mode bit or whatever)
> > > you still need ACE for client protocols that only support ASCII
> > > names.
> >
> > Unless we go either into a new class (or some EDNS-required
> > mechanism) that prevents an "international" name from being seen,
> > and an "international" query from being made, except by IDN-aware
> > applications.
>
> *AND* we insist that "international" names are never leaked
> *by any protocol* (including, say, SMTP) to an application that
> doesn't understand them.  In practice this means not just a mode
> bit for DNS but also a mode bit for every protocol that carries
> DNS names.
>
> which doesn't seem like a very attractive path to me.
>
> Keith




From owner-idn@ops.ietf.org  Wed May  2 21:08:52 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA27753
	for <idn-archive@lists.ietf.org>; Wed, 2 May 2001 21:08:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14v7MX-0009j1-00
	for idn-data@psg.com; Wed, 02 May 2001 17:52:57 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14v7MW-0009iv-00
	for idn@ops.ietf.org; Wed, 02 May 2001 17:52:56 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id UAA16796;
        Wed, 2 May 2001 20:52:48 -0400 (EDT)
Message-Id: <200105030052.UAA16796@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Edmon" <edmon@neteka.com>
cc: "Keith Moore" <moore@cs.utk.edu>, "John C Klensin" <klensin@jck.com>,
        idn@ops.ietf.org
Subject: Re: [idn] Alternative Solutions 
In-reply-to: Your message of "Wed, 02 May 2001 20:03:57 EDT."
             <004201c0d364$94b2a5a0$1001a8c0@vaioedmon> 
Date: Wed, 02 May 2001 20:52:48 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Edmon,

I'm not at all sure it's desirable to have a DNS query protocol which 
allows the server to specify the relationship between the native form 
and the ACE form - you want consistent results regardless of whether
the lookup is done using native or ACE format, and a protocol like you
describe is almost begging servers to play games with the relationship
between the two and to produce inconsistent results.

and even if you allow queries in a native format, you also have to
support queries in ACE format, for the benefit of legacy apps that
don't have any specific knowledge of IDNs but still need to be able 
to look up ACE IDNs.  so I'm not sure how much this helps.

Keith



From owner-idn@ops.ietf.org  Wed May  2 21:31:47 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA28030
	for <idn-archive@lists.ietf.org>; Wed, 2 May 2001 21:31:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14v7oF-000BFu-00
	for idn-data@psg.com; Wed, 02 May 2001 18:21:35 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14v7oE-000BFd-00
	for idn@ops.ietf.org; Wed, 02 May 2001 18:21:34 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 14v7oD-0004PF-00; Wed, 02 May 2001 18:21:33 -0700
Date: Thu, 3 May 2001 01:21:33 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Alternative Solutions
Message-ID: <20010503012132.B15150@arwen.cs.berkeley.edu>
References: <002e01c0d29e$1a80faa0$1001a8c0@vaioedmon> <20010502011708.C6619@arwen.cs.berkeley.edu> <006001c0d2ba$9db4dd80$1001a8c0@vaioedmon> <000701c0d2be$fa5aae80$0200000a@maynardibm> <933130610.988775608@slip-32-101-77-235.dc.us.prserv.net> <200105021226.IAA11009@astro.cs.utk.edu> <200105020335.XAA11064@astro.cs.utk.edu> <933130610.988775608@slip-32-101-77-235.dc.us.prserv.net> <002e01c0d29e$1a80faa0$1001a8c0@vaioedmon> <200105020335.XAA11064@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <200105020335.XAA11064@astro.cs.utk.edu>; from moore@cs.utk.edu on Tue, May 01, 2001 at 11:35:39PM -0400
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This discussion seems to be getting more complicated than necessary.

First, let's make sure we all mean the same thing when we say "ACE".
When I say "ACE", I mean a reversible algorithmic mapping from Unicode
strings to LDH strings.

What started this thread was the possibility that patents might prevent
us from using an ACE.  If we're going to use an ACE at all, we might
as well stick with IDNA, so the alternative ideas, whatever they are,
should not require the use of an ACE.

The main problem that IDN needs to solve is the problem of higher-layer
protocols and software assuming that domain names contain only LDH
characters and dots.  So for every Unicode domain name, there needs
to be an LDH domain name that these older protocols and software can
use.  If we're not allowed to do the transformation algorithmically, the
obvious other option is a giant lookup table.  And that's what DNS is.

So take the IDNA architecture, replace the ace_encode operation by a
dns_lookup_ldh_of(unicode_name) operation, and replace the ace_decode
operation by a dns_lookup_unicode_of(ldh_name) operation.  Everything
else can stay the same.

That bears repeating:  Everything else can stay the same as IDNA.
Things that work or don't work in IDNA will still work or not work in
the new scheme.  The only exceptions are:

  * Applications now need to be online to do these operations, whereas
    in IDNA they could be offline.

  * IDNs can exist only in domains served by upgraded DNS servers that
    know the new resource record types, whereas IDNA requires no changes
    to DNS.

  * The LDH name need not look like gibberish (as in IDNA), but
    can be chosen at the whims of the registrants and/or name
    server administrators.  (Some may choose to manually select
    meaningful LDH names, while others may choose to use an algorithmic
    transformation for ease of administration, but there is no need for
    standardization, or even publication, of the algorithm.)

As someone already pointed out, this is just adding another layer.  Just
as domain names are a layer of abstraction on top of IP addresses,
mapped back and forth by A and PTR records, IDNs would be a layer of
abstraction on top of LDH domain names, mapped back and forth by two new
record types.

I don't like this scheme very much.  I'd prefer IDNA.  But if IDNA were
not an option, this would be an obvious thing to look at instead.

Keith Moore <moore@cs.utk.edu> wrote:

> *AND* we insist that "international" names are never leaked *by any
> protocol* (including, say, SMTP) to an application that doesn't
> understand them.  In practice this means not just a mode bit for DNS
> but also a mode bit for every protocol that carries DNS names.

Existing protocols carry only LDH names, so there is no mode bit.  New
protocols (or new versions of old ones) could choose to use a mode
bit, or could choose to continue to carry only LDH names, and let the
receiver look up the Unicode name if it wants to.

AMC



From owner-idn@ops.ietf.org  Wed May  2 22:07:26 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA29318
	for <idn-archive@lists.ietf.org>; Wed, 2 May 2001 22:07:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14v8M9-000DD6-00
	for idn-data@psg.com; Wed, 02 May 2001 18:56:37 -0700
Received: from inergen.sybase.com ([192.138.151.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14v8M9-000DBE-00
	for idn@ops.ietf.org; Wed, 02 May 2001 18:56:37 -0700
Received: from smtp2.sybase.com (sybgate2.sybase.com [130.214.88.21])
	by inergen.sybase.com  with ESMTP id SAA28486
	for <idn@ops.ietf.org>; Wed, 2 May 2001 18:55:07 -0700 (PDT)
Received: from olympus.sybase.com (olympus [130.214.160.74])
	by smtp2.sybase.com  with ESMTP id SAA12815
	for <idn@ops.ietf.org>; Wed, 2 May 2001 18:55:07 -0700 (PDT)
Received: from birdie.sybase.com by olympus.sybase.com (8.8.8+Sun/SMI-SVR4/SybEC3.5)
	id SAA13247; Wed, 2 May 2001 18:55:06 -0700 (PDT)
Received: (from kenw@localhost)
	by birdie.sybase.com (8.8.8+Sun/8.8.8) id SAA11186;
	Wed, 2 May 2001 18:55:06 -0700 (PDT)
Date: Wed, 2 May 2001 18:55:06 -0700 (PDT)
From: Kenneth Whistler <kenw@sybase.com>
Message-Id: <200105030155.SAA11186@birdie.sybase.com>
To: idn@ops.ietf.org
Subject: Re: [idn] Alternative Solutions
Cc: kenw@sybase.com
X-Sun-Charset: US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> First, let's make sure we all mean the same thing when we say "ACE".
> When I say "ACE", I mean a reversible algorithmic mapping from Unicode
> strings to LDH strings.
> 
> What started this thread was the possibility that patents might prevent
> us from using an ACE.

Has it actually been determined that the WALID patent covers *all*
possible "reversible algorithmic mappings from Unicode strings
to LDH strings"? That seems like a stretch to me.

Before this discussion goes too far off track discussing alternatives,
can no one come up with a functional plugin for ace_encode and
ace_decode that avoids any particular techniques covered by the
patent, but which is still *algorithmic* and does not require online
lookup tables?

Trying to think outside the box:

Has anyone considered trying bit and byte transforms directly on
the UTF-8 encoding form, rather than on the Unicode code point?

How about some deterministic and quick compression run on the
UTF-16 encoding form of a Unicode string, and *then* rearranging
the resulting bytes to accomodate ASCII restrictions?

Something else?

Or has WALID actually gotten a patent on a generic concept without
actually specifying a particular technique to accomplish it??

--Ken



From owner-idn@ops.ietf.org  Wed May  2 23:02:41 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA00847
	for <idn-archive@lists.ietf.org>; Wed, 2 May 2001 23:02:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14v94u-000FkV-00
	for idn-data@psg.com; Wed, 02 May 2001 19:42:52 -0700
Received: from [159.226.6.42] (helo=pier.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14v94s-000FkO-00
	for idn@ops.ietf.org; Wed, 02 May 2001 19:42:51 -0700
Received: from deng ([159.226.7.68]) by pier.cnnic.net.cn
          (Netscape Mail Server v2.02) with SMTP id AAA18135;
          Thu, 3 May 2001 10:44:32 +0800
Message-ID: <004101c0d37a$051e0c20$4407e29f@cnnic.net.cn>
Reply-To: =?utf-8?B?6YKT57+U?= <deng@cnnic.net.cn>
From: deng@pier.cnnic.net.cn (deng)
To: "Maynard Kang" <maynard@pobox.org.sg>, <sun@cnnic.net.cn>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
References: <200104291408.f3TE8Ac11734@nic-naa.net> <3AED3C39.CA9E5BBB@cnnic.net.cn> <004801c0d16c$49810800$0200000a@maynardibm>
Subject: Re: [idn] Zone rules (was: wg milestones update)
Date: Thu, 3 May 2001 10:37:38 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_003E_01C0D3BD.13075060"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_003E_01C0D3BD.13075060
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQot
LS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogTWF5bmFyZCBLYW5nIDxtYXluYXJk
QHBvYm94Lm9yZy5zZz4NClRvOiA8c3VuQGNubmljLm5ldC5jbj47IEVyaWMgQnJ1bm5lci1XaWxs
aWFtcyBpbiBQb3J0bGFuZCBNYWluZSA8YnJ1bm5lckBuaWMtbmFhLm5ldD4NCkNjOiA8aWRuQG9w
cy5pZXRmLm9yZz4NClNlbnQ6IE1vbmRheSwgQXByaWwgMzAsIDIwMDEgNzo1NCBQTQ0KU3ViamVj
dDogUmU6IFtpZG5dIFpvbmUgcnVsZXMgKHdhczogd2cgbWlsZXN0b25lcyB1cGRhdGUpDQoNCk1y
LiBtYXluYXJkOg0KVGhhbmtzIGZvciB5b3VyIHN0cmFpZ2gtb3V0LiBPbiB0aGUgc2NpZW50aWZp
YyByb2FkIHRoZXJlIGlzIG5vIGRpZmZlcmVudCBqdXN0IHRoZSBwcm9ibGVtIHdoaWNoIGlzIHdh
aXRpbmcgZm9yIGJlIHNvbHZlZC4NCg0KPkhpIEd1b25pYW4sDQoNCj4+IGZvciBjaGluZXNlIHVz
ZXIsIHRoZSBUQy1TQyBlcXVpdmFsZW5jZSBydWxlIGlzIGp1c3QgYWxpa2UgdGhlDQpjYXNlLWZv
bGRpbmcgcnVsZS4NCj4+IEknZCBsaWtlIHRvIHNob3cgYW4gZXhhbXBsZSBmb2xsb3dlZCB1c2lu
ZyB0aGUgY2FzZS1mb2xkaW5nIHJ1bGUuDQo+Pg0KPj4gdW5kZXIgem9uZSAuQ09NLCBpZiBtYW5h
Z2VyIGRlZmluZXMgdXBwZXIgY2FzZSBjaGFyYWN0ZXJzIGVxdWFsIHRvIGxvd2VyDQpjYXNlDQo+
PiBjaGFyYWN0ZXJzLiB1c2VycyBjb3VsZCBhY2Nlc3MgSUJNJyBkb21haW4gd2l0aCBpYm0uY29t
LCBJQm0uY29tLCAuLi4gaW4NCmFueQ0KPj4gY2FzZS4NCi4uLg0KPj4gU28gSSB0aGluayB0aGUg
VEMtU0MgZXF1aXZhbGVuY2UgcnVsZSBTSE9VTEQgYmUgY29uc2lzdGVudCBhbnl3aGVyZSAuDQoN
Cj5TaW5jZSB3ZSdyZSBvbiB0aGlzIHRvcGljIG9mIFRDLVNDIGVxdWl2YWxlbmNlIHlldCBhZ2Fp
biwgSSdkIGxpa2UgdG8gcG9pbnQNCj5vdXQgdHdvIGlzc3VlcyB0aGF0IEkgdGhpbmsgd2Ugc2hv
dWxkIGFsbCBjb25zaWRlciBiZWZvcmUgd2UgZ28gZnVydGhlciwgaWYNCj50aGVzZSBoYXZlIG5v
dCBiZWVuIHJlaXRlcmF0ZWQgZW5vdWdoIGluIHByZXZpb3VzIHBvc3RpbmdzIG1hZGUgYnkgbW9y
ZQ0KPnF1YWxpZmllZCBpbmRpdmlkdWFscyB0aGFuIG15c2VsZiBpbiB0aGUgcGFzdDoNCg0KPjEp
IFRoZSBydWxlc2V0IGZvciBUQy1TQyBlcXVpdmFsZW5jZSBpcyBub3QgYSAxLW4gb3Igbi0xIG1h
cHBpbmcgb2YNCj5hYnN0cmFjdCBjaGFyYWN0ZXJzLCBhcyBwb2ludGVkIG91dCBieSBIYXJhbGQg
QWx2ZXN0cmFuZC4gSXQgY2FuDQo+YmUgaGlkZW91c2x5IGNvbXBsZXggKHNlZSBkcmFmdC1pZXRm
LWlkbi1jamstMDEudHh0IGZvciBkZXRhaWxzKSwgd2l0aA0KPm51bWVyb3VzIGxleGljYWwgYW5k
IGNvbnRleHR1YWwgY29uc2lkZXJhdGlvbnMuIEkgYW0gc3VyZSB0aGF0IHlvdSB3b3VsZA0KPmtu
b3cgYWJvdXQgdGhlICLlpLTlj5EiID0gIumgremrriIgYnV0ICLlj5HotKIiICE9ICLpq67osqEi
IHByb2JsZW0uDQoNClRDLVNDIGVxdWl2YWxlbmNlIGlzIE5PVCBsZXhpY2FsIGFuZCBjb250ZXh0
dWFsIHByb2JsZW0uaXQncyBjb2RlIG1hcHBpbmcuDQoxLW4gb3Igbi0xIG1hcHBpbmcgaXMgbWlu
b3JpdHksdGhlIDEtMSBtYXBwaW5nIGlzIG1ham9yaXR5LkFib3V0IHRoZSB0d28gcGFydCx3ZSBj
YW4gdXNlICAgICBkaWZmZXJlbnQgbWV0aG9kIHRvIHNvbHZlLg0KDQo+MikgQ2FzZS1mb2xkaW5n
IGlzIGEgc2ltcGxlIGNhbm9uaWNhbCBwcm9jZXNzLCBhbmQgdGhlIGZvbGRpbmcgcnVsZXMgYXJl
DQo+dGhlIHNhbWUsIEkgYmVsaWV2ZSAoc29tZW9uZSBwbGVhc2UgY29ycmVjdCBtZSBpZiBJJ20g
d3JvbmcpLCBmb3IgbW9zdA0KPnNjcmlwdHMgd2hpY2ggYXJlIGFibGUgdG8gYmUgcmVwcmVzZW50
ZWQgaW4gQVNDSUkgKGkuZS4gRW5nbGlzaCwgU3dhaGlsaSwNCj5IYXdhaWlhbiwNCj5NYWxheSwg
ZXRjKS4NCg0KRGVmaW5pdGVseSxBU0NJSSBqdXN0IGluY2x1ZGUgMjYgbGV0dGVyIGFuZCBpcyBl
YXN5IHRvIGRlYWwgd2l0aC4gQnV0IGl0IGlzIGluIEROUy5BbmQgbm93LHdlIGFyZSBkaXNjdXNz
IElETi4gSWYgSUROIGRvIG5vdCB0byBkZWNpZGUgdG8gc29sdmUgbXVsdGlsaWd1YWwgcHJvYmxl
bSwuLi4NCg0KU3VyZSx0aGUgVEMtU0MgbWFwcGluZyBpcyBkaWZmaWN1bHQuSWYgd2UgZ2l2ZSB1
cCBqdXN0IGJlY2F1c2UgZGlmZmljdWx0LGl0J3Mgbm90IHNjaWVudGlmaWMgYXR0aXR1ZGUuDQoN
Cj5Gb3IgZXhhbXBsZSwgdGhlcmUgaXMgbm8gZGViYXRlIGFzIHRvIHdoZXRoZXIgIkNBVCIgb3Ig
ImNhdCIgb3IgImNBdCINCj5yZWZlcnMgdG8gdGhlIHNhbWUgdGhpbmcgKGluIEVuZ2xpc2gpLCBv
ciB3aGV0aGVyICJLVUNISU5HIiBvciAia3VjaGluZyIgb3INCj4ia1VjaGlORyIgcmVmZXJzIHRv
IHRoZSBzYW1lIHRoaW5nICgiY2F0IiBpbiBNYWxheSkuDQoNClRoZXJlIGlzIGFsc28gbm8gZGVi
YXRlIGFzIHRvIHdoZXRoZXIgIuaXpeeUoiIgPSAi5pel5LqnIiAgaW4gQ2hpbmVzZSByZWZlcnMg
dG8gdGhlIHNhbWUgdGhpbmcuIA0KDQo+SG93ZXZlciwgSGFuIGNoYXJhY3RlciBjYW5vbmljYWxp
emF0aW9uIGRvZXMgbm90IGZvbGxvdyB0aGUgc2FtZSBydWxlcy4gSGFuDQo+Y2hhcmFjdGVycyB1
c2VkIGluIENoaW5lc2UsIEphcGFuZXNlIGFuZCBLb3JlYW4gaGF2ZSBkaWZmZXJlbnQgZXF1aXZh
bGVuY2UNCj5ydWxlcy4gVGhpcyBpcyBhbHNvIHBvaW50ZWQgb3V0IGluIGRyYWZ0LWlldGYtaWRu
LWNqay0wMS50eHQuDQoNCj5Gb3IgZXhhbXBsZSwgIuaXpeeUoiIgPSAi5pel5LqnIiAgaW4gQ2hp
bmVzZSwgYnV0ICLml6XnlKIiICE9ICLml6XkuqciICBpbiBKYXBhbmVzZS4NCj5JbiBib3RoIGNh
c2VzLCB0aGUgZXhhY3Qgc2FtZSBjb2RlIHBvaW50cyBpbiBVbmljb2RlIGFyZSB1c2VkLiBUaGlz
IGhhcw0KPmJlZW4gcG9pbnRlZCBvdXQgdG9vLCB0aGF0IHNpbmNlIFVuaWNvZGUgZG9lcyBub3Qg
cmVjb2duaXplIHRoZSBkaWZmZXJlbmNlDQo+YmV0d2VlbiBsYW5ndWFnZXMsIGJ1dCBvbmx5IHRo
ZSBkaWZmZXJlbmNlIGJldHdlZW4gc2NyaXB0cy4gSGVuY2UsIGl0IHdpbGwNCj5iZSBkaWZmaWN1
bHQgZm9yIGFueSBVbmljb2RlLWJhc2VkIHN5c3RlbSB0byBmdW5jdGlvbiBvbiBsYW5ndWFnZS1i
YXNlZA0KPmVxdWl2YWxlbmNlIHJ1bGVzLg0KDQoi5pel55SiIiA9ICLml6XkuqciICBpbiBDaGlu
ZXNlIGFuZCAi5pel55SiIiAhPSAi5pel5LqnIiAgaW4gSmFwYW5lc2UuIElmIHdlIGRvbid0IHRh
bGsgYWJvdXQgQ2hpbmVzZSBjaGFyYWN0ZXIgbWFwcGlpbmcgcHJvYmxlbSwgYW5kIHdlIGJlZ2lu
IHRhbGsgYWJvdXQgVU5JQ09ERSBjaGFyYWN0ZXIgbWFwcGluZyBwcm9ibGVtLHRoZSBjb2RlIHBv
aW50ICLnlKIiIC0tICLkuqciIGlzIDEtbiBwcm9ibGVtIGFuZCBpdCdzIG5vdCAxLTEgbWFwcGlu
Zy4gDQoNCj5JIGRvIGFncmVlIHdpdGggeW91IHRoYXQgdGhlIHByb2JsZW0gdGhhdCB5b3UgaGF2
ZSBwb2ludGVkIG91dCBpcyBpbmRlZWQgYQ0KPnJlYWwgcHJvYmxlbSBhbmQgdGhlcmUgaXMgYSBu
ZWVkIGZvciBUQy1TQyBlcXVpdmFsZW5jZSBmb3IgbG9jYXRpbmcNCj5yZXNvdXJjZXMgb24gdGhl
IEludGVybmV0Lg0KDQo+SG93ZXZlciwgaXQgaXMgYSBwcm9ibGVtIHRoYXQgY2Fubm90IGJlIHNv
bHZlZCBieSBhIFVuaWNvZGUtYmFzZWQgRE5TDQo+c29sdXRpb24gd2l0aGluIHRoZSBwYXJhbWV0
ZXJzIG9mIHRoZSBJRE4gV0cgYW5kIGhlbmNlIHRoaXMgbWF5IG5vdCBiZSB0aGUNCj5yaWdodCBw
bGFjZSB0byBhZGRyZXNzIHRoZXNlIGlzc3Vlcy4NCg0KPm1heW5hcmQNCg0KRGVuZyBYaWFuZw0K
MjAwMS41LjMNCg0KDQoNCg0KDQoNCg0K

------=_NextPart_000_003E_01C0D3BD.13075060
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0
Zi04IiBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZT4NCjxNRVRBIGNvbnRlbnQ9Ik1TSFRNTCA1LjAw
LjIwMTQuMjEwIiBuYW1lPUdFTkVSQVRPUj4NCjxTVFlMRT48L1NUWUxFPg0KPC9IRUFEPg0KPEJP
RFk+DQo8RElWPg0KPEhSPg0KDQo8SFI+DQo8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT3lrovkvZMg
c2l6ZT0yPi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0gPC9GT05UPg0KPERJVj48Rk9OVCBm
YWNlPeWui+S9kyBzaXplPTI+RnJvbTogTWF5bmFyZCBLYW5nICZsdDs8QSANCmhyZWY9Im1haWx0
bzptYXluYXJkQHBvYm94Lm9yZy5zZyI+bWF5bmFyZEBwb2JveC5vcmcuc2c8L0E+Jmd0OzwvRk9O
VD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT3lrovkvZMgc2l6ZT0yPlRvOiAmbHQ7PEEgDQpocmVm
PSJtYWlsdG86c3VuQGNubmljLm5ldC5jbiI+c3VuQGNubmljLm5ldC5jbjwvQT4mZ3Q7OyBFcmlj
IEJydW5uZXItV2lsbGlhbXMgDQppbiBQb3J0bGFuZCBNYWluZSAmbHQ7PEEgDQpocmVmPSJtYWls
dG86YnJ1bm5lckBuaWMtbmFhLm5ldCI+YnJ1bm5lckBuaWMtbmFhLm5ldDwvQT4mZ3Q7PC9GT05U
PjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPeWui+S9kyBzaXplPTI+Q2M6ICZsdDs8QSANCmhyZWY9
Im1haWx0bzppZG5Ab3BzLmlldGYub3JnIj5pZG5Ab3BzLmlldGYub3JnPC9BPiZndDs8L0ZPTlQ+
PC9ESVY+DQo8RElWPjxGT05UIGZhY2U95a6L5L2TIHNpemU9Mj5TZW50OiBNb25kYXksIEFwcmls
IDMwLCAyMDAxIDc6NTQgUE08L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGZhY2U95a6L5L2TIHNp
emU9Mj5TdWJqZWN0OiBSZTogW2lkbl0gWm9uZSBydWxlcyAod2FzOiB3ZyBtaWxlc3RvbmVzIA0K
dXBkYXRlKTwvRk9OVD48L0RJVj48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05U
IGZhY2U95a6L5L2TIHNpemU9Mj5Nci4gbWF5bmFyZDo8QlI+VGhhbmtzIGZvciB5b3VyIHN0cmFp
Z2gtb3V0LiBPbiANCnRoZSZuYnNwO3NjaWVudGlmaWMgcm9hZCB0aGVyZSBpcyBubyBkaWZmZXJl
bnQganVzdCB0aGUgcHJvYmxlbSB3aGljaCBpcyB3YWl0aW5nIA0KZm9yIGJlIHNvbHZlZC48QlI+
PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPeWui+S9kyBzaXplPTI+Jmd0O0hpIEd1b25p
YW4sPEJSPjxCUj4mZ3Q7Jmd0OyBmb3IgY2hpbmVzZSB1c2VyLCB0aGUgDQpUQy1TQyBlcXVpdmFs
ZW5jZSBydWxlIGlzIGp1c3QgYWxpa2UgdGhlPEJSPmNhc2UtZm9sZGluZyBydWxlLjxCUj4mZ3Q7
Jmd0OyBJJ2QgDQpsaWtlIHRvIHNob3cgYW4gZXhhbXBsZSBmb2xsb3dlZCB1c2luZyB0aGUgY2Fz
ZS1mb2xkaW5nIA0KcnVsZS48QlI+Jmd0OyZndDs8QlI+Jmd0OyZndDsgdW5kZXIgem9uZSAuQ09N
LCBpZiBtYW5hZ2VyIGRlZmluZXMgdXBwZXIgY2FzZSANCmNoYXJhY3RlcnMgZXF1YWwgdG8gbG93
ZXI8QlI+Y2FzZTxCUj4mZ3Q7Jmd0OyBjaGFyYWN0ZXJzLiB1c2VycyBjb3VsZCBhY2Nlc3MgDQpJ
Qk0nIGRvbWFpbiB3aXRoIGlibS5jb20sIElCbS5jb20sIC4uLiBpbjxCUj5hbnk8QlI+Jmd0OyZn
dDsgDQpjYXNlLjxCUj4uLi48QlI+Jmd0OyZndDsgU28gSSB0aGluayB0aGUgVEMtU0MgZXF1aXZh
bGVuY2UgcnVsZSBTSE9VTEQgYmUgDQpjb25zaXN0ZW50IGFueXdoZXJlIC48QlI+PEJSPiZndDtT
aW5jZSB3ZSdyZSBvbiB0aGlzIHRvcGljIG9mIFRDLVNDIGVxdWl2YWxlbmNlIA0KeWV0IGFnYWlu
LCBJJ2QgbGlrZSB0byBwb2ludDxCUj4mZ3Q7b3V0IHR3byBpc3N1ZXMgdGhhdCBJIHRoaW5rIHdl
IHNob3VsZCBhbGwgDQpjb25zaWRlciBiZWZvcmUgd2UgZ28gZnVydGhlciwgaWY8QlI+Jmd0O3Ro
ZXNlIGhhdmUgbm90IGJlZW4gcmVpdGVyYXRlZCBlbm91Z2ggDQppbiBwcmV2aW91cyBwb3N0aW5n
cyBtYWRlIGJ5IG1vcmU8QlI+Jmd0O3F1YWxpZmllZCBpbmRpdmlkdWFscyB0aGFuIG15c2VsZiBp
biANCnRoZSBwYXN0OjxCUj48QlI+Jmd0OzEpIFRoZSBydWxlc2V0IGZvciBUQy1TQyBlcXVpdmFs
ZW5jZSBpcyBub3QgYSAxLW4gb3Igbi0xIA0KbWFwcGluZyBvZjxCUj4mZ3Q7YWJzdHJhY3QgY2hh
cmFjdGVycywgYXMgcG9pbnRlZCBvdXQgYnkgSGFyYWxkIEFsdmVzdHJhbmQuIEl0IA0KY2FuPEJS
PiZndDtiZSBoaWRlb3VzbHkgY29tcGxleCAoc2VlIGRyYWZ0LWlldGYtaWRuLWNqay0wMS50eHQg
Zm9yIGRldGFpbHMpLCANCndpdGg8QlI+Jmd0O251bWVyb3VzIGxleGljYWwgYW5kIGNvbnRleHR1
YWwgY29uc2lkZXJhdGlvbnMuIEkgYW0gc3VyZSB0aGF0IHlvdSANCndvdWxkPEJSPiZndDtrbm93
IGFib3V0IHRoZSAi5aS05Y+RIiA9ICLpoK3pq64iIGJ1dCAi5Y+R6LSiIiAhPSAi6auu6LKhIiAN
CnByb2JsZW0uPEJSPjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT3lrovkvZMgc2l6ZT0y
PlRDLVNDIGVxdWl2YWxlbmNlIGlzIE5PVCBsZXhpY2FsIGFuZCBjb250ZXh0dWFsIA0KcHJvYmxl
bS5pdCdzIGNvZGUgbWFwcGluZy48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGZhY2U95a6L5L2T
IHNpemU9Mj4xLW4gb3Igbi0xIG1hcHBpbmcgaXMgbWlub3JpdHksdGhlIDEtMSBtYXBwaW5nIGlz
IA0KbWFqb3JpdHkuQWJvdXQgdGhlIHR3byBwYXJ0LHdlIGNhbiB1c2UgJm5ic3A7Jm5ic3A7Jm5i
c3A7IGRpZmZlcmVudCBtZXRob2QgdG8gDQpzb2x2ZS48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05U
IGZhY2U95a6L5L2TIHNpemU9Mj48QlI+Jmd0OzIpIENhc2UtZm9sZGluZyBpcyBhIHNpbXBsZSBj
YW5vbmljYWwgcHJvY2VzcywgDQphbmQgdGhlIGZvbGRpbmcgcnVsZXMgYXJlPEJSPiZndDt0aGUg
c2FtZSwgSSBiZWxpZXZlIChzb21lb25lIHBsZWFzZSBjb3JyZWN0IG1lIA0KaWYgSSdtIHdyb25n
KSwgZm9yIG1vc3Q8QlI+Jmd0O3NjcmlwdHMgd2hpY2ggYXJlIGFibGUgdG8gYmUgcmVwcmVzZW50
ZWQgaW4gQVNDSUkgDQooaS5lLiBFbmdsaXNoLCBTd2FoaWxpLDxCUj4mZ3Q7SGF3YWlpYW4sPEJS
PiZndDtNYWxheSwgZXRjKS48QlI+PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPeWui+S9
kyBzaXplPTI+RGVmaW5pdGVseSxBU0NJSSBqdXN0IGluY2x1ZGUgMjYgbGV0dGVyIGFuZCBpcyBl
YXN5IHRvIA0KZGVhbCB3aXRoLiBCdXQgaXQgaXMgaW4gRE5TLkFuZCBub3csd2UgYXJlIGRpc2N1
c3MgSUROLiBJZiBJRE4gZG8gbm90IHRvIGRlY2lkZSANCnRvIHNvbHZlIG11bHRpbGlndWFsIHBy
b2JsZW0sLi4uPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPeWui+S9kyBzaXplPTI+PC9G
T05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPeWui+S9kyBzaXplPTI+U3VyZSx0aGUg
VEMtU0MgbWFwcGluZyBpcyBkaWZmaWN1bHQuSWYmbmJzcDt3ZSBnaXZlIHVwIA0KanVzdCZuYnNw
O2JlY2F1c2U8L0ZPTlQ+Jm5ic3A7PEZPTlQgZmFjZT3lrovkvZMgc2l6ZT0yPmRpZmZpY3VsdCxp
dCdzIG5vdCBzY2llbnRpZmljIA0KYXR0aXR1ZGUuPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBm
YWNlPeWui+S9kyBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPeWu
i+S9kyBzaXplPTI+Jmd0O0ZvciBleGFtcGxlLCB0aGVyZSBpcyBubyBkZWJhdGUgYXMgdG8gd2hl
dGhlciANCiJDQVQiIG9yICJjYXQiIG9yICJjQXQiPEJSPiZndDtyZWZlcnMgdG8gdGhlIHNhbWUg
dGhpbmcgKGluIEVuZ2xpc2gpLCBvciB3aGV0aGVyIA0KIktVQ0hJTkciIG9yICJrdWNoaW5nIiBv
cjxCUj4mZ3Q7ImtVY2hpTkciIHJlZmVycyB0byB0aGUgc2FtZSB0aGluZyAoImNhdCIgaW4gDQpN
YWxheSkuPEJSPjwvRk9OVD48Rk9OVCBmYWNlPeWui+S9kyBzaXplPTI+PEJSPlRoZXJlIGlzIGFs
c28gbm8gZGViYXRlIGFzIHRvIHdoZXRoZXIgDQoi5pel55SiIiA9ICLml6XkuqciJm5ic3A7IGlu
IENoaW5lc2UgcmVmZXJzIHRvIHRoZSBzYW1lIHRoaW5nLiA8L0ZPTlQ+PC9ESVY+DQo8RElWPjxG
T05UIGZhY2U95a6L5L2TIHNpemU9Mj4mbmJzcDs8L0RJVj48L0ZPTlQ+DQo8RElWPjxGT05UIGZh
Y2U95a6L5L2TIHNpemU9Mj4mZ3Q7SG93ZXZlciwgSGFuIGNoYXJhY3RlciBjYW5vbmljYWxpemF0
aW9uIGRvZXMgbm90IA0KZm9sbG93IHRoZSBzYW1lIHJ1bGVzLiBIYW48QlI+Jmd0O2NoYXJhY3Rl
cnMgdXNlZCBpbiBDaGluZXNlLCBKYXBhbmVzZSBhbmQgDQpLb3JlYW4gaGF2ZSBkaWZmZXJlbnQg
ZXF1aXZhbGVuY2U8QlI+Jmd0O3J1bGVzLiBUaGlzIGlzIGFsc28gcG9pbnRlZCBvdXQgaW4gDQpk
cmFmdC1pZXRmLWlkbi1jamstMDEudHh0LjxCUj48QlI+Jmd0O0ZvciBleGFtcGxlLCAi5pel55Si
IiA9ICLml6XkuqciJm5ic3A7IGluIENoaW5lc2UsIA0KYnV0ICLml6XnlKIiICE9ICLml6Xkuqci
Jm5ic3A7IGluIEphcGFuZXNlLjxCUj4mZ3Q7SW4gYm90aCBjYXNlcywgdGhlIGV4YWN0IHNhbWUg
Y29kZSANCnBvaW50cyBpbiBVbmljb2RlIGFyZSB1c2VkLiBUaGlzIGhhczxCUj4mZ3Q7YmVlbiBw
b2ludGVkIG91dCB0b28sIHRoYXQgc2luY2UgDQpVbmljb2RlIGRvZXMgbm90IHJlY29nbml6ZSB0
aGUgZGlmZmVyZW5jZTxCUj4mZ3Q7YmV0d2VlbiBsYW5ndWFnZXMsIGJ1dCBvbmx5IHRoZSANCmRp
ZmZlcmVuY2UgYmV0d2VlbiBzY3JpcHRzLiBIZW5jZSwgaXQgd2lsbDxCUj4mZ3Q7YmUgZGlmZmlj
dWx0IGZvciBhbnkgDQpVbmljb2RlLWJhc2VkIHN5c3RlbSB0byBmdW5jdGlvbiBvbiBsYW5ndWFn
ZS1iYXNlZDxCUj4mZ3Q7ZXF1aXZhbGVuY2UgDQpydWxlcy48QlI+PC9GT05UPjwvRElWPg0KPERJ
Vj48Rk9OVCBmYWNlPeWui+S9kyBzaXplPTI+IuaXpeeUoiIgPSAi5pel5LqnIiZuYnNwOyBpbiBD
aGluZXNlIGFuZCAi5pel55SiIiAhPSAi5pel5LqnIiZuYnNwOyBpbiANCkphcGFuZXNlLiBJZiB3
ZSBkb24ndCB0YWxrIGFib3V0IENoaW5lc2UgY2hhcmFjdGVyIG1hcHBpaW5nIHByb2JsZW0sIGFu
ZCB3ZSANCmJlZ2luIHRhbGsgYWJvdXQgVU5JQ09ERSBjaGFyYWN0ZXIgbWFwcGluZyBwcm9ibGVt
LHRoZSBjb2RlIHBvaW50ICLnlKIiJm5ic3A7LS0gDQoi5LqnIiBpcyAxLW4gcHJvYmxlbSBhbmQg
aXQncyBub3QgMS0xIG1hcHBpbmcuIDwvRElWPjwvRk9OVD4NCjxESVY+PEZPTlQgZmFjZT3lrovk
vZMgc2l6ZT0yPjxCUj4mZ3Q7SSBkbyBhZ3JlZSB3aXRoIHlvdSB0aGF0IHRoZSBwcm9ibGVtIHRo
YXQgeW91IA0KaGF2ZSBwb2ludGVkIG91dCBpcyBpbmRlZWQgYTxCUj4mZ3Q7cmVhbCBwcm9ibGVt
IGFuZCB0aGVyZSBpcyBhIG5lZWQgZm9yIFRDLVNDIA0KZXF1aXZhbGVuY2UgZm9yIGxvY2F0aW5n
PEJSPiZndDtyZXNvdXJjZXMgb24gdGhlIEludGVybmV0LjxCUj48QlI+Jmd0O0hvd2V2ZXIsIA0K
aXQgaXMgYSBwcm9ibGVtIHRoYXQgY2Fubm90IGJlIHNvbHZlZCBieSBhIFVuaWNvZGUtYmFzZWQg
RE5TPEJSPiZndDtzb2x1dGlvbiANCndpdGhpbiB0aGUgcGFyYW1ldGVycyBvZiB0aGUgSUROIFdH
IGFuZCBoZW5jZSB0aGlzIG1heSBub3QgYmUgdGhlPEJSPiZndDtyaWdodCANCnBsYWNlIHRvIGFk
ZHJlc3MgdGhlc2UgaXNzdWVzLjxCUj48QlI+Jmd0O21heW5hcmQ8QlI+PC9GT05UPjwvRElWPg0K
PERJVj48Rk9OVCBmYWNlPeWui+S9kyBzaXplPTI+RGVuZyBYaWFuZzwvRk9OVD48L0RJVj4NCjxE
SVY+PEZPTlQgZmFjZT3lrovkvZMgc2l6ZT0yPjIwMDEuNS4zPC9GT05UPjwvRElWPg0KPERJVj48
Rk9OVCBmYWNlPeWui+S9kyBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBm
YWNlPeWui+S9kyBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPeWu
i+S9kyBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPeWui+S9kyBz
aXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPeWui+S9kyBzaXplPTI+
Jm5ic3A7PC9ESVY+PC9GT05UPg0KPERJVj48Rk9OVCBmYWNlPeWui+S9kyBzaXplPTI+PEJSPiZu
YnNwOzwvRElWPjwvRk9OVD48L0JPRFk+PC9IVE1MPg0K

------=_NextPart_000_003E_01C0D3BD.13075060--




From owner-idn@ops.ietf.org  Wed May  2 23:20:55 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA00991
	for <idn-archive@lists.ietf.org>; Wed, 2 May 2001 23:20:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14v9Tr-000H9i-00
	for idn-data@psg.com; Wed, 02 May 2001 20:08:39 -0700
Received: from [159.226.6.42] (helo=pier.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14v9Tq-000H9K-00
	for idn@ops.ietf.org; Wed, 02 May 2001 20:08:38 -0700
Received: from deng ([159.226.7.68]) by pier.cnnic.net.cn
          (Netscape Mail Server v2.02) with SMTP id AAA18191;
          Thu, 3 May 2001 11:10:20 +0800
Message-ID: <006401c0d37d$9ff9e0e0$4407e29f@cnnic.net.cn>
Reply-To: =?iso-8859-1?B?tcvP6A==?= <deng@cnnic.net.cn>
From: deng@pier.cnnic.net.cn (deng)
To: <idn@ops.ietf.org>, "Adam M. Costello" <amc@cs.berkeley.edu>
References: <200104291408.f3TE8Ac11734@nic-naa.net> <3AED3C39.CA9E5BBB@cnnic.net.cn> <20010430225035.A25647@arwen.cs.berkeley.edu>
Subject: Re: [idn] Zone rules (was: wg milestones update)
Date: Thu, 3 May 2001 11:03:27 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by ietf.org id XAA00991


>Adam wrote:
 
> The second difference is that case equivalence is intuitive.  Any
> person who knows the letter "a" also knows that "A" and "a" are the
> same letter (even if you put diacritics on them, and even when they
> appear in words of an unknown language).  I don't think this is true
> of traditional/simplified Chinese characters.  If I'm not mistaken,
> many people from China cannot read many of the traditional characters,
> and many people from Taiwan, Hong Kong, etc. cannot read many of the
> simplified characters.  And as others have pointed out, the equivalence
> holds in Mandarin but not in Japanese (and I would guess not in
> Cantonese and other Chinese languages, but I don't know).
> 

I can not read some traditional Chinese characters and some simplified Chinese characters,but I want to register some Chinese domain name which include traditional or simplified Chinese characters. These are two different problems.

Deng Xiang
2001.5.3



> 


From owner-idn@ops.ietf.org  Wed May  2 23:31:16 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA01334
	for <idn-archive@lists.ietf.org>; Wed, 2 May 2001 23:31:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14v9d6-000HkS-00
	for idn-data@psg.com; Wed, 02 May 2001 20:18:12 -0700
Received: from [159.226.6.42] (helo=pier.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14v9d5-000HkK-00
	for idn@ops.ietf.org; Wed, 02 May 2001 20:18:11 -0700
Received: from deng ([159.226.7.68]) by pier.cnnic.net.cn
          (Netscape Mail Server v2.02) with SMTP id AAA18220;
          Thu, 3 May 2001 11:19:50 +0800
Message-ID: <006b01c0d37e$f3ba8080$4407e29f@cnnic.net.cn>
Reply-To: =?utf-8?B?6YKT57+U?= <deng@cnnic.net.cn>
From: deng@pier.cnnic.net.cn (deng)
To: "Maynard Kang" <maynard@pobox.org.sg>,
        "James Seng/Personal" <jseng@pobox.org.sg>,
        "Tan Tin Wee" <tinwee@bic.nus.edu.sg>
Cc: <idn@ops.ietf.org>
References: <3AEE3769.7DA077F@bic.nus.edu.sg> <005401c0d1ff$2323ac60$0201000a@jamessonyvaio> <006101c0d23d$a1d47fb0$0200000a@maynardibm>
Subject: Re: Re: [idn] Zone rules (was: wg milestones update)]
Date: Thu, 3 May 2001 11:12:57 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by ietf.org id XAA01334

>maynard wrote:

>Although one Chinese character may map to a two or more Chinese character
>phrase, that is not strictly a TC-SC equivalence rule, but rather just a
>relationship between synonyms (e.g. "å½•" = "é�’"). The semantic meaning may be
>equivalent, but the pronunciation and number of syllables would be
>different (e.g. in English, "car" = "automobile").

In DNS,there is no meaning. For example,if user register "IBM" and if there isn't a company named "IBM",NOBODY know what meaning the user want to express.It's domain name and not human language.

Deng Xiang
2001.5.3




From owner-idn@ops.ietf.org  Thu May  3 00:12:19 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA01827
	for <idn-archive@lists.ietf.org>; Thu, 3 May 2001 00:12:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vAIB-000KAR-00
	for idn-data@psg.com; Wed, 02 May 2001 21:00:39 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14vAIA-000KA5-00
	for idn@ops.ietf.org; Wed, 02 May 2001 21:00:38 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id AAA17707;
        Thu, 3 May 2001 00:00:35 -0400 (EDT)
Message-Id: <200105030400.AAA17707@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Adam M. Costello" <amc@cs.berkeley.edu>
cc: idn@ops.ietf.org
Subject: Re: [idn] Alternative Solutions 
In-reply-to: Your message of "Thu, 03 May 2001 01:21:33 -0000."
             <20010503012132.B15150@arwen.cs.berkeley.edu> 
Date: Thu, 03 May 2001 00:00:35 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> What started this thread was the possibility that patents might prevent
> us from using an ACE. 

We have to use some sort of ASCII name if we expect any IDN to be usable 
in an existing application, because those applications can only deal 
with ASCII names.  

I suppose it doesn't absolutely have to be an algorithmic mapping 
between the ASCII name and the native IDN, but I really don't like 
the idea of doing the mapping on the server.  I see two problems 
with doing the mapping on the server (in addition to those that 
you've already identified):

1. it's difficult to do the mapping in a way that is guaranteed to
produce consistent results between applications using the native IDN
and applications using the ASCII form of the name.

(without this guarantee, when people upgrade to IDN-aware applications
lookups of the same names that they previously used will sometimes 
produce different results - and fail at different times - than before)

2. (sort of like #1) it's difficult to do the mapping in such a way
that the server responsible for ascii->native mapping is the same as 
that for native->ascii mapping.

(without this guarantee, we open up an opportunity for there to be
different authoritative servers - and thus conflicting authorities -
for names that should be equivalent)

however if a solution can satisfy those two constraints, it might 
be worth a try. 

--

one way to do this might be to define a new RR type that specified
that a single ASCII label and a single IDN label (both relative 
to the current zone) were equivalent.  for instance,

#####	IEQ	xyzzy

would specify to the DNS server that (native) label ##### was
equivalent to ASCII label xyzzy.

labels in IEQ records could contain suffixes (and these might
be needed for glue) but only if left and right side had the 
same suffix up to the least significant label.  Thus

#####.a.b	IEQ	xyzzy.a.b

would be legal, but

#####.a.b	IEQ	xyzzy.c.d

would not.

if such a RR appeared in the example.com zone, the servers for
that zone would know to answer queries (regardless of query type)
for #####.example.com identically to queries for xyzzy.example.com.   
in either case one or more IEQ records could be returned as additional 
information, allowing the caller to discover the mapping between the 
native IDN and the ASCII equivalent.

IEQ RRs could either be explicitly specified on a per-zone 
basis or automatically generated by the master server.

Keith



From owner-idn@ops.ietf.org  Thu May  3 07:22:41 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA18733
	for <idn-archive@lists.ietf.org>; Thu, 3 May 2001 07:22:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vGlC-000I0L-00
	for idn-data@psg.com; Thu, 03 May 2001 03:55:02 -0700
Received: from ns.jck.com ([209.187.148.211] helo=A4.JCK.COM)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14vGlB-000I0D-00
	for idn@ops.ietf.org; Thu, 03 May 2001 03:55:01 -0700
Received: from P2 ("port 1254"@[209.187.148.217])
 by a4.jck.com (PMDF V6.0-24 #44844) with ESMTP id <0GCR00BDSABNR9@a4.jck.com>
 for idn@ops.ietf.org; Thu, 03 May 2001 06:55:00 -0400 (EDT)
Date: Thu, 03 May 2001 06:54:58 -0400
From: John C Klensin <klensin@jck.com>
Subject: Re: [idn] Alternative Solutions
In-reply-to: <200105030155.SAA11186@birdie.sybase.com>
To: Kenneth Whistler <kenw@sybase.com>
Cc: idn@ops.ietf.org
Message-id: <1030420740.988872898@P2>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.8 (Win32)
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, 02 May, 2001 18:55 -0700 Kenneth Whistler
<kenw@sybase.com> wrote:

>> First, let's make sure we all mean the same thing when we say
>> "ACE". When I say "ACE", I mean a reversible algorithmic
>> mapping from Unicode strings to LDH strings.
>> 
>> What started this thread was the possibility that patents
>> might prevent us from using an ACE.
> 
> Has it actually been determined that the WALID patent covers
> *all* possible "reversible algorithmic mappings from Unicode
> strings to LDH strings"? That seems like a stretch to me.

As I understand the patent claims, and the claims about them,
there is no practical way to "actually determine that" other
than to try to litigate (and invalidate) the patent.  But, from
reading the correspondence with Walid, and based on what I've
been told several times, the main threat is to IDNA, not to the
set of ACE proposals themselves.

In any event, while I hope we aren't forced to go there (whether
any of those ideas are good ones is another question),
draft-ietf-idn-dumb-00 is an attempt to drive a stake in the
ground relative to some ACE methods that are certainly
unencumbered and/or extremely defensible.  Summary for those who
haven't looked at it (those who have, or who have otherwise
gotten the point, can stop reading here):

* The use of simple "hexification" produces an ACE, is extremely
old in terms of prior art use.  When 32-bit machines and octets
started to become common, they were considered an obvious
extension from expressing characters, and portions of
then-common 18 and 36 bit machine words, in octal, which goes
back even further.  Hex and octal representatives have been
applied in enough different areas that the applicability of the
latter to the DNS should be obvious to an idiot, much less a
skilled practitioner.

* A reference to a character in a code table by its row and
column position, and the joining (catenation) of row and column
(or column and row) positions together, go back at least to the
first BCD table I saw and probably longer.  Such a reference
also generates an ACE, or several different ones, some of which
are slightly different from the hexification ACE.   And, again,
these have been widely enough applied that applicability to the
DNS would be quite obvious (as would be simply inserting a
string of the form "UxNNNN", another ACE.

* Taking the simple binary representation of a code point, or
some other value, from some particular character set coding and
representing it by conversion into a different number base,
where the base is considerably larger than 10, has been long and
widely used in the Internet and elsewhere.   If Roman alphabetic
characters from the ASCII alphanumeric set are used to represent
the "digits" above nine, the mechanisms form ACEs.   The Base64
coding of MIME was, as far as I know, the first of these to be
widely deployed.  But it predates any patent that might be filed
today by a safe margin and, even then, was by no means the first
of these codings (e.g., if I recall, a slightly different Base
64 encoding was used in the first version of Privacy Enhanced
Mail).  Again, the range of applications have been broad enough
that application to the DNS is obvious.

* Taking binary strings, compressing them using a conventional
method (e.g., dictionaries or string length), and then encoding
the result by hexification or coding to some larger base using
letters and/or ASCII symbols also produces an ACE.  And the
sequence of operations is also historically well-known and its
application to a new area should be obvious to anyone familiar
with even a small fraction of those applications.

In Internet time first two approaches data from roughly the time
dinosaurs roamed the earth and the others aren't much more
recent.  And there are more of these, enough to give the WG a
very broad range of choices on the ACE front.

Whether they are the Right Thing to do is another matter.

    john




From owner-idn@ops.ietf.org  Thu May  3 11:54:24 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA28041
	for <idn-archive@lists.ietf.org>; Thu, 3 May 2001 11:54:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vL2M-0007sZ-00
	for idn-data@psg.com; Thu, 03 May 2001 08:29:02 -0700
Received: from web13306.mail.yahoo.com ([216.136.175.42])
	by psg.com with smtp (Exim 3.16 #1)
	id 14vL2L-0007sT-00
	for idn@ops.ietf.org; Thu, 03 May 2001 08:29:01 -0700
Message-ID: <20010503152859.12957.qmail@web13306.mail.yahoo.com>
Received: from [207.61.23.193] by web13306.mail.yahoo.com; Thu, 03 May 2001 08:28:59 PDT
Date: Thu, 3 May 2001 08:28:59 -0700 (PDT)
From: "Sean X. Zhang" <sean_xzhang@yahoo.com>
Subject: Re: [idn] Alternative Solutions
To: Kenneth Whistler <kenw@sybase.com>, idn@ops.ietf.org
Cc: kenw@sybase.com
In-Reply-To: <200105030155.SAA11186@birdie.sybase.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--- Kenneth Whistler <kenw@sybase.com> wrote:
> > First, let's make sure we all mean the same thing when we say "ACE".
> > When I say "ACE", I mean a reversible algorithmic mapping from Unicode
> > strings to LDH strings.
> > 
> > What started this thread was the possibility that patents might prevent
> > us from using an ACE.
> 
> Has it actually been determined that the WALID patent covers *all*
> possible "reversible algorithmic mappings from Unicode strings
> to LDH strings"? That seems like a stretch to me.

What can be "actually determined" has already been commented upon by John.

[...]

> 
> Or has WALID actually gotten a patent on a generic concept without
> actually specifying a particular technique to accomplish it??
> 
> --Ken

He claimed only "a method". But it appears to be a very broad one.

From the US Patent Office's web site, www.uspto.gov, you can get the 
text of the 6,182,148 patent. Its claim 1 states (with [my comments]
in square brackets):

       1. A method of converting an internet international domain name 
          [that's an IDN] to an RFC1035 compliant format [or, an LDH string],
          where the international domain name includes non-English characters
          which are RFC1035 non-compliant, the method comprising [i.e.,
          requires at least the following]: 
              intercepting the international domain name, where the
                   intercepting is transparent to the user 
                   [this appears to be the role of the "DNS proxy" 
                   discussed at http://www.apng.org/idns/]; 
              transforming the international domain name to an RFC1035
                   compliant domain name 
                   [convert the IDN to an LDH string in any way you want,
                   reversible or not; no, a particular technique is not
                   specified for this step, and yes, this step does seem
                   to correspond to a generic concept; 
                   following steps 1, 2, and part of step 3 discussed at
                   http://www.apng.org/idns/ might be one particular
                   technique to accomplish this]; 
             automatically generating a redirector string 
                   [this is probably the string "ar.i18n.net" referred to 
                   in the "Detailed Description" section, in association 
                   with Fig. 2 and numeral "130"; if so, that would 
                   correspond to "idns.apng.org" in the "Note" section 
                   on www.apng.org/idns and the appended string in step 3,
                   above] 
                which includes information for resolving 
                   [cannot tell what information is required; maybe simply
                   another way of saying that the "redirector string" cannot 
                   be arbitrary and must be something like the ones above]
                the RFC1035 compliant domain name; and 
             appending the redirector string to the RFC1035 compliant 
                   do main [appears to be a typo; should be "domain"] name
                   [if above interpretation of "redirector string" is
                   correct, this would be the second half of step 3, above].

If my understanding of the claim language, the technology and the terminology
is correct, then yes, he seems to have a patent covering the generic concept
of converting IDNs to LDH strings. In claim 1, nothing's said about reversible
algorithmic mappings, though it seems to be broad enough to cover the concept.
In particular, his claim 1 would seem to cover the method discussed at
http://www.apng.org/idns/. 

Maybe someone could look at other claims or take a closer look at claim 1 to
see what kind of patent he has obtained?

--
Sean

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/



From owner-idn@ops.ietf.org  Thu May  3 13:13:51 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA00599
	for <idn-archive@lists.ietf.org>; Thu, 3 May 2001 13:13:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vMDI-000C7R-00
	for idn-data@psg.com; Thu, 03 May 2001 09:44:24 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14vMDH-000C6m-00
	for idn@ops.ietf.org; Thu, 03 May 2001 09:44:23 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id MAA19289;
        Thu, 3 May 2001 12:43:40 -0400 (EDT)
Message-Id: <200105031643.MAA19289@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Sean X. Zhang" <sean_xzhang@yahoo.com>
cc: Kenneth Whistler <kenw@sybase.com>, idn@ops.ietf.org
Subject: Re: [idn] Alternative Solutions 
In-reply-to: Your message of "Thu, 03 May 2001 08:28:59 PDT."
             <20010503152859.12957.qmail@web13306.mail.yahoo.com> 
Date: Thu, 03 May 2001 12:43:40 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > 
> > Or has WALID actually gotten a patent on a generic concept without
> > actually specifying a particular technique to accomplish it??
> > 
> > --Ken
> 
> He claimed only "a method". But it appears to be a very broad one.
> 
> From the US Patent Office's web site, www.uspto.gov, you can get the 
> text of the 6,182,148 patent. Its claim 1 states (with [my comments]
> in square brackets):
> 
>        1. A method of converting an internet international domain name 
>           [that's an IDN] to an RFC1035 compliant format [or, an LDH string],
>           where the international domain name includes non-English characters
>           which are RFC1035 non-compliant, 

interesting.  are any characters in UTF-8 "RFC1035 non-compliant"?
It appears that RFC 1035 anticipated the need to store non-ASCII characters
by stating that "attempts to store domain names in 7-bit ASCII
or use of special bytes to terminate labels, etc., should be avoided."
(section 2.3.3, first paragraph)

> the method comprising [i.e.,
>           requires at least the following]: 
>               intercepting the international domain name, where the
>                    intercepting is transparent to the user 
>                    [this appears to be the role of the "DNS proxy" 
>                    discussed at http://www.apng.org/idns/]; 
>               transforming the international domain name to an RFC1035
>                    compliant domain name 
>                    [convert the IDN to an LDH string in any way you want,
>                    reversible or not; no, a particular technique is not
>                    specified for this step, and yes, this step does seem
>                    to correspond to a generic concept; 
>                    following steps 1, 2, and part of step 3 discussed at
>                    http://www.apng.org/idns/ might be one particular
>                    technique to accomplish this]; 
>              automatically generating a redirector string 
>                    [this is probably the string "ar.i18n.net" referred to 
>                    in the "Detailed Description" section, in association 
>                    with Fig. 2 and numeral "130"; if so, that would 
>                    correspond to "idns.apng.org" in the "Note" section 
>                    on www.apng.org/idns and the appended string in step 3,
>                    above] 
>                 which includes information for resolving 
>                    [cannot tell what information is required; maybe simply
>                    another way of saying that the "redirector string" cannot 
>                    be arbitrary and must be something like the ones above]
>                 the RFC1035 compliant domain name; and 
>              appending the redirector string to the RFC1035 compliant 
>                    do main [appears to be a typo; should be "domain"] name
>                    [if above interpretation of "redirector string" is
>                    correct, this would be the second half of step 3, above].
> 
> If my understanding of the claim language, the technology and the terminology
> is correct, then yes, he seems to have a patent covering the generic concept
> of converting IDNs to LDH strings. 

to me, this particular claim doesn't say this at all.  

1. 'intercepting' the domain name seems to imply some sort of proxy 
(something interposed between existing components rather than having 
the components changed to explicitly support IDNs).  

2. an RFC1035 compliant domain name appears to be any string of octets 
less than 256 octets, not beginning with '.', without consecutive '.'s,
and with the labels between the '.'s less than 64 characters in length.  
with the possible exception of length restrictions on labels, ACE isn't 
needed to make a domain name RFC 1035 compliant, it's needed to make the 
domain name compliant with other protocols that expect ASCII.

3. there have been numerous proposals here that don't need any kind
of redirect - the IDN components are looked up directly rather than
via any kind of referral, and IDN lookups are made relative to the 
DNS root rather than relative to any string that is appended to a 
transformed IDN.

maybe it really would be worthwhile for a group of people to pick apart
those claims and write up an argument as to why they do or do not apply 
to one or more of the proposals on the table.  according to 2026, IETF 
as an organization cannot make any statement on the validity of a patent,
but I don't see why one or more individuals cannot try to write up an
persuasive argument and publish it as an I-D.  (if they could recruit
the assistance of some patent attorneys while doing so, so much the 
better). perhaps the document could even be published as Informational,
in due time, after appropriate review by IETF counsel.

Keith



From owner-idn@ops.ietf.org  Thu May  3 13:34:26 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA01311
	for <idn-archive@lists.ietf.org>; Thu, 3 May 2001 13:34:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vMoZ-000EPA-00
	for idn-data@psg.com; Thu, 03 May 2001 10:22:55 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14vMoY-000EP4-00
	for idn@ops.ietf.org; Thu, 03 May 2001 10:22:54 -0700
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id KAA30133
	for <idn@ops.ietf.org>; Thu, 3 May 2001 10:22:53 -0700
Message-Id: <5.1.0.14.2.20010503101846.01e9cc50@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 03 May 2001 10:20:07 -0700
To: idn@ops.ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] Alternative Solutions
In-Reply-To: <1030420740.988872898@P2>
References: <200105030155.SAA11186@birdie.sybase.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 03:54 AM 5/3/2001, John C Klensin wrote:
>* The use of simple "hexification" produces an ACE, is extremely
>old in terms of prior art use.  When 32-bit machines and octets


20+ years ago, we fondly -- if irreverently -- referred to the technique as 
"half-ascii"...

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 May  3 18:06:35 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA11513
	for <idn-archive@lists.ietf.org>; Thu, 3 May 2001 18:06:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vQvZ-0003z8-00
	for idn-data@psg.com; Thu, 03 May 2001 14:46:25 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14vQvY-0003z2-00
	for idn@ops.ietf.org; Thu, 03 May 2001 14:46:24 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 14vQvU-00052E-00; Thu, 03 May 2001 14:46:20 -0700
Date: Thu, 3 May 2001 21:46:20 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Alternative Solutions
Message-ID: <20010503214620.B18888@arwen.cs.berkeley.edu>
References: <20010503152859.12957.qmail@web13306.mail.yahoo.com> <200105031643.MAA19289@astro.cs.utk.edu> <200105030155.SAA11186@birdie.sybase.com> <20010503152859.12957.qmail@web13306.mail.yahoo.com> <200105030155.SAA11186@birdie.sybase.com> <1030420740.988872898@P2> <20010503012132.B15150@arwen.cs.berkeley.edu> <200105030400.AAA17707@astro.cs.utk.edu> <200105030155.SAA11186@birdie.sybase.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <200105030155.SAA11186@birdie.sybase.com>; from kenw@sybase.com on Wed, May 02, 2001 at 06:55:06PM -0700
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Kenneth Whistler <kenw@sybase.com> wrote:

> Has anyone considered trying bit and byte transforms directly on the
> UTF-8 encoding form, rather than on the Unicode code point?

My intuition is that this would result in much longer encodings than
any of the ACEs considered so far.  UTF-8 is already pretty bad for
non-Latin languages.

> How about some deterministic and quick compression run on the UTF-16
> encoding form of a Unicode string, and *then* rearranging the
> resulting bytes to accomodate ASCII restrictions?

You have just described RACE and LACE.

> Or has WALID actually gotten a patent on a generic concept without
> actually specifying a particular technique to accomplish it??

That's my impression.

Keith Moore <moore@cs.utk.edu> wrote:

> one way to do this might be to define a new RR type that specified
> that a single ASCII label and a single IDN label (both relative to the
> current zone) were equivalent.

In other words, instead of doing one lookup to map ####.%%%%.org to
foo.bar.org, you would first look up %%%%.org to get bar.org, then look
up ####.bar.org to get foo.bar.org.  This might be a good idea.  It
looks like more steps, but the single lookup of ####.%%%%.org can be
just as many steps in practice.

I still think you need two new RR types, one to map ####.bar.org to
foo.bar.org, and one to map foo.bar.org to ####.bar.org.  And there's
nothing to stop the administrator of the *.bar.org zone from making
those two pointers inconsistent, just like there's nothing to stop
people from making A and PTR records inconsistent today.  But no one can
usurp your authority.  If you want your own domains to be well-behaved,
then you make your pointers consistent.

You can encourage consistency, but there's no way to guarantee it.  For
example, some name servers today return different responses depending
on the source address of the query.  The administrator of a zone can do
anything they want with that zone.

John C Klensin <klensin@jck.com> wrote:

> But, from reading the correspondence with Walid, and based on what
> I've been told several times, the main threat is to IDNA, not to the
> set of ACE proposals themselves.

That's my impression as well, in which case it doesn't matter whether
we use an old dumb ACE or a new clever ACE, the problem is the whole
IDNA approach.  And maybe the idea of using a DNS lookup instead of an
algorithm to do the transformation still doesn't go far enough to escape
the scope of the patent.  I don't know.

Keith Moore <moore@cs.utk.edu> wrote:

> are any characters in UTF-8 "RFC1035 non-compliant"?

This phrase undoubtedly intendsd to refer to section 2.3.1 "Preferred
name syntax", which says:

    However, when assigning a domain name for an object, the prudent
    user will select a name which satisfies both the rules of the domain
    system and any existing rules for the object, whether these rules
    are published or implied by existing programs.

    For example, when naming a mail domain, the user should satisfy both
    the rules of this memo and those in RFC-822.  When creating a new
    host name, the old rules for HOSTS.TXT should be followed.  This
    avoids problems when old software is converted to use domain names.

    The following syntax will result in fewer problems with many
    applications that use domain names (e.g., mail, TELNET).

The BNF that follows describes the syntax, but that syntax was relaxed
by RFC 1123 to allow labels to start with digits.

> with the possible exception of length restrictions on labels, ACE
> isn't needed to make a domain name RFC 1035 compliant, it's needed to
> make the domain name compliant with other protocols that expect ASCII.

Right, the patent claim doesn't quite say what it means.  But I think
judges usually try to interpret language "reasonably" rather than
literally.

AMC



From owner-idn@ops.ietf.org  Thu May  3 23:15:00 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA19702
	for <idn-archive@lists.ietf.org>; Thu, 3 May 2001 23:14:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vVcw-000LjO-00
	for idn-data@psg.com; Thu, 03 May 2001 19:47:30 -0700
From: Tan Tin Wee <tinwee@bic.nus.edu.sg>
X-Mailer: Mozilla 4.73 [en] (Win98; I)
To: "Sean X. Zhang" <sean_xzhang@yahoo.com>
CC: Kenneth Whistler <kenw@sybase.com>, idn@ops.ietf.org
Subject: Re: [idn] Alternative Solutions
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E14vVcw-000LjO-00@psg.com>
Date: Thu, 03 May 2001 19:47:30 -0700

Speaking personally, I  think these aspects of the patent discussed
below as being covered by WALID Patent already constitutes prior art,
which the APNG commissioned the IDNS project back in 1998,
and how the Patent Office could have issued the patent ... sigh...
>... and to set aside this patent as Dave Crocker pointed out or worse,
contest it, would be subject to the vagaries of the legal system in
US... more
sighs.
I don't understand the USPTO!

tw



"Sean X. Zhang" wrote:
>
> --- Kenneth Whistler <kenw@sybase.com> wrote:
> > > First, let's make sure we all mean the same thing when we say
"ACE".
> > > When I say "ACE", I mean a reversible algorithmic mapping from
Unicode
> > > strings to LDH strings.
> > >
> > > What started this thread was the possibility that patents might
prevent
> > > us from using an ACE.
> >
> > Has it actually been determined that the WALID patent covers *all*
> > possible "reversible algorithmic mappings from Unicode strings
> > to LDH strings"? That seems like a stretch to me.
>
> What can be "actually determined" has already been commented upon by
John.
>
> [...]
>
> >
> > Or has WALID actually gotten a patent on a generic concept without
> > actually specifying a particular technique to accomplish it??
> >
> > --Ken
>
> He claimed only "a method". But it appears to be a very broad one.
>
> >From the US Patent Office's web site, www.uspto.gov, you can get the
> text of the 6,182,148 patent. Its claim 1 states (with [my comments]
> in square brackets):
>
>        1. A method of converting an internet international domain name
>           [that's an IDN] to an RFC1035 compliant format [or, an LDH
string],
>           where the international domain name includes non-English
characters
>           which are RFC1035 non-compliant, the method comprising
[i.e.,
>           requires at least the following]:
>               intercepting the international domain name, where the
>                    intercepting is transparent to the user
>                    [this appears to be the role of the "DNS proxy"
>                    discussed at http://www.apng.org/idns/];
>               transforming the international domain name to an RFC1035
>                    compliant domain name
>                    [convert the IDN to an LDH string in any way you
want,
>                    reversible or not; no, a particular technique is
not
>                    specified for this step, and yes, this step does
seem
>                    to correspond to a generic concept;
>                    following steps 1, 2, and part of step 3 discussed
at
>                    http://www.apng.org/idns/ might be one particular
>                    technique to accomplish this];
>              automatically generating a redirector string
>                    [this is probably the string "ar.i18n.net" referred
to
>                    in the "Detailed Description" section, in
association
>                    with Fig. 2 and numeral "130"; if so, that would
>                    correspond to "idns.apng.org" in the "Note" section
>                    on www.apng.org/idns and the appended string in
step 3,
>                    above]
>                 which includes information for resolving
>                    [cannot tell what information is required; maybe
simply
>                    another way of saying that the "redirector string"
cannot
>                    be arbitrary and must be something like the ones
above]
>                 the RFC1035 compliant domain name; and
>              appending the redirector string to the RFC1035 compliant
>                    do main [appears to be a typo; should be "domain"]
name
>                    [if above interpretation of "redirector string" is
>                    correct, this would be the second half of step 3,
above].
>
> If my understanding of the claim language, the technology and the
terminology
> is correct, then yes, he seems to have a patent covering the generic
concept
> of converting IDNs to LDH strings. In claim 1, nothing's said about
reversible
> algorithmic mappings, though it seems to be broad enough to cover the
concept.
> In particular, his claim 1 would seem to cover the method discussed at
> http://www.apng.org/idns/.
>
> Maybe someone could look at other claims or take a closer look at
claim 1 to
> see what kind of patent he has obtained?
>
> --
> Sean
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - buy the things you want at great prices
> http://auctions.yahoo.com/





From owner-idn@ops.ietf.org  Fri May  4 00:04:59 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA20593
	for <idn-archive@lists.ietf.org>; Fri, 4 May 2001 00:04:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vWXA-000PK5-00
	for idn-data@psg.com; Thu, 03 May 2001 20:45:36 -0700
Received: from web13301.mail.yahoo.com ([216.136.175.37])
	by psg.com with smtp (Exim 3.16 #1)
	id 14vWXA-000PJu-00
	for idn@ops.ietf.org; Thu, 03 May 2001 20:45:36 -0700
Message-ID: <20010504034535.58818.qmail@web13301.mail.yahoo.com>
Received: from [192.197.251.11] by web13301.mail.yahoo.com; Thu, 03 May 2001 20:45:35 PDT
Date: Thu, 3 May 2001 20:45:35 -0700 (PDT)
From: "Sean X. Zhang" <sean_xzhang@yahoo.com>
Subject: Re: [idn] Alternative Solutions 
To: Keith Moore <moore@cs.utk.edu>
Cc: Kenneth Whistler <kenw@sybase.com>, idn@ops.ietf.org
In-Reply-To: <200105031643.MAA19289@astro.cs.utk.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--- Keith Moore <moore@cs.utk.edu> wrote:
> > > 
> > > Or has WALID actually gotten a patent on a generic concept without
> > > actually specifying a particular technique to accomplish it??
> > > 
> > > --Ken
> > 
> > He claimed only "a method". But it appears to be a very broad one.
> > 
> > From the US Patent Office's web site, www.uspto.gov, you can get the 
> > text of the 6,182,148 patent. Its claim 1 states (with [my comments]
> > in square brackets):
> > 
> >        1. A method of converting an internet international domain name 
> >           [that's an IDN] to an RFC1035 compliant format [or, an LDH
> string],
> >           where the international domain name includes non-English
> characters
> >           which are RFC1035 non-compliant, 
> 
> interesting.  are any characters in UTF-8 "RFC1035 non-compliant"?
> It appears that RFC 1035 anticipated the need to store non-ASCII characters
> by stating that "attempts to store domain names in 7-bit ASCII
> or use of special bytes to terminate labels, etc., should be avoided."
> (section 2.3.3, first paragraph)
> 
> > the method comprising [i.e.,
> >           requires at least the following]: 
> >               intercepting the international domain name, where the
> >                    intercepting is transparent to the user 
> >                    [this appears to be the role of the "DNS proxy" 
> >                    discussed at http://www.apng.org/idns/]; 
> >               transforming the international domain name to an RFC1035
> >                    compliant domain name 
> >                    [convert the IDN to an LDH string in any way you want,
> >                    reversible or not; no, a particular technique is not
> >                    specified for this step, and yes, this step does seem
> >                    to correspond to a generic concept; 
> >                    following steps 1, 2, and part of step 3 discussed at
> >                    http://www.apng.org/idns/ might be one particular
> >                    technique to accomplish this]; 
[...]

> 1. 'intercepting' the domain name seems to imply some sort of proxy 
> (something interposed between existing components rather than having 
> the components changed to explicitly support IDNs).  

Proxy, such as the one shown at APNG's website, could be one way of
"intercepting". But as far as conversion goes, can "intercepting" 
be part of the "converter"? Or the "converter" be part of an existing
component? No matter what, the domain name has to be intercepted by, or
fed into, the "converter" (whether a layer, a proxy, or part of an existing
component) before it can be converted. No? The part of being "transparent
to a user" may suggest that the conversion claimed here cannot be some 
form of offline conversion. I raise these questions only because I feel
that this step does not seem to be a serious limitation as long as we
are not talking about some form of offline conversion. But, then, I can 
be wrong.

> 
> 2. an RFC1035 compliant domain name appears to be any string of octets 
> less than 256 octets, not beginning with '.', without consecutive '.'s,
> and with the labels between the '.'s less than 64 characters in length.  

A strict reading of RFC1035 seems to suggest this. In other words, RFC1035
seems to permit any octet (with above restrictions) to appear in a domain 
name. However, in the section dealing with the preferred convention, it 
does limit domain names to use only LDH characters. On the other hand, 
the patent itself seems to equal RFC1035 compliant with English letters
only, rightly or wrongly.

> with the possible exception of length restrictions on labels, ACE isn't 
> needed to make a domain name RFC 1035 compliant, it's needed to make the 
> domain name compliant with other protocols that expect ASCII.

Sean

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/



From owner-idn@ops.ietf.org  Fri May  4 00:11:31 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA20629
	for <idn-archive@lists.ietf.org>; Fri, 4 May 2001 00:11:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vWhJ-000Puu-00
	for idn-data@psg.com; Thu, 03 May 2001 20:56:05 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14vWhI-000Pub-00
	for idn@ops.ietf.org; Thu, 03 May 2001 20:56: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 XAA09078;
        Thu, 3 May 2001 23:55:57 -0400 (EDT)
Message-Id: <200105040355.XAA09078@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Sean X. Zhang" <sean_xzhang@yahoo.com>
cc: Keith Moore <moore@cs.utk.edu>, Kenneth Whistler <kenw@sybase.com>,
        idn@ops.ietf.org
Subject: Re: [idn] Alternative Solutions 
In-reply-to: Your message of "Thu, 03 May 2001 20:45:35 PDT."
             <20010504034535.58818.qmail@web13301.mail.yahoo.com> 
Date: Thu, 03 May 2001 23:55:57 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

in the IETF community it has been clear for many years that DNS was
intended to be 8-bit clean, so for us the interpretation of RFC 1035
is clear.  

the interpretation may not be so "clear" (or it may be "clear" in a 
different way) to a court.  just like what is "obvious" to a person
experienced in Internet applications protocols  (and which therfore
should not be patentable) is not "obvious" to a patent examiner.

for this reason, and unfortunately, technically clueful people are 
probably not very good at trying to second-guess how technically 
clueless people will interpret technical prose.  we might be able to
come up with a compelling (to us) argument that the patent doesn't
apply because of language in 1035, but the best we can hope for is
that this would provide ammunition to a competent patent attorney
who isn't working for the Dark Side.

Keith



From owner-idn@ops.ietf.org  Fri May  4 00:39:35 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA21145
	for <idn-archive@lists.ietf.org>; Fri, 4 May 2001 00:39:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vX0j-0001ED-00
	for idn-data@psg.com; Thu, 03 May 2001 21:16:09 -0700
Received: from web13306.mail.yahoo.com ([216.136.175.42])
	by psg.com with smtp (Exim 3.16 #1)
	id 14vX0i-0001E7-00
	for idn@ops.ietf.org; Thu, 03 May 2001 21:16:08 -0700
Message-ID: <20010504041607.54094.qmail@web13306.mail.yahoo.com>
Received: from [192.197.251.11] by web13306.mail.yahoo.com; Thu, 03 May 2001 21:16:07 PDT
Date: Thu, 3 May 2001 21:16:07 -0700 (PDT)
From: "Sean X. Zhang" <sean_xzhang@yahoo.com>
Subject: Re: [idn] Alternative Solutions
To: Tan Tin Wee <tinwee@bic.nus.edu.sg>
Cc: Kenneth Whistler <kenw@sybase.com>, idn@ops.ietf.org,
        Keith Moore <moore@cs.utk.edu>
In-Reply-To: <E14vVcw-000LjO-00@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Are you saying that the content of the APNG's idns webpage has not
changed since 1998?!

--- Tan Tin Wee <tinwee@bic.nus.edu.sg> wrote:
> Speaking personally, I  think these aspects of the patent discussed
> below as being covered by WALID Patent already constitutes prior art,
> which the APNG commissioned the IDNS project back in 1998,
[...]
> I don't understand the USPTO!
> 

Keith may have said it all.

--- Keith Moore <moore@cs.utk.edu> wrote:
> in the IETF community it has been clear for many years that DNS was
> intended to be 8-bit clean, so for us the interpretation of RFC 1035
> is clear.  
> 
> the interpretation may not be so "clear" (or it may be "clear" in a 
> different way) to a court.  just like what is "obvious" to a person
> experienced in Internet applications protocols  (and which therfore
> should not be patentable) is not "obvious" to a patent examiner.
> 
...

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/



From owner-idn@ops.ietf.org  Fri May  4 01:17:32 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA22944
	for <idn-archive@lists.ietf.org>; Fri, 4 May 2001 01:17:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vXkm-00043K-00
	for idn-data@psg.com; Thu, 03 May 2001 22:03:44 -0700
From: Tan Tin Wee <tinwee@bic.nus.edu.sg>
To: "Sean X. Zhang" <sean_xzhang@yahoo.com>
CC: Kenneth Whistler <kenw@sybase.com>, idn@ops.ietf.org, Keith.Moore
Message-Id: <E14vXkm-00043K-00@psg.com>
Date: Thu, 03 May 2001 22:03:44 -0700

<moore@cs.utk.edu>
Subject: Re: [idn] Alternative Solutions
Sender: owner-idn@ops.ietf.org
Precedence: bulk

The proxy system of APNG has been widely publicised since the project
was commissioned in July 1998.
This was documented in the APNG Geneva Meeting
http://www.apng.org/commission/

The findings and report was adopted in March 1999
http://www.apng.org/commission/idns/ in a public meeting.

>From August to December 1998, the pre-prototype proxy "intercept and
convert"
system using UTF5" was demonstrated in Hong Kong, India, Korea and China
and
managed to gather international interest in this project.
At the IFWP August meeting in Singapore, the system was demonstrated to
various
international delegates to the meeting, who were discussing the issues
surrounding the new IANA, including those from InterNIC and from the
IETF.

If this widely publicised system is not prior art, then I don't really
know
what constitutes prior art.

As for http://www.apng.org/idns/
the original server hosting this is
http://www.irdu.nus.edu.sg/apng/idns/
before it was transferred to the new APNG Chairman's computer
in Waseda University.
mirage: /home/server/webster/WWW/apng/idns > ls -al index*
-rw-rw-r--   1 jseng    idns        9109 Jun  7  1999 index.shtml
when it was last edited to repoint to another new website,
but essentially the contents were of 1998 antiquity.

The powerpoint presentation linked from http://www.apng.org/idns/
mirage: /home/server/webster/WWW/apng/idns > ls -al sgnic-dns.ppt
-rw-r--r--   1 jseng    student    86528 Jul 13  1998 sgnic-dns.ppt
This presentation was originally presented at the SGNIC conference
on DNS in Singapore, which Dave Crocker was also a speaker if my
fading memory still serves me well.

The FAQs for instance http://www.irdu.nus.edu.sg/apng/idns/faq.html
mirage: /home/server/webster/WWW/apng/idns > ls -al *faq*
-rw-rw-r--   1 jseng    idns       11888 Dec  7  1998 faq.html
-rw-rw----   1 jseng    idns        5435 Jul  7  1998 faq2.html
-rw-rw-r--   1 jseng    idns        2413 Jul  3  1998 oldfaq.html

Martin Dürst's ietf draft harks back to 1997 and 1996 even? Martin?
and there's of course Jason Pouflis' work.

And regarding what is obvious to a patent examiner or not, I believe
this is what we pay the Patent Office, inter alia, a search for prior
art.
During the time of patenting, a simple search of Yahoo with search
strings
"internationalised domain names" would immediately pick up:

APNG Chairman's Commission
     ... APNG8-CC2, Jul98, Multilingual Multiscript Domain Names
Service, Joint
APNG-CIR(Singapore)
     Project | URL - launched 17th Oct 98 | Final Report-Meeting March
1999 ...
     http://www.apng.org/commission/   [More Results From: www.apng.org]

And "what is obvious" is pegged at what is obvious to a
professional in the field which the patent is concerned with, and
not pegged at the proverbial "man in the street" or
better (maybe worse), the "patent examiner", although
operationally, it may not be the case, as Keith pointed out.

bestrgds

Tin Wee (personally speaking)

"Sean X. Zhang" wrote:
>
> Are you saying that the content of the APNG's idns webpage has not
> changed since 1998?!
>
> --- Tan Tin Wee <tinwee@bic.nus.edu.sg> wrote:
> > Speaking personally, I  think these aspects of the patent discussed
> > below as being covered by WALID Patent already constitutes prior
art,
> > which the APNG commissioned the IDNS project back in 1998,
> [...]
> > I don't understand the USPTO!
> >
>
> Keith may have said it all.
>
> --- Keith Moore <moore@cs.utk.edu> wrote:
> > in the IETF community it has been clear for many years that DNS was
> > intended to be 8-bit clean, so for us the interpretation of RFC 1035
> > is clear.
> >
> > the interpretation may not be so "clear" (or it may be "clear" in a
> > different way) to a court.  just like what is "obvious" to a person
> > experienced in Internet applications protocols  (and which therfore
> > should not be patentable) is not "obvious" to a patent examiner.
> >
> >...
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - buy the things you want at great prices
> http://auctions.yahoo.com/





From owner-idn@ops.ietf.org  Fri May  4 13:44:43 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17911
	for <idn-archive@lists.ietf.org>; Fri, 4 May 2001 13:44:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vjJH-000LBo-00
	for idn-data@psg.com; Fri, 04 May 2001 10:24:07 -0700
Received: from ns1.neteka.com ([205.150.182.130] helo=neteka.com)
	by psg.com with smtp (Exim 3.16 #1)
	id 14vjJF-000LBa-00
	for idn@ops.ietf.org; Fri, 04 May 2001 10:24:05 -0700
Message-ID: <006001c0d4bf$669d49c0$1001a8c0@vaioedmon>
From: "Edmon" <edmon@neteka.com>
To: "Keith Moore" <moore@cs.utk.edu>, "John C Klensin" <klensin@jck.com>
Cc: <idn@ops.ietf.org>
References: <200105021226.IAA11009@astro.cs.utk.edu> <004201c0d364$94b2a5a0$1001a8c0@vaioedmon>
Subject: Re: [idn] Alternative Solutions 
Date: Fri, 4 May 2001 13:26:41 -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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

From my understanding, the Walid Patent states that the method is
1. intercept multilingual request
2. convert multilingual characters into LDH
3. resolve using LDH

which means using a client or proxy to intercept and convert before sending
LDH to DNS.  ACEing mutlilingual characters is not part of the patent if it
is not done during DNS request.

my suggestion below should have no conflict with the Walid Patent
1. there is no interception -- requests are sent and responded to as is
2. there are no conversion -- additional record contains LDH which could be
used
3. resolution depends on the UTF characters

It gives us the benefit of working with ACE
- alphanumeric could be typed by admins or other people who wish to contact
the domain using its LDH form
- other protocols and apps could use LDH
- mode bit response could be introduced to other protocols as needed (if
apps need to upgrade for display of ACE, then they might as well upgrade for
the mode bit, while in the intermediary, they can use the LDH)
and avoids the Walid Patent

Edmon




> What about this:
> since for IDNA we assume that there needs to be a client upgrade anyway,
> adding more stuff should be ok.
>
> - client sends DNS request with mode bit in UTF
> - Server returns UTF=A/A6/MX, etc AND UTF=LDH(in an ACE)
> - client then chooses to use straight UTF or LDH info when using DNS info
in
> other apps
>   based on - if the other app is IDN aware, it uses UTF with mode bit
>                  - if the other app is nonIDN aware, it uses LDH in ACE
>
> This gives us the benefits of ACE being able to be used for other
protocols
> which are not upgraded yet and also provides a clear path foward towards a
> UTF+mode bit longer term solution.
>
> Edmon
>
>
> > > >> Server-side ACE - ACE transformation takes place at server end
> > > >
> > > > even if you set up another way to do queries for IDNs
> > > > (whether this is a separate protocol or a mode bit or whatever)
> > > > you still need ACE for client protocols that only support ASCII
> > > > names.
> > >
> > > Unless we go either into a new class (or some EDNS-required
> > > mechanism) that prevents an "international" name from being seen,
> > > and an "international" query from being made, except by IDN-aware
> > > applications.
> >
> > *AND* we insist that "international" names are never leaked
> > *by any protocol* (including, say, SMTP) to an application that
> > doesn't understand them.  In practice this means not just a mode
> > bit for DNS but also a mode bit for every protocol that carries
> > DNS names.
> >
> > which doesn't seem like a very attractive path to me.
> >
> > Keith
>




From owner-idn@ops.ietf.org  Fri May  4 13:47:24 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17946
	for <idn-archive@lists.ietf.org>; Fri, 4 May 2001 13:47:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vjOr-000LVL-00
	for idn-data@psg.com; Fri, 04 May 2001 10:29:53 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14vjOq-000LVB-00
	for idn@ops.ietf.org; Fri, 04 May 2001 10:29:52 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA10941;
        Fri, 4 May 2001 13:29:43 -0400 (EDT)
Message-Id: <200105041729.NAA10941@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Edmon" <edmon@neteka.com>
cc: "Keith Moore" <moore@cs.utk.edu>, "John C Klensin" <klensin@jck.com>,
        idn@ops.ietf.org
Subject: Re: [idn] Alternative Solutions 
In-reply-to: Your message of "Fri, 04 May 2001 13:26:41 EDT."
             <006001c0d4bf$669d49c0$1001a8c0@vaioedmon> 
Date: Fri, 04 May 2001 13:29:43 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Edmon,

the problem with your proposal is that it provides no way for 
applications which don't support IDNs to deal with IDNs
(whether ACE-encoded or not) that get sent to them in email 
addresses, URLs, etc.

Keith



From owner-idn@ops.ietf.org  Fri May  4 14:32:33 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18675
	for <idn-archive@lists.ietf.org>; Fri, 4 May 2001 14:32:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vkCe-000OR5-00
	for idn-data@psg.com; Fri, 04 May 2001 11:21:20 -0700
Received: from ns1.neteka.com ([205.150.182.130] helo=neteka.com)
	by psg.com with smtp (Exim 3.16 #1)
	id 14vkCd-000OQz-00
	for idn@ops.ietf.org; Fri, 04 May 2001 11:21:19 -0700
Message-ID: <000b01c0d4c7$667ca8c0$1001a8c0@vaioedmon>
From: "Edmon" <edmon@neteka.com>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: "John C Klensin" <klensin@jck.com>, <idn@ops.ietf.org>
References: <200105041729.NAA10941@astro.cs.utk.edu>
Subject: Re: [idn] Alternative Solutions 
Date: Fri, 4 May 2001 14:23:57 -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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

But if the ACE domain is used for the apps, then the worse case scenario is
still the same if IDNA was used, that is, the ACE string will be displayed.
But that does not affect the resolution or transportation.

In order for a person to send out an email with IDN, they must either:
1. have an IDN aware app; or
2. type in the ACE.

for scenario 1, the IDN aware app will correctly obtain the LDH/ACE before
sending so that the recepient could use it for reply purposes (how this is
done depends on the implementation of the IDN aware MUA and could be
discussed when a mail wg is created)
for scenario 2, the ACE name will be used directly so there should be no
concern except of aesthetics

In order for a person to use an IDN URL, they must either:
1. have an IDN aware browser/app; or
2. type in the ACE

for scenario 1, the IDN aware app will obtain the LDH/ACE and use this to
communicate with the http/web server so there should be no problem
retrieving the resource
for scenario 2, the ACE name is used and will be resolved as if it was an
English domain name

I dont see why you say that there is no way for the ACE to be utilized for
other apps and protocols.

Edmon


----- Original Message -----
From: "Keith Moore" <moore@cs.utk.edu>
To: "Edmon" <edmon@neteka.com>
Cc: "Keith Moore" <moore@cs.utk.edu>; "John C Klensin" <klensin@jck.com>;
<idn@ops.ietf.org>
Sent: Friday, May 04, 2001 1:29 PM
Subject: Re: [idn] Alternative Solutions


> Edmon,
>
> the problem with your proposal is that it provides no way for
> applications which don't support IDNs to deal with IDNs
> (whether ACE-encoded or not) that get sent to them in email
> addresses, URLs, etc.
>
> Keith




From owner-idn@ops.ietf.org  Fri May  4 14:35:49 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18751
	for <idn-archive@lists.ietf.org>; Fri, 4 May 2001 14:35:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vkGq-000OiR-00
	for idn-data@psg.com; Fri, 04 May 2001 11:25:40 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14vkGp-000OiK-00
	for idn@ops.ietf.org; Fri, 04 May 2001 11:25:39 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA11391;
        Fri, 4 May 2001 14:25:35 -0400 (EDT)
Message-Id: <200105041825.OAA11391@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Edmon" <edmon@neteka.com>
cc: "Keith Moore" <moore@cs.utk.edu>, "John C Klensin" <klensin@jck.com>,
        idn@ops.ietf.org
Subject: Re: [idn] Alternative Solutions 
In-reply-to: Your message of "Fri, 04 May 2001 14:23:57 EDT."
             <000b01c0d4c7$667ca8c0$1001a8c0@vaioedmon> 
Date: Fri, 04 May 2001 14:25:35 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> I dont see why you say that there is no way for the ACE to be utilized for
> other apps and protocols.

the non-IDN-aware app still has to be able to lookup the domain using
its ACE format.  this implies that the servers have to support ACE in
addition to supporting native format.

if they can do this without violating the patent, fine.

Keith



From owner-idn@ops.ietf.org  Fri May  4 15:42:51 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA19715
	for <idn-archive@lists.ietf.org>; Fri, 4 May 2001 15:42:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vlGx-0002Zx-00
	for idn-data@psg.com; Fri, 04 May 2001 12:29:51 -0700
Received: from sitemail.everyone.net ([216.200.145.35] helo=omta05.mta.everyone.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14vlGw-0002Zp-00
	for idn@ops.ietf.org; Fri, 04 May 2001 12:29:50 -0700
Received: from sitemail.everyone.net (reports [216.200.145.62])
	by omta05.mta.everyone.net (Postfix) with ESMTP id B7A74490B8
	for <idn@ops.ietf.org>; Fri,  4 May 2001 12:29:43 -0700 (PDT)
Received: by sitemail.everyone.net (Postfix, from userid 99)
	id 77EEC36F9; Fri,  4 May 2001 12:29:43 -0700 (PDT)
Content-Type: text/plain
Content-Disposition: inline
Mime-Version: 1.0
X-Mailer: MIME-tools 4.104 (Entity 4.117)
Date: Fri, 4 May 2001 12:29:43 -0700 (PDT)
From: Shaun Marquardt <shaunm@mahjongplayer.com>
To: idn@ops.ietf.org
Subject: [idn] Link to the Walid patent
Reply-To: shaunm@mahjongplayer.com
X-Originating-Ip: [24.64.44.130]
Message-Id: <20010504192943.77EEC36F9@sitemail.everyone.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Here is a link to Walid patent # 6182148:

http://www.delphion.com/details?&pn=US06182148__

Hope this helps.  

Shaun


_____________________________________________________________
Get yourname@mahjongplayer.com for free!
We also have discussions, chat, links, and special info for collectors. Go to http://www.MahJongPlayer.com and check us out!



From owner-idn@ops.ietf.org  Fri May  4 16:22:34 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA20061
	for <idn-archive@lists.ietf.org>; Fri, 4 May 2001 16:22:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vlvO-0004Mo-00
	for idn-data@psg.com; Fri, 04 May 2001 13:11:38 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14vlvN-0004Mi-00
	for idn@ops.ietf.org; Fri, 04 May 2001 13:11:37 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 14vlvM-00066L-00; Fri, 04 May 2001 13:11:36 -0700
Date: Fri, 4 May 2001 20:11:36 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Alternative Solutions
Message-ID: <20010504201136.C22526@arwen.cs.berkeley.edu>
References: <200105041729.NAA10941@astro.cs.utk.edu> <000b01c0d4c7$667ca8c0$1001a8c0@vaioedmon>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <000b01c0d4c7$667ca8c0$1001a8c0@vaioedmon>; from edmon@neteka.com on Fri, May 04, 2001 at 02:23:57PM -0400
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I think I finally understand Edmon's proposal.

In the current IDNA scheme, the only form of the domain name stored
in DNS is the ACE form.  Applications algorithmically convert Unicode
domain names to and from ACE.

In Edmon's proposal, applications still algorithmically convert ACE to
Unicode, but not Unicode to ACE.  For Unicode to ACE, they do a DNS
lookup, which requires that DNS store duplicate information under both
the ACE names and the Unicode names (or appear to do so).

Presumably this is intended to get around the patent.  I don't know if
it does.  In any case, it seems like such a shame to do a DNS lookup
when a local computation would suffice, and get nothing in return for
that extra cost.  If we're going to pay for a DNS lookup on one end, we
might as well pay for DNS lookups at both ends, because then we can get
something in return: meaningful (non-gibberish) LDH names.

AMC



From owner-idn@ops.ietf.org  Fri May  4 20:00:59 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA22576
	for <idn-archive@lists.ietf.org>; Fri, 4 May 2001 20:00:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vpAi-000GPb-00
	for idn-data@psg.com; Fri, 04 May 2001 16:39:40 -0700
Received: from [216.177.8.114] (helo=ayna.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14vpAh-000GPD-00
	for idn@ops.ietf.org; Fri, 04 May 2001 16:39:39 -0700
Received: (from nobody@localhost)
	by ayna.com (8.9.3/8.9.3) id UAA18682
	for idn@ops.ietf.org; Fri, 4 May 2001 20:06:22 -0400
To: idn@ops.ietf.org
Subject: Re: [idn] Link to the Walid patent
Message-ID: <989021182.3af343fe06857@www.bareed.ayna.com>
Date: Fri, 04 May 2001 20:06:22 +2000 (EDT)
From: Adonis El Fakih <adonis@ayna.com>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: Ayna VER 2.22 
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Thanks for the link.

The information presented in the patent is explained very nicely, but my question to fellow IDN members is this. In what context are we looking at the Walid patent??  Walid patent assumes that each client machine has to do the work before it calls a server with mulitlingual name.  I personally do not see this approach as being a doable thing.  There are far more client machines and a variety of OSes that will make it impossible to get this patented approach to work.  Not to mention that any open source code will be stuck if it has to rely on this technology.  Too many legal loop holes, and special interest groups, have to adopt Walid's patent, and I doubt Microsoft, and the Unix OS developers will all use this, becuase of the legalities involved.

I feel a server side implementation is more appropriate for the long run, and to my understanding there are companies that already have technologies that do similar transformations and will work for international user, by simply setting up root servers that will resolve those names, and in worst case senario, the client has to set the networking of their machine to query a name server that can convert the translated string.

So again I do not see why we are discussing Walid's patent??  Even if we have a majority of people here feel that it is a great technology, no one is gong to fork a penny to Walid unless there is no other way of doing the same thing for free.  And the fact that oher companies already resolve multilingual domains shows that other options do exist.

I would appretiate any input from fellow members about this specific discussion, and what does Walid expect from IETF??

Best regards
Adonis
________________________________________________
Adonis El Fakih - Chairman, CEO
Ayna Corporation, World Trade Center, Suite 315,
Boston, MA 02210 USA



shaunm@mahjongplayer.com ßÊÈ:

> Here is a link to Walid patent # 6182148: 
 
http://www.delphion.com/details?&pn=US06182148__ 
 
Hope this helps.   
 
Shaun 


_____________________________________________________________
Get yourname@mahjongplayer.com for free! 
We also have discussions, chat, links, and special info for collectors. Go to http://www.MahJongPlayer.com and check us out!




______________________________________________________________
Ayna, The Arabic Internet Starts Here.     http://www.ayna.com



From owner-idn@ops.ietf.org  Sat May  5 04:09:02 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA12113
	for <idn-archive@lists.ietf.org>; Sat, 5 May 2001 04:09:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14vwmk-000LC4-00
	for idn-data@psg.com; Sat, 05 May 2001 00:47:26 -0700
Received: from m2.bezeqint.net ([192.115.106.47])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14vwmj-000L7v-00
	for idn@ops.ietf.org; Sat, 05 May 2001 00:47:25 -0700
Received: from qsm3 (bzq-138-192.bezeqint.net [212.179.138.192] (may be forged))
	by m2.bezeqint.net (Mirapoint)
	with SMTP id ABZ59999;
	Sat, 5 May 2001 10:46:14 +0300 (IDT)
From: "Jonathan Rosenne" <rosenne@qsm.co.il>
To: "Adam M. Costello" <amc@cs.berkeley.edu>, <idn@ops.ietf.org>
Subject: RE: [idn] Alternative Solutions
Date: Sat, 5 May 2001 10:43:11 +0300
Message-ID: <NDBBIFGHGLJILJGHOEELCEKEDEAA.rosenne@qsm.co.il>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Importance: Normal
In-Reply-To: <20010504201136.C22526@arwen.cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Maybe, if the spec says to go to the server for the conversion from Unicode to
ACE, and someone short circuits this and saves a lookup, the spec would not be
in conflict with the purported patent.

Jony

> -----Original Message-----
> From: owner-idn@ops.ietf.org [mailto:owner-idn@ops.ietf.org]On Behalf
> Of Adam M. Costello
> Sent: Friday, May 04, 2001 11:12 PM
> To: idn@ops.ietf.org
> Subject: Re: [idn] Alternative Solutions
>
>
> I think I finally understand Edmon's proposal.
>
> In the current IDNA scheme, the only form of the domain name stored
> in DNS is the ACE form.  Applications algorithmically convert Unicode
> domain names to and from ACE.
>
> In Edmon's proposal, applications still algorithmically convert ACE to
> Unicode, but not Unicode to ACE.  For Unicode to ACE, they do a DNS
> lookup, which requires that DNS store duplicate information under both
> the ACE names and the Unicode names (or appear to do so).
>
> Presumably this is intended to get around the patent.  I don't know if
> it does.  In any case, it seems like such a shame to do a DNS lookup
> when a local computation would suffice, and get nothing in return for
> that extra cost.  If we're going to pay for a DNS lookup on one end, we
> might as well pay for DNS lookups at both ends, because then we can get
> something in return: meaningful (non-gibberish) LDH names.
>
> AMC
>
>




From owner-idn@ops.ietf.org  Sun May  6 13:49:48 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA12393
	for <idn-archive@lists.ietf.org>; Sun, 6 May 2001 13:49:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14wSMh-000FE1-00
	for idn-data@psg.com; Sun, 06 May 2001 10:30:39 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14wSMg-000FDr-00
	for idn@ops.ietf.org; Sun, 06 May 2001 10:30:39 -0700
Received: from [192.168.1.35] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id TAA11383;
	Sun, 6 May 2001 19:30:25 +0200 (MET DST)
Date: Sun, 06 May 2001 19:15:42 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Adonis El Fakih <adonis@ayna.com>, idn@ops.ietf.org
Subject: Re: [idn] Link to the Walid patent
Message-ID: <1052442.989176542@localhost>
In-Reply-To: <989021182.3af343fe06857@www.bareed.ayna.com>
References:  <989021182.3af343fe06857@www.bareed.ayna.com>
X-Mailer: Mulberry/2.1.0a5 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-05-04 20.06 +2000 Adonis El Fakih <adonis@ayna.com> wrote:

> I feel a server side implementation is more appropriate for the long run

What do you send in for example SMTP and POP?

I.e. IDN is _not_ a DNS-problem. It's a domain name problem.

  paf




From owner-idn@ops.ietf.org  Mon May  7 12:44:40 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA16220
	for <idn-archive@lists.ietf.org>; Mon, 7 May 2001 12:44:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14wnkM-000NG3-00
	for idn-data@psg.com; Mon, 07 May 2001 09:20:30 -0700
Date: Mon, 07 May 2001 09:10:43 -0700
To: idn@ops.ietf.org
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: [idn] iDNS transition: end-system vs. infrastructure?
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E14wnkM-000NG3-00@psg.com>

Folks,

I've been dogmatically applying the standard view that having to change
only end-systems is  much, much better for transition than having to
change
the infrastructure.  That is why MIME-like encapsulated encoding of the
UTF-8 string makes sense.

The only weakness to such an approach is when it is not possible to do
such
a change.  That is, when it is not possible to limit changes only to
"end
systems". IPv6 is largely an example of needing to change more than
end-systems, namely needing to change infrastructure, except for
IPv6-over-IPv4 tunneling and gatewaying between 6 and 4.  But really,
basic
IPv6 transition is a pure, dual-stack approach.  It does not work unless
and until the infrastructure has been upgraded to support it.  I've been
assuming that iDNS is better using MIME-like encoding than IPv6
dual-stack.

But is it really?

DNS Exchanges are between a client and a true server -- that is, the
entire
transaction is between the DNS client and the DNS server.  The DNS
server
is the real and only target.  By contrast for email, there is a sender
at
one end (email originator) a receiver at the other (email destination)
with
an infrastructure in the middle (SMTP relays).

The DNS infrastructure comprises the DNS servers, I think.  But iDNS
does
not work unless new types of strings are IN THE SERVER.  The "MIME"
model
has been applied on the theory that the server changes are limited to
the
administrative software, which installs an iDNS string into an otherwise
unchanged server.

However it strikes me that having to change a server's administrative
software is no different than having to change some other part of the
server.  That means that iDNS is inherently an infrastructure
transition,
and not really subject to an an end-system transition strategy like
encapsulation.

Let's look at this from another perspective:

There is no problem with a aDNS (old-time ascii DNS) client talking to
an
iDNS server, I assume.  So we can ignore that case.  iDNS client talking
to
iDNS server is even more uninteresting.

So the only interesting case is an iDNS client talking to an aDNS
server.

What is an iDNS client?  It is a user with an iDNS string.

Test 1 (DNS client-side):  If a user enters a UTF-8 string to DNS client
software, what breaks?  That is, if the user with an international
domain
name tries to use client software not ready for it, what happens?

Test 1, tentative answer:  What happens whenever any user tries to use
facilities not supported by their client software?  Bad things.  But
that
is the user's problem to work out with the client software supplier.
This
is no different.  We can therefore, I think, ignore this case,
dismissing
it as "tell the user to upgrade".

Test 2 (DNS server-side):  A user with an iDNS string and an
iDNS-capable
client queries a non-iDNS server.

Test 2, meta-answer:  This is already an error condition; the query is a
mistake.  That is if the server does not support iDNS, then it certainly
won't be holding the entry for the iDNS name that is being
provided.  Hence, querying that DNS server should not be happening!

Test 2, part a:  The UTF-8 shows up at the aDNS server.  The most
important
question is whether the server crashes.  A server that crashes from
malformed input data is a pretty sorry server, but IFF the condition is
prevalent it cannot be ignored.  If the condition is rare, then it can
perhaps be ignored, or treated as less than a showstopper.

Test 2, part b:  If the aDNS server does not crash, does the response
from
the server cause the iDNS *client* to crash?  We can constrain the
problem
by finding out what these responses are, currently, and writing them
into a
client specification.  That should eliminate this factor as a concern.

Test 3:  Client side application-level support for iDNS (the software
that
is the iDNS client's client.)  As with Test 1, this can be ignored by
virtue of being between consenting user and client software provider.

Test 4, parts a and b:  Replicate Test 2 questions, but for
application-level iDNS string servers.  This needs to be sampled around
the
net.  Any substantial amount of server applications crashing (hence Test
4,
part a) is a serious problem, possibly with no clear resolution.

What cases have I missed?

How hard would it be to do some large-scale sampling of deployed servers
around the net?


Summary:

         Users of iDNS currently need revised software.  No matter what
the
technical approach for creating iDNS, users will always need revised
software.  It must be both revised application software and revised DNS
client software.

         Hence, the primary concern for "just do pure UTF-8" is the
effect
of sending UTF-8 to an aDNS server.  However the nature of DNS is such
that
a DNS field with a UTF-8 string only gets sent to a server that is
supposed
to be able to resolve the that field.  With one exception:  The only
time
an aDNS server is likely to get an iDNS query is when the server is
doing
primary support for end-users.  That is, when it is the DNS server that
is
first contact by a client.

d/



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






From owner-idn@ops.ietf.org  Mon May  7 12:55:01 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA16488
	for <idn-archive@lists.ietf.org>; Mon, 7 May 2001 12:54:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14wo36-000NmY-00
	for idn-data@psg.com; Mon, 07 May 2001 09:39:52 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14wo35-000NmR-00
	for idn@ops.ietf.org; Mon, 07 May 2001 09:39:51 -0700
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id JAA10468
	for <idn@ops.ietf.org>; Mon, 7 May 2001 09:39:51 -0700
Message-Id: <5.1.0.14.2.20010507092433.01eb3858@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 07 May 2001 09:40:27 -0700
To: idn@ops.ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Subject: [idn] Assessing patent "validity"
In-Reply-To: <1052442.989176542@localhost>
References: <989021182.3af343fe06857@www.bareed.ayna.com>
 <989021182.3af343fe06857@www.bareed.ayna.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk


It is tempting for the working group to travel down a path, considering 
whether the Walid patent is valid.

Let me very, very strongly encourage people to avoid the temptation:

         An IETF working group lacks competence for such a 
discussion.  Nothing we can do will change that.

         Finding some patent attorneys who will say that the patent is weak 
does not alter the competence of the group.  Fighting a patent is ALWAYS a 
lengthy, messy, expensive affair and the outcome is NEVER guaranteed.  I 
said ALWAYS lengthy and the outcome is NEVER guaranteed.

         A standards group cannot afford to pass a standard that uses 
technology with questionable legal standing.  It confuses the market and a 
confused market will not invest in the standard.  Hence it does not get 
deployed or used.

         We have an urgent requirement for an iDNS standard that can be 
used immediately.  Choosing a specification that is known to be encumbered 
by intellectual property claims -- when the holder of those claims has not 
provided a documented commitment to handle the claims in a way that is 
acceptable to the IETF -- means that the specification will not succeed.

         Walid has had months to participate constructively, to find a way 
to handle the claims acceptably for the IETF.  Serious negotiations can 
take months, but in this case, serious discussions have not even 
begun!  This establishes an unfortunate but clear situation:  The working 
group must assume that there will not be an agreement between Walid and the 
IETF that is acceptable to the IETF.

         So we need to engineer a solution that works around their patent.

d/



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




From owner-idn@ops.ietf.org  Mon May  7 13:02:43 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA16733
	for <idn-archive@lists.ietf.org>; Mon, 7 May 2001 13:02:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14wo36-000Nmg-00
	for idn-data@psg.com; Mon, 07 May 2001 09:39:52 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14wo36-000NmS-00
	for idn@ops.ietf.org; Mon, 07 May 2001 09:39:52 -0700
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id JAA10471
	for <idn@ops.ietf.org>; Mon, 7 May 2001 09:39:51 -0700
Message-Id: <5.1.0.14.2.20010507092548.03196f10@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 07 May 2001 09:29:53 -0700
To: idn@ops.ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Subject: [idn] "server-side" implementation
In-Reply-To: <989021182.3af343fe06857@www.bareed.ayna.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Folks,

Since the idea of restricting iDNS to require only implementation on the 
server has been appearing a number of times.

We need to shoot this idea dead.  It has nothing to do with networking or 
the IETF.  If something is restricted to be within a machine, it is not 
networking.

Unfortunately, iDNS requires sending an "international" string between a 
DNS client and a DNS server.
That IS a networking activity, and it means that there must be a protocol 
between client and server, supporting that international string, such as UTF-8.

So anyone who thinks that iDNS can be restricted to a server needs to 
consider how the iDNS string shows up at the server.

d/


>I feel a server side implementation is more appropriate for the long run, 
>and to my understanding there are companies that already have technologies 
>that do similar transformations and will work for international user, by 
>simply setting up root servers that will resolve those names, and in worst 
>case senario, the client has to set the networking of their machine to 
>query a name server that can convert the translated string.
>
>So again I do not see why we are discussing Walid's patent??  Even if we 
>have a majority of people here

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




From owner-idn@ops.ietf.org  Mon May  7 14:55:40 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA19222
	for <idn-archive@lists.ietf.org>; Mon, 7 May 2001 14:55:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14wpvx-0000xX-00
	for idn-data@psg.com; Mon, 07 May 2001 11:40:37 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14wpvw-0000xQ-00
	for idn@ops.ietf.org; Mon, 07 May 2001 11:40:36 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA22629;
        Mon, 7 May 2001 14:40:32 -0400 (EDT)
Message-Id: <200105071840.OAA22629@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] Assessing patent "validity" 
In-reply-to: Your message of "Mon, 07 May 2001 09:40:27 PDT."
             <5.1.0.14.2.20010507092433.01eb3858@dcrocker.net> 
Date: Mon, 07 May 2001 14:40:32 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dave Crocker writes...

> It is tempting for the working group to travel down a path, considering
> whether the Walid patent is valid.
> 
> Let me very, very strongly encourage people to avoid the temptation:
> 
>          An IETF working group lacks competence for such a
> discussion.  Nothing we can do will change that.

[...]
>          So we need to engineer a solution that works around their patent.

it strikes me that attempting to determine whether the patent is valid
is very similar to attempting to determine whether a proposed solution
infringes a patent.  each is subject to the whim of some technically 
clueless judge, whose decisions are informed by technically clueless
patent attorneys, who are paid not to bring expertise to the discussion 
but to oppose one another.

what we have to do in IETF is reach consensus.  we might reach consensus
because we mostly think that our solution doesn't infringe the patent at
all, or we might reach consensus because we mostly think that our solution
doesn't infringe portions of the patent that will hold up in court.  and
different people can have different reasons for supporting it.

Keith



From owner-idn@ops.ietf.org  Mon May  7 22:02:59 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA27330
	for <idn-archive@lists.ietf.org>; Mon, 7 May 2001 22:02:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14wwR2-000CLw-00
	for idn-data@psg.com; Mon, 07 May 2001 18:37:08 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14wwR1-000CLq-00
	for idn@ops.ietf.org; Mon, 07 May 2001 18:37:07 -0700
Received: from [165.227.249.20] (ip20.proper.com [165.227.249.20])
	by above.proper.com (8.9.3/8.9.3) with ESMTP id SAA20932
	for <idn@ops.ietf.org>; Mon, 7 May 2001 18:37:02 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0510031cb71cfa60c81a@[165.227.249.20]>
In-Reply-To: <200105071840.OAA22629@astro.cs.utk.edu>
References: <200105071840.OAA22629@astro.cs.utk.edu>
Date: Mon, 7 May 2001 18:36:59 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: [idn] The WALID patent may not apply to IDNA
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 2:40 PM -0400 5/7/01, Keith Moore wrote:
>it strikes me that attempting to determine whether the patent is valid
>is very similar to attempting to determine whether a proposed solution
>infringes a patent.

Keith is absolutely right. Assessing whether a patent applies takes 
the same set of skills as assessing whether it does not.

In the past few weeks, there has been a lot of off-list discussion of 
the WALID patent. One common thread in many of the discussions has 
been "our company doesn't want to be the first to post to the list". 
I have discovered another advantage of not working for companies. :-)

Many people have made the assumption that the WALID patent applies to 
the IDNA protocol. Until recently, I did too, based on a not-careful 
reading of the patent. After reading more carefully, I believe that 
the WALID patent does *not* apply to the IDNA protocol. Every claim 
in the patent talks about "redirector string" that is another layer 
of the DNS hierarchy (such as appending ".i" to the end of a FQDN); 
IDNA does not use that method and in fact doesn't use anything even 
vaguely similar.

Many of the people who are speaking on the mailing list have admitted 
off-line to not having read the patent. The combination of some of 
those of us who have read the patent saying we thought it might apply 
to IDNA and those who have not read the patent saying the same thing 
has caused many people on the list to assume that the patent applies.

WALID has never claimed that the patent applies to the IDNA protocol. 
There may be a good reason for this.

In the off-line discussion, every company I have talked with who has 
had their patent lawyers look at the WALID patent have said that they 
don't think it applies to IDNA. However, none of them wanted to say 
that first. On re-reading the patent, I now agree with them (and kind 
of curse myself for my cursory reading earlier on).

This working group has to reach consensus. We already did that about 
IDNA; then the WALID patent surfaced. However, unless the working 
group thinks the patent actually applies to IDNA, we should continue 
to work on IDNA.

If anyone who has read the patent would like to say why they think it 
applies to IDNA, please do so. Otherwise, I propose that the working 
group moves forward on IDNA and we ignore the WALID patent.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Tue May  8 00:38:11 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA00879
	for <idn-archive@lists.ietf.org>; Tue, 8 May 2001 00:38:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14wyqd-000LZl-00
	for idn-data@psg.com; Mon, 07 May 2001 21:11:43 -0700
Date: Mon, 07 May 2001 18:53:28 -0700
To: Keith Moore <moore@cs.utk.edu>
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: Re: [idn] Assessing patent "validity"
Cc: idn@ops.ietf.org
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E14wyqd-000LZl-00@psg.com>

At 11:40 AM 5/7/2001, Keith Moore wrote:
>Dave Crocker writes...
> >          An IETF working group lacks competence for such a
> > discussion.  Nothing we can do will change that.
>
>
>what we have to do in IETF is reach consensus.  we might reach
consensus
>because we mostly think that our solution doesn't infringe the patent
at
>all, or we might reach consensus because we mostly think that our
solution
>doesn't infringe portions of the patent that will hold up in court.
and
>different people can have different reasons for supporting it.


Evidently you misunderstood both of my major points:

         1.  The IETF has no competence at assessing legal merit in an
intellectual property conflict.

Any effort to factor such issues into a decision are sure to be done
badly.

(Your assessment of the players in the legal process is accurate for
some
players and wholly off the mark for others, of course.)


         2.  Passing a standard that has ambiguous and/or contested
intellectual property claims, or ambiguous/contested licensing terms, is
certain -- as in, guaranteed -- to scare vendors off from implementing
the
standard.

d/






From owner-idn@ops.ietf.org  Tue May  8 01:09:06 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA01540
	for <idn-archive@lists.ietf.org>; Tue, 8 May 2001 01:09:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14wzLg-000Mbp-00
	for idn-data@psg.com; Mon, 07 May 2001 21:43:48 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14wzLf-000Mbj-00
	for idn@ops.ietf.org; Mon, 07 May 2001 21:43:48 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id B3F1DFFC01; Tue,  8 May 2001 12:46:39 +0800 (SGT)
Message-ID: <019801c0d779$5cccbc70$0201000a@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "John C Klensin" <klensin@jck.com>, <idn@ops.ietf.org>,
        "Zita Wenzel" <zita@isi.edu>
References: <875398750.988717876@P2>
Subject: Re: [idn] requirements-05
Date: Tue, 8 May 2001 12:43: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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi John,

Requirements-06 have just been submitted to incorporate your comments
here.

-James Seng

----- Original Message -----
From: "John C Klensin" <klensin@jck.com>
To: <idn@ops.ietf.org>
Sent: Tuesday, May 01, 2001 11:51 PM
Subject: [idn] requirements-05


> Marc, James, and Zita,
>
> I have just finished giving requirements-05 a careful read.  I
> suggest that it is not yet ready for the IESG, either
> substantively or editorially, although we are arguably getting
> close.  Contrary to normal practice, I'm including editorial
> comments at the bottom of this note, partially to suggest that
> few people have read it carefully.
>
> A few of these issues have already been spotted by others and
> I want to reinforce them and give the editors a more
> consolidated list.  Apologies if I have missed anything already
> noted by others.
>
>     --john
>
> ------------
>
> 1. Substantive.
>
> (i) Section 1, end of first paragraph.  I believe that it
> would be useful if the document made the "assumption" a bit
> more explicit by pointing out that there may not be consensus
> in the IETF community on that assumption and that several
> sections of the document, including the "definitions and
> conventions" are likely to be useful even if the assumption is
> false.
>
> (ii) Section 1.5, third bullet: "ip6.int" should be
> "ip6.arpa".
>
> (iii) Section 2.1, requirement [1], last sentence.  This
> statement appears to me to be inherently false.  Since
> internationalized domain names cannot be resolved (within
> existing protocols) today, it is an impossibility to require
> that any system that exists today must be able to continue
> resolving such names.
>
> (iv) Section 2.2, requirement [14].  It is not clear to me
> what this requirement means.  I believe that some of nameprep
> is intended precisely to reject some characters.  And the
> recent "testbed" introduction of registrations of dingbats and
> other symbols as domain names may call for further
> consideration of some of the related issues.  The requirement
> at least needs clarification.
>
> (v) Requirements [22] and [30] appear to me to be inconsistent
> and contradictory.  Case folding is ultimately just an
> equivalence rule.  [22] says that the equivalence rule must be
> the same globally.   [30] says that equivalence rules may
> differ by zone.  I don't think one can have it both ways.  Or,
> if I misunderstand what is intended, the text is badly in need
> of clarification.
>
> 2. Editorial
>
> (i) Section 1.1, second paragraph.  "trough" should presumably
> be "through"
>
> (ii) Section 1.2, third paragraph, last sentence.  The comma
> after "contexts" probably belongs after "document" or should
> be deleted or the sentence rewritten.
>
> (iii) Section 1.4, second bullet.  There is a missing right
> paranthesis matching the one before "listed".   And the final
> sentence should probably contain "what is being transferred",
> not "what are".
>
> (iv) Section 1.5, fourth bullet.  "who provides" should be
> "who provide" (hosts is plural) and I think "who" should be
> "which" unless those hosts are human.
>
> (v) Section 2.4.  There is no section 2.3, so this should
> probably be renumbered.
>
> (vi) There is certainly precedent for leaving this for the RFC
> Editor, but the references are not consistent about the
> ordering of author, title, rfc reference (where appropriate),
> and date.
>
>
>




From owner-idn@ops.ietf.org  Tue May  8 01:13:06 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA02032
	for <idn-archive@lists.ietf.org>; Tue, 8 May 2001 01:13:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14wzVs-000Mzg-00
	for idn-data@psg.com; Mon, 07 May 2001 21:54:20 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14wzVr-000Mza-00
	for idn@ops.ietf.org; Mon, 07 May 2001 21:54:19 -0700
Received: from bbprime.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id VAA24129;
	Mon, 7 May 2001 21:54:18 -0700
Message-Id: <5.1.0.14.2.20010507213529.01cd37b8@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 07 May 2001 21:38:26 -0700
To: Paul Hoffman / IMC <phoffman@imc.org>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] The WALID patent may not apply to IDNA
Cc: idn@ops.ietf.org
In-Reply-To: <p0510031cb71cfa60c81a@[165.227.249.20]>
References: <200105071840.OAA22629@astro.cs.utk.edu>
 <200105071840.OAA22629@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 06:36 PM 5/7/2001, Paul Hoffman / IMC wrote:
>If anyone who has read the patent would like to say why they think it 
>applies to IDNA, please do so. Otherwise, I propose that the working group 
>moves forward on IDNA and we ignore the WALID patent.


hmmm. ISOC/IETF have hired council before, concerning intellectual property 
issues.  given that some technically knowledgeable readers believe IDNA 
does not read on the Walid patent and given that there are reports of 
patent attorneys holding the same belief, perhaps we should request that an 
independent patent attorney be retained to offer an opinion?

Probably would cost $5,000-10,000.

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 May  8 01:47:10 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA05835
	for <idn-archive@lists.ietf.org>; Tue, 8 May 2001 01:47:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14x03m-000ODW-00
	for idn-data@psg.com; Mon, 07 May 2001 22:29:22 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14x03l-000ODQ-00
	for idn@ops.ietf.org; Mon, 07 May 2001 22:29:21 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id BAA26272;
        Tue, 8 May 2001 01:29:18 -0400 (EDT)
Message-Id: <200105080529.BAA26272@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Dave Crocker <dcrocker@brandenburg.com>
cc: Keith Moore <moore@cs.utk.edu>, idn@ops.ietf.org
Subject: Re: [idn] Assessing patent "validity" 
In-reply-to: Your message of "Mon, 07 May 2001 18:53:28 PDT."
             <5.1.0.14.2.20010507184722.01deb088@brandenburg.com> 
Date: Tue, 08 May 2001 01:29:17 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Evidently you misunderstood both of my major points:

and evidently you misunderstood mine.
 
>          1.  The IETF has no competence at assessing legal merit in an
> intellectual property conflict.

true.  but nevertheless, individuals within the IETF, who possess 
varying degrees of competence at assessing both the legal merit of 
a patent and the applicability of a patent toward a potential standard,
*DO* use whatever competence they possess (or lack thereof) to determine
whether to support a consensus toward that standard.

this is in fact the best we can do. 

>          2.  Passing a standard that has ambiguous and/or contested
> intellectual property claims, or ambiguous/contested licensing terms, is
> certain -- as in, guaranteed -- to scare vendors off from implementing the
> standard.

and this will also get factored in to whether individuals decide to 
contribute toward a consensus.

Keith



From owner-idn@ops.ietf.org  Tue May  8 03:12:07 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA16641
	for <idn-archive@lists.ietf.org>; Tue, 8 May 2001 03:12:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14x14F-000Pr1-00
	for idn-data@psg.com; Mon, 07 May 2001 23:33:55 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14x14E-000Pqu-00
	for idn@ops.ietf.org; Mon, 07 May 2001 23:33:54 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id CAA26852;
        Tue, 8 May 2001 02:33:50 -0400 (EDT)
Message-Id: <200105080633.CAA26852@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: Paul Hoffman / IMC <phoffman@imc.org>, idn@ops.ietf.org
Subject: Re: [idn] The WALID patent may not apply to IDNA 
In-reply-to: Your message of "Mon, 07 May 2001 21:38:26 PDT."
             <5.1.0.14.2.20010507213529.01cd37b8@dcrocker.net> 
Date: Tue, 08 May 2001 02:33:50 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> perhaps we should request that an
> independent patent attorney be retained to offer an opinion?

2026 is quite clear in this regard:
IETF does not take a position on such issues.
it's up to the individual participants to decide.

Keith



From owner-idn@ops.ietf.org  Tue May  8 03:25:37 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA16745
	for <idn-archive@lists.ietf.org>; Tue, 8 May 2001 03:25:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14x1a1-0000a6-00
	for idn-data@psg.com; Tue, 08 May 2001 00:06:45 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14x1Zx-0000Zx-00
	for idn@ops.ietf.org; Tue, 08 May 2001 00:06:42 -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 AAA26027;
	Tue, 8 May 2001 00:06:39 -0700
Message-Id: <5.1.0.14.2.20010508000257.03028290@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 08 May 2001 00:05:56 -0700
To: Keith Moore <moore@cs.utk.edu>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] The WALID patent may not apply to IDNA 
Cc: idn@ops.ietf.org
In-Reply-To: <200105080633.CAA26852@astro.cs.utk.edu>
References: <Your message of "Mon, 07 May 2001 21:38:26 PDT." <5.1.0.14.2.20010507213529.01cd37b8@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 11:33 PM 5/7/2001, Keith Moore wrote:
> > perhaps we should request that an independent patent attorney be 
> retained to offer an opinion?
>
>2026 is quite clear in this regard: IETF does not take a position on such 
>issues.  it's up to the individual participants to decide.

I must not be writing things clearly.

I did not suggest that the IETF take a formal position.

I suggested that it hire an independent attorney to offer one.

And it doesn't really matter whether the attorney is hired by the IETF or 
by some aggregation of companies that chip in a few dollars each.

One could even imagine it being done under the umbrella of some trade 
association that has the 5-10K available, as long as the mandate and 
obligations of the attorney are lined up properly.

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 May  8 09:12:40 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA20630
	for <idn-archive@lists.ietf.org>; Tue, 8 May 2001 09:12:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14x6oo-0007G3-00
	for idn-data@psg.com; Tue, 08 May 2001 05:42:22 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14x6on-0007Fx-00
	for idn@ops.ietf.org; Tue, 08 May 2001 05:42:21 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id IAA26442;
        Tue, 8 May 2001 08:42:17 -0400 (EDT)
Message-Id: <200105081242.IAA26442@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: Keith Moore <moore@cs.utk.edu>, idn@ops.ietf.org
Subject: Re: [idn] The WALID patent may not apply to IDNA 
In-reply-to: Your message of "Tue, 08 May 2001 00:05:56 PDT."
             <5.1.0.14.2.20010508000257.03028290@dcrocker.net> 
Date: Tue, 08 May 2001 08:42:17 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> I must not be writing things clearly.
> 
> I did not suggest that the IETF take a formal position.
> 
> I suggested that it hire an independent attorney to offer one.

I guess I think that this would be so close to having IETF offer
a formal position as to be essentially the same thing - or at least,
too easily confused with the same thing.  The last thing we need 
is for someone to accuse us of a process violation over this.

> And it doesn't really matter whether the attorney is hired by the IETF or
> by some aggregation of companies that chip in a few dollars each.

I don't see any problem with the latter.  Nor do I see any problem, if
WG participants have already consulted with counsel about this matter,
if they forward their attorneys' opinions to the list.

Keith



From owner-idn@ops.ietf.org  Tue May  8 11:56:05 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA29031
	for <idn-archive@lists.ietf.org>; Tue, 8 May 2001 11:56:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14x9RD-000B1F-00
	for idn-data@psg.com; Tue, 08 May 2001 08:30:11 -0700
Received: from femail4.sdc1.sfba.home.com ([24.0.95.84])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14x9RC-000B16-00
	for idn@ops.ietf.org; Tue, 08 May 2001 08:30:10 -0700
Received: from c1340594a ([65.11.104.12]) by femail4.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20010508152705.ONMT14836.femail4.sdc1.sfba.home.com@c1340594a>;
          Tue, 8 May 2001 08:27:05 -0700
Message-ID: <007b01c0d7d3$d2c0b5d0$0c680b41@c1340594a>
Reply-To: "Mark Davis" <mark@macchiato.com>
From: "Mark Davis" <markdavis34@home.com>
To: "John C Klensin" <klensin@jck.com>, "Kenneth Whistler" <kenw@sybase.com>
Cc: <idn@ops.ietf.org>
References: <1030420740.988872898@P2>
Subject: Re: [idn] Alternative Solutions
Date: Tue, 8 May 2001 08:30:29 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John has mentioned many other examples of prior art. I will mention one more
example: A paper given in 1997, encoding Unicode in barcodes. This is very
similar to the actual method used in WALID. There are 47 allowable values,
and it uses differencing (like xor) to typically get small values, then uses
a variable number of them.

B3: Ultracode: A Barcode Symbology Encoding Unicode 2.0, at:
http://www.unicode.org/iuc/iuc10/program.html

<opinion>
It is clear that the US Patent office has thrown in the towel, and is
resting on the courts to do their job for them. There is a massive amount of
prior art for the WALID patent.

Given that the PO doesn't do even the most casual research as to prior art,
even if the IETF chose an alternative -- and that alternative was
implemented -- the PO might even ignore that implementation and grant a
patent to some DILAW company after the fact. There is some non-zero
probability of that, probably near the probability that the WALID patent
would hold up in court.
</opinion>




From owner-idn@ops.ietf.org  Wed May  9 10:07:03 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA07396
	for <idn-archive@lists.ietf.org>; Wed, 9 May 2001 10:07:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14xU4W-0008oi-00
	for idn-data@psg.com; Wed, 09 May 2001 06:32:08 -0700
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14xU4V-0008ob-00
	for idn@ops.ietf.org; Wed, 09 May 2001 06:32:07 -0700
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06136;
	Wed, 9 May 2001 09:32:00 -0400 (EDT)
Message-Id: <200105091332.JAA06136@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-requirements-06.txt
Date: Wed, 09 May 2001 09:31:59 -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		: Requirements of Internationalized Domain Names
	Author(s)	: Z. Wenzel, J. Seng
	Filename	: draft-ietf-idn-requirements-06.txt
	Pages		: 8
	Date		: 08-May-01
	
This document describes the requirement for encoding international
characters into DNS names and records. This document is guidance for
developing protocols for internationalized domain names.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idn-requirements-06.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-requirements-06.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-requirements-06.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:	<20010508152301.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idn-requirements-06.txt

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

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

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Wed May  9 22:03:23 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA01930
	for <idn-archive@lists.ietf.org>; Wed, 9 May 2001 22:03:21 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14xfW6-000J1L-00
	for idn-data@psg.com; Wed, 09 May 2001 18:45:22 -0700
Subject: [idn] FW: I-D ACTION:draft-skwan-utf8-dns-06.txt
Date: Wed, 9 May 2001 16:08:13 -0700
From: "Levon Esibov" <levone@windows.microsoft.com>
To: <idn@ops.ietf.org>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E14xfW6-000J1L-00@psg.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C0D8DC.EC42554C
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

FYI:

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20
Sent: Wednesday, May 09, 2001 6:32 AM
Subject: I-D ACTION:draft-skwan-utf8-dns-06.txt

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


Title : Using the UTF-8 Character Set in the Domain
Name=20
                          System
Author(s) : S. Kwan, J. Gilroy, L. Esibov
Filename : draft-skwan-utf8-dns-06.txt
Pages : 8
Date : 08-May-01
=09
The Domain Name System standard specifies that names are represented
using the ASCII character encoding.  This docuent expands that
specification to allow the use of the UTF-8 character encoding, a
superset of ASCII and a translation of the UCS-2 character encoding.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-skwan-utf8-dns-06.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-skwan-utf8-dns-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html=20
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-skwan-utf8-dns-06.txt".
=09
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.
=09
=09
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

------_=_NextPart_001_01C0D8DC.EC42554C
Content-Type: application/octet-stream;
name="ATT46668.TXT"
Content-Transfer-Encoding: base64
Content-Description: ATT46668.TXT
Content-Disposition: attachment;
filename="ATT46668.TXT"

Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7DQoJYWNjZXNzLXR5cGU9Im1h
aWwt
c2VydmVyIjsNCglzZXJ2ZXI9Im1haWxzZXJ2QGlldGYub3JnIg0KDQpDb250ZW50LVR5cGU6
IHRl
eHQvcGxhaW4NCkNvbnRlbnQtSUQ6CTwyMDAxMDUwODE1MjI0MS5JLURAaWV0Zi5vcmc+DQoN
CkVO
Q09ESU5HIG1pbWUNCkZJTEUgL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1za3dhbi11dGY4LWRu
cy0w
Ni50eHQNCg==

------_=_NextPart_001_01C0D8DC.EC42554C
Content-Type: application/octet-stream;
name="draft-skwan-utf8-dns-06.URL"
Content-Transfer-Encoding: base64
Content-Description: draft-skwan-utf8-dns-06.URL
Content-Disposition: attachment;
filename="draft-skwan-utf8-dns-06.URL"

W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRy
YWZ0
cy9kcmFmdC1za3dhbi11dGY4LWRucy0wNi50eHQNCg==

------_=_NextPart_001_01C0D8DC.EC42554C--






From owner-idn@ops.ietf.org  Fri May 11 18:24:54 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA22063
	for <idn-archive@lists.ietf.org>; Fri, 11 May 2001 18:24:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14yKrJ-0005XD-00
	for idn-data@psg.com; Fri, 11 May 2001 14:54:01 -0700
Received: from tce-e-7-182-12.bta.net.cn ([202.106.182.12] helo=china.com)
	by psg.com with smtp (Exim 3.16 #1)
	id 14yKrH-0005X6-00
	for idn@ops.ietf.org; Fri, 11 May 2001 14:54:00 -0700
Received: from china.com([10.1.7.101]) by china.com(AIMC 2.9.5.1)
	with SMTP id jm63afc72ba; Sat, 12 May 2001 05:53:54 +0800
Received: from loki.ietf.org([132.151.1.177]) by china.com(AIMC 2.9.5.1)
	with SMTP id jm7c3afbcaf2; Fri, 11 May 2001 14:52:34 +0800
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id LAA14539
	for ietf-123-outbound.02@ietf.org; Wed, 9 May 2001 11:35: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 JAA13251
	for <all-ietf@loki.ietf.org>; Wed, 9 May 2001 09:32:04 -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 JAA06136;
	Wed, 9 May 2001 09:32:00 -0400 (EDT)
Message-Id: <200105091332.JAA06136@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-requirements-06.txt
Date: Wed, 09 May 2001 09:31:59 -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		: Requirements of Internationalized Domain Names
	Author(s)	: Z. Wenzel, J. Seng
	Filename	: draft-ietf-idn-requirements-06.txt
	Pages		: 8
	Date		: 08-May-01
	
This document describes the requirement for encoding international
characters into DNS names and records. This document is guidance for
developing protocols for internationalized domain names.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idn-requirements-06.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-requirements-06.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-requirements-06.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:	<20010508152301.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idn-requirements-06.txt

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

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

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Fri May 11 18:43:29 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA22327
	for <idn-archive@lists.ietf.org>; Fri, 11 May 2001 18:43:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14yLSp-000683-00
	for idn-data@psg.com; Fri, 11 May 2001 15:32:47 -0700
Received: from df-inet1.exchange.microsoft.com ([131.107.8.8])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14yLSo-00067x-00
	for idn@ops.ietf.org; Fri, 11 May 2001 15:32:46 -0700
Received: from df-virus2.platinum.corp.microsoft.com ([172.30.236.33]) by df-inet1.exchange.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Fri, 11 May 2001 15:33:30 -0700
Received: from 172.30.236.11 by df-virus2.platinum.corp.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 11 May 2001 15:32:41 -0700 (Pacific Daylight Time)
Received: from DINO.platinum.corp.microsoft.com ([172.30.236.101]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Fri, 11 May 2001 15:32:41 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: [idn] iDNS transition: end-system vs. infrastructure?
Date: Fri, 11 May 2001 15:32:40 -0700
Message-ID: <DE1B1F489EDD6D4C9A0118DC3F6C3E730329FD43@DINO.platinum.corp.microsoft.com>
Thread-Topic: [idn] iDNS transition: end-system vs. infrastructure?
Thread-Index: AcDXEtX4bXGNTNHDQr6vQozQvlpBCgAA9LnQ
From: "Russ Rolfe" <rrolfe@exchange.microsoft.com>
To: "Dave Crocker" <dcrocker@brandenburg.com>, <idn@ops.ietf.org>
X-OriginalArrivalTime: 11 May 2001 22:32:41.0667 (UTC) FILETIME=[4A70D130:01C0DA6A]
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA22327

Dave Crocker wrote: 7 May 2001

         Hence, the primary concern for "just do pure UTF-8" is
> the effect of sending UTF-8 to an aDNS server.  However the nature of 
> DNS is such that a DNS field with a UTF-8 string only gets sent to a 
> server that is supposed to be able to resolve the that field.

Since we are looking at alternatives depending on the Walid proposal and
"just do pure UTF-8" is an alternative, could someone kindly post a
simple list of the reasons they feel "Just do pure UTF-8" is *not* a
valid alternative.  I am still not convinced that we should not just use
pure UTF-8.

Regards, Russ Rolfe
Microsoft



From owner-idn@ops.ietf.org  Fri May 11 19:04:09 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22505
	for <idn-archive@lists.ietf.org>; Fri, 11 May 2001 19:04:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14yLlV-0006Sk-00
	for idn-data@psg.com; Fri, 11 May 2001 15:52:05 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14yLlU-0006Sd-00
	for idn@ops.ietf.org; Fri, 11 May 2001 15:52: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 SAA16457;
        Fri, 11 May 2001 18:51:50 -0400 (EDT)
Message-Id: <200105112251.SAA16457@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Russ Rolfe" <rrolfe@exchange.microsoft.com>
cc: "Dave Crocker" <dcrocker@brandenburg.com>, idn@ops.ietf.org
Subject: Re: [idn] iDNS transition: end-system vs. infrastructure? 
In-reply-to: Your message of "Fri, 11 May 2001 15:32:40 PDT."
             <DE1B1F489EDD6D4C9A0118DC3F6C3E730329FD43@DINO.platinum.corp.microsoft.com> 
Date: Fri, 11 May 2001 18:51:50 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> could someone kindly post a
> simple list of the reasons they feel "Just do pure UTF-8" is *not* a
> valid alternative.  I am still not convinced that we should not just use
> pure UTF-8.

we cannot use pure UTF-8 because non-IDN-aware applications will still 
need to be able to lookup ACE-encoded IDNs.

so while we could have a pure UTF-8 query interface to look up IDNs,
we would still need the ACE query interface also.  and we'd want the
two to produce consistent results.

but we should be careful about using the patent as justification for
adding another query interface.  as far as I can tell IDNA doesn't 
infringe on the patent anyway.

Keith



From owner-idn@ops.ietf.org  Fri May 11 19:12:45 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22655
	for <idn-archive@lists.ietf.org>; Fri, 11 May 2001 19:12:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14yLvI-0006de-00
	for idn-data@psg.com; Fri, 11 May 2001 16:02:12 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14yLvH-0006dY-00
	for idn@ops.ietf.org; Fri, 11 May 2001 16:02:11 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 14yLvG-00007V-00; Fri, 11 May 2001 16:02:10 -0700
Date: Fri, 11 May 2001 23:02:10 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] iDNS transition: end-system vs. infrastructure?
Message-ID: <20010511230208.C32401@arwen.cs.berkeley.edu>
References: <DE1B1F489EDD6D4C9A0118DC3F6C3E730329FD43@DINO.platinum.corp.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <DE1B1F489EDD6D4C9A0118DC3F6C3E730329FD43@DINO.platinum.corp.microsoft.com>; from rrolfe@exchange.microsoft.com on Fri, May 11, 2001 at 03:32:40PM -0700
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Russ Rolfe <rrolfe@exchange.microsoft.com> wrote:

> could someone kindly post a simple list of the reasons they feel "Just
> do pure UTF-8" is *not* a valid alternative.

Domain names appearing in message headers, SMTP commands, URIs, etc. are
required by various standards to contain only ASCII letters, digits,
hyphens, and dots.  Therefore there is no telling what existing software
would do if faced with domain names containing other characters.  Some
of it would surely break.  DNS is not the problem.

AMC



From owner-idn@ops.ietf.org  Sat May 12 08:16:54 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA15645
	for <idn-archive@lists.ietf.org>; Sat, 12 May 2001 08:16:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14yXyb-000Jkh-00
	for idn-data@psg.com; Sat, 12 May 2001 04:54:25 -0700
Received: from ns.jck.com ([209.187.148.211] helo=A4.JCK.COM)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14yXya-000JkU-00
	for idn@ops.ietf.org; Sat, 12 May 2001 04:54:24 -0700
Received: from P2 ("port 2332"@[209.187.148.217])
 by a4.jck.com (PMDF V6.0-24 #44844) with ESMTP id <0GD800FGI12MS8@a4.jck.com>
 for idn@ops.ietf.org; Sat, 12 May 2001 07:54:22 -0400 (EDT)
Date: Sat, 12 May 2001 07:54:21 -0400
From: John C Klensin <klensin@jck.com>
Subject: Re: [idn] iDNS transition: end-system vs. infrastructure?
In-reply-to: <200105112251.SAA16457@astro.cs.utk.edu>
To: Keith Moore <moore@cs.utk.edu>
Cc: idn@ops.ietf.org
Message-id: <1811583540.989654061@P2>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.8 (Win32)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Friday, 11 May, 2001 18:51 -0400 Keith Moore
<moore@cs.utk.edu> wrote:

>> could someone kindly post a
>> simple list of the reasons they feel "Just do pure UTF-8" is
>> *not* a valid alternative.  I am still not convinced that we
>> should not just use pure UTF-8.
> 
> we cannot use pure UTF-8 because non-IDN-aware applications
> will still  need to be able to lookup ACE-encoded IDNs.

Keith,

While I agree -- for the reasons mentioned by Adam and that I'm
sure will be repeated and expanded upon by others-- that "just
send UTF-8" is a bad idea, I'm not sure the above follows.

We have approaches --the "use a different DNS Class" idea is
certainly one example-- which would prevent a non-IDN-aware
application from ever encountering an IDN in a context in which
being able to resolve it is a reasonable expectation.  And
having an application that is completely non-IDN-aware handle
ACE-type IDNs correctly (with IDNA or otherwise), is likely, but
not certain, to bypass unanticipated problems.

So I would contend that the community actually has to make a
choice here, a choice among:

	(i) A family of solutions, including "just send UTF-8"
	which expose non-IDN-aware applications to things they
	almost certainly are not expecting and which, given our
	experience, are likely to cause application problems.
	Showing otherwise would require analysis of all
	implementations of all applications, which is roughly
	equivalent to proving a universal negative.  And, with
	the understanding that this is an observation, not a
	slam, I would assume that anyone with experience with
	applications and operating systems that respond to
	unexpected conditions and data formats with blue screens
	would be particularly sensitive to this sort of problem.
	
	(ii) A family of solutions, including IDNA and
	presumably most of the other ACE-based ideas, that
	attempts to encode the IDN data so that it will slip by
	non-IDN-aware applications, databases, and systems.
	These solutions are, I think clearly, less likely to
	exhibit serious problems than those in the first group,
	but there are still risks.   And some of the human
	interface, and text-imbedded-in-document, issues seem to
	me quite daunting.  The community could conclude that
	the advantages (including a form of quick deployment
	that does not change the DNS and leaves applications on
	their own) are a good compromise with the risks, but the
	approaches are still compromises with risk.
	
	(iii) A family of solutions that are "no risk", because
	their designs prevent non-IDN-aware applications from
	ever seeing an IDN in a DNS context.  If a putative URL
	appears in running text, the application can either cope
	with it or not, but, if it tries to do something with it
	and violates its own rules about what it can handle and
	pass to the DNS, that is clearly a problem with that
	application (not just failure to upgrade).  And, with
	these solutions, DNS queries and responses from
	non-upgraded applications just will not involve IDNs.  

The solutions in the third group, which might be characterized
as "not in Class=IN" or "not in the DNS", or "need to fully
negotiate first" (as far is I know, we don't have any plausible
ones of the latter on the table, but they are logically
possible) have the clear disadvantage that they require serious
deployment to work for the people/ language groups/ countries
that need IDNs.  So they are not quick fixes.  But some of them
provide functionality, possibly critical functionally (such as
imprecise search), that neither of the other two groups do.  So,
again, it is a tradeoff.

But let's avoid assuming that the second group of approaches are
the only alternative to the first and, hence, that applications
will need to handle ACE names no matter what.

   john




From owner-idn@ops.ietf.org  Sat May 12 10:40:34 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA17462
	for <idn-archive@lists.ietf.org>; Sat, 12 May 2001 10:40:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14yaEd-000LsO-00
	for idn-data@psg.com; Sat, 12 May 2001 07:19:07 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14yaEb-000LsH-00
	for idn@ops.ietf.org; Sat, 12 May 2001 07:19:06 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4CEJQc90267
	for <idn@ops.ietf.org>; Sat, 12 May 2001 10:19:26 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105121419.f4CEJQc90267@nic-naa.net>
To: idn@ops.ietf.org
Subject: [idn] Re: I-D ACTION:draft-ietf-idn-requirements-06.txt
Date: Sat, 12 May 2001 10:19:25 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

53: s/altho/although

Who cares in a WG requirements draft if a current assumption may not yet
or ever enjoy the celebrated status of the consensus of the IETF community?
We're here to solve a problem _caused_ by some prior consensus, a statement
of work not unique to this WG. Compare, v4 vs v6.

Also, at 49, s/item/protocol/.

496-502 [30]

Just what does a change from MUST to MAY accomplish? This doesn't remove the
(argued) problem of zone-specific semantics. MUST NOT would have accomplished
that. The original motivation for [30] appeares to have been either forgotten
or mislaid, and weakening it isn't the same as removing it, or restating it.

Note to the authors: My query of 30 April is appended.

651: s/<</</.

Cheers,
Eric

------- Forwarded Message


Message-Id: <200104301212.f3UCCkc16114@nic-naa.net>
To: zita@isi.edu, jseng@pobox.org.sg
cc: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>,
   idn@ops.ietf.org, brunner@nic-naa.net
Subject: [idn] Clarification, draft-ietf-idn-requirements-0?.txt, [30]
Date: Mon, 30 Apr 2001 08:12:46 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Authors,

Would you do me the kindness of reminding me who proposed the current text
of General Requirements, item [30]? I'd like to know what use case(s) were
offered to motivate this manditory-to-implement (zone manager definition of
equivalency rules) requirement.

Tia,
Eric


------- End of Forwarded Message




From owner-idn@ops.ietf.org  Sat May 12 13:37:16 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA18641
	for <idn-archive@lists.ietf.org>; Sat, 12 May 2001 13:37:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14yd6w-000OwS-00
	for idn-data@psg.com; Sat, 12 May 2001 10:23:22 -0700
Received: from ns.jck.com ([209.187.148.211] helo=A4.JCK.COM)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14yd6v-000OwM-00
	for idn@ops.ietf.org; Sat, 12 May 2001 10:23:21 -0700
Received: from P2 ("port 1057"@[209.187.148.217])
 by a4.jck.com (PMDF V6.0-24 #44844) with ESMTP id <0GD800F1BGAVZT@a4.jck.com>
 for idn@ops.ietf.org; Sat, 12 May 2001 13:23:20 -0400 (EDT)
Date: Sat, 12 May 2001 13:23:18 -0400
From: John C Klensin <klensin@jck.com>
Subject: Re: [idn] Re: I-D ACTION:draft-ietf-idn-requirements-06.txt
In-reply-to: <200105121419.f4CEJQc90267@nic-naa.net>
To: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Cc: idn@ops.ietf.org
Message-id: <1831320900.989673798@P2>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.8 (Win32)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Saturday, 12 May, 2001 10:19 -0400 Eric Brunner-Williams in
Portland Maine <brunner@nic-naa.net> wrote:

>...
> 496-502 [30]
> 
> Just what does a change from MUST to MAY accomplish? This
> doesn't remove the (argued) problem of zone-specific
> semantics. MUST NOT would have accomplished that. The original
> motivation for [30] appeares to have been either forgotten or
> mislaid, and weakening it isn't the same as removing it, or
> restating it.

I want to reinforce Eric's point here, but from a slightly
different direction.  Often, especially with application
protocols, we permit "MAY" specifications because we really do
not care whether a feature is supported.  But, with something
like the DNS, interoperability is everything.  To say "MAY" in
the DNS context is to say "maybe someone will do this, maybe
they won't, but, if all of the client, authoritative server,
secondary servers, and any caches don't make the same decision,
things won't work consistently and as expected.   And that is
essentially equivalent to saying "if is ok if we don't have
interoperation in this area".  

I don't see that as acceptable, at least unless there is a clear
default strategy that is required and failures in interworking
with a "may implement" option or variation are so designed so
that the need for, and operation of, the fallback to that
default behavior are clear.

And I do not see [30] as meeting that sort of criteria.

   john





From owner-idn@ops.ietf.org  Sat May 12 15:51:29 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA19502
	for <idn-archive@lists.ietf.org>; Sat, 12 May 2001 15:51:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14yfGF-0001ON-00
	for idn-data@psg.com; Sat, 12 May 2001 12:41:07 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14yfGE-0001OH-00
	for idn@ops.ietf.org; Sat, 12 May 2001 12:41:06 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 14yfGD-0000xb-00; Sat, 12 May 2001 12:41:05 -0700
Date: Sat, 12 May 2001 19:41:05 +0000
To: idn working group <idn@ops.ietf.org>
Subject: Re: [idn] iDNS transition: end-system vs. infrastructure?
Message-ID: <20010512194105.A3633@arwen.cs.berkeley.edu>
References: <200105112251.SAA16457@astro.cs.utk.edu> <1811583540.989654061@P2>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <1811583540.989654061@P2>; from klensin@jck.com on Sat, May 12, 2001 at 07:54:21AM -0400
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

John C Klensin <klensin@jck.com> wrote:

>  (iii) A family of solutions that are "no risk", because their designs
>  prevent non-IDN-aware applications from ever seeing an IDN in a DNS
>  context.
>
> But let's avoid assuming...that applications will need to handle ACE
> names no matter what.

Could you elaborate on this, with examples?  What sorts of things
would occupy the domain name position in a message header field, or
an SMTP command, or a URI?  Does family (iii) entail revising every
protocol/format that embeds domain names?

What about the case where I send an email message to two people, and one
of them has an IDN address and the other is using a mail program that
predates IDN.  Can the latter reply to all of us?

I might not be understanding what you have in mind, but (iii) looks
difficult to deploy without a lot of effort/pain.

AMC



From owner-idn@ops.ietf.org  Sat May 12 16:45:01 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA20061
	for <idn-archive@lists.ietf.org>; Sat, 12 May 2001 16:45:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14yg5V-0002Lp-00
	for idn-data@psg.com; Sat, 12 May 2001 13:34:05 -0700
Received: from ns.jck.com ([209.187.148.211] helo=A4.JCK.COM)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14yg5U-0002Lj-00
	for idn@ops.ietf.org; Sat, 12 May 2001 13:34:05 -0700
Received: from P2 ("port 1139"@[209.187.148.217])
 by a4.jck.com (PMDF V6.0-24 #44844) with ESMTP id <0GD800F2RP4QZT@a4.jck.com>
 for idn@ops.ietf.org; Sat, 12 May 2001 16:34:03 -0400 (EDT)
Date: Sat, 12 May 2001 16:34:01 -0400
From: John C Klensin <klensin@jck.com>
Subject: Re: [idn] iDNS transition: end-system vs. infrastructure?
In-reply-to: <20010512194105.A3633@arwen.cs.berkeley.edu>
To: "Adam M. Costello" <amc@cs.berkeley.edu>
Cc: idn working group <idn@ops.ietf.org>
Message-id: <1842763860.989685241@P2>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.8 (Win32)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Saturday, 12 May, 2001 19:41 +0000 "Adam M. Costello"
<amc@cs.berkeley.edu> wrote:

> John C Klensin <klensin@jck.com> wrote:
> 
>>  (iii) A family of solutions that are "no risk", because
>>  their designs prevent non-IDN-aware applications from ever
>>  seeing an IDN in a DNS context.
>> 
>> But let's avoid assuming...that applications will need to
>> handle ACE names no matter what.
> 
> Could you elaborate on this, with examples?  What sorts of
> things would occupy the domain name position in a message
> header field, or an SMTP command, or a URI?

Depends on which member of family (iii) one picks.  

The notion of using a different DNS class (see
draft-klensin-i18n-newclass-... for some discussion; I gather a
more detailled document is coming) is in this family.  If that
were chosen, the answer in all the cases you list would be "DNS
name", but DNS name in a class that would not be used by
non-IDN-aware applications.   If those names were passed to a
non-IDN-aware app, they would presumably be rejected as improper
format if they were in UTF-8 format and passed through with a
"Class=IN" query in ACE-ish formats (or if UTF-8 slipped
through), after which they would get NODOMAIN responses.

At least some of the "directory" / "search system" / "keyword"
approaches also fall into family (iii).  See
draft-klensin-dns-role-... for some discussion of them and watch
for a new and more extensive document/ discussion RSN.  Those
assume that we would gradually migrate all applications that
reference objects using "words" or "names" or "service marks"
--rather than protocol identifiers for network objects-- to
utilize an intermediate layer (or two) whose behavior more
closely matches the expectations of normal users.  I.e.,
searching, imprecise matches, and, generally, a "when in doubt,
ask the user" strategy would be possible and normal.   That, of
course, requires changing not only the code of all of those
applications, but their user interface design.  Large deployment
problem, but possibly the right solution in the long term...
indeed, possibly that only one that will be seen as "working" in
the long term.

  Does family (iii)
> entail revising every protocol/format that embeds domain names?

And worse in some cases.  See above.

> What about the case where I send an email message to two
> people, and one of them has an IDN address and the other is
> using a mail program that predates IDN.  Can the latter reply
> to all of us?

Most likely not, at least without going to some effort.  On the
other hand, this is not necessarily bad news either.  It
encourages those who need to communicate to upgrade, just as the
relative invisibility of new hosts being added to the Internet
was one of the things that finally got people moving on DNS
deployment.  Specifically, if I sent mail to two people, one of
whom had a DNS-only address (possibly with MX records) and the
other one of whom was still using host tables, the latter could
not reply to me and the other correspondent without going
through a more or less complicated drill to translate the DNS
name into an address.  So we have been there before, with what I
would contend was a very similar situation, and we survived it.

> I might not be understanding what you have in mind, but (iii)
> looks difficult to deploy without a lot of effort/pain.

I have carefully not claimed otherwise.  The difficulties with
(i) and (ii) is that they

* Risk considerable damage and subtle interoperability problems
that users can't work around (note that the Hosttable-DNS
transition example above is a case where we have worked examples
of a transition situation the user can work around)

* Arguably don't solve the problem.  As long as there is a
single case in which the result produced by nameprep may be
debatably wrong from the standpoint of a user (characters that
match across scripts and different treatments of case matching
are likely candidate problem areas here, but there are others),
or in which mapping rules are required that may be complex, not
one-one, or that may have heuristic properties, we are sooner or
later going to need something with "search" or "fuzzy match",
not just "lookup" properties.   

The DNS can't do that, and that makes the question one of "if we
have to deploy an 'other layer' solution eventually --including
all those application changes-- do we really help ourselves by
putting complex and risky solutions into the DNS?".  I have
opinions about the answer to that question, but wouldn't claim
to have any certainty about the correct answer.

    john




From owner-idn@ops.ietf.org  Sat May 12 17:53:15 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA20439
	for <idn-archive@lists.ietf.org>; Sat, 12 May 2001 17:53:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14yh8m-0003XS-00
	for idn-data@psg.com; Sat, 12 May 2001 14:41:32 -0700
Received: from [216.177.8.114] (helo=ayna.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14yh8m-0003XM-00
	for idn@ops.ietf.org; Sat, 12 May 2001 14:41:32 -0700
Received: (from nobody@localhost)
	by ayna.com (8.9.3/8.9.3) id SAA10871
	for idn@ops.ietf.org; Sat, 12 May 2001 18:06:50 -0400
To: idn working group <idn@ops.ietf.org>
Subject: Re: [idn] iDNS transition: end-system vs. infrastructure?
Message-ID: <989705210.3afdb3fa76d45@www.bareed.ayna.com>
Date: Sat, 12 May 2001 18:06:50 -0400 (EDT)
From: Adonis El Fakih <adonis@ayna.com>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: Ayna VER 2.22 
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi,

I agree that there are various protocols that will need to be addressed case by case and examine the UTF8, UTF7, UCS2 or ACE solutions.

It would be easier if we can make a list of protocols/applications that will be affected by internationalized domain names (idn).  I feel this would be the first step to make sure we did not skip any protocol/application in the process of evaluating  what is the best solution.

>From the top of my head I can think of
HTTP requests -> DNS
Mail Clients -> SMTP or SMTP-8
Ftp CLients -> ASCII??
News Clients -> NNTP
IMAP CLients -> IMAP
POP CLients -> POP

Although we are looking at what technology to use be it plain UTF8, ACE or something in between, we also need to remember that the protocols we know today will slowly shift to support IDN, and in some cases some will never do. 

I am sorry that I am trying to go to the basics, becuase both UTF8 and ACE solutions seem to be good depending on what apps we are talkign about, so if we define apps/protocols we are trying to make word with IDN, we may also have to introduce a time frame on using one or the other. i.e. it may be that ACE is the best way to implement something now, but then put recommendations forward that all new versions of each protocol should work with UTF8, becasuse ACE also has its drawbacks.  In a way we are trying to map old systems to work with Unicode and future applications, and we want to force the additions of new value added data within the limited scope of 7bit ASCII to be fully backward compliant.

Sorry for the ranting. and Thanks.
Adonis



"Adam M. Costello" <amc@cs.berkeley.edu> ßÊÈ:

> Russ Rolfe <rrolfe@exchange.microsoft.com> wrote:

> could someone kindly post a simple list of the reasons they feel "Just
> do pure UTF-8" is *not* a valid alternative.

Domain names appearing in message headers, SMTP commands, URIs, etc. are
required by various standards to contain only ASCII letters, digits,
hyphens, and dots.  Therefore there is no telling what existing software
would do if faced with domain names containing other characters.  Some
of it would surely break.  DNS is not the problem.

AMC




______________________________________________________________
Ayna, The Arabic Internet Starts Here.     http://www.ayna.com



From owner-idn@ops.ietf.org  Sat May 12 21:28:13 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA21993
	for <idn-archive@lists.ietf.org>; Sat, 12 May 2001 21:28:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14ykQr-0007ao-00
	for idn-data@psg.com; Sat, 12 May 2001 18:12:25 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14ykQp-0007ai-00
	for idn@ops.ietf.org; Sat, 12 May 2001 18:12:24 -0700
Received: from jamessonyvaio (hs0216.singnet.com.sg [165.21.194.229])
	by mail.i-dns.net (Postfix) with SMTP
	id 6FE2AFFC06; Sun, 13 May 2001 09:15:06 +0800 (SGT)
Message-ID: <008401c0db49$a7307440$0201000a@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "John C Klensin" <klensin@jck.com>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
References: <1831320900.989673798@P2>
Subject: Re: [idn] Re: I-D ACTION:draft-ietf-idn-requirements-06.txt
Date: Sun, 13 May 2001 09:11:30 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

If changing MUST to MAY is not acceptable, then please kindly forward
the appropriate wording changes.

ps: [14] and [30] are in conflict. We knew it all the time. There is a
tag which say it is in conflict from -01 to -04 but no one mention it
until now.

-James Seng

----- Original Message -----
From: "John C Klensin" <klensin@jck.com>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>
Sent: Sunday, May 13, 2001 1:23 AM
Subject: Re: [idn] Re: I-D ACTION:draft-ietf-idn-requirements-06.txt


> --On Saturday, 12 May, 2001 10:19 -0400 Eric Brunner-Williams in
> Portland Maine <brunner@nic-naa.net> wrote:
>
> >...
> > 496-502 [30]
> >
> > Just what does a change from MUST to MAY accomplish? This
> > doesn't remove the (argued) problem of zone-specific
> > semantics. MUST NOT would have accomplished that. The original
> > motivation for [30] appeares to have been either forgotten or
> > mislaid, and weakening it isn't the same as removing it, or
> > restating it.
>
> I want to reinforce Eric's point here, but from a slightly
> different direction.  Often, especially with application
> protocols, we permit "MAY" specifications because we really do
> not care whether a feature is supported.  But, with something
> like the DNS, interoperability is everything.  To say "MAY" in
> the DNS context is to say "maybe someone will do this, maybe
> they won't, but, if all of the client, authoritative server,
> secondary servers, and any caches don't make the same decision,
> things won't work consistently and as expected.   And that is
> essentially equivalent to saying "if is ok if we don't have
> interoperation in this area".
>
> I don't see that as acceptable, at least unless there is a clear
> default strategy that is required and failures in interworking
> with a "may implement" option or variation are so designed so
> that the need for, and operation of, the fallback to that
> default behavior are clear.
>
> And I do not see [30] as meeting that sort of criteria.
>
>    john
>
>
>




From owner-idn@ops.ietf.org  Sat May 12 22:17:40 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA23234
	for <idn-archive@lists.ietf.org>; Sat, 12 May 2001 22:17:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14ylFN-0008bG-00
	for idn-data@psg.com; Sat, 12 May 2001 19:04:37 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14ylFM-0008b9-00
	for idn@ops.ietf.org; Sat, 12 May 2001 19:04:36 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4D24xc91829;
	Sat, 12 May 2001 22:04:59 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105130204.f4D24xc91829@nic-naa.net>
To: "James Seng/Personal" <James@Seng.cc>
cc: "John C Klensin" <klensin@jck.com>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Re: I-D ACTION:draft-ietf-idn-requirements-06.txt 
In-Reply-To: Your message of "Sun, 13 May 2001 09:11:30 +0800."
             <008401c0db49$a7307440$0201000a@jamessonyvaio> 
Date: Sat, 12 May 2001 22:04:58 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Mr. Seng,

It is not. When the authors respond to my question I'll be in a position to
judge which change to suggest. Mr. Klensin is quite capable of offering yet
another suggestion.

If you would be so kind as to provide a pointer to the versions which had a
conflict with [30] I would appreciate it. I don't have -01 - -04 at hand (if
I ever did), and never would have noticed [30] if momentary circumstances had
not given me pause to think. I trust you don't mean CCS or CES or charset
uniqueness. If you ment the -06 [17], then there is a possible overlap of
requirements with -06 [30]. My longer note to Jony covered this, the use of
"8" (digit) as a alpha-tuple in Algonquin family orthographies, e.g., in the
Canadian Maritimes, Northern New England and Quebec -- W8banakia. Of course
-06 [17] can be read as flatly contradicting -06 [30].

I'm at a loss as to what to make of your sudden politness.

Eric



From owner-idn@ops.ietf.org  Sun May 13 01:56:59 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA02533
	for <idn-archive@lists.ietf.org>; Sun, 13 May 2001 01:56:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14yoZK-000CZJ-00
	for idn-data@psg.com; Sat, 12 May 2001 22:37:26 -0700
Received: from ns.jck.com ([209.187.148.211] helo=A4.JCK.COM)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14yoZJ-000CZD-00
	for idn@ops.ietf.org; Sat, 12 May 2001 22:37:25 -0700
Received: from P2 ("port 1375"@[209.187.148.217])
 by a4.jck.com (PMDF V6.0-24 #44844) with ESMTP id <0GD900F6LEABZT@a4.jck.com>
 for idn@ops.ietf.org; Sun, 13 May 2001 01:37:23 -0400 (EDT)
Date: Sun, 13 May 2001 01:37:22 -0400
From: John C Klensin <klensin@jck.com>
Subject: Re: [idn] Re: I-D ACTION:draft-ietf-idn-requirements-06.txt
In-reply-to: <008401c0db49$a7307440$0201000a@jamessonyvaio>
To: James Seng/Personal <James@Seng.cc>
Cc: idn@ops.ietf.org
Message-id: <1875364670.989717842@P2>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.8 (Win32)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On Sunday, 13 May, 2001 09:11 +0800 "James Seng/Personal"
<James@Seng.cc> wrote:

Taking your comments in reverse order...

> ps: [14] and [30] are in conflict. We knew it all the time.
> There is a tag which say it is in conflict from -01 to -04 but
> no one mention it until now.

Well, I mentioned it when I noticed it hadn't been straightened
out by -05, having assumed that it was under consideration.   It
needs to be fixed.  I think, personally, it needs to be fixed by
dropping [30] and any notion of zone-dependent (zone-variant)
resolution from the requirements.  I would be happier with a
requirement that said, more or less "you MUST not even
contemplate that idea", but I'd settle for dropping [30].  

But the WG needs to decide what it wants to do here.  I would
note that some localization-dependent (not
zone-structure-dependent) options/ variations are possible, but
more likely in a search environment (see my note to Adam) than
anything having to do with DNS server operations.   But the
document doesn't say that.

> If changing MUST to MAY is not acceptable, then please kindly
> forward the appropriate wording changes.

From my point of view, the "appropriate wording change" is to
lose [30] --and any other notion of different things happening
in different zones-- entirely.  Zone-dependent stuff assumes
that one can tie DNS hierarchy to specific languages or
character sets.  That is, obviously, possible in a few cases,
but only at the cost of chaos for multilingual countries, groups
in the relevant countries/ zones who use other languages and
conventions, and overlaying orthogonal semantic structure on the
administrative structure of the DNS -- just can't work in the
general case or the long term, however much some groups might
want it.

If the WG doesn't want to drop [30], then it needs to figure out
how to resolve the conflict/ contradiction in some other way.
Once it does, we can work on text.

    john




From owner-idn@ops.ietf.org  Mon May 14 16:52:36 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA24455
	for <idn-archive@lists.ietf.org>; Mon, 14 May 2001 16:52:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14zOxb-000BhX-00
	for idn-data@psg.com; Mon, 14 May 2001 13:28:55 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14zOxa-000BhQ-00
	for idn@ops.ietf.org; Mon, 14 May 2001 13:28:54 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id QAA26992;
        Mon, 14 May 2001 16:28:17 -0400 (EDT)
Message-Id: <200105142028.QAA26992@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: John C Klensin <klensin@jck.com>
cc: Keith Moore <moore@cs.utk.edu>, idn@ops.ietf.org
Subject: Re: [idn] iDNS transition: end-system vs. infrastructure? 
In-reply-to: Your message of "Sat, 12 May 2001 07:54:21 EDT."
             <1811583540.989654061@P2> 
Date: Mon, 14 May 2001 16:28:17 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > we cannot use pure UTF-8 because non-IDN-aware applications
> > will still  need to be able to lookup ACE-encoded IDNs.
> 
> Keith,
> 
> While I agree -- for the reasons mentioned by Adam and that I'm
> sure will be repeated and expanded upon by others-- that "just
> send UTF-8" is a bad idea, I'm not sure the above follows.
> 
> We have approaches --the "use a different DNS Class" idea is
> certainly one example-- which would prevent a non-IDN-aware
> application from ever encountering an IDN in a context in which
> being able to resolve it is a reasonable expectation.  

people have suggested such approaches.  I personally do not believe
that they are viable.  in particular, we cannot implement such an
approach without adding explicit negotiation for IDN-compatibility
to every protocol which currently carries a DNS name - including
protocols such as internet mail (rfc2822/mime) and html which are
exchanged via many different bearer protocols.  it's simply not
feasible to add IDN-capability negotiation to each of these.  Nor,
absent conversion to some sort of ascii equivalent,  do there appear 
to be any acceptable modes of operation for the case when the 
negotiation reveals that the destination is not IDN-capable. 

> And
> having an application that is completely non-IDN-aware handle
> ACE-type IDNs correctly (with IDNA or otherwise), is likely, but
> not certain, to bypass unanticipated problems.

I think we've established there there will be some problems no
matter which approach is chosen.  We can still hope to minimize
them.

So in summary, I agree with your categorization of the design 
choices that this group has to make, but for me, both:
(i) just send native IDNs to non-aware applications , and
(iii) preventing non-aware applications from seeing native IDNs
are non-starters, at least for a general approach to retrofitting
existing applications.   (some new applications could perhaps
reasonably employ a type iii solution if they never exchanged
IDNs with other applications)

I disagree with the categorization of type iii as "no risk",
because to me it appears that there is considerable risk 
associated with adding IDN capability negotiation to the 
large number of existing applications that use DNS names.
This risk might not be so much that existing applications
are exposed to IDNs, but instead that updating a large
number of applications to explicitly support IDN negotiation
will introduce new failure modes that are not easily understood 
by users, and require changes to software that will sometimes 
require major restructuring and thereby introduce bugs that
will cause operational errors.

Keith



From owner-idn@ops.ietf.org  Mon May 14 21:50:29 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA29566
	for <idn-archive@lists.ietf.org>; Mon, 14 May 2001 21:50:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14zTfC-000I6Y-00
	for idn-data@psg.com; Mon, 14 May 2001 18:30:14 -0700
From: "Larson, Matt" <mlarson@verisign.com>
To: idn@ops.ietf.org
Subject: RE: [idn] The WALID patent may not apply to IDNA
Date: Mon, 14 May 2001 12:40:40 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E14zTfC-000I6Y-00@psg.com>

Paul Hoffman wrote:
> This working group has to reach consensus. We already did that about
> IDNA; then the WALID patent surfaced. However, unless the working
> group thinks the patent actually applies to IDNA, we should continue
> to work on IDNA.
>
> If anyone who has read the patent would like to say why they think it
> applies to IDNA, please do so. Otherwise, I propose that the working
> group moves forward on IDNA and we ignore the WALID patent.

VeriSign Global Registry Services would like to express its support for
IDNA
and encourage the working group to move forward with it.

Matt
--
Matt Larson <mlarson@verisign.com>
VeriSign Global Registry Services





From owner-idn@ops.ietf.org  Tue May 15 00:40:18 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA02895
	for <idn-archive@lists.ietf.org>; Tue, 15 May 2001 00:40:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14zWQ9-000Lu3-00
	for idn-data@psg.com; Mon, 14 May 2001 21:26:53 -0700
From: Michael Mealling <michael@bailey.dscga.com>
To: Adonis El Fakih <adonis@ayna.com>
Cc: idn working group <idn@ops.ietf.org>
Subject: Re: [idn] iDNS transition: end-system vs. infrastructure?
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E14zWQ9-000Lu3-00@psg.com>
Date: Mon, 14 May 2001 21:26:53 -0700

On Sat, May 12, 2001 at 06:06:50PM -0400, Adonis El Fakih wrote:
> It would be easier if we can make a list of protocols/applications
> that will be affected by internationalized domain names (idn).  I feel
> this would be the first step to make sure we did not skip any
> protocol/application in the process of evaluating  what is the best
> solution.

Don't forget about the literally hundreds of
proprietary/one-off/in-house
protocols that have been developed over the years that make these exact
same
assumptions. IMHO, you're talking an upgrade for nearly every public and
private protocol on the Internet. IMHO, if you're going to go to that
much of an effort lets instead deploy something new that will fix more
than
20% of the perceived problem space....

-MM

--
------------------------------------------------------------------------
--------
Michael Mealling |      Vote Libertarian!       | www.rwhois.net/michael
Sr. Research Engineer   |   www.ga.lp.org/gwinnett     | ICQ#:
14198821
Network Solutions |          www.lp.org          |  michaelm@netsol.com





From owner-idn@ops.ietf.org  Tue May 15 02:10:05 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA17666
	for <idn-archive@lists.ietf.org>; Tue, 15 May 2001 02:10:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14zXXH-000Nop-00
	for idn-data@psg.com; Mon, 14 May 2001 22:38:19 -0700
Received: from gro.dd.org ([209.198.103.200])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14zXXF-000Nof-00
	for idn@ops.ietf.org; Mon, 14 May 2001 22:38:18 -0700
Received: (from tale@localhost)
	by gro.dd.org (8.9.0/8.8.5) id BAA15609;
	Tue, 15 May 2001 01:38:12 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15104.49347.772393.96046@gro.dd.org>
Date: Tue, 15 May 2001 01:38:11 -0400 (EDT)
From: tale@nominum.com (David C Lawrence)
To: <idn@ops.ietf.org>
Subject: RE: [idn] iDNS transition: end-system vs. infrastructure?
In-Reply-To: <DE1B1F489EDD6D4C9A0118DC3F6C3E730329FD43@DINO.platinum.corp.microsoft.com>
References: <DE1B1F489EDD6D4C9A0118DC3F6C3E730329FD43@DINO.platinum.corp.microsoft.com>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Russ Rolfe writes:
> could someone kindly post a simple list of the reasons they feel
> "Just do pure UTF-8" is *not* a valid alternative.

Besides the other reasons already mentioned, there is the issues that
the security risk is greatly increased that someone can spoof domain
names.  Just craft a string in some character set or encoding other
than UTF-8 that can be interpreted as valid UTF-8, then trick people
with non-aware clients into sending the binary name as a DNS request.

Take for example a bad guy who sends a KOI-8 email to victim that has
a link within it to {TSE}{IO}.ru, perhaps the web site of a well-known
company.  Victim's legacy browser requests {TSE}{IO}.ru, but it is
interpreted as UTF-8, so he gets back the address for
{LATIN SMALL LETTER O WITH ACUTE}.ru -- the bad guy's sham site.

This admittedly takes some special circumstances (I am not suggesting
that every IDN would be spoofable this way) but with all of the
permutations of non-UTF-8 and millions of IDNs, there will surely be
plenty of opportunity for either accidental or intentional
misdirection to happen.

This does not rule out UTF-8, it only rules out the "Just Send" part.
There must be some way for a program to indicate that it is aware of
the rules surrounding the use of binary goop as a DNS name.





From owner-idn@ops.ietf.org  Tue May 15 03:28:35 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA18351
	for <idn-archive@lists.ietf.org>; Tue, 15 May 2001 03:28:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14zYz0-000Puz-00
	for idn-data@psg.com; Tue, 15 May 2001 00:11:02 -0700
Received: from smtp.mailbox.co.uk ([195.82.125.32] helo=smtp.mailbox.net.uk)
	by psg.com with esmtp (Exim 3.16 #1)
	id 14zYyz-000Put-00
	for idn@ops.ietf.org; Tue, 15 May 2001 00:11:01 -0700
Received: from [195.82.120.191] (helo=steve.mailbox.net.uk)
	by smtp.mailbox.net.uk with esmtp (Exim 3.22 #2)
	id 14zYqO-0001aZ-00; Tue, 15 May 2001 08:02:08 +0100
Message-Id: <4.3.1.2.20010515075553.022b07a8@pop3.mailbox.co.uk>
X-Sender: steve@pop3.mailbox.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Tue, 15 May 2001 08:10:40 +0100
To: "Larson, Matt" <mlarson@verisign.com>
From: Stephen Dyer <steve@uk.com>
Subject: RE: [idn] The WALID patent may not apply to IDNA
Cc: idn@ops.ietf.org
In-Reply-To: <E14zTfC-000I6Y-00@psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hi All,

>Matt Larson Wrote:
>VeriSign Global Registry Services would like to express its support for
>IDNA
>and encourage the working group to move forward with it.

 > Matt Larson <mlarson@verisign.com>
 > VeriSign Global Registry Services

I am not a supporter of the NSI Testbed because it is a premature 
implementation of a proposed standard and encourages similar non-standard 
deployments.

However, VeriSign does have the financial clout to test the Walid patent in 
the Courts. Now it has committed to this standard - (because that's what 
the "testbed" is) it has a real commercial need for the full deployment of 
this standard. So how about spending the money Matt? - this would be real 
support - roll out your attorneys.

Regards

Steve Dyer
Chairman CentralNic




From owner-idn@ops.ietf.org  Tue May 15 08:32:53 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA23507
	for <idn-archive@lists.ietf.org>; Tue, 15 May 2001 08:32:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 14zdht-0005t5-00
	for idn-data@psg.com; Tue, 15 May 2001 05:13:41 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 14zdhs-0005sL-00
	for idn@ops.ietf.org; Tue, 15 May 2001 05:13:40 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id IAA01003;
        Tue, 15 May 2001 08:13:28 -0400 (EDT)
Message-Id: <200105151213.IAA01003@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Stephen Dyer <steve@uk.com>
cc: "Larson, Matt" <mlarson@verisign.com>, idn@ops.ietf.org
Subject: Re: [idn] The WALID patent may not apply to IDNA 
In-reply-to: Your message of "Tue, 15 May 2001 08:10:40 BST."
             <4.3.1.2.20010515075553.022b07a8@pop3.mailbox.co.uk> 
Date: Tue, 15 May 2001 08:13:28 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> However, VeriSign does have the financial clout to test the Walid patent in
> the Courts. 

it would almost certainly be cheaper for them to get a license for the patent,
and this would actually harm the ability of others to use the standard.

so I take VeriSign's show of support to mean absolutely nothing regarding
their beliefs about the validity of the patent.

Keith



From owner-idn@ops.ietf.org  Fri May 18 07:20:15 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA22562
	for <idn-archive@lists.ietf.org>; Fri, 18 May 2001 07:20:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 150huw-000Btp-00
	for idn-data@psg.com; Fri, 18 May 2001 03:55:34 -0700
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.16 #1)
	id 150huu-000Bti-00
	for idn@ops.ietf.org; Fri, 18 May 2001 03:55:33 -0700
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21884;
	Fri, 18 May 2001 06:55:20 -0400 (EDT)
Message-Id: <200105181055.GAA21884@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-iptr-02.txt
Date: Fri, 18 May 2001 06:55:20 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: Internationalized PTR Resource Record (IPTR)
	Author(s)	: H. Shi, J. Liang
	Filename	: draft-ietf-idn-iptr-02.txt
	Pages		: 9
	Date		: 17-May-01
	
This draft attempts to address the problem of how an IP address should
be properly mapped to a set of internationalized domain names(iDNs).
It is currently unspecified how a PTR record can be used for this
purpose.  In addition, the syntax of the PTR resource record may be
too restrictive for such a mapping in a more culturally meaningful
context.  This document suggests a new TYPE called IPTR using EDNS0
and a mechanism to combind language information with such a mapping.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idn-iptr-02.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-iptr-02.txt".

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


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

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

--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:	<20010517101121.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idn-iptr-02.txt

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

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

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Sun May 20 10:21:58 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA10611
	for <idn-archive@lists.ietf.org>; Sun, 20 May 2001 10:21:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 151TZS-000Boh-00
	for idn-data@psg.com; Sun, 20 May 2001 06:48:34 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.16 #1)
	id 151TZR-000Bob-00
	for idn@ops.ietf.org; Sun, 20 May 2001 06:48:34 -0700
Received: from CLASSIC.viagenie.qc.ca (modemcable245.48-201-24.que.mc.videotron.ca [24.201.48.245])
	by jazz.viagenie.qc.ca (Viagenie/8.11.0) with ESMTP id f4KE2c109756;
	Sun, 20 May 2001 10:02:38 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010519150455.02e8fbd0@mail.viagenie.qc.ca>
X-Sender: blanchet@mail.viagenie.qc.ca
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 20 May 2001 09:51:31 -0400
To: idn@ops.ietf.org
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: [idn] time to move
Cc: jseng@pobox.org.sg
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hi,
	In december, the wg came to a rough concensus on the idna-nameprep-ace 
proposals to be forwarded as the recommendation of the wg to the IESG. In 
the recent months, a patent claim was discussed.  Some members of the wg 
told the wg that they do not think that the proposals are covered by a 
patent claim.  Other members of the wg are uncertain about patent's 
relevance to the wg.  No formal legal opinions have been offered to the group.
	The current working group documents are:
http://www.ietf.org/internet-drafts/draft-ietf-idn-idna-01.txt
http://www.ietf.org/internet-drafts/draft-ietf-idn-nameprep-03.txt

These documents may have further revisions. Final revision would be sent 
for wg last call. The ACE design team is waiting for the confirmation of 
the wg orientation to propose to the wg the ACE choice.
	The chairs would like to make an electronic straw poll to reverify the 
concensus obtained in december. You have to understand that this will help 
the chairs to identify concensus.  If we think we have reached concensus, 
then the authors of the documents as well as the ACE design team will be 
requested to finish their work so that all documents would be forwarded to 
IESG.

	The results of the straw poll will be public.

	Please follow the instructions below. Send a email to 
idn-concensus@viagenie.qc.ca
   with in the subject: AgreeOnIdna-nameprep-ace   if you agree with 
retaining the IDNA technical approach
  or with in the subject: DisagreeOnIdna-nameprep-ace   if you disagree 
with pursuing IDNA and, instead, feel that an alternative approach should 
be pursued.

If you agree, you need not put anything in the body!
If you disagree, then the body of the email should contain a reference to a 
internet draft suggested as your alternative.

For your convenience:
Agree: mailto:idn-concensus@viagenie.qc.ca?Subject:AgreeOnIdna-nameprep-ace
Disagree: 
mailto:idn-concensus@viagenie.qc.ca?Subject:DisagreeOnIdna-nameprep-ace

The straw poll will conclude on wednesday May 23rd 2001, 23h59 
GMT.  Counting will be done by a few members of the working group (Dave 
Crocker, Rick Wesson, James Seng, Marc Blanchet) and results will be posted 
as soon as possible.

Thanks for participating

Marc & James.




From owner-idn@ops.ietf.org  Sun May 20 12:51:39 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA11603
	for <idn-archive@lists.ietf.org>; Sun, 20 May 2001 12:51:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 151W7X-000LJJ-00
	for idn-data@psg.com; Sun, 20 May 2001 09:31:55 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 151W7W-000LJD-00
	for idn@ops.ietf.org; Sun, 20 May 2001 09:31:54 -0700
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id JAA03065
	for <idn@ops.ietf.org>; Sun, 20 May 2001 09:31:53 -0700
Message-Id: <5.1.0.14.2.20010520092230.027ff490@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 20 May 2001 09:25:20 -0700
To: idn@ops.ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] The WALID patent may not apply to IDNA 
In-Reply-To: <200105151213.IAA01003@astro.cs.utk.edu>
References: <Your message of "Tue, 15 May 2001 08:10:40 BST." <4.3.1.2.20010515075553.022b07a8@pop3.mailbox.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 05:13 AM 5/15/2001, Keith Moore wrote:
> > However, VeriSign does have the financial clout to test the Walid patent in
> > the Courts.
>
>it would almost certainly be cheaper for them to get a license for the patent,
>and this would actually harm the ability of others to use the standard.
>
>so I take VeriSign's show of support to mean absolutely nothing regarding
>their beliefs about the validity of the patent.


Unfortunately, I agree. Reactions to potential patent infringement are very 
different for well-funded market leaders than for the rest of an industry.

The major benefit of the note from NSI is to set an example for others to 
make similar announcements... if their own independent intellectual 
property lawyers believe the patent does not apply.

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




From owner-idn@ops.ietf.org  Sun May 20 13:55:31 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA11837
	for <idn-archive@lists.ietf.org>; Sun, 20 May 2001 13:55:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 151XFO-000PcZ-00
	for idn-data@psg.com; Sun, 20 May 2001 10:44:06 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 151XFN-000PcS-00
	for idn@ops.ietf.org; Sun, 20 May 2001 10:44:05 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4KHh3f29565;
	Sun, 20 May 2001 13:43:03 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105201743.f4KHh3f29565@nic-naa.net>
To: Dave Crocker <dhc@dcrocker.net>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] The WALID patent may not apply to IDNA 
In-Reply-To: Your message of "Sun, 20 May 2001 09:25:20 PDT."
             <5.1.0.14.2.20010520092230.027ff490@dcrocker.net> 
Date: Sun, 20 May 2001 13:43:03 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> The major benefit of the note from NSI is to set an example for others to 
> make similar announcements... if their own independent intellectual 
> property lawyers believe the patent does not apply.

We (.biz) have not yet completed this (independent patent review) activity. 

Eric



From owner-idn@ops.ietf.org  Sun May 20 15:19:35 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA12359
	for <idn-archive@lists.ietf.org>; Sun, 20 May 2001 15:19:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 151YOJ-0004Mr-00
	for idn-data@psg.com; Sun, 20 May 2001 11:57:23 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 151YOE-0004Ml-00
	for idn@ops.ietf.org; Sun, 20 May 2001 11:57:19 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4KIuEf29761;
	Sun, 20 May 2001 14:56:14 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105201856.f4KIuEf29761@nic-naa.net>
To: zita@isi.edu, jseng@pobox.org.sg
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: [idn] Reminder:  Clarification, draft-ietf-idn-requirements-0?.txt, [30]
Date: Sun, 20 May 2001 14:56:14 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Authors,

This is a resend of a query sent to you on April 30th, about three weeks past.

Eric
------- Forwarded Message

Message-Id: <200104301212.f3UCCkc16114@nic-naa.net>
To: zita@isi.edu, jseng@pobox.org.sg
cc: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>,
   idn@ops.ietf.org, brunner@nic-naa.net
Subject: [idn] Clarification, draft-ietf-idn-requirements-0?.txt, [30]
Date: Mon, 30 Apr 2001 08:12:46 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Authors,

Would you do me the kindness of reminding me who proposed the current text
of General Requirements, item [30]? I'd like to know what use case(s) were
offered to motivate this manditory-to-implement (zone manager definition of
equivalency rules) requirement.

Tia,
Eric


------- End of Forwarded Message




From owner-idn@ops.ietf.org  Mon May 21 10:48:32 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA10670
	for <idn-archive@lists.ietf.org>; Mon, 21 May 2001 10:48:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 151qRw-00060U-00
	for idn-data@psg.com; Mon, 21 May 2001 07:14:20 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.16 #1)
	id 151qRv-00060O-00
	for idn@ops.ietf.org; Mon, 21 May 2001 07:14:19 -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 f4LEDwo04080; Mon, 21 May 2001 16:13:59 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Mon, 21 May 2001 16:13:05 +0200 (MEST) (MET)
Message-Id: <200105211413.QAA26111@valinor.malmo.trab.se>
Date: Mon, 21 May 2001 16:13:05 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: [idn] time to move
To: idn@ops.ietf.org, Marc.Blanchet@viagenie.qc.ca
Cc: jseng@pobox.org.sg
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Am4VNxQ8EG66NTQJ720j+A==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk

:
>http://www.ietf.org/internet-drafts/draft-ietf-idn-idna-01.txt
>http://www.ietf.org/internet-drafts/draft-ietf-idn-nameprep-03.txt
>
>These documents may have further revisions. Final revision would be sent 
>for wg last call. The ACE design team is waiting for the confirmation of 
>the wg orientation to propose to the wg the ACE choice.
>	The chairs would like to make an electronic straw poll to reverify the 
>concensus obtained in december. 


I have for some time thought that we should start deciding on what to
do, but I do not think we are ready to say idna/nameprep.
We have decisions to do before that:


1) Are we going to use UTF-8 only? (and accept that this will force
   many applications to get fixed, that otherwise could wait a long time
   with fixing).
   
   
   
2) If the answer to 1) is No, the an ACE will be nedded.

   The we get: Is the goal to have UTF-8 as nativ format in DNS in
   the future, or are we going to use ACE forever?
     - If we are going for UTF-8 then ACE is a transition mechanism.
       The ACE should then be simple and fast to implement.
     - If we are going for ACE forever, the ACE selected need to
       be compact so that as many characters can be included in
       as few bytes as possible.
       
       
3) If the goal is UTF-8.
   - ACE support should be declared to end at a curtain date, say 2010.
   - The best solution then is to use something like UDNS, which
     supports both the future UTF-8 and the ACE/IDNA backward
     compatibility mechanism.
     
     
     
   Dan




From owner-idn@ops.ietf.org  Mon May 21 11:17:44 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA11043
	for <idn-archive@lists.ietf.org>; Mon, 21 May 2001 11:17:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 151r97-0008az-00
	for idn-data@psg.com; Mon, 21 May 2001 07:58:57 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.16 #1)
	id 151r96-0008at-00
	for idn@ops.ietf.org; Mon, 21 May 2001 07:58:56 -0700
Received: from CLASSIC.viagenie.qc.ca (modemcable245.48-201-24.que.mc.videotron.ca [24.201.48.245])
	by jazz.viagenie.qc.ca (Viagenie/8.11.0) with ESMTP id f4LFCP118678;
	Mon, 21 May 2001 11:12:25 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010521105700.0314ed80@mail.viagenie.qc.ca>
X-Sender: blanchet@mail.viagenie.qc.ca
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 21 May 2001 11:01:05 -0400
To: Dan Oscarsson <Dan.Oscarsson@trab.se>, idn@ops.ietf.org
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: Re: [idn] time to move
Cc: jseng@pobox.org.sg
In-Reply-To: <200105211413.QAA26111@valinor.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/À 16:13 2001-05-21 +0200, Dan Oscarsson you wrote/vous écriviez:
>:
> >http://www.ietf.org/internet-drafts/draft-ietf-idn-idna-01.txt
> >http://www.ietf.org/internet-drafts/draft-ietf-idn-nameprep-03.txt
> >
> >These documents may have further revisions. Final revision would be sent
> >for wg last call. The ACE design team is waiting for the confirmation of
> >the wg orientation to propose to the wg the ACE choice.
> >       The chairs would like to make an electronic straw poll to 
> reverify the
> >concensus obtained in december.
>
>
>I have for some time thought that we should start deciding on what to
>do, but I do not think we are ready to say idna/nameprep.
>We have decisions to do before that:
>
>
>1) Are we going to use UTF-8 only? (and accept that this will force
>    many applications to get fixed, that otherwise could wait a long time
>    with fixing).

this was not the design team recommendation and perceived wg concensus. 
This electronic straw poll is to find if the wg still think the 
idna-nameprep-ace is the way to go. If we find no concensus on 
idna-nameprep-ace proposal, then we go back to the drawing board.

Marc.

>
>
>
>2) If the answer to 1) is No, the an ACE will be nedded.
>
>    The we get: Is the goal to have UTF-8 as nativ format in DNS in
>    the future, or are we going to use ACE forever?
>      - If we are going for UTF-8 then ACE is a transition mechanism.
>        The ACE should then be simple and fast to implement.
>      - If we are going for ACE forever, the ACE selected need to
>        be compact so that as many characters can be included in
>        as few bytes as possible.

the ACE design team is working on that. If there is a concensus of the wg 
for idna-nameprep-ace, then the ACE design team will hopefully come to the 
wg with a recommendation.

>
>
>3) If the goal is UTF-8.
>    - ACE support should be declared to end at a curtain date, say 2010.
>    - The best solution then is to use something like UDNS, which
>      supports both the future UTF-8 and the ACE/IDNA backward
>      compatibility mechanism.
>
>
>
>    Dan





From owner-idn@ops.ietf.org  Mon May 21 20:31:08 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA21194
	for <idn-archive@lists.ietf.org>; Mon, 21 May 2001 20:31:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 151zhj-0009wP-00
	for idn-data@psg.com; Mon, 21 May 2001 17:07:15 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 151zhi-0009wB-00
	for idn@ops.ietf.org; Mon, 21 May 2001 17:07:14 -0700
Received: (qmail 8643 invoked by uid 1001); 21 May 2001 23:50:57 -0000
Date: 21 May 2001 23:50:57 -0000
Message-ID: <20010521235057.26248.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] time to move
References: <5.1.0.14.1.20010519150455.02e8fbd0@mail.viagenie.qc.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Could we please have a single clear statement of what exactly this poll
is measuring?

Many of us think that moving at this point would be premature. We think
that IDNA was rammed through the WG without adequate discussion. We find
it worrisome that the centerpiece of the IDNA ``design philosophy'' is a
statement about DNS servers that has turned out to be completely wrong.
We want to see a careful cost-benefit analysis, with all facts verified,
before we go screwing around with several critical Internet protocols.
And, of course, we want to know the effects of this patent.

How exactly are we supposed to respond to this poll?

---Dan



From owner-idn@ops.ietf.org  Tue May 22 10:58:28 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA21224
	for <idn-archive@lists.ietf.org>; Tue, 22 May 2001 10:58:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152D6p-000F2m-00
	for idn-data@psg.com; Tue, 22 May 2001 07:26:03 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.16 #1)
	id 152D6p-000F2f-00
	for idn@ops.ietf.org; Tue, 22 May 2001 07:26:03 -0700
Message-ID: <002101c0e2cb$8c3cb0c0$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: <idn@ops.ietf.org>, "Dave Crocker" <dhc@dcrocker.net>
References: <Your message of "Tue, 15 May 2001 08:10:40 BST." <4.3.1.2.20010515075553.022b07a8@pop3.mailbox.co.uk> <5.1.0.14.2.20010520092230.027ff490@dcrocker.net>
Subject: Re: [idn] The WALID patent may not apply to IDNA 
Date: Tue, 22 May 2001 10:28:57 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

From my point of view, I dont see any value of VeriSign coming out to talk
about the patent.  As far as I understand, VeriSign itself is not infringing
on the patent, it is the companies who create the clients that will have a
problem.

Edmon


----- Original Message -----
From: "Dave Crocker" <dhc@dcrocker.net>
To: <idn@ops.ietf.org>
Sent: Sunday, May 20, 2001 12:25 PM
Subject: Re: [idn] The WALID patent may not apply to IDNA


> At 05:13 AM 5/15/2001, Keith Moore wrote:
> > > However, VeriSign does have the financial clout to test the Walid
patent in
> > > the Courts.
> >
> >it would almost certainly be cheaper for them to get a license for the
patent,
> >and this would actually harm the ability of others to use the standard.
> >
> >so I take VeriSign's show of support to mean absolutely nothing regarding
> >their beliefs about the validity of the patent.
>
>
> Unfortunately, I agree. Reactions to potential patent infringement are
very
> different for well-funded market leaders than for the rest of an industry.
>
> The major benefit of the note from NSI is to set an example for others to
> make similar announcements... if their own independent intellectual
> property lawyers believe the patent does not apply.
>
> 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 May 22 10:58:30 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA21227
	for <idn-archive@lists.ietf.org>; Tue, 22 May 2001 10:58:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152DDT-000FA5-00
	for idn-data@psg.com; Tue, 22 May 2001 07:32:55 -0700
Received: from [66.48.4.181] (helo=neteka.com)
	by psg.com with smtp (Exim 3.16 #1)
	id 152DDS-000F9w-00
	for idn@ops.ietf.org; Tue, 22 May 2001 07:32:54 -0700
Message-ID: <004601c0e2cc$81b4f620$1001a8c0@neteka.com>
From: "Edmon" <edmon@neteka.com>
To: <idn@ops.ietf.org>, "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>
Cc: <jseng@pobox.org.sg>
References: <5.1.0.14.1.20010519150455.02e8fbd0@mail.viagenie.qc.ca>
Subject: Re: [idn] time to move
Date: Tue, 22 May 2001 10:35:51 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I think we are still discussing possible alternatives and from your
instructions we have to point to a current I-D if we disagree.
I am thinking that there would be one or more new I-Ds coming out from the
discussion of possible alternatives discussed here in the mailing list
therefore I think it is premature to do this just yet.  Or it should be
possible to vote for "disagree" without pointing to a particular I-D.
Edmon



----- Original Message -----
From: "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>
To: <idn@ops.ietf.org>
Cc: <jseng@pobox.org.sg>
Sent: Sunday, May 20, 2001 9:51 AM
Subject: [idn] time to move


> Hi,
> In december, the wg came to a rough concensus on the idna-nameprep-ace
> proposals to be forwarded as the recommendation of the wg to the IESG. In
> the recent months, a patent claim was discussed.  Some members of the wg
> told the wg that they do not think that the proposals are covered by a
> patent claim.  Other members of the wg are uncertain about patent's
> relevance to the wg.  No formal legal opinions have been offered to the
group.
> The current working group documents are:
> http://www.ietf.org/internet-drafts/draft-ietf-idn-idna-01.txt
> http://www.ietf.org/internet-drafts/draft-ietf-idn-nameprep-03.txt
>
> These documents may have further revisions. Final revision would be sent
> for wg last call. The ACE design team is waiting for the confirmation of
> the wg orientation to propose to the wg the ACE choice.
> The chairs would like to make an electronic straw poll to reverify the
> concensus obtained in december. You have to understand that this will help
> the chairs to identify concensus.  If we think we have reached concensus,
> then the authors of the documents as well as the ACE design team will be
> requested to finish their work so that all documents would be forwarded to
> IESG.
>
> The results of the straw poll will be public.
>
> Please follow the instructions below. Send a email to
> idn-concensus@viagenie.qc.ca
>    with in the subject: AgreeOnIdna-nameprep-ace   if you agree with
> retaining the IDNA technical approach
>   or with in the subject: DisagreeOnIdna-nameprep-ace   if you disagree
> with pursuing IDNA and, instead, feel that an alternative approach should
> be pursued.
>
> If you agree, you need not put anything in the body!
> If you disagree, then the body of the email should contain a reference to
a
> internet draft suggested as your alternative.
>
> For your convenience:
> Agree:
mailto:idn-concensus@viagenie.qc.ca?Subject:AgreeOnIdna-nameprep-ace
> Disagree:
> mailto:idn-concensus@viagenie.qc.ca?Subject:DisagreeOnIdna-nameprep-ace
>
> The straw poll will conclude on wednesday May 23rd 2001, 23h59
> GMT.  Counting will be done by a few members of the working group (Dave
> Crocker, Rick Wesson, James Seng, Marc Blanchet) and results will be
posted
> as soon as possible.
>
> Thanks for participating
>
> Marc & James.
>




From owner-idn@ops.ietf.org  Tue May 22 12:05:52 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA23807
	for <idn-archive@lists.ietf.org>; Tue, 22 May 2001 12:05:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152EJP-000GSi-00
	for idn-data@psg.com; Tue, 22 May 2001 08:43:07 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152EJM-000GSb-00
	for idn@ops.ietf.org; Tue, 22 May 2001 08:43:05 -0700
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id IAA22672
	for <idn@ops.ietf.org>; Tue, 22 May 2001 08:42:52 -0700
Message-Id: <5.1.0.14.2.20010522082111.081af5a8@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 22 May 2001 08:27:24 -0700
To: idn@ops.ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] time to move
In-Reply-To: <20010521235057.26248.qmail@cr.yp.to>
References: <5.1.0.14.1.20010519150455.02e8fbd0@mail.viagenie.qc.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dan,

At 04:50 PM 5/21/2001, D. J. Bernstein wrote:
>Could we please have a single clear statement of what exactly this poll
>is measuring?

The language in the polling question is quite thorough.  If you do not 
understand portions of it, you should consider asking specific questions 
about that language.


>Many of us think that moving at this point would be premature.

Making an assertion like "many of us" is a bit ironic, given that the 
purpose of the poll is to get a sense of proportionate preference.

Your making such an assertion suggests that you have already done such a 
survey, unbeknownst to the rest of the working group.


>We think
>that IDNA was rammed through the WG without adequate discussion.

A process which first establishes rough consensus and then returns to 
re-verify that consensus can hardly be called "rammed through".


>We find
>it worrisome that the centerpiece of the IDNA ``design philosophy'' is a
>statement about DNS servers that has turned out to be completely wrong.

What statement is that?


>We want to see a careful cost-benefit analysis, with all facts verified,

The nice thing about the IETF process is that people who feel strongly 
about a requirement are free to pursue its development.

It's fine to propose such analyses -- though quite unusual -- but once the 
working group does not choose to take on the task, you are always free to 
gather worker bees around the task and buzz through the task.


>How exactly are we supposed to respond to this poll?

Why are you asking such a question after you already sent in your own response?

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 May 22 18:25:10 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA05914
	for <idn-archive@lists.ietf.org>; Tue, 22 May 2001 18:25:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152KLY-000ME6-00
	for idn-data@psg.com; Tue, 22 May 2001 15:09:44 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 152KLW-000ME0-00
	for idn@ops.ietf.org; Tue, 22 May 2001 15:09:42 -0700
Received: (qmail 9751 invoked by uid 1001); 22 May 2001 22:09:53 -0000
Date: 22 May 2001 22:09:53 -0000
Message-ID: <20010522220953.22977.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] time to move
References: <5.1.0.14.1.20010519150455.02e8fbd0@mail.viagenie.qc.ca> <20010521235057.26248.qmail@cr.yp.to> <5.1.0.14.2.20010522082111.081af5a8@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > How exactly are we supposed to respond to this poll?
> Why are you asking such a question after you already sent in your own
> response?

The only choices provided were ``agree with retaining the IDNA technical
approach'' and ``disagree with pursuing IDNA and, instead, feel that an
alternative approach should be pursued.''

The poll didn't provide any way to say ``evaluate the options carefully;
this is a major decision; moving right now is premature.''

I sent a ``disagree'' response because it seems that the poll-takers
will interpret ``agree'' responses as a reason to rush forward without
considering the facts. But the fact that I've sent a response doesn't
mean that I'm happy with the form of the poll.

> Your making such an assertion suggests that you have already done such a 
> survey, unbeknownst to the rest of the working group.

I'm paying attention to the messages on the mailing list. Are you?

> > We find
> > it worrisome that the centerpiece of the IDNA ``design philosophy'' is a
> > statement about DNS servers that has turned out to be completely wrong.
> What statement is that?

``To date, the proposals for IDN protocols have required that DNS
servers be updated to handle internationalized host names.''

---Dan



From owner-idn@ops.ietf.org  Tue May 22 21:49:36 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA09308
	for <idn-archive@lists.ietf.org>; Tue, 22 May 2001 21:49:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152NQK-000NNS-00
	for idn-data@psg.com; Tue, 22 May 2001 18:26:52 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 152NQJ-000NNM-00
	for idn@ops.ietf.org; Tue, 22 May 2001 18:26:51 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP id 9A1B7FFC04
	for <idn@ops.ietf.org>; Wed, 23 May 2001 09:29:26 +0800 (SGT)
Message-ID: <01b701c0e327$56c40310$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: <idn@ops.ietf.org>
Subject: [idn] requirements-07
Date: Wed, 23 May 2001 09:26:06 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Requirements-07 has just been send to internet-drafts@ietf.org. 

Changes from -06:

1. Correcting typos at line 59 and 663.

2. Remove requirement [30] and renumber [31] to [30].

-James Seng




From owner-idn@ops.ietf.org  Wed May 23 00:16:31 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA12296
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 00:16:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152Pis-000PuX-00
	for idn-data@psg.com; Tue, 22 May 2001 20:54: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.16 #1)
	id 152Pis-000PuR-00
	for idn@ops.ietf.org; Tue, 22 May 2001 20:54:10 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4N3rSf68194;
	Tue, 22 May 2001 23:53:28 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105230353.f4N3rSf68194@nic-naa.net>
To: "James Seng/Personal" <James@Seng.cc>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] requirements-07 
In-Reply-To: Your message of "Wed, 23 May 2001 09:26:06 +0800."
             <01b701c0e327$56c40310$dd00a8c0@jamessonyvaio> 
Date: Tue, 22 May 2001 23:53:28 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> 2. Remove requirement [30] and renumber [31] to [30].    

Without ever identifying who thought that zone-specific semantics MUST
be useful? Without ever identifying what use cases were offered for or
against such an apparently authorless assertion? Without a requirement
that zone-specific semantics MUST NOT be useful?

How ... creative.

Co-author and co-chair Seng asked me for alternate text. I responded
that without knowing why [30] ever came into being in the first place,
alternate text could not be the best course of action. Now, as if this
is "better" than the last botch (substituting "MAY" for "MUST"), all
requirement relative to semantic scope (and consistency or its lack)
has been removed.

There is something above peculiar in the process this WG is thrashing
under.

I'd like the authors of the document to respond to substantive queries,
not fumble serial text botches. I want to know why [30] was ever in, as
why it could be out is a much simpler question, though not necessarily
with only one answer.

Eric



From owner-idn@ops.ietf.org  Wed May 23 00:19:29 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA12320
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 00:19:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152Pnk-00002w-00
	for idn-data@psg.com; Tue, 22 May 2001 20:59:12 -0700
Received: from ibd.ar.com ([63.194.205.75])
	by psg.com with esmtp (Exim 3.16 #1)
	id 152Pnj-00002q-00
	for idn@ops.ietf.org; Tue, 22 May 2001 20:59:12 -0700
Received: from loki (wessorh@loki.ar.com [10.10.10.88])
	by ibd.ar.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id UAA01075
	for <idn@ops.ietf.org>; Tue, 22 May 2001 20:57:37 -0700 (PDT)
Date: Tue, 22 May 2001 20:59:14 -0700 (PDT)
From: Rick H Wesson <wessorh@ar.com>
To: <idn@ops.ietf.org>
Subject: [idn] Verisign mores the IDN testbed forward.
Message-ID: <Pine.LNX.4.30.0105222055340.5745-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


all:

In case you all didn't know it, Verisign intends to put RACE based
multilingual names in to the com/net/org zones starting on May 29th, 2001.

aparently VeriSign polled their current IDN enabled registrars and
decided it was a good idea to move forward.


-rick





From owner-idn@ops.ietf.org  Wed May 23 01:12:42 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA13536
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 01:12:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152QlS-0001EU-00
	for idn-data@psg.com; Tue, 22 May 2001 22:00:54 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 152QlR-0001EM-00
	for idn@ops.ietf.org; Tue, 22 May 2001 22:00:53 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id E6538FFC01; Wed, 23 May 2001 13:03:29 +0800 (SGT)
Message-ID: <032101c0e345$3db785e0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>, <brunner@nic-naa.net>
References: <200105230353.f4N3rSf68194@nic-naa.net>
Subject: Re: [idn] requirements-07 
Date: Wed, 23 May 2001 13:00: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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Once again, we (Zita & myself) are not "authors" but rather "editors" of
this document. We did not come up with these requirements but rather
taking comments from the Working Group across our discussion since Nov
99 and piece them together.

If you want to track the source, you should not be looking for us. Look
for the one who made this comments OR you can find it by going thru the
archives http://www.i-d-n.net/ yourself.

ps: The reason for the slowness to response to your editorial is because
I have an filter which put emails from brunner@nic-naa.net in the same
folder as Jeff Williams. You can consider it as /dev/null for all intent
and purposes.

-James Seng

----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: "James Seng/Personal" <James@seng.cc>
Cc: <idn@ops.ietf.org>; <brunner@nic-naa.net>
Sent: Wednesday, May 23, 2001 11:53 AM
Subject: Re: [idn] requirements-07


> > 2. Remove requirement [30] and renumber [31] to [30].
>
> Without ever identifying who thought that zone-specific semantics MUST
> be useful? Without ever identifying what use cases were offered for or
> against such an apparently authorless assertion? Without a requirement
> that zone-specific semantics MUST NOT be useful?
>
> How ... creative.
>
> Co-author and co-chair Seng asked me for alternate text. I responded
> that without knowing why [30] ever came into being in the first place,
> alternate text could not be the best course of action. Now, as if this
> is "better" than the last botch (substituting "MAY" for "MUST"), all
> requirement relative to semantic scope (and consistency or its lack)
> has been removed.
>
> There is something above peculiar in the process this WG is thrashing
> under.
>
> I'd like the authors of the document to respond to substantive
queries,
> not fumble serial text botches. I want to know why [30] was ever in,
as
> why it could be out is a much simpler question, though not necessarily
> with only one answer.
>
> Eric
>




From owner-idn@ops.ietf.org  Wed May 23 01:54:50 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA16091
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 01:54:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152RL0-0001xQ-00
	for idn-data@psg.com; Tue, 22 May 2001 22:37:38 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152RKz-0001xJ-00
	for idn@ops.ietf.org; Tue, 22 May 2001 22:37:37 -0700
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id WAA23481;
	Tue, 22 May 2001 22:37:06 -0700
Message-Id: <5.1.0.14.2.20010522201355.03bdaa20@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 22 May 2001 22:37:39 -0700
To: "D. J. Bernstein" <djb@cr.yp.to>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] time to move
Cc: idn@ops.ietf.org
In-Reply-To: <20010522220953.22977.qmail@cr.yp.to>
References: <5.1.0.14.1.20010519150455.02e8fbd0@mail.viagenie.qc.ca>
 <20010521235057.26248.qmail@cr.yp.to>
 <5.1.0.14.2.20010522082111.081af5a8@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 03:09 PM 5/22/2001, D. J. Bernstein wrote:
> > > How exactly are we supposed to respond to this poll?
> > Why are you asking such a question after you already sent in your own
> > response?
>
>The only choices provided were ``agree with retaining the IDNA technical
>approach'' and ``disagree with pursuing IDNA and, instead, feel that an
>alternative approach should be pursued.''
>
>The poll didn't provide any way to say ``evaluate the options carefully;
>this is a major decision; moving right now is premature.''

You prompt a number of interesting points.

One is that it is remarkable how anyone can fail to see the urgency in this 
situation.  It takes really quite an unusual effort to miss the import of 
the current situation and the scope of pressure being applied to resolve it 
quickly.

The second is how productive it would be to have every participant demand 
exactly the precise wording for the questionnaire that they want.  It does 
wonders to survey research validity.  (The ability to cope with inadequate 
choice is a rather interesting personality characteristic that psych types 
like to measure.  It pertains to maturity.)


> > Your making such an assertion suggests that you have already done such a
> > survey, unbeknownst to the rest of the working group.
>
>I'm paying attention to the messages on the mailing list. Are you?

Of course not, Dan.  Why bother, when all I need to do is read your 
messages to find out the One True Truth.

For example, think how remarkable it is that you are so clear on the sense 
of the mailing list.  Why bother to take a straw poll?

And what will it mean if the rough consensus from the poll differs from 
your own, flawless assessment of the group?


> > > We find
> > > it worrisome that the centerpiece of the IDNA ``design philosophy'' is a
> > > statement about DNS servers that has turned out to be completely wrong.
> > What statement is that?
>
>``To date, the proposals for IDN protocols have required that DNS
>servers be updated to handle internationalized host names.''

Well, let's see:

1.  It is certainly true that typical approaches to the problem have 
required changes to the servers

2.  It does not matter whether that assessment is correct.  The center 
piece to the design philosophy is that it requires no change to server 
protocol engines or data base modules; it does not matter whether other 
proposals have that characteristic or not.

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 May 23 03:39:47 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA28663
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 03:39:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152SqW-0003xK-00
	for idn-data@psg.com; Wed, 23 May 2001 00:14:16 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 152SqU-0003ww-00
	for idn@ops.ietf.org; Wed, 23 May 2001 00:14:15 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 44C59FFC01; Wed, 23 May 2001 15:16:48 +0800 (SGT)
Message-ID: <03a001c0e357$dcfe09f0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>, <brunner@nic-naa.net>
References: <200105230353.f4N3rSf68194@nic-naa.net>
Subject: Re: [idn] requirements-07 
Date: Wed, 23 May 2001 15:13:27 +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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Just another note:

[30] is drop at the request of John Klensin sent on 13th May:

"" From my point of view, the "appropriate wording change" is to
lose [30] --and any other notion of different things happening
in different zones-- entirely.  ...""

There is no further comments or objections to this after 10days.

-James Seng

----- Original Message -----
From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
To: "James Seng/Personal" <James@seng.cc>
Cc: <idn@ops.ietf.org>; <brunner@nic-naa.net>
Sent: Wednesday, May 23, 2001 11:53 AM
Subject: Re: [idn] requirements-07


> > 2. Remove requirement [30] and renumber [31] to [30].
>
> Without ever identifying who thought that zone-specific semantics MUST
> be useful? Without ever identifying what use cases were offered for or
> against such an apparently authorless assertion? Without a requirement
> that zone-specific semantics MUST NOT be useful?
>
> How ... creative.
>
> Co-author and co-chair Seng asked me for alternate text. I responded
> that without knowing why [30] ever came into being in the first place,
> alternate text could not be the best course of action. Now, as if this
> is "better" than the last botch (substituting "MAY" for "MUST"), all
> requirement relative to semantic scope (and consistency or its lack)
> has been removed.
>
> There is something above peculiar in the process this WG is thrashing
> under.
>
> I'd like the authors of the document to respond to substantive
queries,
> not fumble serial text botches. I want to know why [30] was ever in,
as
> why it could be out is a much simpler question, though not necessarily
> with only one answer.
>
> Eric
>




From owner-idn@ops.ietf.org  Wed May 23 06:05:44 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA29714
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 06:05:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152VI5-0006nZ-00
	for idn-data@psg.com; Wed, 23 May 2001 02:50:53 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.16 #1)
	id 152VI4-0006nS-00
	for idn@ops.ietf.org; Wed, 23 May 2001 02:50:52 -0700
Received: from terra (terra.malmo.trab.se [131.115.48.22]) by malmo.trab.se (8.10.1/TRAB-primary-2) with SMTP id f4N9ono28050 for <idn@ops.ietf.org>; Wed, 23 May 2001 11:50:49 +0200 (MEST)
Message-Id: <200105230950.f4N9ono28050@malmo.trab.se>
Date: Wed, 23 May 2001 11:50:47 +0200 (MEST)
From: Dan <Dan.Oscarsson@trab.se>
Reply-To: Dan <Dan.Oscarsson@trab.se>
Subject: Re: [idn] Verisign mores the IDN testbed forward.
To: idn@ops.ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: SnutS9X3ODiJQ/vczjK9Xg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk


>
>In case you all didn't know it, Verisign intends to put RACE based
>multilingual names in to the com/net/org zones starting on May 29th, 2001.
>
>aparently VeriSign polled their current IDN enabled registrars and
>decided it was a good idea to move forward.
>

I am getting the feeling that the open community of IETF is ignored
in the area of internationalisation of DNS. I doubt very much that
RACE is the best ACE. It is quite complex to use.
First we need to decide what is needed of a good ACE. Thing like:
- must be simple
- fast
- compact
- ....
And what is most important.
The all the ACE formats available must be tested.
After that, we can decide what to use.

   Dan




From owner-idn@ops.ietf.org  Wed May 23 06:07:31 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA29727
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 06:07:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152VBk-0006gF-00
	for idn-data@psg.com; Wed, 23 May 2001 02:44:20 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.16 #1)
	id 152VBj-0006g9-00
	for idn@ops.ietf.org; Wed, 23 May 2001 02:44:20 -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 f4N9iAo13947; Wed, 23 May 2001 11:44:10 +0200 (MEST)
Message-Id: <200105230944.f4N9iAo13947@malmo.trab.se>
Date: Wed, 23 May 2001 11:44:07 +0200 (MEST)
From: Dan <Dan.Oscarsson@trab.se>
Reply-To: Dan <Dan.Oscarsson@trab.se>
Subject: Re: [idn] time to move
To: idn@ops.ietf.org, Marc.Blanchet@viagenie.qc.ca
Cc: jseng@pobox.org.sg
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: o6UJ/RVKuAum6VMsVAYIiA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk


>>1) Are we going to use UTF-8 only? (and accept that this will force
>>    many applications to get fixed, that otherwise could wait a long time
>>    with fixing).
>
>this was not the design team recommendation and perceived wg concensus.

That was long time ago. There have been much talking about UTF-8 since then.
But I agree that most do not dare say "just UTF-8" so I expect
a solution with both UTF-8 and ACE is what most think is best.
 
>This electronic straw poll is to find if the wg still think the 
>idna-nameprep-ace is the way to go. If we find no concensus on 
>idna-nameprep-ace proposal, then we go back to the drawing board.

I do not think it answers that, because it does not specify the
alternatives.

I also dislike combining two things into one. Nameprep has some basic
failures in which characters match which that should be agreed on first.
Before it can go on.



>>2) If the answer to 1) is No, the an ACE will be nedded.
>>
>>    The we get: Is the goal to have UTF-8 as nativ format in DNS in
>>    the future, or are we going to use ACE forever?
>>      - If we are going for UTF-8 then ACE is a transition mechanism.
>>        The ACE should then be simple and fast to implement.
>>      - If we are going for ACE forever, the ACE selected need to
>>        be compact so that as many characters can be included in
>>        as few bytes as possible.
>
>the ACE design team is working on that. If there is a concensus of the wg 
>for idna-nameprep-ace, then the ACE design team will hopefully come to the 
>wg with a recommendation.

Why is the ACE design team working on that? It is something that
should be discussed by all before we decide what ACE should be used.
Where is the archive of the ACE design team work?

If we decide that DNS should use UTF-8 and ACE is a transition
mechanism, IDNA is only a temporary and partial solution to what we
need. ACE support should be declared dead about 2010 so only UTF-8
is supported.

I do not want ACE for more than a transition mechanism with a
clear end date. I am tired of "quoted-printable" solutions and all
the problems they result in.
Also why only IDNA? Why not like in UDNS with server support.
Support at my site will be server based, as far as possible. It
is much easier than upgrading all applications.

   Dan





From owner-idn@ops.ietf.org  Wed May 23 06:28:17 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA29865
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 06:28:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152Va2-0007Ah-00
	for idn-data@psg.com; Wed, 23 May 2001 03:09:26 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 152Va0-0007Aa-00
	for idn@ops.ietf.org; Wed, 23 May 2001 03:09:26 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 92CE7FFC01; Wed, 23 May 2001 18:12:01 +0800 (SGT)
Message-ID: <051c01c0e370$5733f8c0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Dan" <Dan.Oscarsson@trab.se>, <idn@ops.ietf.org>,
        <Marc.Blanchet@viagenie.qc.ca>
References: <200105230944.f4N9iAo13947@malmo.trab.se>
Subject: Re: [idn] time to move
Date: Wed, 23 May 2001 18:08:40 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Why is the ACE design team working on that? It is something that
> should be discussed by all before we decide what ACE should be used.
> Where is the archive of the ACE design team work?

I think the right phrasing is that the ACE design team is working on a
ACE recommendation for the WG. The WG still have to decide if it is
willing to go with the recommended solution.

As I recalled during discussion with the design team, the archives would
be make public after the design team finish their work.

-James Seng




From owner-idn@ops.ietf.org  Wed May 23 07:35:40 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA00748
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 07:35:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152WcJ-0008OH-00
	for idn-data@psg.com; Wed, 23 May 2001 04:15:51 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152WcI-0008OB-00
	for idn@ops.ietf.org; Wed, 23 May 2001 04:15:51 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4NBFAf69314;
	Wed, 23 May 2001 07:15:10 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105231115.f4NBFAf69314@nic-naa.net>
To: "James Seng/Personal" <James@Seng.cc>
cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] requirements-07 
In-Reply-To: Your message of "Wed, 23 May 2001 15:13:27 +0800."
             <03a001c0e357$dcfe09f0$dd00a8c0@jamessonyvaio> 
Date: Wed, 23 May 2001 07:15:10 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> ps: The reason for the slowness to response to your editorial is because
> I have an filter which put emails from brunner@nic-naa.net in the same
> folder as Jeff Williams. You can consider it as /dev/null for all intent
> and purposes.

Well, that clears up question I had about the delay in response to my question
on [30]. That doesn't clear up the the substantive question, though I suppose
"search the archives" is a responsible substitute from anyone for a considered
response.

Tia,
Eric



From owner-idn@ops.ietf.org  Wed May 23 07:57:16 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA01413
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 07:57:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152WvM-0008oA-00
	for idn-data@psg.com; Wed, 23 May 2001 04:35:32 -0700
Received: from mail.ndl.net.nu ([208.36.200.249] helo=mail.nic.nu)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152WvL-0008o3-00
	for idn@ops.ietf.org; Wed, 23 May 2001 04:35:32 -0700
Received: from bill ([65.96.148.150]) by mail.nic.nu
          (Post.Office MTA v3.5.3 release 223 ID# 0-61576U100L100S0V35)
          with SMTP id nu; Wed, 23 May 2001 07:36:40 -0400
Message-Id: <3.0.5.32.20010523073246.05065280@mail.nic.nu>
X-Sender: bill@mail.nic.nu
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Wed, 23 May 2001 07:32:46 -0400
To: Dan <Dan.Oscarsson@trab.se>, idn@ops.ietf.org,
        Marc.Blanchet@viagenie.qc.ca
From: bill@mail.nic.nu (J. William Semich)
Subject: Re: [idn] time to move
Cc: jseng@pobox.org.sg
In-Reply-To: <200105230944.f4N9iAo13947@malmo.trab.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I agree with Dan. Let's focus on a clear point of agreement, and ask for
consensus on *just* nameprep. 

So, for the record, I answer "no" to the straw poll, and propose a
more-limited poll on agreeing to move forward with nameprep.

I'd prefer to reconsider other alternatives, whether transition based or
not, such as UDNS, Paul and Marc's IDNE and John's proposal for a new class
(draft-klensin-dnsclass0e) instead of a permanent ACE solution like IDNA at
this point...

Regards,

Bill Semich

At 11:44 AM 5/23/01 +0200, Dan wrote:
>
>>>1) Are we going to use UTF-8 only? (and accept that this will force
>>>    many applications to get fixed, that otherwise could wait a long time
>>>    with fixing).
>>
>>this was not the design team recommendation and perceived wg concensus.
>
>That was long time ago. There have been much talking about UTF-8 since then.
>But I agree that most do not dare say "just UTF-8" so I expect
>a solution with both UTF-8 and ACE is what most think is best.
> 
>>This electronic straw poll is to find if the wg still think the 
>>idna-nameprep-ace is the way to go. If we find no concensus on 
>>idna-nameprep-ace proposal, then we go back to the drawing board.
>
>I do not think it answers that, because it does not specify the
>alternatives.
>
>I also dislike combining two things into one. Nameprep has some basic
>failures in which characters match which that should be agreed on first.
>Before it can go on.
>
>
>
>>>2) If the answer to 1) is No, the an ACE will be nedded.
>>>
>>>    The we get: Is the goal to have UTF-8 as nativ format in DNS in
>>>    the future, or are we going to use ACE forever?
>>>      - If we are going for UTF-8 then ACE is a transition mechanism.
>>>        The ACE should then be simple and fast to implement.
>>>      - If we are going for ACE forever, the ACE selected need to
>>>        be compact so that as many characters can be included in
>>>        as few bytes as possible.
>>
>>the ACE design team is working on that. If there is a concensus of the wg 
>>for idna-nameprep-ace, then the ACE design team will hopefully come to the 
>>wg with a recommendation.
>
>Why is the ACE design team working on that? It is something that
>should be discussed by all before we decide what ACE should be used.
>Where is the archive of the ACE design team work?
>
>If we decide that DNS should use UTF-8 and ACE is a transition
>mechanism, IDNA is only a temporary and partial solution to what we
>need. ACE support should be declared dead about 2010 so only UTF-8
>is supported.
>
>I do not want ACE for more than a transition mechanism with a
>clear end date. I am tired of "quoted-printable" solutions and all
>the problems they result in.
>Also why only IDNA? Why not like in UDNS with server support.
>Support at my site will be server based, as far as possible. It
>is much easier than upgrading all applications.
>
>   Dan
>
>
>
>
Bill Semich
President and Founder
WorldNames, Inc.
http://www.worldnames.net
bsemich@worldnames.net



From owner-idn@ops.ietf.org  Wed May 23 07:57:30 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA01428
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 07:57:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152WwE-0008pp-00
	for idn-data@psg.com; Wed, 23 May 2001 04:36:26 -0700
Received: from mail.ndl.net.nu ([208.36.200.249] helo=mail.nic.nu)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152WwD-0008ph-00
	for idn@ops.ietf.org; Wed, 23 May 2001 04:36:25 -0700
Received: from bill ([65.96.148.150]) by mail.nic.nu
          (Post.Office MTA v3.5.3 release 223 ID# 0-61576U100L100S0V35)
          with SMTP id nu; Wed, 23 May 2001 07:37:34 -0400
Message-Id: <3.0.5.32.20010523073339.05069c10@mail.nic.nu>
X-Sender: bill@mail.nic.nu
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Wed, 23 May 2001 07:33:39 -0400
To: Dan <Dan.Oscarsson@trab.se>, idn@ops.ietf.org,
        Marc.Blanchet@viagenie.qc.ca
From: bill@mail.nic.nu (J. William Semich)
Subject: Re: [idn] time to move
Cc: jseng@pobox.org.sg
In-Reply-To: <200105230944.f4N9iAo13947@malmo.trab.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I agree with Dan. Let's focus on a clear point of agreement, and ask for
consensus on *just* nameprep. 

So, for the record, I answer "no" to the straw poll, and propose a
more-limited poll on agreeing to move forward with nameprep.

I'd prefer to reconsider other alternatives, whether transition based or
not, such as UDNS, Paul and Marc's IDNE and John's proposal for a new class
(draft-klensin-dnsclass0e) instead of a permanent ACE solution like IDNA at
this point...

Regards,

Bill Semich

At 11:44 AM 5/23/01 +0200, Dan wrote:
>
>>>1) Are we going to use UTF-8 only? (and accept that this will force
>>>    many applications to get fixed, that otherwise could wait a long time
>>>    with fixing).
>>
>>this was not the design team recommendation and perceived wg concensus.
>
>That was long time ago. There have been much talking about UTF-8 since then.
>But I agree that most do not dare say "just UTF-8" so I expect
>a solution with both UTF-8 and ACE is what most think is best.
> 
>>This electronic straw poll is to find if the wg still think the 
>>idna-nameprep-ace is the way to go. If we find no concensus on 
>>idna-nameprep-ace proposal, then we go back to the drawing board.
>
>I do not think it answers that, because it does not specify the
>alternatives.
>
>I also dislike combining two things into one. Nameprep has some basic
>failures in which characters match which that should be agreed on first.
>Before it can go on.
>
>
>
>>>2) If the answer to 1) is No, the an ACE will be nedded.
>>>
>>>    The we get: Is the goal to have UTF-8 as nativ format in DNS in
>>>    the future, or are we going to use ACE forever?
>>>      - If we are going for UTF-8 then ACE is a transition mechanism.
>>>        The ACE should then be simple and fast to implement.
>>>      - If we are going for ACE forever, the ACE selected need to
>>>        be compact so that as many characters can be included in
>>>        as few bytes as possible.
>>
>>the ACE design team is working on that. If there is a concensus of the wg 
>>for idna-nameprep-ace, then the ACE design team will hopefully come to the 
>>wg with a recommendation.
>
>Why is the ACE design team working on that? It is something that
>should be discussed by all before we decide what ACE should be used.
>Where is the archive of the ACE design team work?
>
>If we decide that DNS should use UTF-8 and ACE is a transition
>mechanism, IDNA is only a temporary and partial solution to what we
>need. ACE support should be declared dead about 2010 so only UTF-8
>is supported.
>
>I do not want ACE for more than a transition mechanism with a
>clear end date. I am tired of "quoted-printable" solutions and all
>the problems they result in.
>Also why only IDNA? Why not like in UDNS with server support.
>Support at my site will be server based, as far as possible. It
>is much easier than upgrading all applications.
>
>   Dan
>
>
>
>



From owner-idn@ops.ietf.org  Wed May 23 09:41:03 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA04905
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 09:41:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152YSY-000Atg-00
	for idn-data@psg.com; Wed, 23 May 2001 06:13:54 -0700
Received: from mail.ndl.net.nu ([208.36.200.249] helo=mail.nic.nu)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152YSX-000Ata-00
	for idn@ops.ietf.org; Wed, 23 May 2001 06:13:53 -0700
Received: from bill ([65.96.148.150]) by mail.nic.nu
          (Post.Office MTA v3.5.3 release 223 ID# 0-61576U100L100S0V35)
          with SMTP id nu; Wed, 23 May 2001 09:15:02 -0400
Message-Id: <3.0.5.32.20010523091107.05066d00@mail.nic.nu>
X-Sender: bill@mail.nic.nu
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Wed, 23 May 2001 09:11:07 -0400
To: "James Seng/Personal" <James@Seng.cc>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
From: bill@mail.nic.nu (J. William Semich)
Subject: Re: [idn] requirements-07 
Cc: <idn@ops.ietf.org>, <brunner@nic-naa.net>
In-Reply-To: <032101c0e345$3db785e0$dd00a8c0@jamessonyvaio>
References: <200105230353.f4N3rSf68194@nic-naa.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 01:00 PM 5/23/01 +0800, James Seng/Personal wrote:
<snip>>ps: The reason for the slowness to response to your editorial is
because
>I have an filter which put emails from brunner@nic-naa.net in the same
>folder as Jeff Williams. You can consider it as /dev/null for all intent
>and purposes.
>
>-James Seng

Coming from the co-chair of this WG, who IMHO should be giving equal care
and consideration to input from all participants in the WG, this comment
and the behavior that it describes are wholly inappropriate.


Bill Semich/Personal





From owner-idn@ops.ietf.org  Wed May 23 12:43:58 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA09367
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 12:43:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152bM0-000ES3-00
	for idn-data@psg.com; Wed, 23 May 2001 09:19:20 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 152bLz-000ERp-00
	for idn@ops.ietf.org; Wed, 23 May 2001 09:19:19 -0700
Received: (qmail 3187 invoked by uid 1001); 23 May 2001 15:45:48 -0000
Date: 23 May 2001 15:45:48 -0000
Message-ID: <20010523154548.23749.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] time to move
References: <5.1.0.14.1.20010519150455.02e8fbd0@mail.viagenie.qc.ca> <20010521235057.26248.qmail@cr.yp.to> <5.1.0.14.2.20010522082111.081af5a8@dcrocker.net> <20010522220953.22977.qmail@cr.yp.to> <5.1.0.14.2.20010522201355.03bdaa20@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

More procedural flaws with this poll: the Subject line doesn't identify
it as a poll; and the deadline, today, is only three days after the poll
was announced.

Dave Crocker writes:
> For example, think how remarkable it is that you are so clear on the
> sense of the mailing list.  Why bother to take a straw poll?

I didn't say anything about ``the sense of the mailing list.'' I said
``Many of us think that moving at this point would be premature.'' Do
you understand what the word ``many'' means? 

> The center piece to the design philosophy is that it requires no
> change to server protocol engines or data base modules; it does not
> matter whether other proposals have that characteristic or not.

Of course it matters. Proposals compete on their merits. The very first
sentence of the IDNA ``design philosophy'' is the incorrect claim that
all previous proposals require changes to DNS servers.

---Dan



From owner-idn@ops.ietf.org  Wed May 23 13:08:53 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA10039
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 13:08:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152bwT-000FSL-00
	for idn-data@psg.com; Wed, 23 May 2001 09:57:01 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152bwS-000FSC-00
	for idn@ops.ietf.org; Wed, 23 May 2001 09:57:00 -0700
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id JAA16444;
	Wed, 23 May 2001 09:56:58 -0700
Message-Id: <5.1.0.14.2.20010523093558.02bbf510@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 23 May 2001 09:41:15 -0700
To: "D. J. Bernstein" <djb@cr.yp.to>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] time to move
Cc: idn@ops.ietf.org
In-Reply-To: <20010523154548.23749.qmail@cr.yp.to>
References: <5.1.0.14.1.20010519150455.02e8fbd0@mail.viagenie.qc.ca>
 <20010521235057.26248.qmail@cr.yp.to>
 <5.1.0.14.2.20010522082111.081af5a8@dcrocker.net>
 <20010522220953.22977.qmail@cr.yp.to>
 <5.1.0.14.2.20010522201355.03bdaa20@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 08:45 AM 5/23/2001, D. J. Bernstein wrote:
>More procedural flaws with this poll: the Subject line doesn't identify
>it as a poll; and the deadline, today, is only three days after the poll
>was announced.

Only two more flaws?  Dan, you can do better than that.  Remember, this is 
a survey and survey research involves extraordinarily subtle forces.

oops.  it's really a straw poll.  not a precise measure of the group.


>I didn't say anything about ``the sense of the mailing list.'' I said
>``Many of us think that moving at this point would be premature.'' Do
>you understand what the word ``many'' means?

Indeed.  The style of use that you employed is for the purpose of conveying 
import.  It attempts to claim that their is a substantial force behind a 
statement.

Unfortunately it is typically used as a debating technique when there is 
little real and objective substance to the "Many".  That is, where "many" 
really is more like the meaning used in very early societies, with limited 
math.  They would count one, two three, many.


>Of course it matters. Proposals compete on their merits. The very first
>sentence of the IDNA ``design philosophy'' is the incorrect claim that
>all previous proposals require changes to DNS servers.

The merit of a proposal is based on its technical content, Dan.

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 May 23 16:49:36 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA14774
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 16:49:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152fNP-000JVr-00
	for idn-data@psg.com; Wed, 23 May 2001 13:37:03 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152fNO-000JVj-00
	for idn@ops.ietf.org; Wed, 23 May 2001 13:37:02 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 152fNM-0007AY-00; Wed, 23 May 2001 13:37:00 -0700
Date: Wed, 23 May 2001 20:37:00 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] time to move
Message-ID: <20010523203700.F26947@arwen.cs.berkeley.edu>
References: <200105230944.f4N9iAo13947@malmo.trab.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <200105230944.f4N9iAo13947@malmo.trab.se>; from Dan.Oscarsson@trab.se on Wed, May 23, 2001 at 11:44:07AM +0200
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

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

> If we decide that DNS should use UTF-8 and ACE is a transition
> mechanism...

Please remember that DNS is not the problem.  DNS is just one of many
protocols that embed domain names.  Others include message headers,
SMTP, URIs, ssh keys, PGP keys, and on and on.  All these protocols, and
the software that implements them, will need to be revised if domain
names are allowed to contain non-LDH characters.

Also note that if ACE is a transition to UTF-8, then there are really
two transitions: one from LDH-only to ACE, and another from ACE
to UTF-8.  If ACE is seen as the solution, then there is only one
transition.

Finally, note that UTF-8 has issues with encoding efficiency (the length
of the encoded string).  It's excellent for Latin scripts, good for CJK
scripts, bad for some other popular scripts like Cyrillic and Arabic,
and horrible for most Indian and southeast Asian scripts.  UTF-16 is
excellent for CJK and bad for everything else.  An ACE can be designed
to be more balanced, achieving good or at least decent efficiency for
all scripts.

AMC



From owner-idn@ops.ietf.org  Wed May 23 17:47:17 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA16036
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 17:47:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152gGS-000KPi-00
	for idn-data@psg.com; Wed, 23 May 2001 14:33:56 -0700
Received: from sina.sharif.ac.ir ([62.41.32.2] ident=roozbeh)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152gGP-000KPY-00
	for idn@ops.ietf.org; Wed, 23 May 2001 14:33:54 -0700
Received: from localhost (roozbeh@localhost)
	by Sina.sharif.ac.ir (8.9.3/8.9.3) with ESMTP id CAA05343;
	Thu, 24 May 2001 02:03:25 +0430
Date: Thu, 24 May 2001 02:03:25 +0430 (IRDT)
From: Roozbeh Pournader <roozbeh@sharif.edu>
X-Sender: roozbeh@Sina.sharif.ac.ir
To: "Adam M. Costello" <amc@cs.berkeley.edu>
cc: idn@ops.ietf.org
Subject: Re: [idn] time to move
In-Reply-To: <20010523203700.F26947@arwen.cs.berkeley.edu>
Message-ID: <Pine.LNX.4.10.10105240159550.5141-100000@Sina.sharif.ac.ir>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk



On Wed, 23 May 2001, Adam M. Costello wrote:

> Finally, note that UTF-8 has issues with encoding efficiency (the
> length of the encoded string).  It's [...] bad for some other popular
> scripts like Cyrillic and Arabic, [...]

Would you describe why do you see UTF-8 bad for Arabic and Cyrillic? You
don't want to suggest usin 8-bit character sets, do you?




From owner-idn@ops.ietf.org  Wed May 23 18:04:33 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA16309
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 18:04:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152gYs-000KWw-00
	for idn-data@psg.com; Wed, 23 May 2001 14:52:58 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152gYs-000KWp-00
	for idn@ops.ietf.org; Wed, 23 May 2001 14:52:58 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 152gYq-0007FB-00; Wed, 23 May 2001 14:52:56 -0700
Date: Wed, 23 May 2001 21:52:56 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] time to move
Message-ID: <20010523215256.G26947@arwen.cs.berkeley.edu>
References: <20010523203700.F26947@arwen.cs.berkeley.edu> <Pine.LNX.4.10.10105240159550.5141-100000@Sina.sharif.ac.ir>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <Pine.LNX.4.10.10105240159550.5141-100000@Sina.sharif.ac.ir>; from roozbeh@sharif.edu on Thu, May 24, 2001 at 02:03:25AM +0430
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Roozbeh Pournader <roozbeh@sharif.edu> wrote:

> Would you describe why do you see UTF-8 bad for Arabic and Cyrillic?

Because for those scripts the ACE encoding is usually significantly
smaller than the UTF-8 encoding.

Seen another way, the Cyrillic and Arabic alphabets are about the same
size as the Latin alphabet, so the amount of information per character
is about the same for all three scripts, but UTF-8 uses almost double
the number of octets per character for Cyrillic and Arabic as opposed to
Latin.

AMC



From owner-idn@ops.ietf.org  Wed May 23 18:14:41 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA16456
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 18:14:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152giU-000Kbk-00
	for idn-data@psg.com; Wed, 23 May 2001 15:02: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.16 #1)
	id 152giT-000Kbd-00
	for idn@ops.ietf.org; Wed, 23 May 2001 15:02:53 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4NM25f71405;
	Wed, 23 May 2001 18:02:05 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105232202.f4NM25f71405@nic-naa.net>
To: "Adam M. Costello" <amc@cs.berkeley.edu>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] time to move 
In-Reply-To: Your message of "Wed, 23 May 2001 20:37:00 -0000."
             <20010523203700.F26947@arwen.cs.berkeley.edu> 
Date: Wed, 23 May 2001 18:02:05 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Adam,

In your reply to Dan Oscarsson you wrote:

> Please remember that DNS is not the problem.  DNS is just one of many
> protocols that embed domain names.  Others include message headers,

How does dns embed domain names? Is the resolution question (assuming it
still exists) equivalent to the transparent to code-set-dependent apps
question?

I'd the impression it wasn't, and that most of this group's focus was on
constraints for, or elimination of, the transparency question.

I fail to see the point of your second note.

The issue of encoding efficiency is interesting. A small cabal (the IE6
P3P implementors, myself and some of the P3P Spec WG considered just how
"compact" to make XML privacy policies on cookies. Two other groups, the
Mozillia and Amaya developers, and quite a few IETF I-Ds hopefully set on
a standards track trajectory, seem genuinely committed to XML. If your
view is the best one, then most of these people, and their products in the
56k-bandwidth-defined mass market are very poorly advised.

As today is "call me an idiot" day, would you do me the kindness of letting
me know where the i18n architectures of AIX 3.2, Solaris 2.6, and HP-UX 10
and their successors in interests, all of which use, or anticipated use of
utf8 for internal encoding. I've a lasting interest in the strengths, and
weaknesses, of "code set independent architecture" conception, implementation
and deployment in mid-90's POSIX operating systems.

I've obviously failed to grasp something deep and profound, either about
l10n-capable edge devices (other than cell phones), or last-mile network
characteristics, and so I've probably made a muddle of the dns registry
provisioning protocol, which a) uses XML, b) allows for utf8 in the
encoding of technical and social data, c) declines to impose heroic hardware
on its nodes, and d) also declines to impose heroic bandwidth on its links.

Tia,
Eric



From owner-idn@ops.ietf.org  Wed May 23 18:32:06 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA16699
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 18:32:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152h1a-000KkK-00
	for idn-data@psg.com; Wed, 23 May 2001 15:22: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.16 #1)
	id 152h1Z-000KkE-00
	for idn@ops.ietf.org; Wed, 23 May 2001 15:22:37 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4NMM1f71520
	for <idn@ops.ietf.org>; Wed, 23 May 2001 18:22:01 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105232222.f4NMM1f71520@nic-naa.net>
To: idn@ops.ietf.org
Subject: Re: [idn] time to move
Date: Wed, 23 May 2001 18:22:01 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk


> Roozbeh Pournader <roozbeh@sharif.edu> wrote:
> 
> > Would you describe why do you see UTF-8 bad for Arabic and Cyrillic?
> 
> Because for those scripts the ACE encoding is usually significantly
> smaller than the UTF-8 encoding.
> 
> Seen another way, the Cyrillic and Arabic alphabets are about the same
> size as the Latin alphabet, so the amount of information per character
> is about the same for all three scripts, but UTF-8 uses almost double
> the number of octets per character for Cyrillic and Arabic as opposed to
> Latin.
> 
> AMC

Is octet counting an argument you'd like to offer as controlling for
edge device functional requirements in the end2end-interest list?

If you'll assume for the moment that interoperation implies "over a wire",
then
	it (octet count arguements) isn't compelling where intermediary
	hops are concerned,
and
	it (octet count arguements) isn't compelling where host requirements
	are concerned,
and
	it (octet count arguements) may be defensible only in last-mile
	bandwidth settings, which are XML dominated where "interactive".

Just what does that assumption leave?

What assumption is better?

Starting about XPG/4.2, we (os vendors) have been trudging down the utf-8
road, from Redmond, Austin, Mtn. View, Coopertino, even Berkeley. Has it
been an error?

Tia,
Eric



From owner-idn@ops.ietf.org  Wed May 23 19:11:05 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA17382
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 19:11:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152hVW-000L34-00
	for idn-data@psg.com; Wed, 23 May 2001 15:53:34 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152hVV-000L2x-00
	for idn@ops.ietf.org; Wed, 23 May 2001 15:53:33 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 152hVT-0007Jl-00; Wed, 23 May 2001 15:53:31 -0700
Date: Wed, 23 May 2001 22:53:31 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] time to move
Message-ID: <20010523225331.H26947@arwen.cs.berkeley.edu>
References: <20010523203700.F26947@arwen.cs.berkeley.edu> <200105232202.f4NM25f71405@nic-naa.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <200105232202.f4NM25f71405@nic-naa.net>; from brunner@nic-naa.net on Wed, May 23, 2001 at 06:02:05PM -0400
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net> wrote:

> > Please remember that DNS is not the problem.  DNS is just one of
> > many protocols that embed domain names.  Others include message
> > headers,
>
> How does dns embed domain names?

Domain names appear in message headers, SMTP commands, URIs, ssh keys,
SSL certificates, and DNS requests and responses.  All I meant was that
DNS is just one of many protocols that exchange messages containing
domain names.  And virtually all such protocols (except DNS, actually)
assume that domain names contain only LDH characters and dots.  What
happens in these protocols if domain names contain other characters?  I
think most of the protocol specifications either don't say (in which
case implementations might do anything) or they say it's an error.

> Is the resolution question (assuming it still exists) equivalent to
> the transparent to code-set-dependent apps question?

I'm not exactly sure what you mean by either one, but they sound
different.  Resolving IDNs is going to be pretty easy no matter what
we do, because DNS is pretty versatile.  ACE makes resolution trivial,
but I do *not* see that as an important argument in favor of ACE.  The
argument for ACE is that it allows IDNs to flow through all the untold
existing protocols and software unharmed.

> I fail to see the point of your second note.

Which was:

    Also note that if ACE is a transition to UTF-8, then there are
    really two transitions: one from LDH-only to ACE, and another from
    ACE to UTF-8.  If ACE is seen as the solution, then there is only
    one transition.

Is the point not obvious?  Transitions are typically difficult and
disruptive.  Two transitions are twice as difficult and disruptive as
one.

> The issue of encoding efficiency is interesting.
> [long defense of UTF-8, XML, and inefficient encodings in general]

I did not mean to imply that UTF-8 is bad in general, or that encoding
efficiency is important in general.  UTF-8 has many amazingly wonderful
properties: all ASCII strings are UTF-8 strings, substrings cannot be
misinterpreted, lexicographic sorting of code points is preserved, and
no look-ahead is required for decoding.  I am very impressed by the
elegance of UTF-8, and would endorse it for almost any situation where
you want to use a single character encoding.

Encoding efficiency is usually not a top concern.  Bandwith grows, disks
grow.  Making things easy and versatile is usually more important than
saving bits.

But in this case, we have a hard limit of 63 bytes per label.  That's
why encoding efficiency matters in this case.

Although I suppose, if you already expect to update every protocol and
every piece of software that uses domain names, you might as well remove
the 63-byte limit.  In that case, I would have no problem with UTF-8.
But I'm extremely skeptical of that whole approach.

AMC



From owner-idn@ops.ietf.org  Wed May 23 21:35:20 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA20380
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 21:35:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152jiT-000NYn-00
	for idn-data@psg.com; Wed, 23 May 2001 18:15:05 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.16 #1)
	id 152jiT-000NYB-00
	for idn@ops.ietf.org; Wed, 23 May 2001 18:15:05 -0700
Received: from yamada (e144133.ppp.asahi-net.or.jp [211.13.144.133])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id KAA13070;
	Thu, 24 May 2001 10:15:20 +0900 (JST)
Message-Id: <4.2.0.58.J.20010524082253.03d5c2d0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 24 May 2001 08:27:03 +0900
To: "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] time to move
In-Reply-To: <20010523225331.H26947@arwen.cs.berkeley.edu>
References: <200105232202.f4NM25f71405@nic-naa.net>
 <20010523203700.F26947@arwen.cs.berkeley.edu>
 <200105232202.f4NM25f71405@nic-naa.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 22:53 01/05/23 +0000, Adam M. Costello wrote:

>But in this case, we have a hard limit of 63 bytes per label.  That's
>why encoding efficiency matters in this case.
>
>Although I suppose, if you already expect to update every protocol and
>every piece of software that uses domain names, you might as well remove
>the 63-byte limit.  In that case, I would have no problem with UTF-8.

How many 'real' domain names are longer than 20 characters?
By 'real' I mean those not made artificially to meet the limit,
or otherwise more looking like a joke than anything else.
And how many of these could be shortened with a bit of
ingenuity if needed? And how many of these could be dealt
with by splitting them into two labels?

I see the 63-byte limit as something we have to ask ourselves
carefully about, but not at all as a show-stopper for UTF-8.

Regards,   Martin.



From owner-idn@ops.ietf.org  Wed May 23 22:41:45 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA21967
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 22:41:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152kiu-000Oxt-00
	for idn-data@psg.com; Wed, 23 May 2001 19:19:36 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152kit-000Oxn-00
	for idn@ops.ietf.org; Wed, 23 May 2001 19:19:35 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4O2Ivf72172;
	Wed, 23 May 2001 22:18:57 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105240218.f4O2Ivf72172@nic-naa.net>
To: "Adam M. Costello" <amc@cs.berkeley.edu>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] time to move 
In-Reply-To: Your message of "Wed, 23 May 2001 22:53:31 -0000."
             <20010523225331.H26947@arwen.cs.berkeley.edu> 
Date: Wed, 23 May 2001 22:18:57 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

...
> DNS is just one of many protocols that exchange messages containing
> domain names

In a fairly peculiar and constrained way. Unique one might say.

(dns) resolution != (apps) transparency. Good, or at last that is
comfortably consistent with my own ignorance and sloth.

I still fail the novel point of your second note, and I'm still
surprised that ACE could be considered as anything other than a
"temporary", and controversial fix, unless the problem scope has
changed without my being aware of it.

> [long defense of UTF-8, XML, and inefficient encodings in general]

Thanks for the send-up, but a whole bunch of people are betting their
time and money that there are other "efficiencies" than octet counting.
Thus far, the router, host, link, and even last-mile vendors haven't
stopped them with stakes, nooses, or other bits of constructive criticism,
and argued forcefully for "efficiency".

If the label-space is the issue referred to by "inefficiency", then
as a label-space vendor I'm really interested.

	I've blocked or otherwise squashed labels shorter than two
	octets, and have an idea as to how many "TLA" labels I will
	sell before year's end, and have a poorer idea as to how
	many labels I will sell over five years that are 20 ASCII
	characters or less, or at 30 alphanumerics plus diacriticals.

	I haven't a damn clue what the demand is for labels twice
	that size in the ASCII or ISO8859-* markets, or how important
	labels this size are in the CJKV market -- except that CNNIC
	already went utf8.

	True, the CNNIC presentation and oral comments at -50 did cite
	label octet limits as inconvenient when the encoding is utf8,
	but they obviously made a choice -- an engineering trade-off,
	and rolled out a utf8 architecture.

That's just our market research, and CNNIC's deployment experience. Your
mailage may vary, and you can see Martin's comment as well.

Cheers,
Eric



From owner-idn@ops.ietf.org  Wed May 23 23:04:52 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA22163
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 23:04:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152lH6-000Pkd-00
	for idn-data@psg.com; Wed, 23 May 2001 19:54:56 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 152lH5-000PkX-00
	for idn@ops.ietf.org; Wed, 23 May 2001 19:54:55 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id WAA13233;
        Wed, 23 May 2001 22:54:51 -0400 (EDT)
Message-Id: <200105240254.WAA13233@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
cc: "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] time to move 
In-reply-to: Your message of "Wed, 23 May 2001 22:18:57 EDT."
             <200105240218.f4O2Ivf72172@nic-naa.net> 
Date: Wed, 23 May 2001 22:54:51 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> I still fail the novel point of your second note, and I'm still
> surprised that ACE could be considered as anything other than a
> "temporary", and controversial fix, unless the problem scope has
> changed without my being aware of it.

it is less controversial because it is easier than the alternatives.

it is perhaps also worthwhile to point out that fixes based on 
EDNS will not work so well through intermediaries.  so if we want
a utf-8 query protcol in addition to the ACE query protocol
that we need for compatibility with existing applications, then
we might have to wait a while before it can actually be used.

for me the choice is clear: ACE is necessary in the short term.
a utf-8 query protocol might be desirable in the longer term,
especially for new protocols that don't have the burden of 
backward compatibility.  but we have the luxury of defining 
the utf-8 query protocol after we get the ACE solution out the door.  

we cannot make the jump directly to utf-8 - it is simply not practical.

Keith



From owner-idn@ops.ietf.org  Wed May 23 23:12:46 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA22229
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 23:12:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152lPm-000Pxn-00
	for idn-data@psg.com; Wed, 23 May 2001 20:03: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.16 #1)
	id 152lPl-000Pxh-00
	for idn@ops.ietf.org; Wed, 23 May 2001 20:03:53 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4O33Gf72353;
	Wed, 23 May 2001 23:03:16 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105240303.f4O33Gf72353@nic-naa.net>
To: Keith Moore <moore@cs.utk.edu>
cc: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org,
        brunner@nic-naa.net
Subject: Re: [idn] time to move 
In-Reply-To: Your message of "Wed, 23 May 2001 22:54:51 EDT."
             <200105240254.WAA13233@astro.cs.utk.edu> 
Date: Wed, 23 May 2001 23:03:16 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> we cannot make the jump directly to utf-8 - it is simply not practical.

Does "we" include CNNIC?



From owner-idn@ops.ietf.org  Wed May 23 23:24:33 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA22290
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 23:24:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152lWi-0000A9-00
	for idn-data@psg.com; Wed, 23 May 2001 20:11:04 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 152lWi-0000A3-00
	for idn@ops.ietf.org; Wed, 23 May 2001 20:11: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 XAA13377;
        Wed, 23 May 2001 23:11:00 -0400 (EDT)
Message-Id: <200105240311.XAA13377@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
cc: Keith Moore <moore@cs.utk.edu>, "Adam M. Costello" <amc@cs.berkeley.edu>,
        idn@ops.ietf.org
Subject: Re: [idn] time to move 
In-reply-to: Your message of "Wed, 23 May 2001 23:03:16 EDT."
             <200105240303.f4O33Gf72353@nic-naa.net> 
Date: Wed, 23 May 2001 23:11:00 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Does "we" include CNNIC?

it means "we" the Internet.  various islands can go to utf-8 if they
don't care about backward compatibility.  but the purpose of a standard
is to provide a solution that everybody can use.  we don't need to provide
a solution that can only be used by an island - others are already
doing that quite well.



From owner-idn@ops.ietf.org  Wed May 23 23:45:30 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA22871
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 23:45:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152ls8-0000h1-00
	for idn-data@psg.com; Wed, 23 May 2001 20:33:12 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.16 #1)
	id 152ls7-0000gp-00
	for idn@ops.ietf.org; Wed, 23 May 2001 20:33:11 -0700
Received: from yamada (e144133.ppp.asahi-net.or.jp [211.13.144.133])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id MAA13463;
	Thu, 24 May 2001 12:33:01 +0900 (JST)
Message-Id: <4.2.0.58.J.20010524121238.00cec4d0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 24 May 2001 12:32:11 +0900
To: Keith Moore <moore@cs.utk.edu>,
        Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
From: Martin Duerst <duerst@w3.org>
Subject: Why we can go directly to UTF-8 (was: Re: [idn] time to move)
Cc: "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
In-Reply-To: <200105240254.WAA13233@astro.cs.utk.edu>
References: <Your message of "Wed, 23 May 2001 22:18:57 EDT." <200105240218.f4O2Ivf72172@nic-naa.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Hello Keith,

Your conclusion

>we cannot make the jump directly to utf-8 - it is simply not practical.

isn't really a given. The main point in support of UTF-8 is that
the main drive for idns is coming from Web usage (http URIs).
Email is a very clear second, and all other usages don't have
1% of the pressure and urgency we have for Web usage. If we can
solve the problem for the Web and for Email, we get some time
to work on the rest. Even if we have a solution that in the
near term only works on the Web, that gives us quite some time.

This correlates extremely well with the fact that the average
Web browser is about the easiest place to introduce UTF-8 idns
(or any other idn solution, for that matter), and that the main
protocol there (HTTP) also should work nicely. Overall, it may
take ten years, but the things people want most will work much
sooner. Also, we are moving towards the final solution directly.

Also, I don't buy that once an ACE is deployed, we will come back
to work on UTF-8. Also, I don't buy that application protocols
will do the work to upgrade to UTF-8 internally if they can just
use ACE. Some might, but most won't. And the result would look
strangely backwards. On the other hand, if any particular
application (e.g. email) really thinks they need ACE, they
can do that on their own, and bear the consequences.

Also, if one puts together the protocol issues, the user interface
issues, and the management issues (zone files, scripts, and the like),
rather than just looking at the protocol issues, ACE is about as
impractical as anything else.

Regards,   Martin.


At 22:54 01/05/23 -0400, Keith Moore wrote:
> > I still fail the novel point of your second note, and I'm still
> > surprised that ACE could be considered as anything other than a
> > "temporary", and controversial fix, unless the problem scope has
> > changed without my being aware of it.
>
>it is less controversial because it is easier than the alternatives.
>
>it is perhaps also worthwhile to point out that fixes based on
>EDNS will not work so well through intermediaries.  so if we want
>a utf-8 query protcol in addition to the ACE query protocol
>that we need for compatibility with existing applications, then
>we might have to wait a while before it can actually be used.
>
>for me the choice is clear: ACE is necessary in the short term.
>a utf-8 query protocol might be desirable in the longer term,
>especially for new protocols that don't have the burden of
>backward compatibility.  but we have the luxury of defining
>the utf-8 query protocol after we get the ACE solution out the door.
>
>we cannot make the jump directly to utf-8 - it is simply not practical.
>
>Keith




From owner-idn@ops.ietf.org  Wed May 23 23:58:12 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA22988
	for <idn-archive@lists.ietf.org>; Wed, 23 May 2001 23:58:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152m7d-000182-00
	for idn-data@psg.com; Wed, 23 May 2001 20:49:13 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 152m7c-00017w-00
	for idn@ops.ietf.org; Wed, 23 May 2001 20:49:12 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id XAA13613;
        Wed, 23 May 2001 23:49:06 -0400 (EDT)
Message-Id: <200105240349.XAA13613@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Martin Duerst <duerst@w3.org>
cc: Keith Moore <moore@cs.utk.edu>,
        Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: Why we can go directly to UTF-8 (was: Re: [idn] time to move) 
In-reply-to: Your message of "Thu, 24 May 2001 12:32:11 +0900."
             <4.2.0.58.J.20010524121238.00cec4d0@sh.w3.mag.keio.ac.jp> 
Date: Wed, 23 May 2001 23:49:06 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> 
> Your conclusion
> 
> >we cannot make the jump directly to utf-8 - it is simply not practical.
> 
> isn't really a given. The main point in support of UTF-8 is that
> the main drive for idns is coming from Web usage (http URIs).

the 'main drive' for IDNS is irrelevant.  the major applications do not
exist in isolation; web and email together touch almost everything else.
we can't solve the IDN problem for just the  two and pretend that it will
not do harm to other applications; the boundaries are not that clean.

> Also, I don't buy that once an ACE is deployed, we will come back
> to work on UTF-8. 

I didn't say that we would.  I said that we "might".  But I suspect
that it's at least worthwhile to consider as a followon effort, and I
also suspect that there are enough people who  are willing to do the 
work.  Whether application developers will use it is a different
matter.  But it's hard to see why they wouldn't use it if their protocols
are using UTF-8 internally anyway.

> Also, I don't buy that application protocols
> will do the work to upgrade to UTF-8 internally if they can just
> use ACE. Some might, but most won't. And the result would look
> strangely backwards. 

I didn't say that they would do the work to upgrade to UTF-8, and it's
not even clear that it's desirable overall for them to do so.  I don't 
think this is backwards at all - it is just the way of things.  Old 
interfaces that work tend to get used with few changes for a very long time.  
The POTS telephone interface is ancient and very clunky, and we could
do far better today.  but almost all subscriber equipment still uses it.

> On the other hand, if any particular
> application (e.g. email) really thinks they need ACE, they
> can do that on their own, and bear the consequences.

no they can't, because unless DNS supports queries by ACE from day one,
those applications will not work with ACE names. 

> Also, if one puts together the protocol issues, the user interface
> issues, and the management issues (zone files, scripts, and the like),
> rather than just looking at the protocol issues, ACE is about as
> impractical as anything else.

all of the above issues exist with each of the solution paths.
ACE wins because it has the best backward compabtibility and the
lowest barrier to quick deployment.

Keith



From owner-idn@ops.ietf.org  Thu May 24 00:01:43 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA23022
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 00:01:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152m3n-000115-00
	for idn-data@psg.com; Wed, 23 May 2001 20:45:15 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152m3m-00010z-00
	for idn@ops.ietf.org; Wed, 23 May 2001 20:45:14 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 152m3l-0007qf-00; Wed, 23 May 2001 20:45:13 -0700
Date: Thu, 24 May 2001 03:45:13 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] time to move
Message-ID: <20010524034513.J26947@arwen.cs.berkeley.edu>
References: <20010523225331.H26947@arwen.cs.berkeley.edu> <200105240218.f4O2Ivf72172@nic-naa.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <200105240218.f4O2Ivf72172@nic-naa.net>; from brunner@nic-naa.net on Wed, May 23, 2001 at 10:18:57PM -0400
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net> wrote:

> I'm still surprised that ACE could be considered as anything other
> than a "temporary", and controversial fix

Well, sometimes good ideas are surprising. :)  I admit that when I first
heard about ACE, it struck me as an ugly hack.  But once I realized what
an interoperability nightmare it would be to have domain names with
no LDH representation, my opinion changed.

New and updated protocols are free to support UTF-8 if they wish, but
the ACE representation will need to continue to work for a long time,
because domain names can pass through old protocols and old software
along the way.  What compelling reason is there to set a deadline beyond
which ACEs will stop working?

> Thus far, the router, host, link, and even last-mile vendors haven't
> stopped them with stakes, nooses, or other bits of constructive
> criticism, and argued forcefully for "efficiency".

I don't think there is any shortage of bytes on links or in routers.
It's only in domain name labels where there's a limited supply.

> True, the CNNIC presentation and oral comments at -50 did cite label
> octet limits as inconvenient when the encoding is utf8, but they
> obviously made a choice -- an engineering trade-off, and rolled out a
> utf8 architecture.

UTF-8 is not bad for Chinese.  21 Chinese characters is plenty of room,
because there's a lot of information per character (most words are two
characters).  But UTF-8 would impose the same 21-character limit on most
Indian and southeast Asian scripts, and those characters are comparable
to Latin letters in terms of information content--it takes several of
them to make a word or a name.

The greatest thing about UTF-8 is its compatibility with ASCII.  But in
the case of IDN, if you care about compatibility, you need ACE.  If you
don't care about compatibility, and you segregate the IDNs from the LDH
domain names, then UTF-16 is probably better than UTF-8, because then
everyone would get 31 characters per label, which even I would concede
ought to be enough.  I wonder why CNNIC didn't go with UTF-16.  Maybe
they don't plan to segregate the IDNs from the LDH domain names, and
are counting on software that uses UTF-8 internally to "just work" by
accident.  Of course, some things will just break, too.

AMC



From owner-idn@ops.ietf.org  Thu May 24 00:07:32 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA23115
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 00:07:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152mHV-0001Ql-00
	for idn-data@psg.com; Wed, 23 May 2001 20:59:25 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152mHU-0001Qf-00
	for idn@ops.ietf.org; Wed, 23 May 2001 20:59:24 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4O3wgf72532;
	Wed, 23 May 2001 23:58:42 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105240358.f4O3wgf72532@nic-naa.net>
To: Keith Moore <moore@cs.utk.edu>
cc: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org,
        brunner@nic-naa.net
Subject: Re: [idn] time to move 
In-Reply-To: Your message of "Wed, 23 May 2001 23:11:00 EDT."
             <200105240311.XAA13377@astro.cs.utk.edu> 
Date: Wed, 23 May 2001 23:58:42 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Does "we" exclude anyone?

For quite a long time "we" ment .arpa, as in BRUNNER@SRI-SPAM.ARPA.

> various islands can go to utf-8 if they don't care about backward
> compatibility

I don't have a whole lot of 3Mb/sec Type I Ethernet lying about these
days (see above). I also don't have XNS forcing me to maintain bridged
subnets, and generally don't have pervasive obsolecense controlling my
site's infrastructure. What I do have that is obnoxious is MS Exchange,
but that's another form of brain-death.

I'm leery of letting the phrase "backward compatibility" run the show,
as it may not care very much about anything but the (vain)glorious past.
Recall, in .ARPA-time, packets to the PRC was less likely than to RSRE.

> the purpose of a standard is to provide a solution that everybody can use

Hmm. I don't suppose anyone (other than Ken Lunde) has a clue how many times
an ASCII compatible extension has been adopted by sundry national standards
bodies (non-US, obviously, lack of necessity) which for some reason simply
haven't been "adopted by the internauters" ("us" in some locales).

The CJK series of standards is stricking in its optimism that if ASCII is
repeated sufficiently often, then its extension will be advanced (somehow).
From JIS C 6226-1978 to the present. It would be really funny if we were in
their shoes, trying to deal with some indifferent EBCDIC monster that made
sounds like "global transparancy" and "backward compatibility" every time
we tried to get it modernized. Oh. Been there. Done that. Got the tee-shirt.

> we don't need to provide a solution that can only be used by an island

Isn't this slightly disengenious?

Isn't the line of march of uniqueness and consistency and so forth predicated
upon the inexistence of ... "island(s)", and the non-deployment of utf8?

I think I'd like a helping of ECE please (EBCDIC COMPATIBLE EXTENION, shouted
naturally), and some variable length bytes on the side.

Eric



From owner-idn@ops.ietf.org  Thu May 24 00:23:02 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA23218
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 00:23:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152mRP-0001hb-00
	for idn-data@psg.com; Wed, 23 May 2001 21:09:39 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 152mRO-0001hV-00
	for idn@ops.ietf.org; Wed, 23 May 2001 21:09:38 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id AAA13879;
        Thu, 24 May 2001 00:09:37 -0400 (EDT)
Message-Id: <200105240409.AAA13879@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
X-PGP-Key: 2F07A741 ; 78 15 8E 8B C0 06 5D D1  BC 08 05 7F 42 81 7E 90 
To: idn@ops.ietf.org
Subject: [idn] Why we cannot go directly to UTF-8
cc: moore@cs.utk.edu
From: Keith Moore <moore@cs.utk.edu>
Date: Thu, 24 May 2001 00:09:37 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

It's really quite simple.

If we use UTF-8 names, each component in a signal path that handles
an IDN has to be upgraded before the application will work with IDNs.

For email, this means every UA, MTA, message store, mail filter,
mailing list, etc that uses the addresses in the header or
envelope of a message.  For the web, this means every web browser,
proxy, cache, and origin server that makes use of domain names
in the request or response (header or payload).  For both cases,
it means that every DNS query library, resolver, cache, and server
involved in the lookups supports UTF-8 also (unless you believe
that the existing ones will already support UTF-8 without protocol
extensions, which is far from a given).  There's little incentive
to upgrade because so many other components need to be upgraded
before you can get reliable operation.

If we use ASCII compatible names, each component in a signal path
that handles a domain name can upgrade independently, and things
will keep working - they just won't display the name as nicely if 
they're not updated.    And only the components that interface with 
users need to be upgraded before the users see a benefit.

It's easier to get real IDN support into the various components 
using ASCII compatible names because fewer components need to be
upgraded.  And the incentives for adoption are greater with ASCII 
names because the benefit of upgrading will be seen sooner.

Users won't care about whether the applications protocols represent 
IDNs in ACE or UTF-8.  But they will care about whether their
applications support IDNs.  ACE lets them do so far more quickly.

Keith



From owner-idn@ops.ietf.org  Thu May 24 00:35:51 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA23644
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 00:35:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152mYA-0001ta-00
	for idn-data@psg.com; Wed, 23 May 2001 21:16:38 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 152mY9-0001tU-00
	for idn@ops.ietf.org; Wed, 23 May 2001 21:16:37 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id AAA13928;
        Thu, 24 May 2001 00:16:33 -0400 (EDT)
Message-Id: <200105240416.AAA13928@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
cc: Keith Moore <moore@cs.utk.edu>, "Adam M. Costello" <amc@cs.berkeley.edu>,
        idn@ops.ietf.org
Subject: Re: [idn] time to move 
In-reply-to: Your message of "Wed, 23 May 2001 23:58:42 EDT."
             <200105240358.f4O3wgf72532@nic-naa.net> 
Date: Thu, 24 May 2001 00:16:33 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> I don't have a whole lot of 3Mb/sec Type I Ethernet lying about these
> days (see above). 

perhaps not.  but the folks I know where were using IP over 3Mb/sec
Ethernet are still using IP.  IPv4 is starting to look obsolete due
to a shortage of addresses, but I don't know anyone who thinks it's
going to be discarded anytime soon.

> Isn't the line of march of uniqueness and consistency and so forth predicated
> upon the inexistence of ... "island(s)", and the non-deployment of utf8?

it's predicated on the non-deployment of utf-8 *in Internet applications*
*at the time the IDN solution is deployed*.  it is currently the case
that few Internet applications support utf-8, and this isn't likely to 
change in the near future.

if you want to wait until everything else  is using utf-8 before deploying
IDNs that use utf-8, feel free.  I suspect that most of us don't want
to wait that long.  I also suspect that the fastest way to get to having
applications use utf-8 natively (if that's even worth the trouble)
is to use ACE IDNs in the near term.

Keith



From owner-idn@ops.ietf.org  Thu May 24 00:36:41 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA23655
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 00:36:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152mYq-0001v2-00
	for idn-data@psg.com; Wed, 23 May 2001 21:17:20 -0700
Received: from [159.226.6.42] (helo=pier.cnnic.net.cn)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152mYp-0001uu-00
	for idn@ops.ietf.org; Wed, 23 May 2001 21:17:20 -0700
Received: from deng ([159.226.7.68]) by pier.cnnic.net.cn
          (Netscape Mail Server v2.02) with SMTP id AAA22484;
          Thu, 24 May 2001 12:18:58 +0800
Message-ID: <012001c0e407$b09172c0$4407e29f@cnnic.net.cn>
Reply-To: =?gb2312?B?tcvP6A==?= <deng@cnnic.net.cn>
From: deng@pier.cnnic.net.cn (deng)
To: "Keith Moore" <moore@cs.utk.edu>,
        "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
Cc: "Keith Moore" <moore@cs.utk.edu>, "Adam M. Costello" <amc@cs.berkeley.edu>,
        <idn@ops.ietf.org>
References: <200105240311.XAA13377@astro.cs.utk.edu>
Subject: Re: [idn] time to move 
Date: Thu, 24 May 2001 12:12:04 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by ietf.org id AAA23655

Eric:

We are talk about technological solutions and problems. We should allow
any opinions. ANY USERs have the right to ask for using his language 
and his script. 

ANY ATTACKs are nonsensical,it have no help to solve problem.
......

CNNIC are friendly to anyone. 

What we should do is:
Keep quiet and think what's the best solution.

Deng Xiang
CNNIC CDNGROUP
2001.5.24



> > Does "we" include CNNIC?
> 
> it means "we" the Internet.  various islands can go to utf-8 if they
> don't care about backward compatibility.  but the purpose of a standard
> is to provide a solution that everybody can use.  we don't need to provide
> a solution that can only be used by an island - others are already
> doing that quite well.
> 


From owner-idn@ops.ietf.org  Thu May 24 02:26:25 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAB05884
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 02:26:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152oLC-00051f-00
	for idn-data@psg.com; Wed, 23 May 2001 23:11:22 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 152oLB-00051Y-00
	for idn@ops.ietf.org; Wed, 23 May 2001 23:11:21 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 33D3BFFC04; Thu, 24 May 2001 14:13:59 +0800 (SGT)
Message-ID: <062b01c0e418$42692930$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        "J. William Semich" <bill@mail.nic.nu>
Cc: <idn@ops.ietf.org>, <brunner@nic-naa.net>
References: <200105230353.f4N3rSf68194@nic-naa.net> <3.0.5.32.20010523091107.05066d00@mail.nic.nu>
Subject: Re: [idn] requirements-07 
Date: Thu, 24 May 2001 14:10:40 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I have some other personal conflict with Eric. I have put him on the
filter because I do not want to wish to spend my time arguing (or
getting upset) over his mails to me. My filter on him is not a
representation of his technical contribution nor ability but rather a
personal thing between two of us.

I wish I have a better excuse but I don't. I apologise to the Working
Group and to Eric Brunner if any of you gets the wrong idea.

ps: mails posted to the mailing lists as precedence over any other
filter so I do read every mail on the list.

-James Seng

----- Original Message -----
From: "J. William Semich" <bill@mail.nic.nu>
To: "James Seng/Personal" <James@Seng.cc>; "Eric Brunner-Williams in
Portland Maine" <brunner@nic-naa.net>
Cc: <idn@ops.ietf.org>; <brunner@nic-naa.net>
Sent: Wednesday, May 23, 2001 9:11 PM
Subject: Re: [idn] requirements-07


> At 01:00 PM 5/23/01 +0800, James Seng/Personal wrote:
> <snip>>ps: The reason for the slowness to response to your editorial
is
> because
> >I have an filter which put emails from brunner@nic-naa.net in the
same
> >folder as Jeff Williams. You can consider it as /dev/null for all
intent
> >and purposes.
> >
> >-James Seng
>
> Coming from the co-chair of this WG, who IMHO should be giving equal
care
> and consideration to input from all participants in the WG, this
comment
> and the behavior that it describes are wholly inappropriate.
>
>
> Bill Semich/Personal
>
>




From owner-idn@ops.ietf.org  Thu May 24 02:30:39 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA06175
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 02:30:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152oEf-0004nO-00
	for idn-data@psg.com; Wed, 23 May 2001 23:04:37 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.16 #1)
	id 152oEe-0004nH-00
	for idn@ops.ietf.org; Wed, 23 May 2001 23:04:36 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH9bcopsRQlWg+RSGoFyxA8tzQykdLHFIkw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id F57C6G73; Thu, 24 May 2001 02:03:41 EDT
To: idn@ops.ietf.org
Cc: liana.ydisg@juno.com
Date: Wed, 23 May 2001 23:16:34 -0700
Subject: [idn] Working direction of IDN
Message-ID: <20010523.231637.-774175.2.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.5
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-14,25,31-32
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:

Answer to James Seng's comment:

>Correct me if I am wrong...from your email, you are suggesting that IDN
>to be encoded in a strings based on its symbols which makes up the
>script. While this is an intriguing thought, unfortunately, I do not
>think we have sufficient work done in that direction.

>Our current works basically resolves using ISO10646 as a basis for
>encoding names. Whatever limitation ISO10646 has, it is improving.

I am suggesting that IDN to be encoded in a strings based on its symbols 
which makes up the script. 

	Although IDN has no need to concern with trademarks at this time, it is
the idn limitation to support only [ISO10646] bothers me.  [ISO10646]
does not support all Chinese characters, since Chinese character set has
more than 100,000 characters already.  There are cases that we can not
find a live person's name on our current computers, don't  mention the
dead ones.  At the speed of computer and network development, when the
applications catch up with us, millions of more data going to be on the
net for accessing.  Are we going to revamp our idn again?  I can suggest
an ACE using a recursive rule to handle any symbols that are not possible
to be simply folded onto ASCII character set.  Such an ACE creats a
virtue character set, which is possible
 to include any characters or icons requested by a user, as long as that
icon has been encoded by an ACE somewhere on the net.  When the IDN can
take more than 63 octets or v6 or v8, the ACE can follow without
troubling the users.  Let alone the idea to send Unicode down to the
wire.  It is not user friendly, it is make no sense for the tradename
servers. 

Liana Ye 



From owner-idn@ops.ietf.org  Thu May 24 07:24:20 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA10827
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 07:24:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152t0k-000CoG-00
	for idn-data@psg.com; Thu, 24 May 2001 04:10:34 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152t0i-000Co9-00
	for idn@ops.ietf.org; Thu, 24 May 2001 04:10:33 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4OB9tf73751;
	Thu, 24 May 2001 07:09:55 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105241109.f4OB9tf73751@nic-naa.net>
To: Keith Moore <moore@cs.utk.edu>
cc: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org,
        brunner@nic-naa.net
Subject: Re: [idn] time to move 
In-Reply-To: Your message of "Thu, 24 May 2001 00:16:33 EDT."
             <200105240416.AAA13928@astro.cs.utk.edu> 
Date: Thu, 24 May 2001 07:09:55 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Keith,

> if you want to wait until everything else  is using utf-8 before deploying
> IDNs that use utf-8, feel free.  I suspect that most of us don't want
> to wait that long.

Of course I want to wait until <arbitrary precondition> before extending
the label space from 0x2d, 0x30-0x39, 0x41-0x5a, 0x61-0x7z to that set
plux (to be minimal and true to my calling) 0x2b. I'm a straw-person, and
its a given that everyone has vastly more clue than I.

Less rhetoric, more engineering. Please. Or we should stop meeting after
midight, list-time.

At present, no user of a dns may use code points other than the HDL list,
because <arbitrary precondition> is controlling until <arbitrary date>.

Getting a fix on <arbitrary precondition> and <arbitrary date> are worth
spending some time on, but aren't in themselves adequate for failing to
extend the existing set of label space octet encodings.

Well, BiDi just landed in the Mozilla tree. I'm willing to keep my own
personal shell at adb (a very old SRI prank), but there's an entire
cohort of users who's internet is post-modern, either because they data
just got "there" or because MicroSquash has eaten all the alternatives
they are capable of using. 

I suppose I could fix something. I hear that NSI has everything a grown
person could want in an IDN, if they were smart enough to let NSI define
need.

Eric



From owner-idn@ops.ietf.org  Thu May 24 07:25:07 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA10840
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 07:25:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152ssU-000CZo-00
	for idn-data@psg.com; Thu, 24 May 2001 04:02:02 -0700
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152ssT-000CZi-00
	for idn@ops.ietf.org; Thu, 24 May 2001 04:02:02 -0700
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10383;
	Thu, 24 May 2001 07:01:44 -0400 (EDT)
Message-Id: <200105241101.HAA10383@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-requirements-07.txt
Date: Thu, 24 May 2001 07:01:43 -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		: Requirements of Internationalized Domain Names
	Author(s)	: Z. Wenzel, J. Seng
	Filename	: draft-ietf-idn-requirements-07.txt
	Pages		: 8
	Date		: 23-May-01
	
This document describes the requirement for encoding international
characters into DNS names and records. This document is guidance for
developing protocols for internationalized domain names.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idn-requirements-07.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-requirements-07.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-requirements-07.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:	<20010523114119.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idn-requirements-07.txt

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

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

--OtherAccess--

--NextPart--





From owner-idn@ops.ietf.org  Thu May 24 08:50:16 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA12171
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 08:50:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152uIp-000EwE-00
	for idn-data@psg.com; Thu, 24 May 2001 05:33:19 -0700
Received: from mail.lysator.liu.se ([130.236.254.3])
	by psg.com with esmtp (Exim 3.16 #1)
	id 152uIo-000Ew8-00
	for idn@ops.ietf.org; Thu, 24 May 2001 05:33:18 -0700
Received: from sandra.lysator.liu.se (sandra.lysator.liu.se [130.236.254.203])
	by mail.lysator.liu.se (Postfix) with ESMTP
	id D0D3F82F4F4; Thu, 24 May 2001 14:33:16 +0200 (MET DST)
Received: from localhost (mag@localhost)
	by sandra.lysator.liu.se (8.9.0/8.8.7) with SMTP id OAA22890;
	Thu, 24 May 2001 14:33:16 +0200 (MET DST)
X-Authentication-Warning: sandra.lysator.liu.se: mag owned process doing -bs
Date: Thu, 24 May 2001 14:33:16 +0200 (MET DST)
From: C C Magnus Gustavsson <mag@lysator.liu.se>
To: "Adam M. Costello" <amc@cs.berkeley.edu>
Cc: idn@ops.ietf.org
Subject: Re: [idn] time to move
In-Reply-To: <20010523203700.F26947@arwen.cs.berkeley.edu>
Message-ID: <Pine.GSO.4.00.10105241432170.22854-100000@sandra.lysator.liu.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Wed, 23 May 2001, Adam M. Costello wrote:

> Finally, note that UTF-8 has issues with encoding efficiency (the
> length of the encoded string).

Perhaps, but I don't think that is an issue for this working group.

We need fixed and unified codings for characters. That is among the
most important issues here, in any IETF work and in computer industry.
We need something which like ASCII is the same everywhere and doesn't
depend on what kind of computer or what protocol you're using.

The major reason for using Unicode/ISO 10646 is to know that 01101001
is always 'i', not only for 'i' but for all other characters as well.
I don't think some of the people here realize what kind of problems
the use of a myriad encodings result in.

But sure, in the case of protocols the problem is a little different.
We can let our computers do the conversions automatically. In theory.
Experience, however, shows that it is too complex for most software to
handle properly. The result is frequent leakage of internal formats as
e g in the case of quoted-printable.

That is why the IETF should specify a single encoding to be used in
all protocols. And - fortunately - IETF already has. BCP 18 (RFC 2277)
clearly specifies that UTF-8 is to be used as the standard character
set in all protocols. It might be argued that UTF-8 was a bad choice,
but this WG is not the place to change it. And until it is changed,
UTF-8 should be at least the long term goal for this WG.

/Magnus


And, btw:

I think "international characters" and "internationalized host names"
are very strange terms to use. What is more international than ASCII?
Wouldn't "local" and "localized" be better?




From owner-idn@ops.ietf.org  Thu May 24 09:39:47 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA13168
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 09:39:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152v6p-000GKh-00
	for idn-data@psg.com; Thu, 24 May 2001 06:24:59 -0700
Received: from [209.187.148.217] (helo=P2)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152v6o-000GKJ-00
	for idn@ops.ietf.org; Thu, 24 May 2001 06:24:58 -0700
Date: Thu, 24 May 2001 09:24:56 -0400
From: John C Klensin <klensin@jck.com>
To: idn@ops.ietf.org
Subject: [idn] Time to reconsider
Message-ID: <2853818850.990696296@P2>
In-Reply-To: <200105241157.f4OBvHf73852@nic-naa.net>
X-Mailer: Mulberry/2.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I started to write the attached as a response to a note in a
side-conversation.  I think it belongs on the list.  Since I
haven't asked the author of the quoted material/ questions, I've
anonymized those remarks (variations on which, actually, could
have been made by several people in the threads of the last few
days although I particularly like this formulation).

Quick summary: I believe that we should not agree to either
Nameprep or the Requirements document as they stand because the
underlying assumptions behind what we are doing have been shown,
by the WG's work, to be fundamentally flawed.  I try to explain
"why" below, followed by a quick summary of what we should be
doing instead.  More on the latter within the next day or two.

(referring to the former (as of draft -06) requirement [30] and
other "localization" ideas)...
> Is scope a requirement? Is scopelessness a requirement?

My personal response would be that this is more evidence that
trying to do these things in the DNS is a mistake.  The issue
isn't that of one coding versus another.  It is that we are
expecting a lookup-and-exact-match system to do the impossible
-- fuzzy matching that doesn't astonish a user whose cultural
and linguistic assumptions cannot be predicted or identified
given the tools at hand.

> There was substantive discussion involving CNNIC, and the
> question of TC and SC equivalence. [...]  at Minneapolis [...]
> I'd prefer to see technical
> consensus.

My personal belief is that you will never get it.  The problem
is that interpretations of "matching" vary locally.  That means
there will be cases of ambiguity -- things that do, or do not,
match depending on context or the user's assumptions.
Simplified and traditional Chinese are either matching issues or
language translation, depending on those assumptions: the
requirement is clear for those who need the matching, but
agreement that it is universally necessary or desirable is
problematic.  

And that may be one of the cases with an answer on which global
consensus can be reached, but the more general problem is
certainly not unique to one language or script.  As we keep
looking, it seems that we have at least a few examples per
script.  Even ASCII (although not the "hostname" subset) has
them if one goes back far enough or starts looking carefully.
E.g., are "tilde" (Ux007e) and "not sign" (Ux00AC) the same
character?   Well, several programming languages and database
systems made them the same (the glyphs were treated as alternate
stylizations of the same character) back in what could be
described as the "unified Roman" days of ISO 646.  For some,
"macron" (Ux00AF)  If, as some registries are proposing (or
actually registering), we can have dingbats in the DNS, there is
certainly no reason to ban these characters.  There are several
single-line optical scanner products on the market that proport
to read URLs and enter them directly into browsers.  Do these
code points match?    How about "vertical line" (Ux007C) and
"broken bar" (Ux00A6)?  That pair and the tilde/not-sign one are
equivalenced in character set translations between ASCII and
another _very_ popular coded character set.   To a person not
trained or socialized in Roman alphabets, the pairs may "look"
more similar than two Han characters, or two characters from
different Han-based language scripts look to an untrained person
such as myself.

But they are separated in Unicode because there are good reasons
to separate them, especially if one is worried about typography.
Should they be matched (treated as equivalent)?  Well,
sometimes: no "yes" or "no" answer is going to satisfy everyone
and, worse, the same answer may be unsatisfactory to the same
person on different occasions.  One needs context --cultural or
use-- and the DNS cannot supply or support that context in an
unambiguous way, at least without kludges which are much more
horrible than any we have contemplated so far.

Consequently, there is no way to get technical agreement without
favoring the social/ political/ cultural preferences of one
group over another.  I believe that the WG has managed to prove
a negative by exhaustion, and that we need to stop before we
wreck the DNS only to get an unsatisfactory and incomplete
result.

So, my formulation to respond to Marc's "time to move" question
is that we should:

(i) Carefully review the requirements document again.  The
issues over [30] (which I saw as a "localization" -- every zone
can have its own matching rules-- hook) may exist in other
places.  The resulting document should either focus on solutions
that are not limited to changes to the DNS or what is permitted
in it or how its names are interpreted (I consider IDNA, etc.,
to be cases of such changes, disclaimers that the interpretation
is elsewhere notwithstanding), or should clearly identify where
important requirements cannot be met in the DNS alone.

(ii) We should make another sweep over "nameprep", to change the
matching and mapping lists from "yes" or "no" to "yes"/ "no"/
and "sometimes" (or an equivalent three-way choice).  The
latter, ambiguous, category, should include cases like those
above as well as the "is 'A' in Roman, Cyrillic, or Greek?"
issue we have kicked around before, and all of their relatives
and parallels in other scripts.

(iii) And then we should concentrate IETF's efforts on searching
and matching systems that permit context and user choice over
the ambiguous cases, rather than hoping that "sneak this into
the DNS by clever coding and hope the problems will somehow
solve themselves elsewhere --perhaps by the world adapting its
natural languages and cultures to our conventions" will be
adequate.  It won't.

     john




From owner-idn@ops.ietf.org  Thu May 24 10:06:55 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA13819
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 10:06:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152vWp-000H0N-00
	for idn-data@psg.com; Thu, 24 May 2001 06:51:51 -0700
Received: from [24.0.95.81] (helo=femail1.sdc1.sfba.home.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152vWo-000Gxz-00
	for idn@ops.ietf.org; Thu, 24 May 2001 06:51:50 -0700
Received: from c1340594a ([65.11.104.12]) by femail1.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20010524135041.GVVW12911.femail1.sdc1.sfba.home.com@c1340594a>;
          Thu, 24 May 2001 06:50:41 -0700
Message-ID: <004201c0e458$9fdfc070$0c680b41@c1340594a>
Reply-To: "Mark Davis" <mark@macchiato.com>
From: "Mark Davis" <markdavis34@home.com>
To: <idn@ops.ietf.org>, <liana.ydisg@juno.com>
Cc: <liana.ydisg@juno.com>
References: <20010523.231637.-774175.2.liana.ydisg@juno.com>
Subject: Re: [idn] Working direction of IDN
Date: Thu, 24 May 2001 06:51:25 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

There is a lot of misinformation floating around about the support of
Chinese, Japanese and Korean characters. ISO 10646 / Unicode supports over
70,000 Chinese characters right now, and work is underway to encode further
sets. It has the same repertoire as the Chinese GB18030 and GB 13000.

This work is being done by the IRG, which includes representatives of the
governments of China, Hong Kong, Singapore, Japan, South Korea, North Korea,
Taiwan and Vietnam, plus a representative from the Unicode consortium (cf
http://www.info.gov.hk/digital21/eng/structure/intro_irg.html).

This group is very careful cataloging, reviewing, and assessing Chinese
characters for inclusion into the standard. The only real limitation on the
number of Chinese characters in the standard is the ability of this group to
process them, because the characters are increasingly obscure (no person
knows more than a fraction of the set already encoded).

Mark

----- Original Message -----
From: <liana.ydisg@juno.com>
To: <idn@ops.ietf.org>
Cc: <liana.ydisg@juno.com>
Sent: Wednesday, May 23, 2001 23:16
Subject: [idn] Working direction of IDN


> All:
>
> Answer to James Seng's comment:
>
> >Correct me if I am wrong...from your email, you are suggesting that IDN
> >to be encoded in a strings based on its symbols which makes up the
> >script. While this is an intriguing thought, unfortunately, I do not
> >think we have sufficient work done in that direction.
>
> >Our current works basically resolves using ISO10646 as a basis for
> >encoding names. Whatever limitation ISO10646 has, it is improving.
>
> I am suggesting that IDN to be encoded in a strings based on its symbols
> which makes up the script.
>
> Although IDN has no need to concern with trademarks at this time, it is
> the idn limitation to support only [ISO10646] bothers me.  [ISO10646]
> does not support all Chinese characters, since Chinese character set has
> more than 100,000 characters already.  There are cases that we can not
> find a live person's name on our current computers, don't  mention the
> dead ones.  At the speed of computer and network development, when the
> applications catch up with us, millions of more data going to be on the
> net for accessing.  Are we going to revamp our idn again?  I can suggest
> an ACE using a recursive rule to handle any symbols that are not possible
> to be simply folded onto ASCII character set.  Such an ACE creats a
> virtue character set, which is possible
>  to include any characters or icons requested by a user, as long as that
> icon has been encoded by an ACE somewhere on the net.  When the IDN can
> take more than 63 octets or v6 or v8, the ACE can follow without
> troubling the users.  Let alone the idea to send Unicode down to the
> wire.  It is not user friendly, it is make no sense for the tradename
> servers.
>
> Liana Ye
>




From owner-idn@ops.ietf.org  Thu May 24 10:25:27 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA14186
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 10:25:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152vkm-000HRQ-00
	for idn-data@psg.com; Thu, 24 May 2001 07:06:16 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152vkl-000HRJ-00
	for idn@ops.ietf.org; Thu, 24 May 2001 07:06:15 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4OE5Lf74257;
	Thu, 24 May 2001 10:05:21 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105241405.f4OE5Lf74257@nic-naa.net>
To: "James Seng/Personal" <James@Seng.cc>
cc: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>,
        "J. William Semich" <bill@mail.nic.nu>, idn@ops.ietf.org,
        brunner@nic-naa.net
Subject: Re: [idn] requirements-07 
In-Reply-To: Your message of "Thu, 24 May 2001 14:10:40 +0800."
             <062b01c0e418$42692930$dd00a8c0@jamessonyvaio> 
Date: Thu, 24 May 2001 10:05:21 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I expected that failing to be convinced of James' views on the authentication
mechanism in dns registry provisioning (provreg) would have to be paid for
somewhere. The payback of not reading my draft and not breaking my rice bowl
commentaries on the ietf-provreg list clearly weren't sufficient.

I'll go stand next to Bill Simpson in the disliked-by-the-chair corner for the
obligatory 60 seconds and then get back to the work of contributing towards
interoperable engineering.

Cheers,
Eric



From owner-idn@ops.ietf.org  Thu May 24 14:01:00 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18190
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 14:00:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 152yyh-000NAF-00
	for idn-data@psg.com; Thu, 24 May 2001 10:32:51 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 152yyg-000NA5-00
	for idn@ops.ietf.org; Thu, 24 May 2001 10:32:50 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4OHTkf74933;
	Thu, 24 May 2001 13:29:46 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105241729.f4OHTkf74933@nic-naa.net>
To: John C Klensin <klensin@jck.com>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] Time to reconsider 
In-Reply-To: Your message of "Thu, 24 May 2001 09:24:56 EDT."
             <2853818850.990696296@P2> 
Date: Thu, 24 May 2001 13:29:45 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Since I
> haven't asked the author of the quoted material/ questions, I've
> anonymized those remarks

John, I suggested that we take the scope issue back to the main list.
Quote me till the cows come home. We also now know the origin of [30].

Semantic scope isn't encoding selection, encoding is just one possible
policy that could have scoped semantics, or could be scopeless. In the
context I mentioned in our side-bar, now back in the main list, rules
for equivalency over the same encoding (utf8) were the subject of
discussion. In the origin-of-[30] note, rules for equivalency over the
same encoding (ASCII) were the subject of discussion.

> Quick summary: I believe that we should not agree to either
> Nameprep or the Requirements document as they stand because the
> underlying assumptions behind what we are doing have been shown,
> by the WG's work, to be fundamentally flawed. 

This far I agree. Where I expect we disagree is what the underlying
assumption(s) are which appear (to each of us) to be fundamentally
flawed, which I'll restate as affirmative goals.

	JK:	extend "meaning" (languages, scripts, and fuzzy matching)
	EB-W:	extend "labels" (0x2d, 0x30-0x39, 0x41-0x5a, 0x61-0x7z)

Is consensus possible?

In practical terms, "apparently not":

	VGS is going live with its RACE, the mechanism for non-ASCII
	in the .com namespace.

	CN went live with UTF8, the mechanism for ASCII and non-ASCII
	in the .cn namespace.

There are a lot of other choices to pick from, but of these two, I'm
going to deploy UTF8, subject to possible ICANN and possible Registry
Trade Association regulatory oversight and technical coordination.

In working group terms, the answer isn't much better.

There are 6,182,148 (Walid), and 5,410,306 (Ydisg), encumberments, and we
have simply not had the bandwidth to conclude independently as VGS did that
neither applies to IDNA, a lack of knowledge I happen to know is shared by
at least two other namespace vendors.

We've a nameprep/idna poll (my reply was "no" and "rfc2044") outstanding.

All this, and about 20 drafts in various stages of aging are before this
working group, along with the prior organizational art, rfc2044 and rfc2130,
and rfc1034/1035.

It will take a wiser head than mine to sort out the WG roadmap to rough
consensus in finite time, and it appears that time is very finite indeed.

Eric



From owner-idn@ops.ietf.org  Thu May 24 15:42:13 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA19814
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 15:42:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1530hr-0000Y8-00
	for idn-data@psg.com; Thu, 24 May 2001 12:23:35 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 1530hq-0000Xw-00
	for idn@ops.ietf.org; Thu, 24 May 2001 12:23:34 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA18957;
        Thu, 24 May 2001 15:21:16 -0400 (EDT)
Message-Id: <200105241921.PAA18957@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: John C Klensin <klensin@jck.com>
cc: idn@ops.ietf.org
Subject: Re: [idn] Time to reconsider 
In-reply-to: Your message of "Thu, 24 May 2001 09:24:56 EDT."
             <2853818850.990696296@P2> 
Date: Thu, 24 May 2001 15:21:16 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

John,

> My personal response would be that this is more evidence that
> trying to do these things in the DNS is a mistake.  The issue
> isn't that of one coding versus another.  It is that we are
> expecting a lookup-and-exact-match system to do the impossible
> -- fuzzy matching that doesn't astonish a user whose cultural
> and linguistic assumptions cannot be predicted or identified
> given the tools at hand.

Here's why I'm skeptical about this argument.  Most of the 
computer operating systems I'm aware of use more-or-less
the same matching algorithm for filenames (including filenames
typed by humans) as that used by DNS - exact comparison modulo
case folding.  Yes, point-and-click interfaces exist, but they 
don't scale.

Now it might turn out that that kind of filename matching is 
completely impractical for some language because they have
too many different ways of spelling words.  But I suspect 
that, to the extent possible, folks who speak languages
that have multiple ways of spelling words can develop
conventions for spelling domain names in that language - just 
as we have found some restrictions on English-language domain 
names (e.g. the LDH rule) useful in minimizing the differences 
in how domain names can be spelled.

I do think we should realize the limitations that are inherent
in the approach of extending DNS to non-ASCII characters.  
However, I don't think we should stop developing an IDN solution
simply because it's not the perfect solution to all name lookup
problems.

The other bit is that it's very hard to build a federated name
space once you get away from canonicalization followed by exact 
matching.  Which means that in such a world you either have a 
single point of control for ALL names (not just the TLDs), or 
you don't get consistent results from one lookup service to 
another.  Neither one of these sounds particularly desirable as
a replacement for domain name lookup.  The struggle for control
of the DNS root and TLDs has been too painful already, and the
major contributors to that war have shown no sign of willingness
to exercise restraint or minimize the collateral damage.
 
The last thing we need is to have a fight over control of all names.
Because people will demand fuzzy-matching all the way to the root,
with all of the chaos and inefficiency that this implies.

So I think that IDN is still needed, even though we may also 
recognize that a fuzzy-matching lookup service might also be
needed.

Keith



From owner-idn@ops.ietf.org  Thu May 24 21:02:02 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA23429
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 21:02:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1535UQ-0005Jk-00
	for idn-data@psg.com; Thu, 24 May 2001 17:30:02 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.16 #1)
	id 1535QX-000568-00
	for idn@ops.ietf.org; Thu, 24 May 2001 17:27:02 -0700
Received: from yamada (g053083.ppp.asahi-net.or.jp [211.132.53.83])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id JAA16791;
	Fri, 25 May 2001 09:15:26 +0900 (JST)
Message-Id: <4.2.0.58.J.20010524222818.02f9edf0@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Thu, 24 May 2001 22:36:05 +0900
To: Keith Moore <moore@cs.utk.edu>,
        Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] time to move 
Cc: Keith Moore <moore@cs.utk.edu>, "Adam M. Costello" <amc@cs.berkeley.edu>,
        idn@ops.ietf.org
In-Reply-To: <200105240416.AAA13928@astro.cs.utk.edu>
References: <Your message of "Wed, 23 May 2001 23:58:42 EDT." <200105240358.f4O3wgf72532@nic-naa.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 00:16 01/05/24 -0400, Keith Moore wrote:
> > I don't have a whole lot of 3Mb/sec Type I Ethernet lying about these
> > days (see above).
>
>perhaps not.  but the folks I know where were using IP over 3Mb/sec
>Ethernet are still using IP.  IPv4 is starting to look obsolete due
>to a shortage of addresses, but I don't know anyone who thinks it's
>going to be discarded anytime soon.

Yes. But if that example applies to anything, it applies with
IP4 <=> ACE, IP6 <=> UTF-8, i.e. once we have ACE, we will have
big problems to get to UTF-8.


> > Isn't the line of march of uniqueness and consistency and so forth 
> predicated
> > upon the inexistence of ... "island(s)", and the non-deployment of utf8?
>
>it's predicated on the non-deployment of utf-8 *in Internet applications*
>*at the time the IDN solution is deployed*.

utf-8 is well supported by the recent generations of browsers.
The situation is similar for e-mail, with some exceptions.
Speaking about 'non-deployment of utf-8 in Internet applications'
is just spreading bad rumors. If a bit more people had had the
guts to go for utf-8 a few months ago, we would already have quite
some things running, end-to-end.


>it is currently the case
>that few Internet applications support utf-8, and this isn't likely to
>change in the near future.

Can you please help me understand your facts by telling me how you
count?


>if you want to wait until everything else  is using utf-8 before deploying
>IDNs that use utf-8, feel free.  I suspect that most of us don't want
>to wait that long.  I also suspect that the fastest way to get to having
>applications use utf-8 natively (if that's even worth the trouble)
>is to use ACE IDNs in the near term.

I think this is very seriously wrong. For a very large number of applications,
the only thing you have to do to work with utf-8 is make sure they are
8-bit compatible. In many cases, that's already the case. Even for something
as old as sendmail, an easy hack to achieve this has been described on this 
list.


Regards,   Martin.



From owner-idn@ops.ietf.org  Thu May 24 22:02:34 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA24787
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 22:02:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1536f1-0007OA-00
	for idn-data@psg.com; Thu, 24 May 2001 18:45:03 -0700
Received: from mail.fm-net.ne.jp ([211.15.66.133])
	by psg.com with esmtp (Exim 3.16 #1)
	id 1536ez-0007Nh-00
	for idn@ops.ietf.org; Thu, 24 May 2001 18:45: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 KAA27304
	for <idn@ops.ietf.org>; Fri, 25 May 2001 10:44:57 +0900
Message-ID: <003501c0e4bc$359adce0$a3420fd3@bruce>
From: "Bruce Thomson" <bthomson@fm-net.ne.jp>
To: <idn@ops.ietf.org>
References: <Your message of "Wed, 23 May 2001 23:58:42 EDT." <200105240358.f4O3wgf72532@nic-naa.net> <4.2.0.58.J.20010524222818.02f9edf0@sh.w3.mag.keio.ac.jp>
Subject: Re: [idn] time to move 
Date: Fri, 25 May 2001 10:44:16 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> utf-8 is well supported by the recent generations of browsers.
> The situation is similar for e-mail, with some exceptions.
> Speaking about 'non-deployment of utf-8 in Internet applications'
> is just spreading bad rumors. If a bit more people had had the
> guts to go for utf-8 a few months ago, we would already have quite
> some things running, end-to-end.
> 
Can somebody point me to a list of what e-mail clients are currently
working with UTF-8? I had been working under the assumption that
only browsers were working.

If these two apps are really there, I am surprised that we aren't just
going for UTF-8. History will likely record that it was this WG that
was the biggest barrier to deployment. ACE has outlived its usefulness
already.

Yes, I know that some things will break. Many multilingual apps are
broken in any case, but are being gradually fixed. Each new OS
or new piece of hardware breaks lots of things, but the world goes on.





From owner-idn@ops.ietf.org  Thu May 24 22:23:52 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA24919
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 22:23:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1536uq-0007r7-00
	for idn-data@psg.com; Thu, 24 May 2001 19:01:24 -0700
Received: from sh.w3.mag.keio.ac.jp ([133.27.194.41])
	by psg.com with esmtp (Exim 3.16 #1)
	id 1536lI-0007Ys-00
	for idn@ops.ietf.org; Thu, 24 May 2001 18:55:23 -0700
Received: from yamada (g053083.ppp.asahi-net.or.jp [211.132.53.83])
	by sh.w3.mag.keio.ac.jp (8.9.3/3.7W) with ESMTP id KAA16971;
	Fri, 25 May 2001 10:51:01 +0900 (JST)
Message-Id: <4.2.0.58.J.20010524223716.02fe5100@sh.w3.mag.keio.ac.jp>
X-Sender: duerst@sh.w3.mag.keio.ac.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58.J 
Date: Fri, 25 May 2001 10:50:22 +0900
To: Keith Moore <moore@cs.utk.edu>, idn@ops.ietf.org
From: Martin Duerst <duerst@w3.org>
Subject: Re: [idn] Why we can go directly to UTF-8
In-Reply-To: <200105240409.AAA13879@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 00:09 01/05/24 -0400, Keith Moore wrote:
>It's really quite simple.
>
>If we use UTF-8 names, each component in a signal path that handles
>an IDN has to be upgraded before the application will work with IDNs.

Each component *may* have to be upgraded. Some may not need an
upgrade. For many, 8-bit transparency will do just fine.


>For email, this means every UA, MTA, message store, mail filter,
>mailing list, etc that uses the addresses in the header or
>envelope of a message.  For the web, this means every web browser,
>proxy, cache, and origin server that makes use of domain names
>in the request or response (header or payload).

'every' is too general. It's just those in the relevant paths.
For the average web case, it's just the browser and the server.
Proxies can be changed if necessary.


>For both cases,
>it means that every DNS query library, resolver, cache, and server
>involved in the lookups supports UTF-8 also (unless you believe
>that the existing ones will already support UTF-8 without protocol
>extensions, which is far from a given).  There's little incentive
>to upgrade because so many other components need to be upgraded
>before you can get reliable operation.

I very much doubt your last sentence. Companies that are interested
in being found with an idn will obviously upgrade their DNS and
web servers (if necessary). Users interested in using idns will
upgrade their browsers (if necessary). If people will be using
idns as frequently as we all think, the missing bits will be
filled in quite quickly.



>If we use ASCII compatible names, each component in a signal path
>that handles a domain name can upgrade independently, and things
>will keep working - they just won't display the name as nicely if
>they're not updated.    And only the components that interface with
>users need to be upgraded before the users see a benefit.

This is an end-to-end problem, and the end is the user, not some
system. A system that gives (people like you) the impression that
it works, but displays ASCII garbage, is a total failure.

*Nobody* who has a choice between let's say 'toshiba.co.jp' and
some garbage like 'xyz--ttnhpur83g4prhoaunh3.co.jp' (rather
than something like TOUSIBA.co.jp, imagine upper-case as kanji)
will ever want to use the later. It's completely useless for
humans.



>It's easier to get real IDN support into the various components
>using ASCII compatible names because fewer components need to be
>upgraded.  And the incentives for adoption are greater with ASCII
>names because the benefit of upgrading will be seen sooner.

No, what will happen is that the problems will be seen sooner,
and people will complain. Using UTF-8 will help to make sure
that clients are upgraded before idns are used, and that's
crucial for making sure that things work reasonably well
(for the humans who are the purpose of this exercise, not
only for some machines) from the start.


>Users won't care about whether the applications protocols represent
>IDNs in ACE or UTF-8.  But they will care about whether their
>applications support IDNs.  ACE lets them do so far more quickly.

Users care very much whether they see things in their script or they
see some ACE garbage. A half-way solution is not a solution, and ACE
will expose a half-way solution for a long time. Very ugly.

Of course, most probably to you ASCII garbage looks better than
Arabic, Chinese, Japanese, Korean, Hebrew, or other scripts.
Given that you have spent decades reading English, and maybe
only seconds or minutes looking at the other scripts, this is
nothing to be blamed for, and it's something that is in many
ways very difficult to become aware off, to get atop of it
and be able to judge from an independent viewpoint. I know
these kinds of things very well, because still after learning
and reading Japanese for close to 20 years, if I see an
announcement in both Japanese and English, my eyes move
to the English first even if it's printed very small,
and the Japanese is much bigger. Reading is an activity
that we spend more time on learning and doing than anything
else, and so it's no wonder that it happens all automatically
without us being aware of what happens.

So again, I would like to remind you: If users see ACE garbage,
this is a protocol failure in an end-to-end system, not something
we can gloss over lightly.


Regards,   Martin.




From owner-idn@ops.ietf.org  Thu May 24 23:34:14 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA26940
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 23:34:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 15386D-0009uL-00
	for idn-data@psg.com; Thu, 24 May 2001 20:17:13 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 15386C-0009uF-00
	for idn@ops.ietf.org; Thu, 24 May 2001 20:17:12 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id XAA23311;
        Thu, 24 May 2001 23:17:05 -0400 (EDT)
Message-Id: <200105250317.XAA23311@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Martin Duerst <duerst@w3.org>
cc: Keith Moore <moore@cs.utk.edu>,
        Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] time to move 
In-reply-to: Your message of "Thu, 24 May 2001 22:36:05 +0900."
             <4.2.0.58.J.20010524222818.02f9edf0@sh.w3.mag.keio.ac.jp> 
Date: Thu, 24 May 2001 23:17:04 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> At 00:16 01/05/24 -0400, Keith Moore wrote:
> > > I don't have a whole lot of 3Mb/sec Type I Ethernet lying about these
> > > days (see above).
> >
> >perhaps not.  but the folks I know where were using IP over 3Mb/sec
> >Ethernet are still using IP.  IPv4 is starting to look obsolete due
> >to a shortage of addresses, but I don't know anyone who thinks it's
> >going to be discarded anytime soon.
> 
> Yes. But if that example applies to anything, it applies with
> IP4 <=> ACE, IP6 <=> UTF-8, i.e. once we have ACE, we will have
> big problems to get to UTF-8.

Actually, we will have big problems to "get to" UTF-8 whether we
go to ACE first or not.    I'd argue that it's easier to "get to"
UTF-8 by going to ACE first because going to ACE allows folks to
get benefit without having to upgrade every single component
in the signal path. 

Of course, the goal of IDN isn't to "get to" utf-8 at all; it is 
to allow domain names to use characters outside of the ASCII repertoire.
If you want to "get to" utf-8 you're trying to solve a different
problem. If you insist that that problem be piggybacked on the
IDN problem then you're trying to make the IDN problem more difficult
than it needs to be.
 
> > > Isn't the line of march of uniqueness and consistency and so forth 
> > predicated
> > > upon the inexistence of ... "island(s)", and the non-deployment of utf8?
> >
> >it's predicated on the non-deployment of utf-8 *in Internet applications*
> >*at the time the IDN solution is deployed*.
> 
> utf-8 is well supported by the recent generations of browsers.

Browsers are but a small subset of internet applications.

> The situation is similar for e-mail, with some exceptions.

Email support for utf-8 is essentially nonexistent.

> Speaking about 'non-deployment of utf-8 in Internet applications'
> is just spreading bad rumors. 

You might not like it, but it's the truth.

> If a bit more people had had the
> guts to go for utf-8 a few months ago, we would already have quite
> some things running, end-to-end.

we would have some prototype code for each of the components.
that doesn't mean it would be deployable in the real world.

no application upgrade in the history of the internet has had 
signifcant deployment in a few months' time.  not even close.
even the MIME upgrade, which was far less disruptive than
what you are proposing, took many years.

we have prototype code for ACE solutions also.  ability to develop
a prototype isn't the issue here.

> >it is currently the case
> >that few Internet applications support utf-8, and this isn't likely to
> >change in the near future.
> 
> Can you please help me understand your facts by telling me how you
> count?

I examine every internet application to which I have easy access - which is
to say, several dozen.  I see how many of them would work with UTF-8 domain
names.  The answer is zero.  Even the applications that accept UTF-8 input
don't do nameprep, neither do they  know better than to pass UTF-8 names 
to other applications that don't deal with UTF-8.  

the "just use UTF-8 in existing applications" approach has always been
a non-starter.
 
> >if you want to wait until everything else  is using utf-8 before deploying
> >IDNs that use utf-8, feel free.  I suspect that most of us don't want
> >to wait that long.  I also suspect that the fastest way to get to having
> >applications use utf-8 natively (if that's even worth the trouble)
> >is to use ACE IDNs in the near term.
> 
> I think this is very seriously wrong. For a very large number of applications,
> the only thing you have to do to work with utf-8 is make sure they are
> 8-bit compatible. In many cases, that's already the case. Even for something
> as old as sendmail, an easy hack to achieve this has been described on this 
> list.

this analysis is simply incorrect, as numerous people have already pointed out.

this discussion can serve no further purpose.  I can't make you believe 
something that you don't want to believe, and I won't waste my energy trying.
but there is no basis for agreement between us, because your assessment of 
the situation is completely incompatible with mine.

Keith



From owner-idn@ops.ietf.org  Thu May 24 23:52:40 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA27134
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 23:52:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1538QV-000AUF-00
	for idn-data@psg.com; Thu, 24 May 2001 20:38:11 -0700
Received: from arachnid.ehsco.com ([209.31.7.46] helo=Arachnid.NTRG.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 1538QU-000AU9-00
	for idn@ops.ietf.org; Thu, 24 May 2001 20:38:10 -0700
Received: from ehsco.com (FERRET.NTRG.com [192.168.10.10])
          by Arachnid.NTRG.com (Netscape Messaging Server 3.62)  with ESMTP
          id 403; Thu, 24 May 2001 20:38:08 -0700
Message-ID: <3B0DD39F.515161DD@ehsco.com>
Date: Thu, 24 May 2001 20:38:07 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Martin Duerst <duerst@w3.org>
CC: Keith Moore <moore@cs.utk.edu>, idn@ops.ietf.org
Subject: Re: [idn] Why we can go directly to UTF-8
References: <4.2.0.58.J.20010524223716.02fe5100@sh.w3.mag.keio.ac.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Martin Duerst wrote:

> 'every' is too general. It's just those in the relevant paths.

I agree that "every" is too general, but so is "just those in the relevant
paths".

The number of systems which will break with UTF-8 is greater than the
number of systems which break when they encounter an underscore in the
domain name. Moreover, the "path" includes protocols such as BOOTP/DHCP
clients and servers, X clients and servers, and a bunch of other stuff.

Moreover, some of these systems are firmare-based boxes that are no longer
maintained. Think of all the terminal servers and printer servers that
were acquired, orphaned or died.

If we were to go to UTF-8, we would pretty much have to cleanly break with
history in order to ensure interoperability.

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



From owner-idn@ops.ietf.org  Thu May 24 23:57:38 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA27174
	for <idn-archive@lists.ietf.org>; Thu, 24 May 2001 23:57:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1538St-000AYr-00
	for idn-data@psg.com; Thu, 24 May 2001 20:40:39 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 1538Ss-000AYl-00
	for idn@ops.ietf.org; Thu, 24 May 2001 20:40:38 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4P3e3f77144;
	Thu, 24 May 2001 23:40:03 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105250340.f4P3e3f77144@nic-naa.net>
To: Keith Moore <moore@cs.utk.edu>
cc: Martin Duerst <duerst@w3.org>,
        Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org,
        brunner@nic-naa.net
Subject: Re: [idn] time to move 
In-Reply-To: Your message of "Thu, 24 May 2001 23:17:04 EDT."
             <200105250317.XAA23311@astro.cs.utk.edu> 
Date: Thu, 24 May 2001 23:40:03 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Keith,

> If you want to "get to" utf-8 you're trying to solve a different
> problem.

Do you really think that Martin is proposing a different problem?

> If you insist that that problem be piggybacked on the
> IDN problem then you're trying to make the IDN problem more difficult
> than it needs to be.

Do you really think that John's proposal fits this test poorer than the
proposal either you've ascribed to Martin, or Martin has actually made?

> this discussion can serve no further purpose.

So how about those NATs?

Eric



From owner-idn@ops.ietf.org  Fri May 25 00:05:29 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA27213
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 00:05:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1538eZ-000Axj-00
	for idn-data@psg.com; Thu, 24 May 2001 20:52:43 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 1538eY-000Axd-00
	for idn@ops.ietf.org; Thu, 24 May 2001 20:52:42 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id XAA23715;
        Thu, 24 May 2001 23:52:34 -0400 (EDT)
Message-Id: <200105250352.XAA23715@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Martin Duerst <duerst@w3.org>
cc: Keith Moore <moore@cs.utk.edu>, idn@ops.ietf.org
Subject: Re: [idn] Why we can go directly to UTF-8 
In-reply-to: Your message of "Fri, 25 May 2001 10:50:22 +0900."
             <4.2.0.58.J.20010524223716.02fe5100@sh.w3.mag.keio.ac.jp> 
Date: Thu, 24 May 2001 23:52:34 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> At 00:09 01/05/24 -0400, Keith Moore wrote:
> >It's really quite simple.
> >
> >If we use UTF-8 names, each component in a signal path that handles
> >an IDN has to be upgraded before the application will work with IDNs.
> 
> Each component *may* have to be upgraded. Some may not need an
> upgrade. For many, 8-bit transparency will do just fine.

the reason I say that each component has to be upgraded is that for
every component at least one of the following is likely to be true:

- it needs to be upgraded to keep from breaking the next component 
  by sending it utf-8 when it's not ready to deal with it

- it needs to be upgraded to do nameprep before making a query
  so that the existing DNS servers will work in the face of various
  representations of the IDN

- it needs to be upgraded to be able to correctly compare utf-8
  names in the protocol  with names in a configuration file

- it needs to be upgraded to treat UTF-8 as UTF-8 and not as some
  other locale-specific character set.

> >For email, this means every UA, MTA, message store, mail filter,
> >mailing list, etc that uses the addresses in the header or
> >envelope of a message.  For the web, this means every web browser,
> >proxy, cache, and origin server that makes use of domain names
> >in the request or response (header or payload).
> 
> 'every' is too general. It's just those in the relevant paths.

that's why I said "every component in the signal path".
of course, an IDN solution that works only for a few signal
paths isn't terribly useful.

> For the average web case, it's just the browser and the server.
> Proxies can be changed if necessary.

the browser and every server that the user wants to contact which
uses IDNs, and possibly the web proxies. and the dns servers and 
their proxies also.

> >For both cases,
> >it means that every DNS query library, resolver, cache, and server
> >involved in the lookups supports UTF-8 also (unless you believe
> >that the existing ones will already support UTF-8 without protocol
> >extensions, which is far from a given).  There's little incentive
> >to upgrade because so many other components need to be upgraded
> >before you can get reliable operation.
> 
> I very much doubt your last sentence. Companies that are interested
> in being found with an idn will obviously upgrade their DNS and
> web servers (if necessary). Users interested in using idns will
> upgrade their browsers (if necessary). 

or the user will upgrade his browser and not see any improvement,
because few companies support it, and because his service provider
or LAN has a proxy that prevents it from working.  the service 
might even be worse than before because the user will see IDNs
in print and other media and try to type them in, and they will fail
because one compoent or another hasn't been upgraded. and the user 
will say "why bother"?  

and the  web is easier to ugprade than most applications.

the user will upgrade his email client and try to use IDNs in his
address and find that lots of folks cannot reply to them, and that
sometimes his mail doesn't get delivered or gets damaged in transit.
and his recipients postmasters will rigthly blame the sender of mail 
containing IDNs because that mail violates the protocol specifications. 
and once again the user will say "why bother?"  


> If people will be using
> idns as frequently as we all think, the missing bits will be
> filled in quite quickly.

OTOH, if people find that IDNs don't work reliably, and if they cause 
things to break, IDNs will get a bad reputation and users will
learn to avoid them.

> >If we use ASCII compatible names, each component in a signal path
> >that handles a domain name can upgrade independently, and things
> >will keep working - they just won't display the name as nicely if
> >they're not updated.    And only the components that interface with
> >users need to be upgraded before the users see a benefit.
> 
> This is an end-to-end problem, and the end is the user, not some
> system. A system that gives (people like you) the impression that
> it works, but displays ASCII garbage, is a total failure.

if you believe that then there is no possible successful solution.

an IDN will display as garbage on a system that doesn't support IDNs.
it doesn't matter whether it's in ACE or UTF-8, it still looks like 
garbage.

but ACE garbage doesn't mess up my display formatting; UTF-8 garbage
will.  ACE garbage doesn't cause parse errors in existing software;
UTF-8 garbage will.  ACE garbage can be looked up in DNS even if
the software can't display it; UTF-8 garbage is less likely to work.

> *Nobody* who has a choice between let's say 'toshiba.co.jp' and
> some garbage like 'xyz--ttnhpur83g4prhoaunh3.co.jp' (rather
> than something like TOUSIBA.co.jp, imagine upper-case as kanji)
> will ever want to use the later. It's completely useless for
> humans.

probably true.  I suspect that at first people will use IDNs 
sparingly at first, regardless of what representation is chosen. 
 
> >It's easier to get real IDN support into the various components
> >using ASCII compatible names because fewer components need to be
> >upgraded.  And the incentives for adoption are greater with ASCII
> >names because the benefit of upgrading will be seen sooner.
> 
> No, what will happen is that the problems will be seen sooner,
> and people will complain. 

perhaps.  but the logical extension of this argument is that we
should avoid deploying IDNs as long as possible since that way
we can put off seeing the problems for as long as possible.

> Using UTF-8 will help to make sure
> that clients are upgraded before idns are used

how do you figure that?  the clients have to be upgraded in either
case before the user sees a benefit.  and there's no incentive
to upgrade the clients to support IDNs before they can be used.
I suppose the vendors might just update their clients to support
IDNs in the next release cycle,  and eventually most computers
will be running a relase that supports IDNs.  But that could
take a decade or more.

meanwhile, we don't want use of IDNs to cause things to break.
nor do we want to get a bunch of software widely deployed
after many years' time and only then realise that it has
serious bugs or incompatibilities.  (some vendors might try to
do this, believing it would give them a competitive advantage)

> >Users won't care about whether the applications protocols represent
> >IDNs in ACE or UTF-8.  But they will care about whether their
> >applications support IDNs.  ACE lets them do so far more quickly.
> 
> Users care very much whether they see things in their script or they
> see some ACE garbage. A half-way solution is not a solution, and ACE
> will expose a half-way solution for a long time. Very ugly.

so will UTF-8, and it's also very ugly.  

humans will see the ugliness either way.  you are correct that
IDNs are being done for the benefit of humans. but the difference 
between the ACE approach and the UTF-8 approach is that the ACE 
approach allows existing software to continue to work reliably
(even if it looks ugly), while the UTF-8 approach casues existing 
software to fail randomly (while also being ugly).

> Of course, most probably to you ASCII garbage looks better than
> Arabic, Chinese, Japanese, Korean, Hebrew, or other scripts.

it probably does.  but for lots of people, the UTF-8 
version won't display in Arabic, Chinese, Japanese, etc. either -
it will display as unprintable garbage rather than the ACE
version which will display as printable garbage.

> So again, I would like to remind you: If users see ACE garbage,
> this is a protocol failure in an end-to-end system, not something
> we can gloss over lightly.

fine, I'll accept that definition for the purpose of argument.
but that means that if users see UTF-8 as garbage, that's an even 
worse protocol failure - since the UTF-8 is less likely than ASCII
to be displayable at all.  (which follows because the ASCII 
characters used in ACE are a strict subset of UTF-8)

you have now defined terms in such a way that success is impossible.

you've also defined success criteria in such a way that having
the names look right is more important than having them work 
reliably when used.  which seems pretty strange to me.

Keith



From owner-idn@ops.ietf.org  Fri May 25 00:18:35 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA27304
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 00:18:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1538m8-000BDY-00
	for idn-data@psg.com; Thu, 24 May 2001 21:00:32 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 1538m7-000BDP-00
	for idn@ops.ietf.org; Thu, 24 May 2001 21:00: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 AAA23905;
        Fri, 25 May 2001 00:00:26 -0400 (EDT)
Message-Id: <200105250400.AAA23905@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
cc: Keith Moore <moore@cs.utk.edu>, Martin Duerst <duerst@w3.org>,
        "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] time to move 
In-reply-to: Your message of "Thu, 24 May 2001 23:40:03 EDT."
             <200105250340.f4P3e3f77144@nic-naa.net> 
Date: Fri, 25 May 2001 00:00:26 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Keith,
> 
> > If you want to "get to" utf-8 you're trying to solve a different
> > problem.
> 
> Do you really think that Martin is proposing a different problem?

yes.  though he might not realize it.

> > If you insist that that problem be piggybacked on the
> > IDN problem then you're trying to make the IDN problem more difficult
> > than it needs to be.
> 
> Do you really think that John's proposal fits this test poorer than the
> proposal either you've ascribed to Martin, or Martin has actually made?

I have trouble parsing this, so I might have misunderstood it.

But I think that both the problem that John appears to be trying to solve 
and the problem that Martin appears to be trying to solve are more 
difficult than the problem that the IDN WG is trying to solve.  

I think solving the IDN WG's problem is very worthwhile.  

I think solving Martin's problem is also very worthwhile, but I don't want 
to couple that solution to the IDN solution; I think doing so would 
delay the IDN solution too long, and as a result we would end up with a large 
variety of poor and non-interoperable solutions being deployed.

I'm not convinced that John's problem is solvable, but I think it's worth 
investigating.  But I don't want to couple this problem with the IDN problem either.

> > this discussion can serve no further purpose.
> 
> So how about those NATs?

they're the handiwork of the devil, of course.   what else is new?

Keith



From owner-idn@ops.ietf.org  Fri May 25 00:21:59 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA27378
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 00:21:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1538lE-000BBL-00
	for idn-data@psg.com; Thu, 24 May 2001 20:59:36 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 1538lD-000BBC-00
	for idn@ops.ietf.org; Thu, 24 May 2001 20:59:35 -0700
Received: (qmail 4376 invoked by uid 1001); 25 May 2001 03:59:48 -0000
Date: 25 May 2001 03:59:48 -0000
Message-ID: <20010525035948.28153.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] Why we can go directly to UTF-8
References: <4.2.0.58.J.20010524223716.02fe5100@sh.w3.mag.keio.ac.jp> <3B0DD39F.515161DD@ehsco.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:
> The number of systems which will break with UTF-8

Details, please.

My UNIX list at the bottom of http://cr.yp.to/proto/idn.html includes
gethostbyname() (some versions of which have already been fixed), mutt,
pine, and sendmail. Are you claiming that something else needs to be
upgraded? If so, what? We want verifiable facts.

---Dan



From owner-idn@ops.ietf.org  Fri May 25 00:26:05 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA27437
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 00:26:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1538vH-000BV6-00
	for idn-data@psg.com; Thu, 24 May 2001 21:09:59 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 1538vG-000BUz-00
	for idn@ops.ietf.org; Thu, 24 May 2001 21:09:58 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id AAA24172;
        Fri, 25 May 2001 00:09:54 -0400 (EDT)
Message-Id: <200105250409.AAA24172@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Bruce Thomson" <bthomson@fm-net.ne.jp>
cc: idn@ops.ietf.org
Subject: Re: [idn] time to move 
In-reply-to: Your message of "Fri, 25 May 2001 10:44:16 +0900."
             <003501c0e4bc$359adce0$a3420fd3@bruce> 
Date: Fri, 25 May 2001 00:09:54 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > utf-8 is well supported by the recent generations of browsers.
> > The situation is similar for e-mail, with some exceptions.
> > Speaking about 'non-deployment of utf-8 in Internet applications'
> > is just spreading bad rumors. If a bit more people had had the
> > guts to go for utf-8 a few months ago, we would already have quite
> > some things running, end-to-end.
> > 
> Can somebody point me to a list of what e-mail clients are currently
> working with UTF-8? 

if by "working" you mean not only ability to display UTF-8 names but
also the ability to reliably look them up in DNS, send mail to them,
reply to them, and compare them with other UTF-8 names for equivalence,
the list of "working" clients is the empty set.

> I had been working under the assumption that
> only browsers were working.

that's a misimpression.  browsers aren't working either, for any useful
meaning of the word "working".

Keith



From owner-idn@ops.ietf.org  Fri May 25 00:49:41 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA27737
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 00:49:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1539LE-000CDk-00
	for idn-data@psg.com; Thu, 24 May 2001 21:36:48 -0700
Received: from arachnid.ehsco.com ([209.31.7.46] helo=Arachnid.NTRG.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 1539LE-000CDe-00
	for idn@ops.ietf.org; Thu, 24 May 2001 21:36:48 -0700
Received: from ehsco.com (FERRET.NTRG.com [192.168.10.10])
          by Arachnid.NTRG.com (Netscape Messaging Server 3.62)  with ESMTP
          id 568; Thu, 24 May 2001 21:36:46 -0700
Message-ID: <3B0DE15D.752FBECA@ehsco.com>
Date: Thu, 24 May 2001 21:36:45 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "D. J. Bernstein" <djb@cr.yp.to>
CC: idn@ops.ietf.org
Subject: Re: [idn] Why we can go directly to UTF-8
References: <4.2.0.58.J.20010524223716.02fe5100@sh.w3.mag.keio.ac.jp> <3B0DD39F.515161DD@ehsco.com> <20010525035948.28153.qmail@cr.yp.to>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


"D. J. Bernstein" wrote:
> 
> Eric A. Hall writes:
> > The number of systems which will break with UTF-8
> 
> Details, please.
> 
> My UNIX list at the bottom of http://cr.yp.to/proto/idn.html includes
> gethostbyname() (some versions of which have already been fixed), mutt,
> pine, and sendmail. Are you claiming that something else needs to be
> upgraded? If so, what? We want verifiable facts.

If I had kept a list of every device and application that broke when a
customer of mine thought "_" was legal, I'd gladly give it to you.

Those systems enforce LDH, and will reject non-LDH sets.

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



From owner-idn@ops.ietf.org  Fri May 25 01:04:04 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA27906
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 01:04:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1539XI-000CbG-00
	for idn-data@psg.com; Thu, 24 May 2001 21:49:16 -0700
Received: from arachnid.ehsco.com ([209.31.7.46] helo=Arachnid.NTRG.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 1539XI-000CbA-00
	for idn@ops.ietf.org; Thu, 24 May 2001 21:49:16 -0700
Received: from ehsco.com (FERRET.NTRG.com [192.168.10.10])
          by Arachnid.NTRG.com (Netscape Messaging Server 3.62)  with ESMTP
          id 626 for <idn@ops.ietf.org>; Thu, 24 May 2001 21:49:14 -0700
Message-ID: <3B0DE44A.4C0462B2@ehsco.com>
Date: Thu, 24 May 2001 21:49:14 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: idn@ops.ietf.org
Subject: Re: [idn] Why we can go directly to UTF-8
References: <4.2.0.58.J.20010524223716.02fe5100@sh.w3.mag.keio.ac.jp> <3B0DD39F.515161DD@ehsco.com> <20010525035948.28153.qmail@cr.yp.to> <3B0DE15D.752FBECA@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


> Those systems enforce LDH, and will reject non-LDH sets.

If we're into lists, here's one I'd like to see: all of the systems which
provide user input of domain names, and which are also aware of the
variable-octets underlying UTF-8 domain names. These systems need to know
that the domain name will have a maximum label length of 63 octets and
prevent additional input when the UTF-8 octet limit is exceeded, which
will be dramatically different than the displayed character count.

The list of systems which do support this will certainly be shorter than
the list of systems which don't, so that is an action item for you I would
guess. :/

Now look, seriously, there is *no* *freakin* *way* that we can go to
just-do-UTF-8. At the very least resolvers need to know about the
difference between wide() and normal names, systems need $HOSTNAME calls
that support UTF-8 encodings, etc. This is a massive undertaking.

I am clearly on record in the archives as supporting a clean break from
the past, but it must be a clean break. Fudgery just will not work.

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



From owner-idn@ops.ietf.org  Fri May 25 03:24:58 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA13188
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 03:24:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153BVa-000GLW-00
	for idn-data@psg.com; Thu, 24 May 2001 23:55:38 -0700
To: mark@macchiato.com
Cc: idn@ops.ietf.org, liana.ydisg@juno.com
Date: Thu, 24 May 2001 13:23:48 -0700
Subject: Re: [idn] Working direction of IDN
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Message-Id: <E153BVa-000GLW-00@psg.com>

You have addressed the very problem of using ISO 10646 / Unicode as day
to day
information/samantic processing of CJK characters.  There is no single
expert who
would use all of the characters in the set, why do we care to carry so
many characters
in our register?  However, there are sparse needs for the characters,
which
the computer does well for human beings.  That is an argument for a
language
based script to be coded as IDN names.

Besides, there are studies from China in the 80's, that about 1000
frequently used Chinese characters which are composed into the larger
set
of Chinese characters.

Liana Ye


On Thu, 24 May 2001 06:51:25 -0700 "Mark Davis" <markdavis34@home.com>
writes:
> There is a lot of misinformation floating around about the support of
> Chinese, Japanese and Korean characters. ISO 10646 / Unicode
> supports over
> 70,000 Chinese characters right now, and work is underway to encode
> further
> sets. It has the same repertoire as the Chinese GB18030 and GB
> 13000.
>
> This work is being done by the IRG, which includes representatives
> of the
> governments of China, Hong Kong, Singapore, Japan, South Korea,
> North Korea,
> Taiwan and Vietnam, plus a representative from the Unicode
> consortium (cf
> http://www.info.gov.hk/digital21/eng/structure/intro_irg.html).
>
> This group is very careful cataloging, reviewing, and assessing
> Chinese
> characters for inclusion into the standard. The only real limitation
> on the
> number of Chinese characters in the standard is the ability of this
> group to
> process them, because the characters are increasingly obscure (no
> person
> knows more than a fraction of the set already encoded).
>
> Mark
>
> ----- Original Message -----
> From: <liana.ydisg@juno.com>
> To: <idn@ops.ietf.org>
> Cc: <liana.ydisg@juno.com>
> Sent: Wednesday, May 23, 2001 23:16
> Subject: [idn] Working direction of IDN
>
>
> > All:
> >
> > Answer to James Seng's comment:
> >
> > >Correct me if I am wrong...from your email, you are suggesting
> that IDN
> > >to be encoded in a strings based on its symbols which makes up
> the
> > >script. While this is an intriguing thought, unfortunately, I do
> not
> > >think we have sufficient work done in that direction.
> >
> > >Our current works basically resolves using ISO10646 as a basis
> for
> > >encoding names. Whatever limitation ISO10646 has, it is
> improving.
> >
> > I am suggesting that IDN to be encoded in a strings based on its
> symbols
> > which makes up the script.
> >
> > Although IDN has no need to concern with trademarks at this time,
> it is
> > the idn limitation to support only [ISO10646] bothers me.
> [ISO10646]
> > does not support all Chinese characters, since Chinese character
> set has
> > more than 100,000 characters already.  There are cases that we can
> not
> > find a live person's name on our current computers, don't  mention
> the
> > dead ones.  At the speed of computer and network development, when
> the
> > applications catch up with us, millions of more data going to be
> on the
> > net for accessing.  Are we going to revamp our idn again?  I can
> suggest
> > an ACE using a recursive rule to handle any symbols that are not
> possible
> > to be simply folded onto ASCII character set.  Such an ACE creats
> a
> > virtue character set, which is possible
> >  to include any characters or icons requested by a user, as long
> as that
> > icon has been encoded by an ACE somewhere on the net.  When the
> IDN can
> > take more than 63 octets or v6 or v8, the ACE can follow without
> > troubling the users.  Let alone the idea to send Unicode down to
> the
> > wire.  It is not user friendly, it is make no sense for the
> tradename
> > servers.
> >
> > Liana Ye
> >
>





From owner-idn@ops.ietf.org  Fri May 25 07:35:58 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA15119
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 07:35:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153FYg-000OCs-00
	for idn-data@psg.com; Fri, 25 May 2001 04:15:06 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 153FYe-000OCU-00
	for idn@ops.ietf.org; Fri, 25 May 2001 04:15:04 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4PBETf78406
	for <idn@ops.ietf.org>; Fri, 25 May 2001 07:14:30 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105251114.f4PBETf78406@nic-naa.net>
To: idn@ops.ietf.org
Subject: [idn] Listing utf8 (in)capable parts
Date: Fri, 25 May 2001 07:14:29 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I suggest that those interested in moving the discussion of binary only,
or ace plus binary, or ace only, can contribute to making the evaluation
of architectural choices clearer.

The mail could look like this:
	To: idn@ops.ietf.org
	From: Person with Foo Clue
	Subject: Foo (MTA) utf8 status [yes/no/other]
with an optionally non-empty body.

There'd be unformatted but searchable ascii in the idn list archive, anyone
could pretty-print it who wanted to make a (im)possible-to-proceede matrix,
and we could dampen the trivial/intractible assertions slightly.

If this work has already been done I'd appreciate a pointer.

Cheers,
Eric



From owner-idn@ops.ietf.org  Fri May 25 08:59:40 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA16939
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 08:59:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153H13-00012H-00
	for idn-data@psg.com; Fri, 25 May 2001 05:48:29 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153H13-000122-00
	for idn@ops.ietf.org; Fri, 25 May 2001 05:48:29 -0700
Received: from CLASSIC.viagenie.qc.ca (classic.viagenie.qc.ca [206.123.31.136])
	by jazz.viagenie.qc.ca (Viagenie/8.11.0) with ESMTP id f4PD39133212
	for <idn@ops.ietf.org>; Fri, 25 May 2001 09:03:09 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca>
X-Sender: blanchet@mail.viagenie.qc.ca
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 25 May 2001 08:38:50 -0400
To: idn@ops.ietf.org
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: [idn] report of the straw poll
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Sun, 20 May 2001 09:51:31 -0400, an electronic straw poll was requested 
by the idn co-chairs to reverify the previous concensus on 
idna-nameprep-ace proposal. Those who disagree were asked to identify the 
draft of the suggested alternative. The end of the poll was wednesday May 
23rd 2001, 23h59 GMT.

50 participants participated in the straw poll.

36 participants agree with the idna-nameprep-ace orientation.

14 participants disagree. In this group, here is a summary of the suggested 
alternatives with the number of people in the front of each line:

   1 UCS or UTF variants preferred
   2 draft-skwan-utf8-dns-06.txt
   2 Just send UTF

   1 The DNSII Multilingual Domain Name Protocol
   1 draft-ietf-idn-vidn-01.txt
   1 draft-ietf-idn-uname-00.txt

   2 draft-ietf-idn-udns, draft-ietf-idn-uname, draft-ietf-idn-idne, 
draft-ietf-idn-iptr, draft-ietf-idn-vidn, draft-skwan-utf8-dns,
      draft-klensin-dns-role
   1 premature to decide before exploring alternatives

   3 nothing proposed


The counters group: Marc Blanchet, Dave Crocker, James Seng, Rick Wesson, 
Yoshiro Yoneya







From owner-idn@ops.ietf.org  Fri May 25 09:15:23 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA17372
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 09:15:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153HB5-0001NI-00
	for idn-data@psg.com; Fri, 25 May 2001 05:58:51 -0700
Received: from [152.160.20.25] (helo=admin1.corp.walid.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 153HB4-0001N6-00
	for idn@ops.ietf.org; Fri, 25 May 2001 05:58:51 -0700
Received: from CHOAM (admin1.corp.walid.com [152.160.20.25])
	by admin1.corp.walid.com (8.9.3/8.9.3) with SMTP id MAA05279;
	Fri, 25 May 2001 12:58:14 GMT
From: "Brian W. Spolarich" <briansp@walid.com>
To: "Eric A. Hall" <ehall@ehsco.com>, <idn@ops.ietf.org>
Subject: RE: [idn] Why we can go directly to UTF-8
Date: Fri, 25 May 2001 09:00:52 -0400
Message-ID: <FJEPLIJJEDBNPIOAEIHDEEMECDAA.briansp@walid.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
In-Reply-To: <3B0DE44A.4C0462B2@ehsco.com>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


| Now look, seriously, there is *no* *freakin* *way* that we can go to
| just-do-UTF-8. At the very least resolvers need to know about the
| difference between wide() and normal names, systems need $HOSTNAME calls
| that support UTF-8 encodings, etc. This is a massive undertaking.

  The 'just send UTF-8' approach also ignores the normalization issues
addressed by nameprep, unless you think, as Bill Semich has suggested,
that a protocol based on nameprep only somehow makes sense and is 
actually deployable.

  -bws



From owner-idn@ops.ietf.org  Fri May 25 09:24:46 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA17562
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 09:24:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153HPW-0001sB-00
	for idn-data@psg.com; Fri, 25 May 2001 06:13:46 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153HPV-0001s4-00
	for idn@ops.ietf.org; Fri, 25 May 2001 06:13: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 JAA27470;
        Fri, 25 May 2001 09:13:43 -0400 (EDT)
Message-Id: <200105251313.JAA27470@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
cc: idn@ops.ietf.org
Subject: Re: [idn] Listing utf8 (in)capable parts 
In-reply-to: Your message of "Fri, 25 May 2001 07:14:29 EDT."
             <200105251114.f4PBETf78406@nic-naa.net> 
Date: Fri, 25 May 2001 09:13:43 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> If this work has already been done I'd appreciate a pointer.

a vague assertion of a particular component "working" with utf8
is meaningless.  this is true partially because we lack agreement 
on a useful definition of "work". but even if we had such a 
definition,  the fact that a few individual components "work"
under controlled conditions with a limited sample of cases
is not terribly useful as an indicator of whether large numbers of 
components would interoperate in the diversity of the real world.

networks interoperate reliably by design, not by accident.

Keith



From owner-idn@ops.ietf.org  Fri May 25 10:11:24 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA18505
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 10:11:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153I2z-0003Ho-00
	for idn-data@psg.com; Fri, 25 May 2001 06:54:33 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153I2y-0003Hh-00
	for idn@ops.ietf.org; Fri, 25 May 2001 06:54:32 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA27981;
        Fri, 25 May 2001 09:54:29 -0400 (EDT)
Message-Id: <200105251354.JAA27981@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
cc: idn@ops.ietf.org
Subject: Re: [idn] report of the straw poll 
In-reply-to: Your message of "Fri, 25 May 2001 08:38:50 EDT."
             <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca> 
Date: Fri, 25 May 2001 09:54:29 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I'd be curious to know who would support idna-nameprep-ace in the
short term with the assurance that a native utf-8 query protocol
would be worked on after idna-nameprep-ace went out the door.

Granted, this wouldn't automatically force upgrade of all applications
to use utf-8 domains, but it would make it easier for new applications
to use utf-8 natively, which is something.  

Existing applications could also upgrade to use it, but this would
happen on a per-application basis, and would require (at a minimum)
that there be sufficient interest in a group to work out the details 
of a a smooth and non-disruptive transition.

Keith



From owner-idn@ops.ietf.org  Fri May 25 10:27:57 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA18825
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 10:27:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153INO-00045J-00
	for idn-data@psg.com; Fri, 25 May 2001 07:15:38 -0700
Received: from femail1.sdc1.sfba.home.com ([24.0.95.81])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153INN-000455-00
	for idn@ops.ietf.org; Fri, 25 May 2001 07:15:37 -0700
Received: from c1340594a ([65.11.104.12]) by femail1.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20010525141531.ILAN13163.femail1.sdc1.sfba.home.com@c1340594a>;
          Fri, 25 May 2001 07:15:31 -0700
Message-ID: <007d01c0e525$42585610$0c680b41@c1340594a>
Reply-To: "Mark Davis" <mark@macchiato.com>
From: "Mark Davis" <markdavis34@home.com>
To: <mark@macchiato.com>, <liana.ydisg@juno.com>, <idn@ops.ietf.org>
References: <E153BVa-000GLW-00@psg.com>
Subject: Re: [idn] Working direction of IDN
Date: Fri, 25 May 2001 07:16:15 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I'm sorry, I don't really understand your point.

We recognize that additional characters are in use, and the national
governments of these countries are continuing to encode more characters in
the IRG. However, the frequency of use of those characters is *extremely*
low, and does not prevent the successful deployment of Unicode/10646
solutions for CJK characters. (For example, anyone using Microsoft Office
for Japanese, Chinese or Korean is already using Unicode internally).

When you say "language-based script", I was guessing that you are in favor
of encoding different national standards for encoding Chinese characters.
There are huge disadvantages to the approach of using different encodings,
in that there would be *many* different representations for the same
sequence of characters.

While theoretically one could have mapping tables between these sequences,
in practice every platform's mappings differs from the others. Even when you
think that you are using the same charset, on different platforms you will
get different conversions: that means that you will get data corruption
problems. (For example, in IBM we have collected over 700 unique character
conversion mappings that we have found on different platforms -- see
http://oss.software.ibm.com/cvs/icu/charset/data/xml/).

However, the last part of your message seems to indicate that you don't want
a national standard, but instead want to use some new system that uses
decomposition of Chinese characters. While Unicode/10646 does provide a way
to *describe* characters via such a mechanism (see Ideographic Description
Characters in the Unicode Standard), it is not recommended for encoding
Chinese characters.

Early in Unicode's history, we looked at the possibility of encoding Chinese
characters in this way. This approach requires the use of variable numbers
of code points to represent Chinese characters, and that unless far more
than 1000 base characters used, the lengths of the sequences can get quite
long.

If you are interested in further discussion of this topic, I'd suggest you
contact some of the experts in the IRG.

Mark

----- Original Message -----
From: <liana.ydisg@juno.com>
To: <mark@macchiato.com>
Cc: <idn@ops.ietf.org>; <liana.ydisg@juno.com>
Sent: Thursday, May 24, 2001 13:23
Subject: Re: [idn] Working direction of IDN


> You have addressed the very problem of using ISO 10646 / Unicode as day
> to day
> information/samantic processing of CJK characters.  There is no single
> expert who
> would use all of the characters in the set, why do we care to carry so
> many characters
> in our register?  However, there are sparse needs for the characters,
> which
> the computer does well for human beings.  That is an argument for a
> language
> based script to be coded as IDN names.
>
> Besides, there are studies from China in the 80's, that about 1000
> frequently used Chinese characters which are composed into the larger
> set
> of Chinese characters.
>
> Liana Ye
>
>
> On Thu, 24 May 2001 06:51:25 -0700 "Mark Davis" <markdavis34@home.com>
> writes:
> > There is a lot of misinformation floating around about the support of
> > Chinese, Japanese and Korean characters. ISO 10646 / Unicode
> > supports over
> > 70,000 Chinese characters right now, and work is underway to encode
> > further
> > sets. It has the same repertoire as the Chinese GB18030 and GB
> > 13000.
> >
> > This work is being done by the IRG, which includes representatives
> > of the
> > governments of China, Hong Kong, Singapore, Japan, South Korea,
> > North Korea,
> > Taiwan and Vietnam, plus a representative from the Unicode
> > consortium (cf
> > http://www.info.gov.hk/digital21/eng/structure/intro_irg.html).
> >
> > This group is very careful cataloging, reviewing, and assessing
> > Chinese
> > characters for inclusion into the standard. The only real limitation
> > on the
> > number of Chinese characters in the standard is the ability of this
> > group to
> > process them, because the characters are increasingly obscure (no
> > person
> > knows more than a fraction of the set already encoded).
> >
> > Mark
> >
> > ----- Original Message -----
> > From: <liana.ydisg@juno.com>
> > To: <idn@ops.ietf.org>
> > Cc: <liana.ydisg@juno.com>
> > Sent: Wednesday, May 23, 2001 23:16
> > Subject: [idn] Working direction of IDN
> >
> >
> > > All:
> > >
> > > Answer to James Seng's comment:
> > >
> > > >Correct me if I am wrong...from your email, you are suggesting
> > that IDN
> > > >to be encoded in a strings based on its symbols which makes up
> > the
> > > >script. While this is an intriguing thought, unfortunately, I do
> > not
> > > >think we have sufficient work done in that direction.
> > >
> > > >Our current works basically resolves using ISO10646 as a basis
> > for
> > > >encoding names. Whatever limitation ISO10646 has, it is
> > improving.
> > >
> > > I am suggesting that IDN to be encoded in a strings based on its
> > symbols
> > > which makes up the script.
> > >
> > > Although IDN has no need to concern with trademarks at this time,
> > it is
> > > the idn limitation to support only [ISO10646] bothers me.
> > [ISO10646]
> > > does not support all Chinese characters, since Chinese character
> > set has
> > > more than 100,000 characters already.  There are cases that we can
> > not
> > > find a live person's name on our current computers, don't  mention
> > the
> > > dead ones.  At the speed of computer and network development, when
> > the
> > > applications catch up with us, millions of more data going to be
> > on the
> > > net for accessing.  Are we going to revamp our idn again?  I can
> > suggest
> > > an ACE using a recursive rule to handle any symbols that are not
> > possible
> > > to be simply folded onto ASCII character set.  Such an ACE creats
> > a
> > > virtue character set, which is possible
> > >  to include any characters or icons requested by a user, as long
> > as that
> > > icon has been encoded by an ACE somewhere on the net.  When the
> > IDN can
> > > take more than 63 octets or v6 or v8, the ACE can follow without
> > > troubling the users.  Let alone the idea to send Unicode down to
> > the
> > > wire.  It is not user friendly, it is make no sense for the
> > tradename
> > > servers.
> > >
> > > Liana Ye
> > >
> >
>
>
>
>




From owner-idn@ops.ietf.org  Fri May 25 11:50:20 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA19919
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 11:50:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153JWt-0006ep-00
	for idn-data@psg.com; Fri, 25 May 2001 08:29:31 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 153JWs-0006ej-00
	for idn@ops.ietf.org; Fri, 25 May 2001 08:29:30 -0700
Received: (qmail 18514 invoked by uid 1001); 25 May 2001 14:29:12 -0000
Date: 25 May 2001 14:29:12 -0000
Message-ID: <20010525142912.23844.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] Why we can go directly to UTF-8
References: <4.2.0.58.J.20010524223716.02fe5100@sh.w3.mag.keio.ac.jp> <3B0DD39F.515161DD@ehsco.com> <20010525035948.28153.qmail@cr.yp.to> <3B0DE15D.752FBECA@ehsco.com> <3B0DE44A.4C0462B2@ehsco.com> <4.2.0.58.J.20010524223716.02fe5100@sh.w3.mag.keio.ac.jp> <3B0DD39F.515161DD@ehsco.com> <20010525035948.28153.qmail@cr.yp.to> <3B0DE15D.752FBECA@ehsco.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:
> This is a massive undertaking.

Every IDN proposal involves massive costs---in particular, upgrading
sendmail. The point of my IDN web page is to collect information on
those costs:

   http://cr.yp.to/proto/idn.html

ACE with slow nameprep requires redeployment of apache, fetchmail,
gethostbyname, lynx, mutt, named, netscape, pine, publicfile, qmail,
sendmail, sshd, tcpclient, tcprules, tinydns, w3m, and many similar
pieces of code.

UTF-8 with fast nameprep requires redeployment of gethostbyname (except
that some versions have been fixed already), mutt, pine, and sendmail.
If anything else needs to be upgraded, please let me know.

> These systems need to know
> that the domain name will have a maximum label length of 63 octets

Wrong again. The 63-byte limit is isolated inside one library routine
that converts textual domain names to DNS packet format. That routine
already works perfectly with UTF-8. I don't know where you got the idea
that applications have to stop users from typing more than 63 bytes.

> If I had kept a list of every device and application that broke when a
> customer of mine thought "_" was legal, I'd gladly give it to you.

In other words, you don't have a single shred of verifiable evidence.   
Your memories are so vague that you can't even tell us what programs you
were using---but you're confident that those programs would have trouble
with UTF-8, and you're making major decisions on this basis.

---Dan



From owner-idn@ops.ietf.org  Fri May 25 12:26:36 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA20693
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 12:26:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153Jw9-0007VN-00
	for idn-data@psg.com; Fri, 25 May 2001 08:55:37 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153Jw8-0007VH-00
	for idn@ops.ietf.org; Fri, 25 May 2001 08:55:36 -0700
Received: from [165.227.249.18] (ip18.proper.com [165.227.249.18] (may be forged))
	by above.proper.com (8.9.3/8.9.3) with ESMTP id IAA13688
	for <idn@ops.ietf.org>; Fri, 25 May 2001 08:55:33 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100336b7342f40ac9b@[165.227.249.18]>
In-Reply-To: <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca>
References: <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca>
Date: Fri, 25 May 2001 08:54:46 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] report of the straw poll
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 8:38 AM -0400 5/25/01, Marc Blanchet wrote:
>50 participants participated in the straw poll.
>
>36 participants agree with the idna-nameprep-ace orientation.
>
>14 participants disagree. In this group, here is a summary of the 
>suggested alternatives with the number of people in the front of 
>each line:

The WG chair didn't seem to declare "rough consensus", unfortunately. 
The poll showed one strongly-favored choice and a vast smattering of 
other choices with none having even 10% of the support. Is there a 
suggestion about how we should proceed? If the folks not supporting 
the most-desired protocol could coalesce around a single Internet 
Draft, it would be most helpful. Otherwise, there is nothing to 
compare with the strongly-favored Internet Draft.

Given that the large majority of the voters want to see IDNA, Patrik 
and I will certainly continue to work on it. Note that there is, as 
far as we can tell, almost no more work to be done; we have received 
only one substantiative comment on the draft, and that will be 
included in a new draft in the next few days. Beyond that, we need to 
pick an ACE (and the ACE Design Team should have at least a 
preliminary statement shortly), and need to finish nameprep, which at 
this point is finished other than it does not address the new 
characters added in Unicode 3.1.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Fri May 25 12:30:17 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA20777
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 12:30:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153KDR-000897-00
	for idn-data@psg.com; Fri, 25 May 2001 09:13:29 -0700
Received: from [208.36.200.36] (helo=BILL)
	by psg.com with esmtp (Exim 3.16 #1)
	id 153KDQ-00088y-00
	for idn@ops.ietf.org; Fri, 25 May 2001 09:13:28 -0700
Received: from localhost [127.0.0.1]
	by BILL
	with SMTPBeamer v3.19 ;
	Fri, 25 May 2001 12:10:15 -0400
Message-Id: <3.0.5.32.20010525121013.04c2f100@mail.nic.nu>
X-Sender: bill@mail.nic.nu
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Fri, 25 May 2001 12:10:13 -0400
To: Paul Hoffman / IMC <phoffman@imc.org>, idn@ops.ietf.org
From: "J. William Semich" <bill@mail.nic.nu>
Subject: Re: [idn] report of the straw poll
In-Reply-To: <p05100336b7342f40ac9b@[165.227.249.18]>
References: <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca>
 <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 08:54 AM 5/25/01 -0700, Paul Hoffman / IMC wrote:
<snip>

>Given that the large majority of the voters want to see IDNA, ...>
>--Paul Hoffman, Director
>--Internet Mail Consortium
>
Paul - The opinions of the tiny subset of 36 members of this WG do not
represent a "vast" majority of anything whatsoever in the truly vast set of
multi-millions of Internet users, systems and application developers, and
connectivity providers.

Bill Semich




From owner-idn@ops.ietf.org  Fri May 25 12:48:59 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA21206
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 12:48:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153KSv-0008ph-00
	for idn-data@psg.com; Fri, 25 May 2001 09:29:29 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153KSu-0008pb-00
	for idn@ops.ietf.org; Fri, 25 May 2001 09:29:28 -0700
Received: from [165.227.249.18] (ip18.proper.com [165.227.249.18] (may be forged))
	by above.proper.com (8.9.3/8.9.3) with ESMTP id JAA15261
	for <idn@ops.ietf.org>; Fri, 25 May 2001 09:29:25 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100339b73436e47854@[165.227.249.18]>
In-Reply-To: <3.0.5.32.20010525121013.04c2f100@mail.nic.nu>
References: <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca>
 <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca>
 <3.0.5.32.20010525121013.04c2f100@mail.nic.nu>
Date: Fri, 25 May 2001 09:28:39 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] report of the straw poll
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 12:10 PM -0400 5/25/01, J. William Semich wrote:
>Paul - The opinions of the tiny subset of 36 members of this WG do not
>represent a "vast" majority of anything whatsoever in the truly vast set of
>multi-millions of Internet users, systems and application developers, and
>connectivity providers.

So, what are you suggesting that we do instead? Because the IETF 
cannot ever get the opinions of even 1% of all Internet users as we 
develop new Internet protocols, are you saying we should just stop 
working on them right now? If so, who do you propose should work on 
Internet protocols? No other standards body polls any significant 
percentage of Internet users before creating protocols, and no 
private company does so before it creates its own proprietary 
protocols. Are you saying that no more protocols should be developed 
by anyone?

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Fri May 25 13:17:23 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA21747
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 13:17:21 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153KyZ-000A54-00
	for idn-data@psg.com; Fri, 25 May 2001 10:02:11 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 153KyY-000A4o-00
	for idn@ops.ietf.org; Fri, 25 May 2001 10:02:10 -0700
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id KAA24148;
	Fri, 25 May 2001 10:02:04 -0700
Message-Id: <5.1.0.14.2.20010525095627.039fa698@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 25 May 2001 10:00:20 -0700
To: Paul Hoffman / IMC <phoffman@imc.org>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] report of the straw poll
Cc: idn@ops.ietf.org
In-Reply-To: <p05100336b7342f40ac9b@[165.227.249.18]>
References: <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca>
 <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 08:54 AM 5/25/2001, Paul Hoffman / IMC wrote:
>The WG chair didn't seem to declare "rough consensus", unfortunately. The 
>poll showed one strongly-favored choice and a vast smattering of other 
>choices with none having even 10% of the support. Is

Bill Semich's concern that 'yes' got only 36 votes has some appeal, 
although the normal IETF view is that we only consider the concerns and 
desires of those who show up.  We cannot guess the desires of people who 
did not participate in the straw poll.

On the other hand, the 36 was less than 2/3 of the vote.  My personal 
approximation between "rough consensus" a percentage is not less than 2/3, 
because having 1/3 of a group disagree with a decision is simply too strong 
a constituency to have unhappy.

As to how to proceed, I wonder whether we should first resolve the question 
of urgency.  Although it is beyond my comprehension, a number of people 
seem to believe that there is little urgency.  Perhaps we should assess 
working group view of urgency.  If there is consensus about urgency THEN we 
can try to consider what solutions are amenable to quicker deployment.

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 May 25 13:20:35 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA21791
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 13:20:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153L6T-000AOj-00
	for idn-data@psg.com; Fri, 25 May 2001 10:10:21 -0700
Received: from arachnid.ehsco.com ([209.31.7.46] helo=Arachnid.NTRG.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 153L6S-000AOd-00
	for idn@ops.ietf.org; Fri, 25 May 2001 10:10:20 -0700
Received: from ehsco.com (FERRET.NTRG.com [192.168.10.10])
          by Arachnid.NTRG.com (Netscape Messaging Server 3.62)  with ESMTP
          id 574 for <idn@ops.ietf.org>; Fri, 25 May 2001 10:10:17 -0700
Message-ID: <3B0E91F9.3415113A@ehsco.com>
Date: Fri, 25 May 2001 10:10:17 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
CC: idn@ops.ietf.org
Subject: Re: [idn] Why we can go directly to UTF-8
References: <4.2.0.58.J.20010524223716.02fe5100@sh.w3.mag.keio.ac.jp> <3B0DD39F.515161DD@ehsco.com> <20010525035948.28153.qmail@cr.yp.to> <3B0DE15D.752FBECA@ehsco.com> <3B0DE44A.4C0462B2@ehsco.com> <4.2.0.58.J.20010524223716.02fe5100@sh.w3.mag.keio.ac.jp> <3B0DD39F.515161DD@ehsco.com> <20010525035948.28153.qmail@cr.yp.to> <3B0DE15D.752FBECA@ehsco.com> <20010525142912.23844.qmail@cr.yp.to>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


"D. J. Bernstein" wrote:

> Your memories are so vague that you can't even tell us what programs
> you were using---but you're confident that those programs would have
> trouble with UTF-8, and you're making major decisions on this basis.

Feel free to rename your domain to _test_.cr.yp.to. and report back with
your success. Since I already know what will happen, I won't bother.

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



From owner-idn@ops.ietf.org  Fri May 25 13:21:39 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA21802
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 13:21:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153L55-000AKq-00
	for idn-data@psg.com; Fri, 25 May 2001 10:08: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.16 #1)
	id 153L54-000AKj-00
	for idn@ops.ietf.org; Fri, 25 May 2001 10:08:54 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4PH8Pf79644
	for <idn@ops.ietf.org>; Fri, 25 May 2001 13:08:25 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105251708.f4PH8Pf79644@nic-naa.net>
To: idn@ops.ietf.org
Subject: [idn] Poisonous atmosphere
Date: Fri, 25 May 2001 13:08:25 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This list has become really ugly all of a sudden. Is it the onset of Summer
and alergy season, or ICANN Encounters of the Worst Kind, or just the rise
of greenhouse gases? I wish it would go away, and if I brought it on, I'd
go and take it with me.

Cheers,
Eric



From owner-idn@ops.ietf.org  Fri May 25 13:43:45 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA22127
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 13:43:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153LNP-000B0A-00
	for idn-data@psg.com; Fri, 25 May 2001 10:27:51 -0700
Received: from [208.36.200.36] (helo=BILL)
	by psg.com with esmtp (Exim 3.16 #1)
	id 153LNO-000B03-00
	for idn@ops.ietf.org; Fri, 25 May 2001 10:27:50 -0700
Received: from localhost [127.0.0.1]
	by BILL
	with SMTPBeamer v3.19 ;
	Fri, 25 May 2001 13:09:50 -0400
Message-Id: <3.0.5.32.20010525130949.04c2ed10@mail.nic.nu>
X-Sender: bill@mail.nic.nu
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Fri, 25 May 2001 13:09:49 -0400
To: Paul Hoffman / IMC <phoffman@imc.org>, idn@ops.ietf.org
From: "J. William Semich" <bill@mail.nic.nu>
Subject: Re: [idn] report of the straw poll
In-Reply-To: <p05100339b73436e47854@[165.227.249.18]>
References: <3.0.5.32.20010525121013.04c2f100@mail.nic.nu>
 <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca>
 <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca>
 <3.0.5.32.20010525121013.04c2f100@mail.nic.nu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I think we should wrok harder to get consensus, that's all. Among the 14
are representatives of the interests of many millions of users, working all
over the world with systems using established protocols based on UTF-8,
etc. That should be given some weight as well.

I agree it would be a good idea to put forward a single alternative to IDNA
for consideration ...

Bill

At 09:28 AM 5/25/01 -0700, Paul Hoffman / IMC wrote:
>At 12:10 PM -0400 5/25/01, J. William Semich wrote:
>>Paul - The opinions of the tiny subset of 36 members of this WG do not
>>represent a "vast" majority of anything whatsoever in the truly vast set of
>>multi-millions of Internet users, systems and application developers, and
>>connectivity providers.
>
>So, what are you suggesting that we do instead? Because the IETF 
>cannot ever get the opinions of even 1% of all Internet users as we 
>develop new Internet protocols, are you saying we should just stop 
>working on them right now? If so, who do you propose should work on 
>Internet protocols? No other standards body polls any significant 
>percentage of Internet users before creating protocols, and no 
>private company does so before it creates its own proprietary 
>protocols. Are you saying that no more protocols should be developed 
>by anyone?
>
>--Paul Hoffman, Director
>--Internet Mail Consortium
>
>
Bill Semich
President and Founder
WorldNames, Inc.
http://www.worldnames.net
bsemich@worldnames.net



From owner-idn@ops.ietf.org  Fri May 25 13:58:13 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA22356
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 13:58:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153LUS-000BHn-00
	for idn-data@psg.com; Fri, 25 May 2001 10:35:08 -0700
Received: from work.netcorps.com ([207.1.125.100])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153LUR-000BHd-00
	for idn@ops.ietf.org; Fri, 25 May 2001 10:35:07 -0700
Received: from localhost (bright@localhost)
	by work.netcorps.com (8.9.0/8.9.0) with SMTP id KAA17675;
	Fri, 25 May 2001 10:34:26 -0700 (PDT)
Date: Fri, 25 May 2001 10:34:26 -0700 (PDT)
From: Bright Fulton <bright@alldomains.com>
X-Sender: bright@work.netcorps.com
To: Dave Crocker <dhc@dcrocker.net>
cc: Paul Hoffman / IMC <phoffman@imc.org>, idn@ops.ietf.org
Subject: Re: [idn] report of the straw poll
In-Reply-To: <5.1.0.14.2.20010525095627.039fa698@dcrocker.net>
Message-ID: <Pine.GSO.3.96.1010525103031.16075C-100000@work.netcorps.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

36 of 50 is 72%.  The other 28% was split.  Whether or not the poll was
accurate, and whether or not the majority is right, there is a clear
majority.

Bright


On Fri, 25 May 2001, Dave Crocker wrote:

> At 08:54 AM 5/25/2001, Paul Hoffman / IMC wrote:
> >The WG chair didn't seem to declare "rough consensus", unfortunately. The 
> >poll showed one strongly-favored choice and a vast smattering of other 
> >choices with none having even 10% of the support. Is
> 
> Bill Semich's concern that 'yes' got only 36 votes has some appeal, 
> although the normal IETF view is that we only consider the concerns and 
> desires of those who show up.  We cannot guess the desires of people who 
> did not participate in the straw poll.
> 
> On the other hand, the 36 was less than 2/3 of the vote.  My personal 
> approximation between "rough consensus" a percentage is not less than 2/3, 
> because having 1/3 of a group disagree with a decision is simply too strong 
> a constituency to have unhappy.
> 
> As to how to proceed, I wonder whether we should first resolve the question 
> of urgency.  Although it is beyond my comprehension, a number of people 
> seem to believe that there is little urgency.  Perhaps we should assess 
> working group view of urgency.  If there is consensus about urgency THEN we 
> can try to consider what solutions are amenable to quicker deployment.
> 
> 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 May 25 13:58:13 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA22355
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 13:58:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153LZu-000BYE-00
	for idn-data@psg.com; Fri, 25 May 2001 10:40:46 -0700
Received: from arachnid.ehsco.com ([209.31.7.46] helo=Arachnid.NTRG.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 153LZu-000BY7-00
	for idn@ops.ietf.org; Fri, 25 May 2001 10:40:46 -0700
Received: from ehsco.com (FERRET.NTRG.com [192.168.10.10])
          by Arachnid.NTRG.com (Netscape Messaging Server 3.62)  with ESMTP
          id 648; Fri, 25 May 2001 10:40:43 -0700
Message-ID: <3B0E991A.454DFECB@ehsco.com>
Date: Fri, 25 May 2001 10:40:42 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>, idn@ops.ietf.org
Subject: Re: [idn] report of the straw poll
References: <200105251354.JAA27981@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Keith Moore wrote:
> 
> I'd be curious to know who would support idna-nameprep-ace in the
> short term with the assurance that a native utf-8 query protocol
> would be worked on after idna-nameprep-ace went out the door.

Can you turn that statement around and still be happy with it? Rather than
saying, "we commit to do something better in the long term" can we say
"ACE is the legacy interface component of XXXX long-term strategy"? IOW,
can we define a long-term strategy that ACE plugs into?

I've advocated EDNS as the best technical solution to the problem, but I
also recognize that the use of UTF-8 data breaks older systems (I favor
EDNS because it forces the break, and because it offers the broadest
future features). If we can agree that EDNS (as an example) is the
appropriate long-term solution AND begin designing around it, AND then we
include ACE as a way to provide fall-back backwards compatibilty to legacy
systems, then we have a holistic solution.

Let's take email as an example of this principle. Just for arguments sake,
we agree that EDNS is the way to go and begin desingingh an ESMTP
extension to negotiate the use of IDN, and specify the use of ACE if the
negotiation fails.

In that example, ACE provides necessary backwards compatibility to a
long-term approach, rather than being a destination in its own right. We
can design for long-term features and capabilities from the start, without
asking designers to do everything twice (once for ACE, once for something
else).

FWIW, I did not vote in the straw poll because neither option represented
my feelings on the matter.

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



From owner-idn@ops.ietf.org  Fri May 25 13:58:46 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA22378
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 13:58:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153LZE-000BX6-00
	for idn-data@psg.com; Fri, 25 May 2001 10:40:04 -0700
Received: from ibd.ar.com ([63.194.205.75])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153LZD-000BWx-00
	for idn@ops.ietf.org; Fri, 25 May 2001 10:40:03 -0700
Received: from loki (wessorh@loki.ar.com [10.10.10.88])
	by ibd.ar.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id KAA06691;
	Fri, 25 May 2001 10:38:12 -0700 (PDT)
Date: Fri, 25 May 2001 10:39:53 -0700 (PDT)
From: Rick H Wesson <wessorh@ar.com>
To: "J. William Semich" <bill@mail.nic.nu>
cc: Paul Hoffman / IMC <phoffman@imc.org>, <idn@ops.ietf.org>
Subject: Re: [idn] report of the straw poll
In-Reply-To: <3.0.5.32.20010525130949.04c2ed10@mail.nic.nu>
Message-ID: <Pine.LNX.4.30.0105251037060.409-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk



Bill,

first you state that the 36 yes votes represent individuals, later you
state the 14 no votes represent "millions of users," you can't have it
both ways.

you did get one thing orrect, you need to coloess the 14 no votes with
nearly 7 proposals into one single alternative to IDNA.

-rick


On Fri, 25 May 2001, J. William Semich wrote:

> I think we should wrok harder to get consensus, that's all. Among the 14
> are representatives of the interests of many millions of users, working all
> over the world with systems using established protocols based on UTF-8,
> etc. That should be given some weight as well.
>
> I agree it would be a good idea to put forward a single alternative to IDNA
> for consideration ...
>
> Bill
>
> At 09:28 AM 5/25/01 -0700, Paul Hoffman / IMC wrote:
> >At 12:10 PM -0400 5/25/01, J. William Semich wrote:
> >>Paul - The opinions of the tiny subset of 36 members of this WG do not
> >>represent a "vast" majority of anything whatsoever in the truly vast set of
> >>multi-millions of Internet users, systems and application developers, and
> >>connectivity providers.
> >
> >So, what are you suggesting that we do instead? Because the IETF
> >cannot ever get the opinions of even 1% of all Internet users as we
> >develop new Internet protocols, are you saying we should just stop
> >working on them right now? If so, who do you propose should work on
> >Internet protocols? No other standards body polls any significant
> >percentage of Internet users before creating protocols, and no
> >private company does so before it creates its own proprietary
> >protocols. Are you saying that no more protocols should be developed
> >by anyone?
> >
> >--Paul Hoffman, Director
> >--Internet Mail Consortium
> >
> >
> Bill Semich
> President and Founder
> WorldNames, Inc.
> http://www.worldnames.net
> bsemich@worldnames.net
>




From owner-idn@ops.ietf.org  Fri May 25 14:03:47 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA22483
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 14:03:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153LYY-000BVr-00
	for idn-data@psg.com; Fri, 25 May 2001 10:39:22 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 153LYX-000BVl-00
	for idn@ops.ietf.org; Fri, 25 May 2001 10:39:21 -0700
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id KAA25693;
	Fri, 25 May 2001 10:39:19 -0700
Message-Id: <5.1.0.14.2.20010525103651.03a74048@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 25 May 2001 10:40:12 -0700
To: Bright Fulton <bright@alldomains.com>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] report of the straw poll
Cc: Paul Hoffman / IMC <phoffman@imc.org>, idn@ops.ietf.org
In-Reply-To: <Pine.GSO.3.96.1010525103031.16075C-100000@work.netcorps.co
 m>
References: <5.1.0.14.2.20010525095627.039fa698@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:34 AM 5/25/2001, Bright Fulton wrote:
>36 of 50 is 72%.  The other 28% was split.  Whether or not the poll was
>accurate, and whether or not the majority is right, there is a clear
>majority.

Every now and again, I seem to be demonstrate that knowing something about 
computer science does not mean that one is any good at all with 
numbers...  Sorry to have imposed that demonstration on the list.

I'll add that while I use 2/3 as a minimal measure, 3/4 is vastly 
preferred.  So, at best, we are in grey territory.

Anyhow, the fact that the disagreers are fragmented about the desired 
solution is not as significant as the fact that they are aligned in 
disagreeing.

That is why I'm suggesting trying to go through a sequence that steps 
toward a constructive group decision, based on a series of strategic 
concerns, starting with assessing group urgency.

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 May 25 14:08:50 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA22567
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 14:08:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153Li9-000Bij-00
	for idn-data@psg.com; Fri, 25 May 2001 10:49:17 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153Li8-000Bid-00
	for idn@ops.ietf.org; Fri, 25 May 2001 10:49:16 -0700
Received: from [165.227.249.18] (ip18.proper.com [165.227.249.18] (may be forged))
	by above.proper.com (8.9.3/8.9.3) with ESMTP id KAA19659
	for <idn@ops.ietf.org>; Fri, 25 May 2001 10:49:13 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100346b7344a771171@[165.227.249.18]>
In-Reply-To: <3.0.5.32.20010525130949.04c2ed10@mail.nic.nu>
References: <3.0.5.32.20010525121013.04c2f100@mail.nic.nu>
 <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca>
 <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca>
 <3.0.5.32.20010525121013.04c2f100@mail.nic.nu>
 <3.0.5.32.20010525130949.04c2ed10@mail.nic.nu>
Date: Fri, 25 May 2001 10:48:27 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] report of the straw poll
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 1:09 PM -0400 5/25/01, J. William Semich wrote:
>I think we should wrok harder to get consensus, that's all.

Ah! That's not what you said in the last message. Good to hear that 
you are interested in working towards consensus.

>  Among the 14
>are representatives of the interests of many millions of users, working all
>over the world with systems using established protocols based on UTF-8,
>etc.

Yes, and among the 36, there are also representatives of the 
interests of many millions of users, working all over the world with 
systems using established protocols based on UTF-8, etc. What does 
that have to do with achieving consensus?

>I agree it would be a good idea to put forward a single alternative to IDNA
>for consideration ...

Please note that I said a single Internet Draft. This mailing list 
discussion has been fruitful, but trying to nail down fruit is not 
useful in the long run.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Fri May 25 14:09:11 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA22581
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 14:09:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153Lpf-000Bx4-00
	for idn-data@psg.com; Fri, 25 May 2001 10:57:03 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153Lpe-000Bwt-00
	for idn@ops.ietf.org; Fri, 25 May 2001 10:57:02 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA00594;
        Fri, 25 May 2001 13:56:53 -0400 (EDT)
Message-Id: <200105251756.NAA00594@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: Keith Moore <moore@cs.utk.edu>,
        Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>, idn@ops.ietf.org
Subject: Re: [idn] report of the straw poll 
In-reply-to: Your message of "Fri, 25 May 2001 10:40:42 PDT."
             <3B0E991A.454DFECB@ehsco.com> 
Date: Fri, 25 May 2001 13:56:52 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > I'd be curious to know who would support idna-nameprep-ace in the
> > short term with the assurance that a native utf-8 query protocol
> > would be worked on after idna-nameprep-ace went out the door.
> 
> Can you turn that statement around and still be happy with it? Rather than
> saying, "we commit to do something better in the long term" can we say
> "ACE is the legacy interface component of XXXX long-term strategy"? IOW,
> can we define a long-term strategy that ACE plugs into?

I am not sure what is the appropriate long-term strategy for existing
applications.  I think it might be different for different applications,
that such strategies need to be worked out by the folks who are 
most familiar with those applications. And at least for some of those 
applications, the precise details of how the transformation would be
done are very important and should not be anticipated by the IDN group.

For the specific example of email I would be reluctant to support per-hop
negotiation of IDN capability, and more generally I would be reluctant
to support any per-hop negotiation which required MTAs to mung or translate
messages.  I think MTAs should in general relay mail as faithfully as 
possible from end to end without trying to anticipate what translations
are wanted by the recipients. OTOH, I might support a strategy that had 
sending UAs decide whether to generate UTF-8 or ACE addresses (on a 
per-recipient basis) based on the result of a rescap query for each 
recipient address.

Keith



From owner-idn@ops.ietf.org  Fri May 25 14:10:04 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA22601
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 14:10:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153LiR-000Bj2-00
	for idn-data@psg.com; Fri, 25 May 2001 10:49:35 -0700
Received: from femail2.sdc1.sfba.home.com ([24.0.95.82])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153LiQ-000Bio-00
	for idn@ops.ietf.org; Fri, 25 May 2001 10:49:34 -0700
Received: from c1340594a ([65.11.104.12]) by femail2.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP
          id <20010525174927.PNSG8481.femail2.sdc1.sfba.home.com@c1340594a>;
          Fri, 25 May 2001 10:49:27 -0700
Message-ID: <022e01c0e543$25648c90$0c680b41@c1340594a>
Reply-To: "Mark Davis" <mark@macchiato.com>
From: "Mark Davis" <markdavis34@home.com>
To: "Paul Hoffman / IMC" <phoffman@imc.org>, "Dave Crocker" <dhc@dcrocker.net>
Cc: <idn@ops.ietf.org>
References: <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca> <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca> <5.1.0.14.2.20010525095627.039fa698@dcrocker.net>
Subject: Re: [idn] report of the straw poll
Date: Fri, 25 May 2001 10:50:01 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

This is clearly urgent.

1) There is a vast pent-up demand for this, as evidenced by the number of
registrations at the Verisign test bed and other places. (I suspect that if
the English speakers on this list had been forced to write URLs with
Cyrillic characters all their lives, they would have more of a sense of
urgency also ;-)

2) The delay is just producing dozens of incompatible ad-hoc 'solutions',
all getting more and more entrenched. (From the outside, it does not appear
that the debate on this list has been particularly productive for some time,
in that there is little evidence of people changing their positions due to
the discussions.)

Mark

----- Original Message -----
From: "Dave Crocker" <dhc@dcrocker.net>
To: "Paul Hoffman / IMC" <phoffman@imc.org>
Cc: <idn@ops.ietf.org>
Sent: Friday, May 25, 2001 10:00
Subject: Re: [idn] report of the straw poll


> At 08:54 AM 5/25/2001, Paul Hoffman / IMC wrote:
> >The WG chair didn't seem to declare "rough consensus", unfortunately. The
> >poll showed one strongly-favored choice and a vast smattering of other
> >choices with none having even 10% of the support. Is
>
> Bill Semich's concern that 'yes' got only 36 votes has some appeal,
> although the normal IETF view is that we only consider the concerns and
> desires of those who show up.  We cannot guess the desires of people who
> did not participate in the straw poll.
>
> On the other hand, the 36 was less than 2/3 of the vote.  My personal
> approximation between "rough consensus" a percentage is not less than 2/3,
> because having 1/3 of a group disagree with a decision is simply too
strong
> a constituency to have unhappy.
>
> As to how to proceed, I wonder whether we should first resolve the
question
> of urgency.  Although it is beyond my comprehension, a number of people
> seem to believe that there is little urgency.  Perhaps we should assess
> working group view of urgency.  If there is consensus about urgency THEN
we
> can try to consider what solutions are amenable to quicker deployment.
>
> 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 May 25 16:13:16 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA24214
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 16:13:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153NVv-000EKv-00
	for idn-data@psg.com; Fri, 25 May 2001 12:44:47 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153NVu-000EKp-00
	for idn@ops.ietf.org; Fri, 25 May 2001 12:44:46 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA03303;
        Fri, 25 May 2001 15:44:34 -0400 (EDT)
Message-Id: <200105251944.PAA03303@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: Bright Fulton <bright@alldomains.com>,
        Paul Hoffman / IMC <phoffman@imc.org>, idn@ops.ietf.org
Subject: Re: [idn] report of the straw poll 
In-reply-to: Your message of "Fri, 25 May 2001 10:40:12 PDT."
             <5.1.0.14.2.20010525103651.03a74048@dcrocker.net> 
Date: Fri, 25 May 2001 15:44:34 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Anyhow, the fact that the disagreers are fragmented about the desired
> solution is not as significant as the fact that they are aligned in
> disagreeing.
> 
> That is why I'm suggesting trying to go through a sequence that steps
> toward a constructive group decision, based on a series of strategic
> concerns, starting with assessing group urgency.

and this is why I suggested that the group consider agreeing to work
on a native UTF-8 protocol, after getting IDNA out the door - as a
compromise for those who are concerned that we will be stuck with
ACE forever.  we can't go to utf8 everywhere immediately, but we can 
at least make it easier for new applications to use native utf-8,
and for old applications to migrate when they can work out the details.

Keith



From owner-idn@ops.ietf.org  Fri May 25 18:37:46 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA26506
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 18:37:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153PPd-000HZH-00
	for idn-data@psg.com; Fri, 25 May 2001 14:46:25 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 153PPc-000HZ9-00
	for idn@ops.ietf.org; Fri, 25 May 2001 14:46:24 -0700
Received: (qmail 29618 invoked by uid 1001); 25 May 2001 21:46:41 -0000
Date: 25 May 2001 21:46:41 -0000
Message-ID: <20010525214641.13168.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] report of the straw poll
References: <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca> <p05100336b7342f40ac9b@[165.227.249.18]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Paul Hoffman / IMC writes:
> a vast smattering of other choices with none having even 10% of the support.

In fact, several of those ``other choices'' were UTF-8; some of us
support UTF-8 but didn't list a choice in the poll; and we don't know
how many of the IDNA supporters also support UTF-8.

Bottom line: This poll was not presented to us as a measurement of UTF-8
support. It is thoroughly inappropriate for you to be using it that way.

> nameprep, which at this point is finished

No, it isn't, because it allows Beta, in violation of the nameprep-02
requirement that normalization ``must not introduce any chance that two
host names could be represented by two distinct strings of characters
that look identical to typical users.''

You seem to have removed that requirement without WG approval, but the
problem remains: you are allowing B and Beta in host names, normalized
to the distinct characters b and beta, even though B and Beta have
identical appearances in print.

---Dan



From owner-idn@ops.ietf.org  Fri May 25 20:33:53 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA27941
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 20:33:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153Rci-000JXD-00
	for idn-data@psg.com; Fri, 25 May 2001 17:08:04 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 153Rch-000JX6-00
	for idn@ops.ietf.org; Fri, 25 May 2001 17:08:03 -0700
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id RAA06626;
	Fri, 25 May 2001 17:07:55 -0700
Message-Id: <5.1.0.14.2.20010525164600.03b363e8@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 25 May 2001 16:48:21 -0700
To: Keith Moore <moore@cs.utk.edu>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] report of the straw poll 
Cc: Bright Fulton <bright@alldomains.com>,
        Paul Hoffman / IMC <phoffman@imc.org>, idn@ops.ietf.org
In-Reply-To: <200105251944.PAA03303@astro.cs.utk.edu>
References: <Your message of "Fri, 25 May 2001 10:40:12 PDT." <5.1.0.14.2.20010525103651.03a74048@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 12:44 PM 5/25/2001, Keith Moore wrote:
> > That is why I'm suggesting trying to go through a sequence that steps
> > toward a constructive group decision, based on a series of strategic
> > concerns, starting with assessing group urgency.
>
>and this is why I suggested that the group consider agreeing to work
>on a native UTF-8 protocol,

Keith,

There is massive distance between agreeing that a problem is urgent and 
agreeing that a particular technical path is the best solution.

Jumping to assert the correctness of a particular solution has proved 
problematic, here.  That is why I am suggesting a series of SMALL decision 
steps, starting with one that is focussed on the anture problem and not the 
solution.  Getting agreements about the problem are necessary before people 
can agree on the choice of solution.

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 May 25 20:36:49 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA27965
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 20:36:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153RoI-000Jce-00
	for idn-data@psg.com; Fri, 25 May 2001 17:20:02 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153RoG-000JcP-00
	for idn@ops.ietf.org; Fri, 25 May 2001 17:20: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 UAA06404;
        Fri, 25 May 2001 20:19:53 -0400 (EDT)
Message-Id: <200105260019.UAA06404@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: Keith Moore <moore@cs.utk.edu>, Bright Fulton <bright@alldomains.com>,
        Paul Hoffman / IMC <phoffman@imc.org>, idn@ops.ietf.org
Subject: Re: [idn] report of the straw poll 
In-reply-to: Your message of "Fri, 25 May 2001 16:48:21 PDT."
             <5.1.0.14.2.20010525164600.03b363e8@dcrocker.net> 
Date: Fri, 25 May 2001 20:19:53 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> There is massive distance between agreeing that a problem is urgent and
> agreeing that a particular technical path is the best solution.

no doubt.
 
> Jumping to assert the correctness of a particular solution has proved
> problematic, here.  

No doubt about that either.  But I don't think I've made any such assertions.

There is a point beyond which you're not likely to get any agreement on the
nature of the problem.  I think we reached that point several months ago.
There is likely to continue to be a gap between those who strongly feel
that we must provide the minimal possible disruption to the installed base
and those who strongly feel that we cannot afford to saddle everyone with
ASCII baggage forever.    Both views have merit, they simply reflect different
kinds of experience.  But there's no way to establish for certain which path 
is better.

Fortunately we really don't have to have concensus on the nature of the 
problem in order to make progress.  All we have to do is get consensus
on a solution, or at this point, on a strategy for moving forward.  We 
don't have to have consensus on the reason for choosing that strategy.

Keith



From owner-idn@ops.ietf.org  Fri May 25 20:55:17 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA28082
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 20:55:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153S8K-000JnQ-00
	for idn-data@psg.com; Fri, 25 May 2001 17:40:44 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 153S8J-000JnJ-00
	for idn@ops.ietf.org; Fri, 25 May 2001 17:40:43 -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 RAA07667;
	Fri, 25 May 2001 17:40:39 -0700
Message-Id: <5.1.0.14.2.20010525173612.0275bbb0@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 25 May 2001 17:38:41 -0700
To: Keith Moore <moore@cs.utk.edu>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] report of the straw poll 
Cc: Keith Moore <moore@cs.utk.edu>, Bright Fulton <bright@alldomains.com>,
        Paul Hoffman / IMC <phoffman@imc.org>, idn@ops.ietf.org
In-Reply-To: <200105260019.UAA06404@astro.cs.utk.edu>
References: <Your message of "Fri, 25 May 2001 16:48:21 PDT." <5.1.0.14.2.20010525164600.03b363e8@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 05:19 PM 5/25/2001, Keith Moore wrote:
> > Jumping to assert the correctness of a particular solution has proved
> > problematic, here.
>
>No doubt about that either.  But I don't think I've made any such assertions.

Unfortunately, that is exactly what you did.  Re-read the way you asserted 
a particular solution.


>There is a point beyond which you're not likely to get any agreement on the
>nature of the problem.  I think we reached that point several months ago.

I thought we did, too, but the fact that there is lack of clarity about the 
sense of urgency was a rather surprising suggestion that that we have NOT 
reached that point.

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 May 25 21:14:31 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA28242
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 21:14:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153SKl-000JsW-00
	for idn-data@psg.com; Fri, 25 May 2001 17:53:35 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153SKk-000JsQ-00
	for idn@ops.ietf.org; Fri, 25 May 2001 17:53:34 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id UAA10957;
        Fri, 25 May 2001 20:53:28 -0400 (EDT)
Message-Id: <200105260053.UAA10957@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: Keith Moore <moore@cs.utk.edu>, Bright Fulton <bright@alldomains.com>,
        Paul Hoffman / IMC <phoffman@imc.org>, idn@ops.ietf.org
Subject: Re: [idn] report of the straw poll 
In-reply-to: Your message of "Fri, 25 May 2001 17:38:41 PDT."
             <5.1.0.14.2.20010525173612.0275bbb0@dcrocker.net> 
Date: Fri, 25 May 2001 20:53:28 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > > Jumping to assert the correctness of a particular solution has proved
> > > problematic, here.
> >
> >No doubt about that either.  But I don't think I've made any such assertions.
> 
> Unfortunately, that is exactly what you did.  Re-read the way you asserted
> a particular solution.

Dave, you might or might not agree with the plan of action I proposed,
but I don't see how it's helpful for you to question my intent.  Nor do
I see how it's helpful for us to argue about whether I've asserted "a 
correct solution", asserted "a solution", or merely suggested a way 
forward.  So let's just drop it.

> >There is a point beyond which you're not likely to get any agreement on the
> >nature of the problem.  I think we reached that point several months ago.
> 
> I thought we did, too, but the fact that there is lack of clarity about the
> sense of urgency was a rather surprising suggestion that that we have NOT
> reached that point.

Even though I happen to think that our window of opportunity for doing
anything useful is fast disappearing, I'm not going to get hung up on 
whether other people feel a sense of urgency - because I believe that 
trying to convince people that there's a sense of urgency will take 
too long.  Just like any other factor, the urgency is more visible to 
some people than others.

Keith



From owner-idn@ops.ietf.org  Fri May 25 23:25:39 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA01183
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 23:25:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153UUX-000Kll-00
	for idn-data@psg.com; Fri, 25 May 2001 20:11:49 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153UUV-000Klf-00
	for idn@ops.ietf.org; Fri, 25 May 2001 20:11:47 -0700
Received: from jamessonyvaio (58alpha078.singnet.com.sg [165.21.208.88])
	by mail.i-dns.net (Postfix) with SMTP
	id D8D5DFFC01; Sat, 26 May 2001 11:14:18 +0800 (SGT)
Message-ID: <00b601c0e591$7f147680$7dcb15a5@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Mark Davis" <mark@macchiato.com>, "Paul Hoffman / IMC" <phoffman@imc.org>,
        "Dave Crocker" <dhc@dcrocker.net>
Cc: <idn@ops.ietf.org>
References: <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca> <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca> <5.1.0.14.2.20010525095627.039fa698@dcrocker.net> <022e01c0e543$25648c90$0c680b41@c1340594a>
Subject: Re: [idn] report of the straw poll
Date: Sat, 26 May 2001 11:11:01 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

To add another point, which we may/may not want to consider valid:

Verisign is moving ahead to put RACE into their .COM zone would means
wide deployment of RACE and also applications (or servers) to be
developed to support resolutions. They may or may not be IDNA or even
close to the what we like to be.

But the fact that this is happening is somewhat of a concern as it may
undermine the work we are doing in this Working Group as it *might* lead
to an industry driven protocol.

-James Seng

----- Original Message -----
From: "Mark Davis" <markdavis34@home.com>
To: "Paul Hoffman / IMC" <phoffman@imc.org>; "Dave Crocker"
<dhc@dcrocker.net>
Cc: <idn@ops.ietf.org>
Sent: Saturday, May 26, 2001 1:50 AM
Subject: Re: [idn] report of the straw poll


> This is clearly urgent.
>
> 1) There is a vast pent-up demand for this, as evidenced by the number
of
> registrations at the Verisign test bed and other places. (I suspect
that if
> the English speakers on this list had been forced to write URLs with
> Cyrillic characters all their lives, they would have more of a sense
of
> urgency also ;-)
>
> 2) The delay is just producing dozens of incompatible ad-hoc
'solutions',
> all getting more and more entrenched. (From the outside, it does not
appear
> that the debate on this list has been particularly productive for some
time,
> in that there is little evidence of people changing their positions
due to
> the discussions.)
>
> Mark
>
> ----- Original Message -----
> From: "Dave Crocker" <dhc@dcrocker.net>
> To: "Paul Hoffman / IMC" <phoffman@imc.org>
> Cc: <idn@ops.ietf.org>
> Sent: Friday, May 25, 2001 10:00
> Subject: Re: [idn] report of the straw poll
>
>
> > At 08:54 AM 5/25/2001, Paul Hoffman / IMC wrote:
> > >The WG chair didn't seem to declare "rough consensus",
unfortunately. The
> > >poll showed one strongly-favored choice and a vast smattering of
other
> > >choices with none having even 10% of the support. Is
> >
> > Bill Semich's concern that 'yes' got only 36 votes has some appeal,
> > although the normal IETF view is that we only consider the concerns
and
> > desires of those who show up.  We cannot guess the desires of people
who
> > did not participate in the straw poll.
> >
> > On the other hand, the 36 was less than 2/3 of the vote.  My
personal
> > approximation between "rough consensus" a percentage is not less
than 2/3,
> > because having 1/3 of a group disagree with a decision is simply too
> strong
> > a constituency to have unhappy.
> >
> > As to how to proceed, I wonder whether we should first resolve the
> question
> > of urgency.  Although it is beyond my comprehension, a number of
people
> > seem to believe that there is little urgency.  Perhaps we should
assess
> > working group view of urgency.  If there is consensus about urgency
THEN
> we
> > can try to consider what solutions are amenable to quicker
deployment.
> >
> > 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 May 25 23:30:01 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA01203
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 23:29:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153UZR-000Kzv-00
	for idn-data@psg.com; Fri, 25 May 2001 20:16:53 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153UZQ-000Kzp-00
	for idn@ops.ietf.org; Fri, 25 May 2001 20:16:52 -0700
Received: from jamessonyvaio (58alpha078.singnet.com.sg [165.21.208.88])
	by mail.i-dns.net (Postfix) with SMTP
	id D9539FFC01; Sat, 26 May 2001 11:19:28 +0800 (SGT)
Message-ID: <010101c0e592$37c00190$7dcb15a5@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Bright Fulton" <bright@alldomains.com>, "Dave Crocker" <dhc@dcrocker.net>
Cc: "Paul Hoffman / IMC" <phoffman@imc.org>, <idn@ops.ietf.org>
References: <Pine.GSO.3.96.1010525103031.16075C-100000@work.netcorps.com>
Subject: Re: [idn] report of the straw poll
Date: Sat, 26 May 2001 11:16:08 +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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

If we count the 14 who disagree with IDNA and suggested their own
Internet Draft instead, then ...

-James Seng

----- Original Message -----
From: "Bright Fulton" <bright@alldomains.com>
To: "Dave Crocker" <dhc@dcrocker.net>
Cc: "Paul Hoffman / IMC" <phoffman@imc.org>; <idn@ops.ietf.org>
Sent: Saturday, May 26, 2001 1:34 AM
Subject: Re: [idn] report of the straw poll


> 36 of 50 is 72%.  The other 28% was split.  Whether or not the poll
was
> accurate, and whether or not the majority is right, there is a clear
> majority.
>
> Bright
>
>
> On Fri, 25 May 2001, Dave Crocker wrote:
>
> > At 08:54 AM 5/25/2001, Paul Hoffman / IMC wrote:
> > >The WG chair didn't seem to declare "rough consensus",
unfortunately. The
> > >poll showed one strongly-favored choice and a vast smattering of
other
> > >choices with none having even 10% of the support. Is
> >
> > Bill Semich's concern that 'yes' got only 36 votes has some appeal,
> > although the normal IETF view is that we only consider the concerns
and
> > desires of those who show up.  We cannot guess the desires of people
who
> > did not participate in the straw poll.
> >
> > On the other hand, the 36 was less than 2/3 of the vote.  My
personal
> > approximation between "rough consensus" a percentage is not less
than 2/3,
> > because having 1/3 of a group disagree with a decision is simply too
strong
> > a constituency to have unhappy.
> >
> > As to how to proceed, I wonder whether we should first resolve the
question
> > of urgency.  Although it is beyond my comprehension, a number of
people
> > seem to believe that there is little urgency.  Perhaps we should
assess
> > working group view of urgency.  If there is consensus about urgency
THEN we
> > can try to consider what solutions are amenable to quicker
deployment.
> >
> > 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 May 25 23:36:15 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA01610
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 23:36:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153Uif-000LIK-00
	for idn-data@psg.com; Fri, 25 May 2001 20:26:25 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153Uie-000LI8-00
	for idn@ops.ietf.org; Fri, 25 May 2001 20:26:24 -0700
Received: from [165.227.249.18] (ip18.proper.com [165.227.249.18] (may be forged))
	by above.proper.com (8.9.3/8.9.3) with ESMTP id UAA22972
	for <idn@ops.ietf.org>; Fri, 25 May 2001 20:26:19 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100308b734d15ae424@[165.227.249.18]>
In-Reply-To: <00b601c0e591$7f147680$7dcb15a5@jamessonyvaio>
References: <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca>
 <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca>
 <5.1.0.14.2.20010525095627.039fa698@dcrocker.net>
 <022e01c0e543$25648c90$0c680b41@c1340594a>
 <00b601c0e591$7f147680$7dcb15a5@jamessonyvaio>
Date: Fri, 25 May 2001 20:25:27 -0700
To: <idn@ops.ietf.org>
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] report of the straw poll
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 11:11 AM +0800 5/26/01, James Seng/Personal wrote:
>Verisign is moving ahead to put RACE into their .COM zone would means
>wide deployment of RACE and also applications (or servers) to be
>developed to support resolutions. They may or may not be IDNA or even
>close to the what we like to be.

VGRS *might* put RACE into the .com zone, or they might do the more 
rational thing and wait for the ACE Design Team's report. It is not 
appropriate to say what VGRS will or will not do in the future; that 
changes all the time.

Section C of Appendix K of the agreement between VGRS and ICANN 
reserves all RACE names for ICANN; VGRS needs permission before they 
can add them to the TLDs.

Why is any of this relevant to the straw poll?

>But the fact that this is happening is somewhat of a concern as it may
>undermine the work we are doing in this Working Group as it *might* lead
>to an industry driven protocol.

Or it might not.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Fri May 25 23:41:00 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA01646
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 23:40:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153UnR-000LSe-00
	for idn-data@psg.com; Fri, 25 May 2001 20:31:21 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153UnQ-000LSX-00
	for idn@ops.ietf.org; Fri, 25 May 2001 20:31:20 -0700
Received: from jamessonyvaio (58alpha078.singnet.com.sg [165.21.208.88])
	by mail.i-dns.net (Postfix) with SMTP
	id C7FE7FFC01; Sat, 26 May 2001 11:33:56 +0800 (SGT)
Message-ID: <01d001c0e594$3cea1c30$7dcb15a5@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Eric A. Hall" <ehall@ehsco.com>
Cc: <idn@ops.ietf.org>
References: <4.2.0.58.J.20010524223716.02fe5100@sh.w3.mag.keio.ac.jp> <3B0DD39F.515161DD@ehsco.com> <20010525035948.28153.qmail@cr.yp.to> <3B0DE15D.752FBECA@ehsco.com> <3B0DE44A.4C0462B2@ehsco.com> <4.2.0.58.J.20010524223716.02fe5100@sh.w3.mag.keio.ac.jp> <3B0DD39F.515161DD@ehsco.com> <20010525035948.28153.qmail@cr.yp.to> <3B0DE15D.752FBECA@ehsco.com> <20010525142912.23844.qmail@cr.yp.to> <3B0E91F9.3415113A@ehsco.com>
Subject: Re: [idn] Why we can go directly to UTF-8
Date: Sat, 26 May 2001 11:30:39 +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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

If you need a UTF-8 example, please try this: å®žéªŒ.cr.yp.to

-James Seng

----- Original Message -----
From: "Eric A. Hall" <ehall@ehsco.com>
Cc: <idn@ops.ietf.org>
Sent: Saturday, May 26, 2001 1:10 AM
Subject: Re: [idn] Why we can go directly to UTF-8


>
> "D. J. Bernstein" wrote:
>
> > Your memories are so vague that you can't even tell us what programs
> > you were using---but you're confident that those programs would have
> > trouble with UTF-8, and you're making major decisions on this basis.
>
> Feel free to rename your domain to _test_.cr.yp.to. and report back
with
> your success. Since I already know what will happen, I won't bother.
>
> --
> Eric A. Hall
http://www.ehsco.com/
> Internet Core Protocols
http://www.oreilly.com/catalog/coreprot/
>




From owner-idn@ops.ietf.org  Fri May 25 23:48:41 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA01739
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 23:48:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153UvO-000LWv-00
	for idn-data@psg.com; Fri, 25 May 2001 20:39:34 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153UvL-000LWk-00
	for idn@ops.ietf.org; Fri, 25 May 2001 20:39:31 -0700
Received: from jamessonyvaio (58alpha078.singnet.com.sg [165.21.208.88])
	by mail.i-dns.net (Postfix) with SMTP
	id DB4C8FFC01; Sat, 26 May 2001 11:42:07 +0800 (SGT)
Message-ID: <01f001c0e595$619e5c70$7dcb15a5@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: <idn@ops.ietf.org>, "Paul Hoffman / IMC" <phoffman@imc.org>
References: <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca> <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca> <5.1.0.14.2.20010525095627.039fa698@dcrocker.net> <022e01c0e543$25648c90$0c680b41@c1340594a> <00b601c0e591$7f147680$7dcb15a5@jamessonyvaio> <p05100308b734d15ae424@[165.227.249.18]>
Subject: Verisign Testbed (was Re: [idn] report of the straw poll)
Date: Sat, 26 May 2001 11:38:50 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Section C of Appendix K of the agreement between VGRS and ICANN
> reserves all RACE names for ICANN; VGRS needs permission before they
> can add them to the TLDs.
>
> Why is any of this relevant to the straw poll?

Nope, of course it is not. It may not even be relevant to the work we do
here since it is a commerical testbed and we should not let it drive our
work. But still, it is unnerving.

OTOH, it is comforting to know there is a "Section C of Appendix K" of
some agreement which bind them. :-) I am obviously not a lawyer so I
have to presume it is air-tied (unlike the one they did in 98).

Anyhow, it is a side-topic which as we agree it may not be relevant. Let
not dwell on this.

-James Seng




From owner-idn@ops.ietf.org  Fri May 25 23:50:48 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA01764
	for <idn-archive@lists.ietf.org>; Fri, 25 May 2001 23:50:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153Uxa-000LZ2-00
	for idn-data@psg.com; Fri, 25 May 2001 20:41:50 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153UxY-000LYt-00
	for idn@ops.ietf.org; Fri, 25 May 2001 20:41:49 -0700
Received: from jamessonyvaio (58alpha078.singnet.com.sg [165.21.208.88])
	by mail.i-dns.net (Postfix) with SMTP
	id BADA3FFC04; Sat, 26 May 2001 11:44:25 +0800 (SGT)
Message-ID: <01fb01c0e595$b3d60790$7dcb15a5@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "James Seng/Personal" <James@Seng.cc>, "Eric A. Hall" <ehall@ehsco.com>
Cc: <idn@ops.ietf.org>
References: <4.2.0.58.J.20010524223716.02fe5100@sh.w3.mag.keio.ac.jp> <3B0DD39F.515161DD@ehsco.com> <20010525035948.28153.qmail@cr.yp.to> <3B0DE15D.752FBECA@ehsco.com> <3B0DE44A.4C0462B2@ehsco.com> <4.2.0.58.J.20010524223716.02fe5100@sh.w3.mag.keio.ac.jp> <3B0DD39F.515161DD@ehsco.com> <20010525035948.28153.qmail@cr.yp.to> <3B0DE15D.752FBECA@ehsco.com> <20010525142912.23844.qmail@cr.yp.to> <3B0E91F9.3415113A@ehsco.com> <01d001c0e594$3cea1c30$7dcb15a5@jamessonyvaio>
Subject: Re: [idn] Why we can go directly to UTF-8
Date: Sat, 26 May 2001 11:41:08 +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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Sometimes, people think I spoken broken English with my bad grammers and
spelling which I only caught after I send out. The fact is that it
happens with me in Chinese too!

s/å®žéªŒ/è¯•éªŒ/

-James Seng

----- Original Message -----
From: "James Seng/Personal" <James@seng.cc>
To: "Eric A. Hall" <ehall@ehsco.com>
Cc: <idn@ops.ietf.org>
Sent: Saturday, May 26, 2001 11:30 AM
Subject: Re: [idn] Why we can go directly to UTF-8


> If you need a UTF-8 example, please try this: å®žéªŒ.cr.yp.to
>
> -James Seng
>
> ----- Original Message -----
> From: "Eric A. Hall" <ehall@ehsco.com>
> Cc: <idn@ops.ietf.org>
> Sent: Saturday, May 26, 2001 1:10 AM
> Subject: Re: [idn] Why we can go directly to UTF-8
>
>
> >
> > "D. J. Bernstein" wrote:
> >
> > > Your memories are so vague that you can't even tell us what
programs
> > > you were using---but you're confident that those programs would
have
> > > trouble with UTF-8, and you're making major decisions on this
basis.
> >
> > Feel free to rename your domain to _test_.cr.yp.to. and report back
> with
> > your success. Since I already know what will happen, I won't bother.
> >
> > --
> > Eric A. Hall
> http://www.ehsco.com/
> > Internet Core Protocols
> http://www.oreilly.com/catalog/coreprot/
> >
>
>




From owner-idn@ops.ietf.org  Sat May 26 01:40:53 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA04087
	for <idn-archive@lists.ietf.org>; Sat, 26 May 2001 01:40:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153WIl-000Lyq-00
	for idn-data@psg.com; Fri, 25 May 2001 22:07:47 -0700
Received: from ibd.ar.com ([63.194.205.75])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153WIk-000Lyk-00
	for idn@ops.ietf.org; Fri, 25 May 2001 22:07:46 -0700
Received: from loki (wessorh@loki.ar.com [10.10.10.88])
	by ibd.ar.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id WAA07770;
	Fri, 25 May 2001 22:05:58 -0700 (PDT)
Date: Fri, 25 May 2001 22:07:42 -0700 (PDT)
From: Rick H Wesson <wessorh@ar.com>
To: James Seng/Personal <James@Seng.cc>
cc: Mark Davis <mark@macchiato.com>, Paul Hoffman / IMC <phoffman@imc.org>,
        Dave Crocker <dhc@dcrocker.net>, <idn@ops.ietf.org>
Subject: Re: [idn] report of the straw poll
In-Reply-To: <00b601c0e591$7f147680$7dcb15a5@jamessonyvaio>
Message-ID: <Pine.LNX.4.30.0105252206160.409-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


It looks like we have a 3 week reprieve on RACE going into .com.

> To All IDN Registrars:
>
> Based upon recommendations from ICANN, VeriSign GRS is delaying the
> start of Resolution Phase 3.3 for three weeks.  The deployment date
> for Resolution Phase 3.3 is now scheduled for June 19, 2001.
> VeriSign GRS regrets the lateness of this notification.

-rick


On Sat, 26 May 2001, James Seng/Personal wrote:

> To add another point, which we may/may not want to consider valid:
>
> Verisign is moving ahead to put RACE into their .COM zone would means
> wide deployment of RACE and also applications (or servers) to be
> developed to support resolutions. They may or may not be IDNA or even
> close to the what we like to be.
>
> But the fact that this is happening is somewhat of a concern as it may
> undermine the work we are doing in this Working Group as it *might* lead
> to an industry driven protocol.
>
> -James Seng
>
> ----- Original Message -----
> From: "Mark Davis" <markdavis34@home.com>
> To: "Paul Hoffman / IMC" <phoffman@imc.org>; "Dave Crocker"
> <dhc@dcrocker.net>
> Cc: <idn@ops.ietf.org>
> Sent: Saturday, May 26, 2001 1:50 AM
> Subject: Re: [idn] report of the straw poll
>
>
> > This is clearly urgent.
> >
> > 1) There is a vast pent-up demand for this, as evidenced by the number
> of
> > registrations at the Verisign test bed and other places. (I suspect
> that if
> > the English speakers on this list had been forced to write URLs with
> > Cyrillic characters all their lives, they would have more of a sense
> of
> > urgency also ;-)
> >
> > 2) The delay is just producing dozens of incompatible ad-hoc
> 'solutions',
> > all getting more and more entrenched. (From the outside, it does not
> appear
> > that the debate on this list has been particularly productive for some
> time,
> > in that there is little evidence of people changing their positions
> due to
> > the discussions.)
> >
> > Mark
> >
> > ----- Original Message -----
> > From: "Dave Crocker" <dhc@dcrocker.net>
> > To: "Paul Hoffman / IMC" <phoffman@imc.org>
> > Cc: <idn@ops.ietf.org>
> > Sent: Friday, May 25, 2001 10:00
> > Subject: Re: [idn] report of the straw poll
> >
> >
> > > At 08:54 AM 5/25/2001, Paul Hoffman / IMC wrote:
> > > >The WG chair didn't seem to declare "rough consensus",
> unfortunately. The
> > > >poll showed one strongly-favored choice and a vast smattering of
> other
> > > >choices with none having even 10% of the support. Is
> > >
> > > Bill Semich's concern that 'yes' got only 36 votes has some appeal,
> > > although the normal IETF view is that we only consider the concerns
> and
> > > desires of those who show up.  We cannot guess the desires of people
> who
> > > did not participate in the straw poll.
> > >
> > > On the other hand, the 36 was less than 2/3 of the vote.  My
> personal
> > > approximation between "rough consensus" a percentage is not less
> than 2/3,
> > > because having 1/3 of a group disagree with a decision is simply too
> > strong
> > > a constituency to have unhappy.
> > >
> > > As to how to proceed, I wonder whether we should first resolve the
> > question
> > > of urgency.  Although it is beyond my comprehension, a number of
> people
> > > seem to believe that there is little urgency.  Perhaps we should
> assess
> > > working group view of urgency.  If there is consensus about urgency
> THEN
> > we
> > > can try to consider what solutions are amenable to quicker
> deployment.
> > >
> > > 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 May 26 01:40:58 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA04106
	for <idn-archive@lists.ietf.org>; Sat, 26 May 2001 01:40:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153WSt-000M1l-00
	for idn-data@psg.com; Fri, 25 May 2001 22:18:15 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 153WSs-000M1f-00
	for idn@ops.ietf.org; Fri, 25 May 2001 22:18:14 -0700
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id WAA16360;
	Fri, 25 May 2001 22:18:09 -0700
Message-Id: <5.1.0.14.2.20010525221602.03a34c28@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 25 May 2001 22:18:17 -0700
To: Keith Moore <moore@cs.utk.edu>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] report of the straw poll 
Cc: Keith Moore <moore@cs.utk.edu>, Bright Fulton <bright@alldomains.com>,
        Paul Hoffman / IMC <phoffman@imc.org>, idn@ops.ietf.org
In-Reply-To: <200105260053.UAA10957@astro.cs.utk.edu>
References: <Your message of "Fri, 25 May 2001 17:38:41 PDT." <5.1.0.14.2.20010525173612.0275bbb0@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 05:53 PM 5/25/2001, Keith Moore wrote:
>Dave, you might or might not agree with the plan of action I proposed,
>but I don't see how it's helpful for you to question my intent.  Nor do

It was not your intent, it was your action.

The reason that I responded to your note was that I was (and am) suggesting 
that the way to reach a solution is to pursue a series of small steps.

Your note was phrased in a way that made it easy to think it was intended 
to be related to my suggestion, though it was not.  I therefore wanted to 
make sure that no one thought it was.

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 May 26 05:14:40 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA17390
	for <idn-archive@lists.ietf.org>; Sat, 26 May 2001 05:14:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153ZwV-000Nx4-00
	for idn-data@psg.com; Sat, 26 May 2001 02:01:03 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 153ZwT-000Nwy-00
	for idn@ops.ietf.org; Sat, 26 May 2001 02:01:02 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4Q90Wf84779
	for <idn@ops.ietf.org>; Sat, 26 May 2001 05:00:32 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105260900.f4Q90Wf84779@nic-naa.net>
To: idn@ops.ietf.org
Subject: Re: [idn] report of the straw poll
Date: Sat, 26 May 2001 05:00:32 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> I'd be curious to know who would support idna-nameprep-ace in the
> short term with the assurance that a native utf-8 query protocol
> would be worked on after idna-nameprep-ace went out the door.

utf8-on-the-wire has been a third-rail of IETF DNS politics for some
time. I'm unable to discern any modification of this, and can't imagine
who could provide assurance to whom.

Eric



From owner-idn@ops.ietf.org  Sat May 26 05:58:58 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA17526
	for <idn-archive@lists.ietf.org>; Sat, 26 May 2001 05:58:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153aYl-000OMo-00
	for idn-data@psg.com; Sat, 26 May 2001 02:40:35 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153aYk-000OMg-00
	for idn@ops.ietf.org; Sat, 26 May 2001 02:40:34 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH9bcopsRQlWgXvvXWI+ti4qVhJS+Nt83lA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id F6CWB3KB; Sat, 26 May 2001 05:40:01 EDT
To: mark@macchiato.com
Cc: idn@ops.ietf.org
Date: Sat, 26 May 2001 02:52:34 -0700
Subject: Re: [idn] Working direction of IDN
Message-ID: <20010526.025307.-762217.0.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.5
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 1-3,5,7,9-19,21-243
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 if we can come up with and agree to use a basicaly *one*
representation
 for the same sequence of characters using the same language label?

>Early in Unicode's history, we looked at the possibility of encoding
Chinese
> characters in this way. This approach requires the use of variable
numbers
> of code points to represent Chinese characters, and that unless far
more
> than 1000 base characters used, the lengths of the sequences can get 
> quite long.

Often used sequences can be short and likely to be used as IDN, the long 
ones are stored as text files, only program needs to deal with them.  
Can you accept this type of variable number of code points? 

Liana Ye


On Fri, 25 May 2001 07:16:15 -0700 "Mark Davis" <markdavis34@home.com>
writes:
> I'm sorry, I don't really understand your point.
> 
> We recognize that additional characters are in use, and the national
> governments of these countries are continuing to encode more 
> characters in
> the IRG. However, the frequency of use of those characters is 
> *extremely*
> low, and does not prevent the successful deployment of Unicode/10646
> solutions for CJK characters. (For example, anyone using Microsoft 
> Office
> for Japanese, Chinese or Korean is already using Unicode 
> internally).
> 
> When you say "language-based script", I was guessing that you are in 
> favor
> of encoding different national standards for encoding Chinese 
> characters.
> There are huge disadvantages to the approach of using different 
> encodings,
> in that there would be *many* different representations for the same
> sequence of characters.
> 
> While theoretically one could have mapping tables between these 
> sequences,
> in practice every platform's mappings differs from the others. Even 
> when you
> think that you are using the same charset, on different platforms 
> you will
> get different conversions: that means that you will get data 
> corruption
> problems. (For example, in IBM we have collected over 700 unique 
> character
> conversion mappings that we have found on different platforms -- see
> http://oss.software.ibm.com/cvs/icu/charset/data/xml/).
> 
> However, the last part of your message seems to indicate that you 
> don't want
> a national standard, but instead want to use some new system that 
> uses
> decomposition of Chinese characters. While Unicode/10646 does 
> provide a way
> to *describe* characters via such a mechanism (see Ideographic 
> Description
> Characters in the Unicode Standard), it is not recommended for 
> encoding
> Chinese characters.
> 
> Early in Unicode's history, we looked at the possibility of encoding 
> Chinese
> characters in this way. This approach requires the use of variable 
> numbers
> of code points to represent Chinese characters, and that unless far 
> more
> than 1000 base characters used, the lengths of the sequences can get 
> quite
> long.
> 
> If you are interested in further discussion of this topic, I'd 
> suggest you
> contact some of the experts in the IRG.
> 
> Mark
> 
> ----- Original Message -----
> From: <liana.ydisg@juno.com>
> To: <mark@macchiato.com>
> Cc: <idn@ops.ietf.org>; <liana.ydisg@juno.com>
> Sent: Thursday, May 24, 2001 13:23
> Subject: Re: [idn] Working direction of IDN
> 
> 
> > You have addressed the very problem of using ISO 10646 / Unicode 
> as day
> > to day
> > information/samantic processing of CJK characters.  There is no 
> single
> > expert who
> > would use all of the characters in the set, why do we care to 
> carry so
> > many characters
> > in our register?  However, there are sparse needs for the 
> characters,
> > which
> > the computer does well for human beings.  That is an argument for 
> a
> > language
> > based script to be coded as IDN names.
> >
> > Besides, there are studies from China in the 80's, that about 1000
> > frequently used Chinese characters which are composed into the 
> larger
> > set
> > of Chinese characters.
> >
> > Liana Ye
> >
> >
> > On Thu, 24 May 2001 06:51:25 -0700 "Mark Davis" 
> <markdavis34@home.com>
> > writes:
> > > There is a lot of misinformation floating around about the 
> support of
> > > Chinese, Japanese and Korean characters. ISO 10646 / Unicode
> > > supports over
> > > 70,000 Chinese characters right now, and work is underway to 
> encode
> > > further
> > > sets. It has the same repertoire as the Chinese GB18030 and GB
> > > 13000.
> > >
> > > This work is being done by the IRG, which includes 
> representatives
> > > of the
> > > governments of China, Hong Kong, Singapore, Japan, South Korea,
> > > North Korea,
> > > Taiwan and Vietnam, plus a representative from the Unicode
> > > consortium (cf
> > > http://www.info.gov.hk/digital21/eng/structure/intro_irg.html).
> > >
> > > This group is very careful cataloging, reviewing, and assessing
> > > Chinese
> > > characters for inclusion into the standard. The only real 
> limitation
> > > on the
> > > number of Chinese characters in the standard is the ability of 
> this
> > > group to
> > > process them, because the characters are increasingly obscure 
> (no
> > > person
> > > knows more than a fraction of the set already encoded).
> > >
> > > Mark
> > >
> > > ----- Original Message -----
> > > From: <liana.ydisg@juno.com>
> > > To: <idn@ops.ietf.org>
> > > Cc: <liana.ydisg@juno.com>
> > > Sent: Wednesday, May 23, 2001 23:16
> > > Subject: [idn] Working direction of IDN
> > >
> > >
> > > > All:
> > > >
> > > > Answer to James Seng's comment:
> > > >
> > > > >Correct me if I am wrong...from your email, you are 
> suggesting
> > > that IDN
> > > > >to be encoded in a strings based on its symbols which makes 
> up
> > > the
> > > > >script. While this is an intriguing thought, unfortunately, I 
> do
> > > not
> > > > >think we have sufficient work done in that direction.
> > > >
> > > > >Our current works basically resolves using ISO10646 as a 
> basis
> > > for
> > > > >encoding names. Whatever limitation ISO10646 has, it is
> > > improving.
> > > >
> > > > I am suggesting that IDN to be encoded in a strings based on 
> its
> > > symbols
> > > > which makes up the script.
> > > >
> > > > Although IDN has no need to concern with trademarks at this 
> time,
> > > it is
> > > > the idn limitation to support only [ISO10646] bothers me.
> > > [ISO10646]
> > > > does not support all Chinese characters, since Chinese 
> character
> > > set has
> > > > more than 100,000 characters already.  There are cases that we 
> can
> > > not
> > > > find a live person's name on our current computers, don't  
> mention
> > > the
> > > > dead ones.  At the speed of computer and network development, 
> when
> > > the
> > > > applications catch up with us, millions of more data going to 
> be
> > > on the
> > > > net for accessing.  Are we going to revamp our idn again?  I 
> can
> > > suggest
> > > > an ACE using a recursive rule to handle any symbols that are 
> not
> > > possible
> > > > to be simply folded onto ASCII character set.  Such an ACE 
> creats
> > > a
> > > > virtue character set, which is possible
> > > >  to include any characters or icons requested by a user, as 
> long
> > > as that
> > > > icon has been encoded by an ACE somewhere on the net.  When 
> the
> > > IDN can
> > > > take more than 63 octets or v6 or v8, the ACE can follow 
> without
> > > > troubling the users.  Let alone the idea to send Unicode down 
> to
> > > the
> > > > wire.  It is not user friendly, it is make no sense for the
> > > tradename
> > > > servers.
> > > >
> > > > Liana Ye
> > > >
> > >
> >
> >
> >
> >
> 
> 



From owner-idn@ops.ietf.org  Sat May 26 06:28:47 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA17648
	for <idn-archive@lists.ietf.org>; Sat, 26 May 2001 06:28:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153b0s-000Obr-00
	for idn-data@psg.com; Sat, 26 May 2001 03:09:38 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153b0r-000ObG-00
	for idn@ops.ietf.org; Sat, 26 May 2001 03:09:37 -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 f4QA9XI11094 for <idn@ops.ietf.org>; Sat, 26 May 2001 12:09:34 +0200 (MEST)
Message-Id: <200105261009.f4QA9XI11094@malmo.trab.se>
Date: Sat, 26 May 2001 12:09:31 +0200 (MEST)
From: Dan <Dan.Oscarsson@trab.se>
Reply-To: Dan <Dan.Oscarsson@trab.se>
Subject: [idn] Let's go forward with IDNA and UTF-8
To: idn@ops.ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: /S0fGjFKHQj6veAMpVizRQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk


From all the discussion on the list I can see two major directions
for non-ASCII names in DNS: use ACE (in application) and use UTF-8.

The people saying ACE/IDNA say it is quickest and least disruptive
to non-IDN aware software. Those wanting UTF-8 thinks this format
is best for internationalisation and fear that starting with IDNA
will result in ACE forever.

I have for a long time wanted UTF-8 but realise that we probably
must use ACE for backward compatiblity.
Before I go on with what I think we should do, I will give some comments
on UTF-8.

Today we have many character sets in use. In protocols we also have many
and we have ACE like encoding, the best example is quoted-printable
in MIME. I have used these encodings and character sets as a user,
a system administrator and as a software developer. It is a terrible
mess! As a user I quite often get to see junk because of things
like quoted-printable in e-mail and as a software programmer I
need very complex software to decode all different encodings used and
to handle all the character sets. To decode an e-mail is difficult,
in it are character sets, encodings and normal text mixed forcing me
to complex parsing. If everything had been in one character set the
world had been much simpler. I would be much more willing to support
languages different from my own. If normalised UCS had been used
everywhere it would be wonderful.
While I know that my system that have everything encoded in ISO 8859-1
cannot change overnight to UCS, if would work much better if all
interoperability protocols used one encoding of all character data.
While UTF-8 is far from perfect, it is the best choice available.
I can today see no other format than UCS normalised using Unicode form C
and then encoded using UTF-8 to be the best to use for interoperability.
That is my reason for wanting UTF-8/UCS/normalisation form C.

Back to business.

I can see we have three things to decide:
1) Internationalsation of the DNS protocol and handling
2) Selecting ACE
3) How to match names (nameprep).


1) Internationalsation of the DNS protocol and handling
Here people want IDNA for quick employment.
ACE for backward compatibility.
UCS/UTF-8 as standard encoding instead of one more encode in ASCII format.

Could we not then do this?
   The DNS protocol/handling selected is:
   - ACE for backward compatibility
   - IDNA for quick employment
   - UCS/UTF-8 as standard encoding combined with EDNS for longer labels.
Of what I can see this can be done. Combining the IDNA draft with the
UDNS draft will give most of it. And both IDNA and UCS/UTF-8 can be
used at the same time.

Would not this satisfy most people?

2) Selecting ACE.
This need to be done quickly. Especially as Verisign plans to use RACE
even though it may not be the best. We cannot accept that one company
selects the ACE to use. The ACE selected must be done after comparing
all ACE formats. We should give the main criteria for selecting it.
I suggest that the ACE working group inform the rest of us what they
are thinking and what they have done so far.


3) How to match names (nameprep).
We also need to define how names are to be matched.
Today we have one draft for that (nameprep) but that one is
written to fit with IDNA and may have to be changed to fit general
matching rules.
The most important matter to take up here, which have been pointed
to by other (like Dan Bernstein), is: shall two characters
that look identical to typical users match as equal?
They do not in the current version of nameprep.



Could we not go forward with something like this?
Or do those favoring IDNA not think UTF-8 is at all acceptable?
Or do those favoring UTF-8 not accept ACE to be used for backward
compatibility?

If we do a compromise and allow for both preferred formats,
IDN can be working fairely soon. Otherwise I suspect IDN handling
in DNS (and other protocols) will be a mess for a long time.

   Dan




From owner-idn@ops.ietf.org  Sat May 26 08:55:39 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA18864
	for <idn-archive@lists.ietf.org>; Sat, 26 May 2001 08:55:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153dPw-0000i3-00
	for idn-data@psg.com; Sat, 26 May 2001 05:43:40 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 153dPt-0000hx-00
	for idn@ops.ietf.org; Sat, 26 May 2001 05:43:38 -0700
Received: from [0.0.0.0] (ams-vpdn-client-258.cisco.com [144.254.47.6])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id OAA18190;
	Sat, 26 May 2001 14:39:49 +0200 (MET DST)
Date: Sat, 26 May 2001 14:36:09 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Dan <Dan.Oscarsson@trab.se>, idn@ops.ietf.org
Subject: Re: [idn] Let's go forward with IDNA and UTF-8
Message-ID: <7054220.990887769@localhost>
In-Reply-To: <200105261009.f4QA9XI11094@malmo.trab.se>
References:  <200105261009.f4QA9XI11094@malmo.trab.se>
X-Mailer: Mulberry/2.1.0a5 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-05-26 12.09 +0200 Dan <Dan.Oscarsson@trab.se> wrote:

> Or do those favoring IDNA not think UTF-8 is at all acceptable?
> Or do those favoring UTF-8 not accept ACE to be used for backward
> compatibility?

Whether UTF-8 can be used in protocols or not have very much to do with the
ability for a client and server to be able to signal the use of this
character set instead of what is in use today (explicitly or implicitly
specified).

This depends on each and every protocol if this is possible or not, and if
the signalling fails (i.e. client announces UTF-8 and server says "foo?")
what then should the client do?

We have in the SMTP world some experience with Quoted Printable as you say
Dan, where the ESMTP extension for 8bitmime is used, and as most (I claim)
servers can handle 8bit message bodies today AND that signalling works we
don't see as much Quoted-Printable now as we did some 5 years ago. And IF
the quoted printable reach the client, most clients know how to decode it.


Yes, I am one of the persons which think we definitly need an ACE encoding
for the reasons above. We can not add negotiations in all protocols, and we
can not change the middleboxes (application layer firwalls and proxies)
which many times are upgraded the least amount of times, and server
software which the enduser doesn't have control over.

So, an encoding which is non-destructable which makes it clear that all
information which the sender send comes to the recipient regardless of
protocol is a good thing.

        paf




From owner-idn@ops.ietf.org  Sat May 26 08:57:33 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA18883
	for <idn-archive@lists.ietf.org>; Sat, 26 May 2001 08:57:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153dTd-0000na-00
	for idn-data@psg.com; Sat, 26 May 2001 05:47:29 -0700
Received: from heron.verisign.com ([216.168.233.95])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153dTa-0000nC-00
	for idn@ops.ietf.org; Sat, 26 May 2001 05:47:26 -0700
Received: from REGDOM-EX01.prod.netsol.com (rdex01-node1.prod.netsol.com [10.131.4.28])
	by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id IAA14026
	for <idn@ops.ietf.org>; Sat, 26 May 2001 08:46:53 -0400 (EDT)
Received: by regdom-ex01.prod.netsol.com with Internet Mail Service (5.5.2653.19)
	id <LGX50TMC>; Sat, 26 May 2001 08:39:02 -0400
Message-ID: <DF737E620579D411A8E400D0B77E671D01877F5C@regdom-ex01.prod.netsol.com>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: idn@ops.ietf.org
Subject: RE: [idn] report of the straw poll
Date: Sat, 26 May 2001 08:38:54 -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: James Seng/Personal [mailto:James@Seng.cc]
> Sent: Friday, May 25, 2001 11:11 PM
> To: Mark Davis; Paul Hoffman / IMC; Dave Crocker
> Cc: idn@ops.ietf.org
> Subject: Re: [idn] report of the straw poll
> 
> 
> To add another point, which we may/may not want to consider valid:
> 
> Verisign is moving ahead to put RACE into their .COM zone would means
> wide deployment of RACE and also applications (or servers) to be
> developed to support resolutions. They may or may not be IDNA or even
> close to the what we like to be.
> 
> But the fact that this is happening is somewhat of a concern as it may
> undermine the work we are doing in this Working Group as it *might* lead
> to an industry driven protocol.

Perhaps i-DNS should stop distributing *ACE toolkits if you have such
concerns about industry driven protocols.

<Scott/>



From owner-idn@ops.ietf.org  Sat May 26 10:03:01 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA19316
	for <idn-archive@lists.ietf.org>; Sat, 26 May 2001 10:03:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153eQf-00019M-00
	for idn-data@psg.com; Sat, 26 May 2001 06:48:29 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153eQd-00019F-00
	for idn@ops.ietf.org; Sat, 26 May 2001 06:48:27 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA15418;
        Sat, 26 May 2001 09:48:21 -0400 (EDT)
Message-Id: <200105261348.JAA15418@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: Keith Moore <moore@cs.utk.edu>, Bright Fulton <bright@alldomains.com>,
        Paul Hoffman / IMC <phoffman@imc.org>, idn@ops.ietf.org
Subject: Re: [idn] report of the straw poll 
In-reply-to: Your message of "Fri, 25 May 2001 22:18:17 PDT."
             <5.1.0.14.2.20010525221602.03a34c28@dcrocker.net> 
Date: Sat, 26 May 2001 09:48:21 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Your note was phrased in a way that made it easy to think it was intended
> to be related to my suggestion, though it was not.  I therefore wanted to
> make sure that no one thought it was.

fair enough.  I don't think my suggestion was much related to yours either.

Keith



From owner-idn@ops.ietf.org  Sat May 26 11:00:03 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA19712
	for <idn-archive@lists.ietf.org>; Sat, 26 May 2001 11:00:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153fGf-0001SP-00
	for idn-data@psg.com; Sat, 26 May 2001 07:42:13 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153fGd-0001SJ-00
	for idn@ops.ietf.org; Sat, 26 May 2001 07:42:12 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id KAA16225;
        Sat, 26 May 2001 10:42:09 -0400 (EDT)
Message-Id: <200105261442.KAA16225@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
cc: idn@ops.ietf.org
Subject: Re: [idn] report of the straw poll 
In-reply-to: Your message of "Sat, 26 May 2001 05:00:32 EDT."
             <200105260900.f4Q90Wf84779@nic-naa.net> 
Date: Sat, 26 May 2001 10:42:08 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> utf8-on-the-wire has been a third-rail of IETF DNS politics for some time. 

could you explain what you mean by this?  I can think of at least three
contradictory meanings for "third-rail".



From owner-idn@ops.ietf.org  Sat May 26 13:13:25 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA20265
	for <idn-archive@lists.ietf.org>; Sat, 26 May 2001 13:13:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153hJF-0002Ug-00
	for idn-data@psg.com; Sat, 26 May 2001 09:53:01 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153hJC-0002UY-00
	for idn@ops.ietf.org; Sat, 26 May 2001 09:52:59 -0700
Received: from jamessonyvaio (tns02433.singnet.com.sg [165.21.189.223])
	by mail.i-dns.net (Postfix) with SMTP
	id 98B94FFC01; Sun, 27 May 2001 00:55:30 +0800 (SGT)
Message-ID: <04a101c0e604$3836b160$7dcb15a5@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, <idn@ops.ietf.org>
References: <DF737E620579D411A8E400D0B77E671D01877F5C@regdom-ex01.prod.netsol.com>
Subject: Re: [idn] report of the straw poll
Date: Sun, 27 May 2001 00:52:14 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I wear too many hats in this field and I tend to be careful. This
comment is sufficient for me to make a clarification:

When I speaks for i-DNS.net, I will state it clearly so. Otherwise, you
can assumed it is my personal views. And in some cases, it may NOT be in
sync with the views the company who pays my salary adopts.

-James Seng

----- Original Message -----
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: <idn@ops.ietf.org>
Sent: Saturday, May 26, 2001 8:38 PM
Subject: RE: [idn] report of the straw poll


> > -----Original Message-----
> > From: James Seng/Personal [mailto:James@Seng.cc]
> > Sent: Friday, May 25, 2001 11:11 PM
> > To: Mark Davis; Paul Hoffman / IMC; Dave Crocker
> > Cc: idn@ops.ietf.org
> > Subject: Re: [idn] report of the straw poll
> >
> >
> > To add another point, which we may/may not want to consider valid:
> >
> > Verisign is moving ahead to put RACE into their .COM zone would
means
> > wide deployment of RACE and also applications (or servers) to be
> > developed to support resolutions. They may or may not be IDNA or
even
> > close to the what we like to be.
> >
> > But the fact that this is happening is somewhat of a concern as it
may
> > undermine the work we are doing in this Working Group as it *might*
lead
> > to an industry driven protocol.
>
> Perhaps i-DNS should stop distributing *ACE toolkits if you have such
> concerns about industry driven protocols.
>
> <Scott/>
>




From owner-idn@ops.ietf.org  Sat May 26 13:32:48 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA20344
	for <idn-archive@lists.ietf.org>; Sat, 26 May 2001 13:32:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153hg0-0002cE-00
	for idn-data@psg.com; Sat, 26 May 2001 10:16:32 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 153hfx-0002bo-00
	for idn@ops.ietf.org; Sat, 26 May 2001 10:16:29 -0700
Received: (qmail 27511 invoked by uid 1001); 26 May 2001 17:16:23 -0000
Date: 26 May 2001 17:16:23 -0000
Message-ID: <20010526171623.7182.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] Let's go forward with IDNA and UTF-8
References: <200105261009.f4QA9XI11094@malmo.trab.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dan writes:
> The people saying ACE/IDNA say it is quickest and least disruptive
> to non-IDN aware software. Those wanting UTF-8 thinks this format
> is best for internationalisation and fear that starting with IDNA
> will result in ACE forever.

I have a much more serious concern: the short-term costs of deploying
ACE appear to be much larger than the total costs of moving directly to
UTF-8. See http://cr.yp.to/proto/idn.html for details.

---Dan



From owner-idn@ops.ietf.org  Sat May 26 15:35:20 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA20745
	for <idn-archive@lists.ietf.org>; Sat, 26 May 2001 15:35:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153jZx-0003rW-00
	for idn-data@psg.com; Sat, 26 May 2001 12:18:25 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 153jZu-0003rQ-00
	for idn@ops.ietf.org; Sat, 26 May 2001 12:18:22 -0700
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id MAA09589;
	Sat, 26 May 2001 12:18:15 -0700
Message-Id: <5.1.0.14.2.20010526121914.02c160b8@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sat, 26 May 2001 12:19:23 -0700
To: "D. J. Bernstein" <djb@cr.yp.to>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] Let's go forward with IDNA and UTF-8
Cc: idn@ops.ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Careful migration is always more complicated and, in some ways, more 
expensive than a simple switchover.

The problem is with the disruption caused by a "simple" switchover.

d/

At 10:16 AM 5/26/2001, D. J. Bernstein wrote:
>Dan writes:
> > The people saying ACE/IDNA say it is quickest and least disruptive
> > to non-IDN aware software. Those wanting UTF-8 thinks this format
> > is best for internationalisation and fear that starting with IDNA
> > will result in ACE forever.
>
>I have a much more serious concern: the short-term costs of deploying
>ACE appear to be much larger than the total costs of moving directly to
>UTF-8. See http://cr.yp.to/proto/idn.html for details.
>
>---Dan


----------
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 May 26 16:41:06 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA20951
	for <idn-archive@lists.ietf.org>; Sat, 26 May 2001 16:41:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153kcX-0004C6-00
	for idn-data@psg.com; Sat, 26 May 2001 13:25:09 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 153kcQ-0004Bu-00
	for idn@ops.ietf.org; Sat, 26 May 2001 13:25:02 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4QKOPf86478;
	Sat, 26 May 2001 16:24:25 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105262024.f4QKOPf86478@nic-naa.net>
To: "James Seng/Personal" <James@Seng.cc>
cc: "Hollenbeck, Scott" <shollenbeck@verisign.com>, idn@ops.ietf.org,
        brunner@nic-naa.net
Subject: Re: [idn] report of the straw poll 
In-Reply-To: Your message of "Sun, 27 May 2001 00:52:14 +0800."
             <04a101c0e604$3836b160$7dcb15a5@jamessonyvaio> 
Date: Sat, 26 May 2001 16:24:25 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> I wear too many hats in this field and I tend to be careful. This
> comment is sufficient for me to make a clarification:
> 
> When I speaks for i-DNS.net, I will state it clearly so. Otherwise, you
> can assumed it is my personal views. And in some cases, it may NOT be in
> sync with the views the company who pays my salary adopts.

I'm sure I'm going to loose sleep over this.



From owner-idn@ops.ietf.org  Sat May 26 16:58:51 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA20997
	for <idn-archive@lists.ietf.org>; Sat, 26 May 2001 16:58:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153ky9-0004JC-00
	for idn-data@psg.com; Sat, 26 May 2001 13:47:29 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 153ky6-0004J2-00
	for idn@ops.ietf.org; Sat, 26 May 2001 13:47:26 -0700
Received: (qmail 30336 invoked by uid 1001); 26 May 2001 20:47:35 -0000
Date: 26 May 2001 20:47:35 -0000
Message-ID: <20010526204735.23606.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] Let's go forward with IDNA and UTF-8
References: <5.1.0.14.2.20010526121914.02c160b8@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dave Crocker writes:
> The problem is with the disruption caused by a "simple" switchover.

You are speaking nonsense. We don't have any IDNs to disrupt. We are not
switching from one IDN solution to another. The current situation (if we
ignore the widespread UTF-8 experiments) is that IDNs simply don't work.
Our job is to extend the infrastructure to support IDNs.

---Dan



From owner-idn@ops.ietf.org  Sat May 26 21:47:07 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA22871
	for <idn-archive@lists.ietf.org>; Sat, 26 May 2001 21:47:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153pFz-000B9l-00
	for idn-data@psg.com; Sat, 26 May 2001 18:22:11 -0700
Received: from f59.law15.hotmail.com ([64.4.23.59] helo=hotmail.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 153pFw-000B9d-00
	for idn@ops.ietf.org; Sat, 26 May 2001 18:22:09 -0700
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Sat, 26 May 2001 18:21:35 -0700
Received: from 24.130.82.137 by lw15fd.law15.hotmail.msn.com with HTTP;	Sun, 27 May 2001 01:21:35 GMT
X-Originating-IP: [24.130.82.137]
From: "Sherin Alsoudani" <sherinalsoudani@hotmail.com>
To: idn@ops.ietf.org
Subject: [idn] UTF-8 / RACE
Date: Sat, 26 May 2001 18:21:35 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F599No5I9BADCDLTyHU0000f121@hotmail.com>
X-OriginalArrivalTime: 27 May 2001 01:21:35.0500 (UTC) FILETIME=[5EDF44C0:01C0E64B]
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dear members of IDN working group,

As an IT representative from the Middle East, I have been following the 
discussion with some interest but I have not felt qualified to comment.  I 
do have a question however after reading the emails being exchanged back and 
forth.

It appears that switching to UTF-8 will cause much existing software to 
break due to the large number of applications that are only 7-bit clean.  
This will necesitate much work to replace that software with updated 
versions that can process UTF-8.

My question is this: will RACE have a similar problem?  Even if RACE 
converts multilingal domain names to English, will we not have to update our 
applications to convert the domain names via RACE?

For example, if my email program needs to be updated to support UTF-8, does 
it not also need to be updated to handle RACE?  Just different places of the 
code - but nonetheless an update either way?

Thank you very much.  I have many other questions, but please educate me 
first by helping me understand the answer to this first one.

Sherin

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com




From owner-idn@ops.ietf.org  Sun May 27 04:24:44 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA05374
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 04:24:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153vZM-000EPx-00
	for idn-data@psg.com; Sun, 27 May 2001 01:06:36 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 153vZK-000EPq-00
	for idn@ops.ietf.org; Sun, 27 May 2001 01:06:34 -0700
Received: from [0.0.0.0] (ams-vpdn-client-258.cisco.com [144.254.47.6])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id KAA26956;
	Sun, 27 May 2001 10:06:03 +0200 (MET DST)
Date: Sun, 27 May 2001 09:48:44 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: "D. J. Bernstein" <djb@cr.yp.to>, idn@ops.ietf.org
Subject: Re: [idn] Let's go forward with IDNA and UTF-8
Message-ID: <7523232.990956924@localhost>
In-Reply-To: <20010526171623.7182.qmail@cr.yp.to>
References: <200105261009.f4QA9XI11094@malmo.trab.se>
 <20010526171623.7182.qmail@cr.yp.to>
X-Mailer: Mulberry/2.1.0a5 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id EAA05374

--On 01-05-26 17.16 +0000 "D. J. Bernstein" <djb@cr.yp.to> wrote:

> I have a much more serious concern: the short-term costs of deploying
> ACE appear to be much larger than the total costs of moving directly to
> UTF-8. See http://cr.yp.to/proto/idn.html for details.

I see two differences between UTF-8 and ACE which was what I used as
arguments when I made up my mind:

(1) Risk of loss of information

ACE approach is NOT destroying any information when data is sent from
sender to receiver in any of the protocols we have today. It is 100%
backward compatible.

Use of UTF-8 in any place in any protocol where we have a domainname today
MIGHT (I don't use any stronger term, but I don't see I have to either)
destroy some data during transport.

(2) How to fix broken domainnames

In an ACE approach, the enduser himself can change his own applications to
get rid of the ACE encoding and instead see the IDN as it was expected.

In an UTF-8 approach the user MIGHT have to change his applications so they
can display UTF-8 characters and (here comes the important part) someone
else than the enduser MUST upgrade the intermediary boxes (HTTP proxies,
SMTP gateways, SMTP MTA's, POP servers, IMAP servers etc) which is not
under his control.


I.e. if we compare with when we launched MIME, many people have told me
that "but the goal is that the user should not see the ACE, and geee what
Quoted Printable was ugly, let's not use the same mechanism again".

You all should know that I do not listen to people saying that which do not
need Quoted Printable to display their own name.

We need something which can be moved from A to B with existing protocols
and services which are deployed, and then the ability for A and B (alone,
not their network managers, or anyone with a root password) to use IDN's.

    Patrik H:son Fältström




From owner-idn@ops.ietf.org  Sun May 27 04:26:22 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA05385
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 04:26:21 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153vZ2-000EPm-00
	for idn-data@psg.com; Sun, 27 May 2001 01:06:16 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 153vYz-000EPX-00
	for idn@ops.ietf.org; Sun, 27 May 2001 01:06:14 -0700
Received: from [0.0.0.0] (ams-vpdn-client-258.cisco.com [144.254.47.6])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id KAA26960;
	Sun, 27 May 2001 10:06:06 +0200 (MET DST)
Date: Sun, 27 May 2001 09:54:40 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Sherin Alsoudani <sherinalsoudani@hotmail.com>, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
Message-ID: <7544575.990957280@localhost>
In-Reply-To: <F599No5I9BADCDLTyHU0000f121@hotmail.com>
References:  <F599No5I9BADCDLTyHU0000f121@hotmail.com>
X-Mailer: Mulberry/2.1.0a5 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-05-26 18.21 -0700 Sherin Alsoudani <sherinalsoudani@hotmail.com>
wrote:

> My question is this: will RACE have a similar problem?  Even if RACE 
> converts multilingal domain names to English, will we not have to update
> our  applications to convert the domain names via RACE?
> 
> For example, if my email program needs to be updated to support UTF-8,
> does  it not also need to be updated to handle RACE?  Just different
> places of the  code - but nonetheless an update either way?

See separate message sent by me.

You have two different problems here:

(1) If we start using UTF-8, the octets which are sent over the wire will
in the cases the data passes some software which is not upgraded destroy
the data. This is why we need to upgrade software for UTF-8. The software
can be the email client you use, the SMTP server, the DNS forwarding
server, the HTTP proxy, the firewall application, or just whatever between
the service you use and yourself.

(2) If you use an ACE approach (RACE will most certainly NOT be the
encoding used), the data will be possible to be sent from A to B, just
because it is encoded "in english" or rather, "with characters/octets which
we already use today". You need to upgrade your email client, your web
broswer and other client applications to be able to see the orginal
characters in the script it was written in by the sender of the data.

Difference is that in UTF-8 you need to replace all intermediate servers,
while with ACE, the enduser can upgrade his applications, and only that, to
be able to see IDN's. I.e. an enduser can start using IDN's even though his
systems manager have not upgraded the system software on the servers (for
DNS, HTTP and SMTP etc) he use.

Two different reasons for upgrading, and in my view, going with ACE gives
the enduser a choice, and that is far more and better than not giving him a
choice. Further, I claim that created the success MIME ended up being for
non-ascii characters.

    paf




From owner-idn@ops.ietf.org  Sun May 27 06:16:42 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA08529
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 06:16:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153xLv-000IYl-00
	for idn-data@psg.com; Sun, 27 May 2001 03:00:51 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153xLr-000IYe-00
	for idn@ops.ietf.org; Sun, 27 May 2001 03:00:48 -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 f4RA0gI04509; Sun, 27 May 2001 12:00:42 +0200 (MEST)
Message-Id: <200105271000.f4RA0gI04509@malmo.trab.se>
Date: Sun, 27 May 2001 12:00:40 +0200 (MEST)
From: Dan <Dan.Oscarsson@trab.se>
Reply-To: Dan <Dan.Oscarsson@trab.se>
Subject: Re: [idn] Let's go forward with IDNA and UTF-8
To: djb@cr.yp.to, idn@ops.ietf.org, paf@cisco.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Zhscwm8KAV6BezUuP3/g7w==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Patrik said:

>I see two differences between UTF-8 and ACE which was what I used as
>arguments when I made up my mind:
>
>(1) Risk of loss of information
>
>ACE approach is NOT destroying any information when data is sent from
>sender to receiver in any of the protocols we have today. It is 100%
>backward compatible.
Probably 100%, but some software may compare an ACE version of the name
with thde decode version and fail.

But ACE+nameprep IS destroying information.

Also ACE can only be used for host names, if may not fit all types of
DNS names and it cannot be used for other textual data in DNS.
So by using ACE you always need to implement handling of UTF-8 (or what
is used) for all other textual data in DNS.
When we internationalise DNS so IDNs can be handled it must also
include internationalisation of all text data handled in DNS.

>
>Use of UTF-8 in any place in any protocol where we have a domainname today
>MIGHT (I don't use any stronger term, but I don't see I have to either)
>destroy some data during transport.
>
>(2) How to fix broken domainnames
>
>In an ACE approach, the enduser himself can change his own applications to
>get rid of the ACE encoding and instead see the IDN as it was expected.
>
>In an UTF-8 approach the user MIGHT have to change his applications so they
>can display UTF-8 characters and (here comes the important part) someone
>else than the enduser MUST upgrade the intermediary boxes (HTTP proxies,
>SMTP gateways, SMTP MTA's, POP servers, IMAP servers etc) which is not
>under his control.
>
>I.e. if we compare with when we launched MIME, many people have told me
>that "but the goal is that the user should not see the ACE, and geee what
>Quoted Printable was ugly, let's not use the same mechanism again".

There is one major difference between MIME and ACE/UTF-8 in DNS.
In MIME the most importat element for delivery of e-mail, the
e-mail address, was not changed and forced to remain in ascii.
This means that if an adress is copied from an application understanding
MIME to one who does not, it will still work.

With DNS it is the address itself that is changed.
If you have an application understanding ACE and decodes it
into the real address, I am sure people will copy the decoded form
into applications that do not know about ACE and will therefore result
in UTF-8 or other encoding being sent into DNS.
You will get this problem with the UTF-8 solution also.
Some of these problems can be handled if you use DNS servers
like those I have in UDNS which can handle both ACE and UTF-8, as
well as some local characters sets.
So I am sure several of the problems you see with UTF-8 will
also exist with the ACE only solution, though with ACE only
decoded ACE names will never work.

-
One thing everybody also may think about. Even with UTF-8 as
only encoding, there must be a way to display names that
cannot be displayed using the characters available in a client.
So an ACE or a (local charset) Compatible Encoding is still
needed. And I prefer one that can be used by all programs so
all programs display non-displayable names in the same way.


   Dan




From owner-idn@ops.ietf.org  Sun May 27 08:55:40 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA09433
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 08:55:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 153znQ-000O99-00
	for idn-data@psg.com; Sun, 27 May 2001 05:37:24 -0700
Received: from spider.nic-se.se ([212.247.3.67])
	by psg.com with esmtp (Exim 3.16 #1)
	id 153znQ-000O93-00
	for idn@ops.ietf.org; Sun, 27 May 2001 05:37:24 -0700
Received: from localhost (dufberg@localhost)
	by spider.nic-se.se (8.11.1/8.11.1) with ESMTP id f4RCTx005355;
	Sun, 27 May 2001 14:29:59 +0200 (CEST)
X-Authentication-Warning: spider.nic-se.se: dufberg owned process doing -bs
Date: Sun, 27 May 2001 14:29:59 +0200 (CEST)
From: Mats Dufberg <dufberg@nic-se.se>
To: Dan <Dan.Oscarsson@trab.se>
cc: <idn@ops.ietf.org>
Subject: Re: [idn] Let's go forward with IDNA and UTF-8
In-Reply-To: <200105271000.f4RA0gI04509@malmo.trab.se>
Message-ID: <Pine.BSF.4.30.0105271416360.5293-100000@spider.nic-se.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Sun, 27 May 2001, Dan wrote:

> >ACE approach is NOT destroying any information when data is sent from
> >sender to receiver in any of the protocols we have today. It is 100%
> >backward compatible.
> Probably 100%, but some software may compare an ACE version of the name
> with thde decode version and fail.
>
> But ACE+nameprep IS destroying information.
>
> Also ACE can only be used for host names, if may not fit all types of
> DNS names and it cannot be used for other textual data in DNS.

Well, nameprep+UTF-8 will cause the same problem when it comes to the name
part. There is no difference in what codepoints that ACE can handle
compared to UTF-8. Nameprep is there to eliminate ambiguity, and will be
needed for any solution (ACE, UTF-8) to avoide chaos in DNS.

> So by using ACE you always need to implement handling of UTF-8 (or what
> is used) for all other textual data in DNS.

Hm. I guess that some kind of ACE would be better if ACE coding is used
for the names.

> There is one major difference between MIME and ACE/UTF-8 in DNS.

The point is that 8-bit data could be transported through 7-bit-only
server through encoding (quoted-printable, base64). As long as the mail
clients in each end could handle MIME they could use 8-bit character set.

The parallell with the ACE solution is clear.


Mats

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





From owner-idn@ops.ietf.org  Sun May 27 10:41:40 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA10295
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 10:41:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1541Xz-0002Nw-00
	for idn-data@psg.com; Sun, 27 May 2001 07:29: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.16 #1)
	id 1541Xz-0002Nq-00
	for idn@ops.ietf.org; Sun, 27 May 2001 07:29:35 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4RETCf89177;
	Sun, 27 May 2001 10:29:12 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105271429.f4RETCf89177@nic-naa.net>
To: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] report of the straw poll 
In-Reply-To: Your message of "Fri, 25 May 2001 08:38:50 EDT."
             <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca> 
Date: Sun, 27 May 2001 10:29:12 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Marc,

I sent one of the two "Just send binary (UTF)" ballots, (use rfc2044),
arch-1 in Paul's taxonomy (draft-ietf-idn-compare-01.txt).

NeuStar hasn't completed its independent review of the Walid and Ydsig
patent claims. NeuLevel will not deploy RACE, unless directed to do so
by ICANN.

On the presumption that the IPR issue can be resolved acceptably by the
claimants and the IETF, or alternatively that a second independent review,
possibly ours, concludes as Verisign did, that there is no infringement,
my view is consistent with arch-2, "send binary or ACE", and of the ACE
choices, I'm in agreement with the idna-nameprep-ace orientation.

NeuStar will complete its independent review of the Walid and Ydsig patent
claims before London, and I'll post our findings and work-product when they
are available, initially to cooperating registries, and promptly thereafter
to this working group and other interested parties.

People working on the problem of utf8-on-the-wire feel free to drop me a note
off-list.

Eric



From owner-idn@ops.ietf.org  Sun May 27 11:58:39 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA10835
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 11:58:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1542lM-0005MI-00
	for idn-data@psg.com; Sun, 27 May 2001 08:47:28 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 1542lL-0005M0-00
	for idn@ops.ietf.org; Sun, 27 May 2001 08:47:27 -0700
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id IAA09581;
	Sun, 27 May 2001 08:47:25 -0700
Message-Id: <5.1.0.14.2.20010527084627.03aa0d40@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 27 May 2001 08:48:16 -0700
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
From: Dave Crocker <dhc@dcrocker.net>
Subject: RE: [idn] report of the straw poll
Cc: idn@ops.ietf.org
In-Reply-To: <DF737E620579D411A8E400D0B77E671D01877F5C@regdom-ex01.prod.
 netsol.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 05:38 AM 5/26/2001, Hollenbeck, Scott wrote:
> > From: James Seng/Personal [mailto:James@Seng.cc]
> > Verisign is moving ahead to put RACE into their .COM zone would means...
>
>Perhaps i-DNS should stop distributing *ACE toolkits if you have such
>concerns about industry driven protocols.


On the other hand, they are not contractors to ICANN, with a contractual 
obligation to implement standards.

Verisign is.

d/


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




From owner-idn@ops.ietf.org  Sun May 27 13:16:28 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA11042
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 13:16:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1543sW-0008Bz-00
	for idn-data@psg.com; Sun, 27 May 2001 09:58:56 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 1543sV-0008Bq-00
	for idn@ops.ietf.org; Sun, 27 May 2001 09:58:55 -0700
Received: (qmail 30146 invoked by uid 1001); 27 May 2001 16:59:03 -0000
Date: 27 May 2001 16:59:03 -0000
Message-ID: <20010527165903.5833.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
References: <F599No5I9BADCDLTyHU0000f121@hotmail.com> <7544575.990957280@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:
  [ about 8-bit bytes ]
> software which is not upgraded destroy the data

False. For example, qmail and tinydns handle 8-bit data without trouble.
In message <20010105075541.26564.qmail@cr.yp.to> I gave a complete
example of setting up a UTF-8 IDN and sending mail to it, with no
software upgrades. The UTF-8 IDN was displayed properly by xterm.

In contrast, ACE guarantees that the data is unreadable for users of
today's non-ACE software. When you claim that an ACE IDN is transmitted
perfectly, you are ignoring the final step: getting the IDN into the
user's head!

Yes, there are a few pieces of software that have to be upgraded and
redeployed to make UTF-8 IDNs work. But there are many more pieces of
software that have to be upgraded and redeployed to make ACE IDNs work.
See http://cr.yp.to/proto/idn.html for details.

---Dan



From owner-idn@ops.ietf.org  Sun May 27 13:34:10 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA11109
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 13:34:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1544IP-0009HJ-00
	for idn-data@psg.com; Sun, 27 May 2001 10:25:41 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 1544IO-0009HC-00
	for idn@ops.ietf.org; Sun, 27 May 2001 10:25:41 -0700
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id KAA12643
	for <idn@ops.ietf.org>; Sun, 27 May 2001 10:25:40 -0700
Message-Id: <5.1.0.14.2.20010527101902.03a1f6b8@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 27 May 2001 10:20:43 -0700
To: idn@ops.ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] UTF-8 / RACE
In-Reply-To: <20010527165903.5833.qmail@cr.yp.to>
References: <F599No5I9BADCDLTyHU0000f121@hotmail.com>
 <7544575.990957280@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 09:59 AM 5/27/2001, D. J. Bernstein wrote:
>Patrik writes:
>   [ about 8-bit bytes ]
> > software which is not upgraded destroy the data
>
>False. For example, qmail and tinydns handle 8-bit data without trouble.

What a shame that giving an example of some software that handles things 
one way, says nothing at all about other software, which can of course 
behave entirely differently.

d/

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




From owner-idn@ops.ietf.org  Sun May 27 13:59:04 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA11175
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 13:59:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1544ZV-000A1G-00
	for idn-data@psg.com; Sun, 27 May 2001 10:43:21 -0700
Received: from [216.177.8.114] (helo=ayna.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 1544ZU-000A0p-00
	for idn@ops.ietf.org; Sun, 27 May 2001 10:43:20 -0700
Received: (from nobody@localhost)
	by ayna.com (8.9.3/8.9.3) id OAA02995;
	Sun, 27 May 2001 14:04:15 -0400
To: "D. J. Bernstein" <djb@cr.yp.to>, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
Message-ID: <990986655.3b11419f12bac@www.bareed.ayna.com>
Date: Sun, 27 May 2001 14:04:15 -0400 (EDT)
From: Adonis El Fakih <adonis@ayna.com>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: Ayna VER 2.22 
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi IDNers,

I have to agree here.

We have been using utf8 on our site and in all the backend tools like databases, programs, etc.. and some of them I had to hack a little, but I think it is easier to have utf8 implemented than using RACE.  We are also using it today to resolve Arabic domain names with DNS/BIND v9.  

It is evident from both supporters of utf8 and race that in both cases things have to change, so if we change let us do it once and for all to utf8.  The effort spent in making aps work with RACE most likely is very close to making it work with utf8, but more apps have to be converted in the utf8 case.  We are complaining that we have no choice etc..  But how many of us were forced to upgrade by our friend Microsoft, and we did it, despite our unhappiness with the process.  So this is the same, we need to move forward while ASCII is holding us back, and we should not worry about those systems.  ASCII systems most likely will not have to handle IDNs but new apps will, so if we go with utf8 we insure that we are progressing and regressing.

Just my 2 cents of wisdom :))

Ok thanks
Adonis


________________________________________________
Adonis El Fakih - Chairman, CEO
Ayna Corporation, World Trade Center, Suite 315,
Boston, MA 02210 USA



"D. J. Bernstein" <djb@cr.yp.to> ßÊÈ:

> Patrik writes:
  [ about 8-bit bytes ]
> software which is not upgraded destroy the data

False. For example, qmail and tinydns handle 8-bit data without trouble.
In message <20010105075541.26564.qmail@cr.yp.to> I gave a complete
example of setting up a UTF-8 IDN and sending mail to it, with no
software upgrades. The UTF-8 IDN was displayed properly by xterm.

In contrast, ACE guarantees that the data is unreadable for users of
today's non-ACE software. When you claim that an ACE IDN is transmitted
perfectly, you are ignoring the final step: getting the IDN into the
user's head!

Yes, there are a few pieces of software that have to be upgraded and
redeployed to make UTF-8 IDNs work. But there are many more pieces of
software that have to be upgraded and redeployed to make ACE IDNs work.
See http://cr.yp.to/proto/idn.html for details.

---Dan




______________________________________________________________
Ayna, The Arabic Internet Starts Here.     http://www.ayna.com



From owner-idn@ops.ietf.org  Sun May 27 15:04:12 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA11457
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 15:04:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1545ay-000Cfe-00
	for idn-data@psg.com; Sun, 27 May 2001 11:48:56 -0700
Received: from arachnid.ehsco.com ([209.31.7.46] helo=Arachnid.NTRG.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 1545ax-000CfW-00
	for idn@ops.ietf.org; Sun, 27 May 2001 11:48:56 -0700
Received: from ehsco.com (nat-external.ehsco.com [209.31.7.42])
          by Arachnid.NTRG.com (Netscape Messaging Server 3.62)  with ESMTP
          id 597; Sun, 27 May 2001 11:48:53 -0700
Message-ID: <3B114C15.21B15C8E@ehsco.com>
Date: Sun, 27 May 2001 11:48:53 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@cisco.com>
CC: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
References: <F599No5I9BADCDLTyHU0000f121@hotmail.com> <7544575.990957280@localhost>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit


Patrik Fältström wrote:

> Difference is that in UTF-8 you need to replace all intermediate
> servers, while with ACE, the enduser can upgrade his applications,
> and only that, to be able to see IDN's. I.e. an enduser can start
> using IDN's even though his systems manager have not upgraded the
> system software on the servers (for DNS, HTTP and SMTP etc) he use.

Let's keep this in perspective. With either ACE or UTF8, the end-user
applications have to be upgraded before the targeted functionality (local
representation of IDNs) is fully working. We are already talking about a
forklift upgrade of the entire Internet before email addresses, URLs and
other IDN occurances work right. In that context, upgrading the remaining
boxes is not exactly a show-stopper.

Also, if upgrading the servers means that the admin gets native language
support across their entire network instead of only getting it at the
end-user presentation time, I feel certain they would choose that
solution. Given the choice between encoded IDNs which were even more
user-hostile than ASCII domain names, or direct native language support
for slightly more cost, which would you choose?

Moreover, with ACE-only, they do not get this choice. They *cannot* get
native language support across all of their applications. In fact, asking
end-users to upgrade once for ACE and upgrade again later for UTF8 is
essentially asking for two forklift upgrades, which is the most expensive
solution of all.

So options and cost-of-deployments are:

   do nothing:     low-cost     low-functionality
   ACE only:       high-cost    low-functionality
   UTF8/ACE:       higher-cost  high-functionality
   ACE then UTF8:  2X-cost      high-functionality

Furthermore, given the overlap in functionality and deployment costs, I
think that it would be easiest on the development community to do UTF-8
and ACE at the same time, since they have the same basic core requirements
WRT nameprep and such. It would be much more expensive to do one upgrade
for ACE and then come back and repeat the development project for UTF-8,
since it would be two complete development cycles.

So cost-of-deployment for the user is not significantly greater to do
UTF8/ACE, but cost-of-development for the industry *IS* higher to do ACE
and UTF8 on separate development tracks.

One other point: Going to UTF8/ACE means that we can upgrade applications
as/when the WGs want to do it. ACE-only means the WGs cannot use rich IDNs
even if they wanted to.

I will also point out that there is one potential downside to doing ACE
and UTF8 together, and that is the issue of managing duplicate encodings
within the namespace (the ACE and raw domain names both have to be
provided at different times, so they both have to be maintained). That may
be resolvable through protocol, however, although I did want to bring it
up as a potential issue.

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



From owner-idn@ops.ietf.org  Sun May 27 15:16:56 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA11513
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 15:16:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1545rI-000DQ9-00
	for idn-data@psg.com; Sun, 27 May 2001 12:05:48 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 1545rH-000DQ3-00
	for idn@ops.ietf.org; Sun, 27 May 2001 12:05:47 -0700
Received: from [192.168.1.40] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id VAA08669;
	Sun, 27 May 2001 21:02:01 +0200 (MET DST)
Date: Sun, 27 May 2001 21:01:47 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Dan <Dan.Oscarsson@trab.se>, idn@ops.ietf.org
Subject: Re: [idn] Let's go forward with IDNA and UTF-8
Message-ID: <7923789.990997307@[192.168.1.40]>
In-Reply-To: <200105271000.f4RA0gI04509@malmo.trab.se>
References:  <200105271000.f4RA0gI04509@malmo.trab.se>
X-Mailer: Mulberry/2.1.0a5 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-05-27 12.00 +0200 Dan <Dan.Oscarsson@trab.se> wrote:

> Patrik said:
> 
>> I see two differences between UTF-8 and ACE which was what I used as
>> arguments when I made up my mind:
>> 
>> (1) Risk of loss of information
>> 
>> ACE approach is NOT destroying any information when data is sent from
>> sender to receiver in any of the protocols we have today. It is 100%
>> backward compatible.
> Probably 100%, but some software may compare an ACE version of the name
> with thde decode version and fail.
> 
> But ACE+nameprep IS destroying information.

Whether we should do nameprep or not is a different question than encoding,
and that question is orthogonal to whether UTF-8 or ACE encoding of the
domains should be used.

I really want those issues to be separated.

> Also ACE can only be used for host names, if may not fit all types of
> DNS names and it cannot be used for other textual data in DNS.
> So by using ACE you always need to implement handling of UTF-8 (or what
> is used) for all other textual data in DNS.
> When we internationalise DNS so IDNs can be handled it must also
> include internationalisation of all text data handled in DNS.

Sure, but internationalization of the DNS protocol is a no-brainer (I agree
with you here) because the protocol is specified to be able to handle 8bit
octets of any value.

The problem is not DNS, but when the data in DNS is used in other protocols.

> There is one major difference between MIME and ACE/UTF-8 in DNS.
> In MIME the most importat element for delivery of e-mail, the
> e-mail address, was not changed and forced to remain in ascii.
> This means that if an adress is copied from an application understanding
> MIME to one who does not, it will still work.

Correct, and I call this "the clipboard problem" (even though it can happen
automatically aswell).

> With DNS it is the address itself that is changed.
> If you have an application understanding ACE and decodes it
> into the real address, I am sure people will copy the decoded form
> into applications that do not know about ACE and will therefore result
> in UTF-8 or other encoding being sent into DNS.

Yes, absolutely, as also John Klensin has said several times. This is
though nothing special for ACE, or UTF-8 or whatever, but a result of every
operating system in their local version using a different default script.

> You will get this problem with the UTF-8 solution also.

Yes.

> Some of these problems can be handled if you use DNS servers
> like those I have in UDNS which can handle both ACE and UTF-8, as
> well as some local characters sets.
> So I am sure several of the problems you see with UTF-8 will
> also exist with the ACE only solution, though with ACE only
> decoded ACE names will never work.

I don't agree with your conclusion, because if you have an application
which take care of broken "clients" already, that can take care of decoded
ACE aswell as UTF-8 aswell as ISO 2022-JP or whatever.

I.e. I think we all agree about one thing: we will get a complete mess all
over the place, and the only thing that can not stop that is to NOT do IDN
at this layer in the protocol stack at all, and instead just do a
dictionary solution.

> One thing everybody also may think about. Even with UTF-8 as
> only encoding, there must be a way to display names that
> cannot be displayed using the characters available in a client.

I would even say that one of the errors we will get in the "clipboard
problem" is if you copy and paste between two applications which both know
ACE, but the internal script used in either of the applications (or the
clipboard itself) can not handle the characters which are encoded (in ACE
or UTF-8). We will loose there aswell, if not the applications are very
clever, and for example encode the domainname before storing it in a
clipboard.

   paf




From owner-idn@ops.ietf.org  Sun May 27 15:30:03 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA11571
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 15:30:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1545qu-000DPo-00
	for idn-data@psg.com; Sun, 27 May 2001 12:05:24 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 1545qt-000DPT-00
	for idn@ops.ietf.org; Sun, 27 May 2001 12:05:23 -0700
Received: from [192.168.1.40] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id VAA08761;
	Sun, 27 May 2001 21:04:43 +0200 (MET DST)
Date: Sun, 27 May 2001 21:04:29 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: "D. J. Bernstein" <djb@cr.yp.to>, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
Message-ID: <7933497.990997469@[192.168.1.40]>
In-Reply-To: <20010527165903.5833.qmail@cr.yp.to>
References: <F599No5I9BADCDLTyHU0000f121@hotmail.com>
 <7544575.990957280@localhost> <20010527165903.5833.qmail@cr.yp.to>
X-Mailer: Mulberry/2.1.0a5 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-05-27 16.59 +0000 "D. J. Bernstein" <djb@cr.yp.to> wrote:

> False. For example, qmail and tinydns handle 8-bit data without trouble.
> In message <20010105075541.26564.qmail@cr.yp.to> I gave a complete
> example of setting up a UTF-8 IDN and sending mail to it, with no
> software upgrades. The UTF-8 IDN was displayed properly by xterm.
> 
> In contrast, ACE guarantees that the data is unreadable for users of
> today's non-ACE software. When you claim that an ACE IDN is transmitted
> perfectly, you are ignoring the final step: getting the IDN into the
> user's head!

The point of my message was to show that we talk about two different
problems, two different kind of errors.

Not to continue to argue about whether the whole world is using the
software you list as "ok" or not.

   paf




From owner-idn@ops.ietf.org  Sun May 27 15:30:18 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA11582
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 15:30:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1545oB-000DLF-00
	for idn-data@psg.com; Sun, 27 May 2001 12:02:35 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.16 #1)
	id 1545oA-000DL4-00
	for idn@ops.ietf.org; Sun, 27 May 2001 12:02:34 -0700
Received: from CLASSIC.viagenie.qc.ca (modemcable245.48-201-24.que.mc.videotron.ca [24.201.48.245])
	by jazz.viagenie.qc.ca (Viagenie/8.11.0) with ESMTP id f4RJHK156692;
	Sun, 27 May 2001 15:17:20 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010527103838.0200e7c0@mail.viagenie.qc.ca>
X-Sender: blanchet@mail.viagenie.qc.ca
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 27 May 2001 10:47:10 -0400
To: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: Re: [idn] report of the straw poll 
Cc: idn@ops.ietf.org
In-Reply-To: <200105271429.f4RETCf89177@nic-naa.net>
References: <Your message of "Fri, 25 May 2001 08:38:50 EDT." <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

At/À 10:29 2001-05-27 -0400, Eric Brunner-Williams in Portland Maine you 
wrote/vous écriviez:
>Marc,
>
>I sent one of the two "Just send binary (UTF)" ballots, (use rfc2044),
>arch-1 in Paul's taxonomy (draft-ietf-idn-compare-01.txt).
>
>NeuStar hasn't completed its independent review of the Walid and Ydsig
>patent claims. NeuLevel will not deploy RACE, unless directed to do so
>by ICANN.
>
>On the presumption that the IPR issue can be resolved acceptably by the
>claimants and the IETF, or alternatively that a second independent review,
>possibly ours, concludes as Verisign did, that there is no infringement,
>my view is consistent with arch-2, "send binary or ACE", and of the ACE
>choices, I'm in agreement with the idna-nameprep-ace orientation.

you mean that, presuming no IPR, you change your vote to "agree on 
idna-nameprep-ace".
right?


>NeuStar will complete its independent review of the Walid and Ydsig patent
>claims before London, and I'll post our findings and work-product when they
>are available, initially to cooperating registries, and promptly thereafter
>to this working group and other interested parties.

I'm sure that this will be valuable input to the wg.

Thanks, Marc.


>People working on the problem of utf8-on-the-wire feel free to drop me a note
>off-list.
>
>Eric





From owner-idn@ops.ietf.org  Sun May 27 15:52:59 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA11657
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 15:52:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1546Kz-000EkV-00
	for idn-data@psg.com; Sun, 27 May 2001 12:36:29 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 1546Ky-000EkP-00
	for idn@ops.ietf.org; Sun, 27 May 2001 12:36:28 -0700
Received: from jamessonyvaio (tns00824.singnet.com.sg [165.21.185.214])
	by mail.i-dns.net (Postfix) with SMTP
	id 07268FFC01; Mon, 28 May 2001 03:39:03 +0800 (SGT)
Message-ID: <079c01c0e6e4$3bf7ee50$7dcb15a5@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
References: <F599No5I9BADCDLTyHU0000f121@hotmail.com> <7544575.990957280@localhost> <20010527165903.5833.qmail@cr.yp.to>
Subject: Re: [idn] UTF-8 / RACE
Date: Mon, 28 May 2001 03:35:48 +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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Dan,

Let me take a stab at some of the comments you have at
http://cr.yp.to/proto/idn.html
Making it work. apache needs to be upgraded. Domain names in
configuration files need to be converted from possibly bad to good, and
from UTF-8 to 7-bit. 7-bit domain names need to be converted to UTF-8
for logs.

Question: Why would apache needs to be upgraded if ACE+Nameprep been
used? The administrator should already have the ACE for his domain and
that could goes directly into the config file. [1]

fetchmail needs to be upgraded. Domain names embedded in POP usernames
need to be converted from possibly bad to good, and from UTF-8 to 7-bit.

Question: Why is this so? See reason [1].

gethostbyname needs to be upgraded. The input domain name needs to be
converted from possibly bad to good, and from UTF-8 to 7-bit, before it
is sent as a DNS query. The output domain names in h_name and h_aliases
need to be converted from 7-bit to UTF-8.

Question: Why would gethostbyname needs to be upgrade? The specification
in IDNA is quite clear that it does not do anything to gethostbyname.
Thus, if you *do* change gethostbyname, you are violating IDNA, no?

lynx needs to be upgraded. Domain names in configuration files need to
be converted from possibly bad to good, and from UTF-8 to 7-bit. 7-bit
domain names need to be converted to UTF-8 for internationalized URL
displays.

Question: Why is this so? See reason [1].

mutt needs to be upgraded. 7-bit domain names need to be converted to
UTF-8 when messages are displayed. UTF-8 needs to be spaced properly.
Addresses in configuration files need to be converted from possibly bad
to good, and from UTF-8 to 7-bit.

Agree.

named needs to be upgraded. Domain names in configuration files such as
/etc/named.boot need to be converted from possibly bad to good, and from
UTF-8 to 7-bit. 7-bit domain names in queries need to be converted to
UTF-8 for logs.

Question: Why is this so? See reason [1].

netscape needs to be upgraded. 7-bit domain names need to be displayed
as Unicode glyphs. Domain names in configuration files need to be
converted from possibly bad to good, and from UTF-8 to 7-bit.

Agree. That is what IDNA is suppose to do. But in realty, actually it is
much more complex since browser actually works with URL at the UI level,
not just domain names.

pine needs to be upgraded. 7-bit domain names need to be converted to
UTF-8 when messages are displayed. UTF-8 needs to be spaced properly.
Addresses in configuration files need to be converted from possibly bad
to good, and from UTF-8 to 7-bit.

Agree. That is what you mean by IDNA.

publicfile needs to be upgraded. Domain names in the /public/file
directory need to be converted from possibly bad to good, and from UTF-8
to 7-bit. 7-bit domain names need to be converted to UTF-8 for logs.

Question: Why is this so? See reason [1].

qmail-send needs to be upgraded. Domain names in configuration files
such as /var/qmail/control/virtualdomains need to be converted from
possibly bad to good, and from UTF-8 to 7-bit. 7-bit domain names need
to be converted to UTF-8 for logs.

Question: Why is this so? See reason [1].

sendmail needs to be upgraded. Domain names in configuration files such
as /etc/sendmail.cw need to be converted from possibly bad to good, and
from UTF-8 to 7-bit. 7-bit domain names need to be converted to UTF-8
for logs.

Question: Why is this so? See reason [1].

sshd needs to be upgraded. Domain names in configuration files such as
/etc/shosts.equiv need to be converted from possibly bad to good, and
from UTF-8 to 7-bit. 7-bit domain names need to be converted to UTF-8
for logs.

Question: Why is this so? See reason [1].

tcpclient needs to be upgraded. The input domain name needs to be
converted from possibly bad to good, and from UTF-8 to 7-bit, before it
is sent as a DNS query.

Question: Why is this so? See reason [1].

tcprules needs to be upgraded. Domain names in configuration files need
to be converted from possibly bad to good, and from UTF-8 to 7-bit.
7-bit domain names need to be converted to UTF-8 for logs.

Question: Why is this so? See reason [1].

tinydns needs to be upgraded. Domain names in configuration files such
as /service/tinydns/root/data need to be converted from possibly bad to
good, and from UTF-8 to 7-bit. 7-bit domain names in queries need to be
converted to UTF-8 for logs.

Question: Why is this so? See reason [1].

w3m needs to be upgraded. Domain names in configuration files need to be
converted from possibly bad to good, and from UTF-8 to 7-bit. 7-bit
domain names need to be converted to UTF-8 for internationalized URL
displays.

Question: Why is this so? See reason [1].

-James Seng

----- Original Message -----
From: "D. J. Bernstein" <djb@cr.yp.to>
To: <idn@ops.ietf.org>
Sent: Monday, May 28, 2001 12:59 AM
Subject: Re: [idn] UTF-8 / RACE


> Patrik writes:
>   [ about 8-bit bytes ]
> > software which is not upgraded destroy the data
>
> False. For example, qmail and tinydns handle 8-bit data without
trouble.
> In message <20010105075541.26564.qmail@cr.yp.to> I gave a complete
> example of setting up a UTF-8 IDN and sending mail to it, with no
> software upgrades. The UTF-8 IDN was displayed properly by xterm.
>
> In contrast, ACE guarantees that the data is unreadable for users of
> today's non-ACE software. When you claim that an ACE IDN is
transmitted
> perfectly, you are ignoring the final step: getting the IDN into the
> user's head!
>
> Yes, there are a few pieces of software that have to be upgraded and
> redeployed to make UTF-8 IDNs work. But there are many more pieces of
> software that have to be upgraded and redeployed to make ACE IDNs
work.
> See http://cr.yp.to/proto/idn.html for details.
>
> ---Dan
>




From owner-idn@ops.ietf.org  Sun May 27 16:36:08 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA11824
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 16:36:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 15476z-000GfQ-00
	for idn-data@psg.com; Sun, 27 May 2001 13:26:05 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 15476y-000GfI-00
	for idn@ops.ietf.org; Sun, 27 May 2001 13:26:04 -0700
Received: (qmail 30769 invoked by uid 1001); 27 May 2001 20:26:13 -0000
Date: 27 May 2001 20:26:13 -0000
Message-ID: <20010527202613.5518.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
References: <F599No5I9BADCDLTyHU0000f121@hotmail.com> <7544575.990957280@localhost> <20010527165903.5833.qmail@cr.yp.to> <079c01c0e6e4$3bf7ee50$7dcb15a5@jamessonyvaio>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

My web page carefully specifies details of the ACE solution: where ACE
is used, where it is not used, and what has to be changed to make that
work. The reason that gethostbyname() has to be upgraded, for example,
is that ACE is not used in ``command lines for telnet, ssh, etc.'' but
ACE is used in ``DNS queries and responses.''

My web page then carefully specifies details of the UTF-8 solution. See
http://cr.yp.to/proto/idn.html.

I'm willing to analyze the costs of other IDN solutions. But I'm not
interested in proposals that don't actually provide internationalized
domain names. It's idiotic to claim that we have Greek domain names if
Greek users aren't seeing Greek alphas and betas on the screen. (Does
anyone dispute this?)

James Seng/Personal writes:
> The administrator should already have the ACE for his domain and
> that could goes directly into the config file.

No. That would not be a working IDN solution. A Greek administrator
would see unreadable ACE gobbledygook instead of a readable Greek alpha.

---Dan



From owner-idn@ops.ietf.org  Sun May 27 16:47:36 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA11867
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 16:47:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1547JV-000H1o-00
	for idn-data@psg.com; Sun, 27 May 2001 13:39:01 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 1547JU-000H1i-00
	for idn@ops.ietf.org; Sun, 27 May 2001 13:39:00 -0700
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id NAA17958;
	Sun, 27 May 2001 13:38:58 -0700
Message-Id: <5.1.0.14.2.20010527133858.00c24ff0@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 27 May 2001 13:39:55 -0700
To: Patrik Fältström <paf@cisco.com>
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] Let's go forward with IDNA and UTF-8
Cc: idn@ops.ietf.org
In-Reply-To: <7923789.990997307@[192.168.1.40]>
References: <200105271000.f4RA0gI04509@malmo.trab.se>
 <200105271000.f4RA0gI04509@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 12:01 PM 5/27/2001, Patrik Fältström wrote:
>Whether we should do nameprep or not is a different question than encoding,
>and that question is orthogonal to whether UTF-8 or ACE encoding of the
>domains should be used.
>
>I really want those issues to be separated.


   * * *  Y  E  S  ! ! !  * * *

d/

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




From owner-idn@ops.ietf.org  Sun May 27 17:41:28 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA12095
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 17:41:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 15487h-000JUC-00
	for idn-data@psg.com; Sun, 27 May 2001 14:30:53 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 15487g-000JU5-00
	for idn@ops.ietf.org; Sun, 27 May 2001 14:30:53 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 15487g-0004aZ-00; Sun, 27 May 2001 14:30:52 -0700
Date: Sun, 27 May 2001 21:30:52 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
Message-ID: <20010527213052.C17337@arwen.cs.berkeley.edu>
References: <F599No5I9BADCDLTyHU0000f121@hotmail.com> <7544575.990957280@localhost> <20010527165903.5833.qmail@cr.yp.to> <079c01c0e6e4$3bf7ee50$7dcb15a5@jamessonyvaio> <20010527202613.5518.qmail@cr.yp.to>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <20010527202613.5518.qmail@cr.yp.to>; from djb@cr.yp.to on Sun, May 27, 2001 at 08:26:13PM -0000
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Some people seem to be arguing that using ACE requires no less (or even
more) upgrading of software than using UTF-8 without ACE.  While it may
be true that ACE-fully-working-everywhere requires as much upgrading as
UTF-8-working-fully-everywhere, that comparison overlooks an important
point.

ACE affords incremental deployment much better than no-ACE.  Suppose I
am considering getting an IDN for my domain.  With ACE, this will make
things better for some users (who have upgraded their clients to decode
the ACE) and worse for others (who have old clients and will see ugly
ACEs) but nothing will actually break (mail will get through, web pages
will load, etc).

But without ACE, if I get an IDN for my domain, this will make things
better for some users (who have upgraded their clients, or who are lucky
enough to already be using UTF-8 clients) and will *completely* *break*
things for other users (mail will not get through, web pages will not
load, etc).  There may be nothing those users can do to fix it, because
the breakage might be happening in their provider's software.  The
provider might be very slow to upgrade, because 99% of their customers
might be English speakers, and the other 1% are just screwed.

With ACE, people might have to put visible ACEs in some config
files, which is annoying, but at least it will work.  Eventually
the application might get upgraded to support native characters in
the config files and then things will get easier.  Without ACE, the
application will simply be unusable with IDNs until it is upgraded.

Conclusion: There should be ACE.

Next question:  Given that there will be ACE, should DNS support 8-bit
queries in addition to ACE queries?  I don't know.  No matter what
is recommended or discouraged, some DNS servers will probably try to
guess the encoding of 8-bit queries.  This will help old clients, but
increases the risk of spoofing, and allows some applications to be
lazier about upgrading.  I haven't yet formed an opinion on this.

Next question:  Should ACE ever be phased out?  I don't think so.  Very
few systems will ever support all Unicode characters, so applications
will sometimes try to display IDNs containing unsupported characters.
What should they display?  They should display the ACE, because that's
no uglier than anything else they might display, and has the added bonus
that you can copy it into any other application and it will still work.

Furthmore, domain names are first and foremost *global* identifiers
intended to be used by *humans* *anywhere* to refer to network objects.
For people who know the Unicode characters in the domain name, the
native representation is easiest, but for the billions of people who
don't know those characters, the ACE is much easier to type, write,
speak, and visually compare.  (The Roman alphabet is one of the smallest
alphabets in existence, and is already widely recognized.  If you have
to chose a fallback character set for everyone to learn, that's the best
choice.)

I'm not saying that various protocols shouldn't allow 8-bit encoding in
addition to ACE (I have no opinion on that yet), I'm just saying that
ACE will always serve a useful function, and should never be deprecated.

AMC



From owner-idn@ops.ietf.org  Sun May 27 17:41:29 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA12102
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 17:41:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 15486r-000JRP-00
	for idn-data@psg.com; Sun, 27 May 2001 14:30:01 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 15486p-000JRD-00
	for idn@ops.ietf.org; Sun, 27 May 2001 14:29:59 -0700
Received: from jamessonyvaio (58delta639.singnet.com.sg [165.21.219.5])
	by mail.i-dns.net (Postfix) with SMTP
	id 40E38FFC01; Mon, 28 May 2001 05:32:34 +0800 (SGT)
Message-ID: <07cd01c0e6f4$1843f750$7dcb15a5@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
References: <F599No5I9BADCDLTyHU0000f121@hotmail.com> <7544575.990957280@localhost> <20010527165903.5833.qmail@cr.yp.to> <079c01c0e6e4$3bf7ee50$7dcb15a5@jamessonyvaio> <20010527202613.5518.qmail@cr.yp.to>
Subject: Re: [idn] UTF-8 / RACE
Date: Mon, 28 May 2001 05:29:21 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Lets go on this track a bit further since you touch the topic of "seeing
on the screen".

On an OS/Application, we can consider an I18N UI to have three layer,
altho it is not obvious sometimes:

Layer 1: Rendering of Glyphs/Fonts
Layer 2: Application Encoding
Layer 3: Machine Encoding

Layer 3 is what the OS use internally for representation of codepoints.
Some OS uses Unicode (UTF-16), very few uses UTF-8, and a lot of legacy
one uses  their own native encodings. In Windows example, this would be
either UTF-16 (>Win98) or native encodings (<Win98SE).

Layer 2 is what the application uses internally. Similarly at OS,
different apps choose different encodings. For example, Microsoft IE
uses native encodings (vary occuring to locale OS) at its interface
layer but you can switch it to support mulitple encodings including
UTF-8.

Layer 1 is where Layer 2 encodings are rendered into proper characters
so it can be display. This is by far the most troublesome since we have
to assumed the users have the right fonts and rendering engine to
display it.

Layer 1 cause the problem of 'seeing on the screen'. Supposing I were to
attach some chinese characters in this email using UTF-8 but you are not
equip with the chinese fonts, all you end up seeing is some gibberish.
This is a problem which cannot be solve using UTF-8 (Layer 2/3), but
rather an rendering and font problem (Layer 1).

AFAICS, some 8-bit gibberish is no different some seeing some ACE
gibberish if I am not ready to handle your scripts. A gibberish is a
gibberish if I cant see it even if it is encoded in UTF-8. Hence, the
end-user have to upgrade/update the client, in some ways.

Thus, "seeing on the screen" is probably not so a simple problem of
'using UTF-8 and we are done'.

Aside, I am a bit confuse by your defination of "UTF-8 with Fast
Nameprep". When you mean "Fast Nameprep", do you mean we don't do
Nameprep at all? I would be glad to give comments on the second part of
your website once this is clear up.

-James Seng

----- Original Message -----
From: "D. J. Bernstein" <djb@cr.yp.to>
To: <idn@ops.ietf.org>
Sent: Monday, May 28, 2001 4:26 AM
Subject: Re: [idn] UTF-8 / RACE


> My web page carefully specifies details of the ACE solution: where ACE
> is used, where it is not used, and what has to be changed to make that
> work. The reason that gethostbyname() has to be upgraded, for example,
> is that ACE is not used in ``command lines for telnet, ssh, etc.'' but
> ACE is used in ``DNS queries and responses.''
>
> My web page then carefully specifies details of the UTF-8 solution.
See
> http://cr.yp.to/proto/idn.html.
>
> I'm willing to analyze the costs of other IDN solutions. But I'm not
> interested in proposals that don't actually provide internationalized
> domain names. It's idiotic to claim that we have Greek domain names if
> Greek users aren't seeing Greek alphas and betas on the screen. (Does
> anyone dispute this?)
>
> James Seng/Personal writes:
> > The administrator should already have the ACE for his domain and
> > that could goes directly into the config file.
>
> No. That would not be a working IDN solution. A Greek administrator
> would see unreadable ACE gobbledygook instead of a readable Greek
alpha.
>
> ---Dan
>




From owner-idn@ops.ietf.org  Sun May 27 17:59:41 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA12146
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 17:59:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1548Rv-000KTw-00
	for idn-data@psg.com; Sun, 27 May 2001 14:51:47 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 1548Ru-000KTq-00
	for idn@ops.ietf.org; Sun, 27 May 2001 14:51:46 -0700
Received: from jamessonyvaio (58delta639.singnet.com.sg [165.21.219.5])
	by mail.i-dns.net (Postfix) with SMTP
	id 655F9FFC01; Mon, 28 May 2001 05:54:21 +0800 (SGT)
Message-ID: <083c01c0e6f7$235b7200$7dcb15a5@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
References: <F599No5I9BADCDLTyHU0000f121@hotmail.com> <7544575.990957280@localhost> <20010527165903.5833.qmail@cr.yp.to> <079c01c0e6e4$3bf7ee50$7dcb15a5@jamessonyvaio> <20010527202613.5518.qmail@cr.yp.to>
Subject: Re: [idn] UTF-8 / RACE
Date: Mon, 28 May 2001 05:51:08 +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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> My web page carefully specifies details of the ACE solution: where ACE
> is used, where it is not used, and what has to be changed to make that
> work. The reason that gethostbyname() has to be upgraded, for example,
> is that ACE is not used in ``command lines for telnet, ssh, etc.'' but
> ACE is used in ``DNS queries and responses.''

If we were to consider telnet/ssh etc as "Applications" and then look at
IDNA:

*If* we adopt IDNA, then telnet/ssh etc have to be upgraded to be IDNA
compatible. So we will end up with IDNA-enabled telnet/ssh or
non-IDNA-enabled telnet/ssh. Sad but true. On the bright-side, only
users would needs IDNA-enabled telnet would need to upgrade their
telnet.

Upgrading gethostbyname() is not in-line with IDNA. In fact, by
upgrading gethostbyname(), you are doing IDNRA not IDNA. Correct me if I
am wrong, but IDNRA has already been given up by the authors.

Therefore, I do not think gethostbyname() should be upgraded (again, on
the assumption that IDNA is been adopted).

-James Seng




From owner-idn@ops.ietf.org  Sun May 27 18:12:55 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA12222
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 18:12:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1548fF-000L7l-00
	for idn-data@psg.com; Sun, 27 May 2001 15:05:33 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 1548fE-000L7f-00
	for idn@ops.ietf.org; Sun, 27 May 2001 15:05:32 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 1548fE-0004ef-00; Sun, 27 May 2001 15:05:32 -0700
Date: Sun, 27 May 2001 22:05:31 +0000
To: idn working group <idn@ops.ietf.org>
Subject: Re: [idn] UTF-8 / RACE
Message-ID: <20010527220531.E17337@arwen.cs.berkeley.edu>
References: <F599No5I9BADCDLTyHU0000f121@hotmail.com> <7544575.990957280@localhost> <20010527165903.5833.qmail@cr.yp.to> <079c01c0e6e4$3bf7ee50$7dcb15a5@jamessonyvaio> <20010527202613.5518.qmail@cr.yp.to> <083c01c0e6f7$235b7200$7dcb15a5@jamessonyvaio>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <083c01c0e6f7$235b7200$7dcb15a5@jamessonyvaio>; from James@Seng.cc on Mon, May 28, 2001 at 05:51:08AM +0800
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James Seng/Personal <James@Seng.cc> wrote:

> *If* we adopt IDNA, then telnet/ssh etc have to be upgraded to be IDNA
> compatible.

Just to be perfectly clear:  If we adopt IDNA, then telnet/ssh etc.
have to be upgraded to be IDNA *friendly*, but they are already IDNA
*compatible*.  While people are waiting for those upgrades, they are not
completely out of luck.  They can do something like:

telnet `ace NATIVECHARACTERS`

where ace is a single program that can be used in this way with telnet,
ssh, ftp, finger, etc.

AMC



From owner-idn@ops.ietf.org  Sun May 27 18:33:20 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA12274
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 18:33:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1548yi-000M2j-00
	for idn-data@psg.com; Sun, 27 May 2001 15:25:40 -0700
Received: from f86.law15.hotmail.com ([64.4.23.86] helo=hotmail.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 1548yh-000Lz5-00
	for idn@ops.ietf.org; Sun, 27 May 2001 15:25:39 -0700
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Sun, 27 May 2001 15:25:08 -0700
Received: from 24.130.82.137 by lw15fd.law15.hotmail.msn.com with HTTP;	Sun, 27 May 2001 22:25:08 GMT
X-Originating-IP: [24.130.82.137]
From: "Sherin Alsoudani" <sherinalsoudani@hotmail.com>
To: amc@cs.berkeley.edu, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
Date: Sun, 27 May 2001 15:25:08 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F86ip68V8zDv60gxapz0000f8ba@hotmail.com>
X-OriginalArrivalTime: 27 May 2001 22:25:08.0547 (UTC) FILETIME=[E2F83130:01C0E6FB]
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dear Adam,

I have some very strong reservations about some of the points you have 
raised.  Though I do not consider myself a DNS expert by any means, I 
believe my experience as a software developer gives me enough insight to 
hopefully understand most of what you wrote.

My comments are interspersed below.

>From: "Adam M. Costello" <amc@cs.berkeley.edu>
>To: idn@ops.ietf.org
>Subject: Re: [idn] UTF-8 / RACE
>Date: Sun, 27 May 2001 21:30:52 +0000
>
>Some people seem to be arguing that using ACE requires no less (or even
>more) upgrading of software than using UTF-8 without ACE.  While it may
>be true that ACE-fully-working-everywhere requires as much upgrading as
>UTF-8-working-fully-everywhere, that comparison overlooks an important
>point.
>
>ACE affords incremental deployment much better than no-ACE.  Suppose I
>am considering getting an IDN for my domain.  With ACE, this will make
>things better for some users (who have upgraded their clients to decode
>the ACE) and worse for others (who have old clients and will see ugly
>ACEs) but nothing will actually break (mail will get through, web pages
>will load, etc).

This is completely wrong because it disregards the human face of the 
Internet.  This working group should not just focus on "clients", 
"applications", and "protocols".  We should keep in mind the bottom line: 
the Internet is basically a medium for communication.  If by converting to 
ACE, it makes it easier for the client/application/protocol developers, but 
makes it harder for the *average* person to get on the Internet, then I have 
strong reservations against ACE.  In my part of the world, the Middle East, 
the hugely overwhelming majority of the population is not English-fluent at 
all.  To say that "nothing will actually break" is wrong - this is only at 
the protocol etc. level.  However, at the human level, if the IDN is an ACE, 
and my application does not support the proper display of that IDN, then 
something most definitely WILL break: the human user of that application 
will simply not type in that IDN.

To me, the final result is the same: even if ACE is inherently friendlier to 
the existing infrastructure, most people will not be able to utilize IDN's 
because they will not understand the ACE encoded name whatsoever.  People 
will have to upgrade their applications.

>But without ACE, if I get an IDN for my domain, this will make things
>better for some users (who have upgraded their clients, or who are lucky
>enough to already be using UTF-8 clients) and will *completely* *break*
>things for other users (mail will not get through, web pages will not
>load, etc).  There may be nothing those users can do to fix it, because
>the breakage might be happening in their provider's software.  The
>provider might be very slow to upgrade, because 99% of their customers
>might be English speakers, and the other 1% are just screwed.

This is not true.  In the Middle East, there are at least two or three 
providers of IDN's currently: Walid, i-DNS, and Nativ Name.  As far as I 
understand, Native Name provides a UTF-8 solution, I do not know about the 
others.  The response has been very strong from what I know: providers ARE 
switching to UTF-8; there is a good chance that my ISP will upgrade to a 
UTF-8 compatible software assuming they have not done so already.  I believe 
it is a later version of BIND that is necessary.

I also read on this list that CNNIC has chosen UTF-8 as their current 
encoding.  This is another indication that providers ARE switching.

Another thing: assuming 99% English and 1% non-English in the Middle East is 
completely wrong.  I, and many other IT professionals here, are committed to 
bringing our people online.  Most of our people have little understanding of 
the written Arabic language, let alone English.

>With ACE, people might have to put visible ACEs in some config
>files, which is annoying, but at least it will work.  Eventually
>the application might get upgraded to support native characters in
>the config files and then things will get easier.  Without ACE, the
>application will simply be unusable with IDNs until it is upgraded.
>
>Conclusion: There should be ACE.

This conclusion is premature to say the least.

>Next question:  Given that there will be ACE, should DNS support 8-bit
>queries in addition to ACE queries?  I don't know.  No matter what
>is recommended or discouraged, some DNS servers will probably try to
>guess the encoding of 8-bit queries.  This will help old clients, but
>increases the risk of spoofing, and allows some applications to be
>lazier about upgrading.  I haven't yet formed an opinion on this.
>
>Next question:  Should ACE ever be phased out?  I don't think so.  Very
>few systems will ever support all Unicode characters, so applications
>will sometimes try to display IDNs containing unsupported characters.
>What should they display?  They should display the ACE, because that's
>no uglier than anything else they might display, and has the added bonus
>that you can copy it into any other application and it will still work.
>
>Furthmore, domain names are first and foremost *global* identifiers
>intended to be used by *humans* *anywhere* to refer to network objects.
>For people who know the Unicode characters in the domain name, the
>native representation is easiest, but for the billions of people who
>don't know those characters, the ACE is much easier to type, write,
>speak, and visually compare.  (The Roman alphabet is one of the smallest
>alphabets in existence, and is already widely recognized.  If you have
>to chose a fallback character set for everyone to learn, that's the best
>choice.)

If you wish to try to come to Egypt or any other place in the Middle East, 
and convince people here that English is a good choice even as a "fallback 
character set for everyone to learn", I do not envy your task as you will 
not be taken seriously.  I do not understand your comment of "billions of 
people" who do not know "those characters", where those characters are the 
native language of the people.  This is so patently wrong to me that I 
believe I must have misunderstood you.  I personally am not interested in 
seeing English propagated as the default language, as a half solution for 
multilingal domains.  It is impossible to ask us to learn the Roman language 
simply to satisfy the protocol writers.  Instead we are happy to go with a 
tougher solution that will give more access to the average, non-English 
speaker ultimately.  If we have to wait a little or a lot longer for that to 
occur, that is worth it compared to a short-term solution that requires me 
to send my mother to English spelling school.

>I'm not saying that various protocols shouldn't allow 8-bit encoding in
>addition to ACE (I have no opinion on that yet), I'm just saying that
>ACE will always serve a useful function, and should never be deprecated.
>
>AMC
>

Sherin

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com




From owner-idn@ops.ietf.org  Sun May 27 18:41:26 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA12306
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 18:41:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 15496I-000MRW-00
	for idn-data@psg.com; Sun, 27 May 2001 15:33:30 -0700
Received: from arachnid.ehsco.com ([209.31.7.46] helo=Arachnid.NTRG.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 15496H-000MRP-00
	for idn@ops.ietf.org; Sun, 27 May 2001 15:33:29 -0700
Received: from ehsco.com (nat-external.ehsco.com [209.31.7.42])
          by Arachnid.NTRG.com (Netscape Messaging Server 3.62)  with ESMTP
          id 573; Sun, 27 May 2001 15:33:27 -0700
Message-ID: <3B1180B6.8939BDC1@ehsco.com>
Date: Sun, 27 May 2001 15:33:27 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Adam M. Costello" <amc@cs.berkeley.edu>
CC: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
References: <F599No5I9BADCDLTyHU0000f121@hotmail.com> <7544575.990957280@localhost> <20010527165903.5833.qmail@cr.yp.to> <079c01c0e6e4$3bf7ee50$7dcb15a5@jamessonyvaio> <20010527202613.5518.qmail@cr.yp.to> <20010527213052.C17337@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


> Some people seem to be arguing that using ACE requires no less (or
> even more) upgrading of software than using UTF-8 without ACE.

Some of us are arguing the cost of UTF8-with-ACE is only slightly greater
than the cost of ACE-only.

Some of us are also arguing that the cost of ACE-now-UTF8-later is 2x the
cost of UTF8-with-ACE.

> ACE affords incremental deployment much better than no-ACE.

ACE is analogous to dipping your toe into the kiddie pool. Even if you
find out that the water is comfortable, you won't be able to thoroughly
enjoy it.

The international user community doesn't end at email and web. Think about
the end-user networks out there with admins who are struggling with
ASCII-based DHCP, lpd, and just about everything else that ACE doesn't
help with. Worse, it makes embracing IDNS more difficult for them, since
they have to go from using ASCII to a highly cryptic naming service that
is outright user-hostile. It is highly unlikely that those services will
ever be fixed until a UTF8 form is developed by us, embraced by the WG,
and coded by the vendor community.

ACE is transitional, not a destination. The cost and time of getting to
the real destination can be shortened by embracing it early.

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



From owner-idn@ops.ietf.org  Sun May 27 21:24:01 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA12788
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 21:23:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154BUk-000PaB-00
	for idn-data@psg.com; Sun, 27 May 2001 18:06:54 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154BUj-000Pa5-00
	for idn@ops.ietf.org; Sun, 27 May 2001 18:06:53 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id VAA29976;
        Sun, 27 May 2001 21:06:45 -0400 (EDT)
Message-Id: <200105280106.VAA29976@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] UTF-8 / RACE 
In-reply-to: Your message of "27 May 2001 16:59:03 -0000."
             <20010527165903.5833.qmail@cr.yp.to> 
Date: Sun, 27 May 2001 21:06:45 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> In contrast, ACE guarantees that the data is unreadable for users of
> today's non-ACE software. 

so what?  UTF-8 guarantees that the data is unreadable for users of
today's non UTF-8 software.  and even the software that today can
display UTF-8 and accept it as input, cannot reliably compare two 
UTF-8 representations of an IDN and see if they are equivalent.

> When you claim that an ACE IDN is transmitted
> perfectly, you are ignoring the final step: getting the IDN into the
> user's head!

with ACE, we have the case that zero existing software can display them
properly or accept them as input.  this software will have to be upgraded
for those who wish to use IDNs, but at least it will be obvious that this
software has faults that need to be corrected.  in the meantime, uses of
IDNs that do not require  input or display (say, replying to an email 
message, relaying mail from one MTA to another, or clicking on a URL 
link) will continue to work.

with UTF-8, we have the case that some existing software can display them
properly and/or accept them as input.  however, this software will not
nameprep IDNs accepted as input, and thus, for some languages, the 
software will not reliably lookup IDNs even though it will accept them as
input.  these faults will not be so obvious to the user as those with ACE.

summary: in either case software has to be upgraded.  ACE is less likely
to disrupt operations; its flaws are more likely to be noticed and therefore
more likely to be fixed, and ACE is more amenable to incremental upgrade.

> Yes, there are a few pieces of software that have to be upgraded and
> redeployed to make UTF-8 IDNs work. But there are many more pieces of
> software that have to be upgraded and redeployed to make ACE IDNs work.
> See http://cr.yp.to/proto/idn.html for details.

this is a mischaracterization, based on numerous erroneous assumptions.

Keith



From owner-idn@ops.ietf.org  Sun May 27 21:27:34 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA12810
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 21:27:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154BcF-000PeN-00
	for idn-data@psg.com; Sun, 27 May 2001 18:14:39 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154BcE-000PeH-00
	for idn@ops.ietf.org; Sun, 27 May 2001 18:14:38 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id VAA00203;
        Sun, 27 May 2001 21:14:36 -0400 (EDT)
Message-Id: <200105280114.VAA00203@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] UTF-8 / RACE 
In-reply-to: Your message of "27 May 2001 20:26:13 -0000."
             <20010527202613.5518.qmail@cr.yp.to> 
Date: Sun, 27 May 2001 21:14:36 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> My web page carefully specifies details of the ACE solution: where ACE
> is used, where it is not used, and what has to be changed to make that
> work. 

yes, but those details are chosen to favor the argument you want to make.
it's unlikely that a real ACE solution would work that way.

> The reason that gethostbyname() has to be upgraded, for example,
> is that ACE is not used in ``command lines for telnet, ssh, etc.'' but
> ACE is used in ``DNS queries and responses.''

wrong.  gethostbyname should not be upgraded, because this would cause
harm to applications that expect ASCII domain names.   it's pure fantasy
to think that you can simply change gethostbyname and expect most
applications to start support UTF-8.  some will work, some won't,
and some of those that appear to work will work unreliably.

changing an existing interface underneath an application is a good
way to make that application fail in subtle ways.

> I'm willing to analyze the costs of other IDN solutions. But I'm not
> interested in proposals that don't actually provide internationalized
> domain names. 

nor do you appear to be interested in analyzing the difficulties 
associated with incremental transitions of UTF-8, since you 
consistently fail to consider them.

> It's idiotic to claim that we have Greek domain names if
> Greek users aren't seeing Greek alphas and betas on the screen. (Does
> anyone dispute this?)

it's idiotic to claim to perform an analysis when you refuse to consider
significant and obvious costs and failure modes.



From owner-idn@ops.ietf.org  Sun May 27 22:10:05 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA13905
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 22:10:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154CDX-0000TY-00
	for idn-data@psg.com; Sun, 27 May 2001 18:53:11 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154CDV-0000TS-00
	for idn@ops.ietf.org; Sun, 27 May 2001 18:53:10 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 1D314FFC04; Mon, 28 May 2001 09:55:45 +0800 (SGT)
Message-ID: <095001c0e718$dbe911d0$7dcb15a5@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Sherin Alsoudani" <sherinalsoudani@hotmail.com>, <amc@cs.berkeley.edu>,
        <idn@ops.ietf.org>
References: <F86ip68V8zDv60gxapz0000f8ba@hotmail.com>
Subject: Re: [idn] UTF-8 / RACE
Date: Mon, 28 May 2001 09:52:32 +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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sherin,

I agree with most of your comment here on user aspect and friendliness.
It is certainly one of the consideration the Working Group need to
balance with interoperability and usefulness.

However, I am curious about one point: You made an assumption that ACE
would be unfriendly to end-users. Why is that so?

And how would a UTF-8 solution more friendly given that most of the
Arabic Internet is using Sakhr encoding or CP1256?

-James Seng

----- Original Message -----
From: "Sherin Alsoudani" <sherinalsoudani@hotmail.com>
To: <amc@cs.berkeley.edu>; <idn@ops.ietf.org>
Sent: Monday, May 28, 2001 6:25 AM
Subject: Re: [idn] UTF-8 / RACE


> Dear Adam,
>
> I have some very strong reservations about some of the points you have
> raised.  Though I do not consider myself a DNS expert by any means, I
> believe my experience as a software developer gives me enough insight
to
> hopefully understand most of what you wrote.
>
> My comments are interspersed below.
>
> >From: "Adam M. Costello" <amc@cs.berkeley.edu>
> >To: idn@ops.ietf.org
> >Subject: Re: [idn] UTF-8 / RACE
> >Date: Sun, 27 May 2001 21:30:52 +0000
> >
> >Some people seem to be arguing that using ACE requires no less (or
even
> >more) upgrading of software than using UTF-8 without ACE.  While it
may
> >be true that ACE-fully-working-everywhere requires as much upgrading
as
> >UTF-8-working-fully-everywhere, that comparison overlooks an
important
> >point.
> >
> >ACE affords incremental deployment much better than no-ACE.  Suppose
I
> >am considering getting an IDN for my domain.  With ACE, this will
make
> >things better for some users (who have upgraded their clients to
decode
> >the ACE) and worse for others (who have old clients and will see ugly
> >ACEs) but nothing will actually break (mail will get through, web
pages
> >will load, etc).
>
> This is completely wrong because it disregards the human face of the
> Internet.  This working group should not just focus on "clients",
> "applications", and "protocols".  We should keep in mind the bottom
line:
> the Internet is basically a medium for communication.  If by
converting to
> ACE, it makes it easier for the client/application/protocol
developers, but
> makes it harder for the *average* person to get on the Internet, then
I have
> strong reservations against ACE.  In my part of the world, the Middle
East,
> the hugely overwhelming majority of the population is not
English-fluent at
> all.  To say that "nothing will actually break" is wrong - this is
only at
> the protocol etc. level.  However, at the human level, if the IDN is
an ACE,
> and my application does not support the proper display of that IDN,
then
> something most definitely WILL break: the human user of that
application
> will simply not type in that IDN.
>
> To me, the final result is the same: even if ACE is inherently
friendlier to
> the existing infrastructure, most people will not be able to utilize
IDN's
> because they will not understand the ACE encoded name whatsoever.
People
> will have to upgrade their applications.
>
> >But without ACE, if I get an IDN for my domain, this will make things
> >better for some users (who have upgraded their clients, or who are
lucky
> >enough to already be using UTF-8 clients) and will *completely*
*break*
> >things for other users (mail will not get through, web pages will not
> >load, etc).  There may be nothing those users can do to fix it,
because
> >the breakage might be happening in their provider's software.  The
> >provider might be very slow to upgrade, because 99% of their
customers
> >might be English speakers, and the other 1% are just screwed.
>
> This is not true.  In the Middle East, there are at least two or three
> providers of IDN's currently: Walid, i-DNS, and Nativ Name.  As far as
I
> understand, Native Name provides a UTF-8 solution, I do not know about
the
> others.  The response has been very strong from what I know: providers
ARE
> switching to UTF-8; there is a good chance that my ISP will upgrade to
a
> UTF-8 compatible software assuming they have not done so already.  I
believe
> it is a later version of BIND that is necessary.
>
> I also read on this list that CNNIC has chosen UTF-8 as their current
> encoding.  This is another indication that providers ARE switching.
>
> Another thing: assuming 99% English and 1% non-English in the Middle
East is
> completely wrong.  I, and many other IT professionals here, are
committed to
> bringing our people online.  Most of our people have little
understanding of
> the written Arabic language, let alone English.
>
> >With ACE, people might have to put visible ACEs in some config
> >files, which is annoying, but at least it will work.  Eventually
> >the application might get upgraded to support native characters in
> >the config files and then things will get easier.  Without ACE, the
> >application will simply be unusable with IDNs until it is upgraded.
> >
> >Conclusion: There should be ACE.
>
> This conclusion is premature to say the least.
>
> >Next question:  Given that there will be ACE, should DNS support
8-bit
> >queries in addition to ACE queries?  I don't know.  No matter what
> >is recommended or discouraged, some DNS servers will probably try to
> >guess the encoding of 8-bit queries.  This will help old clients, but
> >increases the risk of spoofing, and allows some applications to be
> >lazier about upgrading.  I haven't yet formed an opinion on this.
> >
> >Next question:  Should ACE ever be phased out?  I don't think so.
Very
> >few systems will ever support all Unicode characters, so applications
> >will sometimes try to display IDNs containing unsupported characters.
> >What should they display?  They should display the ACE, because
that's
> >no uglier than anything else they might display, and has the added
bonus
> >that you can copy it into any other application and it will still
work.
> >
> >Furthmore, domain names are first and foremost *global* identifiers
> >intended to be used by *humans* *anywhere* to refer to network
objects.
> >For people who know the Unicode characters in the domain name, the
> >native representation is easiest, but for the billions of people who
> >don't know those characters, the ACE is much easier to type, write,
> >speak, and visually compare.  (The Roman alphabet is one of the
smallest
> >alphabets in existence, and is already widely recognized.  If you
have
> >to chose a fallback character set for everyone to learn, that's the
best
> >choice.)
>
> If you wish to try to come to Egypt or any other place in the Middle
East,
> and convince people here that English is a good choice even as a
"fallback
> character set for everyone to learn", I do not envy your task as you
will
> not be taken seriously.  I do not understand your comment of "billions
of
> people" who do not know "those characters", where those characters are
the
> native language of the people.  This is so patently wrong to me that I
> believe I must have misunderstood you.  I personally am not interested
in
> seeing English propagated as the default language, as a half solution
for
> multilingal domains.  It is impossible to ask us to learn the Roman
language
> simply to satisfy the protocol writers.  Instead we are happy to go
with a
> tougher solution that will give more access to the average,
non-English
> speaker ultimately.  If we have to wait a little or a lot longer for
that to
> occur, that is worth it compared to a short-term solution that
requires me
> to send my mother to English spelling school.
>
> >I'm not saying that various protocols shouldn't allow 8-bit encoding
in
> >addition to ACE (I have no opinion on that yet), I'm just saying that
> >ACE will always serve a useful function, and should never be
deprecated.
> >
> >AMC
> >
>
> Sherin
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
>




From owner-idn@ops.ietf.org  Sun May 27 22:15:37 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA13927
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 22:15:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154CKV-0000Wm-00
	for idn-data@psg.com; Sun, 27 May 2001 19:00:23 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154CKU-0000Wg-00
	for idn@ops.ietf.org; Sun, 27 May 2001 19:00:22 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id WAA00572;
        Sun, 27 May 2001 22:00:18 -0400 (EDT)
Message-Id: <200105280200.WAA00572@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Adam M. Costello" <amc@cs.berkeley.edu>
cc: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE 
In-reply-to: Your message of "Sun, 27 May 2001 21:30:52 -0000."
             <20010527213052.C17337@arwen.cs.berkeley.edu> 
Date: Sun, 27 May 2001 22:00:18 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Conclusion: There should be ACE.

concur.  it's the only way to get incremental deployment of IDNs
without massive operational disruption.

> Next question:  Given that there will be ACE, should DNS support 8-bit
> queries in addition to ACE queries? 

the value in doing so is mostly psychological.  applications that are
modified to deal with UTF-8 natively will call a different routine
than gethostbyname() to look up IDNs - this routine can easily  convert 
nameprepped UTF-8 IDNs to ACE format before the query goes on the wire.
similarly, gethostbyaddr() equivalents can convert ACE results from
a DNS query to UTF- results.  and the conversion routines will also
be available to those applications that need them.

still, I don't see any harm in having a native UTF-8 DNS query
interface if we can achieve the following:

- delegation paths for UTF-8 are the same as for ACE
  (queries for equivalent names go to the same servers)
- results of a query are consistent between the two encoding schemes
  (a query of one type made to a server produces equivalent results
  - modulo encoding - as a query of the other type)
- success/failure semantics are the same for the two
  (if a query using one encoding succeeds or fails, the same 
  should be true for the same query using the other encoding)
- delay characteristics are similar for the two

however, that might be tall order, given (a) the need to upgrade
DNS servers to support UTF-8 comparisons (between query strings
and zone files where the names aren't nameprepped by the editor),
and (b) problems with sending EDNS queries through old DNS servers.
even if it works, it could take some time to work out the details.

> Next question:  Should ACE ever be phased out?  I don't think so. 

nor do I.  consider that if ACE is used in email, folks will have stored
email dating back for many years.  if ACE were phased out it could 
needlessly make those email addresses invalid.

never is a long time.  but I don't think we can reliably predict when 
ACE will no longer be needed.  we might discover many years from now 
that this is the case, but we should not try to establish a deadline.

Keith



From owner-idn@ops.ietf.org  Sun May 27 22:30:39 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA14311
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 22:30:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154CZc-0000ew-00
	for idn-data@psg.com; Sun, 27 May 2001 19:16:00 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154CZb-0000ef-00
	for idn@ops.ietf.org; Sun, 27 May 2001 19:15:59 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 154CZa-00058s-00; Sun, 27 May 2001 19:15:58 -0700
Date: Mon, 28 May 2001 02:15:58 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
Message-ID: <20010528021558.G17337@arwen.cs.berkeley.edu>
References: <F599No5I9BADCDLTyHU0000f121@hotmail.com> <7544575.990957280@localhost> <20010527165903.5833.qmail@cr.yp.to> <079c01c0e6e4$3bf7ee50$7dcb15a5@jamessonyvaio> <20010527202613.5518.qmail@cr.yp.to> <20010527213052.C17337@arwen.cs.berkeley.edu> <3B1180B6.8939BDC1@ehsco.com> <F86ip68V8zDv60gxapz0000f8ba@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <F86ip68V8zDv60gxapz0000f8ba@hotmail.com>; from sherinalsoudani@hotmail.com on Sun, May 27, 2001 at 03:25:08PM -0700
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This message contains two replies, one to Eric Hall and one to Sherin
Alsoudani.

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

> Some of us are arguing the cost of UTF8-with-ACE is only slightly
> greater than the cost of ACE-only.

I don't claim otherwise.

> Some of us are also arguing that the cost of ACE-now-UTF8-later is 2x
> the cost of UTF8-with-ACE.

I don't claim otherwise.  I made no argument about ACE-only versus
ACE-with-UTF8.  I merely argued that ACE is good and should exist.

> Think about the end-user networks out there with admins who are
> struggling with ASCII-based DHCP, lpd, and just about everything else
> that ACE doesn't help with.

ACE helps with all of them by allowing administrators to put IDNs in the
config files now, before the software has been upgraded, if they have an
urgent need.  There is nothing stopping any software from adding support
for UTF-8 (or any other encoding) in their config files, and I doubt
anyone here would want to discourage that.

As for how those protocols represent domain names on the wire, that's
another question, I don't know, but I think that has less of an impact
on the admins.

> It is highly unlikely that those services will ever be fixed until a
> UTF8 form is developed by us...

As soon as we have fully specified the ACE form, the UTF-8 form is
implicitly defined.

Sherin Alsoudani <sherinalsoudani@hotmail.com> wrote:

> To say that "nothing will actually break" is wrong - this is only at
> the protocol etc. level.  However, at the human level, if the IDN is
> an ACE, and my application does not support the proper display of that
> IDN, then something most definitely WILL break: the human user of that
> application will simply not type in that IDN.

Some (maybe most) people will not type in the ACE, and that can be
considered broken.  But someone who really needs to access that domain
name before their application has been upgraded has the option of typing
in the ACE.  And besides, typing domain names is not the only way to use
them.  Replying to mail will work, clicking on hyperlinks will work,
checking SSL certificates will work, etc.  Without ACE a lot of those
operations would break for a lot of users, but with ACE they completely
work for all users.

> People will have to upgrade their applications.

Yes, with or without ACE, people will have to upgrade their
applications.  But with ACE, upgrading their own applications is
sufficient.  Without ACE, they need to not only upgrade their
applications, but also wait for other people to upgrade the
infrastructure, which is out of their control.

> > The provider might be very slow to upgrade, because 99% of their
> > customers might be English speakers, and the other 1% are just
> > screwed.
>
> This is not true...  The response has been very strong from what I
> know: providers ARE switching to UTF-8...

I didn't claim that all providers would be slow to upgrade, I'm saying
that some providers might be slow to upgrade, and without ACE, users
will not be in control, they'll need to wait for the infrastructure to
catch up with them.

> Another thing: assuming 99% English and 1% non-English in the Middle
> East is completely wrong.

I said nothing about the Middle-East.  What about Arabic speakers in the
rest of the world, where they are a small minority?  I bet they'd like
to access the Arabic domain names when they appear.  What about people
who don't even speak Arabic but like to listen to Arabic music?  The
internet is supposed to be for everyone; it's supposed to bring people
together, not put up walls between them.  Without ACE, a domain that
uses an IDN would basically be saying "foreigners keep out".

> I do not understand your comment of "billions of people" who do
> not know "those characters", where those characters are the native
> language of the people.  This is so patently wrong to me that I
> believe I must have misunderstood you.

I believe you must have.  There are billions of people in the world who
do not know Arabic characters, and whose computers do not support Arabic
characters, but sometimes those people will want to use an Arabic domain
name.  Maybe to hear some music, maybe to send a reply to all recipients
of an email message, one of whom is bilingual and has an Arabic address.

> I personally am not interested in seeing English propagated as the
> default language, as a half solution for multilingal domains.  It is
> impossible to ask us to learn the Roman language simply to satisfy the
> protocol writers.

I am not asking anyone to learn any language.  I am suggesting that
occasionally an Arabic speaker will want to access a Chinese domain,
and before they get around to learning several thousand Han characters,
and before they get around to upgrading their computer to support those
characters, they might find it more convenient to learn 52 Roman letters
(38 if you consider upper/lowercase pairs that look the same) and use
the ACE.

> If we have to wait a little or a lot longer for that to occur, that is
> worth it compared to a short-term solution that requires me to send my
> mother to English spelling school.

I'm not asking your mother to use Roman letters to access Arabic
domains.  You should upgrade her applications so she doesn't see the ACE
when accessing Arabic domains.

AMC



From owner-idn@ops.ietf.org  Sun May 27 22:40:53 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA14985
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 22:40:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154Ckr-0000ol-00
	for idn-data@psg.com; Sun, 27 May 2001 19:27:37 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154Ckq-0000oe-00
	for idn@ops.ietf.org; Sun, 27 May 2001 19:27:36 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id WAA00791;
        Sun, 27 May 2001 22:27:32 -0400 (EDT)
Message-Id: <200105280227.WAA00791@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: "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE 
In-reply-to: Your message of "Sun, 27 May 2001 15:33:27 PDT."
             <3B1180B6.8939BDC1@ehsco.com> 
Date: Sun, 27 May 2001 22:27:32 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > Some people seem to be arguing that using ACE requires no less (or
> > even more) upgrading of software than using UTF-8 without ACE.
> 
> Some of us are arguing the cost of UTF8-with-ACE is only slightly greater
> than the cost of ACE-only.

this is probably true.  but the biggest part of the 'cost' in adding
UTF8 support to an ACE solution is probably not the implementation 
effort but the additional delay required to figure out how to make
the two work reliably and consistently together given the limitations
of presently-deployed DNS servers.

if getting the UTF8 part right would delay the adoption of a standard
ACE enough that there were significant deployment of nonstandard
IDN solutions, this might make it far more difficult to ever get a
standard solution (be it ACE, UTf-8 or whatever) in place.

this is why I favor moving forward with an ACE solution now.

> Some of us are also arguing that the cost of ACE-now-UTF8-later is 2x the
> cost of UTF8-with-ACE.

I think this presumes that UTF8-with-ACE can be deployed in the same 
timeframe as ACE-now-UTF8-later, and I don't think that's the case.
My guess is six months to a year additional standards work just to figure 
out how to make the the ACE and UTF-8 queries work consistently with
one another.

> > ACE affords incremental deployment much better than no-ACE.
> 
> ACE is analogous to dipping your toe into the kiddie pool. Even if you
> find out that the water is comfortable, you won't be able to thoroughly
> enjoy it.

someone recently told me to be careful when using analogies, because it 
tempts people to argue about whether then analogies are valid rather than
about the matter at hand.

I don't think it's fair to characterize ACE as a halfway solution.
Most applications that get upgraded to use ACE will get every bit as much 
of a facelift as they would if they were upgraded to use UTF-8.    The only
difference is that they will encode IDNs using ACE "on the wire" when
exchanging IDNs with applications that might not have been upgraded.

The real issue is not the difficulty in upgrading individual applications, 
but the difficulty in upgrading all implementations of a given application.   
And the latter is far easier if you can upgrade each component incrementally 
without disrupting service.

> The international user community doesn't end at email and web. Think about
> the end-user networks out there with admins who are struggling with
> ASCII-based DHCP, lpd, and just about everything else that ACE doesn't
> help with. 

I think that's a mischaracterization.   The format that is used for 
on-the-wire DNS queries is almost completely irrelevant to applications -
since the vast majority of applications will be using standard APIs
which convert between native character set and encoding and those
used on the wire.  For this purpose, the application doesn't care
whether the format is UTF-8 or ACE.  But the applications that currently
use DNS names are expecting ASCII names, ACE does help ease 
the transition with these, and these applications do include DHCP and lpd 
and anything else that uses DNS names. 

> Worse, it makes embracing IDNS more difficult for them, since
> they have to go from using ASCII to a highly cryptic naming service that
> is outright user-hostile. It is highly unlikely that those services will
> ever be fixed until a UTF8 form is developed by us, embraced by the WG,
> and coded by the vendor community.

think of it another way - there's no way that the IDN WG can "fix" these
services, because each service has its own transition issues.  each 
protocol must be "fixed" by people who understand that protocol.  the
IDN WG cannot simply say "all protocols will use UTF-8 IDNs".  a statement
like that would be tantamount to saying that we cannot move to UTF-8 
IDNs until we understand how to fix every major application - and that 
would take decades.

> ACE is transitional, not a destination. The cost and time of getting to
> the real destination can be shortened by embracing it early.

The Internet itself is transitional.  It continues to evolve, and in the
past we have not demonstrated a good ability to predict how it will evolve.
However we do have some experience that indicates that solutions which
require massive infrastructure upgrades are far less likely to succeed
than solutions which were designed to allow incremental upgrading.

Keith



From owner-idn@ops.ietf.org  Sun May 27 22:50:08 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA15066
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 22:50:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154CwM-00011W-00
	for idn-data@psg.com; Sun, 27 May 2001 19:39:30 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154CwL-00011P-00
	for idn@ops.ietf.org; Sun, 27 May 2001 19:39:29 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id WAA00909;
        Sun, 27 May 2001 22:39:26 -0400 (EDT)
Message-Id: <200105280239.WAA00909@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Sherin Alsoudani" <sherinalsoudani@hotmail.com>
cc: amc@cs.berkeley.edu, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE 
In-reply-to: Your message of "Sun, 27 May 2001 15:25:08 PDT."
             <F86ip68V8zDv60gxapz0000f8ba@hotmail.com> 
Date: Sun, 27 May 2001 22:39:25 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> >ACE affords incremental deployment much better than no-ACE.  Suppose I
> >am considering getting an IDN for my domain.  With ACE, this will make
> >things better for some users (who have upgraded their clients to decode
> >the ACE) and worse for others (who have old clients and will see ugly
> >ACEs) but nothing will actually break (mail will get through, web pages
> >will load, etc).
> 
> This is completely wrong because it disregards the human face of the
> Internet. 

I don't see how you get that idea.  Both ACE and UTF-8 solutions would
accept and display IDNs in native form for upgraded applciations.
Human users of upgraded applications would see no difference in the
input or display of IDNs.  

The only difference that they would see is that:

- the ACE solution gets deployed more quickly
- the ACE solution is more reliable in the near term
- the ACE solution works better with interoperating with non-upgraded clients

you are correct that the Internet is a medium for human communications.
but humans need for those communications to be reliable, and going directly
to UTF-8 disrupts that reliability.

here is one way of comparing the two:

- if we use ACE, human users will get annoyed when those ACE names are
  displayed by non-upgraded tools, and when they leak
  (as for example when an email header address is copied into the message 
  text)

- if we use UTF-8, human users will get annoyed when those UTF-8 names
  are displayed by tools that don't support UTF-8, and when they
  leak to environments that don't display UTF-8, and when they do not
  work as reliably as before (because the UTF-8 is causing sutble
  bugs in software that was written to expect ASCII), and/or they cannot
  interoperate with tools that are not upgraded.

people will complain no matter which path we take.  but the former approach
works better and produces fewer problems.

Keith 



From owner-idn@ops.ietf.org  Sun May 27 23:37:40 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA15685
	for <idn-archive@lists.ietf.org>; Sun, 27 May 2001 23:37:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154DeT-0001lV-00
	for idn-data@psg.com; Sun, 27 May 2001 20:25:05 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 154DeS-0001lG-00
	for idn@ops.ietf.org; Sun, 27 May 2001 20:25:04 -0700
Received: (qmail 9402 invoked by uid 1001); 28 May 2001 03:25:18 -0000
Date: 28 May 2001 03:25:18 -0000
Message-ID: <20010528032518.26680.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
References: <F86ip68V8zDv60gxapz0000f8ba@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

It's very helpful to have these reports from countries that don't use
Latin-based character sets. The users would benefit tremendously from a
working IDN solution; I hope the IDN WG doesn't ignore their needs.

Sherin Alsoudani writes:
> The response has been very strong from what I know: providers ARE 
> switching to UTF-8; there is a good chance that my ISP will upgrade to
> a UTF-8 compatible software assuming they have not done so already.  I
> believe it is a later version of BIND that is necessary.

Could you ask your ISP for more details about what changes it is making?

The only BIND problem with UTF-8 is the gethostbyname() library, which
rejects 8-bit characters in violation of RFC 2181. Current versions of
BIND support no-check-names in /etc/resolv.conf to fix this behavior.

---Dan



From owner-idn@ops.ietf.org  Mon May 28 00:16:13 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA16151
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 00:16:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154E9T-0001yo-00
	for idn-data@psg.com; Sun, 27 May 2001 20:57:07 -0700
Received: from drugs.dv.isc.org ([130.155.191.236])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154E9R-0001yh-00
	for idn@ops.ietf.org; Sun, 27 May 2001 20:57:06 -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 f4S3tjv60619
	for <idn@ops.ietf.org>; Mon, 28 May 2001 13:55:46 +1000 (EST)
	(envelope-from marka@nominum.com)
Message-Id: <200105280355.f4S3tjv60619@drugs.dv.isc.org>
To: idn@ops.ietf.org
From: Mark.Andrews@nominum.com
Mail-Followup-To: idn@ops.ietf.org 
Subject: Re: [idn] UTF-8 / RACE 
In-reply-to: Your message of "28 May 2001 03:25:18 GMT."
             <20010528032518.26680.qmail@cr.yp.to> 
Date: Mon, 28 May 2001 13:55:44 +1000
Sender: owner-idn@ops.ietf.org
Precedence: bulk


> The only BIND problem with UTF-8 is the gethostbyname() library, which
> rejects 8-bit characters in violation of RFC 2181.

	gethostbyname() is a client of the DNS and as such is not
	covered by RFC 2181.  gethostbyname() is part of a
	implementation of RFC 952.

	Yes we are talking here about extending RFC 952, however
	that does not imply that it is necessarily safe to extend
	gethostbyname().  The safest thing to do is to specify a
	new API which is defined to accept IHN and return IHN's.
	That way you don't break all the legacy applications when
	you upgrade your shared library.

	If you can extend a existing API, well and good, but it should
	require some action on the part of the application developer to
	get at the extended parts.

> Current versions of BIND support no-check-names in /etc/resolv.conf to
> fix this behavior.
	
	And when you do this you still get a ASCII string back.  Most
	applications don't look at it but it is there.

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



From owner-idn@ops.ietf.org  Mon May 28 00:48:45 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA16474
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 00:48:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154Ely-0002Eb-00
	for idn-data@psg.com; Sun, 27 May 2001 21:36:54 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 154Elx-0002EV-00
	for idn@ops.ietf.org; Sun, 27 May 2001 21:36:53 -0700
Received: (qmail 15135 invoked by uid 1001); 28 May 2001 04:36:39 -0000
Date: 28 May 2001 04:36:39 -0000
Message-ID: <20010528043639.9273.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
References: <079c01c0e6e4$3bf7ee50$7dcb15a5@jamessonyvaio> <20010527202613.5518.qmail@cr.yp.to> <083c01c0e6f7$235b7200$7dcb15a5@jamessonyvaio> <20010527220531.E17337@arwen.cs.berkeley.edu> <F599No5I9BADCDLTyHU0000f121@hotmail.com> <7544575.990957280@localhost> <20010527165903.5833.qmail@cr.yp.to> <079c01c0e6e4$3bf7ee50$7dcb15a5@jamessonyvaio> <20010527202613.5518.qmail@cr.yp.to> <083c01c0e6f7$235b7200$7dcb15a5@jamessonyvaio>
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:
> telnet `ace NATIVECHARACTERS`

Even if that were a complete solution---what do you do about telnet's
open command? or its status display? or the ssh password prompt? etc.---
it would have no advantages over simply fixing gethostbyname().

When I was working out the details of the ACE solution, I was careful to
minimize the number of pieces of code that would have to be upgraded and
redeployed, subject to the constraint of names being encoded as ACE over
the wire. Using ACE on the telnet command line and the ssh command line
and so on would be, to put it bluntly, bad programming.

> with or without ACE, people will have to upgrade their applications

Except, of course, for all the programs that _already_ work with UTF-8.
See http://cr.yp.to/proto/idn.html.

---Dan



From owner-idn@ops.ietf.org  Mon May 28 00:51:03 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA16491
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 00:51:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154Ekp-0002E2-00
	for idn-data@psg.com; Sun, 27 May 2001 21:35:43 -0700
Received: from f157.law15.hotmail.com ([64.4.23.157] helo=hotmail.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154Eko-0002Dm-00
	for idn@ops.ietf.org; Sun, 27 May 2001 21:35:42 -0700
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Sun, 27 May 2001 21:35:11 -0700
Received: from 24.130.82.137 by lw15fd.law15.hotmail.msn.com with HTTP;	Mon, 28 May 2001 04:35:11 GMT
X-Originating-IP: [24.130.82.137]
From: "Sherin Alsoudani" <sherinalsoudani@hotmail.com>
To: James@Seng.cc, amc@cs.berkeley.edu, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
Date: Sun, 27 May 2001 21:35:11 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F157s9U6TOZgkbN6WAv0000976e@hotmail.com>
X-OriginalArrivalTime: 28 May 2001 04:35:11.0685 (UTC) FILETIME=[95122F50:01C0E72F]
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dear James,

It is good to hear that the overall WG is keeping in mind that most of the 
world does not understand English well enough to type in that language.  For 
Arabs, we write from right to left, and we have no notion of upper case and 
lower case, plus it is a phonetic language.  This is why a RACE solution in 
the short-term would be not so good for us in the Middle East.  If the 
members of this WG are seeing the fact of applications being deficient in 
their ability to display RACE-encoded IDN's as a problem, for us in the 
Middle East it is a very big problem.  Arabic and English are very 
different, and our population does not have a strong command of English.  As 
we wait for applications to display RACE properly, it will set us back for a 
long while - that is the crux of the problem I am afraid of.

For example, the number one Internet application in the Middle East today is 
probably Microsoft Internet Explorer.  It already has support for UTF-8.  
Judging from the emails in this group, Microsoft's claims of "just send 
UTF-8" are not enough.  However, for the entire Middle East, the little 
support that comes with IE 5 for Arabic URL's is a definite positive step, 
and there is momentum there.

Note that the assumption of most of the Arabic Internet using CP1256 or 
Sakhr is not entirely accurate.  It is more accurate to state in what 
context is what encoding more popular.  For Web content, you will find more 
sites written using CP1256 but there are some significant implementations 
using UTF-8.  I am happy to see that Mr. Adonis Fakih is already on this 
list since he represents Ayna.com.  Ayna is the number one Arabic portal - 
and it supports UTF-8.

In the context of Arabic URL's however, there is no de facto standard, 
though Microsoft has certainly given us a strong pathway to one via UTF-8.  
Native Name appears to be exploiting that, and it seems to be the 
front-runner at this stage.  I believe it would be easy for the other 
players to do the same thing, including i-DNS and Walid.

I hope this explains my worries James.  In a nutshell, we already have a 
starting point in the Middle East for giving users of the Web portion of the 
Internet access to Arabic domain names using UTF-8.  It works 
"out-of-the-box."  Given that most of the new users of the Internet in the 
Middle East equate the Internet with the Web, I would hate to see that 
momentum die.  Keep in mind that Internet Explorer has over 90% of the 
market in the Middle East due to Netscape 4's inability to display Arabic 
fonts.  Netscape 6 solves this, but it may be well too late.

Sherin

>From: "James Seng/Personal" <James@Seng.cc>
>To: "Sherin Alsoudani" <sherinalsoudani@hotmail.com>, 
><amc@cs.berkeley.edu>, <idn@ops.ietf.org>
>Subject: Re: [idn] UTF-8 / RACE
>Date: Mon, 28 May 2001 09:52:32 +0800
>
>Sherin,
>
>I agree with most of your comment here on user aspect and friendliness.
>It is certainly one of the consideration the Working Group need to
>balance with interoperability and usefulness.
>
>However, I am curious about one point: You made an assumption that ACE
>would be unfriendly to end-users. Why is that so?
>
>And how would a UTF-8 solution more friendly given that most of the
>Arabic Internet is using Sakhr encoding or CP1256?
>
>-James Seng
>
>----- Original Message -----
>From: "Sherin Alsoudani" <sherinalsoudani@hotmail.com>
>To: <amc@cs.berkeley.edu>; <idn@ops.ietf.org>
>Sent: Monday, May 28, 2001 6:25 AM
>Subject: Re: [idn] UTF-8 / RACE
>
>
> > Dear Adam,
> >
> > I have some very strong reservations about some of the points you have
> > raised.  Though I do not consider myself a DNS expert by any means, I
> > believe my experience as a software developer gives me enough insight
>to
> > hopefully understand most of what you wrote.
> >
> > My comments are interspersed below.
> >
> > >From: "Adam M. Costello" <amc@cs.berkeley.edu>
> > >To: idn@ops.ietf.org
> > >Subject: Re: [idn] UTF-8 / RACE
> > >Date: Sun, 27 May 2001 21:30:52 +0000
> > >
> > >Some people seem to be arguing that using ACE requires no less (or
>even
> > >more) upgrading of software than using UTF-8 without ACE.  While it
>may
> > >be true that ACE-fully-working-everywhere requires as much upgrading
>as
> > >UTF-8-working-fully-everywhere, that comparison overlooks an
>important
> > >point.
> > >
> > >ACE affords incremental deployment much better than no-ACE.  Suppose
>I
> > >am considering getting an IDN for my domain.  With ACE, this will
>make
> > >things better for some users (who have upgraded their clients to
>decode
> > >the ACE) and worse for others (who have old clients and will see ugly
> > >ACEs) but nothing will actually break (mail will get through, web
>pages
> > >will load, etc).
> >
> > This is completely wrong because it disregards the human face of the
> > Internet.  This working group should not just focus on "clients",
> > "applications", and "protocols".  We should keep in mind the bottom
>line:
> > the Internet is basically a medium for communication.  If by
>converting to
> > ACE, it makes it easier for the client/application/protocol
>developers, but
> > makes it harder for the *average* person to get on the Internet, then
>I have
> > strong reservations against ACE.  In my part of the world, the Middle
>East,
> > the hugely overwhelming majority of the population is not
>English-fluent at
> > all.  To say that "nothing will actually break" is wrong - this is
>only at
> > the protocol etc. level.  However, at the human level, if the IDN is
>an ACE,
> > and my application does not support the proper display of that IDN,
>then
> > something most definitely WILL break: the human user of that
>application
> > will simply not type in that IDN.
> >
> > To me, the final result is the same: even if ACE is inherently
>friendlier to
> > the existing infrastructure, most people will not be able to utilize
>IDN's
> > because they will not understand the ACE encoded name whatsoever.
>People
> > will have to upgrade their applications.
> >
> > >But without ACE, if I get an IDN for my domain, this will make things
> > >better for some users (who have upgraded their clients, or who are
>lucky
> > >enough to already be using UTF-8 clients) and will *completely*
>*break*
> > >things for other users (mail will not get through, web pages will not
> > >load, etc).  There may be nothing those users can do to fix it,
>because
> > >the breakage might be happening in their provider's software.  The
> > >provider might be very slow to upgrade, because 99% of their
>customers
> > >might be English speakers, and the other 1% are just screwed.
> >
> > This is not true.  In the Middle East, there are at least two or three
> > providers of IDN's currently: Walid, i-DNS, and Nativ Name.  As far as
>I
> > understand, Native Name provides a UTF-8 solution, I do not know about
>the
> > others.  The response has been very strong from what I know: providers
>ARE
> > switching to UTF-8; there is a good chance that my ISP will upgrade to
>a
> > UTF-8 compatible software assuming they have not done so already.  I
>believe
> > it is a later version of BIND that is necessary.
> >
> > I also read on this list that CNNIC has chosen UTF-8 as their current
> > encoding.  This is another indication that providers ARE switching.
> >
> > Another thing: assuming 99% English and 1% non-English in the Middle
>East is
> > completely wrong.  I, and many other IT professionals here, are
>committed to
> > bringing our people online.  Most of our people have little
>understanding of
> > the written Arabic language, let alone English.
> >
> > >With ACE, people might have to put visible ACEs in some config
> > >files, which is annoying, but at least it will work.  Eventually
> > >the application might get upgraded to support native characters in
> > >the config files and then things will get easier.  Without ACE, the
> > >application will simply be unusable with IDNs until it is upgraded.
> > >
> > >Conclusion: There should be ACE.
> >
> > This conclusion is premature to say the least.
> >
> > >Next question:  Given that there will be ACE, should DNS support
>8-bit
> > >queries in addition to ACE queries?  I don't know.  No matter what
> > >is recommended or discouraged, some DNS servers will probably try to
> > >guess the encoding of 8-bit queries.  This will help old clients, but
> > >increases the risk of spoofing, and allows some applications to be
> > >lazier about upgrading.  I haven't yet formed an opinion on this.
> > >
> > >Next question:  Should ACE ever be phased out?  I don't think so.
>Very
> > >few systems will ever support all Unicode characters, so applications
> > >will sometimes try to display IDNs containing unsupported characters.
> > >What should they display?  They should display the ACE, because
>that's
> > >no uglier than anything else they might display, and has the added
>bonus
> > >that you can copy it into any other application and it will still
>work.
> > >
> > >Furthmore, domain names are first and foremost *global* identifiers
> > >intended to be used by *humans* *anywhere* to refer to network
>objects.
> > >For people who know the Unicode characters in the domain name, the
> > >native representation is easiest, but for the billions of people who
> > >don't know those characters, the ACE is much easier to type, write,
> > >speak, and visually compare.  (The Roman alphabet is one of the
>smallest
> > >alphabets in existence, and is already widely recognized.  If you
>have
> > >to chose a fallback character set for everyone to learn, that's the
>best
> > >choice.)
> >
> > If you wish to try to come to Egypt or any other place in the Middle
>East,
> > and convince people here that English is a good choice even as a
>"fallback
> > character set for everyone to learn", I do not envy your task as you
>will
> > not be taken seriously.  I do not understand your comment of "billions
>of
> > people" who do not know "those characters", where those characters are
>the
> > native language of the people.  This is so patently wrong to me that I
> > believe I must have misunderstood you.  I personally am not interested
>in
> > seeing English propagated as the default language, as a half solution
>for
> > multilingal domains.  It is impossible to ask us to learn the Roman
>language
> > simply to satisfy the protocol writers.  Instead we are happy to go
>with a
> > tougher solution that will give more access to the average,
>non-English
> > speaker ultimately.  If we have to wait a little or a lot longer for
>that to
> > occur, that is worth it compared to a short-term solution that
>requires me
> > to send my mother to English spelling school.
> >
> > >I'm not saying that various protocols shouldn't allow 8-bit encoding
>in
> > >addition to ACE (I have no opinion on that yet), I'm just saying that
> > >ACE will always serve a useful function, and should never be
>deprecated.
> > >
> > >AMC
> > >
> >
> > Sherin
> >
> > _________________________________________________________________
> > Get your FREE download of MSN Explorer at http://explorer.msn.com
> >
> >
>

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com




From owner-idn@ops.ietf.org  Mon May 28 01:21:21 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA17820
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 01:21:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154FB7-0002Pu-00
	for idn-data@psg.com; Sun, 27 May 2001 22:02:53 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154FB6-0002Pl-00
	for idn@ops.ietf.org; Sun, 27 May 2001 22:02:53 -0700
Received: from [192.168.1.40] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id HAA24164;
	Mon, 28 May 2001 07:01:53 +0200 (MET DST)
Date: Mon, 28 May 2001 07:01:44 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Sherin Alsoudani <sherinalsoudani@hotmail.com>, James@Seng.cc,
        amc@cs.berkeley.edu, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
Message-ID: <286964.991033304@localhost>
In-Reply-To: <F157s9U6TOZgkbN6WAv0000976e@hotmail.com>
References:  <F157s9U6TOZgkbN6WAv0000976e@hotmail.com>
X-Mailer: Mulberry/2.1.0a6 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-05-27 21.35 -0700 Sherin Alsoudani <sherinalsoudani@hotmail.com>
wrote:

> As 
> we wait for applications to display RACE properly, it will set us back
> for a  long while - that is the crux of the problem I am afraid of.
>
> For example, the number one Internet application in the Middle East today
> is  probably Microsoft Internet Explorer.  It already has support for
> UTF-8.  

You still don't recognize the difference many people on this mailing list
try to get through to you, which is that IF you use an ACE encoding the
enduser can himself control whether he is seeing the ACE encoded word or
not. In the case of UTF-8, he must wait for the system administrator to
upgrade software in the path of the information and upgrade his own
software. Because of this argument, introduction of IDN is arguably faster
with ACE than UTF-8.

You continue to say that software have already support for UTF-8, while you
point out the true statement that for arabic you don't differ between
casing of chararcters. This means that the software somewhere not only use
UTF-8 encoding, but also that some normalization is done somewhere (or
should happen somewhere). Because the kind of normalization that happens if
you want case insensitivity everyone need to agree on what normalization
scheme to use. That is what we in this group call nameprep.

When nameprep is finalized (and a decision is taken whether nameprep should
happen or not)  then you need to change all applications again, even though
you use UTF-8, just because the comparison algorithms need to be agreed
upon (and, no, existing UTF-8 software don't do this according to current
nameprep proposal).

   paf




From owner-idn@ops.ietf.org  Mon May 28 01:21:42 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA17844
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 01:21:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154FHP-0002S0-00
	for idn-data@psg.com; Sun, 27 May 2001 22:09:23 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 154FHO-0002Ru-00
	for idn@ops.ietf.org; Sun, 27 May 2001 22:09:22 -0700
Received: (qmail 26247 invoked by uid 1001); 28 May 2001 05:09:43 -0000
Date: 28 May 2001 05:09:43 -0000
Message-ID: <20010528050943.16457.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
References: <F86ip68V8zDv60gxapz0000f8ba@hotmail.com> <200105280239.WAA00909@astro.cs.utk.edu> <3B1180B6.8939BDC1@ehsco.com> <200105280227.WAA00791@astro.cs.utk.edu> <20010527213052.C17337@arwen.cs.berkeley.edu> <200105280200.WAA00572@astro.cs.utk.edu> <20010527202613.5518.qmail@cr.yp.to> <200105280114.VAA00203@astro.cs.utk.edu> <20010527165903.5833.qmail@cr.yp.to> <200105280106.VAA29976@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:
> gethostbyname should not be upgraded, because this would cause
> harm to applications that expect ASCII domain names.

Sorry, Keith, but the real world doesn't care about your delusions. The
current gethostbyname() release already works with UTF-8 domain names.

> UTF-8 is causing sutble bugs in software that was written to expect ASCII

Obviously those programs should be fixed as soon as possible. I've
already proposed that the WG publish a document requiring this. The only
known example is sendmail, and the fix in that case is straightforward.

> each protocol must be "fixed" by people who understand that protocol.

You're absolutely right, Keith. This WG can't handle a job as tricky as
changing ``sequence of bytes 1-127'' to ``sequence of bytes 1-255.''
Those Internet text protocols are amazingly subtle.

> UTF-8 guarantees that the data is unreadable for users of
> today's non UTF-8 software.

Programs that don't support UTF-8 are being fixed. We have, for example,
terminals and editors that work with UTF-8 text. UTF-8 is much bigger
than IDN; it is going to be available everywhere no matter what this WG
does. See http://www.cl.cam.ac.uk/~mgk25/unicode.html.

In contrast, ACE is not a general-purpose text format. Nobody is writing
an ACE version of xterm or vi. There is no movement to convert all
textual data to ACE; the idea is absurd. ACE is never going to be
readable the way that UTF-8 is.

> reliably compare two UTF-8 representations of an IDN

There is only one good (``canonical'') UTF-8 representation of an IDN.
With fast nameprep, the keyboard interface helps the user type this good
name, so applications don't have to worry about bad names.

This is just like the current handling of dots. Yes, there are bad dots,
but the keyboard interface helps the user type domain names with the
ASCII dot, so applications don't have to worry about bad dots. Are you
going to demand that we change and redeploy thousands of programs to
accept non-canonical dots in domain names?

---Dan



From owner-idn@ops.ietf.org  Mon May 28 01:43:53 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA19074
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 01:43:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154FWi-0002ZY-00
	for idn-data@psg.com; Sun, 27 May 2001 22:25:12 -0700
Received: from f95.law15.hotmail.com ([64.4.23.95] helo=hotmail.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154FWi-0002ZD-00
	for idn@ops.ietf.org; Sun, 27 May 2001 22:25:12 -0700
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Sun, 27 May 2001 22:24:41 -0700
Received: from 24.130.82.137 by lw15fd.law15.hotmail.msn.com with HTTP;	Mon, 28 May 2001 05:24:40 GMT
X-Originating-IP: [24.130.82.137]
From: "Sherin Alsoudani" <sherinalsoudani@hotmail.com>
To: paf@cisco.com, James@Seng.cc, amc@cs.berkeley.edu, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
Date: Sun, 27 May 2001 22:24:40 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F95Aztxc1o8yfogkJXr0000f868@hotmail.com>
X-OriginalArrivalTime: 28 May 2001 05:24:41.0155 (UTC) FILETIME=[7F035930:01C0E736]
Sender: owner-idn@ops.ietf.org
Precedence: bulk


Dear Patrik,

> > As
> > we wait for applications to display RACE properly, it will set us back
> > for a  long while - that is the crux of the problem I am afraid of.
> >
> > For example, the number one Internet application in the Middle East 
>today
> > is  probably Microsoft Internet Explorer.  It already has support for
> > UTF-8.
>
>You still don't recognize the difference many people on this mailing list
>try to get through to you, which is that IF you use an ACE encoding the
>enduser can himself control whether he is seeing the ACE encoded word or
>not. In the case of UTF-8, he must wait for the system administrator to
>upgrade software in the path of the information and upgrade his own
>software. Because of this argument, introduction of IDN is arguably faster
>with ACE than UTF-8.

Sadly, you and many people on this list are not understanding what I have 
written.  My point has been to be practical: you say that the enduser can 
control whether he is seeing the ACE encoded word or not.  Please show me 
one client that can do this today.

And after you find that one client, explain to me why I should change my 
position regarding IE, given that IE is successfully putting out UTF-8 
characters today, there are providers compatible with this today, and that 
bringing the Internet to people sooner rather than later is important 
*today*.  For the 95% of the Middle East that is not on the Internet, there 
are ongoing efforts by system administrators all over to make it easier to 
come online.  Five minutes of research on the net will educate you about 
this.

I am puzzled by this amount of theory that is passed back on forth on the 
list.  Things ARE moving, and UTF-8 is recognized as a better ultimate 
solution.  If it is more painful, I can appreciate that through the 
education you and others have given me.  Nonetheless, "necessity is the 
mother of invention", and your and others claims that it will be very 
difficult, and very slow...well, I would invite you to look around at the 
different efforts going on to prove that wrong.

>You continue to say that software have already support for UTF-8, while you
>point out the true statement that for arabic you don't differ between
>casing of chararcters. This means that the software somewhere not only use
>UTF-8 encoding, but also that some normalization is done somewhere (or
>should happen somewhere). Because the kind of normalization that happens if
>you want case insensitivity everyone need to agree on what normalization
>scheme to use. That is what we in this group call nameprep.

Actually, you misunderstood: Arabic does not have any case - there is no 
concept of upper/lower case.  But I certainly appreciate the need for what 
you call nameprep; there are other issues that Arabic will need.

Sherin

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com




From owner-idn@ops.ietf.org  Mon May 28 01:54:40 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA19745
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 01:54:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154FiO-0002eI-00
	for idn-data@psg.com; Sun, 27 May 2001 22:37:16 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154FiN-0002eB-00
	for idn@ops.ietf.org; Sun, 27 May 2001 22:37:15 -0700
Received: from [192.168.1.40] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id HAA26857;
	Mon, 28 May 2001 07:36:27 +0200 (MET DST)
Date: Mon, 28 May 2001 07:36:21 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Sherin Alsoudani <sherinalsoudani@hotmail.com>, James@Seng.cc,
        amc@cs.berkeley.edu, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
Message-ID: <411523.991035381@localhost>
In-Reply-To: <F95Aztxc1o8yfogkJXr0000f868@hotmail.com>
References:  <F95Aztxc1o8yfogkJXr0000f868@hotmail.com>
X-Mailer: Mulberry/2.1.0a6 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-05-27 22.24 -0700 Sherin Alsoudani <sherinalsoudani@hotmail.com>
wrote:

> Sadly, you and many people on this list are not understanding what I have 
> written.  My point has been to be practical: you say that the enduser can 
> control whether he is seeing the ACE encoded word or not.  Please show me 
> one client that can do this today.

There is no client which do UTF-8 encoding according to what this wg will
agree on, and there is no client which do ACE according to what this wg
will agree on.

The application the user is using have to be changed regardless of what
solution is chosen.

But, if you choose UTF-8 as the path, you have to also replace software in
the middle, which the enduser doesn't control, and which the enduser can
not change.

The enduser because of this have to wait until his network administrator do
the change.

In your environment, on your network, it seems that the network
administrator is doing changes fast, but that is certainly not the case in
many cases in the world (including at some sites in Arab countries I have
been working with).

> And after you find that one client, explain to me why I should change my 
> position regarding IE, given that IE is successfully putting out UTF-8 
> characters today, there are providers compatible with this today, and
> that  bringing the Internet to people sooner rather than later is
> important  *today*.

No, it is not doing it correctly.

See previous argument about nameprep.

Also, the Internet is not only the web, and no, a user can not communicate
only with a client with other peoples clients. Server software also have to
be replaced.

> I am puzzled by this amount of theory that is passed back on forth on the 
> list.  Things ARE moving, and UTF-8 is recognized as a better ultimate 
> solution.

I am not talking about the ultimate solution. I am talking about getting
started with IDN, and giving the users the power of doing so.

> Actually, you misunderstood: Arabic does not have any case - there is no 
> concept of upper/lower case.  But I certainly appreciate the need for
> what  you call nameprep; there are other issues that Arabic will need.

I know Arabic doesn't have any case. I know how it works. I promise you. I
wrote a directory service in 1995 with full UTF-8 support, especially for
Arabic.

But, the glyphs have different codepoints in Unicode. That was my point.


   paf




From owner-idn@ops.ietf.org  Mon May 28 01:59:53 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA20049
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 01:59:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154FjE-0002eo-00
	for idn-data@psg.com; Sun, 27 May 2001 22:38:08 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154FjD-0002ei-00
	for idn@ops.ietf.org; Sun, 27 May 2001 22:38:07 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id BAA02917;
        Mon, 28 May 2001 01:38:05 -0400 (EDT)
Message-Id: <200105280538.BAA02917@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] UTF-8 / RACE 
In-reply-to: Your message of "28 May 2001 04:36:39 -0000."
             <20010528043639.9273.qmail@cr.yp.to> 
Date: Mon, 28 May 2001 01:38:05 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > with or without ACE, people will have to upgrade their applications
> 
> Except, of course, for all the programs that _already_ work with UTF-8.

which is the null set.

Keith




From owner-idn@ops.ietf.org  Mon May 28 02:12:42 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA28108
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 02:12:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154G0i-0002ne-00
	for idn-data@psg.com; Sun, 27 May 2001 22:56:12 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154G0h-0002nY-00
	for idn@ops.ietf.org; Sun, 27 May 2001 22:56:11 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id BAA03053;
        Mon, 28 May 2001 01:56:09 -0400 (EDT)
Message-Id: <200105280556.BAA03053@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] UTF-8 / RACE 
In-reply-to: Your message of "28 May 2001 05:09:43 -0000."
             <20010528050943.16457.qmail@cr.yp.to> 
Date: Mon, 28 May 2001 01:56:09 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Keith Moore writes:
> > gethostbyname should not be upgraded, because this would cause
> > harm to applications that expect ASCII domain names.
> 
> Sorry, Keith, but the real world doesn't care about your delusions. 

And it regards your delusions as the irrefutable truth?

I'm not interested in whose delusions the world cares about, I'm
interested in what works well.

> The current gethostbyname() release already works with UTF-8 domain names.

delusion #1.

In the current DNS world, neither the client nor the server implements 
any kind of name canonicalization before comparing two names.     thus
there is no way for any current implement gethostbyname () to "work"
for any useful definition of "work".

> > UTF-8 is causing sutble bugs in software that was written to expect ASCII
> 
> Obviously those programs should be fixed as soon as possible. 

obviously.  and everyone should upgrade all of their software immediately,
regardless of whether the people involved are actually likely to use
IDNs, because Dan said so.   (delusion #2 is that this is going to happen)

> I've already proposed that the WG publish a document requiring this. 

as if that were in this WG's purview (delusion #3)

> The only known example is sendmail, 

(delusion #4)

and the fix in that case is straightforward.

(delusion #5)

> > each protocol must be "fixed" by people who understand that protocol.
> 
> You're absolutely right, Keith. This WG can't handle a job as tricky as
> changing ``sequence of bytes 1-127'' to ``sequence of bytes 1-255.''

(delusion #6 is that the change is as simple as making the tool 8-bit
transparent.)

> > UTF-8 guarantees that the data is unreadable for users of
> > today's non UTF-8 software.
> 
> Programs that don't support UTF-8 are being fixed. 

delusion #7.  yes, more and more programs support UTF-8, but that doesn't
support a generalization that "programs...are being fixed".  the programs
that are being upgraded might or might not be the ones that people
want to use.    After all, people are still using VMS MAIL and ucbmail.

> We have, for example,
> terminals and editors that work with UTF-8 text. UTF-8 is much bigger
> than IDN; it is going to be available everywhere no matter what this WG
> does. 

wow...you actually made a defensible statement.  I was starting to worry.

yes, UTF-8 is a very useful encoding that will eventually be supported 
on all platforms.  that does not mean it will replace all other encodings,
nor that all applications will support it.

> In contrast, ACE is not a general-purpose text format. Nobody is writing
> an ACE version of xterm or vi. There is no movement to convert all
> textual data to ACE; the idea is absurd. ACE is never going to be
> readable the way that UTF-8 is.
> 
> > reliably compare two UTF-8 representations of an IDN
> 
> There is only one good (``canonical'') UTF-8 representation of an IDN.
> With fast nameprep, the keyboard interface helps the user type this good
> name, so applications don't have to worry about bad names.

let's see - so you reject the approach that the IDN portions of a 
plain UTF-8 text file can be encoded differently than the rest of
the text file (as if plain text files were a dominant text format
anymore), but you somehow think that everybody's keyboard interface
should have a separate IDN input mode. 

nothing in the ACE approach suggests that IDNs in plain text
should be in ACE format.  the only constraint is that they be
nameprepped and converted to ACE format before they are passed
as protocol elements.  

> This is just like the current handling of dots. Yes, there are bad dots,
> but the keyboard interface helps the user type domain names with the
> ASCII dot, so applications don't have to worry about bad dots. Are you
> going to demand that we change and redeploy thousands of programs to
> accept non-canonical dots in domain names?

no.  I'm just going to demand that we don't break existing applications
by sending them UTF-8 domains when they quite reasonably expect ASCII.

Keith



From owner-idn@ops.ietf.org  Mon May 28 02:17:36 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA28409
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 02:17:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154G9F-0002rh-00
	for idn-data@psg.com; Sun, 27 May 2001 23:05:01 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154G9E-0002rX-00
	for idn@ops.ietf.org; Sun, 27 May 2001 23:05: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 CAA03113;
        Mon, 28 May 2001 02:04:40 -0400 (EDT)
Message-Id: <200105280604.CAA03113@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Sherin Alsoudani" <sherinalsoudani@hotmail.com>
cc: James@Seng.cc, amc@cs.berkeley.edu, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE 
In-reply-to: Your message of "Sun, 27 May 2001 21:35:11 PDT."
             <F157s9U6TOZgkbN6WAv0000976e@hotmail.com> 
Date: Mon, 28 May 2001 02:04:40 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> It is good to hear that the overall WG is keeping in mind that most of the
> world does not understand English well enough to type in that language.  For
> Arabs, we write from right to left, and we have no notion of upper case and
> lower case, plus it is a phonetic language.  This is why a RACE solution in
> the short-term would be not so good for us in the Middle East.  

I don't understand how the last statement follows from the earlier ones.
What does it matter how the IDN is encoded within a protocol, as long as
the application handles the encoding and decoding correctly?

> If the
> members of this WG are seeing the fact of applications being deficient in
> their ability to display RACE-encoded IDN's as a problem, for us in the
> Middle East it is a very big problem.  

I have no doubt that this is true.  But how many of your currently -deployed
applications could display UTF-8 encoded IDNs?  And of those, how many of
them would be able to accept UTF-8 IDNs as input and nameprep them before
doing any queries or name comparisons?

> Arabic and English are very
> different, and our population does not have a strong command of English.  As
> we wait for applications to display RACE properly, it will set us back for a
> long while - that is the crux of the problem I am afraid of.

Is display of IDNs the most important concern, or is it also important that
these applications be able to accept them as input and look them up in DNS?
If the latter two are also important, I don't see why it will take any longer
for these applications to be updated to handle ACE vs. UTF-8.

> For example, the number one Internet application in the Middle East today is
> probably Microsoft Internet Explorer.  It already has support for UTF-8.

perhaps it is able to display UTF-8 text and accept UTF-8 as input, but it 
does not canonicalize UTF-8 names before issuing a DNS query.

> Judging from the emails in this group, Microsoft's claims of "just send
> UTF-8" are not enough.  However, for the entire Middle East, the little
> support that comes with IE 5 for Arabic URL's is a definite positive step,
> and there is momentum there.

Since an ACE is just an encoding of UTF-8, this momentum would apply equally 
to ACE as to UTF-8.  And as you point out, MSIE would have to be updated
in either case.

Keith



From owner-idn@ops.ietf.org  Mon May 28 02:18:28 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA28495
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 02:18:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154GBL-0002sl-00
	for idn-data@psg.com; Sun, 27 May 2001 23:07:11 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154GBK-0002sf-00
	for idn@ops.ietf.org; Sun, 27 May 2001 23:07:10 -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 f4S678I23559; Mon, 28 May 2001 08:07:08 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Mon, 28 May 2001 08:06:04 +0200 (MEST) (MET)
Message-Id: <200105280606.IAA04110@valinor.malmo.trab.se>
Date: Mon, 28 May 2001 08:06:04 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: [idn] Let's go forward with IDNA and UTF-8
To: dufberg@nic-se.se
Cc: idn@ops.ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: DxniWG23kZSW6qBJ/9yI+g==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk


Mats wrote:
>
>> But ACE+nameprep IS destroying information.
>>
>> Also ACE can only be used for host names, if may not fit all types of
>> DNS names and it cannot be used for other textual data in DNS.
>
>Well, nameprep+UTF-8 will cause the same problem when it comes to the name
>part. There is no difference in what codepoints that ACE can handle
>compared to UTF-8. Nameprep is there to eliminate ambiguity, and will be
>needed for any solution (ACE, UTF-8) to avoide chaos in DNS.

Not if you compare UDNS with IDNA.
In IDNA you do nameprep (and destroy information) in the client.
In UDNS, all UTF-8 encoded data is using normalised UCS form C.
The "nameprep" equivalent is only used in matching of names.
So name can retain all information.

   Dan




From owner-idn@ops.ietf.org  Mon May 28 02:40:48 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA00009
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 02:40:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154GKJ-0002yB-00
	for idn-data@psg.com; Sun, 27 May 2001 23:16:27 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154GKI-0002y5-00
	for idn@ops.ietf.org; Sun, 27 May 2001 23:16:26 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id CAA03315;
        Mon, 28 May 2001 02:16:19 -0400 (EDT)
Message-Id: <200105280616.CAA03315@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Sherin Alsoudani" <sherinalsoudani@hotmail.com>
cc: paf@cisco.com, James@Seng.cc, amc@cs.berkeley.edu, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE 
In-reply-to: Your message of "Sun, 27 May 2001 22:24:40 PDT."
             <F95Aztxc1o8yfogkJXr0000f868@hotmail.com> 
Date: Mon, 28 May 2001 02:16:19 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> And after you find that one client, explain to me why I should change my
> position regarding IE, given that IE is successfully putting out UTF-8
> characters today, there are providers compatible with this today, and that
> bringing the Internet to people sooner rather than later is important
> *today*. 

because even if IE is canonicalizing the naems before it sends them out,
there is no standard algorithm for doing so.  so MSIE as currently deployed
might do it differently than other applications.  and without such a 
canonicaliation step we have no way to ensure that the same name typed 
into different applications will look up the same records in the DNS.

small scale tests do not predict large scale behavior.  MSIE is just one
application, from a single vendor, and the tests you cite are for a single
language and a small number of information providers.    we need a solution
that will work for any application, any vendor, any of the world's commonly-
used languages, and any information providers who want to use it.

it's easy to provide an example of an IDN solution that works on a small scale 
today; several such examples exist.  It's much more difficult to make a 
convincing case that the solution will work on a large scale once it is deployed.

Keith



From owner-idn@ops.ietf.org  Mon May 28 02:54:59 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA00957
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 02:54:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154GcZ-00036Y-00
	for idn-data@psg.com; Sun, 27 May 2001 23:35:19 -0700
Received: from arachnid.ehsco.com ([209.31.7.46] helo=Arachnid.NTRG.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154GcY-00036S-00
	for idn@ops.ietf.org; Sun, 27 May 2001 23:35:19 -0700
Received: from ehsco.com (nat-external.ehsco.com [209.31.7.42])
          by Arachnid.NTRG.com (Netscape Messaging Server 3.62)  with ESMTP
          id 660; Sun, 27 May 2001 23:35:16 -0700
Message-ID: <3B11F1A3.567C83C1@ehsco.com>
Date: Sun, 27 May 2001 23:35:15 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
References: <200105280200.WAA00572@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> still, I don't see any harm in having a native UTF-8 DNS query
> interface if we can achieve the following:
> 
> - delegation paths for UTF-8 are the same as for ACE
>   (queries for equivalent names go to the same servers)
> - results of a query are consistent between the two encoding schemes
>   (a query of one type made to a server produces equivalent results
>   - modulo encoding - as a query of the other type)
> - success/failure semantics are the same for the two
>   (if a query using one encoding succeeds or fails, the same
>   should be true for the same query using the other encoding)
> - delay characteristics are similar for the two

This is doable with the following scenario:

 - UTF8 is only sent in new EDNS message.

 - ACE is only sent in legacy message.

 - Server returns answer data based on query message format.

In that model, the answers that the client gets back depends on the query
that they send. Both sets of answers are sourced from the same server so
there is no divergence. Zone data would be managed in the UTF8 form, and
ACE conversion equivalents would be generated by the servers, thereby
providing consistency at the source.

There are a few other issues here:

 - There needs to be a wide() version of gethostbyname and the
   like so that clients can make the right calls depending on
   their application support.

 - Queries have to go to the UTF8 server or its cache, which
   means that the authoritative servers for the zone have to
   be upgraded. As to the size of this as a problem, I put it
   in the same camp as IMAP-v-POP: if you want IMAP on your POP
   server, upgrade.

   Note that this does not affect queries for remote zones,
   since ignorant queries would be in legacy form, and would
   be therefore answered in ACE form. Only the authoritative
   servers for the zone need upgrading.

 - Caches will not always be completely synchronized, since an
   ACE query may arrive two hours before a UTF8 query, and the
   data may have changed in the meantime. I don't consider
   this to be a propblem since cache integrity is not assured
   currently. But it may be excessively confusing to have two
   users issue the same query and get different answers.

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



From owner-idn@ops.ietf.org  Mon May 28 02:58:18 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA01199
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 02:58:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154Gl9-0003AI-00
	for idn-data@psg.com; Sun, 27 May 2001 23:44:11 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154Gl8-0003AB-00
	for idn@ops.ietf.org; Sun, 27 May 2001 23:44: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 CAA03589;
        Mon, 28 May 2001 02:44:03 -0400 (EDT)
Message-Id: <200105280644.CAA03589@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: Keith Moore <moore@cs.utk.edu>, "Adam M. Costello" <amc@cs.berkeley.edu>,
        idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE 
In-reply-to: Your message of "Sun, 27 May 2001 23:35:15 PDT."
             <3B11F1A3.567C83C1@ehsco.com> 
Date: Mon, 28 May 2001 02:44:03 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > still, I don't see any harm in having a native UTF-8 DNS query
> > interface if we can achieve the following:
> > 
> > - delegation paths for UTF-8 are the same as for ACE
> >   (queries for equivalent names go to the same servers)
> > - results of a query are consistent between the two encoding schemes
> >   (a query of one type made to a server produces equivalent results
> >   - modulo encoding - as a query of the other type)
> > - success/failure semantics are the same for the two
> >   (if a query using one encoding succeeds or fails, the same
> >   should be true for the same query using the other encoding)
> > - delay characteristics are similar for the two
> 
> This is doable with the following scenario:
> 
>  - UTF8 is only sent in new EDNS message.
> 
>  - ACE is only sent in legacy message.
> 
>  - Server returns answer data based on query message format.

that's pretty much what I imagined.  however my understanding is that many 
existing DNS caches/proxies cannot forward EDNS queries, which implies
that the ACE queries will be more reliable than the EDNS ones.

if you adopt a strategy of "try EDNS, and if that fails, try ACE"
then the EDNS queries take longer on average than the ACE ones.

it's difficult to imagine why your host library wouldn't always convert
the query to ACE format, since that would be both faster and more reliable.

> There are a few other issues here:
> 
>  - There needs to be a wide() version of gethostbyname and the
>    like so that clients can make the right calls depending on
>    their application support.

we would need this in any case, regardless of the format used
for IDN queries on the wire.

>  - Caches will not always be completely synchronized, since an
>    ACE query may arrive two hours before a UTF8 query, and the
>    data may have changed in the meantime. I don't consider
>    this to be a propblem since cache integrity is not assured
>    currently. But it may be excessively confusing to have two
>    users issue the same query and get different answers.

another good point I hadn't thought of.

Keith



From owner-idn@ops.ietf.org  Mon May 28 03:10:16 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA01710
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 03:10:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154Grp-0003De-00
	for idn-data@psg.com; Sun, 27 May 2001 23:51:05 -0700
Received: from arachnid.ehsco.com ([209.31.7.46] helo=Arachnid.NTRG.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154Gro-0003DX-00
	for idn@ops.ietf.org; Sun, 27 May 2001 23:51:05 -0700
Received: from ehsco.com (nat-external.ehsco.com [209.31.7.42])
          by Arachnid.NTRG.com (Netscape Messaging Server 3.62)  with ESMTP
          id 614; Sun, 27 May 2001 23:51:03 -0700
Message-ID: <3B11F556.DCD1CD56@ehsco.com>
Date: Sun, 27 May 2001 23:51:03 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
References: <200105280227.WAA00791@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> I don't think it's fair to characterize ACE as a halfway solution.

It requires significant additional computations and presentation
processing for it to be anywhere near seamless for the user. UTF8 encoded
data does not require multiple translations. Maybe "halfway" isn't proper
descriptor for ACE (did I use it? no matter), but it's not a complete
solution either.

> since the vast majority of applications will be using standard APIs
> which convert between native character set and encoding and those
> used on the wire.  For this purpose, the application doesn't care
> whether the format is UTF-8 or ACE.

My guess is that over the next 10 years, the majority of the systems will
be either be native UTF8 or UTF32.

> > It is highly unlikely that those services will ever be fixed until
> > a UTF8 form is developed by us, embraced by the WG, and coded by
> > the vendor community.
> 
> think of it another way - there's no way that the IDN WG can "fix"
> these services

I made a typo, "WG" should have been plural, as in "the appropriate IETF
working groups for each of the protocols".

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



From owner-idn@ops.ietf.org  Mon May 28 03:18:13 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA01744
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 03:18:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154H7o-0003XP-00
	for idn-data@psg.com; Mon, 28 May 2001 00:07:36 -0700
Received: from [216.177.8.114] (helo=ayna.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154H7l-0003XJ-00
	for idn@ops.ietf.org; Mon, 28 May 2001 00:07:33 -0700
Received: (from nobody@localhost)
	by ayna.com (8.9.3/8.9.3) id DAA12029;
	Mon, 28 May 2001 03:29:47 -0400
To: James Seng/Personal <James@Seng.cc>,
        Sherin Alsoudani <sherinalsoudani@hotmail.com>, amc@cs.berkeley.edu,
        idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
Message-ID: <991034987.3b11fe6b1ef08@www.bareed.ayna.com>
Date: Mon, 28 May 2001 03:29:47 -0400 (EDT)
From: Adonis El Fakih <adonis@ayna.com>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: Ayna VER 2.22 
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi James,

Using utf-8 from the system point of view is the same as using cp1256.  They are both 8bit encoding schemes, and most applications people use to publish on the net, use unicode in the backend.

So I am assuming this is what sherine is refering to.  It is easier to convert applications using 8bit encoding to use utf8 than doing RACE.  While RACE will be good for 7bit encoding applications.  

I have succeffuly converted some apps we use localy to work with utf8 and we had to account for the double bytes compared to one when working with cp1256 or iso88596, and it was not a lot of work. I actually did this about two years ago.

best regards
Adonis




______________________________________________________________
Ayna, The Arabic Internet Starts Here.     http://www.ayna.com



From owner-idn@ops.ietf.org  Mon May 28 03:19:32 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA01755
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 03:19:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154H63-0003QB-00
	for idn-data@psg.com; Mon, 28 May 2001 00:05:47 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154H61-0003Q3-00
	for idn@ops.ietf.org; Mon, 28 May 2001 00:05:45 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 0845FFFC03; Mon, 28 May 2001 15:08:18 +0800 (SGT)
Message-ID: <0a8c01c0e744$85e19600$7dcb15a5@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Sherin Alsoudani" <sherinalsoudani@hotmail.com>, <amc@cs.berkeley.edu>,
        <idn@ops.ietf.org>
References: <F157s9U6TOZgkbN6WAv0000976e@hotmail.com>
Subject: Re: [idn] UTF-8 / RACE
Date: Mon, 28 May 2001 15:05:05 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Sherin,

> It is good to hear that the overall WG is keeping in mind that most of
the
> world does not understand English well enough to type in that
language.  For
> Arabs, we write from right to left, and we have no notion of upper
case and
> lower case, plus it is a phonetic language.  This is why a RACE
solution in
> the short-term would be not so good for us in the Middle East.

While I can understand the first place, I am not able to follow the
logic which leads you this conclusion. What has bidi or phonetic has to
do with RACE encoding?

> If the
> members of this WG are seeing the fact of applications being deficient
in
> their ability to display RACE-encoded IDN's as a problem, for us in
the
> Middle East it is a very big problem.  Arabic and English are very
> different, and our population does not have a strong command of
English.  As
> we wait for applications to display RACE properly, it will set us back
for a
> long while - that is the crux of the problem I am afraid of.

I think there is some misunderstanding here. RACE is NOT English. RACE
is an transformation encoding scheme of Unicode which resultant string
is LDH.

> Note that the assumption of most of the Arabic Internet using CP1256
or
> Sakhr is not entirely accurate.  It is more accurate to state in what
> context is what encoding more popular.  For Web content, you will find
more
> sites written using CP1256 but there are some significant
implementations
> using UTF-8.  I am happy to see that Mr. Adonis Fakih is already on
this
> list since he represents Ayna.com.  Ayna is the number one Arabic
portal -
> and it supports UTF-8.

Interesting. Do you have any statistic on the usage of UTF-8 vs CP1256
in website in Arabic? Or you have pointers to more info on this?

> In the context of Arabic URL's however, there is no de facto standard,
> though Microsoft has certainly given us a strong pathway to one via
UTF-8.
> Native Name appears to be exploiting that, and it seems to be the
> front-runner at this stage.  I believe it would be easy for the other
> players to do the same thing, including i-DNS and Walid.

I think commerical implementation is irrelevant for the WG standard
consideration. We have to do what we have to do to ensure the bring
about the right standard, not one which the commerical company wants.

> I hope this explains my worries James.  In a nutshell, we already have
a
> starting point in the Middle East for giving users of the Web portion
of the
> Internet access to Arabic domain names using UTF-8.  It works
> "out-of-the-box."  Given that most of the new users of the Internet in
the
> Middle East equate the Internet with the Web, I would hate to see that
> momentum die.  Keep in mind that Internet Explorer has over 90% of the
> market in the Middle East due to Netscape 4's inability to display
Arabic
> fonts.  Netscape 6 solves this, but it may be well too late.

I am kind of worried on the statement "out-of-the-box".

You see, given my experience in this field, it is *very* easy to
demostrate a system which works "out-of-the-box" under the right
combination, e.g. Arabic IE in Arabic-enabled Windows using Arabic
domain names.

Have you try Chinese URL on Arabic IE on Thai Windows? I did and I wont
classify the result as "out-of-the-box".

No, I certainly do not buy into the argument of "just-send-utf8" as your
email describe here. Pardon me if I misunderstood it.

-James Seng




From owner-idn@ops.ietf.org  Mon May 28 03:21:24 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA01770
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 03:21:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154HAe-0003cG-00
	for idn-data@psg.com; Mon, 28 May 2001 00:10:32 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154HAd-0003cA-00
	for idn@ops.ietf.org; Mon, 28 May 2001 00:10:31 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 4AA41FFC03; Mon, 28 May 2001 15:13:07 +0800 (SGT)
Message-ID: <0a9c01c0e745$32399c90$7dcb15a5@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
References: <F86ip68V8zDv60gxapz0000f8ba@hotmail.com> <200105280239.WAA00909@astro.cs.utk.edu> <3B1180B6.8939BDC1@ehsco.com> <200105280227.WAA00791@astro.cs.utk.edu> <20010527213052.C17337@arwen.cs.berkeley.edu> <200105280200.WAA00572@astro.cs.utk.edu> <20010527202613.5518.qmail@cr.yp.to> <200105280114.VAA00203@astro.cs.utk.edu> <20010527165903.5833.qmail@cr.yp.to> <200105280106.VAA29976@astro.cs.utk.edu> <20010528050943.16457.qmail@cr.yp.to>
Subject: Re: [idn] UTF-8 / RACE
Date: Mon, 28 May 2001 15:09:54 +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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Is this your defination for Fast Nameprep?

If that is the case, are you suggesting we change the keyboard interface
to do "Nameprep" so there is no 'bad' dot? Please explain further how
you proposed to interact with keyboard interface...

Incidently for those who cares, on a Chinese/Japanese IME, a dot can
either be U+3002 or U+002E depending if it is full/half width and in
Korean IME, a dot can either be U+FF9E or U+002E.

-James Seng

> This is just like the current handling of dots. Yes, there are bad
dots,
> but the keyboard interface helps the user type domain names with the
> ASCII dot, so applications don't have to worry about bad dots. Are you
> going to demand that we change and redeploy thousands of programs to
> accept non-canonical dots in domain names?
>
> ---Dan
>




From owner-idn@ops.ietf.org  Mon May 28 03:23:18 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA01793
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 03:23:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154HCH-0003df-00
	for idn-data@psg.com; Mon, 28 May 2001 00:12:13 -0700
Received: from arachnid.ehsco.com ([209.31.7.46] helo=Arachnid.NTRG.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154HCG-0003dZ-00
	for idn@ops.ietf.org; Mon, 28 May 2001 00:12:13 -0700
Received: from ehsco.com (nat-external.ehsco.com [209.31.7.42])
          by Arachnid.NTRG.com (Netscape Messaging Server 3.62)  with ESMTP
          id 637; Mon, 28 May 2001 00:12:11 -0700
Message-ID: <3B11FA4A.4F88E8AD@ehsco.com>
Date: Mon, 28 May 2001 00:12:10 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
References: <200105280644.CAA03589@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> that's pretty much what I imagined.  however my understanding is that
> many existing DNS caches/proxies cannot forward EDNS queries, which
> implies that the ACE queries will be more reliable than the EDNS ones.

Mark Andrews, could you comment on this issue?

There are other concerns. Delegation can only be made to a server that is
capable of handling the zone data, for example, which may present certain
operational challenges. Clients have to be able to deal with rich data is
another (what format should URLs be in, for example?), although most of
that can be worked out in specific WGs).

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



From owner-idn@ops.ietf.org  Mon May 28 03:57:43 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA02031
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 03:57:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154HWB-0003x0-00
	for idn-data@psg.com; Mon, 28 May 2001 00:32:47 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154HWA-0003wu-00
	for idn@ops.ietf.org; Mon, 28 May 2001 00:32:46 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 90FBBFFC05; Mon, 28 May 2001 15:35:21 +0800 (SGT)
Message-ID: <0ad201c0e748$4d7fda20$7dcb15a5@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Sherin Alsoudani" <sherinalsoudani@hotmail.com>, <amc@cs.berkeley.edu>,
        <idn@ops.ietf.org>, "Adonis El Fakih" <adonis@ayna.com>
References: <991034987.3b11fe6b1ef08@www.bareed.ayna.com>
Subject: Re: [idn] UTF-8 / RACE
Date: Mon, 28 May 2001 15:32:08 +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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Using utf-8 from the system point of view is the same as using cp1256.
> They are both 8bit encoding schemes, and most applications people use
> to publish on the net, use unicode in the backend.

Are we talking about 8-bit vs 7-bit now? If we are, can I raise my hand
to say 8-bit is not sufficient for I18N?

CP1256 and UTF-8 are both 8-bit encodings no doubt. I can also claim
BIG5 and UTF-8 are both 8-bit. Thus, system which works for BIG5
*should* work for UTF-8 (or easily converted). Unfortunately, that is
not true.

While a 8-bit application is already 8-bit clean thus making it easiler,
this does not means the other dependent infrastructure which the
applications relies upon is able to deal with 8-bit characters. Sure, we
can upgrade the infrastructure and going through the pain. The question
now here is that can the WG decide we want to do this...and I am hearing
mixed messages from the members.

> So I am assuming this is what sherine is refering to.  It is easier to
> convert applications using 8bit encoding to use utf8 than doing RACE.
> While RACE will be good for 7bit encoding applications.
>
> I have succeffuly converted some apps we use localy to work with utf8
> and we had to account for the double bytes compared to one when
working
> with cp1256 or iso88596, and it was not a lot of work. I actually did
> this about two years ago.

Actually comparison of UTF-8 is much more complex than handling
double-byte compare. This is why there are Unicode Normalization and its
various forms. Especially for Arabic where there are different
presentation forms beyond the U+0600 to U+06FF which you can only
compare it by normalization. Bit-wise comparison wont work in these
cases.

And if you like double-byte comparison, then try some of the Chinese
double-byte encodings especially Industry-Standard BIG5. You could weep
as you code.

-James Seng




From owner-idn@ops.ietf.org  Mon May 28 04:18:55 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA02173
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 04:18:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154Hz0-000584-00
	for idn-data@psg.com; Mon, 28 May 2001 01:02:34 -0700
Received: from spider.nic-se.se ([212.247.3.67])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154Hyz-00056u-00
	for idn@ops.ietf.org; Mon, 28 May 2001 01:02:33 -0700
Received: from localhost (dufberg@localhost)
	by spider.nic-se.se (8.11.1/8.11.1) with ESMTP id f4S7sWw11021;
	Mon, 28 May 2001 09:54:32 +0200 (CEST)
X-Authentication-Warning: spider.nic-se.se: dufberg owned process doing -bs
Date: Mon, 28 May 2001 09:54:32 +0200 (CEST)
From: Mats Dufberg <dufberg@nic-se.se>
To: Dan Oscarsson <Dan.Oscarsson@trab.se>
cc: <idn@ops.ietf.org>
Subject: Re: [idn] Let's go forward with IDNA and UTF-8
In-Reply-To: <200105280606.IAA04110@valinor.malmo.trab.se>
Message-ID: <Pine.BSF.4.30.0105280952400.9208-100000@spider.nic-se.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Mon, 28 May 2001, Dan Oscarsson wrote:

> Not if you compare UDNS with IDNA.
> In IDNA you do nameprep (and destroy information) in the client.
> In UDNS, all UTF-8 encoded data is using normalised UCS form C.
> The "nameprep" equivalent is only used in matching of names.
> So name can retain all information.

Still, it has nothing to do with the choice between ACE and UTF-8. The
decision to have nameprep is based on reasoning in a different dimension.
You could have ACE without nameprep.


Mats

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





From owner-idn@ops.ietf.org  Mon May 28 06:46:36 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA02961
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 06:46:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154KDz-000DrB-00
	for idn-data@psg.com; Mon, 28 May 2001 03:26:11 -0700
Received: from citadel.cequrux.com ([192.96.22.18])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154KDr-000Dqx-00
	for idn@ops.ietf.org; Mon, 28 May 2001 03:26:07 -0700
Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id MAA04788 for <idn@ops.ietf.org>; Mon, 28 May 2001 12:25:41 +0200 (SAST)
Received: by citadel.cequrux.com via recvmail id 4778; Mon May 28 12:25:30 2001
X-Authentication-Warning: apb.cequrux.com: apb owned process doing -bs
Date: Mon, 28 May 2001 12:25:23 +0200 (SAST)
From: Alan Barrett <apb@cequrux.com>
To: <idn@ops.ietf.org>
Subject: Re: [idn] UTF-8 / RACE
In-Reply-To: <07cd01c0e6f4$1843f750$7dcb15a5@jamessonyvaio>
Message-ID: <Pine.NEB.4.33.0105281214060.422-100000@apb.cequrux.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Mon, 28 May 2001, James Seng/Personal wrote:
> Aside, I am a bit confuse by your defination of "UTF-8 with Fast
> Nameprep". When you mean "Fast Nameprep", do you mean we don't do
> Nameprep at all?

Dan Bernstein's "fast nameprep" means "early nameprep", where nameprep
happens once, as early as possible when the user types a domain name,
and everything outside the keyboard interface can assume that nameprep
has already been done.  Dan's "slow nameprep" means "late nameprep",
where just about anything that wants to do an IDN lookup needs to do
nameprep.

I don't believe that doing early nameprep removes the need for late
nameprep, because any number of intermediate transformations
(involving different encodings of UCS, different normalisations, or
even completely different character sets) might have happened between
the keyboard and the lookup.

--apb (Alan Barrett)




From owner-idn@ops.ietf.org  Mon May 28 07:26:33 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA03350
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 07:26:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154Kwa-000GSr-00
	for idn-data@psg.com; Mon, 28 May 2001 04:12:16 -0700
Received: from nic.cafax.se ([192.71.228.17])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154KwZ-000GSl-00
	for idn@ops.ietf.org; Mon, 28 May 2001 04:12:15 -0700
Received: (from bygg@localhost)
	by nic.cafax.se (8.12.0.Beta5/8.12.0.Beta5) id f4SBCDqv003576
	for idn@ops.ietf.org; Mon, 28 May 2001 13:12:13 +0200 (MEST)
Date: Mon, 28 May 2001 13:12:13 WET DST
From: Johnny Eriksson <bygg@cafax.se>
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
In-Reply-To: Your message of 28 May 2001 04:36:39 -0000
Message-ID: <CMM.0.90.0.991048333.bygg@nic.cafax.se>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

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

> it would have no advantages over simply fixing gethostbyname().

You keep talking about "fixing" gethostbyname.  Sometime people talk
about "fixing" the cat.  I firmly believe that all in all, the end
change in functionality will be in the same direction.

> ---Dan

--Johnny



From owner-idn@ops.ietf.org  Mon May 28 09:20:12 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA04382
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 09:20:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154Mby-000Ja4-00
	for idn-data@psg.com; Mon, 28 May 2001 05:59:06 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154Mbx-000JZy-00
	for idn@ops.ietf.org; Mon, 28 May 2001 05:59:05 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id IAA04824;
        Mon, 28 May 2001 08:59:02 -0400 (EDT)
Message-Id: <200105281259.IAA04824@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: Keith Moore <moore@cs.utk.edu>, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE 
In-reply-to: Your message of "Sun, 27 May 2001 23:51:03 PDT."
             <3B11F556.DCD1CD56@ehsco.com> 
Date: Mon, 28 May 2001 08:59:02 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > I don't think it's fair to characterize ACE as a halfway solution.
> 
> It requires significant additional computations and presentation
> processing for it to be anywhere near seamless for the user. 

Somehow I don't think I would characterize the additional computation
as 'significant' - it's a fairly trivial format conversion.  The
presentation processing is only a significant issue for those applications 
that don't already have to parse the input to distinguish components 
that contain domain names from those that don't.  Most appliations
that I can think off offhand already need to do this.  And even with
UTF-8, any application that accepts input of domain names would also
need to do this, becaue it would need to handle nameprep.

> UTF8 encoded data does not require multiple translations. 

That depends on whether you consider nameprep a translation.  

> Maybe "halfway" isn't proper
> descriptor for ACE (did I use it? no matter), but it's not a complete
> solution either.

Again, I don't see it.  In either the ACE case or the UTF8 case you have
to separate domain names from other text for the purpose of input.
In the case of ACE you have to separate them for the purpose of presentation
also, but often you would have had to do it anyway.  So there's a chance
of needing some additional complexity on the part of ACE for the purpose
of presentation but this is more than offset by not needing the complexity
of negotiation between components before exchanging domains in the
UTF8 case.  

> > since the vast majority of applications will be using standard APIs
> > which convert between native character set and encoding and those
> > used on the wire.  For this purpose, the application doesn't care
> > whether the format is UTF-8 or ACE.
> 
> My guess is that over the next 10 years, the majority of the systems will
> be either be native UTF8 or UTF32.

I'm not sure what you mean by "systems".  Operating systems will certainly
support UTF8, but may use other encodings also.  Applications will use
a variety of encodings internally.  New applications will probably use
a combination of UTF-8 and 32 bit representations.

Keith



From owner-idn@ops.ietf.org  Mon May 28 09:39:07 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA04570
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 09:39:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154N4j-000KXw-00
	for idn-data@psg.com; Mon, 28 May 2001 06:28:49 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154N4j-000KXq-00
	for idn@ops.ietf.org; Mon, 28 May 2001 06:28:49 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA05412;
        Mon, 28 May 2001 09:28:40 -0400 (EDT)
Message-Id: <200105281328.JAA05412@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Adonis El Fakih <adonis@ayna.com>
cc: James Seng/Personal <James@Seng.cc>,
        Sherin Alsoudani <sherinalsoudani@hotmail.com>, amc@cs.berkeley.edu,
        idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE 
In-reply-to: Your message of "Mon, 28 May 2001 03:29:47 EDT."
             <991034987.3b11fe6b1ef08@www.bareed.ayna.com> 
Date: Mon, 28 May 2001 09:28:40 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> It is easier to convert applications using 8bit encoding to use utf8 than doing
> RACE. 

How so?  if the application is just doing lookups, it will call an API routine
in either case, passing it a native-format IDN, and the API routine will take care 
of the nameprep and the conversion to and from ACE for the purpose of the lookup.

if the application is also generating IDNs, it has to call nameprep on the
domain in either case.  in the ACE case it also has to convert to ACE.
but both operations can be done in a single API call, the programmer can 
accomplish them with equal ease.

Keith



From owner-idn@ops.ietf.org  Mon May 28 11:56:42 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA05567
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 11:56:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154OyE-000Oik-00
	for idn-data@psg.com; Mon, 28 May 2001 08:30:14 -0700
Received: from arachnid.ehsco.com ([209.31.7.46] helo=Arachnid.NTRG.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154OyD-000Oic-00
	for idn@ops.ietf.org; Mon, 28 May 2001 08:30:13 -0700
Received: from ehsco.com (nat-external.ehsco.com [209.31.7.42])
          by Arachnid.NTRG.com (Netscape Messaging Server 3.62)  with ESMTP
          id 689; Mon, 28 May 2001 08:30:07 -0700
Message-ID: <3B126EFE.CBF34F6F@ehsco.com>
Date: Mon, 28 May 2001 08:30:06 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
References: <200105281259.IAA04824@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


> Again, I don't see it.  In either the ACE case or the UTF8 case you
> have to separate domain names from other text for the purpose of
> input. In the case of ACE you have to separate them for the purpose
> of presentation also, but often you would have had to do it anyway.

Domain names show up all over the place. lpq listings, netstat, etc. Even
in a GUI environment where font management was simpler, not much of this
stuff would convert ACE for output purposes. Opinion.

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



From owner-idn@ops.ietf.org  Mon May 28 12:04:24 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA05646
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 12:04:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154PHx-000PSt-00
	for idn-data@psg.com; Mon, 28 May 2001 08:50:37 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154PHw-000PSm-00
	for idn@ops.ietf.org; Mon, 28 May 2001 08:50:36 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id LAA06804;
        Mon, 28 May 2001 11:50:32 -0400 (EDT)
Message-Id: <200105281550.LAA06804@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
cc: Keith Moore <moore@cs.utk.edu>, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE 
In-reply-to: Your message of "Mon, 28 May 2001 08:30:06 PDT."
             <3B126EFE.CBF34F6F@ehsco.com> 
Date: Mon, 28 May 2001 11:50:32 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > Again, I don't see it.  In either the ACE case or the UTF8 case you
> > have to separate domain names from other text for the purpose of
> > input. In the case of ACE you have to separate them for the purpose
> > of presentation also, but often you would have had to do it anyway.
> 
> Domain names show up all over the place. lpq listings, netstat, etc. Even
> in a GUI environment where font management was simpler, not much of this
> stuff would convert ACE for output purposes. Opinion.

I agree.  even with an ACE scheme, most of the time when a domain appeared
in text it would appear in native format (i.e. whatever character set and
encoding were used by that text format) rather than ACE.

this is fine so long as:

- things that look up domains first nameprep and convert them to ACE
- things that compare domains know how to handle domains in both 
native and ACE formats

The worst problem with ACE is that legacy software will sometimes leak the
ACE form of a domain into ordinary text.   But I don't think that this 
will happen too much with ugpraded software (which will hide ACEs from the user). 

Keith



From owner-idn@ops.ietf.org  Mon May 28 13:57:19 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA06188
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 13:57:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154R6V-0003Ge-00
	for idn-data@psg.com; Mon, 28 May 2001 10:46:55 -0700
Received: from mail.lysator.liu.se ([130.236.254.3])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154R6U-0003GY-00
	for idn@ops.ietf.org; Mon, 28 May 2001 10:46:54 -0700
Received: from sandra.lysator.liu.se (sandra.lysator.liu.se [130.236.254.203])
	by mail.lysator.liu.se (Postfix) with ESMTP id 358C182F520
	for <idn@ops.ietf.org>; Mon, 28 May 2001 19:46:53 +0200 (MET DST)
Received: from localhost (mag@localhost)
	by sandra.lysator.liu.se (8.9.0/8.8.7) with SMTP id TAA05897
	for <idn@ops.ietf.org>; Mon, 28 May 2001 19:46:52 +0200 (MET DST)
X-Authentication-Warning: sandra.lysator.liu.se: mag owned process doing -bs
Date: Mon, 28 May 2001 19:46:52 +0200 (MET DST)
From: C C Magnus Gustavsson <mag@lysator.liu.se>
To: idn@ops.ietf.org
Subject: [idn] Moving forward
Message-ID: <Pine.GSO.4.00.10105281945410.5818-100000@sandra.lysator.liu.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

The current discussion is not leading anywere. The work group seemed
to make some progress half a year ago but now it's stuck again.


We should ask ourselves the following questions:

1. Do we require or want a rough consensus?

   There is a significant amount of people who demand ACE in the short
   term and another significant amount of people who demand UTF-8 in
   the long term.

   So if the answer is "no" we can run one part over and go for a ACE
   only or UTF-8 only solution.

   If the answer is "yes" we need to realize that there is only one
   solution that we might reach consensus about: arch-2 or "ACE now -
   UTF-8 eventually".

   It should be obvious by now that we can never agree on anything
   else even if we have this discussion until the End of Time. So, if
   we want consensus we should now move on to discuss the following:

2. Given arch-2, how can we make ACE and UTF-8 co-exist?

3. How is ACE to be phased out in the future?


I think we can agree then that some fallback solution is needed. If
UTF-8 is possible, the software must use it. Otherwise, use ACE. New
software must be able to use UTF-8 to comply to standards.

Then we know that ACE will eventually be phased out as soon as all
systems are upgraded. Then we don't need a deadline; we wouldn't be
able to enforce a deadline anyway.

Do we want consensus? Is this an acceptable way to move forward?


/Magnus (who didn't vote in the straw poll, lacking good alternatives)




From owner-idn@ops.ietf.org  Mon May 28 13:59:45 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA06204
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 13:59:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154R59-0003DL-00
	for idn-data@psg.com; Mon, 28 May 2001 10:45:31 -0700
Received: from mail.lysator.liu.se ([130.236.254.3])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154R58-0003Cy-00
	for idn@ops.ietf.org; Mon, 28 May 2001 10:45:30 -0700
Received: from sandra.lysator.liu.se (sandra.lysator.liu.se [130.236.254.203])
	by mail.lysator.liu.se (Postfix) with ESMTP
	id 396F082F482; Mon, 28 May 2001 19:45:28 +0200 (MET DST)
Received: from localhost (mag@localhost)
	by sandra.lysator.liu.se (8.9.0/8.8.7) with SMTP id TAA05860;
	Mon, 28 May 2001 19:45:27 +0200 (MET DST)
X-Authentication-Warning: sandra.lysator.liu.se: mag owned process doing -bs
Date: Mon, 28 May 2001 19:45:27 +0200 (MET DST)
From: C C Magnus Gustavsson <mag@lysator.liu.se>
To: "Adam M. Costello" <amc@cs.berkeley.edu>
Cc: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
In-Reply-To: <20010527213052.C17337@arwen.cs.berkeley.edu>
Message-ID: <Pine.GSO.4.00.10105281944310.5818-100000@sandra.lysator.liu.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Sun, 27 May 2001, Adam M. Costello wrote:

> What should they display?  They should display the ACE, because that's
> no uglier than anything else they might display, and has the added bonus
> that you can copy it into any other application and it will still work.

Yes, it is uglier than something else. How much uglier depends on what
ACE is chosen. In the worst case everything is garbage while most of
the characters could have been displayed correctly. In the best case
it's only unnecessary ugly because it's displaying an internal prefix
to the user and some of the characters in an uncommon way.

Furthermore, a computer can't always recognize what is a domain name
and what is not. I think it's pretty darn ugly that the same domain
e g in the header of a mail message and in the body of the same
message should be displayed in two completely different ways.

The problem of characters which can't be displayed should be solved in
exactly the same way it is today. Which is: Not standardized. Some
systems or programs can use a default character. Others, like Emacs,
could use a backslash ('\') and a coding point number. And so on.
Since the coding point is stored internally even though it can't be
displayed, there should be no problems with copying and pasting it.

ACE has it's advantages but the display problem is not a reason to
choose ACE. I think it's obvious that it should eventually be phased
out. Once again, in the long perspective we need a common encoding
like ASCII: The Unified Encoding that is used for every single piece
of text that is transmitted on the Internet.


> (The Roman alphabet is one of the smallest
> alphabets in existence, and is already widely recognized.  If you have
> to chose a fallback character set for everyone to learn, that's the best
> choice.)

Since you're not talking about the Roman alphabet here, I suggest you
use the term "English alphabet" instead. Even though the first is
based on the latter, they are not the same. Being correct doesn't hurt.

/Magnus




From owner-idn@ops.ietf.org  Mon May 28 15:24:00 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA06556
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 15:23:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154SU0-0006hM-00
	for idn-data@psg.com; Mon, 28 May 2001 12:15:16 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154STz-0006hF-00
	for idn@ops.ietf.org; Mon, 28 May 2001 12:15:15 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA08907;
        Mon, 28 May 2001 15:15:06 -0400 (EDT)
Message-Id: <200105281915.PAA08907@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: C C Magnus Gustavsson <mag@lysator.liu.se>
cc: "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE 
In-reply-to: Your message of "Mon, 28 May 2001 19:45:27 +0200."
             <Pine.GSO.4.00.10105281944310.5818-100000@sandra.lysator.liu.se> 
Date: Mon, 28 May 2001 15:15:05 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Furthermore, a computer can't always recognize what is a domain name
> and what is not. I think it's pretty darn ugly that the same domain
> e g in the header of a mail message and in the body of the same
> message should be displayed in two completely different ways.

I agree that it's ugly.  However this is a natural result of the fact
that header information is structured according to one standard
(RFC 822, now RFC 2822), and textual message bodies are encoding
with any of a variety of character encoding standards.

Currently, message headers are specified to be ASCII (with non-ASCII
portions encoded per RFC 2047), though in reality a variety of
character sets are used without labelling.  Textual body parts may be in 
any of several different character encodings, and these are sometimes
labelled correctly.    UTF-8 is allowed as one of the encodings for 
textual message bodies , but it is not widely used.

In order to reduce this "ugliness" of having different encodings
for message header and message body it would be necessary not only
to extend message headers to allow UTF-8 but also for UTF-8 to become
a popular method of encoding textual message bodies.  The latter 
seems unlikely to happen for a great many years, because even if many
user agents support the ability to display UTF-8, the number of user 
agents that can display other common character sets will still be greater.
Thus, for many languages, it will be safer to send text in some other
character set besides UTF-8. 
 
> ACE has it's advantages but the display problem is not a reason to
> choose ACE. I think it's obvious that it should eventually be phased
> out. Once again, in the long perspective we need a common encoding
> like ASCII: The Unified Encoding that is used for every single piece
> of text that is transmitted on the Internet.

I am not sure that we will find that Holy Grail anytime soon.
Even if we adopt UTF-8 we will still have to deal with various ways
of encoding "rich" text.

But this is all beside the point.  The IDN WG cannot legislate the 
encodings that are used by other applications; and it cannot legislate
that existing applications change their behavior.  It can only recommend
how to solve the I18N problem for domain names.  If the solution that
IDN recommends doesn't work well for some applications, it will not get
adopted for those applications - even if the recommended solution gets
approved as a standard.

It's very important to be realistic about what can be acheived.


I support the effort to craft a compromise around the idea of
ACE now - UTF-8 eventually.  But we need to realize that we cannot
mandate UTF-8 for existing applications within any particular
time frame.  

Keith



From owner-idn@ops.ietf.org  Mon May 28 15:25:38 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA06571
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 15:25:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154SVP-0006lf-00
	for idn-data@psg.com; Mon, 28 May 2001 12:16:43 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 154SVO-0006lW-00
	for idn@ops.ietf.org; Mon, 28 May 2001 12:16:42 -0700
Received: (qmail 1020 invoked by uid 1001); 28 May 2001 19:17:02 -0000
Date: 28 May 2001 19:17:02 -0000
Message-ID: <20010528191702.1600.qmail@cr.yp.to>
Mail-Followup-To: eric@sendmail.com,
  idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Cc: eric@sendmail.com
Subject: Re: [idn] Moving forward
References: <Pine.GSO.4.00.10105281945410.5818-100000@sandra.lysator.liu.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

C C Magnus Gustavsson writes:
> There is a significant amount of people who demand ACE in the short
> term and another significant amount of people who demand UTF-8 in
> the long term.

I'd like to see a poll on the question of whether UTF-8 will be the
long-term IDN solution. I suspect we have consensus that it will be. The
only person arguing for ACE-forever is Keith ``Q-P forever'' Moore.

It will help us move forward if we have a clear UTF-8 goal in mind. We
can, for example, agree that sendmail's destruction of 8-bit characters
is a bug, and has to be fixed.

The real decision is between ACE-then-UTF-8 and a direct move to UTF-8.
There appear to be more people in this group supporting ACE-then-UTF-8.
However, (1) many people here have been misled by incorrect statements
of the costs of ACE and UTF-8, and (2) UTF-8 appears to be the de facto
standard for working IDN experiments today.

---Dan



From owner-idn@ops.ietf.org  Mon May 28 15:38:23 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA06596
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 15:38:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154Sgo-0007Ek-00
	for idn-data@psg.com; Mon, 28 May 2001 12:28:30 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154Sgn-0007EI-00
	for idn@ops.ietf.org; Mon, 28 May 2001 12:28:29 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA09034;
        Mon, 28 May 2001 15:28:28 -0400 (EDT)
Message-Id: <200105281928.PAA09034@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
X-PGP-Key: 2F07A741 ; 78 15 8E 8B C0 06 5D D1  BC 08 05 7F 42 81 7E 90 
To: idn@ops.ietf.org
Subject: [idn] another idea
cc: moore@cs.utk.edu
From: Keith Moore <moore@cs.utk.edu>
Date: Mon, 28 May 2001 15:28:27 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I wonder how many people would support an "ACE now, UTF-8 eventually" solution
if there were a committment to upgrade the world wide web protocols to use
UTF-8 ASAP?

Many people have argued that the web protocols are easily upgraded.  Use of
UTF-8 with HTML is already defined, and many web browsers can display it if 
the appropriate fonts are installed (even if they don't nameprep IDNs in 
links before trying to open them).  The additional specification work needed 
to insure robust interoperability should be fairly minimal.  Furthermore,
the compatibility problems assocaited with upgrading the web also appear to 
be minimal (as compared to some other applications).  The web also makes
a good test case; the experience gained in upgrading web protocols should 
be useful to the efforts to upgrade other protocols.

Also, since the web is arguably the most visible Internet application, 
upgrading the web would be a big step toward making the Internet friendly
for those who use languages other than English.

While this WG can't insist that the work be done, my guess is that the 
appropriate communities would be interested in doing the work.

Keith 



From owner-idn@ops.ietf.org  Mon May 28 16:13:33 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA06802
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 16:13:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154T9k-0008LN-00
	for idn-data@psg.com; Mon, 28 May 2001 12:58:24 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154T9k-0008LH-00
	for idn@ops.ietf.org; Mon, 28 May 2001 12:58:24 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA09321;
        Mon, 28 May 2001 15:58:18 -0400 (EDT)
Message-Id: <200105281958.PAA09321@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, eric@sendmail.com
Subject: Re: [idn] Moving forward 
In-reply-to: Your message of "28 May 2001 19:17:02 -0000."
             <20010528191702.1600.qmail@cr.yp.to> 
Date: Mon, 28 May 2001 15:58:18 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> We can, for example, agree that sendmail's destruction of 8-bit 
>characters is a bug, and has to be fixed.

or we might agree that Dan's misrepresentations of other people's 
software, and other people's opinions, and operational reality in
general, are bugs which need to be fixed.  I suspect that we would 
not get consensus on this, but that we would get as least as much
agreement to this statement as to Dan's statement above.

Keith



From owner-idn@ops.ietf.org  Mon May 28 16:16:43 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA06813
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 16:16:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154TGk-0008YI-00
	for idn-data@psg.com; Mon, 28 May 2001 13:05: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.16 #1)
	id 154TGj-0008YC-00
	for idn@ops.ietf.org; Mon, 28 May 2001 13:05:37 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4SK5Kf93953;
	Mon, 28 May 2001 16:05:20 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105282005.f4SK5Kf93953@nic-naa.net>
To: Keith Moore <moore@cs.utk.edu>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] another idea 
In-Reply-To: Your message of "Mon, 28 May 2001 15:28:27 EDT."
             <200105281928.PAA09034@astro.cs.utk.edu> 
Date: Mon, 28 May 2001 16:05:19 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> I wonder how many people would support an "ACE now, UTF-8 eventually"

This revisits the speculative note of the 26th, without discernable
improvement. s/assurance/committment/.

> While this WG can't insist that the work be done, my guess is that the 

The amaya/jigsaw and mozilla/apache collaborative developments have i18n
projects, current status, and downloadable snapshots for test. For serious
inquiries, there are IE/IIS comperable bits as well. There are alternatives
to speculation.



From owner-idn@ops.ietf.org  Mon May 28 17:33:32 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA07410
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 17:33:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154UOl-000990-00
	for idn-data@psg.com; Mon, 28 May 2001 14:17:59 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 154UOk-00098t-00
	for idn@ops.ietf.org; Mon, 28 May 2001 14:17:58 -0700
Received: (qmail 17337 invoked by uid 1001); 28 May 2001 21:18:11 -0000
Date: 28 May 2001 21:18:11 -0000
Message-ID: <20010528211811.4490.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: [idn] Dots, and a path to working IDNs
References: <3B1180B6.8939BDC1@ehsco.com> <200105280227.WAA00791@astro.cs.utk.edu> <20010527213052.C17337@arwen.cs.berkeley.edu> <200105280200.WAA00572@astro.cs.utk.edu> <20010527202613.5518.qmail@cr.yp.to> <200105280114.VAA00203@astro.cs.utk.edu> <20010527165903.5833.qmail@cr.yp.to> <200105280106.VAA29976@astro.cs.utk.edu> <20010528050943.16457.qmail@cr.yp.to> <0a9c01c0e745$32399c90$7dcb15a5@jamessonyvaio>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James Seng/Personal writes:
> Incidently for those who cares, on a Chinese/Japanese IME, a dot can
> either be U+3002 or U+002E depending if it is full/half width and in
> Korean IME, a dot can either be U+FF9E or U+002E.

This is part of what I was referring to. Why aren't Keith and Patrik
screaming that we need dotprep in thousands of programs? Don't they care
about millions of confused users who have typed the wrong dot?

Reports from Japan suggest that, in fact, keyboard interfaces already
have adequate support for typing domain names. Users type the good dot,
the canonical dot, the ASCII dot. A domain name with a bad dot simply
doesn't work; the user fixes it.

Maybe users will keep trying to put bad dots into domain names for some
reason. Maybe we _do_ want to put dotprep into thousands of programs.
Okay; we'll do that if and when the need for it is clear. However, in
the meantime, we can still use dots!

We can handle UTF-8 IDNs the same way:

   * People will register good UTF-8 IDNs. Lowercase, ASCII dots, no
     confusing characters. We can distribute name-checking software so
     that DNS administrators can make sure their IDNs are good.

   * It's the responsibility of the keyboard interface to help users
     type good IDNs. Bad IDNs simply won't work.

   * Maybe users will keep putting bad characters into domain names for
     some reason. Maybe we really _do_ want slow nameprep, with
     thousands of programs converting bad IDNs to good IDNs. Okay; we'll
     do that if and when the need for it is clear. However, in the
     meantime, we can still use IDNs!

This way we get useful IDNs as soon as possible. We take advantage of
all the existing UTF-8 support. If it turns out that the user interface
isn't good enough, that we need to suffer the massive costs of upgrading
and redeploying thousands of programs, then we'll do that. The existing
IDNs will continue to work.

There are two obstacles to having these IDNs work instantaneously. One
is that many versions of gethostbyname() reject 8-bit characters. The
other is that sendmail destroys bytes 128-159 (which don't show up in
lowercase European characters in UTF-8, but which do show up in other
characters). Both of these problems should be fixed as soon as possible.

---Dan



From owner-idn@ops.ietf.org  Mon May 28 17:38:36 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA07434
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 17:38:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154UXo-0009Dd-00
	for idn-data@psg.com; Mon, 28 May 2001 14:27:20 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154UXn-0009DX-00
	for idn@ops.ietf.org; Mon, 28 May 2001 14:27:19 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0AY64l30v0UYe1cBY7HXnA+Pv9/hSkRVQ==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id F6KBKJUS; Mon, 28 May 2001 17:26:45 EDT
To: djb@cr.yp.to
Cc: idn@ops.ietf.org
Date: Mon, 28 May 2001 14:37:45 -0700
Subject: Re: [idn] Moving forward
Message-ID: <20010528.144003.-817845.0.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.5
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Att: 0
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

 I am preparing an ACE draft which suggest that UTF-8 may be unnecessary
for IDN.  Sorry, that I can not be any faster.

Liana 

On 28 May 2001 19:17:02 -0000 "D. J. Bernstein" <djb@cr.yp.to> writes:
> C C Magnus Gustavsson writes:
> > There is a significant amount of people who demand ACE in the 
> short
> > term and another significant amount of people who demand UTF-8 in
> > the long term.
> 
> I'd like to see a poll on the question of whether UTF-8 will be the
> long-term IDN solution. I suspect we have consensus that it will be. 
> The
> only person arguing for ACE-forever is Keith ``Q-P forever'' Moore.
> 
> It will help us move forward if we have a clear UTF-8 goal in mind. 
> We
> can, for example, agree that sendmail's destruction of 8-bit 
> characters
> is a bug, and has to be fixed.
> 
> The real decision is between ACE-then-UTF-8 and a direct move to 
> UTF-8.
> There appear to be more people in this group supporting 
> ACE-then-UTF-8.
> However, (1) many people here have been misled by incorrect 
> statements
> of the costs of ACE and UTF-8, and (2) UTF-8 appears to be the de 
> facto
> standard for working IDN experiments today.
> 
> ---Dan
> 



From owner-idn@ops.ietf.org  Mon May 28 17:50:48 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA07484
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 17:50:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154Umx-0009MQ-00
	for idn-data@psg.com; Mon, 28 May 2001 14:42:59 -0700
Received: from [152.160.20.25] (helo=admin1.corp.walid.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154Umw-0009Lv-00
	for idn@ops.ietf.org; Mon, 28 May 2001 14:42:58 -0700
Received: from CHOAM (admin1.corp.walid.com [152.160.20.25])
	by admin1.corp.walid.com (8.9.3/8.9.3) with SMTP id VAA20617;
	Mon, 28 May 2001 21:41:52 GMT
From: "Brian W. Spolarich" <briansp@walid.com>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
Cc: <eric@sendmail.com>
Subject: RE: [idn] Moving forward
Date: Mon, 28 May 2001 17:44:29 -0400
Message-ID: <FJEPLIJJEDBNPIOAEIHDIEOMCDAA.briansp@walid.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
In-Reply-To: <20010528191702.1600.qmail@cr.yp.to>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


| 
| The real decision is between ACE-then-UTF-8 and a direct move to UTF-8.
| There appear to be more people in this group supporting ACE-then-UTF-8.
| However, (1) many people here have been misled by incorrect statements
| of the costs of ACE and UTF-8, and (2) UTF-8 appears to be the de facto
| standard for working IDN experiments today.

  Depends entirely on your definition of 'working'.  From what I've 
seen of the 'just send UTF-8' approaches out there they 1) completely
ignore the normalization issues and 2) completely ignore the applications,
protocols, etc. that are not directly user-facing.

  -bws



From owner-idn@ops.ietf.org  Mon May 28 17:50:50 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA07495
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 17:50:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154Un5-0009MX-00
	for idn-data@psg.com; Mon, 28 May 2001 14:43:07 -0700
Received: from [152.160.20.25] (helo=admin1.corp.walid.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154Un4-0009M4-00
	for idn@ops.ietf.org; Mon, 28 May 2001 14:43:06 -0700
Received: from CHOAM (admin1.corp.walid.com [152.160.20.25])
	by admin1.corp.walid.com (8.9.3/8.9.3) with SMTP id VAA20620;
	Mon, 28 May 2001 21:41:53 GMT
From: "Brian W. Spolarich" <briansp@walid.com>
To: "James Seng/Personal" <James@Seng.cc>,
        "Sherin Alsoudani" <sherinalsoudani@hotmail.com>,
        <amc@cs.berkeley.edu>, <idn@ops.ietf.org>
Subject: RE: [idn] UTF-8 / RACE
Date: Mon, 28 May 2001 17:44:30 -0400
Message-ID: <FJEPLIJJEDBNPIOAEIHDKEOMCDAA.briansp@walid.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
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)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
In-Reply-To: <0a8c01c0e744$85e19600$7dcb15a5@jamessonyvaio>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


| I am kind of worried on the statement "out-of-the-box".

  Me too.  This usually means 'on my particular box, with my
particular software and configuration'.

| You see, given my experience in this field, it is *very* easy to
| demostrate a system which works "out-of-the-box" under the right
| combination, e.g. Arabic IE in Arabic-enabled Windows using Arabic
| domain names.
|
| Have you try Chinese URL on Arabic IE on Thai Windows? I did and I wont
| classify the result as "out-of-the-box".

  Based on our experience with WALID WorldConnect, these kind of scenarios
will yield undefined, unexpected, and sometimes entertaining results (and
I expect the i-DNS iClient testers went through similar gyrations, weeping,
and gnashing of teeth).

  -bws




From owner-idn@ops.ietf.org  Mon May 28 18:28:36 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA07689
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 18:28:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154VJJ-0009n3-00
	for idn-data@psg.com; Mon, 28 May 2001 15:16:25 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 154VJI-0009mx-00
	for idn@ops.ietf.org; Mon, 28 May 2001 15:16:24 -0700
Received: (qmail 20027 invoked by uid 1001); 28 May 2001 22:16:45 -0000
Date: 28 May 2001 22:16:45 -0000
Message-ID: <20010528221645.27870.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: [idn] Extending gethostbyname()
References: <20010528032518.26680.qmail@cr.yp.to> <200105280355.f4S3tjv60619@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Mark.Andrews@nominum.com writes:
> Yes we are talking here about extending RFC 952, however
> that does not imply that it is necessarily safe to extend
> gethostbyname().  The safest thing to do is to specify a
> new API which is defined to accept IHN and return IHN's.

Perhaps you have forgotten that RFC 952 is obsolete. RFC 1123 extended
the host name syntax twelve years ago.

The gethostbyname() maintainers could have insisted that gethostbyname()
be used only for the old syntax. They could have introduced an idiotic
new gethostbyextendedname() function. They could have forced programs to
switch from gethostbyname() to gethostbyextendedname() to support the
new syntax.

In short, they could have changed a simple syntax extension into a
compatibility disaster. But they didn't.

---Dan



From owner-idn@ops.ietf.org  Mon May 28 19:07:19 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA08000
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 19:07:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154VtJ-000ATG-00
	for idn-data@psg.com; Mon, 28 May 2001 15:53:37 -0700
Received: from mail.lysator.liu.se ([130.236.254.3])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154VtI-000AT9-00
	for idn@ops.ietf.org; Mon, 28 May 2001 15:53:36 -0700
Received: from sandra.lysator.liu.se (sandra.lysator.liu.se [130.236.254.203])
	by mail.lysator.liu.se (Postfix) with ESMTP
	id 49B0482F487; Tue, 29 May 2001 00:53:34 +0200 (MET DST)
Received: from localhost (mag@localhost)
	by sandra.lysator.liu.se (8.9.0/8.8.7) with SMTP id AAA09635;
	Tue, 29 May 2001 00:53:33 +0200 (MET DST)
X-Authentication-Warning: sandra.lysator.liu.se: mag owned process doing -bs
Date: Tue, 29 May 2001 00:53:33 +0200 (MET DST)
From: C C Magnus Gustavsson <mag@lysator.liu.se>
To: Keith Moore <moore@cs.utk.edu>
Cc: "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE 
In-Reply-To: <200105281915.PAA08907@astro.cs.utk.edu>
Message-ID: <Pine.GSO.4.00.10105290049450.9614-100000@sandra.lysator.liu.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Mon, 28 May 2001, Keith Moore wrote:

> > Furthermore, a computer can't always recognize what is a domain name
> > and what is not. I think it's pretty darn ugly that the same domain
> > e g in the header of a mail message and in the body of the same
> > message should be displayed in two completely different ways.
> 
> I agree that it's ugly.  However this is a natural result of the fact
> that header information is structured according to one standard
> (RFC 822, now RFC 2822), and textual message bodies are encoding
> with any of a variety of character encoding standards.
> 
> Currently, message headers are specified to be ASCII (with non-ASCII
> portions encoded per RFC 2047), though in reality a variety of
> character sets are used without labelling.  Textual body parts may be in 
> any of several different character encodings, and these are sometimes
> labelled correctly.    UTF-8 is allowed as one of the encodings for 
> textual message bodies , but it is not widely used.

No, it's a natural result of mr Costellos suggestion that domains with
characters that can't be displayed should be displayed as ACE. I fail
to see that your comment is relevant to what I wrote. Perhaps you
should read what I wrote and replied to one more time?


Let's say John Luser sends the following mail to you (where <oe> is o
with umlaut).

  From: John Luser <luser@f<oe>reningen.org>
  To: Keith Moore <moore@cs.utk.edu>
  Subject: Hello
  Content-Type: TEXT/PLAIN; charset=ISO-8859-1
  Content-Transfer-Encoding: 8BIT
  
  Hello Keith,
  
  Why don't you take a look at our new website on f<oe>reningen.org?
  
  Have a nice day!
  
  John


Now, let's say your local system knows about ISO 8859-1 and is able to
convert it to the internal encoding but unable to display <oe>. Thus
it displays it as [] (square box - your systems default character).


With mr Costellos suggestion this would be displayed to you as:

  From: John Luser <luser@px--sdn3fnfuwy4rn5wutn.org>
  To: Keith Moore <moore@cs.utk.edu>
  Subject: Hello
  
  Hello Keith,
  
  Why don't you take a look at our new website on f[]reningen.org?
  
  Have a nice day!
  
  John


(Or whatever the chosen ACE encoding turns it into.)

It's hard to recognize px--sdn3fnfuwy4rn5wutn.org as the same domain
as f[]reningen.org. It's a lot uglier as well.

A less ugly way of displaying it would be:


  From: John Luser <luser@f[]reningen.org>
  To: Keith Moore <moore@cs.utk.edu>
  Subject: Hello
  
  Hello Keith,
  
  Why don't you take a look at our new website on f[]reningen.org?
  
  Have a nice day!
  
  John


You don't know what character [] is but at least it's displayed in the
same way. Since there's no way for your computer to know that
f[]reningen.org in the body is a domain name instead of a number, a
missed space or whatever it can't turn it into ACE.

It doesn't matter that the header domain is encoded in ACE/UTF-8 and
the body in ISO 8859-1 since your system can convert them both to it's
internal format. The set of characters available in your systems
font(s) is still the same no matter what encoding is used.

ACE is always a worse and an uglier thing to display when a system
encounters unknown characters. Thus it's hardly an argument for using
ACE. I can't agree that displaying the domain in the header as ACE,
i e as "px--f+xg-reningen.org", "px--sdn3fnfuwy4rn5wutn.org" or
whatever, is "no uglier than anything else they might display".

The same goes for everything else. Let's say we have a web page where
location is "http://px--sdn3fnfuwy4rn5wutn.org" and the text on the
page says "Welcome to f[]reningen.org!". And so on...

Do you understand what I'm saying now?


> In order to reduce this "ugliness" of having different encodings
> for message header and message body it would be necessary not only
> to extend message headers to allow UTF-8 but also for UTF-8 to become
> a popular method of encoding textual message bodies.  The latter 
> seems unlikely to happen for a great many years, because even if many
> user agents support the ability to display UTF-8, the number of user 
> agents that can display other common character sets will still be greater.
> Thus, for many languages, it will be safer to send text in some other
> character set besides UTF-8. 

See above. That is not the ugliness I was refering to. What I was
refering to was the suggestion that applications wanting "to display
IDNs containing unsupported characters [...] should display the ACE".


> > ACE has it's advantages but the display problem is not a reason to
> > choose ACE. I think it's obvious that it should eventually be phased
> > out. Once again, in the long perspective we need a common encoding
> > like ASCII: The Unified Encoding that is used for every single piece
> > of text that is transmitted on the Internet.
> 
> I am not sure that we will find that Holy Grail anytime soon.
> Even if we adopt UTF-8 we will still have to deal with various ways
> of encoding "rich" text.

True, but we have to start somewhere. Every journey begins with a
single step. (Although, this journey started with BCP 18. This is just
a very large and important step on the way.)


> But this is all beside the point.  The IDN WG cannot legislate the 
> encodings that are used by other applications; and it cannot legislate
> that existing applications change their behavior.  It can only recommend
> how to solve the I18N problem for domain names.  If the solution that
> IDN recommends doesn't work well for some applications, it will not get
> adopted for those applications - even if the recommended solution gets
> approved as a standard.
> 
> It's very important to be realistic about what can be acheived.

Sure, but it is hardly a reason or excuse for this WG to suggest a bad
solution. And I fail to see what it has to do with displaying domains
as ACE when the application encounters unknown characters.

/Magnus





From owner-idn@ops.ietf.org  Mon May 28 20:56:08 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA08420
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 20:56:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154XMD-000BaX-00
	for idn-data@psg.com; Mon, 28 May 2001 17:27:33 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154XMC-000BaR-00
	for idn@ops.ietf.org; Mon, 28 May 2001 17:27:32 -0700
Received: from [165.227.249.18] (ip18.proper.com [165.227.249.18])
	by above.proper.com (8.9.3/8.9.3) with ESMTP id RAA07925
	for <idn@ops.ietf.org>; Mon, 28 May 2001 17:27:28 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0510030eb7389ab8633e@[165.227.249.18]>
In-Reply-To: <20010528191702.1600.qmail@cr.yp.to>
References: 
 <Pine.GSO.4.00.10105281945410.5818-100000@sandra.lysator.liu.se>
 <20010528191702.1600.qmail@cr.yp.to>
Date: Mon, 28 May 2001 17:26:29 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] Moving forward
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 7:17 PM +0000 5/28/01, D. J. Bernstein wrote:
>I'd like to see a poll on the question of whether UTF-8 will be the
>long-term IDN solution. I suspect we have consensus that it will be. The
>only person arguing for ACE-forever is Keith ``Q-P forever'' Moore.

Keith is not the only person arguing for it, and he is not the only 
person supporting it. Many people would rather be poked in the eye 
with a sharp stick than to try to argue with you. As has been seen 
over the years, many people also would rather be silent than agree 
with you because you often turn and attack your supporters.

Thus, the small number of people on the list who are willing to take 
either position doesn't mean that a small number of people have an 
opinion.

The best way to resolve this is for someone who supports the "first 
ACE then UTF-8" position to write an Internet Draft. That person 
needs to be someone who is willing to later edit the draft to include 
other people's opinions, and to revise it in a timely manner when 
people comment on it. The draft needs to cover how the new protocols, 
and the change between them, affects applications, protocols, and 
users. Until there is a draft that gives the arguments in detail, 
there is no reasonable way to compare it to IDNA.

And, yes, Patrik and I need to add more about all of this in the IDNA 
draft. Look for something this week.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Mon May 28 21:20:07 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA08495
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 21:20:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154XyW-000C0V-00
	for idn-data@psg.com; Mon, 28 May 2001 18:07:08 -0700
Received: from drugs.dv.isc.org ([130.155.191.236])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154XyV-000C0O-00
	for idn@ops.ietf.org; Mon, 28 May 2001 18:07:07 -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 f4T15hv66344
	for <idn@ops.ietf.org>; Tue, 29 May 2001 11:05:45 +1000 (EST)
	(envelope-from marka@nominum.com)
Message-Id: <200105290105.f4T15hv66344@drugs.dv.isc.org>
To: idn@ops.ietf.org
From: Mark.Andrews@nominum.com
Mail-Followup-To: idn@ops.ietf.org 
Subject: Re: [idn] Extending gethostbyname() 
In-reply-to: Your message of "28 May 2001 22:16:45 GMT."
             <20010528221645.27870.qmail@cr.yp.to> 
Date: Tue, 29 May 2001 11:05:43 +1000
Sender: owner-idn@ops.ietf.org
Precedence: bulk


> Mark.Andrews@nominum.com writes:
> > Yes we are talking here about extending RFC 952, however
> > that does not imply that it is necessarily safe to extend
> > gethostbyname().  The safest thing to do is to specify a
> > new API which is defined to accept IHN and return IHN's.
> 
> Perhaps you have forgotten that RFC 952 is obsolete. RFC 1123 extended
> the host name syntax twelve years ago.

	RFC 1123 did not obsolete RFC 952, it updated it.

> 
> The gethostbyname() maintainers could have insisted that gethostbyname()
> be used only for the old syntax. They could have introduced an idiotic
> new gethostbyextendedname() function. They could have forced programs to
> switch from gethostbyname() to gethostbyextendedname() to support the
> new syntax.

	I'm sure they thought about it.  Relaxing the requirements
	to allow a digit as the first character of a label broke
	some applications as did the extention from 63 to 255
	characters.  These were trivial changes compared to what
	is being proposed here.

	It took years for some mailers to be able to mail to
	user@3com.com.

> 
> In short, they could have changed a simple syntax extension into a
> compatibility disaster. But they didn't.

	This is not a simple syntax extension.  It a radical change.

	Mark

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



From owner-idn@ops.ietf.org  Mon May 28 23:35:53 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA11385
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 23:35:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154ZzY-000CjM-00
	for idn-data@psg.com; Mon, 28 May 2001 20:16:20 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154ZzY-000CjG-00
	for idn@ops.ietf.org; Mon, 28 May 2001 20:16:20 -0700
Received: from [165.227.249.18] (ip18.proper.com [165.227.249.18])
	by above.proper.com (8.9.3/8.9.3) with ESMTP id UAA17920
	for <idn@ops.ietf.org>; Mon, 28 May 2001 20:16:14 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p0510031ab738c3c80950@[165.227.249.18]>
Date: Mon, 28 May 2001 20:15:15 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: [idn] Preliminary report from the ACE Design Team
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

The ACE Design Team has been evaluating the large number of ACEs that 
have been proposed in the IDN WG. In comparing them, we have looked 
primarily at two factors:
- how easy they are to understand and implement
- how they would restrict long names that are likely to be used

We are not ready to issue a final report, but we expect to do so 
soon; when we do, it will be as an Internet Draft. However, we want 
the WG to know that when we issue the report, we hope to recommend a 
single ACE. Further, we are quite sure that the ACE we recommend will 
*not* be RACE. That is, we are quite sure that our recommendation 
will be an ACE that, when compared with RACE, is both easier to 
understand and implement, and will have similar or less restriction 
on long names that are likely to be used.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Mon May 28 23:47:18 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA11509
	for <idn-archive@lists.ietf.org>; Mon, 28 May 2001 23:47:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154aDT-000Cpm-00
	for idn-data@psg.com; Mon, 28 May 2001 20:30:43 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154aDS-000Cpg-00
	for idn@ops.ietf.org; Mon, 28 May 2001 20:30:42 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 154aDR-0006IC-00; Mon, 28 May 2001 20:30:41 -0700
Date: Tue, 29 May 2001 03:30:41 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
Message-ID: <20010529033041.B22313@arwen.cs.berkeley.edu>
References: <20010527202613.5518.qmail@cr.yp.to> <083c01c0e6f7$235b7200$7dcb15a5@jamessonyvaio> <20010527220531.E17337@arwen.cs.berkeley.edu> <F599No5I9BADCDLTyHU0000f121@hotmail.com> <7544575.990957280@localhost> <20010527165903.5833.qmail@cr.yp.to> <079c01c0e6e4$3bf7ee50$7dcb15a5@jamessonyvaio> <20010527202613.5518.qmail@cr.yp.to> <083c01c0e6f7$235b7200$7dcb15a5@jamessonyvaio> <20010528043639.9273.qmail@cr.yp.to>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <20010528043639.9273.qmail@cr.yp.to>; from djb@cr.yp.to on Mon, May 28, 2001 at 04:36:39AM -0000
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

This message contains replies to D. J. Bernstein, C C Magnus Gustavsson,
and Eric A. Hall.

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

> > telnet `ace NATIVECHARACTERS`
> 
> Even if that were a complete solution

It's not.  It's a workaround that people could use while they're waiting
for stuff to get upgraded.

> what do you do about telnet's open command?

Nothing.  I'd quit telnet and start it again as above.

> or its status display?

Ignore it.  This is just a workaround.  The point is that with ACE
workarounds are possible.  Without ACE, when things choke on UTF-8
names, you're just out of luck until stuff gets upgraded, and some of
that stuff might not be under your control.

> it would have no advantages over simply fixing gethostbyname().

It would have a few minor advantages:  Installing a standalone program
is easier than upgrading libc.  The upgraded gethostbyname() will work
only if my local DNS server doesn't choke on UTF-8 names, whereas the
ace program doesn't depend on anything outside my system.

But I'll admit, for telnet, the advantages are minor.  Let's try mail.
Upgrading gethostbyname() is not going to allow "mail user1@IDN.org
user2@foo.bar" to work, because the mail program still has to get
IDN.org into the header somehow.  Putting UTF-8 directly into the header
violates RFC 822 and RFC 821, and even if it somehow gets to user1
intact, it might not get to user2 intact, and even if it does, user2's
mail program might choke on it.  Without ACE, it's simply not going
to work until I upgrade my mail program, and user2 upgrades his mail
program, and all the intervening SMTP servers get upgraded.  But with
ACE, I have a workaround that doesn't depend on anyone else upgrading
anything: mail user1@`ace IDN.org` user2@foo.bar

> Except, of course, for all the programs that _already_ work with
> UTF-8.

Yes, the advantage of UTF-8 is that some programs already use it
natively, and they might be able to use IDNs by accident.  But there are
also many programs that don't use UTF-8.  I use a terminal emulator and
a text editor and a web browser all written to support Japanese (kterm,
nvi-m17n, w3m), and none of them supports UTF-8.  They could all benefit
immediately from the sort of ACE workarounds described above.

Remember, I'm not arguing against UTF-8; I'm merely arguing in favor of
ACE.  I'm certainly willing to consider an architecture where both are
used.

C C Magnus Gustavsson <mag@lysator.liu.se> wrote:

> The problem of characters which can't be displayed should be solved
> in exactly the same way it is today. Which is: Not standardized. Some
> systems or programs can use a default character. Others, like Emacs,
> could use a backslash ('\') and a coding point number. And so on.

Okay, I'll back off a little on my claim that the ACE should be
displayed when the name contains unsupported characters.  Ideally it
should be a user-configurable option.  I personally would choose the
ACE, so that I could cut and paste it.

> Since the coding point is stored internally even though it can't be
> displayed, there should be no problems with copying and pasting it.

I agree that there "should" be no problems, but there will be.  In my
experience, copying text with the mouse usually gives you exactly what
is displayed; very rarely does the application intercept the operation,
because it's usually being handled entirely by the GUI library.

> I think it's obvious that [ACE] should eventually be phased out.

It's not obvious to me.  Someone (Keith?) mentioned archived mail.
Should those addresses arbitrarily stop working someday?

> Since you're not talking about the Roman alphabet here, I suggest you
> use the term "English alphabet" instead.

<offtopic> I rarely hear the phrase "English alphabet".  When I do, I
think to myself, "There is no English alphabet.  English uses the Roman
alphabet."  The phrase "Roman alphabet" is the more common name for the
letters A-Z.  "English alphabet" sounds arrogant to me, since England
merely inherited the alphabet from the Roman empire.  The most formally
correct phrase might be "modern Roman alphabet". </offtopic>

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

> Domain names show up all over the place. lpq listings, netstat,
> etc. Even in a GUI environment where font management was simpler, not
> much of this stuff would convert ACE for output purposes. Opinion.

Agreed.  If netstat gets back UTF-8 from gethostbyaddr() and blindly
outputs it, it will look nice if it happens to be running in a UTF-8
environment, and will produce useless garbage otherwise.  If it gets
back ACE, it will produce garbage in all environments, but potentially
useful garbage (because it can be copied into other applications).
There will be problems of one sort or another until netstat is upgraded
to call a function that returns the domain name in the local charset.

AMC



From owner-idn@ops.ietf.org  Tue May 29 00:41:27 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA11771
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 00:41:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154b4k-000DCD-00
	for idn-data@psg.com; Mon, 28 May 2001 21:25:46 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 154b4j-000DC4-00
	for idn@ops.ietf.org; Mon, 28 May 2001 21:25:45 -0700
Received: (qmail 27350 invoked by uid 1001); 29 May 2001 04:25:57 -0000
Date: 29 May 2001 04:25:57 -0000
Message-ID: <20010529042557.13041.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: [idn] UTF-8 as the long-term IDN solution
References: <Pine.GSO.4.00.10105281945410.5818-100000@sandra.lysator.liu.se> <20010528191702.1600.qmail@cr.yp.to> <p0510030eb7389ab8633e@[165.227.249.18]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I suspect that we have consensus that the long-term IDN solution will
encode Unicode characters as UTF-8 on the wire. I request that the WG
chairs run a poll to see whether we have consensus.

If we do, in fact, have consensus on this point, then we can stop
wasting time considering ACE-now-and-forever. We can instead compare
the actual possibilities: (1) ACE-now-UTF-8-later; (2) simply UTF-8.

---Dan

P.S. I'm not going to bother responding to Hoffman's ad-hominem attacks.



From owner-idn@ops.ietf.org  Tue May 29 01:02:14 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA11842
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 01:02:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154bSC-000DLp-00
	for idn-data@psg.com; Mon, 28 May 2001 21:50:00 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154bSB-000DLi-00
	for idn@ops.ietf.org; Mon, 28 May 2001 21:49:59 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id AAA13143;
        Tue, 29 May 2001 00:49:50 -0400 (EDT)
Message-Id: <200105290449.AAA13143@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
cc: Keith Moore <moore@cs.utk.edu>, idn@ops.ietf.org
Subject: Re: [idn] another idea 
In-reply-to: Your message of "Mon, 28 May 2001 16:05:19 EDT."
             <200105282005.f4SK5Kf93953@nic-naa.net> 
Date: Tue, 29 May 2001 00:49:50 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > I wonder how many people would support an "ACE now, UTF-8 eventually"
> 
> This revisits the speculative note of the 26th, without discernable
> improvement. s/assurance/committment/.

The difference is the suggestion that the web adopt UTF-8 ASAP,
since this application seems to be of special interest and also because
the web appears to be easier to fix than some applications.

> > While this WG can't insist that the work be done, my guess is that the
> 
> The amaya/jigsaw and mozilla/apache collaborative developments have i18n
> projects, current status, and downloadable snapshots for test. For serious
> inquiries, there are IE/IIS comperable bits as well. There are alternatives
> to speculation.

There is also a difference between prototyping and specification.

Keith



From owner-idn@ops.ietf.org  Tue May 29 01:02:15 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA11843
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 01:02:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154bRa-000DLY-00
	for idn-data@psg.com; Mon, 28 May 2001 21:49:22 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154bRZ-000DLS-00
	for idn@ops.ietf.org; Mon, 28 May 2001 21:49:21 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 154bRZ-0006Mr-00; Mon, 28 May 2001 21:49:21 -0700
Date: Tue, 29 May 2001 04:49:21 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Moving forward
Message-ID: <20010529044920.C22313@arwen.cs.berkeley.edu>
References: <Pine.GSO.4.00.10105281945410.5818-100000@sandra.lysator.liu.se> <20010528191702.1600.qmail@cr.yp.to> <Pine.GSO.4.00.10105281945410.5818-100000@sandra.lysator.liu.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <Pine.GSO.4.00.10105281945410.5818-100000@sandra.lysator.liu.se>; from mag@lysator.liu.se on Mon, May 28, 2001 at 07:46:52PM +0200
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

C C Magnus Gustavsson <mag@lysator.liu.se> wrote:

> we need to realize that there is only one solution that we might reach
> consensus about: arch-2 or "ACE now - UTF-8 eventually".

I agree if you mean that any solution with a chance of fostering
consensus must allow ACE now and must encourage UTF-8 in the future.  I
suspect that we will be even more likely to reach consensus if we allow
UTF-8 to coexist with ACE as soon as possible, and if we don't require a
complete ACE phase-out any time soon.

How about this model:

Just as there are now multiple ways to represent domain names (ASCII,
EBCDIC, ink on paper, ...) and one especially customary way (ASCII),
there will be many ways to represent IDNs (ACE, UTF-8, UTF-16,
iso-2022-jp, koi8, ink on paper, ...) and two especially customary ways
(ACE and UTF-8).

Obviously any existing protocol that defines a hostname as a sequence
of dot-separated LDH labels has no choice but to use ACE.  New versions
of those protocols may opt to support UTF-8 in addition.  New protocols
must support UTF-8 domain names (I think that follows from an existing
IETF policy regarding UTF-8), which implies that they can also handle
ASCII names, including ACE names.

Senders must not send UTF-8 domain names unless they know that the
receiver can handle it (based on the protocol or protocol-version).
Any program that might sometimes send a domain name to a receiver that
cannot handle UTF-8 names must be prepared to perform ACE encoding.
Notice that this does not apply to new protocols, since new protocols
are required to support UTF-8 names.

Programs that send domain names to receivers known to handle UTF-8 names
may perform ACE decoding on ACEs before sending, but are not required or
even encouraged to do so (because maybe someday ACE will be rare and it
would be useless functionality).

Programs that display domain names to users should perform ACE decoding.
Maybe someday, if ACE becomes rare, this could be weakened from "should"
to "may".

DNS servers must accept both UTF-8 and ACE queries (how it accepts
UTF-8 queries is an open question).  Maybe someday DNS will be the only
protocol left that uses ACE.  If/when that happens, we can revisit the
phase-out question.

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

> We can, for example, agree that sendmail's destruction of 8-bit
> characters is a bug

Given that RFC 821 specifies that messages shall be 7-bit, I don't think
it's fair to characterize sendmail's handling of 8-bit characters as a
bug.  We might agree that it should change anyway, but I think that's a
matter for a different working group.

AMC



From owner-idn@ops.ietf.org  Tue May 29 01:02:16 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA11857
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 01:02:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154bQ3-000DKr-00
	for idn-data@psg.com; Mon, 28 May 2001 21:47:47 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 154bQ2-000DKk-00
	for idn@ops.ietf.org; Mon, 28 May 2001 21:47:46 -0700
Received: (qmail 27630 invoked by uid 1001); 29 May 2001 04:47:34 -0000
Date: 29 May 2001 04:47:34 -0000
Message-ID: <20010529044734.1803.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] Extending gethostbyname()
References: <20010528221645.27870.qmail@cr.yp.to> <200105290105.f4T15hv66344@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Did the RFC 1123 authors worry about some badly written programs having
trouble with names like 3com.com? Yes, they did. Did that stop them from
extending the host name syntax? No, it didn't.

Those programs were declared buggy, and they were fixed, and now we can
use 3com.com without trouble. Programmers don't have to encode 3com.com
as ACE-GARBAGE-DIGIT-THREE-LETTER-C-LETTER-O-LETTER-M.com.

Now, do we want to follow the model of RFC 1123's easy syntax extension?
Or do we want to follow the model of RFC 1342, which is continuing to
annoy users and programmers a decade after its introduction, and which
promises to continue annoying us for decades to come?

Mark.Andrews@nominum.com writes:
> Relaxing the requirements to allow a digit as the first character of a
> label broke some applications

Extending gethostbyname() didn't break anything. In fact, extending
gethostbyname() made it vastly _easier_ for applications to support the
new syntax. Most applications worked perfectly, no effort required.

In contrast, if gethostbyname() had enforced the old syntax, and if an
idiotic new gethostbyextendedname() function had been introduced for the
new syntax, nothing would have worked. Every application would have had
to switch from gethostbyname() to gethostbyextendedname(). Ridiculous!

---Dan



From owner-idn@ops.ietf.org  Tue May 29 01:10:24 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA12191
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 01:10:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154bYa-000DPe-00
	for idn-data@psg.com; Mon, 28 May 2001 21:56:36 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 154bYZ-000DPY-00
	for idn@ops.ietf.org; Mon, 28 May 2001 21:56:35 -0700
Received: (qmail 26605 invoked by uid 1001); 29 May 2001 04:56:56 -0000
Date: 29 May 2001 04:56:56 -0000
Message-ID: <20010529045656.23237.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
References: <083c01c0e6f7$235b7200$7dcb15a5@jamessonyvaio> <20010527220531.E17337@arwen.cs.berkeley.edu> <F599No5I9BADCDLTyHU0000f121@hotmail.com> <7544575.990957280@localhost> <20010527165903.5833.qmail@cr.yp.to> <079c01c0e6e4$3bf7ee50$7dcb15a5@jamessonyvaio> <20010527202613.5518.qmail@cr.yp.to> <083c01c0e6f7$235b7200$7dcb15a5@jamessonyvaio> <20010528043639.9273.qmail@cr.yp.to> <20010529033041.B22313@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

Apparently Adam has lost track of this thread.

The question was why, in http://cr.yp.to/proto/idn.html, I listed
gethostbyname() as something to be upgraded as part of the ACE solution.
This has nothing to do with the UTF-8 solution!

The answer is that ACE conversion has to happen somewhere between the
user's command lines and the DNS packets. Changing the gethostbyname()
code is easier than changing every program that uses gethostbyname().

---Dan



From owner-idn@ops.ietf.org  Tue May 29 01:24:11 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA13015
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 01:24:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154biP-000DW6-00
	for idn-data@psg.com; Mon, 28 May 2001 22:06:45 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154biO-000DW0-00
	for idn@ops.ietf.org; Mon, 28 May 2001 22:06: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 BAA13380;
        Tue, 29 May 2001 01:06:35 -0400 (EDT)
Message-Id: <200105290506.BAA13380@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: C C Magnus Gustavsson <mag@lysator.liu.se>
cc: Keith Moore <moore@cs.utk.edu>, "Adam M. Costello" <amc@cs.berkeley.edu>,
        idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE 
In-reply-to: Your message of "Tue, 29 May 2001 00:53:33 +0200."
             <Pine.GSO.4.00.10105290049450.9614-100000@sandra.lysator.liu.se> 
Date: Tue, 29 May 2001 01:06:34 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> 
> Let's say John Luser sends the following mail to you (where <oe> is o
> with umlaut).
> 
>   From: John Luser <luser@f<oe>reningen.org>
>   To: Keith Moore <moore@cs.utk.edu>
>   Subject: Hello
>   Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>   Content-Transfer-Encoding: 8BIT
>   
>   Hello Keith,
>   
>   Why don't you take a look at our new website on f<oe>reningen.org?
>   
>   Have a nice day!
>   
>   John
> 
> 
> Now, let's say your local system knows about ISO 8859-1 and is able to
> convert it to the internal encoding but unable to display <oe>. Thus
> it displays it as [] (square box - your systems default character).
> 
> 
> With mr Costellos suggestion this would be displayed to you as:
> 
>   From: John Luser <luser@px--sdn3fnfuwy4rn5wutn.org>
>   To: Keith Moore <moore@cs.utk.edu>
>   Subject: Hello
>   
>   Hello Keith,
>   
>   Why don't you take a look at our new website on f[]reningen.org?
>   
>   Have a nice day!
>   
>   John
> 
> 
> (Or whatever the chosen ACE encoding turns it into.)
> 
> It's hard to recognize px--sdn3fnfuwy4rn5wutn.org as the same domain
> as f[]reningen.org. It's a lot uglier as well.

okay, I see your point.  I can see why a user might want either form -
the "ugly" format so that he/she could transcribe the ACE format, and
the "pretty" format so that it wouldn't be so distracting.  If I were
writing an MUA I'd probably display the pretty one by default but 
have an option to display the ugly form (just as MUAs have options to
display certain message headers that aren't displayed by default).

I don't think I'd want the protocol standards to dictate how 
non-presentable characters are displayed, except perhaps to say 
that they shouldn't mislead the recipient.  (i.e don't display
o with umlaut as o or oe and make the recipient think that it's
a different address than it really is.)

> ACE is always a worse and an uglier thing to display when a system
> encounters unknown characters. Thus it's hardly an argument for using
> ACE. I can't agree that displaying the domain in the header as ACE,
> i e as "px--f+xg-reningen.org", "px--sdn3fnfuwy4rn5wutn.org" or
> whatever, is "no uglier than anything else they might display".

nor can I.  and the experience with RFC 2047 encodings would also 
seem to support your argument (and those were designed to be at least
somewhat readable for supersets of ASCII).  people found display of
2047 encodings annoying even when they could manage to read them.
to a lesser extent this was also true of quoted-printable in message 
bodies.
 
> Do you understand what I'm saying now?

I think so (though perhaps I should not be so presumptious as to
claim that I do for sure?)  thanks for the clarification.
 
> > I am not sure that we will find that Holy Grail anytime soon.
> > Even if we adopt UTF-8 we will still have to deal with various ways
> > of encoding "rich" text.
> 
> True, but we have to start somewhere. Every journey begins with a
> single step. (Although, this journey started with BCP 18. This is just
> a very large and important step on the way.)

True.  But  (as long as we are being philosophical) just because you start 
on a journey does not mean you know where it will take you, or how you 
will get there. :)


> > But this is all beside the point.  The IDN WG cannot legislate the 
> > encodings that are used by other applications; and it cannot legislate
> > that existing applications change their behavior.  It can only recommend
> > how to solve the I18N problem for domain names.  If the solution that
> > IDN recommends doesn't work well for some applications, it will not get
> > adopted for those applications - even if the recommended solution gets
> > approved as a standard.
> > 
> > It's very important to be realistic about what can be acheived.
> 
> Sure, but it is hardly a reason or excuse for this WG to suggest a bad
> solution. And I fail to see what it has to do with displaying domains
> as ACE when the application encounters unknown characters.

I think that ACE is necessary for other reasons, but I agree that this 
particular argument does not lend much support to ACE.

Keith



From owner-idn@ops.ietf.org  Tue May 29 01:37:21 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA13799
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 01:37:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154byV-000Dbb-00
	for idn-data@psg.com; Mon, 28 May 2001 22:23:23 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154byU-000DbU-00
	for idn@ops.ietf.org; Mon, 28 May 2001 22:23:22 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 154byU-0006RY-00; Mon, 28 May 2001 22:23:22 -0700
Date: Tue, 29 May 2001 05:23:22 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
Message-ID: <20010529052322.E22313@arwen.cs.berkeley.edu>
References: <20010527220531.E17337@arwen.cs.berkeley.edu> <F599No5I9BADCDLTyHU0000f121@hotmail.com> <7544575.990957280@localhost> <20010527165903.5833.qmail@cr.yp.to> <079c01c0e6e4$3bf7ee50$7dcb15a5@jamessonyvaio> <20010527202613.5518.qmail@cr.yp.to> <083c01c0e6f7$235b7200$7dcb15a5@jamessonyvaio> <20010528043639.9273.qmail@cr.yp.to> <20010529033041.B22313@arwen.cs.berkeley.edu> <20010529045656.23237.qmail@cr.yp.to>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <20010529045656.23237.qmail@cr.yp.to>; from djb@cr.yp.to on Tue, May 29, 2001 at 04:56:56AM -0000
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

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

> The question was why, in http://cr.yp.to/proto/idn.html, I listed
> gethostbyname() as something to be upgraded as part of the ACE solution.

I don't think it was me who asked that question.

> The answer is that ACE conversion has to happen somewhere between the
> user's command lines and the DNS packets. Changing the gethostbyname()
> code is easier than changing every program that uses gethostbyname().

I am willing to entertain the notion that changing gethostbyname() may
be a good idea.  It has been argued that existing programs do not expect
to get non-ASCII text back from gethostbyname(), and I buy that argument
to some extent:  If a program passes an ASCII name to gethostbyname(),
then gethostbyname() should not return any non-ASCII text (not even
if the ASCII name turns out to be an alias for an IDN), unless the
program has somehow explicitly invited non-ASCII text.  But if a program
passes non-ASCII text to gethostbyname(), and is surprised to get
non-ASCII text back, it's arguably the program's fault.  Perhaps passing
non-ASCII text to gethostbyname() should be considered permission for
gethostbyname() to return non-ASCII text.

If gethostbyname() receives 8-bit text, should it assume that it's
UTF-8, or should it assume that it's in the encoding of the current
locale?  My gut feeling is the latter.  And of course gethostbyname()
should use the same encoding for both the argument and the return value.

AMC



From owner-idn@ops.ietf.org  Tue May 29 01:56:56 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA14885
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 01:56:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154c8m-000DhO-00
	for idn-data@psg.com; Mon, 28 May 2001 22:34:00 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154c8l-000DhH-00
	for idn@ops.ietf.org; Mon, 28 May 2001 22:33:59 -0700
Received: from [192.168.1.40] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id HAA14060;
	Tue, 29 May 2001 07:33:10 +0200 (MET DST)
Date: Tue, 29 May 2001 07:31:14 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: Keith Moore <moore@cs.utk.edu>, C C Magnus Gustavsson <mag@lysator.liu.se>
cc: Keith Moore <moore@cs.utk.edu>, "Adam M. Costello" <amc@cs.berkeley.edu>,
        idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE 
Message-ID: <2858724.991121474@localhost>
In-Reply-To: <200105290506.BAA13380@astro.cs.utk.edu>
References:  <200105290506.BAA13380@astro.cs.utk.edu>
X-Mailer: Mulberry/2.1.0a6 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-05-29 01.06 -0400 Keith Moore <moore@cs.utk.edu> wrote:

> I think that ACE is necessary for other reasons, but I agree that this 
> particular argument does not lend much support to ACE.

You will get exactly the same kind of problem as soon as you have a charset
parameter for a MIME bodypart which have a different value than the
charset/encoding we will use for a domainname.

Reason for this is that the transformation in the header:

<sender local script> -> <whatever the IDN group selects> -> <receiver
local script>

and the transformation in the body:

<sender local script> -> <whatever the email client selects as charset> ->
<receiver local script>

most certainly will produce different results in receiver local script
regardless of what the IDN group selects.

This especially in clients where the client is not "IDN aware".


And, this regardless of whether UTF-8 or ACE encoding will be selected (or
anything else).


I think John has already pointed this out a number of times...

    paf




From owner-idn@ops.ietf.org  Tue May 29 02:08:04 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA22804
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 02:08:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154cNL-000DnT-00
	for idn-data@psg.com; Mon, 28 May 2001 22:49:03 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154cNK-000DnM-00
	for idn@ops.ietf.org; Mon, 28 May 2001 22:49:02 -0700
Received: from [192.168.1.40] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id HAA15713;
	Tue, 29 May 2001 07:48:22 +0200 (MET DST)
Date: Tue, 29 May 2001 07:47:34 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
Message-ID: <2917497.991122454@localhost>
In-Reply-To: <20010529052322.E22313@arwen.cs.berkeley.edu>
References: <20010527220531.E17337@arwen.cs.berkeley.edu>
 <F599No5I9BADCDLTyHU0000f121@hotmail.com> <7544575.990957280@localhost>
 <20010527165903.5833.qmail@cr.yp.to>
 <079c01c0e6e4$3bf7ee50$7dcb15a5@jamessonyvaio>
 <20010527202613.5518.qmail@cr.yp.to>
 <083c01c0e6f7$235b7200$7dcb15a5@jamessonyvaio>
 <20010528043639.9273.qmail@cr.yp.to>
 <20010529033041.B22313@arwen.cs.berkeley.edu>
 <20010529045656.23237.qmail@cr.yp.to>
 <20010529052322.E22313@arwen.cs.berkeley.edu>
X-Mailer: Mulberry/2.1.0a6 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-05-29 05.23 +0000 "Adam M. Costello" <amc@cs.berkeley.edu> wrote:

>> The answer is that ACE conversion has to happen somewhere between the
>> user's command lines and the DNS packets. Changing the gethostbyname()
>> code is easier than changing every program that uses gethostbyname().
> 
> If gethostbyname() receives 8-bit text, should it assume that it's
> UTF-8, or should it assume that it's in the encoding of the current
> locale?  My gut feeling is the latter.  And of course gethostbyname()
> should use the same encoding for both the argument and the return value.

I start feeling like a parrot...repeating myself over and over and over
again.

The problem is NOT the DNS protocol or gethostbyname() or such, the problem
are all the applications while using some application layer protocol, and
what charset they are going to use when passing around what they belive is
a domainname.

Not all operating systems and applications (far from the majority) use
Unicode of some encoding locally, so a conversion need always to happen.
All applications have to be changed.

   paf




From owner-idn@ops.ietf.org  Tue May 29 02:10:03 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA22922
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 02:10:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154cK9-000Dma-00
	for idn-data@psg.com; Mon, 28 May 2001 22:45:45 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154cK8-000DmU-00
	for idn@ops.ietf.org; Mon, 28 May 2001 22:45:44 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id BAA13806;
        Tue, 29 May 2001 01:45:42 -0400 (EDT)
Message-Id: <200105290545.BAA13806@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] Dots, and a path to working IDNs 
In-reply-to: Your message of "28 May 2001 21:18:11 -0000."
             <20010528211811.4490.qmail@cr.yp.to> 
Date: Tue, 29 May 2001 01:45:41 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > Incidently for those who cares, on a Chinese/Japanese IME, a dot can
> > either be U+3002 or U+002E depending if it is full/half width and in
> > Korean IME, a dot can either be U+FF9E or U+002E.
> 
> This is part of what I was referring to. Why aren't Keith and Patrik
> screaming that we need dotprep in thousands of programs? Don't they care
> about millions of confused users who have typed the wrong dot?

My guess is that this can be done in nameprep.  Perhaps it's not defined
in the current version of nameprep, but this could be fixed.  I'm not
screaming about this partially because I see us as currently arguing about 
more fundamental architectural issues, and because I have confidence 
that we will be willing to address this issue once we agree on how to
proceed at an architectural level.

That is, I don't expect that every detail of the protocol needs to be
worked out before we settle on an architecture.  

> Reports from Japan suggest that, in fact, keyboard interfaces already
> have adequate support for typing domain names. Users type the good dot,
> the canonical dot, the ASCII dot. A domain name with a bad dot simply
> doesn't work; the user fixes it.

As far as I'm concerned that's a perfectly reasonable solution if it works.
But there are some caveats.  For instance, it is one thing if typing the 
"bad" dots causes the lookup to fail; quite another if typing the "bad" 
dots causes a lookup for a completely different domain; and still another 
if the "bad" dots work differently in different clients.

If we don't specify how the "bad" dots are handled as part of the IDN 
protocol, we are essentially defering this to the registries.  Given their 
history and the competitive environment in which they exist, it's not clear 
whether they will strive to minimize bad effects.   At the same time, some 
of this will be left to the registies no matter what - we clearly cannot 
fix all potential IDN ambiguities in the protocol.

> Maybe users will keep trying to put bad dots into domain names for some
> reason. Maybe we _do_ want to put dotprep into thousands of programs.
> Okay; we'll do that if and when the need for it is clear. 

I think the question (for this and many other issues) is - to what extent 
we can risk requiring hosts or applications or servers to be upgraded 
when we discover some failure in our design?  The flip side of this 
question is - to what extent we can get this right the first time, and 
how long should we delay the standard trying to get it right?  I think that 
nameprep goes a long way toward solving the problem, and that it's a
useful approach, but it's not quite there yet.

> However, in
> the meantime, we can still use dots!
> 
> We can handle UTF-8 IDNs the same way:
> 
>    * People will register good UTF-8 IDNs. Lowercase, ASCII dots, no
>      confusing characters. We can distribute name-checking software so
>      that DNS administrators can make sure their IDNs are good.

if we can precisely define what is "good" beforehand (well enough to 
write the name-checking software), couldn't we just as easily define 
nameprep in such a way that it would either convert "bad" names to 
"good" names (for obvious translations) or reject "bad" names that
couldn't be reliably translated to good ones?

>    * It's the responsibility of the keyboard interface to help users
>      type good IDNs. Bad IDNs simply won't work.

quite honestly, I don't think that this will fly.  it strikes me as far
more difficult to get platforms to create a special input mode for
IDNs, and to get applications to use that input mode, than it does to
get applications to accept IDNs using a normal text interface.
it's especially difficult to retro-fit existing applications to use
new input modes.  and as somebody pointed out, we will also need to 
check names that originate from other sources besides the keyboard.

We could quite reasonably define a name-check API routine that would 
return good/bad for a given domain name, and that would be far easier 
than defining a new input mode.  But this could also just be
done by the nameprep routine.

>    * Maybe users will keep putting bad characters into domain names for
>      some reason. Maybe we really _do_ want slow nameprep, with
>      thousands of programs converting bad IDNs to good IDNs. Okay; we'll
>      do that if and when the need for it is clear. However, in the
>      meantime, we can still use IDNs!

this is going to be a massive upgrade.  we would like to avoid having
millions of programs upgraded only to find out that their IDN support is 
buggy and that (for instance) people can't reliably use certain IDNs 
with certain clients, and that there will be yet another massive upgrade
required to fix this.   good design is generally cheaper than good maintenance.

> This way we get useful IDNs as soon as possible. We take advantage of
> all the existing UTF-8 support. If it turns out that the user interface
> isn't good enough, that we need to suffer the massive costs of upgrading
> and redeploying thousands of programs, then we'll do that. The existing
> IDNs will continue to work.

we already know of instances where the UTF-8 support isn't good enough.
surely you would not have us ignore what we've learned from experience 
with these prototypes?

> There are two obstacles to having these IDNs work instantaneously. One
> is that many versions of gethostbyname() reject 8-bit characters. The
> other is that sendmail destroys bytes 128-159 (which don't show up in
> lowercase European characters in UTF-8, but which do show up in other
> characters). Both of these problems should be fixed as soon as possible.

I strongly disagree with this analysis, and it seems that many others do 
also.  But we've been through this argument before, and I don't see the 
point of rehashing it.

Keith



From owner-idn@ops.ietf.org  Tue May 29 02:12:08 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA23079
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 02:12:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154cYl-000Ds2-00
	for idn-data@psg.com; Mon, 28 May 2001 23:00:51 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154cYk-000Drw-00
	for idn@ops.ietf.org; Mon, 28 May 2001 23:00:50 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id CAA13979;
        Tue, 29 May 2001 02:00:48 -0400 (EDT)
Message-Id: <200105290600.CAA13979@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Mark.Andrews@nominum.com
cc: idn@ops.ietf.org
Subject: Re: [idn] Extending gethostbyname() 
In-reply-to: Your message of "Tue, 29 May 2001 11:05:43 +1000."
             <200105290105.f4T15hv66344@drugs.dv.isc.org> 
Date: Tue, 29 May 2001 02:00:48 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

In fact, when gethostbyname() was extended to use DNS (and YP, later NIS)
rather than simply looking up names in /etc/hosts, it broke numerous applications.
This happened because gethostbyname() had no way to return temporary failure 
(e.g. DNS server unreachable) as opposed to "this domain does not exist".
This caused a lot of bounced mail.

More generally, experience suggests that any time you change a programming
interface in an incompatible way then you need to make that change explicit,
rather than to change the behavior that existing applications expect.

Perhaps for some programs the change really will be as trivial as 
s/gethostbyname/gethostbyidn/ or whatnot.  But I doubt this will be true 
in general.  For instance, given that UNIX systems deployed today use a wide 
variety of locales and character sets, if I were updating a UNIX program that 
was in widespread use I wouldn't want that program to assume that its output 
device displays UTF-8.   Even if UNIX vendors are now supporting UTF-8,
not everyone will upgrade their systems immediately, and some will continue
to use old locales.  So I'd probably want a separate routine to convert 
an IDN from internal format to the format required by the display.
It might be a NOOP for the case when the display supported UTF-8, but it
would be needed in other cases.

Keith



From owner-idn@ops.ietf.org  Tue May 29 02:30:48 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA24213
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 02:30:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154chP-000DxF-00
	for idn-data@psg.com; Mon, 28 May 2001 23:09:47 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154chO-000Dx8-00
	for idn@ops.ietf.org; Mon, 28 May 2001 23:09:46 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id CAA14075;
        Tue, 29 May 2001 02:09:44 -0400 (EDT)
Message-Id: <200105290609.CAA14075@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] UTF-8 as the long-term IDN solution 
In-reply-to: Your message of "29 May 2001 04:25:57 -0000."
             <20010529042557.13041.qmail@cr.yp.to> 
Date: Tue, 29 May 2001 02:09:44 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> I suspect that we have consensus that the long-term IDN solution will
> encode Unicode characters as UTF-8 on the wire. I request that the WG
> chairs run a poll to see whether we have consensus.

I doubt that we have consensus that this is "the" long-term solution,
i.e. that UTF-8 will completely replace ACE in finite time.
(If/when it does happen, I expect it will happen because DNS itself 
is replaced...but I don't think we are even close to ready to touch that)

I suspect we are closer to consensus that we can have a way to 
use UTF-8 on the wire in DNS queries and responses.  Though I cannot 
justify it on a purely technical basis due to transition issues (it's 
hard to imagine the circumstances where a UTF-8 query will be more 
reliable than, and as fast as, an ACE query), to me it would be worth 
it to agree to define a UTF-8 query option if it allows us to move forward.

Keith



From owner-idn@ops.ietf.org  Tue May 29 02:30:57 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA24231
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 02:30:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154cdS-000Due-00
	for idn-data@psg.com; Mon, 28 May 2001 23:05:42 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154cdR-000DuW-00
	for idn@ops.ietf.org; Mon, 28 May 2001 23:05:42 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 87370FFC05; Tue, 29 May 2001 14:08:15 +0800 (SGT)
Message-ID: <005801c0e805$4e1d08a0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
References: <Pine.GSO.4.00.10105281945410.5818-100000@sandra.lysator.liu.se> <20010528191702.1600.qmail@cr.yp.to> <p0510030eb7389ab8633e@[165.227.249.18]> <20010529042557.13041.qmail@cr.yp.to>
Subject: Re: [idn] UTF-8 as the long-term IDN solution
Date: Tue, 29 May 2001 14:05:04 +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.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I would like to hear some support on this before we run this poll.

-James Seng

----- Original Message -----
From: "D. J. Bernstein" <djb@cr.yp.to>
To: <idn@ops.ietf.org>
Sent: Tuesday, May 29, 2001 12:25 PM
Subject: [idn] UTF-8 as the long-term IDN solution


> I suspect that we have consensus that the long-term IDN solution will
> encode Unicode characters as UTF-8 on the wire. I request that the WG
> chairs run a poll to see whether we have consensus.
>
> If we do, in fact, have consensus on this point, then we can stop
> wasting time considering ACE-now-and-forever. We can instead compare
> the actual possibilities: (1) ACE-now-UTF-8-later; (2) simply UTF-8.
>
> ---Dan
>
> P.S. I'm not going to bother responding to Hoffman's ad-hominem
attacks.
>




From owner-idn@ops.ietf.org  Tue May 29 02:42:52 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA25001
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 02:42:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154d0t-000E5c-00
	for idn-data@psg.com; Mon, 28 May 2001 23:29:55 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154d0s-000E5U-00
	for idn@ops.ietf.org; Mon, 28 May 2001 23:29:54 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id CAA14561;
        Tue, 29 May 2001 02:29:52 -0400 (EDT)
Message-Id: <200105290629.CAA14561@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] Extending gethostbyname() 
In-reply-to: Your message of "29 May 2001 04:47:34 -0000."
             <20010529044734.1803.qmail@cr.yp.to> 
Date: Tue, 29 May 2001 02:29:52 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Did the RFC 1123 authors worry about some badly written programs having
> trouble with names like 3com.com? 

perhaps.  but they did not specify that the APIs had to stay the same,
or for that matter, that they had to change.  rather they assumed that
API writers would do something reasonable.  

also, RFC 1123 didn't change the interpretation of the octets used
in a domain name. both before and after RFC 1123 those octets were 
understood to be from the printable subset of ASCII.  There was 
no question as to whether a program printing the name obtained from 
gethostbyaddr() before RFC 1123 would be able to print a name obtained
from that routine after a post-1123 upgrade, and the ambiguities 
that crop up when using ASCII (eg 0 vs O, l vs 1, - vs _) were 
reasonably well-understood.

These questions do crop up when considering whether to use native UTF-8 
in IDNs.

Also, the 'net was *much* smaller and in many ways less diverse when 
1123 was written. It was much easier to understand the likely impact of 
such changes, and there were fewer constituencies that had to be satisfied.

Keith



From owner-idn@ops.ietf.org  Tue May 29 02:48:55 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA25380
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 02:48:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154d2b-000E7D-00
	for idn-data@psg.com; Mon, 28 May 2001 23:31:41 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154d2Z-000E77-00
	for idn@ops.ietf.org; Mon, 28 May 2001 23:31:40 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 6A960FFC04; Tue, 29 May 2001 14:34:13 +0800 (SGT)
Message-ID: <008301c0e808$eea3f9c0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
References: <3B1180B6.8939BDC1@ehsco.com> <200105280227.WAA00791@astro.cs.utk.edu> <20010527213052.C17337@arwen.cs.berkeley.edu> <200105280200.WAA00572@astro.cs.utk.edu> <20010527202613.5518.qmail@cr.yp.to> <200105280114.VAA00203@astro.cs.utk.edu> <20010527165903.5833.qmail@cr.yp.to> <200105280106.VAA29976@astro.cs.utk.edu> <20010528050943.16457.qmail@cr.yp.to> <0a9c01c0e745$32399c90$7dcb15a5@jamessonyvaio> <20010528211811.4490.qmail@cr.yp.to>
Subject: Re: [idn] Dots, and a path to working IDNs
Date: Tue, 29 May 2001 14:31:02 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> This is part of what I was referring to. Why aren't Keith and Patrik
> screaming that we need dotprep in thousands of programs? Don't they
care
> about millions of confused users who have typed the wrong dot?

Actually this was brought up in the Nameprep design team.

> Reports from Japan suggest that, in fact, keyboard interfaces already
> have adequate support for typing domain names. Users type the good
dot,
> the canonical dot, the ASCII dot. A domain name with a bad dot simply
> doesn't work; the user fixes it.

I see what you mean now. Hmm..it is a thought: to leave the
normalization problem to the users and let them sort learn what is the
right thing to type.

However, I see some problems too. Normalization of diacritics. If my
keyboard only produce decomposed diacritics but the name is in compsed
diacritics, irregardless how much I try, I wont be able to get it in.

And also, I remember Sherin bought up yesterday on a topic of
userfriendiness and I am not sure if this fits it well.

>    * People will register good UTF-8 IDNs. Lowercase, ASCII dots, no
>      confusing characters. We can distribute name-checking software so
>      that DNS administrators can make sure their IDNs are good.

Agree. I think this should be done anyway, whether it is UTF-8, ACE or
whatever else we have (or decided). It is a good practice to do so.

>    * It's the responsibility of the keyboard interface to help users
>      type good IDNs. Bad IDNs simply won't work.

I don't agree with this or even think it is possible to be done.
Keyboard interface deals with generic input. IDN is only one specific
use for the keyboard. I don't think keyboard producer would have any
incentives to change what they doing for one specific IDN.

There are very likely good reasons someone wants to key in a full-width
dot (U+3002). Expecting the keyboard to produce only ASCII dot is not an
option. You see, that is how Chinese and Japanese write a full-stop ie a
hollow circle. Pick up a Chinese/Japanese book and take a look.

>    * Maybe users will keep putting bad characters into domain names
for
>      some reason. Maybe we really _do_ want slow nameprep, with
>      thousands of programs converting bad IDNs to good IDNs. Okay;
we'll
>      do that if and when the need for it is clear. However, in the
>      meantime, we can still use IDNs!

I am not sure I agree with the last statement. Experience has shown that
we can start using IDN in a just-send-utf8 method in some particular
setup with some particular software.

> This way we get useful IDNs as soon as possible. We take advantage of
> all the existing UTF-8 support. If it turns out that the user
interface
> isn't good enough, that we need to suffer the massive costs of
upgrading
> and redeploying thousands of programs, then we'll do that. The
existing
> IDNs will continue to work.

I could build upon this argument and suggest we all use GBK immediately.
In fact, GBK has better support than UTF-8 since it is mandated by the
Standard Burea. GBK is supported on all Chinese Windows and IE. Users
can already render/display and input GBK without problems and a lot of
applications already support GBK. If we were to use GBK on the wire now,
we can put GBK in the zone files, works with IE and Chinese users would
not have any problem input and using these GBK domain names.

I could go down this analogy in greater scary details...but lets stop
here for now.

What I am trying to say is this argument of 'immediate works' can have
devastating consequences if you are not careful. It is should not be an
argument for supporting some standard.

-James Seng




From owner-idn@ops.ietf.org  Tue May 29 02:49:12 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA25419
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 02:49:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154d6L-000E8n-00
	for idn-data@psg.com; Mon, 28 May 2001 23:35:33 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154d6K-000E8h-00
	for idn@ops.ietf.org; Mon, 28 May 2001 23:35:32 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id CAA14624;
        Tue, 29 May 2001 02:35:30 -0400 (EDT)
Message-Id: <200105290635.CAA14624@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Adam M. Costello" <amc@cs.berkeley.edu>
cc: idn@ops.ietf.org
Subject: Re: [idn] Moving forward 
In-reply-to: Your message of "Tue, 29 May 2001 04:49:21 -0000."
             <20010529044920.C22313@arwen.cs.berkeley.edu> 
Date: Tue, 29 May 2001 02:35:30 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Adam,

I think this framework would be a good basis for moving forward, perhaps
with one exception:

> Programs that send domain names to receivers known to handle UTF-8 names
> may perform ACE decoding on ACEs before sending, but are not required or
> even encouraged to do so.

I'm not sure this is a good idea for all applications - in particular,
I think it would be a bad idea for email.  Partially because email is more
reliable if MTAs don't do unnecessary transformations on messages, and
partially because in email there's really no way to know the capabilities
of the "ultimate" receiver (there may in fact be multiple receivers).

It might be that more precise wording of your statement would address
this concern, though offhand I cannot suggest text that would do so.

Keith



From owner-idn@ops.ietf.org  Tue May 29 03:23:59 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA27046
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 03:23:58 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154dKn-000EJL-00
	for idn-data@psg.com; Mon, 28 May 2001 23:50:29 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154dKn-000EJF-00
	for idn@ops.ietf.org; Mon, 28 May 2001 23:50:29 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 154dKl-0006Zg-00; Mon, 28 May 2001 23:50:27 -0700
Date: Tue, 29 May 2001 06:50:27 +0000
To: Patrik =?iso-8859-1?B?RuRsdHN0cvZt?= <paf@cisco.com>
Cc: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
Message-ID: <20010529065027.F22313@arwen.cs.berkeley.edu>
References: <7544575.990957280@localhost> <20010527165903.5833.qmail@cr.yp.to> <079c01c0e6e4$3bf7ee50$7dcb15a5@jamessonyvaio> <20010527202613.5518.qmail@cr.yp.to> <083c01c0e6f7$235b7200$7dcb15a5@jamessonyvaio> <20010528043639.9273.qmail@cr.yp.to> <20010529033041.B22313@arwen.cs.berkeley.edu> <20010529045656.23237.qmail@cr.yp.to> <20010529052322.E22313@arwen.cs.berkeley.edu> <2917497.991122454@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.3.17i
In-Reply-To: <2917497.991122454@localhost>; from paf@cisco.com on Tue, May 29, 2001 at 07:47:34AM +0200
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Patrik Fältström <paf@cisco.com> wrote:

> The problem is NOT the DNS protocol or gethostbyname() or such, the
> problem are all the applications while using some application layer
> protocol, and what charset they are going to use when passing around
> what they belive is a domainname.

Oh yes, I understand this.

> All applications have to be changed.

There are some small applications that never pass domain names around
except to/from the user and to/from DNS (like ping and netstat, and
telnet I think).  For these applications, changing gethostbyname() to
support the encoding of the current locale might be enough (if they are
already 8-bit clean).

But application-layer protocols do indeed need to define a common
representation of domain names and convert between that and the local
charset.

AMC



From owner-idn@ops.ietf.org  Tue May 29 03:24:24 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA27058
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 03:24:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154dSo-000EX5-00
	for idn-data@psg.com; Mon, 28 May 2001 23:58:46 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154dSl-000EWB-00
	for idn@ops.ietf.org; Mon, 28 May 2001 23:58:44 -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 f4T6wBI22874; Tue, 29 May 2001 08:58:11 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Tue, 29 May 2001 08:57:05 +0200 (MEST) (MET)
Message-Id: <200105290657.IAA04912@valinor.malmo.trab.se>
Date: Tue, 29 May 2001 08:57:05 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: [idn] UTF-8 as the long-term IDN solution
To: djb@cr.yp.to, idn@ops.ietf.org, James@Seng.cc
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: vkfwUezWCCe1Bkzk5izp5w==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-idn@ops.ietf.org
Precedence: bulk

>I would like to hear some support on this before we run this poll.
>
>-James Seng
>
>----- Original Message -----
>From: "D. J. Bernstein" <djb@cr.yp.to>
>To: <idn@ops.ietf.org>
>Sent: Tuesday, May 29, 2001 12:25 PM
>Subject: [idn] UTF-8 as the long-term IDN solution
>

>> If we do, in fact, have consensus on this point, then we can stop
>> wasting time considering ACE-now-and-forever. We can instead compare
>> the actual possibilities: (1) ACE-now-UTF-8-later; (2) simply UTF-8.
>>

This will be a mixture off comments to several letters. There are too
many to comment separately.

I have since the beginning wanted UCS as standard in DNS, and have seen
ACE as a needed backward compatibility. My drafts have been supporting
both at the same time.

Unless we go for "simpy UTF-8", we should go for "ACE and UTF-8 now".
This works, unless my UDNS draft is wrong, and can work with IDNA.

There is one big difference between ACE/IDNA and UTF-8:
ACE: to work as in IDNA the name must be nameprepped before encoded
     using ACE.
UTF-8:  need only be normalised. (though you could force it to be nameprepped
     to work in servers withou understanding how to compare UTF-8, but
     then all names will be forced into a specific form (like lower case)).
     As names are not nameprepped they can contain the name owners favorite
     form (for example using mixed case).
The above is one reason why I cannot accept to use IDNA as I want to be
able, just like in DNS today, to use names containg upper case letters.

As a software developer I have one major reason why I want UTF-8:
- I can spend time to add code to convert between ONE external character
encoding and my own local one. I do not have time to implement handling
of international characters if every protocol uses its own encoding.

If we use UTF-8 with ACE for backward compatibility, I could implement handling
of UTF-8 but ignore most handling of ACE names. This because having the ACE
name inside my UTF-8 text will do no harm (more than looking ugly) and will
work when pasted into other applications.

As many have pointed out, if UTF-8 is selected it cannot just go into
everybodys text, because locally many use something different than UTF-8.
But, as a software developer it is much easier to handle one standard
character encoding instead of many. Just think about:
In my e-mail I get a line:
To: text QUOTED-PRINTABLE-TEXT <USER-NAME-COMPATABLE-TEXT@ACE-NAME.ACE-NAME.com>

To handle this I must parse the line, identify each part that have their
own encoding, have an decode for each type and decode them.
If we used just UTF-8, to convert into local character set, you just
do if for the entire line without having to parse out each part and decode them
separately.

We must think outside just DNS, domain names will appear in many places
together with other elements. If each element have their own encoding
if will be very difficult to handle. It would be nicest if ACE could
be avoided all together, but I think we need it for backward compatibility.

   Dan




From owner-idn@ops.ietf.org  Tue May 29 03:46:31 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA27140
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 03:46:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154e16-000FbY-00
	for idn-data@psg.com; Tue, 29 May 2001 00:34:12 -0700
Received: from f150.law15.hotmail.com ([64.4.23.150] helo=hotmail.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154e15-000FbH-00
	for idn@ops.ietf.org; Tue, 29 May 2001 00:34:11 -0700
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 29 May 2001 00:33:41 -0700
Received: from 24.130.82.137 by lw15fd.law15.hotmail.msn.com with HTTP;	Tue, 29 May 2001 07:33:40 GMT
X-Originating-IP: [24.130.82.137]
From: "Sherin Alsoudani" <sherinalsoudani@hotmail.com>
To: James@Seng.cc, djb@cr.yp.to, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 as the long-term IDN solution
Date: Tue, 29 May 2001 00:33:40 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F150CRGryWtIIZS2TRq0000a873@hotmail.com>
X-OriginalArrivalTime: 29 May 2001 07:33:41.0047 (UTC) FILETIME=[AEC2E470:01C0E811]
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dear James,

I agree that the choice of ACE-forever is simply not a realistic option.  
Given that the largest use of the Internet is for the Web, and given that at 
least for Arabic there is basically only one de facto browser that supports 
that language, then it is necessary for Arabic speakers to ask "what 
encoding, if any, does that browser support?"  The answer is UTF-8, and I 
cannot speculate on when Microsoft would upgrade their browser to send 
RACE...

For this purely pragmatic reason, I would like to express support for 
getting consensus on the two choices expressed below.

Sherin

>From: "James Seng/Personal" <James@Seng.cc>
>To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
>Subject: Re: [idn] UTF-8 as the long-term IDN solution
>Date: Tue, 29 May 2001 14:05:04 +0800
>
>I would like to hear some support on this before we run this poll.
>
>-James Seng
>
>----- Original Message -----
>From: "D. J. Bernstein" <djb@cr.yp.to>
>To: <idn@ops.ietf.org>
>Sent: Tuesday, May 29, 2001 12:25 PM
>Subject: [idn] UTF-8 as the long-term IDN solution
>
>
> > I suspect that we have consensus that the long-term IDN solution will
> > encode Unicode characters as UTF-8 on the wire. I request that the WG
> > chairs run a poll to see whether we have consensus.
> >
> > If we do, in fact, have consensus on this point, then we can stop
> > wasting time considering ACE-now-and-forever. We can instead compare
> > the actual possibilities: (1) ACE-now-UTF-8-later; (2) simply UTF-8.
> >
> > ---Dan
> >
> > P.S. I'm not going to bother responding to Hoffman's ad-hominem
>attacks.
> >
>
>

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com




From owner-idn@ops.ietf.org  Tue May 29 03:50:55 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA27165
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 03:50:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154dzF-000FYZ-00
	for idn-data@psg.com; Tue, 29 May 2001 00:32:17 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154dzF-000FYT-00
	for idn@ops.ietf.org; Tue, 29 May 2001 00:32:17 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 154dzE-0006cD-00; Tue, 29 May 2001 00:32:16 -0700
Date: Tue, 29 May 2001 07:32:16 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Moving forward
Message-ID: <20010529073216.G22313@arwen.cs.berkeley.edu>
References: <20010529044920.C22313@arwen.cs.berkeley.edu> <200105290635.CAA14624@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <200105290635.CAA14624@astro.cs.utk.edu>; from moore@cs.utk.edu on Tue, May 29, 2001 at 02:35:30AM -0400
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Keith Moore <moore@cs.utk.edu> wrote:

> > Programs that send domain names to receivers known to handle UTF-8
> > names may perform ACE decoding on ACEs before sending, but are not
> > required or even encouraged to do so.
>
> I'm not sure this is a good idea for all applications - in particular,
> I think it would be a bad idea for email.  Partially because email
> is more reliable if MTAs don't do unnecessary transformations on
> messages, and partially because in email there's really no way to know
> the capabilities of the "ultimate" receiver (there may in fact be
> multiple receivers).

Yes, MTAs are already recommended not to alter messages, and that would
still apply.

> It might be that more precise wording of your statement would address
> this concern, though offhand I cannot suggest text that would do so.

I guess I should say that ACE decoding is permissible only when the
sender of a protocol message knows that all recipients of that message
(both direct and indirect) can handle it.  In the case of email headers,
I don't see how the sender could know that.  But in the case of SMTP
MAIL and RCPT commands, only the next-hop MTA receives those commands,
so ACE decoding would be safe there.  Probably pointless though.

The reason I included this option in the model was to allow for the
reduction of ACE-leakage.  Example scenario:  After IDN is standardized,
a new application protocol is defined that uses nameprep'd UTF-8.  Since
this application talks only to itself, it doesn't bother implementing
ACE decoding when displaying names to the user (it is recommended, but
not required, to decode ACE); it just handles conversion of UTF-8 to the
local charset.  That works fairly well until someone writes a gateway
between this application and some other protocol.  Now it might be nice
to put ACE decoding in the gateway, since the application doesn't do it
itself.  This is safe because the gateway knows that this application
handles UTF-8.

AMC



From owner-idn@ops.ietf.org  Tue May 29 03:51:56 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA27176
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 03:51:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154e2C-000FdJ-00
	for idn-data@psg.com; Tue, 29 May 2001 00:35:20 -0700
Received: from mail.fm-net.ne.jp ([211.15.66.133])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154e2B-000FdD-00
	for idn@ops.ietf.org; Tue, 29 May 2001 00:35:19 -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 QAA18260
	for <idn@ops.ietf.org>; Tue, 29 May 2001 16:35:17 +0900
Message-ID: <090701c0e811$b76b8960$a3420fd3@bruce>
From: "Bruce Thomson" <bthomson@fm-net.ne.jp>
To: <idn@ops.ietf.org>
References: <Pine.GSO.4.00.10105281945410.5818-100000@sandra.lysator.liu.se> <20010528191702.1600.qmail@cr.yp.to> <p0510030eb7389ab8633e@[165.227.249.18]> <20010529042557.13041.qmail@cr.yp.to> <005801c0e805$4e1d08a0$dd00a8c0@jamessonyvaio>
Subject: Re: [idn] UTF-8 as the long-term IDN solution
Date: Tue, 29 May 2001 16:33:55 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> > I suspect that we have consensus that the long-term IDN solution will
> > encode Unicode characters as UTF-8 on the wire. I request that the WG
> > chairs run a poll to see whether we have consensus.
> >
> > If we do, in fact, have consensus on this point, then we can stop
> > wasting time considering ACE-now-and-forever. We can instead compare
> > the actual possibilities: (1) ACE-now-UTF-8-later; (2) simply UTF-8.

> I would like to hear some support on this before we run this poll.
> 
> -James Seng
> 

It is likely that we have consensus on this point, and it would be well
worth the effort of a straw poll to establish this, so we can move on.

Bruce Thomson





From owner-idn@ops.ietf.org  Tue May 29 04:14:20 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA27263
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 04:14:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154eR2-000GIc-00
	for idn-data@psg.com; Tue, 29 May 2001 01:01:00 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154eR1-000GIW-00
	for idn@ops.ietf.org; Tue, 29 May 2001 01:01:00 -0700
Received: from dhcp-64-103-48-158.cisco.com (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id KAA09421
	for <idn@ops.ietf.org>; Tue, 29 May 2001 10:00:54 +0200 (MET DST)
Date: Tue, 29 May 2001 09:57:09 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: idn@ops.ietf.org
Subject: Re: [idn] Dots, and a path to working IDNs
Message-ID: <3233178.991130229@localhost>
In-Reply-To: <20010528211811.4490.qmail@cr.yp.to>
References: <3B1180B6.8939BDC1@ehsco.com>
 <200105280227.WAA00791@astro.cs.utk.edu>
 <20010527213052.C17337@arwen.cs.berkeley.edu>
 <200105280200.WAA00572@astro.cs.utk.edu>
 <20010527202613.5518.qmail@cr.yp.to>
 <200105280114.VAA00203@astro.cs.utk.edu>
 <20010527165903.5833.qmail@cr.yp.to>
 <200105280106.VAA29976@astro.cs.utk.edu>
 <20010528050943.16457.qmail@cr.yp.to>
 <0a9c01c0e745$32399c90$7dcb15a5@jamessonyvaio>
 <20010528211811.4490.qmail@cr.yp.to>
X-Mailer: Mulberry/2.1.0a6 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-05-28 21.18 +0000 "D. J. Bernstein" <djb@cr.yp.to> wrote:

> James Seng/Personal writes:
>> Incidently for those who cares, on a Chinese/Japanese IME, a dot can
>> either be U+3002 or U+002E depending if it is full/half width and in
>> Korean IME, a dot can either be U+FF9E or U+002E.
> 
> This is part of what I was referring to. Why aren't Keith and Patrik
> screaming that we need dotprep in thousands of programs? Don't they care
> about millions of confused users who have typed the wrong dot?

The issues with individual characters (especially the dot in Japanese and
Chinese input mechanisms) has been discussed extensively in the group which
have been talking about nameprep.

See the nameprep draft section 5.10.

  paf




From owner-idn@ops.ietf.org  Tue May 29 04:17:54 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA27296
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 04:17:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154eOz-000GEu-00
	for idn-data@psg.com; Tue, 29 May 2001 00:58:53 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154eOz-000GEo-00
	for idn@ops.ietf.org; Tue, 29 May 2001 00:58:53 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 154eOv-0006e3-00; Tue, 29 May 2001 00:58:49 -0700
Date: Tue, 29 May 2001 07:58:49 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 as the long-term IDN solution
Message-ID: <20010529075849.H22313@arwen.cs.berkeley.edu>
References: <200105290657.IAA04912@valinor.malmo.trab.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <200105290657.IAA04912@valinor.malmo.trab.se>; from Dan.Oscarsson@trab.se on Tue, May 29, 2001 at 08:57:05AM +0200
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

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

> ACE: to work as in IDNA the name must be nameprepped before encoded
>      using ACE.
> UTF-8:  need only be normalised.

Why even normalize it?  If you intend to require DNS servers to perform
Unicode case-folding in order to perform the lookup, then why not have
them perform normalization as well?

AMC



From owner-idn@ops.ietf.org  Tue May 29 05:25:03 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA27759
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 05:25:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154fYX-000I5r-00
	for idn-data@psg.com; Tue, 29 May 2001 02:12:49 -0700
Received: from [209.187.148.217] (helo=P2)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154fYW-000I5D-00; Tue, 29 May 2001 02:12:48 -0700
Date: Tue, 29 May 2001 05:12:31 -0400
From: John C Klensin <klensin@jck.com>
To: "James Seng/Personal" <James@Seng.cc>, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 as the long-term IDN solution
Message-ID: <3270673640.991113151@localhost>
In-Reply-To: <005801c0e805$4e1d08a0$dd00a8c0@jamessonyvaio>
X-Mailer: Mulberry/2.0.8 (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, 29 May, 2001 14:05 +0800 "James Seng/Personal"
<James@Seng.cc> wrote:

> I would like to hear some support on this before we run this
> poll.

The third alternative, which seemed to have some support in
Minneapolis and other places, is

ACE and/or UTF-8 now, some sort of search/directory system in
the long term.  We should not let that one get washed out in the
heat of the current discussions (see my tediously long note,
just posted).

    john






From owner-idn@ops.ietf.org  Tue May 29 05:25:11 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA27770
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 05:25:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154fVw-000I2H-00
	for idn-data@psg.com; Tue, 29 May 2001 02:10:08 -0700
Received: from [209.187.148.217] (helo=P2)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154fVv-000I1u-00
	for idn@ops.ietf.org; Tue, 29 May 2001 02:10:07 -0700
Date: Tue, 29 May 2001 05:09:50 -0400
From: John C Klensin <klensin@jck.com>
To: idn@ops.ietf.org
Subject: [idn] Stepping back and taking another look (long)
Message-ID: <3270512440.991112990@localhost>
X-Mailer: Mulberry/2.0.8 (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

IDN WG participants, 

Hi.  I have been struggling about whether to send this note,
or something like it, for several weeks now.  Some of you have
inferred parts of the content from remarks I have made
earlier; it may come as a surprise to others.  The request
from Marc and James for a consensus conclusion/ straw poll on
IDNA and ACE and its results precipitates the note: as
discussed in detail below, I do not agree that they are the
right way to go, but feel a need to offer an alternatives
view, however incomplete.   

It was also driven by the recent (and ongoing) "ACE versus
UTF-8" discussion: as the text (and the two I-Ds) I hope make
clear, I see the long-term solution to the real problem as
lying outside the DNS entirely, bringing a wider range of
coding options with it, and its being less important what, if
anything, we do to (in?) the DNS in the shorter term.  Hence I
also don't feel that the ACE versus UTF-8 discussion is very
important, although I believe that many of those issues
(although not necessarily the arguments) would be basically
the same for any approach we take, even the more extreme ones
suggested here.

I apologize in advance for the length of this note.  I've
attempted to throughly explain the issues as I see them,
rather than engage in the many short notes and back-and-forth
sniping we've seen about less complex topics before the WG.
Think of it as nearly an I-D that doesn't deserve even that
level of status, at least in this informal form.

One observation up front (to anticipate parts of section 3):
Section 3 argues that the existence of a short-term solution
that works much of the time for some fraction of the network
will block a long-term, more effective, soution from ever
deploying.  Despite what appears there, that argument cannot
be proven but is a matter of belief.  If one believes it, then
this document is an argument for radically reconsidering the
course IDN is on today and then heading off in another
direction.  If one does not, some of it, and much of another
document [LSearch] is a roadmap for where we (IETF and the
Internet community) should be going after we finish the
current work (and perhaps an argument that we should get
started on it even before the current work is finished).

Some of it, too, can be taken as an argument for an extremely
conservative approach to DNS changes (e.g., see [NEWCLASS] and
a forthcoming document which I understand David Lawrence is
working on and that should fill in many of the details my "new
class" one leaves out), rather than attempting to sneak new
functionality into the existing machinery.

Finally, the word "patent" doesn't appear below or in the new
drafts which it introduces.  If the approach I'm suggesting
permits getting around intellectual property rights claims, so
much the better.  But I don't think that should be (or needs
to be) a major motivation.

The terminology in this note is consistent with the
definitions in [DIRDEF].



1. Context of WG efforts and decision-making

Part of what has delayed these notes has been a debate, not
about technical content, but about the behavior of members of
the WG.  It saddens me that the IETF has reached the point
where decisions sometimes get made on that basis; but the
issues here seem important enough to take the risks.  So,
before I get to substance, I want to make an appeal to the WG:

Since its inception, the work of the IDN WG has been made more
complex by the presence and active (loud) participation of at
least two factions:

   (i) A small collection of parties with a strong financial
   investment in particular outcomes and more commitment to
   those outcomes than to finding a solution that works well
   for the Internet as a whole.  It has appeared from time to
   time that a subset of these parties would prefer to see the
   WG fail completely than to have it adopt a solution other
   than their own -- at least, that way, they would not be
   competing against an agreed-upon standard.

   (ii) A few individuals or groups who are taking what seems
   to be an "a simple approach works for me, and for people
   whose languages use the same code tables as mine (or ones I
   can predict), and therefore it is fine".  Sometimes these
   are "80% solution" arguments instead, but the impact is the
   same: some portion of the present or future Internet user
   population is being written off in the interest of a
   simplistic and straightforward solution.

There have been several arguments made that I should not send
this note because it will immediately play into the hands of
those two groups: they will "win" and the rest of the Internet
will "lose".  I have more confidence in the ability of the WG
membership to be able to filter out the noise (and the
impulses to get _some sort_ of solution, "right now") and
address the real issues carefully and thoughtfully.  I hope
I'm right.  If I'm not, I think we are all in serious trouble
(whether or not the substantive comments below are correct).


2. Layering of solutions

It has been suggested that introducing a "directory" or
"keywords" into, or above, the DNS could be used as a solution
to the problem.  Probing those statements often quickly
demonstrates that their advocates don't agree on exactly what
they mean.  Some aspects of the desired solutions are clear:
they permit matching that is at least somewhat imprecise, so
that, unlike the DNS, it becomes possible to expose
near-matches to users and let the human beings, rather than
overly-precise computer systems, make the decisions.  And many
of them are intended to permit a certain amount of
localization (and localization is very difficult, if not
impossible, to provide in the DNS without creating worse
problems).

The motivation for those approaches is discussed in a revised
version of the "DNS Role" document [DNSROLE] and a way of
integrating them is outlined in a new document [LSearch].
Informal discussions with the relevant ADs seems to indicate
that the technical strategy implied by those documents, and
the one discussed in [NEWCLASS], are not IDN work items.  But
the IDN WG should be aware of them because they may --I
believe should-- inform the IDN efforts.  See section 4.


3. Short-term as a blocking mechanism for long-term and
related issues

3.1 Internet applications history and its implications

Whether or not it is a good thing, there is one piece of
internet history that should be understood as IDN options are
considered.  Our history of replacing, rather than trying to
incrementally improve, applications that turn out to be
defective is just miserable.  Basically, we have almost never
done it successfully unless one or both of two conditions are
met:

 * The application being replaced is widely viewed as being
 incompetent or as having failed in very significant ways.

 * The new application is perceived as filling a vacuum or
 niche where no application (or even the perceived need for
 one) existed before.

Based upon this, there is strong reason to fear that the
deployment of a DNS-based solution that solves even a small
fraction of the perceived problems will prevent a non-DNS
solution, or a solution layered on top of the DNS, from ever
being developed and effectively deployed at least until that
solution is seen as failing in ways that cause serious
problems that cannot be ignored.  On the other hand, there is
reason to believe that some of the proposed (inside and
outside the WG) solutions that rely on local conventions or
that solve the wrong problem will fall into that "fail
significantly" criterion and that we will be able to apply a
broader and more targeted approach some years down the line.

But, if a solution based on a searching-capable system were to
be deployed eventually, some of the DNS modification options
now being considered would become obsolete, facing us with the
problem of determining whether to remove them (and improve
efficiency at the cost of backward compatibility) or leave
them there and incur the inefficiencies and complexities
forever (see 4.2 below).

3.2 "A directory is only a few years away".

In fairness, our history with variants on the proposed
solution may be as bad as that outlined above for applications
replacement.  We have been hearing that good, directory-based
solutions to one problem or another, including comprehensive
"white pages" services, are nearly here and should take over
the DNS problems in "a couple of years", for a very long time
now.  Arguably, the problem has been a combination of
bickering over small details (and too many options to bicker
over) and insufficient real demand, but it may be more
fundamental.  I believe that a good-quality, worldwide,
multilingual naming solution is important enough to create the
needed demand (especially when combined with some of the other
issues discussed in the "DNS role" document), but I know
opinions differ on that subject.

3.3 The sense of time pressure

One of the things that is driving many people in the WG is the
feeling that there are enough commercial, and often local,
solutions being developed that, if the IETF does not produce a
solution quickly, we will become irrelevant and people will
just go their own ways.  They may be right.  On the other
hand, we may have already lost that war: it is arguably
already too late for "quickly".  And producing a solution that
does not really fix the problem, especially a late one, does
not really help us --or the IETF's credibility in this area--
either.  All of this makes the "real" definition of the
problem --something I said a few words about in Minneapolis--
very important.

3.4 The real problem

One of the often-hidden debates in the WG about what problem
we are trying to solve.  I think there are at least three
versions of the answer:

* "Just get non-ASCII names into the DNS; let the users
  figure out what matches and adopt adequate conventions".  If
  this is the problem, then nameprep is probably unnecessary,
  or can be lightened considerably.

* "Just get non-ASCII names into the DNS, but make sure that
  identifiers that users will think match given that they know
  the relevant script, etc., do match".  If this is the
  problem, then we need nameprep, and we can (and I think
  must) continue to argue about whether it is good enough.

* "People are really looking for support for names in natural
  languages, not just identifiers".  The law of least
  astonishment applies and we must keep our expectations of
  the degree to which cultures and assumptions will change to
  meet the Internet's needs quite moderate.  Mechanisms for
  dealing with ambiguity are necessary (probably even within
  the nameprep framework, e.g., to deal with look-alike
  characters).  And DNS-based solutions are probably,
  inevitably, inadequate. 

And those issues are, of course, independent of the ACE versus
other things debate, the DNS class issues, etc.



4. Where we should go next

4.1 The question facing the IDN WG is what to do next.  I believe
that there is a case to be made (and I hope I'm making it) for
more or less declaring success and stopping.   That would
involve

 (i) Finishing and publishing the "requirements" and
    "nameprep" documents, the latter as a guide to
    canonicalization and matching in the context of Unicode/
    10646 strings.  IMO, the "nameprep" group should, however,
	take a careful look at ISO/IEC 14651 to see if it provides
	a useful alternate or supplemental model.

    It would also be extremely useful to review the code
	points impacted by nameprep to permit moving away from a
	binary model and toward a "clearly map", "clearly do not
	map", and "ambiguous" (or "sometimes") one.  That third
	category could help focus our thinking and, to the extent
	that we move toward a search-based model, would identify
	important areas for interactive user choice or the
	requirement for additional semantics or heuristics.

 (ii) Evaluating and selecting among the various ACE-based 
    encoding techniques and then publishing the results.  Even
    though I do not believe these should be deployed as
    changes in how the DNS itself is populated and used, the
    techniques are almost certain to be useful in other
    contexts.

And then handing either the "DNS searching" problem or the
"new DNS class" one, or both, over to other working groups.


4.2 If we can deploy this type of multilevel base, should we
still change the DNS?

If a search-based model is adopted, most of the multilingual
"action" would occur above the DNS layer.  Technically, there
would be no requirement that any changes (actual or
conceptual) at all be made to the DNS or its applications
interfaces, i.e., we could go back to treating DNS labels as
protocol elements with rather restrictive, applications-
driven, format and content rules.

On the other hand, the marketing events and pressures of the
last year may argue for making DNS changes to accomodate at
least some non-ASCII strings, if only to provide mneumonic
identifiers for languages not utilizing Roman-based alphabets.
Of course, this runs some risk of increased complexity and
unanticipated damage (at least unless a "new class" solution
is adopted), but the tradeoff is worth considering.

As we consider it, it is also worth remembering that the most
important function of the DNS is tied to long-term stable
identifiers.  We just don't have any other satisfactory way to
do them and they are very important.  Things that put that use
at risk should, arguably, be dealt with in other ways.

4.4 Deployment against DNS base

As with the "new class" approach to DNS changes [NEWCLASS], the
approach outlined here does not require any changes to the
existing installed DNS base.  But, like all solutions to the
multilingual name issues, it requires changes to all relevant
applications.  The notion of moving from lookup to searching
does imply that we will need, not merely to change the code
that calls the name resolution system, but to rethink the UIs
of those applications.


References

(I-D names and numbers current or submitted at the time of
this writing.)

[DIRDEF] Alvestrand, Harald. "Definitions for talking about
directories", work in progress,
draft-alvestrand-directory-defs-02.txt

[DNSROLE] Klensin, John. "Role of the Domain Name System",
work in progress, draft-klensin-dns-role-01.txt

[LSearch] Klensin, John.  "A Search-based access model for the
DNS", work in progress, draft-klensin-dns-search-00.txt.

[NEWCLASS] Klensin, John, "Internationalizing the DNS -- A New
Class", work in progress, draft-klensin-i18n-newclass-00.txt




From owner-idn@ops.ietf.org  Tue May 29 06:37:41 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA28085
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 06:37:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154gcU-000Jr5-00
	for idn-data@psg.com; Tue, 29 May 2001 03:20:58 -0700
Received: from spider.nic-se.se ([212.247.3.67])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154gcU-000Jqy-00
	for idn@ops.ietf.org; Tue, 29 May 2001 03:20:58 -0700
Received: from localhost (dufberg@localhost)
	by spider.nic-se.se (8.11.1/8.11.1) with ESMTP id f4TADQ205161
	for <idn@ops.ietf.org>; Tue, 29 May 2001 12:13:26 +0200 (CEST)
X-Authentication-Warning: spider.nic-se.se: dufberg owned process doing -bs
Date: Tue, 29 May 2001 12:13:26 +0200 (CEST)
From: Mats Dufberg <dufberg@nic-se.se>
To: <idn@ops.ietf.org>
Subject: Re: [idn] UTF-8 as the long-term IDN solution
In-Reply-To: <20010529042557.13041.qmail@cr.yp.to>
Message-ID: <Pine.BSF.4.30.0105291200340.29244-100000@spider.nic-se.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On 29 May 2001, D. J. Bernstein wrote:

> I suspect that we have consensus that the long-term IDN solution will
> encode Unicode characters as UTF-8 on the wire. I request that the WG
> chairs run a poll to see whether we have consensus.

Independent of IDN scheme it is important that the the solution is
considered as an upgrade of DNS, not a temporary hack, to have it
uniformly implemented.

If IDN is implemented as Nameprep+ACE I do not think that we will see
enough reason to replace ACE with UTF-8 on the wire in a foreseeable
future. Such a change would require that all DNS infrastructure is
upgraded. If UTF-8 is used, the ACE-to-UTF-8 and UTF-8-to-ACE conversions
can easily be handled in the interface to the DNS system.

Today we have three alternatives, as far as I can see:

1. UTF-8 without nameprep
2. UTF-8 with nameprep
3. ACE with nameprep


I do not consider "ACE now, UTF-8 later" an alternative.



Mats

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





From owner-idn@ops.ietf.org  Tue May 29 06:44:01 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA28145
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 06:44:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154gZi-000Jm2-00
	for idn-data@psg.com; Tue, 29 May 2001 03:18:06 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154gZh-000Jlu-00
	for idn@ops.ietf.org; Tue, 29 May 2001 03:18:05 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP id 615EAFFC06
	for <idn@ops.ietf.org>; Tue, 29 May 2001 18:20:39 +0800 (SGT)
Message-ID: <02d801c0e828$9041a150$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: <idn@ops.ietf.org>
References: <F86ip68V8zDv60gxapz0000f8ba@hotmail.com> <200105280239.WAA00909@astro.cs.utk.edu> <3B1180B6.8939BDC1@ehsco.com> <200105280227.WAA00791@astro.cs.utk.edu> <20010527213052.C17337@arwen.cs.berkeley.edu> <200105280200.WAA00572@astro.cs.utk.edu> <20010527202613.5518.qmail@cr.yp.to> <200105280114.VAA00203@astro.cs.utk.edu> <20010527165903.5833.qmail@cr.yp.to> <200105280106.VAA29976@astro.cs.utk.edu> <20010528050943.16457.qmail@cr.yp.to> <0a9c01c0e745$32399c90$7dcb15a5@jamessonyvaio>
Subject: Re: [idn] UTF-8 / RACE
Date: Tue, 29 May 2001 18:17:28 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

As I say I will try to give some comments on UTF-8 with fast nameprep
after I get an understanding of what you mean by that.
Costs of UTF-8 with fast nameprep
What it means. Domain names are encoded as UTF-8 strings in all of the
above contexts.
Bad names are not allowed to appear. (Exception: Users can send bad
names in DNS registration forms; the registrar will send back a
rejection notice showing the closest good name.)

JS: What is considered a "bad names"? From some of your note, you
suggested only lower-case characters allowed in DNS. Does this two match
"françious" vs "FRANÇIOUS"? (By your fast-nameprep definition, they wont
match unless the users key in exactly in the same way the administrator
puts it in).

Making it work. gethostbyname needs to be upgraded. Many current
installations, in violation of RFC 2181, reject DNS answers that contain
unusual characters. (However, some versions will work correctly with
options allow_special all or options no-check-names in
/etc/resolv.conf.)

JS: Agree with this altho it is probably a simplistic summary of the
pain.

mutt needs to be upgraded. UTF-8 needs to be spaced properly.

pine needs to be upgraded. UTF-8 needs to be spaced properly.

JS: Lets expand this to any non-UTF-8 applications which uses Domain
Names.

sendmail needs to be upgraded. Current versions are not 8-bit clean:
they discard bytes \200 through \237 in mail message headers, because
those bytes are used for other purposes inside sendmail's
string-handling routines. The relevant section of code is in collect.c:
...

JS: It is too early to suspect how I18N Email will look like to decide
what changes would be required in sendmail but I suspect making it 8-bit
clean as you suggested here is probably needed if UTF-8 are use in IDN.

There's one report that an obsolete version of the Netscape mailer
crashes under Solaris when it reads UTF-8 messages. I need verifiable
details.

JS: Lets go thru the list you made for IDNA and I see most of them would
need to be patch or made 8-bit clean to work (including bind).
Applications which does not support UTF-8 has to be upgraded to support
UTF-8.

But most important of all, you left out the needs to 'patch/replace' the
keyboard so that 'bad names' cannot be entered.

-James Seng

----- Original Message -----
From: "James Seng/Personal" <James@seng.cc>
To: "D. J. Bernstein" <djb@cr.yp.to>; <idn@ops.ietf.org>
Sent: Monday, May 28, 2001 3:09 PM
Subject: Re: [idn] UTF-8 / RACE


> Is this your defination for Fast Nameprep?
>
> If that is the case, are you suggesting we change the keyboard
interface
> to do "Nameprep" so there is no 'bad' dot? Please explain further how
> you proposed to interact with keyboard interface...
>
> Incidently for those who cares, on a Chinese/Japanese IME, a dot can
> either be U+3002 or U+002E depending if it is full/half width and in
> Korean IME, a dot can either be U+FF9E or U+002E.
>
> -James Seng
>
> > This is just like the current handling of dots. Yes, there are bad
> dots,
> > but the keyboard interface helps the user type domain names with the
> > ASCII dot, so applications don't have to worry about bad dots. Are
you
> > going to demand that we change and redeploy thousands of programs to
> > accept non-canonical dots in domain names?
> >
> > ---Dan
> >
>
>




From owner-idn@ops.ietf.org  Tue May 29 07:16:22 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA28398
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 07:16:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154hAe-000Kpk-00
	for idn-data@psg.com; Tue, 29 May 2001 03:56:16 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154hAd-000Kpe-00
	for idn@ops.ietf.org; Tue, 29 May 2001 03:56:15 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0AY64l30v0U3rbhSsPdL84UsvXiPLKifA==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id F6LRUVHX; Tue, 29 May 2001 06:55:45 EDT
To: Internet-Drafts@ietf.org
Cc: idn@ops.ietf.org
Date: Tue, 29 May 2001 04:09:23 -0700
Subject: [idn] draft-ietf-idn-step
Message-ID: <20010529.040927.-710641.0.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.5
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=--__JNP_000_4cbf.3257.21f0
X-Juno-Line-Breaks: 0-6,8,10-18,20,22,24-26,26-32767
X-Juno-Att: 1
X-Juno-RefParts: 0
From: liana.ydisg@juno.com
Sender: owner-idn@ops.ietf.org
Precedence: bulk

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

----__JNP_000_4cbf.3257.21f0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

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

	Title		: StepCode- A  User Access Oriented  IDN Encoding
	Author(s)	: Liana Ye
	Filename	: draft-ietf-idn-step-00.txt
	Pages		: 11
	Date		: 29-May-01
	
Development of Internationalized Domain Name (IDN) has been a heated
discussion over what to send down to the wire as international hostnames.
 
Shall we send UTF-8 in addition to current DNS or scatch DNS completely
and starts 
over some times down the line.   This proposal hope to answer the
question 
and make UTF-8 an unnecessary addition to hostnames.


----__JNP_000_4cbf.3257.21f0
Content-Type: text/plain; name="draft-ietf-idn-step.txt"
Content-Transfer-Encoding: base64

SW50ZXJuZXQgRHJhZnQgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgTGlhbmEg
WWUNCmRyYWZ0LWlldGYtaWRuLXN0ZXAtMDAudHh0ICAgICAgICAgICAgICAgICAgICAgICAgICBZ
JkQgSVNHDQpNYXkgMjksIDIwMDENCkV4cGlyZXMgaW4gc2l4IG1vbnRocyAoTm92ZW1iZXIgMjAw
MSkgICAgICAgICAgICAgICAgICAgICAgICAgDQoJCSAgIA0KCSBTdGVwQ29kZS0gQSBVc2VyIEFj
Y2VzcyBPcmllbnRlZCBJRE4gRW5jb2RpbmcNCgkJDQpTdGF0dXMgb2YgdGhpcyBtZW1vDQoNClRo
aXMgZG9jdW1lbnQgaXMgYW4gSW50ZXJuZXQtRHJhZnQgYW5kIGlzIGluIGZ1bGwgY29uZm9ybWFu
Y2Ugd2l0aA0KYWxsIHByb3Zpc2lvbnMgb2YgU2VjdGlvbiAxMCBvZiBSRkMyMDI2Lg0KDQpJbnRl
cm5ldC1EcmFmdHMgYXJlIHdvcmtpbmcgZG9jdW1lbnRzIG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVl
cmluZw0KVGFzayBGb3JjZSAoSUVURiksIGl0cyBhcmVhcywgYW5kIGl0cyB3b3JraW5nIGdyb3Vw
cy4gTm90ZSB0aGF0DQpvdGhlciBncm91cHMgbWF5IGFsc28gZGlzdHJpYnV0ZSB3b3JraW5nIGRv
Y3VtZW50cyBhcw0KSW50ZXJuZXQtRHJhZnRzLg0KDQpJbnRlcm5ldC1EcmFmdHMgYXJlIGRyYWZ0
IGRvY3VtZW50cyB2YWxpZCBmb3IgYSBtYXhpbXVtIG9mIHNpeA0KbW9udGhzIGFuZCBtYXkgYmUg
dXBkYXRlZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRlZCBieSBvdGhlciBkb2N1bWVudHMNCmF0IGFu
eSB0aW1lLiBJdCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMgcmVm
ZXJlbmNlDQptYXRlcmlhbCBvciB0byBjaXRlIHRoZW0gb3RoZXIgdGhhbiBhcyAid29yayBpbiBw
cm9ncmVzcy4iDQoNCiAgICAgVGhlIGxpc3Qgb2YgY3VycmVudCBJbnRlcm5ldC1EcmFmdHMgY2Fu
IGJlIGFjY2Vzc2VkIGF0DQogICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvaWV0Zi8xaWQtYWJzdHJh
Y3RzLnR4dA0KDQogICAgIFRoZSBsaXN0IG9mIEludGVybmV0LURyYWZ0IFNoYWRvdyBEaXJlY3Rv
cmllcyBjYW4gYmUgYWNjZXNzZWQNCgkgYXQgaHR0cDovL3d3dy5pZXRmLm9yZy9zaGFkb3cuaHRt
bC4NCg0KDQpBYnN0cmFjdA0KDQpUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBhIHRyYW5zZm9ybWF0
aW9uIG1ldGhvZCBmcm9tIGFuIGVuZCB1c2VyDQppbnRvIFVuaWNvZGUgbGlicmFyeSBmb3IgcmVw
cmVzZW50aW5nIENoaW5lc2UgY2hhcmFjdGVycyBpbiBob3N0IA0KbmFtZSBwYXJ0cyBpbiBhIGZh
c2hpb24gdGhhdCBpcyBleHRlbmRhYmxlIHRvIGluY2x1ZGUgbW9yZSB0aGFuIA0KVW5pY29kZSBz
eW1ib2xzIGFuZCBjb21wbGV0ZWx5IGNvbXBhdGlibGUgd2l0aCB0aGUgY3VycmVudCBETlMuIA0K
SXQgaXMgYSBwb3RlbnRpYWwgY2FuZGlkYXRlIGZvciBhbiBBU0NJSS1Db21wYXRpYmxlIEVuY29k
aW5nIChBQ0UpIA0KZm9yIGludGVybmF0aW9uYWxpemVkIGhvc3RuYW1lcy4gIFRoaXMgbWV0aG9k
IGlzIGJhc2VkDQpvbiB1c2VyIHdpZGVseSB1c2VkIGNvbmNlcHQgZm9yIGRlbm90aW5nIGEgQ2hp
bmVzZSBjaGFyYWN0ZXIgd2l0aCANCml0cyBwaG9uZXRpYyBlbGVtZW50cywgYW5kIHJlZ2lzdGVy
IHRoZWlyIElETiBuYW1lcyB3aXRoIHN1Y2ggYW4gDQpleHRlbnRlZCBwaG9uZXRpYyBkZXNjcmlw
dGlvbiAoRW5nbGlzaCBzcGVha2VycyBjYW4gcmVnaXN0ZXIgYSANCkNKSyBnbHlwaCBmb3IgdGhl
aXIgYmxlc3NpbmcgdG9vLiksIHNvIHRoYXQgYW4gSUROIG5hbWUgaW4gZWl0aGVyIA0KdHJhZGl0
aW9uYWwgb3Igc2ltcGxpZmllZCBjaGFyYWN0ZXIgc2V0IGNhbiBiZSBlZmZlY3RpdmUgd2l0aCAN
CmJvdGggdXNlciBjb21tdW5pdGllcyBkZXBlbmRpbmcgb24gc2VydmVycywgYW5kIGFsbG93cyBz
dGFuZGFyZCANCnZhcmlhdGlvbnMgZm9yIGNvbXByZXNzaW5nIGFuZCBzZWN1cml0eSBmaWx0ZXJp
bmcgb2YgdGhhdCANCmluZm9ybWF0aW9uLiBUaGUgbWV0aG9kIGNhbiBiZSBleHRlbnRlZCBmb3Ig
b3RoZXIgc2NyaXB0cyBhcyBsb25nIA0KYXMgdGhleSBuZWVkIG1vcmUgdGhlbiAyNiBiYXNpYyBB
U0NJSSBsZXR0ZXJzIHRvIGJlIG1hcHBlZC4gDQoNCg0KMS4gSW50cm9kdWN0aW9uDQoNCjEuMSBD
b250ZXh0DQoNClRoZXJlIGlzIGEgc3Ryb25nIHdvcmxkLXdpZGUgZGVzaXJlIHRvIHVzZSBjaGFy
YWN0ZXJzIG90aGVyIHRoYW4NCnBsYWluIEFTQ0lJIGluIGhvc3RuYW1lcy4gSG9zdG5hbWVzIGhh
dmUgYmVjb21lIHRoZSBlcXVpdmFsZW50IG9mDQpidXNpbmVzcyBvciBwcm9kdWN0IG5hbWVzIGZv
ciBtYW55IHNlcnZpY2VzIG9uIHRoZSBJbnRlcm5ldCwgc28NCnRoZXJlIGlzIGEgbmVlZCB0byBt
YWtlIHRoZW0gdXNhYmxlIGJ5IHBlb3BsZSB3aG9zZSBuYXRpdmUgc2NyaXB0cw0KYXJlIG5vdCBy
ZXByZXNlbnRhYmxlIGJ5IEFTQ0lJLiBUaGUgcmVxdWlyZW1lbnRzIGZvcg0KaW50ZXJuYXRpb25h
bGl6aW5nIGhvc3RuYW1lcyBhcmUgZGVzY3JpYmVkIGluIHRoZSBJRE4gV0cncw0KcmVxdWlyZW1l
bnRzIGRvY3VtZW50LCBbSUROUmVxXS4NCg0KVGhlIElETiBXRydzIGNvbXBhcmlzb24gZG9jdW1l
bnQgW0lETkNvbXBdIGRlc2NyaWJlcyB0aHJlZSBwb3RlbnRpYWwNCm1haW4gYXJjaGl0ZWN0dXJl
cyBmb3IgSUROOiBhcmNoLTEgKGp1c3Qgc2VuZCBiaW5hcnkpLCBhcmNoLTIgKHNlbmQNCmJpbmFy
eSBvciBBQ0UpLCBhbmQgYXJjaC0zIChqdXN0IHNlbmQgQUNFKS4gU3RlcENvZGUgaXMgYW4gQUNF
IHRoYXQgDQpjYW4gYmUgdXNlZCB3aXRoIHByb3RvY29scyB0aGF0IG1hdGNoIGFyY2gtMiBvciBh
cmNoLTMuIEhvcGVmdWxseSwgDQp0aGlzIEFDRSBtYXkgcmVuZGVyIGFyY2gtMiB1bm5lY2Vzc2Fy
eS4gSXQgaXMgZWl0aGVyIGEgc2VydmVyIG9yIGENCmNsaWVudCBnZW5lcmF0YWJsZSBhbmQgc2Vs
ZWN0YWJsZSBBQ0UgYWNjb3JkaW5nIHRvIGEgc3RyaW5nJ3MgDQpsYW5ndWFnZS9zY3JpcHQgdGFn
L2xhYmVsW1JGQzE3NjZdLiBCZWNhdXNlIGl0IGRvZXMgbm90IGF0dGVtcHQgYW55IA0KcGFydGlj
dWxhciBvcHRpbWl6YXRpb24gb3IgY29tcHJlc3Npb24gb2Ygc3RyaW5nIHBhdHRlcm5zLCB0aGUg
DQphdmVyYWdlIGxlbmd0aCBmb3IgYSBDaGluZXNlIGNoYXJhY3RlciBpbiBbSVNPMTA2NDZdIGlz
IGFib3V0IDEzIA0KY2hhcmFjdGVycyBsb25nLCBlbm91Z2ggdG8gY29kZSDQwtbxx+W7qi5jb20g
KEkgd2lzaCAyMCUgcmVhZGVyIA0KY2FuIHNlZSB0aGlzLCBhbmQgdGhlIHJlc3Qgc2hvdWxkIGJl
IGF0IGxvc3QuKSBhczogDQp4aW56aHVxaW5naHVhMTIxMnFpbjFqaW4wZ2UxZ2Uwc2h1aTFxaW5n
MGh1YTJzaGkwLmNvbSB3aXRoIDU0IG9jdGV0cy4NCkluIHRoZSBjb2RlIHRoZSBmaXJzdCBncm91
cCBvZiBkaWdpdHMgc3BlY2lmeSB0aGUgdG9uZXMgb2YgZWFjaCANCmdseXBoIGFzIHdlbGwgYXMg
dGhlIG51bWJlciBvZiBjb2RlcG9pbnRzIGluIFtJU08xMDY0Nl0gb3IgZ2x5cGhzLiANClRoZSBy
ZXN0IG9mIGRpZ2l0cyBzcGVjaWZ5IHRoZSBsYXlvdXQgb2YgZGlmZmVyZW50IHBhcnRzIG9mIGVh
Y2ggDQpnbHlwaCBvZiBhYm92ZSBzdHJpbmcuDQoNClRoZSBTdGVwQ29kZSBwcm90b2NvbCBoYXMg
dGhlIGZvbGxvd2luZyBmZWF0dXJlczoNCg0KLSBUaGVyZSBpcyBleGFjdGx5IG9uZSB3YXkgdG8g
Y29udmVydCBpbnRlcm5hdGlvbmFsaXplZCBob3N0IHBhcnRzDQp0byBhbmQgZnJvbSBTdGVwQ29k
ZSBzdHJpbmdzIHdpdGggYSBzY3JpcHQgdGFnL2xhYmVsLiBJdCBwZXJtaXRzDQpkaWZmZXJlbnQg
c2NyaXB0IHRhZ3MgdG8gYWNjZXNzIHRoZSBzYW1lIGdseXBoIGluIFtJU08xMDY0Nl0gDQpzaW1p
bGFyIHdpdGggYSBzZWFyY2hpbmcgbWV0aG9kIGludG8gYSBib29rIGxpYnJhcnksIHdoaWxlIHRo
ZSANCmNvZGVwb2ludHMgb2YgW0lTTzEwNjQ2XSBpcyBhbiBhbmFsb2d5IHRvIElTRE4gYm9vayBu
dW1iZXIuIEhvc3QgDQpuYW1lIHBhcnQgdW5pcXVlbmVzcyBpcyBwcmVzZXJ2ZWQuIElmIHRoZXJl
IGlzIGEgZGlmZmVyZW5jZSBpbiB0aGUgDQpjb2RlLCBpdCBpcyBjb25zaWRlcmVkIGFzIHVzZXIg
aW5wdXQgZXJyb3IuDQoNCi0gSG9zdCBwYXJ0cyBoYXZlIG5vIGludGVybmF0aW9uYWwgZ2x5cGhz
IGJ1dCBVUy1BU0NJSS4NCg0KLSBOYW1lcyB1c2luZyBTdGVwQ29kZSBoYXZlIGxlbmd0aHMgcHJv
cG9ydGlvbmF0ZSB0byB0aGUgbnVtYmVyDQpvZiBnbHlwaHMgKGZyb20gSVMgMTA2NDYpIGluIHRo
ZSBuYW1lcyB0aGVtc2VsdmVzIHBsdXMgdGhlDQpzY3JpcHQgdGFnLiAgSG93ZXZlciwgU3RlcENv
ZGUgZm9yIG1vc3QgZnJlcXVlbnRseSB1c2VkIGdseXBocw0KaW4gdGhlIHRhYmxlIGlzIHNob3J0
ZW5kIHNpZ25pZmljYW50bHkgc3VjaCBhcyBDeXJpbGxpYy4gDQoNCi0gVGhpcyBzcGVjaWZpY2F0
aW9uIGFsbG93cyBzdGFuZGFyZCBjb21wcmVzc2lvbiBvciBzZWN1cml0eSANCnRyZWF0bWVudCBj
b21wYXRpYmxlIHdpdGggZXhpc3RpbmcgaG9zdG5hbWVzLg0KDQpJdCBpcyBpbXBvcnRhbnQgdG8g
bm90ZSB0aGF0IHRoZSBmb2xsb3dpbmcgc2VjdGlvbnMgY29udGFpbiBtYW55DQpub3JtYXRpdmUg
c3RhdGVtZW50cyB3aXRoICJNVVNUIiBhbmQgIk1VU1QgTk9UIi4gQW55IGltcGxlbWVudGF0aW9u
DQp0aGF0IGRvZXMgbm90IGZvbGxvdyB0aGVzZSBzdGF0ZW1lbnRzIGV4YWN0bHkgaXMgbGlrZWx5
IHRvIGNhdXNlDQpkYW1hZ2UgdG8gdGhlIEludGVybmV0IGJ5IGNyZWF0aW5nIG5vbi11bmlxdWUg
cmVwcmVzZW50YXRpb25zIG9mDQpob3N0bmFtZXMuDQoNCjEuMiBBdXRob3IncyBEaXNjbGFpbWVy
DQoNClRoaXMgZG9jdW1lbnQgd2FzIHdyaXR0ZW4gZm9yIHRoZSBjb252ZW5pZW5jZSBvZiB0aGUg
SUROIFdHLCBpbiANCmNhc2Ugc29tZW9uZSBiZWxpZXZlcyB0aGF0IHRoZXJlIGFyZSBubyBhZ3Jl
ZWFibGUgbWVjaGFuaXNtcyBmb3IgDQpyZWZlcmVuY2luZyBpbnRlcm5hdGlvbmFsaXplZCBuYW1l
cyB3aXRob3V0IGNvbnZlcnRpbmcgW0lTTzEwNjQ2XQ0KY29kZXBvaW50cy4gVGhlIGF1dGhvciBi
ZWxpZXZlcyB0aGF0IFtJU08xMDY0Nl0gaXMgdG8NCmVzdGFibGlzaCBhIHN5bWJvbCBsaWJhcmF5
LCBhbmQgdGhlcmUgYXJlIGJldHRlciB3YXlzIHRvIGRvIGhpZ2ggDQpmcmVxdWVuY3kgc3ltYm9s
IGFjY2Vzc2luZy4gIERpc3BsYXkgYSBzeW1ib2wgb250byANCm5vIEROUy1iYXNlZCBhcHByb2Fj
aCBjYW4gc29sdmUgdGhlICJJRE4iIHByb2JsZW0gYXMgaXQgDQppcyBob3BlZCBieSB1c2VycyBh
bmQgY29tcGFueS9lbnRlcnByaXNlIGRvbWFpbiBuYW1lIA0KcmVnaXN0cmFudHMgYW5kIGl0IGlz
IHByb3NzaWJsZSBub3QgdG8gYWRkIGFub3RoZXIgY29kaW5nIGZvcm1hdCwgDQpmdXJ0aGVyIGNv
bXBsaWNhdGUgdGhlIEROUyBhbmQgcmlzayB1bmtub3duIHByb2JsZW1zIGFuZCANCmluY29tcGF0
aWJpbGl0aWVzLg0KDQoxLjMgVGVybWlub2xvZ3kNCg0KVGhlIGtleSB3b3JkcyAiTVVTVCIsICJT
SEFMTCIsICJSRVFVSVJFRCIsICJTSE9VTEQiLCAiUkVDT01NRU5ERUQiLA0KYW5kICJNQVkiIGlu
IHRoaXMgZG9jdW1lbnQgYXJlIHRvIGJlIGludGVycHJldGVkIGFzIGRlc2NyaWJlZCBpbg0KIFtS
RkMyMTE5XS4NCg0KSGV4YWRlY2ltYWwgdmFsdWVzIGFyZSBzaG93biBwcmVjZWRlZCB3aXRoIGFu
ICIweCIuIEZvciBleGFtcGxlLA0KIjB4YTFiNSIgaW5kaWNhdGVzIHR3byBvY3RldHMsIDB4YTEg
Zm9sbG93ZWQgYnkgMHhiNS4gQmluYXJ5IHZhbHVlcw0KYXJlIHNob3duIHByZWNlZGVkIHdpdGgg
YW4gIjBiIi4gRm9yIGV4YW1wbGUsIGEgbmluZS1iaXQgdmFsdWUgbWlnaHQNCmJlIHNob3duIGFz
ICIwYjEwMTEwMTExMSIuDQoNCkV4YW1wbGVzIGluIHRoaXMgZG9jdW1lbnQgdXNlIHRoZSBub3Rh
dGlvbiBmcm9tIHRoZSBVbmljb2RlIFN0YW5kYXJkDQpbVW5pY29kZTNdIGFzIHdlbGwgYXMgdGhl
IElTTyAxMDY0NiBuYW1lcy4gRm9yIGV4YW1wbGUsIHRoZSBsZXR0ZXINCiJhIiBtYXkgYmUgcmVw
cmVzZW50ZWQgYXMgZWl0aGVyICJVKzAwNjEiIG9yICJMQVRJTiBTTUFMTCBMRVRURVIgQSIuDQoN
ClN0ZXBDb2RlIGNvbnZlcnRzIHN0cmluZ3MgYXQgYSBjbGllbnQgc2l0ZSB3aXRoIGludGVybmF0
aW9uYWxpemVkIA0KY2hhcmFjdGVycyBpbnRvIHN0cmluZ3Mgb2YgVVMtQVNDSUkgdGhhdCBhcmUg
YWNjZXB0YWJsZSBhcyBob3N0IA0KbmFtZSBwYXJ0cyBpbiBjdXJyZW50IEROUyBob3N0IG5hbWlu
ZyB1c2FnZS4gVGhlIGZvcm1lciBhcmUgY2FsbGVkDQoicHJlLWNvbnZlcnRlZCIgYW5kIGEgImds
eXBoIiBmb3IgYSBzeW1ib2wgcmVwZXNlbnRlZCBieSBvbmUgY29kZXBvaW50IA0KaW4gW0lTTzEw
NjQ2XSBvciAiZ2x5cGhzIiBmb3IgYSBzdHJpbmcgb2YgdGhhdCwgYW5kIHRoZSBsYXR0ZXIgDQph
cmUgY2FsbGVkICJwb3N0LWNvbnZlcnRlZCIuDQoNClRoZSBwcm90b2NvbCBjb250YWlucyBvbmUg
cHJvY2VkdXJlIGFuZCBjYWxscyBmb3Igc3RhbmRhcmRpemluZw0KYSBtaW5pbXVtIG51bWJlciBv
ZiBnbHlwaHMgb2YgYSBzY3JpcHQgdXNpbmcgdGhlIHNhbWUgc2NyaXB0DQp0YWcuIEdseXBocyBp
biB0aGUgbWluaW11bSBudW1iZXIgb2YgZ2x5cGggc2V0IGlzIGNhbGxlZCANCiJwYXJ0aWNsZXMi
LiANCg0KVGhlIHByb3RvY29sIHVzaW5nIFVTLUFTQ0lJIHRvIGRlbm90ZSB0aGUgcGhvbmV0aWMg
ZWxlbWVudHMgb2YgYSANCnNjcmlwdCBhbmQgY2FsbHMgZm9yIHN0YW5kYXJkaXppbmcgc3VjaCBh
IG1hcHBpbmcgZm9yIGVhY2ggDQpzY3JpcHQgdGFnLiBUaGUgcGhvbmV0aWMgZWxlbWVudHMgb2Yg
YSBnbHlwaCBpcyBjYWxsZWQgInNwZWxsaW5nIiANCm9mIHRoZSBnbHlwaCBhbmQgaXMgY2FsbGVk
ICJzdGVtIiBmb3IgdGhhdCBvZiBhIHBhcnRpY2xlLg0KDQpUaGUgcHJvdG9jb2wgc3BlY2lmaWVz
IGFuIEFTQ0lJIENvbXBhdGlibGUgW0FDRV0gRW5jb2RpbmcNCm1ldGhvZCBhbmQgdXNpbmcgQ2hp
bmVzZSBzY3JpcHQgYXMgYW4gZXhhbXBsZSB0byBkZW1vbnN0cmF0ZSBpdHMgDQpmZWF0dXJlcywg
aGVyZSBpcyByZWZlcmVkIGFzIGFuICJBQ0UiIHByb2Nlc3MuDQoNCjEuNCBJRE4gc3VtbWFyeQ0K
DQpVc2luZyB0aGUgdGVybWlub2xvZ3kgaW4gW0lETkNvbXBdLCBTdGVwQ29kZSBzcGVjaWZpZXMg
YW4gQUNFIGZvcm1hdCANCmZvciBhcmNoLTIgKHNlbmQgYmluYXJ5IG9yIEFDRSksIGFuZCBhcmNo
LTMgKGp1c3Qgc2VuZCBBQ0UpLg0KDQpUaGUgbGVuZ3RoIGNoYXJhY3RlcmlzdGljcyBvZiBTdGVw
Q29kZSBhcmUgZGlzY3Vzc2VkIGFib3ZlIA0KKDEuMSBDb250ZXh0KSwgaXMgYSB2YXJpYWJsZSBk
ZXBlbmRpbmcgb24gdXNlcnMnIGNob2ljZSBhbW9uZyANCm1hbnkgZmFjdG9ycy4gSXQgZml0cyB3
ZWxsIHdpdGggZXhpc3RpbmcgY29tcHJlc3Npb24gYW5kIHNlY3VyaXR5DQp0cmVhdG1lbnRzLiAN
Cg0KSXQgY2FsbHMgZm9yIHN0YW5kYXJkcml6aW5nIHBob25ldGljIGVsZW1lbnRzIGFuZCBtaW5p
bXVtIGdseXBoIHNldA0Kd2l0aGluIGl0cyB1c2VyIGNvbW11bml0eSAoYW5kIGxhYmVsZWQgYnkg
c2NyaXB0IHRhZyksIHdoaWxlIA0KYXNraW5nIHRoZSBpbnRlcm5ldCBpbmR1c3RyeSB0byBlbmZv
cmNlIHRoZSBzdGFuZGFyZCBhbmQgcHJvdmlkaW5nDQpjcm9zcyByZWZlcmVuY2UgdG8gZGlmZmVy
ZW50IHNjcmlwdCB0YWdzIGludG8gVW5pY29kZSBzdGFuZGFyZC4NCg0KMi4gSG9zdCBQYXJ0IFRy
YW5zZm9ybWF0aW9uDQoNCkFjY29yZGluZyB0byBbU1REMTNdLCBob3N0IHBhcnRzIG11c3QgYmUg
Y2FzZS1pbnNlbnNpdGl2ZSwgc3RhcnQgYW5kDQplbmQgd2l0aCBhIGxldHRlciBvciBkaWdpdCwg
YW5kIGNvbnRhaW4gb25seSBsZXR0ZXJzLCBkaWdpdHMsIGFuZA0KdGhlIGh5cGhlbiBjaGFyYWN0
ZXIgKCItIikuIFRoaXMsIG9mIGNvdXJzZSwgZXhjbHVkZXMgYW55DQppbnRlcm5hdGlvbmFsaXpl
ZCBjaGFyYWN0ZXJzLCBhcyB3ZWxsIGFzIG1hbnkgb3RoZXIgY2hhcmFjdGVycyBpbg0KdGhlIEFT
Q0lJIGNoYXJhY3RlciByZXBlcnRvaXJlLiBGdXJ0aGVyLCBkb21haW4gbmFtZSBwYXJ0cyBtdXN0
IGJlDQo2MyBvY3RldHMgb3Igc2hvcnRlciBpbiBsZW5ndGguDQoNCjIuMSBOYW1lIHRhZ2dpbmcN
Cg0KQWxsIHBvc3QtY29udmVydGVkIG5hbWUgcGFydHMgdGhhdCBjb250YWluIGludGVybmF0aW9u
YWxpemVkDQpjaGFyYWN0ZXJzIGJlZ2luIHdpdGggdGhlIHN0cmluZyAiZ2wtcC0iLCB3aGVyZSAi
Z2wiIGRlbm90ZSB0aGUgDQpnbHlwaCBzZXQgb3Igc2NyaXB0IGVuY29kZWQgYXMgc3BlY2lmaWVk
IGJ5IFtSRkMyMjc3XSwgYW5kIA0KInAiIGRlbm90ZSB0aGUgcGhvbmV0aWMgc3RhbmRhcmQgdXNl
ZCwgaXQgU0hPVUxEIGJlIHJlc2VydmVkIHdpdGgNCklBTkEuIFRoZSBzdHJpbmcgImdsLXAtIiB3
aWxsIGFsbG93IDY3NCBzY3JpcHRzIGFuZCAyNCBwaG9uZXRpYyANCnN0YW5kYXJkcyBvZiBlYWNo
IHRvIGJlIGVuY29kZWQuIFRoZSBhc3NpZ25tZW50IG9mICJnbC1wLSIgc2hhbGwgDQpiZSBkZWZp
bmVkIGluIGZ1dHVyZSB2ZXJzaW9ucyBvZiB0aGlzIGRyYWZ0Lg0KDQpOb3RlIHRoYXQgYSB6b25l
IGFkbWluaXN0cmF0b3IgTUFZIHN0aWxsIGNob29zZSB0byB1c2UgImdsLXAtIiBhdA0KdGhlIGJl
Z2lubmluZyBvZiBhIGhvc3RuYW1lIHBhcnQgZXZlbiBpZiB0aGF0IHBhcnQgZG9lcyBub3QgY29u
dGFpbg0KaW50ZXJuYXRpb25hbGl6ZWQgY2hhcmFjdGVycy4gWm9uZSBhZG1pbmlzdHJhdG9ycyBN
QVkgY3JlYXRlDQpob3N0IHBhcnQgbmFtZXMgdGhhdCBiZWdpbiB3aXRoICJnbC1wLSIgd2hpY2gg
bWVhbnMgbm8gY29udmVyc2lvbg0KaXMgZG9uZSBhbmQgZGlzcGxheSBzeXN0ZW1zIFNIT1VMRCBp
Z25vcmUgY29udmVydGluZyANCmludGVybmF0aW9uYWxpemVkIGNoYXJhY3RlcnMgYmFjayBmb3Ig
ZGlzcGxheS4NCg0KMi4yIENvbnZlcnRpbmcgYW4gaW50ZXJuYXRpb25hbGl6ZWQgbmFtZSB0byBh
biBBQ0UgbmFtZSBwYXJ0DQoNClRvIGNvbnZlcnQgYSBzdHJpbmcgb2YgaW50ZXJuYXRpb25hbGl6
ZWQgY2hhcmFjdGVycyBpbnRvIGFuIEFDRSBuYW1lDQpwYXJ0LCB0aGUgZm9sbG93aW5nIHN0ZXBz
IE1VU1QgYmUgcHJlZm9ybWVkIGluIHRoZSBleGFjdCBvcmRlciBvZg0KdGhlIHN1YnNlY3Rpb25z
IGdpdmVuIGhlcmUuDQoNCklmIGEgbmFtZSBwYXJ0IGNvbnNpc3RzIGV4Y2x1c2l2ZWx5IG9mIGNo
YXJhY3RlcnMgdGhhdCBjb25mb3JtIHRvDQp0aGUgaG9zdG5hbWUgcmVxdWlyZW1lbnRzIGluIFtT
VEQxM10gb3IgdGhlIHN0cmluZyAiZ2wtcC0iLCANCnRoZSBuYW1lIE1VU1QgTk9UIGJlIGNvbnZl
cnRlZCB0byBTdGVwQ29kZS4gVGhhdCBpcywgYSBuYW1lIHBhcnQgDQp0aGF0IGNhbiBiZSByZXBy
ZXNlbnRlZCB3aXRob3V0IFN0ZXBDb2RlIE1VU1QgTk9UIGJlIGNoYW5nZWQuIA0KVGhpcyBhYnNv
bHV0ZSByZXF1aXJlbWVudCBwcmV2ZW50czoNCgkxLiBkb3VibGUgZW5jb2RpbmcgZnJvbSBhIGNs
aWVudCBvZiB1c2VyIGtleWJvYXJkIGlucHV0IGFuZA0KCSBhIHNlcnZlciBwcm92aWRlcjsNCgky
LiBtZXNzIHVwIGV4aXN0aW5nIHJlZ2lzdGVyZWQgZG9tYWluIG5hbWVzOw0KCTMuIGZyb20gYmVp
bmcgdHdvIGRpZmZlcmVudCBlbmNvZGluZ3MgZm9yIGEgc2luZ2xlIEROUyANCglyZWdpc3RlcmVk
IGhvc3RuYW1lOw0KCTQuIGludGVyZmVyaW5nIHdpdGggcmVnaXN0ZXJlZCBnbHlwaHMgd2l0aCBt
b3JlIHRoYW4gb25lDQoJcGhvbmV0aWMgc3RhbmRhcmQsIHN1Y2ggYXMgQ2hpbmVzZSBzY3JpcHQu
DQoNCklmIGFueSBjaGVja2luZyBmb3IgcHJvaGliaXRlZCBuYW1lIHBhcnRzIChzdWNoIGFzIG9u
ZXMgdGhhdCBhcmUNCnByb2hpYml0ZWQgY2hhcmFjdGVycywgY2FzZS1mb2xkaW5nLCBvciBjYW5v
bmljYWxpemF0aW9uKSBpcyB0byBiZQ0KZG9uZSwgaXQgTVVTVCBiZSBkb25lIGFmdGVyIGRvaW5n
IHRoZSBjb252ZXJzaW9uIHRvIGFuIEFDRSBuYW1lIA0KcGFydCBhcyBpdCBpcyBzcGVjaWZpZWQg
aW4gW25hbWVwcmVwXS4NCg0KQ2hhcmFjdGVycyBvdXRzaWRlIHRoZSBmaXJzdCBwbGFuZSBvZiBj
aGFyYWN0ZXJzICh0aG9zZSB3aXRoDQpjb2RlcG9pbnRzIGFib3ZlIFUrRkZGRikgTVVTVCBiZSBy
ZXByZXNlbnRlZCB1c2luZyBzdXJyb2dhdGVzLCBhcw0KZGVzY3JpYmVkIGluIHRoZSBVVEYtMTYg
ZGVzY3JpcHRpb24gaW4gSVNPIDEwNjQ2Lg0KDQpUaGUgaW5wdXQgbmFtZSBzdHJpbmcgY29uc2lz
dHMgb2YgY2hhcmFjdGVycyBmcm9tIHRoZSBJU08gMTA2NDYNCmNoYXJhY3RlciBzZXQgaW4gYmln
LWVuZGlhbiBVVEYtMTYgZW5jb2RpbmcuIFRoaXMgaXMgdGhlDQpwcmUtY29udmVydGVkIHN0cmlu
Zy4NCg0KMi4yLjEgQ2hlY2sgdGhlIGlucHV0IHN0cmluZyBmb3IgZGlzYWxsb3dlZCBuYW1lcw0K
DQpJZiB0aGUgaW5wdXQgc3RyaW5nIGNvbnNpc3RzIG9ubHkgb2YgY2hhcmFjdGVycyB0aGF0IGNv
bmZvcm0gdG8gdGhlDQpob3N0bmFtZSByZXF1aXJlbWVudHMgaW4gW1NURDEzXSwgb3IgdGhlIGlu
cHV0IHN0cmluZyBjb25zaXN0cyANCmEgbnVsbCBsYW5ndWFnZSB0YWcsIHRoZSBjb252ZXJzaW9u
IE1VU1Qgc3RvcCB3aXRoIGFuIGVycm9yLg0KDQoyLjIuMiBSZXByZXNlbnQgZ2x5cGhzIGJ5IHRo
ZWlyIHNwZWxsaW5nIGFuZCBwYXJ0aWNsZSBsYXlvdXQuDQoNCjIuMi4yLjEgU3RlcENvZGUgZGVm
aW5hdGlvbiBmb3IgZGlnaXRzDQoNCglUb25lIG1hcmtzIFtNYWNtaWxsYW45M10NCgkwCW5vIHRv
bmUNCgkxCWZsYXQvbWFjcm9uICgtKQ0KCTIJcmlzZS9hY3V0ZSAoLykNCgkzCWRpcC9icmV2ZSAo
dikNCgk0CWRyb3AvZ3JhdmUgKFwpDQoJNQl0aHJvdy9jaXJjdW1mbGV4ICheKQ0KCTYJdGhyaWxs
L3RpbGRlICh+KQ0KCTcJZGllcmVzaXMgKC4uKQ0KCTgJY2VkaWxsYQkoaG9vaykJDQoNCglQYXJ0
aWNsZSBsYXlvdXQgW1llOTVdDQoJMAllbmQgb2YgYSBzdGVtIG9yIGEgc3BlbGxpbmcNCgkxCXRv
IGl0cyBsZWZ0DQoJMgl0byBpdHMgYmVsbG93DQoJMwl0byBpdHMgaW5zaWRlIChhbiBlbmNsb3N1
cmUgcGFydGljbGUpDQoJNAl0byBpdHMgb3V0c2lkZSAobm9ybWFsbHkgYSBjZW50ZXIgZGl2aWRl
cikNCg0KMi4yLjIuMiBTdGVwQ29kZSBwaG9uZXRpYyBzeW1ib2wgdGFibGVzDQoNCjIuMi4yLjIu
MSBDaGluZXNlDQoNCglOb3RlOiBUaGlzIGlzIGEgbGlzdCBleHRyYWN0ZWQgZnJvbSBbRGljdGlv
bmFyeTc5XSBhbmQgDQpvdGhlciBzb3VyY2VzLiANCg0KCVBpbnlpbgkJV2FkZQkJWmh1eWluDQoJ
YgkJcAkJYg0KCXAJCXAvCQlwDQoJbQkJbQkJbQ0KCWYJCWYJCWYNCglkCQl0CQlkDQoJdAkJdC8J
CXQNCgluCQluCQluDQoJbAkJbAkJbA0KCWcJCWsJCWcNCglrCQlrLwkJaw0KCWgJCWgJCWgNCglq
CQljaAkJag0KCXEJCWNoLwkJcQ0KCXgJCWhzCQl4DQoJemgJCWNoCQl6aA0KCWNoCQljaC8JCWNo
DQoJc2gJCXNoCQlzaA0KCXIJCWoJCXINCgl6CQl0cwkJeg0KCWMJCXRzLwkJYw0KCXMJCXMJCXMN
CglhCQlhCQlhDQoJbwkJdQkJbw0KCWUJCWVeCQllDQoJZV4JCWVoCQllaQ0KCWkJCXVoCQlpDQoJ
dQkJdQkJdQ0KCXVvCQlvCQlvbw0KCXUuLgkJdS4uCQl1Li4NCgl5CQl5CQl5DQoJdwkJdwkJdw0K
CXYgKCcgc3BlbGxpbmcgc2VwYXJhdG9yKQ0KDQoyLjIuMi4yLjIgT3RoZXIgc2NyaXB0cyB0byBj
b21lDQoNCjIuMi4zIFN0ZXBDb2RlIEZvcm1hdA0KCUZvcm1hdCBEZWZpbmF0aW9uOiBBIFN0ZXBj
b2RlIHVuaXQgaXMgYSBzdHJpbmcgb2YgW0EtWmEtejAtOV0NCmNoYXJhY3RlcnMgd2l0aG91dCBh
bnkgd2hpdGUgc3BhY2VzLCBCTEFOSywgaW4gYmV0d2Vlbi4gRm9yIGVhY2ggU3RlcENvZGUgdW5p
dCwgDQp0aGVyZSBhcmUgZGF0YSBlbGVtZW50cyBpbmRpY2F0ZWQgYnkgIiIsIHdoaWNoIGlzIGEg
cmVxdWlyZWQgZWxlbG1lbnQsDQphbmQgW10gd2hlcmUgdGhlIGVsZW1lbnQgaXMgb3B0aW9uYWws
IGFuZCAvIHdoZXJlIHRoZSBkYXRhIGlzIHNlbGVjdGFibGUuDQoNCglTeCBzdGFuZHMgZm9yIFNw
ZWxsaW5nIG9mIHh0aCBnbHlwaDsNCglUeCBzdGFuZHMgZm9yIFRvbmUgb2YgeHRoIGdseXBoOw0K
CVB5IHN0YW5kcyBmb3IgU3RlbSBmb3IgeXRoIHBhcnRpY2xlOw0KCUx5IHN0YW5kcyBmb3IgTGF5
b3V0IHJlbGF0aW9uIGZyb20geSB0byB5KzE7DQoJUHgueSBzdGFuZHMgZm9yIFN0ZW0gZm9yIFh0
aCBnbHlwaCBhbmQgaXRzIHl0aCBwYXJ0aWNsZTsNCglMeC55IHN0YW5kcyBmb3IgTGF5b3V0IHJl
bGF0aW9uIGZyb20gWHRoIGdseXBoIGFuZCBpdHMgeSB0byB5KzEuDQoJIA0KMi4yLjMuMS4gT25l
IGdseXBoDQoJIlMiIlQiW1AxXVtMMV1bUDJdW0wyXS4uLltQeV1bMC9CTEFOS10NCg0KRXhhbXBs
ZTp4aW4xcWluIA0KCXhpbjFxaW4xamluMCANCg0KMi4yLjMuMi4gR2x5cGhzDQoJIlMxUzJTMy4u
LlN4IiJUMVQyLi4uVHgiW1AxLjFdW0wxLjFdW1AxLjJdW0wxLjJdLi4uW1AxLnldWzBdDQoJCQlb
UDIuMV1bTDIuMV1bUDIuMl1bTDIuMl0uLi5bUDIueV1bMF0NCgkJCS4uLiANCgkJCVtQeC4xXVtM
eC4xXVtQeC4yXVtMeC4yXS4uLltQeC55XVswL0JMQU5LXQ0KDQpFeGFtcGxlIG9mIGdseXBocyBv
ZiBmb3VyOg0KCXhpbnpodXFpbmdodWExMjEyDQoJeGluemh1cWluZ2h1YTEyMTJxaW4xamluMGdl
MWdlMHNodWkxcWluZzANCgl4aW56aHVxaW5naHVhMTIxMnFpbjFqaW4wZ2UxZ2Uwc2h1aTFxaW5n
MGh1YQ0KCXhpbnpodXFpbmdodWExMjEycWluMWppbjBnZTFnZTBzaHVpMXFpbmcwaHVhMnNoaTAN
Cg0KVGhlIGZvdXIgU3RlcENvZGVzIGFyZSBlcXVpdmFsZW50LCBkZXBlbmRpbmcgb24gd2hlcmUg
DQppdCBpcyByZWdpc3RlcmVkLCB0aGUgc2l6ZSBvZiB0aGUgZGF0YWJhc2UsIGFzIHdlbGwgYXMg
dGhlcmUgZXhpc3QNCnNpbWlsYXIgaG9zdG5hbWVzIGl0IGhhcyBjb25maWN0IHdpdGguIA0KDQoy
LjMuIFN0ZXBDb2RlIEVuY29kaW5nIFByb2Nlc3MNCg0KRWl0aGVyLCBTdGVwQ29kZSBtYXkgYmUg
b2J0YWluZWQgZnJvbSBVbmljb2RlIHRvIFN0ZXBDb2RlIHRocm91Z2gNCmEgY29kZSBsb29rdXAg
dGFibGUsIGFuZCBjb21iaW5lcyBnbHlwaCBjb2RlIGludG8gZ2x5cGhzIGNvZGUgYXMgDQpzaG93
biBpbiAyLjIuIA0KDQpPciwgaXQgaXMgaW5wdXRlZCBkaXJlY3RseSBmcm9tIGtleWJvYXJkcywg
d2hlcmUgYW4gaW5wdXQgDQpwcm9jZXNzaW5nIG1vZHVsZSB0byB2ZXJpZnkgY29ycmVjdG5lc3Mg
b2YgaW50ZW50ZWQgZ2x5cGhzIGlzIG5lY2Vzc2FyeS4gDQoNClByZXBlbmQgImdscC0tIiBvciB0
aGUgbmFtZSBvZiBjb252ZXJzaW9uIHRhYmxlIHVzZWQgYXMgc2NyaXB0IHRhZyANCnRvIHRoZSBw
b3N0LWNvbnZlcmVkIHN0cmluZzsgZmluaXNoLiBUaGlzIGlzIHRoZSBob3N0bmFtZSBwYXJ0IHRo
YXQgDQpjYW4gYmUgdXNlZCBpbiBETlMgcmVnaXN0cmF0aW9uIGFzIHdlbGwgYXMgcmVzb2x1dGlv
bi4gDQoNCkdvIHRocm91Z2ggW25hbWVwcmVwXSwgY2hlY2tpbmcgZm9yIHByb2hpYml0ZWQgY2hh
cmFjdGVycywgDQpjYXNlLWZvbGRpbmcsIG9yIGNhbm9uaWNhbGl6YXRpb24uIA0KDQoyLjQuIENv
bnZlcnRpbmcgYSBTdGVwQ29kZSBob3N0bmFtZSBwYXJ0IHRvIGFuIGludGVybmF0aW9uYWxpemVk
IG5hbWUNCg0KVGhlIHByb2Nlc3MgaGFzIHRocmVlIHN0ZXBzIHdpdGggc2NyaXB0IHRhZyB1bnRv
dWNoZWQ6DQoNClN0ZXAgMS5JZiBhIGRvbWFpbiBuYW1lIHBhcnQgY29uc2lzdHMgbm8gc2NyaXB0
IHRhZywgdGhlbiBnb3RvIFN0ZXAgMzsNCglPdGhlcndpc2UgZW5hYmxlIGNvbnZlcnNpb24gdGFi
bGUgbmFtZWQgImdscCIgZnJvbSBTdGVwQ29kZSB0byANCglVbmljb2RlIG9yIG90aGVyIGNvZGUs
IG9idGFpbiB0aGUgY29yZXNwb25kZW5kcy4gDQpTdGVwIDIuSWYgdGhlIGNvcmVzcG9uZGVudCBp
cyB0aGVyZSB0aGVuIGdvdG8gU3RlcCAzOw0KCU90aGVyd2lzZSBkZWNvbXBvc2VzIHRoZSBwb3N0
LWNvbnZlcnRlZCBzdHJpbmcgaW50byBhIG51bWJlcg0KCSAgIG9mIGluZGl2aWR1YWwgZ2x5cGgg
c3BlY2lmaWVkIGluIHRoZSAiVCIgZmllbGQ7IA0KCVNlYXJjaGluZyBmb3IgZWFjaCBnbHlwaDsN
CglJZiBhbnkgb2YgdGhlIGdseXBoIGlzIG5vdCBmb3VuZCwgDQoJCWNvbXBvc2UgYW4gZXJyb3Ig
bWVzc2FnZSBhbmQgDQoJCVJlcXVlc3RpbmcgdGhlIG1pc3NpbmcgZ2x5cGggdG8gYmUgc3VwcGxp
ZWQgDQoJCQlmcm9tIHRoZSBzZW5kZXIuDQpTdGVwIDMuRGlzcGxheSBhdmFpbGFibGUgZ2x5cGgg
d2hlcmUgbWlzc2luZyBnbHlwaCBpcyBzaG93biB3aXRoDQoJaXRzIFN0ZXBDb2RlLiANCg0KMy4g
U2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMNCg0KTXVjaCBvZiB0aGUgc2VjdXJpdHkgb2YgdGhlIElu
dGVybmV0IHJlbGllcyBvbiB0aGUgRE5TLiBUaHVzLCBhbnkNCmNoYW5nZSB0byB0aGUgY2hhcmFj
dGVyaXN0aWNzIG9mIHRoZSBETlMgY2FuIGNoYW5nZSB0aGUgc2VjdXJpdHkgb2YNCm11Y2ggb2Yg
dGhlIEludGVybmV0LiBUaHVzLCBTdGVwQ29kZSBtYWtlcyBubyBjaGFuZ2VzIHRvIHRoZSBETlMg
aXRzZWxmLg0KDQpIb3N0bmFtZXMgYXJlIHVzZWQgYnkgdXNlcnMgdG8gY29ubmVjdCB0byBJbnRl
cm5ldCBzZXJ2ZXJzLiBUaGUNCnNlY3VyaXR5IG9mIHRoZSBJbnRlcm5ldCB3b3VsZCBiZSBjb21w
cm9taXNlZCBpZiBhIHVzZXIgZW50ZXJpbmcgYQ0Kc2luZ2xlIGludGVybmF0aW9uYWxpemVkIG5h
bWUgY291bGQgYmUgY29ubmVjdGVkIHRvIGRpZmZlcmVudA0Kc2VydmVycyBiYXNlZCBvbiBkaWZm
ZXJlbnQgaW50ZXJwcmV0YXRpb25zIG9mIHRoZSBpbnRlcm5hdGlvbmFsaXplZA0KaG9zdG5hbWUu
IFRodXMgdGhlIHJlc3RyaWN0aW9uIG9mIEROUyBuYW1lcyB0byBhIHNtYWxsIHN5bWJvbCBzZXQg
aXMNCm5lY2Vzc2FyeSBhbmQgZWZmZWN0aXZlLCB3aGVyZSBhZGRpbmcgYW55IG90aGVyIGRhdGEg
Zm9ybWF0IHN1Y2ggYXMgDQpVVEYtOCBvbmx5IG9wZW5zIHRoZSBzZWN1cml0eSBnYXRlIGZvciBj
b21wbGljYXRpb24uICANCg0KNC5JbnRlcm5hdGlvbmFsaXphdGlvbiBjb25zaWRlcmF0aW9ucw0K
DQpTdGVwQ29kZSBpcyBkZXNpZ25lZCBzbyB0aGF0IGV2ZXJ5IGludGVybmF0aW9uYWxpemVkIGhv
c3RuYW1lIHBhcnQgY2FuDQpiZSByZXByZXNlbnRlZCBhcyBvbmUgYW5kIG9ubHkgb25lIEROUy1j
b21wYXRpYmxlIHN0cmluZy4gSWYgdGhlcmUNCmlzIHR3byBkaWZmZXJlbnQgd2F5cyB0byBvYnRh
aW4gdGhlIHNhbWUgZ2x5cGggb24gYSBkaXNwbGF5IGRldmljZSwNCnRoZW4gdGhleSBhcmUgc3Rp
bGwgdHdvIGRpc3RpbmN0IGhvc3RuYW1lcywgd2l0aCBubyBiZWFyaW5nIG9uIA0Kc2VjdXJpdHkg
aXNzdWUuIElmIHRoZXJlIGlzIGFueSB3YXkgdG8gZm9sbG93IHRoZSBzdGVwcyBpbiB0aGlzIA0K
ZG9jdW1lbnQgYW5kIGdldCB0d28gb3IgbW9yZSBkaWZmZXJlbnQgcmVzdWx0cywgaXQgaXMgYW4g
ZXJyb3IgaW4gDQp0aGUgZG9tYWluIG5hbWUgcmVnaXN0cmF0aW9uIHByb2Nlc3MsIHdoZXJlIG9u
ZSBkb21haW4gbmFtZSByZWdpc3Rlcg0KIGZhaWxzIHVwZGF0ZXMgb3RoZXIgZG9tYWluIG5hbWUg
cmVnaXN0ZXIgc2VydmVycyBhIG5ld2x5IHJlZ2lzdGVyZWQNCiBhbmQgd2VsbCByZXNlYXJjaGVk
IGhvc3RuYW1lLiANCg0KNS4gUmVmZXJlbmNlcw0KDQpbQVNDSUldIEFtZXJpY2FuIE5hdGlvbmFs
IFN0YW5kYXJkcyBJbnN0aXR1dGUgKGZvcm1lcmx5IFVuaXRlZA0KU3RhdGVzIG9mIEFtZXJpY2Eg
U3RhbmRhcmRzIEluc3RpdHV0ZSksIFgzLjQsIDE5NjgsICJVU0EgQ29kZSBmb3INCkluZm9ybWF0
aW9uIEludGVyY2hhbmdlIi4gKEFOU0kgWDMuNC0xOTY4KQ0KDQpbSUROQ09NUF0gICAiQ29tcGFy
aXNvbiBvZiBJbnRlcm5hdGlvbmFsaXplZCBEb21haW4gTmFtZSBQcm9wb3NhbHMiLA0KICAgICAg
ICAgICAgZHJhZnQtaWV0Zi1pZG4tY29tcGFyZS0wMC50eHQsIEp1bmUgMjAwMCwgUC4gSG9mZm1h
bi4NCg0KW0lETlJlcV0gWml0YSBXZW56ZWwgYW5kIEphbWVzIFNlbmcsICJSZXF1aXJlbWVudHMg
b2YNCkludGVybmF0aW9uYWxpemVkIERvbWFpbiBOYW1lcyIsIGRyYWZ0LWlldGYtaWRuLXJlcXVp
cmVtZW50cy4gTWF5IDIwMDEuKQ0KDQpbSVNPMTA2NDZdICBJU08vSUVDIDEwNjQ2LTE6MjAwMCAo
bm90ZSB0aGF0IGFuIGFtZW5kbWVudCAxIGlzIGluDQogICAgICAgICAgICBwcmVwYXJhdGlvbiks
IElTTy9JRUMgMTA2NDYtMiAoaW4gcHJlcGFyYXRpb24pLCBwbHVzDQogICAgICAgICAgICBjb3Jy
aWdlbmRhIGFuZCBhbWVuZG1lbnRzIHRvIHRoZXNlIHN0YW5kYXJkcy4NCg0KW0RpY3Rpb25hcnk3
OV0gQmVpamluZyBGb3JpZWduIExhbmd1YWdlIERlcHQuLCAiQSBDaGluZXNlLUVuZ2xpc2ggDQpE
aWN0aW9uYXJ5IiwgMTk3OSwgQksjIDkwMTcuODEwLg0KDQpbTWFjbWlsbGFuOTNdIFRoZSBNYWNt
aWxsYW4gVmlzdWFsIERlc2sgUmVmZXJlbmNlLCAxOTkzLCANCklTQk4gMC0wMi01MzEzMTAteC4N
Cg0KW1JGQzIyNzddICAgIklFVEYgUG9saWN5IG9uIENoYXJhY3RlciBTZXRzIGFuZCBMYW5ndWFn
ZXMiLA0KICAgICAgICAgICAgcmZjMjI3Ny50eHQsIEphbnVhcnkgMTk5OCwgSC4gQWx2ZXN0cmFu
ZC4NCg0KW1JGQzIxMTldIFNjb3R0IEJyYWRuZXIsICJLZXkgd29yZHMgZm9yIHVzZSBpbiBSRkNz
IHRvIEluZGljYXRlDQpSZXF1aXJlbWVudCBMZXZlbHMiLCBNYXJjaCAxOTk3LCBSRkMgMjExOS4N
Cg0KW1NURDEzXSBQYXVsIE1vY2thcGV0cmlzLCAiRG9tYWluIG5hbWVzIC0gaW1wbGVtZW50YXRp
b24gYW5kDQpzcGVjaWZpY2F0aW9uIiwgTm92ZW1iZXIgMTk4NywgU1REIDEzIChSRkMgMTAzNSku
DQoNCltVTklDT0RFXSAgIFRoZSBVbmljb2RlIENvbnNvcnRpdW0sICJUaGUgVW5pY29kZSBTdGFu
ZGFyZCIuIERlc2NyaWJlZCBhdA0KICAgICAgICAgICAgaHR0cDovL3d3dy51bmljb2RlLm9yZy91
bmljb2RlL3N0YW5kYXJkL3ZlcnNpb25zLy4NCg0KW1VOSUNPREUzMF0gVGhlIFVuaWNvZGUgQ29u
c29ydGl1bSwgIlRoZSBVbmljb2RlIFN0YW5kYXJkIC0tIFZlcnNpb24NCiAgICAgICAgICAgIDMu
MCIsIElTQk4gMC0yMDEtNjE2MzMtNS4gU2FtZSByZXBlcnRvaXJlIGFzIElTTy9JRUMNCiAgICAg
ICAgICAgIDEwNjQ2LTE6MjAwMC4gRGVzY3JpYmVkIGF0IGh0dHA6Ly93d3cudW5pY29kZS5vcmcv
dW5pY29kZS8NCiAgICAgICAgICAgIHN0YW5kYXJkL3ZlcnNpb25zL1VuaWNvZGUzLjAuaHRtbC4N
Cg0KW1llOTVdIExpYW5hIFllLCAiQSBMYW5ndWFnZSBPcmllbnRlZCBDaGluZXNlIEVuY29kaW5n
IGZvciANCk11bHRpbGluZ3VhbCBDb21wdXRpbmcgRW52aXJvbm1lbnRzIiwgaW4gIlByb2NlZWRp
bmcgb2YgdGhlIDE5OTUgDQpJbnRlcm5hdGlvbmFsIENvbmZlcmVuY2Ugb24gQ29tcHV0ZXIgUHJv
Y2Vzc2luZyBvZiBPcmllbnRhbA0KTGFuZ3VhZ2VzIiwgUGFnZSAzMjMuDQoNCjYuIEFja25vd2xl
ZGdlbWVudHMNCg0KVGhlIGF1dGhvciBoYXMgcmV1c2VkIGV4aXN0aW5nIElETiBkcmFmdCBkb2N1
bWVudCBhbmQgbGFuZ3VhZ2UgYXMgDQptdWNoIGFzIHBvc3NpYmxlIHRvIGRlbW9uc3RyYXRlIHRo
ZSBkZWVwIHJlc3BlY3QgZm9yIHRoZSB3b3JrIGhhcyANCmJlZW4gZG9uZSBieSBtZW1iZXJzIG9m
IHRoaXMgd29ya2luZyBncm91cC4NCg0KNy4gSUFOQSBDb25zaWRlcmF0aW9ucw0KDQpUaGlzIGRv
Y3VtZW50IHJlcXVpcmUgSUFOQSBhY3Rpb24gZm9yIGF2YWlsaWJpbGl0eSBvZiBsYW5ndWFnZSB0
YWcsIA0KYW5kIHJlZ2lzdHJhdGlvbiBmb3IgZWFjaCB0YWcgYW5kIGl0cyBzdWItZmllbGQgZm9y
IHBob25ldGljIHN5c3RlbSANCnVzZWQuDQoNCjguIEF1dGhvciBDb250YWN0IEluZm9ybWF0aW9u
DQoNCkxpYW5hIFllDQpZJkQgSVNHDQoyNjA3IFJlYWQgQXZlLg0KQmVsbW9udCwgQ0EgOTQwMDIs
IFVTQS4NCig2NTApIDU5Mi03MDkyDQpsaWFuYS55ZGlzZ0BqdW5vLmNvbQ0KDQpFeHBpcmVzIE5v
dmVtYmVyIDIwMDENCg0K
----__JNP_000_4cbf.3257.21f0--



From owner-idn@ops.ietf.org  Tue May 29 07:19:20 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA28500
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 07:19:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154hHh-000L1T-00
	for idn-data@psg.com; Tue, 29 May 2001 04:03:33 -0700
Received: from malmo.trab.se ([131.115.48.10])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154hHb-000L1N-00
	for idn@ops.ietf.org; Tue, 29 May 2001 04:03:32 -0700
Received: from valinor.malmo.trab.se (valinor [131.115.48.20]) by malmo.trab.se (8.10.1/TRAB-primary-2) with ESMTP id f4TB3LI27407; Tue, 29 May 2001 13:03:21 +0200 (MEST)
Received: from valinor by valinor.malmo.trab.se (8.9.3+Sun/TRM-1-KLIENT); Tue, 29 May 2001 13:02:16 +0200 (MEST) (MET)
Message-Id: <200105291102.NAA04973@valinor.malmo.trab.se>
Date: Tue, 29 May 2001 13:02:16 +0200 (MEST)
From: Dan Oscarsson <Dan.Oscarsson@trab.se>
Reply-To: Dan Oscarsson <Dan.Oscarsson@trab.se>
Subject: Re: [idn] UTF-8 as the long-term IDN solution
To: idn@ops.ietf.org, amc@cs.berkeley.edu
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: tVvly1qWSI/NwSxWD/Dffg==
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: to work as in IDNA the name must be nameprepped before encoded
>>      using ACE.
>> UTF-8:  need only be normalised.
>
>Why even normalize it?  If you intend to require DNS servers to perform
>Unicode case-folding in order to perform the lookup, then why not have
>them perform normalization as well?
>

If all UCS text is normalised (and it is quite easy to do this on input),
the software to handle UCS/UTF-8 gets much simpler.

   Dan




From owner-idn@ops.ietf.org  Tue May 29 09:32:31 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA00985
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 09:32:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154jR8-000OE9-00
	for idn-data@psg.com; Tue, 29 May 2001 06:21:26 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154jR7-000OE3-00
	for idn@ops.ietf.org; Tue, 29 May 2001 06:21:25 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA16663;
        Tue, 29 May 2001 09:21:21 -0400 (EDT)
Message-Id: <200105291321.JAA16663@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Sherin Alsoudani" <sherinalsoudani@hotmail.com>
cc: James@Seng.cc, djb@cr.yp.to, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 as the long-term IDN solution 
In-reply-to: Your message of "Tue, 29 May 2001 00:33:40 PDT."
             <F150CRGryWtIIZS2TRq0000a873@hotmail.com> 
Date: Tue, 29 May 2001 09:21:21 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> I agree that the choice of ACE-forever is simply not a realistic option.
> Given that the largest use of the Internet is for the Web, and given that at
> least for Arabic there is basically only one de facto browser that supports
> that language, then it is necessary for Arabic speakers to ask "what
> encoding, if any, does that browser support?"  The answer is UTF-8, and I
> cannot speculate on when Microsoft would upgrade their browser to send
> RACE...

Even if we allowed UTF-8 queries from day one, it seems unlikely that these
would be done in a manner that is compatible with this existing browser.
If nothing else, this browser isn't going to normalize the names before sending 
them in queries.

(For that matter, it's also unlikely that we would adopt RACE - we would very
likely choose some other ACE.)

Keith



From owner-idn@ops.ietf.org  Tue May 29 09:32:34 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA00996
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 09:32:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154jNB-000O72-00
	for idn-data@psg.com; Tue, 29 May 2001 06:17:21 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154jNA-000O6w-00
	for idn@ops.ietf.org; Tue, 29 May 2001 06:17:20 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA16602;
        Tue, 29 May 2001 09:15:54 -0400 (EDT)
Message-Id: <200105291315.JAA16602@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Dan Oscarsson <Dan.Oscarsson@trab.se>
cc: djb@cr.yp.to, idn@ops.ietf.org, James@Seng.cc
Subject: Re: [idn] UTF-8 as the long-term IDN solution 
In-reply-to: Your message of "Tue, 29 May 2001 08:57:05 +0200."
             <200105290657.IAA04912@valinor.malmo.trab.se> 
Date: Tue, 29 May 2001 09:15:54 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Just think about:
> In my e-mail I get a line:
> To: text QUOTED-PRINTABLE-TEXT <USER-NAME-COMPATABLE-TEXT@ACE-NAME.ACE-NAME.com>
> 
> To handle this I must parse the line, identify each part that have their
> own encoding, have an decode for each type and decode them.
> If we used just UTF-8, to convert into local character set, you just
> do if for the entire line without having to parse out each part and decode them
> separately.

Actually, even if we use just UTF-8, an MUA still has to parse the field, because:

- MUAs need to be able to read old messages (dating back to the 1980s at least),
  and for a sufficiently large customer base those old messages contain a mixture 
  of ASCII, RFC 2047, and other character sets without encoding. 

  I have code that attempts to handle ASCII, RFC 2047, ISO-2022-*, UTF-8, and
  a default 8-bit character set (if none of the above, assume something like 
  iso-8859-1) in a message header.  It's not terribly difficult, but you do have
  to bust up the header field into tokens before displaying it.

- There are other reasons completely unrelated to I18N that you might want to 
  parse the field.  If you're formatting the field for a different display width, 
  you can make the display more pleasing if you wrap long lines between addresses
  rather than at arbitrary token boundaries.  Also, it looks *much* better to remove
  redundant phrases and comments left there by brain-damaged mailers.  To take a 
  fairly common example:

  	To: "'moore@cs.utk.edu'" <moore@cs.utk.edu>

  displays much better as 

  	To: moore@cs.utk.edu

  Finally, if you are composing a "reply to all" it is a good idea to remove
  duplicate addresses that appear in (for example) both the From and To fields,
  so that they only appear once in the list of reply recipients.

  I suspect most MUAs already do have an address parser - they just don't 
  necessarily use it for display.
 
Keith



From owner-idn@ops.ietf.org  Tue May 29 09:43:11 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA01203
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 09:43:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154jZg-000OXp-00
	for idn-data@psg.com; Tue, 29 May 2001 06:30:16 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154jZf-000OXd-00
	for idn@ops.ietf.org; Tue, 29 May 2001 06:30:15 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA16766;
        Tue, 29 May 2001 09:30:03 -0400 (EDT)
Message-Id: <200105291330.JAA16766@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Adam M. Costello" <amc@cs.berkeley.edu>
cc: idn@ops.ietf.org
Subject: Re: [idn] Moving forward 
In-reply-to: Your message of "Tue, 29 May 2001 07:32:16 -0000."
             <20010529073216.G22313@arwen.cs.berkeley.edu> 
Date: Tue, 29 May 2001 09:30:03 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Yes, MTAs are already recommended not to alter messages, and that would
> still apply.
> 
> > It might be that more precise wording of your statement would address
> > this concern, though offhand I cannot suggest text that would do so.
> 
> I guess I should say that ACE decoding is permissible only when the
> sender of a protocol message knows that all recipients of that message
> (both direct and indirect) can handle it.  In the case of email headers,
> I don't see how the sender could know that.  But in the case of SMTP
> MAIL and RCPT commands, only the next-hop MTA receives those commands,
> so ACE decoding would be safe there.  Probably pointless though.

probably so, since users don't see this most of the time.  

also there is the potential for utf-8 IDNs to leak out in delivery status
notifications (DSNs) which expect addresses in ASCII.

> The reason I included this option in the model was to allow for the
> reduction of ACE-leakage.  

sure.  but utf-8 leakage is also a concern.  one guy's improvement
is another guy's leakage :)

> Example scenario:  After IDN is standardized,
> a new application protocol is defined that uses nameprep'd UTF-8.  Since
> this application talks only to itself, it doesn't bother implementing
> ACE decoding when displaying names to the user (it is recommended, but
> not required, to decode ACE); it just handles conversion of UTF-8 to the
> local charset.  That works fairly well until someone writes a gateway
> between this application and some other protocol.  Now it might be nice
> to put ACE decoding in the gateway, since the application doesn't do it
> itself.  This is safe because the gateway knows that this application
> handles UTF-8.

this would be fine.  but we usually don't specify the behavior of gateways.
there are too many details to track down for marginal cases.

Keith



From owner-idn@ops.ietf.org  Tue May 29 09:55:55 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA01287
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 09:55:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154jZg-000OXp-00
	for idn-data@psg.com; Tue, 29 May 2001 06:30:16 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154jZf-000OXd-00
	for idn@ops.ietf.org; Tue, 29 May 2001 06:30:15 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA16766;
        Tue, 29 May 2001 09:30:03 -0400 (EDT)
Message-Id: <200105291330.JAA16766@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Adam M. Costello" <amc@cs.berkeley.edu>
cc: idn@ops.ietf.org
Subject: Re: [idn] Moving forward 
In-reply-to: Your message of "Tue, 29 May 2001 07:32:16 -0000."
             <20010529073216.G22313@arwen.cs.berkeley.edu> 
Date: Tue, 29 May 2001 09:30:03 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Yes, MTAs are already recommended not to alter messages, and that would
> still apply.
> 
> > It might be that more precise wording of your statement would address
> > this concern, though offhand I cannot suggest text that would do so.
> 
> I guess I should say that ACE decoding is permissible only when the
> sender of a protocol message knows that all recipients of that message
> (both direct and indirect) can handle it.  In the case of email headers,
> I don't see how the sender could know that.  But in the case of SMTP
> MAIL and RCPT commands, only the next-hop MTA receives those commands,
> so ACE decoding would be safe there.  Probably pointless though.

probably so, since users don't see this most of the time.  

also there is the potential for utf-8 IDNs to leak out in delivery status
notifications (DSNs) which expect addresses in ASCII.

> The reason I included this option in the model was to allow for the
> reduction of ACE-leakage.  

sure.  but utf-8 leakage is also a concern.  one guy's improvement
is another guy's leakage :)

> Example scenario:  After IDN is standardized,
> a new application protocol is defined that uses nameprep'd UTF-8.  Since
> this application talks only to itself, it doesn't bother implementing
> ACE decoding when displaying names to the user (it is recommended, but
> not required, to decode ACE); it just handles conversion of UTF-8 to the
> local charset.  That works fairly well until someone writes a gateway
> between this application and some other protocol.  Now it might be nice
> to put ACE decoding in the gateway, since the application doesn't do it
> itself.  This is safe because the gateway knows that this application
> handles UTF-8.

this would be fine.  but we usually don't specify the behavior of gateways.
there are too many details to track down for marginal cases.

Keith



From owner-idn@ops.ietf.org  Tue May 29 09:57:42 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA01350
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 09:57:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154joD-000PDL-00
	for idn-data@psg.com; Tue, 29 May 2001 06:45:17 -0700
Received: from heron.verisign.com ([216.168.233.95])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154joC-000PBb-00
	for idn@ops.ietf.org; Tue, 29 May 2001 06:45:17 -0700
Received: from REGDOM-EX01.prod.netsol.com (rdex01-node1.prod.netsol.com [10.131.4.28])
	by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id JAA16143
	for <idn@ops.ietf.org>; Tue, 29 May 2001 09:44:45 -0400 (EDT)
Received: by regdom-ex01.prod.netsol.com with Internet Mail Service (5.5.2653.19)
	id <LGX50TZQ>; Tue, 29 May 2001 09:36:49 -0400
Message-ID: <DF737E620579D411A8E400D0B77E671D01877F62@regdom-ex01.prod.netsol.com>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: idn@ops.ietf.org
Subject: RE: [idn] report of the straw poll
Date: Tue, 29 May 2001 09:36:47 -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: Dave Crocker [mailto:dhc@dcrocker.net]
> Sent: Sunday, May 27, 2001 11:48 AM
> To: Hollenbeck, Scott
> Cc: idn@ops.ietf.org
> Subject: RE: [idn] report of the straw poll
> 
> 
> At 05:38 AM 5/26/2001, Hollenbeck, Scott wrote:
> > > From: James Seng/Personal [mailto:James@Seng.cc]
> > > Verisign is moving ahead to put RACE into their .COM zone 
> would means...
> >
> >Perhaps i-DNS should stop distributing *ACE toolkits if you have such
> >concerns about industry driven protocols.
> 
> 
> On the other hand, they are not contractors to ICANN, with a contractual 
> obligation to implement standards.
> 
> Verisign is.

The agreements between ICANN and VeriSign require VeriSign to enforce
specific name syntax restrictions which are not violated by any ACE
proposal.  There is no limitless obligation to "implement standards", but
even these limited restrictions provide a measure of protection to the WG
process that is not required of other entities involved in deploying IDN
technology.  The current lack of a consensus direction within the WG is
likely a greater threat to WG success than anything being done by any
company.

<Scott/>



From owner-idn@ops.ietf.org  Tue May 29 10:25:17 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA02286
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 10:25:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154kAl-000PxQ-00
	for idn-data@psg.com; Tue, 29 May 2001 07:08:35 -0700
Received: from mail.lysator.liu.se ([130.236.254.3])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154kAk-000PxJ-00
	for idn@ops.ietf.org; Tue, 29 May 2001 07:08:34 -0700
Received: from sandra.lysator.liu.se (sandra.lysator.liu.se [130.236.254.203])
	by mail.lysator.liu.se (Postfix) with ESMTP
	id 2F14782F4AD; Tue, 29 May 2001 16:08:32 +0200 (MET DST)
Received: from localhost (mag@localhost)
	by sandra.lysator.liu.se (8.9.0/8.8.7) with SMTP id QAA15920;
	Tue, 29 May 2001 16:08:31 +0200 (MET DST)
X-Authentication-Warning: sandra.lysator.liu.se: mag owned process doing -bs
Date: Tue, 29 May 2001 16:08:31 +0200 (MET DST)
From: C C Magnus Gustavsson <mag@lysator.liu.se>
To: "Adam M. Costello" <amc@cs.berkeley.edu>
Cc: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
In-Reply-To: <20010529033041.B22313@arwen.cs.berkeley.edu>
Message-ID: <Pine.GSO.4.00.10105291607250.15896-100000@sandra.lysator.liu.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Tue, 29 May 2001, Adam M. Costello wrote:

> I agree that there "should" be no problems, but there will be.  In my
> experience, copying text with the mouse usually gives you exactly what
> is displayed; very rarely does the application intercept the operation,
> because it's usually being handled entirely by the GUI library.

It's not the graphics but the encoded characters that are copied. If a
characters is available in the fonts does not make a difference.


> It's not obvious to me.  Someone (Keith?) mentioned archived mail.
> Should those addresses arbitrarily stop working someday?

They should not be archived as ACE in the first place. If they are,
they should be converted whenever possible.


> <offtopic> I rarely hear the phrase "English alphabet".  When I do, I
> think to myself, "There is no English alphabet.  English uses the Roman
> alphabet."  The phrase "Roman alphabet" is the more common name for the
> letters A-Z.  "English alphabet" sounds arrogant to me, since England
> merely inherited the alphabet from the Roman empire.  The most formally
> correct phrase might be "modern Roman alphabet". </offtopic>

I'm very sorry for keeping this off topic a little while longer but I
feel that statements as wrong as this should be corrected.

No, English does not use the Roman (or Latin) alphabet. English uses
an alphabet based on the Latin alphabet but so does numerous other
languages, each with a different set of characters. The Latin alphabet
contains 14 consonants (bcdfghlmnpqrst) and 5 vowels (aeiou). (It
might be argued that it's actually 16 consonants if we choose to count
j and v as separate letters from i and u, which the Romans did not.)

It might be that the phrase "Roman alphabet" is commonly used for the 
letters A-Z in the USA, but if so it's historically incorrect since
that is not the alphabet the Romans used. England did not only inherit
it's alphabet. It inherited it's language as well (although not from
Latin) and it evolved with time. Yet we call it the English language
to separate it from e g the related French and German languages. 

If anything is arrogant, it's using the term "modern Roman alphabet"
for the English alphabet. What makes it more modern or more Roman than
any of the other alphabets based on the Latin (e g the German)?

I suppose you don't believe me so to make sure I quote from my copy of
the Oxford Latin Dictionary (page v): "The Latin alphabet contains
fifteen consonants" and "It contains five vowels".

(They count v but not j as a separate character. I quote (page iii):
"While the letter 'i' is both a vowel and a consonant and thus there
is no 'j' in Latin, it unfortunately still appears necessary to make a
distinction between 'u' as a vowel (as in English) and as a consonant,
the latter being given as 'v'. This is unhistorical and philologically
unsound and it is hoped that before too long the letter 'v' can be
eradicated from this dictionary.")


Nosce te Latinum.

Now, can we please leave this topic?

/Magnus




From owner-idn@ops.ietf.org  Tue May 29 12:26:45 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA05402
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 12:26:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154ltf-0003Sb-00
	for idn-data@psg.com; Tue, 29 May 2001 08:59:03 -0700
Received: from jazz.viagenie.qc.ca ([206.123.31.2])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154lte-0003SV-00
	for idn@ops.ietf.org; Tue, 29 May 2001 08:59:02 -0700
Received: from CLASSIC.viagenie.qc.ca (classic.viagenie.qc.ca [206.123.31.136])
	by jazz.viagenie.qc.ca (Viagenie/8.11.0) with ESMTP id f4TGED177635
	for <idn@ops.ietf.org>; Tue, 29 May 2001 12:14:13 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <5.1.0.14.1.20010529115442.01eab018@mail.viagenie.qc.ca>
X-Sender: blanchet@mail.viagenie.qc.ca
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 29 May 2001 12:01:34 -0400
To: idn@ops.ietf.org
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: Re: [idn] report of the straw poll
In-Reply-To: <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

another (much more contentious, but I'm throwing it anyway) reading of the 
straw poll:
- in the disagree group, there is no concensus on alternatives.
- one would expect to vote for himself: i.e. I've not looked at who vote 
for what, but I could suspect interested parties to vote for their 
technology or their proposals.
- 3 disagree proposed nothing.

If one put aside the "vote for myself" and the "nothing proposed", then 
only 5 people remains and all propose some variant of UTF8.

compared to 36 participants who all agree on the same proposal.

So another reading of the results is maybe that we do have a "rough concensus".

controversial statement, right? Think about it before replying.

Before someone jump over me: I'm fairly neutral for the outcome of the wg 
orientation.

Marc.


At/À 08:38 2001-05-25 -0400, Marc Blanchet you wrote/vous écriviez:
>On Sun, 20 May 2001 09:51:31 -0400, an electronic straw poll was requested 
>by the idn co-chairs to reverify the previous concensus on 
>idna-nameprep-ace proposal. Those who disagree were asked to identify the 
>draft of the suggested alternative. The end of the poll was wednesday May 
>23rd 2001, 23h59 GMT.
>
>50 participants participated in the straw poll.
>
>36 participants agree with the idna-nameprep-ace orientation.
>
>14 participants disagree. In this group, here is a summary of the 
>suggested alternatives with the number of people in the front of each line:
>
>   1 UCS or UTF variants preferred
>   2 draft-skwan-utf8-dns-06.txt
>   2 Just send UTF
>
>   1 The DNSII Multilingual Domain Name Protocol
>   1 draft-ietf-idn-vidn-01.txt
>   1 draft-ietf-idn-uname-00.txt
>
>   2 draft-ietf-idn-udns, draft-ietf-idn-uname, draft-ietf-idn-idne, 
> draft-ietf-idn-iptr, draft-ietf-idn-vidn, draft-skwan-utf8-dns,
>      draft-klensin-dns-role
>   1 premature to decide before exploring alternatives
>
>   3 nothing proposed
>
>
>The counters group: Marc Blanchet, Dave Crocker, James Seng, Rick Wesson, 
>Yoshiro Yoneya
>
>
>





From owner-idn@ops.ietf.org  Tue May 29 12:36:17 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA05646
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 12:36:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154m3s-0003mv-00
	for idn-data@psg.com; Tue, 29 May 2001 09:09:36 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154m3s-0003mp-00
	for idn@ops.ietf.org; Tue, 29 May 2001 09:09:36 -0700
Received: from [165.227.249.18] (ip18.proper.com [165.227.249.18])
	by above.proper.com (8.9.3/8.9.3) with ESMTP id JAA27155
	for <idn@ops.ietf.org>; Tue, 29 May 2001 09:09:33 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100323b739767904cf@[165.227.249.18]>
In-Reply-To: <20010529042557.13041.qmail@cr.yp.to>
References: 
 <Pine.GSO.4.00.10105281945410.5818-100000@sandra.lysator.liu.se>
 <20010528191702.1600.qmail@cr.yp.to>
 <p0510030eb7389ab8633e@[165.227.249.18]>
 <20010529042557.13041.qmail@cr.yp.to>
Date: Tue, 29 May 2001 09:07:07 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] UTF-8 as the long-term IDN solution
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 4:25 AM +0000 5/29/01, D. J. Bernstein wrote:
>I suspect that we have consensus that the long-term IDN solution will
>encode Unicode characters as UTF-8 on the wire.

I suspect this is incorrect.

If ACE works for all the IDN strings we want, then there is no reason 
to do the second transition to UTF-8.

If ACE doesn't work for al the IDN strings we want, then it should 
not be deployed at all.

And, for those of you who are supporting the idea of the transition, 
please consider the companies and people who register names that are 
legal in ACE but illegal in UTF-8 because of the 63-octet limit on 
name parts. As has been pointed out here earlier, many ACEs compress 
some scripts better than UTF-8. Thus, if we do "ACE first then 
UTF-8", there will some names that are legal ACE and illegal UTF-8. 
Is this a good policy?

The reverse is also true: there are many names that will will fit in 
63 octets of UTF-8 that cannot fit in 63 octets of any of the ACEs 
proposed to date. Those names will be usable to some people (the ones 
who have made the transition) but not to the people who haven't. How 
is this transition supposed to work?

No transition is needed. Either we do ACE, or we do non-ACE. 
Currently, ACE seems to the be the strongly preferred solution in the 
WG.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Tue May 29 12:53:37 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA06138
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 12:53:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154mSe-0004c9-00
	for idn-data@psg.com; Tue, 29 May 2001 09:35:12 -0700
Received: from heron.verisign.com ([216.168.233.95])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154mSd-0004Zl-00
	for idn@ops.ietf.org; Tue, 29 May 2001 09:35:11 -0700
Received: from REGDOM-EX01.prod.netsol.com (rdex01-node1.prod.netsol.com [10.131.4.28])
	by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id MAA17175
	for <idn@ops.ietf.org>; Tue, 29 May 2001 12:34:40 -0400 (EDT)
Received: by regdom-ex01.prod.netsol.com with Internet Mail Service (5.5.2653.19)
	id <LGX504BQ>; Tue, 29 May 2001 12:26:44 -0400
Message-ID: <DF737E620579D411A8E400D0B77E671D01877F65@regdom-ex01.prod.netsol.com>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: idn@ops.ietf.org
Subject: RE: [idn] report of the straw poll
Date: Tue, 29 May 2001 12:26:34 -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: Marc Blanchet [mailto:Marc.Blanchet@viagenie.qc.ca]
>Sent: Tuesday, May 29, 2001 12:02 PM
>To: idn@ops.ietf.org
>Subject: Re: [idn] report of the straw poll
>
>
>another (much more contentious, but I'm throwing it anyway) 
>reading of the straw poll:
>- in the disagree group, there is no concensus on alternatives.
>- one would expect to vote for himself: i.e. I've not looked 
>at who vote 
>for what, but I could suspect interested parties to vote for their 
>technology or their proposals.
>- 3 disagree proposed nothing.
>
>If one put aside the "vote for myself" and the "nothing 
>proposed", then 
>only 5 people remains and all propose some variant of UTF8.
>
>compared to 36 participants who all agree on the same proposal.
>
>So another reading of the results is maybe that we do have a 
>"rough concensus".
>
>controversial statement, right? Think about it before replying.
>
>Before someone jump over me: I'm fairly neutral for the 
>outcome of the wg orientation.

After following all of the discussions since the results were announced I'm
not sure that the same results would be obtained if the question asked in
the straw poll had been phrased slightly differently.  A number of people
have stated that they didn't vote because they didn't care for either of the
two alternatives, so perhaps it would be better to ask a simple yes/no
question if your desire is to measure consensus for the IDNA proposal.  A
question similar to "Do you favor acceptance of the IDNA proposal?" leaves
little room for ambiguity and should allow everyone to vote one way or
another.  If "rough consensus" is defined by some measure of a majority
(simple?, 2.3?), then direction will be clear.  In the absense of rough
consensus it'll be back to discussing alternatives, but at least one
alternative will have been eliminated.

<Scott/>



From owner-idn@ops.ietf.org  Tue May 29 12:59:42 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA06474
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 12:59:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154mY8-0004n8-00
	for idn-data@psg.com; Tue, 29 May 2001 09:40:52 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154mY7-0004n2-00
	for idn@ops.ietf.org; Tue, 29 May 2001 09:40:51 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4TGeRf97732;
	Tue, 29 May 2001 12:40:27 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105291640.f4TGeRf97732@nic-naa.net>
To: Paul Hoffman / IMC <phoffman@imc.org>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] UTF-8 as the long-term IDN solution 
In-Reply-To: Your message of "Tue, 29 May 2001 09:07:07 PDT."
             <p05100323b739767904cf@[165.227.249.18]> 
Date: Tue, 29 May 2001 12:40:27 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Paul,

Just what was the point of having arch-2 in your comparison document?

Eric



From owner-idn@ops.ietf.org  Tue May 29 13:42:20 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA07731
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 13:42:20 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154n9T-00066g-00
	for idn-data@psg.com; Tue, 29 May 2001 10:19:27 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154n9T-00066a-00
	for idn@ops.ietf.org; Tue, 29 May 2001 10:19:27 -0700
Received: from [165.227.249.18] (ip18.proper.com [165.227.249.18])
	by above.proper.com (8.9.3/8.9.3) with ESMTP id KAA01466
	for <idn@ops.ietf.org>; Tue, 29 May 2001 10:19:24 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100330b73989477005@[165.227.249.18]>
In-Reply-To: <200105291640.f4TGeRf97732@nic-naa.net>
References: <200105291640.f4TGeRf97732@nic-naa.net>
Date: Tue, 29 May 2001 10:18:14 -0700
To: idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] UTF-8 as the long-term IDN solution
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 12:40 PM -0400 5/29/01, Eric Brunner-Williams in Portland Maine wrote:
>Just what was the point of having arch-2 in your comparison document?

arch-2 had been proposed in the WG, and the original idea for the 
comparison document was to cover all the proposals. Now that the 
number of proposals is huge, and the fact that many of the 
most-talked-about proposals don't have active Internet Drafts, and 
the fact that I have become a proponent of one of the solutions, and 
the fact that no one commented on the comparision document, I have 
given up on the document. The WG chairs may want to get someone who 
is neutral to keep it alive, but I'm not sure it is still useful.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-idn@ops.ietf.org  Tue May 29 14:55:00 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA09081
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 14:55:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154oLo-0008aE-00
	for idn-data@psg.com; Tue, 29 May 2001 11:36:16 -0700
Received: from 216-220-241-232.midmaine.com ([216.220.241.232] helo=nic-naa.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154oLn-0008a8-00
	for idn@ops.ietf.org; Tue, 29 May 2001 11:36:15 -0700
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1])
	by nic-naa.net (8.11.3/8.9.3) with ESMTP id f4TIZwf98179;
	Tue, 29 May 2001 14:35:58 -0400 (EDT)
	(envelope-from brunner@nic-naa.net)
Message-Id: <200105291835.f4TIZwf98179@nic-naa.net>
To: Paul Hoffman / IMC <phoffman@imc.org>
cc: idn@ops.ietf.org, brunner@nic-naa.net
Subject: Re: [idn] UTF-8 as the long-term IDN solution 
In-Reply-To: Your message of "Tue, 29 May 2001 10:18:14 PDT."
             <p05100330b73989477005@[165.227.249.18]> 
Date: Tue, 29 May 2001 14:35:58 -0400
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Paul,

The point isn't authorship of a document, it was the presentation of a
middle that wasn't fictive.

Eric



From owner-idn@ops.ietf.org  Tue May 29 15:25:17 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA09671
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 15:25:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154ovD-0009bL-00
	for idn-data@psg.com; Tue, 29 May 2001 12:12:51 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 154ovC-0009a9-00
	for idn@ops.ietf.org; Tue, 29 May 2001 12:12:50 -0700
Received: (qmail 32034 invoked by uid 1001); 29 May 2001 18:59:11 -0000
Date: 29 May 2001 18:59:11 -0000
Message-ID: <20010529185911.17254.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: [idn] How gethostbyname() handles 8-bit characters
References: <F599No5I9BADCDLTyHU0000f121@hotmail.com> <7544575.990957280@localhost> <20010527165903.5833.qmail@cr.yp.to> <079c01c0e6e4$3bf7ee50$7dcb15a5@jamessonyvaio> <20010527202613.5518.qmail@cr.yp.to> <083c01c0e6f7$235b7200$7dcb15a5@jamessonyvaio> <20010528043639.9273.qmail@cr.yp.to> <20010529033041.B22313@arwen.cs.berkeley.edu> <20010529045656.23237.qmail@cr.yp.to> <20010529052322.E22313@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:
> If gethostbyname() receives 8-bit text, should it assume that it's UTF-8,

The current gethostbyname() release (if you put no-check-names into
/etc/resolv.conf) simply copies the 8-bit bytes to the DNS packet. It
doesn't care about the interpretation of the bytes as characters.

If we make the obvious specification of 8-bit bytes in DNS as UTF-8, the
current gethostbyname() semantics will be consistent with two coherent
programming models:

   (1) The local character encoding might not be UTF-8. Higher-level
       routines are responsible for converting from the local character
       encoding to UTF-8 before calling gethostbyname(). It would be
       convenient to have a central routine that does this.

   (2) The local character encoding is UTF-8. No conversion is required
       in this case. This is simpler than #1, and it's wildly popular
       among programmers---dealing with multiple character encodings is
       a royal pain. UNIX is rapidly moving from #1 to #2.

There are other programming models that aren't consistent with the
current gethostbyname() semantics. This might be a sufficient reason to
berak compatibility if those models were as nice as #2, but they aren't.

---Dan



From owner-idn@ops.ietf.org  Tue May 29 16:07:13 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA10404
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 16:07:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154pTN-000AX5-00
	for idn-data@psg.com; Tue, 29 May 2001 12:48:09 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 154pTL-000AWu-00
	for idn@ops.ietf.org; Tue, 29 May 2001 12:48:08 -0700
Received: (qmail 7261 invoked by uid 1001); 29 May 2001 19:45:40 -0000
Date: 29 May 2001 19:45:40 -0000
Message-ID: <20010529194540.8982.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] Dots, and a path to working IDNs
References: <20010528211811.4490.qmail@cr.yp.to> <200105290545.BAA13806@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:
> For instance, it is one thing if typing the "bad" dots causes the
> lookup to fail; quite another if typing the "bad" dots causes a lookup
> for a completely different domain; and still another if the "bad" dots
> work differently in different clients.

I agree that having two different names, one using a good dot and one
using a bad dot, would be confusing for users. It would also mean that,
if we ever decided to move to ``bad dots are converted to good,'' we'd
break some working names. Disaster!

The current situation, however, is that the bad dot isn't used. So
neither problem happens. There's only one name. The worst case is a
failure, forcing the user to change the bad dot to a good dot.

My proposal is to do the same for IDNs. We can allow good UTF-8 IDNs,
and prohibit bad UTF-8 IDNs. Everything necessary to make this work is
something that we want to do anyway. Nothing has been lost if it turns
out that the users also need bad->good conversion.

> we would like to avoid having millions of programs upgraded only to
> find out that their IDN support is buggy and that (for instance)
> people can't reliably use certain IDNs with certain clients, and that
> there will be yet another massive upgrade

Aha---you're missing a basic point. My plan is compatible with bad->good
conversion: bad IDNs will be prohibited on the wire. If a programmer has
time to do all the work necessary for bad->good conversion, then he can
do that and deploy it. Nothing in my plan slows him down.

What I'm trying to do is make IDNs work as soon as possible. We already
have widespread support for UTF-8 in existing programs. We can take
advantage of this---as many people already have---to get UTF-8 IDNs.

Yes, it's possible that simple UTF-8 IDNs won't be as good as UTF-8 IDNs
with bad->good conversion in thosuands of programs. But they're clearly
much better than no IDNs at all. We can still add bad->good conversion;
we simply have to make sure to prohibit bad IDNs on the wire.

> it strikes me as far more difficult to get platforms to create a
> special input mode for IDNs,

The worst case is exactly what Adam has been proposing for ACE: a
separate little IDN tool, added on to the OS, that reads input from the
user and prints a good IDN.

> we already know of instances where the UTF-8 support isn't good enough.

What are you talking about?

---Dan



From owner-idn@ops.ietf.org  Tue May 29 16:26:32 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA10642
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 16:26:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154ppC-000BGC-00
	for idn-data@psg.com; Tue, 29 May 2001 13:10:42 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 154ppB-000BG6-00
	for idn@ops.ietf.org; Tue, 29 May 2001 13:10:41 -0700
Received: (qmail 15569 invoked by uid 1001); 29 May 2001 20:07:12 -0000
Date: 29 May 2001 20:07:12 -0000
Message-ID: <20010529200712.15401.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 as the long-term IDN solution
References: <Pine.GSO.4.00.10105281945410.5818-100000@sandra.lysator.liu.se> <20010528191702.1600.qmail@cr.yp.to> <p0510030eb7389ab8633e@[165.227.249.18]> <20010529042557.13041.qmail@cr.yp.to> <p05100323b739767904cf@[165.227.249.18]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Paul Hoffman / IMC writes:
> If ACE works for all the IDN strings we want, then there is no reason 
> to do the second transition to UTF-8.

Consider a programmer writing network software five years from now, or
ten years from now.

He'll be working with text in UTF-8. But wait, you say, he has to
convert to some screwy ACE format on the wire. When he asks why all the
Internet protocols have this strange complication, you mumble something
about ancient versions of Sendmail that didn't support 8-bit text.

So he'll have to deal with ACE, taking time away from implementing new
features that users actually want.

You should be ashamed of yourself.

---Dan



From owner-idn@ops.ietf.org  Tue May 29 16:32:16 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA10718
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 16:32:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154pvN-000BUX-00
	for idn-data@psg.com; Tue, 29 May 2001 13:17:05 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 154pvN-000BUR-00
	for idn@ops.ietf.org; Tue, 29 May 2001 13:17:05 -0700
Received: (qmail 28453 invoked by uid 1001); 29 May 2001 20:15:56 -0000
Date: 29 May 2001 20:15:56 -0000
Message-ID: <20010529201556.19799.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
References: <200105280227.WAA00791@astro.cs.utk.edu> <20010527213052.C17337@arwen.cs.berkeley.edu> <200105280200.WAA00572@astro.cs.utk.edu> <20010527202613.5518.qmail@cr.yp.to> <200105280114.VAA00203@astro.cs.utk.edu> <20010527165903.5833.qmail@cr.yp.to> <200105280106.VAA29976@astro.cs.utk.edu> <20010528050943.16457.qmail@cr.yp.to> <0a9c01c0e745$32399c90$7dcb15a5@jamessonyvaio> <02d801c0e828$9041a150$dd00a8c0@jamessonyvaio>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James Seng/Personal writes:
> What is considered a "bad names"?

Read the page: ``An uppercase ... is guaranteed to cause confusion: when
the uppercase Alpha is printed properly, it looks just like an uppercase
A. Some other strings are also guaranteed to cause confusion. There's a
complicated definition of good names among all Unicode strings. Good
names won't be confused with each other. Registrars won't allow
registration of bad names.''

Good names are the same concept as the output of nameprep, except that
the current nameprep specification is flawed---it doesn't handle Alpha,
for example.

> Lets expand this to any non-UTF-8 applications which uses Domain Names.

No. The issue is specific to text-mode programs that need to know the
width of their output, such as full-screen tty MUAs. A few of these
programs don't support UTF-8 yet.

> It is too early to suspect how I18N Email will look like to decide
> what changes would be required in sendmail but I suspect making it 8-bit
> clean as you suggested here is probably needed if UTF-8 are use in IDN.

You are confused. The changes I specified are necessary and sufficient.

> But most important of all, you left out the needs to 'patch/replace' the
> keyboard

No, I didn't leave it out. Read the page.

---Dan



From owner-idn@ops.ietf.org  Tue May 29 21:06:10 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA13435
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 21:06:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154u3I-000GmL-00
	for idn-data@psg.com; Tue, 29 May 2001 17:41:32 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154u3H-000GmF-00
	for idn@ops.ietf.org; Tue, 29 May 2001 17:41: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 UAA22410;
        Tue, 29 May 2001 20:41:28 -0400 (EDT)
Message-Id: <200105300041.UAA22410@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Paul Hoffman / IMC <phoffman@imc.org>
cc: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 as the long-term IDN solution 
In-reply-to: Your message of "Tue, 29 May 2001 09:07:07 PDT."
             <p05100323b739767904cf@[165.227.249.18]> 
Date: Tue, 29 May 2001 20:41:28 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> And, for those of you who are supporting the idea of the transition,
> please consider the companies and people who register names that are
> legal in ACE but illegal in UTF-8 because of the 63-octet limit on
> name parts.

That's an interesting point.  However, I expect that we'll need some 
DNS exetnsion to do UTF-8 anyway.  Might such an extension allow us to
do away with the 63 octet limit?

Keith



From owner-idn@ops.ietf.org  Tue May 29 21:13:19 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA13505
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 21:13:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154uEE-000Grj-00
	for idn-data@psg.com; Tue, 29 May 2001 17:52:50 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154uED-000GrV-00
	for idn@ops.ietf.org; Tue, 29 May 2001 17:52:49 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id UAA22552;
        Tue, 29 May 2001 20:52:46 -0400 (EDT)
Message-Id: <200105300052.UAA22552@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] UTF-8 as the long-term IDN solution 
In-reply-to: Your message of "29 May 2001 20:07:12 -0000."
             <20010529200712.15401.qmail@cr.yp.to> 
Date: Tue, 29 May 2001 20:52:46 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> He'll be working with text in UTF-8. But wait, you say, he has to
> convert to some screwy ACE format on the wire. 

yes, but there will be a library routine for that.  the programmer
will still have to deal with it, but it's not much worse than 
the effort that would otherwise be required to deal reasonably 
with message headers.

do you really think we'll be using a paper-tape I/O model 10 years 
from now?  even on UNIX?  maybe we will - it's endured a long time -
but I wouldn't bet the farm on it.

> When he asks why all the
> Internet protocols have this strange complication, you mumble something
> about ancient versions of Sendmail that didn't support 8-bit text.

no, that's what *you* would say.  the rest of us might mumble something
about the need for backward compatibility with ASCII mail standards,
because we understand that sendmail is not the source of the problem.

Keith

p.s. if and when qmail has been around for 20+ years,  and if it still 
has significant popularity, some young upstart is going to trash your
code for being shortsighted and brain-damaged.  and you are not going
to want to rewrite qmail - because you will have spent too much sweat
on it and fought too many interoperability battles for that code to 
give up on it, and those things that you did to make the code ugly
will seem (even in hindsight) to have been perfectly defensible at the 
time.



From owner-idn@ops.ietf.org  Tue May 29 21:29:38 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA13645
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 21:29:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154uS2-000H9P-00
	for idn-data@psg.com; Tue, 29 May 2001 18:07:06 -0700
Received: from songbird.com
	([208.184.79.7] helo=joy.songbird.com ident=root)
	by psg.com with esmtp (Exim 3.16 #1)
	id 154uS1-000H9A-00
	for idn@ops.ietf.org; Tue, 29 May 2001 18:07:05 -0700
Received: from bbdesk.dcrocker.net (c1193160-a.snvl1.sfba.home.com [65.0.152.112])
	by joy.songbird.com (8.9.3/8.9.3) with ESMTP id SAA11187
	for <idn@ops.ietf.org>; Tue, 29 May 2001 18:07:03 -0700
Message-Id: <5.1.0.14.2.20010529175754.04eb52f8@dcrocker.net>
X-Sender: dhc@brandenburg.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 29 May 2001 18:04:00 -0700
To: idn@ops.ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: [idn] UTF-8 as the long-term IDN solution
In-Reply-To: <20010529200712.15401.qmail@cr.yp.to>
References: <Pine.GSO.4.00.10105281945410.5818-100000@sandra.lysator.liu.se>
 <20010528191702.1600.qmail@cr.yp.to>
 <p0510030eb7389ab8633e@[165.227.249.18]>
 <20010529042557.13041.qmail@cr.yp.to>
 <p05100323b739767904cf@[165.227.249.18]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 01:07 PM 5/29/2001, D. J. Bernstein wrote:
>He'll be working with text in UTF-8. But wait, you say, he has to
>convert to some screwy ACE format on the wire.

It's true.  Practical standards are really a drag.

We should change them every year... no, that won't be quick enough.

Let's say every 3 months, to reflect all of the most modern changes in 
technical practise.

Each 3 months, it will of course be obvious what the new practises, 5 years 
from now, will be.

After all, we all have such a good track record when predicting the future, 
don't we.  In 1992 we were assured that Unicode was instantly going to be 
in mass use, for example.

But wait.  It takes years to adopt and deploy a standard.  That means that 
we will never have any stability, since we will be spending all our time 
revising everything to be infinitely current.

After all, look how much better the computer science purity of X.400 was, 
over the clearly atrocious -- and by the way, I'm not kidding -- 
RFC822/RFC821 suite.


>You should be ashamed of yourself.

Dan, please stop talking to yourself outloud.  Try listening and you might 
learn something.

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 May 29 21:41:10 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA14727
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 21:41:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154unK-000HnQ-00
	for idn-data@psg.com; Tue, 29 May 2001 18:29:06 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154unJ-000HnJ-00
	for idn@ops.ietf.org; Tue, 29 May 2001 18:29:06 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 22600FFC05; Wed, 30 May 2001 09:31:40 +0800 (SGT)
Message-ID: <039101c0e8a7$d5318a30$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, <idn@ops.ietf.org>
References: <DF737E620579D411A8E400D0B77E671D01877F62@regdom-ex01.prod.netsol.com>
Subject: Re: [idn] report of the straw poll
Date: Wed, 30 May 2001 09:28:29 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

How true...especially when we are thrashing old arguments over and over
again...

-James Seng

> The current lack of a consensus direction within the WG is
> likely a greater threat to WG success than anything being done by any
> company.





From owner-idn@ops.ietf.org  Tue May 29 21:42:05 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA14744
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 21:42:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154umk-000HmQ-00
	for idn-data@psg.com; Tue, 29 May 2001 18:28:30 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154umj-000HmJ-00
	for idn@ops.ietf.org; Tue, 29 May 2001 18:28:29 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id VAA22811;
        Tue, 29 May 2001 21:28:27 -0400 (EDT)
Message-Id: <200105300128.VAA22811@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] Dots, and a path to working IDNs 
In-reply-to: Your message of "29 May 2001 19:45:40 -0000."
             <20010529194540.8982.qmail@cr.yp.to> 
Date: Tue, 29 May 2001 21:28:26 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Keith Moore writes:
> > For instance, it is one thing if typing the "bad" dots causes the
> > lookup to fail; quite another if typing the "bad" dots causes a lookup
> > for a completely different domain; and still another if the "bad" dots
> > work differently in different clients.
> 
> I agree that having two different names, one using a good dot and one
> using a bad dot, would be confusing for users. It would also mean that,
> if we ever decided to move to ``bad dots are converted to good,'' we'd
> break some working names. Disaster!
> 
> The current situation, however, is that the bad dot isn't used. So
> neither problem happens. There's only one name. 

Right.  So one way to prevent this ambiguity is to encourage applications 
to refuse to accept domain names containing "bad" dots.  That way, there
won't be any market for them. (Another way is to encourage DNS servers
to complain when they find bad dots in their zone files.)

> My proposal is to do the same for IDNs. We can allow good UTF-8 IDNs,
> and prohibit bad UTF-8 IDNs. Everything necessary to make this work is
> something that we want to do anyway. Nothing has been lost if it turns
> out that the users also need bad->good conversion.

I think that's right - the crucial question being: what is the mechanism
for "prohibiting" bad IDNs?

(note that this is completely orthogonal to whether UTF-8 or ACE is used)
 
> > we would like to avoid having millions of programs upgraded only to
> > find out that their IDN support is buggy and that (for instance)
> > people can't reliably use certain IDNs with certain clients, and that
> > there will be yet another massive upgrade
> 
> Aha---you're missing a basic point. My plan is compatible with bad->good
> conversion: bad IDNs will be prohibited on the wire. If a programmer has
> time to do all the work necessary for bad->good conversion, then he can
> do that and deploy it. Nothing in my plan slows him down.

I think the difficulty is ensuring that we've identified all or most
"bad" IDNs before we deploy the code that prohibits them.  Again, we
have this difficulty regardless of the encoding that is used on the wire.

> What I'm trying to do is make IDNs work as soon as possible. 

I think we share that goal, but we favor different strategies for getting 
there.  One difference may be in how we define what it means for IDNs
to "work".  Another difference may be in our assumptions about when and to 
what extent people will be willing to upgrade their existing software.

> We already
> have widespread support for UTF-8 in existing programs. We can take
> advantage of this---as many people already have---to get UTF-8 IDNs.

But there are risks and costs associated with going down this path -
if the results are inconsistent (either from one application to another
or from one operating environment to another) or unpredictable, if they 
won't work well for some important languages, of if they preclude or 
delay deployment of a better solution that does work well for most languages.

> Yes, it's possible that simple UTF-8 IDNs won't be as good as UTF-8 IDNs
> with bad->good conversion in thosuands of programs. But they're clearly
> much better than no IDNs at all. 

I'm not sure that this is "clearly" the case.  When we know that there 
are significant problems with the simple approach for some languages, or
if we're pretty sure that the simple approach won't work well for very
long, it's sort of irresponsible for us to encourage people to follow
that approach - even if a few vendors have (irresponsibly?) shipped code
that assumes that approach.

Put another way, an IETF WG's job is not to endorse quick fixes, but to 
figure out what will work well in the medium to long term.  That doesn't 
mean that vendors cannot deploy short-term fixes, but we believe that
for a solution to be worth the massive deployment effort, it needs to
work well for a long time and for the vast majority of users.  We cannot
accept limitations in an IETF solution that a vendor might accept in a
short-term solution.  If we cannot do better than the short-term approach, 
we  shouldn't be wasting our time - the vendor community doesn't need 
IETF to bless something that already works well.  It's precisely because 
the quick and easy solutions do not work well that we are engaged in this 
effort.

> > it strikes me as far more difficult to get platforms to create a
> > special input mode for IDNs,
> 
> The worst case is exactly what Adam has been proposing for ACE: a
> separate little IDN tool, added on to the OS, that reads input from the
> user and prints a good IDN.

I didn't see Adam's proposal as anything more than a workaround for expert
users of UNIX.  The vast majority of users out there would not use such
a tool regardless of whether it emitted ACE or UTF-8.
 
> > we already know of instances where the UTF-8 support isn't good enough.
> 
> What are you talking about?

We already know that different systems generate different representations
of the same characters, even when the users try to generate the same 
characters,  and that this isn't fixed by the currently-deployed software 
that just sends UTF-8. 

Keith



From owner-idn@ops.ietf.org  Tue May 29 22:01:05 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA14896
	for <idn-archive@lists.ietf.org>; Tue, 29 May 2001 22:01:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 154v5G-000Hyz-00
	for idn-data@psg.com; Tue, 29 May 2001 18:47:38 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 154v5E-000Hyt-00
	for idn@ops.ietf.org; Tue, 29 May 2001 18:47:37 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id 47185FFC04; Wed, 30 May 2001 09:50:11 +0800 (SGT)
Message-ID: <03f201c0e8aa$6b772a70$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
References: <200105280227.WAA00791@astro.cs.utk.edu> <20010527213052.C17337@arwen.cs.berkeley.edu> <200105280200.WAA00572@astro.cs.utk.edu> <20010527202613.5518.qmail@cr.yp.to> <200105280114.VAA00203@astro.cs.utk.edu> <20010527165903.5833.qmail@cr.yp.to> <200105280106.VAA29976@astro.cs.utk.edu> <20010528050943.16457.qmail@cr.yp.to> <0a9c01c0e745$32399c90$7dcb15a5@jamessonyvaio> <02d801c0e828$9041a150$dd00a8c0@jamessonyvaio> <20010529201556.19799.qmail@cr.yp.to>
Subject: Re: [idn] UTF-8 / RACE
Date: Wed, 30 May 2001 09:47:01 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

> Read the page: ``An uppercase ... is guaranteed to cause confusion:
when
> the uppercase Alpha is printed properly, it looks just like an
uppercase
> A. Some other strings are also guaranteed to cause confusion. There's
a
> complicated definition of good names among all Unicode strings. Good
> names won't be confused with each other. Registrars won't allow
> registration of bad names.''

So you mean I could only have "françious" but could never "FRANÇIOUS"?
What if due to my personal preference/trademark, I want to have
uppercase char? To draw an english analogy, try "IBM" or "eBay" or "AOL"
or ...

> Good names are the same concept as the output of nameprep, except that
> the current nameprep specification is flawed---it doesn't handle
Alpha,
> for example.

In other words, there would be a routine to create 'good' names. It may
be less complex than the current Nameprep but there will be.

> > It is too early to suspect how I18N Email will look like to decide
> > what changes would be required in sendmail but I suspect making it
8-bit
> > clean as you suggested here is probably needed if UTF-8 are use in
IDN.
>
> You are confused. The changes I specified are necessary and
sufficient.

I dont think I am confused. I am just not ready to do I18N Email right
now.
Your current implict proposal is to do it by pushing UTF-8 thru SMTP and
I am not ready to conclude this is right way.

> > But most important of all, you left out the needs to 'patch/replace'
the
> > keyboard
>
> No, I didn't leave it out. Read the page.

Okay. My mistake. IMHO, this would be the greatest pain of all to go
thru...

-James Seng




From owner-idn@ops.ietf.org  Wed May 30 03:47:04 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA03221
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 03:47:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1550Nx-000LQZ-00
	for idn-data@psg.com; Wed, 30 May 2001 00:27:17 -0700
Received: from epa.secret.org ([206.220.140.150] ident=0)
	by psg.com with esmtp (Exim 3.16 #1)
	id 1550Nw-000LQP-00
	for idn@ops.ietf.org; Wed, 30 May 2001 00:27:16 -0700
Received: from localhost (lucid@localhost)
	by epa.secret.org (8.9.3/8.9.1) with ESMTP id DAA03756;
	Wed, 30 May 2001 03:27:03 -0400 (EDT)
Date: Wed, 30 May 2001 03:27:03 -0400 (EDT)
From: lucid@epa.secret.org
To: James Seng/Personal <James@Seng.cc>
cc: "D. J. Bernstein" <djb@cr.yp.to>, idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
In-Reply-To: <03f201c0e8aa$6b772a70$dd00a8c0@jamessonyvaio>
Message-ID: <Pine.BSF.4.10.10105300259190.3537-100000@epa.secret.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk



On Wed, 30 May 2001, James Seng/Personal wrote:
> > > But most important of all, you left out the needs to 'patch/replace'
> the
> > > keyboard
> >
> > No, I didn't leave it out. Read the page.
> 
> Okay. My mistake. IMHO, this would be the greatest pain of all to go
> thru...
> 
> -James Seng
> 

I belive the hardest problem is upgrading the end users. Please try and
keep in mind that whatever the solution, the greatest pain will probably
be compatibility issues between the computer and the user.

The sysadmins and support techs will be the ones dealing with these
compatability issues. Dont make our lives harder.

Please.

-Bill




From owner-idn@ops.ietf.org  Wed May 30 05:36:43 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA04214
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 05:36:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1551Sk-000MDV-00
	for idn-data@psg.com; Wed, 30 May 2001 01:36:18 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 1551Si-000MDP-00
	for idn@ops.ietf.org; Wed, 30 May 2001 01:36:17 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP id A8E3BFFC04
	for <idn@ops.ietf.org>; Wed, 30 May 2001 16:38:49 +0800 (SGT)
Message-ID: <08ab01c0e8e3$811d3890$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: <idn@ops.ietf.org>
Subject: [idn] IDN Panel at INET'2001
Date: Wed, 30 May 2001 16:35:38 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Marc and myself are chairing a IETF track panel on IDN at INET'2001. 
Our panel is held on Thrusday 7th June, 11:00 to 12:30pm. For details,
please refer to http://www.isoc.org/inet2001/F_IETF.shtml#i-3

For those attending INET'2001, please come and join us.

-James Seng




From owner-idn@ops.ietf.org  Wed May 30 05:43:24 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA04271
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 05:43:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1552EE-000MRY-00
	for idn-data@psg.com; Wed, 30 May 2001 02:25:22 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 1552EC-000MRR-00
	for idn@ops.ietf.org; Wed, 30 May 2001 02:25:21 -0700
Received: from jamessonyvaio (unknown [203.126.116.227])
	by mail.i-dns.net (Postfix) with SMTP
	id F21B9FFC05; Wed, 30 May 2001 17:27:54 +0800 (SGT)
Message-ID: <0b1601c0e8ea$5c97d6e0$dd00a8c0@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: <lucid@epa.secret.org>
Cc: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
References: <Pine.BSF.4.10.10105300259190.3537-100000@epa.secret.org>
Subject: Re: [idn] UTF-8 / RACE
Date: Wed, 30 May 2001 17:24:43 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> On Wed, 30 May 2001, James Seng/Personal wrote:
> > Okay. My mistake. IMHO, this would be the greatest pain of all to go
> > thru...

Actually "all" refers to the list of things Dan listed in his website
which needs to be change to handle Fast-Nameprep-UTF8.

> I belive the hardest problem is upgrading the end users. Please try
and
> keep in mind that whatever the solution, the greatest pain will
probably
> be compatibility issues between the computer and the user.
>
> The sysadmins and support techs will be the ones dealing with these
> compatability issues. Dont make our lives harder.
>
> Please.

Any suggestions or ideas how we can make it easiler? I am curious to
know...

If I am a tech support guy in Europe, and some users calls me up over
the phone asking me how to access his Korean domain names, I probably
freak out anyway. (Yes, it does not matter how slowly he speaks in
korean :-).

-James Seng




From owner-idn@ops.ietf.org  Wed May 30 09:30:08 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA10055
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 09:30:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1555aU-000Oez-00
	for idn-data@psg.com; Wed, 30 May 2001 06:00:34 -0700
Received: from bailey.dscga.com ([198.78.9.11])
	by psg.com with esmtp (Exim 3.16 #1)
	id 1555aS-000OeW-00
	for idn@ops.ietf.org; Wed, 30 May 2001 06:00:33 -0700
Received: (from michael@localhost) by bailey.dscga.com (8.9.1/) id IAA28388 for idn@ops.ietf.org; Wed, 30 May 2001 08:56:37 -0400 (EDT)
Date: Wed, 30 May 2001 08:56:37 -0400
From: Michael Mealling <michael@neonym.net>
To: idn@ops.ietf.org
Subject: [idn] suggested reading.....
Message-ID: <20010530085637.E27001@bailey.dscga.com>
Reply-To: Michael Mealling <michael@neonym.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.1.2i
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Everyone involved in the IDN effort should read John Klensin's latest drafts.
IMHO, they represent a much more logical approach:

A Search-based access model for the DNS
http://www.ietf.org/internet-drafts/draft-klensin-dns-search-00.txt

Role of the Domain Name System
http://www.ietf.org/internet-drafts/draft-klensin-dns-role-01.txt

Internationalizing the DNS -- A New Class
http://www.ietf.org/internet-drafts/draft-klensin-i18n-newclass-00.txt

-MM

-- 
--------------------------------------------------------------------------------
Michael Mealling	|      Vote Libertarian!       | urn:pin:1
michael@neonym.net      |                              | http://www.neonym.net
                        |                              | go:Michael Mealling



From owner-idn@ops.ietf.org  Wed May 30 09:30:13 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA10067
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 09:30:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1555mf-000Onn-00
	for idn-data@psg.com; Wed, 30 May 2001 06:13:09 -0700
Received: from ns.jck.com ([209.187.148.211] helo=A4.JCK.COM)
	by psg.com with esmtp (Exim 3.16 #1)
	id 1555me-000Ong-00
	for idn@ops.ietf.org; Wed, 30 May 2001 06:13:09 -0700
Received: from P2 ("port 2002"@[209.187.148.217])
 by a4.jck.com (PMDF V6.0-24 #44844) with ESMTP id <0GE5000MMGPVNJ@a4.jck.com>
 for idn@ops.ietf.org; Wed, 30 May 2001 09:13:07 -0400 (EDT)
Date: Wed, 30 May 2001 09:13:05 -0400
From: John C Klensin <klensin@jck.com>
Subject: Re: [idn] UTF-8 / RACE
In-reply-to: <0b1601c0e8ea$5c97d6e0$dd00a8c0@jamessonyvaio>
To: James Seng/Personal <James@Seng.cc>
Cc: idn@ops.ietf.org
Message-id: <3371507350.991213985@P2>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.8 (Win32)
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, 30 May, 2001 17:24 +0800 "James Seng/Personal"
<James@Seng.cc> wrote:

>> I belive the hardest problem is upgrading the end users.
>> Please try
> and
>> keep in mind that whatever the solution, the greatest pain
>> will
> probably
>> be compatibility issues between the computer and the user.
>> 
>> The sysadmins and support techs will be the ones dealing with
>> these compatability issues. Dont make our lives harder.
>> 
>> Please.
> 
> Any suggestions or ideas how we can make it easiler? I am
> curious to know...
> 
> If I am a tech support guy in Europe, and some users calls me
> up over the phone asking me how to access his Korean domain
> names, I probably freak out anyway. (Yes, it does not matter
> how slowly he speaks in korean :-).

James,

I think this is illustrative of one of the key problems, and is
tied to the reason why I no longer believe in a "class=IN"
DNS-based solution.  I believe that the only thing that helps
that tech support person is for the call to never occur, and
that means we have to engineer protocols and user interfaces to
do the right thing in the marginal cases.  I was taught many
years ago that the key to software that is perceived by users as
effective, easy-to-use, and reliable is to figure out all of the
failure cases (actual errors and having the computer do
something different from what the user expected) and then design
backward from those cases to make sure that reasonable things
happened.

The case (to use your example) of a Korean-speaking user,
sitting in Korea and connected to a Korean ISP, in front of a
Korean workstation, accessing a site in the KR domain, and
(obviously) with Korean-speaking tech support, is always going
to be the easiest one (although a DNS solution may still not be
adequate if fuzzy search or keywords/hint are needed). There are
a whole range of approaches that will "work" or appear to work
(even though some of them are Internet- fragmenting, etc.).

The hard problems all arise when some of those assumptions are
not met.  The person speaking a particular language in a country
where another one dominates, accessing a largely
internationalized domain from a different one, using client
software that does not provide for the relevant language, etc.,
is in more or less big trouble, and "call tech support" may just
result in additional frustration.  

Clearly, seeing the Korean characters through a user agent that
understands how to handle them is the best solution, especially
if they are supplemented by language-switchable help files and
hint mechanisms.  If that is not possible, it is an open
question as to whether seeing an untranslated ACE or a
collection of "undisplayable character" glyphs is likely to
cause the greater frustration.  There is even a strong case that
the best answer is to get a clear "undisplayable international
domain name -- upgrade your user agent software or install a
shim" message rather than any failing approximations at the
display.  And, of course, such mechanisms are aided by a clear
separation between "legacy" and "internationalized" systems,
rather that tricking the existing DNS (and class) into carrying
non-LDH names or names with non-LDH interpretations.

    john




From owner-idn@ops.ietf.org  Wed May 30 13:42:35 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA19343
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 13:42:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 1559lC-00025U-00
	for idn-data@psg.com; Wed, 30 May 2001 10:27:54 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 1559lB-00025J-00
	for idn@ops.ietf.org; Wed, 30 May 2001 10:27:53 -0700
Received: (qmail 28183 invoked by uid 1001); 30 May 2001 17:18:09 -0000
Date: 30 May 2001 17:18:09 -0000
Message-ID: <20010530171809.10756.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 as the long-term IDN solution
References: <20010529200712.15401.qmail@cr.yp.to> <200105300052.UAA22552@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:
> do you really think we'll be using a paper-tape I/O model 10 years 
> from now?  even on UNIX?  maybe we will - it's endured a long time -
> but I wouldn't bet the farm on it.

Ever heard of TCP? Byte streams aren't going away.

> p.s. if and when qmail has been around for 20+ years,  and if it still 
> has significant popularity, some young upstart is going to trash your
> code for being shortsighted and brain-damaged.

It has been around for more than 5 years. It hasn't needed any syntax
extensions except to work around bugs in other software (space after
MAIL FROM, for example). If it turns out someday that I haven't planned
ahead far enough, I'll make whatever changes are necessary.

For comparison: In February 1999, when it became clear that the revised
USENET message header field format was going to allow unencoded UTF-8, I
explained to Eric Allman how to make sendmail 8-bit-clean. (USENET
messages are often forwarded through mail by 8-bit-clean gateways.) A
few days ago, he released another security-fix release of sendmail. It
still isn't 8-bit-clean.

---Dan



From owner-idn@ops.ietf.org  Wed May 30 14:29:11 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA20711
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 14:29:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155AOs-0002UE-00
	for idn-data@psg.com; Wed, 30 May 2001 11:08:54 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 155AOr-0002Tk-00
	for idn@ops.ietf.org; Wed, 30 May 2001 11:08:53 -0700
Received: (qmail 26947 invoked by uid 1001); 30 May 2001 17:49:31 -0000
Date: 30 May 2001 17:49:31 -0000
Message-ID: <20010530174931.15520.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] Dots, and a path to working IDNs
References: <20010529194540.8982.qmail@cr.yp.to> <200105300128.VAA22811@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 again complains that UTF-8 might not ``work well for some
important languages.'' I think it would be a complete waste of time to
discuss this; the world has settled on UTF-8. I again ask the WG chairs
to run a poll to see whether we have consensus that the long-term IDN
solution will encode Unicode characters as UTF-8 on the wire.

Keith Moore writes:
> So one way to prevent this ambiguity is to encourage applications 
> to refuse to accept domain names containing "bad" dots.  That way,
> there won't be any market for them.

Probably bad->good conversion is just as easy as rejecting bad names, if
the application is going to be upgraded anyway. The mere threat should
be enough to dissuade people from trying to use bad names.

> One difference may be in how we define what it means for IDNs to "work".

http://cr.yp.to/proto/idn.html: ``We want to let people use domain names
like ... (`alpha beta gamma dot com'). They should be able to register
the name, set up computers under the name, connect to those computers by
name, set up web pages under the name, set up links to those web pages,
browse those web pages given the name or a link, send email from an
address under the name, receive email at that address, etc.''

> Another difference may be in our assumptions about when and to 
> what extent people will be willing to upgrade their existing software.

The crucial advantage of the plan I've described is that we _don't_ have
to wait for massive software upgrades before deploying IDNs. We can take
advantage of widespread UTF-8 support in existing software.

If it turns out that users won't be completely happy without the slow,
painful nameprep-in-every-program updates, then nothing has been lost.
There won't be any transition problems, because bad IDNs won't exist.

---Dan



From owner-idn@ops.ietf.org  Wed May 30 14:52:08 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA21354
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 14:52:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155AZP-0002bU-00
	for idn-data@psg.com; Wed, 30 May 2001 11:19:47 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 155AZO-0002bM-00
	for idn@ops.ietf.org; Wed, 30 May 2001 11:19:46 -0700
Received: (qmail 11622 invoked by uid 1001); 30 May 2001 17:58:53 -0000
Date: 30 May 2001 17:58:53 -0000
Message-ID: <20010530175853.22560.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
References: <200105280200.WAA00572@astro.cs.utk.edu> <20010527202613.5518.qmail@cr.yp.to> <200105280114.VAA00203@astro.cs.utk.edu> <20010527165903.5833.qmail@cr.yp.to> <200105280106.VAA29976@astro.cs.utk.edu> <20010528050943.16457.qmail@cr.yp.to> <0a9c01c0e745$32399c90$7dcb15a5@jamessonyvaio> <02d801c0e828$9041a150$dd00a8c0@jamessonyvaio> <20010529201556.19799.qmail@cr.yp.to> <03f201c0e8aa$6b772a70$dd00a8c0@jamessonyvaio>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

James Seng/Personal writes:
> What if due to my personal preference/trademark, I want to have
> uppercase char?

Existing DNS servers, SMTP servers, HTTP servers, etc. don't treat an
uppercase C-cedilla the same way as a lowercase c-cedilla.

This is why, in both the ACE approach and the UTF-8 approach, C-cedilla
is prohibited on the wire.

If you want users to be able to type C-cedilla and access your c-cedilla
domain name, you'll have to wait for thousands of programs to be changed
and redeployed. I don't want to suffer these costs, and I certainly
don't want to wait that long for working IDNs.

---Dan

P.S. The UTF-8 encoding of c-cedilla passes safely through sendmail.



From owner-idn@ops.ietf.org  Wed May 30 14:59:38 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA21584
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 14:59:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155AhH-0002hH-00
	for idn-data@psg.com; Wed, 30 May 2001 11:27:55 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 155AhG-0002hB-00
	for idn@ops.ietf.org; Wed, 30 May 2001 11:27:54 -0700
Received: (qmail 26225 invoked by uid 1001); 30 May 2001 18:08:28 -0000
Date: 30 May 2001 18:08:28 -0000
Message-ID: <20010530180828.6925.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
References: <03f201c0e8aa$6b772a70$dd00a8c0@jamessonyvaio> <Pine.BSF.4.10.10105300259190.3537-100000@epa.secret.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

lucid@epa.secret.org writes:
> I belive the hardest problem is upgrading the end users. Please try and
> keep in mind that whatever the solution, the greatest pain will probably
> be compatibility issues between the computer and the user.

This problem is exactly what ISO 14755 is all about.

Users should be able to type Shift-Ctrl-222E for Unicode character 222E.
Users should be able to move the mouse on top of that character and see
222E CONTOUR INTEGRAL. For printouts on business cards I'd expect a
small boxed 222E on the next line.

---Dan



From owner-idn@ops.ietf.org  Wed May 30 15:18:36 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA22236
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 15:18:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155BG3-00037z-00
	for idn-data@psg.com; Wed, 30 May 2001 12:03:51 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 155BG2-00037c-00
	for idn@ops.ietf.org; Wed, 30 May 2001 12:03:50 -0700
Received: (qmail 8897 invoked by uid 1001); 30 May 2001 18:42:00 -0000
Date: 30 May 2001 18:42:00 -0000
Message-ID: <20010530184200.8224.qmail@cr.yp.to>
Mail-Followup-To: eric@sendmail.com,
  idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Cc: eric@sendmail.com
Subject: Re: [idn] UTF-8 as the long-term IDN solution
References: <Pine.GSO.4.00.10105281945410.5818-100000@sandra.lysator.liu.se> <20010528191702.1600.qmail@cr.yp.to> <p0510030eb7389ab8633e@[165.227.249.18]> <20010529042557.13041.qmail@cr.yp.to> <p05100323b739767904cf@[165.227.249.18]> <20010529200712.15401.qmail@cr.yp.to> <5.1.0.14.2.20010529175754.04eb52f8@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dave Crocker writes:
> In 1992 we were assured that Unicode was instantly going to be in mass
> use, for example.

Really? Precise reference and exact quote, please. Who told you that
Unicode was ``instantly'' going to be in mass use? (It's widely used
now, though it isn't universal yet.)

When I say that many people proposed deprecating 7-bit SMTP a decade
ago, I can back up my statements. For example, Andre Pirard said ``I
find Robert Ullmann's proposition excellent. Require that relays pass 8
bits ...'' See http://www.imc.org/ietf-smtp/old-archive/0326.html.

The only objection to that requirement was the claim that 8-bit support
would take a long time to be deployed. Vixie said that he had some
seven-year-old sendmail binaries, for example, and concluded ``with
near-certainty'' that ``any changes to the SMTP spec will take at least
a decade to reach 90% of the critical server population.''

Well, it's now a decade later, and every critical server supports 8 bits
in the message body EVEN THOUGH YOU IETF IDIOTS STILL ALLOW 7-BIT MTAS.
If the SMTP spec had changed ten years ago to require transparent 8-bit
handling in both the header and the body, we wouldn't have sendmail's
UTF-8 failures today.

I DO NOT WANT TO BE FACED WITH 8-BIT PROBLEMS IN ANOTHER TEN YEARS. I am
astounded that anyone would object to requiring 8-bit support. Even in
the case of a horrible piece of code like sendmail, handling 8 bits is a
simple matter of converting dangerous characters to two-byte sequences
on input and doing the opposite conversion on output.

> After all, we all have such a good track record when predicting the
> future, don't we. 

Obviously _you_ don't.

---Dan



From owner-idn@ops.ietf.org  Wed May 30 15:53:39 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA22796
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 15:53:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155Bmk-0007tv-00
	for idn-data@psg.com; Wed, 30 May 2001 12:37:38 -0700
Received: from arachnid.ehsco.com ([209.31.7.46] helo=Arachnid.NTRG.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 155Bmj-0007to-00
	for idn@ops.ietf.org; Wed, 30 May 2001 12:37:38 -0700
Received: from ehsco.com (nat-external.ehsco.com [209.31.7.42])
          by Arachnid.NTRG.com (Netscape Messaging Server 3.62)  with ESMTP
          id 586; Wed, 30 May 2001 12:37:33 -0700
Message-ID: <3B154BFB.998E424F@ehsco.com>
Date: Wed, 30 May 2001 12:37:31 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "D. J. Bernstein" <djb@cr.yp.to>
CC: idn@ops.ietf.org
Subject: Re: [idn] Dots, and a path to working IDNs
References: <20010529194540.8982.qmail@cr.yp.to> <200105300128.VAA22811@astro.cs.utk.edu> <20010530174931.15520.qmail@cr.yp.to>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


"D. J. Bernstein" wrote:

> I again ask the WG chairs to run a poll to see whether we have
> consensus that the long-term IDN solution will encode Unicode
> characters as UTF-8 on the wire.

So that we know exactly what it is that we'd be voting for or against,
could you put together a draft which clearly documents how your
just-send-utf8 proposal would work with the legacy protocol and
implementations in the following scenarios:

 a) Where does bad-v-good filtering occur? For example, allowing
    current apps and resolvers to just-send-utf8 means that
    Z-with-caron will have different code values based on the
    local charset (windows-1252 is different from 8859-15 is
    different from 10646/unicode). Where and how is the
    normalization handled in your scheme?

 b) How do you prevent utf8 chars from breaking legacy devices?
    EG, for an older (and orphaned) X terminal that legitimately
    rejects underscore in hostnames, how do you keep utf8 from
    jamming up bootp/tftp on that host? Similarly, how do you
    prevent utf8 in CNAME responses from jamming up all of the
    other hosts that legitimately enforce existing standards?

 c) Also, how do you prevent utf8 in PTR RRs from jamming up
    syslog daemons, received headers, netstat output and the
    hundreds if not thousands of other applications that
    currently process PTR data for hostnames and which reject
    data that does not comply with LDH rules?

I don't think you can do it with the current protocol and implementation
limitations. Your hand-waving is unconvincing. Prove me wrong. Consider
yourself double-dog-dared if you must, but please either poop or get off
the pot. Unless you can clearly describe how this will work, please let us
get on with real progress.

I repeat, this needs to be in an ID so that we know for certain what you
really mean. Your web site does not serve that purpose.

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



From owner-idn@ops.ietf.org  Wed May 30 15:55:43 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA22856
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 15:55:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155Bs1-000811-00
	for idn-data@psg.com; Wed, 30 May 2001 12:43:05 -0700
Received: from epa.secret.org ([206.220.140.150] ident=0)
	by psg.com with esmtp (Exim 3.16 #1)
	id 155Bs0-00080u-00
	for idn@ops.ietf.org; Wed, 30 May 2001 12:43:04 -0700
Received: from localhost (lucid@localhost)
	by epa.secret.org (8.9.3/8.9.1) with ESMTP id PAA09923;
	Wed, 30 May 2001 15:43:03 -0400 (EDT)
Date: Wed, 30 May 2001 15:43:03 -0400 (EDT)
From: lucid@epa.secret.org
To: "D. J. Bernstein" <djb@cr.yp.to>
cc: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 / RACE
In-Reply-To: <20010530180828.6925.qmail@cr.yp.to>
Message-ID: <Pine.BSF.4.10.10105301523370.5332-100000@epa.secret.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk



On 30 May 2001, D. J. Bernstein wrote:

> lucid@epa.secret.org writes:
> > I belive the hardest problem is upgrading the end users. Please try and
> > keep in mind that whatever the solution, the greatest pain will probably
> > be compatibility issues between the computer and the user.
> 
> This problem is exactly what ISO 14755 is all about.
> 
> Users should be able to type Shift-Ctrl-222E for Unicode character 222E.
> Users should be able to move the mouse on top of that character and see
> 222E CONTOUR INTEGRAL. For printouts on business cards I'd expect a
> small boxed 222E on the next line.
> 
> ---Dan

No offense but, what planet do these users come from? and are they
hiring sysadmins on this planet? Seriously, enough users have problems
double clicking that Microsoft dropped it as a required skill for
using Windows.

I dont belive in users that can handle typing Shift-Ctrl-anything,
and I talk to them all day. I have more faith in Santa, and he is alot
easier to talk to.

-Bill





From owner-idn@ops.ietf.org  Wed May 30 16:42:18 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA24165
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 16:42:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155Ca3-0008Qk-00
	for idn-data@psg.com; Wed, 30 May 2001 13:28:35 -0700
Received: from epa.secret.org ([206.220.140.150] ident=0)
	by psg.com with esmtp (Exim 3.16 #1)
	id 155Ca3-0008Qe-00
	for idn@ops.ietf.org; Wed, 30 May 2001 13:28:35 -0700
Received: from localhost (lucid@localhost)
	by epa.secret.org (8.9.3/8.9.1) with ESMTP id QAA10382
	for <idn@ops.ietf.org>; Wed, 30 May 2001 16:28:34 -0400 (EDT)
Date: Wed, 30 May 2001 16:28:34 -0400 (EDT)
From: lucid@epa.secret.org
To: idn@ops.ietf.org
Subject: [idn] A sysadmins perspective
In-Reply-To: <20010530184200.8224.qmail@cr.yp.to>
Message-ID: <Pine.BSF.4.10.10105301552090.5332-100000@epa.secret.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk


My biggest concern is supporting IDN.
Writing code, and upgrading servers are one time costs.
Support is unfortunatly reoccuring

I am happy to upgrade production nameservers,
I am wont mind upgrading production webservers,
I am willing to upgrade production mailservers, pop servers and etc.

I want to be able to tell users that they must upgrade to
Windows XP service pack 20 or MacOS X.1.2.3 or whatever
to use IDN or we wont support them.

I dont want to have to spend 4 hours on a support call
trying to explain what ACE means or explaining that
UTF-8 is a character set when the problem is that their
capslock key is stuck and mistyped their password.

IDNs should only displayed to users who userstand them.

The only way I see to do this is mapping them at the
application layer.

example: (assume ~i18n~ is any IDN name)

~i18n~.com <-mapping-> myi18n.com

Sender
--------
Date: Wed, 30 May 2001 12:42:06 -0700 (PDT)
From: user <user@~i18n~.com>
To: Joe <joe@example.com>
Subject: ...


test

On-The-Wire
--------
Date: Wed, 30 May 2001 12:42:06 -0700 (PDT)
From: user <user@myi18n.com>
To: Joe <joe@example.com>
Subject: ...


test

Receive with IDN
--------
Date: Wed, 30 May 2001 12:42:06 -0700 (PDT)
From: user <user@~i18n~.com>
To: Joe <joe@example.com>
Subject: ...


test


Receive without IDN
--------
Date: Wed, 30 May 2001 12:42:06 -0700 (PDT)
From: user <user@myi18n.com>
To: Joe <joe@example.com>
Subject: ...


test


The IDN application could do a lookup to convert myi18n.com to ~i18n~.com
It is possible that locale style support could be built-in so that
myi18n.com is diaplayed as;
ru_RU gets ~i18n~ru~.com
en_US gets myi18n.com
ja_JP gets ~i18n~ja~.com
etc...

All of these would get converted back before being put back on the wire.

I dont know if this is functional or usefull but I am up for anything
that cuts down on support.

-Bill




From owner-idn@ops.ietf.org  Wed May 30 17:17:25 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA24946
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 17:17:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155D7e-0008nQ-00
	for idn-data@psg.com; Wed, 30 May 2001 14:03:18 -0700
Received: from nordic.cisco.com ([64.103.48.45] helo=cisco.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 155D7d-0008nJ-00
	for idn@ops.ietf.org; Wed, 30 May 2001 14:03:17 -0700
Received: from [192.168.1.40] (ssh-ams1.cisco.com [144.254.74.55])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id XAA25148;
	Wed, 30 May 2001 23:03:10 +0200 (MET DST)
Date: Wed, 30 May 2001 23:01:43 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
To: idn@ops.ietf.org
cc: eric@sendmail.com
Subject: Re: [idn] UTF-8 as the long-term IDN solution
Message-ID: <6541992.991263703@localhost>
In-Reply-To: <20010530184200.8224.qmail@cr.yp.to>
References: <Pine.GSO.4.00.10105281945410.5818-100000@sandra.lysator.liu.se>
 <20010528191702.1600.qmail@cr.yp.to>
 <p0510030eb7389ab8633e@[165.227.249.18]>
 <20010529042557.13041.qmail@cr.yp.to>
 <p05100323b739767904cf@[165.227.249.18]>
 <20010529200712.15401.qmail@cr.yp.to>
 <5.1.0.14.2.20010529175754.04eb52f8@dcrocker.net>
 <20010530184200.8224.qmail@cr.yp.to>
X-Mailer: Mulberry/2.1.0a6 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

--On 01-05-30 18.42 +0000 "D. J. Bernstein" <djb@cr.yp.to> wrote:

> EVEN THOUGH YOU IETF IDIOTS STILL ALLOW 7-BIT MTAS

That was pretty constructive, and I guess everyone in this working group
which feel they participate in the IETF now understand exactly how you feel
about them.

At least it was explicit.

Thank's for sharing.

   paf




From owner-idn@ops.ietf.org  Wed May 30 17:38:51 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA25291
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 17:38:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155DOM-0008xw-00
	for idn-data@psg.com; Wed, 30 May 2001 14:20:34 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 155DOM-0008xq-00
	for idn@ops.ietf.org; Wed, 30 May 2001 14:20:34 -0700
Received: (qmail 11523 invoked by uid 1001); 30 May 2001 20:18:52 -0000
Date: 30 May 2001 20:18:52 -0000
Message-ID: <20010530201852.12411.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] Dots, and a path to working IDNs
References: <20010529194540.8982.qmail@cr.yp.to> <200105300128.VAA22811@astro.cs.utk.edu> <20010530174931.15520.qmail@cr.yp.to> <3B154BFB.998E424F@ehsco.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:
> So that we know exactly what it is

``The long-term IDN solution will encode Unicode characters as UTF-8 on
the wire.'' I suspect that we have consensus on this point, even though
we don't have consensus on the short-term approach.

> that we'd be voting for or against

I'm sure several people will pop up to inform you that IETF has ``straw
polls'' but doesn't have ``votes.'' Votes are things done by legitimate
standards organizations that obey United States antitrust law; the IETF
is not one of those organizations.

> How do you prevent utf8 chars from breaking legacy devices?

Fix the legacy devices. This is obviously something that's going to
happen anyway.

> an older (and orphaned) X terminal that legitimately rejects
> underscore in hostnames

Are you fantasizing, or can you identify an actual X terminal that has
to be fixed?

Same question about your ``hundreds if not thousands of other
applications that ... reject data that does not comply with LDH rules.''
Do you have any evidence that the fixes listed on my web page---in
particular, enabling no-check-names in /etc/resolv.conf, with the
current gethostbyname() library---are not sufficient?

> I don't think you can do it with the current protocol

You are speaking nonsense. The proposal changes the protocols.

> and implementation limitations.

Implementation problems are a serious issue. That's why I've been going
to so much effort to identify the implementation work that actually has
to be done. See http://cr.yp.to/proto/idn.html.

---Dan



From owner-idn@ops.ietf.org  Wed May 30 18:10:09 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA26082
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 18:10:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155Dt6-0009EZ-00
	for idn-data@psg.com; Wed, 30 May 2001 14:52:20 -0700
Received: from arachnid.ehsco.com ([209.31.7.46] helo=Arachnid.NTRG.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 155Dt6-0009ET-00
	for idn@ops.ietf.org; Wed, 30 May 2001 14:52:20 -0700
Received: from ehsco.com (nat-external.ehsco.com [209.31.7.42])
          by Arachnid.NTRG.com (Netscape Messaging Server 3.62)  with ESMTP
          id 526 for <idn@ops.ietf.org>; Wed, 30 May 2001 14:52:18 -0700
Message-ID: <3B156B91.6F62C93F@ehsco.com>
Date: Wed, 30 May 2001 14:52:18 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
CC: idn@ops.ietf.org
Subject: Re: [idn] Dots, and a path to working IDNs
References: <20010529194540.8982.qmail@cr.yp.to> <200105300128.VAA22811@astro.cs.utk.edu> <20010530174931.15520.qmail@cr.yp.to> <3B154BFB.998E424F@ehsco.com> <20010530201852.12411.qmail@cr.yp.to>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


"D. J. Bernstein" wrote:

> > How do you prevent utf8 chars from breaking legacy devices?
> 
> Fix the legacy devices. This is obviously something that's going to
> happen anyway.

Sooner or later, but your approach breaks them until they are replaced.
Your refusal to concede this point does not change the fact.

> > an older (and orphaned) X terminal that legitimately rejects
> > underscore in hostnames
> 
> Are you fantasizing, or can you identify an actual X terminal that has
> to be fixed?

I don't remember the exact make and model, but I encountered this
particular problem at AVIS 10 or 15 years ago. Probably NCD, but it is
irrelevant really.

Your list of broken apps proves that there is more than one. Surely you
know that your list is incomplete, statistically and quantitatively. Your
position that any list of would be finite is completely untenable.

> You are speaking nonsense. The proposal changes the protocols.

What proposal?

Also, you ignored item (a) in your response. Please tell us how you plan
to restrict the eight-bit data that enters the DNS service space.

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



From owner-idn@ops.ietf.org  Wed May 30 18:25:45 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA26322
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 18:25:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155EBU-0009W3-00
	for idn-data@psg.com; Wed, 30 May 2001 15:11:20 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 155EBU-0009Vt-00
	for idn@ops.ietf.org; Wed, 30 May 2001 15:11:20 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id SAA02221;
        Wed, 30 May 2001 18:11:18 -0400 (EDT)
Message-Id: <200105302211.SAA02221@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] Dots, and a path to working IDNs 
In-reply-to: Your message of "30 May 2001 17:49:31 -0000."
             <20010530174931.15520.qmail@cr.yp.to> 
Date: Wed, 30 May 2001 18:11:18 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> Keith again complains that UTF-8 might not ``work well for some
> important languages.'' 

once again, misrepresenting my statements.

you're absolutely right - there's no point in us arguing about such things.

Keith



From owner-idn@ops.ietf.org  Wed May 30 19:31:36 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA27389
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 19:31:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155FCD-000A1w-00
	for idn-data@psg.com; Wed, 30 May 2001 16:16:09 -0700
Received: from muncher.math.uic.edu ([131.193.178.181])
	by psg.com with smtp (Exim 3.16 #1)
	id 155FCC-000A1p-00
	for idn@ops.ietf.org; Wed, 30 May 2001 16:16:08 -0700
Received: (qmail 15429 invoked by uid 1001); 30 May 2001 22:49:36 -0000
Date: 30 May 2001 22:49:36 -0000
Message-ID: <20010530224936.10280.qmail@cr.yp.to>
Mail-Followup-To: idn@ops.ietf.org
From: "D. J. Bernstein" <djb@cr.yp.to>
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 as the long-term IDN solution
References: <20010530171809.10756.qmail@cr.yp.to> <200105302208.SAA02183@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:
> You stubbornly refuse to fix qmail to comply with the standards, 

Wrong as usual. Please read RFC 2821, section 2.4: ``In general, a relay
SMTP SHOULD assume that the message content it has received is valid
and, assuming that the envelope permits doing so, relay it without
inspecting that content.''

You may reasonably argue that message creators today shouldn't use 8-bit
bytes in header fields. But you are being a fool when you claim that
MTAs must, or even should, reject 8-bit bytes.

> Fortunately, most deployed MTAs block 8-bit characters in message 
> headers, which keeps people from depending on them.

Wrong on both counts. Europeans rely heavily on ISO 8859-1 in Subject
lines, for example. The only reason that we're suffering through the
incompatible change from 8859-1 to UTF-8 is that 8859-1 is missing the
characters that billions of people want.

---Dan



From owner-idn@ops.ietf.org  Wed May 30 19:35:00 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA27430
	for <idn-archive@lists.ietf.org>; Wed, 30 May 2001 19:34:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155E91-0009Ty-00
	for idn-data@psg.com; Wed, 30 May 2001 15:08:47 -0700
Received: from astro.cs.utk.edu ([160.36.58.43])
	by psg.com with esmtp (Exim 3.16 #1)
	id 155E90-0009Ts-00
	for idn@ops.ietf.org; Wed, 30 May 2001 15:08:47 -0700
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id SAA02183;
        Wed, 30 May 2001 18:08:40 -0400 (EDT)
Message-Id: <200105302208.SAA02183@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] UTF-8 as the long-term IDN solution 
In-reply-to: Your message of "30 May 2001 17:18:09 -0000."
             <20010530171809.10756.qmail@cr.yp.to> 
Date: Wed, 30 May 2001 18:08:39 -0400
Sender: owner-idn@ops.ietf.org
Precedence: bulk

> > do you really think we'll be using a paper-tape I/O model 10 years
> > from now?  even on UNIX?  maybe we will - it's endured a long time -
> > but I wouldn't bet the farm on it.
> 
> Ever heard of TCP? Byte streams aren't going away.

okay, well perhaps I should have asked:

"do you really think we'll be using user interfaces designed for a
paper-tape I/O model 10 years from now?"

> > p.s. if and when qmail has been around for 20+ years,  and if it still
> > has significant popularity, some young upstart is going to trash your
> > code for being shortsighted and brain-damaged.
> 
> It has been around for more than 5 years. It hasn't needed any syntax
> extensions except to work around bugs in other software (space after
> MAIL FROM, for example). If it turns out someday that I haven't planned
> ahead far enough, I'll make whatever changes are necessary.

unlike sendmail, you had the luxury of implementing qmail after the 
mail standards had stabilized, when pretty much everyone was using
DNS with MX records and SMTP over TCP.

> For comparison: In February 1999, when it became clear that the revised
> USENET message header field format was going to allow unencoded UTF-8, I
> explained to Eric Allman how to make sendmail 8-bit-clean. (USENET
> messages are often forwarded through mail by 8-bit-clean gateways.) A
> few days ago, he released another security-fix release of sendmail. It
> still isn't 8-bit-clean.

As a matter of fact, message headers are still required to be in ASCII.
An MTA that accepts or relays broken message headers is arguably broken.
Fortunately, most deployed MTAs block 8-bit characters in message 
headers, which keeps people from depending on them. This is a good thing 
because their behavior isn't defined they wouldn't be reliable even if
they were passed cleanly.  So when are you going to fix qmail?

(you don't have to answer that, it's a rhetorical question)

You stubbornly refuse to fix qmail to comply with the standards, 
because you think that you know better than anyone else how things 
should work - which characteristics of software or a protocol are 
bugs and which are features, who should deploy what new servers at
what timeframe, etc.  It's your right and privilege to think that, and 
you are free to implement your own software however you wish.  But you 
shouldn't be surprised to find out that others have different opinions 
about how things should work.  

For a protocol to be interoperable in the real world it must be able to
tolerate some variation in implementation, user interface, and deployment.
People everywhere will not follow your game plan (or anyone else's) just
because you claim it's a good idea.  Different people in different 
situations will inevitably favor different solution paths. 

Keith



From owner-idn@ops.ietf.org  Thu May 31 02:55:09 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA17237
	for <idn-archive@lists.ietf.org>; Thu, 31 May 2001 02:55:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155Lwq-0003mu-00
	for idn-data@psg.com; Wed, 30 May 2001 23:28:44 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.16 #1)
	id 155Lwp-0003mo-00
	for idn@ops.ietf.org; Wed, 30 May 2001 23:28:43 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0AY64l30v0U3x/VQ2dYZ4X8YlbDcBcVJw==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id F6RE9HUZ; Thu, 31 May 2001 02:26:37 EDT
To: djb@cr.yp.to
Cc: idn@ops.ietf.org
Date: Wed, 30 May 2001 23:39:52 -0700
Subject: Re: [idn] Dots, and a path to working IDNs
Message-ID: <20010530.233955.-813665.0.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.5
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-1,3-4,6-10,12,14,16,18-20,22,24,26,28-32
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

Allow me to comment on your UTF-8 as a long term solution.

Most people in the world using a limited number of basic phonetic symbols
to
communicate.  This point can be shown by looking through Unicode tables.
Even for Chinese, it can be handled by 25 letters as the minimum.  We can

infer that the number of symbols in Latin alphabet is an optimum number 
for majority people in the world.  

The most charllenge problem is dealing with Chinese symbols, there are 
100,000 on the rise and the often used ones are over 8,000(depending on
who's 
viewpoint this is.) each is cramed inside a square space.  If we can
represent them 
with the existing small set of phonetic symbols why should we bother with
UTF-8?  
IBM started 8-bits characters with international users in mind.  But that
solution 
was not effective and the industry  knows the reasons. 
 
I can see supporting UTF-8, such that  we may have International
Alphabet, Cyrillic,
 Arabic with a larger keyboard for the user to take the full usefulness
of 8-bits. 
Chinese have been tried large keyboards, and a medium 10x10 keyboard, but

only the English 3x10 has survived.  Without significent improvement for
the
 users, who would dive into UTF-8 trouble?  

Liana Ye




From owner-idn@ops.ietf.org  Thu May 31 05:52:11 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA19082
	for <idn-archive@lists.ietf.org>; Thu, 31 May 2001 05:52:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155OrN-0004uW-00
	for idn-data@psg.com; Thu, 31 May 2001 02:35:17 -0700
Received: from mail.i-dns.net ([203.126.116.228])
	by psg.com with esmtp (Exim 3.16 #1)
	id 155OrM-0004uI-00
	for idn@ops.ietf.org; Thu, 31 May 2001 02:35:16 -0700
Received: from jamessonyvaio (p9d2.du.dataphone.se [212.37.2.136])
	by mail.i-dns.net (Postfix) with SMTP
	id 214D5FFC05; Thu, 31 May 2001 17:37:42 +0800 (SGT)
Message-ID: <039d01c0ea7e$1067f080$880225d4@jamessonyvaio>
From: "James Seng/Personal" <James@Seng.cc>
To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
References: <20010529194540.8982.qmail@cr.yp.to> <200105300128.VAA22811@astro.cs.utk.edu> <20010530174931.15520.qmail@cr.yp.to> <3B154BFB.998E424F@ehsco.com> <20010530201852.12411.qmail@cr.yp.to>
Subject: Re: [idn] Dots, and a path to working IDNs
Date: Fri, 1 Jun 2001 17:34:29 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

If this is the vote for the strawpoll, it is too vague to move forward
with. UTF-8 on the wire ... how? tag? untag? negiotated? retrofit into
the packet? what needs to be change? what will break? what wouldnt? what
difficulties would we face.

We could move forward with a strawpoll if only you have a concrete
proposal (or one which you can point to). Currently, all we have is what
you have on your website and honestly, I think it is not a complete
picture nor a detail description of who needs to do what and what have
to be taken care of. And given our discussion, it is apparently your
Fast-Nameprep (on Keyboard) idea is far too different compared to some
other proposal we have.

In order to move this forward, could I ask you document your idea into
an I-D first? Thanks!

ps: If I were to vote now, I would vote for UTF-64 (if there is one). My
guess is 10-20 years later, we going to see 64bits hardware, with 64bits
OS computing in 64bits wide characters. Thus UTF-64 makes more sense for
a long term solution. We wont want our future engineers to scream at us
for limiting to them only 8-bits when they have 64-bits to play with.

-James Seng

> ``The long-term IDN solution will encode Unicode characters as UTF-8
on
> the wire.'' I suspect that we have consensus on this point, even
though
> we don't have consensus on the short-term approach.




From owner-idn@ops.ietf.org  Thu May 31 10:22:39 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA26220
	for <idn-archive@lists.ietf.org>; Thu, 31 May 2001 10:22:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155T3F-000715-00
	for idn-data@psg.com; Thu, 31 May 2001 07:03:49 -0700
Received: from mail.lysator.liu.se ([130.236.254.3])
	by psg.com with esmtp (Exim 3.16 #1)
	id 155T3E-00070z-00
	for idn@ops.ietf.org; Thu, 31 May 2001 07:03:48 -0700
Received: from sandra.lysator.liu.se (sandra.lysator.liu.se [130.236.254.203])
	by mail.lysator.liu.se (Postfix) with ESMTP
	id C67BA82F52B; Thu, 31 May 2001 16:03:45 +0200 (MET DST)
Received: from localhost (mag@localhost)
	by sandra.lysator.liu.se (8.9.0/8.8.7) with SMTP id QAA04997;
	Thu, 31 May 2001 16:03:45 +0200 (MET DST)
X-Authentication-Warning: sandra.lysator.liu.se: mag owned process doing -bs
Date: Thu, 31 May 2001 16:03:44 +0200 (MET DST)
From: C C Magnus Gustavsson <mag@lysator.liu.se>
To: liana.ydisg@juno.com
Cc: djb@cr.yp.to, idn@ops.ietf.org
Subject: Re: [idn] Dots, and a path to working IDNs
In-Reply-To: <20010530.233955.-813665.0.liana.ydisg@juno.com>
Message-ID: <Pine.GSO.4.00.10105311602130.4991-100000@sandra.lysator.liu.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-idn@ops.ietf.org
Precedence: bulk

On Wed, 30 May 2001 liana.ydisg@juno.com wrote:

> Allow me to comment on your UTF-8 as a long term solution.
> 
> Most people in the world using a limited number of basic phonetic symbols
> to
> communicate.  This point can be shown by looking through Unicode tables.
> Even for Chinese, it can be handled by 25 letters as the minimum.  We can
> 
> infer that the number of symbols in Latin alphabet is an optimum number 
> for majority people in the world.  

The number of consonants may be fine but the Latin vowals are at least
by far too few to represent the sounds of a large number of languages
(including English, btw).


> The most charllenge problem is dealing with Chinese symbols, there are 
> 100,000 on the rise and the often used ones are over 8,000(depending on
> who's 
> viewpoint this is.) each is cramed inside a square space.  If we can
> represent them 
> with the existing small set of phonetic symbols why should we bother with
> UTF-8?  
> IBM started 8-bits characters with international users in mind.  But that
> solution 
> was not effective and the industry  knows the reasons. 

I guess that I'm not part of "industry" then after all, because I sure
don't know neither that 8 bit characters are not effective nor the
reasons. Perhaps you could explain them to us?


> I can see supporting UTF-8, such that  we may have International
> Alphabet, Cyrillic,
>  Arabic with a larger keyboard for the user to take the full usefulness
> of 8-bits. 
> Chinese have been tried large keyboards, and a medium 10x10 keyboard, but
> 
> only the English 3x10 has survived.  Without significent improvement for
> the
>  users, who would dive into UTF-8 trouble?  

I'm sorry but I don't understand. What are you suggesting? That we
stick with ASCII and don't bother about anything else? Are you really
trying to say that you don't see any improvement with using anything
else than ASCII?

/Magnus




From owner-idn@ops.ietf.org  Thu May 31 15:13:02 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA06546
	for <idn-archive@lists.ietf.org>; Thu, 31 May 2001 15:13:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155XZd-000B3k-00
	for idn-data@psg.com; Thu, 31 May 2001 11:53:33 -0700
Received: from m2.boston.juno.com ([64.136.24.65])
	by psg.com with esmtp (Exim 3.16 #1)
	id 155XZc-000B3e-00
	for idn@ops.ietf.org; Thu, 31 May 2001 11:53:33 -0700
Received: from cookie.juno.com by cookie.juno.com for <"h3psgxK7wwe0kgb98qASH0AY64l30v0UiEQTXMaeDmZWhF+MbmrS/Q==">
Received: (from liana.ydisg@juno.com)
 by m2.boston.juno.com (queuemail) id F6SRRDLL; Thu, 31 May 2001 14:49:17 EDT
To: mag@lysator.liu.se
Cc: djb@cr.yp.to, idn@ops.ietf.org
Date: Thu, 31 May 2001 12:02:40 -0700
Subject: Re: [idn] Dots, and a path to working IDNs
Message-ID: <20010531.120241.-1033675.0.liana.ydisg@juno.com>
X-Mailer: Juno 4.0.5
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-8,10-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 am only address the user interface side of the question.  For 
industrial development, please see J. Seng's comment.  

Phonetic symbols is not the same with the number of sounds in
 a language.  For the number of sounds in a language you have
to ask speech recognition experts.

Liana Ye

On Thu, 31 May 2001 16:03:44 +0200 (MET DST) C C Magnus Gustavsson
<mag@lysator.liu.se> writes:
> On Wed, 30 May 2001 liana.ydisg@juno.com wrote:
> 
> > Allow me to comment on your UTF-8 as a long term solution.
> > 
> > Most people in the world using a limited number of basic phonetic 
> symbols
> > to
> > communicate.  This point can be shown by looking through Unicode 
> tables.
> > Even for Chinese, it can be handled by 25 letters as the minimum.  
> We can
> > 
> > infer that the number of symbols in Latin alphabet is an optimum 
> number 
> > for majority people in the world.  
> 
> The number of consonants may be fine but the Latin vowals are at 
> least
> by far too few to represent the sounds of a large number of 
> languages
> (including English, btw).
> 
> 
> > The most charllenge problem is dealing with Chinese symbols, there 
> are 
> > 100,000 on the rise and the often used ones are over 
> 8,000(depending on
> > who's 
> > viewpoint this is.) each is cramed inside a square space.  If we 
> can
> > represent them 
> > with the existing small set of phonetic symbols why should we 
> bother with
> > UTF-8?  
> > IBM started 8-bits characters with international users in mind.  
> But that
> > solution 
> > was not effective and the industry  knows the reasons. 
> 
> I guess that I'm not part of "industry" then after all, because I 
> sure
> don't know neither that 8 bit characters are not effective nor the
> reasons. Perhaps you could explain them to us?
> 
> 
> > I can see supporting UTF-8, such that  we may have International
> > Alphabet, Cyrillic,
> >  Arabic with a larger keyboard for the user to take the full 
> usefulness
> > of 8-bits. 
> > Chinese have been tried large keyboards, and a medium 10x10 
> keyboard, but
> > 
> > only the English 3x10 has survived.  Without significent 
> improvement for
> > the
> >  users, who would dive into UTF-8 trouble?  
> 
> I'm sorry but I don't understand. What are you suggesting? That we
> stick with ASCII and don't bother about anything else? Are you 
> really
> trying to say that you don't see any improvement with using anything
> else than ASCII?
> 
> /Magnus
> 



From owner-idn@ops.ietf.org  Thu May 31 22:15:52 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA12851
	for <idn-archive@lists.ietf.org>; Thu, 31 May 2001 22:15:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155e4u-000Gfs-00
	for idn-data@psg.com; Thu, 31 May 2001 18:50:16 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 155e4t-000Gfm-00
	for idn@ops.ietf.org; Thu, 31 May 2001 18:50:15 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 155e4s-0004kH-00; Thu, 31 May 2001 18:50:14 -0700
Date: Fri, 1 Jun 2001 01:50:14 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 as the long-term IDN solution
Message-ID: <20010601015014.I16547@arwen.cs.berkeley.edu>
References: <p05100323b739767904cf@[165.227.249.18]> <200105300041.UAA22410@astro.cs.utk.edu> <Pine.GSO.4.00.10105281945410.5818-100000@sandra.lysator.liu.se> <20010528191702.1600.qmail@cr.yp.to> <p0510030eb7389ab8633e@[165.227.249.18]> <20010529042557.13041.qmail@cr.yp.to> <p05100323b739767904cf@[165.227.249.18]> <20010529042557.13041.qmail@cr.yp.to> <Pine.BSF.4.30.0105291200340.29244-100000@spider.nic-se.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <Pine.BSF.4.30.0105291200340.29244-100000@spider.nic-se.se>; from dufberg@nic-se.se on Tue, May 29, 2001 at 12:13:26PM +0200
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

I've had some further thoughts regarding that model I proposed, some
of which are similar to thoughts that have been posted in this thread.
First here's a quick recap of the model:

IDNs can be represented in a multitude of ways, but there are two
especially customary representations: ACE and UTF-8.  Old protocols
use ACE on the wire; new protocols use UTF-8 on the wire.  Evolving
protocols need to either stick with ACE or handle the transition
cleanly, perhaps by negotiating capabilities.  DNS must accept both ACE
queries (returning ACE responses) and UTF-8 queries (returning UTF-8
responses).

It's the DNS part that I've been thinking about.  The ACE
queries/responses are obviously needed for backward compatibility, and
they require no changes to the infrastructure.  But how are the UTF-8
queries going to work?

I can think of two approaches:  Either segregate UTF-8 queries into a
new kind of request (using a protocol extension or a new class or new
resource records or whatever), or allow UTF-8 in regular DNS queries.

If UTF-8 queries use a new type of request, then they can be used
only if both the client's resolver and the local DNS server have been
upgraded to support the new query format.  If you're upgrading the
resolver, you might as well include an ACE encoder/decoder, because
ACE queries will always work, even before the local DNS server has
been upgraded.  And once you have an ACE encoder/decoder, why bother
implementing the new query format?  Applications will never know or care
which format the resolver is using.  Even if every other protocol and
application migrates to UTF-8 and forgets how to encode and decode ACE,
the resolvers and DNS servers could still be speaking ACE to each other
and the other protocols/applications would be oblivious.

The other approach, allowing UTF-8 in regular DNS queries, has
advantages and disadvantages.  The advantage is that some existing
applications will work to some extent by accident.  In particular, if an
application uses UTF-8 natively, and its resolver is 8-bit clean, and
its DNS servers are 8-bit clean, and the UTF-8 encoding of an IDN fits
in 63 bytes (which won't always happen--UTF-8 is about 50% larger than
ACE for some scripts), then a lookup of the IDN will work by accident.
Of course, if this application talks to other applications that don't
use UTF-8 natively, there may be other problems, but let's focus on
DNS for the moment.  One disadvantage of this approach is an increased
opportunity for spoofing:  If some applications accidentally send
UTF-8 in DNS queries, then surely other applications will accidentally
send other 8-bit encodings, some of which are coincidentally valid
UTF-8.  But it could be argued that any existing application that does a
lookup on an 8-bit domain name is asking for trouble, and gets what it
deserves, except that UTF-8 applications will be pardoned (sometimes).

Does anyone find this accidentally-works phenomenon to be a compelling
reason to allow UTF-8 in regular DNS queries?

It looks to me like allowing UTF-8 in regular DNS queries may be more
trouble than it's worth, and creating a new query format just for UTF-8
is certainly more trouble than it's worth.  If someday there is a
pressing need for a new query format for some other reason, we might as
well make it use UTF-8, but UTF-8 itself is not a sufficient reason to
introduce a new format now.

Please remember that even if DNS sticks with ACE for now, that doesn't
impede any other application/protocol from using UTF-8.  It's quite
orthogonal.

AMC



From owner-idn@ops.ietf.org  Thu May 31 22:34:57 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA13934
	for <idn-archive@lists.ietf.org>; Thu, 31 May 2001 22:34:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155eW6-000H2i-00
	for idn-data@psg.com; Thu, 31 May 2001 19:18:22 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 155eW6-000H2b-00
	for idn@ops.ietf.org; Thu, 31 May 2001 19:18:22 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 155eW5-0004mQ-00; Thu, 31 May 2001 19:18:21 -0700
Date: Fri, 1 Jun 2001 02:18:21 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] How gethostbyname() handles 8-bit characters
Message-ID: <20010601021821.J16547@arwen.cs.berkeley.edu>
References: <7544575.990957280@localhost> <20010527165903.5833.qmail@cr.yp.to> <079c01c0e6e4$3bf7ee50$7dcb15a5@jamessonyvaio> <20010527202613.5518.qmail@cr.yp.to> <083c01c0e6f7$235b7200$7dcb15a5@jamessonyvaio> <20010528043639.9273.qmail@cr.yp.to> <20010529033041.B22313@arwen.cs.berkeley.edu> <20010529045656.23237.qmail@cr.yp.to> <20010529052322.E22313@arwen.cs.berkeley.edu> <20010529185911.17254.qmail@cr.yp.to>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <20010529185911.17254.qmail@cr.yp.to>; from djb@cr.yp.to on Tue, May 29, 2001 at 06:59:11PM -0000
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

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

> The current gethostbyname() release (if you put no-check-names into
> /etc/resolv.conf) simply copies the 8-bit bytes to the DNS packet.  It
> doesn't care about the interpretation of the bytes as characters.

What about in the normal case?  Is gethostbyname() copying the bytes
because the interface takes bytes, or because the interface takes ASCII
and DNS also takes ASCII?  I've tried to discover the answer, to no
avail; I think the semantics are ambiguous.

Putting no-check-names into /etc/resolv.conf is obviously a workaround,
a way to tell the library "get out of my way, I'm doing something
experimental, and I'll take responsibility for it", so I don't think we
can infer anything about the intended semantics from the behavior under
those circumstances.

It would be instructive to see how gethostbyname() behaves in a
locale for which the LDH characters do not occupy their ASCII code
positions.  But I know of no such locale on any system that implements
gethostbyname().

My gut feeling is still that if gethostbyname() is going to start
accepting 8-bit names, it should interpret them according to the charset
of the current locale (unless "no-check-names" is in effect, which
disables any interpretation and lets the caller specify the raw bytes).
If application programmers want it to assume UTF-8, they merely need to
set the locale to one that uses UTF-8.  And if you're predictions are
correct, that will be the default anyway.

AMC



From owner-idn@ops.ietf.org  Thu May 31 23:09:20 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA14372
	for <idn-archive@lists.ietf.org>; Thu, 31 May 2001 23:09:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155f67-000HNJ-00
	for idn-data@psg.com; Thu, 31 May 2001 19:55:35 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 155f67-000HND-00
	for idn@ops.ietf.org; Thu, 31 May 2001 19:55:35 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 155f66-0004pG-00; Thu, 31 May 2001 19:55:34 -0700
Date: Fri, 1 Jun 2001 02:55:34 +0000
To: idn@ops.ietf.org
Subject: Re: [idn] Dots, and a path to working IDNs
Message-ID: <20010601025534.M16547@arwen.cs.berkeley.edu>
References: <20010530.233955.-813665.0.liana.ydisg@juno.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <20010530.233955.-813665.0.liana.ydisg@juno.com>; from liana.ydisg@juno.com on Wed, May 30, 2001 at 11:39:52PM -0700
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

liana.ydisg@juno.com wrote:

> Allow me to comment on your UTF-8 as a long term solution.

If I understand correctly, you are proposing an alternative model for
representing characters.  Currently, characters are represented as
indices into a table.  If a character is not in the table, it cannot be
represented.

You are proposing that instead of a table of characters, we have a
table of character-building-blocks, and to represent characters as
instructions for how to compose them from the building blocks.  This
would allow new/obscure characters to be used without deploying new
fonts everywhere.

(You also propose to represent the building blocks phonetically using
ASCII, but I think that's an orthogonal issue.)

Is my understanding roughly correct?

It's an interesting idea, but dramatically different from the current
text model.  I suspect that you'd have to change lots of things in all
applications and all operating systems to make this work.

Regarding the use of English keyboards, I'm not sure what your point is.
The representation of text in a file or on a wire is unrelated to how
users type that text, right?

AMC



From owner-idn@ops.ietf.org  Thu May 31 23:26:19 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA14444
	for <idn-archive@lists.ietf.org>; Thu, 31 May 2001 23:26:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155fI3-000HSH-00
	for idn-data@psg.com; Thu, 31 May 2001 20:07:55 -0700
Received: from arwen.cs.berkeley.edu ([128.32.46.192] helo=nicemice.net)
	by psg.com with esmtp (Exim 3.16 #1)
	id 155fI3-000HSB-00
	for idn@ops.ietf.org; Thu, 31 May 2001 20:07:55 -0700
Received: from amc by nicemice.net with local (Exim 3.22 #1 (Debian))
	id 155fI2-0004qU-00; Thu, 31 May 2001 20:07:54 -0700
Date: Fri, 1 Jun 2001 03:07:54 +0000
To: idn@ops.ietf.org
Subject: [idn] nameprep
Message-ID: <20010601030754.N16547@arwen.cs.berkeley.edu>
References: <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca> <p05100336b7342f40ac9b@[165.227.249.18]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.17i
In-Reply-To: <p05100336b7342f40ac9b@[165.227.249.18]>; from phoffman@imc.org on Fri, May 25, 2001 at 08:54:46AM -0700
From: "Adam M. Costello" <amc@cs.berkeley.edu>
Sender: owner-idn@ops.ietf.org
Precedence: bulk

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

> need to finish nameprep, which at this point is finished other than it
> does not address the new characters added in Unicode 3.1.

Nameprep currently includes the following steps:

    KC-normalize
    map
    KC-normalize
    prohibit

KC-normalize is defined (by the relevant Unicode technical report) as
compatible-decomposition followed by canonical composition.  So the
steps are really:

    compatible-decompose
    canonical-compose
    map
    compatible-decompose
    canonical-compose
    prohibit

Do libraries that provide a KC-normalize function also provide the
separate decompose and compose functions?  If so, consider simplifying
the procedure to:

    compatible-decompose
    map
    canonical-compose
    prohibit

Nameprep defines the mapping step itself, so it could take care to
define it in such a way that it preserves the compatibly-decomposed
property (easy--just make sure the output of each mapping entry is
compatibly decomposed), which ensures that the final output is in
normalization form KC.  The mapping table would be smaller this way,
because it would be operating on a smaller repertoire.

AMC



From owner-idn@ops.ietf.org  Thu May 31 23:31:40 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA14789
	for <idn-archive@lists.ietf.org>; Thu, 31 May 2001 23:31:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155fT5-000HWR-00
	for idn-data@psg.com; Thu, 31 May 2001 20:19:19 -0700
Received: from arachnid.ehsco.com ([209.31.7.46] helo=Arachnid.NTRG.com)
	by psg.com with esmtp (Exim 3.16 #1)
	id 155fT4-000HWG-00
	for idn@ops.ietf.org; Thu, 31 May 2001 20:19:18 -0700
Received: from ehsco.com (nat-external.ehsco.com [209.31.7.42])
          by Arachnid.NTRG.com (Netscape Messaging Server 3.62)  with ESMTP
          id 673; Thu, 31 May 2001 20:19:13 -0700
Message-ID: <3B1709B1.B092032@ehsco.com>
Date: Thu, 31 May 2001 20:19:13 -0700
From: "Eric A. Hall" <ehall@ehsco.com>
Organization: EHS Company
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Adam M. Costello" <amc@cs.berkeley.edu>
CC: idn@ops.ietf.org
Subject: Re: [idn] UTF-8 as the long-term IDN solution
References: <p05100323b739767904cf@[165.227.249.18]> <200105300041.UAA22410@astro.cs.utk.edu> <Pine.GSO.4.00.10105281945410.5818-100000@sandra.lysator.liu.se> <20010528191702.1600.qmail@cr.yp.to> <p0510030eb7389ab8633e@[165.227.249.18]> <20010529042557.13041.qmail@cr.yp.to> <p05100323b739767904cf@[165.227.249.18]> <20010529042557.13041.qmail@cr.yp.to> <Pine.BSF.4.30.0105291200340.29244-100000@spider.nic-se.se> <20010601015014.I16547@arwen.cs.berkeley.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


"Adam M. Costello" wrote:

> If UTF-8 queries use a new type of request, then they can be used
> only if both the client's resolver and the local DNS server have been
> upgraded to support the new query format.  If you're upgrading the
> resolver, you might as well include an ACE encoder/decoder, because
> ACE queries will always work, even before the local DNS server has
> been upgraded.  And once you have an ACE encoder/decoder, why bother
> implementing the new query format?  Applications will never know or
> care which format the resolver is using.  Even if every other protocol
> and application migrates to UTF-8 and forgets how to encode and decode
> ACE, the resolvers and DNS servers could still be speaking ACE to each
> other and the other protocols/applications would be oblivious.

This is missing a component, which is the resolver-application interface.
Applications store/display names that they are given by DNS, so DNS must
provide them with the data in the appropriate format. Although the
on-the-wire protocol can be ACE as you suggest, the resolver still needs a
way to remember the desired disposition format of the query results.

For example, assume that an ESMTP extension for UTF8 in Received headers
comes to pass, and everybody agrees that displaying the headers in UTF8 is
beneficial to the user community, blah blah blah. When the MTA issues a
reverse lookup for the domain name associated with the IP addr, it doesn't
matter what format DNS uses, but the local resolver still needs to know
that the answer data should be returned in UTF8.

I suppose that it's technically feasible to ask resolvers to maintain
state, but the latest round of proposals have been to use UTF8 as the
default encoding on the wire so that it's preserved end-to-end, with the
expectation that UTF8 will be the preferred default encoding for many
years to come.

> It looks to me like allowing UTF-8 in regular DNS queries may be more
> trouble than it's worth,

Yes

> and creating a new query format just for UTF-8 is certainly more
> trouble than it's worth.

No. The EDNS message is already defined and is required/used for things
like A6 and DNAME already. This would just be another usage of that
message. It also allows us to resolve the sizing problems.

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



From owner-idn@ops.ietf.org  Thu May 31 23:50:59 2001
Received: from psg.com (exim@[147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA15057
	for <idn-archive@lists.ietf.org>; Thu, 31 May 2001 23:50:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.16 #1)
	id 155fmk-000HfK-00
	for idn-data@psg.com; Thu, 31 May 2001 20:39:38 -0700
Received: from above.proper.com ([208.184.76.39])
	by psg.com with esmtp (Exim 3.16 #1)
	id 155fmj-000HfD-00
	for idn@ops.ietf.org; Thu, 31 May 2001 20:39:37 -0700
Received: from [165.227.249.18] (ip18.proper.com [165.227.249.18])
	by above.proper.com (8.9.3/8.9.3) with ESMTP id UAA15082;
	Thu, 31 May 2001 20:39:32 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p05100334b73cbe43537d@[165.227.249.18]>
In-Reply-To: <20010601030754.N16547@arwen.cs.berkeley.edu>
References: <5.1.0.14.1.20010525083737.029ba370@mail.viagenie.qc.ca>
 <p05100336b7342f40ac9b@[165.227.249.18]>
 <20010601030754.N16547@arwen.cs.berkeley.edu>
Date: Thu, 31 May 2001 20:38:37 -0700
To: "Adam M. Costello" <amc@cs.berkeley.edu>, idn@ops.ietf.org
From: Paul Hoffman / IMC <phoffman@imc.org>
Subject: Re: [idn] nameprep
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-idn@ops.ietf.org
Precedence: bulk

At 3:07 AM +0000 6/1/01, Adam M. Costello wrote:
>Paul Hoffman / IMC <phoffman@imc.org> wrote:
>
>>  need to finish nameprep, which at this point is finished other than it
>>  does not address the new characters added in Unicode 3.1.
>
>Nameprep currently includes the following steps:
>
>     KC-normalize
>     map
>     KC-normalize
>     prohibit

Er, no it doesn't. It only includes map->normalize->prohibit.

--Paul Hoffman, Director
--Internet Mail Consortium



