How Not To Do Internet Governance.

Alexander Svensson takes a look at the WSIS process, and notes that the ongoing Prepcom-3 is probably a good example of what internet governance in a government-led ICANN replacement could look like: Governments negotiate behind closed doors, larg…

Alexander Svensson takes a look at the WSIS process, and notes that the ongoing Prepcom-3 is probably a good example of what internet governance in a government-led ICANN replacement could look like: Governments negotiate behind closed doors, large parts of industry and civil society are permitted to wait on the hallway. That perspective doesn’t look terribly promising — unofficial reports coming in from prepcom-3 quite frankly sound a lot more bizarre than any ICANN meeting I’ve experienced so far.

Text: GNSO Council Resolution on Sitefinder

The GNSO Council’s resolution on Sitefinder, as adopted today with the votes of all constituencies, except the registries (who abstained), and the IPC (which didn’t attend) has just been posted by the GNSO Secretariat. Commentary from Karl Auerbac…

The GNSO Council’s resolution on Sitefinder, as adopted today with the votes of all constituencies, except the registries (who abstained), and the IPC (which didn’t attend) has just been posted by the GNSO Secretariat.Commentary from Karl Auerbach is here.

Notes from the GNSO Council.

On the Council’s agenda for today: Actions from the last meeting, i.e., WIPO2 committee, UDRP issue prioritization, number of representatives per constituency, new gTLDs; TLD wildcard entries; WHOIS steering group update; UDRP issue prioritization.

On the Council’s agenda for today: Actions from the last meeting, i.e., WIPO2 committee, UDRP issue prioritization, number of representatives per constituency, new gTLDs; TLD wildcard entries; WHOIS steering group update; UDRP issue prioritization.

A Bad Time for the Net?

Seems like we’re living in bad times for the open, end-to-end Internet. First, Verisign believes it is a smart idea to move error handling away from the network’s edges towards its center, and to limit it to a single application-level protocol. No…

Seems like we’re living in bad times for the open, end-to-end Internet.First, Verisign believes it is a smart idea to move error handling away from the network’s edges towards its center, and to limit it to a single application-level protocol. Now David Isenberg and Cory Doctorow point to a company named CloudShield. This company believes that the notion that the network should remain “dumb” and simply perform transport is outdated, and develops the tools to make that notion enforceable.

New .au WHOIS Policy

The new .au WHOIS policy (background materials) in a nutshell: The names and e-mail addresses of the registrant and the technical contact are the only personal data disclosed. There are restrictions on the number of queries that a user can send to…

The new .au WHOIS policy (background materials) in a nutshell: The names and e-mail addresses of the registrant and the technical contact are the only personal data disclosed. There are restrictions on the number of queries that a user can send to the WHOIS service. Law enforcement requests are dealt with on a case-by-case basis.

PIR: No wildcards in TLDs, please.

In a letter to ICANN, the Public Interest Registry supports a suspension of VeriSign DNS wildcard service, and commits not to implement such a service for .org. Some rather interesting remarks come close to the end of the letter: We are informed t…

In a letter to ICANN, the Public Interest Registry supports a suspension of VeriSign DNS wildcard service, and commits not to implement such a service for .org.Some rather interesting remarks come close to the end of the letter: We are informed that other domain registries may be exploring services similar to the VeriSign Site Finder. … If this is the case, our comments concerning Site Finder apply with equal force to those other services. … Therefore, we urge ICANN to take whatever remedial action is needed to remove all “wildcard” DNS systems, including VeriSign’s Site Finder, from the DNS. Such action, emphasizing the central responsibility of all service providers, would be an important step in preserving the openness and accessibility of the Internet.It will be interesting to see what position the gTLD registry constituency’s representatives on the GNSO Council will take tomorrow.

SECSAC to Verisign: Stop this.

ICANN’s Security and Stability Advisory Committee has issued some recommendations on sitefinder: Recognizing the concerns about the wildcard service, we call on VeriSign to voluntarily suspend the service and participate in the various review proc…

ICANN’s Security and Stability Advisory Committee has issued some recommendations on sitefinder: Recognizing the concerns about the wildcard service, we call on VeriSign to voluntarily suspend the service and participate in the various review processes now underway. We call on ICANN to examine the procedures for changes in service, including provisions to protect users from abrupt changes in service.Also, the committee is soliciting input on practical security and stability implications, to be sent to secsac-comments@icann.org.