<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: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;}
@font-face
{font-family:Verdana;
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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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.ecxmsonormal, li.ecxmsonormal, div.ecxmsonormal
{mso-style-name:ecxmsonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ecxmsochpdefault, li.ecxmsochpdefault, div.ecxmsochpdefault
{mso-style-name:ecxmsochpdefault;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.ecxmsohyperlink
{mso-style-name:ecxmsohyperlink;}
span.ecxmsohyperlinkfollowed
{mso-style-name:ecxmsohyperlinkfollowed;}
span.ecxemailstyle17
{mso-style-name:ecxemailstyle17;}
p.ecxmsonormal1, li.ecxmsonormal1, div.ecxmsonormal1
{mso-style-name:ecxmsonormal1;
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.ecxmsohyperlink1
{mso-style-name:ecxmsohyperlink1;
color:blue;
text-decoration:underline;}
span.ecxmsohyperlinkfollowed1
{mso-style-name:ecxmsohyperlinkfollowed1;
color:purple;
text-decoration:underline;}
span.ecxemailstyle171
{mso-style-name:ecxemailstyle171;
font-family:"Calibri","sans-serif";
color:windowtext;}
p.ecxmsochpdefault1, li.ecxmsochpdefault1, div.ecxmsochpdefault1
{mso-style-name:ecxmsochpdefault1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle28
{mso-style-type:personal-reply;
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";}
.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">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">In response to John’s inquiry – I’m not the one characterizing this as a policy matter, I am the one reporting that ICANN has stated it will develop “effective
and feasible <b>policy…rules” </b>for post-delegation RPMs,<b> </b>and that it intends to “reconfigure” (as in revisit and alter) the URS.<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">The relevant provisions in the draft budget are:<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"><b><i><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Rights Protection Mechanisms</span></i></b><i><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">. Implementation
of additional post-delegation rights protection mechanisms will take place. These efforts include work with the community to develop effective and feasible
<b>policy</b> and administrative <b>rules</b>, and the engagement of one or more Uniform Rapid Suspension (URS) providers.<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></i></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">…and…<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Uniform Rapid Suspension (URS) – $175K
</span></i></b><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><i><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">At present there is a significant gap between the features specified for the URS procedure and the desired cost. In order to bridge this gap we
will: hold two summit sessions to <b>reconfigure the URS to arrive at a lower cost model</b> (one session in FY12 budget and another in this FY13 plan), conduct a process to develop and
<b>finalize URS Model</b> in consultation with current UDRP providers and community members; and
<b>conduct RFP based on URS Model</b> and select URS providers. The goal is have a URS program in place and providers contracted and onboard by June 2013.<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></i></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The first reference characterizes this as a process to develop policy rules, and differentiates that from administrative rules (the latter falling
within the implementation category).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The second reference characterizes their goal as reconfiguring URS to meet the promised price point, and to put out a Request for Proposals (RFP)
from prospective providers based on that newly reconfigured RFP model, not on the current model.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Their intent clearly goes beyond mere implementation of what is in the Guidebook now – in fact, they explicitly state that there is a “gap” between
the features of the URS as it now stands and the low filing fee that was promised. (Those ‘features’ are fairly fundamental, so it’s not clear to me how much they can be tinkered with.)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I also want to point out that what’s in the Budget is very different from the responses Kurt gave to questions I raised about URS implementation at
the last two ICANN meetings. (I have taken it as a given that URS will, in fact must, be in place around the time that the first new gTLDs get beyond sunrise sales and open domain purchases to the general public – and my goal in raising questions has been
to assure that sufficient time and thought is afforded to URS implementation so that it is a credible and effective mechanism that affords adequate due process to both parties. Also, in an aside, if ICANN fails to meet its “goal” of having the program and
providers in place by June 2013 that could negatively impact the timing of new gTLD launches.)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">In Dakar Kurt conceded that arbitration providers like WIPO and NAF had informed ICANN that they would not bid on any URS RFP because the pricing
would not accommodate the fees they pay to qualified experts. He also stated that an Implementation Advisory Group (IAG) would be established for URS, just like the one that was already up and running for the Trademark Clearinghouse, within a month – that
obviously never happened.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">In San Jose he stated that an RFP would be issued within a month to solicit URS providers. That statement has now been negated by the Budget document,
which indicates that the RFP is many, many months away, after the two summits have been held and there is further consultation with current UDRP providers and the community, and will only be issued after the URS has been reconfigured into a significantly revised
model. It is unclear from this statement whether the entire ICANN community will be able to participate in those Summits or whether they will be restricted to a narrower group of participants.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Adding all that up, I think it’s pretty clear that what is intended for URS is not mere implementation but substantive recasting that falls within
the policy category.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Final policy thought: I think it is axiomatic that URS must be narrowed if achieving the promised $300-500 price point is ICANN’s top priority and
is to be realized (although I am skeptical that can be met in any circumstances, given what expert trademark attorneys charge for their time – even a “slam dunk” case requires some time to research and affirm the complainant’s rights, evaluate any registrant
response, and prepare a report on the decision). The filing fee for a single domain, single panelist UDRP is about $1300; if the URS were to be “reconfigured” (as some want, but ICA opposes) to lower the complainant’s burden of proof to the same as that for
UDRP then the consideration a case must be afforded by the expert increases because it contemplates cases that are more shades of grey than black and white – so that is incompatible with pricing it at less than one-half or even less than one-quarter of the
current UDRP filing fee. The promised fee range does not pay for even one hour of an expert’s time – and the arbitration provider must add on their own administrative costs.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Final process thought: In a time of continuing economic stress holding these URS “summits” on a date and at a location other than in conjunction with
the Prague and subsequent full ICANN meetings imposes an economic burden that will likely prevent many who might wish to participate from doing so (assuming they are allowed to, as it’s not clear that the full community will be invited or welcome). I assume
they will provide an opportunity for remote participation, but that’s never as informative or effective.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN" 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"><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>
<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="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="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="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>Marilyn Cade<br>
<b>Sent:</b> Friday, May 04, 2012 9:26 AM<br>
<b>To:</b> John Berard; Steve Delbianco; Chris at Andalucia; Elisa Cooper; bc - GNSO list<br>
<b>Cc:</b> Zahid Jamil<br>
<b>Subject:</b> [bc-gnso] Important to hear from members -- Reconfiguring the URS?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Thanks, John, the discussion about URS needs to include the full BC.<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Many members have concerns, and I will note that that in the IRT last approach, some BC members were excluded from participation, in favor of others in the community, so we
were not balanced in our BC participants. That was a serious challenge within the BC. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Whether a URS; WHAT URS, and HOW URS is a serious topic to more than a few BC members.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">As to whether it is implementation/ and how that discussion progresses, versus if it is policy, is not clear, right now. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">What was the policy recommendation that created it? <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Should that policy recommendation be revised?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Is this a change in how to implement a policy recommendation or a proposal to change/modify a policy recommendation?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Finally, Summit? What is that? What are the parameters? Did the SO/AC/SG/Constituencies support such a budget proposal, and how and who would be funded to participate?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">The IPC may love this; the BC and ISPCP need to study it. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">As to what is 'returned' to Council to provide policy advice on, this is a seriously challenging area for us, I fully agree.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">We do want to hear from our broader membership on first this particular issue, and then we will talk further in the BC, probably in Prague, on 'what is policy and what is
implementation'. I think that we all need to develop clarity on that for future. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Whether the BC would take up a further policy clarity discussion on that latter topic would then come from Steve after the BC members offer views. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Short term: My view on this for now: I want to see a staff discussion doc that explains the problems. Curtailing the URS and making it less useful doesn't excite me. paying
a bit more an having useful option -- willing to discuss and understand. ICANN staff seem headed in a direction against that. Personal view: pay more/have a viable option. IF not, then no use, so don't proceed with URS. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">PERSONAL views only in that view. Discussion from informed members critical for next 36 hours. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Marilyn Cade, BC Chair<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<hr size="2" width="100%" align="center" id="stopSpelling">
</span></div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Subject: Fwd: [council] Reconfiguring the URS?<br>
From: <a href="mailto:johnberard@aol.com">johnberard@aol.com</a><br>
Date: Thu, 3 May 2012 16:09:38 -0400<br>
CC: <a href="mailto:zahid@dndrc.com">zahid@dndrc.com</a><br>
To: <a href="mailto:marilynscade@hotmail.com">marilynscade@hotmail.com</a>; <a href="mailto:sdelbianco@netchoice.org">
sdelbianco@netchoice.org</a>; <a href="mailto:chris@andalucia.com">chris@andalucia.com</a>;
<a href="mailto:elisa.cooper@markmonitor.com">elisa.cooper@markmonitor.com</a><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Do we agree with Phil that this is a policy matter? My instinct is to say it is not, but...<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Berard<br>
<br>
Sent from my iPhone<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><br>
Begin forwarded message:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<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""> "Neuman, Jeff" <<a href="mailto:Jeff.Neuman@neustar.us">Jeff.Neuman@neustar.us</a>><br>
<b>Date:</b> May 3, 2012 2:09:09 PM EDT<br>
<b>To:</b> "<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>" <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>><br>
<b>Subject:</b> <b>[council] Reconfiguring the URS?</b><o:p></o:p></span></p>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Thanks to Phil Corwin for catching this, but buried in the new budget document (<a href="http://www.icann.org/en/news/public-comment/op-budget-fy13-01may12-en.htm" target="_blank">http://www.icann.org/en/news/public-comment/op-budget-fy13-01may12-en.htm</a>)
just put out for comment is a note on “reconfiguring” the URS. Excerpt provided below. I guess they could not find any URS providers that could do it for the costs that they had projected, so ICANN is holding 2 summits to work on a new model. My question
for the Council, is whether this is really a policy issue that should be referred back to the GNSO Community as opposed to having ICANN on its own resolving after holding 2 summits. Given the controversy around this over the past few years, any tweaks to
the URS should probably go back to the community in my opinion.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:9.0pt;text-align:justify;line-height:15.6pt">
<b><i><span lang="EN" style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">Uniform Rapid Suspension (URS) – $175K
</span></i></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:9.0pt;text-align:justify;line-height:15.6pt">
<i><span lang="EN" style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">At present there is a significant gap between the features specified for the URS procedure and the desired cost. In order to bridge this gap we will: hold two summit
sessions to reconfigure the URS to arrive at a lower cost model (one session in FY12 budget and another in this FY13 plan), conduct a process to develop and finalize URS Model in consultation with current UDRP providers and community members; and conduct RFP
based on URS Model and select URS providers. The goal is have a URS program in place and providers contracted and onboard by June 2013.</span></i><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Jeffrey J. Neuman<span style="color:#3366FF">
<br>
</span><span style="color:#068658">Neustar, Inc. / Vice President, Business Affairs</span></span></b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D"><br>
21575 Ridgetop Circle, Sterling, VA 20166</span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray"><br>
</span><b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658">Office:</span></b><b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#333333">
</span></b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D">+1.571.434.5772</span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#000066">
</span><b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658">Mobile:
</span></b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D">+1.202.549.5079</span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray">
</span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#000066"> </span><b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658">Fax:
</span></b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D">+1.703.738.7965</span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray">
</span><b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658">/</span></b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#3366FF">
</span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><a href="mailto:jeff.neuman@neustar.biz"><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658">jeff.neuman@neustar.biz</span></a></span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658">
</span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray"> </span><b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658">/</span></b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#3366FF">
</span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><a href="http://www.neustar.biz/" target="_blank"><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658">www.neustar.biz</span></a></span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray">
</span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <o:p></o:p></span></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<hr size="1" width="100%" noshade="" style="color:#A0A0A0" align="center">
</span></div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">No virus found in this message.<br>
Checked by AVG - <a href="http://www.avg.com">www.avg.com</a><br>
Version: 2012.0.2171 / Virus Database: 2425/4977 - Release Date: 05/04/12<o:p></o:p></span></p>
</div>
</body>
</html>