<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Actually John - IPng started out being called IPv7, but we caught
the mistake and renamed it IPv6. Whew :-)<br>
<br>
Geoff<br>
<br>
<br>
<div class="moz-cite-prefix">On 2/15/21 8:33 AM, John Curran wrote:<br>
</div>
<blockquote type="cite"
cite="mid:7BFAE5F2-3E15-4B54-AC90-D534DF392769@istaff.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
On 15 Feb 2021, at 2:01 AM, Mark Andrews <<a
href="mailto:marka@isc.org" class="" moz-do-not-send="true">marka@isc.org</a>>
wrote:<br class="">
<div>
<blockquote type="cite" class="">...<br
class="Apple-interchange-newline">
<div class="">
<meta charset="UTF-8" class="">
<span style="caret-color: rgb(0, 0, 0); font-family:
Helvetica; font-size: 12px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none; float: none; display: inline
!important;" class="">Complain to your vendors about not
implementing RFC 8305, RFC 6724, and</span><br
style="caret-color: rgb(0, 0, 0); font-family: Helvetica;
font-size: 12px; font-style: normal; font-variant-caps:
normal; font-weight: normal; letter-spacing: normal;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px; text-decoration: none;"
class="">
<span style="caret-color: rgb(0, 0, 0); font-family:
Helvetica; font-size: 12px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none; float: none; display: inline
!important;" class="">RFC 7078. RFC 8305 or RFC6724 + RFC
7078 would fix your issue.</span><br style="caret-color:
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px;
font-style: normal; font-variant-caps: normal;
font-weight: normal; letter-spacing: normal; text-align:
start; text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px; text-decoration: none;"
class="">
<br style="caret-color: rgb(0, 0, 0); font-family:
Helvetica; font-size: 12px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none;" class="">
<span style="caret-color: rgb(0, 0, 0); font-family:
Helvetica; font-size: 12px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none; float: none; display: inline
!important;" class="">Thats Happy Eyeballs and tuneable
address selection rules.</span></div>
</blockquote>
<br class="">
</div>
<div>Mark - </div>
<div><br class="">
</div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span>You’ve
properly pointed out IPv6 can indeed be readily & safely
deployed today using modern equipment that supports a reasonable
transition approach… full agreement there. </div>
<div><br class="">
</div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span>Interestingly
enough, you’ve also pointed out the not-so-secret reason why
it's taken so long to get sizable deployment of IPv6 – that is,
despite us knowing that we needed "a straightforward transition
plan” on day one that documented how to move from IPv4 to IPng
(aka IPv6), we opted in 1995 to select a next generation
protocol which lacked any meaningful transition plan and instead
left that nasty transition topic as an exercise for the reader
and/or addressed by postulated outputs from newly-defined
working groups… thus the underlying reason for the lost decades
of creative engineering efforts in gap-filling by those who came
after and had to actually build working networks and
applications using IPv6.</div>
<div><br class="">
</div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span>For
what it’s worth, I do think we’re finally 98 or 99% of the way
there, but it has resulted some very real costs - rampant
industry confusion, loss of standards credibility, etc. There’s
some real lessons to be had here – as one who was in the IP
Directorate at the time (and thus sharing in the blame), I know
I would have done quite a bit differently, but it’s unclear if
there’s been any systematic look-back or institutional learning
coming out of the entire experience.</div>
<div><br class="">
</div>
<div>FYI,</div>
<div>/John </div>
<div><br class="">
</div>
<div><br class="">
</div>
</blockquote>
<br>
</body>
</html>