From e72ec9bdd9941f99a9dc2cdaa7161e3520f8f5bd Mon Sep 17 00:00:00 2001 From: Caleb Geiger <48812321+ElodinLaarz@users.noreply.github.com> Date: Wed, 23 Apr 2025 13:22:56 -0400 Subject: [PATCH] Add clarification for suppress_redundant and delete behavior. --- rpc/gnmi/gnmi-specification.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/rpc/gnmi/gnmi-specification.md b/rpc/gnmi/gnmi-specification.md index d164ca9..c4a4181 100644 --- a/rpc/gnmi/gnmi-specification.md +++ b/rpc/gnmi/gnmi-specification.md @@ -1626,6 +1626,11 @@ with one of the following `modes`: `d` branching from the `b` node - if the value of `c` has changed, but `d` remains unchanged, an update for `d` MUST NOT be generated, whereas an update for `c` MUST be generated. + - Note that when the `suppress_redundant` flag is enabled, delete + notifications **must** be transmitted by the server. This is a + consequence of the fact that a client is unable to invalidate outdated + messages, as it is not possible to differentiate between a suppressed + value and an invalid value. - A `heartbeat_interval` MAY be specified to modify the behavior of `suppress_redundant` in a sampled subscription. In this case, the target MUST generate one telemetry update per heartbeat interval,