- New BGP analysis could enhance disruption detection, but challenges in deployment persist.
- QUIC adoption is hindered by browser inconsistencies, requiring both trigger mechanisms for widespread support.
What happened: Key topics at IETF 123 on BGP and QUIC challenges
The IETF 123 meeting in Madrid brought together the Internet Engineering and Planning Group (IEPG) to discuss several key technical challenges. One major topic was the detection of network disruptions through BGP (Border Gateway Protocol) analysis. The team looked at BGP withdrawals and topology updates to infer potential inter-Autonomous System (AS) failures. While this approach is not new, turning this analysis into a practical tool for ISPs remains difficult.
Another topic was the adoption of QUIC, the transport protocol designed to reduce connection latency and improve speed. The discussion revealed challenges with browser support. Chrome, while supporting QUIC, shows much lower usage rates than expected. Safari, meanwhile, uses a newer approach, but only partially supports QUIC. For servers to fully leverage QUIC, they need to support both the alt-svc and DNS HTTPS trigger mechanisms. This creates complications for content servers.
Also Read: IETF 123: Boosts protocols with hackathon and sprint
Also Read: IETF 123 advances in Madrid following hackathon conclusion
Why it’s important
The discussions highlight two important issues for improving Internet operations. First, using BGP data to detect disruptions could greatly improve network monitoring. However, making this insight accessible and useful for ISPs remains a challenge. On the QUIC front, despite its potential, the slow adoption across browsers continues to hinder its effectiveness. For QUIC to reach its full potential, content servers must support both triggering mechanisms, raising concerns about protocol deployment and browser compatibility.
