<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)">
<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: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";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:402795461;
mso-list-template-ids:-744328386;}
@list l0: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 l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
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="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">First of all let me thank DT-N (is that Avri & Stephanie?) for doing this. I find it quite helpful. Below are my personal views regarding the DT-N review.<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">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> cwg-stewardship-bounces@icann.org [mailto:cwg-stewardship-bounces@icann.org]
<b>On Behalf Of </b>Duchesneau, Stephanie<br>
<b>Sent:</b> Friday, May 29, 2015 3:22 AM<br>
<b>To:</b> cwg-stewardship@icann.org<br>
<b>Cc:</b> avri@acm.org<br>
<b>Subject:</b> [CWG-Stewardship] Initial DT-N Response to Major Comment Areas<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Hi All,</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">In order to facilitate today’s review of comments, DT-N has formulated a review of some of the major topics identified in the related public comments and an initial
design team position (including identification of areas where further discussion is required. Our summary is below:</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 lfo1;vertical-align:baseline">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Composition:
</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">A large number of comments focused on the composition of the IFRT, though the “asks” varied widely. Some called for greater registry representation, some called for increased
representation by Advisory Committees, others called for a balance between the GNSO/ccNSO participation. One comment called to remove the CSC liaison while another called for the entire CSC to participate and for 5 liaisons to be created. The structure proposed
by the working group is an effort to balance between these different positions; we note that the structure was generally derived from the outcome of the intensive working weekend (then in the context of the MRT) that followed a survey of the working group
on this topic.<o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><b><i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[Chuck Gomes] I think that the structure is fairly well balanced considering what I think is a need to
limit the total size to a not too large and dysfunctional size.</span></i></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 lfo1;vertical-align:baseline">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Geographic Representation:
</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Some comments called out for geographic balance in the representation of the IFRT. The DT supports this principle but notes that implementation is difficult for a group of
this small size, particularly where experience is key. To these ends we recommend that a principle that, to the extent possible, groups appointing more than one representative strive to have representatives from different geographic regions.<o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><b><i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[Chuck Gomes] I believe this is a reasonable approach but it might be helpful to also encourage some cross-group
collaboration before individual groups finalize their selections with the goal of increasing geographic diversity if possible.</span></i></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> One way of doing this might be to
ask groups to communicate their preliminary selections to one another as a whole, evaluate the overall geographic balance, and then explore whether any of the groups have any flexibility to adjust their selections to improve the total geographic representation
without compromising on needed expertise and qualifications.<o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 lfo1;vertical-align:baseline">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Frequency</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">: Some comments called for reviews to be carried out
more frequently. We generally feel that a review carried out every year or every other year (as called for by the comments) would be too frequent. However, we are open to suggestions made that a recommendation for the frequency of the regular reviews could
be deferred to completion of the first review.<b><o:p></o:p></b></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><b><i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[Chuck Gomes] 1) If an IFR requires at least nine months to be completed (including selection of IFRT members),
then an annual review would mean that we are almost constantly reviewing with little or no time to evaluate the results of previous reviews</span></i></b><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">. 2) I would like
to think that the IANA service should be relatively stable as it has been in the past; if that is true, then conducting periodic reviews too frequently may be overkill. 3) The option for Special IFRs provides the opportunity for more frequent reviews if specific
needs are identified. Therefore, I support the recommendation for an initial periodic review after two years and then every five years thereafter.<o:p></o:p></span></b></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></b></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 lfo1;vertical-align:baseline">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Outcomes of IFR:
</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Some comments called for the outcomes of the IFR to be explicitly stated. While we believe that these should not be prescribed, the creation of a SCWG is identified as one
possible outcome. We would be open to creating an inventory of other possible outcomes but would not want this work to confine the Review Team.
<b><o:p></o:p></b></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><b><i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[Chuck Gomes] Providing as much clarify as possible in terms of what is to be reviewed would be helpful
but, if we want objective reviews to occur, I don’t see how we could explicitly predefine outcomes and I suspect that this is not what commenters were suggesting. Providing general guidance for periodic reviews and more specific guidance for Special reviews
will be very helpful but I think there should be enough flexibility to review unanticipated issues.<o:p></o:p></span></i></b></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></b></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 lfo1;vertical-align:baseline">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Appointment of the ccTLD Members:
</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">One comment called for the non-ccNSO ccTLD representative to be appointed by the ccNSO. We believe that the ccNSO is in the best position to appoint this representative and
to communicate with all ccTLD operators about the process. We support clarifying this in the draft comment.
<b><o:p></o:p></b></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><b><i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[Chuck Gomes] I believe it is a good idea to use existing ICANN structures so as to avoid having to create
new structures but there needs to be accommodation for those who are not part of ICANN structures so additional clarification of this make sense.</span></i></b><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> It might be
best of ccTLD registries develop ways of doing this that are acceptable to them. The same would apply for gTLD registries to the extent that this issue may apply to them.<o:p></o:p></span></b></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></b></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 lfo1;vertical-align:baseline">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Scope of IFRT:
</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">One comment requested clarification that this applies only to the Naming Functions. It is the intention that the IFRT will apply only to the Naming Functions. We will ensure
that this is clarified in current drafts.<b><o:p></o:p></b></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 lfo1;vertical-align:baseline">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Details Around Separation Review:
</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Several comments called for more detail to be inputted about the Separation Review. We note that significant work has been carried out since the Draft Proposal to further
define the separation process/mechanism (the SCWG). These processes encompass some of the sub-recommendations with respect to separation (e.g. community consultation)</span><b><span style="font-family:"Arial","sans-serif";color:black"><o:p></o:p></span></b></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 lfo1;vertical-align:baseline">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Role of the Board</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">: Some comments expressed concern about the role
of the Board in the processes of implementing IFRT Recommendations or in the Separation Process. We note that this role has been limited to Board approval, which we believe is requisite in both instances. To address related concerns, in the revised process
details have been added that rejection of these recommendations would have to be handled by the board in accordance with the thresholds and procedures for rejecting the output of a PDP.
</span><b><span style="font-family:"Arial","sans-serif";color:black"><o:p></o:p></span></b></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 lfo1;vertical-align:baseline">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Home of IFRT:
</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Some comments raised concerns about the possibility of the IFRT sitting inside PTI and/or supported by PTI. The intent of DT-N was to have the IFRT exist within ICANN and
to be defined in the ICANN Bylaws. We will make this clearer in the current draft. We will also clarify that ICANN will provide secretariat and other support services for the IFRT.</span><b><span style="font-family:"Arial","sans-serif";color:black"><o:p></o:p></span></b></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><b><i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[Chuck Gomes] I agree with DT-</span></i></b><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">N
on this because the accountability mechanisms will be for ICANN.<o:p></o:p></span></b></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></b></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;vertical-align:baseline">
<b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Separation Costs:
</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Some comments dealt with concerns about how IANA expenses would be covered following a separation process. DT-N supports this recommendation. We look to the full CWG for a
determination on where this issue is best resolved (DT N, DT L, DT O or full CWG).<o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><b><i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[Chuck Gomes] I am biased toward the RySG recommendation in this regard, i.</span></i></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">e.,
that a sufficient portion of registry fees be designated for IANA services and that those fees be used to support the IANA function operator regardless of who the IFO is.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black"><br>
<br>
</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Sorry for sending this out on such short order. Hope this aids today’s discussion.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><br>
<br>
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Best.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><br>
<br>
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Stephanie</span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#262626">Stephanie Duchesneau</span></b><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#3366FF"> </span></b><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#068658">Neustar, Inc. / </span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#7D7D7D">Public Policy Manager<br>
1775 Pennsylvania Avenue NW, 4<sup>th</sup> Floor, Washington, DC 20006</span><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:gray"><br>
</span><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#068658">Office:</span></b><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#333333"> </span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#7D7D7D">+1.202.533.2623 </span><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#068658">Mobile: </span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#7D7D7D">+1.703.731.2040</span><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:gray"> </span><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#000066"> </span><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#068658">Fax: </span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#7D7D7D">+1.202.533.2623</span><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:gray"> </span><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#068658">/</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#068658"> </span><a href="http://www.neustar.biz/"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#068658">www.neustar.biz</span></a><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:gray">
</span><o:p></o:p></p>
</div>
</div>
</body>
</html>