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

Wesley Eddy <wes@mti-systems.com> Tue, 29 October 2013 20:31 UTC

Return-Path: <wes@mti-systems.com>
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 EAF7C21E80BF for <tsv-area@ietfa.amsl.com>; Tue, 29 Oct 2013 13:31:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.716
X-Spam-Level:
X-Spam-Status: No, score=-1.716 tagged_above=-999 required=5 tests=[AWL=0.883, BAYES_00=-2.599]
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 z6AQqnMIxyKC for <tsv-area@ietfa.amsl.com>; Tue, 29 Oct 2013 13:31:50 -0700 (PDT)
Received: from atl4mhob10.myregisteredsite.com (atl4mhob10.myregisteredsite.com [209.17.115.48]) by ietfa.amsl.com (Postfix) with ESMTP id A058D11E814C for <tsv-area@ietf.org>; Tue, 29 Oct 2013 13:31:49 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.206]) by atl4mhob10.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r9TKVfZF009083 for <tsv-area@ietf.org>; Tue, 29 Oct 2013 16:31:41 -0400
Received: (qmail 24323 invoked by uid 0); 29 Oct 2013 20:31:41 -0000
X-TCPREMOTEIP: 107.45.126.23
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.43.65?) (wes@mti-systems.com@107.45.126.23) by 0 with ESMTPA; 29 Oct 2013 20:31:40 -0000
Message-ID: <52701B25.8030603@mti-systems.com>
Date: Tue, 29 Oct 2013 16:31:33 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
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>, "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>
In-Reply-To: <52701811.2020408@gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
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: Tue, 29 Oct 2013 20:31:56 -0000

On 10/29/2013 4:18 PM, Martin Stiemerling wrote:
> Hi Linda,
> 
> We have a full talk about QUIC which is not exactly HTTP but might get
> us some taste of the direction of HTTP.
> 
> However, if there are specific things to discuss, I am more than open to
> discuss them.
> 


If there's anything to discuss about HTTP, it would relate to its
needs from a transport protocol, as was done a bit at IETF87 and
on mailing lists afterwards.

HTTP itself isn't a transport protocol.  People run over it in order
to get through middleboxes and want to view it that way, but there are
still real transport protocols underneath it (TCP, QUIC, etc).

-- 
Wes Eddy
MTI Systems