Skip to content

Commit

Permalink
Fix links for patch release (#160)
Browse files Browse the repository at this point in the history
  • Loading branch information
garethsb authored Aug 31, 2022
1 parent 613121f commit 45b2262
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion docs/Controllers.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ Controllers MUST adhere to the [APIs: Client Side Implementation Notes](APIs%20-

#### API Common Keys

Controllers MUST follow the requirements for common API keys specified in the [IS-04 APIs: Common Keys](https://specs.amwa.tv/is-04/releases/v1.3.1/docs/2.1._APIs_-_Common_Keys.html) document including the requirements regarding [use of URNs](https://specs.amwa.tv/is-04/releases/v1.3.1/docs/2.1._APIs_-_Common_Keys.html#use-of-urns).
Controllers MUST follow the requirements for common API keys specified in the [IS-04 APIs: Common Keys](https://specs.amwa.tv/is-04/releases/v1.3.2/docs/APIs_-_Common_Keys.html) document including the requirements regarding [use of URNs](https://specs.amwa.tv/is-04/releases/v1.3.2/docs/APIs_-_Common_Keys.html#use-of-urns).

### Interacting with Non-NMOS Devices

Expand Down
2 changes: 1 addition & 1 deletion docs/Interoperability - IS-04.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ The Connection API includes a `master_enable` parameter in the `/active` endpoin
The Receiver endpoint also includes a `sender_id` parameter that can be used to indicate that the Receiver is connected to a specific NMOS Sender, for example, via unicast RTP or source-specific multicast.
Similarly, the Sender endpoint includes a `receiver_id` parameter that can be used to indicate that the Sender is connected to a specific NMOS Receiver, for example, via unicast RTP.

The API implementation MUST use these parameters to populate the `subscription` attribute of the corresponding IS-04 Sender or Receiver, according to the [Behaviour: Nodes](https://specs.amwa.tv/is-04/releases/v1.3.1/docs/4.3._Behaviour_-_Nodes.html) section of the IS-04 specification.
The API implementation MUST use these parameters to populate the `subscription` attribute of the corresponding IS-04 Sender or Receiver, according to the [Behaviour: Nodes](https://specs.amwa.tv/is-04/releases/v1.3.2/docs/Behaviour_-_Nodes.html) section of the IS-04 specification.
It is the client's responsibility to set or unset (using `null`) the `sender_id` or `receiver_id` parameters when modifying the `transport_params` or `transport_file`.

## Support For Legacy IS-04 Connection Management
Expand Down

0 comments on commit 45b2262

Please sign in to comment.