Re: [Lucid] FW: [mark@macchiato.com: Re: Non-normalizable diacritics - new property]
Andrew Sullivan <ajs@anvilwalrusden.com> Thu, 19 March 2015 02:30 UTC
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: lucid@ietfa.amsl.com
Delivered-To: lucid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB6461A7D84 for <lucid@ietfa.amsl.com>; Wed, 18 Mar 2015 19:30:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level:
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B2QJnC-zw-Hw for <lucid@ietfa.amsl.com>; Wed, 18 Mar 2015 19:30:35 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5B281A7035 for <lucid@ietf.org>; Wed, 18 Mar 2015 19:30:35 -0700 (PDT)
Received: from mx1.yitter.info (unknown [67.211.120.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id BE80B8A035 for <lucid@ietf.org>; Thu, 19 Mar 2015 02:30:34 +0000 (UTC)
Date: Wed, 18 Mar 2015 22:30:30 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: lucid@ietf.org
Message-ID: <20150319023029.GA6046@mx1.yitter.info>
References: <20150311013300.GC12479@dyn.com> <CA+9kkMDZW9yPtDxtLTfY1=VS6itvHtXHF1qdZKtXdwwORwqnew@mail.gmail.com> <55008F97.8040701@ix.netcom.com> <CA+9kkMAcgSA1Ch0B9W1Np0LMn2udegZ=AzU1b26dAi+SDcbGgg@mail.gmail.com> <CY1PR0301MB07310C68F6CFDD46AE22086F82190@CY1PR0301MB0731.namprd03.prod.outlook.com> <20150311200941.GV15037@mx1.yitter.info> <CY1PR0301MB0731F4EBE5EB5C3340F7059282190@CY1PR0301MB0731.namprd03.prod.outlook.com> <20150319014018.GI5743@mx1.yitter.info> <BLUPR03MB1378184CE32E928A3086665582010@BLUPR03MB1378.namprd03.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <BLUPR03MB1378184CE32E928A3086665582010@BLUPR03MB1378.namprd03.prod.outlook.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/gl5vpVUcXjX4bxUNNcej8chG20E>
Subject: Re: [Lucid] FW: [mark@macchiato.com: Re: Non-normalizable diacritics - new property]
X-BeenThere: lucid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Locale-free UniCode Identifiers \(LUCID\)" <lucid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lucid>, <mailto:lucid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lucid/>
List-Post: <mailto:lucid@ietf.org>
List-Help: <mailto:lucid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lucid>, <mailto:lucid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Mar 2015 02:30:37 -0000
On Thu, Mar 19, 2015 at 02:11:56AM +0000, Shawn Steele wrote: > > At every level. DNS names are exact-match. Each identifier is unique. > > For the machine, sure. But if you throw in font weirdness and stuff, they become non-unique (to humans, not to machines) even in ASCII. To make them be more unique one has to impose more rules, like "use a decent font", "lowercase everything". Etc. > Yes. That's what we're trying to understand. > No, even all NFC or NFKC would be 100% unique to the machine This is either tautologically true, or false. Certainly we learned with IDNA2003 that NFKC doesn't work, because while it's good for increasing match probability the identifiers aren't stable. So when they're handed around through different environments, stuff happens that is bad. > What I'm questioning is how unique is good enough? Surely that's part of what we're trying to understand? > By your analogy, adding a bunch of laws isn't necessarily going to stop crime. Similarity in one dimension of an analogy doesn't entail similarity in all of them: if there were no differences, it wouldn't be an analogy. In this case, I think you have made a syllogistic mistake of conflating "all" and "some", but I suspect the analogy is just a distraction. The point is merely that you cannot get from "this won't ever be pefect" to "therefore we shouldn't even try" without a bunch more premises. > > I agree, with the caveat that we also balance the cost and the benefits/risk. "As safe as possible" would argue against allowing both 0 and O or l and 1 to exist. Almost nobody's argued that, so I don't think we want "As safe as possible". > And hence, a BoF to try to understand these issues. > > We do seem to have some desire to be linguistic. Otherwise Sharp-S and Greek didn't need touched. We have people who want identifiers that work as useful things in their writing systems. And sharp-s and sigma seemed to be cases where people were quite surprised, which means that the identifers are less useful (because if the identifier system furnishes you with surprises, that's inconvenient). This new set of cases is in fact another set of lurking surprises, which is why some of us are concerned about these cases. > I think the opinions of the computer scientists and users in marketing departments may differ greatly here. Many users treat domain names more as a natural linguistic thing than a mathematical identifier. Enough to sue over names. > I think speculating about the anthropololical facts here is going to lead us to grief. Let's stick with a domain of discourse we know well. Best regards, A -- Andrew Sullivan ajs@anvilwalrusden.com
- [Lucid] [mark@macchiato.com: Re: Non-normalizable… Andrew Sullivan
- Re: [Lucid] [mark@macchiato.com: Re: Non-normaliz… Ted Hardie
- Re: [Lucid] [mark@macchiato.com: Re: Non-normaliz… Ted Hardie
- Re: [Lucid] [mark@macchiato.com: Re: Non-normaliz… Shawn Steele
- Re: [Lucid] [mark@macchiato.com: Re: Non-normaliz… Andrew Sullivan
- [Lucid] FW: [mark@macchiato.com: Re: Non-normaliz… Shawn Steele
- Re: [Lucid] FW: [mark@macchiato.com: Re: Non-norm… Andrew Sullivan
- Re: [Lucid] FW: [mark@macchiato.com: Re: Non-norm… Shawn Steele
- Re: [Lucid] FW: [mark@macchiato.com: Re: Non-norm… Andrew Sullivan
- Re: [Lucid] FW: [mark@macchiato.com: Re: Non-norm… Asmus Freytag
- Re: [Lucid] FW: [mark@macchiato.com: Re: Non-norm… John C Klensin
- Re: [Lucid] FW: [mark@macchiato.com: Re: Non-norm… Shawn Steele
- Re: [Lucid] FW: [mark@macchiato.com: Re: Non-norm… Shawn Steele
- Re: [Lucid] FW: [mark@macchiato.com: Re: Non-norm… John C Klensin
- Re: [Lucid] FW: [mark@macchiato.com: Re: Non-norm… Shawn Steele
- Re: [Lucid] FW: [mark@macchiato.com: Re: Non-norm… Asmus Freytag
- Re: [Lucid] FW: [mark@macchiato.com: Re: Non-norm… John C Klensin
- Re: [Lucid] FW: [mark@macchiato.com: Re: Non-norm… Asmus Freytag
- Re: [Lucid] FW: [mark@macchiato.com: Re: Non-norm… Shawn Steele
- Re: [Lucid] FW: [mark@macchiato.com: Re: Non-norm… John C Klensin
- Re: [Lucid] FW: [mark@macchiato.com: Re: Non-norm… Andrew Sullivan
- Re: [Lucid] [mark@macchiato.com: Re: Non-normaliz… John C Klensin