<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="background-color: rgb(255, 255, 255); color: rgb(0, 0,
0); font-family: Tahoma; font-size: 16px;" text="#000000"
bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 2/Oct/17 11:24, Andrew Alston wrote:<br>
<br>
</div>
<blockquote type="cite"
cite="mid:20171002094105.4CB5A3087F73_9D209B1B@mx1.seacom.mu"
style="border-left: 2px solid #009900 !important; border-right:
2px solid #009900 !important; padding: 0px 15px 0px 15px; margin:
8px 2px; background-color: null !important; color: null
!important;">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--><o:p> </o:p>
<div class="WordSection1">
<p class="MsoNormal">I figured I’d drop a note that may be of
interest to some of you.</p>
</div>
</blockquote>
<br>
Thanks, Andrew, for sharing your experiences.<br>
<br>
<br>
<blockquote type="cite"
cite="mid:20171002094105.4CB5A3087F73_9D209B1B@mx1.seacom.mu"
style="border-left: 2px solid #009900 !important; border-right:
2px solid #009900 !important; padding: 0px 15px 0px 15px; margin:
8px 2px; background-color: null !important; color: null
!important;">
<div class="WordSection1"><o:p></o:p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Effectively though – it is now possible to
remove V4 entirely from P routers without losing any
functionality – providing you engineer it right. So we’re
making progress
<span style="font-family:"Segoe UI
Emoji",sans-serif">😊</span><o:p></o:p></p>
</div>
</blockquote>
<br>
So as you've confirmed again, a number of MPLS-based applications
still do not have native IPv6 support, while they do in IPv4. This
issue is compounded when operators maintain not only equipment from
different vendors, but also different equipment from the same
vendor. As if that's not enough, different software with different
levels of feature support from the same or different vendors, for
the same or different equipment.<br>
<br>
We, for example, are a triple-vendor network - Cisco, Juniper and
Arista. Fair point, we only use Arista for Layer 2 core switching,
so those boxes do not participate in our MPLS domain. However, we
have different platforms from Cisco and Juniper in operation, each
running their own versions of software that are at different levels
of development re: MPLS applications over IPv6.<br>
<br>
Unless one is bound to recover a significant amount of IPv4 space by
converting one's backbone (core, edge, or both) to IPv6-only, I'd
only consider doing MPLSv6 network-wide once there is parity within
and between vendors. I'd probably spend more time delivering working
IPv6 to customers, until that day.<br>
<br>
I can imagine the cluster-mess enabling MPLS applications for
IPv6-only that would ensue if anyone tried this with the current
state-of-the-art.<br>
<br>
Mark.<br>
</body>
</html>