[55809] in North American Network Operators' Group
re: BST - BGP Scalable Transport
daemon@ATHENA.MIT.EDU (Cengiz Alaettinoglu)
Tue Feb 11 11:43:45 2003
From: Cengiz Alaettinoglu <cengiz@packetdesign.com>
To: Ron da Silva <ron@aol.net>
Cc: NANOG <nanog@merit.edu>
In-Reply-To: <20030210192439.GD20317@aol.net>
Date: 11 Feb 2003 08:43:04 -0800
Errors-To: owner-nanog-outgoing@merit.edu
Hi Ron,
On Mon, 2003-02-10 at 11:24, Ron da Silva wrote:
> Van/Cengiz/Kedar,
>
> Questions that missed the cutoff at the end of your preso:
>
> Most operators have some per-peer inbound policies. Since the
> next hop adjacency may move around due to chaning primaries,
> where do you configure the policy ? (all routers?)
>
Yes. The entire pool of routers responsible for ebgp peers on that
location needs to share the configuration information because any one of
them could be the primary for that peer.
> Also, some of those polices include modifying attributes before
> forwarded the update internally via iBGP. Where does the
> policy get implemented? (on the NA box?)
>
Policy is applied at the primary and the secondary routers for the ebgp
peer. The bst sessions used for handling the ebgp peer and ibgp peers
are different and the rest of the routers will only learn the modified
routes from the primary.
Cengiz
