<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></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 4th Meeting on 16 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="">Discussion on a recent suggestion made on <a href="https://docs.google.com/document/d/1su38Vko9_3-aoo_LYvKckbK6PNVTwfLgzbYQBN3bv7c/edit" class="">Scope</a> wording: </li><ul class=""><li class="">Suggestion made to change wording of the Scope as noted in the Policy Document. </li><li class=""><b class="">Action on Filiz: </b>Inform TF of the suggestion and allow a week and then have Scope text on website updated. </li><li class=""><b class="">Action on all TF members: </b>Go through the scope doc . If you you think the current wording does not work for you, pls share thoughts and your suggestions for change on the mailing list before 24 Dec. </li></ul><li class=""><a href="https://docs.google.com/document/d/1wVqWwmQpYu5L-2lhvLeu0VHOTWCw8dJMEOrw8Cg5DBk/edit#heading=h.mnvwhx5r2153" class="">Policy Document</a>:</li><ul class=""><li class="">Discussion took place on the Overarching Principles section. General agreement on that this section is a good idea. </li><li class="">Discussion took place on the Data Description section. Virtual networks and issues for Facilities were described. Recognition of these issues showing parallels with note that IXP/Network issue may more operational problems and consequences for those involved. Suggestion of considering some kind of two-factor authentication method for object creation where more than one entity is involved (giving the example of route objects in RIPE DB), instead of the current status quo of trying to determine one single entity to do so. </li><li class=""><b class="">Action on Job and Filiz: </b>Work on wording regarding the curated vs user-maintained data context under the section of Overarching Principles. </li><li class=""><b class="">Action on Arnold:</b> Inform TF regarding the procedures and practices of Admin Committee towards ensuring data quality in PeeringDB.</li><li class=""><b class="">(Reminder of) Action on All:</b> Please contribute on the wording of the Policy Document <span class="Apple-tab-span" style="white-space:pre"> </span></li></ul><li class="">Next meeting:</li><ul class=""><li class="">Meeting #5 will be scheduled to take place during 2-10 Jan </li><li class=""><b class="">Action on Filiz:</b> Doddle next meeting</li></ul></ul></div></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>