Re: [Isms] Ismssnmp: URI scheme transport extensions

[Juergen Schoenwaelder <j.schoenwaelder at jacobs-university.de>]

On Mon, Jul 27, 2009 at 10:47:36AM +0200, David Harrington wrote:

> What is the use case that requires including this info in the URI?

We have no interoperable way to write down and to pass around how you
access SNMP resources. The snmp: service URI format does address this
but the definition is incomplete.

I have a command line tool that uses snmp: URIs instead of collections
of command line options to specify to which agent you talk to - and it
also generates such URIs if you want to. Having a compact serialized
notation to pass around this information is helpful. RFC 4088 was
actually created because some MIB modules had a need to indicate in a
compact way (= one MIB object) where a management application can be
found without having to go through multiple related MIB tables.

Cut'n'paste of URIs really works great compared to cut'n'paste of
collections of MIB objects. ;-)

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>