[Gnso-newgtld-wg-wt2] Agenda for WT2 Call at 20:30 UTC 5 October 2017

[Jeff Neuman]

Are you joining the call today….that is on in 5 minutes?

Jeffrey J. Neuman
Senior Vice President |Valideus USA | Com Laude USA
1751 Pinnacle Drive, Suite 600
Mclean, VA 22102, United States
E: jeff.neuman at valideus.com<mailto:jeff.neuman at valideus.com> or jeff.neuman at comlaude.com<mailto:jeff.neuman at comlaude.com>
T: +1.703.635.7514
M: +1.202.549.5079
@Jintlaw

From: gnso-newgtld-wg-wt2-bounces at icann.org [mailto:gnso-newgtld-wg-wt2-bounces at icann.org] On Behalf Of Kathy Kleiman
Sent: Thursday, October 5, 2017 3:25 PM
To: gnso-newgtld-wg-wt2 at icann.org
Subject: Re: [Gnso-newgtld-wg-wt2] Agenda for WT2 Call at 20:30 UTC 5 October 2017


That one's simple, Dish DBS amended its application for .MOBILE dramatically in course of the Community Objection (responding to many but not all of the objections raised). The Panelist finding was that Dish's .MOBILE application was now "open and non-discriminatory" and hence, no longer a Closed Generic.

Best, Kathy

On 10/5/2017 2:46 PM, Rosette, Kristina via Gnso-newgtld-wg-wt2 wrote:
Thanks, Michael.  Can you or ICANN staff help me understand why the document didn’t include the findings of the unsuccessful community objection against .MOBILE?  That would be helpful to a more complete understanding.


From: gnso-newgtld-wg-wt2-bounces at icann.org<mailto:gnso-newgtld-wg-wt2-bounces at icann.org> [mailto:gnso-newgtld-wg-wt2-bounces at icann.org] On Behalf Of Michael Flemming
Sent: Thursday, October 05, 2017 7:32 AM
To: gnso-newgtld-wg-wt2 at icann.org<mailto:gnso-newgtld-wg-wt2 at icann.org>
Subject: Re: [Gnso-newgtld-wg-wt2] Agenda for WT2 Call at 20:30 UTC 5 October 2017

Dear All,

Staff has finished putting together a document that highlights findings of the panelists from objections of .MOBILE and .BOOK. While both of these have two different outcomes, they do share common themes of seeking whether or not a standing community qualifies to or not to file an objection against a proposed Closed Generic.

It is the hope that we will be able to review other objections as well to establish a path forward.

I look forward to discussing with all of you in roughly six hours.

Kind regards,

Michael Flemming

On Wed, Oct 4, 2017 at 10:31 PM, Michael Flemming <flemming at brightsconsulting.com<mailto:flemming at brightsconsulting.com>> wrote:
Dear All,

Please note the link to the Community Objection determinations I am referring to. If you have anymore questions, please note I am traveling today and will answer them as much as I can before the call.

https://iccwbo.org/dispute-resolution-services/icann-gtld-process/expert-determinations/

Regards,

Michael Flemming

El El mar, 3 oct 2017 a las 13:12, Michael Flemming <flemming at brightsconsulting.com<mailto:flemming at brightsconsulting.com>> escribió:
Dear All,

Please note that the agenda for this week's call is as below.


  1.  Welcome
  2.  SOI Updates
  3.  Closed Generic Discussion
  4.  AOB
Please note that this week will be a continuation of our discussion from last week on Closed Generics. In addition to the NGPC decision, there were several objections filed based against closed generics from the 2012 round. One of these, .mobile, was mentioned on the last couple of calls. Turns out there was more than one decision on this issue, but with opposite results. The assignment is to see if we can extract common themes in the findings to create a path forward that may allow certain closed generics to proceed while addressing the potential harms.

I look forward to discussing with everyone.

Kind regards,

Michael Flemming

--
Sent from my mobile.





_______________________________________________

Gnso-newgtld-wg-wt2 mailing list

Gnso-newgtld-wg-wt2 at icann.org<mailto:Gnso-newgtld-wg-wt2 at icann.org>

https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt2

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg-wt2/attachments/20171005/912dbf0f/attachment-0001.html>