Hi Alain, > >>For edification. I have a node on a work LAN that knows nothing of >>IPv6. I download software and configure my node to be >capable of IPv6. >>I manually configure my interface to support IPv6. I now ftp to an >>IPv6 address. This is not going to work. But I was stupid >to think it >>would? Is this the kind of basic mistake your also worried about? >> >Alternate scenario: >We ship our system so they configure IPv6 ON by default on all >interface. User install this machine on his v4-only network >and now experiment larger than usual delays to connect to his >favorite servers. User call customer support. This is what I >worried about.
Yep. I know of large user that may require all new systems very soon must be capable of supporting both IPv4 and IPv6. They specifically will require IPv6 not be enabled automaitcally. The reason is that they have gone far beyond Sebastien's draft of potential problems and know not to have it enabled automatically. It is good to document these use issues in the IETF but we need to be responsible to make sure all sides of the coin are depicted. I think it's a thin line where the IETF should work on operational conditions and where they should not. We all say we are so busy and we have the entire problem statement area BOF in San Francisco next week. Part of our problem is we are doing more than what we were mean't to do in the IETF. A lot of these issues are documented in the market but they are not going to publicize it so some of us have to watch it get redone here. Regards, /jim -------------------------------------------------------------------- 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] --------------------------------------------------------------------
