Re: [precis] I-D Action: draft-ietf-precis-7700bis-01.txt

Sam Whited <> Sun, 04 September 2016 14:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3FEDF12B241 for <>; Sun, 4 Sep 2016 07:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.701
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4ZT2MtIH-9AL for <>; Sun, 4 Sep 2016 07:29:31 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400d:c0d::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B3EA212B017 for <>; Sun, 4 Sep 2016 07:29:31 -0700 (PDT)
Received: by with SMTP id 38so43178521qte.1 for <>; Sun, 04 Sep 2016 07:29:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=swgoo; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Qu52A33tQzAP8q+qH1t99UNqLh11huz4iJNG/lGKa98=; b=CIL6yoU/1WiBk8RWU5ltwWkYgXQdRc3hrxc+WOdZ/KouvhTkcxL4/IaYpYV7Pg7JOc FxTaXUn+MeQjAyxbUf38iDNkFPEPpV0vDifgacPmNlRn4lq09eVBBxajjcsGCSfAD9++ 7igpWsRzhO+jUoq9v+dlxvOZxB/Y6o+QH2QRE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Qu52A33tQzAP8q+qH1t99UNqLh11huz4iJNG/lGKa98=; b=ikNfhNf5dn27jRdEYRex81fADQ0yDSMu6mPCEUoTatK+CftiozMSQqy38ga8ZddTAQ wlxV5TX0S+J8qcATw80O/MuB0f2wj4pdCTscQ8AuvO4EyMdsFfJa4NdGN48OoWMa+8lU JMWKmY8lamRuhKFwZNOCSJaTFqsz3fROBBRuus7jvoEJlqcjJYs85JqRUQLfoJBxvgP3 LDJm3QMUS1sc0akbWFR5QMfe5JNPN33H6qeabH3fbWsiXIhjDz5E55oYO5VihpDaHlIY 5eC6Hw81hk2Tqc/jI97zQPJx60GxPgC2yB51FIGZ3Krghjc9gEzmhLxeofQaZRrF4Oz5 E/Rg==
X-Gm-Message-State: AE9vXwM1Seg3KljHFAqueJZOi4Yz4rKUkqxxxDTtzhU6/R8OcQZM9tgqtytwImkvhtANSxyRW5qXLl46QT2Ivg==
X-Received: by with SMTP id j88mr34389010qtb.131.1472999370813; Sun, 04 Sep 2016 07:29:30 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Sun, 4 Sep 2016 07:28:50 -0700 (PDT)
X-Originating-IP: [2605:a601:1166:8b00:b774:1488:5007:efa9]
In-Reply-To: <>
References: <> <> <>
From: Sam Whited <>
Date: Sun, 4 Sep 2016 09:28:50 -0500
Message-ID: <>
To: Peter Saint-Andre <>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [precis] I-D Action: draft-ietf-precis-7700bis-01.txt
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 04 Sep 2016 14:29:33 -0000

On Sat, Sep 3, 2016 at 4:21 PM, Peter Saint-Andre <> wrote:
>> * §2.1: "May any instances of non-ASCII space be mapped…" sounds odd,
>> should this just say "Instances of non-ASCII space should be mapped…"
> Typo: s/May/Map/

That makes the document read: "Map any instances of non-ASCII space be
mapped to ASCII space"; the "be mapped" still needs to be removed in
the current draft.

>> * §2.2 Specifies that UTF-8 MUST be used as the encoding; do we really
>> want to limit this to UTF-8 only? Is this for comparison purposes?
>> Then again, 99.99% of the time UTF-8 is what you should be using
>> anyways, so I'm not sure that it matters.
> UTF-8 is your friend, and everything in PRECIS is UTF-8.

PRECIS is mostly encoding agnostic; implementations might favor a
specific encoding, but I don't think anything in the spec specifically
*needs* UTF-8. That being said, there are so few reasons to use
anything other than UTF-8 that I don't think it really matters, it was
just curious to me that some of the PRECIS related specs called out
UTF-8 and some didn't.


Sam Whited
pub 4096R/54083AE104EA7AD3