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).
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)
The text was updated successfully, but these errors were encountered: