IANA Stewardship Transition Process 09 March 2016 Implementation

  • Slides: 20
Download presentation
IANA Stewardship Transition Process 09 March 2016

IANA Stewardship Transition Process 09 March 2016

Implementation Planning Update

Implementation Planning Update

Post-Transition RZMS, RZMA & Names New Entities SLEs Status As Of Date: 03/08/16 Project

Post-Transition RZMS, RZMA & Names New Entities SLEs Status As Of Date: 03/08/16 Project Description Plan Completion Date Status % Complete RZMS changes to remove RZA role and support parallel testing Remove NTIA's authorization process from RZMS (code changes for ICANN and Verisign, and parallel testing). 09/30/15 08/15/16 40% Names SLEs (SLEs for Naming Community) RZMS code changes to accommodate new SLEs, inclusion of performance targets in ICANN-PTI contract, dashboard reporting of SLAs. 09/30/15 08/15/16 15% RZMA (Agreement with Root Zone Maintainer) Completion of draft RZMA. 01/31/16 02/29/16 90% Key Dates: ICANN’s Existing RZMS data Parsing code changes conclusions shared (RZA) NO V DE C ü JAN a ICANN’s RZMS code changes (SLEs) ü ü ü ICANN’s FE B a Start parallel testing MAR RZMS code RZMA changes ready for public (parallel review testing) Project Updates: ü Met with DT-A on 07 March to agree on future work phases and approach ü Met with Verisign to finalize the remaining issues ü Plan completion date for RZMS and Names SLEs changed to 15 August due to NTIA’s requirement DRAFT for Discussion SLA targets defined AP R VRSGN’s RZMS code changes (parallel testing) MA Y JU N JUL t End parallel testing c AU G Remove RZA Role in production RZMS t SE P c OC T NO V Insert SLAs SLA into ICANN- dashboard PTI contract ready Upcoming Activities: § Finalize draft RZMA § Begin tool development to aggregate and convert data On-track Not started Behind schedule, but recovery still Target will be missed Open Items: § Pending Verisign’s code changes to start parallel testing * All dates are estimates | 3

PTI Status As Of Date: 03/08/16 Project Description Plan Completion Date Formation of PTI

PTI Status As Of Date: 03/08/16 Project Description Plan Completion Date Formation of PTI entity: legal formation (incorporation of affiliate, filing for 501 c 3, drafting of contract, etc. ) and operationalization of PTI entity (board nominations, budget, etc. ). PTI (Post-Transition IANA) Key Dates: DE C JAN FE B MAR DRAFT for Discussion 10% PTI budget adopted by ICANN Board MA Y JU N JUL AU G SE P ICANNPTI contract ready for public review PTI implementation plan ready for public review Updates: ü Working with CWG on engagement process to implement PTI ü Plan completion date for PTI changed to 15 August due to NTIA’s requirement AP R % Complete 09/30/16 08/15/16 PTI entity legally formed NO V Status OC T NO V 501 c 3 status ready Upcoming activities: § Engagement with CWG on PTI implementation On-track Not started Behind schedule, but recovery still Target will be missed Open Items: * All dates are estimates | 4

IPR, RZERC, CSC & Escalation Processes Project Description Plan Completion Date Status As Of

IPR, RZERC, CSC & Escalation Processes Project Description Plan Completion Date Status As Of Date: 03/08/16 Status % Complete IANA IPR Transfer of IANA IPR to a neutral trust. RZERC (Root Zone Evolution Review Committee) Formation of committee to advise ICANN Board on RZMS architectural and operational changes. 09/30/16 08/15/16 10% CSC (Customer Service Formation of committee to monitor PTI performance. 09/30/16 08/15/16 10% Escalation Processes Updating of existing IANA operational complaint and escalation processes. 09/30/16 08/15/16 10% Standing Committee) Key Dates: 0% Escalation RZERC Draft charter Processes implementation planready for plan ready for review NO V DE C JAN FE B MAR AP R MA Y JU N CSC implementation plan ready for review Project Update: ü Working with CWG on engagement process to implement RZERC, CSC, and Escalation Processes ü Plan completion date for RZERC, CSC, and Escalation Processes changed to 15 August due to NTIA’s requirement DRAFT for Discussion JUL AU G SE P OC T NO V CSC constituted Upcoming Activities: § Engagement with CWG on PTI implementation On-track Not started Behind schedule, but recovery still Target will be missed Open Items: • Waiting on implementation requirements for IANA IPR * All dates are estimates | 5

Enhancing ICANN’s Accountability Project Description Status As Of Date: 03/08/16 Plan Completion Date Status

Enhancing ICANN’s Accountability Project Description Status As Of Date: 03/08/16 Plan Completion Date Status % Complete ICANN’s Bylaws Updating of ICANN Bylaws. 06/09/16 05/27/16* 10% IRP Enhancements Implement enhancements to Independent Review Process. 09/30/16 08/15/16 0% RR Enhancements Implement enhancements to ICANN's reconsideration request process. 09/30/16 08/15/16 0% Empowered Community Enhancements Implement processes and mechanisms in support of the empowered community. 09/30/16 08/15/16 0% * Assuming a 90 -days NTIA inter-agency review period Key Dates: Bylaws posted for public comment s NO V DE C JAN FE B c MAR c. AP Ra ICANN Board adopts Bylaws MA Y a JU N JUL AU G SE P OC T NO V • Key dates are based on assumption of proposals being delivered at ICANN 55. Project Update: ü The representatives from the CWG, CCWG, NTIA, Board, and staff met 08 March to discuss Bylaws drafting process and timeline ü Plan completion date for all projects changed to 15 August due to NTIA’s requirement DRAFT for Discussion Upcoming Activities: Open Items: § Final language of CCWG proposal On-track Not started Behind schedule, but recovery still Target will be missed * All dates are estimates | 6

Implementation of CWG-Stewardship Proposal: What does the cc. NSO need to do?

Implementation of CWG-Stewardship Proposal: What does the cc. NSO need to do?

Post-Transition New Entities Entity Customer Standing Committee (CSC) Root Zone Evolution Review Committee (RZERC)

Post-Transition New Entities Entity Customer Standing Committee (CSC) Root Zone Evolution Review Committee (RZERC) Description To monitor the performance of the PTI To advise the ICANN Board of the architectural and operational changes to the root zone environment To review PTI’s SOW and PTI’s performance against ICANN-PTI contract and SOW Occurrence On-Going As needed Special IANA Function Review Team (Special IFRT) Periodic (Within 2 years from the transition, then no more than every 5 years thereafter) To review the issues identified by CSC (only As needed cc. NSO and GNSO can initiate Special IFR) Separation Cross-Community Working Group (SCWG) To review the issues raised by the Special IFR and make recommendation [CSC Charter Review] To review CSC Charter IANA Function Review Team (IFRT) [CSC Effectiveness Review] [CSC Service Level Target Review] As needed (1 year after the first CSC meeting, then as requested thereafter) To review the effectiveness of CSC Periodic (2 years after the first CSC meeting, then every 3 years thereafter) To review the requests of review or change As needed to the service level targets Classification Standing Committee Cross Community Working Group Cross Community Working Group | 8

Required Work for Transition • Appointment of CSC members • Approval of the whole

Required Work for Transition • Appointment of CSC members • Approval of the whole composition of CSC • Appointment of RZERC member | 9

Timing of CSC Constitution ICANN submits implementation report to NTIA Expiration of IANA contract

Timing of CSC Constitution ICANN submits implementation report to NTIA Expiration of IANA contract 30 15 ICANN outreach SO/ACs appoint candidates ICANN sends SO/AC selected candidates to cc. NSO/GNSO CSC constituted Mar Apr May Jun Jul Aug Sep Oct Deadline | 10

Timing of RZERC Constitution ICANN submits implementation report to NTIA Expiration of IANA contract

Timing of RZERC Constitution ICANN submits implementation report to NTIA Expiration of IANA contract 30 15 ICANN outreach Candidates appointment RZERC constituted Mar Apr May Jun Jul Aug Sep Oct Deadline | 11

Customer Standing Committee (CSC) CSC Members: cc. TLD ROs | g. TLD ROs |

Customer Standing Committee (CSC) CSC Members: cc. TLD ROs | g. TLD ROs | TLD Rep (non g/cc. TLD) Liaisons: GAC | NRL/ASO | RSSAC | GNSO (non-registry) | ALAC | PTI Activity: • Ongoing membership management Activity: • Monitor PTI performance against agreed service level targets Activity: • Provide regular updates to the direct customers of the IANA naming function Touch point with cc. NSO • Reappointment due to recall or expiration of term Touch point with cc. NSO: • Review CSC escalated issues and decide whether to take further action with GNSO Touch point with cc. NSO: • Provide briefing to the cc. NSO and Ry. SG 3 times a year (i. e. ICANN meeting) | 12

Root Zone Evolution Review Committee (RZERC) RZERC Members: cc. NSO | GNSO Ry. SG

Root Zone Evolution Review Committee (RZERC) RZERC Members: cc. NSO | GNSO Ry. SG | ASO | IETF | RSSAC | RZM IFO | ICANN Board Activity: • Ongoing membership management Activity: • TBD per RZERC Charter Touch point with cc. NSO • Reappointment due to recall or expiration of term Touch point with cc. NSO • TBD | 13

IANA Function Review Team (IFRT) IFRT Members: cc. NSO | cc. TLD (non-cc. NSO)

IANA Function Review Team (IFRT) IFRT Members: cc. NSO | cc. TLD (non-cc. NSO) | Ry. SG | Rr. SG CSG | NSCG | RSSAC | GAC | ALAC | CSC Activity: • Appoint member Activity: • Review and recommend changes to IANA SOW Touch point with cc. NSO • Appoint members from cc. NSO • Appoint non-cc. NSO cc. TLD representative by consulting with Regional cc. TLD Organizations Touch point with cc. NSO • Provide ratification to IANA SOW amendment with GNSO | 14

Special IANA Function Review Team (Special IFRT) Special IFRT Members: cc. NSO | cc.

Special IANA Function Review Team (Special IFRT) Special IFRT Members: cc. NSO | cc. TLD (non-cc. NSO) | Ry. SG | Rr. SG CSG | NSCG | RSSAC | GAC | ALAC | CSC Numbers Community | Protocol Community Activity: • N/A Activity: • Appoint member Activity: • Recommend the creation of the Separation Cross. Community Working Group (SCWG) Touch point with cc. NSO • Review CSC escalated issues with GNSO to determine whether to trigger a Special IFR Touch point with cc. NSO: • Appoint members from cc. NSO • Appoint non-cc. NSO cc. TLD representative by consulting with Regional cc. TLD Organizations Touch point with cc. NSO: • Approve the creation of the SCWG with GNSO | 15

Separation Cross Community Working Group (SCWG) SCWG Members: cc. NSO | cc. TLD (non-cc.

Separation Cross Community Working Group (SCWG) SCWG Members: cc. NSO | cc. TLD (non-cc. NSO) | Ry. SG | Rr. SG | CSG NSCG | RSSAC | GAC | ALAC | CSC | IFRT Numbers Community | Protocol Community Activity: • Appoint member Touch point with cc. NSO • Appoint members from cc. NSO • Appoint non-cc. NSO cc. TLD representative by consulting with Regional cc. TLD Organizations | 16

[CSC Charter Review] Members: cc. NSO Ry. SG Activity: • Appoint member Activity: •

[CSC Charter Review] Members: cc. NSO Ry. SG Activity: • Appoint member Activity: • Make recommendation to change CSC Charter Touch point with cc. NSO • Appoint representatives from cc. NSO Touch point with cc. NSO • Provide ratification to recommended changes with GNSO | 17

[CSC Effectiveness Review] Members: TBD Activity: • TBD Touch point with cc. NSO •

[CSC Effectiveness Review] Members: TBD Activity: • TBD Touch point with cc. NSO • Determine methods of review with GNSO | 18

[CSC Service Level Target Review] Members: cc. NSO GNSO Activity: • Recommend change to

[CSC Service Level Target Review] Members: cc. NSO GNSO Activity: • Recommend change to the service level targets Touch point with cc. NSO • Provide ratification to proposed changes to service level targets with GNSO | 19

cc. TLD Community Work CWG-Stewardship Proposal Paragraph 1106 -6: Appeal mechanism. An appeal mechanism,

cc. TLD Community Work CWG-Stewardship Proposal Paragraph 1106 -6: Appeal mechanism. An appeal mechanism, for example in the form of an Independent Review Panel, for issues relating to the IANA functions. For example, direct customers with non-remediated issues or matters referred by cc. NSO or GNSO after escalation by the CSC will have access to an Independent Review Panel. The appeal mechanism will not cover issues relating to cc. TLD delegation and redelegation, which mechanism is to be developed by the cc. TLD community posttransition. | 20