RE: few quick comments on notification-07

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

 hi

Having read through this Martin & Andy thread, here are my thoughts

1) If there are ambiguities in the base protocol that the notification
draft brings up, it likely makes sense to clarify them in the base
document so that all capabilities can take advantage of them

2) In general, 'any' is viewed as something you want to avoid, but
seeing as we have it in subtree filtering, we should just clarify
whether merging is supported on the subtree object and if so what the
expected behaviour is. Were there any other issues with the edit-config
of the named profiles? 

3) Does the named profile really need a key? It is easy enough to add
one, but if we don't actually need it, then I'd say leave things as is.
The current XSD, based on earlier discussion, allows people to rename
named profiles and I don't know whether making name a key still allows
that.

4) It seems we have raised minor issues with named profiles, which in
the spirit of a second working group last call, it would seem that the
correct thing to do would be to fix them, not to make drastic changes to
the document.

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