<HTML>
<HEAD>
<TITLE>Re: Re[2]: [bc-gnso] DRAFT BC Public Comments on DAGv4</TITLE>
</HEAD>
<BODY>
<FONT FACE="Arial"><SPAN STYLE='font-size:12pt'>Berard is right – the common ground for the BC can be a desire to protect consumer confidence in the Internet. As a coalition of brand owners, CADNA ultimately support Sarah’s drafted comments. We feel that the draft speaks to the need for better protection of businesses and consumers in the DAG if the new gTLD process moves forward. <BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Arial"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Arial"><SPAN STYLE='font-size:12pt'>CADNA hopes that the BC can reach a consensus on a new set of comments. Given that there is a range of perspectives among the members of the BC, submitting individual comments is going to be critical for voicing specific concerns – however, the BC position should focus on business and consumer protection. <BR>
<BR>
<BR>
<BR>
Yvette Miller<BR>
Director, Communications<BR>
The Coalition Against Domain Name Abuse (CADNA) <BR>
1632 Wisconsin Ave, NW <BR>
Washington, D.C. 20007 <BR>
Office: +1 202 223 9355 <BR>
Mobile: +1 202 341 3799<BR>
<a href="yvette@cadna.org">yvette@cadna.org</a><BR>
<BR>
<BR>
On 7/19/10 9:28 PM, "<a href="john@crediblecontext.com">john@crediblecontext.com</a>" <<a href="john@crediblecontext.com">john@crediblecontext.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT SIZE="2"><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>I can lurk no longer!<BR>
<BR>
Setting aside the snark of Phil's email, he has a point. There is no apple so big that can accommodate the extra bites taken over the last few days.<BR>
<BR>
But rather than lay blame at the feet of the Business Constituency, I think we are falling into the trap set by ICANN's history of never making a decision today it can put off until tomorrow. It is why lawsuits are the real policy making processes. <BR>
<BR>
The ability to drive consensus is essential but, when one considers the breadth of membership (now and potential), it ain't easy. For me, the thing that ultimately gets us there is a shared commitment to building out and protecting consumer confidence in the Internet. <BR>
<BR>
At bottom, most of the dissonance in the BC merely is rooted in different appetites for arbitrage. We all have far more in common, reason to find consensus and to work together to get ICANN to live by its rules.<BR>
<BR>
Too preachy?<BR>
<BR>
Cheers,<BR>
<BR>
Berard<BR>
</SPAN></FONT></FONT><BLOCKQUOTE><FONT SIZE="2"><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>-------- Original Message --------<BR>
Subject: RE: Re[2]: [bc-gnso] DRAFT BC Public Comments on DAGv4<BR>
From: Phil Corwin <<a href="pcorwin@butera-andrews.com">pcorwin@butera-andrews.com</a> <<a href="mailto://pcorwin@butera-andrews.com">mailto://pcorwin@butera-andrews.com</a>> ><BR>
Date: Mon, July 19, 2010 3:22 pm<BR>
To: "<a href="zahid@dndrc.com">zahid@dndrc.com</a> <<a href="mailto://zahid@dndrc.com">mailto://zahid@dndrc.com</a>> " <<a href="zahid@dndrc.com">zahid@dndrc.com</a> <<a href="mailto://zahid@dndrc.com">mailto://zahid@dndrc.com</a>> >, Jon Nevett <<a href="jon@nevett.net">jon@nevett.net</a> <<a href="mailto://jon@nevett.net">mailto://jon@nevett.net</a>> ><BR>
Cc: Sarah B Deutsch <<a href="sarah.b.deutsch@verizon.com">sarah.b.deutsch@verizon.com</a> <<a href="mailto://sarah.b.deutsch@verizon.com">mailto://sarah.b.deutsch@verizon.com</a>> >, <BR>
"<a href="michaelc@traveler.com">michaelc@traveler.com</a> <<a href="mailto://michaelc@traveler.com">mailto://michaelc@traveler.com</a>> " <<a href="michaelc@traveler.com">michaelc@traveler.com</a> <<a href="mailto://michaelc@traveler.com">mailto://michaelc@traveler.com</a>> >, <BR>
"<a href="mike@haven2.com">mike@haven2.com</a> <<a href="mailto://mike@haven2.com">mailto://mike@haven2.com</a>> " <<a href="mike@haven2.com">mike@haven2.com</a> <<a href="mailto://mike@haven2.com">mailto://mike@haven2.com</a>> >, "<a href="jb7454@att.com">jb7454@att.com</a> <<a href="mailto://jb7454@att.com">mailto://jb7454@att.com</a>> " <<a href="jb7454@att.com">jb7454@att.com</a> <<a href="mailto://jb7454@att.com">mailto://jb7454@att.com</a>> >, <BR>
"<a href="randruff@rnapartners.com">randruff@rnapartners.com</a> <<a href="mailto://randruff@rnapartners.com">mailto://randruff@rnapartners.com</a>> " <<a href="randruff@rnapartners.com">randruff@rnapartners.com</a> <<a href="mailto://randruff@rnapartners.com">mailto://randruff@rnapartners.com</a>> >, <BR>
"<a href="ffelman@markmonitor.com">ffelman@markmonitor.com</a> <<a href="mailto://ffelman@markmonitor.com">mailto://ffelman@markmonitor.com</a>> " <<a href="ffelman@markmonitor.com">ffelman@markmonitor.com</a> <<a href="mailto://ffelman@markmonitor.com">mailto://ffelman@markmonitor.com</a>> >, BC<BR>
Secretariat <<a href="bc-gnso@icann.org">bc-gnso@icann.org</a> <<a href="mailto://bc-gnso@icann.org">mailto://bc-gnso@icann.org</a>> ><BR>
<BR>
<BR>
</SPAN></FONT><SPAN STYLE='font-size:10pt'><FONT FACE="Tahoma, Verdana, Helvetica, Arial"> <BR>
So we get a draft position less than a week before the filing deadline, multiple BC members raise concerns about it, and then we're told that for the sake of consistency it must be repeated because there is no time to formulate a new approach? <BR>
<BR>
<BR>
<BR>
Maybe the way we should operate is that without demonstration by member polling that consensus still exists for the prior unsuccessful arguments the Constituency should remain silent and we all go file our own statements? But then of course Jon did formulate revisions for which there appeared to be broader support, but I guess that's now rejected because only even stronger statements will be regarded as consistent with the prior position.<BR>
<BR>
<BR>
<BR>
Is that how this Constituency is now operating? Biased toward suppressing alternate views instead of seeking consensus?<BR>
<BR>
<BR>
<BR>
I would suggest that in regard to all future policy matters on which the BC leadership wishes to file a Constituency position that members be provided with a draft no less than two weeks before the deadline so that there is sufficinet time to formulate a new or revised position if there is significant internal disagreement -- and that all such BC positions require a formal vote to see if there is indeed consensus, regardless of past positions.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</FONT></SPAN></FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT COLOR="#000080"><FONT SIZE="2"><FONT FACE="Arial Black"><SPAN STYLE='font-size:10pt'>Philip S. Corwin <BR>
Partner <BR>
Butera & Andrews <BR>
1301 Pennsylvania Ave., NW <BR>
Suite 500 <BR>
Washington, DC 20004<BR>
</SPAN></FONT></FONT></FONT><FONT SIZE="2"><SPAN STYLE='font-size:10pt'><FONT FACE="Tahoma, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT COLOR="#000080"><FONT FACE="Arial Black">202-347-6875 (office) <BR>
</FONT></FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT COLOR="#000080"><FONT FACE="Arial Black">202-347-6876 (fax</FONT><FONT FACE="Arial">)<BR>
</FONT></FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT COLOR="#000080"><FONT FACE="Arial Black">202-255-6172 (cell)<BR>
</FONT></FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial"> <BR>
</FONT><FONT COLOR="#000080"><FONT FACE="Arial Black"><I>"Luck is the residue of design."</I> -- Branch Rickey<BR>
</FONT></FONT><FONT FACE="Tahoma, Verdana, Helvetica, Arial"> <BR>
<BR>
<BR>
</FONT></SPAN></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<HR ALIGN=CENTER SIZE="3" WIDTH="100%"> <BR>
</SPAN></FONT><SPAN STYLE='font-size:12pt'><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><B>From:</B> Zahid Jamil [<a href="zahid@dndrc.com">zahid@dndrc.com</a> <<a href="mailto://zahid@dndrc.com">mailto://zahid@dndrc.com</a>> ]<BR>
<B>Sent:</B> Monday, July 19, 2010 6:05 PM<BR>
<B>To:</B> Jon Nevett<BR>
<B>Cc:</B> Sarah B Deutsch; Phil Corwin; <a href="michaelc@traveler.com">michaelc@traveler.com</a> <<a href="mailto://michaelc@traveler.com">mailto://michaelc@traveler.com</a>> ; <a href="mike@haven2.com">mike@haven2.com</a> <<a href="mailto://mike@haven2.com">mailto://mike@haven2.com</a>> ; <a href="jb7454@att.com">jb7454@att.com</a> <<a href="mailto://jb7454@att.com">mailto://jb7454@att.com</a>> ; <a href="randruff@rnapartners.com">randruff@rnapartners.com</a> <<a href="mailto://randruff@rnapartners.com">mailto://randruff@rnapartners.com</a>> ; <a href="ffelman@markmonitor.com">ffelman@markmonitor.com</a> <<a href="mailto://ffelman@markmonitor.com">mailto://ffelman@markmonitor.com</a>> ; BC Secretariat<BR>
<B>Subject:</B> Re: Re[2]: [bc-gnso] DRAFT BC Public Comments on DAGv4<BR>
<BR>
</FONT><FONT FACE="Times New Roman"> <BR>
<BR>
<BR>
I am sure there is some validity to much of your arguments. Be that as it may. <BR>
<BR>
There is little time to initiate a new approach and consensus within the BC for such a new approach. <BR>
<BR>
As such we need to stick to our current accepted positions and new comments consistent with these positions and comment before the deadline.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Sincerely,<BR>
<BR>
Zahid Jamil<BR>
Barrister-at-law<BR>
Jamil & Jamil<BR>
Barristers-at-law<BR>
219-221 Central Hotel Annexe<BR>
Merewether Road, Karachi. Pakistan<BR>
Cell: +923008238230<BR>
Tel: +92 21 5680760 / 5685276 / 5655025<BR>
Fax: +92 21 5655026<BR>
www.jamilandjamil.com <<a href="http://www.jamilandjamil.com">http://www.jamilandjamil.com</a>> <BR>
<BR>
Notice / Disclaimer<BR>
This message contains confidential information and its contents are being communicated only for the intended recipients . If you are not the intended recipient you should not disseminate, distribute or copy this e-mail.<BR>
Please notify the sender immediately by e-mail if you have received this message by mistake and delete it from your system. The contents above may contain/are the intellectual property of Jamil & Jamil, Barristers-at-Law, and constitute privileged information protected by attorney client privilege. The reproduction, publication, use, amendment, modification of any kind whatsoever of any part or parts (including photocopying or storing it in any medium by electronic means whether or not transiently or incidentally or some other use of this communication) without prior written permission and consent of Jamil & Jamil is prohibited.<BR>
<BR>
<BR>
Sent from my BlackBerry® wireless device<BR>
<BR>
<HR ALIGN=CENTER SIZE="3" WIDTH="100%"> <BR>
<B>From: </B>Jon Nevett <<a href="jon@nevett.net">jon@nevett.net</a> <<a href="mailto://jon@nevett.net">mailto://jon@nevett.net</a>> > <BR>
<BR>
<B>Date: </B>Mon, 19 Jul 2010 18:01:04 -0400<BR>
<BR>
<B>To: </B>Zahid Jamil<<a href="zahid@dndrc.com">zahid@dndrc.com</a> <<a href="mailto://zahid@dndrc.com">mailto://zahid@dndrc.com</a>> ><BR>
<BR>
<B>Cc: </B>'Deutsch, Sarah B'<<a href="sarah.b.deutsch@verizon.com">sarah.b.deutsch@verizon.com</a> <<a href="mailto://sarah.b.deutsch@verizon.com">mailto://sarah.b.deutsch@verizon.com</a>> >; 'Phil Corwin'<<a href="pcorwin@butera-andrews.com">pcorwin@butera-andrews.com</a> <<a href="mailto://pcorwin@butera-andrews.com">mailto://pcorwin@butera-andrews.com</a>> >; <<a href="michaelc@traveler.com">michaelc@traveler.com</a> <<a href="mailto://michaelc@traveler.com">mailto://michaelc@traveler.com</a>> >; <<a href="mike@haven2.com">mike@haven2.com</a> <<a href="mailto://mike@haven2.com">mailto://mike@haven2.com</a>> >; <<a href="jb7454@att.com">jb7454@att.com</a> <<a href="mailto://jb7454@att.com">mailto://jb7454@att.com</a>> >; <<a href="randruff@rnapartners.com">randruff@rnapartners.com</a> <<a href="mailto://randruff@rnapartners.com">mailto://randruff@rnapartners.com</a>> >; <<a href="ffelman@markmonitor.com">ffelman@markmonitor.com</a> <<a href="mailto://ffelman@markmonitor.com">mailto://ffelman@markmonitor.com</a>> >; <<a href="bc-GNSO@icann.org">bc-GNSO@icann.org</a> <<a href="mailto://bc-GNSO@icann.org">mailto://bc-GNSO@icann.org</a>> ><BR>
<BR>
<B>Subject: </B>Re: Re[2]: [bc-gnso] DRAFT BC Public Comments on DAGv4<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Zahid:<BR>
<BR>
<BR>
<BR>
<BR>
The timely introduction of new TLDs is not a registrar issue or BC issue, it is a community issue. I am told that the registrars are not commenting on the DAGv4 because they do not agree on the issues sufficiently to have a uniform position. On the RPMs some probably think they go too far and others might think that they don't go far enough. I don't know. Some BC members think enough is enough and let's get on with it. The New TLDs will be much safer from a TM standpoint than .com and the other existing gTLDs, the vast majority of ccTLDs, and the newly approved IDN ccTLDs. I have corporate clients that have been waiting years to apply for their TLD. They are getting increasingly frustrated with the same arguments being made. Just because some arguments weren't accepted does not mean that they were ignored. Others obviously disagree with that position. The BC is a big tent and we will have a diversity of viewpoints, especially on this issue. Based on the comments I have seen thus far on this list and in private e-mails of support, it is clear that there is a division in the BC on the outstanding New TLD issues. Some want the application process to open forthwith others don't want to see it open at all or not for a long time. Big tent. <BR>
<BR>
<BR>
<BR>
<BR>
Per your last note. if you don't think that it requires a consensus of the membership to reissue the DAGv3 comments in response to DAGv4, then go ahead. Ron, I and others could have saved a great deal of time working on redlines of the drafts.<BR>
<BR>
<BR>
<BR>
<BR>
Thanks.<BR>
<BR>
<BR>
<BR>
<BR>
Jon<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
On Jul 19, 2010, at 5:00 PM, Zahid Jamil wrote:<BR>
<BR>
<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE='font-size:12pt'><FONT FACE="Times New Roman"> <BR>
<BR>
<BR>
</FONT></SPAN><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Dear All,<BR>
</SPAN></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
</SPAN></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Have been following in this discussion intermittently. Here are some of my quick thoughts. The IRT is not and has not been the yard stick by which BC comments or views have been formed in the past. BC did support the IRT but clearly stated that the IRT had not gone far enough. If we take the argument that the IRT position should be followed solely then please keep the GPML in.<BR>
</SPAN></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
</SPAN></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>We currently have no solutions for the defensive registration problem. The URS is not Rapid. There is no transfer of the domain in a URS. The Trademark Clearinghouse is not a Rights Protection Mechanism (admittedly). So what are we really left with. <BR>
</SPAN></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
</SPAN></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Jon’s discussions here in the BC are reminiscent of the arguments Jon made in the IRT and the STI where, at the time, Jon was representing Registrar interests. He has been a valuable member of both groups and I look forward to his arguing in favour of BC positions now with the same, if not greater, zeal.<BR>
</SPAN></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
</SPAN></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Any argument that amounts to –they didn’t listen to us in the past so let’s give up and settle for what we can does not address the problem. There is much to be said about consistency. I would encourage the BC to also take from the existing BC minority position in the STI report. That is a BC position and hence, it ought to be repeated where appropriate (have attached the STI report – BC minority position is at page 31). We should be lobbying for better protection, in my view, not less since ICANN staff proposals sideline and ignore business and trademark interests.<BR>
</SPAN></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
</SPAN></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Lets also remember that the BC position has been vindicated in the Economic Analysis which asks that limited rounds be undertaken and clearly underscores the economic cost of the defensive registration problem. Just because we haven’t worked on how limited rounds would be implemented it doesn’t mean that the concept is flawed. The Economic study makes cogent arguments in its favour. Its now up to ICANN staff and possibly community to come up with mechanisms.<BR>
</SPAN></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
</SPAN></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Also the Economic Analysis clearly finds that there need to be surveys and studies (details in the report) which should be conducted and then mechanisms developed based on actual statistics. Clearly showing that ICANN staff has run away with the new gTLD proposal without adequate study and analysis. Hence, mention of the Analysis is quite pertinent and I support Jeff’s views in this.<BR>
</SPAN></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Have pasted my Brussels email below:<BR>
</SPAN></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><SPAN STYLE='font-size:12pt'><FONT FACE="Verdana, Helvetica, Arial"><B>My edits in [...]<BR>
</B></FONT><FONT FACE="Times New Roman"> <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</FONT><FONT FACE="Verdana, Helvetica, Arial"><B>Economic Study:<BR>
</B></FONT><FONT FACE="Times New Roman"> <BR>
</FONT><FONT FACE="Verdana, Helvetica, Arial">In light of the newly released economic study what steps are envisioned by ICANN staff: including:<BR>
</FONT><FONT FACE="Times New Roman"> <BR>
</FONT><FONT FACE="Verdana, Helvetica, Arial">Survey (how)<BR>
</FONT><FONT FACE="Times New Roman"> <BR>
</FONT><FONT FACE="Verdana, Helvetica, Arial">Study (how)<BR>
</FONT><FONT FACE="Times New Roman"> <BR>
</FONT><FONT FACE="Verdana, Helvetica, Arial">Past introductions<BR>
</FONT><FONT FACE="Times New Roman"> <BR>
</FONT><FONT FACE="Verdana, Helvetica, Arial">Methodlogies<BR>
</FONT><FONT FACE="Times New Roman"> <BR>
</FONT><FONT FACE="Verdana, Helvetica, Arial">In particular re TM, user confusion (notwithstanding the current RPMs)<BR>
</FONT><FONT FACE="Times New Roman"> <BR>
<BR>
<BR>
</FONT><FONT FACE="Verdana, Helvetica, Arial">P – 16 – 17 :<BR>
</FONT><FONT FACE="Times New Roman"> <BR>
</FONT><FONT FACE="Verdana, Helvetica, Arial">Subsidies<BR>
</FONT><FONT FACE="Times New Roman"> <BR>
</FONT><FONT FACE="Verdana, Helvetica, Arial"><B>Adjust Fee vs. Favourable approval process<BR>
</B></FONT><FONT FACE="Times New Roman"> <BR>
<BR>
<BR>
</FONT><FONT FACE="Verdana, Helvetica, Arial">25 - </FONT><FONT FACE="Times New Roman"><I>Potential consumer confusion or fragmentation of the Internet<BR>
</I> <BR>
</FONT><FONT FACE="Verdana, Helvetica, Arial">26 - </FONT><FONT FACE="Times New Roman"><I>Increased registration costs for companies that feel the need to be<BR>
</I> <BR>
<I>in multiple places on the Internet<BR>
</I> <BR>
</FONT><FONT FACE="Verdana, Helvetica, Arial">28 - </FONT><FONT FACE="Times New Roman"><I>Defensive registrations<BR>
</I> <BR>
</FONT><FONT FACE="Verdana, Helvetica, Arial">29 - </FONT><FONT FACE="Times New Roman"><I>Increased cost to companies to police new gTLD registrations that<BR>
</I> <BR>
<I>violate trademarks or copyrights [<B>VIGILANCE</B>]<BR>
</I> <BR>
</FONT><FONT FACE="Verdana, Helvetica, Arial">44 - </FONT><FONT FACE="Times New Roman">74 percent of the registered domain names either were “under construction,” for<BR>
<BR>
sale, returned an error, or did not return a website at all. Thus, at least in the early stages of .biz, the great majority of registered domain names were not being used to provide content to users, again indicating that the registrations may have been defensive.<BR>
<BR>
<BR>
<BR>
</FONT><FONT FACE="Verdana, Helvetica, Arial">59 –<BR>
</FONT><FONT FACE="Times New Roman"> <BR>
</FONT><FONT FACE="Arial">105<B>. A survey of registrants would likely be needed to disentangle the extent to which<BR>
</B></FONT><FONT FACE="Times New Roman"> <BR>
</FONT><FONT FACE="Arial"><B>duplicate registrations are either purely defensive (and constitute external costs) or generate benefits to the registrants</B>. A survey of trademark owners could provide information on the reasons for registration of domain names in multiple gTLDs, such as how registrants use the additional gTLDs (</FONT><FONT FACE="Times New Roman"><I>e.g., </I></FONT><FONT FACE="Arial">to provide new content or purely to redirect to another site) and whether the registrants expect to reach a new audience with the new gTLD.</FONT></SPAN><FONT FACE="Arial"><FONT SIZE="1"><SPAN STYLE='font-size:7pt'>115<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
</SPAN></FONT><FONT SIZE="5"><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:15pt'><B>[Zahid Note - SURVEY requested by IRT hasn’t been undertaken by Staff either]<BR>
</B></SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
</SPAN></FONT><SPAN STYLE='font-size:12pt'><FONT FACE="Verdana, Helvetica, Arial">61 - </FONT><FONT FACE="Arial">We recommend that ICANN consider the potential for consumer confusion in deciding how quickly to proceed with the introduction of gTLDs, possibly incorporating some methodology to measure consume confusion as new gTLDs are rolled out over time.<BR>
</FONT><FONT FACE="Times New Roman"> <BR>
<BR>
<BR>
</FONT><FONT FACE="Verdana, Helvetica, Arial">62 - </FONT><FONT FACE="Arial">This potential project would use case studies to examine the likely costs and benefits in broad categories of new gTLDs.<BR>
</FONT><FONT FACE="Times New Roman"> <BR>
<BR>
<BR>
</FONT><FONT FACE="Arial"><B><U>Such studies would lead to recommendations on how ICANN could craft its application process and ongoing rules to lessen the likelihood of delegating gTLDs that will have negative net social benefits and to enhance the net social benefits from gTLDs that are designated.</U></B></FONT></SPAN><FONT FACE="Arial"><B><U><FONT SIZE="1"><SPAN STYLE='font-size:7pt'>117<BR>
</SPAN></FONT></U></B></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
</SPAN></FONT><SPAN STYLE='font-size:12pt'><FONT FACE="Verdana, Helvetica, Arial">para 117 – end:<BR>
</FONT><FONT FACE="Times New Roman"> <BR>
<BR>
<BR>
</FONT><FONT FACE="Arial">117. First, it may be wise to continue ICANN’s practice of <B>introducing new gTLDs in discrete, limited rounds</B>. It is impossible to predict the costs and benefits of new gTLDs accurately. By proceeding with multiple rounds, the biggest likely costs—consumer confusion and trademark protection—can be evaluated in the earlier rounds to make more accurate predictions about later rounds.<BR>
</FONT><FONT FACE="Times New Roman"> <BR>
<BR>
<BR>
</FONT><FONT FACE="Arial">118. Second, in order to derive the greatest informational benefits from the next round of<BR>
</FONT><FONT FACE="Times New Roman"> <BR>
</FONT><FONT FACE="Arial">gTLD introductions, ICANN should <B>adopt practices that will facilitate the assessment of the net benefits from the initial rollout of additional gTLDs</B>. Specifically, ICANN should require registries, registrars, and domain names registrants to provide information sufficient to allow the estimation of the costs and benefits of new gTLDs. For example, there might be mandatory reporting of trademark disputes.<BR>
</FONT><FONT FACE="Times New Roman"> <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</FONT></SPAN><FONT SIZE="2"><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Sincerely,<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><FONT SIZE="2"><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Zahid Jamil<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT SIZE="1"><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:9pt'>Barrister-at-law<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT SIZE="2"><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Jamil & Jamil<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT SIZE="2"><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Barristers-at-law<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT SIZE="1"><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:9pt'>219-221 Central Hotel Annexe<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT SIZE="1"><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:9pt'>Merewether Road, Karachi. Pakistan<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT SIZE="1"><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:9pt'>Cell: +923008238230<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT SIZE="1"><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:9pt'>Tel: +92 21 35680760 / 35685276 / 35655025<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT SIZE="1"><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:9pt'>Fax: +92 21 35655026<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT COLOR="#0000FF"><FONT SIZE="1"><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:9pt'>www.jamilandjamil.com</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <<a href="http://www.jamilandjamil.com/">http://www.jamilandjamil.com/</a>> <BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
</SPAN></FONT><FONT SIZE="1"><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:7pt'>Notice / Disclaimer<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT SIZE="1"><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:7pt'>This message contains confidential information and its contents are being communicated only for the intended recipients . If you are not the intended recipient you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this message by mistake and delete it from your system. The contents above may contain/are the intellectual property of Jamil & Jamil, Barristers-at-Law, and constitute privileged information protected by attorney client privilege. The reproduction, publication, use, amendment, modification of any kind whatsoever of any part or parts (including photocopying or storing it in any medium by electronic means whether or not transiently or incidentally or some other use of this communication) without prior written permission and consent of Jamil & Jamil is prohibited.<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><B>From:</B> <FONT COLOR="#0000FF"><a href="owner-bc-gnso@icann.org">owner-bc-gnso@icann.org</a></FONT> [<a href="mailto:owner-bc-gnso@icann.org">mailto:owner-bc-gnso@icann.org</a>] <B>On Behalf Of </B>Deutsch, Sarah B<BR>
<B>Sent:</B> 19 July 2010 15:26<BR>
<B>To:</B> Jon Nevett<BR>
<B>Cc:</B> Zahid Jamil; Phil Corwin; <FONT COLOR="#0000FF"><a href="michaelc@traveler.com">michaelc@traveler.com</a></FONT>; <FONT COLOR="#0000FF"><a href="mike@haven2.com">mike@haven2.com</a></FONT>; <FONT COLOR="#0000FF"><a href="jb7454@att.com">jb7454@att.com</a></FONT>; <FONT COLOR="#0000FF"><a href="randruff@rnapartners.com">randruff@rnapartners.com</a></FONT>; <FONT COLOR="#0000FF"><a href="ffelman@markmonitor.com">ffelman@markmonitor.com</a></FONT>; <FONT COLOR="#0000FF"><a href="bc-GNSO@icann.org">bc-GNSO@icann.org</a><BR>
</FONT> <B>Subject:</B> RE: Re[2]: [bc-gnso] DRAFT BC Public Comments on DAGv4<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><FONT COLOR="#0000FF"><FONT SIZE="2"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'>Jon,<BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><FONT COLOR="#0000FF"><FONT SIZE="2"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'>Thanks for clarifying. If this is the case, then it looks like ICANN kept the high burden of proof for trademark owners on the one hand and ditched other parts of the deal, including that it be in exchange for a rapid (hence the "R" in the name URS) process.<BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><FONT COLOR="#0000FF"><FONT SIZE="2"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'>As a practical matter, I don't see how any trademark owner will be able to prove anything more than they already prove in filing a UDRP case. For example, in most cases, you'll know the infringer took your domain name, which is identical or confusingly similar to your trademark. You may or may not have screen shots of ads on their infringing webpages. You may or may not have accurate WHOIS information about the infringer. You may or may not have evidence that the infringer stole other third party trademarks. <BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
</SPAN></FONT><FONT COLOR="#0000FF"><FONT SIZE="2"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'>There is no certainty for trademark owners about what is meant by "clear and convincing evidence" and how to meet that standard over the evidence we typically submit in the UDRP process. Obviously, there's no way to know the subjective intent of the infringer without full blown litigation and discovery. At a minimum, ICANN needs to give more guidance on this issue.<BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
</SPAN></FONT><FONT COLOR="#0000FF"><FONT SIZE="2"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'>This burden of evidence standard is just one more reason why brand owners will avoid using the URS. <BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
</SPAN></FONT><FONT COLOR="#0000FF"><FONT SIZE="2"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'>Sarah<BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT COLOR="#000080"><FONT SIZE="2"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'>Sarah B. Deutsch <BR>
Vice President & Associate General Counsel <BR>
Verizon Communications <BR>
Phone: 703-351-3044 <BR>
Fax: 703-351-3670<BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT>
<P ALIGN=CENTER>
<FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<HR ALIGN=CENTER SIZE="2" WIDTH="100%">
</SPAN></FONT>
<P>
<FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><B>From:</B> Jon Nevett [<a href="mailto:jon@nevett.net">mailto:jon@nevett.net</a>] <BR>
<B>Sent:</B> Monday, July 19, 2010 3:10 PM<BR>
<B>To:</B> Deutsch, Sarah B<BR>
<B>Cc:</B> Zahid Jamil; Phil Corwin; <FONT COLOR="#0000FF"><a href="michaelc@traveler.com">michaelc@traveler.com</a></FONT>; <FONT COLOR="#0000FF"><a href="mike@haven2.com">mike@haven2.com</a></FONT>; <FONT COLOR="#0000FF"><a href="jb7454@att.com">jb7454@att.com</a></FONT>; <FONT COLOR="#0000FF"><a href="randruff@rnapartners.com">randruff@rnapartners.com</a></FONT>; <FONT COLOR="#0000FF"><a href="ffelman@markmonitor.com">ffelman@markmonitor.com</a></FONT>; <FONT COLOR="#0000FF"><a href="bc-GNSO@icann.org">bc-GNSO@icann.org</a><BR>
</FONT> <B>Subject:</B> Re: Re[2]: [bc-gnso] DRAFT BC Public Comments on DAGv4<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
Sarah:<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Sorry if I was unclear. The intent of the IRT was to have the same legal standard for the UDRP and URS (the same elements -- registration with bad fait intent, etc.), but having a higher burden of proof (clear and convincing vs. preponderance.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Here are the relevant quotes from the IRT report -- <FONT COLOR="#0000FF"><a href="http://www.icann.org/en/announcements/announcement-4-29may09-en.htm">http://www.icann.org/en/announcements/announcement-4-29may09-en.htm</a><BR>
</FONT> <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><FONT SIZE="1"><FONT FACE="Arial"><SPAN STYLE='font-size:9pt'>"The Final Evaluation analysis involves consideration of three basic issues, similar to the standards for a UDRP decision, but requires a<B> much higher burden of proof</B>." (emphasis added)<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><FONT SIZE="1"><FONT FACE="Arial"><SPAN STYLE='font-size:9pt'>"If the Examiner finds that all of these elements are satisfied by <B>clear and convincing evidence</B> and that there is no genuine contestable issue, then the Examiner shall issue a decision in favor of the Complainant." (emphasis added)<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><FONT COLOR="#0000FF"><FONT SIZE="1"><FONT FACE="Arial"><SPAN STYLE='font-size:9pt'><a href="http://www.icann.org/en/announcements/announcement-4-29may09-en.htm">http://www.icann.org/en/announcements/announcement-4-29may09-en.htm</a><BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><FONT SIZE="1"><FONT FACE="Arial"><SPAN STYLE='font-size:9pt'>These positions had a unanimous consensus of the IRT. Not sure the relevance of my status on the IRT, but for the record I was told by the IPC that I wasn't representing registrars on the IRT. If you had heard the crap that I got from my former registrar colleagues, you would understand that I definitely wasn't representing them on the IRT :-).<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><FONT SIZE="1"><FONT FACE="Arial"><SPAN STYLE='font-size:9pt'>As I don't believe that the BC complained about this burden of proof in the past on the IRT, on the STI, or any public comments thereafter, I don't think that we should raise it here. If we think that the URS was changed in a way that is problematic, let's focus on those changes instead of trying to go back on issues that had complete consensus and haven't changed at all.<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><FONT SIZE="1"><FONT FACE="Arial"><SPAN STYLE='font-size:9pt'>Thanks!<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><FONT SIZE="1"><FONT FACE="Arial"><SPAN STYLE='font-size:9pt'>jon<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
On Jul 19, 2010, at 2:39 PM, Deutsch, Sarah B wrote:<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><FONT COLOR="#0000FF"><FONT SIZE="2"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'>Jon,<BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><FONT COLOR="#0000FF"><FONT SIZE="2"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'>Thank you for your many constructive changes. I want to respond to one suggested edit you made below:<BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><FONT COLOR="#0000FF"><FONT SIZE="2"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'><I>*I deleted the clear and convincing evidence issue with regard to the URS. As a member of the IRT, I can say that it clearly was our intent for the URS to have a higher burden of proof than the UDRP -- the legal standard is exactly the same. We wanted the URS to be for "slam dunk" cases. The URS was to be a less expensive alternative to the UDRP cognizant of the fact that 70% of UDRPs go unanswered.</I> <BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
<BR>
</SPAN></FONT><SPAN STYLE='font-size:12pt'><FONT FACE="Arial"> <BR>
</FONT><FONT FACE="Times New Roman"> <BR>
<BR>
</FONT></SPAN><FONT COLOR="#0000FF"><FONT SIZE="2"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'>1. I don't disagree that the URS, like the UDRP, should be used for slam dunk cases. I'm glad you confirmed that the legal standard was supposed to be exactly the same. It's my understanding that proof under the UDRP is in fact based on a preponderance of the evidence standard, not a clear and convincing evidence standard. See below. <BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
</SPAN></FONT><SPAN STYLE='font-size:12pt'><FONT FACE="Verdana, Helvetica, Arial"><B>Section 1.3.1.1 – Burden of Proof (How much proof is necessary?)<BR>
</B></FONT><FONT FACE="Times New Roman"> <BR>
</FONT></SPAN><FONT COLOR="#0000FF"><FONT SIZE="2"><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><B>In the administrative proceeding, the Complainant must prove that each of the three elements contained in Section 4(a) of the Policy are present.<BR>
</B></SPAN></FONT></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT COLOR="#0000FF"><FONT SIZE="2"><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><B>Comment: In general, the Panels recognize a preponderance of the evidence standard. Preponderance of the evidence means that a fact is proved when it is more likely than not that the fact is true.<BR>
</B></SPAN></FONT></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT COLOR="#0000FF"><FONT SIZE="2"><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>2. Rather than delete this sentence in its entirety, I would recommend inserting back in the following single sentence: "The BC recommends that while the URS is intended to deal with "slam dunk," cases, we ask ICANN to clarify that the legal standard remain the exactly the same as that found in the UDRP. ICANN should clarify that while proof of bad faith must be clear, the evidence generally can be established by a proponderance of evidence standard."<BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT COLOR="#0000FF"><FONT SIZE="2"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'>3. I know that you were a valuable member of the IRT and at that time you were representing registrars' views. Other IRT members point out to me one additional point. The "slam dunk" aspect of the URS was in exchange for a quick and cheap process. No one knows how cheap this will wind up being, but there is no question that the "quick" part of this trade off has disappeared. Many IRT participants confirm that the DAG4 doesn't represent anything akin to the deal they thought they had struck. <BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
</SPAN></FONT><FONT COLOR="#0000FF"><FONT SIZE="2"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'>Sarah<BR>
</SPAN></FONT></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
</SPAN></FONT><FONT SIZE="2"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'> <BR>
<FONT COLOR="#000080">Sarah B. Deutsch <BR>
Vice President & Associate General Counsel <BR>
Verizon Communications <BR>
Phone: 703-351-3044 <BR>
Fax: 703-351-3670<BR>
</FONT></SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT>
<P ALIGN=CENTER>
<FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
<HR ALIGN=CENTER SIZE="2" WIDTH="100%">
</SPAN></FONT>
<P>
<FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><B>From:</B> Jon Nevett [<a href="mailto:jon@nevett.net">mailto:jon@nevett.net</a>] <BR>
<B>Sent:</B> Sunday, July 18, 2010 9:40 PM<BR>
<B>To:</B> Zahid Jamil<BR>
<B>Cc:</B> Deutsch, Sarah B; 'Phil Corwin'; <FONT COLOR="#0000FF"><a href="michaelc@traveler.com">michaelc@traveler.com</a></FONT>; <FONT COLOR="#0000FF"><a href="mike@haven2.com">mike@haven2.com</a></FONT>; <FONT COLOR="#0000FF"><a href="jb7454@att.com">jb7454@att.com</a></FONT>; <FONT COLOR="#0000FF"><a href="randruff@rnapartners.com">randruff@rnapartners.com</a></FONT>; <FONT COLOR="#0000FF"><a href="ffelman@markmonitor.com">ffelman@markmonitor.com</a></FONT>; <FONT COLOR="#0000FF"><a href="bc-GNSO@icann.org">bc-GNSO@icann.org</a><BR>
</FONT> <B>Subject:</B> Re: Re[2]: [bc-gnso] DRAFT BC Public Comments on DAGv4<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
Folks:<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Attached is a suggested redraft to bridge the gap. I personally don't agree with some of the arguments I left in the attached, but I tried to keep the longstanding BC positions while toning down the anti-TLD language. I also deleted a couple of the arguments that were objected to in some of the notes I reviewed.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Here are some of the highlights:<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
*I deleted the GPML section.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
*I deleted the clear and convincing evidence issue with regard to the URS. As a member of the IRT, I can say that it clearly was our intent for the URS to have a higher burden of proof than the UDRP -- the legal standard is exactly the same. We wanted the URS to be for "slam dunk" cases. The URS was to be a less expensive alternative to the UDRP cognizant of the fact that 70% of UDRPs go unanswered. Has this issue even been raised before by the BC?<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
*Based on Sarah's helpful e-mail, I left alone the complaint about transferring names after a successful URS as that has been an issue that Zahid, Mike and others in the BC have argued consistently. I do note, however, that transfer was not in the IRT recommendation and the STI agreed to add a year to the registration at the request of the complainant as a compromise. <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
*Again based on Sarah's e-mail, I left the PDDRP section pretty much alone except for an argument about registries warehousing names, but not using them, as that argument didn't make much sense to me. That's exactly the function of a registry to warehouse names until they are sold by registrars. If a registry "reserves" a name and it is not in use at all, the mark holder should be thrilled that it can't be registered by a squatter.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
*I also deleted the paragraph about the Director of Compliance. I don't think it appropriate to comment on those kinds of personnel matters. <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
*I didn't touch the arguments related to community and 13 points (though I personally favor 14 points to avoid gaming -- sorry Ron), as that seems to be longstanding BC position.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
*I didn't do much on the Market Differentiation section either other than soften some of the language.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
I have no idea if my attempt will get consensus or not, but I thought it worthwhile to offer alternative language and I tried hard to find a balance. <BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Thanks.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Jon<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<sti-wt-recommendations-11dec09-en-Final.pdf><BR>
</SPAN></FONT></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> </SPAN></FONT><SPAN STYLE='font-size:12pt'><FONT FACE="Arial">-- <BR>
<BR>
Yvette Miller<BR>
Director, Communications<BR>
The Coalition Against Domain Name Abuse (CADNA) <BR>
1632 Wisconsin Ave, NW <BR>
Washington, D.C. 20007 <BR>
Office: +1 202 223 9355 <BR>
Mobile: +1 202 341 3799<BR>
<a href="yvette@cadna.org">yvette@cadna.org</a><BR>
<BR>
CADNA: <a href="http://www.cadna.org">http://www.cadna.org</a><BR>
<BR>
This message is intended only for the use of the addressee and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify us immediately by return e-mail and delete this e-mail and all attachments from your system.<BR>
</FONT></SPAN><BLOCKQUOTE><BLOCKQUOTE><SPAN STYLE='font-size:12pt'><FONT FACE="Times New Roman"> <BR>
</FONT></SPAN><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'> <BR>
</SPAN></FONT><SPAN STYLE='font-size:10pt'><FONT FACE="Verdana, Helvetica, Arial"> <BR>
</FONT></SPAN></FONT></BLOCKQUOTE><FONT FACE="Arial"><SPAN STYLE='font-size:12pt'><BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Arial"><SPAN STYLE='font-size:12pt'><BR>
</SPAN></FONT>
</BODY>
</HTML>