September 2018 - comments-gtld-subsequent-procedures-initial-03jul18@icann.org

[Comments-gtld-subsequent-procedures-initial-03jul18] NCSG comment
by Rafik Dammak Sept. 27, 2018

Sept. 27, 2018

Hi, Please find attached the NCSG comment. Best Regards, Rafik Dammak

1 0

[Comments-gtld-subsequent-procedures-initial-03jul18] UPDATED - Pending Ratification: Initial Report on the New gTLD Subsequent Procedures Policy Development Process (Overarching Issues & Work Tracks 1-4)
by ICANN At-Large Staff Sept. 27, 2018

Sept. 27, 2018

Dear All, Please find attached an updated version of the ALAC statement on the Initial Report on the New gTLD Subsequent Procedures Policy Development Process (Overarching Issues & Work Tracks 1-4)<https://community.icann.org/pages/viewpage.action?pageId=88573813>. The sections on 2.5.1: Application Fees (WT1) and 2.5.2: Variable Fees (WT1) were updated. In the interest of time, the ALAC Chair requested that the statement be transmitted to the ICANN public comment process with a note that the statement is pending ALAC ratification. Kind Regards, ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

[Comments-gtld-subsequent-procedures-initial-03jul18] GNSO IPC Comment -- Initial Report on the New gTLD Subsequent Procedures Policy Development Process (Overarching Issues & Work Tracks 1-4)
by Brian Scarpelli Sept. 27, 2018

Sept. 27, 2018

On behalf of the GNSO Intellectual Property Constituency IPC, see attached for the IPC comment re 'Initial Report on the New gTLD Subsequent Procedures Policy Development Process (Overarching Issues & Work Tracks 1-4).' Please let me know if IPC can assist ICANN further in this matter, Brian Scarpelli Senior Global Policy Counsel +1 517-507-1446<mailto:+1%20517-507-1446> | bscarpelli(a)actonline.org<mailto:bscarpelli@actonline.org> ACT | The App Association 1401 K St NW (Ste 501) Washington, DC 20005

1 0

[Comments-gtld-subsequent-procedures-initial-03jul18] Comments of the Public Interest Community on Subsequent Procedures Initial Report
by Mitch Stoltz Sept. 26, 2018

Sept. 26, 2018

Please find attached the comments of the Public Interest Community on the Initial Report on the New gTLD Subsequent Procedures Policy Development Process. -- Mitch Stoltz Senior Staff Attorney, EFF | 415-436-9333 x142 https://www.eff.org/donate | https://act.eff.org/

1 0

[Comments-gtld-subsequent-procedures-initial-03jul18] Comment on the Initial Report on the New gTLD Subsequent Procedures Policy Development Process
by Stephen Deerhake ＠ ASNIC Sept. 26, 2018

Sept. 26, 2018

AS Domain Registry (.as) welcomes the opportunity to comment on the Initial Report on the New gTLD Subsequent Procedures Policy Development Process. The Registry strenuously objects to the idea that 2 character (1 alpha, 1 numeric), as envisioned by Question 2.7.1.e.2, should EVER be introduced as gTLD strings. The reasons for this are detailed in the statements submitted by APTLD, CENTR, and LACNIC, which AS Domain Registry fully support. AS Domain Registry (.as) GDNS, LLC Stephen Deerhake General Manager and Director of Registry Services

1 0

[Comments-gtld-subsequent-procedures-initial-03jul18] Comments on Initial Report on the New gTLD Subsequent Procedures Policy Development
by Alexander Schubert Sept. 26, 2018

Sept. 26, 2018

All comments made by Alexander Schubert, Riga, Latvia in his personal capacity. Co-founder of .berlin and active participant in several work tracks. * In 2.5.1.c.2: I assume "principal" should be "principle"? * In 2.5.1.e.4: Are there policy, economic, or other principles or factors that might help guide the establishment of the floor amount? As we will most likely see several more rounds before we switch to continues application mode and as by the start of the next round about 8 to 9 years since the 1st round have gone by there will be a very high demand in applications. In order to keep that amount manageable and in order to prevent an application stack that would take 2,3 or maybe even 3 years to work off it would be only natural to keep the application fees for the coming round HIGH. The results would be: * A manageable application stack (ideally to be processed within a year, so the next round could start a year later) * Less speculative registrations (less warehousing) * Speedy processing for all applicants (no risk, that an application might be at the end of a long stack) The application fee floor could be slowly lowered round by round - adapting to the amount of applications of the previous round I suggest an application fee of 500,000 USD in the next round: If that should yield to only 100 or less applications; no problem as the following round would come up within a few month then (short application stack, speedy processing) Sadly in our current world seemingly a financial barrier is the only real working barrier. And absent a high entry barrier we will be FLOODED with new gTLDs - which eventually renders the DNS senseless * 2.6.1: Application Queuing (WT2) - general remark (if has to be tied with a question then 2.6.1.e.3): o The entire "application queuing" came only up as way more application were submitted than expected. THIS time we do KNOW that we have to queue! So why not simply including that task into the application process? * Any entity that doesn't wish speedy processing would indicate already at submission of the application. * Every application will receive a random (many digit long) "queueing number" assigned by the application system (yes: computers can create RANDOM numbers, since decades already) * The applications are then queued by these numbers * Absolutely no need to start hilariously complicated processes like "auctions" * 2.6.1.e.4: o CAUTION with statements like "those from the Global South should be prioritized". In other words if portfolio applicants use "global south" tax havens (like Seychelles) instead of the Caribbean: they get prioritized? We live in a globalized world: the applicant entities can be positioned ANYWHERE on the globe! * 2.6.1.c.4: o Absolutely RIDICIOUS thought. Why granting portfolio applicants EXTRA PERKS? Doesn't make ANY sense at all. Who comes up with such heinous thoughts? Why would we create BENEFITS for portfolio applicants? I thought the goal was to PREVENT "warehousing"? So NO: There is no cherry picking in the queueing process within several applications from one applicant. Thanks, Alexander Schubert

1 0

[Comments-gtld-subsequent-procedures-initial-03jul18] MarkMonitor Comments on Subsequent Procedures Working Group Initial Report
by King, Brian Sept. 26, 2018

Sept. 26, 2018

Hello, Please find MarkMonitor's comments attached, and please let me know if you have any questions. Best regards, Brian Brian J. King Director of Internet Policy & Industry Affairs MarkMonitor / Part of Clarivate Analytics Phone: +1 (443) 761-3726 brian.king(a)markmonitor.com<mailto:brian.king@markmonitor.com>

1 0

[Comments-gtld-subsequent-procedures-initial-03jul18] Google Registry - Comment on Subsequent Procedures Initial Report
by Stephanie Duchesneau Sept. 26, 2018

Sept. 26, 2018

To Whom It May Concern, Please find attached the comments by Google Registry on the Initial Report on the New gTLD Subsequent Procedures Policy Development Process. Best, Stephanie -- Stephanie Duchesneau | Domains Policy and Compliance | sd(a)google.com | 202-642-2325

1 0

[Comments-gtld-subsequent-procedures-initial-03jul18] NIC Mexico | .MX - Comments on gTLD Subsecuent procedures
by José Ernesto Grimaldo Tijerina Sept. 26, 2018

Sept. 26, 2018

A quien corresponda, NIC México<http://www.nicmexico.mx/> es la organización encargada de la administración del nombre de dominio territorial (ccTLD<http://www.nicmexico.mx/es/NicMx.Historia>, country code Top Level Domain) .MX, el código de dos letras asignado a cada país según el ISO 3166<http://www.nicmexico.mx/jsf/static_content/external_redirect.jsf?url=http:/…>. Entre sus funciones están el proveer los servicios de información y registro para .MX así como la asignación de direcciones de IP y el mantenimiento de las bases de datos respectivas a cada recurso. A continuación, presentamos la posición de NIC Mexico y .MX respecto al "Initial Report of the New gTLD Subsequent Procedures Policy Development Process Working Group" En referencia a las preguntas del Reporte Inicial: "2.7.1.e.2: If there are no technical obstacles to the use of 2-character strings at the top level consisting of one letter and one digit (or digits more generally), should the reservation of those strings be removed? Why or why not? Do you believe that any additional analysis is needed to ensure that these types of strings will not pose harm or risk to security and stability? Please explain." NIC Mexico | .MX establece que: Las preguntas técnicas solicitadas por el Grupo de trabajo de la GNSO deben ser abordadas y respondidas por grupos técnicos relevantes como el SSAC. Que cadenas de dos caracteres, que constan de una letra y un dígito, o dos dígitos, inequívocamente no deberían permitirse en futuras rondas de aplicaciones de gTLD debido al conflicto con la política de asignación de ccTLD y los códigos ISO de dos caracteres (que son externos a la ICANN), así como los problemas homográficos discutidos anteriormente. Atentamente. NIC Mexico | .MX Ernesto Grimaldo | Registry .MX English ***** NIC México is the organization in charge of the administration of the territorial domain name (ccTLD, country code Top Level Domian) .MX, the two letters code assigned to each country following the ISO 3166. Among its functions are the provisioning of information and registration services for .MX as well as the IP addresses assignation and the respective maintenances of the data bases associated to each resource. Following, is .MX - NIC Mexico´s input with respect to the Initial Report of the New gTLD Subsequent Procedures Policy Development Process Working Group, which is chartered to evaluate what changes or additions need to be made to existing new gTLD policy recommendations and includes materials from the full Working Group and four sub-teams within the Working Group, Work Tracks 1-4. In reference to the Initial Report following questions: "2.7.1.e.2: If there are no technical obstacles to the use of 2-character strings at the top level consisting of one letter and one digit (or digits more generally), should the reservation of those strings be removed? Why or why not? Do you believe that any additional analysis is needed to ensure that these types of strings will not pose harm or risk to security and stability? Please explain." NIC Mexico | .MX states that: The technical questions asked by the GNSO Working Group need to be addressed and answered by relevant technical bodies like the SSAC. That two character strings, consisting of one letter and one digit, or two digits, should unequivocally not ever be permitted in future gTLD application rounds because of the conflict with ccTLD allocation policy and ISO two-character codes (which are external to ICANN), as well as the homographic issues discussed above. Sincerely yours. NIC Mexico | .MX Ernesto Grimaldo | Registry .MX Este mensaje contiene información confidencial y se entiende dirigido y para uso exclusivo del destinatario. Si recibes este mensaje y no eres el destinatario por favor elimínalo, ya que difundir, revelar, copiar o tomar cualquier acción basada en el contenido está estrictamente prohibido. Network Information Center, S.A. de C.V., ubicado en Ave. Eugenio Garza Sada 427 L4-6 Col. Altavista, Monterrey, México, C.P. 64840 recaba tus datos personales necesarios para: la prestación, estudio, análisis y mejora del servicio, la realización de comunicaciones y notificaciones; la transferencia y publicación en los casos aplicables; el cumplimiento de la relación existente; así como para la prevención o denuncia en la comisión de ilícitos. Si eres colaborador o candidato a colaborador de NIC México, tus datos serán utilizados para: la creación y administración de tu perfil como profesionista; el otorgamiento de herramientas de trabajo; la realización de estudios; el otorgamiento de programas y beneficios para mejorar tu desarrollo profesional; la gestión y administración de servicios de pago y/o nómina; así como para contacto y/o notificaciones. Si participas en promociones o en estudios podrás dejar de participar. Para mayor información revisa el Aviso de Privacidad<http://www.nic.mx/es/NicMx.AvisosDePrivacidad>. This message contains confidential information and is intended only for the individual named. If you are not the named addressee please delete it, since the dissemination, distribuition, copy or taking any action in reliance on the contents is strictly prohibited. Network Information Center, S.A. de C.V., located on Av. Eugenio Garza Sada 427 L4-6, Col. Altavista, Monterrey, Mexico, CP 64840 collects your personal data which is necessary to: provide, research, analyze and improve the service; send communications and notices; transfer and publish your personal data when applicable; fulfill the existing relationship; prevent or inform in the commission of unlawful acts or events. If the data is processed in your quality of candidate or collaborator of NIC Mexico, the purpose of treatment is to: create and manage your profile as a professional; provide you with working tools; conduct studies; grant benefits and programs to enhance your professional development; manage and administrate payment services and/or payroll; as well as to contact you. If you participate in promotions or surveys you may stop or quit your participation at any time. For more information read the Privacy Note<http://www.nic.mx/es/NicMx.AvisosDePrivacidad>.

2 1

[Comments-gtld-subsequent-procedures-initial-03jul18] Sending on behalf of Valideus: Valideus comments on Sub Pro Initial Report
by Steve Chan Sept. 26, 2018

Sept. 26, 2018

Note: sending Valideus’ public comments on their behalf due to challenges with the submission page. Steven Chan  Policy Director, GNSO Support ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Mobile: +1.310.339.4410 Office Telephone: +1.310.301.5800 Office Fax: +1.310.823.8649 Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages. Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/ http://gnso.icann.org/en/

1 0