DNSOP Working Group

DNSOP Working Group
Name	DNSOP Working Group
Formation	2010s
Type	Working group
Location	Internet Engineering Task Force, global
Focus	Domain Name System operations and protocol deployment

DNSOP Working Group

The DNSOP Working Group is an Internet Engineering Task Force-chartered working group focused on operational practices, protocol updates, and deployment guidance for the Domain Name System, coordinating among standards bodies, registries, and network operators. It produces informational and standards-track documents to guide operators of root name servers, top-level domain registries, recursive resolvers, and authoritative servers, engaging with communities such as ICANN, IETF Working Group, Regional Internet Registrys and operator forums like DNS-OARC and RIPE NCC.

Overview

The group addresses operational aspects of the Domain Name System as implemented across infrastructure such as root zone, generic top-level domains, country code top-level domains, and recursive resolver ecosystems represented by entities including Verisign, Cloudflare, Google Public DNS, OpenDNS, and Quad9. It collaborates with protocol development efforts in IETF areas like TRANSPORT and security work in IETF Security Area while liaising with organizations such as Internet Society, ISOC Chapters, APNIC, ARIN, LACNIC, and AFRINIC to align operational guidance with deployment realities.

History and Formation

The working group emerged in the 2010s from operational discussions at venues including IETF meetings, IETF 83, IETF 84, and operator gatherings such as DNS-OARC Workshop and RIPE Meetings. Key drivers included operational challenges posed by protocol extensions like DNSSEC deployment, EDNS options, and transport developments such as DNS over HTTPS and DNS over TLS. Early contributors and conveners drew from organizations like ICANN staff, academic groups at ICSI and University of California, Berkeley, and commercial operators including Verisign and Akamai.

Scope and Charter

The charter mandates work in areas including operational guidance, best current practices, and interoperability for topics such as DNSSEC, zone management for registrys and registrars, resolver behavior, caching, privacy-preserving transports, and operational responses to incidents involving Distributed Denial of Service attacks and cache poisoning. The charter requires liaison with groups such as IESG, IESG-appointed contacts, IAB, ICANN policy teams, and standards efforts like RFC editing and coordination with IETF Area Directors.

Key Projects and Documents

Major outputs include best current practice documents and informational RFCs on subjects like DNSSEC operational guidance, recommendations for ANY and AXFR usage, guidance for EDNS buffer sizes, and documents addressing TLS usage for DNS transports such as DoT and DoH. The group has produced work that intersects with foundational RFCs authored by figures and groups associated with Paul Vixie-era projects, ISC operations, and operator contributions from NTT and Verisign. Collaborative publications reference operational incidents such as large-scale DDoS events attributed in analyses involving Mirai botnet and related mitigations involving BGP-level coordination with Network Operator Groups.

Working Group Processes and Operations

The working group follows IETF procedures for consensus, using mailing lists, IETF meeting sessions, and designated co-chairs to shepherd drafts through IETF last call and IESG review. It uses tools and practices familiar to IETF Working Groupes: Internet-Drafts, RFC publication, and public archives, and engages in outreach at convenings like ICANN Meetings, ENOG, MENOG, and Cloudflare-hosted operator events. Decisions are informed by implementation experience from operators at APNIC Labs and research reported at conferences such as USENIX, ACM SIGCOMM, and IEEE INFOCOM.

Participants and Membership

Participants include network operators, registry and registrar engineers, academics, and vendor representatives from organizations such as Verisign, Akamai Technologies, Cloudflare, Google LLC, Microsoft Corporation, ISC (Internet Systems Consortium), NLnet Labs, Farsight Security, and regional forums like RIPE NCC and APNIC. Individual contributors have included authors and implementers with prior involvement in standards such as RFC 1034, RFC 1035, and later operational RFCs. Open participation follows IETF norms: any interested party may join mailing list discussions and attend sessions at IETF Meetings.

Impact and Adoption

Guidance from the working group has influenced operational practice at critical Internet infrastructure operators including root zone operators, registry operators managing gTLD and ccTLD zones, public DNS resolver deployments such as Google Public DNS and Cloudflare DNS, and enterprise implementations by vendors like Cisco Systems and Juniper Networks. Its recommendations have been cited in operational playbooks used during incidents involving Mirai botnet-driven DDoS attacks, large-scale BGP routing incidents, and in the adoption of privacy-enhancing transports such as DNS over HTTPS by browser vendors including Mozilla Foundation and Google Chrome teams. The group's outputs continue to guide interoperability among standards developed by IETF and policy considerations discussed at ICANN and operator communities such as NOGs.

Category:Internet Engineering Task Force