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

["Steven Berl \(sberl\)" <sberl@cisco.com>]

> -----Original Message-----
> From: owner-netconf@ops.ietf.org 
> [mailto:owner-netconf@ops.ietf.org] On Behalf Of Phil Shafer
> Sent: Monday, March 14, 2005 5:40 PM
> To: sberl@cisco.com
> Cc: netconf@ops.ietf.org
> Subject: Re: What happened to <format> parameter on <get-config>? 
> 
> "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>

This actually isn't value by the XSD. It would need to be:

<rpc>
   <get-config>
     <source>
        <config>
          <configuration-text xmlns="http://example.com/text/1.0"/>
        </config>
     </source>
  </get-config>
</rpc>

I didn't see the <config> element available inside of the <source> as a
choice before. The problem with this is that I can't specify both a <config>
and a <config-name> in the same <source> element. This "format specifier" or
"implementation specific parameter" doesn't really seem like it belongs in
the <source> anyway. I'd think that it should be child of <get-config>, a
part of the sequence that includes <source> and <filter>. 

Any chance that we can fix this? Put <config> as a child of <get-config>
instead of a child of <source>?

-steve

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

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