[Gnso-newgtld-wg] - Community Comment 2 Next Steps

Mon Feb 20 15:51:47 UTC 2017

Hi WG members,

in 2.3 (Reserved Names). We in this WG are dealing with the terminology on daily basis – but not everybody we are tasking to provide feedback does. I have seen time after time people confusing the top-level and the second level when it comes to “reserved names”. For the avoidance of doubt I suggest to add for each section whether it pertains the top-level or the second level. Seems all bullet points but 2.3.5 concern top-level strings, only 2.3.5 is related to the 2nd level?

In 2.3.3 we ask: “…..should Country or Territory Names be allowed within the New gTLD Program (e.g., section 2.2.1.4.1 of the Applicant Guidebook)?”. 
This seems to be rather unspecific. What is  “e.g., section 2.2.1.4.1 of the Applicant Guidebook” be meant to say? 2.2.1.4.1 is the ONLY provision excluding ISO 3166 Alpha 3 / territory names. Why “e.g.”? That suggests there were other provisions. There are not. 
2.2.1.4.1 was a placeholder created to postpone the decision how ISO 3166 Alpha 3 / territory names are dealt with. An entire cross community WG spent YEARS to deal with the problem – and came recently up with very little (I am member of it). This can’t be addressed in a side sentence. I suggest the following changes:

Current version:
“For instance, should Country or Territory Names be allowed within the New gTLD Program (e.g., section 2.2.1.4.1 of the Applicant Guidebook)?”

Suggested version:

For instance, should Country & Territory Names or ISO 3166 Alpha-3 code elements (as specified in section 2.2.1.4.1 of the Applicant Guidebook) be allowed within the New gTLD Program? According to the current AG version they would already automatically require government support (2.2.1.4.2 AG). Would that be sufficient or would you suggest additional requirements (e.g. approval by the relevant ccTLD manager or GAC member)?

Background: I have observed in WGs and ICANN sessions as well as in personal discussions with ccTLD managers and GAC members that most stakeholders are NOT aware that removing section 2.2.1.4.1 of the Applicant Guidebook would OF COURSE still require Government support for these strings – as they are all part of the various sections of ISO 3166! Removing 2.2.1.4.1 would NOT result in territory, country names or 3166 Alpha 3 codes being available WITHOUT government support (nor should it in my opinion). 

Thanks,

Alexander Schubert

From: gnso-newgtld-wg-bounces at icann.org [mailto:gnso-newgtld-wg-bounces at icann.org] On Behalf Of Steve Chan
Sent: Friday, February 17, 2017 3:47 AM
To: gnso-newgtld-wg at icann.org
Subject: [Gnso-newgtld-wg] - Community Comment 2 Next Steps

Dear WG Members,

As you probably know, the WG is currently drafting its second request for community comment. The WG co-chairs and co-leaders of the work tracks encourage you to review the draft Community Comment 2 (CC2) questions and make suggestions in the document to amend language, add questions, omit questions, etc. The WG is collaborating via Google Docs, which can be found here: https://docs.google.com/document/d/1iZBCVEAJPBYEDg7jLsMHKkNczR_b6-jH2Wl5eVH-WWM/edit?usp=sharing. Attached, please find an extract of the questions in Word, for those that are unable to access Google Docs.

The intention is to distribute and publish these questions for public comment before ICANN58. To do so, here is the suggested path forward:

*         Members review and suggest changes. Some WTs may choose to discuss during their meetings, but we hope to conclude this phase on 24 February. Your contributions are critical to ensuring your voice is heard!

*         The full WG reviews CC2 on 27 February. This will be considered the first reading of CC2.

*         An additional full WG meeting will be scheduled for 6 March, where CC2 will be reviewed and be considered the second, and presumably final reading. 

Assuming agreement is reached on the 6 March meeting, CC2 would then be published for public comment, as well as distributed to the chairs of the various Stakeholder Groups, Constituencies, Supporting Organizations, and Advisory Committees. 

If you have any questions, please let staff or the WG leadership know.

Best,

Steve

Steven Chan

Sr. Policy Manager

ICANN

12025 Waterfront Drive, Suite 300

Los Angeles, CA 90094-2536

 <mailto:steve.chan at icann.org> steve.chan at icann.org

mobile: +1.310.339.4410

office tel: +1.310.301.5800

office fax: +1.310.823.8649

Find out more about the GNSO by taking our i <applewebdata://310CAD3E-E244-4690-A938-C2655DD44BDE/learn.icann.org/courses/gnso> nteractive courses and visiting the  <http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers> GNSO Newcomer pages.

Follow @GNSO on Twitter:  <https://twitter.com/ICANN_GNSO> https://twitter.com/ICANN_GNSO

Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/ 

 <http://gnso.icann.org/en/> http://gnso.icann.org/en/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg/attachments/20170220/72222d2c/attachment.html>