Dense Mode
Dense mode multicast is one mode that multicast can use to construct a tree for sending packets to the multicast subscribers. It is the opposite of sparse multicast.
The basic assumption behind dense mode is that the multicast packet stream has receivers at most locations. Sparse mode assumes relatively fewer receivers. Dense mode is ideal for groups where many of the nodes will subscribe to receive the multicast packets, so that most of the routers must receive and forward these packets (groups of a high density).
This difference shows up in the initial behavior and mechanisms of the two protocols. Dense Mode uses a fairly simple approach to handle IP multicast routing. The source initially broadcasts to every router directly connected to it. These neighboring routers further forward the data to their neighbors. When a router does not wish to receive this group's data (if no other neighboring PIM routers are present and no host is interested in the group), it sends a Prune message to indicate its lack of interest. Upon receiving a Prune message, the router will modify its state so that it will not forward those packets out that interface. If every interface on a router is pruned, the router will also be pruned.
In older Cisco IOS releases, PIM-DM would re-flood all the multicast traffic every 3 minutes. This is fine for low volume multicast, but not higher bandwidth multicast packet streams. More recent Cisco IOS versions support a new feature called PIM Dense Mode State Refresh, since 12.1(5)T. This feature uses a PIM state refresh messages to refresh the Prune state on outgoing interfaces. Another benefit is that topology changes are recognized more quickly. By default, the PIM state refresh messages are sent every 60 seconds.
Additionally, the routers will use reverse-path forwarding to ensure that there are no loops for packet forwarding among routers that wish to receive multicast packets. When a data packet is received on a non-RPF interface, a mechanism is required to prevent loops. If the non-RPF interface is a LAN, an Assert message is sent. Non-Forwarder routers then send a Prune on their RPF interface if they don't need the multicast stream. Only one such Prune is sent, at the time of the transition to having no interfaces in the Outgoing Interface List (OILIST). The LAN Prune receiver delays acting on it for 3 seconds, so that if another LAN router still needs the multicast stream, it can send a PIM Join message to counteract (cancel) the Prune. ("That router doesn't need it, but I still do!")
Suppose a router has Pruned, and some time later a receiver requests the multicast stream with an IGMP message. The router then sends a Graft message. In effect, "hey, I need that multicast stream over here now".
Read more about this topic: Protocol Independent Multicast
Famous quotes containing the words dense and/or mode:
“No sleep. The sultriness pervades the air
And binds the brain—a dense oppression, such
As tawny tigers feel in matted shades,
Vexing their blood and making apt for ravage.”
—Herman Melville (1819–1891)
“Yours of the 24th, asking “the best mode of obtaining a thorough knowledge of the law” is received. The mode is very simple, though laborious, and tedious. It is only to get the books, and read, and study them carefully.... Work, work, work, is the main thing.”
—Abraham Lincoln (1809–1865)