Re: [quicwg/base-drafts] Don't store or retransmit PATH_RESPONSE frames, avoid buffering (#2729)

[ianswett <[e-mail]>]

ianswett commented on this pull request.



> @@ -1721,7 +1721,12 @@ it can associate the peer's response with the corresponding PATH_CHALLENGE.
 ## Path Validation Responses
 
 On receiving a PATH_CHALLENGE frame, an endpoint MUST respond immediately by
-echoing the data contained in the PATH_CHALLENGE frame in a PATH_RESPONSE frame.
+echoing the data contained in the PATH_CHALLENGE frame in a PATH_RESPONSE frame,
+unless it has PATH_RESPONSE frames buffered for the same destination connection
+ID and wishes to limit memory consumption.

If we forbid multiple PATH_CHALLENGE frames in a single packet, I believe we don't need to add text about buffering.  But I'm not sure if that's an acceptable restriction to the WG.  If not, an alternate option would be to say you SHOULD only send one PATH_CHALLENGE in a packet and you SHOULD only respond to one PATH_CHALLENGE from a single packet.

-- 
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/2729#discussion_r292256204