Problem appears to be that as I'd apply these to _inbound_ lists, and
pretty much nobody has structured their policy like ASy:AS-CUSTOMERS:xxx,
this can't really be done. :-( (It would also get very complex with
customers' customers but that's a fringe case probably).
It appears the only way to do this would be to bug the peers to build
their policy using those Customer sets.. somehow I dont' see them jumping
right into this :-/
Well in my case I was using my own registry (and just registering a
copy at RADB for info) so I could create all the sets I wanted :-)
You could use a different naming scheme if you wanted to host the
objects at RADB (just prepend every name with your AS number) and
didn't want to badger your customers/peers into doing "the right
thing"[tm].