prefix filter generation for customers

[Phillip Vandry <Phil.Vandry () telus com>]

Hi,

I'm looking for input about how other people deal with this problem:

We generate prefix filters for our customers from RADB using their AS 
or as-set. Our upstreams do the same for us.

Our filters are generated with a simple WHOIS query and will pick up
objects not only from RADB but from the various other IRRs that are
mirrored in RADB.

The problem is that it looks like at least one of our upstreams does not
pick up the route objects that are in IRRs other than the one we asked
them to use for us (RADB). One of our customers uses a different IRR and
their routes did not get included in the filter generated by our upstream.

Do we need to force all of our customers to use the same IRR as we do,
or is there some way that we can support offering our customers a
choice of IRRs just like our upstreams do for us?

-Phil