<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Jordan, et al,<div><br></div><div>A potentially unintended consequence of the wording might be an inability to INCREASE the IANA budget should the need arise. If a need arises for the PTI do something not anticipated in its annual budget, ICANN ought to be able to provide the additional funds. I think these words, as written, impose the same barrier for adding funds as there would be for reducing the funding.</div><div><br></div><div>Another concern is who determines what the budget should be and on what basis. Do we want to put the PTI in the position of campaigning to the community to put pressure on ICANN management to increase its budget each year?</div><div><br></div><div>Thanks,</div><div><br></div><div>Steve</div><div><br></div><div><br><div><div>On Jul 18, 2015, at 11:09 AM, Jordan Carter <<a href="mailto:jordan@internetnz.net.nz">jordan@internetnz.net.nz</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=utf-8"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi all<div class=""><br class=""></div><div class="">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<div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">In our discussion we sketched out the following thoughts:</div><div class=""><ul class=""><li class="">The IANA Budget (the PTI Budget) would be a separate Budget from the ICANN budget.</li><li class="">The same community veto power would be available for the IANA Budget as for the ICANN budget.</li><li class="">The threshold for a veto of the IANA Budget could be lower than is proposed for the ICANN budget, due to its greater sensitivity.</li><li class="">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.</li><li class="">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.</li></ul><div class="">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. </div><div class=""><br class=""></div><div class="">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. </div></div><div class=""><br class=""></div><div class="">Thoughts on the general approach? The separate IANA Budget? A different threshold?</div><div class=""><br class=""></div><div class="">cheers</div><div class="">Jordan</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><p class="" style="margin: 0cm 0cm 12pt 54pt;"><span lang="EN-US" class="">1.<span style="font-size: 7pt; font-family: 'Times New Roman';" class=""> </span></span><b class=""><span lang="EN-US" class="">ICANN Budget and IANA Budget. </span></b><span lang="EN-US" class="">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.</span></p></div><div class=""><span lang="EN-US" class=""><br class=""></span></div><div class="">
<div class=""><span style="color: rgb(34, 34, 34); font-family: arial; font-size: small; background-color: rgb(255, 255, 255);" class="">-- </span><br style="color: rgb(34, 34, 34); font-family: arial; font-size: small;" class=""><div dir="ltr" style="color: rgb(34, 34, 34); font-family: arial; font-size: small;" class="">Jordan Carter<br class=""><br class="">Chief Executive <br class=""><b class="">InternetNZ</b><br class=""><br class="">04 495 2118 (office) | +64 21 442 649 (mob)<br class=""><a href="mailto:jordan@internetnz.net.nz" target="_blank" style="color: rgb(17, 85, 204);" class="">jordan@internetnz.net.nz</a> <br class="">Skype: jordancarter<br class=""><br class=""><i class="">To promote the Internet's benefits and uses, and protect its potential.</i></div></div>
</div>
<br class=""></div></div>_______________________________________________<br>Accountability-Cross-Community mailing list<br><a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>https://mm.icann.org/mailman/listinfo/accountability-cross-community<br></blockquote></div><br></div></body></html>