Abstract. Many new Internet applications require data transmission from a sender to multiple receivers. Unfortunately, the IP Multicast technology used today suffers from scalability problems, especially when used for small and sparse groups. Multicast for Small Conferences aims at providing more efficient support for example to audio conferences. In this work, we present a performance study of the concept, based on simulations of real-world scenarios with the ns-2 network simulation software. The results indicate that Multicast for Small Conferences has the potential of replacing IP Multicast for many delay sensitive small group applications, even with very limited support from the network infrastructure.
Explicit MulticastIP Multicast does not scale well for (many) small groups such as in audio conferences or multi-player games. Multicast routing entries cannot be aggregated such as unicast routing entries since multicast address selection is arbitrary. Moreover, multicast routing entries do not only consist of destination addresss but may include source addresses. With many small group applications routing table sizes are increasing massively, which deteriorates the performance of (backbone) routers. Explicit Multicast [3] (Xcast, the successor of Small Group Multicast [4]) is a multicast scheme designed for supporting a very large number of multicast sessions as present in audio/video conferencing, network games or collaborative working. It differs from native multicast in that the sending node keeps track of all session members and explicitly encodes the list of destinations in a special packet header. This newly defined header introduces a new protocol between the network (IP) and the transport (UDP/TCP) layer. Xcast capable routers that receive such a packet parse the Xcast header and use the ordinary unicast routing table to determine how to route the packet to each destination, generating a packet copy for every affected outgoing interface. Each address list contains only the addresses that can be reached via that interface. If there is only one destination address for a particular next hop, the packet may be sent as a standard unicast packet. With the Xcast scheme, routers do not have to maintain per session state. This