<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=Windows-1252">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<base href="x-msg://68/"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Cambria;
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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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;}
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.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{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;}
--></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">Points taken Milton. I think we need to find the right balance on this.<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>
<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""> Milton L Mueller [mailto:mueller@syr.edu]
<br>
<b>Sent:</b> Wednesday, April 29, 2015 12:54 PM<br>
<b>To:</b> 'Martin Boyle'; Gomes, Chuck; 'CW Lists'; 'Grace Abuhamad'<br>
<b>Cc:</b> 'cwg-stewardship@icann.org'<br>
<b>Subject:</b> RE: [CWG-Stewardship] A few additional comments for … Two additional webinars on 6-7 May<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></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>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
<a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a> [<a href="mailto:cwg-stewardship-bounces@icann.org">mailto:cwg-stewardship-bounces@icann.org</a>]
<b>On Behalf Of </b>Martin Boyle</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">MB: I agree with Chuck on this. Our objective in oversight of the operation of the IANA functions should be to ensure as near a self-healing process
as we can get: spotting issues early and addressing them – and that was the thinking in the CSC design team, using internal escalation to ensure that there is a proper understanding of issues within the management chain so that resources can be brought to
bear. However, that relies on there being a will to resolve issues. If there is not and we end up with a failing IANA functions operator (as we have had in the past), we need to be able to find a solution and implement it quickly. That in itself is not
going to be easy without also having to face a slog against a reluctant bureaucracy.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">MM:
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I am glad that both you and Chuck think it would be a mistake to give anyone the right to operate IANA services in perpetuity.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Even so, I still detect a tendency to erect too many barriers to separability. The right to terminate the contract is just basic common sense.
It is the simplest and most powerful accountability mechanism there is. IANA is nothing but a clerical service performed for technical coordination needs. If an IANA functions operator does not do the job right, you fire them and find another service provider.
True, changing providers can create disruptions, and service providers often exploit these to lock you in to their service. But one of the weaknesses of the current proposal is that it makes this process of separation far too complex and slow. No one in the
community wants to change providers for the heck of it. But if they do, we should not make it difficult.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The IETF makes extensive use of IANA, and their MoU says is that they can terminate their agreement with ICANN with 6 months notice. For any reason,
at any time. In the DNS environment more stakeholders need to be consulted, so I don’t oppose having a more defined review process, but the idea that we must bend over backwards to ensure that the existing IANA functions operator is given 6 bites at the apple
before we can change it is a bit ridiculous. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></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">cwg-stewardship-bounces@icann.org</a> [<a href="mailto:cwg-stewardship-bounces@icann.org">mailto:cwg-stewardship-bounces@icann.org</a>]
<b>On Behalf Of </b>Gomes, Chuck<br>
<b>Sent:</b> 28 April 2015 22:42<br>
<b>To:</b> CW Lists; Grace Abuhamad<br>
<b>Cc:</b> <a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a><br>
<b>Subject:</b> Re: [CWG-Stewardship] A few additional comments for … Two additional webinars on 6-7 May<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Chris,<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">While I believe that that separation should only happen after several progressive steps and that it should be only done for intractable breaches, I also don’t
think it is wise to make it so difficult that ICANN essentially believes that there is no real threat of that happening because that would be little different than giving them the rights to operate IANA in perpetuity, which I think would be a terrible mistake.<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>
<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">cwg-stewardship-bounces@icann.org</a> [<a href="mailto:cwg-stewardship-bounces@icann.org">mailto:cwg-stewardship-bounces@icann.org</a>]
<b>On Behalf Of </b>CW Lists<br>
<b>Sent:</b> Tuesday, April 28, 2015 5:03 PM<br>
<b>To:</b> Grace Abuhamad<br>
<b>Cc:</b> <a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a><br>
<b>Subject:</b> [CWG-Stewardship] A few additional comments for … Two additional webinars on 6-7 May<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Good evening:<o:p></o:p></p>
</blockquote>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p class="MsoNormal">1.<span class="apple-tab-span"> </span>It is important that Post Transition IANA, as a whole, remains anchored with Protocols and Numbering, that is with IETF and the RIRs. There are several reasons for this. ( a ) Open Internet
Standards are critical for fair competition and low entry barriers. Governments and Users have an existential interest in the work of IETF. ( b ) Numbering, and particularly communications numbering are of critical interest to public policy. Most governments
have accepted with more-or-less good grace that that shall continue to be done for the Internet by the RIRs. However, I believe that in the last resort their ability to comment and advise on numbering policy through ICANN/IANA/GAC is a significant element
in their acceptance.<br>
<br>
2.<span class="apple-tab-span"> </span>The recent debate within the CWG has clearly revealed support for separation of IANA/Names from the other IANA functions and - if possible - from ICANN. Whether that has been for ideological or commercial reasons
is immaterial at this stage. The present CWG compromise proposal is workable for the time being, but I expect that debate on separation to re-open shortly after the transition, not least on the basis of the proposed array of IANA performance criteria.<br>
<br>
As a long-time student and practitioner of industrial economics applied to the information society, let me say that IANA, as a fully privatised commercial service, would become financially invaluable to its owners. I do not want to see that happen, ever.
The first line of defence is to ensure the continued integration of all IANA functions: Naming, numbering and protocols.<br>
The second line of defence is to make it as difficult as possible to separate IANA from ICANN (as to be reformed under the CCWG Accountability proposals). In the last resort, a 'separate' IANA must be protected as a public service against any form of capture.
However, that last resort is not yet credible. There are no safeguards in place, not least because the multistakeholder community has tacitly, if not explicitly, come to the conclusion that we do not wish to reproduce all the checks and balances that ought
to be present within ICANN, in the IANA context as well.<br>
<br>
3.<span class="apple-tab-span"> </span>Granted, IETF/CRISP/RIRs/CWG have all been working to date within their respective 'silos'. So be it, although the risks were already visible in ICANN 50/London. It is now up to the ICG to make sure that they do
not materialise. ICG must ensure that there is no 'poison pill' for post transition IANA arising from the 'separability' debate in CWG.<br>
<br>
Regards<br>
<br>
CW<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On 28 Apr 2015, at 22:18, Grace Abuhamad <<a href="mailto:grace.abuhamad@icann.org">grace.abuhamad@icann.org</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Dear CWG-Stewardship, <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Following a request from our GAC member Elise Lindeberg and the <a href="https://community.icann.org/x/ryYnAw"><span style="color:purple">two briefing webinars on 24 April</span></a> (last
week), the Chairs are going to hold two additional webinars on 6-7 May. The announcement will be posted within the next 24h, but I wanted to share the information with the group now. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">The two additional webinars will be held on:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#333333">6 May from 13:00 – 14:30 UTC </span></b><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#333333">(time zone converter </span><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><a href="http://www.timeanddate.com/worldclock/fixedtime.html?msg=CWG-Stewardship+Webinar&iso=20150506T13&p1=1440&ah=1&am=30"><span style="color:#0088CC;text-decoration:none">here</span></a><span style="color:#333333">)</span><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#333333">7 May from 06:00 – 07:30 UTC </span></b><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#333333">(time zone converter </span><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><a href="http://www.timeanddate.com/worldclock/fixedtime.html?msg=CWG-Stewardship+Webinar&iso=20150507T06&p1=1440&ah=1&am=30"><span style="color:#0088CC;text-decoration:none">here</span></a><span style="color:#333333">)</span><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Cambria","serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:#333333">These webinars will focus more on the content of the proposal and less on the work process that led to the development of the 2nd draft
proposal. The main value of these webinars is that they will allow for further questions and answers from the community, while still giving the community enough time to submit comments in time for the close of the public comment period on 20 May.</span><span style="font-family:"Cambria","serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Cambria","serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Brenda will send calendar notices to the group with call details. </span><span style="font-family:"Cambria","serif""><o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Talk to you all on the CWG call on Thursday, <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Grace<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif""><br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org"><span style="color:purple">CWG-Stewardship@icann.org</span></a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship"><span style="color:purple">https://mm.icann.org/mailman/listinfo/cwg-stewardship</span></a><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>