Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!ucbcad!ucbvax!CITI.UMICH.EDU!tom
From: tom@CITI.UMICH.EDU.UUCP
Newsgroups: comp.protocols.appletalk
Subject: Re: KIP code and Ultrix
Message-ID: <8711122327.AA07901@ucbvax.Berkeley.EDU>
Date: Thu, 12-Nov-87 09:03:00 EST
Article-I.D.: ucbvax.8711122327.AA07901
Posted: Thu Nov 12 09:03:00 1987
Date-Received: Sat, 14-Nov-87 14:53:29 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 17

>If the K-box can't handle 576 byte packets or do fragmentation and reassembly,
>then it violates RFC-1009, which specifes IP gateway behavior.
>Or is it the Mac TCP/IP implementations that can't do reassembly?

CITI played with putting IP fragmentation into Stanford's KIP code but
found out that the Kineticts gateway was unable to receive more that
two (if even that) back to back packets from a sun so we droped the
work.  (If fragmentation ever looks feasable we will give it another
try.) Because the Kinetics box can't fragment, our TCP/IP
implementation has never had to do reassembly (we do do fragmentation
however).  We just added Ethernet support to our new version of MacIP
and will soon be adding reassembly as well.

Tom Unger
tom@citi.umich.edu
Center for Information and Technology Integration
The University of Michigan