name: "openconfig-interface:interfaces" } elem { name: "interface" key { key: "name" value: "Loopback111" } } } • Openconfig: No path prefixes are used. These can only be used with a path to an openconfig model. The behavior of the Openconfig namespace prefixing is the same when no origin or namespace is provided. For example, the openconfig path to a loopback interface will be /interfaces/interface[name=Loopback111]/ The following example shows a gNMI path with an Openconfig namespacing: path { origin: “openconfig" elem { name: "interfaces" } elem { name: "interface" key { key: "name" value: "Loopback111" } } } • Blank: Same as the openconfig prefix. This is the default.
The following example shows a gNMI path with a blank Openconfig namespacing: path { elem { name: "interfaces" } elem { name: "interface" key { key: "name" value: "Loopback111" } } } This section describes the path prefixing used in releases prior to Cisco IOS XE Gibraltar 16.10.1. Here, path prefixing uses the YANG module prefix as defined in the YANG module definition. For example, the openconfig path to a loopback interface will be /oc-if:interfaces/ interface[name=Loopback111]/ The following example shows a gNMI Path with with legacy namespacing: path { origin: “legacy" elem { name: "oc-if:interfaces" } gNMI Protocol gNMI Namespace gNMI Protocol 10