[172763] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Best practice for BGP session/ full routes for customer

daemon@ATHENA.MIT.EDU (Mark Tinka)
Tue Jul 8 17:04:07 2014

X-Original-To: nanog@nanog.org
From: Mark Tinka <mark.tinka@seacom.mu>
To: nanog@nanog.org
Date: Tue, 8 Jul 2014 22:58:32 +0200
In-Reply-To: <1E4F174D-09C6-4F40-80B7-B0DC9FAE79A6@lixfeld.ca>
Cc: Jason Lixfeld <jason@lixfeld.ca>
Reply-To: mark.tinka@seacom.mu
Errors-To: nanog-bounces@nanog.org

--nextPart1865859.ZlYOoJXEOV
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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=20
bundles or ML-PPP.=20

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

Mark.

--nextPart1865859.ZlYOoJXEOV
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)

iQIcBAABAgAGBQJTvFt4AAoJEGcZuYTeKm+GazQP/RRp5eJ200GaX9eW8JYguOba
xo8ZPAEGJ+Les6qxlPyRnX+WNP59jXHm+KcMZcHPVW1RruKJzC04VKPOvGU6EWUD
KrU0yRfYOCuX4h5EnQ87oQ3SDZNnxSC6lXBW9bgFXmVLudRfd9MJ1/NqGECEZXAx
oNo/YTGkUq1NpI6TWtAN+fixbo2LqbJLqPrqbsaMEvloJsd3wlIrJHN42Vl6Vy2O
GU1QecvqvNxzXkuJfzBlBhwGEwffabOOklPgY5K4XQEQoOgf2L6GzlhHvXTI1QOB
0LwKj03j7VbTmnGblqXymn9rroLs/Wdl6reKWLr9Gwp1v0HfsvdYhd88nw/ztPs7
qE7Ye1+C2Hj069X+Fw3Y7n1YN5zzrFdHGdsfPdxlNTpAAN/j8exKHaOUESg0GPfz
26op1mqd401/Ij87yC1ocdkmiJmDFEwRrtjYSP1uUeKXHwgScZ8g2YlB6lEDIZGW
aMfxYwzLoUG2z3vvxgm/5yhy0uwKEacHUn5vbkDVUM7S1Rfvd3ECcxBOwSZuBTPe
eFDZ/maMuvPzQh9s2KJIsx1FBBNVGLLvKczV8WMp8nKgPUB+wwAmmxX485FiW/AK
hhFnIlCt2CRKZRcvdDqNoEA4+tGrdUSxqLTYRF0saz4Km6wb0x375TaGe/QiYK93
Ffbcw6XLN0KfQvpYAn4r
=nU/+
-----END PGP SIGNATURE-----

--nextPart1865859.ZlYOoJXEOV--

home help back first fref pref prev next nref lref last post