<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=""><div class="">Hello all,</div><div class=""><br class=""></div><div class="">We had a discussion about this during the last meeting we just had. </div><div class="">Both Job and Stefan noted their agreement with the wording as it is in the latest draft Chris shared:</div><div class=""><br class=""></div><div class=""><a href="https://www.caputo.com/dotf/0.20200325.1-WM-CC-DB-AN-TS-BS-PG.txt" class="">https://www.caputo.com/dotf/0.20200325.1-WM-CC-DB-AN-TS-BS-PG.txt</a></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Accordingly, I believe we have general agreement on the wording considering the support mails so far. </div><div class="">This is also confirmed during the last meeting we had (see the notes in my previous mail). </div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><b class="">Chris</b>, have you received any off-list comments that you need to share with the rest of the TF after 25 March? </div><div class=""><br class=""></div><div class="">If not, in line with the support during the meeting towards calling a Last Call, I suggest <b class="">5 April 2020 23:59 UTC </b>as the deadline of the Last Call on the aforementioned draft.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Please note Last Call is for <i class="">objections only</i>. </div><div class="">We do not need anyone to repeat their agreement on the draft if they have done so already. </div><div class=""><br class=""></div><div class="">If we do not receive objections to the document we will have it as policy after the deadline. </div><div class=""><br class=""></div><div class="">If you have objection(s), pls raise your concerns and comments on the mailing list, providing detailed arguments supporting your reasons of objection(s). </div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Kind regards</div><div class="">Filiz </div><div class=""><br class=""></div><div class=""> </div><div class=""><br class=""></div><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 30 Mar 2020, at 14:39, Stefan Wahl <<a href="mailto:swa@open7.de" class="">swa@open7.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi,<br class=""><br class="">I agree with Job here. Simple is better.<br class=""><br class="">Best<br class=""><br class=""> Stefan<br class=""><br class=""><blockquote type="cite" class="">Am 22.03.2020 um 03:21 schrieb Job Snijders <<a href="mailto:job@instituut.net" class="">job@instituut.net</a>>:<br class=""><br class="">On Sun, Mar 22, 2020, at 00:26, Arnold Nipper wrote:<br class=""><blockquote type="cite" class="">Actually how the dispute resolution is implemented should be left to the<br class="">AC/Board to agree upon. Simply<br class=""><br class=""> - This Task Force recommends that the Admin Committee charter be<br class=""> amended by a dispute resolution procedure.<br class=""><br class="">Does that make sense?<br class=""></blockquote><br class="">At the end of the day the board is legally responsible for PeeringDB (why else does the board exist?). The role of the board should be acknowledged in this task force output. Already today anyone can write the board about an data-ownership issue which could mean they are appealing a decision someone made. <br class=""><br class="">If I recall correctly the group discussed on the January call to document escalation procedures. Yesterday’s draft didn’t contain such text yet. <br class=""><br class="">I would recommend to return to Chris’ original text: “Decisions of the Admin Committee may be appealed to the PeeringDB Board of Directors.” as it is simplest and describes reality.<br class=""><br class="">Kind regards,<br class=""><br class="">Job<br class="">-- <br class="">DataOwnership-TF mailing list<br class=""><a href="mailto:DataOwnership-TF@lists.peeringdb.com" class="">DataOwnership-TF@lists.peeringdb.com</a><br class="">https://lists.peeringdb.com/cgi-bin/mailman/listinfo/dataownership-tf<br class=""></blockquote><br class="">-- <br class="">DataOwnership-TF mailing list<br class=""><a href="mailto:DataOwnership-TF@lists.peeringdb.com" class="">DataOwnership-TF@lists.peeringdb.com</a><br class="">https://lists.peeringdb.com/cgi-bin/mailman/listinfo/dataownership-tf<br class=""></div></div></blockquote></div><br class=""></body></html>