YANG actions

E208069

YANG actions are operations defined within YANG data models that allow invoking specific behaviors or procedures directly on data nodes, complementing traditional NETCONF RPCs.

All labels observed (1)

Label Occurrences
YANG actions canonical 1

How this entity was disambiguated

Statements (48)

Predicate Object
instanceOf YANG language construct
operation mechanism in YANG data models
allow invocation of procedures on data nodes
invocation of specific behaviors on data nodes
canBeDefinedUnder anydata nodes
anyxml nodes
container nodes
list entries
canBeInvokedVia NETCONF
RESTCONF
canBeMappedTo NETCONF <action> operation
RESTCONF
surface form: RESTCONF action resource
canUse if-feature statements for feature-based availability
must and when statements for conditional presence
complement NETCONF
surface form: NETCONF RPCs
constrains input and output via YANG type system
definedBy IETF NETMOD Working Group
surface form: IETF NETMOD working group
definedIn YANG
surface form: YANG 1.1 specification
differentFrom top-level NETCONF RPCs
documentation YANG module descriptions and reference statements
enable fine-grained operations on configuration data
fine-grained operations on state data
executionContext relative to the data node where the action is defined
executionModel request-response
goal to improve modularity of operational behavior in YANG models
to provide node-local operations without global RPCs
introducedInVersion YANG 1.1
lifecycle invoked on demand and do not persist as data
modeledAs children of data nodes in YANG modules
notAllowedUnder grouping statements
notification statements
rpc statements
typedef statements
operateOn YANG data nodes
relatedConcept YANG RPCs
YANG notifications
scope bound to a specific data node subtree
semantics invoked on a specific instance of the parent data node
standardizedIn RFC 7950
support error reporting via standard NETCONF/RESTCONF mechanisms
input parameters
output parameters
supportUseCase performing maintenance on a specific list entry
resetting a specific interface
triggering diagnostics on a particular device component
transportIndependent true
usedFor node-scoped operations
operations tightly coupled to configuration or state data

How these facts were elicited

Referenced by (1)

Full triples — surface form annotated when it differs from this entity's canonical label.

RFC 7950 definesConcept YANG actions