Video sample component range

[garethsb]

Should there be a [component_]range Flow attribute and a matching urn:x-nmos:cap:format:[component_]range Receiver parameter constraint, corresponding to the RANGE format-specific parameter defined in ST 2110-20 for video/raw and in RFC 9134 for video/jxsv?

See e.g. https://tools.ietf.org/html/rfc9134#section-7.1.

Following the general pattern for such questions...

• If there are Receivers that can only correctly handle streams with a sub-set of the possible values of this parameter, then the answer is probably yes.
• If it is only that Receivers need the value to correctly handle a given stream, then the presence of the RANGE format-specific parameter in the SDP data is probably enough.

[garethsb]

@jonathan-r-thorpe points out that VSF TR-08 distinguishes between Full Range from limited range for two interoperability points in Capability Set C:

However, those interoperability points are also distinguished by other properties (e.g., frame height of 1200).

[garethsb]

One other note is that ST 2110-20 and RFC 9134 define the default value differently.