<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
I am in agreement with Sarah and Mike. and, yes, Mike, thanks for that reminder! I still have the transcripts from part of that session! <div>I recall one graduate student who told us that IPR shouldn't exist on the Internet! <br><br><br><br><hr id="stopSpelling">From: michael@palage.com<br>To: sarah.b.deutsch@verizon.com; philip.sheppard@aim.be; pcorwin@butera-andrews.com; bc-gnso@icann.org<br>Subject: RE: [bc-gnso] RE: Revised Draft BC Position on Establishing Standard Contract for UDRP Providers<br>Date: Wed, 20 Oct 2010 09:28:32 -0400<br><br>
<meta http-equiv="Content-Type" content="text/html; charset=unicode">
<meta name="Generator" content="Microsoft SafeHTML">
<style>
.ExternalClass .ecxshape
{;}
</style>
<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.ecxEmailStyle18
{font-family:'Calibri','sans-serif';color:#1F497D;}
.ExternalClass .ecxMsoChpDefault
{font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;}
.ExternalClass div.ecxWordSection1
{page:WordSection1;}
</style>
<div class="ecxWordSection1">
<p class="ecxMsoNormal"><span style="font-size:11.0pt;font-family:'Calibri','sans-serif';color:#1F497D">Sarah,</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">I share your concerns. In fact this type of rigid “contract”
language is what stalled individual ccTLD participation within the ICANN
process for so long. It was only after ICANN adopted an accountability
framework document that more participation/recognition occurred.</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">I think Phil’s concerns can be address without the hard
coded “contract” language. Having dealt with IGOs over the past
several years I can tell you that getting them to sign “contracts” can
be a complicated process. Therefore making WIPO sign a UDRP provider contract
is likely to run into some complications that would likely draw the
support/empathy of the GAC. Do we really want to pick that fight? </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">Having dealt with WIPO during the past 11 years ago (remember that
first UDRP meeting at Georgetown Sarah/Marilyn – seems almost like
yesterday) I think as a trustee of this process WIPO would be in agreement about
ensuring some uniformity of the rules. So let’s figure how to make
them part of the solution, instead of making them part of the problem.</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">Just my two cents.</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">Best regards,</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">Michael </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>Deutsch,
Sarah B<br>
<b>Sent:</b> Wednesday, October 20, 2010 8:50 AM<br>
<b>To:</b> 'Philip Sheppard'; 'Phil Corwin'; bc-gnso@icann.org<br>
<b>Subject:</b> RE: [bc-gnso] RE: Revised Draft BC Position on Establishing
Standard Contract for UDRP Providers</span></p>
</div>
</div>
<p class="ecxMsoNormal"> </p>
<p class="ecxMsoNormal"><span style="font-size:10.0pt;font-family:'Arial','sans-serif';color:blue">My concern is that by includng the words "contract" this
will be misread by ICANN as a green light to go forward with regulation having
nothing to do with these parties' qualifications even if the idea of
an "other mechanism" is also included as an option. </span></p>
<p class="ecxMsoNormal"> </p>
<p class="ecxMsoNormal"><span style="font-size:10.0pt;font-family:'Arial','sans-serif';color:blue">The following language addresses my concern but keeps the same
meaning Phil originally intended:</span></p>
<p class="ecxMsoNormal"> </p>
<p class="ecxMsoNormal"><span style="font-family:'Arial','sans-serif';color:black">The
Business Constituency (BC) cannot support approval of this or any other UDRP
accreditation application <u>at this time</u> on the grounds that no new UDRP
providers should be accredited until ICANN implements with
all accredited providers a standard mechanism for establishing
uniform rules and procedures and flexible means of delineating and enforcing
arbitration provider responsibilities.</span></p>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-size:10.0pt;font-family:'Arial','sans-serif';color:blue">In the rest of the document, I'd recommend replacing
"contact" with "standard mechanism." </span></p>
</div>
<div>
<p class="ecxMsoNormal"><br>
<span style="font-size:10.0pt;font-family:'Arial','sans-serif';color:blue">Thanks,</span></p>
</div>
<div>
<p class="ecxMsoNormal"><br>
<span style="font-size:10.0pt;font-family:'Arial','sans-serif';color:blue">Sarah</span></p>
</div>
<p class="ecxMsoNormal"><br>
<br>
<span style="font-size:10.0pt;font-family:'Arial','sans-serif';color:navy">Sarah
B. Deutsch <br>
Vice President & Associate General Counsel <br>
Verizon Communications <br>
Phone: 703-351-3044 <br>
Fax: 703-351-3670 </span></p>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<p class="ecxMsoNormal"> </p>
<div class="ecxMsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="ecxMsoNormal" style="margin-bottom:12.0pt"><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'"> Philip Sheppard [mailto:philip.sheppard@aim.be]
<br>
<b>Sent:</b> Wednesday, October 20, 2010 3:29 AM<br>
<b>To:</b> 'Phil Corwin'; Deutsch, Sarah B; bc-gnso@icann.org<br>
<b>Subject:</b> RE: [bc-gnso] RE: Revised Draft BC Position on Establishing
Standard Contract for UDRP Providers</span></p>
<div>
<p class="ecxMsoNormal"><span style="font-size:10.0pt;font-family:'Arial','sans-serif'">I
share Sarah's concern but agree with Phil that our current language is
flexible:</span></p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal" style="text-align:justify"><span style="font-family:'Arial','sans-serif'">The
Business Constituency (BC) cannot support approval of this or any other UDRP
accreditation application <u>at this time</u> on the grounds that no new UDRP
providers should be accredited until ICANN implements a standard contract
with all accredited providers <strong><span style="font-family:'Arial','sans-serif'">or
develops some other mechanism </span></strong>for establishing uniform rules
and procedures and flexible means of delineating and enforcing arbitration
provider responsibilities. (emphasis added)<br>
<br>
Philip</span></p>
<p class="ecxMsoNormal" style="text-align:justify"> <span style="font-family:'Arial','sans-serif'"></span></p>
</div>
</div></div> </body>
</html>