IETF Logo Mail Archive

Re: [precis] RFC 8264 / 8265 Order of rules

Peter Saint-Andre <stpeter@mozilla.com> Wed, 06 December 2017 22:07 UTC

Return-Path: <stpeter@mozilla.com>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C921127869 for <precis@ietfa.amsl.com>; Wed, 6 Dec 2017 14:07:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.com
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 wZQjH8V3_b2y for <precis@ietfa.amsl.com>; Wed, 6 Dec 2017 14:07:53 -0800 (PST)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (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 62E0E126BF3 for <precis@ietf.org>; Wed, 6 Dec 2017 14:07:53 -0800 (PST)
Received: by mail-it0-x236.google.com with SMTP id 68so9861405ite.4 for <precis@ietf.org>; Wed, 06 Dec 2017 14:07:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to; bh=ldw0OoNg9BRSo+mf78OC8AohEORgA9lotFeaPVm9/XQ=; b=UaItSS0Xd5BVuFLarzU/3x4B03/ZREDyZjA6BBxIADcjzOHRQz7R66XKg1+DXveHkc uKkBaBJOVGSTpQDTVtsZ4sIZCwIUBrO+RrSq3Mi4xmf51X3q+h2CZwqc98Nshk252qCM r7jvwXqUfiQGZVe4MvFULVzrhsE8lvIMv/fMY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=ldw0OoNg9BRSo+mf78OC8AohEORgA9lotFeaPVm9/XQ=; b=i+TcE2rrriSuHFcBmD18eB2uttG3GL7rFKQyX5ihyFOJiU4HK1Cgj5/bXZszec2kCF pwXrtZEm9IKCZwbG/QtNkrQw1rof/Hn5UTE18oKg7U5Xck2PYlJoxjMr5vav9udCaXfn yWT7SEcSeNABWG2pn8UmmnV8YWPtU1h6BYQy2CTJ+KxFnt10h7v7MpP6mH4zDEEMfsSH +83f9eeeACRD3TyP0xVt+8EF/4AXmuWlGHi4vydT6iLMq9mtVTh74kNa0BzdEViJrE8p ksfbXy0cnOkP58UOyk6mEayyZRKSajdqq9ovLjcMvju6f5woFIaTlMrvGz8OvX6fe44c YxbQ==
X-Gm-Message-State: AKGB3mJpAAYTO5nORAiIJpJhKI+q2Fj9PDr+up/V+eHXRLYPt18O4kag 0YJ4S1xbpV06BJISWZJ0PwqoYw==
X-Google-Smtp-Source: AGs4zMZcqFurxfdOWZVOUyGh31sTJLXwyGSSMNU+yowhTWZyFkRfwDnKdutjyCvxKRXHJ/03cAlDxA==
X-Received: by 10.36.147.3 with SMTP id y3mr26853273itd.82.1512598072655; Wed, 06 Dec 2017 14:07:52 -0800 (PST)
Received: from dragon.local ([76.25.3.152]) by smtp.gmail.com with ESMTPSA id g79sm2038281itb.29.2017.12.06.14.07.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Dec 2017 14:07:51 -0800 (PST)
To: William Fisher <william.w.fisher@gmail.com>, Christian Schudt <christian.schudt@gmx.de>
Cc: precis@ietf.org
References: <0207F020-32D2-4181-A020-3143BD8E88FE@gmx.de> <CAHVjMKFYO=9twJeJkM7YCv1tT6Fv=4Psw482EPS43sedMyeiSQ@mail.gmail.com>
From: Peter Saint-Andre <stpeter@mozilla.com>
Message-ID: <3c7ba81b-190d-639b-d992-8d0125e8b33e@mozilla.com>
Date: Wed, 06 Dec 2017 15:07:39 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <CAHVjMKFYO=9twJeJkM7YCv1tT6Fv=4Psw482EPS43sedMyeiSQ@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="X3ifBbFfKkclo1Q7MPq0NUfRi3na14mLp"
Archived-At: <https://mailarchive.ietf.org/arch/msg/precis/t-ydayruadVA_3KKCuE7tK9F1mU>
Subject: Re: [precis] RFC 8264 / 8265 Order of rules
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.22
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, 06 Dec 2017 22:07:55 -0000

On 12/4/17 8:58 PM, William Fisher wrote:
> On Mon, Dec 4, 2017 at 4:06 PM, Christian Schudt
> <christian.schudt@gmx.de> wrote:
>> If a user wishes to create a username with U+212B (Angstrom sign), should an application reject it (because it’s disallowed) or allow it, because enforcement converts the character to a valid code point first?
> 
> I implemented enforcement based on the rules in RFC 8264 section 7.
> The behavioral rules (IdentifierClass) are applied last.
> 
>>>> from precis_i18n import get_profile
>>>> ic = get_profile('IdentifierClass')
>>>> ic.enforce('\u212b')
> Traceback (most recent call last):
>  ...
> UnicodeEncodeError: 'IdentifierClass' codec can't encode character
> '\u212b' in position 0: DISALLOWED/has_compat
>>>> un = get_profile('UsernameCasePreserved')
>>>> un.enforce('\u212b')
> 'Å'
> 
> See also:
>   https://www.ietf.org/mail-archive/web/precis/current/msg01225.html
> 
> You're right that the references to preparation in RFC 8265 (sections
> 3.3.2, 3.4.2) are at odds with RFC 8264 and the mailing list.

Sigh.

I'm sorry that we failed to make things clear and consistent.

I agree with Bill that implementations should follow the order of rules
in Section 7 of RFC 8264.

Let me think about how we can clarify things. That might involve filing
an erratum against RFC 8265.

Peter

v2.23.0 | Report a Bug | By Email