RIFT Protocol Leaf-Transfer Capability for Ring Network Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The RIFT protocol lacks support for leaf ring network access, which is common in metropolitan area networks and bearer networks, limiting its adaptability in ring topology scenarios.
Innovation Solution
Incorporating a leaf-transfer capability identifier into the RIFT protocol to enable leaf nodes to access the network through designated nodes, establishing neighbor relations, and flooding topology and prefix information to facilitate routing computations that include links with leaf-transfer capability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the RIFT protocol is used for routing in fat tree topology, then routing efficiency and ECMP support are improved, but support for leaf ring network access is lost
Solution Approach 1:
The patent makes the RIFT protocol dynamic by introducing a leaf-transfer capability identifier that can be enabled or disabled based on network topology requirements. Leaf nodes can dynamically support leaf-to-leaf access when the identifier is enabled, allowing the protocol to adapt between traditional fat-tree operation and ring network access modes as needed
2Device complexity
If the RIFT protocol supports only spine-leaf topology, then protocol simplicity is maintained, but adaptability to ring network scenarios is reduced
Solution Approach 1:
The patent changes a key parameter of the RIFT protocol by introducing the leaf-transfer capability identifier. This parameter change enables leaf nodes to accept traffic from other leaf nodes directly, transforming the protocol's behavior to support ring network scenarios while maintaining backward compatibility with traditional spine-leaf operations
3Reliability
If leaf nodes are interconnected in a ring topology, then network redundancy and access flexibility are improved, but protocol compatibility issues arise
Solution Approach 1:
The leaf-transfer capability identifier acts as an intermediary mechanism that enables compatibility between the RIFT protocol and ring network topologies. It mediates the interaction between leaf nodes, allowing them to exchange routing information and establish direct paths while maintaining protocol standard compliance
Data Source
AI summary
A protocol processing method and apparatus, and a storage medium are provided. The method includes: carrying a leaf-transfer capability identifier in an RIFT protocol, the leaf-transfer capability identifier being configured to indicate that a first node that carries the leaf-transfer capability identifier supports other leaf nodes within a network to access the network through the first node.