[arin-tech-discuss] returned error message when I am trying to create an OrgHandle....

Wed Feb 6 13:54:50 EST 2013

Hi David,

In your scenario:

Today, you can:

1) Create a POC
2) Create a recipient ORG
3) Reassign the /29 to the recipient ORG

When the customer disco, you then:

4) Delete the /29
5) Delete the ORG
6) Delete the POC

If 4 occurs does 5 & 6 need to occur or can the org be used for other IP's?

Thanks,
Ron
-----Original Message-----
From: David Huberman [mailto:dhuberma at arin.net] 
Sent: Wednesday, February 06, 2013 11:58 AM
To: Grimes, Ronald; Zhao, Sean; 'arin-tech-discuss at arin.net'
Subject: Re: [arin-tech-discuss] returned error message when I am trying to create an OrgHandle....

Hi Ron,

Good question.  I believe the biggest virtue of recipient customer orgs is to allow the upstream to control all aspects of the objects.  What does that mean? In the old days of SWIP, before REST, there was no concept of recipient orgs.  So here's what would happen:

1) You would SWIP a /29 to a customer with a reassign-detailed template.
Three things would happen as a result:
- a POC would be created for the customer
- an OrgID would be created for the customer
- the /29 would be delegated from the ISP to the new OrgID with the new POC

2) The customer eventually discos.  The ISP sends in netmod template and "R"emoves the /29 reassignment to the OrgID.

3) The POC and the OrgID defining the customer would then sit in ARIN's Whois in perpetuity, so the contact information was never really scrubbed.
  This was less than ideal for those customers.   I've taken many phone
calls and emails over the years from old customers of ISPs who were very unhappy their contact information (address, sometimes home address, phone, sometimes mobile phone) was found in ARIN's Whois for the whole world to see.

Today, you can:

1) Create a POC
2) Create a recipient ORG
3) Reassign the /29 to the recipient ORG

When the customer disco, you then:

4) Delete the /29
5) Delete the ORG
6) Delete the POC

And it's all done by the RESTful system you're designing so it's all automated and lightning quick.  As a result, ARIN Whois is much cleaner, and your former customers don't have all their sensitive contact information sitting in ARIN's Whois.

I hope I explained that well.  There may be other benefits of recipient ORGs which I'm not thinking about right now, but which I'm sure someone will remind me of and I'll share with the list :)

Best,
David

---
David R Huberman
Principal Technical Analyst, ARIN
703-227-9866

On 2/5/13 4:25 PM, "Grimes, Ronald" <Ron.Grimes at CenturyLink.com> wrote:

What is the purpose of sending the Parent Handle when create "Recipient Customer Org" is done?

Thanks,
Ron
-----Original Message-----
From: David Huberman [mailto:dhuberma at arin.net]
Sent: Tuesday, February 05, 2013 3:50 PM
To: Grimes, Ronald; Zhao, Sean; 'arin-tech-discuss at arin.net'
Subject: Re: [arin-tech-discuss] returned error message when I am trying to create an OrgHandle....

Hi Ron!

The resulting OrgID can be assigned IP addresses out of any parent block (and even from blocks registered to other ISPs).

Regards,
David

---
David R Huberman
Principal Technical Analyst, ARIN
703-227-9866

On 2/5/13 12:41 PM, "Grimes, Ronald" <Ron.Grimes at CenturyLink.com> wrote:

Hi David,

When CTL calls with "Recipient Customer Org" does this mean that the ORG ID that it creates can only be assigned to IP Addresses that have the same Parent Handle as what the ORG ID is created with?

Thanks
Ron

-----Original Message-----
From: David Huberman [mailto:dhuberma at arin.net]
Sent: Monday, February 04, 2013 4:00 PM
To: Zhao, Sean; 'arin-tech-discuss at arin.net'
Cc: Grimes, Ronald
Subject: Re: [arin-tech-discuss] returned error message when I am trying to create an OrgHandle....

Hiya again,

So there are two different Org creates:

- a standard Org Handle, which is what you sent.  It results in an OrgID in Whois which can be used for anything.  Requests to create new OrgIDs are reviewed by ARIN staff

- "Recipient Customer Org" creates an OrgID which can be managed by an ISP like Century Link. I think that's the org create you are looking for.
When you POST a recipient customer org create, it will auto-approve and send you the handle back.

Best,
David

---
David R Huberman
Principal Technical Analyst, ARIN
703-227-9866

On 2/4/13 3:50 PM, "Zhao, Sean" <Sean.Zhao at CenturyLink.com> wrote:

Thanks a lot, David. It is the url problem.

Now I got this xml returned,

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><ticket xmlns="http://www.arin.net/regrws/core/v1"
xmlns:ns2="http://www.arin.net/regrws/messages/v1"><createdDate>2013-02-04T
15:40:18.708-05:00</createdDate><ticketNo>20130204-X861</ticketNo><updatedD
ate>2013-02-04T15:40:18.708-05:00</updatedDate><webTicketStatus>PENDING_
ate>REV
IEW</webTicketStatus><webTicketType>ORG_CREATE</webTicketType></ticket>

I remember it used to return me a new orgHandel instead of ticket number.
Am I missing anything or Arin won't return OrgHandle immediately anymore?

Thanks,

Sean Zhao
Sean.Zhao at CenturyLink.com

-----Original Message-----
From: David Huberman [mailto:dhuberma at arin.net]
Sent: Monday, February 04, 2013 3:31 PM
To: Zhao, Sean; 'arin-tech-discuss at arin.net'
Cc: Grimes, Ronald
Subject: Re: [arin-tech-discuss] returned error message when I am trying to create an OrgHandle....

Hiya Sean Zhao,

Looks to me like the problem is your URL.  It's /rest/org/  rather than /rest/net/org/

Try that out and let us know if you continue to have errors.

Best,
David

---
David R Huberman
Principal Technical Analyst, ARIN
703-227-9866

On 2/4/13 3:25 PM, "Zhao, Sean" <Sean.Zhao at CenturyLink.com> wrote:

Hi,
                I am trying to create and org handle vs RESTFul. But I keep getting an error message, like this, <?xml version="1.0"
encoding="UTF-8" standalone="yes"?><error xmlns="http://www.arin.net/regrws/core/v1"><additionalInfo><message>Ensure
that the proper HTTP method has been used for this request.</message></additionalInfo><code>E_BAD_REQUEST</code><components/><
message>No
 resource method found for POST, return 405 with Allow header</message></error>

Here is my payload.
 <?xml version="1.0" encoding="UTF-8"?>
<org xmlns="http://www.arin.net/regrws/core/v1">
<iso3166-2>OH</iso3166-2>
<iso3166-1>
<code3>USA</code3>
<code2></code2>
<name></name>
<e164></e164>
</iso3166-1>
<streetAddress>
<line number="1">6000 Parkwood Pl</line> </streetAddress> <city>DUBLIN</city> <postalCode>43016</postalCode> <orgName>CENTURYLINK LIMS</orgName> <pocLinks> <pocLinkRef description="SEAN ZHAO"
handle="KOTLO3-ARIN" function="AB"/> <pocLinkRef description="SEAN ZHAO"
handle="ZHAOS15-ARIN" function="AD"/> <pocLinkRef description="SEAN ZHAO"
handle="ZHAOS13-ARIN" function="N"/> <pocLinkRef description="SEAN ZHAO"
handle="ZHAOS14-ARIN" function="T"/> </pocLinks> </org>

The url I am using
https://www.arin.net/rest/net/org/?apikey=MyAPIKey

this url & payload worked before back to early of 2010. Am I missing any updated things?

Thanks,

Sean Zhao
Sean.Zhao at CenturyLink.com