Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!ucbvax!MATHOM.CISCO.COM!BILLW
From: BILLW@MATHOM.CISCO.COM (William "Chops" Westfield)
Newsgroups: comp.protocols.tcp-ip
Subject: TCP options...
Message-ID: <12642163454.13.BILLW@mathom.cisco.com>
Date: 1 Dec 90 00:37:57 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 11

TCP options are apparently not included in the sequence space - At least,
all the implementations I see have the first datagram after the syn/mss
packet with a sequence number 1 greater than the syn (which covers the
syn, but not the 4 bytes of tcp options that make up the mss option.)

HR rfc requires that TCPs accept options in any packet - does this actually
mean that in order to ensure reliable delivery of an option, it has to be
sent in a packet that also contains data?  Sure seems that way...

BillW
-------


Brought to you by Super Global Mega Corp .com