RIPE Policy Proposal 2006-04

This proposal suggests that working and up-to-date contact e-mail addresses should be maintained at all times for address space that is registered in the RIPE Database.

a. Current (if modify):

4.0 Registration Requirements

...
...Registration data (range, contact information, status etc.) must be correct at all times (i.e. they have to be maintained).

b. New:

4.0 Registration Requirements

...
...Registration data (range, contact information, status etc.) must be correct at all times (i.e. they have to be maintained). Every organisation controlling an IP address should provide at least one working contact e-mail address where notifications of abuse emanating from that IP address can be sent.

All persons and organisations assigned an IP address should act to prevent abusive messages originating from that IP address.

a. Arguments Supporting the Proposal

From time to time, our security department has had to expend considerable effort to find working e-mail addresses for organisations responsible for IP addresses registered in the RIPE Database. In some instances, no working address could be found or a time consuming visit to a website was required to make contact.

By making the wording of the existing policy about contact information in the RIPE Database more explicit, we should see less spam and abuse and more rapid correction in network operations.

b. Arguments Opposing the Proposal

RIPE Documents already require documentation to be maintained, which implies "correct documentation.