-
Notifications
You must be signed in to change notification settings - Fork 22
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
Allow additional discovery mechanisms. #283
Conversation
@DavidSchinazi here's some updated language about DNS-SD usage for OSP. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing this!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @mfoltzgoogle for this PR LGTM also changes proposed by @DavidSchinazi
Sorry for the long turnaround time @DavidSchinazi. I finally got around to addressing your last review comments. The group agreed this was good to merge with your comments addressed; if you have any additional feedback feel free to append to the issue. |
SHA: 7305111 Reason: push, by @mfoltzgoogle Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Addresses Issue #273: [mDNS] OpenScreenProtocol should not restrict DNS-SD to mDNS
This makes it explicit that while DNS-SD over mDNS is mandatory to implement, the rest of the protocol doesn't rely on mDNS being the only way for agents to discover one another, and they can query DNS-SD over unicast DNS.
Note that we may need to adjust the
at
mechanism intended to restrict connection attempts to intra-LAN scenarios. Would like to look at that in a separate issue.Preview | Diff