Dear Colleagues, thank you all for your feedback. We will implement the following for NWI-5, and also deploy to production on 4th September:
- Separate NRTM streams by source. Updates to out of region objects (route, route6, aut-num) will appear on the RIPE-NONAUTH stream only. In order to be notified of all changes, NRTM clients will need to query both streams. After NWI-5 is deployed to production in September, the updates to change the source on out of region objects will appear on the RIPE-NONAUTH stream. - Move out of region objects into a separate database dump file, and split files. We will deploy these changes separately to the Release Candidate environment, and will notify the current NRTM users individually. Regards Ed Shryane RIPE NCC > On 23 Jul 2018, at 11:46, Piotr Strzyzewski <[email protected]> > wrote: > > On Thu, Jul 19, 2018 at 07:40:33PM +0000, Job Snijders via db-wg wrote: > > Dear All, > >>> We also do not plan to separate the database dumps by source. This can >>> be done, but any consumers need to make adjustments or will no longer >>> find out of region objects. >> >> yes, that is the point. We make a change, and people need to update if >> they rely on this. By splitting the NRTM and database dumps, most >> implementations only need to add an additional source, rather than >> reprogram their client software to understand that what used to be a >> single file containing a single source, now contains multiple sources. >> >>> I welcome discussion on these points, we will implement as the DB-WG >>> prefers. >> >> Because of NWI-5 the RIPE IRR is splitting into two, and we should plan >> accordingly. To me that means separate database dumps and separate NRTM >> streams. > > Although I do not run NRTM, I fully support Job's point of view. It is > consistent with current practice. > > Piotr > > -- > Piotr Strzyżewski > Silesian University of Technology, Computer Centre > Gliwice, Poland
