<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr">Wouldn’t it be great if when IPv6 was designed there was some kind of automatic translation that could take place so that IPV four could go through a router that understands both IPv6 and IPV four and translate it?<br><br>I’m not talking about NAT, but someway that that router could actually route between the two, it would solve many of these problems that keep coming up over and over.</div><div dir="ltr"></div><div dir="ltr"></div><div dir="ltr"><br>On Oct 2, 2019, at 6:03 PM, Naslund, Steve <<a href="mailto:SNaslund@medline.com">SNaslund@medline.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr">
<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:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">In my experience, the biggest hurdle to installing a pure IPv6 has nothing to do with network gear or network engineers. That stuff I expect to support v6. This biggest hurdle is the dumb stuff like machinery
interfaces, surveillance devices, the must have IP interface on such and such of an obsolete appliance, etc. The dumb legacy app that supports the ancient obsolete pen plotter that we must keep forever, etc.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The next largest hurdle is trying to explain to your server guys that you are going to go with all dynamically assigned addressing now and explaining to your system admin that can’t get a net mask in v4 figured
out, how to configure their systems for IPv6. There are a lot of people in the IT industry who are not nearly ready for v6. In large enterprise networks, there is lots of East/West communications between systems and that is very difficult to transition through
a dual stack process without tripping over a bug or serious incident.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">It is really hard to look at cost difference in v6/v4 but there will be a definite learning curve with the associate oops moments and re-education that all costs time/money/downtime. The simply reality is that
there are more IT people that understand v4 and do not understand v6 yet.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Steven Naslund<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Chicago IL<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">></span>I'd strongly disagree that it anywhere near doubles costs. Ultimately you're buying hardware X and it's going to cost whatever it costs. So what more do you really need to do to support IPv6?
<span style="color:#1F497D">></span>Well, let's say you're using OSPF. This means you'll also need to use OSPFv3, but that's not hard because your OSPFv3 configs are going to basically mirror your OSPF configs. You'll need to
<span style="color:#1F497D">></span>run IPv6 over iBGP, perhaps, and over eBGP to your peers and transits, but that's just another set of addresses bound to interfaces, sessions that mirror the IPv4 ones, and policy rules/filters. If
<span style="color:#1F497D">></span>you're doing super heavy TE, then the filter configs might take some effort, but if we're talking about smaller shops, doing heavy TE is unlikely. At that point, you just add a v6 address to your
<span style="color:#1F497D">>l</span>ayer3 interfaces and you're good to go for the network side. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">></span>Most of the time you spend configuring things won't be v4 or v6 specific, and the v4 specific configurations can be copy/pasted with a quick string swap to support v6 in a lot of cases. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div></blockquote></body></html>