Comments on Schema-query

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

Hello Mark,

General) We retrieve a list of Netconf data model descriptions. These might be Yang modules or 
XML Schemas or something else.

The document should be merged with the netconf-monitoring draft.

Ch 1.) The Hello should contain the capabilities related to data models as well. See Netconf 
standard:
   5.2.  Data Modeling
"The device uses capabilities to announce the set of data models that the device implements..."

Ch. 1.1.1 last requirement)
a means to advertise the availability/location of the formal data model descriptions

Ch 3.1) Use simple get. We don't want new get-A, get-B, get-C operations for each new bit of data.

Ch 3.2.1.1.1)
I assume the identifier and version are unique only together not one-by-one.
Define what is the identifier? Is it the capability string/XML namespace?
The schemalist should be rather at the location netconf/schemalist similarly to the 
Notification model.
Indent the RPC-reply example!

Ch.4) Discovering the models supported by the node facilitates hacking the node, so access 
control must protect the schemalist.

regards Balazs

--
Balazs Lengyel                       Ericsson Hungary Ltd.
TSP System Manager
ECN: 831 7320                        Fax: +36 1 4377792
Tel: +36-1-437-7320     email: Balazs.Lengyel@ericsson.com

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