v6 Avian Carriers?

I'm not sure about that, but we know that, if a Sullenberger unit has been installed, a large aircraft can survive a DoS attack perpetrated by the avian carrier.

I was thinking today would be a good day to write an RFC for "fractional
DHCP" where end-users can get issued say 1/64 of an v4 IP, say Other users on the same DSLAM, etc behind the
carrier NAT would have other shares of the same public IP. :slight_smile:

Would the end-user get both the TCP and UDP ports from their assigned range? Also, how would you handle ICMP/ESP/etc... or would those be 'free with the purchase of..."?


I'm thinking both TCP and UDP, and for ICMP don't NAT's use the sequence
number field to keep them separate ?


I'm not sure if this is an attempt at a continuation of the April Fools meme, or a serious idea, but this has kind already been thought of. :slight_smile:


It's a nice illustration that the only idea which doesn't suck post exhaustion[0], is IPv6.


[0] i.e., now.

I believe that the Sullenberger unit effected the loss of the avian carriers requiring regeneration and retransmission.

Dave Edelman

In my experience, the Avian Carriers usually eat the NATs.

James R. Cutler

Be careful what you wish for:

Not true.

The occupants of the aircraft survived. The aircraft did not.


Hm, in my recollection the payload made it to the destination. Perhaps the route was a bit unexpected though.

Random re-encapsulation. Now there's an interesting protocol!