Dan, Thank you for your comments. See inline:
>> * Vanity naming >> >> Today, the network names are tied to the underlying network hardware >> (e.g., bge0, ce0). Because configuring the system always requires >> network interface names to be stored in a wide range of configuration >> files, being able to give a meaningful and consistent vanity name to >> network interfaces will make network administration much easier. More >> importantly, vanity naming will prove especially useful for machine >> migration and Dynamic Reconfiguration. >> > I wonder if there is a better way to word this paragraph. When I read > it the first time, I thought "How would giving an interface a meaningful > vanity help with interface names scattered through a wide variety of > files? Wouldn't we have to keep track of each instance in each file?". > After thinking about it, I could see how having a vanity name would > help (i.e. indirection). It feels like you're missing a step in > explaining how vanity naming would be helpful. > Right, vanity naming does not help to track those configuration files. But carefully-chose names can help to make the configuration meaningful. Is that not clear? Which step do you think I missed? >> - By what criteria will you judge its success? >> >> The project will be complete once the following requirements have >> been met: >> >> * Must provide a consistent model for network interface administration: >> >> - All network interfaces are administrated by the same set of >> commands. >> > > Even third party interfaces like Syskonnect? > Anything special of the Syskconnect interfaces? I would think they are just legacy devices which can be managed by softmac then administered by dladm. >> - All network interfaces support all features that specific hardware >> can support. >> > > Same as above, even third party interfaces? > Same as above. >> 8. Reliability, Availability, Serviceability (RAS) >> >> - Does the project make any material improvement to RAS? >> >> No. >> > > Since more interfaces can be configured as aggregations, wouldn't we be > improving Solaris's RAS? > Good point. I will add it. >> - Is system or subsystem security compromised in any way if your >> project's configuration files are corrupt or missing? >> >> No. >> > > What if someone hand edits /etc/datalink.conf to change some > configuration information? I can't think of any potential exploits off > the top of my head, but if there's a potential exploit there, someone > will find it. > Hmm, I am not expert on security and I cannot think how security would be compromised. Hope Seb and Meem know better in this subject. >> - Is the project internationalized and localized? >> >> N/A >> > > What happens if a user wants to name an interface using characters that > aren't in 7-bit US-ASCII? Is that even possible? A few examples: > > - a Chinese user naming an interface using a Chinese character set > (like Big5) > - Spanish users typing names that include tildas or accent marks in > a UTF-8 environment > - Russian users wanting to use names with Cyrillic characters? > Meem answered this. Other typos are fixed. Thanks - Cathy
