From 95392c148dfe1143ef99acb2bb11d1ddd051927f Mon Sep 17 00:00:00 2001 From: osquitun Date: Tue, 21 Jan 2025 09:23:56 -0500 Subject: [PATCH] Update gnmi-specification.md Clarification in 3.5.1.5.2 On Change for counter type exclusion and heartbeat behaviors. --- rpc/gnmi/gnmi-specification.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rpc/gnmi/gnmi-specification.md b/rpc/gnmi/gnmi-specification.md index bb412c7..d43416f 100644 --- a/rpc/gnmi/gnmi-specification.md +++ b/rpc/gnmi/gnmi-specification.md @@ -1602,7 +1602,7 @@ with one of the following `modes`: - For all `ON_CHANGE` subscriptions, the target MUST first generate updates for all paths that match the subscription path(s), and transmit them. Following this initial set of updates, updated values SHOULD only be - transmitted when their value changes. + transmitted when their value changes with the exception of rapidly changing counter types. Counter type values SHOULD be transmitted upon the initial subscription update and at each heartbeat_interval if one is specified. - A heartbeat interval MAY be specified along with an "on change" subscription - in this case, the value of the data item(s) MUST be re-sent once per heartbeat interval regardless of whether the value has changed or