[arin-tech-discuss] Developing Reg-RWS discovery requirements (was Re: Listing all reassignments?)

Andy Newton andy at arin.net
Tue Nov 29 13:23:58 EST 2011


My response is inline.

On Nov 23, 2011, at 1:49 PM, Thomas St.Pierre wrote:

> 1) For a given IP, (usually the network address of the subnet I'm about to reassign) find out what the parent NET HANDLE is. This is required for the net payload to do the reassign. (From my understanding of the documentation anyways)

Because many registrants SWiP network blocks to themselves, this isn't as straightforward as one would hope. The logic may need to be "find the parent NET HANDLE for the most specific (or least specific) of my networks". I guess most specific is the proper logic, but I could easily be wrong about that. Another option to help solve that problem might be to return ALL the net handles for each network registered by a registrant given an IP. Because it is possible for a single API Key to have an authorization over multiple organizations, that query would also need to include an ORG Handle.

> 2) For a given IP, find what the existing NET HANDLE and customer handle are. Useful for updating existing objects.

Would the intent be to use this in a batch operation, such as a nightly syncing process, or more for updating objects on the fly? And if it is more of a batch mode, how do you decide which IP address to use?

This has been helpful.

Andy Newton

More information about the arin-tech-discuss mailing list