Current Status of WG Activities

Similar documents
IGO/INGO Identifiers Protection Policy Implementation. Meeting with the IRT 9 March 2016

Rights Protection Mechanisms: User Feedback Session

GNSO Council Report to the ICANN Board Locking of a Domain Name subject to UDRP Proceedings PDP

Contractual Compliance. Text. IPC Meeting. Tuesday, 24 June 2014 #ICANN50

Post- Expira,on Domain Name Recovery PDP WG. ICANN San Francisco March 2011

DOMAINS PROTECTED MARKS LIST (DPML) PRIMER

Proposed Final Report on the Post-Expiration Domain Name Recovery Policy Development Process Executive Summary

Privacy and Proxy Service Provider Accreditation. ICANN58 Working Meeting 11 March 2017

Introduction. Prepared by: ICANN Org Published on: 12 January 2018

UN FREEDOM OF INFORMATION POLICIES INTERNATIONAL TELECOMMUNICATION UNION (ITU)

The IDN Variant TLD Program: Updated Program Plan 23 August 2012

gtld Applicant Guidebook (v ) Module 5

New gtld Program. Community Priority Evaluation Result. Report Date: 3 September 2015

Related to the Internet

Draft Thick RDDS (Whois) Consensus Policy and Implementation Notes

Contracting and Onboarding!

Registration Abuse Policies Final Report. Greg Aaron, RAPWG Chair Sunday, 20 June 2010

Intellectual Property Constituency (IPC)

ICANN Contractual Compliance Proforma DNS Infrastructure Abuse November 2018 Registry Audit Request For Information (RFI)*

Proposed Interim Model for GDPR Compliance-- Summary Description

July 13, Via to RE: International Internet Policy Priorities [Docket No ]

Report of Public Comments

Progress Report Negotiations on the Registrar Accreditation Agreement Status as of 1 March 2012

en.pdf

DirectTrust Governmental Trust Anchor Bundle Standard Operating Procedure

UNCONTROLLED IF PRINTED

For Facilitator Use Only. B3. Conformity Assessment: Roles and Responsibilities (Perfect score: 30 points)

Post-Expiration Domain Name Recovery PDP Initial Report Update to the GNSO Council. Saturday, 19 June 2010

2. What do you think is the significance, purpose and scope of enhanced cooperation as per the Tunis Agenda? a) Significance b) Purpose c) Scope

A1. Actions which have been undertaken by Governments

BENEFITS of MEMBERSHIP FOR YOUR INSTITUTION

Whois Study Table Updated 18 February 2009

SSC Transformation Initiative Fairness Monitoring Services

IRTP Part A PDP Final Report. Thursday 16 April 2009 GNSO Council Meeting

Draft Applicant Guidebook, v3

Post-Expiration Domain Name Recovery PDP. Presentation of Final Report

Trademark Clearinghouse. Rights Protection Mechanism Requirements (Revised 6 Aug 2013)

Promoting accountability and transparency of multistakeholder partnerships for the implementation of the 2030 Agenda

Introduction to the American Academy of Forensic Sciences Standards Board

DISCUSSION PAPER. Board of Certification Oral Examination Consistency

The Open Group Standards Process Part 1 - Overview. Copyright 2015 The Open Group

General Update Contractual Compliance Initiatives and Improvements Audit Program Update Complaints Handling and Enforcement Summary

ICANN Contractual Compliance. ALAC Mee(ng. Sunday, 23 March 2014 #ICANN49

General Data Protection Regulation (GDPR)

Certification Standing Committee (CSC) Charter. Appendix A Certification Standing Committee (CSC) Charter

FileMaker Business Alliance. Program Guide

CSTD Working Group on improvements to the IGF Summary of the 3 rd meeting

GAC PRINCIPLES REGARDING gtld WHOIS SERVICES. Presented by the Governmental Advisory Committee March 28, 2007

Proposed Service. Name of Proposed Service: Technical description of Proposed Service: Redemption Grace Period for.name.

Request for Information on Domain Tasting 10 August 2007

OIX DDP. Open-IX Document Development Process draft July 2017

First Session of the Asia Pacific Information Superhighway Steering Committee, 1 2 November 2017, Dhaka, Bangladesh.

DNS Abuse Handling. FIRST TC Noumea New Caledonia. Champika Wijayatunga Regional Security, Stability and Resiliency Engagement Manager Asia Pacific

Introducing ICANN and the Global Partnership approach Giovanni Seppia European Liaison e-stas conference, Seville, 12 May 2006

Trademark Clearinghouse Requirements. September Draft September 2012 Page 1

InsideNGO Certificate

ICANN48 BUENOS AIRES. November 20th

APNIC Update. AfriNIC June Sanjaya Services Director, APNIC

ACCEPTABLE USE POLICY

Advisory Statement: Temporary Specification for gtld Registration Data

UNH-IOL NVMe Test Consortium

Invitation to Participate

ICANN and the IANA. Elsa Saade and Fahd Batayneh MEAC-SIG August 2016

Revised November EFESC Handbook

CERTIFICATE IN LUXEMBOURG COMPANY SECRETARIAL & GOVERNANCE PRACTICE

Introduction to GlobalPlatform Compliance Secretariat

Draft Applicant Guidebook, v4

Name Collision Mitigation Update

Fast Flux Hosting Final Report. GNSO Council Meeting 13 August 2009

WHOIS Studies Update. Liz Gasster

The General Assembly (GA) was established as part of the DNSO. The original guiding rules for establishment and participation can be found here.

9 March Assessment Policy for Qualifications and Part Qualifications on the Occupational Qualifications Sub-Framework (OQSF)

SCS FSC Chain-of-Custody Guidance for Certification of Multiple Sites FSC-STD V2-1

KENIC Report 2007/8. 33 rd ICANN Meeting, 4 th November 2008, Intercontinental Hotel, Cairo. Ali Hussein

SECTION 10 CONTRACTING FOR PROFESSIONAL SERVICES CONSULTANT COMPETITIVE NEGOTIATION ACT (CCNA)

ISAO SO Product Outline

Internet Governance The Global Agenda. Peter Major Special adviser Permanent Mission of Hungary to the UN, Geneva

亞洲域名爭議解決中心 ASIAN DOMAIN NAME DISPUTE RESOLUTION CENTRE (HONG KONG OFFICE)

FSC STANDARD. Standard for Multi-site Certification of Chain of Custody Operations. FSC-STD (Version 1-0) EN

IPv4 depletion & IPv6 deployment in the RIPE NCC service region. Kjell Leknes - June 2010

ITEM 6D TO: FROM: SUBJECT: DATE: background groups. STRATEGY. transition to HIGHLIGHTS. Process for New Program.

Webinar upgrade Rightside DPML

Payment Card Industry (PCI) 3-D Secure (PCI 3DS) Qualification Requirements for 3DS Assessors

ANNEX 2: Policy Development Process Manual

ICANN Update at PacNOG15

THE BERKSHIRE ARCHERY COACHING GROUP PRIVACY NOTICE

Notes for authors preparing technical guidelines for the IPCC Task Group on Data and Scenario Support for Impact and Climate Analysis (TGICA)

Agenda and General Information

APPROVAL PROCESS TO BE FOLLOWED FOR PROVISIONAL ACCREDITATION OF CBs UNDER FM CERTIFICATION SCHEME

Final Report on the Privacy & Proxy Services Accreditation Issues Policy Development Process

Proposal for a model to address the General Data Protection Regulation (GDPR)

PUTNAM CITY SCHOOLS Information Technology Services 5401 NW 40th Oklahoma City, OK 73122

New gtld Application Comments Forum User Guide

Impacts of the GDPR in Afnic - Registrar relations: FAQ

The Internet Society. on behalf of. The IETF Administrative Oversight Committee. Request for Proposal. RFC Editor RFC Format CSS Design

Website Privacy Policy

e180 Privacy Policy July 2018

Plenipotentiary Conference (PP- 14) Busan, 20 October 7 November 2014

Improving WHOIS- An Update. 20 November, 2013

Handbook December 2018

Transcription:

IGO/INGO PDP WG

Current Status of WG Activities WG published its Initial Report on 14 June includes policy recommendation options under consideration by the WG for the protection of IGO, RCRC, IOC and other INGO identifiers in all gtlds recommendation options do not represent a consensus position by the WG members objective of Initial Report is to solicit feedback from the community on these policy recommendation options reply period closes 7 August WG to review input received during public comment forum in view of reaching consensus on a set of policy recommendations

Solicitation of Public Comment To help facilitate community feedback on the number of specific proposed policy recommendation options, provided a structured response form in the public comment box. General Comments section Matrix of top and 2nd level protection options: respondents asked to indicate whether they support the type of protection being considered by the IGO-INGO WG, and the rationale Also asked to indicate which organizations should receive that particular type of protection for their respective identifiers: 1) IGOs; 2) RCRC; 3) IOC; 4) INGOs other than the RCRC and IOC

Solicitation of Public Comment Public discussion session in Durban on Wednesday, 17 July Professional facilitators to conduct interactive session to solicit feedback from the community Focus on key issues that would help the WG move forward in reaching consensus

OVERVIEW Policy Update IGO/INGO PDP 11.00 12.30 on Wednesday, 17 July in Hall 6 This session has two goals: 1.Raise awareness of why this issue is important and provide transparency on WG deliberations/contrasting positions to date 2.Facilitate an interactive discussion and solicit new ideas from the community on key outstanding issues to help guide WG moving forward Agenda Time Activity :05 min Welcome/introductions :15 min Description of activities/goals & presentation of topics and associated propositions :12 min Gallery walk input time #1, then rotate :12 min Gallery walk input time #2, then rotate :12 min Gallery walk input time #3, then rotate :12 min Gallery walk input time #4, then return to seats 5 :20 min Readout of key ideas generated at each position (~5 min / topic)

THE EXERCISE In our Gallery Walk exercise, participants will cycle through each of four locations in the room spending :12 minutes at each to discuss and provide their input on a topic there. While participants will move, each location will be staffed by two people throughout: A subject matter expert for that topic to prompt and answer questions A facilitator to help prompt input and ensure collection of ideas Topic B Topic C Topic A Topic D 6

TOPIC A Should the identifiers of IGOs & INGOs be protected at the top and/or second level? Proposition A Proposition B Proposition C Proposition D Protections should be provided to identifiers of qualifying INGOs Protections should not be provided to INGOs other than the RCRC and IOC Protections should be provided to identifiers of INGOs other than the RCRC & IOC Protections should not be provided to any IGOs or INGOs Other ideas or suggestions? 7

TOPIC B If protections are provided through a Reserved Names List, should there be an exception process to allow the relevant organization and/or a legitimate right holder to register the identifier at the top and/or second level? Proposition A Exception Option #1 Proposition B Exception Option #2 Proposition C No exception procedures Other ideas or suggestions? 8

TOPIC C Should organization acronyms be protected at the top and/or second level? Proposition A Proposition B Proposition C Protection from registration Use of a Clearinghouse Model and/or existing RPMs No protections Other ideas or suggestions? 9

TOPIC D What should be the objective set of criteria to determine whether an organization should receive special protections? Proposition A Proposition B Proposition C Matrix Recommendation #1 RCRC/IOC Matrix Recommendation #2 IGOs Matrix Recommendation #3 INGOs Other ideas or suggestions? 10

OUTPUTS XPLANE to provide high-resolution photos of notes collected as a digital archive ICANN to take the physical feedback (posters) ICANN option to provide write-up of the feedback collected to the community Example poster of feedback collected on a topic from an earlier ICANN workshop. 11

Remaining Work Consensus call on set of policy recommendations Consideration of exception procedures Consideration of mechanisms to apply any adopted protections in existing gtlds Issuance of draft Final Report for public comment prior to submission to GNSO Council

Thank you

Appendix

# Top-Level Comments / Recommendation Options Rationale Note 1: In some cases recommendations are mutually exclusive, while others may be made in conjunction with each other. Note 2: The Working Group has made a decision during the course of its deliberations that the four types of organizations listed in the scope of identifiers above should be looked at individually in terms of protection for their respective identifiers, due to the fact as noted above that the WG could not agree on a single set of objective qualification criteria for all of them. In the matrix of proposed policy recommendations below, IGO and INGO identifiers are listed together for the sake of simplicity. In the case where the RCRC and IOC are treated the same or listed together, this only reflects the view and actions of the GAC and ICANN Board to date, and does not reflect the approach of the WG. Therefore, with respect to each option, protections of IGO, INGO, IOC and RCRC identifiers may be considered separately from one another. Top-Level protections of only Exact Match, Full Name identifiers are placed in Applicant Guidebook section 2.2.1.2.3, of the Applicant 1 Guidebook, Strings "Ineligible for Delegation" (see option #3 for a variation of this) Top-Level protections of Exact Match, Acronym identifiers are placed in Applicant Guidebook section 2.2.1.2.3, of the Applicant Guidebook, 2 Strings "Ineligible for Delegation" (see option #4 for a variation of this) 3 IGO-INGO identifiers if reserved from any registration (as in options #1 and/or #2), may require an exception procedure in cases where a protected organization wishes to apply for their protected string at the Top-Level 4 NO Top-Level protections or reservations for Exact Match, Full Name will be created (i.e., identifiers of IGO-INGOs seeking protection will NOT be added to section 2.2.1.2.3, of the Applicant Guidebook, Strings "Ineligible for Delegation") 5 6 NO Top-Level protections or reservations for Exact Match Acronym will be created (i.e., identifiers of IGO-INGOs seeking protection will NOT be added to section 2.2.1.2.3, of the Applicant Guidebook, Strings "Ineligible for Delegation") IGO-INGO organizations be granted a fee waiver (or funding) for objections filed to applied-for gtlds at the Top-Level TOP-LEVEL

# Second-Level Recommendation Options Comments / Rationale Note 1: In some cases recommendations are mutually exclusive, while others may be made in conjunction with each other. Note 2: The Working Group has made a decision during the course of its deliberations that the four types of organizations listed in the scope of identifiers above should be looked at individually in terms of protection for their respective identifiers, due to the fact as noted above that the WG could not agree on a single set of objective qualification criteria for all of them. In the matrix of proposed policy recommendations below, IGO and INGO identifiers are listed together for the sake of simplicity. In the case where the RCRC and IOC are treated the same or listed together, this only reflects the view and actions of the GAC and ICANN Board to date, and does not reflect the approach of the WG. Therefore, with respect to each option, protections of IGO, INGO, IOC and RCRC identifiers may be considered separately from one another. 1 2 3 2nd-Level protections of only Exact Match, Full Name identifiers are placed in Specification 5 of Registry Agreement 2nd-Level protections of Exact Match, Acronym identifiers are placed in Specification 5 of Registry Agreement 2nd-Level protections of Exact Match, Full Name identifiers are applied for by the organization requesting protection and placed in a Clearinghouse Model modified to accommodate use by IGOs and INGOs (hereafter referred to as Clearinghouse Model ) Rationale: 4 2nd-Level protections of Exact Match, Full Name + Acronym identifiers are applied for by the organization requesting protection and placed in a Clearinghouse Model 5 6 7 IGO-INGOs allowed to participate in Sunrise phase of each new gtld launch IGO-INGOs allowed to participate in 90 Day Claims Notification phase of each new gtld launch IGO-INGOs allowed to participate in permanent Claims Notification of each gtld launch 2ND-LEVEL

# Second-Level Recommendation Options Comments / Rationale Note 1: In some cases recommendations are mutually exclusive, while others may be made in conjunction with each other. Note 2: The Working Group has made a decision during the course of its deliberations that the four types of organizations listed in the scope of identifiers above should be looked at individually in terms of protection for their respective identifiers, due to the fact as noted above that the WG could not agree on a single set of objective qualification criteria for all of them. In the matrix of proposed policy recommendations below, IGO and INGO identifiers are listed together for the sake of simplicity. In the case where the RCRC and IOC are treated the same or listed together, this only reflects the view and actions of the GAC and ICANN Board to date, and does not reflect the approach of the WG. Therefore, with respect to each option, protections of IGO, INGO, IOC and RCRC identifiers may be considered separately from one another. 8 Fee waivers or reduced pricing (or limited subsidies, e.g., first 2 entries) for registering into a Clearinghouse Model the identifiers of IGO-INGO organizations 9 Review and modify where necessary the curative rights protections of the URS and UDRP so that IGO-INGO organizations have access to these curative rights protection mechanisms. 10 Fee waivers or reduced pricing for IGO-INGOs filing a URS or UDRP action 11 Create a registration exception procedure for IGO-INGOs wishing to register a 2 nd -Level name or where 3 rd party, legitimate use of domain may exist 12 13 NO 2nd-Level reservations of an Exact Match, Full Name will be established (i.e., identifiers of IGO-INGOs seeking protection will NOT be added to Specification 5 of the Registry Agreement) NO 2nd-Level reservations of an Exact Match, Acronym will be established (i.e., identifiers of IGO-INGOs seeking protection will NOT be added to Specification 5 of the Registry Agreement) 2ND-LEVEL

# Recommendation Options Comments / Rationale 1 IOC & RCRC Qualification Criteria are based on international and national legal protections as recognized by the GAC and ICANN Board The scope of identifiers is outlined in 2.2.1.2.3 of Applicant Guide Book 2 IGO Qualification Criteria are defined by a list managed by the GAC GAC List (full name & acronym) submitted to ICANN Board 22 March 2013, noting that a further GAC response to the Board on language of protection, periodic review of the list, and treatment of potential coexistence claims is pending. INGO Qualification Criteria Proposal: 3 i. The INGO benefits from some privileges, immunities or other protections in law on the basis of the INGO s proven (quasi-governmental) international status; ii. The INGO enjoys existing legal protection (including trademark protection) for its name/acronym in over 50+ countries or in three (of five) ICANN regions or alternatively using a percentage: more than 50%; iii. The INGO engages in recognized global public work shown by; a. inclusion on the General Consultative Status of the UN ECOSOC list, or b. membership of 50+ national representative entities, which themselves are governmental/ public agencies or non-governmental organizations that each fully and solely represent their respective national interests in the INGO s work and governance. Some community members believe that INGOs (other than the IOC and RCRC) which have recognised global public missions and have been granted privileges, immunities, or other protections in law on the basis of their quasi-governmental international status and extensive legal protection for their names, should be afforded special protections if found eligible based on an objective set of criteria. The rationale is that such non-profit INGOs with global public missions (including well-known INGOs) are as vulnerable as the RCRC and IOC when it comes to battling the increasing potential and impact of cybersquatting (and such efforts would divert from their global public service and public funds.) Qualification Criteria