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

[mDNS] Investigate compatibility with DNS-SD sleep proxy spec #121

Open
markafoltz opened this issue Nov 20, 2018 · 1 comment
Open

[mDNS] Investigate compatibility with DNS-SD sleep proxy spec #121

markafoltz opened this issue Nov 20, 2018 · 1 comment

Comments

@markafoltz
Copy link
Contributor

Based on internal feedback, we've found out that there is a spec in progress to allow a compatible network device to act as a "sleep proxy." The "sleep proxy" device advertises an DNS-SD service on behalf of another device that has gone to sleep (and thus can't respond to queries). The sleep proxy then wakes up the other device (apparently through WoL) if it sees an incoming packet for the service.

Details: http://stuartcheshire.org/sleepproxy/
Spec draft: https://tools.ietf.org/html/draft-ietf-dnssd-srp-00#section-2.6.2

It looks like sleep proxy is supported on Mac OS X and AirPort-branded devices.

Some things to investigate:

  • Is it compatible with QUIC?
  • What devices make sense as the proxy? Presumably access points/routers, but possibly PCs as well.
  • Is interoperability likely?
@markafoltz markafoltz changed the title [mDNS] Investigate and prioritize compatibility with DNS-SD sleep proxy spec [mDNS] Investigate compatibility with DNS-SD sleep proxy spec Nov 20, 2018
@markafoltz markafoltz added F2F and removed F2F labels May 2, 2019
@markafoltz markafoltz removed the F2F label Oct 18, 2020
@markafoltz
Copy link
Contributor Author

Would be great for someone in the group to investigate and report back here on the possibilities for the mDNS sleep proxy.

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