From: Peter van Oene (pvo@xxxxxxxxxxxx)
Date: Wed Jul 10 2002 - 09:20:34 GMT-3
Where is it recommended that one set no-export on inbound routes for this
purpose? This sounds pretty weak to me. Most ISP's will mark routes as
transit/peer/customer/local-as-aggregate etc with a community structure and
explicit accepts on various communities for advertisement while rejecting
all other routes.
For example, to a peer I'd announce local-as-aggregate/customer, to a
customer I'd announce somewhere in between all routes,
local-as-aggregate+customer(partial)+default or just default and to a
transit provider I'd announce local-as-aggregate/customer+ any per peer
specifics I might want to leak for TE reasons.
Pete
At 03:48 AM 7/10/2002 -0700, ccie candidate wrote:
>community "no-export"
>--
>
>On Wed, 10 Jul 2002 08:43:12
> Ademola Osindero wrote:
> >Hi group,
> >
> >How do u prevent your AS from being a transit AS without usisng AS PATH
> >FILTERING?
> >
> >Regards,
> >
> >Osindero Ademola
> >Schlumberger Network Solutions
> >Tel: 234 1 261 0446 Ext 5427
> >Fax 234 1 262 1034
> >email:osindero@lagos.sns.slb.com
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:25 GMT-3