Status endpoint requirements for CAEP interop profile

[thomasdarimont]

This topic should address the discussion on the requirements for the status endpoint for the CAEP interoperability profile.

[jischr]

Stream Status 8.1.2
Event Streams are managed independently. A Receiver MAY request that events from a stream be interrupted by Updating the Stream Status (Section 8.1.2.2). If a Transmitter decides to enable, pause or disable updates from a stream independently of an update request from a Receiver, it MUST send a Stream Updated Event (Section 8.1.5) to the Receiver.

The Profile mentions
Stream Verification
A Receiver MUST be able to verify the liveness of the Stream by requesting that the Transmitter send it a Stream Verification event by providing a valid authorization
This is a bit vague, perhaps we can reiterate what is in SSF. This section is getting distorted with the Receiver's ability to read a stream’s status by making a HTTP GET request to the stream's Status Endpoint. The Transmitter MUST support this.

Profile Addition?
As defined in Section 8.1.2, If a Transmitter decides to enable, pause or disable updates from a stream independently of an update request from a Receiver, it MUST send a Stream Updated Event to the Receiver. (It MUST also be able to to receive an update request from a Receiver and update the status of a stream accordingly. - this needs clarification with section on Updating/Replacing a Stream’s Configuration)

What operations count as "activity" for poll-based streams?
How should Receivers react to streams disabled due to inactivity?