<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Dear all,<div class=""><br class=""></div><div class="">We had our 3rd Meeting on 2 Dec 2019, Monday. </div><div class=""><br class=""></div><div class="">Below you can find information about this meeting, the actions and pointers for further follow-up:</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Agendas, the high-level notes and the recordings of the meetings are all in the shared folder (<a href="https://drive.google.com/drive/u/2/folders/1wz08_g6NtqkiBkOYUhekLwVJYwZkCnBv" class="">https://drive.google.com/drive/u/2/folders/1wz08_g6NtqkiBkOYUhekLwVJYwZkCnBv</a>).</div><div class=""> </div><div class=""><br class=""><div class="">Highlights of the meeting were:<br class=""></div><div class=""><br class=""></div><div class=""><ul class=""><li class="">Agreement reached that the current wording of the scope statement is good.</li><ul class=""><li class="">6 December deadline stands to conclude it. </li><li class="">After 6 December, scope will be published at the Data Ownership Task Force website. </li><li class=""><b class="">Action on all TF members: </b>Go through the <a href="https://docs.google.com/document/d/1su38Vko9_3-aoo_LYvKckbK6PNVTwfLgzbYQBN3bv7c/edit" class="">scope doc</a> . If you you think the current wording does not work for you, pls share thoughts and your suggestions for change on the mailing list asap. </li></ul></ul></div></div><div class=""><ul class=""><li class="">Revisiting the agreement on the policy document that it is a good start and it has the right structure. Further on:</li><ul class=""><li class="">The document should note future changes in PeeringDB can trigger updates on the policy document.</li><li class="">We discussed at length the port speed data in PeeringDB, as an example, how it can be understood to be different from IXP or Network point of view. </li><li class="">Suggestion to have an “Overarching Principle” section in the Policy Document, that can possibly note high level principles</li><ul class=""><li class="">General agreement that this is a good suggestion. </li></ul><li class=""><b class="">Action on all TF members: </b>Go through the <a href="https://docs.google.com/document/d/1wVqWwmQpYu5L-2lhvLeu0VHOTWCw8dJMEOrw8Cg5DBk/edit#heading=h.mnvwhx5r2153" class="">policy doc</a> and start making comments or edits. </li></ul></ul><ul class=""><li class="">Meeting Scheduling: </li><ul class=""><li class="">If we can find a common slot, it is great to have them at a fixed time, but it is hard to find it. </li><li class="">Everyone at the call seemed to be flexible with odd hrs in general. </li><li class="">Terry will send a no-meeting zone for Filiz to look into some options for a fixed slot. </li><li class="">Until a fixed date/fime can be announced, we will keep Doodling. </li><li class=""><b class="">Action on Terry: </b>Send Filiz his no-meeting time period. </li><li class=""><b class="">Action on Filiz:</b> Doddle next meeting in the 16-20 Dec week. </li></ul></ul></div><div class=""><br class=""></div><div class="">If you have any questions, please let me know.</div><div class=""><br class=""></div><div class="">Kind regards</div><div class="">Filiz</div></body></html>