};
{endcode}
+{section: IPv6 support in External Libraries}
+gSOAP : according to their homepage, they support IPv6.
+OpenSSL : according to their news,
+o Added support for IPv6 addresses in certificate extensions.
+ See RFC 1884, section 2.2.
+
+So, what is certificate extensions?
{section: Todo}
Manageable daily work-list.
@@ -261,6 +268,7 @@
1:change every incidents where use sockaddr,sockaddr_in, and int.
1:change IpVerify not to depend on IPv4 address
1:think about test plan since IPv6 port is kind of overhaul. changing occurs in many places.
+1:Examine external libraries that deals with network. gSOAP, OpenSSL, and what else?
{section: Done}
@@ -276,6 +284,7 @@
1::We may create two sockets, IPv4 and IPv6. Call non-blocking accept to both of them. And poll() or select() or kqueue() on both sockets. In current Linux implementation, I think we do not need this kind of complexity. Linux kernels deal smoothly with faked IPv6 address. I expect it will be true for commercial Unix like AIX and Solaris.
*:internet.h seems to have a lot of IPv6 incompatible functions.
+
*:why do you call <a.b.c.d:pppp> as sinful string? what does it mean 'sinful'? - Now that I know.
This is Condor specific term. We need to extend definition to include IPv6 address. For example, <[a:b:c:d:e:f:g:h]:pppp> would work.
