Move metadata discovery to network protocol #367
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Move agent-info, agent-status messages and CDDL to network spec - Add pre-auth message restrictions and abuse protection guidance - Keep capability value definitions (receive-audio, etc.) in application spec - Resolve Issue(346) by making agent-info a network-level message
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Moves
agent-infomessage definitions and metadata discovery from the application protocol to the network protocol,establishing clearer separation of concerns.
Motivation
Addresses #346: The spec currently links DNS-SD instance names with
agent-infofor consistency checking, creatingtight coupling between discovery and application layers. Since
agent-infocan be exchanged before authenticationcompletes, protocol implementations need the network layer to control this exchange to maintain security boundaries.
By making
agent-infoa network protocol message, the DNS-SD/agent-info coordination becomes internal to the networkspec rather than a cross-spec dependency.
Also partially relates to #343 by moving
agent-status(connection keep-alive) to the network protocol as it seemsbetter suited for transport-specific details.
Changes
Network protocol (
network.bs):agent-infomessage definitionagent-statusmessagesApplication protocol (
application.bs):agent-infomechanismCDDL:
agent-info-*,agent-status-*,request,responsetonetwork_messages.cddlagent-capabilityenum inapplication_messages.cddl