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

[Meta] Evaluate presentation screen discovery mechanisms #5

Closed
2 tasks done
mfoltzgoogle opened this issue Nov 22, 2016 · 9 comments
Closed
2 tasks done

[Meta] Evaluate presentation screen discovery mechanisms #5

mfoltzgoogle opened this issue Nov 22, 2016 · 9 comments
Labels

Comments

@mfoltzgoogle
Copy link
Contributor

mfoltzgoogle commented Nov 22, 2016

This issue covers evaluation of presentation screen discovery mechanisms.

Per the charter scope, the focus will be on LAN discovery mechanisms. The following have been proposed thus far:

(If there are any I have missed, please reply to this issue.)

The task for each is to evaluate them along the functional and non-functional requirements, and make an initial recommendation to explore further.

@mfoltzgoogle
Copy link
Contributor Author

mfoltzgoogle commented Nov 22, 2016

The evaluations should cover the following criteria (non-exhaustive):

  • Functional
  • Reliability
  • Latency of device discovery / device removal
  • Ease of implementation / deployment
  • Security - both of the implementation, and whether it can be leveraged to enhance security of the entire protocol
  • Privacy: what device information is exposed
  • Network efficiency
  • Power efficiency
  • IPv4 and IPv6 support
  • Standardization status and likelihood of successful interop

@louaybassbouss
Copy link
Contributor

@mfoltzgoogle you can count on me for the discovery part. I will first start with SSDP/DIAL.

@mwatson2
Copy link

mwatson2 commented Dec 6, 2016

@louaybassbouss Please let me know if I can help with the DIAL related aspects.

@louaybassbouss
Copy link
Contributor

@mwatson2 sorry for late reply, yes I will let you know if I need help. I am not sure if in the evaluation of discovery protocols we need to consider DIAL or only SSDP. I think the DIAL API part (POST/GET/DELETE HTTP requests on the /apps/... endpoint) could be evaluated in the "Protocol Signalling". What do you think?

@chrisn
Copy link
Member

chrisn commented Jan 20, 2017

As input to the evaluation, here's some previous work from myself and a colleague - there may be some useful info on mDNS and SSDP.

@louaybassbouss
Copy link
Contributor

@mfoltzgoogle @mwatson2 @chrisn I just submitted the PR #20 which contains the SSDP evaluation. feel free to review and comment.
@mwatson2 I focussed in the document only on the discovery part which is SSDP but discussed how DIAL uses SSDP, Device Description and how it signal the Endpoint of the DIAL Server. We should consider DIAL REST API in the control protocol (#11) evaluation as well. What do you think?

@mfoltzgoogle
Copy link
Contributor Author

We've landed initial evaluations for #6 and #7. There are some follow up items around security and data collection which are tracked under separate issues linked from the main documents.

@chrisn Apologies, but I missed #5 (comment) you made some time ago with the MediaScape report on discovery. I'll definitively take a look before closing this meta-issue out.

@mfoltzgoogle
Copy link
Contributor Author

@chrisn, I deep linked to your literature review in the README - thanks for noting it as I wasn't familiar with some of the technologies listed.

@chrisn
Copy link
Member

chrisn commented Oct 6, 2017

Many thanks @mfoltzgoogle, I've just edited the review to bring a few parts up to date.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants