Forum Discussion
Solved
TLS 1.3
TLS 1.3 is a very needed feature for those in corporate environments for our public facing websites. The speed advantages are immense in larger sites with no caching
TheAutisticTechie As with Chrome, TLS/1.3 is supported in all versions of Chromium-based Edge (and will be supported on all platforms).
1) TLS1.2 was announced and available to insiders to use & test at approx 6 months.
2) Responsible maintenance of a community that use your product should include announcing timelines for major updates like this..
3) the speed difference, as per plenty of real life benchmarks from the companies using it in production today is not insignificant.
It makes as 50% improvement in setup time for a TLS connection because only 2 instead of 3 total roundtrips are needed. The TLS component is halved.
For customers in Australia connecting to a US Server, that typically means about 200ms cut off the TTFB.
And 200ms latency is common. The global average RTT latency seen by users of Slack is reported as 200ms after they implemented their all-traffic cdn.
Another advantage of is that in a sense, it remembers! On sites you have previously visited, you can now send data on the first message to the server. This is called a “zero round trip.” (0-RTT). And yes, this also results in improved load time times
4) all software has vulnerabilities. & patches.
No one's suggesting cutting corners.
Microsoft's silence is either due to poor communication or because this isn't a priority.
If it's low priority it also won't the better developers assigned, and also will be a lower quality implementation.
2) Responsible maintenance of a community that use your product should include announcing timelines for major updates like this..
3) the speed difference, as per plenty of real life benchmarks from the companies using it in production today is not insignificant.
It makes as 50% improvement in setup time for a TLS connection because only 2 instead of 3 total roundtrips are needed. The TLS component is halved.
For customers in Australia connecting to a US Server, that typically means about 200ms cut off the TTFB.
And 200ms latency is common. The global average RTT latency seen by users of Slack is reported as 200ms after they implemented their all-traffic cdn.
Another advantage of is that in a sense, it remembers! On sites you have previously visited, you can now send data on the first message to the server. This is called a “zero round trip.” (0-RTT). And yes, this also results in improved load time times
4) all software has vulnerabilities. & patches.
No one's suggesting cutting corners.
Microsoft's silence is either due to poor communication or because this isn't a priority.
If it's low priority it also won't the better developers assigned, and also will be a lower quality implementation.
No, it hasn't been.
https://www.nccgroup.trust/us/about-us/newsroom-and-events/blog/2019/february/downgrade-attack-on-tls-1.3-and-vulnerabilities-in-major-tls-libraries/
- Eric_Lawrence
Microsoft
Unoki TLS/1.3 has been available in the new Edge since its first Canary release. Discussions of IIS and Windows more broadly are not in scope for this forum; you can find other communities where such conversations are more appropriate.
Eric_Lawrence Can we had a way (in entreprise) like they do in firefox to reject tls 1.0 and 1.1 and other weak cipher suite ?
