HP 10500 SERIES Configuration Manual page 103

ResvConf messages—Sent to receivers to confirm Resv messages.
•
Hello messages—Sent between any two directly connected RSVP neighbors to set up and maintain
•
the neighbor relationship that has local significance on the link.
The TE extension to RSVP adds new objects to the Path message and the Resv message. These objects
carry not only label bindings but also routing constraints, supporting CR-LSP and FRR.
New objects added to the Path message include LABEL_REQUEST, EXPLICIT_ROUTE,
•
RECORD_ROUTE, and SESSION_ATTRIBUTE.
• New objects added to the Resv message include LABEL and RECORD_ROUTE
The LABEL_REQUEST object in the Path message requests the label bindings for an LSP. It is also saved
in the path state block. The node receiving LABEL_REQUEST advertises the label binding using the LABEL
object in the Resv message to the upstream node, accomplishing label advertisement and transmission.
Setting up an LSP tunnel
Figure 27 Setting up an LSP tunnel
The following is a simplified procedure for setting up an LSP tunnel with RSVP:
The ingress LSR sends a Path message that carries the label request information, and then forwards
1.
the message along the path calculated by CSPF hop-by-hop towards the egress LSR.
After receiving the Path message, the egress generates a Resv message carrying the reservation
2.
information and label and then forwards the message towards the ingress along the reverse
direction of the path along which the Path message travels. The LSRs that the Resv message
traverses along the path reserve resources as required.
When the ingress LSR receives the Resv message, LSP is established.
3.
As resources are reserved on the LSRs along the path for the LSP established by using RSVP-TE, services
transmitted on the LSP are guaranteed.
RSVP refresh mechanism
RSVP maintains path and reservation state by periodically retransmitting two types of messages—Path
and Resv. These periodically retransmitted Path and Resv messages are called refresh messages. They are
sent along the path that the last Path or Resv message travels to synchronize the state between RSVP
neighbors and to recover lost RSVP messages.
When many RSVP sessions are present, periodically sent refresh messages become a network burden. In
addition, for some delay sensitive applications, the refreshing delay they must wait for recovering lost
RSVP messages may be unbearable. Because tuning refresh intervals is not adequate to address the two
problems, the refreshing mechanism was extended in RFC 2961 RSVP Refresh Overhead Reduction
Extensions to address the problems.
Message_ID extension
•
RSVP itself uses Raw IP to send messages. The Message_ID extension mechanism defined in RFC
2961 adds objects that can be carried in RSVP messages. Of them, the Message_ID object and
the Message_ID_ACK object are used to acknowledge RSVP messages, improving transmission
reliability.
95