- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Wed, 08 Jun 2016 10:13:16 +0000
- To: Martin Thomson <martin.thomson@gmail.com>
- cc: Amos Jeffries <squid3@treenet.co.nz>, HTTP Working Group <ietf-http-wg@w3.org>
-------- In message <CABkgnnVXT18UepV93_Bx82qhNGu8A1+tK=A2G2gLqNt5XPOVpw@mail.gmail.com> , Martin Thomson writes: >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. Works for me. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Received on Wednesday, 8 June 2016 10:13:52 UTC