<html><head></head><body><div style="color:#000; background-color:#fff; font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_ym19_1_1539599962189_375482">Hi guys</div><div id="yui_3_16_0_ym19_1_1539599962189_375818"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1539599962189_375816">There is a corner case where invalid ROUTE(6) objects may occur in the source: RIPE database. Before NWI-5 a ROUTE(6) object could be created either by the address space holder or the ASN holder. Both had to authorise the creation, but whoever created the object would maintain it.</div><div dir="ltr" id="yui_3_16_0_ym19_1_1539599962189_375972"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1539599962189_375700">Suppose the ASN holder created an object and maintains it, then the address space holder chooses another ASN to announce the address space. The address space holder can delete the ROUTE(6) object using the Force Delete mechanism(1), if they know about it. But many resource holders still don't know such mechanisms exist. They may instead just create an RPKI ROA for the new announcement and leave the old ROUTE(6) object in the database.</div><div dir="ltr" id="yui_3_16_0_ym19_1_1539599962189_375779"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1539599962189_375762">AFAIK there isn't yet any alignment mechanism, but it has been talked about recently, and the cleanup proposal under discussion only applies to source: RIPE-NONAUTH (but I'm not suggesting you extend it). Although this is a corner case, it means you can't guarantee all the data in source: RIPE is still authoritative.</div><div dir="ltr" id="yui_3_16_0_ym19_1_1539599962189_375808"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1539599962189_375842">(1) <a href="https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-database-documentation/10-authorisation/10-13-force-delete-functionality" class="" id="yui_3_16_0_ym19_1_1539599962189_375841">https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-database-documentation/10-authorisation/10-13-force-delete-functionality</a></div><div dir="ltr" id="yui_3_16_0_ym19_1_1539599962189_376004"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1539599962189_375933">cheers</div><div dir="ltr" id="yui_3_16_0_ym19_1_1539599962189_375934">denis</div><div dir="ltr" id="yui_3_16_0_ym19_1_1539599962189_376014">co-chair DB-WG</div><div dir="ltr" id="yui_3_16_0_ym19_1_1539599962189_376016"><br></div><div id="yui_3_16_0_ym19_1_1539599962189_375862"><br></div><div id="yui_3_16_0_ym19_1_1539599962189_375923"><br></div></div></body></html>