RE: transport mappings capability

["Rob Enns" <rpe@juniper.net>]

> > I guess your capability proposal is to solve the problem 
> where I might
> > prefer to talk to you using another transport protocol. Having a
> > capability wouldn't hurt in this case, but this is more of 
> a corner case
> > then being able to talk in the first place.
> >   
> 
> There is no corner case.   It is just a need to discover all the
> mappings that an agent will support.
> 
> A manager can always talk to an agent over the default mapping (SSH).
> The issue is whether a standard capability, standard data model,
> or proprietary mechanism be used to find out if any other mappings
> are supported.  

I wonder if it would be used though. Would a manager connect to
an agent over SSH, discover that the agent supports SOAP, and go
back to use SOAP? Most deployments would know the connection
method by fiat.

Rob

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>