Send arin-tech-discuss mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.arin.net/mailman/listinfo/arin-tech-discuss
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of arin-tech-discuss digest..."
Today's Topics:
1. Does it make sense to forego RWhois and move to RESTful API
for all customer assignments? (Dani Roisman)
2. Re: Does it make sense to forego RWhois and move to RESTful
API for all customer assignments? (Andy Newton)
----------------------------------------------------------------------
Message: 1
Date: Mon, 29 Apr 2013 18:03:29 +0000
From: Dani Roisman <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [arin-tech-discuss] Does it make sense to forego RWhois and
move to RESTful API for all customer assignments?
Message-ID:
<C40B18ECB19B374EBB7B033835339F1D7A2D21BE@SM-DAG156.softlayer.local>
Content-Type: text/plain; charset="us-ascii"
Hi folks,
We've implemented RESTful registrations of IP assignments when our customers
have been explicitly requesting "SWIP" and have been using it successfully for
some time. By default, our customer IP assignments are only recorded in our
'rwhois' database, which is updated via daily batch process.
I'm impressed with the rapid response and updates to 'whois' which result from
this method, and so far ARIN servers seem to be holding up with our (admittedly
low) request volume.
I wanted to post a question to the list: Does it make sense to replace our
'rwhois' functionality entirely with ARIN registrations at this point in time?
For customer assignments in our RIPE and APNIC datacenters, this has been
standard operating procedure, as those RIRs do not offer 'rwhois' support
AFAIK. I can tell you that our sysadmins and developers would love to be able
to turn off 'rwhois' entirely, and submit all assignment information into
ARIN's DB.
A few follow-up questions:
1) Is there a limit to ARIN RESTful API requests (performance-related or
artificially imposed)? I don't have our numbers handy, but it could be in the
"hundreds" of assignment/releases on a busy day, and it would be nice for our
provisioning system to do these in real-time.
2) Is the ARIN DB prepared to handle this volume of assignment information?
Again, I don't have our exact numbers handy, but it's in the low "hundreds of
thousands" of subnets.
3) Have others been considering or doing this yet? If so, has it been
successful / are there things to watch out for?
4) Is there a plan to allow us to associate multiple subnets with a single
"Customer" object? At this time, RESTful API is making us create a new
"Customer" object for *each* subnet, which just seems wrong to me in that it
creates a bunch of extra data needlessly, and doesn't allow for reverse
queries, e.g. "show all subnets assigned to CustomerXYZ."
----
Dani Roisman
VP, Network Operations
(281) 714-3714 direct
http://www.softlayer.com
------------------------------
Message: 2
Date: Tue, 30 Apr 2013 13:34:50 +0000
From: Andy Newton <[email protected]>
To: Dani Roisman <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [arin-tech-discuss] Does it make sense to forego RWhois
and move to RESTful API for all customer assignments?
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Dani,
Thanks for your questions. My response are in-line below:
On 4/29/13 2:03 PM, "Dani Roisman" <[email protected]> wrote:
>1) Is there a limit to ARIN RESTful API requests (performance-related or
>artificially imposed)? I don't have our numbers handy, but it could be
>in the "hundreds" of assignment/releases on a busy day, and it would be
>nice for our provisioning system to do these in real-time.
While we don't publish our limits, the use case you have outlined here is
well within normal usage of Reg-RWS. There should be no problem with the
load you are describing.
>2) Is the ARIN DB prepared to handle this volume of assignment
>information? Again, I don't have our exact numbers handy, but it's in
>the low "hundreds of thousands" of subnets.
Yes, we should be able to handle it.
>3) Have others been considering or doing this yet? If so, has it been
>successful / are there things to watch out for?
I can't actually speak for what others are doing with Reg-RWS, but we have
certainly seen a big rise in the number of transactions via RESTful calls.
>4) Is there a plan to allow us to associate multiple subnets with a
>single "Customer" object? At this time, RESTful API is making us create a
>new "Customer" object for *each* subnet, which just seems wrong to me in
>that it creates a bunch of extra data needlessly, and doesn't allow for
>reverse queries, e.g. "show all subnets assigned to CustomerXYZ."
When we redesigned our systems to accommodate Reg-RWS we did take into
account the ability to have multiple assignments for a customer. While
some work is still required on our end to allow this capability, it is not
onerous. If you would like to see ARIN prioritize this capability, the
official method for getting it in front of our management team is to
submit a suggestion via the ARIN Consultation and Suggestion Process
(ACSP). You can find the link to submit an ACSP here:
https://www.arin.net/app/suggestion/
Thanks for your questions. Let me know if you have any follow up comments
or questions.
Andy Newton,
Chief Engineer, ARIN
------------------------------
_______________________________________________
arin-tech-discuss mailing list
[email protected]
http://lists.arin.net/mailman/listinfo/arin-tech-discuss
End of arin-tech-discuss Digest, Vol 27, Issue 4
************************************************
