Skip to main content

Draft of DRAFT: Frequent Database Update Request

This policy proposal has been withdrawn
Go back to Frequent Update Request

1.0 Notification Request

Once every 12 months, the RIPE NCC will send an update notification request to the maintainers of all inetnum, inet6num and aut-num objects directly allocated by the RIPE NCC.

This notification will explain that maintainers must log into the LIR Portal and verify all objects that are directly linked to the above mentioned inetnum, inet6num and aut-num objects.

The database objects to be considered are:

  • inetnum
  • inet6num
  • aut-num
  • person
  • role
  • organisation
  • irt

Maintainers must actively click and acknowledge the correctness of the objects for which they are responsible.

  • Any necessary updates or additions of new objects (for whatever reason) should be done.

Even if the owner only verifies existing data and has not made any changes, the "changed:" attribute in the RIPE Database objects will include the date the owner verified the object. This will give users of whois an idea on how recently the object owner verified the accuracy of the data.

If the RIPE NCC becomes aware that the database object contains invalid information, update notifications to responsible organisations will be sent at all times.

The RIPE NCC will offer a webform that gives whois users the ability to report invalid whois objects.

1.2 Non-responsive Maintainers

The RIPE NCC will handle non-responsive maintainers in the following way:

  • Maintainers will have 60 days from the time of any initial message from the RIPE NCC to confirm that their objects are up to date.
  • If the maintainer does not respond to the initial message, reminder emails will be sent 10, 30 and 50 days after the original email.
  • After the 60-day period has passed, if the object owner has not verified their object details, the RIPE NCC will add the ranges of resources maintained by the non-responsive object owner to the publicly available list of resources described in 1.3 below.

1.3 Maintainer Lists

The RIPE NCC will maintain two publicly available lists:

  • Resources associated with non-responsive object owners
    • This list would include resources associated with maintainers who have not responded to the RIPE NCC's requests as described in section 1.2 above.
  • Resources associated with known invalid contact details.
    • This list would include resources that have been reported to contain invalid contact details. It is left to the discretion of the RIPE NCC whether to include an explicit remark in the corresponding database objects to show that the information in the objects is invalid.