From tedm at ipinc.net  Wed Jul 14 20:53:09 2010
From: tedm at ipinc.net (Ted Mittelstaedt)
Date: Wed, 14 Jul 2010 17:53:09 -0700
Subject: [Arin-whoisrws] Why is http://whois.arin.net offline?
Message-ID: <4C3E5BF5.3070104@ipinc.net>


Why is http://whois.arin.net offline?


From markk at arin.net  Thu Jul 15 16:41:17 2010
From: markk at arin.net (Mark Kosters)
Date: Thu, 15 Jul 2010 16:41:17 -0400
Subject: [Arin-whoisrws] Why is http://whois.arin.net offline?
In-Reply-To: <4C3E5BF5.3070104@ipinc.net>
References: <4C3E5BF5.3070104@ipinc.net>
Message-ID: <20100715204116.GB9379@arin.net>

On Wed, Jul 14, 2010 at 08:53:09PM -0400, Ted Mittelstaedt wrote:
> 
> Why is http://whois.arin.net offline?

Hi Ted

You are right - there is nothing running on port 80 (http) at the moment.

The legacy Whois service runs only off tcp port 43 (Whois). Whois-RWS, will 
support port 43 as well as a port 80 web interface. Unfortunately, we had to 
roll back the Whois-RWS deployment on June 26 and turn back on the legacy Whois
service.  We have since fixed the identified issues with Whois-RWS and will be 
releasing again this Saturday (July 17). When you log in later in the day on 
July 17, you again will see that wonderful web interface.  

Meanwhile, you are more than welcome to continue to use the web interface on 
http://whoisrws-demo.arin.net.
 
Regards,
Mark


From tedm at ipinc.net  Thu Jul 15 17:15:16 2010
From: tedm at ipinc.net (Ted Mittelstaedt)
Date: Thu, 15 Jul 2010 14:15:16 -0700
Subject: [Arin-whoisrws] How to modify POCs?
In-Reply-To: <20100715204116.GB9379@arin.net>
References: <4C3E5BF5.3070104@ipinc.net> <20100715204116.GB9379@arin.net>
Message-ID: <4C3F7A64.7030502@ipinc.net>

I have looked through the data at

https://www.arin.net/resources/whoisrws/whois_api.html

but I am having trouble understading how to use the
interface to upload data to WHOIS-RWS

Obtaining a POC seems easy enough with the command example:

xsltproc poc.xsl http://whois.arin.net/rest/poc/KOSTE-ARIN

but there seems to me no example on how a remote host can
push a SWIP to WHOIS-RWS using the interface, or am I missing
something?

(Yes I know there's a human-friendly webinterface but thats
not what I'm looking for)

Ted


From markk at arin.net  Fri Jul 16 12:19:58 2010
From: markk at arin.net (Mark Kosters)
Date: Fri, 16 Jul 2010 12:19:58 -0400
Subject: [Arin-whoisrws] How to modify POCs?
In-Reply-To: <4C3F7A64.7030502@ipinc.net>
Message-ID: <C865FEEE.1C561%markk@arin.net>

On 7/15/10 5:15 PM, "Ted Mittelstaedt" <tedm at ipinc.net> wrote:

> I have looked through the data at
> 
> https://www.arin.net/resources/whoisrws/whois_api.html
> 
> but I am having trouble understading how to use the
> interface to upload data to WHOIS-RWS
> 
> Obtaining a POC seems easy enough with the command example:
> 
> xsltproc poc.xsl http://whois.arin.net/rest/poc/KOSTE-ARIN
> 
> but there seems to me no example on how a remote host can
> push a SWIP to WHOIS-RWS using the interface, or am I missing
> something?
> 
> (Yes I know there's a human-friendly webinterface but thats
> not what I'm looking for)
> 
> Ted

Hi Ted

The current Whois-RWS service only supports gets. I think we may need to
make it more explicitly clear in the Whois-RWS documentation that it is a
read-only service. For provisioning, the restful calls and associated
templates are in development and will be a separate service. You can see a
preview of this effort at:

https://www.arin.net/features/api_keys.html

Further documentation is located at:

https://www.arin.net/resources/restful-interfaces.html

Regards,
Mark



From ross at kallisti.us  Fri Jul 16 13:48:59 2010
From: ross at kallisti.us (Ross Vandegrift)
Date: Fri, 16 Jul 2010 13:48:59 -0400
Subject: [Arin-whoisrws] Non-normalized ASNs and duplicate Customer objects
Message-ID: <20100716174859.GA12237@kallisti.us>

Hello,

I've been working on an Python ORM that maps high-level Python objects
to model objects in ARIN's demo WHOIS-RWS.  So far, I'm pretty pleased
with how easy it's been to interact with.  I do have two questions:

1) Is there a reason that Network objects don't return normalized data
for originASes?  ASN are quite easy to search for, but the rest of the
data is well-normalized, and I'm kinda of surprised not to get a list
of originASRefs.  It's no major impediment, just a bit odd.

2) Is there a reason that identical customer records weren't merged
during creation?  If a single entity has multiple SWIPs in WHOIS, it
looks like a new Customer object has been created for each Network.
This is pretty counter-intuitive.  Shouldn't these be merged into a
single record?

Thanks,
Ross


-- 
Ross Vandegrift
ross at kallisti.us

"If the fight gets hot, the songs get hotter.  If the going gets tough,
the songs get tougher."
	--Woody Guthrie
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <https://lists.arin.net/pipermail/arin-whoisrws/attachments/20100716/69b9dc22/attachment.sig>

From andy at arin.net  Tue Jul 20 09:13:39 2010
From: andy at arin.net (Andy Newton)
Date: Tue, 20 Jul 2010 09:13:39 -0400
Subject: [Arin-whoisrws] Non-normalized ASNs and duplicate Customer
 objects
In-Reply-To: <20100716174859.GA12237@kallisti.us>
References: <20100716174859.GA12237@kallisti.us>
Message-ID: <B01E22E7-7A30-4461-A776-C007F21E561C@arin.net>

Ross,

I'm sorry for the delayed response.  I'll answer your questions in-line:

On Jul 16, 2010, at 1:48 PM, Ross Vandegrift wrote:

> 1) Is there a reason that Network objects don't return normalized data
> for originASes?  ASN are quite easy to search for, but the rest of the
> data is well-normalized, and I'm kinda of surprised not to get a list
> of originASRefs.  It's no major impediment, just a bit odd.

ASN entities in our registration system represent blocks of AS numbers that ARIN has handed out.  Like networks, they are entities "registered" in our database.  However, when a network operator specifies an origin AS on a network, that AS number can come from any RIR.  In other words, the origin AS numbers on networks are not entities that are registered by ARIN, and they have none of the meta-data associated with an actual ASN registration.

> 2) Is there a reason that identical customer records weren't merged
> during creation?  If a single entity has multiple SWIPs in WHOIS, it
> looks like a new Customer object has been created for each Network.
> This is pretty counter-intuitive.  Shouldn't these be merged into a
> single record?

At present, simple reassignment SWiPs automatically create a new customer record, and there really is no good way for us to merge them automatically that would not induce some error.  However, we have kept the customer record separated out in the data model for the future possibility of re-using the same customer with multiple network reassignments.  Currently it is not possible to do this with the email templating registration system using simple reassignments, but we are looking into the possibility of allowing it in the new RESTful registration service that is in development.

Thanks for your questions Ross.  I hope these answers help, and we are glad to hear that you are being quite successful with the code integration of Whois-RWS.

Andy Newton
Chief Engineer
ARIN

From ross at kallisti.us  Tue Jul 20 16:29:00 2010
From: ross at kallisti.us (Ross Vandegrift)
Date: Tue, 20 Jul 2010 16:29:00 -0400
Subject: [Arin-whoisrws] Non-normalized ASNs and duplicate
	Customer	objects
In-Reply-To: <B01E22E7-7A30-4461-A776-C007F21E561C@arin.net>
References: <20100716174859.GA12237@kallisti.us>
	<B01E22E7-7A30-4461-A776-C007F21E561C@arin.net>
Message-ID: <20100720202900.GA32265@kallisti.us>

On Tue, Jul 20, 2010 at 09:13:39AM -0400, Andy Newton wrote:
> However, when a network operator specifies an origin AS on a
> network, that AS number can come from any RIR.

Aha, of course.  Hadn't thought of that case - all of my origin AS
attributes are ARIN registered.  Makes perfect sense.

> However, we have kept the customer record separated out in the data
> model for the future possibility of re-using the same customer with
> multiple network reassignments.  Currently it is not possible to do
> this with the email templating registration system using simple
> reassignments, but we are looking into the possibility of allowing
> it in the new RESTful registration service that is in development.

Hmmm, yea, this would be pretty desirable in my mind - a unique
customer object that has appropriate references to all of the
associated resources.

> Thanks for your questions Ross.  I hope these answers help, and we
> are glad to hear that you are being quite successful with the code
> integration of Whois-RWS.

Definitely makes both points clear, thanks.  I was initially among the
skeptics for a move away from the traditional WHOIS.  I'm pretty much
sold.  Reusing customer objects for association purposes is the only
issue I've got so far, and it sounds like that's being worked on.

Ross

-- 
Ross Vandegrift
ross at kallisti.us

"If the fight gets hot, the songs get hotter.  If the going gets tough,
the songs get tougher."
	--Woody Guthrie
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <https://lists.arin.net/pipermail/arin-whoisrws/attachments/20100720/7533e7f3/attachment.sig>