HTCondorWiki: Ipv Six Work Note

 
 I do not think we need any class that encapsulating those BSD socket interfaces.  The reason is that I do not change any semantics of BSD socket interface but only syntax.
 
-Another reason is that BSD socket interface is kinda universal and well formed. For application socket classes, we already have Sock, ReliSock, and so on. Any abstraction other than proxy between application socket classes and BSD socket interface? I did not find any appealing reason. If you have any idea, please let me know.
+*:No DNS
+Some of functions already has condor_* replacement. These replacement functions has common structure, "nodns_enabled()". The purpose of these functions should be to support an environment that does not have DNS.
+
+IPv6 port should work well with nodns option.
 
 {section: Converting each socket functions }