Re: Call for Adoption: Encrypted Content Encoding from Cory Benfield on 2015-11-25 (ietf-http-wg@w3.org from October to December 2015)

From: Cory Benfield <cory@lukasa.co.uk>
Date: Wed, 25 Nov 2015 15:12:14 +0000
To: Mark Nottingham <mnot@mnot.net>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <698105A0-80AF-45CE-8CD6-EFEFFB377B8A@lukasa.co.uk>

> On 25 Nov 2015, at 04:53, Mark Nottingham <mnot@mnot.net> wrote:
> 
> Please comment on-list; we’ll make a decision about adoption at the end of next week.
> 
> 

In general, I’m +1 on this, and can also claim Intent to Implement for the Python Requests library.

I do have a few general concerns with the spec as written. Firstly, some of the text remains fairly unclear, though that could just be the problem of an early draft. I am however concerned a bit with the padding model: it seems remarkably unusual to front-pad, and the draft makes no effort to explain why it was done the way it was. Can someone elaborate on that decision?

Received on Wednesday, 25 November 2015 15:13:03 UTC