The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2001-Oct> msg00471



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

Mandatory objects when using RSVP-TE for LSP Tunnels

  • From: Jean-Bertos Simo <JBSimo@VIPswitch.com>
  • Date: Thu, 1 Nov 2001 14:21:13 -0500

Title: Mandatory objects when using RSVP-TE for LSP Tunnels

In draft-ietf-mpls-rsvp-lsp-tunnels-08.txt, <sender descriptor> and <LABEL_REQUEST> are mandatory objects in a Path Message. I would like someone to enlighten me about the following issues:

1) What's the expected behavior of an RSVP-capable router that receives a Path Message:
-  without a <LABEL_REQUEST> object?
-  without a <sender descriptor> object?
My understanding is that the Path Message can be silently dropped or the router can return a PathErr Message. However, my preference would go to dropping the Path Message to reduce traffic load.

2) Are these two objects mandatory in a PathTear Message when dealing with a LSP_TUNNEL_IPV4_SESSION session object?

3) If any of these objects is missing in a PathTear Message, what behavior is expected from a RSVP-capable router?

4) When processing a PathTear Message, do we have to check whether  the <SENDER_TEMPLATE> or  <SENDER_TSPEC> objects are empty or containing any data?

5) Can anyone provide me references where I can find mandatory objects of Teardown, Error and Confirmation messages of RSVP-TE?

Thanks for your help.

Jean-Bertos