Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop
RFC 5549, “Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop”, is a Proposed Standard document published in May 2009 by F. Le Faucheur, E. Rosen. It has been obsoleted by RFC 8950 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5549 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5548 Routing Requirements for Urban Low-Power and Lossy Networks
- RFC 5550 The Internet Email to Support Diverse Service Environments Profile
- RFC 5547 A Session Description Protocol Offer/Answer Mechanism to Enable File Transfer
- RFC 5551 Lemonade Notifications Architecture
- RFC 5546 iCalendar Transport-Independent Interoperability Protocol
- RFC 5552 SIP Interface to VoiceXML Media Services
- RFC 5545 Internet Calendaring and Scheduling Core Object Specification
- RFC 5553 Resource Reservation Protocol Extensions for Path Key Support