[j-nsp] Policy option for advertising full routes

[Erdem Sener]

and this proves one should not reply to e-mails at 4am, if minds to be
ashamed :)

Of course, tagging communities with import policies and building
export policies based on those would be much better on large scale
networks, and this is what we're doing anyways :)

Erdem

On 10/22/05, Jeff S Wheeler <jsw at inconcepts.biz> wrote:
> On Sat, 2005-10-22 at 03:28 +0300, Erdem Sener wrote:
> > term My-Upstreams {
> >     from as-path-group Upstreams;
> >     then accept;
> > }
>
> You would be much better off using BGP communities as the basis of your
> export policy.  Your suggested policy requires the operator to maintain
> as-path-groups on all customer-facing routers anytime a neighbor is
> added or removed.  In addition, you did not consider the need to export
> your own routes to the downstream customer.  Your policy will certainly
> advertise transit, peer, and customer routes; but not your own!  You'd
> better hope you're honoring default from one of your transit providers,
> or your customer will be able to reach everyone but you ... ;-)
>
> - J
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>