On Tue, 24 Jul 2018, Templin (US), Fred L wrote:
Try it - by default, iperf3 sets an 8KB UDP packet size and allows
packets to fragment across paths that support only smaller MTUs. I have
seen iperf3 exercise IP reassembly at line rates on high-speed links,
i.e., it shows that reassembly at high rates is feasible.
We know from RFC4963 that there are dangers for reassembly at high
rates, but there are applications such as iperf3 that ignore the "SHOULD
NOT" and leverage IP fragmentation anyway. So, should the "SHOULD NOT"
have an asterisk?
The iperf3 usage of fragments for UDP testing seems to be platform
specific, at least that's what I've seen. Behaviour has been different on
MacOS compared to Linux.
Anyhow, I believe we should keep the "SHOULD NOT". This allows
applications that feel they have a good reason to do fragmentation to do
so, but doesn't disallow it.
--
Mikael Abrahamsson email: [email protected]
_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area
