Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Obsoleted by:

RFC 8950

Authors:

F. Le Faucheur
E. Rosen

Stream:

IETF

Source:

softwire (int)

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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

Abstract

Multiprotocol BGP (MP-BGP) specifies that the set of network-layerprotocols to which the address carried in the Next Hop field maybelong is determined by the Address Family Identifier (AFI) and theSubsequent Address Family Identifier (SAFI). The current 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 toallow advertising 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 in order to determine which of the protocolsthe address actually belongs to, and a new BGP Capability allowingMP-BGP Peers to dynamically discover whether they can exchange IPv4NLRI and VPN-IPv4 NLRI with an IPv6 Next Hop. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.