MPLS LSP Connectivity Test with Unknown Initiator Address
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional MPLS connectivity test protocols fail to successfully perform end-to-end connectivity tests across multiple network segments when the initiator's address is unknown, as responders lack the necessary address information to send echo replies back to the initiator.
Innovation Solution
Incorporating a segment reachability sub-TLV (type-length-value) element into echo request and echo reply messages to carry reachability information, allowing responders to label switch the echo reply back to the initiator along the same path as the echo request, even if the initiator's address is unknown.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional MPLS connectivity test protocols are used, then the protocol structure remains simple, but the connectivity test fails when the initiator's address is unknown
Solution Approach 1:
The reachability information is segmented into a separate sub-TLV (type-length-value) element within the echo request message. This sub-TLV contains the initiator's address information that the responder needs to send the echo reply back. By segmenting the message structure and adding only the necessary reachability component, the protocol becomes reliable for unknown initiators without completely redesigning the entire message format.
Solution Approach 2:
The initiator's reachability information is collected and embedded in the echo request message before the connectivity test is executed. This preliminary inclusion of address information allows the responder to immediately know how to route the echo reply back to the initiator, ensuring the test can succeed even when the initiator's address would otherwise be unknown.
2Reliability
If reachability information is added to enable replies to unknown initiators, then connectivity test reliability improves, but message processing complexity increases
Solution Approach 1:
The sub-TLV element acts as an intermediary structure that carries the initiator's reachability information between the initiator and responder. Instead of requiring complex address resolution protocols or multiple message exchanges, the reachability information is directly embedded in the sub-TLV, simplifying the overall processing while ensuring reliable delivery of echo replies.
Solution Approach 2:
The sub-TLV structure is designed to be universal and can carry different types of reachability information depending on the specific network scenario. This multi-functional design allows the same message format to handle both known and unknown initiator cases, as well as different network segment configurations, without requiring separate protocol definitions.
3Loss of information
If segment reachability sub-TLV is used to carry reachability information, then end-to-end connectivity across multiple network segments is enabled, but information loss in traditional protocols is eliminated
Solution Approach 1:
The reachability information is nested within the existing echo request message structure as a sub-TLV element. This nested structure allows the additional information to be carried along with the original message without requiring a completely new protocol format. The sub-TLV is embedded within the broader message framework, maintaining compatibility while preventing information loss.
Data Source
AI summary
The present disclosure provides for carrying reachability information in an echo request message and/or an echo reply message, which can be used to reach an initiator when the initiator's address is unknown. An echo request message includes an FEC (forwarding equivalence class) stack that identifies a label switched path (LSP). The echo request message is received by a label switching routing element (LSR) on the LSP, and the echo request is originated by an initiator. In response to a detection that the FEC stack changes at the LSR, a segment reachability (SR) sub-TLV (type-length-value) element can be generated, where the SR sub-TLV includes reachability information that can be used to reach the initiator, and the reachability information includes an incoming label allocated by the LSR to reach the initiator.