Enforce encryption/authentication on in-session RMCP+ messages

In-session RMCP+ messages must have the encryption set to match the
negotiated encryption setting that was set at session creation time.

Tested: Attempt to send an unencrypted payload with a valid session ID.

Change-Id: Iaa20cb9df9b2224bb81e3be5808cab9202e6dbf4
Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com>
1 file changed