[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Additional RFC Editor Note for draft-ietf-netconf-prot-12
Hi,
This is an important bug fix for the netconf XSD.
The current definition does not allow for an empty node
in 3 places, which contradicts normative text in the
rest of the document.
There are 4 instances of the word 'restriction', which
need to be changed to the word 'extension':
------------------------------------------------------
draft-ietf-netconf-prot-12.txt, bottom of page 80:
OLD:
<!--
Type for <config> element
-->
<xs:complexType name="configInlineType">
<xs:complexContent>
<xs:restriction base="xs:anyType"/>
^^^^^^^^^^^
</xs:complexContent>
NEW:
<!--
Type for <config> element
-->
<xs:complexType name="configInlineType">
<xs:complexContent>
<xs:extension base="xs:anyType"/>
</xs:complexContent>
------------------------------------------------------
draft-ietf-netconf-prot-12.txt, bottom of page 80:
OLD:
</xs:complexType>
<!--
Type for <data> element
-->
<xs:complexType name="dataInlineType">
<xs:complexContent>
<xs:restriction base="xs:anyType"/>
^^^^^^^^^^^
</xs:complexContent>
</xs:complexType>
NEW:
</xs:complexType>
<!--
Type for <data> element
-->
<xs:complexType name="dataInlineType">
<xs:complexContent>
<xs:extension base="xs:anyType"/>
</xs:complexContent>
</xs:complexType>
------------------------------------------------------
draft-ietf-netconf-prot-12.txt, top of page 81:
OLD:
<xs:complexContent>
<xs:restriction base="xs:anyType">
^^^^^^^^^^^
<xs:attribute name="type"
type="FilterType" default="subtree"/>
</xs:restriction>
^^^^^^^^^^^
</xs:complexContent>
</xs:complexType>
NEW:
<xs:complexContent>
<xs:extension base="xs:anyType">
<xs:attribute name="type"
type="FilterType" default="subtree"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
--
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/>