[db-wg] Out-Of-Region routes ?
Nick Hilliard nick at foobar.org
Wed Jul 3 13:01:50 CEST 2019
Ronald F. Guilmette via db-wg wrote on 03/07/2019 11:49: > My recollection is that there came a time ... I can no longer remember > if that was just last year or the year before... when it was decided > and implmented that the RIPE DB would no longer allow the addition of > route objects for out-of-region address space. > > Somebody please refresh my memory. At that time, how was it decided > that pre-existing route objects for out-of-region IP address locks > would be handled? > > I gather than those were not in fact ejected from the data base, but > rather that it was decided... I seem to recall... to simply mark them > in some distinctive way. Is that correct? And if so, what was/is that > distinctive marking? All out-of-region routes were moved from having "source: RIPE" to having "source: RIPE-NONAUTH". The change happened on Sep 4th 2018: > https://www.ripe.net/publications/news/announcements/changes-to-out-of-region-objects-in-the-ripe-database This makes it possible to filter out authoritative entries from non-authenticated entries - if you select only source: RIPE, you'll only get authoritative entries. It is no longer possible to create out-of-region objects in the ripe database. This means that the prefixes that are there can be updated, but if they are deleted, there is no way to re-insert them. Nick
[ db-wg Archives ]