Re: Call for Adoption: Encrypted Content Encoding

Hello,

can someone tell me REAL USEFUL use case where someone would need
this way of having something encrypted on a webserver?

HTTP means hypertext transport protocol and nothing more;

there has always been the alternative to transfer an encrypted file
(e.g. a .rar file, or .zip file or whatever) using any way of transfer 
(e.g. FTP, HTTP, HTTPS, ...)
there is no reason not doing so now.

Walter

On 25.11.2015 05:53, Mark Nottingham wrote:
> We've discussed this document a few times:
>   <https://tools.ietf.org/html/draft-thomson-http-encryption>
>
> WEBPUSH now has a normative requirement upon it in
>    <https://tools.ietf.org/html/draft-ietf-webpush-encryption>
>
> So, I believe that we should adopt this document as a WG product, with a target of Proposed Standard.
>
> Please comment on-list; we’ll make a decision about adoption at the end of next week.
>
> Regards,
>
> --
> Mark Nottingham   https://www.mnot.net/