Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Obsoletes:

RFC 5549

Authors:

S. Litkowski
S. Agrawal
K. Ananthamurthy
K. Patel

Stream:

IETF

Source:

bess (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8950

Discuss this RFC: Send questions or comments to the mailing listbess@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8950

Abstract

Multiprotocol BGP (MP-BGP) specifies that the set of usable next-hopaddress families is determined by the Address Family Identifier (AFI)and the Subsequent Address Family Identifier (SAFI). The AFI/SAFIdefinitions for the IPv4 address family only have provisions foradvertising a next-hop address that belongs to the IPv4 protocol whenadvertising IPv4 Network Layer Reachability Information (NLRI) orVPN-IPv4 NLRI.

This document specifies the extensions necessary to allow theadvertising of IPv4 NLRI or VPN-IPv4 NLRI with a next-hop addressthat belongs to the IPv6 protocol. This comprises an extension ofthe AFI/SAFI definitions to allow the address of the next hop forIPv4 NLRI or VPN-IPv4 NLRI to also belong to the IPv6 protocol, theencoding of the next hop to determine which of the protocols theaddress actually belongs to, and a BGP Capability allowing MP-BGPpeers to dynamically discover whether they can exchange IPv4 NLRI andVPN-IPv4 NLRI with an IPv6 next hop. This document obsoletes RFC5549.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.