Re: Comments on draft-ietf-httpbis-encryption-encoding-04

Julian Reschke <julian.reschke@gmx.de> Sat, 12 November 2016 07:36 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 53B361299C7 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 11 Nov 2016 23:36:41 -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 318ZGkbMdW_J for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 11 Nov 2016 23:36:39 -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 36D5912960F for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 11 Nov 2016 23:36:39 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1c5SoY-0003wQ-5w for ietf-http-wg-dist@listhub.w3.org; Sat, 12 Nov 2016 07:33:26 +0000
Resent-Date: Sat, 12 Nov 2016 07:33:26 +0000
Resent-Message-Id: <E1c5SoY-0003wQ-5w@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 1c5SoS-0003vW-M7 for ietf-http-wg@listhub.w3.org; Sat, 12 Nov 2016 07:33:20 +0000
Received: from mout.gmx.net ([212.227.15.18]) 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 1c5SoM-0007An-Hu for ietf-http-wg@w3.org; Sat, 12 Nov 2016 07:33:15 +0000
Received: from [192.168.178.20] ([93.217.126.213]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M9s2y-1byuIf2TBQ-00B6NA; Sat, 12 Nov 2016 08:32:45 +0100
To: Martin Thomson <martin.thomson@gmail.com>, Eric Rescorla <ekr@rtfm.com>
References: <CABcZeBN3B9eYqN0i5abfDmJp+6N86ETwOKfDjCZrkf9AuZ=hdQ@mail.gmail.com> <CABkgnnV3m-_PO1CKYxy=jYaBY0f72LdSqXxkdNdma1d6AM0MEQ@mail.gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <a3f3a4e0-5be3-f619-d2f8-cdda6ce2ed1e@gmx.de>
Date: Sat, 12 Nov 2016 08:32:44 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CABkgnnV3m-_PO1CKYxy=jYaBY0f72LdSqXxkdNdma1d6AM0MEQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:Ke1P4UO9DiQ4JlDlNoPvh3dhgtaNn6DrdhvE6DzaMBeqLylCE65 gjqmHQOP9dlkMKaAyAcRSZxpNAzpbjGc20sJx50eGuiXthfCeXWsctJtTzxDCxlQMDUKRcd wy0PBSItVCniLsEre3B2pdqs7Fb2Ih2ud5jj7MLSgf5vTb384Ol5CV6/l8H69fgvqlwYJFD jBz002B/UI8BiB2lRygpA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:7GMua9vWhwc=:jSV3AYjticE/AyWSkqXQrj Idp52oOsTScA8+NJC31kweDdH41Vb8j+TAK6q0OePBpKuYpc3Oi2UZ//em2GUEZSE+P7PbsI2 kTm3FA5qPSqqUVZ66bwf1I8l4WnOuJfLBlouLZAHEzgwQ/gytCsD7L2HcPaIUpn1g3jUhlHSi k/BYSj8ENAclSZsqOPPwl4ZjiUGPB3w8hbdiBpPu6wxLeybQ3ZlFT//GhpO9Vuee19uTtY1JJ yjgkoPmmww0WU2MAo5fTKBEvIuV2be6g0Iu1rOJJN1US5a6+vRotCXpyGz5D3EVxkQYO06rHv Da4FwaG7GTk+fs7Vf5kKWWcnsg1xS6Sp/gx9pJdRBGzP9yevqtIQuKfl8ZFtoIx1DsmSH39QL 2ncYMH7J5WSNtA5GgJj+g9v++b25nlEPBa+Uvfy9KadHegTWw+gT1Uo2ZxAxs4BhobnUDt/xT TTGGAznbHdwApgAPijolHVaf6D9KvQM1l5N4PYXeO5L8eHbYpA8uVr8GCGpS8HPGxWr7Zi9A5 Av3Hn/CR8UIiYrVPbP6K2GNGN1MDW/0Mqy+8CXqZE33f+8H07j6QWnO0QplRErabPqouRQKmN afzmwxi+/J6MNRK2B1D7EViWXAEIOgwD09wn79IRRD4+lgRvqF1+lbR3cb8GL+gQ2EWqdlk3r dRe+ZuY+vcckVZ7jOqspJdY8K7KdiJqXMex+w8FyfLgNc/hPlw7YmBDMbNsjhx7+6wPjUKwZK ZDwNr5PRl0SIJBoed+JdZaJlRKmjc5IUX9SltGpXiS5B3IICkCDBnwC3bX82JPPgSrr02K8N+ nWIsOp0
Received-SPF: pass client-ip=212.227.15.18; envelope-from=julian.reschke@gmx.de; helo=mout.gmx.net
X-W3C-Hub-Spam-Status: No, score=-8.1
X-W3C-Hub-Spam-Report: AWL=1.397, BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.899, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1c5SoM-0007An-Hu 501a1a403c815532c1d0d26d4b56e9b4
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Comments on draft-ietf-httpbis-encryption-encoding-04
Archived-At: <http://www.w3.org/mid/a3f3a4e0-5be3-f619-d2f8-cdda6ce2ed1e@gmx.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32868
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-12 07:56, Martin Thomson wrote:
> ...
>> S 3.
>> This whole Crypto-Key thing seems like a menace. As has been noted,
>> it's a terrible idea to provide Crypto-Key and encrypted data
>> for the same key in the same HTTP message, but that's the only
>> thing you see to support:
>>
>>    The value or values provided in the Crypto-Key header field is valid
>>    only for the current HTTP message unless additional information
>>    indicates a greater scope.
>>
>> Do we have a concrete use case for Crypto-Key? If not, I would remove
>> it. If so, I would consider writing a different spec.
>
> Maybe we can discuss this in the meeting, I don't have any objection
> to this.  I like deleting code.
> ...

One use case is over here: 
<https://greenbytes.de/tech/webdav/draft-reschke-http-oob-encoding-09.html#n-example-involving-an-encrypted-resource>

If "Cryto-Key" isn't defined in the base spec, any other spec that 
defines how to pass around the key information will have to define it 
itself. That doesn't sound like a good idea to me.

Best regards, Julian