Re: NANOG Operational TTL Alert for 160-bit Headers (aka IPv4)
On 3/3/12 3:02 PM, Guru NANOG wrote: > Common Misconception - IPv4 is Out of Address Space You couldn't wait just 29 more days to post this? It would have been so much more appropriate. -- Jay Hennigan - CCIE #7880 - Network Engineering - j...@impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV
Re: NANOG Operational TTL Alert for 160-bit Headers (aka IPv4)
Someone has been drinking the bong water Sent from my iPhone On 2012-03-03, at 5:03 PM, "Guru NANOG" wrote: > 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: SD11 > > Packets without the 11 will enter Deep Packet Inspection processing > (slow) > > SD are new Source and Destination Address bits set via the generic > 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.☺ >
Re: NANOG Operational TTL Alert for 160-bit Headers (aka IPv4)
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. -- Leigh Porter On 3 Mar 2012, at 23:27, "Robert Glover" wrote: > Someone get this man a Xanax! > > -Original message- > From: Guru NANOG > To: nanog > Sent: 2012 Mar, Sun, 4 00:01:04 GMT+00:00 > Subject: 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: SD11 > > Packets without the 11 will enter Deep Packet Inspection processing (slow) > > SD are new Source and Destination Address bits set via the generic > 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.☺ > > > __ > This email has been scanned by the Symantec Email Security.cloud service. > For more information please visit http://www.symanteccloud.com > __ __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __
Re: NANOG Operational TTL Alert for 160-bit Headers (aka IPv4)
Someone get this man a Xanax! -Original message- From: Guru NANOG To: nanog Sent: 2012 Mar, Sun, 4 00:01:04 GMT+00:00 Subject: 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: SD11 Packets without the 11 will enter Deep Packet Inspection processing (slow) SD are new Source and Destination Address bits set via the generic 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.☺
