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. Re: Does it make sense to forego RWhois and move to RESTful
      API for all customer assignments? (Brian Rak)
   2. OT&E RESTful Whois support? (Brian Rak)
   3. Re: Does it make sense to forego RWhois and move to RESTful
      API for all customer assignments? (Dani Roisman)
   4. Problems creating recipient org? (Brian Rak)
   5. Re: OT&E RESTful Whois support? (Mark Kosters)


----------------------------------------------------------------------

Message: 1
Date: Wed, 29 May 2013 12:52:52 -0400
From: Brian Rak <[email protected]>
To: [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=ISO-8859-1; format=flowed

Is there a place I can see if this has already been proposed?  I found 
https://www.arin.net/participate/acsp/index.html, but I can't tell if 
there's suggestions there that haven't been confirmed already.

We'd like to switch over to using the API (instead of sending tons of 
emails), and having one customer object per actual customer seems like 
the way to go.

On 4/30/2013 9:34 AM, Andy Newton wrote:
>> 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



------------------------------

Message: 2
Date: Wed, 29 May 2013 13:05:10 -0400
From: Brian Rak <[email protected]>
To: [email protected]
Subject: [arin-tech-discuss] OT&E RESTful Whois support?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Has support for RESTful whois been added to the OT&E Environment? 
https://www.arin.net/resources/restful-ote.html indicates that it will 
be added "in 2012".  At this point I don't have access to the 
environment, so I can't check myself.  If not, is there an updated ETA?


------------------------------

Message: 3
Date: Wed, 29 May 2013 19:09:46 +0000
From: Dani Roisman <[email protected]>
To: Brian Rak <[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:
        <C40B18ECB19B374EBB7B033835339F1D7A3C7AD0@SM-DAG156.softlayer.local>
Content-Type: text/plain; charset="us-ascii"

Hi Brian - um no it appears I dropped the ball on that one, thanks for 
reminding me.  I just submitted the request. . . look for it on the ACSP distro 
within a couple days.


----
Dani Roisman
VP, Network Operations
SoftLayer


| -----Original Message-----
| From: [email protected] [mailto:arin-tech-discuss-
| [email protected]] On Behalf Of Brian Rak
| Sent: Wednesday, May 29, 2013 11:53
| To: [email protected]
| Subject: Re: [arin-tech-discuss] Does it make sense to forego RWhois and
| move to RESTful API for all customer assignments?
| 
| Is there a place I can see if this has already been proposed?  I found
| https://www.arin.net/participate/acsp/index.html, but I can't tell if
| there's suggestions there that haven't been confirmed already.
| 
| We'd like to switch over to using the API (instead of sending tons of
| emails), and having one customer object per actual customer seems like
| the way to go.
| 
| On 4/30/2013 9:34 AM, Andy Newton wrote:
| >> 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
| 
| _______________________________________________
| arin-tech-discuss mailing list
| [email protected]
| http://lists.arin.net/mailman/listinfo/arin-tech-discuss


------------------------------

Message: 4
Date: Wed, 29 May 2013 15:38:31 -0400
From: Brian Rak <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [arin-tech-discuss] Problems creating recipient org?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

(Sorry about all the emails, I keep running into issues and there's very 
little documentation outside of the API method lists)

I'm trying to create a recipient org, and I keep getting a 404 error 
back.  This is pretty confusing, as the PARENTNETHANDLE I'm using 
definitely exists.

For example, I am sending the following request to https://reg.arin.net:

POST /rest/net/NET-64-237-32-0-1/org?apikey=API-AAAA-BBBB-CCCC-DDDD HTTP/1.1
Host: reg.arin.net
Accept: text/xml
Content-Type: text/xml
Content-Length: 344

<?xml version="1.0" encoding="UTF-8"?>
<org xmlns="http://www.arin.net/regrws/core/v1";>
.....
</org>

and getting the following back:

< HTTP/1.1 404 Not Found
< Date: Wed, 29 May 2013 19:29:52 GMT
< Server: Apache-Coyote/1.1
< Content-Type: text/html;charset=utf-8
< Content-Length: 1541
< Set-Cookie: JSESSIONID=XXXXXXXX.jboss1; Path=/regcore
< Connection: close
<
* Closing connection #0
<html><head><title>JBoss Web/7.0.10.Final - Error 
report</title><style><!--H1 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
 
H2 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
 
H3 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
 
BODY 
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B 
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} 
P 
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
 
{color : black;}A.name {color : black;}HR {color : #525D76;}--></style> 
</head><body><h1>HTTP Status 404 - Could not find resource for relative 
: /net/NET-64-237-32-0-1/org of full path: 
http://jboss1.cha.arin.net:8080/regcore/seam/resource/rest/net/NET-64-237-32-0-1/org?apikey=API-AAAA-BBBB-CCCC-DDDD</h1><HR
 
size="1" noshade="noshade"><p><b>type</b> Status 
report</p><p><b>message</b> <u>Could not find resource for relative : 
/net/NET-64-237-32-0-1/org of full path: 
http://jboss1.cha.arin.net:8080/regcore/seam/resource/rest/net/NET-64-237-32-0-1/org?apikey=API-AAAA-BBBB-CCCC-DDDD</u></p><p><b>description</b>
 
<u>The requested resource (Could not find resource for relative : 
/net/NET-64-237-32-0-1/org of full path: 
http://jboss1.cha.arin.net:8080/regcore/seam/resource/rest/net/NET-64-237-32-0-1/org?apikey=API-AAAA-BBBB-CCCC-DDDD)
 
is not available.</u></p><HR size="1" noshade="noshade"><h3>JBoss 
Web/7.0.10.Final</h3></body></html>


The only information I've been able to find about this is someone using 
PUT instead of POST.  What am I missing here?  Given that I'm getting a 
404 back I'm thinking that I have the wrong URL.  I can't seem to find 
any other URL that I could possibly use though.  The NET object I'm 
using definitely exists: 
http://whois.arin.net/rest/net/NET-64-237-32-0-1/pft , so that's not it 
either.


------------------------------

Message: 5
Date: Wed, 29 May 2013 20:02:03 +0000
From: Mark Kosters <[email protected]>
To: Brian Rak <[email protected]>, "[email protected]"
        <[email protected]>
Subject: Re: [arin-tech-discuss] OT&E RESTful Whois support?
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="us-ascii"

Hi Brian

The service has been available since July 23 2012. The announcement to
arin-tech-discuss said:

ARIN is proud to announce that the Whois-RWS RESTful service is now
available in ARIN's OT&E environment.  The URL for testing RESTful queries
is located at https://rest-beta.arin.net/wsrest. The UI component is
located at https://rest-beta.arin.net/ui
You can use this service to easily check changes you make in the OT&E
environment. Note that tcp port 43 queries are not supported.


Hope this helps,
Mark




On 5/29/13 1:05 PM, "Brian Rak" <[email protected]> wrote:

>Has support for RESTful whois been added to the OT&E Environment?
>https://www.arin.net/resources/restful-ote.html indicates that it will
>be added "in 2012".  At this point I don't have access to the
>environment, so I can't check myself.  If not, is there an updated ETA?
>_______________________________________________
>arin-tech-discuss mailing list
>[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


End of arin-tech-discuss Digest, Vol 28, Issue 1
************************************************

Reply via email to