Re: RIP: Crypto-Key header field

Martin Thomson <martin.thomson@gmail.com> Wed, 23 November 2016 23:31 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CE8C12940B for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 23 Nov 2016 15:31:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.998
X-Spam-Level:
X-Spam-Status: No, score=-7.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, 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 jQNJDnWuG0vi for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 23 Nov 2016 15:31:49 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36EB4129404 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 23 Nov 2016 15:31:48 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1c9gxG-0002uN-BM for ietf-http-wg-dist@listhub.w3.org; Wed, 23 Nov 2016 23:27:54 +0000
Resent-Date: Wed, 23 Nov 2016 23:27:54 +0000
Resent-Message-Id: <E1c9gxG-0002uN-BM@frink.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by frink.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <martin.thomson@gmail.com>) id 1c9gx9-0002pq-3C for ietf-http-wg@listhub.w3.org; Wed, 23 Nov 2016 23:27:47 +0000
Received: from mail-qk0-f174.google.com ([209.85.220.174]) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <martin.thomson@gmail.com>) id 1c9gx3-0006mz-4M for ietf-http-wg@w3.org; Wed, 23 Nov 2016 23:27:41 +0000
Received: by mail-qk0-f174.google.com with SMTP id n21so32475306qka.3 for <ietf-http-wg@w3.org>; Wed, 23 Nov 2016 15:27:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=zM3H5AuG58M2ezbcbsyFsD3CWQzXHTDZCOxCtYyaI4c=; b=VLff5KS96K/01E9Di1skyPQeRiRUuuhu3udeibikqdtjhE/NEWeKc1eTwz2GxW3ZV0 uC2JkM4HiELyu6WSZXFYN04EGAxTIBpWnK/Vrcm+Lt56T2+i7QPWQEa4qg37xKcZ35I9 inHdFr5eSe6l/QU1j16N6SR533R7qZMEc046lT9YfCXAse+/UPxLEcIz3aX7ln4N5HUk PmKtvjmG+OAyeUqh7EsGezvO3MnNW4qT0jDl6Ftz6yi/6UznKlUWQy+gQuUinSkDKkAi UwOkn09ywjx8yzueE2Xj3jt5dsyqC57ddhClZIsDYdU9/cywFDTc3GTmLSEKIDrmDEms 1eog==
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:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=zM3H5AuG58M2ezbcbsyFsD3CWQzXHTDZCOxCtYyaI4c=; b=cw/6ASK0eB4NwUS5Dtt0lvD4E7UcwBv6pFPaQLFhipulbMru0ayL7CFjmCARnU6cX6 bdDLQgbxQFQWvVdrt5+D8KuWxqjdNh2stUIGjpzRnT/sD0fNek5C5Xw3dP574O8UiU/w 0HS5c1FQH5JikkEQO83w+l21hXULfoLgk83Y4XdzgOjKCV4cPPzjJtvOeU+uNXcdbk1k PwLip4c8zCVFPUH3ZQ7G1IyK2zczyxLgfXadxL+W6IpGmFjGf5u5/DJ+ADA6vBmcYW5I lf3jdlrSj04t5H6bkyp1rVm1KQUW8C5UH33CV7DlfsuK/HC1tPvAacyfFRk/hXhGkBMC 07cQ==
X-Gm-Message-State: AKaTC03fvbXEPQvRa/5CZM/BPeZoyMWsOo19BHpRiLRVUffrlI7BrSt/jQGH6GrIy3LUlSuEWL5pkzadmhPt7A==
X-Received: by 10.233.235.72 with SMTP id b69mr5833117qkg.144.1479943635203; Wed, 23 Nov 2016 15:27:15 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.85.101 with HTTP; Wed, 23 Nov 2016 15:27:14 -0800 (PST)
In-Reply-To: <dd003ab2-323b-d617-29b8-c39eee8915ec@it.aoyama.ac.jp>
References: <CABkgnnXQ7jFX+U0Ziai_kmja740h-6MBmBG5vxNF5Tr2fpTX3w@mail.gmail.com> <41b1ccf6-32ff-c450-9f61-8f51feb99dad@gmx.de> <CABkgnnV4wtcnZBajJy0VCYXbTQ=LDjGuytz4iOzOLVvVHqB24Q@mail.gmail.com> <249e067b-7c37-9aa2-2937-2bfbbebd033b@gmx.de> <dd003ab2-323b-d617-29b8-c39eee8915ec@it.aoyama.ac.jp>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 24 Nov 2016 10:27:14 +1100
Message-ID: <CABkgnnVd+414QH8F7dMmmFmAd5S0cTXbUC12pQoapUdpoAYvZg@mail.gmail.com>
To: =?UTF-8?Q?Martin_J=2E_D=C3=BCrst?= <duerst@it.aoyama.ac.jp>
Cc: Julian Reschke <julian.reschke@gmx.de>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Received-SPF: pass client-ip=209.85.220.174; envelope-from=martin.thomson@gmail.com; helo=mail-qk0-f174.google.com
X-W3C-Hub-Spam-Status: No, score=-6.1
X-W3C-Hub-Spam-Report: AWL=0.103, 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1c9gx3-0006mz-4M ec85d91b4b54d481d008efe3eac347f4
X-Original-To: ietf-http-wg@w3.org
Subject: Re: RIP: Crypto-Key header field
Archived-At: <http://www.w3.org/mid/CABkgnnVd+414QH8F7dMmmFmAd5S0cTXbUC12pQoapUdpoAYvZg@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32977
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On 23 November 2016 at 18:51, Martin J. Dürst <duerst@it.aoyama.ac.jp> wrote:
>> I see lot of additional works and potential bugs by allowing non-UTF-8
>> octet sequences, and something like zero advantages.
>
>
> Yes indeed. Not knowing what character encoding is used for a string, or not
> knowing whether something is binary or text, it a lot of pain, and no
> "virtue" at all. We have a lot of experience with that; let's not repeat
> these same mistakes over and over again.

This presumes that the field is a string.  We already have a use for
it that treats it as an octet sequence.  If someone cares to designate
a usage that needs strings, then UTF-8 is available to them.