<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
<div><br></div>thanks all. Good work going on here in the discussions and exchanges of views. <div><br><div>Steve and I will be discussing a process to get to a BC outcome. </div><div><br></div><div>. </div><div><br></div><div>Everyone's work and focus on this is much appreciated. </div><div><br></div><div>I know this is busy times and our members have diverse views in some cases, but in others, I think we have common ground. </div><div>I do want to make one comment. The BC has a position of supporting managed, responsible introduction of gTLDs [and IDNs] that expand the names space in a differentiated manner. We also have a position about ICANN acting responsibly. </div><div><br></div><div>I have seen a few comments from BC members that seem to indicate a concern that the BC opposes the expansion of new gTLDs. Our position is much more responsible than that, but it does include addressing the challenges of expansion of the gTLD space. </div><div><br></div><div>So, just to assure members who thought that there was a rewrite of the BC position on expansion, I don't see that in the comments. However, I appreciate the concern about tone and I think that is being addressed. </div><div><br></div><div>Stay tuned for a suggested approach after I talk with Steve, as V.Chair, Policy Coordination. </div><div><br></div><div>Marilyn Cade</div><div>BC Chair</div><div><br></div><div><br><br><br><br><br><hr id="stopSpelling">From: cgmartin@uscib.org<br>To: jon@nevett.net; zahid@dndrc.com<br>CC: sarah.b.deutsch@verizon.com; pcorwin@butera-andrews.com; michaelc@traveler.com; mike@haven2.com; jb7454@att.com; randruff@rnapartners.com; ffelman@markmonitor.com; bc-GNSO@icann.org<br>Date: Mon, 19 Jul 2010 09:57:57 -0400<br>Subject: RE: Re[2]: [bc-gnso] DRAFT BC Public Comments on DAGv4<br><br>
<style>
.ExternalClass p.ecxMsoNormal, .ExternalClass li.ecxMsoNormal, .ExternalClass div.ecxMsoNormal
{margin-bottom:.0001pt;font-size:12.0pt;font-family:'Times New Roman','serif';}
.ExternalClass a:link, .ExternalClass span.ecxMsoHyperlink
{color:blue;text-decoration:underline;}
.ExternalClass a:visited, .ExternalClass span.ecxMsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
.ExternalClass span.ecxEmailStyle17
{font-family:'Calibri','sans-serif';color:#1F497D;}
.ExternalClass .ecxMsoChpDefault
{font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;}
.ExternalClass div.ecxSection1
{page:Section1;}
</style>
<div class="ecxSection1">
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:'Calibri','sans-serif';color:#1F497D">Hi all. USCIB is currently in the process of drafting our own
DAG4 input, and so we cannot comment directly on substantive language at this
time. However, on RPMs, USCIB generally supported the IRT’s
recommendations. Many of the BC’s comments in the current draft(s)
reflect the fact that the current DAG does not contain the thrust of those
recommendations and thus we support language drawing attention to those
failings and many of the suggested remedies, including much of what is said on
mechanisms like URS and the Trademark Clearinghouse. We stand by the
incorporation of these items and language supporting the general thrust of the IRT
recommendations in the BC comments. </span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:'Calibri','sans-serif';color:#1F497D"> </span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:'Calibri','sans-serif';color:#1F497D">On tone of the document, I agree that some language from the
original draft could be shifted to more positively construe our input. I think
Jon’s edits do a pretty good job in terms of changing the tone (again, no
comment directly on the substantive language used except for above).</span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:'Calibri','sans-serif';color:#1F497D"> </span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:'Calibri','sans-serif';color:#1F497D">Cheers,</span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:'Calibri','sans-serif';color:#1F497D">Chris</span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:'Calibri','sans-serif';color:#1F497D"> </span></p>
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:'Calibri','sans-serif';color:#1F497D"> </span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="ecxMsoNormal"><b><span style="font-size:10.0pt;font-family:'Tahoma','sans-serif'">From:</span></b><span style="font-size:10.0pt;font-family:'Tahoma','sans-serif'">
owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <b>On Behalf Of </b>Jon
Nevett<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'; michaelc@traveler.com;
mike@haven2.com; jb7454@att.com; randruff@rnapartners.com;
ffelman@markmonitor.com; bc-GNSO@icann.org<br>
<b>Subject:</b> Re: Re[2]: [bc-gnso] DRAFT BC Public Comments on DAGv4</span></p>
</div>
</div>
<p class="ecxMsoNormal"> </p>
<p class="ecxMsoNormal">Folks:</p>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal">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.</p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal">Here are some of the highlights:</p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal">*I deleted the GPML section.</p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal">*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?</p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal">*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.
</p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal">*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.</p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal">*I also deleted the paragraph about the Director of
Compliance. I don't think it appropriate to comment on those kinds of
personnel matters. </p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal">*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.</p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal">*I didn't do much on the Market Differentiation section
either other than soften some of the language.</p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal">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. </p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal">Thanks.</p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal">Jon</p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
</div></div></div> </body>
</html>