Mike,

We have no regular processes to delete orphaned customer records. In our 
analysis of the growth of our data set, orphaned records do not constitute an 
area of excessive growth and therefore instituting a regular process to purge 
them has not been implemented.

Once unlinked from a network, a customer record cannot be easily found except 
for by a lookup of its handle. There is no API function to list orphaned 
records.

I hope that answers your questions.

Andy Newton,
ARIN

On Jan 2, 2015, at 8:24 PM, Mike Joseph 
<[email protected]<mailto:[email protected]>> wrote:

Hey folks,

I have a few questions about Customer records in the ARIN DB and how orphaned 
ones are handled.  Specifically, I'm asking about Customer records in the 
following situations:

  *   Customer record created (POST /rest/net/PARENTNETHANDLE/customer) but no 
reassignment made
  *   Simple reassignment deleted (DELETE /rest/net/NETHANDLE) without explicit 
deletion of the customer record (DELETE /rest/customer/CUSTOMERHANDLE)

I know that the documentation admonishes developers not to get into this 
situation and to be fastidious about cleaning up Customer records, but of 
course it can happen.  And I've tested in both scenarios (knowing the Customer 
record ID #) that the record persists at least for a while.

So, my questions are:

  1.  What happens to these orphaned records?
  2.  Does ARIN make any effort to remove them?
  3.  If I wanted to clean ours up, how would I even find them?  I can't find 
an API call to find Customer records by NET.

Thanks.

-MJ

--

Mike Joseph |    Manager, Sustaining Engineering & Operations |  
[email protected]<mailto:[email protected]> |         +1-650-214-4543

_______________________________________________
arin-tech-discuss mailing list
[email protected]<mailto:[email protected]>
http://lists.arin.net/mailman/listinfo/arin-tech-discuss

_______________________________________________
arin-tech-discuss mailing list
[email protected]
http://lists.arin.net/mailman/listinfo/arin-tech-discuss

Reply via email to