ok element

[Andy Bierman <ietf@andybierman.com>]

Hi,

From prot-10, sec 4.4:

 The <ok> element is sent in <rpc-reply> messages if no error occurred
  during the processing of an <rpc> request.

And the schema for this bit:

   <xs:complexType name="rpcReplyType">
      <xs:choice>
        <xs:element name="ok"/>
        <xs:group ref="rpcResponse"/>
      </xs:choice>
      <xs:attribute name="message-id" type="xs:string" use="optional"/>
      <!--
        Any attributes supplied with <rpc> element must be returned
        on <rpc-reply>.
      -->
      <xs:anyAttribute processContents="lax"/>
    </xs:complexType>

I think there is a corner-case that needs to be documented.
What if the operation succeeds with warnings but no errors?

I suggest this edit to sec 4.4:   s/no error/no errors or warnings/

It might also be a good idea to point out that an operation can
still succeed even if there are <rpc-error> elements instead of
an <ok> element. (They could be warnings, not errors.)

Andy






--
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/>