Repository navigation
Conversation
baylesj
force-pushed
the
baylesj/issue-342-transport-discovery-reqs
branch
from
October 29, 2026 21:35
2d59e08 to
62102be
Compare
baylesj
changed the title
baylesj
changed the title
baylesj
marked this pull request as ready for review
October 29, 2026 21:40
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Addresses #342 (part of #341). Builds on #378, so this PR targets that branch and the diff only shows the changes on top of it.
#378 adds discovery guidelines and transport requirements, but several sections still name mDNS, DNS-SD, or TLS-secured QUIC directly. These include how the Presentation API and Remote Playback API find receivers, and the security and privacy sections on private browsing, API considerations, and display names.
This PR changes those sections to refer to the discovery guidelines, OSP connections, and the transport requirements. The display name rules now cover names from any discovery mechanism, and DNS-SD Instance Names become one example.