Skip to content
Home » Network Layer – Rpb , Rpm , Igmp And Dvmrp Protocols? The 20 Detailed Answer

Network Layer – Rpb , Rpm , Igmp And Dvmrp Protocols? The 20 Detailed Answer

Are you looking for an answer to the topic “Network Layer – RPB , RPM , IGMP And DVMRP Protocols“? We answer all your questions at the website Chambazone.com in category: 40+ Marketing Blog Topics & Ideas. You will find the answer right below.

Keep Reading


IGMP – Internet Group Message Protocol | Network Layer Protocol | Learnaholic India

IGMP – Internet Group Message Protocol | Network Layer Protocol | Learnaholic India
IGMP – Internet Group Message Protocol | Network Layer Protocol | Learnaholic India

Images related to the topicIGMP – Internet Group Message Protocol | Network Layer Protocol | Learnaholic India

Igmp - Internet Group Message Protocol | Network Layer Protocol | Learnaholic India
Igmp – Internet Group Message Protocol | Network Layer Protocol | Learnaholic India

This post is the last in a series about protocols implemented at the network layer. In this post, we mainly focus on some remaining network layer protocols, namely H. RPB, RPM, IGMP and DVMRP protocols. So let’s start with the IGMP protocol first.

What is IGMP (Internet Group Management Protocol) ?

The IP protocol can involve two types of communication, H. Unicast and Multicast (already covered in previous posts). Unicast is communication between sender and receiver. This is one-on-one communication. However, some processes sometimes need to send the same message to a large number of recipients at the same time. This is called multicast and it is one-to-many communication. Some applications including distance learning and video-on-demand are well-known examples of multicasting. Internet Group Management Protocol (IGMP) is one of the necessary but insufficient protocols involved in multicasting. IGMP is a companion to the IP protocol.

Group Management in IGMP

For multicast on the Internet, we need routers that can route multicast packets. The routing tables of these routers need to be updated using one of the multicast routing protocols we discussed in the previous article. IGMP is not a multicast routing protocol, but it is essentially a protocol for managing group membership. Every network should have one or more multicast routers that distribute multicast packets to other hosts or other routers. The IGMP protocol primarily proves multicast routers with information about the membership status of hosts (routers) connected to the network. A multicast router can receive many different groups of multicast packets each day. If the router doesn’t know the membership of the host, it sends all these packets. This generates a lot of traffic. One solution is to keep a list of groups that have at least one loyal member on the network (router). IGMP helps multicast routers create and update this list.

IGMP Messages

IGMP has gone through two versions. IGMPv2 is the current version. IGMPv2 has three types of messages, viz. H. Inquiries, Membership Reports and Exit Reports. There are two types of query messages, general and special.

Message Format in IGMP

The following figure shows the format of an IGMP message (version 2):.

IGMP Operation

IGMP works locally. A multicast router is attached to a network and has a list of multicast addresses for groups that have at least one loyal member in that network. In each group there is a router whose task is to distribute multicast packets destined for that particular group. This basically means that when three multicast routers are connected to the network, their lists of group IDs are mutually exclusive. If the router is a member, it means that the network connection to one of its other interfaces will receive these multicast packets. We say that the host or router is interested in the group. In either case, hosts and routers maintain a list of group IDs and forward their interest to the distribution router.

Distance Vector Multicast Routing Protocol  (DVMRP)

In this section, we will discuss the multicast distance vector routing and its implementation on the Internet, DVMRP. Multicast routing doesn’t allow a router to send its routing table to its neighbors.  Multicast distance vector routing uses source-based trees, but the router never actually makes a routing table. DVMRP is another multicast routing algorithm. This is used in the MBONE routers. It is based on a combination of RIP and RPM. In this RPM , grafting and pruning are used for making source level tree. When any router receives a multicast packet, it forwards the packet as though it is consulting a routing table. We can say that the shortest path tree is evanescent. After its usage, (after a packet is forwarded) the table is destroyed. To accomplish this, the multicast distance vector algorithm uses a process based on four decision-making strategies.  Flooding is the first strategy that comes to mind. A router first receives a packet and, without even looking at the destination group address, sends it out from every interface except the one from which it was received. Flooding clearly accomplishes the first goal of multicasting i.e.  every network with active members receives the packet. This is a broadcast, not a multicast variety. DVMRP is not suitable for very large internetwork because the maximum number of hops is limited to 15  in RIP. There is one more problem i.e. it creates loops. A packet that already left the router may come back again from another interface or the same interface and be forwarded again. Some flooding protocols generally keep a copy of the packet for a while and discard any duplicates to avo loops. The next strategy is the reverse path forwarding,  which corrects this defect. Let’s understand this in a more realistic manner. Private IPv4 Addresses available for use : 10.0.0.0  to  10.255.255.255  (2 raised to 24 addresses) 172.16.0.0  to  172.31.255.255 (2 raised to 20 addresses) 192.168.0.0  to  192.168.255.255 (2 raised to 16 addresses) Any organization can use an address out of this set without taking permission from the internet authorities.  These reserved addresses are for private networks. They are unique inse the organization (like the EPBX numbers) , but they are not globally unique. So it cannot be used for internet communication . No router will forward the packet    with one of these addresses as the destination address. The site must have only one connection to the global internet through the Network Address Translation (NAT) router . The private network uses private addresses . The router that connects any network to the global address uses one private address and one global address . The private network is transparent to the rest of the internet, the rest of the internet sees only the NAT router with the address 200.20.5.2 All the outgoing packets eventually go through the NAT router , which replaces the source address in the packet with the global NAT address . All incoming packets also pass through the NAT router which replaces the destination address  (DA) in the packet with the appropriate private address. Reverse Path Forwarding (RPF) : RPF is basically a modified flooding strategy. In order to prevent loops, only one copy is forwarded and the other copies are dropped. In RPF, a router forwards only the copy that has traveled the shortest path from the source to the router. To find this specific copy, RPF uses the unicast routing table. The router receives a packet and extracts the source address (a unicast address). It consults its unicast routing table as though it wants to send a packet to the source address. The routing table tells router the next hop. If the multicast packet has just come from the hop defined in the table, the packet has traveled the shortest path from the source to the router because the shortest path is reciprocal in unicast distance vector routing protocols. If the path from A to B in the shortest, then it is also the shortest from B to A. The router forwards the packet if it has traveled from the shortest path , it discards it otherwise. This strategy prevents loops because there is always one shortest path from the source to the router. If a packet leaves the router and comes back again, it has not traveled the shortest path. The below figure shows part of a domain and a source. The shortest path tree as calculated by routers R1, R2, and R3 is shown by a thick line. When R1 receives a packet from the source through the interface m1, it consults its routing table and finds that the shortest path from R1 to the source is through interface m1. The packet is forwarded. Reverse Path Broadcasting (RPB) :  RPF guarantees that each network receives a copy of the multicast packet without the formation of loops. However, RPF does not guarantee that each network receives only one copy , a network may receive two or more copies. The reason is that RPF is not based on the destination address (a group address) , and forwarding is based on the source address. To eliminate duplication, we should define only one parent router for each network. We must have this restriction i.e. A network can receive a multicast packet from a specific source only through a designated parent router. Now we can say that for each source, the router sends the packet only out of those interfaces for which it is the designated parent. This policy is called reverse path Broadcasting (RPB). RPB further guarantees that the packet reaches every network and that every network receives only one copy. Figure below shows the difference between RPF and RPB. Now you may ask how the designated parent is determined. The designated parent router can be a router with the shortest path to the source. Because routers periodically send updating packets to each other (in RIP), they can easily determine which router in the neighborhood has the shortest path to the source (when interpreting the source as the destination). If more than one router qualifies, then the router with the smallest IP address is selected. From the above figure, Net3 receives two copies of packets even though the router sends only one copy from each interface. Thus there is a clear duplication of packets. This is mainly because of the presence of two-parent routers i.e. R2 and R4 . To eliminate this duplication, we must define only one parent router for each network. Reverse Path Multicasting (RPM) : RPB does not multicast the packet, it broadcasts it. This is not efficient. To increase the efficiency, the multicast packet must reach only those networks that have active members for that particular group. This is called reverse path multicasting (RPM). To convert the broadcasting to multicasting , the protocol uses two procedures, pruning and grafting. This is a type of multicasting technique.  For some applications such as teleconferencing, a source may want to send packets to multiple destinations (not one and not all the destinations) simultaneously. This is possible with multicast routing. In the figure, source A wants to transmit to destinations (B, C and E) with multicast group G1. Although a source can send each copy of the packet separately to each destination by using unicast routing, a more efficient method is multicasting to minimize the number of copies. The approach that is used in  multicast backbone (MBONE) network is called reverse path multicasting  (RPM) . MBONE is an overlay packet network on the internet supporting routing of IP multicast packets with D address. (MBONE is nothing but a logical tunnel between islands of isolated routers. Due to MBONE unicast routers forward the packets further. So far only DVMRP supports MBONE technique) The designated parent router of each network is responsible for holding the membership information. This is done through the IGMP protocol .  In a nutshell, we can say that RPB creates the shortest path broadcast tree source to destination . It further completely eliminated the problem of duplication of packets of data. RPF eliminates the loop in the flooding process. Finally, we have reached the end of this long post. Stay tuned for more interesting stuff of the next OSI layer. report this ad



See some more details on the topic Network Layer – RPB , RPM , IGMP And DVMRP Protocols here:

Network Layer – RPB , RPM , IGMP And DVMRP Protocols

In this post i.e Network Layer – RPB , RPM , IGMP And DVMRP Protocols , you will get complete overview of the protocols implemented in the …

+ View Here

IP Multicasting: Concepts, Algorithms, and Protocols

It describes the multicast protocol such as DVMRP, MOSPF, … In the RPB family of algorithms (RPB, TRPB, and RPM) the shortest path between …

+ Read More Here

IP Networks – Multicast Routing (MOSPF, DVMRP, CBT, PIM)

Distance Vector Multicast Routing Protocol (DVMRP); Multicast Open Shortest Path … Any host can “join” a multicast group at network layer.

+ View More Here

What is DVMRP (Distance Vector Multicast Routing Protocol)?

3. Reverse Path Multicasting (RPM) … To overcome the problem of broadcasting in RPB, Reverse Path Multicasting in used. … In this the desired multicast network …

+ View Here

Related searches to Network Layer – RPB , RPM , IGMP And DVMRP Protocols

  • network layer rpb rpm igmp and dvmrp protocols forum
  • reverse path multicasting
  • network layer rpb rpm igmp and dvmrp protocols free
  • network layer rpb rpm igmp and dvmrp protocols reddit
  • network layer rpb rpm igmp and dvmrp protocols pdf
  • network layer rpb rpm igmp and dvmrp protocols download

Information related to the topic Network Layer – RPB , RPM , IGMP And DVMRP Protocols

Here are the search results of the thread Network Layer – RPB , RPM , IGMP And DVMRP Protocols from Bing. You can read more if you want.


You have just come across an article on the topic Network Layer – RPB , RPM , IGMP And DVMRP Protocols. If you found this article useful, please share it. Thank you very much.

Leave a Reply

Your email address will not be published.