home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.os2.networking:2104 comp.protocols.misc:833
- Path: sparky!uunet!ogicse!uwm.edu!zaphod.mps.ohio-state.edu!darwin.sura.net!ra!atkinson
- From: atkinson@itd.nrl.navy.mil (Randall Atkinson)
- Newsgroups: comp.os.os2.networking,comp.protocols.misc
- Subject: Re: Is there a "ONE TO MANY" protocol ?
- Message-ID: <BxKw1C.Ixt@ra.nrl.navy.mil>
- Date: 12 Nov 92 00:58:24 GMT
- Article-I.D.: ra.BxKw1C.Ixt
- References: <1992Nov10.093253.27111@news.tu-graz.ac.at>
- Sender: usenet@ra.nrl.navy.mil
- Organization: Naval Research Laboratory, DC
- Lines: 24
-
- In article <1992Nov10.093253.27111@news.tu-graz.ac.at> tom@piassun1.joanneum.ac.at (Tom Leitner) writes:
- >Hi,
- >
- >For our application we'd need a protocol which supports "ONE TO MANY"
- >connections (on top of Ethernet). Is there something like that ? Perhaps
- >there is a nifty trick how it can be done with IP networks.
-
- There is an IP Multicast specification in a published RFC and it has
- a fair bit of implementation experience and seems to work just fine
- both for a LAN and for a multi-continent WAN. Code to implement IP
- Multicast for BSD is available for anonymous ftp from
- gregorio.stanford.edu
-
- IP Multicast is one of the underpinnings of the thrice yearly IETF
- audio/video multicast transmissions. Coincidentally there is an IETF
- meeting next week and so a lot of us will be using IP multicast to
- tune in to DC from wherever (I believe Australia, Europe, and North
- America all tuned in last time).
-
- A less widely implemented alternative is XTP. I don't know of any
- freely distributable XTP implementation.
-
- Ran
- atkinson@itd.nrl.navy.mil
-