August 2012 - council - lists.icann.org

New e-mail address
by Mason Cole 22 Aug '12

22 Aug '12

Council colleagues -- I have been having e-mail issues with my mcole(a)nameking.com address, so for at least the time being, I've asked staff to update my contact in the list to my personal address. If you've sent mail to me at the other address and are awaiting reply, I would ask you to forward it to me here. Sorry for the inconvenience. For the record, no change in my affiliation, etc. This is merely a technical issue. Thanks -- Mason

1 0

New gTLD Update for Applicants
by Glen de Saint Géry 21 Aug '12

21 Aug '12

http://www.icann.org/en/news/announcements/announcement-3-20aug12-en.htm New gTLD Update for Applicants 20 August 2012 This week we have updates on several aspects of the new gTLD program that you should be aware of, and here they are: Metering/Batching Comments We asked<http://newgtlds.icann.org/en/announcements-and-media/announcement-29jul12-en> applicants and the broader ICANN community for ideas on how best to meter applications into the delegation process for entering approved new gTLDs into the root of the Internet. That comment period ended on 20 August. We will spend the next six weeks reviewing these contributions and, with the community, developing possible solutions. For more detailed information, check out the recently posted Roadmap for Processing New gTLD Applications<http://newgtlds.icann.org/en/announcements-and-media/announcement-17aug12-en>. Clarification Questions Pilot As we mentioned in the recent Applicant Webinar<http://newgtlds.icann.org/en/announcements-and-media/webinars>, the Clarification Questions Pilot is about to begin. This is intended to ensure consistency and effectiveness in the follow-up questions from evaluators to applicants. We have selected 50 applications to participate in the pilot, and we will be notifying those applicants soon. Participation is not required - it is completely optional. Application Withdrawals To date, six applications have been withdrawn from the new gTLD program. The withdrawals are being processed and once the applicants have received their refunds, we will provide an update. New gTLD Milestone Timeline We have posted a new timeline that displays upcoming milestones in the new gTLD program. It will be updated regularly and you can find it on the microsite homepage<http://newgtlds.icann.org/en>. We hope you find it useful. Next Applicant Webinar We are planning another applicant webinar in early September. Check the microsite often for the specific date and time. If you would like a particular topic to be discussed during the webinar, send an email to newgtldcommunications(a)icann.org<mailto:newgtldcommunications@icann.org> and we will do our best to accommodate your request. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Call for Expressions of Interest for 2012-2013 NomCom Chair
by Glen de Saint Géry 21 Aug '12

21 Aug '12

http://www.icann.org/en/news/announcements/announcement-2-20aug12-en.htm Call for Expressions of Interest for 2012-2013 NomCom Chair 20 August 2012 ICANN is immediately seeking expressions of interest for the 2012-2013 Nominating Committee (NomCom) Chair. In accordance with ICANN's Bylaws, "[i]t is anticipated that upon the conclusion of the term of the Chair-Elect, the Chair-Elect will be appointed by the Board to the position of Chair." See Article VII, section 3.4. But, the current NomCom Chair-Elect chose after the Prague meeting to not stand for NomCom Chair. That is why ICANN is now calling for those interested in serving as Chair of the 2012-2013 Nominating Committee to submit a statement of interest. All individuals who have expressed interest in serving as the Chair-Elect will be directly notified about being considered for Chair. Accordingly, if you have already submitted your statement of interest for Chair-Elect, you need not do so again for the Chair position. For more information about the NomCom see: http://nomcom.icann.org/ Position Description - Nominating Committee Chair This position blends time management and negotiation skills with the practical aspects of conducting a world-wide search for individuals to fill various ICANN leadership positions. The NomCom Chair will be called on to schedule, organize and lead numerous in-person and telephonic meetings with a large committee of community members. The NomCom Chair is also responsible for managing the candidate identification and statement of interest process, with other committee members, and for managing the due diligence to be performed on nominated candidates, in cooperation with ICANN's General Counsel and any retained outside firm(s). Throughout all NomCom activities, the Chair is responsible for ensuring that all NomCom operating rules and procedures are followed, and that all required documentation and reports are prepared in a timely fashion and provided to the proper parties as necessary. Skills and Experience To properly serve as the NomCom Chair, the selected individual must have: (i) adequate time available to undertake the role; (ii) excellent communication and negotiation skills to manage a committee of 20-21 members; (iii) a clear understanding of the duties and responsibilities of each position for which the NomCom is selecting candidates; (iv) experience on or with a Board of Directors of organizations with similar scale, scope and diversity as ICANN; (v) strong organization and leadership skills; (vi) ability to remain unbiased; (vii) no conflicts of interest, and (viii) a thorough understanding of, and satisfy, all criteria set forth in ICANN Bylaws relating to the NomCom (see http://www.icann.org/en/about/governance/bylaws#VII). Specific Duties and Responsibilities 1. Plans and schedules NomCom meetings as required, including ensuring posting schedules for public review. Please see attached for a Listing of the NomCom activities. 2. Appoints non-voting Associate Chair if so desired. 3. Reports to ICANN Board and the community on status of the NomCom. 4. Prepares and publishes the NomCom report. 5. Ensures that NomCom operating rules and procedures are followed. 6. Manages NomCom Selection Process, including: (a) Approves outreach/advertising methods for attracting candidates. (b) Conducts outreach with ICANN Constituencies, ACs and SOs (with Chairs of those groups), ICANN Board, and others. (c) With other committee members, reviews and evaluates candidate Statements of Interest (SOIs) and references submitted during NomCom process (d) Coordinates due diligence on nominated candidates in cooperation with ICANN's General Counsel and any outside firm(s) retained to perform due diligence activities. 7. Approves posting of NomCom announcements and schedules on ICANN website. 8. Ensures NomCom records are properly established, maintained and archived. Eligibility Exclusion No person who is an employee of or is a paid consultant to ICANN (including the Ombudsman) shall simultaneously serve as a member of the NomCom, including the post of Chair or Chair-Elect. Expenses All reasonable travel expenses and administrative costs incurred as a result of performing the duties as NomCom Chair or Chair-Elect in accordance with ICANN's policies will be reimbursed by ICANN upon the Chair or Chair-Elect's submission to ICANN of valid receipts and invoices. Expressions of Interest Expressions of Interest, which will be maintained as confidential, should be sent to NomComChair2013(a)icann.org<mailto:NomComChair2013@icann.org> no later than 4 September 2012. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Update to DNS Risk Management Framework Consultant RFP - Responses to Questions Received
by Glen de Saint Géry 21 Aug '12

21 Aug '12

http://www.icann.org/en/news/announcements/announcement-20aug12-en.htm Update to DNS Risk Management Framework Consultant RFP - Responses to Questions Received 20 August 2012 On 16 July, ICANN published a request for proposals<http://www.icann.org/en/news/announcements/announcement-16jul12-en.htm> for an expert consultant to assist ICANN with the development of a DNS Risk Management Framework. The announcement indicated that questions on the RFP could be submitted between 1-16 August 23:59 UTC. The period to submit questions on the RFP is now closed. ICANN is providing the questions received and responses in this update so all parties interested in responding to the call for proposals may have the same information. The deadline for responses to the call for proposals is 31 August 2012, 23:59 UTC. Responses should be sent to drmf-rfi(a)icann.org<mailto:drmf-rfi@icann.org> to the attention of Patrick Jones in the ICANN Security team. Questions Proposal Submission 1. We would like to know if you will accept proposals for this assignment from a consortium (two consulting firms) or if you are looking for a single consultant. Response - Proposals from a consortium would be welcomed. The proposal should include a description of how the parties in the consortium would work together and interact with ICANN. Timing 2. What is the anticipated time span of the project, in terms of ICANN meetings elapsed, given the the required times for internal and public comment? Response - Ideally, ICANN would be able to retain a consultant to begin work on this project in late September, and participate in an open community panel at the ICANN meeting in October in Toronto, Ontario. Specific timing deliverables will be set once the consultant is retained, but it the expectation from the Board-level working group that a draft DNS Risk Management Framework be available for discussion in early December 2012, and following relevant public comment periods for the ICANN Board at the ICANN meeting in Beijing, China in April 2013. 3. What is the anticipated duration of the transition plan to complete the launch in terms of ICANN staff availability? Response - ICANN staff will be available and following the work of the consultant throughout the project. This should reduce any delays between the start of the project and the implementation phase to operational risk management at ICANN. 4. What is the anticipated start date to execute on the RFP activities? Response - The consultant should be available to begin as soon as possible after the completion of the contracting process. Ideally this work should commence in late September so that there is sufficient time to start in advance of the ICANN meeting in Toronto. The Board-level working group will have a open community session at the ICANN meeting on Thursday 18 October, participation from the consultant in this session would be expected in order to use this time to interact with the community. 5. When will ICANN state its decision on the winning bidder? Response - ICANN intends to make its decision quickly, based on the quality of the responses received and the internal selection process. ICANN is aiming for early September to make this decision. Staff Support 6. What is the anticipated size of ICANN's internal team to implement the methodology and geographical location and diversity of designated staff? Response - Implementation of the DNS Risk Management Framework will be led by ICANN's Security team but will involve expertise from staff in other departments, including Legal, DNS Operations, IT, Finance, IANA, among others. ICANN's staff are globally distributed, although the Security team is currently split between the East Coast and West Coast US. 7. What is the makeup of the ICANN staff dedicated to executing risk management activities (number of staff, hierarchy, etc.)? Response - ICANN's Security team provides staff support to the Board Risk Committee and Board-level DNS Risk Management Framework Working Group. There are ICANN staff from the Legal team providing both Board support and Executive team participation by ICANN's General Counsel. The Executive team follows risk management activities, and individual department staff track department risks. 8. What is the commitment of FTEs in regards to ICANN's availability to contribute to the project efforts? Response - The ICANN Security team will provide staff support to engage with the consultant on this project. Preparation of Materials 9. The RFP indicates that the expert consultant will deliver a report to the Board DNS Risk Management Framework Working Group and the ICANN community. Will the deliverables that the expert consultant produces be shared verbatim with the community as public documents, or will ICANN or the expert consultant prepare summaries to be shared publically? Response - The consultant should assume that the deliverables produced for the this project will be shared verbatim with the community as public documents. The consultant should also provide executive summaries where appropriate to support community comprehension of the risk framework once it is developed. List of Tasks for a DNS Risk Management Framework 10. Task 2 - Risk Framework - Has ICANN previously adopted a risk management framework? Which framework is it? Response - Yes, ICANN has an internal enterprise risk management framework. 11. Task 2 - Risk Framework - Does ICANN have any frameworks that it is considering for adoption into their organization? Response - ICANN would be receptive to practical and implementable approaches to DNS risk management. 12. Task 2 - Risk Framework - Does ICANN have an Enterprise Risk Management (ERM) framework with which this security risk management framework should align? Response - ICANN has an internal enterprise risk management framework. ICANN would be receptive to practical and implementable approaches to DNS risk management. 13. Task 2 - Risk Framework - Would ICANN consider basing their risk management framework on leading practices and globally accepted frameworks such as Risk IT and COBIT5 for Security? Response - COBIT is primarily an information technology process framework. The consultant should take into account the focus of the risk management framework is not entirely on information technology, but broadly on DNS risks for ICANN as an organization. COBIT5 and Risk IT can serve as examples but should not be the sole basis of the consultant's proposed framework. 14. Task 2 - Risk Framework - The list of deliverables does not clearly articulate the requirement of risk governance (e.g., risk appetite and tolerance, responsibilities and accountability for IT risk management, awareness and communication, risk culture). Is this also a desired deliverable? Response - Recommendations from the consultant on mechanisms for clearly articulating the requirement of risk governance would be welcomed within the context of DNS risks. 15. Task 3 - Build Consensus - How long is the public comment cycle expected to last? The process for ICANN's public comment cycle is described at http://www.icann.org/en/news/public-comment. The total length of the public comment cycle will depend on whether comments are received in the initial comment period, requiring a reply comment period. The Working Group envisioned public comment being conducted in the early part of 2013, although this is subject to change depending on a variety of factors. 16. Task 3 - Build Consensus - Will the Working Group provide review and comment prior to the public comment cycle? Will there be opportunity to make revisions to the framework prior to release for public comment, based on feedback from the Working Group? Response - Yes 17. Task 3 - Build Consensus - What measure will the Working Group utilize to gauge if consensus has been achieved? Response - The Working Group seeks a DNS Risk Management Framework that will be implementable and is generally accepted by the community as meeting the deliverables in this tender. 18. Task 3 - Build Consensus - The RFP indicates that the expert consultant will "assist staff and the working group to build consensus in support of the risk management framework within ICANN (the organization and the community)." Will the expert consultant be interacting directly with the community, or will the expert consultant interact with the community only through ICANN staff? Response - From a starting point, it is desired by the Board-level Working Group to have the consultant participate in the open session of the Working Group at the ICANN meeting in Toronto on 18 October 2012. This meeting will provide an opportunity for interested participants in the community to ask questions, and for the consultant to engage with those attending the meeting. It is also expected that the consultant will interact directly with experts in the community in development of the risk framework. 19. Task 4 - Risk Cycle - The RFP indicates that Task 4 is part of a "Potential Phase II". What are the determinants for whether "Phase II" will occur? The Board and ICANN senior management will determine next steps in the process after the delivery of the Phase 1 DNS risk management framework, including the timing and feasibility of Phase II as described in the RFP. The response to the RFP can include a description of how the consultant would consider deliverables in Phase II. 20. Task 4 - Risk Cycle - Should the proposal include estimates for potential Phase II activities? Response - Yes, although this could be presented at a high level, granular detail on steps in Phase II is not required for Phase I but may be helpful for ICANN to understand the methodology that the consultant proposes to use. 21. Task 4 - Risk Cycle - What tools is ICANN utilizing today to identify, document, manage and monitor risks? Response - ICANN tracks risks within its departments and also provides regular updates on key program risk areas through the relevant Board Committee, such as the Board Risk Committee, Board Finance Committee, Board IANA Committee, among others. The new gTLD program has a separate risk reporting mechanism through the Board New gTLD Committee. 22. Task 4 - Does ICANN leverage any Governance, Risk Management and Compliance (GRC) technology solutions? Response - ICANN's Compliance team is in the process of developing tools to assist its efforts in managing compliance risks. ICANN would be receptive to suggestions for technology solutions that assist in making the DNS risk management framework practical and implementable once delivered by the consultant. 23. Task 4 - Risk Cycle - Does ICANN leverage previously identified and documented risks in their organization? Are there other risk activities occurring in the organization? What are they? Response - ICANN conducts regular meetings of its Board Risk Committee and utilizes its previously identified and documented risks in managing risk within the organization. 24. Task 4 - Risk Cycle - Would ICANN like to include in the deliverable a baseline process, risk and control library for their key security risks? Response - The primary tasks for this contract are described in the RFP. Additional information should support the delivery of a DNS risk management framework for the organization. 25. Task 4 - Risk Cycle - In addressing the risk plan (risk response strategy), does ICANN want sample test procedures included to validate the effectiveness of the risk plan in addition to monitoring procedures of key indicators? Response - Yes, these can be included if they support the framework. 26. Task 4 - Risk Cycle - Would ICANN like assistance in the design and development of monitoring and dashboard reports? Response - Design and development of monitoring and dashboard reporting would go toward implementation and execution of an initial cycle of the framework as part of Phase II. These suggestions could be included in the RFP but are not required at this stage. General 27. What are the key selection criteria ICANN is using to award this RFP? Response - ICANN will evaluate the responses received to identify an expert consultant that can apply risk methodologies to the unique aspects of the Domain Name System, including its international nature and multistakeholder participation. ICANN needs a consultant who can deliver a quality product in a relatively narrow period of time, that will hold up to community scrutiny and analysis. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Final Consumer Metrics Advice
by john＠crediblecontext.com 20 Aug '12

20 Aug '12

Councillors, As the GNSO Council liaison to the Consumer Metrics drafting team, it is my honor to forward for discussion a copy of the final advice letter. Recall that in response to the Affirmation of Commitments requirement for a post-new gTLD launch review of competition, consumer trust and consumer choice, the ICANN Board resolved in December 2010 to request advice from the ALAC, GAC, GNSO and ccNSO on establishing the definition, measures, and three year targets for those measures, for competition, consumer trust and consumer choice. That advice is attached. Also attached is a proposed timeline beginning with a request that we put this item on our September 13 meeting agenda. Cheers, John Berard

1 0

ICANN Seeks Input on gTLD Batching
by Thomas Rickert 19 Aug '12

19 Aug '12

Dear all, you will have heard that ICANN has recently published an announcement, due to which it seeks input on gTLD Batching, see https://www.icann.org/en/news/announcements/announcement-29jul12-en.htm eco is planning to submit a comment. With this e-mail I would like to encourage all of you to provide me with input by August 5th. I will amalgamate your input into one statement and send it to this list for your review. Please let me know if you have any questions. Also, please let me know if you would like me to include other / additional contacts inside your company. Best regards, Thomas Rickert ___________________________________________________________ Thomas Rickert, Attorney at Law Director Names & Numbers ------------------------------------- eco - Verband der deutschen Internetwirtschaft e.V. Lichtstraße 43h 50825 Köln Fon: +49 (0) 221 - 70 00 48 - 0 Fax: +49 (0) 221 - 70 00 48 - 111 E-Mail: thomas.rickert(a)eco.de Web: http://www.eco.de --------------------------------------------------- eco - Verband der deutschen Internetwirtschaft e.V. Geschäftsführer: Harald A. Summa Vorstand: Prof. Michael Rotert (Vorsitzender), Oliver Süme (stv. Vorsitzender), Klaus Landefeld, Thomas von Bülow, Felix Höger Vereinsregister: Amtsgericht Köln, VR 14478 Sitz des Vereins: Köln

1 3

Fwd: Message on Constituency Travel
by Stéphane Van Gelder 16 Aug '12

16 Aug '12

Councillors, FYI. Stéphane Van Gelder Directeur Général / General manager INDOM Group NBT France ---------------- Head of Domain Operations Group NBT Début du message réexpédié : > De : Janice Douma Lange <janice.lange(a)icann.org> > Objet : Message on Constituency Travel > Date : 16 août 2012 03:56:26 UTC+02:00 > À : Marilyn Cade <marilynscade(a)hotmail.com>, "ocl(a)gih.com" <ocl(a)gih.com>, Tony Holmes <tonyarholmes(a)btinternet.com>, "stephane.vangelder(a)indom.com" <stephane.vangelder(a)indom.com>, Robin Gross <robin(a)ipjustice.org>, "Metalitz, Steven (met(a)msk.com)" <met(a)msk.com>, "Alain Berranger (alain.berranger(a)gmail.com)" <alain.berranger(a)gmail.com>, "Chris Chaplow (chris(a)andaluciaws.com)" <chris(a)andaluciaws.com>, "Heather (Heather.Dryden(a)ic.gc.ca)" <Heather.Dryden(a)ic.gc.ca>, Jacqueline Campbell <Jacqueline.Campbell(a)nominet.org.uk>, "'Louie Lee (louie(a)louie.net)'" <louie(a)louie.net>, "'jcurran(a)arin.net'" <jcurran(a)arin.net>, 'Patrik Fältström ' <patrik(a)frobbit.se>, "'Jun Murai (junsec(a)wide.ad.jp)'" <junsec(a)wide.ad.jp>, "'dave(a)difference.com.au'" <dave(a)difference.com.au>, 'David Maher ' <dmaher(a)pir.org>, "'matt.serlin(a)markmonitor.com'" <matt.serlin(a)markmonitor.com> > Cc: "policy(a)icann.org" <policy(a)icann.org>, Aba Diakite <aba.diakite(a)icann.org>, "Xavier J. Calvez" <xavier.calvez(a)icann.org>, ICANN Constituency Travel <constituency-travel(a)icann.org>, Jeannie Ellers <jeannie.ellers(a)icann.org>, Karla Valente <karla.valente(a)icann.org>, Tim Cole <Tim.Cole(a)icann.org> > > As there were several inquiries recently regarding FY13 supported community travel, we decided to put out this clarifying email for all SO, AC and SG community members. Please respond back directly to me if there are any questions. > > > > > > > > > > > > > > > > > > > > Travel Support for Community Members in FY13 Budget > Travelers per ICANN Meeting > ALAC > 27.0 > ccNSO > 12.0 > > GAC > 20.0 > GNSO > 21.0 > SSAC > 10.0 > > Nom Com > 22.0 > Fellow > 25.0 > > > > Additional Travel Support per the Approved SO AC Requests for FY13 Only: > > 1. NCSG-EC – 3 travel slots per each (2) ICANN meetings in FY13 > > 2. gNSO Non-contracted parties > BC – 3 addt’l slots per each (2) ICANN meetings in FY13 > IPC – 3 addt’l slots per each (2) ICANN meetings in FY13 > ISP – 3 addt’l slots per each (2) ICANN meetings in FY13 > NCUC – 3 addt’l slots per each (2) ICANN meetings in FY13 > NPOC – 3 addt’l slots per each (2) ICANN meetings in FY13 > > 3. NARALO – travel support will be provided as allowed in approved budget

1 0

Input Tracking for the Board GNSO PDP Recommendations
by David Olive 15 Aug '12

15 Aug '12

Dear GNSO Council Members and Liaisons: As part of ICANN's implementation of the ATRT Recommendations, we have developed and are implementing the attached checklist as a tool to meet Recommendation 20, which states: 20. The Board should ensure that all necessary inputs that have been received in policy making processes are accounted for and included for consideration by the Board. To assist in this, the Board should as soon as possible adopt and make available to the community a mechanism such as a checklist or template to accompany documentation for Board decisions that certifies what inputs have been received and are included for consideration by the Board. As the GNSO is the SO that is most active in providing recommendations to the Board arising out of the policy development process, this checklist is being piloted within the GNSO. This would be a tool that staff would have the primary obligation for completing as part of the submission of GNSO Policy recommendations, and is not intended to replace any of the existing documentation requirements. We would appreciate your thoughts on if there are improvements that could be made to this checklist to help make sure that this is sufficient to capture the inputs as identified in the ATRT Recommendation. Please provide your inputs to rec-20-checklist(a)icann.org by 7 September 2012. After your input is collected, we will be revising the checklist for use by each of the Supporting Organizations. We expect that this checklist will go through iterations as we gain experience working with it. Thank you for your help and input. Regards, David David A. Olive Vice President, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) 1101 New York Avenue, NW - Suite 930 Washington, D.C. 20005 Office: 202.570.7126 Mobile: 202.341.3611

1 0

Re: Canada and GAC High-level Meeting at ICANN 45 - Toronto
by Stéphane Van Gelder 15 Aug '12

15 Aug '12

Councillors, Please find below the GAC response to my clarification question. I have put this on the agenda for our next meeting as I would like us to have discussed this before going into Toronto. Please also share with your respective groups as required. Stéphane Van Gelder Directeur Général / General manager INDOM Group NBT France ---------------- Head of Domain Operations Group NBT Le 15 août 2012 à 04:02, Heather.Dryden(a)ic.gc.ca a écrit : > The HLM meetings will be open and transcribed so attendance of the SOAC leadership for the other parts of the program would be based on their level of interest and availability. > > Without going into all the protocol and history of the exchanges among governments about how to convene a high-level meeting at ICANN, perhaps it is easiest to say that the GAC and the Canadian government are "co-hosting" the HLM meetings (it just happens that GAC chair is also Canadian). For the 4pm session, I would recommend preparation of Qs and lining up speakers in advance. I trust that the GNSO leadership will work with the GAC, as well as my Canadian colleagues, to find a balance between the differing cultures of the GNSO, and senior officials and politicians unfamiliar with the ICANN environment, to have a positive and productive exchange to reinforce and improve the multistakeholder model. > > Thanks! > Heather > > From: Stéphane Van Gelder [mailto:stephane.vangelder@indom.com] > Sent: Tue 2012-08-14 12:03 PM > To: Dryden, Heather: SPS > Cc: lesley(a)nominet.org.uk; ocl(a)gih.com; paf(a)frobbit.se; jcurran(a)arin.net; Johnston, Susan: SPS; LIM_Choon_Sai(a)ida.gov.sg; alice(a)apc.org; maria.hall(a)enterprise.ministry.se; jeannie.ellers(a)icann.org > Subject: Re: Canada and GAC High-level Meeting at ICANN 45 - Toronto > > Thanks Heather. > > It is unclear to me from reading the attachment wether this is a meeting where you are asking for SO/AC leadership attendance (beside the 16pm slot on Monday) and if so, what level of input you are asking from those participants. > > On the 16pm slot, I would be grateful for more context on this high-level meeting, if it is purely a canadian initiative (or is it a GAC initiative) and whether you are expecting a real conversation or a Q&A type session only? > > Thanks. > > In the meantime, I will post on the GNSO Council list so that Councillors are informed. > > Stéphane Van Gelder > Directeur Général / General manager > INDOM Group NBT France > ---------------- > Head of Domain Operations > Group NBT > > Le 14 août 2012 à 07:22, <Heather.Dryden(a)ic.gc.ca> a écrit : > >> Dear SOAC chairs, (please forward if I have missed anyone) >> >> I am writing to provide you with some preliminary information about the Canada and GAC High-Level meetings to take place on October 15th in Toronto. Canada is currently seeking feedback on the proposal from GAC members and initial comments from the SO and AC chairs would also be appreciated. This information has also been provided to the Board for feedback. >> >> As you can see from the attached, we are proposing an exchange with the leadership of the SOs and ACs at ICANN in the afternoon. >> >> I will now be on vacation until the beginning of September. However, I am copying Susan Johnston (susan.johnston(a)ic.gc.ca), who is responsible for planning the event on behalf of Industry Canada, as well as the GAC vice-chairs and Jeannie, who will be capably handling GAC matters in my absence. Please contact the aforementioned for further information or guidance. >> >> We can also discuss this on the next SOAC teleconference (which I think is scheduled for September). >> >> All the best, >> Heather >> >> >> >> >> <SITT-STIT-#294667-v8-ICANN_GAC_HLM_preliminary_agenda_.doc> >

1 0

DSSA Working Group Phase 1 Report - Public Comment Period Open
by Glen de Saint Géry 15 Aug '12

15 Aug '12

http://www.icann.org/en/news/announcements/announcement-14aug12-en.htm DSSA Working Group Phase 1 Report Comment/Reply Periods (*) Important Information Links Comment Open: 14 August 2012 Comment Close: 13 September 2012 Close Time (UTC): 23:59 UTC Public Comment Announcement<http://www.icann.org/en/news/announcements/announcement-14aug12-en.htm> Reply Open: 14 September 2012 To Submit Your Comments (Forum)<mailto:dssa-phase-1-report@icann.org> Reply Close: 21 October 2012 View Comments Submitted<http://forum.icann.org/lists/dssa-phase-1-report/> Close Time (UTC): 23:59 UTC Report of Public Comments Brief Overview Originating Organization: DNS Security & Stability Analysis Working Group Categories/Tags: * DNS * Security/Stability Purpose (Brief): The DNS Security & Stability Analysis (DSSA) Working Group is seeking community comment on its Phase 1 Report. The Report was originally published on 15 June 2012 prior to the ICANN meeting in Prague, Czech Republic. The goal of the report is to bring forward for the community the work that the DSSA has completed to date and describe the work that remains. Current Status: Open for public comment Next Steps: The DSSA Working Group intends to perform a proof of concept to refine and streamline the methodology on one broad risk-scenario topic with the goal of reducing cycle time and making it more accessible to the broader community. Public comment on the Phase 1 Report will be used to focus attention of the DSSA Working Group on specific work areas and refinement of the methodology. Staff Contact: Patrick Jones Email: patrick.jones(a)icann.org<mailto:patrick.jones@icann.org?subject=More%20information%20on%20the%20DSSA%20Working%20Group%20Phase%201%20Report%20public%20comment%20period> Detailed Information Section I: Description, Explanation, and Purpose This is the first of two reports from the DNS Security & Stability Analysis Working Group. The goal of this document is to bring forward the substantial work that has been completed to date and describe the work that remains. This has been in many respects a "pioneering" cross-constituency security-assessment effort that has developed knowledge and processes that others will hopefully find helpful and can be reused in the future. The DSSA has: * Established a cross-constituency working group and put the organizational framework to manage that group in place * Clarified the system, organizational and functional scope of the effort * Developed an approach to handling confidential information, should such information be required for certain assessments * Selected and tailored a risk-assessment methodology to structure the work * Developed and tested mechanisms to rapidly collect and consolidate risk-assessment scenarios across and broad and diverse group of interested participants * Used an "alpha-test" of those systems to develop the high-level risk-scenarios in this report. Those scenarios will serve as the starting point for the remainder of the effort. Work that remains: * Perform a proof of concept to refine and streamline the methodology on one broad risk-scenario topic with the goal of reducing cycle time and making it more accessible to a broader community * Roll the methodology out to progressively broader groups of participants to introduce the methodology to the community and further improve the process and tools on the way to completing the assessment. Public comment is sought on the Phase 1 Report. Section II: Background The objective of the DSSA Working Group is to draw upon the collective expertise of the participating SOs and ACs, solicit expert input and advice and report to the respective participating SOs and ACs on: The actual level, frequency and severity of threats to the DNS. The DSSA Working Group was originally published on 15 June 2012 prior to the ICANN Prague meeting. The report was discussed at the DSSA Working Group open session in Prague, and details on that meeting can be found at http://prague44.icann.org/node/31805. Section III: Document and Resource Links DSSA Working Group Phase 1 Report<http://gnso.icann.org/en/issues/dssa/dssa-phase-1-report-15jun12-en.pdf> [PDF, 4.57 MB] Section IV: Additional Information None (*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0