RE: Punycode at ASCII for IDN & MDN via Y2K Project Management

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Further to what I wrote yesterday, "the 2 IDN algorithms: ToASCII and ToUnicode perhaps would need tweaks hence ToASCII2 and ToUnicode2 with perhaps ASCII registrations needing also an ACE sort prefix, say yn-- similar to xn-- that are put for IDN.  This development could then allow MDN (Multilingual Domain Names) that would help the users that are multilingual / would like multilingual text at domain name platform."

You can have for MDN another ACE sort prefix, say zn-- to distinguish them from IDN and ASCII registrations.


Regards


Meeku



--- On Mon, 10/11/08, linuxa linux <linuxalinux@xxxxxxxxxxx> wrote:

> From: linuxa linux <linuxalinux@xxxxxxxxxxx>
> Subject: RE: Punycode at ASCII for IDN & MDN via Y2K Project Management
> To: ietf@xxxxxxxx, unicode@xxxxxxxxxxx
> Cc: "Ruszlan Gaszanov" <ruszlan@xxxxxxxxx>
> Date: Monday, 10 November, 2008, 11:15 PM
> --- On Sun, 9/11/08, Ruszlan Gaszanov
> <ruszlan@xxxxxxxxx> wrote:
> 
> > From: Ruszlan Gaszanov <ruszlan@xxxxxxxxx>
> > Subject: RE: Punycode at ASCII for IDN & MDN via
> Y2K Project Management
> > To: linuxalinux@xxxxxxxxxxx, ietf@xxxxxxxx
> > Date: Sunday, 9 November, 2008, 10:21 PM
> 
> 
> > ......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.
> 
> > As soon as you want to encode ASCII characters with
> > something else, you'll
> > need a new parallel DNS infrastructure and at this
> point a
> > new version of
> > DNS protocol that works.......
> 
> You got this wrong because when you Punycode via Punycode2
> ASCII registrations you will have ASCII letters however they
> will be in machine  code, same as IDN thus equal virtue and
> for ASCII registrations to be viewed they will be viewed
> similarly as IDN (Internationalized Domain Names /
> Internationalised Domain Names) and here also equal virtue. 
>   
> 
> > .......But the bottom line is that there is no
> > way to develop a
> > "new punycode" encoding ASCII domain names
> with
> > something else then ASCII
> > and implement that on existing DNS infrastructure
> without
> > completely
> > breaking the Internet, period.  
> 
> Again you are putting something which I have not said for
> Punycode2.  While you wait for learning curve developments,
> I suggest you use ASCII based letters for Punycode 2 however
> you machine code the ASCII registrations like you are doing
> with IDN. 
> 
> I am not a technical expert, however based on what I have
> gleaned can I suggest the 2 IDN algorithms: ToASCII and
> ToUnicode perhaps would need tweaks hence ToASCII2 and
> ToUnicode2 with perhaps ASCII registrations needing also an
> ACE sort prefix, say yn-- similar to xn-- that are put for
> IDN.  This development could then allow MDN (Multilingual
> Domain Names) that would help the users that are
> multilingual / would like multilingual text at domain name
> platform. 
> 
> I hope this signals to you the urgency that is required for
> implementing.
> 
> 
> 
> Regards
> 
> 
> Meeku


      
_______________________________________________

Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]