twitter.com/nepotism
--- On Tue, 11/11/08, linuxa linux <[EMAIL PROTECTED]> wrote:
> From: linuxa linux <[EMAIL PROTECTED]>
> Subject: RE: Punycode at ASCII for IDN & MDN via Y2K Project Management
> To: ietf@ietf.org, [EMAIL PROTECTED]
> Cc: "Ruszlan Gaszanov" &l
--- On Tue, 11/11/08, Ruszlan Gaszanov <[EMAIL PROTECTED]> wrote:
> From: Ruszlan Gaszanov <[EMAIL PROTECTED]>
> Subject: RE: Punycode at ASCII for IDN & MDN via Y2K Project Management
> To: [EMAIL PROTECTED], ietf@ietf.org
> Date: Tuesday, 11 November, 2008, 9:3
>> ..ASCII domain names *are* in fact
>> punycode domain names
>> by definition.
>
> That's the problem and the reason for Punycode2 allowing ASCII
> registrations to be Punycoded via Punicode2.
This is called *backward compatibility* and this is what permits punycode
registrations to be im
nuxa linux <[EMAIL PROTECTED]> wrote:
> From: linuxa linux <[EMAIL PROTECTED]>
> Subject: RE: Punycode at ASCII for IDN & MDN via Y2K Project Management
> To: ietf@ietf.org, [EMAIL PROTECTED]
> Cc: "Ruszlan Gaszanov" <[EMAIL PROTECTED]>
> Date: Monday, 1
--- On Sun, 9/11/08, Ruszlan Gaszanov <[EMAIL PROTECTED]> wrote:
> From: Ruszlan Gaszanov <[EMAIL PROTECTED]>
> Subject: RE: Punycode at ASCII for IDN & MDN via Y2K Project Management
> To: [EMAIL PROTECTED], ietf@ietf.org
> Date: Sunday, 9 November, 2008, 10:21 PM
Meeku,
> Punycode exists at the Whois for Internationalised Domain Names and you
> could easily put a Y2K project management with a timeline for ending old
> type ASCII registrations and where new type Punycode registrations would
> commence at ASCII names. ASCII names would get processed via
Meeku,
Ok, I could go into more details and explain why your proposal is extremely
problematic from the technical point of view... but I don't believe Unicode
mailing list is the proper place to discuss this topic, since Internet
protocols are not directly related to the Unicode Standard. Standard