On Sun, Mar 24, 2019 at 12:51:52PM +0000, ripedenis@yahoo.co.uk wrote:
You seem to now be suggesting that a form of NRTM for only routing information (IRR data) and open to anyone without a contract would satisfy what you are looking for.
Yes.
I thought NRTM is a pull mechanism not a push?
A client connects to the NRTM server, and asks "did anything change since serial X?" where serial X is the last serial the client saw.
Aris mentioned you need this info to 'create filters'. Not being a routing expert, is this something you do periodically or in real time as routing information changes?
Filters are generated 'periodically', perhaps once a minute! But not as routing information changes.
If it's periodically then to pull an edited NRTM stream, only containing operational routing data updates, would work. If you want changes to routing data in the RIPE Database to trigger filter creation then you do need a new push mechanism.
indeed. Kind regards, Job