![]() ![]() ![]() QUIC’s low-latency handshake is its headline feature. In this post I'll use real (anonymous and aggregated) data from the Fastly network to illustrate how important compression is in practice for achieving the fast startup performance that QUIC promises. ![]() QUIC implementations are now faced with the decision of whether or not updating their embedded TLS code to support certificate compression is urgent. At the same time, QUIC's headline feature is its built-in low latency handshake that is more reliant on small handshake sizes than is widely understood. The IETF recently approved the TLS certificate compression extension, an optimization that promises to reduce the size of the TLS handshake by compressing its largest part. Powered by Signal Sciences Next-Gen WAF Bot protection DDoS mitigationīy industry Streaming media Digital publishing Online retail Financial services SaaS Travel & hospitality Online educationīy need Infrastructure savings Multi-cloud optimizationīy service Live event services Professional services Managed CDN Support plansĭoes the QUIC handshake require compression to be fast? Network Services Content delivery (CDN) CDN Video Streaming Load balancing Image Optimization TLS encryption Origin Connect The platform behind the products that lets you create unforgettable experiences at global scale Learn more
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |