Use of PIM Address List Hello across address families
draft-ietf-pim-ipv4-prefix-over-ipv6-nh-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Ashutosh Gupta , Stig Venaas | ||
| Last updated | 2018-04-30 (Latest revision 2017-10-27) | ||
| Replaces | draft-pim-with-ipv4-prefix-over-ipv6-nh | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
In the PIM Sparse Mode standard there is an Address List Hello option used to list secondary addresses of an interface. Usually the addresses would be of the same address family as the primary address. In this document we provide a use case for listing secondary addresses that are from a different family. In particular, 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). When using this combined with PIM, the Address List Hello option can be used to determine which PIM neighbor to use as RPF neighbor.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)