Open coxley opened 8 years ago
I think this sounds great on the surface and in my mindbrain. Could you please explain a little bit of your reasoning for this and perhaps some example use-cases for ASNs as a discrete resource type?
Well, we use asn=<AS>
as an attribute for some network resources to show route origin, but there's not currently a way to explain what that represents.
My thoughts are to have a way to ask what this entity is vs what originates from it.
The main feature I'm missing from NSoT at this point (other than maturity which is continuing to come!) is ASN support.
We have many internal ASes slewn about, many of the main ones I remember but corporate ones I don't. That and these numbers have little meaning to those outside of our teams which is why the internal NSoT IRC bot script is popular.
This is a feature request to implement this.