Re: [tcpm] STD 7, RFC 9293 on Transmission Control Protocol (TCP)
Wesley Eddy <wes@mti-systems.com> Thu, 18 August 2022 16:20 UTC
Return-Path: <wes@mti-systems.com>
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 07B68C14792F for <tcpm@ietfa.amsl.com>; Thu, 18 Aug 2022 09:20:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 (2048-bit key) header.d=mti-systems-com.20210112.gappssmtp.com
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 aot6xeYquhhh for <tcpm@ietfa.amsl.com>; Thu, 18 Aug 2022 09:20:15 -0700 (PDT)
Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11DAEC14792E for <tcpm@ietf.org>; Thu, 18 Aug 2022 09:20:15 -0700 (PDT)
Received: by mail-qt1-x836.google.com with SMTP id h4so1471260qtj.11 for <tcpm@ietf.org>; Thu, 18 Aug 2022 09:20:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mti-systems-com.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc; bh=5ol1cLqnqyGuDi2bQsFWmRyldACCajBdCjf5M8/E7GU=; b=BpfK+1jpN8WextiXlzMpQapGUFLKNdAhOvF7DdHoSio+22tQIE0j9/GAdHPV5IaLXA /vddkvNjz4h0itDSf8vBcBqBVtwDXXPotyMiKuZx8WjBbcfU1AlKOu15G7bJveAbYhgn rrvoRXsJus3B0ONg8Ijw8Pan42rIgbVU9119bZWo7nykz8joG6/pHlOIsh9IBOkN6/Ur H6AnyaS2D1YhB1kT8JngU1qRifTVzZVqqfpjVd7yj7ReXeKNMk8weqKLNs+btgnZfE5/ i71MVdV3qRvXNh6KmHgVWo/pzEsIJEC72V0ANUUptq7kFVGehIo5o5WlEys/srN6IBBc 4OZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc; bh=5ol1cLqnqyGuDi2bQsFWmRyldACCajBdCjf5M8/E7GU=; b=TtZ/djgdYa5wb702oLdXenTahWfW7zgUYdKPwsjvO3hBDNt8/Xpt6DFwrhL7ffaV7Z ZQHw/L46JIfqiCVdn6MXVij29l4Shs68UHvenaYffU1D9cOH6tBLTCmCDq8ylnPTLJSO M7Ii152q9Bl5wNwkG74LjREghasASs/K0ysFuSN1AgL7WfdGw+LqIAbYbfpne/1u+MsA LRTrxR9TUS4bml4r2cdkOXKiz4n09QTM5I4iyS2qBwv+0WMUjW/swhlu59ptpfmeqM08 RrZ5r68U4XdG+DtbxxClWcrnPu5F7NNI3ZVXXZHdr8cnJfG2Z3nib/njpWyc7oJA4ibj YyJg==
X-Gm-Message-State: ACgBeo1oxIKVpODGq9ewKx5uzUaWYafa0SOkIRK1oXGB4Jwi7dAi1INB FWn4b+RpcTWw93uTR+xhSGZQmdXqNjr2Vg==
X-Google-Smtp-Source: AA6agR5/mI0YlG8bsW8KtSN8VjXKMKQIX6/wgs4JFgdrtg2d3H4Hx9Vrnjo5Vld6njVrINUg/jGrAg==
X-Received: by 2002:ac8:7d48:0:b0:344:55b4:1897 with SMTP id h8-20020ac87d48000000b0034455b41897mr3350293qtb.309.1660839613648; Thu, 18 Aug 2022 09:20:13 -0700 (PDT)
Received: from [192.168.1.121] (069-135-001-122.biz.spectrum.com. [69.135.1.122]) by smtp.gmail.com with ESMTPSA id f13-20020ac8470d000000b00341a807ed21sm1275061qtp.72.2022.08.18.09.20.12 for <tcpm@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 18 Aug 2022 09:20:12 -0700 (PDT)
Message-ID: <d0927c28-0214-9a91-c967-03aed08a40b5@mti-systems.com>
Date: Thu, 18 Aug 2022 12:20:10 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0
Content-Language: en-US
To: tcpm@ietf.org
References: <20220818135827.DF5931527DC@rfcpa.amsl.com> <A513B72C-D683-4200-994D-6B7971CE61EF@ericsson.com>
From: Wesley Eddy <wes@mti-systems.com>
In-Reply-To: <A513B72C-D683-4200-994D-6B7971CE61EF@ericsson.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/7zSjluoo-Ye4g8Nd3PD9lScN-Us>
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 16:20:19 -0000
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%2Fietf-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%2Fietf-announce > > _______________________________________________ > 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