Please Whitelist This Site?

I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)

If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.

If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.

Thanks for your understanding!

Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide


NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.

The Book is Here... and Now On Sale!

Get The TCP/IP Guide for your own computer.
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Lower-Layer (Interface, Internet and Transport) Protocols (OSI Layers 2, 3 and 4)
      9  TCP/IP Internet Layer (OSI Network Layer) Protocols
           9  Internet Protocol (IP/IPv4, IPng/IPv6) and IP-Related Protocols (IP NAT, IPSec, Mobile IP)
                9  Internet Protocol Version 4 (IP, IPv4)

Previous Topic/Section
IP Routing In A Subnet Or Classless Addressing (CIDR) Environment
Previous Page
Pages in Current Topic/Section
1
2
Next Page
Internet Protocol Version 6 (IPv6) / IP Next Generation (IPng)
Next Topic/Section

IP Multicasting
(Page 1 of 2)

The great bulk of TCP/IP communications uses the Internet Protocol to send messages from one source device to one recipient device; this is called unicast communications. This is the type of messaging we normally use TCP/IP for; when you use the Internet you are using unicast for pretty much everything. For this reason, most of my discussion of IP has been oriented around describing unicast messaging.

IP does, however, also support the ability to have one device send a message to a set of recipients. This is called multicasting. IP multicasting has been “officially” supported since IPv4 was first defined, but has not seen widespread use over the years, due largely to lack of support for multicasting in many hardware devices. Interest in multicasting has increased in recent years, and support for multicasting was made a standard part of the next generation IP version 6 protocol. Therefore, I felt it worthwhile to provide a brief overview of IP multicasting. It's a large and very complex subject, so I will not be getting into it in detail—you'll have to look elsewhere for a full description of IP multicasting. (Sorry, it was either a brief summary or nothing; maybe I'll write more on multicasting in the future.)

The idea behind IP multicasting is to allow a device on an IP internetwork to send datagrams not to just one recipient but to an arbitrary collection of other devices. IP multicasting is modeled after the similar function used in the data link layer to allow a single hardware device to send to various members of a group. Multicasting is relatively easy at the data link layer, however, because all the devices can communicate directly. In contrast, at the network layer, we are connecting together devices that may be quite far away from each other, and must route datagrams between these different networks. This necessarily complicates multicasting when done using IP (except in the special case where we use IP multicasting only between devices on the same data link layer network.)

There are three primary functions that must be performed to implement IP multicasting: addressing, group management, and datagram processing / routing.

Multicast Addressing

Special addressing must be used for multicasting. These multicast addresses identify not single devices but rather multicast groups of devices that listen for certain datagrams sent to them. In IPv4, 1/16th of the entire address space was set aside for multicast addresses: the Class D block of the original “classful” addressing scheme.

Special techniques are used to define the meaning of addresses within this block, and to define a mapping between IP multicast and data link layer multicast addresses. This is all described in the topic on IP multicast addressing; mapping of IP multicast addresses to hardware layer multicast addresses is discussed in the section on address resolution.


Previous Topic/Section
IP Routing In A Subnet Or Classless Addressing (CIDR) Environment
Previous Page
Pages in Current Topic/Section
1
2
Next Page
Internet Protocol Version 6 (IPv6) / IP Next Generation (IPng)
Next Topic/Section

If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005

© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.