[c-nsp] LDPv6 Census Check

adamv0025 at netconsultings.com adamv0025 at netconsultings.com
Tue Jun 16 10:00:17 UTC 2020

> From: Mark Tinka <mark.tinka at seacom.mu>
> Sent: Monday, June 15, 2020 4:07 PM
> On 15/Jun/20 12:13, adamv0025 at netconsultings.com wrote:
> > Not to mention this whole thread is focused solely on next-hop
> identification -which is just the lowest of the layers of abstraction in the
> vertical stack.
> > We haven’t talked about other "entities" that need identification like:
> VPNs, applications, policies (yes I'm looking at you VXLAN!) etc... - all of
> which are way better identified by a simple label rather than IPinIPinIP....
> The problem is if you want to have MPLS services signaled over IPv6, you first
> need an IPv6 control plane that will signal the labels that will support those
> services, i.e., LDPv6 and RSVPv6.
> Right now, all vendors that support LDPv6 do so only for pure MPLS-IPv6
> forwarding. If you want l2vpnv6, l3vpnv6, EVPNv6, 4PE, 4VPE, TE-FRRv6,
> e.t.c., you can't get that today. You'd have to signal those services over LDPv4
> or RSVPv4.
Hence my earlier comment on why I think it's not commercially feasible to switch to v6 control plane, (the only thing I'd be getting is MPLS-IPv6 which I already have (or have had) via L3VPN-6VPE), time will tell if I ever need to make the switch. 
But I'm thankful to you for doing the "ice breaking" for the rest of the community.  


More information about the NANOG mailing list