[Lksctp-developers] About the sctp_opt_info

[Fan, A. <ard...@in...>]

Hi Jon

Since "sctp_opt_info needs added to the user headers, or we added to the
library if we can't do it like the I-D proposes.", I read the source for it.
Here are some points/questions:

The current sctp source has defined all option name macros and option
argument structures in include\net\sctp\sctp_user.h, but no reference to
them at all.
According to the API I-D document, sctp_opt_info is a supplement for
read-only getsockopt(), if the implementations DO support a read/write
getsockopt interface, sctp_opt_info() is just a simple macro wrapper of
getsockopt(). 
But, firstly there is also setsockopt() which can support write operation
for options, why sctp_opt_info is also needed? Or is it just an wrapper of
both setsockopt() and getsockopt()?
Secondly, current getsockopt and setsockopt do nothing about the option name
listed in I-D doc, such as SCTP_RTOINFO, SCTP_ASSOCINFO,
SCTP_SET_PRIMARY_ADDR, ... I want to know will these two interface functions
implement them in future?
You mentioned that whether implement the sctp_opt_info in kernel space or in
user library. Is there any existing library for sctp now? I think both ways
are open, what standard should be used to make decision?

Thanks
Regards/Ardelle