Re: [tcpm] Roadmap for TCP - New Version

"Scheffenegger, Richard" <rs@netapp.com> Tue, 02 April 2013 21:32 UTC

Return-Path: <rs@netapp.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 823BC21F85CE for <tcpm@ietfa.amsl.com>; Tue, 2 Apr 2013 14:32:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.266
X-Spam-Level:
X-Spam-Status: No, score=-10.266 tagged_above=-999 required=5 tests=[AWL=0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 FdyWN177Q2P9 for <tcpm@ietfa.amsl.com>; Tue, 2 Apr 2013 14:32:07 -0700 (PDT)
Received: from mx1.netapp.com (mx1.netapp.com [216.240.18.38]) by ietfa.amsl.com (Postfix) with ESMTP id ED8B221F85CB for <tcpm@ietf.org>; Tue, 2 Apr 2013 14:32:06 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,394,1363158000"; d="scan'208";a="250226474"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx1-out.netapp.com with ESMTP; 02 Apr 2013 14:32:07 -0700
Received: from vmwexceht01-prd.hq.netapp.com (exchsmtp.hq.netapp.com [10.106.76.239]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r32LW6iq027631; Tue, 2 Apr 2013 14:32:06 -0700 (PDT)
Received: from SACEXCMBX02-PRD.hq.netapp.com ([169.254.1.222]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.02.0342.003; Tue, 2 Apr 2013 14:32:05 -0700
From: "Scheffenegger, Richard" <rs@netapp.com>
To: Alexander Zimmermann <alexander.zimmermann@comsys.rwth-aachen.de>
Thread-Topic: [tcpm] Roadmap for TCP - New Version
Thread-Index: AQHOLwSgJNhMzjvV7US/RrlyS2movJjDLjTQgAC45AD//4syEA==
Date: Tue, 02 Apr 2013 21:32:05 +0000
Message-ID: <012C3117EDDB3C4781FD802A8C27DD4F24AE1744@SACEXCMBX02-PRD.hq.netapp.com>
References: <F7E8B035-64AC-4271-A81B-22C8953C455F@comsys.rwth-aachen.de> <012C3117EDDB3C4781FD802A8C27DD4F24AE1132@SACEXCMBX02-PRD.hq.netapp.com> <B6137318-002F-4496-A41D-D1D92B0EC450@comsys.rwth-aachen.de>
In-Reply-To: <B6137318-002F-4496-A41D-D1D92B0EC450@comsys.rwth-aachen.de>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.104.60.116]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tcpm (tcpm@ietf.org)" <tcpm@ietf.org>
Subject: Re: [tcpm] Roadmap for TCP - New Version
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2013 21:32:07 -0000

Hi Alex,


> Why not... What do you propose? Like this?
> 
> 
> RFC 6824 E: "TCP Extensions for Multipath Operation with Multiple
>    Addresses" (January 2013) (Errata)
> 
>       This document [RFC6824] presents protocol changes required to add
>       multipath capability to TCP; specifically, those for signaling and
>       setting up multiple paths ("subflows"), managing these subflows,
>       reassembly of data, and termination of sessions.
> 
> Or completely different?

Yes, something light-weight like that, when technical errata that affect the mechanisms exist.


> > 3.4 eifel detection missing - fwd reference to 4.2?
> 
> Eifel detection is still experimental... (as well as DSACK) We can include
> the fwd ref into the missing intro text of sec. 3.4. OK?

Ok; 


> > Section 7: FACK (SACK)?
> 
> Yes as well as CUBIC and CompoundTCP


For cubic and CTCP there are some (expired) drafts, at least:

http://tools.ietf.org/html/draft-sridharan-tcpm-ctcp-02

http://tools.ietf.org/html/draft-rhee-tcpm-cubic-02

I think the only ietf draft so far describing FACK is

http://tools.ietf.org/html/draft-dukkipati-tcpm-tcp-loss-probe-01#section-2.2




> > Current developments (PRR, IW10)
> 
> OK. Make sense. I will do that.


Richard Scheffenegger