Re: [precis] Ambiguity in specification of case mapping in RFC 7613 and draft-ietf-precis-nickname
Tom Worster <fsb@thefsb.org> Wed, 04 November 2015 16:51 UTC
Return-Path: <fsb@thefsb.org>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id C43211B33C3
for <precis@ietfa.amsl.com>; Wed, 4 Nov 2015 08:51:36 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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 e5N-2kPAq957 for <precis@ietfa.amsl.com>;
Wed, 4 Nov 2015 08:51:35 -0800 (PST)
Received: from smtp74.iad3a.emailsrvr.com (smtp74.iad3a.emailsrvr.com
[173.203.187.74])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 292EE1B3381
for <precis@ietf.org>; Wed, 4 Nov 2015 08:51:35 -0800 (PST)
Received: from smtp26.relay.iad3a.emailsrvr.com (localhost.localdomain
[127.0.0.1])
by smtp26.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 0ECB480435;
Wed, 4 Nov 2015 11:51:34 -0500 (EST)
Received: by smtp26.relay.iad3a.emailsrvr.com (Authenticated sender:
fsb-AT-thefsb.org) with ESMTPSA id A7C9C80312;
Wed, 4 Nov 2015 11:51:30 -0500 (EST)
X-Sender-Id: fsb@thefsb.org
Received: from [10.0.1.2] (c-73-4-147-142.hsd1.ma.comcast.net [73.4.147.142])
(using TLSv1 with cipher DES-CBC3-SHA) by 0.0.0.0:465 (trex/5.5.4);
Wed, 04 Nov 2015 11:51:34 -0500
User-Agent: Microsoft-MacOutlook/14.5.7.151005
Date: Wed, 04 Nov 2015 11:51:27 -0500
From: Tom Worster <fsb@thefsb.org>
To: Peter Saint-Andre <peter@andyet.net>, John C Klensin <john-ietf@jck.com>,
Alexey Melnikov <Alexey.Melnikov@isode.com>
Message-ID: <D25FA194.676D0%fsb@thefsb.org>
Thread-Topic: [precis] Ambiguity in specification of case mapping in RFC 7613
and draft-ietf-precis-nickname
References: <0347834EBDC481BD99BDBE67@JcK-HP8200.jck.com>
<56302E6D.5030901@andyet.net> <56312AAC.1000300@andyet.net>
<56313616.8000801@andyet.net> <563143B9.7020707@andyet.net>
<56383B2F.6080505@andyet.net> <D25E1ABD.673A9%fsb@thefsb.org>
<DB8A468B42BB20CDC0E06929@JcK-HP8200.jck.com>
<563A261F.2040904@andyet.net>
In-Reply-To: <563A261F.2040904@andyet.net>
Mime-version: 1.0
Content-type: text/plain;
charset="UTF-8"
Content-transfer-encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/3XvFLth-d6ufF2EMSQSq20cp9t8>
Cc: precis@ietf.org
Subject: Re: [precis] Ambiguity in specification of case mapping in RFC 7613
and draft-ietf-precis-nickname
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings
<precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>,
<mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>,
<mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Nov 2015 16:51:37 -0000
On 11/4/15, 10:37 AM, "Peter Saint-Andre" <peter@andyet.net> wrote: > >That may be. We could simply remove the offending sentence: > >OLD > > 3. Case Mapping Rule: Unicode Default Case Folding MUST be applied, > as defined in the Unicode Standard [Unicode] (at the time of this > writing, the algorithm is specified in Chapter 3 of > [Unicode7.0]). The primary result of doing so is that uppercase > characters are mapped to lowercase characters. In applications > that prohibit conflicting nicknames, this rule helps to reduce > the possibility of confusion by ensuring that nicknames differing > only by case (e.g., "stpeter" vs. "StPeter") would not be > presented to a human user at the same time. > >NEW > > > 3. Case Mapping Rule: Unicode Default Case Folding MUST be applied, > as defined in the Unicode Standard [Unicode] (at the time of this > writing, the algorithm is specified in Chapter 3 of > [Unicode7.0]). In applications that prohibit conflicting > nicknames, this rule helps to reduce the possibility of > confusion by ensuring that nicknames differing only by case > (e.g., "stpeter" vs. "StPeter") would not be presented to a > human user at the same time. > >If we do that, we're no longer dancing around issues. Splendid idea! Tom
- [precis] Ambiguity in specification of case mappi… Tom Worster
- Re: [precis] Ambiguity in specification of case m… Peter Saint-Andre - &yet
- Re: [precis] Ambiguity in specification of case m… John C Klensin
- Re: [precis] Ambiguity in specification of case m… Tom Worster
- Re: [precis] Ambiguity in specification of case m… John C Klensin
- Re: [precis] Ambiguity in specification of case m… Peter Saint-Andre - &yet
- Re: [precis] Ambiguity in specification of case m… Peter Saint-Andre
- Re: [precis] Ambiguity in specification of case m… John C Klensin
- Re: [precis] Ambiguity in specification of case m… Peter Saint-Andre
- Re: [precis] Ambiguity in specification of case m… John C Klensin
- Re: [precis] Ambiguity in specification of case m… Peter Saint-Andre
- Re: [precis] Ambiguity in specification of case m… Peter Saint-Andre
- Re: [precis] Ambiguity in specification of case m… Peter Saint-Andre
- Re: [precis] Ambiguity in specification of case m… Peter Saint-Andre
- Re: [precis] Ambiguity in specification of case m… Peter Saint-Andre
- Re: [precis] Ambiguity in specification of case m… Tom Worster
- Re: [precis] Ambiguity in specification of case m… John C Klensin
- Re: [precis] Ambiguity in specification of case m… Tom Worster
- Re: [precis] Ambiguity in specification of case m… Peter Saint-Andre
- Re: [precis] Ambiguity in specification of case m… Tom Worster
- Re: [precis] Ambiguity in specification of case m… John C Klensin