<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFCC">
<font face="monospace">I would support getting a proper standard
format/api/whatever in place for all the RIR's to agree on. And
yes, that's outside our scope but that doesn't mean it can't be
done.<br>
<br>
Then, and only then, replace what we have. Otherwise, things will
just get worse.<br>
<br>
This proposal isn't a path forward, it's sideways into the muck.<br>
<br>
-lee<br>
</font><br>
<div class="moz-cite-prefix">On 10/27/2021 12:51 PM, David Farmer
via ARIN-PPML wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAN-Dau1ZOVmseTycBhuocCfoLL8xmvH10EZN9uOVjW62oHo+tQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>And <a class="moz-txt-link-rfc2396E" href="tel:123-456-7890">"tel:123-456-7890"</a> is a URL for a phone number.
However, that means to replace the current POC info you need
at least two URLs and probably more if you want to support a
web form and possibly an API option. But I don't believe a
single URL is a viable solution. </div>
<div><br>
</div>
<div>But then, with multiple URLs there becomes a question of
order of preference. Which does the entity providing the URLs
prefer and in what order? Furthermore, if you provide only a
Web Form or API URL, where do you call or email if it seems to
have gone wrong? </div>
<div><br>
</div>
<div>Simply changing the Abuse Contact to a URL isn't
necessarily going to make things better, and it could make
things much worse. While this could allow those that want to
be responsive to increase their responsiveness, however, I
fear that it also allows those that want to be unresponsive to
obfuscate things even more than is possible today. </div>
<div><br>
</div>
<div>Having staff translate the current POC data to URLs is a
reasonable transition strategy on the data production side of
things. But a flag day on the data consumption side, would be
unacceptable, at least in my opinion. So, there would need to
be an overlap where both the Abuse POC and Abuse URL Data are
available, and I think we are talking about multiple years of
overlap. Further, for at least for part of that time those
that want to provide only an Abuse URL would still need to
provide an Abuse POC. <br>
</div>
<div><br>
</div>
<div>There are many users of the current Abuse POC, and an
abrupt change in the format of this data is not acceptable in
my opinion. So, while I support work in this area, some
changes are most definitely needed, and long-term this seems
like the right direction, nevertheless, we need to proceed
very carefully. Therefore, without at least a more detailed
and lengthy transition plan, I can not support any proposal
that effectively eliminates the Abuse POC as we know it today.
I would support the addition of a URL option, without the
elimination of the Abuse POC at this time.</div>
<div><br>
</div>
<div>Thanks. </div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Oct 27, 2021 at 2:10
AM William Herrin <<a href="mailto:bill@herrin.us"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">bill@herrin.us</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">On Tue, Oct 26, 2021 at
2:59 PM John Santos <<a href="mailto:john@egh.com"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">john@egh.com</a>> wrote:<br>
> My domain has a valid abuse contact (me), and it's been
years since I actually<br>
> received anything except spam. (I check the spam
detector output daily to make<br>
> sure it actually is spam, and it always is. It's
usually no more than a handful<br>
> of spam emails daily, probably because I never respond
to it or originate any<br>
> email from the "abuse" address, so there is nothing for
the spammers to harvest.)<br>
><br>
> Under this new scheme, would I still be able to handle
abuse the exact same way?<br>
<br>
Hi John,<br>
<br>
"mailto:<a href="mailto:your@address" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">your@address</a>"
is a valid URL, is it not?<br>
<br>
<br>
>> Initial implementation suggested to replace the
abuse POC with a URL<br>
>> pointing to ARIN’s display of the same POC record
which was used for<br>
>> abuse reporting. Should support multiple URLs so
that if desired an<br>
>> organization can specify both “mailto:<a
href="mailto:somebody@here" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">somebody@here</a>”
and<br>
>> “<a class="moz-txt-link-freetext" href="tel:1234567”">tel:1234567”</a> if that’s how they actually want
abuse reported to them.<br>
<br>
Regards,<br>
Bill Herrin<br>
<br>
<br>
-- <br>
William Herrin<br>
<a href="mailto:bill@herrin.us" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">bill@herrin.us</a><br>
<a href="https://bill.herrin.us/" rel="noreferrer"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://bill.herrin.us/</a><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"
moz-do-not-send="true" class="moz-txt-link-freetext">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" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">info@arin.net</a> if you
experience any issues.<br>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr">===============================================<br>
David Farmer <a
href="mailto:Email%3Afarmer@umn.edu" target="_blank"
moz-do-not-send="true">Email:farmer@umn.edu</a><br>
Networking & Telecommunication Services<br>
Office of Information Technology<br>
University of Minnesota <br>
2218 University Ave SE Phone: 612-626-0815<br>
Minneapolis, MN 55414-3029 Cell: 612-812-9952<br>
=============================================== </div>
<div dir="ltr"><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.
</pre>
</blockquote>
<br>
</body>
</html>