Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!ucla-cs!zen!ucbvax!UDEL.EDU!Mills
From: Mills@UDEL.EDU
Newsgroups: comp.protocols.tcp-ip
Subject: EGP updates over the top
Message-ID: <8709112213.aa23967@Huey.UDEL.EDU>
Date: Fri, 11-Sep-87 22:13:07 EDT
Article-I.D.: Huey.8709112213.aa23967
Posted: Fri Sep 11 22:13:07 1987
Date-Received: Sat, 12-Sep-87 22:33:46 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 17

Folks,

EGP jumbograms observed here have topped out above the ARPANET MTU of 1006+
octets, which means they will be fragmented. I'm sure the many Unix system
wizards will be casting spells on the reassembly buffer size and crank that
up accordingly. For the fuzzball system warlocks, be advised its EGP does
now reassemble updates. Fixes will be distributed over the weekend. The
reason I dropped this message on the full list is an interesting observation
that the LSI-11 core gateways set the don't-fragment bit on updates to
match the same bit on received packets. Thus, if your EGP code sets this bit
in the IP header, the update that comes back will self-destruct while coming
back. Obviously, the don't-fragment bit should not be set.

having flattened head while learning the above nugget today, I would like to
invite our BBN comrades to expand upon the theme.

Dave