Re: [tcpm] On allocating reserved bits in the TCP header

Lars Eggert <lars@eggert.org> Thu, 03 October 2019 11:31 UTC

Return-Path: <lars@eggert.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 69E7B120091 for <tcpm@ietfa.amsl.com>; Thu, 3 Oct 2019 04:31:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 X_YFOmgkBodD for <tcpm@ietfa.amsl.com>; Thu, 3 Oct 2019 04:31:34 -0700 (PDT)
Received: from emh06.mail.saunalahti.fi (emh06.mail.saunalahti.fi [62.142.5.116]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 079C112003F for <tcpm@ietf.org>; Thu, 3 Oct 2019 04:31:34 -0700 (PDT)
Received: from eggert.org (unknown [62.248.255.8]) by emh06.mail.saunalahti.fi (Postfix) with ESMTP id AAA7B30031; Thu, 3 Oct 2019 14:31:31 +0300 (EEST)
Received: from slate.eggert.org (Slate.eggert.org [172.19.235.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by eggert.org (Postfix) with ESMTPSA id 229D6841F08; Thu, 3 Oct 2019 14:31:27 +0300 (EEST)
From: Lars Eggert <lars@eggert.org>
Message-Id: <13123FDD-D69C-4D67-9F1B-B9B27FB6A234@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_5AE2071B-C548-4E2D-8586-63ECF444A4C9"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Thu, 3 Oct 2019 14:31:26 +0300
In-Reply-To: <6EC6417807D9754DA64F3087E2E2E03E2D437915@rznt8114.rznt.rzdir.fht-esslingen.de>
Cc: "tcpm@ietf.org" <tcpm@ietf.org>
To: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>
References: <6EC6417807D9754DA64F3087E2E2E03E2D437915@rznt8114.rznt.rzdir.fht-esslingen.de>
X-MailScanner-ID: 229D6841F08.A42CB
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/4VMPE3KNrTKQDyfmGv-CFno1YQk>
Subject: Re: [tcpm] On allocating reserved bits in the TCP header
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: Thu, 03 Oct 2019 11:31:36 -0000

On 2019-9-10, at 13:50, Scharf, Michael <Michael.Scharf@hs-esslingen.de> wrote:
> In my reading of RFC 2780 and RFC 8126, it would be a policy violation to allocate a bit in the main TCP header to an experiment without a proper standards track document allowing this experimentation. I am convinced that for bits in the main TCP header the IETF should just follow its own rules.

Agreed.

Lars