Folks,
I just resubmitted a revised draft on the address
selection preference API incorporating comments and
suggestions we got from reviewers (thanks!) since -03
went out last year.
Until it shows up in the repository, you find it here:
Hello,
Some random comments:
The proposed API adds a new IPv6-level socket option
(IPV6_ADDRESS_PREFERENCES). IMHO, it ought to
also specify that this can also be used as a non-sticky option through
sendmsg() ancilliarry data, like other IPv6 options found in the
advanced IPv6 API.
It
Hello again,
For consistency with the current getaddrinfo and setsockopt usage, I
think the preference flags ought to be an int rather than an
uin32_t, and that resetting the socket option to system default should
be achieved by passing -1 as the socket option value, rather than
using
Su,
On Oct 19, 2006, at 5:49 PM, ext Su Thunder wrote:
If we can predict that many new extension headers will be defined
in the future,a new draft for the router to recognize the newly
defined extension header will be neccessary.For example,we can
define a set of parameters including the
