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

Metadata coordination between discovery and application protocols #346

Open
Tracked by #345
markafoltz opened this issue Sep 18, 2024 · 1 comment
Open
Tracked by #345
Assignees

Comments

@markafoltz
Copy link
Contributor

The existing spec checks for consistency between metadata obtained through DNS-SD (instance name) and CBOR (agent-info) and considers inconsistency a reason to flag the agent as not trustworthy.

https://www.w3.org/TR/openscreenprotocol/#instance-names

If we want to maintain this requirement, we need to rephrase this in a way that does not link DNS-SD and CBOR so closely.

@markafoltz
Copy link
Contributor Author

From #344, @backkem wrote

It may be worth considering if part of the agent-info concerns are better handled on the 'network' side of the split. E.g.: it's hard to know what you're connecting to/authenticating without giving it a proper name. But this can be refined in iterations.

Agreed. agent-info also covers a lot of the application level concerns like the API capabilities of the agent and the locales for rendering presentations. One resolution would be to split it into multiple messages.

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

1 participant