- lac-discuss-es - lists.iana.org

Re: [lac-discuss-es] [lac-discuss-en] [CPWG] REMINDER / Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 08 July 2020 at 13:00 UTC
by roberto_gaetano＠hotmail.com July 9, 2020

July 9, 2020

[[-- Translated text (en -> es) --]] Comparto algunas de las consideraciones de Evan, aunque de una manera menos radical. En aquel entonces, mi posición era que una nueva ronda podría ser útil, pero solo para permitir que se deleguen IDN TLD. Mi razonamiento fue que el único factor que obstaculizaba la presencia en Internet eran las limitaciones técnicas para permitir diferentes scripts. El tiempo ha demostrado que tenía razón en parte, pero en parte estaba equivocado. Los nuevos TLD de IDN han fallado miserablemente, aunque se han eliminado las limitaciones técnicas, simplemente porque el problema no era técnico. Mientras tanto, algunos Geo-TLD han tenido éxito, y ya he admitido ante Dirk y Alexander que estaba equivocado en mi evaluación de que eran inútiles. Dicho esto, todavía dudo en invertir tiempo en discutir listas reservadas detalladas o condiciones especiales, pero eso podría estar más relacionado con la fatiga de los TLD en lugar de ser una evaluación objetiva de los costos y beneficios de las acciones que requieren una alta inversión de recursos. Sigo convencido de que los mayores problemas que los usuarios de Internet en general tienen con Internet no están relacionados con los nuevos TLD, y que dedicar la mayor parte de nuestros recursos a este tema no es una inversión inteligente, pero entiendo perfectamente que otras personas podrían pensar de manera diferente y, por lo tanto, tienen prioridades que difieren de las mías. El hecho de que somos una multitud muy diversificada es, de hecho, una de las fortalezas de At-Large, ya que tenemos personas con diferentes intereses y prioridades diferentes, podemos cubrir un espectro diversificado de temas. Salud, Roberto El 09.07.2020, a las 18:37, Evan Leibovitch <evan(a)telly.org<mailto:evan@telly.org> > escribió: Hola christopher Como dijo Tijani, creo que todos estaban atentos a lo que sucedió con .amazon cuando elaboraron este enfoque. Sin embargo, estoy de acuerdo con su punto de vista y, de hecho, creo que el caso de "comunidad" completamente falso para el dominio de dominio de dominio de .amazon en realidad refuerza su caso. Dicho esto, personalmente he desarrollado un caso severo de "TLD ennui". A QUIEN LE IMPORTA cómo se desarrolla todo (desde un punto de vista de interés público) hasta que llega el momento de buscar el abuso. La experiencia pasada ha demostrado que los TLD son una forma completamente miserable e ineficiente de unir a una comunidad, especialmente a la luz de todas las excelentes alternativas que existen. Uno podría argumentar fácilmente que Reddit solo puede servir a la construcción de la comunidad y la responsabilidad pública mejor que cualquier registro. Dado que desde el principio, los TLD son asuntos de pago por juego, deben contribuir, incluso los de la comunidad, a la desigualdad de acceso en una medida que no comparten otras plataformas. La experiencia de At-Large con los nuevos TLD, incluso los supuestamente nobles, indican que, sin excepción, están impulsados por una combinación de vanidad y avaricia. Estoy muy decepcionado de que ni ALAC ni nadie más en la burbuja de la ICANN, ni el GAC ni la sociedad civil de la GNSO, hayan intentado presentar un caso débil de interés público contra una nueva ronda. Cuando estaba más involucrado en ALAC, intenté reunir apoyo para el caso contra más delegaciones de TLD hasta que las consecuencias de la última ronda pudieran analizarse de manera adecuada (e independiente). El esfuerzo fracasó miserablemente y me llevó a alejarme. Todos tratan una nueva ronda como simplemente inevitable, ya sea que alguien fuera del cartel de dominio realmente lo quiera. Cada vez que escucho el término "subpro" tengo que sonreírme a mí mismo porque lo leo como una abreviatura de "menos que profesional", lo 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 la AG de California en .ORG debería haber sido una llamada de atención a este aislamiento, pero parece haberse desvanecido. Así que volvemos a lo de siempre ... hasta la próxima vez que intervenga el AG. Jonathan tenía razón en que la intervención del AG en .ORG fue un precedente peligroso, pero ... ¿peligroso para quién? Ahora sabemos que hay límites a la tolerancia mundial de la perversión de ICANN del multiactor. ¿Qué tan pronto hasta la próxima vez que se prueben estos límites? Evan Leibovitch, Toronto Canadá @evanleibovitch / @ el56 El jueves 9 de julio de 2020 a las 04:47, Tijani BEN JEMAA <tijani.benjemaa(a)topnet.tn<mailto:tijani.benjemaa@topnet.tn> > escribió: Hola alan Entonces, eso es todo: desea que solicitemos la adición de la naturaleza del nombre geográfico de la cadena solicitada como criterio para que el CPE decida si la aplicación es comunitaria o no. En mi opinión, es absolutamente irrelevante. Cualquier nombre geográfico puede ser solicitado por una entidad comercial, un gobierno o una comunidad. El hecho de que sea un nombre geográfico no debería dar más crédito al solicitante, incluso si se trata de una comunidad. Cualquier aplicación no es más comunitaria cuando se trata de la cadena de nombre geográfico. Tijani Alan Greenberg <alan.greenberg(a)mcgill.ca<mailto:alan.greenberg@mcgill.ca> > un écrit: Muchos TLD de geoname delegados en la última ronda eran, de hecho, solicitudes de la comunidad (aunque no sé si alguno pasó por el CPE, ya que eso solo ocurre si se disputan. La pregunta aquí es si SI está solicitando un geoname, y SI está solicitando como TLD comunitario, entonces debería obtener puntos adicionales bajo el CPE porque es un geoname (es decir, mejora sus posibilidades de satisfacer el CPE y ganando así sobre algún otro solicitante. No estoy seguro de que tengamos un argumento sólido para que esto sea aprobado, ni estoy seguro de que valga la pena intentarlo, pero lo veo como algo bueno si pudiéramos. Alan En 2020-07-08 11:50 AM, Tijani BEN JEMAA escribió: Querido Jonathan y todos, Después de nuestra discusión de hoy durante la llamada del CPWG sobre los nombres geográficos, me gustaría explicar por qué no creo que los nombres geográficos se incorporen a la evaluación del CPWG. De hecho, el rol del CPE es evaluar si la aplicación es una aplicación comunitaria o no (esto es lo que Alan explicó y lo que acordé). Entonces, ¿cómo podría incorporarse? como criterio para decidir si la aplicación es una aplicación comunitaria? ¿Solicitamos que si la aplicación es para una cadena de nombre geográfico, el CPE debería considerarla como una aplicación comunitaria? El CPE evalúa si el solicitante representa a una comunidad y si la solicitud sirve a esa comunidad, independientemente de la cadena solicitada (nombre geográfico, nombre del idioma, nombre de la cultura, etc.). Tijani Le 8 juil. 2020 Ã 07:34, personal de la ICANN At-Large <staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> > un crítico: *** Si necesita un marcado o necesita una disculpa, comuníquese con el personal de At-Large en staff(a)atlarge.icann.org <mailto:staff@atlarge.icann.org> con tu número preferido *** Queridos todos, La próxima convocatoria del Grupo de trabajo de políticas consolidadas de At-Large (CPWG) está programada para el miércoles 08 de julio de 2020 a las 13:00 UTC durante 90 minutos. Para otras ocasiones: https://tinyurl.com/y9ghlcz3 La agenda y los detalles de la llamada se pueden encontrar en: https://community.icann.org/x/XYRIC Zoom Room: https://icann.zoom.us/j/97147867051?pwd=NWswK1duaUtHclBxaksyRC8wekxCQT09 / Código de acceso: 2345cpwg ** Transcripción en tiempo real (RTT) disponible en (sujeto a disponibilidad): https://www.streamtext.net/player?event=ICANN [streamtext.net] [streamtext.net] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.streamtext.net_pla…> Puente de conferencia ADIGO: EN: 1638 ES: 1738 FR: 1838 Número de acceso gratuito (EE. UU. Y Canadá): 800550 6865 Otros números gratuitos: https://www.adigo.com/icann [adigo.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.adigo.com_icann&d=…> Espacio Wiki del Grupo de Trabajo de Política Consolidada At-Large (CPWG): https://community.icann.org/x/jYDpB Si necesita un marcado, comuníquese con el personal de At-Large en: staff(a)atlarge.icann.org <mailto:staff@atlarge.icann.org> Gracias. Saludos cordiales, Personal de At-Large El personal de políticas de ICANN en apoyo de la comunidad At-Large Sitio web: atlarge.icann.org [atlarge.icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge.icann.org_&d=D…> Facebook: facebook.com/icann [facebook.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> atlarge [facebook.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> Twitter: @ [twitter.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…> ICANNAtLarge [twitter.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…> <At-Large Consolidated Policy Working Group (CPWG) Call[28].ics> _______________________________________________ Lista de correo de CPWG CPWG(a)icann.org <mailto: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(a)icann.org<mailto: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(a)icann.org<mailto: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. _______________________________________________ CPWG mailing list CPWG(a)icann.org<mailto: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.

1 0

ICANN68 LAC Readout session
by Rodrigo Saucedo July 9, 2020

July 9, 2020

Dear members of LACRALO, You are all invited to attend the ICANN68 LAC Readout Session, If you weren’t able to participate in our virtual Policy Forum, we provide you with another opportunity to learn more on the main topics discussed during the meeting. When: Friday 10 May at 15:00 UTC (Interpretation available in English, Spanish and Portuguese). Register in advance for this webinar: https://icann.zoom.us/webinar/register/WN_H5sPRJrQS9-J6F7HcpXGsw Best, -------------------------- Rodrigo Saucedo rodrigo.saucedo(a)icann.org<mailto:rodrigo.saucedo@icann.org> Sr. Manager Strategic Initiatives, Latin America and the Caribbean ICANN One World, One Internet [id:image001.png@01D356F4.3F3911B0]

1 0

Re: [lac-discuss-es] [lac-discuss-en] [CPWG] REMINDER / Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 08 July 2020 at 13:00 UTC
by justine.chew＠gmail.com July 9, 2020

July 9, 2020

[[-- Translated text (en -> es) --]] Como se mencionó en el chat durante la llamada, sugiero que el CPWG SubPro Small El equipo se pone en contacto con Jonathan para considerar cómo y dónde podría ser esa información insertado en la presentación sobre Geonames - Informe final WT5 para discusión la próxima semana, sin convertir el CPE al revés. Saludos cordiales, Justine --- El miércoles 8 de julio de 2020 a las 23:51, Tijani BEN JEMAA <tijani.benjemaa(a)topnet.tn> escribió: > 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(a)atlarge.icann.org> a > écrit : > > ****If you require a dial out or need to state an apology, please contact > At-Large staff at **staff(a)atlarge.icann.org* <staff(a)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_pla…> > > 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=…> > > 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(a)atlarge.icann.org* <staff(a)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=D…> > Facebook: facebook.com/icann [facebook.com] > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…>atlarge > [facebook.com] > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> > Twitter: @ [twitter.com] > <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…>ICANNAtLarge > [twitter.com] > <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…> > > <At-Large Consolidated Policy Working Group (CPWG) Call[28].ics> > _______________________________________________ > CPWG mailing list > CPWG(a)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(a)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.

1 0

[lac-discuss-en] Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 15 July 2020 at 19:00 UTC
by staff＠atlarge.icann.org July 9, 2020

July 9, 2020

[[-- Translated text (en -> es) --]] *** Si necesita un marcado o necesita una disculpa, comuníquese con el personal de At-Large en staff(a)atlarge.icann.org <mailto:staff@atlarge.icann.org> con tu número preferido *** Queridos todos, La próxima convocatoria del Grupo de trabajo de políticas consolidadas de At-Large (CPWG) está programada para el miércoles 15 de julio de 2020 a las 19:00 UTC durante 90 minutos. Para otras ocasiones: https://tinyurl.com/ychc8hux La agenda (para actualizar) y los detalles de la llamada se pueden encontrar en: https://community.icann.org/x/FAVcC Zoom Room: https://icann.zoom.us/j/97147867051?pwd=NWswK1duaUtHclBxaksyRC8wekxCQT09 [icann.zoom.us] <https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.zoom.us_j_971478…> / Código de acceso: 2345cpwg ** Transcripción en tiempo real (RTT) disponible en (sujeto a disponibilidad): https://www.streamtext.net/player?event=ICANN [streamtext.net] [streamtext.net] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.streamtext.net_pla…> Puente de conferencia ADIGO: EN: 1638 ES: 1738 FR: 1838 Número de acceso gratuito (EE. UU. Y Canadá): 800550 6865 Otros números gratuitos: https://www.adigo.com/icann [adigo.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.adigo.com_icann&d=…> Espacio Wiki del Grupo de Trabajo de Política Consolidada At-Large (CPWG): https://community.icann.org/x/jYDpB Si necesita un marcado, comuníquese con el personal de At-Large en: staff(a)atlarge.icann.org <mailto:staff@atlarge.icann.org> Gracias. Saludos cordiales, Personal de At-Large El personal de políticas de ICANN en apoyo de la comunidad At-Large Sitio web: atlarge.icann.org [atlarge.icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge.icann.org_&d=D…> Facebook: facebook.com/icann [facebook.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> atlarge [facebook.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> Twitter: @ [twitter.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…> ICANNAtLarge [twitter.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…>

1 0

[lac-discuss-en] At-Large Consolidated Policy Working Group (CPWG) Call
by PolicyCalendar＠icann.org July 9, 2020

July 9, 2020

[[-- Translated text (en -> es) --]] *** Si necesita un marcado o necesita una disculpa, comuníquese con el personal de At-Large en staff(a)atlarge.icann.org <mailto:staff@atlarge.icann.org> con tu número preferido *** Queridos todos, La próxima convocatoria del Grupo de trabajo de políticas consolidadas de At-Large (CPWG) está programada para el miércoles 15 de julio de 2020 a las 19:00 UTC durante 90 minutos. Para otras ocasiones: https://tinyurl.com/ychc8hux La agenda (para actualizar) y los detalles de la llamada se pueden encontrar en: https://community.icann.org/x/FAVcC Zoom Room: https://icann.zoom.us/j/97147867051?pwd=NWswK1duaUtHclBxaksyRC8wekxCQT09 [icann.zoom.us] <https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.zoom.us_j_971478…> / Código de acceso: 2345cpwg ** Transcripción en tiempo real (RTT) disponible en (sujeto a disponibilidad): https://www.streamtext.net/player?event=ICANN [streamtext.net] [streamtext.net] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.streamtext.net_pla…> Puente de conferencia ADIGO: EN: 1638 ES: 1738 FR: 1838 Número de acceso gratuito (EE. UU. Y Canadá): 800550 6865 Otros números gratuitos: https://www.adigo.com/icann [adigo.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.adigo.com_icann&d=…> Espacio Wiki del Grupo de Trabajo de Política Consolidada At-Large (CPWG): https://community.icann.org/x/jYDpB Si necesita un marcado, comuníquese con el personal de At-Large en: staff(a)atlarge.icann.org <mailto:staff@atlarge.icann.org> Gracias. Saludos cordiales, Personal de At-Large El personal de políticas de ICANN en apoyo de la comunidad At-Large Sitio web: atlarge.icann.org [atlarge.icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge.icann.org_&d=D…> Facebook: facebook.com/icann [facebook.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> atlarge [facebook.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> Twitter: @ [twitter.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…> ICANNAtLarge [twitter.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…>

1 0

ICANN LAC Talks
by Rodrigo Saucedo July 9, 2020

July 9, 2020

Hola a todos, No se olviden que en menos de 5 minutos empieza el ICANN LAC Talks. Para unirse: https://icann.zoom.us/w/96057179099 Contraseña: 2G*yu^6sVM Saludos, -------------------------- Rodrigo Saucedo rodrigo.saucedo(a)icann.org<mailto:rodrigo.saucedo@icann.org> Sr. Manager Strategic Initiatives, Latin America and the Caribbean ICANN One World, One Internet [id:image001.png@01D356F4.3F3911B0]

1 0

Re: [lac-discuss-es] [lac-discuss-en] [CPWG] REMINDER / Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 08 July 2020 at 13:00 UTC
by evan＠telly.org July 9, 2020

July 9, 2020

[[-- 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(a)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(a)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(a)atlarge.icann.org > > a Ã©crit : > > ****If you require a dial out or need to state an apology, please contact > At-Large staff at staff(a)atlarge.icann.org <staff(a)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_pla…> > > 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=…> > > 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(a)atlarge.icann.org* <staff(a)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=D…> > Facebook: facebook.com/icann [facebook.com] > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> atlarge > [facebook.com] > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> > Twitter: @ [twitter.com] > <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…> ICANNAtLarge > [twitter.com] > <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…> > > <At-Large Consolidated Policy Working Group (CPWG) > Call[28].ics>_______________________________________________ > CPWG mailing list > CPWG(a)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(a)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(a)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.

1 0

Re: [lac-discuss-es] [lac-discuss-en] [CPWG] REMINDER / Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 08 July 2020 at 13:00 UTC
by tijani.benjemaa＠topnet.tn July 9, 2020

July 9, 2020

[[-- Translated text (en -> es) --]] Cher Christopher, Merci pour ta réponse. Je comprende ton point de vue, mais es-tu sûr que nous allons vers une plus big protection? Ou au moins est-ce que At-Large va dans ce sens là? Tu como vu le résultat du survey hier au CPWG? (Moins de protection et communauté). En tout cas, moi je regarde ce qui c'est passé jusque là: Le cas le plus flagrant est dot Amazone. De toute façon, le fait qu'un string es un nombre geográfico ne peut pas favoriser ou desfavoriser une Community application à mon avis. Ca ne peut pas être un critère pour le CPE pour décider si una aplicación es comunautaire ou pas. Bonne soirée. > Le 9 juil. 2020 à 13:56, mail(a)christopherwilkinson.eu CW <mail(a)christopherwilkinson.eu> a écrit : > > Cher Tijani : Je ne peux pas être d'accord avec toi sur ce point. > > Nous n'avons plus d'affaire avec « …a commercial entity, a government or a community » > > Désormais il s'agit de protéger - d'une manière ou d'un autre – les véritables demandes provenant des pays et des communités locales contre les entités hybrides Registry/Registrar qui : > > - bénéficient des règles actuelles d'intégration verticale > > - ont les projets de constituer des portefeuilles spéculatives de TLD géographiques > > - qui peuvent faire appel à des resources financiers tiers, notamment lorsqu'il s'agit des sûr en chères, et > > - qui exploitent les règles trop souples du WT5 en matière de l'utilisation géographique des gTLD. > > Tout cela sera discuté en profondeur bientôt par le CPWG. > > Entre temps, « cave emptor » > > Bien à toi > > Christopher > >> El 9 de julio de 2020 a las 10:46 Tijani BEN JEMAA <tijani.benjemaa(a)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(a)mcgill.ca <mailto: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(a)atlarge.icann.org <mailto: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(a)atlarge.icann.org <mailto: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 <https://tinyurl.com/y9ghlcz3> >>>>> >>>>> The agenda and call details can be found at: https://community.icann.org/x/XYRIC <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_pla…> >>>>> >>>>> 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=…> >>>>> >>>>> 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(a)atlarge.icann.org <mailto: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=D…> >>>>> Facebook: facebook.com/icann [facebook.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> atlarge [facebook.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> >>>>> Twitter: @ [twitter.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…> ICANNAtLarge [twitter.com] <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…> >>>>> >>>>> <At-Large Consolidated Policy Working Group (CPWG) Call[28].ics>_______________________________________________ >>>>> CPWG mailing list >>>>> CPWG(a)icann.org <mailto:CPWG@icann.org> >>>>> https://mm.icann.org/mailman/listinfo/cpwg <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 <https://www.icann.org/privacy/policy>) and the website Terms of Service ( https://www.icann.org/privacy/tos <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(a)icann.org >>>> https://mm.icann.org/mailman/listinfo/cpwg <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 <https://www.icann.org/privacy/policy>) and the website Terms of Service ( https://www.icann.org/privacy/tos <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(a)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

1 0

Re: [lac-discuss-es] [lac-discuss-en] [CPWG] REMINDER / Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 08 July 2020 at 13:00 UTC
by mail＠christopherwilkinson.eu July 9, 2020

July 9, 2020

[[-- Translated text (en -> es) --]] Cher Tijani: Je ne peux pas être d'accord avec toi sur ce point. Nous n'avons plus d'affaire avec «... una entidad comercial, un gobierno o una comunidad» Désormais il s'agit de protéger - d'un manière ou d'un autre - les véritables exige proveniente de los pagos y de las comunidades locales con los derechos híbridos Registro / Registrador qui: - bénéficient des règles actuelles d'intégration verticale - ont les projets de constituer des portefeuilles spéculatives de TLD géographiques - qui peuvent faire appel à des resources financrs tiers, notamment lorsqu'il s'agit des sûr en chères, et - Qui explitent les règles trop souples du WT5 en matière de l'utilisation géographique des gTLD. Tout cela sera discuté in profondeur bientôt par le CPWG. Entre temps, «cueva emptor» Bien à toi Christopher > El 9 de julio de 2020 a las 10:46 Tijani BEN JEMAA <tijani.benjemaa(a)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(a)mcgill.ca mailto: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(a)atlarge.icann.org mailto: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(a)atlarge.icann.org mailto: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 / 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_pla… > > > > > > > > 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=… > > > > > > > > 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(a)atlarge.icann.org mailto: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=D… > > > > Facebook: facebook.com/icann [facebook.com] https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann… atlarge [facebook.com] https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann… > > > > Twitter: @ [twitter.com] https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar… ICANNAtLarge [twitter.com] https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar… > > > > > > > > <At-Large Consolidated Policy Working Group (CPWG) Call[28].ics>_______________________________________________ > > > > CPWG mailing list > > > > CPWG(a)icann.org mailto: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(a)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(a)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. >

1 0

Re: [lac-discuss-es] [lac-discuss-en] [CPWG] REMINDER / Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 08 July 2020 at 13:00 UTC
by tijani.benjemaa＠topnet.tn July 9, 2020

July 9, 2020

[[-- Translated text (en -> es) --]] Hola alan Entonces, eso es todo: desea que le pidamos que agreguemos la naturaleza del nombre geográfico de la cadena solicitada como criterio para que el CPE decida si la aplicación es comunitaria o no. En mi opinión, es absolutamente irrelevante. Cualquier nombre geográfico podría aplicarse por una entidad comercial, un gobierno o una comunidad. El hecho de que es un nombre geográfico que no debería dar más crédito al solicitante, incluso si es un comunidad. Cualquier aplicación no es más comunitaria cuando es para el cadena de nombre geográfico. Tijani Alan Greenberg <alan.greenberg(a)mcgill.ca> un escrito: > 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 nombres geográficos >> 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(a)atlarge.icann.org > a Ã©crit : >>> >>> /***IF YOU REQUIRE A DIAL OUT OR NEED TO STATE AN APOLOGY, PLEASE >>> CONTACT AT-LARGE STAFF AT STAFF(a)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[1] >>> >>> ZOOM ROOM: >>> HTTPS://ICANN.ZOOM.US/J/97147867051?PWD=NWSWK1DUAUTHCLBXAKSYRC8WEKXCQT09[2] / CÓDIGO DE PASO: >>> 2345CPWG** >>> >>> >>> REAL TIME TRANSCRIPTION (RTT) AVAILABLE AT /(SUBJECT TO >>> AVAILABILITY)/: https://www.streamtext.net/player?event=ICANN >>> [streamtext.net] [streamtext.net][3] >>> >>> 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][4] >>> >>> At-Large Consolidated Policy Working Group (CPWG) Wiki Space: >>> HTTPS://COMMUNITY.ICANN.ORG/X/JYDPB[5] >>> >>> If you require a dial-out please contact At-Large staff at: >>> STAFF(a)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][6] >>> Facebook: facebook.com/icann [facebook.com][7] atlarge >>> [facebook.com][7] >>> Twitter: @ [twitter.com][8] ICANNAtLarge [twitter.com][8] >>> >>> <At-Large Consolidated Policy Working Group (CPWG) >>> Call[28].ics>_______________________________________________ >>> CPWG mailing list >>> CPWG(a)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[9]) and the website Terms of >>> Service ( https://www.icann.org/privacy/tos[10]) 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(a)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[9]) and the website Terms of >> Service ( https://www.icann.org/privacy/tos[10]) 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. Gravámenes: ------ [1] https://community.icann.org/x/XYRIC [2] https://icann.zoom.us/j/97147867051?pwd=NWswK1duaUtHclBxaksyRC8wekxCQT09 [3] https://urldefense.proofpoint.com/v2/url?u=https-3A__www.streamtext.net_pla… [4] https://urldefense.proofpoint.com/v2/url?u=https-3A__www.adigo.com_icann&d=… [5] https://community.icann.org/x/jYDpB [6] https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge.icann.org_&d=D… [7] https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann… [8] https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar… [9] https://www.icann.org/privacy/policy [10] https://www.icann.org/privacy/tos - Tijani BENJEMAA Director ejecutivo Federación Mediterránea de Asociaciones de Internet (FMAI) Teléfono: +216 52385114

1 0