[arin-ppml] Snarl: Using ARIN Contacts to report abuse.
sdean at bard.edu
Mon Nov 3 13:51:11 EST 2008
What is wrong with sending something to abuse, if only a copy? This is
the canonical forever way to do it, if only a copy; it's in the
dad-cussed RFC whatever...not that anybody follows them, gripe, gripe. I
know, we don't really need standards, everyone whould just wing it as
best he or she sees fit.
When I came to make the change from people to symbolic POCs (because our
IT head changed), I just updated the the existing POCs
individually...there was no abuse POC in our long extant whois listing.
It might help if the POC update template from indicated a list of POC
roles as a hint. This a gotcha.
I *really* try to get things right, and this feels gratuitous.
I'll just sit over here in my corner and munch more sour grapes........
David Farmer wrote:
> I looked up your Org entry, you should add an Abuse POC handle, you only
> have an Admin POC Handle and 2 Tech POC Handles. By not having an
> abuse handle your not telling people that you want abuse complaints sent
> somewhere else. Without an Abuse POC I would probably send abuse
> complaints to your Tech POC Handles, because if you don't publish your
> abuse contact information why would I assume you even have one?
> I suspect if you publish an Abuse POC you will see abuse complaints go
> "Abuse POC Handle: Indicate the ARIN POC handle of a contact
> responsible for handling operational aspects of the acceptable or
> appropriate uses of the allocated network. The abuse POC may not make
> modifications to the allocated network registration. "
> On 3 Nov 2008 Stewart Dean wrote:
>> I am increasingly seeing that abuse-related comments are going to our
>> ARIN whois info contacts instead of abuse@<domain>. ...this seems to be
>> the new thing....I guess they figure that this way they'll get someone,
>> since these addresses are explicitly listed, where abuse@<domain> is one
>> of the implicitly (by RFC standard) required, but not always incarnated
>> Damn. This is one of those expedient, but wrong way to do things, but
>> everyone is adopting it.
>> It's fortunate that I made the contacts symbolic aliases (iptech,
>> ipadmin, ipbill) instead of actual people's names. At least this way we
>> can send it to multiple people...otherwise, if it was going to an actual
>> user, we'd have to rely on that person to fwd..........which wouldn't
>> happen when they were on vacation.
>> ==== Once upon a time, the Internet was a friendly,
>> neighbors-helping-neighbors small town, and no one locked their doors.
>> Now it's like an apartment in Bed-Stuy: you need three heavy duty
>> pick-proof locks, one of those braces that goes from the lock to the
>> floor, and bars on the windows....
>> ==== Stewart Dean, Unix System Admin, Bard College, New York 12504
>> sdean at bard.edu voice: 845-758-7475, fax: 845-758-7035
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
>> Unsubscribe or manage your mailing list subscription at:
>> Please contact info at arin.net if you experience any issues.
> David Farmer Email: farmer at umn.edu
> Office of Information Technology
> Networking & Telecomunication Services
> University of Minnesota Phone: 612-626-0815
> 2218 University Ave SE Cell: 612-812-9952
> Minneapolis, MN 55414-3029 FAX: 612-626-1818
==== Once upon a time, the Internet was a friendly,
neighbors-helping-neighbors small town, and no one locked their doors.
Now it's like an apartment in Bed-Stuy: you need three heavy duty
pick-proof locks, one of those braces that goes from the lock to the
floor, and bars on the windows.... ==== Stewart Dean, Unix System Admin,
Bard College, New York 12504 sdean at bard.edu voice: 845-758-7475, fax:
More information about the ARIN-PPML