>=> my target is not the same, you want to provide an optional IPv6 support
>(so 3) or 4) are needed), I want to provide an integrated IPv6 support
>so the IPv6 support is *not* optional, there is only a possibility to
>disable it for disaster recovery (because I run the code on the same
>system I develop it, I don't use the traditional/expensive way with
>two boxes).
for this part, people have different requirements depending on their
standpoints. for example, for *BSD-integrated KAME systems, it was
strict requirement that we can let people happily replace IPv4/v6 dual
stack kernel with IPv4-only kernel, without requiring recompilation of
userland programs. therefore, we decided we shouldn't use AF_INET6
hardcoded, we should be using getaddrinfo loop instead.
{Free,Net,Open}BSD ships compiled kernel binary with IPv6 support by
default, which is good. however, there are people who are doing
embedded IPv4-only router product and such. if we use AF_INET6
hardcoded into uersland binaries, they will be in trouble.
you may still be able to provide AF_INET6 socket layer, without
IPv6 code, but it looked too hairy to me.
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]
--------------------------------------------------------------------
