The conversation continues...this time we came up with several areas that needed a bit of research and synthesis of ideas; each of us has an assignment to do that and report back to this list, so we'll see more follow up soon.
-renee * Locations: should the automatic and no-net locations be read-only, like the automatic ncp? Conclusion: no. We can imagine use cases where the user might want to change the ipfilter rules for the no-net location, for example. There will be an option to restore defaults, though. Problem: what if the user modified the ipf.conf file we provide as part of the no-net location? There's no way to restore the default if the file's been changed. Solution: we can't completely prevent this from happening; but we will deliver "ipf.default" files which will be copied for use by the no-net location. If the user mods that file, there's nothing we can do; but if the location version of the file is changed, the default can still be recovered from that file. * Startup behavior, specifically with respect to locations: section 7.2 is not up-to-date with the current thinking that came out of a mail thread last month "nwamd startup behavior". There's also some concern that the network/location service is overloaded, and/or nwamd is doing too much restarter-style management of that service. Anurag will re-write section 7.2 to reflect the new thinking, and we'll review that via e-mail. * Extensible location properties and the smf template facility: we need to tweak the libnwam support for extensible properties in locations; it's likely consumers will find out about the existence of these via libnwam, but then use libscf to learn template details (e.g. how to display, descriptive text). Renee will take a look at what libscf provides along with Alan's notes on what we need and pull this together. * libnwam: need to clarify the known wlan list manipulation interfaces. Alan has started on this, will update to reflect discussions about BSSID usage and post. * API for events: door vs. libnwam? We need to provide details about how this works. Michael has been working on this and will write up some notes.
