Show ASNs per RIR

[ryanmerolle]

NetBox version

v3.1.6

Feature type

New functionality

Proposed functionality

Currently the page for a RIR record only shows the associated aggregates, and it only has a button to add an aggregate.

With ASNs needing to be associated to a RIR, the RIR object view should be updated accordingly.

Use case

Enable consistency with regards to object pages in the GUI.

Database changes

N/A

External dependencies

N/A

[PieterL75]

Maybe an idea to introduce LIRs on top of the RIR?
LIRs own address space and ASN's.

The RIR object has always confused me. There are only 5 RIRs, so why make them dynamic?

Currently I use a RIR rather as a LIR.
A LIR would model the IP world better, because it is the glue between public ASN and the prefixes.

P

[ryanmerolle]

That sounds like a feature request to create a way to model LIR membership. I get your thinking and confusion, but it likely is a low return and high investment feature request. It can be useful for modeling when there is some reason a company manages multiple LIRs (maybe an MSP with tenants, or a firm that went through some mergers and acquisitions).

This feature request was just to enable some assumed functionality within the NetBox views given this view is in place for most other objects with similar relationship models.

[DanSheps]

LIRs own address space and ASN's.

At least in North America, ASN's are only owned and managed by the RIR. LIR's do not handle ASNs. LIR's only handle allocations for sub-delegation. I don't think this relationship needs a model, as in most cases LIR's could be modelled by a "tenant" on a prefix.

It looks like, at least for ASN's, APNIC, RIPE, LACNIC, and AFNIC are all the same

Prefixes could be modelled differently, but it looks like at least a few use the RIR > NIC > LIR. I think it is easier to just model RIR.

With ASNs needing to be associated to a RIR, the RIR object view should be updated accordingly.

100% agree with this. This was an oversight when I did the ASN model.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

[github-actions]

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.