Quickstart Guide to IRR/RPSL
job at ntt.net
Thu Jul 19 18:30:17 UTC 2018
On Thu, Jul 19, 2018 at 11:19:12AM -0700, Kenneth Finnegan wrote:
> As for ARIN-WHOIS, I think I had gotten confused whether it was
> additive or exclusive of IRR objects for allowing prefixes.
Indeed, in arouteserver it is 'additive'. Documentation from ARIN is
> > 2/ I'd delete the "Step 2: Document Your Autonomous System’s Routing
> > Policy" step, nobody uses this.
> Is the expectation that the only source of a network's as-set is
> PeeringDB then?
Yes, or the IX/transit operator can ask what AS-SET to use during the
turn-up of the circuit.
> I have reason to believe there are IRR consumers who do parse
> export/mp-export statements. I think at least documenting an mp-export
> to AS-ANY policy is reasonable, but I'll reconsider that.
Globally I think there are only 2 or 3 organisations left that parse
this information. The vast majority either autodiscovers via peeringdb,
or just explicitly asks for it during provisioning.
> > Can I update http://peering.exposed/ and add FCIX with a 'yes' to
> > both secure route servers & BCP 214? :-)
> Please do. :-) $0 for 10G, N/A for 100G.
> The next IRR puzzle for us is converting a CSV of member ASNs to their
> as-sets to generate the requested AS33495:AS-MEMBERS as-set so our
> members can also generate filters against the route servers. It seems
> like there's probably a tool like bgpq3 that can turn a list of ASNs
> into an as-set of their exports, but I'm not seeing it.
bgpq3 can only go from IRR sources (using the RADB IRRd protocol) to
outputs such as Cisco, Juniper, BIRD, JSON - not the other way around.
> Anyone have something at hand, or am I breaking out the python soon?
More information about the NANOG