Re: Padding and record sizes in draft-thomson-http-encryption from Martin Thomson on 2016-01-28 (ietf-http-wg@w3.org from January to March 2016)

From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 29 Jan 2016 08:56:35 +1100
To: Peter Beverloo <beverloo@google.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <CABkgnnUNC31huPf2t_8h0ga5-g-SMvARhg0UuLy+jzyW1KKc8A@mail.gmail.com>

On 28 January 2016 at 23:49, Peter Beverloo <beverloo@google.com> wrote:
> For records larger than the default of 4K, this means that implementations
> will have to specify their length in the Encryption header while it can
> be derived from the content's length. This seems sub-optimal.

I assume that you are talking about push again.  I figured that since
we aren't guaranteeing that messages larger than 4k are delivered,
this would be an uncommon scenario.   >4k is pretty sub-optimal for
push for other reasons too.

Received on Thursday, 28 January 2016 21:57:05 UTC