Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bundle new client connection ID and path challenge in migration probes #1730

Merged
merged 10 commits into from Sep 12, 2018
9 changes: 5 additions & 4 deletions draft-ietf-quic-transport.md
Expand Up @@ -2074,10 +2074,11 @@ path validation with other frames. For instance, an endpoint may pad a packet
carrying a PATH_CHALLENGE for PMTU discovery, or an endpoint may bundle a
PATH_RESPONSE with its own PATH_CHALLENGE.

When probing a new path, an endpoint may want to ensure that the response, if
any, is sent to a specific connection ID. The endpoint achieves that by bundling
NEW_CONNECTION_ID and PATH_CHALLENGE frames. This ensures that at least one new
connection ID will be available at the peer for use in the probe response.
When probing a new path, an endpoint might want to ensure that its peer has an
unused connection ID available for responses. The endpoint can send
NEW_CONNECTION_ID and PATH_CHALLENGE frames in the same packet. This ensures
that an unused connection ID will be available to the peer when sending a
response.

### Initiation

Expand Down