February 2017 - Accountability-Cross-Community

Notes, recordings and transcript - WS2 Ombudsman Subgroup | Meeting #11 | Monday, 24 October 2016 @ 19:00 UTC
by MSSI Secretariat Oct. 30, 2017

Oct. 30, 2017

Hello all, The notes, recordings and transcripts for CCWG Accountability WS2 Ombudsman Subgroup - Meeting #11 - 24 October 2016 @ 19:00 UTC will be available on the wiki page: https://community.icann.org/x/2xK4Aw. A copy of the notes from the meeting are available below. Thank you. Kindest 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=DQMFAw&…> ________________________________ Notes (including relevant parts of chat): 9 Participants at start of call. 1. Welcome Sebastien Bachollet: no exceptions. 2. Review of plan for Hyderabad Sebastien Bachollet: (Presentation of slides) Herb Waye: Concerned this report only represents the views of a small number of people and not the community. Sebastien Bachollet: Our work will be presented to the plenary of the CCWG-WS2 so this is not an issue. After it is accepted it will go for public comment to be accepted by the community. Herb Waye: Willing to pay for part of the evaluation, have funds and will have to do one (there may be a conflict of interest with such funding). Klaus: I am just thinking about if anybody outside the WG will actually understand the slides? Somehow I think not. We might need a more "understandable" version. Content is OK but who will understand and do we get the message across? Avri Doria: i think there will be chance to explain t to assembled crowd. In terms of staff accountability, we have included a reference to the necessity of coordinating with this group. Chris LaHatte: the slide about consent of the Ombuds is an issue Avri Doria: but the people listening will all be CCWG participants. Herb Waye Ombuds: Did this idea of consent come about as a copy of the reconsideration new process in the bylaws I wonder? Klaus: I think the cross group issue is critical now, we will need to have a mechanism in place to have the input from the other WG's Bernard Turcotte: @Klaus - the co-chairs advised on the leadership call last week that they would focus on this to ensure synchronicity between sub-groups Klaus: Great, good to know. Thanks Karen Mulberry: I am working out the details for the Review that you have asked for Cheryl Langdon-Orr: we should note that at least from the slide mentioning crossover matters the mention of Elections might be inflammatory for some CCWG Members. Sebastien Bachollet: This was one of my suggestions for our work. Herb Waye Ombuds: That idea is good Seébastien and it could be in the office but I would need to ask for funding for staff... The IOO could become a sort of ethics office Sebastien Bachollet: the evaluation will probably impact our timetable. Klaus: Ethics can never be a subject of an office but an community. Happy to discuss this at a face to face basis. Herb Waye Ombuds: Agree Klaus, two separate hats but some organizations do it as part time functions. Sbastien Bachollet: Shall we resume our calls immediately after Hyderabad. Next meeting on November 14 or 21? will check with staff AOB? (none). Adjourned.

2 1

WS2 and Ombuds, Compaints,... Offices
by Sebastien Bachollet March 16, 2017

March 16, 2017

Dear Colleagues, In different WS2 Subgroups new processes or functionalities and/or new possible problems and/or complains are arising from the work. Along with those issues the question of independence (from Staff, from Board, from part of the community…) was also discussed. The evolution of role of the ICANN Ombuds Office (IOO) is at the center of the IOO Subgroup. The new Complaints Office role is also discussed in various subgroups. How to best organize the « complaints » OfficeS need to be work out? It is the reason I send you the document attached. Your comments are welcome. If you consider the topic useful, we may need to schedule some time to discuss that during our F2F meeting in Copenhagen. Please find it attached in a doc format and in a PDF format. Do we ned a Google doc? Thanks for your consideration and your help. All the best Sébastien Bachollet For ICANN lists sebicann(a)bachollet.fr

5 6

WS2 dashboard - January (final)
by MSSI Secretariat March 7, 2017

March 7, 2017

Hi All - On behalf of the CCWG Accountability Co-Chairs, please find attached the final version of the Dashboard for the month of January 2017. Kind Regards, Yvette Guigneaux Multi-Stakeholder & Strategic Initiative Asst. ICANN - Internet Corporation for Assigned Names and Numbers Email: yvette.guigneaux(a)icann.org Cell: +1-310-460-8432 Skype: yvette.guigneaux.icann www.icann.org<http://www.icann.org>

2 1

CCWG-Accountability-WS2-TravelSupport-ICANN59Johannesburg-25June2017-Announcement and Process
by Bernard Turcotte March 1, 2017

March 1, 2017

The body of this email contains: - The announcement for Travel Funding Applications for the CCWG-Accountability-WS2 Face to Face at ICANN59 on 25 June 2017 - The CCWG-Accountability-WS2 Travel Funding Policy - The CCWG-Accountability-WS2 Travel Funding Application Form (Applications must be submitted by 23:59 UTC Sunday 19 March 2017) All, The CCWG-Accountability -WS2 has travel funding for some Members and Rapporteurs to attend the Face to Face meetings held the day prior to an ICANN meeting who do not have any other funding available to them to attend. Members are those individuals that are specifically appointed by the chartering SO/ACs to the CCWG-Accountability - the list of Members can be found at https://community.icann.org/pages/viewpage.action?pageId=59640780 . Rapporteurs are those listed as such on the CCWG-Accountability-WS2 Wiki for specific sub-groups located at https://community.icann.org/di splay/WEIA/WS2+SubGroup+Topics. Please see the attached policy for details regarding this funding. If you are not a Member or a Rapporteur, please do not apply as there is a very limited number of seats available. The next Face to Face meeting of the CCWG-accountability will be held on 25 June 2017 in conjunction with ICANN 59 in Johannesburg South Africa. Those Members and Rapporteurs wishing to be considered for travel funding should fill out the attached form and submit it by 23:59 UTC Sunday 19 March 2017 to Acct-Staff(a)icann.org. The funding is for the Face- to- Face meeting of the CCWG-Accountability WS2 , which can include airfare, hotel and a per-diem allocation for meals for attending the Face to Face meeting only (and not the full ICANN meeting). However, in analyzing the requests the CCWG-Accountability-WS2 Co-Chairs will consider requests for partial funding (such as only an additional day of hotel and per diem to attend the Face to Face meeting) in order to maximize participation. As such Members are encouraged to only apply for what they need to allow for funding as many Members and Rapporteurs as possible. The final decisions on travel funding will be made by the CCWG-Accountability-WS2 Co-Chairs and published on the CCWG-Accountability WS2 wiki at https://community.icann.org/display/WEIA/Travel+Support within 7 days of the application period closing (a confirmation of the posting will be sent to the CCWG email list). Those being supported will then be contacted by ICANN Travel using the standard ICANN travel funding process to arrange details. Should you have any questions please do not hesitate to contact the CCWG-Accountability support staff at Acct-Staff(a)icann.org . Bernard Turcotte ICANN Staff Support to the CCWG-Accountability-WS2 *Updated Process for Expressions of Interest requesting CCWG Travel Support (December 2016)* The current budgeted amount to support the work of CCWG WS2 members allocates travel support (travel, hotel and per diem) for an amount equivalent to 20 appointed members or rapporteurs to attend only a CCWG face-to-face meeting. The Co-Chairs have the authority to re-allocate this amount – this could include supporting requests for partial funding to allow them to maximize the number of members attending (e.g. the requestor may ask for any or all of the following: airfare, and/or hotel and/or per diem) or to extend the stay of some key participants. You are eligible for travel support from the CCWG if you are an officially appointed member of WS2 from a chartering SO or AC or if you are officially listed as a Rapporteur or Co-Rapporteur on the CCWG-Accountability-WS2 Wiki located at https://community.icann.org/display/WEIA/WS2+-+Enhancing+ICA NN+Accountability+Home . Travel support arrangements will follow Constituency Travel Guidelines located at: https://community.icann.org/display/trvlconstit/Constituency +Travel+Home The CCWG travel support slots will be allocated in priority as follows: CCWG-Accountability Co-Chairs – 3 slots (or equivalent amount) CCWG-Accountability Chartering Organization Appointed Members CCWG-Accountability Rapporteurs CCWG appointed Members and Rapporteurs requesting consideration by the Co-Chairs for travel support to attend a face-to-face meeting must complete and submit the travel request form by the stipulated deadline in order to be considered for funding. NOTE: In evaluating the applications for travel funding the Co-Chairs will consider applicant's attendance to CCWG meetings and their contributions to the ongoing work as well as the availability of alternate funding to the applicant. CCWG Staff support will send out an announcement regarding the application for travel support and deadline for application submissions as soon as a face-to-face meeting has been approved. Applications to request travel support are located at: https://community.icann.org/di splay/WEIA/Travel+Support Completed forms can be sent to Acct-Staff(a)icann.org <Acct-Staff(a)icann.org> for submission to the Co-Chairs for review and approval. All applicants for CCWG WS2 travel support will be posted on the CCWG WS2 wiki under Travel Support. Names will be listed REQUESTED and once approved will be listed as APPROVED for travel support including the type of support that is approved. The Co-Chairs will review the applications received, including the requests for partial support, and determine the list of approved CCWG members who will receive travel funding. The CCWG approved travel support list will be submitted to ICANN Constituency Travel for processing according to community travel guidelines. The approved list of funded CCWG members will be posted on the WS2 wiki at https://community.icann.org/display/WEIA/Travel+Suppor <https://community.icann.org/display/WEIA/Travel+Support>*t* =========================================================== CCWG-Accountability-WS2 Supported Travel Request Form You are eligible for travel support from the CCWG-Accountability only if you are an officially appointed member of WS2 from a chartering SO or AC or if you are an officially listed Rapporteur for a WS2 sub-group. The CCWG-Accountability-WS2 Co-Chairs will review the applications received, including the requests for partial support, and determine the list of approved CCWG members who will receive travel funding. The CCWG-Accountability-WS2 approved travel support list will be submitted to ICANN Constituency Travel for processing according to community travel guidelines Travel support arrangements will follow Constituency travel guidelines located at: https://community.icann.org/display/trvlconstit/Constituency +Travel+Home CCWG-Accountability-WS2 appointed Members or rapporteurs requesting consideration by the Co-Chairs for travel support to attend a face-to-face meeting must complete and submit the travel request form by the stipulated deadline in order to be considered for funding. Applicant Identification ======================== Name: Chartering Org or Rapporteur for which WS2 Group: Email address: Date of Request: Other sources of support ======================== Please indicate if you are receiving travel support from another organization to attend the ICANN meeting I am receiving support from another organization (yes or no): If you are not receiving support from another organization, please proceed to “Support requested from CCWG-Accountability”. If you are receiving support, please provide the information requested below: Name of the Organization(s) providing the support: Indicate type of support and how many days the support is provided (BY FUNDING ORGANIZATION): Airfare (yes or no): Hotel (# days): Per Diem (# days): Support requested from CCWG-Accountability =========================================== Please indicate the type of travel support (including the number of days) you are seeking from the CCWG for WS2 - please remember this is only for attending the Face to Face meeting and is not for the entire ICANN meeting. Airfare (yes or no): Hotel (# days): Per Diem (# days):

17 28

Notes, recordings and transcript for WS2 Human Rights Subgroup Meeting # 22 | 28 February 2017
by MSSI Secretariat Feb. 28, 2017

Feb. 28, 2017

Hello all, Please see the notes, recordings, and transcript for the CCWG Accountability WS2 Human Rights Subgroup Meeting #22 here; https://community.icann.org/x/K6vRAw 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) [id:image001.png@01D28DF5.EF27C2B0] Notes (including relevant portions of the chat): 14 Participants at start of call 1. Administrivia - Roll call, absentees, SoIs, etc Apologies: Jorge Cancio, Herb Waye, Mathew Shears Niels ten Oever - Audio only? (AAS). Any update to SOIs (none). May of been premature to call this a first reading but if we agree today it would allow us to have a meeting next week to have a second reading to submit to the plenary. David McAuley (RySG): are we meeting next week? Paul McGrady: Not everyone is going to make it to the face to face due to the way the meeting schedule turned out Kavouss Arasteh: There is no Plenary before Copenhagen Anne Aikman-Scalese: Next week Tuesday meeting would be hard for those travelling from far. Tatiana Tropina: I put red tick as while I think it would be good, I am very much against excluding those who can't make this call next week Greg Shatan: That will also be too late to submit a document for the Plenary. Tatiana Tropina: Greg, yes. Kavous Arasteh: There is no meeting scheduled for next week and my points have not been addressed. Niels ten Oever - temperature check to have a meeting next week (no support). Ok will advise Co-Chairs that we will not have a document for the face to face. Tatiana Tropina: this is of course sad but we can't compromise on the quality and inclusion :-) Niels ten Oever - should we look at the JC document or my version? Kavouss Arasteh - I have also sent a revised version why is not being considered? Niels ten Oever - KA your comments have already been integrated in the document. Anne Aikman-Scalese - I have not seen it so if we use it can you be specific. 2. First reading (of two) of the Considerations document prepared by the drafting team Tatian Tropina - (reading document). Paul McGrady - could we deal with one para at a time. On para 1 seems inconsistent. No definition of DECLERATION. Now we have OTHER INSTRUMENTS which are also undefined. Then we get into COVENANTS which is also undefined. We need to clean this up and call it one thing consistently throughout the document. Greg Shatan: Maybe we should use "conventions and other instruments" as used in the "consideration". Tatian Tropina - PM thanks this is very useful. If we use the language from Annex 12 would this meet the requirement. Paul McGrady - The definition can be broad we use anything we want and then use it consistently it will be fine. Tatiana Tropina: But for the substance we use the "HR conventions or other instruments" as in the Annex 12 Niels ten Oever: But for interpretation we might also use UDHR, no? Kavouss Arasteh - Agree with PM but still have issues with the first para given agreements are one thing but declarations are something else - you cannot mix these things as states have not agreed to all these things - maybe just drop the first sentence. Tatiana Tropina: that this means declarations, conventions, Bills, etc widely agreed internationally avri doria: Since none of it is binding on ICANN, it really does not matter who signed or implemented. Paul McGrady: Human Rights conventions, agreements, declarations, conventions, covenants, and instruments (collectively "Human Rights Documents") Paul McGrady: +1 Avri Tatiana Tropina: Paul, inserting this in the google doc - thanks much much! Niels ten Oever - good suggestions for the drafting team. Greg Shatan: "Documents" seems a bit too generic -- I would prefer that we use "conventions and other instruments" each time. Markus Kummer: "internationally agreed human rights instruments" ? Tatiana Tropina: Greg, that's what I suggested while speaking, but we can fine tune for the next call avri doria: i like conventions and other instruments as well Paul McGrady: (collectively "Human Rights Cannon") Tatiana Tropina: we have to follow the language of annex 12 but still implement Paul's corrections Niels ten Oever: "States are parties to these document" Markus Kummer: instrument is the usual overarching term used in international law Greg Shatan - Need to reflect that whatever we define is aimed at States. Tatiana Tropina - lets put all the comments in the Googledoc and the lawyer it up to make consistent. Kavouss Arasteh - You cannot use INSTRUMENTS sometimes this is more than conventions or not. Still suggest we drop the first part. Avri Doria - Irrelevant how many states have agreed to these things does not matter since they are not applicable to ICANN. Greg Shatan: +1 Avri. Paul McGrady: +1 Avri Tatiana Tropina: + 1 Avri - very much to the point. Janet Shih Hajek: Instead of Human Rights conventions are agreements between states,” why not just start with “ICANN, as a non-state private party, is not a party to any Human Rights convention or other human rights instrument. However, ICANN could refer to any of the widely adopted Human Rights conventions and other instruments . . . “ Tatiana Tropina: there is nothing all countries Kavouss Arasteh: Disagree with AD, agreed with states causes problem need to fix. Tatiana Tropina - (reading next section). Not happy with JC proposed language but can live with it. David McAuley (RySG): Agree w/Tatiana on this Kavouss Arasteh - do not agree with JC language. Greg Shatan - KA proposal not much different and we can replace CONSENSUS with AGREEMENT. Tatiana Tropina: yes this should be fine. It makes no big difference for me, but if it's very critical for someone let's replace Paul McGrady - do not understand how the second and third paras fit together. I think we were considering if they were binding and para should say it is not. Para 3 just says what we say in para 1 but only about 1 thing. Para 2 needs to be stronger and there does not seem to be a reason for para. Tatiana Tropina - the problem is because of the definintion of UN guidance on HR for Business. As to para 2 the recommendation has been watered down to have a compromise because some people still think they should be binding. David McAuley (RySG): I think paragraph 2 is fine and accurate David McAuley (RySG): And agree w/Tatiana that the language was crafted with compromise in mind Paul McGrady: @Tatiana - thank you. That discussion is helpful and explains why we need paragraph 3. Kavouss Arasteh - tend to agree with PM. If you want to maintain para 3 it should be before para 2. But do not favour keeping para 3. If kept should be reworded to show there is not consensus on the matter. Greg Shatan: Paras 2 and 3 deal with interpretation and implementation of the Guiding Principles, respectively. Paul McGrady: Once we ake it clear that Guiding Principles are not part of the Human Rights Documents contemplated in paragraph 1, I think paragraph 3 makes sense now. avri doria: para 3 is important and it is the saving grace of the section. Paul McGrady: @Avri - :) Anne Aikman-Scalese - We need to be clear for the Board on the Ruggie principles other it will be a recipe for trouble. Taiana Tropina - 3rd para was a compromise from the last version. Would be happy not to have it but it would probably cause an issue so we will keep it and fix it. David McAuley (RySG): The interpretation of the bylaw cannot undo the bylaw – it will be binding if it is international recognized under applicable law – that may differ from place to place Greg Shatan - Have looked up HR Instruments do not include Ruggie and would suggest that para 2 and 3 are out of scope. avri doria: and time to time David McAuley (RySG): agreed, @Avri Niels ten Oever: UNGPs are a softlaw instrument Tatiana Tropina: oooooooohhhh that's too radical even for me. Kavouss Arasteh - if we drop para 3 then we can drop 2 also. Guiding cannot be binding. Tatiana Tropina: Wow, I find myself in disagreement with Greg, finally! :-) Niels ten Oever: https://en.wikipedia.org/wiki/United_Nations_Guiding_Principles_on_Business… Niels ten Oever: And Kavouss and Greg aligned avri doria: deletion of Ruggie comes close to some of our die in the ditch regions avri doria: a UN agreed doc is in scope! Paul McGrady: To say nothing about it after all this work on it, doesn't seem productive. Greg, can you find another place in this document to address the Guiding Principles? David McAuley (RySG): We should address Ruggie as not reaching consensus - we spent considerabl;e time on it Tatiana Tropina - As AD has stated Ruggie principles will be die in the ditch for some. It may be best to actually deal with this in the document because it would create ambiguity going forward Niels ten Oever: Then Paul asked a question, we explained, and now everything is up in the air Niels ten Oever: am a bit surprised avri doria: i think the 3 para is the right solution avri doria: there was a sophistic twist on the matter of scope. but denying scope to an UN aggreed document in scope abuse. David McAuley (RySG): I agree w/Niels on this - the language was carefully put together Greg Shatan - My suggestion to remove the paras has nothing to do with Ruggie but rather simply if it is in scope or not. Tatiana Tropina: I think it should be treated with caution instead of leaving the things blank. remember the jurisdiction debate. Niels ten Oever: Ruggie is an instrument - there is no doubt about that Tatiana Tropina: David, yes. And the Ruggie principles is like elephants in the room Tatiana Tropina: we don't have to redefine terms instruments but we have to note that they are not instruments. Yes, seems like a good suggestion avri doria: here we go again. Tatiana Tropina: Agree with David's last comment Tatiana Tropina: We can't ignore Ruggie, this will be reopened at one point and we have to deliver. Paul McGrady: "could be" is not "must be" Kavouss Arasteh - We do not use Ruggie to interpret the Bylaw - we can use it to interpret Human Rights. What is the definition of a HR Core Value? Paul McGrady: Let's add the caveat and save the hard work we have done on dealing with Ruggie. Tatiana Tropina: Oh I would be happy with deleting the para 3 but many will die in the ditch for this Greg Shatan: We are calling it the "Human Rights Core Value." Greg Shatan: Core Value is singular and refers only to that Core Value that refers to human rights. Tatiana Tropina: Paul, this seems like the best solution. And yes, the text has to be clarified. As I said already in all the fights about the substance we are sometimes paying more attention to compromise than the quality and clarity of the explanation Greg Shatan: Core Values is plural and would refer to all the Core Values. Kavouss Arasteh: Greg, it is wrong to call it Core Value Tatiana Tropina: Paul has been our reality check - thanks so much Paul. Greg Shatan: That is exactly what it is. Kavouss Arasteh: Why you wish to generalize it to cover all core values Tatiana Tropina: Avri, we have to mention them. I agree - being an opponent of Ruggie. Paul McGrady: We need to tell the plenary about the work we did on this. We can't just leave it blank... Avri Doria - going at this again. Trying to use the definition to get Ruggie out is not valid. As such disagree with this. Tatiana Tropina: Avri, yes. The para is carefully crafted consensus and we have to leave it there (may be fine tune) David McAuley (RySG): Bylaw 27.2(a) says: The Core Value set forth in Section 1.2(b)(viii) shall have no force or effect unless and until a framework of interpretation for human rights ("FOI-HR") ... Tatiana Tropina: I do dislike saying this because I was against the para 3, but I think we have to take this into consideration Niels ten Oever - should go back to the drafting group. Adjourned.

1 0

CCWG-Accountability -WS2 Calendar for March 2017
by Bernard Turcotte Feb. 28, 2017

Feb. 28, 2017

All, Given this is the last day of February here is the current status of the March CCWG-Accountability -WS2 Calendar. This is a CURRENT status and we would encourage you to check the master calendar located at: https://docs.google.com/spreadsheets/d/1qwr41BesyvDQBnqF_gBQlHfJlRkOGrjHa26… Bernard Turcotte ICANN Staff Support to the CCWG-Accountability-WS2 Day of week 05:00 UTC 13:00 UTC 19:00 UTC Notes 1 Wednesday Jurisdiction Guidelines for G.Faith 2 Thursday SOAC Acct IRP-IOT HOLD Staff Acct 3 Friday Documents due for March 10 Plenary 4 Saturday 5 Sunday 6 Monday Obudsman (BT) PCST report publication 7 Tuesday 8 Wednesday Travel day 9 Thursday Travel day Dashboard publication 10 Friday CCWG-Accountability Face to Face Plenary 11 Saturday ICANN58 - Copenhagen 12 Sunday ICANN58 - Copenhagen Note: Time change in North American +1 hour 13 Monday ICANN58 - Copenhagen 14 Tuesday ICANN58 - Copenhagen 15 Wednesday ICANN58 - Copenhagen 16 Thursday ICANN58 - Copenhagen 17 Friday Travel day 18 Saturday Travel day 19 Sunday End of Travel Funding Application for ICANN 59 20 Monday Obudsman (BT) 21 Tuesday 22 Wednesday Guidelines for G. Faith BT - co-chair/staff meeting 1500 - Documents due for March 29 Plenary 23 Thursday SOAC Acct IOT 24 Friday 25 Saturday 26 Sunday 27 Monday Obudsman (BT) 28 Tuesday Travel funding confirmations due to ICANN travel 29 Wednesday Plenary Guidelines for G. Faith Report on IOT Public Consultation due. 30 Thursday Staff Acct SOAC Acct IOT Dashboard inputs from rapporteurs due 31 Friday

1 0

Notes, recordings, transcript for WS2 Staff Accountability Subgroup Meeting #10_ 28 February 2017
by MSSI Secretariat Feb. 28, 2017

Feb. 28, 2017

Hello all, The notes, recordings and transcripts for CCWG Accountability WS2 Staff Accountability Subgroup Meeting #10 – 28 February 2017 will be available here: https://community.icann.org/x/Y6bRAw A copy of the notes may be found below. Thank you. Kind Regards, Yvette Guigneaux Multi-Stakeholder & Strategic Initiative Asst. ICANN – Internet Corporation for Assigned Names and Numbers Email: yvette.guigneaux(a)icann.org Cell: +1-310-460-8432 Skype: yvette.guigneaux.icann www.icann.org<http://www.icann.org> ________________________________ Notes Staff Accountability Meeting #10 28 February 2017 @ 05:00 UTC Agenda: 1. Intro: agenda review, attendance, SOI check 2. Second reading document A version 1.5. Jordan is rapporteur on this document If there is time after completing Document A for submission to Plenary (note the documents are open for comment and suggested edits. Contributions to content invited): 3. Discussion / seeking feedback on Draft Document B v1.2 Avri is rapporteur on this document 4. Continuing Discussion of Responses to Staff questions (if time) 5. Schedule check 6. AOB Notes (including relevant portions of the chat): 7 Participants at start of call Avri Doria - Usual administrivia - Pam Little - updated SOI, now representing Alibaba. Jordan Carter - (review of structure of document). Any comments? George Sadowsky - Difficult comments to make given my liaison status - My sense is of real concern because the document to my mind misses the mark completely. What problems are trying to be solved here - seems most clear. Limited Board feedback is there is no understanding what is going. You could cut out 80% of the document without losing much - the two main recommendations are F and J which seems to make sense. the document provides a lot of background, too much in many cases and some incorrect. Does this document really address the problem (statement from Rec. 12). Greg Shatan: I have the same general concerns as George has expressed. Jordan Carter - Agree just focusing on the problem would be better but this is not the requirement from Rec. 12. Greg Shatan - Do not think the suggestions made by GS are incoherent with Rec. 12. there may not be a need for a "history of the world" approach. Do not think this document is what was required by WS1. Jordan Carter - The italicized text is copy/paste from rec. 12 which says we should develop this in cooperation with staff - however there does not seem to be an operational model, given our attempts, that would allow us to do this. In part this is why I think this should go to the Plenary so we can get an understanding of what we should be doing. Avri Doria - Agree with JC comments and should be repeated to the plenary so we can find out if we are meeting the requirements of rec. 12. There does seem to be an (elephant) in the room but it is uncertain. avri doria: i actually did not say an elephant in the room. i said something large covered in a blanket walking through the room, but we don't know exactly what it is. Might be a rhinocerous for all I know. George Sadowsky - The elephant in the room seems to be people think that staff are crossing over the line to policy implementation and there is no place where the community can get that addressed. Jordan Carter - what I thought is that staff would provide a paper in June that would provide the information that was requested - but that was not the case. As a group of volunteers getting replies every two months does not seem to be very functional - GS How do we fix this so we can work with ICANN? George Sadowsky - My experience with staff is different - do not think staff is particularly hostile to this effort - and I apologize for not being there earlier in the process and am willing to help however I can at this point. Avri Doria - really think we should include this discussion in the document and send it to the plenary. I have made numerous requests to get staff participation to little avail and am not optimistic of participation going forward. Jordan Carter - Agree with AD - we need plenary input. Have no ownership issues with the document and have no issues with staff writing some of this. Avri Doria: Not perfectly comfortable with this approach. Need to send this document along with the cover note so we can have the wider discussion. Jordan Carter 2: I'm relaxed about including it, because if people don't read it, they won't have a sense of what is being pushed against or for George Sadowsky: Nothing wrong with that, Avri. Greg Shatan - In asking to frame this we have to consider if we want to ask the plenary to read 19 pages. Avri Doria - pertinent part of document is now only 11 pages. Jordan Carter - Agree this needs Framing to go to the plenary and that this conversation has helped verbalize some of my discomfort. We are not looking for any editorial comments from the Plenary. avri doria: we need to be careful not to whitewash in our zeal to be comfortable Greg Shatan: One last working note: we may want to let Board members generally know that they can participate on an equal footing with other participants, rather than feeling like they must only "liaise." Avri Doria – I have made that clear to GS a number of times. Jordan Carter - will draft a one page cover framing what we are asking the plenary and we will finish this on the Thursday meeting. George Sadowsky - More than willing to put in comments in the Googledoc but there seems to be too many comments. Avri Doria - that should work. Ok we have a plan. JC will produce a document in the next few hours which will be considered on our Thursday call. In the meantime people can finish cleaning up as much as they want. Jordan Carter 2: i'll circulate that cover note to the group in about 12h, or about 15h George Sadowsky: I will put all my comments on the GooglerDocs within 24 hours. Avri Doria - The specificity of the recommendations will be in the B document but needs the input from the A document. Any AOB (none). Adjourned.

1 0

[CCWG-ACCT] CCWG-Accountability-WS2-TravelSupport-ICANN59Johannesburg-25June2017 Applications
by Bernard Turcotte Feb. 27, 2017

Feb. 27, 2017

All Just another friendly reminder that many of us will start travelling to Copenhagen next week and that the application period for travel funding to ICANN 59 closes 23:59UTC Sunday 19 March following the close of ICANN 58. The travel application can be found at the end of the announcement email and has been copied at the end of this email for your convenience (reminder this is ONLY for Members or Rapporteurs - if you are uncertain please read the announcement). Details can also be found on the WS2 wiki at: https://community.icann.org/display/WEIA/Travel+Support+ICANN59 Bernard Turcotte Staff Support to the CCWG-Accountability-WS2 ========================================================== CCWG-Accountability-WS2 Supported Travel Request Form You are eligible for travel support from the CCWG-Accountability only if you are an officially appointed member of WS2 from a chartering SO or AC or if you are an officially listed Rapporteur for a WS2 sub-group. The CCWG-Accountability-WS2 Co-Chairs will review the applications received, including the requests for partial support, and determine the list of approved CCWG members who will receive travel funding. The CCWG-Accountability-WS2 approved travel support list will be submitted to ICANN Constituency Travel for processing according to community travel guidelines Travel support arrangements will follow Constituency travel guidelines located at:https://community.icann.org/display/trvlconstit/Constituency +Travel+Home CCWG-Accountability-WS2 appointed Members or rapporteurs requesting consideration by the Co-Chairs for travel support to attend a face-to-face meeting must complete and submit the travel request form by the stipulated deadline in order to be considered for funding. Applicant Identification ======================== Name: Chartering Org or Rapporteur for which WS2 Group: Email address: Date of Request: Other sources of support ======================== Please indicate if you are receiving travel support from another organization to attend the ICANN meeting I am receiving support from another organization (yes or no): If you are not receiving support from another organization, please proceed to“Support requested from CCWG-Accountability”. If you are receiving support, please provide the information requested below: Name of the Organization(s) providing the support: Indicate type of support and how many days the support is provided (BY FUNDING ORGANIZATION): Airfare (yes or no): Hotel (# days): Per Diem (# days): Support requested from CCWG-Accountability =========================================== Please indicate the type of travel support (including the number of days) you are seeking from the CCWG for WS2 - please remember this is only for attending the Face to Face meeting and is not for the entire ICANN meeting. Airfare (yes or no): Hotel (# days): Per Diem (# days):

1 0

CCWG-Accountability-WS2-Meeting Documents for Face to Face in Copenhagen
by Bernard Turcotte Feb. 27, 2017

Feb. 27, 2017

All, This is simply a friendly reminder to the sub-groups that if they wish material to be considered by the Plenary at its face to face meeting in Copenhagen on 10 March that those materials have to be sent to Staff or the plenary list by 23:59UTC Friday 3 March. Bernard Turcotte ICANN Staff Support to the CCWG-Accountability WS2

1 0

CCWG-Accountability Jurisdiction Subgroup Questions for ICANN Legal
by Greg Shatan Feb. 24, 2017

Feb. 24, 2017

Co-Chairs and Fellow Participants, Attached for the appropriate review and submission to ICANN Legal are several questions from the Jurisdiction Subgroup. Please let us know if there are any questions or concern before these are sent to ICANN Legal. When these are submitted to ICANN Legal, please ask for an estimate of the time to return answers, and advise them that they may respond on a rolling basis, if that will allow us to receive certain answers more quickly. For convenience, a link to a Google Doc version is also included: https://docs.google.com/document/d/1HslgBieiTl2LNT1CXNct7ZS1Qi5lZy3r8Y42CVz… Thank you. Greg Shatan *Rapporteur* *Greg Shatan *C: 917-816-6428 S: gsshatan Phone-to-Skype: 646-845-9428 gregshatanipc(a)gmail.com

2 1