mahboud@kinetics.UUCP (Mahboud Zabetian) (09/02/89)
From article <RICH.89Aug31093708@sendai.sendai.ann-arbor.mi.us>, by rich@sendai.sendai.ann-arbor.mi.us (K. Richard Magill): > Why is this an issue? From the IP side, this is just another packet. > > Conceptually simple. I can write it in bsd sockets or STREAMS pretty > simply. I couldn't begin to tell you how to put it into the mac side. > -- > rich. Well, we have a code module here that operates similar to the EtherTalk adev module, with the exception of spitting out DDP in UDP, on ethernet. With it, you can have Macs on an all IP network talking to eachother, CAP servers, FastPaths and GatorBoxes. Also, Macs could communicate over the internet without the need of any AppleTalk-literate gateways. There are many reasons why IPTalk needs discussion: How should Macs (or for that matter, gateways and other machines) do routing? atalkad? What to do to re-direct packets? Was the original design of KIP a valid, or good design? Could there be better ways???? Also (my main concern), it would be nice if we could have Apple support IPTalk in their MacTCP, then we could have Macs acting as IP routers. Currently IPTalk (the adev) runs on top of TCPort. So, anyone from Apple want to give us a hand in writing the RFC? -mahboud Standard Disclaimer: Don't mind me, I'm just babbling. ------------------------------------------------------------------------------ Mahboud Zabetian (415) 975-4511 mahboud@kinetics.com Kinetics/Excelan/Novell 1340 Treat Blvd, Suite 500 ...!ucbvax!mtxinu!kinetics!mahboud Walnut Creek, CA 94596 ------------------------------------------------------------------------------ Woke up in my clothes again this morning, I don't know exactly where I am.... --- Sting ------------------------------------------------------------------------------