June 2013 - Bc-gnso - lists.icann.org

Nominet CCO fired
by svg＠stephanevangelder.com 20 Jun '13

20 Jun '13

For those who follow the cc space, this announcement might be of interest: http://www.nominet.org.uk/news/latest/news-about-our-cco Stéphane Van Gelder Chairman and Managing Director/Fondateur STEPHANE VAN GELDER CONSULTING T (UK): +44 (0)7583 457053 T (FR): +33 (0)6 20 40 55 89 Skype: SVANGELDER www.StephaneVanGelder.com ---------------- Follow us on Twitter: @stephvg and "like" us on Facebook: www.facebook.com/DomainConsultant LinkedIn: fr.linkedin.com/in/domainconsultant/

1 0

ICANN Staff Report on Public Comments re: GAC Safeguard Advice
by Phil Corwin 20 Jun '13

20 Jun '13

http://forum.icann.org/lists/comments-gac-safeguard-advice-23apr13/msg00134… Philip S. Corwin, Founding Principal Virtualaw LLC 1155 F Street, NW Suite 1050 Washington, DC 20004 202-559-8597/Direct 202-559-8750/Fax 202-255-6172/cell Twitter: @VlawDC "Luck is the residue of design" -- Branch Rickey

5 4

Nominating Committee June Report Card
by Ron Andruff 11 Jun '13

11 Jun '13

Dear colleagues, Attached to this mail is the Nom Com June Report Card, which reflects the work that Waudo and I have been participating in on behalf of the BC over the last month. As always, please let us know if you have any thoughts or questions. Kind regards, RA Ron Andruff RNA Partners www.rnapartners.com <http://www.rnapartners.com>

2 2

BC Members Call - June 6, 2013: Minutes, Transcript & MP3 Recording
by Benedetta Rossi 11 Jun '13

11 Jun '13

Dear BC Members, Please find attached the minutes I drafted and the transcript from the BC Members call which took place on Thursday, June 6th 2013 at 11 am EST. Please find the MP3 recording here: https://icann.box.com/shared/static/oo4mmqs1ofpredka30hs.mp3 These materials can also be found on the BC Wiki's conference call section: https://community.icann.org/x/0YHbAQ Thank you, -- Kind Regards, Benedetta Rossi BC Secretariat bc-secretariat(a)icann.org <https://community.icann.org/display/gnsobc/Home> https://community.icann.org/display/gnsobc/Home www.bizconst.org

3 2

BC Website Updated
by Benedetta Rossi 10 Jun '13

10 Jun '13

Dear BC Members, Please note that the BC Website has been updated recently, and now reflects all of the current positions and statements that the BC has drafted and filed, and the membership list has been updated to reflect the new members who have joined the BC. As a reminder, the BC Website is: www.bizconst.org . Comments and statements can be viewed here: http://www.bizconst.org/positions.htm . BC Membership List can be viewed here: http://www.bizconst.org/members.htm Please do not hesitate to contact me should you have any ideas or comments regarding the BC Website or the BC Wiki. Thank you, -- Kind Regards, Benedetta Rossi BC Secretariat bc-secretariat(a)icann.org <https://community.icann.org/display/gnsobc/Home> https://community.icann.org/display/gnsobc/Home www.bizconst.org

1 0

ICANN - Announcement re staff appointments/shifts- of relevance
by Marilyn Cade 08 Jun '13

08 Jun '13

ICANN to shift around top-level execs http://news.cnet.com/8301-1023_3-57588190-93/icann-to-shift-around-top-leve… Sent via BlackBerry by AT&T

1 0

Regrets on today's call
by Phil Corwin 06 Jun '13

06 Jun '13

I regret that an irreconcilable conflict will make it impossible for me to participate in this morning's BC call. Best regards to all. Philip S. Corwin, Founding Principal Virtualaw LLC 1155 F Street, NW Suite 1050 Washington, DC 20004 202-559-8597/Direct 202-559-8750/Fax 202-255-6172/cell Twitter: @VlawDC "Luck is the residue of design" -- Branch Rickey

2 1

policy docs for today's BC Member call
by Steve DelBianco 06 Jun '13

06 Jun '13

Here's background for policy topics on today's call. Recently submitted public comments from the BC: Comments on GAC Safeguard Advice for new gTLDs<http://www.bizconst.org/Positions-Statements/BC%20Comment%20on%20GAC%20Advi…> BC Comments FY14 Draft Operating Plan and Budget<http://www.bizconst.org/Positions-Statements/BC%20Comment%20on%20FY2014%20I…> BC Comments on Proposed Final 2013 RAA<http://www.bizconst.org/Positions-Statements/BC%20Comment%20on%20final%2020…> Draft BC comments on final Registry Agreement (link<http://www.icann.org/en/news/public-comment/base-agreement-29apr13-en.htm>) Elisa Cooper's latest draft is attached This draft is based on BC's previous comments in Mar-2013 (link<http://www.bizconst.org/Positions-Statements/BC%20Comment%20on%20new%20gTLD…>) Should we request community input on contract changes arising from new registry services? This comment period closes 11-Jun Draft BC comments to Accountability & Transparency Review Team Public comment page is here<http://www.icann.org/en/news/public-comment/atrt2-02apr13-en.htm>. The document with questions we want to address is here<http://www.icann.org/about/aoc-review/atrt/community-questions-02apr13-en.p…>. This comment period closes 9-Jun During the 22-May call we suggested 4 areas where the BC should comment: 1. GAC's role in ICANN 2. Who and how to define "public interest" for ICANN purposes 3. Policy vs Implementation (see BC Comment on Policy vs Implementatio<http://www.bizconst.org/Positions-Statements/BC%20Comment%20on%20Policy%20v…>n, Mar-2013) 4. Problems/questions with Volunteer selection process Volunteers included Stephane Van Gelder, Zahid Jamil, and Marilyn Cade. Below are draft comments received so far. Steve DelBianco draft for 2) Who and how to define "public interest" for ICANN purposes. The ATRT is to assess whether ICANN is accountable to the global "public interest" as required by the Affirmation of Commitments. When signing the Affirmation in 2009, Lawrence Strickling, Administrator of the U.S. National Telecommunications and Information Administration said, "this framework puts the public interest front and center and it establishes processes for stakeholders around the world to review ICANN's performance." But until the ICANN community comes together on what 'public interest' means, we are flying blind in our efforts to meet this key imperative. Leaving the term 'public interest' undefined leaves the floor open to conflicting and competing interpretations that serve the particular interests of ICANN stakeholders. The BC has previously recommended a definition for public interest that is limited to the scope of ICANN's mission. Namely, to ensure the availability and integrity of registration and resolution services. But it is not for the BC or the ATRT to define public interest for iCANN. The definition should be derived through a process open to Internet stakeholders. ICANN management have already taken steps in this direction, launching a project under the CEO's "Affirmation of Purpose" objective. Sally Costerton was assigned the goal to "Co-create clear, shared definition of the public interest." It is not clear how management would involve the community to "co-create" the definition, so the ATRT should recommend a process and guidelines to define public interest for ICANN purposes. Stephane Van Gelder's draft for 3) Policy vs Implementation: The policy versus implementation debate can only be settled by having a clear definition of each, and by having clear guidelines as to when the question should be asked and what kind of answer we are looking for. So far, the debate has clearly at times been used to obfuscate the real issue and simply attempt to get the outcome wanted by specific individuals or groups. This is a short term view that does not do justice to the multistakeholder model. The BC is part of the GNSO. As such, it supports the model of having an SO in charge of defining policy for generic Top Level Domains, with groups such as our constituency able to actively participate. This work of developing policy, which is then managed by the GNSO Council, is crucial to ICANN's function as technical coordinator for the Internet's naming and addressing system. It is crucial to develop policy, but also to implement policy. If we as a community do not know where one stops and the other begins, we run the risk of mismanaging the policy development process and of not seeing policies implemented in the way they were designed to be by the people who took the time to develop them. The BC therefore suggests that clear guidelines be set-up on what constitutes policy implementation. This is the important step, as there are already extensive rules and procedures on policy development at GNSO level. [Addition by Steve DelBianco] In accord with Affirmation paragraph 9.1, the ATRT poses questions about whether ICANN decisions are supported by the Internet community, and about the effectiveness of the Policy Development Process. (questions 12-16). The ATRT seeks specific examples for each of these questions, and the BC suggests that Strawman implementation solutions are a useful example to consider. The BC proposed that implementation decisions imposing material new obligations should be considered policy. Using the BC’s recommended distinction of whether “material new obligations” would be created, here’s how we saw the Strawman solutions breaking down between policy and implementation: (include text of our Mar-2013 comments) Stephane Van Gelder's draft for 4) Problems/questions with Volunteer selection process The ATRT is a good example of effective volunteer selection by the respective groups that make up the ICANN Community. However, the BC is concerned at what appears to be a developing trend for top-down decisions on who can participate in volunteer groups. Taking the ATRT as an example, the selection process could be tweaked so that it is fully carried out at AC or SO level and does not require final selection by the Chairman of the Board or the Chairman of the GAC. There are reasons rooted within the original AOC text for this to be the case as far as the ATRT goes, and the BC understands that. However, there are many other volunteer groups where the AOC has no bearing on the way volunteers are chosen, and yet there remains a top down approach with either the Board or ICANN Staff presiding over selections. This tends to lead to situations of under-representation by some groups, and the BC has suffered from this in the past. We would suggest that as much as possible be done to keep the volunteer group selection process as open and inclusive of all ICANN community groups as possible.

1 0

Call for Expressions of Interest for 2014 Nominating Committee Chair and Chair-Elect
by Benedetta Rossi 06 Jun '13

06 Jun '13

https://www.icann.org/en/news/announcements/announcement-05jun13-en.htm Call for Expressions of Interest for 2014 Nominating Committee Chair and Chair-Elect 5 June 2013 ICANN is immediately seeking expressions of interest for leadership roles in the 2014 Nominating Committee (NomCom) - that of the 2014 NomCom Chair and Chair-Elect. In October 2012 the ICANN Board resolved that "the Board adopts the recommendation of the BGC and hereby appoints Yrjö Juhani Länsipuro as the 2013 NomCom Chair and Cheryl Langdon-Orr as the 2013 NomCom Chair-Elect." (See <https://www.icann.org/en/groups/board/documents/resolutions-03oct12-en.htm# 2.a> http://www.icann.org/en/groups/board/documents/resolutions-03oct12-en.htm#2. a) In accordance with the 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. Accordingly, while it anticipated that the 2013 NomCom Chair Elect will succeed to the role of 2014 NomCom Chair, the incumbent NomCom leaders, in discussion with the Board Governance Committee (BGC), agree that in support of continuous improvement in its accountability and transparency, the NomCom will be initiating a new practice this year to evaluate performance of the NomCom leadership. Specifically, the NomCom will be undertaking 360 degree reviews of its Chair and its Chair-Elect, which typically consists of input from an immediate circle of colleagues - top down, bottom up and peer-to-peer, and in this case will consist of interviewing other NomCom leadership, NomCom members, as well as designated NomCom staff. These 360 degree reviews will be conducted by an independent third party provider. The BGC will utilize the outcomes of these 360 degree reviews in their processes leading up to the Board's formal appointment of the 2014 NomCom Chair and Chair-Elect. The NomCom Chair is responsible for organizing the NomCom in its activities to select certain ICANN Board members and individuals who will serve in key leadership positions within ICANN's supporting organizations (SOs) and advisory committees (ACs) in accordance with ICANN's Bylaws. The Chair is a non-voting member of the NomCom selected by ICANN's Board to serve until the conclusion of the next ICANN Annual Meeting. The Chair-Elect is a position created within the Bylaws as an outcome of the independent review of the NomCom. The Chair-Elect position is not a replacement of the Advisor to the NomCom Chair, and is not intended to fill an advisory role. Rather, the Chair-Elect will receive the benefit of training while serving alongside the Chair, gaining skills and knowledge to be applied for the Chair-Elect's anticipated succession into the role of the Chair. Candidates for Chair-Elect should possess the same skills as candidates for the Chair. Position Description 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: 1. adequate time available to undertake the role; 2. excellent communication and negotiation skills to manage a committee of 20-21 members; 3. a clear understanding of the duties and responsibilities of each position for which the NomCom is selecting candidates; 4. experience on or with a Board of Directors of organizations with similar scale, scope and diversity as ICANN; 5. strong organization and leadership skills; 6. ability to remain unbiased; 7. no conflicts of interest, and 8. a thorough understanding of, and satisfy, all criteria set forth in ICANN Bylaws relating to the NomCom (see <https://www.icann.org/en/general/bylaws.htm#VII> http://www.icann.org/general/bylaws.htm#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: 1. Approves outreach/advertising methods for attracting candidates. 2. Conducts outreach with ICANN Constituencies, ACs and SOs (with Chairs of those groups), ICANN Board, and others. 3. With other committee members, reviews and evaluates candidate Statements of Interest (SOIs) and references submitted during NomCom process 4. 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 <mailto:NomComChair2014@icann.org> NomComChair2014(a)icann.org no later than 30 June 2013. For more information about the NomCom see <http://nomcom.icann.org/> http://nomcom.icann.org/ Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Pre-Durban ICANN Policy Update Webinar Invitation 27 June 2013
by Benedetta Rossi 06 Jun '13

06 Jun '13

Dear BC Members, Please find below the Pre-Durban ICANN Policy Update Webinar Invitation for the 27th of June, 2013. To join this webinar please follow the RSVP instructions in the email below. Thank you, -- Kind Regards, Benedetta Rossi BC Secretariat bc-secretariat(a)icann.org <https://community.icann.org/display/gnsobc/Home> https://community.icann.org/display/gnsobc/Home www.bizconst.org <https://www.icann.org/en/news/announcements/announcement-03jun13-en.htm> https://www.icann.org/en/news/announcements/announcement-03jun13-en.htm Pre-Durban ICANN Policy Update Webinar Invitation 27 June 2013 3 June 2013 In order to participate, please RSVP via email to the GNSO Secretariat ( <mailto:gnso.secretariat@gnso.icann.org> gnso.secretariat(a)gnso.icann.org) to receive the call details. Whether you plan to participate in the upcoming ICANN meeting in Durban remotely or in person, you're invited to a quick reminder of the background and current status of each major policy issue currently under discussion in ICANN. The ICANN Policy Staff will provide a briefing on Thursday 27 June at 12.00 UTC and Thursday 27 June at 19.00 UTC, summarizing policy issues across the different ICANN Supporting Organizations, namely the Generic Names Supporting Organization (GNSO), Country Code Names Supporting Organization (ccNSO) and Address Supporting Organization (ASO). Among other topics, updates will be provided on: * Protection of IGO/INGO names in gTLDs PDP * 'Thick' Whois Policy Development Process * Locking of a Domain Name subject to UDRP Proceedings PDP * 10th Anniversary of the ccNSO * IDN ccPDP * Joint DNS Security and Stability Analysis Working Group * Update on RSSAC Reorganization The two sessions are duplicates, scheduled to accommodate different time zones. Each session, scheduled to run for 90 minutes, will be conducted in English only. The meeting will be run in Adobe Connect with a slide presentation along with a dial-in conference bridge for audio. Participants will have the opportunity to ask questions at the end of each session. During the course of the webinar, questions may be submitted using the chat function of Adobe Connect. If you are not able to participate in either of the live sessions, the recording of the session will be made available shortly after the meeting. The policy staff is always available to answer any questions that you email to <mailto:policy-staff@icann.org> policy-staff(a)icann.org. In order to participate, please RSVP via email to the GNSO Secretariat ( <mailto:gnso.secretariat@gnso.icann.org> gnso.secretariat(a)gnso.icann.org) to receive the call details. Please indicate which call you would like to join, Thursday at 12.00 UTC or Thursday at 19.00 UTC (to convert those times into your local time, see: <http://www.timeanddate.com/worldclock/fixedform.html> http://www.timeanddate.com/worldclock/fixedform.html) We will send you an e-mail reminder before the event with log-in and dial-in details. Please DO NOT RSVP to any other ICANN staff members e-mail address. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0