[acm-tf] Abuse Contact Information - Policy Proposal
Alessandro Vesely vesely at tana.it
Wed Sep 21 17:32:26 CEST 2011
A add some +1s to agree with Tobias' text, and propose a few changes. On 21/Sep/11 11:45, Tobias Knecht wrote: > ##### > > Summary of the proposal: > > This is a proposal to introduce a new contact attribute named abuse-c, > which can be references by inetnum, inet6num and aut-num objects. +1 > It provides a more accurate and efficient way for abuse reports to > reach the correct network contact It is more efficient for the maintainers. Isn't this the most relevant change with respect to abuse-mailbox? > and helps reporting institutions to find the correct abuse contact > information more easily. +1 > ##### > > Summary of the current problem: > > Network owners increasingly operate dedicated abuse handling > departments, distinct from the basic operations department. +1 > More and more network owners and other institutions are also starting to > exchange data about abusive behavior with each other, to more quickly > allow networks to identify internal abuse, external abuse, and other > security problems. +1 > Currently within the RIPE region, the biggest problem for network > operators is to know the best place to publish abuse contact information > (irt, "abuse-mailbox:", "remark-fields:", and in addition to that, in > which object they should publish them?). On the other hand abuse > reporting parties having a huge problem with finding a correct abuse > contact in the variety of possibilities. Hm... I'd reword this slightly. E.g. like so Currently within the RIPE region, /it is a problem/ for network operators /to determine/ the best place to publish abuse contact information (irt, "abuse-mailbox:", "remark-fields:", and in addition to that, in which object they should publish them?). /As a consequence, it is a huge problem for/ abuse reporting parties /to find the/ correct abuse contact in the variety of possibilities. > This proposal will help to stop uncontrolled growth and solves the above > mentioned problems. +1, but we should avoid effects like http://www.xkcd.com/927/ > ##### > > Situation in other RIRs > > AfriNIC: > Policy Proposal AFPUB-2010-GEN-006 is awaiting implementation. > http://www.afrinic.net/docs/policies/AFPUB-2010-GEN-006-draft-02.htm > > APNIC > Policy Proposal "prop-079: Abuse contact information" was implemented in > November 2010. > http://www.apnic.net/policy/proposals/prop-079 > > ARIN: > An abuse-POC exists for Organisational ID identifiers. > https://www.arin.net/knowledge/database.html#abusepoc > ARIN decided to make abuse-c mandatory. > https://www.arin.net/announcements/2011/20110718.html > > LACNIC: > An "abuse-c:" exists for aut-num, inetnum and inet6num objects. > http://lacnic.net/en/politicas/manual4.html +1 > #####
[ Acm-tf Archives ]