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

linuxa linux <linuxalinux@yahoo.co.uk> Tue, 11 November 2008 09:09 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1D0DC3A6AF3; Tue, 11 Nov 2008 01:09:38 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9520428C11D for <ietf@core3.amsl.com>; Tue, 11 Nov 2008 01:09:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.185
X-Spam-Level:
X-Spam-Status: No, score=-2.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XEmNQIQvOOMB for <ietf@core3.amsl.com>; Tue, 11 Nov 2008 01:09:36 -0800 (PST)
Received: from web25307.mail.ukl.yahoo.com (web25307.mail.ukl.yahoo.com [217.12.10.79]) by core3.amsl.com (Postfix) with SMTP id 71D9F3A6AF3 for <ietf@ietf.org>; Tue, 11 Nov 2008 01:09:36 -0800 (PST)
Received: (qmail 48559 invoked by uid 60001); 11 Nov 2008 09:09:36 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=tmoDc+Otz0+ISkBGdVq9n+YwGlUrql7nIFVYu45/nFPu3B0MShVnj9kNTKi3fP/4a09qHMomujPL3nbTLWJjSQxaHDD78A0N89umHHvbb7e686HTyQy69T51HVHxhI22H3/ztRYj6BAFwgB96CbGbI4s1ZDZnZCRhpUzrwIrghs=;
X-YMail-OSG: ufsWbWIVM1mFLnbmZCmMcLTth7Ff2w5nZxevQ5a1zmdkOP0MOgFCEXme5YSqUpfvXqt45Rt523T0CeV6XzXyLmvXpFHsJfMq.MamyTcu.BJB5BmDC5ch6w1JranYHW.0.jS.2G5Kb7u0fTCDZlapdq.z4XkP_n.VsEpniuk9wGNsNG_QIqqCODdCVa5w
Received: from [62.69.35.215] by web25307.mail.ukl.yahoo.com via HTTP; Tue, 11 Nov 2008 09:09:36 GMT
X-Mailer: YahooMailWebService/0.7.260.1
Date: Tue, 11 Nov 2008 09:09:36 +0000
From: linuxa linux <linuxalinux@yahoo.co.uk>
Subject: RE: Punycode at ASCII for IDN & MDN via Y2K Project Management
To: ietf@ietf.org, unicode@unicode.org
In-Reply-To: <605557.42973.qm@web25302.mail.ukl.yahoo.com>
MIME-Version: 1.0
Message-ID: <524127.48532.qm@web25307.mail.ukl.yahoo.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: linuxalinux@yahoo.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

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@yahoo.co.uk> wrote:

> From: linuxa linux <linuxalinux@yahoo.co.uk>
> Subject: RE: Punycode at ASCII for IDN & MDN via Y2K Project Management
> To: ietf@ietf.org, unicode@unicode.org
> Cc: "Ruszlan Gaszanov" <ruszlan@ather.net>
> Date: Monday, 10 November, 2008, 11:15 PM
> --- On Sun, 9/11/08, Ruszlan Gaszanov
> <ruszlan@ather.net> wrote:
> 
> > From: Ruszlan Gaszanov <ruszlan@ather.net>
> > Subject: RE: Punycode at ASCII for IDN & MDN via
> Y2K Project Management
> > To: linuxalinux@yahoo.co.uk, ietf@ietf.org
> > 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 mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf