[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Question on TCP MSS with repsect to IPSEC

To: ipsec@TIS.COM, naganand@ftp.com
Subject: Re: Question on TCP MSS with repsect to IPSEC
From: touch@isi.edu
Date: Wed, 31 Jul 1996 11:33:24 -0700
Cc: solensky@ftp.com
MMDF-Warning: Parse error in original version of preceding line at neptune.TIS.COM
Posted-Date: Wed, 31 Jul 1996 11:33:24 -0700
Sender: ipsec-approval@neptune.tis.com

> When we adverstise MSS for TCP connections, am I right in saying that the
> MSS value should take into account the ESP and AH header and data.
> 
> For example if the MTU is 576, and the AH header+data is 24 bytes and ESP
> header +data 20 bytes (assuming 8 bytes padding), then the MSS I announce
> should be
> (576 - 40 - 24 - 20).
> 
> Thanks,
> 
> --Naganand
> ----------------------------------------------------------------
> naganand@ftp.com
> Tel #: (508)684-6743 (O)

Hmmm. The current BSD code uses the min of the MSS and 512,
to optimize alignments, e.g., with pages, socket buffers, etc.

Given that this leaves 492, a size of 256 seems small, but may
have some benefit.

Joe
----------------------------------------------------------------------
Joe Touch - touch@isi.edu		    http://www.isi.edu/~touch/
ISI / Project Leader, ATOMIC-2, LSAM       http://www.isi.edu/atomic2/
USC / Research Assistant Prof.                http://www.isi.edu/lsam/

Prev by Date: Re: Question on TCP MSS with repsect to IPSEC
Next by Date: PF_KEY Key Management API
Prev by thread: Re: Question on TCP MSS with repsect to IPSEC
Next by thread: Re: Question on TCP MSS with repsect to IPSEC
Index(es):
- Main
- Thread