Re: [DNSOP] draft-liman-tld-names-04

Richard Clayton <richard@highwayman.com> Tue, 16 November 2010 01:03 UTC

Return-Path: <richard@highwayman.com>
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B05A3A6C68 for <dnsop@core3.amsl.com>; Mon, 15 Nov 2010 17:03:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 9w1MGgwcGpXP for <dnsop@core3.amsl.com>; Mon, 15 Nov 2010 17:03:06 -0800 (PST)
Received: from lon1-msapost-1.mail.demon.net (lon1-msapost-1.mail.demon.net [195.173.77.180]) by core3.amsl.com (Postfix) with ESMTP id 114EF3A6C62 for <dnsop@ietf.org>; Mon, 15 Nov 2010 17:03:05 -0800 (PST)
Received: from cpc2-cmbg9-0-0-cust25.5-4.cable.virginmedia.com ([82.16.100.26] helo=happyday.al.cl.cam.ac.uk) by lon1-post-1.mail.demon.net with esmtpsa (AUTH happyday) (SSLv3:AES256-SHA:256) (Exim 4.69) id 1PI9xb-0003LB-Wq for dnsop@ietf.org; Tue, 16 Nov 2010 01:03:47 +0000
Message-ID: <GblCgSCaed4MFAqZ@highwayman.com>
Date: Tue, 16 Nov 2010 01:00:10 +0000
To: dnsop@ietf.org
From: Richard Clayton <richard@highwayman.com>
References: <61252B4A-571B-4879-B945-556C03DE2A96@frobbit.se> <4CDDD642.8080108@necom830.hpcl.titech.ac.jp> <FB73AEDC-2B5E-48F9-BCA5-2637CAF6B6A4@frobbit.se> <4CDE6D2D.40805@necom830.hpcl.titech.ac.jp> <4819246C-FF1F-456D-9732-51510F0537A1@frobbit.se> <4CE0F829.1010605@necom830.hpcl.titech.ac.jp> <7F03C666-16F8-49E4-BC56-F5DD441DD970@frobbit.se> <4CE1A110.1060403@necom830.hpcl.titech.ac.jp> <20101115213532.GD322@shinkuro.com> <4CE1AAEC.80906@necom830.hpcl.titech.ac.jp> <20101115221534.GE322@shinkuro.com> <4CE1B830.5040804@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4CE1B830.5040804@necom830.hpcl.titech.ac.jp>
MIME-Version: 1.0
X-Mailer: Turnpike Integrated Version 5.03 M <370$+7Qf77vdnOKLcua+dOjCxu>
Subject: Re: [DNSOP] draft-liman-tld-names-04
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Nov 2010 01:03:07 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In message <4CE1B830.5040804@necom830.hpcl.titech.ac.jp>, Masataka Ohta
<mohta@necom830.hpcl.titech.ac.jp> writes

>I already gave an example of capital form of 'c' with cedille is
>often plain 'C' without cedille 

That, as I understand it, is the convention in mainland France.

>and seldom 'C' with cedille,

That, as it has been explained to me by the natives, is the convention
in Canadian French.

> even
>though tools of ISO 8859/1 and Unicode support 'C' with cedille.

These conventions (which I first came across when building multilingual
word processors in the early 1980s) very much predate these standards...

... I've no doubt that you can find erudite people in both France and
Canada to discuss how formally specified these rules are. My
understanding of these rules comes solely from ensuring that the locals
didn't get overexcited when we shipped product :-)

What it means is that if you're writing a word processor and forcing
material into upper case you need to understand if your text is written
in "French" or "Canadian French". If you're not sure -- or your text is
labelled "British English" then you have to take an arbitrary view as to
what the right thing to do might be, which is probably to make yourself
look good in Paris... the people in Montreal will be annoyed, but will
understand your dilemma.

>It's a fact, not an assumption.
>
>Moreover, it is a fact that ISO 8859/1 includes 'y' with
>diaeresis but not 'Y' with diaeresis, which means people
>accept plain 'Y' without diaeresis as capital form of 'y'
>with diaeresis whenISO 8859/1 was defined.

As a practical matter, if you're trying to avoid most (not all) of the
gotchas in case insensitive coding, you don't upper case strings, but
you force anything which is in upper case to a lower case form :)

- -=-=-=-

Anyway... since we're meant to be discussing the document, I admit to
being entirely puzzled by this section:

   A Restricted-A-Label is a DNS-Label which satisfies all the following
   conditions:

   1.  the DNS-Label is a valid A-Label according to [RFC5890];

   2.  the derived property value of all code points, as defined by
       [RFC5890], is PVALID;

   3.  the general category of all code points, is one of { Ll, Lo, Lm,
       Mn }.

The reason I'm puzzled is that RFC5890 doesn't discuss what "property"
is and PVALID seems to be in a table in a different document (and so
doesn't appear in RFC5890 at all). ie: I think the reference to RFC5890
in #2 may be a typo.

I would also like to know where I'd go to look up what a category is ...

... I think what this is intending to say is that you can have a TLD of
".2go" but only if there's an xn-- at the front of the whole thing :)

- -- 
richard.clayton@cl.cam.ac.uk                     "Nothing seems the same
                          Still you never see the change from day to day
                                And no-one notices the customs slip away"

-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1

iQA/AwUBTOHXmpoAxkTY1oPiEQIpKwCdGtudUojdMUOEQN1IIjbSkuiP77YAoIeu
GNyjC9rxEyeM5/vtQwKFqCsU
=BTkU
-----END PGP SIGNATURE-----