>>>>> On Fri, 17 Nov 2000 17:59:33 +0100 (CET),
>>>>> Yves Legrandgerard <[EMAIL PROTECTED]> said:
>>> As we said in a previous message, F. Dupont and me, a useful option would be
>>> a new option to getsockopt() to get the outgoing MTU. For example, it helps
>>> tracemtu to discover the right mtu to start (otherwise, we have to set
>>> IPV6_DONTFRAG option, and try successive MTU (choosen in a list of possible
>>> MTU, ordered decreasingly) until we don't get EMSGSIZE error (an other pb :
>>> does exist such a list, i.e. the (right) list of all possible MTUs?).
>>
>> Presumably such an option needs to take a sockaddr_in6 as an argument
>> to specify the destination. We can reuse the proposed ip6_mtuinfo structure
>> for this.
>>
>> Do you care to know whether the kernel has path mtu information or
>> is just returning the mtu of the outgoing interface?
>>
> [ylg]=> No, I don't care. I'm only interessed in outgoing interface mtu. I
> think that your proposal to reuse the proposed ip6_mtuinfo structure is a good
> idea.
Then why not just look up the routing table and get the MTU of the
outgoing interface? I admit that a single operation to do that would
be convenient, but I personally don't think we have to add a separate
socket option for this particular purpose.
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]
--------------------------------------------------------------------
