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

"Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com> Tue, 27 January 2015 15:59 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 336C01A88A7 for <tcpm@ietfa.amsl.com>; Tue, 27 Jan 2015 07:59:26 -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 pMnxwWbH9HUc for <tcpm@ietfa.amsl.com>; Tue, 27 Jan 2015 07:59:17 -0800 (PST)
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 9C0971A8849 for <tcpm@ietf.org>; Tue, 27 Jan 2015 07:56:27 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 62593BFBC95A0; Tue, 27 Jan 2015 15:56:22 +0000 (GMT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id t0RFuPej019734 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 27 Jan 2015 16:56:25 +0100
Received: from FR711WXCHMBA05.zeu.alcatel-lucent.com ([169.254.1.165]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Tue, 27 Jan 2015 16:56:26 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: Joe Touch <touch@isi.edu>, "tcpm@ietf.org" <tcpm@ietf.org>
Thread-Topic: [tcpm] Rechartering TCPM for alternative congestion control algorithms
Thread-Index: AdA6Gw2/aMIpCeKlQZ6aha0AlCWw1gAIzXWAAAI6RtA=
Date: Tue, 27 Jan 2015 15:56:24 +0000
Message-ID: <655C07320163294895BBADA28372AF5D16BCD3B5@FR711WXCHMBA05.zeu.alcatel-lucent.com>
References: <655C07320163294895BBADA28372AF5D16BCCD3D@FR711WXCHMBA05.zeu.alcatel-lucent.com> <54C7AFDD.5040502@isi.edu>
In-Reply-To: <54C7AFDD.5040502@isi.edu>
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/KCYo_MJ_Xg0wIfagUixogFb-9tg>
Cc: "tcpm-chairs@tools.ietf.org" <tcpm-chairs@tools.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 15:59:26 -0000

Hi Joe,

The current TCPM charter very explicitly includes "incremental enhancements of TCP's standard congestion control". RFC 5681 is a TCPM document.

Are you suggesting that *all* documents dealing with TCP congestion control should be moved from TCPM to TSVWG, including e.g. potential future updates of RFC 5681?

I guess this would result in a major re-chartering both of TCPM and TSVWG. And it could be a slippery road. A lot of TCPM documents affect congestion control at least partly.

Thanks

Michael


> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Tuesday, January 27, 2015 4:34 PM
> To: Scharf, Michael (Michael); tcpm@ietf.org
> Cc: tcpm-chairs@tools.ietf.org
> Subject: Re: [tcpm] Rechartering TCPM for alternative congestion
> control algorithms
> 
> Hi, all,
> 
> I disagree; TCP congestion control algorithms are also deployed in
> other
> transports, and thus this seems more appropriate for TSVWG.
> 
> Joe
> 
> On 1/27/2015 2:21 AM, Scharf, Michael (Michael) 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.
> >
> > 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
> >