Jeff;

Both scenarios still have to reconcile with string similarities for not-yet-delegated (yet not withdrawn) strings.

Imagine the .merck contention set was still undecided by the start of the next round. Irrelevant which of both suggested  "identical string policies" we adapt - how do we handle string similarity of 2nd round strings with not yet withdrawn 1st round strings (e.g. a 2nd round .merk application)? Obviously the 2nd round string similarity evaluation would have to include these not-yet-delegated (yet not withdrawn) strings. And then? 
A) Put the newly applied for string on hold? (Until the previous round applications are withdrawn - or delegated)
B) Allow them to join the previous round contention set? (Bonkers)
C) Let them become a new gTLD - which would require the withdrawal of the previous round "similar" (not yet withdrawn) strings? (Even more bonkers)

Obviously B) and C) would be highly unfair.

A policy needs to be in place. I say A)!

Thanks,

Alexander



Sent from my Samsung device


-------- Original message --------
From: Jeff Neuman <jeff.neuman@comlaude.com>
Date: 9/4/19 22:10 (GMT+02:00)
To: "Aikman-Scalese, Anne" <AAikman@lrrc.com>, Susan Payne <susan.payne@valideus.com>
Cc: gnso-newgtld-wg@icann.org
Subject: Re: [Gnso-newgtld-wg] Proposal on Prioritising Applications - prohibition on applying in a later round for a string from a prior round which has not yet been delegated

Anne,

 

During the call that Susan is referring to Susan volunteered to draft some language to flesh out her proposal.  And although it did not seem to have a huge amount of support on that call, she was asked to send the proposal around to the list to see if it has traction. 

 

As you have pointed out, decisions are not generally made with just one phone call.  Discussions can and should happen on the mailing list.  Susan has responded with her proposal on the list and we can see which version has support.  The options are:

 

  1. Prohibit Applications for strings where the applications are still pending (for whatever reason) – As per Susan’s proposal; or
  2. Allow applications in for those strings, but do not process them any further than the reveal stage, unless and/or until the applications from the previous round that match those strings have had their final disposition. 

 

Jeff Neuman

Senior Vice President 

Com Laude | Valideus

D: +1.703.635.7514

E: jeff.neuman@comlaude.com

 

From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org> On Behalf Of Aikman-Scalese, Anne
Sent: Tuesday, September 3, 2019 7:09 PM
To: Susan Payne <susan.payne@valideus.com>
Cc: gnso-newgtld-wg@icann.org
Subject: Re: [Gnso-newgtld-wg] Proposal on Prioritising Applications - prohibition on applying in a later round for a string from a prior round which has not yet been delegated

 

Susan – sorry for the confusion but based on Jeff’s request, I had understood you were “fleshing out” the part that the WG might be able to agree on – which was that prior round applications should be “completed” prior to subsequent round applications for the same string being considered.    I’m pretty sure the recording will confirm this.

Anne

 

From: Susan Payne <susan.payne@valideus.com>
Sent: Tuesday, September 3, 2019 4:06 PM
To: Aikman-Scalese, Anne <AAikman@lrrc.com>
Cc: gnso-newgtld-wg@icann.org
Subject: Re: Proposal on Prioritising Applications - prohibition on applying in a later round for a string from a prior round which has not yet been delegated

 

[EXTERNAL]


Anne, This is based on the comments that my company and INTA had made. I was asked on the call, including by you, to flesh this out so that the group could see what such a proposal would look like, and whether it would garner sufficient support. Here it is. 

 

Sent from my iPad


On 3 Sep 2019, at 17:57, Aikman-Scalese, Anne <