Skip to content

Commit

Permalink
Fixed comments from meeeting 2024-11-27
Browse files Browse the repository at this point in the history
Added back 2022-2 reference in the introduction
Senders and receivers must be in the transport registry
Changed wording JSON to resources for examples
Added back SDP examples in IS-04/5 + note on usage for RTP
Moved IS-04 section around to group flows and sources separate from senders and receivers.
  • Loading branch information
grukx authored Dec 3, 2024
1 parent 763c0d0 commit f342715
Showing 1 changed file with 16 additions and 6 deletions.
22 changes: 16 additions & 6 deletions docs/NMOS With MPEG TS.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,9 @@ _(c) AMWA 2024, CC Attribution-NoDerivatives 4.0 International (CC BY-ND 4.0)_

[MPEG Transport Stream][MPEG-TS] is a standard digital container format specified in ISO/IEC 13818-1, widely used for transmission and storage of audio, video, and data.

This BCP allows for the use of all transport types defined by IS-05 that can carry media type `video/MP2T`.
SMPTE [ST 2022-2][ST-2022-2] defines the Unidirectional Transport of Constant Bit Rate MPEG-2 Transport Streams using RTP on IP Networks.

This BCP allows for the use of all transport types defined in the [Transports][Transports-Registry] registry that can carry media type `video/MP2T`.

## Use of Normative Language

Expand All @@ -20,7 +22,7 @@ and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119]

The NMOS terms 'Controller', 'Node', 'Source', 'Flow', 'Sender', 'Receiver' are used as defined in the [NMOS Glossary][NMOS-Glossary].

## MPEG TS IS-04 Sources, Flows, and Senders
## MPEG TS IS-04 Sources, Flows

Nodes capable of transmitting MPEG TS streams **MUST** have Source, Flow, and Sender resources in the IS-04 Node API.

Expand All @@ -41,16 +43,19 @@ The Flow resource **MUST** indicate `video/MP2T` in the `media_type` attribute,

An example Flow resource is provided in the [Examples](../examples/).

## MPEG TS IS-04 Senders and Receivers
IS-04 Senders and Receivers **MUST** use transports defined in the [Transports][Transports-Registry] parameter registry.

### Senders
For Nodes implementing IS-04 v1.3 or higher, the following additional attributes defined in the [sender attributes register][Sender-Attributes] of the NMOS Parameter Registers are used for MPEG TS:

- [Bit Rate][Sender-Transport-Bit-Rate]
This attribute **MUST** be present as defined in equipment where the bit rate is known.

An example Sender JSON is provided in the [Examples](../examples/).

## MPEG TS IS-04 Receivers
The SDP file published at the `manifest_href` end-point **MUST** comply with the IS-05 usage guidelines for the specific transport and [RFC 4566][RFC-4566]

An example Sender resource is provided in the [Examples](../examples/).
## Receivers
Nodes capable of receiving MPEG TS streams **MUST** have a Receiver resource in the IS-04 Node API, which lists `video/MP2T` in the `media_types` array within the `caps` object.

If the Receiver has limitations on or preferences regarding the MPEG TS streams that it supports, the Receiver resource **MUST** indicate constraints in accordance with the [BCP 004-01][BCP-004-01] Receiver Capabilities specification.
Expand All @@ -64,12 +69,16 @@ The `constraint_sets` parameter within the `caps` object can be used to describe
The following parameter constraints **MAY** be used to express limitations on MPEG TS streams:
- [Transport Bit Rate][Cap-Transport-Bit-Rate]

An example Receiver JSON is provided in the [Examples](../examples/).
An example Receiver resource is provided in the [Examples](../examples/).

## MPEG TS IS-05 Senders and Receivers

Connection Management follows IS-05 for the transport type.

Any SDP file published at the **/transportfile** end-point **MUST** comply with the IS-05 usage guidelines for the RTP transport and [RFC 4566][RFC-4566].

An example SDP file is provided in the [Examples](../examples/).

## Controllers

Controllers **MUST** use IS-04 to discover MPEG TS Senders and Receivers and IS-05 to manage connections between them.
Expand All @@ -86,5 +95,6 @@ Controllers **MUST** support the BCP-004-01 Receiver Capabilities mechanism and
[Sender-Attributes]: https://specs.amwa.tv/nmos-parameter-registers/branches/main/sender-attributes "Sender Attributes Register"
[Sender-Transport-Bit-Rate]: https://specs.amwa.tv/nmos-parameter-registers/branches/main/sender-attributes/#bit-rate "Sender Transport Bit Rate"
[Cap-Transport-Bit-Rate]: https://specs.amwa.tv/nmos-parameter-registers/branches/main/capabilities/#transport-bit-rate "Transport Bit Rate"
[Transports-Registry]: https://specs.amwa.tv/nmos-parameter-registers/branches/main/transports "Transports"


0 comments on commit f342715

Please sign in to comment.