RFE 7187677 "make IPV6_NEXTHOP option work with IPv4 mapped addresses": does it make any sense?
Hi, All
While the world migrates to new generation IPv6 stack after IPv4 address exhaustion in middle of 2011, Solaris OS had delivered IPv4 mapping support at socket interface level.
which greatly simplifies code modification in order to get IPv6 compatibility in existing software.
It is possible that transition period to IPv6 will be extended to a couple of years when both IPv4 and IPv6 functionality will be solicited to work simultaneously in a single UNIX process context.
Solaris OS meets that requirement with exception of some socket options support.
I am using IP_NEXTHOP functionality many years for IPv4 applications.
While the world migrates to new generation IPv6 stack after IPv4 address exhaustion in middle of 2011, Solaris OS had delivered IPv4 mapping support at socket interface level.
which greatly simplifies code modification in order to get IPv6 compatibility in existing software.
It is possible that transition period to IPv6 will be extended to a couple of years when both IPv4 and IPv6 functionality will be solicited to work simultaneously in a single UNIX process context.
Solaris OS meets that requirement with exception of some socket options support.
I am using IP_NEXTHOP functionality many years for IPv4 applications.
0