<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=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
/* 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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.im
{mso-style-name:im;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@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">Seun,<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">It is probably best if Paul answers your questions but I take a stab at them below, understanding that I was not on the SLE WG.<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>
<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""> Seun Ojedeji [mailto:seun.ojedeji@gmail.com]
<br>
<b>Sent:</b> Tuesday, October 13, 2015 4:46 PM<br>
<b>To:</b> Gomes, Chuck<br>
<b>Cc:</b> Andrew Sullivan; cwg-stewardship@icann.org<br>
<b>Subject:</b> Re: [CWG-Stewardship] SLE update - ICANN seeks to delay SLE Accountability reporting......<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">On Tue, Oct 13, 2015 at 8:57 PM, Gomes, Chuck <<a href="mailto:cgomes@verisign.com" target="_blank">cgomes@verisign.com</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">I personally had assumed that the new SLEs would be implemented before or at the transition,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Perhaps we should ask the IETF of their experience when they tried updating their SLA (which was somewhat the outcome of the IANAPLAN) during the transition.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">but that doesn't mean that our proposal made that clear. Whether the SLEs are implemented as I thought they would be or as Andrew suggests, we need to first agree on the SLEs.<o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I had thought Paul's team passed the level of agreeing on the SLE requirements with IANA no?<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[Chuck Gomes] No. Most of them were not defined.<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><br>
<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal"> Most of them are not defined yet. The way I understand it is that the testing that the SLE WG proposed to help us define the SLEs. If I am correct on that, then we need to focus on implementing the testing.<o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">If I may, what does testing imply? does testing in this case mean working on the live system or creating a dummy setup or doing similar hypothetical test case scenario like it was done within the CCWG?<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[Chuck Gomes] I believe it meant working on a parallel system.</span></i></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">Cheers! <o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<span class="im">Chuck</span><br>
<br>
<span class="im">-----Original Message-----</span><br>
<span class="im">From: <a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a> [mailto:<a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a>] On Behalf Of Andrew Sullivan</span><br>
<span class="im">Sent: Tuesday, October 13, 2015 3:21 PM</span><br>
<span class="im">To: <a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a></span><br>
<span class="im">Subject: Re: [CWG-Stewardship] SLE update - ICANN seeks to delay SLE Accountability reporting......</span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">On Tue, Oct 13, 2015 at 07:11:35PM +0100, Paul M Kane - CWG wrote:<br>
> the IANA operator is either:<br>
> a) accountable to the NTIA via the SLA, or<br>
> b) accountable to the naming community via the SLE.<br>
<br>
Obviously. But changing the counterparty and changing the measurements in question are two completely separate problems. One is contract-only, the other involves changes to how the data is gathered, what the thresholds are, and even what data is gathered.<br>
<br>
> So delay in finalising the SLE just delays the date of transition from NTIA.<br>
<br>
That doesn't follow, and Annex H doesn't say that. There's nothing in Annex H by my reading that requires that the actual data gathered and the levels of service need to change at the same time the parties to the agreement change, unless I am missing something.<br>
<br>
From a technical operations standpoint, this is the most stable way to<br>
proceed:<br>
<br>
1. Get an agreement that the old SLE measurements and levels remain in place but that the new counterparty is ICANN to PTI.<br>
<br>
2. Get an agreement that within n months (for some n) the new SLE measurements and levels take effect.<br>
<br>
[transition can happen after that]<br>
<br>
3. Run in parallel the new-SLE and old-SLE measurements under ICANN stewardship. Iterate until working.<br>
<br>
4. Switch over to new SLEs by month n.<br>
<br>
As nearly as I can tell, that approach is completely consistent with what's in Annex H and doesn't block the transition. I was not arguing that the new SLEs are not valuable or shouldn't be pursued. I argued before (and argue now) that the above approach
is consistent with the goal, maximises stability, and allows the transition. Contrary to what Milton seems to be implying, I'm not trying to undo any consensus; frankly, this is what I thought people had agreed to since the SLE text wasn't even close to ready
in time to submit to the ICG.<br>
<br>
If people are insistent on something else and IANA can't deliver on the timetable we want (which seems to be the report), what is the fallback plan? For it seems to me that it'd be a needless crisis if these SLEs can't be had as quickly as one would like.<br>
<br>
Best regards,<br>
<br>
A<br>
<br>
--<br>
Andrew Sullivan<br>
<a href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<br>
-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">------------------------------------------------------------------------<span style="color:#888888"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><i><span style="font-family:"Garamond","serif";color:#006600">Seun Ojedeji,<br>
Federal University Oye-Ekiti<br>
web: </span></i><i><span style="font-family:"Garamond","serif";color:#888888"><a href="http://www.fuoye.edu.ng" target="_blank">http://www.fuoye.edu.ng</a><br>
</span></i><i><span style="font-family:"Garamond","serif";color:#006600">Mobile: +2348035233535</span></i><i><span style="font-family:"Garamond","serif";color:#888888"><br>
</span></i><i><span style="font-family:"Garamond","serif";color:#006600">alt email:<a href="http://goog_1872880453" target="_blank">
</a><a href="mailto:seun.ojedeji@fuoye.edu.ng" target="_blank">seun.ojedeji@fuoye.edu.ng</a></span></i><span style="font-family:"Garamond","serif";color:#888888"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Garamond","serif";color:#888888">Bringing another down does not take you up - think about your action!<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>