IETF merges DNS provisioning and registration working groups for improved efficiency

The migration of domain registration and DNS provisioning to the Operations Area reflects a shift toward programmatic, automated infrastructure management over manual configuration. For streaming providers and CDNs, this transition reduces the friction of managing global customer zones while improving the security of registration data via RDAP’s structured JSON format. Standardizing Domain Connect specifically addresses the complexity of multi-tenant service discovery, potentially lowering operational overhead for large-scale video delivery networks. Watch for the official publication of the Domain Connect Standards Track RFC, expected between December 2026 and March 2027.

The transition to the Registration Data Access Protocol (RDAP) reached a major milestone in early 2025 when ICANN officially removed the requirement for generic top-level domains (gTLDs) to support the legacy WHOIS port-43 service. Per IETF tracking and ICANN reports from July 2026, RDAP query volumes surpassed WHOIS for the first time in June 2025, with monthly RDAP traffic growing from 7 billion to over 65 billion queries in just seven months. This shift is critical as approximately 85% of gTLD registrations are now serviced by RDAP endpoints, though country-code TLDs (ccTLDs) like .de and .jp remain at roughly 40% adoption as they are not contractually mandated to upgrade.

Technically, the move toward RESTful paradigms is accelerating. In April 2026, the IETF created the RESTful Provisioning Protocol (RPP) working group to develop a JSON-based alternative to the XML-heavy Extensible Provisioning Protocol (EPP). While EPP remains the global standard for machine-to-machine domain management, the new REGEXT initiatives to enable EPP over HTTPS and QUIC reflect an industry-wide effort to align core infrastructure with modern web transport standards. These updates aim to improve the reliability of domain intelligence and threat analysis pipelines by providing machine-readable, authenticated data that the unencrypted WHOIS protocol could not support.

Simultaneously, the Domain Connect protocol, originally developed by GoDaddy in 2016, is moving toward finalized standardization to solve the 'DNS discovery' problem. According to reporting from ICANN and IETF developers in 2026, the protocol has gained traction with major platform providers including Microsoft and Cloudflare. The current focus remains on ensuring backward compatibility for the existing installed base while introducing asynchronous workflows via OAuth to facilitate continuous, authorized DNS revalidation without requiring manual user intervention.