How to check if a SSF Transmitter supports multiple streams per receiver

[thomasdarimont]

In section 8.1.1.1. Creating a Stream of the SSF spec, it says that an SSF Transmitter should respond with status 409 | if the Transmitter does not support multiple streams per Receiver.

In the OIDF conformance tests, we assumed that the transmitter supports only one stream per receiver. I just relaxed this check in the conformance test to accept the status codes 201 and 409.

• 201: Transmitter supports multiple streams per receiver
• 409: Transmitter does NOT support multiple streams per receiver
  (I’ll update the demo env tomorrow)

I was wondering if this might cause interoperability problems, since a receiver cannot tell upfront whether a CAEP Interop-compatible transmitter supports multiple streams per receiver. This is not exposed in the transmitter metadata and can only be deduced from the stream creation response.

The CAEP interop spec, in 2.3.8.2 Stream Control, says that the Transmitter MAY support multiple streams with the same Receiver.

Is MAY support for multiple streams enough, or should we say here that the transmitter must support only one stream per receiver?

[tulshi]

I think the intent of that language is that if the same receiver tries to create more than one stream with the same transmitter, and the transmitter does not support multiple streams, then the transmitter responds with a 409. The first "create stream" (if successful) will always return 201, regardless of whether the transmitter supports multiple streams or not.

[jogu]

Is MAY support for multiple streams enough, or should we say here that the transmitter must support only one stream per receiver?

I think at a minimum there's probably a need for a statement to match the 'MAY' - i.e. that receivers MUST function correctly even if they can only create a single stream?