<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>I need more education before I comment further.<br>How do you enforce if they are using a natted IP and your gateway is coming back as the abused address?<br>We are deploying IPv6 but it has taken years.<br>We have equipment that monitor and shapes traffic and a hard attack going through our gateway our Upstream fiber provider blacklists an incoming abusing IP<br>or shuts all of our network down inbound.<br>But outbound natted addresses using dynamic DNS, I don't have any knowledge how to stop from internal except by high consumption.<br>What other ways are there?<br><br></div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>From: </b>"Shawn Bakhtiar" <shashaness@gmail.com><br><b>To: </b>"Michael Greenup" <michael.greenup@ionos.com><br><b>Cc: </b>"arin-ppml" <ARIN-PPML@arin.net><br><b>Sent: </b>Friday, August 29, 2025 2:44:42 PM<br><b>Subject: </b>Re: [arin-ppml] Policy Proposal 2003-1: Required Performance of Abuse Contact<br></div><div><br></div><div data-marker="__QUOTED_TEXT__"><br id="lineBreakAtBeginningOfMessage"><div><br><blockquote><div>On Aug 29, 2025, at 12:02 PM, Michael Greenup <michael.greenup@ionos.com> wrote:</div><br class="Apple-interchange-newline"><div><div dir="ltr"><div><div style="font-family:monospace" class="gmail_default">Hi Shawn,</div><div style="font-family:monospace" class="gmail_default"><br></div><div style="font-family:monospace" class="gmail_default">Please allow me to clarify my position. I will happily look at any proposal you submit but like the others I am wanting to help you understand the complexities involved with this idea.</div></div></div></div></blockquote><br>I really appreciate that :)</div><div><br><blockquote><div><div dir="ltr"><div><div style="font-family:monospace" class="gmail_default"><br></div><div style="font-family:monospace" class="gmail_default">My company is, by your definition, already compliant: We issue a ticket when we receive an abuse complaint and I can assure you I have personally scoured our networks looking for abusive accounts and personally taken them offline (even before we had an abuse complaint). However, I work for a hosting provider and I can assure you, the additional overhead this will cost my company will be incredibly high. We already have to deal with DMCA requests, Better Business Bureau issues, and various other industry complaints as a cost of doing business. We accept this because we want to be good netizens. This does not mean we are perfect or that we could not find areas in which we can improve, but we actively iterate on our processes to ensure we are meeting or exceeding expectations where possible. <br></div><div style="font-family:monospace" class="gmail_default"><br></div><div style="font-family:monospace" class="gmail_default">At the same time, it seems you are not wanting to hear what others are saying either. You have your point of view which I respect and empathize with as it is both a real and expensive issue for every device, website, server, etc. owner on the Internet. Being a role model for other RIRs does not really work in practice or we would have adopted some of the policies and database functionality of RIPE (as an example). If a policy like this is to be implemented, it should really be implemented at a higher level like the IETF or even ICANN so it can apply to all RIRs.</div><div style="font-family:monospace" class="gmail_default"><br></div><div style="font-family:monospace" class="gmail_default">How many more employees should AWS, Google, or any of the other "compliant" businesses actually hire to ensure this policy is fulfilled? I mean, if you really want to know why this policy will meet resistance then understand you are asking companies to reduce their bottom line by increasing OPEX, increase their prices to cover the OPEX increase to ensure compliance thus making their product look less attractive, or even getting legitimate complaints missed because of all the malicious complaints received. </div></div></div></div></blockquote><br><div>I hear you. I appreciate everything you are saying, and more importantly doing to keep the internet safe for all of us.</div><br><div>Question:</div><div>You're doing it, AWS IS doing it (following the policy voluntarily), Digital Ocean is doing it, I use to do it, and many others are already voluntarily following the policy, which means it won't cost us anything, as you said we are compliant already. </div><br><div>Google is not and neither is Microsoft. Why do they get to not? Why do we have to deal with the extra burden of them not caring? </div><br><div>This policy would simply level the playing field. That's it, and the only ones who would have to do more, are the ones who were not following the policy.</div><br><blockquote><div><div dir="ltr"><div><div style="font-family:monospace" class="gmail_default"><br></div><div style="font-family:monospace" class="gmail_default">Believe me, the volume of spam our abuse@ email receives is ridiculous. I know of at least one person who gets angry at us every so often and goes and submits all our POC addresses to various mailing lists - and because we are "subscribed" the spam filter doesn't pick them up and just fills up the ticket queue. Again, the potential for maliciousness and abuse of such a policy is high and then you want us to be able to lose resources because we didn't respond with the correct answer to some malicious complaint? I cannot imagine any resource holder agreeing to this policy no matter how compliant they are.</div></div></div></div></blockquote><blockquote><div><div dir="ltr"><div><div style="font-family:monospace" class="gmail_default"><br></div><div style="font-family:monospace" class="gmail_default">Also a point of consideration is what will this look like from ARIN's side? What "evidence" must a complainant provide to show a good faith attempt to get the abuse resolved to open an investigation? What "evidence" will be required by ARIN to ensure the abuse@ holder did everything necessary to comply with the policy? Understand, gathering this information costs both time and employee resources for ARIN and the abuse@ holder for very low effort for the complainant. Any time you have a low effort bar for one side which turns into a high effort bar for the other is going to breed maliciousness (like a DNS reflection attack). How is your proposal going to deal with this issue?</div></div></div></div></blockquote><blockquote><div><div dir="ltr"><div><div style="font-family:monospace" class="gmail_default"><br></div><div style="font-family:monospace" class="gmail_default">Again, I look forward to reading your proposal and I really hope you will figure out how to get around these issues. Until I read your proposal though, I cannot help but be opposed to the idea in principle.</div></div></div></div></blockquote><br><div>I appreciate your consideration, and I really thank everyone who has responded to me on this list. I am beginning to understand the viewpoint, even if I am not, as of yet, convinced of the validity of the arguments.</div><br><br><blockquote><div><div dir="ltr"><div><div style="font-family:monospace" class="gmail_default">Regards,<br></div><br clear="all"></div><div><div dir="ltr" class="gmail_signature"><div dir="ltr">Michael</div><div dir="ltr"><br></div><div dir="ltr"><div style="font-family:monospace" class="gmail_default"><em>The opinions and beliefs expressed in this email are mine alone and do not reflect the opinions and beliefs of my employer.</em></div><br></div></div></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, Aug 29, 2025 at 12:56 PM Shawn Bakhtiar <<a href="mailto:shashaness@gmail.com" target="_blank" rel="nofollow noopener noreferrer">shashaness@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb( 204 , 204 , 204 );padding-left:1ex"><div>I would agree with everything you are saying, save there is one problem....<br><div>As much as I appreciate your thorough arguments, they fly in the face of reality. </div><br><div>AWS, DigitalOcean, Datapacker, and many others are following the proposed policy and succeeding in reducing the abusive behavior. I use to do it and I'm a mom and pop shop.</div><br><div>It sounds like you've already resigned yourself to defeat. </div><br><div>I believe we can revive this policy in ARIN, set an example for the rest of RIRs, and make a huge dent in the amount of useless traffic generated on the internet. </div><br><div>Everyone would benefit, and I have as of yet to hear a good argument against, given that all the arguments made so far (administratively prohibitive) are being proven wrong by all the providers that are doing it and being effective at it.</div><br><div><div><br><blockquote><div>On Aug 29, 2025, at 8:46 AM, Michael Greenup <<a href="mailto:michael.greenup@ionos.com" target="_blank" rel="nofollow noopener noreferrer">michael.greenup@ionos.com</a>> wrote:</div><br><div><div dir="ltr"><div><div style="font-family:monospace" class="gmail_default">Hi Shawn,</div><div style="font-family:monospace" class="gmail_default"><br></div><div style="font-family:monospace" class="gmail_default">In a world where DMCA takedown requests are made based on a search of keywords (and not actual content to see if there is actually any infringement), this proposal creates some significant issues for ARIN resource holders.</div><div style="font-family:monospace" class="gmail_default"><br></div><div style="font-family:monospace" class="gmail_default">I agree, a response from abuse@ should have a timely response and resolution, but the problem is the resolution might not be what the abuse@ sender is actually wanting. Just open port 22 to the Internet and watch all the brute force attacks against your device. Unfortunately, while I agree this is abuse, it is a normal reality we will face from all regions, not just the ARIN region. I could easily set up a script to record every IP and automatically send an email to every abuse@ address but that would essentially lead to my own email being spammed with responses. Honestly, nobody has time to go through all those responses to see if they are accomplishing what I want, which is that the abuse stops.<br></div><div style="font-family:monospace" class="gmail_default"><br></div><div style="font-family:monospace" class="gmail_default">Even worse, many DDoS vectors spoof an IP address in an attempt to get the spoofed source IP address flooded. Think of how a DNS reflection attack works. Currently, SHODAN shows some 90k open DNS resolvers on the Internet. All it takes is for a malicious source to spoof a source IP address and send requests to these servers to take your source IP offline. So if we follow the logic of the proposal and your view of it, ARIN should start policing DNS resolving and operators should have to prove their DNS cannot be maliciously used or forfeit their right to resolve DNS. This, however, is not the purpose of ARIN. ARIN provides resources according to established policy, but it does not dictate nor police how those IPs are to be used. <br></div><div style="font-family:monospace" class="gmail_default"><br></div><div style="font-family:monospace" class="gmail_default">The sad reality is, the Internet was never designed with security or safety in mind. Give everybody a useful tool and somebody will figure out a way to abuse it. While I resent the notion of "just through cpu/ram/money/whatever" at the problem, in some cases, we have to take on the role of sysadmin and figure out how best to protect ourselves against these malicious actors. The only thing this policy would do is create more issues for those responsible providers for doing what we are supposed to do because all it would take is one person who wrote abuse@ to make a claim to ARIN that we are not acting like a responsible provider. Multiply that by X malicious actors (something like that could be easily scripted and there are enough bot networks out there to flood ARIN) and you can see how this idea does not scale.</div><div style="font-family:monospace" class="gmail_default"><br></div><div style="font-family:monospace" class="gmail_default">Providers like spamhaus are also able to be exploited. All one needs do is talk to any email service provider to find out how quickly and easily it is to get added to any number of the spam lists out there but how difficult it is to get off the list. Something as simple as deciding I don't want to receive email from a list and reporting it to a spam list provider instead of clicking 'unsubscribe' happens unfortunately more than some like to admit.</div><div style="font-family:monospace" class="gmail_default"><br></div><div style="font-family:monospace" class="gmail_default">In other words, there is no perfect solution to this issue. I, therefore, join my fellow community members in opposing this policy.</div><div style="font-family:monospace" class="gmail_default"><br></div><div style="font-family:monospace" class="gmail_default">Regards,<br></div><br clear="all"></div><div><div dir="ltr" class="gmail_signature"><div dir="ltr">Michael </div><div dir="ltr"><br></div><div dir="ltr"><div style="font-family:monospace" class="gmail_default"><em>The opinions and beliefs expressed in this email are mine alone and do not reflect the opinions and beliefs of my employer.<br></em></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 29, 2025 at 9:32 AM Shawn Bakhtiar <<a href="mailto:shashaness@gmail.com" target="_blank" rel="nofollow noopener noreferrer">shashaness@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb( 204 , 204 , 204 );padding-left:1ex"><div>Good morning Scott, Paul,<br><div><div>I'm not sure who Matt is, so far the only reasonable response I've received have been from Bill, who's right about doing my homework on the topic, and I truly appreciate his time and effort in leading me in a good direction.</div><br><div>You and Paul's suggestion, on the other hand, to simply block / report / sue, I find completely lacking, and frankly sad.</div><br><div>Your suggestions reeks of the those supposedly (edumicated) computer engineers I see managing servers, who simply throw CPU and memory at a problems instead of caring about or addressing the underlying root cause of an issue. Do either of you run OSSEC on servers you manage?</div><br><div>Your argument is tantamount to, I don't know what to do, so I'll just kick the can down to a policing organization who actually has very little skill or ability to meaningfully do anything about it. I've been there and done that, it's all but pointless. After 40 years of government and private work (long before the modern form of the internet was even a verb), I can assure you, your suggestion is lacking at best, and.... well... let's just leave it there, before I break the protocols of politeness :)</div><br><div>it is a shirking of responsibility for an organization that claims as part of it mission statement "...member-based organization that supports the operation and growth of the Internet."</div><br><div>I would argue that letting this behavior continue would neither be supportive nor promote growth (unless we're taking about the growth of Microsoft and others who abuse their size).</div><br><div>I'm not talking about a few vulnerability scans done by Universities et al, I'm taking about being hammered by 100s of popup-script-kiddie-servers made popular by products like Kali Linux, and the fact that some providers like AWS take it seriously while others like Microsoft completely ignore emails sent to registered abuse emails. </div><br><div>It perplexes me to no bounds to see Amazon AWS (of all people), Digital Ocean, and many others, being a good netizen, and doing it (despite ARIN's inability to define a very common sense policy, responding to abuse emails, assigning support tickets, and taking action on them, while Microsoft (we all know who they are) does not, and I'm beginning to see why. </div><br><div>This I did not expect. </div><br><div>You have quickly dismissed a real concern, without engaging in any meaningful debate. If what you say is remotely true, than why does Spanhuase exists? why does Abuse Radar exists? Why are their so many REAL COMMUNITY BASED organizations forming to dealing with an very serious issue, that law enforcement has no capabilities to deal with and apparently ARIN (the very governing body of IP addresses) doesn't care to do anything about, even though a very sound and reasonable policy was written, but never adopted, probably due to naysayers like yourself and Paul.</div><br><div>Lazy and bad. <-- period!</div><br><div>Curious though, you and Paul have attempted to dismissing me quite quickly and out of hand, but if I may, why not implement the policy, what do you think is going to happen? Why would it be bad to hold abuse POCs accountable for what their IP address is doing? What hardship do you think this will cause the community, other than you personally not wanting to be responsible for the IP addresses under your charge?</div><br><div>Again, I'm not asking ARIN to police it, I'm asking them to govern it. I'm not asking for people to be sent to jail or fined, I'm asking for the governing body to take action in stopping the behavior (preferable without the need for behemoth, slow, broadsword agencies like law enforcement having to get involved, they have a whole lot of issues they need to fix before they can even approach an issue like this).</div><br><div>I've been a POC for more than my fare share of ranges, I don't recall this ever being in issue, and I know I took my responsibility for the IP addresses under my charge very seriously. I would create a ticket, follow up with my end users, and if deemed inappropriate or against our policy, their privileges would be revoked. </div><br><div>Telling me that ARIN isn't the police is like telling me the sky is not green. Obviously. </div><br><div>However, it is the governing body, for the assignment of IP addresses. If the idea behind the abuse email was NOT to have it used to take down bad actors, then why even have it at all?</div><br><div>Why are some organization voluntarily doing what you and Paul find so offensive a policy, and why are you and Paul so much against it, other than a blanket statement the ARIN is not the police (again this obvious). However IT IS the governing body, and does bear responsibility for how the community behaves.</div><br><div>Honestly curious,</div><div>Shawn</div><br><br><br><div><blockquote><div>On Aug 28, 2025, at 5:14 PM, Scott Leibrand <<a href="mailto:scottleibrand@gmail.com" target="_blank" rel="nofollow noopener noreferrer">scottleibrand@gmail.com</a>> wrote:</div><br><div><div dir="ltr">Just block them, as Matt suggested. Or sue them, if they're harming your business in some meaningful way that can't be trivially handled by blocking their abusive subnets. Or contact law enforcement if there's actual criminal trespass or some other law being broken.<br><div>ARIN is not set up to be the Internet police, and I would oppose any efforts to make it try to play that role. As Matt eloquently elucidated, any requirements ARIN could enforce would likely make things worse for everyone holding ARIN IP addresses for very little tangible social benefit.</div><br><div>-Scott</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Aug 28, 2025 at 4:57 PM Shawn Bakhtiar <<a href="mailto:shashaness@gmail.com" target="_blank" rel="nofollow noopener noreferrer">shashaness@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb( 204 , 204 , 204 );padding-left:1ex">Thank You Bill!<br>
<br>
I really appreciate the input, and these are all great suggestions. I will certainly do my homework and reach out again to the group with more specific questions on the topic. <br>
<br>
As I said in my email to Alison, <br>
<br>
AWS (of all people), auto responds to any email sent to the abuse email on record for a given IP segment. It includes a ticket number, and without me having to follow up (usually a few days later) an email back often having remediated the issue, or in the rare instances where the they did not remedy the issue, explaining why the behavior is not abuse or a violation of their policies. <br>
<br>
Digital Ocean does the same thing (without a ticket number). So do several midsize providers. Hit and miss with anything smaller than a /24.<br>
<br>
Microsoft (where the preponderance of abusive behaviors come from) and Google. Do nothing. Literally nothing. I have OSSEC notification logs in which a single IP address with a Microsoft abuse POC, continues to scan different customer's networks, looking for Wordpress vulnerabilities, and has done so for over a month, without any remediation. <br>
<br>
The aforementioned policy is a common sense one already being (voluntarily) done by a good number of the providers out there. I am very curious as to what objections anyone could have to it, and how we can address those concerns so we can put what seems like a very common sense policy into place. We need to bring accountability back to the internet.<br>
<br>
Again, thank you for the guidance, I look forward to any and all questions, comments, and or concerns.<br>
<br>
> On Aug 28, 2025, at 3:24 AM, William Herrin <<a href="mailto:bill@herrin.us" target="_blank" rel="nofollow noopener noreferrer">bill@herrin.us</a>> wrote:<br>
> <br>
> On Wed, Aug 27, 2025 at 11:45 AM Shawn Bakhtiar <<a href="mailto:shashaness@gmail.com" target="_blank" rel="nofollow noopener noreferrer">shashaness@gmail.com</a>> wrote:<br>
>> I would like to re-introduce the following Policy Proposal from 2003 to hold abuse POCs accountable.<br>
>> <a href="https://www.arin.net/vault/participate/policy/drafts/2003/2003_1/" rel="noreferrer nofollow noopener noreferrer" target="_blank">https://www.arin.net/vault/participate/policy/drafts/2003/2003_1/</a><br>
> <br>
>>> Changes to ARIN’s policies may be made via submission of a policy proposal<br>
>>> via ARIN’s Policy Devcelopment Process - more details available here<br>
>>> - <a href="https://www.arin.net/participate/policy/pdp/" rel="noreferrer nofollow noopener noreferrer" target="_blank">https://www.arin.net/participate/policy/pdp/</a><br>
> <br>
> Hi Shawn,<br>
> <br>
> I note that the practical question of "how do I submit a policy<br>
> proposal" is not answered in<br>
> <a href="https://www.arin.net/participate/policy/pdp/" rel="noreferrer nofollow noopener noreferrer" target="_blank">https://www.arin.net/participate/policy/pdp/</a>, or if it is, it's buried<br>
> so deeply I can't find it.<br>
> <br>
> What you probably want is the policy proposal template, which you can<br>
> find here: <a href="https://www.arin.net/participate/policy/pdp/appendix_b/" rel="noreferrer nofollow noopener noreferrer" target="_blank">https://www.arin.net/participate/policy/pdp/appendix_b/</a><br>
> <br>
> You can also discuss policy changes here on the mailing list without<br>
> making a formal proposal. That would enable you to gather information<br>
> which could inform a formal proposal.<br>
> <br>
> I recommend you sift through the mailing list archives at<br>
> <a href="https://lists.arin.net/pipermail/arin-ppml/" rel="noreferrer nofollow noopener noreferrer" target="_blank">https://lists.arin.net/pipermail/arin-ppml/</a> and read the original<br>
> discussions around proposal 2003-1. This can help you understand what<br>
> defects in that proposal led to it failing to reach consensus.<br>
> <br>
> Finally, I note that there have been other off and on discussions<br>
> about the published POCs and their utility. It might be worth digging<br>
> into them as well. Try a Google search such as, "site:<a href="http://lists.arin.net/" rel="noreferrer nofollow noopener noreferrer" target="_blank">lists.arin.net</a><br>
> abuse poc"<br>
> <br>
> Regards,<br>
> Bill Herrin<br>
> <br>
> <br>
> <br>
> -- <br>
> William Herrin<br>
> <a href="mailto:bill@herrin.us" target="_blank" rel="nofollow noopener noreferrer">bill@herrin.us</a><br>
> <a href="https://bill.herrin.us/" rel="noreferrer nofollow noopener noreferrer" target="_blank">https://bill.herrin.us/</a><br>
<br>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank" rel="nofollow noopener noreferrer">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer nofollow noopener noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank" rel="nofollow noopener noreferrer">info@arin.net</a> if you experience any issues.<br>
</blockquote></div>
</div></blockquote></div><br></div></div>_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank" rel="nofollow noopener noreferrer">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer nofollow noopener noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank" rel="nofollow noopener noreferrer">info@arin.net</a> if you experience any issues.<br>
</blockquote></div>
</div></blockquote></div><br></div></div></blockquote></div>
</div></blockquote></div><br><br>_______________________________________________<br>ARIN-PPML<br>You are receiving this message because you are subscribed to<br>the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).<br>Unsubscribe or manage your mailing list subscription at:<br>https://lists.arin.net/mailman/listinfo/arin-ppml<br>Please contact info@arin.net if you experience any issues.<br></div></div></body></html>