Multicast Source Routing over IPv6
bofreq-liu-multicast-source-routing-over-ipv6msr6-06
Document | Type | Proposed BOF request Snapshot | |
---|---|---|---|
Title | Multicast Source Routing over IPv6 | ||
Last updated | 2022-01-18 | ||
State | Proposed | ||
Editor | Yisong Liu | ||
Responsible leadership | |||
Send notices to | (None) |
Name: Multicast Source Routing over IPv6 (MSR6)
Description
Now that IPv6 deployment is at last growing rapidly, operators need to add IPv6 multicast support to the core unicast mechanisms. Existing approaches offer partial solutions, but there is an opportunity for a source routing based new multicast architecture can be developed that is designed to address the two most important potential multicast scenarios in IPv6 networks:
• For massive multicast streaming scenarios (e.g., OTT live streaming), the main requirement is to avoid per-multicast flow status maintenance in the intermediate network device, in order to increase scalability and transport as many services as possible;
• For sparse multicast explicit path scenarios (e.g., Audio/Video Conferencing), the main requirement is to dynamically build the multicast tree and provide path optimization to satisfy the SLA.
The existing technologies can’t satisfy the above requirements:
1. The BIER architecture which is defined in RFC8279 and the Layer 2.5 BIER encapsulation defined in RFC8296 (both worked on in the BIER WG) are not native to IPv6.
2. Existing IP multicast protocols (PIM, IGMP, MLD) worked on in the PIM WG request per-tree status maintenance.
3. Point-to-multipoint Segment Routing (SR P2MP) defined in the PIM WG also requests per-tree status.
MSR6 provides source routing multicast based on native IPv6 (IPv6 and IPv6 extension headers), including Best Effort and Traffic Engineering solutions, which could satisfy the requirements of scalability and deployment simplicity for different application scenarios.
The BOF is to discuss the use case, requirements, and potential solutions for MSR6.
Required Details
- Status: WG Forming
- Responsible AD: Alvaro Retana
- BOF proponents: Yisong Liu <liuyisong@chinamobile.com>, Aijun Wang <wangaijun@tsinghua.org.cn>, Xueru Zhang <zhangxr49@chinaunicom.cn>, Huaimo Chen <huaimo.chen@futurewei.com>, Xuesong Geng <gengxuesong@huawei.com>
- Proposed BOF chairs: Weiqiang Cheng<chengweiqiang@chinamobile.com>, Mike McBride< Mike McBride <mmcbride7@gmail.com>>
- Number of people expected to attend: 100
- Length of session: 2 hours
- Conflicts (whole Areas and/or WGs): SRPING, BIER, 6MAN, PIM, Mboned
- Chair Conflicts: TBD
- Technology Overlap: Segment Routing, Multicast
- Key Participant Conflict: TBD
Agenda
1.Administration: Chairs [5 minutes]
2.MSR6 Overview/Design Consideration: Weiqiang Cheng [10 minutes]
3.MSR6 Use Case [30 minutes]
4.MSR6 BE/TE Potential Solutions [20 minutes]
5.MSR6 WG Scope Discussion [10 minutes]
6.MSR6 WG Charter Discussion [30 minutes]
7.Conclusions and next steps: Chairs and AD [5 minutes]
Links to the mailing list, draft charter if any, relevant Internet-Drafts, etc.
-
Mailing List: Not Yet
-
Draft charter:
The MSR6 WG focuses on source routing multicast based on native IPv6 (IPv6 and IPv6 extension headers), including Best Effort and Traffic Engineering solutions, which is able to decouple multicast forwarding with per flow status in intermediate nodes.
MSR6 WG will manage its specific work items by milestones agreed with the responsible Area Director.
The work-items of the MSR6 WG include functional specifications for:
o New types of MSR6 segments mapping to forwarding behavior and IPv6 Encapsulation for MSR6 Best Effort.
o New types of MSR6 segments mapping to forwarding behavior and IPv6 Encapsulation for MSR6 Traffic Engineering.
o MSR6 associated steering and signaling mechanisms.
o MSR6 Management and Security.
YANG Models and OAM could be covered in the work of next stage once the functional specifications have been completed.
-
Relevant drafts:
-
Design Considerations:
-
Proposed Solutions:
-