RSVP-TE for FRR

The FRR protection tunnel LSP’s set-up priority, holding priority, hoplimit,

and bandwidth (bytes per second)

• Protection method: one-to-one (

• Administrative group (link-coloring) information such as

0x1) or facility (0x2)include-any,

exclude-any

32-bit masking, mapping to the 32-bit admin group bits

New

messages for one-to-one backup only. It contains a list of possible PLRs and the

node each PLR should avoid.


FRR-Related Flags Defi ned in the SESSION_ATTRIBUTE Object — In
the PATH message, the SESSON_ATTRIBUTE object has an 8-bit fl ag fi eld.
In the RSVP-TE for MPLS LSP signaling (RFC 3209), the fi rst three
least signifi cant bits are defi ned: local-protection-desired (0x1),
label-recording-desired (0x2), and SE-style-desired (0x4). RFC
4090 uses the next two bits for FRR: bandwidth-protection-desired (0x8)
and node-protection-desired (0x10). These two bits allow the HE router
to indicate the desire for node protection and the reservation of bandwidth
for the FRR protection tunnels.
• FRR-Related Flags Defi ned in the RRO Object — In the PATH and
RESV messages, the RRO object has an 8-bit fl ag fi eld in each IPv4
subobject. In the RSVP-TE for MPLS LSP signaling (RFC 3209), the fi rst
two least signifi cant bits are used: local-protection-available (0x1)
and local-protection-in-use (0x2). RFC 4090 uses the next two
bits for FRR: bandwidth-protection-available (0x8) and
node-protection-available (0x10). These two bits allow the Tail
router to indicate the availability of node protection and reservation
of bandwidth for the FRR protection tunnels.

DETOUR Object (Object Class 63) — This object is used in the PATH, and include-all subobjects. Each of these subobjects is a