[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Separation of protocol and information model

To: "Allen, Keith" <Keith_Allen@labs.sbc.com>
Subject: Re: Separation of protocol and information model
From: Phil Shafer <phil@juniper.net>
Date: Thu, 04 Sep 2003 09:49:34 -0400
Cc: "'Bobby Krupczak'" <rdk@krupczak.org>, netconf@ops.ietf.org
In-reply-to: Your message of "Thu, 04 Sep 2003 08:35:06 CDT." <905A1C4ABF353F4C8CC16FA9F53DD0D603800966@trimail2>

"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?

Thanks,
 Phil

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

References:
- RE: Separation of protocol and information model
  - From: "Allen, Keith" <Keith_Allen@labs.sbc.com>

Prev by Date: RE: Separation of protocol and information model
Next by Date: Re: Separation of protocol and information model
Previous by thread: RE: Separation of protocol and information model
Next by thread: RE: Separation of protocol and information model
Index(es):
- Date
- Thread