Networked Media Open Specifications
RAML APIs for v1.1.2
JSON Schemas for v1.1.2
receiver_transport_params_dash
receiver_transport_params_mqtt
receiver_transport_params_websocket
JSON Examples for v1.1.2
receiver-active-get-200-uninit
receiver-constraints-get-200-2022-7
receiver-constraints-get-200-mqtt
receiver-constraints-get-200-websocket-ext
receiver-patch-activation-only
receiver-patch-redundant-streams
receiver-stage-scheduled-absolute
receiver-stage-scheduled-relative
receiver-stage-scheduled-transportfile
receiver-stage-success-redundant-streams
sender-constraints-get-200-2022-7
sender-constraints-get-200-mqtt
sender-constraints-get-200-websocket-ext
sender-patch-redundant-streams
Best Common Practices
BCP-002-02: Asset Distinguishing Information
BCP-003-01: Secure Communications in NMOS Systems
BCP-003-02: Authorization in NMOS Systems
BCP-003-03: Certificate Provisioning in NMOS Systems
BCP-004-01: Receiver Capabilities
BCP-005-01: EDID to Receiver Capabilities Mapping
←APIs - Server Side Implementation · Index↑ · Interoperability - NMOS IS-04→
The Connection Management API is intended to be used alongside other NMOS specifications, and may also be used alongside other common non-NMOS specifications. These documents cover common interoperability requirements when operating in either of these situations.
←APIs - Server Side Implementation · Index↑ · Interoperability - NMOS IS-04→