%% You should probably cite rfc8638 instead of this I-D. @techreport{ietf-softwire-mesh-multicast-04, number = {draft-ietf-softwire-mesh-multicast-04}, 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/04/}, author = {Mingwei Xu and Yong Cui and Jianping Wu and Shu Yang and Chris Metz and Greg Shepherd}, title = {{Softwire Mesh Multicast}}, pagetotal = 26, year = 2013, month = jan, day = 12, abstract = {The Internet needs to support IPv4 and IPv6 packets. Both address families and their attendant protocol suites support multicast of the single-source and any-source varieties. As part of the transition to IPv6, there will be scenarios where a backbone network running one IP address family internally (referred to as internal IP or I-IP) will provide transit services to attached client networks running another IP address family (referred to as external IP or E-IP). It is expected that the I-IP backbone will offer unicast and multicast transit services to the client E-IP networks. Softwire Mesh is a solution to E-IP unicast and multicast support across an I-IP backbone. This document describes the mechanisms for supporting Internet-style multicast across a set of E-IP and I-IP networks supporting softwire mesh.}, }