insert title here 75 characters maximum
play

Insert title here (75 characters maximum) Insert subtitle here (75 - PowerPoint PPT Presentation

Insert title here (75 characters maximum) Insert subtitle here (75 characters maximum) Name of Presenter Event Name PRE-ICANN62 POLICY WEBINAR DD Month 2017 12 JUNE 2018 | 1 Welcome to Pre-ICANN62 Policy Webinar This is a text box caption


  1. Insert title here (75 characters maximum) Insert subtitle here (75 characters maximum) Name of Presenter Event Name PRE-ICANN62 POLICY WEBINAR DD Month 2017 12 JUNE 2018 | 1

  2. Welcome to Pre-ICANN62 Policy Webinar This is a text box caption to describe David Olive the photo to the left. Senior Vice President, Policy Development Support | 2

  3. Policy Development Support 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. Policy Development Support Staff Subject Matter 11 Languages 34 Experts and • Afrikaans • Chinese SO/AC Support FTE • Dutch Services • English • French • German • Italian • Japanese 5 Time Zones • Spanish across 11 • Swedish • Turkish Countries | 4

  5. ICANN62 – Policy Forum 2 3 1 Policy Development Enhance Outreach Focus Cross-Community Components Interactions 4 5 No Opening No Public Forums Ceremony | 5

  6. ICANN62 Cross-Community and High Interest Topics ¤ Update from the Registration Directory Service (RDS) – WHOIS2 Review Team ¤ WHOIS/Registration Directory Service (RDS) Policy Post-General Data Protection Regulation (GDPR) ¤ Cross-Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) Work Stream 2 Final Recommendations ¤ Session on GNSO Temporary Specification for gTLD Registration Data Consensus Policy Development Process ¤ Geographic Names at the Top-Level | 6

  7. Cross-Community and High Interest Topics | 7 | 7

  8. Update from the Registration Directory Service (RDS) – WHOIS2 Review Team David Olive Senior Vice President, Policy Development Support | 8

  9. Update from the RDS-WHOIS2 Review Team Overview What to expect at ICANN62 RDS Review, formerly known During this session on Monday 25 June from 17.00 – as “WHOIS” is mandated by 18:30 the RDS-WHOIS2 Review Team will update the the ICANN Bylaws. The scope community on its findings to date. The Review Team of its work includes assessing will seek input on its findings and address any how the recommendations of questions pertaining to its scope and work plan. the first WHOIS Review were carried out, as well as assessing the effectiveness of the gTLD Registry Directory Service and whether its How to Prepare implementation meets the legitimate needs of law For more information please visit the RDS-WHOIS2 wiki enforcement, promoting https://community.icann.org/x/JIfDAw consumer trust and safeguarding registrant data. Learn more about the opportunities to participate in RDS-WHOIS2 work at https://community.icann.org/x/ccHRAw | 9

  10. WHOIS/Registration Directory Service (RDS) Policy Post-General Data Protection Regulation (GDPR) David Olive Senior Vice President, Policy Development Support | 10

  11. WHOIS/RDS Policy Post-GDPR Overview What to expect at ICANN62 The European General Data During this session on Tuesday 26 June starting at Protection Regulation (GDPR) 15:15, panelists will engage with the community to has precipitated significant discuss key policy changes resulting from the changes to the Registration Temporary Specification, and how to move forward Directory Services (RDS), with developing a final Consensus Policy that moves currently known as WHOIS. beyond the temporary policy toward a more permanent Most recently, the ICANN solution. Board adopted a Temporary Specification implementing an ICANN Org-driven interim How to Prepare GDPR compliance model for WHOIS. With the adoption of For more information; the Temporary Specification, the community has a new https://www.icann.org/dataprotectionprivacy opportunity to try an adopt an “ultimate model” for a next- generation registration data directory service. | 11

  12. Cross-Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) Work Stream 2 Final Recommendations David Olive Senior Vice President, Policy Development Support | 12

  13. CCWG-Accountability WS2 Final Report Overview What to expect at ICANN62 Cross-Community Working During this session on Wednesday 27 June from Group on Enhancing ICANN 17:00-18:30, the CCWG-Accountability Co-Chairs will Accountability has divided its present the recommendations in the final report of the work into two work streams. CCWG-Accountability WS2. The session will feature a Work Stream 2 focuses on facilitated question and answer dialogue to allow for addressing accountability comments from the community and chartering topics for which a timeline for organization members. developing solutions and full implementation may extend beyond the IANA Stewardship How to Prepare Transition. It has the following subgroups; Diversity, Guidelines for Good Faith For more information please visit the CCWG- Conduct, Human Rights, Accountability WS2 wiki Jurisdiction, Ombudsman, Reviewing the Cooperative https://community.icann.org/x/uQuOAw Engagement Process (CEP), SO/AC Accountability, Staff Accountability, Transparency. | 13

  14. Session on GNSO Temporary Specification for gTLD Registration Data Consensus Policy Development Process Caitlin Tubergen Policy Senior Manager, GNSO Support | 14

Recommend


More recommend