during RFC2292 to 2292bis transition, it seems that the following text
has been added to multiple places:
(how to reset values set by IPV6_HOPLIMIT setsockopt)
> In order to clear a sticky IPV6_HOPLIMIT option the application can
> specify -1 as the value. Alternatively, the application can specify <--
> an IPV6_HOPLIMIT socket option with a zero length. <--
i don't think it is a usual practice for setsockopt. they normally
take a parameter with fixed length.
i'm wondering where did this behavior come from, and how popular is it
for UNIX setsockopt to behave like this. any hints?
itojun
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
