validate IRR/RPKI

[forkwhilefork]

this could be done in the frontend or the backend, but I think it would be a lot more efficient to do it in the backend.

[forkwhilefork]

after much testing and consideration, here is the current plan:

• pull rpki json file from NTT when it changes (https://rpki.gin.ntt.net/api/export.json)
• pull IRR DBs every....10-15 mins? and generate json file using https://github.com/forkwhilefork/irr-jsonify
  • this will actually generate two files, one with route(6) objects and one with AS-SET members
• parse all three json files, process them a bit, and store them as binary files
  • I think it makes more sense to do this in a separate process so (1) we're not converting them unnecessarily every time bgp.exposed starts even though outside of dev that's not very often and (2) we're not loading the whole json files into memory and then just waiting for them to get GC'd
• when the binary files change on disk, somehow signal the bgp.exposed core process to re-load them
• on reload just dump the previous trie and use the new one. probably need a lock on the object.
• do validation in the core between getting a "route received" message from the BGP process and sending it to the client - basically enrich in-path

[forkwhilefork]

Updated the previous comment with the current plan. The prerequisites are almost done, just waiting on bgp-exposed/irr-jsonify#3 and bgp-exposed/rpki-fetch#1. Then we can start implementation in this repo.