On 18-Nov-00 Erik Nordmark wrote:
>
> This is what I've edited together so far.
> Note that the IPV6_PATHMTU option is used both as ancillary data (when
> IPV6_RECVPATHMTU is enabled) and with getsockopt to retrieve the
> current path MTU value for a destination.
>
> Comments?
> Erik
>
>
> 11.1. Sending with the Minimum MTU
>
[ylg]=> I would prefer to replace this option by the more general one
IPV6_USEMTU (IPV6_USE_MIN_MTU <=> (IPV6_USEMTU, 1280)) and add the particular
case (IPV6_USEMTU, 0) to say to the application to use the outgoing MTU (case
which is not covered in your proposal, see below 11.4)
> 11.2. Sending without fragmentation
>
[ylg]=> That's OK. And, as you wrote in a previous message, I think this stuff
must be keeped separate from preceding paragraph 11.1.
> 11.4. Determining the current path MTU
>
> path MTU value for a given destination address. If the IP layer does
> not have a cached path MTU value it will return the interface MTU for
> the interface that will be used when sending to the specified IPv6
> address.
[ylg]=> It does not solve the problem to get/use the MTU of outgoing
interface because you need the path MTU for the destination to be uncached
(unless, of course, the route is deleted before).
----------------------------------
Yves Legrandg�rard
E-Mail: [EMAIL PROTECTED]
Date: 20-Nov-00
Time: 11:18:14
----------------------------------
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
