[At-Large] [CPWG] [registration-issues-wg] Planning for Round Two of New gTLDS is open?

[Alberto Soto]

n ICANN, the change in the multi-stakeholder model is being addressed. In Barcelona, at the ALAC meeting with the ICANN Board, I asked if this change would also imply a change in the bottom-up work methodology that is essential to establish our relationship with the end users and obtain the necessary feedbak for the generation of policies They answered that that would not change.

This type of measures, are showing that this methodology has already changed, that the opinion of several of the multiple stakeholders is no longer taken into account ..

 

Regards

 

Alberto

 

De: At-Large <at-large-bounces at atlarge-lists.icann.org> en nombre de Kaili Kan <kankaili at gmail.com>
Fecha: lunes, 1 de julio de 2019, 07:00
Para: "cw at christopherwilkinson.eu" <cw at christopherwilkinson.eu>
CC: "cpwg at icann.org" <cpwg at icann.org>, At-Large Worldwide <at-large at atlarge-lists.icann.org>
Asunto: Re: [At-Large] [CPWG] [registration-issues-wg] Planning for Round Two of New gTLDS is open?

 

Yes, this seems to be ignoring our opinions expressed.

 

However, as the gTLD market is already over-saturated, I believe the results of another round will work against those who are pushing for it.  Thus, after saying what should be said, we may just wait and see ...    ALAC will be be blamed anyway.

 

Also, if there is going to be another CCT-RT for that round, I would gladly volunteer for it.   : )

 

Kaili

 

 

On Mon, Jul 1, 2019 at 1:01 AM cw at christopherwilkinson.eu<cw at christopherwilkinson.eu> wrote:

Indeed:

 

1. The ICANN working paper ignores several key points that have been raised in the PDP, by ALAC, and in the meetings in ICANN65.

 

2.  The Circle ID article by the CEO of Cum Laude, presumably is an embarrassment to the PDP CoChairs.

 

CW




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/at-large/attachments/20190701/000f99f8/attachment.html>