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

Hi Ronald,

less than a week ago, on this same list there was the conclusion that
these route objects would be removed.
real-soon-now, is my understanding.

That should resolve *this* issue.
But I think the holders could then create a similar route object in
AfriNIC...


Another thing that confuses me:

[I see the inetnum object in AfriNIC, but:]

$ whois -h whois.iana.org 62.61.192.0
says one should look at RIPE whois for the whole /8

and
$ whois -h whois.ripe.net 62.61.192.0
says "nothing here - look at IANA"

shouldn't IANA point to AfriNIC??

Regards,
Frank

On 12/05/2021 03:06, Ronald F. Guilmette via db-wg wrote:
> 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
>