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

[Job Snijders]

Hi David, everyone,

I'm the one who initiated the process towards ARIN-2021-8. I've put in
considerable effort to find a purpose and use for the ARIN Originations
field in automated tool chains, and ultimately concluded the field has
so many apparent challenges it might be better to get rid of it,
especially since IRR and RPKI nowadays exist.

On Tue, Apr 26, 2022 at 11:53:58AM -0500, David Farmer via ARIN-PPML wrote:
> While I do not support the deprecation of the 'Autonomous System
> Originations' Field from the database at this time for many of the reasons
> discussed at the microphone at ARIN 49. 

Unfortunatey, I wasn't there. Would you be so kind to outline the many
reasons in an email?

> Nevertheless, as discussed in the problem statement this field has
> several problems and it eventually needs to be deprecated. However,
> since this is an optional field within the ARIN database, without any
> enforcement actions required by policy, it seems possible to remove
> section 3.5 from the NRPM at this time, without also deprecating the
> field at this time.
> 
> Further, this would set things up for the future deprecation of the
> 'Autonomous System Originations' Field from the database to proceed when
> the community feels that is appropriate, as expressed through a separate
> ARIN Consultation Process, without necessitating additional policy actions.
> 
> If this policy proposal were modified to only remove section 3.5 from the
> NRPM at this time, with the deprecation of the 'Autonomous System
> Originations' Field from the database occurring at some future date, to be
> determined at a later time by the ARIN community, I would support this
> policy proposal proceeding forward.

Why do you favor a separate consultation?

My objective is to clean up the number of (less than optimal) routing
related data sources; my primary goal is not to reduce the text size of
the NPRM :-)

Kind regards,

Job