Re: [idn] Comments on protocol drafts

[bill@mail.nic.nu (J. William Semich)]

At 07:01 AM 2/7/00 +0100, you wrote:
<snip>...

> If ASCII is not to be
>encoded in domain names, I see no reason for it to be just because
>there are one or two non-ASCII characters as well in the string.
>
>Therefore, I propose the following requirement:
>
>  If an encoding is used, the ASCII characters in a string must not
>  be encoded in different ways depending on what other characters
>  the string contains.
>
>
>Then, of course, as it seems the discussion about whether to cludge
>around old standards or not will be unavoidable later on. I think
>I've already made my point a month ago...


Problem solved, according to RFC 2044:

Network Working Group                                       F. Yergeau
Request for Comments: 2279                           Alis Technologies
Obsoletes: 2044                                           January 1998
Category: Standards Track


              UTF-8, a transformation format of ISO 10646
<snip>

...UTF-8, the object of this memo, has the characteristic of preserving the
full US-ASCII range, providing compatibility with file systems, parsers and
other software that rely on US-ASCII values but are transparent to other
values....

<end of excerpt>

As I have said, why invent something to solve a "problem" when it has
already been solved?

Bill Semich
.NU Domain