[arin-ppml] ARIN 2021-7
Amy Potter
amybpotter at gmail.com
Thu Jun 16 13:17:37 EDT 2022
Hi all,
Just wanted to check in with the community to see if there is any feedback
on our latest draft of 2021-7. We've adjusted the language to clear up the
problem statement and clarify that an optional abuse field for a
machine-readable URI will be added to the abuse POC.
*Problem Statement:*
The current abuse contact fields are not sufficient for the abuse reporting
mechanisms most frequently used today. For many network providers, the
process for dealing with network abuse usually starts with a web page. The
web page provides instructions and may offer forms for describing the abuse
and uploading supporting material of the nature that the service provider
needs in order to take action. It would be helpful for these organizations
if the abuse contact had a specific field for a machine-readable abuse URI.
*Policy statement:*
Section 2.12- add “Organizations may provide an optional machine-readable
abuse URI for reporting abuse” to end of paragraph.
Section 4.2.3.7.3.2: add “and may have an optional machine-readable abuse
URI” after “Each private downstream residential reassignment must have
accurate upstream Abuse and Technical POCs” so the sentence reads…
“Each private downstream residential reassignment must have accurate
upstream Abuse and Technical POCs and may have an optional machine-readable
abuse URI visible on the WHOIS or Distributed Information Service record
for that block.”
Section 6.5.5.3.1: add “and may have an optional machine-readable abuse
URI” after “Each private downstream residential reassignment must have
accurate upstream Abuse and Technical POCs” so that the sentence reads
“Each private downstream residential reassignment must have accurate
upstream Abuse and Technical POCs and may have an optional machine-readable
abuse URI visible on the WHOIS or Distributed Information Service record
for that block.”
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20220616/08cc97df/attachment.htm>
More information about the ARIN-PPML
mailing list