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 ]
Cynthia Revström
me at cynthia.re
Sat Mar 23 20:35:51 CET 2019
Hi Aris, see responses in line. On 2019-03-23 20:31, Aris Lambrianidis via db-wg wrote: > > 1. It still is a pull rather than a push mechanism You set up a connection to the RIPE NRTM service, then it pushes. > 2. It doesn't allow any granularity to receiving only specific > objects: We would > need to receive all of the database as-set and aut-num objects and > parse them for the ones we're interested in You can filter out the ones you don't want in your software, I like using IRRd4 and mirror the databases I want and then just connect to the Postgres DB. > 3. It needs some red tape before being able to consume it Not much to say here, it is true - Cynthia
- 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 ]