PIM Encoding and Procedures for Unicast IPv4 prefixes with IPv6 next-hop
draft-pim-with-ipv4-prefix-over-ipv6-nh-01
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Ashutosh Gupta , Stig Venaas | ||
| Last updated | 2017-06-30 | ||
| Replaced by | draft-ietf-pim-ipv4-prefix-over-ipv6-nh | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-pim-ipv4-prefix-over-ipv6-nh | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-pim-with-ipv4-prefix-over-ipv6-nh-01.txt
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.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)