[Tsv-art] do we need a checklist or guidelines?

Joe Touch <touch@isi.edu> Wed, 19 July 2017 18:17 UTC

Return-Path: <touch@isi.edu>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D18C131B22 for <tsv-art@ietfa.amsl.com>; Wed, 19 Jul 2017 11:17:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 nbqD4n6Rs2LI for <tsv-art@ietfa.amsl.com>; Wed, 19 Jul 2017 11:17:18 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F33C131B0A for <tsv-art@ietf.org>; Wed, 19 Jul 2017 11:17:18 -0700 (PDT)
Received: from [128.9.184.233] ([128.9.184.233]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id v6JIGt62015263 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 19 Jul 2017 11:16:56 -0700 (PDT)
To: "tsv-art@ietf.org" <tsv-art@ietf.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <44b6345c-359b-65b3-d71e-3210f676fbbc@isi.edu>
Date: Wed, 19 Jul 2017 11:16:53 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/R6G48FY5xCYIZmHo4e9GZwfYeeQ>
Subject: [Tsv-art] do we need a checklist or guidelines?
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 18:17:20 -0000

Hi, all,

I'm seeing increasingly bizzare attempts to modify TCP.

We currently have two requirements for TCP mods, AFAICT:

    a) passes TSV-chair, TSV-ART, and possibly TCPM, TSVWG, etc. review

    b) includes "TCP-friendliness" (mostly for congestion control)

I propose it's time for some new criteria, as follows. Can others let me
know if this would be useful to document somehow, whether formally as an
ID or at least as a TSV-ART checklist?

    c) compliant with existing TCP requirements, notably:

        1) compatible with already-defined TCP options

        2) fail-safe fallback to legacy endpoints (notably not requiring
a new connection attempt with different parameters)

Criteria "c)" is currently under "attack" (imo) by some in the LWIP and
MPTCP groups, the former which hasn't addressed this issue at all and
the latter appears to be actively rejecting it.

Thoughts?

I'd be glad to write this up further, with justification.

Joe