%% You should probably cite draft-ietf-pim-ipv4-prefix-over-ipv6-nh instead of this I-D. @techreport{pim-with-ipv4-prefix-over-ipv6-nh-01, number = {draft-pim-with-ipv4-prefix-over-ipv6-nh-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-pim-with-ipv4-prefix-over-ipv6-nh/01/}, author = {Ashutosh Gupta and Stig Venaas}, title = {{PIM Encoding and Procedures for Unicast IPv4 prefixes with IPv6 next-hop}}, pagetotal = 5, year = 2017, month = jun, day = 30, abstract = {Multi-Protocol BGP (MP-BGP) has support for distributing next-hop information for multiple address families using one AFI/SAFI Network Layer Reachability Information (NLRI). {[}RFC5549{]} specifies the extensions necessary to allow advertising IPv4 NLRI or VPN-IPv4 NLRI with a Next Hop address that belongs to the IPv6 protocol. While the next-hop info is learnt via MP-BGP, certain procedures are needed to enable traffic forwarding. This document describes PIM extensions and the use-cases for multicast forwarding in various scenarios.}, }