Agree Rubens. Applicants  under prioritized group could have a  question to mark yes or no agreeing to be put under this prioritization. It will be simpler than debate one by one after during the process.

 

Vanda Scartezini

Polo Consultores Associados

Av. Paulista 1159, cj 1004

01311-200- Sao Paulo, SP, Brazil

Land Line: +55 11 3266.6253

Mobile: + 55 11 98181.1464 

Sorry for any typos. 

 

 

 

 

 

From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org> on behalf of Rubens Kuhl <rubensk@nic.br>
Date: Monday, April 13, 2020 at 13:07
To: Jeff Neuman <jeff.neuman@comlaude.com>
Cc: Gnso-newgtld-wg <gnso-newgtld-wg@icann.org>
Subject: Re: [Gnso-newgtld-wg] Prioritization of IDNs proposal (Proportional Prioritization)

 

 

What if the IDN applicant prefers not being a first mover ? That was the case of brands in 2012, for instance. 

 

While I'm happy providing priority if the IDN applicant wants it, although evaluation priority address just one of the many issues faced by IDNs, I don't think we should prioritise applications that want exactly the opposite. 

 

 

Rubens

 



On 13 Apr 2020, at 12:55, Jeff Neuman <jeff.neuman@comlaude.com> wrote:

 

All,

 

In an effort to offer a compromise between those that favor the prioritization of all IDN applications and those that do not favor the prioritization, I wanted to see if I could provide a compromise solution.

 

Background

The prioritization of IDN applications was a decision made by ICANN org well after all applications were submitted in 2012 and made a lot of sense to the community for the following reasons.  (1) There were only approximate 115 IDN applications out of 1930 (about 6% of the applications); (2) it was the first round to ever accept applications for new IDN gTLDs, (3) part of the rationale for the first expansion was for innovation and expansion of the name space to the global community and (4) it was a good thing to do for the increased globalization of the Internet.

 

Those in favor of prioritization of IDNs still believe that despite not being the first round, reasons (3) and (4) are still worthy of pursuing.  Many who are not in favor of prioritization are afraid that the next round could see thousands of new applications including thousands of IDNs.  To prioritize all IDNs up front could take months or even years (in theory) before a new non-IDN could be processed.

 

Proposal – Proportional Prioritization

What is we stated that the first 10% of each batch of applications must consist of IDN applications until there are no more IDN applications.  Therefore, if ICANN wants to create batches of 500 applications, the first 50 of each application batch processed must be IDNs.  The remaining 450 would be random (of both IDN and Non-IDN applications).

 

Example

In a batch of 500, priority #1-50 must be IDNs; 51-500 can be either IDN or non-IDN applications.  In other words if a particular IDN application is not chosen in #1-50, it would have a equal chance of being selected in 51-500.

 

In the next batch of 500 (Applications #501-1000), #501 - #550 must be IDN (if there are any left), and #551-1000 can be either IDN or non-IDN

 

In the next batch of 500 (Applications #1001 – 1500), #1001 - #1050 must be IDN (if any are left), and #1051 -1500 can be either IDN or non-IDN…..etc

 

Thus in a round with more than 1500 application, there would be a guarantee of evaluating at least 150 IDN applications PLUS any IDN applications showing up in the randomized drawings for the remaining 1,350 spots.

 

I hope this works as a reasonable compromise.  

  

 

Jeff Neuman

Senior Vice President 

 

Com Laude | Valideus
1751 Pinnacle Drive

Suite 600, McLean

VA 22102, USA


M: +1.202.549.5079

D: +1.703.635.7514


<image003.jpg>

 


The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that the Com Laude Group does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 06181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176, having its registered office at 33 Melville Street, Edinburgh, Lothian, EH3 7JF Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, headquartered at 1751 Pinnacle Drive, Suite 600, McLean, VA 22102, USA; Com Laude (Japan) Corporation, a company registered in Japan having its registered office at Suite 319,1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan. For further information see www.comlaude.com_______________________________________________
Gnso-newgtld-wg mailing list
Gnso-newgtld-wg@icann.org
https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (
https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.