draft-ietf-tcpm-tcp-rfc4614bis-08.txt   rfc7414.txt 
TCP Maintenance and Minor Extensions M. Duke Internet Engineering Task Force (IETF) M. Duke
(TCPM) WG F5 Request for Comments: 7414 F5
Internet-Draft R. Braden Obsoletes: 4614 R. Braden
Obsoletes: 4614 (if approved) ISI Category: Informational ISI
Intended status: Informational W. Eddy ISSN: 2070-1721 W. Eddy
Expires: February 13, 2015 MTI Systems MTI Systems
E. Blanton E. Blanton
Interrupt Sciences
A. Zimmermann A. Zimmermann
NetApp, Inc. NetApp, Inc.
August 12, 2014 February 2015
A Roadmap for Transmission Control Protocol (TCP) Specification A Roadmap for Transmission Control Protocol (TCP)
Documents Specification Documents
draft-ietf-tcpm-tcp-rfc4614bis-08
Abstract Abstract
This document contains a "roadmap" to the Requests for Comments (RFC) This document contains a roadmap to the Request for Comments (RFC)
documents relating to the Internet's Transmission Control Protocol documents relating to the Internet's Transmission Control Protocol
(TCP). This roadmap provides a brief summary of the documents (TCP). This roadmap provides a brief summary of the documents
defining TCP and various TCP extensions that have accumulated in the defining TCP and various TCP extensions that have accumulated in the
RFC series. This serves as a guide and quick reference for both TCP RFC series. This serves as a guide and quick reference for both TCP
implementers and other parties who desire information contained in implementers and other parties who desire information contained in
the TCP-related RFCs. the TCP-related RFCs.
This document obsoletes RFC 4614. This document obsoletes RFC 4614.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This document is not an Internet Standards Track specification; it is
Task Force (IETF). Note that other groups may also distribute published for informational purposes.
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
This Internet-Draft will expire on February 13, 2015. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7414.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction ....................................................4
2. Core Functionality . . . . . . . . . . . . . . . . . . . . . . 5 2. Core Functionality ..............................................6
3. Strongly Encouraged Enhancements . . . . . . . . . . . . . . . 8 3. Strongly Encouraged Enhancements ................................8
3.1. Fundamental Changes . . . . . . . . . . . . . . . . . . . 8 3.1. Fundamental Changes ........................................9
3.2. Congestion Control Extensions . . . . . . . . . . . . . . 9 3.2. Congestion Control Extensions .............................10
3.3. Loss Recovery Extensions . . . . . . . . . . . . . . . . . 11 3.3. Loss Recovery Extensions ..................................11
3.4. Detection and Prevention of Spurious Retransmissions . . . 12 3.4. Detection and Prevention of Spurious Retransmissions ......13
3.5. Path MTU Discovery . . . . . . . . . . . . . . . . . . . . 13 3.5. Path MTU Discovery ........................................14
3.6. Header Compression . . . . . . . . . . . . . . . . . . . . 14 3.6. Header Compression ........................................15
3.7. Defending Spoofing and Flooding Attacks . . . . . . . . . 15 3.7. Defending Spoofing and Flooding Attacks ...................15
4. Experimental Extensions . . . . . . . . . . . . . . . . . . . 17 4. Experimental Extensions ........................................17
4.1. Architectural Guidelines . . . . . . . . . . . . . . . . . 17 4.1. Architectural Guidelines ..................................18
4.2. Fundamental Changes . . . . . . . . . . . . . . . . . . . 18 4.2. Fundamental Changes .......................................18
4.3. Congestion Control Extensions . . . . . . . . . . . . . . 18 4.3. Congestion Control Extensions .............................19
4.4. Loss Recovery Extensions . . . . . . . . . . . . . . . . . 20 4.4. Loss Recovery Extensions ..................................20
4.5. Detection and Prevention of Spurious Retransmissions . . . 20 4.5. Detection and Prevention of Spurious Retransmissions ......21
4.6. TCP Timeouts . . . . . . . . . . . . . . . . . . . . . . . 21 4.6. TCP Timeouts ..............................................22
4.7. Multipath TCP . . . . . . . . . . . . . . . . . . . . . . 21 4.7. Multipath TCP .............................................22
5. TCP Parameters at IANA . . . . . . . . . . . . . . . . . . . . 22 5. TCP Parameters at IANA .........................................23
6. Historic and Undeployed Extensions . . . . . . . . . . . . . . 23 6. Historic and Undeployed Extensions .............................24
7. Support Documents . . . . . . . . . . . . . . . . . . . . . . 26 7. Support Documents ..............................................27
7.1. Foundational Works . . . . . . . . . . . . . . . . . . . . 26 7.1. Foundational Works ........................................27
7.2. Architectural Guidelines . . . . . . . . . . . . . . . . . 28 7.2. Architectural Guidelines ..................................29
7.3. Difficult Network Environments . . . . . . . . . . . . . . 29 7.3. Difficult Network Environments ............................30
7.4. Guidance for Developing, Analyzing, and Evaluating TCP . . 32 7.4. Guidance for Developing, Analyzing, and Evaluating TCP ....33
7.5. Implementation Advice . . . . . . . . . . . . . . . . . . 33 7.5. Implementation Advice .....................................34
7.6. Tools and Tutorials . . . . . . . . . . . . . . . . . . . 35 7.6. Tools and Tutorials .......................................36
7.7. MIB Modules . . . . . . . . . . . . . . . . . . . . . . . 36 7.7. MIB Modules ...............................................37
7.8. Case Studies . . . . . . . . . . . . . . . . . . . . . . . 37 7.8. Case Studies ..............................................39
8. Undocumented TCP Features . . . . . . . . . . . . . . . . . . 38 8. Undocumented TCP Features ......................................40
9. Security Considerations . . . . . . . . . . . . . . . . . . . 40 9. Security Considerations ........................................41
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40 10. References ....................................................42
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 40 10.1. Normative References .....................................42
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 40 10.2. Informative References ...................................53
12.1. Normative References . . . . . . . . . . . . . . . . . . . 40 Acknowledgments ...................................................56
12.2. Informative References . . . . . . . . . . . . . . . . . . 50 Authors' Addresses ................................................57
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 51
1. Introduction 1. Introduction
A correct and efficient implementation of the Transmission Control A correct and efficient implementation of the Transmission Control
Protocol (TCP) is a critical part of the software of most Internet Protocol (TCP) is a critical part of the software of most Internet
hosts. As TCP has evolved over the years, many distinct documents hosts. As TCP has evolved over the years, many distinct documents
have become part of the accepted standard for TCP. At the same time, have become part of the accepted standard for TCP. At the same time,
a large number of experimental modifications to TCP have also been a large number of experimental modifications to TCP have also been
published in the RFC series, along with informational notes, case published in the RFC series, along with informational notes, case
studies, and other advice. studies, and other advice.
As an introduction to newcomers and an attempt to organize the As an introduction to newcomers and an attempt to organize the
plethora of information for old hands, this document contains a plethora of information for old hands, this document contains a
"roadmap" to the TCP-related RFCs. It provides a brief summary of roadmap to the TCP-related RFCs. It provides a brief summary of the
the RFC documents that define TCP. This should provide guidance to RFC documents that define TCP. This should provide guidance to
implementers on the relevance and significance of the standards-track implementers on the relevance and significance of the standards-track
extensions, informational notes, and best current practices that extensions, informational notes, and best current practices that
relate to TCP. relate to TCP.
This document is not an update of RFC 1122 [RFC1122] and is not a This document is not an update of RFC 1122 [RFC1122] and is not a
rigorous standard for what needs to be implemented in TCP. This rigorous standard for what needs to be implemented in TCP. This
document is merely an informational roadmap that captures, organizes, document is merely an informational roadmap that captures, organizes,
and summarizes most of the RFC documents that a TCP implementer, and summarizes most of the RFC documents that a TCP implementer,
experimenter, or student should be aware of. Particular comments or experimenter, or student should be aware of. Particular comments or
broad categorizations that this document makes about individual broad categorizations that this document makes about individual
skipping to change at page 4, line 40 skipping to change at page 4, line 40
should the content of this document alone influence implementation should the content of this document alone influence implementation
decisions. decisions.
This roadmap includes a brief description of the contents of each This roadmap includes a brief description of the contents of each
TCP-related RFC. In some cases, we simply supply the abstract or a TCP-related RFC. In some cases, we simply supply the abstract or a
key summary sentence from the text as a terse description. In key summary sentence from the text as a terse description. In
addition, a letter code after an RFC number indicates its category in addition, a letter code after an RFC number indicates its category in
the RFC series (see BCP 9 [RFC2026] for explanation of these the RFC series (see BCP 9 [RFC2026] for explanation of these
categories): categories):
S - Standards Track (Proposed Standard, Draft Standard, or S - Standards Track (Proposed Standard, Draft Standard, or Internet
Internet Standard) Standard)
E - Experimental
I - Informational E - Experimental
H - Historic I - Informational
B - Best Current Practice H - Historic
U - Unknown (not formally defined) B - Best Current Practice
U - Unknown (not formally defined)
Note that the category of an RFC does not necessarily reflect its Note that the category of an RFC does not necessarily reflect its
current relevance. For instance, RFC 5681 [RFC5681] is considered current relevance. For instance, RFC 5681 [RFC5681] is considered
part of the required core functionality of TCP, although the RFC is part of the required core functionality of TCP, although the RFC is
only a Draft Standard. Similarly, some Informational RFCs contain only a Draft Standard. Similarly, some Informational RFCs contain
significant technical proposals for changing TCP. significant technical proposals for changing TCP.
Finally, if an error in the technical content has been found after Finally, if an error in the technical content has been found after
publication of an RFC, this fact is indicated by the term "(Errata)" publication of an RFC (at the time of this writing), this fact is
in the headline of the RFC's description. The contents of the errata indicated by the term "(Errata)" in the headline of the RFC's
can be found at the RFC editor home page [Errata]. description. The contents of the errata can be found through the RFC
Errata page [Errata].
This roadmap is divided into three main sections. Section 2 lists This roadmap is divided into three main sections. Section 2 lists
the RFCs that describe absolutely required TCP behaviors for proper the RFCs that describe absolutely required TCP behaviors for proper
functioning and interoperability. Further RFCs that describe functioning and interoperability. Further RFCs that describe
strongly encouraged, but non-essential, behaviors are listed in strongly encouraged, but nonessential, behaviors are listed in
Section 3. Experimental extensions that are not yet standard Section 3. Experimental extensions that are not yet standard
practices, but that potentially could be in the future, are described practices, but that potentially could be in the future, are described
in Section 4. in Section 4.
The reader will probably notice that these three sections are broadly The reader will probably notice that these three sections are broadly
equivalent to MUST/SHOULD/MAY specifications (per RFC 2119 equivalent to MUST/SHOULD/MAY specifications (per RFC 2119
[RFC2119]), and although the authors support this intuition, this [RFC2119]), and although the authors support this intuition, this
document is merely descriptive; it does not represent a binding document is merely descriptive; it does not represent a binding
standards-track position. Individual implementers still need to Standards Track position. Individual implementers still need to
examine the standards documents themselves to evaluate specific examine the Standards Track RFCs themselves to evaluate specific
requirement levels. requirement levels.
Section 5 describes both the procedures that the Internet Assigned Section 5 describes both the procedures that the Internet Assigned
Numbers Authority (IANA) uses and an RFC author should follow when Numbers Authority (IANA) uses and an RFC author should follow when
new TCP parameters are requested and finally assigned. new TCP parameters are requested and finally assigned.
A small number of older experimental extensions that have not been A small number of older experimental extensions that have not been
widely implemented, deployed, and used are noted in Section 6. Many widely implemented, deployed, and used are noted in Section 6. Many
other supporting documents that are relevant to the development, other supporting documents that are relevant to the development,
implementation, and deployment of TCP are described in Section 7. implementation, and deployment of TCP are described in Section 7.
skipping to change at page 6, line 9 skipping to change at page 6, line 14
2. Core Functionality 2. Core Functionality
A small number of documents compose the core specification of TCP. A small number of documents compose the core specification of TCP.
These define the required core functionalities of TCP's header These define the required core functionalities of TCP's header
parsing, state machine, congestion control, and retransmission parsing, state machine, congestion control, and retransmission
timeout computation. These base specifications must be correctly timeout computation. These base specifications must be correctly
followed for interoperability. followed for interoperability.
RFC 793 S: "Transmission Control Protocol", STD 7 (September 1981) RFC 793 S: "Transmission Control Protocol", STD 7 (September 1981)
(Errata) (Errata)
This is the fundamental TCP specification document [RFC0793]. This is the fundamental TCP specification document [RFC793].
Written by Jon Postel as part of the Internet protocol suite's Written by Jon Postel as part of the Internet protocol suite's
core, it describes the TCP packet format, the TCP state machine core, it describes the TCP packet format, the TCP state machine
and event processing, and TCP's semantics for data transmission, and event processing, and TCP's semantics for data transmission,
reliability, flow control, multiplexing, and acknowledgment. reliability, flow control, multiplexing, and acknowledgment.
Section 3.6 of RFC 793, describing TCP's handling of the IP Section 3.6 of RFC 793, describing TCP's handling of the IP
precedence and security compartment, is mostly irrelevant today. precedence and security compartment, is mostly irrelevant today.
RFC 2873 (see Section 2) changed the IP precedence handling, and RFC 2873 (discussed later in Section 2 below) changed the IP
the security compartment portion of the API is no longer precedence handling, and the security compartment portion of the
implemented or used. In addition, RFC 793 did not describe any API is no longer implemented or used. In addition, RFC 793 did
congestion control mechanism. Otherwise, however, the majority of not describe any congestion control mechanism. Otherwise,
this document still accurately describes modern TCPs. RFC 793 is however, the majority of this document still accurately describes
the last of a series of developmental TCP specifications, starting modern TCPs. RFC 793 is the last of a series of developmental TCP
in the Internet Experimental Notes (IENs) and continuing in the specifications, starting in the Internet Experimental Notes (IENs)
RFC series. and continuing in the RFC series.
RFC 1122 S: "Requirements for Internet Hosts - Communication Layers" RFC 1122 S: "Requirements for Internet Hosts - Communication Layers"
(October 1989) (October 1989)
This document [RFC1122] updates and clarifies RFC 793 (see This document [RFC1122] updates and clarifies RFC 793 (see above
Section 2), fixing some specification bugs and oversights. It in Section 2), fixing some specification bugs and oversights. It
also explains some features such as keep-alives and Karn's and also explains some features such as keep-alives and Karn's and
Jacobson's RTO estimation algorithms [KP87][Jac88][JK92]. ICMP Jacobson's RTO estimation algorithms [KP87][Jac88][JK92]. ICMP
interactions are mentioned, and some tips are given for efficient interactions are mentioned, and some tips are given for efficient
implementation. RFC 1122 is an Applicability Statement, listing implementation. RFC 1122 is an Applicability Statement, listing
the various features that MUST, SHOULD, MAY, SHOULD NOT, and MUST the various features that MUST, SHOULD, MAY, SHOULD NOT, and MUST
NOT be present in standards-conforming TCP implementations. NOT be present in standards-conforming TCP implementations.
Unlike a purely informational "roadmap", this Applicability Unlike a purely informational roadmap, this Applicability
Statement is a standards document and gives formal rules for Statement is a standards document and gives formal rules for
implementation. implementation.
RFC 2460 S: "Internet Protocol, Version 6 (IPv6) Specification" RFC 2460 S: "Internet Protocol, Version 6 (IPv6) Specification"
(December 1998) (Errata) (December 1998) (Errata)
This document [RFC2460] is of relevance to TCP because it defines This document [RFC2460] is of relevance to TCP because it defines
how the pseudo-header for TCP's checksum computation is derived how the pseudo-header for TCP's checksum computation is derived
when 128-bit IPv6 addresses are used instead of 32-bit IPv4 when 128-bit IPv6 addresses are used instead of 32-bit IPv4
addresses. Additionally, RFC 2675 (see Section 3.1) describes TCP addresses. Additionally, RFC 2675 (see Section 3.1 of this
changes required to support IPv6 jumbograms. document) describes TCP changes required to support IPv6
jumbograms.
RFC 2873 S: "TCP Processing of the IPv4 Precedence Field" (June 2000) RFC 2873 S: "TCP Processing of the IPv4 Precedence Field" (June 2000)
(Errata) (Errata)
This document [RFC2873] removes from the TCP specification all This document [RFC2873] removes from the TCP specification all
processing of the precedence bits of the TOS byte of the IP processing of the precedence bits of the TOS byte of the IP
header. This resolves a conflict over the use of these bits header. This resolves a conflict over the use of these bits
between RFC 793 Section 2 and Differentiated Services [RFC2474]. between RFC 793 (see above in Section 2) and Differentiated
Services [RFC2474].
RFC 5681 S: "TCP Congestion Control" (August 2009) RFC 5681 S: "TCP Congestion Control" (August 2009)
Although RFC 793 (see Section 2) did not contain any congestion Although RFC 793 (see above in Section 2) did not contain any
control mechanisms, today congestion control is a required congestion control mechanisms, today congestion control is a
component of TCP implementations. This document [RFC5681] defines required component of TCP implementations. This document
congestion avoidance and control mechanism for TCP, based on Van [RFC5681] defines congestion avoidance and control mechanism for
Jacobson's 1988 SIGCOMM paper [Jac88]. TCP, based on Van Jacobson's 1988 SIGCOMM paper [Jac88].
A number of behaviors that together constitute what the community A number of behaviors that together constitute what the community
refers to as "Reno TCP" is described in RFC 5681. The name "Reno" refers to as "Reno TCP" is described in RFC 5681. The name "Reno"
comes from the Net/2 release of the 4.3 BSD operating system. comes from the Net/2 release of the 4.3 BSD operating system.
This is generally regarded as the least common denominator among This is generally regarded as the least common denominator among
TCP flavors currently found running on Internet hosts. Reno TCP TCP flavors currently found running on Internet hosts. Reno TCP
includes the congestion control features of slow start, congestion includes the congestion control features of slow start, congestion
avoidance, fast retransmit, and fast recovery. avoidance, fast retransmit, and fast recovery.
RFC 5681 details the currently accepted congestion control RFC 5681 details the currently accepted congestion control
mechanism, while RFC 1122 Section 2 mandates that such a mechanism, while RFC 1122, (see above in Section 2) mandates that
congestion control mechanism must be implemented. RFC 5681 such a congestion control mechanism must be implemented. RFC 5681
differs slightly from the other documents listed in this section, differs slightly from the other documents listed in this section,
as it does not affect the ability of two TCP endpoints to as it does not affect the ability of two TCP endpoints to
communicate; however, congestion control remains a critical communicate; however, congestion control remains a critical
component of any widely deployed TCP implementation and is component of any widely deployed TCP implementation and is
required for the avoidance of congestion collapse and to ensure required for the avoidance of congestion collapse and to ensure
fairness among competing flows. fairness among competing flows.
RFC 2001 and RFC 2581 are the conceptual precursors of RFC 5681. RFCs 2001 and 2581 are the conceptual precursors of RFC 5681. The
The most important changes relative to RFC 2581 are: most important changes relative to RFC 2581 are:
(a) The initial window requirements were changed to allow larger (a) The initial window requirements were changed to allow larger
Initial Windows as standardized in [RFC3390] (see Initial Windows as standardized in [RFC3390] (see Section 3.2
Section 3.2). of this document).
(b) During slow start and congestion avoidance, the usage of (b) During slow start and congestion avoidance, the usage of
Appropriate Byte Counting [RFC3465] (see Section 3.2) is Appropriate Byte Counting [RFC3465] (see Section 3.2 of this
explicitly recommended. document) is explicitly recommended.
(c) The use of Limited Transmit [RFC3042] (see Section 3.3) is (c) The use of Limited Transmit [RFC3042] (see Section 3.3 of
now recommended. this document) is now recommended.
RFC 6093 S: "On the Implementation of the TCP Urgent Mechanism" RFC 6093 S: "On the Implementation of the TCP Urgent Mechanism"
(January 2011) (January 2011)
This document [RFC6093] analyzes how current TCP stacks process This document [RFC6093] analyzes how current TCP stacks process
TCP urgent indications, and how the behavior of widely deployed TCP urgent indications, and how the behavior of widely deployed
middleboxes affects the urgent indications processing. The middleboxes affects the urgent indications processing. The
document updates the relevant specifications such that it document updates the relevant specifications such that it
accommodates current practice in processing TCP urgent accommodates current practice in processing TCP urgent
indications. Finally, the document raises awareness about the indications. Finally, the document raises awareness about the
reliability of TCP urgent indications in the Internet, and reliability of TCP urgent indications in the Internet, and
recommends against the use of urgent mechanism. recommends against the use of urgent mechanism.
RFC 6298 S: "Computing TCP's Retransmission Timer" (June 2011) RFC 6298 S: "Computing TCP's Retransmission Timer" (June 2011)
Abstract: "This document defines the standard algorithm that Abstract of RFC 6298 [RFC6298]: "This document defines the
Transmission Control Protocol (TCP) senders are required to use to standard algorithm that Transmission Control Protocol (TCP)
compute and manage their retransmission timer. It expands on the senders are required to use to compute and manage their
discussion in section 4.2.3.1 of RFC 1122 (see Section 2) and retransmission timer. It expands on the discussion in
upgrades the requirement of supporting the algorithm from a SHOULD Section 4.2.3.1 of RFC 1122 and upgrades the requirement of
to a MUST." [RFC6298]. RFC 6298 updates RFC 2988 by changing the supporting the algorithm from a SHOULD to a MUST." RFC 6298
initial RTO from 3s to 1s updates RFC 2988 by changing the initial RTO from 3s to 1s.
RFC 6691 I: "TCP Options and Maximum Segment Size (MSS)" (July 2012) RFC 6691 I: "TCP Options and Maximum Segment Size (MSS)" (July 2012)
This document [RFC6691] clarifies what value to use with the TCP This document [RFC6691] clarifies what value to use with the TCP
Maximum Segment Size (MSS) option when IP and TCP options are in Maximum Segment Size (MSS) option when IP and TCP options are in
use. use.
3. Strongly Encouraged Enhancements 3. Strongly Encouraged Enhancements
This section describes recommended TCP modifications that improve This section describes recommended TCP modifications that improve
performance and security. Section 3.1 represents fundamental changes performance and security. Section 3.1 represents fundamental changes
to the protocol. Section 3.2 and Section 3.3 list improvements over to the protocol. Sections 3.2 and 3.3 list improvements over the
the congestion control and loss recovery mechanisms as specified in congestion control and loss recovery mechanisms as specified in RFC
RFC 5681 (see Section 2). Section 3.4 describes algorithms that 5681 (see Section 2). Section 3.4 describes algorithms that allow a
allow a TCP sender to detect whether it has entered loss recovery TCP sender to detect whether it has entered loss recovery spuriously.
spuriously. Section 3.5 comprises Path MTU Discovery mechanisms.
Schemes for TCP/IP header compression are listed in Section 3.6. Section 3.5 comprises Path MTU Discovery mechanisms. Schemes for
Finally, Section 3.7 deals with the problem of preventing acceptance TCP/IP header compression are listed in Section 3.6. Finally,
of forged segments and flooding attacks. Section 3.7 deals with the problem of preventing acceptance of forged
segments and flooding attacks.
3.1. Fundamental Changes 3.1. Fundamental Changes
RFCs 2675 and 7323 represent fundamental changes to TCP by redefining RFCs 2675 and 7323 represent fundamental changes to TCP by redefining
how parts of the basic TCP header and options are interpreted. RFC how parts of the basic TCP header and options are interpreted. RFC
7323 defines the Window Scale Option, which re-interprets the 7323 defines the Window Scale option, which reinterprets the
advertised receive window. RFC 2675 specifies that MSS option and advertised receive window. RFC 2675 specifies that MSS option and
urgent pointer fields with a value of 65,535 are to be treated urgent pointer fields with a value of 65,535 are to be treated
specially. specially.
RFC 2675 S: "IPv6 Jumbograms" (August 1999) (Errata) RFC 2675 S: "IPv6 Jumbograms" (August 1999) (Errata)
IPv6 supports longer datagrams than were allowed in IPv4. These IPv6 supports longer datagrams than were allowed in IPv4. These
are known as jumbograms, and use with TCP has necessitated changes are known as jumbograms, and use with TCP has necessitated changes
to the handling of TCP's MSS and Urgent fields (both 16 bits). to the handling of TCP's MSS and Urgent fields (both 16 bits).
This document [RFC2675] explains those changes. Although it This document [RFC2675] explains those changes. Although it
skipping to change at page 9, line 29 skipping to change at page 9, line 41
interoperability with other TCP implementations when IPv4 or non- interoperability with other TCP implementations when IPv4 or non-
jumbogram IPv6 is used. This document states that jumbograms are jumbogram IPv6 is used. This document states that jumbograms are
to only be used when it can be guaranteed that all receiving to only be used when it can be guaranteed that all receiving
nodes, including each router in the end-to-end path, will support nodes, including each router in the end-to-end path, will support
jumbograms. If even a single node that does not support jumbograms. If even a single node that does not support
jumbograms is attached to a local network, then no host on that jumbograms is attached to a local network, then no host on that
network may use jumbograms. This explains why jumbogram use has network may use jumbograms. This explains why jumbogram use has
been rare, and why this document is considered a performance been rare, and why this document is considered a performance
optimization and not part of TCP over IPv6's basic functionality. optimization and not part of TCP over IPv6's basic functionality.
RFC 7323 S: "TCP Extensions for High Performance" (July 2014) RFC 7323 S: "TCP Extensions for High Performance" (September 2014)
This document [I-D.ietf-tcpm-1323bis] defines TCP extensions for This document [RFC7323] defines TCP extensions for window scaling,
window scaling, timestamps, and protection against wrapped timestamps, and protection against wrapped sequence numbers, for
sequence numbers, for efficient and safe operation over paths with efficient and safe operation over paths with large bandwidth-delay
large bandwidth-delay products. These extensions are commonly products. These extensions are commonly found in currently used
found in currently used systems. The predecessor of this systems. The predecessor of this document, RFC 1323, was
document, RFC 1323, was published in 1992, and is deployed in most published in 1992, and is deployed in most TCP implementations.
TCP implementations. This document includes fixes and This document includes fixes and clarifications based on the
clarifications based on the gained deployment experience. One gained deployment experience. One specific issued addressed in
specific issued addressed in this specification is a this specification is a recommendation how to modify the algorithm
recommendation how to modify the algorithm for estimating the mean for estimating the mean RTT when timestamps are used. RFCs 1072,
RTT when timestamps are used. RFC 1072, RFC 1185, and RFC 1323 1185, and 1323 are the conceptual precursors of RFC 7323.
are the conceptual precursors of RFC 7323.
3.2. Congestion Control Extensions 3.2. Congestion Control Extensions
Two of the most important aspects of TCP are its congestion control Two of the most important aspects of TCP are its congestion control
and loss recovery features. TCP treats lost packets as indicating and loss recovery features. TCP treats lost packets as indicating
congestion-related loss, and cannot distinguish between congestion- congestion-related loss and cannot distinguish between congestion-
related loss and loss due to transmission errors. Even when ECN is related loss and loss due to transmission errors. Even when ECN is
in use, there is a rather intimate coupling between congestion in use, there is a rather intimate coupling between congestion
control and loss recovery mechanisms. There are several extensions control and loss recovery mechanisms. There are several extensions
to both features, and more often than not, a particular extension to both features, and more often than not, a particular extension
applies to both. In these two sub-sections, we group enhancements to applies to both. In these two subsections, we group enhancements to
TCP's congestion control, while the next sub-section focus on TCP's TCP's congestion control, while the next subsection focus on TCP's
loss recovery. loss recovery.
RFC 3168 S: "The Addition of Explicit Congestion Notification (ECN) RFC 3168 S: "The Addition of Explicit Congestion Notification (ECN)
to IP" (September 2001) to IP" (September 2001)
This document [RFC3168] defines a means for end hosts to detect This document [RFC3168] defines a means for end hosts to detect
congestion before congested routers are forced to discard packets. congestion before congested routers are forced to discard packets.
Although congestion notification takes place at the IP level, ECN Although congestion notification takes place at the IP level, ECN
requires support at the transport level (e.g., in TCP) to echo the requires support at the transport level (e.g., in TCP) to echo the
bits and adapt the sending rate. This document updates RFC 793 bits and adapt the sending rate. This document updates RFC 793
(see Section 2) to define two previously unused flag bits in the (see Section 2 of this document) to define two previously unused
TCP header for ECN support. RFC 3540 (see Section 4.3) provides a flag bits in the TCP header for ECN support. RFC 3540 (see
supplementary (experimental) means for more secure use of ECN, and Section 4.3 of this document) provides a supplementary
RFC 2884 (see Section 7.8) provides some sample results from using (experimental) means for more secure use of ECN, and RFC 2884 (see
ECN. Section 7.8 of this document) provides some sample results from
using ECN.
RFC 3390 S: "Increasing TCP's Initial Window" (October 2002) RFC 3390 S: "Increasing TCP's Initial Window" (October 2002)
This document [RFC3390] specifies an increase in the permitted This document [RFC3390] specifies an increase in the permitted
initial window for TCP from one segment to three or four segments initial window for TCP from one segment to three or four segments
during the slow start phase, depending on the segment size. during the slow start phase, depending on the segment size.
RFC 3465 E: "TCP Congestion Control with Appropriate Byte Counting RFC 3465 E: "TCP Congestion Control with Appropriate Byte Counting
(ABC)" (February 2003) (ABC)" (February 2003)
This document [RFC3465] suggests that congestion control use the This document [RFC3465] suggests that congestion control use the
number of bytes acknowledged instead of the number of number of bytes acknowledged instead of the number of
acknowledgments received. This change improves the performance of acknowledgments received. This change improves the performance of
TCP in situations where is no one-to-one relationship between data TCP in situations where there is no one-to-one relationship
segments and acknowledgments (e.g. delayed ACKs or ACK loss) and between data segments and acknowledgments (e.g., delayed ACKs or
closes a security hole TCP receivers can use to induce the sender ACK loss) and closes a security hole TCP receivers can use to
into increasing the sending rate too rapidly (ACK-division induce the sender into increasing the sending rate too rapidly
[SCWA99][RFC3449]). ABC is recommended by RFC 5681 (see (ACK-division [SCWA99] [RFC3449]). ABC is recommended by RFC 5681
Section 2). (see Section 2 of this document).
RFC 6633 S: "Deprecation of ICMP Source Quench Messages" (May 2012) RFC 6633 S: "Deprecation of ICMP Source Quench Messages" (May 2012)
This document [RFC6633] formally deprecates the use of ICMP Source This document [RFC6633] formally deprecates the use of ICMP Source
Quench messages by transport protocols and recommends against the Quench messages by transport protocols and recommends against the
implementation of [RFC1016]. implementation of [RFC1016].
3.3. Loss Recovery Extensions 3.3. Loss Recovery Extensions
For the typical implementation of the TCP fast recovery algorithm For the typical implementation of the TCP fast recovery algorithm
described in RFC 5681 (see Section 2), a TCP sender only retransmits described in RFC 5681 (see Section 2 of this document), a TCP sender
a segment after a retransmit timeout has occurred, or after three only retransmits a segment after a retransmit timeout has occurred,
duplicate ACKs have arrived triggering the fast retransmit. A single or after three duplicate ACKs have arrived triggering the fast
RTO might result in the retransmission of several segments, while the retransmit. A single RTO might result in the retransmission of
fast retransmit algorithm in RFC 5681 leads only to a single several segments, while the fast retransmit algorithm in RFC 5681
retransmission. Hence, multiple losses from a single window of data leads only to a single retransmission. Hence, multiple losses from a
can lead to a performance degradation. Documents listed in this single window of data can lead to a performance degradation.
section aim to improve the overall performance of TCP's standard loss Documents listed in this section aim to improve the overall
recovery algorithms. In particular, some of them allow TCP senders performance of TCP's standard loss recovery algorithms. In
to recover more effectively when multiple segments are lost from a particular, some of them allow TCP senders to recover more
single flight of data. effectively when multiple segments are lost from a single flight of
data.
RFC 2018 S: "TCP Selective Acknowledgment Options" (October 1996) RFC 2018 S: "TCP Selective Acknowledgment Options" (October 1996)
(Errata) (Errata)
When more than one packet is lost during one round trip time TCP When more than one packet is lost during one RTT, TCP may
may experience poor performance since a TCP sender can only learn experience poor performance since a TCP sender can only learn
about a single lost packet per round trip time from cumulative about a single lost packet per RTT from cumulative
acknowledgments. This document [RFC2018] defines the basic acknowledgments. This document [RFC2018] defines the basic
selective acknowledgment (SACK) mechanism for TCP, which can help selective acknowledgment (SACK) mechanism for TCP, which can help
to overcome these limitations. The receiving TCP returns SACK to overcome these limitations. The receiving TCP returns SACK
blocks to inform the sender which data has been received. The blocks to inform the sender which data has been received. The
sender can then retransmit only the missing data segments. sender can then retransmit only the missing data segments.
RFC 3042 S: "Enhancing TCP's Loss Recovery Using Limited Transmit" RFC 3042 S: "Enhancing TCP's Loss Recovery Using Limited Transmit"
(January 2001) (January 2001)
Abstract: "This document proposes Limited Transmit, a new Abstract of RFC 3042 [RFC3042]: "This document proposes a new
Transmission Control Protocol (TCP) mechanism that can be used to Transmission Control Protocol (TCP) mechanism that can be used to
more effectively recover lost segments when a connection's more effectively recover lost segments when a connection's
congestion window is small, or when a large number of segments are congestion window is small, or when a large number of segments are
lost in a single transmission window." [RFC3042] Tests from 2004 lost in a single transmission window." This algorithm described
showed that Limited Transmit was deployed in roughly one third of in RFC 3042 is called "Limited Transmit". Tests from 2004 showed
the web servers tested [MAF04]. Limited Transmit is recommended that Limited Transmit was deployed in roughly one third of the web
by RFC 5681 (see Section 2). servers tested [MAF04]. Limited Transmit is recommended by RFC
5681 (see Section 2 of this document).
RFC 6582 S: "The NewReno Modification to TCP's Fast Recovery RFC 6582 S: "The NewReno Modification to TCP's Fast Recovery
Algorithm" (April 2012) Algorithm" (April 2012)
This document [RFC6582] specifies a modification to the standard This document [RFC6582] specifies a modification to the standard
Reno fast recovery algorithm, whereby a TCP sender can use partial Reno fast recovery algorithm, whereby a TCP sender can use partial
acknowledgments to make inferences determining the next segment to acknowledgments to make inferences determining the next segment to
send in situations where SACK would be helpful but isn't send in situations where SACK would be helpful but isn't
available. Although it is only a slight modification, the NewReno available. Although it is only a slight modification, the NewReno
behavior can make a significant difference in performance when behavior can make a significant difference in performance when
multiple segments are lost from a single window of data. multiple segments are lost from a single window of data.
RFC 2582 and RFC 3782 are the conceptual precursors of RFC 6582. RFCs 2582 and 3782 are the conceptual precursors of RFC 6582. The
The main change in RFC 3782 relative to RFC 2582 was to specify main change in RFC 3782 relative to RFC 2582 was to specify the
the Careful variant of NewReno's Fast Retransmit and Fast Recovery Careful variant of NewReno's Fast Retransmit and Fast Recovery
algorithms and advance those two algorithms from Experimental to algorithms and advance those two algorithms from Experimental to
Standards Track status. The main change in RFC 6582 relative to Standards Track status. The main change in RFC 6582 relative to
RFC 3782 was to solve a performance degradation that could occur RFC 3782 was to solve a performance degradation that could occur
if FlightSize on Full ACK reception is zero. if FlightSize on Full ACK reception is zero.
RFC 6675 S: "A Conservative Loss Recovery Algorithm Based on RFC 6675 S: "A Conservative Loss Recovery Algorithm Based on
Selective Acknowledgment (SACK) for TCP" (August 2012) Selective Acknowledgment (SACK) for TCP" (August 2012)
This document [RFC6675] describes a conservative loss recovery This document [RFC6675] describes a conservative loss recovery
algorithm for TCP that is based on the use of the selective algorithm for TCP that is based on the use of the selective
acknowledgment (SACK) TCP option [RFC2018] (see Section 3.3). The acknowledgment (SACK) TCP option [RFC2018] (see above in
algorithm conforms to the spirit of the congestion control Section 3.3). The algorithm conforms to the spirit of the
specification in RFC 5681 (see Section 2), but allows TCP senders congestion control specification in RFC 5681 (see Section 2 of
to recover more effectively when multiple segments are lost from a this document), but allows TCP senders to recover more effectively
single flight of data. when multiple segments are lost from a single flight of data.
RFC 6675 is a revision of RFC 3517 to address several situations RFC 6675 is a revision of RFC 3517 to address several situations
that are not handled explicitly before. In particular that are not handled explicitly before. In particular,
(a) it improves the loss detection in the event that the sender (a) it improves the loss detection in the event that the sender
has outstanding segments that are smaller than SMSS. has outstanding segments that are smaller than Sender Maximum
Segment Size (SMSS).
(b) it modifies the definition of a "duplicate acknowledgment" to (b) it modifies the definition of a "duplicate acknowledgment" to
utilize the SACK information in detecting loss. utilize the SACK information in detecting loss.
(c) it maintains the ACK clock under certain circumstances (c) it maintains the ACK clock under certain circumstances
involving loss at the end of the window. involving loss at the end of the window.
3.4. Detection and Prevention of Spurious Retransmissions 3.4. Detection and Prevention of Spurious Retransmissions
Spurious retransmission timeouts are harmful to TCP performance and Spurious retransmission timeouts are harmful to TCP performance and
multiple algorithms have been defined for detecting when spurious multiple algorithms have been defined for detecting when spurious
retransmissions have occurred, and then responding differently in retransmissions have occurred, but they respond differently with
order to recover performance. The IETF defined multiple algorithms regard to their manners of recovering performance. The IETF defined
because there are tradeoffs in whether or not certain TCP options multiple algorithms because there are trade-offs in whether or not
need to be implemented, and concerns about IPR status. The Standards certain TCP options need to be implemented and concerns about IPR
Track documents in this section are closely related to the status. The Standards Track RFCs in this section are closely related
Experimental documents in Section 4.5 also addressing this topic. to the Experimental RFCs in Section 4.5 also addressing this topic.
RFC 2883 S: "An Extension to the Selective Acknowledgement (SACK) RFC 2883 S: "An Extension to the Selective Acknowledgement (SACK)
Option for TCP" (July 2000) Option for TCP" (July 2000)
This document [RFC2883] extends RFC 2018 (see Section 3.3). It This document [RFC2883] extends RFC 2018 (see Section 3.3 of this
enables use of the SACK option to acknowledge duplicate packets. document). It enables use of the SACK option to acknowledge
With this extension, called DSACK, the sender is able to infer the duplicate packets. With this extension, called DSACK, the sender
order of packets received at the receiver, and therefore to infer is able to infer the order of packets received at the receiver
when it has unnecessarily retransmitted a packet. A TCP sender and, therefore, to infer when it has unnecessarily retransmitted a
could then use this information to detect spurious retransmissions packet. A TCP sender could then use this information to detect
(see [RFC3708]. spurious retransmissions (see [RFC3708]).
RFC 4015 S: "The Eifel Response Algorithm for TCP" (February 2005) RFC 4015 S: "The Eifel Response Algorithm for TCP" (February 2005)
This document [RFC4015] describes the response portion of the This document [RFC4015] describes the response portion of the
Eifel algorithm, which can be used in conjunction with one of Eifel algorithm, which can be used in conjunction with one of
several methods of detecting when loss recovery has been several methods of detecting when loss recovery has been
spuriously entered, such as the Eifel detection algorithm in RFC spuriously entered, such as the Eifel detection algorithm in RFC
3522 (see Section 4.5), the algorithm in RFC 3708 (see 3522 (see Section 4.5), the algorithm in RFC 3708 (see Section 4.5
Section 4.5), or F-RTO in RFC 5682 (see Section 3.4). of this document), or F-RTO in RFC 5682 (see below in
Section 3.4).
Abstract: "Based on an appropriate detection algorithm, the Eifel Abstract of RFC 4015 [RFC4015]: "Based on an appropriate detection
response algorithm provides a way for a TCP sender to respond to a algorithm, the Eifel response algorithm provides a way for a TCP
detected spurious timeout. It adapts the retransmission timer to sender to respond to a detected spurious timeout. It adapts the
avoid further spurious timeouts, and can avoid - depending on the retransmission timer to avoid further spurious timeouts and
detection algorithm - the often unnecessary go-back-N retransmits (depending on the detection algorithm) can avoid the often
that would otherwise be sent. In addition, the Eifel response unnecessary go-back-N retransmits that would otherwise be sent.
algorithm restores the congestion control state in such a way that In addition, the Eifel response algorithm restores the congestion
packet bursts are avoided." control state in such a way that packet bursts are avoided."
RFC 5682 S: "Forward RTO-Recovery (F-RTO): An Algorithm for Detecting RFC 5682 S: "Forward RTO-Recovery (F-RTO): An Algorithm for Detecting
Spurious Retransmission Timeouts with TCP" (September 2009) Spurious Retransmission Timeouts with TCP" (September
2009)
The F-RTO detection algorithm [RFC5682], originally described in The F-RTO detection algorithm [RFC5682], originally described in
RFC 4138, provides an option for inferring spurious retransmission RFC 4138, provides an option for inferring spurious retransmission
timeouts. Unlike some similar detection methods (e.g. RFC 3522 timeouts. Unlike some similar detection methods (e.g., RFCs 3522
in Section 4.5 and RFC 3708 in Section 4.5), F-RTO does not rely and 3708, both listed in Section 4.5 of this document), F-RTO does
on the use of any TCP options. The basic idea is to send not rely on the use of any TCP options. The basic idea is to send
previously unsent data after the first retransmission after a RTO. previously unsent data after the first retransmission after a RTO.
If the ACKs advance the window, the RTO may be declared spurious. If the ACKs advance the window, the RTO may be declared spurious.
3.5. Path MTU Discovery 3.5. Path MTU Discovery
The MTUs supported by different links and tunnels within the Internet The MTUs supported by different links and tunnels within the Internet
can vary widely. Fragmentation of packets larger than the supported can vary widely. Fragmentation of packets larger than the supported
MTU on a hop is undesirable. As TCP is the segmentation layer for MTU on a hop is undesirable. As TCP is the segmentation layer for
dividing an application's bytestream into IP packet payloads, TCP dividing an application's byte stream into IP packet payloads, TCP
implementations generally include Path MTU Discovery (PMTUD) implementations generally include Path MTU Discovery (PMTUD)
mechanisms in order to maximize the size of segments they send, mechanisms in order to maximize the size of segments they send,
without causing fragmentation within the network. Some algorithms without causing fragmentation within the network. Some algorithms
may utilize signaling from routers on the path that the MTU has been may utilize signaling from routers on the path to determine that the
exceeded. MTU on some part of the path has been exceeded.
RFC 1191 S: "Path MTU Discovery" (November 1990) RFC 1191 S: "Path MTU Discovery" (November 1990)
Abstract: "This memo describes a technique for dynamically Abstract of RFC 1191 [RFC1191]: "This memo describes a technique
discovering the MTU of an arbitrary Internet path. It specifies a for dynamically discovering the maximum transmission unit (MTU) of
small change to the way routers generate one type of ICMP message. an arbitrary internet path. It specifies a small change to the
For a path that passes through a router that has not been so way routers generate one type of ICMP message. For a path that
changed, this technique might not discover the correct path MTU, passes through a router that has not been so changed, this
but it will always choose a path MTU as accurate as, and in many technique might not discover the correct Path MTU, but it will
cases more accurate than, the path MTU that would be chosen by always choose a Path MTU as accurate as, and in many cases more
current practice." [RFC1191] accurate than, the Path MTU that would be chosen by current
practice."
RFC 1981 S: "Path MTU Discovery for IP version 6" (August 1996) RFC 1981 S: "Path MTU Discovery for IP version 6" (August 1996)
Abstract: "This document describes Path MTU Discovery for IP Abstract of RFC 1981 [RFC1981]: "This document describes Path MTU
version 6. It is largely derived from RFC 1191 (see Section 3.5), Discovery for IP version 6. It is largely derived from RFC 1191,
which describes Path MTU Discovery for IP version 4." [RFC1981] which describes Path MTU Discovery for IP version 4."
RFC 4821 S: "Packetization Layer Path MTU Discovery" (March 2007) RFC 4821 S: "Packetization Layer Path MTU Discovery" (March 2007)
Abstract: "This document describes a robust method for Path MTU Abstract of RFC 4821 [RFC4821]: "This document describes a robust
Discovery (PMTUD) that relies on TCP or some other Packetization method for Path MTU Discovery (PMTUD) that relies on TCP or some
Layer to probe an Internet path with progressively larger packets. other Packetization Layer to probe an Internet path with
This method is described as an extension to RFC 1191 (see progressively larger packets. This method is described as an
Section 3.5) and RFC 1981 (see Section 3.5), which specify ICMP- extension to RFC 1191 and RFC 1981, which specify ICMP-based Path
based Path MTU Discovery for IP versions 4 and 6, respectively." MTU Discovery for IP versions 4 and 6, respectively."
[RFC4821]
3.6. Header Compression 3.6. Header Compression
Especially in streaming applications, the overhead of TCP/IP headers Especially in streaming applications, the overhead of TCP/IP headers
could correspond to more then 50% of the total amount of data sent. could correspond to more than 50% of the total amount of data sent.
Such large overheads may be tolerable in wired LANs where capacity is Such large overheads may be tolerable in wired LANs where capacity is
often not an issue, but are excessive for WANs and wireless systems often not an issue, but are excessive for WANs and wireless systems
where bandwidth is scarce. Header compression schemes for TCP/IP where bandwidth is scarce. Header compression schemes for TCP/IP
like "RObust Header Compression (ROHC) can significantly compress like RObust Header Compression (ROHC) can significantly compress this
this overhead. It performs well over links with significant error overhead. It performs well over links with significant error rates
rates and long round-trip times. and long round-trip times.
RFC 1144 S: "Compressing TCP/IP Headers for Low-Speed Serial Links" RFC 1144 S: "Compressing TCP/IP Headers for Low-Speed Serial Links"
(February 1990) (February 1990)
This document [RFC1144] describes a method for compressing the This document [RFC1144] describes a method for compressing the
headers of TCP/IP datagrams to improve performance over low speed headers of TCP/IP datagrams to improve performance over low-speed
serial links. The method described in this document is limited in serial links. The method described in this document is limited in
its handling of TCP options and cannot compress the headers of its handling of TCP options and cannot compress the headers of
SYNs and FINs. SYNs and FINs.
RFC 6846 S: "RObust Header Compression (ROHC): A Profile for TCP/IP RFC 6846 S: "RObust Header Compression (ROHC): A Profile for TCP/IP
(ROHC-TCP)" January 2013) (ROHC-TCP)" (January 2013)
From abstract: "This document specifies a RObust Header From the Abstract of RFC 6846 [RFC6846]: "This document specifies
Compression (ROHC) profile for compression of TCP/IP packets. The a RObust Header Compression (ROHC) profile for compression of TCP/
profile, called ROHC-TCP, provides efficient and robust IP packets. The profile, called ROHC-TCP, provides efficient and
compression of TCP headers, including frequently used TCP options robust compression of TCP headers, including frequently used TCP
such as selective acknowledgments (SACKs) and Timestamps." options such as selective acknowledgments (SACKs) and Timestamps."
[RFC6846] RFC 6846 is the successor of RFC 4996. It fixes a RFC 6846 is the successor of RFC 4996. It fixes a technical issue
technical issue with the SACK compression and clarifies other with the SACK compression and clarifies other compression methods
compression methods used. used.
3.7. Defending Spoofing and Flooding Attacks 3.7. Defending Spoofing and Flooding Attacks
By default, TCP lacks any cryptographic structures to differentiate By default, TCP lacks any cryptographic structures to differentiate
legitimate segments from those spoofed from malicious hosts. legitimate segments from those spoofed from malicious hosts.
Spoofing valid segments requires correctly guessing a number of Spoofing valid segments requires correctly guessing a number of
fields. The documents in this sub-section describe ways to make that fields. The documents in this subsection describe ways to make that
guessing harder, or to prevent it from being able to affect a guessing harder or to prevent it from being able to affect a
connection negatively. connection negatively.
RFC 4953 I: "Defending TCP Against Spoofing Attacks" (July 2007) RFC 4953 I: "Defending TCP Against Spoofing Attacks" (July 2007)
This document [RFC4953] discusses the recently increased This document [RFC4953] discusses the recently increased
vulnerability of long-lived TCP connections, such as BGP vulnerability of long-lived TCP connections, such as BGP
connections, to reset (send RST) spoofing attacks. The document connections, to reset (send RST) spoofing attacks. The document
analyzes the vulnerability, discussing proposed solutions at the analyzes the vulnerability, discussing proposed solutions at the
transport level and their inherent challenges, as well as existing transport level and their inherent challenges, as well as existing
network level solutions and the feasibility of their deployment. network level solutions and the feasibility of their deployment.
RFC 5461 I: "TCP's Reaction to Soft Errors" (February 2009) RFC 5461 I: "TCP's Reaction to Soft Errors" (February 2009)
This document [RFC5461] describes a non-standard but widely This document [RFC5461] describes a nonstandard but widely
implemented modification to TCP's handling of ICMP soft error implemented modification to TCP's handling of ICMP soft error
messages that rejects pending connection-requests when such error messages that rejects pending connection-requests when such error
messages are received. This behavior reduces the likelihood of messages are received. This behavior reduces the likelihood of
long delays between connection-establishment attempts that may long delays between connection-establishment attempts that may
arise in some scenarios. arise in some scenarios.
RFC 4987 I: "TCP SYN Flooding Attacks and Common Mitigations" (August RFC 4987 I: "TCP SYN Flooding Attacks and Common Mitigations" (August
2007) 2007)
This document [RFC4987] describes the well-known TCP SYN flooding This document [RFC4987] describes the well-known TCP SYN flooding
attack. It analyzes and discusses various countermeasures against attack. It analyzes and discusses various countermeasures against
these attacks, including their use and trade-offs. these attacks, including their use and trade-offs.
RFC 5925 S: "The TCP Authentication Option" (May 2010) RFC 5925 S: "The TCP Authentication Option" (June 2010)
This document [RFC5925] describes the TCP Authentication Option This document [RFC5925] describes the TCP Authentication Option
(TCP-AO), which is used to authenticate TCP segments. TCP-AO (TCP-AO), which is used to authenticate TCP segments. TCP-AO
obsoletes the TCP MD5 Signature option of RFC 2385. It supports obsoletes the TCP MD5 Signature option of RFC 2385. It supports
the use of stronger hash functions, protects against replays for the use of stronger hash functions, protects against replays for
long-lived TCP connections (as used, e.g., in BGP and LDP), long-lived TCP connections (as used, e.g., in BGP and LDP),
coordinates key exchanges between endpoints, and provides a more coordinates key exchanges between endpoints, and provides a more
explicit recommendation for external key management. explicit recommendation for external key management.
Cryptographic algorithms for TCP-AO are defined in [RFC5926] (see Cryptographic algorithms for TCP-AO are defined in [RFC5926] (see
Section 3.7). below in Section 3.7).
RFC 5926 S: "Cryptographic Algorithms for the TCP Authentication RFC 5926 S: "Cryptographic Algorithms for the TCP Authentication
Option (TCP-AO)" (May 2010) Option (TCP-AO)" (June 2010)
This document [RFC5926] specifies the algorithms and attributes This document [RFC5926] specifies the algorithms and attributes
that can be used in TCP Authentication Option's (TCP-AO) [RFC5925] that can be used in TCP Authentication Option's (TCP-AO) [RFC5925]
(see Section 3.7) current manual keying mechanism and provides the (see above in Section 3.7) current manual keying mechanism and
interface for future message authentication codes (MACs). provides the interface for future message authentication codes
(MACs).
RFC 5927 I: "ICMP attacks against TCP" (July 2010) RFC 5927 I: "ICMP Attacks against TCP" (July 2010)
Abstract: "This document discusses the use of the Internet Control Abstract of RFC 5927 [RFC5927]: "This document discusses the use
Message Protocol (ICMP) to perform a variety of attacks against of the Internet Control Message Protocol (ICMP) to perform a
the Transmission Control Protocol (TCP). Additionally, this variety of attacks against the Transmission Control Protocol
document describes a number of widely implemented modifications to (TCP). Additionally, this document describes a number of widely
TCP's handling of ICMP error messages that help to mitigate these implemented modifications to TCP's handling of ICMP error messages
issues." [RFC5927] that help to mitigate these issues."
RFC 5961 S: "Improving TCP's Robustness to Blind In-Window Attacks" RFC 5961 S: "Improving TCP's Robustness to Blind In-Window Attacks"
(August 2010) (August 2010)
This document [RFC5961] describes minor modifications to how TCP This document [RFC5961] describes minor modifications to how TCP
handles inbound segments. This renders TCP connections, handles inbound segments. This renders TCP connections,
especially long-lived connections such as H-323 or BGP, less especially long-lived connections such as H-323 or BGP, less
vulnerable to spoofed packet injection attacks where the 4-tuple vulnerable to spoofed packet injection attacks where the 4-tuple
(the source and destination IP addresses and the source and (the source and destination IP addresses and the source and
destination ports) has been guessed. destination ports) has been guessed.
RFC 6528 S: "Defending Against Sequence Number Attacks" (February RFC 6528 S: "Defending against Sequence Number Attacks" (February
2012) 2012)
Abstract: "This document [RFC6528] specifies an algorithm for the Abstract of RFC 6528 [RFC6528]: "This document specifies an
generation of TCP Initial Sequence Numbers (ISNs), such that the algorithm for the generation of TCP Initial Sequence Numbers
chances of an off-path attacker guessing the sequence numbers in (ISNs), such that the chances of an off-path attacker guessing the
use by a target connection are reduced. This document revises sequence numbers in use by a target connection are reduced. This
(and formally obsoletes) RFC 1948, and takes the ISN generation document revises (and formally obsoletes) RFC 1948, and takes the
algorithm originally proposed in that document to Standards Track, ISN generation algorithm originally proposed in that document to
formally updating RFC 793 (see Section 2). Standards Track, formally updating RFC 793"
4. Experimental Extensions 4. Experimental Extensions
The RFCs in this section are either experimental and may become The RFCs in this section are either Experimental and may become
proposed standards in the future or are proposed standard (or Proposed Standards in the future or are Proposed Standards (or
informational), but can considered as experimental due to lack of Informational), but can be considered experimental due to lack of
wide deployment. At least part of the reason that they are still wide deployment. At least part of the reason that they are still
experimental is to gain more wide-scale experience with them before a experimental is to gain more wide-scale experience with them before a
standards track decision is made. standards track decision is made.
If the experimental RFC is a proposal for a new protocol capability If the Experimental RFC is a proposal for a new protocol capability
or service, i.e., it requires a new TCP option code point, the or service, i.e., it requires a new TCP option code point, the
implementation and experimentation should follow [RFC6994] (see implementation and experimentation should follow [RFC6994] (see
Section 5), which describes how the experimental TCP option code Section 5 of this document), which describes how the experimental TCP
points can concurrently support multiple TCP extensions. option code points can concurrently support multiple TCP extensions.
By their publication as experimental RFCs, it is hoped that the By their publication as Experimental RFCs, it is hoped that the
community of TCP researchers will analyze and test the contents of community of TCP researchers will analyze and test the contents of
these RFCs. Although experimentation is encouraged, there is not yet these RFCs. Although experimentation is encouraged, there is not yet
formal consensus that these are fully logical and safe behaviors. formal consensus that these are fully logical and safe behaviors.
Wide-scale deployment of implementations that use these features Wide-scale deployment of implementations that use these features
should be well thought-out in terms of consequences. should be well thought out in terms of consequences.
4.1. Architectural Guidelines 4.1. Architectural Guidelines
As multiple flows may share the same paths, sections of paths, or As multiple flows may share the same paths, sections of paths, or
other resources, the TCP implementation may benefit from sharing other resources, the TCP implementation may benefit from sharing
information across TCP connections or other flows. Some Experimental information across TCP connections or other flows. Some experimental
proposals have been documented and some implementations have included proposals have been documented and some implementations have included
the concepts. the concepts.
RFC 2140 I: "TCP Control Block Interdependence" (April 1997) RFC 2140 I: "TCP Control Block Interdependence" (April 1997)
This document [RFC2140] suggests how TCP connections between the This document [RFC2140] suggests how TCP connections between the
same endpoints might share information, such as their congestion same endpoints might share information, such as their congestion
control state. To some degree, this is done in practice by a few control state. To some degree, this is done in practice by a few
operating systems; for example, Linux currently has a destination operating systems; for example, Linux currently has a destination
cache. Although this RFC is technically informational, the cache. Although this RFC is technically Informational, the
concepts it describes are in experimental use, so we include it in concepts it describes are in experimental use, so we include it in
this section. this section.
RFC 3124 S: "The Congestion Manager" (June 2001) RFC 3124 S: "The Congestion Manager" (June 2001)
This document [RFC3124], the Congestion Manager, is a related This document [RFC3124] is a related proposal to RFC 2140 (see
proposal to RFC 2140 (see Section 4.1). The idea behind the above in Section 4.1). The idea behind the Congestion Manager,
Congestion Manager, moving congestion control outside of moving congestion control outside of individual TCP connections,
individual TCP connections, represents a modification to the core represents a modification to the core of TCP, which supports
of TCP, which supports sharing information among TCP connections. sharing information among TCP connections. Although a Proposed
Although a Proposed Standard, some pieces of the Congestion Standard, some pieces of the Congestion Manager support
Manager support architecture have not been specified yet, and it architecture have not been specified yet, and it has not achieved
has not achieved use or implementation beyond experimental stacks, use or implementation beyond experimental stacks, so it is not
so it is not listed among the standard TCP enhancements in this listed among the standard TCP enhancements in this roadmap.
roadmap.
4.2. Fundamental Changes 4.2. Fundamental Changes
Like the standard documents listed in Section 3.1, there also exist Like the Standards Track documents listed in Section 3.1, there also
new Experimental RFCs that specify fundamental changes to TCP. At exist new Experimental RFCs that specify fundamental changes to TCP.
the time of writing, the only example so far is TCP Fast Open that At the time of writing, the only example so far is TCP Fast Open that
deviates from the standard TCP semantics of [RFC0793]. deviates from the standard TCP semantics of [RFC793].
RFC XXX E: "TCP Fast Open" (XXX 2014) RFC 7413 E: "TCP Fast Open" (December 2014)
This document [I-D.ietf-tcpm-fastopen] describes TCP Fast Open This document [RFC7413] describes TCP Fast Open that allows data
that allows data to be carried in the SYN and SYN-ACK packets and to be carried in the SYN and SYN-ACK packets and consumed by the
consumed by the receiver during the initial connection handshake. receiver during the initial connection handshake. It saves up to
It saves up to one RTT compared to the standard TCP, which one RTT compared to the standard TCP, which requires a three-way
requires a three-way handshake to complete before data can be handshake to complete before data can be exchanged.
exchanged.
4.3. Congestion Control Extensions 4.3. Congestion Control Extensions
TCP congestion control has been an extremely active research area for TCP congestion control has been an extremely active research area for
many years (see RFC 5783, Section 7.6), as it determines the many years (see RFC 5783 discussed in Section 7.6 of this document),
performance of many applications that use TCP. A number of as it determines the performance of many applications that use TCP.
experimental RFCs address issues with flow start-up, overshoot, and A number of Experimental RFCs address issues with flow start up,
steady-state behavior in the basic RFC 5681 (see Section 2) overshoot, and steady-state behavior in the basic algorithms of RFC
algorithms. In these sub-sections, enhancements to TCP's congestion 5681 (see Section 2 of this document). In these subsections,
control are listed. The next sub-section focuses on TCP's loss enhancements to TCP's congestion control are listed. The next
recovery. subsection focuses on TCP's loss recovery.
RFC 2861 E: "TCP Congestion Window Validation" (June 2000) RFC 2861 E: "TCP Congestion Window Validation" (June 2000)
This document [RFC2861] suggests reducing the congestion window This document [RFC2861] suggests reducing the congestion window
over time when no packets are flowing. This behavior is more over time when no packets are flowing. This behavior is more
aggressive than that specified in RFC 5681 (see Section 2), which aggressive than that specified in RFC 5681 (see Section 2 of this
says that a TCP sender SHOULD set its congestion window to the document), which says that a TCP sender SHOULD set its congestion
initial window after an idle period of an RTO or greater. window to the initial window after an idle period of an RTO or
greater.
RFC 3540 E: "Robust Explicit Congestion Notification (ECN) signaling RFC 3540 E: "Robust Explicit Congestion Notification (ECN) Signaling
with Nonces" (June 2003) with Nonces" (June 2003)
This document [RFC3540] describes an optional addition to ECN that This document [RFC3540] describes an optional addition to ECN that
protects against accidental or malicious concealment of marked protects against accidental or malicious concealment of marked
packets from the TCP sender. packets from the TCP sender.
RFC 3649 E: "HighSpeed TCP for Large Congestion Windows" (December RFC 3649 E: "HighSpeed TCP for Large Congestion Windows" (December
2003) 2003)
This document [RFC3649] proposes a modification to TCP's This document [RFC3649] proposes a modification to TCP's
congestion control mechanism for use with TCP connections with congestion control mechanism for use with TCP connections with
large congestion windows, to allow TCP to achieve a higher large congestion windows, to allow TCP to achieve a higher
throughput in high-bandwidth environments. throughput in high-bandwidth environments.
RFC 3742 E: "Limited Slow-Start for TCP with Large Congestion RFC 3742 E: "Limited Slow-Start for TCP with Large Congestion
Windows" (March 2004) Windows" (March 2004)
This document [RFC3742] describes a more conservative slow-start This document [RFC3742] describes a more conservative slow-start
behavior to prevent massive packet losses when a connection uses a behavior to prevent massive packet losses when a connection uses a
very large congestion window. very large congestion window.
RFC 4782 E: "Quick-Start for TCP and IP" (January 2007) (Errata) RFC 4782 E: "Quick-Start for TCP and IP" (January 2007) (Errata)
This document [RFC4782] specifies the optional Quick-Start This document [RFC4782] specifies the optional Quick-Start
mechanism for TCP. This mechanism allows connections to use mechanism for TCP. This mechanism allows connections to use
higher sending rates at the beginning of the data transfer or higher sending rates at the beginning of the data transfer or
after an idle period, provided that there is significant unused after an idle period, provided that there is significant unused
bandwidth along the path, and the sender and all of the routers bandwidth along the path, and the sender and all of the routers
along the path approve this higher rate. along the path approve this higher rate.
RFC 5562 E: "Adding Explicit Congestion Notification (ECN) Capability RFC 5562 E: "Adding Explicit Congestion Notification (ECN) Capability
to TCP's SYN/ACK Packets" (June 2009) to TCP's SYN/ACK Packets" (June 2009)
This document [RFC5562] describes an experimental modification to This document [RFC5562] describes an experimental modification to
ECN [RFC3168] (see Section 3.2) for the use of ECN in TCP SYN/ACK ECN [RFC3168] (see Section 3.2 of this document) for the use of
packets. This would allow to ECN-mark rather than drop the TCP ECN in TCP SYN/ACK packets. This would allow to ECN-mark rather
SYN/ACK packet at an ECN-capable router, and to avoid the severe than drop the TCP SYN/ACK packet at an ECN-capable router, and to
penalty of a retransmission timeout for a connection when the SYN/ avoid the severe penalty of a retransmission timeout for a
ACK packet is dropped. connection when the SYN/ACK packet is dropped.
RFC 5690 I: "Adding Acknowledgement Congestion Control to TCP" RFC 5690 I: "Adding Acknowledgement Congestion Control to TCP"
(February 2010) (February 2010)
This document [RFC5690] describes a congestion control mechanism This document [RFC5690] describes a congestion control mechanism
for acknowledgment (ACKs) traffic in TCP. The mechanism is based for acknowledgment (ACKs) traffic in TCP. The mechanism is based
on the acknowledgment congestion control of the Datagram on the acknowledgment congestion control of the Datagram
Congestion Control Protocol's (DCCP's) [RFC4340] Congestion Congestion Control Protocol's (DCCP's) [RFC4340] Congestion
Control Identifier (CCID) 2 [RFC4341]. Control Identifier (CCID) 2 [RFC4341].
RFC 6928 E: "Increasing TCP's Initial Window" (April 2013) RFC 6928 E: "Increasing TCP's Initial Window" (April 2013)
This document [RFC6928] proposes to increase the TCP initial This document [RFC6928] proposes to increase the TCP initial
window from between 2 and 4 segments, as specified in RFC 3390 window from between 2 and 4 segments, as specified in RFC 3390
(see Section 3.2), to 10 segments with a fallback to the existing (see Section 3.2 of this document), to 10 segments with a fallback
recommendation when performance issues are detected. to the existing recommendation when performance issues are
detected.
4.4. Loss Recovery Extensions 4.4. Loss Recovery Extensions
RFC 5827 E: "Early Retransmit for TCP and SCTP" (April 2010) RFC 5827 E: "Early Retransmit for TCP and Stream Control Transmission
Protocol (SCTP)" (April 2010)
This document [RFC5827] proposes the "Early Retransmit" mechanism This document [RFC5827] proposes the "Early Retransmit" mechanism
for TCP (and SCTP) that can be used to recover lost segments when for TCP (and SCTP) that can be used to recover lost segments when
a connection's congestion window is small. In certain special a connection's congestion window is small. In certain special
circumstances, Early Retransmit reduces the number of duplicate circumstances, Early Retransmit reduces the number of duplicate
acknowledgments required to trigger fast retransmit to recover acknowledgments required to trigger fast retransmit to recover
segment losses without waiting for a lengthy retransmission segment losses without waiting for a lengthy retransmission
timeout. timeout.
RFC 6069 E: "Making TCP more Robust to Long Connectivity Disruptions RFC 6069 E: "Making TCP More Robust to Long Connectivity Disruptions
(TCP-LCD)" (December 2010) (TCP-LCD)" (December 2010)
This document [RFC6069] describes how standard ICMP messages can This document [RFC6069] describes how standard ICMP messages can
be used to disambiguate true congestion loss from non-congestion be used to disambiguate true congestion loss from non-congestion
loss caused by connectivity disruptions. It proposes a reversion loss caused by connectivity disruptions. It proposes a reversion
strategy of TCP's retransmission timer that enables a more prompt strategy of TCP's retransmission timer that enables a more prompt
detection of whether or not the connectivity has been restored. detection of whether or not the connectivity has been restored.
RFC 6937 E: "Proportional Rate Reduction for TCP" (May 2013) RFC 6937 E: "Proportional Rate Reduction for TCP" (May 2013)
This document [RFC6937] describes an experimental Proportional This document [RFC6937] describes an experimental Proportional
skipping to change at page 21, line 6 skipping to change at page 21, line 35
documented. documented.
RFC 3522 E: "The Eifel Detection Algorithm for TCP" (April 2003) RFC 3522 E: "The Eifel Detection Algorithm for TCP" (April 2003)
The Eifel detection algorithm [RFC3522] allows a TCP sender to The Eifel detection algorithm [RFC3522] allows a TCP sender to
detect a posteriori whether it has entered loss recovery detect a posteriori whether it has entered loss recovery
unnecessarily by using the TCP timestamp option to solve the ACK unnecessarily by using the TCP timestamp option to solve the ACK
ambiguity. ambiguity.
RFC 3708 E: "Using TCP Duplicate Selective Acknowledgement (DSACKs) RFC 3708 E: "Using TCP Duplicate Selective Acknowledgement (DSACKs)
and Stream Control Transmission Protocol (SCTP) Duplicate and Stream Control Transmission Protocol (SCTP) Duplicate
Transmission Sequence Numbers (TSNs) to Detect Spurious Transmission Sequence Numbers (TSNs) to Detect Spurious
Retransmissions" (February 2004) Retransmissions" (February 2004)
Abstract: "TCP and Stream Control Transmission Protocol (SCTP) Abstract: "TCP and Stream Control Transmission Protocol (SCTP)
provide notification of duplicate segment receipt through provide notification of duplicate segment receipt through
Duplicate Selective Acknowledgement (DSACKs) and Duplicate Duplicate Selective Acknowledgement (DSACKs) and Duplicate
Transmission Sequence Number (TSN) notification, respectively. Transmission Sequence Number (TSN) notification, respectively.
This document presents conservative methods of using this This document presents conservative methods of using this
information to identify unnecessary retransmissions for various information to identify unnecessary retransmissions for various
applications." [RFC3708] applications."
RFC 4653 E: "Improving the Robustness of TCP to Non-Congestion RFC 4653 E: "Improving the Robustness of TCP to Non-Congestion
Events" (August 2008) Events" (August 2006)
In the presence of non-congestion events, such as reordering an In the presence of non-congestion events, such as packet
out-of-order segment does not necessarily indicates a lost segment reordering, an out-of-order segment does not necessarily indicate
and congestion. This document [RFC4653] proposes to increase the a lost segment and congestion. This document [RFC4653] proposes
threshold used to trigger a fast retransmission from the fixed to increase the threshold used to trigger a fast retransmission
value of three duplicate ACKs to about one congestion window of from the fixed value of three duplicate ACKs to about one
data in order to disambiguate true segment loss from segment congestion window of data in order to disambiguate true segment
reordering. loss from segment reordering.
4.6. TCP Timeouts 4.6. TCP Timeouts
Besides the well-known retransmission timeout the TCP standard Besides the well-known retransmission timeout the TCP standard
[RFC0793] defines other timeouts. This section lists documents that [RFC793] defines other timeouts. This section lists documents that
deal with TCP's various timeouts. deal with TCP's various timeouts.
RFC 5482 S: "TCP User Timeout Option" (June 2009) RFC 5482 S: "TCP User Timeout Option" (March 2009)
As a local per-connection parameter the TCP user timeout controls As a local per-connection parameter, the TCP user timeout controls
how long transmitted data may remain unacknowledged before a how long transmitted data may remain unacknowledged before a
connection is forcefully closed. This document [RFC5482] connection is forcefully closed. This document [RFC5482]
specifies the TCP User Timeout Option that allows one end of a TCP specifies the TCP User Timeout Option that allows one end of a TCP
connection to advertise its current user timeout value. This connection to advertise its current user timeout value. This
information provides advice to the other end of the TCP connection information provides advice to the other end of the TCP connection
to adapt its user timeout accordingly. to adapt its user timeout accordingly.
4.7. Multipath TCP 4.7. Multipath TCP
MultiPath TCP (MPTCP) is an ongoing effort within the IETF that MultiPath TCP (MPTCP) is an ongoing effort within the IETF that
allows a TCP connection to simultaneously use multiple IP-addresses/ allows a TCP connection to simultaneously use multiple IP addresses /
interfaces to spread their data across several subflows, while interfaces to spread their data across several subflows, while
presenting a regular TCP interface to applications. Benefits of this presenting a regular TCP interface to applications. Benefits of this
include better resource utilization, better throughput and smoother include better resource utilization, better throughput and smoother
reaction to failures. The documents listed in this section specify reaction to failures. The documents listed in this section specify
the Multipath TCP scheme, while the documents in Sections 7.2, 7.4, the Multipath TCP scheme, while the documents in Sections 7.2, 7.4,
and 7.5 provide some additional background information. and 7.5 provide some additional background information.
RFC 6356 E: "Coupled Congestion Control for Multipath Transport RFC 6356 E: "Coupled Congestion Control for Multipath Transport
Protocols" (August 2011) Protocols" (October 2011)
This document [RFC6356] presents a congestion control algorithm This document [RFC6356] presents a congestion control algorithm
for multipath transport protocols such as Multipath TCP. It for multipath transport protocols such as Multipath TCP. It
couples the congestion control algorithms running on different couples the congestion control algorithms running on different
subflows by linking their increase functions, and dynamically subflows by linking their increase functions, and dynamically
controls the overall aggressiveness of the multipath flow. The controls the overall aggressiveness of the multipath flow. The
result is an algorithm that is fair to TCP at bottlenecks while result is an algorithm that is fair to TCP at bottlenecks while
moving traffic away from congested links. moving traffic away from congested links.
RFC 6824 E: "TCP Extensions for Multipath Operation with Multiple RFC 6824 E: "TCP Extensions for Multipath Operation with Multiple
Addresses" (January 2013) (Errata) Addresses" (January 2013) (Errata)
This document [RFC6824] presents protocol changes required to add This document [RFC6824] presents protocol changes required to add
multipath capability to TCP; specifically, those for signaling and multipath capability to TCP; specifically, those for signaling and
setting up multiple paths ("subflows"), managing these subflows, setting up multiple paths ("subflows"), managing these subflows,
reassembly of data, and termination of sessions. reassembly of data, and termination of sessions.
5. TCP Parameters at IANA 5. TCP Parameters at IANA
RFCs listed here describes both the procedures that the Internet RFCs listed here describes both the procedures that the Internet
Assigned Numbers Authority (IANA) uses when handling assignments and Assigned Numbers Authority (IANA) uses when handling assignments and
the procedures an RFC author should follow when requesting new TCP the procedures an RFC author should follow when requesting new TCP
option codepoints. option code points.
RFC 2780 B: "IANA Allocation Guidelines For Values In the Internet RFC 2780 B: "IANA Allocation Guidelines For Values In the Internet
Protocol and Related Headers" (March 2000) Protocol and Related Headers" (March 2000)
Abstract: "This memo provides guidance for the IANA to use in Abstract of RFC 2780 [RFC2780]: "This memo provides guidance for
assigning parameters for fields in the IPv4, IPv6, ICMP, UDP and the IANA to use in assigning parameters for fields in the IPv4,
TCP protocol headers."[RFC2780] IPv6, ICMP, UDP and TCP protocol headers."
RFC 4727 S: "Experimental Values" (November 2006) RFC 4727 S: "Experimental Values in IPv4, IPv6, ICMPv4, ICMPv6, UDP,
and TCP Headers" (November 2006)
This document [RFC4727] reserves both TCP options 253 and 254 for This document [RFC4727] reserves both TCP options 253 and 254 for
experimentation purposes. When such experiments are deployed in experimentation purposes. When such experiments are deployed in
the Internet, they should follow the additional requirements in the Internet, they should follow the additional requirements in
RFC 6994 (see Section 5). RFC 6994 (see below in Section 5).
RFC 6335 B: "Internet Assigned Numbers Authority (IANA) Procedures RFC 6335 B: "Internet Assigned Numbers Authority (IANA) Procedures
for the Management of the Service Name and Transport Protocol Port for the Management of the Service Name and Transport
Number Registry (August 2011) Protocol Port Number Registry" (August 2011)
From abstract: "This document defines the procedures that the
Internet Assigned Numbers Authority (IANA) uses when handling From the Abstract of RFC 6335 [RFC6335]: "This document defines
assignment and other requests related to the Service Name and the procedures that the Internet Assigned Numbers Authority (IANA)
Transport Protocol Port Number registry." [RFC6335] uses when handling assignment and other requests related to the
Service Name and Transport Protocol Port Number registry."
RFC 6994 S: "Shared Use of Experimental TCP Options (August 2013) RFC 6994 S: "Shared Use of Experimental TCP Options (August 2013)
This document [RFC6994] describes how the experimental TCP option This document [RFC6994] describes how the experimental TCP option
code points can concurrently support multiple TCP extensions, even code points can concurrently support multiple TCP extensions, even
within the same connection. It creates an IANA registry for within the same connection. It creates an IANA registry for
extensions to the experimental code points. extensions to the experimental code points.
6. Historic and Undeployed Extensions 6. Historic and Undeployed Extensions
The RFCs listed here define extensions that have thus far failed to The RFCs listed here define extensions that have thus far failed to
arouse substantial interest from implementers and have never seen arouse substantial interest from implementers and have never seen
widespread deployment, or were found to be defective for general use. widespread deployment or were found to be defective for general use.
Most of them are reclassified by [RFC6247] to Historic status. Most of them were reclassified by [RFC6247] to Historic status.
RFC 721 U: "Out-of-Band Control Signals in a Host-to-Host Protocol" RFC 721 U: "Out-of-Band Control Signals in a Host-to-Host Protocol"
(September 1976): lack of interest (September 1976): lack of interest
RFC 721 [RFC0721] addresses the problem of implementing a reliable RFC 721 [RFC721] addresses the problem of implementing a reliable
out-of-band signal (interrupts) for use in a host-to-host out-of-band signal (interrupts) for use in a host-to-host
protocol. The proposal was not included in the final TCP protocol. The proposal was not included in the final TCP
specification. specification.
RFC 1078 U: "TCP Port Service Multiplexer (TCPMUX)" (November 1988): RFC 1078 U: "TCP Port Service Multiplexer (TCPMUX)" (November 1988):
lack of interest lack of interest
This document [RFC1078] proposes a protocol to contact multiple This document [RFC1078] proposes a protocol to contact multiple
services on a single well-known TCP port using a service name services on a single well-known TCP port using a service name
instead of a well-known number. instead of a well-known number.
RFC 1106 H: "TCP Big Window and NAK Options" (June 1989): found RFC 1106 H: "TCP Big Window and Nak Options" (June 1989): found
defective defective
This RFC [RFC1106] defined an alternative to the Window Scale This RFC [RFC1106] defined an alternative to the Window Scale
option for using large windows and described the "negative option for using large windows and described the "negative
acknowledgment" or NAK option. There is a comparison of NAK and acknowledgment" or NAK option. There is a comparison of NAK and
SACK methods, and early discussion of TCP over satellite issues. SACK methods and early discussion of TCP over satellite issues.
RFC 1110 (see Section 6) explains some problems with the RFC 1110 (see below in Section 6) explains some problems with the
approaches described in RFC 1106. The options described in this approaches described in RFC 1106. The options described in this
document have not been adopted by the larger community, although document have not been adopted by the larger community, although
NAKs are used in the SCPS-TP adaptation of TCP for satellite and NAKs are used in the SCPS-TP adaptation of TCP for satellite and
spacecraft use, developed by the Consultative Committee for Space spacecraft use, developed by the Consultative Committee for Space
Data Systems (CCSDS). Data Systems (CCSDS).
RFC 1110 H: "A Problem with the TCP Big Window Option" (August 1989): RFC 1110 H: "A Problem with the TCP Big Window Option" (August 1989):
deprecates RFC 1106 deprecates RFC 1106
Abstract: "The TCP Big Window option discussed in RFC 1106 (see Abstract of RFC 1110 [RFC1110]: "The TCP Big Window option
Section 6) will not work properly in an Internet environment which discussed in RFC 1106 will not work properly in an Internet
has both a high bandwidth * delay product and the possibility of environment which has both a high bandwidth * delay product and
disordering and duplicating packets. In such networks, the window the possibility of disordering and duplicating packets. In such
size must not be increased without a similar increase in the networks, the window size must not be increased without a similar
sequence number space. Therefore, a different approach to big increase in the sequence number space. Therefore, a different
windows should be taken in the Internet." [RFC1110] approach to big windows should be taken in the Internet."
RFC 1146 H: "TCP Alternate Checksum Options" (March 1990): lack of RFC 1146 H: "TCP Alternate Checksum Options" (March 1990): lack of
interest interest
This document [RFC1146] defined more robust TCP checksums than the This document [RFC1146] defined more robust TCP checksums than the
16-bit ones-complement in use today. A typographical error in RFC 16-bit ones-complement in use today. A typographical error in RFC
1145 is fixed in RFC 1146; otherwise, the documents are the same. 1145 is fixed in RFC 1146; otherwise, the documents are the same.
RFC 1263 I: "TCP Extensions Considered Harmful" (October 1991): lack RFC 1263 I: "TCP Extensions Considered Harmful" (October 1991): lack
of interest of interest
This document [RFC1263] argues against "backwards compatible" TCP This document [RFC1263] argues against "backwards compatible" TCP
extensions. Specifically mentioned are several TCP enhancements extensions. Specifically mentioned are several TCP enhancements
that have been successful, including timestamps, window scaling, that have been successful, including timestamps, window scaling,
PAWS, and SACK. RFC 1263 presents an alternative approach called PAWS, and SACK. RFC 1263 presents an alternative approach called
"protocol evolution", whereby several evolutionary versions of TCP "protocol evolution", whereby several evolutionary versions of TCP
would exist on hosts. These distinct TCP versions would represent would exist on hosts. These distinct TCP versions would represent
upgrades to each other and could be header-incompatible. upgrades to each other and could be header incompatible.
Interoperability would be provided by having a virtualization Interoperability would be provided by having a virtualization
layer select the right TCP version for a particular connection. layer select the right TCP version for a particular connection.
This idea did not catch on with the community, while the type of This idea did not catch on with the community, while the type of
extensions RFC 1263 specifically targeted as harmful did become extensions RFC 1263 specifically targeted as harmful did become
popular. popular.
RFC 1379 H: "Extending TCP for Transactions -- Concepts" (November RFC 1379 H: "Extending TCP for Transactions -- Concepts" (November
1992): found defective 1992): found defective
See RFC 1644, Section 6. See RFC 1644, in Section 6 below.
RFC 1644 H: "T/TCP -- TCP Extensions for Transactions Functional RFC 1644 H: "T/TCP -- TCP Extensions for Transactions Functional
Specification" (July 1994): found defective Specification" (July 1994): found defective
The inventors of TCP believed that cached connection state could The inventors of TCP believed that cached connection state could
have been used to eliminate TCP's 3-way handshake, to support two- have been used to eliminate TCP's three-way handshake, to support
packet request/response exchanges. RFC 1379 [RFC1379] (see two-packet request/response exchanges. RFC 1379 [RFC1379] (see
Section 6) and RFC 1644 [RFC1644] show that this is far from above in Section 6) and RFC 1644 [RFC1644] show that this is far
simple. Furthermore, T/TCP floundered on the ease of denial-of- from simple. Furthermore, T/TCP floundered on the ease of denial-
service attacks that can result. One idea pioneered by T/TCP of-service attacks that can result. One idea pioneered by T/TCP
lives on in RFC 2140 (see Section 4.1), in the sharing of state lives on in RFC 2140 (see Section 4.1 of this document), in the
across connections. sharing of state across connections.
RFC 1693 H: "An Extension to TCP: Partial Order Service" (November RFC 1693 H: "An Extension to TCP: Partial Order Service" (November
1994): lack of interest 1994): lack of interest
This document [RFC1693] defines a TCP extension for applications This document [RFC1693] defines a TCP extension for applications
that do not care about the order in which application-layer that do not care about the order in which application-layer
objects are received. Examples are multimedia and database objects are received. Examples are multimedia and database
applications. In practice, these applications either accept the applications. In practice, these applications either accept the
possible performance loss because of TCP's strict ordering or they possible performance loss because of TCP's strict ordering or use
use specialized transport protocols other than TCP, such as PR- specialized transport protocols other than TCP, such as PR-SCTP
SCTP [RFC3758]. [RFC3758].
RFC 1705 I: "Six Virtual Inches to the Left: The Problem with IPng" RFC 1705 I: "Six Virtual Inches to the Left: The Problem with IPng"
(October 1994): lack of interest (October 1994): lack of interest
To overcome the exhaustion of the IP class B address space, To overcome the exhaustion of the IP class B address space, this
suggest this document [RFC1705] that a new version of TCP (TCPng) document [RFC1705] suggests that a new version of TCP (TCPng)
needs to be developed and deployed. It proposes that a globally needs to be developed and deployed. It proposes that a globally
unique address be assigned to Transport layer to uniquely identify unique address be assigned to the transport layer to uniquely
an Internet host without specifying any routing information. identify an Internet host without specifying any routing
Later work on splitting locator and identifier values is information. Later work on splitting locator and identifier
summarized well in [RFC6115], but no resulting changes to TCP have values is summarized well in [RFC6115], but no resulting changes
occurred. to TCP have occurred.
RFC 6013 E: "TCP Cookie Transactions (TCPCT)" (January 2011): lack of RFC 6013 E: "TCP Cookie Transactions (TCPCT)" (January 2011): lack of
interest interest
This document [RFC6013] describes a method to exchange a cookie This document [RFC6013] describes a method to exchange a cookie
(nonce) during the connection establishment to negotiate (nonce) during the connection establishment to negotiate
elimination of receiver state. These cookies are later used to elimination of receiver state. These cookies are later used to
inhibit premature closing of connections, and reduce retention of inhibit premature closing of connections and reduce retention of
state after the connection has terminated. state after the connection has terminated.
Since the cookie pair is too large to fit with the other TCP Since the cookie pair is too large to fit with the other TCP
options in the 40 bytes of TCP option space, the document further options in the 40 bytes of TCP option space, the document further
describes a method to extent the option space after the connection describes a method to extent the option space after the connection
establishment. establishment.
Although RFC 6013 was published in 2011, the authors of this Although RFC 6013 was published in 2011, the authors of this
document places it in this section of the roadmap document due to document places it in this section of the roadmap document due to
two factors. two factors.
skipping to change at page 25, line 47 skipping to change at page 26, line 45
state after the connection has terminated. state after the connection has terminated.
Since the cookie pair is too large to fit with the other TCP Since the cookie pair is too large to fit with the other TCP
options in the 40 bytes of TCP option space, the document further options in the 40 bytes of TCP option space, the document further
describes a method to extent the option space after the connection describes a method to extent the option space after the connection
establishment. establishment.
Although RFC 6013 was published in 2011, the authors of this Although RFC 6013 was published in 2011, the authors of this
document places it in this section of the roadmap document due to document places it in this section of the roadmap document due to
two factors. two factors.
(a) The authors are not aware of any wide deployment and use of (a) The authors are not aware of any wide deployment and use of
RFC 6013. RFC 6013.
(b) RFC 6013 uses experimental TCP option code points, which
(b) RFC 6013 uses experimental TCP option codepoints, which
prohibits a large-scale deployment. prohibits a large-scale deployment.
7. Support Documents 7. Support Documents
This section contains several classes of documents that do not This section contains several classes of documents that do not
necessarily define current protocol behaviors, but that are necessarily define current protocol behaviors but that are
nevertheless of interest to TCP implementers. Section 7.1 describes nevertheless of interest to TCP implementers. Section 7.1 describes
several foundational RFCs that give modern readers a better several foundational RFCs that give modern readers a better
understanding of the principles underlying TCP's behaviors and understanding of the principles underlying TCP's behaviors and
development over the years. Section 7.2 contains architectural development over the years. Section 7.2 contains architectural
guidelines and principles for TCP architects and designers. The guidelines and principles for TCP architects and designers. The
documents listed in Section 7.3 provide advice on using TCP in documents listed in Section 7.3 provide advice on using TCP in
various types of network situations that pose challenges above those various types of network situations that pose challenges above those
of typical wired links. Guidance for developing, analyzing, and of typical wired links. Guidance for developing, analyzing, and
evaluating TCP is given in Section 7.4. Some implementation notes evaluating TCP is given in Section 7.4. Some implementation notes
and implementation advice can be found in Section 7.5. RFCs that and implementation advice can be found in Section 7.5. RFCs that
skipping to change at page 26, line 39 skipping to change at page 27, line 36
The documents listed in this section contain information that is The documents listed in this section contain information that is
largely duplicated by the standards documents previously discussed. largely duplicated by the standards documents previously discussed.
However, some of them contain a greater depth of problem statement However, some of them contain a greater depth of problem statement
explanation or other context. Particularly, RFCs 813 - 817 (known as explanation or other context. Particularly, RFCs 813 - 817 (known as
the "Dave Clark Five") describe some early problems and solutions the "Dave Clark Five") describe some early problems and solutions
(RFC 815 only describes the reassembly of IP fragments and is not (RFC 815 only describes the reassembly of IP fragments and is not
included in this TCP roadmap). included in this TCP roadmap).
RFC 675 U: "Specification of Internet Transmission Control Program" RFC 675 U: "Specification of Internet Transmission Control Program"
(December 1974) (December 1974)
This document [RFC0675] is a very early precursor of the This document [RFC675] is a very early precursor of the
fundamental RFC 793 (see Section 2), which already contained the fundamental RFC 793 (see Section 2 of this document), which
three-way handshake in its final form and the concept of sliding already contained the three-way handshake in its final form and
windows for reliable data transmission. Apart from that the the concept of sliding windows for reliable data transmission.
segment layout is totally different and the specified API differs Apart from that, the segment layout is totally different and the
from the latter RFC 793 (see Section 2). specified API differs from the latter RFC 793 (see Section 2 of
this document).
RFC 761 U: "DoD standard Transmission Control Protocol" (January RFC 761 U: "DoD Standard Transmission Control Protocol" (January
1980) 1980)
This document [RFC0761] is the immediate precursor of RFC 793 (see This document [RFC761] is the immediate precursor of RFC 793 (see
Section 2). The header format, the connection establishment Section 2 of this document). The header format, the connection
including the different connection states, and the overall API establishment (including the different connection states), and the
correspond mostly to the final Standard RFC 793 (see Section 2). overall API correspond mostly to the final Standard RFC 793 (see
Section 2 of this document).
RFC 813 U: "Window and Acknowledgement Strategy in TCP" (July 1982) RFC 813 U: "Window and Acknowledgement Strategy in TCP" (July 1982)
This document [RFC0813] contains an early discussion of Silly This document [RFC813] contains an early discussion of Silly
Window Syndrome and its avoidance and motivates and describes the Window Syndrome and its avoidance and motivates and describes the
use of delayed acknowledgments. use of delayed acknowledgments.
RFC 814 U: "Name, Addresses, Ports, and Routes" (July 1982) RFC 814 U: "Name, Addresses, Ports, and Routes" (July 1982)
Suggestions and guidance for the design of tables and algorithms Suggestions and guidance for the design of tables and algorithms
to keep track of various identifiers within a TCP/IP to keep track of various identifiers within a TCP/IP
implementation are provided by this document [RFC0814]. implementation are provided by this document [RFC814].
RFC 816 U: "Fault Isolation and Recovery" (July 1982) RFC 816 U: "Fault Isolation and Recovery" (July 1982)
In this document [RFC0816], TCP's response to indications of In this document [RFC816], TCP's response to indications of
network error conditions such as timeouts or received ICMP network error conditions such as timeouts or received ICMP
messages is discussed. messages is discussed.
RFC 817 U: "Modularity and Efficiency in Protocol Implementation" RFC 817 U: "Modularity and Efficiency in Protocol Implementation"
(July 1982) (July 1982)
This document [RFC0817] contains implementation suggestions that This document [RFC817] contains implementation suggestions that
are general and not TCP specific. However, they have been used to are general and not TCP specific. However, they have been used to
develop TCP implementations and describe some performance develop TCP implementations and describe some performance
implications of the interactions between various layers in the implications of the interactions between various layers in the
Internet stack. Internet stack.
RFC 872 U: "TCP-on-a-LAN" (September 1982) RFC 872 U: "TCP-on-a-LAN" (September 1982)
Conclusion: "The sometimes-expressed fear that using TCP on a Conclusion of RFC 872 [RFC872]: "The sometimes-expressed fear that
local net is a bad idea is unfounded." [RFC0872] using TCP on a local net is a bad idea is unfounded."
RFC 896 U: "Congestion Control in IP/TCP Internetworks" (January RFC 896 U: "Congestion Control in IP/TCP Internetworks" (January
1984) 1984)
This document [RFC0896] contains some early experiences with This document [RFC896] contains some early experiences with
congestion collapse and some initial thoughts on how to avoid it congestion collapse and some initial thoughts on how to avoid it
using congestion control in TCP. Furthermore, it defined an using congestion control in TCP. Furthermore, it defined an
algorithm for efficient transmission of small packets that is algorithm for efficient transmission of small packets that is
today known as the Nagle Algorithm. today known as the Nagle algorithm.
RFC 964 U: "Some Problems with the Specification of the Military RFC 964 U: "Some Problems with the Specification of the Military
Standard Transmission Control Protocol" (November 1985) Standard Transmission Control Protocol" (November 1985)
This document [RFC0964] points out several specification bugs in This document [RFC964] points out several specification bugs in
the US Military's MIL-STD-1778 document, which was intended as a the US Military's MIL-STD-1778 document, which was intended as a
successor to RFC 793 (see Section 2). This serves to remind us of successor to RFC 793 (see Section 2 of this document). This
the difficulty in specification writing (even when we work from serves to remind us of the difficulty in specification writing
existing documents!). (even when we work from existing documents!).
7.2. Architectural Guidelines 7.2. Architectural Guidelines
Some documents in this section contain architectural guidance and Some documents in this section contain architectural guidance and
concerns, while others specify TCP- and congestion-control-related concerns, while others specify TCP- and congestion-control-related
mechanisms that are broadly applicable and have impacts on TCP's mechanisms that are broadly applicable and have impacts on TCP's
congestion control techniques. Some of these documents are direct congestion control techniques. Some of these documents are direct
products of the Internet Architecture Board (IAB), giving their products of the Internet Architecture Board (IAB) giving their
guidance on specific aspects of congestion control in the Internet. guidance on specific aspects of congestion control in the Internet.
RFC 1958 I: "Architectural Principles of the Internet" (June 1996) RFC 1958 I: "Architectural Principles of the Internet" (June 1996)
This document [RFC1958] describes the underlying principles of the This document [RFC1958] describes the underlying principles of the
Internet architecture. It provides guidelines for network systems Internet architecture. It provides guidelines for network systems
designs that have proven useful in the evolution of the Internet. designs that have proven useful in the evolution of the Internet.
RFC 2914 B: "Congestion Control Principles" (September 2000) RFC 2914 B: "Congestion Control Principles" (September 2000)
This document [RFC2914] motivates the use of end-to-end congestion This document [RFC2914] motivates the use of end-to-end congestion
control for preventing congestion collapse and providing fairness control for preventing congestion collapse and providing fairness
to TCP. Later work on TCP has included several more aggressive to TCP. Later work on TCP has included several more aggressive
mechanisms than Reno TCP includes, and RFC 5033 (see Section 7.4) mechanisms than Reno TCP includes, and RFC 5033 (see Section 7.4
provides additional guidance on use of such algorithms. The of this document) provides additional guidance on use of such
fundamental architectural discussion in RFC 2914 remains valid, algorithms. The fundamental architectural discussion in RFC 2914
regarding the standards process role in defining protocol aspects remains valid, regarding the standards process role in defining
that are critical to performance and avoiding congestion collapse protocol aspects that are critical to performance and avoiding
scenarios. congestion collapse scenarios.
RFC 3360 B: "Inappropriate TCP Resets Considered Harmful" (August RFC 3360 B: "Inappropriate TCP Resets Considered Harmful" (August
2002) 2002)
This document [RFC3360] is a plea that firewall vendors not send This document [RFC3360] is a plea that firewall vendors not send
gratuitous TCP RST (Reset) packets when unassigned TCP header bits gratuitous TCP RST (Reset) packets when unassigned TCP header bits
are used. This practice prevents desirable extension and are used. This practice prevents desirable extension and
evolution of the protocol and thus is potentially harmful to the evolution of the protocol and thus is potentially harmful to the
future of the Internet. future of the Internet.
RFC 3439 I: "Some Internet Architectural Guidelines and Philosophy" RFC 3439 I: "Some Internet Architectural Guidelines and Philosophy"
(December 2002) (December 2002)
This document [RFC3439] updates RFC 1958 (see Section 7.2) by This document [RFC3439] updates RFC 1958 (see above in
outlining some philosophical guidelines for architects and Section 7.2) by outlining some philosophical guidelines for
designers of Internet backbone networks. The document describes architects and designers of Internet backbone networks. The
the Simplicity Principle, which states that complexity is the document describes the Simplicity Principle, which states that
primary impediment to efficient scaling. complexity is the primary impediment to efficient scaling.
RFC 4774 B: "Specifying Alternate Semantics for the Explicit RFC 4774 B: "Specifying Alternate Semantics for the Explicit
Congestion Notification (ECN) Field" (November 2006) Congestion Notification (ECN) Field" (November 2006)
This document [RFC4774] discusses some of the issues in defining This document [RFC4774] discusses some of the issues in defining
alternate semantics for the ECN field, and specifies requirements alternate semantics for the ECN field and specifies requirements
for a safe co-existence with routers that do not understand the for a safe coexistence with routers that do not understand the
defined alternate semantics. defined alternate semantics.
RFC 6182 I: "Architectural Guidelines for Multipath TCP Development" RFC 6182 I: "Architectural Guidelines for Multipath TCP Development"
(March 2011) (March 2011)
Abstract: "This document outlines architectural guidelines for the Abstract of RFC 6182 [RFC6182]: "This document outlines
development of a Multipath Transport Protocol, with references to architectural guidelines for the development of a Multipath
how these architectural components come together in the Transport Protocol, with references to how these architectural
development of a Multipath TCP (MPTCP) (see Section 4.7). This components come together in the development of a Multipath TCP
document lists certain high-level design decisions that provide (MPTCP) (see Section 4.7 of this document). This document lists
foundations for the design of the MPTCP protocol, based upon these certain high-level design decisions that provide foundations for
architectural requirements" [RFC6182] the design of the MPTCP protocol, based upon these architectural
requirements"
7.3. Difficult Network Environments 7.3. Difficult Network Environments
As the internetworking field has explored wireless, satellite, As the internetworking field has explored wireless, satellite,
cellular telephone, and other kinds of link-layer technologies, a cellular telephone, and other kinds of link-layer technologies, a
large body of work has built up on enhancing TCP performance for such large body of work has built up on enhancing TCP performance for such
links. The RFCs listed in this section describe some of these more links. The RFCs listed in this section describe some of these more
challenging network environments and how TCP interacts with them. challenging network environments and how TCP interacts with them.
RFC 2488 B: "Enhancing TCP Over Satellite Channels using Standard RFC 2488 B: "Enhancing TCP Over Satellite Channels using Standard
Mechanisms" (January 1999) Mechanisms" (January 1999)
From abstract: "While TCP works over satellite channels there are From the Abstract of RFC 2488 [RFC2488]: "While TCP works over
several IETF standardized mechanisms that enable TCP to more satellite channels there are several IETF standardized mechanisms
effectively utilize the available capacity of the network path. that enable TCP to more effectively utilize the available capacity
This document outlines some of these TCP mitigations. At this of the network path. This document outlines some of these TCP
time, all mitigations discussed in this document are IETF mitigations. At this time, all mitigations discussed in this
standards track mechanisms (or are compliant with IETF document are IETF standards track mechanisms (or are compliant
standards)." [RFC2488] with IETF standards)."
RFC 2757 I: "Long Thin Networks" (January 2000) RFC 2757 I: "Long Thin Networks" (January 2000)
Several methods of improving TCP performance over long thin Several methods of improving TCP performance over long thin
networks (i.e., networks with low bandwidth and high delay), such networks (i.e., networks with low bandwidth and high delay), such
as geosynchronous satellite links, are discussed in this document as geosynchronous satellite links, are discussed in this document
[RFC2757]. A particular set of TCP options is developed that [RFC2757]. A particular set of TCP options is developed that
should work well in such environments and be safe to use in the should work well in such environments and be safe to use in the
global Internet. The implications of such environments have been global Internet. The implications of such environments have been
further discussed in RFC 3150 (see Section 7.3) and RFC 3155 (see further discussed in RFCs 3150 and 3155 (see below in
Section 7.3), and these documents should be preferred where there Section 7.3), and these documents should be preferred where there
is overlap between them and RFC 2757 (see Section 7.3). is overlap between them and RFC 2757 (see Section 7.3 of this
document).
RFC 2760 I: "Ongoing TCP Research Related to Satellites" (February RFC 2760 I: "Ongoing TCP Research Related to Satellites" (February
2000) 2000)
This document [RFC2760] discusses the advantages and disadvantages This document [RFC2760] discusses the advantages and disadvantages
of several different experimental means of improving TCP of several different experimental means of improving TCP
performance over long-delay or error-prone paths. These include performance over long-delay or error-prone paths. These include
T/TCP, larger initial windows, byte counting, delayed T/TCP, larger initial windows, byte counting, delayed
acknowledgments, slow start thresholds, NewReno and SACK-based acknowledgments, slow start thresholds, NewReno and SACK-based
loss recovery, FACK [MM96], ECN, various corruption-detection loss recovery, FACK [MM96], ECN, various corruption-detection
mechanisms, congestion avoidance changes for fairness, use of mechanisms, congestion avoidance changes for fairness, use of
multiple parallel flows, pacing, header compression, state multiple parallel flows, pacing, header compression, state
sharing, and ACK congestion control, filtering, and sharing, and ACK congestion control, filtering, and
reconstruction. Although RFC 2488 (see Section 7.3) looks at reconstruction. Although RFC 2488 (see above in Section 7.3)
standard extensions, this document focuses on more experimental looks at standard extensions, this document focuses on more
means of performance enhancement. experimental means of performance enhancement.
RFC 3135 I: "Performance Enhancing Proxies Intended to Mitigate Link- RFC 3135 I: "Performance Enhancing Proxies Intended to Mitigate Link-
Related Degradations" (June 2001) Related Degradations" (June 2001)
From abstract: "This document is a survey of Performance Enhancing From the Abstract of RFC 3135 [RFC3135]: "This document is a
Proxies (PEPs) often employed to improve degraded TCP performance survey of Performance Enhancing Proxies (PEPs) often employed to
caused by characteristics of specific link environments, for improve degraded TCP performance caused by characteristics of
example, in satellite, wireless WAN, and wireless LAN specific link environments, for example, in satellite, wireless
environments. Different types of Performance Enhancing Proxies WAN, and wireless LAN environments. Different types of
are described as well as the mechanisms used to improve Performance Enhancing Proxies are described as well as the
performance." [RFC3135] mechanisms used to improve performance."
RFC 3150 B: "End-to-end Performance Implications of Slow Links" (July RFC 3150 B: "End-to-end Performance Implications of Slow Links" (July
2001) 2001)
From abstract: "This document makes performance-related From the Abstract of RFC 3150 [RFC3150]: "This document makes
recommendations for users of network paths that traverse "very low performance-related recommendations for users of network paths
bit-rate" links....This recommendation may be useful in any that traverse "very low bit-rate" links....This recommendation may
network where hosts can saturate available bandwidth, but the be useful in any network where hosts can saturate available
design space for this recommendation explicitly includes bandwidth, but the design space for this recommendation explicitly
connections that traverse 56 Kb/second modem links or 4.8 Kb/ includes connections that traverse 56 Kb/second modem links or 4.8
second wireless access links - both of which are widely deployed." Kb/second wireless access links - both of which are widely
[RFC3150] deployed."
RFC 3155 B: "End-to-end Performance Implications of Links with RFC 3155 B: "End-to-end Performance Implications of Links with
Errors" (August 2001) Errors" (August 2001)
From abstract: "This document discusses the specific TCP From the Abstract of RFC 3155 [RFC3155]: "This document discusses
mechanisms that are problematic in environments with high the specific TCP mechanisms that are problematic in environments
uncorrected error rates, and discusses what can be done to with high uncorrected error rates, and discusses what can be done
mitigate the problems without introducing intermediate devices to mitigate the problems without introducing intermediate devices
into the connection." [RFC3155] into the connection."
RFC 3366 B: "Advice to link designers on link Automatic Repeat RFC 3366 B: "Advice to link designers on link Automatic Repeat
reQuest (ARQ)" (August 2002) reQuest (ARQ)" (August 2002)
From abstract: "This document provides advice to the designers of From the Abstract of RFC 3366 [RFC3366]: "This document provides
digital communication equipment and link-layer protocols employing advice to the designers of digital communication equipment and
link-layer Automatic Repeat reQuest (ARQ) techniques. This link-layer protocols employing link-layer Automatic Repeat reQuest
document presumes that the designers wish to support Internet (ARQ) techniques. This document presumes that the designers wish
protocols, but may be unfamiliar with the architecture of the to support Internet protocols, but may be unfamiliar with the
Internet and with the implications of their design choices for the architecture of the Internet and with the implications of their
performance and efficiency of Internet traffic carried over their design choices for the performance and efficiency of Internet
links." [RFC3366] traffic carried over their links."
RFC 3449 B: "TCP Performance Implications of Network Path Asymmetry" RFC 3449 B: "TCP Performance Implications of Network Path Asymmetry"
(December 2002) (December 2002)
From abstract: "This document describes TCP performance problems From the Abstract of RFC 3449 [RFC3449]: "This document describes
that arise because of asymmetric effects. These problems arise in TCP performance problems that arise because of asymmetric effects.
several access networks, including bandwidth-asymmetric networks These problems arise in several access networks, including
and packet radio subnetworks, for different underlying reasons. bandwidth-asymmetric networks and packet radio subnetworks, for
However, the end result on TCP performance is the same in both different underlying reasons. However, the end result on TCP
cases: performance often degrades significantly because of performance is the same in both cases: performance often degrades
imperfection and variability in the ACK feedback from the receiver significantly because of imperfection and variability in the ACK
to the sender. feedback from the receiver to the sender.
The document details several mitigations to these effects, which The document details several mitigations to these effects, which
have either been proposed or evaluated in the literature, or are have either been proposed or evaluated in the literature, or are
currently deployed in networks." [RFC3449] currently deployed in networks.
RFC 3481 B: "TCP over Second (2.5G) and Third (3G) Generation RFC 3481 B: "TCP over Second (2.5G) and Third (3G) Generation
Wireless Networks" (February 2003) Wireless Networks" (February 2003)
From abstract: "This document describes a profile for optimizing From the Abstract of RFC 3481 [RFC3481]: "This document describes
TCP to adapt so that it handles paths including second (2.5G) and a profile for optimizing TCP to adapt so that it handles paths
third (3G) generation wireless networks." [RFC3481] including second (2.5G) and third (3G) generation wireless
networks."
RFC 3819 B: "Advice for Internet Subnetwork Designers" (July 2004) RFC 3819 B: "Advice for Internet Subnetwork Designers" (July 2004)
This document [RFC3819] describes how TCP performance can be This document [RFC3819] describes how TCP performance can be
negatively affected by some particular lower-layer behaviors and negatively affected by some particular lower-layer behaviors and
provides guidance in designing lower-layer networks and protocols provides guidance in designing lower-layer networks and protocols
to be amicable to TCP. RFC 3366 (see Section 7.3) specifically to be amicable to TCP. RFC 3366 (see above in Section 7.3)
focuses on ARQ mechanisms, while RFC 3819 more widely covers specifically focuses on ARQ mechanisms, while RFC 3819 more widely
additional aspects of the underlying layers covers additional aspects of the underlying layers
7.4. Guidance for Developing, Analyzing, and Evaluating TCP 7.4. Guidance for Developing, Analyzing, and Evaluating TCP
Documents in this section give general guidance for developing, Documents in this section give general guidance for developing,
analyzing, and evaluating TCP. Some of the documents discuss for analyzing, and evaluating TCP. Some of the documents discuss, for
example the properties of congestion control protocols that are example, the properties of congestion control protocols that are
"safe" for Internet deployment, as well as how to measure the "safe" for Internet deployment as well as how to measure the
properties of congestion control mechanisms and transport protocols. properties of congestion control mechanisms and transport protocols.
RFC 5033 B: "Specifying New Congestion Control Algorithms" (August RFC 5033 B: "Specifying New Congestion Control Algorithms" (August
2007) 2007)
This document [RFC5033] considers the evaluation of suggested This document [RFC5033] considers the evaluation of suggested
congestion control algorithms that differ from the principles congestion control algorithms that differ from the principles
outlined in RFC 2914 (see Section 7.2). It is useful for authors outlined in RFC 2914 (see Section 7.2 of this document). It is
of such algorithms as well as for IETF members reviewing the useful for authors of such algorithms as well as for IETF members
associated documents. reviewing the associated documents.
RFC 5166 I: "Metrics for the Evaluation of Congestion Control RFC 5166 I: "Metrics for the Evaluation of Congestion Control
Mechanisms" (March 2008) Mechanisms" (March 2008)
This document [RFC5166] discusses metrics that needs to be This document [RFC5166] discusses metrics that need to be
considered when evaluating new or modified congestion control considered when evaluating new or modified congestion control
mechanisms for the Internet. Among others topics, the document mechanisms for the Internet. Among other topics, the document
discusses throughput, delay, loss rates, response times, fairness discusses throughput, delay, loss rates, response times, fairness,
and robustness for challenging environments. and robustness for challenging environments.
RFC 6077 I: "Open Research Issues in Internet Congestion Control" RFC 6077 I: "Open Research Issues in Internet Congestion Control"
(January 2011) (February 2011)
This RFC [RFC6077] summarizes the main open problems in the domain This document [RFC6077] summarizes the main open problems in the
of Internet congestion control. As a good starting point for domain of Internet congestion control. As a good starting point
newcomers, the document describes several new challenges that are for newcomers, the document describes several new challenges that
becoming important as the network grows, as well as some issues are becoming important as the network grows, as well as some
that have been known for many years. issues that have been known for many years.
RFC 6181 I: "Threat Analysis for TCP Extensions for Multipath RFC 6181 I: "Threat Analysis for TCP Extensions for Multipath
Operation with Multiple Addresses" (March 2011) Operation with Multiple Addresses" (March 2011)
This document [RFC6181] describes a threat analysis for Multipath This document [RFC6181] describes a threat analysis for Multipath
TCP (MPTCP) (see Section 4.7). The document discusses several TCP (MPTCP) (see Section 4.7 of this document). The document
types of attacks and provides recommendations for MPTCP designers discusses several types of attacks and provides recommendations
how to create an MPTCP specification that is as secure as the for MPTCP designers how to create an MPTCP specification that is
current (single-path) TCP. as secure as the current (single-path) TCP.
RFC 6349 I: "Framework for TCP Throughput Testing" (August 2011) RFC 6349 I: "Framework for TCP Throughput Testing" (August 2011)
From abstract: "This document describes a practical methodology From the Abstract of RFC 6349 [RFC6349]: "This framework describes
for measuring end-to-end TCP throughput in a managed IP network. a practical methodology for measuring end-to-end TCP Throughput in
The goal is to provide a better indication in regard to user a managed IP network. The goal is to provide a better indication
experience. In this framework, TCP and IP parameters are in regard to user experience. In this framework, TCP and IP
specified to optimize TCP throughput." [RFC6349] parameters are specified to optimize TCP Throughput."
7.5. Implementation Advice 7.5. Implementation Advice
RFC 794 U: "PRE-EMPTION" (September 1981) RFC 794 U: "PRE-EMPTION" (September 1981)
This document [RFC0794] clarifies that operating systems need to This document [RFC794] clarifies that operating systems need to
manage their limited resources, which may include TCP connection manage their limited resources, which may include TCP connection
state, and that these decisions can be made with application state, and that these decisions can be made with application
input, but they do not need to be part of the TCP protocol input, but they do not need to be part of the TCP protocol
specification itself. specification itself.
RFC 879 U: "The TCP Maximum Segment Size and Related Topics" RFC 879 U: "The TCP Maximum Segment Size and Related Topics"
(November 1983) (November 1983)
Abstract: "This memo discusses the TCP Maximum Segment Size Option Abstract of RFC 879 [RFC879]: "This memo discusses the TCP Maximum
and related topics. The purpose is to clarify some aspects of TCP Segment Size Option and related topics. The purposes [sic] is to
and its interaction with IP. This memo is a clarification to the clarify some aspects of TCP and its interaction with IP. This
TCP specification, and contains information that may be considered memo is a clarification to the TCP specification, and contains
as 'advice to implementers'." [RFC0879] information that may be considered as 'advice to implementers'."
RFC 1071 U: "Computing the Internet Checksum" (September 1988) RFC 1071 U: "Computing the Internet Checksum" (September 1988)
(Errata) (Errata)
This document [RFC1071] lists a number of implementation This document [RFC1071] lists a number of implementation
techniques for efficiently computing the Internet checksum (used techniques for efficiently computing the Internet checksum (used
by TCP). by TCP).
RFC 1624 I: "Computation of the Internet Checksum via Incremental RFC 1624 I: "Computation of the Internet Checksum via Incremental
Update" (May 1994) Update" (May 1994)
Incrementally updating the Internet checksum is useful to routers Incrementally updating the Internet checksum is useful to routers
in updating IP checksums. Some middleboxes that alter TCP headers in updating IP checksums. Some middleboxes that alter TCP headers
may also be able to update the TCP checksum incrementally. This may also be able to update the TCP checksum incrementally. This
document [RFC1624] expands upon the explanation of the incremental document [RFC1624] expands upon the explanation of the incremental
update procedure in RFC 1071 (see Section 7.5). update procedure in RFC 1071 (see above in Section 7.5).
RFC 1936 I: "Implementing the Internet Checksum in Hardware" (April RFC 1936 I: "Implementing the Internet Checksum in Hardware" (April
1996) 1996)
This document [RFC1936] describes the motivation for implementing This document [RFC1936] describes the motivation for implementing
the Internet checksum in hardware, rather than in software, and the Internet checksum in hardware, rather than in software, and
provides an implementation example. provides an implementation example.
RFC 2525 I: "Known TCP Implementation Problems" (March 1999) RFC 2525 I: "Known TCP Implementation Problems" (March 1999)
From abstract: "This memo catalogs a number of known TCP From the Abstract of RFC 2525 [RFC2525]: "This memo catalogs a
implementation problems. The goal is to improve conditions in the number of known TCP implementation problems. The goal in doing so
existing Internet by enhancing the quality of current TCP/IP is to improve conditions in the existing Internet by enhancing the
implementations." [RFC2525] quality of current TCP/IP implementations."
RFC 2923 I: "TCP Problems with Path MTU Discovery" (September 2000) RFC 2923 I: "TCP Problems with Path MTU Discovery" (September 2000)
From abstract: "This memo catalogs several known Transmission From abstract: "This memo catalogs several known Transmission
Control Protocol (TCP) implementation problems dealing with Path Control Protocol (TCP) implementation problems dealing with Path
Maximum Transmission Unit Discovery (PMTUD), including the long- Maximum Transmission Unit Discovery (PMTUD), including the long-
standing black hole problem, stretch acknowledgments (ACKs) due to standing black hole problem, stretch acknowledgments (ACKs) due to
confusion between Maximum Segment Size (MSS) and segment size, and confusion between Maximum Segment Size (MSS) and segment size, and
MSS advertisement based on PMTU." [RFC2923] MSS advertisement based on PMTU." [RFC2923]
RFC 3493 I: "Basic Socket Interface Extensions for IPv6" (February RFC 3493 I: "Basic Socket Interface Extensions for IPv6" (February
2003) 2003)
This document [RFC3493] describes the de facto standard sockets This document [RFC3493] describes the de facto standard sockets
API for programming with TCP. This API is implemented nearly API for programming with TCP. This API is implemented nearly
ubiquitously in modern operating systems and programming ubiquitously in modern operating systems and programming
languages. languages.
RFC 6056 B: "Recommendations for Transport-Protocol Port RFC 6056 B: "Recommendations for Transport-Protocol Port
Randomization" (December 2010) Randomization" (December 2010)
This document [RFC6056] describes a number of simple and efficient This document [RFC6056] describes a number of simple and efficient
methods for the selection of the client port number. It reduces methods for the selection of the client port number. It reduces
the possibility of an attacker guessing the correct five-tuple the possibility of an attacker guessing the correct five-tuple
(Protocol, Source/Destination Address, Source/Destination Port). (Protocol, Source/Destination Address, Source/Destination Port).
RFC 6191 B: "Reducing the TIME-WAIT State Using TCP timestamps" RFC 6191 B: "Reducing the TIME-WAIT State Using TCP Timestamps"
(April 2011) (April 2011)
This document [RFC6191] describes the usage of the TCP Timestamps This document [RFC6191] describes the usage of the TCP Timestamps
option (RFC 7323, see Section 3.1) to perform heuristics to option (RFC 7323, see Section 3.1 of this document) to perform
determine whether or not to allow the creation of a new heuristics to determine whether or not to allow the creation of a
incarnation of a connection that is in the TIME-WAIT state. new incarnation of a connection that is in the TIME-WAIT state.
RFC 6429 I: "TCP Sender Clarification for Persist Condition" RFC 6429 I: "TCP Sender Clarification for Persist Condition"
(December 2011) (December 2011)
This document [RFC6429] clarifies the actions that a TCP can take This document [RFC6429] clarifies the actions that a TCP can take
on connections that are experiencing the Zero Window Probe (ZWP) on connections that are experiencing the Zero Window Probe (ZWP)
condition. condition.
RFC 6897 I: "Multipath TCP (MPTCP) Application Interface RFC 6897 I: "Multipath TCP (MPTCP) Application Interface
Considerations" (March 2013) Considerations" (March 2013)
This document [RFC6897] characterizes the impact that Multipath This document [RFC6897] characterizes the impact that Multipath
TCP (MPTCP) (see Section 4.7) may have on applications. It TCP (MPTCP) (see Section 4.7 of this document) may have on
further discusses compatibility issues of MPTCP in combination applications. It further discusses compatibility issues of MPTCP
with non-MPTCP-aware applications. Finally, it describes a basic in combination with non-MPTCP-aware applications. Finally, it
API that is a simple extension of TCP's interface for MPTCP-aware describes a basic API that is a simple extension of TCP's
applications. interface for MPTCP-aware applications.
7.6. Tools and Tutorials 7.6. Tools and Tutorials
RFC 1180 I: "TCP/IP Tutorial" (January 1991) (Errata) RFC 1180 I: "TCP/IP Tutorial" (January 1991) (Errata)
This document [RFC1180] is an extremely brief overview of the This document [RFC1180] is an extremely brief overview of the TCP/
TCP/IP protocol suite as a whole. It gives some explanation as to IP protocol suite as a whole. It gives some explanation as to how
how and where TCP fits in. and where TCP fits in.
RFC 1470 I: "FYI on a Network Management Tool Catalog: Tools for RFC 1470 I: "FYI on a Network Management Tool Catalog: Tools for
Monitoring and Debugging TCP/IP Internets and Interconnected Devices" Monitoring and Debugging TCP/IP Internets and
(June 1993) Interconnected Devices" (June 1993)
A few of the tools that this document [RFC1470] describes are A few of the tools that this document [RFC1470] describes are
still maintained and in use today; for example, ttcp and tcpdump. still maintained and in use today, for example, ttcp and tcpdump.
However, many of the tools described do not relate specifically to However, many of the tools described do not relate specifically to
TCP and are no longer used or easily available. TCP and are no longer used or easily available.
RFC 2398 I: "Some Testing Tools for TCP Implementors" (August 1998) RFC 2398 I: "Some Testing Tools for TCP Implementors" (August 1998)
This document [RFC2398] describes a number of TCP packet This document [RFC2398] describes a number of TCP packet
generation and analysis tools. Although some of these tools are generation and analysis tools. Although some of these tools are
no longer readily available or widely used, for the most part they no longer readily available or widely used, for the most part they
are still relevant and usable. are still relevant and usable.
RFC 5783 I: "Congestion Control in the RFC Series" (February 2010) RFC 5783 I: "Congestion Control in the RFC Series" (February 2010)
This document [RFC5783] provides an overview of RFCs related to This document [RFC5783] provides an overview of RFCs related to
congestion control that have been published so far. The focus of congestion control that had been published at the time. The focus
the document is on end-host-based congestion control. of the document is on end-host-based congestion control.
7.7. MIB Modules 7.7. MIB Modules
The first MIB module defined for use with Simple Network Management The first MIB module defined for use with Simple Network Management
Protocol (SNMP) was a single monolithic MIB module, called MIB-I, Protocol (SNMP) was a single monolithic MIB module, called MIB-I,
defined in RFC 1156. This evolved over time to the MIB-II defined in RFC 1156. This evolved over time to the MIB-II
specification in RFC 1213, which obsoletes RFC 1156. It then became specification in RFC 1213, which obsoletes RFC 1156. It then became
apparent that having a single monolithic MIB module was not scalable, apparent that having a single monolithic MIB module was not scalable,
given the number and breadth of MIB data definitions that needed to given the number and breadth of MIB data definitions that needed to
be included. Thus, additional MIB modules were defined, and those be included. Thus, additional MIB modules were defined, and those
parts of MIB-II that needed to evolve were split off. Eventually, parts of MIB-II that needed to evolve were split off. Eventually,
the remaining parts of MIB-II were also split off, the TCP-specific the remaining parts of MIB-II were also split off, the TCP-specific
part being documented in RFC 2012. RFC 2012 was obsoleted by RFC part being documented in RFC 2012. RFC 2012 was obsoleted by RFC
4022, which is the primary TCP MIB document today. For current TCP 4022, which is the primary TCP MIB document at the time of writing.
implementers, RFC 4022 should be supported. For current TCP implementers, RFC 4022 should be supported.
RFC 1156 S: "Management Information Base for Network Management of RFC 1156 S: "Management Information Base for Network Management of
TCP/IP-based Internets" (May 1990) TCP/IP-based Internets" (May 1990)
This document [RFC1156] describes the required MIB fields for TCP This document [RFC1156] describes the required MIB fields for TCP
implementations with minor corrections and no technical changes implementations with minor corrections and no technical changes
from RFC 1066, which it obsoletes. This is the standards track from RFC 1066, which it obsoletes. This is the Standards Track
document for MIB-I. RFC for MIB-I.
RFC 1213 S: "Management Information Base for Network Management of RFC 1213 S: "Management Information Base for Network Management of
TCP/IP-based Internets: MIB-II" (March 1991) TCP/IP-based internets: MIB-II" (March 1991)
This document [RFC1213] describes the second version of the MIB in This document [RFC1213] describes the second version of the MIB in
a monolithic form. It is the immediate successor of RFC 1158, a monolithic form. It is the immediate successor of RFC 1158,
with minor modifications. It obsoletes the MIB-I, defined in RFC with minor modifications. It obsoletes the MIB-I, defined in RFC
1156 (see Section 7.7). 1156 (see above in Section 7.7).
RFC 2012 S: "SNMPv2 Management Information Base for the Transmission RFC 2012 S: "SNMPv2 Management Information Base for the Transmission
Control Protocol using SMIv2" (November 1996) Control Protocol using SMIv2" (November 1996)
In an update to RFC 1213 (see Section 7.7), this document In an update to RFC 1213 (see Section 7.7 of this document), this
[RFC2012] defines the TCP MIB by splitting out the TCP-specific document [RFC2012] defines the TCP MIB by splitting out the TCP-
portions. It is now obsoleted by RFC 4022 (see Section 7.7). specific portions. It is now obsoleted by RFC 4022 (see below in
Section 7.7).
RFC 2452 S: "IP Version 6 Management Information Base for the RFC 2452 S: "IP Version 6 Management Information Base for the
Transmission Control Protocol" (December 1998) Transmission Control Protocol" (December 1998)
This document [RFC2452] augments RFC 2012 (see Section 7.7) by This document [RFC2452] augments RFC 2012 (see Section 7.7 of this
adding an IPv6-specific connection table. The rest of RFC 2012 document) by adding an IPv6-specific connection table. The rest
holds for any IP version. RFC 2452 is now obsoleted by RFC 4022 of RFC 2012 holds for any IP version. RFC 2452 is now obsoleted
(see Section 7.7). by RFC 4022 (see below in Section 7.7).
Although it is a standards track document, RFC 2452 is considered Although it is a Standards Track RFC, RFC 2452 is considered a
a historic mistake by the MIB community, as it is based on the historic mistake by the MIB community, as it is based on the idea
idea of parallel IPv4 and IPv6 structures. Although IPv6 requires of parallel IPv4 and IPv6 structures. Although IPv6 requires new
new structures, the community has decided to define a single structures, the community has decided to define a single generic
generic structure for both IPv4 and IPv6. This will aid in structure for both IPv4 and IPv6. This will aid in definition,
definition, implementation, and transition between IPv4 and IPv6. implementation, and transition between IPv4 and IPv6.
RFC 4022 S: "Management Information Base for the Transmission Control RFC 4022 S: "Management Information Base for the Transmission Control
Protocol (TCP)" (March 2005) Protocol (TCP)" (March 2005)
This document [RFC4022] obsoletes RFC 2012 (see Section 7.7) and This document [RFC4022] obsoletes RFCs 2012 and 2452 (see above in
RFC 2452 (see Section 7.7) and specifies the current standard for Section 7.7) and specifies the current standard for the TCP MIB
the TCP MIB that should be deployed. that should be deployed.
RFC 4898 S: "TCP Extended Statistics MIB" (May 2007) RFC 4898 S: "TCP Extended Statistics MIB" (May 2007)
This document [RFC4898] describes extended performance statistics This document [RFC4898] describes extended performance statistics
for TCP. They are designed to use TCP's ideal vantage point to for TCP. They are designed to use TCP's ideal vantage point to
diagnose performance problems in both the network and the diagnose performance problems in both the network and the
application. application.
7.8. Case Studies 7.8. Case Studies
RFC 700 U: "A Protocol Experiment" (August 1974) RFC 700 U: "A Protocol Experiment" (August 1974)
This document [RFC0700] presents a field report about the This document [RFC700] presents a field report about the
deployment of a very early version of TCP, the so-called INWN #39 deployment of a very early version of TCP, the so-called INWN #39
protocol, which is originally described by Cerf and Kahn in INWG protocol, which is originally described by Cerf and Kahn in INWG
Note #39 [CK73] to use a PDP-11 line printer via the ARPANET. Note #39 [CK73] to use a PDP-11 line printer via the ARPANET.
RFC 889 U: "Internet Delay Experiments" (December 1983) RFC 889 U: "Internet Delay Experiments" (December 1983)
This document [RFC0889] is a status report about experiments This document [RFC889] is a status report about experiments
concerning the TCP retransmission timeout calculation and also concerning the TCP retransmission timeout calculation and also
provides advices for implementers. provides advice for implementers.
RFC 1337 I: "TIME-WAIT Assassination Hazards in TCP" (May 1992) RFC 1337 I: "TIME-WAIT Assassination Hazards in TCP" (May 1992)
This document [RFC1337] points out a problem with acting on This document [RFC1337] points out a problem with acting on
received reset segments while one is in the TIME-WAIT state. The received reset segments while one is in the TIME-WAIT state. The
main recommendation is that hosts in TIME-WAIT ignore resets. main recommendation is that hosts in TIME-WAIT ignore resets.
This recommendation might not currently be widely implemented. This recommendation might not currently be widely implemented.
RFC 2415 I: "Simulation Studies of Increased Initial TCP Window Size" RFC 2415 I: "Simulation Studies of Increased Initial TCP Window Size"
(September 1998) (September 1998)
This document [RFC2415] presents results of some simulations using This document [RFC2415] presents results of some simulations using
TCP initial windows greater than 1 segment. The analysis TCP initial windows greater than 1 segment. The analysis
indicates that user-perceived performance can be improved by indicates that user-perceived performance can be improved by
increasing the initial window to 3 segments. increasing the initial window to 3 segments.
RFC 2416 I: "When TCP Starts Up With Four Packets Into Only Three RFC 2416 I: "When TCP Starts Up With Four Packets Into Only Three
Buffers" (September 1998) Buffers" (September 1998)
This document [RFC2416] uses simulation results to clear up some This document [RFC2416] uses simulation results to clear up some
concerns about using an initial window of 4 segments when the concerns about using an initial window of 4 segments when the
network path has less provisioning. network path has less provisioning.
RFC 2884 I: "Performance Evaluation of Explicit Congestion RFC 2884 I: "Performance Evaluation of Explicit Congestion
Notification (ECN) in IP Networks" (July 2000) Notification (ECN) in IP Networks" (July 2000)
This document [RFC2884] describes experimental results that show This document [RFC2884] describes experimental results that show
some improvements to the performance of both short- and long-lived some improvements to the performance of both short- and long-lived
connections due to ECN. connections due to ECN.
8. Undocumented TCP Features 8. Undocumented TCP Features
There are a few important implementation tactics for the TCP that There are a few important implementation tactics for the TCP that
have not yet been described in any RFC. Although this roadmap is have not yet been described in any RFC. Although this roadmap is
primarily concerned with mapping the TCP RFCs, this section is primarily concerned with mapping the TCP RFCs, this section is
included because an implementer needs to be aware of these important included because an implementer needs to be aware of these important
issues. issues.
Header Prediction Header Prediction
Header prediction is a trick to speed up the processing of Header prediction is a trick to speed up the processing of
segments. Van Jacobson and Mike Karels developed the technique in segments. Van Jacobson and Mike Karels developed the technique in
the late 1980s. The basic idea is that some processing time can the late 1980s. The basic idea is that some processing time can
be saved when most of a segment's fields can be predicted from be saved when most of a segment's fields can be predicted from
previous segments. A good description of this was sent to the previous segments. A good description of this was sent to the
TCP-IP mailing list by Van Jacobson on March 9, 1988: TCP-IP mailing list by Van Jacobson on March 9, 1988 (see
[Jacobson] for the full message):
"Quite a bit of the speedup comes from an algorithm that we ('we' Quite a bit of the speedup comes from an algorithm that we
refers to collaborator Mike Karels and myself) are calling "header ('we' refers to collaborator Mike Karels and myself) are
prediction". The idea is that if you're in the middle of a bulk calling "header prediction". The idea is that if you're in the
data transfer and have just seen a packet, you know what the next middle of a bulk data transfer and have just seen a packet, you
packet is going to look like: It will look just like the current know what the next packet is going to look like: It will look
packet with either the sequence number or ack number updated just like the current packet with either the sequence number or
(depending on whether you're the sender or receiver). Combining ack number updated (depending on whether you're the sender or
this with the "Use hints" epigram from Butler Lampson's classic receiver). Combining this with the "Use hints" epigram from
"Epigrams for System Designers", you start to think of the tcp Butler Lampson's classic "Epigrams for System Designers", you
state (rcv.nxt, snd.una, etc.) as "hints" about what the next start to think of the tcp state (rcv.nxt, snd.una, etc.) as
packet should look like. "hints" about what the next packet should look like.
If you arrange those "hints" so they match the layout of a tcp If you arrange those "hints" so they match the layout of a tcp
packet header, it takes a single 14-byte compare to see if your packet header, it takes a single 14-byte compare to see if your
prediction is correct (3 longword compares to pick up the send & prediction is correct (3 longword compares to pick up the send
ack sequence numbers, header length, flags and window, plus a & ack sequence numbers, header length, flags and window, plus a
short compare on the length). If the prediction is correct, short compare on the length). If the prediction is correct,
there's a single test on the length to see if you're the sender or there's a single test on the length to see if you're the sender
receiver followed by the appropriate processing. E.g., if the or receiver followed by the appropriate processing. E.g., if
length is non-zero (you're the receiver), checksum and append the the length is non-zero (you're the receiver), checksum and
data to the socket buffer then wake any process that's sleeping on append the data to the socket buffer then wake any process
the buffer. Update rcv.nxt by the length of this packet (this that's sleeping on the buffer. Update rcv.nxt by the length of
updates your "prediction" of the next packet). Check if you can this packet (this updates your "prediction" of the next
handle another packet the same size as the current one. If not, packet). Check if you can handle another packet the same size
set one of the unused flag bits in your header prediction to as the current one. If not, set one of the unused flag bits in
guarantee that the prediction will fail on the next packet and your header prediction to guarantee that the prediction will
force you to go through full protocol processing. Otherwise, fail on the next packet and force you to go through full
you're done with this packet. So, the *total* tcp protocol protocol processing. Otherwise, you're done with this packet.
processing, exclusive of checksumming, is on the order of 6 So, the *total* tcp protocol processing, exclusive of
compares and an add." checksumming, is on the order of 6 compares and an add.
Forward Acknowledgement (FACK) Forward Acknowledgement (FACK)
FACK [MM96] includes an alternate algorithm for triggering fast FACK [MM96] includes an alternate algorithm for triggering fast
retransmit [RFC5681], based on the extent of the SACK scoreboard. retransmit [RFC5681], based on the extent of the SACK scoreboard.
Its goal is to trigger fast retransmit as soon as the receiver's Its goal is to trigger fast retransmit as soon as the receiver's
reassembly queue is larger than the duplicate ACK threshold, as reassembly queue is larger than the duplicate ACK threshold, as
indicated by the difference between the forward most SACK block indicated by the difference between the forward most SACK block
edge and SND.UNA. This algorithm quickly and reliably triggers edge and SND.UNA. This algorithm quickly and reliably triggers
fast retransmit in the presence of burst losses -- often on the fast retransmit in the presence of burst losses -- often on the
first SACK following such a loss. Such a threshold-based first SACK following such a loss. Such a threshold-based
algorithm also triggers fast retransmit immediately in the algorithm also triggers fast retransmit immediately in the
presence of any reordering with extent greater than the duplicate presence of any reordering with extent greater than the duplicate
ACK threshold. FACK is implemented in Linux and turned on per ACK threshold. FACK is implemented in Linux and turned on per
default. default.
Congestion Control for High Rate Flows Congestion Control for High Rate Flows
In the last decade significant research effort has been put into In the last decade significant research effort has been put into
experimental TCP congestion control modifications for obtaining experimental TCP congestion control modifications for obtaining
high throughput with reduced startup and recovery times. Only few high throughput with reduced startup and recovery times. Only a
RFCs have been published on some of these modifications, including few RFCs have been published on some of these modifications,
HighSpeed TCP [RFC3649] (see Section 4.3), Limited Slow-Start including HighSpeed TCP [RFC3649], Limited Slow-Start [RFC3742],
[RFC3742] (see Section 4.3), and Quick-Start [RFC4782] (see and Quick-Start [RFC4782] (see Section 4.3 of this document for
Section 4.3), but high-rate congestion control mechanisms are more information on each), but high-rate congestion control
still considered an open issue in congestion control research. mechanisms are still considered an open issue in congestion
Some other schemes have been published as Internet-Drafts, e.g. control research. Some other schemes have been published as
CUBIC [I-D.rhee-tcpm-cubic] (the standard TCP congestion control Internet-Drafts, e.g. CUBIC [CUBIC] (the standard TCP congestion
algorithm in Linux), Compound TCP [I-D.sridharan-tcpm-ctcp], and control algorithm in Linux), Compound TCP [CTCP], and H-TCP [HTCP]
H-TCP [I-D.leith-tcp-htcp] or have been discussed a little by the or have been discussed a little by the IETF, but much of the work
IETF, but much of the work in this area has not been adopted in this area has not been adopted within the IETF yet, so the
within the IETF yet, so the majority of this work is outside the majority of this work is outside the RFC series and may be
RFC series and may be discussed in other products of the IRTF discussed in other products of the IRTF Internet Congestion
Internet Congestion Control Research Group (ICCRG). Control Research Group (ICCRG).
9. Security Considerations 9. Security Considerations
This document introduces no new security considerations. Each RFC This document introduces no new security considerations. Each RFC
listed in this document attempts to address the security listed in this document attempts to address the security
considerations of the specification it contains. considerations of the specification it contains.
10. IANA Considerations 10. References
This document contains no IANA considerations.
11. Acknowledgments
This document grew out of a discussion on the end2end-interest
mailing list, the public list of the End-to-End Research Group of the
IRTF, and continued development under the IETF's TCP Maintenance and
Minor Extensions (TCPM) working group. We thank Mark Allman, Yuchung
Cheng, Ted Faber, Fairhurst, Sally Floyd, Janardhan Iyengar, Reiner
Ludwig, Pekka Savola, and Joe Touch for their contributions, in
particular. Keith McCloghrie provided some useful notes and
clarification on the various MIB-related RFCs.
12. References
12.1. Normative References
[I-D.ietf-tcpm-1323bis]
Borman, D., Braden, R., Jacobson, V., and R.
Scheffenegger, "TCP Extensions for High Performance",
draft-ietf-tcpm-1323bis-21 (work in progress), April 2014.
[I-D.ietf-tcpm-fastopen] 10.1. Normative References
Cheng, Y., Chu, J., Radhakrishnan, S., and A. Jain, "TCP
Fast Open", draft-ietf-tcpm-fastopen-09 (work in
progress), July 2014.
[RFC0675] Cerf, V., Dalal, Y., and C. Sunshine, "Specification of [RFC675] Cerf, V., Dalal, Y., and C. Sunshine, "Specification of
Internet Transmission Control Program", RFC 675, Internet Transmission Control Program", RFC 675, December
December 1974. 1974, <http://www.rfc-editor.org/info/rfc675>.
[RFC0700] Mader, E., Plummer, W., and R. Tomlinson, "Protocol [RFC700] Mader, E., Plummer, W., and R. Tomlinson, "Protocol
experiment", RFC 700, August 1974. experiment", RFC 700, August 1974,
<http://www.rfc-editor.org/info/rfc700>.
[RFC0721] Garlick, L., "Out-of-Band Control Signals in a Host-to- [RFC721] Garlick, L., "Out-of-Band Control Signals in a Host-to-
Host Protocol", RFC 721, September 1976. Host Protocol", RFC 721, September 1976,
<http://www.rfc-editor.org/info/rfc721>.
[RFC0761] Postel, J., "DoD standard Transmission Control Protocol", [RFC761] Postel, J., "DoD standard Transmission Control Protocol",
RFC 761, January 1980. RFC 761, January 1980,
<http://www.rfc-editor.org/info/rfc761>.
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7, [RFC793] Postel, J., "Transmission Control Protocol", STD 7, RFC
RFC 793, September 1981. 793, September 1981,
<http://www.rfc-editor.org/info/rfc793>.
[RFC0794] Cerf, V., "Pre-emption", RFC 794, September 1981. [RFC794] Cerf, V., "Pre-emption", RFC 794, September 1981,
<http://www.rfc-editor.org/info/rfc794>.
[RFC0813] Clark, D., "Window and Acknowledgement Strategy in TCP", [RFC813] Clark, D., "Window and Acknowledgement Strategy in TCP",
RFC 813, July 1982. RFC 813, July 1982,
<http://www.rfc-editor.org/info/rfc813>.
[RFC0814] Clark, D., "Name, addresses, ports, and routes", RFC 814, [RFC814] Clark, D., "Name, addresses, ports, and routes", RFC 814,
July 1982. July 1982, <http://www.rfc-editor.org/info/rfc814>.
[RFC0816] Clark, D., "Fault isolation and recovery", RFC 816, [RFC816] Clark, D., "Fault isolation and recovery", RFC 816, July
July 1982. 1982, <http://www.rfc-editor.org/info/rfc816>.
[RFC0817] Clark, D., "Modularity and efficiency in protocol [RFC817] Clark, D., "Modularity and efficiency in protocol
implementation", RFC 817, July 1982. implementation", RFC 817, July 1982,
<http://www.rfc-editor.org/info/rfc817>.
[RFC0872] Padlipsky, M., "TCP-on-a-LAN", RFC 872, September 1982. [RFC872] Padlipsky, M., "TCP-on-a-LAN", RFC 872, September 1982,
<http://www.rfc-editor.org/info/rfc872>.
[RFC0879] Postel, J., "TCP maximum segment size and related topics", [RFC879] Postel, J., "TCP maximum segment size and related topics",
RFC 879, November 1983. RFC 879, November 1983,
<http://www.rfc-editor.org/info/rfc879>.
[RFC0889] Mills, D., "Internet delay experiments", RFC 889, [RFC889] Mills, D., "Internet delay experiments", RFC 889, December
December 1983. 1983, <http://www.rfc-editor.org/info/rfc889>.
[RFC0896] Nagle, J., "Congestion control in IP/TCP internetworks", [RFC896] Nagle, J., "Congestion control in IP/TCP internetworks",
RFC 896, January 1984. RFC 896, January 1984,
<http://www.rfc-editor.org/info/rfc896>.
[RFC0964] Sidhu, D. and T. Blumer, "Some problems with the [RFC964] Sidhu, D. and T. Blumer, "Some problems with the
specification of the Military Standard Transmission specification of the Military Standard Transmission
Control Protocol", RFC 964, November 1985. Control Protocol", RFC 964, November 1985,
<http://www.rfc-editor.org/info/rfc964>.
[RFC1071] Braden, R., Borman, D., Partridge, C., and W. Plummer, [RFC1071] Braden, R., Borman, D., Partridge, C., and W. Plummer,
"Computing the Internet checksum", RFC 1071, "Computing the Internet checksum", RFC 1071, September
September 1988. 1988, <http://www.rfc-editor.org/info/rfc1071>.
[RFC1078] Lottor, M., "TCP port service Multiplexer (TCPMUX)", [RFC1078] Lottor, M., "TCP port service Multiplexer (TCPMUX)", RFC
RFC 1078, November 1988. 1078, November 1988,
<http://www.rfc-editor.org/info/rfc1078>.
[RFC1106] Fox, R., "TCP big window and NAK options", RFC 1106, [RFC1106] Fox, R., "TCP big window and NAK options", RFC 1106, June
June 1989. 1989, <http://www.rfc-editor.org/info/rfc1106>.
[RFC1110] McKenzie, A., "Problem with the TCP big window option", [RFC1110] McKenzie, A., "Problem with the TCP big window option",
RFC 1110, August 1989. RFC 1110, August 1989,
<http://www.rfc-editor.org/info/rfc1110>.
[RFC1122] Braden, R., "Requirements for Internet Hosts - [RFC1122] Braden, R., "Requirements for Internet Hosts -
Communication Layers", STD 3, RFC 1122, October 1989. Communication Layers", STD 3, RFC 1122, October 1989,
<http://www.rfc-editor.org/info/rfc1122>.
[RFC1144] Jacobson, V., "Compressing TCP/IP headers for low-speed [RFC1144] Jacobson, V., "Compressing TCP/IP headers for low-speed
serial links", RFC 1144, February 1990. serial links", RFC 1144, February 1990,
<http://www.rfc-editor.org/info/rfc1144>.
[RFC1146] Zweig, J. and C. Partridge, "TCP alternate checksum [RFC1146] Zweig, J. and C. Partridge, "TCP alternate checksum
options", RFC 1146, March 1990. options", RFC 1146, March 1990,
<http://www.rfc-editor.org/info/rfc1146>.
[RFC1156] McCloghrie, K. and M. Rose, "Management Information Base [RFC1156] McCloghrie, K. and M. Rose, "Management Information Base
for network management of TCP/IP-based internets", for network management of TCP/IP-based internets", RFC
RFC 1156, May 1990. 1156, May 1990, <http://www.rfc-editor.org/info/rfc1156>.
[RFC1180] Socolofsky, T. and C. Kale, "TCP/IP tutorial", RFC 1180, [RFC1180] Socolofsky, T. and C. Kale, "TCP/IP tutorial", RFC 1180,
January 1991. January 1991, <http://www.rfc-editor.org/info/rfc1180>.
[RFC1191] Mogul, J. and S. Deering, "Path MTU discovery", RFC 1191, [RFC1191] Mogul, J. and S. Deering, "Path MTU discovery", RFC 1191,
November 1990. November 1990, <http://www.rfc-editor.org/info/rfc1191>.
[RFC1213] McCloghrie, K. and M. Rose, "Management Information Base [RFC1213] McCloghrie, K. and M. Rose, "Management Information Base
for Network Management of TCP/IP-based internets:MIB-II", for Network Management of TCP/IP-based internets:MIB-II",
STD 17, RFC 1213, March 1991. STD 17, RFC 1213, March 1991,
<http://www.rfc-editor.org/info/rfc1213>.
[RFC1263] O'Malley, S. and L. Peterson, "TCP Extensions Considered [RFC1263] O'Malley, S. and L. Peterson, "TCP Extensions Considered
Harmful", RFC 1263, October 1991. Harmful", RFC 1263, October 1991,
<http://www.rfc-editor.org/info/rfc1263>.
[RFC1337] Braden, B., "TIME-WAIT Assassination Hazards in TCP", [RFC1337] Braden, B., "TIME-WAIT Assassination Hazards in TCP", RFC
RFC 1337, May 1992. 1337, May 1992, <http://www.rfc-editor.org/info/rfc1337>.
[RFC1379] Braden, B., "Extending TCP for Transactions -- Concepts", [RFC1379] Braden, B., "Extending TCP for Transactions -- Concepts",
RFC 1379, November 1992. RFC 1379, November 1992,
<http://www.rfc-editor.org/info/rfc1379>.
[RFC1470] Enger, R. and J. Reynolds, "FYI on a Network Management [RFC1470] Enger, R. and J. Reynolds, "FYI on a Network Management
Tool Catalog: Tools for Monitoring and Debugging TCP/IP Tool Catalog: Tools for Monitoring and Debugging TCP/IP
Internets and Interconnected Devices", RFC 1470, Internets and Interconnected Devices", RFC 1470, June
June 1993. 1993, <http://www.rfc-editor.org/info/rfc1470>.
[RFC1624] Rijsinghani, A., "Computation of the Internet Checksum via [RFC1624] Rijsinghani, A., "Computation of the Internet Checksum via
Incremental Update", RFC 1624, May 1994. Incremental Update", RFC 1624, May 1994,
<http://www.rfc-editor.org/info/rfc1624>.
[RFC1644] Braden, B., "T/TCP -- TCP Extensions for Transactions [RFC1644] Braden, B., "T/TCP -- TCP Extensions for Transactions
Functional Specification", RFC 1644, July 1994. Functional Specification", RFC 1644, July 1994,
<http://www.rfc-editor.org/info/rfc1644>.
[RFC1693] Connolly, T., Amer, P., and P. Conrad, "An Extension to [RFC1693] Connolly, T., Amer, P., and P. Conrad, "An Extension to
TCP : Partial Order Service", RFC 1693, November 1994. TCP : Partial Order Service", RFC 1693, November 1994,
<http://www.rfc-editor.org/info/rfc1693>.
[RFC1705] Carlson, R. and D. Ficarella, "Six Virtual Inches to the [RFC1705] Carlson, R. and D. Ficarella, "Six Virtual Inches to the
Left: The Problem with IPng", RFC 1705, October 1994. Left: The Problem with IPng", RFC 1705, October 1994,
<http://www.rfc-editor.org/info/rfc1705>.
[RFC1936] Touch, J. and B. Parham, "Implementing the Internet [RFC1936] Touch, J. and B. Parham, "Implementing the Internet
Checksum in Hardware", RFC 1936, April 1996. Checksum in Hardware", RFC 1936, April 1996,
<http://www.rfc-editor.org/info/rfc1936>.
[RFC1958] Carpenter, B., "Architectural Principles of the Internet", [RFC1958] Carpenter, B., "Architectural Principles of the Internet",
RFC 1958, June 1996. RFC 1958, June 1996,
<http://www.rfc-editor.org/info/rfc1958>.
[RFC1981] McCann, J., Deering, S., and J. Mogul, "Path MTU Discovery [RFC1981] McCann, J., Deering, S., and J. Mogul, "Path MTU Discovery
for IP version 6", RFC 1981, August 1996. for IP version 6", RFC 1981, August 1996,
<http://www.rfc-editor.org/info/rfc1981>.
[RFC2012] McCloghrie, K., "SNMPv2 Management Information Base for [RFC2012] McCloghrie, K., "SNMPv2 Management Information Base for
the Transmission Control Protocol using SMIv2", RFC 2012, the Transmission Control Protocol using SMIv2", RFC 2012,
November 1996. November 1996, <http://www.rfc-editor.org/info/rfc2012>.
[RFC2018] Mathis, M., Mahdavi, J., Floyd, S., and A. Romanow, "TCP [RFC2018] Mathis, M., Mahdavi, J., Floyd, S., and A. Romanow, "TCP
Selective Acknowledgment Options", RFC 2018, October 1996. Selective Acknowledgment Options", RFC 2018, October 1996,
<http://www.rfc-editor.org/info/rfc2018>.
[RFC2140] Touch, J., "TCP Control Block Interdependence", RFC 2140, [RFC2140] Touch, J., "TCP Control Block Interdependence", RFC 2140,
April 1997. April 1997, <http://www.rfc-editor.org/info/rfc2140>.
[RFC2398] Parker, S. and C. Schmechel, "Some Testing Tools for TCP [RFC2398] Parker, S. and C. Schmechel, "Some Testing Tools for TCP
Implementors", RFC 2398, August 1998. Implementors", RFC 2398, August 1998,
<http://www.rfc-editor.org/info/rfc2398>.
[RFC2415] Poduri, K., "Simulation Studies of Increased Initial TCP [RFC2415] Poduri, K., "Simulation Studies of Increased Initial TCP
Window Size", RFC 2415, September 1998. Window Size", RFC 2415, September 1998,
<http://www.rfc-editor.org/info/rfc2415>.
[RFC2416] Shepard, T. and C. Partridge, "When TCP Starts Up With [RFC2416] Shepard, T. and C. Partridge, "When TCP Starts Up With
Four Packets Into Only Three Buffers", RFC 2416, Four Packets Into Only Three Buffers", RFC 2416, September
September 1998. 1998, <http://www.rfc-editor.org/info/rfc2416>.
[RFC2452] Daniele, M., "IP Version 6 Management Information Base for [RFC2452] Daniele, M., "IP Version 6 Management Information Base for
the Transmission Control Protocol", RFC 2452, the Transmission Control Protocol", RFC 2452, December
December 1998. 1998, <http://www.rfc-editor.org/info/rfc2452>.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998. (IPv6) Specification", RFC 2460, December 1998,
<http://www.rfc-editor.org/info/rfc2460>.
[RFC2488] Allman, M., Glover, D., and L. Sanchez, "Enhancing TCP [RFC2488] Allman, M., Glover, D., and L. Sanchez, "Enhancing TCP
Over Satellite Channels using Standard Mechanisms", Over Satellite Channels using Standard Mechanisms", BCP
BCP 28, RFC 2488, January 1999. 28, RFC 2488, January 1999,
<http://www.rfc-editor.org/info/rfc2488>.
[RFC2525] Paxson, V., Dawson, S., Fenner, W., Griner, J., Heavens, [RFC2525] Paxson, V., Dawson, S., Fenner, W., Griner, J., Heavens,
I., Lahey, K., Semke, J., and B. Volz, "Known TCP I., Lahey, K., Semke, J., and B. Volz, "Known TCP
Implementation Problems", RFC 2525, March 1999. Implementation Problems", RFC 2525, March 1999,
<http://www.rfc-editor.org/info/rfc2525>.
[RFC2675] Borman, D., Deering, S., and R. Hinden, "IPv6 Jumbograms", [RFC2675] Borman, D., Deering, S., and R. Hinden, "IPv6 Jumbograms",
RFC 2675, August 1999. RFC 2675, August 1999,
<http://www.rfc-editor.org/info/rfc2675>.
[RFC2757] Montenegro, G., Dawkins, S., Kojo, M., Magret, V., and N. [RFC2757] Montenegro, G., Dawkins, S., Kojo, M., Magret, V., and N.
Vaidya, "Long Thin Networks", RFC 2757, January 2000. Vaidya, "Long Thin Networks", RFC 2757, January 2000,
<http://www.rfc-editor.org/info/rfc2757>.
[RFC2760] Allman, M., Dawkins, S., Glover, D., Griner, J., Tran, D., [RFC2760] Allman, M., Dawkins, S., Glover, D., Griner, J., Tran, D.,
Henderson, T., Heidemann, J., Touch, J., Kruse, H., Henderson, T., Heidemann, J., Touch, J., Kruse, H.,
Ostermann, S., Scott, K., and J. Semke, "Ongoing TCP Ostermann, S., Scott, K., and J. Semke, "Ongoing TCP
Research Related to Satellites", RFC 2760, February 2000. Research Related to Satellites", RFC 2760, February 2000,
<http://www.rfc-editor.org/info/rfc2760>.
[RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For [RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For
Values In the Internet Protocol and Related Headers", Values In the Internet Protocol and Related Headers", BCP
BCP 37, RFC 2780, March 2000. 37, RFC 2780, March 2000,
<http://www.rfc-editor.org/info/rfc2780>.
[RFC2861] Handley, M., Padhye, J., and S. Floyd, "TCP Congestion [RFC2861] Handley, M., Padhye, J., and S. Floyd, "TCP Congestion
Window Validation", RFC 2861, June 2000. Window Validation", RFC 2861, June 2000,
<http://www.rfc-editor.org/info/rfc2861>.
[RFC2873] Xiao, X., Hannan, A., Paxson, V., and E. Crabbe, "TCP [RFC2873] Xiao, X., Hannan, A., Paxson, V., and E. Crabbe, "TCP
Processing of the IPv4 Precedence Field", RFC 2873, Processing of the IPv4 Precedence Field", RFC 2873, June
June 2000. 2000, <http://www.rfc-editor.org/info/rfc2873>.
[RFC2883] Floyd, S., Mahdavi, J., Mathis, M., and M. Podolsky, "An [RFC2883] Floyd, S., Mahdavi, J., Mathis, M., and M. Podolsky, "An
Extension to the Selective Acknowledgement (SACK) Option Extension to the Selective Acknowledgement (SACK) Option
for TCP", RFC 2883, July 2000. for TCP", RFC 2883, July 2000,
<http://www.rfc-editor.org/info/rfc2883>.
[RFC2884] Hadi Salim, J. and U. Ahmed, "Performance Evaluation of [RFC2884] Hadi Salim, J. and U. Ahmed, "Performance Evaluation of
Explicit Congestion Notification (ECN) in IP Networks", Explicit Congestion Notification (ECN) in IP Networks",
RFC 2884, July 2000. RFC 2884, July 2000,
<http://www.rfc-editor.org/info/rfc2884>.
[RFC2914] Floyd, S., "Congestion Control Principles", BCP 41, [RFC2914] Floyd, S., "Congestion Control Principles", BCP 41, RFC
RFC 2914, September 2000. 2914, September 2000,
<http://www.rfc-editor.org/info/rfc2914>.
[RFC2923] Lahey, K., "TCP Problems with Path MTU Discovery", [RFC2923] Lahey, K., "TCP Problems with Path MTU Discovery", RFC
RFC 2923, September 2000. 2923, September 2000,
<http://www.rfc-editor.org/info/rfc2923>.
[RFC3042] Allman, M., Balakrishnan, H., and S. Floyd, "Enhancing [RFC3042] Allman, M., Balakrishnan, H., and S. Floyd, "Enhancing
TCP's Loss Recovery Using Limited Transmit", RFC 3042, TCP's Loss Recovery Using Limited Transmit", RFC 3042,
January 2001. January 2001, <http://www.rfc-editor.org/info/rfc3042>.
[RFC3124] Balakrishnan, H. and S. Seshan, "The Congestion Manager", [RFC3124] Balakrishnan, H. and S. Seshan, "The Congestion Manager",
RFC 3124, June 2001. RFC 3124, June 2001,
<http://www.rfc-editor.org/info/rfc3124>.
[RFC3135] Border, J., Kojo, M., Griner, J., Montenegro, G., and Z. [RFC3135] Border, J., Kojo, M., Griner, J., Montenegro, G., and Z.
Shelby, "Performance Enhancing Proxies Intended to Shelby, "Performance Enhancing Proxies Intended to
Mitigate Link-Related Degradations", RFC 3135, June 2001. Mitigate Link-Related Degradations", RFC 3135, June 2001,
<http://www.rfc-editor.org/info/rfc3135>.
[RFC3150] Dawkins, S., Montenegro, G., Kojo, M., and V. Magret, [RFC3150] Dawkins, S., Montenegro, G., Kojo, M., and V. Magret,
"End-to-end Performance Implications of Slow Links", "End-to-end Performance Implications of Slow Links", BCP
BCP 48, RFC 3150, July 2001. 48, RFC 3150, July 2001,
<http://www.rfc-editor.org/info/rfc3150>.
[RFC3155] Dawkins, S., Montenegro, G., Kojo, M., Magret, V., and N. [RFC3155] Dawkins, S., Montenegro, G., Kojo, M., Magret, V., and N.
Vaidya, "End-to-end Performance Implications of Links with Vaidya, "End-to-end Performance Implications of Links with
Errors", BCP 50, RFC 3155, August 2001. Errors", BCP 50, RFC 3155, August 2001,
<http://www.rfc-editor.org/info/rfc3155>.
[RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition [RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition
of Explicit Congestion Notification (ECN) to IP", of Explicit Congestion Notification (ECN) to IP", RFC
RFC 3168, September 2001. 3168, September 2001,
<http://www.rfc-editor.org/info/rfc3168>.
[RFC3360] Floyd, S., "Inappropriate TCP Resets Considered Harmful", [RFC3360] Floyd, S., "Inappropriate TCP Resets Considered Harmful",
BCP 60, RFC 3360, August 2002. BCP 60, RFC 3360, August 2002,
<http://www.rfc-editor.org/info/rfc3360>.
[RFC3366] Fairhurst, G. and L. Wood, "Advice to link designers on [RFC3366] Fairhurst, G. and L. Wood, "Advice to link designers on
link Automatic Repeat reQuest (ARQ)", BCP 62, RFC 3366, link Automatic Repeat reQuest (ARQ)", BCP 62, RFC 3366,
August 2002. August 2002, <http://www.rfc-editor.org/info/rfc3366>.
[RFC3390] Allman, M., Floyd, S., and C. Partridge, "Increasing TCP's [RFC3390] Allman, M., Floyd, S., and C. Partridge, "Increasing TCP's
Initial Window", RFC 3390, October 2002. Initial Window", RFC 3390, October 2002,
<http://www.rfc-editor.org/info/rfc3390>.
[RFC3439] Bush, R. and D. Meyer, "Some Internet Architectural [RFC3439] Bush, R. and D. Meyer, "Some Internet Architectural
Guidelines and Philosophy", RFC 3439, December 2002. Guidelines and Philosophy", RFC 3439, December 2002,
<http://www.rfc-editor.org/info/rfc3439>.
[RFC3449] Balakrishnan, H., Padmanabhan, V., Fairhurst, G., and M. [RFC3449] Balakrishnan, H., Padmanabhan, V., Fairhurst, G., and M.
Sooriyabandara, "TCP Performance Implications of Network Sooriyabandara, "TCP Performance Implications of Network
Path Asymmetry", BCP 69, RFC 3449, December 2002. Path Asymmetry", BCP 69, RFC 3449, December 2002,
<http://www.rfc-editor.org/info/rfc3449>.
[RFC3465] Allman, M., "TCP Congestion Control with Appropriate Byte [RFC3465] Allman, M., "TCP Congestion Control with Appropriate Byte
Counting (ABC)", RFC 3465, February 2003. Counting (ABC)", RFC 3465, February 2003,
<http://www.rfc-editor.org/info/rfc3465>.
[RFC3481] Inamura, H., Montenegro, G., Ludwig, R., Gurtov, A., and [RFC3481] Inamura, H., Montenegro, G., Ludwig, R., Gurtov, A., and
F. Khafizov, "TCP over Second (2.5G) and Third (3G) F. Khafizov, "TCP over Second (2.5G) and Third (3G)
Generation Wireless Networks", BCP 71, RFC 3481, Generation Wireless Networks", BCP 71, RFC 3481, February
February 2003. 2003, <http://www.rfc-editor.org/info/rfc3481>.
[RFC3493] Gilligan, R., Thomson, S., Bound, J., McCann, J., and W. [RFC3493] Gilligan, R., Thomson, S., Bound, J., McCann, J., and W.
Stevens, "Basic Socket Interface Extensions for IPv6", Stevens, "Basic Socket Interface Extensions for IPv6", RFC
RFC 3493, February 2003. 3493, February 2003,
<http://www.rfc-editor.org/info/rfc3493>.
[RFC3522] Ludwig, R. and M. Meyer, "The Eifel Detection Algorithm [RFC3522] Ludwig, R. and M. Meyer, "The Eifel Detection Algorithm
for TCP", RFC 3522, April 2003. for TCP", RFC 3522, April 2003,
<http://www.rfc-editor.org/info/rfc3522>.
[RFC3540] Spring, N., Wetherall, D., and D. Ely, "Robust Explicit [RFC3540] Spring, N., Wetherall, D., and D. Ely, "Robust Explicit
Congestion Notification (ECN) Signaling with Nonces", Congestion Notification (ECN) Signaling with Nonces", RFC
RFC 3540, June 2003. 3540, June 2003, <http://www.rfc-editor.org/info/rfc3540>.
[RFC3649] Floyd, S., "HighSpeed TCP for Large Congestion Windows", [RFC3649] Floyd, S., "HighSpeed TCP for Large Congestion Windows",
RFC 3649, December 2003. RFC 3649, December 2003,
<http://www.rfc-editor.org/info/rfc3649>.
[RFC3708] Blanton, E. and M. Allman, "Using TCP Duplicate Selective [RFC3708] Blanton, E. and M. Allman, "Using TCP Duplicate Selective
Acknowledgement (DSACKs) and Stream Control Transmission Acknowledgement (DSACKs) and Stream Control Transmission
Protocol (SCTP) Duplicate Transmission Sequence Numbers Protocol (SCTP) Duplicate Transmission Sequence Numbers
(TSNs) to Detect Spurious Retransmissions", RFC 3708, (TSNs) to Detect Spurious Retransmissions", RFC 3708,
February 2004. February 2004, <http://www.rfc-editor.org/info/rfc3708>.
[RFC3742] Floyd, S., "Limited Slow-Start for TCP with Large [RFC3742] Floyd, S., "Limited Slow-Start for TCP with Large
Congestion Windows", RFC 3742, March 2004. Congestion Windows", RFC 3742, March 2004,
<http://www.rfc-editor.org/info/rfc3742>.
[RFC3819] Karn, P., Bormann, C., Fairhurst, G., Grossman, D., [RFC3819] Karn, P., Bormann, C., Fairhurst, G., Grossman, D.,
Ludwig, R., Mahdavi, J., Montenegro, G., Touch, J., and L. Ludwig, R., Mahdavi, J., Montenegro, G., Touch, J., and L.
Wood, "Advice for Internet Subnetwork Designers", BCP 89, Wood, "Advice for Internet Subnetwork Designers", BCP 89,
RFC 3819, July 2004. RFC 3819, July 2004,
<http://www.rfc-editor.org/info/rfc3819>.
[RFC4015] Ludwig, R. and A. Gurtov, "The Eifel Response Algorithm [RFC4015] Ludwig, R. and A. Gurtov, "The Eifel Response Algorithm
for TCP", RFC 4015, February 2005. for TCP", RFC 4015, February 2005,
<http://www.rfc-editor.org/info/rfc4015>.
[RFC4022] Raghunarayan, R., "Management Information Base for the [RFC4022] Raghunarayan, R., "Management Information Base for the
Transmission Control Protocol (TCP)", RFC 4022, Transmission Control Protocol (TCP)", RFC 4022, March
March 2005. 2005, <http://www.rfc-editor.org/info/rfc4022>.
[RFC4653] Bhandarkar, S., Reddy, A., Allman, M., and E. Blanton, [RFC4653] Bhandarkar, S., Reddy, A., Allman, M., and E. Blanton,
"Improving the Robustness of TCP to Non-Congestion "Improving the Robustness of TCP to Non-Congestion
Events", RFC 4653, August 2006. Events", RFC 4653, August 2006,
<http://www.rfc-editor.org/info/rfc4653>.
[RFC4727] Fenner, B., "Experimental Values In IPv4, IPv6, ICMPv4, [RFC4727] Fenner, B., "Experimental Values In IPv4, IPv6, ICMPv4,
ICMPv6, UDP, and TCP Headers", RFC 4727, November 2006. ICMPv6, UDP, and TCP Headers", RFC 4727, November 2006,
<http://www.rfc-editor.org/info/rfc4727>.
[RFC4774] Floyd, S., "Specifying Alternate Semantics for the [RFC4774] Floyd, S., "Specifying Alternate Semantics for the
Explicit Congestion Notification (ECN) Field", BCP 124, Explicit Congestion Notification (ECN) Field", BCP 124,
RFC 4774, November 2006. RFC 4774, November 2006,
<http://www.rfc-editor.org/info/rfc4774>.
[RFC4782] Floyd, S., Allman, M., Jain, A., and P. Sarolahti, "Quick- [RFC4782] Floyd, S., Allman, M., Jain, A., and P. Sarolahti, "Quick-
Start for TCP and IP", RFC 4782, January 2007. Start for TCP and IP", RFC 4782, January 2007,
<http://www.rfc-editor.org/info/rfc4782>.
[RFC4821] Mathis, M. and J. Heffner, "Packetization Layer Path MTU [RFC4821] Mathis, M. and J. Heffner, "Packetization Layer Path MTU
Discovery", RFC 4821, March 2007. Discovery", RFC 4821, March 2007,
<http://www.rfc-editor.org/info/rfc4821>.
[RFC4898] Mathis, M., Heffner, J., and R. Raghunarayan, "TCP [RFC4898] Mathis, M., Heffner, J., and R. Raghunarayan, "TCP
Extended Statistics MIB", RFC 4898, May 2007. Extended Statistics MIB", RFC 4898, May 2007,
<http://www.rfc-editor.org/info/rfc4898>.
[RFC4953] Touch, J., "Defending TCP Against Spoofing Attacks", [RFC4953] Touch, J., "Defending TCP Against Spoofing Attacks", RFC
RFC 4953, July 2007. 4953, July 2007, <http://www.rfc-editor.org/info/rfc4953>.
[RFC4987] Eddy, W., "TCP SYN Flooding Attacks and Common [RFC4987] Eddy, W., "TCP SYN Flooding Attacks and Common
Mitigations", RFC 4987, August 2007. Mitigations", RFC 4987, August 2007,
<http://www.rfc-editor.org/info/rfc4987>.
[RFC5033] Floyd, S. and M. Allman, "Specifying New Congestion [RFC5033] Floyd, S. and M. Allman, "Specifying New Congestion
Control Algorithms", BCP 133, RFC 5033, August 2007. Control Algorithms", BCP 133, RFC 5033, August 2007,
<http://www.rfc-editor.org/info/rfc5033>.
[RFC5166] Floyd, S., "Metrics for the Evaluation of Congestion [RFC5166] Floyd, S., "Metrics for the Evaluation of Congestion
Control Mechanisms", RFC 5166, March 2008. Control Mechanisms", RFC 5166, March 2008,
<http://www.rfc-editor.org/info/rfc5166>.
[RFC5461] Gont, F., "TCP's Reaction to Soft Errors", RFC 5461, [RFC5461] Gont, F., "TCP's Reaction to Soft Errors", RFC 5461,
February 2009. February 2009, <http://www.rfc-editor.org/info/rfc5461>.
[RFC5482] Eggert, L. and F. Gont, "TCP User Timeout Option", [RFC5482] Eggert, L. and F. Gont, "TCP User Timeout Option", RFC
RFC 5482, March 2009. 5482, March 2009,
<http://www.rfc-editor.org/info/rfc5482>.
[RFC5562] Kuzmanovic, A., Mondal, A., Floyd, S., and K. [RFC5562] Kuzmanovic, A., Mondal, A., Floyd, S., and K.
Ramakrishnan, "Adding Explicit Congestion Notification Ramakrishnan, "Adding Explicit Congestion Notification
(ECN) Capability to TCP's SYN/ACK Packets", RFC 5562, (ECN) Capability to TCP's SYN/ACK Packets", RFC 5562, June
June 2009. 2009, <http://www.rfc-editor.org/info/rfc5562>.
[RFC5681] Allman, M., Paxson, V., and E. Blanton, "TCP Congestion [RFC5681] Allman, M., Paxson, V., and E. Blanton, "TCP Congestion
Control", RFC 5681, September 2009. Control", RFC 5681, September 2009,
<http://www.rfc-editor.org/info/rfc5681>.
[RFC5682] Sarolahti, P., Kojo, M., Yamamoto, K., and M. Hata, [RFC5682] Sarolahti, P., Kojo, M., Yamamoto, K., and M. Hata,
"Forward RTO-Recovery (F-RTO): An Algorithm for Detecting "Forward RTO-Recovery (F-RTO): An Algorithm for Detecting
Spurious Retransmission Timeouts with TCP", RFC 5682, Spurious Retransmission Timeouts with TCP", RFC 5682,
September 2009. September 2009, <http://www.rfc-editor.org/info/rfc5682>.
[RFC5690] Floyd, S., Arcia, A., Ros, D., and J. Iyengar, "Adding [RFC5690] Floyd, S., Arcia, A., Ros, D., and J. Iyengar, "Adding
Acknowledgement Congestion Control to TCP", RFC 5690, Acknowledgement Congestion Control to TCP", RFC 5690,
February 2010. February 2010, <http://www.rfc-editor.org/info/rfc5690>.
[RFC5783] Welzl, M. and W. Eddy, "Congestion Control in the RFC [RFC5783] Welzl, M. and W. Eddy, "Congestion Control in the RFC
Series", RFC 5783, February 2010. Series", RFC 5783, February 2010,
<http://www.rfc-editor.org/info/rfc5783>.
[RFC5827] Allman, M., Avrachenkov, K., Ayesta, U., Blanton, J., and [RFC5827] Allman, M., Avrachenkov, K., Ayesta, U., Blanton, J., and
P. Hurtig, "Early Retransmit for TCP and Stream Control P. Hurtig, "Early Retransmit for TCP and Stream Control
Transmission Protocol (SCTP)", RFC 5827, May 2010. Transmission Protocol (SCTP)", RFC 5827, May 2010,
<http://www.rfc-editor.org/info/rfc5827>.
[RFC5925] Touch, J., Mankin, A., and R. Bonica, "The TCP [RFC5925] Touch, J., Mankin, A., and R. Bonica, "The TCP
Authentication Option", RFC 5925, June 2010. Authentication Option", RFC 5925, June 2010,
<http://www.rfc-editor.org/info/rfc5925>.
[RFC5926] Lebovitz, G. and E. Rescorla, "Cryptographic Algorithms [RFC5926] Lebovitz, G. and E. Rescorla, "Cryptographic Algorithms
for the TCP Authentication Option (TCP-AO)", RFC 5926, for the TCP Authentication Option (TCP-AO)", RFC 5926,
June 2010. June 2010, <http://www.rfc-editor.org/info/rfc5926>.
[RFC5927] Gont, F., "ICMP Attacks against TCP", RFC 5927, July 2010. [RFC5927] Gont, F., "ICMP Attacks against TCP", RFC 5927, July 2010,
<http://www.rfc-editor.org/info/rfc5927>.
[RFC5961] Ramaiah, A., Stewart, R., and M. Dalal, "Improving TCP's [RFC5961] Ramaiah, A., Stewart, R., and M. Dalal, "Improving TCP's
Robustness to Blind In-Window Attacks", RFC 5961, Robustness to Blind In-Window Attacks", RFC 5961, August
August 2010. 2010, <http://www.rfc-editor.org/info/rfc5961>.
[RFC6013] Simpson, W., "TCP Cookie Transactions (TCPCT)", RFC 6013, [RFC6013] Simpson, W., "TCP Cookie Transactions (TCPCT)", RFC 6013,
January 2011. January 2011, <http://www.rfc-editor.org/info/rfc6013>.
[RFC6056] Larsen, M. and F. Gont, "Recommendations for Transport- [RFC6056] Larsen, M. and F. Gont, "Recommendations for Transport-
Protocol Port Randomization", BCP 156, RFC 6056, Protocol Port Randomization", BCP 156, RFC 6056, January
January 2011. 2011, <http://www.rfc-editor.org/info/rfc6056>.
[RFC6069] Zimmermann, A. and A. Hannemann, "Making TCP More Robust [RFC6069] Zimmermann, A. and A. Hannemann, "Making TCP More Robust
to Long Connectivity Disruptions (TCP-LCD)", RFC 6069, to Long Connectivity Disruptions (TCP-LCD)", RFC 6069,
December 2010. December 2010, <http://www.rfc-editor.org/info/rfc6069>.
[RFC6077] Papadimitriou, D., Welzl, M., Scharf, M., and B. Briscoe, [RFC6077] Papadimitriou, D., Welzl, M., Scharf, M., and B. Briscoe,
"Open Research Issues in Internet Congestion Control", "Open Research Issues in Internet Congestion Control", RFC
RFC 6077, February 2011. 6077, February 2011,
<http://www.rfc-editor.org/info/rfc6077>.
[RFC6093] Gont, F. and A. Yourtchenko, "On the Implementation of the [RFC6093] Gont, F. and A. Yourtchenko, "On the Implementation of the
TCP Urgent Mechanism", RFC 6093, January 2011. TCP Urgent Mechanism", RFC 6093, January 2011,
<http://www.rfc-editor.org/info/rfc6093>.
[RFC6181] Bagnulo, M., "Threat Analysis for TCP Extensions for [RFC6181] Bagnulo, M., "Threat Analysis for TCP Extensions for
Multipath Operation with Multiple Addresses", RFC 6181, Multipath Operation with Multiple Addresses", RFC 6181,
March 2011. March 2011, <http://www.rfc-editor.org/info/rfc6181>.
[RFC6182] Ford, A., Raiciu, C., Handley, M., Barre, S., and J. [RFC6182] Ford, A., Raiciu, C., Handley, M., Barre, S., and J.
Iyengar, "Architectural Guidelines for Multipath TCP Iyengar, "Architectural Guidelines for Multipath TCP
Development", RFC 6182, March 2011. Development", RFC 6182, March 2011,
<http://www.rfc-editor.org/info/rfc6182>.
[RFC6191] Gont, F., "Reducing the TIME-WAIT State Using TCP [RFC6191] Gont, F., "Reducing the TIME-WAIT State Using TCP
Timestamps", BCP 159, RFC 6191, April 2011. Timestamps", BCP 159, RFC 6191, April 2011,
<http://www.rfc-editor.org/info/rfc6191>.
[RFC6247] Eggert, L., "Moving the Undeployed TCP Extensions RFC [RFC6247] Eggert, L., "Moving the Undeployed TCP Extensions RFC
1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379,
RFC 1644, and RFC 1693 to Historic Status", RFC 6247, RFC 1644, and RFC 1693 to Historic Status", RFC 6247, May
May 2011. 2011, <http://www.rfc-editor.org/info/rfc6247>.
[RFC6298] Paxson, V., Allman, M., Chu, J., and M. Sargent, [RFC6298] Paxson, V., Allman, M., Chu, J., and M. Sargent,
"Computing TCP's Retransmission Timer", RFC 6298, "Computing TCP's Retransmission Timer", RFC 6298, June
June 2011. 2011, <http://www.rfc-editor.org/info/rfc6298>.
[RFC6335] Cotton, M., Eggert, L., Touch, J., Westerlund, M., and S. [RFC6335] Cotton, M., Eggert, L., Touch, J., Westerlund, M., and S.
Cheshire, "Internet Assigned Numbers Authority (IANA) Cheshire, "Internet Assigned Numbers Authority (IANA)
Procedures for the Management of the Service Name and Procedures for the Management of the Service Name and
Transport Protocol Port Number Registry", BCP 165, Transport Protocol Port Number Registry", BCP 165, RFC
RFC 6335, August 2011. 6335, August 2011,
<http://www.rfc-editor.org/info/rfc6335>.
[RFC6349] Constantine, B., Forget, G., Geib, R., and R. Schrage, [RFC6349] Constantine, B., Forget, G., Geib, R., and R. Schrage,
"Framework for TCP Throughput Testing", RFC 6349, "Framework for TCP Throughput Testing", RFC 6349, August
August 2011. 2011, <http://www.rfc-editor.org/info/rfc6349>.
[RFC6356] Raiciu, C., Handley, M., and D. Wischik, "Coupled [RFC6356] Raiciu, C., Handley, M., and D. Wischik, "Coupled
Congestion Control for Multipath Transport Protocols", Congestion Control for Multipath Transport Protocols", RFC
RFC 6356, October 2011. 6356, October 2011,
<http://www.rfc-editor.org/info/rfc6356>.
[RFC6429] Bashyam, M., Jethanandani, M., and A. Ramaiah, "TCP Sender [RFC6429] Bashyam, M., Jethanandani, M., and A. Ramaiah, "TCP Sender
Clarification for Persist Condition", RFC 6429, Clarification for Persist Condition", RFC 6429, December
December 2011. 2011, <http://www.rfc-editor.org/info/rfc6429>.
[RFC6528] Gont, F. and S. Bellovin, "Defending against Sequence [RFC6528] Gont, F. and S. Bellovin, "Defending against Sequence
Number Attacks", RFC 6528, February 2012. Number Attacks", RFC 6528, February 2012,
<http://www.rfc-editor.org/info/rfc6528>.
[RFC6582] Henderson, T., Floyd, S., Gurtov, A., and Y. Nishida, "The [RFC6582] Henderson, T., Floyd, S., Gurtov, A., and Y. Nishida, "The
NewReno Modification to TCP's Fast Recovery Algorithm", NewReno Modification to TCP's Fast Recovery Algorithm",
RFC 6582, April 2012. RFC 6582, April 2012,
<http://www.rfc-editor.org/info/rfc6582>.
[RFC6633] Gont, F., "Deprecation of ICMP Source Quench Messages", [RFC6633] Gont, F., "Deprecation of ICMP Source Quench Messages",
RFC 6633, May 2012. RFC 6633, May 2012,
<http://www.rfc-editor.org/info/rfc6633>.
[RFC6675] Blanton, E., Allman, M., Wang, L., Jarvinen, I., Kojo, M., [RFC6675] Blanton, E., Allman, M., Wang, L., Jarvinen, I., Kojo, M.,
and Y. Nishida, "A Conservative Loss Recovery Algorithm and Y. Nishida, "A Conservative Loss Recovery Algorithm
Based on Selective Acknowledgment (SACK) for TCP", Based on Selective Acknowledgment (SACK) for TCP", RFC
RFC 6675, August 2012. 6675, August 2012,
<http://www.rfc-editor.org/info/rfc6675>.
[RFC6691] Borman, D., "TCP Options and Maximum Segment Size (MSS)", [RFC6691] Borman, D., "TCP Options and Maximum Segment Size (MSS)",
RFC 6691, July 2012. RFC 6691, July 2012,
<http://www.rfc-editor.org/info/rfc6691>.
[RFC6824] Ford, A., Raiciu, C., Handley, M., and O. Bonaventure, [RFC6824] Ford, A., Raiciu, C., Handley, M., and O. Bonaventure,
"TCP Extensions for Multipath Operation with Multiple "TCP Extensions for Multipath Operation with Multiple
Addresses", RFC 6824, January 2013. Addresses", RFC 6824, January 2013,
<http://www.rfc-editor.org/info/rfc6824>.
[RFC6846] Pelletier, G., Sandlund, K., Jonsson, L-E., and M. West, [RFC6846] Pelletier, G., Sandlund, K., Jonsson, L-E., and M. West,
"RObust Header Compression (ROHC): A Profile for TCP/IP "RObust Header Compression (ROHC): A Profile for TCP/IP
(ROHC-TCP)", RFC 6846, January 2013. (ROHC-TCP)", RFC 6846, January 2013,
<http://www.rfc-editor.org/info/rfc6846>.
[RFC6897] Scharf, M. and A. Ford, "Multipath TCP (MPTCP) Application [RFC6897] Scharf, M. and A. Ford, "Multipath TCP (MPTCP) Application
Interface Considerations", RFC 6897, March 2013. Interface Considerations", RFC 6897, March 2013,
<http://www.rfc-editor.org/info/rfc6897>.
[RFC6928] Chu, J., Dukkipati, N., Cheng, Y., and M. Mathis, [RFC6928] Chu, J., Dukkipati, N., Cheng, Y., and M. Mathis,
"Increasing TCP's Initial Window", RFC 6928, April 2013. "Increasing TCP's Initial Window", RFC 6928, April 2013,
<http://www.rfc-editor.org/info/rfc6928>.
[RFC6937] Mathis, M., Dukkipati, N., and Y. Cheng, "Proportional [RFC6937] Mathis, M., Dukkipati, N., and Y. Cheng, "Proportional
Rate Reduction for TCP", RFC 6937, May 2013. Rate Reduction for TCP", RFC 6937, May 2013,
<http://www.rfc-editor.org/info/rfc6937>.
[RFC6994] Touch, J., "Shared Use of Experimental TCP Options", [RFC6994] Touch, J., "Shared Use of Experimental TCP Options", RFC
RFC 6994, August 2013. 6994, August 2013,
<http://www.rfc-editor.org/info/rfc6994>.
12.2. Informative References [RFC7323] Borman, D., Braden, B., Jacobson, V., and R.
Scheffenegger, "TCP Extensions for High Performance", RFC
7323, September 2014,
<http://www.rfc-editor.org/info/rfc7323>.
[CK73] Cerf, V. and R. Kahn, "Towards Protocols for Internetwork [RFC7413] Cheng, Y., Chu, J., Radhakrishnan, S., and A. Jain, "TCP
Communication", IFIP/TC6.1, NIC 18764, INWG 39, Fast Open", RFC 7413, December 2014,
September 1973. <http://www.rfc-editor.org/info/rfc7413>.
[Errata] "RFC Editor - RFC Errata", 10.2. Informative References
<http://www.rfc-editor.org/errata.php>.
[I-D.leith-tcp-htcp] [CK73] Cerf, V. and R. Kahn, "Towards Protocols for Internetwork
Leith, D., "H-TCP: TCP Congestion Control for High Communication", IFIP/TC6.1, NIC 18764, INWG 39, September
Bandwidth-Delay Product Paths", draft-leith-tcp-htcp-06 1973.
(work in progress), April 2008.
[I-D.rhee-tcpm-cubic] [CTCP] Sridharan, M., Tan, K., Bansal, D., and D. Thaler,
Rhee, I., Xu, L., and S. Ha, "CUBIC for Fast Long-Distance "Compound TCP: A New TCP Congestion Control for High-Speed
Networks", draft-rhee-tcpm-cubic-02 (work in progress), and Long Distance Networks", Work in Progress,
draft-sridharan-tcpm-ctcp-02, November 2008.
[CUBIC] Rhee, I., Xu, L., and S. Ha, "CUBIC for Fast Long-Distance
Networks", Work in Progress, draft-rhee-tcpm-cubic-02,
August 2008. August 2008.
[I-D.sridharan-tcpm-ctcp] [Errata] RFC Editor, "RFC Errata",
Sridharan, M., Tan, K., Bansal, D., and D. Thaler, <http://www.rfc-editor.org/errata.php>.
"Compound TCP: A New TCP Congestion Control for High-Speed
and Long Distance Networks", draft-sridharan-tcpm-ctcp-02 [HTCP] Leith, D., "H-TCP: TCP Congestion Control for High
(work in progress), November 2008. Bandwidth-Delay Product Paths", Work in Progress,
draft-leith-tcp-htcp-06, April 2008.
[JK92] Jacobson, V. and M. Karels, "Congestion Avoidance and [JK92] Jacobson, V. and M. Karels, "Congestion Avoidance and
Control", This paper is a revised version of [Jac88], that Control", November 1992,
includes an additional appendix. This paper has not been <ftp://ftp.ee.lbl.gov/papers/congavoid.ps.Z>.
traditionally published, but is currently available at
ftp://ftp.ee.lbl.gov/papers/congavoid.ps.Z. 1992.
[Jac88] Jacobson, V., "Congestion Avoidance and Control", ACM [Jac88] Jacobson, V., "Congestion Avoidance and Control", ACM
SIGCOMM 1988 Proceedings, in ACM Computer Communication SIGCOMM 1988 Proceedings, in ACM Computer Communication
Review, 18 (4), pp. 314-329, August 1988. Review, 18 (4), pp. 314-329, August 1988.
[Jacobson] Jacobson, V., "TCP-IP Mailing List", Article 167 of
comp.protocols.tcp-ip, March 1988,
<ftp://ftp.ee.lbl.gov/email/vanj.88mar10.txt>.
[KP87] Karn, P. and C. Partridge, "Round Trip Time Estimation", [KP87] Karn, P. and C. Partridge, "Round Trip Time Estimation",
ACM SIGCOMM 1987 Proceedings, in ACM Computer ACM SIGCOMM 1987 Proceedings, in ACM Computer
Communication Review, 17 (5), pp. 2-7, August 1987. Communication Review, 17 (5), pp. 2-7, August 1987.
[MAF04] Medina, A., Allman, M., and S. Floyd, "Measuring the [MAF04] Medina, A., Allman, M., and S. Floyd, "Measuring the
Evolution of Transport Protocols in the Internet", ACM Evolution of Transport Protocols in the Internet", ACM
Computer Communication Review, 35 (2), April 2005. Computer Communication Review, 35 (2), April 2005.
[MM96] Mathis, M. and J. Mahdavi, "Forward Acknowledgement: [MM96] Mathis, M. and J. Mahdavi, "Forward Acknowledgement:
Refining TCP Congestion Control", ACM SIGCOMM 1996 Refining TCP Congestion Control", ACM SIGCOMM 1996
Proceedings, in ACM Computer Communication Review 26 (4), Proceedings, in ACM Computer Communication Review 26 (4),
pp. 281-292, October 1996. pp. 281-292, October 1996.
[RFC1016] Prue, W. and J. Postel, "Something a host could do with [RFC1016] Prue, W. and J. Postel, "Something a host could do with
source quench: The Source Quench Introduced Delay source quench: The Source Quench Introduced Delay
(SQuID)", RFC 1016, July 1987. (SQuID)", RFC 1016, July 1987,
<http://www.rfc-editor.org/info/rfc1016>.
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996. 3", BCP 9, RFC 2026, October 1996,
<http://www.rfc-editor.org/info/rfc2026>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black,
"Definition of the Differentiated Services Field (DS "Definition of the Differentiated Services Field (DS
Field) in the IPv4 and IPv6 Headers", RFC 2474, Field) in the IPv4 and IPv6 Headers", RFC 2474, December
December 1998. 1998, <http://www.rfc-editor.org/info/rfc2474>.
[RFC3758] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P. [RFC3758] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P.
Conrad, "Stream Control Transmission Protocol (SCTP) Conrad, "Stream Control Transmission Protocol (SCTP)
Partial Reliability Extension", RFC 3758, May 2004. Partial Reliability Extension", RFC 3758, May 2004,
<http://www.rfc-editor.org/info/rfc3758>.
[RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram [RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram
Congestion Control Protocol (DCCP)", RFC 4340, March 2006. Congestion Control Protocol (DCCP)", RFC 4340, March 2006,
<http://www.rfc-editor.org/info/rfc4340>.
[RFC4341] Floyd, S. and E. Kohler, "Profile for Datagram Congestion [RFC4341] Floyd, S. and E. Kohler, "Profile for Datagram Congestion
Control Protocol (DCCP) Congestion Control ID 2: TCP-like Control Protocol (DCCP) Congestion Control ID 2: TCP-like
Congestion Control", RFC 4341, March 2006. Congestion Control", RFC 4341, March 2006,
<http://www.rfc-editor.org/info/rfc4341>.
[RFC6115] Li, T., "Recommendation for a Routing Architecture", [RFC6115] Li, T., "Recommendation for a Routing Architecture", RFC
RFC 6115, February 2011. 6115, February 2011,
<http://www.rfc-editor.org/info/rfc6115>.
[SCWA99] Savage, S., Cardwell, N., Wetherall, D., and T. Anderson, [SCWA99] Savage, S., Cardwell, N., Wetherall, D., and T. Anderson,
"TCP Congestion Control with a Misbehaving Receiver", ACM "TCP Congestion Control with a Misbehaving Receiver", ACM
Computer Communication Review, 29 (5), pp. 71-78, Computer Communication Review, 29 (5), pp. 71-78, October
October 1999. 1999.
Acknowledgments
This document grew out of a discussion on the end2end-interest
mailing list, the public list of the End-to-End Research Group of the
IRTF, and continued development under the IETF's TCP Maintenance and
Minor Extensions (TCPM) working group. We thank Mark Allman, Yuchung
Cheng, Ted Faber, Gorry Fairhurst, Sally Floyd, Janardhan Iyengar,
Reiner Ludwig, Pekka Savola, and Joe Touch for their contributions,
in particular. Keith McCloghrie provided some useful notes and
clarification on the various MIB-related RFCs.
Authors' Addresses Authors' Addresses
Martin Duke Martin Duke
F5 Networks F5 Networks
401 Elliott Ave W 401 Elliott Ave W
Seattle, WA 98119 Seattle, WA 98119
United States
Phone: 206-272-7537 Phone: 206-272-7537
Email: m.duke@f5.com EMail: m.duke@f5.com
Robert Braden Robert Braden
USC Information Sciences Institute USC Information Sciences Institute
Marina del Rey, CA 90292-6695 Marina del Rey, CA 90292-6695
United States
Phone: 310-448-9173 Phone: 310-448-9173
Email: braden@isi.edu EMail: braden@isi.edu
Wesley M. Eddy Wesley M. Eddy
MTI Systems MTI Systems
MS 500-ASRC; 21000 Brookpark Rd 18013 Cleveland Parkway
Suite 170
Cleveland, OH 44135 Cleveland, OH 44135
United States
Phone: 216-433-6682 Phone: 216-433-6682
Email: wes@mti-systems.com EMail: wes@mti-systems.com
Ethan Blanton Ethan Blanton
Interrupt Sciences
Email: elb@psg.com EMail: elb@interruptsciences.com
Alexander Zimmermann Alexander Zimmermann
NetApp, Inc. NetApp, Inc.
Sonnenallee 1 Sonnenallee 1
Kirchheim 85551 Kirchheim 85551
Germany Germany
Phone: +49 89 900594712 Phone: +49 89 900594712
Email: alexander.zimmermann@netapp.com EMail: alexander.zimmermann@netapp.com
 End of changes. 406 change blocks. 
912 lines changed or deleted 1027 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/