<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<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: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";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{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;}
/* List Definitions */
@list l0
{mso-list-id:189682034;
mso-list-type:hybrid;
mso-list-template-ids:-327887424 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:2124105519;
mso-list-template-ids:1353855244;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
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">FYI---<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a href="http://internetcommerce.org/URS_Implementation">http://internetcommerce.org/URS_Implementation</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" align="center" style="margin-bottom:10.0pt;text-align:center;line-height:115%">
<b><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">URS Implementation Finally to Commence Under GNSO Direction<o:p></o:p></span></b></p>
<p class="MsoNormal" align="center" style="margin-bottom:10.0pt;text-align:center;line-height:115%">
<b><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif""><o:p> </o:p></span></b></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;text-align:justify;line-height:115%">
<span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">For more than a year ICA has been asking ICANN when it will commence with the task of implementing the Uniform Rapid Suspension (URS) policy for the new gTLD program as it currently
stands in the Applicant Guidebook (AG). The URS is a required rights protection mechanism (RPM) that must be in place before any new gTLDs can open, and the current model balances trademark holder and registrant rights and is the result of a laborious two-year
process resulting in recommendations that were unanimously adopted by the GNSO Council and subsequently by the ICANN Board. Each of our inquiries about the commencement of URS implementation have received the same general response of “soon”, but no perceptible
progress had been made since the new gTLD program launched in the spring of 2011.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;text-align:justify;line-height:115%">
<span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">We have just learned that ICANN senior executive Kurt Pritz has sent a publicly available e-mail to GNSO Council Chairman Stephane Van Gelder advising him that URS implementation
will finally begin in earnest within a few weeks. That exchange is below, and here are our key take-aways:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormalCxSpMiddle" style="margin-bottom:10.0pt;mso-add-space:auto;text-align:justify;line-height:115%;mso-list:l0 level1 lfo3">
<span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">ICANN continues to assert that the present URS model does “<i>not appear to meet cost requirements”.</i> Yet, so far as know, and our knowledge includes a targeted document disclosure
request filed on this and related subjects (see <a href="http://internetcommerce.org/WIPO2ICANN_URS_Summits">
http://internetcommerce.org/WIPO2ICANN_URS_Summits</a>), ICANN has no documented cost analysis proving this assertion and is instead relying on the feedback of the two principal UDRP providers, WIPO and NAF, who have their own separate rationales for making
such an assertion. At the conference held yesterday in Washington held to discuss Melbourne IT’s HARM proposal (about which we shall post separately) there was a fairly broad consensus that ICANN should publish an RFP for the URS and solicit bids from a broad
range of credible arbitration providers beyond the thin ranks of WIPO and NAF, based on the common sense belief that a URS focused on slam dunk infringement should not require a great deal of expert time or associated cost (if it takes more than 15 minutes
to render a decision, it’s not a black-and-white case and belongs in a UDRP proceeding). There was also considerable support for the notion that, if the price target of $300-$500 simply cannot be met, ICANN should consider at least short-term subsidization
by using some of the $350 million it has collected in new gTLD application fees. ICA believes it is premature to “<i>flesh out some of those [alternative] models for possible implementation”</i>, and thereby contemplate significant revisions of URS, until
we have market testing of the true cost of implementing the present model. Before there is any consideration of “<i>potential solutions”,
</i>let’s determine if there really is a cost problem that needs to be solved.<o:p></o:p></span></li><li class="MsoNormalCxSpMiddle" style="margin-bottom:10.0pt;mso-add-space:auto;text-align:justify;line-height:115%;mso-list:l0 level1 lfo3">
<span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">A meeting on URS implementation, possibly in the form of a webinar, will be scheduled for the first week of October. We are unsure who will be invited to speak at the webinar and
whether it will include adequate representation of the registrant community, both commercial and non-commercial. Let’s wait and see.<o:p></o:p></span></li><li class="MsoNormalCxSpMiddle" style="margin-bottom:10.0pt;mso-add-space:auto;text-align:justify;line-height:115%;mso-list:l0 level1 lfo3">
<span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">A second meeting will be scheduled during the upcoming ICANN meeting in Toronto. We believe it’s is essential that this critical meeting result in a credible path to timely implementation.<o:p></o:p></span></li><li class="MsoNormalCxSpMiddle" style="margin-bottom:10.0pt;mso-add-space:auto;text-align:justify;line-height:115%;mso-list:l0 level1 lfo3">
<span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">ICANN has stated that “<i>the meetings we are having are open to all”.
</i>This is consistent with the open and transparent approach to URS implementation that ICA has consistently advocated, and we intend to be intimately involved.<o:p></o:p></span></li><li class="MsoNormalCxSpMiddle" style="margin-bottom:10.0pt;mso-add-space:auto;text-align:justify;line-height:115%;mso-list:l0 level1 lfo3">
<span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">ICANN understands the key role played by the GNSO Council in developing and approving the present model and “<i>that the GNSO leadership might want to conduct the URS discussions
in a certain way”, </i>and is willing to “<i>work in whichever way the GNSO wishes to proceed”.</i> From our viewpoint, this position is an extremely positive development because it respects the key policymaking role that the Council plays for gTLDs, puts
the ICANN community as represented by the Council rather than ICANN staff in the driver’s seat on designing and managing the implementation process, and is a far better approach than the “Summit” concept contemplated earlier this year. It also undercuts potential
efforts by some brand interests to try to circumvent the Council through direct lobbying of the Governmental Advisory Committee (GAC) and, through it, the ICANN Board.<o:p></o:p></span></li><li class="MsoNormalCxSpMiddle" style="margin-bottom:10.0pt;mso-add-space:auto;text-align:justify;line-height:115%;mso-list:l0 level1 lfo3">
<span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">ICANN aims to “<i>seek to meet the cost and timeliness goals for which the URS was designed”
</i>and to balance that with a commitment to <i>“seek to ensure that registrants enjoy the protections written into the current model”.</i>
<b><u>Assuring that registrants enjoy the essential due process rights written into the current policy, and that they are not diluted in pursuit of complainant cost reduction, will be ICA’s foremost goal as this discussion ensues.<o:p></o:p></u></b></span></li></ul>
<p class="MsoNormal" style="margin-bottom:10.0pt;text-align:justify;line-height:115%">
<b><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">All in all, these are overdue but overall positive developments. Again, it’s our belief that any substantial alteration of the URS based on cost goals should not even be considered
until we have some accurate, market-tested idea of the cost of implementing the current model -- and that does not yet exist. Even then, we are wary of reopening this carefully constructed RPM because some of the ideas floating around for reducing cost could
substantially reduce registrant rights in new gTLDs and convert the URS from a narrow supplement to the UDRP into a cut-price, rights-gutting alternative to it. That’s an unacceptable bait-and-switch.<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;text-align:justify;line-height:115%">
<b><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">But ICANN’s recognition of the central role to be played by the GNSO Council in considering any alteration is positive. It is critically important that whatever is done on URS
implementation get off to a sound launch in Toronto, because there is an unusually long half-year gap between it and the next, April 2013 ICANN meeting in Beijing. A botched process could lead to further pushback in the launch date for new gTLDs, while one
that results in evisceration of registrant rights could fatally undermine their prospects for success.<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;text-align:justify;line-height:115%">
<u><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">The e-mail exchange follows:<o:p></o:p></span></u></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><b><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">From:</span></i></b><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">
<a href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a> <a href="mailto:[mailto:owner-council@gnso.icann.org]">
[mailto:owner-council@gnso.icann.org]</a> <b>On Behalf Of </b>Stéphane Van Gelder<br>
<b>Sent:</b> Wednesday, September 19, 2012 5:08 AM<br>
<b>To:</b> Kurt Pritz<br>
<b>Cc:</b> GNSO Council List<br>
<b>Subject:</b> [council] Re: Uniform Rapid Suspension Discussion<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif""><o:p> </o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">Thanks Kurt. I am copying the Council for their information.<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif""><o:p> </o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">The Council will no doubt follow-up on this in the near future.<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif""><o:p> </o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">Best,<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif""><o:p> </o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">Stéphane Van Gelder<br>
Directeur Général / General manager<br>
INDOM NetNames France<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">----------------<br>
Registry Relations and Strategy Director<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">NetNames<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span lang="EN-GB" style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">T: +33 (0)1 48 01 83 51<br>
F: +33 (0)1 48 01 83 61</span></i><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif""><o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif""><o:p> </o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">Le 18 sept. 2012 à 22:09, Kurt Pritz a écrit :<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif""><o:p> </o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif""><o:p> </o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">Hi Stephane:<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif""><o:p> </o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">I am writing to let you know that we are planning a set of discussions on Uniform Rapid Suspension (URS) implementation
in the near future and seek the input of GNSO leadership. As you know, a meeting in Prague we indicated that URS, as currently designed, did not appear to meet cost requirements. In Prague, contributors in the meeting described briefly several potential solutions.
In the next set of meetings, we want to flesh out some of those models for possible implementation. We want to have one meeting in about two weeks (probably a webinar type of format with a possibility for some face-to-face interaction), and then we have a
meeting in Toronto is scheduled. The first meeting will be announced shortly.<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif""><o:p> </o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">I am writing you because some of the proposed solutions, while feasible, do not match up with the specific
conclusions of the STI team when it did its work. We recognize the role of the GNSO in those discussions. While the meetings we are having are open to all, we understand that the GNSO leadership might want to conduct the URS discussions in a certain way. Having
the twin goals of developing a solution in time for use by new gTLDs and ensuring that all those interested can participate in the discussion, we can work in whichever way the GNSO wishes to proceed. (Of course, we also seek to meet the cost and timeliness
goals for which the URS was designed and also seek to ensure that registrants enjoy the protections written into the current model by the IRT and STI.)The output of the next meetings can inform GNSO discussion or we can carry on in a way acceptable to the
GNSO.<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif""><o:p> </o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">I am also copying Olivier as ALAC members participated in the STI.<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif""><o:p> </o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">I hope you find this helpful. Contact me anytime with questions.<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif""><o:p> </o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">Regards,<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif""><o:p> </o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><i><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif"">Kurt<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><span style="font-size:12.0pt;line-height:115%;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><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: 2012.0.2221 / Virus Database: 2437/5263 - Release Date: 09/11/12<br>
Internal Virus Database is out of date.<o:p></o:p></span></p>
</div>
</body>
</html>