RE: the future of SNMP
"Glenn Waters" <[email protected]> Fri, 28 Feb 2003 08:59:12 -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_01C2DF31.92A8A996 Content-Type: text/plain > -----Original Message----- > From: Bob Natale [mailto:[email protected]] > Sent: Thursday, February 27, 2003 18:40 > To: [email protected] > Subject: Re: the future of SNMP [...] > 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. Cheers, /gww ------_=_NextPart_001_01C2DF31.92A8A996 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.2655.35"> <TITLE>RE: the future of SNMP </TITLE> </HEAD> <BODY> <BR> <BR> <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: Thursday, February 27, 2003 18:40</FONT> <BR><FONT SIZE=3D2>> To: [email protected]</FONT> <BR><FONT SIZE=3D2>> Subject: Re: the future of SNMP</FONT> </P> <P><FONT SIZE=3D2>[...]</FONT> </P> <P><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> </P> <P><FONT SIZE=3D2>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.</FONT></P> <P><FONT SIZE=3D2>Cheers, /gww </FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01C2DF31.92A8A996--