Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop

Metadata

Publisher: IETF
Doc Type: Standard
Pages: 10
Abstract: Multiprotocol BGP (MP-BGP) specifies that the set of network-layer protocols to which the address carried in the Next Hop field may belong is determined by the Address Family Identifier (AFI) and the Subsequent Address Family Identifier (SAFI). The current AFI/SAFI definitions for the IPv4 address family only have provisions for advertising a Next Hop address that belongs to the IPv4 protocol when advertising IPv4 Network Layer Reachability Information (NLRI) or VPN-IPv4 NLRI. This document specifies the extensions necessary to allow advertising IPv4 NLRI or VPN-IPv4 NLRI with a Next Hop address that belongs to the IPv6 protocol. This comprises an extension of the AFI/SAFI definitions to allow the address of the Next Hop for IPv4 NLRI or VPN-IPv4 NLRI to also belong to the IPv6 protocol, the encoding of the Next Hop in order to determine which of the protocols the address actually belongs to, and a new BGP Capability allowing MP-BGP Peers to dynamically discover whether they can exchange IPv4 NLRI and VPN-IPv4 NLRI with an IPv6 Next Hop. [STANDARDS-TRACK]
Publication Date: 2009-05-01
Status Note: Proposed Standard
DOI: 10.17487/RFC5549
Link: https://doi.org/10.17487/RFC5549
Author(s): François Le Faucheur
Eric C. Rosen
Keyword(s): BGP, IPv6, IPv4

Latest version of IETF RFC 5549

Document Versions — IETF RFC 5549

▶ IETF RFC 5549 (2009-05-01)

THIS DOC [SUPERSEDED] [LATEST VERSION]

Normative Reference(s)

IETF RFC 2119 [Active*]
IETF RFC 2545 [Active*]
IETF RFC 3107 [Superseded*]
IETF RFC 4291 [Active*]
IETF RFC 4364 [Active*]
IETF RFC 4760 [Active*]
IETF RFC 5492 [Active*]

Bibliographic Reference(s)

Chen, E. and S. Sangli, "Dynamic Capability for BGP-4" , Work in Progress, November 2006. EXTERNAL
Wu, J., Cui, Y., Metz, C., and E. Rosen, "Softwire Mesh Framework", Work in Progress, February 2009. EXTERNAL
Rosen, E., "Provisioning, Autodiscovery, and Signaling in L2VPNs", Work in Progress, May 2006. EXTERNAL
IETF RFC 4659 [Active*]
IETF RFC 4684 [Active*]
IETF RFC 4798 [Active*]
IETF RFC 4925 [Active*]
IETF RFC 5226 [Superseded*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5549.json

Superseded by:

RFC8950 NOT IN REGISTRY

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 5549, Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop. Available at https://doi.org/10.17487/RFC5549

Snippet:

IETF RFC 5549, Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop. Available at https://doi.org/10.17487/RFC5549

HTML (ISO 690 compliant)

Preview:

IETF RFC 5549, Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop. Available at https://doi.org/10.17487/RFC5549

Snippet:

<span class="citation"><cite>IETF RFC 5549</cite>, Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop. Available at <a href="https://doi.org/10.17487/RFC5549" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5549</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 5549, Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop
doi: 10.17487/RFC5549
url: https://doi.org/10.17487/RFC5549

Snippet:

<li>
<cite id="bib-rfc5549">IETF RFC 5549</cite>, Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop
<span class="doi">10.17487/RFC5549</span>
</li>

Referenced By

IETF RFC 5565 [Active*]
IETF RFC 5566 [Superseded*]
IETF RFC 7606 [Active*]
IETF RFC 8277 [Active*]