<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<font style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Consensus understood/I'm working on a revised draft and will circulate it later today.
<br>
Philip S. Corwin <br>
Partner, Butera & Andrews <br>
1301 Pennsylvania Ave., NW <br>
Suite 500 <br>
Washington, DC 20004 <br>
202-347-6875/Office <br>
202-255-6172/Cell <br>
<br>
"Luck is the residue of design." <br>
-- Branch Rickey</font><br>
<br>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<font style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><b>From</b>: Michael D. Palage [mailto:michael@palage.com]
<br>
<b>Sent</b>: Wednesday, October 20, 2010 09:28 AM<br>
<b>To</b>: 'Deutsch, Sarah B' <sarah.b.deutsch@verizon.com>; 'Philip Sheppard' <philip.sheppard@aim.be>; Phil Corwin; bc-gnso@icann.org <bc-gnso@icann.org>
<br>
<b>Subject</b>: RE: [bc-gnso] RE: Revised Draft BC Position on Establishing Standard Contract for UDRP Providers
<br>
</font> <br>
</div>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Sarah,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><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?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Just my two cents.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Michael
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><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<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><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><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><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><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><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><o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><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><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:blue">Thanks,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:blue">Sarah</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><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><o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal" 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><o:p></o:p></p>
<div>
<p class="MsoNormal"><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><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" 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<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"> <span style="font-family:
"Arial","sans-serif""><o:p></o:p></span></p>
</div>
</div>
</body>
</html>