ICANN's Security and Stability Advisory Committee (SECSAC) recently released some recommendations regarding the DNS infrastructure, specifying among other things, that sub-zone delegation be kept up-to-date. ...The SECSAC report doesn't mention, but I believe is trying to address, is the alarming fact that nearly 10% of the name servers listed in the root zone are lame, either they aren't authoritative for the zones they are supposed to be, or they are unreachable much of the time.
The Council of European National Top-Level Domain Registries (CENTR) announced today their response to Professor Michael Geist's draft survey report "Government and country-code top level Domains: A global survey", which was conducted on behalf of the International Telecommunication Union (ITU) in December 2003. "In the last decade the general trend has been to de-regulate markets in the Communications Industry, which continues to stimulate economic growth and innovation, and it seems perverse that this ITU supported report is seeking to go against the proven successful trend," said Paul Kane, chairman of CENTR.
On November 4, 2003, VeriSign announced a new "trust enhancing" seal which they built using Macromedia's Flash technology...While there are problems inherent to VeriSign's approach that call into question their understanding of "The Value of Trust," there are ways they could have made this particular implementation less trivially spoofable. The flaws I demonstrate on this page are flaws in the concept and the execution rather than anything inherently flawed in Flash. Overall this kind of graphical "trustmark" is extremely easy to forge just by recreating the artwork. But in this case, you don't even have to do that. The seal can still be called directly off the VeriSign servers, yet it is easily modified, without recreating artwork, and without doing anything untoward with VeriSign's servers!
In a Message from RegistryPro Advisory Board to Tina Dam on 24 October 2003, it is noted that .Pro is, again, asking ICANN to allow for the registration of 2nd level domains. I am, again, of mixed opinion on this. On the one hand, a registry should be able to do what it wants, within reason. This clearly falls into that category. On the other hand, .Pro has been denied once already on the grounds that registering 2nd level domains is not the proposal upon which they were approved in the "testbed" procedure of November 2000.
CircleID recently interview Paul Vixie, Founder & Chairman of Internet Software Consortium (ISC), to discuss ISC's newly formed Operations, Analysis, and Research Center (OARC). OARC is launched in response to DDoS attacks at the Internet's core infrastructure and the vital requirement for a formal coordination system. OARC is also a part of US homeland security initiatives, such as the formation of Information Sharing and Analysis Centers (ISACs).
"Registries and registrars, ccTLD operators, large corporate NOCs, ISPs and ecommerce companies that host many domain names are all likely candidates. This is also a natural for law enforcement groups that are worried about attacks on the Internet."
On October 16, 2003, VeriSign announced the sale of its Network Solutions (NSI) business unit three years after its purchase from SAIC. This is a report on the historical snapshot of Network Solutions and a collection of commentaries made in response to this event...Network Solutions, Inc. was founded by Emmit J. McHenry as a joint venture with the National Science Foundation and AT&T...
There is a worldwide interest in the extension of the namespace to include new Top-Level Domains (TLDs) and select new registries to run them. If these New TLDs are to be selected objectively, and without partisan favours to insiders, then there is a clear need for criteria and careful evaluation of lessons gained from previous TLD launches. This was the principle behind the "Proof of Concept" approach, promised by ICANN, and yet ICANN appears to have retreated to a lightweight in-house evaluation, carried out obscurely, in the hands of selected individual under a 6-month contract 4 months ago. What have we learned about Sunrise, about Landrush, about abuse of process, about implementation and enforcement of agreements, about registrars who game the system to warehouse names for themselves, about proposed marketing budgets which evaporate into thin air?
ICANN today has made a formal demand stating: "Given the magnitude of the issues that have been raised, and their potential impact on the security and stability of the Internet, the DNS and the .com and .net top level domains, VeriSign must suspend the changes to the .com and .net top-level domains introduced on 15 September 2003 by 6:00 PM PDT on 4 October 2003. Failure to comply with this demand by that time will leave ICANN with no choice but to seek promptly to enforce VeriSign's contractual obligations." What follows is a collection of commentaries made around the net and by experts in response to today's announcement...
Attention so far has been focusing on the ethics of the move (positively satanic), its effects on DNS and non-Web applications (Considered Harmful), and on possible technical responses (Software Aimed at Blocking VeriSign's Search Program). On the legal side of the fence, though, we're not just talking about a can of worms. We're talking about an oil drum of Arcturan Flesh-Eating Tapeworms.
A third lawsuit has been filed late Friday in a federal district court in California against VeriSign, Inc. over its controversial DNS wildcard redirection service known as SiteFinder. It was filed by the longtime Internet litigator Ira Rothken. In addition, while two other lawsuits have been filed by Go Daddy Software, Inc. and Popular Enterprises, LLC. in Arizona and Florida, this is the first lawsuit to seek class-action status. Here is an excerpt from the "Introduction" section of this class-action lawsuit...