RE: Punycode at ASCII for IDN & MDN via Y2K Project Management
linuxa linux <linuxalinux@yahoo.co.uk> Tue, 11 November 2008 20:32 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 B52263A68C5; Tue, 11 Nov 2008 12:32:12 -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 2C6503A68C5 for <ietf@core3.amsl.com>; Tue, 11 Nov 2008 12:32:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.995
X-Spam-Level:
X-Spam-Status: No, score=-3.995 tagged_above=-999 required=5 tests=[AWL=0.604, BAYES_00=-2.599, 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 YmAnNqk1-0PM for <ietf@core3.amsl.com>; Tue, 11 Nov 2008 12:32:10 -0800 (PST)
Received: from web25305.mail.ukl.yahoo.com (web25305.mail.ukl.yahoo.com [217.12.10.77]) by core3.amsl.com (Postfix) with SMTP id AD2833A67A5 for <ietf@ietf.org>; Tue, 11 Nov 2008 12:32:09 -0800 (PST)
Received: (qmail 82003 invoked by uid 60001); 11 Nov 2008 20:32:10 -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:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=XgaEOnmU12aqZo2zmUHf3gAN5+PVIPrM+4R2ImMXvOFwEd7ovibjuxNRTSTVqsY0NYiku/0rtC1y92fLiFbuLuepps62A/ys11H3UoHZ9B6/CcPciy5YzuA7sbVl235oz+wRtpED9saofQH0qNt2S2OF9iD7xqqSaKduM1vW8Xc=;
X-YMail-OSG: zsfm1_oVM1kNkN2B7CySbmPUog9vG_neNTbJF9uetzRrFJ8ymiXTrSmMmnE.Cwhx.AFqsC8fyptg5tecg7IdcMLO4Vo5bmbQGkKuitwm_U35HMixv9buc5PnnAQ3ppICmPsZjlOr8x9Ff5XWEV.XFeb9gjzV0gD3vktlTvd5.Zhiq0C59GPFE3uIcEHO
Received: from [62.69.37.89] by web25305.mail.ukl.yahoo.com via HTTP; Tue, 11 Nov 2008 20:32:09 GMT
X-Mailer: YahooMailWebService/0.7.260.1
Date: Tue, 11 Nov 2008 20:32:09 +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
MIME-Version: 1.0
Message-ID: <35907.81988.qm@web25305.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
Correction 1: "FUD (Fear, Uncertainty and Doubt)" Correction 2: "This is then your goal at the internet/web, it then is also related to your passive/active goal beyond internet/web technical activities." Corrected also at below emailed copy. Regards Meeku http://twitter.com/nepotism --- On Tue, 11/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: Tuesday, 11 November, 2008, 8:20 PM > --- On Tue, 11/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: Tuesday, 11 November, 2008, 9:36 AM > > > > > .......... without messing up the registrations that > > have been there for decades. > > The proposal is for new registrations, why twist the issue? > Previous registrations would become sort after learning > curve developments like I said to you. > > > > ASCII is also *machine code* for goodness sake! You > just do > > not see it as machine code because virtually all > software > > knows how to translate it to something you can read. > Any > > information stored on computers and transmitted over > digital > > networks is *machine code* - it is only a matter of > whether > > your software can present this or that machine code in > > human-readable form or not. > > You are putting a molecular backend eye to ASCII, when you > know quite well we are discussing from a user and practical > layer, see http://en.wikipedia.org/wiki/Image:ASCII_full.svg > That image shows you "Complete set of printable ASCII > characters" and the letters are roman/latin based > letters. These and a few symbols are what the frontend > internet/web user sees / is able to see at the frontend > layer. I am concerned about the nepotistic network that has > developed where a shortcut is being given to ASCII > roman/latin character based language at the frontend layer > however for the non-ASCII based languages the user gets an > almost backend / machine code service. Thus the proposal is > to give a equal field where all users get a frontend layer > service. This proposal also would bring about MDN > (Multilingual Domain Names) an issue that you are totally > ignoring. > > > > .......you can't just update > > existing registrations to new format instantly on > millions > > of DNS servers all over the World operated by > different > > organizations. If ICANN starts doing that, the whole > > domain-name-lookup infrastructure will submerge in > complete > > chaos for months, which would render the Internet > virtually > > unusable. > > However you are accusing without any technical basis and > all your arguments are FUD (Fear, Uncertainty and Doubt). > You know that IDN is based on ASCII machine code thus > non-IDN / ASCII registrations should also use ASCII machine > code. You want ASCII at the frontend however you should not > have a nepotistic service, quite the opposite you need to > implement an equal service to all users at the frontend > layer. Thus you need to put the equal service for all users > not that you give one user class a poor frontend layer > that's almost backend machine code and another class a > rich frontend layer. Then there is a class that want MDN > (Multilingual Domain Names) however you are basically say > don't give them any service. Thus your proposal is a > nepotism one where only close conspiratorial charactered > friends get a real frontend service and those that are not > have to become close conspiratorial charactered friends. > This is then your goal at the internet/web, it > then is also related to your passive/active goal beyond > internet/web technical activities. > > > Regards > > > > Meeku > http://twitter.com/nepotism _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Punycode at ASCII for IDN & MDN via Y2K Project M… linuxa linux
- RE: Punycode at ASCII for IDN & MDN via Y2K Proje… Ruszlan Gaszanov
- RE: Punycode at ASCII for IDN & MDN via Y2K Proje… Ruszlan Gaszanov
- RE: Punycode at ASCII for IDN & MDN via Y2K Proje… linuxa linux
- RE: Punycode at ASCII for IDN & MDN via Y2K Proje… linuxa linux
- RE: Punycode at ASCII for IDN & MDN via Y2K Proje… Ruszlan Gaszanov
- RE: Punycode at ASCII for IDN & MDN via Y2K Proje… linuxa linux
- RE: Punycode at ASCII for IDN & MDN via Y2K Proje… linuxa linux