Notification startTime

NETCONF
1

I Create a notification session by sending “create-subscription” request from client such that start-time is later than current time.

]]>]]>

2019-03-07T11:47:12+05:30
9-Mar-2018::15:25:43.713 **< sess:19 write:

<rpc-reply message-id=“23” xmlns=“urn:ietf:params:xml:ns:netconf:base:1.0”

ok2020-03-07T11:47:30:07+05/



According to RFC5277 it isn’t valid.
I expect to get error from CONFD.

Thansk,

Evyatar Wiesel

2

Hi,

Can you please answer?

Thanks,
Evyatar

3

Hi,
If you want to get help from the community with an issue you likely want to enable others to see the NETCONF XML output in your post.

See for example http://commonmark.org/help/ and search for “code block” example.

4

Hi,

Sorry. I paste here again the XML message:

<rpc message-id="23" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <create-subscription xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
    <startTime>2019-03-07T11:47:12+05:30 9-Mar-2018::15:25:43.713 **< sess:19 write:
</startTime>
<rpc-reply message-id="23" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"    <stopTime>
>  <ok2020-03-07T11:47:07+05:30/>
</stopTime>
</rpc-reply>
  </create-subscription>
</rpc>
5

Thanks,
In the RPC you provide the startTime is set to 2019 and stopTime to 2020, so stopTime is later than startTime in your example?

If you actually provide a startTime that is later than stopTime you will get an error, i.e.
with an error message “stopTime earlier than startTime”.