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.

address. In this situation, multicast packets are filtered by lower-layer network<br />

interface hardware.<br />

6.1.2 Multicasting between network segments<br />

Multicast traffic is not limited to a single physical network. However, there are<br />

inherent dangers when multicasting between networks. If the environment<br />

contains multiple routers, specific precautions must be taken to ensure multicast<br />

packets do not continuously loop through the network. It is simple to create a<br />

multicast routing loop. To address this, multicast routing protocols have been<br />

developed to deliver packets while simultaneously avoiding routing loops <strong>and</strong><br />

excess transmissions.<br />

There are two requirements to multicast data across multiple networks:<br />

► Determining multicast participants: A mechanism for determining if a<br />

multicast datagram needs to be forwarded on a specific network. This<br />

mechanism is defined in RFC 3376, Internet Group Management Protocol<br />

(IGMP), Version 3.<br />

► Determining multicast scope: A mechanism for determining the scope of a<br />

transmission. Unlike unicast addresses, multicast addresses can extend<br />

through the entire Internet.<br />

The TTL field in a multicast datagram can be used to determine the scope of<br />

a transmission. Like other datagrams, each multicast datagram has a Time<br />

To Live (TTL) field. The value contained in this field is decremented at each<br />

hop. When a host or multicast router receives a datagram, packet processing<br />

depends on both the TTL value <strong>and</strong> the destination <strong>IP</strong> address:<br />

– TTL = 0: A multicast datagram received with a TTL value of zero is<br />

restricted to the source host.<br />

– TTL = 1: A multicast datagram with a TTL value of one reaches all hosts<br />

on the subnet that are members of the group. Multicast routers decrement<br />

the value to zero. However unlike unicast datagrams, no ICMP Time<br />

Exceeded error message is returned to the source host. Datagram<br />

expiration is a st<strong>and</strong>ard occurrence in multicast environments.<br />

– TTL = 2 (or more): A multicast datagram with this TTL value reaches all<br />

hosts on the subnet that are members of the group. The action performed<br />

by multicast routers depends on the specific group address:<br />

240 <strong>TCP</strong>/<strong>IP</strong> <strong>Tutorial</strong> <strong>and</strong> <strong>Technical</strong> <strong>Overview</strong><br />

224.0.0.0 - 224.0.0.255: This range of addresses is intended for<br />

single-hop multicast applications. Multicast routers will not forward<br />

datagrams with destination addresses in this range.

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

Saved successfully!

Ooh no, something went wrong!