<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 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
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;}
--></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'>Dear Mikey:<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 Board made these resolutions about SAC063: <a href="http://www.icann.org/en/groups/board/documents/resolutions-21nov13-en.htm#2.e">http://www.icann.org/en/groups/board/documents/resolutions-21nov13-en.htm#2.e</a> According to that, Fadi has until February 19 to make a recommendation to the Board. (If Fadi doesn’t recommend that all the recommendations be accepted, presumably the rationale will be published.) Where Fadi recommends that any advice be accepted, he is supposed to have the feasibility and costs and an implementation plan with timelines and high-level milestones for review by the Board no later than March 21. That’s right before ICANN Singapore begins. <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 key rollover metrics will require significant technical expertise to develop. <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'>Fadi has the same deadlines as above for SAC062 (Name Collisions):<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="http://www.icann.org/en/groups/board/documents/resolutions-21nov13-en.htm#2.d">http://www.icann.org/en/groups/board/documents/resolutions-21nov13-en.htm#2.d</a> <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'>So track those four deadlines related to SAC062 and SAC063. <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'>All best,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>--Greg<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><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"'> gnso-ssr-bounces@icann.org [mailto:gnso-ssr-bounces@icann.org] <b>On Behalf Of </b>Mike O'Connor<br><b>Sent:</b> Wednesday, February 12, 2014 8:41 AM<br><b>To:</b> GNSO SSR List<br><b>Subject:</b> [Gnso-ssr] discussion -- SAC063 -- SSAC Advisory on DNSSEC Key Rollover in the Root Zone<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>hi all,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>here’s a last thread to talk about the root-key rollover topic and a starter-kit of GNSO-oriented questions<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>- has the worldwide publicity effort been taken up?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>- is there anything the GNSO SGs and Constituencies can do to help with this effort? Could the root-key rollover outreach be used to leverage the broader goal of better-engaging with the technical community?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>- how’s that testbed coming along? again, could this collaboration be a point of leverage for broader technical outreach efforts?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>- how are those metrics coming? are they something that could be worked into the Data and Metrics for Policy-Making non-PDP WG that we are just launching in the GNSO?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>- where is the rollback procedure at? is that something that the GNSO take a look at before it’s implemented?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>- is there anything that the GNSO, and/or the GNSO Council, should be doing in Singapore to help move this along?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>- are there any other questions people would like to raise about this report?<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><b>SAC063: SSAC Advisory on DNSSEC Key Rollover in the Root Zone</b><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><a href="http://www.icann.org/en/groups/ssac/documents/sac-063-en.pdf">http://www.icann.org/en/groups/ssac/documents/sac-063-en.pdf</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><b>Recommendations:</b><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div></div><blockquote style='margin-left:30.0pt;margin-right:0in'><div><p class=MsoNormal>Recommendation 1: Internet Corporation for Assigned Names and Numbers (ICANN) staff, in coordination with the other Root Zone Management Partners (United States Department of Commerce, National Telecommunications and Information Administration (NTIA), and Verisign), <b>should immediately undertake a significant, worldwide communications effort to publicize the root zone KSK rollover motivation and process as widely as possible</b>.<o:p></o:p></p></div><div><p class=MsoNormal><span class=apple-tab-span> </span><o:p></o:p></p></div><div><p class=MsoNormal>Recommendation 2: ICANN staff should lead, coordinate, or otherwise encourage the creation of a collaborative, representative testbed for the purpose of analyzing behaviors of various validating resolver implementations, their versions, and their network environments (e.g., middle boxes) that may affect or be affected by a root KSK rollover, <b>such that potential problem areas can be identified, communicated, and addressed.</b><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Recommendation 3: ICANN staff should lead, coordinate, or otherwise encourage<b> the creation of clear and objective metrics for acceptable levels of “breakage” resulting from a key rollover.</b><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Recommendation 4: ICANN staff should lead, coordinate, or otherwise encourage <b>the development of rollback procedures to be executed when a rollover has affected operational stability beyond a reasonable boundary.</b><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Recommendation 5: ICANN staff should lead, coordinate, or otherwise encourage the collection of as much information as possible about the impact of a KSK rollover to provide input to planning for future rollovers.<o:p></o:p></p></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>