[j-nsp] Standard practice for customer eBGP peering traffic engineer

[Hugo Slabbert]

On Mon 2017-Nov-13 15:27:36 +0000, Nick Cutting <ncutting at 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 at slabnet.com
pgp key: B178313E   | also on Signal
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20171114/8fb9f174/attachment.sig>