RE: [midcom] SNMPv3 as MIDCOM protocol: Opinions?

"Wijnen, Bert (Bert)" <[email protected]>
Newsgroups gmane.ietf.snmpv3
Message-ID <F74EF3316D9CD4118D8400508BAEDCAA07A5A024@nl0006exch001u.nl.lucent.com>
I don;t have the stats, but remembering the implementation I did
a few years back, I see no problem with a number of transactions
per minute. Many SETs per second might become problematic,
depending on the complexity of the SETs and what a SET
would cause in underlying work and such.

Thanks,
Bert 

> -----Original Message-----
> From: Harrington, David [mailto:[email protected]]
> Sent: vrijdag 6 december 2002 21:10
> To: [email protected] (E-mail)
> Subject: FW: [midcom] SNMPv3 as MIDCOM protocol: Opinions?
> 
> 
> Hi,
> 
> Does anybody have any stats regarding the processing power 
> required for SNMPv3?
> 
> dbh
> 
> -----Original Message-----
> From: Eric Burger [mailto:[email protected]]
> Sent: Friday, December 06, 2002 10:48 AM
> To: Martin Stiemerling
> Cc: [email protected]
> Subject: RE: [midcom] SNMPv3 as MIDCOM protocol: Opinions?
> 
> 
> My bad feeling?  Performance.
> 
> I can see SNMPv3 working for a residential or SOHO gateway, 
> where there will be a few transactions per day.
> 
> I might be able to see SNMPv3 working for a small enterprise 
> gateway, where there will be a few transaction per hour.
> 
> I can't imagine using SNMPv3 SETs for a large enterprise or 
> inter-service provider gateway, where there will be a number 
> of transactions per minute.  We've done the math, and you 
> need a LOT of processing power to support such a rate.
> 
> > -----Original Message-----
> > From: Martin Stiemerling [mailto:[email protected]]
> > Sent: Thursday, December 05, 2002 9:24 AM
> > To: [email protected]
> > Cc: [email protected]
> > Subject: [midcom] SNMPv3 as MIDCOM protocol: Opinions?
> > 
> > 
> > [please keep me in the recipient list, since I'm not subscribed to 
> > snmvp3 list]
> > 
> > Hi,
> > 
> > as you may have heard: the MIDCOM WG is currently doing a protocol 
> > evaluation which protocol to use as the MIDCOM protocol. SNMPv3 is 
> > amongst these candidates (diameter, cops(-pr), megaco).
> > Would you strongly recommend to use SNMPv3 as the MIDCOM protocol 
> > without having a bad feeling? Actually there are only a few 
> > pro and cons 
> > discussed so far.
> > 
> > Thanks in advance
> > Martin
> _______________________________________________
> midcom mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/midcom
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.