%% You should probably cite draft-briscoe-tcpm-inner-space-01 instead of this revision. @techreport{briscoe-tcpm-inner-space-00, number = {draft-briscoe-tcpm-inner-space-00}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-briscoe-tcpm-inner-space/00/}, author = {Bob Briscoe}, title = {{Inner Space for TCP Options}}, pagetotal = 45, year = 2014, month = oct, day = 19, abstract = {This document describes an experimental method to extend the limited space for control options in every segment of a TCP connection. It can use a dual handshake so that, from the very first SYN segment, extra option space can immediately start to be used optimistically. At the same time the dual handshake prevents a legacy server from getting confused and sending the control options to the application as user-data. The dual handshake is only one strategy - a single handshake will usually suffice once deployment has got started. The protocol is designed to traverse most known middleboxes including connection splitters, because it sits wholly within the TCP Data. It also provides reliable ordered delivery for control options. Therefore, it should allow new TCP options to be introduced i) with minimal middlebox traversal problems; ii) avoiding incremental deployment problems with pre-existing servers; iii) without an extra round of handshaking delay iv) without having to provide its own loss recovery and ordering mechanism and v) without arbitrary limits on available space.}, }