draft-ietf-tcpm-tcp-rfc4614bis-06.txt   draft-ietf-tcpm-tcp-rfc4614bis-07.txt 
skipping to change at page 1, line 17 skipping to change at page 1, line 17
Intended status: Informational W. Eddy Intended status: Informational W. Eddy
Expires: January 4, 2015 MTI Systems Expires: January 4, 2015 MTI Systems
E. Blanton E. Blanton
A. Zimmermann A. Zimmermann
NetApp, Inc. NetApp, Inc.
July 3, 2014 July 3, 2014
A Roadmap for Transmission Control Protocol (TCP) Specification A Roadmap for Transmission Control Protocol (TCP) Specification
Documents Documents
draft-ietf-tcpm-tcp-rfc4614bis-06 draft-ietf-tcpm-tcp-rfc4614bis-07
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.
skipping to change at page 16, line 49 skipping to change at page 16, line 49
generation of TCP Initial Sequence Numbers (ISNs), such that the generation of TCP Initial Sequence Numbers (ISNs), such that the
chances of an off-path attacker guessing the sequence numbers in chances of an off-path attacker guessing the sequence numbers in
use by a target connection are reduced. This document revises use by a target connection are reduced. This document revises
(and formally obsoletes) RFC 1948, and takes the ISN generation (and formally obsoletes) RFC 1948, and takes the ISN generation
algorithm originally proposed in that document to Standards Track, algorithm originally proposed in that document to Standards Track,
formally updating RFC 793 (see Section 2). formally updating RFC 793 (see Section 2).
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 already be proposed standard proposed standards in the future or are proposed standard (or
(or informational), but considered as experimental due to lack of informational), but can considered as 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.
At this point is worth mentioning that if the experimental RFC is a At this point is worth mentioning that if the experimental RFC is a
proposal for a new protocol capability or service, i.e., it requires proposal for a new protocol capability or service, i.e., it requires
a new TCP option code point, the implementation and experimentation a new TCP option code point, the implementation and experimentation
should follows [RFC6994] (see Section 5), which describes how the should follows [RFC6994] (see Section 5), which describes how the
experimental TCP option code points can concurrently support multiple experimental TCP option code points can concurrently support multiple
TCP extensions. TCP extensions.
 End of changes. 2 change blocks. 
3 lines changed or deleted 3 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/