<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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.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;}
/* List Definitions */
@list l0
{mso-list-id:1620528851;
mso-list-template-ids:1382846094;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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">My personal thoughts are inserted below.<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""> cwg-stewardship-bounces@icann.org [mailto:cwg-stewardship-bounces@icann.org]
<b>On Behalf Of </b>Jordan Carter<br>
<b>Sent:</b> Monday, July 20, 2015 7:18 PM<br>
<b>To:</b> cwg-stewardship@icann.org<br>
<b>Subject:</b> [CWG-Stewardship] Fwd: Meeting CWG requirements for IANA Budget - pls comment<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">All - views from CWG participants on the below would be useful / helpful.... <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Jordan <br>
<br>
---------- Forwarded message ----------<br>
From: <b>Jordan Carter</b> <<a href="mailto:jordan@internetnz.net.nz">jordan@internetnz.net.nz</a>><br>
Date: Sunday, 19 July 2015<br>
Subject: Meeting CWG requirements for IANA Budget - pls comment<br>
To: <a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a><br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal">Hi all<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">As noted, Lise and I have had a chat about the CWG’s requirements for the IANA Budget. There has to be provision as a fundamental bylaw and we need to be clear and constructive in how we provide appropriate<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The CWG’s purpose as I understand it, is that through this power the community has the chance to protect IANA's funding at an adequate level so that it can do its job.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In our discussion we sketched out the following thoughts:<o:p></o:p></p>
</div>
<div>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
The IANA Budget (the PTI Budget) would be a separate Budget from the ICANN budget.<b><i><span style="color:#1F497D">[Chuck Gomes]
</span></i></b><span style="color:#1F497D"> I don’t think it would be a problem if the IANA budget was a subset of the ICANN budget provided that all of the IANA costs are included and detailed in the IANA budget.</span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
The same community veto power would be available for the IANA Budget as for the ICANN budget.<b><i><span style="color:#1F497D">[Chuck Gomes]
</span></i></b><span style="color:#1F497D"> I think this is correct. If any compromise is made on this area in the CCWG, I think it would make sense for the veto power to at least apply to the IANA Budget.</span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
The threshold for a veto of the IANA Budget could be lower than is proposed for the ICANN budget, due to its greater sensitivity.<b><i><span style="color:#1F497D">[Chuck Gomes]
</span></i></b><span style="color:#1F497D"> I think we should discuss this further. A low threshold might make it too easy to delay IANA funding and could risk the stability of the services. Lowering the threshold would need to be accompanied by some other
requirements that would ensure sufficient ongoing funding so that services are not degraded and security is maintained.</span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
If an IANA Budget was vetoed, because of the requirement for earlier Budgeting, the issue would likely be resolved before the start of the relevant financial year.<b><i><span style="color:#1F497D">[Chuck Gomes]
</span></i></b><span style="color:#1F497D"> I don’t think this is a true statement. The process has been improved greatly so that community input is received early enough to result in possible changes to the draft budget before the Board acts on it. But the
Board still doesn’t act on it until late June, just before the new fiscal year starts. I assume the veto wouldn’t occur until after Board action so that would only leave a few days for resolution. Also, I suspect that it would take some time for the veto
process to take place.</span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
The caretaker proposal for the IANA Budget would be that if there had been a community veto and it carried into the new financial year, funding would continue at the same level.<b><i><span style="color:#1F497D">[Chuck Gomes]
</span></i></b><span style="color:#1F497D"> This would be a step in the right direction but what if a critical improvement project needed new funding?</span><o:p></o:p></li></ul>
<div>
<p class="MsoNormal">Now: this all looks very similar to what would happen to the ICANN budget. So the only critical design question is whether it is a part of the ICANN budget or whether it is separate. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I think separate makes sense. There will have to be a separate budget identified anyway, so this precursors future improvements to the IANA Budget review mentioned by the CWG. <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thoughts on the general approach? The separate IANA Budget? A different threshold?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">cheers<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>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.75in">
1.<span style="font-size:7.0pt"> </span><b>ICANN Budget and IANA Budget. </b>The ability for the community to approve or veto the ICANN budget after it has been approved by the ICANN Board but before it comes into effect. The community may reject
the ICANN Budget based on perceived inconsistency with the purpose, mission and role set forth in ICANN’s Articles and Bylaws, the global public interest, the needs of ICANN stakeholders, financial stability or other matters of concern to the community. The
CWG-Stewardship recommends that the IFO’s comprehensive costs should be transparent and ICANN’s operating plans and budget should include itemization of all IANA operations costs to the project level and below as needed. An itemization of IANA costs would
include “Direct Costs for the IANA department”, “Direct Costs for Shared resources” and “Support functions allocation”. Furthermore, these costs should be itemized into more specific costs related to each specific function to the project level and below as
needed. PTI should also have a yearly budget that is reviewed and approved by the ICANN community on an annual basis. PTI should submit a budget to ICANN at least nine months in advance of the fiscal year to ensure the stability of the IANA services. It is
the view of the CWG-Stewardship that the IANA budget should be approved by the ICANN Board in a much earlier timeframe than the overall ICANN budget. The CWG (or a successor implementation group) will need to develop a proposed process for the IANA-specific
budget review, which may become a component of the overall budget review.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:#222222;background:white">-- </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:#222222">Jordan Carter<br>
<br>
Chief Executive <br>
<b>InternetNZ</b><br>
<br>
04 495 2118 (office) | +64 21 442 649 (mob)<br>
<a href="javascript:_e(%7B%7D,'cvml','jordan@internetnz.net.nz');" target="_blank"><span style="color:#1155CC">jordan@internetnz.net.nz</span></a> <br>
Skype: jordancarter<br>
<br>
<i>To promote the Internet's benefits and uses, and protect its potential.</i><o:p></o:p></span></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
-- <br>
Jordan Carter<br>
Chief Executive, InternetNZ<o:p></o:p></p>
<p>+64-21-442-649 | <a href="mailto:jordan@internetnz.net.nz">jordan@internetnz.net.nz</a><o:p></o:p></p>
<p>Sent on the run, apologies for brevity<o:p></o:p></p>
</div>
</body>
</html>