[quicwg/base-drafts] MAX_PACKET_SIZE frame (#2545)

[Igor Lubashev <[e-mail]>]

This is likely a v2 feature, as we discussed on the list.

There are several ongoing efforts in IETF to have network deliver PMTU information to the intended destination, in addition to sending the traditional ICMP PTB message to the sender from an on-path device.

The efforts include [draft-hinden-6man-mtu-option](https://tools.ietf.org/html/draft-hinden-6man-mtu-option), [draft-leddy-6man-truncate attempts](https://tools.ietf.org/html/draft-leddy-6man-truncate attempts), [draft-ioametal-ippm-6man-ioam-ipv6-options](https://tools.ietf.org/html/draft-ioametal-ippm-6man-ioam-ipv6-options), [draft-ietf-ippm-ioam-data](https://tools.ietf.org/html/draft-ietf-ippm-ioam-data).

In all cases, if an endpoint learns the PMTU from the sender to itself, there is still a problem of passing that information back to the sender.  We know that ICMP PTB has only limited chances of getting back to the sender, even if sent directly by the receiver.  However, a QUIC packet with MAX_PACKET_SIZE frame that updates the “max_packet_size” transport parameter solves the problem.  Hence the proposed new frame.

-- 
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/2545