Re: [idn] Alternative Solutions

["Edmon" <edmon@neteka.com>]

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