<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Dear Database Working Group Members,
<div class=""> <br class="">
At the last RIPE meeting we discussed the topic of orphaned objects, and it seems that this term was confusing to some. This is an attempt to clarify the problem and hopefully find a solution forward. This continues to be a problem where number block holders
are getting “locked” out of being able to manage their routing objects and in-addr records. </div>
<div class=""><br class="">
</div>
<div class="">Today, we continue to have a problem where a block holder does not have an ability to manage the objects that operationally impact their number blocks. Examples include a routing or reverse dns object that exist in the database but are not currently
maintained by an active number block maintainer. This is typically the case where a number block holder (usually legacy) may have contracted services through a third party. Time goes by, the business relationship ends but the third party never removed their
associated records (in-addrs, routing objects, etc). </div>
<div class=""><br class="">
</div>
<div class="">The number block holder now seeks to update the block (either directly or through a new service provider) and is unable to add these resource records to their number block. The database can help fix this problem through allowing the appropriate
control for a number block holder to maintain their own information. In many cases the last resort is to contact RIPE NCC to make the change to an object the number block holder should have had online access to manage directly in the first place. This proposal
intends to enable number block holders to have a greater ability to manage their own resources. </div>
<div class=""><br class="">
I propose that the maintainer of a number block shall have full control over the association of contacts, routing, and reverse dns entries related to the number block held. The number block holder should not be able to delete an object they do not have maintainer
status for, but they should be able to remove the association from their number block. The number block maintainer shall have an ability to delete the relationship between a related object and the number block through the LIR Portal, Webupdates, and related
systems. </div>
<div class=""> </div>
<div class="">Open items to discuss; </div>
<div class=""><br class="">
</div>
<div class="">1) What is the best method to enable a number block holder to manage and control objects associated with their blocks in Ripe DB? </div>
<div class=""><br class="">
</div>
<div class="">2) Should any objects be excluded from this control? </div>
<div class=""><br class="">
</div>
<div class="">3) What is a reasonable schedule for announcements and implementation? </div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Thank you for your consideration and I look forward to your comments. </div>
<div class=""><br class="">
</div>
<div class="">Billy</div>
<div class=""><br class="">
</div>
<div class="">William Sylvester</div>
<div class=""><a href="mailto:william.sylvester@addrex.net" class="">william.sylvester@addrex.net</a></div>
</body>
</html>