Re: [netconf] Error to make a NETCONF action call without including an action node?

["Reshad Rahman (rrahman)" <[e-mail]>]

Jason, my understanding is that an error should be returned since the input leaf has mandatory true.

Interestingly, the following text (for rpc) is missing from the action section. Oversight or on purpose?
https://tools.ietf.org/html/rfc7950#section-7.14.2
   If a leaf in the input tree has a "mandatory" statement with the
   value "true", the leaf MUST be present in an RPC invocation.

I’d expect this error:
https://tools.ietf.org/html/rfc6241#appendix-A
   error-tag:      missing-attribute
   error-type:     rpc, protocol, application
   error-severity: error
   error-info:     <bad-attribute> : name of the missing attribute
                   <bad-element> : name of the element that is supposed
                     to contain the missing attribute
   Description:    An expected attribute is missing.

Regards,
Reshad.

From: netconf <[e-mail]> on behalf of "Sterne, Jason (Nokia - CA/Ottawa)" <[e-mail]>
Date: Thursday, April 30, 2020 at 11:06 AM
To: "[e-mail]" <[e-mail]>
Subject: [netconf] Error to make a NETCONF action call without including an action node?

Hi all,

If we have this YANG model (omitting some details):

   module test {
       container foo {
         leaf bar { type uint8; }
         action reset {
           input {
             leaf reset-at {
               type yang:date-and-time;
               mandatory true;
              }
            }
            output {
              leaf reset-finished-at {
                type yang:date-and-time;
                mandatory true;
              }
            }
         } // action reset
       } // container foo
   } // module

Should NETCONF return an error (which one?) for this request or would the server simply do nothing an return "OK" (like doing a get-data on a non-existent list entry) ?

     <rpc message-id="101"
          xmlns="urn:ietf:params:xml:ns:netconf:base:1..0">
       <action xmlns="urn:ietf:params:xml:ns:yang:1">
         <foo xmlns="urn:example:test">
         </foo>
       </action>
     </rpc>

Jason