Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!uw-beaver!fluke!jeff
From: jeff@tc.fluke.COM (Jeff Stearns)
Newsgroups: comp.protocols.appletalk
Subject: Re: BSD-TCP/Appletalk ?
Keywords: appletalk protocol TCP BSD
Message-ID: <7579@fluke.COM>
Date: 5 Apr 89 23:26:46 GMT
References: <29020@bu-cs.BU.EDU> <1852@umbc3.UMBC.EDU>
Sender: news@tc.fluke.COM
Organization: John Fluke Mfg. Co., Inc., Everett, WA
Lines: 30

In article <1852@umbc3.UMBC.EDU> alex@otter.UMBC.EDU (Alex Crain) writes:
>
>	I'm currently working on porting the Berkeley socket code (now public
>domain) to a system 5 box (At&t 3b1) and I'm considering using appletalk for
>the serial line protocol rather then SLIP. ...
>
>Alex Crain
>Systems Programmer			alex@umbc3.umbc.edu
>Univ Md Baltimore County		umbc3.umbc.edu!nerwin!alex

You might want to think about using the Asynchronous AppleTalk protocol.

It's used by the Async AppleTalk driver from Dartmouth.
I suspect that it's spoken by several commercial products as well.

The protocol is quite simple; it just wraps a DDP packet between two framing
characters.  A 16-bit checksum is included, raising the total overhead to
4 bytes.  Framing characters appearing inside DDP packets are escaped; this
adds slightly to the overall packet length.

Richard Brown at Dartmouth College is probably the best contact:
	Rich Brown
	richard.e.brown@dartmouth.edu
	603-646-3648
-- 
    Jeff Stearns        John Fluke Mfg. Co, Inc.               (206) 356-5064
    jeff@tc.fluke.COM   {uw-beaver,microsoft,sun}!fluke!jeff
						  
PS - Calling all users of the Vitalink TransLAN IV Ethernet bridge! Please
     drop me a line.