06-08-2011 07:44 AM - edited 03-04-2019 12:39 PM
06-11-2011 08:37 AM
Sachin,
The IGMPv1 was the first widely used version of the protocol that allowed a station to explicitly announce its willingness to receive a particular multicast traffic. This version had two messages only: the Membership Query and a Membership Reply. The Membership Query was always sent to 224.0.0.1 by multicast routers, and the Membership Report was always sent by stations to the group that a station wanted to join. There was no message to announce that a station is leaving (unsubscribing) a multicast group, resulting in situations that a multicast stream was fed to a segment even after all stations have left the particular group. Only after a timeout period the router discovered that there are no more subscribers to the group, and stopped the multicast feed.
IGMPv2 brought a number of improvements. First, it allows the Membership Query to be both general (sent to 224.0.0.1) and group-specific (sent to a particular multicast group). The general Membership Query is used to find out all multicast groups that the stations are subscribed to. The group-specific Membership Query is used to find out if there is a subscriber for a particular group. Second, there was a new message introduced in IGMPv2 - the Leave message to advertise that a station is unsubscribing from a multicast group, allowing the router to stop an unnecessary multicast stream feed much more promptly. Third, the IGMPv2 cleared the way how a multicast querier (a router that send Queries) is elected if there are multiple multicast routers connected to a common network. In IGMPv1, all multicast routers were expected to send Queries. The IGMPv2 stipulates that only the multicast router with the lowest IP address on the segment shall become the Querier and send Queries. Other routers are free to listen to the Replies (they have to do it anyway) but they do not send Queries themselves.
Both IGMPv1 and IGMPv2 are suitable for any source multicast where a station is interested in receiving all transmissions to a multicast group, regardless of who is the sender. However, there are applications where a station wants to receive only a transmission from a particular sender to a particular group. We call this multicast the source-specific multicast. The IGMPv1/IGMPv2 does not have the capability to specify a particular sender. The extensions of the IGMP to support the source-specific multicast led to creation of the IGMPv3 that has more complex inner working than its predecessors, and its main difference is the support of source-specific multicast.
I hope this helps a bit.
Best regards,
Peter
06-11-2011 08:37 AM
Sachin,
The IGMPv1 was the first widely used version of the protocol that allowed a station to explicitly announce its willingness to receive a particular multicast traffic. This version had two messages only: the Membership Query and a Membership Reply. The Membership Query was always sent to 224.0.0.1 by multicast routers, and the Membership Report was always sent by stations to the group that a station wanted to join. There was no message to announce that a station is leaving (unsubscribing) a multicast group, resulting in situations that a multicast stream was fed to a segment even after all stations have left the particular group. Only after a timeout period the router discovered that there are no more subscribers to the group, and stopped the multicast feed.
IGMPv2 brought a number of improvements. First, it allows the Membership Query to be both general (sent to 224.0.0.1) and group-specific (sent to a particular multicast group). The general Membership Query is used to find out all multicast groups that the stations are subscribed to. The group-specific Membership Query is used to find out if there is a subscriber for a particular group. Second, there was a new message introduced in IGMPv2 - the Leave message to advertise that a station is unsubscribing from a multicast group, allowing the router to stop an unnecessary multicast stream feed much more promptly. Third, the IGMPv2 cleared the way how a multicast querier (a router that send Queries) is elected if there are multiple multicast routers connected to a common network. In IGMPv1, all multicast routers were expected to send Queries. The IGMPv2 stipulates that only the multicast router with the lowest IP address on the segment shall become the Querier and send Queries. Other routers are free to listen to the Replies (they have to do it anyway) but they do not send Queries themselves.
Both IGMPv1 and IGMPv2 are suitable for any source multicast where a station is interested in receiving all transmissions to a multicast group, regardless of who is the sender. However, there are applications where a station wants to receive only a transmission from a particular sender to a particular group. We call this multicast the source-specific multicast. The IGMPv1/IGMPv2 does not have the capability to specify a particular sender. The extensions of the IGMP to support the source-specific multicast led to creation of the IGMPv3 that has more complex inner working than its predecessors, and its main difference is the support of source-specific multicast.
I hope this helps a bit.
Best regards,
Peter
10-01-2017 04:39 PM
thanks peter for better explination
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide