RFC 9229: IPv4 Routes with an IPv6 Next Hop in the Babel Routing Protocol
In plain English — editorial summary, not part of the RFC
This document defines an extension to the Babel routing protocol that allows announcing routes to an IPv4 prefix with an IPv6 next hop, which makes it possible for IPv4 traffic to flow through interfaces that have not been assigned an IPv4 address.
Document record
- Document ID
- RFC9229
- Published
- May 2022
- Authors
- J. Chroboczek
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8215Local-Use IPv4/IPv6 Translation PrefixCurrent
August 2017
- RFC 6782Wireline Incremental IPv6Current
November 2012
- RFC 9262Tree Engineering for Bit Index Explicit Replication (BIER-TE)Current
October 2022
- RFC 9166A YANG Data Model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) SnoopingCurrent
February 2022
- RFC 9403A YANG Data Model for RIB ExtensionsCurrent
November 2023
- RFC 9450Reliable and Available Wireless (RAW) Use CasesCurrent
August 2023
- RFC 8965Applicability of the Babel Routing ProtocolCurrent
January 2021
- RFC 9657Time-Variant Routing (TVR) Use CasesCurrent
October 2024
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?