Internet Group Management Protocol

Short description: Protocol for establishing multicast group memberships on IPv4 networks

Not to be confused with ICMP.

Internet protocol suite

Application layer

* BGP
* DHCP
* DNS
* FTP
* HTTP
* HTTPS
* IMAP
* LDAP
* MGCP
* MQTT
* NNTP
* NTP
* POP
* ONC/RPC
* RTP
* RTSP
* RIP
* SIP
* SMTP
* SNMP
* SSH
* Telnet
* TLS/SSL
* XMPP
* more...

Transport layer

* TCP
* UDP
* DCCP
* SCTP
* RSVP
* QUIC
* more...

Internet layer

* IP
* IPv4
* IPv6
* ICMP
* ICMPv6
* ECN
* IGMP
* IPsec
* more...

Link layer

* ARP
* NDP
* OSPF
* Tunnels
* L2TP
* PPP
* MAC
* Ethernet
* Wi-Fi
* DSL
* ISDN
* FDDI

* more...

* v
* t
* e

The Internet Group Management Protocol (IGMP) is a communications protocol used by hosts and adjacent routers on IPv4 networks to establish multicast group memberships. IGMP is an integral part of IP multicast and allows the network to direct multicast transmissions only to hosts that have requested them.

IGMP can be used for one-to-many networking applications such as online streaming video and gaming, and allows more efficient use of resources when supporting these types of applications.

IGMP is used on IPv4 networks. Multicast management on IPv6 networks is handled by Multicast Listener Discovery (MLD) which is a part of ICMPv6 in contrast to IGMP's bare IP encapsulation.

## Contents

* 1 Architecture
* 2 Versions
* 3 Messages
* 3.1 IGMPv2 messages
* 3.2 IGMPv3 membership query
* 4 Implementations
* 5 See also
* 6 Notes
* 7 References

## Architecture

A network designed to deliver a multicast service using IGMP might use this basic architecture:

580px

IGMP operates between a host and a local multicast router. Switches featuring IGMP snooping also derive useful information by observing these IGMP transactions. Protocol Independent Multicast (PIM) is then used between the local and remote multicast routers to direct multicast traffic from hosts sending multicasts to hosts that have registered through IGMP to receive them.

IGMP operates on the network layer (layer 3), just the same as other network management protocols like ICMP.[1]

The IGMP protocol is implemented on hosts and within routers. A host requests membership to a group through its local router while a router listens for these requests and periodically sends out subscription queries. A single router per subnet is elected to perform this querying function. Some multilayer switches include an IGMP querier capability to allow their IGMP snooping features to work in the absence of an IGMP-capable router in the layer 2 network.

IGMP is vulnerable to some attacks,[2][3][4][5] and firewalls commonly allow the user to disable it if not needed.

## Versions

There are three versions of IGMP.[6] IGMPv1 was defined in 1989.REFERENCE FOR RFC1112 IS NOT DEFINED YET. You are invited to add it here. IGMPv2, defined in 1997,REFERENCE FOR RFC2236 IS NOT DEFINED YET. You are invited to add it here. improves IGMPv1 by adding the ability for a host to signal a desire to leave a multicast group.

In 2002, IGMPv3 improved IGMPv2 by supporting source-specific multicast[7] and introduces membership report aggregation.REFERENCE FOR RFC3376 IS NOT DEFINED YET. You are invited to add it here. The support for source-specific multicast was improved in 2006.REFERENCE FOR RFC4604 IS NOT DEFINED YET. You are invited to add it here.

The three versions of IGMP are backward compatible. A router supporting IGMPv3 can support clients running IGMPv1, IGMPv2, and IGMPv3. IGMPv1 uses a query-response model. Queries are sent to 224.0.0.1. Membership reports are sent to the group's multicast address. IGMPv2 accelerates the process of leaving a group and adjusts other timeouts. Leave-group messages are sent to 224.0.0.2. A group-specific query is introduced. Group-specific queries are sent to the group's multicast address. A means for routers to select an IGMP querier for the network is introduced. IGMPv3 introduces source-specific multicast capability. Membership reports are sent to 224.0.0.22.

## Messages

There are several types of IGMP messages:

General membership queries
Sent by multicast routers to determine which multicast addresses are of interest to systems attached to the network(s) they serve to refresh the group membership state for all systems on its network.
Group-specific membership queries
Used for determining the reception state for a particular multicast address.
Group-and-source-specific queries
Allow the router to determine if any systems desire reception of messages sent to a multicast group from a source address specified in a list of unicast addresses.
Membership reports
Sent by multicast receivers in response to a membership query or asynchronously when first registering for a multicast group.
Leave group messages
Sent by multicast receivers when specified multicast transmissions are no longer needed at the receiver.

IGMP messages are carried in bare IP packets with IP protocol number 2.REFERENCE FOR RFC3376 IS NOT DEFINED YET. You are invited to add it here. Similar to the Internet Control Message Protocol, there is no transport layer used with IGMP messaging.

### IGMPv2 messages

Template:APHD Template:APHD Template:APHD Template:APHD

Template:APHD

Message  | Type value

|

Membership Query  | 0x11
IGMPv1 Membership Report  | 0x12
IGMPv2 Membership Report  | 0x16
IGMPv3 Membership Report  | 0x22
Leave Group  | 0x17

Template:APHD
Template:APHD
Template:APHD
The message is sent to the following IP multicast addresses:REFERENCE FOR RFC2236 IS NOT DEFINED YET. You are invited to add it here.

Message type | Multicast address

|

General Query | All hosts (224.0.0.1)
Group-Specific Query | The group being queried
Membership Report (all IGMP versions) | The group being reported
Leave Group | All routers (224.0.0.2)

### IGMPv3 membership query

Template:APHD Template:APHD Template:APHD Template:APHD Template:APHD Template:APHD Template:APHD Template:APHD Template:APHD

Template:APHD
Template:APHD
Template:APHD
Template:APHD
Template:APHD
Template:APHD
Template:APHD
Template:APHD
Template:APHD
Template:APHD

## Implementations

FreeBSD,[note 1] Linux[note 2] and Windows all support IGMP on the host side.

## See also

* Internet Group Management Protocol with Access Control

## Notes

1. ↑ IGMPv3 was added to FreeBSD in version 8.0.
2. ↑ IGMPv3 was added in the Linux 2.5 kernel series.

## References

1. ↑ Forouzan, Behrouz A. (2012). Data Communications and Networking (5th ed.). New York, NY: McGraw-Hill. p. 658. ISBN 978-0073376226.
2. ↑ Spoofed IGMP report denial of service vulnerability.
3. ↑ "Fragmented IGMP Packet May Promote "Denial of Service" Attack". Dec 20, 2004. http://support.microsoft.com/default.aspx?scid=kb;en-us;238329&sd=tech.
4. ↑ IGMP Security Problem Statement and Requirements .
5. ↑ "Vulnerability in TCP/IP Could Allow Denial of Service (MS06-007, 913446))". February 14, 2006. http://www.microsoft.com/technet/security/Bulletin/MS06-007.mspx.
6. ↑ IP Multicast Routing Configuration Guide, Cisco, pp. 25–28, https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3750x_3560x/software/release/15-2_2_e/multicast/configuration_guide/b_mc_1522e_3750x_3560x_cg/b_mc_3750x_3560x_chapter_011.html, retrieved 2017-05-27
7. ↑ "Internet Group Management Protocol Overview". Javvin. http://www.javvin.com/protocolIGMP.html.

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Internet Group Management Protocol. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Internet_Group_Management_Protocol&oldid=4297577"
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template