pre icann63 policy open house
play

PRE-ICANN63 POLICY OPEN HOUSE 11 OCTOBER 2018 This is a text box - PowerPoint PPT Presentation

Welcome to Pre-ICANN62 Policy Webinar PRE-ICANN63 POLICY OPEN HOUSE 11 OCTOBER 2018 This is a text box caption to describe David Olive the photo to the left. Senior Vice President, Policy Development Support | 1 Welcome and Introduction


  1. Welcome to Pre-ICANN62 Policy Webinar PRE-ICANN63 POLICY OPEN HOUSE 11 OCTOBER 2018 This is a text box caption to describe David Olive the photo to the left. Senior Vice President, Policy Development Support | 1

  2. Welcome and Introduction David Olive Senior Vice President, Policy Development Support Open House Format ¤ Interactive Format | A question and answer exchange with the Policy Team ¤ Simultaneous Interpretation | Interpretation in Spanish ¤ Preparatory Materials | The Pre-ICANN63 Policy Report and Generic Names Supporting Organization Policy Briefing: ICANN63 Edition | 2 | 2

  3. Multistakeholder Policy Development Multistakeholder Policy Development The ICANN Policy Development Support Team facilitates bottom-up, consensus-driven processes for global gTLD, ccTLD and IP address policies. Generic Names Supporting Organization (GNSO) Country Code Names Supporting Organization (ccNSO) Address Supporting Organization (ASO) GNSO Council is composed of 21 members — divided into 2 houses ASO Address Council (AC) is composed of 15 volunteers — 3 from each The ccNSO (Council and members) works on global policies relating to (contracted and non-contracted parties) — who work on generic top-level of the Regional Internet Registries (RIRs)* — who work on global country code top-level domain name (ccTLD) policies (e.g., .br, .uk). domain name (gTLD) policies (e.g., .com, new gTLDs). Internet Protocol (IP) Address Policy. GNSO Policy Development Process ccNSO Policy Development Process ASO Global Policy Development Process 1 1 1 GNSO Council, ICANN Board or an ccNSO Council, ICANN Board, Any individual may submit global IDENTIFY THE AC identifies issue. REQUEST AN ISSUE REPORT Regional ccTLD organizations, IDENTIFY THE ISSUE policy proposal to ASO AC or RIR. ISSUE SO/AC or at least 10 members GNSO Council considers if issue RIR PDP generates global policy of ccNSO may request Issue will result in consensus policy. proposal. Report. ICANN Board may also request ccNSO Council appoints issue global policy proposal. manager. 2 2 2 If yes, GNSO Council requests SCOPE THE ISSUE Issue manager determines if issue is SCOPE THE Preliminary Issue Report. within the scope of ccNSO. ASO AC appoints Policy Proposal DETERMINE REQUIREMENTS ISSUE Facilitator Team (PPFT). Sta fg publishes Preliminary Issue ICANN Bylaws define and limit the Report for Public Comment Period. scope of issues. ASO AC or PPFT determine if global policy proposal requires specific IANA Following Public Comment review, 3 functions actions or outcomes. Final Issue Report is submitted for GNSO Council consideration. INITIATE THE PDP If issue is in scope and ccNSO ASO AC oversees global PDP. 3 Council approves Issue Report, INITIATE THE PDP GNSO Council considers Final Issue PDP begins. 3 Report and decides whether to ccNSO Council gives Public REVIEW BY RIRs AND ASO AC initiate PDP. Five RIRs review global policy Notice and opens Public proposal. If yes, GNSO Council Comment Period. 4 Five RIRs must approve identical develops/adopts charter for PDP WG . global policy proposal. ccNSO Council appoints WG to DEVELOP POLICY GNSO Council calls for volunteers to form PDP WG. develop the policy. Five RIRs submit approved global policy proposal to ASO AC for WG issues Initial Report. 4 FINAL review. REPORT WG opens Public Comment Period. WG consults with Community and FORM A WORKING 4 WG produces Final Report. develops Initial Report for Public GROUP ASO AC submits ratified global REVIEW BY ICANN BOARD Comment Period. ccNSO Council requests GAC input. policy proposal to ICANN Board. 5 A f er reviews, WG submits Final ICANN Board may accept, Report to GNSO Council. Stage 1. ccNSO Council VOTE BY ccNSO reject, request changes or take 5 (TWO STAGES) deliberates Final Report and if no action. adopted, makes DELIBERATE THE FINAL REPORT GNSO Council reviews Final Report recommendation to its and considers adoption. members. If adopted, GNSO Council submits Stage 2. If members approve, Final Report to ICANN Board. ccNSO Council submits Final *Regional Internet Registries (RIRs) 6 Report to ICANN Board. AFRINIC Africa 6 ICANN Board consults Community VOTE BY ICANN APNIC Asia and Pacific region and GAC. BOARD ICANN Board votes on Final Report VOTE BY ICANN ARIN Canada, parts of the Caribbean and North Atlantic islands, and the U.S. ICANN Board votes on Final Report recommendations, but national LACNIC Latin America and parts of the Caribbean BOARD recommendations. laws remain paramount. RIPE NCC Europe, the Middle East and parts of Central Asia Learn more about the GNSO Learn more about the ccNSO Learn more about the ASO gnso.icann.org ccnso.icann.org aso.icann.org GAC Governmental Advisory Committee | PDP Policy Development Process | SO/AC Supporting Organizations/Advisory Committees | WG Working Group Designed by ICANN Communications | January 2017 2016 | Creative Commons Attribution - NonCommercial | 3

  4. Multistakeholder Advice Development | 4

  5. Cross-Community and High Interest Sessions at ICANN63 • General Data Protection Regulation (GDPR) • Expedited policy Development Process (EPDP) on the Temporary Specification for generic Top-Level Domain (gTLD) Registration Data • Innovation in Top-Level Domains | 5 | 5

  6. Supporting Organizations & Advisory Committees (SO/AC) Updates | 6 | 6

  7. Country Code Names Supporting Organization (ccNSO) Joke Braeken ccNSO Policy Advisor • Policy Development Process (PDP) on the Retirement of Country Code Top Level Domains (ccTLDs) • Internationalized Domain Name (IDN) Policy Review • Progress made by the ccNSO Study Group on the use of emoji as second level domains • Customer Standing Committee (CSC) Effectiveness Review | 7 | 7

  8. Country Code Names Supporting Organization (ccNSO) Joke Braeken ccNSO Policy Advisor PDP on Retirement of ccTLDs • Completed to date: o analyses of cases to date (significant change of name of country, dissolution of country/territory) o Glossary/terminology • Under discussion, to be continued at ICANN63. Core elements for policy: o Applicability to all ccTLDs non-ccNSO members: ultimately ccTLD needs to be removed, o Time when needs to be removed from DNS rootzone o How to remove, the road to removal o Oversight of process • Next steps: stress test of recommended policy | 8 | 8

  9. Generic Names Supporting Organization (GNSO) Marika Konings Vice President, Policy Development for the GNSO | 9 | 9

  10. Generic Names Supporting Organization (GNSO) ICANN63 Highlights Significant time for PDP GNSO Sunday Bilateral meetings F2F WG meetings : Sessions : with the ICANN Board, • EPDP on Temporary • PDP 3.0 ccNSO and Specification • Update on new approach Governmental Advisory • New gTLDs Subsequent for fellowship program Committee Procedures • Interview with GNSO • Review of Rights Chair Candidates Protection Mechanisms in • Internet Governance all gTLDs Engagement Group GNSO Council Meeting : GNSO Wrap-up GNSO Stakeholder Session • Curative Rights Protections Group and for IGO/INGOs PDP Constituency • GNSO Council Liaison to Meetings the GAC • GNSO Chair Elections • Termination of Next Generation RDS PDP WG | 10 | 10

  11. EPDP on Temporary Specification for gTLD Registration Data Overview What to expect at ICANN63 On 17 May 2018, the ICANN Extensive time has been carved out at ICANN63 to allow the Board approved the Temporary EPDP Team to continue its deliberations as well as present its Specification for gTLD draft recommendations to the community: Registration Data to allow • Full day EPDP Team meeting on Saturday contracted parties to comply with • EPDP Team sessions (90 minutes each) on Sunday, existing ICANN contractual Wednesday and Thursday requirements while also • High Interest Topic session on Monday from 15.15 – 16.45 complying with the European Union's General Data Protection Regulation (GDPR). The EPDP Team’s Goal adoption of the temporary specification triggered the The scope of the EPDP Team’s efforts includes requirement for the GNSO to confirming, or not, the Temporary Specification by 25 complete a consensus policy May 2019. Additionally, the scope includes discussion of development process on the a standardized access model to nonpublic registration temporary specification within a data; however, these discussions will occur only after the one year period. An EPDP was EPDP Team has comprehensively answered a series of initiated on 19 July 2018 “gating questions”, which are specified in the charter. | 11

  12. Generic Names Supporting Organization (GNSO) Emily Barabas Policy Manager | 12 | 12

Recommend


More recommend