[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] RE: An idn protocol for consideration in making the requirements
- To: Patrik Fältström <firstname.lastname@example.org>,Karlsson Kent - keka <email@example.com>,firstname.lastname@example.org
- Subject: Re: [idn] RE: An idn protocol for consideration in making the requirements
- From: email@example.com (J. William Semich)
- Date: Thu, 03 Feb 2000 15:14:27 -0500
- Delivery-date: Thu, 03 Feb 2000 12:21:17 -0800
- Envelope-to: firstname.lastname@example.org
Fine with me. then let's be sure to not include anything like :
|In order to encode non-ASCII characters in DNS-compatible domain parts,
|they must be converted into legal characters. This is done with Base32
|encoding, described here.
|Table 3 shows the mapping between input bits and output characters in
|Base32. Design note: the digits used in Base32 are "2" through "8" ("8" ... <etc>
and deal with it at implementation.
At 08:45 PM 2/3/00 +0100, Patrik Fältström wrote:
>--On 2000-02-03 14.26 -0500, "J. William Semich" <email@example.com> wrote:
>> I agree with Kent on this. UTF-8 is it.
>Let's get done with the requirement before we talk about implementation,
>and, if we go with Unicode/10646 let's solve the meta-problem with sorting,
>casing and comparisons first, and encoding later.
>[As I told you in Stockholm :-) ] Coming up with an encoding is easy, doing
>the definitions on the meta-level is difficult.
President and Founder
.NU Domain Ltd