RE: Call for Adoption: Encrypted Content Encoding

Without wading into the morass of arguments already rehashed, +1 on adopting this.  It doesn't have much stand-alone value, but it's a necessary building block in some things that *are* valuable. 

-----Original Message-----
From: Mark Nottingham [mailto:mnot@mnot.net] 
Sent: Tuesday, November 24, 2015 8:53 PM
To: HTTP Working Group <ietf-http-wg@w3.org>
Subject: Call for Adoption: Encrypted Content Encoding

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 Thursday, 3 December 2015 23:21:33 UTC