Re: error-path

[Martin Bjorklund <mbj@tail-f.com>]

Andy Bierman <ietf@andybierman.com> wrote:
> >>Shouldn't the correct error-path in your example be:
> >>    /rpc/edit-config/config/srv:servers/srv:server/srv:foo
> >>
> >>It needs to indicate the same node as <bad-element>.
> >>    
> >The text says "the node which is associated with the error".  If the
> >error is missing-element, my interpretation was that the error is in
> >the parent.
> >
> >If the intention is that error-path MUST indicate the same node as
> >bad-element, maybe this should be added to the text.
> >
> >
> Actually, in this case, you should be using <missing-element>,
> not <bad-element>,

The element <bad-element> is in <error-info>:

  <error-path xmlns:srv="http://www.tail-f.com/test";>
    /rpc/edit-config/config/srv:servers/srv:server
  </error-path>
  <error-info>
    <bad-element>foo</bad-element>
  </error-info>

There is no element <missing-element>.  The <error-tag> is 
'missing-element' in this case.

> and <error-path> should point to 'foo',
> which is the missing element.

Ok.


> We need to stop adding tiny little details to the draft.
> IMO, we don't need to change anything here.

Ok.



/martin

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