About two months ago, I got together with some fellow DNS engineers and sent a letter to the U. S. Senate explaining once again why the mandated DNS filtering requirements of S. 968 ("PIPA") were technically unworkable. This letter was an updated reminder of the issues we had previously covered in our earlier white paper on the same subject.
In the time since then, the U. S. House of Representatives has issued their companion bill, H. R. 3261 ("SOPA") and all indications are that they will begin "markup" on this bill some time next week. SOPA contains a DNS filtering mandate similar to PIPA's, and our arguments about the technical unworkability of PIPA are entirely accurate about the technical flaws in SOPA. We've also heard rumours of a possible "compromise" whereby Congress may be willing to water down these bills and require that DNS lookups for infringing web sites are simply not answered, as if that would be somehow better than answering with a pointer to a government warning page.
This is not a compromise, and would not work anyway. Today we're sending a letter to the chairmen, members, and staffs of the committees in the House and Senate who are trying to figure out how to re-engineer the DNS to protect brands and intellectual property from online infringement. The simple fact is, DNS doesn't work the way Congress needs it to work, and mandated interception in any form will not make it so.
In other news, I participated in a panel at Stanford University's law school the other night, topic: "What's Wrong With SOPA?". While we had no SOPA proponents on the panel itself, we had plenty in the audience, as the Q&A will show. The video is here. And if you missed the webinar last month where we discussed the dangers of PIPA (and SOPA) with some ISP's, the audio is here.
|Data Center||Policy & Regulation|
|DNS Security||Regional Registries|
|Domain Names||Registry Services|
|Intellectual Property||Top-Level Domains|
|Internet of Things||Web|
|Internet Protocol||White Space|
Afilias - Mobile & Web Services