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

Re: Call for Adoption: Encrypted Content Encoding

From: Walter H. <Walter.H@mathemainzel.info>
Date: Fri, 27 Nov 2015 05:48:56 +0100
Message-ID: <5657E0B8.2080809@mathemainzel.info>
To: ietf-http-wg@w3.org

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.


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/

Received on Friday, 27 November 2015 04:49:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:40 UTC