--On Tuesday, July 09, 2002 15:57:49 -0400 "Lu, Ping" <PLu at cw.net> wrote:
> Several examples:
>> 1. Confederate AS : only the top level AS number is announced by design,
> all member ASes should not be visible outside the confederate.
Which by desing should be done with private as:es. It's more or less in the
instruction book.
> 2. CIDR aggregate : If customer's address got aggregated by upstream ISP,
> usually you won't see their AS numbers from the upstream ISP's CIDR
> (especially for those people like to filter on allocation boundary).
I am lost. If customer routes are aggregated by upstream, I assume the
customer don't have an AS? If the customer have an AS and is multihomed you
might aggregate his addresses, but you will still see the originating AS in
the AS-path (or through the other path - as the customer won't get an AS
unless he is multihomed).
> Technically I don't see how RIPE NCC can possibly find all the ASes that
> are originated but invisible to the public route server.
I can't see how people should/could/would need AS:es from the public space
that is not visible in the public space.
- kurtis -

The RIPE NCC uses cookies. Some of these cookies may have been set already. More information about our cookies can be found in our privacypolicy. You can accept our cookies either by clicking here or by continuing to use the site.