Re: Genart last call review of draft-ietf-httpbis-encryption-encoding-08

Martin Thomson <martin.thomson@gmail.com> Tue, 18 April 2017 06:49 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98D66127077; Mon, 17 Apr 2017 23:49:16 -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, FREEMAIL_FROM=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 (2048-bit key) header.d=gmail.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 2F4hiGK-YXXS; Mon, 17 Apr 2017 23:49:15 -0700 (PDT)
Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (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 1CB6D1201F2; Mon, 17 Apr 2017 23:49:15 -0700 (PDT)
Received: by mail-lf0-x232.google.com with SMTP id c80so25193812lfh.3; Mon, 17 Apr 2017 23:49:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=46B7kiD6ba1pzb7vIdLBMFVYv+IG93qlNGNk9dYnH68=; b=Gg1sfv5x2Bu/sbnTz4vsZOvQUKRhIquqmIoNHeqfRxczIua2KNSpmvm2lHLqY6VnRL LxtPwi1cA8EnTDCXqPgXUyexNoSXQBQQb26857mvSThe+a6uz9NZldlp66WoC8ndLYJy x1ThhMGfN1Z1UaSQr98bg/ftIX2RQpLakVqOgN9TcV+szLNtguiaZ9SaAVL+gRaxgegb pW51A4Qk13gA/I9FfopvNwVFkO7UJUu17EOIDbp+Dtdk6GuZz5/t+FH/smQ1SCo6gODO 2Ph1tUrnXcJ+Cy2g9SgWcsFx9jtS+HkghaxV7L4YZ8q2Mu1ltPZEzvziHnJ0ldk9eQ+I UDWg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=46B7kiD6ba1pzb7vIdLBMFVYv+IG93qlNGNk9dYnH68=; b=gZrSf/7eRV2Li+glLB6UxSgcSEKVvoDWku/NO8G7WNQfgv8cugS2MuHzuNhu/3akPp Dq8jAnJXjBXxq2v160RTjc91jYJF9lpyeXpCuKbhm1DB1xxOG1sqj7cCHZJJKtDfZaaQ iRk/WRRVkQkeAmuEb5ajLBW4J710u8Gl7MWpPdjWVKGTVCQXq4/nVWs9C0YljKI0nYAl mLofFjcck/JZJkpn+nAl+wf9r7zh+W7xAPq/U459OnW8Gjk5iBLCqaFXSa01ngEyEoXN Okq5kBTBrB3gwsLXM5CFc73PL18vudvXlfhC5iemsqPjR5TCCoEb+5P6Ab5JuTXF47cV ocaA==
X-Gm-Message-State: AN3rC/5Jzmytpy9S5dF0kW1vmHys7Je9RreFlMrbz535Q/Q9v/mm0T6g SAU12lJ8/sBH+6hi+vuFHd3CCH74WQ==
X-Received: by 10.25.79.27 with SMTP id d27mr2802667lfb.76.1492498153390; Mon, 17 Apr 2017 23:49:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.83.5 with HTTP; Mon, 17 Apr 2017 23:49:12 -0700 (PDT)
In-Reply-To: <149145796867.21962.18267109107454658774@ietfa.amsl.com>
References: <149145796867.21962.18267109107454658774@ietfa.amsl.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 18 Apr 2017 16:49:12 +1000
Message-ID: <CABkgnnUFBGngUzqM0GjpwyvF0w9pCB3eqFgxL8LY_R1otp49dw@mail.gmail.com>
Subject: Re: Genart last call review of draft-ietf-httpbis-encryption-encoding-08
To: Pete Resnick <presnick@qti.qualcomm.com>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-httpbis-encryption-encoding.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/umxsWAYrMeLwex4yAvU6QkZGlEw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 06:49:17 -0000

Thanks Pete,

On 6 April 2017 at 15:52, Pete Resnick <presnick@qti.qualcomm.com>; wrote:
>       A "keyid" parameter SHOULD be a UTF-8
>       [RFC3629] encoded string, particularly where the identifier
> might
>       need to appear in a textual form.
>
> I presume that simply means "might need to be rendered" and does not
> include "might need to be typed in by someone", correct? The former is
> easy; the latter probably requires a bit more text.

Indeed.  Until we have a good copy-and-paste version of the Unicode
typed/spoken/interpretive-danced input problem for security
identifiers, it is not a goal to have specifications casually tackling
problems that are outside their (and maybe anyone's) capabilities.

I made the suggested change in the editor's copy.