Hi Billy

The reclaim functionality does cover the related routing and reverse delegation objects. That is what it was introduced for. The point you are missing is that it ONLY applies to resource objects where the RIPE NCC has a contractual relationship with the resource holder (or their sponsoring organisation) for that resource. If you want this functionality for legacy address space I suspect you need to consider the address policy issues before looking at database technical issues.

cheers
denis
independent netizen

From: William Sylvester <william.sylvester@addrex.net>
To: denis walker <ripedenis@yahoo.co.uk>
Cc: "db-wg@ripe.net" <db-wg@ripe.net>; Shane Kerr <shane@time-travellers.org>
Sent: Friday, 1 May 2015, 14:28
Subject: Re: [db-wg] Proposal regarding Orphaned Objects

Denis, 

Just to be clear, this proposal is specifically for objects related to an inetnum like routing and in-addr where the maintainer is not the same as the maintainer of the inetnum. This problem is especially problematic for legacy resources. How would you better describe the situation where an object has a maintainer who is not accurately maintaining their objects? What process should a inetnum holder be subjected to for full control over their resource? In the use case of wanting to move from one service provider to another, should the inetnum holder/maintainer be able to manage and maintain their own resources? Including for example their routing objects? 

One could also classify these as stale records versus orphaned. Regardless of the terminology the outcome is the same. These objects are not accurate and impede an inetnum holder from using their space. The intent of the proposal is to both increase database accuracy and enable inetnum holders to be better able to maintain all the aspects of their inetnum number block and related objects. I agree that contact objects containing personal or contact data should not be modifiable. 

Thanks,
Billy




On May 1, 2015, at 6:56 AM, denis walker <ripedenis@yahoo.co.uk> wrote:

HI

Shane is correct. This functionality already exists and allows resource holders of resources allocated or assigned by the RIPE NCC to delete any operational object within their address space. Note that this functionality does not apply to any objects containing personal or contact details. Also it only applies to resource objects where the RIPE NCC has a contractual relationship with the resource holder (or their sponsoring organisation) for that resource.

Just to add a caveat regarding orphaned objects, just because an object has not been updated in a very long time does not make it orphaned, even if the original maintainers are unresponsive.

cheers
denis
independent netizen



Date: Fri, 1 May 2015 09:02:23 +0000
From: Shane Kerr <shane@time-travellers.org>
To: William Sylvester <william.sylvester@addrex.net>
Cc: db-wg@ripe.net
Subject: Re: [db-wg] Proposal regarding Orphaned Objects
Message-ID: <20150501090223.0427845f@vulcan.home.time-travellers.org>
Content-Type: text/plain; charset=US-ASCII

William,

On Tue, 28 Apr 2015 14:32:33 -0400
William Sylvester <william.sylvester@addrex.net> wrote:

> Currently, when a number block holder wishes to update their number
> block they are unable to do so directly. They must contact the
> maintainer of the old object. Many of the older maintainers do not
> have current contact or have been acquired by another company and
> left in an unknown orphaned status. These maintainers can be
> difficult or impossible to contact. RIPE NCC then must be engaged to
> make the change to an object the number block holder should have had
> online access to manage directly in the first place.

As I understand it, the database allows the maintainer of
less-specific ("parent") inetnum or inet6num objects to delete
more-specific ("child") objects.

So, the recipient of either an allocation or assignment from the RIPE
NCC already has the power to clean up their space.

I believe this sort of delete functionality also applies to route and
related domain (meaning reverse DNS) objects.

https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-database-documentation-1.79/10-authorisation/10-13-reclaim-functionality-1/10-13-2-authorisation-to-reclaim

As I understand it, your proposal has already been implemented, with
the difference that maintainers can only delete, not modify objects
that they do not directly maintain but are in their space.

Cheers,

--
Shane



End of db-wg Digest, Vol 45, Issue 1
************************************