Re: notification-08 comments

[Andy Bierman <ietf@andybierman.com>]

Balazs Lengyel wrote:
> Hello
>
> Andy Bierman wrote:
> > 3.3.2, para 3:
> >
> >    A replayComplete notification is sent to indicate that all of the
> >    replay notifications have been sent.
> >
> > Use 'replayComplete' or <replayComplete>.
> >
> >    becomes a normal NETCONF session again.
> >
> > Indicate that the agent will now accept <rpc> operations.
> > Any requests which have been received but not processed by
> > the agent will now be processed in the order they were received.
> [BALAZS]: Buffering earlier received <rpc> operations for a potentially 
> long time seems bad. I would prefere discarding all <rpc> operations 
> before <replayComplete> and accepting only new <rpc> operations.

How does the agent know the next <rpc> just arrived or has been
in queue for an hour.  Isn't this implementation-dependent?
Wording it the other way (flush the queue) is also implementation-dependent.

But the other way, the manager would get no indication the <rpc> elements were
dropped.  It would wait for replies, and the agent would
wait for a new <rpc> -- and the session would hang.

> Balazs

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