Re: sack delay parameter

From: Kacheong Poon <kacheong.poon@sun.com>
Date: Wed Feb 16 2005 - 15:53:00 EST

('binary' encoding is not supported, stored as-is) ('binary' encoding is not supported, stored as-is) David Lehmann wrote:

> In RFC2960, section 6.2, the sack delay is specified as 200ms
> and can be configured up to 500ms. Can we add a sack delay
> parameter to the API, maybe in struct sctp_assocparams?

If we add it, I think it should probably be in
sctp_paddrparams. And given the recent discussion
on using spp_hbinterval, I guess we can change the
structure a little bit to accomodate both. This
also applies to enforcing a fix MTU (this means
that the DF bit will not be set in v4 if the MTU
is bigger than the PMTU).

-- 
						K. Poon.
						kacheong.poon@sun.com

Received on Wed Feb 16 15:55:30 2005