Re: [tcpm] STD 7, RFC 9293 on Transmission Control Protocol (TCP)
Neal Cardwell <ncardwell@google.com> Thu, 18 August 2022 17:06 UTC
Return-Path: <ncardwell@google.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 80187C14CE46 for <tcpm@ietfa.amsl.com>; Thu, 18 Aug 2022 10:06:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.606
X-Spam-Level:
X-Spam-Status: No, score=-17.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 Rhna_Xggzwpk for <tcpm@ietfa.amsl.com>; Thu, 18 Aug 2022 10:06:02 -0700 (PDT)
Received: from mail-qv1-xf2f.google.com (mail-qv1-xf2f.google.com [IPv6:2607:f8b0:4864:20::f2f]) (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 C6A71C14CE2C for <tcpm@ietf.org>; Thu, 18 Aug 2022 10:06:02 -0700 (PDT)
Received: by mail-qv1-xf2f.google.com with SMTP id d1so1661981qvs.0 for <tcpm@ietf.org>; Thu, 18 Aug 2022 10:06:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=t3W0J0BgN6w5VmsMcoSNbBQloYVJnCiKs+uUGFDrfa0=; b=jsKvb4IkFNZ2lrZqpnfcPairYvFrarYmE4XiZNVU/dlOl9TJAoprpDxaPT/pUTyP34 goRSf7t9fVA7ui4maPVUEBH7ETOeGS+Ru/jqmjBDyEtAIe01b2X09bhLGHMkqGRsTBZM slIBNOGae7Ou19NBSRdwBjHv22vgz9t3gf/ifu7HNXzJCD0cG2vf4FYPbjFuTQvQUByR fXXL+q6uca9q2jWzRBevDVEkQ4KvQYxOwjTvzvrakq/EsQauzc2OPjinuQf2ej/fcHTb jBZvyu2Sd0ZylQSqT2ApVhnkk3Clb1rHkcxSv/ZzpvK02MOtGpnubmWWdUryJ8QYwVu7 YFgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=t3W0J0BgN6w5VmsMcoSNbBQloYVJnCiKs+uUGFDrfa0=; b=62AS8indYGHqnsew+95y5eKCCiVmIWhvDqiPNMGzi5qWmTC2ThoHI0Tl0GEcBMeDpz BtILeolXRkRjyYWwmbnZZmgcn6EwrNm2IyOYv4HzR4O2ooDCD2RxpydANJz+cANlSLQG tYnPk2muKlzhvKmy/E2rf6RDrncD56MRKuRtefBso8fFIxclt2XtRakTLGBfmtebkHt5 OeAm3UtLpFjLD9a/zu+un6EDjj60BvYJp7YzzBh7y7HOfRn7Eyy5Pc9tlNlipGS2P/qt ff1JKK+rGAicsa1qu3vVnzwDpuRggqFztUwtJvE83Sw5zQe2Dgc093klC8kitm0k3HH3 teNw==
X-Gm-Message-State: ACgBeo06Cj5T9qYfqnaU/JMfvVpiKB5GIAu8nIs8T0RDSq/1q8TVO9NP 68tP8gyR+3HTzZ+JxnLS8xAox/oZGcrpZ+NCpLN5+A==
X-Google-Smtp-Source: AA6agR4/v+OW26IcwXomzlu8mFkP5Pjqze2zDeNHa1E/HcOrVZvA5K7+0CKBU2Rywc/PNTz9y5g9h+kx4fcSabVAes0=
X-Received: by 2002:a05:6214:e4d:b0:477:2400:812a with SMTP id o13-20020a0562140e4d00b004772400812amr3630480qvc.99.1660842360944; Thu, 18 Aug 2022 10:06:00 -0700 (PDT)
MIME-Version: 1.0
References: <20220818135827.DF5931527DC@rfcpa.amsl.com> <A513B72C-D683-4200-994D-6B7971CE61EF@ericsson.com> <d0927c28-0214-9a91-c967-03aed08a40b5@mti-systems.com> <CAK6E8=fAhApUf_x=Fn0R7RTEjiNxYSEp-smPa9oKLndf6Jm5eg@mail.gmail.com>
In-Reply-To: <CAK6E8=fAhApUf_x=Fn0R7RTEjiNxYSEp-smPa9oKLndf6Jm5eg@mail.gmail.com>
From: Neal Cardwell <ncardwell@google.com>
Date: Thu, 18 Aug 2022 13:05:45 -0400
Message-ID: <CADVnQymNozo=bZ7LMrOPAr+M4dUf4GFhmjWMyHNukDyC-8y8dQ@mail.gmail.com>
To: Yuchung Cheng <ycheng=40google.com@dmarc.ietf.org>
Cc: Wesley Eddy <wes@mti-systems.com>, tcpm@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f42be505e686fe52"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/EzTMk-SvIJGRNGMu-clzHYpDCsE>
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 17:06:07 -0000
Yes, thanks for all your work on this, Wes! neal On Thu, Aug 18, 2022 at 12:33 PM Yuchung Cheng <ycheng= 40google.com@dmarc.ietf.org> wrote: > Excellent milestone indeed. Kudos to Wes! > > On Thu, Aug 18, 2022 at 9:20 AM Wesley Eddy <wes@mti-systems.com> wrote: > >> 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 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