reference
reference copied to clipboard
This repository contains reference implementations, specifications and tooling related to OpenConfig-based network management.
Consider the below two event-driven attributes which fit "on-change" mode type. /interfaces/interface/state/**admin-status** /interfaces/interface/state/**oper-status** 1. If gnmi "sample" mode subscribe rpc request is received for these leaf level attributes, should the...
Hi, Let's say I have the following leaf-list, which represents a list of 8 elements, each has a value in the range 0 .. 7: ``` leaf-list my_leaf { min-elements...
Provide clarification to On Change for STREAM Subscription in section 3.5.1.5.2 to exclude rapidly changing counter types and only stream updates on the initial subscription and at the heartbeat interval...
In the specification, deletes are listed as optional for `SAMPLE` subscriptions, but this is not the case when the `suppress_redundant` flag is present. Normally, if a client does not get...
``` * (M) rpc/gnmi/gnmi-extensions.md - Add clarification that unknown extensions must not be treated as an error. - Add clarification that known extensions that are invalid may be treated as...
Current version of the spec does not explicitly define the behavior in cases when a server receives a request with an unsupported extension message. - should the extension(s) be ignored...
Request Type: GNMI On-Change Subscription with Heartbeat interval. Expected Behavior from GNMI Specs: 1) Send full dump of data to tell the client of current state. Once done, send a...
Based on the gNMI specification section [3.5.2.4 SubscribeResponse Behavior Table](https://github.com/openconfig/reference/blob/master/rpc/gnmi/gnmi-specification.md#3524-subscriberesponse-behavior-table), there are these following scenarios: ID | Subscription Scenario | ONCE/POLL | STREAM -- | -- | -- | --...