October 2013 - ispcp - lists.icann.org

REMINDER: Meeting Invitation/ ISPCP CALL
by Nathalie Peregrine Feb. 13, 2014

Feb. 13, 2014

Dear All, The next ISPCP call is scheduled on Monday 14 October 2013 at 1300 UTC. To check your local time: http://tinyurl.com/psxypoh Adobe Connect room: https://icann.adobeconnect.com/_a819976787/ispcp/?launcher=false Please find the dial-in details below: Participant Passcode: Participant: 3429 # Dial-in numbers: http://www.adigo.com/icann/ Thank you. Kind regards, Nathalie

2 8

Fw: [council] new gTLD update webinar - 23 Oct 2013
by WUKnoben Oct. 29, 2013

Oct. 29, 2013

FYI Best regards Wolf-Ulrich

1 0

Fwd: [council] Fake Renewal Notices
by Novoa, Osvaldo Oct. 29, 2013

Oct. 29, 2013

All, For your information. Best regards, Osvaldo Enviado desde mi iPhone Inicio del mensaje reenviado: De: "Mason Cole" <mcole(a)5x5com.com<mailto:mcole@5x5com.com>> Fecha: 28 de octubre de 2013 18:31:17 GMT-2 Para: "Winterfeldt, Brian J." <brian.winterfeldt(a)kattenlaw.com<mailto:brian.winterfeldt@kattenlaw.com>> Cc: <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Asunto: Re: [council] Fake Renewal Notices Brian -- Many thanks for your question and please forgive my long delay in replying. By way of an update, several registrars have provided me with examples of fake renewal notices, which I have filed. I had hoped to have some legal assistance in crafting a submission to the American and Canadian consumer protection authorities, but have not been able to do so. I am happy to continue with this project (even as I will be leaving the council after the Buenos Aires meeting) -- would you or perhaps another attorney be willing to help put together a submission to consumer protection officials? I would be pleased to finish this project off. Thanks -- Mason On Oct 10, 2013, at 11:49 AM, Winterfeldt, Brian J. wrote: Dear Mason: I have a few questions with respect to fake renewal notices on behalf of the IPC, and I am hopeful you will be able to provide the Council with an update on the matter at your convenience. By way of background, here is what the Council’s pending projects list most recently provided: At its meeting in July, the GNSO Council considered the report of the Fake Renewal Notices DT (seehttp://gnso.icann.org/issues/frn/fake-renewal-notices-updated-report-20j…) On the recommendation of the RrSG, a number of alternative approaches are now being pursued to address this issue, including working with ICANN Compliance, reaching out to the relevant local authorities and considering whether it would be appropriate to address this as part of the RAA negotiations. Mason Cole provided a status update by email in February (see http://gnso.icann.org/mailing-lists/archives/council/msg14235.html) The Council will consider at its next meeting whether to close this project. And your latest update was as follows: You may recall that the council investigated a PDP but ultimately decided to reserve resources for such a PDP for other work, since the matter could be dealt with more effectively by registrars communicating to relevant law enforcement (particularly in North America). Since that time I have been collecting from registrars examples of fake renewal notices, which I will provide to the attorney that works with our SG -- she will help us submit them to the FTC in the US and other relevant law enforcement and consumer protection agencies. I realize it's been a while since the council has been updated on this, but I want to make sure we have as complete a case as possible when we approach the authorities. I anticipate doing so shortly and will of course update the council when that step is complete. My question is whether the RrSG was able to collect examples for fake renewal notices and provide them to law enforcement agencies, as well as pursue additional efforts on the matter. Was there any report delivered on these efforts? And what specifically has been done to address fake renewal notices or deceptive advertising practices from resellers? We look forward to receiving an update from you on these inquiries. Thank you, Brian Brian J. Winterfeldt Head of Internet Practice Katten Muchin Rosenman LLP 2900 K Street NW, North Tower - Suite 200 / Washington, DC 20007-5118 p / (202) 625-3562 f / (202) 339-8244 brian.winterfeldt(a)kattenlaw.com<mailto:brian.winterfeldt@kattenlaw.com> / www.kattenlaw.com<http://www.kattenlaw.com/> =========================================================== CIRCULAR 230 DISCLOSURE: Pursuant to Regulations Governing Practice Before the Internal Revenue Service, any tax advice contained herein is not intended or written to be used and cannot be used by a taxpayer for the purpose of avoiding tax penalties that may be imposed on the taxpayer. =========================================================== CONFIDENTIALITY NOTICE: This electronic mail message and any attached files contain information intended for the exclusive use of the individual or entity to whom it is addressed and may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information may be subject to legal restriction or sanction. Please notify the sender, by electronic mail or telephone, of any unintended recipients and delete the original message without making any copies. =========================================================== NOTIFICATION: Katten Muchin Rosenman LLP is an Illinois limited liability partnership that has elected to be governed by the Illinois Uniform Partnership Act (1997). =========================================================== ________________________________ El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

1 0

RV: For your review - updated GNSO PDP Improvements Table
by Novoa, Osvaldo Oct. 25, 2013

Oct. 25, 2013

Dear all, For your information and comments. Best regards, [cid:317521614@25102013-0F46]Osvaldo Novoa Subgerente General Antel Guatemala 1075, Nivel 22 Montevideo, 11800 Uruguay Tel. +598 2928 6400 Fax. +598 2928 6401 ________________________________ De: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] En nombre de Marika Konings Enviado el: Viernes, 25 de Octubre de 2013 11:11 Para: GNSO Council Asunto: [council] For your review - updated GNSO PDP Improvements Table Dear All, In relation to agenda item 8 - Prospective Improvements to the Policy Development Process - of the upcoming GNSO Council meeting, please find attached an updated version of the table. As you may be aware, the ATRT2 Draft Report (see http://www.icann.org/en/about/aoc-review/atrt/draft-recommendations-15oct13…) includes a number of recommendations concerning the GNSO PDP, some of which closely relate to those under discussion by the GNSO Council. We thought it could be helpful to include those in the overview to facilitate the discussions. As noted in the action items, 'Council members are requested to encourage their groups to review the proposed improvements and consider which suggestions can be supported and implemented'. With best regards, Marika ________________________________ El presente correo y cualquier posible archivo adjunto está dirigido únicamente al destinatario del mensaje y contiene información que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Está prohibida cualquier utilización, difusión o copia de este e-mail por cualquier persona o entidad que no sean las específicas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicación que haya sido emitida incumpliendo nuestra Política de Seguridad de la Información This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

1 0

Fw: [Soac-infoalert] Fwd: [policy] Fwd: Indian Center for DNS SecurityAnnounced
by WUKnoben Oct. 18, 2013

Oct. 18, 2013

Indian Center for DNS Security AnnouncedFYI. How will this get connected with the community needs, e.g. re name collisions? Best regards Wolf-Ulrich From: David Olive Sent: Thursday, October 17, 2013 8:38 AM To: soac-infoalert(a)icann.org Subject: [Soac-infoalert] Fwd: [policy] Fwd: Indian Center for DNS SecurityAnnounced FOR IMMEDIATE RELEASE 17 October 2013 Indian Center for DNS Security Announced ICANN and CDAC will launch research center to thwart security threats to Domain Name System New Delhi, India… ICANN today announced, in partnership with the Center for Development of Advanced Computing (CDAC), plans to coordinate on the creation of a Center of Excellence in Domain Name System Security in India. The Center of Excellence is anticipated to work alongside ICANN security staff to design research projects intended to solve critical Domain Name System (DNS) security issues, such as thwarting cyber attacks. The center is also envisioned to be home to a state-of-the-art research laboratory to evaluate and test security solutions. “This center will play a central role in ensuring the security and stability of the Domain Name System,” said Fadi Chehadé, ICANN President and Chief Executive Officer. “The Internet has become one of the world’s most valued resources and it is deserves nothing less than full global cooperation and collaboration in developing concrete solutions to combat threats to the DNS.” Fadi Chehadé, along with Dr. Rajat Moona, Director General of CDAC, will sign a letter of intent regarding the building of the center during a signing ceremony at the Internet, Mobile & Digital Economy Conference (IMDEC) IMDEC is a conference organized by the Federation of Indian Chambers of Commerce and Industry (FICCI) in association with the Ministry of Communications and IT. The topic of the conference is Internet to Equinet: Empowering a Billion OnLine”. Minister Kapil Sibal, Indian Minister of Communications and Information Technology, will oversee the signing ceremony. The Center for Development of Advanced Computing is the research and development arm of India’s Department of Electronics and Information Technology, a part of India’s Ministry of Communications & Information Technology. ### For more information about FICCI, please visit: http://www.ficci.com/events-page.asp?evid=21654 For more information about the Center for Development of Advanced Computing, please visit: http://cdac.in/ MEDIA CONTACTS: James Cole ICANN Global Media Coordinator Washington, D.C. Tel. +1 202.570.7240 james.cole(a)icann.org Andrew Robertson Edelman Public Relations London, U.K. Tel. + 44 (7811) 341 945 andrew.robertson(a)edelman.com About ICANN: ICANN’s mission is to ensure a stable, secure and unified global Internet. To reach another person on the Internet you have to type an address into your computer - a name or a number. That address has to be unique so computers know where to find each other. ICANN coordinates these unique identifiers across the world. Without that coordination we wouldn't have one global Internet. ICANN was formed in 1998. It is a not-for-profit public-benefit corporation with participants from all over the world dedicated to keeping the Internet secure, stable and interoperable. It promotes competition and develops policy on the Internet’s unique identifiers. ICANN doesn’t control content on the Internet. It cannot stop spam and it doesn’t deal with access to the Internet. But through its coordination role of the Internet’s naming system, it does have an important impact on the expansion and evolution of the Internet. For more information please visit: www.icann.org. -------------------------------------------------------------------------------- _______________________________________________ soac-infoalert mailing list soac-infoalert(a)icann.org https://mm.icann.org/mailman/listinfo/soac-infoalert

3 2

RV: [gnso-igo-ingo] Proposed Agenda - IGO-INGO Meeting 16 Oct 2013
by Novoa, Osvaldo Oct. 16, 2013

Oct. 16, 2013

All, Here you have the comments on the IGOs/INGOs WG Report. I was trying to write an abstract but it is very complicated, the RySG document is quite clear. Best regards, Osvaldo [cid:882013513@16102013-03AA]Osvaldo Novoa Subgerente General Antel Guatemala 1075, Nivel 22 Montevideo, 11800 Uruguay Tel. +598 2928 6400 Fax. +598 2928 6401 ________________________________ De: owner-gnso-igo-ingo(a)icann.org [mailto:owner-gnso-igo-ingo@icann.org] En nombre de Berry Cobb Enviado el: Martes, 15 de Octubre de 2013 18:06 Para: gnso-igo-ingo(a)icann.org Asunto: [gnso-igo-ingo] Proposed Agenda - IGO-INGO Meeting 16 Oct 2013 WG Members, Please find below the proposed agenda for Wednesday's meeting. Attached is the latest version of the public comment review tool for our draft Final Report. Also included is a PDF of the RySG submission. I suspect members may have had difficulty in accessing their attached spreadsheet and I reformatted the sheet to allow tab contents to fit on a single page. Proposed Agenda - IGO-INGO WG Meeting - 16 OCTOBER 2013 @ 16:00 UTC (120 Min): 1. Review Agenda & Changes to SOI's 2. Chair's status discussion and update 3. Review Public Comments 4. Review Workplan 5. Confirm next meeting, 23 October 2013 @ 16:00 UTC [pending DST changes] Thank you. B Berry Cobb Internet Corporation for Assigned Names & Numbers (ICANN) 720.839.5735 mail(a)berrycobb.com<mailto:mail@berrycobb.com> @berrycobb ________________________________ El presente correo y cualquier posible archivo adjunto est? dirigido ?nicamente al destinatario del mensaje y contiene informaci?n que puede ser confidencial. Si Ud. no es el destinatario correcto por favor notifique al remitente respondiendo anexando este mensaje y elimine inmediatamente el e-mail y los posibles archivos adjuntos al mismo de su sistema. Est? prohibida cualquier utilizaci?n, difusi?n o copia de este e-mail por cualquier persona o entidad que no sean las espec?ficas destinatarias del mensaje. ANTEL no acepta ninguna responsabilidad con respecto a cualquier comunicaci?n que haya sido emitida incumpliendo nuestra Pol?tica de Seguridad de la Informaci?n This e-mail and any attachment is confidential and is intended solely for the addressee(s). If you are not intended recipient please inform the sender immediately, answering this e-mail and delete it as well as the attached files. Any use, circulation or copy of this e-mail by any person or entity that is not the specific addressee(s) is prohibited. ANTEL is not responsible for any communication emitted without respecting our Information Security Policy.

2 1

CSG meeting with ATRT2 in Buenos aires
by Tony Holmes Oct. 15, 2013

Oct. 15, 2013

Please note: The CSG will now meet with the ATRT2 team at the Buenos Aires meeting on Tuesday from 12:30-1:15, following the meeting with the Board.

1 0

ICANN Strategy Panels
by WUKnoben Oct. 15, 2013

Oct. 15, 2013

FYI http://www.icann.org/en/news/announcements/announcement-14oct13-en.htm Best regards Wolf-Ulrich

1 0

Fw: [council] IDN Variant TLDS: GNSO Council response to request for further input & guidance
by WUKnoben Oct. 12, 2013

Oct. 12, 2013

FYI Wolf-Ulrich Knoben From: Glen de Saint Géry Sent: Thursday, October 10, 2013 5:05 PM To: council(a)gnso.icann.org Subject: [council] IDN Variant TLDS: GNSO Council response to request for further input & guidance Dear Councillors, Please note the correspondence between the GNSO chair, Jonathan Robinson and the ICANN Board chair, Steve Crocker regarding GNSO Council response to the request for further input and guidance on the IDN Variant TLDS http://gnso.icann.org/en/correspondence/robinson-to-crocker-07oct13-en.pdf on page http://gnso.icann.org/en/council/correspondence Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Fw: [council] ICANN Blog post on name collisions
by WUKnoben Oct. 11, 2013

Oct. 11, 2013

FYI Wolf-Ulrich Moving Forward with Delegation of Top-Level Domains by ICANN Blog on October 9, 2013 By Jeff Moss and John L. Crain ICANN's New gTLD Program Committee (NGPC) has approved resolutions allowing us to move forward in expanding the Internet's name space while mitigating possible issues in the expansion. A document describing the mitigation plan can be found here [PDF, 841 KB]. It's an understatement to say that ICANN takes its obligation to preserve the Security, Stability and Resiliency (SSR) of the Identifier Systems seriously. In fact, that part of our mission is the very first thing you read in ICANN's bylaws. In recent months, concerns have been raised that there will be "collisions" between some of the proposed new TLD strings and those used in private name spaces. The possibility that collisions can occur in the DNS is not new. Queries for non-existing strings are currently a common occurrence throughout the DNS. They can be caused by simple typos, errors in configuration, and historic or recommended use of certain names for intranet applications. The DNS is often queried to resolve such names and this "leakage" of queries from private spaces occurs at rather remarkable volumes. At the Board's direction, ICANN staff commissioned a study to examine the extent of the name collision problem and to look at possible methods for mitigating the risks. As has been noted by many community members, it is much easier to observe the occurrences of collisions than it is to assess the potential impact of a collision. DNS data collected at the root and elsewhere reveals some interesting information about queries for the proposed new TLD strings. But to assess the precise impact of these occurrences, there needs to be additional study which would allow us to learn quite a bit more about the extent of these occurrences and to determine which strings appear most often in queries. Ultimately, the additional study will allow us to develop targeted mitigation strategies. The basic concept of the risk mitigation plan adopted by the NGPC is fourfold: - First, to document on a per TLD basis those collisions that have been identified in studies of the "Day In The Life of the Internet" (DITL) data and to place each of the Secondary Level Domain (SLD) strings identified to have had collisions on a reserved or blocked list for that specific TLD. These strings will not be allowed to be registered or to resolve until such a time as the effects of the specific collision are known and appropriate mitigation strategies are developed and implemented. - Second, ICANN will develop a process by which affected parties may report and request the blocking of a SLD that causes demonstrable harm as a consequence of a name collision. This process is intended to mitigate the risk of harmful collision occurrences not observed in the study. - Third, ICANN will develop a framework to identify the probability and severity of harm to better assess the consequences of name collisions. Remember that harm and risk are not the same thing. This framework will be an important tool in identifying the likelihood of harm but also for helping to identify mitigation techniques. Once acceptable mitigations are in place it may be possible to allow the release of strings from the list of reserved or blocked names. - Finally, promoting awareness and mitigation strategies through a targeted outreach campaign will help potentially affected parties identify and manage the causes of name collision occurrences arising from their own networks. We believe the proposals outlined above afford a balanced way of moving forward. The plan minimizes the risk that collisions will cause serious harm by implementing measures to avert the problem by mitigating the associated risks and continuously monitoring the situation. We would like to thank those who have submitted research, comments, and feedback on real world examples of name collisions. The community efforts have shown that we can put aside our self-interest, consider a complex problem and drive toward solutions to meet our common objective - ensuring that the Domain Name System continues to provide services to all users in a secure, stable and resilient manner while still allowing it to grow and innovate.

1 0