Table 2: Example of a SetRequest on Leaf Value gNMI Namespace A namespace specifies the path prefixing to be used in the origin field of a message. This section describes the namespaces used in Cisco IOS XE Gibraltar 16.10.1 and later releases: • RFC 7951-specified namespaces: Path prefixes use the YANG module name as defined in RFC 7951. The RFC 7951-specified value prefixing uses the YANG module name. Value prefixing is not affected by the selected path prefix namespace. The following example shows an RFC 7951-specified value prefix: val { json_ietf_val:"{ "openconfig-interfaces:config": { “DESCRIPTION” } }" } “openconfig-interfaces:description":
An RFC 7951-specified namespace prefixing also uses the YANG module name. For example, the openconfig path to a loopback interface will be / openconfig-interfaces: interfaces/interface[name=Loopback111]/ The following example shows a gNMI path with RFC7951 namespacing: path { origin: “rfc7951" elem { gNMI Protocol gNMI Namespace SetRequest SetResponse ++++++++ Sending set request: ++++++++ update { path { elem { name: "interfaces" } elem { name: "interface" key { key: "name" value: "Loopback111" } } elem { name: "config" } elem { name: "description" } } val { json ietf val: "\"UPDATE DESCRIPTION\"" _ _ } } ++++++++ Received set response: ++++++++ response { path { elem { name:
"interfaces" } elem { name: "interface" key { key: "name" value: "Loopback111" } } elem { name: "config" } elem { name: "description" } } op: UPDATE } timestamp: 1521699342123890045 gNMI Protocol 9