Transport and message encoding
←Overview · Index↑ · Security and authorization→
Implementations MUST use HTTP
or HTTPS
as the communication transport.
Implementations MUST use JSON
as the message encoding data format.
RAML APIs for v1.0.0
JSON Schemas for v1.0.0
JSON Examples for v1.0.0
bulkProperties-get-no-descriptors-200
bulkProperties-put-rebuild-200
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-004-02: Sender Capabilities
BCP-005-01: EDID to Receiver Capabilities Mapping
BCP-005-02: NMOS Support for IPMX/HKEP
BCP-005-03: NMOS Support for IPMX/PEP
BCP-006-04: NMOS Support for MPEG Transport Streams
←Overview · Index↑ · Security and authorization→
Implementations MUST use HTTP
or HTTPS
as the communication transport.
Implementations MUST use JSON
as the message encoding data format.