Origin AS Information (Autonomous System Originations)
The Origin Autonomous System (AS) field is an optional field collected by ARIN during all IPv4 and IPv6 block transactions (allocation and assignment requests, reallocation and reassignment actions, transfer and experimental requests). This additional field is used by IP address block holders (including legacy address holders) to record a list of the Autonomous System Numbers (ASNs), separated by commas or whitespace, from which the addresses in the address block(s) may originate.
ARIN collects this information and provides a mapping of IP address blocks to the associated ASNs on the ARIN ftp site. Collecting Origin AS information and making that information available to the community is part of the implementation of Policy ARIN-2006-3: Capturing Originations in Templates, included in the ARIN Number Resource Policy Manual (NRPM) Section 3.5: "Autonomous System Originations."
Using the Origin AS Field to Validate LOAs
Origin AS information can assist Internet Service Providers (ISPs) in determining the validity of a Letter of Authority (LOA) provided by a customer when requesting to manage an IP address block. In cases where tools like Whois or an examination of registry information does not provide a clear case for a customer's holdership, the ISP can request that the customer configure the Origin AS field to match the ISP's AS. If a customer is an IP address block holder (including legacy address holders), they can easily set the Origin AS attribute using an ARIN Online account. Organizations that don't have current contact information associated with their address block will need to be validated initially by ARIN before updating their network record. Requiring an Origin AS update confirms to the ISP that the IP address block owner is verified and correct.
Configuring an Origin AS
The Origin AS can be set by the appropriate Point of Contact (POC) (Admin, Tech, or Resource) in one of two ways:
- Within ARIN Online: ARIN Online allows authenticated users to manage their network registration records.
- Using the Registration RESTful Web Service (Reg-RWS): This API allows for automated and authorized updates for an IP address block by the authorized contact to occur via ARIN's provisioning system.
Managing Network Resources
To manage network resources within ARIN Online, you need an ARIN Online account. If you do not have an account, follow these instructions to create one.
Once you have your ARIN Online account:
- Link your ARIN Online account to an Admin or Tech Point of Contact (POC).
- Select Organization Identifiers (Org ID), and select the Org ID associated with the POC that manages the resources you need to access.
If your account does not have access to the resources, you can view information on transferring resources before you request that they be transferred to you.
Using ARIN Online to Configure an Origin AS
To configure an Origin AS for an IP address block as an associated Admin, Tech, or Resource POC:
Log into ARIN Online, select Organization Identifiers on the dashboard, and choose the Org ID that contains the IP address block for which you want to configure the Origin AS. From the IP Networks list, choose the Network Name. Select Modify to open the Modify Network page.
In the Origin AS field, enter an ASN and select the + button.
After entering the ASN(s), select Submit.
You will see a notification if the information was successfully saved, and the Origin AS will appear in the Information page.
You can also configure Origin AS information in ARIN Online when reassigning or reallocating IP addresses:
Note: Organizations with outdated contact information associated with their resources will need to be validated by ARIN before configuring an Origin AS.
Using Reg-RWS to Configure an Origin AS
The Origin AS field can be configured if you are using Reg-RWS to submit registration data to ARIN. In short, Reg-RWS allows you to configure applications or scripts that use the Reg-RWS API to connect to the ARIN database. The application can access a URL to get information about records, create new records, modify existing records, or delete records in the database. Additional information about the record (for example, organization data) is contained in an XML payload that is sent or received. The Origin AS field is located in the NET payload, which contains information about the IPv4 or IPv6 network.
For more information on Reg-RWS, visit: