<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="">Below pls find a draft agenda for our Meeting#2, scheduled on 18 Nov 17:00 CET.</div><div class=""><br class=""></div><div class="">After our 1st meeting on introductions, problem definition and initial discussions, I would like to have this time focusing on our Scope and an initial discussion and hopefully agreement on what the resulting Policy Document should be containing. </div><div class=""><br class=""></div><div class="">Talk to you soon!</div><div class="">Filiz</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">------------</div><div class=""><br class=""></div><div class="">Draft Agenda:</div><div class=""><br class=""></div><div class="">0. Welcome - 2 mins</div><div class=""><br class=""></div><div class="">1. Scope of Task Force - 25 mins</div><div class=""><br class=""></div><div class="">The expected output and so the goal of the task force is producing a Policy Document on Data Ownership as you know. </div><div class="">We need a scope statement that describes that and that will be published on <a href="https://docs.peeringdb.com/taskforce/dataownership/" class="">https://docs.peeringdb.com/taskforce/dataownership/</a>. </div><div class="">Having it agreed and documented will help us with our planning and structuring the resulting Policy Document too. </div><div class=""><br class=""></div><div class="">I will send an initial wording tomorrow (my) morning before the meeting so we can start discussing it during the meeting. </div><div class=""><br class=""></div><div class="">2. Policy Document - 25 mins</div><div class=""><br class=""></div><div class="">I would like to start having a discussion on the structure of the policy document we need to produce. </div><div class=""><br class=""></div><div class="">Such a policy Document, imo, should list </div><div class=""><br class=""></div><div class="">- all data tokens (object types) in PeeringDB </div><div class="">- for each object </div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>- what they are for, ie who they represent and mean in PeeringDB</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>- who can create and update them, </div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>- what else? </div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">If we can start talking and hopefully start agreeing on such a the list above, we can also start our work drafting some document inline with ongoing discussions. </div><div class="">I will also start a document before our meeting tomorrow on this and so we can use it during the meeting. </div><div class=""><br class=""></div><div class="">3. AOB (3 mins)</div><div class=""><br class=""></div><div class="">4. Adjourn</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">------------</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""> </div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>