[[--Translated text (es -> en)--]] Subject: Re:???? = Iso-8859-1 3A_solicitud_de_comentarios q = FW = 3A = q = iso-8859-1 _Declaraci = F3n_del_ALAC_sobre_la_introducci = F3n_de_dos_car = q = iso-8859-1 acteres_de_nombres_de_dominio_en_el_Nuevo_gTLD_Espacio_de_?? = = iso-8859-1? q? names? = From: apisan@unam.mx Alberto, the declaracinbsicamente says nothing. And ALAC are already Voting. This issue has been on the table long. In LACRALO who might have more interest are those involved in international territories in dispute and are not expressed. That suggests the conclusion that we really have a collective opinin formed and must vote in abstention. Of course there are also aware that they do not bring any later serposible complaint and we will be dedicating the existing situation for the use of country codes under new gTLDs: some protections for names is n today's list of ISO 3166-MA and future ningn space on the second level for the territories that are created or recognized, or cambin name (in the last decade or two in Latin America at least three continental countries have changed names, or this ssucede). Best regards. Alejandro Pisanty - - - - - - - - - - - - - - - - - - - - - - - - - - - Dr. Alejandro Pisanty School of Chemistry UNAM 3000 University Av,. 04510 Mexico DF Mexico + 52-1-5541444475 FROM ABROAD SMS +525541444475 +525541444475 FROM MEXICO Blog: http://pisanty.blogspot.com LinkedIn: http://www.linkedin.com/in/pisanty Join the group on LinkedIn UNAM, http://www.linkedin.com/e/gis/22285/4A106C0C8614 Twitter: http://twitter.com/apisanty ---- >> Join ISOC Mexico, http://www.isoc.org . . . . . . . . . . . . . . . . ________________________________________ From: lac-discuss-es-bounces@atlarge-lists.icann.org [lac-discuss-es-bounces@atlarge-lists.icann.org] on behalf of Alberto Soto [asoto@ibero-americano.org] Posted on: Monday, 11 August 2014 14:43 To: lac-discuss-es@atlarge-lists.icann.org Subject: Re: [lac-discuss-es] FW: Request for comments: ALAC Declaration on the introduction of two-character domain names in the new gTLD namespace Thanks to the quick response Dev. Dear, if you follow the thread that gives Dev, there vern reviews found on this topic. Already have intervened Ftima and Ada, as podrn see. I welcome your comments Best Regards Alberto Soto ----- Original Message ----- From: lac-discuss-es-bounces@atlarge-lists.icann.org [Mailto: lac-discuss-es-bounces@atlarge-lists.icann.org] On Behalf Of devtee@gmail.com Posted on: Monday, August 11, 2014 3:04 pm To: lac-discuss-es@atlarge-lists.icann.org Subject: Re: FW: Request for comments: ALAC Declaration on introduction of two-character domain names in the new gTLD Namespace [[Translated text (en -> s) -]] Subject: Re: FW: Request for comments: ALAC Declaration on introduction of two-character domain names in the new gTLD Namespace From: devtee@gmail.com Dear Alberto, My attempt at a declaration ( https://community.icann.org/x/VqzhAg) two points: - Issues of safety and stability Absent any DNS related, and given the use of 2 strings of various gTLD and ccTLD, the convenience of ms shorter domains are used to potential registrants and two characters For other meanings, no restriction should be no two characters ASCII labels on the second level within the TLD as agreements Registration (Specification for the two labels all 5 blocks of characters in the second level Default) - The second preocupacin is with respect to the logic that is used to many RSEP excepcina applications for the registration specification 5, which asks that Release 2 no strings of letters in the ISO list is actual.Considero erroneous because the ISO list is not static and is periodically updated to reflect changes in the countries and territories.This results in a potential disparity in the future in some countries and territories ESTN protected on the Specification for the 5, but the future they are not. This (in my mind), no must be and all countries and territories should be treated equally. However, this second point has received several comments that if there consensus to any restriction by the RSEPs qusolo requests, especially labels for two characters on the second level and ESTN happening for various gTLD and ccTLD? And if the latter withdraws preocupacin really I have to say that the first preocupacin? Dev Anand On Friday, August 8, 2014 at 1:20 pm, <asoto@ibero-americano.org> I wrote:

[[--Translated text (es -> en)--]]

Subject: FW: CALL FOR COMMENTS: ALAC Statement on the Introduction of Two-Character Domain Names in the New gTLD Namespace From: asoto@ibero-americano.org

Hi Dev, please can make a summary of a few lines on this subject to our Regin?

Thank you very much!

Alberto

From: alac-announce-bounces@atlarge-lists.icann.org [Mailto: alac-announce-bounces@atlarge-lists.icann.org] On behalf of ICANN At-Large Staff Posted on: Friday, August 8, 2014 11:07 a.m. To: ALAC-Announce@atlarge-lists.icann.org Subject: [ALAC-Announce] CALL FOR COMMENTS: ALAC Statement on the Introduction of Two-Character Domain Names in the New gTLD Namespace

Dear All,

Olivier Crpin-Leblond, Chair of the ALAC, you Asked That a call for be made comments on the draft ALAC Statement on the Introduction of Two-Character Domain Names in the New gTLD Namespace < https://community.icann.org/x/VqzhAg> ALAC ratification process.

The current draft, as well as additional information on the Public Comment, can be found on the At-Large Introduction of Two-Character Domain Names the New gTLD Namespace Workspace < https://community.icann.org/x/VqzhAg>

Please submit any comments on the workspace by using the comments 11 August 2014 20:00 GMT.

Regards,

Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Terri Agnew

ICANN Policy Staff in support of ALAC

E-mail: staff@atlarge.icann.org

ich,% 20Vivanco 20Silvia%%% 20Ashtiani 20Matt% 20Liang 20Ariel%%% 20Gru 20Gisella ber, 20Nathalie%%% 20and% 20Peregrine 20Julia 20ICANN%%% 20Charvolen 20Policy% 20Sta ff% 20in% 20support% 20of% 20ALACmailto: staff@atlarge.icann.org>

[[--Original text (es) http://mm.icann.org/transbot_archive/83cb185d0c.html --]]