Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!rochester!PT.CS.CMU.EDU!IUS2.CS.CMU.EDU!ralphw
From: ralphw@IUS2.CS.CMU.EDU (Ralph Hyre)
Newsgroups: comp.protocols.appletalk
Subject: Re: KIP code and Ultrix
Message-ID: <346@PT.CS.CMU.EDU>
Date: Wed, 11-Nov-87 13:33:30 EST
Article-I.D.: PT.346
Posted: Wed Nov 11 13:33:30 1987
Date-Received: Sat, 14-Nov-87 00:06:38 EST
References: <8710301520.AA05064@lurch.ncsa.uiuc.edu>
Sender: netnews@PT.CS.CMU.EDU
Organization: Carnegie-Mellon University, CS/RI
Lines: 22

In article <8710301520.AA05064@lurch.ncsa.uiuc.edu> gaige@ncsa.uiuc.EDU writes:
>
>We have done some work with vax's here at NCSA and have found a problem
>with some of the TCP's not handling MSS directives (Maximum segment size).
>Because of the size of an appletalk packet not allowing much more than 512
>bytes per packet, any ethernet-based TCP/IP that sends a >512 byte packet
>will not get through the Kinetics box.  You might want to check with your
>vax administrator and see if might be your problem and if he/she would be
>willing to lower the MSS for the Vax to 512.

I thought this was what fragmentation was developed for.  Can't the Kinetics 
box handle it?  I believe that the default MTU for the Internet is 576 
(octets) bytes, so it seems like lots of Kboxes will have this problem.

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?
-- 
					- Ralph W. Hyre, Jr.

Internet: ralphw@ius2.cs.cmu.edu    Phone:(412)268-{2847,3275} CMU-{BUGS,DARK}
Amateur Packet Radio: N3FGW@W2XO, or c/o W3VC, CMU Radio Club, Pittsburgh, PA