Hi Ronald, wg, Forgive me for top-posting, but rather than going into the details of the reported objects, I wanted to remind you all that the decision to lock these objects was not taken lightly. It was necessary to prevent hijacking of the legitimate objects that are there: https://www.ripe.net/ripe/mail/archives/ncc-announce/2016-April/001035.html As mentioned in this email: "The legitimate holder of the resources of these objects can contact ripe-dbm@ripe.net in case the objects need to be unlocked.". So either the out-of-region prefix holder, or the out-of-region AS holder can contact ripe-dbm@ripe.net, to get their own maintainer on locked objects. The more fundamental problem of out-of-region objects in the RIPE Database IRR is the subject of two numbered work items: NWI-3 - AFRINIC IRR Homing: https://www.ripe.net/ripe/mail/archives/db-wg/2016-May/005241.html This item seeks to improve the situation for the 'simple' cases where both the prefix and AS holder are in the Afrinic region. Consensus was called on the problem definition, but not yet reached on the proposed solution. NWI-5 - Out of region ROUTE(6) / AUT-NUM objects: https://www.ripe.net/ripe/mail/archives/db-wg/2016-May/005245.html This item is a problem definition for the more general issue. Consensus on a precise problem definition was not yet reached, and therefore specific (possibly even partial) solutions have not been discussed in detail yet in that thread. In either case I would like to re-assure everyone that no one at RIPE NCC is particularly happy with the situation that exists. But we need to have a clear discussion with the WG and have clear consensus on ways forward in order to be able to address this. Kind regards Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group
On 21 Nov 2016, at 12:46, fransossen@yahoo.com wrote:
Hi Ronald,
The following does not help you in your quest, but you highlighted one problem in the RIPE Database. It is unfortunately something that has happened many times over over the years in the RIPE Database:
"remarks: http://www.ripe.net/db/none-deprecation-042004.html" "remarks: For information on "status:" attribute read https://www.ripe.net/data-tools/db/faq/faq-status-values-legacy-resources, status=LEGACY" "remarks: http://www.ripe.net/db/support/security/domain/syntax.html" "remarks: MD5 passwords older than November 2011 were removed from this maintainer, see: https://www.ripe.net/removed2011pw" "remarks: Auth lines removed by ripe-dbm@ripe.net on 19/8/2002"
"remarks: Please see http://www.ripe.net/db/mailfrom.html for explanation"
Remarks: attribute being added during a "clean up" or implementation project. They projects are mainly successful but you are then left with lots of "remarks:" trying to explain why and what, many of them with now broken links and no follow up on removing the remarks after X amount of months/years/decades when the information is no longer relevant.
One of the more recent and still being added is the "legacy status:" on AS numbers. It is still being added to new AS numbers, even though it has been years since the Status attribute was added to AS numbers. Maybe it is time to stop adding it? And also time to remove it from all objects where it was added?
The URL will eventually reach the URL graveyard and will only be there as a reminder that something was done once upon a time with zero information value other than confusion to any users.
The other cleanup and implementation URLs are so old that they also make very little sense to still be there in general.
From Job's email.
enroll in the online academy: https://academy.ripe.net
The online courses from the academy are free and open to anyone.
or follow one of the online courses: https://lirportal.ripe.net/training/register/courseCode/WEB20160037 (all dates here: https://lirportal.ripe.net/training/courses)
The training courses in a class are free, but require an active RegID (to be a RIPE NCC member) to signup for you to able to attend.
Cheers, David Hilario