<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Forcing new networks to go to their Tier1 providers was more important. It finally tried to make addresses location-dependent and route-independent. Before this, IP addresses weren’t really addresses. As you say, they were network names.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 13, 2019, at 15:09, Andrew G. Malis <<a href="mailto:agmalis@gmail.com" class="">agmalis@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class="">Dave,<div class=""><br class=""></div><div class="">NAT/private address spaces was as important as CIDR to allow the Internet to keep growing. </div><div class=""><br class=""></div><div class="">CIDR came first. By mid-to-late 1992, it was clear that we were running out of class A and B network numbers. The resulting CIDR work progressed quite rapidly, and the RFCs were published in September 93.</div><div class=""><br class=""></div><div class="">CIDR allowed the allocation of lots of new more appropriately sized network numbers. But that only exacerbated another problem, the explosion of the global routing table size, which was putting a real strain on the backbone routers' memory table size and routing processing capacity.</div><div class=""><br class=""></div><div class="">That lead to RFC 1597 in March of 1994, which defined class A, B, and C private address spaces - our now familiar net 10, 192.168.X, and so on (it was later updated and replaced by the more famous RFC 1918). That was quickly followed by NAT (RFC 1631), published that following May.<br class=""></div><div class=""><br class=""></div><div class="">The combination of CIDR, private address spaces, and NAT took a lot of pressure off of the IPv4 address space exhaustion and routing table growth problems.</div><div class=""><br class=""></div><div class="">And the rest, as they say, is history.</div><div class=""><br class=""></div><div class="">Cheers,<br class=""></div><div class="">Andy</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 13, 2019 at 2:17 PM Dave Taht <<a href="mailto:dave@taht.net" class="">dave@taht.net</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br class="">
The 0.0.0.0 thread has been fascinating and I now have more to read<br class="">
than I ever imagined I would. Moving sideways...<br class="">
<br class="">
So, it seems obvious that address size problems plagued the arpanet<br class="">
and earlier versions of IP. When did the writing show up on the wall<br class="">
that the classful design wasn't working, and secondly that 32 bits<br class="">
wasn't enough?<br class="">
<br class="">
As near as I can tell, this netnews exchange<br class="">
<br class="">
<a href="https://web.archive.org/web/20030718205943/http://www-mice.cs.ucl.ac.uk:80/multimedia/misc/tcp_ip/8813.mm.www/0178.html" rel="noreferrer" target="_blank" class="">https://web.archive.org/web/20030718205943/http://www-mice.cs.ucl.ac.uk:80/multimedia/misc/tcp_ip/8813.mm.www/0178.html</a><br class="">
<br class="">
ultimately resulted in CIDR and the next message, kicked off IPv6 - for<br class="">
the toasters!<br class="">
<br class="">
<a href="https://web.archive.org/web/20030913113707/http://www-mice.cs.ucl.ac.uk/multimedia/misc/tcp_ip/8813.mm.www/0237.html" rel="noreferrer" target="_blank" class="">https://web.archive.org/web/20030913113707/http://www-mice.cs.ucl.ac.uk/multimedia/misc/tcp_ip/8813.mm.www/0237.html</a><br class="">
<br class="">
Somewhere also in this fascinating month of internet history (morris<br class="">
worm days) someone suggested starting to use the class-e space, with no<br class="">
replies.... Were there proposals to use this as an extension of some sort?<br class="">
<br class="">
Anyway it seems to me (in retrospect) that everybody *knew* 32 bits<br class="">
wasn't enough even going back as far as 1981 (loved hearing about how<br class="">
tcp went from v2 to v4) ?) but it didn't become<br class="">
recognized as a serious problem til about this era. ?<br class="">
<br class="">
><br class="">
> I personally (in my current naive state of mind) would like to see <br class="">
> daemons daemons source traffic from any of the other 65,535 ports <br class="">
> excluding than the destination port as a possible source port.<br class="">
<br class="">
IANA suggests a smaller ephemeral port range than what linux uses.<br class="">
<a href="https://en.wikipedia.org/wiki/Ephemeral_port" rel="noreferrer" target="_blank" class="">https://en.wikipedia.org/wiki/Ephemeral_port</a><br class="">
<br class="">
Given the profusion of NAT-like nasty things like CGNs and DS-lite and<br class="">
the rise of QUIC I would favor extending the ephemeral port range as far<br class="">
as possible. <br class="">
<br class="">
><br class="">
> Aside: Why is port 0 special? }:-)<br class="">
_______<br class="">
internet-history mailing list<br class="">
<a href="mailto:internet-history@postel.org" target="_blank" class="">internet-history@postel.org</a><br class="">
<a href="http://mailman.postel.org/mailman/listinfo/internet-history" rel="noreferrer" target="_blank" class="">http://mailman.postel.org/mailman/listinfo/internet-history</a><br class="">
Contact <a href="mailto:list-owner@postel.org" target="_blank" class="">list-owner@postel.org</a> for assistance.<br class="">
</blockquote></div>
_______<br class="">internet-history mailing list<br class=""><a href="mailto:internet-history@postel.org" class="">internet-history@postel.org</a><br class="">http://mailman.postel.org/mailman/listinfo/internet-history<br class="">Contact list-owner@postel.org for assistance.<br class=""></div></blockquote></div><br class=""></body></html>