Re: [quicwg/base-drafts] MSS Clamping Support (#3330)

[Martin Thomson <[e-mail]>]

The [section on PMTUD](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#name-icmp-packet-too-big-message) addresses this point.  In addition to PLPMTUD, we also describe how to use ICMP.

The answer we have does allow the path to send signals, but it doesn't allow for packet modification in any way.  In short, if the ICMP message gets through AND it contains enough information that the endpoint can be assured that the sender was on-path, then it can be used.

That's probably not an especially satisfactory answer, but I believe that is the state of the protocol and at this stage it would require significant effort to change - in the core protocol.

If there is a high path MTU but smaller packets would exhibit better performance, we currently have no answer.  That doesn't mean it is impossible to design a solution, but that would have to go through the endpoints and we don't currently have a way to do that.  One would need to be defined.  I suspect that the chances of getting that in for QUIC version 1 approaches zero, but this is work that can proceed independently.

Defining a generic IP-layer capability that protocols like QUIC could benefit from would be my suggested approach.  After all, I'm sure that the WebRTC folks would be thrilled to learn how to reduce latency or throughput for video on links that have these characteristics.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3330#issuecomment-572411529