09-29-2005 04:58 AM - edited 03-03-2019 10:37 AM
As far as I know almost all the applications using multicast send data over UDP.
But you could use instead TCP.
If what I'm stating is true, how does the TCP acknowledge behave in this case? Does it go back to the multicast source?
Please clarify
Thanks!
09-29-2005 05:25 AM
You can't use TCP over Mcast since TCP is session based. As you stated UDP is the protocol of choice for Mcast applications. Other non session based protocol such as IGMP, OSPF, EIGRP, RIP also use Mcast for message delivery.
Let me know if I answered your question,
09-29-2005 07:50 AM
Hi Harold,
Pls forgive my ignorance..
But could you pls explain, why we cant use a session based protocol over multicast..?
Theoretically,it is session between multicast source and each multicast client...Pls correct me if I am wrong..
Thanks in advance
Thomas.
09-29-2005 09:45 AM
Mcast is point to multipoint. A TCP session is between two host (p2p). TCP was not designed to handle p2mp.
Hope this helps,
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: