Mark Andrews wrote: > In message <[EMAIL PROTECTED]>, Thomas Narten > writes: >> I'm not involved in this in detail, so I may be off base, but my >> understanding is that the advanced API has not been picked up by Open >> Group because its members didn't support doing so -- they just didn't >> see a need to. >> >> My own take is that standardization of the advanced API just isn't >> compelling. When I did a survey in the past of what various vendors >> had done with the advanced API, I found that none implemented it >> completely. Rather, most implemented bits and pieces of it depending >> on what applications needed the funcitonality (or just implemented >> private versions for the applications that needed the >> functionality). And since the functionality in the adnvanced API (by >> definition) isn't needed accept by fairly exotic usages, it's hard to >> make the arguement that it needs to be implemented for basic >> interoperability. >> >> Thomas >> -------------------------------------------------------------------- >> IETF IPv6 working group mailing list >> [email protected] >> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 >> -------------------------------------------------------------------- > > If you want to make UDP replies work without using a > descriptor per address you listen on you need part's of the > advanced API. > > Named uses the advanced API to get reply UDP traffic > sourced from the correct address.
Right, I have also used it for receiving unicast and multicast on the same socket and checking the destination address to determine if unicast or multicast, or to which multicast group when receiving multiple groups. I also have some multicast debugging/testing tools that work on a wide range of platforms (http://www.venaas.no/ssmping/) where I need the advanced API (not in6_pktinfo though) to get the hoplimit of received packets, Stig -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
