IETF Logo Mail Archive

Re: Announcing the TSVAREA session on "Evolution of IETF Transport Protocols" @ IETF-88

Joe Touch <touch@isi.edu> Thu, 31 October 2013 18:09 UTC

Return-Path: <touch@isi.edu>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44B6021F9DA0 for <tsv-area@ietfa.amsl.com>; Thu, 31 Oct 2013 11:09:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.676
X-Spam-Level:
X-Spam-Status: No, score=-103.676 tagged_above=-999 required=5 tests=[AWL=-1.077, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tJnpWsx4YubM for <tsv-area@ietfa.amsl.com>; Thu, 31 Oct 2013 11:08:59 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 50EC711E817F for <tsv-area@ietf.org>; Thu, 31 Oct 2013 11:07:36 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r9VI6xpc009635 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 31 Oct 2013 11:07:00 -0700 (PDT)
Message-ID: <52729C9D.5020204@isi.edu>
Date: Thu, 31 Oct 2013 11:08:29 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Martin Stiemerling <mls.ietf@gmail.com>, Linda Dunbar <linda.dunbar@huawei.com>, Wesley Eddy <wes@mti-systems.com>, "tsv-area@ietf.org" <tsv-area@ietf.org>
Subject: Re: Announcing the TSVAREA session on "Evolution of IETF Transport Protocols" @ IETF-88
References: <526776F0.50401@gmail.com> <4A95BA014132FF49AE685FAB4B9F17F645BE80CD@dfweml509-mbb.china.huawei.com> <52701811.2020408@gmail.com> <52701B25.8030603@mti-systems.com> <4A95BA014132FF49AE685FAB4B9F17F645BF807E@dfweml509-mbx.china.huawei.com> <527299E9.90704@gmail.com>
In-Reply-To: <527299E9.90704@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Oct 2013 18:09:14 -0000

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

v2.23.0 | Report a Bug | By Email