Re: Why no uint16_t in in6_addr?
Stig Venaas <[email protected]>
| Newsgroups | gmane.network.ipv6.general |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Nov 03, 2005 at 05:10:30AM +0900, JINMEI Tatuya / ?$B?@L@C#:H wrote:
[...]
> One important point is, however, that a portable applications should
> not assume such internal details. So, for example, it should be
> generally discouraged for an application to get access to the
> __u6_addrXX members directly or to assume the internal data is aligned
> at some particular boundary.
Right, as I read the RFC, the only thing you can assume is
struct in6_addr {
uint8_t s6_addr[16]; /* IPv6 address */
};
So portable applications generally can use the s6_addr if they need.
Stig
---------------------------------------------------------------------
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [email protected]