[quicwg/base-drafts] Address validation for connection migration (#732)

[Martin Thomson <[e-mail]>]

This has been much-discussed, and it's a relatively isolated change, so I did it.

This modifies PING to have an optional payload and adds a PONG frame to echo
the PING.  An empty PING generates an ACK; a PING with a payload demands a
PONG.

Generating an unguessable PING is the basis of mid-connection address
validation.  If the PING is sent on the new path, and the PONG comes back, then
the remote address is probably OK to use.

I've taken the discussion in the issue into consideration here.  There's a lot
of potential nuance to capture in terms of how an endpoint might reduce and
restore send rates, but I've done what I can to thread the gap between allowing
unbounded sending along new and untested paths and allowing connections to get
back to doing business.

It's annoying that this makes PING and PONG so disparate.  I think that we have
a re-ordering of frames in our near future to correct minor infidelities like
this.  I didn't want to do that here and pollute this PR though.

Closes #161.
You can view, comment on, or merge this pull request online at:

  https://github.com/quicwg/base-drafts/pull/732

-- Commit Summary --

  * Address validation for connection migration

-- File Changes --

    M draft-ietf-quic-transport.md (122)

-- Patch Links --

https://github.com/quicwg/base-drafts/pull/732.patch
https://github.com/quicwg/base-drafts/pull/732.diff

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