Welcome:
Login
|
Sign Up
|
About CircleID
Follow:
|
|
|
Domain Names |
Sponsored by |
|
Today a letter was submitted to the President of ICANN, Paul Twomey, at the ICANN Carthage meeting, "asking him to ensure that strong privacy safeguards, based on internationally accepted standards, are established for the WHOIS database." Latest reports indicated that the draft letter had been signed by about 50 nonprofit groups and represented 21 countries on six continents. "Signers of the letter included the American Library Association, the U.S. Association for Computing Machinery, the Australian Council for Civil Liberties, Electronic Frontier Finland, Privacy Ukraine, and the United Kingdom's Foundation for Information Policy Research." more
An article based on the most recent study for the European Commission on the Policy Implications of Convergence in the Field of Naming, Numbering and Addressing written by Joe McNamee and Tiina Satuli of Political Intelligence.
"With relation to the Internet and also IP addresses, the "scarcity" is more complicated: there are not only intellectual property issues with regards to domain names, but there is also an issue of managing the integrity of the system. For any naming or numbering system to work, it is essential that the names and addresses used cannot be confused with any other -- in other words, no one system can have two end-points with the same fully qualified number or name..." more
Network Penetration conducted a survey at the start of 2003 to check the status of the UK's DNS infrastructure. The second scan of the year has just been completed and the results are much more positive. There are however still some serious holes in major areas...Here is a look at what was tested, the results, some sample zone transfers and recommendations. more
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? more
EDUCAUSE, the exclusive registry operator and registrar of .edu domain names under a Cooperative Agreement with the U.S. Department of Commerce, is preparing a mass purge of .edu domain names. The organization says it is part of the final phase in a year long project to improve the accuracy of the WHOIS database for the .edu space. more
After roughly 19 days of its introduction, VeriSign's Site Finder service was finally shutdown on October 4, 2003 following a "Formal Deadline" issued by ICANN (previously reported here). With the plug pulled, the Internet appears to be returning to its regular status ending a historic event that can be best described as a 'Hurricane' -- a Cyber-Hurricane. What follows is a collection of commentaries and questions raised around the Net in response to this event during and after the final hours of VeriSign's deadline... more
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...
more
In light of the recent events caused by VeriSign's release of Site Finder for .net and .com domain names, CircleID is carrying out a 'Site Finder Special Coverage' and asking all stakeholders (all individuals and organization that own domain names or provide services) to submit their comments 'in favor' or 'against' Site Finder. All comments gathered will be posted on CircleID and distributed to key members of industry. more
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. more
We Internet users, who either own domain names or have an interest in the domain name system, wish to object to the VeriSign's Site Finder system. We believe that the system: 1) Breaks technical standards, by rewriting the expected error codes to instead point to VeriSign's pay-per-click web directory, and threatens the security and stability of the Internet; 2) Breaks technical standards affecting email services, and other Internet systems... more
The ICANN At-Large Advisory Committee would like to bring to ICANN's attention concerns about VeriSign's surprising roll-out of the "SiteFinder" service for .com and .net. This practice raises grave technical concerns, as it de facto removes error diagnostics from the DNS protocol, and replaces them by an error handling method that is tailored for HTTP, which is just one of the many Internet protocols that make use of the DNS.
more
But even if the collateral damage is left out of the picture, the very idea behind SiteFinder is user-unfriendly, and that's the second half of the ALAC's note: SiteFinder is, ultimately, about short-cutting other error handling methods, and redirecting any users that enter non-existing domain names into a web browser to Verisign's own service, for commercial purposes. SiteFinder is designed so it becomes difficult to deploy superior error handling services that would compete with it -- because errors aren't flagged. more
I just discovered that VeriSign's SiteFinder Web site is leaking data submitted in Web forms to its marketing analysis partner, Omniture. Forms can easily contain personal information such as an email address. For the problem to occur, a Web form must use the GET method. This data spill problem occurs if a Web page anywhere on the Internet submits a Web form to an action URL with a misspelled or expired domain name. Because of VeriSign's recent controversial changes to the DNS system, this form data is submitted to the SiteFinder Web site. more
Applications and devices like cell phones, email, search engines, and automated programs handle the error messages differently; it would be naive for VeriSign to think only humans with browsers rely on DNS. When a user enters a non-exist domain name on their cell phone the DNS error message would prevent downloading. Now cell phones download VeriSign's SiteFinder webpage and Service Providers bill the cell phone user for that extra usage. SPAM prevention programs also rely on this error message to check to see if the domain is real. more
Want a sense of just how much traffic VeriSign is receiving from its SiteFinder service? Alexa, with its Alexa Toolbar and associated traffic tracking services, makes it easy to find out...Over the past three months, taken as a whole, VeriSign had traffic rank 1,559. But today its traffic rank is 19, meaning... more
A World-Renowned Source for Internet Developments. Serving Since 2002.