[routing-wg] source: RIPE may also contain invalid ROUTEs

Hi,

On Wed, Oct 17, 2018 at 08:22:54PM +0000, denis walker via routing-wg wrote:
> 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.

It is still authoritative in the sense of "we know that the owner of the
address space authorized creation of the route(6) object".

If they decide to have multiple different origins in the RIPE-DB, it's
still *authorized* data - and there might be good reason (like preparing
a move to a new origin AS, or just having moved and not yet cleaned up, 
etc).

We might want to send the object owner a notification from RIS(?) if
a conflicting ROA is detected, but I see no incentive to force-delete
these objects.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.ripe.net/ripe/mail/archives/routing-wg/attachments/20181018/e1c10acb/attachment.sig>