Yes, there seems to be some confusion here between the "stack" and things that run over it. Although I suppose this distinction is probably more important to those of us who worked on it than it is to the average end user.
The IPv6 stack currently shipping in Windows XP is primarily intended for developers and trial network deployments. The new getadrinfo and getnameinfo APIs are supported for use with IPv6 and IPv4, so developers can write their programs to be protocol agnostic. Additionally, other APIs (like GetAdaptersAddresses) are now IPv6-aware. We'd like to encourage independent developers to port their applications to support IPv6. As other people have pointed out, many of the network utilities (e.g. telnet, ftp) that are included with Windows XP are IPv6-enabled. A number of people had been asking for netstat support, and that's there now. Netsh can be used for configuration, the hosts file can contain IPv6 addresses, etc. And IE 6 (really wininet as Jeroen points out) now supports native IPv6 web browsing. One thing that I haven't seen mentioned yet is RPC. RPC is IPv6-enabled in XP, so any applications that run over RPC can use IPv6 between XP machines. Most of the other things people are asking for here (like IIS, file sharing, DNS over v6 transport, Windows Media Services, etc) are being worked on. I've used working prototypes for several of these. I don't want to disappoint anyone by promising any specific release dates though. The FAQ for IPv6 on Windows XP can be found at http://www.microsoft.com/windowsxp/pro/techinfo/administration/ipv6/defa ult.asp And more info about our IPv6 plans can be found at http://www.microsoft.com/ipv6 Thanks, --Brian -------------------------------------------------------------------- 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] --------------------------------------------------------------------
