Re: Working Group Last Call: Encrypted Content-Encoding for HTTP from Martin Thomson on 2016-06-08 (ietf-http-wg@w3.org from April to June 2016)

From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 8 Jun 2016 19:26:15 +1000
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Cc: Amos Jeffries <squid3@treenet.co.nz>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <CABkgnnVXT18UepV93_Bx82qhNGu8A1+tK=A2G2gLqNt5XPOVpw@mail.gmail.com>

On 8 June 2016 at 18:01, Poul-Henning Kamp <phk@phk.freebsd.dk> wrote:
> I suggest it simply be removed:

WFM.  Here's what I have in the end, with the clarifications I think
help overall:

> The "keyid" parameter identifies the keying material that is used.  When the
  Crypto-Key header field is used, the "keyid" identifies a matching value in
  that field.  The "keyid" parameter MUST be used if keying material included
  in an Crypto-Key header field is needed to derive the content encryption key.
  The "keyid" parameter can also be used to identify keys in an
  application-specific fashion.

...and I'm sure that's too much information.

Received on Wednesday, 8 June 2016 09:26:45 UTC