Re: Separation of protocol and information model

[Bobby Krupczak <rdk@krupczak.org>]

Hi!

>"Allen, Keith" writes:
>>Our
>>preference was to design a very simple protocol and develop some of the more
>>complicated features (killing sessions, locking, copying and validating
>>configurations, etc.) in a standard MIB along with a standard equipment
>>model, interface models, and so on.
>
>If your preference is for a simple protocol and complex mibs, why
>are you looking at anything besides snmp?

I cant speak for Keith . . . 

Perhaps because SNMP is a good monitoring protocol but sucks for bulk
configuration (and a host of other configuration-related activities.)

Bobby

--
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/>