Re: [quicwg/base-drafts] Describe PMTU probing that includes source connection ID for routing … (#2402)

[Kazuho Oku <[e-mail]>]

kazuho commented on this pull request.



> @@ -3274,6 +3274,22 @@ The considerations for processing ICMP messages in the previous section also
 apply if these messages are used by DPLPMTUD.
 
 
+### PMTU Probes Containing Source Connection ID
+
+Endpoints that rely on the destination connection ID for routing QUIC packets
+are likely to require that connection ID included in PMTU probe packets in order
+to route resulting ICMP messages ({{icmp-pmtud}}) back to the correct endpoints.
+
+Only long header packets ({{long-header}}) contain source connection IDs, but
+long header packets will not be acknowledged once the connection has been
+established.  One way to construct a PMTU probe is to coalesce (see
+{{packet-coalesce}}) a Handshake packet ({{packet-handshake}}) with a short

@igorlord I am fine with using a Handshake packet considering that this is an example (i.e., "One  way of...").

Though personally, I might be interested in sending an 0-RTT packet with zero-length payload (i.e. the Length field set to zero) even just to grease the client implementations.

-- 
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/pull/2402#discussion_r254109241