The call for the New gTLD Subsequent Procedures Sub Group A will take place on Thursday, 17 January 2019 at 15:00 UTC for 60 minutes.

07:00 PST, 10:00 EST, 16:00 Paris CET, 20:00 Karachi PKT, (Friday) 00:00 Tokyo JST, (Friday) 02:00 Melbourne AEDT

For other times: https://tinyurl.com/y7a8wk2z

PROPOSED AGENDA


  1. Agenda review/SOIs
  2. Discussion of Public Comments 
    1. 2.2.4: Different TLD Types (Specifically section 2.2.4.e.2, line 44 in the Google doc)
    2. Time permitting - 2.2.5: Applications Submission Limits
  3. AOB

For agenda item 2, please find the relevant public comment review document: https://docs.google.com/spreadsheets/d/15zDdzlBwLCz5m2sNXui6N6pporbUq-lDFEwfh4rKi4A/edit?usp=sharing

 BACKGROUND DOCUMENTS



RECORDINGS


Mp3

Adobe Connect Recording

GNSO transcripts are located on the GNSO Calendar

PARTICIPATION


Attendance & AC chat

Apologies: Michael Casadevall 

Guests: Collin Kurre, Iona Stupariu, Akriti Bopanna, Austin Ruckstuhl

Notes/ Action Items


Actions:


2.2.5.c.1: ACTION ITEM: Ask Public Interest Community the origin of the number reference in the following quotation: "We recommend that ICANN allow no more than 2 dozen applications for each company, including its parent company, subsidiaries, and affiliates. "


Notes:


1. Updates to Statements of Interest (SOIs): No updates provided.


2. Discussion of Public Comments :


a. 2.2.4: Different TLD Types (Specifically section 2.2.4.e.2, line 44 in the Google doc):


2.2.4.e.2:

Line 44, RySG -- See 2.2.4.c.1 above (Line 13): Support the existing brand categories;

Line 45, INTA -- See responses to 2.2.4.c.1 and 2.2.4.e.1 (Line 21): Support the creation of a Brand TLD; talk about that they think geographic TLDs are standard but have some pre-qualifications.


2.2.4.e.3:

Lines 47-49, Fairwinds, LEMARIT, ALAC -- Agreement.


Line 50, NABP - New Idea: As stated above, a verified TLD is one that requires verification of eligibility prior to use, adherence to standards, autonomy to take back a name, and ongoing verification. This definition - and by extension, a commitment to adhere to it -- should be included as a specification in the Registry Agreement for new applicants. Failure to continue to meet those qualifications would result in disciplinary actions up to and including a notice of breach of the Registry Agreement and, absent corrective actions, termination of the Registry Agreement.


From the chat:

Kathy Kleiman: But they are trying to set up a new type of objection so they can object to others trying to hve a New gTLD

Kathy Kleiman: OK

Kathy Kleiman: (not agreeing, but it makes sense they are asking for a new type of objection)

Justine Chew: We need a better way to link topics, or at least link or highlight related comments from the same contributor

Martin Sutton: @Jeff - that ties in with the INTA idea too, if objection/contention set can be resolved by amending string applied for, then their suggestion could be considered. Otherwise, can be ignored.

Kathy Kleiman: @Martin, the revision or amending of New gTLD strings could raise huge free expression and other public interest objections

Kathy Kleiman: @Martin, the revision or amending of New gTLD strings could raise huge free expression and other public interest objections

Kathy Kleiman: And NCSG has objected

Martin Sutton: @Kathy - I'm not putting an opinion forward, just making sure we pick up the relevant comments if other aspects of Sub Pro create changes

Jeff Neuman (Subgroup A Co-Leader): @CLO - right.....no new ideas (in blue) have been accepted, but still merit discussion


LIne 51, Business Constituency -- New Idea: Eligibility requirements should be stricter and allow for validation that the application does adhere to the requirements of that specific category. .


Line 52, INTA -- New Idea (see spreadsheet for detail).  Saying that if we do allow brands during contention resolution or objections to change strings and if we think it's acceptable then then should be allowed Spec 13 treatment.  (Right now Spec 13 only applies to exact matches.)


Line 53, RySG -- See 2.2.4.c.1 above.


Additional Comments:

Line 55, Christopher Wilkinson -- New Idea.


b. Time permitting - 2.2.5: Applications: Submission Limits:


2.2.5.c.1:

Lines 4-13 -- Agreement


Line 14, Christopher Wilkinson -- Divergence: The next round should ensure (a) that diverse entities had access to the application process and (b) that new applicants have the option of engaging an RSP that is independent of pre-existing Registries or Registrars. From this point of view, the WT should have considered a cap on new applications from individual entities. That would be a particularly sensitive issue in the case of geographical names..


Line 15, Public Interest Community: Divergence


-- Question re: relevance of technical limits (number of TLDs in the root) is a subject for Sub Group B.


ACTION ITEM: Ask Public Interest Community the origin of the number reference in the following quotation: "We recommend that ICANN allow no more than 2 dozen applications for each company, including its parent company, subsidiaries, and affiliates. "


  • No labels