Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IS-04 Sender "interface_bindings" for IS-07 Senders #37

Open
garethsb opened this issue May 8, 2019 · 2 comments
Open

IS-04 Sender "interface_bindings" for IS-07 Senders #37

garethsb opened this issue May 8, 2019 · 2 comments
Labels
dependency issue This issue depends on an issue in an 'upstream' specification

Comments

@garethsb
Copy link
Contributor

garethsb commented May 8, 2019

This may be more of a question for IS-04.

The example in Core models - IS-04 highlights - Senders shows "interface_bindings": [ "eth0" ].

Does it make sense for Senders with transports like WebSocket or MQTT to be bound to a particular interface?

If so, in an out-of-band configuration (separate media and control networks) which network would WebSocket/MQTT flows be likely to use?

@mjeras
Copy link
Contributor

mjeras commented May 8, 2019

I think that strictly speaking we would have to announce the out-of-band interfaces and bind to them in order not to violate the existing NMOS. I can also see how that leads to increased complexity and potential confusion, so in my opinion it is a very valid discussion topic.

@garethsb
Copy link
Contributor Author

This is now an issue in IS-05 - AMWA-TV/is-05#70 - since binding to multiple interfaces in IS-04 probably then requires that we represent the multiple redundant interfaces with multiple 'legs' in IS-05.

@garethsb garethsb added the dependency issue This issue depends on an issue in an 'upstream' specification label May 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependency issue This issue depends on an issue in an 'upstream' specification
Projects
None yet
Development

No branches or pull requests

2 participants