HP 6125G HP 6125G & 6125G/XG Blade Switches IP Multicast Configuration - Page 271

How MLDv2 works, IPv6 multicast group filtering

Page 271 highlights

1. The host sends an MLD done message to all IPv6 multicast routers on the local subnet. The destination address is FF02::2. 2. After receiving the MLD done message, the querier sends a configurable number of multicast-address-specific queries to the group that the host is leaving. The destination address field and group address field of the message are both filled with the address of the IPv6 multicast group that is being queried. 3. One of the remaining members (if any on the subnet) of the group being queried should send a report within the time of the maximum response delay set in the query messages. 4. If the querier receives a report for the group within the maximum response delay time, it will maintain the memberships of the IPv6 multicast group. Otherwise, the querier will assume that no hosts on the subnet are still interested in IPv6 multicast traffic addressed to that group and will stop maintaining the memberships of the group. How MLDv2 works Compared with MLDv1, MLDv2 provides the following new features: IPv6 multicast group filtering MLDv2 has introduced IPv6 multicast source filtering modes (Include and Exclude), so that a host not only can join a designated IPv6 multicast group, but also can specify to receive or reject multicast data from designated IPv6 multicast sources. When a host joins an IPv6 multicast group, one of the following situation occurs: • If it expects IPv6 multicast data from specific IPv6 multicast sources like S1, S2, ..., it sends a report with Filter-Mode denoted as "Include Sources (S1, S2 If it does not expect IPv6 multicast data from specific IPv6 multicast sources like S1, S2, ..., it sends a report with Filter-Mode denoted as "Exclude Sources (S1, S2, ...)." As shown in Figure 73, the network comprises two IPv6 multicast sources, Source 1 (S1) and Source 2 (S2), both of which can send IPv6 multicast data to IPv6 multicast group G. Host B is interested only in the IPv6 multicast data that Source 1 sends to G but not in the data from Source 2. Figure 73 Flow paths of multicast-address-and-source-specific multicast traffic In the case of MLDv1, Host B cannot select IPv6 multicast sources when it joins IPv6 multicast group G. Therefore, IPv6 multicast streams from both Source 1 and Source 2 will flow to Host B whether it needs them or not. 260

  • 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
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379

260
1.
The host sends an MLD done message to all IPv6 multicast routers on the local subnet. The
destination address is FF02::2.
2.
After receiving the MLD done message, the querier sends a configurable number of
multicast-address-specific queries to the group that the host is leaving. The destination address field
and group address field of the message are both filled with the address of the IPv6 multicast group
that is being queried.
3.
One of the remaining members (if any on the subnet) of the group being queried should send a
report within the time of the maximum response delay set in the query messages.
4.
If the querier receives a report for the group within the maximum response delay time, it will
maintain the memberships of the IPv6 multicast group. Otherwise, the querier will assume that no
hosts on the subnet are still interested in IPv6 multicast traffic addressed to that group and will stop
maintaining the memberships of the group.
How MLDv2 works
Compared with MLDv1, MLDv2 provides the following new features:
IPv6 multicast group filtering
MLDv2 has introduced IPv6 multicast source filtering modes (Include and Exclude), so that a host not only
can join a designated IPv6 multicast group, but also can specify to receive or reject multicast data from
designated IPv6 multicast sources. When a host joins an IPv6 multicast group, one of the following
situation occurs:
If it expects IPv6 multicast data from specific IPv6 multicast sources like S1, S2, …, it sends a report
with Filter-Mode denoted as "Include Sources (S1, S2, …)."
If it does not expect IPv6 multicast data from specific IPv6 multicast sources like S1, S2, …, it sends
a report with Filter-Mode denoted as "Exclude Sources (S1, S2, …)."
As shown in
Figure 73
, the network comprises two IPv6 multicast sources, Source 1 (S1) and Source 2
(S2), both of which can send IPv6 multicast data to IPv6 multicast group G. Host B is interested only in
the IPv6 multicast data that Source 1 sends to G but not in the data from Source 2.
Figure 73
Flow paths of multicast-address-and-source-specific multicast traffic
In the case of MLDv1, Host B cannot select IPv6 multicast sources when it joins IPv6 multicast group G.
Therefore, IPv6 multicast streams from both Source 1 and Source 2 will flow to Host B whether it needs
them or not.