Re: [tcpm] WGLC for MSS document

[Joe Touch <[e-mail]>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, Lloyd,

[e-mail] wrote:
> Can't TCP MSS also vary across multipath environments? 

Yes, but that's discovered by PMTUD. I think this doc is focusing more
on what the interface says is available - which ROHC might have an
effect on.

> Strikes me
> that these are more common than header compression - which should
> be advertising conservative minimum MTUs for their link interfaces.

I'm not sure what's more common, but they're separate effects AFAICT.

Joe

> -----Original Message-----
> From: [e-mail] on behalf of Joe Touch
> Sent: Thu 2009-08-20 19:28
> To: Eddy, Wesley M. (GRC-MS00)[Verizon]
> Cc: [e-mail]
> Subject: Re: [tcpm] WGLC for MSS document
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi, all,
> 
> Eddy, Wesley M. (GRC-MS00)[Verizon] wrote:
>> This note starts a 2-week Working Group Last Call on the TCPM document:
>> http://tools.ietf.org/html/draft-ietf-tcpm-tcpmss-02
>> Please send any comments to the TCPM list.  The WGLC will last until
>> September 1.
> 
> I'd like to suggest the following for this doc:
> 
> MSSs can sometimes vary, as when used with variable compression, e.g.,
> ROHC. The ROHC doc missed an opportunity to address the interaction of
> variable MSS with TCP, and this might be a good place to include a
> sentence or two on it, e.g. (IMO):
> 
> - ---
> 
> MSSs can sometimes vary, as when used with variable compression, e.g.,
> ROHC [RFC5255]. It is tempting for TCP to want to advertise the largest
> possible MSS, to support the most efficient use of compressed payloads.
> Unfortunately, some compression schemes occasionally need to transmit
> full headers (and thus smaller payloads) to resynchronize state at their
> endpoint compressor/decompressors. If the largest MSS is advertised, TCP
> retransmission may interfere with compressor resynchonization.
> 
> As a result, when effective MSS varies, TCP SHOULD compute its
> advertised MSS based on the smallest effective MSS.
> 
> - ---
> 
> Joe
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqNs5gACgkQE5f5cImnZrubugCeJ4Kb4SsRAun/ywcbJ4ZgRL7o
uCUAoKu0j0eIMLSwj7GAqZH/184RSqoR
=7QTE
-----END PGP SIGNATURE-----