"?> Re: Header compression: buffer management from Poul-Henning Kamp on 2013-03-21 (ietf-http-wg@w3.org from January to March 2013)

W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013

Re: Header compression: buffer management

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Thu, 21 Mar 2013 16:49:35 +0000
To: RUELLAN Herve <Herve.Ruellan@crf.canon.fr>
cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-ID: <1818.1363884575@critter.freebsd.dk>
In message <6C71876BDCCD01488E70A2399529D5E5163F39C4@ADELE.crf.canon.fr>, RUELL
AN Herve writes:

>In HeaderDiff we chose to let the encoder decide how the buffer is managed
>(regarding additions and removals). These decisions are encoded on the wire
> and applied by the decoder on its own buffer. We think this choice has
> several advantages.

Has this been analysed from a denial-of-service perspective ?

Anything in the protocol where the client can cause memory allocation
on the server/proxy/whatever, should be scrutinized in a DoS perspective.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
Received on Thursday, 21 March 2013 16:50:01 GMT

This archive was generated by hypermail 2.3.1 : Thursday, 21 March 2013 16:50:03 GMT