<div dir="ltr"><div><div>Hello Chuck,<br><br></div>In other to maximise time and hopefully reduce the volume query on DT outcome, i think the scope of work of the design team should be determined before leaving things to their creativity. <br><br></div><div>One of such scope is for the DT not to introduce new SLE(A) requirements but ensure there are means to update the requirements post-transition.<br></div><div><br></div>Regards<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 6, 2015 at 1:21 PM, Gomes, Chuck <span dir="ltr"><<a href="mailto:cgomes@verisign.com" target="_blank">cgomes@verisign.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">In my personal opinion, it is too early to decide that no changes should occur in the SLAs before transition. We should let the design team come up with recommendations
on that.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Chuck<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></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""> <a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounces@icann.org</a> [mailto:<a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounces@icann.org</a>]
<b>On Behalf Of </b>Martin Boyle<br>
<b>Sent:</b> Monday, March 02, 2015 5:49 AM<br>
<b>To:</b> Jordan Carter; Seun Ojedeji</span></p><div><div class="h5"><br>
<b>Cc:</b> <a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a><br>
<b>Subject:</b> Re: [CWG-Stewardship] Service Level Expectations Design Team Template<u></u><u></u></div></div><p></p>
</div>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB">Hi Jordan, all,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB">I liked your first compilation. I am less clear on what your amendment does: is it that the design team will seek to identify specific areas
of SLA that should be amended <i>before</i> transition? In other words, that a revised SLA would need to be negotiated (let’s not forget that we are talking about an agreement and there are usually consequences on amending service levels).<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB">Without having any clear idea of what the design team might decide falls in this revised category, I’m not very happy with munging b) and c):
processes that allow us to maintain the SLAs post transition and pre-transition changes. If it really is necessary to amend specific terms before transition, that is an additional step:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB"><u></u> <u></u></span></p>
<p style="margin-left:.25in">
<u></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB"><span>1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB">Pre-transition
<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB">a) identification of any conditions that need to be amended or updated
<b>before</b> transition and what needs to be done in order to address these concerns;<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB">b) porting across existing service level obligations to the post-transition environment; and<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB">c) creating the possibility of reviewing and changing them in future.<u></u><u></u></span></p>
<p style="margin-left:.25in">
<u></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB"><span>2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB">Post-transition
<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:.25in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB">d) Regular reviewing and updating the substantive content<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB">The design team would therefore look at a)-c). And I would expect there to be very few – and clearly justified – items under a).<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB">Martin<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" lang="EN-GB"><u></u> <u></u></span></p>
<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"">
<a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounces@icann.org</a> [<a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">mailto:cwg-stewardship-bounces@icann.org</a>]
<b>On Behalf Of </b>Jordan Carter<br>
<b>Sent:</b> 01 March 2015 07:17<br>
<b>To:</b> Seun Ojedeji<br>
<b>Cc:</b> <a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a><br>
<b>Subject:</b> Re: [CWG-Stewardship] Service Level Expectations Design Team Template<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">I've thought of a b/c mid point complication: <u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">It is: whether anything needs to be added to currently documented SLA standards to allow the transition to be acceptable to any key customer community.<u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">That's not a wholesale review but it's a little more than b), while respecting the need for conservatism and efficiency....<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Jordan <br>
<br>
On Sunday, 1 March 2015, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>> wrote:<u></u><u></u></span></p>
<p><span lang="EN-GB">+1 to Jordan's specific suggestion as well; considering that everything works just fine right now is an indication that repeating the current SLA would at least maintain status quo.<u></u><u></u></span></p>
<p><span lang="EN-GB">Will be good if that methodology is applied to other design teams as much as possible.
<br>
The goal is to build a stronger ICANN and so long as we have a multistakeholder means/process to do that, then our job is done.<u></u><u></u></span></p>
<p><span lang="EN-GB">Cheers!<u></u><u></u></span></p>
<p><span lang="EN-GB">sent from Google nexus 4<br>
kindly excuse brevity and typos.<u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB">On 1 Mar 2015 01:46, "Chris Disspain" <<a>ceo@auda.org.au</a>> wrote:<u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">You read me right, man ;-)<u></u><u></u></span></p>
<div>
<p><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB"><u></u> <u></u></span></p>
<p><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB"><u></u> <u></u></span></p>
<p><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">Cheers,<u></u><u></u></span></p>
<p><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB"><u></u> <u></u></span></p>
<p><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">Chris<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB"><u></u> <u></u></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">On 1 Mar 2015, at 11:35 , Jordan Carter <<a>jordan@internetnz.net.nz</a>>
wrote:<u></u><u></u></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">Hi all,<u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">I think Chris's proposal makes sense too in logically separating:<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">a) porting across existing service level obligations to the post-transition environment;<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">b) creating the possibility of reviewing and changing them in future; and <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">c) reviewing and updating the substantive content<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">If I read him right a) and b) should be done, but c) should not. <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">That might trim the work this design team needs to do and make finalising the names community proposal easier...<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">cheers<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">Jordan<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB"><u></u> <u></u></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">On 1 March 2015 at 08:56, Avri Doria <<a>avri@acm.org</a>> wrote:<u></u><u></u></span></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">Hi,<br>
<br>
Makes sense to me.<br>
<br>
avri<u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">On 28-Feb-15 18:43, Chris Disspain wrote:<u></u><u></u></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">On that basis I wonder whether we would not be better served by accepting the current status quo and building a mechanism for review and negotiated
changes to those service levels that could be employed immediately after transition and on an ongoing basis. <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">Thoughts?<u></u><u></u></span></p>
</div>
</blockquote>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB"><u></u> <u></u></span></p>
<div class="MsoNormal" style="text-align:center" align="center"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">
<hr style="color:#909090" noshade size="2" width="99%" align="center">
</span></div>
<table style="border-collapse:collapse" cellpadding="0" cellspacing="0" border="0">
<tbody>
<tr>
<td style="padding:0in 11.25pt 0in 6.0pt">
<p class="MsoNormal"><a href="http://www.avast.com/" target="_blank"><span style="text-decoration:none"><img src="http://static.avast.com/emails/avast-mail-stamp.png" border="0"></span></a><u></u><u></u></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p><span style="font-family:"Calibri","sans-serif";color:#3d4d5a">This email has been checked for viruses by Avast antivirus software.
<br>
<a href="http://www.avast.com/" target="_blank">www.avast.com</a> <u></u><u></u></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB"><u></u> <u></u></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB"><br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a>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><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB"><br>
<br clear="all">
<u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB"><u></u> <u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">--
<u></u><u></u></span></p>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">Jordan Carter<br>
<br>
Chief Executive <br>
<b>InternetNZ</b><br>
<br>
04 495 2118 (office) | <a href="tel:%2B64%2021%20442%20649" target="_blank">+64 21 442 649</a> (mob)<br>
<a>jordan@internetnz.net.nz</a>
<br>
Skype: jordancarter<br>
<br>
<i>A better world through a better Internet </i><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#666666" lang="EN-GB">_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a>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><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-GB"><br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a>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><u></u><u></u></span></p>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"><br>
<br>
-- <br>
Jordan Carter<br>
Chief Executive, InternetNZ<u></u><u></u></span></p>
<p><span lang="EN-GB"><a href="tel:%2B64-21-442-649" value="+6421442649" target="_blank">+64-21-442-649</a> | <a href="mailto:jordan@internetnz.net.nz" target="_blank">
jordan@internetnz.net.nz</a><u></u><u></u></span></p>
<p><span lang="EN-GB">Sent on the run, apologies for brevity<u></u><u></u></span></p>
</div></div></div>
</div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr">------------------------------------------------------------------------<br><font color="#888888"><blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;font-family:garamond,serif">
<i><span style="color:rgb(0,102,0)">Seun Ojedeji,<br style="color:rgb(0,102,0)"></span><span style="color:rgb(0,102,0)">Federal University Oye-Ekiti<br style="color:rgb(0,102,0)"></span><span style="color:rgb(0,102,0)">web: </span><a href="http://www.fuoye.edu.ng" target="_blank">http://www.fuoye.edu.ng</a><br>
<span style="color:rgb(0,102,0)"></span><span style="color:rgb(0,102,0)">Mobile: <a value="+2348035233535">+2348035233535</a></span><span style="color:rgb(0,102,0)"></span><br></i><i><span style="color:rgb(0,102,0)">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><br><br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The key to understanding is humility - my view !<br></blockquote></blockquote></font><br></div></div>
</div>