Re: RIP: Crypto-Key header field

Julian Reschke <julian.reschke@gmx.de> Thu, 24 November 2016 06:25 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 E332C1295FF for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 23 Nov 2016 22:25:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.398
X-Spam-Level:
X-Spam-Status: No, score=-8.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.497, 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 zRXExaC7sayJ for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 23 Nov 2016 22:25:44 -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 5C44712954E for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 23 Nov 2016 22:25:44 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1c9nPi-0001xV-2o for ietf-http-wg-dist@listhub.w3.org; Thu, 24 Nov 2016 06:21:42 +0000
Resent-Date: Thu, 24 Nov 2016 06:21:42 +0000
Resent-Message-Id: <E1c9nPi-0001xV-2o@frink.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by frink.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <julian.reschke@gmx.de>) id 1c9nPa-0001wF-60 for ietf-http-wg@listhub.w3.org; Thu, 24 Nov 2016 06:21:34 +0000
Received: from mout.gmx.net ([212.227.15.15]) by titan.w3.org with esmtps (TLS1.2:DHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <julian.reschke@gmx.de>) id 1c9nPS-0002Df-N8 for ietf-http-wg@w3.org; Thu, 24 Nov 2016 06:21:28 +0000
Received: from [192.168.178.20] ([93.217.104.55]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Lm3bl-1cj8De2Dgn-00ZdR5; Thu, 24 Nov 2016 07:20:55 +0100
To: Martin Thomson <martin.thomson@gmail.com>, =?UTF-8?Q?Martin_J._D=c3=bcrst?= <duerst@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> <CABkgnnVd+414QH8F7dMmmFmAd5S0cTXbUC12pQoapUdpoAYvZg@mail.gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <23699f01-1a0f-1b2f-edcd-c21dbce4d5a8@gmx.de>
Date: Thu, 24 Nov 2016 07:20:53 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0
MIME-Version: 1.0
In-Reply-To: <CABkgnnVd+414QH8F7dMmmFmAd5S0cTXbUC12pQoapUdpoAYvZg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:n1/1Vzwsx8sJenxs3aMGxSHJyDTU0R1lIlYKRJydGUa96rc1v5V F3GYwmZcjh8NU7KbSI495YqVW7JL/cprQ5YpqP7BEfZSLCHqRk9Anlo4iAwwzMcg3IwU9Sx MzS/jyjKlpmMEu7Dc5C4V9vKRMJ5qwIVPJa15X9m/fVdiJrmJLvAK35x3iKJkEHruHeq904 nlLNM1QoR320c1cYNCu/A==
X-UI-Out-Filterresults: notjunk:1;V01:K0:MD9W7DqOs3c=:wES4edWiuGYS89i6+He1PO MlPSRHvPHnYyl25ejjTjzKqts3qBtWRYIFnemeCeDM4/AKkP1HgnuF7LOmrTnDsBsXAVOVPW0 pP14ETJ93BdL+qcLwL0sN6+cAILDcmrlQmbAABo5IMJTcZ8Ml4DlMv3pZ8S8NM/s8vdUcN5oG TvEytFdvzvV0v9tHAGlvBePNY2KsoGMZuyUgF1MPYkue1wxreV3vXi7TG/8+h7ylryqMM/acF bQtQRPqmzUVTJkNOF0U6e3dp0ZsjsrKLs2+LTeSbGmMZCYYRRkL8n900iaKx/xHUt1PTHp5Lp JzxYoClnap+gMOztBPr6oAjagQnXo/pu+zXTD2nosW+B01prHvnuaWk/YtNCHl+81T4B71jYY PzQgcUke9oh8Qk4ADls9QPGYp3bEAm740JSHu8cVNY36utwNYqNAN3qLH+qEoWQUBiDeb/4i5 Vi1iejq+ZHGdOf2E84q93aaTW3Vgx+NQfOp1lJeCNa76SgN7gsREbmo8PTP0tvNlp0oZmgqKp hevBPdQD5oDylxok1sJ45+1ttTj5wGF2epu1GVpiQ5aW0h1gJVfqi6Ql2lsZ6vSPCmlv3Cmn2 TSMRiq0KmDJOQtRQ+ApEubhZVHr1q4e4vlhHe3pJg68dwHvVx/qqPnouGRb+x2a41xuQbcOSX emKtxLle369NTu5w+SjKFvmQ40xjx3PFfVW+UDqIng0l2b6g6tFIw2G3dr/OThzZuhlBsfmVc qE3LGHqMugILG8OULWYdalJ+VQZiOVWaoPjbjVn3T/0Ze0aMd1K8j7AROn9NAeMbHIDoeQDBR V5lvK3D
Received-SPF: pass client-ip=212.227.15.15; envelope-from=julian.reschke@gmx.de; helo=mout.gmx.net
X-W3C-Hub-Spam-Status: No, score=-6.6
X-W3C-Hub-Spam-Report: AWL=-0.025, BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1c9nPS-0002Df-N8 06a2940f3d4aecccf6fb9b5c865f0b1e
X-Original-To: ietf-http-wg@w3.org
Subject: Re: RIP: Crypto-Key header field
Archived-At: <http://www.w3.org/mid/23699f01-1a0f-1b2f-edcd-c21dbce4d5a8@gmx.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32989
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 2016-11-24 00:27, Martin Thomson wrote:
> 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

Which?

> a usage that needs strings, then UTF-8 is available to them.

Which implies that those who define the use of dictionaries and the way 
they are transmitted have full control over what keyids are used. Is 
this the case?

Best regards, Julian