<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 15 (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:"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:Consolas;
panose-1:2 11 6 9 2 2 4 3 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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle19
{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:363411240;
mso-list-template-ids:-2005644026;}
@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"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I have to agree with David that we do not have time or the resident expertise in this group to propose new operational
procedures for RZM. <o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Identifying issues and requirements might be a good fallback position but even there, I don’t think we have sufficient
time. <o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">David’s proposed principles are a nice starting point but are quite generic and I don’t see the value of calling
for things like “accuracy” – no one will argue for inaccuracy and unless we can propose a framework that we believe improves accuracy, stability, etc. I am not sure of the value of such an exercise.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I suggest that we continue working on this beyond the 4 days and start adjusting our framework to the proposed model
that the CWG seems to be converging on.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">--MM
<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></font></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><font size="2" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;font-weight:bold">From:</span></font></b><font size="2" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> cwg-dtf-bounces@icann.org
[mailto:cwg-dtf-bounces@icann.org] <b><span style="font-weight:bold">On Behalf Of
</span></b>David Conrad<br>
<b><span style="font-weight:bold">Sent:</span></b> Monday, April 6, 2015 11:48 PM<br>
<b><span style="font-weight:bold">To:</span></b> Alan Greenberg<br>
<b><span style="font-weight:bold">Cc:</span></b> CWG DT-F<br>
<b><span style="font-weight:bold">Subject:</span></b> Re: [DT-F] Design Team F kickoff<o:p></o:p></span></font></p>
</div>
</div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"><o:p> </o:p></span></font></p>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">Hi,<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">Given the looming deadline (4 days?!), I remain uncertain there is sufficient time for us to both identify the salient
issues <i><span style="font-style:italic">and</span></i> come up with a new architecture for root zone publication, particularly since these would appear to be serial operations. In addition, I suspect revising the root zone architecture to address the identified
issues is probably going to require a bit of thought from a variety of folks not necessarily represented on the the design team (e.g., the root server operators and the IAB to name a couple). Perhaps a more realistic approach would be to identify the issues/requirements
and propose a framework (similar to what the IETF and RIR folks have done in different contexts) under which a new architecture can be devised? (My quarter-baked thought would be to have the CSC form an ad hoc group of technical experts who would propose a
revised architecture for subsequent public comment, but will admit I haven't thought much about the process by which stuff like this happens).<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">In any event and to start off, in terms of principles, I'd offer as a first cut (in alphabetical order):<o:p></o:p></span></font></p>
</div>
<ul type="disc">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Accountability: all activities associated with root management must be unambiguously attributable to an authorized actor and that actor must be held
responsible for those activities.<o:p></o:p></span></font></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Accuracy: all changes must be implemented with no errors.<o:p></o:p></span></font></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Auditability: all activities that impact the public that are performed by root management actors must be recorded.<o:p></o:p></span></font></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Improvability: root management must be able to evolve to meet the changing Internet.<o:p></o:p></span></font></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Predictability: there should be no surprises associated with root management processing.<o:p></o:p></span></font></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Security: no unauthorized entity should be able to make a change and only the changes requested are the ones that are implemented.<o:p></o:p></span></font></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Simplicity: the root management systems must be as simple as possible ("but no simpler").<o:p></o:p></span></font></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Stability: the processes related to root change requests should be consistent over time with any changes well documented and introduced with appropriate
lead time.<o:p></o:p></span></font></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Standards-based: interactions between actors in root management should be based on open standards; no proprietary mechanisms or interfaces should be
used between actors.<o:p></o:p></span></font></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Transparency: changes made as part of root management, and the policies upon which they are based, must be visible to interested stakeholders.<o:p></o:p></span></font></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Resiliency: it must be possible to quickly recover from a failure in any part of the system (even if the failure remains present).<o:p></o:p></span></font></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Robustness: single points of failure must be minimized or mechanisms must be in place to mitigate their impact.<o:p></o:p></span></font></li></ul>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">Note that some of these principles may tend to be in opposition to each other (e.g., a simple solution may not be the
most secure or robust).<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">I'm sure I missed some principles…<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">Regards,<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">-drc<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></font></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><font size="2" color="black" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black;font-weight:bold">From:
</span></font></b><font size="2" color="black" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>><br>
<b><span style="font-weight:bold">Date: </span></b>Monday, April 6, 2015 at 3:22 PM<br>
<b><span style="font-weight:bold">To: </span></b>CWG DT-F <<a href="mailto:cwg-dtf@icann.org">cwg-dtf@icann.org</a>><br>
<b><span style="font-weight:bold">Subject: </span></b>[DT-F] Design Team F kickoff<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></font></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">Although the template for DT-F (Relationship between the NTIA, IANA and the Root Zone Maintainer)
has not officially been approved, I see no reason on to start the work, all the more so since the target completion date is just 4 days away. We are likely to miss that deadline, but I would like to keep the slippage as small as possible.<br>
<br>
The draft template is attached. The DT members are:<o:p></o:p></span></font></p>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">Jaap Akkerhuis<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">Gary Campbell<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">Jordan Carter<o:p></o:p></span></font></pre>
<p class="MsoNormal"><font size="2" color="black" face="Calibri"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:black">David Conrad<o:p></o:p></span></font></p>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">Alan Greenberg<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">Milton Mueller<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">Rudi Vansnick<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black"><o:p> </o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">Bernie Turcotte and Grace Abuhamad will be providing staff support.<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black"><o:p> </o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">David is arguably the person with the deepest knowledge of the subject,<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">and can hopefully provide some insight into the issues.<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black"><o:p> </o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">As I see it, we have two parts to our task. The first is to identify the<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">salient issues in a post transition IANA with relation to the Root Zone<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">Maintainer (RZM), and then to propose an architecture for publication of<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">the Root Zone.<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black"><o:p> </o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">As a first step, I would suggest that we identify any:<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">- principles we wish to adhere to (such as transparency, auditability);<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">- problems (or potential problems) with the current process;<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">- Current NTIA operational involvement and if/how this needs to be<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">replaced or compensated for.<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black"><o:p> </o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">Current processes are documented in<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black"><a href="https://www.icann.org/en/system/files/files/sac-067-en.pdf"><o:p></o:p></a></span></font></pre>
<pre><span class="MsoHyperlink"><u><font size="2" color="blue" face="Courier New"><span style="font-size:10.0pt"><a href="https://www.icann.org/en/system/files/files/sac-067-en.pdf">https://www.icann.org/en/system/files/files/sac-067-en.pdf</a></span></font></u></span><font color="black"><span style="color:black">, pages<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">10-22.<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black"><o:p> </o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black">Alan<o:p></o:p></span></font></pre>
<pre><font size="2" color="black" face="Courier New"><span style="font-size:10.0pt;color:black"><o:p> </o:p></span></font></pre>
</div>
</div>
</blockquote>
</div>
</div>
</body>
</html>