<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>“I would support the addition of a URL option, without the elimination of the Abuse POC at this time.”<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Me too. +1<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Regards,<o:p></o:p></p><p class=MsoNormal>Mike Burns<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> ARIN-PPML <arin-ppml-bounces@arin.net> <b>On Behalf Of </b>David Farmer via ARIN-PPML<br><b>Sent:</b> Wednesday, October 27, 2021 12:51 PM<br><b>To:</b> William Herrin <bill@herrin.us><br><b>Cc:</b> arin-ppml@arin.net<br><b>Subject:</b> Re: [arin-ppml] Draft Policy ARIN-2021-7: Make Abuse Contact Useful<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>And "<a 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. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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? <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Wed, Oct 27, 2021 at 2:10 AM William Herrin <<a href="mailto:bill@herrin.us" target="_blank">bill@herrin.us</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal>On Tue, Oct 26, 2021 at 2:59 PM John Santos <<a href="mailto:john@egh.com" target="_blank">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">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">somebody@here</a>” and<br>>> “<a 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">bill@herrin.us</a><br><a href="https://bill.herrin.us/" target="_blank">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">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" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<o:p></o:p></p></blockquote></div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>-- <o:p></o:p></p><div><p class=MsoNormal>===============================================<br>David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">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>=============================================== <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>