TL;DR
This paper introduces a YANG data model for the Routing Information Base (RIB) that standardizes how network devices manage routing information. This model is crucial for enabling programmatic control and automation of network routing, aligning with the Interface to the Routing System (I2RS) initiative.
What Problem Does This Paper Address?
Network devices maintain a Routing Information Base (RIB) which stores information about how to forward network traffic. Traditionally, managing and querying this information has been complex and vendor-specific, hindering automation and interoperability. The I2RS (Interface to the Routing System) initiative aims to provide a standardized way to programmatically access and control routing functions. However, a key component, the RIB, lacked a standardized data model. This paper addresses this gap by defining a YANG data model for the RIB that is compatible with the I2RS framework, enabling consistent and efficient management of routing information across different network devices.
Methods
The paper defines a YANG (Yet Another Next Generation) data model, which is a standardized language for modeling network configuration and state data. The model is structured to represent the RIB, including routing instances, address families, routes, and nexthops. It leverages YANG's features for defining data structures, constraints, and operations. Key aspects include:
- Hierarchical Data Structure: The model organizes routing information in a tree-like structure, starting from routing instances down to individual routes and their associated nexthops.
- RPC Operations: The model defines Remote Procedure Call (RPC) operations for common routing tasks such as adding/deleting RIBs and routes, and updating routes.
- Notifications: It specifies notifications for events like route changes and nexthop resolution status, allowing for real-time monitoring.
- Features and If-Features: These are used to advertise the capabilities of a network device, such as support for different types of nexthops (e.g., tunnel, chain, protection) and encapsulation mechanisms.
Datasets
Not discussed in the paper.
Key Insights and Ideas
- Standardization is Key for Automation: The core insight is that a standardized data model for the RIB is essential for enabling programmatic control and automation of network routing, a goal of the I2RS initiative.
- Flexibility in Nexthop Representation: The model's detailed representation of nexthops, including various types like base, chain, protection, and load-balance, allows for flexible and sophisticated routing policies.
- Capability Negotiation: The use of YANG features and if-features is a smart way to allow network devices to advertise their supported routing capabilities, preventing configuration errors and ensuring interoperability.
- Comprehensive Operations: The inclusion of RPCs for add, delete, and update operations, along with notifications, provides a robust framework for managing routing information.
Key Results
The paper presents a detailed YANG data model that fulfills the requirements for managing the Routing Information Base within the I2RS framework. The model is designed to be comprehensive, covering various aspects of routing, including:
- Routing Instances: The ability to define and manage multiple routing instances.
- Address Families: Support for different address families (IPv4, IPv6, MPLS, MAC).
- Route Definitions: Detailed modeling of routes, including match conditions, attributes, and status.
- Nexthop Structures: A rich set of nexthop types to support complex forwarding scenarios.
- RPC Operations: Defined operations for RIB and route management.
- Notifications: Mechanisms for signaling route and nexthop status changes.
The primary "result" is the definition and specification of this YANG module, which serves as a blueprint for network device vendors and network operators.
Limitations and Future Work
- Implementation Specifics: While the model defines the data, the actual implementation details and how specific hardware capabilities map to the model are left to implementations.
- Future Enhancements: The paper references other related work and implies that further extensions might be needed for more advanced routing features or specific vendor implementations. The "Informative References" section points to related work on I2RS use cases and other YANG models, suggesting ongoing development in this area.
Summary updated