draft-ietf-tcpm-tcp-rfc4614bis-04.txt   draft-ietf-tcpm-tcp-rfc4614bis-05.txt 
TCP Maintenance and Minor Extensions M. Duke TCP Maintenance and Minor Extensions M. Duke
(TCPM) WG F5 (TCPM) WG F5
Internet-Draft R. Braden Internet-Draft R. Braden
Obsoletes: 4614 (if approved) ISI Obsoletes: 4614 (if approved) ISI
Intended status: Informational W. Eddy Intended status: Informational W. Eddy
Expires: October 11, 2014 MTI Systems Expires: October 30, 2014 MTI Systems
E. Blanton E. Blanton
A. Zimmermann A. Zimmermann
NetApp, Inc. NetApp, Inc.
April 9, 2014 April 28, 2014
A Roadmap for Transmission Control Protocol (TCP) Specification A Roadmap for Transmission Control Protocol (TCP) Specification
Documents Documents
draft-ietf-tcpm-tcp-rfc4614bis-04 draft-ietf-tcpm-tcp-rfc4614bis-05
Abstract Abstract
This document contains a "roadmap" to the Requests for Comments (RFC) This document contains a "roadmap" to the Requests 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.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 11, 2014. This Internet-Draft will expire on October 30, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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
skipping to change at page 9, line 41 skipping to change at page 9, line 41
This document [I-D.ietf-tcpm-1323bis] defines TCP extensions for This document [I-D.ietf-tcpm-1323bis] defines TCP extensions for
window scaling, timestamps, and protection against wrapped window scaling, timestamps, and protection against wrapped
sequence numbers, for efficient and safe operation over paths with sequence numbers, for efficient and safe operation over paths with
large bandwidth-delay products. These extensions are commonly large bandwidth-delay products. These extensions are commonly
found in currently used systems. The predecessor of this found in currently used systems. The predecessor of this
document, RFC 1323, was published in 1992, and is deployed in most document, RFC 1323, was published in 1992, and is deployed in most
TCP implementations. This document includes fixes and TCP implementations. This document includes fixes and
clarifications based on the gained deployment experience. One clarifications based on the gained deployment experience. One
specific issued addressed in this specification is a specific issued addressed in this specification is a
recommendation how to modify the algorithm for estimating the mean recommendation how to modify the algorithm for estimating the mean
RTT when timestamps are used. RFC 1072, RFC 1185, and RFC RFC RTT when timestamps are used. RFC 1072, RFC 1185, and RFC 1323
1323 are the conceptual precursors of RFC XXXX. are the conceptual precursors of RFC XXXX.
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
skipping to change at page 26, line 48 skipping to change at page 26, line 48
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 [RFC0675] is a very early precursor of the
fundamental RFC 793 (see Section 2), which already contained the fundamental RFC 793 (see Section 2), which already contained the
three-way handshake in its final form and the concept of sliding three-way handshake in its final form and the concept of sliding
windows for reliable data transmission. Apart from that the windows for reliable data transmission. Apart from that the
segment layout is totally different and the specified API differs segment layout is totally different and the specified API differs
from the latter RFC 793 (see Section 2). from the latter RFC 793 (see Section 2).
RFC 761 H: "DoD standard Transmission Control Protocol" (Januar RFC 761 U: "DoD standard Transmission Control Protocol" (Januar
1980) 1980)
This document [RFC0761] is the immediate precursor of RFC 793 (see This document [RFC0761] is the immediate precursor of RFC 793 (see
Section 2). The header format, the connection establishment Section 2). The header format, the connection establishment
including the different connection states, and the overall API including the different connection states, and the overall API
correspond mostly to the final Standard RFC 793 (see Section 2). correspond mostly to the final Standard RFC 793 (see Section 2).
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 [RFC0813] contains an early discussion of Silly
skipping to change at page 40, line 37 skipping to change at page 40, line 37
particular. Keith McCloghrie provided some useful notes and particular. Keith McCloghrie provided some useful notes and
clarification on the various MIB-related RFCs. clarification on the various MIB-related RFCs.
12. References 12. References
12.1. Normative References 12.1. Normative References
[I-D.ietf-tcpm-1323bis] [I-D.ietf-tcpm-1323bis]
Borman, D., Braden, R., Jacobson, V., and R. Borman, D., Braden, R., Jacobson, V., and R.
Scheffenegger, "TCP Extensions for High Performance", Scheffenegger, "TCP Extensions for High Performance",
draft-ietf-tcpm-1323bis-17 (work in progress), draft-ietf-tcpm-1323bis-21 (work in progress), April 2014.
November 2013.
[I-D.ietf-tcpm-fastopen] [I-D.ietf-tcpm-fastopen]
Cheng, Y., Chu, J., Radhakrishnan, S., and A. Jain, "TCP Cheng, Y., Chu, J., Radhakrishnan, S., and A. Jain, "TCP
Fast Open", draft-ietf-tcpm-fastopen-05 (work in Fast Open", draft-ietf-tcpm-fastopen-08 (work in
progress), October 2013. progress), March 2014.
[RFC0675] Cerf, V., Dalal, Y., and C. Sunshine, "Specification of [RFC0675] Cerf, V., Dalal, Y., and C. Sunshine, "Specification of
Internet Transmission Control Program", RFC 675, Internet Transmission Control Program", RFC 675,
December 1974. December 1974.
[RFC0700] Mader, E., Plummer, W., and R. Tomlinson, "Protocol [RFC0700] Mader, E., Plummer, W., and R. Tomlinson, "Protocol
experiment", RFC 700, August 1974. experiment", RFC 700, August 1974.
[RFC0721] Garlick, L., "Out-of-Band Control Signals in a Host-to- [RFC0721] Garlick, L., "Out-of-Band Control Signals in a Host-to-
Host Protocol", RFC 721, September 1976. Host Protocol", RFC 721, September 1976.
 End of changes. 10 change blocks. 
12 lines changed or deleted 12 lines changed or added

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