Re: SCTP API section 7.1.13

From: David Lehmann <lehmann@ulticom.com>
Date: Tue Feb 15 2005 - 09:25:53 EST

('binary' encoding is not supported, stored as-is) ('binary' encoding is not supported, stored as-is) Ryan W Bickhart wrote:
> I believe what you would do is first get all the current peer address
> parameter values which are returned in the sctp_paddrparams struct,
> change the fields that you want to new values, and then do a set,
> passing the struct back to SCTP. Anything you didn't modify would remain
> what it was before. Maybe there is a more direct way but that would
> definitely work.

How do you "get all the current peer address parameter values" without
setting it? The draft says that you "should" use sctp_opt_info which
'sets' and 'gets'. Does this mean that you can use getsockopt() as well?
If so, I did not see that statement in the draft.

Even if this is the case, it seems that this API is
inconsistent with the other structures where zero means
"don't change". Also, it is very inconvenient to get a value just
so we can then set it to the same value.

IMHO, zero should mean "don't change". UINT32_MAX could mean
disable heartbeats. (Or ~49 days, which is affectively
disabled.) How about adding a boolean parameter "spp_send_hb"?
zero would mean don't send a HB; nonzero would mean send it.
That would leave spp_hbinterval to behave like the other parameters.

-- 
David Lehmann                          Ulticom, Inc.
AOL/Yahoo IM: davidULCM                1020 Briggs Road
1-856-787-2729                         Mt. Laurel, NJ 08054   USA

Received on Tue Feb 15 09:50:49 2005