<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="color: rgb(0, 0, 0);"><font face="Arial" style="font-size: 12px;">Hi All,</font></div>
<div style="color: rgb(0, 0, 0);"><font face="Arial" style="font-size: 12px;"><br>
</font></div>
<div style="color: rgb(0, 0, 0);"><font face="Arial" style="font-size: 12px;">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:</font></div>
<div style="color: rgb(0, 0, 0);"><font face="Arial" style="font-size: 12px;"><br>
</font></div>
<div style="color: rgb(0, 0, 0);"><span id="docs-internal-guid-1d651aa0-9e89-193b-b7af-cd043f6240a9">
<ul style="margin-top: 0pt; margin-bottom: 0pt;">
<font face="Arial">
<li dir="ltr" style="font-size: 12px; list-style-type: disc; vertical-align: baseline;">
<p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="font-weight: bold; vertical-align: baseline; white-space: pre-wrap;">Composition:
</span><span style="vertical-align: baseline; white-space: pre-wrap;">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.</span></p>
</li><li dir="ltr" style="font-size: 12px; list-style-type: disc; vertical-align: baseline;">
<p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="font-weight: bold; vertical-align: baseline; white-space: pre-wrap;">Geographic Representation:
</span><span style="vertical-align: baseline; white-space: pre-wrap;">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.</span></p>
</li><li dir="ltr" style="font-size: 12px; list-style-type: disc; font-weight: bold; vertical-align: baseline;">
<p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="vertical-align: baseline; white-space: pre-wrap;">Frequency</span><span style="font-weight: normal; vertical-align: baseline; white-space: pre-wrap;">: 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.</span></p>
</li><li dir="ltr" style="font-size: 12px; list-style-type: disc; font-weight: bold; vertical-align: baseline;">
<p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="vertical-align: baseline; white-space: pre-wrap;">Outcomes of IFR:
</span><span style="font-weight: normal; vertical-align: baseline; white-space: pre-wrap;">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.
</span></p>
</li><li dir="ltr" style="font-size: 12px; list-style-type: disc; font-weight: bold; vertical-align: baseline;">
<p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="vertical-align: baseline; white-space: pre-wrap;">Appointment of the ccTLD Members:
</span><span style="font-weight: normal; vertical-align: baseline; white-space: pre-wrap;">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.
</span></p>
</li><li dir="ltr" style="font-size: 12px; list-style-type: disc; font-weight: bold; vertical-align: baseline;">
<p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="vertical-align: baseline; white-space: pre-wrap;">Scope of IFRT:
</span><span style="font-weight: normal; vertical-align: baseline; white-space: pre-wrap;">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.</span></p>
</li><li dir="ltr" style="list-style-type: disc; font-weight: bold; vertical-align: baseline;">
<p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 12px; vertical-align: baseline; white-space: pre-wrap;">Details Around Separation Review:
</span><span style="font-weight: normal; vertical-align: baseline; white-space: pre-wrap;"><span style="font-size: 12px;">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></span></p>
</li><li dir="ltr" style="list-style-type: disc; font-weight: bold; vertical-align: baseline;">
<p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="font-size: 12px;"><span style="vertical-align: baseline; white-space: pre-wrap;">Role of the Board</span><span style="font-weight: normal; vertical-align: baseline; white-space: pre-wrap;">:
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></span></p>
</li><li dir="ltr" style="list-style-type: disc; vertical-align: baseline;">
<p dir="ltr" style="font-weight: bold; line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;">
<span style="font-size: 12px;"><span style="vertical-align: baseline; white-space: pre-wrap;">Home of IFRT:
</span><span style="font-weight: normal; vertical-align: baseline; white-space: pre-wrap;">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></span></p>
<p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 12px;"><span style="font-weight: bold; vertical-align: baseline; white-space: pre-wrap;">Separation Costs:
</span><span style="vertical-align: baseline; white-space: pre-wrap;">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).</span></span></p>
</font></li></ul>
</span></div>
<div style="color: rgb(0, 0, 0);"><span><span style="vertical-align: baseline; white-space: pre-wrap; font-size: 12px;"><font face="Arial"><br>
</font></span></span></div>
<div><span style="vertical-align: baseline;"><span style="white-space: pre-wrap; font-size: 12px;"><font face="Arial">Sorry for sending this out on such short order. Hope this aids today’s discussion.</font></span></span></div>
<div><span style="vertical-align: baseline;"><span style="white-space: pre-wrap; font-size: 12px;"><font face="Arial"><br>
</font></span></span></div>
<div><span style="vertical-align: baseline;"><span style="white-space: pre-wrap; font-size: 12px;"><font face="Arial">Best.</font></span></span></div>
<div><span style="vertical-align: baseline;"><span style="white-space: pre-wrap; font-size: 12px;"><font face="Arial"><br>
</font></span></span></div>
<div><span style="vertical-align: baseline;"><span style="white-space: pre-wrap; font-size: 12px;"><font face="Arial">Stephanie</font></span></span></div>
<div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<b style="font-size: 15px;"><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(38, 38, 38);"><br>
</span></b></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<b style="font-size: 15px;"><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(38, 38, 38);">Stephanie Duchesneau</span></b><b style="font-size: 15px;"><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(51, 102, 255);"> </span></b></div>
<b style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 15px;"><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(6, 134, 88);">Neustar, Inc. / </span></b><span style="color: rgb(125, 125, 125); font-family: Arial, sans-serif; font-size: 9pt;">Public
Policy Manager<br>
1775 Pennsylvania Avenue NW, 4<sup>th</sup> Floor, Washington, DC 20006</span><span style="color: gray; font-family: Arial, sans-serif; font-size: 9pt;"><br>
</span><b style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 15px;"><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(6, 134, 88);">Office:</span></b><b style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 15px;"><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(51, 51, 51);"> </span></b><span style="color: rgb(125, 125, 125); font-family: Arial, sans-serif; font-size: 9pt;">+1.202.533.2623 </span><b style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 15px;"><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(6, 134, 88);">Mobile: </span></b><span style="color: rgb(125, 125, 125); font-family: Arial, sans-serif; font-size: 9pt;">+1.703.731.2040</span><span style="color: gray; font-family: Arial, sans-serif; font-size: 9pt;"> </span><span style="color: rgb(0, 0, 102); font-family: Arial, sans-serif; font-size: 9pt;"> </span><b style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 15px;"><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(6, 134, 88);">Fax: </span></b><span style="color: rgb(125, 125, 125); font-family: Arial, sans-serif; font-size: 9pt;">+1.202.533.2623</span><span style="color: gray; font-family: Arial, sans-serif; font-size: 9pt;"> </span><b style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 15px;"><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(6, 134, 88);">/</span></b><span style="color: rgb(6, 134, 88); font-family: Arial, sans-serif; font-size: 9pt;"> </span><a href="http://www.neustar.biz/" style="color: purple; font-family: Calibri, sans-serif; font-size: 15px;"><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(6, 134, 88);">www.neustar.biz</span></a><span style="color: gray; font-family: Arial, sans-serif; font-size: 9pt;">
</span></div>
</body>
</html>