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

Further investigation on local network and discovery #7

Open
tomoyukilabs opened this issue Sep 18, 2018 · 3 comments
Open

Further investigation on local network and discovery #7

tomoyukilabs opened this issue Sep 18, 2018 · 3 comments

Comments

@tomoyukilabs
Copy link
Member

As pointed out in #1, device names in local network is not globally unique and it is difficult to determine how to trust such a device. Such a device often has its default name, it can be assigned automatically, or users can determine its name as they want.

On the other hand, we could face several difficulties when we would use such a local network device. For example:

  • We must manually indicate device name as a form of a URL that begins with http:// or https://.
  • Current modern browser do not provide capability of service discovery to find local servers automatically. Note that the old versions of Safari for Mac used to have such a feature.
  • Web applications do not have any methods to discover local servers due to security and privacy consideration. (see W3C Working Group Note of Network Service Discovery for more information.)

In this issue, we would like to explore how we should deal with device names and DNS-SD/mDNS for local device utilization and enhancement without enlarging risks and threats, so that users would gain benefits of local device integration into web applications.

@tomoyukilabs
Copy link
Member Author

One additional comment for clarification: Usually, default device names are defined by device manufacturers, and often like VENDORNAME-MODELNAME-XXX.local instead of a simple name like printer.local. Of course, such a name does not seem user-friendly.

@X-Ryl669
Copy link

If you can separate setup phase from using phase, then you can expect that a device will have its "unfriendly" name only during setup phase, and the user will give it a more useful name that'll be used in its using phase.

Ideally, the setup phase should use HTTPS, but the using phase must use HTTPS. If the proposal ensure the latter, I think it's good.

I don't think it's the goal of this proposal to make setup phase easier (setting up a new device is too manufacturer-specific), so let's focus on using phase being easy.

@tomoyukilabs
Copy link
Member Author

I don't think it's the goal of this proposal to make setup phase easier

@X-Ryl669 Correct. We should focus on the using phase. The comment above about the default name is just informative. Thanks for clarification.

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

No branches or pull requests

2 participants