%% You should probably cite draft-mishra-bess-deplment-guidlin-ipv4nlri-ipv6nh instead of this I-D.
@techreport{mishra-bess-ipv4nlri-ipv6nh-use-cases-05,
    number =    {draft-mishra-bess-ipv4nlri-ipv6nh-use-cases-05},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-mishra-bess-ipv4nlri-ipv6nh-use-cases/05/},
    author =    {Gyan Mishra and Mankamana Prasad Mishra and Jeff Tantsura},
    title =     {{IPv4 NLRI with IPv6 Next Hop Use Cases}},
    pagetotal = 16,
    year =      2020,
    month =     oct,
    day =       30,
    abstract =  {As Enterprises and Service Providers upgrade their brown field or green field MPLS/SR core to an IPv6 transport such as MPLS LDPv6, SR- MPLSv6 or SRv6, Multiprotocol BGP (MP-BGP)now plays an important role in the transition of the core from IPv4 to IPv6 being able to continue to support legacy IPv4, VPN-IPv4, and Multicast VPN IPv4 customers. This document describes the critical use case and OPEX savings of being able to leverage the MP-BGP capability exchange usage as a pure transport allowing both IPv4 and IPv6 to be carried over the same BGP TCP session. By doing so, allows for the elimination of Dual Stacking on the PE-CE connections making the peering IPv6-ONLY to now carry both IPv4 and IPv6 Network Layer Reachability Information (NLRI). This document now provides a solution for IXPs (Internet Exchange points) that are facing IPv4 address depletion at these peering points to use BGP-MP capability exchange defined in {[}RFC5549{]} to carry IPv4 (Network Layer Reachability Information) NLRI in an IPv6 next hop using the {[}RFC5565{]} softwire mesh framework.},
}