DNS |
Sponsored by |
Earlier this year, the Internet Engineering Task Force’s (IETF’s) Internet Engineering Steering Group (IESG) announced that several Proposed Standards related to the Registration Data Access Protocol (RDAP), including three that I co-authored, were being promoted to the prestigious designation of Internet Standard. Initially accepted as proposed standards six years ago, RFC 7480, RFC 7481, RFC 9082 and RFC 9083 now comprise the new Standard 95. RDAP allows users to access domain registration data and could one day replace its predecessor the WHOIS protocol.
The global internet, from the perspective of its billions of users, has often been envisioned as a cloud -- a shapeless structure that connects users to applications and to one another, with the internal details left up to the infrastructure operators inside. From the perspective of the infrastructure operators, however, the global internet is a network of networks. It's a complex set of connections among network operators, application platforms, content providers and other parties.
A substantial amount of DNS community discussion on the topic of DNS Abuse is focused on defining what is or is not DNS Abuse. The definition adopted by ICANN contracted parties, as well as the DNS Abuse Institute, is straightforward: DNS Abuse is malware, botnets, pharming, phishing, and spam where it's a vehicle for the preceding harms. There is, of course, some fuzziness on the margins, where technical harms are also using content.
Decentralization is exciting. Headline-grabbing, even. After all, in a world where frustration levels are sky-high and rising, it should not come as a shock that many individuals are willing to embrace what we might call "anti-system solutions." Decentralized solutions, in our case, which come with the ambitious promise of providing everything their centralized counterpart can provide but without centralized points of failure and regulations. In our previous article, we enumerated several advantages associated with decentralized domain names.
With solution providers such as Unstoppable Domains or Handshake, and blockchain technology-friendly browsers, such as Brave, that are more than happy to assist on the implementation front, decentralized alternatives to the traditional Domain Name System has been receiving more and more attention lately. Centralized vs. decentralized... what will it be?
In April, I published an article, The Multistakeholder Moment of Truth: Will Stakeholders Hold ICANN Accountable?, alerting stakeholders that ICANN is violating its legal agreements with the U.S. Government -- namely the InterNIC licensing agreement and merged Memorandum of Understanding. At that time, I warned that it is essential for stakeholders not to remain silent in the face of this transgression, "hoping that such behavior left unchecked will end of its own accord."
Technical management of the Internet was delegated to ICANN by the U.S. government because it was believed that the private sector would be more agile and responsive to the needs of globally distributed stakeholders. However, this optimism and the faith it has produced has proven to be misplaced since ICANN's multi-stakeholder governance continues falling far short of the basic expectations set when it was created.
During ICANN71, the Brand Registry Group (BRG) openly asked potential future applicants what ICANN can do to help prepare them for the next gTLD round. The answer was very clear - commit to opening the next round and provide as much information as possible early on. However, in recent correspondence to the BRG from ICANN Chair, Maarten Botterman, he emphasized that "significant work lies ahead of us: the 2012 Applicant Guidebook must be updated with more than 100 outputs...
A recent study carried out by Governance Primer on behalf of the Universal Acceptance Steering Group (UASG) identified trends in the acceptance of all domain names in software hosted at Github, the largest open-source repository globally. This research builds on top of previous efforts aimed at identifying the underlying issues that result in problems when different applications need to handle Internationalized Domain Names (IDNs) and new gTLDs, particularly when it comes to email addresses.
As we finished this article, the world was hit by another global outage by content delivery network (CDN) provider, Akamai, on June 17, 2021. The cause seems to be related to the lack of capacity to a certain "routing table" of their distributed denial of service (DDoS) mitigation. Although the technical analysis is not yet available, the central premise of this article also applies to this incident, and it serves as a timely testimony.