FAQs for abuse-c
- How did you communicate these plans to RIPE NCC members?
RIPE NCC members received several email requests to set an "abuse-c:" attribute for their resources, including in May 2013, August 2013 and November 2013. Until 30 November 2013, LIRs had the opportunity to set their own "abuse-c:" attribute for allocated (PA) resources, either using an existing role object or creating a new role object for this purpose, and choose which email address would be used for reporting abuse.
PI and ASN resource holders will start receiving emails in early 2014 asking them to set an "abuse-c:" attribute for their resources.
- How can I see what email address is currently being used to report abuse for the resources I hold?
- How do I change the email address being used to report abuse for my resources?
The abuse email address is contained in the "abuse-mailbox:" attribute in a role object. It is this role object that is referenced by the "abuse-c:" attribute in the organisation object. That means in order to change the email address used, you need to change the relevant role object containing the "abuse-mailbox:" attribute.
Both RIPE NCC members and PI or ASN resource holders can update the "abuse-mailbox:" attribute in the relevant role object using the Webupdates tool.
1. Look up your organisation object in the RIPE Database
2. Check which role object has been created for you in the "abuse-c:" attribute. Note the NIC handle of this role account.
3. Go to the Webupdates tool
4. Search for: NIC Handle role object > object type: role > click on search
5. Edit the email address in the "abuse-mailbox:" attribute
6. Click edit and your abuse contact has now been changed
- How do I change my "abuse-c:" attribute to reference a different role object?
Note: You do not need to update the "abuse-c:" attribute in order to update the email address used for your abuse contact. To change the email address, you simply need to update the role object. See this FAQ about how to do that.
However, you might wish to change the "abuse-c:" attribute itself. For example, you might want to change the role object that your "abuse-c:" references. Please ensure you do the following when updating your "abuse-c:" attribute:
RIPE NCC members:
- Make sure you have set up the default maintainer for your LIR
- Update your organisation object using any RIPE Database update method you prefer
PI assignments, ASNs and PA created out of your allocation:
- Search for your organisation in the Webupdates tool
- Update the referenced role object in the "abuse-c:" attribute
- How do I set abuse-c for my PI space or ASN?
The abuse email address is contained in the "abuse-mailbox:" attribute in a role object. It is this role object that is referenced by the "abuse-c:" attribute in the organisation object. This has to be done for all the organisation objects linked to the resources you manage.
First make sure you have created an organsiation object for the assignment and that it is also referenced in the assignment itself.
To update your organisation with an abuse contact:
- Go to the RIPE Database Query page and search for your organisation object
- Click Update beside the object
- In webupdates, find the "abuse-c:" attribute and enter a value
- If you have an existing role object with an abuse-mailbox, enter the nic-hdl of the role
- If you do not have an existing role object, enter an email address (an abuse-c role will be created for you)
- How do I set abuse-c for an assignment (PA) created out of my allocation?
If you have delegated responsibility for handling abuse to a customer for the part of your network they use, they need a similar set-up to your own. Either you can set this up for them, if you maintain all the RIPE Database objects, or they can partly set it up themselves. However, in most cases, you will maintain the inet(6)num assignment objects, so you will have to add the organisation reference to these objects.
You first need a role object for the customer and it must contain an "abuse-mailbox:" attribute. If the customer already has one, you can use that one. Otherwise, you will need to create a new one. This role object does not need to reference any person objects. It will be public with no query limits, so all information it contains is assumed to be business data, not personal or private data.
When creating a new organisation object with "org-type: OTHER" or editing an existing one using Webupdates, you will be able to search for an existing abuse role account in the "abuse-c:" attribute, or create a new one seamlessly.
Finally, reference this organisation object in the customer's assignment object(s). Any query for the customer's IP address(es) will now return their abuse contact details instead of the contact details you set up for the parent allocation.