-----Original Message----- From: Kurt Erik Lindqvist [mailto:kurtis@kurtis.pp.se] Sent: Thursday, July 11, 2002 6:41 AM To: lir-wg@ripe.net Subject: RE: [lir-wg] AS Number Policy
A customer can have a peer with the default transit, which aggregates the adresspace from the customer, and the customer can have other peerings via some ix:es, and the customer could perform transit to/from the ix:es to the default transit, in this scenario the customer MUST have a public AS, which you will not see in the public space, since removing private AS in the AS-path will result in somewhat unpredictable behaviour if there are several private AS involved at the customer premises.
Yes, but this still makes the AS publicly visible.
Best regards,
- kurtis -
As we already seen some real examples, the correct USED ASN will only be seen from their upstream (it is public no matter what) but not outside to other peers (may due to CIDR, may due to inactive route). This has nothing to do with private ASN but make it impossible to enforce the proposed policy just by looking at the RIS. I agree that RIPE NCC need to have an ASN revoke policy but just can NOT based on the RIS info only. Ping Lu Cable & Wireless USA Network Tools and Analysis Group W: +1-703-292-2359 E: plu@cw.net