Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!netnews.engin.umich.edu!billkatt
From: billkatt@caen.engin.umich.edu (billkatt)
Newsgroups: comp.protocols.appletalk
Subject: Re: UDPTalk as a backbone
Message-ID: <1989Sep5.193002.15583@caen.engin.umich.edu>
Date: 5 Sep 89 19:30:02 GMT
References: <1989Sep3.063402.22872@caen.engin.umich.edu> <31297@ames.arc.nasa.gov> <1989Sep4.202733.6326@caen.engin.umich.edu> <1435@intercon.UUCP>
Reply-To: billkatt@caen.engin.umich.edu (billkatt)
Organization: Computer Aided Engineering Network (CAEN), University of Michigan
Lines: 28

In article <1435@intercon.UUCP> amanda@intercon.uu.net (Amanda Walker) writes:
>In article <1989Sep4.202733.6326@caen.engin.umich.edu>,
>billkatt@caen.engin.umich.edu (billkatt) writes:
>> Maybe you should research your facts.  Kinetics INVENTED UDPTalk.  The
>> original FastPaths (1's) were invented to bridge LocalTalk to UDPTalk
>> (EtherTalk didn't exist yet).
>
>Methinks the gentleman is a bit rusty on his history.  Bill Croft at Stanford
>invented AppleTalk-over-UDP.  Kinetics from the start has pushed their
>version, which started as "ELAP" and is now EtherTalk.  It is only with
>the recent release of K-STAR that they are supporting UDP encapsulation.

Yes, K*Star is newer than KIP.  Maybe I mistated what I mean, but the FastPath
was simply a hardware device to run KIP.  Sure, Kinetics supplied different
software (EtherTalk), but that's not what people ran.  If you only consider
what Kinetics sends and supports as being the use for their hardware, then
you can't include atalkad as software which is made for it.  atalkad is part
of KIP, which Kinetics doesn't supply or support, but that's what people run.
-Steve
>
>--
>Amanda Walker
>InterCon Systems Corporation
>
>amanda@intercon.uu.net    |    ...!uunet!intercon!amanda
>--
>"The trouble with doing something right the first time is that nobody
> appreciates how difficult it was"       --Walt West