Welcome:
Login
|
Sign Up
|
About CircleID
Follow:
|
|
|
So my prediction from last year that "ICANN will open the new gTLD application period without any glitches" could not have been more wrong. And yes - I actually used the word 'glitches'... Regardless of my crystal-ball gazing skills, it's been another incredibly eventful year, and below are the Top 10 Domain Stories from 2012.
At his first meeting as CEO of ICANN, Fadi Chehade showed up ready to work AND to listen. ICANN's new CEO described his objectives for the organization which included 1) affirmation of purpose, 2) operational excellence, 3) internationalization, and 4) evolution of the multi-stakeholder model on which ICANN is built. He also described significant organizational changes to ICANN leadership and staff...
ICANN is clearly changing with the new CEO making immediate changes to the organizational structure and Compliance announcing a number more effective tools and procedures at Sunday's At-Large Advisory Committee (ALAC) and Regional Leadership Meetings. It seems very ambitious and they will need to be because our year-long research, publicly distributed here for the first time, shows a complete breakdown in ICANN's Compliance functions on every level possible.
In response to a letter from ICANN's Noncommercial Users Constituency (NCUC) to data protection authorities concerning overreaching requests of law enforcement agencies in ICANN's ongoing Registrar Accreditation Agreement negotiations, the Article 29 Data Protection Working Party has written the ICANN Board.
Question: why has air travel become so painful? Because the threat posed by bad actors requires making everyone jump through hoops before letting them board a plane. To the point that, despite obvious requirements to ensure air safety, some are now openly questioning if the cure is not worse than the disease. Registering a domain name could be about to go the same way.
With all the recent attention to WHOIS, it's time for a confession: I'm somewhat guilty for the infamous WHOIS Data Reminder Policy. With hindsight, it's a bad policy, and it needs to die. The year was 2002. ICANN's DNSO (soon to be renamed as the GNSO) had a WHOIS Task Force, and was trying to extract policy choices from an ill-conceived and worse-executed survey of assorted self-selected stakeholders.
ICANN Compliance now has two conflicting answers on record concerning the enforceability of RAA 378 on WHOIS inaccuracy. This is a topic of extreme importance and one we are trying to get to the bottom of. ...inconsistency needs to be resolved as it directly impacts the current RAA negotiations and certainly before new gTLDs are deployed.
Declan McCullagh recently opined that the "FBI [and the] DEA warn [that] IPv6 could shield criminals from police." His post was picked-up relatively widely in the past few days, with the headlines adding more hyperbole along the way. So just how real is this threat? Let's take a look.
We have posted our support of the WHOIS Policy Review Team Report with two important comments. First, on page 79 of the report it is confirmed that the RAA is unenforceable on WHOIS inaccuracy (we wrote about this while at the last ICANN meeting) because the language of RAA 3.7.8 has no enforcement provision. It is now time for ICANN to confirm this problem officially.
The same thing happens before every ICANN meeting. It starts raining. Not men, as the song goes, or droplets of H2O. It starts raining documents. In the run-up to one of its three-a-year international meetings, ICANN goes into hyperdrive. And this time, days before the Prague meeting (from the 24th to the 29th), the usual downpour has turned into a veritable deluge. Let's just take June 4th as an example.
A World-Renowned Source for Internet Developments. Serving Since 2002.