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-05 v1.1-dev "connection_uri" is singular #70

Open
garethsb opened this issue May 7, 2019 · 4 comments
Open

IS-05 v1.1-dev "connection_uri" is singular #70

garethsb opened this issue May 7, 2019 · 4 comments

Comments

@garethsb
Copy link
Contributor

garethsb commented May 7, 2019

In general, NMOS specs are written to allow redundancy and versioning of locators, e.g. by array properties for endpoints/URLs in various places in IS-04 and IS-05. The new "connection_uri" transport property is singular (and cannot be an array due to the schema for properties).

Is this a problem?

@garethsb
Copy link
Contributor Author

The /constraints endpoint can of course enumerate multiple possibilities for "connection_uri", but that's not quite the same thing as having multiple URLs active simultaneously...

@andrewbonney
Copy link
Contributor

When considering this initially I wondered if this ought to be another case where multiple 'legs' in the transport_params array is used. Each leg would have to correspond to an IS-04 interface_binding as before.

@garethsb
Copy link
Contributor Author

Ah, yes, hmmmm. Makes sense - different URLs represent different redundant endpoints - but (perhaps not in this case but in other imagined similar ones) it could be that many/all of the other transport parameters had to be common between all the 'legs', which makes updating them interesting?

Label "Discussion required"? ;-)

@andrewbonney
Copy link
Contributor

Hmm, yes, I hadn't considered that aspect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants