IPv6 support on Win2K3

Hi,
Currently we are planning to port our IPv4 based application running on Win2k3 (IPv4 stack) to IPv6.
We came to know that Windows Vista onwards there is a new mechanism where in a single socket can be used for both IPv4 and IPv6 (WSK, Winsock Kernel). But since our application is running on Win2K3,
* is there any way the single socket option can be implemented in Win2K3 with Winsock2 API.
* Is there any driver which I can install to provide this functionality ?
* Currently we are planning to use following options if stack/winsock does not support single socket
- Create multiple socket (we want to avoid this if possible)
- Create separate thread for IPv6 and create dedicated socket for IPv6
- Use two separate sockets and non blocking select API
Any comment on this mechansim ? Or any other alternatives?
* Also is there any plan to port WSK APIs to Win2K3 or supportIPV6_V6ONLY to use a single socket .
Appreciate inputs on this.
Regards
Manoj
[1449 byte] By [maniyan75] at [2008-1-9]
# 1

FYI . The migrated application will run on a dual stack Win2k3.

Rgds

Manoj

maniyan75 at 2007-10-3 > top of Msdn Tech,Windows Networking Development,Winsock Kernel (WSK)...
# 2

Pls somebody from MS clarify this ?

1. None of the GQoS API documentations talk about support of flow label field or traffic class indicator (Used for QoS marking) in IPv6. Also Winsock2 does not seem to support RFC 3542 (Advanced Socket API for IPv6) If it is supported, is there any mechanism to set these values from the application layer. We are currently using Windows 2003 server with dual stack.
2. Named Pipes are predominantly used in our application. As per our understanding Named pipes use NetBIOS over TCP/IP as underlying protocol. NetBIOS currently does not support IPv6. In that case is there any way we can support existing named pipes on a IPv6 based Windows 2003 server?
3. As per MSDN documentation, dual mode socket or WSK APIs are available only in Windows Longhorn and Vista. Is there any plan to introduce this functionality in Windows 2003 ? If yes, when is it expected to be out? For supporting IPv6 and IPv4 simultaneously in Win 2K3, creating two separate sockets is the only option ?
4. As per our understanding of .Net APIs there wont be any change on the IPv6 migration perspective for the code which uses System.Net.Sockets.TcpClient for establishing socket connection.Is this correct ?
Thanks in advance
maniyan75 at 2007-10-3 > top of Msdn Tech,Windows Networking Development,Winsock Kernel (WSK)...
# 3

131 views, no replies (other than mine). Does it mean

* this is wrong forum to ask ?

* My qn doesn;t make any sense ?

* No body knows the answer ?

maniyan75 at 2007-10-3 > top of Msdn Tech,Windows Networking Development,Winsock Kernel (WSK)...