[lacnog] Fwd: [ripe-list] The Future of Discussion Lists

[Carlos Marcelo Martinez Cagnazzo]

<div dir="auto">Se que es una discusion que a varios en la lista les va a interesar. <div style=""><br style=""></div><div style="">/Carlos<br style=""><br style=""><div id="cm_footer" class="cm_footer" style=""><div id="cm_sent_from" style="">via <a href="https://cloudmagic.com/k/d/mailapp?ct=pi&cv=10.0.62&pv=16.4.1&source=email_footer_2" style="">Newton Mail</a></div></div><br style=""><div id="cm_replymail_content_wrap" style=""><p style="">------Forwarded message------ <br style="">From: Leo Vegoda <<a href="mailto:leo en vegoda.org" target="_blank" rel="noopener noreferrer">leo en vegoda.org</a>> <br style="">Date: Fri, May 26, 2023 at 4:41<br style="">Subject: [ripe-list] The Future of Discussion Lists            <br style="">To: <a href="mailto:ripe-list en ripe.net" target="_blank" rel="noopener noreferrer">ripe-list en ripe.net</a> </p> <br style=""><br style=""><div id="cm_replymail_content_1685101971" style="overflow: visible;">Dear RIPE community,<br style=""><br style="">At yesterday’s community plenary I asked whether mailing lists are<br style="">sustainable as our main communication channel. For those who were not<br style="">able to attend, the slide and a recording are available here:<br style=""><br style="">- <a href="https://tr.cloudmagic.com/h/v6/link-track/1.0/1685102033136572-8c6206e6-6b7e-912f-0ac2-31ed57098460/1685102016/96f2d3060286ecbab9150cfe7cb38c63/54a8114ee3c78f0d14605fb8679b29ac/c685fcd416a89ab357b7e28c4a5ee604?redirect_uri=https://ripe86.ripe.net/wp-content/uploads/presentations/12-Mailing-Lists-RIPE-86.pdf" target="_blank" rel="noopener noreferrer">ripe86.ripe.net/wp-content/uploads/presentations/12-Mailing-Lists-RIPE-86.pdf</a><br style="">- <a href="https://tr.cloudmagic.com/h/v6/link-track/1.0/1685102033136584-749e5ef5-eca1-3f5c-152b-dd5e5488f449/1685102016/96f2d3060286ecbab9150cfe7cb38c63/54a8114ee3c78f0d14605fb8679b29ac/c685fcd416a89ab357b7e28c4a5ee604?redirect_uri=https://ripe86.ripe.net/archives/video/1115" target="_blank" rel="noopener noreferrer">ripe86.ripe.net/archives/video/1115</a><br style=""><br style="">I am obviously concerned that discussion lists might not serve us with<br style="">fidelity in the future. If that is the case, I want us to manage any<br style="">change we need to make. We should not be bounced into rapid change.<br style=""><br style="">There was more discussion than I expected. I’m sending this message to<br style="">ask the questions:<br style=""><br style="">- Am I wrong? Are e-mail discussion lists a sustainable communication<br style="">channel for the foreseeable future?<br style="">- Are e-mail discussion lists an acceptable technology to people<br style="">joining the industry?<br style=""><br style="">The text below is similar to something I shared with the WG Chairs<br style="">several months ago.<br style=""><br style="">Kind regards,.<br style=""><br style="">Leo<br style=""><br style="">ripe-781 describes four fundamental principles supporting our policy<br style="">development process. The first two principles are openness and<br style="">transparency.<br style=""><br style="">Changes in the treatment of e-mail by large industry players presents<br style="">a challenge to these two principles.<br style=""><br style="">In 1992, when ripe-001 was published, anyone could run e-mail services<br style="">on any Internet infrastructure they could use. It is now far more<br style="">difficult to run e-mail services. Technology developments, like DMARC,<br style="">have made discussion mailing lists less effective.<br style=""><br style="">Validation failures increase the probability of messages being treated<br style="">as junk. Subscribers to RIPE's discussion lists will miss messages<br style="">when their e-mail services provider treats them as junk.<br style=""><br style="">When a legitimate message to a RIPE discussion list is treated as junk<br style="">the sender's voice has been moderated by a third-party mail provider.<br style="">RIPE's transparency is diminished when its discussion lists are<br style="">subjected to gatekeeping by third-party mail providers.<br style=""><br style="">In 1992, e-mail was an improvement to postal services and telephony<br style="">protocols. In 2023, we have a wide choice of communication protocols<br style="">and platforms.<br style=""><br style="">I believe that new protocols and platforms are preferred over e-mail<br style="">by potential participants in RIPE at the start of their careers. We<br style="">want these people to take part in RIPE. They are the future of<br style="">coordination for the operators of IP networks in Europe and the rest<br style="">of the world.<br style=""><br style="">We must offer all current and potential participants in RIPE an<br style="">effective set of tools. Any tools we use must support the principles<br style="">of openness and transparency.<br style=""><br style="">An ideal set of tools might have features like this:<br style=""><br style="">1. An open protocol available for implementation by anyone.<br style="">2. Free(ly available) software implementations for popular operating<br style="">systems (Android, iOS, Linux, macOS, and Windows).<br style="">3. Allows a user to choose to have activity pushed to them. They must<br style="">not be forced to maintain a login to be informed of activity they are<br style="">interested in.<br style="">4. A public archive that cannot be retrospectively edited (barring<br style="">exceptional situations).<br style=""><br style="">While the technology choices need to support the principles of<br style="">openness and transparency, they do not need to do all the work.<br style="">Announcements, blog posts, and other kinds of communications can be<br style="">built into our processes.<br style=""><br style="">The combination of technology and process can make the whole more effective.<br style=""><br style="">-- <br style=""><br style="">To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: <a href="https://tr.cloudmagic.com/h/v6/link-track/1.0/1685102033136590-945b1403-2c2d-0590-2c87-3e8b24cf2180/1685102016/96f2d3060286ecbab9150cfe7cb38c63/54a8114ee3c78f0d14605fb8679b29ac/c685fcd416a89ab357b7e28c4a5ee604?redirect_uri=https://lists.ripe.net/mailman/listinfo/ripe-list" target="_blank" rel="noopener noreferrer">lists.ripe.net/mailman/listinfo/ripe-list</a><br style=""></div>            </div>            </div></div>
------------ próxima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: <https://mail.lacnic.net/pipermail/lacnog/attachments/20230526/261ebc2c/attachment.htm>