[ixpmanager] IRR updating issue with BGPQ3

[Douglas Fischer]

Just to bring more complicated things to the table...

And what about using the AS-SET object declared in PeeringDB?

The more usual (and relaxed) syntax is AS65123::AS-CUSTOMERS, or
AS-JOHNDOENET
But the mor strict (and more correct, in my opinion) syntax is RADB::
AS65123::AS-CUSTOMERS or RADB::AS-JOHNDOENET

On the first syntax the ASN operator is saying to the world:
"The AS-SET that defines the cone of prefixes that can be announced by our
network is this one."

On the first syntax the ASN operator is saying to the world:
"The AS-SET that defines the cone of prefixes that can be announced by our
network is this one. And you should be considered true just the information
in the RADB IRR."



Em seg., 3 de jul. de 2023 às 19:24, Nick Hilliard via ixpmanager <
ixpmanager at inex.ie> escreveu:

> Paul Emmons wrote on 03/07/2023 22:56:
>
> Agreed, but here is a deeper issue that is happening that I can show using
> actual participants.   Member uses ARIN as their IRR - very high quality
> IRR and that member doesn't have any down streams. Member B provides
> downstream to A but Member B just uses their AUTNUM and not an AS-SET for
> Member A.  Member B has their AS-SET as RADB (not the worst but they do
> refuse to remove proxy routes that don't exist).  Member A's prefixes are
> filtered out of Member B's announcements in the route servers.  (Member A
> still has connectivity on the exchange.  But what happens if Member A's IX
> circuit goes down or if Member A isn't on the exchange?
>
> It is probably more of an issue of training member B not to use AUTNUMs
> for down streams.  Maybe some form of reporting would be helpful.  (I
> always start at the IX looking glass).
>
>
> yep, getting this sort of thing right takes work and engagement with IX
> participants.  Birdseye is designed to make it easy to catch this sort of
> misconfig and it's a good idea to take a peek through what prefixes are
> being rejected to see if the irrdb policy can be tweaked to make it better.
>
> Also, pulling data from several sources is troublesome.  At least IRRD4
> means it's no longer non-deterministic, although there are still plenty of
> failure modes.
>
> Nick
> _______________________________________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> Unsubscribe or change options here:
> https://www.inex.ie/mailman/listinfo/ixpmanager
>


-- 
Douglas Fernando Fischer
Engº de Controle e Automação
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20230704/aedb1449/attachment.htm>