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

Wesley Eddy <wes@mti-systems.com> Tue, 27 January 2015 16:42 UTC

Return-Path: <wes@mti-systems.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 B04241A8872 for <tcpm@ietfa.amsl.com>; Tue, 27 Jan 2015 08:42:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 ARo4oPeoGu0r for <tcpm@ietfa.amsl.com>; Tue, 27 Jan 2015 08:42:49 -0800 (PST)
Received: from atl4mhob10.myregisteredsite.com (atl4mhob10.myregisteredsite.com [209.17.115.48]) by ietfa.amsl.com (Postfix) with ESMTP id 8B5FD1A8862 for <tcpm@ietf.org>; Tue, 27 Jan 2015 08:40:10 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.208]) by atl4mhob10.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id t0RGe8qB004426 for <tcpm@ietf.org>; Tue, 27 Jan 2015 11:40:08 -0500
Received: (qmail 21699 invoked by uid 0); 27 Jan 2015 16:40:08 -0000
X-TCPREMOTEIP: 69.81.157.169
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.112?) (wes@mti-systems.com@69.81.157.169) by 0 with ESMTPA; 27 Jan 2015 16:40:08 -0000
Message-ID: <54C7BF65.7030104@mti-systems.com>
Date: Tue, 27 Jan 2015 11:40:05 -0500
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>, Joe Touch <touch@isi.edu>, "tcpm@ietf.org" <tcpm@ietf.org>
References: <655C07320163294895BBADA28372AF5D16BCCD3D@FR711WXCHMBA05.zeu.alcatel-lucent.com> <54C7AFDD.5040502@isi.edu> <655C07320163294895BBADA28372AF5D16BCD3B5@FR711WXCHMBA05.zeu.alcatel-lucent.com>
In-Reply-To: <655C07320163294895BBADA28372AF5D16BCD3B5@FR711WXCHMBA05.zeu.alcatel-lucent.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/tcpm/4ooMjKH110EkqRByOOzpx8Od3D4>
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 16:42:50 -0000

On 1/27/2015 10:56 AM, Scharf, Michael (Michael) wrote:
> 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.


When you read the TSVWG or TCPM mailing lists or go to the
meetings, it's a heavily overlapping set of names and faces,
so this is really about which mailing list to use and which
set of chairs will run the process, IMHO.

In the past, when CTCP, CUBIC, and HTCP were being proposed,
TCPM was the group that would have taken them, as mentioned
in the IESG statement from back then:
https://www.ietf.org/iesg/statement/congestion-control.html

TCPM should definitely be the home for this, and TSVWG can be
copied on the adoption call in case some folks there who aren't
following TCPM want to participate.

Either way, reviewing the draft is more important than which
list's name it happens under, so there's no need to have a
constitutional crisis over it.


-- 
Wes Eddy
MTI Systems