COPS gives every 'table' its own create and destroy 'method'. Discussion on where to bind operations to. Side-effects are still allowed. Put operations inside table definitions, and allow the annotation mechanism to add operations in separate documents to existing tables. Reboot turns out to be a table after all.
Enumerations are sufficient as error codes.
We assume 'at most once' or better semantics for operation invocations. The invoker can tell that the invocation actually succeeded. Need to specify the relevant ASIs. Small example MIB with operations. Use this to get implementation experience.