[c-nsp] Good practices for peering

[A. Rahman Isnaini R Sutan]

----- Original Message -----
From: "Marko Milivojevic" <markom at pangalactic.net>
To: "Vincent De Keyzer" <vincent at dekeyzer.net>
Cc: <cisco-nsp at puck.nether.net>
Sent: Wednesday, December 28, 2005 11:17 PM
Subject: Re: [c-nsp] Good practices for peering


> > List 1 is to announce only my routes; list 2 is to make sure that the
>  > other guy does not leak any route towards me.
>
> So, you will accept 0.0.0.0/0 originated in his AS? :-)
>
> What I would do is move all the rules into route-map's and use other
> utilities to build filters based on information in route information
> databases. It puts some overhead on your operations, but it's worth if you
> have more than just a few peers and upstreams. If you are providing
transit
> to customers, it's even more valuable.
>
> Marko.

I completely agree and route-map gives more flexible in reconfiguring the
routing policy (advertising, filtering, etc)

A. Rahman Isnaini R. Sutan
-- Network Operation Division


> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>