>>>>> On Tue, 07 Jan 2003 16:42:18 -0800,
>>>>> "Fred L. Templin" <[EMAIL PROTECTED]> said:
> I believe the text you are referring to is the following:
> "When the application is sending packets too big for the path MTU
> recvmsg() will return zero (indicating no data) but there will be a
> cmsghdr with cmsg_type set to IPV6_PATHMTU, and cmsg_len will
> indicate that cmsg_data is sizeof(struct ip6_mtuinfo) bytes long."
> The way I read this, applications are informed of path MTU restrictions
> when they are actively sending packets that result in ICMPv6 "packet too
> big" error messages (i.e., even when the "packet too big" messages are
> locally-generated). I see no requirement in this specification for
> asynchronous notification of PMTU decreases.
That depends on what you meant by "asynchronous" and "requirement".
As for "asynchronous"ness:
If the application watches a read (note: not "write") event on the UDP
socket, it will be ale to receive the "asynchronous" notification when
an ICMPv6 too big occurs.
As for "requirement":
Whether the application watches read events is (of course) up to the
application; the specification does not require the application to
follow the usage. In this sense, you are correct: there is no
"requirement" in the specification for asynchronous notification.
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]
--------------------------------------------------------------------
