Re: stopping notifications

[Balazs Lengyel <balazs.lengyel@ericsson.com>]

Hello,
I think the previous text from draft-07 is quite good:

"A NETCONF server is not required to process RPC requests on the
   session associated with the subscription until the notification
   subscription is done and may silently discard these requests."

I also remember that in Montreal we sad we don't process requests just to report errors even 
though this slightly violates the base RFC.

Two additional aspects:
1) We should preferably not mention capabilities that are not defined properly. If we do not 
forbid a specific behavior a vendor might have optional capabilities implementing it, so why 
speak about it?

2) I completely agree with Phil that we should very explicitly define the Netconf session being 
in Command-Response mode or in Notification mode.
Notification mode starts at create-subscription and its response.
Notification mode ends at replayComplete or session termination.

replayComplete MUST only be sent if a stop-time was used in the create-subscription. This is 
ambiguous even in the draft-08.

Balazs




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