[177156] in North American Network Operators' Group
Re: MPLS VPN design - RR in forwarding path?
daemon@ATHENA.MIT.EDU (Mark Tinka)
Fri Jan 2 13:28:39 2015
X-Original-To: nanog@nanog.org
From: Mark Tinka <mark.tinka@seacom.mu>
To: nanog@nanog.org
Date: Fri, 2 Jan 2015 20:24:48 +0200
In-Reply-To: <54A5C5A0.3040506@foobar.org>
Reply-To: mark.tinka@seacom.mu
Errors-To: nanog-bounces@nanog.org
--nextPart2047175.Vp16Fo6HQb
Content-Type: Text/Plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
On Friday, January 02, 2015 12:09:36 AM Nick Hilliard wrote:
> there are patches for both code-bases and some
> preliminary support for vpnv4 in quagga, but other than
> that neither currently supports either ldp or the
> vpnv4/vpnv6 address families in the main-line code.
LDP support would not be necessary for an out-of-path RR,=20
but lack of VPNv4/VPNv6 is hurdle.
Mark.
--nextPart2047175.Vp16Fo6HQb
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)
iQIcBAABAgAGBQJUpuJwAAoJEGcZuYTeKm+GwgQP/AuUA7+3AzB6KMk1ohFFrZZ6
JyS1KHxt/ajfKCYJFD+aHM3mfbOFGSHHJSltVbLNL0dCp/BTOoYE5ZKTustCDYX4
/+9VcvRwjqYanVwgpsjzCL/qPS6tpcpbyR0WD9Ch60rZ8C9WtCi1b/bM5YDVUVmX
gw9QOAW8dtvJ+qXiD91DYIZJY8KbHfeWyKCfs14aDlzAC5OQgVtMGI8Yvm8OeOHa
VlEJvTKy0TGN6pfHT3AYSOyhmcFu51ywLVwYWGo4BHZSgW6uWpOhLv42OV7MVOPq
Y2P0mvrtEmgsAtMYzeRMRRinoHoLLfdEV8zSGBFKYWWc8H71uE6DSKQGOWtpoo4o
6+9fwRh8V4WPwANfnslETdnmLxqNEvXhHCmhqNOiPqIjQTZZg7KNxxGDIv6P8b3T
DvnTj8l9cjoT7C9/OonyFJLZ7atuPwaP5Qgh9xUfguTXpqEAcuhUkldVe46ZZdFi
BLuDkusDJeyNKfuZaty6HqET71U32dnrAOiAzTWNk5RCxfV5ldAlGPtrhMFPFL0y
2ePRtedfU36ynITL917sJQBLDbdZBEBFx+lpFL9SmpmiG/3LeYvhbgvmFSYsL+pu
Nwj05k7OldvhqLzyYM/5gjEiDVFumVFhDheJBAQ/UmK9amFIhVHs5R6SUScFa3uH
i4imiW2HSXFVtNrGVEtg
=1BP0
-----END PGP SIGNATURE-----
--nextPart2047175.Vp16Fo6HQb--
