25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

6.7.1 PIM dense mode<br />

The PIM-DM protocol implements the RPF process described in 6.4.1, “Reverse<br />

path forwarding algorithm” on page 252. Specifically, when a PIM-DM device<br />

receives a packet, it validates the incoming interface with the existing unicast<br />

routing table. If the incoming interface reflects the best path back to the source,<br />

the router floods the multicast packet. The packet is sent out to every interface<br />

that has not been pruned from the multicast delivery tree.<br />

Unlike DVMRP, PIM-DM does not attempt to compute multicast specific routes.<br />

Rather, it assumes that the routes in the unicast routing table are symmetric.<br />

Similar to operations in a DVMRP environment, a PIM-DM device initially<br />

assumes all downstream interfaces need to receive multicast traffic. The router<br />

floods datagrams to all areas of the network. If some areas do not have receivers<br />

for the specific multicast group, PIM-DM reactively prunes these branches from<br />

the delivery tree. This reactive pruning is done because PIM-DM does not obtain<br />

downstream receiver information from the unicast routing table. Figure 6-9<br />

contains an example of a PIM-DM pruning.<br />

Figure 6-9 PIM-DM flood <strong>and</strong> prune operation<br />

PIM-DM is relatively simple to implement. The only assumption is that a router is<br />

able to retain a list of prune requests.<br />

PIM-DM benefits<br />

Given the flood <strong>and</strong> prune methodology used in PIM-DM, use this protocol in<br />

environments where the majority of hosts within a domain need to receive the<br />

multicast data. In these environments, the majority of networks will not be pruned<br />

262 <strong>TCP</strong>/<strong>IP</strong> <strong>Tutorial</strong> <strong>and</strong> <strong>Technical</strong> <strong>Overview</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!