RFC 8430: RIB Information Model
In plain English — editorial summary, not part of the RFC
Routing and routing functions in enterprise and carrier networks are typically performed by network devices (routers and switches) using a Routing Information Base (RIB). Protocols and configurations push data into the RIB, and the RIB manager installs state into the hardware for packet forwarding. This document specifies an information model for the RIB to enable defining a standardized data model. The IETF's I2RS WG used this document to design the I2RS RIB data model. This document is being published to record the higher- level information model decisions for RIBs so that other developers of RIBs may benefit from the design concepts.
Document record
- Document ID
- RFC8430
- Published
- September 2018
- Authors
- N. Bahadur; S. Kini; J. Medved
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 28
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9403A YANG Data Model for RIB ExtensionsCurrent
November 2023
- RFC 7608IPv6 Prefix Length Recommendation for ForwardingCurrent
July 2015
- RFC 8431A YANG Data Model for the Routing Information Base (RIB)Current
September 2018
- RFC 8432A Framework for Management and Control of Microwave and Millimeter Wave Interface ParametersCurrent
October 2018
- RFC 8426Recommendations for RSVP-TE and Segment Routing (SR) Label Switched Path (LSP) CoexistenceCurrent
July 2018
- RFC 8424Extensions to RSVP-TE for Label Switched Path (LSP) Ingress Fast Reroute (FRR) ProtectionCurrent
August 2018
- RFC 8444OSPFv2 Extensions for Bit Index Explicit Replication (BIER)Updated
November 2018
- RFC 8416Simplified Local Internet Number Resource Management with the RPKI (SLURM)Current
August 2018
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?