In your previous mail you wrote:
I'm now considering UDP applications that are sensitive to path MTU
(toward the destinations). I recalled a discussion about a new socket
option "IPV6_USEMTU", which allowed an application to specify an
appropriate path MTU for packets sent from the application. I checked
the archive of this list in April 2000, and, to my suprise, the
discussion suddenly disappeared without any consensus.
=> today only IPV6_USE_MIN_MTU seems to be defined, implemented and
used (for instance by BIND and racoon, the KAME IKE daemon).
I don't know if IPV6_USEMTU as you define is very useful but the
getsockopt() counterpart (which gives the actual path MTU) *is* useful.
Perhaps the getsockopt() with a standard way to disable fragmentation
is enough (it should be enough for a traceroute_pmtu6)?
Regards
[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]
--------------------------------------------------------------------
