[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FW: I-D ACTION:draft-weijing-netconf-interface-00.txt
>>>>> Chen, Weijing writes:
Weijing> I guess to summarize our philosophy, I would say we think
Weijing> that a management protocol should be divided into two parts,
Weijing> a basic set of management "operations" and an "information
Weijing> model" that defines the manageable capabilities of a device.
Weijing> Probably no argument there. Where I think we may begin to
Weijing> disagree, however, is that we feel the management operations
Weijing> should be as simple and flexible as possible, with the
Weijing> information model being the focus for defining the complexity
Weijing> of the device. Wherever possible, our preference would be to
Weijing> make the protocol simpler and the information model more
Weijing> complex.
The question is where you draw the line between protocol primitives
and what is being done in the information model. SNMP is a well known
example where the desire to stick to the very basic set of protocol
primitives and to do everything else in the data models led to thinks
like RowStatus which at the end have been more expensive then adding
create/delete operations to the protocol.
From a very abstract viewpoint, I believe that a data-centric or
object-centric management protocol must support the following set of
essential management protocol primitives:
o get, set, create, delete
o search (or at the very least iterate)
o lock, unlock, commit, rollback
o notify
o execute or invoke an operation
Introduction of additional primitives should be done with great care
because either (a) the abstract model above is wrong and needs to be
corrected or (b) the new primitives are solely justified because they
allow for significant optimizations.
/js
--
Juergen Schoenwaelder International University Bremen
<http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany
--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>