<html theme="default-light" iconset="color"><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head><body text="#485663">Serge, <br>
<br>
The first step is for the WG to reach some consensus about what it ought
to recharter to. There's a bunch of topics for a potential new
security-wg which seem to be broadly acceptable to people on the WG, and
another set of suggestions relating to telling the RIPE NCC to turn
itself into an enforcement body, which has never reached consensus over
the years.<br>
<br>
The question for the WG is whether to move forward with rechartering to
what it can agree on or - once again - get bogged down on what it
can't. This is where the problem is.<br>
<br>
Nick<br>
<br>
<span>Serge Droz via anti-abuse-wg wrote on 13/05/2024 17:18:</span><br>
<blockquote type="cite"
cite="mid:61cf502c-1d5c-4815-8aa7-64e89694c4d9@first.org">That's fine.
The WG can make suggestions, RIPE NCC considers this, and
if necessary asks the members, possibly explaining, or asking the WG to
explain why the change makes sense. Most people are sensible.
<br>
<br>
I don't see where there is a problem.
<br>
<br>
Best
<br>
Serge
<br>
<br>
On 13.05.24 16:11, Michele Neylon - Blacknight wrote:
<br>
<blockquote type="cite">Suresh
<br>
<br>It might be helpful to discuss this with them. I’m sure there are
**some** things that they could do without putting it to the members,
but there’s a lot of things that would need member agreement in order to
change.
<br>
<br>Regards
<br>
<br>Michele
<br>
<br>-- <br>
<br>Mr Michele Neylon
<br>
<br>Blacknight Solutions
<br>
<br>Hosting, Colocation & Domains
<br>
<br><a class="moz-txt-link-freetext" href="https://www.blacknight.com/">https://www.blacknight.com/</a> <a class="moz-txt-link-rfc2396E" href="https://www.blacknight.com/"><https://www.blacknight.com/></a>
<br>
<br><a class="moz-txt-link-freetext" href="https://blacknight.blog/">https://blacknight.blog/</a> <a class="moz-txt-link-rfc2396E" href="https://blacknight.blog/"><https://blacknight.blog/></a>
<br>
<br>Intl. +353 (0) 59 9183072
<br>
<br>Direct Dial: +353 (0)59 9183090
<br>
<br>Personal blog: <a class="moz-txt-link-freetext" href="https://michele.blog/">https://michele.blog/</a> <a class="moz-txt-link-rfc2396E" href="https://michele.blog/"><https://michele.blog/></a>
<br>
<br>Some thoughts: <a class="moz-txt-link-freetext" href="https://ceo.hosting/">https://ceo.hosting/</a> <a class="moz-txt-link-rfc2396E" href="https://ceo.hosting/"><https://ceo.hosting/></a>
<br>
<br>-------------------------------
<br>
<br>Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business
Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.:
370845
<br>
<br>I have sent this email at a time that is convenient for me. I do not
expect you to respond to it outside of your usual working hours.
<br>
<br>*From: *anti-abuse-wg <a class="moz-txt-link-rfc2396E" href="mailto:anti-abuse-wg-bounces@ripe.net"><anti-abuse-wg-bounces@ripe.net></a> on
behalf of
Suresh Ramasubramanian <a class="moz-txt-link-rfc2396E" href="mailto:ops.lists@gmail.com"><ops.lists@gmail.com></a>
<br>*Date: *Monday, 13 May 2024 at 14:44
<br>*To: *Serge Droz <a class="moz-txt-link-rfc2396E" href="mailto:serge.droz@first.org"><serge.droz@first.org></a>
<br>*Cc: *anti-abuse-wg@ripe.net <a class="moz-txt-link-rfc2396E" href="mailto:anti-abuse-wg@ripe.net"><anti-abuse-wg@ripe.net></a>
<br>*Subject: *Re: [anti-abuse-wg] Seeking Input on the Future of the
Anti-Abuse Working Group
<br>
<br>*[EXTERNAL EMAIL]*Please use caution when opening attachments from
unrecognised sources.
<br>
<br>RIPE NCC doesn’t really need member input or consensus to change a
lot
of this. Certainly not in tightening or enforcing due diligence
procedures rather than charging 50 euro an ASN
<br>
<br>—srs
<br>
<br>------------------------------------------------------------------------
<br>
<br>*From:*anti-abuse-wg <a class="moz-txt-link-rfc2396E" href="mailto:anti-abuse-wg-bounces@ripe.net"><anti-abuse-wg-bounces@ripe.net></a> on
behalf of Serge
Droz via anti-abuse-wg <a class="moz-txt-link-rfc2396E" href="mailto:anti-abuse-wg@ripe.net"><anti-abuse-wg@ripe.net></a>
<br>*Sent:* Monday, May 13, 2024 7:03:18 PM
<br>*Cc:* <a class="moz-txt-link-abbreviated" href="mailto:anti-abuse-wg@ripe.net">anti-abuse-wg@ripe.net</a> <a class="moz-txt-link-rfc2396E" href="mailto:anti-abuse-wg@ripe.net"><anti-abuse-wg@ripe.net></a>
<br>*Subject:* Re: [anti-abuse-wg] Seeking Input on the Future of the
Anti-Abuse Working Group
<br>
<br>Hi Michele
<br>
<br>
<br><blockquote type="cite">RIPE currently does not have the power to do
a lot of things. The WG
cannot magically change that.
<br></blockquote>
<br>
<br>This is the old merry go round.
<br>
<br>Maybe RIPE NCC needs to change certain things, or it will be changed
for
<br>them. The WG could provide guidance and suggest possible avenues
where
<br>RIPE needs/should change. RIPE can then still ignore that. Believe
it or
<br>not: Organizations can change.
<br>
<br>So if you say you don't want to discuss this, fine. But don't blame
it
<br>RIPE not being able to change.
<br>
<br>Best
<br>Serge
<br>
<br>-- <br>Dr. Serge Droz
<br>Member, FIRST Board of Directors
<br><a class="moz-txt-link-freetext" href="https://www.first.org">https://www.first.org</a> <a class="moz-txt-link-rfc2396E" href="https://www.first.org"><https://www.first.org></a>
<br>
<br>-- <br>
<br>To unsubscribe from this mailing list, get a password reminder, or
change your subscription options, please visit:
<a class="moz-txt-link-freetext" href="https://mailman.ripe.net/">https://mailman.ripe.net/</a>
<a class="moz-txt-link-rfc2396E" href="https://mailman.ripe.net/"><https://mailman.ripe.net/></a>
<br>
<br></blockquote>
<br>
</blockquote>
<br>
</body></html>