[arin-ppml] /6 View and /12 View of Legacy IPv4 Address Space

[IPv3.com]

It seems clear that IPv6 has missed the mark in terms of market needs.
People with
huge investments in IPv6 will likely continue to promote it.
http://www.ietf.org/mail-archive/web/ipv6/current/msg11681.html

Near-term extensions to IPv4 can help extend the life. Contrary to
people's claims, all
routers and software in the world do not have to change to extend
IPv4. Estimates
show that 80% or more of IPv4 equipment never directly touches the
global (public?)
Internet.

Making those changes with an eye to the future may be prudent. Moving
from 32-bits
to 34-bits requires 2-bits for Source & Destination. Those are easy to
mine from idle
and deprecated bits in the 160-bit header.

http://a1.twimg.com/profile_background_images/95178872/IPv4.png
via http://Twitter.com/IPv3

With 34-bit addressing the /6 "View" and the /12 "View" of the IANA
Legacy allocation
table helps to show the current state of affairs. With the /6 view
there are only 64 Rows.
With the /12 view there are 4096 Rows.
http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml

For IPv6 Hobbyists & people who want to play with 64-bit addressing
FREE 64-bit addressing using 12+18+6+24+4 can be coded using
6-bit symbols such as: LL_LLL_L_LLLL_X (Example: US_COM_L_IPV3_4)

The 12+18=30 are routed on legacy equipment. The Destination is
Flipped and 6+24=30 is routed.
This assumes /30 routing is where the legacy core reaches steady
state. Any /32 features will not
likely be tapped. That is because the +4 bits are carried un-flipped
in the right-most bits.

===================================
00 - UNIX
01 - ISOC, IETF, IRTF, IANA, ICANN, NANOG, RIRs...
10 - IEEE, ATSC, FCC, NTIA, NIST, LEOs...
11 - UN, ITU, ETSI...
===================================