Hi,

I am working from RFC4741/draft-4741bis-00 to develop a compliant
NETCONF implementation and have a question with respect to the
<error-message> element in <rpc-error>.

The <error-message> element is described in section 4.3. as:
     "Contains a string suitable for human display that
      describes the error condition.  This element will not be present
      if no appropriate message is provided for a particular error
      condition.  This element SHOULD include an xml:lang attribute as
      defined in [1] and discussed in [12]."

And just before the examples in this section the following statement appears:

     "Appendix A enumerates the standard NETCONF errors."


If my NETCONF client sends a frame containing NETCONF protocol level
errors as follow:


<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rpc message-id="106"
     xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
    <edit-config>
        <target>
            <running/>
        </target>
        <default-operation>splurge</default-operation>
        <test-option>set-then-test</test-option>
        <error-option>contemplate-on-error</error-option>
        <mishigas/>
        <config>
           <a-config-subtree operation="merge">
               blah blah blah blah
           </a-config-subtree>
        </config>
    </edit-config>
</rpc>
]]>]]>



If my NETCONF server is constrained by Appendix A, then it will
respond with: (example reply 1)


<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rpc-reply message-id="106" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
    <rpc-error>
        <error-type>rpc</error-type>
        <error-tag>bad-element</error-tag>
        <error-severity>error</error-severity>
        <error-message xml:lang="en">An element value is not correct;
e.g., wrong type, out of range, pattern mismatch.</error-message>
        <error-info>
            <bad-element>default-operation</bad-element>
        </error-info>
    </rpc-error>
    <rpc-error>
        <error-type>rpc</error-type>
        <error-tag>bad-element</error-tag>
        <error-severity>error</error-severity>
        <error-message xml:lang="en">An element value is not correct;
e.g., wrong type, out of range, pattern mismatch.</error-message>
        <error-info>
            <bad-element>test-option</bad-element>
        </error-info>
    </rpc-error>
    <rpc-error>
        <error-type>rpc</error-type>
        <error-tag>bad-element</error-tag>
        <error-severity>error</error-severity>
        <error-message xml:lang="en">An element value is not correct;
e.g., wrong type, out of range, pattern mismatch.</error-message>
        <error-info>
            <bad-element>error-option</bad-element>
        </error-info>
    </rpc-error>
    <rpc-error>
        <error-type>rpc</error-type>
        <error-tag>unknown-element</error-tag>
        <error-severity>error</error-severity>
        <error-message xml:lang="en">An unexpected element is
present.</error-message>
        <error-info>
            <bad-element>mishigas</bad-element>
        </error-info>
    </rpc-error>
</rpc-reply>
]]>]]>


However, there is more specific information available that my NETCONF
server can provide with respect to the simple types having an
enumeration constraint- <default-operation>, <test-operation> and
<error-option>: (example reply 2)


<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rpc-reply message-id="106" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
    <rpc-error>
        <error-type>rpc</error-type>
        <error-tag>bad-element</error-tag>
        <error-severity>error</error-severity>
        <error-message xml:lang="en">Value 'splurge' is not
facet-valid with respect to enumeration '[merge, replace, none]'. It
must be a value from the enumeration.</error-message>
        <error-info>
            <bad-element>default-operation</bad-element>
        </error-info>
    </rpc-error>
    <rpc-error>
        <error-type>rpc</error-type>
        <error-tag>bad-element</error-tag>
        <error-severity>error</error-severity>
        <error-message xml:lang="en">Value 'set-then-test' is not
facet-valid with respect to enumeration '[test-then-set, set]'. It
must be a value from the enumeration.</error-message>
        <error-info>
            <bad-element>test-option</bad-element>
        </error-info>
    </rpc-error>
    <rpc-error>
        <error-type>rpc</error-type>
        <error-tag>bad-element</error-tag>
        <error-severity>error</error-severity>
        <error-message xml:lang="en">Value 'contemplate-on-error' is
not facet-valid with respect to enumeration '[stop-on-error,
continue-on-error, rollback-on-error]'. It must be a value from the
enumeration.</error-message>
        <error-info>
            <bad-element>error-option</bad-element>
        </error-info>
    </rpc-error>
    <rpc-error>
        <error-type>rpc</error-type>
        <error-tag>unknown-element</error-tag>
        <error-severity>error</error-severity>
        <error-message xml:lang="en">An unexpected element is
present.</error-message>
        <error-info>
            <bad-element>mishigas</bad-element>
        </error-info>
    </rpc-error>
</rpc-reply>
]]>]]>


The above error-message text is taken directly from the SAX/DOM parser
errors based upon the NETCONF schema and appear to be more useful than
the error-message text contained in Appendix A.

Now, in order to be compliant wih respect to 4741/4741bis does my
NETCONF server for errors occurring at the NETCONF protocol level need
to constrain eror-message text to that contained in Appendix A?  Or,
can the error-message text be as in example reply 2?  (Or even a
concatenation of Appendix A error-message text with the text in
example reply 2?)

Regards,

Mark