IGO/INGO Identifiers Protection Policy ImplementationImplementation Review Team Meeting | 28 June 2016

| 3

SessionObjective

Project Background

Project Status

Implementation Approach

Community Feedback

Next Steps

1 2 3

4 5 6

Agenda

| 4

Session Objective

¤ This Policy Implementation Review Team session at ICANN56 is open to public

¤ Community is invited to learn about this policy implementation project, ask questions and provide inputs to the Implementation Team

¤ Implementation Project Team consists of ICANN Staff and Implementation Review Team (IRT)

¤ Implementation Review Team is made up of community volunteers:

Jean-François Vanden Eynde – NameshieldRegistryBrian Cimbolic – PIRCrystal Ondo - DonutsDavid Maher – PIRPetter Rindforth - Fenix Legal KB

Lori Schulman - INTAMike Rodenbaugh - RodenbaughLawJim Bikoff - SGR LLPHolly Lance - SGR LLP

| 5

Project Background

This Policy Development Process (PDP) was initiated to develop policy recommendations for the provision of protection for identifiers of certain International Governmental Organizations (IGOs) and International Non-Governmental Organizations (INGOs), including the Red Cross/Red Crescent Movement (RCRC) and the International Olympic Committee (IOC).

The PDP Working Group completed its work in November 2013 and its consensus recommendations were approved by the GNSO Council. In April 2014, the ICANN Board adopted those of the PDP recommendations that were “not inconsistent” with GAC advice received on the topic, and requested more time to consider the remaining, inconsistent recommendations.

The adopted recommendations relate to protection at the top and second level for specific RCRC, IOC and IGO names (with an Exception Procedure to be designed for the affected organizations), and a 90-days Claims Notification process at the second level for certain INGO acronyms.

| 6

Policy Recommendation Scope TrackingOrg Board Resolution (A): “Not Inconsistent”

Implementation AuthorizedBoard Res (B) GNSO differing GACImplementation Not Authorized

RCRC Reserve Full Names of Red Cross, Red Crescent, Red Crystal, Red Lion & Sun at Top and Second levels in the 6 UN languages with Exceptions Procedure

189 National RC Societies: permanent protection vs 90-days claims only?Full name only vs acronyms also for ICRC and IFRC, etc?

IOC Reserve Full Names of OLYMPIC and OLYMPIAD at Top and Second Levels in UN6+German, Greek, & Korean with Exceptions Procedure

No difference

IGO Reserve Full Names of IGOs in GAC List at Top and Second Levels, in 2 languages with Exceptions Procedures

Protection for Acronyms?90-days or permanent claims?Access to Curative rights? + other ?

INGO Reserve Full Names of INGOs in ECOSOC General List at Top Level with Exceptions Procedure; Second Level: TMCH+90-days Claims Protection for INGO Full Names on ECOSOC General and Special Lists

No difference

| 7

Current Activities on IGO/INGOs Protections

IGO/INGO Identifiers Protection Policy Implementation (GDD, IRT)

IGO/INGO Currative Rights Protection Mechanism PDP WG (GNSO)

Protection of IGO/INGO Indentifiers in All gTLDs PDP WG

20 Nov. 2013GNSO Council

Resolution

30 Apr. 2014Board Resolution

5 June 2014GNSO Resolution Initiation of PDP

Reconciliation of GNSO Recommendation Differing from GAC Advice (Board)

Today

This Policy Implementation Project is focused on the “GNSO Recommendations Not Inconsistent with GAC Advice”

| 8

Implementation Plan and Status

¤ Secure Initial Authoritative Lists of Identifiers and Required Datao RCRC, IOC, INGO Identifiers – Completeo INGOs Contact Data – Completeo IGOs Identifiers – seeking ”up to two languages” from GAC

¤ Define List Update Processo INGO – in development working with UNDESA o IGO/IOC/RCRC - in definition with IRT

¤ Develop Systems and Processeso Full name reservation process

• Use current system/process o 90-day claims system

• TMCH-like system in design phase

| 9

IGO/INGO Identifier Initial Lists Status

Lists Status Action

RCRC Received; complete No further action

IOC Received; complete No further action

IGOIncomplete;

Received in one language only

Letter to GAC requesting the “up to two languages”

list(17 June 2016)

INGO Received; complete No further action

| 10

IGO/INGO Identifier Lists Update Process

¤ INGOo List Authority: ECOSOC List – UNDESAo Annual updated list provided by UNDESA to ICANNo ICANN provides the updated list to Claims system

¤ IGOo List Authority: GACo GAC may provide updated list “time to time” per policy recommendationo ICANN updates the reservation list upon receipt

¤ RCRCo No policy recommendation language received regarding updateso Follow the same process as IGO

¤ IOCo No policy recommendation language received regarding updateso Follow the same process as IGO

| 11

INGO Identifier 90-Day Claims System/Process

¤ Design approach in considerationo Coordinate and collaborate with UNDESA as the ECOSOC authorityo UNDESA provides ECOSOC list with Contact Data to ICANNo ICANN does not evaluate or adjust the ECOSOC list; use the list exactly

as receivedo ICANN produces DNS labels using the same algorithm used for existing

Spec. 5 Reserved Names Listo If the length of any label produced by the algorithm is not between 1

and 63, there is no resulting labelo The list and data are bulk loaded to the Claims Systemo A notice similar to the TMCH notices will be providedo New entries to ECOSOC list can only be made through UNDESA as the

list authorityo UNDESA provides an updated ECOSOC list to ICANN on an annual

basis per UNDES update cycleo ICANN updates the Claims System with each update from UNDESA

2015

DecOctSep Nov

2016

Feb AprJan Aug DecOctJun Jul Sep NovMar May

ICANN 56 (B) ICANN 57 (C)

FebJan Mar

2017

ICANN 54

Current Timeline Assumptions for Implementation

Apr Aug OctJun Jul Sep NovMay Dec

ICANN 59 (B)

ICANN 60 (C)ICANN 58 (A)ICANN 55 (A)

Drafting of Implementation Plan

Finalization of Implementation Plan with IRT

Public Comments on Draft Implementation Plan

Release of Draft Implementation Plan for Public Comment

Announce Policy Effective Date

Policy Effective Date

Implementation by Affected Parties & ICANN

IRT Meetings

| 13

Required Deliverables for Key Milestones

¤ Implementation Plan Release for Public Comment (target August 2016) 1. INGO: Agreement with UNDESA for ECOSOC list2. INGO: 90-day claims solution defined3. IGO, IOC, RCRC list update process defined4. Draft consensus policy language document

• with implementation notes (community input?)¤ Announce Policy Effective Date (February 2017)

1. IGO list: up to two language from GAC2. IOC List3. RCRC List4. INGO List: ECOSOC list with contact info5. Claims system designed and ready to implement6. Implementation Notes for Registries7. Final Consensus Policy Language

¤ Policy Effective Date (6 months from announcement)1. The Policy Language posted2. Claims system operational

| 14

Next Steps for Implementation Team

¤ Pursue MoU with USDESA¤ Define 90 day claims system¤ Define list update process for IGO, IOC, and RCRC¤ Develop Draft Consensus Policy Language for Public Comment

¤ Next scheduled IRT Meetingso IRT call 28 July 2016o IRT call 25 August 2016 (last review before Public Comment)

¤ IRT Community wiki pagehttps://community.icann.org/pages/viewpage.action?pageId=54694212

| 15

Other Meetings of Interest at ICANN56

Tuesday, June 28 • 13:30 - 15:00GNSO IGO-INGO Access to Curative Rights Mechanisms Policy Development Process WGThe PDP WG considers whether or not existing processes such as the Uniform Dispute Resolution Policy and the Uniform Rapid Suspension procedure should be modified, or possibly a new process developed, to address the specific needs of international governmental organizations (IGOs) and international non-governmental organizations (INGOs)

Thursday, June 30 • 11:00 - 11:30 IGO/INGO Names and Acronyms Protections The objective of the session is to update the GAC on the developments on this issue and recommend further discussion from the GAC

| 16

Reach me at:Email: dennis.chang@icann.orgWebsite: icann.org

Thank You and Questions

gplus.to/icann

weibo.com/ICANNorg

flickr.com/photos/icann

slideshare.net/icannpresentations

twitter.com/icann

facebook.com/icannorg

linkedin.com/company/icann

youtube.com/user/icannnews

Engage with ICANN

Tell us what you think of the Policy Meeting Format.Download the ICANN56 Mobile App and complete a short survey.

meetingapp.icann.org