|
194 | 194 |
|
195 | 195 | <t>The scope of this document is restricted to unmanaged BYOD devices
|
196 | 196 | without a configuration profile and split DNS configuration on
|
197 |
| - explicitly trusted networks. It is similar to the way users explicitly |
198 |
| - disable VPN connection in specific networks and VPN connection is |
199 |
| - enabled by default in other networks for privacy. In this use case, the |
200 |
| - the user has authorized the client to override local DNS settings for a |
201 |
| - specific network. The unmanaged BYOD devices typically use the |
202 |
| - credentials (user name and password) provided by the IT admin to |
203 |
| - mutually authenticate to the Enterprise WLAN Access Point (e.g., |
204 |
| - PEAP-MSCHAPv2 <xref target="PEAP"></xref>, EAP-pwd <xref |
205 |
| - target="RFC8146"></xref>, EAP-PSK <xref target="RFC4764"></xref>). </t> |
| 197 | + explicitly trusted networks. In this use case, the user has authorized |
| 198 | + the client to override local DNS settings for a specific network. It is |
| 199 | + similar to the way users explicitly disable VPN connection in specific |
| 200 | + networks and VPN connection is enabled by default in other networks for |
| 201 | + privacy. The unmanaged BYOD devices typically use the credentials (user |
| 202 | + name and password) provided by the IT admin to mutually authenticate to |
| 203 | + the Enterprise WLAN Access Point (e.g., PEAP-MSCHAPv2 <xref |
| 204 | + target="PEAP"></xref>, EAP-pwd <xref target="RFC8146"></xref>, EAP-PSK |
| 205 | + <xref target="RFC4764"></xref>). </t> |
206 | 206 |
|
207 | 207 | <t><list style="hanging">
|
208 | 208 | <t hangText="Note: ">Many users have privacy and personal data
|
|
0 commit comments