Transition Planning Update Trang Nguyen | 28 June 2016
Agenda Opening Remarks (Jonathan Robinson/Lise Fuhr) Implementation Planning Update (Trang Nguyen) Q&A Closing Remarks (Jonathan Robinson/Lise Fuhr) | 3
Opening Remarks Lise Fuhr and Jonathan Robinson
Implementation Planning Update
Implementation Planning Timeline – Proposals Delivered in March 2016 Completed Remaining Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep ICANN ICANN ‘15 ‘15 ‘16 ‘16 ‘16 ‘16 ‘16 ‘16 ‘16 ‘16 ‘16 55 56 Root Zone Management System Track 1 90% +40% 10% (RZMS) changes & parallel testing Root Zone Maintainer Agreement 95% +90% 5% (RZMA) Service Level Expectations (SLEs) for 75% +60% 25% Naming Community Service Level Agreements (SLAs) with 95% +50% 5% the Number Community IETF MoU Supplemental Agreement 95% +50% 5% Post-Transition IANA (PTI) Track 2 50% +40% 50% Root Zone Evolution Review Committee 60% 40% +55% (RZERC) Customer Standing Committee (CSC) 70% 30% +65% IANA Intellectual Property Rights (IPR) 35% +25% 65% IANA Operational Escalation Processes 90% +80% 10% ✔ ICANN Bylaws +90% ICANN Articles of Incorporation 50% 50% Independent Review Process (IRP) Enhancements 5% 95% Track 3 Reconsideration Request 5% 95% Enhancements Empowered Community 5% 95% Implementation of the post-transition 50% 50% Financial Planning Process | 6 Progress since ICANN 55
PTI Overview Board Officers Staff • 5 directors • Appointed by PTI Board • Seconded from ICANN to • 3 from ICANN or PTI staff • PTI President (seconded PTI • 2 by ICANN NomCom from ICANN at time of • After transition, ICANN will • Jonathan Robinson and transition) work to put in place Lise Fuhr to serve as • Treasurer (ICANN direct benefits, systems and interim directors shared resource) processes • Abide by Conflict of • Secretary (ICANN direct • Once in place, PTI will be Interest and Code of shared resource) required to offer Conduct employment to seconded employees and new hires Legal Status Services Operations • Affiliate of ICANN • Name • At time of transition, • ICANN is sole member • Number resources required to • Domiciled in California • Protocol Parameters support PTI’s operations • 501(c)(3) tax status • Other current IANA and legal status will be services provided by ICANN and the cost charged to PTI • PTI Board may review arrangement post transition | 7
ICANN-PTI Contractual Relationship | 8
Post-Transition Landscape | 9
Names SLEs Names SLEs Implementation Phases Developing Polishing proposal for developments community review Proposed performance targets will be shared with CWG’s SLE workgroup in July. Once they have been agreed upon with the community, SLAs will be included in the ICANN-PTI naming function contract. | 10
Customer Standing Committee (CSC) Composition Purpose • Monitor performance of PTI against Names SLAs. May also • Members recommend changes to SLAs. • 2 ccTLDs • 2 gTLDs • Undertake actions to address poor performance including • Optional 1 escalation to ccNSO and GNSO. representative from .ARPA, .MIL, or .GOV • As necessary, propose changes to IANA naming services or • Liaisons operations to enhance the provision of the naming • optional 1 liaison from services. each organization below: • GNSO (RrSG or Status & Next Step NCPH) • ALAC • NRO or ASO 1 June 2016: ICANN requested appointment • GAC of candidates • RSSAC • SSAC 22 July 2016: Deadline for appointments • PTI 10 August*: ccNSO & GNSO Councils’ final approval of CSC membership composition *Tentative date | 11
Root Zone Evolution Review Committee (RZERC) Composition Purpose • Review and provide input regarding proposed • ICANN Board architectural and operational changes to the root zone. • SSAC • RSSAC • As determined necessary by the committee, propose • ASO architectural and operational changes to the Root Zone • IETF for consideration by the ICANN Board. • RySG • Act as a consultation body for ICANN during the RFP • ccNSO process for the Root Zone Maintainer, if needed. • RZM • PTI Status & Next Step IOTF reviews Charter CWG reviews Charter 30-day public comment ICANN Board approves Charter ICANN requests appointments RZERC formed | 12
IANA IPR On-going coordination and collaboration between operational communities Operational Communities working on finalizing the IANA IPR framework Contracts will need to be drafted iana.org operational arrangement and approval processes need to be agreed-to | 13
Engage and Contribute Public Comment Root Zone Evolution Review Committee Charter https://www.icann.org/public- comments/draft-rzerc-charter-2016-06-10-en ICANN Restated Articles of Incorporation https://www.icann.org/public- comments/draft-restated-articles-incorporation-2016-05-27-en Volunteer Customer Standing Committee https://www.icann.org/en/stewardship-implementation/customer-standing-committee-csc Participate in, or Follow Discussions CWG-Stewardship Mail List cwg-stewardship@icann.org Implementation Oversight Task Force (IOTF) Mail List iotf@icann.org IANA IPR Mail List iana- ipr@nro.net | 14
Q&A
Recommend
More recommend
