Paper Review: A Reliable Multicast Framework for Light-weight Sessions and Application Level Framing

From: Robert Danek <rdanek_at_sympatico.ca>
Date: Mon, 30 Oct 2006 23:19:27 -0500

Paper: A Reliable Multicast Framework for Light-weight Sessions and Application Level Framing

Name: Robert Danek
Course: CS2209, Fall '06

        Multicast transmission involves sending a packet to a set of nodes
that all belong to the same "group". One way to implement this is by
having a sender unicast a packet to each member of the group. This,
however, is inefficient, since it may involve sending the same packet
multiple times over links that are near to the sender. The paper, "A
Reliable Multicast Framework for Light-weight Sessions and Application
Level Framing", introduces a more efficient approach, called Scalable
Reliable Multicast (SRM).

        SRM recognizes that a "one size fits all" approach is not one that
should be taken when designing a multicast protocol. Rather, it uses
the ideas put forward by the Application Level Framing (ALF) protocol
model, which leaves a large chunk of functionality that is to be
implemented to the application itself. There are, however, parts of the
SRM framework that are common to all applications that require reliable
multicast, such as scaling considerations and loss recovery.

        The paper goes on to examine the different parts of the SRM framework.
One aspect of SRM is its session messages. These messages are used for
reporting the sequence number state of active resources, for
determining the current members of the session, and for estimating the
one-way distance between nodes. In order to prevent explosion of state
information reported in session messages, the state space is
partitioned into pages. Each member of the multicast group only reports
state information for the page that it is currently viewing.

        Another important aspect of SRM is how loss recovery is done. In SRM,
receivers are responsible for detecting loss by noticing gaps in
sequence space, and requesting retransmission. After a loss is detected
by a receiver, the receiver starts a repair timer that waits a random amount
of time before sending the repair request. When other members of the
group see the request for repair, if they had also detected the loss,
they exponentially back off their timer and reset it. In this way, if
multiple members of the group detect loss, the network will not be
flooded with repair requests.

        The paper explores the repair algorithms in detail for a number of
simple topologies, including chains, stars, and bounded-degree trees.
Simulations of the repair algorithms are also performed on the random
and bounded-degree tree topologies. By exploring these topologies, the
authors illustrate that the performance of the loss recovery algorithms
is heavily dependent on the underlying network topology.

        The authors also propose an adaptive loss recovery algorithm that
involves adjusting the repair timer parameters. The parameters are
adjusted based on past behaviour of the recovery algorithms.

        Overall, this was a good paper. It was exhaustive in its exploration
of the different aspects of the loss recovery mechanism. In addition to
what has already been mentioned, the authors also examined the problem
of loss recovery from a local perspective -- that is, the case where
losses are confined to a limited area of the network topology. Beyond
this, there did not appear to be any other angle from which the authors
could have explored the loss recovery mechanism.
Received on Mon Oct 30 2006 - 23:19:17 EST

This archive was generated by hypermail 2.2.0 : Tue Oct 31 2006 - 01:26:37 EST