IETF-92 Proceedings
Introduction | Area, Working Goup & BoF Reports | Plenaries | Training | Internet Research Task Force
TCP Maintenance and Minor Extensions (tcpm) (WG)
Additional information is available at tools.ietf.org/wg/tcpm
Chair(s):
Transport Area Area Director(s):
Assigned Area Director
|
Recordings:
Meeting Slides:
Blue Sheets:
Internet-Drafts:
Request for Comments:
- The NewReno Modification to TCP's Fast Recovery Algorithm (RFC 6582) (35413 bytes)
obsoletes rfc3782
- A Conservative Loss Recovery Algorithm Based on Selective Acknowledgment (SACK) for TCP (RFC 6675) (34484 bytes)
obsoletes rfc3517
- Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP and the Stream Control Transmission Protocol (SCTP) (RFC 4138) (55538 bytes)
updated by RFC 5682
- A Roadmap for Transmission Control Protocol (TCP) Specification Documents (RFC 4614) (75645 bytes)
obsoleted by RFC 7414
updated by RFC 6247
- Improving the Robustness of TCP to Non-Congestion Events (RFC 4653) (42268 bytes)
- Defending TCP Against Spoofing Attacks (RFC 4953) (72756 bytes)
- TCP SYN Flooding Attacks and Common Mitigations (RFC 4987) (48753 bytes)
- TCP's Reaction to Soft Errors (RFC 5461) (31749 bytes)
- TCP User Timeout Option (RFC 5482) (33568 bytes)
- Adding Explicit Congestion Notification (ECN) Capability to TCP's SYN/ACK Packets (RFC 5562) (77110 bytes)
- TCP Congestion Control (RFC 5681) (44339 bytes)
obsoletes rfc2581
- Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP (RFC 5682) (47337 bytes)
updates RFC4138
- Early Retransmit for TCP and Stream Control Transmission Protocol (SCTP) (RFC 5827) (35383 bytes)
- ICMP Attacks against TCP (RFC 5927) (87744 bytes)
- The TCP Authentication Option (RFC 5925) (106174 bytes)
obsoletes rfc2385
- Cryptographic Algorithms for the TCP Authentication Option (TCP-AO) (RFC 5926) (31010 bytes)
- Improving TCP's Robustness to Blind In-Window Attacks (RFC 5961) (44717 bytes)
- Making TCP More Robust to Long Connectivity Disruptions (TCP-LCD) (RFC 6069) (59600 bytes)
- Reducing the TIME-WAIT State Using TCP Timestamps (RFC 6191) (22953 bytes)
- Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status (RFC 6247) (6414 bytes)
obsoletes rfc1072 obsoletes rfc1106 obsoletes rfc1110 obsoletes rfc1145 obsoletes rfc1146 obsoletes rfc1379 obsoletes rfc1644 obsoletes rfc1693 updates RFC4614
- Computing TCP's Retransmission Timer (RFC 6298) (22454 bytes)
obsoletes rfc2988 updates RFC1122
- TCP Sender Clarification for Persist Condition (RFC 6429) (14280 bytes)
- Defending against Sequence Number Attacks (RFC 6528) (26917 bytes)
obsoletes rfc1948 updates RFC793
- Increasing TCP's Initial Window (RFC 6928) (56523 bytes)
- Proportional Rate Reduction for TCP (RFC 6937) (39437 bytes)
- TCP Options and Maximum Segment Size (MSS) (RFC 6691) (16707 bytes)
updates RFC2385,RFC879
- Shared Use of Experimental TCP Options (RFC 6994) (25577 bytes)
- TCP Extensions for High Performance (RFC 7323) (106013 bytes)
obsoletes rfc1323
- TCP Fast Open (RFC 7413) (59945 bytes)
- A Roadmap for Transmission Control Protocol (TCP) Specification Documents (RFC 7414) (130622 bytes)
obsoletes rfc4614
- On the Implementation of the TCP Urgent Mechanism (RFC 6093) (25921 bytes)
updates RFC793,RFC1011,RFC1122
Charter (as of 2015-04-10):
TCP is currently the Internet's predominant transport protocol. TCPM
is the working group within the IETF that handles small TCP changes,
i.e., minor extensions to TCP algorithms and protocol mechanisms.
The TCPM WG serves several purposes:
* The WG mostly focuses on maintenance issues (e.g., bug fixes) and
modest changes to the protocol, algorithms, and interfaces that
maintain TCP's utility.
* The WG is a venue for moving current TCP specifications along the
standards track (as community energy is available for such efforts).
* The focus of the working group is TCP. In cases where small
changes are directly applicable to other transports (e.g., SCTP or
DCCP), the mappings to other transports may be specified alongside
that for TCP, but other significant additions and changes to other
transports are not in scope.
TCPM also provides a venue for standardization of incremental
enhancements of TCP's standard congestion control. In addition,
TCPM may document alternative TCP congestion control algorithms
that are known to be widely deployed, and that are considered
safe for large-scale deployment in the Internet. Changes of algorithms
may require additional review by the IRTF Congestion Control
Research Group (ICCRG). Fundamental changes to TCP or its congestion
control algorithms (e.g., departure from loss-based congestion
control) will be handled by other working groups or will require
rechartering.
TCP's congestion control algorithms are the model followed by
alternate transports (e.g., SCTP or DCCP), which are standardized in
other working groups, such as the Transport Area WG (tsvwg). In the
past, the IETF has worked on several documents about algorithms that
are specified for multiple protocols (e.g., TCP and SCTP) in the
same document. Which WG shepherds such documents will be determined
on a case-by-case basis. In any case, the TCPM WG will remain in
close contact with other relevant WGs working on these protocols to
ensure openness and stringent review from all angles.
New TCPM milestones that fall within the scope specified within the
charter can be added after consensus on acceptance in the working
group and approval by the responsible Area Director.