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

Sam Whited <sam@samwhited.com> Thu, 05 May 2016 01:26 UTC

Return-Path: <sam@samwhited.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 D3D7312B00F for <precis@ietfa.amsl.com>; Wed, 4 May 2016 18:26:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_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=samwhited.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 4hSdspZ1VbdX for <precis@ietfa.amsl.com>; Wed, 4 May 2016 18:26:37 -0700 (PDT)
Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) (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 2EEC112D18F for <precis@ietf.org>; Wed, 4 May 2016 18:26:37 -0700 (PDT)
Received: by mail-qg0-x230.google.com with SMTP id 90so33229810qgz.1 for <precis@ietf.org>; Wed, 04 May 2016 18:26:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samwhited.com; s=swgoo; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=G+SJFR4LGM8bOTi3Iw5JF2ggrVF2zDWnyGMpz38gM90=; b=x7fayxfkcq4CRQNKfPVtezecp8QSfCL03NB6lfYDY6EyDnPq7l01rN6T2hCjeWFr6c pY2zl2vMKk50ZaTjsneuZSJ5gwyZ9zHy5SkQTvYcBK9uU4FPScnpamx2KBX8aGj6CZqc VcQAMY5LT6E0v7PNPFso0bBNGJNHxr9SppWHw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=G+SJFR4LGM8bOTi3Iw5JF2ggrVF2zDWnyGMpz38gM90=; b=kw5QeA/l5zVGAayP3/HMCc5rZy78vZZ3bCO8q4UX/DeM6pD3N4SMEjqCUW/e4CV/qo k3mmvucmJp2UAf+q27j4bTay+GC7ChZovrXDhbA76p8POH4ygP8j6tif/gh2o0fbfdiL Bx444Sdg91fA3fUAoUbiIkb7myDWqWwv+OaTATT71AlwYlhsmgaqdKzlWABOrtC2fPnB pEOd9Rn6A05SKrOZWAbe3E/ycfLbUUabfhJtg7DxK0KZCAy7IsUfgSMjrRbh9YsOHUEW sAQ+8Tl+4XFSmwPpzsVhMC99t2rPCZOLVt+h/BpFdzF3hUoYB1GsyQEWdklbol3KE+z+ 5wVQ==
X-Gm-Message-State: AOPr4FUAU9NKqpIABzPBpf5VnsR20Odai6jJMYKlucith8OfelhOqY3ChBn5kprAkLTvA4nVsUDCf5dG9uUzRA==
MIME-Version: 1.0
X-Received: by 10.140.133.5 with SMTP id 5mr93885qhf.19.1462411596352; Wed, 04 May 2016 18:26:36 -0700 (PDT)
Received: by 10.55.197.132 with HTTP; Wed, 4 May 2016 18:26:35 -0700 (PDT)
X-Originating-IP: [2607:fb90:1c3d:b3e2:5ef3:cd5a:b1d2:465e]
Received: by 10.55.197.132 with HTTP; Wed, 4 May 2016 18:26:35 -0700 (PDT)
In-Reply-To: <572A9F8D.2070701@stpeter.im>
References: <20151220193202.24380180006@rfc-editor.org> <CALaySJL0uOk9jvF3XWso8ockQVkRzQu5g0m++6Q5Xw6Uca+FuQ@mail.gmail.com> <572A9F8D.2070701@stpeter.im>
Date: Wed, 4 May 2016 20:26:35 -0500
Message-ID: <CAHbk4RLjsSnxk80gYnPG3WL=KN+j8Uj62sBhRCZkjG74fmzs3w@mail.gmail.com>
From: Sam Whited <sam@samwhited.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: multipart/alternative; boundary=001a1135df9ab768a405320e3bcc
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/pRtf7syjJ67Mhjrw-QYTMjRt-Dk>
Cc: Peter Saint-Andre <peter@andyet.com>, precis@ietf.org, Barry Leiba <barryleiba@computer.org>, RFC Errata System <rfc-editor@rfc-editor.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:26:39 -0000

On May 4, 2016 20:19, "Peter Saint-Andre" <stpeter@stpeter.im> wrote:
> 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.

That sounds very clear to me and addresses my concerns.

Best,
Sam