Domain Names |
Sponsored by |
|
Isn't security as important to discuss as .XSS? The DNS has become an abuse infrastructure, it is no longer just a functional infrastructure. It is not being used by malware, phishing and other Bad Things [TM], it facilitates them. Operational needs require the policy and governance folks to start taking notice. It's high time security got where it needs to be on the agenda, not just because it is important to consider security, but rather because lack of security controls made it a necessity. more
There is a current ongoing Internet emergency: a critical 0day vulnerability currently exploited in the wild threatens numerous desktop systems which are being compromised and turned into bots, and the domain names hosting it are a significant part of the reason why this attack has not yet been mitigated. This incident is currently being handled by several operational groups. This past February, I sent an email to the Reg-Ops (Registrar Operations) mailing list. The email, which is quoted below, states how DNS abuse (not the DNS infrastructure) is the biggest unmitigated current vulnerability in day-to-day Internet security operations, not to mention abuse. more
Many in the technical community attribute the rapid growth and spread of the Internet to innovation that took place at the "edge" of the network, while its "core" was left largely application neutral to provide a universal and predictable building block for innovation. It is this core neutrality that provides a basis for the security and stability of the Internet as a whole. And it is this same core neutrality that is critical to the continued spread of the Internet across the Digital Divide. Unfortunately, when the politics of censorship rather than solely technical concerns drive the coordination of these "core" Internet resources, it threatens the future security and stability of the Internet. This paper proposes a paradigm upon which all the governments of the world have equal access to these core Internet resources to empower them and their citizens with the rights acknowledged in the WSIS Declaration of Principles. more
Earlier in the Registerfly controversy, ICANN Vice President Paul Levins posted to the ICANN Blog: "ICANN is not a regulator. We rely mainly on contract law. We do not condone in any way whatsoever RegisterFly's business practice and behaviour." This is disingenuous. ICANN is the central link in a web of contracts that regulate the business of domain name allocation. ICANN has committed, as a public benefit corporation, to enforcing those contracts in the public interest. Domain name registrants, among others, rely on those contracts to establish a secure, stable environment for domain name registration and through that for online content location. more
The Internet Commerce Association sent this letter to ICANN yesterday in regard to the RegisterFly situation: "I am writing to you in my capacity as Counsel to the Internet Commerce Association (ICA), a non-profit trade association dedicated to promoting and protecting the rights of domain name (DN) owners... It has come to our attention that an ICANN-accredited registrar is in the midst of what appears to be a near-complete operational breakdown, and that its ongoing failure to carry out its responsibilities is causing substantial economic loss to tens of thousands of DN registrants in both the United States and multiple foreign jurisdictions." more
There is a definite advantage to knowing what users look for when typing in domain names that they think should work. This article from Government Computer News shows an excellent example in .gov. "600,000 visitors a year to FirstGov try to find the federal government's Web site by typing USA.gov into their browser", so they switched from firstgov.gov to usa.gov. It wasn't mentioned in the article, but firstgov.gov redirects automatically; this is more intelligence than I normally expect from US government web sites. more
A U.S.-led Task Force in ICANN's Governmental Advisory Committee (GAC) released version 3 of its "Whois Principles" in preparation for the ICANN meeting in Brazil, where it will be debated and finalized. European countries pushed back against U.S. Government efforts to stop ICANN from respecting privacy concerns in its handling of domain name registrant contact data... more
It was rather interesting to read this new agreement between the USDoC and ICANN talking about the mechanisms, methods and procedures necessary to effect the transition of Internet domain name and addressing system (DNS) to the private sector. What was more interesting though was to read in this very agreement the following: "...the Department continues to support the work of ICANN as the coordinator for the technical functions related to the management of the Internet DNS". OK, let's be honest! Technical? more
This is serious. I'm not joking. You can look it up. Morgan Stanley brought a UDRP action involving the domain name 'mymorganstaleyplatinum.com' against a registrant identified as "Meow ("Respondent"), Baroness Penelope Cat of Nash DCB, Ashbed Barn, Boraston Track, Tenbury Wells, Worcestershire WR15 8LQ, GB." The decision summarizes the response... more
What would it take for this upcoming meeting to be a success? I am a big believer in ICANN's core principles, and in the forum it provides for private self-governance of domain names and numbers. I think the ICANN model continues to have great potential as a form of governance. For this meeting to be a success for me, personally, I'd like to see those core principles made more visibly operational -- or at least see a start made on this effort. I'm putting a stake in the ground with these posts, and we'll see whether progress happens or not. more
Over at VoxPI, Alexandre Nappey reports that, a few days ago, the first French judicial decision over a .eu domain name was released -- or more specifically the first decision over an application for a .eu name. The two parties own a trademark "EUROSTAR". They agreed on the coexistence of their respective marks in September 2004. Both applied for the same name 'eurostar.eu', on the same day. more
For three years, I've been a member of ICANN's "Interim" At-Large Advisory Committee, ALAC. At this Vancouver meeting, for the first time, the ICANN Board met with us, and Bret captured it on mp3 for podcast. ALAC criticized ICANN's proposed settlement with VeriSign, and then spoke about the problems with the current structure for at-large participation. more
I've often said that ICANN regulates the business of buying and selling of domain names and that ICANN's claim that it coordinates technical matters to preserve the stability of DNS is a fantasy. Well I am proven wrong. ICANN has done something technical. ICANN has issued Guidelines for the Implementation of Internationalized Domain Names, Draft Version 2 [PDF] (pending approval by the ICANN board.) It's only four pages long, but those few pages contain a lot of significant material. more
A month ago, ICANN announced that it had a large set of proposed changes to its "Guidelines for the Implementation of Internationalized Domain Names". The original guidelines are fairly confusing and not widely deployed by the ccTLDs, so one would think that the proposed revisions would be clearer and more useful. No such luck. Instead of describing what the problems with the old guidelines were, the committee that put together the new proposal simply added a whole bunch more rules. more
The Measurement Factory and Infoblox have announced results of a survey of more than 1.3 million Internet-connected, authoritative domain name system (DNS) servers around the globe. The results of the survey indicate that as many as 84 percent of Internet name servers could be vulnerable to pharming attacks, and that many exhibit other security and deployment-related vulnerabilities. The surveys consisted of several queries directed at each of a large set of external DNS servers to estimate the number of systems deployed today and determine specific configuration details. more
A World-Renowned Source for Internet Developments. Serving Since 2002.