| | Rémi Denis-Courmont wrote: | > In any case, getaddrinfo() should be patched to | > [...] | | What should be the behavior is socktype and protocol are zero? Should | these two types be returned by default? What others? So far we return | TCP, UDP, and raw socket information. I'd rather keep the list short | but since we already have raw sockets in there (because they are in | POSIX) I won't reject anything that's more useful than raw sockets. | | - -- RFC 3493 says that 0 for socktype/protocol means that caller will accept any socket type / protocol, so presumably this does include DCCP and UDP-Lite. It would be just _great_ if getaddrinfo() could support Remi's cases for DCCP (RFC 4340) and UDP-Lite (RFC 3828). So far it is only possible to get an address by "cheating", i.e. pretending to getaddrinfo to be TCP or UDP. This does not really work well and still causes lots of problems/broken applications. Gerrit -- To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
