In your previous mail you wrote:
> => I have the opposite policy so results are different. My target is
> integrated systems where IPv6 is *not* optional, no more than IP is!
That is a longer term goal. Currently that only works in closed
environments.
=> I disagree about the closed environments, this works everywhere but
this is very interesting only in environments where IPv6 is common.
>From my viewpoint, the applications wrt. ipv6 support can be split into a
few categories:
1) no ipv6 support
2) ipv6 support togglable at compile time; if you use the app on
ipv4-only system, it won't even run (or ipv4 features don't work properly)
[for example xinetd]
3) ipv6 support togglable at compile time; if you use the app on
ipv4-only system, ipv4 features work
4) ipv6 support detected/configured at runtime
I don't consider applications to be integrated properly unless 4) applies.
=> I support 4) only for some applications which are critical in case of
a crash (the kind of applications which are statically linked).
I get the impression you are doing mostly 2).
=> more than 2), the IPv6 support is not togglable!
As ipv4 isn't going away
any time soon, except in some closed environments like 3G mobile phones,
you have to be able to deal with all kinds of situations.
=> as an IPv6 application is IPv4 capable on a RFC 2553 compliant system
I don't understand your concern.
As said, I don't think this works yet in real life (consider: OS
distributions), and is counter-productive for the spread of IPv6 as
distributions cannot ship ipv6 ready apps just in case unless they're 3)
or 4) (because that'd hurt the operation of production software).
=> 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).
Regards
[EMAIL PROTECTED]
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
