<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style></style></head><body lang=ES link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1>Hi Niall, all,<o:p></o:p><o:p> </o:p>I need to insist in some of the points that I’ve raised on February 20th, rephrasing them a little bit, considering the new version:<o:p></o:p><o:p> </o:p><ol style='margin-top:0cm' start=1 type=1><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'>Elements of the TF structure of work (Rationale, Charter, etc.). I don’t agree it should be the Chair unique responsibility to define them. May be the way to resolve this is that once they are drafted by the Chair, there is an opportunity for the community to comment on those, let’s say during a one-month period? Alternatively, the TF itself may be able to propose a review on that once the work is started and seek community support.<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'>There is no way an open and transparent community can accept a non-justified decision for appointing TF members. This is prone to arbitrary and discriminatory decisions, even if not done in bad faith. Considering the “usual” level of participation, I think it will be fine to just call for volunteers. You will never get 100 volunteers. I will even agree to say “the Chair is suggesting the following experts and we open a n weeks period for other volunteers, up to a limit of 10 participants” (just an example). Expertise is not the only important thing. You can have experts that don’t have the time, or have a bias, or whatever. Allowing open participation removes the arbitrariness and provides a balance not only with experts, but also with other community eyes.<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'>Consensus building. I’m happier with the new version of this section. However, there is something that is still not resolved. If the TF members don’t reach an agreement in specific issues, the report from the TF must show that disagreement and explain the different views, because that is most probably very representative of what the community could think and it is a way to be very transparent so the community can either provide alternative views that may be the TF didn’t consider, or balance the TF outcome, etc.<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'>Participation of observers in TF calls. Exactly the same we are saying that TF mailing list and minutes must be open to the community, the community must be able to join the calls (if the TF is using them) as observers (no voice, no “vote”). Minutes are good, but they aren’t scripts of all what is being said or discussed, and there may be details that are very important and can provide means for observers to contribute with additional suggestions from details in that discussion.<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'> This is not only relevant for the TFs and don’t belong to this document but it shows very well the point I’m trying to make. We need a clear pre-defined well-known timing in case a TF outcome needs to go for community consensus. This is the reason I’m saying that the governance documents should also use the PDP, because it is a well-known process with well-known timing.<o:p></o:p></li></ol><o:p> </o:p><div><o:p> </o:p>Overall comment that explains my objections/proposed changes: We know that whatever is drafted by the TF will need to reach the community consensus or bring the creation of a new document(s), etc. However we also know that the participation in consensus decision (either in a direct outcome from the TF or subsequent documents) is extremely low. So, it is easy to understand that a report from a TF that doesn’t neccesarily have a community “overall” support, may not receive sufficient inputs (either in favour or against) because many community members can think “oh well, it was a TF working on that, they know what they are doing, it should be ok”. So there is a lower level of review, etc.<o:p></o:p><o:p> </o:p>Regards,<o:p></o:p>Jordi<o:p></o:p>@jordipalet<o:p></o:p><o:p> </o:p></div><o:p> </o:p><o:p> </o:p><div><div>El 23/3/22, 15:38, "ripe-list en nombre de Niall O'Reilly" <<a href="mailto:ripe-list-bounces@ripe.net">ripe-list-bounces@ripe.net</a> en nombre de <a href="mailto:niall.oreilly@ucd.ie">niall.oreilly@ucd.ie</a>> escribió:<o:p></o:p></div></div><div><o:p> </o:p></div><div><div>Dear Colleagues,<o:p></o:p>[Please view this message as either plain text or HTML, according to your preference.]<o:p></o:p>In view of significant comments received during what we had expected to be a restricted last call, Mirjam and I have decided to make a fresh draft of the proposed document on RIPE Task Forces and to make this available for your review <a href="https://www.ripe.net/publications/docs/ripe-documents/other-documents/ripe-task-forces-definition-and-guidelines-v3/">here</a>. An onward link leads to an <a href="https://ripe.net/publications/docs/ripe-documents/other-documents/ripe-task-forces-definition-and-guidelines/@@diff-items?id=ripe-task-forces-definition-and-guidelines-v3">alternative presentation</a> of the draft, in which recent changes are highlighted.<o:p></o:p>We are very grateful to Boris Duval and Antony Gollan, who did most of the real work.<o:p></o:p>We plan to close the review period just before 24:00 UTC on Sunday 10 April next, and to announce a two-week last-call period shortly after that.<o:p></o:p>Please let us know what you think, in sufficient numbers so that we can understand whether the draft enjoys community consensus.<o:p></o:p>For your convenience, the table below shows the dates when successive drafts of this proposed RIPE Document were announced.<o:p></o:p><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 style='margin-left:59.4pt;background:#F7F7F7;border-collapse:collapse;border-radius:5px 5px 5px 5px'><thead><tr><td style='padding:6.0pt 6.0pt 6.0pt 6.0pt'>Date<o:p></o:p></td><td style='padding:6.0pt 6.0pt 6.0pt 6.0pt'>From<o:p></o:p></td><td style='padding:6.0pt 6.0pt 6.0pt 6.0pt'>Remarks<o:p></o:p></td></tr></thead><tr><td style='padding:6.0pt 6.0pt 6.0pt 6.0pt;border-top:lightgray'>19 Nov 2021<o:p></o:p></td><td style='padding:6.0pt 6.0pt 6.0pt 6.0pt;border-top:lightgray;border-left:lightgray'>M.Kuehne<o:p></o:p></td><td style='padding:6.0pt 6.0pt 6.0pt 6.0pt;border-top:lightgray;border-left:lightgray'><a href="https://www.ripe.net/ripe/mail/archives/ripe-list/2021-November/002363.html">002363</a> Draft; suggestions invited<o:p></o:p></td></tr><tr><td style='padding:6.0pt 6.0pt 6.0pt 6.0pt;border-top:lightgray'>16 Dec 2021<o:p></o:p></td><td style='padding:6.0pt 6.0pt 6.0pt 6.0pt;border-top:lightgray;border-left:lightgray'>N.O'Reilly<o:p></o:p></td><td style='padding:6.0pt 6.0pt 6.0pt 6.0pt;border-top:lightgray;border-left:lightgray'><a href="https://www.ripe.net/ripe/mail/archives/ripe-list/2021-December/002402.html">002402</a> Update; last call closing 14 Jan<o:p></o:p></td></tr><tr><td style='padding:6.0pt 6.0pt 6.0pt 6.0pt;border-top:lightgray'>3 Feb 2022<o:p></o:p></td><td style='padding:6.0pt 6.0pt 6.0pt 6.0pt;border-top:lightgray;border-left:lightgray'>N.O'Reilly<o:p></o:p></td><td style='padding:6.0pt 6.0pt 6.0pt 6.0pt;border-top:lightgray;border-left:lightgray'><a href="https://www.ripe.net/ripe/mail/archives/ripe-list/2022-February/002444.html">002444</a> Update; last call extended to 18 Feb<o:p></o:p></td></tr><tr><td style='padding:6.0pt 6.0pt 6.0pt 6.0pt;border-top:lightgray'>23 Mar 2022<o:p></o:p></td><td style='padding:6.0pt 6.0pt 6.0pt 6.0pt;border-top:lightgray;border-left:lightgray'>N.O'Reilly<o:p></o:p></td><td style='padding:6.0pt 6.0pt 6.0pt 6.0pt;border-top:lightgray;border-left:lightgray'><a href="https://www.ripe.net/publications/docs/ripe-documents/other-documents/ripe-task-forces-definition-and-guidelines-v3/">v3</a> Fresh draft for review until 10 Apr<o:p></o:p></td></tr></table>Best regards, Niall O’Reilly<o:p></o:p><div class=MsoNormal align=center style='margin-left:35.4pt;text-align:center'><hr size=0 width="100%" align=center></div></div></div>-- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/ripe-list <o:p></o:p></div> ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. </body></html>