
From nobody Mon Mar  9 19:28:45 2015
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 E5C5A1A006F for <lucid@ietfa.amsl.com>; Mon,  9 Mar 2015 19:28:42 -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 EyXsU7Ywq7Zg for <lucid@ietfa.amsl.com>; Mon,  9 Mar 2015 19:28:41 -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 EFEA81A007A for <lucid@ietf.org>; Mon,  9 Mar 2015 19:28:24 -0700 (PDT)
Received: from mx1.yitter.info (unknown [50.189.173.0]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id B09868A031 for <lucid@ietf.org>; Tue, 10 Mar 2015 02:28:22 +0000 (UTC)
Date: Mon, 9 Mar 2015 22:28:21 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: lucid@ietf.org
Message-ID: <20150310022821.GK10131@mx1.yitter.info>
References: <A81A9FC9-9B62-4783-8C21-1ED462821835@viagenie.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <A81A9FC9-9B62-4783-8C21-1ED462821835@viagenie.ca>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/s4rAoPIhZcoAPEtcLKpuBZXBbQM>
Subject: Re: [Lucid] Problem statement and scope
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: Tue, 10 Mar 2015 02:28:43 -0000

Dear colleagues,

On Wed, Feb 25, 2015 at 10:13:33AM -0500, Marc Blanchet wrote:
> Hello,
>  First item to agree is the problem statement and scope.  Do we have a concensus on this? Let me start some (on purpose wide) questions:
> - is the problem only limited to a few codepoints where the pre-composed and composed forms are not normalized appropriately?
> - are we tackling homoglyphs?
> - else?

In response to these questions (admittedly, somewhat longer after the
fact than we'd have liked), Asmus and I have put together a draft
outlining what we understand to be the issues.  It's at
http://datatracker.ietf.org/doc/draft-sullivan-lucid-prob-stmt/.

We'd like very much to have some discussion on the list prior to
Dallas.  If we go into the meeting in Dallas without the necessary
preparation, the BoF will not tell us what to do next.

I also really strongly encourage people to read
draft-klensin-idna-5892upd-unicode70 (which is currently at -03 but, I
understand, may become an -04 in the very near future).  There's a lot
of very helpful background in it.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Tue Mar 10 18:33:57 2015
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 9CB171A9124 for <lucid@ietfa.amsl.com>; Tue, 10 Mar 2015 18:33:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.242
X-Spam-Level: 
X-Spam-Status: No, score=-0.242 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, GB_I_LETTER=-2, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=ham
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 GFyHNh4N-I7O for <lucid@ietfa.amsl.com>; Tue, 10 Mar 2015 18:33:54 -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 D30931A9088 for <lucid@ietf.org>; Tue, 10 Mar 2015 18:33:53 -0700 (PDT)
Received: from dyn.com (unknown [50.189.173.0]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 87C308A035 for <lucid@ietf.org>; Wed, 11 Mar 2015 01:33:52 +0000 (UTC)
Date: Tue, 10 Mar 2015 21:33:47 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: lucid@ietf.org
Message-ID: <20150311013300.GC12479@dyn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/XyU6AvtoALoz33jLLCZCBqkEgCc>
Subject: [Lucid] [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: Wed, 11 Mar 2015 01:33:56 -0000

Dear colleagues,

I hereby forward a message sent to a few people (including Asmus and
me) responding to the draft Asmus and I submitted yesterday.

I think this is a valuable response, though I am not sure I agree with
the approach it's taking.  Nevertheless, if we are to have any hope of
useful discussion in Dallas, it'd be good to have a look at the issues
in advance.

Best regards,

A

----- Forwarded message from Mark Davis ?️ <mark@macchiato.com> -----

Date: Tue, 10 Mar 2015 16:53:33 +0100
From: Mark Davis ?️ <mark@macchiato.com>
To: "Asmus Freytag (t)" <asmus-inc@ix.netcom.com>
Cc: Roozbeh Pournader <roozbeh@unicode.org>, Ken Whistler <kenwhistler@att.net>, Lisa
	Moore <lisam@us.ibm.com>, Michel Suignard <michel@suignard.com>, Markus
	Scherer <markus.icu@gmail.com>, Peter Constable <petercon@microsoft.com>,
	asullivan@dyn.com
Subject: Re: Non-normalizable diacritics - new property

+ Andrew

​> ​
In the meantime, the following has been released in preparation to the BOF
at the IETF meeting in Dallas.

​> ​
https://datatracker.ietf.org/doc/draft-sullivan-lucid-prob-stmt/
<https://datatracker.ietf.org/doc/draft-sullivan-lucid-prob-stmt/>


A well written report, and I think will help a great deal in resolving the
issues.

However, I'd strongly suggest a couple of changes to be more precise, and
thus avoid confusion (no pun intended). Although these may seem overly
formal, it is vital that the text be unambiguous, because the subject is so
very tricky, and it is thus so easy for people to be arguing based on
different interpretations of terms.

I will try to suggest some minimal changes, although it might be even
better with some more extensive rewording.

> I3 depends on the assumption that strings that will be used in
>   identifiers will not have any ambiguous matching to other strings.

When discussing strings, the term "ambiguous matching" is itself quite
ambiguous. I can have ambiguous matching with SJIS, for example, because
0x61 can be an 'a' or be part of another character; similarly there are
sequences of bytes ..XY.. where XY is a character or X is the end of one
character, and Y is the start of another. There are other forms of
ambiguity as well.

To eliminate this ambiguity, change every 8 other cases of "ambiguous/ity"
to prefix by "visually".

=>   identifiers will not be visually ambiguous with other strings used as
identifiers.
...

Look for other cases that could profit by that, such as like
"indistinguishable", and "matches".

See the later:

> Worse, identifiers, by their very nature, are things that must
>   provide reliable exact matches.  The whole point of an identifier is
>   that it provides a reliable way of uniquely naming the thing to be
>   identified.

In this section, to be precise, one would need to use "visual matches".
There are so, so many other ways strings can "match", like "have the same
code points".

However, the second sentence is still problematic. The characters in two
different strings that have similar appearances *are* different characters,
so the identifiers are "unique" in that sense. I guess what you meant to
say is something like:

=> it provides a reliable way of naming the thing to be identified, so as
to have a unique visual appearance.

Now, I think adding "visual" makes it clear that this paragraph needs some
work. As it stands, it would be too strong: it would call for eliminating
all homographs from all identifiers (eg disallowing "top" written in
Cyrillic characters.)

Later, there is a shift to confusability, but the text never relates that
directly to "confusability", which is what is elaborated upon.

(In general, many different phrases are (apparently) used to mean the same
thing: matching, indistinguishable, etc. While use of different terms makes
the text flow better, it has the big disadvantage that the reader never
knows whether phrase1 is meant to have a broader or narrower scope than
phrase2, or is meant to be identical. This would be a more extensive
change, however, to use more consistent defined language. Alternatively, at
the top you could say that when you use the terms "matches",
"indistinguishable", "ambiguous", etc. (you'll have to go through and find
them all) that what is meant is in terms of visual appearance.)

> (We use the term "homoglyph" strictly: code points that normally use the
same glyph when rendered.)

This needs a bit of work. First step would be:

Strings S1 and S2 are strict homoglyphs when they are different, yet
normally use the same glyph sequence when rendered.

Second would be to clarify "normally use". Does that mean "in the fonts
that most people use on most platforms"? There are often more significant
differences in serif fonts than non-serif, for example. Does that require
that the same font is used? There is huge variation among glyphs in fonts: ţ
 and ț may look the identical in font 1, and may be discernibly different
when both are in font2, but ţ in font1 may also look identical to ț in
font2. This also gets tricky because in many systems there is font
fallback. If a character is not in font1, then it might be displayed in a
fallback font 2.

Third would be to clarify "same glyph sequence". Does this mean pixel by
pixel? At all resolutions, or just some? Pixel by pixel is extremely strict.

One could try to bring in "intent", but that is very dicy. The intent is
from the Unicode encoding side may not be followed precisely by all or even
most font vendors. So it is of only theoretical value to point to intent.

The exact degree of strictness matters a great deal, because under a
sufficiently strict interpretation <ARABIC LETTER BEH (U+0628) + ARABIC
HAMZA ABOVE (U+0654)> is *not* a strict homograph for U+08A1, ARABIC LETTER
BEH WITH HAMZA ABOVE. That is, most current fonts do not display them as
pixel-for-pixel identical.

I know well that this is a continuum, but since you are focusing on strict
homoglyphs, you have to be clearer what you mean by that term; where you
draw the line. That also carries over into related terms elsewhere in the
document like "the same glyph"; does that mean in all fonts (or
some?/most?//common?), pixel for pixel or not, at all sizes or just
body-text sizes, etc.?

You might think about providing a definition for "the same glyph sequence",
then using that in the definition for homograph, and elsewhere in the text.

> Mitigation may be as simple as using a font
   designed to distinguish among different characters.

Should mention that in practice this is extremely difficult to enforce; it
only works in closed systems, those that have complete control over the
fonts used for display of the kinds of identifiers in question.

----- End forwarded message -----

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Wed Mar 11 10:39:24 2015
Return-Path: <john-ietf@jck.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 4FB211A0025 for <lucid@ietfa.amsl.com>; Wed, 11 Mar 2015 10:39:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 sKsdBZPVLWgD for <lucid@ietfa.amsl.com>; Wed, 11 Mar 2015 10:39:21 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D45871A0053 for <lucid@ietf.org>; Wed, 11 Mar 2015 10:39:19 -0700 (PDT)
Received: from [198.252.137.35] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1YVkbE-0000qy-HU; Wed, 11 Mar 2015 13:39:16 -0400
Date: Wed, 11 Mar 2015 13:39:11 -0400
From: John C Klensin <john-ietf@jck.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, lucid@ietf.org
Message-ID: <E27153A287CB94506F29BE00@JcK-HP8200.jck.com>
In-Reply-To: <20150310022821.GK10131@mx1.yitter.info>
References: <A81A9FC9-9B62-4783-8C21-1ED462821835@viagenie.ca> <20150310022821.GK10131@mx1.yitter.info>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.35
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/o4LVfd_gJcl83oL5RqEgu6VnCLk>
Subject: Re: [Lucid] Problem statement and scope
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: Wed, 11 Mar 2015 17:39:23 -0000

--On Monday, March 09, 2015 22:28 -0400 Andrew Sullivan
<ajs@anvilwalrusden.com> wrote:

> In response to these questions (admittedly, somewhat longer
> after the fact than we'd have liked), Asmus and I have put
> together a draft outlining what we understand to be the
> issues.  It's at
> http://datatracker.ietf.org/doc/draft-sullivan-lucid-prob-stmt
> /.
>...
> I also really strongly encourage people to read
> draft-klensin-idna-5892upd-unicode70 (which is currently at
> -03 but, I understand, may become an -04 in the very near
> future).  There's a lot of very helpful background in it.

Andrew, Thanks.  

draft-klensin-idna-5892upd-unicode70-04 is now awaiting posting.
Please don't bother with -03 -- the new version is a complete
rewrite, reflecting a very different understanding of the scope
and nature of the problem(s) compared to the one we had in early
January.

This version provides a much broader view of the problem than
its predecessor and explores some of the risks and solution
spaces.  WHile I recommend reading the whole thing, those who
don't intend to do so (it is about 24 pages of text exclusive of
references) may still benefit from a careful look at sections of
particular interest.   Those who decide to read it only in part
should include the introductory note in draft in their reading
-- it is important to understand what this version of the
document is... and isn't.

While we have been talking with Andrew, Asmus, and the members
of the IAB's I18n Program, this document was written
independently of the IAB Statement 
and the draft Andrews announces above (the other two may be a
bit less independent of it).  The documents represent different
perspective on the problem (including on the question of what
the problem actually is).   I hope that everyone who intends to
participate in the BoF will do so with awareness of both (or all
three) perspectives.

    john



From nobody Wed Mar 11 10:58:23 2015
Return-Path: <ted.ietf@gmail.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 334B61A1B28 for <lucid@ietfa.amsl.com>; Wed, 11 Mar 2015 10:58:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.999
X-Spam-Level: 
X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 LJgG-9u7xkJ0 for <lucid@ietfa.amsl.com>; Wed, 11 Mar 2015 10:58:16 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E30601A0211 for <lucid@ietf.org>; Wed, 11 Mar 2015 10:58:15 -0700 (PDT)
Received: by iecsl2 with SMTP id sl2so459246iec.1 for <lucid@ietf.org>; Wed, 11 Mar 2015 10:58:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FEIF8I8LefCgBVNZ+zDMIVvs8Bq6/q0vjcqcoDUwErM=; b=wFABt0HlAmGde9M3UeihxyCE5JANQWGMzbqoGJ07nAjDM/2TrtVmPDxbco3mzwlYmR vwUANfmLCNzke9VKUBnZeelbWJDUUPEFL5vftpygHpZ5788K0WDbOUhUwHUJfQ14eucZ EIiS+pOKWLw4enqeOQS8j2vaXDY2EbeK1OLgwRQQuTA3qox1KLygOuuWZhPdn2OXQbzu mXJs8xxQrH/2VuaI0126tFg1q+eJ+pmpZ7jNRUxFhBxqDf+NmWe6lBZEsrXuPkKwuaRq NVKrcYiruxbHGVbEaNhppFcbnnEjHSYaFdHgJFc3X4fj0Fyx5tDjcF2BvMAG30rTTUEx pPhQ==
MIME-Version: 1.0
X-Received: by 10.50.43.130 with SMTP id w2mr66933882igl.30.1426096695199; Wed, 11 Mar 2015 10:58:15 -0700 (PDT)
Received: by 10.42.129.17 with HTTP; Wed, 11 Mar 2015 10:58:15 -0700 (PDT)
In-Reply-To: <20150311013300.GC12479@dyn.com>
References: <20150311013300.GC12479@dyn.com>
Date: Wed, 11 Mar 2015 10:58:15 -0700
Message-ID: <CA+9kkMDZW9yPtDxtLTfY1=VS6itvHtXHF1qdZKtXdwwORwqnew@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary=089e0103de4eeecef6051107024d
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/PObGbYv_2MBxqZq61SEd7HI1pWM>
Cc: lucid@ietf.org
Subject: Re: [Lucid] [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: Wed, 11 Mar 2015 17:58:20 -0000

--089e0103de4eeecef6051107024d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Andrew,

So, I'm far from an expert on this, but I have some concerns about the
proposal to use "visually" here in the way Mark proposes.  If I understand
things correctly, this problem will also occur in any system that reads a
sequence of characters aloud.  That is, there is no way to distinguish in
an audio system between U+08A1 and the combination of U+0628 and U+0654.  T=
he
current draft talks about rendering the glyph, and I think that is closer
to correct--it doesn't matter whether the rendering is audio or graphical
for the problem to occur.  In the audio forms, the  quality of  running
text providing context vs. independent identifiers without it also seems
similar, at least to me.

I also don't believe that Mark's point about  parsing of byte sequences as
XY when X and Y or meant is quite correct; in string contexts that would be
a parsing error.  It might not be easily distinguished on the wire, but in
protocol slots, this seems to be an at best unrelated issue.  I may not be
familiar, though, with contexts in which this may occur.

regards,

Ted

On Tue, Mar 10, 2015 at 6:33 PM, Andrew Sullivan <ajs@anvilwalrusden.com>
wrote:

> Dear colleagues,
>
> I hereby forward a message sent to a few people (including Asmus and
> me) responding to the draft Asmus and I submitted yesterday.
>
> I think this is a valuable response, though I am not sure I agree with
> the approach it's taking.  Nevertheless, if we are to have any hope of
> useful discussion in Dallas, it'd be good to have a look at the issues
> in advance.
>
> Best regards,
>
> A
>
> ----- Forwarded message from Mark Davis ?=EF=B8=8F <mark@macchiato.com> -=
----
>
> Date: Tue, 10 Mar 2015 16:53:33 +0100
> From: Mark Davis ?=EF=B8=8F <mark@macchiato.com>
> To: "Asmus Freytag (t)" <asmus-inc@ix.netcom.com>
> Cc: Roozbeh Pournader <roozbeh@unicode.org>, Ken Whistler <
> kenwhistler@att.net>, Lisa
>         Moore <lisam@us.ibm.com>, Michel Suignard <michel@suignard.com>,
> Markus
>         Scherer <markus.icu@gmail.com>, Peter Constable <
> petercon@microsoft.com>,
>         asullivan@dyn.com
> Subject: Re: Non-normalizable diacritics - new property
>
> + Andrew
>
> =E2=80=8B> =E2=80=8B
> In the meantime, the following has been released in preparation to the BO=
F
> at the IETF meeting in Dallas.
>
> =E2=80=8B> =E2=80=8B
> https://datatracker.ietf.org/doc/draft-sullivan-lucid-prob-stmt/
> <https://datatracker.ietf.org/doc/draft-sullivan-lucid-prob-stmt/>
>
>
> A well written report, and I think will help a great deal in resolving th=
e
> issues.
>
> However, I'd strongly suggest a couple of changes to be more precise, and
> thus avoid confusion (no pun intended). Although these may seem overly
> formal, it is vital that the text be unambiguous, because the subject is =
so
> very tricky, and it is thus so easy for people to be arguing based on
> different interpretations of terms.
>
> I will try to suggest some minimal changes, although it might be even
> better with some more extensive rewording.
>
> > I3 depends on the assumption that strings that will be used in
> >   identifiers will not have any ambiguous matching to other strings.
>
> When discussing strings, the term "ambiguous matching" is itself quite
> ambiguous. I can have ambiguous matching with SJIS, for example, because
> 0x61 can be an 'a' or be part of another character; similarly there are
> sequences of bytes ..XY.. where XY is a character or X is the end of one
> character, and Y is the start of another. There are other forms of
> ambiguity as well.
>
> To eliminate this ambiguity, change every 8 other cases of "ambiguous/ity=
"
> to prefix by "visually".
>
> =3D>   identifiers will not be visually ambiguous with other strings used=
 as
> identifiers.
> ...
>
> Look for other cases that could profit by that, such as like
> "indistinguishable", and "matches".
>
> See the later:
>
> > Worse, identifiers, by their very nature, are things that must
> >   provide reliable exact matches.  The whole point of an identifier is
> >   that it provides a reliable way of uniquely naming the thing to be
> >   identified.
>
> In this section, to be precise, one would need to use "visual matches".
> There are so, so many other ways strings can "match", like "have the same
> code points".
>
> However, the second sentence is still problematic. The characters in two
> different strings that have similar appearances *are* different character=
s,
> so the identifiers are "unique" in that sense. I guess what you meant to
> say is something like:
>
> =3D> it provides a reliable way of naming the thing to be identified, so =
as
> to have a unique visual appearance.
>
> Now, I think adding "visual" makes it clear that this paragraph needs som=
e
> work. As it stands, it would be too strong: it would call for eliminating
> all homographs from all identifiers (eg disallowing "top" written in
> Cyrillic characters.)
>
> Later, there is a shift to confusability, but the text never relates that
> directly to "confusability", which is what is elaborated upon.
>
> (In general, many different phrases are (apparently) used to mean the sam=
e
> thing: matching, indistinguishable, etc. While use of different terms mak=
es
> the text flow better, it has the big disadvantage that the reader never
> knows whether phrase1 is meant to have a broader or narrower scope than
> phrase2, or is meant to be identical. This would be a more extensive
> change, however, to use more consistent defined language. Alternatively, =
at
> the top you could say that when you use the terms "matches",
> "indistinguishable", "ambiguous", etc. (you'll have to go through and fin=
d
> them all) that what is meant is in terms of visual appearance.)
>
> > (We use the term "homoglyph" strictly: code points that normally use th=
e
> same glyph when rendered.)
>
> This needs a bit of work. First step would be:
>
> Strings S1 and S2 are strict homoglyphs when they are different, yet
> normally use the same glyph sequence when rendered.
>
> Second would be to clarify "normally use". Does that mean "in the fonts
> that most people use on most platforms"? There are often more significant
> differences in serif fonts than non-serif, for example. Does that require
> that the same font is used? There is huge variation among glyphs in fonts=
:
> =C5=A3
>  and =C8=9B may look the identical in font 1, and may be discernibly diff=
erent
> when both are in font2, but =C5=A3 in font1 may also look identical to =
=C8=9B in
> font2. This also gets tricky because in many systems there is font
> fallback. If a character is not in font1, then it might be displayed in a
> fallback font 2.
>
> Third would be to clarify "same glyph sequence". Does this mean pixel by
> pixel? At all resolutions, or just some? Pixel by pixel is extremely
> strict.
>
> One could try to bring in "intent", but that is very dicy. The intent is
> from the Unicode encoding side may not be followed precisely by all or ev=
en
> most font vendors. So it is of only theoretical value to point to intent.
>
> The exact degree of strictness matters a great deal, because under a
> sufficiently strict interpretation <ARABIC LETTER BEH (U+0628) + ARABIC
> HAMZA ABOVE (U+0654)> is *not* a strict homograph for U+08A1, ARABIC LETT=
ER
> BEH WITH HAMZA ABOVE. That is, most current fonts do not display them as
> pixel-for-pixel identical.
>
> I know well that this is a continuum, but since you are focusing on stric=
t
> homoglyphs, you have to be clearer what you mean by that term; where you
> draw the line. That also carries over into related terms elsewhere in the
> document like "the same glyph"; does that mean in all fonts (or
> some?/most?//common?), pixel for pixel or not, at all sizes or just
> body-text sizes, etc.?
>
> You might think about providing a definition for "the same glyph sequence=
",
> then using that in the definition for homograph, and elsewhere in the tex=
t.
>
> > Mitigation may be as simple as using a font
>    designed to distinguish among different characters.
>
> Should mention that in practice this is extremely difficult to enforce; i=
t
> only works in closed systems, those that have complete control over the
> fonts used for display of the kinds of identifiers in question.
>
> ----- End forwarded message -----
>
> --
> Andrew Sullivan
> ajs@anvilwalrusden.com
>
> _______________________________________________
> Lucid mailing list
> Lucid@ietf.org
> https://www.ietf.org/mailman/listinfo/lucid
>

--089e0103de4eeecef6051107024d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:tahoma,s=
ans-serif;font-size:small">Hi Andrew,<br><br></div><div class=3D"gmail_defa=
ult" style=3D"font-family:tahoma,sans-serif"><font>So, I&#39;m far from an =
expert on this, but I have some concerns about the proposal to use &quot;vi=
sually&quot; here in the way Mark proposes.=C2=A0 If I understand things co=
rrectly, this problem will also occur in any system that reads a sequence o=
f characters aloud.=C2=A0 That is, there is no way to distinguish in an aud=
io system between<span style=3D"font-family:arial,helvetica,sans-serif"> U+=
08A1 and the combination of U+0628 and U+0654.=C2=A0 </span>The current dra=
ft talks about rendering the glyph, and I think that is closer to correct--=
it doesn&#39;t matter whether the rendering is audio or graphical for the p=
roblem to occur.=C2=A0 In the audio forms, the=C2=A0 quality of=C2=A0 runni=
ng text providing context vs. independent identifiers without it also seems=
 similar, at least to me.<br><br></font></div><div class=3D"gmail_default" =
style=3D"font-family:tahoma,sans-serif"><font>I also don&#39;t believe that=
 Mark&#39;s point about=C2=A0 parsing of byte sequences as XY when X and Y =
or meant is quite correct; in string contexts that would be a parsing error=
.=C2=A0 It might not be easily distinguished on the wire, but in protocol s=
lots, this seems to be an at best unrelated issue.=C2=A0 I may not be famil=
iar, though, with contexts in which this may occur.<br><br></font></div><di=
v class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif"><font>reg=
ards,<br><br></font></div><div class=3D"gmail_default" style=3D"font-family=
:tahoma,sans-serif;font-size:small"><font>Ted</font><br></div></div><div cl=
ass=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Mar 10, 2015 at =
6:33 PM, Andrew Sullivan <span dir=3D"ltr">&lt;<a href=3D"mailto:ajs@anvilw=
alrusden.com" target=3D"_blank">ajs@anvilwalrusden.com</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">Dear colleagues,<br>
<br>
I hereby forward a message sent to a few people (including Asmus and<br>
me) responding to the draft Asmus and I submitted yesterday.<br>
<br>
I think this is a valuable response, though I am not sure I agree with<br>
the approach it&#39;s taking.=C2=A0 Nevertheless, if we are to have any hop=
e of<br>
useful discussion in Dallas, it&#39;d be good to have a look at the issues<=
br>
in advance.<br>
<br>
Best regards,<br>
<br>
A<br>
<br>
----- Forwarded message from Mark Davis ?=EF=B8=8F &lt;<a href=3D"mailto:ma=
rk@macchiato.com">mark@macchiato.com</a>&gt; -----<br>
<br>
Date: Tue, 10 Mar 2015 16:53:33 +0100<br>
From: Mark Davis ?=EF=B8=8F &lt;<a href=3D"mailto:mark@macchiato.com">mark@=
macchiato.com</a>&gt;<br>
To: &quot;Asmus Freytag (t)&quot; &lt;<a href=3D"mailto:asmus-inc@ix.netcom=
.com">asmus-inc@ix.netcom.com</a>&gt;<br>
Cc: Roozbeh Pournader &lt;<a href=3D"mailto:roozbeh@unicode.org">roozbeh@un=
icode.org</a>&gt;, Ken Whistler &lt;<a href=3D"mailto:kenwhistler@att.net">=
kenwhistler@att.net</a>&gt;, Lisa<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Moore &lt;<a href=3D"mailto:lisam@us.ibm.com">l=
isam@us.ibm.com</a>&gt;, Michel Suignard &lt;<a href=3D"mailto:michel@suign=
ard.com">michel@suignard.com</a>&gt;, Markus<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Scherer &lt;<a href=3D"mailto:markus.icu@gmail.=
com">markus.icu@gmail.com</a>&gt;, Peter Constable &lt;<a href=3D"mailto:pe=
tercon@microsoft.com">petercon@microsoft.com</a>&gt;,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:asullivan@dyn.com">asullivan@=
dyn.com</a><br>
Subject: Re: Non-normalizable diacritics - new property<br>
<br>
+ Andrew<br>
<br>
=E2=80=8B&gt; =E2=80=8B<br>
In the meantime, the following has been released in preparation to the BOF<=
br>
at the IETF meeting in Dallas.<br>
<br>
=E2=80=8B&gt; =E2=80=8B<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-sullivan-lucid-prob-stmt/=
" target=3D"_blank">https://datatracker.ietf.org/doc/draft-sullivan-lucid-p=
rob-stmt/</a><br>
&lt;<a href=3D"https://datatracker.ietf.org/doc/draft-sullivan-lucid-prob-s=
tmt/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-sullivan-luc=
id-prob-stmt/</a>&gt;<br>
<br>
<br>
A well written report, and I think will help a great deal in resolving the<=
br>
issues.<br>
<br>
However, I&#39;d strongly suggest a couple of changes to be more precise, a=
nd<br>
thus avoid confusion (no pun intended). Although these may seem overly<br>
formal, it is vital that the text be unambiguous, because the subject is so=
<br>
very tricky, and it is thus so easy for people to be arguing based on<br>
different interpretations of terms.<br>
<br>
I will try to suggest some minimal changes, although it might be even<br>
better with some more extensive rewording.<br>
<br>
&gt; I3 depends on the assumption that strings that will be used in<br>
&gt;=C2=A0 =C2=A0identifiers will not have any ambiguous matching to other =
strings.<br>
<br>
When discussing strings, the term &quot;ambiguous matching&quot; is itself =
quite<br>
ambiguous. I can have ambiguous matching with SJIS, for example, because<br=
>
0x61 can be an &#39;a&#39; or be part of another character; similarly there=
 are<br>
sequences of bytes ..XY.. where XY is a character or X is the end of one<br=
>
character, and Y is the start of another. There are other forms of<br>
ambiguity as well.<br>
<br>
To eliminate this ambiguity, change every 8 other cases of &quot;ambiguous/=
ity&quot;<br>
to prefix by &quot;visually&quot;.<br>
<br>
=3D&gt;=C2=A0 =C2=A0identifiers will not be visually ambiguous with other s=
trings used as<br>
identifiers.<br>
...<br>
<br>
Look for other cases that could profit by that, such as like<br>
&quot;indistinguishable&quot;, and &quot;matches&quot;.<br>
<br>
See the later:<br>
<br>
&gt; Worse, identifiers, by their very nature, are things that must<br>
&gt;=C2=A0 =C2=A0provide reliable exact matches.=C2=A0 The whole point of a=
n identifier is<br>
&gt;=C2=A0 =C2=A0that it provides a reliable way of uniquely naming the thi=
ng to be<br>
&gt;=C2=A0 =C2=A0identified.<br>
<br>
In this section, to be precise, one would need to use &quot;visual matches&=
quot;.<br>
There are so, so many other ways strings can &quot;match&quot;, like &quot;=
have the same<br>
code points&quot;.<br>
<br>
However, the second sentence is still problematic. The characters in two<br=
>
different strings that have similar appearances *are* different characters,=
<br>
so the identifiers are &quot;unique&quot; in that sense. I guess what you m=
eant to<br>
say is something like:<br>
<br>
=3D&gt; it provides a reliable way of naming the thing to be identified, so=
 as<br>
to have a unique visual appearance.<br>
<br>
Now, I think adding &quot;visual&quot; makes it clear that this paragraph n=
eeds some<br>
work. As it stands, it would be too strong: it would call for eliminating<b=
r>
all homographs from all identifiers (eg disallowing &quot;top&quot; written=
 in<br>
Cyrillic characters.)<br>
<br>
Later, there is a shift to confusability, but the text never relates that<b=
r>
directly to &quot;confusability&quot;, which is what is elaborated upon.<br=
>
<br>
(In general, many different phrases are (apparently) used to mean the same<=
br>
thing: matching, indistinguishable, etc. While use of different terms makes=
<br>
the text flow better, it has the big disadvantage that the reader never<br>
knows whether phrase1 is meant to have a broader or narrower scope than<br>
phrase2, or is meant to be identical. This would be a more extensive<br>
change, however, to use more consistent defined language. Alternatively, at=
<br>
the top you could say that when you use the terms &quot;matches&quot;,<br>
&quot;indistinguishable&quot;, &quot;ambiguous&quot;, etc. (you&#39;ll have=
 to go through and find<br>
them all) that what is meant is in terms of visual appearance.)<br>
<br>
&gt; (We use the term &quot;homoglyph&quot; strictly: code points that norm=
ally use the<br>
same glyph when rendered.)<br>
<br>
This needs a bit of work. First step would be:<br>
<br>
Strings S1 and S2 are strict homoglyphs when they are different, yet<br>
normally use the same glyph sequence when rendered.<br>
<br>
Second would be to clarify &quot;normally use&quot;. Does that mean &quot;i=
n the fonts<br>
that most people use on most platforms&quot;? There are often more signific=
ant<br>
differences in serif fonts than non-serif, for example. Does that require<b=
r>
that the same font is used? There is huge variation among glyphs in fonts: =
=C5=A3<br>
=C2=A0and =C8=9B may look the identical in font 1, and may be discernibly d=
ifferent<br>
when both are in font2, but =C5=A3 in font1 may also look identical to =C8=
=9B in<br>
font2. This also gets tricky because in many systems there is font<br>
fallback. If a character is not in font1, then it might be displayed in a<b=
r>
fallback font 2.<br>
<br>
Third would be to clarify &quot;same glyph sequence&quot;. Does this mean p=
ixel by<br>
pixel? At all resolutions, or just some? Pixel by pixel is extremely strict=
.<br>
<br>
One could try to bring in &quot;intent&quot;, but that is very dicy. The in=
tent is<br>
from the Unicode encoding side may not be followed precisely by all or even=
<br>
most font vendors. So it is of only theoretical value to point to intent.<b=
r>
<br>
The exact degree of strictness matters a great deal, because under a<br>
sufficiently strict interpretation &lt;ARABIC LETTER BEH (U+0628) + ARABIC<=
br>
HAMZA ABOVE (U+0654)&gt; is *not* a strict homograph for U+08A1, ARABIC LET=
TER<br>
BEH WITH HAMZA ABOVE. That is, most current fonts do not display them as<br=
>
pixel-for-pixel identical.<br>
<br>
I know well that this is a continuum, but since you are focusing on strict<=
br>
homoglyphs, you have to be clearer what you mean by that term; where you<br=
>
draw the line. That also carries over into related terms elsewhere in the<b=
r>
document like &quot;the same glyph&quot;; does that mean in all fonts (or<b=
r>
some?/most?//common?), pixel for pixel or not, at all sizes or just<br>
body-text sizes, etc.?<br>
<br>
You might think about providing a definition for &quot;the same glyph seque=
nce&quot;,<br>
then using that in the definition for homograph, and elsewhere in the text.=
<br>
<br>
&gt; Mitigation may be as simple as using a font<br>
=C2=A0 =C2=A0designed to distinguish among different characters.<br>
<br>
Should mention that in practice this is extremely difficult to enforce; it<=
br>
only works in closed systems, those that have complete control over the<br>
fonts used for display of the kinds of identifiers in question.<br>
<br>
----- End forwarded message -----<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Andrew Sullivan<br>
<a href=3D"mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br>
<br>
_______________________________________________<br>
Lucid mailing list<br>
<a href=3D"mailto:Lucid@ietf.org">Lucid@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/lucid" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/lucid</a><br>
</font></span></blockquote></div><br></div>

--089e0103de4eeecef6051107024d--


From nobody Wed Mar 11 12:15:46 2015
Return-Path: <ted.ietf@gmail.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 675331A017C for <lucid@ietfa.amsl.com>; Wed, 11 Mar 2015 12:15:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.999
X-Spam-Level: 
X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 LpsHPOlUdjsG for <lucid@ietfa.amsl.com>; Wed, 11 Mar 2015 12:15:40 -0700 (PDT)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20FFF1A6ED9 for <lucid@ietf.org>; Wed, 11 Mar 2015 12:15:40 -0700 (PDT)
Received: by igbhl2 with SMTP id hl2so43031454igb.3 for <lucid@ietf.org>; Wed, 11 Mar 2015 12:15:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4BnD9CtaXT3fjhvyS+5ryCkls/xfbWhZ10D2LXhTBRg=; b=c0rYvShtQ9z6bC5yza6faVa/tJ8tj6PeYe3D+uTxUUEQPwB+mA0TjCj/ji/pVq8iCQ BhDsVhIx3SzMfamq3JjQGQw66uVrkQjXIid4VF71eUFzSk67TaVqgIFNDguwjffTN/me Hq2xDW/ExzhLCLBFudrSCUVh/XyRtJSE/qZ3ijLFxAs/xYHO7MdIlKihPJc9bYcnPopx Gcf3OCnX0nQChlvyOWXm0sqs8Ngp0YTzWSa48yn2W0Z5Qm0y25AmcRyy0I9LKOWfKrDm nFhck+0NDWIrGEJZs6PWi0E5v+GfxS7+NHcjuwf13Fq2r+sXWwOnxircGrBST+twNGGC sMmQ==
MIME-Version: 1.0
X-Received: by 10.42.41.148 with SMTP id p20mr42904755ice.62.1426101339498; Wed, 11 Mar 2015 12:15:39 -0700 (PDT)
Received: by 10.42.129.17 with HTTP; Wed, 11 Mar 2015 12:15:39 -0700 (PDT)
In-Reply-To: <55008F97.8040701@ix.netcom.com>
References: <20150311013300.GC12479@dyn.com> <CA+9kkMDZW9yPtDxtLTfY1=VS6itvHtXHF1qdZKtXdwwORwqnew@mail.gmail.com> <55008F97.8040701@ix.netcom.com>
Date: Wed, 11 Mar 2015 12:15:39 -0700
Message-ID: <CA+9kkMAcgSA1Ch0B9W1Np0LMn2udegZ=AzU1b26dAi+SDcbGgg@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: "Asmus Freytag (t)" <asmus-inc@ix.netcom.com>
Content-Type: multipart/alternative; boundary=20cf301d3a28c12e43051108179a
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/AGO563EHmipmURMZiGw-Drh2ncc>
Cc: lucid@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [Lucid] [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: Wed, 11 Mar 2015 19:15:44 -0000

--20cf301d3a28c12e43051108179a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 11, 2015 at 11:55 AM, Asmus Freytag (t) <asmus-inc@ix.netcom.co=
m
> wrote:

>  On 3/11/2015 10:58 AM, Ted Hardie wrote:
>
>  Hi Andrew,
>
>  So, I'm far from an expert on this, but I have some concerns about the
> proposal to use "visually" here in the way Mark proposes.  If I understan=
d
> things correctly, this problem will also occur in any system that reads a
> sequence of characters aloud.  That is, there is no way to distinguish in
> an audio system between U+08A1 and the combination of U+0628 and U+0654.
>
>
> Where do get that?
>
> U+0654 is used to represent a glottal stop, but my understanding is that
> U+08A1 was encoded partially because it represents a sound that does not
> have a glottal stop. If my understanding is correct, the distinction shou=
ld
> be quite audible.
>

I asked a native Arabic speaker about the systems she used and she played
them to check.  Those systems may be non-representative, though, or simply
wrong.  Or, rather than wrong, they may be tuned to a case in which the
result isn't audible.

Are we confident that this difference is general for the other cases?  If
so, that would be a very powerful way to explain the problem--code points
which are visually indistinguishable but would render differently in
audio.  (If it is not general, we still may want be cautious about focusing
solely on visual renderings).

regards,

Ted



>   The current draft talks about rendering the glyph, and I think that is
> closer to correct--it doesn't matter whether the rendering is audio or
> graphical for the problem to occur.  In the audio forms, the  quality of
> running text providing context vs. independent identifiers without it als=
o
> seems similar, at least to me.
>
>
> I think that the focus on visual as suggested by Mark ignores that there
> are identifiers for which the user community claims that certain visually
> distinct representations are considered "the same" by users, to the point
> that one cannot rely on users to faithfully retain which version of the
> identifier is the desired one.
>
> As the problem statement is concerned with general background, it is
> important to recognize such other levels of ambiguity exist.
>
> A./
>
>
>  I also don't believe that Mark's point about  parsing of byte sequences
> as XY when X and Y or meant is quite correct; in string contexts that wou=
ld
> be a parsing error.  It might not be easily distinguished on the wire, bu=
t
> in protocol slots, this seems to be an at best unrelated issue.  I may no=
t
> be familiar, though, with contexts in which this may occur.
>
>  regards,
>
>  Ted
>
> On Tue, Mar 10, 2015 at 6:33 PM, Andrew Sullivan <ajs@anvilwalrusden.com>
> wrote:
>
>> Dear colleagues,
>>
>> I hereby forward a message sent to a few people (including Asmus and
>> me) responding to the draft Asmus and I submitted yesterday.
>>
>> I think this is a valuable response, though I am not sure I agree with
>> the approach it's taking.  Nevertheless, if we are to have any hope of
>> useful discussion in Dallas, it'd be good to have a look at the issues
>> in advance.
>>
>> Best regards,
>>
>> A
>>
>> ----- Forwarded message from Mark Davis ?=EF=B8=8F <mark@macchiato.com> =
-----
>>
>> Date: Tue, 10 Mar 2015 16:53:33 +0100
>> From: Mark Davis ?=EF=B8=8F <mark@macchiato.com>
>> To: "Asmus Freytag (t)" <asmus-inc@ix.netcom.com>
>> Cc: Roozbeh Pournader <roozbeh@unicode.org>, Ken Whistler <
>> kenwhistler@att.net>, Lisa
>>         Moore <lisam@us.ibm.com>, Michel Suignard <michel@suignard.com>,
>> Markus
>>         Scherer <markus.icu@gmail.com>, Peter Constable <
>> petercon@microsoft.com>,
>>         asullivan@dyn.com
>> Subject: Re: Non-normalizable diacritics - new property
>>
>> + Andrew
>>
>> =E2=80=8B> =E2=80=8B
>> In the meantime, the following has been released in preparation to the B=
OF
>> at the IETF meeting in Dallas.
>>
>> =E2=80=8B> =E2=80=8B
>> https://datatracker.ietf.org/doc/draft-sullivan-lucid-prob-stmt/
>> <https://datatracker.ietf.org/doc/draft-sullivan-lucid-prob-stmt/>
>>
>>
>> A well written report, and I think will help a great deal in resolving t=
he
>> issues.
>>
>> However, I'd strongly suggest a couple of changes to be more precise, an=
d
>> thus avoid confusion (no pun intended). Although these may seem overly
>> formal, it is vital that the text be unambiguous, because the subject is
>> so
>> very tricky, and it is thus so easy for people to be arguing based on
>> different interpretations of terms.
>>
>> I will try to suggest some minimal changes, although it might be even
>> better with some more extensive rewording.
>>
>> > I3 depends on the assumption that strings that will be used in
>> >   identifiers will not have any ambiguous matching to other strings.
>>
>> When discussing strings, the term "ambiguous matching" is itself quite
>> ambiguous. I can have ambiguous matching with SJIS, for example, because
>> 0x61 can be an 'a' or be part of another character; similarly there are
>> sequences of bytes ..XY.. where XY is a character or X is the end of one
>> character, and Y is the start of another. There are other forms of
>> ambiguity as well.
>>
>> To eliminate this ambiguity, change every 8 other cases of "ambiguous/it=
y"
>> to prefix by "visually".
>>
>> =3D>   identifiers will not be visually ambiguous with other strings use=
d as
>> identifiers.
>> ...
>>
>> Look for other cases that could profit by that, such as like
>> "indistinguishable", and "matches".
>>
>> See the later:
>>
>> > Worse, identifiers, by their very nature, are things that must
>> >   provide reliable exact matches.  The whole point of an identifier is
>> >   that it provides a reliable way of uniquely naming the thing to be
>> >   identified.
>>
>> In this section, to be precise, one would need to use "visual matches".
>> There are so, so many other ways strings can "match", like "have the sam=
e
>> code points".
>>
>> However, the second sentence is still problematic. The characters in two
>> different strings that have similar appearances *are* different
>> characters,
>> so the identifiers are "unique" in that sense. I guess what you meant to
>> say is something like:
>>
>> =3D> it provides a reliable way of naming the thing to be identified, so=
 as
>> to have a unique visual appearance.
>>
>> Now, I think adding "visual" makes it clear that this paragraph needs so=
me
>> work. As it stands, it would be too strong: it would call for eliminatin=
g
>> all homographs from all identifiers (eg disallowing "top" written in
>> Cyrillic characters.)
>>
>> Later, there is a shift to confusability, but the text never relates tha=
t
>> directly to "confusability", which is what is elaborated upon.
>>
>> (In general, many different phrases are (apparently) used to mean the sa=
me
>> thing: matching, indistinguishable, etc. While use of different terms
>> makes
>> the text flow better, it has the big disadvantage that the reader never
>> knows whether phrase1 is meant to have a broader or narrower scope than
>> phrase2, or is meant to be identical. This would be a more extensive
>> change, however, to use more consistent defined language. Alternatively,
>> at
>> the top you could say that when you use the terms "matches",
>> "indistinguishable", "ambiguous", etc. (you'll have to go through and fi=
nd
>> them all) that what is meant is in terms of visual appearance.)
>>
>> > (We use the term "homoglyph" strictly: code points that normally use t=
he
>> same glyph when rendered.)
>>
>> This needs a bit of work. First step would be:
>>
>> Strings S1 and S2 are strict homoglyphs when they are different, yet
>> normally use the same glyph sequence when rendered.
>>
>> Second would be to clarify "normally use". Does that mean "in the fonts
>> that most people use on most platforms"? There are often more significan=
t
>> differences in serif fonts than non-serif, for example. Does that requir=
e
>> that the same font is used? There is huge variation among glyphs in
>> fonts: =C5=A3
>>  and =C8=9B may look the identical in font 1, and may be discernibly dif=
ferent
>> when both are in font2, but =C5=A3 in font1 may also look identical to =
=C8=9B in
>> font2. This also gets tricky because in many systems there is font
>> fallback. If a character is not in font1, then it might be displayed in =
a
>> fallback font 2.
>>
>> Third would be to clarify "same glyph sequence". Does this mean pixel by
>> pixel? At all resolutions, or just some? Pixel by pixel is extremely
>> strict.
>>
>> One could try to bring in "intent", but that is very dicy. The intent is
>> from the Unicode encoding side may not be followed precisely by all or
>> even
>> most font vendors. So it is of only theoretical value to point to intent=
.
>>
>> The exact degree of strictness matters a great deal, because under a
>> sufficiently strict interpretation <ARABIC LETTER BEH (U+0628) + ARABIC
>> HAMZA ABOVE (U+0654)> is *not* a strict homograph for U+08A1, ARABIC
>> LETTER
>> BEH WITH HAMZA ABOVE. That is, most current fonts do not display them as
>> pixel-for-pixel identical.
>>
>> I know well that this is a continuum, but since you are focusing on stri=
ct
>> homoglyphs, you have to be clearer what you mean by that term; where you
>> draw the line. That also carries over into related terms elsewhere in th=
e
>> document like "the same glyph"; does that mean in all fonts (or
>> some?/most?//common?), pixel for pixel or not, at all sizes or just
>> body-text sizes, etc.?
>>
>> You might think about providing a definition for "the same glyph
>> sequence",
>> then using that in the definition for homograph, and elsewhere in the
>> text.
>>
>> > Mitigation may be as simple as using a font
>>    designed to distinguish among different characters.
>>
>> Should mention that in practice this is extremely difficult to enforce; =
it
>> only works in closed systems, those that have complete control over the
>> fonts used for display of the kinds of identifiers in question.
>>
>> ----- End forwarded message -----
>>
>> --
>> Andrew Sullivan
>> ajs@anvilwalrusden.com
>>
>> _______________________________________________
>> Lucid mailing list
>> Lucid@ietf.org
>> https://www.ietf.org/mailman/listinfo/lucid
>>
>
>
>
> _______________________________________________
> Lucid mailing listLucid@ietf.orghttps://www.ietf.org/mailman/listinfo/luc=
id
>
>
>

--20cf301d3a28c12e43051108179a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">On Wed, Mar 11, 2015 at 11:55 A=
M, Asmus Freytag (t) <span dir=3D"ltr">&lt;<a href=3D"mailto:asmus-inc@ix.n=
etcom.com" target=3D"_blank">asmus-inc@ix.netcom.com</a>&gt;</span> wrote:<=
br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000"><span class=3D"">
    <div>On 3/11/2015 10:58 AM, Ted Hardie
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div style=3D"font-family:tahoma,sans-serif;font-size:small">Hi
          Andrew,<br>
          <br>
        </div>
        <div style=3D"font-family:tahoma,sans-serif"><font>So,
            I&#39;m far from an expert on this, but I have some concerns
            about the proposal to use &quot;visually&quot; here in the way =
Mark
            proposes.=C2=A0 If I understand things correctly, this problem
            will also occur in any system that reads a sequence of
            characters aloud.=C2=A0 That is, there is no way to distinguish
            in an audio system between<span style=3D"font-family:arial,helv=
etica,sans-serif"> U+08A1 and
              the combination of U+0628 and U+0654. <br>
            </span></font></div>
      </div>
    </blockquote>
    <br></span>
    Where do get that?<br>
    <br>
    U+0654 is used to represent a glottal stop, but my understanding is
    that U+08A1 was encoded partially because it represents a sound that
    does not have a glottal stop. If my understanding is correct, the
    distinction should be quite audible.<span class=3D""><br></span></div><=
/blockquote><div><br><div class=3D"gmail_default" style=3D"font-family:taho=
ma,sans-serif;font-size:small">I asked a native Arabic speaker about the sy=
stems she used and she played them to check.=C2=A0 Those systems may be non=
-representative, though, or simply wrong.=C2=A0 Or, rather than wrong, they=
 may be tuned to a case in which the result isn&#39;t audible.=C2=A0 <br><b=
r></div><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif=
;font-size:small">Are we confident that this difference is general for the =
other cases?=C2=A0 If so, that would be a very powerful way to explain the =
problem--code points which are visually indistinguishable but would render =
differently in audio.=C2=A0 (If it is not general, we still may want be cau=
tious about focusing solely on visual renderings).<br><br></div><div class=
=3D"gmail_default" style=3D"font-family:tahoma,sans-serif;font-size:small">=
regards,<br><br></div><div class=3D"gmail_default" style=3D"font-family:tah=
oma,sans-serif;font-size:small">Ted<br></div><br>=C2=A0</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex"><div bgcolor=3D"#FFFFFF" text=3D"#000000"><span class=3D""=
>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div style=3D"font-family:tahoma,sans-serif"><font><span style=3D"f=
ont-family:arial,helvetica,sans-serif"> </span>The
            current draft talks about rendering the glyph, and I think
            that is closer to correct--it doesn&#39;t matter whether the
            rendering is audio or graphical for the problem to occur.=C2=A0
            In the audio forms, the=C2=A0 quality of=C2=A0 running text pro=
viding
            context vs. independent identifiers without it also seems
            similar, at least to me.<br>
          </font></div>
      </div>
    </blockquote>
    <br></span>
    I think that the focus on visual as suggested by Mark ignores that
    there are identifiers for which the user community claims that
    certain visually distinct representations are considered &quot;the same=
&quot;
    by users, to the point that one cannot rely on users to faithfully
    retain which version of the identifier is the desired one. <br>
    <br>
    As the problem statement is concerned with general background, it is
    important to recognize such other levels of ambiguity exist.<span class=
=3D"HOEnZb"><font color=3D"#888888"><br>
    <br>
    A./</font></span><div><div class=3D"h5"><br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div style=3D"font-family:tahoma,sans-serif"><font><br>
          </font></div>
        <div style=3D"font-family:tahoma,sans-serif"><font>I
            also don&#39;t believe that Mark&#39;s point about=C2=A0 parsin=
g of byte
            sequences as XY when X and Y or meant is quite correct; in
            string contexts that would be a parsing error.=C2=A0 It might n=
ot
            be easily distinguished on the wire, but in protocol slots,
            this seems to be an at best unrelated issue.=C2=A0 I may not be
            familiar, though, with contexts in which this may occur.<br>
            <br>
          </font></div>
        <div style=3D"font-family:tahoma,sans-serif"><font>regards,<br>
            <br>
          </font></div>
        <div style=3D"font-family:tahoma,sans-serif;font-size:small"><font>=
Ted</font><br>
        </div>
      </div>
      <div class=3D"gmail_extra"><br>
        <div class=3D"gmail_quote">On Tue, Mar 10, 2015 at 6:33 PM, Andrew
          Sullivan <span dir=3D"ltr">&lt;<a href=3D"mailto:ajs@anvilwalrusd=
en.com" target=3D"_blank">ajs@anvilwalrusden.com</a>&gt;</span>
          wrote:<br>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">Dear
            colleagues,<br>
            <br>
            I hereby forward a message sent to a few people (including
            Asmus and<br>
            me) responding to the draft Asmus and I submitted yesterday.<br=
>
            <br>
            I think this is a valuable response, though I am not sure I
            agree with<br>
            the approach it&#39;s taking.=C2=A0 Nevertheless, if we are to =
have
            any hope of<br>
            useful discussion in Dallas, it&#39;d be good to have a look at
            the issues<br>
            in advance.<br>
            <br>
            Best regards,<br>
            <br>
            A<br>
            <br>
            ----- Forwarded message from Mark Davis ?=EF=B8=8F &lt;<a href=
=3D"mailto:mark@macchiato.com" target=3D"_blank">mark@macchiato.com</a>&gt;
            -----<br>
            <br>
            Date: Tue, 10 Mar 2015 16:53:33 +0100<br>
            From: Mark Davis ?=EF=B8=8F &lt;<a href=3D"mailto:mark@macchiat=
o.com" target=3D"_blank">mark@macchiato.com</a>&gt;<br>
            To: &quot;Asmus Freytag (t)&quot; &lt;<a href=3D"mailto:asmus-i=
nc@ix.netcom.com" target=3D"_blank">asmus-inc@ix.netcom.com</a>&gt;<br>
            Cc: Roozbeh Pournader &lt;<a href=3D"mailto:roozbeh@unicode.org=
" target=3D"_blank">roozbeh@unicode.org</a>&gt;,
            Ken Whistler &lt;<a href=3D"mailto:kenwhistler@att.net" target=
=3D"_blank">kenwhistler@att.net</a>&gt;,
            Lisa<br>
            =C2=A0 =C2=A0 =C2=A0 =C2=A0 Moore &lt;<a href=3D"mailto:lisam@u=
s.ibm.com" target=3D"_blank">lisam@us.ibm.com</a>&gt;,
            Michel Suignard &lt;<a href=3D"mailto:michel@suignard.com" targ=
et=3D"_blank">michel@suignard.com</a>&gt;,
            Markus<br>
            =C2=A0 =C2=A0 =C2=A0 =C2=A0 Scherer &lt;<a href=3D"mailto:marku=
s.icu@gmail.com" target=3D"_blank">markus.icu@gmail.com</a>&gt;,
            Peter Constable &lt;<a href=3D"mailto:petercon@microsoft.com" t=
arget=3D"_blank">petercon@microsoft.com</a>&gt;,<br>
            =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:asullivan@dyn.com=
" target=3D"_blank">asullivan@dyn.com</a><br>
            Subject: Re: Non-normalizable diacritics - new property<br>
            <br>
            + Andrew<br>
            <br>
            =E2=80=8B&gt; =E2=80=8B<br>
            In the meantime, the following has been released in
            preparation to the BOF<br>
            at the IETF meeting in Dallas.<br>
            <br>
            =E2=80=8B&gt; =E2=80=8B<br>
            <a href=3D"https://datatracker.ietf.org/doc/draft-sullivan-luci=
d-prob-stmt/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-sull=
ivan-lucid-prob-stmt/</a><br>
            &lt;<a href=3D"https://datatracker.ietf.org/doc/draft-sullivan-=
lucid-prob-stmt/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-=
sullivan-lucid-prob-stmt/</a>&gt;<br>
            <br>
            <br>
            A well written report, and I think will help a great deal in
            resolving the<br>
            issues.<br>
            <br>
            However, I&#39;d strongly suggest a couple of changes to be mor=
e
            precise, and<br>
            thus avoid confusion (no pun intended). Although these may
            seem overly<br>
            formal, it is vital that the text be unambiguous, because
            the subject is so<br>
            very tricky, and it is thus so easy for people to be arguing
            based on<br>
            different interpretations of terms.<br>
            <br>
            I will try to suggest some minimal changes, although it
            might be even<br>
            better with some more extensive rewording.<br>
            <br>
            &gt; I3 depends on the assumption that strings that will be
            used in<br>
            &gt;=C2=A0 =C2=A0identifiers will not have any ambiguous matchi=
ng to
            other strings.<br>
            <br>
            When discussing strings, the term &quot;ambiguous matching&quot=
; is
            itself quite<br>
            ambiguous. I can have ambiguous matching with SJIS, for
            example, because<br>
            0x61 can be an &#39;a&#39; or be part of another character;
            similarly there are<br>
            sequences of bytes ..XY.. where XY is a character or X is
            the end of one<br>
            character, and Y is the start of another. There are other
            forms of<br>
            ambiguity as well.<br>
            <br>
            To eliminate this ambiguity, change every 8 other cases of
            &quot;ambiguous/ity&quot;<br>
            to prefix by &quot;visually&quot;.<br>
            <br>
            =3D&gt;=C2=A0 =C2=A0identifiers will not be visually ambiguous =
with
            other strings used as<br>
            identifiers.<br>
            ...<br>
            <br>
            Look for other cases that could profit by that, such as like<br=
>
            &quot;indistinguishable&quot;, and &quot;matches&quot;.<br>
            <br>
            See the later:<br>
            <br>
            &gt; Worse, identifiers, by their very nature, are things
            that must<br>
            &gt;=C2=A0 =C2=A0provide reliable exact matches.=C2=A0 The whol=
e point of
            an identifier is<br>
            &gt;=C2=A0 =C2=A0that it provides a reliable way of uniquely na=
ming
            the thing to be<br>
            &gt;=C2=A0 =C2=A0identified.<br>
            <br>
            In this section, to be precise, one would need to use
            &quot;visual matches&quot;.<br>
            There are so, so many other ways strings can &quot;match&quot;,=
 like
            &quot;have the same<br>
            code points&quot;.<br>
            <br>
            However, the second sentence is still problematic. The
            characters in two<br>
            different strings that have similar appearances *are*
            different characters,<br>
            so the identifiers are &quot;unique&quot; in that sense. I gues=
s what
            you meant to<br>
            say is something like:<br>
            <br>
            =3D&gt; it provides a reliable way of naming the thing to be
            identified, so as<br>
            to have a unique visual appearance.<br>
            <br>
            Now, I think adding &quot;visual&quot; makes it clear that this
            paragraph needs some<br>
            work. As it stands, it would be too strong: it would call
            for eliminating<br>
            all homographs from all identifiers (eg disallowing &quot;top&q=
uot;
            written in<br>
            Cyrillic characters.)<br>
            <br>
            Later, there is a shift to confusability, but the text never
            relates that<br>
            directly to &quot;confusability&quot;, which is what is elabora=
ted
            upon.<br>
            <br>
            (In general, many different phrases are (apparently) used to
            mean the same<br>
            thing: matching, indistinguishable, etc. While use of
            different terms makes<br>
            the text flow better, it has the big disadvantage that the
            reader never<br>
            knows whether phrase1 is meant to have a broader or narrower
            scope than<br>
            phrase2, or is meant to be identical. This would be a more
            extensive<br>
            change, however, to use more consistent defined language.
            Alternatively, at<br>
            the top you could say that when you use the terms &quot;matches=
&quot;,<br>
            &quot;indistinguishable&quot;, &quot;ambiguous&quot;, etc. (you=
&#39;ll have to go
            through and find<br>
            them all) that what is meant is in terms of visual
            appearance.)<br>
            <br>
            &gt; (We use the term &quot;homoglyph&quot; strictly: code poin=
ts that
            normally use the<br>
            same glyph when rendered.)<br>
            <br>
            This needs a bit of work. First step would be:<br>
            <br>
            Strings S1 and S2 are strict homoglyphs when they are
            different, yet<br>
            normally use the same glyph sequence when rendered.<br>
            <br>
            Second would be to clarify &quot;normally use&quot;. Does that =
mean
            &quot;in the fonts<br>
            that most people use on most platforms&quot;? There are often
            more significant<br>
            differences in serif fonts than non-serif, for example. Does
            that require<br>
            that the same font is used? There is huge variation among
            glyphs in fonts: =C5=A3<br>
            =C2=A0and =C8=9B may look the identical in font 1, and may be
            discernibly different<br>
            when both are in font2, but =C5=A3 in font1 may also look
            identical to =C8=9B in<br>
            font2. This also gets tricky because in many systems there
            is font<br>
            fallback. If a character is not in font1, then it might be
            displayed in a<br>
            fallback font 2.<br>
            <br>
            Third would be to clarify &quot;same glyph sequence&quot;. Does=
 this
            mean pixel by<br>
            pixel? At all resolutions, or just some? Pixel by pixel is
            extremely strict.<br>
            <br>
            One could try to bring in &quot;intent&quot;, but that is very =
dicy.
            The intent is<br>
            from the Unicode encoding side may not be followed precisely
            by all or even<br>
            most font vendors. So it is of only theoretical value to
            point to intent.<br>
            <br>
            The exact degree of strictness matters a great deal, because
            under a<br>
            sufficiently strict interpretation &lt;ARABIC LETTER BEH
            (U+0628) + ARABIC<br>
            HAMZA ABOVE (U+0654)&gt; is *not* a strict homograph for
            U+08A1, ARABIC LETTER<br>
            BEH WITH HAMZA ABOVE. That is, most current fonts do not
            display them as<br>
            pixel-for-pixel identical.<br>
            <br>
            I know well that this is a continuum, but since you are
            focusing on strict<br>
            homoglyphs, you have to be clearer what you mean by that
            term; where you<br>
            draw the line. That also carries over into related terms
            elsewhere in the<br>
            document like &quot;the same glyph&quot;; does that mean in all=
 fonts
            (or<br>
            some?/most?//common?), pixel for pixel or not, at all sizes
            or just<br>
            body-text sizes, etc.?<br>
            <br>
            You might think about providing a definition for &quot;the same
            glyph sequence&quot;,<br>
            then using that in the definition for homograph, and
            elsewhere in the text.<br>
            <br>
            &gt; Mitigation may be as simple as using a font<br>
            =C2=A0 =C2=A0designed to distinguish among different characters=
.<br>
            <br>
            Should mention that in practice this is extremely difficult
            to enforce; it<br>
            only works in closed systems, those that have complete
            control over the<br>
            fonts used for display of the kinds of identifiers in
            question.<br>
            <br>
            ----- End forwarded message -----<br>
            <span><font color=3D"#888888"><br>
                --<br>
                Andrew Sullivan<br>
                <a href=3D"mailto:ajs@anvilwalrusden.com" target=3D"_blank"=
>ajs@anvilwalrusden.com</a><br>
                <br>
                _______________________________________________<br>
                Lucid mailing list<br>
                <a href=3D"mailto:Lucid@ietf.org" target=3D"_blank">Lucid@i=
etf.org</a><br>
                <a href=3D"https://www.ietf.org/mailman/listinfo/lucid" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/lucid</a><br>
              </font></span></blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
Lucid mailing list
<a href=3D"mailto:Lucid@ietf.org" target=3D"_blank">Lucid@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/lucid" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/lucid</a>
</pre>
    </blockquote>
    <br>
  </div></div></div>

</blockquote></div><br></div></div>

--20cf301d3a28c12e43051108179a--


From nobody Wed Mar 11 12:43:39 2015
Return-Path: <Shawn.Steele@microsoft.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 E288E1A1B8B for <lucid@ietfa.amsl.com>; Wed, 11 Mar 2015 12:43:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 EWr80V1JZ_P3 for <lucid@ietfa.amsl.com>; Wed, 11 Mar 2015 12:43:34 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0705.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::705]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 420071A1B8A for <lucid@ietf.org>; Wed, 11 Mar 2015 12:43:34 -0700 (PDT)
Received: from CY1PR0301MB0731.namprd03.prod.outlook.com (25.160.159.149) by BL2PR03MB402.namprd03.prod.outlook.com (10.141.91.146) with Microsoft SMTP Server (TLS) id 15.1.112.13; Wed, 11 Mar 2015 19:43:13 +0000
Received: from CY1PR0301MB0731.namprd03.prod.outlook.com ([25.160.159.149]) by CY1PR0301MB0731.namprd03.prod.outlook.com ([25.160.159.149]) with mapi id 15.01.0106.007; Wed, 11 Mar 2015 19:43:12 +0000
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: Ted Hardie <ted.ietf@gmail.com>, "Asmus Freytag (t)" <asmus-inc@ix.netcom.com>
Thread-Topic: [Lucid] [mark@macchiato.com: Re: Non-normalizable diacritics - new property]
Thread-Index: AQHQXCT6v+fcyt1y/kWOJMb4v31hfZ0Xp0gsgAACDiA=
Date: Wed, 11 Mar 2015 19:43:12 +0000
Message-ID: <CY1PR0301MB07310C68F6CFDD46AE22086F82190@CY1PR0301MB0731.namprd03.prod.outlook.com>
References: <20150311013300.GC12479@dyn.com> <CA+9kkMDZW9yPtDxtLTfY1=VS6itvHtXHF1qdZKtXdwwORwqnew@mail.gmail.com> <55008F97.8040701@ix.netcom.com> <CA+9kkMAcgSA1Ch0B9W1Np0LMn2udegZ=AzU1b26dAi+SDcbGgg@mail.gmail.com>
In-Reply-To: <CA+9kkMAcgSA1Ch0B9W1Np0LMn2udegZ=AzU1b26dAi+SDcbGgg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e0:ee43::3]
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BL2PR03MB402;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(106116001)(50986999)(16601075003)(54356999)(76576001)(76176999)(19609705001)(99286002)(122556002)(19300405004)(2656002)(87936001)(33656002)(19625215002)(2950100001)(62966003)(77156002)(92566002)(19580395003)(40100003)(74316001)(46102003)(86362001)(86612001)(102836002)(15975445007)(93886004)(2900100001)(19617315012)(16236675004)(7059030)(3826002)(222073002); DIR:OUT; SFP:1102; SCL:1; SRVR:BL2PR03MB402; H:CY1PR0301MB0731.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-microsoft-antispam-prvs: <BL2PR03MB4026629F79534E957DAA18E82190@BL2PR03MB402.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002009)(5005006); SRVR:BL2PR03MB402; BCL:0; PCL:0; RULEID:; SRVR:BL2PR03MB402; 
x-forefront-prvs: 0512CC5201
Content-Type: multipart/alternative; boundary="_000_CY1PR0301MB07310C68F6CFDD46AE22086F82190CY1PR0301MB0731_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Mar 2015 19:43:12.6334 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL2PR03MB402
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/6U-lTwuLOg-WaWCmu0x4i1Np0PA>
Cc: "lucid@ietf.org" <lucid@ietf.org>, Dave Thaler <dthaler@microsoft.com>, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [Lucid] [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: Wed, 11 Mar 2015 19:43:37 -0000

--_000_CY1PR0301MB07310C68F6CFDD46AE22086F82190CY1PR0301MB0731_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

UmU6IGF1ZGlvIHZzIHZpc3VhbCByZW5kZXJpbmfigKYgIEkgcHJvbm91bmNlIG15IGRyb2lkIOKA
nEwzLUcw4oCdIGFzIOKAnEVsIFRocmVlIEdlZSBPaOKAnS4gIFdoaWNoIGxlYWRzIHRvIHByb2Js
ZW1zIGFzIHRoZSBsYXN0IGNoYXJhY3RlciBpcyBhIHplcm8uDQoNClRoaXMgZG9jdW1lbnQgbWFr
ZXMgYSBoYXJkIGxpbmUgYmV0d2VlbiDigJxob21vZ2x5cGhz4oCdIGFuZCDigJx2aXN1YWxseSBz
aW1pbGFy4oCdLiAgU3BlY2lmaWNhbGx5IGNhbGxpbmcgb3V0IHRvIChwYXJhcGhyYXNpbmcpIGp1
c3QgdXNlIGEgZm9udCB0aGF0IG1ha2VzIGNoYXJhY3RlcnMgbG9vayBkaWZmZXJlbnQuICBJ4oCZ
ZCBhc3NlcnQgdGhhdCB0aGVyZSBpc27igJl0IGEgaGFyZCBsaW5lIGJldHdlZW4gdGhlc2UgY29u
Y2VwdHMgYW5kIHRoYXQganVzdCBwaWNraW5nIHRoZSByaWdodCBmb250IGdsb3NzZXMgb3ZlciB0
aGUgZGlmZmljdWx0aWVzIGluIHRoZSBwcm9ibGVtLg0KDQpUaGUgyrtva2luYSBpcyBhIGRlY2Vu
dCBjYXNlIHdoZXJlIGl0IGxvb2tzIGEgbG90IGxpa2UgYW5vdGhlciBjaGFyYWN0ZXIsIGFuZCBv
ZnRlbiBmb250cyBtYXkgZXZlbiB1c2UgdGhlIHNhbWUgZ2x5cGgsIGhvd2V2ZXIgc29tZXRpbWVz
IGZvbnQgZGVzaWduZXJzIGNob29zZSB0byBtYWtlIGEgZGlzdGluY3Rpb24uICBJdOKAmXMgbmVh
cmx5IGltcG9zc2libGUgdG8gdGVsbCBhIGRldmVsb3BlciB0byDigJx1c2UgdGhlIHJpZ2h0IGZv
bnTigJ0uDQoNCkFkZGl0aW9uYWxseSBpdCBjb250aW51ZXMgdG8gdHJlYXQgdGhlc2UgbmV3bHkg
bm90aWNlZCBjaGFyYWN0ZXJzIGFzIGEgc3BlY2lhbCBjYXNlIHdpdGhvdXQgY29uc2lkZXJpbmcg
dGhlIG1hbnkgZXhpc3RpbmcgcHJvYmxlbXMuDQoNCknigJltIGFsc28gY29uZnVzZWQgYnkgdGhl
IGRvY3VtZW504oCZcyBhdHRlbnRpb24gdG8gdGhlIG5lZWQgZm9yIHVuaXF1ZSBpZGVudGlmaWVy
cyBhdCB0aGUgYmVnaW5uaW5nLCBidXQgdGhlbiBsb29rcyBhdCB0aGUgZXhpc3RpbmcgSUROQSBw
cm9ibGVtLiAgSSBkb27igJl0IGNvbnNpZGVyIElETkEgYWJsZSB0byBwcm92aWRlIOKAnHNlY3Vy
ZeKAnSAobWVhbmluZyB1bmNvbmZ1c2FibGUpIGlkZW50aWZpZXJzLg0KDQpJ4oCZbSBkZWZpbml0
ZWx5IGluIHRoZSA0LjEgY2FtcCDigJxKdXN0IGFub3RoZXIgc3BlY2llcyBvZiBDb25mdXNhYmxl
c+KAnS4gIEhvd2V2ZXIgSSBkaXNhZ3JlZSB3aXRoIHRoZSBmaW5hbCBwYXJhZ3JhcGguDQoNCklN
TyB0aGUgY29zdCBvZiBhbnkgbWl0aWdhdGlvbiAoYW5kIGltcGxpZWQgY29zdCBvZiBoYXZpbmcg
YSBmaXJlZHJpbGwgdGhlIG5leHQgdGltZSBvbmUgb2YgdGhlc2UgaGFwcGVucykgb3V0d2VpZ2hz
IGFueSBwb3NzaWJpbGl0eSBvZiByZWR1Y2luZyB0aGUgY29uZnVzYWJsZSBzcGFjZS4gIFdl4oCZ
cmUgc3BlbmRpbmcgaHVuZHJlZHMgb2YgaG91cnMgYW5kIHRob3VzYW5kcyBvZiBkb2xsYXJzIG9u
IHRoaXMgdG9waWMsIGJ1dCBJ4oCZZCBiZSByZWFsbHkgc3VycHJpc2VkIGlmIGFuIGF0dGFja2Vy
IGV2ZW4gYm90aGVyZWQgd2l0aCB0aGlzIGNvZGUgcG9pbnQuICBJZiB0aGV5IGRpZCwgaXTigJlk
IGJlIDAuMSUgb2YgdGhlIGF0dGFja3MsIHdpdGggOTAlIG9mIHRoZSBhdHRhY2tzIHVzaW5nIGZh
ciBsZXNzIGVzb3RlcmljIG1ldGhvZHMuDQoNCklNTyB0aGUgcmVhc29uIHRvIHNvbHZlIHRoZSBw
cm9ibGVtIHdpdGggdGhpcyBjaGFyYWN0ZXIgd291bGQgYmUgYXMgcGFydCBvZiBhIHNvbHV0aW9u
IHRvIHNvbHZlIGNvbmZ1c2FiaWxpdHkgYXR0YWNrcyBpbiBJRE5BIGluIGdlbmVyYWwuICBZZXQg
dGhpcyBzb2x1dGlvbiBhZGRyZXNzZXMgb25seSBhIGZldyBjaGFyYWN0ZXJzIG9mIHdoYXQgYXJl
IHByb2JhYmx5IGJpbGxpb25zIG9mIHdheXMgdG8gbWFrZSBjb25mdXNhYmxlIGF0dGFja3MuDQoN
Ci1TaGF3bg0KDQpodHRwOi8vTDMtRzAuY29tDQo=

--_000_CY1PR0301MB07310C68F6CFDD46AE22086F82190CY1PR0301MB0731_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDEx
IDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg
Um9tYW4iLHNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnByZQ0K
CXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0
dGVkIENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQt
c2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpzcGFuLmhvZW56Yg0K
CXttc28tc3R5bGUtbmFtZTpob2VuemI7fQ0Kc3Bhbi5IVE1MUHJlZm9ybWF0dGVkQ2hhcg0KCXtt
c28tc3R5bGUtbmFtZToiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCI7DQoJZm9udC1mYW1p
bHk6Q29uc29sYXM7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjANCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29u
YWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzFGNDk3RDt9
DQpzcGFuLkVtYWlsU3R5bGUyMQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1jb21wb3NlOw0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0K
Lk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7fQ0KQHBhZ2UgV29y
ZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBp
biAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwv
c3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJl
ZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNv
IDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0i
ZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwv
aGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxk
aXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMt
c2VyaWY7Y29sb3I6IzFGNDk3RCI+UmU6IGF1ZGlvIHZzIHZpc3VhbCByZW5kZXJpbmfigKYmbmJz
cDsgSSBwcm9ub3VuY2UgbXkgZHJvaWQg4oCcTDMtRzDigJ0gYXMg4oCcRWwgVGhyZWUgR2VlIE9o
4oCdLiZuYnNwOyBXaGljaCBsZWFkcyB0byBwcm9ibGVtcyBhcyB0aGUgbGFzdCBjaGFyYWN0ZXIg
aXMgYSB6ZXJvLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+VGhp
cyBkb2N1bWVudCBtYWtlcyBhIGhhcmQgbGluZSBiZXR3ZWVuIOKAnGhvbW9nbHlwaHPigJ0gYW5k
IOKAnHZpc3VhbGx5IHNpbWlsYXLigJ0uJm5ic3A7IFNwZWNpZmljYWxseSBjYWxsaW5nIG91dCB0
byAocGFyYXBocmFzaW5nKSBqdXN0IHVzZSBhIGZvbnQgdGhhdCBtYWtlcyBjaGFyYWN0ZXJzDQog
bG9vayBkaWZmZXJlbnQuJm5ic3A7IEnigJlkIGFzc2VydCB0aGF0IHRoZXJlIGlzbuKAmXQgYSBo
YXJkIGxpbmUgYmV0d2VlbiB0aGVzZSBjb25jZXB0cyBhbmQgdGhhdCBqdXN0IHBpY2tpbmcgdGhl
IHJpZ2h0IGZvbnQgZ2xvc3NlcyBvdmVyIHRoZSBkaWZmaWN1bHRpZXMgaW4gdGhlIHByb2JsZW0u
Jm5ic3A7DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPlRoZSDK
u29raW5hIGlzIGEgZGVjZW50IGNhc2Ugd2hlcmUgaXQgbG9va3MgYSBsb3QgbGlrZSBhbm90aGVy
IGNoYXJhY3RlciwgYW5kIG9mdGVuIGZvbnRzIG1heSBldmVuIHVzZSB0aGUgc2FtZSBnbHlwaCwg
aG93ZXZlciBzb21ldGltZXMgZm9udCBkZXNpZ25lcnMgY2hvb3NlDQogdG8gbWFrZSBhIGRpc3Rp
bmN0aW9uLiZuYnNwOyBJdOKAmXMgbmVhcmx5IGltcG9zc2libGUgdG8gdGVsbCBhIGRldmVsb3Bl
ciB0byDigJx1c2UgdGhlIHJpZ2h0IGZvbnTigJ0uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjojMUY0OTdEIj5BZGRpdGlvbmFsbHkgaXQgY29udGludWVzIHRvIHRyZWF0IHRoZXNl
IG5ld2x5IG5vdGljZWQgY2hhcmFjdGVycyBhcyBhIHNwZWNpYWwgY2FzZSB3aXRob3V0IGNvbnNp
ZGVyaW5nIHRoZSBtYW55IGV4aXN0aW5nIHByb2JsZW1zLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMt
c2VyaWY7Y29sb3I6IzFGNDk3RCI+SeKAmW0gYWxzbyBjb25mdXNlZCBieSB0aGUgZG9jdW1lbnTi
gJlzIGF0dGVudGlvbiB0byB0aGUgbmVlZCBmb3IgdW5pcXVlIGlkZW50aWZpZXJzIGF0IHRoZSBi
ZWdpbm5pbmcsIGJ1dCB0aGVuIGxvb2tzIGF0IHRoZSBleGlzdGluZyBJRE5BIHByb2JsZW0uJm5i
c3A7IEkgZG9u4oCZdCBjb25zaWRlcg0KIElETkEgYWJsZSB0byBwcm92aWRlIOKAnHNlY3VyZeKA
nSAobWVhbmluZyB1bmNvbmZ1c2FibGUpIGlkZW50aWZpZXJzLiAmbmJzcDs8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFG
NDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPknigJltIGRlZmluaXRlbHkgaW4gdGhlIDQu
MSBjYW1wIOKAnEp1c3QgYW5vdGhlciBzcGVjaWVzIG9mIENvbmZ1c2FibGVz4oCdLiZuYnNwOyBI
b3dldmVyIEkgZGlzYWdyZWUgd2l0aCB0aGUgZmluYWwgcGFyYWdyYXBoLiZuYnNwOw0KPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5JTU8gdGhlIGNvc3Qgb2YgYW55
IG1pdGlnYXRpb24gKGFuZCBpbXBsaWVkIGNvc3Qgb2YgaGF2aW5nIGEgZmlyZWRyaWxsIHRoZSBu
ZXh0IHRpbWUgb25lIG9mIHRoZXNlIGhhcHBlbnMpIG91dHdlaWdocyBhbnkgcG9zc2liaWxpdHkg
b2YgcmVkdWNpbmcgdGhlIGNvbmZ1c2FibGUNCiBzcGFjZS4mbmJzcDsgV2XigJlyZSBzcGVuZGlu
ZyBodW5kcmVkcyBvZiBob3VycyBhbmQgdGhvdXNhbmRzIG9mIGRvbGxhcnMgb24gdGhpcyB0b3Bp
YywgYnV0IEnigJlkIGJlIHJlYWxseSBzdXJwcmlzZWQgaWYgYW4gYXR0YWNrZXIgZXZlbiBib3Ro
ZXJlZCB3aXRoIHRoaXMgY29kZSBwb2ludC4gJm5ic3A7SWYgdGhleSBkaWQsIGl04oCZZCBiZSAw
LjElIG9mIHRoZSBhdHRhY2tzLCB3aXRoIDkwJSBvZiB0aGUgYXR0YWNrcyB1c2luZyBmYXIgbGVz
cyBlc290ZXJpYyBtZXRob2RzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFG
NDk3RCI+SU1PIHRoZSByZWFzb24gdG8gc29sdmUgdGhlIHByb2JsZW0gd2l0aCB0aGlzIGNoYXJh
Y3RlciB3b3VsZCBiZSBhcyBwYXJ0IG9mIGEgc29sdXRpb24gdG8gc29sdmUgY29uZnVzYWJpbGl0
eSBhdHRhY2tzIGluIElETkEgaW4gZ2VuZXJhbC4mbmJzcDsgWWV0IHRoaXMgc29sdXRpb24gYWRk
cmVzc2VzDQogb25seSBhIGZldyBjaGFyYWN0ZXJzIG9mIHdoYXQgYXJlIHByb2JhYmx5IGJpbGxp
b25zIG9mIHdheXMgdG8gbWFrZSBjb25mdXNhYmxlIGF0dGFja3MuPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Qi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4tU2hhd248bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48YSBocmVmPSJodHRwOi8vTDMt
RzAuY29tIj5odHRwOi8vTDMtRzAuY29tPC9hPg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_CY1PR0301MB07310C68F6CFDD46AE22086F82190CY1PR0301MB0731_--


From nobody Wed Mar 11 13:09:50 2015
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 AE4B31A700F for <lucid@ietfa.amsl.com>; Wed, 11 Mar 2015 13:09:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.141
X-Spam-Level: 
X-Spam-Status: No, score=-2.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=ham
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 oQb9g38QEVs2 for <lucid@ietfa.amsl.com>; Wed, 11 Mar 2015 13:09:44 -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 67DB11A1AB9 for <lucid@ietf.org>; Wed, 11 Mar 2015 13:09:44 -0700 (PDT)
Received: from mx1.yitter.info (unknown [50.189.173.0]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 2CDF98A031 for <lucid@ietf.org>; Wed, 11 Mar 2015 20:09:43 +0000 (UTC)
Date: Wed, 11 Mar 2015 16:09:41 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: lucid@ietf.org
Message-ID: <20150311200941.GV15037@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CY1PR0301MB07310C68F6CFDD46AE22086F82190@CY1PR0301MB0731.namprd03.prod.outlook.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/mjRhjHuihrbp9lDynCYR5vafB4Y>
Subject: Re: [Lucid] [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: Wed, 11 Mar 2015 20:09:49 -0000

On Wed, Mar 11, 2015 at 07:43:12PM +0000, Shawn Steele wrote:
> This document makes a hard line between “homoglyphs” and “visually similar”.

No, it does not.  It says right there in section 2.2.1:

       Any character that can be confused for
   another one can be called confusable, and confusability can be
   thought of as a spectrum with "visually similar" at one end, and
   "homoglyphs" at the other.  (We use the term "homoglyph" strictly:
   code points that normally use the same glyph when rendered.)

> The ʻokina is a decent case where it looks a lot like another character, and often fonts may even use the same glyph, however sometimes font designers choose to make a distinction.  It’s nearly impossible to tell a developer to “use the right font”.
> 

It's funny that you should pick ʻokina, because you're sort of making
the point the draft is after.  In any properly-designed font, U+02BB
will be rendered as though it is a single opening curly-quote, in the
way English (not American) quotation marks were historically typeset.
But U+02BC (ʼ) is a letter, and it's actually called "APOSTROPHE", and
in any decent font will look like the single closing curly-quote,
which is what was historically used in English for the apostrophe as
well.  This is not U+0027 ('), of course.  So all three can be
distinguished in a proper font.  There's moreover an argument to be
made that U+0027 is close to U+02BC than it is to U+02BB, though of
course the context might make a difference.  (Also, of course, U+0027
has other different properties.)

None of this is like the case of, say, the precomposed e-with-acute
and the combining sequence, which should never even in principle show
a difference.  That particular case is solved by NFC, but it is
clearly different from the cases where a font should or could, in
principle, make them distinguishable.

I think we're all aware that you can't tell developers what font to
use, but there is clearly an in-principle difference between "could be
mitigated with font" and "cannot possibly be mitigated with font".
And as the draft notes, this is all a spectrum with many small
gradations.  The purpose of the discussion is to make distinctions
apparent where we can, so that we can talk sensibly about them.  So
trying to say they're all the same doesn't help make those
distinctions clear.

> Additionally it continues to treat these newly noticed characters as a special case without considering the many existing problems.
>

Where, please?

> I’m also confused by the document’s attention to the need for unique identifiers at the beginning, but then looks at the existing IDNA problem.  I don’t consider IDNA able to provide “secure” (meaning unconfusable) identifiers.
> 

IDNA is supposed to be providing unique identifiers.  It in fact does,
in the sense that when a series of U-labels or A-labels are put
together they (respectively) produce exactly one FQDN that can be
looked up.  That's why it's part of the problem.

> 
> IMO the reason to solve the problem with this character

Which character, exactly?

Best regards,

A
-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Wed Mar 11 14:15:50 2015
Return-Path: <john-ietf@jck.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 A2F3C1A8786 for <lucid@ietfa.amsl.com>; Wed, 11 Mar 2015 14:15:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 AZtghPQaDR1a for <lucid@ietfa.amsl.com>; Wed, 11 Mar 2015 14:15:46 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90CA61A878A for <lucid@ietf.org>; Wed, 11 Mar 2015 14:15:39 -0700 (PDT)
Received: from [198.252.137.35] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1YVnyW-0001O2-Ce; Wed, 11 Mar 2015 17:15:32 -0400
Date: Wed, 11 Mar 2015 17:15:27 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Hardie <ted.ietf@gmail.com>, Andrew Sullivan <ajs@anvilwalrusden.com>
Message-ID: <4A00B59133258EB59C38CD37@JcK-HP8200.jck.com>
In-Reply-To: <CA+9kkMDZW9yPtDxtLTfY1=VS6itvHtXHF1qdZKtXdwwORwqnew@mail.gmail.com>
References: <20150311013300.GC12479@dyn.com> <CA+9kkMDZW9yPtDxtLTfY1=VS6itvHtXHF1qdZKtXdwwORwqnew@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.35
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/oqUzKDYMCTP-pSjEGFV4Iis7eYk>
Cc: lucid@ietf.org
Subject: Re: [Lucid] [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: Wed, 11 Mar 2015 21:15:48 -0000

Ted,

I won't claim to more than about 10% more expertise, but maybe I
can clarify some of the issues you raise (and with which I
generally agree)...

--On Wednesday, March 11, 2015 10:58 -0700 Ted Hardie
<ted.ietf@gmail.com> wrote:

> Hi Andrew,
> 
> So, I'm far from an expert on this, but I have some concerns
> about the proposal to use "visually" here in the way Mark
> proposes.  If I understand things correctly, this problem will
> also occur in any system that reads a sequence of characters
> aloud.

Or not.  To give more familiar example than the one that started
this (I'm assuming there are no first-language speakers of Fula
on this list and, if there are, that they probably don't
primarily write it in Arabic characters), text to speech
programs generally need to know the language involved and often
have language-specific dictionaries.  Anyone who speaks
competent French knows that English vowel phonemes and French
ones are different.  When one set is used to render the other
language, what first-language speakers of the second language
hear is "weird accent" at best and speech that is
incomprehensible at worst.   English is particularly bad in this
regard because it has a lot fewer vowel (and consonant, but the
vowels are more obvious) symbols than it has phonemes, while
many languages that use Latin Script "decorate" their characters
in various ways that provide much more written distinction among
those phonemes.

In written form, type style and rendering distinctions, which
are very much tied up with "visual", involve many of the same
issues because accurate rendering is often tied up with
language, rather than being intrinsic properties of the script.

Interestingly, as soon as a suggestion is made that takes us to
the "language" distinctions that are often key to both "visual"
and "spoken", it also brings up back to where the original
discussion about U+08A1 --the discussion that led to our
understanding of the extent and complexity of these problems--
started: if one knows the language contexts, the distinctions
that Unicode makes by not having some characters decompose
become obvious.  Conversely, if one it talking about the DNS or
other identifiers in which language information is inherently
unavailable or non-applicable, then statements and ideas that
depend on language just don't help.

There are a second set of distinctions that get involved here
and that do not depend on language -- a collection of combining
characters that (using a summary with which Unicode experts
might not agree) are not defined precisely enough that one can
predict how they will overlay on or combine with the base
characters.  The resulting precomposed characters (almost)never
decomponse.  This issue is discussed briefly in the forth
paragraph of Section 3.3.1 of
draft-klensin-idna-5892upd-unicode70-04 and the piece of the
Unicode Standard referenced there as "Unicod70-Overlay" (sic - I
hate it when a typo is spotted immediately after a document is
posted) so this isn't _just_ a language-distinction (or
phoneme-distinction) problem, but that is part of it.

>  That is, there is no way to distinguish in an audio
> system between U+08A1 and the combination of U+0628 and
> U+0654.

Actually, if we are willing to drag the discussion back into
into Hamza issues (one of the reasons why
draft-klensin-idna-5892upd-unicode70-04 is twice the length of
draft-sullivan-lucid-prob-stmt), there is a significant phonetic
difference.  See section 2.2.2 of the latter and a different
(and more comprehensive) version in 3.2.3 of the former and, as
needed, the Unicode explanations it references.  I prefer to
think of these distinctions as language ones rather than
phonetic ones because if they were the latter, no normal human
being would be able to tell which code point to use even though
reading (i.e., text to speech) systems would be happier.  If
both the combining sequence and the precomposed character could
reasonably appear with the same language and be treated as
distinct, there would be a big problem but, if that problem
exists, I haven't seen an example yet.

The other problem with "visual" is that it pulls us back into
subjective confusability and that is both a nightmare we would
prefer to avoid if possible and something that has been the
source of earlier claims that there is no solvable problem in
this area.

>  The current draft talks about rendering the glyph,
> and I think that is closer to correct--it doesn't matter
> whether the rendering is audio or graphical for the problem to
> occur.  In the audio forms, the  quality of  running text
> providing context vs. independent identifiers without it also
> seems similar, at least to me.
>...

    john


From nobody Wed Mar 11 14:58:51 2015
Return-Path: <Shawn.Steele@microsoft.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 EBA8B1A87EF for <lucid@ietfa.amsl.com>; Wed, 11 Mar 2015 14:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 M4qEhOKE7lUE for <lucid@ietfa.amsl.com>; Wed, 11 Mar 2015 14:58:45 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0776.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::776]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA5481A87A5 for <lucid@ietf.org>; Wed, 11 Mar 2015 14:58:44 -0700 (PDT)
Received: from CY1PR0301MB0731.namprd03.prod.outlook.com (25.160.159.149) by CY1PR0301MB0732.namprd03.prod.outlook.com (25.160.159.150) with Microsoft SMTP Server (TLS) id 15.1.106.15; Wed, 11 Mar 2015 21:58:26 +0000
Received: from CY1PR0301MB0731.namprd03.prod.outlook.com ([25.160.159.149]) by CY1PR0301MB0731.namprd03.prod.outlook.com ([25.160.159.149]) with mapi id 15.01.0106.007; Wed, 11 Mar 2015 21:58:26 +0000
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "lucid@ietf.org" <lucid@ietf.org>
Thread-Topic: [Lucid] [mark@macchiato.com: Re: Non-normalizable diacritics - new property]
Thread-Index: AQHQXCT6v+fcyt1y/kWOJMb4v31hfZ0Xp0gsgAACDiCAAAz9gIAABLlwgAAZkeA=
Date: Wed, 11 Mar 2015 21:58:26 +0000
Message-ID: <CY1PR0301MB0731F4EBE5EB5C3340F7059282190@CY1PR0301MB0731.namprd03.prod.outlook.com>
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> 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e0:ee43::3]
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR0301MB0732;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(51704005)(107886001)(19580395003)(76576001)(450100001)(15975445007)(110136001)(19300405004)(54356999)(2351001)(86612001)(99286002)(19580405001)(2900100001)(19617315012)(87936001)(93886004)(122556002)(86362001)(16236675004)(2656002)(77156002)(62966003)(19625215002)(40100003)(50986999)(16601075003)(106116001)(92566002)(2501003)(46102003)(74316001)(76176999)(33656002)(102836002)(3826002)(222073002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0301MB0732; H:CY1PR0301MB0731.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-microsoft-antispam-prvs: <CY1PR0301MB0732B1781C6474752FF40AF482190@CY1PR0301MB0732.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002009)(5005006); SRVR:CY1PR0301MB0732; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0301MB0732; 
x-forefront-prvs: 0512CC5201
Content-Type: multipart/alternative; boundary="_000_CY1PR0301MB0731F4EBE5EB5C3340F7059282190CY1PR0301MB0731_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Mar 2015 21:58:26.1291 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0301MB0732
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/PX6Bgwy2dSbxohBnqx173S-P2yk>
Subject: [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: Wed, 11 Mar 2015 21:58:49 -0000

--_000_CY1PR0301MB0731F4EBE5EB5C3340F7059282190CY1PR0301MB0731_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

T29wcywgSSBzZWVtIHRvIGhhdmUgZHJvcHBlZCB0aGUgbGlzdC4NCg0KRnJvbTogU2hhd24gU3Rl
ZWxlDQpTZW50OiB3ZW5TamFqLCBtYXJjaCAxMSwgRElTIDIwMTUgdGVyYScgMTQ6MjMNClRvOiAn
QW5kcmV3IFN1bGxpdmFuJw0KU3ViamVjdDogUkU6IFtMdWNpZF0gW21hcmtAbWFjY2hpYXRvLmNv
bTogUmU6IE5vbi1ub3JtYWxpemFibGUgZGlhY3JpdGljcyAtIG5ldyBwcm9wZXJ0eV0NCg0KDQo+
ICAgICAgIEFueSBjaGFyYWN0ZXIgdGhhdCBjYW4gYmUgY29uZnVzZWQgZm9yDQoNCj4gICBhbm90
aGVyIG9uZSBjYW4gYmUgY2FsbGVkIGNvbmZ1c2FibGUsIGFuZCBjb25mdXNhYmlsaXR5IGNhbiBi
ZQ0KDQo+ICAgdGhvdWdodCBvZiBhcyBhIHNwZWN0cnVtIHdpdGggInZpc3VhbGx5IHNpbWlsYXIi
IGF0IG9uZSBlbmQsIGFuZA0KDQo+ICAgImhvbW9nbHlwaHMiIGF0IHRoZSBvdGhlci4gIChXZSB1
c2UgdGhlIHRlcm0gImhvbW9nbHlwaCIgc3RyaWN0bHk6DQoNCj4gICBjb2RlIHBvaW50cyB0aGF0
IG5vcm1hbGx5IHVzZSB0aGUgc2FtZSBnbHlwaCB3aGVuIHJlbmRlcmVkLikNCg0KDQoNCkl0IHNh
eXMgInRoZXJlJ3MgYSBzcGVjdHJ1bSIsIGJ1dCB0aGVuICJXZSB1c2UgdGhlIHRlcm0gImhvbW9n
bHlwaCIgc3RyaWN0bHk6Li4uIiAgVGhhdCBzZWVtcyBsaWtlIGFuIGF0dGVtcHQgYXQgYSBoYXJk
IGxpbmUsIHRob3VnaCBpdCBkb2VzIHNheSAibm9ybWFsbHkiDQoNCg0KDQo+IMq7b2tpbmENCg0K
DQoNCkhtbSwgSSdkIHRob3VnaHQgSSdkIHNlZW4gaXQgZGlmZmVyZW50LCBidXQgbWF5YmUgbm90
LCBzb3JyeSBpZiB0aGF0IHdhcyBhIGJhZCBleGFtcGxlLiAgQWN0dWFsbHksIFdpa2lwZWRpYSBo
YXMgYSBjb3VwbGUgZXhhbXBsZXPigKYgaHR0cDovL2VuLndpa2lwZWRpYS5vcmcvd2lraS8lQ0El
QkJPa2luYSBUaGF04oCZcyBwYXJ0IG9mIG15IGNvbmNlcm4gd2l0aCBzYXlpbmcg4oCcbm9ybWFs
bHkgcmVuZGVyZWQgdGhlIHNhbWXigJ0uICBUaGV5IGRvbuKAmXQgaGF2ZSB0byBiZSwgdGhhdOKA
mXMgdGhlIGFydCBvZiBjcmVhdGluZyBhIGZvbnQuDQoNCg0KDQo+IEkgdGhpbmsgd2UncmUgYWxs
IGF3YXJlIHRoYXQgeW91IGNhbid0IHRlbGwgZGV2ZWxvcGVycyB3aGF0IGZvbnQgdG8gdXNlLA0K
DQo+IGJ1dCB0aGVyZSBpcyBjbGVhcmx5IGFuIGluLXByaW5jaXBsZSBkaWZmZXJlbmNlIGJldHdl
ZW4gImNvdWxkIGJlDQoNCj4gbWl0aWdhdGVkIHdpdGggZm9udCIgYW5kICJjYW5ub3QgcG9zc2li
bHkgYmUgbWl0aWdhdGVkIHdpdGggZm9udCIuDQoNCg0KDQpJIHN1cHBvc2Ugc29tZSBjaGFyYWN0
ZXJzIGFyZSBsZXNzIGxpa2VseSB0byBiZSBhYmxlIHRvIGJlIG1pdGlnYXRlZCB3aXRoIGEgZm9u
dCwgaG93ZXZlciBJJ20gbm90IHN1cmUgSSBjb3VsZCBlYXNpbHkgZmluZCBhIGZvbnQgdGhhdCBt
aXRpZ2F0ZWQgYSBsYXJnZSBzZXQgb2YgY2hhcmFjdGVycy4gIEkgY291bGQgcGVyaGFwcyBzdWdn
ZXN0IHRoYXQgZm9udCBkZXNpZ25lcnMgY29uc2lkZXIgdGhlc2UgdGhpbmdzIHdoZW4gYWRkaW5n
IGNoYXJhY3RlcnMgb3IgbWFraW5nIGEgbmV3IGZvbnQsIGJ1dCAoYXMgbXkgb2tpbmEgY2hvaWNl
IGRlbW9uc3RyYXRlcykgSSdtIG5vdCBzdXJlIHdoaWNoIGZvbnQocykgaGF2ZSB3aGF0IGJlaGF2
aW9yLg0KDQoNCg0KQWx0aG91Z2ggSSB0aGluayBpdCdzIGZhaXIgZm9yIGFuIFJGQyB0byBpbmRp
Y2F0ZSB0aGF0IHNvbWUgZm9udHMgY2FuIGV4YWNlcmJhdGUgdGhlIHByb2JsZW0sIEknbSBub3Qg
c3VyZSB0aGF0IGl0J3MgZmFpciB0byBzdGF0ZSB0aGF0IHBhcnRzIG9mIHRoZSBwcm9ibGVtIGNv
dWxkIGJlICJzb2x2ZWQiIGJ5IGEgZm9udC4gIEZvciBleGFtcGxlLCBzb21ldGltZXMgdGhlIGZv
bnQgY2hvaWNlIG1heSBiZSB1bmRlciB0aGUgY29udHJvbCBvZiB0aGUgYXR0YWNrZXIuDQoNCg0K
DQo+ID4gQWRkaXRpb25hbGx5IGl0IGNvbnRpbnVlcyB0byB0cmVhdCB0aGVzZSBuZXdseSBub3Rp
Y2VkIGNoYXJhY3RlcnMgYXMgYQ0KDQo+ID4gc3BlY2lhbCBjYXNlIHdpdGhvdXQgY29uc2lkZXJp
bmcgdGhlIG1hbnkgZXhpc3RpbmcgcHJvYmxlbXMuDQoNCg0KDQo+IFdoZXJlLCBwbGVhc2U/DQoN
Cg0KDQo/PyAyLjIuMiBleHBsaWNpdGx5IGVtcGhhc2l6ZXMgdGhlIEFyYWJpYyBIYW16YSBBYm92
ZSBjYXNlLCB0aG91Z2ggaXQgZG9lcyBnbyBvbiB0byBtZW50aW9uIHRoYXQgdGhlcmUgYXJlIG90
aGVyIGNoYXJhY3RlcnMuICBIb3dldmVyIHRoZXJlIGFyZSBtYW55IGNvbmZ1c2FibGUgY2hhcmFj
dGVycyBpbiBJRE5BLiAgV29yc2UgdGhhbiBqdXN0IGNvbmZ1c2FibGUgZ2x5cGhzIHBlcmhhcHMg
YXJlIGNvbmZ1c2FibGUgY29uY2VwdHMsIGFzIHRoZSBkaXNjdXNzaW9uIG9mICJwcm9udW5jaWF0
aW9uIiBhbGx1ZGVzLiAgJ29raW5hIGlzbid0IGNvbmZ1c2FibGUgaWYgeW91IHByb25vdW5jZSBp
dCAnb2tpbmEgYW5kIHByb25vdW5jZSB0aGUgcXVvdGUgYXMgYSBsZWZ0IHF1b3RlLiAgWWV0IGl0
IGlzIHZpc3VhbGx5IGNvbmZ1c2FibGUuDQoNCg0KDQpGb3IgZXhhbXBsZSwgdGhpcyBmb2N1c2Vz
IG9uIHRoZSBleGFtcGxlcyBpbGx1bWluYXRlZCBieSBhIHZlcnkgZXNvdGVyaWMgQXJhYmljIGNv
ZGUgcG9pbnQuICBJ4oCZbSBkaWdyZXNzaW5nLCBidXQgSSBuZXZlciBzZWUgYW55IGRpc2N1c3Np
b24gb2Yg5ouUIHZzIOaLqCBvciAg5pqWIHZzIOaapyAoZGVwZW5kaW5nIG9uIGZvbnQsIFlNTVYp
LiAgSG93ZXZlciB0aG9zZSBjYW4gYmUgdmVyeSBjb25mdXNhYmxlIHRvIENoaW5lc2UgcmVhZGVy
cywgcGFydGljdWxhcmx5IGlmIHRoZSBjb250ZXh0IGxlYWRzIG9uZSB0byBleHBlY3Qgb25lIGNo
YXJhY3RlciBvciB0aGUgb3RoZXIuDQoNCg0KDQo+IElETkEgaXMgc3VwcG9zZWQgdG8gYmUgcHJv
dmlkaW5nIHVuaXF1ZSBpZGVudGlmaWVycy4gIEl0IGluIGZhY3QgZG9lcywgaW4gdGhlDQoNCj4g
c2Vuc2UgdGhhdCB3aGVuIGEgc2VyaWVzIG9mIFUtbGFiZWxzIG9yIEEtbGFiZWxzIGFyZSBwdXQg
dG9nZXRoZXIgdGhleSAocmVzcGVjdGl2ZWx5KQ0KDQo+IHByb2R1Y2UgZXhhY3RseSBvbmUgRlFE
TiB0aGF0IGNhbiBiZSBsb29rZWQgdXAuICBUaGF0J3Mgd2h5IGl0J3MgcGFydCBvZiB0aGUgcHJv
YmxlbS4NCg0KDQoNCkF0IHdoYXQgbGV2ZWw/ICBTdXJlLCB0aGV54oCZcmUgdW5pcXVlIGFzIGEg
YmluYXJ5IG51bWJlciBzZXF1ZW5jZS4gIEJ1dCBjbGVhcmx5IHRoZXkgYXJlbuKAmXQgdmlzdWFs
bHkgKG9yIGV2ZW4gYXVkaWJseSkgdW5pcXVlLCBVVFMjNDYgd2FzIGNyZWF0ZWQgZm9yIHRoYXQu
ICBOb3IgYXJlIHRoZXkgbGluZ3Vpc3RpY2FsbHkgdW5pcXVlIGFzIGFueSBvZiB0aGUgbnVtZXJv
dXMg4oCmbnltcyBjb3VsZCBjYXVzZSBjb25mdXNpb24uICBOb3IgYXJlIHRoZXkgYSB1bmlxdWUg
cmVzb3VyY2UgaWRlbnRpZmllciBhcyBtdWx0aXBsZSBuYW1lcyBjb3VsZCBhY3R1YWxseSBwb2lu
dCB0byB0aGUgc2FtZSBwbGFjZS4NCg0KDQoNCkNhbiB0aGV5IHByb3ZpZGUgYSB1bmlxdWUgRlFE
TiB0aGF0IG1hcHMgdG8gYSBzaW5nbGUgc2VydmVyPyAgU3VyZSwgYnV0IHRoZXkgY291bGQgZG8g
dGhhdCBpZiB3ZeKAmWQganVzdCBsZWZ0IGl0IGF0IOKAnGFsbCBvZiBVbmljb2Rl4oCdLg0KDQoN
Cg0KQXQgdGhlIG1hY2hpbmUgbGV2ZWwsIHllcywgSUROQSBwcm92aWRlcyB1bmlxdWUgaWRlbnRp
ZmllcnMuDQoNCg0KDQpBdCB0aGUgaHVtYW4gbGV2ZWwsIGl0IG1vc3QgY2VydGFpbmx5IGRvZXMg
bm90LiAgRm9yIGl0IHRvIGJlIHVuaXF1ZSBhdCBhIGh1bWFuIGxldmVsIHdvdWxkIG1lYW4gdGhh
dCBJ4oCZZCBoYXZlIHRvIGJlIGFibGUgdG8gaGFuZCBhIHdyaXR0ZW4gbm90ZSB0byBhbm90aGVy
IGh1bWFuIGFuZCB0aGV54oCZZCBiZSBhYmxlIHRvIGtleSB0aGF0IGluIHdpdGggMTAwJSBhY2N1
cmFjeS4gIFRoaXMgZG9jdW1lbnQgbm90ZXMgdGhlIHByb2JsZW1zIHdpdGggbCBhbmQgMSwgYW5k
IG9idmlvdXNseSAwIGFuZCBPLCBsZXQgYWxvbmUgYW55IG51bWJlciBvZiBvdGhlciBwcm9ibGVt
cy4NCg0KDQoNCkkgY3JlYXRlZCBodHRwOi8vTDMtRzAuY29tICBIb3dldmVyIGRlc3BpdGUgdGhh
dCwgbXkgbW5lbW9uaWMgaGFzIGxlZCBtZSB0byB0eXBlIGwzLWdvIG9uIG1vcmUgdGhhbiBvbmUg
b2NjYXNpb24uICBJdOKAmXMgYWxzbyBsZWQgbWUgdG8gdGVsbCB0aGUgbmFtZSB0byBvdGhlcnMg
d2hvbSBJ4oCZbSBmYWlybHkgc3VyZSBoYXZlIHRoZW4gbWlza2V5ZWQgaXQuDQoNCg0KDQpEZXNw
aXRlIGFsbCB0aGF0LCBJIGJlbGlldmUgdGhhdCBJRE4gc3VmZmljZXMgZm9yIHRoZSBwdXJwb3Nl
cyBvZiBhbGxvd2luZyB1c2VycyB0byBmaW5kIHdlYiBzZXJ2ZXJzICYgbWFjaGluZXMgdGhhdCB0
aGV5IGFyZSBpbnRlcmVzdGVkIGluLg0KDQoNCg0KSG93ZXZlciBJRE4gZG9lcyBub3Qgc3VmZmlj
ZSB0byBwcm92aWRlIGFuIHVuYW1iaWd1b3VzICh0byBodW1hbnMpIGlkZW50aWZpZXIuICBBZGRy
ZXNzaW5nIHRoZSBjbGFzcyBvZiBjaGFyYWN0ZXJzIGJlaW5nIGRpc2N1c3NlZCBoZWFyIHByb3Zp
ZGVzIG5vIHN0YXRpc3RpY2FsbHkgbWVhbmluZ2Z1bCByZWR1Y3Rpb24gb2YgdGhlIHBvdGVudGlh
bCBhbWJpZ3VpdHkgb2YgSUROLCBwYXJ0aWN1bGFybHkgYnkgYSBtYWxpY2lvdXMgYXR0YWNrZXIu
ICBJdCBhbHNvIHByb3ZpZGVzIG5vIHN0YXRpc3RpY2FsbHkgaW50ZXJlc3RpbmcgaW1wcm92ZW1l
bnQgaW4gdGhlIGFiaWxpdHkgZm9yIHdlbGwtaW50ZW50aW9uZWQgdXNlcnMgdG8gZmluZCB0aGUg
cmVzb3VyY2UgdGhleeKAmXJlIGxvb2tpbmcgZm9yLCBhcyBwcmVzdW1hYmx5IHRoZSB1c2VycyBp
bnRlcmVzdGVkIGluIHRoZSB2YXJpYXRpb25zIGRpc2N1c3NlZCBoZXJlIHdpbGwgYmUgZnVsbHkg
Y2FwYWJsZSBvZiB1c2luZyB0aGUgY29ycmVjdCB2YXJpYXRpb24uDQoNCg0KDQpTbyBJIGRvbuKA
mXQga25vdyB3aGF0IG91ciBnb2FscyBhcmUgaGVyZS4gIEkgY2FuIGVudmlzaW9uIHNldmVyYWwg
cG9zc2liaWxpdGllczoNCg0KDQoNCkEpICAgICBBIG1hY2hpbmUgaWRlbnRpZmllciBzdWl0YWJs
ZSBmb3IgdW5pcXVlbHkgaWRlbnRpZnlpbmcgcmVzb3VyY2VzLg0KDQphLiAgICAgIElNTywgdGhp
cyBpcyBhbHJlYWR5IHNvbHZlZC4gIE5vIG1hY2hpbmUgaXMgZ29pbmcgdG8gY29uZnVzZSBhbnkg
b2YgdGhlc2UsIHRoZXnigJlyZSBqdXN0IG51bWJlcnMuDQoNCmIuICAgICAgQWx0ZXJuYXRpdmVs
eSBtYWNoaW5lcyBjb3VsZCB1c2UgYWN0dWFsIG51bWJlcnMgKG9yIEdVSURzLCBvciBhIHNwZWNp
ZmljIGJpdCBvZiBBU0NJSSwgb3IgYW55IG90aGVyIG9mIGEgbnVtYmVyIG9mIHdheXMgb2YgZ2Vu
ZXJhdGluZyB0cnVlIHVuaXF1ZSBpZGVudGlmaWVycykuDQoNCkIpICAgICBXZSB3YW50IGEgaHVt
YW4gc2FmZSB1bmlxdWUgaWRlbnRpZmllci4NCg0KYS4gICAgICBUaGUgcHJvYmxlbSBkZXNjcmli
ZWQgaGVyZSBoYXMgbm8gbWVhbmluZ2Z1bCBpbXBhY3Qgb24gdGhlIHNjb3BlIG9mIHRoZSBwcm9i
bGVtLg0KDQpiLiAgICAgIEnigJltIG5vdCBzdXJlIHRoaXMgaXMgYWNoaWV2YWJsZS4gIEl04oCZ
bGwgYmUgaGFyZCBmb3Igc3VyZS4NCg0KYy4gICAgICBJTU8gc3VjaCBhbiBpZGVudGlmaWVyIGNv
dWxkIG5vdCBhbHNvIGJlIHBlcmZlY3RseSBsaW5ndWlzdGljLg0KDQogICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgaS4gICAgIFdl4oCZZCBoYXZlIHRv
IG1hcCB0aGluZ3MgdGhhdCBjb3VsZCBiZSBjb25mdXNlZCB0b2dldGhlciBpbiBhIHdheSB0aGF0
IHdvdWxkIGVuc3VyZSB0aGVyZSB3YXMgbm8gYW1iaWd1aXR5IGluIHRoZSByZXN1bHRpbmcgaWRl
bnRpZmllci4NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgaWkuICAgICBFZzogbWFwIExhdGluLCBHcmVlayAmIEN5cmlsbGljIGFzIGFwcHJvcHJp
YXRlLg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IGlpaS4gICAgIENsZWFybHkgc3VjaCBhbiBJRCBjb3VsZG7igJl0IHJvdW5kIHRyaXAgdG8gYSDi
gJxwcmV0dHnigJ0gaHVtYW4gZm9ybS4gIFRob3VnaCB3ZSBjb3VsZCBlbnN1cmUgYSBwcmV0dHkg
aHVtYW4gZm9ybSBhbHdheXMgbWFwcGVkIHRvIHRoZSBzYW1lIElEDQoNCmQuICAgICAgVGhpcyBp
c27igJl0IElETkENCg0KQykgICAgIFdlIHdhbnQgdG8gcHJvdmlkZSDigJxzYWZl4oCdIGJyb3dz
aW5nIHVzaW5nIElETkEuDQoNCmEuICAgICAgQWdhaW4sIHRoZSBpc3N1ZXMgYmVpbmcgZGlzY3Vz
c2VkIGhlcmUgaGF2ZSBubyBtZWFuaW5nZnVsIGltcGFjdCBvbiB0aGUgc2NvcGUgb2YgdGhpcyBw
cm9ibGVtDQoNCmIuICAgICAgVGhhdCB3b3VsZCBuZWVkIHRvIGNvbnNpZGVyIHNvbWUgb2YgdGhl
IGZhciBncmF5ZXIgYXJlYXMgdGhhbiBhcmUgYmVpbmcgZGlzY3Vzc2VkIGhlcmUuDQoNCmMuICAg
ICAgSSB0aGluayBvdGhlciB0ZWNobm9sb2dpZXMgYXJlIGFwcHJvcHJpYXRlIGhlcmUsIGVnOiBz
cGFtIGZpbHRlcnMsIGJsYWNrbGlzdHMsIHNhZmV0eSBwbHVnaW5zLCBjZXJ0aWZpY2F0ZXMsIGV0
Yy4NCg0KDQoNCkNsZWFybHkgc29tZSBwZW9wbGUgdGhpbmsgdGhhdCB0aGUgY2xhc3Mgb2YgdGhl
IHByb2JsZW0gaGVyZSBpcyBhIHJlYWwgcHJvYmxlbSwgYW5kIHByZXN1bWFibHkgdGhhdCBpdCBp
cyB3b3J0aCB0aGUgZWZmb3J0IHRvIGF0dGVtcHQgdG8gc29sdmUgdGhlIHBlcmNlaXZlZCBwcm9i
bGVtLiAgSW4gb3RoZXIgd29yZHMsIHRoYXQgc29sdmluZyB0aGlzIHdvdWxkIHByb3ZpZGUgc29t
ZSBzdGF0aXN0aWNhbCBhbmQgbWVhc3VyYWJsZSBpbXByb3ZlbWVudCBpbiB0aGUgc2VjdXJpdHkg
b2YgSUROQS4gIEhvd2V2ZXIsIEnigJltIG5vdCBhYmxlIHRvIGZvbGxvdyB0aGUgbG9naWMuDQoN
Cg0KDQpQZXJoYXBzIGlmIHRoZSBkb2N1bWVudCBjb3VsZCBwcm92aWRlIHNvbWUgc29ydCBvZiBz
dGF0ZW1lbnQgb2YgdGhlIHJlZHVjdGlvbiBvZiBjb25mdXNhYmxlIGNoYXJhY3RlcnMgdGhhdCB3
b3VsZCBoZWxwLiAgRWc6ICDigJxBZGRyZXNzaW5nIHRoaXMgaXNzdWUgd2lsbCByZWR1Y2UgOTAl
IG9mIHRoZSBjb25mdXNpb24gb2YgSUROIGxhYmVsc+KAnS4NCg0KDQoNCi1TaGF3bg0KDQoNCg0K
DQoNCg0KDQoNCg==

--_000_CY1PR0301MB0731F4EBE5EB5C3340F7059282190CY1PR0301MB0731_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiU2Vnb2UgVUkiOw0KCXBhbm9zZS0xOjIg
MTEgNSAyIDQgMiA0IDIgMiAzO30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Ik1hbGd1biBH
b3RoaWMiOw0KCXBhbm9zZS0xOjIgMTEgNSAzIDIgMCAwIDIgMCA0O30NCkBmb250LWZhY2UNCgl7
Zm9udC1mYW1pbHk6IlxATWFsZ3VuIEdvdGhpYyI7DQoJcGFub3NlLTE6MiAxMSA1IDMgMiAwIDAg
MiAwIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiTWljcm9zb2Z0IEpoZW5nSGVpIjsN
CglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFt
aWx5OiJcQE1pY3Jvc29mdCBKaGVuZ0hlaSI7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQph
OmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xv
cjojMDU2M0MxOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjoj
OTU0RjcyOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29QbGFpblRleHQsIGxp
Lk1zb1BsYWluVGV4dCwgZGl2Lk1zb1BsYWluVGV4dA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7
DQoJbXNvLXN0eWxlLWxpbms6IlBsYWluIFRleHQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJn
aW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2Fs
aWJyaSIsc2Fucy1zZXJpZjt9DQpzcGFuLlBsYWluVGV4dENoYXINCgl7bXNvLXN0eWxlLW5hbWU6
IlBsYWluIFRleHQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1s
aW5rOiJQbGFpbiBUZXh0IjsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpz
cGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250
LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBE
ZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7
fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBp
biAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rp
b24xO30NCi8qIExpc3QgRGVmaW5pdGlvbnMgKi8NCkBsaXN0IGwwDQoJe21zby1saXN0LWlkOjgx
OTgwNDU1MDsNCgltc28tbGlzdC10eXBlOmh5YnJpZDsNCgltc28tbGlzdC10ZW1wbGF0ZS1pZHM6
LTEwMDg1Nzc2MTYgLTQwMTU4NDY3NCA2NzY5ODcxMyA2NzY5ODcxNSA2NzY5ODcwMyA2NzY5ODcx
MyA2NzY5ODcxNSA2NzY5ODcwMyA2NzY5ODcxMyA2NzY5ODcxNTt9DQpAbGlzdCBsMDpsZXZlbDEN
Cgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YWxwaGEtdXBwZXI7DQoJbXNvLWxldmVsLXRleHQ6
IiUxXCkiOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9z
aXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47fQ0KQGxpc3QgbDA6bGV2ZWwyDQoJe21z
by1sZXZlbC1udW1iZXItZm9ybWF0OmFscGhhLWxvd2VyOw0KCW1zby1sZXZlbC10YWItc3RvcDpu
b25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1
aW47fQ0KQGxpc3QgbDA6bGV2ZWwzDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OnJvbWFuLWxv
d2VyOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRp
b246cmlnaHQ7DQoJdGV4dC1pbmRlbnQ6LTkuMHB0O30NCkBsaXN0IGwwOmxldmVsNA0KCXttc28t
bGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJ
dGV4dC1pbmRlbnQ6LS4yNWluO30NCkBsaXN0IGwwOmxldmVsNQ0KCXttc28tbGV2ZWwtbnVtYmVy
LWZvcm1hdDphbHBoYS1sb3dlcjsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2
ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluO30NCkBsaXN0IGww
OmxldmVsNg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpyb21hbi1sb3dlcjsNCgltc28tbGV2
ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOnJpZ2h0Ow0KCXRl
eHQtaW5kZW50Oi05LjBwdDt9DQpAbGlzdCBsMDpsZXZlbDcNCgl7bXNvLWxldmVsLXRhYi1zdG9w
Om5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0u
MjVpbjt9DQpAbGlzdCBsMDpsZXZlbDgNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YWxwaGEt
bG93ZXI7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3Np
dGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjt9DQpAbGlzdCBsMDpsZXZlbDkNCgl7bXNv
LWxldmVsLW51bWJlci1mb3JtYXQ6cm9tYW4tbG93ZXI7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5v
bmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpyaWdodDsNCgl0ZXh0LWluZGVudDotOS4w
cHQ7fQ0Kb2wNCgl7bWFyZ2luLWJvdHRvbTowaW47fQ0KdWwNCgl7bWFyZ2luLWJvdHRvbTowaW47
fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMg
djpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lm
IGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFw
IHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlm
XS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9IiMwNTYzQzEiIHZsaW5rPSIj
OTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+T29wcywgSSBzZWVtIHRvIGhhdmUgZHJvcHBl
ZCB0aGUgbGlzdC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
YSBuYW1lPSJfTWFpbEVuZENvbXBvc2UiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L2E+PC9wPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpu
b25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4g
MGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPkZyb206PC9iPiBTaGF3biBTdGVlbGUgPGJy
Pg0KPGI+U2VudDo8L2I+IHdlblNqYWosIG1hcmNoIDExLCBESVMgMjAxNSB0ZXJhJyAxNDoyMzxi
cj4NCjxiPlRvOjwvYj4gJ0FuZHJldyBTdWxsaXZhbic8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUkU6
IFtMdWNpZF0gW21hcmtAbWFjY2hpYXRvLmNvbTogUmU6IE5vbi1ub3JtYWxpemFibGUgZGlhY3Jp
dGljcyAtIG5ldyBwcm9wZXJ0eV08bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgQW55IGNoYXJh
Y3RlciB0aGF0IGNhbiBiZSBjb25mdXNlZCBmb3I8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPiZndDsmbmJzcDsmbmJzcDsgYW5vdGhlciBvbmUgY2FuIGJlIGNhbGxlZCBj
b25mdXNhYmxlLCBhbmQgY29uZnVzYWJpbGl0eSBjYW4gYmU8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPiZndDsmbmJzcDsmbmJzcDsgdGhvdWdodCBvZiBhcyBhIHNwZWN0
cnVtIHdpdGggJnF1b3Q7dmlzdWFsbHkgc2ltaWxhciZxdW90OyBhdCBvbmUgZW5kLCBhbmQ8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsmbmJzcDsmbmJzcDsgJnF1
b3Q7aG9tb2dseXBocyZxdW90OyBhdCB0aGUgb3RoZXIuJm5ic3A7IChXZSB1c2UgdGhlIHRlcm0g
JnF1b3Q7aG9tb2dseXBoJnF1b3Q7IHN0cmljdGx5OjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+Jmd0OyZuYnNwOyZuYnNwOyBjb2RlIHBvaW50cyB0aGF0IG5vcm1hbGx5
IHVzZSB0aGUgc2FtZSBnbHlwaCB3aGVuIHJlbmRlcmVkLik8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+SXQgc2F5cyAmcXVvdDt0aGVyZSdzIGEgc3BlY3RydW0mcXVvdDssIGJ1dCB0aGVu
ICZxdW90O1dlIHVzZSB0aGUgdGVybSAmcXVvdDtob21vZ2x5cGgmcXVvdDsgc3RyaWN0bHk6Li4u
JnF1b3Q7Jm5ic3A7IFRoYXQgc2VlbXMgbGlrZSBhbiBhdHRlbXB0IGF0IGEgaGFyZCBsaW5lLCB0
aG91Z2ggaXQgZG9lcyBzYXkgJnF1b3Q7bm9ybWFsbHkmcXVvdDs8bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+Jmd0OyDKu29raW5hIDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5I
bW0sIEknZCB0aG91Z2h0IEknZCBzZWVuIGl0IGRpZmZlcmVudCwgYnV0IG1heWJlIG5vdCwgc29y
cnkgaWYgdGhhdCB3YXMgYSBiYWQgZXhhbXBsZS4gJm5ic3A7QWN0dWFsbHksIFdpa2lwZWRpYSBo
YXMgYSBjb3VwbGUgZXhhbXBsZXPigKYNCjxhIGhyZWY9Imh0dHA6Ly9lbi53aWtpcGVkaWEub3Jn
L3dpa2kvJUNBJUJCT2tpbmEiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O1NlZ29lIFVJJnF1b3Q7LHNhbnMtc2VyaWYiPmh0dHA6Ly9lbi53aWtpcGVkaWEu
b3JnL3dpa2kvJUNBJUJCT2tpbmE8L3NwYW4+PC9hPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Ymxh
Y2siPiBUaGF04oCZcyBwYXJ0DQogb2YgbXkgY29uY2VybiB3aXRoIHNheWluZyDigJxub3JtYWxs
eSByZW5kZXJlZCB0aGUgc2FtZeKAnS4mbmJzcDsgVGhleSBkb27igJl0IGhhdmUgdG8gYmUsIHRo
YXTigJlzIHRoZSBhcnQgb2YgY3JlYXRpbmcgYSBmb250Ljwvc3Bhbj48bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+Jmd0OyBJIHRoaW5rIHdlJ3JlIGFsbCBhd2FyZSB0aGF0IHlvdSBjYW4n
dCB0ZWxsIGRldmVsb3BlcnMgd2hhdCBmb250IHRvIHVzZSw8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPiZndDsgYnV0IHRoZXJlIGlzIGNsZWFybHkgYW4gaW4tcHJpbmNp
cGxlIGRpZmZlcmVuY2UgYmV0d2VlbiAmcXVvdDtjb3VsZCBiZQ0KPG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IG1pdGlnYXRlZCB3aXRoIGZvbnQmcXVvdDsgYW5k
ICZxdW90O2Nhbm5vdCBwb3NzaWJseSBiZSBtaXRpZ2F0ZWQgd2l0aCBmb250JnF1b3Q7LjxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPkkgc3Vw
cG9zZSBzb21lIGNoYXJhY3RlcnMgYXJlIGxlc3MgbGlrZWx5IHRvIGJlIGFibGUgdG8gYmUgbWl0
aWdhdGVkIHdpdGggYSBmb250LCBob3dldmVyIEknbSBub3Qgc3VyZSBJIGNvdWxkIGVhc2lseSBm
aW5kIGEgZm9udCB0aGF0IG1pdGlnYXRlZCBhIGxhcmdlIHNldCBvZiBjaGFyYWN0ZXJzLiZuYnNw
OyBJIGNvdWxkIHBlcmhhcHMgc3VnZ2VzdCB0aGF0IGZvbnQNCiBkZXNpZ25lcnMgY29uc2lkZXIg
dGhlc2UgdGhpbmdzIHdoZW4gYWRkaW5nIGNoYXJhY3RlcnMgb3IgbWFraW5nIGEgbmV3IGZvbnQs
IGJ1dCAoYXMgbXkgb2tpbmEgY2hvaWNlIGRlbW9uc3RyYXRlcykgSSdtIG5vdCBzdXJlIHdoaWNo
IGZvbnQocykgaGF2ZSB3aGF0IGJlaGF2aW9yLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9ImNv
bG9yOmJsYWNrIj5BbHRob3VnaCBJIHRoaW5rIGl0J3MgZmFpciBmb3IgYW4gUkZDIHRvIGluZGlj
YXRlIHRoYXQgc29tZSBmb250cyBjYW4gZXhhY2VyYmF0ZSB0aGUgcHJvYmxlbSwgSSdtIG5vdCBz
dXJlIHRoYXQgaXQncyBmYWlyIHRvIHN0YXRlIHRoYXQgcGFydHMgb2YgdGhlIHByb2JsZW0gY291
bGQgYmUgJnF1b3Q7c29sdmVkJnF1b3Q7IGJ5IGEgZm9udC4mbmJzcDsgRm9yIGV4YW1wbGUsIHNv
bWV0aW1lcw0KIHRoZSBmb250IGNob2ljZSBtYXkgYmUgdW5kZXIgdGhlIGNvbnRyb2wgb2YgdGhl
IGF0dGFja2VyLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQi
PjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jmd0OyAmZ3Q7IEFkZGl0aW9uYWxseSBpdCBjb250aW51
ZXMgdG8gdHJlYXQgdGhlc2UgbmV3bHkgbm90aWNlZCBjaGFyYWN0ZXJzIGFzIGENCjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jmd0OyAmZ3Q7IHNwZWNpYWwgY2FzZSB3
aXRob3V0IGNvbnNpZGVyaW5nIHRoZSBtYW55IGV4aXN0aW5nIHByb2JsZW1zLjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IFdoZXJlLCBwbGVhc2U/PG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxl
PSJjb2xvcjpibGFjayI+Pz8gMi4yLjIgZXhwbGljaXRseSBlbXBoYXNpemVzIHRoZSBBcmFiaWMg
SGFtemEgQWJvdmUgY2FzZSwgdGhvdWdoIGl0IGRvZXMgZ28gb24gdG8gbWVudGlvbiB0aGF0IHRo
ZXJlIGFyZSBvdGhlciBjaGFyYWN0ZXJzLiZuYnNwOyBIb3dldmVyIHRoZXJlIGFyZSBtYW55IGNv
bmZ1c2FibGUgY2hhcmFjdGVycyBpbiBJRE5BLiZuYnNwOyBXb3JzZSB0aGFuIGp1c3QgY29uZnVz
YWJsZQ0KIGdseXBocyBwZXJoYXBzIGFyZSBjb25mdXNhYmxlIGNvbmNlcHRzLCBhcyB0aGUgZGlz
Y3Vzc2lvbiBvZiAmcXVvdDtwcm9udW5jaWF0aW9uJnF1b3Q7IGFsbHVkZXMuJm5ic3A7ICdva2lu
YSBpc24ndCBjb25mdXNhYmxlIGlmIHlvdSBwcm9ub3VuY2UgaXQgJ29raW5hIGFuZCBwcm9ub3Vu
Y2UgdGhlIHF1b3RlIGFzIGEgbGVmdCBxdW90ZS4mbmJzcDsgWWV0IGl0IGlzIHZpc3VhbGx5IGNv
bmZ1c2FibGUuJm5ic3A7DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+
Rm9yIGV4YW1wbGUsIHRoaXMgZm9jdXNlcyBvbiB0aGUgZXhhbXBsZXMgaWxsdW1pbmF0ZWQgYnkg
YSB2ZXJ5IGVzb3RlcmljIEFyYWJpYyBjb2RlIHBvaW50LiZuYnNwOyBJ4oCZbSBkaWdyZXNzaW5n
LCBidXQgSSBuZXZlciBzZWUgYW55IGRpc2N1c3Npb24gb2YNCjwvc3Bhbj48c3BhbiBzdHlsZT0i
Y29sb3I6YmxhY2siPuaLlDwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPiB2czwvc3Bh
bj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7TWFsZ3VuIEdvdGhpYyZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOmJsYWNrIj4NCjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1
b3Q7TWljcm9zb2Z0IEpoZW5nSGVpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPuaLqCA8
L3NwYW4+DQo8c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPm9yPC9zcGFuPjxzcGFuIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtNaWNyb3NvZnQgSmhlbmdIZWkmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjpibGFjayI+DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJzcDs8L3NwYW4+
PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj7mmpY8L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOmJs
YWNrIj4gdnMNCjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7TWljcm9zb2Z0
IEpoZW5nSGVpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPuaapzwvc3Bhbj48c3BhbiBz
dHlsZT0iY29sb3I6YmxhY2siPiAoZGVwZW5kaW5nIG9uIGZvbnQsIFlNTVYpLiZuYnNwOyBIb3dl
dmVyIHRob3NlIGNhbiBiZSB2ZXJ5IGNvbmZ1c2FibGUgdG8gQ2hpbmVzZSByZWFkZXJzLCBwYXJ0
aWN1bGFybHkgaWYgdGhlIGNvbnRleHQgbGVhZHMgb25lIHRvIGV4cGVjdCBvbmUgY2hhcmFjdGVy
DQogb3IgdGhlIG90aGVyLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jmd0
OyBJRE5BIGlzIHN1cHBvc2VkIHRvIGJlIHByb3ZpZGluZyB1bmlxdWUgaWRlbnRpZmllcnMuJm5i
c3A7IEl0IGluIGZhY3QgZG9lcywgaW4gdGhlPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij4mZ3Q7IHNlbnNlIHRoYXQgd2hlbiBhIHNlcmllcyBvZiBVLWxhYmVscyBvciBB
LWxhYmVscyBhcmUgcHV0IHRvZ2V0aGVyIHRoZXkgKHJlc3BlY3RpdmVseSkNCjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jmd0OyBwcm9kdWNlIGV4YWN0bHkgb25lIEZR
RE4gdGhhdCBjYW4gYmUgbG9va2VkIHVwLiZuYnNwOyBUaGF0J3Mgd2h5IGl0J3MgcGFydCBvZiB0
aGUgcHJvYmxlbS48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFu
IHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj5BdCB3aGF0IGxldmVs
PyZuYnNwOyBTdXJlLCB0aGV54oCZcmUgdW5pcXVlIGFzIGEgYmluYXJ5IG51bWJlciBzZXF1ZW5j
ZS4mbmJzcDsgQnV0IGNsZWFybHkgdGhleSBhcmVu4oCZdCB2aXN1YWxseSAob3IgZXZlbiBhdWRp
Ymx5KSB1bmlxdWUsIFVUUyM0NiB3YXMgY3JlYXRlZCBmb3IgdGhhdC4mbmJzcDsgTm9yIGFyZSB0
aGV5IGxpbmd1aXN0aWNhbGx5IHVuaXF1ZSBhcyBhbnkgb2YgdGhlIG51bWVyb3VzDQog4oCmbnlt
cyBjb3VsZCBjYXVzZSBjb25mdXNpb24uJm5ic3A7IE5vciBhcmUgdGhleSBhIHVuaXF1ZSByZXNv
dXJjZSBpZGVudGlmaWVyIGFzIG11bHRpcGxlIG5hbWVzIGNvdWxkIGFjdHVhbGx5IHBvaW50IHRv
IHRoZSBzYW1lIHBsYWNlLiZuYnNwOw0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0iY29sb3I6
YmxhY2siPkNhbiB0aGV5IHByb3ZpZGUgYSB1bmlxdWUgRlFETiB0aGF0IG1hcHMgdG8gYSBzaW5n
bGUgc2VydmVyPyZuYnNwOyBTdXJlLCBidXQgdGhleSBjb3VsZCBkbyB0aGF0IGlmIHdl4oCZZCBq
dXN0IGxlZnQgaXQgYXQg4oCcYWxsIG9mIFVuaWNvZGXigJ0uPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBz
dHlsZT0iY29sb3I6YmxhY2siPkF0IHRoZSBtYWNoaW5lIGxldmVsLCB5ZXMsIElETkEgcHJvdmlk
ZXMgdW5pcXVlIGlkZW50aWZpZXJzLiZuYnNwOw0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0i
Y29sb3I6YmxhY2siPkF0IHRoZSBodW1hbiBsZXZlbCwgaXQgbW9zdCBjZXJ0YWlubHkgZG9lcyBu
b3QuICZuYnNwO0ZvciBpdCB0byBiZSB1bmlxdWUgYXQgYSBodW1hbiBsZXZlbCB3b3VsZCBtZWFu
IHRoYXQgSeKAmWQgaGF2ZSB0byBiZSBhYmxlIHRvIGhhbmQgYSB3cml0dGVuIG5vdGUgdG8gYW5v
dGhlciBodW1hbiBhbmQgdGhleeKAmWQgYmUgYWJsZSB0byBrZXkgdGhhdCBpbiB3aXRoIDEwMCUg
YWNjdXJhY3kuJm5ic3A7DQogVGhpcyBkb2N1bWVudCBub3RlcyB0aGUgcHJvYmxlbXMgd2l0aCBs
IGFuZCAxLCBhbmQgb2J2aW91c2x5IDAgYW5kIE8sIGxldCBhbG9uZSBhbnkgbnVtYmVyIG9mIG90
aGVyIHByb2JsZW1zLiZuYnNwOw0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0iY29sb3I6Ymxh
Y2siPkkgY3JlYXRlZCA8YSBocmVmPSJodHRwOi8vTDMtRzAuY29tIj4NCmh0dHA6Ly9MMy1HMC5j
b208L2E+Jm5ic3A7IEhvd2V2ZXIgZGVzcGl0ZSB0aGF0LCBteSBtbmVtb25pYyBoYXMgbGVkIG1l
IHRvIHR5cGUgbDMtZ28gb24gbW9yZSB0aGFuIG9uZSBvY2Nhc2lvbi4mbmJzcDsgSXTigJlzIGFs
c28gbGVkIG1lIHRvIHRlbGwgdGhlIG5hbWUgdG8gb3RoZXJzIHdob20gSeKAmW0gZmFpcmx5IHN1
cmUgaGF2ZSB0aGVuIG1pc2tleWVkIGl0LiZuYnNwOw0KPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHls
ZT0iY29sb3I6YmxhY2siPkRlc3BpdGUgYWxsIHRoYXQsIEkgYmVsaWV2ZSB0aGF0IElETiBzdWZm
aWNlcyBmb3IgdGhlIHB1cnBvc2VzIG9mIGFsbG93aW5nIHVzZXJzIHRvIGZpbmQgd2ViIHNlcnZl
cnMgJmFtcDsgbWFjaGluZXMgdGhhdCB0aGV5IGFyZSBpbnRlcmVzdGVkIGluLiZuYnNwOw0KPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9
ImNvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPkhvd2V2ZXIgSUROIGRvZXMgbm90
IHN1ZmZpY2UgdG8gcHJvdmlkZSBhbiB1bmFtYmlndW91cyAodG8gaHVtYW5zKSBpZGVudGlmaWVy
LiZuYnNwOyBBZGRyZXNzaW5nIHRoZSBjbGFzcyBvZiBjaGFyYWN0ZXJzIGJlaW5nIGRpc2N1c3Nl
ZCBoZWFyIHByb3ZpZGVzIG5vIHN0YXRpc3RpY2FsbHkgbWVhbmluZ2Z1bCByZWR1Y3Rpb24gb2Yg
dGhlIHBvdGVudGlhbCBhbWJpZ3VpdHkNCiBvZiBJRE4sIHBhcnRpY3VsYXJseSBieSBhIG1hbGlj
aW91cyBhdHRhY2tlci4mbmJzcDsgSXQgYWxzbyBwcm92aWRlcyBubyBzdGF0aXN0aWNhbGx5IGlu
dGVyZXN0aW5nIGltcHJvdmVtZW50IGluIHRoZSBhYmlsaXR5IGZvciB3ZWxsLWludGVudGlvbmVk
IHVzZXJzIHRvIGZpbmQgdGhlIHJlc291cmNlIHRoZXnigJlyZSBsb29raW5nIGZvciwgYXMgcHJl
c3VtYWJseSB0aGUgdXNlcnMgaW50ZXJlc3RlZCBpbiB0aGUgdmFyaWF0aW9ucyBkaXNjdXNzZWQg
aGVyZQ0KIHdpbGwgYmUgZnVsbHkgY2FwYWJsZSBvZiB1c2luZyB0aGUgY29ycmVjdCB2YXJpYXRp
b24uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4g
c3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPlNvIEkgZG9u4oCZdCBr
bm93IHdoYXQgb3VyIGdvYWxzIGFyZSBoZXJlLiZuYnNwOyBJIGNhbiBlbnZpc2lvbiBzZXZlcmFs
IHBvc3NpYmlsaXRpZXM6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0IiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbjt0ZXh0
LWluZGVudDotLjI1aW47bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzIiPg0KPCFbaWYgIXN1cHBvcnRM
aXN0c10+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdu
b3JlIj5BKTxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90
OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRp
Zl0+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj5BIG1hY2hpbmUgaWRlbnRpZmllciBzdWl0YWJs
ZSBmb3IgdW5pcXVlbHkgaWRlbnRpZnlpbmcgcmVzb3VyY2VzLjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiIHN0eWxlPSJtYXJnaW4tbGVmdDoxLjBpbjt0ZXh0
LWluZGVudDotLjI1aW47bXNvLWxpc3Q6bDAgbGV2ZWwyIGxmbzIiPg0KPCFbaWYgIXN1cHBvcnRM
aXN0c10+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdu
b3JlIj5hLjxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90
OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48
IVtlbmRpZl0+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj5JTU8sIHRoaXMgaXMgYWxyZWFkeSBz
b2x2ZWQuJm5ic3A7IE5vIG1hY2hpbmUgaXMgZ29pbmcgdG8gY29uZnVzZSBhbnkgb2YgdGhlc2Us
IHRoZXnigJlyZSBqdXN0IG51bWJlcnMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjEuMGluO3RleHQtaW5kZW50Oi0uMjVp
bjttc28tbGlzdDpsMCBsZXZlbDIgbGZvMiI+DQo8IVtpZiAhc3VwcG9ydExpc3RzXT48c3BhbiBz
dHlsZT0iY29sb3I6YmxhY2siPjxzcGFuIHN0eWxlPSJtc28tbGlzdDpJZ25vcmUiPmIuPHNwYW4g
c3R5bGU9ImZvbnQ6Ny4wcHQgJnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4mbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3Bh
biBzdHlsZT0iY29sb3I6YmxhY2siPkFsdGVybmF0aXZlbHkgbWFjaGluZXMgY291bGQgdXNlIGFj
dHVhbCBudW1iZXJzIChvciBHVUlEcywgb3IgYSBzcGVjaWZpYyBiaXQgb2YgQVNDSUksIG9yIGFu
eSBvdGhlciBvZiBhIG51bWJlciBvZiB3YXlzIG9mIGdlbmVyYXRpbmcgdHJ1ZSB1bmlxdWUgaWRl
bnRpZmllcnMpLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQi
IHN0eWxlPSJtYXJnaW4tbGVmdDouNWluO3RleHQtaW5kZW50Oi0uMjVpbjttc28tbGlzdDpsMCBs
ZXZlbDEgbGZvMiI+DQo8IVtpZiAhc3VwcG9ydExpc3RzXT48c3BhbiBzdHlsZT0iY29sb3I6Ymxh
Y2siPjxzcGFuIHN0eWxlPSJtc28tbGlzdDpJZ25vcmUiPkIpPHNwYW4gc3R5bGU9ImZvbnQ6Ny4w
cHQgJnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsN
Cjwvc3Bhbj48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2si
PldlIHdhbnQgYSBodW1hbiBzYWZlIHVuaXF1ZSBpZGVudGlmaWVyLjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiIHN0eWxlPSJtYXJnaW4tbGVmdDoxLjBpbjt0
ZXh0LWluZGVudDotLjI1aW47bXNvLWxpc3Q6bDAgbGV2ZWwyIGxmbzIiPg0KPCFbaWYgIXN1cHBv
cnRMaXN0c10+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6
SWdub3JlIj5hLjxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZx
dW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwvc3Bh
bj48IVtlbmRpZl0+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj5UaGUgcHJvYmxlbSBkZXNjcmli
ZWQgaGVyZSBoYXMgbm8gbWVhbmluZ2Z1bCBpbXBhY3Qgb24gdGhlIHNjb3BlIG9mIHRoZSBwcm9i
bGVtLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiIHN0eWxl
PSJtYXJnaW4tbGVmdDoxLjBpbjt0ZXh0LWluZGVudDotLjI1aW47bXNvLWxpc3Q6bDAgbGV2ZWwy
IGxmbzIiPg0KPCFbaWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48
c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3JlIj5iLjxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZx
dW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNr
Ij5J4oCZbSBub3Qgc3VyZSB0aGlzIGlzIGFjaGlldmFibGUuJm5ic3A7IEl04oCZbGwgYmUgaGFy
ZCBmb3Igc3VyZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
IiBzdHlsZT0ibWFyZ2luLWxlZnQ6MS4waW47dGV4dC1pbmRlbnQ6LS4yNWluO21zby1saXN0Omww
IGxldmVsMiBsZm8yIj4NCjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSJjb2xvcjpi
bGFjayI+PHNwYW4gc3R5bGU9Im1zby1saXN0Oklnbm9yZSI+Yy48c3BhbiBzdHlsZT0iZm9udDo3
LjBwdCAmcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOw0KPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxzcGFuIHN0eWxlPSJjb2xv
cjpibGFjayI+SU1PIHN1Y2ggYW4gaWRlbnRpZmllciBjb3VsZCBub3QgYWxzbyBiZSBwZXJmZWN0
bHkgbGluZ3Vpc3RpYy4mbmJzcDsNCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiIHN0eWxlPSJtYXJnaW4tbGVmdDoxLjVpbjt0ZXh0LWluZGVudDotMS41aW47
bXNvLXRleHQtaW5kZW50LWFsdDotOS4wcHQ7bXNvLWxpc3Q6bDAgbGV2ZWwzIGxmbzIiPg0KPCFb
aWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48c3BhbiBzdHlsZT0i
bXNvLWxpc3Q6SWdub3JlIj48c3BhbiBzdHlsZT0iZm9udDo3LjBwdCAmcXVvdDtUaW1lcyBOZXcg
Um9tYW4mcXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9zcGFuPmkuPHNwYW4gc3R5bGU9
ImZvbnQ6Ny4wcHQgJnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4mbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsgPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxzcGFuIHN0eWxlPSJjb2xv
cjpibGFjayI+V2XigJlkIGhhdmUgdG8gbWFwIHRoaW5ncyB0aGF0IGNvdWxkIGJlIGNvbmZ1c2Vk
IHRvZ2V0aGVyIGluIGEgd2F5IHRoYXQgd291bGQgZW5zdXJlIHRoZXJlIHdhcyBubyBhbWJpZ3Vp
dHkgaW4gdGhlIHJlc3VsdGluZyBpZGVudGlmaWVyLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiIHN0eWxlPSJtYXJnaW4tbGVmdDoxLjVpbjt0ZXh0LWluZGVu
dDotMS41aW47bXNvLXRleHQtaW5kZW50LWFsdDotOS4wcHQ7bXNvLWxpc3Q6bDAgbGV2ZWwzIGxm
bzIiPg0KPCFbaWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48c3Bh
biBzdHlsZT0ibXNvLWxpc3Q6SWdub3JlIj48c3BhbiBzdHlsZT0iZm9udDo3LjBwdCAmcXVvdDtU
aW1lcyBOZXcgUm9tYW4mcXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9zcGFuPmlpLjxzcGFuIHN0
eWxlPSJmb250OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7IDwvc3Bhbj48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBzdHlsZT0i
Y29sb3I6YmxhY2siPkVnOiBtYXAgTGF0aW4sIEdyZWVrICZhbXA7IEN5cmlsbGljIGFzIGFwcHJv
cHJpYXRlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiIHN0
eWxlPSJtYXJnaW4tbGVmdDoxLjVpbjt0ZXh0LWluZGVudDotMS41aW47bXNvLXRleHQtaW5kZW50
LWFsdDotOS4wcHQ7bXNvLWxpc3Q6bDAgbGV2ZWwzIGxmbzIiPg0KPCFbaWYgIXN1cHBvcnRMaXN0
c10+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3Jl
Ij48c3BhbiBzdHlsZT0iZm9udDo3LjBwdCAmcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOw0KPC9zcGFuPmlpaS48c3BhbiBzdHlsZT0iZm9udDo3LjBwdCAmcXVvdDtUaW1lcyBO
ZXcgUm9tYW4mcXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8L3NwYW4+PC9zcGFuPjwv
c3Bhbj48IVtlbmRpZl0+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj5DbGVhcmx5IHN1Y2ggYW4g
SUQgY291bGRu4oCZdCByb3VuZCB0cmlwIHRvIGEg4oCccHJldHR54oCdIGh1bWFuIGZvcm0uJm5i
c3A7IFRob3VnaCB3ZSBjb3VsZCBlbnN1cmUgYSBwcmV0dHkgaHVtYW4gZm9ybSBhbHdheXMgbWFw
cGVkIHRvIHRoZSBzYW1lIElEPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjEuMGluO3RleHQtaW5kZW50Oi0uMjVpbjttc28t
bGlzdDpsMCBsZXZlbDIgbGZvMiI+DQo8IVtpZiAhc3VwcG9ydExpc3RzXT48c3BhbiBzdHlsZT0i
Y29sb3I6YmxhY2siPjxzcGFuIHN0eWxlPSJtc28tbGlzdDpJZ25vcmUiPmQuPHNwYW4gc3R5bGU9
ImZvbnQ6Ny4wcHQgJnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4mbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBzdHls
ZT0iY29sb3I6YmxhY2siPlRoaXMgaXNu4oCZdCBJRE5BPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW47dGV4dC1pbmRl
bnQ6LS4yNWluO21zby1saXN0OmwwIGxldmVsMSBsZm8yIj4NCjwhW2lmICFzdXBwb3J0TGlzdHNd
PjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PHNwYW4gc3R5bGU9Im1zby1saXN0Oklnbm9yZSI+
Qyk8c3BhbiBzdHlsZT0iZm9udDo3LjBwdCAmcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxz
cGFuIHN0eWxlPSJjb2xvcjpibGFjayI+V2Ugd2FudCB0byBwcm92aWRlIOKAnHNhZmXigJ0gYnJv
d3NpbmcgdXNpbmcgSUROQS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0IiBzdHlsZT0ibWFyZ2luLWxlZnQ6MS4waW47dGV4dC1pbmRlbnQ6LS4yNWluO21zby1s
aXN0OmwwIGxldmVsMiBsZm8yIj4NCjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSJj
b2xvcjpibGFjayI+PHNwYW4gc3R5bGU9Im1zby1saXN0Oklnbm9yZSI+YS48c3BhbiBzdHlsZT0i
Zm9udDo3LjBwdCAmcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOw0KPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxzcGFuIHN0eWxl
PSJjb2xvcjpibGFjayI+QWdhaW4sIHRoZSBpc3N1ZXMgYmVpbmcgZGlzY3Vzc2VkIGhlcmUgaGF2
ZSBubyBtZWFuaW5nZnVsIGltcGFjdCBvbiB0aGUgc2NvcGUgb2YgdGhpcyBwcm9ibGVtPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCIgc3R5bGU9Im1hcmdpbi1s
ZWZ0OjEuMGluO3RleHQtaW5kZW50Oi0uMjVpbjttc28tbGlzdDpsMCBsZXZlbDIgbGZvMiI+DQo8
IVtpZiAhc3VwcG9ydExpc3RzXT48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPjxzcGFuIHN0eWxl
PSJtc28tbGlzdDpJZ25vcmUiPmIuPHNwYW4gc3R5bGU9ImZvbnQ6Ny4wcHQgJnF1b3Q7VGltZXMg
TmV3IFJvbWFuJnF1b3Q7Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj48
L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPlRoYXQgd291
bGQgbmVlZCB0byBjb25zaWRlciBzb21lIG9mIHRoZSBmYXIgZ3JheWVyIGFyZWFzIHRoYW4gYXJl
IGJlaW5nIGRpc2N1c3NlZCBoZXJlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiIHN0eWxlPSJtYXJnaW4tbGVmdDoxLjBpbjt0ZXh0LWluZGVudDotLjI1aW47
bXNvLWxpc3Q6bDAgbGV2ZWwyIGxmbzIiPg0KPCFbaWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gc3R5
bGU9ImNvbG9yOmJsYWNrIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3JlIj5jLjxzcGFuIHN0
eWxlPSJmb250OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4g
c3R5bGU9ImNvbG9yOmJsYWNrIj5JIHRoaW5rIG90aGVyIHRlY2hub2xvZ2llcyBhcmUgYXBwcm9w
cmlhdGUgaGVyZSwgZWc6IHNwYW0gZmlsdGVycywgYmxhY2tsaXN0cywgc2FmZXR5IHBsdWdpbnMs
IGNlcnRpZmljYXRlcywgZXRjLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNr
Ij5DbGVhcmx5IHNvbWUgcGVvcGxlIHRoaW5rIHRoYXQgdGhlIGNsYXNzIG9mIHRoZSBwcm9ibGVt
IGhlcmUgaXMgYSByZWFsIHByb2JsZW0sIGFuZCBwcmVzdW1hYmx5IHRoYXQgaXQgaXMgd29ydGgg
dGhlIGVmZm9ydCB0byBhdHRlbXB0IHRvIHNvbHZlIHRoZSBwZXJjZWl2ZWQgcHJvYmxlbS4mbmJz
cDsgSW4gb3RoZXIgd29yZHMsIHRoYXQgc29sdmluZyB0aGlzIHdvdWxkDQogcHJvdmlkZSBzb21l
IHN0YXRpc3RpY2FsIGFuZCBtZWFzdXJhYmxlIGltcHJvdmVtZW50IGluIHRoZSBzZWN1cml0eSBv
ZiBJRE5BLiZuYnNwOyBIb3dldmVyLCBJ4oCZbSBub3QgYWJsZSB0byBmb2xsb3cgdGhlIGxvZ2lj
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIHN0
eWxlPSJjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj5QZXJoYXBzIGlmIHRoZSBk
b2N1bWVudCBjb3VsZCBwcm92aWRlIHNvbWUgc29ydCBvZiBzdGF0ZW1lbnQgb2YgdGhlIHJlZHVj
dGlvbiBvZiBjb25mdXNhYmxlIGNoYXJhY3RlcnMgdGhhdCB3b3VsZCBoZWxwLiZuYnNwOyBFZzom
bmJzcDsg4oCcQWRkcmVzc2luZyB0aGlzIGlzc3VlIHdpbGwgcmVkdWNlIDkwJSBvZiB0aGUgY29u
ZnVzaW9uIG9mIElETiBsYWJlbHPigJ0uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBzdHlsZT0iY29sb3I6
YmxhY2siPi1TaGF3bjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRl
eHQiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_CY1PR0301MB0731F4EBE5EB5C3340F7059282190CY1PR0301MB0731_--


From nobody Wed Mar 11 15:01:30 2015
Return-Path: <john-ietf@jck.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 499EE1A8834 for <lucid@ietfa.amsl.com>; Wed, 11 Mar 2015 15:01:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 a_hqg69fu-oL for <lucid@ietfa.amsl.com>; Wed, 11 Mar 2015 15:01:27 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B45A1A87EF for <lucid@ietf.org>; Wed, 11 Mar 2015 15:01:27 -0700 (PDT)
Received: from [198.252.137.35] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1YVogw-0001WR-IB for lucid@ietf.org; Wed, 11 Mar 2015 18:01:26 -0400
Date: Wed, 11 Mar 2015 18:01:21 -0400
From: John C Klensin <john-ietf@jck.com>
To: lucid@ietf.org
Message-ID: <7F4D2DD785AC80C3C981B100@JcK-HP8200.jck.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="==========61373BE580086B96F020=========="
X-SA-Exim-Connect-IP: 198.252.137.35
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/RA87dUr9rJc0-RpsKh9iTMTGO6A>
Subject: [Lucid] FWD: I-D ACTION:draft-klensin-idna-5892upd-unicode70-04.txt
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: Wed, 11 Mar 2015 22:01:29 -0000

--==========61373BE580086B96F020==========
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

For those who haven't seen this announcement, the draft referred
to in Andrew's and my earlier comments (and the IAB Statement)
has now been posted.

    john


---------- Forwarded Message ----------
Date: Wednesday, March 11, 2015 12:43 -0700
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-klensin-idna-5892upd-unicode70-04.txt

A new Internet-Draft is available from the on-line
Internet-Drafts directories.


    Title         : IDNA Update for Unicode 7.0.0

    Author(s)     : J. Klensin, et al
    Filename      : draft-klensin-idna-5892upd-unicode70
    Pages         : 29 
    Date          : 2015-03-11 
    
   The current version of the IDNA specifications anticipated
that each    new version of Unicode would be reviewed to verify
that no changes    had been introduced that required adjustments
to the set of rules    and, in particular, whether new
exceptions or backward compatibility    adjustments were needed.
The review for Unicode 7.0.0 first    identified a potentially
problematic new code point and then a much    more general and
difficult issue with Unicode normalization.  This
specification discusses those issues and proposes updates to IDNA
   and, potentially, the way the IETF handles comparison of
identifiers    more generally, especially when there is no
associated language or    language identification.  It also
applies an editorial clarification    to RFC 5892 that was the
subject of an earlier erratum and updates    RFC 5894 to point
to the issues involved.

A URL for this Internet-Draft is:
https://www.ietf.org/internet-drafts/draft-klensin-idna-5892upd-
unicode70-04.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

---------- End Forwarded Message ----------




--==========61373BE580086B96F020==========
Content-Type: message/rfc822;
 name="I-D ACTION:draft-klensin-idna-5892upd-unicode70-04.txt"

Return-path: <i-d-announce-bounces@ietf.org>
Envelope-to: klensin+ietf@jck.com
Delivery-date: Wed, 11 Mar 2015 15:43:50 -0400
Received: from mail.ietf.org ([4.31.198.44])
	by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD))
	(envelope-from <i-d-announce-bounces@ietf.org>)
	id 1YVmXm-0001Aj-KZ
	for klensin+ietf@jck.com; Wed, 11 Mar 2015 15:43:50 -0400
Received: from ietfa.amsl.com (localhost [IPv6:::1])
	by ietfa.amsl.com (Postfix) with ESMTP id 073A41A1EEE;
	Wed, 11 Mar 2015 12:43:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1426103018; bh=KX+DvlZsEiGF5wjek2FC6yDtszUjvLO8FiyqmSkP3xM=;
	h=MIME-Version:Content-Type:From:To:Subject:Message-ID:Date:
	 Reply-To:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:
	 List-Subscribe:Sender;
	b=u1h7saVKaBgQ2305tn5vHV0aABlxewnK8hvRSSjTJGdc+7NfoR8sW+Hq8wYk8+LnM
	 qEZfMjV7cGETARmYn/Vq0epLojD4YumJfwTfvI+vQphhffLVzA5Wc+/So0yqtDtDUy
	 LNnLNJxCc2WhwrnHTsnM2m4yUEuO5xglUI+MZGfY=
X-Original-To: i-d-announce@ietfa.amsl.com
Delivered-To: i-d-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id EF3FB1A1EEE
 for <i-d-announce@ietfa.amsl.com>; Wed, 11 Mar 2015 12:43:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level: 
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 qkg_T9uOpZyJ for <i-d-announce@ietfa.amsl.com>;
 Wed, 11 Mar 2015 12:43:34 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1])
 by ietfa.amsl.com (Postfix) with ESMTP id D95C41A1B8B
 for <i-d-announce@ietf.org>; Wed, 11 Mar 2015 12:43:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D ACTION:draft-klensin-idna-5892upd-unicode70-04.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.12.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150311194334.3270.84635.idtracker@ietfa.amsl.com>
Date: Wed, 11 Mar 2015 12:43:34 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/i-d-announce/ugJxd9_o3OYLDlWVebv8nCCSjNs>
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: internet-drafts@ietf.org
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i-d-announce>,
 <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/i-d-announce/>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
 <mailto:i-d-announce-request@ietf.org?subject=subscribe>
Errors-To: i-d-announce-bounces@ietf.org
Sender: "I-D-Announce" <i-d-announce-bounces@ietf.org>
X-SA-Exim-Connect-IP: 4.31.198.44
X-SA-Exim-Mail-From: i-d-announce-bounces@ietf.org
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false

--NextPart

A new Internet-Draft is available from the on-line Internet-Drafts directories.


    Title         : IDNA Update for Unicode 7.0.0

    Author(s)     : J. Klensin, et al
    Filename      : draft-klensin-idna-5892upd-unicode70
    Pages         : 29 
    Date          : 2015-03-11 
    
   The current version of the IDNA specifications anticipated that each
   new version of Unicode would be reviewed to verify that no changes
   had been introduced that required adjustments to the set of rules
   and, in particular, whether new exceptions or backward compatibility
   adjustments were needed.  The review for Unicode 7.0.0 first
   identified a potentially problematic new code point and then a much
   more general and difficult issue with Unicode normalization.  This
   specification discusses those issues and proposes updates to IDNA
   and, potentially, the way the IETF handles comparison of identifiers
   more generally, especially when there is no associated language or
   language identification.  It also applies an editorial clarification
   to RFC 5892 that was the subject of an earlier erratum and updates
   RFC 5894 to point to the issues involved.

A URL for this Internet-Draft is:
https://www.ietf.org/internet-drafts/draft-klensin-idna-5892upd-unicode70-04.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
 name="draft-klensin-idna-5892upd-unicode70"; site="ftp.ietf.org";
 access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2015-03-11124334.I-D@ietf.org>


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--NextPart--


--==========61373BE580086B96F020==========--


From nobody Wed Mar 11 17:26:18 2015
Return-Path: <klensin@jck.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 529E91A1DBE for <lucid@ietfa.amsl.com>; Wed, 11 Mar 2015 13:08:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 p78Bo9dk2Ccm for <lucid@ietfa.amsl.com>; Wed, 11 Mar 2015 13:08:13 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 424CF1A6F15 for <lucid@ietf.org>; Wed, 11 Mar 2015 13:08:13 -0700 (PDT)
Received: from [198.252.137.35] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <klensin@jck.com>) id 1YVmvM-0001FD-82 for lucid@ietf.org; Wed, 11 Mar 2015 16:08:12 -0400
Date: Wed, 11 Mar 2015 16:08:07 -0400
From: John C Klensin <klensin@jck.com>
To: lucid@ietf.org
Message-ID: <5160D4E03DD89C9BD15D7194@JcK-HP8200.jck.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="==========7D72985DE2C08CD10651=========="
X-SA-Exim-Connect-IP: 198.252.137.35
X-SA-Exim-Mail-From: klensin@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/d98IPcxvwlnf2NThNq964DAjmEg>
X-Mailman-Approved-At: Wed, 11 Mar 2015 17:26:16 -0700
Subject: [Lucid] FWD: I-D ACTION:draft-klensin-idna-5892upd-unicode70-04.txt
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: Wed, 11 Mar 2015 20:08:15 -0000

--==========7D72985DE2C08CD10651==========
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

For those who haven't seen this announcement, the draft referred
to in Andrew's and my earlier comments (and the IAB Statement)
has now been posted.

    john


---------- Forwarded Message ----------
Date: Wednesday, March 11, 2015 12:43 -0700
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-klensin-idna-5892upd-unicode70-04.txt

A new Internet-Draft is available from the on-line
Internet-Drafts directories.


    Title         : IDNA Update for Unicode 7.0.0

    Author(s)     : J. Klensin, et al
    Filename      : draft-klensin-idna-5892upd-unicode70
    Pages         : 29 
    Date          : 2015-03-11 
    
   The current version of the IDNA specifications anticipated
that each    new version of Unicode would be reviewed to verify
that no changes    had been introduced that required adjustments
to the set of rules    and, in particular, whether new
exceptions or backward compatibility    adjustments were needed.
The review for Unicode 7.0.0 first    identified a potentially
problematic new code point and then a much    more general and
difficult issue with Unicode normalization.  This
specification discusses those issues and proposes updates to IDNA
   and, potentially, the way the IETF handles comparison of
identifiers    more generally, especially when there is no
associated language or    language identification.  It also
applies an editorial clarification    to RFC 5892 that was the
subject of an earlier erratum and updates    RFC 5894 to point
to the issues involved.

A URL for this Internet-Draft is:
https://www.ietf.org/internet-drafts/draft-klensin-idna-5892upd-
unicode70-04.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

---------- End Forwarded Message ----------




--==========7D72985DE2C08CD10651==========
Content-Type: message/rfc822;
 name="I-D ACTION:draft-klensin-idna-5892upd-unicode70-04.txt"

Return-path: <i-d-announce-bounces@ietf.org>
Envelope-to: klensin+ietf@jck.com
Delivery-date: Wed, 11 Mar 2015 15:43:50 -0400
Received: from mail.ietf.org ([4.31.198.44])
	by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD))
	(envelope-from <i-d-announce-bounces@ietf.org>)
	id 1YVmXm-0001Aj-KZ
	for klensin+ietf@jck.com; Wed, 11 Mar 2015 15:43:50 -0400
Received: from ietfa.amsl.com (localhost [IPv6:::1])
	by ietfa.amsl.com (Postfix) with ESMTP id 073A41A1EEE;
	Wed, 11 Mar 2015 12:43:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1426103018; bh=KX+DvlZsEiGF5wjek2FC6yDtszUjvLO8FiyqmSkP3xM=;
	h=MIME-Version:Content-Type:From:To:Subject:Message-ID:Date:
	 Reply-To:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:
	 List-Subscribe:Sender;
	b=u1h7saVKaBgQ2305tn5vHV0aABlxewnK8hvRSSjTJGdc+7NfoR8sW+Hq8wYk8+LnM
	 qEZfMjV7cGETARmYn/Vq0epLojD4YumJfwTfvI+vQphhffLVzA5Wc+/So0yqtDtDUy
	 LNnLNJxCc2WhwrnHTsnM2m4yUEuO5xglUI+MZGfY=
X-Original-To: i-d-announce@ietfa.amsl.com
Delivered-To: i-d-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id EF3FB1A1EEE
 for <i-d-announce@ietfa.amsl.com>; Wed, 11 Mar 2015 12:43:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level: 
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 qkg_T9uOpZyJ for <i-d-announce@ietfa.amsl.com>;
 Wed, 11 Mar 2015 12:43:34 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1])
 by ietfa.amsl.com (Postfix) with ESMTP id D95C41A1B8B
 for <i-d-announce@ietf.org>; Wed, 11 Mar 2015 12:43:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D ACTION:draft-klensin-idna-5892upd-unicode70-04.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.12.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150311194334.3270.84635.idtracker@ietfa.amsl.com>
Date: Wed, 11 Mar 2015 12:43:34 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/i-d-announce/ugJxd9_o3OYLDlWVebv8nCCSjNs>
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: internet-drafts@ietf.org
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i-d-announce>,
 <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/i-d-announce/>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
 <mailto:i-d-announce-request@ietf.org?subject=subscribe>
Errors-To: i-d-announce-bounces@ietf.org
Sender: "I-D-Announce" <i-d-announce-bounces@ietf.org>
X-SA-Exim-Connect-IP: 4.31.198.44
X-SA-Exim-Mail-From: i-d-announce-bounces@ietf.org
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false

--NextPart

A new Internet-Draft is available from the on-line Internet-Drafts directories.


    Title         : IDNA Update for Unicode 7.0.0

    Author(s)     : J. Klensin, et al
    Filename      : draft-klensin-idna-5892upd-unicode70
    Pages         : 29 
    Date          : 2015-03-11 
    
   The current version of the IDNA specifications anticipated that each
   new version of Unicode would be reviewed to verify that no changes
   had been introduced that required adjustments to the set of rules
   and, in particular, whether new exceptions or backward compatibility
   adjustments were needed.  The review for Unicode 7.0.0 first
   identified a potentially problematic new code point and then a much
   more general and difficult issue with Unicode normalization.  This
   specification discusses those issues and proposes updates to IDNA
   and, potentially, the way the IETF handles comparison of identifiers
   more generally, especially when there is no associated language or
   language identification.  It also applies an editorial clarification
   to RFC 5892 that was the subject of an earlier erratum and updates
   RFC 5894 to point to the issues involved.

A URL for this Internet-Draft is:
https://www.ietf.org/internet-drafts/draft-klensin-idna-5892upd-unicode70-04.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
 name="draft-klensin-idna-5892upd-unicode70"; site="ftp.ietf.org";
 access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2015-03-11124334.I-D@ietf.org>


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--NextPart--


--==========7D72985DE2C08CD10651==========--


From nobody Wed Mar 18 18:40:25 2015
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 D5A401AC3CE for <lucid@ietfa.amsl.com>; Wed, 18 Mar 2015 18:40:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.559
X-Spam-Level: **
X-Spam-Status: No, score=2.559 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 wFQAXokCzELO for <lucid@ietfa.amsl.com>; Wed, 18 Mar 2015 18:40:22 -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 AEC301AC3C8 for <lucid@ietf.org>; Wed, 18 Mar 2015 18:40:22 -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 925568A035 for <lucid@ietf.org>; Thu, 19 Mar 2015 01:40:20 +0000 (UTC)
Date: Wed, 18 Mar 2015 21:40:19 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: lucid@ietf.org
Message-ID: <20150319014018.GI5743@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CY1PR0301MB0731F4EBE5EB5C3340F7059282190@CY1PR0301MB0731.namprd03.prod.outlook.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/izzVIqE56AXPZ-UOtiVZ7alSgJg>
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 01:40:25 -0000

On Wed, Mar 11, 2015 at 09:58:26PM +0000, Shawn Steele wrote:
> 
> 
> It says "there's a spectrum", but then "We use the term "homoglyph" strictly:..."  That seems like an attempt at a hard line, though it does say "normally"
> 

As I said in an exchange off-list, the point here is to situate
"homoglyph" in a spectrum of different cases, all of which are more or
less confusable.  rn and m are plainly not homoglyphs, because if you
set them in even moderately large type with serifs you can immediately
see the difference.  Latin A and Cyrillic A are just homoglyphs: no
reasonable font even tries to differentiate them, partly because as a
matter of history they evolved from the same form and therefore it's
not surprising that they look the same now.  They're different
abstract characters because they are in different writing systems, but
they look identical.

> > ʻokina
> 
> 
> 
> Hmm, I'd thought I'd seen it different, but maybe not, sorry if that was a bad example.

It wasn't a bad example.  It was a good example, but of something
different than what you intended. :) The point is precisely that these
fine details are going to matter in this discussion, so we need to
attend to them.
 
> 
> Although I think it's fair for an RFC to indicate that some fonts can exacerbate the problem, I'm not sure that it's fair to state that parts of the problem could be "solved" by a font.  For example, sometimes the font choice may be under the control of the attacker.
> 

I think the draft says "mitigate", not "solve".
 
> ?? 2.2.2 explicitly emphasizes the Arabic Hamza Above case, though it does go on to mention that there are other characters.

There's a _whole appendix_ that attempts to illustrate the range of
the issue, and the text goes out of its way to point the reader at
that and to avoid talking about specific characters except to explain
the history, because we're trying to attend to the general problem.

> For example, this focuses on the examples illuminated by a very esoteric Arabic code point.  I’m digressing, but I never see any discussion of 拔 vs 拨 or  暖 vs 暧 (depending on font, YMMV)

In fact there is a (different) Han character in the appendix.

> > IDNA is supposed to be providing unique identifiers.

> At what level?

At every level.  DNS names are exact-match.  Each identifier is
unique.

In the DNS, color.tld and colour.tld are not the same identifier.
Conceptually they are confusing for Canadians (and spelled wrong for
USians and English respectively), but they're different.  We want that
to be as reliable as possible, and we seem to have stumbled on a class
of cases for which we cannot make derivative-property rules.  I think
that might be a problem, which is why I wanted to get a discussion
going in order to understand.

> Can they provide a unique FQDN that maps to a single server?  Sure, but they could do that if we’d just left it at “all of Unicode”.
> 

No, we would not have.  Are you quite sure you understand how the
matching rules work?  It was _never_ "all of Unicode", because that doesn't even catch the normalization cases.

> At the human level, it most certainly does not.

That's sort of the point, here, though.  But I think your description
of how this would work (elided) presents a false dichotomy: either
everyone can get this with 100% accuracy or it's not a unique
identifier.  By similar reasoning, if you cannot eliminate all crime
then you should have no laws.

> B)     We want a human safe unique identifier.

It seems to me that, more mildly, we could just say that we want one
as safe as possible, or whose "safety" we understand.  Remember, this
is a BoF and the point of the I-D was to get people to understand and
articulate problems.

> b.      I’m not sure this is achievable.  It’ll be hard for sure.

Yes.

> c.      IMO such an identifier could not also be perfectly linguistic.

Existing identifiers of all sorts are already not linguistic.  I
observe that "anvilwalrusden" is not, to my knowledge, a word in any
language.  Certainly "dyn" (my employer) is not -- the name is a
constant source of fun around the office, since virtually everybody
pronounces it "wrong" (i.e. correctly according to the
locally-prevailing norms of pronunciation).

>                                                    ii.     Eg: map Latin, Greek & Cyrillic as appropriate.
> 

This might actually not be a bad idea.

> d.      This isn’t IDNA

This BoF is not only about IDNA.

> 
> Clearly some people think that the class of the problem here is a real problem, and presumably that it is worth the effort to attempt to solve the perceived problem.

I would be satisfied if, in Dallas, we came away with a clear
delineation of the problem, or even a clear idea of how we might
delineate the problem.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Wed Mar 18 19:12:04 2015
Return-Path: <Shawn.Steele@microsoft.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 780D81A8029 for <lucid@ietfa.amsl.com>; Wed, 18 Mar 2015 19:12:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.003
X-Spam-Level: 
X-Spam-Status: No, score=-0.003 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 3GFyzOYUMzH0 for <lucid@ietfa.amsl.com>; Wed, 18 Mar 2015 19:11:59 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0105.outbound.protection.outlook.com [65.55.169.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E82B1A6FF2 for <lucid@ietf.org>; Wed, 18 Mar 2015 19:11:59 -0700 (PDT)
Received: from BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) by BLUPR03MB1380.namprd03.prod.outlook.com (25.163.81.139) with Microsoft SMTP Server (TLS) id 15.1.112.19; Thu, 19 Mar 2015 02:11:56 +0000
Received: from BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) by BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) with mapi id 15.01.0112.000; Thu, 19 Mar 2015 02:11:57 +0000
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, "lucid@ietf.org" <lucid@ietf.org>
Thread-Topic: [Lucid] FW: [mark@macchiato.com: Re: Non-normalizable diacritics - new property]
Thread-Index: AQHQYeWvrIxB8XNhl06inScNBJS0IJ0jC27g
Date: Thu, 19 Mar 2015 02:11:56 +0000
Message-ID: <BLUPR03MB1378184CE32E928A3086665582010@BLUPR03MB1378.namprd03.prod.outlook.com>
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>
In-Reply-To: <20150319014018.GI5743@mx1.yitter.info>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [50.34.94.236]
authentication-results: anvilwalrusden.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR03MB1380;
x-microsoft-antispam-prvs: <BLUPR03MB13803BEE5CD2A7E08BA7271182010@BLUPR03MB1380.namprd03.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(51704005)(2950100001)(2656002)(54356999)(66066001)(40100003)(92566002)(2900100001)(50986999)(102836002)(62966003)(77156002)(76576001)(2501003)(74316001)(46102003)(99286002)(33656002)(86362001)(107886001)(87936001)(106116001)(122556002)(222073002)(220923002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR03MB1380; H:BLUPR03MB1378.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:BLUPR03MB1380; BCL:0; PCL:0; RULEID:;  SRVR:BLUPR03MB1380; 
x-forefront-prvs: 052017CAF1
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Mar 2015 02:11:56.8706 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB1380
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/q1d7ldeDzb98rsOGtXuB2o9aAkw>
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:12:01 -0000

PiA+ID4gSUROQSBpcyBzdXBwb3NlZCB0byBiZSBwcm92aWRpbmcgdW5pcXVlIGlkZW50aWZpZXJz
Lg0KDQo+ID4gQXQgd2hhdCBsZXZlbD8NCg0KPiBBdCBldmVyeSBsZXZlbC4gIEROUyBuYW1lcyBh
cmUgZXhhY3QtbWF0Y2guICBFYWNoIGlkZW50aWZpZXIgaXMgdW5pcXVlLg0KDQpGb3IgdGhlIG1h
Y2hpbmUsIHN1cmUuICBCdXQgaWYgeW91IHRocm93IGluIGZvbnQgd2VpcmRuZXNzIGFuZCBzdHVm
ZiwgdGhleSBiZWNvbWUgbm9uLXVuaXF1ZSAodG8gaHVtYW5zLCBub3QgdG8gbWFjaGluZXMpIGV2
ZW4gaW4gQVNDSUkuICBUbyBtYWtlIHRoZW0gYmUgbW9yZSB1bmlxdWUgb25lIGhhcyB0byBpbXBv
c2UgbW9yZSBydWxlcywgbGlrZSAidXNlIGEgZGVjZW50IGZvbnQiLCAibG93ZXJjYXNlIGV2ZXJ5
dGhpbmciLiAgRXRjLiANCg0KPiA+IEF0IHRoZSBodW1hbiBsZXZlbCwgaXQgbW9zdCBjZXJ0YWlu
bHkgZG9lcyBub3QuDQoNCj4gVGhhdCdzIHNvcnQgb2YgdGhlIHBvaW50LCBoZXJlLCB0aG91Z2gu
ICBCdXQgSSB0aGluayB5b3VyIGRlc2NyaXB0aW9uIG9mIGhvdyB0aGlzIHdvdWxkIHdvcmsgKGVs
aWRlZCkgcHJlc2VudHMgYSBmYWxzZSBkaWNob3RvbXk6IGVpdGhlciBldmVyeW9uZSBjYW4gZ2V0
IHRoaXMgd2l0aCAxMDAlIGFjY3VyYWN5IG9yIGl0J3Mgbm90IGEgdW5pcXVlIGlkZW50aWZpZXIu
ICBCeSBzaW1pbGFyIHJlYXNvbmluZywgaWYgeW91IGNhbm5vdCBlbGltaW5hdGUgYWxsIGNyaW1l
IHRoZW4geW91IHNob3VsZCBoYXZlIG5vIGxhd3MuDQoNCk5vLCBldmVuIGFsbCBORkMgb3IgTkZL
QyB3b3VsZCBiZSAxMDAlIHVuaXF1ZSB0byB0aGUgbWFjaGluZSwgaG93ZXZlciBJRE4gaXMgc3Ry
aWN0ZXIgdGhhbiB0aGF0LiAgVG8gaHVtYW5zIGl0J3MgaW1wb3NzaWJsZSB0byBiZSAxMDAlIHVu
aXF1ZSAodW5sZXNzIHdlIHdlbnQgdG8gb25seSBBU0NJSSBBLVowLTkgYW5kIHRocmV3IG91dCBh
IGZldyBvZiB0aG9zZSkuICBXaGF0IEknbSBxdWVzdGlvbmluZyBpcyBob3cgdW5pcXVlIGlzIGdv
b2QgZW5vdWdoPyAgQnkgeW91ciBhbmFsb2d5LCBhZGRpbmcgYSBidW5jaCBvZiBsYXdzIGlzbid0
IG5lY2Vzc2FyaWx5IGdvaW5nIHRvIHN0b3AgY3JpbWUuICBUaGVyZSdzIGEgbG90IG9mIGRlYmF0
ZSBhYm91dCB0aGF0LCBhbmQgd2UgY2FuIHNlZSB0aGF0IGRpZmZlcmVudCBsb2NhbGVzIGhhdmUg
ZGlmZmVyZW50IGNyaW1lIHJhdGVzLCBzb21lIGxvdyBjcmltZSBhbmQgbG93IGxhd3MsIHNvbWUg
aGlnaCBjcmltZSBhbmQgbG90cyBvZiBsYXdzLCBhbmQgZXZlcnl3aGVyZSBpbmJldHdlZW4uICBU
aGUgY2hhbGxlbmdlIGlzIHRvIGJhbGFuY2UgdGhlIHJlc3VsdHMgb24gY3JpbWUgd2l0aCB0aGUg
b3ZlcmhlYWQgb2YgdGhlIGxhd3MuDQoNCj4gPiBCKSAgICAgV2Ugd2FudCBhIGh1bWFuIHNhZmUg
dW5pcXVlIGlkZW50aWZpZXIuDQoNCj4gSXQgc2VlbXMgdG8gbWUgdGhhdCwgbW9yZSBtaWxkbHks
IHdlIGNvdWxkIGp1c3Qgc2F5IHRoYXQgd2Ugd2FudCBvbmUgYXMgc2FmZSBhcyBwb3NzaWJsZSwg
b3Igd2hvc2UgInNhZmV0eSIgd2UgdW5kZXJzdGFuZC4gIA0KDQpJIGFncmVlLCB3aXRoIHRoZSBj
YXZlYXQgdGhhdCB3ZSBhbHNvIGJhbGFuY2UgdGhlIGNvc3QgYW5kIHRoZSBiZW5lZml0cy9yaXNr
LiAgIkFzIHNhZmUgYXMgcG9zc2libGUiIHdvdWxkIGFyZ3VlIGFnYWluc3QgYWxsb3dpbmcgYm90
aCAwIGFuZCBPIG9yIGwgYW5kIDEgdG8gZXhpc3QuICBBbG1vc3Qgbm9ib2R5J3MgYXJndWVkIHRo
YXQsIHNvIEkgZG9uJ3QgdGhpbmsgd2Ugd2FudCAiQXMgc2FmZSBhcyBwb3NzaWJsZSIuICANCg0K
DQo+ID4gYy4gICAgICBJTU8gc3VjaCBhbiBpZGVudGlmaWVyIGNvdWxkIG5vdCBhbHNvIGJlIHBl
cmZlY3RseSBsaW5ndWlzdGljLg0KDQo+IEV4aXN0aW5nIGlkZW50aWZpZXJzIG9mIGFsbCBzb3J0
cyBhcmUgYWxyZWFkeSBub3QgbGluZ3Vpc3RpYy4gIEkgb2JzZXJ2ZSB0aGF0ICJhbnZpbHdhbHJ1
c2RlbiIgaXMgbm90LCB0byBteSBrbm93bGVkZ2UsIGEgd29yZCBpbiBhbnkgbGFuZ3VhZ2UuICAN
Cg0KV2UgZG8gc2VlbSB0byBoYXZlIHNvbWUgZGVzaXJlIHRvIGJlIGxpbmd1aXN0aWMuICBPdGhl
cndpc2UgU2hhcnAtUyBhbmQgR3JlZWsgZGlkbid0IG5lZWQgdG91Y2hlZC4gIEkgdGhpbmsgdGhl
IG9waW5pb25zIG9mIHRoZSBjb21wdXRlciBzY2llbnRpc3RzIGFuZCB1c2VycyBpbiBtYXJrZXRp
bmcgZGVwYXJ0bWVudHMgbWF5IGRpZmZlciBncmVhdGx5IGhlcmUuICBNYW55IHVzZXJzIHRyZWF0
IGRvbWFpbiBuYW1lcyBtb3JlIGFzIGEgbmF0dXJhbCBsaW5ndWlzdGljIHRoaW5nIHRoYW4gYSBt
YXRoZW1hdGljYWwgaWRlbnRpZmllci4gIEVub3VnaCB0byBzdWUgb3ZlciBuYW1lcy4NCg0KPiA+
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIGlpLiAg
ICAgRWc6IG1hcCBMYXRpbiwgR3JlZWsgJiBDeXJpbGxpYyBhcyBhcHByb3ByaWF0ZS4NCg0KPiBU
aGlzIG1pZ2h0IGFjdHVhbGx5IG5vdCBiZSBhIGJhZCBpZGVhLg0KDQpJZiB3ZSBuZWVkIG1vcmUg
c3RydWN0dXJlLCB0aGF0IHdvdWxkIGJlIG15IHByZWZlcmVuY2UgKGtpbmRhKS4gIFdlIGNhbid0
IGJlIHBlcmZlY3QsIGJ1dCBpZiB3ZSBtYXBwZWQgbW9zdCBvZiB0aGUgbW9yZSBvYnZpb3VzIGNv
bmZ1c2FibGVzIHRvZ2V0aGVyLCB0aGVuIHdlJ2QgYXZvaWQgc29tZSBvZiB0aGlzIHByb2JsZW0u
DQoNCj4gPiBkLiAgICAgIFRoaXMgaXNu4oCZdCBJRE5BDQoNCj4gVGhpcyBCb0YgaXMgbm90IG9u
bHkgYWJvdXQgSUROQS4NCg0KV2hpY2ggbWF5IGJlIHBhcnQgb2YgdGhlIHByb2JsZW0uICBJRE5B
IGlzICJwZXJtaXNzaXZlIiBhbmQgY2F0ZXJzIHRvIGxpbmd1aXN0aWMgcmVwcmVzZW50YXRpb25z
IG9mIHRoaW5ncy4gIFdoaWNoIElNTyBpcyBoYXJkIHRvIHJlY29uY2lsZSB3aXRoIGEgc3RyaWN0
IGlkZW50aWZpZXIuDQoNCi1TaGF3bg0K


From nobody Wed Mar 18 19:30:37 2015
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


From nobody Wed Mar 18 21:21:32 2015
Return-Path: <asmusf@ix.netcom.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 392F41A876D for <lucid@ietfa.amsl.com>; Wed, 18 Mar 2015 21:21:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 CEsiBydsj-eC for <lucid@ietfa.amsl.com>; Wed, 18 Mar 2015 21:21:29 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id 5DAC01A8766 for <lucid@ietf.org>; Wed, 18 Mar 2015 21:21:29 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=X7tY5ADkG5R/xmZ8UIIIK9Hs3qlcvHUY5cPWjAsH5PMs7eBdXd0yjDkg0G+hB48l; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [72.244.206.133] (helo=[192.168.0.107]) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <asmusf@ix.netcom.com>) id 1YYRxX-0006Su-II for lucid@ietf.org; Thu, 19 Mar 2015 00:21:28 -0400
Message-ID: <550A4EC6.3090203@ix.netcom.com>
Date: Wed, 18 Mar 2015 21:21:26 -0700
From: Asmus Freytag <asmusf@ix.netcom.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: lucid@ietf.org
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> <20150319023029.GA6046@mx1.yitter.info>
In-Reply-To: <20150319023029.GA6046@mx1.yitter.info>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2b65b6112f8911537c9cad3191107dd905d55cc620145e8f3350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 72.244.206.133
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/IvWKLvce3V6DRnZK2JNSaer9IDg>
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 04:21:31 -0000

On 3/18/2015 7:30 PM, Andrew Sullivan wrote:
> 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.

As in, buggy implementations?
>
>>   What I'm questioning is how unique is good enough?
> Surely that's part of what we're trying to understand?

I understood the IETF concern this way:

"While we all know that human perception can be tricked, and poor 
rendering doesn't help, we are concerned about the case where careful, 
conscientious users cannot tell apart two identifiers that the protocol 
deems unique."

While this looks superficially like the normalization issue, it is not, 
but it may be (perhaps partially) something that can be addressed at the 
protocol level with reasonable cost. So why not deal with it there?

Yes, this doesn't address the rest of the human perception issues, but 
because the subset we identified doesn't really hinge on any human 
inadequacies, addressing the current issue should not interfere with 
other solutions that address these inadequacies.


>
>> 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.
As  a btw:

I'm amazed at the near total lack of IDNs registered for the Latin 
script in the root. It seems that people like the "fall-back" nature of 
non-accented ASCII labels for anything that should be accessed 
universally (top level).

So, for that script at least, you could say that users don't like being 
surprised by a more linguistically accurate, but less universally 
accessible way of constructing identifiers.

Interesting....

A./



From nobody Wed Mar 18 21:31:44 2015
Return-Path: <Shawn.Steele@microsoft.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 CEEC21A876F for <lucid@ietfa.amsl.com>; Wed, 18 Mar 2015 21:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 r8kVVqjD8z1g for <lucid@ietfa.amsl.com>; Wed, 18 Mar 2015 21:31:41 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0781.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::781]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18C6D1A876D for <lucid@ietf.org>; Wed, 18 Mar 2015 21:31:41 -0700 (PDT)
Received: from BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) by BLUPR03MB1377.namprd03.prod.outlook.com (25.163.81.11) with Microsoft SMTP Server (TLS) id 15.1.118.21; Thu, 19 Mar 2015 04:31:23 +0000
Received: from BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) by BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) with mapi id 15.01.0112.000; Thu, 19 Mar 2015 04:31:23 +0000
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, "lucid@ietf.org" <lucid@ietf.org>
Thread-Topic: [Lucid] FW: [mark@macchiato.com: Re: Non-normalizable diacritics - new property]
Thread-Index: AQHQYeWvrIxB8XNhl06inScNBJS0IJ0jC27ggAAKHACAAB/PsA==
Date: Thu, 19 Mar 2015 04:31:23 +0000
Message-ID: <BLUPR03MB137886903F15000BB01E3F5882010@BLUPR03MB1378.namprd03.prod.outlook.com>
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> <20150319023029.GA6046@mx1.yitter.info>
In-Reply-To: <20150319023029.GA6046@mx1.yitter.info>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [50.34.94.236]
authentication-results: anvilwalrusden.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR03MB1377;
x-microsoft-antispam-prvs: <BLUPR03MB1377EB4CABA3B0A209BC3F4982010@BLUPR03MB1377.namprd03.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(51704005)(76576001)(99286002)(77156002)(102836002)(62966003)(106116001)(40100003)(86362001)(74316001)(2656002)(87936001)(2501003)(107886001)(54356999)(50986999)(122556002)(2950100001)(92566002)(66066001)(2900100001)(46102003)(33656002)(220923002)(222073002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR03MB1377; H:BLUPR03MB1378.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:BLUPR03MB1377; BCL:0; PCL:0; RULEID:;  SRVR:BLUPR03MB1377; 
x-forefront-prvs: 052017CAF1
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Mar 2015 04:31:23.3975 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB1377
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/uwRID9K3_tofOjNXhvbQthmgsRk>
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 04:31:43 -0000

> > 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 mat=
ch probability the identifiers aren't stable.  So when they're handed aroun=
d through different environments, stuff happens that is bad.

I said "to the machine".  They're "just numbers", and the NFC/NFKC rules ar=
e mathematical.  Yes, you do have to exclude unassigned code points as thos=
e don't have defined behavior, however "Assigned NFC or NFKC for defined co=
de points" would be 100% unique to the machine.

>  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'm not trying to go from "this can't be perfect" to "we shouldn't try".  I=
 am trying to say that this is good enough.  The additional cost of trying =
doesn't add value.  =20

> > 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.

IDN is sociological exercise.  If the need was purely scientific/mathematic=
al, then we'd only need a bunch of numbers or opaque IDs.  In order to make=
 much progress here I think we need to think about how people use them.

-Shawn


From nobody Thu Mar 19 01:07:44 2015
Return-Path: <john-ietf@jck.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 53ED21A1B57 for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 01:07:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.61
X-Spam-Level: 
X-Spam-Status: No, score=-4.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 eVidwkYAgkVz for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 01:07:36 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC3EF1A6EF1 for <lucid@ietf.org>; Thu, 19 Mar 2015 01:07:36 -0700 (PDT)
Received: from [198.252.137.35] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1YYVU8-000NpR-RU; Thu, 19 Mar 2015 04:07:20 -0400
Date: Thu, 19 Mar 2015 04:07:15 -0400
From: John C Klensin <john-ietf@jck.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>
Message-ID: <A62526FD387D08270363E96E@JcK-HP8200.jck.com>
In-Reply-To: <BLUPR03MB137886903F15000BB01E3F5882010@BLUPR03MB1378.namprd03.prod.outlook.com>
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.namprd0 3.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> <20150319023029.GA6046@mx1.yitter.info> <BLUPR03MB137886903F15000BB01E3F5882010@BLUPR03MB1378.namprd03.prod.outlook.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.35
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/zQypaW7l3D-TH4mz-393WTucPeU>
Cc: lucid@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
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 08:07:42 -0000

--On Thursday, March 19, 2015 04:31 +0000 Shawn Steele
<Shawn.Steele@microsoft.com> wrote:

>> > No, even all NFC or NFKC would be 100% unique to the =
machine
>=20
>> 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.
>=20
> I said "to the machine".  They're "just numbers", and the
> NFC/NFKC rules are mathematical.  Yes, you do have to exclude
> unassigned code points as those don't have defined behavior,
> however "Assigned NFC or NFKC for defined code points" would
> be 100% unique to the machine.

Shawn,

A few observations, although we may need to agree to disagree.

First, saying "NFC/NFKC rules" tends to obscure the issue here.
An important property of NFC/NFD is reversibility, i.e., a dual
relationship in the mathematical sense.  You may not be able to
recover whatever the original way, but you can go back and forth
between the two normalized forms without loss of information.
By contrast, NFKC (and NFKD) are potentially information-losing
and that is (although more of some sets of compatibility
equivalences than others) significant.

>...
> I'm not trying to go from "this can't be perfect" to "we
> shouldn't try".  I am trying to say that this is good enough.
> The additional cost of trying doesn't add value.  =20

Sorry.  I think you can argue that it doesn't add enough value
to be worth the trouble.  I disagree with that given an
appropriate definition of the problem and believe we don't agree
on that definition.   But "doesn't add value"... well, we
disagree.

>...
>> 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.
>=20
> IDN is sociological exercise.  If the need was purely
> scientific/mathematical, then we'd only need a bunch of
> numbers or opaque IDs.  In order to make much progress here I
> think we need to think about how people use them.

At one level, I agree about "sociological exercise".  I would
normally characterize it a bit differently, but let's accept
that for the purposes of this note.  I would say much the same
thing, not just about IDNs, but about almost any human-readable
identifier, noting that, as soon as a "bunch of numbers" is
expressed as numerals in written forms, there are "sociological"
issues of number base and the set of numerals to be used (in
Unicode-land and modern writing systems bound to script for
everything but Arabic). =20

However, maybe there is a different way to characterize this
issue that avoids the sociological exercise.  I continue to
accept that, at least in general, Unicode has a reasonable set
of coding principles and that, in general, a reasonable set of
decisions has been made given those principles.  I firmly
believe that a different coding system, with different
principles (or priorities among principles) would simply trade
one set of issues for another but might otherwise be equally
"good".  However, many of those decisions -- about coding, not
about characters -- do have alternatives.  For example, instead
of coding lower and upper case characters differently, one could
have dealt with case distinctions by assigning a single code
point to the case-insensitive abstract character and then using
a qualifier to designate case (either always for one case or
when anyone cared for both -- two different coding style
distinctions).  Similarly, ZWJ and ZWNJ are, in some sense,
indicators and artifacts of coding decisions, not "characters":
one could have avoiding them by assigning separate code points
to the characters they affect on rendering (note that there have
been passionate arguments that just that should have been done
with some Indic scripts). =20

In a way, decisions about script boundaries are, themselves,
coding decisions rather than inherent character properties but,
having been vaguely involved with an attempt to define a
universal character set that did not depend on such boundaries,
that path seems to lead to madness.  Unicode still could have
defined its script boundaries differently, e.g., seeking a
higher level of integration (or "unification") across the board
but, while I think understand that as a choice is helpful,
pursuing it very far probably is not.

Modulo the script boundary issue, it is (approximately) possible
to see all of the "confusion" and "too-similar appearance"
problems as human perception issues involving the
recipient/viewer (not really "sociological", but the distinction
may not be important).   Seen that way, the issue here is not
about the viewer perception issue but about the coding one --
resolving differences in decisions about how something might
have been code (again and for convenience, within a script).  If
one goes back a few hundred years, the question might become,
not whether someone viewing the character would "see" the
difference but whether the calligrapher or perhaps even someone
trying to set a string in cold type would see an important
difference -- also, in a way, a coding decision problem.

Coming back to the issue that started this, had Unicode
(followed by the IETF) not deprecated embedded code points to
identify languages, U+08A1 could have been coded (using an odd
notation whose intent should be obvious) as=20
    <lang:fula>U+0628 U+0654</lang>
without loss of any phonetic or semantic information and the
justification for adding the code point at all would disappear
(at least absent what we generically describe as "politics", in
which case the justification for its not decomposing would
disappear).

Similarly, a different CCS could have avoided at least the
portion of the "Mathematical" collection that are ultimately
Latin or Greek letters in special fonts by different coding
conventions that would use the base character plus qualifiers
for usage and/or type style.

Another example lies in the collection of combining characters
that can be used to for precomposed character that don't
decompose, not for, e.g., phonetic reasons but because the
definitions of those combining characters don't contain quite
enough information (see Section 3.3.2.3 of
draft-klensin-idna-5892upd-unicode70-04.txt and its citations).
At least in theory, Unicode could have chosen to assign code
points to more precisely-defined (as to how they affect base
characters) combining characters.  A coding system with
different principles might have used position and/or size
indicator coding with similar effect (an approach that will
probably be needed if Unicode ever takes on, e.g., Classic Mayan
script).

Now, from that perspective, this issue is about smoothing over
(by either some form of equivalence rules or exclusion (or
non-inclusion)) differences among character code sequences that
are the result of coding decisions (decisions that are at least
semi-arbitrary because others could have been made with no
"important" information loss -- and, yes, "important" is
sometimes debatable without yet other coding decisions).  For
sequences that compose and decompose symmetrically, NFC (or NFD)
normalization does the necessary job.  IDNA2008 disallows those
mathematical characters as a way to do a different part of the
job without making non-reversible compatibility equivalences
part of the standard.

As another coding decision matter, all of this would be
significantly easier were Unicode consistent about its coding
distinctions.   Such consistency is likely impossible, at least
given other decisions, but that doesn't mean it wouldn't be
helpful.   However, we have, instead, a combining sequence
preference (with exceptions) for Latin but a precomposed
character preference for Arabic.  We have all precombined Latin
characters where combining sequences decomposing, except for
some combining characters.  Most European scripts code the
abstract graphics in grapheme clusters but East and South Asian
ones use indicators like ZWJ and ZWNJ.  There is a strict rule
against assigning separate code points to typestyle distinctions
but an exception for some usage contexts such as mathematics and
phonetic description.  Unicode does not have indicator codes or
separate code points for layout or presentation (leaving that to
external markup), but such coding has proved necessary for
writing systems that are primarily right-to-left and in such
cases as non-breaking space.  There are no language-dependent or
pronunciation-dependent coding distinctions (see Section 2 of
draft-klensin-idna-5892upd-unicode70-04.txt and/or Chapter 2 of
Uniocde 7.0) except where there are.=20

Again, I don't think any of those decisions are "wrong".  But
they are all problematic for the IETF's language-insensitive,
fairly context-free, identifier comparison purposes.  And they
are, at least IMO, worth some effort because (again, independent
of discussions about "confusion"), at least,

(i) We have already established the precedent of dealing with
all of the important groups of coding artifacts we knew about
when IDNA2008 was under consideration by adopting normalization
rules, DISALLOWing a lot of characters, and even developing
special context-dependent rules for some of them.

(ii) When different input methods, using data entry devices that
are indistinguishable to the user (e.g., the alphabetic key
layouts on a German keyboard for Windows, Linux, and the Mac are
the same) and will produce different output (stored) strings for
the same input, we are dealing with coding artifacts, not
"visual confusion".   Whether the difference in internal coding
is the decision of one system to prefer NFC and that of another
to prefer NFD or the result of one typist using an "=C3=B6" key =
and
another deciding to type an "o" and a "dead key" umlaut, we have
(and IMO, should have) comparison systems that eliminate those
coding differences.    This is, from that point of view, just a
new set of coding decision differences that neither Unicode nor
we arranged to compensate for earlier.

     john



One way to look at the issue involved here 


From nobody Thu Mar 19 01:48:09 2015
Return-Path: <john-ietf@jck.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 2F3941A026C for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 01:48:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.61
X-Spam-Level: 
X-Spam-Status: No, score=-4.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 eLIGbU9hwGbD for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 01:48:06 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 747AC1A8966 for <lucid@ietf.org>; Thu, 19 Mar 2015 01:48:06 -0700 (PDT)
Received: from [198.252.137.35] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1YYW7X-000NwZ-QQ; Thu, 19 Mar 2015 04:48:03 -0400
Date: Thu, 19 Mar 2015 04:47:58 -0400
From: John C Klensin <john-ietf@jck.com>
To: Asmus Freytag <asmusf@ix.netcom.com>, lucid@ietf.org
Message-ID: <C884797C1998868E85D84343@JcK-HP8200.jck.com>
In-Reply-To: <550A4EC6.3090203@ix.netcom.com>
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.namprd0 3.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> <20150319023029.GA6046@mx1.yitter.info> <550A4EC6.3090203@ix.netcom.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.35
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/tz_xzvBCy3o_2foj-NPmHe7LbZU>
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 08:48:08 -0000

--On Wednesday, March 18, 2015 21:21 -0700 Asmus Freytag
<asmusf@ix.netcom.com> wrote:

> As  a btw:
> 
> I'm amazed at the near total lack of IDNs registered for the
> Latin script in the root. It seems that people like the
> "fall-back" nature of non-accented ASCII labels for anything
> that should be accessed universally (top level).
> 
> So, for that script at least, you could say that users don't
> like being surprised by a more linguistically accurate, but
> less universally accessible way of constructing identifiers.
> 
> Interesting....

Or it is a policy artifact.

Suppose I have a language (not, not just script) with
well-defined and often-used conventions for representing
characters in, e.g., a simplified or less decorated form.  I'm
almost certainly going to want that form in the DNS (not just
the root, but at other levels as well).  That is especially
likely to be true if people have been using those simplified
forms in the DNS for 20 or 25 years (as is the case for most
European use of Latin Script) so that "often-used" including
users getting used to those forms in Internet contexts.

Now we introduce IDNs, making "linguistically accurate" forms
possible.  In at least some domains, those IDN forms are
registered alongside the simplified (for Latin script, ASCII)
ones, either as privileged "variants" or because registration of
both forms separately is cheap, certain, and efficient.

Then ICANN come along with IDN rules for the root.   For, e.g.,
Chinese, delegation of both the Simplified and more decorated
Traditional form is straightforward and the marginal cost of
doing so (in dollars and/or aggravation) is almost zero.  For
Latin script, a decision was made (at least at one point) to ban
variants in the root, so the only way to get both the simplified
(i.e., ASCII) form and the decorated (and more correct) one
costs USD 168K in fees, plus whatever it costs to prepare the
application, plus an aggravating review process, plus the
possibility that some committee, process, or bureaucrat will
decide that the decorated form is confusingly similar to the
simplified one and reject the application causing that (probably
USD 200K plus) investment to disappear with no benefits to the
applicant.

The situation might be quite accidentally reinforced by the
observation that acronyms and abbreviations are much more common
and accepted (and likely to end up in the DNS) in many languages
that use Latin script than with some other languages.
Especially for the large subset of those languages for which
typical strings are mostly ASCII with a few "decorated" letters,
those abbreviations or acronyms are reasonably likely to be
ASCII in "linguistically accurate" form.

Under those conditions, would you expect a lot of Latin script,
"linguistically accurate", registrations?

It would be an interesting experiment to ask Latin script
registrants whose own languages make significant use of
non-ASCII characters or those whose chosen labels are an ACII
adaptation whether, if they were offered the option of
registering a "linguistically accurate" form at little or no
charge (and after a simple application) whether or not they
would do so.   Absent that experiment or something equivalent, I
think it is hard to infer anything reliably from your
observation about the number of such strings now registered.

best,
    john




From nobody Thu Mar 19 03:21:06 2015
Return-Path: <Shawn.Steele@microsoft.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 395691A897B for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 03:21:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 fqHzj-9wFbiW for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 03:21:04 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0769.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:769]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8A371A897A for <lucid@ietf.org>; Thu, 19 Mar 2015 03:21:03 -0700 (PDT)
Received: from BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) by BLUPR03MB1379.namprd03.prod.outlook.com (25.163.81.13) with Microsoft SMTP Server (TLS) id 15.1.118.21; Thu, 19 Mar 2015 10:20:45 +0000
Received: from BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) by BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) with mapi id 15.01.0112.000; Thu, 19 Mar 2015 10:20:45 +0000
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: John C Klensin <john-ietf@jck.com>
Thread-Topic: [Lucid] FW: [mark@macchiato.com: Re: Non-normalizable diacritics - new property]
Thread-Index: AQHQYeWvrIxB8XNhl06inScNBJS0IJ0jC27ggAAKHACAAB/PsIAAPkeAgAAdDOA=
Date: Thu, 19 Mar 2015 10:20:44 +0000
Message-ID: <BLUPR03MB137839811770E882A0EDA60C82010@BLUPR03MB1378.namprd03.prod.outlook.com>
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.namprd0 3.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> <20150319023029.GA6046@mx1.yitter.info> <BLUPR03MB137886903F15000BB01E3F5882010@BLUPR03MB1378.namprd03.prod.outlook.com> <A62526FD387D08270363E96E@JcK-HP8200.jck.com>
In-Reply-To: <A62526FD387D08270363E96E@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [50.34.94.236]
authentication-results: jck.com; dkim=none (message not signed) header.d=none; 
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR03MB1379;
x-microsoft-antispam-prvs: <BLUPR03MB13798D52DB9C1E3B16CBC93382010@BLUPR03MB1379.namprd03.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(62966003)(76576001)(77156002)(33656002)(76176999)(50986999)(54356999)(102836002)(2950100001)(2900100001)(66066001)(99286002)(86362001)(93886004)(46102003)(40100003)(122556002)(110136001)(106116001)(92566002)(74316001)(87936001)(2656002)(220923002)(222073002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR03MB1379; H:BLUPR03MB1378.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:BLUPR03MB1379; BCL:0; PCL:0; RULEID:;  SRVR:BLUPR03MB1379; 
x-forefront-prvs: 052017CAF1
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Mar 2015 10:20:44.3150 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB1379
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/Tb_iuNQFEmfjciHZomqSTBXPdqc>
Cc: "lucid@ietf.org" <lucid@ietf.org>, Andrew Sullivan <ajs@anvilwalrusden.com>
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 10:21:06 -0000

PiBGaXJzdCwgc2F5aW5nICJORkMvTkZLQyBydWxlcyIgdGVuZHMgdG8gb2JzY3VyZSB0aGUgaXNz
dWUgaGVyZS4NCg0KPiBBbiBpbXBvcnRhbnQgcHJvcGVydHkgb2YgTkZDL05GRCBpcyByZXZlcnNp
YmlsaXR5LCBpLmUuLCBhIGR1YWwgcmVsYXRpb25zaGlwIGluIHRoZSBtYXRoZW1hdGljYWwgc2Vu
c2UuLi4uDQoNCkkgd2FzIHRyeWluZyB0byBtYWtlIGFuIGV4YW1wbGUuDQoNClByZXN1bWluZyBJ
IGNyZWF0ZWQgYSBzeXN0ZW0gd2hlcmUgSSBtYXBwZWQgQS1DIHRvICIxIiBhbmQgRC1HIHRvICIy
IiBhbmQgRi1QIHRvICIzIiBhbmQgUy1aIHRvICI0IiwgdGhlbiBJIGNvdWxkIHN0aWxsIGhhdmUg
YSBzeXN0ZW0gdGhhdCBwcm92aWRlZCBtYWNoaW5lIHJlYWRhYmxlIHVuaXF1ZSBpZGVudGlmaWVy
cy4gIFRoZXJlJ3MgYmUgbW9yZSB0aGFuIG9uZSB3YXkgdG8gd3JpdGUgdGhlbSwgYnV0IHRoZSBt
ZWNoYW5pc20gaXMgY29tcGxldGVseSB1bmFtYmlndW91cy4gIExhdGVyIGlmIEkgZGVjaWRlZCB0
byBtYXAgIUAjJCVeIHRvICI1IiBhbmQgJiooKV8rIHRvICI2IiwgSSdkIGhhdmUgbW9yZSBpZGVu
dGlmaWVycywgYnV0IHRoZXknZCBzdGlsbCBiZSB1bmlxdWUgdG8gdGhlIG1hY2hpbmUuDQoNCldl
IGhhdmUgYSBmdW5jdGlvbiB3aGVyZSBmKGlucHV0KSA9IFguICBFdmVyeSBpbnB1dCB3aWxsIHJl
cGVhdGVkbHkgYW5kIHBlcmZlY3RseSByZXN1bHQgaW4gdGhlIHNhbWUgWC4gIFRoZSBzZXQgb2Yg
dmFsdWVzIHRoYXQgWCBtYXkgY29udGFpbiBtYXkgY2hhbmdlIG92ZXIgdGltZSBhcyBtb3JlIGlu
cHV0cyBhcmUgcGVybWl0dGVkLCBob3dldmVyIGV2ZXJ5IGlucHV0IHdpbGwgY29udGludWUgdG8g
YmUgdHJhbnNmb3JtZWQgYnkgdGhpcyBmdW5jdGlvbiBpbnRvIHRoZSBzYW1lIFguICAoRXhjZXB0
IGZvciB0aGUgY2hhbmdlIGZyb20gSUROQSAyMDAzIHRvIElETkEgMjAwOCwgd2hpY2ggYnJva2Ug
dGhpcyBzdGFiaWxpdHksIGJ1dCBJJ20gaG9waW5nIHdlIGRvbid0IGRvIHRoYXQgYWdhaW4pLg0K
DQpTbyB3ZSBhbHJlYWR5IGhhdmUgbWF0aGVtYXRpY2FsbHkgdW5hbWJpZ3VvdXMgaWRlbnRpZmll
cnMgLSB3aXRoaW4gdGhlIHN5c3RlbSB0aGF0IHRoZSBtYWNoaW5lIHVzZXMuDQoNCj4gU29ycnku
ICBJIHRoaW5rIHlvdSBjYW4gYXJndWUgdGhhdCBpdCBkb2Vzbid0IGFkZCBlbm91Z2ggdmFsdWUg
dG8gYmUgd29ydGggdGhlIHRyb3VibGUuICBJIGRpc2FncmVlIHdpdGggdGhhdCBnaXZlbiBhbiBh
cHByb3ByaWF0ZSBkZWZpbml0aW9uIG9mIHRoZSBwcm9ibGVtIGFuZCBiZWxpZXZlIHdlIGRvbid0
IGFncmVlDQo+IG9uIHRoYXQgZGVmaW5pdGlvbi4gICBCdXQgImRvZXNuJ3QgYWRkIHZhbHVlIi4u
LiB3ZWxsLCB3ZSBkaXNhZ3JlZS4NCg0KRGlzYWdyZWVpbmcgaXMgT0sgOikNCg0KTWF0aGVtYXRp
Y2FsbHksIHdlIGhhdmUgdW5pcXVlIGlkZW50aWZpZXJzLiAgVGhlIHByb2JsZW0gaXMgY3JlYXRl
ZCB3aGVuIHdlIGludHJvZHVjZSB0aGUgaHVtYW4uDQoNCj4gSG93ZXZlciwgbWFueSBvZiB0aG9z
ZSBkZWNpc2lvbnMgLS0gYWJvdXQgY29kaW5nLCBub3QgYWJvdXQgY2hhcmFjdGVycyAtLSBkbyBo
YXZlIGFsdGVybmF0aXZlcy4NCg0KWXVwLCBtYW55IG9mIHRob3NlIHdlcmUgYXR0ZW1wdGVkIGlu
IGNvZGUgcGFnZXMuICBPZnRlbiB3aXRoIHNpZGUgZWZmZWN0cyB0aGF0IHdlcmUgbm90IHZlcnkg
bmljZSBpbiBoaW5kc2lnaHQuDQoNCj4gICJVbmljb2RlIGNvdWxkIGhhdmUgYmVlbiBkZXNpZ25l
ZCBkaWZmZXJlbnRseSIgKHBhcmFwaHJhc2luZykuDQoNCkkgc3Ryb25nbHkgc3VnZ2VzdCB0aGF0
IGlmIHlvdSBhcmUgcGFzc2lvbmF0ZSBhYm91dCBob3cgY2hhcmFjdGVycyBhcmUgZW5jb2RlZCwg
YW5kIGZlZWwgdGhhdCB5b3UgY291bGQgaGVscCBlbmNvZGUgbmV3IGNoYXJhY3RlcnMgYmV0dGVy
LCB0aGF0IHlvdSBwYXJ0aWNpcGF0ZSBpbiBVbmljb2RlLiAgSSBkb24ndCBwcmV0ZW5kIHRvIGtu
b3cgZXZlcnl0aGluZyBhYm91dCBVbmljb2RlLCBidXQgSSBmZWFyIHlvdSdyZSBzZXJpb3VzbHkg
b3ZlcnNpbXBsaWZ5aW5nIHRoZSBjb21wbGV4aXR5IG9mIHRoZSBwcm9ibGVtLiAgVGhlcmUgYXJl
IHJlYXNvbnMsIHNvbWUgZ29vZCwgc29tZSBiYWQsIGZvciB3aHkgc3R1ZmYgaXMgdGhlIHdheSBp
dCBpcyBVbmljb2RlLiAgSSBkb24ndCB0aGluayB0aGF0IHRoZSBJRVRGIHNob3VsZCBiZSBpbiB0
aGUgYnVzaW5lc3Mgb2YgZml4aW5nIG9yIHNlY29uZCBndWVzc2luZyBVbmljb2RlLiAgSWYgcGVv
cGxlIHdhbnQgYSBiZXR0ZXIgVW5pY29kZSwgdGhlbiBwYXJ0aWNpcGF0ZS4NCg0KPiBBZ2Fpbiwg
SSBkb24ndCB0aGluayBhbnkgb2YgdGhvc2UgZGVjaXNpb25zIGFyZSAid3JvbmciLiAgQnV0IHRo
ZXkgYXJlIGFsbCBwcm9ibGVtYXRpYyBmb3IgdGhlIElFVEYncyBsYW5ndWFnZS1pbnNlbnNpdGl2
ZSwgZmFpcmx5IGNvbnRleHQtZnJlZSwgaWRlbnRpZmllciBjb21wYXJpc29uIHB1cnBvc2VzLiAg
QW5kIHRoZXkgYXJlLCBhdCBsZWFzdCBJTU8sIHdvcnRoIHNvbWUgZWZmb3J0IGJlY2F1c2UgKGFn
YWluLCBpbmRlcGVuZGVudCBvZiBkaXNjdXNzaW9ucyBhYm91dCAiY29uZnVzaW9uIiksIGF0IGxl
YXN0LA0KDQpJdCdzIG9ubHkgcHJvYmxlbWF0aWMgb25jZSB5b3UgYXNrIGEgaHVtYW4gdG8gaW50
ZXJwcmV0L3RyYW5zY3JpYmUvcmVhZCB0aGUgaWRlbnRpZmllci4gIFRoZXJlJ3Mgbm8gYW1iaWd1
aXR5IGF0IHRoZSBtYWNoaW5lIGxldmVsLg0KDQo+IChpaSkgV2hlbiBkaWZmZXJlbnQgaW5wdXQg
bWV0aG9kcywgdXNpbmcgZGF0YSBlbnRyeSBkZXZpY2VzIHRoYXQgYXJlIGluZGlzdGluZ3Vpc2hh
YmxlIHRvIHRoZSB1c2VyIChlLmcuLCB0aGUgYWxwaGFiZXRpYyBrZXkgbGF5b3V0cyBvbiBhIEdl
cm1hbiBrZXlib2FyZCBmb3IgV2luZG93cywgTGludXgsIGFuZCB0aGUgTWFjIGFyZSB0aGUgc2Ft
ZSkgYW5kIHdpbGwgcHJvZHVjZSBkaWZmZXJlbnQgb3V0cHV0IChzdG9yZWQpIHN0cmluZ3MgZm9y
IHRoZSBzYW1lIGlucHV0LCB3ZSBhcmUgZGVhbGluZyB3aXRoIGNvZGluZyBhcnRpZmFjdHMsIG5v
dA0KInZpc3VhbCBjb25mdXNpb24iLiAgIFdoZXRoZXIgdGhlIGRpZmZlcmVuY2UgaW4gaW50ZXJu
YWwgY29kaW5nDQppcyB0aGUgZGVjaXNpb24gb2Ygb25lIHN5c3RlbSB0byBwcmVmZXIgTkZDIGFu
ZCB0aGF0IG9mIGFub3RoZXIgdG8gcHJlZmVyIE5GRCBvciB0aGUgcmVzdWx0IG9mIG9uZSB0eXBp
c3QgdXNpbmcgYW4gIsO2IiBrZXkgYW5kIGFub3RoZXIgZGVjaWRpbmcgdG8gdHlwZSBhbiAibyIg
YW5kIGEgImRlYWQga2V5IiB1bWxhdXQsIHdlIGhhdmUgKGFuZCBJTU8sIHNob3VsZCBoYXZlKSBj
b21wYXJpc29uIHN5c3RlbXMgdGhhdCBlbGltaW5hdGUgdGhvc2UNCmNvZGluZyBkaWZmZXJlbmNl
cy4gICAgVGhpcyBpcywgZnJvbSB0aGF0IHBvaW50IG9mIHZpZXcsIGp1c3QgYQ0KbmV3IHNldCBv
ZiBjb2RpbmcgZGVjaXNpb24gZGlmZmVyZW5jZXMgdGhhdCBuZWl0aGVyIFVuaWNvZGUgbm9yIHdl
IGFycmFuZ2VkIHRvIGNvbXBlbnNhdGUgZm9yIGVhcmxpZXIuDQoNClRoYXQncyBoYW5kbGVkIGlu
IElETkEgYnkgdXNpbmcgTkZLQy4gIEkgaGF2ZW4ndCBoZWFyZCB0aGF0IHRoZXJlIGlzIGFueSBw
cm9ibGVtIHdpdGggdXNpbmcgSU5EQSBmb3IgaWRlbnRpZmllcnMgZHVlIHRvIHVzaW5nIMO2IG9y
IG8gKyB1bWxhdXQgdG8gcmVwcmVzZW50IEdlcm1hbi4NCg0KQUZBSUsgaWYgdGhlIGh1bWFuIGVu
dGVycyB0aGUgY29ycmVjdCBjaGFyYWN0ZXJzIHVzaW5nIHRoZWlyIGtleWJvYXJkIGluIGEgbm9y
bWFsIGZhc2hpb24sIHVzaW5nIHRoZSBjb3JyZWN0IHNjcmlwdCBmb3IgdGhlaXIgbGFuZ3VhZ2Us
IGFuZCBiYXJyaW5nIGFueSB0cmFuc2NyaXB0aW9uIGVycm9ycywgdHlwb3Mgb3IgaG9tb2dyYXBo
IGNvbmZ1c2lvbiwgSUROQSB3aWxsIGNvbnNpc3RlbnRseSBwb2ludCB0byB0aGUgc2FtZSByZWNv
cmQgcmVnYXJkbGVzcyBvZiB0aGUgaW5wdXQgbWV0aG9kLiAgSSBkb24ndCByZWNhbGwgYW55IGV4
YW1wbGVzIHdoZXJlIHVzZSBvZiBhbiBhcHByb3ByaWF0ZSBpbnB1dCBtZXRob2Qva2V5Ym9hcmQg
d291bGQgbGVhZCB0byBhbWJpZ3VvdXMgaWRlbnRpZmllcnMuICANCg0KLVNoYXduDQoNCg==


From nobody Thu Mar 19 03:26:58 2015
Return-Path: <Shawn.Steele@microsoft.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 AA73C1A893A for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 03:26:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.902
X-Spam-Level: 
X-Spam-Status: No, score=-3.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 pMSH57UpMDSA for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 03:26:54 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0792.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:792]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A8921A0161 for <lucid@ietf.org>; Thu, 19 Mar 2015 03:26:54 -0700 (PDT)
Received: from BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) by BLUPR03MB214.namprd03.prod.outlook.com (10.255.212.151) with Microsoft SMTP Server (TLS) id 15.1.118.15; Thu, 19 Mar 2015 10:26:34 +0000
Received: from BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) by BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) with Microsoft SMTP Server (TLS) id 15.1.112.19; Thu, 19 Mar 2015 10:26:33 +0000
Received: from BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) by BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) with mapi id 15.01.0112.000; Thu, 19 Mar 2015 10:26:33 +0000
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: John C Klensin <john-ietf@jck.com>, Asmus Freytag <asmusf@ix.netcom.com>,  "lucid@ietf.org" <lucid@ietf.org>
Thread-Topic: [Lucid] FW: [mark@macchiato.com: Re: Non-normalizable diacritics - new property]
Thread-Index: AQHQYeWvrIxB8XNhl06inScNBJS0IJ0jC27ggAAKHACAAB7+AIAASngAgAAaawA=
Date: Thu, 19 Mar 2015 10:26:32 +0000
Message-ID: <BLUPR03MB1378E8DC91D298DB612C678582010@BLUPR03MB1378.namprd03.prod.outlook.com>
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.namprd0 3.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> <20150319023029.GA6046@mx1.yitter.info> <550A4EC6.3090203@ix.netcom.com> <C884797C1998868E85D84343@JcK-HP8200.jck.com>
In-Reply-To: <C884797C1998868E85D84343@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [50.34.94.236]
authentication-results: jck.com; dkim=none (message not signed) header.d=none; 
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:; SRVR:BLUPR03MB1378; UriScan:; BCL:0; PCL:0; RULEID:; SRVR:BLUPR03MB214; 
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(377454003)(24454002)(51704005)(33656002)(66066001)(15975445007)(102836002)(40100003)(122556002)(74316001)(76176999)(54356999)(50986999)(76576001)(2656002)(87936001)(107886001)(106116001)(19580405001)(19580395003)(86362001)(92566002)(2950100001)(2900100001)(93886004)(77156002)(62966003)(46102003)(2501003)(99286002)(7059030)(222073002)(220923002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR03MB1378; H:BLUPR03MB1378.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-microsoft-antispam-prvs: <BLUPR03MB13785FA5A91B6177C09251D182010@BLUPR03MB1378.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:BLUPR03MB1378; BCL:0; PCL:0; RULEID:;  SRVR:BLUPR03MB1378; 
x-forefront-prvs: 052017CAF1
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Mar 2015 10:26:32.9347 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB1378
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/TiltN_DgpHMx8h0eF5P22gzyhKk>
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 10:26:56 -0000

I agree with John on this one... there's a lot of momentum behind Latin, ID=
N is really new, and there are still systems that don't handle it (so I "ne=
ed" to have a pure ASCII name anyway).  Businesses could register alternate=
s, but I'm always amazed at the simple ASCII-only variations that they don'=
t bother to register/protect/claim.

I think it'll take the non-Latin scripts really taking off to kick Latin in=
to gear.  The other scripts have a much bigger incentive to make sure their=
 systems work with IDN.  They'll drag the Latin crowd along, but it's going=
 to take a bit.

-Shawn

-----Original Message-----
From: Lucid [mailto:lucid-bounces@ietf.org] On Behalf Of John C Klensin
Sent: Thursday, March 19, 2015 1:48 AM
To: Asmus Freytag; lucid@ietf.org
Subject: Re: [Lucid] FW: [mark@macchiato.com: Re: Non-normalizable diacriti=
cs - new property]



--On Wednesday, March 18, 2015 21:21 -0700 Asmus Freytag <asmusf@ix.netcom.=
com> wrote:

> As  a btw:
>=20
> I'm amazed at the near total lack of IDNs registered for the Latin=20
> script in the root. It seems that people like the "fall-back" nature=20
> of non-accented ASCII labels for anything that should be accessed=20
> universally (top level).
>=20
> So, for that script at least, you could say that users don't like=20
> being surprised by a more linguistically accurate, but less=20
> universally accessible way of constructing identifiers.
>=20
> Interesting....

Or it is a policy artifact.

Suppose I have a language (not, not just script) with well-defined and ofte=
n-used conventions for representing characters in, e.g., a simplified or le=
ss decorated form.  I'm almost certainly going to want that form in the DNS=
 (not just the root, but at other levels as well).  That is especially like=
ly to be true if people have been using those simplified forms in the DNS f=
or 20 or 25 years (as is the case for most European use of Latin Script) so=
 that "often-used" including users getting used to those forms in Internet =
contexts.

Now we introduce IDNs, making "linguistically accurate" forms possible.  In=
 at least some domains, those IDN forms are registered alongside the simpli=
fied (for Latin script, ASCII) ones, either as privileged "variants" or bec=
ause registration of both forms separately is cheap, certain, and efficient=
.

Then ICANN come along with IDN rules for the root.   For, e.g.,
Chinese, delegation of both the Simplified and more decorated Traditional f=
orm is straightforward and the marginal cost of doing so (in dollars and/or=
 aggravation) is almost zero.  For Latin script, a decision was made (at le=
ast at one point) to ban variants in the root, so the only way to get both =
the simplified (i.e., ASCII) form and the decorated (and more correct) one =
costs USD 168K in fees, plus whatever it costs to prepare the application, =
plus an aggravating review process, plus the possibility that some committe=
e, process, or bureaucrat will decide that the decorated form is confusingl=
y similar to the simplified one and reject the application causing that (pr=
obably USD 200K plus) investment to disappear with no benefits to the appli=
cant.

The situation might be quite accidentally reinforced by the observation tha=
t acronyms and abbreviations are much more common and accepted (and likely =
to end up in the DNS) in many languages that use Latin script than with som=
e other languages.
Especially for the large subset of those languages for which typical string=
s are mostly ASCII with a few "decorated" letters, those abbreviations or a=
cronyms are reasonably likely to be ASCII in "linguistically accurate" form=
.

Under those conditions, would you expect a lot of Latin script, "linguistic=
ally accurate", registrations?

It would be an interesting experiment to ask Latin script registrants whose=
 own languages make significant use of non-ASCII characters or those whose =
chosen labels are an ACII adaptation whether, if they were offered the opti=
on of registering a "linguistically accurate" form at little or no charge (=
and after a simple application) whether or not they
would do so.   Absent that experiment or something equivalent, I
think it is hard to infer anything reliably from your observation about the=
 number of such strings now registered.

best,
    john



_______________________________________________
Lucid mailing list
Lucid@ietf.org
https://www.ietf.org/mailman/listinfo/lucid


From nobody Thu Mar 19 10:50:46 2015
Return-Path: <asmusf@ix.netcom.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 D12591A8885 for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 10:50:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4
X-Spam-Level: 
X-Spam-Status: No, score=-4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_LETTER=-2, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 DXUxWj6utwne for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 10:50:41 -0700 (PDT)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by ietfa.amsl.com (Postfix) with ESMTP id C58091A874C for <lucid@ietf.org>; Thu, 19 Mar 2015 10:50:40 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=RGLbyBk38Az0JhFiYpz0fE49z7QmdjjH+7qKGJtdK97ip0Y0AKXoEd51lJsTFRuE; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [72.244.206.133] (helo=[192.168.0.107]) by elasmtp-junco.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <asmusf@ix.netcom.com>) id 1YYeac-0001CR-B2; Thu, 19 Mar 2015 12:50:39 -0500
Message-ID: <550B0C70.7030003@ix.netcom.com>
Date: Thu, 19 Mar 2015 10:50:40 -0700
From: Asmus Freytag <asmusf@ix.netcom.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: lucid@ietf.org
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.namprd0 3.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> <20150319023029.GA6046@mx1.yitter.info> <BLUPR03MB137886903F15000BB01E3F5882010@BLUPR03MB1378.namprd03.prod.outlook.com> <A62526FD387D08270363E96E@JcK-HP8200.jck.com>
In-Reply-To: <A62526FD387D08270363E96E@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2b65b6112f89115373fcf221f6c58394fdb10b840b3f82fbe350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 72.244.206.133
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/9mOFg4fso0p7cRSpbMhCWUDZp3U>
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>
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 17:50:45 -0000

On 3/19/2015 1:07 AM, John C Klensin wrote:
>
> --On Thursday, March 19, 2015 04:31 +0000 Shawn Steele
> <Shawn.Steele@microsoft.com> wrote:
>
>>>> 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.
>> I said "to the machine".  They're "just numbers", and the
>> NFC/NFKC rules are mathematical.  Yes, you do have to exclude
>> unassigned code points as those don't have defined behavior,
>> however "Assigned NFC or NFKC for defined code points" would
>> be 100% unique to the machine.
> Shawn,
>
> A few observations, although we may need to agree to disagree.
>
> First, saying "NFC/NFKC rules" tends to obscure the issue here.
> An important property of NFC/NFD is reversibility, i.e., a dual
> relationship in the mathematical sense.  You may not be able to
> recover whatever the original way, but you can go back and forth
> between the two normalized forms without loss of information.
> By contrast, NFKC (and NFKD) are potentially information-losing
> and that is (although more of some sets of compatibility
> equivalences than others) significant.

Correct about the information loss, but, like case folding (which also loses
information that is significant to the human), NFKC does pick a unique
element out of each equivalence set, satisfying Shawn's statement about
"unique to the machine".

Any of these forms, if they can be guaranteed to be stable, will satisfy
that condition, but the point about the discussion is that identifiers
that are "reasonably mnemonic" as one could characterize IDNs, do
occupy a space between machine and human interaction with writing systems.
>
>> ...
>>> 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.
>> IDN is sociological exercise.  If the need was purely
>> scientific/mathematical, then we'd only need a bunch of
>> numbers or opaque IDs.  In order to make much progress here I
>> think we need to think about how people use them.
> At one level, I agree about "sociological exercise".  I would
> normally characterize it a bit differently, but let's accept
> that for the purposes of this note.  I would say much the same
> thing, not just about IDNs, but about almost any human-readable
> identifier, noting that, as soon as a "bunch of numbers" is
> expressed as numerals in written forms, there are "sociological"
> issues of number base and the set of numerals to be used (in
> Unicode-land and modern writing systems bound to script for
> everything but Arabic).

Actually, Arabic even has potential "variants" among the digits, so while
you can make the identifier be based on the numeric value of what the
human wrote in whatever writing system, you get into issues of recognition
of identifiers etc. once they are communicated in their human-readable
form.
>
> However, maybe there is a different way to characterize this
> issue that avoids the sociological exercise.

It's not just the conventions of a group of users, but also human perception
issues that plague human-readable identifiers, and the "sociological" issue
of the need to counteract fraud.

>   I continue to
> accept that, at least in general, Unicode has a reasonable set
> of coding principles and that, in general, a reasonable set of
> decisions has been made given those principles.  I firmly
> believe that a different coding system, with different
> principles (or priorities among principles) would simply trade
> one set of issues for another but might otherwise be equally
> "good".

Definitely agree with this take.

> However, many of those decisions -- about coding, not
> about characters -- do have alternatives.  For example, instead
> of coding lower and upper case characters differently, one could
> have dealt with case distinctions by assigning a single code
> point to the case-insensitive abstract character and then using
> a qualifier to designate case (either always for one case or
> when anyone cared for both -- two different coding style
> distinctions).  Similarly, ZWJ and ZWNJ are, in some sense,
> indicators and artifacts of coding decisions, not "characters":
> one could have avoiding them by assigning separate code points
> to the characters they affect on rendering (note that there have
> been passionate arguments that just that should have been done
> with some Indic scripts).

Also definitely agree. The task of a universal character set is to make
available a set of what Unicode calls "code elements" that are sufficiently
fine-grained and have the correct properties so that you can use them to
represent all "text elements" needed in writing.

There is certainly some latitude in that analysis of the problem so that the
outcome could, in principle, be a different set of code elements.

Usually, competing solutions are not equal in their degree of efficiency or
usability, but, perhaps unfortunately, the metrics for that is not a single
scale: each type of operation on text, from input, to storage, search, sort
and finally output, could potentially benefit from a different way of
analyzing the fundamental text elements. Creating and processing identifiers
is, not surprisingly, no different.
>
> In a way, decisions about script boundaries are, themselves,
> coding decisions rather than inherent character properties

Correct. You see that when Unicode is forced to duplicate letters because
they were borrowed from one script into another. (Like Latin Q and W
were borrowed into Cyrillic when it was used to write Kurdish)

> but,
> having been vaguely involved with an attempt to define a
> universal character set that did not depend on such boundaries,
> that path seems to lead to madness.  Unicode still could have
> defined its script boundaries differently, e.g., seeking a
> higher level of integration (or "unification") across the board
> but, while I think understand that as a choice is helpful,
> pursuing it very far probably is not.

In some sense one has to accept that writing is a historical process that
accumulates design decisions over time, and very conservatively sticks
to them for long time periods.

Not surprisingly, character encoding, though much younger than writing,
mimics that to some degree. For better or for worse, Unicode largely
inherited the analysis of many writing systems into code elements as
it had been present in existing precursors. And, yes, collectively, these
did include the duality of combining sequences and precomposed forms,
for example.

The value added proposition of a single, universal set was such that it
resulted in the critical mass needed to lead to first adoption and then
rapid replacement of the preceding encodings -- a process that's still
in the tail end of the curve.

While most likely many choices made by Unicode (where there was a
choice to be made that was not constrained) are not "perfect", it's
highly doubtful that they are collectively so bad that any alternative
would represent enough value added to offset the cost and disruption
of a wholesale replacement. Certainly not for some decades.

(I won't say never, because the same as languages go through wrenching
orthography reforms, nothing is truly static when it comes to writing
systems and the technology to implement them).

>
> Modulo the script boundary issue, it is (approximately) possible
> to see all of the "confusion" and "too-similar appearance"
> problems as human perception issues involving the
> recipient/viewer (not really "sociological", but the distinction
> may not be important).   Seen that way, the issue here is not
> about the viewer perception issue but about the coding one --
> resolving differences in decisions about how something might
> have been code (again and for convenience, within a script).  If
> one goes back a few hundred years, the question might become,
> not whether someone viewing the character would "see" the
> difference but whether the calligrapher or perhaps even someone
> trying to set a string in cold type would see an important
> difference -- also, in a way, a coding decision problem.
>
> Coming back to the issue that started this, had Unicode
> (followed by the IETF) not deprecated embedded code points to
> identify languages, U+08A1 could have been coded (using an odd
> notation whose intent should be obvious) as
>      <lang:fula>U+0628 U+0654</lang>
> without loss of any phonetic or semantic information and the
> justification for adding the code point at all would disappear
> (at least absent what we generically describe as "politics", in
> which case the justification for its not decomposing would
> disappear).

It's not just that a language unaccountably prefers a different sequence,
but that the Hamza normally is used to indicate a glottal stop. It's a
separate letter, even though, because it graphically floats, Unicode
represents it as a combining character.  In the case of the Fula language,
the same shape is used as a decoration on a letter, making a new,
single entity, that just happens to look like a glottal stop was placed
after a beh.

There's no constraint, when it comes to Fula, for the writers and font
designers (over long periods) to maintain the precise shape of the
decoration on that letter. While they started out borrowing the shape
of a hamza, who knows where this letter shape will end up -- it's not
constrained, I would argue, because the decoration isn't a hamza
(glottal stop) any longer.

This, in addition to sorting, is one of the arguments for duplicating
letters across scripts, in case of borrowings. While this hasn't happened
on a large scale, glyph shapes and font designs definitely drift over
time and it's best to allow these borrowed letters to drift with the
new script they are now embedded in, and not link them to the
old script that they originated from.

While it's possible to convey all of these distinctions by invisible
codes (markup) they are not necessarily the most robust choice:
invisible codes and markup of any kind have a way of getting
separated from the letters they are supposed to affect.
> Similarly, a different CCS could have avoided at least the
> portion of the "Mathematical" collection that are ultimately
> Latin or Greek letters in special fonts by different coding
> conventions that would use the base character plus qualifiers
> for usage and/or type style.
>
> Another example lies in the collection of combining characters
> that can be used to for precomposed character that don't
> decompose, not for, e.g., phonetic reasons but because the
> definitions of those combining characters don't contain quite
> enough information (see Section 3.3.2.3 of
> draft-klensin-idna-5892upd-unicode70-04.txt and its citations).
> At least in theory, Unicode could have chosen to assign code
> points to more precisely-defined (as to how they affect base
> characters) combining characters.  A coding system with
> different principles might have used position and/or size
> indicator coding with similar effect (an approach that will
> probably be needed if Unicode ever takes on, e.g., Classic Mayan
> script).
>
> Now, from that perspective, this issue is about smoothing over
> (by either some form of equivalence rules or exclusion (or
> non-inclusion)) differences among character code sequences that
> are the result of coding decisions (decisions that are at least
> semi-arbitrary because others could have been made with no
> "important" information loss -- and, yes, "important" is
> sometimes debatable without yet other coding decisions).  For
> sequences that compose and decompose symmetrically, NFC (or NFD)
> normalization does the necessary job.  IDNA2008 disallows those
> mathematical characters as a way to do a different part of the
> job without making non-reversible compatibility equivalences
> part of the standard.

Unfortunately, IDNA2008 lacks a tool that would make many of these issues
easy to manage: there is a subset of the problem where neither normalization
nor non-inclusion is the most adequate way of handling the issue.

Normalization presupposes that in each equivalence set, one an pick one
canonical element without prejudice. Where two different traditions of
writing each use a different element in the set, any canonical choice
in favor of one represents a prejudice against the other.

The same problem plagues non-inclusion. One would have to pick
favorites.

Outside the protocol, other means of addressing the problem exist, such
as mutual exclusion with first-come, first-serve. This requires a registry
with appropriate policies (resulting in a definition of a blocked variant).

The touchstone case for the current discussion, possibly falls into this
category, except that it seems that the use of the glottal stop in Arabic
in general is seen as less essential for identifier purposes (for example
the root zone would not include it).

Luckily, many of the other cases that have been identified following
the publication of the original paper, would be addressable by 
non-inclusion.
In those cases, Unicode has an operational principle of always encoding
any combinations needed for orthographic (as opposed to technical)
use, so that non-inclusion of certain combining marks would be feasible.
>
> As another coding decision matter, all of this would be
> significantly easier were Unicode consistent about its coding
> distinctions.   Such consistency is likely impossible, at least
> given other decisions, but that doesn't mean it wouldn't be
> helpful.   However, we have, instead, a combining sequence
> preference (with exceptions) for Latin but a precomposed
> character preference for Arabic.

It's actually more complex. There are systematic exceptions in Latin, based
on the nature of the mark.

The way Arabic ended up is perhaps more historical accident than perfect
design; few would argue that. But we are stuck with it, just as we are
stuck with other historical accidents.
>   We have all precombined Latin
> characters where combining sequences decomposing, except for
> some combining characters.  Most European scripts code the
> abstract graphics in grapheme clusters but East and South Asian
> ones use indicators like ZWJ and ZWNJ.  There is a strict rule
> against assigning separate code points to typestyle distinctions
> but an exception for some usage contexts such as mathematics and
> phonetic description.  Unicode does not have indicator codes or
> separate code points for layout or presentation (leaving that to
> external markup), but such coding has proved necessary for
> writing systems that are primarily right-to-left and in such
> cases as non-breaking space.  There are no language-dependent or
> pronunciation-dependent coding distinctions (see Section 2 of
> draft-klensin-idna-5892upd-unicode70-04.txt and/or Chapter 2 of
> Uniocde 7.0) except where there are.

An important issue is to remember that code elements aren't text elements,
they are merely guaranteed to be able to represent all needed text elements.

And, while the basic goal is to cover text elements needed to make the text
"readable" (for content) as opposed to final form (with style), some cases
exists where the borderline between form and content is drawn differently,
and in some cases, in order to process a text, more information about 
content
has to be supplied, such as using a no-break space between words that form
some sort of compound (e.g. title and name) without being written together.

Incidentally, not all of the invisible (format or control) characters 
have been
accepted by the user community (LS, PS, or NEL anyone?). But where they
have been, it's a sign that they were addressing a real need in a way that
added value.
>
> Again, I don't think any of those decisions are "wrong".  But
> they are all problematic for the IETF's language-insensitive,
> fairly context-free, identifier comparison purposes.  And they
> are, at least IMO, worth some effort because (again, independent
> of discussions about "confusion"), at least,
>
> (i) We have already established the precedent of dealing with
> all of the important groups of coding artifacts we knew about
> when IDNA2008 was under consideration by adopting normalization
> rules, DISALLOWing a lot of characters, and even developing
> special context-dependent rules for some of them.
>
> (ii) When different input methods, using data entry devices that
> are indistinguishable to the user (e.g., the alphabetic key
> layouts on a German keyboard for Windows, Linux, and the Mac are
> the same) and will produce different output (stored) strings for
> the same input, we are dealing with coding artifacts, not
> "visual confusion".   Whether the difference in internal coding
> is the decision of one system to prefer NFC and that of another
> to prefer NFD or the result of one typist using an "ö" key and
> another deciding to type an "o" and a "dead key" umlaut, we have
> (and IMO, should have) comparison systems that eliminate those
> coding differences.    This is, from that point of view, just a
> new set of coding decision differences that neither Unicode nor
> we arranged to compensate for earlier.

I think the process will bump up against he fundamental limitations that
I pointed out earlier, but, as long as IETF isn't trying to pretend 
those don't
exists, searching for a solution for the tractable cases (and there are 
many)
seems worthwhile to me.

I just don't think it adds value to get hung up over any intractable 
edge cases,
because there are whole classes of problems that are also not tractable on
the protocol level, and, perforce, these have to be handled outside of it.

That's where the recognition of the human perception issue as a big part
of the overall issue with identifiers is a necessary corrective to any 
attempts
to use only the tools available in the protocol.

A./
>
>       john
>
>
>
> One way to look at the issue involved here
>
> _______________________________________________
> Lucid mailing list
> Lucid@ietf.org
> https://www.ietf.org/mailman/listinfo/lucid


From nobody Thu Mar 19 11:29:29 2015
Return-Path: <Shawn.Steele@microsoft.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 4B1541A87A4 for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 11:29:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 xVqb8uzbhKE0 for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 11:29:25 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0707.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::707]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFC941A8772 for <lucid@ietf.org>; Thu, 19 Mar 2015 11:29:25 -0700 (PDT)
Received: from BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) by BLUPR03MB1380.namprd03.prod.outlook.com (25.163.81.139) with Microsoft SMTP Server (TLS) id 15.1.112.19; Thu, 19 Mar 2015 18:29:06 +0000
Received: from BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) by BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) with mapi id 15.01.0112.000; Thu, 19 Mar 2015 18:29:06 +0000
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "Asmus Freytag (t)" <asmus-inc@ix.netcom.com>, John C Klensin <john-ietf@jck.com>
Thread-Topic: [Lucid] FW: [mark@macchiato.com: Re: Non-normalizable diacritics - new property]
Thread-Index: AQHQYeWvrIxB8XNhl06inScNBJS0IJ0jC27ggAAKHACAAB/PsIAAPkeAgACgVQCAAAQLwA==
Date: Thu, 19 Mar 2015 18:29:06 +0000
Message-ID: <BLUPR03MB1378985F9780A98646E7B31B82010@BLUPR03MB1378.namprd03.prod.outlook.com>
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.namprd0 3.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> <20150319023029.GA6046@mx1.yitter.info> <BLUPR03MB137886903F15000BB01E3F5882010@BLUPR03MB1378.namprd03.prod.outlook.com> <A62526FD387D08270363E96E@JcK-HP8200.jck.com> <550B0A32.8080704@ix.netcom.com>
In-Reply-To: <550B0A32.8080704@ix.netcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [50.34.94.236]
authentication-results: ix.netcom.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR03MB1380;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(86362001)(106116001)(99286002)(33656002)(46102003)(122556002)(93886004)(40100003)(19580405001)(19580395003)(92566002)(86612001)(102836002)(2950100001)(2900100001)(77156002)(62966003)(74316001)(2656002)(50986999)(87936001)(76176999)(66066001)(54356999)(76576001)(7059030)(220923002)(222073002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR03MB1380; H:BLUPR03MB1378.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-microsoft-antispam-prvs: <BLUPR03MB13802BDA943C04F5295AE24582010@BLUPR03MB1380.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:BLUPR03MB1380; BCL:0; PCL:0; RULEID:;  SRVR:BLUPR03MB1380; 
x-forefront-prvs: 052017CAF1
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Mar 2015 18:29:06.0869 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB1380
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/CwLkU-QrPNvhYCNMtZWi8iiKewQ>
Cc: "lucid@ietf.org" <lucid@ietf.org>, Andrew Sullivan <ajs@anvilwalrusden.com>
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 18:29:28 -0000

PiBBbnkgb2YgdGhlc2UgZm9ybXMsIGlmIHRoZXkgY2FuIGJlIGd1YXJhbnRlZWQgdG8gYmUgc3Rh
YmxlLCB3aWxsIHNhdGlzZnkgdGhhdCBjb25kaXRpb24sIGJ1dCB0aGUgcG9pbnQgYWJvdXQgdGhl
IGRpc2N1c3Npb24gaXMgdGhhdCBpZGVudGlmaWVycyB0aGF0IGFyZSAicmVhc29uYWJseSBtbmVt
b25pYyIgYXMgb25lIGNvdWxkIGNoYXJhY3Rlcml6ZSBJRE5zLCBkbyBvY2N1cHkgYSBzcGFjZSBi
ZXR3ZWVuIG1hY2hpbmUgYW5kIGh1bWFuIGludGVyYWN0aW9uIHdpdGggd3JpdGluZyBzeXN0ZW1z
Lg0KDQpUaGlzIGRpc2N1c3Npb24gc2VlbXMgdG8gYmUgYWJvdXQgbG90cyBvZiB0aGluZ3MsIGJ1
dCAicmVhc29uYWJseSBtbmVtb25pYyIgd291bGQgbGltaXQgdGhlIHByb2JsZW0gaHVnZWx5LiAg
VGhhdCBpbXBsaWVzIHRoYXQgSSBjYW4gc2VlIGl0IGFuZCByZW1lbWJlciB3aGF0IGl0IHdhcyB0
byB0eXBlIGl0IGxhdGVyLiAgSG93ZXZlciB0aGF0IHNjZW5hcmlvIGRvZXNuJ3QgaGl0IGFueSBv
ZiB0aGUgc2VjdXJpdHkgY29uY2VybnMgYmVpbmcgcmFpc2VkIGFzIEknbSBnb2luZyB0byB0eXBl
IGl0IHVzaW5nIHRoZSBhcHByb3ByaWF0ZSBrZXlib2FyZCBmb3IgbXkgbGFuZ3VhZ2UuICBTdXJl
LCBpZiB0aGUgZG9tYWluIGhhZCBhIEN5cmlsbGljIGwgbWF5IGhhdmUgdHJvdWJsZSwgaG93ZXZl
ciB0aGF0J3Mgbm90IG1uZW1vbmljLCB0aGF0J3Mgc29tZW9uZSBiZWluZyBzbmVha3kuICAoU2Vl
IGZyYXVkIGJlbG93KQ0KDQo+IEFjdHVhbGx5LCBBcmFiaWMgZXZlbiBoYXMgcG90ZW50aWFsICJ2
YXJpYW50cyIgYW1vbmcgdGhlIGRpZ2l0cywgc28gd2hpbGUgeW91IGNhbiBtYWtlIHRoZSBpZGVu
dGlmaWVyIGJlIGJhc2VkIG9uIHRoZSBudW1lcmljIHZhbHVlIG9mIHdoYXQgdGhlIGh1bWFuIHdy
b3RlIGluIHdoYXRldmVyIHdyaXRpbmcgc3lzdGVtLCB5b3UgZ2V0IGludG8gaXNzdWVzIG9mIHJl
Y29nbml0aW9uIG9mIGlkZW50aWZpZXJzIGV0Yy4gb25jZSB0aGV5IGFyZSBjb21tdW5pY2F0ZWQg
aW4gdGhlaXIgaHVtYW4tcmVhZGFibGUgZm9ybS4NCg0KVGhhdCdzIGRpZ3Jlc3NpbmcgZnJvbSBt
eSBwb2ludC4gIEkgd2FzIHRyeWluZyB0byBzYXkgdGhhdCwgaWYgd2UgY29uc2lkZXIgdGhlIHBy
b2JsZW0gd2l0aG91dCBhbnkgaHVtYW4gZmFjdG9ycywgd2UgYWxyZWFkeSBoYXZlIHVuaXF1ZSBJ
RHMuICBUaGVyZSdzIG5vIHdheSB0aGF0IG1hY2hpbmVzIGNvbmZ1c2UgYW55IG9mIHRoZXNlIG5h
bWVzLCBpdCdzIG9ubHkgdGhlIGh1bWFucyB0aGF0IGRvIHRoYXQuICAoWWVzLCB0aGV5J3JlIGFu
IGltcG9ydGFudCBwYXJ0KS4gDQoNCj4gSXQncyBub3QganVzdCB0aGUgY29udmVudGlvbnMgb2Yg
YSBncm91cCBvZiB1c2VycywgYnV0IGFsc28gaHVtYW4gcGVyY2VwdGlvbiBpc3N1ZXMgdGhhdCBw
bGFndWUgaHVtYW4tcmVhZGFibGUgaWRlbnRpZmllcnMsIGFuZCB0aGUgInNvY2lvbG9naWNhbCIg
aXNzdWUgb2YgdGhlIG5lZWQgdG8gY291bnRlcmFjdCBmcmF1ZC4NCg0KVGhhdCdzIGFuIGFkZGl0
aW9uYWwgcmVxdWlyZW1lbnQgdG8gdGhlICJyZWFzb25hYmx5IG1uZW1vbmljIiBhYm92ZS4gIEhv
d2V2ZXIgaWYgdGhpcyBlbnRpcmUgZXhlcmNpc2UgaXMgaW50ZW5kZWQgdG8gY291bnRlcmFjdCBm
cmF1ZCwgdGhlbiB3ZSBnZXQgbXkgdmlldyB0aGF0ICJ0cnlpbmcgdG8gYWRkcmVzcyB0aGVzZSBj
b2RlcG9pbnRzIGlzIHdheSBtb3JlIGNvc3RseSB0aGFuIGl0cyBiZW5lZml0Ii4gIA0KDQpUaGUg
cGVvcGxlIGluIHRoaXMgcm9vbSBhcmVuJ3QgZ29pbmcgdG8gY2xpY2sgb24gIjFzdGJhbmsudHJ1
c3RtZS5jb20iLCBidXQgZXZlcnlvbmUgZWxzZSBvbiB0aGUgcGxhbmV0IChvciBhdCBsZWFzdCA5
MCUgb2YgdGhlbSkgY2xpY2sgdGhhdCBsaW5rLiAgU28gd29ycnlpbmcgYWJvdXQgc29tZW9uZSBz
cGVsbGluZyBpdCAibHN0YmFuay5jb20iIHByb3ZpZGVzIGNsb3NlIHRvIHplcm8gdmFsdWUuICBB
dCBsZWFzdCBpbiB0aGUgcmlnaHQgZm9udCA1MCUgb2YgdGhlIG90aGVyIGh1bWFucyBtaWdodCBz
dGFydCBzdXNwZWN0aW5nIHRoYXQgb25lLg0KDQpIZWNrIFJFQUwgQlVTSU5FU1NFUyBzZW5kIG1l
IHRvIGNyYXBweSBVUkxzIGxpa2UgdGhhdCBhbGwgdGhlIHRpbWUuICAiV2UgcGFydG5lcmVkIHdp
dGggQUJDc3VydmV5LmNvbSB0byBnZXQgeW91ciBmZWVkYmFjaywgdHJ1c3QgdXMiLiAgIldlJ3Jl
IHJlcGx5aW5nIGFib3V0IHlvdXIgcmVjZW50IGV4cGVyaWVuY2UgZnJvbSB0cnVzdG1lQGVtYWls
aG9zdGluZy5jb20iLiAgIldlIHNlZSB5b3UgbGlrZSBvdXIgbXVzZXVtLCBjb25zaWRlciBkb25h
dGluZyBhdCBmdW5kcmFpc2luZy5jb20vb3VybXVzZXVtIi4gIEV2ZW4gbXkgQkFOSyBkb2VzIHRo
YXQuICBIZWNrLCB0aGV5IGV2ZW4gc2VuZCBtZSB0aGUgIjFzdGJhbmsudHJ1c3RtZS5jb20iIGxp
bmtzLiAgSXQgaXJyaXRhdGVzIG1lIHRvIG5vIGVuZC4gDQoNCihUaGlzIHRvdGFsIG9ibGl2aW91
c25lc3MgdG8gc2VjdXJpdHkvc3Bvb2ZpbmcvcGhpc2hpbmcgaXNuJ3QgZXZlbiBsaW1pdGVkIHRv
IEROUywgSSd2ZSByZWNlaXZlZCBjYWxscyBiZWNhdXNlIG9mIGJpbGxpbmcgZ2xpdGNoZXMgYW5k
IHRoZSBiYW5rIHNheXMgInlvdSBjYW4gcGF5IG5vdywgZ2l2ZSB1cyB5b3VyIENDIG9yIGNoZWNr
IHJvdXRpbmcgaW5mbyIuICBUaGF0J3Mgbm9ybWFsLiAgVGhleSB0aGV5IGFzayBteSBzZWNyZXQg
Y29kZSBvciB3aGF0ZXZlciB0byB2ZXJpZnkgaXQncyBtZSwgYW5kIEkgcG9pbnQgb3V0IHRoYXQg
SSBjYW4ndCBldmVuIHZlcmlmeSB0aGF0IHRoZXkncmUgd2hvIHRoZXkgc2F5IHRoZXkgYXJlIGFu
ZCB0aGV5J3JlIHN0dW1wZWQuICBXZWxsLCB5b3UgY2FuIGNhbGwgdXMgYmFjayBhdCAxLTgwMC0x
MjMtNDU2Ny4gIFNlcmlvdXNseSE/IT8hICBFdmVuIG15IGJhbmsgaGFzIG5vIGNsdWUgd2hhdCBz
ZWN1cml0eSBpcz8pDQoNCkZpeCB0aGF0LCBhbmQgdGhlbiB3ZSBjYW4gdGFsayBhYm91dCB3aGV0
aGVyIGl0J3Mgd29ydGggZml4aW5nIGEgY291cGxlIGVzb3RlcmljIGNvZGUgcG9pbnRzLiAgVGhl
cmUgYXJlIEZBUiBlYXNpZXIgZXhwbG9pdHMgZm9yIGFueSBzZXJpb3VzIGF0dGFja2VyIHRvIGF0
dGFjay4gIEl0J3MgY2VydGFpbmx5IG5vdCB3b3J0aCByaXNraW5nIGJyZWFraW5nIHJlYWwgc3Ry
aW5ncyBhbmQgcmVhbCBtbmVtb25pY3MgdGhhdCByZWFsIHVzZXJzIG1pZ2h0IHdhbnQgdG8gdXNl
LiAgKElNTyBpdHMgbm90IGV2ZW4gd29ydGggcHJvaGliaXRpbmcgSeKZpU5ZLmNvbSkNCg0KQXQg
dGhpcyBwb2ludCBJJ20gd2VsbCBiZXlvbmQgdGhlICJpZGVudGlmeWluZyB0aGUgcHJvYmxlbSBz
dGF0ZW1lbnQiLCBzb3JyeS4NCg0KSG93ZXZlciwgdGhhdCBkb2VzIGJyaW5nIG1lIGJhY2sgdG8g
dGhlICJ3aGF0IGFyZSB3ZSB0cnlpbmcgdG8gZG8gdGhpcyBmb3I/IiBxdWVzdGlvbi4gIElNTyB0
aGVyZSBpcyBubyB2YWx1ZSBpbiB0cnlpbmcgdG8gc2VjdXJlIEROUyBieSBwcm9oaWJpdGluZyB0
aGVzZS4gIEhvd2V2ZXIgSSdtIG9wZW4gdG8gdGhlIGlkZWEgdGhhdCB0aGVyZSdzIGFuIG1hY2hp
bmUvY29tcHV0ZXIgc2NpZW5jZSBuZWVkIGZvciB1bmlxdWUgaWRlbnRpZmllcnMgdGhhdCBhcHBh
cmVudGx5IHdlIHdhbnQgdG8gYmUgbW5lbW9uaWMuICBJIGhhdmUgbm8gY2x1ZSB3aGF0IHRob3Nl
IHNjZW5hcmlvcyBhcmUuICBJIGdldCB3YW50aW5nIGFuIElSSSB0byBpZGVudGlmeSBhIHVuaXF1
ZSByZXNvdXJjZSwgYnV0IHdlIGFscmVhZHkgaGF2ZSB0aGF0IChwcmVzdW1pbmcgdGhlIG1hY2hp
bmUgZG9lcyB0aGUgaW50ZXJwcmV0YXRpb24gdGhlcmUncyBubyBhbWJpZ3VpdHkpLiAgSSBhbSBj
bGVhcmx5IHRvdGFsbHkgbWlzc2luZyB3aGF0ZXZlciBzY2VuYXJpbyBpdCBpcyB3aGVyZSBhIGNv
bmZ1c2FibGUgdHlwZSBJRCBpcyBuZWVkZWQgZm9yIGFuIGlkZW50aWZpZXIgaW4gYSBzeXN0ZW0g
d2hlcmUgaXQgY291bGQgYWN0dWFsbHkgYmUgY29uZnVzZWQuDQoNCi1TaGF3bg0K


From nobody Thu Mar 19 12:29:56 2015
Return-Path: <john-ietf@jck.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 775E71A8844 for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 12:29:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 UvHjnJa5_zjU for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 12:29:45 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 990A41A8856 for <lucid@ietf.org>; Thu, 19 Mar 2015 12:29:45 -0700 (PDT)
Received: from [198.252.137.35] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1YYg8N-000Pc2-RM; Thu, 19 Mar 2015 15:29:35 -0400
Date: Thu, 19 Mar 2015 15:29:30 -0400
From: John C Klensin <john-ietf@jck.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>, "Asmus Freytag (t)" <asmus-inc@ix.netcom.com>
Message-ID: <B26BCFD19372D553F50138A9@JcK-HP8200.jck.com>
In-Reply-To: <BLUPR03MB1378985F9780A98646E7B31B82010@BLUPR03MB1378.namprd03.prod.outlook.com>
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.namprd0 3.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> <20150319023029.GA6046@mx1.yitter.info> <BLUPR03MB137886903F15000BB01E3F5882010@BLUPR03MB1378.namprd03.prod.outlook.com> <A62526FD387D08270363E96E@JcK-HP8200.jck.com> <550B0A32.8080704@ix.netcom.com> <BLUPR03MB1378985F9780A98646E7B31B82010@BLUPR03MB1378.namprd03.prod.outlook.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.35
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/zdDiZWgTLUfOa1Pu_g5rpvzecFg>
Cc: lucid@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
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 19:29:52 -0000

--On Thursday, March 19, 2015 18:29 +0000 Shawn Steele
<Shawn.Steele@microsoft.com> wrote:

>> Any of these forms, if they can be guaranteed to be stable,
>> will satisfy that condition, but the point about the
>> discussion is that identifiers that are "reasonably mnemonic"
>> as one could characterize IDNs, do occupy a space between
>> machine and human interaction with writing systems.
>=20
> This discussion seems to be about lots of things, but
> "reasonably mnemonic" would limit the problem hugely.  That
> implies that I can see it and remember what it was to type it
> later.  However that scenario doesn't hit any of the security
> concerns being raised as I'm going to type it using the
> appropriate keyboard for my language.  Sure, if the domain had
> a Cyrillic l may have trouble, however that's not mnemonic,
> that's someone being sneaky.  (See fraud below)

Shawn, for better or worse, "reasonably mnemonic" might be an
attractive way to think about things, but it is never been a
requirement the community has chosen to impose on the DNS (even
though ICANN has chosen to impose variations on it on domains it
controls).  See RFC 2181 for some rather strong statements to
the contrary.   "No mnemonic requirement" is actually important
outside the IDN space because there are a number of applications
that use strings  as owner names that, on inspection, we might
guess were hashes.  Lack of willingness to impose such a
restriction is also the main reasons why IDNA has never
contained a "no mixed scripts" rule (there is also a technical
reason, but we could have gotten around that one).

>> Actually, Arabic even has potential "variants" among the
>> digits, so while you can make the identifier be based on the
>> numeric value of what the human wrote in whatever writing
>> system, you get into issues of recognition of identifiers
>> etc. once they are communicated in their human-readable form.
>=20
> That's digressing from my point.  I was trying to say that, if
> we consider the problem without any human factors, we already
> have unique IDs.=20

We also, as you point out, have no justification for IDNs.  The
community has, for better or worse, thoroughly rejected that
position, so I hope we can move on.

> There's no way that machines confuse any of
> these names, it's only the humans that do that.

Quite the contrary.  If differences among coding sequences for
the same string, depending on human-invisible distinctions such
as choice of IME or host, can produce different results and then
a comparison procedure is used, then, in practical terms, it is
the machines that are confused.  That is precisely why we
normalize before comparing and one of the key reasons why
IDNA2008 DISALLOWs a lot of code points that might be
problematic for machine comparison purposes.   By contrast,
case-folding and DISALLOWing some other characters are about the
potential for human confusion because machines know perfectly
well that upper and lower case characters (no matter how coded
as long as they are coded distinctly) are different.   Probably
part of the present problem is that we may need to be a little
more precise about those distinctions than we have been in the
past but, while that would change our vocabulary, it would not
change the problem.

Some of the above might help with fraud detection or prevention,
but the requirements exist without any consideration of fraud.

Please read and try to understand the distinction I tried to
make between coding artifacts and character confusion in my
previous response to you and try to work your way through the
discussion of cases in draft-klensin-idna-5892upd-unicode70-04
-- they really are important to this.

>...
> That's an additional requirement to the "reasonably mnemonic"
> above.  However if this entire exercise is intended to
> counteract fraud, then we get my view that "trying to address
> these codepoints is way more costly than its benefit". =20

It is not entirely or even largely to counteract fraud.  Things
like ICANN's Label Generation Rules might well be defined in
terms of fraud or at least confusion.  I encourage you to read
about them and comment.  But, these particular issues, as
described in draft-sullivan-lucid-prob-stmt and
draft-klensin-idna-5892upd-unicode70 (-04 and anything later),
are really about resolving different coding for the same
character, and not confusion or fraud except incidentally.
There is a big issue in that about what "same character" means,
but that still isn't about fraud or even about confusion between
pairs of characters that almost everyone agrees are different.

> The people in this room aren't going to click on
> "1stbank.trustme.com", but everyone else on the planet (or at
> least 90% of them) click that link.  So worrying about someone
> spelling it "lstbank.com" provides close to zero value.  At
> least in the right font 50% of the other humans might start
> suspecting that one.

And that, while interesting, seems to me completely irrelevant
to the current discussion.   If you want to make comments on the
fraud case, please explain how the "humans in this room" are
expected to distinguish between "n=C3=BCr" (with the middle
character coded as U+00FC) and "n=C3=BCr" (with the middle =
character
coded as U+0075 U+0308).  Applying NFC to both strings handles
that case perfectly well and that is why we do it.  Part of the
issue here is the cases that NFC does not handle as well.

>...
> (This total obliviousness to security/spoofing/phishing isn't
> even limited to DNS, I've received calls because of billing
> glitches and the bank says "you can pay now, give us your CC
> or check routing info".  That's normal.  They they ask my
> secret code or whatever to verify it's me, and I point out
> that I can't even verify that they're who they say they are
> and they're stumped.  Well, you can call us back at
> 1-800-123-4567.  Seriously!?!?!  Even my bank has no clue what
> security is?)

Of course.  And I've had endless arguments with various
financial institutions, both about their procedures and their
barriers to letting me use even rudimentary self-protective
measures.  But it has nothing to do with the present question
whether or not I carry out my fantasy of posting all of those
examples to rants-are-us.example or, better yet, the more
elegant (or perverse, depending one one's perspective)
rants-=D1=8F-us.example.

> Fix that, and then we can talk about whether it's worth fixing
> a couple esoteric code points.  There are FAR easier exploits
> for any serious attacker to attack.  It's certainly not worth
> risking breaking real strings and real mnemonics that real
> users might want to use.  (IMO its not even worth prohibiting
> I=E2=99=A5NY.com)

Sorry, but the community believes you are in the rough.
Incidentally, one of the main reasons why the second character
in I=E2=99=A5NY is DISALLOWED (and hence why the string is =
invalid as
a U-label) also has nothing to do with fraud but is associated
with difficulties in precise enough description of symbols in
screen readers and other text-to-speech applications that they
can be typed back in.  That is another human consideration of
course... too bad about those humans, the world would be so much
neater without them.

>...

I've probably said too much already -- please try to forgive my
frustration after struggling with the real for more months than
I want to think about and being regularly distracted by people
who want to talk about confusion.  Again, please read the two
I-Ds which, at least IMO, actually do give a decent description
of what the problem is thought to be or at least parts of that
puzzle.   IMO, if either uses words like "confusion" or "fraud",
they are historical errors grounded in ways of thinking about
other problems. =20

If you want to talk about confusion and fraud, they are really
interesting discussions on which a lot of good people have spent
a lot of time, but they are really not what this is about.

 best,
    john


From nobody Thu Mar 19 12:32:17 2015
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 629631A3B9B for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 12:32:09 -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 txdUl03O-h7R for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 12:32:08 -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 AA3A81A8868 for <lucid@ietf.org>; Thu, 19 Mar 2015 12:32:01 -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 AF6AE8A031 for <lucid@ietf.org>; Thu, 19 Mar 2015 19:32:00 +0000 (UTC)
Date: Thu, 19 Mar 2015 15:31:59 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: lucid@ietf.org
Message-ID: <20150319193158.GH6655@mx1.yitter.info>
References: <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> <20150319023029.GA6046@mx1.yitter.info> <BLUPR03MB137886903F15000BB01E3F5882010@BLUPR03MB1378.namprd03.prod.outlook.com> <A62526FD387D08270363E96E@JcK-HP8200.jck.com> <550B0A32.8080704@ix.netcom.com> <BLUPR03MB1378985F9780A98646E7B31B82010@BLUPR03MB1378.namprd03.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BLUPR03MB1378985F9780A98646E7B31B82010@BLUPR03MB1378.namprd03.prod.outlook.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/ywS_B9Zl8fQFCpdy69Klw01Hy4M>
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 19:32:09 -0000

On Thu, Mar 19, 2015 at 06:29:06PM +0000, Shawn Steele wrote:

> This discussion seems to be about lots of things, but "reasonably mnemonic" would limit the problem hugely.  That implies that I can see it and remember what it was to type it later.  However that scenario doesn't hit any of the security concerns being raised as I'm going to type it using the appropriate keyboard for my language.

No, because it's reasonably mnemonic _for someone_, not for everyone.
You're assuming that localization is the only relevant parameter, but
it's not: the problem with identifiers for Internet-wide use is that
they're supposed to be both internationalized and localized at the
same time. 

For instance, CAs are supposed to be doing validation on these names
and nailing them to organizations.  We've already had problems with
invalid issuance of certificates (as you may be aware, since your
apparent employer has been one of the targets), and this issue opens
that door more widely.  CAs are not going to be experts in every
writing system, and the same-script registration rules won't help
anything here because they're ineffective.

Similar issues might be expected for other kinds of identifiers in
Internet-scope use.

I think if you read the I-D carefully, you'll discover that this point
is made in section 3.1.

> That's digressing from my point.  I was trying to say that, if we consider the problem without any human factors, we already have unique IDs.

And as I said before, this is tautologically true or false, depending
on what you mean by "ID".  It seems you're devoted to "tautologically
true", but I fail to understand why you think that's a remotely
interesting point in this discussion.  Everyone already agrees that
there's a human factors issue here.

> Fix that, and then we can talk about whether it's worth fixing a couple esoteric code points.  There are FAR easier exploits for any serious attacker to attack.

"There is that problem over there, so this problem isn't worth
fixing."  I'm not suggesting that the other problem is not an issue,
but this one turns out to be an in-principle misunderstanding on the
part of the IETF about how it was going to construct internationalized
identifiers.  In principle misunderstandings are the sort of things
that one must address (even to conclude "not worth fixing") if one is
going to write protocols that are worth anything at all.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Thu Mar 19 13:36:50 2015
Return-Path: <john-ietf@jck.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 270DA1A9084 for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 13:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.61
X-Spam-Level: 
X-Spam-Status: No, score=-4.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Yf1PQpizGYt2 for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 13:36:48 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 094541A9064 for <lucid@ietf.org>; Thu, 19 Mar 2015 13:36:48 -0700 (PDT)
Received: from [198.252.137.35] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1YYhBM-000Pkv-KR; Thu, 19 Mar 2015 16:36:44 -0400
Date: Thu, 19 Mar 2015 16:36:39 -0400
From: John C Klensin <john-ietf@jck.com>
To: Asmus Freytag <asmusf@ix.netcom.com>, lucid@ietf.org
Message-ID: <65FEF8E132C1656B0E10BCAC@JcK-HP8200.jck.com>
In-Reply-To: <550B0C70.7030003@ix.netcom.com>
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.namprd0 3.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> <20150319023029.GA6046@mx1.yitter.info> <BLUPR03MB137886903F15000BB01E3F5882010@BLUPR03MB1378.namprd03.prod.outlook.com> <A62526FD387D08270363E96E@JcK-HP8200.jck.com> <550B0C70.7030003@ix.netcom.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.35
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/NmHa_YGjpIlNUuJBo3YeJ_0DNPE>
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>
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 20:36:50 -0000

--On Thursday, March 19, 2015 10:50 -0700 Asmus Freytag
<asmusf@ix.netcom.com> wrote:

>...
>> Coming back to the issue that started this, had Unicode
>> (followed by the IETF) not deprecated embedded code points to
>> identify languages, U+08A1 could have been coded (using an =
odd
>> notation whose intent should be obvious) as
>>      <lang:fula>U+0628 U+0654</lang>
>> without loss of any phonetic or semantic information and the
>> justification for adding the code point at all would =
disappear
>> (at least absent what we generically describe as "politics",
>> in which case the justification for its not decomposing would
>> disappear).
>=20
> It's not just that a language unaccountably prefers a
> different sequence,
> but that the Hamza normally is used to indicate a glottal
> stop.=20

"unaccountability" is a judgment that has nothing to do with
this.  I've talked about it and constructed an example in
language terms because that is the way this example was first
justified to us and I was trying to refer back to that example
and presentation.   Pursuing the same example, one could as
easily, in a hypothetical coding system different from Unicode,
but taking advantage of the same basic code space, write=20
    U+0628 U+0654 <phoneme:U+0294/>=20
which would use U+0654 to identify an abstraction for the Hamza
grapheme and qualify its phonetic use with a qualifier that
identifies the phoneme.  The same story could be applied to our
old example of "=C3=B6" with different phonetic and/or language
qualifiers for German and Swedish.

Again, I'm not advocating any of those alternatives, only trying
to reinforce my point that these results are the consequences of
decisions about coding (either due to a general, if complex, set
of rules or to per character decisions) and not intrinsic
properties of the grapheme clusters.

> It's a
> separate letter, even though, because it graphically floats,
> Unicode
> represents it as a combining character.  In the case of the
> Fula language,
> the same shape is used as a decoration on a letter, making a
> new,
> single entity, that just happens to look like a glottal stop
> was placed after a beh.

Given the above, and various other conversations, I believe the
above statement about "separate letter" is true, but that the
argument is ultimately circular.   In other words, Unicode has
adopted a set of rules about when characters are distinct (rules
that, sadly, are not completely described in the standard) and
them applied them.  Application of those rules (which I'm
prepared to believe are reasonable for some general case and
self-consistent) results in "combining character" in one place
and "separate character" in another.  Application of a
hypothetical different set of rules (including, purely as an
example, my reading of the [now obviously incomplete] set of
rules that actually appear in The Unicode Standards) might yield
a different result, such as a precomposed character that
decomposed or no precomposed character at all.

> There's no constraint, when it comes to Fula, for the writers
> and font
> designers (over long periods) to maintain the precise shape of
> the
> decoration on that letter. While they started out borrowing
> the shape
> of a hamza, who knows where this letter shape will end up --
> it's not
> constrained, I would argue, because the decoration isn't a
> hamza (glottal stop) any longer.
>...

And I suppose that, if we wait enough centuries and Fula evolves
backwards from being written primarily in Latin script (after
being written primarily in Arabic script until a few centuries
ago), we will find out.  But, if things a going to be coded
differently because the writing systems associated with
different languages might evolve differently (as I agree they
have over the centuries) and the desire is to future-proof
things), then we should really code "=C3=B6" differently for =
Swedish
than for German because, after all, Swedish writing might evolve
in the direction of Danish or Norwegian so that "=C3=B6" would =
be
replaced by the phonetically-similar "=C3=B8".     Or perhaps =
the
evolution would work the other way and we should therefore code
Norwegian and Danish separately lest "=C3=B8" in Norwegian =
evolve in
the direction of "=C3=B6" while Danish remains unchanged.  The
"borrowed letter" analogy applies there too because few, if any,
of those languages were originally written in Latin script
(whether we should permit, e.g., Runic in the DNS is of course a
separate issue as is the likelihood of, e.g., Norwegian evolving
back toward it).  I imagine those changes are probably unlikely,
but they are less drastic than the Fula example which would
require a complete reversal of the writing system's choice of
basic script.

Unless Unicode is going to go back and review the decisions
(which various stability rules now prohibit), I don't think this
helps except for understanding whether there are actually
predictable rules or whether code point allocation decisions are
ultimately made by a small cluster of people sitting more or
less in private and saying "that should be a separate,
non-decomposing, code point because it feels that way to us and
that other thing shouldn't because it doesn't" (or in the words
of a notorious US judge "I know it when I see it ").   I still
hope the situation is closer to the former and your explanations
have helped me a lot in understanding why that may be true. =20

But our bottom line is still (or again) that we need some sort
of overlay or mechanism that will allow identifier comparison
among strings with absolutely no language, phonetic, or other
usage-context information (other than script) to work, present
tense, to a first order approximation of what those writing the
grapheme clusters or seeing them in isolation perceive.  How
symbols are pronounced or affect pronunciation, how those
symbols might evolve as the writing system evolves, whether they
are used as word-forming letters in a script or as, e.g.,
Mathematical notations, or what languages they are used with are
simply not relevant to the issue. =20

Either enough of the alternate coding sequences have to be
disallowed to eliminate ambiguity because only one combination
is left, the alternatives have to somehow compare equal, or we
need to conclude that certain combinations are sufficiently
unlikely to justify not worrying about.  I imagine we might end
up with a combination of those options for different cases.   If
the choice rules can be turned into properties that help in that
process, that would be great.  If not, I think we may need to
lose interest in them other than accepting that they will
sometimes produce these distinctions in coding choices.

> While it's possible to convey all of these distinctions by
> invisible
> codes (markup) they are not necessarily the most robust =
choice:
> invisible codes and markup of any kind have a way of getting
> separated from the letters they are supposed to affect.

Of course, that is an argument against direction indicators in
Bidi situations and a number of other things.  I trust we all
understand by now that this is all about tradeoffs, optimization
for particular classes of usage, good choices about what to
optimize for, and, as you have pointed out, sometimes the result
that optimizing a coding system for one group of things may
pessimize it for another.

best,
    john


From nobody Thu Mar 19 15:15:46 2015
Return-Path: <asmusf@ix.netcom.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 594F51B2AF5 for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 15:15:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4
X-Spam-Level: 
X-Spam-Status: No, score=-4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_LETTER=-2, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 vFrlZDN4Pk1t for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 15:15:41 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id 78DB51B2AF4 for <lucid@ietf.org>; Thu, 19 Mar 2015 15:15:41 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=JeANuFUafvJApyDGu6+2vDt3D8C5t/6km4XQGVB56iAutE74qU64x+TlEbpbH7RA; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [72.244.206.133] (helo=[192.168.0.107]) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <asmusf@ix.netcom.com>) id 1YYiik-0000ud-MZ; Thu, 19 Mar 2015 18:15:20 -0400
Message-ID: <550B4A78.2020108@ix.netcom.com>
Date: Thu, 19 Mar 2015 15:15:20 -0700
From: Asmus Freytag <asmusf@ix.netcom.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, lucid@ietf.org
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.namprd0 3.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> <20150319023029.GA6046@mx1.yitter.info> <BLUPR03MB137886903F15000BB01E3F5882010@BLUPR03MB1378.namprd03.prod.outlook.com> <A62526FD387D08270363E96E@JcK-HP8200.jck.com> <550B0C70.7030003@ix.netcom.com> <65FEF8E132C1656B0E10BCAC@JcK-HP8200.jck.com>
In-Reply-To: <65FEF8E132C1656B0E10BCAC@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2b65b6112f8911537af5e3def6ebc7056cf102e77eeb84a22350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 72.244.206.133
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/6ogi2cJwpTIj9-nIiUmdYZkip9w>
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>
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 22:15:45 -0000

On 3/19/2015 1:36 PM, John C Klensin wrote:
>
> --On Thursday, March 19, 2015 10:50 -0700 Asmus Freytag
> <asmusf@ix.netcom.com> wrote:
>
>> ...
>>> Coming back to the issue that started this, had Unicode
>>> (followed by the IETF) not deprecated embedded code points to
>>> identify languages, U+08A1 could have been coded (using an odd
>>> notation whose intent should be obvious) as
>>>       <lang:fula>U+0628 U+0654</lang>
>>> without loss of any phonetic or semantic information and the
>>> justification for adding the code point at all would disappear
>>> (at least absent what we generically describe as "politics",
>>> in which case the justification for its not decomposing would
>>> disappear).
>> It's not just that a language unaccountably prefers a
>> different sequence,
>> but that the Hamza normally is used to indicate a glottal
>> stop.
> "unaccountability" is a judgment that has nothing to do with
> this.

I used that term to merely mean "apparently without cause".

>    I've talked about it and constructed an example in
> language terms because that is the way this example was first
> justified to us and I was trying to refer back to that example
> and presentation.   Pursuing the same example, one could as
> easily, in a hypothetical coding system different from Unicode,
> but taking advantage of the same basic code space, write
>      U+0628 U+0654 <phoneme:U+0294/>
> which would use U+0654 to identify an abstraction for the Hamza
> grapheme and qualify its phonetic use with a qualifier that
> identifies the phoneme.  The same story could be applied to our
> old example of "ö" with different phonetic and/or language
> qualifiers for German and Swedish.

Character encoding is not the process of numbering entities by shape.

It's the process of numbering entities by their underlying identity in
writing.

For 90% plus of all cases, the distinction seemingly doesn't matter,
because, especially in context, we experience the different entities
as having different shapes. We don't even realize that we abstract
away the shape, radically in many cases, and we treat unexpected
overlaps of the shapes associated with different characters as
accidents of fonts, low-resolution rendering, or what not.

But U+0041 really encodes the idea of an uppercase letter A.
That it is possible to render it in a Fraktur font, where it may well
look (to the uninitiated) as a form of triangular U, and that this
does not cause any issues (usually) is fully indicative of this:
to repeat, what is encoded is the (abstract) identity, not the concrete
shape.

This works really well for ordinary texts where context allows us
to effortlessly (more or less) read characters even if they are shown
in (artistically) distorted shapes, such as used in decorative fonts.

There are cases, mostly for symbols and punctuation, where there
is both less of a shared understanding of what the expected range
of appearance is for a given text element defined in the abstract.

Here, then, is the case where character encoders (including Unicode)
will decide to defer more to the appearance in marking the boundary
between different abstract text elements, and thus disunify them
in the encoding.

On top of that, frozen letter forms (selected, very specific renderings that
do no longer admit of the same range of glyph shapes as the original
did) have been borrowed into technical notation - most prominently
phonetic and mathematical. (Much phonetic notation has then given
rise to new alphabets, returning  the frozen form back into the
pool, but now as a new letter).

No wonder that Unicode doesn't have an "algorithm" to decide on
where the boundaries fall in identifying the boundary between
separate abstract entities to be encoded. In the end, more often
than not, this bottoms out in a pragmatic judgment of the "I know
it when I see it" variety.

It's a fundamental misunderstanding, then, of character encoding to
expect it to be glyph based, and an equally fundamental misunder-
standing to expect combining marks primarily as lego blocks for
glyph construction.

Combining marks represent, variously, separate letters that happen
to graphically "float" above other characters or result in merged
shapes (Arabic and Indic scripts have plenty of examples) or they
represent identifiable decorations of characters, best understood
by the combining arrow above to represent a vector in math.

The decoration, in this case has a very clear semantic component
of its own, hence is a separate character, but graphically exists
only as a decoration (requires a base).

Most diacritics (accent marks, etc.) at least in phonetics, also have
these separate identities.

True dual encoding entered the picture because of the conservative
nature of writing systems (and character encodings). The precursor
encodings had (largely, but not exclusively) chosen a simpler
analysis, and encoded precomposed entities. Unicode inherited that
model (but also the competing model). It turns out combinations could
not be rationally supported in a universal set, because to be universal
one would have to cater for the needs of scholars to apply these marks
to (practically) *any* other character. Incomplete drafts of lists of known
combinations, for Latin only, reached several thousand combinations,
before sanity finally prevailed, and the precomposed entities were
limited to the then existing set needed for legacy support.

So why does Unicode continue to encode "precomposed" Latin
letters? The reason is that for some decorations, it's not sufficient
to say "apply the decoration" -- you also have to say where and
how to apply it. And there are many possible options. Therefore,
Unicode has identified certain combinations that will always be
encoded whenever they are part of an alphabet -- leaving the
use of the combining mark for non-standard purposes, like a one-off
use in a phonetics paper.

The list of combining marks that are treated that way (for the purposes
of Latin and similar scripts) is not currently documented in machine
readable form, but Unicode Technical Committee experts are quite
willing to entertain the needs of the larger community to identify
them via code point properties, so that IETF can use that property
to DISALLOW the combining marks.

Other combining marks can be identified as never (realistically)
leading to potential use in letters that are part of conceivable alphabets;
these can be identified and be added to the set of combining marks
for which NFC already prevents additional precomposed entities.

Any discussion leading to the adoption of such properties by IETF
would receive the necessary support from Unicode, and would
allow to cut down the problem significantly in the future.

The hamza cases may be harder in some ways.

>
> Again, I'm not advocating any of those alternatives, only trying
> to reinforce my point that these results are the consequences of
> decisions about coding (either due to a general, if complex, set
> of rules or to per character decisions) and not intrinsic
> properties of the grapheme clusters.

I digressed earlier away from a point by point reply. But the key item I
want to reiterate is that "identifying the abstract entity" that is to 
be encoded
is a matter that cannot be reduced to an algorithm; it cannot be reduced
to a pseudo algorithm (such as human-applied, but otherwise inflexible
principles). In its full generality (including all edge cases) it will 
always
boil down to judgment calls.
>
>> It's a
>> separate letter, even though, because it graphically floats,
>> Unicode
>> represents it as a combining character.  In the case of the
>> Fula language,
>> the same shape is used as a decoration on a letter, making a
>> new,
>> single entity, that just happens to look like a glottal stop
>> was placed after a beh.
> Given the above, and various other conversations, I believe the
> above statement about "separate letter" is true, but that the
> argument is ultimately circular.   In other words, Unicode has
> adopted a set of rules about when characters are distinct (rules
> that, sadly, are not completely described in the standard) and
> them applied them.

See above about rules.

Principles exist, in the form of "guiding principles", but they cannot be
absolute, because the complexity of human writing system is such that
the only way you can make inflexible principles is retroactively -- and
not only is Unicode still a work in progress, writing systems themselves
are never fully stable.

> Application of those rules (which I'm
> prepared to believe are reasonable for some general case and
> self-consistent) results in "combining character" in one place
> and "separate character" in another.  Application of a
> hypothetical different set of rules (including, purely as an
> example, my reading of the [now obviously incomplete] set of
> rules that actually appear in The Unicode Standards) might yield
> a different result, such as a precomposed character that
> decomposed or no precomposed character at all.

A good chunk of the problem is treatable "by rule" -- that is, Unicode
experts have agreed that it is reasonable to assign properties to some
subsets of combining marks that would identify their participation or
non-participation in forming sequences that are used as letters.
(non-participation means that any use of the combining mark today
is not considered a "letter" in the sense of "member of an alphabet").

There will be edge cases, hamza being one of them, where such simple
solutions appear not possible. Some code points, again hamza being an
example, could be explicitly given a property of having a problem in that
regard - if IETF would find that helpful.
>
>> There's no constraint, when it comes to Fula, for the writers
>> and font
>> designers (over long periods) to maintain the precise shape of
>> the
>> decoration on that letter. While they started out borrowing
>> the shape
>> of a hamza, who knows where this letter shape will end up --
>> it's not
>> constrained, I would argue, because the decoration isn't a
>> hamza (glottal stop) any longer.
>> ...
> And I suppose that, if we wait enough centuries and Fula evolves
> backwards from being written primarily in Latin script (after
> being written primarily in Arabic script until a few centuries
> ago), we will find out.
I'm not proposing that we should wait --- the point is more about that
things that can evolve on different paths are probably distinct entities,
and as character encoding is not a cataloging of shapes, but of entities,
then this considerations enters in the decision where to draw the boundary
between entities.
>   But, if things a going to be coded
> differently because the writing systems associated with
> different languages might evolve differently (as I agree they
> have over the centuries) and the desire is to future-proof
> things), then we should really code "ö" differently for Swedish
> than for German because, after all, Swedish writing might evolve
> in the direction of Danish or Norwegian so that "ö" would be
> replaced by the phonetically-similar "ø".     Or perhaps the
> evolution would work the other way and we should therefore code
> Norwegian and Danish separately lest "ø" in Norwegian evolve in
> the direction of "ö" while Danish remains unchanged.  The
> "borrowed letter" analogy applies there too because few, if any,
> of those languages were originally written in Latin script
> (whether we should permit, e.g., Runic in the DNS is of course a
> separate issue as is the likelihood of, e.g., Norwegian evolving
> back toward it).  I imagine those changes are probably unlikely,
> but they are less drastic than the Fula example which would
> require a complete reversal of the writing system's choice of
> basic script.

We have, in the history of Latin writing, nothing that might serve as a
strong precedent. Most orthographic reforms result in the adoption of
entirely new forms (like a-with-ring instead of aa in Danish).

The closest we come is a preference for different angles of
the accent when used in Polish vs. French.

The judgment call was to leave that to font designers.

A more problematic case is the distinction between comma below
and cedilla below on S and T, which are claimed (against available
evidence of actual use) to track with local preference.

The actual situation is that font designs are all over the map, which
is fine for the precomposed shapes. But for the combining sequence,
the two marks, comma below and cedilla below are distinct. That
presents a quandary, because now the name clearly indicates a
preferred shape and there is only one possible decomposition for the
precomposed shape. As a result, Unicode was forced, by the internal
logic of a universal set to provide the alternate shapes with alternate
decomposition - doing a huge disservice to users who now have
confusability and data migration issues (this went down before
NFC was frozen, so only the confusability issue remains, because
depending on the font, both comma below and cedilla below may
appear the same in the precomposed form).
>
> Unless Unicode is going to go back and review the decisions
> (which various stability rules now prohibit), I don't think this
> helps except for understanding whether there are actually
> predictable rules or whether code point allocation decisions are
> ultimately made by a small cluster of people sitting more or
> less in private and saying "that should be a separate,
> non-decomposing, code point because it feels that way to us and
> that other thing shouldn't because it doesn't" (or in the words
> of a notorious US judge "I know it when I see it ").   I still
> hope the situation is closer to the former and your explanations
> have helped me a lot in understanding why that may be true.

I think the bulk of all cases tends to fall in the predictable scenario, 
because
UTC strives quite hard, actually to follow precedent. There is an 
irreducible
set of cases where things come down to judgment. You see that more often
in code points in the symbols and punctuation area, because of the 
difficulty
of separating form and function there.

>
> But our bottom line is still (or again) that we need some sort
> of overlay or mechanism that will allow identifier comparison
> among strings with absolutely no language, phonetic, or other
> usage-context information (other than script) to work, present
> tense, to a first order approximation of what those writing the
> grapheme clusters or seeing them in isolation perceive.  How
> symbols are pronounced or affect pronunciation, how those
> symbols might evolve as the writing system evolves, whether they
> are used as word-forming letters in a script or as, e.g.,
> Mathematical notations, or what languages they are used with are
> simply not relevant to the issue.

See above.
>
> Either enough of the alternate coding sequences have to be
> disallowed to eliminate ambiguity because only one combination
> is left, the alternatives have to somehow compare equal, or we
> need to conclude that certain combinations are sufficiently
> unlikely to justify not worrying about.
Yes, that too.
> I imagine we might end
> up with a combination of those options for different cases.

I agree - this will not be a "one size fits all".

>    If
> the choice rules can be turned into properties that help in that
> process, that would be great.  If not, I think we may need to
> lose interest in them other than accepting that they will
> sometimes produce these distinctions in coding choices.

Properties. Definitely.

>> While it's possible to convey all of these distinctions by
>> invisible
>> codes (markup) they are not necessarily the most robust choice:
>> invisible codes and markup of any kind have a way of getting
>> separated from the letters they are supposed to affect.
> Of course, that is an argument against direction indicators in
> Bidi situations and a number of other things.

Correct -- and to the degree that they are not implemented, at some point
protocols can decide that they are safely prohibited. Unicode just recently
added a new set, one that could be used to isolate one bidi stretch from 
another.
Those look like they are useful ones for protocols to require when 
displaying
labels. Too early to see whether they will be widely adopted. (Looks 
like, though,
because they would allow plain text mapping of HTML directional markup).
>   I trust we all
> understand by now that this is all about tradeoffs, optimization
> for particular classes of usage, good choices about what to
> optimize for, and, as you have pointed out, sometimes the result
> that optimizing a coding system for one group of things may
> pessimize it for another.

Yep. As long as we understand that Unicode can't be optimized for IDNA,
we can then find ways to optimize IDNA for Unicode :)

A./


From nobody Thu Mar 19 15:37:36 2015
Return-Path: <Shawn.Steele@microsoft.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 079821A90E9 for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 15:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 LNNO9WU3Zgns for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 15:37:33 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0113.outbound.protection.outlook.com [207.46.100.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69F011A88F7 for <lucid@ietf.org>; Thu, 19 Mar 2015 15:37:33 -0700 (PDT)
Received: from BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) by BLUPR03MB549.namprd03.prod.outlook.com (10.141.76.17) with Microsoft SMTP Server (TLS) id 15.1.112.19; Thu, 19 Mar 2015 22:37:32 +0000
Received: from BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) by BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) with Microsoft SMTP Server (TLS) id 15.1.112.19; Thu, 19 Mar 2015 22:37:31 +0000
Received: from BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) by BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) with mapi id 15.01.0112.000; Thu, 19 Mar 2015 22:37:31 +0000
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "lucid@ietf.org" <lucid@ietf.org>
Thread-Topic: Communication.  
Thread-Index: AdBilGgqZ6ymGH/2S3K+k5B0kyebMQ==
Date: Thu, 19 Mar 2015 22:37:31 +0000
Message-ID: <BLUPR03MB1378075831687B9D8DCE68A382010@BLUPR03MB1378.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e8:ee31::2]
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Shawn.Steele@microsoft.com; 
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:; SRVR:BLUPR03MB1378; UriScan:; BCL:0; PCL:0; RULEID:; SRVR:BLUPR03MB549; 
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(979002)(6009001)(86362001)(2351001)(106356001)(2656002)(87936001)(107886001)(86612001)(229853001)(19580395003)(110136001)(97736003)(46102003)(99286002)(2501003)(92566002)(62966003)(68736005)(2900100001)(77156002)(450100001)(15975445007)(102836002)(122556002)(40100003)(33656002)(54356999)(76576001)(74316001)(50986999)(3826002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR03MB1378; H:BLUPR03MB1378.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
x-microsoft-antispam-prvs: <BLUPR03MB1378AFE24599C72F94EA0C4E82010@BLUPR03MB1378.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:BLUPR03MB1378; BCL:0; PCL:0; RULEID:;  SRVR:BLUPR03MB1378; 
x-forefront-prvs: 052017CAF1
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Mar 2015 22:37:31.0176 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB1378
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/QctWvZGACVxSlrYdDbvBO04Q-lY>
Subject: [Lucid] Communication.
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 22:37:35 -0000

I feel like I'm speaking a different language, or at least not worrying abo=
ut the same problems.

Andrew keeps asking, I've read https://datatracker.ietf.org/doc/draft-sulli=
van-lucid-prob-stmt/?include_text=3D1 several times now...

It looks like the PRECIS effort and Unicode aren't speaking the same langua=
ge.  Which is unfortunate, since PRECIS is attempting to suggest ways to us=
e Unicode. =20

I think Asmus said that well " Character encoding is not the process of num=
bering entities by shape. It's the process of numbering entities by their u=
nderlying identity in writing." =20

The PRECIS effort's language is all about characters are encoded by shape. =
 Unicodes language defined them as being encoded by their underlying identi=
ty.

-Shawn

PS: I love the sentence that starts off RFC 6885: "If a protocol expects to=
 compare two strings and is prepared only for those strings to be ASCII, th=
en using Unicode code points in those strings requires they be prepared som=
ehow."  That makes me want to go hide in a cave or something.


From nobody Thu Mar 19 15:59:28 2015
Return-Path: <peter@andyet.net>
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 9B5961AD066 for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 15:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 U-pmduqEe4Hz for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 15:59:25 -0700 (PDT)
Received: from mail-ie0-f180.google.com (mail-ie0-f180.google.com [209.85.223.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F9021A0118 for <lucid@ietf.org>; Thu, 19 Mar 2015 15:59:25 -0700 (PDT)
Received: by iecvj10 with SMTP id vj10so79820232iec.0 for <lucid@ietf.org>; Thu, 19 Mar 2015 15:59:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=spCm0S2nJrb96oXrJrCas7x9n1P8jSRLrhpTnx0/tpM=; b=GEmeZTnG1TVcGWjtrTlBlMUXz1hjLHxuRQYqQGGpNxVFXVoZI5/9YBiQjn0bizXFEK Sm4otj6sbYgOFcx6IWZhijCRNvzkjxWdsVi6KNuq09p5GoNDUGoxuWX0AmhNZ2B4PcvE h6sVCfzrsAhkVCNWZ882SFPYNUI0+EgXQmmOzarb3G0LuN/xl9Do1JAlR6uXl/2irWiF etL5nLR0DMtbGlJa5n6IGFtQ9CZDND7FQi/w8amPE1CJHWxSRygkUHNuEuE+oy4RYl/3 GZXWbRG0EIkgKObVU+mjIwun2/rYn2mXANZbkBOv7GcCTW322QDtHjLm/AoLOutL32xA R+Vw==
X-Gm-Message-State: ALoCoQng96rHkRScwjbEeFZqDl2cmdjGvQfmXlt7w39oioe/mX7Qu+xgS8muAmvoO1z8PNSYSG8q
X-Received: by 10.43.55.145 with SMTP id vy17mr520215icb.60.1426805964500; Thu, 19 Mar 2015 15:59:24 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by mx.google.com with ESMTPSA id mw1sm277874igb.18.2015.03.19.15.59.23 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Mar 2015 15:59:23 -0700 (PDT)
Message-ID: <550B54CA.1050202@andyet.net>
Date: Thu, 19 Mar 2015 16:59:22 -0600
From: Peter Saint-Andre - &yet <peter@andyet.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Shawn Steele <Shawn.Steele@microsoft.com>,  "lucid@ietf.org" <lucid@ietf.org>
References: <BLUPR03MB1378075831687B9D8DCE68A382010@BLUPR03MB1378.namprd03.prod.outlook.com>
In-Reply-To: <BLUPR03MB1378075831687B9D8DCE68A382010@BLUPR03MB1378.namprd03.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/90wBk6v4dUzvnfATAESRS-TUmVE>
Subject: Re: [Lucid] Communication.
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 22:59:26 -0000

On 3/19/15 4:37 PM, Shawn Steele wrote:
> I feel like I'm speaking a different language, or at least not
> worrying about the same problems.
>
> Andrew keeps asking, I've read
> https://datatracker.ietf.org/doc/draft-sullivan-lucid-prob-stmt/?include_text=1
> several times now...
>
> It looks like the PRECIS effort and Unicode aren't speaking the same
> language.  Which is unfortunate, since PRECIS is attempting to
> suggest ways to use Unicode.
>
> I think Asmus said that well " Character encoding is not the process
> of numbering entities by shape. It's the process of numbering
> entities by their underlying identity in writing."
>
> The PRECIS effort's language is all about characters are encoded by
> shape.  Unicodes language defined them as being encoded by their
> underlying identity.

Really? Now I need to ask if you have read draft-ietf-precis-framework:

http://datatracker.ietf.org/doc/draft-ietf-precis-framework/

Just as with IDNA2008, we structured PRECIS so that decisions are made 
algorithmically based on the properties of code points (which together 
constitute the code point's identity), not the shapes of glyphs.

Peter

-- 
Peter Saint-Andre
https://andyet.com/


From nobody Thu Mar 19 16:14:31 2015
Return-Path: <Shawn.Steele@microsoft.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 73B4C1A000A for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 16:14:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 4xUhYZ91HCEK for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 16:14:26 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0763.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:763]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0A381A000B for <lucid@ietf.org>; Thu, 19 Mar 2015 16:14:25 -0700 (PDT)
Received: from BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) by BLUPR03MB151.namprd03.prod.outlook.com (10.255.212.25) with Microsoft SMTP Server (TLS) id 15.1.106.15; Thu, 19 Mar 2015 23:14:07 +0000
Received: from BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) by BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) with Microsoft SMTP Server (TLS) id 15.1.112.19; Thu, 19 Mar 2015 23:14:06 +0000
Received: from BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) by BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) with mapi id 15.01.0112.000; Thu, 19 Mar 2015 23:14:06 +0000
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: Peter Saint-Andre - &yet <peter@andyet.net>, "lucid@ietf.org" <lucid@ietf.org>
Thread-Topic: [Lucid] Communication.
Thread-Index: AQHQYphZmKACuLeXr0GotId8E7ZSCp0kb3LA
Date: Thu, 19 Mar 2015 23:14:06 +0000
Message-ID: <BLUPR03MB1378243051BDD99E366CE40782010@BLUPR03MB1378.namprd03.prod.outlook.com>
References: <BLUPR03MB1378075831687B9D8DCE68A382010@BLUPR03MB1378.namprd03.prod.outlook.com> <550B54CA.1050202@andyet.net>
In-Reply-To: <550B54CA.1050202@andyet.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e8:ee31::2]
authentication-results: andyet.net; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:; SRVR:BLUPR03MB1378; UriScan:; BCL:0; PCL:0; RULEID:; SRVR:BLUPR03MB151; 
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(86362001)(2656002)(107886001)(86612001)(106116001)(2950100001)(46102003)(99286002)(2501003)(92566002)(62966003)(2900100001)(77156002)(102836002)(122556002)(40100003)(33656002)(76176999)(54356999)(76576001)(87936001)(74316001)(50986999)(3826002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR03MB1378; H:BLUPR03MB1378.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-microsoft-antispam-prvs: <BLUPR03MB1378E138F1A35EFADED9E5BB82010@BLUPR03MB1378.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:BLUPR03MB1378; BCL:0; PCL:0; RULEID:;  SRVR:BLUPR03MB1378; 
x-forefront-prvs: 052017CAF1
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Mar 2015 23:14:06.5358 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB1378
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/sViz4JgCbQ20LkuO29wlCdPI6oE>
Subject: Re: [Lucid] Communication.
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 23:14:30 -0000

> Just as with IDNA2008, we structured PRECIS so that decisions are made al=
gorithmically based on the properties of code points (which together consti=
tute the code point's identity), not the shapes of glyphs.

Yet this discussion is about whether that algorithm correctly handles the c=
haracters based on the shapes of the glyphs.


From nobody Thu Mar 19 16:15:58 2015
Return-Path: <peter@andyet.net>
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 6F7311A000D for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 16:15:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 a63w-5zfXLPq for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 16:15:55 -0700 (PDT)
Received: from mail-ig0-f173.google.com (mail-ig0-f173.google.com [209.85.213.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25DBC1A000B for <lucid@ietf.org>; Thu, 19 Mar 2015 16:15:55 -0700 (PDT)
Received: by igcau2 with SMTP id au2so3830899igc.0 for <lucid@ietf.org>; Thu, 19 Mar 2015 16:15:54 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XDNLA20TfiXC51XEELGkskxaijdiD4H6mWXoWwdChDA=; b=l+fGjaha/82qwTSmNbyxo+6nF59ubIDQ+Briyrd1TETLslPO0xKnozSJEfExdRs0kt IFzhtvjXLs5Ix/GQyPCULJvdla6zal+6lt2oV36JwfIgspw8ivKVc5p+svYum9iMojR3 AFx5Esm9NNdZ4RhS74RNkCnKLSmHJrIXscrWcUZKiz24Cz4F0cC0GRN3rKFd2ImBaxJD z9S7HAXAysY2WAo3IntzJ3lnpT/tADP6FT0fqtnyvR4whHVMHuS+DX8VkVUFqBXFyHLK bi5THxjdom2p9dUmSlEvBSJzL7BF8tusAO1M7mmBcoYSRefw3N+bA4Z4rLayKeyL0SSl XxRw==
X-Gm-Message-State: ALoCoQn4tZNJUD2DFyaW4GTDqiR/wyq2qFRB4Z45oiFmJ7NP7Ko0JHXPyYkPXFjklEdeFIvLRKA3
X-Received: by 10.50.78.9 with SMTP id x9mr20778142igw.44.1426806954515; Thu, 19 Mar 2015 16:15:54 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by mx.google.com with ESMTPSA id g195sm1880692iog.24.2015.03.19.16.15.53 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Mar 2015 16:15:53 -0700 (PDT)
Message-ID: <550B58A8.8030101@andyet.net>
Date: Thu, 19 Mar 2015 17:15:52 -0600
From: Peter Saint-Andre - &yet <peter@andyet.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Shawn Steele <Shawn.Steele@microsoft.com>,  "lucid@ietf.org" <lucid@ietf.org>
References: <BLUPR03MB1378075831687B9D8DCE68A382010@BLUPR03MB1378.namprd03.prod.outlook.com> <550B54CA.1050202@andyet.net> <BLUPR03MB1378243051BDD99E366CE40782010@BLUPR03MB1378.namprd03.prod.outlook.com>
In-Reply-To: <BLUPR03MB1378243051BDD99E366CE40782010@BLUPR03MB1378.namprd03.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/1-50ZiM_5GcKaW1ZctLZAHPyp5Q>
Subject: Re: [Lucid] Communication.
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 23:15:56 -0000

On 3/19/15 5:14 PM, Shawn Steele wrote:
>> Just as with IDNA2008, we structured PRECIS so that decisions are made algorithmically based on the properties of code points (which together constitute the code point's identity), not the shapes of glyphs.
>
> Yet this discussion is about whether that algorithm correctly handles the characters based on the shapes of the glyphs.

Humans aren't computers and they make decisions and get confused based 
on appearance. I don't see the two perspectives as mutually exclusive.

Peter

-- 
Peter Saint-Andre
https://andyet.com/


From nobody Thu Mar 19 16:49:39 2015
Return-Path: <Shawn.Steele@microsoft.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 B3FF71A00EF for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 16:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 Rgxhj1zA7hrL for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 16:49:37 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0744.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:744]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFC991A00EA for <lucid@ietf.org>; Thu, 19 Mar 2015 16:49:36 -0700 (PDT)
Received: from BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) by BLUPR03MB1379.namprd03.prod.outlook.com (25.163.81.13) with Microsoft SMTP Server (TLS) id 15.1.118.21; Thu, 19 Mar 2015 23:49:16 +0000
Received: from BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) by BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) with mapi id 15.01.0112.000; Thu, 19 Mar 2015 23:49:16 +0000
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: Peter Saint-Andre - &yet <peter@andyet.net>, "lucid@ietf.org" <lucid@ietf.org>
Thread-Topic: [Lucid] Communication.
Thread-Index: AQHQYphZmKACuLeXr0GotId8E7ZSCp0kb3LAgAAApgCAAAG90A==
Date: Thu, 19 Mar 2015 23:49:15 +0000
Message-ID: <BLUPR03MB137850E3E232AA345126D1D282010@BLUPR03MB1378.namprd03.prod.outlook.com>
References: <BLUPR03MB1378075831687B9D8DCE68A382010@BLUPR03MB1378.namprd03.prod.outlook.com> <550B54CA.1050202@andyet.net> <BLUPR03MB1378243051BDD99E366CE40782010@BLUPR03MB1378.namprd03.prod.outlook.com> <550B58A8.8030101@andyet.net>
In-Reply-To: <550B58A8.8030101@andyet.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e8:ee31::2]
authentication-results: andyet.net; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR03MB1379;
x-microsoft-antispam-prvs: <BLUPR03MB1379B4BC27C34E1412C6AD2082010@BLUPR03MB1379.namprd03.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(76176999)(50986999)(76576001)(54356999)(62966003)(77156002)(33656002)(102836002)(2501003)(2950100001)(2900100001)(99286002)(86612001)(86362001)(46102003)(40100003)(122556002)(106116001)(92566002)(74316001)(107886001)(87936001)(2656002)(3826002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR03MB1379; H:BLUPR03MB1378.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:BLUPR03MB1379; BCL:0; PCL:0; RULEID:;  SRVR:BLUPR03MB1379; 
x-forefront-prvs: 052017CAF1
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Mar 2015 23:49:15.9888 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB1379
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/0P3HI4WquXtcFbLmrzfwnwvEcSg>
Subject: Re: [Lucid] Communication.
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 23:49:38 -0000

PiBIdW1hbnMgYXJlbid0IGNvbXB1dGVycyBhbmQgdGhleSBtYWtlIGRlY2lzaW9ucyBhbmQgZ2V0
IGNvbmZ1c2VkIGJhc2VkIG9uIGFwcGVhcmFuY2UuIEkgZG9uJ3Qgc2VlIHRoZSB0d28gcGVyc3Bl
Y3RpdmVzIGFzIG11dHVhbGx5IGV4Y2x1c2l2ZS4NCg0KVGhleSdyZSBvcnRob2dvbmFsIHRob3Vn
aC4gIENsZWFybHkgc29tZSBjaGFyYWN0ZXJzIGFyZSBjb25mdXNhYmxlIHlldCBuZWNlc3Nhcnkg
KEN5cmlsbGljINCQIGFuZCBMYXRpbiBBKS4gIFRoZSBleGFtcGxlIGluIHRoZSBhcHBlbmRpeCBw
b2ludCBvdXQgb3RoZXIgY2FzZXMgd2hlcmUgbXVsdGlwbGUgY29kZSBwb2ludHMgYXJlIGNvbmZ1
c2FibGUuICBUaGUgb25seSByZWFsIGRpZmZlcmVuY2UgYmV0d2VlbiB0aGUgZXhhbXBsZXMgaW4g
UFJFQ0lTL2x1Y2lkJ3MgQXBwZW5kaXggQSBpcyBxdWVzdGlvbmluZyBvZiB0aGUgdmFsaWRpdHkg
b2YgdGhlIHNhbWUtc2NyaXB0IHNpbWlsYXJpdGllcyBpbiBBcHBlbmRpeCBBLCBiYXNlcyBwcmlt
YXJpbHkgaW4gdGhlIGFwcGVhcmFuY2UuDQoNCkkgZmluZCBszKYgYW5kIMS8IGZhaXJseSBkaWZm
aWN1bHQgdG8gZGlzdGluZ3Vpc2gsIHlldCB0aGUgZGlzdGluY3Rpb24gYmV0d2VlbiDImyBhbmQg
xaMgKGVhc2llciB0byB0ZWxsLCBidXQgdGhlIHNhbWUgY29tYmluaW5nIG1hcmtzKSBpcyBpbXBv
cnRhbnQgdG8gc29tZS4gICBTaG91bGQgbMymIGFuZCDEvCBiZSBmb3JiaWRkZW4gb3IgdW5pZmll
ZCBiZWNhdXNlIEkgY2FuJ3Qgc2VlIGEgZGlzdGluY3Rpb24gYW5kIEkgaGF2ZSBubyBjbHVlIGhv
dyBwZW9wbGUgd291bGQgdXNlIHRoZW0/ICBszKYgYW5kIMS8IGFyZW4ndCBpbiBBcHBlbmRpeCBB
IChhcmUgdGhleSBzdXBwb3NlZCB0byBiZT8pICANCg0KRm9yIHRoYXQgbWF0dGVyLCBJIGhhdmUg
YSBoYXJkIHRpbWUgc2VlaW5nIGEgZGlmZmVyZW5jZSBiZXR3ZWVuIGkgYW5kIGnMhywgaG93ZXZl
ciBJRE5BIG1ha2VzIHBhcnRpY3VsYXIgdXNlIG9mIHRoZSBvZGQgY29tYmluYXRpb24gaW4gdGhl
IGNhc2luZy9ub3JtYWxpemF0aW9uIHJ1bGVzLiAgVGhvc2UgYXJlbid0IGluIEFwcGVuZGl4IEEu
DQoNClNob3VsZCBpIGFuZCBpzIcgYmUgaW4gQXBwZW5kaXggQT8gIFdoYXQgYWJvdXQgbMymIGFu
ZCDEvD8gIElmIG5vdCwgY2FuIHNvbWVvbmUgZXhwbGFpbiB3aHkgdGhleSdyZSBzcGVjaWFsPw0K
DQotU2hhd24NCg0KDQo=


From nobody Thu Mar 19 16:52:50 2015
Return-Path: <asmusf@ix.netcom.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 A9BC01A0111 for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 16:52:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 m63dRgwblSxu for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 16:52:48 -0700 (PDT)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by ietfa.amsl.com (Postfix) with ESMTP id E55761A0141 for <lucid@ietf.org>; Thu, 19 Mar 2015 16:52:47 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=jjdFpO8NSOvZOzkzAmSDkrMFiVyOfsxzEdCknrKT+Y/bHIx2pptFOZpqBb8hW6S9; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP;
Received: from [72.244.206.133] (helo=[192.168.0.107]) by elasmtp-curtail.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <asmusf@ix.netcom.com>) id 1YYkF4-0006fw-Te; Thu, 19 Mar 2015 19:52:47 -0400
Message-ID: <550B6150.20705@ix.netcom.com>
Date: Thu, 19 Mar 2015 16:52:48 -0700
From: Asmus Freytag <asmusf@ix.netcom.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Peter Saint-Andre - &yet <peter@andyet.net>,  Shawn Steele <Shawn.Steele@microsoft.com>, lucid@ietf.org
References: <BLUPR03MB1378075831687B9D8DCE68A382010@BLUPR03MB1378.namprd03.prod.outlook.com> <550B54CA.1050202@andyet.net>
In-Reply-To: <550B54CA.1050202@andyet.net>
Content-Type: multipart/alternative; boundary="------------090204010400000906060805"
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2b65b6112f891153763f60484aeba024d329077a82ed40bc1350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 72.244.206.133
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/Up4NRWRwAyerr-LQitZg37cMB28>
Subject: Re: [Lucid] Communication.
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 23:52:49 -0000

This is a multi-part message in MIME format.
--------------090204010400000906060805
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 3/19/2015 3:59 PM, Peter Saint-Andre - &yet wrote:
> On 3/19/15 4:37 PM, Shawn Steele wrote:
>> I think Asmus said that well " Character encoding is not the process
>> of numbering entities by shape. It's the process of numbering
>> entities by their underlying identity in writing."
>>
>> The PRECIS effort's language is all about characters are encoded by
>> shape.  Unicodes language defined them as being encoded by their
>> underlying identity.
>
>
> Just as with IDNA2008, we structured PRECIS so that decisions are
> made algorithmically based on the properties of code points (which
> together constitute the code point's identity), not the shapes of glyphs.
>
> Peter
>
Peter,

nobody argues that IDNA or PRECIS are not based on
character properties.  They most clearly are.

What I was trying to highlight is the fact that there may be
a misunderstanding of how Unicode (and pretty much all
character encoding, except for, the most trivial cases)
is conceived.

By basing your specification on properties, you can
ensure uniqueness of underling encoded identity,
but, unless the particular properties happen to take into
account information on shape, you won't get uniqueness
in shape.

I'm all for helping IDNA and PRECIS by having Unicode
provide some additional properties that can help address
the case of "apparent identity" where the shapes agree,
but the identity actually is distinct.

A./

--------------090204010400000906060805
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 3/19/2015 3:59 PM, Peter Saint-Andre
      - &amp;yet wrote:<br>
    </div>
    <blockquote cite="mid:550B54CA.1050202@andyet.net" type="cite">On
      3/19/15 4:37 PM, Shawn Steele wrote:
      <br>
      <blockquote type="cite">I think Asmus said that well " Character
        encoding is not the process
        <br>
        of numbering entities by shape. It's the process of numbering
        <br>
        entities by their underlying identity in writing."
        <br>
        <br>
        The PRECIS effort's language is all about characters are encoded
        by
        <br>
        shape.  Unicodes language defined them as being encoded by their
        <br>
        underlying identity.
        <br>
      </blockquote>
      <br>
      <br>
      Just as with IDNA2008, we structured PRECIS so that decisions are
      <br>
      made algorithmically based on the properties of code points (which
      <br>
      together constitute the code point's identity), not the shapes of
      glyphs.
      <br>
      <br>
      Peter
      <br>
      <br>
    </blockquote>
    <font face="Candara">Peter,<br>
      <br>
      nobody argues that IDNA or PRECIS are not based on <br>
      character properties.  They most clearly are.<br>
      <br>
      What I was trying to highlight is the fact that there may be<br>
      a misunderstanding of how Unicode (and pretty much all <br>
      character encoding, except for, the most trivial cases) <br>
      is conceived.<br>
      <br>
      By basing your specification on properties, you can<br>
      ensure uniqueness of underling encoded identity,<br>
      but, unless the particular properties happen to take into<br>
      account information on shape, you won't get uniqueness<br>
      in shape.<br>
      <br>
      I'm all for helping IDNA and PRECIS by having Unicode<br>
      provide some additional properties that can help address <br>
      the case of "apparent identity" where the shapes agree, <br>
      but the identity actually is distinct.<br>
      <br>
      A./<br>
    </font>
  </body>
</html>

--------------090204010400000906060805--


From nobody Thu Mar 19 16:53:01 2015
Return-Path: <Shawn.Steele@microsoft.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 93CED1A0151 for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 16:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 IA82q8W1y3wB for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 16:52:58 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0767.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:767]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E143D1A0111 for <lucid@ietf.org>; Thu, 19 Mar 2015 16:52:56 -0700 (PDT)
Received: from BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) by BLUPR03MB261.namprd03.prod.outlook.com (10.255.213.12) with Microsoft SMTP Server (TLS) id 15.1.125.14; Thu, 19 Mar 2015 23:52:37 +0000
Received: from BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) by BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) with Microsoft SMTP Server (TLS) id 15.1.112.19; Thu, 19 Mar 2015 23:52:35 +0000
Received: from BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) by BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) with mapi id 15.01.0112.000; Thu, 19 Mar 2015 23:52:35 +0000
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: Peter Saint-Andre - &yet <peter@andyet.net>, "lucid@ietf.org" <lucid@ietf.org>
Thread-Topic: [Lucid] Communication.
Thread-Index: AQHQYphZmKACuLeXr0GotId8E7ZSCp0kb3LAgAAApgCAAAG90IAAB+DQ
Date: Thu, 19 Mar 2015 23:52:35 +0000
Message-ID: <BLUPR03MB1378A841576A4805708C56E282010@BLUPR03MB1378.namprd03.prod.outlook.com>
References: <BLUPR03MB1378075831687B9D8DCE68A382010@BLUPR03MB1378.namprd03.prod.outlook.com> <550B54CA.1050202@andyet.net> <BLUPR03MB1378243051BDD99E366CE40782010@BLUPR03MB1378.namprd03.prod.outlook.com> <550B58A8.8030101@andyet.net> 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e8:ee31::2]
authentication-results: andyet.net; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:; SRVR:BLUPR03MB1378; UriScan:; BCL:0; PCL:0; RULEID:; SRVR:BLUPR03MB261; 
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(377454003)(13464003)(122556002)(102836002)(33656002)(40100003)(76576001)(54356999)(76176999)(74316001)(50986999)(87936001)(2656002)(107886001)(106116001)(19580395003)(19580405001)(86612001)(86362001)(2900100001)(62966003)(77156002)(46102003)(92566002)(99286002)(2501003)(3826002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR03MB1378; H:BLUPR03MB1378.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-microsoft-antispam-prvs: <BLUPR03MB137809842857A66B2A2E5F0182010@BLUPR03MB1378.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:BLUPR03MB1378; BCL:0; PCL:0; RULEID:;  SRVR:BLUPR03MB1378; 
x-forefront-prvs: 052017CAF1
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Mar 2015 23:52:35.4010 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB1378
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/Ivor5_6WB_Q3QhnHle4lSkS8qvY>
Subject: Re: [Lucid] Communication.
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 23:52:59 -0000

U29ycnksIEkgd2FzIGEgbGl0dGxlIHZhZ3VlIHRoZXJlLiAgSUROQSB3ZW50IHRvIHNwZWNpYWwg
ZWZmb3J0IHRvIG1ha2UgaSBhbmQgaSBoYXBwZW4gYnkgbWFwcGluZyBJzIcgdG8gacyHLiAgU28g
aXQgc2VlbXMgcGVjdWxpYXIgdG8gbWUgdG8gcXVlc3Rpb24gaXQgbm93Lg0KDQotU2hhd24NCg0K
LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IFNoYXduIFN0ZWVsZSANClNlbnQ6IFRo
dXJzZGF5LCBNYXJjaCAxOSwgMjAxNSA0OjQ5IFBNDQpUbzogJ1BldGVyIFNhaW50LUFuZHJlIC0g
JnlldCc7IGx1Y2lkQGlldGYub3JnDQpTdWJqZWN0OiBSRTogW0x1Y2lkXSBDb21tdW5pY2F0aW9u
Lg0KDQo+IEh1bWFucyBhcmVuJ3QgY29tcHV0ZXJzIGFuZCB0aGV5IG1ha2UgZGVjaXNpb25zIGFu
ZCBnZXQgY29uZnVzZWQgYmFzZWQgb24gYXBwZWFyYW5jZS4gSSBkb24ndCBzZWUgdGhlIHR3byBw
ZXJzcGVjdGl2ZXMgYXMgbXV0dWFsbHkgZXhjbHVzaXZlLg0KDQpUaGV5J3JlIG9ydGhvZ29uYWwg
dGhvdWdoLiAgQ2xlYXJseSBzb21lIGNoYXJhY3RlcnMgYXJlIGNvbmZ1c2FibGUgeWV0IG5lY2Vz
c2FyeSAoQ3lyaWxsaWMg0JAgYW5kIExhdGluIEEpLiAgVGhlIGV4YW1wbGUgaW4gdGhlIGFwcGVu
ZGl4IHBvaW50IG91dCBvdGhlciBjYXNlcyB3aGVyZSBtdWx0aXBsZSBjb2RlIHBvaW50cyBhcmUg
Y29uZnVzYWJsZS4gIFRoZSBvbmx5IHJlYWwgZGlmZmVyZW5jZSBiZXR3ZWVuIHRoZSBleGFtcGxl
cyBpbiBQUkVDSVMvbHVjaWQncyBBcHBlbmRpeCBBIGlzIHF1ZXN0aW9uaW5nIG9mIHRoZSB2YWxp
ZGl0eSBvZiB0aGUgc2FtZS1zY3JpcHQgc2ltaWxhcml0aWVzIGluIEFwcGVuZGl4IEEsIGJhc2Vz
IHByaW1hcmlseSBpbiB0aGUgYXBwZWFyYW5jZS4NCg0KSSBmaW5kIGzMpiBhbmQgxLwgZmFpcmx5
IGRpZmZpY3VsdCB0byBkaXN0aW5ndWlzaCwgeWV0IHRoZSBkaXN0aW5jdGlvbiBiZXR3ZWVuIMib
IGFuZCDFoyAoZWFzaWVyIHRvIHRlbGwsIGJ1dCB0aGUgc2FtZSBjb21iaW5pbmcgbWFya3MpIGlz
IGltcG9ydGFudCB0byBzb21lLiAgIFNob3VsZCBszKYgYW5kIMS8IGJlIGZvcmJpZGRlbiBvciB1
bmlmaWVkIGJlY2F1c2UgSSBjYW4ndCBzZWUgYSBkaXN0aW5jdGlvbiBhbmQgSSBoYXZlIG5vIGNs
dWUgaG93IHBlb3BsZSB3b3VsZCB1c2UgdGhlbT8gIGzMpiBhbmQgxLwgYXJlbid0IGluIEFwcGVu
ZGl4IEEgKGFyZSB0aGV5IHN1cHBvc2VkIHRvIGJlPykgIA0KDQpGb3IgdGhhdCBtYXR0ZXIsIEkg
aGF2ZSBhIGhhcmQgdGltZSBzZWVpbmcgYSBkaWZmZXJlbmNlIGJldHdlZW4gaSBhbmQgacyHLCBo
b3dldmVyIElETkEgbWFrZXMgcGFydGljdWxhciB1c2Ugb2YgdGhlIG9kZCBjb21iaW5hdGlvbiBp
biB0aGUgY2FzaW5nL25vcm1hbGl6YXRpb24gcnVsZXMuICBUaG9zZSBhcmVuJ3QgaW4gQXBwZW5k
aXggQS4NCg0KU2hvdWxkIGkgYW5kIGnMhyBiZSBpbiBBcHBlbmRpeCBBPyAgV2hhdCBhYm91dCBs
zKYgYW5kIMS8PyAgSWYgbm90LCBjYW4gc29tZW9uZSBleHBsYWluIHdoeSB0aGV5J3JlIHNwZWNp
YWw/DQoNCi1TaGF3bg0KDQoNCg==


From nobody Thu Mar 19 17:02:21 2015
Return-Path: <Shawn.Steele@microsoft.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 8C06F1A01A8 for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 17:02:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.901
X-Spam-Level: 
X-Spam-Status: No, score=-3.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 JLsSvQeRu9Du for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 17:02:18 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0798.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::798]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D28F81A0167 for <lucid@ietf.org>; Thu, 19 Mar 2015 17:02:17 -0700 (PDT)
Received: from BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) by BLUPR03MB1380.namprd03.prod.outlook.com (25.163.81.139) with Microsoft SMTP Server (TLS) id 15.1.112.19; Fri, 20 Mar 2015 00:01:58 +0000
Received: from BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) by BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) with mapi id 15.01.0112.000; Fri, 20 Mar 2015 00:01:58 +0000
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "lucid@ietf.org" <lucid@ietf.org>
Thread-Topic: Please clarify the i's in Appendix A
Thread-Index: AdBin+ZuKs3zpeT0SS+0IvxOVk8XSg==
Date: Fri, 20 Mar 2015 00:01:58 +0000
Message-ID: <BLUPR03MB1378FED1AEB1C756C5D058C2820E0@BLUPR03MB1378.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e8:ee31::2]
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR03MB1380;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(86362001)(19300405004)(107886001)(2351001)(110136001)(99286002)(19625215002)(33656002)(46102003)(19617315012)(229853001)(122556002)(40100003)(19580395003)(92566002)(16236675004)(86612001)(15975445007)(102836002)(2900100001)(77156002)(62966003)(450100001)(74316001)(50986999)(2656002)(2501003)(87936001)(54356999)(76576001)(16601075003)(3826002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR03MB1380; H:BLUPR03MB1378.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-microsoft-antispam-prvs: <BLUPR03MB1380D521D9F04601BB46786E820E0@BLUPR03MB1380.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:BLUPR03MB1380; BCL:0; PCL:0; RULEID:;  SRVR:BLUPR03MB1380; 
x-forefront-prvs: 05214FD68E
Content-Type: multipart/alternative; boundary="_000_BLUPR03MB1378FED1AEB1C756C5D058C2820E0BLUPR03MB1378namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Mar 2015 00:01:58.0270 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB1380
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/i2jqttz-eS3UG9Ydehh45LeWdqA>
Subject: [Lucid] Please clarify the i's in Appendix A
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: Fri, 20 Mar 2015 00:02:20 -0000

--_000_BLUPR03MB1378FED1AEB1C756C5D058C2820E0BLUPR03MB1378namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

aHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtc3VsbGl2YW4tbHVjaWQtcHJv
Yi1zdG10Lz9pbmNsdWRlX3RleHQ9MSB0aGF0IHNlZW1zIG9kZCB0byBtZSwgd2hlcmUgZG9lcyBV
bmljb2RlIGRvY3VtZW50IHRoaXM/DQoNCiAgIFUrMDY5IHZzIFx1JzAwNjknXHUnMDMwNycgIExB
VElOIFNNQUxMIExFVFRFUiBJIGZvbGxvd2VkIGJ5IENPTUJJTklORw0KICAgICAgRE9UIEFCT1ZF
IGJ5IGRlZmluaXRpb24sIHJlbmRlcnMgZXhhY3RseSB0aGUgc2FtZSBhcyBMQVRJTiBTTUFMTA0K
ICAgICAgTEVUVEVSIEkgYnkgaXRzZWxmIGFuZCBkb2VzIHNvIGluIHByYWN0aWNlIGZvciBhbnkg
Z29vZCBmb250LiAgVGhlDQogICAgICBzYW1lIHdvdWxkIGJlIHRydWUgaWYgImkiIHdhcyByZXBs
YWNlZCB3aXRoIGFueSBvZiB0aGUgb3RoZXINCiAgICAgIFNvZnRfRG90dGVkIGNoYXJhY3RlcnMg
ZGVmaW5lZCBpbiBVbmljb2RlLiAgVGhlIGNoYXJhY3RlciBzZXF1ZW5jZQ0KICAgICAgXHUnMDA2
OSdcdScwMzA3JyAoZm9sbG93ZWQgYnkgbm8gb3RoZXIgY29tYmluaW5nIG1hcmspIGlzDQogICAg
ICByZXBvcnRlZGx5IHJhdGhlciBjb21tb24gb24gdGhlIEludGVybmV0LiAgQmVjYXVzZSBiYXNl
IGNoYXJhY3Rlcg0KICAgICAgYW5kIHN0YW5kLWFsb25lIGNvZGUgcG9pbnQgYXJlIHRoZSBzYW1l
IGluIHRoaXMgY2FzZSwgYW5kIHRoZSBjb2RlDQogICAgICBwb2ludHMgYWZmZWN0ZWQgaGF2ZSB0
aGUgU29mdF9Eb3R0ZWQgcHJvcGVydHkgYWxyZWFkeSwgdGhpcyBjb3VsZA0KICAgICAgYmUgbWl0
aWdhdGVkIHNlcGFyYXRlbHkgdmlhIGEgY29udGV4dCBydWxlIGFmZmVjdGluZyBVKzAzMDcuDQoN
CklETkEgbWFrZXMgdGhpcyB3b3JzZSBieSBtYXBwaW5nIMSwIFUrMDEzMCB0byBVKzAwNjkgKyBV
KzAzMDcsIGFwcGFyZW50bHkgdG8gZ2V0IGEgdmlzdWFsIGVmZmVjdC4gIEl0IHNlZW1zIHBlY3Vs
aWFyIHRvIG1lIHRoYXQgdGhlcmUgd291bGQgbmVlZCB0byBiZSBhbiBleGNlcHRpb24gdG8gdGhl
IGV4aXN0aW5nIGV4Y2VwdGlvbi4NCg0KSeKAmWQgbGlrZSBhbiBhdHRyaWJ1dGlvbiBmb3IgdGhl
IHJlbWFyayDigJxcdScwMDY5J1x1JzAzMDcnIChmb2xsb3dlZCBieSBubyBvdGhlciBjb21iaW5p
bmcgbWFyaykgaXMgcmVwb3J0ZWRseSByYXRoZXIgY29tbW9uIG9uIHRoZSBJbnRlcm5ldOKAnS4g
IEnigJlkIGFsc28gYmUgaW50ZXJlc3RlZCBpbiB3aGF0IGNvbnRleHRzLiAgSeKAmWQgYWxzbyBi
ZSBjdXJpb3VzIGFib3V0IGhvdyB0aG9zZSBjYW1lIGludG8gZXhpc3RlbmNlLiAgKE5GRCBmb2xs
b3dlZCBieSBsb3dlciBjYXNlPykNCg0KLVNoYXduDQoNCu+jou+jkO+jp++jmyDvo6Lvo6Pvo5fv
o5Tvo5kNCmh0dHA6Ly9ibG9ncy5tc2RuLmNvbS9zaGF3bnN0ZQ0KaHR0cDovL0wzLUcwLmJsb2dz
cG90LmNvbQ0KDQo=

--_000_BLUPR03MB1378FED1AEB1C756C5D058C2820E0BLUPR03MB1378namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpwSXFhRDsNCglwYW5vc2UtMToyIDAgNiAz
IDAgMCAwIDAgMCAwO30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGku
TXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTou
MDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMt
c2VyaWY7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJY29sb3I6IzA1NjNDMTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlz
aXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7
DQoJY29sb3I6Izk1NEY3MjsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnNwYW4uRW1h
aWxTdHlsZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxp
YnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgN
Cgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMt
c2VyaWY7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUt
dHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xv
cjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTIwDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFs
LWNvbXBvc2U7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2lu
ZG93dGV4dDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsN
Cglmb250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDEx
LjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9u
MQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48
eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwv
eG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQg
djpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hh
cGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIg
bGluaz0iIzA1NjNDMSIgdmxpbms9IiM5NTRGNzIiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24x
Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJsaW5lLWhlaWdodDoxNC40cHQiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1
b3Q7Ij48YSBocmVmPSJodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1zdWxs
aXZhbi1sdWNpZC1wcm9iLXN0bXQvP2luY2x1ZGVfdGV4dD0xIj5odHRwczovL2RhdGF0cmFja2Vy
LmlldGYub3JnL2RvYy9kcmFmdC1zdWxsaXZhbi1sdWNpZC1wcm9iLXN0bXQvP2luY2x1ZGVfdGV4
dD0xPC9hPg0KIHRoYXQgc2VlbXMgb2RkIHRvIG1lLCB3aGVyZSBkb2VzIFVuaWNvZGUgZG9jdW1l
bnQgdGhpcz88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibGluZS1oZWlnaHQ6MTQuNHB0Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImxpbmUtaGVpZ2h0OjE0LjRwdCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDsiPiZuYnNwOyZuYnNwOyBVJiM0MzswNjkgdnMgXHUnMDA2OSdcdScwMzA3JyZuYnNwOyBM
QVRJTiBTTUFMTCBMRVRURVIgSSBmb2xsb3dlZCBieSBDT01CSU5JTkc8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibGluZS1oZWlnaHQ6MTQuNHB0Ij48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5l
dyZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IERPVCBBQk9WRSBieSBkZWZp
bml0aW9uLCByZW5kZXJzIGV4YWN0bHkgdGhlIHNhbWUgYXMgTEFUSU4gU01BTEw8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibGluZS1oZWlnaHQ6MTQu
NHB0Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3Vy
aWVyIE5ldyZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IExFVFRFUiBJIGJ5
IGl0c2VsZiBhbmQgZG9lcyBzbyBpbiBwcmFjdGljZSBmb3IgYW55IGdvb2QgZm9udC4mbmJzcDsg
VGhlPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Imxp
bmUtaGVpZ2h0OjE0LjRwdCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyBzYW1lIHdvdWxkIGJlIHRydWUgaWYgJnF1b3Q7aSZxdW90OyB3YXMgcmVwbGFjZWQgd2l0aCBh
bnkgb2YgdGhlIG90aGVyPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9ImxpbmUtaGVpZ2h0OjE0LjRwdCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyBTb2Z0X0RvdHRlZCBjaGFyYWN0ZXJzIGRlZmluZWQgaW4gVW5pY29kZS4m
bmJzcDsgVGhlIGNoYXJhY3RlciBzZXF1ZW5jZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJsaW5lLWhlaWdodDoxNC40cHQiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij4mbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgXHUnMDA2OSdcdScwMzA3JyAoZm9sbG93ZWQgYnkg
bm8gb3RoZXIgY29tYmluaW5nIG1hcmspIGlzPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9ImxpbmUtaGVpZ2h0OjE0LjRwdCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyByZXBvcnRlZGx5IHJhdGhlciBjb21tb24gb24gdGhl
IEludGVybmV0LiZuYnNwOyBCZWNhdXNlIGJhc2UgY2hhcmFjdGVyPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9ImxpbmUtaGVpZ2h0OjE0LjRwdCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBhbmQgc3RhbmQtYWxvbmUgY29k
ZSBwb2ludCBhcmUgdGhlIHNhbWUgaW4gdGhpcyBjYXNlLCBhbmQgdGhlIGNvZGU8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibGluZS1oZWlnaHQ6MTQu
NHB0Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3Vy
aWVyIE5ldyZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHBvaW50cyBhZmZl
Y3RlZCBoYXZlIHRoZSBTb2Z0X0RvdHRlZCBwcm9wZXJ0eSBhbHJlYWR5LCB0aGlzIGNvdWxkPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBiZSBtaXRpZ2F0ZWQgc2VwYXJhdGVseSB2aWEgYSBj
b250ZXh0IHJ1bGUgYWZmZWN0aW5nIFUmIzQzOzAzMDcuPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+SUROQSBtYWtlcyB0aGlzIHdvcnNl
IGJ5IG1hcHBpbmcgxLAgVSYjNDM7MDEzMCB0byBVJiM0MzswMDY5ICYjNDM7IFUmIzQzOzAzMDcs
IGFwcGFyZW50bHkgdG8gZ2V0IGEgdmlzdWFsIGVmZmVjdC4mbmJzcDsgSXQgc2VlbXMgcGVjdWxp
YXIgdG8gbWUgdGhhdCB0aGVyZSB3b3VsZCBuZWVkIHRvIGJlIGFuIGV4Y2VwdGlvbiB0byB0aGUg
ZXhpc3RpbmcgZXhjZXB0aW9uLiAmbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMx
RjQ5N0QiPknigJlkIGxpa2UgYW4gYXR0cmlidXRpb24gZm9yIHRoZSByZW1hcmsg4oCcXHUnMDA2
OSdcdScwMzA3JyAoZm9sbG93ZWQgYnkgbm8gb3RoZXIgY29tYmluaW5nIG1hcmspIGlzIHJlcG9y
dGVkbHkgcmF0aGVyIGNvbW1vbiBvbiB0aGUgSW50ZXJuZXTigJ0uJm5ic3A7IEnigJlkIGFsc28g
YmUgaW50ZXJlc3RlZCBpbiB3aGF0IGNvbnRleHRzLiZuYnNwOyBJ4oCZZCBhbHNvIGJlIGN1cmlv
dXMgYWJvdXQNCiBob3cgdGhvc2UgY2FtZSBpbnRvIGV4aXN0ZW5jZS4mbmJzcDsgKE5GRCBmb2xs
b3dlZCBieSBsb3dlciBjYXNlPyk8L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQiPi1TaGF3bjxicj4NCjxicj4NCjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseTpwSXFhRCI+76Oi76OQ76On76ObIO+jou+jo++jl++jlO+jmTwvc3Bhbj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+PGJyPg0KPGEgaHJlZj0iaHR0cDovL2Jsb2dz
Lm1zZG4uY29tL3NoYXduc3RlIj48c3BhbiBzdHlsZT0iY29sb3I6Ymx1ZSI+aHR0cDovL2Jsb2dz
Lm1zZG4uY29tL3NoYXduc3RlPC9zcGFuPjwvYT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+PGEgaHJlZj0i
aHR0cDovL0wzLUcwLmJsb2dzcG90LmNvbSI+aHR0cDovL0wzLUcwLmJsb2dzcG90LmNvbTwvYT4N
Cjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_BLUPR03MB1378FED1AEB1C756C5D058C2820E0BLUPR03MB1378namp_--


From nobody Thu Mar 19 22:55:12 2015
Return-Path: <paf@frobbit.se>
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 73B111B2C43 for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 22:55:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.961
X-Spam-Level: 
X-Spam-Status: No, score=-1.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 sZSIGPoEjTqv for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 22:55:10 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38F1E1B2C1B for <lucid@ietf.org>; Thu, 19 Mar 2015 22:55:10 -0700 (PDT)
Received: from [IPv6:2a02:80:3ffc::6587:a472:46cb:ee39] (unknown [IPv6:2a02:80:3ffc:0:6587:a472:46cb:ee39]) by mail.frobbit.se (Postfix) with ESMTPSA id B46FE1FF18; Fri, 20 Mar 2015 06:55:06 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_54A16BDF-6696-4A9A-BDCC-B5D30A9995B2"; protocol="application/pgp-signature"; micalg=pgp-sha1
X-Pgp-Agent: GPGMail 2.5b6
From: =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>
In-Reply-To: <BLUPR03MB1378FED1AEB1C756C5D058C2820E0@BLUPR03MB1378.namprd03.prod.outlook.com>
Date: Fri, 20 Mar 2015 06:55:06 +0100
Message-Id: <184B22C8-336A-4687-8FAD-E9A4942C6CD8@frobbit.se>
References: <BLUPR03MB1378FED1AEB1C756C5D058C2820E0@BLUPR03MB1378.namprd03.prod.outlook.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/3T-ZWCRQiN1H8Ag2eDcGjsLm2Tw>
Cc: "lucid@ietf.org" <lucid@ietf.org>
Subject: Re: [Lucid] Please clarify the i's in Appendix A
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: Fri, 20 Mar 2015 05:55:11 -0000

--Apple-Mail=_54A16BDF-6696-4A9A-BDCC-B5D30A9995B2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 20 mar 2015, at 01:01, Shawn Steele <Shawn.Steele@microsoft.com> =
wrote:
>=20
> IDNA makes this worse by mapping =C4=B0 U+0130 to U+0069 + U+0307, =
apparently to get a visual effect.  It seems peculiar to me that there =
would need to be an exception to the existing exception.

Can you please clarify?

IDNA do not include mapping, so I presume you mean "IDNA would make this =
worse IF it mapped..."?

   Patrik


--Apple-Mail=_54A16BDF-6696-4A9A-BDCC-B5D30A9995B2
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFVC7Y6rMabGguI180RAioHAJ9foL3ezVR+K1eXBSTDVScfV89clACaAj9J
n8Fg38Gjl5pqdpFfFcYPJgM=
=cvrE
-----END PGP SIGNATURE-----

--Apple-Mail=_54A16BDF-6696-4A9A-BDCC-B5D30A9995B2--


From nobody Thu Mar 19 23:51:57 2015
Return-Path: <Shawn.Steele@microsoft.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 10A451B2C51 for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 23:51:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level: 
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 viuJNYXHY1V7 for <lucid@ietfa.amsl.com>; Thu, 19 Mar 2015 23:51:54 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0139.outbound.protection.outlook.com [65.55.169.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A00A21B2C50 for <lucid@ietf.org>; Thu, 19 Mar 2015 23:51:54 -0700 (PDT)
Received: from BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) by BLUPR03MB1377.namprd03.prod.outlook.com (25.163.81.11) with Microsoft SMTP Server (TLS) id 15.1.118.21; Fri, 20 Mar 2015 06:51:52 +0000
Received: from BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) by BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) with mapi id 15.01.0112.000; Fri, 20 Mar 2015 06:51:52 +0000
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: =?utf-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
Thread-Topic: [Lucid] Please clarify the i's in Appendix A
Thread-Index: AdBin+ZuKs3zpeT0SS+0IvxOVk8XSgAMoPgAAAEwJGA=
Date: Fri, 20 Mar 2015 06:51:52 +0000
Message-ID: <BLUPR03MB1378664A6F96AEBBC2E27EE4820E0@BLUPR03MB1378.namprd03.prod.outlook.com>
References: <BLUPR03MB1378FED1AEB1C756C5D058C2820E0@BLUPR03MB1378.namprd03.prod.outlook.com> <184B22C8-336A-4687-8FAD-E9A4942C6CD8@frobbit.se>
In-Reply-To: <184B22C8-336A-4687-8FAD-E9A4942C6CD8@frobbit.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [50.34.94.236]
authentication-results: frobbit.se; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR03MB1377;
x-microsoft-antispam-prvs: <BLUPR03MB1377BD1D85FF5F3CDCCBBB15820E0@BLUPR03MB1377.namprd03.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(377454003)(13464003)(51704005)(62966003)(99286002)(15975445007)(77156002)(102836002)(74316001)(110136001)(86362001)(76576001)(2656002)(86612001)(87936001)(54356999)(50986999)(122556002)(2950100001)(92566002)(19580405001)(19580395003)(40100003)(66066001)(33656002)(46102003)(2900100001); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR03MB1377; H:BLUPR03MB1378.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:BLUPR03MB1377; BCL:0; PCL:0; RULEID:;  SRVR:BLUPR03MB1377; 
x-forefront-prvs: 05214FD68E
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Mar 2015 06:51:52.4641 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB1377
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/BjSmPwNa2-_vn-wF6qC40MHAGwA>
Cc: "lucid@ietf.org" <lucid@ietf.org>
Subject: Re: [Lucid] Please clarify the i's in Appendix A
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: Fri, 20 Mar 2015 06:51:56 -0000

VSswMTMwIGlzIGRpc2FsbG93ZWQsIGhvd2V2ZXIgbW9zdCBpbXBsZW1lbnRhdGlvbnMgZG8gbWFw
cGluZyBmb3IgbG9va3VwLCBpbiB3aGljaCBjYXNlIFUrMDEzMCBjaGFuZ2VzIHRvIFUrMDA2OSAr
IFUrMDMwNywgZHVlIHRvIHRoZSBhcHBsaWNhdGlvbiBvZiBORktDICsgQ2FzZWZvbGRpbmcuICBo
dHRwOi8vd3d3LnVuaWNvZGUub3JnL1B1YmxpYy9pZG5hLzguMC4wL0lkbmFNYXBwaW5nVGFibGUu
dHh0IA0KDQpPciBpcyBsdWNpZCBvbmx5IGNvbmNlcm5lZCB3aXRoIHRoZSBjYXNlIHdoZXJlIG5v
IG1hcHBpbmcgaXMgYXBwbGllZD8NCg0KLVNoYXduDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0t
LS0tDQpGcm9tOiBQYXRyaWsgRsOkbHRzdHLDtm0gW21haWx0bzpwYWZAZnJvYmJpdC5zZV0gDQpT
ZW50OiBUaHVyc2RheSwgTWFyY2ggMTksIDIwMTUgMTA6NTUgUE0NClRvOiBTaGF3biBTdGVlbGUN
CkNjOiBsdWNpZEBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtMdWNpZF0gUGxlYXNlIGNsYXJpZnkg
dGhlIGkncyBpbiBBcHBlbmRpeCBBDQoNCg0KPiBPbiAyMCBtYXIgMjAxNSwgYXQgMDE6MDEsIFNo
YXduIFN0ZWVsZSA8U2hhd24uU3RlZWxlQG1pY3Jvc29mdC5jb20+IHdyb3RlOg0KPiANCj4gSURO
QSBtYWtlcyB0aGlzIHdvcnNlIGJ5IG1hcHBpbmcgxLAgVSswMTMwIHRvIFUrMDA2OSArIFUrMDMw
NywgYXBwYXJlbnRseSB0byBnZXQgYSB2aXN1YWwgZWZmZWN0LiAgSXQgc2VlbXMgcGVjdWxpYXIg
dG8gbWUgdGhhdCB0aGVyZSB3b3VsZCBuZWVkIHRvIGJlIGFuIGV4Y2VwdGlvbiB0byB0aGUgZXhp
c3RpbmcgZXhjZXB0aW9uLg0KDQpDYW4geW91IHBsZWFzZSBjbGFyaWZ5Pw0KDQpJRE5BIGRvIG5v
dCBpbmNsdWRlIG1hcHBpbmcsIHNvIEkgcHJlc3VtZSB5b3UgbWVhbiAiSUROQSB3b3VsZCBtYWtl
IHRoaXMgd29yc2UgSUYgaXQgbWFwcGVkLi4uIj8NCg0KICAgUGF0cmlrDQoNCg==


From nobody Fri Mar 20 00:03:18 2015
Return-Path: <paf@frobbit.se>
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 0C9561B2C57 for <lucid@ietfa.amsl.com>; Fri, 20 Mar 2015 00:03:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.261
X-Spam-Level: 
X-Spam-Status: No, score=-1.261 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 miYVkKveJpq1 for <lucid@ietfa.amsl.com>; Fri, 20 Mar 2015 00:03:01 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25C271B2C54 for <lucid@ietf.org>; Fri, 20 Mar 2015 00:03:01 -0700 (PDT)
Received: from [192.168.1.138] (frobbit.cust.teleservice.net [85.30.128.225]) by mail.frobbit.se (Postfix) with ESMTPSA id 8C9E42027C; Fri, 20 Mar 2015 08:02:59 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_3E890D6C-4974-40E7-892E-C06724295709"; protocol="application/pgp-signature"; micalg=pgp-sha1
X-Pgp-Agent: GPGMail 2.5b6
From: =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>
In-Reply-To: <BLUPR03MB1378664A6F96AEBBC2E27EE4820E0@BLUPR03MB1378.namprd03.prod.outlook.com>
Date: Fri, 20 Mar 2015 08:02:58 +0100
Message-Id: <7B7C4544-19CA-4E85-8EF6-69305216FCF6@frobbit.se>
References: <BLUPR03MB1378FED1AEB1C756C5D058C2820E0@BLUPR03MB1378.namprd03.prod.outlook.com> <184B22C8-336A-4687-8FAD-E9A4942C6CD8@frobbit.se> <BLUPR03MB1378664A6F96AEBBC2E27EE4820E0@BLUPR03MB1378.namprd03.prod.outlook.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/Np7gXCNUzBdynEj_Qj0qFCObRUI>
Cc: "lucid@ietf.org" <lucid@ietf.org>
Subject: Re: [Lucid] Please clarify the i's in Appendix A
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: Fri, 20 Mar 2015 07:03:10 -0000

--Apple-Mail=_3E890D6C-4974-40E7-892E-C06724295709
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On 20 mar 2015, at 07:51, Shawn Steele <Shawn.Steele@microsoft.com> =
wrote:
>=20
> U+0130 is disallowed, however most implementations do mapping for =
lookup, in which case U+0130 changes to U+0069 + U+0307, due to the =
application of NFKC + Casefolding.  =
http://www.unicode.org/Public/idna/8.0.0/IdnaMappingTable.txt

Ok, then I understand.

That is though for me very different from IDNA including mapping, which =
it does not.

> Or is lucid only concerned with the case where no mapping is applied?

Not from my perspective.

But one of the ways IDNA2008 was able to move forward was to, as we all =
know, ensure mapping was not part of IDNA, just because different =
contexts required and needed different mappings. And because we really =
needed in IDNA strict rules for 1:1 mappings between A-label and =
U-label, and whether codepoints where allowed or not.

So we maybe unfortunately must be a bit precise when we look at =
solutions, or I am afraid it will be very hard to come to a conclusion.

   Patrik


--Apple-Mail=_3E890D6C-4974-40E7-892E-C06724295709
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFVC8YjrMabGguI180RAvbTAJ9LtS+mhuL9sF0cIOkc8626+JiYPACeL4vR
e2qNwfeSn8POs0J1ZinWs58=
=QVy6
-----END PGP SIGNATURE-----

--Apple-Mail=_3E890D6C-4974-40E7-892E-C06724295709--


From nobody Sat Mar 21 10:45:17 2015
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 6163F1A1BA2 for <lucid@ietfa.amsl.com>; Sat, 21 Mar 2015 10:45:16 -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 QMtovVPwq4Nn for <lucid@ietfa.amsl.com>; Sat, 21 Mar 2015 10:45:15 -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 40B3A1A1B2B for <lucid@ietf.org>; Sat, 21 Mar 2015 10:45:15 -0700 (PDT)
Received: from mx1.yitter.info (dhcp-905d.meeting.ietf.org [31.133.144.93]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 04C7D8A031 for <lucid@ietf.org>; Sat, 21 Mar 2015 17:45:13 +0000 (UTC)
Date: Sat, 21 Mar 2015 12:45:17 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: lucid@ietf.org
Message-ID: <20150321174516.GC6841@mx1.yitter.info>
References: <BLUPR03MB1378FED1AEB1C756C5D058C2820E0@BLUPR03MB1378.namprd03.prod.outlook.com> <184B22C8-336A-4687-8FAD-E9A4942C6CD8@frobbit.se> <BLUPR03MB1378664A6F96AEBBC2E27EE4820E0@BLUPR03MB1378.namprd03.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BLUPR03MB1378664A6F96AEBBC2E27EE4820E0@BLUPR03MB1378.namprd03.prod.outlook.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/KoyIqZVmNxKgb9M6MFhit8VpFz0>
Subject: Re: [Lucid] Please clarify the i's in Appendix A
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: Sat, 21 Mar 2015 17:45:16 -0000

Hi,

On Fri, Mar 20, 2015 at 06:51:52AM +0000, Shawn Steele wrote:
> U+0130 is disallowed,

Ok.

> however most implementations do mapping for lookup,

Yes.

> in which case U+0130 changes to U+0069 + U+0307, due to the application of NFKC + Casefolding.

> http://www.unicode.org/Public/idna/8.0.0/IdnaMappingTable.txt 

What you're saying, actually, is that "most implementations" do
casefolding of upper-case input strings prior to IDNA processing
according to an approach that Unicode has (in this case pre-?)
published?  I'm just trying to understand.

> Or is lucid only concerned with the case where no mapping is applied?

I think we have to worry about cases where input strings are the
result of mapping, yes, but _before_ we tackle the really hard cases
can we sort out the merely hard cases?

Thanks,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Sat Mar 21 12:40:45 2015
Return-Path: <Shawn.Steele@microsoft.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 29E451A875A for <lucid@ietfa.amsl.com>; Sat, 21 Mar 2015 12:40:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 xTXFw90-rAa8 for <lucid@ietfa.amsl.com>; Sat, 21 Mar 2015 12:40:41 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0726.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:726]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46CCC1A875E for <lucid@ietf.org>; Sat, 21 Mar 2015 12:40:41 -0700 (PDT)
Received: from BLUPR03MB1378.namprd03.prod.outlook.com (25.163.81.12) by BLUPR03MB1377.namprd03.prod.outlook.com (25.163.81.11) with Microsoft SMTP Server (TLS) id 15.1.118.21; Sat, 21 Mar 2015 19:40:23 +0000
Received: from BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) by BLUPR03MB1378.namprd03.prod.outlook.com ([25.163.81.12]) with mapi id 15.01.0112.000; Sat, 21 Mar 2015 19:40:23 +0000
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, "lucid@ietf.org" <lucid@ietf.org>
Thread-Topic: [Lucid] Please clarify the i's in Appendix A
Thread-Index: AdBin+ZuKs3zpeT0SS+0IvxOVk8XSgAMoPgAAAEwJGAASef/gAAD4reQ
Date: Sat, 21 Mar 2015 19:40:23 +0000
Message-ID: <BLUPR03MB1378A7B9166A44E41437B91A820F0@BLUPR03MB1378.namprd03.prod.outlook.com>
References: <BLUPR03MB1378FED1AEB1C756C5D058C2820E0@BLUPR03MB1378.namprd03.prod.outlook.com> <184B22C8-336A-4687-8FAD-E9A4942C6CD8@frobbit.se> <BLUPR03MB1378664A6F96AEBBC2E27EE4820E0@BLUPR03MB1378.namprd03.prod.outlook.com> <20150321174516.GC6841@mx1.yitter.info>
In-Reply-To: <20150321174516.GC6841@mx1.yitter.info>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [50.34.94.236]
authentication-results: anvilwalrusden.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR03MB1377;
x-microsoft-antispam-prvs: <BLUPR03MB137758AFEFB04BD7451B649D820F0@BLUPR03MB1377.namprd03.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(2950100001)(122556002)(92566002)(33656002)(2900100001)(46102003)(40100003)(66066001)(2656002)(93886004)(76576001)(77156002)(102836002)(62966003)(99286002)(74316001)(50986999)(86362001)(86612001)(76176999)(107886001)(54356999)(2501003)(87936001); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR03MB1377; H:BLUPR03MB1378.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:BLUPR03MB1377; BCL:0; PCL:0; RULEID:;  SRVR:BLUPR03MB1377; 
x-forefront-prvs: 05220145DE
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Mar 2015 19:40:23.2151 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB1377
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/vo5miixU22q5CoBpCZaESW6-6pw>
Subject: Re: [Lucid] Please clarify the i's in Appendix A
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: Sat, 21 Mar 2015 19:40:43 -0000

> What you're saying, actually, is that "most implementations" do casefoldi=
ng of upper-case input strings prior to IDNA processing according to an app=
roach that Unicode has (in this case pre-?) published?  I'm just trying to =
understand.

In IDNA 2008 it was recognized that mappings existed in IDNA2003 and that i=
mplementations such as browser address bars would find them useful.  It was=
 also recognized that mapping is a complex problem, so IDNA 2008 didn't tac=
kle the mapping problem, suggesting that different folks could implement th=
eir own appropriate mappings.

Clearly it doesn't help much to have everyone doing their own different map=
ping, so Unicode provided a mapping which was influenced heavily by the map=
pings of IDNA 2003 for compatibility.  I'm not quite sure how U+0130 ended =
up with its peculiar mapping, which seems like a quirk or the order the rul=
es are applied.  Though I find that particular mapping confusing, it is con=
sistent with IDNA2003.

> I think we have to worry about cases where input strings are the result o=
f mapping, yes, but _before_ we tackle the really hard cases can we sort ou=
t the merely hard cases?

Hmm


From nobody Sat Mar 21 14:32:44 2015
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 ACAAB1A8FD7 for <lucid@ietfa.amsl.com>; Sat, 21 Mar 2015 14:32:42 -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 5tgkv8UiCSOM for <lucid@ietfa.amsl.com>; Sat, 21 Mar 2015 14:32:41 -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 A017B1A8F50 for <lucid@ietf.org>; Sat, 21 Mar 2015 14:32:41 -0700 (PDT)
Received: from mx1.yitter.info (dhcp-905d.meeting.ietf.org [31.133.144.93]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 8DEEF8A031 for <lucid@ietf.org>; Sat, 21 Mar 2015 21:32:38 +0000 (UTC)
Date: Sat, 21 Mar 2015 16:32:42 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: lucid@ietf.org
Message-ID: <20150321213241.GG6841@mx1.yitter.info>
References: <BLUPR03MB1378FED1AEB1C756C5D058C2820E0@BLUPR03MB1378.namprd03.prod.outlook.com> <184B22C8-336A-4687-8FAD-E9A4942C6CD8@frobbit.se> <BLUPR03MB1378664A6F96AEBBC2E27EE4820E0@BLUPR03MB1378.namprd03.prod.outlook.com> <20150321174516.GC6841@mx1.yitter.info> <BLUPR03MB1378A7B9166A44E41437B91A820F0@BLUPR03MB1378.namprd03.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BLUPR03MB1378A7B9166A44E41437B91A820F0@BLUPR03MB1378.namprd03.prod.outlook.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/7K61hWp1FK4wsvUxKeCPhdL-M8U>
Subject: Re: [Lucid] Please clarify the i's in Appendix A
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: Sat, 21 Mar 2015 21:32:42 -0000

On Sat, Mar 21, 2015 at 07:40:23PM +0000, Shawn Steele wrote:

> In IDNA 2008 it was recognized that mappings existed in IDNA2003 and
> that implementations such as browser address bars would find them
> useful.  It was also recognized that mapping is a complex problem,
> so IDNA 2008 didn't tackle the mapping problem, suggesting that
> different folks could implement their own appropriate mappings.

> Clearly it doesn't help much to have everyone doing their own
> different mapping,

My memory is different about this case (no pun intended).  What I
recall about IDNA2008 was that we realized, though experience, that a
single set of mappings would not work reliably universally.  The
Turkic I-set you're raising with this example is actually quite a good
example of this, because whereas the case folding of I is mostly
straightforward, Turkic causes trouble.  Moreover, different
conventions for i-accent handling cause trouble, too.  What we
concluded in the WG was that, if localization were to be taken
seriously, then you could not come up with a universal handler for
this, and registration rules would have to suffice to avoid serious
problems where the community was Internet- (or even
significant-chunk-of-Internet-) scale.  (This is part of why Asmus's
and my draft discusses the network scope as a factor; we seem to have
forgotten this part of the original assumptions of i3.)

The Unicode single-mapping approach basically just does away with that
assumption of the IDNA2008 work (on which PRECIS is founded).
Presumably, Unicode thinks this is a stupid idea, but it was one of
the original founding notions in i3 and if the IETF is to abandon it
we ought to do so with our eyes open.

Anyway, it still seems to me that we have a problem with things that
are straightforwardly PVALID, and we ought to try to understand that
case before we work out what to do with strings that are DISALLOWED
but that have some other transformation on the path to i3.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Mon Mar 30 08:20:58 2015
Return-Path: <marc.blanchet@viagenie.ca>
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 70F1E1ACF59 for <lucid@ietfa.amsl.com>; Mon, 30 Mar 2015 08:20:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.789
X-Spam-Level: 
X-Spam-Status: No, score=0.789 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 9keuaMBHr-DA for <lucid@ietfa.amsl.com>; Mon, 30 Mar 2015 08:20:54 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id BC59E1AD0A2 for <lucid@ietf.org>; Mon, 30 Mar 2015 08:20:54 -0700 (PDT)
Received: from h226.viagenie.ca (h226.viagenie.ca [206.123.31.226]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 7C8CC40393 for <lucid@ietf.org>; Mon, 30 Mar 2015 11:20:56 -0400 (EDT)
From: Marc Blanchet <marc.blanchet@viagenie.ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <EFC4C6ED-F2A4-45A9-A742-7E5CF62273E7@viagenie.ca>
Date: Mon, 30 Mar 2015 11:20:54 -0400
To: lucid@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lucid/LbDZt8eeo92Ib5M-M8gIHmHcamk>
Subject: [Lucid] minutes of the Dallas meeting
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: Mon, 30 Mar 2015 15:20:56 -0000

hello,
 thanks to Stuart Cheshire who did a great job of scribing, the minutes =
of the meeting are available =
(https://www.ietf.org/proceedings/92/minutes/minutes-92-lucid).=20
Please send any changes to bof co-chairs (marc.blanchet@viagenie.ca, =
dthaler@microsoft.com).

Regards, Marc.=

