The leaked Trans Pacific Partnership intellectual property chapter has revealed a number of U.S. proposals including U.S. demands for Internet provider liability that could lead to subscriber termination, content blocking, and ISP monitoring, copyright term extension and anti-counterfeiting provisions. This post discusses Article QQ.C.12 on domain names.
In a very casual and low-key footnote over the weekend, ICANN announced it would be further bypassing the Affirmation of Commitments and ignoring the WHOIS Review Team Report. There will be no enhanced validation or verification of WHOIS because unidentified people citing unknown statistics have said it would be too expensive... As a topic which has burned untold hours of community debate and development, the vague minimalist statement dismisses every ounce of work put in by stakeholders.
ICANN has opened the Generic Names Supporting Organization (GNSO) Whois study on privacy/proxy abuse for public comment. Performed by the National Physical Laboratory (NPL), this study is one of many commissioned by the GNSO to examine the current, disparate, and often maligned registration directory service, and aims to measure the hypothesis that "a significant percentage of the domain names used to conduct illegal or harmful Internet activities are registered via privacy and proxy services to obscure the perpetrator's identity."
In spite of the material we were presented with in Durban something has gone very wrong inside of ICANN Compliance. KnujOn has published a report which demonstrates that ICANN Compliance appears to completely collapse between September 2012 and December 2012. Following December 2012, ICANN seems to stop responding to or processing any complaints. It is around this time certain compliance employees start disappearing. This was not limited to the Sydney office as some would have us believe...
The IETF WEIRDS working group is defining a follow-on to WHOIS. Since this is the IETF, it's working on the technical issues about which it can deal with, not policy which is up to ICANN and the country registries. Somewhat to my surprise, the group is making steady progress. We've agreed that the basic model is RESTful, with queries via http, and responses as JSON data structures. The protocol is named RDAP for Registration Data Access Protocol, or maybe RESTful Data Access protocol.
With all the focus in the TLD world on the imminent arrival of more than a thousand new TLDs and the still unfinished discussions within ICANN on what policy framework those TLDs will need to follow, it is often forgotten that there are hundreds of other TLD policy frameworks that are mature, stable and well tested. These of course are the ccTLD policy frameworks that have been actively developed over 20 years.
As some readers probably know, I spend quite a bit of my time working on Internet policy related matters. Some of it may appear incredibly boring, but it matters. (If you really want me to explain why it matters I'd be happy to do so!) Since earlier this year I've been part of a small team of people drawn from the four corners of the globe and asked to re-examine "whois".
It's safe to say that with just a week to go before ICANN intended to sign the first contract for a new gTLD, the last thing anyone wanted was a 12-page document from the world's governments with 16 new "safeguards", six of which it wants to see applied to every new extension. But what the industry shouldn't overlook, especially in the face of the expected critical responses this week and next, is that the Governmental Advisory Committee's (GAC's) formal advice from the ICANN Beijing meeting represents an opportunity for the domain name industry to lock-in self-regulation at a critical point in its evolution.
There are two Bills that are floating through the corridors of power on the Hill that could potentially change the course of civil and political rights within the United States and the world. One was introduced through the House of Representatives and the other through the Senate. The two Bills touch on a common thread that are premised on "national security" however there are interesting challenges that will surface should the Bills be passed that affect global public interest that require further examination, introspection and discussion.
It is just another phishing case. Why should I care? I happened to receive my own copy of the phishing email message. Most Internet users will just smile bitterly before deleting it. I checked it to see why it had gone through the spam filters. It had no URL in the text but a reply-to address. So it needed a valid domain name, and had one: postfinances.com. PostFinance (without trailing "s") is the payment system of the Swiss Post. It has millions of users.
A World-Renowned Source for Internet Developments. Serving Since 2002.