3 ms·

"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 rele

• tptacek 8y ago
  Those are internal TLS versions used only by Chrome; they're not being promoted as a "standard". I don't know if this is an instance of it, but there's an annoying phenomenon where people on message boards like to pretend that standards have near-statutory authority; that once a standard is issued, every vendor has to adhere to it no matter what their purpose. Were that to be your argument here, you'd in effect be arguing that Google can't deviate from the TLS 1.3 standard even to help TLS standardization efforts.
  • peterwwillis 8y ago
    I was trying to point out how middleware vendors' implementations of standards will always monkey with somebody else's client/server model, and that the idea of "well let's just add some features to this standard and expect things to keep working" is a fool's errand. They can monkey with the standards all they like, but the way they're doing it is doomed to failure. Separate from that I was just kind of chuckling at how their proposal is literally "we're shipping out changes with Chrome so you guys can either get on the bandwagon or figure something else out".
    • tptacek 8y ago
      Nobody else needs to get on the bandwagon. The whole point of the experiment is that standards-compliant software won't care about what Google is doing; the only things that should be impacted are middleboxes that violate the standard.