use case mapping to management functions + hotspot functionality

[jfisherbah]

The FMT_SMF.1/SERVER_CONF_SERVER functions referenced in Appendix H are inaccurate because they were not updated along with the function itself (so e.g. "Function f" doesn't exist).

Additionally for appendix H.1:

• FMT_SMF.1/SERVER_CONFG_AGENT function 34 references the need to assign "personal hotspot connections (if feature exists)." MDM function 34 maps to MDF function 25. Per feedback on the MDF PP, function 25 should not refer to hotspot functionality because that is actually covered by the WLAN Client module and configuration of that is mandated as function WL-3. Based on this, the reference to function 34 should be removed.
• similarly, FMT_SMF.1/SERVER_CONFIG_AGENT function 51 maps to MDF function 41 and tells the ST author to select "both options." Previously this referenced configuration of both hotspot and USB tethering. However, per the same MDF feedback, hotspot tethering is already covered in the WLAN Client module and therefore was removed from MDF function 41. Per different feedback, Bluetooth tethering needed to be referenced in some capacity, so it was added to function 41. Function 41 therefore has gone from "hotspot and USB" to "USB and Bluetooth." Assuming that this change is okay, it's not clear whether the MDM use case guidance should still be to select both options, because the Bluetooth option wasn't there previously.

Flagging this because of that question but also because that function in MDF may end up changing again as Bluetooth gets reviewed and updated. Specifically, if wifi hotspot is configurable as a WLAN Client module function, maybe it makes more sense to have Bluetooth tethering go in the Bluetooth module rather than have that be in MDF while wifi isn't.

[jfisherbah]

Similarly H.2 requires function 34 to be claimed and to include all applicable servers. However, if being a wifi hotspot no longer counts as a "server" in this requirement, it is an option question as to whether this is still required. i.e. what other servers might exist that the MDM needs to be able to configure in this use case? If there are specific ones it would make more sense to list them, and if there aren't any besides hotspot maybe this just gets taken out.

[jfisherbah]

We already reference functions WL-1 and WL-2 as things we can manage from the MDM so another possibility would be to add WL-3 as a selectable option to cover the potential for hotspot configuration and then have the use case say to select it.