Re: UCAS and related scripts
Eric Brunner-Williams <ebw@abenaki.wabanaki.net> Mon, 07 April 2008 17:09 UTC
Return-Path: <ebw@abenaki.wabanaki.net>
X-Original-To: idna-update@alvestrand.no
Delivered-To: idna-update@alvestrand.no
Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 0F27425973A for <idna-update@alvestrand.no>; Mon, 7 Apr 2008 19:09:13 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16254-07 for <idna-update@alvestrand.no>; Mon, 7 Apr 2008 19:09:01 +0200 (CEST)
X-Greylist: from auto-whitelisted by SQLgrey-1.6.7
Received: from abenaki.wabanaki.net (abenaki.wabanaki.net [65.99.1.130]) by eikenes.alvestrand.no (Postfix) with ESMTP id E8601259723 for <idna-update@alvestrand.no>; Mon, 7 Apr 2008 19:09:00 +0200 (CEST)
Received: from eric-brunner-williamss-macbook.local (dpc67142250094.direcpc.com [67.142.250.94]) by abenaki.wabanaki.net (8.14.2/8.14.2) with ESMTP id m37H864D028736; Mon, 7 Apr 2008 13:08:08 -0400 (EDT) (envelope-from ebw@abenaki.wabanaki.net)
Message-ID: <47FA551E.8010807@abenaki.wabanaki.net>
Date: Mon, 07 Apr 2008 10:08:46 -0700
From: Eric Brunner-Williams <ebw@abenaki.wabanaki.net>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: John C Klensin <klensin@jck.com>
References: <47F9662F.1070301@abenaki.wabanaki.net> <6.0.0.20.2.20080407150451.0711b1f0@localhost> <47FA4431.8070909@abenaki.wabanaki.net> <CF044A2BBA0F7B75EE77BACC@p3.JCK.COM>
In-Reply-To: <CF044A2BBA0F7B75EE77BACC@p3.JCK.COM>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at alvestrand.no
Cc: Martin Duerst <duerst@it.aoyama.ac.jp>, idna-update@alvestrand.no
Subject: Re: UCAS and related scripts
X-BeenThere: idna-update@alvestrand.no
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IDNA update work <idna-update.alvestrand.no>
List-Unsubscribe: <http://www.alvestrand.no/mailman/listinfo/idna-update>, <mailto:idna-update-request@alvestrand.no?subject=unsubscribe>
List-Archive: <http://www.alvestrand.no/pipermail/idna-update>
List-Post: <mailto:idna-update@alvestrand.no>
List-Help: <mailto:idna-update-request@alvestrand.no?subject=help>
List-Subscribe: <http://www.alvestrand.no/mailman/listinfo/idna-update>, <mailto:idna-update-request@alvestrand.no?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2008 17:09:13 -0000
John C Klensin wrote: > --On Monday, 07 April, 2008 08:56 -0700 Eric Brunner-Williams > <ebw@abenaki.wabanaki.net> wrote: > > >> Thank you for writing back. >> >> I'm more interested in the full stop (166e in your table) than >> in the symbol for a foreign cult (166d in the same text). >> >> I'm guessing that the rational for the full stop exclusion is >> not that its "confusingly similar to" some other character, >> but because it is functionally equivalent to "dot" (and is >> always translated into roman script as "."). >> >> Which rational, or something I've not guessed, is present? >> > > Eric, > > There may be some exceptions, for which it is better that you > check the I-Ds rather than my trying to summarize and get it > wrong but, in general, we have not disallowed characters because > of confusing similarity (aka "phishing risk") alone. In the > case of U+166E, it is excluded because it has the Unicode > General Category "Po" (other punctuation) and all such > characters are Disallowed. > > Correctly or incorrectly, U+166D is also in "Po". If I > correctly understand your comments and those of Michael Everson, > it might better have been classified as a symbol of some > flavor, but that would make no difference for our purposes, > since symbols are also disallowed. > > If you haven't had time to look at the Rationale document > (draft-klensin-idnabis-issues) yet, the general theme of this > part of the new approach is to return to the "LDH" rule > associated with traditional hostnames and then try to generalize > the "letter" and "digit" parts to corresponding characters in > Unicode, rather than, e.g., trying to see how much can be > included without causing problems. If that formulation is > working out well for indigenous North American writing systems, > it suggests that the rules we are using generally worked rather > than because we conducted a character-by-character examination > and then invented new classifications. > > john > > > > John, I've gotten through Patrick's draft, and Harald's draft, and a few pages into your protocol draft, so I haven't made it to your issues draft. Exclusion of a punctuation character as a punctuation character is reasonable. I've looked at a bunch of texts, from eastern Algonquin through (western) Carrier, not pretending that my Cree and Siksika is either necessary nor sufficient, and I can't see an interesting use case where an infix full-stop would work as a domain name. Just a reminder, I speak for myself, not the imaginary union of all literate and semi-literate present and future consumers and producers of text written in northern syllabic scripts, who may or may not find the DNS a source of joy and wonder. Eric
- A comment on draft-faltstrom-idnabis-tables-05.txt Eric Brunner-Williams
- Re: A comment on draft-faltstrom-idnabis-tables-0… Martin Duerst
- Re: A comment on draft-faltstrom-idnabis-tables-0… Michael Everson
- Re: A comment on draft-faltstrom-idnabis-tables-0… Eric Brunner-Williams
- UCAS and related scripts (was: Re: A comment on d… John C Klensin
- Re: UCAS and related scripts (was: Re: A comment … Michael Everson
- Re: UCAS and related scripts Eric Brunner-Williams
- Re: UCAS and related scripts Eric Brunner-Williams
- Re: A comment on draft-faltstrom-idnabis-tables-0… Martin Duerst
- draft-faltstrom-idnabis-tables-05.txt: 166D and 1… Patrik Fältström
- Re: draft-faltstrom-idnabis-tables-05.txt: 166D a… Eric Brunner-Williams