- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sat, 12 Nov 2016 09:37:50 +0100
- To: Martin Thomson <martin.thomson@gmail.com>, Kari Hurtta <hurtta-ietf@elmme-mailer.org>
- Cc: HTTP working group mailing list <ietf-http-wg@w3.org>, Eric Rescorla <ekr@rtfm.com>
On 2016-11-12 09:32, Martin Thomson wrote: > On 12 November 2016 at 17:18, Kari Hurtta <hurtta-ietf@elmme-mailer.org> wrote: >> If I understand correclty Eric Rescorla suggest own specification: >> >> Crypto-Key header field for HTTP Encrypted Content-Encoding >> >> >> Essentially moving >> >> 3. Crypto-Key Header Field >> https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-04#section-3 >> >> to that specification. >> >> Then also there need something to be done with examples. > > The alternative is to find a different solution for that draft, like > moving the keys to the payload. Yes, that's how it actually started. The question remains whether a common mechanism is desirable/needed. Best regards, Julian
Received on Saturday, 12 November 2016 08:38:29 UTC