reference
reference copied to clipboard
This repository contains reference implementations, specifications and tooling related to OpenConfig-based network management.
I am referring to gNMI spec ver 0.6.0 and openconfig-telemetry.yang ver "0.4.1". As I understand by yang module, the dynamic subscriptions are typically configured through an RPC channel; I presume...
``` * (M) rpc/gnmi/gnmi-specification.md - remove references to the deprecated `error` field in the `SetResponse` and `UpdateResult` messages, explicitly specifying the error handling behaviour follows the standard gRPC error model....
Hi all, I would like to clarify on how targets should interprete non-leaf paths for Get and Subscribe RPCs when any of JSON encodings is used. Consider the yang schema...
Hi All, The GetResponse message consists of: `notification - a set of Notification messages, as defined in Section 2.1. The target MUST generate a Notification message for each path specified...
clarification for allow_aggregation control
Looking for guidelines on handling keyless lists e.g., `/network-instances/network-instance[name=vrfInst1]/protocols/protocol[identifier=BGP][name=bgp]/bgp/rib/attr-sets/attr-set[index=1]/as-path/as-segment`. This list is defined without any keys. Below is a definition tree of the same. There are other occurrences as well....
### Background RFC7951 specifies the JSON format for a [list node](https://tools.ietf.org/html/rfc7951#section-5.4), but fails to specify the format for a specific element in a list node (e.g. `/interfaces/interface[name="foo"]`). The gNMI spec...
See discussion at https://github.com/openconfig/reference/issues/142#issuecomment-917086760
I have a question about GetRequest/GetResponse. Suppose we send a request which has multiple paths in it but some of the paths are deleted but some of them are not....
``` * (M) rpc/gnmi/gnmi-specification.md - Remove references to the `timestamp` field of an `UpdateResult`. - Clarify the value to be specified in the `SetResponse` `timestamp` field. ``` Fixes #63.