is-05
is-05 copied to clipboard
AMWA-TV
AMWA IS-05 NMOS Device Connection Management Specification (Stable)
By allowing for incomplete Requests to be made via HTTP Patch using the `/single` Interface a more or less undocumented state-machine is created. Apart from that request validation and general...
It should be made mandatory for the controller to push new SDPs to subscribed devices when a sender updates itself in the registry (based off the version field).
The example Sender Stage Succes https://specs.amwa.tv/is-05/releases/v1.1.2/examples/sender-stage-success.html does not match the Schema https://specs.amwa.tv/is-05/releases/v1.1.2/APIs/schemas/resolved/sender-response-schema.html for "activation-time". https://specs.amwa.tv/is-05/releases/v1.1.2/examples/sender-stage-success-redundant-streams.html has the same issue.
During Montreal workshop, the following question came up. Where do the 4-200 ranges come from for `fec_block_width`, `fec_block_height`, here: https://github.com/AMWA-TV/is-05/blob/d18748f078b34a827b9c5ddcd3d2211f0a3c633a/APIs/schemas/sender_transport_params_rtp.json#L90-L101 These ranges have been present since these parameters were introduced...
I believe there is a typo in the example for absolute sender activation: `activate_scheduled_relative` should be `activate_scheduled_absolute` (https://github.com/AMWA-TV/is-05/blob/v1.1.x/examples/sender-stage-absolute-success.json#L5) A similar issue was fixed for receivers in #32, but not for...
Section "Operation with RTCP" doesn't comply with https://datatracker.ietf.org/doc/html/rfc3550. I wasn't managed to find the source of > Where RTCP and forward error correction are both in use the RTP port...
See @garethsb's comment at end of #165
Questions from @maweit on AMWA Slack that we think are worth tracking to clarify in the spec or an accompanying INFO doc... We're having difficulties to judge if an activation...
As of v1.1-dev, new transport types have been added (websocket/mqtt), but a version bump is required in order to add any further new ones. This is the safest route, but...
Adding this as an issue here but with the expectation that @AMWA-TV/nmos-architecture-review will move it somewhere more general. IS-04 and IS-05 say things like: > Versions MUST be represented as...