The next call for the New gTLD Subsequent Procedures Working Group is scheduled to take place on Monday, 06 June 2016 at 16:00 UTC for 90 minutes.
09:00 PDT, 12:00 EDT, 17:00 London, 18:00 CEST
for other places see:http://tinyurl.com/hfbzcvr
Agenda:
Below, please find the proposed agenda for the New gTLD Subsequent Procedures WG meeting scheduled for Monday, 6 June 2016 at 16:00 UTC.
- Review Agenda
- Roll Call/SOIs
- Review of action items (https://community.icann.org/x/A0WAAw)
- CC1 Discussion, continued (redlined and clean drafts attached, in Word and PDF)
- AOB
Apologies: Samantha Demetriou, Carlos Raul Gutierrez, Tom Dale, Jannik Skou, Amr Elsadr, Christa Taylor
On audio only: None
Notes/Actions:
Next Proposed Meeting:
Monday, 13 June 2016, 1300 UTC
Notes/Action Items:
Review of Action Items
Responses from Advice/Statements request are coming in (SSAC)
Incorporate timelines from other efforts, like Advice/Statements, into the PDP WG timeline
CC1
1. Question 1(b) - will absence of ongoing mechanism have anti-competitive effect for potential applicants - what does "ongoing mechanism" mean? Does this cover all potential methods of having all applications received or something else?
ANSWER - assumption was that this meant "absence of any subsequent procedures for further new gTLDs", what about clarifying further to say "absence of any mechanisms or procedures to apply for any more new gTLDs"?
NOTE - could also define "mechanism" as it is used regularly throughout the document OR just delete the word "ongoing" (phrase "ongoing mechanism" originated in the 2007 GNSO report)
CONSENSUS - co-chairs and staff to discuss refining or modifying existing phrasing, to be shared on the list for resolution
2. Change final question in each section to specify "on this subject"
3. Add footnote regarding Spec 13 (for Subject 2, pg 6)
4. What does "Open TLD with minor charter registration challenges" (one of the several possible categories) mean? Some open TLDs have registration restrictions or may have them subject to a DRP (not the same as validated restricted registries)
SUGGESTION - Change to "Challenge Policy Restricted Registry" or render it a sub-type of validated restricted registries or clarify "self-validated" and "prior validation versus subsequent challenges"? In any case, the word "minor" does not seem appropriate - delete "minor" and replace with "self-validated" or other word/phrase?
CONSENSUS - co-chairs and staff to discuss and propose alternative wording to the list
5. Page 13, change "like ... in the ICANN Bylaws" to "e.g.". - OK
6. Be consistent as to usage of "Subsequent Procedures" (or similar phrasing) rather than "Rounds". Clarify language where necessary.
7. "Aggregate application limit" - intended to differentiate between total applications in a window/process/round versus an individual number of applications in a window/process/round;
SUGGESTION -
(1) change subject heading to be more precise: "Application Limits during an Application "Round"" - OK
(2) substitute "total" for "aggregate" - OK
8. Should Subject 6 (Question 6(b)) also cover total number of strings?
SUGGESTION - add "and/or the total number of strings" within each of the questions in Subject 6 - OK
9. 6(e) & 6(f) - could their placement create confusion? Move 6(g) up so it appears first - OK
10. For 6(g) - "number" not "numbers"; change "entity" to "applicant" - OK
Deadline to send - 10 June (but document should go out at the earliest opprtunity); give option to SO/AC/SG/Cs to answer either as online questionnaire or in document form?
Deadline for responses - recommend 45 days, deadline of 23 July (ICANN56 ends 30 June; RPM WG's input solicitation letter requests responses by 9 July)
