ICANN ICANN Email List Archives

[gnso-review-dt]


<<< Chronological Index >>>    <<< Thread Index >>>

RE: [gnso-review-dt] Public Comments & Next Meeting

  • To: "'Jen Wolfe'" <jwolfe@xxxxxxxxxxxxxxx>, <gnso-review-dt@xxxxxxxxx>
  • Subject: RE: [gnso-review-dt] Public Comments & Next Meeting
  • From: "BRG" <philip@xxxxxxxxxxxxxxxxxxxxxx>
  • Date: Fri, 24 Jul 2015 15:56:00 +0200

Thanks Jen,
I will be unable to make a call on 30 July
Philip
 


  _____  

From: owner-gnso-review-dt@xxxxxxxxx [mailto:owner-gnso-review-dt@xxxxxxxxx]
On Behalf Of Jen Wolfe
Sent: 24 July 2015 14:39
To: gnso-review-dt@xxxxxxxxx
Subject: [gnso-review-dt] Public Comments & Next Meeting



Hello GNSO Review Working Team:

 

Thank you again for your continued time and commitment to this process.  As
you may have seen from our email thread, there have been some concerns
expressed about the 24 July (today) deadline to provide public comments.  I
am reaching out to let you know that the schedule can accommodate extending
the deadline for one additional week to 31 July so that any groups or
individual who wish to comment  have one more week to respond.  I appreciate
those groups who have completed their public comments and encourage everyone
to have your respective groups provide comments by next week's deadline,
which will be the final deadline in order for the finalized report to be
issued on 31 August. 

 

I have summarized the comments received to date below:

 

Comments to date:

.             Brand Registry Group has submitted a
<http://forum.icann.org/lists/comments-gnso-review-01jun15/msg00000.html>
comment on 16 July

.             Registry Stakeholder Group has submitted a
<http://forum.icann.org/lists/comments-gnso-review-01jun15/msg00001.html>
comment on 23 July

.             In progress are comments from ISPCP and ALAC - all expected to
be submitted by the current due date of 24 July.  There may be others, but
staff is not currently aware of this.

.             64 comments provided verbally during ICANN53 sessions - see
<http://forum.icann.org/lists/comments-gnso-review-01jun15/msg00002.html>
posted table 

 

Public Comment/Engagement:

This
<https://www.icann.org/public-comments/gnso-review-draft-2015-06-01-en>
Public Comment period opened on 1 June and has been extended once to 24 July
- total of 53 days.

.         During ICANN53, Westlake conducted a total of 8 briefings for the
community, in addition to a briefing included in the
<https://buenosaires53.icann.org/en/schedule/wed-aoc-org-reviews> public
session on Reviews.  

.         A total of 64 comments made during these presentations have been
catalogued and are being considered by Westlake - see the
<http://forum.icann.org/lists/comments-gnso-review-01jun15/msg00002.html>
posted table. 

 

As one additional point:  we were scheduled to have a call next Thursday to
discuss the comments and begin formulating our recommendation to the SIC on
which recommendations we think should move into implementation.  I would
like to suggest that we proceed with the call as scheduled to use the time
to touch base on comments and begin the conversation on implementation, but
certainly understand if it would be more advantageous to wait until all
public comments have been received.

 

I would appreciate your feedback so we can either send out a new Doodle poll
to reschedule or plan to proceed as scheduled.

 

Thanks again for your continued support of this process!  Have a great
weekend!

 

Jen

 

 

jennifer c. WOLFE, esq., apr, SSBB

Founder & President, wolfe domain, a digital brand strategy advisory firm

513.746.2800 x 1 or Cell 513.238.4348

IAM 300 - TOp 300 global ip strategists 2011-2014

What will you do with your Dot Brand?  :  <http://ow.ly/Ebl8P>
http://ow.ly/Ebl8P 

Subscribe to Our You Tube Channel on Brand gTLDs   <http://ow.ly/Eblgc>
http://ow.ly/Eblgc  

Jen Wolfe gTLD Click Z Column   <http://ow.ly/EbljP> http://ow.ly/EbljP  

Linked In Group:  gTLD Strategy for Brands  <http://ow.ly/EbloM>
http://ow.ly/EbloM 

 



<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy