>> > struct ip6_mtuinfo {
>> > struct sockaddr_in6 ip6m_addr; /* dst IPv6 address including scope */
>> > unsigned int ip6m_mtu; /* path MTU in host byte order */
>>
>> Is "unsigned int" appropriate here (I'm just wondering, not sure on
>> this)?
>
>What would you like to see instead?
>uint32_t? uint16_t?
An observation: both icmp6_mtu and nd_opt_mtu_mtu are uint32_t.
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
- Re: IPV6_USEMTU socket option Francis Dupont
- Re: IPV6_USEMTU socket option JINMEI Tatuya / 神明達哉
- Re: IPV6_USEMTU socket option Erik Nordmark
- Re: IPV6_USEMTU socket option Francis Dupont
- Re: IPV6_USEMTU socket option JINMEI Tatuya / 神明達哉
- Re: IPV6_USEMTU socket option Yves Legrandgerard
- Re: IPV6_USEMTU socket option Francis Dupont
- Re: IPV6_USEMTU socket option JINMEI Tatuya / 神明達哉
- Re: IPV6_USEMTU socket option Erik Nordmark
- Re: IPV6_USEMTU socket option JINMEI Tatuya / 神明達哉
- Re: IPV6_USEMTU socket option Jack McCann
- Re: IPV6_USEMTU socket option Tim Hartrick
- Re: IPV6_USEMTU socket option JINMEI Tatuya / 神明達哉
- Re: IPV6_USEMTU socket option Jun-ichiro itojun Hagino
- Re: IPV6_USEMTU socket option Jason R Thorpe
