IETF Interim: Domain Name System Operations (DNSOP) 2026-02-18 20:00
•February 20, 2026
0
Why It Matters
Standardizing DNS error reporting and linking to neutral incident databases enhances user awareness of censorship, reduces support overhead, and strengthens trust in internet infrastructure.
Key Takeaways
- •Structured DNS error draft updated to version 16, adds client flexibility.
- •New option code separates request indicator from extended error data.
- •Public resolver errors draft shifts to incident databases for transparency.
- •Chrome aims to display filtering info via Lumen database by M147.
- •Trust concerns addressed by allowing any resolver to reference neutral databases.
Summary
The IETF DNS Operations (DNSOP) interim meeting focused on two working‑group drafts: the Structured DNS Error specification and the Public Resolver Errors draft. Participants reviewed progress, incorporated feedback from the previous IETF last call, and outlined next steps toward working‑group last calls and IETF‑EG submission.
Dan Wing presented the updated Structured DNS Error draft (version 16), highlighting client‑side flexibility in handling extended error data, a new option code that cleanly separates request indicators from responses, and the creation of an ANO registry for extensible sub‑error codes. Mark Nottingham then described the Public Resolver Errors draft, which addresses growing DNS‑based censorship by surfacing filtering incidents through neutral incident databases such as the Lumen (formerly Chilling Effects) repository, moving away from privileged resolver‑only disclosures.
Key examples included the plan to integrate Lumen links into Chrome’s DNS error page by the M147 release, currently behind a feature flag, and the broader strategy of allowing any resolver to reference trusted databases rather than limiting visibility to a few designated resolvers. The discussion also touched on trust challenges when third‑party resolvers display policy‑driven messages and the need for safeguards against misuse.
If adopted, these drafts will improve transparency for end‑users encountering DNS filtering, reduce support burdens on ISPs and browsers, and provide a standardized mechanism for communicating legal or policy‑driven blocks. The changes also set a precedent for collaborative governance of DNS error handling across the internet ecosystem.
Original Description
Domain Name System Operations (DNSOP) interim meeting session
2026-02-18 20:00
0
Comments
Want to join the conversation?
Loading comments...