%% You should probably cite rfc8638 instead of this I-D. @techreport{ietf-softwire-mesh-multicast-22, number = {draft-ietf-softwire-mesh-multicast-22}, 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/22/}, author = {Mingwei Xu and Yong Cui and Jianping Wu and Shu Yang and Chris Metz}, title = {{IPv4 Multicast over an IPv6 Multicast in Softwire Mesh Network}}, pagetotal = 18, year = 2018, month = jun, day = 18, abstract = {During the transition to IPv6, there will be scenarios where a backbone network internally running one IP address family (referred to as the internal IP or I-IP family), connects client networks running another IP address family (referred to as the external IP or E-IP family). In such cases, the I-IP backbone needs to offer both unicast and multicast transit services to the client E-IP networks. This document describes a mechanism for supporting multicast across backbone networks where the I-IP and E-IP protocol families differ. The document focuses on IPv4-over-IPv6 scenario, due to lack of real- world use cases for IPv6-over-IPv4 scenario.}, }