<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:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Cambria;
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:11.0pt;
font-family:"Calibri","sans-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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
p.Default, li.Default, div.Default
{mso-style-name:Default;
margin:0in;
margin-bottom:.0001pt;
text-autospace:none;
font-size:12.0pt;
font-family:"Cambria","serif";
color:black;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:898903470;
mso-list-type:hybrid;
mso-list-template-ids:1451128454 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1
{mso-list-id:1352488061;
mso-list-type:hybrid;
mso-list-template-ids:538476784 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">On Saturday I sent the e-mail below to all BC members, requesting that the BC weigh in with the Board prior to its special meeting scheduled for this Thursday, February 28<sup>th</sup> at which the request of
the ACDR to be an accredited UDRP provider is on the consent calendar. While the listing does not indicate whether the Board is lined up to approve or disapprove the request, one must presume that it would not be on the consent calendar if approval was not
contemplated.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Here is additional information regarding this matter:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">ACDR’s application to be a UDRP provider was opened to public comment on September 28, 2010. In other words this matter was first contemplated almost two and one half years ago and ICANN has said and
done nothing more on it since that time <a href="http://www.icann.org/en/news/announcements/announcement-28sep10-en.htm">
http://www.icann.org/en/news/announcements/announcement-28sep10-en.htm</a> .<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">In addition to the BC comment requesting that no new UDRP providers be accredited until ICANN developed a standard contract for all UDRP providers, the IPC also expressed concerns about the application.
All comments may be viewed at <a href="http://forum.icann.org/lists/acdr-proposal/">
http://forum.icann.org/lists/acdr-proposal/</a> . A summary of comments prepared by ICANN staff is below.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="color:#1F497D">In view of the facts that this matter has been dormant for the past 2.5 years, that ICANN has added it to the Board’s calendar without any public notice other than the publication of the calendar, that ICANN
has not stated whether and to what extent it has taken into account and accommodated the public comments (or whether ACDR has submitted a revised proposal) – and that this matter will be discussed and decided by the Board in about 72 hours –<u>I am again requesting
that the BC take immediate action to communicate the following to the Board:<o:p></o:p></u></span></b></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><b><span style="color:#1F497D">Reiterate its position that no new UDRP providers should be approved absent development of a standard contract for all UDRP providers.<o:p></o:p></span></b></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><b><span style="color:#1F497D">Defer action on this matter until a public notice has been published advising the community of whether and to what extent ACDR’s application to be a UDRP provider has been revised to accommodate
the comments that were received in 2010.<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="color:#1F497D">The BC has been vigilant in asserting its established policy positions in other matters when the need to do so has arisen, and I would hope and expect that it will do the same in this case.<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best regards, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Philip<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">ICANN staff summary of comments received ---<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="http://forum.icann.org/lists/acdr-proposal/msg00007.html">http://forum.icann.org/lists/acdr-proposal/msg00007.html</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="Default"><o:p> </o:p></p>
<p class="Default"><b><span style="font-size:11.5pt">Summary and Analysis of Public Comments for ACDR Proposal to be Recognized as an Official Dispute Resolution Provider Under the UDRP
</span></b><span style="font-size:11.5pt"><o:p></o:p></span></p>
<p class="Default"><b><span style="font-size:11.5pt">Comment period: 28 September 2010 – 28 October 2010
</span></b><span style="font-size:11.5pt"><o:p></o:p></span></p>
<p class="Default"><b><span style="font-size:11.5pt">Background </span></b><span style="font-size:11.5pt"><o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">The Arab Center for Domain Name Dispute Resolution (ACDR) submitted a proposal to ICANN to be recognized as an official dispute resolution provider under the UDRP. The proposal was submitted pursuant to the
process specified at </span><span style="font-size:11.5pt;color:blue">http://www.icann.org/en/dndr/udrp/provider-approval-process.htm
</span><span style="font-size:11.5pt">. <o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">At its 5 August 2010 meeting, the Board approved staff’s recommendation to publish the ACDR proposal for a public comment for a period of not less than 30 days.
<o:p></o:p></span></p>
<p class="Default"><b><span style="font-size:11.5pt">Comments received </span></b><span style="font-size:11.5pt"><o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">A total of seven comments were received.
<o:p></o:p></span></p>
<p class="Default"><b><span style="font-size:11.5pt">Summary of relevant comments
</span></b><span style="font-size:11.5pt"><o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">George Kirikos of Leap Financial Services Inc. commented that ICANN should not approve another UDRP provider and should instead prioritize bringing existing UDRP providers under contract.
</span><span style="font-size:11.5pt;color:blue">http://forum.icann.org/lists/acdr-proposal/msg00000.html
</span><span style="font-size:11.5pt"><o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">Barbara Madonik of Unicom Communication Consultants Inc. commented that while she applauds the attempt to establish an international center, the locale of the ACDR “might not be ideal” and ICANN should seek
a more neutral location to serve both Arab and non-Arab countries. </span><span style="font-size:11.5pt;color:blue">http://forum.icann.org/lists/acdr-proposal/msg00001.html
</span><span style="font-size:11.5pt"><o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">Moe Alramahi expressed support for the ACDR’s proposal, noting that it is “reasonable, comprehensive and robust.” Mr. Alramahi also noted that recent developments in the domain name system, such as the introduction
of IDNs and gTLDs will lead to increased disputes, and local knowledge and expertise will expedite the handling of those disputes.
</span><span style="font-size:11.5pt;color:blue">http://forum.icann.org/lists/acdr-proposal/msg00002.html
</span><span style="font-size:11.5pt"><o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">A commenter identified as Volodya submitted comments covering positive and negative aspects of the ACDR proposal. Among the positives are the location of the Center, which will provide a “more balanced process”;
the provision of multilingual services, and the multinational composition of the initial panel. Among the negatives are the apparent view of the ACDR to enforce the “strong protection of Intellectual Property Rights,” which raises questions of the ACDR’s commitment
to <o:p></o:p></span></p>
<p class="Default" style="page-break-before:always"><span style="font-size:11.5pt">neutrality. Further, the Advisory Board’s selection is based upon experience in “intellectual property protection” – again demonstrating a bias. Though the panel selection procedures
allow for persons to be chosen that “do[] not openly show support for Intellectual Property,” the remainder of the document “suggests . . . a deliberate attempt to derail the neutral process of domain name resolution.” Volodya notes that this could result
in biased panels, and would not represent the “complexity of the IP debate.” </span>
<span style="font-size:11.5pt;color:blue">http://forum.icann.org/lists/acdr-proposal/msg00003.html
</span><span style="font-size:11.5pt"><o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">Steve DelBianco on behalf of the ICANN Business Constituency (BC) submitted the BC’s comment that it cannot support the approval of ACDR’s proposal nor any other proposal until “ICANN implements a standard mechanism
for establishing uniform rules and procedures and flexible means of delineating and enforcing arbitration provider responsibilities.” The BC noted that gTLD names can only be registered through accredited registrars under contract with ICANN, but non-contracted
UDRP providers have the power to order the involuntary deletion or transfer of those same names. The BC raised a concern of the consistency of the UDRP process among providers, and noted that these concerns grow if additional providers are approved without
first creating a uniform framework. Therefore, the BC “advocates” that ICANN should first standardize a framework for UDRP providers – allowing for regular ICANN review and ultimate loss of approval where appropriate – prior to approving any new providers.
The creation of a uniform framework – including constraints on provider authority – is increasingly important with the anticipated expansion of gTLDs and jurisdictions where disputes are likely to arise. This will further the goal of consistency among decisions
and will allow the UDRP to remain “an expedited an lower cost remediation” to address cybersquatting. The BC notes that the standardization of provider practices does not require a full review of the substantive elements of the UDRP.
</span><span style="font-size:11.5pt;color:blue">http://forum.icann.org/lists/acdr-proposal/msg00004.html
</span><span style="font-size:11.5pt"><o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">J. Scott Evans on behalf of the Intellectual Property Constituency (IPC) submitted conditional approval of the ACDR proposal, noting the geographic and cultural diversity the ACDR would bring to the UDRP process
at a time where Arabic expertise is needed. The IPC provides substantive comment on portions of the ACDR’s proposal, suggesting that a proposal adopting all of the IPC’s modifications would be appropriate for approval, but if the ACDR elects not to incorporate
all revisions, the proposal should be presented for further public comment. The IPC also cautioned that “any enthusiasm for the ACDR’s proposal must be tempered by the desire to ensure a predictable and equitable system of domain name dispute resolution –
as opposed to any profit-driven ‘race to the bottom’ between UDRP providers.” The IPC’s substantive comments on the proposal identified issues such as potential inconsistencies with the UDRP and its Rules on electronic filings, commencement dates, and definition
of “writings.” The IPC also recommends changes to the fee structure proposed, with an eye to minimizing fees to complainants. Additional recommendations include: inclusion of statements on the commitment to impartiality and fairness; additional information
on the start-up <o:p></o:p></span></p>
<p class="Default" style="page-break-before:always"><span style="font-size:11.5pt">period and background and track record for handling ADR proceedings; and clarification of the role of a presiding panelist.
</span><span style="font-size:11.5pt;color:blue">http://forum.icann.org/lists/acdr-proposal/msg00006.html
</span><span style="font-size:11.5pt"><o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">Philip Corwin on behalf of the Internet Commerce Association (ICA) submitted its opposition to the ACDR proposal. As with the BC comments, the ICA notes that it “strongly opposes” the approval of any new UDRP
dispute resolution provider until ICANN forms a uniform, enforceable agreement with all UDRP providers, to assure due process to all parties to a UDRP actions, and to prevent forum shopping among UDRP providers. The ICA provides substantial discussion of the
need for enforceable agreements with UDRP providers, echoing many comments made by the BC regarding the contractual regime in place for the registration of domain names within gTLDs and the lack of contracts with the entities that may force involuntary deletions
or transfers of those names. The ICA emphasizes the need for uniformity of process that can be achieved through enforceable agreements. The ICA comments refer to prior ICA communications on this same topic, including comments relating to a proposal of another
UDRP provider to allow for reduced fees for UDRP proceedings where no response is filed. The ICA provides a suggested list of topics that such an agreement should encompass. The ICA then identified deficiencies to be addressed in ACDR’s proposal. These deficiencies
include: a lack of “meaningful” information on the types of arbitration handled by the ACDR’s component entities and their “track records”; more fulsome documentation of the preparation of panel training materials; no representations of monthly case handling
capabilities; the “meaningless” assertion of being able to handle 5,000 proceedings in a start-up period, particularly when compared to the numbers of cases handled by existing UDRP providers; a lack of description of communications with other UDRP providers,
and a commitment to researching decisions of other providers so as to assure consistency.
<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">ICA notes its opinion that if ACDR is approved as a provider, a strict limitation on the number of cases it may handle, subject to an ICANN quality review before the limitation can be lifted. Finally, ICA comments
on the confidentiality of ACDR’s internal operating procedures and that the community will not be able to review those for fairness.
</span><span style="font-size:11.5pt;color:blue">http://forum.icann.org/lists/acdr-proposal/msg00005.html
</span><span style="font-size:11.5pt"><o:p></o:p></span></p>
<p class="Default"><b><span style="font-size:11.5pt">Analysis and Next Steps </span>
</b><span style="font-size:11.5pt"><o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">The commenters were of varied opinions on the ACDR’s proposal: Three commenters (George Kirikos, the BC and the ICA) were expressly against the ACDR proposal. The IPC noted its conditional approval subject to
incorporation of suggested changes, and only one commenter (Alramahi) submitted unqualified support for the ACDR proposal.
<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">Some commenters identified the fact that the ACDR would bring greater cultural and geographic diversity to the UDRP providers, as well as expand multi-lingual abilities of UDRP providers. Though one commenter
questioned whether Jordan is a neutral <o:p></o:p></span></p>
<p class="Default" style="page-break-before:always"><span style="font-size:11.5pt">enough locale for a UDRP provider, if the ACDR were to be approved as a provider, such approval would not limit the ability for others in the region to seek to become an approved
provider as well. <o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">The three commenters opposed to the approval of the ACDR proposal noted their opinion that ICANN should not approve
<i>any </i>additional UDRP providers prior to establishing a uniform, enforceable arrangement with all existing UDRP providers. The ICA also recommended that ICANN undertake an expert third party review of the operation of UDRP generally.
<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">One commenter, Volodya, raised the question of the neutrality of the panelists to be appointed by the center, based upon the statement in the ACDR’s proposal that it will enforce the “strong protection of Intellectual
Property Rights.” No other commenters raised this neutrality argument. The IPC and the ICA each provided substantial comments on the substance of the ACDR proposal. The IPC noted that if all of its suggestions were addressed, then it may be appropriate for
ICANN to approve the ACDR’s application; otherwise the proposal should be posted for additional public comment. The ICA, after attempting to evaluate the proposal against the published criteria for applying to be a UDRP provider, suggested that there is no
way for ICANN to proceed to approval of the ACDR’s proposal. <o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">Some areas identified by the IPC and ICA include:
<o:p></o:p></span></p>
<p class="Default" style="margin-bottom:.5pt"><span style="font-size:11.5pt">(i) Provision of more detail on track record in handling alternative dispute resolution proceedings;
<o:p></o:p></span></p>
<p class="Default" style="margin-bottom:.5pt"><span style="font-size:11.5pt">(ii) A more precise statement regarding the case load administrative capacity that the ACDR anticipates handling;
<o:p></o:p></span></p>
<p class="Default" style="margin-bottom:.5pt"><span style="font-size:11.5pt">(iii) Better documentation regarding the creation of training materials;
<o:p></o:p></span></p>
<p class="Default" style="margin-bottom:.5pt"><span style="font-size:11.5pt">(iv) Revision of specific terms in the supplemental rules to better align with the UDRP process;
<o:p></o:p></span></p>
<p class="Default" style="margin-bottom:.5pt"><span style="font-size:11.5pt">(v) Revision to the ACDR’s fee structure; and
<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">(vi) Release of confidential internal operating procedures.
<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">ICANN is providing the ACDR with a copy of this summary and analysis so that the ACDR may determine how to respond and whether it wishes to revise any portion of its proposal. When a revised proposal is received,
the proposal will be reviewed to determine if further public comment is advisable prior to presentation to the Board for consideration. Further comment may not be necessary, for example, if the ACDR elects to not alter its fee schedule, as the UDRP allows
providers to set their own fees. <o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">Separate from the ACDR proposal, ICANN has been undertaking a process to review its relationships with UDRP providers, and that review is ongoing.
<o:p></o:p></span></p>
<p class="Default"><b><span style="font-size:11.5pt">Contributors (chronological order of posting):
</span></b><span style="font-size:11.5pt"><o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">George Kirikos, President, Leap of Faith Financial Services Inc.
<o:p></o:p></span></p>
<p class="Default" style="page-break-before:always"><span style="font-size:11.5pt">Barbara Madonik, President, Unicom Communication Consultants Inc.
<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">Moe Alramahi, Law Lecturer/ Domain Name Panelist (ADNDRC)
<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">Volodya <o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">Steve DelBianco, Business Constituency
<o:p></o:p></span></p>
<p class="Default"><span style="font-size:11.5pt">J. Scott Evans, Intellectual Property Constituency
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.5pt">Philip Corwin, Internet Commerce Association</span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Philip S. Corwin, Founding Principal</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Virtualaw LLC</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">1155 F Street, NW</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Suite 1050</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Washington, DC 20004</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">202-559-8597/Direct</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">202-559-8750/Fax</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">202-255-6172/cell</span></b><b><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:navy"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Twitter: @VlawDC</span></b><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">"Luck is the residue of design" -- Branch Rickey</span></i></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="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""> Phil Corwin
<br>
<b>Sent:</b> Saturday, February 23, 2013 2:36 PM<br>
<b>To:</b> Phil Corwin; bc-gnso@icann.org<br>
<b>Subject:</b> RE: ICANN Board Considering New UDRP Provider<br>
<b>Importance:</b> High<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Fellow BC Members:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">In October 2010 the BC adopted a position of non-support the accreditation of the Arab Center for Domain name Dispute Resolution or any other new gTLD provider “until ICANN implements a standard mechanism<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">for establishing uniform rules and procedures and flexible means of delineating and enforcing arbitration provider responsibilities.” I was the rapporteur for the position statement but it received consensus
support from the entire BC, with many trademark owners expressing concern about a diminishment of UDRP standards in the absence of some standard and enforceable mechanism to assure uniform application of that policy.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="color:#1F497D">The accreditation of the ACDR is on the ICANN Board’s Consent calendar for its meeting of Thursday, February 28<sup>th</sup>. I am hereby requesting that the BC communicate this position statement to the Board
in advance of its discussion of that matter, as it has done in the past on other issues for which the BC has a relevant established position.<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thank you for your consideration of this request.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best, Philip<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="http://forum.icann.org/lists/acdr-proposal/msg00004.html">http://forum.icann.org/lists/acdr-proposal/msg00004.html</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">Business Constituency (BC) Comment on ICANN Proposal<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">to Recognize New Domain Name Dispute Provider<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New"">*Background*
<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New"">There is a pending request for comment regarding the application of the Arab<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New"">Center for Domain Name Dispute Resolution (ACDR) to become a certified<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New"">Uniform Dispute Resolution Procedure (UDRP) arbitration provider.<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New""><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New"">*Summary*
<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New"">The Business Constituency (BC) cannot support approval of this or any other<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New"">UDRP accreditation application at this time on the grounds that no new UDRP<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New"">providers should be accredited until ICANN implements a standard mechanism<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New"">for establishing uniform rules and procedures and flexible means of<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New"">delineating and enforcing arbitration provider responsibilities.<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">*Explanation*
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">The BC notes that the voluntary registration or renewal of a gTLD domain<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">must be undertaken via an ICANN-accredited registrar. All registrars are<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">subject to a uniform contractual agreement with ICANN, the Registrar<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">Accreditation Agreement (RAA). ICANN recently strengthened the RAA with<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">additional amendments and the addition of flexible enforcement options, and<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">a Final Report proposing additional RAA amendments has just been delivered<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">to the GNSO for its consideration.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">In stark contrast, the involuntary termination or transfer of a domain can<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">be ordered under the authority of a UDRP provider that has been accredited<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">by ICANN but which is not bound by any constraints on or requirements<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">pertaining to the exercise of that delegated authority. This has led to<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">increasing concerns about the lack of adequate procedural and substantive<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">consistency in the UDRP process. Such concerns are likely to grow if<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">additional providers are accredited in the absence of the uniform framework<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">of a standard mechanism.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New"">The BC strongly advocates that ICANN must first implement a standard<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New"">mechanism with any and all UDRP arbitration providers that defines and<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New"">constrains their authority and powers, and establishes regular and<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New"">standardized review by ICANN with flexible and effective means of<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New"">enforcement. The ultimate sanction of cancelling accreditation is an extreme<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New"">sanction that ICANN has demonstrated a reluctance to initiate in other<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Courier New"">contexts.
<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New""> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">ICANN appears to be transitioning from an environment in which the vast<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">majority of UDRP cases (approximately 98%) were handled by two arbitration<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">providers (WIPO and NAF) and in which significant gTLDs were based in a<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">limited number of national jurisdictions to one in which the majority of<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">gTLDs and UDRP providers may well be headquartered in a widely distributed<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">group of jurisdictions.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">In the future, business interests may well be investing substantial amounts<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">in these new gTLDs, for both defensive, new branding, and other purposes.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">In this type of environment it is even more important that all UDRP<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">providers be subject to uniform and enforceable responsibilities, as that is<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">the only means of furthering the goal that UDRP decisions are consistent<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">within and among UDRP providers, and that the UDRP remains an expedited and<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">lower cost remediation for addressing cybersquatting.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">The BC notes that the issue of whether UDRP providers should be under a<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">standard mechanism with ICANN is almost entirely separable from the question<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">of whether the UDRP evaluation standards for determining the existence of<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">cybersquatting should be reformed. There is no need to debate the<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">substantive elements of the UDRP in order to address the fundamental issue<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">of whether UDRP providers should be under a standard mechanism.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">***
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">The rapporteur for these comments was Phil Corwin.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New"">ICANN Business Constituency<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New""><a href="http://www.bizconst.org">http://www.bizconst.org</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Philip S. Corwin, Founding Principal</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Virtualaw LLC</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">1155 F Street, NW</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Suite 1050</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Washington, DC 20004</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">202-559-8597/Direct</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">202-559-8750/Fax</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">202-255-6172/cell</span></b><b><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:navy"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Twitter: @VlawDC</span></b><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">"Luck is the residue of design" -- Branch Rickey</span></i></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="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"">
<a href="mailto:owner-bc-gnso@icann.org">owner-bc-gnso@icann.org</a> [<a href="mailto:owner-bc-gnso@icann.org">mailto:owner-bc-gnso@icann.org</a>]
<b>On Behalf Of </b>Phil Corwin<br>
<b>Sent:</b> Friday, February 22, 2013 3:37 PM<br>
<b>To:</b> <a href="mailto:bc-gnso@icann.org">bc-gnso@icann.org</a><br>
<b>Subject:</b> [bc-gnso] ICANN Board Considering New UDRP Provider<br>
<b>Importance:</b> High<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">FYI, on the consent calendar for the 2/28 ICANN Board Meeting
<a href="https://www.icann.org/en/groups/board/documents/agenda-28feb13-en.htm">https://www.icann.org/en/groups/board/documents/agenda-28feb13-en.htm</a> ---<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span lang="EN">Arab Center for Dispute Resolution's Proposal to Serve as UDRP Provider<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span lang="EN"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span lang="EN"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span lang="EN">You may recall that the BC is on record as stating several years back (don’t have time right now to find document) that ICANN should not accredit any new UDRP providers until it developed a standard contract for all providers.
My recollection is that this provider was one of the two being considered at that time and is based in Amman, Jordan.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN">In a related matter, while ICANN announced yesterday that NAF would be a URS provider, it did not state whether NAF would be placed under contract per the STI recommendation.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Philip S. Corwin, Founding Principal</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Virtualaw LLC</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">1155 F Street, NW</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Suite 1050</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Washington, DC 20004</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">202-559-8597/Direct</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">202-559-8750/Fax</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">202-255-6172/cell</span></b><b><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:navy"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Twitter: @VlawDC</span></b><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">"Luck is the residue of design" -- Branch Rickey</span></i></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">
<hr size="1" width="100%" noshade="" style="color:#A0A0A0" align="center">
</span></div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">No virus found in this message.<br>
Checked by AVG - <a href="http://www.avg.com">www.avg.com</a><br>
Version: 2013.0.2899 / Virus Database: 2639/6119 - Release Date: 02/20/13<o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">
<hr size="1" width="100%" noshade="" style="color:#A0A0A0" align="center">
</span></div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">No virus found in this message.<br>
Checked by AVG - <a href="http://www.avg.com">www.avg.com</a><br>
Version: 2013.0.2899 / Virus Database: 2639/6119 - Release Date: 02/20/13<o:p></o:p></span></p>
</div>
</body>
</html>