RE: Netconf operation definitions

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

> > 1) The current get-config definition for source says:
> >
> > "source:
> >
> >         Name of the configuration datastore being queried, such as
> >         <running/>.  If this element is unspecified, the <running/>
> >         configuration is used."
> >
> > The definition for get-config the XSD includes element 
> source which is 
> > of type rpcOperationSourceType. One of the choices is 
> "config" which 
> > is config-inlineType
> >
> >     <xs:complexType name="rpcOperationSourceType">
> >       <xs:choice>
> >         <xs:element ref="config"/>
> >         <xs:element ref="config-name"/>
> >         <xs:element ref="url"/>
> >       </xs:choice>
> >     </xs:complexType>
> >
> > My suggestion would be for the XSD definition to be modified to not 
> > allow this  since a definition change can be made to 
> enforce what the 
> > text says.
> 
> I think the text and XSD are both wrong here, since we changed the 
> <get-config>
> operation to add the <filter> parameter.  It doesn't make 
> sense for the 
> source
> to be inline configuration XML (choice=config).  That made 
> sense before 
> we moved
> the filter specification to its own parameter. 
> 
> The 'source' parameter needs to be changed to 'target', and
> the type is changed from rpcOperationSourceType to 
> rpcOperationTargetType.

I'd prefer to use a new type, rather than rename source to target,
since it seems like one should "get" from a "source". Cool?

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