[ARIN-consult] Consultation Now Open on the Future of ARIN’s IRR

[John Curran]

On 1 Mar 2021, at 12:05 PM, Job Snijders <job at fastly.com> wrote:
> 
> On Mon, Mar 01, 2021 at 03:00:46PM +0000, John Curran wrote:
>> On 12 Feb 2021, at 2:54 PM, Rob Seastrom
>> <rs at seastrom.com<mailto:rs at seastrom.com>> wrote:
>> 
>>> I urge that Job's thoughts for orderly burndown be given heavy
>>> consideration.  Upon further discussion with Job I have the
>>> following points to make:
>> 
>>> * Of the total of 62,352 entries in ARIN-NONAUTH about 10k of those
>>> routes show up in the DFZ and about 1,933 are rpki invalid.  … 
>> Presuming RIPE-731 deployment and per your data above, we would
>> presumably see removal of approximately two thousand of the 10K routes
>> in the DFZ which correspond to ARIN-NONAUTH objects - is that correct?
>> If that’s the case, once the conflicting ARIN-NONAUTH objects were
>> deleted, how does that affect the necessary wait time for a full
>> shutdown of ARIN-NONAUTH?
> 
> The 10K and 2K are disjoint sets. The 2K was brought up as it is the
> lowest hanging fruit, the first step really, towards cleaning up the
> source.

Acknowledged,

I was trying to figure out the merits of focusing on that portion of ARIN-NONAUTH which should be deleted (due to being overtaken by valid ROAs) rather than the portion which actually is present in the DFZ.  

> In order to shut down ARIN-NONAUTH, one has to *first* perform clean-up,
> and after multiple clean-up steps (at each step trying to measure
> impact), the community will have clear visiblity into what still is in
> ARIN-NONAUTH and what its importance is.

That’s certainly one approach - taking that which is known invalid and removing it, and continuing that process until there is a small amount of relevant data left.  

There is also the approach of focusing on what is relevant and operational today and working to migrate those entries elsewhere. 

It is not inevitable that one approach must be done before the other, but rather the priority should depend to a great extent on how much is known relevant, known invalid, and those ratios to the entire corpus. 

> That is not what is being suggested. Waiting a full year still is an
> incredibly aggressive timeline which to me doesn't seem warranted.
> 
> I would appreciate if ARIN takes their feet off the gaspedal on this
> project. ARIN would do well to perform an 'impact analysis' and share
> their conclusions with the community before proceeding. Use Routeviews,
> use IRR data from other registries, intersect those with each other...
> this is the same work I've been doing.

An excellent suggestion - well worth considering, particularly given the relatively modest amount on ARIN-NONAUTH entries germane to the DFZ. 

Thanks for the feedback!
/John

John Curran
President and CEO
American Registry for Internet Numbers