Table 4.2 Messages used in SReM
Message |
Function |
Originator |
Receiver |
JoinM |
IGMP v3 message |
Multicast receiver wants to |
A multicast-enabled Local |
LeaveM |
IGMP v3 message |
Multicast member wants to |
A multicast-enabled Local |
RqMs(type) |
Request message on behalf of new |
Local Multicast Router |
The multicast group source |
RpMs(type) |
Reply message on behalf of RqM |
The multicast group source |
The designated LMR |
eBNM |
Branching node enquiry message |
Any Branching Node |
Downstream Intermediate |
rBNM |
Branching node reply message |
Any IMR eligible to be a |
The upstream BNR that |
4.3 Membership Management
4.3.1 Dynamic Branching node-based Tree (DBT)
In SReM, the interaction between branching nodes due to multicast group member joins
and/or leaves, leads the setup of the multicast tree dynamically and gradually, rather than in
advance. Therefore, the multicast tree is referred to as a dynamic branching node-based tree
(DBT). The two types of branching node messages used to set up the DBT are enquiring
BNM (eBNM) and replying BNM (rBNM). These two messages carry information like
previous branching node address, next branching node address and new Local Multicast-
enabled Router (LMR).
The key point in setting up the DBT is that each Intermediate Multicast Router (IMR) is
aware whether it is a BNR or not. So, IMRs have three functions: -
■ Know its state as a BNR or not.
59