Subject: RE: NETCONF inconsistency in get-config/source

From: "Rob Enns" <[email-masked]>
Date: Tue, 6 Dec 2005 12:53:16 -0800

Thanks. The WG had previously decided that the <source> element is mandatory in <get-config>, I'll strike the 2nd sentence in the <source> parameter description.
 
Rob

________________________________

	From: [email-masked] [mailto:[email-masked]] On Behalf Of Stig Solberg (LN/EAB)
	Sent: Thursday, November 24, 2005 10:55 PM
	To: [email-masked]
	Subject: NETCONF inconsistency in get-config/source

	Hi, 
	there seems to be an inconsistency in how the source element is specified for get-config 
	in text (page 31) and how it it is specified in the NETCONF schema. 
	In the text section it is defined as follows. That is, it seems to be an optional 
	element 
	     source: 

	         Name of the configuration datastore being queried, such as 
	         <running/>.  If this element is unspecified, the <running/> 
	         configuration is used. 

	But in it NETCONF schema it is specified as being an mandatory element since 
	minOccurs by default have the value 1: 
	     <xs:complexType name="getConfigType"> 
	       <xs:complexContent> 
	         <xs:extension base="rpcOperationType"> 
	           <xs:sequence> 
	             <xs:element name="source" 
	                         type="getConfigSourceType"/> 
	             <xs:element name="filter" 
	                         type="filterInlineType" minOccurs="0"/> 
	           </xs:sequence> 
	<cut> 

	Regards, 
	Stig Solberg 
	Software Engineer              Voice: +46 (0)31 747 3251 
	Ericsson AB                    Fax  : +46 (0)31 747 6033 
	Göteborg, Sweden               Email: [email-masked]