%% You should probably cite rfc8638 instead of this I-D.
@techreport{ietf-softwire-mesh-multicast-19,
    number =    {draft-ietf-softwire-mesh-multicast-19},
    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/19/},
    author =    {Mingwei Xu and Yong Cui and Jianping Wu and Shu Yang and Chris Metz and Greg Shepherd},
    title =     {{IPv4 Multicast over an IPv6 Multicast in Softwire Mesh Network}},
    pagetotal = 19,
    year =      2017,
    month =     nov,
    day =       15,
    abstract =  {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. This document describes the mechanism for supporting multicast across a set of E-IP and I-IP networks supporting softwire mesh. The document focuses on IPv4-over-IPv6 scenario, due to lack of real- world use cases for IPv6-over-IPv4 scenario.},
}