[lir-wg] AS Number Policy
Vladimir A. Jakovenko vovik at lucky.net
Tue Jul 9 22:15:48 CEST 2002
On Tue, Jul 09, 2002 at 03:57:49PM -0400, Lu, Ping 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. What is the reason (or advantage) in using AS numbers from PUBLIC pool for confederate ASes, if they are not visible outside of confederation? >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). Again - what is the reason in using AS numbers from PUBLIC pool for customer's ASes if this ASes will never appear outside of upstream ISP network? I may imagine only one case - customer's AS peering with public IX. >Technically I don't see how RIPE NCC can possibly find all the ASes that are >originated but invisible to the public route server. Agree. But there are also administrative possibilites. -- Regards, Vladimir.
[ lir-wg Archives ]