RE: NETCONF Notifications Issues List

["Sharon Chisholm" <schishol@nortel.com>]

Hi

Some comments as technical contributor inline: 

> 2) RPC Methods
>   - create-subscription
>     - why isn't there a stop-time in the replay capability?  [BL]
>     - why stop notifications after replay (e.g. no tail -f mode) [BL]

The first issue was in the discussion list before the -04 update. I
tried to generate some discussion on the topic, but wasn't successful so
I kept it open. I'll try again. In the use cases I've seen, an implicit
stop time of when the command was sent works, so adding stop time
doesn't seem necessary. Thoughts?

For the second one, in the use cases I've seen, people don't want to
have to wait until the replay has completed before getting current
alarms. They therefore do not want replay and real-time on the same
subscription.


> 6) Data Models
>   - Why do we need to query the notification subscriptions? [BL]
>   http://ops.ietf.org/lists/netconf/netconf.2006/msg01226.html

If a working group in any other IETF area developed a protocol with no
way to manage it, we would think they hadn't design a proper solution.
Somehow in Netconf, we seem to be holding ourselves to a lower standard.
I think we need monitoring schema to report on the state of the system.



Sharon

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