>>>>> On Fri, 17 Nov 2000 16:28:00 -0800 (PST),
>>>>> Erik Nordmark <[EMAIL PROTECTED]> said:
> This is what I've edited together so far.
> 11.3. Path MTU Discovery and UDP
> UDP and raw socket applications need to be able to determine the
> "maximum send transport-message size" (Section 5.1 of [RFC-1981]) to
> a given destination so that those applications can participate in
> path MTU discovery. This lets those applications send smaller
> datagrams to the destination, avoiding fragmentation.
> This is accomplished using a new ancillary data item (IPV6_PATHMTU)
> which is delivered to recvmsg() without any actual data. The
> application enable the receipt of IPV6_PATHMTU ancillary data items
> by enabing IPV6_RECVPATHMTU.
I have one more question about the option. What if the size of an
outgoing packet is larger than the MTU of the outgoing interface on
the sending node, when the application set the IPV6_RECVPATHMTU
option? Should the kerenl pass the IPV6_PATHMTU ancillary data with
the MTU of the outgoing interface?
(BTW, our current implementation does not pass the ancillary data on
the sending node. In such a case, it just fragment the packet using
the MTU of the outgoing interface.)
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]
--------------------------------------------------------------------
