> x == -1: use kernel default. That is, perform path MTU discovery
> for unicast, and disable it for multicast.
> x == 0: always perform path MTU discovery.
> x >= 1: always disable path MTU discovery and send packets at
> the minimum MTU.
> (values less than -1 are invalid.)
I'd restate the text for -1 to say something like:
Perform path MTU discovery for unicast destinations but do not
perform it for multicast destinations. Packets to multicast
destinations are therefor sent with the minimum MTU.
and separately state that
The default value of this option is -1.
Why the x >=1 as opposed to x == 1? To be compatible with existing
applications?
The reason I'm asking is because it looks a bit odd to disallow less than -1
when greater than 1 is allowed.
Erik
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
