[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: few quick comments on notification-07
Sharon Chisholm wrote:
...
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.
I am still trying to understand this comment.
Imagine if we were writing a MIB, and decided to
leave the INDEX clause out of the 'namedProfileEntry'
OBJECT-TYPE macro, in case somebody wanted a different INDEX clause.
Priority 1 is multi-vendor interoperability.
The document should focus entirely on the standard mechanisms
agreed to by the WG.
Clearly, the 'name' of a named profile is its key.
Without a key, none of the edit-config operations
(create, delete, merge, replace) can be implemented.
I am unaware of any earlier discussion proposing a different INDEX
for this table.
...
Sharon
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/>