3.1.5.2 Receiving a Route Check Summary message

When a Route Check Summary message arrives through a TCP Socket, it is correlated back to a Route Check Session object.

Unexpected Message - If the per-session Expected Message field is not equal to 0x14, the initiator MUST fail the Route Check Experiment request that instantiated the session and the associated session object is deleted.

Otherwise, the Expected Message field is set to 0x00 to indicate that the initiator is not expecting an incoming message. The initiator validates the fields in the Handshake header inside the message as per section 2.2.1.1 and section 2.2.2.8. If the header contains an invalid value, the initiator MUST fail the Route Check Experiment request that instantiated the session and the associated session object is deleted.

Packet Inversion Detected- If the Obs flag in the Handshake header of the Route Check Summary message (see section 2.2.2.8) is set to 0x01 (Packet inversion detected), the initiator MUST succeed the Route Check Experiment request that instantiated the session with a Prioritization Supported status and the associated session object is deleted.

Consecutive Packet loss Detected -If the Obs flag in the Handshake header of the Route Check Summary message is set to 0x02 (Packet loss detected) and the per-session Previous Observation field is also set to 0x02, the initiator MUST succeed the Route Check Experiment request that instantiated the session with a Prioritization Not Supported status and the associated session object is deleted.

Next, the Previous Observation field MUST be set to the value of the Obs flag in the Handshake header of the Route Check Summary message. The per-session Summaries Received field MUST be incremented by 1.

If the Summaries Received field is equal to 5, the initiator MUST succeed the Route Check Experiment request that instantiated the session with a Prioritization Not Supported status and the associated session object is deleted.