Re: [tcpm] Fwd: I-D Action:draft-cheng-tcpm-fastopen-00.txt

"Scheffenegger, Richard" <rs@netapp.com> Wed, 16 March 2011 14:39 UTC

Return-Path: <rs@netapp.com>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 909983A6911 for <tcpm@core3.amsl.com>; Wed, 16 Mar 2011 07:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.566
X-Spam-Level:
X-Spam-Status: No, score=-10.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1XaHEHsR0636 for <tcpm@core3.amsl.com>; Wed, 16 Mar 2011 07:39:00 -0700 (PDT)
Received: from mx4.netapp.com (mx4.netapp.com [217.70.210.8]) by core3.amsl.com (Postfix) with ESMTP id D32EE3A6954 for <tcpm@ietf.org>; Wed, 16 Mar 2011 07:38:59 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.63,194,1299484800"; d="scan'208";a="246044662"
Received: from smtp3.europe.netapp.com ([10.64.2.67]) by mx4-out.netapp.com with ESMTP; 16 Mar 2011 07:40:25 -0700
Received: from ldcrsexc1-prd.hq.netapp.com (emeaexchrs.hq.netapp.com [10.65.251.109]) by smtp3.europe.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id p2GEePYV002948; Wed, 16 Mar 2011 07:40:25 -0700 (PDT)
Received: from LDCMVEXC1-PRD.hq.netapp.com ([10.65.251.107]) by ldcrsexc1-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 16 Mar 2011 14:40:25 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 16 Mar 2011 14:40:10 -0000
Message-ID: <5FDC413D5FA246468C200652D63E627A0D5F21F6@LDCMVEXC1-PRD.hq.netapp.com>
In-Reply-To: <4D80B572.8090707@gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [tcpm] Fwd: I-D Action:draft-cheng-tcpm-fastopen-00.txt
Thread-Index: Acvj2sClrOcTGxkJShKM1Fcj/g/eUwAAbZxQ
References: <20110308004501.27770.44908.idtracker@localhost> <AANLkTikCwtT_Z0fs7vtWwdEKOxa1Dq0pbzpSFkC3caWu@mail.gmail.com> <5FDC413D5FA246468C200652D63E627A0D4F4DE1@LDCMVEXC1-PRD.hq.netapp.com> <4D7E4EA5.80001@gmail.com><AANLkTi=OkswGWeD+4cLqCD=+8NauVp_fRkC3TQtm+D-z@mail.gmail.com> <4D80B572.8090707@gmail.com>
From: "Scheffenegger, Richard" <rs@netapp.com>
To: William Allen Simpson <william.allen.simpson@gmail.com>, tcpm@ietf.org
X-OriginalArrivalTime: 16 Mar 2011 14:40:25.0174 (UTC) FILETIME=[16081F60:01CBE3E8]
Subject: Re: [tcpm] Fwd: I-D Action:draft-cheng-tcpm-fastopen-00.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 16 Mar 2011 14:39:01 -0000

Richard Scheffenegger

> 
> However, I do not view flooding data on the second connection as
> important as reducing all latency by including data on the first
> connection (and all subsequent connections).  Much more bang for
> the buck!

Ever since browsers were allowed to use multiple connections, stepping
back from their use puts your session(s) at a disadvantage... this
behavior is questionable/discussionable, but never the less, fact.
 
> The fact that your proposal does not test whether SYN data works
> *before*
> flooding the data is a serious flaw, as it will in many cases actually
> increase the number of RTT.  First do no harm....

Yes, you loose either the data contents of the SYN-flagged segments (1
RTT for recovery), of the full initial flight (also 1 RTT, but more
troublesome to the network).

> I do not consider sacrificing reliability and security for performance
> a good trade.


> Moreover, this impedes ever adding any other TCP option ever again.
> This actively prevents inclusion of options approved by the IETF and
this
> group over the past few years.


What did I miss here again? The Cookie is 4..16 bytes in size - the
option 6..18; What prevents me from using smaller cookies when I want to
use other options too? (MSS+WS+SACK+TS has the very same issue today
also).

Best regards,
  Richard