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

VRHL+111.T1.000+Port12+30+Frag6

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

NANOG.GURU.:slight_smile:

Someone get this man a Xanax!

He has a point. The IPv4 exhaustion problem was manufactured by the illuminati to usher in their IPv6 protocol (note the use of the number 6, the number if the beast. Combined with the tuple of source, destination address and protocol type this is 666!).

The illuminati want us to deploy IPv6 so they can use it to control people ready for the new world order.

It was all predicted by Nostradamus.

Innit.

Someone has been drinking the bong water

You couldn't wait just 29 more days to post this? It would have been so
much more appropriate.

abuse@rr.com doesn't seem to think so.

-Dan

According to Whois that's a commercial roadrunner connection, and it falls in one of their netblocks.

Plenty of info here: http://bgp.he.net/ip/74.218.84.10

So anyone have a roadrunner contact with some clue?

-Dan