<div dir="ltr"><div class="gmail_default" style="font-size:small">Kurt,</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Just a note that DT-D on authorization has completed its work which did not include the authorization of new functions.<br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">B.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 10, 2015 at 5:31 PM, Kurt Pritz <span dir="ltr"><<a href="mailto:kpritz@thedna.org" target="_blank">kpritz@thedna.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">To David:<div><br></div><div>My thought is that the mechanism for considering changes to IANA services and operations is the equivalent of the NTIA authorization function. NTIA authorized root zone changes and also authorized when new services or operations (such as automation) could be "turned on." Even if the root-zone change authorization is abandoned (which to me is ill-advised) there remains this other authorization task (that the authorization design team might decide to abandon also).</div><div><br></div><div>To Stephanie:</div><div><br></div><div>My thought is that the consultation would be among the "contracted parties": the IANA function, registry operators and other direct customs such as the RIRs if they are affected. Then that team could call in experts as need be. I don't see that any consultation on new or changed services goes beyond the function of IANA. IANA provides services, figures out how to improve those services or accommodate changes in the environment, gets agreement on the change from their customers, and implements the change. IANA staff might bring in ICANN staff to help with the design and implementation but that would be decided on a case by case basis. </div><div><br></div><div>Kurt</div><div><br></div><div><br><div><div>On Apr 10, 2015, at 1:55 PM, "Duchesneau, Stephanie" <<a href="mailto:Stephanie.Duchesneau@neustar.us" target="_blank">Stephanie.Duchesneau@neustar.us</a>> wrote:</div><br><blockquote type="cite"><div lang="EN-US" link="#0563C1" vlink="#954F72" style="font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><a name="14ca53f6aff6bf75_OLE_LINK1"></a><a name="14ca53f6aff6bf75_OLE_LINK2">I am comfortable with this language. I think there will have to be some reconciliation between this/the escalation language/the periodic review language when we convene next week, but this is inevitable.<u></u><u></u></a></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">The one question I would ask is whether this should be convened by ICANN and not IANA because consultation process itself seems beyond the function that would be carried out by the actual IANA department.<u></u><u></u></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><br>Thanks for all your work (and fearless leadership) on this Donna.<u></u><u></u></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><br>Stephanie<u></u><u></u></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div><div><p class="MsoNormal" style="margin:12pt 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(38,38,38)">Stephanie Duchesneau</span></b><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(51,102,255)"><span> </span><br></span></b><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(6,134,88)">Neustar, Inc. /<span> </span></span></b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(125,125,125)">Public Policy Manager<br>1775 Pennsylvania Avenue NW, 4<sup>th</sup><span> </span>Floor, Washington, DC 20006</span><span style="font-size:9pt;font-family:Arial,sans-serif;color:gray"><br></span><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(6,134,88)">Office:</span></b><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(51,51,51)"> </span></b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(125,125,125)"><a href="tel:%2B1.202.533.2623" value="+12025332623" target="_blank">+1.202.533.2623</a><span> </span></span><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(6,134,88)">Mobile:<span> </span></span></b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(125,125,125)"><a href="tel:%2B1.703.731.2040" value="+17037312040" target="_blank">+1.703.731.2040</a></span><span style="font-size:9pt;font-family:Arial,sans-serif;color:gray"> </span><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(0,0,102)"> </span><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(6,134,88)">Fax:<span> </span></span></b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(125,125,125)"><a href="tel:%2B1.202.533.2623" value="+12025332623" target="_blank">+1.202.533.2623</a></span><span style="font-size:9pt;font-family:Arial,sans-serif;color:gray"> </span><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(6,134,88)">/</span></b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(6,134,88)"> </span><a href="http://www.neustar.biz/" style="color:rgb(149,79,114);text-decoration:underline" target="_blank"><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(6,134,88)">www.neustar.biz</span></a><span style="font-size:9pt;font-family:Arial,sans-serif;color:gray"><span> </span> <u></u><u></u></span></p><div><div class="MsoNormal" style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:8pt;font-family:'Times New Roman',serif;color:rgb(125,125,125)"><hr size="1" width="100%" noshade align="left" style="color:rgb(150,150,150)"></span></div></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:8.5pt;font-family:Arial,sans-serif;color:rgb(125,125,125)">The information contained in this email message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this email message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message.</span><span style="font-size:12pt;font-family:'Times New Roman',serif;color:rgb(125,125,125)"><u></u><u></u></span></div></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div><div><div style="border-style:solid none none;border-top-width:1pt;border-top-color:rgb(181,196,223);padding:3pt 0in 0in"><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-size:10pt;font-family:Tahoma,sans-serif">From:</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif"><span> </span><a href="mailto:dt3-bounces@icann.org" target="_blank">dt3-bounces@icann.org</a> [mailto:<a href="mailto:dt3-" target="_blank">dt3-</a><a href="mailto:bounces@icann.org" target="_blank">bounces@icann.org</a>]<span> </span><b>On Behalf Of<span> </span></b>David Conrad<br><b>Sent:</b><span> </span>Friday, April 10, 2015 4:45 PM<br><b>To:</b><span> </span>Donna Austin; <a href="mailto:dt3@icann.org" target="_blank">dt3@icann.org</a><br><b>Subject:</b><span> </span>Re: [DTC CSC] CSC Charter 0 7<u></u><u></u></span></div></div></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:10pt">Donna,<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:10pt"> </span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:10pt">Speaking for myself only, the wording looks fine for me.<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:10pt"> </span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:10pt">If others feel gives the CSC an inappropriate role, I would think a key recommendation from the Design Team to the CWG is that some (other) mechanism must be defined to accommodate technological/evolutionary changes in the Internet.<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:10pt"> </span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:10pt">Regards,<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:10pt">-drc<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:10pt"> </span></div></div><div style="border-style:solid none none;border-top-width:1pt;border-top-color:rgb(181,196,223);padding:3pt 0in 0in"><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><b><span>From:<span> </span></span></b><span>Donna Austin <<a href="mailto:Donna.Austin@ariservices.com" style="color:rgb(149,79,114);text-decoration:underline" target="_blank">Donna.Austin@ariservices.com</a>><br><b>Date:<span> </span></b>Friday, April 10, 2015 at 1:31 PM<br><b>To:<span> </span></b>"<a href="mailto:dt3@icann.org" style="color:rgb(149,79,114);text-decoration:underline" target="_blank">dt3@icann.org</a>" <<a href="mailto:dt3@icann.org" style="color:rgb(149,79,114);text-decoration:underline" target="_blank">dt3@icann.org</a>><br><b>Cc:<span> </span></b>David Conrad <<a href="mailto:david.conrad@icann.org" style="color:rgb(149,79,114);text-decoration:underline" target="_blank">david.conrad@icann.org</a>>, Kim Davies <<a href="mailto:kim.davies@icann.org" style="color:rgb(149,79,114);text-decoration:underline" target="_blank">kim.davies@icann.org</a>><br><b>Subject:<span> </span></b>CSC Charter 0 7<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:10pt"> </span></div></div><blockquote style="border-style:none none none solid;border-left-width:4.5pt;border-left-color:rgb(181,196,223);padding:0in 0in 0in 4pt;margin-left:3.75pt;margin-right:0in"><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span>All</span><span lang="EN-AU"><u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span> </span><span lang="EN-AU"><u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span>I think I’ve captured the changes suggested from the call this morning.</span><span lang="EN-AU"><u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span> </span><span lang="EN-AU"><u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span>On the big issue of ‘technological changes’ I’ve flagged that the Design Team has concerns about the CSC being responsible for anything other than monitoring. I’ve also provided some new text to try to overcome that concern, which I’m repeating here for ease of reference. I’m happy to take this out and just leave what we had and express our concerns if others do not think this is a viable option in that it does not overcome our primary concern.</span><span lang="EN-AU"><u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span> </span><span lang="EN-AU"><u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><i><span lang="EN-AU">The CSC, in consultation with registry operators, is authorised to discuss with the IANA Functions Operator ways to enhance the provision of IANA’s operational services to meet changing technological environments; as a means to address performance issues; or other unforeseen circumstances. In the event it is agreed that a material change in IANA functions services or operations would be beneficial, the CSC reserves the right to call for a community consultation and independent validation, to be convened by IANA, on the proposed change. Any recommended change must be approved by the ccNSO and RySG.</span></i><span lang="EN-AU"><u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><i><span lang="EN-AU"> </span></i><span lang="EN-AU"><u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><i><span lang="EN-AU">The IANA Functions Operator would be responsible for implementing any recommended changes and must ensure that sufficient testing is undertaken to ensure smooth transition and no disruption to service levels.</span></i><span lang="EN-AU"><u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><i><span lang="EN-AU"> </span></i><span lang="EN-AU"><u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-AU">I’m conscious that we need to wrap this up today and get to the CWG, but it would be useful if we could defer until such time as Staffan and Martin have had a chance to review.<u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-AU"> <u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-AU">Thanks<u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-AU"> <u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-AU">Donna<u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span> </span><span lang="EN-AU"><u></u><u></u></span></div></blockquote></div>_______________________________________________<br>dt3 mailing list<br><a href="mailto:dt3@icann.org" target="_blank">dt3@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/dt3" target="_blank">https://mm.icann.org/mailman/listinfo/dt3</a></div></blockquote></div><br></div></div><br>_______________________________________________<br>
dt3 mailing list<br>
<a href="mailto:dt3@icann.org">dt3@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/dt3" target="_blank">https://mm.icann.org/mailman/listinfo/dt3</a><br>
<br></blockquote></div><br></div>