Recently, I have been reporting on a highly questionable auction scheme for a single domain name, o.com, which is currently being improperly warehoused by ICANN along with a number of other .com and .net domain names. This violates ICANN's Bylaws -- but, so what?
Verisign recently informed ICANN that it had received a letter from the National Institute for Standards and Technology (NIST), an agency of the U.S. Department of Commerce, regarding the proposed auction of o.com described in the Second Amendment to the .com Registry Agreement agreed to by ICANN and Verisign in March 2019. This letter, which doesn't appear to be on official letterhead, is from a NIST Grants Officer and purports to overturn a letter raising objections to the auction...
During the two-year period preceding the IANA transition in 2016, there was a near-superhuman effort put forth by the community of stakeholders to design, debate, and deploy an accountability framework for ICANN that would serve to check and balance the coordinator of the global DNS. One of the overriding concerns that stakeholders sought to address was the possibility of ICANN being captured, and it was argued that the global community of stakeholders would serve as a "backstop" that would hold ICANN accountable.
Public Interest Registry (PIR) announced the creation of the DNS Abuse Institute about two months ago as it believes that "every .ORG makes the world a better place" and "anything that gets in the way of that is a threat," notably in the form of Domain Name System (DNS) abuse. To show support for the initiative, WhoisXML API analyzed monthly typosquatting data feeds for December 2020, January 2021, and February 2021 to identify .ORG domain trends...
In a recent article, Is ICANN Staff Misleading the Board Into Violating Obligations to the U.S. Government, I wrote: The referenced Memorandum of Understanding (MOU) is the vehicle by which the U.S. government delegates to ICANN the responsibilities for overseeing the technical management of the Internet's Domain Name System (DNS)... This is important for many reasons, and much remains to be analyzed for additional context that can help expose the rot at the Internet's root.
Recently, I had time to reflect on various matters after the alternator in my vehicle decided that the middle of a mountain pass was the appropriate time and place to go to that great big pick-and-pull scrapyard in the sky while leaving me stranded with no cell signal on the side of the road in the middle of nowhere. Until that point, I had been seriously considering applying to ICANN's Nominating Committee for one of the three open seats on ICANN's Board of Directors.
Back in 2014, to foster innovation and to better the choice in domain names, ICANN introduced new generic top-level domains through its New gTLD Program. It was a monumental move that enabled businesses, individuals, and communities across the globe to mark their presence on the Internet. Allowing users to be present digitally in their chosen language (non-ASCII characters and scripts) gave opportunities to local businesses, civil societies, and governments to better serve their communities.
Most of the single-character .com labels were initially registered in 1993 by Dr. Jon Postel while performing work pursuant to a contract with, and funded by, the U.S. government and are currently assigned to a "shell registrar" created and controlled by ICANN. This shell - which is the 376th entry on ICANN's list of accredited registrars - is misleadingly identified as the IANA registrar while being engaged in the illicit warehousing of domain names for speculative purposes.
On March 13, 2019, I published an article on CircleID, Portrait of a Single-Character Domain Name, that explored the proposed release and auction of o.com, a single-character .com domain name that was registered in 1993 and assigned to the Internet Assigned Numbers Authority (IANA) by Dr. Jon Postel. Although the National Telecommunications and Information Administration (NTIA) has since raised serious objections...
On 19 February 2020, ICANN announced that ICANN67 would be held via remote participation out of an abundance of caution associated with the COVID-19 outbreak. Little did we know at the time that twelve months later, ICANN meetings would still be held via remote participation. For a community that has been accustomed to meeting face-to-face at least three times a year since ICANN1 in Singapore in March 1999, this has created a tremendous challenge for how we conduct our business.