Each PLR will signal a bypass tunnel that avoids the next-hop node or link.

When a failure occurs, the PLR will push an additional label onto the label stack and start forwarding traffic onto its bypass tunnel.

The ingress router will include a RRO object in the path message to indicate the routers that should be PLRs and MPs along the protected path.

The ingress router will set the local protection desired flag in the session attribute object of the path message to inform all routers along the protected LSP path to establish bypass tunnels.

When the bypass tunnel is in use, the MP will include the RRO object in its PathErr message, with the local protection in use flag set to notify the ingress router that it is using the bypass tunnel.

The packet can only be forwarded as an unlabeled packet.

The packet can be forwarded as a labeled or unlabeled packet, depending on the received label value.

The packet can be forwarded as a labeled or unlabeled packet, depending on the destination IP address in the payload

The packet can only be forwarded as a labeled packet.

An LSR answers requests for label mappings immediately, without waiting for a label mapping from the next-hop.

An LSR advertises label mappings to all peers for which it might be a next-hop for a given FEC.

An LSR distributes a label mapping for a FEC when it has been requested to do so.

An LSR propagates a label mapping downstream for a FEC. only if it has a label mapping for the FEC's next-hop.

The adjacency forms with the lower timeout value

The "show router Idp session" command output displays the adjacency in state "init"

The adjacency forms with the higher timeout value

The adjacency times out after 30 seconds

RSVP-TE operates in a downstream unsolicited label advertisement mode.

RSVP-TE makes use of ordered control mode.

RSVP-TE is an MPLS signaling protocol, based on the resource reservation protocol.

RSVP-TE enables the establishment of explicitly routed LSPs that can be automatically routed away from network failures

RSVP-TE supports explicitly routed LSPs using either loose or strict route definitions.

An LSP is a bidirectional path across the MPLS domain.

An LSP is a bidirectional path for a particular FEC across the MPLS domain.

An LSP is a unidirectional path across the MPLS domain.

An LSP is a bidirectional path between adjacent LSRs.

An LSP is a unidirectional path between adjacent LSRs.

When the interface to the peer router is down.

When router R1 has no route to the peer address 10.10.10.2.

When the adjacency between the two routers fails.

When the targeted session is not yet configured.

A router will never receive a packet containing this label value.

Request a new label from the peer that provided this label.

Pop the label.

PUSH an additional label onto the label stack.

Signal a new label to the peer that sent the packet.

The router cannot do a SWAP of this label.

The label does not match the egress label for the same FEC.

The label is for a FEC for which the next-hop is the peer router

The label was signaled in error.

The LSP will switchover to another path if a failure occurs.

The LSP will switchover to a better path as soon as it is available.

CSPF must be enabled for this LSP to attempt to find a better path.

The LSP will switchover to a better path in a MBB fashion.