perfsonar development work

[Fausto Vetter <>]

Hi,

Thats the point. if you see the following store file, for example, you  
can see community, version...

http://anonsvn.internet2.edu/svn/nmwg/branches/snmp/example_instances/snmp/store.xml

Fausto

Quoting Joe Metzger 
<>:

> Fausto,
> It depends on what you mean by SNMP information.
> There is a significant difference between information gathered by SNMP
> and the information
> necessary to collect that information from the raw devices, ie
> community strings, management
> interface addresses, etc.
>
> So far, I have only seen discussions about sharing the data collected
> by SNMP.  And reasonable
> service architectures could allow a "collect this SNMP MIB from router
> X" request authenticated
> with perfSONAR based authentication to be carried out using a SNMP
> community string that only the
> service actually knows. There is no need to expose the community string
> via the perfSONAR interface,
> and several good reasons not to.
>
> --Joe
>
>
> On Sep 6, 2007, at 8:44 AM, Jason Zurawski wrote:
>
> > Fausto;
> >
> > > Isnt it unsafe to share SNMP Information (like community)   
> > > throughout domains, once normally community for the version 1 of   
> > > SNMP is the only authentication for SNMP? may you give this option  
> > >  on your implementation to user?
> >
> > Again, its up to the individual service deplorer to decide if they   
> > wish to share this information.  At a bare minimum all that is   
> > required to mark data as being SNMP compatible is an eventType.    
> > Other parameters are not required to be listed.
> >
> > -jason



--
Fausto Vetter
NPD/UFSC

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.