Re: [tcpm] STD 7, RFC 9293 on Transmission Control Protocol (TCP)
"Scharf, Michael" <Michael.Scharf@hs-esslingen.de> Thu, 18 August 2022 18:16 UTC
Return-Path: <Michael.Scharf@hs-esslingen.de>
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 274A1C14F742 for <tcpm@ietfa.amsl.com>; Thu, 18 Aug 2022 11:16:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hs-esslingen.de
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T_TzmMwOHVC4 for <tcpm@ietfa.amsl.com>; Thu, 18 Aug 2022 11:15:55 -0700 (PDT)
Received: from mail.hs-esslingen.de (mail.hs-esslingen.de [134.108.32.78]) (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 9F5F8C14F719 for <tcpm@ietf.org>; Thu, 18 Aug 2022 11:15:54 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.hs-esslingen.de (Postfix) with ESMTP id D56FA25A16; Thu, 18 Aug 2022 20:15:51 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hs-esslingen.de; s=mail; t=1660846551; bh=Yu7V6XW8Fm7jWHt0uldjCxf1E+yK8+8LnumjV2TJP2E=; h=From:To:Subject:Date:References:In-Reply-To:From; b=OARHgZX4ZbVBBChfNM4dIxfEC1Smjho1uoARxrZ99xP501lMEMq0W7LFH85wjcrgH 9TxKzEOX+utXPGpvK/1fuaVvtZi0RwUman7z7mByQLeMRBdXiF4ZWWqIrQZlPg2OdU G274+4uau4lpk6KRZpAxM3q7XRvYOsZU17+gg8Dk=
X-Virus-Scanned: by amavisd-new-2.7.1 (20120429) (Debian) at hs-esslingen.de
Received: from mail.hs-esslingen.de ([127.0.0.1]) by localhost (hs-esslingen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DX8WupgwrZpN; Thu, 18 Aug 2022 20:15:50 +0200 (CEST)
Received: from rznt8201.rznt.rzdir.fht-esslingen.de (rznt8201.hs-esslingen.de [134.108.48.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.hs-esslingen.de (Postfix) with ESMTPS; Thu, 18 Aug 2022 20:15:50 +0200 (CEST)
Received: from rznt8202.rznt.rzdir.fht-esslingen.de (134.108.48.165) by rznt8201.rznt.rzdir.fht-esslingen.de (134.108.48.164) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Thu, 18 Aug 2022 20:15:50 +0200
Received: from rznt8202.rznt.rzdir.fht-esslingen.de ([fe80::aca4:171a:3ee1:57e0]) by rznt8202.rznt.rzdir.fht-esslingen.de ([fe80::aca4:171a:3ee1:57e0%3]) with mapi id 15.01.2375.031; Thu, 18 Aug 2022 20:15:50 +0200
From: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>
To: Wesley Eddy <wes@mti-systems.com>, "tcpm@ietf.org" <tcpm@ietf.org>
Thread-Topic: [tcpm] STD 7, RFC 9293 on Transmission Control Protocol (TCP)
Thread-Index: AQHYswrmGON9O7qCbkmsGK20oVNc8a20jmWAgAAmxACAAEBOgA==
Date: Thu, 18 Aug 2022 18:15:50 +0000
Message-ID: <aae1af1ed4184f50bf7d609621191400@hs-esslingen.de>
References: <20220818135827.DF5931527DC@rfcpa.amsl.com> <A513B72C-D683-4200-994D-6B7971CE61EF@ericsson.com> <d0927c28-0214-9a91-c967-03aed08a40b5@mti-systems.com>
In-Reply-To: <d0927c28-0214-9a91-c967-03aed08a40b5@mti-systems.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [134.108.140.249]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/LjtbVHre64hDSGcJ5A2Y4fWd3I4>
Subject: Re: [tcpm] STD 7, RFC 9293 on Transmission Control Protocol (TCP)
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.39
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, 18 Aug 2022 18:16:01 -0000
Well, the chairs were discussing back then whether this endeavor would end up as RFC 10793... But 9273 is a nice number, too. And it proofs that TCPM can be faster than expected ;-) Michael > -----Original Message----- > From: tcpm <tcpm-bounces@ietf.org> On Behalf Of Wesley Eddy > Sent: Thursday, August 18, 2022 6:20 PM > To: tcpm@ietf.org > Subject: Re: [tcpm] STD 7, RFC 9293 on Transmission Control Protocol (TCP) > > Thank you! I'm pretty sure I remember at IETF 88 in Vancouver (2013) > estimating that this work might take about a year. :) > > Many people contributed, and I should also point out that near the end > the RFC Editor staff did a really nice job tuning some of the formatting > and converting some of the ASCII art tables into proper XML2RFC tables > (in addition to a lot of other work they did). That might make 9293bis > a bit easier for someone 30 years from now. > > > On 8/18/2022 10:01 AM, Mirja Kuehlewind wrote: > > Yeah! Thanks Wes! > > > > > > > > On 18.08.22, 16:00, "IETF-Announce on behalf of rfc-editor@rfc-editor.org" > <ietf-announce-bounces@ietf.org on behalf of rfc-editor@rfc-editor.org> > wrote: > > > > A new Request for Comments is now available in online RFC libraries. > > > > STD 7 > > RFC 9293 > > > > Title: Transmission Control Protocol (TCP) > > Author: W. Eddy, Ed. > > Status: Standards Track > > Stream: IETF > > Date: August 2022 > > Mailbox: wes@mti-systems.com > > Pages: 98 > > Obsoletes: RFC 793, RFC 879, RFC 2873, RFC 6093, > > RFC 6429, RFC 6528, RFC 6691 > > Updates: RFC 1011, RFC 1122, RFC 5961 > > See Also: STD 7 > > > > I-D Tag: draft-ietf-tcpm-rfc793bis-28.txt > > > > URL: https://www.rfc-editor.org/info/rfc9293 > > > > DOI: 10.17487/RFC9293 > > > > This document specifies the Transmission Control Protocol (TCP). TCP > > is an important transport-layer protocol in the Internet protocol > > stack, and it has continuously evolved over decades of use and growth > > of the Internet. Over this time, a number of changes have been made > > to TCP as it was specified in RFC 793, though these have only been > > documented in a piecemeal fashion. This document collects and brings > > those changes together with the protocol specification from RFC 793. > > This document obsoletes RFC 793, as well as RFCs 879, 2873, 6093, > > 6429, 6528, and 6691 that updated parts of RFC 793. It updates RFCs > > 1011 and 1122, and it should be considered as a replacement for the > > portions of those documents dealing with TCP requirements. It also > > updates RFC 5961 by adding a small clarification in reset handling > > while in the SYN-RECEIVED state. The TCP header control bits from > > RFC 793 have also been updated based on RFC 3168. > > > > This document is a product of the TCP Maintenance and Minor > Extensions Working Group of the IETF. > > > > This is now an Internet Standard. > > > > STANDARDS TRACK: This document specifies an Internet Standards Track > > protocol for the Internet community, and requests discussion and > suggestions > > for improvements. Please refer to the current edition of the Official > > Internet Protocol Standards (https://www.rfc-editor.org/standards) for > the > > standardization state and status of this protocol. Distribution of this > > memo is unlimited. > > > > This announcement is sent to the IETF-Announce and rfc-dist lists. > > To subscribe or unsubscribe, see > > https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af- > 454445555731-43d34bb74fdd53e0&q=1&e=518134fd-4f57-4fc2-970d- > 7d09af789a55&u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2F > ietf-announce > > https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > > > For searching the RFC series, see https://www.rfc-editor.org/search > > For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk > > > > Requests for special distribution should be addressed to either the > > author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless > > specifically noted otherwise on the RFC itself, all RFCs are for > > unlimited distribution. > > > > > > The RFC Editor Team > > Association Management Solutions, LLC > > > > > > _______________________________________________ > > IETF-Announce mailing list > > IETF-Announce@ietf.org > > https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af- > 454445555731-43d34bb74fdd53e0&q=1&e=518134fd-4f57-4fc2-970d- > 7d09af789a55&u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2F > ietf-announce > > > > _______________________________________________ > > tcpm mailing list > > tcpm@ietf.org > > https://www.ietf.org/mailman/listinfo/tcpm > > _______________________________________________ > tcpm mailing list > tcpm@ietf.org > https://www.ietf.org/mailman/listinfo/tcpm
- [tcpm] STD 7, RFC 9293 on Transmission Control Pr… rfc-editor
- Re: [tcpm] STD 7, RFC 9293 on Transmission Contro… Mirja Kuehlewind
- Re: [tcpm] STD 7, RFC 9293 on Transmission Contro… Wesley Eddy
- Re: [tcpm] STD 7, RFC 9293 on Transmission Contro… Yuchung Cheng
- Re: [tcpm] STD 7, RFC 9293 on Transmission Contro… Neal Cardwell
- Re: [tcpm] STD 7, RFC 9293 on Transmission Contro… Scharf, Michael