[tcpm] Rechartering TCPM for alternative congestion control algorithms

"Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com> Tue, 27 January 2015 10:22 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 AF34D1A8789 for <tcpm@ietfa.amsl.com>; Tue, 27 Jan 2015 02:22:06 -0800 (PST)
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 26OmrnQQlyqU for <tcpm@ietfa.amsl.com>; Tue, 27 Jan 2015 02:22:04 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-01.alcatel-lucent.com [135.245.210.22]) (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 9AB9C1A8783 for <tcpm@ietf.org>; Tue, 27 Jan 2015 02:22:04 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (unknown [135.239.2.122]) by Websense Email Security Gateway with ESMTPS id 042674A41ED6B; Tue, 27 Jan 2015 10:22:01 +0000 (GMT)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id t0RALwTd015955 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 27 Jan 2015 11:22:02 +0100
Received: from FR711WXCHMBA05.zeu.alcatel-lucent.com ([169.254.1.165]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.03.0195.001; Tue, 27 Jan 2015 11:21:47 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: "tcpm@ietf.org" <tcpm@ietf.org>
Thread-Topic: Rechartering TCPM for alternative congestion control algorithms
Thread-Index: AdA6Gw2/aMIpCeKlQZ6aha0AlCWw1g==
Date: Tue, 27 Jan 2015 10:21:47 +0000
Message-ID: <655C07320163294895BBADA28372AF5D16BCCD3D@FR711WXCHMBA05.zeu.alcatel-lucent.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.38]
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/ZQTdK91GJWIxUyiN6Ycq-9ZEoLE>
Cc: "tcpm-chairs@tools.ietf.org" <tcpm-chairs@tools.ietf.org>
Subject: [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:22:06 -0000

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.

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/