Re: [precis] Ambiguity in specification of case mapping in RFC 7613 and draft-ietf-precis-nickname

Peter Saint-Andre <peter@andyet.net> Tue, 27 October 2015 14:23 UTC

Return-Path: <peter@andyet.net>
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 CE5891A8A55 for <precis@ietfa.amsl.com>; Tue, 27 Oct 2015 07:23:21 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 uLoje8h1umPM for <precis@ietfa.amsl.com>; Tue, 27 Oct 2015 07:23:20 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (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 6BF071A8A3B for <precis@ietf.org>; Tue, 27 Oct 2015 07:23:20 -0700 (PDT)
Received: by oies66 with SMTP id s66so120586265oie.1 for <precis@ietf.org>; Tue, 27 Oct 2015 07:23:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=andyet_net.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=QaFRaDJGSDkXFdfGKjEWLz+WNOg6IFYEYzSKGzWfNic=; b=np5tyh+Wxu4cR/0QgToSBzwQOWFuK5TQ6tRq9s2/nCRfWKwNvzCPdnF+6UkWHQAiSZ cEzDxSspj7hAix8UWvTwgfkRTxzXFTRItvCN637M6fljve5iRXBa5aPDv2R4IRE0qI9p zy+G+oYUZdqQWcFi8ENdIJO3X6Pj9eeHbXNTblPv/+DziPb5dv2VEpourWhAadp4a2it HYKNNqPEJTF/87X69U5BYMYnFyxIY8GtDRFMT1BOCI4QjaaI0QUdasiCk8/1VjKQc7tG 15L9c6KAR548LSgA7Dsb1Piab7j8HrTVRgleAA2UH9cF/U2QjaG3c46fQ03ZwyKKpCB1 9rzw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=QaFRaDJGSDkXFdfGKjEWLz+WNOg6IFYEYzSKGzWfNic=; b=fpM5e8xwdmx9l8wqC6CcKU0JdX7xxoR4ThsIvHUcDj56EFf+Ki85VrGdfjRLjj9rZx wSNqwtAWKxiZIGdgwe1dGt8TaAPPl4rlWTTUfpRmSM3O3Biz119GfCROtv3y/ThD+RAr E7jpuiGZ03DUHOtXSGSqSQIvH2M4a17TqIk0ctQzVB1dgEfEEUJP/0Vsdt8fVaIgjQV9 J5nsdCSmM8mzFfWbxRhqRx8Q78RpuIHW1cj8t/Xn7A4VKHL4jNp9+Enx751iN5T2BBv3 kl4dhQ/sHbOvzEMraD7VSQm0h662++hR6TaetFnBqYa5Yjk8YENtSGEuqK5N2QdHKdcZ Kpwg==
X-Gm-Message-State: ALoCoQlTTKSYtN3gb4go5TUTfHoYyjC78ZUx5DBp1CIz1nz2FCKiHnDBqCgdB2/hptOapbLaNWhc
X-Received: by 10.202.77.142 with SMTP id a136mr27659770oib.123.1445955799682; Tue, 27 Oct 2015 07:23:19 -0700 (PDT)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by smtp.googlemail.com with ESMTPSA id s19sm17269594oet.7.2015.10.27.07.23.17 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Oct 2015 07:23:18 -0700 (PDT)
To: John C Klensin <john-ietf@jck.com>, Tom Worster <fsb@thefsb.org>, Alexey Melnikov <Alexey.Melnikov@isode.com>
References: <D230767C.6587A%fsb@thefsb.org> <560C5149.5090607@andyet.net> <588752141F4228C805E674FC@JcK-HP8200.jck.com> <562EA055.3030404@andyet.net> <562F8194.2020108@andyet.net> <6EB77470DA21E4ED85940C28@JcK-HP8200.jck.com>
From: Peter Saint-Andre <peter@andyet.net>
Message-ID: <562F88D4.6070609@andyet.net>
Date: Tue, 27 Oct 2015 08:23:16 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <6EB77470DA21E4ED85940C28@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/_7y0UdZB0FDyZpt6-_fiRMKXoSw>
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: Tue, 27 Oct 2015 14:23:22 -0000

Thanks, John!

On 10/27/15 8:12 AM, John C Klensin wrote:
> I am most of the way through a response now... should be able to
> mail it within an hour or so if I'm not interrupted again; later
> today in any event.
>
>     john
>
>
> --On Tuesday, October 27, 2015 07:52 -0600 Peter Saint-Andre
> <peter@andyet.net> wrote:
>
>> This issue has greater urgency now because
>> draft-ietf-precis-nickname is now in AUTH48...
>>
>> On 10/26/15 3:51 PM, Peter Saint-Andre - &yet wrote:
>>
>>> After all that, I have 3 questions:
>>>
>>> (1) Is my proposed text enough of a clarification that we
>>> should make that change before the nickname I-D is published
>>> as an RFC?
>>
>> I think so.
>>
>>> (2) Should we modify draft-ietf-precis-nickname so that case
>>> folding is applied only as part of comparison and not as part
>>> of enforcement? If so, should we make that change before this
>>> document is published as an RFC?
>>
>> Although it seems to be the case that Unicode case folding is
>> primarily designed for the purpose of matching (i.e.,
>> comparison), I have a concern that applying the PRECIS case
>> mapping rule after applying the normalization and
>> directionality rules might have unintended consequences that
>> we haven't had a chance to consider yet. The PRECIS framework
>> expresses a preference (actually a hard requirement) for
>> applying the rules in a particular order. We made a late
>> change to the username profiles (RFC 7613), such that width
>> mapping is applied first (in order to accommodate fullwidth
>> and halfwidth characters in certain East Asian scripts).
>> Making a late change to the nickname profile also concerns me,
>> even though both of these late changes seem reasonable on the
>> face of it. I will try to find time to think about this
>> further in the next 24 hours.
>>
>>> (3) Should we update RFC 7613 so that case folding is applied
>>> only as part of comparison and not as part of enforcement?
>>
>> That is less urgent so I suggest that we address the nickname
>> spec first.
>>
>> Peter
>>