[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SNMP improvements
- To: "Harrington, David" <dbh@enterasys.com>
- Subject: Re: SNMP improvements
- From: Wes Hardaker <wjhns1@hardakers.net>
- Date: Fri, 19 Sep 2003 11:11:22 -0700
- Cc: <mibs@ops.ietf.org>
- Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEXotKX87e8eDA4GAQbQgmlzNycHAwizYkruzul2AAACaUlEQVR4nFXUTW/jIBAGYFI56jWutuq1S9b2dddW6dWtQFxbq4jzwq73Glmg+fv7DiT9QJGS+GEGhiER67TWEQ5CtOeh21ZcIIbmOPq5QvMZYlyV6u+/gsJLTSrGIL/CxEPxQuPAcP0JYlQsq3x5B3UJmUaEyB6yZ+CQ+pwXCzKsbXtbIhg4KtZypPz+AVGtlxH69c87qAqRY6Rc5QUmZMGeAj+TfVjjUwE1lflKys5JGXpM+V0hltqCJ0qL7Plkft4wRM6lxi5p3Wyy7O7fB8TgtdZivxy5rvAB6wSYhbA9vn+GOCaOEGJRPO2mHgk+q1Chyf0Up3AG0NjhOXI19ogEFziq6M+ZtN3kUZ13NW4qUCprC3CW668C06M5jihON1Vsjq8F1CPJB8LINNeQfscwxUEvAwM5Xghvsq2pBr3hnKhbDIrMS3cBRDx70uS9JW2dy667gM0AbZFFmyvn3GOBGB8wG9kppaSNz357LaCmUdtSny5LU9qeCrglvJmyH20TwkjnXQE0usscIWayCWZJ7OpZ4QbUVGRnhuTub3cMYRk99oSplDIfibzfn0FyXyk7z8XThuvC0P/dGCwee7O8aZJBmh0vPixy0NrYhDaR02aR3W0BbyT6h23OB5Hzybj+DOm5w6XCOZG13p5Oh/bursJVh9S+bBiFnPCDuntpcTH080AO+7GlW1i3bRphBM04dZ2dI6yMLjmGFqnIok/cB1YU8sJAACTeuHOd5+lumQHfDM6KyLqEm4aWkkcc1m4PqBewZxBZOg44lT+aJiexDteewboiVhxAjSHxQwhiYJEdCR6tMN1/uckirDRNbsgAAAAASUVORK5CYII=
- In-reply-to: <6D745637A7E0F94DA070743C55CDA9BAEA9C56@NHROCMBX1.ets.enterasys.com> (David Harrington's message of "Fri, 19 Sep 2003 11:03:56 -0400")
- Organization: Sparta
- References: <6D745637A7E0F94DA070743C55CDA9BAEA9C56@NHROCMBX1.ets.enterasys.com>
- User-agent: Gnus/5.1003 (Gnus v5.10.3) XEmacs/21.5 (brussels sprouts, linux)
>>>>> On Fri, 19 Sep 2003 11:03:56 -0400, "Harrington, David" <dbh@enterasys.com> said:
David> The NM Workshop identified a number of long-term goals and
David> which technologies were preferred by the operators to get us
David> there. I recommend we take RFC3535 as a starting point and
David> chart a course forward, with long term goals and a strategy of
David> developing the necessary technologies to reach those goals.
David> I'm willing to help drive this effort and/or help edit and review
David> documents.
Ok, sounds like a good informational RFC. Note: it was needed last
year, so its already late ;-)
So if we're at:
SNMP <----------> We're here <-------------------------------> Netconf
We need some concrete suggestions to get us forward (safely). I
listed a bunch in my presentation in SF and I can reiterate them here.
This is a cut-n-paste of my previous thoughts on the subject:
In order to avoid pain, we MUST:
Move to XML in as short a time frame as possible
Make SNMP last till XML can fill its (size 4) shoes
Switching to XML quickly
We have the starting momentum, but there is much to do:
Security
Data Modeling Language
Data Models
Monitoring
We must start on these NOW
Keeping SNMP alive that last few miles
SNMP has many known problems.
A few things are needed to fill the gap:
SMIv2.1
Bulking Fixes
Security infrastructure utilization
Better Encryption Support
Most importantly, however, what this does not mention is that we need
to get the word spread about *how* we still need to use existing
technologies in the interim. I think it should be formally stated
that in the future one of the goals netconf will be to make use of
pre-existing SMIv2 documents such that it's still a suitable
documentation mechanism for today while we wait for something better.
IE, its the gaps that need documenting for how people should jump over
them.
--
"In the bathtub of history the truth is harder to hold than the soap,
and much more difficult to find." -- Terry Pratchett