[181940] in North American Network Operators' Group
Re: Dual stack IPv6 for IPv4 depletion
daemon@ATHENA.MIT.EDU (Mark Tinka)
Thu Jul 9 03:54:02 2015
X-Original-To: nanog@nanog.org
To: Mel Beckman <mel@beckman.org>, Greg Hankins <ghankins@mindspring.com>
From: Mark Tinka <mark.tinka@seacom.mu>
Date: Wed, 8 Jul 2015 20:47:37 +0200
In-Reply-To: <D3F1F0FD-F5B8-442B-B9BA-0F51DEBF7345@beckman.org>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On 8/Jul/15 17:59, Mel Beckman wrote:
> Greg,
>
> After investigating what a previous poster said about Cisco and Juniper, I'm getting the feeling that not all major impediments to running MPLS over IPv6-only networks have been addressed.
>
> Your comment mentions LDP IPv6 support. Do you now handle all the major gaps identified the the IETF MPLS IPv6 Gap Analysis (RFC7439) from this last January?
>
> https://tools.ietf.org/html/rfc7439#section-3
>
> It seems like their are still gaps in the MPLS spec itself before IPv6 has parity with IPv4 in MPLS.
The LDPv6 support is just the control plane portion to get labels
assigned to IPv6 addresses. This should get you basic forwarding of
encapsulation and forwarding of IPv6 traffic in MPLS. The immediate
use-case would be removal of IPv6 BGP routing in the core, if that is
your thing.
Otherwise, yes, there are still a bunch of MPLS gaps that need to be
fixed for those additional services to run natively over an IPv6-only
network. Baby steps...
Mark.
