W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2016

Re: WGLC comment on draft-ietf-httpbis-encryption-encoding-03, was: Encryption content coding simplification

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Thu, 13 Oct 2016 07:39:35 +0000
To: Julian Reschke <julian.reschke@gmx.de>
cc: Martin Thomson <martin.thomson@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <28071.1476344375@critter.freebsd.dk>
In message <49a8c514-5a39-d4f6-7012-01977cbefb9c@gmx.de>, Julian Reschke writes

>With that, I actually end up with something similar to one of PHK's 
>	Content-Encoding: aesgcm, aesgcm
>	CE-params: aesgcm;key="csPJEXBYA5U-Tal9EdJi-w";
>		    salt="NfzOeuV5USPRA-n_9s1Lag",
>                    aesgcm
>...where the only difference is that any content coding that *can* have 
>parameters MUST have an associated entry in CE-params.

I have a hard time dreaming up C-E's other than encryption which will
require parameters, but I'm all for taking the general approach up
front, rather than wait for my limited imagination to be exposed.

+1 from here

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 Thursday, 13 October 2016 07:40:03 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 13 October 2016 07:40:07 UTC