Gordon Messmer writes:
On 01/20/2011 03:31 PM, Sam Varshavchik wrote:Courier's code relies on being able to use IPv6 sockets to connect to either IPv4 or IPv6 addresses. There is no way to configure that an IPv4 socket be used for IPv4 addresses, and IPv6 sockets for IPv6 addresses. Doing something like this requires some code rewriting.Wouldn't the easiest fix be to use IPV6_V6ONLY mentioned in section 5.3 of RFC 3493?
No, that's something that's unrelated.But RFC 3493 also serves as a clear counterexample to what Debian's doing. The language in section 3.7 is just as clear as day:
Applications may use AF_INET6 sockets to open TCP connections to IPv4 nodes, or send UDP packets to IPv4 nodes, by simply encoding the destination's IPv4 address as an IPv4-mapped IPv6 address, and passing that address, within a sockaddr_in6 structure, in the connect() or sendto() call.With such, clear, unambiguous language, you can't help but ask yourself not only WTF is Debian's default config explicitly does the opposite, but why is that option even in the Linux kernel to start with?
So now you have not one, but multiple RFCs document that IPv6 sockets should be interoperable IPv4, and I just do not understand why this freight train is going in exactly the opposite direction. This one's a headscratcher.
pgp0d73B69flc.pgp
Description: PGP signature
------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
