Re: RFC3678: header incompatibility

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>	i'm aware of that line, but that does not really meet my observations.

You asked that we revise the RFC to be compatible with POSIX.
I observed that the RFC is not incompatible with POSIX.  Now you
are asserting that isn't what you were really asking?

>	if the above POSIX line suggests inclusion of <sys/socket.h> from
>	<netinet/in.h>, why freebsd did not do that and defined sockaddr_storage
>	in two places?

Because FreeBSD chose a different implementation.

Are you suggesting that POSIX is wrong, or that we were wrong to write
the spec to be compatible with what POSIX requires?  Or are you saying
that we should have ignored POSIX and instead written the spec to
what FreeBSD, OpenSolaris and *BSD prefer?

(I'd note that MacOS X has a simple #include <sys/socket.h> in
<netinet/in.h>, so apparently it's not impossible to implement
things that way.)

  Bill

_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]