- Ws2-staff_acct - lists.icann.org

Doc B
by avri doria Jan. 16, 2017

Jan. 16, 2017

hi, A few days late, and far short of what the doc needs to become, but a first draft can be found in: <https://docs.google.com/document/d/1UnkJuukv0px-CfIDgLrjdDZa2CpBvSahPvAXdYY…> The doc is open for text suggestions, recommended edits and comments. A pdf is attached. At this point i am the only person who has contributed to this doc. It needs more of a team effort than just that. I will try to get more time on it in the next days, but still need help. Also note that the request for access to staff documentation that is beyond the staff portal is still pending. thanks avri --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 0

Reminder - thoughts on doc A
by Jordan Carter Jan. 10, 2017

Jan. 10, 2017

Hi all A reminder from our last call - there's an action on participants in the Staff Accountability group to have a look at the working draft of the document that looks at relationships between Board, Staff and Community in ICANN: https://docs.google.com/document/d/1wXuZw-VFeMLT3B5UHLU_nY1SWyzp6-VLeVZF1FY… It's my task to edit and reconcile those comments later this week. *If you are able to add your input by Midnight Wednesday UTC that would be helpful.* Thanks! Jordan -- Jordan Carter Chief Executive *InternetNZ * +64-4-495-2118 (office) | +64-21-442-649 (mob) | Skype: jordancarter jordan(a)InternetNZ.net.nz | www.InternetNZ.nz *A better world through a better Internet*

2 1

Agenda for meeting week 1 2017; 5 Jan 0500
by avri doria Jan. 5, 2017

Jan. 5, 2017

Agenda for meeting week 1 2017; 5 Jan 0500 * Meeting start items * Discussion of CCWG Staff Accountability working draft draft 1.2 - Jordon is lead rapporteur on this doc. * Schedule check * AOB Document, open to comments and suggested edits, can be found at: <https://docs.google.com/document/d/1wXuZw-VFeMLT3B5UHLU_nY1SWyzp6-VLeVZF1FY…> PDF attached, however pdf downloads from Drive do not show comments made to the text in the Drive doc. If you cannot make the meeting please take an opportunity to comment in the Drive document so the comments can be included in meeting discussion. If you cannot make comments directly in the drive doc, please send them to the list. Note, Google drive does have the capability of allow editing of documents offline. You need to be online for initial access and for posting the edits, but they can be made when offline. Works on most mobiles as well. Thanks avri --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

3 2

Should the Complaints Officer report into the General Counsel’s office?
by Pam Little Jan. 5, 2017

Jan. 5, 2017

Hi all, During today’s call, I noted that there have been some discussions on the list and in Hyderabad but not sure if the issue has been dropped or settled. I raised my concern over this newly created role reporting to ICANN’s General Counsel. My concern is twofold: potential conflict of interest and risks associated with concentration of power. I advocated for a separate Compliance & Ethics office be created within ICANN and would welcome thoughts and feedback from this group. There is no shortage of debate and diverse views on whether legal and compliance functions should be separate but thought this article (or the excerpt) might be of interest. https://globalcompliancenews.com/independence-day-the-separate-and-equal-co… Moreover, a joint Society of Corporate Compliance and Ethics (“SCCE”) and NYSE Governance Services survey released in September 2014 found that only 8% of the 249 organizations surveyed placed overall responsibility for the ethics and compliance program with the general counsel or chief legal officer, while 56% placed it with a compliance and/or ethics officer.[4] Among the entities surveyed, only 18% of the individuals responsible for compliance reported to the general counsel, while 38% reported to the CEO, and 19% to the board of directors. Accordingly, well over half of the entities surveyed maintain compliance departments separate from, and certainly not under the direct control of, the general counsel. An annual benchmarking survey conducted by Deloitte and Compliance Week reveals a similar trend. Of the 364 respondents participating in their 2015 Compliance Trends Survey, 59% reported having a stand-alone CCO, representing a 9% increase from the survey’s 2014 findings and a 22% increase from the 2013 findings. Additionally, in 57% of the participant companies, the CCO reports directly to the CEO or board of directors. Kind regards, Pam Little From: accountability-cross-community-bounces(a)icann.org [mailto:accountability-cross-community-bounces@icann.org] On Behalf Of MSSI Secretariat Sent: Thursday, January 05, 2017 5:31 PM To: ws2-staff_acct(a)icann.org Cc: CCWG Accountability Subject: [CCWG-ACCT] Notes, recordings, transcript for WS2 Staff Accountability Subgroup Meeting #6_ 05JAN17 Hello all, The notes, recordings and transcripts for CCWG Accountability WS2 Staff Accountability Subgroup Meeting #6 – 05 January 2017 will be available here: https://community.icann.org/x/wp3DAw A copy of the notes may be found below. Thank you. Kind Regards, Yvette Guigneaux Multi-Stakeholder & Strategic Initiative Assistant ICANN | Internet Corporation for Assigned Names & Numbers 12025 Waterfront Drive, Playa Vista, CA 90094 yvette.guigneaux(a)icann.org | www.icann.org[icann.org] <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DgMGaQ…> _____ NOTES 1. Meeting start items - review of agenda and other administrative items 2. Review and discussion of responses to Questions from ICANN - noted that some of the responses to the questions may lead to recommendations for the group to consider. - need to provide some responses to the quetions posed in the response noted documents available to the staff to describe codes and they are posted on ICANN.org web site, wondered if those documents are available for the community to review/read, assumption that they are not currently available for the community - are they private to the employess and not visible to the community? - noted the need for further review of the response - concerns raised that ICANN has a lot of process and documents in place, but who is looking into the practice of the process and what are the consequences of not following the process in place, example what happens when CEO exceeds power delegated to him, noted are things as good as ICANN would like us to believe - concerns on the devils in the details Action (Karen): see if it would be possible to have a follow-up discussion with HR - concerns expressed on the Compliance Officer being under the General Counsel's office. Action (Pam Little): send email to the list with suggestions on the Compliance Officer Questions for follow-up: - Are the staff documents/codes noted in the response privet to staff only or are they public for community review? 3. Discussion of CCWG Staff Accountability working draft draft 1.2 (Document A) - document seems to be longer than expected. - document is meant to look at the relationship between the Board, the community and the staff. - there might be perceived conflicts of interest. - there appears to be different expectations from the community of the roles of staff, board and community. - there is a basic gap between what is said and what happens in reality. - not sure what was descriptive and what was normative in this document. - concern over the isolation of the board, and isolation of the 3 groups from each other. - document is a first draft, and needs more work from the group. - competing interests within the ICANN community makes it challenging for staff to be held accountable Action (subgroup): review and edit the document by the middle of next week (Wednesday, Jan 11), add comments but also add drafting changes in suggestion mode. Jordan and Klaus will then edit the document before the next call. For document B: - hiring process should be more open 4. Schedule check - Goal is to try and close document A by the next meeting - Avri will be working on document B next week, and will send the URL to the group - sticking to the schedule discussed in the last call: · Call 19 January (19h UTC): Test agreed changes to draft Document A. Work through draft Document B · Call 2 February (13h UTC): Test agreed changes to draft Document B. Finalise Document A for CCWG Plenary. Can send A to CCWG Plenary. · Call 16 February (05h UTC): Finalise Document B for CCWG Plenary. Both Documents to CCWG Plenary · Call 2 March (19h UTC): (if necessary - incorporate feedback from Plenary?) · Face to Face Plenary - 10 March 5. AOB - Concerns raised over the fact that very limited group of people are participating. We can try to get more people involved through the plenary. -Suggestion to get emails of participants and send the URL link to participants.

1 0

Notes, recordings, transcript for WS2 Staff Accountability Subgroup Meeting #6_ 05JAN17
by MSSI Secretariat Jan. 5, 2017

Jan. 5, 2017

Hello all, The notes, recordings and transcripts for CCWG Accountability WS2 Staff Accountability Subgroup Meeting #6 – 05 January 2017 will be available here: https://community.icann.org/x/wp3DAw A copy of the notes may be found below. Thank you. Kind Regards, Yvette Guigneaux Multi-Stakeholder & Strategic Initiative Assistant ICANN | Internet Corporation for Assigned Names & Numbers 12025 Waterfront Drive, Playa Vista, CA 90094 yvette.guigneaux(a)icann.org<mailto:yvette.guigneaux@icann.org> | www.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DgMGaQ…> ________________________________ NOTES 1. Meeting start items - review of agenda and other administrative items 2. Review and discussion of responses to Questions from ICANN - noted that some of the responses to the questions may lead to recommendations for the group to consider. - need to provide some responses to the quetions posed in the response noted documents available to the staff to describe codes and they are posted on ICANN.org web site, wondered if those documents are available for the community to review/read, assumption that they are not currently available for the community - are they private to the employess and not visible to the community? - noted the need for further review of the response - concerns raised that ICANN has a lot of process and documents in place, but who is looking into the practice of the process and what are the consequences of not following the process in place, example what happens when CEO exceeds power delegated to him, noted are things as good as ICANN would like us to believe - concerns on the devils in the details Action (Karen): see if it would be possible to have a follow-up discussion with HR - concerns expressed on the Compliance Officer being under the General Counsel's office. Action (Pam Little): send email to the list with suggestions on the Compliance Officer Questions for follow-up: - Are the staff documents/codes noted in the response privet to staff only or are they public for community review? 3. Discussion of CCWG Staff Accountability working draft draft 1.2 (Document A) - document seems to be longer than expected. - document is meant to look at the relationship between the Board, the community and the staff. - there might be perceived conflicts of interest. - there appears to be different expectations from the community of the roles of staff, board and community. - there is a basic gap between what is said and what happens in reality. - not sure what was descriptive and what was normative in this document. - concern over the isolation of the board, and isolation of the 3 groups from each other. - document is a first draft, and needs more work from the group. - competing interests within the ICANN community makes it challenging for staff to be held accountable Action (subgroup): review and edit the document by the middle of next week (Wednesday, Jan 11), add comments but also add drafting changes in suggestion mode. Jordan and Klaus will then edit the document before the next call. For document B: - hiring process should be more open 4. Schedule check - Goal is to try and close document A by the next meeting - Avri will be working on document B next week, and will send the URL to the group - sticking to the schedule discussed in the last call: • Call 19 January (19h UTC): Test agreed changes to draft Document A. Work through draft Document B • Call 2 February (13h UTC): Test agreed changes to draft Document B. Finalise Document A for CCWG Plenary. Can send A to CCWG Plenary. • Call 16 February (05h UTC): Finalise Document B for CCWG Plenary. Both Documents to CCWG Plenary • Call 2 March (19h UTC): (if necessary - incorporate feedback from Plenary?) • Face to Face Plenary - 10 March 5. AOB - Concerns raised over the fact that very limited group of people are participating. We can try to get more people involved through the plenary. -Suggestion to get emails of participants and send the URL link to participants.

1 0

Re: [Ws2-staff_acct] Agenda for meeting week 1 2017; 5 Jan 0500
by avri＠acm.org Jan. 5, 2017

Jan. 5, 2017

Hi, I don't think we did. Sounds like a good idea. Avri Sent from my T-Mobile 4G LTE Device -------- Original message --------From: Jordan Carter <jordan(a)internetnz.net.nz> Date: 1/3/17 21:13 (GMT-05:00) To: avri(a)acm.org, ws2-staff_acct(a)icann.org Subject: Re: [Ws2-staff_acct] Agenda for meeting week 1 2017; 5 Jan 0500 I missed a few meetings end of last year but have we discussed the staff reply to our questions? If not, shall we add that? J On Tue, 3 Jan 2017 at 1:25 PM, avri doria <avri(a)acm.org> wrote: Agenda for meeting week 1 2017; 5 Jan 0500 * Meeting start items * Discussion of CCWG Staff Accountability working draft draft 1.2 - Jordon is lead rapporteur on this doc. * Schedule check * AOB Document, open to comments and suggested edits, can be found at: <https://docs.google.com/document/d/1wXuZw-VFeMLT3B5UHLU_nY1SWyzp6-VLeVZF1FY…> PDF attached, however pdf downloads from Drive do not show comments made to the text in the Drive doc. If you cannot make the meeting please take an opportunity to comment in the Drive document so the comments can be included in meeting discussion. If you cannot make comments directly in the drive doc, please send them to the list. Note, Google drive does have the capability of allow editing of documents offline. You need to be online for initial access and for posting the edits, but they can be made when offline. Works on most mobiles as well. Thanks avri --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus _______________________________________________ Ws2-staff_acct mailing list Ws2-staff_acct(a)icann.org https://mm.icann.org/mailman/listinfo/ws2-staff_acct -- Jordan Carter Chief Executive, InternetNZ +64-21-442-649 | jordan(a)internetnz.net.nz Sent on the run, apologies for brevity

2 2

ICANN doc on board/staff roles
by Jordan Carter Dec. 22, 2016

Dec. 22, 2016

Hi all As part of the ICANN reply to our questions on roles and responsibilities, they referenced a delegations document approved by the Board last month. I've copied it as an attachment to this email, and the link is: https://www.icann.org/en/system/files/files/delegation-of-authority-guideli… This provides substantial basis for the Document A work I am doing some low key drafting on (definition below). *Could those interested in the relationships Board <--> Staff <--> Community, have a look at the document and offer your opinions about its content?* This will help as I prepare a first draft of the paper over the next few days. By way of reminder, here is what document A is... - The CCWG-Accountability work with ICANN to develop a document that clearly describes the role of ICANN staff vis-à-vis the ICANN Board and the ICANN community. This document should include a general description of the powers vested in ICANN staff by the ICANN Board of Directors that need, and do not need, approval of the ICANN Board of Directors. *4-8 page document* - *Specifies roles of Staff, Board, Community* - *Staff* - *Board* - *Community* - *Specifies relationships between them* - *Staff<->Board* - *Staff<->Community* - *Board<->Community (descriptive only)* - *Describes any proposed Changes / Clarifications * - *Describes any activities that should be started/continued/stopped* - *Recommendations* Thanks in advance for your thoughts, Jordan *-- * Jordan Carter Chief Executive *InternetNZ * +64-4-495-2118 (office) | +64-21-442-649 (mob) | Skype: jordancarter jordan(a)InternetNZ.net.nz | www.InternetNZ.nz *A better world through a better Internet*

1 0

Fwd: ICANN Responses to Staff Accountability Questions
by Jordan Carter Dec. 21, 2016

Dec. 21, 2016

Hi all Replies to questions received today from ICANN. best Jordan ---------- Forwarded message ---------- From: Karen Mulberry <karen.mulberry(a)icann.org> Date: 22 December 2016 at 08:35 Subject: ICANN Responses to Staff Accountability Questions To: avri doria <avri(a)acm.org>, Jordan Carter <jordan(a)internetnz.net.nz> Cc: León Felipe Sánchez Ambía <leonfelipe(a)sanchez.mx>, Mathieu Weill < mathieu.weill(a)afnic.fr>, Thomas Rickert <rickert(a)anwaelte.de>, ACCT-Staff < acct-staff(a)icann.org> Attached is the response from ICANN.org to the questions that were submitted by the WS2 Staff Accountability Subgroup. *Karen Mulberry* Director, Multistakeholder Strategy and Strategic Initiatives (MSSI) *ICANN* 12025 Waterfront Dr., Suite 300 Los Angeles, CA 90094 Phone: +1 424 353 9745 <+1%20424-353-9745> -- Jordan Carter Chief Executive *InternetNZ * +64-4-495-2118 (office) | +64-21-442-649 (mob) | Skype: jordancarter jordan(a)InternetNZ.net.nz | www.InternetNZ.nz *A better world through a better Internet*

1 0

Notes, recordings, transcript for WS2 Staff Accountability Subgroup Meeting #6_ 15 December 2016
by MSSI Secretariat Dec. 15, 2016

Dec. 15, 2016

Hello all, The notes, recordings and transcripts for CCWG Accountability WS2 Staff Accountability Subgroup Meeting #6 – 15 December 2016 will be available here: https://community.icann.org/x/GJTDAw A copy of the notes may be found below. Thank you. With kind regards, Brenda Brewer, Projects & Operations Assistant Multistakeholder Strategy & Strategic Initiatives (MSSI) Internet Corporation for Assigned Names and Numbers (ICANN) Notes: (including relevant portions of the chat) 1. Intro, agenda review, SOI check Avri Doria: Proposed agenda - accepted. SOI check - no changes. Still awaiting documents from staff as agreed in Hyderabad. 2. Review of 'proposed next steps" Avri Doria: Presentation of Proposed Next Steps document. JC and I have advised the co-chairs that we will now be on track 2 (longer track). Discussion of 2 documents A and B. George Sadowsky: Issue of Board relationship of the Board with staff and the community is beyond the scope of this group (descriptive only instead of prescriptive). Avri Doria: Agree - if we ever notice anything in this area we would note it without making a recommendations. Klaus Stoll: good plan as long as we do not see this outline as absolute - will be glad to participate. Avri Doria: JC will be the pen holder on document A. There may be others. On to document B which I will initially hold the pen on. Description of B - expected to be a longer document - maybe 20 pages - any comments? George Sadowsky: Not all of the CCWG-Accountability? AD - from the WS1 recommendation but we are delegated by the CCWG to do this. GS also ICANN org and ICANN Board. AD - again but can add a footnote. Avri Doria: any other comments? (none). Seems acceptable. Next questions - Specifications? (no comment). Need volunteers for the documents. Review of schedule going forward - there are no additional calls this year and resume 5 January - description of schedule/plan in document. We need to get the draft done over the holidays and early January. Comments? (none). Who is volunteering? Klaus Stoll: These documents will be based on existing documents - have we captured all of these in one place to facilitate our drafting? Avri Doria: As noted earlier we are still waiting on staff to provide those - but we have to move ahead with what we have given the schedules. Klaus Stoll: Should ask staff to expedite - this is very important. Georgee Sadowsky: Support what Klaus is saying. Karen Mulberry: I have been told that it is being worked on and that it should be sent soon Pam Little: Can we ask Staff to send whatever they have now? Pam Little: Instead of waiting for everything. Karen Mulberry: Sorry, best i can do Karen Mulberry: Its my understanding that they are responding to all questions Avri Doria: Still looking for contributors to the documents. Ideally need a core group of 3 or 4 writers per document (none except KS). Alan Greenberg: I will put time into reviewing once something is drafted, but volunteering to do the work is less realistic. Avri Doria: AOB? (none0 Document B can be found at https://docs.google.com/document/d/1UnkJuukv0px-CfIDgLrjdDZa2CpBvSahPvAXdYY… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> Adjourned.

2 1

Agenda for meeting 15 Dec 1300 UTC
by avri doria Dec. 15, 2016

Dec. 15, 2016

Agenda 15 Dec 2016* * Intro: agenda review, attendance, SOI check *Review of “proposed next steps o Volunteers for Docs A & B PDF attached for agenda and proposed steps doc <https://docs.google.com/document/d/1Ftd-Ps_qF46pf_iXf5foGjdUfCq64-St_43inFe…>” --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 0