>>>>> On Sun, 10 Jun 2001 15:11:35 -0400,
>>>>> "Lori Napoli" <[EMAIL PROTECTED]> said:
> I should have been more specific with my question. I agree the ancillary
> data will override the setsockopt. I was really asking what happens if an
> application does a setsockopt for IPV6_UNICAST_HOPS and IPV6_HOPLIMIT?
> Does the IPV6_HOPLIMIT replace the value specified by the IPV6_UNICAST_HOPS
> or are they separate values?
Sorry, I forgot to reply to this. I believe the spec is ambiguous on
this point. Our (KAME's) implementation always prefer IPV6_HOPLIMIT
to IPV6_xxCAST_HOPS. So,
> Lets say IPV6_UNICAST_HOPS = x, kernel
> default = z and IPV6_HOPLIMIT = y. Would 'y' be the hoplimit used for a
> unicast send?
Yes, in our implementation.
> Then suppose the application clears the IPV6_HOPLIMIT value.
> Do we fall back to 'x' (the value specified on IPV6_UNICAST_HOPS) or 'z'
> (kernel default)?
Our implementation should fall back to 'x'.
It would be better to make this clear on the next revision of the
rfc2292bis draft.
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[EMAIL PROTECTED]
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
