RE: the future of SNMP
"Glenn Waters" <[email protected]> Mon, 3 Mar 2003 09:22:03 -0500
| Newsgroups | gmane.ietf.eos |
|---|---|
| Message-ID | <[email protected]> |
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C2E190.42E4575A Content-Type: text/plain I clearly said each MIB requires special code for each MIB. The protocol operation only need special code once. So, you can implement "n" times for "n" MIBs or you can implement once for the protocol ops. /gww > -----Original Message----- > From: Bob Natale [mailto:[email protected]] > Sent: Saturday, March 01, 2003 01:35 > To: Waters, Glenn [CAR:IO47:EXCH] > Cc: [email protected] > Subject: RE: the future of SNMP > > At 2/28/2003:08:59 AM, Glenn Waters wrote: > > Hi Glenn, > > >> Filtering, selection, etc., can be done in the agent > >> via Set-able MIB objects; most of the schemes proposed for MIB- > >> based out-of-band bulkdata/file transfer would work just fine > >> a practical sense. > > > >I have to disagree with the above statement. In a *practical* sense many > of these MIB schemes need special code not only in the agent but also in > the manager. New special code needs to be created for each new MIB that > gets designed to fix some problem. By adding protocol operations a general > solution can be provided that can be implemented just once. > > I can't imagine where you got the idea that anyone would > think that more capable MIBs would not entail support in > both agents and management apps. Ditto for any SNMP > protocol ops changes. > > There is no such thing as a free lunch, as they say...it's > all a matter of whether you want to waste your lunch money > on junk food or something with more nutritional value. > > Cheers, > > BobN ------_=_NextPart_001_01C2E190.42E4575A Content-Type: text/html Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Dus-ascii"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2656.31"> <TITLE>RE: the future of SNMP </TITLE> </HEAD> <BODY> <P><FONT SIZE=3D2>I clearly said each MIB requires special code for = each MIB. The protocol operation only need special code once. So, you = can implement "n" times for "n" MIBs or you can = implement once for the protocol ops.</FONT></P> <P><FONT SIZE=3D2>/gww</FONT> </P> <P><FONT SIZE=3D2>> -----Original Message-----</FONT> <BR><FONT SIZE=3D2>> From: Bob Natale [<A = HREF=3D"mailto:[email protected]">mailto:Bob.Natale@AppliedSNMP= .com</A>]</FONT> <BR><FONT SIZE=3D2>> Sent: Saturday, March 01, 2003 01:35</FONT> <BR><FONT SIZE=3D2>> To: Waters, Glenn [CAR:IO47:EXCH]</FONT> <BR><FONT SIZE=3D2>> Cc: [email protected]</FONT> <BR><FONT SIZE=3D2>> Subject: RE: the future of SNMP</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> At 2/28/2003:08:59 AM, Glenn Waters = wrote:</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> Hi Glenn,</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> >> Filtering, selection, etc., can be = done in the agent</FONT> <BR><FONT SIZE=3D2>> >> via Set-able MIB objects; most of the = schemes proposed for MIB-</FONT> <BR><FONT SIZE=3D2>> >> based out-of-band bulkdata/file = transfer would work just fine</FONT> <BR><FONT SIZE=3D2>> >> a practical sense.</FONT> <BR><FONT SIZE=3D2>> ></FONT> <BR><FONT SIZE=3D2>> >I have to disagree with the above = statement. In a *practical* sense many</FONT> <BR><FONT SIZE=3D2>> of these MIB schemes need special code not only = in the agent but also in</FONT> <BR><FONT SIZE=3D2>> the manager. New special code needs to be = created for each new MIB that</FONT> <BR><FONT SIZE=3D2>> gets designed to fix some problem. By adding = protocol operations a general</FONT> <BR><FONT SIZE=3D2>> solution can be provided that can be = implemented just once.</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> I can't imagine where you got the idea that = anyone would</FONT> <BR><FONT SIZE=3D2>> think that more capable MIBs would not entail = support in</FONT> <BR><FONT SIZE=3D2>> both agents and management apps. Ditto = for any SNMP</FONT> <BR><FONT SIZE=3D2>> protocol ops changes.</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> There is no such thing as a free lunch, as they = say...it's</FONT> <BR><FONT SIZE=3D2>> all a matter of whether you want to waste your = lunch money</FONT> <BR><FONT SIZE=3D2>> on junk food or something with more nutritional = value.</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> Cheers,</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> BobN</FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01C2E190.42E4575A--