I've thought of a b/c mid point complication: <div><br></div><div>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.<div><br></div><div>That's not a wholesale review <span></span>but it's a little more than b), while respecting the need for conservatism and efficiency....</div><div><br></div><div>Jordan <br><br>On Sunday, 1 March 2015, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">+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.</p>
<p dir="ltr">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.</p>
<p dir="ltr">Cheers!</p>
<p dir="ltr">sent from Google nexus 4<br>
kindly excuse brevity and typos.</p>
<div class="gmail_quote">On 1 Mar 2015 01:46, "Chris Disspain" <<a href="javascript:_e(%7B%7D,'cvml','ceo@auda.org.au');" target="_blank">ceo@auda.org.au</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><span style="font-family:'Verdana';font-size:13px;color:rgb(102,102,102)">You read me right, man ;-)<br><div>
<p><br></p>
<p><br></p>
<p>Cheers,</p>
<p><br></p>
<p>Chris</p>
</div>
<br><div><div>On 1 Mar 2015, at 11:35 , Jordan Carter <<a href="javascript:_e(%7B%7D,'cvml','jordan@internetnz.net.nz');" target="_blank">jordan@internetnz.net.nz</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr">Hi all,<div><br></div><div>I think Chris's proposal makes sense too in logically separating:</div><div><br></div><div>a) porting across existing service level obligations to the post-transition environment;</div><div>b) creating the possibility of reviewing and changing them in future; and </div><div>c) reviewing and updating the substantive content</div><div><br></div><div>If I read him right a) and b) should be done, but c) should not. </div><div><br></div><div>That might trim the work this design team needs to do and make finalising the names community proposal easier...</div><div><br></div><div>cheers</div><div>Jordan</div><div><br></div><div><div class="gmail_extra"><br><div class="gmail_quote">On 1 March 2015 at 08:56, Avri Doria <span dir="ltr"><<a href="javascript:_e(%7B%7D,'cvml','avri@acm.org');" target="_blank">avri@acm.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#330033">
Hi,<br>
<br>
Makes sense to me.<br>
<br>
avri<span><br>
<br>
<div>On 28-Feb-15 18:43, Chris Disspain
wrote:<br>
</div>
<blockquote type="cite"><span style="font-family:'Verdana';font-size:13px;color:rgb(102,102,102)">
<div>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. </div>
<div><br>
</div>
<div>Thoughts?</div>
</span></blockquote>
<br>
<br><br>
</span><hr style="border:none;color:#909090;background-color:#b0b0b0;min-height:1px;width:99%">
<table style="border-collapse:collapse;border:none">
        <tbody><tr>
                <td style="border:none;padding:0px 15px 0px 8px">
                        <a href="http://www.avast.com/" target="_blank">
                                <img border="0" src="http://static.avast.com/emails/avast-mail-stamp.png">
                        </a>
                </td>
                <td><p style="color:#3d4d5a;font-family:"Calibri","Verdana","Arial","Helvetica";font-size:12pt">
                                This email has been checked for viruses by Avast antivirus software.
                                <br><a href="http://www.avast.com/" target="_blank">www.avast.com</a>
                        </p>
                </td>
        </tr>
</tbody></table>
<br>
</div>
<br>_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="javascript:_e(%7B%7D,'cvml','CWG-Stewardship@icann.org');" target="_blank">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></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><div dir="ltr">Jordan Carter<br><br>Chief Executive <br><b>InternetNZ</b><br><br>04 495 2118 (office) | <a href="tel:%2B64%2021%20442%20649" value="+6421442649" target="_blank">+64 21 442 649</a> (mob)<br><a href="javascript:_e(%7B%7D,'cvml','jordan@internetnz.net.nz');" target="_blank">jordan@internetnz.net.nz</a> <br>Skype: jordancarter<br><br><i>A better world through a better Internet </i><br><br></div></div></div>
</div></div></div>
_______________________________________________<br>CWG-Stewardship mailing list<br><a href="javascript:_e(%7B%7D,'cvml','CWG-Stewardship@icann.org');" target="_blank">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></blockquote></div><br></span></div><br>_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="javascript:_e(%7B%7D,'cvml','CWG-Stewardship@icann.org');" target="_blank">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></blockquote></div>
</blockquote></div></div><br><br>-- <br>Jordan Carter<br>Chief Executive, InternetNZ<p>+64-21-442-649 | <a href="mailto:jordan@internetnz.net.nz">jordan@internetnz.net.nz</a><p>Sent on the run, apologies for brevity<br></p></p>