Add Receiver requirements to CAEP Interop Profile

[jischr]

This PR starts to address adding Receiver requirements. More diffs will likely come in another PR.

Issue #294

[tulshi]

General comment: Instead of generic language such as "provide stream configuration", "provide current stream status", etc., should we specify the management API calls that need to be supported? E.g. "When a Receiver makes a Read Stream Configuration call as described in section 8.1.1.2 of the SSF spec to the Transmitter with valid authorization, the Transmitter MUST respond with a valid Stream Configuration as described in section 8.1.1. of the SSF spec.

[jischr]

General comment: Instead of generic language such as "provide stream configuration", "provide current stream status", etc., should we specify the management API calls that need to be supported? E.g. "When a Receiver makes a Read Stream Configuration call as described in section 8.1.1.2 of the SSF spec to the Transmitter with valid authorization, the Transmitter MUST respond with a valid Stream Configuration as described in section 8.1.1. of the SSF spec.

I agree. The organization is a bit lacking and i want to match the language a bit closer to SSF.

[appsdesh]

Thank you @jischr

[iamseanodentity]

Looks good. I fact checked most/all references to the Final spec published.