Log in

No account? Create an account

How to Good-Bye IPv4 Issues: If You Constrict Header 100 Times Everyday. Malarkey? or Effective Way?

« previous entry | next entry »
Mar. 4th, 2012 | 05:33 pm
mood: amusedamused

The following is a pair of emails that just appeared on the nanog list earlier today, proposing a rather... unique solution to the problem of IPv4 address exhaustion:

NANOG Operational TTL Alert for 160-bit Headers (aka IPv4)

Common Misconception - IPv4 is Out of Address Space

NANOG Operational TTL Alert for 160-bit Headers (aka IPv4)

The 8-bit TTL field is reduced to 4-bits plus two 11 bits stuck at 1 for a long time

The new 8-bit fields are: SD11TTTT

Packets without the 11 will enter Deep Packet Inspection processing (slow)

SD are new Source and Destination Address bits set via the generic AAAA 128-bit records

4+8+12+30+6 = 60 + 68 = 128


T1 sets the TTL bits - Use T0 at your own risk - VRHL=0101=5


Evil Bit and Spread Spectrum IP Addressing - NANOG Source Address Shaping

Common Misconception: One additional bit of IPv4 Addressing will solve world hunger

The Evil Bit (or spare unused bit) can be used to store (restore) one bit

The Left-Most bit of the 32-bit Source Address Field can be SET to Zero no matter what the original value. The Evil bit can be set IFF the Left-Most bit is **changed**.

Setting the Left-Most bit to zero **folds** this table in half.

Setting the Left-Most bit to ONE would move return traffic to the upper half of the Spectrum which has vast quantities of unused /8s

Wide-spread consensus shows that TWO bits can work. Three bits folds the table to 1/8th.
Governments want a 4-bit Return Prefix to their Super-Hubs for IPv6-like intercept.

The U.S.FCC is expected to issue the regulations on how Spread Spectrum Source Address Shaping will work in their licensed CPE wireless devices. There are 160-bits
in the deprecated header so there are many ways to go.

One-Way Broadcast IP Addressing is now available. The Source Address Field is used
for the second half of the 64-bit Destination Address. The DF (Did Flip) bit near the Evil
Bit is used to note the two halves of the Destination Address have been *flipped*.
NANOGers simply route 32 and then 32 after the flip based only on the Destination Field.
There is no Source Address, only a channel (port).

As another (sane) list member wryly noted, "[s]omeone has been drinking the bong water". It did make me laugh, though.

Link | Leave a comment |

Comments {1}

(Deleted comment)


(no subject)

from: schnee
date: Mar. 4th, 2012 10:53 pm (UTC)

Aye, that's exactly the problem — you'd have to update so many devices that have the assumption that these addresses are unroutable built into them[1], and doing so would take much more time than the move'd actually buy you in the end.

And yeah, I doubt I could come up with this level of craziness even if I tried. :) Some people also commented that the guy was about four weeks early; if he'd spent those four weeks working these mails into something nice and proper and coherent (if still batshit crazy), we'd have had our April Fool's RFC for this year. :)

1. Whether they ever should've been built like that is another question, but we gotta work with what we got.

Reply | Parent | Thread