<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hi all, </div><div class=""><br class=""></div><div class="">Here are the notes from this afternoon’s call. </div><div class=""><br class=""></div><div class="">Cheers</div><div class=""><br class=""></div><div class="">Antony</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">###</div><b class=""><div class=""><b class=""><br class=""></b></div>RIPE Accountability Task Force Meeting Notes<br class=""></b><br class="">2 October 2017<br class=""><br class="">Attendees:<br class="">Athina Fragkouli, Antony Gollan, Alexander Isavnin, Peter Koch, William Sylvester<br class=""><br class=""><b class="">1. Welcome, finalise agenda, adopt minutes<br class="">2. Review of open action items <br class="">3. Review from face-to-face meeting and preparations for Dubai (pre-meeting email & presentation)</b><br class=""><br class=""><br class=""><b class="">1. Welcome, finalise agenda, adopt minutes<br class=""></b><br class="">There were no changes to the agenda. Antony apologised for not getting the minutes from the face-to-face meeting out sooner, he said he would get these sent after the call.<br class=""><br class=""><b class="">2. Review of open action items<br class=""></b><br class="">Antony said that while he hadn't sent around the minutes, he had an updated list of action items, including those from the face-to-face meeting.<br class=""><br class=""><b class="">20170907-2: RIPE NCC to research and report back on what governance obligations are there for the RIPE NCC to abide by community policy.<br class=""></b><br class="">William said that he had discussed this with Paul recently at the ARIN Meeting, and he said he was looking into this.<br class=""><br class=""><b class="">20170907-3: the task force to clarify with the community: Is public benefit a core aspirational factor, or are RIPE community members working for their own benefit? (There is also likely some research that can be done into RIPE Documents here as well).<br class=""></b><br class="">Antony said this was something that the group had discussed during their face-to-face – whether RIPE was about the narrow self-interest of network operators, or whether there were other societal considerations. They could look at including this question in the presentation William gave at RIPE 75, or perhaps this in their email to the community before the meeting. Or perhaps it was something to include in their report as needing further community discussion.<br class=""><br class=""><b class="">20170907-4: Malcolm to work draft a definition of consensus/rough consensus that can be presented to the community.<br class=""></b><br class="">Antony said this was with Malcolm.<br class=""><br class=""><b class="">20170703-2: RIPE NCC to look for past statements/presentations that might be relevant to the TF’s work.<br class=""></b><br class="">Antony said that they still needed to look at this, however, he had reviewed all of the RIPE mailing list and hadn't found anything that was relevant, which was surprising. <br class=""><br class=""><b class="">20170509-1: TF Chairs to put together work plan after the meeting.<br class=""></b><br class=""><b class="">20170306-1: RIPE NCC to further develop accountability mapping document with task force input.<br class=""></b><br class=""><b class="">20170306-2: Task force members to review and comment on accountability mapping document.<br class=""></b><br class="">Antony said these three items were placeholders from earlier calls. However, he had updated the accountability mapping document with the task force's feedback at the face-to-face meeting and would send this soon.<br class=""><br class="">Athina noted they also had an action item for Malcolm to finalise the mind-map they had discussed at their face-to-face meeting as a supporting document.<br class=""><br class=""><b class="">3. Review from face-to-face meeting and preparations for Dubai (pre-meeting email & presentation)<br class=""></b><br class="">Alexander suggested that as there weren’t many people on the call, they should wait until the minutes and other documents had been sent, and then have another call on Monday next week.<br class=""><br class="">William said they could also find an updated link for Malcom's mind map and share that with the group. He said the work they needed to focus on over the next couple of weeks was preparation for the Dubai meeting and anything they needed to share with the community.<br class=""><br class="">Alexander said they should establish which task force members would be attending RIPE 75. He suggested they meet the day before the plenary session to finalise the presentation.<br class=""><br class="">Antony said he had spoken with their conference coordinator and if they wanted to have a full catered lunch like at RIPE 74, they would need to have their meeting during either the Sunday or Thursday lunchtime (the first and last days of the meeting). If they were happy with something simple like arrange some sandwiches in a board room, then there were plenty of options.<br class=""><br class="">Alexander said he was talking about an informal meeting with no special requirements. But if they could do it during lunch that might also be good. He suggested they put together a list of when people would be arriving.<br class=""><br class="">William asked when their plenary presentation was scheduled for.<br class=""><br class="">Athina said it was on Monday at 16:00.<br class=""><br class="">William asked if everyone would be okay if they met on Sunday and had a normal lunch and just grabbed a side-room. He said they could put this on the mailing list and figure it out. He added that another meeting after the presentation would be useful, to go over the community feedback received.<div class=""><br class=""><br class=""><b class="">Action Items<br class=""><br class="">20170907-1: Malcolm to finalise the mind-map as a supporting document for the task force. [Added after the call].<br class=""><br class=""></b><div class=""><b class="">20170907-2: RIPE NCC to research and report back on what governance obligations are there for the RIPE NCC to abide by community policy. <br class=""><br class=""></b><div class=""><b class="">20170907-3: the task force to clarify with the community: Is public benefit a core aspirational factor, or are RIPE community members working for their own benefit? (There is also likely some research that can be done into RIPE Documents here as well).<br class=""><br class=""></b><div class=""><b class="">20170907-4: Malcolm to work draft a definition of consensus/rough consensus that can be presented to the community.<br class=""><br class="">20170703-2: RIPE NCC to look for past statements/presentations that might be relevant to the TF’s work.<br class=""><br class="">20170509-1: TF Chairs to put together work plan after the meeting.<br class=""><br class="">20170306-1: RIPE NCC to further develop accountability mapping document with task force input.<br class=""><br class="">20170306-2: Task force members to review and comment on accountability mapping document.</b><br class=""><br class=""> <br class=""><br class=""> </div></div></div></div></body></html>