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

[Kari Hurtta <[e-mail]>]

> 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?

https://lists.w3.org/Archives/Public/ietf-http-wg/2016OctDec/0196.html

Is this just about moving Encryption header to body?

   HTTP/1.1 200 OK
   Content-Type: text/html
   Content-Encoding: gzip, aesgcm
   Transfer-Encoding: chunked

   {magic marker}
   keyid="[e-mail]";
   salt="m2hJ_NttRtFyUiMRPwfpHA"
   {magic terminator}
   [encrypted payload]

On https://greenbytes.de/tech/webdav/draft-reschke-http-oob-encoding-08.html#rfc.section.3.5.3
there is 

   Crypto-Key: keyid="a1"; aesgcm="csPJEXBYA5U-Tal9EdJi-w"

which you do not want move to body. That is different thing.

And content-type is just here, it is not moved to
server to where out-of-band points:

TTP/1.1 200 OK
Date: Thu, 14 May 2015 18:52:00 GMT
Content-Encoding: aesgcm, out-of-band
Content-Type: text/plain
Encryption: keyid="a1"; salt="vr0o6Uq3w_KDWeatc27mUg"
Crypto-Key: keyid="a1"; aesgcm="csPJEXBYA5U-Tal9EdJi-w"
Content-Length: 101
Vary: Accept-Encoding

{
  "sr": [
    { "r" :
      "http://example.net/bae27c36-fa6a-11e4-ae5d-00059a3c7a00"}
  ]
}


/ Kari Hurtta