>>>>> On Tue, 14 Nov 2000 09:42:19 +0100,
>>>>> Francis Dupont <[EMAIL PROTECTED]> said:
> 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)?
My main concern is about UDP applications that can't divide outgoing
data into multiple packets but do not want to fragment the packet in a
(much) smaller size than the path MTU. Possible examples would be NFS
and DHCP. I admit that NFS may not be a good example, because in UNIX
systems, NFS is typically implemented in the kernel.
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]
--------------------------------------------------------------------
