tree 8129b0f406b65b207e28017c46b49957eea41869
parent e32549edf945287cb799c8deb5c2524eee527779
author Nick Harper <nharper@chromium.org> 1588281349 -0700
committer CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> 1588950480 +0000

Restrict when 0-RTT will be accepted in QUIC.

QUIC imposes additional restrictions on when 0-RTT data can be accepted.
With this change, a QUIC server configured to support 0-RTT will only
accept early data if the transport parameters and application protocol
specific context are a byte-for-byte match from the original connection
to the 0-RTT resumption attempt.

Bug: 295
Change-Id: Ie5d4688d1c9076b49f2131bb66b27c87e2ba041a
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/41145
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: David Benjamin <davidben@google.com>