NWAM Design Summit AIs & Qs

AI ID	Description	Owner	Status	Notes
1	Temporary state: follow up with meem and mws regarding conflicting views; choose one approach.	Max	Done
2	Verify with David Bustos that enhanced smf profiles will provide functionality needed to represent temporary instances (non-persistent config created by admin) in the repository. Only required if the answer to AI:1 is "yes, we'll include temp state in the repository."	rld
3	Define Automatic and No-net Locations. Depends on AI:7.	mph
4	Write up thoughts on how we deal with tunnels.	rld
5	Specify how libnwam uses snapshots (mostly document what's already been implemented).	alan
6	Need more specific problem statement for link renaming, and input from folks outside the team (clearview/uv and smf folks in particular).	max
7	Define "hardwired" Location properties.	mph
8	Define library structure and relationships (libnetadm, libnwam, libdladm).	alan
9	Complete API, including generic transaction support.	alan
10	Update gate to use loc instead of env in libnwam function names.	jan	done
11	Design fix for RFE 6219893 (allow non-priv users to do dladm show cmds).	mph
12	Sync with GWW on state of workstation owner proposal, figure out if resources are available to implement this.	mph
13	Can workstation owner role create secure objects?	mph
14	Update p1spec/daemon to indicate that link state change notes come from libdlpi notifications, not routing socket.	rld	done
15	Specify NO_MAGIC event and expected responses from GUI.	mph
16	Write up multiple state machine design.	mph/rld
17	Review/update cold start behavior (p1spec/daemon) in light of new service/repository layout and update as needed.	rld
18	State machine needs to recognize DL_NOTE_LINK_{UP!DOWN} notifications from wifi links as indication of successful connection to a wlan.	mph/rld
19	Document SMF big picture; depends on much of the other work defined here.	rld

Question ID	Description	Owner	Status	Notes
1	Define semantics (ordering, how updated in non-nwam case) of known/preferred wlan list that's stored in repository and shared by all policy engines.	mph
2	How is keying material created in non-nwam case? How are non-nwam- created secobjs mapped to wlans?	mph
3	Need alternative to the requirement that ip be plumbed on a wifi link before connecting to a wlan.	alan
4	How do the parts of the network/physical:default start script that are not link or interface specific get done? Examples are the dladm up-aggr call and the hypervisor setup).	rld
5	How are v4 vs. v6 details of ip ncu config represented?	rld
6	Define policy-engine property group to advertise what the policy engine supports.	alan
7	Keeping SMF state in sync with link state: what's driving the change, who does it, and what changes are made?	max
8	What happens when admin-created persistent config conflicts with existing config (which has been temporarily removed, but still exists in the repository)?	max
9	What does nwam do when it encounters link types it can't handle in the repository? Can we make nwamd itself support all link types now, and just omit the UI support in phase 1?	rld
10	How does nwamd learn about the creation of non-phys links (typically done via dladm)? Use FEM to monitory changes to the /net dir? Is there a more direct way?	mph
11	Replace network/loopback with network/ip:lo0?	alan
12	Can we make smf network services more stable?	mph
13	How does profile upgrade work?	alan

NWAM Design Summit AIs & Qs

Labels