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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

In this environment, an ASBR in the MOSPF domain is configured as an inter-AS<br />

multicast forwarder. This router is also configured with an inter-AS multicast<br />

routing protocol. Although the MOSPF st<strong>and</strong>ard does not dictate the operations<br />

of the inter-AS protocol, it does assume the protocol forwards datagrams using<br />

RPF principles. Specifically, MOSPF assumes that a multicast datagram whose<br />

source is outside the domain will enter the domain at a point that is advertising<br />

(into OSPF) the best route to the source. MOSPF uses this information to<br />

calculate the path of the datagram through the domain.<br />

MOSPF designates an inter-AS multicast forwarder as a wildcard multicast<br />

receiver. As with inter-area communications, this ensures that the receiver<br />

remains on all pruned shortest-path delivery trees. They receive all multicast<br />

datagrams, regardless of destination. Because this device has complete<br />

knowledge of all group membership outside the AS, datagrams can be forwarded<br />

to group members in other autonomous systems.<br />

6.6.4 MOSPF interoperability<br />

Routers configured to support an MOSPF network can be intermixed with<br />

non-multicast OSPF routers. Both types of routers interoperate when forwarding<br />

unicast data traffic. However, forwarding <strong>IP</strong> multicast traffic is limited to the<br />

MOSPF domain. Unlike DVMRP, MOSPF does not provide the ability to tunnel<br />

multicast traffic through non-multicast routers.<br />

6.7 Protocol Independent Multicast (PIM)<br />

The complexity associated with MOSPF lead to the development <strong>and</strong><br />

deployment of PIM. PIM is another multicast routing protocol. Unlike MOSPF,<br />

PIM is independent of any underlying unicast routing protocol. It interoperates<br />

with all existing unicast routing protocols.<br />

PIM defines two modes or operation:<br />

► Dense mode (PIM-DM), specified in RFC 3973<br />

► Sparse mode (PIM-SM), specified in RFC 2362<br />

Dense mode <strong>and</strong> sparse mode refer to the density of group members within an<br />

area. In a r<strong>and</strong>om sampling, a group is considered dense if the probability of<br />

finding at least one group member within the sample is high. This holds even if<br />

the sample size is reasonably small. A group is considered sparse if the<br />

probability of finding group members within the sample is low.<br />

PIM provides the ability to switch between spare mode <strong>and</strong> dense mode. It also<br />

permits both modes to be used within the same group.<br />

Chapter 6. <strong>IP</strong> multicast 261

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

Saved successfully!

Ooh no, something went wrong!