draft-ietf-tcpm-tcp-edo-03.txt   draft-ietf-tcpm-tcp-edo-04.txt 
TCPM WG J. Touch TCPM WG J. Touch
Internet Draft USC/ISI Internet Draft USC/ISI
Updates: 793 Wes Eddy Updates: 793 Wes Eddy
Intended status: Standards Track MTI Systems Intended status: Standards Track MTI Systems
Expires: October 2015 April 15, 2015 Expires: May 2016 November 2, 2015
TCP Extended Data Offset Option TCP Extended Data Offset Option
draft-ietf-tcpm-tcp-edo-03.txt draft-ietf-tcpm-tcp-edo-04.txt
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), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on October 15, 2015. This Internet-Draft will expire on April 2, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 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
skipping to change at page 11, line 13 skipping to change at page 11, line 13
would require 30 bytes without SACK, thus limiting the SACK option would require 30 bytes without SACK, thus limiting the SACK option
to one block unless EDO is also supported on at least non-SYN to one block unless EDO is also supported on at least non-SYN
segments. segments.
The full combination of the above options (47 bytes for TS, WS, MSS, The full combination of the above options (47 bytes for TS, WS, MSS,
SACK, TCP-AO, and MPTCP) does not fit in the existing SYN option SACK, TCP-AO, and MPTCP) does not fit in the existing SYN option
space and (as noted) that space cannot be extended within a single space and (as noted) that space cannot be extended within a single
SYN segment. There has been a proposal to change TS to a 2 byte "TS SYN segment. There has been a proposal to change TS to a 2 byte "TS
permitted" signal in the initial SYN, provided it can be safely permitted" signal in the initial SYN, provided it can be safely
enabled during the connection later or might be avoided completely enabled during the connection later or might be avoided completely
[Ni14]. Even using "TS-permitted", the total space is still too [Ni15]. Even using "TS-permitted", the total space is still too
large to support in the initial SYN without SYN option space large to support in the initial SYN without SYN option space
extension [Bo14][Br14][To15]. extension [Bo14][Br14][To15].
The EDO Extension option has negligible impact on other headers, The EDO Extension option has negligible impact on other headers,
because it can either come first or just after security information, because it can either come first or just after security information,
and in either case the additional 4 or 6 bytes are easily and in either case the additional 4 or 6 bytes are easily
accommodated within the TCP Data Offset length. Once the EDO option accommodated within the TCP Data Offset length. Once the EDO option
is processed, the entirety of the remainder of the TCP segment is is processed, the entirety of the remainder of the TCP segment is
available for any remaining options. available for any remaining options.
skipping to change at page 21, line 20 skipping to change at page 21, line 20
progress), July 2008. progress), July 2008.
[Ho11] Honda, M., Nishida, Y., Raiciu, C., Greenhalgh, A., [Ho11] Honda, M., Nishida, Y., Raiciu, C., Greenhalgh, A.,
Handley, M., and H. Tokuda, "Is it still possible to Handley, M., and H. Tokuda, "Is it still possible to
extend TCP", Proc. ACM Sigcomm Internet Measurement extend TCP", Proc. ACM Sigcomm Internet Measurement
Conference (IMC), 2011, pp. 181-194. Conference (IMC), 2011, pp. 181-194.
[Ko04] Kohler, E., "Extended Option Space for TCP", draft-kohler- [Ko04] Kohler, E., "Extended Option Space for TCP", draft-kohler-
tcpm-extopt-00 (work in progress), September 2004. tcpm-extopt-00 (work in progress), September 2004.
[Ni14] Nishida, Y., "A-PAWS: Alternative Approach for PAWS", [Ni15] Nishida, Y., "A-PAWS: Alternative Approach for PAWS",
draft-nishida-tcpm-apaws-01 (work in progress), June 2014. draft-nishida-tcpm-apaws-02 (work in progress), Oct. 2015.
[Ra12] Ramaiah, A., "TCP option space extension", draft-ananth- [Ra12] Ramaiah, A., "TCP option space extension", draft-ananth-
tcpm-tcpoptext-00 (work in progress), March 2012. tcpm-tcpoptext-00 (work in progress), March 2012.
[RFC792] Postel, J., "Internet Control Message Protocol", RFC 792, [RFC792] Postel, J., "Internet Control Message Protocol", RFC 792,
September 1981. September 1981.
[RFC1812] Baker, F. (Ed.), "Requirements for IP Version 4 Routers," [RFC1812] Baker, F. (Ed.), "Requirements for IP Version 4 Routers,"
RFC 1812, June 1995. RFC 1812, June 1995.
 End of changes. 5 change blocks. 
6 lines changed or deleted 6 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/