Re: A few potential requirements

[Randy Bush <randy@psg.com>]

>> I think having a CLI command that brings up an
>> *optional* menu-driven interface is okay.
>     
> I guess I agree, and there are certainly kinds of devices that I like to
> have menus for, but I also think we need to be careful about making
> suggestions to vendors which are beyond what we _really really want them
> to do_, since it may encourage them to invest effort in menu stuff, rather
> than in a uniform CLI.

thank you.  let's keep a hard eye on simplicity and must-haves.

> I agree, basically, but think we need a little more discussion.  What
> you say is definitely correct and important with respect to big iron.
> What about small boxes, like CPE?  End-users won't have serial cables
> and terminals, and may really need web access enabled by default.

as you imply, this varies with the marker.  and the vendor probably knows
who their market is.  but one should be easily able to know what holes are
open and be easily able to close the unwanted ones.

> Specifically, do you mean that it should be on by default when a box
> comes from the factory (I assume we have consensus on that), or that it
> should be _impossible to disable_?  I think I'd agree with the latter as
> well, but it's likely to be more controversial.

on many devices, the craft interface is often the most exposed and the least
protected/protectable.

randy