3 ms·
Interestingly they've chosen to just not offer 0RTT at all at the back end, at least for now. I'm not actually sure if this helps. I guess it means 0RTT mitiga
by tialaramex 8y ago
Interestingly they've chosen to just not offer 0RTT at all at the back end, at least for now.
I'm not actually sure if this helps. I guess it means 0RTT mitigation at Cloudflare concentrates the risk there - they can take full responsibility for doing a good job and if your clients have nasty RTT (e.g. satellite) you get most of the benefit with no work. Still, if you're very small 0RTT safety is easy whereas Cloudflare has to work very hard to even make it somewhat resist replays because their system is so distributed.
- vbtechguy 8y agoYeah confirmed no TLS 1.3 0-RTT early data support on origin backend communications right now https://community.cloudflare.com/t/cloudflare-speak-tls-1-3-0-rtt-with-origin-backend/31507 https://community.cloudflare.com/t/cloudflare-speak-tls-1-3-...
- toast0 8y agoThey're not going to proxy the 0RTT to the origin to determine if they accept it or not, so it's two separate questions of accepting it from clients and offering it to origins. For clients, especially mobile or satellite clients, the latency win from one round trip saved may be worth the risk; for origins, the worst latency is probably not too much, and connection reuse over multiple client requests likely reduces the total number of connections made.
- dward 8y agoThe policy seems sane. * They know when they can serve 0RTT from their cache safely because they can be reasonably certain if handling a cached request is side effect free. * If connections to backend origins are reasonably persistent, there's not much latency reduction benefit from 0RTT compared to connections from consumer user agents.