[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: stopping notifications
Juergen Schoenwaelder wrote:
On Sun, Jul 08, 2007 at 07:55:55AM -0700, Andy Bierman wrote:
Note that in Montreal it was agreed that processing messages just to
produce error messages just did not make sense.
I do not remember this at all.
RFC 4741, sec. 4.2 does not agree with this statement.
The <rpc-reply> is expected if the <rpc> is received
by the agent. It does not say anything in RFC 4741 about
the agent ignoring <rpc> requests for any reason.
Does it say that requests have to be processed within a given time
interval? A single threaded implementation might just postpone
No, there are no time limits for any NETCONF PDU exchanges.
I suppose an implementation can be compliant by never
processing the message and claiming no time limit has
IMO, it would be a huge CLR to forbid an agent from responding
to new <rpc> requests, but the document should not specify that this
feature is supported with some unidentified capability.
In this case, if the agent drops the <rpc> request,
then the manager should eventually time out and drop the session
(the only thing it was allowed to do in the first place).
So the text does not need to say anything except perhaps
that the agent is not required to respond to subsequent <rpc>
requests after <create-subscription> is completed.
to unsubscribe send a message to firstname.lastname@example.org with
the word 'unsubscribe' in a single line as the message text body.