On 10/31/2013 10:56 AM, Martin Stiemerling wrote:
On 10/29/2013 09:58 PM, Linda Dunbar wrote:
Here is my naive thinking of some improvement to be done at the
transport layer for HTTP. I say naïve because it could be totally not
feasible.
More and more flows need to go through some additional functions (or
treatment) based on HTTP header (e.g. HTTP request or reply). But the
HTTP header is not fixed in the payload. There could be multiple
HTTP headers in one packet, or one HTTP message being carried by
multiple packets. Therefore, it requires expensive DPI to filter
packets with certain HTTP characteristics.
It would make life easier for network equipment if the TCP header has
a few bits to indicate the characteristics of HTTP message being
carried. E.g. offset to the HTTP header, the number of HTTP message
in the packet, etc.
I don't see any need to make TCP specific to HTTP.
+1
Besides, DPI is meaningless as we shift to using HTTPS (as Google did
since Sept 28, 2013).
Joe
