<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>On 2019-07-22 6:09 PM, Owen DeLong wrote:<br class="">
</p>
<blockquote type="cite"
cite="mid:D2081E51-4DC7-453A-A743-817C1DEFBF4E@delong.com">
<div>
<blockquote type="cite" class="">
<div class="">On Jul 22, 2019, at 12:15 , Naslund, Steve <<a
href="mailto:SNaslund@medline.com" class=""
moz-do-not-send="true">SNaslund@medline.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="WordSection1" style="page: WordSection1;
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;">
<div style="margin: 0in 0in 0.0001pt; font-size: 12pt;
font-family: "Times New Roman", serif;"
class=""><span style="font-size: 11pt; font-family:
Calibri, sans-serif; color: rgb(31, 73, 125);"
class="">I think the Class E block has been covered
before. There were two reasons to not re-allocate it.<o:p
class=""></o:p></span></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 12pt;
font-family: "Times New Roman", serif;"
class=""><span style="font-size: 11pt; font-family:
Calibri, sans-serif; color: rgb(31, 73, 125);"
class=""><o:p class=""> </o:p></span></div>
<div style="margin: 0in 0in 0.0001pt 0.5in; font-size:
12pt; font-family: "Times New Roman", serif;
text-indent: -0.25in;" class=""><span style="font-size:
11pt; font-family: Calibri, sans-serif; color: rgb(31,
73, 125);" class=""><span class="">1.<span
style="font-style: normal; font-variant-caps:
normal; font-weight: normal; font-stretch: normal;
font-size: 7pt; line-height: normal; font-family:
"Times New Roman";" class=""> <span
class="Apple-converted-space"> </span></span></span></span><span
style="font-size: 11pt; font-family: Calibri,
sans-serif; color: rgb(31, 73, 125);" class="">A lot
of existing code base does not know how to handle
those addresses and may refuse to route them or will
otherwise mishandle them.<o:p class=""></o:p></span></div>
<div style="margin: 0in 0in 0.0001pt 0.5in; font-size:
12pt; font-family: "Times New Roman", serif;
text-indent: -0.25in;" class=""><span style="font-size:
11pt; font-family: Calibri, sans-serif; color: rgb(31,
73, 125);" class=""><span class="">2.<span
style="font-style: normal; font-variant-caps:
normal; font-weight: normal; font-stretch: normal;
font-size: 7pt; line-height: normal; font-family:
"Times New Roman";" class=""> <span
class="Apple-converted-space"> </span></span></span></span><span
style="font-size: 11pt; font-family: Calibri,
sans-serif; color: rgb(31, 73, 125);" class="">It was
decided that squeezing every bit of space out of the
v4 allocations only served to delay the desired v6
deployment.</span></div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div><br class="">
</div>
Close, but there is a subtle error…</div>
<div><br class="">
</div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span>2.<span class="Apple-tab-span" style="white-space:pre"> </span>It
was decided that the effort to modify each and every IP stack in
order to facilitate use of this relatively small block (16 /8s
being evaluated against a global</div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span>run
rate at the time of roughly 2.5 /8s per month, mostly to RIPE
and APNIC) vs. putting that same effort into modifying each and
every IP stack to support</div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span>IPv6
was an equation of very small benefit for slightly smaller cost.
(Less than 8 additional months of IPv4 free pool vs. hopefully
making IPv6 deployable</div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span>before
IPv4 ran out).</div>
</blockquote>
<p>All of this, plus what Fred Baker said upthread. <br>
</p>
<p>When I was running the IANA in the early 2000's we discussed this
issue with many different experts, hardware company reps, etc. Not
only was there a software issue that was insurmountable for all
practical purposes (pretty much every TCP/IP stack has "Class E
space is not unicast" built in), in the case of basically all
network hardware, this limitation is also in the silicon. So even
if it were possible to fix the software issue, it would not be
possible to fix the hardware issue without replacing pretty much
all the hardware. <br>
</p>
<p>... and even if some magical forces appeared and gave every open
source software project, and every company, and every consumer in
the developed world the means and opportunity to do all of the
above; doing so would have left the developing world out in the
cold, since in many cases there is reliance on older,
second/third/fourth hand equipment that they could never afford to
replace. <br>
</p>
<p>So the decision was made to start tooting the IPv4 runout horns
in the hopes that folks would start taking conservation of the
space seriously (which happened more often than not), and
accelerate the adoption of IPv6. *cough* <br>
</p>
<p>Personally, I also pushed to bring IPv6 support from ICANN up to
par, including going the last mile on putting the IPv6 addresses
of the root servers in the zone, creating and socializing a
long-term plan for allocating to the RIRs, etc. <br>
</p>
<p>So no, there were exactly zero "IPv6 loons" involved in this
decision. <span class="moz-smiley-s1"><span>:-)</span></span><br>
</p>
<p>Doug</p>
<p><br>
</p>
</body>
</html>