[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Netconf Notifications WC LC: Issues & Proposed Resolutions - Part 1

Sharon Chisholm wrote:

hi



>...

2.	Section 2.1.1 (Source Ken)

The "negative response" section should clearly indicate what happens
when either the start-time is set but the stream doesn't support replay
or when the stop-time is set without having the start-time set - both of
these conditions are marked as illegal by the spec without any clear
statement about what will happen (i.e. what rpc-error will be returned)
Proposed Resolution: 
Add the following text to Section 2.1.1 under Negative Response
"If a stop-time is specified in a request without having specified a
start-time the following error is returned

   Tag:         bad-element
   Error-type:  protocol
   Severity:    error
Error-info: <start-time> Description: An element value is not correct; e.g., wrong type, 
                out of range, pattern mismatch.




This is not correct.
The bad-element error-tag defines a <bad-element> QName,
which in this case, is set to 'startTime':

  <rpc-error>
    <error-tag>bad-element</error-tag>
    ...
    <error-info xmlns:err="urn:ietf:params:xml:ns:netmod:notification">
       <bad-element>err:startTime</bad-element>
    </error-info>
  </rpc-error>

>...


Sharon Chisholm



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