- ispcp - lists.icann.org

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

Re: REMINDER: Meeting Invitation/ ISPCP OUTREACH COMMITTEE CALL
by Mike O'Connor Oct. 10, 2013

Oct. 10, 2013

hm… i wonder if i goofed this up. we just had a call, where the Outreach committee met. i wonder if we should change this one to an ISPCP "general" call? i think i'll copy the whole list and see how this time works for other people. sorry about the confusion -- can you all check your calendars and see whether time time would work for you? thanks, mikey On Oct 10, 2013, at 7:56 AM, Nathalie Peregrine <nathalie.peregrine(a)icann.org> wrote: > Dear All, > > The next ISPCP Outreach Committee 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 > PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

3 3

RE: [ispcp] Outreach call
by Tony Holmes Oct. 10, 2013

Oct. 10, 2013

Excellent thanks Alain Ive also just received my copies. Tony From: alain.bidron(a)orange.com [mailto:alain.bidron@orange.com] Sent: 10 October 2013 15:15 To: Tony Holmes; Ispcp mailing list Cc: 'Anthony Harris' (harris(a)cabase.org.ar) Subject: RE: [ispcp] Outreach call I have just received the ISPCP Brochures mailed to my office by the ICANN staff. Just on time to used them during the next RIPE meeting in Athens next week and the next IGF meeting in Bali the week after. De : owner-ispcp(a)gnso.icann.org [mailto:owner-ispcp@gnso.icann.org] De la part de Tony Holmes Envoyé : lundi 7 octobre 2013 09:59 À : Ispcp mailing list Objet : [ispcp] Outreach call ---------------------------------------------------------------------------- --------------------------------------------------------------------------- ------ Oups, votre interlocuteur continue de vous ecrire a votre ancienne adresse email : @orange-ftgroup.com. Veuillez lui demander de mettre a jour son carnet d'adresses. Vous pouvez le faire en utilisant ce modele <http://pratique.itn.ftgroup/FR/produitsetservices/messagerie/boitesperso/Do cuments/nouvelle_adresse.msg> d'email. Merci Oops, your contact is still using your old email address @orange-ftgroup.com. Please could you tell them to update their address book details for you? You can use this email template <http://pratique.itn.ftgroup/FR/produitsetservices/messagerie/boitesperso/Do cuments/nouvelle_adresse.msg> if you like. Thanks ---------------------------------------------------------------------------- --------------------------------------------------------------------------- ------ Just a reminder to those involved in the ISPCP outreach activities that there is a call scheduled for 13.00 UTC today. All those involved should have received call-in details via a separate email. If thats not the case please contact me for those details. Tony ____________________________________________________________________________ _____________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

Fw: [council] Resolution on New gTLD Collision Occurrence Management from the new gTLD committee meeting 7 Oct 2013
by WUKnoben Oct. 9, 2013

Oct. 9, 2013

FYI Wolf-Ulrich -----Ursprüngliche Nachricht----- From: Bruce Tonkin Sent: Wednesday, October 09, 2013 11:58 AM To: council(a)gnso.icann.org Subject: [council] Resolution on New gTLD Collision Occurrence Management from the new gTLD committee meeting 7 Oct 2013 From: http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-07oct13… 1. Main Agenda: a. New gTLD Collision Occurrence Management Whereas, on 15 March 2013, the ICANN Security and Stability Advisory Committee (SSAC) published SAC 057: SSAC Advisory on Internal Name Certificates. Whereas, in response to the overall issues highlighted in SAC 057, the ICANN Board directed the President and CEO, in consultation with the SSAC, to commission a study on the use of TLDs that are not currently delegated at the root level of the public DNS (the "Name Collision Study"). Whereas, the Name Collision Study, together with a proposal to manage the risks identified in the Name Collision Study (the "Proposal") was published for public comment from 5 August to 17 September. The Proposal has been revised in response to public comments. Whereas, the NGPC is undertaking this action pursuant to the authority granted to it by the Board on 10 April 2012, to exercise the ICANN Board's authority for any and all issues that may arise relating to the New gTLD Program. Resolved (2013.10.07.NG01), the NGPC directs the President, Generic Domains Division to implement the proposal to manage the occurrence of collisions between new gTLDs and existing private uses of the same strings as presented in the "New gTLD Collision Occurrence Management Plan" attached as Annex 1 (http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-annex-1… ) and in doing so to take into account further advice that may be offered by SSAC and other experts and stakeholders. Resolved (2013.10.07.NG02), the NGPC directs the ICANN President and CEO, and as appropriate through the President, Generic Domains Division, to appropriately target the planned outreach campaign. The NGPC also recommends to the Board that: (1) the ICANN Board Risk Committee expressly reviews this matter and reports back to the Board, and continues to review and report at regular intervals; (2) the Board directs the ICANN President and CEO to develop a long-term plan to manage name collision at the root; and (3) the Board directs the ICANN President and CEO to work with the community to develop a long-term plan to retain and measure root-server data.

1 0

Outreach call
by Tony Holmes Oct. 7, 2013

Oct. 7, 2013

Just a reminder to those involved in the ISPCP outreach activities that there is a call scheduled for 13.00 UTC today. All those involved should have received call-in details via a separate email. If that's not the case please contact me for those details. Tony

1 0

Fw: [council] Agenda for new gTLD Program Committee - 4 Oct 2013
by WUKnoben Oct. 4, 2013

Oct. 4, 2013

FYI Best regards Wolf-Ulrich -----Ursprüngliche Nachricht----- From: Bruce Tonkin Sent: Thursday, October 03, 2013 8:30 AM To: council(a)gnso.icann.org Subject: [council] Agenda for new gTLD Program Committee - 4 Oct 2013 Hello All, Note that the new gTLD Program Committee will be discussing Name Collision Risk Management at its meeting on Friday 4 October 2013. See: http://www.icann.org/en/groups/board/documents/agenda-new-gtld-04oct13-en.h… Regards, Bruce Tonkin

1 0

fake renewal notices
by Mike O'Connor Oct. 3, 2013

Oct. 3, 2013

hi Wolf-Ulrich and Osvaldo was there any discussion of the Fake Renewal Notices issue in the Council meeting? i noticed that it has been put on hold in the Consent Agenda. my recollection was that Mason Cole was going to run with that one and come back to the Council with a plan for what to do about those. did he ever do that? thanks, mikey PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

2 2