[[-- Translated text (en -> es) --]] Hola christopher Como dijo Tijani, creo que todos estaban atentos a lo que sucedió con .amazon al elaborar este enfoque. Sin embargo, estoy de acuerdo con tu punto de vista y en hecho cree que el caso de "comunidad" completamente falso para el TLD .amazon En realidad refuerza su caso. Dicho esto, personalmente he desarrollado un caso severo de "TLD ennui". A quién le importa cómo se despliega todo (desde un punto de vista de interés público) hasta que llegue hora de cazar abusos. La experiencia pasada ha demostrado que los TLD son completamente miserables y forma ineficiente de reunir a una comunidad, especialmente a la luz de todo Las grandes alternativas que existen. Uno podría hacer fácilmente el caso de que Solo Reddit puede servir mejor a la construcción de la comunidad y la responsabilidad pública que cualquier registro Desde el principio, los TLD son asuntos de pago por juego que debe, incluso los de la comunidad, contribuir a la desigualdad de acceso a un extensión no compartida por otras plataformas. La experiencia de At-Large con nuevos TLD, incluso los supuestamente nobles, indican que son, sin excepción, impulsados por alguna combinación de vanidad y avaricia. Estoy muy decepcionado de que ni ALAC ni nadie más en la burbuja de ICANN - ni el GAC ni la grupa de la sociedad civil de la GNSO - trató de hacer incluso un caso débil de interés público contra una nueva ronda. Cuando yo era más profundamente involucrado en ALAC Traté de reunir apoyo para el caso contra más delegaciones de TLD hasta que las consecuencias de la última ronda puedan ser correctamente (e independientemente) analizado. El esfuerzo fracasó miserablemente y condujo a mi alejándose. Todos tratan una nueva ronda como simplemente inevitable, si alguien fuera del cartel de dominio realmente lo quiere. Cada vez que yo escucho el término "subpro" tengo que sonreírme a mí mismo porque lo leí como un abreviatura de "menos que profesional", que de hecho creo que es el caso para ese grupo cuando se trata de considerar el interés público. La inevitable marcha hacia nuevas rondas, ya sean necesarias o no, ofrece Un claro recordatorio del aislamiento total de la burbuja de ICANN (incluido ALAC) del mundo exterior La intervención de California AG en .ORG debería haber sido una llamada de atención a este aislamiento, pero parece tener volcado Así que vuelve a la normalidad ... hasta la próxima vez que AG interviene. Jonathan tenía razón en que la intervención de AG en .ORG fue un precedente peligroso, pero ... ¿peligroso para quién? Ahora sabemos que hay límites para la tolerancia mundial de ICANN perversión del multiactor. ¿Qué tan pronto hasta la próxima vez que estos los límites son probados? Evan Leibovitch, Toronto Canadá @evanleibovitch / @ el56 El jueves 9 de julio de 2020 a las 04:47, Tijani BEN JEMAA <tijani.benjemaa@topnet.tn> escribió:

Hi Alan,

So, that's it: you want us to ask the addition of the geo-name nature of the string applied for as a criterion for the CPE to decide whether the application is Community one or not.

In my opinion, it's absolutely irrelevent. Any geo-name could be applied for by a commercial entity, a government or a community. The fact that it is a geo-name shouldn't give more credit to the applicat even if it is a community. Any application is not more community one when it is for the geo-name string.

Tijani

Alan Greenberg <alan.greenberg@mcgill.ca> a écrit :

Many geoname TLDs delegated in the last round were in fact community applications (although I don't know if any went through the CPE since that only happens if they are contested.

The question here is that IF you are applying for a geoname, and IF you are applying as a community TLD, then should you get extra points under the CPE because it is a geoname (that is, it improves your chances of satisfying the CPE and thus winning over some other applicant.

I am not sure we have a strong case for getting this approved, nor am I sure it is even worth the effort to try, but I see it as a good thing if we could.

Alan

At 2020-07-08 11:50 AM, Tijani BEN JEMAA wrote:

Dear Jonathan and all,

Following up on our discussion today during the CPWG call about the geo-names, I would like to explain why I don’t think that geo-names should be incorporated into the CPWG evaluation. In fact, the CPE role is to evaluate whether the application is a community application or not (this is what Alan explained and what I agreed on). So how it might be incorporated? as a criterion to decide if the application is a community application? Shall we request that if the application is for a geo-name string, the CPE should consider it as a community application? The CPE evaluates if the applicant represents a community and if the application serves that community whatever the string applied for is (geo-name, language name, culture name, etc.).

Tijani

Le 8 juil. 2020 à 07:34, ICANN At-Large Staff <staff@atlarge.icann.org > a écrit :

****If you require a dial out or need to state an apology, please contact At-Large staff at staff@atlarge.icann.org <staff@atlarge.icann.org> with your preferred number****

Dear All,

The next *At-Large* *Consolidated Policy Working Group (CPWG) Call* is scheduled for *Wednesday, 08 July 2020 at 13:00 UTC for 90 mins.*

For other times: https://tinyurl.com/y9ghlcz3

The agenda and call details can be found at: https://community.icann.org/x/XYRIC

*Zoom Room: https://icann.zoom.us/j/97147867051?pwd=NWswK1duaUtHclBxaksyRC8wekxCQT09 <https://icann.zoom.us/j/97147867051?pwd=NWswK1duaUtHclBxaksyRC8wekxCQT09> / Passcode: 2345cpwg** *

*Real time transcription (RTT) available at (subject to availability):* https://www.streamtext.net/player?event=ICANN [streamtext.net] [streamtext.net] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.streamtext.net_play...>

ADIGO Conference Bridge: EN: 1638 ES: 1738 FR: 1838

Toll-free access number (US and Canada): 800 550 6865

Other toll-free numbers: *https://www.adigo.com/icann [adigo.com]* <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.adigo.com_icann&d=D...>

At-Large Consolidated Policy Working Group (CPWG) Wiki Space: *https://community.icann.org/x/jYDpB* <https://community.icann.org/x/jYDpB>

If you require a dial-out please contact At-Large staff at: *staff@atlarge.icann.org* <staff@atlarge.icann.org>

Thank you. Kind regards,

At-Large Staff

ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org [atlarge.icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge.icann.org_&d=Dw...> Facebook: facebook.com/icann [facebook.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icanna...> atlarge [facebook.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icanna...> Twitter: @ [twitter.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLarg...> ICANNAtLarge [twitter.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLarg...>

<At-Large Consolidated Policy Working Group (CPWG) Call[28].ics>_______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg

_______________________________________________ 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.

Tijani BEN JEMAA

_______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg

_______________________________________________ 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.

------------------------------------------------------------------------------ *Tijani BENJEMAA* Executive Director Mediterranean Federation of Internet Associations (*FMAI*) Telephone: +216 52 385 114

------------------------------------------------------------------------------

_______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg

_______________________________________________ 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.