[171528] in North American Network Operators' Group
Re: Shared Transition Space VS. BGP Next Hop [was: Re: Best practices
daemon@ATHENA.MIT.EDU (Mark Tinka)
Sun May 4 17:37:29 2014
X-Original-To: nanog@nanog.org
From: Mark Tinka <mark.tinka@seacom.mu>
To: nanog@nanog.org
Date: Sun, 4 May 2014 23:37:03 +0200
In-Reply-To: <20140503092627.GR13966@besserwisser.org>
Reply-To: mark.tinka@seacom.mu
Errors-To: nanog-bounces@nanog.org
--nextPart2962173.tYc37yKd8M
Content-Type: Text/Plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
On Saturday, May 03, 2014 11:26:27 AM M=E5ns Nilsson wrote:
> Ideally, we would have a solution where an entire MPLS
> infrastructure could be built without v4 space, demoting
> v4 to a legacy application inside a VRF, but the MPLS
> standards wg seems content with status quo.
There is work ongoing in the MPLS IETF WG on identifying the=20
gaps that various MPLS applications have so they can be=20
prepared for IPv6 MPLS control and data planes.
Long overdue, if you ask me, but at least it's starting to=20
get some attention.
Mark.
--nextPart2962173.tYc37yKd8M
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)
iQIcBAABAgAGBQJTZrMCAAoJEGcZuYTeKm+GUDMQAKEB4mRMDfsGylXntqG/dYTf
czFJCVtqgPvNWFoYWvAFqttnOoqplG/4LWlNWy/gILXpv4biI74dk+17kdfB5G9c
/ajlMwrJgjvaODpJrtrzje0BikTmxuRLLvSx29dZAJaeP0PPda3WLW918PbhHxIH
bExCei7kq39tvZnAfQgu1nVfaj+1W8eERS8cLHNS5KNNDbvCddnYsXWKvAzGJ4Ab
Xun05XqaBnICW3pKFy9t5IFYjVG+1kJISVmjDk2NjIhkpEheCyssvTaQrmz7XloN
bGp0xer9vbqo8J3KZaHxHl9qpuoVIezx75oN/kmbBGMacixxQZISGgdW9ZUQlzis
bcPR+HS15SF7f4URiV0OFGvZyvwJs+bTLS7ddG7GXccrYoXNiSumyn2ETei5Pyov
/JzC5Xq6oIfjqcYEdSHiJqmMxhJ1WnYf0QfsIh2ze3cJm3IUseX+XFbr7baOFVMm
Nj4wV2O4PBFHnA8Rd7HtMDi2Gc3v2nsOg7V2PBCyy44Nd1FYQINrgOezmimPFHud
AVZJXNHBRUN2WRGtt8SbT6gk3pRMOfo++de0NPl608lEY1MZEgJ4HznPB4SlemiT
RuaYncIXC3EPAz+HBdVXjvAEmgbsMG0KQiNeNc88a9cCkvJ295Zp8y/11Piv2TpV
bS9FTIdwDsLZ1TSac4fr
=1+mO
-----END PGP SIGNATURE-----
--nextPart2962173.tYc37yKd8M--
