-------
For Inception Review
--------
seb-0	Assuming that the future of network configuration is
	NWAM-only, and that the existing mess that comprises
	network/physical:default will eventually go away, are there
	design, architectural, or even scoping constraints that this
	project imposes on other current and future project?  For
	example, I know of a current larval project planning on
	replacing ifconfig and /etc/hostname* files as an IP interface
	configuration tool.  If nwamcfg and its GUI are the future,
	should that project stop what it's doing?

seb-1	How does the system behave when configuration that is managed
	by NWAM changes while NWAM has a given profile activated?
	Does those changes in configuration get silently blown away
	when NWAM activates a different profile, or does that
	configuration become part of the currently activated profile?

-------
Post Inception Review
-------

jmp0:	I have an uncomfortable lingering impression that NWAM
	equates to a completely disruptive change in how networking
	configuration is performed (was /etc/files, SMF services and
	related admin commands, now is NNWAM cli/gui and
	NWAM-library-aware commands only).  This is problematic for
	two reasons:  It invalidates a lot of existing sysadmin
	knowledge, scripts and tools, and it means that the networking
	system can't be extended without first extending NWAM (i.e., we
	can't use vlans now because NWAM doesn't support vlans yet,
	extrapolate for honeycomb and other new technologies...)
------
Commitment Review
------
gww-99	Nit, just a reminder that it seem auditing will be needed in
	netcfgd and likely changes to nwamd.  Please coordinate with
	the Audit project team.  Some of the requirements are in the
	process of changing.

djr-1	I concur with jmp0 and I'm afraid that NWAM is going to create a
	network administration that makes life easier for those that point
	and click with their mouse and are happy but will cause much
	consternation if it defaults to on for server installations.
	Feedback from professional systems administrators has indicated
	that they dislike for the "lets bury network interface admin in
	a directory tree under /etc, somewhere" - as Linux does.

djr-2	If I'm doing a jumpstart install today, I can use /etc/hostname.*
	and friends to deliver files as part of the installation that
	completely configure my host for the network. If the new default
	install is with NWAM active and these legacy files are no longer
	used, how is this not a regression for me? Where will I find
	documentation on all of this? (Nothing in the materials seems
	to tell me how to do this?)

djr-3	Why is only /etc/hosts managed by NWAM?
	Why have the others (services, networks, netmasks, inetd.conf,
	ntp.conf) been forgotten?
	Is this proposal complete if it is only managing a few of
	these files and not all?

seb-2	One current architectural issue with NWAM Phase < 1 is the
	fact that links that NWAM doesn't support aren't configured
	at boot time even when the user doesn't want NWAM to touch
	them.  How does Phase 1 handle that?