<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<div>
<div dir="ltr">There is somewhat more being proposed than that bare minimum of due diligence but none of this makes ripe ncc a regulator any more than a pharmacist verifying a prescription becomes the FDA</div>
</div>
<div id="ms-outlook-mobile-signature">
<div><br>
</div>
<div style="direction: ltr;">--srs</div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Matthias Merkel <matthias.merkel@staclar.com><br>
<b>Sent:</b> Thursday, November 30, 2023 4:03:07 PM<br>
<b>To:</b> Suresh Ramasubramanian <ops.lists@gmail.com>; Leo Vegoda <leo@vegoda.org><br>
<b>Cc:</b> anti-abuse-wg@ripe.net <anti-abuse-wg@ripe.net><br>
<b>Subject:</b> Re: [anti-abuse-wg] Abuse Report ignored. What to do as next?</font>
<div> </div>
</div>
<div>
<div class="x_main-style-f1430775be1aabf3a3c0" style="">
<div>I have already noted that I have no objections to a proposal solely to verify abuse mailbox functionality, but that we should be careful adding anything further. Perhaps I wasn't clear enough in this:</div>
<blockquote style="margin:0 0 0 7px; border-left:3px solid #bbbdbf; padding-left:10px">
<div>Arguably a proposal to simply require verification of the abuse mailbox does not make the NCC a regulator (and, in fact, I think the NCC already does this with ASNs), but I do not see how this would be an effective measure. </div>
<div><br>
</div>
<div>Making further requirements would make the NCC a regulator, and this may be dangerous precedent. </div>
</blockquote>
<div><br>
</div>
<div>Regarding the potential that government regulators will put rules in place if we don't, I don't think this is a big concern here. Many governments already do have those rules and already supervise network operators in their countries. The issue in this
specific case is that some countries simply don't care, and do not have laws or regulations around the issue.</div>
<br>
<div class="x_front-signature">
<div>�</div>
<div>Maria Merkel</div>
<div><img src="https://cdn.staclar.com/logos/novecore/newlogo.png" style="width:118px; height:14.75px"></div>
<div><br>
</div>
<div><span style="font-size:10px">This email was sent by [company]. Any statements contained in this email are personal to the author and are not necessarily the statements of the company unless specifically stated.</span></div>
<div><br>
</div>
<div><span style="font-size:10px">Novecore and Staclar are collective trading names of Novecore Ltd., registered in England and Wales under company number 11748197, Novecore Licensing Ltd., registered in England and Wales under company number 11544982, Staclar
Carrier Ltd., registered in England and Wales under company number 12219686, Staclar Financial Services Ltd., registered in England and Wales under company number 13843292 (registered offices 54 Portland Place, London, UK, W1B 1DY); Novecore Professional Services
Ltd., registered in England and Wales under company number 13965912 (registered office 13 Freeland Park, Wareham Road, Poole, UK, BH16 6FA); Novecore (Estonia) O�, registered in Estonia under registry code 16543205 (local contact Baltic Business Services O�,
Narva mnt 5, 10117 Tallinn, Estonia); Novecore (USA) Inc., registered in Delaware under file number 6707907, Novecore Licensing (USA) LLC, registered in Delaware under file number 4030866, and Staclar, Inc., registered in Delaware under file number 7413401
(registered agents The Corporation Trust Company, Corporation Trust Center, 1209 Orange St, Wilmington DE 19801, USA). Novecore Licensing Ltd. is registered for VAT in the United Kingdom under VAT registration number 347 4545 80. Novecore (Estonia) O� is registered
for VAT in the European Union under VAT registration number EE102518979. Novecore Professional Services Ltd. is a trust or company service provider registered with and supervised by HM Revenue & Customs under the Money Laundering, Terrorist Financing and Transfer
of Funds (Information on the Payer) Regulations 2017 (registration number XMML00000178208). Staclar Financial Services Ltd. is an Annex 1 financial institution registered with and supervised by the Financial Conduct Authority under the Money Laundering, Terrorist
Financing and Transfer of Funds (Information on the Payer) Regulations 2017 (firm reference number 989521). Registration is not equivalent to authorisation and is not an endorsement to do business with a firm. Staclar Financial Services Ltd. is not an authorised
person within the meaning of the Financial Services and Markets Act 2000 and does not review, approve, or endorse financial promotions for securities issues it is involved in or provide any form of investment advice.</span></div>
</div>
</div>
<img alt="Sent from Front" aria-hidden="true" src="https://app.frontapp.com/api/1/noauth/companies/2fa1142cccd8fdcdb954/seen/msg_123t5r4a/0/d2467c39.gif" style="width:1px; height:1px"><br>
<blockquote type="cite" class="x_front-blockquote">On November 30, 2023 at 11:25 AM GMT+1
<a href="mailto:ops.lists@gmail.com" target="_blank" rel="noopener noreferrer">ops.lists@gmail.com</a> wrote:<br>
<br>
<div id="x_fae_123t5r4ali0erf">
<div>
<div></div>
<div class="x_fasrn39y x_front-email-body">
<div>
<div dir="ltr">
<div dir="ltr">This is simply an ongoing verification that the justification and other paperwork which were used to allocate the numbers are reasonable and correct </div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Consensus tends to work in strange ways - and room packing isn�t unknown if you see the example I cited </div>
</div>
</div>
<div id="x_ms-outlook-mobile-signature">
<div><br>
</div>
<div style="direction:ltr">--srs</div>
</div>
<hr style="display:inline-block; width:98%">
<div dir="ltr" id="x_divRplyFwdMsg"><font color="#000000" face="Calibri, sans-serif" style="font-size:11pt"><b>From:</b> anti-abuse-wg <<a rel="noopener noreferrer" href="mailto:anti-abuse-wg-bounces@ripe.net" target="_blank">anti-abuse-wg-bounces@ripe.net</a>>
on behalf of Matthias Merkel <<a rel="noopener noreferrer" href="mailto:matthias.merkel@staclar.com" target="_blank">matthias.merkel@staclar.com</a>><br>
<b>Sent:</b> Thursday, November 30, 2023 3:24:02 PM<br>
<b>To:</b> Leo Vegoda <<a rel="noopener noreferrer" href="mailto:leo@vegoda.org" target="_blank">leo@vegoda.org</a>>; Suresh Ramasubramanian <<a rel="noopener noreferrer" href="mailto:ops.lists@gmail.com" target="_blank">ops.lists@gmail.com</a>><br>
<b>Cc:</b> <a rel="noopener noreferrer" href="mailto:anti-abuse-wg@ripe.net" target="_blank">
anti-abuse-wg@ripe.net</a> <<a rel="noopener noreferrer" href="mailto:anti-abuse-wg@ripe.net" target="_blank">anti-abuse-wg@ripe.net</a>><br>
<b>Subject:</b> Re: [anti-abuse-wg] Abuse Report ignored. What to do as next?</font>
<div> </div>
</div>
<div>
<div class="x_farjkdot" style="">
<div>Of course, this is not how consensus works. </div>
<div><br>
</div>
<div>I also think you're misunderstanding my argument. I'm all for fighting abuse. A lot of my work is in abuse and fraud prevention and in the prevention of financial crime. I'm not arguing against preventing abuse, only against adding even more regulators
where they aren't needed. </div>
<div><br>
</div>
<div>The Gmail example still does not address my concern. They say what you can do with Gmail, which is the service. An IP address itself is not an abusable service, the systems addressed by them are. Gmail doesn't tell you what to do on third party services
you sign up to with your <a rel="noopener noreferrer" href="http://gmail.com/" target="_blank">
gmail.com</a> address. Google is responsible for Gmail. The RIPE NCC is responsible for the IP addresses. The network operator is responsible for the systems. </div>
<br>
<div class="x_fae5kelq">
<div>�</div>
<div>Maria Merkel</div>
<div><img src="https://cdn.staclar.com/logos/novecore/newlogo.png" style="width:118px; height:14.75px"></div>
<div><br>
</div>
<div><span style="font-size:10px">This email was sent by [company]. Any statements contained in this email are personal to the author and are not necessarily the statements of the company unless specifically stated.</span></div>
<div><span style="font-size:10px"><br>
</span></div>
<div><span style="font-size:10px">Novecore and Staclar are collective trading names of Novecore Ltd., registered in England and Wales under company number 11748197, Novecore Licensing Ltd., registered in England and Wales under company number 11544982, Staclar
Carrier Ltd., registered in England and Wales under company number 12219686, Staclar Financial Services Ltd., registered in England and Wales under company number 13843292 (registered offices 54 Portland Place, London, UK, W1B 1DY); Novecore Professional Services
Ltd., registered in England and Wales under company number 13965912 (registered office 13 Freeland Park, Wareham Road, Poole, UK, BH16 6FA); Novecore (Estonia) O�, registered in Estonia under registry code 16543205 (local contact Baltic Business Services O�,
Narva mnt 5, 10117 Tallinn, Estonia); Novecore (USA) Inc., registered in Delaware under file number 6707907, Novecore Licensing (USA) LLC, registered in Delaware under file number 4030866, and Staclar, Inc., registered in Delaware under file number 7413401
(registered agents The Corporation Trust Company, Corporation Trust Center, 1209 Orange St, Wilmington DE 19801, USA). Novecore Licensing Ltd. is registered for VAT in the United Kingdom under VAT registration number 347 4545 80. Novecore (Estonia) O� is registered
for VAT in the European Union under VAT registration number EE102518979. Novecore Professional Services Ltd. is a trust or company service provider registered with and supervised by HM Revenue & Customs under the Money Laundering, Terrorist Financing and Transfer
of Funds (Information on the Payer) Regulations 2017 (registration number XMML00000178208). Staclar Financial Services Ltd. is an Annex 1 financial institution registered with and supervised by the Financial Conduct Authority under the Money Laundering, Terrorist
Financing and Transfer of Funds (Information on the Payer) Regulations 2017 (firm reference number 989521). Registration is not equivalent to authorisation and is not an endorsement to do business with a firm. Staclar Financial Services Ltd. is not an authorised
person within the meaning of the Financial Services and Markets Act 2000 and does not review, approve, or endorse financial promotions for securities issues it is involved in or provide any form of investment advice.</span></div>
</div>
</div>
<img alt="Sent from Front" src="https://app.frontapp.com/api/1/noauth/companies/2fa1142cccd8fdcdb954/seen/msg_123sdvbe/0/4cb5711a.gif" style="width:1px; height:1px"><br>
<blockquote class="x_fa-xpxp76 x_front-blockquote" type="cite">On November 30, 2023 at 10:48 AM GMT+1
<a rel="noopener noreferrer" href="mailto:leo@vegoda.org" target="_blank">leo@vegoda.org</a> wrote:<br>
<br>
<div id="x_x_fae_123sdvbe1g6lp3">On Thu, 30 Nov 2023 at 10:44, Suresh Ramasubramanian
<br>
<<a rel="noopener noreferrer" href="mailto:ops.lists@gmail.com" target="_blank">ops.lists@gmail.com</a>> wrote:
<blockquote type="cite" class="x_fa-xpxp76 x_front-blockquote"><br>
> <br>
> The funny part is that the abuse teams of the very same companies will be out there in other conferences working earnestly and well on best practices. If they were to turn up at a ripe meeting and provide consensus ..
<br>
> <br>
> And before you accuse me of packing the room to generate artificial consensus <br>
<br>
Consensus isn't a numbers thing. I think you've misunderstood the process. <br>
<br>
Regards, <br>
<br>
Leo <br>
<br>
-- <br>
<br>
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit:
<a rel="noopener noreferrer" href="https://mailman.ripe.net/" target="_blank">
https://mailman.ripe.net/</a> <br>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</body>
</html>