Re: [tcpm] STD 7, RFC 9293 on Transmission Control Protocol (TCP)

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
>