%% You should probably cite rfc8638 instead of this I-D. @techreport{ietf-softwire-mesh-multicast-17, number = {draft-ietf-softwire-mesh-multicast-17}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-softwire-mesh-multicast/17/}, author = {Mingwei Xu and Yong Cui and Jianping Wu and Shu Yang and Chris Metz and Greg Shepherd}, title = {{Softwire Mesh Multicast}}, pagetotal = 19, year = ** No value found for 'doc.pub_date.year' **, month = ** No value found for 'doc.pub_date' **, day = ** No value found for 'doc.pub_date.day' **, abstract = {The Internet needs to support IPv4 and IPv6 packets. Both address families and their related protocol suites support multicast of the single-source and any-source varieties. During IPv6 transition, there will be scenarios where a backbone network running one IP address family internally (referred to as internal IP or I-IP), while the attached client networks running another IP address family (referred to as external IP or E-IP). The I-IP backbone should offer both unicast and multicast transit services to the client E-IP networks. Softwire Mesh is a solution providing E-IP unicast and multicast support across an I-IP backbone. This document describes the mechanism for supporting Internet-style multicast across a set of E-IP and I-IP networks supporting softwire mesh. We focus on IPv4- over-IPv6 scenario in this document, due to lack of real-world use cases for IPv6-over-IPv4 scenario.}, }