[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: What happened to <format> parameter on <get-config>?


Couple of additonal questions...

- Can you provide any further insight into the discussions leading to the decision to use namespaces vs. the format param
- Any plans to provide some examples to clarify this

thanks

Hector


Phil Shafer wrote:
"Steven Berl \(sberl\)" writes:
  
I know we used to have a <format> parameter as part of the <get-config>
operation, and that it got removed in an earlier draft. I can't seem to find
the reason why it was removed, and what alternative has been provided to
allow me to send an additional parameter as part of a <get-config> request.
    

The concensus was that namespaces could be used to determine
the sort of information that was being requested.

<rpc>
  <get-config>  <!-- from memory; caveat xmler -->
    <config>
       <configuration-text xmlns="http://example.com/text/1.0"/>
    </config>
  </get-config>
</rpc>

It does give a richer set of possible configs (and the strings
the describe them), but is a bit uglier.

  
Basically my problem is that the config can be represented in 2 different
ways and I need to tell <get-config> which way to return it. 
    

Same here.  We default to xml and allow the above hook to
get normal text output (ala "show configuration").

Thanks,
 Phil

--
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/>

  

-- 
Hector Trevino
Network Management Technology Group (NMTG)
Cisco Systems Inc.        Voice:  720-875-1369
Suite 400                      
9155 E. Nichols Ave     Fax:    720-875-3014
Englewood, CO             E-mail: htrevino@cisco.com
80112