OPS-NM status

[Steve Feldman <feldman@twincreeks.net>]

The OPS-NM minutes from Salt Lake City are available at
    http://www.ietf.org/proceedings/01dec/minutes/OPS-NM.HTM

and the latest draft (from before the meeting) is at
    http://www.ietf.org/internet-drafts/draft-ops-operator-req-mgmt-01.txt

During the meeting we had consensus that this effort is worthwhile,
and that we should go over each of the points in the draft to
decide whether to keep, modify, or drop them.

We would like to have a version of the draft ready for last call
before Minneapolis, and don't currently plan to have another BOF there.

To start discussion again, here's the list from Bill's slides
(numbered for my convenience):

1. ASCII communications.

2. One syntax and vocabulary for all common functions.

3. Console/craft/serial port required.

4. Secure and authenticated in-band interactive and batch communications
must be available.

5. Device must not drop characters from input communications stream.

6. Paging of output must be present by default and overridable per
session.

7. Devices must at least present the appearance of a file system.

8. Devices must not naively autoconfigure.

9. Reads and writes must utilize the same name-space.

10. Devices must save and export their complete configuration by
default.

11. Devices must support a configuration display mode which makes
all assumed and default values visible.

12. Devices must support both line-by-line and bulk commit, with
syntax checking and rollback either line-by-line or bulk, as
appropriate to the mode.

13. Devices should support a ?syntax check only? mode, bulk or
line-by-line, which only reports errors and does not actually apply
changes to the configuration.

14. Simple versioned numeric result codes should precede human-readable
output wherever useful and appropriate.

15. Devices should immediately log the source and details of access
attempts, configuration changes, and operator-initiated state
changes to one or more external devices.

16. Operators must be able to create configuration snippet templates
and apply them individually or as new defaults, overriding vendor
defaults.

17. Operators must be able to apply configuration snippets to ranges
or lists of instances, not just one-by-one.

18. In-band authentication methods like RADIUS and Kerberos must
be backed up with locally-stored passwords for disconnected use.

19. Devices must support user and role accounts at multiple
permissions levels with different read/write privileges.

20. Divergence between human and machine interfaces:
    As late as possible
    Tabular versus pair-value
    When output can't be parsed w/o reference to previous line?
    Necessary at all?

So to start off, let's hear if you think any of these _don't_ belong
in the draft.

Cheers,
	Steve