This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[anti-abuse-wg] Sources of Abuse Contact Info For Abuse Handlers
- Previous message (by thread): [anti-abuse-wg] Sources of Abuse Contact Info For Abuse Handlers
- Next message (by thread): [anti-abuse-wg] Sources of Abuse Contact Info For Abuse Handlers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
de =?utf-8?q?Br=C3=BCn?=, Markus
markus.debruen at bsi.bund.de
Wed Nov 18 17:01:30 CET 2015
I also would like to thank the authours of this document. I think the document is well written and contains useful information. Speaking in IETF terms I would consider this document to be "informational" though, and not "bcp". A few remarks: Sources like TI or FIRST are useful if you are looking for national CERT contacts. If you want to report an issue to network operators or hosting providers directly, you have to use Whois information. Unfortunately, there are still lots of CIDRs for which the RIPE DB does not return a dedicated abuse contact. In some cases, you can find an appropriate contact in the "remarks" or other records - which is difficult to parse automatically. In other cases there is no contact information at all. Section 6.6.1 of this document says that "it [is] mandatory for every resource object (inetnum, inet6num and aut-num) to have a dedicated abuse contact." <nitpicking> ripe-563 states that "every direct allocated inetnum and inet6num needs to have an “abuse-c:”", which is different from "every" as is the quote above. </nitpicking> In fact, afaik you cannot add an abuse-c record to an inetnum object at all, can you? abuse-c records are usually added to higher level objects like LIR ORG and then inherited by the lower level inetnum objects. If you want to set a dedicated abuse-contact for an inetnum, you need to add a reference to an ORG object with the corresponding abuse-c record. (see https://labs.ripe.net/Members/denis/creating-and-finding-abuse-contacts-in-the-ripe-database) Cheers, Markus -- Markus de Brün Federal Office for Information Security, Germany __________ ursprüngliche Nachricht __________ Von: Brian Nisbet <brian.nisbet at heanet.ie> Datum: Montag, 16. November 2015, 16:33:30 An: anti-abuse-wg at ripe.net Kopie: Betr.: [anti-abuse-wg] Sources of Abuse Contact Info For Abuse Handlers > Colleagues, > > Mirjam Kuehne, L. Aaron Kaplan and Christian Teuschel have been doing a > lot of work on a document on "Sources of Abuse Contact Info For Abuse > Handlers". Versions of this document have been sent to the WG over the > past year. > > There has been a lot of input from a lot of people and organisations and > we'd like to thank them all. > > At this point it is our intend to publish this as a BCP RIPE Document > from the AA-WG. > > At this point we would like to invite any final comments from the WG (a > last call of sorts) before it is published. Ideally these comments would > be great before the WG Session at 11:00 EET on Thursday 19th November, > but definitely before the end of this week. > > Thanks again to all involved. > > Brian > Co-Chair, RIPE Anti-Abuse WG -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part. URL: </ripe/mail/archives/anti-abuse-wg/attachments/20151118/8a2711c9/attachment.sig>
- Previous message (by thread): [anti-abuse-wg] Sources of Abuse Contact Info For Abuse Handlers
- Next message (by thread): [anti-abuse-wg] Sources of Abuse Contact Info For Abuse Handlers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]