Label Distribution Protocol
7450 ESS MPLS Guide Page 587
guidelines and all Capability Negotiation Procedures as defined in RFC 5561. This TLV is
encoded using vendor proprietary TLV encoding as per RFC 5036. It uses a TLV type value of
0x3E03 and the Timetra OUI value of 0003FA.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|U|F| LSR Overload Cap TLV Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timetra OUI = 0003FA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S| Reserved |
+-+-+-+-+-+-+-+-+
Figure 56: LSR Overload Protection Capability TLV (Type== 0x3E03)
Where:
U and F bits : MUST be 1 and 0 respectively as per section 3 of LDP
Capabilities [RFC5561].
S-bit : MUST be 1 (indicates that capability is being advertised).
Procedures for LSR overload protection
The procedures defined in this document apply only to LSRs that support Downstream
Unsolicited (DU) label advertisement mode and Liberal Label Retention Mode. An LSR that
implements the LSR overload protection follows the following procedures:
1. A LSR MUST NOT use LSR Overload notification procedures with a peer LSR that has
not specified LSR Overload Protection Capability in Initialization Message received from
the peer LSR.
2. When an upstream LSR detects that it is overloaded with a FEC type then it MUST
initiate a LDP Notification Message with S bit ON in LSR Overload Status TLV and a
To Next Page
Loading...
