In short, we plan to regularly mint new TLS versions (and likely other sensitive parameters such as extensions), roughly every six weeks matching Chrome’s release cycle. Chrome, Google servers, and any other deployment that wishes to participate, would support two (or more) versions of TLS 1.3: the standard stable 0x0304, and a rolling alternate version. Every six weeks, we would randomly pick a new code point.

source: HN

it does seem like there is a nontrivial failure rate

source: green

On replay, the main finding is that what’s in the draft is not workably secure, and the review includes 5 different attacks against 0-RTT data to illustrate that.

https://github.com/tlswg/tls13-spec/issues/1001

source: green

Updates in response to NSA analysis.

source: solar