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/[email protected]/

[db-wg] Route objects for space administered by other RIRs

Previous message (by thread): [db-wg] New on RIPE Labs: RPKI Repositories and the RIPE Database in the Cloud
Next message (by thread): [db-wg] Route objects for space administered by other RIRs

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Ronald F. Guilmette rfg at tristatelogic.com
Wed May 12 02:06:28 CEST 2021

Can anyone please explain to me, preferably using small words that
I can understand, why route objects such as the following still exist
in the data base at the present time?

route:          62.61.192.0/18
descr:          SRR
origin:         AS49902
mnt-by:         CEGETEL_LA_REUNION
created:        2014-09-30T15:01:51Z
last-modified:  2018-09-04T18:00:38Z
source:         RIPE-NONAUTH

(Please note that the whole of 62.61.192.0/18 currently appears to be
under the administration of AFRINIC.)

I understand that pre-existing route objects within the RIPE data base
that relate to IP space which is under the administration of other
(non-RIPE) RIRs was set to "RIPE-NONAUTH" awhile back, which is
certainly a Good Thing, but I wonder if there is a date certain by
which even these route objects will be sunsetted and removed from the
RIPE db.


Regards,
rfg

Previous message (by thread): [db-wg] New on RIPE Labs: RPKI Repositories and the RIPE Database in the Cloud
Next message (by thread): [db-wg] Route objects for space administered by other RIRs

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]