Draft Policy ARIN-2021-8

Deprecation of the ‘Autonomous System Originations’ Field

Status: Under Discussion
Shepherds: Alicia Trotman, Anita Nikolich

Current Text (13 September 2022)

Problem Statement:

In the last two decades ARIN has developed multiple services which provide mechanisms for Internet Number Resource holders to publish information about their routing intentions.

The optional ‘OriginAS’ field was invented before RPKI existed in practice. At that time, ARIN’s Internet Routing Registry (IRR) followed a weak authorization model compared to available and in use today such as RPKI. The ‘OriginAS’ data was an improvement compared the other mechanisms that were available at that time.

However, there are issues with consumption of the data in the OriginAS field:

Consuming the ‘OriginAS’ field in a high-scale automated pipeline is challenging. The consumer needs to enter into a ‘Bulk Whois Data’ agreement with ARIN, download a multiple-gigabytes XML file (which is only generated once a day), parse this XML file, and then extract the OriginAS field. Querying objects one-by-one via the HTTPS interface does not scale well.

Policy statement:

  1. Remove Section 3.5 “Autonomous System Originations” of the NRPM in its entirety.
  2. Removal of ‘OriginAS’ field from the database

Timetable for Implementation:

  1. Immediate after ARIN Board adoption.
  2. December 31st 2024.

Policy Term: Permanent

Staff Understanding

ARIN-2021-8 would remove the entirety of ARIN policy surrounding Autonomous System Originations, including guidelines for ARIN’s origin AS data collection and publication.

The problem statement identifies issues with efficient access to OriginAS data, but the policy statement proposes elimination of the data altogether, rather than proposing potential solutions to the identified shortcomings.

This approach presumes that those benefiting from the OriginAS field today will readily find alternatives, and that may not be a valid presumption and/or should be carefully validated.

Additionally, the timeframe comment calling for implementation prior to ARIN eliminating NONAUTH has been overtaken by events and should be removed.

Implementable as Written?: Yes

Impact on ARIN Registry Operations and Services:

Cannot be determined, as the policy proposal does not make clear whether the use of OriginAS field is to be disallowed once policy is removed, disposition of existing OriginAS data, etc.

Legal Review:

No material legal issue.

Implementation Timeframe Estimate: Nine months

Implementation Requirements:

  • Customer education and outreach with appropriate sunsetting lead times
  • Staff training
  • Updates to public documentation
  • Updates to internal procedures and guidelines

Proposal/Draft Policy Text Assessed: 16 December 2022

History and Earlier Versions

Action Date
Proposal 7 July 2021
Draft Policy 18 November 2021
Revision 16 December 2021