Re: Last Call: 'Neighbor Discovery for IP version 6 (IPv6)' to Draft Standard (draft-ietf-ipv6-2461bis)

2006-11-09 Thread Syam Madanapalli
I agree that the issues mentioned in the draft draft-madanapalli-ipv6-periodic-rtr-advts-00.txt should not be blocking 2461bis, and should be moved forward. But I think the draft is applicable for certain category of networks (Cellular Networks) so it may not be a good idea to put the same

Re: Revised address selection preference API draft-chakrabarti-ipv6-addrselect-api-04

2006-11-09 Thread Samita Chakrabarti
Hello Rémi, Thanks for your time reviewing V04 of the address selection API. Julien L. has already addressed your comments. Here are some additional comments. The proposed solution of extending the getaddrinfo structure (at the end) is designed to keep ABI consistency in mind. The extended

Re: Revised address selection preference API draft-chakrabarti-ipv6-addrselect-api-04

2006-11-09 Thread Samita Chakrabarti
This is all a matter of being consistent with the Advanced IPv6 API, and with the established practice in POSIX world. Pretty much every setsockopt uses int, unless it has very peculiar reason not to do so. Using something else will only confuse people, and add a (minor) extra implementation

Re: Revised address selection preference API draft-chakrabarti-ipv6-addrselect-api-04

2006-11-09 Thread Rémi Denis-Courmont
Hello, On Thu, Nov 09, 2006 at 07:45:29PM -0800, Samita Chakrabarti wrote : The proposed solution of extending the getaddrinfo structure (at the end) is designed to keep ABI consistency in mind. The extended ai_eflags will not break ABI boundaries unless the library design is broken.