[prev in list] [next in list] [prev in thread] [next in thread] 

List:       juniper-nsp
Subject:    Re: [j-nsp] Standard practice for customer eBGP peering traffic engineer
From:       Hugo Slabbert <hugo () slabnet ! com>
Date:       2017-11-14 23:09:22
Message-ID: 20171114230922.GB28211 () bamboo ! slabnet ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Mon 2017-Nov-13 15:27:36 +0000, Nick Cutting <ncutting@edgetg.com> wrote:

>What is the benefit for a customer or a provider in doing this v.s just 
>the customer prepending their own AS?

Prepending done customer side would be visible to anyone beyond that first 
BGP peering between the customer and provider, including any of the 
provider's other BGP customers.

Generally, these provider prepend communities would be targeted for 
external relationships.  So, example would be that you want to have 
provider X's customers send to you directly via provider X, but provider 
X's peering sucks so you want anyone who is *not* a direct customer of 
provider X to avoid routing through provider X.

-- 
Hugo Slabbert       | email, xmpp/jabber: hugo@slabnet.com
pgp key: B178313E   | also on Signal

["signature.asc" (application/pgp-signature)]

_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[prev in list] [next in list] [prev in thread] [next in thread]