>>> recent source code of FreeBSD and NetBSD (which have not supported
>>> 2292bis yet). The only occurrence of ip6r0_addr other than in user
>>> applications is in tcpdump, where no compatibility issue exists since
>>> tcpdump uses its own header definitions.
>
>> Which is telling about the stability and widespread acceptance of this
>> API. I think its very likely that one of the reasons they needed
>> private headers had to do with the variations of API between 2292 and
>> 2292bis.
>
>Actually, tcpdump uses its own header definitions in many source
>files. Regarding IPv6 related ones, it (re)defines the IPv6 header,
>the Hop-by-Hop options header, the Destination options header, the
>Fragment header, and the Routing header.
this is because tcpdump would like to decode IPv6 frames even when
it runs on IPv4-only platforms. the re-definition has nothing to do
with the acceptance of RFC2292.
itojun
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
