...
<OP>/ncmp /<v{v-number}>/cmhandlecmhandles/<cm-handle>handles>/<data|operations|{ncmp-actionoperation}>/ds/{datastore}/<resource{resource-path>?<query>path}?{query}
URI | Mandatory or Optional | |
---|---|---|
<OP> | the HTTP method | Mandatory |
ncmp / | the ncmp root resource | Mandatory |
<v{v-number}> | version of the ncmp interface <path> is the target resource URI <query> is the query parameter list | Mandatory |
cm-handle cmhandles/<cm-handle>handles> | unique (string) identifier of a yang tree instance. | Optional |
<data|operations|{ncmp-action}> | request category - yang data, rpc operation or a (non-modelled) ncmp api action. this could be data, operations or ncmp-action | Mandatory |
ds/{datastore} | optional datastore | Optional |
<resource-path> | the path expression identifying the resource that is being accessed by the operation. If this field is not present, then the target resource is the API itself. | Optional |
<query> | the set of parameters associated with the RESTCONF message; see Section 3.4 of [RFC3986]. RESTCONF parameters have the familiar form of "name=value" pairs. Most query parameters are optional to implement by the server and optional to use by the client. Each optional query parameter is identified by a URI | Optional |
...
Future datastores to be supported by NCMP include :
1 | ncmp-datastores:passthrough-intented (RO) | Read from the live devices ietf-datastores:intended |
2 | ncmp ncmp-datastores:passthrough-operational (RO) | : Read from the live devices ietf-datastores:operational |
23 | ncmp-datastores:passthrough-candidate (RW) | Read from the live devices ietf-datastores:candidate |
...