On 7/19/11 4:26 AM, Karl Auer wrote:
Thanks Erik. I've read the explanation in RFC 2765, and sort of see the
motivation, but it doesn't help me understand exactly what the node
should be doing. That is, the "why" is slightly clearer, but the "what"
is not.
What, exactly, is a node supposed to do when it receives a PTB< 1280
after it has sent an ordinary packet?
a) fragment at 1280, regardless of the returned PMTU value
Correct; fragment as if the path mtu was 1280.
But in addition, insert a fragment header even for packets that don't
require fragmentation.
Erik
b) fragment so as to produce fragments of sizes equal to or smaller than
the returned PMTU value, but don't "remember" the returned PMTU value
>
c) create a new packet that is identical to the original packet but has
a fragment header inserted (i.e., forms a fragment sequence one fragment
long, with More-Fragments=0 in the fragment header)
d) fail to send the packet
e) something else...?
Only b) seems remotely useful, but it makes a mockery of the idea that a
PMTU of 1280 is required for IPv6.
Regards, K.
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
