nanog mailing list archives
Re: 44/8
From: Owen DeLong <owen () delong com>
Date: Mon, 22 Jul 2019 18:09:42 -0700
On Jul 22, 2019, at 12:15 , Naslund, Steve <SNaslund () medline com> wrote: I think the Class E block has been covered before. There were two reasons to not re-allocate it. 1. 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. 2. It was decided that squeezing every bit of space out of the v4 allocations only served to delay the desired v6 deployment.
Close, but there is a subtle error… 2. 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 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 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 before IPv4 ran out). Owen
This is my recollection and might be flawed. Steven Naslund Chicago ILWhatever happened to the entire class E block? I know it's reserved for future use, but sounds like that future is now given that we've exhausted all existing >allocations.
Current thread:
- Re: Ancient history (was Re: 44/8), (continued)
- RE: 44/8 Naslund, Steve (Jul 22)
- Re: 44/8 Stephen Satchell (Jul 22)
- Re: 44/8 Owen DeLong (Jul 22)
- 240/4 (Re: 44/8) Mikael Abrahamsson (Jul 22)
- Re: 240/4 (Re: 44/8) Owen DeLong (Jul 22)
- Re: 240/4 (Re: 44/8) George Herbert (Jul 22)
- Re: 240/4 (Re: 44/8) Ross Tajvar (Jul 22)
- Re: 240/4 (Re: 44/8) Greg Skinner via NANOG (Jul 26)
- Feasibility of using Class E space for public unicast (was re: 44/8) Doug Barton (Jul 26)
- Re: Feasibility of using Class E space for public unicast (was re: 44/8) William Herrin (Jul 26)
- Re: Feasibility of using Class E space for public unicast (was re: 44/8) Doug Barton (Jul 26)
- Re: Feasibility of using Class E space for public unicast (was re: 44/8) William Herrin (Jul 26)
- Re: Feasibility of using Class E space for public unicast (was re: 44/8) Doug Barton (Jul 27)