[139298] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: v6 Avian Carriers?

daemon@ATHENA.MIT.EDU (Fred Heutte)
Fri Apr 1 20:47:04 2011

From: Fred Heutte <aoxomoxoa@sunlightdata.com>
To: <smb@cs.columbia.edu>
Date: Fri, 1 Apr 2011 17:46:48 -0700
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

which reminds me....

----------------

Mr. ENGINEER: (yelling and hitting the send button repeatedly)=
 'ELLO
NOC!!!!! Testing! Testing! Testing! Testing! This is your nine=
 o'clock
customer call!

(Takes RFC 791 out of the binder and thumps it on the counter.=
 Throws it up
in the air and watches it plummet to the floor.)

Mr. ENGINEER: Now that's what I call a dead protocol.

NETWORK OPERATOR FROM HELL: No, no.....No, 'e's truncated!

Mr. ENGINEER: TRUNCATED!?

NOFH: Yeah! You truncated him, just as he was bein' refactored!
Datagrams truncate easily, major.

Mr. ENGINEER: Um...now look...now look, mate, I've definitely=
 'ad
enough of this. That packet is definitely deceased, and when I=
 deployed
it not 'alf an hour ago, you assured me that its total lack of
throughput was due to it bein' tired and shagged out following a
prolonged reroute.

NOFH: Well, he's...he's, ah...probably pining for the big iron.

Mr. ENGINEER: PININ' for the BIG IRON?!?!?!? What kind of talk=
 is
that?, look, why did he fall flat on his back the moment I got=
 'im
through the router?

NOFH: The 4-byte prefers keepin' on it's back! Remarkable=
 protocol,
id'nit, squire? Lovely octets!

Mr. ENGINEER: Look, I took the liberty of examining that packet=
 when I
dispatched it, and I discovered the only reason that it had been
sitting in its queue in the first place was that it had been=
 SWAPPED
there.

(pause)

NOFH: Well, o'course it was swapped there! If I hadn't swapped=
 that
packet, it would have nuzzled up to that DMZ, bent it apart with=
 its
handshake, and VOOM! Feeweeweewee!

Mr. ENGINEER: "VOOM"?!? Mate, this packet wouldn't "voom" if you=
 put
four million hop counts on it! 'E's bleedin' demised!

NOFH: No no! 'E's pining!

Mr. ENGINEER: 'E's not pinin'! 'E's passed on! This packet is no=
 more!
He has ceased to be! 'E's expired and gone to meet 'is archive!=
 'E's a
null set! Bereft of destination, 'e rests in /dev/null! If you=
 hadn't
swapped 'im to the top of the queue 'e'd be pushing off the=
 stack! 'Is
traceroutes are now 'istory! 'E's off the wire! 'E's kicked the=
 bit
bucket, 'e's shuffled off the interwebs, run 'init 0' and joined=
 the
bleedin' choir deprecated!! THIS IS AN EX-PACKET!!


-----------------
>
>On Apr 1, 2011, at 8:41 11AM, Sachs, Marcus Hans (Marc) wrote:
>
>> I was wondering which April 1st this would happen on.   Now I=
 know.  So if a v6 carrier 
swallows a v4 datagram does that count as packet loss or=
 tunneling?
>> 
>> http://datatracker.ietf.org/doc/rfc6214/
>> 
>
>I was disappointed in this RFC -- Section 3.1 didn't include the=
 proper discussion of the 
difference between African and European avian carriers, and we=
 know what happens if that 
question is asked at the wrong time.
>> 
>
>
>=09=09--Steve Bellovin, https://www.cs.columbia.edu/~smb
>
>
>
>
>
>
>



home help back first fref pref prev next nref lref last post