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

gorry@erg.abdn.ac.uk Mon, 04 May 2015 13:16 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
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 2FE8E1A009C for <tcpm@ietfa.amsl.com>; Mon, 4 May 2015 06:16:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.511
X-Spam-Level:
X-Spam-Status: No, score=-1.511 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 EZP_y7Vqdrfo for <tcpm@ietfa.amsl.com>; Mon, 4 May 2015 06:16:02 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 15EE71A0099 for <tcpm@ietf.org>; Mon, 4 May 2015 06:16:01 -0700 (PDT)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 8CDBB1B001DA for <tcpm@ietf.org>; Mon, 4 May 2015 14:16:11 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Mon, 4 May 2015 14:15:13 +0100
Message-ID: <358f1d40d2b8d38605f322d4b70e8b46.squirrel@erg.abdn.ac.uk>
In-Reply-To: <CAOp4FwQrGSBLK=6ASYJ27yPh_Upxujp2GOw_OwbbzAePXB0-_Q@mail.gmail.com>
References: <655C07320163294895BBADA28372AF5D16C939DA@FR712WXCHMBA15.zeu.alcatel-lucent.com> <CAOp4FwQrGSBLK=6ASYJ27yPh_Upxujp2GOw_OwbbzAePXB0-_Q@mail.gmail.com>
Date: Mon, 04 May 2015 14:15:13 +0100
From: gorry@erg.abdn.ac.uk
To: "tcpm@ietf.org" <tcpm@ietf.org>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/tcpm/bjA4DtGmmzvsvR3-y7MOQZwZkxs>
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: Mon, 04 May 2015 13:16:07 -0000

I support work on this topic.

I think that such a document should be maintained within TCPM.

Here are my thoughts:

- WG informational draft
It changes TCP, but there is quite a lot of understanding of how cubic
operates. It could document what is currently implemented, and I think
would be useful exactly in this form. My take is that I do not think it
really competes with any planned IETF work - but would introduce an
alternate CC.

A focus on correcting the text to reflect what is implemented could make
this a fast procedure. That would be a major selling point to me.

- EXP?
I think it could be published as EXP.

The classification at first seems odd, in that there may be more
operational deployment experience with CUBIC than many IETF specs.
However, at least it is more "aggressive" in CC than some IETF-defined
specs.

If the intent of EXP status was to flag this as not yet finally perfected
by IETF experience and to show that the IETF could in future improve this
further, then that would seem a reasonable position. (I'm not even saying
I know of a list of improvements to make).

- PS?
If the WG evaluation concludes that the evidence is good, then it could be
a PS, that would need a consensus call. That call is I suggest impossible
to make until we open the document up to detailed scrutiny and debate.

I can see merits in publishing as INFO asap.

Gorry (as an individual)

> <michael.scharf@alcatel-lucent.com> wrote:
>> Dear all,
>>
>> During IETF 91 [1] and on the list there has been strong support for WG
>> adoption of draft-zimmermann-tcpm-cubic [2]. It seems consensus in TCPM
>> to adopt this document.
>>
>> In order to move forward, the chairs seek for additional community
>> guidance regarding the intended status:
>>
>> a) Proposed standard
>>
>> b) Experimental
>>
>> c) Informational
>>
>