|
Good point and we generally speaking consider them all! Plus time frame pressure to finish the standard so people can start supporting it. I think we need to come up with the goals for XMLconf, and I don’t think XMLconf will fix all the problems SNMP has. But XML is a nice alternative to CLI/TL1/syslog/configuration file. I am pretty sure we will see mix of implementation for a while and eventually the fittest shall survive!
-faye
-----Original Message-----
Glenn >> Certainly for your problem set, simple to implement and test could be a higher priority. That may not be a priority for other implementations. Not everyone has a gigahertz processor, and even if they do most have the processor to deal with the bytes on the wire and not for network management functions. Hey I still want this to manage my toaster (just joking -- but that was a touted benefit of SNMP way back). Glenn>> One of the biggest reasons that standards are hard is that one person's high priority item is someone else's "I don't care".
I thought that I will got this kind of response. Now when there is conflict of design because of different priority, what are we going to do? "Simple to implement and test, flexible to change" gang get one set of specifications, "efficiency" gang get another set? Or a mix of everything to please everyone and end up please no one? Or a real smarter design can indeed please everyone? Or can we scope the work to focus on a particular set of priorities?
-- Weijing Chen
|