Re: additional agenda item

>>>>> On Mon, 1 Mar 2004 00:08:54 -0800 (PST), 
>>>>> Erik Nordmark <Erik.Nordmark <at> sun.com> said:

>> Fair enough, but let me make a quick check: is this a direct response
>> to my request for a slot (positive or negative), or just a general
>> input on this issue itself?

> Latter.

> On the former; Getting the API for the list of addresses documented seems 
> quite useful so I think it makes sense spending face time on this.

Understood, and thanks.

>> u_int             ifa_flags;        /* Interface flags */

> Aren't the flags implementation specific?

I'm not sure, but probably yes, it is implementation specific.

>> The ifa_data field references address family specific data.  For AF_LINK
>> addresses it contains a pointer to the struct if_data (as defined in
>> include file <net/if.h>) which contains various interface attributes and
>> statistics.  For all other address families, it contains a pointer to
>> the struct ifa_data (as defined in include file <net/if.h>) which
>> contains per-address interface statistics.

> The actual statistics that are provided might be implementation specific.

Again, probably correct.

> Do we want an API that can be provided for non-BSD IP stacks? Windows?

If we agree on the need for this kind of API, I believe it should be
portable, that is, it should work for non-BSD, Windows, or whatever.
So, the resulting API might lose some of the information that the
current getifaddrs(3) library can provide.  But I'd rather be happier
to have a portable API.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei <at> isl.rdc.toshiba.co.jp

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 <at> ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------