Re: [tcpm] Thoughts on EXP vs. PS in TCPM
"Mark Allman" <mallman@icir.org> Wed, 20 November 2019 16:44 UTC
Return-Path: <mallman@icir.org>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 267DB120913 for <tcpm@ietfa.amsl.com>; Wed, 20 Nov 2019 08:44:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 T9jjhWzB-9wn for <tcpm@ietfa.amsl.com>; Wed, 20 Nov 2019 08:44:22 -0800 (PST)
Received: from rock.ICSI.Berkeley.EDU (rock.ICSI.Berkeley.EDU [192.150.186.19]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62865120907 for <tcpm@ietf.org>; Wed, 20 Nov 2019 08:44:22 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by rock.ICSI.Berkeley.EDU (Postfix) with ESMTP id ECA9D2C4039; Wed, 20 Nov 2019 08:44:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at ICSI.Berkeley.EDU
Received: from rock.ICSI.Berkeley.EDU ([127.0.0.1]) by localhost (maihub.ICSI.Berkeley.EDU [127.0.0.1]) (amavisd-new, port 10024) with LMTP id EVauLf-wJVKp; Wed, 20 Nov 2019 08:44:21 -0800 (PST)
Received: from lawyers.icir.org (envoy.ICIR.org [192.150.187.30]) by rock.ICSI.Berkeley.EDU (Postfix) with ESMTP id 629C52C4032; Wed, 20 Nov 2019 08:44:21 -0800 (PST)
Received: from [192.168.1.244] (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id F1D931E6D6DF; Wed, 20 Nov 2019 11:44:20 -0500 (EST)
From: Mark Allman <mallman@icir.org>
To: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>
Cc: tcpm IETF list <tcpm@ietf.org>
Date: Wed, 20 Nov 2019 11:44:20 -0500
X-Mailer: MailMate (1.13r5655)
Message-ID: <D9EFBFA7-9291-4598-9A1F-E0FEEFA5FDEA@icsi.berkeley.edu>
In-Reply-To: <6EC6417807D9754DA64F3087E2E2E03E2D51A41C@rznt8114.rznt.rzdir.fht-esslingen.de>
References: <6EC6417807D9754DA64F3087E2E2E03E2D51A41C@rznt8114.rznt.rzdir.fht-esslingen.de>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/bprr0d7bvF_PwKdk86MPGWSdFKY>
Subject: Re: [tcpm] Thoughts on EXP vs. PS in TCPM
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 20 Nov 2019 16:44:24 -0000
Hi Michael! Good questions. Thanks for starting the thread. I agree that TCPM is basically too conservative. We have been too conservative for a long time. I probably contributed my fair share to that. But, I'd put a finer point on it: Have we ever issued something at EXP (or PS for that matter!) that had to be pulled back because it was too aggressive? I am not conjuring anything at the moment. TCPM has long used EXP as a crutch. We don't have the guts to label something a PS, yet we still want to publish it. And, no amount of non-answers to "what's the experiment?" garners rough consensus for issuing as PS. And, my take is that the world doesn't much buy there to be a distinction. I.e., EXP doesn't dissuade general use of something. And, I bet at least part of this is that we're just too conservative with both kinds of RFCs. If we occasionally did publish an EXP that caused TCP to fall on its face then maybe people would be a bit more careful. That said, it's sort of hard to come up with good rules for delineating. For instance, consider this ... > In order to start a WGLC in TCPM for EXP status, there SHOULD be > one implementation in the main source code tree of an important > TCP/IP stack; a default to "off" is perfectly > acceptable. Well, there are a number of implementations of IW=15 or IW=100, it's just that these are off by default. I.e., something like the initial window is just a constant somewhere so what does it mean that we have 'one implementation' of something like this? I think in the end TCPM standardizes a wide variety of stuff and a one-size rule may not apply. E.g., - We standardize actual protocol mechanisms (a la TFO) and those need some sort of interoperability kinds of criteria. - We standardize algorithms and those need some sort of behavioral and safety criteria (a la RACK). - We standardize constants and those need safety criteria (a la IW or RTO). Further, my observation is that for the latter two in particular the WG cares about 'one impl' vs. 'two impls' much less than we care about the overall evidence that something works---or, where it falls down. I wish I had some idea about how to synthesize this better than 'perhaps we should relax and be less conservative', but I don't. I'll think on it. allman -- https://www.icir.org/mallman/ @mallman_icsi
- [tcpm] Thoughts on EXP vs. PS in TCPM Scharf, Michael
- Re: [tcpm] Thoughts on EXP vs. PS in TCPM Scheffenegger, Richard
- Re: [tcpm] Thoughts on EXP vs. PS in TCPM Scharf, Michael
- Re: [tcpm] Thoughts on EXP vs. PS in TCPM Mark Allman
- Re: [tcpm] Thoughts on EXP vs. PS in TCPM Yuchung Cheng
- Re: [tcpm] Thoughts on EXP vs. PS in TCPM Scheffenegger, Richard