Re: [Isms] Ismssnmp: URI scheme transport extensions

["David Harrington" <ietfdbh at comcast.net>]

Hi,

I don't use URIs in my work, so I may be overlooking why we need this.

Why do we need to specify the transport in the URI? We are already
specifying port 5161, which is snmp/ssh.

Why do we need to specify the securityModel in the URI? It is already
specified in the SNMP header.

If the purpose is to specify to the URI user which transport should be
used, and which secmodel should be used, then the information is
incomplete. Wouldn't we need to specify the securityName,
securityLevel, and so on as well? and maybe the ssh username to use?
In fact, wouldn't we need to specify everything that could be
specified in the set of tables in the notification-mib?

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

dbh

> -----Original Message-----
> From: isms-bounces at ietf.org [mailto:isms-bounces at ietf.org] On 
> Behalf Of Wes Hardaker
> Sent: Monday, July 27, 2009 10:13 AM
> To: isms at ietf.org
> Subject: Re: [Isms] Ismssnmp: URI scheme transport extensions
> 
> >>>>> On Mon, 27 Jul 2009 09:29:24 +0200, Juergen 
> Schoenwaelder <j.schoenwaelder at jacobs-university.de> said:
> 
> JS> snmp://tester5 at example.com:5161;transport=ssh
> JS>                                 ^^^^^^^^^^^^^^
> JS>                                 new
> 
> I think you're still missing an important element, namely the
> securityModel.  No where above does it specify TSM anywhere so I
don't
> think it's complete as is.
> 
> [I think that's likely missing from 4088 as well, for that matter,
> regardless of whether it's updated for transport specific 
> concerns; the
> fact that it's excluded from the original document is sort of 
> odd in my
> opinion in the first place since we're obviously to the point where
> multiple security models exist (although they've existed long 
> before this)]
> 
> -- 
> Wes Hardaker
> Cobham Analytic Solutions
> _______________________________________________
> Isms mailing list
> Isms at ietf.org
> https://www.ietf.org/mailman/listinfo/isms
>