Parsing and processing of RSVP messages

After having implemented the support for RSVP messages and a routing interface, it was time to implement the core of the RSVP process: the processing of RSVP messages.

When a message is received, the checksum is verified. If the message is not valid, it is discarded. If it is valid, it is stored in a RsvpMessage object and then passed to the parser.

The parser then performs consistency checks on the messages, such as an address and a port consistency check, and an integrity check (this one always passes as integrity checks have not been implemented), and finally analyses its contents.

One last check is performed before processing the message: it must have the correct shape, i.e. the objects must be correctly ordered. It is done as follows: the RsvpMessage object is transformed into the object corresponding to the message type; the constructor of this object will check that the message has the correct form; if not, it will throw a BadRsvpMessageException exception, and the message will be discarded.

Policy_Data objects should be examined, but as said previously, no standard has been decided yet. Policy_Data objects are hence ignored.

The processing of the message is quite long and complicated; this is the main part of the implementation. An RFC [#!RFC2209!#] based on ISI's implementation has been written in order to describe the operations that an implementation has to do. A summary of the processing of each message is written below. Unfortunately, I did not have time to implement the processing of Resv Error messages. The reasons for that are explained in section .