RSVP Objects Structure

RSVP objects carry the information that comprises the contents of RSVP messages. Different combinations of objects define the information necessary for RSVP to signal LSPs. Each object is represented by a fixed-length header and a variable-length data field, as shown in Figure 9.

Figure 9: RSVP Object Header

The maximum object content length is 65,528 bytes. The Class-Num and C-Type fields may be used together as a 16-bit number to define a unique type for each object. Table 14 lists and describes the fields in the RSVP object header.

Table 14: Fields in the RSVP Object Header

Field Name	Defined	Description
Length	16 bits	Contains the total object length and must always be a multiple of 4.
Class-Num	The values of this field are defined in Appendix A, RFC 2205, Resource ReSerVation Protocol (RSVP), Version 1, Functional Specification.	Identifies the object class; for example, Session. For more information about object classes, see Table 15
C-Type	For a breakdown of the C-Type associated with each RSVP object, see Appendix A, RFC 2205.	Coded with values that are unique to each class number (Class-Num); for example, C-Type 1.
Object Data	The Class-Num and C-Type may be used to define a unique object. C-Type is the object type and is used to accommodate different Internet address families, such as those corresponding to IPv4 and IPv6 [44]. Currently, C-Type 1 is assigned to IPv4 and C-Type 2 is used for IPv6. The structure and format of the objects may change from one family to another.	Contains the data identified by the Class-Num and C-Type fields. For more information on object data, see Table 15.

The setup and maintenance of an RSVP session requires information that is encoded in multiple objects used in the various RSVP message types. Table 15 lists and describes some RSVP objects, the messages in which they are used, and the RFC to which you can refer for further information. The objects are listed in alphabetical order.

Table 15: RSVP Objects

Object Name	RSVP Message	RFC	Description
Adspec	Path	2205	Carries a summary of available services, delay and bandwidth estimates, and operating parameters used by specific QoS control services. The summary is computed as the Adspec passes each hop. The JUNOS software uses the Adspec field for maximum transmission unit (MTU) negotiation.
Detour	Path		Used in one-to-one backup to identify detour LSPs. For more information on the Detour object, see Internet draft draft-ietf-mpls-rsvp-lsp-fastreroute-03.txt, Fast Reroute Extensions to RSVP-TE for LSP Tunnels.
Error	PathErr, ResvErr, ResvConf	2205	Specifies an error in a PathErr or ResvErr message, or a confirmation in a ResvConf message.
Explicit route	Path	3209	Specifies a strict or loose path in the network topology.
FastReroute	Path		Used to control the backup for a protected LSP. The fast reroute object specifies the setup and hold priorities, the session attribute filters, and the bandwidth to be used for protection. It also allows a specific local protection technique to be requested. For more information on the fast reroute object, see Internet draft draft-ietf-mpls-rsvp-lsp-fastreroute-03.txt, Fast Reroute Extensions to RSVP-TE for LSP Tunnels.
Filter	Resv ResvTear ResvErr		Defines the source of the session.
FilterSpec	Resv	2205, 3209	Defines a subset of session data packets that should receive the desired QoS specified by a flow specification object.
FlowSpec	Resv	2205, 2210	Defines a desired QoS.
Hello	Hello	3209	Can be a request or a reply. Every request should generate a reply.
Hop	Path, Resv	2205	Carries the IP address of the RSVP-capable node that sent the message, and a logical outgoing interface.
Integrity	All message types	2205, 2747, 3097	Carries cryptographic data to authenticate the originating node and verify the contents of an RSVP message.
Label	Resv	3209	Contains the label value (for example, 100624) that is mapped to the LSP identified by the session value.
LabelRequest	Path	3209	Indicates, to the next downstream node, that a label assignment is requested.
Null			Has a class number of zero, and its C-Type is ignored. Its length must be at least 4, but can be any multiple of 4. A NULL object may appear anywhere in a sequence of objects, and its contents will be ignored by the receiver.
Policy data	Path, Resv, PathErr, ResvErr	2205	Carries information that allows a local policy module to decide whether an associated reservation is administratively permitted. The use of policy data objects is not fully specified at this time.
Properties		Juniper only	Specifies a Juniper Networks proprietary object used to carry information about the LSP.
RecRoute	Path, Resv	3209	Indicates the list of addresses that this Path message has transited.
RestartCap	Hello	3473	Indicates the sender node's graceful restart capability.
ResvConf	Resv, ResvConf	2205	Response to confirm a reservation request.
Scope	Resv, ResvErr, ResvTear	2205	Carries an explicit list of sender hosts towards which the information in the message is forwarded.
Sender	Path	2205, 3209	Contains a sender IP address and perhaps some additional demultiplexing information to identify a sender.
Session	All message types	2205, 3209	Contains the IP destination address (DestAddress), the IP protocol ID, and some form of generalized destination port, to define a specific session for the other objects that follow.
SessionAttribute	Path	3209	Indicates a variety of parameters including setup priority, hold priority, flags, name length, and session name.
SrcRoute	Path		Contains the list of addresses in the Explicit Route Object (ERO).
Style	Resv	2205, 3209	Defines the reservation style, plus style-specific information that is not in flow specification or filter specification objects.
Time	Path, Resv	2205	Contains the value for the refresh period used by the creator of the message.
Tspec	Path	2205	Defines the traffic characteristics of a sender's data flow.