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/db-wg@ripe.net/
[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 ]
Edward Shryane
eshryane at ripe.net
Wed May 12 10:50:30 CEST 2021
Hi Erik, > On 12 May 2021, at 10:00, Erik Linder <erik.linder at gmail.com> 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 > > regards > erik > The cleanup job follows RFC6811 to match a route prefix: o Matched: A Route Prefix is said to be Matched by a VRP when the Route Prefix is Covered by that VRP, the Route prefix length is less than or equal to the VRP maximum length, and the Route Origin ASN is equal to the VRP ASN. In your example, the ROA should match the route object. I will check whether there is a conflict between the ROA and the route object. Regards Ed
- 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 ]