[e2e] TCP slow start and maximum segment size

[Bob Braden]

  *> From end2end-interest-admin at postel.org  Wed Jun 25 11:42:14 2003
  *> From: David Borman <dab at BSDI.COM>
  *> To: end2end-interest at postel.org, sgshakkottai at yahoo.com,
  *>    valentin at tehutinetworks.com
  *> Subject: RE: [e2e] TCP slow start and maximum segment size
  *> X-AntiVirus: scanned by AMaViS 0.2.1
  *> X-BeenThere: end2end-interest at postel.org
  *> X-Mailman-Version: 2.0.1
  *> List-Help: <mailto:end2end-interest-request at postel.org?subject=help>
  *> List-Archive: <http://www.postel.org/pipermail/end2end-interest/>
  *> Date: Wed, 25 Jun 2003 11:11:14 -0500 (CDT)
  *> X-AntiVirus: scanned by AMaViS 0.2.1
  *> 
  *> Actually, you subtract the fixed IP and TCP header sizes from the
  *> MTU to get the TCP MSS value.  If there are any IP or TCP options,
  *> then the sender will reduce his effective MSS value by the length
  *> of the IP and TCP options.
  *> 

As explained in RFC 1122, nearly 15 years ago...

Bob Braden