[afnog] What are the major challenges in enabling Services to run on IPv6?
Mark Tinka
mark.tinka at seacom.mu
Tue Oct 28 11:38:38 UTC 2014
On Tuesday, October 28, 2014 01:31:36 PM Andrew Alston
wrote:
> Actually that's in the pipeline for what we want to do.
> There are large segments of our network that I could
> comfortably run V6 only on *IF* I had an ability to do
> Martini PW over v6, but sadly, since Martini PW still
> requires LDP in most vendor implementations, this is not
> possible yet. I believe that LDPv6 is on the Juniper
> and Cisco roadmaps for 2015 (though I am open to
> correction on this), and if that happens, I can tell you
> right now, that for at least 1500 devices I can think of
> off the top of my head, v4 will be a thing of the past.
This is the current state of the LDPv6 work:
http://tools.ietf.org/html/draft-ietf-mpls-ldp-ipv6-14
It has come a long way since 2009, but there is still a very
long way to go.
Even though LDPv6 becomes available, there are still a
number of applications that need to be brought up to snuff:
http://tools.ietf.org/html/draft-ietf-mpls-ipv6-only-gap-02
One possible path to a quick solution is SR (Segment
Routing), but the community is looking at traffic
engineering and SDN/NFV as immediate applications for SR -
so MPLSv6 is taking a back seat for now.
Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://afnog.org/pipermail/afnog/attachments/20141028/92ce53eb/attachment.sig>
More information about the afnog
mailing list