[db-wg] Route objects for space administered by other RIRs
- Previous message (by thread): [db-wg] Route objects for space administered by other RIRs
- Next message (by thread): [db-wg] Route objects for space administered by other RIRs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at sobornost.net
Wed May 12 11:08:48 CEST 2021
Dear Erik, On Wed, May 12, 2021 at 12:00:52PM +0400, Erik Linder via db-wg wrote: > is there a need for the ROA object to be identical in length to the route > object? > > take 41.213.128.0/21 is a RIPE-NOAUTH route object and there is a > valid ROA from AFRINIC for 41.213.128.0/17 max length 24 Following the RFC 6811 procedure, the RIPE-NONAUTH route object is 'valid' from a RPKI ROA perspective. 1) 41.213.128.0/17 covers 41.213.128.0/21 2) the /21 prefix length is between /17 and maxlength /24 3) the origin AS in the ROA is equal to the origin AS in the RIPE-NONAUTH object A current overview of related objects is available here: https://irrexplorer.dashcare.nl/prefix/41.213.128.0/21 I recommend reaching out to RIPE NCC directly and request them to remove the objects manually: https://www.ripe.net/contact-form "RIPE database" -> "contact form" Kind regards, Job
- Previous message (by thread): [db-wg] Route objects for space administered by other RIRs
- Next message (by thread): [db-wg] Route objects for space administered by other RIRs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]