Multicast Source Routing over IPv6
|Document||Type||Approved BOF request|
|Title||Multicast Source Routing over IPv6|
|Responsible leadership||Alvaro Retana|
|Send notices to||(None)|
Name: Multicast Source Routing over IPv6 (MSR6)
MSR6 focuses on source routing multicast based on native IPv6 (IPv6 and IPv6 extension headers), including Best Effort and Traffic Engineering solutions, to decouple multicast forwarding from per-flow state at intermediate nodes.
There are some multicast scenarios with the following characteristics that can’t be covered well by the existing work in IETF:
1.Large network scale: in large data center deployments, for example, 10k swtiches, 100k links inside a single domain must be individually addressed. Current encodings in BIER/BIER-TE can't be used without unacceptable encapsulation expense.
2.Numerous multicast service: PIM and SR P2MP defined in PIM WG request maintaining per flow status in the intermediate nodes. For example, in PIM, each multicast flow corresponds to a multicast address, as an entry for the MFIB; in SR P2MP, replication status is allocated for replication SID to indicate replication behavior. When the multicast service is numerous, the number of replication status could overload the capability of the intermediate nodes.
3.Functionalities based on IPv6 Extension Header: for example, security is one of the fundamental requirement in SD-WAN network. IPSec Header(ESP & AH) is supposed to be reused for multicast security. There are some other multicast scenarios, for example finance carried in IPv6 network, request isolation and SLA guarantee, where IPv6 based network slicing could be used.
MSR6 provides the capability to steer and replicate a packet though a sequence of network nodes without maintaining per-flow state at intermediate nodes over native IPv6 data plane.
MSR6 use cases, requirements and potential solutions will be discussed at the BOF.
- Status: WG Forming
- Responsible AD: Alvaro Retana
- BOF proponents: Yisong Liu <firstname.lastname@example.org>, Aijun Wang <email@example.com>, Xueru Zhang <firstname.lastname@example.org>, Huaimo Chen <email@example.com>, Xuesong Geng <firstname.lastname@example.org>, Changwang Lin <email@example.com>
- Proposed BOF chairs: Suresh Krishnan (firstname.lastname@example.org)
- Number of people expected to attend: 100
- Length of session: 2 hours
- Conflicts (whole Areas and/or WGs):
- Chair Conflicts: TBD
- Technology Overlap: SRPING, BIER, 6MAN, PIM, Mboned
- Key Participant Conflict: TBD
- Administration: Chairs [10 minutes]
- MSR6 Use Cases and Requirements [30 minutes]
- MSR6 Proposed Solutions [30 minutes]
- draft-lx-msr6-rgb-segment; draft-xu-msr6-rbs; draft-geng-msr6-traffic-engineering; draft-geng-msr6-rlb-segment; draft-xl-msr6-source-segment
- MSR6 WG Proposed Charter Discussion [30 minutes]
- Conclusions and Next Steps: Chairs and AD [10 minutes]
Links to the mailing list, draft charter if any, relevant Internet-Drafts, etc.
Mailing List: email@example.com
Draft charter: https://github.com/MSR6-community/IETF-113-MSR6-BOF-Request/blob/main/BOF%20Charter%20v4.0