RFC 6241, "Network Configuration Protocol (NETCONF)", June 2011

Note: This RFC has been updated by RFC 7803, RFC 8526

Errata ID: 7624
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Jernej Tuljak
Date Reported: 2023-08-31

Section 4.3. says:

     <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
       <rpc-error>
         <error-type>rpc</error-type>
         <error-tag>missing-attribute</error-tag>
         <error-severity>error</error-severity>
         <error-info>
           <bad-attribute>message-id</bad-attribute>
           <bad-element>rpc</bad-element>
         </error-info>
       </rpc-error>
     </rpc-reply>

It should say:

     <nc:rpc-reply xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">
       <nc:rpc-error>
         <nc:error-type>rpc</nc:error-type>
         <nc:error-tag>missing-attribute</nc:error-tag>
         <nc:error-severity>error</nc:error-severity>
         <nc:error-info>
           <nc:bad-attribute>message-id</nc:bad-attribute>
           <nc:bad-element>nc:rpc</nc:bad-element>
         </nc:error-info>
       </nc:rpc-error>
     </nc:rpc-reply>

Notes:

The original error response is referring to the NETCONF messages layer attribute "message-id", which does not belong to any XML namespace. The response is not properly encoding xs:QName values of elements "bad-attribute" and "bad-element" by placing them both into the default XML namespace. Proposed new text (while verbose) ensures that the values are placed into their respective proper XML namespaces.

Report New Errata