Work Track 5 Overview and Update

Slides:



Advertisements
Similar presentations
1 Update on New gTLD PDP Joint GAC/GNSO meeting Avri Doria Chair, GSNO Council San Juan, Puerto Rico.
Advertisements

GNSO Policy Development Process. “The PDP is broken”….. Photo credit: 2013 NYCitywoman.
Text #ICANN51 GNSO PDP Improvements Status Update.
Cairo 2 November Agenda  Guidebook overview  Supporting and explanatory materials  Guidebook Module detail  Probable timelines 2.
#ICANN51 Saturday 11 October 2014 Next Session: Update - Policy & Implementation Working Group Presenter: J. Scott Evans (Co-Chair) More information:
Policy & Implementation WG Initial Recommendations Report.
GAC-GNSO Consultation Group On GAC Early Engagement in GNSO PDP London Progress Report 22/06/2014.
PDP Improvements Update & Discussion. | 2 Background  Ten proposed improvements aimed to streamline and enhance the GNSO PDP Ten proposed improvements.
CcNSO Update for APTLD New Delhi February 2012 Keith Davidson, ccNSO Councillor.
1 IDN TLD Progress Veni Markovski Manager, Regional Relations ccTLD Meeting, Slovenia – 7-8 Sept 2009.
GAC-GNSO Consultation Group On GAC Early Engagement in GNSO PDP London Progress Report 22/06/2014.
Text. #ICANN49 Data & Metrics for Policy Making Working Group Thursday 27 March 2014 – 08:00.
IRTP Part D PDP WG Items for Review. Items for Review Policy Development Process WG Charter GNSO WG Guidelines.
Text #ICANN51 GAC / GNSO Joint Meeting 12 October 2014.
Text #ICANN49 Policy & Implementation Working Group Update.
GNSO IDN work Dr Bruce Tonkin Chair, GNSO Council IDN Workshop Marrakech, June 25, 2006.
#ICANN50 Standing Committee on Improvements Implementation (SCI) Activities Update to the GNSO Council ICANN-50 London Meeting 21 June 2014.
Joint GAC – GNSO Meeting Wednesday 29 June – 9.30 –
ICANN60 Abu Dhabi – GAC Planning Timeline
Empowered Community Overview of Procedures | XX March 2017.
GAC WG Protection of Geographic Names Proposed draft
of Geographic Names in new gTLDs
Charter for the CCWG on the Use of New gTLD Auction Proceeds
GAC-GNSO Joint Meeting
Two different issues ref. country codes
ccNSO PDP(s) on retirement of ccTLDs and Review mechanism
Country and Territory Identifiers in New gTLDs
New gTLD Subsequent Procedures F2F
ICANN57 F2F Meeting Slides
New gTLD Auction Proceeds CCWG Status Update
GAC in Nomcom Working Group ICANN56 Helsinki , June 2016
GAC Working Group on Protection of Geographic Names in new gTLDs
Geographic protections
Community Session - Next-Generation gTLD Registration Directory Service (RDS) to replace WHOIS
Community Session - Next-Generation gTLD Registration Directory Service (RDS) Policy Requirements RDP PDP WG | ICANN59 | 26 June 2017.
Firewall Management Task Force
CWG on the use of Country & Territory names as TLDs (CWG UCTN)
Cross Community Working Group
SCC P2P – Collaboration Made Easy Contract Management training
Prepared by Rand E Winters, Jr. ASR Senior Auditor October 2014
Update to GNSO Council CWG Report on Rec6
Implementation Strategy July 2002
GAC Operating Principles
Transition Planning Update
CWG on the use of country & territory names as TLDs (CWG UCTN)
IDN Variant TLDs Program Update
GAC WG to Examine the Protection of Geographic Names in Any Future Expansion of New gTLDs Update on WT Track 5 Activities Geographic Names at the Top.
ICANN62 GAC Capacity Building
Introduction to the Generic Names Supporting Organization (GNSO) & Policy Development 23 May 2018.
Action Request (Advice) Registry
Update New gTLD Auction Proceeds CCWG Background information
Status of the RPMs PDP Susan Payne IPC Member and WG participant
Preparation for Meeting with the Board
Service System Structural Proposals
Structure–Feedback on Structure ED-2 and Task Force Proposals
GAC Meeting with the GNSO
One Size Does Not Fit All
ccNSO PDP Review Mechanism & Retirement
Updates about Work Track 5 Geographic Names at the Top-Level
Expedited Policy Development Process on the Temporary Specification for gTLD Registration Data Name of Presenter Event Name DD Month 2018.
Generic Names Supporting Organization
Initial Thoughts on GAC Operating Principles Evolution
New gTLD Subsequent Procedures / Rights Protection Mechanisms
NERC Reliability Standards Development Plan
ICANN61 Puerto Rico – GAC Planning Timeline
Welcome to Your First GAC Meeting
PUBLIC SCHOOL CHOICE RENEWAL PROCESS
GAC Standards and Work Processes Overview
NERC Reliability Standards Development Plan
GAC Travel Support Rules Update
Presentation transcript:

Work Track 5 Overview and Update ICANN62

What is Work Track 5? Work Track 5 is a sub-team of the New gTLD Subsequent Procedures Policy Development Process (PDP) Working Group (WG). The overall Working Group is tasked with calling upon the community’s collective experiences from the 2012 New gTLD Program round to determine what, if any changes may need to be made to the existing 2007 Introduction of New Generic Top-Level Domains policy recommendations. Work Track 5 seeks to review the existing policy and implementation related to the topic of geographic names at the top level, determine if changes are needed, and recommend revised or new policy or implementation guidance, as appropriate.

Why is Work Track 5 Doing this Work? There had previously been parallel efforts within the community working on the issue of geographic names, each with a different focus. The topic of geographic names at the top level is included within the charter of the New gTLD Subsequent Procedures PDP Working Group. The Cross-Community Working Group of Use of Country and Territory Names concluded in 2017. There continues to be a recognition in the community that further work is needed in this area, noting that there are strong interests in the GAC, ccNSO, ALAC, and ccNSO on this issue and divergent views. Work Track 5 offers an opportunity for community members from all SO/ACs (as well as anyone not associated with an SO/AC) to participate in discussions about the future treatment of geographic names at the top level.

How does Work Track 5 Complete its Work? Operates under the GNSO Operating Procedures. Flexibility to experiment with innovative ways to support collaboration and participation from across the community. Inclusive leadership model with four co-leaders representing the ccNSO, GAC, ALAC, and GNSO. Began meeting in November 2017. Currently meeting weekly with very active discussions taking place on the mailing list. Collaborative online tools to collect input. Cross-Community Sessions at ICANN62 are an important way for those in the community not involved in Work Track 5 to share their ideas and opinions on this topic. Please actively participate in the Cross- Community sessions even if you are attending sessions organized by your own SO/AC on this topic.

Membership and Decision-Making Anyone interested can join as a member (e.g., participate during meetings, send messages on list, etc.) or observer (i.e., receives emails sent to the list). Membership in the overall WG is not required. Only members will be included in consensus calls. Decision-Making Definitions for full consensus, consensus, strong support but significant opposition, and divergence available in Annex 1, section 3.6 of the GNSO Operating Procedures. GNSO PDPs do not vote, though some level of polling may occur. Decision-making is not based on the most voices.

What are Work Track 5’s Responsibilities? While WT5 is a sub team to the full New gTLD Subsequent Procedures PDP WG, it operates under its own specific Terms of Reference. The Terms of Reference document includes responsibilities of WT5 and information about how WT5 completes its work. Notes the need for an open participation model, where participants feel comfortable that the process is sufficiently inclusive. Goal is to establish a consensus-driven outcome in the form of policy recommendations and/or implementation guidance. WT5’s recommendations will be delivered to the full WG for consideration. The 4 WT5 co-leads brief the ALAC, ccNSO, GAC, and GNSO on a regular basis. WT5 members are expected to brief and liaise with their respective organizations, if applicable.

Scope of Work Scope - Geographic Names at the top-level only Two-character ASCII letter-letter combinations Country and Territory Names (alpha-3 on 3166-1, short and long- form on 3166-1, additional categories in section 2.2.1.4.1 of AGB) Capital Cities in 3166-1, city names, sub-national names (e.g., county, province, state on 3166-2) UNESCO regions and names appearing on the “Composition of macro geographical (continental) regions, geographical sub- regions, and selected economic and other groupings” Other geographic names such as geographic features (rivers, mountains, valleys, lakes, etc.) and culturally significant terms related to geography The extent to which additional languages receive protection

Work Track 5 Status Discussed categories of strings included in the 2012 Applicant Guidebook including identifying pros and cons of the 2012 AGB treatment: 2-character ASCII letter-letter combinations Country and Territory Names Other Geographic Names listed in the 2012 AGB Discussed whether there should be rules for other strings such as geographic features (rivers, mountains, valleys, lakes, etc.) and culturally significant terms related to geography that were not included in the 2012 AGB. Reviewed and validated a chart outlining the relevant program elements of the 2012 process and began to consider possible process improvements. Currently seeking input from WT members on a working document that seeks to capture the different perspectives and input received so far from WT members.

Preliminary Convergence The Work Track Co-Leaders are beginning to see convergence in support of the following: Continue reservation at the top-level for these country and territory related terms: Two-character ASCII letter-letter combinations. 3-character country codes on the International Organization for Standardization (ISO) 3166-1 list. Long-form and short-form country and territory names on the International Organization for Standardization (ISO) 3166-1 list. Defer broader questions about which entity/entities can apply for these strings and how they may be treated (for instance, as a gTLD, a ccTLD or something else). Continue requirement that an applicant must obtain a letter of consent/non-objection from the relevant government or public authority when applying for a capital city name.

Work Track 5 Timeline – Current Estimates Jul 2018 Aug 2018 October 2018 Q2 2019 Next Steps Draft Initial Report Publish Initial Report Close Public Comment on Initial Report Publish Final Report To adjust the length and width of the arrow, click on the arrow, grab a corner, and lengthen or shorten, depending on your preference. To add a bubble, click on the bubble, ensure it is fully highlighted, COPY and PASTE. Then drag the bubble to your preferred placement. To delete a bubble, click on the bubble, ensuring it is highlighted and click DELETE. If you make a mistake, go to your top bar on PP and click EDIT, UNDO