<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Domain Name Rights Coalition</title>
    <link rel="alternate" type="text/html" href="http://www.netpolicy.com/dnrc/" />
    <link rel="self" type="application/atom+xml" href="http://www.netpolicy.com/dnrc/atom.xml" />
   <id>tag:www.netpolicy.com,2008:/dnrc//7</id>
    <link rel="service.post" type="application/atom+xml" href="http://www.webmongers.com/mt/mt-atom.cgi/weblog/blog_id=7" title="Domain Name Rights Coalition" />
    <updated>2008-06-27T17:07:42Z</updated>
    <subtitle>For Freedom on the Internet</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 3.2</generator>
 
<entry>
    <title>ICANN Takes First Step to Becoming a Global Content Regulator</title>
    <link rel="alternate" type="text/html" href="http://www.netpolicy.com/archives/004131.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webmongers.com/mt/mt-atom.cgi/weblog/blog_id=7/entry_id=4131" title="ICANN Takes First Step to Becoming a Global Content Regulator" />
    <id>tag:www.netpolicy.com,2008:/dnrc//7.4131</id>
    
    <published>2008-06-27T17:07:36Z</published>
    <updated>2008-06-27T17:07:42Z</updated>
    
    <summary>ICANN Takes First Step to Becoming a Global Content Regulator: There has been wide coverage of ICANN&apos;s decision this week to adopt a new process for creating new global Top Level Domains (gTLDs). Publishing a clear, transparent and objective process...</summary>
    <author>
        <name>mikki</name>
        
    </author>
            <category term="ICANN" />
    
    <content type="html" xml:lang="en" xml:base="http://www.netpolicy.com/dnrc/">
        <![CDATA[<p><a href="http://www.circleid.com/posts/print/86278_icann_global_content_regulator/">ICANN Takes First Step to Becoming a Global Content Regulator</a>:<br />
<br /><br />
There has been wide coverage of ICANN's decision this week to adopt a new process for creating new global Top Level Domains (gTLDs). Publishing a clear, transparent and objective process is thought likely to result in a considerable expansion of gTLDs—although nobody really knows whether this means "quite a lot" or "many thousands”.<br />The decision endorses a 2007 report from GNSO Council, an ICANN structure that makes recommendations to the ICANN Board on gTLD policy.<br />Less attention has been given to one of the new tests ICANN will use when considering whether to approve a new gTLD, contained in GNSO's sixth recommendation:<br />Strings [meaning, new top level domain names] must not be contrary to generally accepted legal norms relating to morality and public order that are recognized under international principles of law.<br />The report goes on to amplify on what it means by "generally accepted legal norms relating to morality and public order":<br />Examples of such principles of law include, but are not limited to, the Universal Declaration of Human Rights (UDHR), the International Covenant on Civil and Political Rights (ICCPR), the Convention on the Elimination of All Forms of Discrimination Against Women (CEDAW) and the International Convention on the Elimination of All Forms of Racial Discrimination, intellectual property treaties administered by the World Intellectual Property Organisation (WIPO) and the WTO Agreement on Trade-Related Aspects of Intellectual Property (TRIPS).<br />Quite why intellectual property is included as an issue of "morality and public order" alongside the Universal Declaration of Human Rights isn't explained, and probably owes more to the lobbying power of the American music and film industry associations than anything else. That aside, not everybody is comfortable with ICANN making decisions on "morality and public order".<br />ICANN Board member Wendy Seltzer speaking for the At-Large Community (ALAC), that represents ordinary end users, commented:<br />[ALAC] expressed concern that putting these criteria into the gTLD approval process, even as opportunities for objection, injects ICANN into the business of making morality and public order decisions, or injects that into ICANN's processes in a way that, as ALAC put it, debases the ICANN process. And at-large does not want to see ICANN put into the business of adjudicating or even delegating the adjudication of morality or public order or community support. And so we hope that in implementation, these criteria can be kept sufficiently narrow so that they are both administrable and understandable and so that they do not involve ICANN, the organization, in making, or allowing to be made, determinations about any claim to generally accepted morality principles.<br />ICANN Board member Professor Susan Crawford agreed, going on to say:<br />[N]either national governments acting as sovereigns nor intergovernmental organizations acting as representatives of governments should participate in management of Internet names and addresses.<br />[...]<br />This wasn't done out of enthusiasm for the free market alone. The idea was also to avoid having sovereigns use the Domain Name System for their own content, control, desires. To avoid having the Domain Name System used as a choke point for content. Recommendation 6, which is the morality and public order recommendation, represents quite a sea change in this approach, because the recommendation is that strings must not be contrary to generally acceptable legal norms relating to morality and public order that are recognized under international principles of law. That's the language of the recommendation.<br />Now, if this is broadly implemented, this recommendation would allow for any government to effectively veto a string that made it uncomfortable. Having a government veto strings is not allowing the private sector to lead. It's allowing sovereigns to censor.<br />In the formal discussions, these issues are mainly debated in the abstract, but two key examples are bandied about in private: .jihad (which even the anti-censorship USA seems keen to prohibit) and .nazi (which is an example dear to the hearts of some European governments with strict anti-Nazi laws).<br />Civil libertarians supporting Susan Crawford's line argue that if governments are able to pressure ICANN into prohibiting .jihad (which has perfectly non-violent meanings in Islam as well as the terrorist connotations it has recently acquired in the West), then can a prohibition on .falun-gong be far behind?<br />Traditionalists among the Internet technical community might be less impressed with the cry to protect freedom of expression in top level domains, arguing that domain names—let alone top level domain names—are intended as identifiers in an addressing scheme, not as a medium of expression at all. However, even on this analysis there is cause for concern about the "morality string criterion"<br />Is it possible for a short phrase such as would be valid as a top level domain name to constitute an incitement to violence, or other generally accepted breach of public order, in and of itself? Does it not depend on how the domain is used? Does the objection to .nazi lie not so much in its identification of content that might relate to Nazi ideology and in history, but that it might be used by people sympathetic to the ideology?<br />Whether or not it is possible for a domain to inherently infringe principles of morality and public order, doesn't such a rule invite ICANN to investigate how such a domain might be used in any case? Surely it is inconceivable that ICANN would not consider the likely use of a domain. Is such an invitation a good idea? Do we really think ICANN is well equipped to perform this role?<br />If we accept that ICANN should consider the likely use of a top level domain, and weigh that against principles of morality and public order—not to mention intellectual property law—before deciding whether such a domain should exist, why should it stop there? Why shouldn't ICANN require the registries of gTLDs (including .com) to do the same at the second level? ICANN can impose terms on such registries by contract; the only thing that restrains it is a view that this is not ICANN's proper role or purpose. If we accept the principle that ICANN can adjudicate globally "generally accepted legal norms relating to morality and public order", why not require gTLD registries to enforce these principles at the second level? And why stop with new domains: wouldn't actual proof of "infringing" use be even more damning than speculation about how a new domain might be used in the future?<br />The string criteria debate may attract less attention than the creation of new TLDs, and may not immediately affect as many people as the introduction of Internationalised Domain Names. Nonetheless, history may yet come to view this as the watershed moment when the world first acquired a global Internet content regulator.<br />This article was cross-posted from the LINX Public Affairs blog<br />
<br /></p>]]>
        
    </content>
</entry>
<entry>
    <title>Launch of .PARIS - Circle ID</title>
    <link rel="alternate" type="text/html" href="http://www.netpolicy.com/archives/004123.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webmongers.com/mt/mt-atom.cgi/weblog/blog_id=7/entry_id=4123" title="Launch of .PARIS - Circle ID" />
    <id>tag:www.netpolicy.com,2008:/dnrc//7.4123</id>
    
    <published>2008-06-27T15:05:39Z</published>
    <updated>2008-06-27T15:05:53Z</updated>
    
    <summary>Launch of .PARIS: Yesterday, hundreds of sweaty ICANN attendees put on their best clothes and braved the crush of the rush hour metro on a very hot day to crush together for the ICANN gala at the overwrought Hotel de...</summary>
    <author>
        <name>mikki</name>
        
    </author>
            <category term="ICANN" />
    
    <content type="html" xml:lang="en" xml:base="http://www.netpolicy.com/dnrc/">
        <![CDATA[<p><a href="http://www.circleid.com/posts/86262_launch_of_paris_domain_icann/">Launch of .PARIS</a>:<br />
<br /><br />
Yesterday, hundreds of sweaty ICANN attendees put on their best clothes and braved the crush of the rush hour metro on a very hot day to crush together for the ICANN gala at the overwrought Hotel de Ville (city hall) in Paris.<br />Most of them missed an interesting announcement.<br />I arrived an hour late, but even so food and drink were not yet served (not even water), and everyone was in desperate need of provisioning. The dull roar of heat-induced complaining drowned out the dignitaries making speeches at the far end of the hall.<br />Anyone who has been to an ICANN meeting knows that it's free to attend, and all the events are free as well.  If you're smart, you can get free food and booze most evenings, as well as nibbles during the coffee breaks (which makes up for the hotel bar prices: 12 Euros for two small bottles of Perrier, for example).  ICANN is right to always profusely thank the hosts for footing the bill, and the Paris meeting, sponsored by AFNIC (the French registration authority) and the Mairie de Paris (city of Paris), among others, did a very good job for the most part.<br />So it seems the height of ingratitude to jabber while various luminaries, barely audible, heaped fulsome praise on one another. But jabber they did, and most probably missed the announcement that the mayor's office was supporting the launch of .PARIS, headed by Sebastian Bachollet of ISOC France, which will have technical assistance from AFNIC. (AFNIC's position on TLDs under its sway is baffling, but more on that in a later article.)<br />The inhabitants of Paris consider themselves a breed apart from the other denizens of France, and in this Parisians exactly resemble New Yorkers, Berliners, Londoners, and other citizens of their country's most prominent city.  And, to my mind, that's the key to success for a geographically-based TLD—a feeling for the place (or language, or cultural identity) that makes people want to proudly display their affinity, and which will result in domain names that are actually used on the web, and not just filled up with annoying parking pages. <br />Congratulations .PARIS.<br />We will see many more…<br />
<br /></p>]]>
        
    </content>
</entry>
<entry>
    <title>An Open Access Success Story, Just in Time for CALI</title>
    <link rel="alternate" type="text/html" href="http://www.netpolicy.com/archives/004104.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webmongers.com/mt/mt-atom.cgi/weblog/blog_id=7/entry_id=4104" title="An Open Access Success Story, Just in Time for CALI" />
    <id>tag:www.netpolicy.com,2008:/dnrc//7.4104</id>
    
    <published>2008-06-18T20:21:32Z</published>
    <updated>2008-06-18T20:21:44Z</updated>
    
    <summary>An Open Access Success Story, Just in Time for CALI: I&amp;#8217;m traveling to Baltimore tomorrow, where I&amp;#8217;ll be speaking later this week at UMD, one of the few law schools that can claim to be older than my own. The...</summary>
    <author>
        <name>mikki</name>
        
    </author>
            <category term="Misc" />
    
    <content type="html" xml:lang="en" xml:base="http://www.netpolicy.com/dnrc/">
        <![CDATA[<p><a href="http://blogs.law.harvard.edu/infolaw/2008/06/17/an-open-access-success-story-just-in-time-for-cali/">An Open Access Success Story, Just in Time for CALI</a>:<br />
<br /><br />
<p>I&#8217;m traveling to <a href="http://en.wikipedia.org/wiki/Baltimore%2C_Maryland">Baltimore</a> tomorrow, where I&#8217;ll be speaking later this week at UMD, <a href="http://en.wikipedia.org/wiki/University_of_Maryland_School_of_Law">one of the few law schools</a> that can claim to be older than <a href="http://en.wikipedia.org/wiki/University_of_Cincinnati_College_of_Law">my own</a>. The occasion is this year&#8217;s <a href="http://www.cali.org/">CALI</a> <a href="http://www2.cali.org/index.php?fuseaction=conference.home">Conference for Law School Computing</a>, and I&#8217;ll be <a href="http://wiki.cali.org/calicon08/index.php?n=Sessions.412">delivering</a> an updated version of my talk on the open access movement.</p><br />
<p>As it turns out, I&#8217;ll also be delivering an unexpected bit of good news. The open-access project I <a href="http://blogs.law.harvard.edu/infolaw/2007/10/12/crowdsourcing-and-open-access/">blogged about here</a> last October has yielded some impressive results. The project involved scanning and proofreading the House Judiciary Committee&#8217;s Report on the landmark Copyright Act of 1976.  To my knowledge, the House Report has never been freely available online &mdash; a keenly felt omission, given how frequently United States courts in copyright cases rely on the Report as an aid to construction of the (frequently unilluminating) statutory text.</p><br />
<p>That problem has now been remedied.</p><br />
<p>Working in irregular bursts over the last eight months, volunteers at the English-language <a href="http://en.wikisource.org/wiki/Main_Page">Wikisource</a> project (a sister site of the much better known <a href="http://en.wikipedia.org/wiki/Main_Page">Wikipedia</a> encyclopedia) have proofread all 370 page scans from the original House report, and the results have been stitched together to form a single document: <strong><a href="http://en.wikisource.org/wiki/Copyright_Law_Revision_%28House_Report_No._94-1476%29">Copyright Law Revision (House Report No. 94-1476)</a></strong>. As the accompanying <a href="http://en.wikisource.org/wiki/Template:PageQuality">color-coded</a> chart <a href="http://en.wikisource.org/wiki/Index:H.R._Rep._No._94-1476">reveals</a>, most pages of the report have been proofread by at least two different users, and the rest should be finished within a few weeks if current trends continue.</p><br />
<p>Here are just a few reasons why the Wikisource version of the House Report is the best now available anywhere.</p><br />
<ul><br />
<li><strong>It&#8217;s free.</strong>  Like all U.S. government works, the text is in the <a href="http://www.altlaw.org/v1/codes/us/587561">public domain</a>.  And Wikisource, unlike proprietary database vendors, <a href="http://en.wikisource.org/wiki/Wikisource:Copyright">doesn&#8217;t purport to limit</a> your freedom to copy or reuse the public-domain texts that are hosted on the site.  If you look up the exact same report on <a href="http://en.wikipedia.org/wiki/Westlaw">Westlaw</a>, for instance, you&#8217;ll find this rather forbidding warning:<br /><br />
<blockquote><p>&copy;2008 Thomson/West. Copyright is not claimed as to any part of the original work prepared by a U.S. government officer or employee as part of that person&#8217;s official duties. All rights reserved. <strong>No part of a Westlaw transmission may be copied, downloaded, stored in a retrieval system, further transmitted, or otherwise reproduced, stored, disseminated, transferred, or used, in any form or by any means, except as permitted under the terms of the Subscriber Agreement wherein you obtained access or with prior written permission. Each reproduction of any part of a Westlaw transmission must contain notice of Thomson/West&#8217;s copyright.</strong> Westlaw, WIN, and KeyCite are trademarks registered in the U.S Patent and Trademark Office. WIN Natural Language is protected by U.S. Patent Nos. 5,265,065; 5,418,948; and 5,488,725.</p></blockquote><br />
<p>Where Thomson/West gets off telling me what I can and can&#8217;t do with information they don&#8217;t own is beyond me. By drawing the text of the House Report from the original U.S. Government publication, however, Wikisource&#8217;s version avoids entanglement with similarly overreaching proprietary claims.</li><br />
<li><strong>It&#8217;s complete.</strong> Other online versions of the Report, as well as most hard-copy reprints (<em>e.g.</em>, 1976 <a href="http://en.wikipedia.org/wiki/United_States_Code_Congressional_and_Administrative_News">U.S.C.C.A.N.</a> 5659), omit certain portions. Typically, they exclude the text of the legislation (pp. <a href="http://en.wikisource.org/wiki/Copyright_Law_Revision_%28House_Report_No._94-1476%29#p1">1</a>&#8211;<a href="http://en.wikisource.org/wiki/Copyright_Law_Revision_%28House_Report_No._94-1476%29#p46">46</a> of the Report) as well as an especially lengthy, complicated three-column table that offers a side-by-side comparison of (1) the version of the bill that passed the Senate in 1975, (2) the text of the House&#8217;s amended version, and (3) the corresponding provisions, if any, of the Copyright Act of 1909 (pp. <a href="http://en.wikisource.org/wiki/Copyright_Law_Revision_%28House_Report_No._94-1476%29#p186">186</a>&#8211;<a href="http://en.wikisource.org/wiki/Copyright_Law_Revision_%28House_Report_No._94-1476%29#p358">358</a> of the Report). Wikisource, in keeping with its general editorial philosophy, reproduces the complete text in its entirety; the site&#8217;s editors don&#8217;t substitute their own judgments about which portions of the document will be useful to you.</li><br />
<li><strong>It&#8217;s pinpoint-hyperlink-able</strong> (I&#8217;m sure I&#8217;m overlooking a more technologically correct way of saying that).  Did you spot those hyperlinks in the preceding paragraph? Mitigating the potential unwieldiness of posting a 370-page document as a single Web page is the fact that anchor elements are included to take you directly to any page within the document. So if you want to jump straight to <a href="http://en.wikisource.org/wiki/Copyright_Law_Revision_%28House_Report_No._94-1476%29#p65">the Committee&#8217;s discussion of fair use</a>, for example, you can.</li><br />
<li><strong>It&#8217;s (optionally) annotated.</strong> Wikisource reproduces original texts as published, warts and all. But the architecture of the site makes it easy to offer an alternative <a href="http://en.wikisource.org/wiki/Copyright_Law_Revision_%28House_Report_No._94-1476%29/Annotated">annotated version</a> of the text where errors are marked and corrections offered.</li><br />
</ul><br />
<p>Assisting with the creation of the online version of the House Report has been an educational experience, and I expect to have more to say about the pros and cons after my CALI talk. For now, though, I&#8217;m pleased just to report that an important and influential primary reference source in copyright law has, three decades after the fact, at last become freely available online.</p><br />
<br /></p>]]>
        
    </content>
</entry>
<entry>
    <title>ICM Registry, Applicant of the Proposed .XXX Domain, Files Independent Review Petition Against ICANN</title>
    <link rel="alternate" type="text/html" href="http://www.netpolicy.com/archives/004100.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webmongers.com/mt/mt-atom.cgi/weblog/blog_id=7/entry_id=4100" title="ICM Registry, Applicant of the Proposed .XXX Domain, Files Independent Review Petition Against ICANN" />
    <id>tag:www.netpolicy.com,2008:/dnrc//7.4100</id>
    
    <published>2008-06-18T17:42:01Z</published>
    <updated>2008-06-18T17:42:11Z</updated>
    
    <summary>ICM Registry, Applicant of the Proposed .XXX Domain, Files Independent Review Petition Against ICANN: In a public letter posted on ICM Registry&apos;s Website, Stuart Lawley, Chairman and President of the organization has announced that last week an independent review petition...</summary>
    <author>
        <name>mikki</name>
        
    </author>
            <category term="Domain Names" />
    
    <content type="html" xml:lang="en" xml:base="http://www.netpolicy.com/dnrc/">
        <![CDATA[<p><a href="http://www.circleid.com/posts/86179_icm_registry_xxx_domain_independent_review_icann/">ICM Registry, Applicant of the Proposed .XXX Domain, Files Independent Review Petition Against ICANN</a>:<br />
<br /><br />
In a public letter posted on ICM Registry's Website, Stuart Lawley, Chairman and President of the organization has announced that last week an independent review petition against ICANN was filed. In March 2007, ICM's application for a new .XXX Top-Level Domain (TLD) was rejected by ICANN after a three year long process costing ICM reportedly over US$ 4 million in total (<a href="http://www.circleid.com/main/search?domains=www.circleid.com&q=icm&sa.x=0&sa.y=0&sitesearch=&sitesearch=www.circleid.com&client=pub-1590470126833731&forid=1&ie=ISO-8859-1&oe=ISO-8859-1&safe=active&cof=GALT%3A%23666666%3BGL%3A1%3BDIV%3A%23E6E6E6%3BVLC%3A663366%3BAH%3Acenter%3BBGC%3AFFFFFF%3BLBGC%3A990000%3BALC%3A800000%3BLC%3A800000%3BT%3A000000%3BGFNT%3A003366%3BGIMP%3A003366%3BFORID%3A11&hl=en">view all related posting</a>). Following is the text from today's announcement... <a href="http://www.circleid.com/posts/86179_icm_registry_xxx_domain_independent_review_icann/">More...</a><br />
<br /></p>]]>
        
    </content>
</entry>
<entry>
    <title>FTC Halts Cross Border Domain Name Con Artists</title>
    <link rel="alternate" type="text/html" href="http://www.netpolicy.com/archives/004096.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webmongers.com/mt/mt-atom.cgi/weblog/blog_id=7/entry_id=4096" title="FTC Halts Cross Border Domain Name Con Artists" />
    <id>tag:www.netpolicy.com,2008:/dnrc//7.4096</id>
    
    <published>2008-06-18T17:39:37Z</published>
    <updated>2008-06-18T17:39:48Z</updated>
    
    <summary>FTC Halts Cross Border Domain Name Con Artists: A U.S. District Court Judge has ordered a halt to the illegal practices of Canadian operators who deceptively posed as domain name registrars and sent bogus bills to thousands of U.S. small...</summary>
    <author>
        <name>mikki</name>
        
    </author>
            <category term="Domain Names" />
    
    <content type="html" xml:lang="en" xml:base="http://www.netpolicy.com/dnrc/">
        <![CDATA[<p><a href="http://www.circleid.com/posts/ftc_halts_domain_name_con_artists/">FTC Halts Cross Border Domain Name Con Artists</a>:<br />
<br /><br />
A U.S. District Court Judge has ordered a halt to the illegal practices of Canadian operators who deceptively posed as domain name registrars and sent bogus bills to thousands of U.S. small businesses and nonprofit organizations for their annual "WEBSITE ADDRESS LISTING." Many of the businesses and nonprofits believed they would lose their domain names unless they paid the bill, so they paid. The Federal Trade Commission alleged that in most cases the defendants did not provide domain registration services, did not provide the "search optimization" services it claimed to provide, and bilked small businesses and nonprofits out of millions of dollars. <a href="http://www.circleid.com/posts/ftc_halts_domain_name_con_artists/">More...</a><br />
<br /></p>]]>
        
    </content>
</entry>
<entry>
    <title>CIRA Creates Backdoor WHOIS Exceptions for Police and IP Owners - Michael Geist</title>
    <link rel="alternate" type="text/html" href="http://www.netpolicy.com/archives/004091.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webmongers.com/mt/mt-atom.cgi/weblog/blog_id=7/entry_id=4091" title="CIRA Creates Backdoor WHOIS Exceptions for Police and IP Owners - Michael Geist" />
    <id>tag:www.netpolicy.com,2008:/dnrc//7.4091</id>
    
    <published>2008-06-11T15:51:09Z</published>
    <updated>2008-06-11T15:51:23Z</updated>
    
    <summary>CIRA Creates Backdoor WHOIS Exceptions for Police and IP Owners: Earlier this year, I wrote glowingly about the new CIRA whois policy, which took effect today and which I described as striking the right balance between access and privacy. The...</summary>
    <author>
        <name>mikki</name>
        
    </author>
            <category term="Domain Names" />
    
    <content type="html" xml:lang="en" xml:base="http://www.netpolicy.com/dnrc/">
        <![CDATA[<p><a href="http://www.circleid.com/posts/86103_cira_backdoor_whois_police/">CIRA Creates Backdoor WHOIS Exceptions for Police and IP Owners</a>:<br />
<br /><br />
Earlier this year, I wrote glowingly about the new CIRA whois policy, which took effect today and which I described as striking the right balance between access and privacy. The policy was to have provided new privacy protection to individual registrants — hundreds of thousands of Canadians — by removing the public disclosure of their personal contact information (though the information is collected and stored by domain name registrars).<br /><br />Apparently I spoke too soon. Faced with the prospect of a privacy balance, special interests representing law enforcement and trademark holders quietly pressured CIRA to create a backdoor that will enable these two groups (and these two groups alone) to have special access to registrant information. In the case of law enforcement, police can bring cases to CIRA involving immediate risk to children or the Internet (ie. denial-of-service attacks) and CIRA will hand over registrant information without court oversight. In the case of trademark holders (as well as copyright and patent owners), claims that a domain name infringes their rights will be enough to allow CIRA to again disclose registrant information.<br /><br />This represents a stunning about-face after years of public consultation on the whois policy. While the law enforcement exception appears to be narrowly tailored, the exception for trademark, copyright, and patent interests undermines a crucial part of the whois policy, namely compliance with Canadian privacy law (the policy now arguably violates the law) and the appropriate balance between privacy and access. For example, consider a Canadian that registers companysucks.ca (name your company) as a whistleblower site about a particular company. They understandably wish to remain anonymous to the general public since disclosure of their personal information could lead to negative repercussions. Under the new CIRA policy, if they use fake registrant information, they risk losing the domain. On the other hand, the backdoor exception means that the trademark holder can easily smoke out the identity of the registrant as CIRA will simply hand over this information.<br /><br />Just over six weeks ago, CIRA celebrated its one millionth domain name registration and claimed world class status. Today, the organization has betrayed the very principles of consultation upon which it was built and sent a discouraging message that special interests matter more its own members.<br />
<br /></p>]]>
        
    </content>
</entry>
<entry>
    <title>Domain Names Users vs Domain Names Registrants</title>
    <link rel="alternate" type="text/html" href="http://www.netpolicy.com/archives/004090.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webmongers.com/mt/mt-atom.cgi/weblog/blog_id=7/entry_id=4090" title="Domain Names Users vs Domain Names Registrants" />
    <id>tag:www.netpolicy.com,2008:/dnrc//7.4090</id>
    
    <published>2008-06-09T21:20:25Z</published>
    <updated>2008-06-09T21:20:38Z</updated>
    
    <summary>Domain Names Users vs Domain Names Registrants: Antony Van Couvering from names@work writes that ICANN&apos;s constituencies are a &quot;bad idea&quot;. While I am not sure to agree with him on the general principle, he makes some interesting remarks. Among others,...</summary>
    <author>
        <name>mikki</name>
        
    </author>
            <category term="Domain Names" />
    
    <content type="html" xml:lang="en" xml:base="http://www.netpolicy.com/dnrc/">
        <![CDATA[<p><a href="http://www.circleid.com/posts/domain_names_users_vs_registrants/">Domain Names Users vs Domain Names Registrants</a>:<br />
<br /><br />
Antony Van Couvering from <a href="http://www.namesatwork.com/about/nameswork-team/antony-van-couvering/">names@work</a> writes that <a href="http://www.icann.org/">ICANN</a>'s constituencies are a "<a href="http://www.namesatwork.com/blog/2008/06/08/icann-constituencies-bad-idea-whose-time-has-gone">bad idea</a>". While I am not sure to agree with him on the general principle, he makes some interesting remarks. Among others, he points out that the Generic Names Supporting Organization (GNSO) includes groups that seem to be redundant (the Business and Intellectual Property constituencies) and others like domainers which are not represented in the ICANN arena, yet are an integral part of the domain name business... <a href="http://www.circleid.com/posts/domain_names_users_vs_registrants/">More...</a><br />
<br /></p>]]>
        
    </content>
</entry>
<entry>
    <title>Domain-Name Error Redirect: Incentives and Solutions - Circle ID</title>
    <link rel="alternate" type="text/html" href="http://www.netpolicy.com/archives/004068.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webmongers.com/mt/mt-atom.cgi/weblog/blog_id=7/entry_id=4068" title="Domain-Name Error Redirect: Incentives and Solutions - Circle ID" />
    <id>tag:www.netpolicy.com,2008:/dnrc//7.4068</id>
    
    <published>2008-05-28T17:38:14Z</published>
    <updated>2008-05-28T17:38:27Z</updated>
    
    <summary>Domain-Name Error Redirect: Incentives and Solutions: Some domainers, having forgone parking revenue to avoid any claims of trademark violation, have then found themselves thrown into legal trouble with trademark claimants because of actions taken by a third party (ISPs and...</summary>
    <author>
        <name>mikki</name>
        
    </author>
            <category term="Domain Names" />
    
    <content type="html" xml:lang="en" xml:base="http://www.netpolicy.com/dnrc/">
        <![CDATA[<p><a href="http://www.circleid.com/posts/domain_name_error_redirect/">Domain-Name Error Redirect: Incentives and Solutions</a>:<br />
<br /><br />
Some domainers, having forgone parking revenue to avoid any claims of trademark violation, have then found themselves thrown into legal trouble with trademark claimants because of actions taken by a third party (ISPs and PC manufacturers). In addition to the resulting direct legal cost, the possibility of action by a third party heightens uncertainty and steals management's attention away from its real job. The troubles for the domain name owner start when a surfer who enters in the browser an inactive domain name is redirected to a Web page with advertising instead of getting a page that says there is an input error... <a href="http://www.circleid.com/posts/domain_name_error_redirect/">More...</a><br />
<br /></p>]]>
        
    </content>
</entry>
<entry>
    <title>What is the JPA?- Bret Fausett</title>
    <link rel="alternate" type="text/html" href="http://www.netpolicy.com/archives/003909.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webmongers.com/mt/mt-atom.cgi/weblog/blog_id=7/entry_id=3909" title="What is the JPA?- Bret Fausett" />
    <id>tag:www.netpolicy.com,2008:/dnrc//7.3909</id>
    
    <published>2008-02-08T17:45:08Z</published>
    <updated>2008-02-08T17:45:18Z</updated>
    
    <summary>What is the JPA?: With the NTIA&apos;s mid-term review of ICANN&apos;s performance under the JPA underway, and ICANN writing to the United States to say &quot;the JPA is no longer necessary and can be concluded,&quot; you might well ask yourself,...</summary>
    <author>
        <name>mikki</name>
        
    </author>
            <category term="ICANN" />
    
    <content type="html" xml:lang="en" xml:base="http://www.netpolicy.com/dnrc/">
        <![CDATA[<p><a href="http://blog.lextext.com/blog/_archives/2008/2/8/3512586.html">What is the JPA?</a>:<br />
<br /><br />
With the <a href="http://www.ntia.doc.gov/ntiahome/frnotices/2007/ICANN_JPA_110207.html">NTIA's mid-term review</a> of ICANN's performance under the JPA underway, and ICANN <a href="http://icann.org/correspondence/dengate-thrush-to-sene-09jan08.pdf">writing to the United States</a> to say "the JPA is no longer necessary and can be concluded," you might well ask yourself, "What is the JPA?" I did, and I'm as steeped in this as anyone. <br><br>My sense is that not everyone uses the term "JPA" to refer to the same thing. If we're talking about "concluding the JPA" (what ICANN wants) or "evaluating ICANN's performance under the JPA" (what the NTIA is now doing), it's very important to know if we're talking about the same things when we use the term "JPA.". You'll want to think about this too before you submit comments before next week's <a href="http://www.ntia.doc.gov/ntiahome/frnotices/2007/ICANN_JPA_110207.html">February 15th deadline</a>.<br><br>Here's what I know. In September, 2006, about the same time that ICANN and the NTIA entered what should have been called "Amendment 7" to their November 25, 1998 Memorandum of Understanding, they stopped using the term "MOU" and began referring to their agreement, as modified over the years, as a "Joint Project Agreement." If you look at <a href="http://www.ntia.doc.gov/ntiahome/domainname/agreements/jpa/ICANNJPA_09292006.htm">the text of their September 29, 2006 agreement,</a> you can see that references to the "MOU" have been replaced with references to the "JPA."  <br><br>This September 29, 2006 Agreement, however, is not a complete document. By its plain terms, it is an amendment to something else. That something else is the November 25, 1998 MOU. <br><br>Some people loosely refer to the "JPA" as the set of tasks listed in the September 29, 2006 amendment. Even ICANN's current Chair, Peter Dengate Thrush, uses the term "JPA" loosely in <a href="http://icann.org/correspondence/dengate-thrush-to-sene-09jan08.pdf">his letter </a>to the NTIA. <a href="http://icann.org/correspondence/dengate-thrush-to-sene-09jan08.pdf">He talks about</a> <span style="font-style: italic;">"The JPA &#8211; like the memorandums of understanding before it," </span>as though the JPA somehow replaced the MOUs. In one sense, doing away with the list of tasks in the September 29, 2006 amendment is sound. ICANN is at a stage of its development where it ought to set its own agenda, for right or wrong, and it no longer needs the constant reporting to the USG that it has done over the last few years. <br><br>So if "conclude the JPA" means allow ICANN to set its own agenda and free ICANN from its reporting requirement to the USG, I can support that.<br><br>In its proper form though, the "JPA" refers to the complete current contract between ICANN and the United States. It starts with the November 25, 1998 agreement and is modified seven times, most recently by the September 29, 2006 "JPA." Copies of all versions are here, on the NTIA website. <br><br>Just for my own education, I created a complete version of the Agreement, starting from the first MOU and incorporating all of the revisions over the years. The result is here, in a PDF document:<br><br><div style="text-align: center;"><a href="http://lextext.s3.amazonaws.com/MOU-JPA-Current.pdf">http://lextext.s3.amazonaws.com/MOU-JPA-Current.pdf</a><br></div><br>The text of the so-called "JPA" of September 29, 2006 is in blue typeface. <br><br><br><br />
<br /></p>]]>
        
    </content>
</entry>
<entry>
    <title>Statement for the Record of Karl Auerbach</title>
    <link rel="alternate" type="text/html" href="http://www.netpolicy.com/archives/003908.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webmongers.com/mt/mt-atom.cgi/weblog/blog_id=7/entry_id=3908" title="Statement for the Record of Karl Auerbach" />
    <id>tag:www.netpolicy.com,2008:/dnrc//7.3908</id>
    
    <published>2008-02-08T17:02:16Z</published>
    <updated>2008-02-08T17:02:26Z</updated>
    
    <summary>Statement for the Record of Karl Auerbach: Statement for the Record ofKarl AuerbachFormer (and only) North American Director Elected to the Board of Directors of ICANNYuen Fellow of Law and Technology (Caltech and Loyola Law School)Norbert Wiener Award (2002)Co-Founder Boston...</summary>
    <author>
        <name>mikki</name>
        
    </author>
            <category term="ICANN" />
    
    <content type="html" xml:lang="en" xml:base="http://www.netpolicy.com/dnrc/">
        <![CDATA[<p><a href="http://www.cavebear.com/archive/public/ntia-jpa-2008.html">Statement for the Record of Karl Auerbach</a>:<br />
<br /><br />
Statement for the Record of<br /><br />Karl Auerbach<br /><br />Former (and only) North American Director Elected to the Board of Directors of ICANN<br />Yuen Fellow of Law and Technology (Caltech and Loyola Law School)<br />Norbert Wiener Award (2002)<br />Co-Founder Boston Working Group (BWG)<br />Chief Technical Officer, InterWorking Labs, Inc.<br />Director, Domain Name Rights Coalition<br />Attorney at Law (California) and member of<br />the Intellectual Property Section of the California State Bar.<br /><br />on<br /><br />The Continued Transition of the Technical Coordination and Management of the Internet's Domain Name and Addressing System: Midterm Review of the Joint Project Agreement<br />DEPARTMENT OF COMMERCE<br />National Telecommunications and Information Administration<br />[Docket No. 071023616-7617-01]<br /><br />February 6, 2008<br /><br />Comments<br /><br />In 2006 when NTIA last inquired about ICANN, I submitted a set of comments.  These may be seen on-line at: http://www.cavebear.com/archive/public/ntia-july-7-2006-statement.html<br /><br />It is now 2008.  Those comments made in 2006 remai<br />
<br /></p>]]>
        
    </content>
</entry>
<entry>
    <title>Special Circumstances My Foot - Karl Auerbach</title>
    <link rel="alternate" type="text/html" href="http://www.netpolicy.com/archives/003514.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webmongers.com/mt/mt-atom.cgi/weblog/blog_id=7/entry_id=3514" title="Special Circumstances My Foot - Karl Auerbach" />
    <id>tag:www.netpolicy.com,2007:/dnrc//7.3514</id>
    
    <published>2007-03-30T03:19:24Z</published>
    <updated>2007-03-30T03:20:41Z</updated>
    
    <summary>Special Circumstances My Foot: The &quot;whois&quot; system for domain names is the single greatest violation of privacy rights on the internet. A reasonable cure has been put forth that would require only that domain name registrants designate a contact, who...</summary>
    <author>
        <name>mikki</name>
        
    </author>
            <category term="Privacy" />
    
    <content type="html" xml:lang="en" xml:base="http://www.netpolicy.com/dnrc/">
        <![CDATA[<p><a href="http://www.cavebear.com/cbblog-archives/000308.html">Special Circumstances My Foot</a>:<br />
<br /><br />
<p>The "whois" system for domain names is the single greatest violation<br />
of privacy rights on the internet.</p></p>

<p>A reasonable cure has been put forth that would require only that domain name
registrants designate a contact, who could be an agent, to receive communications
pertaining to the technical operation of the domain.&nbsp; This is not unlike
the way that corporations keep much of their structure private
by designating an agent for the receipt of legal notices.&nbsp;
ICANN and Verisign both do this.</p>

<p>The industry that protects intellectual property (not to be confused
with the industry that creates intellectual property) does not like this proposal;
they would prefer that every person go naked on the internet, with their names and numbers
tattooed to their chests, and live in glass houses.</p>

<p>The trademark industry wants domain name registrants to reveal their information, and
that of their families and children, to the anonymous predators of the world on a 24x7 basis.</p>

<p>The trademark industry will allow but one exception - if a person claims sanctuary
on the basis of "special circumstance".&nbsp; What this means is that a few shelters for
bettered women might be allowed to refrain from publishing their contact information.</p>

<p>This "special circumstances" proposal is contrary to one of the most fundamental
tenets of modern society, that a person is presumed innocent until proven guilty.&nbsp;
The "special circumstances" proposal is nothing short of a systematic conclusion
that you and I and every other domain name registrant is to be presumed to be a thief and
unworthy of privacy.&nbsp; The burden is placed not only on us to rebut that
presumption but to do so in advance even of an accusation.</p>

<p>We are being told in no uncertain terms that our privacy,
and that of our families and children, is worth less than a trademark.</p>

<p>The "special circumstances" shoe should be put on the other foot.&nbsp; If a trademark
owner wants to penetrate the privacy of the Whois data that owner should be obligated
to make a specific accusation, saying on a permanent public record, what rights of that owner
are being violated by the accused domain name owner and what facts exist to support
that accusation.</p>

<p>In other words, the trademark owner should be required to demonstate, with concrete
accusations backed by concrete facts, that special
circumstances exist that are sufficient to violate a person's right to privacy.</p>

<p>We have seen how the music and movie vigilantes, the RIAA and MPOA, have run amok
making groundless accusations against thousands of innocent people.&nbsp;
These are the law-firm office mates of the
trademark people who want to violate our privacy in our domain names.&nbsp;
There is much reason to be skeptical of their intentions.</p>
<br />]]>
        
    </content>
</entry>
<entry>
    <title>Registrars and Customer Service - Three Comments - Part 2</title>
    <link rel="alternate" type="text/html" href="http://www.netpolicy.com/archives/003437.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webmongers.com/mt/mt-atom.cgi/weblog/blog_id=7/entry_id=3437" title="Registrars and Customer Service - Three Comments - Part 2" />
    <id>tag:www.netpolicy.com,2007:/dnrc//7.3437</id>
    
    <published>2007-02-16T13:28:29Z</published>
    <updated>2007-02-16T13:28:51Z</updated>
    
    <summary><![CDATA[Registrars and Customer Service - Three Comments - Part 2: This is a continuation of my previous note, "Registrars and Customer Service - Three Comments - Part 1". One of the two letters was from Tim Ruiz of GoDaddy.&nbsp; The...]]></summary>
    <author>
        <name>mikki</name>
        
    </author>
            <category term="Domain Names" />
            <category term="ICANN" />
    
    <content type="html" xml:lang="en" xml:base="http://www.netpolicy.com/dnrc/">
        <![CDATA[<p><a href="http://www.cavebear.com/cbblog-archives/000301.html">Registrars and Customer Service - Three Comments - Part 2</a>:<br />
<br /><br />
<p>This is a continuation of my previous note, <A href="http://www.cavebear.com/cbblog-archives/000300.html">"Registrars and Customer Service - Three Comments - Part 1"</A>.</p></p>

<p>One of the two <A href="http://www.icann.org/correspondence/ruiz-to-twomey-09feb07.pdf">letters</A> was from Tim Ruiz of GoDaddy.&nbsp;
The gist of this letter was that the number of registrar complaints received by ICANN
really was not significant enough to suggest that there is any problem with
how registrars behave.</p>

<p>The number of complaints cited was 10,000 during 2006.</p>

<p>Sounds like a lot.</p>

<p>Sounds like a lot more when we realize that it is a rule-of-thumb of marketing
and sales that for every customer complaint there are nine more who are angry but
silent.</p>

<p>And it sounds like a lot more when we realize that a large number of domain name
consumers are professional monetizers who are probably in bed with, or at least in the bedroom with, the registrars they work with - complaints from this quarter are probably rare.</p>

<p>That means that we are talking about at least 100,000 upset domain users out of
a pool that mounts to those who actually use domain names as long-term stable identifiers -
a pool that probably amounts to perhaps 10 million at best - so we are talking about
a complaint rate of at least 1% per long-term domain name client per year.&nbsp;
That's a pretty significant problem rate, especially when measured as the expectency
of a long-term domain owner over the lifetime of his/her ownership.</p>

<p>And the number of complaints seems even bigger when we realize that there
are a lot of issues that people have simply learned to accept without complaint.&nbsp;
For example, was there a complaint when GoDaddy became a tool in a dispute and
yanked someone's domain name, with 52 seconds notice?</p>

<p>And there are a lot of people who have simply given up - either because they don't
know to whom they should complain, or have complained in the past and found the system
to be a bowl of futile hope, or simply don't realize that they have been scrod.</p>

<p>So, from the same numbers I draw the opposite conclusion - I perceive that
we have a serious issue between that part of the public who use domain names for what they
were originally intended to be - long term stable identifiers on the internet - and
the registrar/registry system that sells (or rents) those names.</p>
<br />]]>
        
    </content>
</entry>
<entry>
    <title>Registrars and Customer Service - Three Comments - Part 3</title>
    <link rel="alternate" type="text/html" href="http://www.netpolicy.com/archives/003436.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webmongers.com/mt/mt-atom.cgi/weblog/blog_id=7/entry_id=3436" title="Registrars and Customer Service - Three Comments - Part 3" />
    <id>tag:www.netpolicy.com,2007:/dnrc//7.3436</id>
    
    <published>2007-02-16T13:27:58Z</published>
    <updated>2007-02-16T13:28:24Z</updated>
    
    <summary>Registrars and Customer Service - Three Comments - Part 3: This is a continuation of my previous note, &quot;Registrars and Customer Service - Three Comments - Part 1&quot;. One of the two letters was from David Maher of PIR, the...</summary>
    <author>
        <name>mikki</name>
        
    </author>
            <category term="Domain Names" />
            <category term="ICANN" />
    
    <content type="html" xml:lang="en" xml:base="http://www.netpolicy.com/dnrc/">
        <![CDATA[<p><a href="http://www.cavebear.com/cbblog-archives/000302.html">Registrars and Customer Service - Three Comments - Part 3</a>:<br />
<br /><br />
<p>This is a continuation of my previous note, <A href="http://www.cavebear.com/cbblog-archives/000300.html">"Registrars and Customer Service - Three Comments - Part 1"</A>.</p></p>

<p>One of the two <A href="http://www.icann.org/correspondence/maher-to-twomey-07feb07.pdf">letters was from David Maher of PIR</A>, the registry handling <em>.org</em>.</p>

<p>I have great respect for David Maher - he's one of the "white hats".&nbsp;
But in this instance I believe he is going down the wrong path.</p>

<p>Perhaps the most important sentence of his letter was this:</p>

<p><em>While I recognize that the registrar function is best served by a competitive
business model, the Internet has become too important to all its users to allow
pure competition to set the standards for customer service.</em></p>

<p>When it comes to domain names under ICANN we have never ever had a
"competitive business model".</p>

<p>What we have had is a highly regulated marketplace in which there is little
real choice between domain name products - ICANN has dictated many of the terms of sale,
ICANN has dictated the major price components (reserving a hefty chunk
for registries such as PIR and for ICANN),
and ICANN has severely constrained the number of vendors in the marketplace.</p>

<p>In other words, we are already living in the world in which there is
not pure competition, indeed no real competition at all, except on a thin price margin
above the core cost components that ICANN reserves for registries and for ICANN.</p>

<p>Why is this so?&nbsp; Why are we consumers of domain names to be treated as children
and not allowed the full possible smorgasbord of domain name products that vendors might
create?</p>

<p>Let me be even more specific - By implication my proposal for a domain name product,
<A href="http://www.cavebear.com/cbblog-archives/000159.html">my .ewe TLD</A>, is a danger to the internet because it does not follow ICANN's rules.</p>

<p>But I deny that new, and different, ideas such as <em>.ewe</em> represent a danger to
the stability of the internet.&nbsp; Yes, such ideas pose a danger to the business stability
of the current ICANN-approved incumbents, but we have never as a modern society
accepted that there should be such protected marketplaces absent a clear, compelling, and
clearly articulated reason for such protection.</p>

<p>So what I would like to hear is this:&nbsp; What are the reasons that require NTIA
and its secular arm, ICANN, to require that the domain name marketplace be wrapped with
restrictions and limitations that effectively turn the domain name marketplace into
a medieval guild?</p>

<p>I'm not willing to accept vague platitudes - I want to hear
specific and concrete reasons.&nbsp; And my measure of stability is based on the
technical ability of the internet and the upper tier of the domain name system to turn
DNS query packets into DNS reply packets with dispatch, accuracy, and without
prejudice for or against any query source or query target.</p>

<p>I am sure that someone will raise the bogeyman of business failure of
a registry or registrar causing hapless domain name owners to become orphans with
names that no longer work.&nbsp; To me that's a business issue, or a consumer
protection issue.&nbsp; The resolution of such issues is a governmental legislative
matter, not something for a body whose role is technical coordination.&nbsp; And there
are easy, non intrusive answers to this - my own suggestion is that those registries
and registrars that want to demonstrate a commitment to protecting their customers actually
engage in data escrow programs and yearly audit themselves and post a statement attesting
that they engage in adequate data preservation practices that a successor in interest
could pick up the pieces and restore operations.&nbsp; Consumers can learn to look
elsewhere if a registry or registrar does not do these things.&nbsp; This kind of
self-protection on the part of consumers would be greatly enhanced if ICANN were to
remove its existing rule against long-term registration contracts.</p>
<br />]]>
        
    </content>
</entry>
<entry>
    <title>New Improved Cartel Jihad!  Now More Efficient Than Ever! - From Copyfight</title>
    <link rel="alternate" type="text/html" href="http://www.netpolicy.com/archives/003430.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webmongers.com/mt/mt-atom.cgi/weblog/blog_id=7/entry_id=3430" title="New Improved Cartel Jihad!  Now More Efficient Than Ever! - From Copyfight" />
    <id>tag:www.netpolicy.com,2007:/dnrc//7.3430</id>
    
    <published>2007-02-15T16:00:33Z</published>
    <updated>2007-02-15T16:01:52Z</updated>
    
    <summary>New Improved Cartel Jihad! Now More Efficient Than Ever!: In case you were fooled lately into thinking that the RIAA and the rest of the Content Cartel were going to pursue a policy other than &quot;Sue All the World, Sue...</summary>
    <author>
        <name>mikki</name>
        
    </author>
            <category term="Copyright" />
    
    <content type="html" xml:lang="en" xml:base="http://www.netpolicy.com/dnrc/">
        <![CDATA[<p><a href="http://feeds.feedburner.com/~r/Copyfight/~3/91199462/new_improved_cartel_jihad_now_more_efficient_than_ever.php">New Improved Cartel Jihad!  Now More Efficient Than Ever!</a>:<br />
<br /><br />
<p>In case you were fooled lately into thinking that the RIAA and the rest of the Content Cartel were going to pursue a policy other than <a href="http://www.campchaos.com/blog-archives/2006/05/napster_bad_sue_all_the_world.html">"Sue All the World, Sue All the Children"</a> please permit <a href="http://recordingindustryvspeople.blogspot.com/2007/02/riaa-adopts-new-policy-offers-pre-doe.html">the blog "Recording Industry vs The People"</a>, maintained by NYC lawyers Ty Rogers and Ray Beckerman, to adjust your reality.</p></p>

<p></p>

<p>The blog has posted a letter appearntly leaked from the RIAA.  In this letter the Cartel enforcement arm attempts to cajole ISPs into maintaining subscriber ISP records for 180 days.  To make its lawsuits go more smoothly, of course.  In exchange for shutting the hell up and turning over data promptly the ISP's customers get a promise of a $1000 discount for payment prior to lawsuit being filed. It's not at all clear to me why any sane ISP would sign on to this deal since it means more work and more risk for them, not to mention the exposure of being counter-sued by irate customers for turning over records.</p>

<p></p>

<p>You can read a brief summary on the lawyer's blog, and extensive commentary on the various links below the entry. The gist is still the same - the RIAA wants more suits, faster suits, more settlements, and fewer embarrassing publicity gaffes.  I can't exactly blame them for wanting these things, but I'd rather they realized that they haven't made any difference in the past 7+ years of suing their customers and they're not going to make a difference if they spend another 77 years suing their customers.</p><img src="http://feeds.feedburner.com/~r/Copyfight/~4/91199462"/>
<br />]]>
        
    </content>
</entry>
<entry>
    <title>EFF takes Viacom to task over YouTube takedown</title>
    <link rel="alternate" type="text/html" href="http://www.netpolicy.com/archives/003427.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webmongers.com/mt/mt-atom.cgi/weblog/blog_id=7/entry_id=3427" title="EFF takes Viacom to task over YouTube takedown" />
    <id>tag:www.netpolicy.com,2007:/dnrc//7.3427</id>
    
    <published>2007-02-15T14:59:27Z</published>
    <updated>2007-02-15T15:00:26Z</updated>
    
    <summary>EFF takes Viacom to task over YouTube takedown: Web rights advocates say YouTube contributors mistakenly accused of infringing upon Viacom copyright may be the real victims....</summary>
    <author>
        <name>mikki</name>
        
    </author>
            <category term="Copyright" />
    
    <content type="html" xml:lang="en" xml:base="http://www.netpolicy.com/dnrc/">
        <![CDATA[<p><a href="http://news.com.com/2100-1026_3-6159548.html?part=rss&#38;tag=2547-1_3-0-20&#38;subj=news">EFF takes Viacom to task over YouTube takedown</a>:<br />
<br /><br />
Web rights advocates say YouTube contributors mistakenly accused of infringing upon Viacom copyright may be the real victims.<br />
<br /></p>]]>
        
    </content>
</entry>

</feed> 

