Re: [precis] [Technical Errata Reported] RFC7564 (4568)

Peter Saint-Andre <stpeter@stpeter.im> Thu, 05 May 2016 01:19 UTC

Return-Path: <stpeter@stpeter.im>
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 916D712D629 for <precis@ietfa.amsl.com>; Wed, 4 May 2016 18:19:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.898
X-Spam-Level:
X-Spam-Status: No, score=-2.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 FINmmaAEAazI for <precis@ietfa.amsl.com>; Wed, 4 May 2016 18:19:12 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id B596A12D9C0 for <precis@ietf.org>; Wed, 4 May 2016 18:19:12 -0700 (PDT)
Received: from aither.local (unknown [73.34.202.214]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id ABE7141651; Wed, 4 May 2016 19:28:50 -0600 (MDT)
To: Barry Leiba <barryleiba@computer.org>, RFC Errata System <rfc-editor@rfc-editor.org>
References: <20151220193202.24380180006@rfc-editor.org> <CALaySJL0uOk9jvF3XWso8ockQVkRzQu5g0m++6Q5Xw6Uca+FuQ@mail.gmail.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
Message-ID: <572A9F8D.2070701@stpeter.im>
Date: Wed, 4 May 2016 19:19:09 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CALaySJL0uOk9jvF3XWso8ockQVkRzQu5g0m++6Q5Xw6Uca+FuQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/-_d-MAUwnaPWevVGiuX1Omy8X9o>
Cc: Peter Saint-Andre <peter@andyet.com>, precis@ietf.org
Subject: Re: [precis] [Technical Errata Reported] RFC7564 (4568)
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 05 May 2016 01:19:14 -0000

Something along the lines of the proposed text makes sense to me, and I 
plan to incorporate such text into 7564bis. I might prefer slightly 
different wording, such as:

    o  Preparation primarily entails ensuring that the characters in an
       individual string are allowed by the underlying PRECIS string
       class, and sometimes also entails applying one or more of the
       rules specified for a particular string class or profile thereof.
       Preparation can be appropriate for constrained devices that can to
       some extent restrict the characters in a string to a limited
       repertoire but that do not have the processing power or onboard
       memory to perform operations such as Unicode normalization.
       However, preparation does not ensure that an input string conforms
       to all of the rules for a string class or profile thereof.

Peter

On 1/21/16 6:29 AM, Barry Leiba wrote:
> Are there comments from the authors or working group on this errata report?
>
> Barry, ART AD
>
>
> On Sun, Dec 20, 2015 at 2:32 PM, RFC Errata System
> <rfc-editor@rfc-editor.org>; wrote:
>> The following errata report has been submitted for RFC7564,
>> "PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols".
>>
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=7564&eid=4568
>>
>> --------------------------------------
>> Type: Technical
>> Reported by: Sam Whited <sam@samwhited.com>;
>>
>> Section: 3
>>
>> Original Text
>> -------------
>> Preparation entails only ensuring that the characters in an
>> individual string are allowed by the underlying PRECIS string
>> class.
>>
>> Corrected Text
>> --------------
>> Preparation entails applying some or none of the rules specified for a
>> particular string class or profile thereof to an individual string, and
>> ensuring that characters in the resulting string are allowed by the
>> underlying PRECIS string class.
>>
>> Notes
>> -----
>> The original text makes it sound like preparation is ONLY validating that the characters in a string are allowed in the underlying PRECIS string class, however, some profiles (for example, see the UsernameCaseMapped profile) specify that some of the rules must be applied first (in the case of UsernameCaseMapped, preparation includes first applying the Width rule).
>>
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". If necessary, please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party (IESG)
>> can log in to change the status and edit the report, if necessary.
>>
>> --------------------------------------
>> RFC7564 (draft-ietf-precis-framework-23)
>> --------------------------------------
>> Title               : PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols
>> Publication Date    : May 2015
>> Author(s)           : P. Saint-Andre, M. Blanchet
>> Category            : PROPOSED STANDARD
>> Source              : Preparation and Comparison of Internationalized Strings APP
>> Area                : Applications
>> Stream              : IETF
>> Verifying Party     : IESG
>>