[tcpm] ICCRG experimental CC reviews

"Eddy, Wesley M. (GRC-RCN0)[VZ]" <wesley.m.eddy@nasa.gov> Fri, 28 March 2008 13:26 UTC

Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: ietfarch-tcpm-archive@core3.amsl.com
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C49623A6B45; Fri, 28 Mar 2008 06:26:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.328
X-Spam-Level:
X-Spam-Status: No, score=-101.328 tagged_above=-999 required=5 tests=[AWL=-0.890, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1orc84gBtvhb; Fri, 28 Mar 2008 06:26:55 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E3A723A6C67; Fri, 28 Mar 2008 06:26:55 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B0E823A6C67 for <tcpm@core3.amsl.com>; Fri, 28 Mar 2008 06:26:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m1STa-g8tNdH for <tcpm@core3.amsl.com>; Fri, 28 Mar 2008 06:26:54 -0700 (PDT)
Received: from ndjsbar01.ndc.nasa.gov (ndjsbar01.ndc.nasa.gov [198.120.25.38]) by core3.amsl.com (Postfix) with ESMTP id DC5DA3A69E2 for <tcpm@ietf.org>; Fri, 28 Mar 2008 06:26:53 -0700 (PDT)
Received: from ndjsxgw03.ndc.nasa.gov (ndjsxgw03.ndc.nasa.gov [129.166.32.111]) by ndjsbar01.ndc.nasa.gov (Spam Firewall) with ESMTP id 742E87DCCA2; Fri, 28 Mar 2008 08:26:52 -0500 (CDT)
Received: from ndjsxgw03.ndc.nasa.gov (ndjsxgw03.ndc.nasa.gov [129.166.32.111]) by ndjsbar01.ndc.nasa.gov with ESMTP id 3bX6nWfZ3YAhHGRD; Fri, 28 Mar 2008 08:26:52 -0500 (CDT)
Received: from NDJSEVS23A.ndc.nasa.gov ([129.166.32.223]) by ndjsxgw03.ndc.nasa.gov with Microsoft SMTPSVC(6.0.3790.1830); Fri, 28 Mar 2008 08:26:52 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 28 Mar 2008 08:26:51 -0500
Message-ID: <BF3765152B100E4DB0CDB33741F5CFBB8474B3@NDJSEVS23A.ndc.nasa.gov>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: ICCRG experimental CC reviews
Thread-Index: AciQ12GuWgWF+gUnSd2SO6o5DTo0CQ==
From: "Eddy, Wesley M. (GRC-RCN0)[VZ]" <wesley.m.eddy@nasa.gov>
To: tcpm@ietf.org
X-OriginalArrivalTime: 28 Mar 2008 13:26:52.0073 (UTC) FILETIME=[623F1990:01C890D7]
Cc: iccrg@cs.ucl.ac.uk
Subject: [tcpm] ICCRG experimental CC reviews
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

The ICCRG has been attempting to prepare a "safety review" of Compound
TCP as input to TCPM in deciding how to handle the Compound TCP I-D.
When we finish this, the ICCRG is also going to do the same for CUBIC
and the CUBIC I-D, and other experimental congestion control proposals
that come to TCPM.

In Philadelphia, we discovered that we didn't know what level of review
TCPM desired from the ICCRG.  We have been looking at Compound TCP since
last summer, but this review incorporates several independent efforts at
implementation, experimentation, and simulation (i.e. not just document
review).  The delay involved in this may be greater than what people
bringing congestion control proposals to the IETF would like.  It can be
difficult enough to get them to bring the proposals here in the first
place; as history shows, they can put code into their operating systems
and widely deploy without the help of the IETF.

My question for TCPM is: Would TCPM participants rather have a "short"
review from the ICCRG, on the order of 4 months, that considers the I-D
in question and any immediately-available supporting materials, OR
would TCPM rather have a "long" review from the ICCRG, perhaps a year,
that has a very thorough investigation behind it.  Or something else
completely.  The short review may have to hedge its conclusions with
a list of unknowns, but it would specifically identify these, whereas
the long review may have less unknowns.  As an example, in the Compound
TCP review, we have an open question about how it is affected in
wireless
environments.

As a TCPM participant myself, I personally prefer the "short" review to
keep proposals to TCPM from spending more time in ICCRG than they do in
TCPM :).
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm