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

Enhance BYOD description #12

Closed
chris-box opened this issue Sep 3, 2020 · 1 comment
Closed

Enhance BYOD description #12

chris-box opened this issue Sep 3, 2020 · 1 comment
Labels
enhancement

Comments

@chris-box
Copy link
Contributor

@chris-box chris-box commented Sep 3, 2020

No, I don't think that would be right.

I don't think this case is specific to non-MDM devices. Even with MDM devices, devices aren't often configured to know which domains are privately accessible on an enterprise Wi-Fi network. Certainly MDMs could be updated going forward (which wouldn't be possible for pure BYOD cases), but that's not the status quo. Also, if we have a mechanism that works for the pure BYOD case, it wouldn't be necessary to build an MDM-specific solution.

Agreed, we can say the use case is specific to "BYOD" without explicitly saying "BYOD without MDM". On a side note, MDM is a secure way of configuring endpoints and a secure mechanism will be required for pure BYOD case to be applicable to MDM. Configuration profile could be another way to securely provision the BYOD without MDM (see https://tools.ietf.org/html/draft-reddy-add-enterprise-00#section-5).

Originally posted by @tireddy2 in #2 (comment)

@chris-box chris-box added the enhancement label Sep 3, 2020
@chris-box
Copy link
Contributor Author

@chris-box chris-box commented Nov 6, 2020

This topic is not in the current scope of the draft, so closing for now.

@chris-box chris-box closed this Nov 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement
Projects
None yet
Development

No branches or pull requests

1 participant