>>>>> On Thu, 16 Nov 2000 14:46:36 -0800 (PST),
>>>>> Erik Nordmark <[EMAIL PROTECTED]> said:
>> > Applications can dynamically grab the path MTU by the IPV6_RECVPATHMTU
>> > socket option (upon receiving an ICMPv6 packet toobig error).
>> >
>>
>> Is that mean, when IPV6_RECVPATHMTU option is setted (UDP/raw socket), that
>> fragmentation is disabled ?
> No, I don't think so.
> IPV6_RECVPATHMTU is so that e.g. UDP applications that do packetization
> can determine when the path MTU changes and adjust the size of the
> packets they are sending.
My understanding is the same as yours.
> Should we just define the semantic equivalent of setting IP_DF on
> a raw socket with IP_HDRINCL set for IPv6? (IPV6_DONTFRAG?)
I think this type of option can be useful, but I still think the
IPV6_USEMTU option (which allows an application to specify the path
MTU for an outgoing packet) is useful as well. And, if we take this
approach, prohibiting fragment can be implemented as a special case of
the option (i.e, setting a very large value as the MTU). What do you
think of this?
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]
--------------------------------------------------------------------
