Path message processing

When a Path message is received, the path state is searched. If no entry corresponds to this session (characterised by a (Session, Sender_Template) pair), a new one is created. Otherwise, the old entry is updated if necessary. A Session object is required in every RSVP message; Sender_Template describes the sender's data flow.

Then, the Path message is forwarded in order to propagate the message up to the session's receiver.

If this session corresponds to a reservation listed in the reservation state, then reservation refreshes are sent to previous hops (as the control architecture only supports unicast, only one reservation refresh may be sent).

If needed, traffic control is updated.

The code performing Path message processing can be seen in appendix .