[Gnso-newgtld-wg-wt3] WT3 - Agenda & Materials for Tuesday, 12 September @ 25:00 UTC - Discussion GAC Objections / Early Warnings / GAC Advice / String Similarity

[Robin Gross]

Dear All,
 
In preparation for our next call, Tuesday, 12 September 2017 @ 20:00 UTC, please see below for our proposed agenda.

Thanks, Robin
__________________________
 
1.Welcome & Review of Agenda
2. Updates to SOI
3. Plenary Update
4. CC2 — GAC Objections — Q 3.1.10 – 3.1.11 (see attached)
5. CC2 — String Similarity — Q 3.4.1 - 3.4.6 (see attached)
6. AOB

Discussion on GAC Early Warnings and GAC Advice in New GTLD program
3.1.10 - Do you feel that GAC Early Warnings were helpful in identifying potential concerns with applications? 

Do you have suggestions on how to mitigate concerns identified in GAC Early Warnings?


3.1.11 - What improvements and clarifications should be made to GAC Advice procedures? 

What mitigation mechanisms are needed to respond to GAC Advice? 

How can timelines be made more precise?


Discussion on String Similarity

3.4.1 - There was a perception that consistency and predictability of the string similarity evaluation needs to be improved. Do you have examples or evidence of issues? 
If so, do you have suggested changes to the policy recommendations or implementation that may lead to improvement? 
For instance, should the standard of string confusion that the evaluation panel used be updated or refined in any way?
 
3.4.2 - Should the approach for string similarity in gTLDs be harmonized with the way in which they are handled in ccTLDs (ccNSO IDN ccTLD Fast Track Process is described here: https://www.icann.org/resources/pages/fast-track-2012-02-25-en)?


3.4.3 - The WG and the wider community have raised concerns specifically related to singles and plurals of the same word. 
Do you have suggestions on how to develop guidance on singles and plurals that will lead to predictable outcomes? 
Would providing for more predictability of outcomes unfairly prejudice the rights of applicants or others?

3.4.4 - Do you believe that there should be some sort of mechanism to allow for a change of applied-for TLD when it is determined to be in contention with one or more other strings? 
If so, do you have suggestions on a workable mechanism?


3.4.5 - Do you feel that the contention resolution mechanisms from the 2012 round (i.e., CPE and last- resort auctions) met the needs of the community in a sufficient manner? Please explain.

3.4.6 – Do you believe that private auctions (i.e., NOT the auctions of last resort provided by ICANN) resulted in any harm? 
Could they lead to speculative applications seeking to participate in a private auction in future application processes? 
Should they be allowed or otherwise restricted in the future?



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg-wt3/attachments/20170908/83ea5887/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 3.1 Objections_Themes_29Aug17.pdf
Type: application/pdf
Size: 147469 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg-wt3/attachments/20170908/83ea5887/3.1Objections_Themes_29Aug17-0001.pdf>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg-wt3/attachments/20170908/83ea5887/attachment-0004.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CC2 - Work Track 3 - 3.4 String Similarity.pdf
Type: application/pdf
Size: 117445 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg-wt3/attachments/20170908/83ea5887/CC2-WorkTrack3-3.4StringSimilarity-0001.pdf>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg-wt3/attachments/20170908/83ea5887/attachment-0005.html>