D-Link DGS-3308FG Product Manual - Page 57

Reverse Path Broadcasting RPB, Truncated Reverse Path Broadcasting TRPB, Reverse Path Multicasting

Page 57 highlights

8-port Gigabit Ethernet Switch User's Guide Reverse Path Broadcasting (RPB) The RPB algorithm is a modification of the spanning tree algorithm. Instead of building a network-wide spanning tree, a virtual spanning tree is constructed for each multicast source. When a router receives a multicast packet from a source, the router will check to see if the link on which the packet was received is the shortest path to the source. If it is, the packet is forwarded to all ports except the one on which it was received. If it is not, the packet is dropped. If a link-state routing protocol is in use (such as OSPF), the router can determine if it is on the shortest path between itself and a neighboring router. If it is not, then the packet would be discarded at the next router. A link-state routing protocol would provide this information, so the first router could discard the packet. If a distance-vector routing protocol (such as RIP) is being used, the neighboring router can advertise its previous hop for the source as part of its routing table update messages or it can 'poision-reverse' the route. RPB does not use multicast membership information in the construction of multicast distribution trees. Truncated Reverse Path Broadcasting (TRPB) The TRPB algorithm is a modification of the RPB algorithm. It uses IGMP to determine if members of a multicast group are present on the router's subnetwork. If the subnetwork has no multicast members and it is a leaf router (the only router on the subnetwork), TRPB will truncate the distribution tree. If the router is not a leaf router, the tree is not changed. TRPB does use multicast group membership information in the construction of distribution trees. Reverse Path Multicasting (RPM) The RPM algorithm is an enhancement of the RPB and TRPB algorithms. RPM constructs delivery trees that span only subnetworks with group members or subnetworks along the shortest path to routers attached to subnetworks that have group members. The RPM tree is then 'pruned' so that multicast packets are forwarded only along paths that lead to group members. The first multicast packet received by the router is forwarded according to the RPB algorithm. Leaf routers that receive a multicast packet for which they have no group members will send a 'prune' message back to the router from which the message was received. Prune messages indicate that multicast packets for a given membership group should not be forwarded on the link as there are no group members. Prune messages have a TTL of one, so they are only sent back one hop from the router that sends them. The router one hop closer to the multicast source records the prune information in its memory. If the closer router has no group members on its subnetwork, it will send its own prune message to the next router on the path back to the multicast source, and so on. This is continued until multicast packets from a given source are only forwarded on paths that lead to multicast group members for that source. The group membership and the topology of the network and the multicast distribution trees can change dynamically. To accommodate this, the RPM algorithm periodically removes all the prune information from the router's memory. The next multicast packet received by the router gives new multicast group members on its subnet a chance to join the multicast group and leaf routers with new members on their subnetworks also get a chance to join. RPM requires a relatively large amount of router memory space to maintain all the information for the multicast source and group members. 47

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237

8-port Gigabit Ethernet Switch User’s Guide
47
Reverse Path Broadcasting (RPB)
The RPB algorithm is a modification of the spanning tree algorithm. Instead of building a network-wide spanning tree, a
virtual spanning tree is constructed for each multicast source.
When a router receives a multicast packet from a source, the router will check to see if the link on which the packet was
received is the shortest path to the source. If it is, the packet is forwarded to all ports except the one on which it was
received. If it is not, the packet is dropped.
If a link-state routing protocol is in use (such as OSPF), the router can determine if it is on the shortest path between itself
and a neighboring router. If it is not, then the packet would be discarded at the next router. A link-state routing protocol
would provide this information, so the first router could discard the packet.
If a distance-vector routing protocol (such as RIP) is being used, the neighboring router can advertise its previous hop for
the source as part of its routing table update messages or it can ‘poision-reverse’ the route.
RPB does not use multicast membership information in the construction of multicast distribution trees.
Truncated Reverse Path Broadcasting (TRPB)
The TRPB algorithm is a modification of the RPB algorithm. It uses IGMP to determine if members of a multicast group
are present on the router’s subnetwork. If the subnetwork has no multicast members and it is a leaf router (the only router
on the subnetwork), TRPB will truncate the distribution tree. If the router is not a leaf router, the tree is not changed.
TRPB does use multicast group membership information in the construction of distribution trees.
Reverse Path Multicasting (RPM)
The RPM algorithm is an enhancement of the RPB and TRPB algorithms. RPM constructs delivery trees that span only
subnetworks with group members or subnetworks along the shortest path to routers attached to subnetworks that have
group members.
The RPM tree is then ‘pruned’ so that multicast packets are forwarded only along paths that lead to group members.
The first multicast packet received by the router is forwarded according to the RPB algorithm. Leaf routers that receive a
multicast packet for which they have no group members will send a ‘prune’ message back to the router from which the
message was received.
Prune messages indicate that multicast packets for a given membership group should not be forwarded on the link as
there are no group members. Prune messages have a TTL of one, so they are only sent back one hop from the router that
sends them.
The router one hop closer to the multicast source records the prune information in its memory. If the closer router has no
group members on its subnetwork, it will send its own prune message to the next router on the path back to the multicast
source, and so on. This is continued until multicast packets from a given source are only forwarded on paths that lead to
multicast group members for that source.
The group membership and the topology of the network and the multicast distribution trees can change dynamically. To
accommodate this, the RPM algorithm periodically removes all the prune information from the router’s memory. The next
multicast packet received by the router gives new multicast group members on its subnet a chance to join the multicast
group and leaf routers with new members on their subnetworks also get a chance to join.
RPM requires a relatively large amount of router memory space to maintain all the information for the multicast source
and group members.