March 2024 - anti-abuse-wg - mailman.ripe.net

Call for Nominations: Co-Chair of the Anti-Abuse Working Group
by Markus de Brün 11 Apr '24

11 Apr '24

Dear colleagues, Brian's term as co-chair of the Anti-Abuse Working Group will conclude at RIPE 88. As such, we are initiating the selection process for a new co-chair. You can find detailed information about the selection process at [1]. We encourage you to submit nominations, whether self-nominations or nominations of others, before 17:00 CET on 5th May 2024. For those interested in understanding the responsibilities and expectations of a working group co-chair, please refer to RIPE-692 [2] and RIPE-765 [3]. If you have any further questions or would like to submit a nomination, please do not hesitate to contact us at aa-wg-chair(a)ripe.net. Kind regards, Markus Co-chair, Anti-Abuse Working Group [1] https://www.ripe.net/community/wg/active-wg/anti-abuse/anti-abuse-wg-chair-… [2] https://www.ripe.net/publications/docs/ripe-692 [3] https://www.ripe.net/publications/docs/ripe-765/

2 3

Seeking Input on the Future of the Anti-Abuse Working Group
by Markus de Brün 03 Apr '24

03 Apr '24

* Dear Anti-Abuse Working Group Members, As Co-Chairs, we have been carefully monitoring the discussions on the mailing list and are concerned about the current state of stagnation and lack of progress. After consideration and discussion among the Co-Chairs, we believe it is necessary to initiate a dialogue regarding the future direction of our working group. Some action is needed to revitalise our efforts. The Co-Chairs have discussed a number of options, both between ourselves and with the RIPE Chair Team. However, due to the lack of general engagement, and the circular conversations on the list, we see three viable options at this point:: 1. Re-charteringthe working group, possibly transitioning it into a Security Working Group to broaden our scope and address related concerns comprehensively. (The current charter can be found here: https://www.ripe.net/community/wg/active-wg/anti-abuse/ <https://www.ripe.net/community/wg/active-wg/anti-abuse/>) 2. It is possible we are simply the wrong Co-Chairs at the wrong time, so we can step-downand allow the working group to select new Co-Chairs. 3. Closing the working groupif consensus cannot be reached on a viable path forward. It may be that there are people in the Working Group who are eager to propose new policies, or embark on a project to systematically examine the abuse ecosystem, but over the last year or so, there has been no evidence this is the case. However, we firmly believe that the best course of action is to engage all members of the Anti-Abuse Working Group in an open and transparent discussion about the challenges we face and the opportunities for positive change. Your input and perspectives are invaluable in shaping the future of our community. Therefore, we are inviting you to participate actively in this crucial conversation. We encourage you to share your thoughts, suggestions, and concerns regarding the current state of the working group and your vision for its future direction. Your input will help inform our next steps and guide the evolution of the Anti-Abuse Working Group. We encourage you to share your feedback openly on the mailing list so that all members can participate in the conversation. We hope to discuss the status at RIPE88. Thank you for reading this far. We look forward to your active participation in shaping the future of the Anti-Abuse Working Group. Best regards, Brian, Tobias, Markus *

11 10

IS3C public consultation on an alternative narrative to deploy Internet standards
by Wout de Natris 12 Mar '24

12 Mar '24

Dear colleagues, IGF DC IS3C invites you to participate in the consultation on positively enhancing the deployment of two Internet standards: DNSSEC and RPKI. You are invited to answer either of these questions: Do the arguments used to favor a positive decision, convince you to order deployment within your organisation or from your service provider? / Do they assist you to convince decision takers in your organisation to invest in security by design? You are invited to share your views and arguments with IS3C’s expert team and have been granted commenting rights in this document to do so. The consultation runs from 11 March to 12PM UTC, Friday 5 April 2024. Your contribution will be taken into consideration when finalising the text before publication this spring. Here is the link to the Google Doc: https://docs.google.com/document/d/1YYq3ie9D03L1Z5ssgPbWKV5becUgNw0h7_fmm9x… [https://lh7-us.googleusercontent.com/docs/AHkbwyKX2Kk3Ln5vVsuCkXG99FKVph_OJ…]<https://docs.google.com/document/d/1YYq3ie9D03L1Z5ssgPbWKV5becUgNw0h7_fmm9x…> IS3C WG 8 work document<https://docs.google.com/document/d/1YYq3ie9D03L1Z5ssgPbWKV5becUgNw0h7_fmm9x…> docs.google.com We hope to receive your views so we can present the most convincing arguments to deploy DNSSEC, RPKI and all other security-related Internet standards and ICT best practices. (FYI, this project is sponsored by ICANN and RIPE NCC.) Kind regards, Wout de Natris IS3C: Making the Internet more secure and safer

7 9

Re: [anti-abuse-wg] anti-abuse-wg Digest, Vol 145, Issue 7
by Wout de Natris 12 Mar '24

12 Mar '24

Dear colleagues, Thank you all very much for your constructive comments. Please make sure you contribute in the document itself, so our experts can take your views into account when finalising the document. As an explanation. IS3C focuses on the deployment of all security-related Internet standards and ICT best practices. See e.g. the list of 23 Internet standards (of which one is a best practice) we developed recently that all organisation can use when procuring ICTs. The alternative narrative we are working on now, can be used for all standards and best practices (for more information, see is3coaltion.org). Also, we make a clear distinction between organisations that need to take action themselves and organisations that need to demand this level of security to be built in by design when procuring ICTs, by adding them to their procurement demands. The arguments most likely will vary between the two. Please keep this in mind. Why DNSSEC and RPKI? Among IS3C's members the desire arose to have one Working Group focus on two standards only. Consensus led to DNSSEC and RPKI, which led to natural partners. Where your concerns on DNSSEC are concerned, please add them in the doc so that they can be added into the final document. Also, please add the solution, so it can be taken into account as well. Should you be interested to participate in our work in the future, please let me know and I will guide you to our membership list. Finally, I am reaching out to you as the Dynamic Coalition's coordinator. Thank you again, as your comments are very valuable to us. Kind regards, Wout de Natris IS3C: Making the Internet more secure and safer ________________________________ From: anti-abuse-wg <anti-abuse-wg-bounces(a)ripe.net> on behalf of anti-abuse-wg-request(a)ripe.net <anti-abuse-wg-request(a)ripe.net> Sent: Tuesday, March 12, 2024 9:57 AM To: anti-abuse-wg(a)ripe.net <anti-abuse-wg(a)ripe.net> Subject: anti-abuse-wg Digest, Vol 145, Issue 7 Send anti-abuse-wg mailing list submissions to anti-abuse-wg(a)ripe.net To subscribe or unsubscribe via the World Wide Web, visit https://lists.ripe.net/mailman/listinfo/anti-abuse-wg or, via email, send a message with subject or body 'help' to anti-abuse-wg-request(a)ripe.net You can reach the person managing the list at anti-abuse-wg-owner(a)ripe.net When replying, please edit your Subject line so it is more specific than "Re: Contents of anti-abuse-wg digest..." Today's Topics: 1. Re: IS3C public consultation on an alternative narrative to deploy Internet standards (David Conrad) 2. Re: IS3C public consultation on an alternative narrative to deploy Internet standards (John Levine) 3. Re: IS3C public consultation on an alternative narrative to deploy Internet standards (Alessandro Vesely) ---------------------------------------------------------------------- Message: 1 Date: Mon, 11 Mar 2024 19:55:17 +0000 From: David Conrad <drc(a)virtualized.org> To: Wout de Natris <denatrisconsult(a)hotmail.nl> Cc: "anti-abuse-wg(a)ripe.net" <anti-abuse-wg(a)ripe.net> Subject: Re: [anti-abuse-wg] IS3C public consultation on an alternative narrative to deploy Internet standards Message-ID: <3D269691-628C-49B5-B173-B01518B92EB9(a)virtualized.org> Content-Type: text/plain; charset="utf-8" Hi, I've focused my comments specifically on the section entitled "The Alternative Narrative, a Call To Action for Leaders?. While I understand the desire to encourage DNSSEC and RPKI deployment at the leadership level, however if you??re targeting policy makers and C-levels, I would strongly encourage a balanced, honest approach, one that highlights both the benefits as well as risks. From experience, I believe focusing only on (alleged) benefits and stretching applicability (almost beyond recognition) can be quite counter-productive when the inevitable failures (e.g., https://ianix.com/pub/dnssec-outages.html, https://packetvis.com/blog/rpki-trust-anchor-malfunctions/) occur. FWIW. Regards, -drc Partner/CTO, Layer 9 Technologies (layer9.tech <http://layer9.tech/>) > On Mar 11, 2024, at 2:58?AM, Wout de Natris <denatrisconsult(a)hotmail.nl> wrote: > > Dear colleagues, > > IGF DC IS3C invites you to participate in the consultation on positively enhancing the deployment of two Internet standards: DNSSEC and RPKI. You are invited to answer either of these questions: Do the arguments used to favor a positive decision, convince you to order deployment within your organisation or from your service provider? / Do they assist you to convince decision takers in your organisation to invest in security by design? You are invited to share your views and arguments with IS3C?s expert team and have been granted commenting rights in this document to do so. The consultation runs from 11 March to 12PM UTC, Friday 5 April 2024. Your contribution will be taken into consideration when finalising the text before publication this spring. Here is the link to the Google Doc: > > https://docs.google.com/document/d/1YYq3ie9D03L1Z5ssgPbWKV5becUgNw0h7_fmm9x… > <https://docs.google.com/document/d/1YYq3ie9D03L1Z5ssgPbWKV5becUgNw0h7_fmm9x…> > IS3C WG 8 work document <https://docs.google.com/document/d/1YYq3ie9D03L1Z5ssgPbWKV5becUgNw0h7_fmm9x…> > docs.google.com <http://docs.google.com/> > We hope to receive your views so we can present the most convincing arguments to deploy DNSSEC, RPKI and all other security-related Internet standards and ICT best practices. (FYI, this project is sponsored by ICANN and RIPE NCC.) > > Kind regards, > > Wout de Natris > > IS3C: Making the Internet more secure and safer

1 0

Call For Agenda Items - RIPE88
by Brian Nisbet 11 Mar '24

11 Mar '24

Colleagues, As we move further into spring in Europe, it is time to think about the agenda for our next WG meeting, at RIPE 88 in Kraków - https://ripe88.ripe.net/ Registration for the meeting, running from the 20th - 24th May, is open. The Anti-Abuse WG will be meeting and Markus, Tobias and I would invite people to submit topics for discussion, policy proposals, presentations for general enlightenment and, of course, work items for the working group. Speakers & presenters can either be present in Rome or reaching us live via the Internet! The Anti-Abuse WG session will be taking place on the 21st of May at 16:00 CEST. As always you can reach us at aa-wg-chair(a)ripe.net Thanks, Brian Co-Chair, RIPE AA-WG Brian Nisbet (he/him) Service Operations Manager HEAnet CLG, Ireland's National Education and Research Network North Dock Two, 93-94 North Wall Quay, Dublin 1, D01 V8Y6 +35316609040 brian.nisbet(a)heanet.ie www.heanet.ie Registered in Ireland, No. 275301. CRA No. 20036270

1 1