Re: Fwd: Re: A few potential requirements

[Joe Provo <crimson@gweep.net>]

re: 03 & 04. strong echo of Adi's statement. if the vendor only supplied
compiled configurations, they should be required to decompile when speaking
the 'Infrastructure Management Protocol' (regardless if that is to humans
or databases or scripts or...)

re: 05 [SMTP-alike]. I know the intent is not o develop such a protocol
here, but I need to toss in:
- in addition to vebosity switch (rather than binary, I would encourage
  suggesting at least the triad of 'none'/'machine-only'/'machine+human'.
  paranoid sites would undoubtable prefer to leave minimal feedback,
  engaging error/success responses only when they deem needed.
- similarly, if recommending a help, that should not be hard-coded into a
  spec as some folks will want it off (for same reasons as above),
  independant of verbosity.
- one may wish to recommend ESTMP-aline rather than SMTP-alike, and open
  the can of worms of capability negotiation.


-- 
 crimson@sidehack.gweep.net * jprovo@gnu.ai.mit.edu * jzp@rsuc.gweep.net
             RSUC / GweepNet / Spunk / FnB / Usenix / SAGE