Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

STD 7

RFC 9293

Transmission Control Protocol (TCP),August 2022

File formats:

icon for HTMLicon for text fileicon for v3pdficon for XMLicon for inline errata
Also available:XML file for editing
 
Status:
INTERNET STANDARD
Obsoletes:
RFC 793,RFC 879,RFC 2873,RFC 6093,RFC 6429,RFC 6528,RFC 6691
Updates:
RFC 1011,RFC 1122,RFC 5961
Author:
W. Eddy, Ed.
Stream:
IETF
Source:
tcpm (wit)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9293

Discuss this RFC: Send questions or comments to the mailing listtcpm@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9293


Abstract

This document specifies the Transmission Control Protocol (TCP). TCPis an important transport-layer protocol in the Internet protocolstack, and it has continuously evolved over decades of use and growthof the Internet. Over this time, a number of changes have been madeto TCP as it was specified in RFC 793, though these have only beendocumented in a piecemeal fashion. This document collects and bringsthose 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 RFCs1011 and 1122, and it should be considered as a replacement for theportions of those documents dealing with TCP requirements. It alsoupdates RFC 5961 by adding a small clarification in reset handlingwhile in the SYN-RECEIVED state. The TCP header control bits fromRFC 793 have also been updated based on RFC 3168.


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp