Re: [tcpm] Rechartering TCPM for alternative congestion control algorithms

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Tue, 27 January 2015 10:31 UTC

Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 34ECD1A876B for <tcpm@ietfa.amsl.com>; Tue, 27 Jan 2015 02:31:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level:
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 cZj1ZSCiw77p for <tcpm@ietfa.amsl.com>; Tue, 27 Jan 2015 02:31:49 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA23A1A6FF8 for <tcpm@ietf.org>; Tue, 27 Jan 2015 02:31:48 -0800 (PST)
Received: from [192.168.1.200] (p508F02F3.dip0.t-ipconnect.de [80.143.2.243]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id F41141C0B4606; Tue, 27 Jan 2015 11:31:46 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <655C07320163294895BBADA28372AF5D16BCCD3D@FR711WXCHMBA05.zeu.alcatel-lucent.com>
Date: Tue, 27 Jan 2015 11:31:46 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <67E21286-0DC0-45C1-A9D4-FBDDE7038F21@lurchi.franken.de>
References: <655C07320163294895BBADA28372AF5D16BCCD3D@FR711WXCHMBA05.zeu.alcatel-lucent.com>
To: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tcpm/M_wqgtXA-yLt5eNuJ8hclXdGW0I>
Cc: "tcpm-chairs@tools.ietf.org" <tcpm-chairs@tools.ietf.org>, "tcpm@ietf.org" <tcpm@ietf.org>
Subject: Re: [tcpm] Rechartering TCPM for alternative congestion control algorithms
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: Tue, 27 Jan 2015 10:31:51 -0000

> On 27 Jan 2015, at 11:21, Scharf, Michael (Michael) <michael.scharf@alcatel-lucent.com> wrote:
> 
> Hi,
> 
> This e-mails asks for community feedback on a suggested small addon to the TCPM charter [1].
> 
> In the last TCPM meeting [2] there was strong support for adopting a document describing the CUBIC congestion control algorithm [3]. To the chairs, it is not entirely obvious whether this document, or possibly other similar documents, would indeed be in scope of the current TCPM charter. Given the importance of the TCP congestion control, we prefer a community consensus explicitly documented in the charter instead of ambiguity.
> 
> The current charter limits the scope of TCPM to "modest changes to the protocol, algorithms, and interfaces". It allows "incremental enhancements of TCP's standard congestion control" but explicitly mandates rechartering for fundamental changes [1]: 
> 
> OLD:
> 
> TCPM also provides a venue for standardization of incremental
> enhancements of TCP's standard congestion control, but such changes
> may require additional review by the IRTF Congestion Control
> Research Group (ICCRG). Fundamental changes to TCP or its congestion
> control algorithms (e.g., departure from loss-based congestion
> control) will be handled by other working groups or will require
> rechartering.
> 
> We suggest to update this paragraph in the TCPM charter by an explicit statement that "TCPM may document alternative congestion control algorithms that are known to be widely deployed, and that are considered safe for large-scale deployment in the Internet":
> 
> NEW:
> 
> TCPM also provides a venue for standardization of incremental
> enhancements of TCP's standard congestion control. In addition,
> TCPM may document alternative congestion control algorithms
> that are known to be widely deployed, and that are considered
> safe for large-scale deployment in the Internet. Changes of algorithms
> may require additional review by the IRTF Congestion Control
> Research Group (ICCRG). Fundamental changes to TCP or its congestion
> control algorithms (e.g., departure from loss-based congestion
> control) will be handled by other working groups or will require
> rechartering.
> 
> In our reading, "TCP's standard congestion control" is currently defined by RFC 5681.
> 
> This e-mail and the suggested rechartering does not imply any adoption of one or more alternative congestion control algorithms.
> 
> Any feedback regarding this suggested rechartering would be very welcome. In particular, please let us know if there are any concerns with this proposal or if you have suggestions for a different wording. Please let us know any thoughts until Feb. 15, 2015.
How would the usage of TCP based CCs in SCTP be handled? Would it be covered in
the documents in TCPM? Would there additional documents be needed? If yes, would
they go also to TCPM or to TSVWG? Just wondering...

Best regards
Michael
> 
> Thanks a lot!
> 
> Michael, Pasi, Yoshifumi
> 
> 
> [1] https://datatracker.ietf.org/wg/tcpm/charter/
> 
> [2] http://www.ietf.org/proceedings/91/minutes/minutes-91-tcpm
> 
> [3] https://datatracker.ietf.org/doc/draft-zimmermann-tcpm-cubic/
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
>