[arin-ppml] Recommended Draft Policy ARIN-2021-8: Deprecation of the ‘Autonomous System Originations’ Field

[ARIN]

On 21 October 2022, the ARIN Advisory Council (AC) advanced the following Draft Policy to Recommended Draft Policy status:

 

* ARIN-2021-8: Deprecation of the ‘Autonomous System Originations’ Field

 

The text of the Recommended Draft Policy is below, and may also be found at:

 

https://www.arin.net/participate/policy/drafts/2021_8/

 

You are encouraged to discuss all Recommended Draft Policies on PPML prior to their presentation at the next ARIN Public Policy Consultation (PPC). PPML and PPC discussions are invaluable to the AC when determining community consensus.

 

The PDP can be found at:

 

https://www.arin.net/participate/policy/pdp/

 

Draft Policies and Proposals under discussion can be found at:

 

https://www.arin.net/participate/policy/drafts/

 

Regards,

 

Sean Hopkins

Senior Policy Analyst

American Registry for Internet Numbers

 

  

 

Recommended Draft Policy ARIN-2021-8: Deprecation of the ‘Autonomous System Originations’ Field

 

AC Assessment of Conformance with the Principles of Internet Number Resource Policy:

 

Based on community feedback and AC discussion we motion to move ARIN-2021-8: Deprecation of the 'Autonomous System Originations' Field to Recommended Draft, with the following change to Language: The removal of 'OriginAs' fields from December 31st 2024 to 24 months after board adoption.

 

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 the 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. Remove the ‘OriginAS’ field from the database 

 

Timetable for implementation:

 

1. Removal of  section 3.5: Immediate after ARIN Board adoption.

2. Removal of the ‘OriginAS’ field from the database: 24 months after ARIN Board adoption.

 

Policy Term: Permanent

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20221026/cf963cf4/attachment.htm>