This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] In-band notification mechanism?
- Previous message (by thread): [db-wg] In-band notification mechanism?
- Next message (by thread): [db-wg] In-band notification mechanism?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Sun Mar 24 15:41:18 CET 2019
On Sun, Mar 24, 2019 at 12:51:52PM +0000, ripedenis at 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
- Previous message (by thread): [db-wg] In-band notification mechanism?
- Next message (by thread): [db-wg] In-band notification mechanism?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]