| 1

Welcome to Pre-ICANN62 Policy Webinar

This is a text box caption to describe the photo to the left.David Olive

Senior Vice President, Policy Development Support

PRE-ICANN63 POLICY OPEN HOUSE11 OCTOBER 2018

| 2| 2

Welcome and Introduction

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

David OliveSenior Vice President, Policy Development Support

| 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.

Designed by ICANN Communications | January 2017

GAC Governmental Advisory Committee | PDP Policy Development Process | SO/AC Supporting Organizations/Advisory Committees | WG Working Group

Generic Names Supporting Organization (GNSO)

GNSO Council, ICANN Board or an AC identifies issue.GNSO Council considers if issue will result in consensus policy.

If yes, GNSO Council requests Preliminary Issue Report.Staff publishes Preliminary Issue Report for Public Comment Period.Following Public Comment review, Final Issue Report is submitted for GNSO Council consideration.

GNSO Council considers Final Issue Report and decides whether to initiate PDP.If yes, GNSO Council develops/adopts charter for PDP WG.GNSO Council calls for volunteers to form PDP WG.

WG consults with Community and develops Initial Report for Public Comment Period.After reviews, WG submits Final Report to GNSO Council.

GNSO Council reviews Final Report and considers adoption.If adopted, GNSO Council submits Final Report to ICANN Board.

ICANN Board consults Community and GAC.ICANN Board votes on Final Report recommendations.

VOTE BY ICANN BOARD

FORM A WORKING GROUP

SCOPE THE ISSUE

DELIBERATE THE FINAL REPORT

INITIATE THE PDP

IDENTIFY THE ISSUE

GNSO Policy Development Process

1

2

3

4

5

6

gnso.icann.orgLearn more about the GNSO

GNSO Council is composed of 21 members — divided into 2 houses (contracted and non-contracted parties) — who work on generic top-level

domain name (gTLD) policies (e.g., .com, new gTLDs).The ccNSO (Council and members) works on global policies relating to

country code top-level domain name (ccTLD) policies (e.g., .br, .uk).

Country Code Names Supporting Organization (ccNSO)

ccNSO Policy Development Process

ccNSO Council, ICANN Board, Regional ccTLD organizations, SO/AC or at least 10 members of ccNSO may request Issue Report.ccNSO Council appoints issue manager.

Issue manager determines if issue is within the scope of ccNSO. ICANN Bylaws define and limit the scope of issues.

If issue is in scope and ccNSO Council approves Issue Report, PDP begins.ccNSO Council gives Public Notice and opens Public Comment Period.

ccNSO Council appoints WG to develop the policy.WG issues Initial Report.WG opens Public Comment Period.WG produces Final Report.ccNSO Council requests GAC input.

DEVELOP POLICY

VOTE BY ICANN BOARD

INITIATE THE PDP

VOTE BY ccNSO (TWO STAGES)

REQUEST AN ISSUE REPORT1

2

3

Stage 1. ccNSO Council deliberates Final Report and if adopted, makes recommendation to its members.Stage 2. If members approve, ccNSO Council submits Final Report to ICANN Board.

ICANN Board votes on Final Report recommendations, but national laws remain paramount.

4

5

6

ccnso.icann.orgLearn more about the ccNSO

SCOPE THEISSUE

FINAL REPORT

Address Supporting Organization (ASO)

ASO Address Council (AC) is composed of 15 volunteers — 3 from each of the Regional Internet Registries (RIRs)* — who work on global

Internet Protocol (IP) Address Policy.

ASO Global Policy Development Process

Any individual may submit global policy proposal to ASO AC or RIR.RIR PDP generates global policy proposal.ICANN Board may also request global policy proposal.

Five RIRs review global policy proposal. Five RIRs must approve identical global policy proposal.Five RIRs submit approved global policy proposal to ASO AC for review.

ASO AC submits ratified global policy proposal to ICANN Board.

ICANN Board may accept, reject, request changes or take no action.

*Regional Internet Registries (RIRs) AFRINIC Africa APNIC Asia and Pacific region ARIN Canada, parts of the Caribbean and North Atlantic islands, and the U.S. LACNIC Latin America and parts of the Caribbean RIPE NCC Europe, the Middle East and parts of Central Asia

REVIEW BY ICANN BOARD

DETERMINE REQUIREMENTS

REVIEW BY RIRs AND ASO AC

IDENTIFY THE ISSUE1

2

3

4

aso.icann.orgLearn more about the ASO

ASO AC appoints Policy Proposal Facilitator Team (PPFT). ASO AC or PPFT determine if global policy proposal requires specific IANA functions actions or outcomes. ASO AC oversees global PDP.

2016 | Creative Commons Attribution - NonCommercial

C

M

Y

CM

MY

CY

CMY

K

| 4

Multistakeholder Advice Development

| 5| 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

| 6| 6

Supporting Organizations & Advisory Committees (SO/AC) Updates

| 7| 7

Country Code Names Supporting Organization (ccNSO)

Joke BraekenccNSO 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

| 8| 8

Country Code Names Supporting Organization (ccNSO)

Joke BraekenccNSO 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 rootzoneo How to remove, the road to removalo Oversight of process

• Next steps: stress test of recommended policy

| 9| 9

Generic Names Supporting Organization (GNSO)

Marika KoningsVice President, Policy Development for the GNSO

| 10| 10

Generic Names Supporting Organization (GNSO)

Significant time for PDP F2F WG meetings:• EPDP on Temporary

Specification• New gTLDs Subsequent

Procedures• Review of Rights

Protection Mechanisms in all gTLDs

Bilateral meetings with the ICANN Board,

ccNSO and Governmental Advisory

Committee

GNSO Sunday Sessions: • PDP 3.0• Update on new approach

for fellowship program• Interview with GNSO

Chair Candidates• Internet Governance

Engagement Group

GNSO Stakeholder Group and

Constituency Meetings

GNSO Council Meeting: • Curative Rights Protections

for IGO/INGOs PDP• GNSO Council Liaison to

the GAC• GNSO Chair Elections• Termination of Next

Generation RDS PDP WG

GNSO Wrap-up Session

ICANN63 Highlights

| 11

EPDP on Temporary Specification for gTLD Registration Data

On 17 May 2018, the ICANN Board approved the Temporary Specification for gTLD Registration Data to allow contracted parties to comply with existing ICANN contractual requirements while also complying with the European Union's General Data Protection Regulation (GDPR). The adoption of the temporary specification triggered the requirement for the GNSO to complete a consensus policy development process on the temporary specification within a one year period. An EPDP was initiated on 19 July 2018

OverviewExtensive time has been carved out at ICANN63 to allow the EPDP Team to continue its deliberations as well as present its draft recommendations to the community:• Full day EPDP Team meeting on Saturday• EPDP Team sessions (90 minutes each) on Sunday,

Wednesday and Thursday• High Interest Topic session on Monday from 15.15 – 16.45

What to expect at ICANN63

The scope of the EPDP Team’s efforts includes confirming, or not, the Temporary Specification by 25 May 2019. Additionally, the scope includes discussion of a standardized access model to nonpublic registration data; however, these discussions will occur only after the EPDP Team has comprehensively answered a series of “gating questions”, which are specified in the charter.

EPDP Team’s Goal

| 12| 12

Generic Names Supporting Organization (GNSO)

Emily BarabasPolicy Manager

| 13

PDP on New gTLD Subsequent Procedures

The New gTLD Subsequent Procedures PDP (SubPro) was initiated in December of 2015 and is tasked with considering the 2012 round of the New gTLDProgram to determine how to improve, refine, or develop new policy recommendations for new gTLDs, taking into account existing new gTLD policy recommendations from the GNSO’s 2007 Final Report on the Introduction of New gTLDs.

OverviewThe SubPro PDP was allocated a full day to meet on Saturday. • From 09:00-13:15, Work Track 5 (WT5), dedicated to the

topic of geographic names at the top-level, will meet to discuss open topics and its draft Initial Report

• From 13:30-18:30, the full Working Group will meet to discuss a supplemental report and kick off sub groups charged with reviewing public comment on its Initial Report.

What to expect at ICANN63

The SubPro PDP will be looking to make progress on a number of areas and looks forward to input from the wider community. The SubPro PDP is focusing on three major areas:• Beginning review of feedback on its Initial Report• Receiving feedback on its supplemental report• Making progress towards publishing the WT5 Initial

Report after ICANN63.

SubPro’s Goals

| 14| 14

Address Supporting Organization (ASO)

Carlos ReyesStrategic Policy Planning Director

• Address Supporting Organization (ASO) Organizational Review Update

• Regional Internet Registry Policy Development Activities

| 15| 15

At-Large Advisory Committee (ALAC) and At-Large Community

Heidi UllrichVice President, Policy Development and At-Large Relations

• The 15 Member At-Large Advisory Committee represents the best interests of Individual Internet Users. At-Large consists of over 230 At-Large Structures and over 90 individuals.

• Change in ALAC Leadership at ICANN63 – Maureen Hilyard will become ALAC Chair as Alan Greenberg steps down after four years.

• At-Large at ICANN63 - At-Large will have 24 sessions during ICANN63 with a focus on two main projects and two primary policy issues.

• At-Large Review Implementation – The At-Large Review Implementation WG will continue to make progress on the 16 issues it is addressing including their policy advice process, outreach and engagement, and communications.

• At-Large Summit (ATLAS) III – Plans for a third At-Large Summit will be discussed during ICANN63. ATLAS III will be a smaller meeting focused on the At-Large Review Implementation taking place at ICANN66.

| 16| 16

At-Large Advisory Committee (ALAC) and At-Large Community

Evin ErdoğduPolicy Development Senior Coordinator

Silvia VivancoAt-Large Regional Affairs Senior Manager

• Policy Highlights at ICANN63• General Data Protection Regulation• Generic Top-Level Domain (gTLD) Subsequent Procedures• Policy Highlights since ICANN 62

• Regional At-Large Organization Activities at ICANN63• EURALO virtual General Assembly• AFRALO-AFRICANN meeting• Regional Leadership Activities to focus on key policy topics and

outreach and engagement activities

| 17| 17

Governmental Advisory Committee (GAC)

Robert HoggarthVice President, Policy Development and GAC Relations

• High Level Government Meeting

• GDPR (GNSO EPDP and Unified Access Model)

• 2 Character Country Codes at the Second Level

• Geographic Names (New gTLD Sub. Pro. PDP WT5)

• CCWG - Work Stream 2 Accountability

• IGO Curative Rights Protections

• Traditional Priorities:

o Direct Discussions with ICANN Board, ALAC, ccNSO, GNSO, Nominating

Committee, PTI

o GAC Communiqué

Barcelona Hot Topics For GAC:

| 18| 18

Governmental Advisory Committee (GAC)

High Level Government Meeting Highlights – Monday 22 October

• Hosted approximately once every two years by a GAC Member in conjunction with an ICANN public meeting and in addition to the usual GAC meeting.

• Concept grew out of recommendations made by previous Accountability and Transparency Review Teams (ATRT1 and ATRT2)(reaffirming roles & clearer understanding)

• Barcelona is the 4th HLGM• Four Topic sessions:

o The Role of and Opportunities For Governments in ICANN – Post IANA Transition

o Thematic Challenges in the IG Ecosystem – Cybercrime, Data Protection and Privacy

o The Internet Technological Evolution and the Role of ICANNo Global Digital Agenda and Internet Policies

• Participation From ITU Secretary General (Lunch Address To Delegation Leaders)• Post-Meeting Reception (Delegations with Board and SO-AC Chairs)• Additional GDPR Info session for government attendees• Seventy-one HLGM delegations have already RSVP’d for the meeting

| 19| 19

Root Server System Advisory Committee (RSSAC)

Carlos ReyesStrategic Policy Planning Director

• RSSAC040: Recommendations on Anonymization Processes for Source Internet Protocol (IP) Addresses Submitted for Future Analysis

• RSSAC039: RSSAC Statement Regarding ICANN`s Updated Key Signing Key (KSK) Rollover Plan

• RSSAC Organizational Review Update

| 20| 20

Root Zone Evolution Review Committee (RZERC)

Steve Sheng Senior Director, Policy Development Support and Team Lead in Support of RSSAC and SSAC

• RZERC001: Feedback on the Updated Plan for Continuing the Root Key Signing Key (KSK) Rollover

| 21| 21

Security and Stability Advisory Committee (SSAC)

• SAC102: Comment on the Updated Plan for Continuing the Root Key Signing Key (KSK) Rollover

• Update on Name Collision Analysis Project

• SSAC Organizational Review Update

Andrew McConachieTechnical & Policy Manager

| 22

Q & A

Questions and Answers

Adobe Connect room microphones have now been enabled. To activate your microphone, please click

on the microphone icon at the top of the toolbar and follow the instructions.

Please remember to MUTE your microphone when not speaking.

| 23

Questions received through the registration form 1

¤ What kind of support/background/profiles do the different PDP`s need? How can we achieve more PDP participation & engagement by newcomers/fellows? How much participation does the LAC region have on PDP? https://www.icann.org/news/multimedia/3335http://icannlac.org/EN/progress

¤ How long does a policy take before it is implemented and also what processes does it go through?

https://www.icann.org/news/multimedia/3335

¤ With so few words as possible, try to explain the policy in general, and how it will inflect the internet and affect users? Please give some examples. https://www.icann.org/policy

¤ Current state of EPDP for GDPR? Please see slide 11.

https://community.icann.org/x/IYEpBQ

| 24

Questions received through the registration form 2

¤ What is the role of GDPR to Root Zone DNSSec KSK?

There is no role or impact of GDPR to DNSSec KSK.

¤ How will emoji be used as second level domains and what are applications? When do ccTLDs reach retirement? What are the advantages of the ‘next generation RDS’ over the legacy WHOIS? Please see slide 11 and slide 8.

https://www.icann.org/en/system/files/correspondence/conrad-to-forrest-et-al-03oct18-en.pdf

https://www.icann.org/en/system/files/files/sac-095-en.pdf

¤ Trabajo en materia de políticas sobre el retiro de los dominios de alto nivel con código de país (ccTLD) - Work on policy regarding the removal of high level domains with country code (ccTLD)

Please see slide 8.

| 25

Engage with ICANN Policy Development Support

Contact us at policy-staff@icann.orgThank You!Follow us on Twitter:@ICANN @ccNSO@ICANN_GNSO @ICANNAtLarge

Recordings & slides from this Open House will be posted on the Policy Presentations Space on the ICANN website – see link in Adobe Connect Chat Pod and below:

https://www.icann.org/resources/pages/presentations-2012-08-27-en