Subject: [quicwg/base-drafts] PATH_RESPONSE isn't path-tied (#3797)

From: Mike Bishop <[email-masked]>
Date: Tue, 30 Jun 2020 14:06:52 -0700

In #2637, we removed the requirement that PATH_RESPONSE be sent/received on the same path that PATH_CHALLENGE was sent.  However, there is still text in the document that relies on this assumption.

- In 8.5, it explains that receipt of the PATH_RESPONSE on another interface doesn't cause validation to fail, because "It is possible that a valid PATH_RESPONSE might be received in the future."  But receipt of the PATH_RESPONSE, over any interface *is* valid, and causes the validation to *succeed*.
- In 9.2, it suggests using path validation to demonstrate return reachability, but since PATH_RESPONSE need not be sent on the same path, path validation doesn't demonstrate that.

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