Once a message has been accepted, it then has to be parsed. However, it is not very convenient to do operations on a series of bytes. This is why a structure called RsvpMessage is used to cut up the original raw message into logical parts.
The format of an RSVP message is shown in figure
. It has a header common to every message type, followed by a variable number of variable-length objects, as described in RFC 2205 [#!RFC2205!#].
RsvpMessage is therefore composed of a header, a RsvpCommonHeader object, and of a list of RSVP objects (see section
). This class has methods in order to be generated from a raw form.
The list of objects is different for each type of message (see examples in figure
). A class for each RSVP message type has been implemented in order to easily build and send these messages. Those classes all derive from a class called RsvpCoreMessage which contains methods common to all the message types.