Dear All, ICANN Announces the Formation of Two Committees Required for IANA Stewardship Transition https://www.icann.org/news/announcement-2016-08-12-en ICANN announced on August 12 the formation of the Customer Standing Committee (CSC) and the Root Zone Evolution Review Committee (RZERC). Both newly formed committees are requirements for the completion of the IANA Stewardship Transition by the CWG-Stewardship. The CSC will perform the operational oversight of the performance of the IANA naming function, a role currently performed by NTIA. In its oversight role, the CSC will monitor the performance of the IANA naming function against agreed service level expectations. The CSC may also initiate reviews and make recommendations for post-transition changes to service level expectations. For more information, please see the CSC Charter<https://www.icann.org/iana_imp_docs/41-csc-charter-v-v1> [PDF, 139 KB] or the CSC Scope and Responsibilities<https://www.icann.org/iana_imp_docs/43-csc-scope-and-responsibilities-v-v2> [PDF, 83 KB]. Per the CSC Charter, the Country Code Names Supporting Organization (ccNSO) and the Generic Names Supporting Organization (GNSO) Councils have approved the full slate of the membership<https://www.icann.org/en/stewardship-implementation/customer-standing-commit...>. The RZERC will review proposed architectural changes to the content of the root zone, the systems (including both hardware and software components) used in executing changes to the root zone and the mechanisms used for distribution of the root zone. It will also make recommendations related to those changes for consideration by the ICANN Board. The ICANN Board's approval of recommendations developed through the RZERC will replace NTIA's current role in approval of architectural changes to the root zone. The ICANN Board adopted the RZERC Charter<https://www.icann.org/en/system/files/files/revised-rzerc-charter-08aug16-en...> [PDF, 50 KB], finalized through public comment<https://www.icann.org/public-comments/draft-rzerc-charter-2016-06-10-en>, on 10 August 2016. See the full committee here<https://www.icann.org/en/stewardship-implementation/formation-of-a-root-zone...>. These committees will not become operational unless and until the expiration of the IANA Functions Contract. Additional details on ICANN's implementation planning efforts can be found at https://www.icann.org/stewardship-implementation. ICANN Announces Incorporation of Public Technical Identifiers (PTI) https://www.icann.org/news/announcement-2-2016-08-11-en ICANN announced that the incorporation documents for the "Post-Transition IANA" organization have been filed and received by the California Secretary of State under the name Public Technical Identifiers (which will now be referred to as PTI). With this filing and receipt, PTI is now formed as a nonprofit public benefit corporation and controlled affiliate of ICANN. The PTI Incorporation Documents were drafted to reflect the recommendations of the IANA Stewardship Transition Coordination Group (ICG) proposal, as provided to the ICANN Board and transmitted to NTIA on 10 March 2016. PTI was formed to perform the naming-related IANA functions under contract with ICANN. The PTI Articles were posted for public comment on 1 July 2016. At its meeting on 9 August 2016, the ICANN Board approved the PTI Articles and directed ICANN staff to move forward with the incorporation of PTI. Although PTI now exists as a legal entity, it is not yet performing any work. PTI will not perform any services under the IANA Functions Contract with NTIA. PTI will only start performing the IANA functions upon the successful completion of the transition. At that point, PTI will perform the IANA functions pursuant to an IANA Naming Functions Contract with ICANN (released for public comment<https://www.icann.org/public-comments/iana-naming-function-agreement-2016-08...> from 10 August – 9 September 2016) and the subcontracts with ICANN for the performance of the numbering and protocol parameter services. For purposes of coherence of the IANA functions and overall operational logistics, the ICG proposal requires that the performance of the IANA numbering and protocol parameter functions be subcontracted to PTI. These subcontracting agreements are drafted and will be executed between PTI and ICANN so that they are in effect upon transition. The proposed Articles of Incorporation are the first of the various governance documents that will be necessary for PTI to be put into operation. In the coming weeks, ICANN will also be posting the final versions of the PTI Bylaws, Conflict of Interest Policy, Board Code of Conduct, and Expected Standards of Behavior. Each of these documents has already been subject to public comment, and will be submitted for ICANN and PTI Board approvals (where appropriate) before the transition. All efforts surrounding the Incorporation of PTI are designed to meet one of key the recommendations in the ICG proposal: the formation of a new legal entity to perform the three IANA functions. All implementation-planning efforts can be tracked at https://www.icann.org/stewardship-implementation. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken@icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org