IPv6 multicast routing
Configure PIM-SM and SSM for IPv6 (RFC 7761, RFC 4607). Use embedded-RP and unicast-prefix-based IPv6 multicast addresses (RFC 3956, RFC 3306). Troubleshoot IPv6 multicast delivery, including MLD (RFC 4604).
Take the quiz · pass mark 70% · 9 questions
Explanation
IPv6 multicast reuses the ND/MLD machinery from Level 1 but adds routing so a multicast stream crosses routers to every interested receiver.
PIM-SM and SSM
PIM-SM (RFC 7761) is protocol-independent multicast, sparse mode: receivers join a shared tree rooted at a Rendezvous Point (RP), and the network switches to a source tree for efficiency. It is the general-purpose model for Any-Source Multicast (ASM), where receivers ask for a group (*,G) without naming the source.
SSM (Source-Specific Multicast, RFC 4607) is simpler and more secure: the receiver names both the source and the group (S,G), so there is no RP and no shared tree — the router builds a source tree straight to that one source. SSM is the preferred model for one-to-many streaming (IPTV, market data) and avoids the RP complexity entirely. For IPv6, SSM uses the FF3x::/32 multicast range (global scope ff3e::/32).
Receiver signalling: MLD (RFC 4604)
Hosts tell the router what they want with MLD (Multicast Listener Discovery). MLDv2 (with RFC 4604) adds source filtering, which is what SSM needs — a host can say "I want group G from source S" (include) or "except S" (exclude). Without MLDv2 you cannot do SSM. Troubleshooting multicast almost always starts with "did the MLD report reach the router and build the right state?".
Addressing: embedded-RP and unicast-prefix-based (RFC 3956, RFC 3306)
Two IPv6-specific address tricks remove manual RP configuration and global coordination:
- Unicast-prefix-based multicast addresses (RFC 3306) derive a multicast group from a unit's unicast prefix, so an operator can allocate globally unique multicast groups without a central registry — the group is tied to a prefix the operator already owns.
- Embedded-RP (RFC 3956) encodes the RP's address inside the multicast group address. Any router can extract the RP from the group, so ASM works across domains without configuring the RP everywhere — a big operational win unique to IPv6.
ictNetworks scenario
ictNetworks delivers its IPTV-style streams with SSM (ff3e::/32, MLDv2 source filtering) so there is no RP to run, and uses embedded-RP (RFC 3956) only for the few ASM applications that need it, with unicast-prefix-based groups (RFC 3306) derived from its documentation prefix so group allocation needs no registry. Its troubleshooting runbook starts at MLD state on the last-hop router and walks the tree toward the source.
Drawing diagram…
Worked examples
Example 1: The IPv6 SSM range
IPv6 Source-Specific Multicast uses the FF3x::/32 range; the global-scope SSM block is ff3e::/32 (RFC 4607 / RFC 3306). Group addresses for SSM streams come from here.
Example 2: Sources in an SSM channel
An SSM channel is identified by (S,G) and has exactly 1 source by definition, which is why SSM needs no RP and no shared tree — the receiver already knows the source.
Example 3: Mapping to the Ethernet MAC
An IPv6 multicast address maps to an Ethernet multicast MAC by copying its 32 low-order bits after the 33:33 prefix, so delivery on a link still works the same way as the ND multicast of Level 1.
Lab
Goal: Stream SSM multicast across three routers.
You need: a containerlab topology with FRR (pim6d) on three routers, a source and receivers. (IPv6 PIM/pim6d maturity varies by FRR version — check what your version supports before relying on a feature; a vendor NOS image is an alternative.)
- Enable IPv6 multicast routing and MLDv2 on the last-hop router.
- Configure SSM (ff3e::/32 range); start a source and have a receiver send an MLDv2 include (S,G) report.
- Confirm the routers build (S,G) state and the stream is delivered along the source tree.
- Break it deliberately (wrong source, MLDv1 only, or a filtered path) and troubleshoot from MLD state toward the source.
- (Optional) Configure an ASM group with embedded-RP (RFC 3956) and show the RP extracted from the group address.
What to submit: the pim6d/MLD configuration, evidence of (S,G) state and delivery, the troubleshooting walk-through, and (if done) the embedded-RP demonstration.
Summary
- PIM-SM (RFC 7761) serves Any-Source Multicast via an RP; SSM (RFC 4607) serves one-to-many with (S,G), no RP.
- SSM needs MLDv2 source filtering (RFC 4604); IPv6 SSM uses FF3x::/32 (global ff3e::/32).
- Embedded-RP (RFC 3956) and unicast-prefix-based groups (RFC 3306) remove manual RP config and central group allocation.
- Troubleshoot from MLD state on the last-hop router toward the source.
- Next lesson (L8.03): IPv6 for IoT and constrained networks.
Quiz imported · 9 questions · pass mark 70%. Lab questions are not auto-marked.