Re: [tcpm] Feedback on WG acceptance of draft-zimmermann-tcpm-cubic-01

"Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com> Thu, 30 April 2015 09:33 UTC

Return-Path: <michael.scharf@alcatel-lucent.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B1E81A90B0 for <tcpm@ietfa.amsl.com>; Thu, 30 Apr 2015 02:33:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eZ5Nv5oOjxkA for <tcpm@ietfa.amsl.com>; Thu, 30 Apr 2015 02:33:35 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A023B1A8F4A for <tcpm@ietf.org>; Thu, 30 Apr 2015 02:33:35 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id A99BC8C9C62F7; Thu, 30 Apr 2015 09:33:31 +0000 (GMT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id t3U9XWa9020387 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 30 Apr 2015 11:33:33 +0200
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.102]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Thu, 30 Apr 2015 11:33:33 +0200
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: "Eggert, Lars" <lars@netapp.com>, "Scheffenegger, Richard" <rs@netapp.com>
Thread-Topic: [tcpm] Feedback on WG acceptance of draft-zimmermann-tcpm-cubic-01
Thread-Index: AQHQgxQ/N9XmkWoYjEWmlI1mablVN51lQH/Q
Date: Thu, 30 Apr 2015 09:33:32 +0000
Message-ID: <655C07320163294895BBADA28372AF5D16C9B525@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <655C07320163294895BBADA28372AF5D16C939DA@FR712WXCHMBA15.zeu.alcatel-lucent.com> <f66ed0bbaeeb41faa8b41748969a4032@hioexcmbx05-prd.hq.netapp.com> <33E3613D-55E0-4213-BADD-0DFE7B5F8C17@netapp.com>
In-Reply-To: <33E3613D-55E0-4213-BADD-0DFE7B5F8C17@netapp.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tcpm/Z-j0ajlV1H39_r5dxPxC0fqdTMc>
Cc: "tcpm@ietf.org" <tcpm@ietf.org>
Subject: Re: [tcpm] Feedback on WG acceptance of draft-zimmermann-tcpm-cubic-01
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 30 Apr 2015 09:33:37 -0000

> On 2015-4-29, at 14:32, Scheffenegger, Richard <rs@netapp.com> wrote:
> > I'm still in support, on standards track.
> 
> Me too, given that this has been the default CC on Linux for years now.
> What's the reason for Informational; that this was done outside of the
> IETF and therefore doesn't deserve PS? That seems a bit dogmatic given
> the amount of real world experience.

In my view, there is sufficient real world experience, and we had quite a number of TCPM and ICCRG discussions on CUBIC in the past.

I actually care more about another aspect: The CUBIC algorithm have evolved in the past, at least regarding details, and it would be a surprise if this evolution would stop. 

I think the key question is whether we can come up with one "standardized" version of CUBIC that will hopefully be stable for some time, or whether the best we can do in TCPM is to document some snapshot of the algorithm. Both options seem possible to me in principle, but the former one requires more community effort to ensure that the document will not be outdated soon.

> But: I'd rather see it published as Informational that not at all.

In any case, there seems to be unanimous consensus that we will publish a document draft-ietf-tcpm-cubic.

Maybe a related follow-up question should be: What is the expected time-frame for the milestone of submitting draft-ietf-tcpm-cubic to the IESG? 2015? 2016? 2017?

Any thoughts?

Michael


PS: Bob raised a similar question on the AQM list: http://www.ietf.org/mail-archive/web/aqm/current/msg01159.html