WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion rpc/gnmi/gnmi-specification.md
Original file line number Diff line number Diff line change
Expand Up @@ -1356,7 +1356,9 @@ When a client wishes to receive updates relating to the state of data instances
on a target, it creates a subscription via the `Subscribe` RPC. A subscription
consists of one or more paths, with a specified subscription mode. The mode of
each subscription determines the triggers for updates for data sent from the
target to the client.
target to the client. Note that subscription to [NETCONF
events](https://datatracker.ietf.org/doc/html/rfc5277) or
YANG `notification` nodes is not under consideration at this time.

All requests for new subscriptions are encapsulated within a `SubscribeRequest`
message - which itself has a mode which describes the longevity of the
Expand Down