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

Re: 2nd Working Group Last Call: draft-ietf-httpbis-encryption-encoding-03.txt

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Wed, 19 Oct 2016 15:33:15 +0000
To: Julian Reschke <julian.reschke@gmx.de>
cc: Martin Thomson <martin.thomson@gmail.com>, Mark Nottingham <mnot@mnot.net>, HTTP working group mailing list <ietf-http-wg@w3.org>, Patrick McManus <pmcmanus@mozilla.com>
Message-ID: <30262.1476891195@critter.freebsd.dk>
In message <18d7f584-a303-f218-24ec-abf0c341f436@gmx.de>, Julian Reschke writes

>> All this stuff can be done with existing HTTP mechanisms, by defining
>> a new C-E which carries its own metadata in the body, like all other
>> C-E's, and the enourmous advantage of that is that it is backwards
>> compatible.
>But how would you handle the case describes above -- where the metadata 
>(content type, encryption material) is served from a server different 
>from the one having the (encrypted) payload?

I would put it into the inline metadata of the new C-E I defined.

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, 19 October 2016 15:33:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 19 October 2016 15:33:44 UTC