Hello Sean, There are several ways you might want to approach this.
Since the set of direct allocations issued to CenturyLink doesn’t change all that frequently - only when you get a new block from ARIN or via a transfer, or transfer an existing block to another organization - you might consider storing data on all of your direct allocations locally with relevant data - net handle, start IP, end IP, etc. When you want to make a reassign call, you can reference that stored data to take the prefix/range to be reassigned and determine the associated parent net handle. As an example, if you locally store data for the net handle NET-63-144-0-0-1 with a start IP address of 63.144.0.0 and an end IP address of 63.151.255.255, you can then use that data to determine 63.145.104.192 falls within NET-63-144-0-0-1. The only caveat with this approach is that you’d need to update your local data whenever you add a new block, transfer a block to another organization, etc. Another option would be to use ARIN’s Whois-RWS API to identify the parent net handle for a given IP address. You can use that API to form a URL (http://whois.arin.net/rest/ip/63.145.104.192) which asks for the network handle associated with 63.145.104.192. You’ll get back a payload with the network registration information, including the net handle. Note that there’s no way to submit a call asking for only a direct allocation to be returned; if the IP address is already assigned to a customer, you’ll get that record back. You’d have to then use the parent net handle from that record to submit a second query for registration information for that network, then verify what you get back is a direct allocation. Keep in mind the Whois-RWS API is different than the Reg-RWS API. It’s public so there’s no API key, the payloads might not be exactly the same, etc. Those are the options that occur to me as being most useful. If you have any further questions, comments, or concerns please respond to this message or contact me directly. Regards, Jon Worley Principal Technical Analyst ARIN Registration Services https://www.arin.net/ [email protected] 703.227.0660 From: <Zhao>, Sean <[email protected]<mailto:[email protected]>> Date: Thursday, November 13, 2014 at 1:45 PM To: "'[email protected]<mailto:'[email protected]>'" <[email protected]<mailto:[email protected]>> Cc: "Talavagalu Matha Ajjaiah, Chandrasekhara" <[email protected]<mailto:[email protected]>>, "Grimes, Ronald" <[email protected]<mailto:[email protected]>>, "Sugandh, Nimesh" <[email protected]<mailto:[email protected]>> Subject: [arin-tech-discuss] Is ParentNetHandle mandatory in Net payload Hi, >From your payload on your website. parentNetHandle looks like it is mandatory. >My question is how I know the parentNetHandle of an ip that I want to swip? For example. I have an 63.145.104.192. I went to http://whois.arin.net/rest/net/NET-63-145-104-192-1 or http://whois.ote.arin.net/rest/net/NET-63-145-104-192-1 I got now xml return. It used to return me net playload . But the net is parent net. If you changed, do you have alternative way to get parent net handle? All I need is a parent net handle of the ip I am going to assign. <net xmlns="http://www.arin.net/regrws/core/v1"; > <version>4</version> <comment> <line number = "1">Line 1</line> </comment> <registrationDate>Tue Jan 25 16:17:18 EST 2011</registrationDate> <orgHandle>ARIN</orgHandle> <handle>NET-10-0-0-0-1</handle> <netBlocks> <netBlock> <type>A</type> <description>DESCRIPTION</description> <startAddress>010.000.000.000</startAddress> <endAddress>010.000.000.255</endAddress> <cidrLength>24</cidrLength> </netBlock> </netBlocks> <customerHandle>C12341234</customerHandle> <parentNetHandle>PARENTNETHANDLE</parentNetHandle> <netName>NETNAME</netName> <originASes> <originAS>AS102</originAS> </originASes> <pocLinks> <pocLinkRef> </pocLinkRef> </pocLinks> </net> Thanks Sean Zhao [email protected]<mailto:[email protected]> This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
_______________________________________________ arin-tech-discuss mailing list [email protected] http://lists.arin.net/mailman/listinfo/arin-tech-discuss
