<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Olivier & Jordan,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br>This is food for thought and agreed, we should try to improve the materials ahead of BA if necessary. We are working flat-out and I am sure the presentation is not fully refined at this stage.<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'>That said, we in the CWG have all come on a journey to get to where we are now and many of those attending the webinar haven’t been alongside us all the way.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Therefore, I think we do have to do some work to bring them along that journey in order to fully understand how and why we got to the current place which is a compromise for all of us.<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'>I think that there is a third and critical point. That is the role of members (and participants) to help communicate and explain the work – journey & output- of the group. Especially to those organisations that put appointed members onto the CWG.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>We need your help to communicate key points such as outlined by Olivier below. Please do assist in addition to helping us (chairs & staff) in our roles.<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'>Thanks,<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><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Jonathan<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 lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Jordan Carter [mailto:jordan@internetnz.net.nz] <br><b>Sent:</b> 11 June 2015 08:52<br><b>To:</b> Olivier MJ Crepin-Leblond<br><b>Cc:</b> cwg-stewardship@icann.org<br><b>Subject:</b> Re: [CWG-Stewardship] Feedback on First Webinar<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Dear all,dear Olivier<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I would like to just add my voice on the first point - it is my assumption that these webinars are aimed mainly at people who are coming new to the material and who will be looking to understand what they will approve - or not approve - in BA.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>If that assumption is right, I do urge that the format be changed so that the focus is on the substance of the proposal. Taking time on the process does not seem to be the right focus at this stage, for the audience.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>bests,<o:p></o:p></p></div><div><p class=MsoNormal>Jordan<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On 11 June 2015 at 19:42, Olivier MJ Crepin-Leblond <<a href="mailto:ocl@gih.com" target="_blank">ocl@gih.com</a>> wrote:<o:p></o:p></p><p class=MsoNormal>Hello all,<br><br>First, thanks to Lise for taking us through the slide deck and making a<br>complex proposal a lot more understandable.<br>Now for my comments:<br><br>- We have spent again around 30 minutes on the process reaching this<br>point and a much smaller time on the contents of the proposal itself. I<br>think that by this stage we should have a lot more detail in the actual<br>explanation of the contents of the proposal, describing CSC, IFR, the<br>PTI Board, SCWG, the escalation process (there is no slide showing all<br>of the various levels of escalation and remedials) from the time a<br>complaint starts and the various levels at which the complaint can be<br>addressed. IMHO *this* should be the meat of the presentation.<br>- Questions like "what happens to PTI if another IANA Functions Operator<br>is selected after separation?" are bound to come up recurrently and we<br>completely forgot to mention that this is just the Names and the<br>Protocols & Numbers will likely remain with PTI through their contract<br>with ICANN. This is not made clear at all that an IFR is only to do with<br>Names.<br>- We did not emphasize the technical nature of the whole ecosystem and<br>it therefore feels like a lot of these processes are political - and<br>this is not inspiring confidence. Emphasis on Service Level<br>Expectations; emphasis on Operational Continuity; emphasis on Stability<br>of the DNS. How are all of the processes and groups proposed<br>contributing to this emphasis?<br><br>I hope this helps.<br><br>Kind regards,<br><br>Olivier<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><p class=MsoNormal><br><br clear=all><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>-- <o:p></o:p></p><div><div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Jordan Carter<br><br>Chief Executive <br><b>InternetNZ</b><br><br>04 495 2118 (office) | +64 21 442 649 (mob)<br><a href="mailto: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><o:p></o:p></p></div></div></div></div></div></div></body></html>