Best practice for BGP session/ full routes for customer

Mark Tinka mark.tinka at seacom.mu
Tue Jul 8 20:58:32 UTC 2014


On Monday, July 07, 2014 08:46:05 PM Jason Lixfeld wrote:

> 1.  You already know that multihop is very ugly.  If it's
> for a one-off, it's probably fine.  But building a
> product around multi-hop wouldn't be my first choice.

We prefer Layer 2 bundling technologies like 802.1AX, POS 
bundles or ML-PPP. 

However, some customers just can't support this, but have 
multiple links to us and need load sharing. In this case, 
eBGP Mulit-Hop is a reasonable use-case.

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20140708/b99ef873/attachment.pgp>


More information about the NANOG mailing list